SNAX/HLS Management Programming Manual

SNAX/HLS Subsystem Command Descriptions
Commands and Responses
7–18 104708 Tandem Computers Incorporated
ZCMK–TKN–PROG–FILE–MOD
records the modification timestamp of the program file.
The tokens that begin with ZHLS– are described in detail in Section 6, “Common
Definitions.”
ZHLS–TKN–RDT–XFNAME and ZHLS–TKN–RDT–FILE–MOD
contain the name and modification timestamp of the RDT database.
ZHLS–MAP–INFO–PROC–CUST
is included only if customization routines have been enabled in the SNAX/HLS
server.
ZHLS–TKN–INFO–PROC–RDT–BANNER
contains the version banner of the compilation process that created the currently
loaded RDT database.
ZHLS–MAP–TRACE–CTL
is included in the response record only if one or more of the fields has a value
other than its default value that is, if one or both of the following is currently true:
The tracing facility is switched on.
The size of the tracing area is other than the default size of 64 pages.
ZHLS–MAP–TRACE–OPT
is included in the response record only if one or more of the fields has a value
other than its default value that is, if one or more of the trace options are selected.
ZHLS–TKN–TRACE–XFNAME
contains the name of a trace file, if one is defined.
ZHLS–TKN–TWO–STEP
is included only if the current value of the two-step read limit is nonzero.
ZHLS–TKN–SSCP–TEXT–SIZE
is included to specify the current value of the upper limit on the size of SSCP–LU
messages handled by SNAX/HLS when the application processes unformatted
SSCP–LU messages.
The two tokens, ZCMK–TKN–CHFILE–MAPNAME (which names the charactermap)
and ZXMK–TKN–CHFILE–MAPNOTE (which identifies the notes associated with the
charactermap) can be present in the response buffer only if:
You use the HLSCOM ALTER command.
The default charactermap file $SYSTEM.SYSTEM.ZCHARMAP exists.