SNAX/APC Configuration and Management Manual

Introduction
SNAX/APC Configuration and Management Manual—138787
1-9
The SNAX/APC Application Prototype Simulator
System
When a remote application issues a request for communication with a TP, the
SNAX/APC process first checks for a ready TP of the specified type. If no copy is
available, the SNAX/APC process uses the Dispatcher to create a new instance of the
specified TP.
A Dispatcher can start any TPs defined for a SNAX/APC process (that is, Dispatchers
are not configured to start specific TPs). When a Dispatcher starts a TP, that Dispatcher
is engaged until the associated TP completes its tasks. Thus, there should be as many
Dispatchers as the maximum number of concurrent conversations.
The Dispatcher is a Pathway application requester written in SCREEN COBOL, and its
ability to run at high PINs is dependent on its control programs. It can run at high PINs
if it is run under the D-series or G-series Pathway (or NonStop TS/MP and Pathway/TS)
and Enable software.
The SNAX/APC Application Prototype Simulator System
The SNAX/APC Application Prototype Simulator (APS) is a SCREEN COBOL
program that enables you to submit basic or mapped verbs interactively to SNAX/APC
for execution and thus carry on a conversation with a partner TP. You can use APS to
test proposed sequences of verbs in conversation with partner TPs. APS also is an
excellent tool for learning how to use the SNAX/APC verbs. It enables you to observe
the operation of the verbs without having to write any programs.
APS is a Pathway application requester written in SCREEN COBOL, and its ability to
run at D-series or G-series high PINs is dependent on its control programs. It can run at
high PINs if it is opened under the D-series or G-series Pathway (or NonStop TS/MP
and Pathway/TS) and Enable software.
See the SNAX/APC Application Programming Manual for further details on APS.
Logging
You should use the Event Management Service (EMS) rather than the SNAX/APC log
file for the logging of messages. EMS is a standard message handling feature of most
Tandem subsystems. Messages provide a means to diagnose problems related to the
SNAX/APC subsystem. The most common SNAX/APC messages are the initialization
statistics messages; other SNAX/APC messages indicate errors occurring in the
SNAX/APC process.
In addition to EMS messages, log messages can be used and are written to the
SNAX/APC log file. The LOGFILE startup parameter controls logging and specifies
the log file name. Each log message is preceded by the date, the time, and the name of
the SNAX/APC process that sent the message. However, EMS message collection is the
preferred method for logging messages.
Consult the SNAX/APC Management Programming Manual for further details on
interpreting log file messages. Consult Appendix E, Event Management
for further
details on interpreting event messages.