SNAX/HLS Configuration and Control Manual

Step 4. Planning the Application Environment
Planning the SNAX/HLS Environment
104705 Tandem Computers Incorporated 2–17
The designer must make a critical choice as to the creator of the SNAX/HLS processes.
SNAX/HLS can be created outside the Pathway system or under the control of
PATHMON. If SNAX/HLS is created outside of Pathway, the operator has dynamic
control of the CPU assignments of SNAX/HLS, the logging files, and so on. If created
inside Pathway, these decisions must be predefined in the configuration.
The following information, applicable to both device support and gateway
applications, presents points you should consider when defining a Pathway
configuration file for SCOBOLX SNAX/HLS applications. The discussion assumes
that the Pathway system will start the SNAX/HLS processes.
SET Pathway Parameters
The SET Pathway parameters should be specified as follows.
MAXPARAMS. Set this parameter in accordance with the mode with which you want to
deliver startup configuration parameters to application servers started by PATHMON.
MAXPROGRAMS. Set this to the maximum number of program threads you plan to run
simultaneously. If you plan to run APS, you must allow one count for every instance
of the APS program you plan to run in addition to application program runs.
Remember, however, that running APS in a loop-back environment takes two copies
of APS.
MAXSERVERCLASSES. Because each copy of the SNAX/HLS server is one server class,
configure this parameter to the number of SNAX/HLS server classes plus the number
of application classes.
MAXSERVERPROCESSES. In addition to any required for the application, increase this
figure by one for each SNAX/HLS server class defined above.
MAXSTARTUPS. Allow one startup message reservation for each SNAX/HLS server
class in the Pathway system in addition to any required for the application’s server
classes.
MAXTERMS. In terms of SNAX/HLS requirements, this figure should include the total
number of sessions supported by SNAX/HLS requesters.
OWNER. The identity set by this parameter determines which group can control
Pathway.
SET TCP Values
The SET TCP values should be specified as follows.
MAXREPLY. Set this to the length of the longest reply expected. The value 9,000 is
recommended as a default value.
MAXSERVERCLASSES. This should be the same value given for the SET Pathway
MAXSERVERCLASSES parameter.
MAXSERVERPROCESSES. This value must be chosen with care. Because each
SNAX/HLS server performs internal queuing, be sure that this figure is at least as
large as the number of SNAX/HLS sessions supported by this TCP.