Please enable JavaScript to view this site.

A-Shell Development History

Navigation: Version 4.6, builds 699-791

759 — 21 December 2000

Scroll Prev Top Next More

1. Support new ashell command line argument to specify memory size (overriding value in miame.ini.) Syntax is -r ###{,###} where ### is the size in kilobytes. The optional second value is the size of any subsidiary partitions allocated for XCALL AMOS or calling SBX modules. Example:

 

 ashell -r 800

 

The above command would set the memory partition to 800K.

 

2. Support new ashell command line argument to specify a terminal type (overriding TERM environment variable.) Syntax is -td trmtyp where trmtyp is the desired terminal type (e.g. "am62a", "dumb", etc.) Example:

 

 ashell -td dumb

 

The above command would force ashell to use the "dumb" (similar to teltyp) terminal driver.

 

3. SUBMIT.LIT 2.5(128) supports two new switches corresponding to the above ashell switches: /MEMORY:### and /TDV:tdvnam.

 

4. A bug in UNIQUE.SBR under UNIX was fixed.

 

5. The inactivity timeout feature (IATIMEOUT=##) (## in minutes) is now implemented under A-Shell/UNIX. See notes under edit 716 below for details on how the feature works. Note that aside from the 'normal' reasons for using an inactivity timeout, this can be particularly useful to clean up abandoned telnet sessions where the client PC has been powered down or reset. Otherwise, these can go unnoticed by the server for two hours or more, and consequently by A-Shell as well (since it never gets a SIGHUP.) With the inactivity timeout, it would get a basic error 254 and will be shut down just as for a SIGHUP or SIGTERM. One other note: since merely shutting down A-Shell in this case could leave the UNIX parent process running (since it hasn't seen the hangup signal), you might benefit from using the -hp switch on the ashell command line (which will cause A-Shell to sends its parent a SIGHUP when it is forced to exit this way.)

 

6. TRACE=LOCKS (or SET TRACE LOCKS ON) has been aesthetically improved to be somewhat more user friendly in the case of XLOCK and FLOCK locking conflicts. It still shows information about the lock we are waiting for on the status line (or line 24 if no status line present) but it now shows the job #, job name, and user name of the owner of the lock. Also, it only updates this display every 10-20 tries (2-5 seconds) instead of multiple times per second, which was both distracting and a needless waste of CPU time and bandwidth. So, if you use FLOCK.SBR, you might consider adding TRACE=LOCKS to your miame.ini file permanently so that your users will be able to see who has them blocked.

 

7. XCALL MESAG now uses INFLD internally, which means that you can use the ^P command to print the screen at that point.