rev_tsx

SUMMARY OF REVISION J.05 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

TSX J.05 updates the following modules from revision J.04.

Module	Format	Contents
TSXEQU	SED	TSX equates
TSXSYS	SED	TSX macro library
TX.SYM	LIB	TSX symbiont processor
TX.LRP	LIB	TSX line read processor
TX.MSG	LIB	TSX message processor
SCREEN	TOC	TSX screen processor
. (dot)	TOC	"." JM directive

J.04 users can upgrade by replacing these modules. Systems with earlier J.x revisions of TSX can update additional modules changed in all previous point releases discussed below, or you can perform a complete installation.
TX$SYM has a correction that eliminates an extra control character being printed if the second character of a buffer was NULL, i.e. Buf = #3100, write two or more bytes.
TX.LRP and TX.MSG were fixed to issue the proper error message when an invalid user name was defined for an autologon port.
Changes in TSX were completed August 5, 1998 for release J.05 to ensure complete Year 2000 compliance (Y2K). The changes were generally cosmetic. The SCREEN utility was changed to print a 4-digit date when the LDI directive was used. Dates were removed from the DUMP and DBU command listings. The JM utility "." (dot) was modified to display a 4-digit year.

SUMMARY OF REVISION J.04 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

TSX J.04 updates the following modules from revision J.03.

Module	Format	Contents
TSXEQU	SED	TSX equates
TSXSYS	SED	TSX macro library
TX.LRP	LIB	TSX line read processor
TX.SOR	LIB	TSX signon read request
TX.MSG	LIB	TSX message processor

J.03 users can upgrade by replacing the modules listed above. Systems with other revisions must perform a complete upgrade.
The fixes in J.04 involved autologon terminals. Enhancements in previous versions of TX.LRP under some conditions may cause a read to be requeued for autologon terminals during TSX startup. Since these ports never had performed a read, some variables were not initialized and TSX may protect abort. Other symptoms seen on MAX IV rev L two map systems also included destroying low memory. Obviously, operation is unpredictable with uninitialized variables, so if you are using autologon ports or have tried to with intermittent success in the past, this upgrade should stabilize things. An additional message, PORT yyy AUTOLOGON USER NAME NOT VALID, was added to eliminate a TSX loop when an autologon user name is not in the list of valid user names or it is invalid for use on the port specified. This will result in a locked port. An additional bit, XLPMA, was added to the translator terminal characteristics word (XLTCW) as bit 13. The presence of this bit indicates that a terminal is capable of page mode operation.

SUMMARY OF REVISION J.03 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

TSX J.03 updates the following modules from revision J.02:

Module	Format	Contents
TSXEQU	SED	TSX equates
TSXSYS	SED	TSX macro library
TX.SYM	LIB	TSX symbiont front end
TX.LRP	LIB	TSX line read processor

J.02 users can upgrade by replacing the modules listed above. Systems with other revisions must perform a complete upgrade.
Module TX.SYM has been modified to correct an error introduced at the J.01 revision. When device names were used in the TSX DEVICE macro rather than logical file names, invalid LDT addresses were generated during initialization that would cause some ports not to operate. Typically you may have seen the "AWAITING ONLINE STATUS" message for these ports when using the OC command /PTS.
Module TX.LRP has been modified to correct an error introduced at the J.01 revision. This module was failing to detect excessive errors like too many attempts to log on, which would produce the message "TOO MANY ILLEGAL USER NAMES".

SUMMARY OF REVISION J.02 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

TSX J.02 updated the following modules:

Module	Format	Contents
TSXEQU	SED	TSX equates
TSXSYS	SED	TSX macro library
TX.SYM	LIB	TSX symbiont front end

The following modules are new for the J.02 revision:

Module	Format	Contents
TX.COP	LIB	TSX data copy routines
TX.SLW	LIB	TSX user message binary service

