SNAX/HLS Configuration and Control Manual

Trace Analysis
Product Overview
104705 Tandem Computers Incorporated 1–11
Creating A RDT File The following example shows a typical session creating and using a RDT file.
1. Edit the Source file:
> EDIT RDTTEXT
{Perform changes}
*EXIT
2. Compile the RDTTEXT file:
> RUN HLSRDT / IN RDTTEXT, OUT $S.#LP / RDTDATA
3. Run HLSOBJ, passing the newly generated RDTDATA table:
> RUN HLSOBJ/IN RDTDATA,OUT out—file ,&
NAME hls—process—name ,NOWAIT/ Log *
The Operator Interface A command interface, HLSCOM, is delivered with SNAX/HLS. HLSCOM supports a
range of commands suitable for operator control, error determination, and system
tuning. HLSCOM can also enable, disable, and configure trace files for SNAX/HLS
traces.
HLSCOM supports commands that display detailed information about the SNA
protocol in use on the SNAX/HLS session as well as the current states of the SNA
finite state machines (FSMs). This information is useful to systems programmers and
technical support personnel when problems arise.
Prototyping and
Simulation
The Application Prototyping and Simulation utility (APS) provides a convenient
means for application designers and developers to execute verb requests interactively
and to view the replies immediately. An application design can be quickly prototyped
without writing code. Questions about error recovery, message contention, and verb
execution can be explored with APS.
APS also functions well as an educational tool. With APS, programmers unfamiliar
with SNAX/HLS learn about verb dynamics in a few hours of instruction.
APS is a SCOBOLX requester that presents one screen for every SNAX/HLS verb
request. Verb execution is selected by function key. The APS user selects the verb to
be executed by function key, fills in the verb indicators, directs APS to send the verb to
the SNAX/HLS server process, and views the result.