SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC

SNAX/APC Configuration and Management Manual—138787

4-2

Your Level of Configuration Experience

Your first consideration is your background in configuration. This could be one or more

of the following:

•

You have a background in IBM’s LU 6.2 implementations and know the IBM

configuration verbs, but are new to the Tandem system and/or SNAX/APC.

•

You have configured SNAX/APC for previous releases, but now have to implement

the latest release (using SCF).

Read the following subsections that are most appropriate to your situation.

LU 6.2 Background

Although the application programmer and the transaction program should see no

difference between the various implementations of LU 6.2 (at least where the base

option set is concerned), the actual system configuration will obviously vary from

system to system.

The names and syntax of LU 6.2 verbs and parameters differ from the SNAX/APC

implementation of the same functions. This is true for change number of session

(CNOS) verbs, session control verbs, and definition verbs. Refer to Part II, SCF

Reference for SNAX/APC.

The SNAX/APC process maintains all configured objects and their current states in a

database. This database may be permanent or temporary; this is specified by using the

PARAM CONFIG parameter at process startup. A permanent database can also be used

to warm start the SNAX/APC process, ensuring a faster start than rerunning the

command (OBEY) files.

Warm Start

If you use PARAM CONFIG when starting SNAX/APC, and specify the name of an

existing file, SNAX/APC will read that file and add any objects referred to in the file.

With a warm start, SNAX/APC will also process any LUs added using the autostart

feature. For further details, see Part II, SCF Reference for SNAX/APC

Cold Start

If you use PARAM CONFIG and specify the name of a nonexistent file, then

SNAX/APC creates the file and awaits configuration information from the SPI interface.

All configuration information will be saved in that new file, for subsequent re-use.

If PARAM CONFIG is not specified, the SNAX/APC process will be started without

any configuration, and all of the objects added subsequently will not be retained after the

SNAX/APC process is stopped.

The following is an example of specifying the CONFIG parameter:

PARAM CONFIG $QA3.APCCONF.AL01

RUN APCOBJ/NAME $AL01, NOWAIT, CPU 1/2