SNAX/HLS Configuration and Control Manual

Programmatic Startup
Operating SNAX/HLS
5–14 104705 Tandem Computers Incorporated
Message Volume As noted in the previous discussions, SNAX/HLS uses wait I/O for logging and event
generation. This means all tasks under the control of SNAX/HLS are effectively
stalled waiting for the completion of the I/O to the LOG or EMS files. If only
important events are generated, the delays generated by the LOG and EMS traffic will
be small and will have a minimal impact on systems performance.
The selection of which messages to send to each of the possible event-reporting media
is determined by indicators in the HLSMSGS file. Installations are free to modify these
reporting indicators. Increasing the number of events that generate reports
correspondingly degrades system performance.
For information on modifying the message file, see Section 3, "Installing SNAX/HLS."
Programmatic Startup If the application design includes the programmatic initiation of the HLSOBJ module,
special care should be taken to have the correct user library fixed with the program
file. This fix-up operation is performed by system services. Once fixed, a program file
remains fixed until one of the following occurs:
The program file's user library is copied.
A cold load is performed.
The following guidelines should be noted. If no installation-supplied customization
routines are needed and SNAX/HLS has been installed with the INSTALL procedure,
the default customization routines are in the systems library. In this case, the LIB
parameter on the startup line should be omitted, as should its equivalent in the
NEWPROCESS procedure call.
If no installation-supplied customization routines are needed but SNAX/HLS has not
been installed with the INSTALL procedure, a fix-up step is required. This is also the
case when installation-specified customization routines are needed.
In this case, the LIB parameter is needed. The installation has the following choices:
Perform a fix-up of SNAX/HLS the first time the HLSOBJ file is run. A statement
of the form:
RUN HLSOBJ/LIB xxxxxx/
performs the fix-up.
The file names should reflect the real file names: HUXOBJ for the dummy routines,
or the installation's file for real routines. Subsequent initiations of the HLSOBJ file,
whether from a command interpreter or from a NEWPROCESS procedure call,
will use the results of the fixup just performed.
Specify the LIB parameter on every run of the HLSOBJ file, and specify the LIB
parameter on every NEWPROCESS procedure call you use.
The first choice might present operational complications in determining exactly when
the fix–up should be performed and in making sure that it has been performed.