Networking and Data Communications Library SNAX Creator-2 Configuration and Control Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual describes how to configure and manage a SNAX Creator-2 subsystem using the Subsystem Control Facility (SCF). The SNAX Creator-2 subsystem works with Tandem access methods, such as SNAX/XF and SNAX/APN, to enable terminals to log onto applications on Tandem NonStop systems.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second Third 100697 105773 117143 SNAX Creator-2 D20 SNAX Creator-2 D20 SNAX Creator-2 D30 D72.00 based on D20.01 D30.00 D30.02 May 1994 January 1995 July 1995 New editions incorporate any updates issued since the previous edition.
New and Changed Information Changes in this edition of the SNAX Creator-2 Configuration and Control Manual include the following: In 1994, the Pathway transaction processing software that runs on the Himalaya and later models of the Tandem NonStop system was repackaged as two separate products: NonStop Transaction Services/MP (NonStop TS/MP), consisting of the Pathsend procedure calls, the LINKMON process, the PATHMON process, and the PATHCOM process and interface Pathway/Transaction Services (Pathway/TS),
New and Changed Information (This page left intentionally blank) iv 117143 SNAX Creator-2 Configuration and Control Manual
Contents About This Manual xi Notation Conventions Section 1 xiii Introduction to SCF for SNAX Creator-2 SNAX Creator-2 1-1 SNAX Creator-2 With SNAX/XF 1-1 SNAX Creator-2 With SNAX/APN 1-1 SCF Interface to SNAX Creator-2 1-2 Configuration Database 1-2 SCF Product Module for SNAX Creator-2 System Environment 1-3 1-3 Distributed Systems Management 1-3 Subsystem Control Point (SCP) 1-3 Subsystem Control Facility 1-4 SCF Commands 1-4 Objects 1-5 How SCF Works 1-7 Running SCF 1-7 Input Sources and Output
Contents Modifying the SNAX Creator-2 Subsystem 2-12 Altering SNAX Creator-2 Subsystem Characteristics Changing the Primary CPU Designation 2-13 Modifying SNAX Creator-2 Objects 2-13 Adding New Objects 2-13 Altering Object Attributes 2-13 Deleting Objects 2-14 Inquiring About the SNAX Creator-2 Subsystem 2-14 Obtaining File System Open Information 2-15 Obtaining Version Information 2-15 Obtaining Statistics 2-15 Inquiring About SNAX Creator-2 Objects 2-15 Obtaining Object Attribute Values 2-15 Obtaining Ob
Contents SESSION Object Type 3-7 Object Name Format 3-8 Object States 3-8 Attributes 3-8 Commands 3-8 SU Object Type 3-8 Object Name Format Object States 3-9 Attributes 3-9 Commands 3-10 3-9 SUBSYS Object Type 3-10 Object Name Format 3-10 Object States 3-10 Attributes 3-10 Commands 3-11 Complex Naming Example Section 4 3-12 SCF Commands for SNAX Creator-2 Command Overview 4-1 Special Considerations for the ASSUME Command Command Security 4-2 Commands and Object Types 4-3 Command Syntax 4-4 Common Comm
Contents START SU Command 4-39 STATS SUBSYS Command STATUS Command 4-44 STOP SU Command 4-52 VERSION Command Section 5 4-40 4-53 Attributes and Built-in Functions for SNAX Creator-2 Attributes 5-1 Case Sensitivity of Attribute Values 5-1 Filtering of Attribute Values 5-2 Expressions Used As Attribute Values 5-2 Expressions 5-7 Literal Characters 5-7 References to Entries 5-7 Built-in Functions 5-7 Appendix A SCF Command Syntax Summary for SNAX Creator-2 Appendix B SCF Error Messages for SNAX
Contents Using the [#num] Function C-3 Using the [#num1 num2] Function C-3 Using an Entry With the [#OPENNAME] and [#SERVICE] Functions C-4 Load-Balancing Pathway Applications Using Literal Values C-5 Using the [#num] Function C-5 Generating METHOD Values Appendix D C-4 C-5 Configuring SNAX Creator-2 With SNAX/APN Appendix E Configuring SNAX Creator-2 With SNAX/XF New SNAX/XF Configurations E-1 PLU Names Supplied by SNAX/XF E-2 PLU Names Supplied by SNAX Creator-2 Migrating from the Old Creator Proces
Contents (This page left intentionally blank) x 117143 SNAX Creator-2 Configuration and Control Manual
About This Manual This manual explains how to perform configuration and management tasks and describes the Subsystem Control Facility (SCF) interactive interface that enables you to configure, control, and inquire about a SNAX Creator-2 subsystem. Who Should Read This The intended reader of this manual is a person performing configuration and Manual management of the SNAX Creator-2 subsystem.
About This Manual Your Comments Invited SNAX Creator-2 is used with SNAX/APN and the Tandem Logon Manager for IBM Systems (ILOGMGR) to implement the extended logon facility (XLF).
Notation Conventions General Syntax Notation UPPERCASE LETTERS The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: ALTER APPL lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation Conventions Notation for Messages Ellipsis ... An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown.
1 Introduction to SCF for SNAX Creator-2 This manual describes the subsystem-specific details for using the Subsystem Control Facility (SCF) interactive interface to configure and control the SNAX Creator-2 subsystem. This section introduces: The SNAX Creator-2 subsystem The SCF interface to the SNAX Creator-2 subsystem Tandem’s Distributed Systems Management (DSM) The Subsystem Control Facility (SCF) Although the operating system views SNAX Creator-2 as a process, SCF views SNAX Creator-2 as a subsystem.
Introduction to SCF for SNAX Creator-2 SCF Interface to SNAX Creator 2 Figure 1-1.
Introduction to SCF for SNAX Creator-2 Distributed Systems Management SCF Product Module for SNAX Creator-2 The SCF product module for SNAX Creator-2 runs as a separate process started by SCF. The object-code file for this product module, shown in the SCF LISTPM command, is named ZCRESCF and has a file code of 100. This file normally resides in the $SYSTEM.SYSTEM subvolume. Because this product module is a separate process, the “execute” attribute for its object file should be secured for network access.
Introduction to SCF for SNAX Creator-2 Subsystem Control Facility Figure 1-2 . Role of SCP SNAX/XF Terminal SCF Command (OBEY) File Log File SCP ($ZNET) SNAX Creator-2 SNAX/APN 002 Subsystem Control SCF is used to configure, control, and collect information about Tandem data Facility communications subsystems, such as SNAX Creator-2. This subsection provides general information about SCF.
Introduction to SCF for SNAX Creator-2 Subsystem Control Facility screening are called sensitive commands. Sensitive commands are limited to the following user IDs: Members of the super group (group ID 255) Members of the user group that owns the process to which the command is sent. Other commands make no changes, but simply allow the SCF user to view information. SNAX Creator-2 does not perform any security checking on these commands, but allows any user to perform them.
Introduction to SCF for SNAX Creator-2 Subsystem Control Facility Section 3, “Objects for SNAX Creator-2,” defines the hierarchy, object types, and naming conventions for SNAX Creator-2 objects. Some SCF commands include an optional SUB parameter that refers to all subordinate objects. The SUB parameter has the form: SUB [ subtype ] This parameter selects the subordinate objects the command affects. subtype can be a subordinate object type or one of the keywords NONE, ALL, or ONLY.
Introduction to SCF for SNAX Creator-2 Subsystem Control Facility Some SCF commands include an optional SEL parameter that selects only objects that are (or are not) in a particular object state. The SEL parameter has the following syntax: SEL [NOT] state When the SEL option is used without the NOT keyword, the command affects only those objects that are in the specified state. When the SEL option is used with the NOT keyword, the command affects only those objects that are not in the specified state.
Introduction to SCF for SNAX Creator-2 Subsystem Control Facility Input Sources and Output Destinations SCF accepts command input from a terminal or a disk file; it directs output to a disk file, an application process, a terminal, or a printer. The initial input source and output destination are determined by the RUN command used to initiate SCF. At any time during an SCF session, both the source and the destination can be temporarily changed.
2 Startup and Configuration of SNAX Creator-2 This section covers the following topics: Distribution of Function Starting SNAX Creator-2 Configuring SNAX Creator-2 objects Modifying the SNAX Creator-2 subsystem Modifying SNAX Creator-2 objects Inquiring about the SNAX Creator-2 subsystem Inquiring about SNAX Creator-2 objects Distribution of A network may contain multiple SNAX Creator-2 subsystems and access methods.
Startup and Configuration of SNAX Creator-2 Starting SNAX Creator-2 The RUN command for SNAX Creator-2 has the following syntax: >[ RUN ] CREOBJ [/runoptions/] [ param [ ,param ] … ] CREOBJ is the name of the object file for the SNAX Creator-2 subsystem. runoptions is one or more of the standard TACL run options, separated by commas. These are documented in the TACL Reference Manual.
Startup and Configuration of SNAX Creator-2 Starting SNAX Creator-2 TERM terminal-name terminal-name is used by SNAX Creator-2 as the home terminal for diagnostic information. Production environments should not require this usage. RUN Command Startup Parameters The startup parameters can be specified in the RUN command for SNAX Creator-2 or in PARAM statements before the RUN command.
Startup and Configuration of SNAX Creator-2 Starting SNAX Creator-2 parameters is omitted or specified with no value, output designated for this collector is suppressed. The default value is no value, which indicates output designated to these collectors is suppressed. CONFIG filename specifies a file that contains the SNAX Creator-2 configuration database. If the file does not exist, it is created by SNAX Creator-2. SNAX Creator-2, as distributed, has no function assigned to these alternate collectors.
Startup and Configuration of SNAX Creator-2 Starting SNAX Creator-2 If problems are encountered accessing the logging file, SNAX Creator-2 will not start. SWAPVOL disk-name specifies the name of the disk that is used for extended-memory swapping. disk-name must be a simple unqualified device name; for example $ABC or $SYSTEM. If the value is omitted or the device it names is not a local disk volume, the default swap volume is used.
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects Example 2−PARAM Statements This example illustrates a SNAX Creator-2 startup using PARAM statements: CLEAR ALL PARAM PARAM BACKUPCPU 11 PARAM CONFIG $DATA.SXCRE.CONDATA RUN $SYSTEM.SXCRE.CREOBJ / NAME $CREA , CPU 10 , NOWAIT / & & & Configuring SNAX The RUN CREOBJ command identifies a configuration database (configuring one if Creator-2 Objects needed) and creates a SUBSYS object for the SNAX Creator-2 subsystem.
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects For example, to enter the expression A[1]~B[2] as the value of an attribute, you need to enter the expression as follows: A~[1~]~~B[2~] Expressions Expressions can contain literal values, but also one or more of the following items enclosed in square brackets (to distinguish them from literals): Names of entries that have been defined by adding an ENTRY object, for example: ADD ENTRY myentry, TEXT "TACL" Built-in functions that
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects The PASSWORD attribute specifies a password for the SU. The password must match the password in the access method configuration. If a password has not been entered for the access method, do not specify this attribute, or define it to be an empty string.
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects ADD , , , APPL $CREA.C-mypath METHOD PATHWAY PATHMON [mypathmons] PROGRAM [myprogs] When a logon for the application mypath is received, the preceding ADD APPL command is evaluated as follows: ADD , , , Adding APPL Objects APPL $CREA.C-mypath METHOD PATHWAY PATHMON "$pmon1 $pmon2 $pmon3" PROGRAM "prog1 prog2" The ADD APPL command is used to add APPL objects to the SNAX Creator-2 configuration database.
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects For example, the following command configures a TACL application named mytacl with values specified for the four common optional attributes: ADD , , , , , APPL $CREA.C-MYTACL METHOD TACL CPUS "0 1 2 3 4 5 6" MAXARGS 5 MINARGS 1 SYSTEM \node1 Configuring TACL Applications TACL applications are started on the system specified by the SYSTEM attribute (this defaults to the system on which the SNAX Creator-2 is running).
Startup and Configuration of SNAX Creator-2 Configuring SNAX Creator-2 Objects In addition to the CPUS, MAXARGS, MINARGS, and SYSTEM attributes, when the METHOD of the APPL object is SERVER, the following attributes are supported: SERVER, which lists the names of one or more running server processes. If the server process is on a different node from SNAX Creator-2, the node name must be included. MESSAGE, which specifies a message to be sent to the server process.
Startup and Configuration of SNAX Creator-2 Modifying the SNAX Creator 2 Subsystem For example, the following command configures the Pathway application named C-mypath: ADD , , , , , APPL $CREA.C-mypath METHOD PATHWAY PATHMON \node.$pmon PROGRAM prog1 PROCESS $gdsx PRINTER $prt1 When a user logs on from a terminal (say from a terminal named $line.
Startup and Configuration of SNAX Creator-2 Modifying SNAX Creator 2 Objects For example, assume that SNAX Creator-2 was configured on startup with the following RUN command run options and startup parameters: RUN $SYSTEM.SXCRE.CREOBJ / NAME $CREA , CPU 10 , NOWAIT / BACKUPCPU 11 , LOG $TERM , CONFIG $DATA.SXCRE.MYFIG In this configuration, the LOG parameter specifies that log messages be sent to $TERM.
Startup and Configuration of SNAX Creator-2 Inquiring About the SNAX Creator 2 Subsystem The following ALTER APPL command increases the number of CPUs and changes the disk new TACL applications use from $data to $data1: ALTER APPL $CREA.C-mytacl , CPUS "0 1 2 3 4 5 6 7 8" , SEGVOL $data1 For this example, assume that an SU object is defined as follows: ADD , , , SU $CREA.$SSCP.#cre PASSWORD abcdef NAMERULE PLUNAME PLUNAME billing The following command sequence changes the PLU name: STOP SU $CREA.$SSCP.
Startup and Configuration of SNAX Creator-2 Inquiring About SNAX Creator 2 Objects You can also use INFO, NAMES, and STATUS commands with a SUBSYS object −see “Inquiring About SNAX Creator-2 Objects,” later in this section. Obtaining File System Open Information The LISTOPENS SUBSYS command displays a list of all file system opens that apply to the specified SNAX Creator-2 subsystem and information associated with each.
Startup and Configuration of SNAX Creator-2 Inquiring About SNAX Creator 2 Objects (This page left intentionally blank) 2–16 117143 SNAX Creator-2 Configuration and Control Manual
3 Objects for SNAX Creator-2 The individual components of a SNAX Creator-2 subsystem are called objects. Objects can be configured, controlled, and queried by the operator. Each object belongs to an object type. For example, a particular application might be an object of type APPL. SNAX Creator-2 contains six object types: APPL, CONNECTION, ENTRY, SESSION, SU, and SUBSYS.
Objects for SNAX Creator-2 Object Names and Object States Object Names and Object States Object Names This subsection provides an introduction to the naming conventions for objects and the concept of object states. All objects in the SNAX Creator-2 subsystem, except null objects, have an object name. An object name uniquely identifies an object of a given type within the subsystem. Object names are not case-sensitive: either uppercase or lowercase alphabetic characters can be used.
Objects for SNAX Creator-2 APPL Object Type object name returns information about all seven-character APPL names with the letter W as the fourth character. Object States An object in the SNAX Creator-2 subsystem is always in one of several allowable operational states. Certain commands have no effect on an object when it is in one state, but can affect the same object when it is in a different state. For most objects, the operational state changes as commands are issued against the object.
Objects for SNAX Creator-2 APPL Object Type pluname is a character string that satisfies the following criteria: It must contain from one through eight characters. The first character must be either alphabetic (A through Z) or one of the special characters (@,#, or $). Each of the second through eighth characters must be alphanumeric (A through Z, and 0 through 9) or a special character (@,#, or $).
Objects for SNAX Creator-2 CONNECTION Object Type Attributes An APPL object has the following attributes. See Section 5, “Attributes and Expressions for SNAX Creator-2,” for more information about these attributes.
Objects for SNAX Creator-2 ENTRY Object Type $crename2 is a unique name commencing with a dollar sign followed by one alphabetic character and up to four alphanumeric characters. Example If the SNAX Creator-2 subsystem is \NODE2.$CREA and you add an SU \NODE1.$SSCP.#MYSU, a CONNECTION object subordinate to this SU object is automatically created and is named: \NODE1.$SSCP.#MYSU-\NODE2.
Objects for SNAX Creator-2 SESSION Object Type At device logon, the preceding ADD APPL command is equivalent to: ADD , , , Object Name Format APPL $CREA.C-PATH1 METHOD PATHWAY PATHMON "$PWY1 $PWY2 $PWY3" PROGRAM "PROG1 PROG2" An ENTRY object name has the following syntax: entry entry is the unique name of an entry. It can be up to 40 characters long, must start with a letter or underscore, and can contain only letters, numbers, and underscore. Blanks are not allowed. The name is case-insensitive.
Objects for SNAX Creator-2 SU Object Type Object Name Format The SESSION object name is the fully-qualified filename of the port through which the application accesses the terminal. It has the following syntax: \node1.$process2.#subdevice \node1 is a node name commencing with a backslash followed by one alphabetic character and up to six alphanumeric characters. $process2 is a process name commencing with a dollar sign followed by one alphabetic character and and up to six alphanumeric characters.
Objects for SNAX Creator-2 SU Object Type Object Name Format The SU object name has the following syntax: \node1.$process1.#subdevice Note When you use an SU object name in an SCF command, you can omit \node1 and the period following it if the SU object resides on the same node as the SNAX Creator-2 subsystem. \node1 is a node name commencing with a backslash followed by up to seven alphanumeric characters. The first character must be alphabetic, and the remaining characters must be alphanumeric.
Objects for SNAX Creator-2 SUBSYS Object Type Commands The following commands can be applied to the SU object type: ADD ALTER DELETE INFO NAMES START STATUS STOP SUBSYS Object Type The SUBSYS object type defines a SNAX Creator-2 subsystem. It is created and named when the SNAX Creator-2 subsystem is started (see the RUN CREOBJ command in Section 2, “Startup and Configuration of SNAX Creator-2”). You can use it to modify or inquire about operational aspects of a SNAX Creator-2 subsystem.
Objects for SNAX Creator-2 SUBSYS Object Type Commands The following commands can be applied to the SUBSYS object type: ALTER DELETE (valid only when the SUB parameter is used) INFO LISTOPENS NAMES PRIMARY START (valid only when the SUB parameter is used) STATS STATUS STOP (valid only when the SUB parameter is used) VERSION 117143 SNAX Creator-2 Configuration and Control Manual 3–11
Objects for SNAX Creator-2 Complex Naming Example Complex Naming Figure 3-2 shows a distributed configuration with two SNAX Creator-2 subsystems. Example Figure 3-2. Distributed Configuration System \A System \B SCF SCF Operator $CRE1 Connection named \C.$SSCP.#CRE-\A.$CRE1 $CRE2 System \C Connection named \C.$SSCP.#CRE-\B.$CRE2 $SSCP SU named \C.$SSCP.
Objects for SNAX Creator-2 Complex Naming Example The SCF operator at node \A can interrogate or modify the configuration database on node \D through either of the SNAX Creator-2 subsystems, $CRE1 on node \A or $CRE2 on node \B. SCF commands are simply issued with the appropriate manager name. Note that only one of the two SNAX Creator-2 subsystems succeeds in connecting with $SSCP at any given time. This is because the creator port of the SSCP only allows one opener.
Objects for SNAX Creator-2 Complex Naming Example (This page left intentionally blank) 3–14 117143 SNAX Creator-2 Configuration and Control Manual
4 SCF Commands for SNAX Creator-2 This section describes the SCF commands that apply to the SNAX Creator-2 subsystem. It provides general information about these commands, followed by descriptions of each command, including command syntax and examples. The commands are presented in alphabetical order. The commands presented in this manual are a subset of the total commands available through SCF.
SCF Commands for SNAX Creator-2 Command Overview Special Considerations for the ASSUME Command SCF requires designation of a manager name indicating the SNAX Creator-2 subsystem through which to operate. The ASSUME command can be used to specify the manager name for APPL, ENTRY, and SUBSYS objects. For example, the following two commands are equivalent: ADD APPL $CREA.
SCF Commands for SNAX Creator-2 Command Overview Commands and Object Types Table 4-2 lists the SCF commands for SNAX Creator-2 and the applicable object types for each. Table 4-2.
SCF Commands for SNAX Creator-2 Command Syntax Command Syntax This subsection describes the syntax of the SCF commands for SNAX Creator-2. It provides general information such as common syntax terms, followed by descriptions of each individual command. These descriptions are listed in alphabetical order. Common Command Syntax Terms Some syntax terms, such as manager-name and expression, are found in most syntax diagrams in this subsection. The following is a description of these terms.
SCF Commands for SNAX Creator-2 ADD APPL Command ADD APPL Command The ADD APPL command is used to define an APPL object to the SNAX Creator-2 subsystem. It is a sensitive command. ADD APPL command syntax is as follows: ADD [ / OUT file-spec / ] APPL manager-name.
SCF Commands for SNAX Creator-2 ADD APPL Command object-name is an APPL object name, as described in Section 3, “Objects for SNAX Creator-2.” general-attribute-spec is a list of attributes, with the values to be assigned to them, that can apply regardless of the method selected at logon. pathway-attribute-spec is a list of attributes, with the values to be assigned to them, that are used only if the value of the attribute METHOD at logon is PATHWAY. Otherwise, these attributes are ignored.
SCF Commands for SNAX Creator-2 ADD APPL Command The following example defines a TACL application MYTACL: ADD APPL $CREA.C-MYTACL, METHOD TACL, CPUS "0 1 2 3" The next example uses built-in functions and user data to determine the attribute values: ADD APPL $CREA.
SCF Commands for SNAX Creator-2 ADD ENTRY Command ADD ENTRY Command The ADD ENTRY command is used to define ENTRY objects to the SNAX Creator-2 subsystem. It is a sensitive command. ADD ENTRY command syntax is as follows: ADD [ /OUT file-spec/ ] ENTRY manager-name.object-name , TEXT { text-string | expression } OUT causes any SCF output generated for this command to be directed to the file file-spec; it is described in the Subsystem Control Facility (SCF) Reference Manual.
SCF Commands for SNAX Creator-2 ADD SU Command ADD SU Command The ADD SU command is used to define an SU object to the SNAX Creator-2 subsystem. It is a sensitive command. ADD SU command syntax is as follows: ADD [ / OUT file-spec / ] SU manager-name.
SCF Commands for SNAX Creator-2 ADD SU Command Examples In the following example, the NAMERULE attribute has the value PLUNAMEONLY: ADD SU $CREA.$SSCP.#APPL1, NAMERULE PLUNAMEONLY If a request arrives with the PLU name MAIL, and the first word (where the first word is the first character string up to the first blank) in the user data is PATHWAY, the APPL name searched for is C-MAIL. In the following example, the NAMERULE attribute has the value FIRSTWORD: ADD SU $CREA.$SSCP.
SCF Commands for SNAX Creator-2 ALTER APPL Command ALTER APPL The ALTER APPL command changes the values of specified attributes of an existing Command APPL object defined to the SNAX Creator-2 subsystem. It is a sensitive command. ALTER APPL command syntax is as follows: ALTER [ / OUT file-spec / ] APPL manager-name.
SCF Commands for SNAX Creator-2 ALTER APPL Command object-name is an APPL object name, as described in Section 3, “Objects for SNAX Creator-2.” general-attribute-spec is a list of attributes, with the new values to be assigned to them, that can apply regardless of the method selected at logon. pathway-attribute-spec is a list of attributes, with the new values to be assigned to them, that are used only if the value of the attribute METHOD at logon is PATHWAY. Otherwise, these attributes are ignored.
SCF Commands for SNAX Creator-2 ALTER ENTRY Command ALTER ENTRY The ALTER ENTRY command changes specified values of an existing ENTRY object Command defined to the SNAX Creator-2 subsystem. It is a sensitive command. ALTER ENTRY command syntax is as follows: ALTER [ /OUT file-spec/ ] ENTRY manager-name.
SCF Commands for SNAX Creator-2 ALTER SU Command ALTER SU Command The ALTER SU command changes the values of specified attributes of an existing SU object defined to the SNAX Creator-2 subsystem. It is a sensitive command. ALTER SU command syntax is as follows: ALTER [ / OUT file-spec / ] SU manager-name.
SCF Commands for SNAX Creator-2 ALTER SUBSYS Command ALTER SUBSYS The ALTER SUBSYS command changes the values of specified attributes of a running Command SNAX Creator-2 subsystem. It is a sensitive command.
SCF Commands for SNAX Creator-2 ALTER SUBSYS Command to collect messages. See the LOG/LOGFILE startup parameter in Section 2, “Startup and Configuration of SNAX Creator-2,” for valid values and further information. MSG identifies the message template file that SNAX Creator-2 uses when writing messages to the logging file.
SCF Commands for SNAX Creator-2 DELETE Command DELETE Command The DELETE command removes objects from the subsystem. It is a sensitive command. DELETE command syntax is as follows: DELETE [ /OUT file-spec/ ] { { { { APPL ENTRY SU SUBSYS manager-name.object-name manager-name.object-name manager-name.
SCF Commands for SNAX Creator-2 DELETE Command Considerations An SU object must be in the STOPPED state before it can be deleted. Deleting the SU object eventually causes all the subordinate connections to be closed and deleted. DELETE SUBSYS is only valid when the SUB parameter is specified and identifies valid subordinate objects. For example: DELETE SU $CREA.* and DELETE SUBSYS $CREA, SUB SU are equivalent.
SCF Commands for SNAX Creator-2 INFO Command INFO Command The INFO command displays the current attribute settings for the specified object. It is a nonsensitive command. INFO command syntax is as follows: INFO [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name.
SCF Commands for SNAX Creator-2 INFO Command subtype is an object type subordinate to the object named in the command, as described in Section 3, “Objects for SNAX Creator-2.” Considerations For SNAX Creator-2, the DETAIL option can be specified for all object types. Asterisks (*) in the returned displays indicate information that can be altered for the object with the ALTER command. The INFO commands for the SNAX Creator-2 subsystem reflect only what was entered in the ADD or ALTER command.
SCF Commands for SNAX Creator-2 INFO APPL Command Displays INFO APPL Nondetailed Display You can use the INFO APPL command to request nondetailed information for a specified application or for all applications defined to the SNAX Creator-2 subsystem. This example shows the request for nondetailed information about all applications defined to the SNAX Creator-2 subsystem $CREA: INFO APPL $CREA.
SCF Commands for SNAX Creator-2 INFO APPL Command Displays INFO APPL Detailed Display You can use the INFO APPL command to request detailed information for a specified application or for all applications defined to the SNAX Creator-2 subsystem. This example shows the request for detailed information about a Pathway application named C-PATH defined to the SNAX Creator-2 subsystem $CREA: INFO APPL $CREA.C-PATH , DETAIL The following detailed display is returned: SNAX/CRE DETAILED INFO APPL: $CREA.
SCF Commands for SNAX Creator-2 INFO CONNECTION Command Displays INFO CONNECTION Display Suppose $CREA is the name of the SNAX Creator-2 subsystem. The following example shows the request for information about all connections serviced by $CREA: INFO CONNECTION $CREA.* The following display is returned: SNAX/CRE INFO CONNECTION: $CREA Connection Name -----------------------------------------------------------\NODE.$SSCP.#CREQ1-\NODE.$CREA \NODE.$SSCP.#CREQ2-\NODE.
SCF Commands for SNAX Creator-2 INFO ENTRY Command Displays INFO ENTRY Nondetailed Display This example shows the request for nondetailed information about all entries defined to a SNAX Creator-2 subsystem named $CREA: INFO ENTRY $CREA.* The following display is returned: SNAX/CRE INFO ENTRY: $CREA Entry Name *Text -----------------------------------------------------------MYPATH $P02 MYTACL SYSTEM \snax MYSERVER [#APPLFILE] [#OPENNAME] Entry Name shows the names of the table entries.
SCF Commands for SNAX Creator-2 INFO ENTRY Command Displays INFO ENTRY Detailed Display This example shows the request for detailed information about a table entry named MYPATH, which is defined to a SNAX Creator-2 subsystem named $CREA: INFO ENTRY $CRTR.MYPATH , DETAIL The following detailed display is returned: SNAX/CRE DETAILED INFO ENTRY: $CREA.MYPATH *Text............. $P02 Text shows the user-specified text string (displayed in its entirety).
SCF Commands for SNAX Creator-2 INFO SESSION Command Displays INFO SESSION Nondetailed Display This example shows the request for nondetailed information about all sessions defined to a SNAX Creator-2 subsystem named $CREA: INFO SESSION $CREA.* The following display is returned: SNAX/CRE INFO SESSION: $CREA OPEN Name Method Session Start Time -------------------------------------------------------------\NODE1.$NT21LN.#ZR00000 SERVER 26 Jan 1993, 7:17:59.886 \NODE1.$NT21LN.
SCF Commands for SNAX Creator-2 INFO SESSION Command Displays INFO SESSION Detailed Display This example shows the request for detailed information about all sessions defined to a SNAX Creator-2 subsystem named $CREA: INFO SESSION $CREA.* , DETAIL The following detailed display is returned: SNAX/CRE DETAILED INFO SESSION: $CREA.\NODE1.$NT21LN.#ZR00001 Method............ PATHWAY Appl Name......... Program Name...... PROG1 Service Requested. Pathmon Name...... \SNAX.$P02 Requester......... Printer Name......
SCF Commands for SNAX Creator-2 INFO SESSION Command Displays For SNAX/APN, this is the SNA LU name of the requesting terminal. For example, if the IBM system is a type 2.1 node consisting of a VTAM and an NCP, this name matches the LU name in the LU macro in the NCP definition. Service Requested is the name of the application requested by the new logon. For SNAX/XF, this is the PLUNAME value from the ESS table. For SNAX/APN, it is the logon APPLID value.
SCF Commands for SNAX Creator-2 INFO SU Command Displays INFO SU Nondetailed Display This example shows the request for nondetailed information about an SU named #CREQ1: INFO SU $CRTR.$SSCP.#CREQ1 The following display is returned: SNAX/CRE INFO SU: $CRTR SU Name *Pluname *Password *Namerule -------------------------------------------------------------$SSCP.#CREQ1 MYPLU ABCDEFGH FIRSTWORD SU Name is the name of the SU.
SCF Commands for SNAX Creator-2 INFO SU Command Displays INFO SU Detailed Display This example shows the request for detailed information about an SU named #CREQ1: INFO SU $CRTR.$SSCP.#CREQ1,DETAIL The following detailed display is returned: SNAX/CRE DETAILED INFO SU: $CRTR.$SSCP.#CREQ1 *Namerule...... FIRSTWORD *Password...... ABCDEFGH *Pluname....... MYPLU These display fields are described in Section 5, “Attributes and Built-in Functions for SNAX Creator-2.
SCF Commands for SNAX Creator-2 INFO SUBSYS Command Displays INFO SUBSYS Display The following example shows the request for information about the SNAX Creator-2 subsystem named $CRE1: INFO SUBSYS $CRE1 The following display is returned: SNAX/CRE INFO SUBSYS: $CRE1 Primary CPU................. *Backup CPU.................. Configuration File Name..... *EMS Collector............... *EMS Collector-1............. *EMS Collector-2............. *EMS Collector-3............. *LOG File Name...............
SCF Commands for SNAX Creator-2 INFO SUBSYS Command Displays EMS Collector-n displays the name of an alternate EMS collector process assigned for the collection of EMS events. The value of n can be 1, 2, or 3. LOG File Name displays the name of the device or file to which SNAX Creator-2 log output goes. MSG File Name displays the name of the message file being used by the SNAX Creator-2 subsystem.
SCF Commands for SNAX Creator-2 LISTOPENS SUBSYS Command LISTOPENS SUBSYS The LISTOPENS SUBSYS command displays a list of all file system OPEN calls that Command apply to the specified SNAX Creator-2 subsystem. LISTOPENS command syntax is as follows: LISTOPENS [ /OUT file-spec/ ] SUBSYS manager-name OUT causes any SCF output generated for this command to be directed to the file file-spec; it is described in the Subsystem Control Facility (SCF) Reference Manual.
SCF Commands for SNAX Creator-2 LISTOPENS SUBSYS Command LISTOPENS SUBSYS Display This example asks SCF to show all the OPEN requests that apply to the SNAX Creator-2 subsystem named $CREA: LISTOPENS SUBSYS $CREA The following display is returned: SNAX/CRE LISTOPENS SUBSYS: $CREA Open Name Opener PPID BPID PFN BFN ------------------------------------------------------#ZSPI \SNAX.$ZNET 2,101 N/A 7 N/A Open Name is the file name that was opened.
SCF Commands for SNAX Creator-2 NAMES Command NAMES Command The NAMES command displays the names of all objects with the specified object type. NAMES command syntax is as follows: NAMES [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name.
SCF Commands for SNAX Creator-2 NAMES Command Considerations The SUB and SEL parameters are allowed only for the SU and SUBSYS object types. For the SUBSYS object, SEL is meaningful only in conjunction with the SUB parameter.
SCF Commands for SNAX Creator-2 NAMES Command Displays NAMES Displays The following example shows the display returned in response to the NAMES command applied to APPL objects; similar displays occur for other objects. This example requests information about all APPL objects under the control of the SNAX Creator-2 subsystem named $CREA: NAMES APPL $CREA.* Note that the wild-card designator (*) is used in this command to designate the selection of all objects of the specified type.
SCF Commands for SNAX Creator-2 PRIMARY Command PRIMARY Command The PRIMARY command causes the primary and backup CPU to exchange roles. It is a sensitive command. PRIMARY command syntax is as follows: PRIMARY [ /OUT file-spec/ ] [ SUBSYS ] manager-name , cpu-number OUT causes any SCF output generated for this command to be directed to the file file-spec; it is described in the Subsystem Control Facility (SCF) Reference Manual. manager-name is described in Section 3, “Objects for SNAX Creator-2.
SCF Commands for SNAX Creator-2 START SU Command START SU Command The START SU command initiates the operation of an SU object. Successful completion of the START SU command indicates that connections to the access method are created, and that the SNAX Creator-2 subsystem is able to accept logon requests. The default state after an ADD command completes with a successful open is STARTED. START SU is a sensitive command. START SU command syntax is as follows: START [ /OUT file-spec/ ] SU manager-name.
SCF Commands for SNAX Creator-2 STATS SUBSYS Command STATS SUBSYS The STATS SUBSYS command displays statistical information for the SNAX Creator-2 Command subsystem. In addition, for each statistical counter returned, there is an associated timestamp returned, which indicates when the sample was taken. STATS SUBSYS is a sensitive command when used to reset statistics.
SCF Commands for SNAX Creator-2 STATS SUBSYS Command Display STATS SUBSYS Display This example shows the request for statistics on the SNAX Creator-2 subsystem named $CREA: STATS SUBSYS $CREA The following display is returned: SNAX/CRE STATS SUBSYS: $CREA Openers ----------------------------------------------------------Reset Time........ 26 Jan 1993, 9:29:14.565 Sample Time....... 26 Jan 1993, 9:13:20.191 Config Openers.... 17 Current Openers... 1 MAX Openers ......
SCF Commands for SNAX Creator-2 STATS SUBSYS Command Display Current Openers is the current number of OPEN requests to the SNAX Creator-2 subsystem. The current count must always be at least 1. MAX Openers is the maximum number of OPEN requests that have ever been issued to the SNAX Creator-2 subsystem. Config RCV Depth is the maximum depth the operating system allows the receive queue to reach. Current RCV Depth is the current number of unanswered requests on the receive queue.
SCF Commands for SNAX Creator-2 STATS SUBSYS Command Display MAX Allocated is the maximum memory amount (in bytes) that has been allocated for memory pool usage since the SNAX Creator-2 subsystem was started. Growth Count is the number of times the memory pool was enlarged due to storage pressure.
SCF Commands for SNAX Creator-2 STATUS Command STATUS Command The STATUS command returns the current states of the objects. STATUS command syntax is as follows: STATUS [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name.
SCF Commands for SNAX Creator-2 STATUS Command subtype is an object type subordinate to the object named in the command, as described in Section 3, “Objects for SNAX Creator-2.” There is no difference between nondetailed and detailed displays for the STATUS command except that the word DETAILED appears in the header line of the detailed display.
SCF Commands for SNAX Creator-2 STATUS APPL Command Displays STATUS APPL Display This example shows the request for information about the status of all APPL objects in the SNAX Creator-2 subsystem named $FLAU: STATUS APPL $FLAU.
SCF Commands for SNAX Creator-2 STATUS CONNECTION Command Displays STATUS CONNECTION Display This example shows the request for information about the status of all CONNECTION objects in the SNAX Creator-2 subsystem, which is named $CRE2: STATUS CONNECTION $CRE2.* The following display is returned: SNAX/CRE STATUS CONNECTION: $CRE2 Object Name Summary Last State Error -------------------------------------------------------------CONNECTION: \NODE.$SSCP.#CREQ1-\NODE.$CRE2 STARTED 0 CONNECTION: \NODE.$SSCP.
SCF Commands for SNAX Creator-2 STATUS ENTRY Command Displays STATUS ENTRY Display This example shows the request for information about the status of an ENTRY object named MYPATH in the SNAX Creator-2 subsystem named $CREA: STATUS ENTRY $CREA.MYPATH The following display is returned: SNAX/CRE STATUS ENTRY: $CREA Object Name Summary State Last Error -------------------------------------------------------------ENTRY: MYPATH STARTED Object is the object type ENTRY. Name shows the names of the ENTRY objects.
SCF Commands for SNAX Creator-2 STATUS SESSION Command Displays STATUS SESSION Display This example shows the request for and display of information about the status of all SESSION objects in the SNAX Creator-2 subsystem named $CREA. STATUS SESSION $CREA.* The following display is returned: SNAX/CRE STATUS SESSION: $CREA Object Name Summary State Last Error -------------------------------------------------------------SESSION: \NODE.$NT21LN.#ZR00000 STARTED SESSION: \NODE.$NT21LN.
SCF Commands for SNAX Creator-2 STATUS SU Command Displays STATUS SU Display This example shows the request for information about the status of the SU object named $SSCP.#CREQ1 in the SNAX Creator-2 subsystem named $NAME: STATUS SU $NAME.$SSCP.#CREQ1 The following display is returned: SNAX/CRE STATUS SU: $NAME Object Name Summary State Last Error -------------------------------------------------------------SU: $SSCP.#CREQ1 STOPPED Object is the object type SU. Name shows the names of the SU objects.
SCF Commands for SNAX Creator-2 STATUS SUBSYS Command Displays STATUS SUBSYS Display This example shows the request for information about the status of the SUBSYS object representing the SNAX Creator-2 subsystem name $ABCD: STATUS SUBSYS $ABCD.* The following display is returned: SNAX/CRE STATUS SUBSYS: $ABCD Name Takeover Count Backup state ------------------------------------------------$ABCD 0 STARTED Name is the name of the SUBSYS object (SNAX Creator-2 subsystem name).
SCF Commands for SNAX Creator-2 STOP SU Command STOP SU Command The STOP SU command terminates the activity of an SU object in an orderly manner. Upon completion of this command, the configured objects are in a STOPPED state. STOP SU is a sensitive command. STOP SU command syntax is as follows: STOP [ /OUT file-spec/ ] SU manager-name.
SCF Commands for SNAX Creator-2 VERSION Command VERSION Command The VERSION command displays the version of the SNAX Creator-2 subsystem. The VERSION command syntax is as follows: VERSION [ /OUT file-spec/ ] [ SUBSYS ] manager-name [ , DETAIL ] OUT causes any SCF output generated for this command to be directed to the file file-spec; it is described in the Subsystem Control Facility (SCF) Reference Manual. manager-name is described in Section 3, “Objects for SNAX Creator-2.
SCF Commands for SNAX Creator-2 VERSION Command Displays VERSION Nondetailed Display The following example requests the version of a SNAX Creator-2 subsystem in a nondetailed format: VERSION SUBSYS \NODE.$CREA The following display is returned: VERSION \NODE.$CREA : SNAX/CRE (T6918version date id) T6918 is the SNAX Creator-2 product number. version is the SNAX Creator-2 product version number. It consists of an alphabetic character followed by two numeric characters: for example, D10.
SCF Commands for SNAX Creator-2 VERSION Command Displays VERSION Detailed Display The following example requests detailed information about a SNAX Creator-2 version. VERSION SUBSYS \NODE.$CREA, DETAIL The following display is returned: Detailed VERSION \NODE.$CREA SYSTEM \NODE SNAX/CRE (T6918version date id) GUARDIAN - T9050- (id) SCF KERNEL - T9082 (date) (id) SNAXCRE PM - ( T6939version date id) T6918 is the SNAX Creator-2 product number. version is the product version number.
SCF Commands for SNAX Creator-2 VERSION Command Displays (This page left intentionally blank) 4–56 117143 SNAX Creator-2 Configuration and Control Manual
5 Attributes and Built-in Functions for SNAX Creator-2 This section provides a reference to the SCF attributes used in SCF commands to configure SNAX Creator-2 objects and built-in functions. Attributes The following table lists the attributes for SNAX Creator-2 objects (other than the SUBSYS object, which is primarily configured by the RUN CREOBJ command). Table 5-1.
Attributes and Built-in Functions for SNAX Creator-2 BACKUPCPU Filtering of Attribute Values Expressions Used As Attribute Values When a set of values is specified, the values must be separated by blanks and the entire set enclosed between double quotation marks (" "). SNAX Creator-2 filters out invalid values (where indicated) and randomly selects one of the remaining values. Attribute values can be specified as expressions containing literal characters, references to entries, and built-in functions.
Attributes and Built-in Functions for SNAX Creator-2 METHOD MAXARGS Default: Value: Object: None Non-negative integer APPL This attribute specifies the maximum number of comma-separated parameters that may be passed in the logon user data. It is valid for all METHOD values. This attribute is optional. There is no default value; if this attribute is omitted, no maximum limit on the number of parameters exists.
Attributes and Built-in Functions for SNAX Creator-2 MINARGS The following values are valid values for this attribute: Value Meaning PATHWAY The application is a Pathway application and causes a RUN PROGRAM command to be sent to the named PATHMON process. The request (and accompanying message) is forwarded to a server process. The application requested is a TACL process and causes the program $SYSTEM.SYSTEM.TACL to be initiated. If $SYSTEM.SYSTEM.TACL is not present, $SYSTEM.SYSnn.
Attributes and Built-in Functions for SNAX Creator-2 PRINTER in the access method configuration (for SNAX/XF and SNAX/APN, this is in the ADD APPL for the SNAX Creator-2 SU). This attribute is optional. PATHMON Default: Value: Object: None Set of process names (attribute values are filtered for running processes) APPL This attribute is used only if the METHOD attribute has the value PATHWAY. It specifies a set of PATHMON processes from which SNAX Creator-2 selects one.
Attributes and Built-in Functions for SNAX Creator-2 PROCESS This attribute is optional. If omitted, the printer (if any) in the PATHMON configuration is the default. PROCESS Default: Value: Object: None Set of process names (attribute values are filtered for running processes) APPL This attribute is used only if the METHOD attribute has the value PATHWAY. It specifies a set of intermediate processes from which SNAX Creator-2 selects one.
Attributes and Built-in Functions for SNAX Creator-2 Built-in Functions SERVER Default: Value: Object: None Set of process names (attribute values are filtered for being running processes) APPL This attribute is used only if the METHOD attribute has the value SERVER. It specifies a set of server processes from which SNAX Creator-2 selects one. This attribute is optional at configuration, but mandatory at logon.
Attributes and Built-in Functions for SNAX Creator-2 Built-in Functions configuration. For SNAX/APN, the APPLFILE attribute is in the ADD LU command for the SNAX/APN logon manager (TLOGMGR) LU. For SNAX/XF, the APPLFILE attribute is in the ADD APPL command (not to be confused with the ADD APPL command described elsewhere in this manual). [#CPUA] selects an operational CPU (0 through 15) on the system defined by [#SYSTEM].
Attributes and Built-in Functions for SNAX Creator-2 Built-in Functions 2. Takes as the first parameter the subsequent string up to the next comma or end of data (leading and trailing blanks are removed). 3. Takes as the next parameter the string from the next non-blank up to the next comma or end of data (leading and trailing blanks are removed). 4. Continues as in (3) until the end of the data. 5.
Attributes and Built-in Functions for SNAX Creator-2 Built-in Functions [#REPEAT prefix suffix-1 … suffix-n] returns a string of n words, each composed of the prefix followed by the appropriate suffix. For example: [#REPEAT $PWY 1 2 3] would return: $PWY1 $PWY2 $PWY3 [#REQUESTER] returns the SNA name of the requesting secondary logical unit (SLU). For SNAX/XF, the SLU name is not defined, so the LU name in the ADD LU command in the SNAX/XF configuration is used.
Appendix A SCF Command Syntax Summary for SNAX Creator-2 The following pages contain syntax diagrams for each of the SCF commands supported by the SNAX Creator-2 subsystem. For descriptions of these commands and their uses, see Section 4, “SCF Commands for SNAX Creator-2.” ADD [ / OUT file-spec / ] APPL manager-name.
SCF Command Syntax Summary for SNAX Creator-2 ADD [ / OUT file-spec / ] SU manager-name.object-name [ , NAMERULE { PLUNAMEONLY | FIRSTWORD | expression } ] [ , PASSWORD { password | expression } ] [ , PLUNAME { pluname | expression } ] ALTER [ / OUT file-spec / ] APPL manager-name.
SCF Command Syntax Summary for SNAX Creator-2 ALTER [ /OUT file-spec/ ] ENTRY manager-name.object-name , TEXT { text-string | expression } ALTER [ / OUT file-spec / ] SU manager-name.
SCF Command Syntax Summary for SNAX Creator-2 INFO [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name } } } } } } [ , DETAIL ] [ , SEL [ NOT ] state ] [ , SUB { ONLY | ALL | NONE| subtype } ] LISTOPENS [ /OUT file-spec/ ] SUBSYS manager-name NAMES [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.
SCF Command Syntax Summary for SNAX Creator-2 START [ /OUT file-spec/ ] SU manager-name.object-name [ , SEL [ NOT ] state ] STATS [ /OUT file-spec/ ] SUBSYS manager-name [ , RESET ] STATUS [ /OUT file-spec/ ] { { { { { { APPL CONNECTION ENTRY SESSION SU SUBSYS manager-name.object-name manager-name.object-name manager-name.object-name manager-name.object-name manager-name.
SCF Command Syntax Summary for SNAX Creator-2 (This page left intentionally blank) A–6 117143 SNAX Creator-2 Configuration and Control Manual
Appendix B SCF Error Messages for SNAX Creator-2 This appendix describes the various types of error messages you may encounter when using the SNAX Creator-2 subsystem. In particular, this appendix lists the error messages specific to SNAX Creator-2, describes the probable cause and effect of each error, and suggests an appropriate recovery action. Numbers inserted into the messages are shown in this appendix as n. SCF displays an error message when it cannot complete the requested action.
SCF Error Messages for SNAX Creator-2 SNAX Creator 2 Errors SNAX Creator-2 Errors The following errors can be produced by the SNAX Creator-2 SCF product module: Error 1 SU definition error: explanation explanation explains the reason for the failure when an SU attribute was evaluated. Cause. An error occurred when adding or altering an SU. Effect. The application fails to be started. Recovery. Check the configuration command entered (or the configuration file) to correct the problem attribute definition.
Appendix C Configuration Examples This section provides configuration examples using the SNAX Creator-2 built-in functions, entries, and user-supplied data. Built-in functions are described in Section 5, “Attributes and Built-in Functions for SNAX Creator-2.
Configuration Examples Generating SERVER and MESSAGE Values Using the [#num] Function This example shows how to derive values for the attributes PATHMON and PROGRAM from logon user data using the [#num] function. The application named mypath is configured as follows: ADD APPL , , , $CREA.C-mypath METHOD PATHWAY PATHMON [#1] PROGRAM [#2] If the user data is: $pmon, prog1 then the PATHMON attribute is assigned the value $pmon, and the PROGRAM attribute is assigned the value prog1.
Configuration Examples Generating SERVER and MESSAGE Values The application named myserv is configured as follows: ADD APPL , , , $CREA.C-myserv METHOD SERVER SERVER $serv1 MESSAGE "314159" The logon user data is ignored. Using the [#KEYWORD] Function This example shows how to derive values for the SERVER and MESSAGE attributes with the [#KEYWORD] built-in function. The [#KEYWORD] built-in function facilitates decoding of user data that is structured with keywords.
Configuration Examples Load-Balancing Pathway Applications The application named mail is configured as follows: ADD APPL , , , $CREA.C-mail METHOD SERVER SERVER $serv1 MESSAGE "[#1:3]" If the user data is: mydata1, mydata2, mydata3, mydata4 then the value of the MESSAGE attribute is: mydata1,mydata2,mydata3 Additional arguments, such as mydata4, are ignored.
Configuration Examples Generating METHOD Values To load-balance logon requests to the same application, the programs all point to the same application, as defined for example by the INITIAL sco3270 clause. Using Literal Values This example specifies literal values for the PATHMON and PROGRAM attributes. The SNAX Creator-2 application named mypath is configured to load balance consecutive requests as follows: ADD APPL , , , $CREA.
Configuration Examples Generating METHOD Values If the user data is: PATHWAY, $pmon, prog1 then the METHOD attribute is assigned the first parameter, PATHWAY. The PATHMON attribute is assigned the second parameter, $pmon. The PROGRAM attribute is assigned the third parameter, prog1. The remaining attributes (PRIMARYCPU, SERVER, and MESSAGE) have no relevance to a Pathway application and are ignored. If the user data is: SERVER, $serv1 then the METHOD attribute is assigned the first parameter, SERVER.
Appendix D Configuring SNAX Creator-2 With SNAX/APN This appendix assumes that you are familiar with the SNAX/APN extended logon facility (XLF) and Tandem Logon Manager for IBM Systems (ILOGMGR). The SNAX/APN Configuration and Control Manual and the Tandem Logon Manager for IBM Systems (ILOGMGR) Manual provide functional descriptions and detailed configuration information for those products. Users log onto an application from terminals controlled by VTAM in one of two ways: 1.
Configuring SNAX Creator-2 With SNAX/APN Table D-1 shows configuration details in the SNA subarea network. Naming correspondences are indicated by highlighting. Table D-1.
Configuring SNAX Creator-2 With SNAX/APN Table D-2. Configuration Details for the Tandem System Description SNAX/APN Configuration SNAX Creator-2 Configuration Connection between SNAX/XF and SNAX Creator-2 ADD APPL $SSCP.#create ,APPLTYPE LUNSCRE ADD SU $CREA.\node.$SSCP.#create Line to SNA subarea network. Local PU object added automatically. ADD LINE $SNAN1, … SNAX/APN logon manager (local LU object) ADD LU $SNAN1.
Configuring SNAX Creator-2 With SNAX/APN (This page left intentionally blank) D–4 117143 SNAX Creator-2 Configuration and Control Manual
Appendix E Configuring SNAX Creator-2 With SNAX/XF SNAX/XF configurations include SCF object definitions and enhanced system services (ESS) table entries (defined by the SNAX Utility). SNAX/XF users logon to an application by typing the name of an ESS table entry. If required, logon user data can be provided e specifying a CONCDATA value in the ESS table entry. SNAX/XF SCF objects and attributes are described in the SCF Reference Manual for SNAX/XF.
Configuring SNAX Creator-2 With SNAX/XF New SNAX/XF Configurations PLU Names Supplied by SNAX/XF In this example, no PLUNAME attributes are specified on the SU objects, so SNAX Creator-2 searches for an APPL name derived from the SNAX/XF PLU name. Description SNAX/XF Configuration SNAX Creator-2 Configuration Connection for Pathway application ADD APPL $SSCP.#cre1 ,APPLTYPE LUNSCRE ,PASSWORD abcdef ADD SU $CREA.\node.$SSCP.
Configuring SNAX Creator-2 With SNAX/XF New SNAX/XF Configurations PLU Names Supplied by SNAX Creator-2 This example achieves the same result as the previous example, but PLUNAME attributes are specified on the SU objects, so SNAX Creator-2 APPL names need not be coordinated with the SNAX/XF PLU names. Description SNAX/XF Configuration SNAX Creator-2 Configuration Connection for Pathway application ADD APPL $SSCP.#cre1 ,APPLTYPE LUNSCRE ,PASSWORD abcdef ADD SU $CREA.\node.$SSCP.
Configuring SNAX Creator-2 With SNAX/XF Migrating from the Old Creator Process Migrating from the Old This example shows how to migrate from the old Creator process (T6954) to SNAX Creator Process Creator-2 with no change to an existing SNAX/XF configuration. The example defines one application for each startup method: A Pathway application (with user logon mypath) A TACL process (with user logon mytacl) A server-started application (with user logon myprog).
Configuring SNAX Creator-2 With SNAX/XF Migrating from the Old Creator Process 4. For all other applications (neither Pathway nor TACL): The CONCDATA value may indicate TACL or APPLFILE, but the ESS table entry APPLFILE indicates it is not really a TACL application. The SNAX Creator-2 METHOD is SERVER. The user must supply a server process to start the application. The server message typically includes the logon terminal name and application object file.
Configuring SNAX Creator-2 With SNAX/XF Migrating from the Old Creator Process Description SNAX/XF Configuration SNAX Creator-2 Configuration Connection shared by all applications ADD APPL $SSCP.#cre ,APPLTYPE LUNSCRE ,PASSWORD abcdef ADD SU $CREA.\node.$SSCP.#cre ,NAMERULE FIRSTWORD ,PASSWORD abcdef Pathway application; user types mypath ADD ESSCMD mypath ,CMDTYPE LOGON-CHAR ,PLUNAME #myplu1 ,PROTOCOL CRT ,CONCDATA(PATHWAY NAME $pmon, PROGRAM prog) ADD APPL $CREA.
Glossary This glossary defines terms used in this manual. Several definitions are taken from the IBM Dictionary of Computing and the IBM Network Program Products: General Information. Please refer to these IBM manuals for IBM terms not included in this glossary. access method. A generic term referring to the I/O process or communications subsystem that provides application access to a communications line. SNAX/XF and SNAX/APN are access methods. acquire.
Glossary command. A demand for action by a subsystem. A command is typically conveyed as an interprocess message from an application to a subsystem. configuration database. A file where information you enter through SCF is stored. This information includes object names, object states, and attributes. Each SNAX Creator-2 subsystem is associated with a specific configuration database. CONNECTION object type.
Glossary input sources. SCF accepts command input from a terminal or a disk file. The initial input source is determined by the form of the RUN command used to initiate SCF. At any time during an SCF session, the input source can be temporarily changed. line-handler process. A type of process in SNAX/XF or SNAX/APN that handles input and output across a communication line. logon manager. See Tandem Logon Manager for IBM Systems (ILOGMGR) and SNAX/APN logon manager (TLOGMGR). node.
Glossary sensitive command. A command that can be issued only by a user with super-group access, by the owner of the subsystem, or by a member of the group of the owner of the subsystem. SESSION object type. A SNAX Creator-2 object type that is used to record information about a session so that accounting information can be generated when the session is terminated. SESSION objects are nonconfigurable. SLU. See secondary logical unit. SNA. See Systems Network Architecture (SNA). SNAX /APN.
Glossary summary state. See object state. super group. The set of operating system users whose group ID is 255. User IDs within the super group confer implicit authorizations not available to other users, including the ability to execute sensitive Subsystem Control Facility (SCF) commands. system. A Tandem computer system, which consists of from 2 to 16 processors on a dual communication path (Dynabus interprocessor bus).
Glossary (This page left intentionally blank) Glossary–6 117143 SNAX Creator-2 Configuration and Control Manual
Index A Access methods 1-1 See also SNAX/XF, SNAX/APN ADD APPL command 2-1, 2-9, 2-13, 4-5/7 ADD ENTRY command 2-8, 2-13, 4-8 ADD SU command 2-7, 2-8, 2-13, 4-9/10 ALL keyword 1-6 ALTER APPL command 2-13, 4-11/12 ALTER ENTRY command 2-13, 4-13 ALTER SU command 2-13, 4-14 ALTER SUBSYS command 2-12, 2-13, 4-15/16 APPL object type 3-3/5 adding 2-9 attributes 2-10, 2-11, 3-5 BACKUPCPU attribute 2-10, 5-2 CPUS attribute 2-9, 5-2 INFO command display 4-21/22 MAXARGS attribute 2-9, 5-3 MESSAGE attribute 2-11, 5-3
Index Attributes 1-7, 5-1 See also individual attributes APPL object type 3-5 CONNECTION object type 3-6 ENTRY object type 2-8, 3-7 list of 5-1 SESSION object type 3-8 SU object type 2-7, 3-9 SUBSYS object type 3-10 Audit 1-3 B Backup CPU 2-13 Backup state, SUBSYS object type 4-51 BACKUPCPU attribute 5-2 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-10 BACKUPCPU startup parameter 2-3 BCPU attribute 4-15 ALTER SUBSYS command, in 4-15, A-3 in ALTER SUBSYS command, 12 Bu
Index Commands (continued) syntax summary A-1/5 table by object types 4-3 wild-card designators 3-2 Common errors B-1 CONFIG startup parameter 2-4 Configuration database 1-2, 1-3, 2-4, 4-31 adding APPL objects 2-9 adding ENTRY objects 2-8 adding SU objects 2-7 modifying 2-13 CONNECTION object type 3-5/6 attributes 3-6 INFO command display 4-23 NAMES command display 4-37 object name format 3-5 object states 3-6 STATUS command display 4-47 CPU backup 2-13 primary 2-13 CPUA built-in function 5-8 CPUB built-in
Index Display examples (continued) INFO command (continued) SESSION object type 4-26/27 SU object type 4-29/30 SUBSYS object type 4-31 LISTOPENS SUBSYS command 4-34 NAMES command 4-37 STATS SUBSYS command 4-41 STATUS command APPL object type 4-46 CONNECTION object type 4-47 ENTRY object type 4-48 SESSION object type 4-49 SU object type 4-50 SUBSYS object type 4-51 VERSION command 4-54/55 Displaying attribute values 2-15 object names 2-15 opens 2-15 statistics 2-15 version 2-15 Distributed Systems Managemen
Index ENTRY object type 3-6/7 attributes 3-7 expressions, used in 5-7 INFO command display 4-24/25 NAMES command display 4-37 object name format 3-7 object states 3-7 STATUS command display 4-48 TEXT attribute 2-8, 5-7 Error messages B-1 Errors common B-1 duplicate keyword B-2 invalid data B-2 SCF B-1 SNAX Creator-2 B-2 SU definition B-2 ESS table 5-10 Expressions 5-7/10 Extended logon facility (XLF) 1-1 F File code 1-3 FIRSTWORD, naming rule 2-8, 3-3, 5-4, 5-9 Format, SCF command 1-5 H Help, online 1-8 Hi
Index INFO command (continued) SESSION object type 4-26/27 SU object type 4-29/30 SUBSYS object type 4-31 Input sources 1-8 Invalid data error B-2 K KEYWORD built-in function 5-8, C-2, C-3 L LISTOPENS SUBSYS command 2-15, 4-33/34 display 4-34 Literal characters 5-7 Load-balancing configuration C-4 LOG attribute 4-15 ALTER SUBSYS command, in 4-15, A-3 in ALTER SUBSYS command 2-12 LOG or LOGFILE startup parameter 2-4 LOGFILE attribute 4-15 ALTER SUBSYS command, in 4-15, A-3 in ALTER SUBSYS command 2-12 M Man
Index MINARGS attribute 5-4 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-9 Modifying configuration database 2-13 Modifying SUBSYS 2-12 MSG attribute 4-16 ALTER SUBSYS command, in 4-15, A-3 in ALTER SUBSYS command 2-12 N NAME option, SNAX Creator-2 RUN command 2-2 NAMERULE attribute 3-3, 5-4, 5-9 ADD SU command, in 2-8, 4-9, A-2 ALTER SU command, in 4-14, A-3 in ADD SU command 2-7 NAMES command 2-15, 4-35/37 display 4-37 Names, displaying 2-15 Naming rule 2-8, 3-3, 5-
Index Object states 1-6, 1-7, 2-15, 3-3 See also individual object states APPL object type 3-4, 4-46, 4-47 CONNECTION object type 3-6 ENTRY object type 3-7, 4-48 SESSION object type 3-8, 4-49 SU object type 3-9, 4-50 SUBSYS object type 3-10 table by object type 3-3 Object types 1-5 APPL 3-3/5 CONNECTION 3-5/6 ENTRY 3-6/7 hierarchy 3-1 SESSION 3-7/8 SU 3-8/9 SUBSYS 3-10 table by commands 4-3 Objects 1-5 See also Object types, Object names, Object states Online help 1-8 ONLY keyword 1-6 Open square bracket,
Index PLU name 5-10 PLUNAME attribute 5-5 ADD SU command, in 4-9, A-2 ALTER SU command, in 4-14, A-3 in ADD SU command 2-7 PLUNAMEONLY, naming rule 2-8, 3-3, 5-4, 5-8 Plus sign (+), in INFO command display 4-20 PRIMARY command 2-13, 4-38 Primary CPU 2-13 PRIMARYCPU attribute 5-5 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-10 PRINTER attribute 5-5 ADD APPL command, in 2-11, 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-11 PROCESS attribute 5-6 ADD A
Index S SCF 1-2, 1-4 See Subsystem Control Facility (SCF) SCP 1-3 See Subsystem Control Point (SCP) Secondary logical unit 5-10 Security product module 1-3 sensitive commands 4-2 SEGVOL attribute 5-6 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-10 SEL parameter 1-6 Sensitive commands 1-4, 4-2 Server applications 3-3/5 SERVER attribute 5-7 ADD APPL command example C-2 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-11 Server-starte
Index SNAX/APN configuring for SNAX Creator-2 2-1, D-1 PLU name 5-5, 5-10 SLU name 5-10 using with SNAX Creator-2 1-1 SNAX/XF configuring for SNAX Creator-2 2-1, E-1 PLU name 5-5, 5-10 SLU name 5-10 using with SNAX Creator-2 1-1 Utility program 5-10 SNAXUTL program 5-10 SNAX Creator 5-4 SNAX Creator-2 1-1/3 errors B-2 SPI See Subsystem Programmatic Interface (SPI) Square brackets 5-7 START SU command 4-39 STARTED state 1-6 APPL object type 3-4 CONNECTION object type 3-6 ENTRY object type 3-7 SESSION object
Index States, summary See Object states Statistics, collection and display 4-40/43 See also STATS SUBSYS command Statistics, displaying 2-15 STATS SUBSYS command 2-15, 4-2, 4-40/43 display 4-41 STATUS command 2-15, 4-44/51 APPL object type 4-46 CONNECTION object type 4-47 ENTRY object type 4-48 SESSION object type 4-49 SU object type 4-50 SUBSYS object type 4-51 STOP SU command 4-52 STOPPED state 1-6 CONNECTION object type 3-6 SU object type 3-9 STOPPING state 1-6 CONNECTION object type 3-6 SESSION object
Index SUBSYS object (continued) parameters, startup (continued) CONFIG 2-4 SWAPVOL 2-5 SUBSYS object type 2-12, 3-10 attributes 3-10 backup state 4-51 BCPU attribute 4-15 COLLECTOR attribute 4-15 COLLECTOR-n attribute 4-15 EMS attribute 4-15 INFO command display 4-31 LOG attribute 4-15 LOGFILE attribute 4-15 MSG attribute 4-16 NAMES command display 4-37 object name format 3-10 object states 3-10 STATS display 4-41 STATUS command display 4-51 VERSION command display 4-54/55 Subsystem Control Facility (SCF)
Index SYSTEM attribute 5-7 ADD APPL command, in 4-5, A-1 ALTER APPL command, in 4-11, A-2 in ADD APPL command 2-9 SYSTEM built-in function 5-10 System environment 1-3 T TACL applications 2-9, 2-10, 3-3/5 Tandem Logon Manager for IBM Systems (ILOGMGR) 1-1 Tandem Nonstop system, compatibility with SNAX Creator-2 1-3 TERM option, SNAX Creator-2 RUN command 2-3 TEXT attribute 5-7 ADD ENTRY command, in 4-8 ALTER ENTRY command, in 4-13 in ADD ENTRY command 2-8 Tilde, ~ 5-7 TMF See Transaction Management Facility
Index Special characters #ZRnnnnn 5-9 $ZNET 1-3 *, asterisk INFO command display, in 4-20 wild-card designator 3-2 +, plus sign 4-20 -, dash 4-22 ?, question mark wild-card designator 3-2 [#APPLFILE] built-in function 5-7 [#CPUA] built-in function 5-8 [#CPUB] built-in function 5-8 [#KEYWORD] built-in function 5-8, C-2, C-3 [#num1:num2] built-in function 5-9, C-3 [#num] built-in function 5-8, C-2, C-3 [#OPENNAME] built-in function 5-9, C-4 [#REPEAT] built-in function 5-10 [#REQUESTER] built-in function 5-10
Index (This page left intentionally blank) Index–16 117143 Tandem Computers Incorporated