The J.02 release separates the common record copy routines used by the symbiont into a new module TX.COP.
A binary service TX$SLM allows a message to be sent to any port in use by a user or to all ports logged on. Users are identified by user alias, not user name. This service is accessed by performing a binary write operation and must be configured as a TSX binary service to be included in TSX.

SUMMARY OF REVISION J.01 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

TSX J.01 updated the following modules:

Module	Format	Contents
TSXEQU	SED	TSX equates
TSXSYS	SED	TSX macro library
TX.SYM	LIB	TSX symbiont front end
TX.MVR	LIB	TSX move read data module
TX.TRA	LIB	TSX trace module
TX.SS$	LIB	TSX symbiont system subroutines
TX.DTR	LIB	TSX reset DTR (hang up) routine
TX.PSE	LIB	TSX port service executive
TX.TCI	LIB	TSX TCL and channel initializer
TX.LRP	LIB	TSX line read processor
TX.INI	LIB	TSX initialization subroutine
TX.SP	LIB	TSX SPL interface routines
TX.ECP	LIB	TSX exceptional condition probe
USE	LIB	USER OC overlay (must be cataloged)

The following modules are new for the J.01 revision:

Module	Format	Contents
TX.UNR	LIB	TSX username read binary service
TX.UNW	LIB	TSX username write binary service

