SNAX/HLS Management Programming Manual

Appendix B Supplemental Information for
D-Series Systems
104708 Tandem Computers Incorporated B–1
This appendix provides specific information about D-series SNAX/HLS relevant to
the SNAX/HLS Management Programming Manual.
For additional information on the D-series operating system please refer to the
following Tandem documents:
Introduction to D-Series Systems
D-Series System Migration Planning Guide
System Procedure Calls Reference Manual
Guardian Application Conversion Guide
Overview of D-Series
SNAX/HLS
D-series SNAX/HLS has no new function other than the ability to accommodate D-
series features such as high PINs and D-series file and process names.
SNAX/HLS is composed of the following components:
HLSOBJ (server)
HLSCOM (command interpreter)
HLSTAP (trace analyzer)
HLSRDT (configuration builder)
HLSCRDT (RDT table converter)
The HLSOBJ server has been modified to support all of the D-series system features.
HLSTAP, HLSCRDT, and HLSRDT have not been changed and must run at low PINs.
HLSCOM must run at a low PIN. However, HLSCOM can communicate with
HLSOBJ running at either a high or low PIN.
HLSCOM cannot communicate with a remote SNAX/HLS process having a process
name exceeding five characters (including the $).
SNAX/HLS screen displays that include PINs, file names, or process names
accommodate the longer names allowed by the D-series operating system.
GETVERSION
Command
The GETVERSION command supports two new tokens in the D-series SNAX/HLS:
ZCOM-TKN-GETVSN-SUPP-PARAMS
ZCOM-TKN-GETVSN-LVL
If ZCOM-TKN-GETVSN-SUPP-PARAMS is set to TRUE in the request buffer of the
GETVERSION command, the D-series SNAX/HLS server returns the token ZCOM-
TKN-GETVSN-LVL, which will have the value
ZCOM-VAL-GETVSN-ENLIT
if the server is running on a D-series system.