SNAX/APC Configuration and Management Manual Abstract SNAX/APC provides LU type 6.2 support for the Tandem implementation of SNA. This manual describes how to install and configure SNAX/APC. Product Version SNAX/APC D41.00 Supported Releases This manual supports G06.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 123140 SNAX/APC D40 February 1997 134230 SNAX/APC F40 May 1997 134978 SNAX/APC D41 July 1997 136054 SNAX/APC D41 August 1997 138787 SNAX/APC D41 May 1998 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .
SNAX/APC Configuration and Management Manual Glossary Index Figures Tables What’s New in This Manual xvii Manual Information xvii New and Changed Information xvii About This Manual xxi xxi Who should Read This Manual How This Manual is Organized xxi Related Documentation xxii Your Comments Invited xxiv Notation Conventions xxvi Part I. SNAX/APC Planning and Configuration 1. Introduction LU 6.2 and SNAX/APC Concepts Parallel Sessions 1-1 1-4 LU 6.
2. Planning for SNAX/APC Contents 2. Planning for SNAX/APC LU 6.
. Trace Analysis Program Contents 4.
. Introduction to SCF for SNAX/APC Contents 5. Trace Analysis Program (continued) RANGE Command 5-7 RECORD Command SELECT Command TO Command 5-8 5-9 5-10 TRANSLATE Command 5-11 5-12 Using the Trace Analysis Program Using APCTAP Commands 5-13 Interpreting TRACE Entries 5-13 5-16 An Example Session with APCTAP Normal Version (Log Format) 5-17 Error Version (Trace Format) 5-21 Part II. SCF Reference for SNAX/APC 6.
. Objects for SNAX/APC Contents 7.
. SCF Commands for SNAX/APC Contents 8.
8. SCF Commands for SNAX/APC Contents 8.
A. Base and Option Sets Supported by SNAX/APC Contents 8.
B. SCF Command Syntax Summary for SNAX/APC Contents B.
B. SCF Command Syntax Summary for SNAX/APC Contents B.
C. SCF Error Messages for SNAX/APC Contents B. SCF Command Syntax Summary for SNAX/APC (continued) STOP LU Command B-12 STOP PTNR-LU Command B-12 STOP PTNR-MODE Command STOP SESSION Command STOP TPI Command STOP TPN Command B-13 B-13 B-13 B-13 TRACE Command B-13 TRACE LU Command B-13 TRACE PROCESS Command VERSION Command B-14 B-14 C.
C. SCF Error Messages for SNAX/APC Contents C.
D. Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Contents C. SCF Error Messages for SNAX/APC (continued) Error 00507 C-16 Error 00508 C-16 Error 00509 C-16 Error 00510 C-16 D. Comparison of LU 6.2 Control Operator Verbs and SNAX/APC E.
Glossary Contents E.
Tables Contents Figures (continued) Figure 6-1. SCF Overview 6-2 Figure 7-1. Object Type Hierarchical Relationships Figure 7-2. The CONV States Figure 7-3. The LU States Figure 7-4. The PROCESS States 7-13 Figure 7-5. The PTNR-LU States Figure 7-6. The PTNR-MODE States 7-16 Figure 7-7. The SESSION States 7-20 Figure 7-8. The TPN States Figure 7-9. The TPI States 7-22 Figure A-1. LU 6.2 Functions and Option Set Numbering 7-1 7-11 7-12 7-14 7-21 A-4 Tables Table 2-1.
Contents Tables (continued) Table D-3. Definition Verbs Versus SNAX/APC SCF Commands and Attributes D-2 Table E-1. Common Event Messages Table E-2.
What’s New in This Manual Manual Information SNAX/APC Configuration and Management Manual Abstract SNAX/APC provides LU type 6.2 support for the Tandem implementation of SNA. This manual describes how to install and configure SNAX/APC. Product Version SNAX/APC D41.00 Supported Releases This manual supports G06.00 and all subsequent releases until otherwise indicated in a new edition.
What’s New in This Manual New and Changed Information Because this new manual was created from earlier manuals, change bars are used to indicate technical material that has changed from the earlier manuals. The majority of the changed material documents the addition of sync point support. Technical changes have been made in the following areas: Section 2, Planning for SNAX/APC; a new subsection was added: Sync Point Support Considerations on page 2-13.
What’s New in This Manual New and Changed Information Appendix B, SCF Command Syntax Summary for SNAX/APC: Added the new LU attribute, LOCAL-LU-SYNC2-SUPPORT, to the subsections ADD LU Command on page B-2 and ALTER LU Command on page B-4. Appendix D, Comparison of LU 6.
What’s New in This Manual New and Changed Information SNAX/APC Configuration and Management Manual—138787 xxii
About This Manual Who should Read This Manual The SNAX/APC Planning and Configuration Manual is intended for system managers who will install and configure the SNAX Advanced Program Communication (SNAX/APC) subsystem. Personnel using this manual should preferably have an intermediate knowledge of SNA concepts (including LU 6.2 and Node Type 2.1), Tandem systems, and the Pathway transaction processing environment.
Related Documentation About This Manual Section 7, Objects for SNAX/APC, describes the SNAX/APC objects that can be managed using SCF. Section 8, SCF Commands for SNAX/APC, describes the SCF commands used for SNAX/APC and their attributes. Appendix A, Base and Option Sets Supported by SNAX/APC, presents lists of the LU 6.2 functions supported by SNAX/APC. Appendix B, SCF Command Syntax Summary for SNAX/APC, provides a summary of the syntax for the SCF commands used by SNAX/APC.
Availability Information in Tandem Manuals About This Manual SNAX/APN Manuals (D-series Software) • • • SNAX/APN Configuration and Control Manual SNAX/APN Management Programming Manual SCF Reference Manual for SNAX/APN SNAX/XF Manuals (D-series Software) • • • SNAX/XF Configuration and Control Manual SNAX/XF Management Programming Manual SCF Reference Manual for SNAX/XF Combined Manuals (G-series Software) • • SNAX/XF and SNAX/APN Configuration and Control Manual SCF Reference Manual for SNAX/XF a
IBM Manuals About This Manual • • • Availability Guide for Problem Management provides problem prevention, detection, and recovery information. This manual also contains information about automating problem detection and recovery tasks and provides an overview of Tandem’s problem management tools. Availability Practices Guide provides guidelines, procedures, and tips that can be used to improve the availability of NonStop systems or applications.
Notation Conventions About This Manual Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual.
General Syntax Notation About This Manual braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis.
Change Bar Notation About This Manual !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error ) ; !i !o !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
Change Bar Notation About This Manual SNAX/APC Configuration and Management Manual—138787 xxx
Part I. SNAX/APC Planning and Configuration Part I contains Sections 1 through 5 from the SNAX/APC Planning and Configuration Manual, P/N 136054, that is being replaced by this manual. These sections have been updated with information about the Tandem implementation of APPC sync point services. Appendix A from the SNAX/APC Planning and Configuration Manual, P/N 136054 was also updated with information about APPC sync point services and it is now Appendix A in this manual.
Part I.
1 Introduction SNAX/APC allows programs in a Tandem system to communicate with programs in an SNA network that support the logical unit session type 6.2 protocol (LU 6.2). SNAX/APC provides a connection between local transaction programs (TPs) and remote TPs—transaction programs running on other nodes in the network.
LU 6.2 and SNAX/APC Concepts Introduction Figure 1-1. Layers of SNA For LU 6.2 The Upper Layer Transaction Services Presentation Services Half-Session Protocol Machines Path Control Network Data Flow Control Data Flow Control Data Flow Control Transmission Control Transmission Control Transmission Control Path Control Data Link Control Physical Control CDT 001.CDD The transaction services layer includes specifications for special programs considered to be part of the LU.
LU 6.2 and SNAX/APC Concepts Introduction Rather than establish one LU-LU session between each pair of TPs that need to communicate, LU 6.2 creates an LU-LU session between two systems and then treats the LU-LU session as a serially reusable resource—the session may be used by any number of TP pairs, one after the other. This LU-LU session is available to all TPs on the two systems. When two TPs communicate through this shared LU-LU session, the communication is called a conversation (see Figure 1-2).
Parallel Sessions Introduction Figure 1-3. Single, Multiple, and Parallel Sessions Single Session LU LU LU Multiple Sessions LU LU Parallel Sessions LU LU CDT 003.CDD Parallel Sessions Parallel sessions allow two or more sessions with the same partner LU at the same time. This is useful for LU pairs that experience high traffic.
LU 6.2 Verb Categories Introduction Figure 1-4 shows an example of seven parallel sessions between LU1 and LU2. These sessions are grouped into two different modes. Sessions within a mode share similar transmission characteristics. Parallel-session support implies a mechanism for regulating the number of sessions between the partner LUs for each mode. This is known as change number of sessions (CNOS), a service provided by a set of control operator verbs.
LU 6.2 Verb Categories Introduction Conversational Verbs The following types of conversational verbs have been defined for LU 6.2 and are supported by SNAX/APC. All conversational verbs are fully documented in Section 2 of the SNAX/APC Application Programming Manual. • • Basic conversation verbs are intended for use by service transaction programs, performing end-user services such as CNOS actions.
Communication With SNAX/APC Introduction Communication With SNAX/APC TPs communicate with the SNAX/APC system through the Tandem file system by using a message-oriented application program interface. The basic unit of communication is an interprocess communication, or IPC, message. IPC messages contain Units of Work (UOWs), which are defined in the SNAX/APC Application Programming Manual. The TP sends information to SNAX/APC in an IPC message, and SNAX/APC returns information in a reply.
The SNAX/APC Process Introduction D-series or G-series environment. The D-series or G-series environment uses high PINs (process identification numbers). The SNAX/APC process (APCOBJ) can open processes that run at high PINs and accepts requesters that are running at either high or low PINs. The SNAX/APC Dispatcher and SNAX/APC Application Prototype Simulator (APS) System do not support high PINs.
Introduction 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).
Transaction Programs Introduction Transaction Programs SNAX/APC exists to allow user-written transaction programs (TPs) to communicate with other TPs in the SNA network. A transaction is either a part or the entirety of a business function. A typical example of a transaction is the transfer of money from one bank account to another. Such a program can be written in any language and on a wide variety of computer systems.
High Pin Support by SNAX/APC Introduction 2. Use the SHOW command to display the value of the HIGHPIN flag. @show set highpin from apcobj HIGHPIN ON 3. Use the CHANGE command to change the value of the HIGHPIN flag. @change highpin off in abcobj 4. Use the SHOW command to check your changes. @show set highpin from apcobj HIGHPIN OFF 5. Exit BINDER by entering the EXIT command.
Introduction High Pin Support by SNAX/APC SNAX/APC Configuration and Management Manual—138787 1- 12
2 Planning for SNAX/APC This section provides instructions on how to plan the use and configuration of SNAX/APC. Actual configuration examples are given in Section 4, Configuring Network Resources for SNAX/APC, of this manual. This section contains five main subsections: • • • • • LU 6.2 Data Structures. Before you can configure SNAX/APC, you must have an appreciation of how the structures and processes inside a type 6.2 LU work together to enable transaction program (TP) conversations.
Static Structures Planning for SNAX/APC LUs (represented by half-session processes), and active conversations (represented by conversation resources). Tandem has extended the capabilities of the data structures within the SNAX/APC implementation of APPC. Partner LUs and partner modes may optionally become dynamic structures created and configured on demand during a session, whereas the standard 6.2 implementation requires that they be configured before the sessions begin.
Dynamic Structures Planning for SNAX/APC Figure 2-1. Static Data Structures Local LU Information Partner LU 1 TPGM 1 Mode 1 TPGM 2 Mode 2 Partner LU 2 TPGM 3 Mode 1 Mode 2 TPGM 4 ••• ••• ••• Mode 3 CDT 007.CDD Dynamic Structures Figure 2-2 shows some of the relationships between data structures and processes in a dynamic environment. Transaction program instances (TPIs) represent transaction program (TP) processes.
Dynamic Structures Planning for SNAX/APC The resource control block (RCB) represents a conversation. The RCBs represent the connection of a TPI to a half session (HS). This connection is dynamically created and destroyed. The RCB identifies the local TPI and half session in conversation, as well as the remote LU and mode name (in case a conversation is allocated, but no session is immediately available). Half sessions contain instances of the data flow control and transmission control layers of SNA.
Tandem Access Method Configuration Planning for SNAX/APC Tandem Access Method Configuration Three SNA access methods may be used on the Tandem system: • • • SNAX/XF SNAX/APN SNAX/CDF Your choice of method(s) will be largely determined by the existing SNA network with which you want to connect. However, support for parallel sessions and full support for dynamic partner LU/mode configuration is limited to SNAX/APN configurations. SNAX/XF SNAX/XF is configured using the Subsystem Control Facility (SCF).
SNAX/CDF Configuration Planning for SNAX/APC • Remote PU objects. These represent adjacent nodes. At least one PU per line using type 2.1 capabilities is required. SNAX/CDF Configuration There are no added requirements for configuration in order to use SNAX/APC with SNAX/CDF. SNAX/CDF does not support parallel sessions. SNAX/CDF supports dynamic configuration of the partner LU and partner mode, but a line must be predefined to the remote PU. Note.
APPC/PC Configuration Planning for SNAX/APC TERMTYPE=LUTYPE62, NETNAME=luname, : CICS selects the session parameters based on the TERMTYPE parameter. Every mode name supplied when defining LU 6.2 links to CICS must be matched by a VTAM LOGMODE entry name. APPC/PC Configuration SNAX/APC can communicate with APPC/PC (LU 6.2 for the IBM Personal Computer). APPC/PC requires little configuration.
VTAM Definition Parameters Planning for SNAX/APC The following mode-entry source is acceptable for SNAX/APC to CICS. Default values are assumed for this entry. LOGMODE TABLE: MODEENT LOGMODE=cicslu62 MODEEND The mode name (cicslu62) is the mode name specified in the SNAX/APC configuration (MODE) and in the CICS terminal control table (MODNAME).
Conversation-Level Security Considerations Planning for SNAX/APC Notes. 1. The VTAM APPL (application definition) statement defines CICS to VTAM. The name field (CICS1) of the APPL statement is the uninterpreted VTAM LU name. It is unique within the domain. The ACBNAME (CICS) parameter is the network name. It is unique within the SNA network. This name combination allows users to log on to CICS and be connected to the copy of CICS in their domain, such as either CICS1 or CICS2. 2.
SNAX/APC Security Planning for SNAX/APC LUs to verify each other’s identity. LU-LU verification takes place when an LU-LU session is established. Conversation-Level Security The APPC architecture describes a large (and growing) number of options for conversation-level security. To simplify somewhat, the options can be classified into three groups: sending a user ID and password, receiving a user ID and password, and persistent verification.
SNAX/APC Security Planning for SNAX/APC Client Conversation-Level Security Client conversation-level security is implemented in the client transaction program. No configuration of SNAX/APC is required. Server Conversation-Level Security Server conversation-level security is implemented by three components: • • • The SNAX/APC process performs the LU 6.2 protocol functions on behalf of TPs. Security checking is controlled by the configuration of SNAX/APC and the security manager.
SNAX/APC Security Planning for SNAX/APC When the SCF TPN definition of a server TP includes the SECURITYREQUIRED attribute with the value USER, each and every remote client TP that will access that server must be defined as follows: • • In SNAX/APC, the SCF PTNR-LU definition for the client TP must include the LOCAL-LU-SECURITY-ACCEPTANCE attribute with a value of either CONV or ALREADYVERIFIED. In Safeguard, a user ID and password must be defined for the client TP using the SAFECOM command ADD USER.
Sync Point Support Considerations Planning for SNAX/APC Server Conversation-Level Security Test Failures All server conversation-level security checking occurs when an Attach request arrives from a remote LU and the Attach requires security checking. The result of the security checks is that the request is either honored or rejected. When the request is honored, a conversation is started with the requested server transaction program.
Planning for SNAX/APC SNAX/APC Verb Considerations for Sync Point Support SNAX/APC Configuration and Management Manual—138787 2- 14
3 Using SNAX/APC This section provides detailed instruction on how to install and run SNAX/APC. The following information is presented: • • • • The contents of the distribution tape How to edit the messages file The startup parameters for SNAX/APC Starting SNAX/APC, with or without PATHMON control If you want more specific information on SNAX/XF, see the SNAX/XF Configuration and Control Manual. If you want more specific information on SNAX/APN, see the SNAX/APN Configuration and Management Manual.
Installing SNAX/APC From the Distribution Subvolume Using SNAX/APC Table 3-1. Contents of Distribution Tape (page 2 of 2) File Name Description APCOBJ The SNAX/APC server main module. This is a multithreaded process that handles the processing of SNAX/APC verbs and the interface to the SNA access method. APCPCOD The SCREEN COBOL pseudocode for the program requesters using SNAX/APC. APCPDIR The SCREEN COBOL pseudocode directory for the APCPCOD file.
Editing the Messages File Using SNAX/APC Editing the Messages File The messages file, APCMSGS, contains records in numerous formats. Two types of entry records are of interest to users of SNAX/APC : K records and S records. An entry record begins as shown in Table 3-2: Table 3-2.
Configuration Parameters for SNAX/APC Using SNAX/APC S-Records (SNA Sense Codes) S-records provide the interpretation of SNA sense codes. Starting in column 7 is a numeric field terminated by a blank. This field is reserved. Following this field is the logging disposition as described above. If logging or EMS are enabled, the sending or receiving of a negative response will generate a log message and EMS event depending on the logging disposition of the SNA sense code carried in the negative response.
Configuration Parameters for SNAX/APC Using SNAX/APC The PARAMs for the SNAX/APC process are: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ BACKUPCPU ] number ] BACKUPDEBUG { TRUE | FALSE } ] CANCELSUPPORT { ON | OFF } ] CHARMAPFILE [ charactermap-file-name ] ] CHARMAPNAME mapname ] COLLECTOR [ collector-file-name ] ] COLLECTOR-1 [ collector-file-name-1 ] ] COLLECTOR-2 [ collector-file-name-2 ] ] COLLECTOR-3 [ collector-file-name-3 ] ] CONFIG configuration-file-name ] DATAPAGES number [ E | EXTENSI
Configuration Parameters for SNAX/APC Using SNAX/APC CANCELSUPPORT { ON | OFF } enables the handling of CANCEL system messages. CANCELSUPPORT ON specifies that SNAX/APC should process CANCEL system messages from application programs. CANCELSUPPORT OFF specifies that SNAX/APC should ignore CANCEL system messages from application programs. The manner in which SNAX/APC process CANCEL system messages varies according to the verb that SNAX/APC is processing when the CANCEL message arrives.
Configuration Parameters for SNAX/APC Using SNAX/APC COLLECTOR-2 [ collector-file-name-2 ] specifies the identity of alternate EMS collector number 2. If this parameter is omitted or used with no argument, output to this collector is suppressed. The COLLECTOR-2 value may be changed by specifying the COLLECTOR-2 parameter on the SCF or SPI ALTER PROCESS command. COLLECTOR-3 [ collector-file-name-3 ] specifies the identity of alternate EMS collector number 3.
Configuration Parameters for SNAX/APC Using SNAX/APC DEBUGONERROR { TRUE | FALSE } controls the action taken by the program when a fatal error is detected by explicit tests. This parameter is not intended for general use. If set to TRUE, then the DEBUG procedure will be called instead of ABEND. Care should be taken when using this feature, because a backup will not actually take over until the offending primary really exits. The default setting is FALSE.
Configuration Parameters for SNAX/APC Using SNAX/APC specifying an asterisk, output is sent to the default outfile, which is normally the home terminal. You are advised to use the EMS collectors, rather than the log file, to collect and examine event messages. Specifying the log file as a disk file presumes that the file already exists. The SNAX/APC process will not run if the specified disk file does not exist.
Configuration Parameters for SNAX/APC Using SNAX/APC values. If a MAXOUTRUSIZE value is not specified for an individual PTNRMODE object, it gets this value. If SNAX/APC is the primary LU, it sends this value in the BIND request. If SNAX/APC is the secondary LU, its BIND response returns the lesser of MAXOUTRUSIZE and the BIND RU size. If the BIND RU size is less than 16, SNAX/APC returns 16.
Configuration Parameters for SNAX/APC Using SNAX/APC The RMTATTACHTIMER value may be changed by specifying the REMOTEATTACHTIMER parameter on the SCF or SPI ALTER TPN command. SECURITYMANAGER { NONE | SAFEGUARD } specifies whether or not the Safeguard subsystem will be employed as the security manager. If SECURITYMANAGER is not specified, the default value is NONE. TRACEFILE trace-file-name designates the trace file and activates the trace collection. Here is an example of usage: PARAM TRACEFILE $QA3.
Starting SNAX/APC Using SNAX/APC 128 Trace the FSMs for the DFC (data flow control) layer. 64 Trace the FSMs for the TC (transmission control) layer. 32 Trace the SPI events. The SCF TRACE command may overwrite any setting established with this parameter. TRACEPAGES number specifies the maximum number of 2048-byte pages that the SNAX/APC process can use for tracing. When this data area is full, the server starts to overwrite data at the beginning of the data area.
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC prefix is a two-character string used to build process names and various file names. The first character must be alphabetic. option is one of the following terms: APC subvolume specifies the subvolume where the SNAX/APC object file APCOBJ resides. If this option is omitted, the list of subvolumes specified by the TACL built-in #PMSEARCHLIST is used. ATTRIB[UTE[S]] server-number / parm [,parm]...
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC generated by the SNAX/APC servers. To suppress events supply the value OFF (case insensitive). Note: If COLLECTOR is the last option you supply, then omitting a value is equivalent to OFF. CPU[S] server-number-cpu:cpu specifies the primary and backup CPUs for a SNAX/APC process pair. server-number can be set to ALL to designate all SNAX/APC processes, or it can specify a single SNAX/APC server by number.
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC of the corresponding object type are suppressed. The correlation of bit position and object type is shown in Table 3-4: Table 3-4. Bit Position and Object Type Bit Number Object Type Option Value 0 Reserved 1 LU %H4000 2 PTNR-LU %H2000 3 PTNR-MODE %H1000 4 SESSION %H0800 5 TPN %H0400 6 TPI %H0200 7 CONVERSATION %H0100 8 to 15 Reserved The default value is %H0300—suppress TPI and CONVERSATION events.
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC MODE objects may specify different values. If a MAXINRUSIZE value is not specified for an individual PTNR-MODE object, it gets this value. If SNAX/APC is the primary LU, it sends this value in the BIND request. If SNAX/APC is the secondary LU, its BIND response returns the lesser of MAXINRUSIZE and the BIND RU size. If the BIND RU size is less than 16, SNAX/APC returns 16.
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC PATHM[ON] subvolume specifies the subvolume on which the PATHMON program file resides. If this option is omitted, the list of subvolumes specified by the TACL built-in #PMSEARCHLIST is used. PATHMONCPU[S] cpu:cpu specifies the primary and backup CPUs where the PATHMON process will run. PATHT[CP2] subvolume specifies the subvolume on which the PATHTCP2 program file resides.
Using APCRUN to Set Up the PATHMON Environment Using SNAX/APC SWA[P] volume specifies the swap volume for the TCP. TRACE { ON | OFF } specifies whether or not the trace facility should start when the SNAX/APC servers are started. The default value is OFF, which specifies that the trace facility is not started when the SNAX/APC servers are started. TRACEO[PTION] number specifies the type of data to be captured by the trace facility.
Starting SNAX/APC Under Control of the PATHMON Process Using SNAX/APC Names Created by APCRUN APCRUN creates names for a number of processes and files based on the two-character string, prefix, that you specify in the APCRUN command, as shown below. In the templates given below, xx is the two-character string specified in prefix.
Running SNAX/APC Under TACL Using SNAX/APC Running SNAX/APC Under TACL To run SNAX/APC with TACL (that is, without the PATHMON process), you perform all the PARAM statements from TACL rather than from PATHCOM. You can edit the PATHCONF file included in the SNAX/APC distribution subvolume to execute the PARAM statements as a TACL macro. The RUN command options must include a process name (using the NAME option) and must specify NOWAIT.
4 Configuring Network Resources for SNAX/APC This section contains information on how to configure the network resources specifically used by SNAX/APC: • • • General Information, provides some orientation to the tasks of configuration. SCF Objects, contains introductory information about SCF objects. Static and Dynamic Configuration, discusses the difference between configuring partner LUs and Modes at start-up and configuring them (dynamically) after the SNAX/APC subsystem has been started.
Configuring Network Resources for SNAX/APC Your Level of Configuration Experience 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).
Configuring Network Resources for SNAX/APC Capacity Limits or RUN APCOBJ/NAME $AL01, NOWAIT, CPU 1/2, CONFIG & $QA3.APCCONF.AL01 Possible Timeout SNAX/APC will timeout any SCF command if SNAX/APC has not completed the process initialization. In such cases, a delay of 30 seconds before issuing SCF commands is recommended. See Running SNAX/APC Under TACL on page 3-20. Capacity Limits The following are the capacity limits for a new SNAX/APC process: • • • Maximum of 1024 sessions per local LU.
Configuring Network Resources for SNAX/APC SNAX/APC Object Types SNAX/APC Object Types The following object types are used by SNAX/APC. Note that not all of them are used during the configuration. PROCESS The PROCESS object type defines the SNAX/APC process. This object type enables the operator to control SNAX/APC and its subordinate objects. It is frequently used to obtain status information, using SCF commands such as INFO, TRACE, and STATUS.
Object Hierarchies Configuring Network Resources for SNAX/APC TPI This represents an instance of the transaction program. In the Tandem (local) LU, the TPI can be a Tandem process, or a thread within a Tandem process. On the Tandem side, a TPI object is created by a TP issuing a TP-READY service verb, and is deleted by a TP issuing a TP-END service verb, an ABORT/STOP command, or a file system CLOSE request. This object is not created at configuration time. An example object name would be $APC1.LU01.
Configuring Network Resources for SNAX/APC Static and Dynamic Configuration Hierarchies are useful for wild-card referencing; for example in SNAX/APC there may be multiple instances of a transaction program (the TPN object type) running simultaneously. In such a case, an object specification of the form TPN * can be used to refer to all current instances of the TPN. Similarly, as the full example at the end of this section shows, all LUs can be started with a START LU * command.
Configuring Network Resources for SNAX/APC Configuring a Server Mechanism SNAX/APC subsystem. You must also configure the local LU with DYNAMICSUPPORT YES, and either single or parallel session support. See Configuring a Server Mechanism on page 4-7 for further details. Configuring a Server Mechanism Dynamic SNAXFILENAME support allows a SNAX/APC process to receive unsolicited BINDs from unknown partner LUs via the SNAX Creator-2 process.
Configuring a Server Mechanism Configuring Network Resources for SNAX/APC Figure 4-2. Server Support Using SNAX Creator-2 $APC1 4 $APC1.#zcre,bind params,openname $LH2.#znnn $CREATOR-2 CINIT msg 3 open $LH2.#znnn 5 $SSCPn 2 $LH1 $LH2 1 $LH3 BIND msg $LH4 BIND (LUA) CDT 999.CDD A server mechanism must be considered at two levels, the lower level access method such as SNAX/APN, and the higher level API such as SNAX/APC.
Configuring Network Resources for SNAX/APC Configuring a Server Mechanism A primary consideration is the configuration of the remote LU. You might expect that the LU needs to be defined to both SNAX/APN and SNAX/APC, but this is now optional for both subsystems. At the SNAX/APN level the line handler can dynamically add that remote LU object, and will also delete it at the end of the session.
Configuring Network Resources for SNAX/APC Configuring a Server Mechanism Step Five: Upon receipt of this message, the SNAX/APC process first validates the local LU names and responds positively to the Creator-2 process (or rejects the message if the SLU (Local LU) name could not be found). Secondly, the SNAX/APC process adds the dynamic PTNR-LU object and a list of SNA-defined PTNR-MODE objects. The process is slightly different for single and parallel session LUs.
Configuring Network Resources for SNAX/APC Configuring a Local LU that support SNALUXS, which is the SNAX/APN interface used in this mode of operation. There is a slight difference in the mechanics of SNAX/APC and SNAX/HLS. SNAX/APC is the direct target of the SNAX Creator-2 with regard to passing the bindimage and openname. With the SNAX/HLS model, the SNAX Creator-2 will actually open and pass the openname to the application program that uses SNAX/HLS (Pathway) and that program will open SNAX/HLS.
Configuring Network Resources for SNAX/APC Configuring a Local LU The ADD LU command defines a local LU to a SNAX/APC process.
Configuring Network Resources for SNAX/APC Configuring a Local LU SNAXFILENAME access-method-file-name specifies the file name of the Tandem access method that this local LU uses to exchange information with an SNA network. Although SNAX/APC does not check for duplicate files, every local LU should have a distinct value for the SNAXFILENAME attribute, because SNAX/APC issues the OPEN request to the underlying access method exclusively.
Configuring Network Resources for SNAX/APC Configuring a Local LU (the default), the local LU is treated as a single-session LU (an LU that does not support parallel sessions). If the value of MAXSESSION is greater than 1, the local LU is treated as a parallel-session LU, and the TPN object named %06F1% and the PTNR-MODE object named SNASVCMG are added automatically. You can configure all 32 LUs to have MAXSESSION set to 1024, but no more than 1024 sessions are allowed to be active.
Configuring Network Resources for SNAX/APC Configuring a Local TP Name Examples The following is an example of configuring a local LU: -> ADD LU $APC1.LLU01, SNANAME TNDLU01, SNAXFILENAME & $nt21A.#LU101, MAXSESSION 255, AUTOSTART YES, & SNAXMAXRETRYCOUNT 20, SNAXRETRYTIMER 30000 The following shows the same example, using dynamic and sync point support: ADD LU $APC1.
Configuring Network Resources for SNAX/APC Configuring a Local TP Name The ADD TPN command defines a TP name to a local LU.
Configuring Network Resources for SNAX/APC Configuring a Local TP Name NO, the default value, specifies that the transaction program does not support the general TP-READY feature. For information about the general TP-READY feature, see the SNAX/APC Application Programming Manual. REMOTEATTACH { QUEUE | REJECT } QUEUE, the default value, specifies that the remote ATTACH requests designated to this transaction program are queued if there are no outstanding remote-attached TPREADY requests.
Configuring Network Resources for SNAX/APC Configuring a Local TP Name USER specifies an attach must supply a valid user ID and password pair or a valid user ID and the already-verified indicator before it can start a conversation with the transaction program. If the attach includes a user ID and the already-verified indicator, SNAX/APC verifies that the user ID exists locally before granting access to the transaction program. The default value is NONE.
Configuring a Mode Configuring Network Resources for SNAX/APC REPLYDELAYEDONERROR YES, CHARMAPPING YES CHARMAPNAME SPANISH, SECURITYREQUIRED USER & Another example, using minimal options, is as follows: -> ADD TPN LLU01.LTP01 -> ADD TPN LLU01.LTP02 Configuring a Mode A mode is a set of session characteristics that a group of sessions share for a particular partner LU.
Configuring Network Resources for SNAX/APC The ADD PTNR-MODE Command The ADD PTNR-MODE Command The ADD PTNR-MODE command defines a new (LU, Mode) entry to the SNAX/APC process.
Configuring Network Resources for SNAX/APC The ADD PTNR-MODE Command The default value for this attribute is equal to the MAXINRUSIZE attribute value specified in the process startup parameters. If MAXINRUSIZE is not specified, the default value is 256. DEFAULTMAXOUTRUSIZE number specifies the maximum size of normal flow request units (RUs) that the local LU can send over sessions started with this mode. Valid values are from 16 through 16,000.
Configuring Network Resources for SNAX/APC The ADD PTNR-MODE Command MAXAUTOACT attribute is greater than the value of the MINCONWINNER attribute after the CNOS command is negotiated, only the number of sessions specified by the MINCONWINNER attribute are pre-established. The valid range is from 0 through 1024, and the default value is 0. RCVWINDOW number specifies the number of request/response units (RUs) that SNAX/APC can receive from the partner LU at one time.
Configuring Network Resources for SNAX/APC Descriptions of the SNA-defined Modes LU is started, the DEFAULTMAXINRUSIZE and DEFAULTMAXOUTRUSIZE attributes are not validated against the underlying SNAX access method. However if the values of these attributes exceeds the upper limit of the underlying SNAX access method, the CurrentMaxInRUSize and CurrentMaxOutRUSize counters (as shown in the INFO PTNR-MODE detailed display) are set to the upper limit after the PTNR-MODE is started.
Configuring Network Resources for SNAX/APC Descriptions of the SNA-defined Modes SNASVCMG PTNR-MODE $...“SNASVCMG” is the object name of the SNASVCMG PTNR-MODE in a SNAX/APC subsystem. It is architected for the use of the CNOS operation, and has been implemented in SNAX/APC. Default PTNR-MODE $...“#DEFAULT” is the object name of the default PTNR-MODE in a SNAX/APC subsystem.
Configuring Network Resources for SNAX/APC Control and Management DEFAULTMAXOUTRUSIZE = process’ MAXOUTRUSIZE #BATCHSC PTNR-MODE $...“#BATCHSC” is the object name of the #BATCHSC PTNR-MODE in a SNAX/APC subsystem. It could be used by any Application Transaction Programs (ATP).
Configuring Network Resources for SNAX/APC Configuring a Partner LU defined PTNR-MODEs (#DEFAULT, #BATCH, #INTER, #BATCHSC, and #INTERSC), all attributes can be altered. ABORT/STOP Command This command does not apply to the SNASVCMG PTNR-MODE if the wild card is specified in the object name. SNASVCMG PTNR-MODE has to be explicitly specified in an ABORT/STOP command.
Configuring Network Resources for SNAX/APC Configuring a Partner LU A Single-Session LU Upon receipt of an unsolicited BIND request, a PTNR-LU and a PTNR-MODE objects will be added to the local LU with the following attribute values: PTNR-LU Object name = $..PLU-name SNANAME = fully qualified PLU name Peripheral-Node = NO Parallel-Session-LU = NO PTNR-MODE Object name = $...
Configuring Network Resources for SNAX/APC Configuring a Partner LU Immediately after these objects are added, the PTNR-LU and the default SNASVCMG PTNR-MODE will be brought up to the STARTED state, and the BIND request will be processed. The rest of the SNA-defined PTNR-MODEs will be brought up through subsequent CNOS operations. These dynamic objects will be brought down to the STOPPED state and removed from the local LU’s configuration after all of the subordinate sessions are terminated.
Configuring a Partner LU Configuring Network Resources for SNAX/APC LOCAL-LU-SECURITY-ACCEPTANCE { NONE | CONV | ALREADYVERIFIED } determines the values of the security support indicators (byte 23) in the BIND request (if SNAX/APC is the primary LU) or the BIND response (if SNAX/APC is the secondary LU). Setting this attribute to either CONV or ALREADYVERIFIED does not cause security to be enforced; it merely enables security information to be included in incoming attaches.
Complete Examples Configuring Network Resources for SNAX/APC Complete Examples These examples are annotated SCF command files built from examples shown in the previous subsections. Both examples assume that the underlying access methods are configured and started. The difference between the two examples is that the first is for a SNAX/APN environment and the second is for SNAX/XF or SNAX/CDF environments. These are loopback configurations with both local and remote LUs and TPs on the same Tandem system.
Configuring Network Resources for SNAX/APC SNAX/XF or SNAX/CDF Example ========================================================================= == Add local LU for remote node $APC2. The SNAXFILENAME names a == == second SNAX/APN line. The subdevice name must match SNANAME. == ========================================================================= add lu rlu01, snaname rlu01, snaxfilename $nt21b.
Configuring Network Resources for SNAX/APC SNAX/XF or SNAX/CDF Example ========================================================================= == Add a local LU for $APC1. SNAXFILENAME names a SNAX/XF or SNAX/CDF == == line. The subdevice has to match the SNANAME of this local LU. == ========================================================================= add lu llu01, snaname llu01, snaxfilename $line1.
Configuring Network Resources for SNAX/APC SNAX/XF or SNAX/CDF Example start lu * start lu *,sub ptnr-lu start lu *,sub tpn assume process $apc1 start lu *,sub all status lu $apc1.*,sub all status lu $apc2.
Configuring Network Resources for SNAX/APC SNAX/XF or SNAX/CDF Example SNAX/APC Configuration and Management Manual—138787 4- 34
5 Trace Analysis Program When attempting to solve problems in SNAX/APC communications, it is useful to be able to examine the information transmitted between TPs and SNAX/APC, and the information transmitted between SNAX/APC and SNAX/XF, SNAX/APN, or SNAX/CDF. The SNAX/APC Trace Analysis Program (APCTAP) is an interactive utility that allows you to examine information passed among the SNAX/APC components after this information has been captured in a trace file.
APCTAP Commands Trace Analysis Program APCTAP Commands The following pages describe the APCTAP commands. The syntax in the formatter was designed to be as brief as possible. You can omit spaces between a command verb and its parameter. However, if you do omit spaces, be aware that the commands TOFILEX and TO FILEX are not equivalent. The first sends trace output to a file named OFILEX; the second sends trace output to a file named FILEX. Table 5-1 lists the the APCTAP commands. Table 5-1.
COUNT Command Trace Analysis Program COUNT Command Use the COUNT command to display the number of records in a trace file. C[OUNT] DISPLAY Command Use the DISPLAY command to write general information about the trace input file to the trace output file. D[ISPLAY] { A[LL] } { option [ option ... ] } option is one of the following keywords: H[EADER] R[ANGE] S[ELECT] Considerations • • • • A[LL] displays the trace header, range, and select settings. H[EADER] displays the header information.
FROM Command Trace Analysis Program To enable FILTER, at least one of these six parameters has to be specified: LU filters only those records concerning a specific LU, which is represented by an LU ID. SESSION filters only those records associated with a session represented by a session ID. TPI filters only those records associated with a specific TPI represented by an TPI ID. CONV filters only those records concerning a specific conversation represented by a conversation ID.
GO Command Trace Analysis Program trace-file specifies the trace-file name. GO Command Use the GO command to create a trace output file based on the range, select, and translate criteria that are currently in effect. Refer to the FROM and TO command descriptions for information on trace input and output files. G[O] Considerations • • Only records meeting the criteria specified in the SELECT command are processed.
LENGTH Command Trace Analysis Program Example HTRACE produces the following sample output : DIN/BOUT TP READY -----------------======> B E G I N <------ <====== RECEIVE <====== REQUEST RQ DFC TP READY AND WAIT ======> RECEIVE AND WAIT TO SEND ======> SIG DR <====== REQUEST TO SEND RECEIVE AND WAIT ======> <====== RECEIVE AND WAIT CONFIRMED ======> +RP FMD <====== CONFIRMED RECEIVE AND WAIT ======> RQ FMH-5 BB OIC DR 00A3 ------> <------ +RP DFC SIG 00A3 ------> <------ <====== RECEIVE AND WAIT SE
NEXT Command Trace Analysis Program NEXT Command Use the NEXT command to format the next sequential trace record(s).
RECORD Command Trace Analysis Program Considerations • • • • APCTAP supports BREAK key handling to stop the display. If you specify a range that contains more information than your terminal can retain, pressing the BREAK key after a GO command stops the display. If you specify integer values, the end value must be greater than the begin value. When you first start the trace analysis program, the range is set to include all records.
SELECT Command Trace Analysis Program For example, given the following instance of the SELECT command >select data and the following sequence of record types 1 DATA 2 BIU 3 FSM 4 FSM 5 DATA the RECORD command will format records 1 and 5 because they are data types. SELECT Command Use the SELECT command to select the record types to be formatted (or displayed on a terminal). The defaults are BIU and DATA, which are the typical settings for application debugging.
TO Command Trace Analysis Program PROCESS displays data handled by selected internal procedures of SNAX/APC. Most application developers will only be interested in PROCESS records labeled CONFIG; that is, records that are processed while configuring SNAX/APC. Other PROCESS record types are for Tandem internal use. SPI consists of records associated with the SPI interface. QUEUE displays enqueuing and dequeuing of internal buffers. This record is for Tandem internal use.
TRANSLATE Command Trace Analysis Program TRANSLATE Command Use the TRANSLATE command to change the translate options for DATA and BIU records (those identified with the markers , , , and ). The default translation modes for DATA and BIU records are different. The translation mode for DATA records is ASCII; the translation mode for BIU records is EBCDIC. The formatter displays the translated text in the bracketed area to the right of the data.
Using the Trace Analysis Program Trace Analysis Program Using the Trace Analysis Program The header information at the top of the trace file provides information on the system and files used, and the selections such as range, filters and data types selected. In this particular example, all the defaults are in operation (all records are selected), the data types are BIU and DATA, and no filter is being used. APCTAP of System: \ABCD Process: $HI01 Trace Data File $FIELD.APCPSPF.
Using APCTAP Commands Trace Analysis Program Using APCTAP Commands You may reset the selections as desired. For example, the following commands first clear the select, and then reset SELECT to DATA only, and RANGE to records 326 through 385.
Interpreting TRACE Entries Trace Analysis Program DIN and DOUT Entries The following example illustrates a DIN entry. DOUT entries are similar to DIN entries, except they show the response IPC header in place of the request IPC header, and the reply UOW in place of the request UOW. 1 2 3 4 === =============== ================ ===================== ============= @mucb 849642 seq: 8 05/13/92 11:38:43.
Interpreting TRACE Entries Trace Analysis Program 7 Verb. Names the verb and shows the contents of the UOWs in the IPC message. If more than one UOW exists in the IPC message, you have to distinguish each one by looking for the “ST” UOW ID, followed by a verb request. The example shows a single SEND-DATA verb request (also identified by the %H03F0 in the second word of the entry). Figure 5-3 depicts the first 20 bytes of the UOW. The third word contains the length of data being sent (80 bytes, %H0050).
An Example Session with APCTAP Trace Analysis Program BIN and BOUT Entries BIU entries are similar to DATA entries. However, instead of showing the IPC and verbs, formatted BIU entries display the BIU that was transmitted to or received from SNAX/XF, SNAX/APN, or SNAX/CDF. The following example illustrates a BOUT entry: @mucb 849786 seq: 122 05/13/92 11:40:02.
Normal Version (Log Format) Trace Analysis Program Normal Version (Log Format) This version of the conversation (with no errors) is provided to help you follow the flow of information in a normal conversation between two TPs. The version with errors will contain more detailed information—interpretation of the actual trace. The Local TP The conversation is first shown from the point of view of the first speaker, the local TP.
Normal Version (Log Format) Trace Analysis Program • • Yes, the attach is local. No, the TP is not dispatched. All reply and return codes have the value zero (0), a normal completion. Because all the other verbs issued by this TP complete normally, those subsequent responses have been edited out from the rest of the example. 2 The TP uses the ALLOCATE verb to establish a conversation with the remote TP.
Normal Version (Log Format) Trace Analysis Program 6 The local TP issues the TP-END verb. The TP-END verb releases all resources allocated under one TP-READY, canceling the TP-READY. When a TP successfully issues a TP-READY request, it associates the TP with a SNAX/APC LU. A TP-END verb request breaks this association. The Remote TP The following example screen shows the conversation flow from the point of view of the remote TP.
Normal Version (Log Format) Trace Analysis Program 1 On this side, the conversation also starts with a TP-READY verb issued by the remote TP. Remember that the names local and remote are relative (within the context of verb parameters), for example, the local LU is the one that is local to this side of the conversation. The parameters of the verb indicate: • • • • The local LU name is lup01. The local TP name is progp01a001.
Error Version (Trace Format) Trace Analysis Program 6 The remote TP issues DEALLOCATE (LOCAL). This will release the local conversation resources such as the RCBs. The TP finally issues a TP-END to end the TP instance and the TCBs. Error Version (Trace Format) The same conversation takes place, but now an error has been inserted. The example uses the trace program to locate the source of the error.
Trace Analysis Program Error Version (Trace Format) The OPENER entry at the head of each trace identifies which process started the session. The protocol used is APPL, which indicates that a TP issued the OPEN request. ============================================================================== @mucb 850226 seq: 8 05/13/92 11:40:02.
Error Version (Trace Format) Trace Analysis Program The first DIN/DOUT pair shows the TP issuing a TP-READY request to SNAX/APC and the subsequent reply. ============================================================================== @mucb 849786 seq: 66 05/13/92 11:40:02.
Trace Analysis Program Error Version (Trace Format) The RH contains all zeros. The BIN/BOUT pair (above) represent handshaking between SNAX/APC and the SNA access method. These handshaking entries are not relevant to tracing TP problems, and so all subsequent entries like the one shown above have been edited out of the rest of the trace. ============================================================================== @mucb 849818 seq: 134 05/13/92 11:40:03.
Error Version (Trace Format) Trace Analysis Program In this DOUT, the TP is told that the ALLOCATE request has completed. ============================================================================== @mucb 849682 seq: 184 05/13/92 11:40:04.
Error Version (Trace Format) Trace Analysis Program In this DIN, the TP sends a CONFIRM request. ============================================================================== @mucb 849642 seq: 265 05/13/92 11:40:04.
Trace Analysis Program Error Version (Trace Format) 0864 tells us that this is a premature conversation termination. A definite response is requested. ============================================================================== @mucb 853774 seq: 375 05/13/92 11:40:08.
Trace Analysis Program Error Version (Trace Format) field to determine the reason for the deallocation—in this case, 00 indicates that the remote TP terminated the conversation. ============================================================================== @mucb 849818 seq: 433 05/13/92 11:40:08.
Error Version (Trace Format) Trace Analysis Program The DIN shows the local TP sending a DEALLOCATE (LOCAL) request to SNAX/APC. The DOUT shows the reply. ============================================================================== @mucb 849822 seq: 496 05/13/92 11:40:08.
Error Version (Trace Format) Trace Analysis Program The Remote TP So far, all we know is that the error occurred with the remote TP, which unexpectedly terminated the conversation. Now we will take a look at the trace of SNAX/APC and the remote TP to find out why the TP aborted. FMT> display all ============================================================================== seq: 5 05/13/92 11:40:02.57 type: OPEN ocb id: %H0008; protocol: APPL opener name: \ABCE2.
Error Version (Trace Format) Trace Analysis Program SNAX/APC sends a positive response. ============================================================================== @mucb 849342 seq: 58 05/13/92 11:40:03.
Trace Analysis Program Error Version (Trace Format) data has been sent as well as the header—there is a GDS variable with a length of 0010 and an ID of 12FF, for example.) ============================================================================== @mucb 849446 seq: 153 05/13/92 11:40:04.
Error Version (Trace Format) Trace Analysis Program The remote TP first issues a RECEIVE-AND-WAIT request. ============================================================================== @mucb 849426 seq: 215 05/13/92 11:40:05.
Trace Analysis Program Error Version (Trace Format) The remote TP, still in Receive state, should respond with another RECEIVE-ANDWAIT, but it sends a CONFIRMED verb instead. ============================================================================== @mucb 849370 seq: 262 05/13/92 11:40:05.
Trace Analysis Program Error Version (Trace Format) resources are already deallocated.” Note that in the trace, all the resource IDs, for example, have been set to zero. ============================================================================== @mucb 850194 seq: 322 05/13/92 11:40:05.
Trace Analysis Program Error Version (Trace Format) These sense data (SDI) and function management data (FMD) codes have already been covered in the discussion of the local TP and SNAX/APC trace, earlier in this section. ============================================================================== @mucb 849454 seq: 359 05/13/92 11:40:06.
Error Version (Trace Format) Trace Analysis Program The remote TP attempts to send a TP-END request but SNAX/APC no longer recognizes the existence of that TP. See the relevant information on the UOW detail code on the previous page. ============================================================================== seq: 372 05/13/92 11:40:06.75 type: CLOSE ocb id: %H0008; protocol: APPL opener name: \ABCD2.
Trace Analysis Program Error Version (Trace Format) SNAX/APC Configuration and Management Manual—138787 5- 38
Part II. SCF Reference for SNAX/APC Part II contains Sections 1 through 3 from the SCF Reference Manual for SNAX/APC, P/N 136055, that is being replaced by this manual. These sections have been renamed Sections 6 through 8 and have been updated with information about the Tandem implementation of APPC sync point services.
Part II.
6 Introduction to SCF for SNAX/APC This manual describes the subsystem-specific details for using the Subsystem Control Facility (SCF) interactive interface to configure and control the SNAX/APC (Advanced Program Communication) subsystem. SNAX/APC provides LU type 6.2 support for the Tandem implementation of SNA.
Subsystem Control Facility (SCF) Overview Introduction to SCF for SNAX/APC • Stop or abort LU, PTNR-LU, PTNR-MODE, SESSION, TPI, or TPN objects either in an orderly manner or abruptly, as needed Subsystem Control Facility (SCF) Overview The Subsystem Control Facility is used to configure, control, and collect information about Tandem data communications subsystems. This section gives an overview of SCF features and operation and of the objects on which SCF operates.
Introduction to SCF for SNAX/APC • • Subsystem Control Point (SCP) Subsystem environment, in which subsystems (such as SNAX/APC) and the objects they control are managed Management services, which are software products that support the programmatic interface between the two environments SCF is a DSM management tool in the operations environment. It is a unified command interface that simplifies the tasks of configuring, controlling, and collecting information about Tandem subsystems.
Introduction to SCF for SNAX/APC Sensitive and Nonsensitive Commands INFO command to display the current attribute values for objects, and the STATUS command to display the current dynamic status of objects. The ASSUME command defines a default object to be used when the object is omitted from an SCF command. The TRACE command traces the operation of an object. While being traced, the object continues normal operation, but it passes all message traffic to a trace procedure.
Introduction to SCF for SNAX/APC Objects If the command pertains to an object, it is followed immediately by the object type and the object name. For example, the following command aborts the LU object named LU01: ABORT LU $APC01.LU01 The following command aborts a partner LU named CICSLU62: ABORT PTNR-LU $APC01.LU01.CICSLU62 If additional information is required, the object name is followed by a comma and the parameters required to further specify the action to be taken.
Introduction to SCF for SNAX/APC Object States and the name of the partner LU itself. To illustrate, a PTNR-LU object might have the name $APC1.LU01.CICSLU62, where $APC1 is the name of the PROCESS object, LU01 is the name of the LU object, and CICSLU62 is the name of the PTNR-LU object There are many other object types and object names used in SCF. The objects relevant to this subsystem, and the hierarchical relationship that exists between SNAX/APC objects, are described later in this manual.
Introduction to SCF for SNAX/APC How SCF Works For more information about the operational states supported by SNAX/APC, see Object States in Section 7, Objects for SNAX/APC. How SCF Works For commands that relate only to the SCF session (such as VOLUME), SCF takes the appropriate action without communicating with SCP.
Introduction to SCF for SNAX/APC • Setting the Initial Input Source Noninteractive input usually appears in the form of a command (Obey) file. Command (Obey) files are usually EDIT files that contain a series of commands. For more information about interactive and noninteractive modes of operation, see the Subsystem Control Facility (SCF) Reference Manual. Setting the Initial Input Source To specify an initial input source for an SCF session, use the IN option of the RUN command.
Introduction to SCF for SNAX/APC Environmental Requirements To obtain information on the SNAX/APC syntax of object types and the commands that apply to them, you enter the following command: HELP SNAXAPC [ command ] [ object-type ] Environmental Requirements The current version of this product is compatible with the D-series operating system at version DXX and subsequent versions. The current version of this product is compatible with the G-series operating system at version G06 and subsequent versions.
Introduction to SCF for SNAX/APC Environmental Requirements SNAX/APC Configuration and Management Manual—138787 6- 10
7 Objects for SNAX/APC This section describes the types of SNAX/APC objects you can manage using the SCF interface to SNAX/APC, outlines, their hierarchical relationships to each other, and provides a detailed description of each object type and object state. SNAX/APC Object Type Hierarchy A hierarchical relationship exists among the object types in a SNAX/APC subsystem. All object types are subordinate to the SNAX/APC process.
Supported Naming Conventions for D-series or Gseries Systems Objects for SNAX/APC An object name is used whenever the object is referred to by SNAX/APC or other Tandem processes. The syntax for each SCF command, described in Section 8, SCF Commands for SNAX/APC, contains the variable object-spec, which represents the object specification. The value object-spec is a combination of the values object-type and object-name. Note.
The Null Object Type Objects for SNAX/APC Unless you fully understand the possible effects or you have a strong reason for doing so, do not use all six characters when naming processes. Refer to the Introduction to D-Series Systems for more information. The Null Object Type In SNAX/APC, the null object type is supported only for the NAMES and VERSION command; it has no hierarchical relationship to any of the other supported object types.
LU Object Objects for SNAX/APC entered and displayed as a four-digit hexadecimal string. It is not necessary to have the %H prefix for conv-id because it will always be a hexadecimal integer. Examples The following are valid object names for the CONV object: $APC1.LU01.ACCT.0012.003A $APC1.TDMLU001.%6441%.0045.004B LU Object The LU object type represents a local LU. An LU is the entry point through which a transaction program accesses the SNA network.
Naming Conventions Objects for SNAX/APC Naming Conventions The object name for the PROCESS object is $apc-process, and it has the following format: [ \node. ]$apc-process \node is the name of the Tandem node on which the SNAX/APC process resides. This node name is optional unless the SNAX/APC process resides on a different node from the SCF process. $apc-process is the name of the PROCESS object. It is the SNAX/APC process name.
PTNR-MODE Object Objects for SNAX/APC $apc-process is the name of the SNAX/APC process. local-lu is the name of the local LU. partner-lu is the name of the partner LU. The name may consist of one to eight characters, the first of which must be a letter. The name must be unique for a given local LU. Examples The following are valid object names for the PTNR-LU object: $APC1.LU01.CICSLU62 $APC1.TDMLU001.
SESSION Object Objects for SNAX/APC partner-mode is the name of the PTNR-MODE object. The name may consist of one to eight characters, the first of which must be a letter. The name must be unique for a given partner LU. SNASVCMG is a reserved word for the default PTNR-MODE object for change number of sessions (CNOS) operations. In the case of a request for parallel sessions SNAX/APC expects to receive this mode name first, before accepting any other mode names to establish session characteristics.
TPI Object Objects for SNAX/APC session-id is the name of the SESSION object. It is assigned by the SNAX/APC process and is the name that uniquely identifies a session. It is an unsigned integer and it is entered and displayed as a four-digit hexadecimal string. It is not necessary to have the %H prefix for session-id because it will always be a hexadecimal integer. Examples The following are valid object names for the SESSION object: $APC1.LU01.CICSLU62.LU62BIND.013A $APC1.TDMLU001.CICSLU62.LU62BIND.
TPN Object Objects for SNAX/APC Examples The following are valid object names for the TPI object: $APC1.LU01.ACCT.003A $APC1.TDMLU001.%6441%.0034 TPN Object The TPN object type describes a local transaction program name entry known to the SNAX/APC process. Naming Conventions The object name for the TPN object is tpn, and it has the following format: $apc-process.local-lu.tpn $apc-process is the name of the SNAX/APC process. local-lu is the name of the local LU. tpn is the name of the TPN object.
Object States Objects for SNAX/APC Object States Objects defined for SNAX/APC are always in one of several states. The state of an object at any given instant is important. Certain commands have no effect on an object when it is in some states, but can affect the same object when it is in a different state. For most objects, the state changes as commands are issued against the object.
LU States Objects for SNAX/APC 2. The CONV object enters the STARTED state if the ALLOCATE verb is successfully completed or if the remote ATTACH request is attached to the parent TPI object. 3. The CONV object enters the STOPPING state and is in the process of being deallocated when one of the following conditions is detected: • • • • A DEALLOCATE request is received from either the local or remote side A session outage is detected A protocol error is detected A CLOSE request is received 4.
LU States Objects for SNAX/APC access method, the object returns to the STARTING state until the open is successfully retried at which time the object enters the STARTED state. In either of these cases, the STARTING state is an error state. If any object sits in the STARTING state for very long, it is in a error condition. 5. The LU object enters the STOPPED state from the STARTING state or the STARTED state upon receipt of the ABORT or STOP command. 6.
PROCESS States Objects for SNAX/APC timer with the time delay specified in the SNAXRETRYTIMER attribute of the ADD LU command, and retries the OPEN request after the timer expires. The automatic retry continues until either the LU successfully reopens the underlying SNAX access method or the number of retries has reached the limit set by SNAXMAXRETRYCOUNT attribute of the ADD LU command.
PTNR-LU States Objects for SNAX/APC state. If the PTNR-LU object is created dynamically, it will be brought up already in the STARTED state. 2. If you created it, the PTNR-LU object enters the STARTED state upon receipt of the START PTNR-LU command if the local LU is in the STARTED state. The PTNRLU object enters the STARTING state upon receipt of the START PTNR-LU command if the local LU is in the STARTING state.
PTNR-MODE States Objects for SNAX/APC PTNR-MODE States The following describes the states of the PTNR-MODE object. 1. The PTNR-MODE object may be created in one of two ways. You can either create the PTNR-MODE object by using the ADD PTNR-MODE command, or allow it to be created dynamically. If you create the PTNR-MODE object it will be placed in the STOPPED state. The partner mode will only be started if CNOS information is properly exchanged. 2.
Considerations for Dynamically-Added and ParallelSession PTNR-MODE Objects Objects for SNAX/APC Figure 7-6.
Considerations for Dynamically-Added and ParallelSession PTNR-MODE Objects Objects for SNAX/APC In addition, a set of SNA-defined PTNR-MODEs will be added to the PTNR-LU. These objects are discussed in detail next. Immediately after these objects are added, the PTNR-LU and the default SNASVCMG PTNR-MODE will be brought up to the STARTED state, and the BIND request will be processed. The reset of the SNA-defined PTNR-MODEs will be brought up through the following subsequent CNOS operations.
Considerations for Dynamically-Added and ParallelSession PTNR-MODE Objects Objects for SNAX/APC Application Transaction Programs (ATP). It has the following default attribute values: MODENAME = “#BATCH” DEFAULTMAXSESSION = 8 DEFAULTMINCOWINNER = 4 DEFAULTMINCOLOSER = 4 MAXAUTOACT = 0 RCVWINDOW = 3 SENDWINDOW = 3 DEFAULTMAXINRUSIZE = process’ MAXINRUSIZE DEFAULTMAXOUTRUSIZE = process’ MAXOUTRUSIZE • #INTER PTNR-MODE $...
SESSION States Objects for SNAX/APC SNAX/APC subsystem. It could be used by any Application Transaction Programs (ATP). It has the following default attribute values: MODENAME = “#BATCHSC” DEFAULTMAXSESSION = 8 DEFAULTMINCOWINNER = 4 DEFAULTMINCOLOSER = 4 MAXAUTOACT = 0 RCVWINDOW = 3 SENDWINDOW = 3 DEFAULTMAXINRUSIZE = process’ MAXINRUSIZE DEFAULTMAXOUTRUSIZE = process’ MAXOUTRUSIZE • #INTERSC PTNR-MODE $...
TPN States Objects for SNAX/APC 2. If a negative BIND response, a STOP SESSION, or an ABORT SESSION command is received, the session ceases to exist. If the response to the BIND request is positive, the SESSION object enters the STARTED state. 3. If a local LU receives a BIND request from a partner LU, it will accept the BIND and start the session, bypassing the STARTING transitional state and directly entering the STARTED state. 4.
TPI States Objects for SNAX/APC 2. The TPN object enters the STARTED state when it receives a START TPN command if the local LU is in the STARTED state. The TPN object enters the STARTING state upon receipt of the START TPN command if the local LU is in the STARTING state. If the local LU is in the STARTING state, the TPN object remains in the STARTING state until the local LU has started, at which time the TPN enters the STARTED state. 3.
TPI States Objects for SNAX/APC 2. The TPI object enters the STARTED state if the ALLOCATE verb completes successfully or if the TPI receives a remote ATTACH request. 3. The conversation subordinate to the TPI object can be deallocated either locally or remotely, which returns the TPI object to the STARTING state. 4. When an ABORT TPI command, a STOP TPI command, a TP-END request, or a CLOSE request is received, the TPI object ceases to exist.
8 SCF Commands for SNAX/APC This section contains information about the operator commands that apply to the SNAX/APC subsystem. This section outlines the commands that are available, what the command functions are, and which object types apply for each command. The SNAX/APC subsystem commands are a subset of the commands available through the Subsystem Control Facility (SCF). Commands that are generally supported by SCF are documented in the Subsystem Control Facility (SCF) Reference Manual.
SCF Commands for SNAX/APC Using Wild-Card Characters Table 8-1. Command Overview (page 2 of 2) Command STOP† Action TRACE Defines and controls the trace environment of specified objects. VERSION Obtains version and other optional information about the SNAX/APC subsystem. Stops the operation of an object in an orderly manner. † Wild-card characters allowed (see the next subsection).
Command and Object Type Summary SCF Commands for SNAX/APC ASSUME INFO LISTOPENS NAMES STATS (without the RESET option) STATUS VERSION Command and Object Type Summary Table 8-2 lists the SNAX/APC operator commands and the object types that apply for each command. The table is followed by descriptions of each SNAX/APC command, listed alphabetically.
ABORT LU Command SCF Commands for SNAX/APC ABORT is a sensitive command.
ABORT PTNR-LU Command SCF Commands for SNAX/APC ABORT PTNR-LU Command The ABORT PTNR-LU command places the target PTNR-LU object in the STOPPED state. Considerations • • • After issuing an ABORT PTNR-LU command, the local LU can no longer initiate sessions with the target partner LU. Similarly, BIND requests sent from the target partner LU are rejected.
SCF Commands for SNAX/APC ABORT SESSION Command PTNR-MODEs (#DEFAULT, #BATCH, #INTER, #BATCHSC, and #INTERSC) if the command contains wild cards. Considerations • To abort the reserved PTNR-MODE object named SNASVCMG, specify the name SNASVCMG in the command line, as follows: -> ABORT PTNR-MODE SNASVCMG Specifying a wild-card character or the SUB parameter with this command-object pair has no effect on the reserved PTNR-MODE object named SNASVCMG.
SCF Commands for SNAX/APC • • ABORT TPI Command A SESSION object can be aborted while it is in the STARTING state. If all of a dynamic PTNR-LUs sessions are deactivated, the dynamic PTNR-LU and all of its subordinate PTNR-MODEs will be removed from the local LU. Examples -> ASSUME PROCESS $APC1 -> ABORT SESSION LU01.CICSLU62.LU62BIND.013A -> ASSUME PTNR-MODE $APC1.LU01.CICSLU62.LU62BIND -> ABORT SESSION 013A -> ABORT SESSION $APC1.LU01.CICSLU62.LU62BIND.
SCF Commands for SNAX/APC ADD Command Considerations • • • • The ABORT TPN command does not affect any of its subordinate conversations or transaction program instances. However, it prohibits new conversations or transaction program instances from starting. Therefore, the ABORT TPN command can be issued regardless of the current states of its subordinates.
ADD LU Command SCF Commands for SNAX/APC Object Specification The object specification for the SNAX/APC ADD command is: object-type object name representation LU PTNR-LU PTNR-MODE SESSION TPN local-lu partner-lu partner-mode session-id tpn Considerations • • • • • The fully qualified name assigned to the created object must be unique. If an attribute for a given object is not assigned a value in the ADD command, the attribute’s default value is used.
SCF Commands for SNAX/APC ADD LU Command LIKE local-lu2 identifies an existing local LU whose attribute values serve as the model for the values of the attributes of the local LU being created. SNANAME uninterpreted-lu-name specifies the name of the local LU as it is known by the partner system. It can be up to 17 characters, if entered in the form: [net-id.]local-LU-name where net-id is up to 8 characters long and local-LU-name is up to 8 characters long.
SCF Commands for SNAX/APC ADD LU Command If you are using the SNAX/XF access method, enter the name of the associated SNAX/XF LU. The name you specify must include the SNAX/XF device name. The form of the name must be: $snax/xf-name.#lu-name AUTOSTART { YES | NO } YES specifies that the local LU is started automatically during the SNAX/APC process initialization.
SCF Commands for SNAX/APC ADD LU Command The number can also be specified in the form of (HH:MM:SS.CC), where HH, MM, SS, and CC represent hours, minutes, seconds, and hundredths of a second respectively. In addition, both open and close parentheses are required. Note. If a small value is specified for SNAXRETRYTIMER and the underlying access method does not recover from its fault, SNAX/APC may enter a loop temporarily. This attribute is ignored if the value of SNAXMAXRETRYCOUNT is 0.
ADD PTNR-LU Command SCF Commands for SNAX/APC ADD PTNR-LU Command The ADD PTNR-LU command defines a partner LU to a local LU.
SCF Commands for SNAX/APC ADD PTNR-MODE Command CONV specifies the local LU accepts a user ID and password pair from the remote LU. The local LU does not accept the already-verified indicator. ALREADYVERIFIED specifies the local LU accepts either a user ID and password pair or a user ID and the already-verified indicator. The default value for this attribute is NONE. PARALLEL-SESSION-LU { YES | NO } specifies whether or not the partner LU supports parallel sessions.
SCF Commands for SNAX/APC ADD PTNR-MODE Command ADD PTNR-MODE Attributes The attribute specification for the PTNR-MODE object of the SNAX/APC ADD command consists of the following attribute name and value combinations: ADD [ PTNR-MODE partner-mode1 ] [ , LIKE partner-mode2 ] , attribute-spec where attribute-spec is: [ [ [ [ [ [ [ [ , , , , , , , , , MODENAME modename DEFAULTMAXINRUSIZE number ] DEFAULTMAXOUTRUSIZE number ] DEFAULTMAXSESSION number ] DEFAULTMINCONLOSER number ] DEFAULTMINCONWINNER numbe
SCF Commands for SNAX/APC ADD PTNR-MODE Command DEFAULTMAXOUTRUSIZE number specifies the maximum size of normal flow request units (RUs) that the local LU can send over sessions started with this mode. Valid values are from 16 through 16,000. Although 16,000 is the maximum value allowed by SNAX/APC, the actual maximum is 15,360. This is because SNAX/APC adjusts the value specified to the largest RU size defined by SNA that is less than or equal to the value specified by the DEFAULTMAXOUTRUSIZE attribute.
ADD PTNR-MODE Command SCF Commands for SNAX/APC RCVWINDOW number specifies the number of request/response units (RUs) that SNAX/APC can receive from the partner LU at one time. The partner LU will not send more RUs to SNAX/APC until SNAX/APC sends a pacing response indicating that it can receive another pacing window. The valid range is from 0 to 63, and the default value is 0 (which specifies that pacing is not used).
SCF Commands for SNAX/APC • ADD SESSION Command Since SNAX/APC is unable to find the upper limit of the underlying SNAX access method (such as SNAX/APN, SNAX/XF, or SNAX/CDF) of an LU until the LU is started, the DEFAULTMAXINRUSIZE and DEFAULTMAXOUTRUSIZE attributes are not validated against the underlying SNAX access method.
SCF Commands for SNAX/APC ADD TPN Command holder for the session ID. Once the session has been started, you can use the INFO, NAMES, or STATUS commands to determine the session ID that was assigned. Examples -> ASSUME PROCESS $APC1 -> ASSUME LU LU01 -> ADD SESSION CICSLU62.LU62BIND.* -> ASSUME PTNR-MODE $APC1.LU01.CICSLU62.LU62BIND -> ADD SESSION * -> ADD SESSION $APC1.LU01.CICSLU62.LU62BIND.* ADD TPN Command The ADD TPN command defines a transaction program by name to a local LU.
SCF Commands for SNAX/APC ADD TPN Command CHARMAPNAME [ mapname ] specifies the translation table which SNAX/APC will use to perform character translation for all mapped conversations subordinate to the target TPN. If this attribute is omitted, the character map name specified on process startup or through APCRUN is used. The CHARMAPNAME attribute can be present even if character translation is not enabled.
ADD TPN Command SCF Commands for SNAX/APC REPLYDELAYEDONERROR YES indicates that SNAX/APC will not reply to a waiting TP-READY verb until the LU is started or the maximum number of retries has been attempted, whichever comes first. REPLYDELAYEDONERROR NO indicates SNAX/APC replies to a waiting TP-READY verb immediately after the first attempt is made to open the SNAX access method. The default value is NO.
ALTER Command SCF Commands for SNAX/APC Examples -> ASSUME LU $APC1.LU01 -> ADD TPN ACCT, GENERALTPREADY NO, SESSIONCONTROL YES, & REMOTEATTACH REJECT, SECURITYREQUIRED USER -> ADD TPN $APC1.LU01.ACCT, GENERALTPREADY NO, & SESSIONCONTROL YES, REMOTEATTACH QUEUE, & REMOTEATTACHTIMER 43200000, SECURITYREQUIRED USER -> ASSUME LU $APC1.LU01 -> ADD TPN ACCT, SESSIONCONTROL YES, CHARMAPPING YES, & CHARMAPNAME UNITEDKINGDOM, REPLYDELAYEDONERROR YES -> ADD TPN $APC1.LU01.ACCT, CHARMAPPING YES -> ADD TPN $APC1.
SCF Commands for SNAX/APC ALTER LU Command You are limited in the number of attributes you may change when working with dynamic objects. See the individual ALTER commands. ALTER LU Command The ALTER LU command changes the attribute settings of the specified LU.
SCF Commands for SNAX/APC ALTER LU Command treated as a parallel-session LU and the TPN object named %06F1% and the PTNR-MODE object named SNASVCMG are added automatically. You can configure all 32 LUs to have MAXSESSION set to 1024, but no more than 1024 sessions are allowed to be active. SNANAME uninterpreted-lu-name specifies the name of the local LU as it is known by the partner system. It can be up to 17 characters, if entered in the form: [net-id.
SCF Commands for SNAX/APC ALTER LU Command If you are using the SNAX/XF access method, enter the name of the associated SNAX/XF LU. The name you specify must include the SNAX/XF device name. The form of the name must be: $snax/xf-name.#lu-name A null string (simply enter the attribute keyword without any value) can be specified to enable the dynamic SNAXFILENAME support. (DYNAMICSUPPORT must also be set to YES.
SCF Commands for SNAX/APC ALTER PROCESS Command Examples -> ASSUME LU $APC1.LU01 -> ABORT -> ALTER, SNAXFILENAME $NT21.#LUCICS, MAXSESSION 100 -> STOP LU $APC2.LU01 -> ALTER LU $APC2.LU01, MAXSESSION 100, AUTOSTART YES, & LOCAL-LU-SYNC2-SUPPORT SYNCPT -> ASSUME PROCESS $APC1 -> STOP LU LU03 -> ALTER LU LU03, SNAXMAXRETRYCOUNT 10, SNAXRETRYTIMER 6000 -> ASSUME LU $APC1.LU01 -> ABORT -> ALTER,SNAXFILENAME, DYNAMICSUPPORT YES (The last example specifies dynamic support and a dynamically-set SNAXFILENAME.
SCF Commands for SNAX/APC ALTER PROCESS Command BACKUPCPU { cpu-number | STOP } specifies whether a backup process is desired and on which CPU (by number) the backup process is to be running. If you do not want a backup process, specify STOP instead of a CPU number. BACKUPDEBUG { YES | NO } specifies whether the backup process enters the debug mode after it is created. This attribute is intended for use only by Tandem personnel during problem determination.
SCF Commands for SNAX/APC • • ALTER PTNR-LU Command A switch that was initiated by a file becoming inaccessible failed. The CONFIG attribute can be used to attempt another switch when the problems are resolved. If SNAX/APC is started with a temporary configuration file, the CONFIG attribute allows the temporary file to be switched to a permanent file. The file name must be local to the SNAX/APC process.
ALTER PTNR-LU Command SCF Commands for SNAX/APC None of a dynamically-added PTNR-LUs attributes may be changed. An object has to be in a STOPPED state before its attributes may be changed. To bring a dynamic PTNR-LU to a STOPPED state, all its subordinate sessions will be deactivated, and the dynamic PTNR-LU itself will then be deleted.
SCF Commands for SNAX/APC ALTER PTNR-MODE Command PERIPHERAL-NODE { YES | NO } specifies whether the partner LU resides on a peripheral node or a subarea node. YES specifies that the partner LU resides on a peripheral node. If the partner LU is not a parallel-session LU, the partner LU is also a secondary LU (SLU). NO specifies that the partner LU resides on a subarea node. If the partner LU is not a parallel-session LU, the partner LU is also a primary LU (PLU).
SCF Commands for SNAX/APC ALTER PTNR-MODE Command RESPONSIBLE attributes can be altered when the PTNR-MODE is in the STOPPED state.
SCF Commands for SNAX/APC ALTER PTNR-MODE Command The DEFAULTMAXINRUSIZE attribute cannot be specified with the ALTER PTNR-MODE command unless the PTNR-MODE object is in the STOPPED state. The default value for this attribute is equal to the MAXINRUSIZE attribute value specified in the startup of the process.
SCF Commands for SNAX/APC ALTER PTNR-MODE Command The DEFAULTMINCONWINNER attribute cannot be specified with the ALTER PTNR-MODE command unless the PTNR-MODE object is in the STOPPED state. MAXAUTOACT number specifies the number of contention-winner sessions that are activated automatically after the PTNR-MODE object is in the STARTED state. The valid range is from 0 to 1024.
SCF Commands for SNAX/APC ALTER PTNR-MODE Command If the local LU and partner LU are connected by parallel sessions, the default value for the MODENAME attribute is SNASVCMG. SNASVCMG is the SNA-defined mode name that is used for exchanging CNOS requests and replies. The value SNASVCMG is reserved for this use and cannot be entered as the modename. The MODENAME attribute cannot be specified with the ALTER PTNR-MODE command unless the PTNR-MODE object is in the STOPPED state.
SCF Commands for SNAX/APC ALTER TPN Command started, the DEFAULTMAXINRUSIZE and DEFAULTMAXOUTRUSIZE are not validated against the underlying SNAX access method. However if the values of these attributes exceeds the transfer count upper limit of the underlying SNAX access method, the CurrentMaxInRUSize and CurrentMaxOutRUSize counters (as shown in the INFO PTNR-MODE detailed display) are set to the upper limit after the PTNR-MODE is started.
SCF Commands for SNAX/APC ALTER TPN Command YES indicates that character translation will be performed. NO indicates that character translation will not be performed. The default value is NO CHARMAPNAME [ mapname ] alters the translation table which SNAX/APC will use to perform character translation for all mapped conversations subordinate to the target TPN. If this attribute is omitted, the character map name specified on process startup or through APCRUN is used.
SCF Commands for SNAX/APC ALTER TPN Command REPLYDELAYEDONERROR { YES | NO } alters whether SNAX/APC should wait until the maximum number of retries is reached before replying with an error to a TP-READY verb that is waiting for the LU to start. REPLYDELAYEDONERROR YES indicates that SNAX/APC will not reply to a waiting TP-READY verb until the LU is started or the maximum number of retries has been attempted, whichever comes first.
SCF Commands for SNAX/APC ASSUME Command Examples -> ASSUME TPN $APC1.LU01.ACCT -> ALTER, GENERALTPREADY NO, REMOTEATTACH REJECT, & SESSIONCONTROL NO, SECURITYREQUIRED USER -> ASSUME LU $APC1.LU01 -> ALTER TPN ACCT, GENERALTPREADY NO, REMOTEATTACH QUEUE, & REMOTEATTACHTIMER 43200000, SECURITYREQUIRED USER -> ASSUME PROCESS $APC1 -> ALTER TPN LU01.ACCT001, REPLYDELAYEDONERROR YES, & REMOTEATTACHTIMER (10:00) -> ASSUME LU $APC1.
ASSUME CONV Command SCF Commands for SNAX/APC Object Specification The object specification for the SNAX/APC ASSUME command is: object-type object name representation CONV LU PROCESS PTNR-LU PTNR-MODE SESSION TPI TPN conv-id local-lu apc-process partner-lu partner-mode session-id tpi tpn Considerations • • When an SCF session begins, the assumed object type is null. If the object type is omitted and an object name is specified, the default object type remains unchanged.
SCF Commands for SNAX/APC ASSUME PTNR-LU Command Example -> ASSUME PROCESS $APC1 ASSUME PTNR-LU Command The ASSUME PTNR-LU command sets the PTNR-LU object as the default object type for subsequent commands, and optionally, sets the default object name. Examples -> ASSUME PTNR-LU $APC1.LU01.CICSLU62 -> ASSUME PTNR-LU ASSUME PTNR-MODE Command The ASSUME PTNR-MODE command sets the PTNR-MODE object as the default object type for subsequent commands, and optionally, sets the default object name.
ASSUME TPN Command SCF Commands for SNAX/APC ASSUME TPN Command The ASSUME TPN command sets the TPN object as the default object type for subsequent commands, and optionally, sets the default object name. Examples -> ASSUME TPN -> ASSUME TPN LU01.ACCT DELETE Command The DELETE command removes objects that were added with the ADD command. However, the specified object can only be deleted when it is in the STOPPED state and all of its subordinate objects have been removed. DELETE is a sensitive command.
SCF Commands for SNAX/APC DELETE PTNR-LU Command Consideration The DELETE LU command is rejected if the LU has an active trace. Example -> ASSUME PROCESS $APC1 -> DELETE LU LU01 DELETE PTNR-LU Command The DELETE PTNR-LU command removes a partner LU from a local LU. You may not use this command with dynamically-added objects. Consideration The SUB parameter cannot be used with the DELETE PTNR-LU command-object pair when the MODENAME attribute of the subordinate PTNR-MODE has the value SNASVCMG.
SCF Commands for SNAX/APC DELETE TPN Command Examples -> ASSUME PTNR-LU $APC1.LU01.CICSLU62 -> DELETE PTNR-MODE LU62BIND -> ASSUME PTNR-MODE -> DELETE $APC1.LU01.CICSLU62.LU62BIND DELETE TPN Command The DELETE TPN command removes the target TPN object from a local LU. Consideration The reserved TPN object named %06F1% cannot be removed from a local LU with the SUB parameter. Commands attempting to do so are rejected. The TPN object named %06F1% is automatically removed when its parent LU is deleted.
INFO CONV Command SCF Commands for SNAX/APC Object Specification The object specification for the SNAX/APC INFO command is: object-type object name representation CONV LU PROCESS PTNR-LU PTNR-MODE SESSION TPI TPN conv-id local-lu apc-process partner-lu partner-mode session-id tpi tpn Considerations • The SUB parameter cannot be used with the INFO SESSION or INFO CONV command-object pairs. • Asterisks (*) in the returned displays denote attributes that can be altered with the ALTER command.
INFO CONV Command SCF Commands for SNAX/APC CONV Type displays the type of conversation - basic or mapped - that is allocated to start the transaction program. Sync Level indicates the supported synchronization level of the active conversation. This field contains None if a synchronization level is not supported, Confirm if the Confirm synchronization level is supported or Syncpt if the Syncpt synchronization level is supported.
SCF Commands for SNAX/APC INFO LU Command CharMap Note returns a description of the character translation table. It is obtained from the character map file and is present only if the default translation table for the SNAX/APC process is not the standard ASCII-to-EBCDIC translation. Session ID identifies the session on which this conversation is running. Sync Level indicates the supported synchronization level of the active conversation.
INFO LU Command SCF Commands for SNAX/APC SNAX FileName displays the file name of the Tandem access method that the local LU uses to exchange information with the SNA network. Max Sess displays the maximum number of sessions that the local LU can have. If the value of Max Sess is 1, the local LU is treated as a single-session LU. If the value of Max Sess is greater than 1, the local LU is treated as a parallel-session LU.
SCF Commands for SNAX/APC INFO LU Command MaxSession displays the maximum number of sessions that the local LU can have. If the value of MaxSession is 1, the local LU is treated as a single-session LU. If the value of MaxSession is greater than 1, the local LU is treated as a parallel-session LU. AutoStart YES indicates that the local LU is started automatically during the SNAX/APC process initialization.
SCF Commands for SNAX/APC INFO PROCESS Command INFO PROCESS Command The INFO PROCESS command displays the current attribute settings of the SNAX/APC process.
INFO PROCESS Command SCF Commands for SNAX/APC The following display is returned in response to this request: SNAX/APC DETAILED INFO PROCESS: $APC1 *Backup CPU ........ *Debug on Error .... MaxInRUSize ....... MaxApplIoSize ..... OneStepRead ....... SecurityManager.... 12 OFF 256 4096 ON SAFEGUARD *EMS Collector ........... *EMS Collector 1 ......... *EMS Collector 2 ......... *EMS Collector 3 ......... *Message File ............ Message File Last Modif . *Log File Name ...........
INFO PROCESS Command SCF Commands for SNAX/APC *CharMap File Name ....... CharMap File Last Modif . CharMap File Banner ..... 15Apr95 a04AAA) *Default CharMap Name .... Default CharMap Note .... \TSNA.$SYSTEM.SYSTEM.ZCHARMAP 22 Apr 1991, 12:26:51.080 COM-KRNL/BUILD CHARMAP (T9279D30 FRENCH Translation Tables for French CharMap File Contains Following Maps: CharMap Name ......EUROPEAN CharMap Note ..... ISO 8859/1 to IBM EBCDIC International 5 CharMap Name ......SPANISH CharMap Note .....
SCF Commands for SNAX/APC INFO PROCESS Command MaxInRUSize displays the maximum number of bytes allowed in an incoming request/response unit (RU). The number displayed is the process-wide default; individual PTNR-MODE objects may have different values. MaxApplIoSize displays the maximum number of bytes that the SNAX/APC application can send to or receive from the SNAX/APC process (that is, the maximum size of an IPC message). OneStepRead displays whether one step reads are used.
SCF Commands for SNAX/APC INFO PROCESS Command MaxOutRUSize displays the maximum number of bytes in an outgoing request/response unit (RU). The number displayed is the process-wide default; individual PTNR-MODE objects may have different values. RemoteAttach QUEUE indicates that the remote ATTACH requests are queued if there are no outstanding remote-attached TP-READY requests. (A remote-attached TP-READY request is a TP-READY verb with the TP-LOCAL-ATTACH-INDICATOR set to N.
SCF Commands for SNAX/APC INFO PROCESS Command Log File Name displays the name of the device or file to which SNAX/APC log output goes. Configuration File Name displays the name of the file that contains the SNAX/APC configuration information. This is the file specified in the SNAX/APC CONFIG startup parameter, or the temporary file created by SNAX/APC if the CONFIG parameter was not specified in the RUN command or on a ALTER PROCESS command.
INFO PTNR-LU Command SCF Commands for SNAX/APC CharMap File Banner displays the version banner information of the current character map translation file. A value is displayed under this heading only if the character map file is specified at SNAX/APC startup. Default CharMap Name displays the name of the default character map name. Default CharMap Note displays a description of the character translation table. CharMap Name displays the name of each of the character maps in the character map file.
SCF Commands for SNAX/APC INFO PTNR-LU Command system. The SNANAME, rather than the partner-lu name, is used for building SNA requests (such as the session activation BIND request). Peripheral Node YES indicates that the partner LU resides on a peripheral node. It also implies that the partner LU is a secondary LU (SLU) if the PARALLEL-SESSION-LU attribute is set to NO. NO indicates that the partner LU resides on a subarea node.
SCF Commands for SNAX/APC INFO PTNR-MODE Command PERIPHERAL-NODE YES indicates that the partner LU resides on a peripheral node. It also implies that the partner LU is a secondary LU (SLU) if the PARALLEL-SESSION-LU attribute is set to NO. NO indicates that the partner LU resides on a subarea node. It also implies that the partner LU is a primary LU (PLU) if the PARALLEL-SESSION-LU attribute is set to NO. If the local LU is a parallel-session LU, or its underlying access method is a type 2.
INFO PTNR-MODE Command SCF Commands for SNAX/APC INFO PTNR-MODE Nondetailed Display This example shows the request for nondetailed information about all partner modes subordinate to the partner LU named LUS. -> INFO PTNR-MODE $AP01.LUP.LUS.* The following display is returned in response to this request: SNAX/APC INFO PTNR-MODE: PTNR-MODE Name *ModeName *DMax *DMinCon *DMinCon Sess Winner Loser -----------------------------------------------------------$AP01.LUP.LUS.SNASVCMG SNASVCMG 2 1 1 $AP01.LUP.
INFO PTNR-MODE Command SCF Commands for SNAX/APC parameter of the INITIALIZE_SESSION_LIMIT CNOS verb (which is issued as a result of a START PTNR-MODE command). The sum of the DEFAULTMINCONWINNER attribute and the DEFAULTMINCONLOSER attribute should be less than or equal to the value of the DEFAULTMAXSESSION attribute. INFO PTNR-MODE Detailed Display This example shows the request for detailed information about the target PTNR-MODE object: -> INFO PTNR-MODE $APC1.LU01.CICSLU62.
SCF Commands for SNAX/APC INFO PTNR-MODE Command DefaultMaxSession displays the maximum number of sessions that the PTNR-MODE object can have. This value is used as the LU_MODE_SESSION_LIMIT parameter of the INITIALIZE_SESSION_LIMIT CNOS verb (which is issued as a result of a START PTNR-MODE command). The sum of the value displayed in all DefaultMaxSession headings for all PTNR-MODE objects subordinate to a local LU must be less than or equal to the MaxSession heading value of the local LU.
SCF Commands for SNAX/APC INFO PTNR-MODE Command ActvSessCnt displays the number of currently active sessions. TerminateCount displays the number of sessions that need to be terminated. MaxSession displays the maximum number of sessions allowed between a local LU and a partner LU for a specified mode name. If the value of MaxSession is 1, the local LU is treated as a single-session LU (an LU that does not support parallel sessions).
SCF Commands for SNAX/APC INFO SESSION Command DefaultMaxInRUSize returns the maximum size of normal flow request units (RUs) that the local LU can receive over sessions started with this mode. DefaultMaxOutRUSize returns the maximum size of normal flow request units (RUs) that the local LU can send over sessions started with this mode. CurrentMaxInRUSize returns the current maximum size of normal flow request units (RUs) that the local LU receives on the session.
INFO SESSION Command SCF Commands for SNAX/APC FQPCID if present, this is the PCID field of the fully qualified PCID Control Vector in the exchanged BIND request. Type identifies the role of the local LU in the session, either as the primary or secondary LU. INFO SESSION Detailed Display This example shows the request for detailed information about the specified session: -> INFO SESSION $APC1.LU01.CICSLU62.LU62BIND.
SCF Commands for SNAX/APC INFO SESSION Command Max In Ru Size displays the default and current maximum sizes of an incoming request/response unit (RU). The current value is established during the session’s BIND process. Max Out Ru Size displays the default and current maximum number of bytes in the outgoing request/response unit (RU). The current value is established during the session’s BIND process.
SCF Commands for SNAX/APC INFO TPI Command Local TP Name identifies the name of the local transaction program that currently has a conversation using this session. Consideration The SUB parameter cannot be used with this command-object pair. INFO TPI Command The INFO TPI command displays the current attribute settings of the specified transaction program instance. INFO TPI Nondetailed Display This example shows the request for nondetailed information about the current conversation: -> INFO TPI $AP01.
INFO TPN Command SCF Commands for SNAX/APC The following display is returned in response to this request: SNAX/APC DETAILED INFO TPI: $APC1.LU01.ACCT.003A Resource ID ...................... Local TP Process Name ............ Originated ....................... Local Attach Indicator ........... Dispatched Indicator ............. %H003A 0000 EC83 \TSNA.$ACCT Local LU YES NO Resource ID displays in hexadecimal digits the identifier used by SNAX/APC to identify the conversation and its resources.
INFO TPN Command SCF Commands for SNAX/APC The following display is returned in response to this request: SNAX/APC INFO TPN: TPN Name *General TP-Rdy *Sess Ctrl *Char Mapping *RmtAttach Disp Timer ------------------------------------------------------------$AP01.LUP.%06F1% NO YES NO QUEUE -1 $AP01.LUP.ACCT NO NO NO REJECT -1 Note. Attributes marked with an asterisk (*) can be altered using the ALTER command. TPN Name displays the transaction program name.
INFO TPN Command SCF Commands for SNAX/APC RmtAttach Timer specifies the amount of time in milliseconds that SNAX/APC will wait for a remote TP-READY to arrive to satisfy an ATTACH INFO TPN Detailed Display This example shows the request for detailed information about the transaction program: -> INFO TPN $APC1.LU01.ACCT1 The following display is returned in response to this request: SNAX/APC DETAILED INFO TPN: $APC1.LU01.ACCT1 *GeneralTPReady ... NO *RemoteAttach ..... REJECT *CharMapping ......
SCF Commands for SNAX/APC LISTOPENS Command CharMap Name indicates the translation table which SNAX/APC uses to perform character translation for all mapped conversations subordinate to the target TPN. CharMap Note returns a description of the character translation table. It is obtained from the character map file and is present only if the default character map file for the SNAX/APC process is not the standard ASCII-to-EBCDIC translation.
SCF Commands for SNAX/APC LISTOPENS Command Consideration In addition to displaying entries for all of the open transaction programs, there is also an entry for the SCF session (indicated by the opener name #ZSPI). Command Syntax LISTOPENS [ PROCESS apc-process ] [ , DETAIL ] LISTOPENS PROCESS Display This example shows the request for information about all file system OPEN calls that apply to the SNAX/APC process.
NAMES Command SCF Commands for SNAX/APC BFN is the file number of the open from the backup process. N/A is displayed if a backup process does not exist or if a successful CHECKOPEN procedure call to the backup process has not occurred. PROTOCOL is the protocol interface being used by the opener process. APPL is displayed if the opener process is a transaction program. SPI is displayed if the opener process is using the Subsystem Programmatic Interface.
SCF Commands for SNAX/APC NAMES CONV Command NAMES CONV Command The NAMES CONV command displays all of the matching CONV object names. This example shows the request for information about all conversations associated with the process $APC2: -> ASSUME PROCESS $APC2 -> NAMES CONV * The following display is returned in response to this request: SNAX/APC NAMES CONV: $APC2.* CONVERSATION $APC2.LU043.DEPT6141.0076.0034 $APC2.LU043.DEPT6141.0032.0090 $APC2.LU001.DEPT6060.00DA.0067 $APC2.LU001.DEPT6060.0001.
SCF Commands for SNAX/APC NAMES PTNR-LU Command The following display is returned in response to this request: SNAX/APC NAMES PROCESS $APC1 LU $APC1.LU01 PTNR-LU $APC1.LU01.CICSLU62 PTNR-MODE $APC1.LU01.CICSLU62.LU62BIND SESSION $APC1.LU01.CICSLU62.LU62BIND.0012 $APC1.LU01.CICSLU62.LU62BIND.0018 $APC1.LU01.CICSLU62.LU62BIND.0175 TPN $APC1.LU01.ACCT1 TPI $APC1.LU01.ACCT1.003A CONVERSATION $APC1.LU01.ACCT1.003A.
SCF Commands for SNAX/APC NAMES SESSION Command This example shows the request for information about all matching PTNR-MODE objects: -> ASSUME PROCESS $APC1 -> NAMES PTNR-MODE *.*.*BIND The following display is returned in response to this request: SNAX/APC NAMES PTNR-MODE: $APC1.*.*.*BIND PTNR-MODE $APC1.LU01.CICSLU62.LU62BIND NAMES SESSION Command The NAMES SESSION command displays all of the matching SESSION names.
NAMES TPN Command SCF Commands for SNAX/APC NAMES TPN Command The NAMES TPN command displays all of the matching TPN names. This example shows the request for information about all matching TPN objects that have names beginning with DEPT: -> ASSUME PROCESS $APC2 -> NAMES TPN *.DEPT* The following display is returned in response to this request: SNAX/APC NAMES TPN: $APC2.*.DEPT* TPN $APC2.LU03.DEPT6141 $APC2.LU02.
SCF Commands for SNAX/APC START LU Command STARTING state and then placed in the STARTED state after its parent object is started. START LU Command The START LU command places the specified LU in the STARTED state and issues an OPEN request to the underlying access method. Considerations • • Upon completion of the START LU command, SNAX/APC opens the underlying access method (as specified in the SNAXFILENAME attribute).
START PTNR-MODE Command SCF Commands for SNAX/APC START PTNR-MODE Command The START PTNR-MODE command places the target PTNR-MODE in the STARTING state and issues an INITIALIZE_SESSION_LIMIT CNOS verb with the following parameter settings: CNOS Parameters SNAX/APC Attributes LU_NAME partner-lu MODE_NAME MODENAME LU_MODE_SESSION_LIMIT DEFAULTMAXSESSION MIN_CONWINNERS_SOURCE DEFAULTMINCONWINNER MIN_CONWINNERS_TARGET DEFAULTMINCONLOSER Considerations • • • • • The START PTNR-MODE command plac
STATS Command SCF Commands for SNAX/APC Considerations • • • • To start the TPN object named %06F1% (the CNOS transaction program TPN), you must explicitly enter the name %06F1%; wild-card characters have no effect. The TPN object named %06F1% is started automatically when the LU is started. If you stop the TPN object named %06F1%, you need to issue an explicit START TPN %06F1% command before any CNOS commands can be exchanged.
STATS LU Command SCF Commands for SNAX/APC Considerations • • If you use the RESET option, the counters are reset to 0 after being displayed. The SUB parameter cannot be used in a STATS SESSION command. STATS LU Command The STATS LU command displays the current statistical counters for the specified LU. This example requests statistical information about the LU named LU01: -> ASSUME PROCESS $APC1 -> STATS LU LU01 The following display is returned in response to this request: SNAX/APC STATS LU: $APC1.
STATS PROCESS Command SCF Commands for SNAX/APC Bytes Rcvd displays how many bytes of data have been received. STATS PROCESS Command The STATS PROCESS command displays the current statistical counters for a SNAX/APC process. This example requests statistical information about the process $APC1: -> ASSUME PROCESS $APC1 -> STATS The following display is returned in response to this request: SNAX/APC STATS PROCESS: $APC1 Openers -------------------------------------------------------------Sample Time ....
SCF Commands for SNAX/APC STATS PROCESS Command Reset Time displays the date and time that the statistics counters were last reset. The counters can be reset by one of the following events: • • • The statistics counters were reset by the RESET parameter of the STATS command. The process was initiated. A takeover by the backup process occurred. Config Openers displays the maximum allowed number of concurrent opens of the SNAX/APC process.
SCF Commands for SNAX/APC STATS PTNR-MODE Command Max Fragments displays the maximum number of fragments in the memory pool since the last reset. Current Fragments displays the number of fragments currently in the memory pool. Fail Size displays the number of bytes of the last request for memory that failed. This value is 0 (zero) if no requests have failed. Growth Count displays the number of times the memory pool was increased due to storage pressure.
SCF Commands for SNAX/APC STATS SESSION Command Reset Time displays the date and time that the statistics counters were last reset by either a system startup or STATS RESET command. CNOS Verbs Processed displays how many times the CNOS verbs INITIALIZE_SESSION_LIMIT, CHANGE_SESSION_LIMIT, RESET_SESSION_LIMIT, and PROCESS_SESSION_LIMIT have been processed by SNAX/APC. (For a description of the CNOS verbs, refer to the IBM Transaction Programmer’s Reference Manual for LU Type 6.2.
STATUS Command SCF Commands for SNAX/APC Reset Time displays the date and time that the statistics counters were last reset. Conversation Verbs Processed displays how many times various conversation verbs have been processed during this session. (For a description of the conversation verbs, refer to the IBM Transaction Programmer’s Reference Manual for LU Type 6.2.) STATUS Command The STATUS command displays current status information for the specified objects. STATUS is a nonsensitive command.
SCF Commands for SNAX/APC STATUS CONV Command STATUS CONV Command The STATUS CONV command displays information about the current status of the specified conversation. Status CONV Display This example requests status information about a conversation named 003A: -> ASSUME $APC1.LU01.ACCT.003A.0030 -> STATUS CONV The following display is returned in response to this request: SNAX/APC STATUS CONV: $APC1.LU01.ACCT.003A.0030 Sum State .................... STARTED Session ID ...................
SCF Commands for SNAX/APC STATUS LU Command Reset Send Receive Receive Confirm Receive Confirm Send Receive Confirm Deallocate Prepare to Receive Defer Deallocate Defer Pending Deallocate End Conversation Note. For a description of FSM values, refer to the IBM LU 6.2 Reference Manual for Peer Protocols. Received Bytes Not Read displays the number of bytes that have been received by the local LU but have not yet been read by a transaction program.
STATUS LU Command SCF Commands for SNAX/APC LU Name displays the name of the LU. Sum State displays the current summary state of the LU object. Valid summary states are STARTING, STOPPED, and STARTED. Trace State displays the current state of trace activity for this LU. Valid trace states are ACTIVE and INACT (inactive).
SCF Commands for SNAX/APC STATUS PROCESS Command Conversation Count displays the number of current conversations. STATUS PROCESS Command The STATUS PROCESS command displays information about the current status of the specified SNAX/APC process.
STATUS PROCESS Command SCF Commands for SNAX/APC Config State displays the configuration state of the process. INPROG indicates that configuration is currently in progress, and you cannot issue sensitive commands. DONE indicates that the configuration is available for updating, and you can issue sensitive commands. ERROR indicates that SNAX/APC encountered an error while updating the configuration database. SWITCH indicates that a configuration file switch is in progress.
SCF Commands for SNAX/APC STATUS PTNR-LU Trace File Name displays the name of the trace file, if tracing is active. Backup State displays the summary state of the backup process. Valid summary states are STARTED, STARTING, STOPPED, and STOPPING. Log State displays the current state of the log activity. Valid states are ACTIVE and INACT (inactive). Sec Serv State displays the current state of the security server process. Valid states are ACTIVE and INACT (inactive).
SCF Commands for SNAX/APC STATUS PTNR-MODE Status PTNR-LU Detailed Display This example requests detailed status information about the partner LU named CICSLU62: -> ASSUME $APC1.LU01.CICSLU62 -> STATUS PTNR-LU, DETAIL The following display is returned in response to this request: SNAX/APC DETAILED STATUS PTNR-LU: $APC1.LU01.CICSLU62 Sum State ......... STARTED Sum State displays the current summary state of the PTNR-LU object. Valid summary states are STARTING, STOPPED, and STARTED.
SCF Commands for SNAX/APC STATUS SESSION Command Status PTNR-MODE Detailed Display This example requests detailed status information about a PTNR-MODE object named CICSLU62: -> ASSUME $APC1.LU01.CICS1.LU62BIND -> STATUS PTNR-MODE, DETAIL The following display is returned in response to this request: SNAX/APC DETAILED STATUS PTNR-MODE: $APC1.LU01.CICS1.LU62BIND Sum State ........................... STARTED Current Active Session Count ........ 5 Current ConWinner Session Count .....
STATUS SESSION Command SCF Commands for SNAX/APC The following display is returned in response to this request: SNAX/APC STATUS SESSION: $APC1.LU01.CICSLU62.LU62BIND.013A Sum State..................... Current Conversation ID ...... FSM-BIS....................... FSM-BSM....................... FSM-CHAIN-RCV................. FSM-CHAIN-SEND................ FSM-CONVERSATION.............. FSM-ERROR-OR-FAILURE.......... FSM-PAC-RQ-RCV................ FSM-PAC-RQ-SEND............... FSM-POST.....................
SCF Commands for SNAX/APC STATUS SESSION Command Between Brackets In Brackets FSM-CHAIN-RCV indicates the received chain states. The possible values are: Between Chains In Chains Negative Response Sent Pending Response Pending Send Reply FSM-CHAIN-SEND indicates the sending chain states. The possible values are: Between Chains In Chains Negative Response Received Pending Response Pending Receive Reply FSM-CONVERSATION indicates the conversation status.
SCF Commands for SNAX/APC STATUS SESSION Command Reset Pending FSM-PAC-RQ-SEND indicates whether the LU is waiting for a pacing response for send pacing. The possible values are: Reset Awaiting FSM-POST indicates the posting status of the conversation. The possible values are: Reset Pending Posted Posted FSM-QRI-CHAIN-RCV indicates whether SNAX/APC enforces the setting of the Queued Request Indicator (QRI).
SCF Commands for SNAX/APC STATUS SESSION Command Session Activation Free Pending Attach In Use Pending FMH-12 FSM-STATUS indicates the LU-LU session status.
SCF Commands for SNAX/APC STATUS TPI Command Verb In Progress displays the verb that SNAX/APC is processing for the conversation on this session. If no conversation is active or no verb is currently being processed, None (0000) is displayed. STATUS TPI Command The STATUS TPI command displays the current status of the specified transaction program instance. Status TPI Display This example requests status information about a transaction program instance named 003A: -> ASSUME $APC1.LU01.ACCT.
SCF Commands for SNAX/APC STOP Command TPN Name is the name of the transaction program. Sum State shows the current summary state of the TPN object. Valid states are STOPPED, STARTING, and STARTED. Status TPN Detailed Display This example requests detailed status information about a transaction program named ACCT: -> ASSUME $APC1.LU01.ACCT -> STATUS TPN, DETAIL The following display is returned in response to this request: SNAX/APC STATUS TPN: $APC1.LU01.ACCT Sum State ...............
STOP LU Command SCF Commands for SNAX/APC Object Specification The object specification for the SNAX/APC STOP command is: object-type object name representation LU PTNR-LU PTNR-MODE SESSION TPI TPN local-lu partner-lu partner-mode session-id tpi tpn Consideration • The STOP PTNR-MODE and STOP SESSION commands support a set of attributes in addition to the SEL and SUB parameters. • Only the TPN and PTNR-MODE objects can be stopped when their subordinate objects are not in the STOPPED state.
STOP PTNR-MODE Command SCF Commands for SNAX/APC STOP PTNR-MODE Command The STOP PTNR-MODE command issues a CHANGE_SESSION_LIMIT CNOS verb with the following parameter settings: CNOS Parameter SNAX/APC Attribute LU_NAME partner-lu MODE_NAME MODENAME RESPONSIBLE RESPONSIBLE DRAIN_SOURCE_LU DRAINSOURCE DRAIN_TARGET_LU DRAINTARGET FORCE = YES FORCE = NO If FORCE is specified If NORMAL is specified Upon receipt of a successful CNOS response, the specified PTNR-MODE object is placed in STOPPED st
SCF Commands for SNAX/APC STOP SESSION Command RESPONSIBLE { SOURCE | TARGET } specifies the LU that is responsible for selecting and deactivating sessions, as a result of a change that decreases the session limit or the maximum number of contention-winner sessions for the source or target LU. This value is used as the Responsible parameter of the CHANGE_SESSION_LIMIT CNOS verb. SOURCE specifies that the local LU is responsible, while TARGET specifies that the remote LU is responsible.
SCF Commands for SNAX/APC • STOP TPI Command If NORMAL is specified, a DEACTIVATE_SESSION session control verb with a deactivation type of NORMAL is issued. Example -> ASSUME PROCESS $APC1 -> STOP SESSION LU01.CICSLU62.LU62BIND.013A STOP TPI Command The STOP TPI command stops the specified transaction program instance and removes it from the SNAX/APC process. This command has exactly the same effect as the ABORT TPI command. Example -> ASSUME PROCESS $APC1 -> STOP TPI LU01.ACCT1.
TRACE Command SCF Commands for SNAX/APC Object Specification The object specification for the SNAX/APC TRACE command is: object-type object name representation LU PROCESS local-lu apc-process General Command Parameters The attributes that apply to both the LU and the PROCESS object types are: STOP discontinues a trace that is currently in progress. TO file-name specifies the file to which trace information is to be written. If the file already exists, it is purged before a new file is created.
SCF Commands for SNAX/APC TRACE Command BIU traces basic information units (BIUs) sent to and received from the underlying access method (such as SNAX/APN or SNAX/XF). BUFFER traces records obtained and returned to the local or extended buffer pool. DFC traces the finite state machines (FSMs) for the Data Flow Control layer. LNS traces the FSMs for the Logical Network Services layer. PROC traces data handled by the internal procedures of SNAX/APC.
SCF Commands for SNAX/APC TRACE LU Command TRACE LU Command The TRACE LU command starts, stops, or modifies the trace operations of the target local LU. Example -> ASSUME PROCESS $APC1 -> TRACE LU LU01, TO $APC.APCTRC.TRCLU01, RECSIZE 120, NOWRAP -> TRACE LU LU01, STOP TRACE PROCESS Command The TRACE PROCESS command starts, stops, or modifies the trace operations of the target SNAX/APC process.
SCF Commands for SNAX/APC The following detailed display is returned in response to this request: Detailed VERSION \TSNA.
A Base and Option Sets Supported by SNAX/APC This appendix describes the subset of LU 6.2 functions supported by SNAX/APC. Basic and mapped conversations are described in Section 1, Introduction, of this manual. Table A-1.
Base and Option Sets Supported by SNAX/APC Table A-2. Mapped Conversation Verbs Verb Names Support in SNAX/APC MC-ALLOCATE yes MC-CONFIRM yes MC-CONFIRMED yes MC-DEALLOCATE yes MC-FLUSH yes MC-GET-ATTRIBUTES yes MC-POST-ON-RECEIPT no MC-PREPARE-FOR-SYNCPT no MC-PREPARE-TO-RECEIVE yes MC-RECEIVE-AND-WAIT yes MC-RECEIVE-IMMEDIATE yes MC-REQUEST-TO-SEND yes MC-SEND-DATA yes MC-SEND-ERROR yes MC-TEST no Table A-3.
Base and Option Sets Supported by SNAX/APC Table A-4.
Base and Option Sets Supported by SNAX/APC Figure A-1. LU 6.2 Functions and Option Set Numbering Option Sets Verb-Oriented Parameter Oriented Either Orientation Base Set Conversation Verbs Control Operator Verbs 1xx 5xx 2xx 6xx Both Verbs NO NUMBERS IN THE BASE SET 4xx CDT 011.
Base and Option Sets Supported by SNAX/APC Table A-5.
Base and Option Sets Supported by SNAX/APC Table A-5.
Base and Option Sets Supported by SNAX/APC 203 Immediate allocation of a session. This option set allows a program to allocate a contention-winner session only if one is immediately available; otherwise the allocation is unsuccessful. A further description may be found in the SNAX/APC Application Programming Manual. 213 Program-supplied user ID and password. This option set allows the program to supply a user ID and password.
Base and Option Sets Supported by SNAX/APC 607 Uninterpreted LU names. This option set allows a program or operator to specify the uninterpreted names of remote LUs. SNAX/APC knows these names through the define LU verbs, but the TPs can only use the local names of remote LUs in (MC)ALLOCATE verbs. 610 Maximum RU size bounds. This option set allows a program or operator to specify the lower and upper limits for the maximum RU sizes on sessions within an (LU, mode) group.
B SCF Command Syntax Summary for SNAX/APC ABORT Command Use the ABORT command to terminate the operation of objects as quickly as possible. ABORT LU Command ABORT [ LU $apc-process.local-lu ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] ABORT PTNR-LU Command ABORT [ PTNR-LU $apc-process.local-lu.partner-lu ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] ABORT PTNR-MODE Command ABORT [ PTNR-MODE $apc-process.local-lu.ptnr-lu.
SCF Command Syntax Summary for SNAX/APC ADD Command ADD Command The ADD command is used to add various objects to the configuration ADD LU Command The ADD LU command defines an LU object to a SNAX/APC process. ADD [ LU $apc-process.
SCF Command Syntax Summary for SNAX/APC ADD PTNR-MODE Command ADD PTNR-MODE Command The ADD PTNR-MODE command defines a PTNR-MODE object to a SNAX/APC process. ADD [ PTNR-MODE $apc-process.local-lu.ptnr-lu.
SCF Command Syntax Summary for SNAX/APC ALTER LU Command ALTER LU Command The ALTER LU command modifies the values of the attribute settings of an existing object. ALTER [ LU $apc-process.
ALTER PTNR-LU Command SCF Command Syntax Summary for SNAX/APC ALTER PTNR-LU Command The ALTER PTNR-LU command modifies the values of the attribute settings of an existing object. ALTER [ PTNR-LU $apc-process.local-lu.
SCF Command Syntax Summary for SNAX/APC ALTER TPN Command ALTER TPN Command The ALTER TPN command modifies the values of the attribute settings of an existing object. ALTER [ TPN $apc-process.local-lu.
SCF Command Syntax Summary for SNAX/APC ASSUME SESSION Command ASSUME SESSION Command ASSUME [ SESSION $apc-proc.local-lu.ptnr-lu.ptnr-mode.sessid ] ASSUME TPI Command ASSUME [ TPI $apc-process.local-lu.tpn.tpi-id ]] ASSUME TPN Command ASSUME [ TPN $apc-process.local-lu.tpn ] ] DELETE Command The DELETE command removes objects from a SNAX/APC process that were added using the ADD command. DELETE LU Command DELETE [ LU $apc-process.
SCF Command Syntax Summary for SNAX/APC INFO CONV Command INFO CONV Command INFO [ CONV $apc-process.local-lu.tpn.tpi-id.conv-id ] [, DETAIL ] [, SEL [ NOT ] summary-state ] INFO LU Command INFO [ LU $apc-process.local-lu ] [, DETAIL ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] INFO PROCESS Command INFO [ PROCESS $apc-process ] [, DETAIL ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] INFO PTNR-LU Command INFO [ PTNR-LU $apc-process.local-lu.
SCF Command Syntax Summary for SNAX/APC LISTOPENS Command LISTOPENS Command The LISTOPENS command displays a list of all file system OPEN calls that apply to the SNAX/APC process. LISTOPENS [PROCESS $apc-process ] [ , DETAIL ] NAMES Command The NAMES command displays the names of all objects having the specified object type. NAMES CONV Command NAMES [ CONV $apc-process.local-lu.tpn.tpi-id.conv-id ] [, SEL [ NOT ] summary-state ] NAMES LU Command NAMES [ LU $apc-process.
SCF Command Syntax Summary for SNAX/APC NAMES TPI Command NAMES TPI Command NAMES [ TPI $apc-process.local-lu.tpn.tpi-id ] [, SEL [ NOT ] summary-state ] NAMES TPN Command NAMES [ TPN $apc-process.local-lu.tpn ] [, SEL [ NOT ] summary-state ] START Command The START command initiates an object’s operation and places the object in the STARTED state. START LU Command START [ LU $apc-process.local-lu ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] START PTNR-LU Command START [ PTNR-LU $apc-process.
SCF Command Syntax Summary for SNAX/APC STATS LU Command STATS LU Command STATS [ LU $apc-process.local-lu ] [, RESET ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] STATS PROCESS Command STATS [ PROCESS $apc-process ] [, RESET ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] STATS PTNR-MODE Command STATS [ PTNR-MODE $apc-process.local-lu.ptnr-lu.ptnr-mode ] [, RESET ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] STATS SESSION Command STATS [ SESSION $apc-proc.local-lu.ptnr-lu.
SCF Command Syntax Summary for SNAX/APC STATUS PTNR-LU Command STATUS PTNR-LU Command STATUS [ PTNR-LU $apc-process.local-lu.partner-lu ] [, DETAIL ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] STATUS PTNR-MODE Command STATUS [ PTNR-MODE $apc-proc.local-lu.ptnr-lu.ptnr-mode ] [, DETAIL ] [, SEL [ NOT ] summary-state ] [, SUB [ subtype ] ] STATUS SESSION Command STATUS [ SESSION $apc-proc.local-lu.ptnr-lu.ptnr-mode.
SCF Command Syntax Summary for SNAX/APC STOP PTNR-MODE Command STOP PTNR-MODE Command STOP [ PTNR-MODE $apc-process.local-lu.ptnr-lu.ptnr-mode ] [, attribute-spec ] where attribute-spec is: [ [ [ [ [ [ , , , , , , DRAINSOURCE { YES | NO } ] DRAINTARGET { YES | NO } ] { NORMAL | FORCE } ] RESPONSIBLE { SOURCE | TARGET } ] SEL [ NOT ] summary-state ] SUB [ subtype ] ] STOP SESSION Command STOP [ SESSION $apc-proc.local-lu.ptnr-lu.ptnr-mode.
SCF Command Syntax Summary for SNAX/APC TRACE PROCESS Command TRACE PROCESS Command TRACE [ PROCESS $apc-process ] { [ , STOP ] | [ , TO file-name [, attribute-spec ] ] } where, if TO is specified, attribute-spec is none or more of the following: [ [ [ [ , , , , PAGES number ] RECSIZE number ] SELECT { ALL | [(} opt [ ,opt ... ] [)] } { WRAP | NOWRAP } ] VERSION Command The VERSION command retrieves the version string of the SNAX/APC process.
C SCF Error Messages for SNAX/APC This appendix lists the SNAX/APC error messages, describes the probable cause of each error, and suggests an appropriate recovery action. Error messages for SNAX/APC can be generated at various interface levels. When a command is entered at the operator terminal, using the Subsystem Control Facility (SCF) or through a command file, the command takes the following route (if no errors are detected): 1. The command passes through SCF. 2.
SCF Error Messages for SNAX/APC Before You Report a Problem Before You Report a Problem Some error messages are not easily recoverable and require you to seek additional help. In these cases, follow the standard procedures at your site for contacting the appropriate support personnel. These procedures might involve contacting the Tandem NonStop Support Center or your local Tandem support representative. Collect any relevant information before reporting the problem.
SCF Error Messages for SNAX/APC SNAX/APC Errors SNAX/APC Errors This subsection lists all of the SNAX/APC error messages. Error 00001 SNAXAPC 00001 The ADD SESSION command was rejected. Do not retry until the condition is corrected. Probable Cause. The SNAX/APC subsystem encountered an error during the processing of an ADD SESSION command (which is equivalent to the ACTIVATE_SESSION verb). The equivalent return code defined in the IBM Transaction Programmer’s Reference Manual for LU 6.
Error 00004 SCF Error Messages for SNAX/APC be activated because the session limit for the PTNR-MODE object is set to 0. The condition can also occur if a system-definition error or session-activation protocol error occurred before the conversation could be allocated. Recommended Action. The request should not be retried until the cause of the failure has been determined and corrected. Check the EMS event log to identify and correct the problem. Error 00004 SNAXAPC 00004 Operation failed.
SCF Error Messages for SNAX/APC Error 00007 The error is caused by an ABORT or STOP PTNR-MODE command. Recommended Action. None. This message is a warning that the PTNR-MODE object has aborted. Error 00007 SNAXAPC 00007 This command cannot act upon a default object. Probable Cause. The ALTER and DELETE commands cannot act upon either the default PTNR-MODE object, SNASVCMG, or the default TPN object, %06F1%. The command was therefore rejected by SNAX/APC. Recommended Action.
Error 00011 SCF Error Messages for SNAX/APC command was rejected due to a command race. The equivalent return code, as defined in the IBM Transaction Programmer’s Reference Manual for LU 6.2, is COMMAND_RACE_REJECT Recommended Action. Retry the command if the result of the remote CNOS operation is not satisfactory, or if both CNOS operations failed. Error 00011 SNAXAPC 00011 SNAX/APC is still being configured. commands cannot be issued. Sensitive Probable Cause.
SCF Error Messages for SNAX/APC Error 00015 Recommended Action. Change the MODENAME attribute in the ADD PTNR-MODE command. Error 00015 SNAXAPC 00015 An invalid device type was specified. Probable Cause. Either the device type returned by the file specified in the SNAXFILENAME attribute by the underlying access method is unknown to the SNAX/APC subsystem, or the LU is a parallel session LU but the access method is not a node type 2.1. This error is usually caused by a START LU command.
SCF Error Messages for SNAX/APC Error 00018 Recommended Action. Use the INFO command to verify the target PTNR-MODE object’s mode name, and use the ALTER PTNR-MODE command to change it. Error 00018 SNAXAPC 00018 The default object cannot be deleted. Probable Cause. A command attempting to delete a default object was rejected. The default object was probably either the default PTNR-MODE object, SNASVCMG, or the default CNOS TPN, %06F1. Recommended Action. Do not attempt to delete a default object.
SCF Error Messages for SNAX/APC Error 00022 Error 00022 SNAXAPC 00022 A resource failure occurred. Probable Cause. A resource failure occurred during the processing of a CNOS-related command. The equivalent return code, as defined in the IBM Transaction Programmer’s Reference Manual for LU 6.2 is RESOURCE_FAILURE_NO_RETRY. This error was probably caused by an ABORT, STOP, ALTER, or START PTNRMODE command.
SCF Error Messages for SNAX/APC Error 00025 Recommended Action. Issue the ALTER PTNR-MODE command instead. Error 00025 SNAXAPC 00025 The session limit has not been initialized it is still set to 0. Probable Cause. An ALTER PTNR-MODE command attempted to change the PTNRMODE object’s session limit, and was rejected because the PTNR-MODE object was in the STOPPED state and the session limit is 0. The equivalent return code defined in the IBM Transaction Programmer’s Reference Manual for LU 6.
SCF Error Messages for SNAX/APC Error 00029 Error 00029 SNAXAPC 00029 Subordinate objects were not stopped. Probable Cause. An ABORT or STOP command issued for an LU object or a PTNRLU object was rejected because one or more of its subordinate objects was still in the STARTED state. Recommended Action. Stop all of the target object’s subordinate objects before issuing a STOP or ABORT command to the target object, or specify the SUB parameter with the STOP or ABORT command.
SCF Error Messages for SNAX/APC Error 00033 Error 00033 SNAXAPC 00033 Tracing has not been started. Probable Cause. The TRACE, STOP command was rejected because the trace was already in the INACTIVE state. Recommended Action. None. Error 00034 SNAXAPC 00034 Tracing shutdown error. Probable Cause. The TRACE, STOP command was rejected due to a deallocatesegment error. Recommended Action. You need to seek additional help.
SCF Error Messages for SNAX/APC • • Error 00038 When altering the MODENAME, DEFAULTMAXSESSION, DEFAULTMINCONWINNER, DEFAULTMINCONLOSER, MAXAUTOACT, RCVWINDOW, and SENDWINDOW attributes, the PTNR-MODE object must be in the STOPPED state. When altering the MAXSESSION, MINCONWINNER, MINCONLOSER, and RESPONSIBLE attributes, the PTNR-MODE object must be in the STARTED state. Recommended Action.
SCF Error Messages for SNAX/APC Error 00041 Error 00041 SNAXAPC 00041 You did not specify a valid configuration file name. Probable Cause. An invalid configuration file name was specified. The configuration file name must be local to the SNAX/APC process. Recommended Action. Retry the command with a valid file name. Error 00042 SNAXAPC 00042 The object is currently being started. Probable Cause.
SCF Error Messages for SNAX/APC Error 00503 Error 00503 SNAXAPC 00503 Internal error: Input out of range. Probable Cause. An attribute value has been specified that is out of the allowable range. Recommended Action. Correct the command and resend it. Error 00504 SNAXAPC 00504 Input value invalid. Probable Cause. An invalid attribute value has been specified. Recommended Action. Correct the command and resend it. Error 00505 SNAXAPC 00505 Required keyword parameter is missing. Probable Cause.
Error 00509 SCF Error Messages for SNAX/APC Recommended Action. Correct the command and resend it. Error 00509 SNAXAPC 00509 Invalid length for keyword. Probable Cause. The specified length for keyword is invalid. Recommended Action. Enter a valid value for keyword and resubmit the command. Error 00510 SNAXAPC 00510 RPM internal error. Probable Cause. An internal error has occurred. Recommended Action. You need to seek additional help.
D Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-1 lists the LU 6.2 CNOS verbs and parameters and the equivalent commands and attributes implemented by SCF for SNAX/APC. Table D-1.
Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-1. CNOS Verbs Versus SNAX/APC SCF Commands and Attributes (page 2 of 2) CNOS Verbs and Parameters SCF Commands and Attributes DRAIN_TARGET DRAINTARGET FORCE FORCE RETURN_CODE (Command Return) Table D-2 lists the LU 6.2 Session Control verbs and parameters, and the equivalent commands and attributes implemented by SCF for SNAX/APC. Table D-2.
Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-3.
Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-3.
Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-3. Definition Verbs Versus SNAX/APC SCF Commands and Attributes (page 4 of 5) Definition Verbs and Parameters SCF Commands and Attributes INFO PROCESS...DETAIL RECEIVE_MAX_RU_SIZE_LOWER_BOUND INFO PROCESS...
Comparison of LU 6.2 Control Operator Verbs and SNAX/APC Table D-3.
E Event Management The SNAX/APC subsystem provides information about events that occur in the subsystem by issuing event messages. A management application can obtain these event messages by opening an Event Management Service (EMS) distributor process and requesting the messages. The application can also specify that a filter be applied to select certain event messages.
Event Management Subsystem Processes That Report Events 5. EMS logs—include the event (EMS) logs that were active when the problem occurred. 6. Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect, or if it hangs and you invoke Inspect via the DEBUG command, issue the SAVE command. 7.
Common Events: -00001 Through -00999 and -32nnn Series Events Event Management Table E-1.
SNAX/APC Event Summary Event Management Table E-1.
SNAX/APC Event Summary Event Management Table E-2. SNAX/APC Event Messages (page 2 of 3) Event Number Symbolic Name (ZAPC-EVT-) Description 11 BKUP-TAKEOVER The process was taken over by the backup CPU. 12 DEALLOCATE-ERR Deallocation of an extended data segment used for tracing failed. 13 INIT-INFO Indicates initialization information. 14 LU-DEVINFO-ERR A device type inquiry for an LU has failed. 15 LU-CONNECT-ERR A connect for an LU has failed.
SNAX/APC Event Summary Event Management Table E-2. SNAX/APC Event Messages (page 3 of 3) Event Number Symbolic Name (ZAPC-EVT-) Description 34 SWITCHING-DB-DONE The configuration file switching is complete. 35 NO-CFG-FILE The configuration file was not useable or in the switching process when backup takeover occurred 36 SWITCHING-DB-FAILED The switch to a new configuration file failed. 37 CFG-DB-CONVERTED Configuration file has been converted to the current level.
Potentially Critical Events Event Management ZAPC-EVT-INV-OP ZAPC-EVT-INVALID-LOGON ZAPC-EVT-LU-CONNECT-ERR ZAPC-EVT-LU-DEVINFO-ERR ZAPC-EVT-LU-OPEN-ERR ZAPC-EVT-NEG-RSP-RCVD ZAPC-EVT-NEG-RSP-SENT ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE ZAPC-EVT-SEC-SERVER-ERR ZAPC-EVT-SNAX-FILE-ERR Information Events ZAPC-EVT-BID-REJECT ZAPC-EVT-BKP-TAKEOVER ZAPC-EVT-INIT-INFO ZAPC-EVT-TPREADY-REJECT ZAPC-EVT-UNXP-PAC-RQ ZAPC-EVT-UNKNOWN-IPC CNOS Operation Error Events ZAPC-EVT-CNOS-CMD-RACE ZAPC-EVT-CNOS-CMD-REJECTED ZAPC-EVT-
Event Message Descriptions Event Management CONSOLE-PRINT contains the value ZSPI-VAL-TRUE, messages are also displayed on the operator console controlled by the compatibility distributor ($Z0). However, the SNAX/APC message file may be used to inhibit the display of messages on the operator console. (Refer to Part I, SNAX/APC Planning and Configuration for more information about inhibiting message displays.
1: ZAPC-EVT-FSM-ERR Event Management 1: ZAPC-EVT-FSM-ERR SNAX/APC encountered an unexpected finite state machine (FSM) error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-FSM-NAME ZAPC-TKN-STATE ZAPC-TKN-FSM-EVT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT.
1: ZAPC-EVT-FSM-ERR Event Management ZAPC-TKN-FSM-NAME identifies the name of the finite state machine (FSM). This enumerated token can have one of the following literal values: ZAPC-VAL-FSM-NAME-BIS-BDR is the finite state machine FSM_BIS_BIDDER, which represents the status of a bidder half-session. ZAPC-VAL-FSM-NAME-BIS-FSP is the finite state machine FSM_BIS_FSP, which represents the status of a firstspeaker half-session.
1: ZAPC-EVT-FSM-ERR Event Management ZAPC-VAL-FSM-NAME-PAC-RQ-R is the finite state machine FSM_PAC_RQ_RCV, which represents the ability to send a session-pacing response for receive pacing. ZAPC-VAL-FSM-NAME-PAC-RQ-S is the finite state machine FSM_PAC_RQ_SEND, which represents the ability to send a session-level pacing request for send pacing. ZAPC-VAL-FSM-NAME-POST is the finite state machine FSM_POST, which represents the posting status of a conversation.
1: ZAPC-EVT-FSM-ERR Event Management ZAPC-TKN-STATE identifies the state value for FSM error events. ZAPC-TKN-FSM-EVT identifies the event that triggered a FSM error. Conditional Token ZAPC-TKN-LU-NAME identifies the name of the LU. Cause. SNAX/APC encountered an unexpected finite state machine (FSM) error. Effect. The process continues, but some sessions may encounter unpredictable difficulties. Recovery. You need to seek additional help.
2: ZAPC-EVT-INV-INIT Event Management 2: ZAPC-EVT-INV-INIT The SNAX/APC startup parameters contained an invalid PARAM. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-INIT-ERR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Conditional Tokens ZAPC-TKN-FILE-ERR ZAPC-TKN-PARAM token-type ZSPI-TYP-INIT. token-type ZSPI-TYP-STRING 20.
2: ZAPC-EVT-INV-INIT Event Management ZAPC-VAL-INIT-ERR-PARAM indicates that the error was caused by an invalid parameter. ZAPC-VAL-INIT-ERR-VALUE indicates that the error was caused by an invalid parameter value. Conditional Tokens ZAPC-TKN-PARAM-ERR identifies the name of a parameter that is invalid. ZAPC-TKN-FILE-ERR identifies a file-system error. Cause. The SNAX/APC startup parameters contained an invalid PARAM. Effect. The process terminates abnormally. Recovery. Correct the startup parameter.
3: ZAPC-EVT-INV-CONFIG Event Management 3: ZAPC-EVT-INV-CONFIG This indicates an invalid configuration file. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-ERR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Conditional Tokens ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INIT.
3: ZAPC-EVT-INV-CONFIG Event Management ZAPC-TKN-CONFIG-ERR identifies the fault in an invalid configuration file. This is an enumerated token. Possible values are: ZAPC-VAL-CONFIG-ERR-BAD-FILE indicates that the error was caused by an invalid configuration file. ZAPC-VAL-CONFIG-ERR-BAD-CODE indicates that the error was caused by an invalid configuration file code. ZAPC-VAL-CONFIG-ERR-BAD-VSN indicates that the error was caused by a configuration version mismatch.
6: ZAPC-EVT-INV-OP Event Management 6: ZAPC-EVT-INV-OP An operational failure has been detected by SNAX/APC. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Abending - SNAX/APC internal error Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PROC.
10: ZAPC-EVT-BID-REJECT Event Management 10: ZAPC-EVT-BID-REJECT A request from a remote LU for a conversation with a local LU was rejected because SNAX/APC could not obtain the resources. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
11: ZAPC-EVT-BKP-TAKEOVER Event Management 11: ZAPC-EVT-BKP-TAKEOVER The process is taken over by the backup CPU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Process takeover by backup Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PROC. Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number.
12: ZAPC-EVT-DEALLOCATE-ERR Event Management 12: ZAPC-EVT-DEALLOCATE-ERR SNAX/APC was not able to deallocate an extended data segment used for tracing. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Deallocate segment error Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PROC.
13: ZAPC-EVT-INIT-INFO Event Management 13: ZAPC-EVT-INIT-INFO This event provides initialization information. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-INIT-INFO token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Event-Message Text <1>: <2> Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PROC. <2> equals ZAPC-TKN-INIT-INFO.
13: ZAPC-EVT-INIT-INFO Event Management ZAPC-VAL-INIT-INFO-RE-INIT-END indicates that SNAX/APC reinitialization has completed. Cause. SNAX/APC started or ended initialization or reinitialization. Effect. This is an informational event only; the process continues. Recovery. No action is required.
14: ZAPC-EVT-LU-DEVINFO-ERR Event Management 14: ZAPC-EVT-LU-DEVINFO-ERR A device type inquiry for an LU has failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
14: ZAPC-EVT-LU-DEVINFO-ERR Event Management Effect. The process continues; however, the LU does not start. Recovery. Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction.
15: ZAPC-EVT-LU-CONNECT-ERR Event Management 15: ZAPC-EVT-LU-CONNECT-ERR A connect for an LU failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
15: ZAPC-EVT-LU-CONNECT-ERR Event Management Cause. A connect for an LU failed. (A connect is a control-11 call to the underlying access method for the LU.) Effect. The process continues; however, the LU does not start. Recovery. Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction. SNAX/APC was unable to open the underlying access method.
15: ZAPC-EVT-LU-CONNECT-ERR Event Management ZAPC-TKN-LU-NAME. identifies the name of the LU. zapc-tkn-FILE-ERR identifies a file-system error. Cause. SNAX/APC was unable to open the underlying access method. Effect. The process continues; however, the LU does not start. Recovery. Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction.
17: ZAPC-EVT-INV-DEV-TYPE Event Management 17: ZAPC-EVT-INV-DEV-TYPE The device type of an LU is invalid for the underlying access method. Either the LU is neither a SNAX/XF LU nor a SNAX/CDF APPL object, or the LU is a parallel-session LU and the access method is not SNAX/APN. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Management 17: ZAPC-EVT-INV-DEV-TYPE SNAX/CDF APPL object. If the LU is a parallel-session LU, the access method must be SNAX/APN.
20: ZAPC-EVT-SNAX-FILE-ERR Event Management 20: ZAPC-EVT-SNAX-FILE-ERR SNAX/APC received a file-system error from the underlying access method. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
Event Management 20: ZAPC-EVT-SNAX-FILE-ERR Effect. The process continues, but all of the sessions on this LU will be lost and the conversations using theses sessions will be deallocated. A reopen will be issued. If the open fails, the LU and its subordinates will go into the STARTING state. Recovery. Use the file-system error returned in this event message to identify why the error occurred, and take appropriate actions.
21: ZAPC-EVT-TPREADY-REJECT Event Management 21: ZAPC-EVT-TPREADY-REJECT SNAX/APC could not complete a TP-READY request because it could not obtain the necessary resources. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
22: ZAPC-EVT-UNXP-PAC-RQ Event Management 22: ZAPC-EVT-UNXP-PAC-RQ A pacing request was received before SNAX/APC had responded to the last pacing request, or an unexpected pacing request was received. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
23: ZAPC-EVT-UNKNOWN-IPC Event Management 23: ZAPC-EVT-UNKNOWN-IPC SNAX/APC received an unknown IPC message for processing. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Unknown message received Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PROC.
24: ZAPC-EVT-RCVD-RMT-CNOS-CMD Event Management 24: ZAPC-EVT-RCVD-RMT-CNOS-CMD A remote CNOS command was received. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Received remote CNOS command Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PTNR-LU.
25: ZAPC-EVT-CNOS-CONV-FAIL Event Management 25: ZAPC-EVT-CNOS-CONV-FAIL The CNOS conversation failed at the specified conversation verb. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU ZAPC-TKN-CONV-FAILED-AT ZAPC-TKN-RC-RETN ZAPC-TKN-RC-RETN-DETL token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT.
25: ZAPC-EVT-CNOS-CONV-FAIL Event Management ZAPC-VAL-CONV-FAILED-AT-RAW is returned if the CNOS conversation failed at the Receive_and_Wait verb. ZAPC-VAL-CONV-FAILED-AT-SD is returned if the CNOS conversation failed at the Send_Data verb. ZAPC-TKN-RC-RETN identifies the REP-RETURN-CODE of the failed CNOS conversation verb. ZAPC-TKN-RC-RETN-DETL identifies the REP-RETURN-CODE-DETAIL of the failed CNOS conversation verb. Cause. The CNOS conversation failed at the specified conversation verb. Effect.
26: ZAPC-EVT-CNOS-CMD-RACE Event Management 26: ZAPC-EVT-CNOS-CMD-RACE A CNOS command race was detected. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: CNOS command race occurred Message Parameter Descriptions <1> equals ZCOM-TKN-SUBJ-PTNR-LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number.
27: ZAPC-EVT-SESS-LIMIT-CHANGED Event Management 27: ZAPC-EVT-SESS-LIMIT-CHANGED The session limits of the specified PTNR-MODE object were changed by either the local or the remote LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-MODE ZAPC-TKN-OPERATOR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM.
27: ZAPC-EVT-SESS-LIMIT-CHANGED Event Management ZAPC-VAL-OPERATOR-REMOTE-LU specifies that the command was initiated by the partner LU. Cause. The session limits of the specified PTNR-MODE object have been changed by either the local or the remote LU. Effect. The process continues. Recovery. Informational message only; no action is required.
28: ZAPC-EVT-CNOS-CMD-NEGOTIATED Event Management 28: ZAPC-EVT-CNOS-CMD-NEGOTIATED The remote CNOS command is in effect, and the session limits have been negotiated. The CNOS reply was returned to the remote LU with the negotiated session limits. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
29: ZAPC-EVT-CNOS-CMD-REJECTED Event Management 29: ZAPC-EVT-CNOS-CMD-REJECTED The remote CNOS command was rejected due to the specified reason. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU ZAPC-TKN-REASON token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM.
Event Management 29: ZAPC-EVT-CNOS-CMD-REJECTED Cause. The remote CNOS command was rejected for the specified reason. Effect. The remote CNOS command is rejected. A reply is returned with the specified reason. No session limit is changed. Recovery. Correct and reissue the CNOS command at the remote LU.
30: ZAPC-EVT-NEG-RSP-RCVD Event Management 30: ZAPC-EVT-NEG-RSP-RCVD The event indicates the receipt of a negative response on an SNA session.
30: ZAPC-EVT-NEG-RSP-RCVD Event Management ZCMK-TKN-SNAERR is the first two bytes of sense data. In the message text, argument <2> is shown in hexadecimal, while argument <4> shows an English language explanation of the message for this token. ZAPC-TKN-SENSE2 is the second two bytes of sense data. ZAPC-TKN-MUT is the SNA response RU. Cause. A negative response has been received on an SNA session. Effect. Inspect the sense data to determine the effect of the negative response. Recovery.
31: ZAPC-EVT-NEG-RSP-SENT Event Management 31: ZAPC-EVT-NEG-RSP-SENT This event indicates that a negative response has been sent on an SNA session. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-SESS ZCMK-TKN-SNAERR ZAPC-TKN-SENSE2 ZAPC-TKN-MUT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
31: ZAPC-EVT-NEG-RSP-SENT Event Management ZCMK-TKN-SNAERR is the first two bytes of sense data. In the message text, argument <2> is shown in hexadecimal, while argument <4> shows an English language explanation of the message for this token. As much of the session name is supplied as is known at the time the response is sent. For example, if SNAX/APC receives a BIND request, it may reject it before it has located the partner LU (or because it does not recognize the partner LU).
32: ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE Event Management 32: ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE This event indicates that SNAX/APC received an RU that exceeds the maximum RU size. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-SESS-ID token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 32: ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE Cause. SNAX/APC received an RU that exceeds the maximum RU size. Effect. Upon receipt of an oversized RU, SNAX/APC brings down the session. Any conversation using this session is therefore terminated. Recovery. The maximum RU size is decided at the session establishment. No RU should be sent with a size greater than this value. Verify the current RU size setting in the remote LU.
33: ZAPC-EVT-SWITCHING-DB Event Management 33: ZAPC-EVT-SWITCHING-DB The configuration file is currently being switched to the named file. If the file is temporary, only the name of the VOLUME can be displayed at this time. The name of the new file will be indicated in the event generated at the successful completion of the switch (ZAPC-EVT-SWITCHING-DB-DONE).
33: ZAPC-EVT-SWITCHING-DB Event Management Recovery. You should wait for the event that follows to determine the success or failure of the switch. One of the following two possible events will follow this event: ZAPC-EVT-SWITCHING-DB-FAILED or ZAPC-EVT-SWITCHING-DB-DONE If the switch fails, an additional event will precede the ZAPC-EVT-SWITCHING-DBFAILED event. This event will show the error that caused the switch to fail.
34: ZAPC-EVT-SWITCHING-DB-DONE Event Management 34: ZAPC-EVT-SWITCHING-DB-DONE The configuration file switching process is complete. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-FILE token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
35: ZAPC-EVT-NO-CFG-FILE Event Management 35: ZAPC-EVT-NO-CFG-FILE A backup takeover occurred when the configuration database file was unuseable or in the process of being switched to a new file. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
36: ZAPC-EVT-SWITCHING-DB-FAILED Event Management 36: ZAPC-EVT-SWITCHING-DB-FAILED The switch to a new configuration file has failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Switching configuration database - FAILED Message Parameter Descriptions <1>equals ZCOM-TKN-SUBJ-PROC.
37: ZAPC-EVT-CFG-DB-CONVERTED Event Management 37: ZAPC-EVT-CFG-DB-CONVERTED After a warm start, SNAX/APC automatically converts the configuration database specified by the CONFIG attribute value to the current level. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-FILE token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 37: ZAPC-EVT-CFG-DB-CONVERTED from the timestamp and the node, volume, and subvolume values are the same as the node, volume and subvolume names for the new configuration file. Recovery. This is an informational message. No action is required.
38: ZAPC-EVT-INVALID LOGON Event Management 38: ZAPC-EVT-INVALID LOGON SNAX/APC received an attach that contained either an invalid user ID and password pair or an unknown user ID with the already-verified indicator. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-SUBJ-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-SUBJ-MARK ZCOM-TKN-SUBJ-PTNR-LU ZAPC-TKN-LU62-USERID token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-MARK.
Event Management 38: ZAPC-EVT-INVALID LOGON Recovery. The security information supplied by the partner LU does not agree with the security information defined in the local security manager (Safeguard). There are three cases to consider. 1. The local security information is wrong. To recover, correct the security definitions in the security manager, Safeguard. 2. The remote security information is wrong. This could indicate an incorrect configuration at the remote LU.
39: ZAPC-EVT-SEC-SERVER-STARTED Event Management 39: ZAPC-EVT-SEC-SERVER-STARTED This event reports SNAX/APC started the security server. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-SUBJ-MARK ZCOM-TKN-SUBJ-PROC ZAPC-TKN-SEC-SERVER-NAME ZAPC-TKN-SEC-SERVER-CPU token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-UINT.
40: ZAPC-EVT-SEC-SERVER-ERR Event Management 40: ZAPC-EVT-SEC-SERVER-ERR SNAX/APC attempted to access the security server and failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-SUBJ-MARK ZCOM-TKN-SUBJ-PROC ZAPC-TKN-SEC-SERVER-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INT.
Event Management 40: ZAPC-EVT-SEC-SERVER-ERR automatically from the error, SNAX/APC deactivates the session; the UNBIND request contains the sense code %H084F0002, security component not available. Recovery. When SNAX/APC recovers automatically, no other recovery action is required. If SNAX/APC deactivates the session, examine the error number in this event. If the error number indicates a condition that can be corrected, correct the problem and try the operation again.
Event Management 40: ZAPC-EVT-SEC-SERVER-ERR SNAX/APC Configuration and Management Manual—138787 E -62
Glossary This glossary includes several definitions taken from the IBM Dictionary of Computing, IBM Network Program Products: General Information, VTAM Programming for LU 6.2, and SNA Type 2.1 Node Reference Please refer to these IBM manuals for IBM terms not included in this glossary. access method. An I/O process that allows applications running on a NonStop system to communicate with other systems or devices.
backup CPU Glossary attribute is sometimes called a modifier. (2) For the Tandem Service Management (TSM) package, a data item associated with a resource. All attributes can be viewed and some can be modified. backup CPU. The central processing unit (CPU) number of the Tandem processor on which the backup process will run. See backup process. backup process. In a Tandem NonStop system, a process that is identical to the primary process and is created at the same time as the primary process.
CNOS verbs Glossary CNOS verbs. Verbs that a control operator program uses to control the number of sessions between a pair of LUs. command file. An EDIT file that contains a series of commands and serves as a source of command input. configuration. (1) The arrangement of enclosures, system components, and peripheral devices into a working unit. (2) The definition or alteration of characteristics of an object. control operator program. For LU 6.
Distributed Systems Management (DSM) Glossary Distributed Systems Management (DSM). A set of tools used to manage Tandem NonStop systems and Expand networks. domain. A set of objects over which control or ownership is maintained. Types of domains include power domains and service processor (SP) domains. DOUT. Data transmitted from SNAX/APC. DSM. See Distributed Systems Management (DSM). dynamic.
finite state machine Glossary NonStop systems. If the network is properly designed, communication paths are constantly available even if there is a single line failure or component failure. finite state machine. An algorithm that controls the transition of an object—for example, a SNA session—between a finite number of states, each state transition being generated by one of a finite number of events. first speaker.
independent verbs Glossary independent verbs. Verbs that can be used in either basic or mapped conversations. SNAX/APC supports only GET-TYPE. interprocessor communications (IPC). The exchange of messages between processors. I/O process. A system process to manage I/O hardware. Applications use the operating system to send requests to I/O processes. IPC. See interprocessor communications (IPC). IPC version code.
LU-LU session Glossary LU-LU session. The creation of a temporary data path consisting of a physical and a logical connection between two LUs in separate domains for information exchange. To establish a data path between two LUs in separate domains for data exchange, four types of sessions must exist: SSCP-SSCP, SSCP-PU, SSCP-LU, and LU-LU. (LU, mode) pair. A specific combination of partner LU and mode. mapped conversation. In SNA, an LU 6.
NonStop operation Glossary NonStop operation. A Tandem system behavior characterized by continued operation even when a component fails, when equipment is being repaired or replaced, or while new processors or peripheral devices are being added to the system. Legally used only to describe the Tandem Nonstop system or its features, such as NonStop process pairs. Obey file. See command file. object.
PATHMON environment Glossary PATHMON environment . The servers, server classes, TCPs, terminals, SCREEN COBOL programs, and tell messages that run together under the control of one PATHMON process. Pathway. A group of software tools for developing and monitoring OLTP (on-line transaction processing) applications that use the requester/server model.
request unit Glossary request unit. In SNA, a message unit that contains control information such as a request code, or function management headers, end-user data or both. resource control block (RCB). A control block that represents the connection of a transaction program to a half-session. response unit. In SNA, a message unit that acknowledges a request unit. It may contain additional information in response to the request. return code (RC).
service transaction program (STP) Glossary service transaction program (STP). A transaction program that provides only a limited specific network function. session. In SNA, a temporary logical connection between two network addressable units for the purpose of exchanging data and control information in accordance with ground rules that have been agreed upon for that exchange. A session can be activated, tailored to provide various protocols, and deactivated, as requested. SLU.
SNALU Glossary SNALU. A SNAX/XF, SNAX/APN and SNAX/CDF programmatic interface that provides the functions of the lower two SNA layers (data link control and path control) and some functions of the transmission control layer. SNAXLink. A Tandem product comprised of both hardware and software that provides a direct channel link between a Tandem system and several types of IBM systems. SNAXLink can also be used with IBM channel-compatible systems that contain VTAM and SNA support. SPI.
SYSGEN Glossary SYSGEN. Tandem system generation program used to tailor the operating system for a specific hardware and software configuration. SYSGEN is a subset of Install that creates a system image only. The SYSGEN process can be divided into three phases: configuring the system, generating the operating system, and installing the operating system. Synchronization.
TCP Glossary TCP. See terminal control process (TCP). terminal control process (TCP). A process responsible for terminal management and transaction control, provided by Tandem as part of the Pathway/TS product. A TCP is a multithreaded process that interprets the SCREEN COBOL requester programs in the user’s application, executing the appropriate instructions for each I/O device or process the TCP is configured to handle.
VTAM Glossary VTAM. Virtual Telecommunications Access Method. WAN subsystem. See wide area network (WAN). WAN subsystem manager process. A process named $ZZWAN provided as part of the wide area network (WAN) subsystem that starts and manages the WAN subsystem objects, the WAN product process, and device objects. Subsystem Control Facility (SCF) commands are directed to the WAN subsystem manager process for configuring and managing the WAN subsystem and the ServerNet wide area network (SWAN) concentrator.
$ZZWAN Glossary SNAX/APC Configuration and Management Manual—138787 Glossary -16
Index A ABORT command All object types, generic 8-3/8-7 LU object 8-4 PTNR-LU object 8-5 PTNR-MODE object 8-5 SESSION object 8-6 TPI object 8-7 TPN object 8-7 Access Methods introduced 2-5 SNAX/XF 2-5 Access methods SNAX/APN 4-12, 8-10 SNAX/CDF 4-13, 8-10, 8-24 SNAX/XF 4-13, 8-11, 8-24 ACTIVATE_SESSION session control verb 4-18, 8-1, 8-21, 8-66, 8-68 ActvConLoser field INFO PTNR-MODE command 8-59 ActvConWinner field INFO PTNR-MODE command 8-59 ActvSessCnt field INFO PTNR-MODE command 8-60 ADD command All ob
B Index APCRUN (continuation) TRACEOPTION option 3-18 TRACEPAGES option 3-19 APCTAP 6-4 BIN and BOUT trace records 5-16 commands COUNT 5-3 DISPLAY 5-3 EXIT 5-3 FC 5-3 FROM 5-3, 5-4 GO 5-5 HEX 5-5 LENGTH 5-6 LOAD 5-6 NEXT 5-7 RANGE 5-7 RECORD 5-8 SELECT 5-9 TO 5-10 TRANSLATE 5-11 using 5-13 DIN and DOUT trace records 5-14/5-15 D-series environment 1-10, 5-1 interpreting output 5-13 introduction 5-1 starting 5-1 trace facility starting and stopping 5-1 APPC implementations 2-2 Security 2-9 APPC PC configura
C Index BACKUPCPU attribute ALTER PROCESS command 8-27 BACKUPCPU startup PARAM 3-5 BACKUPDEBUG attribute ALTER PROCESS command 8-27 BACKUPDEBUG startup PARAM 3-5 Basic conversation 8-44, 8-45, 8-62, 8-63 BFN field LISTOPENS PROCESS command 8-69 BIND requests/responses FSM status 8-95 Incoming RU size 8-62 Mode name 4-20, 8-15, 8-33, 8-57, 858 Outgoing RU size 8-63 PCID Control Vector 8-62 Rejected 8-5 Session Instance Identifier 8-62 SNA name 4-12, 4-28, 8-10, 8-13, 8-24, 8-30, 8-46, 8-47, 8-54, 8-55 Sync
C Index CHARMAPNAME, APCRUN option 3-13 CHARMAPPING attribute ADD TPN command 4-16, 8-19 ALTER TPN command 8-35 CharMapping field INFO TPN command 8-67 CICS configuration 2-6 CLEANUP, APCRUN option 3-14 Client/Server How to configure 4-7 CNOS service transaction program 8-21 CNOS verbs Allocation request draining 8-60 Number processed by SNAX/APC 8-82 Parameter settings 8-99 See also individual CNOS verbs CNOS Verbs Processed fields STATS PTNR-MODE command 8-82 COLLECTOR attribute ALTER PROCESS command 8-
D Index Configuration PARAMs (continuation) CONFIG 3-7 Cold Start 4-2 Warm Start 4-2 DATAPAGES 3-7 DEBUGONERROR 3-8 EMSSUPPRESS 3-8 LOGFILE 3-9 MAXAPPLIOSIZE 3-9 MAXINRUSIZE 3-9 MAXOPENS 3-9 MAXOUTRUSIZE 3-10 ONESTEPREAD 3-10 REMOTEATTACH 3-10 RMATTACHTIMER 3-11 SECURITYMANAGER 3-11 TRACEFILE 3-11 TRACEOPTION 3-11 TRACEPAGES 3-12 CONV Object name 7-3 Object type 7-3 Summary state 7-10 CONV Type field INFO CONV command 8-44 Conversation Count field STATUS LU command 8-86 Conversation ID field INFO SESSION
D Index Debug mode 8-27, 8-28, 8-49/8-51 Debug on Error field INFO PROCESS command 8-49/8-50 DEBUGONERROR attribute ALTER PROCESS command 8-28 DEBUGONERROR startup PARAM 3-8 Default CharMap Name field INFO PROCESS command 8-54 Default CharMap Note field INFO PROCESS command 8-54 DEFAULTMAXINRUSIZE attribute ADD PTNR-MODE command 4-20, 815 ALTER PTNR-MODE command 8-31 DefaultMaxInRUSize field INFO PTNR-MODE command 8-61 DEFAULTMAXOUTRUSIZE attribute ADD PTNR-MODE command 4-21, 816 ALTER PTNR-MODE command 8
E Index DRAINTARGET attribute STOP PTNR-MODE command 8-99 DrainTarget field INFO PTNR-MODE command 8-60 DRAIN_SOURCE_LU parameter CSL CNOS verb 8-99/8-100 RSL CNOS verb 8-5 DRAIN_TARGET_LU parameter CSL CNOS verb 8-99/8-100 RSL CNOS verb 8-5 Dynamic PTNR-LU support 4-6 Dynamic SNAXFILENAME support 4-6, 4-11 D-series environment 1-7, 1-8, 1-10 D-series systems, object naming conventions for 7-2 E EMS Event collectors 8-27, 8-52 Event suppression 8-28, 8-51 EMS Collector 1 field INFO PROCESS command 8-52 E
G Index FQPCID field INFO SESSION command 8-62 FROM, APCTAP command 5-3, 5-4 FSM error E-9 FSMs Conversation states 8-84 Session states 8-91/8-95 FSM-BIS field STATUS SESSION command 8-92 FSM-BSM field STATUS SESSION command 8-92 FSM-CHAIN-RCV field STATUS SESSION command 8-93 FSM-CHAIN-SEND field STATUS SESSION command 8-93 FSM-CONVERSATION field STATUS CONV command 8-84 STATUS SESSION command 8-93 FSM-ERROR-OR-FAILURE field STATUS SESSION command 8-93 FSM-PAC-RQ-RCV field STATUS SESSION command 8-93 FSM
K Index INITIALIZE_SESSION_LIMIT (continuati on) MIN_CONWINNERS_SOURCE parameter 4-21, 8-16, 8-32, 8-57, 8-59, 8-76 MIN_CONWINNERS_TARGET parameter 4-21, 8-16, 8-32, 8-57, 8-59, 8-76 MODE_NAME parameter 8-76 Processing count 8-82 Input source Defined 6-7 defined 6-7 Setting 6-8 Interactive mode 6-7 Interprocess Communication messages See IPC messages Introduction to SNAX/APC 1-1 IPC Messages between TP and SNAX/APC 1-7 IPC messages 8-44, 8-51, 8-64, 8-65 IPC-RETURN-CODE 8-4, 8-7 K K records editing 3-3
M Index LU 6.2 dummy 1-1/1-7, 4-2 conversations defined 1-3 data structures dynamic 2-3 static 2-1 layers 1-2 LU 6.
N Index Messages, IPC See IPC messages Messages, SPI 6-3 MINCONLOSER attribute ALTER PTNR-MODE command 8-33 MinConLoser field INFO PTNR-MODE command 8-60 MINCONWINNER attribute ALTER PTNR-MODE command 8-33 MinConWinner field INFO PTNR-MODE command 8-60 MIN_CONWINNERS_SOURCE parameter 4-21, 8-16, 8-32, 8-33, 8-57, 859, 8-76 MIN_CONWINNERS_TARGET parameter 4-21, 8-16, 8-32, 8-33, 8-57, 859, 8-76 Mode See (LU,mode) MODENAME attribute 8-42 ADD PTNR-MODE command 4-20, 815 ALTER PTNR-MODE command 8-33 Deleting
P Index Open Name field LISTOPENS PROCESS command 8-69 Open request maximum attempts 4-14, 8-11, 8-25 Opener field LISTOPENS PROCESS command 8-69 Opener process protocol interface 8-70 Operation 6-7 Operations environment, DSM 6-2 Originated field INFO TPI command 8-65 Output destinations Setting 6-8 Overview SCF 6-1/6-2 SCP 6-3 P Pacing Count - Receive field STATUS SESSION command 8-95 Pacing Count - Send field STATUS SESSION command 8-95 Pacing window 4-22, 8-17, 8-33, 8-34, 859, 8-63 PAGES attribute,
Q Index Program File Name field INFO PROCESS command 8-53 Programming considerations, event management E-7 PROTOCOL field LISTOPENS PROCESS command 8-70 PTNR-LU Object name 7-5 Object type 7-5 Summary states 7-13 PTNR-LU Name field INFO LU command 8-54 STATUS PTNR-LU command 8-89 PTNR-MODE Object name 7-6 Object type 7-6 state 8-34 Summary states 7-15 PTNR-MODE Name field INFO PTNR-MODE command 8-57 STATUS PTNR-MODE command 8-90 Q Queued Request Indicator 8-94 R RANGE, APCTAP command 5-7 RCB described 2
S Index RESET_SESSION_LIMIT Parameter settings 8-5 Processing count 8-82 Resource Control Block see RCB Resource ID field INFO CONV command 8-44 INFO TPI command 8-64, 8-65 RESPONSIBLE attribute ALTER PTNR-MODE command 8-34 STOP PTNR-MODE command 8-100 Responsible field INFO PTNR-MODE command 8-60 RESPONSIBLE parameter CSL CNOS verb 8-99 RSL CNOS verb 8-5 RESPONSIBLE parameter (CNOS) CSL CNOS verb 8-100 Responsible parameter (CNOS) 8-34, 8-100 Retry, automatic 7-12 RMATTACHDISP, APCRUN option 3-17 RMATTAC
S Index Password 2-10 SNAX/APC 2-10 Test Failures 2-13 The Security Manager 2-11 The Security Server 2-12 User ID 2-10 Security Server Process field STATUS PROCESS command 8-88 SecurityManager field INFO PROCESS command 8-51 SECURITYMANAGER startup PARAM 311 SECURITYMANAGER, APCRUN option 3-17 SECURITYREQUIRED attribute ADD TPN command 4-17, 8-21 ALTER TPN command 8-37 SecurityRequired field INFO TPN command 8-68 SEL parameter 6-5, 7-10 SELECT attribute, TRACE command 8-102 BIU option 8-103 BUFFER option
S Index Sessions (continuation) multiple defined 1-3 parallel defined 1-4 Setting the input source 6-8 Setting the output destination 6-8 SLUs 4-29, 8-14 SNA defined mode names 4-6 individual descriptions 4-23 SNANAME attribute ADD LU command 4-12, 8-10 ADD PTNR-LU command 4-28, 8-13 ALTER LU command 8-24 ALTER PTNR-LU command 8-30 SNAName field INFO LU command 8-46, 8-47 INFO PTNR-LU command 8-54, 8-55 SNASVCMG Aborting 8-5/8-6 Adding automatically 4-13, 8-11, 8-17, 8-23 Attribute settings 8-17 Default M
S Index PTNR-MODE name 8-57 running 3-4, 3-12 Security 2-10 SESSION name 8-61 starting the process 4-2 starting with TACL 3-20 starting with the PATHMON process 319 TPI name 8-64 TPN name 8-66 trace facility See APCTAP User library 8-53 using SNAX/CDF with 2-6 SNAX/APN access method 4-12, 8-10 SNAX/CDF use with SNAX/APC 2-6 SNAX/CDF access method 4-13, 8-10, 8-24 SNAX/CDF APPL object 8-24 SNAX/XF access method 4-13, 8-11, 8-24 SOURCE 8-60 specifies 3-13 SPI 6-3, 8-70 START command All object types, generi
T Index STATUS PROCESS command 8-87/888 STATUS PTNR-LU command 8-89 STATUS PTNR-MODE command 8-90 STATUS SESSION command 8-92 STATUS TPI command 8-96 STATUS TPN command 8-92, 8-97 Summary states CONV objects 8-84 LU objects 8-85/8-86 PROCESS objects 8-87/8-88 PTNR-LU objects 8-89 PTNR-MODE objects 8-90 SESSION objects 8-92 TPI objects 8-96 TPN objects 8-97 SWAP, APCRUN option 3-18 Sync Level field INFO CONV command 8-44, 8-45 Sync Level Support field INFO SESSION command 8-63 Synchronization 8-44, 8-45 Sy
U Index See APCTAP TRACE command All object types, generic 8-101/8-104 LU object 8-104 PROCESS object 8-104 Trace Facility See also APCTAP Trace facility starting and stopping 5-1 Trace File Name field STATUS LU command 8-86 STATUS PROCESS command 8-88 Trace State field STATUS LU command 8-85/8-86 STATUS PROCESS command 8-87/888 TRACEFILE startup PARAM 3-11 TRACEOPTION startup PARAM 3-11 TRACEOPTION, APCRUN option 3-18 TRACEPAGES startup PARAM 3-12 TRACEPAGES, APCRUN option 3-19 TRACE, APCRUN option 3-18
Special Characters Index ZAPC-VAL-FSM-NAMEBIS-BDR E-10 BIS-FSP E-10 BSM E-10 CHAIN-RCV E-10 CHAIN-SEND E-10 CONV E-10 ERR E-10 IRQ-MODE-R E-10 IRQ-MODE-S E-10 PAC-RQ-R E-11 PAC-RQ-S E-11 POST E-11 QRI-CHAIN-R E-11 RCB-STS-BDR E-11 RCB-STS-FSP E-11 RCV-PURGE E-11 SCB-STS-BDR E-11 SCB-STS-FSP E-11 STATUS E-11 ZAPC-VAL-INIT-ERRPARAM E-14 VALUE E-14 ZAPC-VAL-INIT-INFOINIT-BEG E-21 INIT-END E-21 RE-INIT-END E-22 ZAPC-VAL-OPERATORLOCAL-LU E-39 REMOTE-LU E-40 ZAPC-VAL-REASONUNKWN-MODENAME E-42 ZERO-SESS-LIM E-42