The new files provide a program interface to add, delete, modify, and inquire on user name parameters as well as control the entry permissions for each user name. The user name services are optional. To include the user name services, you must add two statements to the TSX configuration file. Refer to the TSX Reference Manual for further instructions on using these binary services.
The TSX trace has been enhanced to provide more precise formatting of data and UFTs. Tracing of read data buffers for binary services has been added.
The format of the I$NOD. table used for binary services now includes additional information. The 6-word negative UFT has been added, plus the UFT MIAP. These changes have modified the order of some of the elements in this table from prior revisions. This probably will not affect most binary services, but you should check any custom services. At most, a reassembly may be needed.
Initialization of communications channels has been changed at startup to reset connections for dial modems, Telnet channels, etc. Dial devices are disconnected by issuing a Home+Disconnect or by outputting an asynch subchannel hardware command to reset DTR if there is no TCL and the controller type is a 190X or 480X type. After disconnection, a delay of 4 seconds occurs; then the channel is initialized using a Read and Terminate sequence, causing DTR to be asserted. TSX ports that can receive ring events will not have any I/O queued. Ports that do not use events to begin a log-on sequence assert a flag that requests the log-on display to be generated. Non-dial ports are also initialized with the Read and Terminate sequence to cause DTR to be asserted, if needed.
Before sending the logon display, TSX tests the devices to see if the proper RS232 signals are correct, indicating a connection is valid. When the proper status is present, the data will be written to SPL and then monitored to see if it was successfully output. When output is completed, a read is queued to receive the username. Autologon ports have no need to queue the read for the user name. Experience has shown that newer "smart modems" are sensitive to any I/O until all RS232 signals have stabilized. Note: If you have a 4806 or 4807, DSR and DTR do not exist. TSX only examines Carrier Detect to determine if a proper status is present. But with this signal, modems can successfully be used on these channels. Since DTR is missing, it is not possible for TSX to force the modem to hang up. You cannot use the signal loop back jumpers 6820 to qualify Carrier Detect as in other types of RS232 channels for 4806 and 4807 channels since DTR(20) is missing. If your equipment does not supply a signal for Carrier Detect (8), you can define the channel as a Current Loop (CL) to ignore this status.
The new startup logic has been made identical with signal handling during session termination and port aborts to insure proper initialization of ports. Modem and IPS or IPC Telnet ports will be disconnected when TSX is started.
IPS2 Telnet channels will be initialized by supervisory reads from the TX.TLM module if present in your configuration. This system is event driven like a modem but uses a Break signal when a connection is established. It is not generated as a DIAL device.
IPC Telnet channels do behave like modems and should be defined as DIAL devices. They generate Ring, Break, and Disconnect events.
Additional logic has been added to improve restarting TSX in spite of TCT queues that may or may not be terminated or user tasks still in the system that may have nodes in TSX PDT. Now all terminated nodes will be returned at start up. As previously, the terminate notification bit TER in PDTSTA is reset and any existing user tasks are killed, allowing their nodes to be removed by MAX. Previously, if any of these tasks had terminated nodes, the task would not exit since neither TSX nor MAX would process the terminated node. Normally we don't expect you to have to restart TSX often, but it is convenient to be able to do so and have everything clean up correctly, especially during development.
When SPL detects a nonrecoverable output device error, it stops the output and prints an error message, usually at the operator console. TSX detects such events and will log off a session if it exists. If no session exists, TSX will lock the port, assuming that something is broken. Dial devices are not locked however, since it is assumed that a DTR reset or disconnect function will clear any externally offending problems. This is necessary to guarantee that modem ports are not locked. If a device is off-line, additional logic has been added to lock the port until the problem can be corrected. The previously described logic has not been changed, but now TSX turns on SPL's output channel with the skip option to delete the offending operation and insure output is functioning.
TSX and SPL never place output or input devices off-line since only local recovery I/O is used. Sometimes however, other tasks, like TMP or OC, perform system recovery I/O and may leave a TSX logical device off-line. TSX now tests all devices on each port at 2 second intervals. If a device is found off-line, TSX will place the device back on-line and terminate all I/O queued to the device. TSX tracks the number of devices found off-line for each port. If 8 consecutive off-line conditions are detected for a port, TSX will leave the device off-line, terminate the session (if logged on), and request a port lock. A message is printed to indicate the nature of the problem. TSX tries to locate the node that was being processed when the off-line occurred and, if found, will display the status in the diagnostic message. A zero status indicates that no off-line node was found.
TSX will now accurately generate the "Enter date and time" message every 30 seconds until the system time is valid, without regard to the system tick rate.
A correction has been made to the OC overlay USER to prevent loss of user names and a possible protect abort by TSX after removing a user name. This only occurred when a system was generated with exactly 16 ports or even multiples of 16 ports.
HP users can use the HPTERM translator on HP systems that support XWindow terminals to access TSX applications, including page mode forms, via an Ethernet connection from the HP to the MODCOMP. Ethernet support may be either through a MODCOMP IPS2 or a Logical Data Corporation IPC. The translator is named HPT and is supported by the library routine TX.HPT.
The translator supports user-definable colors that allow selection of more pleasing muted colors. Your may replace the standard library routine HPT$CT by assembling a new version. The source is installed in your TSX source library during installation.
Note: As of 08/18/95, HP is currently working on a problem that causes HPTERM to malfunction when performing a send function. This happens only to very few screens. If you experience this problem, verify it by holding TSX and transmitting data in your form. If the screen is modified before resuming TSX, it's probably an HP problem.

SUMMARY OF REVISION J.00 CHANGES

TIME SHARING EXECUTIVE AND TRANSACTION PROCESSOR (TSX)

Support for the Logical Data Corporation IPC Multiline Serial Controller (Asynchronous) and the IPC Telnet Server devices has been added. The IPC Telnet devices emulate standard asynchronous devices (including ring, break, and disconnect events) and require no additional software.
Support for MODCOMP IPS2 Telnet Server devices has been added (requires an optional software module). This support allows MODCOMP Telnet channels to function as dialup, asynchronous channels through TSX. The optional software includes a TSX module for supervising the Telnet server devices and for reporting connected network terminals, plus a replacement TELSRV program to substitute for the MODCOMP TELSRV program, which processes only nonTSX Telnet server devices.
Support for MAX IV revision L.0 added.
If OC has been attached to a TSX port, it will be removed automatically at logoff.
TSX device errors will only cause logoff if they involve the primary device on the port.
A new TSX PC File Support module compatible with this revision of TSX must be installed. PC File Support must be revision D.00 or later.
No changes from the I.00 version are required in the TSX generation procedure or generation statements unless the Telnet support is added.
Corrections have been made to the flow control in the spooling package.