SNAX/XF and SNAX/APN Configuration and Management Manual Abstract This manual describes how to configure and manage SNAX/XF and SNAX/APN communication subsystems for HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers. Product Version SNAX/XF G06 SNAX/XF H01 SNAX/APN G06 SNAX/APN H01 Supported Release Version Updates (RVUs) This manual supports the G06.25 RVU and all subsequent G-series RVUs and the H06.03 RVU and all subsequent H-series RVUs until otherwise indicated in a new edition.
Document History Part Number Product Version Published 424130-001 SNAX/XF G06.06 August 1999 425836-001 SNAX/XF G06.08 May 2000 425836-002 SNAX/XF & SNAX/APN G06.18 December 2002 425836-003 SNAX/XF & SNAX/APN G06.
Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
SNAX/XF and SNAX/APN Configuration and Management Manual Glossary Index Figures What’s New in This Manual xxi Manual Information xxi Summary of New and Changed Information Tables xxii About This Manual xxiii Who Should Use This Manual xxiii How This Manual is Organized xxiii Related Manuals xxiv Notation Conventions xxvi Part I. SNAX/XF and SNAX/APN Configuration 1. SNAX Quickstart and Overview Configuration Quick Start 1-1 Task Summary 1-1 Assumptions 1-1 Task One: Configure X.
Contents 1. SNAX Quickstart and Overview (continued) 1. SNAX Quickstart and Overview (continued) Object Names 1-17 SNAX Resource Limits 1-18 2. WAN Subsystem Objects for SNAX Processes Configuring a SWAN Concentrator 2-1 Configuring WAN Subsystem Objects for SNAX 2-2 SNAX Service Manager DEVICE Modifiers 2-5 SNAX Line Handler DEVICE Modifiers 2-7 3. SNAX/XF Primary Lines Configuring SNAX/XF Primary Lines 3-1 Primary SDLC Line 3-1 Primary Line Using an X.25 PVC 3-3 Primary Line Using an X.
Contents 6. SNAX/APN Advanced Program-to-Program Communication (APPC) (continued) 6. SNAX/APN Advanced Program-to-Program Communication (APPC) (continued) SNAX/APN APPC Using an SDLC Line 6-4 SNAX/APN APPC Using an X.25 PVC 6-6 Configuring SNAX/APC 6-8 Configuring Partner 2.1 Nodes 6-8 AS/400 6-8 SNA Subarea Network 6-9 OS/2 6-10 CICS 6-10 7.
Contents 9. Configuring for Token-Ring Support (continued) 9.
Contents 10. Configuring for Ethernet Support (continued) 10. Configuring for Ethernet Support (continued) Link-station Role Negotiation 10-15 Unique Addressing 10-15 Configuration Example 10-16 Step One: Verify the Ethernet Adapter’s LIF Status Step Two: Configure SNAX 10-16 Sample Configuration 10-17 Notes 10-18 10-16 Part II. SCF for SNAX/XF and SNAX/APN 11.
Contents 12. Objects for SNAX/XF and SNAX/APN (continued) 12.
Contents 13. SCF Commands for SNAX/XF and SNAX/APN (continued) 13. SCF Commands for SNAX/XF and SNAX/APN (continued) PRIMARY Command 13-77 SETMANAGER Command 13-78 START Command 13-81 STATS Command 13-83 STATUS Command 13-94 STOP Command 13-124 STOPOPENS Command 13-127 TRACE Command 13-129 VERSION Command 13-148 14.
Contents 14. Attributes for SNAX/XF and SNAX/APN (continued) 14.
Contents 14. Attributes for SNAX/XF and SNAX/APN (continued) 14.
Contents 14. Attributes for SNAX/XF and SNAX/APN (continued) 14.
Contents 14. Attributes for SNAX/XF and SNAX/APN (continued) 14. Attributes for SNAX/XF and SNAX/APN (continued) TYPE (PU Objects) 14-74 WINDOW 14-75 X21NRDY 14-76 X21T1TIMEOUT 14-76 X21T2TIMEOUT 14-76 X21T3ATIMEOUT 14-77 X21T3BTIMEOUT 14-77 X21T4TIMEOUT 14-77 X21T5TIMEOUT 14-78 X21T6TIMEOUT 14-78 X21T7TIMEOUT 14-78 XMITIMEOUT 14-79 XPAGES (LINE Objects) 14-79 XPAGES (SUBSYS Object) 14-80 15.
Contents 15. PTrace Reference for SNAX/XF and SNAX/APN (continued) 15.
Contents 15. PTrace Reference for SNAX/XF and SNAX/APN (continued) 15.
Contents C. Error Messages C.
Contents C. Error Messages (continued) C.
Contents C. Error Messages (continued) C.
Contents Figures (continued) Figures (continued) Figure 2-2. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 3-7. Figure 4-1. Figure 5-1. Figure 5-2. Figure 5-3. Figure 6-1. Figure 6-2. Figure 6-3. Figure 6-4. Figure 7-1. Figure 7-2. Figure 7-3. Figure 7-4. Figure 7-5. Figure 7-6. Figure 8-1. Figure 9-1. Figure 9-2. Figure 9-3. Figure 9-4. Figure 9-5. Figure 9-6. Figure 9-7. Figure 9-8. Figure 9-9. Figure 9-10. Figure 9-11. Figure 9-12. Figure 9-13. Figure 10-1.
Contents Figures (continued) Figures (continued) Figure 10-2. Figure 10-3. Figure 10-4. Figure 10-5. Figure 10-6. Figure 10-7. Figure 10-8. Figure 10-9. Figure 10-10. Figure 10-11. Figure 11-1. Figure 11-2. Figure 11-3. Figure 11-4. Figure 12-1. Figure 12-2. Figure 15-1. Figure A-1. Figure A-2. Figure A-3. Figure A-4. Figure A-5. Figure A-6. Figure A-7. Figure A-8. Figure A-9. Figure A-10. Figure A-11. Figure A-12.
Contents Tables (continued) Tables (continued) Table 1-7. Table 4-1. Table 4-2. Table 5-1. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 8-1. Table 9-1. Table 9-2. Table 10-1. Table 10-2. Table 12-1. Table 13-1. Table 13-2. Table 13-3. Table 14-1. Table 15-1. Table 15-2. Table 15-3. Table 15-4. Table B-1. Table B-2.
Contents SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 xx
What’s New in This Manual Manual Information SNAX/XF and SNAX/APN Configuration and Management Manual Abstract This manual describes how to configure and manage SNAX/XF and SNAX/APN communication subsystems for HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers. Product Version SNAX/XF G06 SNAX/XF H01 SNAX/APN G06 SNAX/APN H01 Supported Release Version Updates (RVUs) This manual supports the G06.25 RVU and all subsequent G-series RVUs and the H06.
What’s New in This Manual Manual Information Summary of New and Changed Information The revision 425836-006 contains the following changes: Updated range values for L3TIMEOUT on page 14-28, LNT1 on page 14-31,LNT2 on page 14-31 and LNTI on page 14-31. The revision 425836-004 contains these additions and changes: Section Change Section 9, Configuring for Token-Ring Support Text has been added concerning the use of the token-ring protocol by SNAX product that run on Integrity NonStop NSseries servers.
About This Manual This manual describes configuration and management of SNAX/XF and SNAX/APN, which run on HP NonStop S-series servers on G06.08 and subsequent G-series Release Version Updates (RVUs). SNAX/XF and SNAX/APN are HP access methods, supporting Systems Network Architecture (SNA) subarea networking and advanced peer-to-peer networking (APPN) respectively. SNAX/XF and SNAX/APN share a common code base and in this manual are referred to jointly as SNAX.
About This Manual Related Manuals Section Title This Section... 12 Objects for SNAX/XF and SNAX/APN Describes the types of SNAX/XF and SNAX/APN objects you can manage using SCF. 13 SCF Commands for SNAX/XF and SNAX/APN Describes the SCF commands used for SNAX/XF and SNAX/APN. 14 Attributes for SNAX/XF and SNAX/APN Describes the named, configurable characteristics of objects that can be specified as parameters to one or more of the SCF commands ADD, ALTER, and INFO.
About This Manual Related Manuals Figure i. SNAX/XF and SNAX/APN Manuals and Related Manuals Introduction to SNA Capabilities of Tandem NonStop Systems Functional Overview Configuration Prerequisites Configuring SNAX/XF and SNAX/APN ServerNet Communications Configuration and Management Manual SNAX/XF and SNAX/APN Configuration and Mgmt.
About This Manual Notation Conventions Sending an e-mail message to the address included on the form. We will immediately acknowledge receipt of your message and send you a detailed response 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. Many of the improvements you see in manuals are a result of suggestions from our customers.
About This Manual General Syntax Notation A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item.
About This Manual Notation for Messages If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
About This Manual Notation for Messages Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
About This Manual Notation for Management Programming Interfaces Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters.
Part I.
Part I.
1 SNAX Quickstart and Overview SNAX/XF and SNAX/APN are HP access methods, supporting Systems Network Architecture (SNA) subarea networking and advanced peer-to-peer networking (APPN) respectively. They share a common code base and in this manual are referred to jointly as SNAX.
SNAX Quickstart and Overview Task One: Configure X.25 Lines (if required) The ServerNet LAN Systems Access (SLSA) subsystem has been defined and started and an Ethernet 4 ServerNet adapter (E4SA) and/or Token-Ring ServerNet adapter (TRSA) has been installed and started. A NonStop TCP/IP process has been defined and started. This document assumes that the process is named $ZTC0. The WAN manager process ($ZZWAN) has been defined and started.
SNAX Quickstart and Overview Task Two: Configure WAN Subsystem Objects For SNAX 2: Add the X25AM Devices Before you add any X25AM devices, you need to verify that all processes, profiles, and the SWAN concentrator have been added and started. To add an X25AM device, you need to know the SWAN ID, CLIP number, and the line number. Also, you to verify that you have the following X25AM files: $system.sysnn.x25obj $system.cssnn.
SNAX Quickstart and Overview Task Three: Start and Set the SNAX Service Manager Task Three: Start and Set the SNAX Service Manager Use SCF commands to start the service manager and (if using multiple service managers) set the manager name assumed in subsequent SCF commands. For example: START SUBSYS $SSCP1 SETMANAGER $SSCP1 Task Four: Configure SNAX Subsystem Objects Use SCF commands to add and start SNAX LINE, PU, LU, and APPL objects.
SNAX Quickstart and Overview Task Five: Define Custom SET, ESS, and BIND Tables (if required) Figure 1-1. SNAX/XF and SNAX/APN Object Hierarchies SUBSYS Object LINE Object PROCESS Object SUBSYS Object APPL Object LINE Object PROCESS Object PU Object Switched Floating PU Object Local PU Object Remote PU Object LU Object Switched Floating LU Object Local LU Object Remote LU Object SESSION Object SESSION Object SESSION Object SNAX/XF Objects APPL Object SNAX/APN Objects VST101.vsd Notes.
SNAX Quickstart and Overview Changing SNAX Configurations Enhanced system services (ESS) table The ESS table is the NonStop equivalent to an IBM unformatted system services (USS) table. An ESS table sends messages to or interprets character strings received from SNA peripheral nodes. For example, the ESS allows SNAX to provide welcome menus and to allow character-coded logons, BIND table The BIND table is the NonStop equivalent to an IBM logon mode (LOGMODE) table.
SNAX Quickstart and Overview SNAX Lines Figure 1-2. SNAX Processes SNAX Service Manager SNAX Line Handler SNAX Line Handler SNAX Line Handler VST102.vsd Multiple service managers (and, hence, multiple SNAX subsystems) can coexist within a single NonStop system. This has distinct benefits: One NonStop system can control a large network of SNA devices.
SNAX Quickstart and Overview SNAX User Applications Table 1-2. SNAX Lines WAN Protocol Line Type Nonswitched Switched SDLC (58, 5) Dedicated physical connection Physically-switched connection X.25 (58, 3) Connection supporting permanent virtual circuits (PVCs) Connection supporting switched virtual circuits (SVCs) SNAX lines can use the following interfaces: RS-232, enabling medium-speed serial data transmission RS-422, enabling high-speed serial data transmission X.
SNAX Quickstart and Overview SNAX Connectivity The following documents contain detailed information: For the SNALU, CRT, ITI, and PRT protocols provided by SNAX/XF, see the SNAX/XF Application Programming Manual. For the SNALU, CRT, and ITI protocols provided by SNAX/APN, see the SNAX/APN Application Programming Manual. Additional high-level SNAX APIs are available as separate products: SNAX/APC facilitates writing applications for SNA LU6.2 sessions.
SNAX Quickstart and Overview SNAX/APN Connectivity Figure 1-3. SNAX/XF Connectivity SNA Host SNA Host Application Application Secondary Line NonStop System NonStop System Application SNAX/XF Line Handler Secondary Line NonStop System SNAX/XF Line Handler Application SNAX/XF Line Handler SNAX/XF Line Handler Primary Line Primary Line SNA Peripheral Node 1. Primary Line SNA Peripheral Node 2. Secondary Line 3. SNA Session Passthrough VST103.
SNAX Quickstart and Overview SNAX/APN Connectivity The NonStop node can communicate with SNA host nodes and SNA peripheral nodes (SNA type 2 or 2.1 nodes) in an attached SNA subarea network. One form of this connectivity is called the extended logon facility (XLF). To forward logon requests from the SNA subarea network to the NonStop system, the NonStop Logon Manager for IBM Systems (ILOGMGR) must be installed in an SNA host in the subarea network.
SNAX Quickstart and Overview SNAX/APN Connectivity Figure 1-4. SNAX/APN Connectivity NonStop System NonStopSystem NonStop System LU6.2 Application LU6.2 Application Application SNAX/APN Line Handler SNAX/APN Line Handler SNAX/APN Line Handler SNA Host Type 2.1 Node Network Node ILOGMGR LU6.2 Application Note: ILOGMGR is used with XLF; it is not used with ELF APPN Network SNA Subarea Network Type 2.1 Node SNA Peripheral Node LU6.2 Application 1. APPC with Attached Type 2.1 Node 2.
SNAX Quickstart and Overview Shared Lines Shared Lines SNAX/XF and SNAX/APN can share control of a multipoint line. Figure 1-5 shows an example of a shared line. For shared lines, you configure both SNAX/XF and SNAX/APN characteristics (attributes). Only those attributes that apply to SNAX/XF affect the SNAX/XF operation; only attributes that apply to SNAX/APN affect the SNAX/APN operation. Figure 1-5. Shared Line NonStop System Application SNAX Line Handler Type 2.1 Node (SNAX/APN) Appl Type 2.
SNAX Quickstart and Overview Expand over SNAX/APN Expand over SNAX/APN Using the Network Access Method (NAM) interface to SNAX/APN, Expand can establish SNA sessions across SNA networks. Figure 1-6 shows an example where this is used. Figure 1-6. Expand over SNAX/APN NonStop System Application Expand Line Handler SNAX/APN Line Handler APPN Network NonStop System SNAX/APN Line Handler Expand Line Handler NonStop Terminal VST106.
SNAX Quickstart and Overview LU-LU Session Establishment LU-LU Session Establishment LU-LU session establishment is handled differently by different SNAX API protocols: For CRT, ITI, and PRT protocols, handled by the SNAX line handler. For SNALU, handled by the application or by SNAX/HLS or SNAX/APC (when used). For SNALU/XS, handled by SNAX/APC. An LU on the NonStop system can be the primary LU (sends the BIND) or secondary LU (awaits a BIND).
SNAX Quickstart and Overview SNAX Helper Applications SNAX Helper Applications SNAX helper applications interface to the SNAX service manager. They include: LUNS applications Creator processes CNM applications SNAX Connection Manager (SNAX/CM) processes LUNS Applications On SNAX/XF primary lines and SNAX/APN XLF or ELF configurations, the SNAX service manager’s LU network services (LUNS) interface handles network services requests by using the SET, ESS, and BIND tables.
SNAX Quickstart and Overview Object Names APPL Object Types Most of these helper applications are configured as APPL objects, as listed in Table 1-5. Table 1-5. APPL Object Types Type (Integer) Type (Keyword) Description 2 (note 1) CONFIG CNM CONFIG process 3 (note 1) CNMAPPL CNM application 4 (note 1) CNMSERV CNM server 5 LUNSAPPL LUNS applications (note 2) 6 LUNSCRE Creator process (SNAX Creator-2 or original Creator) 10 CMAPPL SNAX/CM process Notes. 1.
SNAX Quickstart and Overview SNAX Resource Limits Figure 1-7. SNAX/XF Naming Example SUBSYS $SSCP LINE (Multipoint) $LINE2 LINE (Point-to-point) $LINE1 PU $LINE1.#PU1 LUs $LINE1.#LU1 $LINE1.#LU2 APPL $SSCP.#APPL1 PU $LINE2.#PU1 LUs $LINE2.#LU1 $LINE2.#LU2 APPL $SSCP.#APPL2 PU $LINE2.#PU2 LUs $LINE2.#LU3 $LINE2.#LU4 VST107.vsd SNAX Resource Limits Table 1-7 shows the logical limits constraining SNAX resources. Practical limits may be much lower. Table 1-7.
2 WAN Subsystem Objects for SNAX Processes This subsection describes how to configure SNAX service managers and line handlers through the WAN subsystem. NonStop S-Series servers communicate across wide-area networks through the ServerNet wide area network (SWAN) concentrator. The WAN subsystem provides a software interface to the SWAN concentrator. The WAN subsystem includes a WAN manager process ($ZZWAN) through which you configure some of the objects for HP wide-area communication subsystems.
WAN Subsystem Objects for SNAX Processes Configuring WAN Subsystem Objects for SNAX Figure 2-1. Configuring a SWAN Concentrator NonStop System WAN Manager $ZZWAN WAN Subsystem Objects SWAN Concentrator SWAN Concentrator Configuration ADD ADAPTER $ZZWAN.#SWAN001A , TRACKID "SWAN30" , TCPIP $ZTC1 , ALTTCPIP $ZTC0 , HOSTIP 155.186.59.103 , ALTHOSTIP 155.186.60.103 , SNMPCODE $SYSTEM.CSS00.C7849P00 , KERNELCODE $SYSTEM.CSS00.C7953P00 ADD SERVER $ZZWAN.#SWAN001A.1 ADD SERVER $ZZWAN.#SWAN001A.
WAN Subsystem Objects for SNAX Processes Configuring WAN Subsystem Objects for SNAX You use these files to define PROFILE objects in the WAN subsystem (you can optionally override the default values in the SUT file). Then, when you define DEVICE objects for the SNAX service manager and line handler processes, you associate the DEVICE object with a PROFILE object (you can again override the PROFILE values for a specific DEVICE object).
WAN Subsystem Objects for SNAX Processes Configuring WAN Subsystem Objects for SNAX Figure 2-2. Configuring WAN Subsystem Objects for SNAX NonStopSystem WAN Manager $ZZWAN SNAX Service Manager $SSCP WAN Subsystem Objects SNAX Line Handler SNAX Line Handler $SNAP1 $SOXP1 SWAN Concentrator $SNAP1 X.25 Line WAN Subsystem SCF Configuration ADD PROFILE $ZZWAN.#SMPROF , FILE $SYSTEM.SYS00.PSX1SVM ADD PROFILE $ZZWAN.#TSPROF , FILE $SYSTEM.CSS00.PSX1TS ADD DEVICE $ZZWAN.
WAN Subsystem Objects for SNAX Processes SNAX Service Manager DEVICE Modifiers Notes. 1. Include SNAX-specific modifiers on the ADD PROFILE commands to modify the values in the specified file. The SNAX-specific modifiers are described under SNAX Service Manager DEVICE Modifiers on page 2-5 and SNAX Line Handler DEVICE Modifiers on page 2-7. 2.
WAN Subsystem Objects for SNAX Processes SNAX Service Manager DEVICE Modifiers page is 1024 words. The extended data segment stores LINE, PU, and LU resource control blocks (RCBs). Pages are locked while in use. If the EXTPOOLPAGES value is too low, SCF ADD commands are rejected, error codes are returned to HP application OPEN requests, and SNA session initiation requests are rejected. In all these cases, the error code or sense code indicates lack of buffer space or resources.
WAN Subsystem Objects for SNAX Processes SNAX Line Handler DEVICE Modifiers example, if the system image was loaded from $SYSTEM.SYS01 and filename is SNXSET, SNAX searches for $SYSTEM.SYS01.SNXSETO. To change the SETTABNAME value, issue an SCF ALTER DEVICE command to the WAN subsystem; for example: STOP DEVICE $ZZWAN.#SSCP ALTER DEVICE $ZZWAN.
WAN Subsystem Objects for SNAX Processes SNAX Line Handler DEVICE Modifiers SNAX supports the following values of n: 0 - United States and Canada (American) 2 - Canada (French) 3 - User1, a table provided for custom translation 4 - User2, a table provided for custom translation 39 - Italy 43 - Austria 44 - United Kingdom 45 - Denmark 46 - Sweden 47 - Norway 49 - Germany 33 1 - France (QWERTY) 33 2 - France (AZERTY) 35 8 - Finland To change the COUNTRY value, issue
WAN Subsystem Objects for SNAX Processes SNAX Line Handler DEVICE Modifiers NT21BPAGES n Default: 0 (4000) Range: 48-4000 The value of NT21BPAGES specifies the number of pages allocated in the line handler extended segment for SNAX/APN operation. The value of 0 for NT21BPAGES results in 4000 pages being allocated for SNAX/APN, allowing more than 2000 parallel sessions without causing congestion.
WAN Subsystem Objects for SNAX Processes SNAX Line Handler DEVICE Modifiers TYPE (58,n) Default: None Values: n = 3 for X.25 lines n = 4 for Token-Ring lines n = 5 for SDCL lines n = 6 for Ethernet lines TYPE specifies the line type, 58 for all SNAX line handlers and the subtype, n that specifies the entity providing link level services to the line handler.
3 SNAX/XF Primary Lines SNAX/XF primary lines control and serve attached SNA peripheral nodes (SNA type 2.0 nodes). Connections between the NonStop node and SNA peripheral nodes can be point-to-point or multipoint. Applications on a NonStop system can use the CRT, ITI, PRT, SNALU, or SNAX/HLS APIs.
SNAX/XF Primary Lines Primary SDLC Line Figure 3-1. Primary SDLC Line NonStop System SNAX/XF SCF Configuration ADD LINE $SNAP1 $SSCP SNAX/XF Line Handler ADD PU $SNAP1.#PU1 , TYPE(13,2) , RECSIZE 265 , MAXLUS 3 , ADDRESS %HC0 $SNAP1 ADD LU $SNAP1.#LU1 , TYPE(14,2) , PUNAME #PU1 , DEVTYPE “3278-2" , RECSIZE 1920 , PROTOCOL CRT , ADDRESS 1 SWAN Concentrator SNAX/XF Primary Line ($SNAP1) PU SNA Peripheral Node LU LU ADD LU $SNAP1.
SNAX/XF Primary Lines Primary Line Using an X.25 PVC Primary Line Using an X.25 PVC Figure 3-2 shows an example of a primary line using an X.25 PVC. The SCF configuration, shown alongside, configures the X25AM LINE and SU object (representing a PVC) and the SNAX/XF LINE, PU, and LU objects. Figure 3-2. Primary Line Using an X.25 PVC NonStop System $SSCP SNAX/XF Line Handler X25AM Line Handler $SNAP2 SU $X25A ADD SU $X25A.
SNAX/XF Primary Lines Primary Line Using an X.25 SVC Primary Line Using an X.25 SVC Figure 3-3 shows an example of a primary line using an X.25 SVC. The SCF configuration, shown alongside, configures the X25AM SU object (representing an SVC) and the SNAX/XF LINE, PU, and LU objects. Figure 3-3. Primary Line Using an X.25 SVC NonStop System $SSCP SNAX/XF Line Handler X25AM Line Handler $SNAP3 SU $X25B SWAN Concentrator X25AM Line ($X25B) X.
SNAX/XF Primary Lines Switched Line Using Permanently-Subordinated PU and LU Objects Notes. 1. The X25AM SU must have PROTOCOL QLLC and DEVTYPE (58,20). 2. The SNAX/XF LINE object has SWITCHED ON. 3. ASSOCIATESUBDEV links the PU object with the SVC (SU object). 4. CALLVALIDATE BOTH on the PU object indicates validation of both the calling DTE address and the connection identifier password in incoming calls. 5. For details of the SCF attributes for X25AM, see the SCF Reference Manual for X25AM.
SNAX/XF Primary Lines Switched Line Using Switched Floating PU and LU Objects Figure 3-4. Switched Line Using Permanently-Subordinated PU and LU Objects NonStop System $SSCP SNAX/XF Line Handler $SNAP4 SNAX/XF Switched Primary Line ($SNAP4) PU LU SNAX/XF SCF Configuration ADD LINE $SNAP4 , SWITCHED ON , INTERFACE V25 , DIALTYPE INOUT , AUTOACCEPT ON ADD PU $SNAP4.#PU1 , ADDRESS %HC1 , PUIDBLK %H123 , PUIDNUM %H45670 , TYPE (13,2) , MAXLUS 8 , RECSIZE 256 ADD LU $SNAP4.
SNAX/XF Primary Lines Switched Line Using Switched Floating PU and LU Objects Figure 3-5. Switched Line Using Switched Floating PU and LU Objects NonStop System $SSCP SNAX/XF Line Handler $SNAP5 SNAX/XF Switched Primary Line ($SNAP5) PU LU SNAX/XF SCF Configuration ADD LINE $SNAP5 , SWITCHED ON , MAXPUS 1 , AUTOACCEPT ON , ESSTABLE ADD PU $SSCP.#PU1 , ADDRESS %HC1 , PUIDBLK %H123 , PUIDNUM %H45670 , TYPE (13,2) , MAXLUS 8 , RECSIZE 256 ADD LU $SSCP.
SNAX/XF Primary Lines Switched Line Controlled Through SNAX/CM Switched Line Controlled Through SNAX/CM SNAX/CM enables dynamic management of SNAX X.25 lines and additional management functions, such as call validation, by programmatic or interactive commands. Programmatic management of lines is best performed by a user-written server process. This server process might, for example, perform call validation, or start an application when a switched connection is established.
SNAX/XF Primary Lines Configuring for LU Accept SNAX/CM commands may then be used to control the line, either interactively through the SNAX/CM process or programmatically through the server process. For more information about SNAX/CM commands and the sample server process (SXCMSV), see the SNAX Connection Manager (SNAX/CM) Manual. Configuring for LU Accept LU accept means allowing remote LUs (such as SNA devices) to log on to applications on the NonStop system.
SNAX/XF Primary Lines Configuring for LU Accept Figure 3-7. LU Accept with SNAX Creator-2 NonStop System $CREA ESS Table SET Table SNAX Creator-2 Process SNAX/XF SCF Configuration ALTER SUBSYS $SSCP , SETTAB $SYSTEM.SYS01.SNXSETADD $SSCP APPL $SSCP.#cre1 , APPLTYPE LUNSCRE , PASSWORD abcdef $SNAPx ADD APPL $SSCP.#cre2 , APPLTYPE LUNSCRE , PASSWORD abcdef SNAX/XF Line Handler SNAXUTL Configuration BEGIN ADD APPL $SSCP.#cre3 , APPLTYPE LUNSCRE , PASSWORD abcdef SELECTFILE $SYSTEM.SNAX.
SNAX/XF Primary Lines Configuring CNM Applications Notes. 1. The ESS entry PLUNAME maps to the last part of the SNAX/XF APPL name and the last part of the SNAX Creator-2 SU name. With this configuration, PLUNAME values can be different in SNAX Creator-2 and SNAX/XF. 2. In the SNAX Creator-2 configuration, each SU PLUNAME maps to the last part of an APPL name, which provides the program name. 3.
SNAX/XF Primary Lines Configuring CNM Applications For more information about writing and configuring CNM applications, see the SNAX/CNM Manual.
4 SNAX/XF Secondary Lines SNAX/XF secondary lines connect a NonStop system to an SNA host (type 5 node), typically through an SNA communication controller (type 4 node). Connections between the NonStop node and SNA hosts can be point-to-point or multipoint. The NonStop system appears to the SNA host as an SNA peripheral node (type 2.0 node). Applications on the NonStop system can use the SNAX/APC, SNAX/HLS, or SNALU APIs.
SNAX/XF Secondary Lines Configuring SNAX/XF Secondary Lines Figure 4-1. Secondary Line SNA Host HOSTAPL1 HOSTAPL2 HOSTAPL3 VTAM SNA Communication Controller NCP Secondary Line ($SNAS1) SWAN Concentrator NonStop System SNAX Line Handler $SNAS1 PU LU SNAX/XF SCF Configuration ADD LINE $SNAS1 , STATION SECONDARY , APPLID (HOSTAPL1, HOSTAPL2, HOSTAPL3) ADD PU $SNAS1.#PU001 , TYPE(13,2) , RECSIZE 265 , MAXLUS 2 , ADDRESS %HC0 ADD LU $SNAS1.
SNAX/XF Secondary Lines Configuring the SNA Network Configuring the SNA Network You need to configure the NCP, NPSI (if X.25 used), and VTAM. NCP Definition In the NCP definition, include LINE, PU, and LU statements for the gateway lines, PUs, and LUs. Certain values must be consistent with the corresponding SNAX/XF object attribute values, as shown in Table 4-2. Table 4-1.
SNAX/XF Secondary Lines VTAM Activation of NonStop SNA Resources VTAM Activation of NonStop SNA Resources Issue VTAM commands to activate the gateway lines, PUs, and LUs on the NonStop system.
5 SNAX/XF Passthrough SNAX/XF passthrough allows SNA peripheral nodes on SNAX/XF primary lines to communicate with SNA hosts on SNAX/XF secondary lines. SNAX/XF makes the connection between the primary and secondary LINE, PU, or LU objects. SNAX lines, PUs, and LUs used for SNA host communication are called gateway lines, PUs, and LUs. When configured for passthrough, gateway LUs are also called passthrough LUs.
SNAX/XF Passthrough Processing Messages from SNA Peripheral Nodes Table 5-1. Types of Passthrough (page 2 of 2) Function Dynamic Associated Static Logon request format HP format HP format IBM format INIT-SELF requests flow from SNA devices to SNA host No No Yes USS messages flow from SNA host to SNA devices No No Yes In addition, SNA host applications may be configured optionally as LUNS applications (through ESS table entries). This type of configuration is called LUNS passthrough.
SNAX/XF Passthrough Configuring SNAX/XF Passthrough Figure 5-1.
SNAX/XF Passthrough Configuring SNAX/XF Passthrough $SNAS1.#PLU3 is configured for static passthrough. . Figure 5-2.
SNAX/XF Passthrough Configuring LUNS Passthrough Notes. 1. Secondary LINE objects must have STATION SECONDARY and APPLID (containing host applications you want to access from the NonStop system) 2. Passthrough LU objects must have the following attributes: PROTOCOL SNALU PASSTHRU ON ASSOCIATE (if associated or static passthrough required) STATIC ON (if static passthrough required) 3. After configuring SNAX/XF, you must still configure the gateway lines, PUs, and LUs to VTAM, NCP, and NPSI (X.
SNAX/XF Passthrough Configuring LUNS Passthrough Figure 5-3. LUNS Passthrough SNA Host HOSTAPL1 SNAXUTL Configuration BEGIN HOSTAPL2 HOSTAPL3 SELECTFILE $SYSTEM.SNAX.ESSTAB1 , TYPE ESS SNA Communication Controller VTAM ALLOCATE 10 NCP ADD ESSCMD APL1 ,SENDHOST Y ,PLUNAME HOSTAPL1 ,CMDTYPE LOGON-INIT ,GATELINE $SNAS1 Secondary Line ($SNAS1) ADD ESSCMD LOGON , SENDHOST Y , CMDTYPE LOGON-CHAR , GATELU $SNAS1.
SNAX/XF Passthrough Configuring LUNS Passthrough Notes. 1. ESS entries for host applications require the following modifiers: SENDHOST Y (to direct request to host) CMDTYPE (to specify what kind of action is required) GATELINE or GATEPU or GATELU (to instruct LUNS to use any LU on a specified line or PU or a specific LU) 2. The first ESS entry (APL1) provides dynamic passthrough between any SNA device and HOSTAPL1. The user enters APL1 at the SNA device.
SNAX/XF Passthrough Configuring LUNS Passthrough SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 5-8
6 SNAX/APN Advanced Program-toProgram Communication (APPC) SNAX/APN enables a NonStop system to function as a LEN or end node, enabling HP LUs to communicate using APPC with: LUs in directly-attached type 2.1 nodes. LUs accessible through an attached APPN network node. Note. Network nodes perform intermediate session routing and act as servers for attached nodes.
XID Validation SNAX/APN Advanced Program-to-Program Communication (APPC) Figure 6-1. Multiple and Parallel Sessions NonStop LEN Node Multiple TNLU1 Partner 2.1 Node IBMLU1 IBMLU2 Parallel TNLU2 IBMLU3 Multiple Parallel TNLU3 IBMLU4 VST601.vsd XID Validation In node type 2.1 operation, link stations send each other format 3 exchange identification information frames (henceforth called XID3 frames).
XID Validation SNAX/APN Advanced Program-to-Program Communication (APPC) Figure 6-2.
SNAX/APN Advanced Program-to-Program Communication (APPC) Configuring SNAX/APN adjacent node. The names and locations of these parameters vary by IBM system type. Note. If multiple service managers are defined in the same HP LEN node, each SNAX subsystem has the same SNANETID (since they are in the same network). Then: When the CPNAME values are the same, the subsystems are viewed from the network as one node, with two ways to access the node.
SNAX/APN APPC Using an SDLC Line SNAX/APN Advanced Program-to-Program Communication (APPC) Figure 6-3. SNAX/APN (LEN or EN) Using an SDLC Line SNAX/APN LEN Configuration NonStop System System ALTER SUBSYS $SSCP , SNANETID USPAL001 SNAX/APN EN Configuration $SSCP ALTER SUBSYS $SSCP , SNANETID USPAL001 , NODETYPE EN START SUBSYS $SSCP ADD LINE $SNAX1 , RECSIZE 524 , MAXPUS 1 , MAXLUS 30 , MAXLOCALLUS 10 , STATION NEGOTIABLE $SNAX1 LU #LLU1 SWAN Concentrator Line ($SNAX1) ADD LU $SNAX1.
SNAX/APN Advanced Program-to-Program Communication (APPC) SNAX/APN APPC Using an X.25 PVC Notes. 1. The SUBSYS object must be configured with a SNANETID value, identifying the SNA network that the NonStop node is in. 2. The LINE object always represents a connection between the NonStop node and adjacent 2.1 nodes. 3. SDLC lines can be configured with STATION PRIMARY, SECONDARY, or NEGOTIABLE (allowing the LUs to negotiate which is the primary link station at session establishment).
SNAX/APN APPC Using an X.25 PVC SNAX/APN Advanced Program-to-Program Communication (APPC) Figure 6-4. SNAX/APN APPC Using an X.25 PVC X25AM SCF Configuration ALTER LINE $X25A , PVCRANGE (1,10) , SVCRANGE (15,50) ADD SU $X25A.#SU1 , PROTOCOL QLLC , DEVTYPE (58,20) , RECSIZE 80 , PVC 1 NonStop System $SSCP SNAX/APN Line Handler X25AM Line Handler $SNAP1 LU #LLU1 SU $X25A SWAN Concentrator X25AM Line ($X25A) X.
Configuring SNAX/APC SNAX/APN Advanced Program-to-Program Communication (APPC) Notes. 1. The X25AM LINE object must be altered to allocate some PVCs. 2. The X25AM SU must have PROTOCOL QLLC, DEVTYPE (58,20), and a PVC number. 3. SNAX/APN X.25 lines must be configured with STATION either PRIMARY or SECONDARY (not NEGOTIABLE). A secondary line can have only one remote PU. 4. The ASSOCIATESUBDEV attribute links the SNAX PU object with the PVC (SU object). 5.
SNA Subarea Network SNAX/APN Advanced Program-to-Program Communication (APPC) Table 6-2.
SNAX/APN Advanced Program-to-Program Communication (APPC) OS/2 Table 6-4. Correspondences Between NPSI and SNAX/APN Values NPSI Value SNAX/APN Value PU IDBLK PU PUIDBLK PU IDNUM PU PUIDNUM PU USRFIL2 PU CALLADDR Also, in the user data field of incoming call, the CID value must match the SNAX/APN PU CONNID value.
7 SNAX/APN Dependent LU Support (XLF and ELF) Dependent LU Support enables non-LU6.2 communication between applications on an NonStop system and dependent LU devices and applications in IBM networks. SNAX/APN does not provide dependent LU support for SNA devices in HP NonStop subarea networks because SNAX/XF provides this function. A dependent LU requires the services of a System Services Control Point (SSCP) and it is controlled by an SSCP_LU session. Type 6.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Acquire Configuring for PLU Accept Using ELF Configuring for PLU Acquire You should have performed Tasks 1 through 3 of Configuration Quick Start on page 1-1. Notes. 1. A SNAX/APN line is configured as primary and nonswitched by default. For SNAX/APN, point-to-point lines also can be configured with STATION NEGOTIABLE. 2. On SNAX/APN lines, the PU and LU objects are distinguished into local and remote. 3.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Acquire Figure 7-1. SNAX/APN PLU Acquire SNAX/APN SCF Configuration ALTER SUBSYS $SSCP , SNANETID USPAL001 NonStop System $SSCP START SUBSYS $SSCP ADD LINE $SNAX1 , MAXLOCALLUS 1 $SNAX1 ADD PU $SNAX1.#RPU1 , TYPE(13,21) , RECSIZE 265 , MAXLUS 3 , ADDRESS %HC0 , SNANETID USPAL001 SWAN Concentrator Line ($SNAX1) SNA Communication Controller ADD LU $SNAX1.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring a Printer Notes. 1. The SUBSYS object must be configured with a SNANETID value that identifies the SNA network of the NonStop node. 2. The LINE object can have STATION values PRIMARY, SECONDARY, or NEGOTIABLE. 3. A remote PU object represents the PU of the adjacent node. 4. Remote LU objects represent LUs in the adjacent node or LUs accessible through that node. 5.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring a Printer Figure 7-2. Configuring a Printer NonStop System Application/ Text File Application $S Collector Process $SPLS Supervisor Process Fetch Disk $SPLB Print Process SNAX/APN Line Handler SNAX/APN SCF Configuration ALTER SUBSYS $SSCP , SNANETID USPALO01 $SNAP1 START SUBSYS $SSCP ADD LINE $SNAP1 , MAXPUS 1 , MAXLUS 30 , MAXLOCALLUS 10 , RECSIZE 524 SWAN Concentrator SNAX/APN Line ($SNAP1) SNA Communication Controller ADD PU $SNAP1.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Accept Using XLF Notes. 1. In the spooler configuration, the DEVTYPE is LU1 for printers using the SNA character string or LU3 for printers using the SNA 3270 data stream. 2. The SNAX/APN remote LU has the attribute PROTOCOL CRT because PSPOOLB operates in block mode. 3. The following examples illustrate some commands that could be used to send NonStop files (named DOC1, TEXTFILE, and MYAPPL) to the IBM printer: FUP COPY DOC1, $S.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Accept Using XLF Figure 7-3 shows an example of SNAX/APN XLF PLU accept using SNAX Creator-2 to start the CRT and ITI applications. This example applies to SNAX/APN LEN Node and End Node. Figure 7-3. SNAX/APN XLF PLU Accept with SNAX Creator-2 NonStop System SNAX Creator-2 Process $CREA $SSCP SNAX/APN $SNAX1 Line LU #TLOG Handler SNAX Creator-2 SCF Configuration ADD SU $CREA.\NODE.$SSCP.#CREATE , PASSWORD abcdef ADD APPL $CREA.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Accept Using XLF Notes. Figure 7-4 shows the name and value correspondences across products. SNAX/APN configuration. Add the following SCF objects: 1. Local LU object for each TLOGMGR with the following attributes: TYPE SNANAME PROTOCOL LOGON CREATOR (if SNAX Creator-2 is used) DLUNAME (if a remote LU object is defined for the ILOGMGR LU) PLUNAME #ZNT21 (the only value allowed). 2. Remote PU object to represent the adjacent type 2.1 node.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Accept Using XLF Figure 7-4.
SNAX/APN Dependent LU Support (XLF and ELF) Configuring for PLU Accept Using ELF Configuring for PLU Accept Using ELF PLU accept means allowing remote SLUs (such as SNA devices) to logon to PLU applications on a NonStop system. For SNAX/APN End Node using ELF, PLU accept does not require ILOGMGRs running in IBM systems and it does not require any of the ILOGMGR and TLOGMGR configuration required by XLF.
SNAX/APN Dependent LU Support (XLF and ELF) Template LUs Thus, if LOCALSNAME in the SNAX/APN configuration specifies mytacl, the corresponding APPL object in the Creator-2 configuration would be: ADD APPL $crea.C-mytacl, METHOD TACL (For more information about Creator-2 configuration, see the SNAX Creator-2 Configuration and Control Manual.) When you define a template LU under a PU, ELF attempts to create the dynamic LU and establish the LU-LU session using the PU under which the template LU is defined.
SNAX/APN Dependent LU Support (XLF and ELF) Template LUs You should have performed Tasks 1 through 3 of Configuration Quick Start on page 1-1. The two examples that follow show a SNAX/APN End Node using ELF PLU accept and SNAX Creator-2 to start the ITI application, TACL. The examples do not apply to SNAX/APN LEN Node because LEN Node does not support ELF. Figure 7-5 on page 7-12 shows a single template LU defined under the network node server PU.
SNAX/APN Dependent LU Support (XLF and ELF) Template LUs Notes. SNAX Creator-2 configuration. 1. Start the SNAX Creator-2 process; for example: RUN CREOBJ /OUT $S.#SPOOL, CPU 1, NAME $CREA, NOWAIT/ 2 , CONFIG $DATA.SXCRE.CONDATA 2. & Add the following SCF objects: An SU object (for each SNAX Creator-2 connection to SNAX/APN) An APPL object (for each NonStop application to be launched — only one is defined for this example) For more information, see the SNAX Creator-2 Configuration and Control Manual.
SNAX/APN Dependent LU Support (XLF and ELF) Template LUs Figure 7-6 shows two template LUs configured through SCF under two different PUs. Neither PU is the network node server PU. In this configuration, subsequent sessions are established under the PUs to which the template LUs are subordinated. Figure 7-6.
8 Expand over SNAX/APN Lines Using the Network Access Method (NAM) interface to SNAX/APN, Expand can establish SNA sessions across SNA networks. This section discusses: Configuring SNAX/APN Configuring Expand Configuring the SNA network Configuring SNAX/APN Figure 8-1 on page 8-2 shows an example of using Expand over SNAX/APN lines.
Expand over SNAX/APN Lines Configuring SNAX/APN Figure 8-1. Expand over SNAX/APN Lines NonStop System \A Application Expand Line Handler SNAX/APN Line $SNAPA Handler SWAN Concentrator SNAX/APN Line ($SNAPA) SNA Network SNAX/APN Line ($SNASB) SWAN Concentrator NonStop System \B $SNASB SNAX/APN Line Handler Expand Line Handler Terminal SCF Configuration for \A ADD LINE $SNAPA , RECSIZE 524 , MAXPUS 1 , MAXLUS 30 , STATION PRIMARY , MAXLOCALLUS 10 , POLLINT 0.01 ADD LU $SNAPA.
Expand over SNAX/APN Lines Configuring Expand Notes. The following apply to local LU object attributes: 1. PROTOCOL NAM is required. 2. The local LU SNANAME on system \A must match the remote LU SNANAME on system \B (and vice versa). 3. If the local LU is to initiate sessions, DLUNAME must be defined (matching the last part of the remote LU object name). If the remote PU has DYNAMIC ON, remote LUs will always be able to initiate sessions.
Expand over SNAX/APN Lines Configuring the SNA Network Table 8-1. Correspondences Between SNA Subarea Network and SNAX/APN (page 2 of 2) SNA Network Value SNAX/APN Value LU name in NCP major node defining system \B Local LU SNANAME on system \B CDRSC name in VTAM CDRSC major node defining system \A Remote LU SNANAME on system \B RUSIZES values in default LOGMODE entry for secondary LU Must be greater than or equal to SNAX/APN BIND bytes 10 and 11 (RUSIZES values).
9 Configuring for Token-Ring Support This section shows SNAX/APN users what is required to configure a NonStop system for communication through a Token-Ring LAN, and includes information about: Uses for Token-Ring Networks which outlines the principle ways you can use the SNAX/APN implementation of Token-Ring. The Architecture of Token-Ring Networks which introduces the concepts of tokens, protocol layers, service access points, and link stations.
Configuring for Token-Ring Support File Transfer in the Data Center File Transfer in the Data Center A significant number of NonStop systems are co-located with IBM mainframes in the corporate data center. A typical requirement is for high-speed connectivity to allow bulk file transfer between HP and IBM equipment. Token-Ring, running at either 4 Mbps (where 1 megabit is 1,000,000 bits) or 16 Mbps, is often used as the link between mainframes because of its throughput potential. Figure 9-1.
Configuring for Token-Ring Support Access to SNA Devices Access to SNA Devices Applications on an NonStop system can initiate LU-LU sessions with SNA devices located in a subarea network, and by using either XLF or ELF, SNA devices located in a subarea network can initiate LU-LU sessions with applications on an NonStop system.
Configuring for Token-Ring Support Client/ Server Connections in the Corporate Network Client/ Server Connections in the Corporate Network Token-Ring LANs can be used to connect end-user devices to SNAX/APN. Token-Ring LANs, connected by bridges and routers, form the high-speed, mission-critical segments of corporate WANs. Figure 9-3. NonStop System as a Workstation Client/Server NonStop System AS/400 System Ring A Ring B Workstations or 3270 Devices VST903.
Configuring for Token-Ring Support Multipurpose Configuration Multipurpose Configuration In a Token-Ring network, a NonStop system can communicate with a variety of devices and perform a variety of functions over the same SNAX/APN line. It can support parallel LU-LU sessions, communicate with SNA terminals through XLF and function as a workstation server. For the sake of clarity, Figure 9-4 shows SNAX/APN performing each of these functions with a separate remote node.
Configuring for Token-Ring Support The Architecture of Token-Ring Networks The Architecture of Token-Ring Networks A Token-Ring network is a type of local area network suitable for high-speed interconnection of computers and computer-controlled devices over moderate distances. The actual distance depends on cable type and line drivers. A Token-Ring LAN is a star-wired ring in which each station is attached to a nearby concentrator.
Configuring for Token-Ring Support Token Control of the Ring Figure 9-5. Token Control of the Ring A A C B D D B Step 1 Step 2 C C C A D A B Step 3 C D B Step 4 C C VST905.vsd The description given previously covers the simplest case of token control. There are other considerations—timing, priority setting, and early release. There are a number of sets of timers used to monitor a station’s performance on the ring.
Configuring for Token-Ring Support Data Rates and Data Throughput a NonStop system have the priority setting of zero. There is no current method that allows an individual application to change this priority level. The early token release feature, incorporated in the IEEE 802.5 standard, enhances the original token-ring architecture by allowing multiple frames on a ring at the same time.
Configuring for Token-Ring Support The IEEE Specifications The IEEE has also defined an internetworking and network management standard (802.1), and a logical link control standard (802.2). HP’s support for Token-Ring is primarily concerned with LLC (802.2) and Token-Ring (802.5) standards. The (802.2) LLC Services The LLC layer is involved with links between network entities; in the case of Token-Ring, these are links between stations on the ring.
Configuring for Token-Ring Support The IEEE Specifications Figure 9-6. The IEEE 802 Model OSI Model IEEE 802 Model IEEE 802.1 Higher-Level Interface Higher Layers IEEE 802.2 Logical Link Control (LLC) Type 1 Connectionless Datagram Type 2 Connection Oriented Type 3 Acknowledged Datagram Data Link Layer IEEE 802.3 CSMA/CD Medium Access Physical Layer CSMA/CD Medium IEEE 802.4 Token-Bus Medium Access Token Bus Medium IEEE 802.5 Token-Ring Medium Access Token Ring Medium VST906.
Configuring for Token-Ring Support The IEEE Specifications Figure 9-7 shows the relationship of the three IEEE-defined Token-Ring layers compared to the ISO and SNA models. Figure 9-7.
Configuring for Token-Ring Support SAPs and Link Station Addresses SAPs and Link Station Addresses In Token-Ring architecture (and other 802 access methods), service access points (SAPs) are the interfaces between the LLC layer and the user application in the upper layers, as shown in Figure 9-8 on page 9-13. Each SAP provides services related to the type of protocol stack it supports, identifying the client layer to the lower layers and indicating the format of the data passed between the layers.
Configuring for Token-Ring Support SAPs and Link Station Addresses Figure 9-8. SAPs and Link Stations User Application Protocol Stack Protocol #2 Stack Protocol #2 Stack #2 Protocol Stack #1 SAP 1 Link Stations SAP 2 Logical Link Control Medium Access Control Physical VST908.
Configuring for Token-Ring Support SAPs and Link Station Addresses Figure 9-9 shows three stations (A, B, and C) connected on a Token-Ring. Station A has SAP A1 that is connected to SAP B1 of Station B. Station B has three active SAPs. SAP B2 has two connections, one with SAP C1 and one with SAP C2. SAP B3 is also connected to SAP C1. What Figure 9-9 does not show is multiple connections between the same two MAC SAPs. For example, SAP B2 cannot have two sessions with SAP C1.
Configuring for Token-Ring Support Types of Conversation Types of Conversation Transmissions over Token-Ring occur in one of two modes; they are either connectionless or connection-oriented. Connectionless (or datagram) transmission means that the Data Link Control component of a sending station does not keep any state information about the data being sent and does not ensure that the data was successfully received in the correct order by the destination station.
Configuring for Token-Ring Support Description of Frames Figure 9-10. LLC Protocol Data Unit DSAP SSAP Control Data D D D D D D U I/G S S S S S S U C/R Information Supervisory Unnumbered VST910.vsd The LPDU is created by the LLC layer. The destination SAP (DSAP) consists of a six-bit address, a seventh bit (U) for a user-defined address, and an eighth bit that specifies whether this is an individual (0) or group (1) address.
Configuring for Token-Ring Support Description of Frames The LPDU is passed from the LLC layer down to the MAC layer. At this layer, the MAC header and trailer is attached, as illustrated by the data frame in Figure 9-11. Figure 9-11. The MAC Frame The Free Token SD AC ED The Data Frame SD AC FC DA SA RI LPDU FCS ED FS DA SA RI MAC FCS ED FS The MAC Frame SD AC FC VST911.
Configuring for Token-Ring Support The HP Implementation The HP Implementation Configuration of resources for Token-Ring support must be done using SCF or an SPI application. To define SNAX/APN Token-Ring resources, additional attributes, modified attributes, or both for the SCF ADD and ALTER LINE, PU, and LU commands must be supplied. Most of the parameters are optional and default to an acceptable value. All the relevant SCF commands are detailed in this section.
Configuring for Token-Ring Support Line Attributes Figure 9-12. From The Adapter To SNAX SNAX Service Mangager SNAX Line Handler Process PAM SLSA Token Ring Adapter VST912.
Configuring for Token-Ring Support Link Station Role Negotiation You may change any one or more of the settings in order to optimize performance. You are advised not to override the defaults without a careful study of the traffic and the types of applications using the processes. The following example shows a single SAPINFO attribute with two SAPs defined. SAPINFO (SAP %H04, MAXLS 20, DFT 30.
Configuring for Token-Ring Support Required Remote PU Attributes Table 9-2. Renamed Token-Ring SCF Attributes Token-Ring Attribute Ethernet and Token-Ring Attribute TRT1 LNT1 TRT2 LNT2 TRTI LNTI To provide backward compatibility with existing configurations, the replaced token-ring attributes will be accepted by SCF, but you are encouraged to use the newer names for new and altered configurations.
Configuring for Token-Ring Support Unique Addressing Figure 9-13. SAP and PU Addressing Station A LU1 LU2 LU3 PU1 PU2 SAP %H04 MAC 400011110001 Station B PU3 %H04 PU4 %H08 400011110002 The Ring VST913.vsd In SNA terms, the link station is the equivalent of a PU. Consider the addressing used to create a connection between PU1 and PU3. The address of PU1 is its SAP/MAC address, in this case 0440001111000,1 and the address of PU3 is 04400011110002.
Configuring for Token-Ring Support Optional Remote PU Attributes Optional Remote PU Attributes Following are the optional PU attributes that support Token-Ring connections; you can specify them or allow them to default: LNMAXIN LNMAXOUT LNMAXOUTINCR LNMAXRETRY LNT1 LNT2 LNTI The Acknowledgments discussion below discusses the use of LNMAXIN, LNMAXOUT, LNMAXOUTINCR, and LNMAXRETRY. The LAN Activity discussion below discusses the use of LNT1, LNT2, and LNTI.
Configuring for Token-Ring Support Remote PU Attributes With Token-Ring Specific Values LAN Activity The PU attributes, LNT1, LNT2, and LNTI may be used to monitor activity on the ring. Depending upon the traffic pattern and types of applications running on your TokenRing LAN, you may want to optimize these values.
Configuring for Token-Ring Support Step One: SLSA Configuration Step One: SLSA Configuration Background To configure the SLSA subsystem, you need to write a command file to configure the adapter, or modify the configuration file that is shipped with your system. Related Manuals The following manual contains conceptual information and SCF command references: LAN Configuration and Management Manual Example Configuration Step One: Add the Adapter and Start It.
Configuring for Token-Ring Support Step Two: PAM Configuration configuration. You may change the PIF defaults by using the SCF ALTER PIF command. Step Two: PAM Configuration Background PAM may be started through the persistence manager, or through a TACL RUN command. The example below uses TACL. A PAM process is associated with a LIF of the SLSA subsystem - in a one-to-one relationship. The LINE and PROCESS objects share the same name.
Configuring for Token-Ring Support Notes Step Four: Start the MSAP Object When PAM is started, the MSAP.#SNATR object is added automatically. By default (MSAPSTARTUP) the object is also brought up in a STARTED state. If you specified MSAPSTARTDOWN in the RUN command you must start the MSAP object. START MSAP $PAM1.#SNATR Notes 1. The PAM process must run in the same CPUs as the SLSA subsystem because both are clients of the QIO subsystem that controls access to ServerNet. 2.
Configuring for Token-Ring Support Notes Step Two: Add the Device and Start It ADD DEVICE #TRS1, PROF TSPROF, CPU 2, ALTCPU 3,& IOPOBJECT $SYSTEM.[sysnn].SNATSOBJ, TYPE (58,4), RECSIZE 128 START DEVICE $ZZWAN.
10 Configuring for Ethernet Support This section shows SNAX users what is required to configure a NonStop system for communication through an Ethernet LAN, and includes information about: The Architecture of Ethernet Networks which introduces the concepts of protocol layers, service access points, and link-stations. This background information is necessary for understanding the line and physical unit (PU) attributes used to configure Ethernet support.
Configuring for Ethernet Support File Transfer in the Data Center File Transfer in the Data Center A significant number of NonStop systems are co-located with IBM mainframes in the corporate data center. A typical requirement is for high-speed connectivity to allow bulk file transfer between HP and IBM equipment. Often, Ethernet is used as the link between mainframes because of its throughput potential. Figure 10-1 shows a major difference between token-ring and Ethernet.
Configuring for Ethernet Support Access to SNA Devices Access to SNA Devices Applications on a NonStop system can initiate LU-LU sessions with SNA devices located in a subarea network, and by using either XLF or ELF, SNA devices located in a subarea network can initiate LU-LU sessions with applications on a NonStop system.
Configuring for Ethernet Support Multipurpose Configuration Multipurpose Configuration In an Ethernet network, a NonStop system can communicate with a variety of devices and perform a variety of functions over one SNAX line. For example, SNAX/APN can support parallel LU-LU sessions, communicate with SNA terminals, and function as a workstation server. Figure 10-3 shows SNAX/APN performing each of these functions with a separate remote node.
Configuring for Ethernet Support The IEEE Specifications 802.5—a ring topology using a token-passing access method The IEEE also defined an internetworking and network management standard (802.1), and a logical link control standard (802.2). NonStop support for Ethernet is concerned with LLC (802.2) and CSMA/CD (802.3) standards. The (802.2) LLC Services The LLC layer concerns links between network entities; in the case of Ethernet, these are links between stations in the network.
Configuring for Ethernet Support The IEEE Specifications Figure 10-4. The IEEE 802 Model OSI Model IEEE 802 Model IEEE 802.1 Higher-Level Interface Higher Layers IEEE 802.2 Logical Link Control (LLC) Type 1 Connectionless Datagram Type 2 Connection Oriented Type 3 Acknowledged Datagram Data Link Layer IEEE 802.3 CSMA/CD Medium Access Physical Layer CSMA/CD Medium IEEE 802.4 Token-Bus Medium Access Token Bus Medium IEEE 802.5 Token-Ring Medium Access Token Ring Medium VST1004.
Configuring for Ethernet Support The IEEE Specifications Figure 10-5 shows the relationship of the three IEEE-defined Ethernet layers compared to the ISO and SNA models. Figure 10-5.
Configuring for Ethernet Support SAPs and Link-station Addresses SAPs and Link-station Addresses In Ethernet architecture (and other 802 access methods), service access points (SAPs) are the interfaces between the LLC layer and the user application in the upper layers, as shown in Figure 10-6 on page 10-9. Each SAP provides services related to the type of protocol stack it supports, identifying the client layer to the lower layers and indicating the format of the data passed between the layers.
Configuring for Ethernet Support SAPs and Link-station Addresses Figure 10-6. SAPs and Link-stations User Application Protocol Stack Protocol #2 Stack Protocol #2 Stack #2 Protocol Stack #1 SAP 1 Link Stations SAP 2 Logical Link Control Medium Access Control Physical VST1006.vsd Figure 10-7 on page 10-10 shows three stations (A, B, and C) connected on an Ethernet LAN. Station A has SAP A1 that is connected to SAP B1 of Station B. Station B has three active SAPs.
Configuring for Ethernet Support Types of Conversation Figure 10-7. SAPs and LLC Connections Station B Station A SAP A1 B1 B2 B3 Station C C1 C2 LLC MAC VST1007.vsd For a further discussion about SAPs, see Figure 10-11 on page 10-15 and Unique Addressing on page 10-15. Types of Conversation Transmissions over Ethernet occur in one of two modes; they are either connectionless or connection-oriented.
Configuring for Ethernet Support Description of Frames Description of Frames At the E4SA, FESA, GESA, or G4SA adapter, data and SDLC control information are encapsulated in a data frame suitable for transport on the Ethernet LAN. SNAX supplies the information for the source and destination SAPs, and the destination MAC address. The first part of the encapsulation is to create the link protocol data unit (LPDU), shown in Figure 10-8. Figure 10-8.
Configuring for Ethernet Support The HP Implementation on NonStop Systems The unnumbered field is used for establishing and disconnecting the data link. The LPDU is passed from the LLC layer down to the MAC layer. At this layer, the MAC header and trailer is attached, as illustrated by the data frame in Figure 10-9. Figure 10-9. The MAC Frame Types The Data Frame SFD DA SA LL LPDU FCS LL MAC FCS The MAC Frame SFD DA SA VST1009.
Configuring for Ethernet Support The HP Implementation on NonStop Systems Table 10-2.
Configuring for Ethernet Support Configuring SNAX for Ethernet cannot have an ASSOCIATESUBDEV value that has already been defined for another PU known to that service manager. If your system has more than one service manager process, the same ASSOCIATESUBDEV value could be used, but only on PUs defined subordinate to different service managers. Like token-ring, the Ethernet SCF PU attribute CALLVALIDATE supports the values NONE and CALLADDR; it does not support the values CONNID or BOTH.
Configuring for Ethernet Support Link-station Role Negotiation Link-station Role Negotiation SNAX allows you to specify STATION NEGOTIABLE on lines connected to an Ethernet network. Role negotiation is implemented using SNA XID exchanges and SNAX negotiates with the remote link-station to determine which station will assume the primary role and which station will assume the secondary role.
Configuring for Ethernet Support Configuration Example example, PU2, that has an address of 04400011110001 must be connected to PU4 through SAP %H08, the unique address being 04400011110001,08400011110002. Note that these restrictions apply only to PU-to-PU connections. There may be many LU-LU sessions channelled through a single PU, and LU6.2 further allows multiple parallel sessions between two LUs. Configuration Example SNAX does not directly control the Ethernet ServerNet adapter.
Configuring for Ethernet Support Sample Configuration The example shows the configuration of the following SNAX SCF objects; LINE, PUs, and LUs. Sample Configuration Step One: Add the SNAX Profiles Your first command sends all subsequent commands to the WAN subsystem. The file PSX1SVM is the service manager profile, PSX1TS is the line handler profile. ASSUME SUBSYS $ZZWAN ADD PROFILE $ZZWAN.#SMPROF, FILE $SYSTEM.[sysnn].PSX1SVM ADD PROFILE $ZZWAN.#TSPROF, FILE $SYSTEM.[sysnn].
Configuring for Ethernet Support Notes Notes 1. In Step Two, TYPE (58,6) refers to the Ethernet adapter. 2. This example does not take you all the way from the base SNAX product to your eventual application program. It is quite possible that you will continue by using the higher-level product SNAX/APC for LU6.2 conversations. 3.
Part II.
Part II.
11 Introduction to SCF for SNAX/XF and SNAX/APN This manual describes the subsystem-specific details for using the Subsystem Control Facility (SCF) interactive interface to configure and control the SNAX/XF (SNAX Extended Facility) and SNAX/APN (SNAX Advanced Peer Networking) products. SNAX/XF provides a NonStop system with the capability to do the following: Interface to Systems Network Architecture (SNA) type 2.0 nodes Interface to SNA hosts (type 5.
Introduction to SCF for SNAX/XF and SNAX/APN Configuration Prerequisites Allow or prevent application opens of specified LUs or groups of LUs Take traces of service manager and line handler processes Define which line-handler process of a NonStop process pair is the primary process Stop lines, PUs, LUs, and active sessions between LUs, either in an orderly manner or abruptly in case of an emergency Configuration Prerequisites Before you can use SCF to configure and control a SNAX/XF or SNAX/APN
Introduction to SCF for SNAX/XF and SNAX/APN SCF and the SNAX/XF and SNAX/APN Subsystems SCF and the SNAX/XF and SNAX/APN Subsystems A SNAX subsystem consists of a service-manager process and one or more linehandler processes, all residing on a single NonStop system (node). The service manager performs a subset of the functions of the SNA system services control point (SSCP). The line-handler processes implement line-specific protocols. A single service manager can manage SNAX/XF and SNAX/APN.
Introduction to SCF for SNAX/XF and SNAX/APN SCF Interface to SNAX/XF and SNAX/APN SCF Interface for NonStop S-Series Servers SCF commands directed to SNAX/XF and SNAX/APN are sent to an intermediate process called the Subsystem Control Point (SCP) process, In turn, SCP routes the SCF commands to the WAN Manager process within the WAN subsystem, as shown in Figure 11-1.
Introduction to SCF for SNAX/XF and SNAX/APN SCF Interface to SNAX/XF and SNAX/APN Figure 11-2. An SCF Command With Dynamic Effect Terminal 1. ADD LINE $SNAP1 SNAX Subsystem Line Handler Process VST1102.vsd Persistent changes to a SNAX subsystem must be sent through the WAN subsystem. The WAN subsystem stores the changes, additions or deletions in the configuration data base, and thus the modified configuration is available any time the SNAX subsystem is restarted.
Introduction to SCF for SNAX/XF and SNAX/APN Distributed Systems Management (DSM) Distributed Systems Management (DSM) This subsection gives you a brief introduction to the Distributed Systems Management (DSM) environment for NonStop systems. For more information, see the manual, Introduction to Distributed Systems Management (DSM). If you are already familiar with DSM and SCF, you can proceed to Section 12, Objects for SNAX/XF and SNAX/APN.
Introduction to SCF for SNAX/XF and SNAX/APN DSM and SCF Commands DSM and SCF Commands SCF is a DSM tool in the operations environment. It is a unified command interface that simplifies the tasks of configuring, controlling, and collecting information about NonStop subsystems. Several SCF commands are available for displaying and changing SCF session parameters. For example, the OUT command controls the files used for display output. The ASSUME command sets the default object type and object name.
Introduction to SCF for SNAX/XF and SNAX/APN SNAX/XF and SNAX/APN Objects For SCF commands that pertain to an object, the keyword is followed by an object type and an object name. For example, the following command deletes the physical unit (PU) object named $SNAP1.#PU2: DELETE LINE $SNAP1.#PU2 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/XF and SNAX/APN How SCF Works SNAX/XF and SNAX/APN Object States Each object has an operational state, such as STOPPED or STARTED. The set of states an object can assume varies depending on the object type. Some subsystem objects are always in the same state: for example, a SNAX/XF SESSION object is always in the STARTED state. The operational state of an object can affect the use of SCF commands to operate on the object.
Introduction to SCF for SNAX/XF and SNAX/APN Running SCF The SCF Reference Manual for G-series RVUs describes how to run SCF. SCF performs most commands in the following sequence: 1. When SCF receives a command, it interprets the command and performs the steps necessary to execute it. Some commands can be handled by SCF with no interaction with SCP (for example, OUT). 2.
12 Objects for SNAX/XF and SNAX/APN This section describes the types of SNAX/XF and SNAX/APN objects, outlines their hierarchical relationships to each other, and provides a detailed description of each object type and object state. Hierarchy of Object Types Figure 12-1 shows the SNAX/XF object types supported by SCF and their hierarchical relationships. The individual object types and their positions in the hierarchy are described in the following subsections. Figure 12-1.
Objects for SNAX/XF and SNAX/APN Object Types and Object Names Figure 12-2. SNAX/APN Object Hierarchy SUBSYS LINE APPL Local PU (#ZNT21) Remote PU Local LU Remote LU SESSION SESSION VST1202.vsd Note. Line-handler process (PROCESS) objects do not appear in SCF displays as part of the object hierarchy. The PROCESS object type is provided for special purposes only, as described later in this section.
Objects for SNAX/XF and SNAX/APN Operating on Multiple Objects Operating on Multiple Objects SNAX/XF and SNAX/APN do not support wild-card characters (* or ?) in object names. However, most SCF commands for SNAX/XF and SNAX/APN allow you to specify multiple object names in a single command. APPL Objects An APPL object allows an application process of a given type to open the servicemanager process.
Objects for SNAX/XF and SNAX/APN Object States For example, the following are valid APPL object names: $SSCP.#CMAPPL1 $SSCP1.#CNMA $SSCP.#CREATE Object States APPL objects have a different set of states than do other types of SNAX/XF and SNAX/APN objects. An APPL object can be in one of three states: INACTIVE, CONNECTED, or OPENED. These object states are described later in this section. LINE Objects SNAX LINE objects represent either an SDLC line or an X.25 virtual circuit.
Objects for SNAX/XF and SNAX/APN LU Objects LU Objects An LU object refers to an SNA logical unit, sometimes referred to as a local LU in the NonStop node, and a remote LU if in another node. When SNAX/APC is used with SNAX/APN for Advanced Program-to-Program Communication (APPC), an LU can support one or more sessions. SNAX/XF LU Objects SNAX/XF LU objects can be subordinate to either a LINE object or the SUBSYS object.
Objects for SNAX/XF and SNAX/APN Object States However, if LUs on a NOnStop system are to initiate sessions with LUs in an adjacent node or network, remote LU objects must be explicitly defined. A remote LU object is created when the name of a remote PU is specified in the PUNAME attribute. When you use XLF for remote device logon, you can configure a remote LU object to represent the HP NonStop Logon Manager (ILOGMGR) for IBM systems. However, you need not do so.
Objects for SNAX/XF and SNAX/APN Naming Conventions The PROCESS object is provided because the BOOT, PRIMARY, and SWITCH commands apply to the line-handler process (PROCESS) and not to the logical line (LINE). PROCESS objects do not appear in SCF displays as part of the object hierarchy. Naming Conventions The PROCESS object name must match the name of a line-handler process defined through the SCF ADD DEVICE command.
Objects for SNAX/XF and SNAX/APN Naming Conventions Local PU Object You cannot use SCF to define a local PU object. A PU object, named #ZNT21, is automatically added for SNAX/APN lines. Although you cannot use SCF to add or alter this PU object, you can issue a STOP or ABORT command to stop it and then restart it with a START command. You can also issue INFO PU, STATS PU, and STATUS PU commands to inquire about it (for example, INFO PU $L1.#ZNT21) and to reset its statistics counters.
Objects for SNAX/XF and SNAX/APN Object States Object States A PU object can be in one of five states: ABORTING, STARTED, STARTING, STOPPED, or STOPPING. These object states are described later in this section. SESSION Objects For SNAX/XF and SNAX/APN, a SESSION object is a non-configured object. A session refers to a temporary logical connection between two SNA components. The only types of sessions supported by SNAX/XF and SNAX/APN are sessions between two LUs (LU-LU sessions).
Objects for SNAX/XF and SNAX/APN Object States Object States A SESSION object is always in the STARTED state. This state is described later in this section. SUBSYS Object The SUBSYS object type is used when attributes of a SNAX/XF and SNAX/APN service-manager process need to be added or modified. It is also used for inquiry about the subsystem and its subordinate objects, as with the INFO, STATS, or STATUS commands.
Objects for SNAX/XF and SNAX/APN States for APPL Objects States for APPL Objects APPL objects have a different set of states than do other types of SNAX/XF and SNAX/APN objects. The following paragraphs define the states that apply to APPL objects. CONNECTED For SNAX/XF, an APPL object is in the CONNECTED state if an application has successfully established a connection to it, including password verification if necessary.
Objects for SNAX/XF and SNAX/APN States for Other Types of Objects SUBSYS X LINE X Local PU X STOPPING STOPPED STARTING STARTED DIAGNOSING ABORTING Table 12-1. States Applicable to SUBSYS, LINE, PU, LU, SESSION, and PROCESS Objects X X X X X X X X X X Local LU X X Remote PU X X Remote LU X X SESSION X PROCESS X X X X X X The following paragraphs define these object states.
Objects for SNAX/XF and SNAX/APN States for Other Types of Objects STARTED When an object is in the STARTED state, it either is ready to accept user data traffic or is in the process of handling user data traffic. The STARTED state applies to LINE, LU, and PU objects that have been defined through the ADD command and initialized with the START command, and to SUBSYS objects that have been initialized with the START command. SESSION and PROCESS objects are always in the STARTED state.
Objects for SNAX/XF and SNAX/APN States for Other Types of Objects SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 12-14
13 SCF Commands for SNAX/XF and SNAX/APN This section provides a quick reference to the syntax and semantics of the SCF commands for SNAX/XF and SNAX/APN. Only those commands that operate on SNAX/XF and SNAX/APN subsystem objects are described in this section; commands such as OUT, ASSUME, ENV, and HELP are described in the SCF Reference Manual for G-series RVUs. Commands and Object Types Table 13-1 lists the SCF commands for SNAX/XF and SNAX/APN and the object types that apply to each command.
SCF Commands for SNAX/XF and SNAX/APN Command Descriptions Command Descriptions The remainder of this section describes the SCF commands that operate on SNAX/XF and SNAX/APN subsystem objects. It defines the function of each command, gives the command syntax, provides any special considerations, and gives examples. The command descriptions are given in alphabetic order. Note.
SCF Commands for SNAX/XF and SNAX/APN ABORT Command ABORT Command The ABORT command forces objects into the STOPPED state without regard to any current activity. It is a sensitive command. ABORT [ / OUT file-spec / ] { { { { { { APPL LINE LU PU SESSION SUBSYS } } } } } } { object-name } { ( object-name [, object-name ]... ) } [, SUB [ subtype ] ] [, SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN ABORT Command General Considerations The object-name sess-name is a 16-digit, hexadecimal, fully qualified procedure correlation identifier (FQPCID).
SCF Commands for SNAX/XF and SNAX/APN ABORT Command If the TLOGMGR LU has an active session with the ILOGMGR LU on the IBM system when an ABORT LU command is issued to the TLOGMGR LU: The session between the TLOGMGR LU and the ILOGMGR LU terminates. The TLOGMGR LU is put in the STOPPED state. Any queued session requests from the ILOGMGR LU that are pending are terminated. However, any existing sessions to the remote LUs that represent the terminals are not affected.
SCF Commands for SNAX/XF and SNAX/APN ADD APPL Command ADD APPL Command The ADD APPL command configures an APPL object within the SNAX/XF and SNAX/APN subsystems. It is a sensitive command. ADD [ / OUT file-spec / ] APPL object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is one of the following (items not in square brackets are required): For SNAX/XF: APPLTYPE { [ ( ] integer [ , integer , ... ] [ ) ] } { [ ( ] name [ , name , ...
SCF Commands for SNAX/XF and SNAX/APN ADD APPL Command Considerations No more than 100 APPL objects can be configured under one SUBSYS object (one service manager); this limit includes both SNAX/APN and SNAX/XF APPL objects if the service manager is used to manage both products. The application cannot use the specified subdevice name to open the service manager until the ADD command adding the APPL object has been processed.
SCF Commands for SNAX/XF and SNAX/APN ADD LINE Command ADD LINE Command The ADD LINE command configures a LINE object within the SNAX/XF and SNAX/APN subsystems. It is a sensitive command. ADD [ / OUT file-spec / ] LINE object-name [ , LIKE object-name ] [ , attribute-spec ]... OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name.
SCF Commands for SNAX/XF and SNAX/APN IOPAGES SNRMIFDM MAXLUS SUPFCSERRMSG MAXPUS TIMEOUT POLLINT WINDOW RECSIZE XMTTIMEOUT RETRIES XPAGES You can also specify any SNAX/XF attribute for the LINE object. However, note the following: ADD LINE Command SNAX/APN cannot share a switched line. Thus, no switched line attributes apply to a shared line. SNAX/APN does not support SNAXLink lines and, therefore, cannot share a SNAXLink line.
SCF Commands for SNAX/XF and SNAX/APN ADD LINE Command Considerations When Using Multiple Service-Manager Processes When the SCF SETMANAGER command is issued, all subsequent SCF commands are directed to the service manager named.
SCF Commands for SNAX/XF and SNAX/APN ADD LINE Command ADD LINE Attributes (58,3) attribute-spec for the LINE object type/subtype 58,3 (X.25 line) in the ADD command is one of the following attribute name and value combinations: [ APPLID [ ( ] IBM-appl-name [ , IBM-appl-name , ...
SCF Commands for SNAX/XF and SNAX/APN ADD LINE Command ADD LINE Attributes (58,4 and 58,6)) attribute-spec for the LINE object type/subtype 58,4 (Token-Ring line) and 58,6 (Ethernet line) in the ADD command is one of the following attribute name and value combinations: [ ADDRESS integer ] [ APPLID [ ( ] IBM-appl-name [ , IBM-appl-name , ...
SCF Commands for SNAX/XF and SNAX/APN [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ADD LINE Command AUTOACCEPT { ON | OFF } ] AUTOLOAD { ON | OFF } ] AUTOTESTRESP { ON | OFF } ] BINDENTRY "bind-table-entry-name" ] BINDTABLE bind-table-name ] CHARACTERSET { ASCII | EBCDIC | KATAKANA } ] DIALTYPE IN ] DSRTIMEMOUT integer ] DUPLEX { HALF | FULL } ] FCSERRREPORTFREQ integer ] FLAGFILL { ON | OFF } ] INTERFACE { RS232 | RS422 | V25 | X21 } ] IOPAGES integer ] L2OPTION1 { O
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command ADD LU Command The ADD LU command configures an LU object within the SNAX/XF and SNAX/APN subsystems. It is a sensitive command. ADD [ / OUT file-spec / ] LU object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is described for each case in the following pages.
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command object-name is the name of the LU object to be added. LIKE object-name identifies an existing LU object whose attribute values serve as a model for the values of the attributes of the object being created. object-name must specify an existing object of the same type. attribute-spec is a specification of an attribute and a value to be assigned to it.
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command The cost of maintaining configuration files by reducing the number of ADD LU commands in those files. NUMBEROFLUS is best used in configurations where several LUs under a PU share identical attribute values (except for names and addresses), and where LU names and addresses are assigned in simple, numerically ascending order. The amount of reduction varies, depending on configurations.
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command Considerations for SNAX/XF ADD [ / OUT file-spec / ] LU object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is described for each case in the following pages.
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command Local LU Object—APPC Local LU objects used for APPC represent local LUs on the NonStop system. SNAX/APC open these local LUs. At least one local LU must always be configured.
SCF Commands for SNAX/XF and SNAX/APN ADD LU Command Remote LU Object—XLF ILOGMGR LU attribute-spec for the ILOGMGR remote LU object type in the ADD command is one of the following attribute name and value combinations: PUNAME #pu-name SNANAME snaname TYPE ( 14, 21 ) [ SNANETID snanetid ] [ TPF { LOW | MED | HI } ] Remote LU Object—XLF Acquired LU The XLF acquired remote LU object represents 3270 terminals and printers that applications on the NonStop system are to acquire.
SCF Commands for SNAX/XF and SNAX/APN ADD PU Command ADD PU Command The ADD PU command configures a PU object within the SNAX/XF and SNAX/APN subsystems. It is a sensitive command. ADD [ / OUT file-spec / ] PU object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is one of the following: (Note that ADDRESS, MAXLUS, RECSIZE and TYPE 13,21 are required for configuring a remote PU object for SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN ADD PU Command LIKE object-name identifies an existing PU object whose attribute values serve as a model for the values of the attributes of the object being created. object-name must specify an existing object of the same type. attribute-spec is a specification of an attribute and a value to be assigned to it. If the LIKE syntax is used, attribute-spec overrides the setting derived from the LIKE object for that attribute.
SCF Commands for SNAX/XF and SNAX/APN AGGREGATE Command AGGREGATE Command The AGGREGATE command retrieves counts of active and defined objects subordinate to the specified object. It is a nonsensitive command. AGGREGATE [ / OUT file-spec / ] { LINE } { PU } { SUBSYS } { object-name } { ( object-name [, object-name ]... ) } OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name.
SCF Commands for SNAX/XF and SNAX/APN AGGREGATE Command AGGREGATE LINE Example The following example illustrates the AGGREGATE LINE command and its returned display. Command Example: ->AGGREGATE LINE \SYS2.$SNAP1 Returned Display: SNAX Aggregate LINE \SYS2.$SNAP1 Type PU LU Total 1 32 Started 1 32 Stopped 0 0 Display Descriptions: Type lists the object types being reported. Total shows the total number of each object type in the report. Started shows the number of objects in the STARTED state.
SCF Commands for SNAX/XF and SNAX/APN AGGREGATE Command Type lists the object types being reported. Total shows the total number of each object type in the report. Started shows the number of objects in the STARTED state. Stopped shows the number of objects in the STOPPED state. AGGREGATE SUBSYS Example The following example illustrates the AGGREGATE SUBSYS command and its returned display. Command Example: ->AGGREGATE SUBSYS \SYS2.$SSCP Returned Display: SNAX Aggregate SUBSYS \SYS2.
SCF Commands for SNAX/XF and SNAX/APN ALLOWOPENS Command ALLOWOPENS Command The ALLOWOPENS command negates the effect of a STOPOPENS command and allows applications to open the specified devices. It is a sensitive command. ALLOWOPENS [ / OUT file-spec / ] { { { { LINE LU PU SUBSYS } } } } { object-name } { ( object-name [, object-name ]... ) } [, SUB [ subtype ] ] [, SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN ALLOWOPENS Command Consideration The only types of LUs for which the ALLOWOPENS command is valid are local LUs used for APPC and acquired remote LUs. If the ALLOWOPENS command is issued for a remote LU used for APPC, a TLOGMGR LU, or an ILOGMGR LU, SCF rejects the command. Therefore, an ALLOWOPENS SUBSYS, SUB LU or ALLOWOPENS LINE, SUB LU command fails unless only local LUs used for APPC and acquired remote LUs are defined under the specified SUBSYS or LINE object.
SCF Commands for SNAX/XF and SNAX/APN ALTER APPL Command ALTER APPL Command The ALTER APPL command changes the values of attributes defining characteristics of an APPL object. It is a sensitive command. ALTER [ / OUT file-spec / ] APPL object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is one of the following for SNAX/XF: [ APPLFILE filename ] [ APPLTYPE { [ ( ] integer [ , integer , ... ] [ ) ] } { [ ( ] name [ , name , ... ] [ ) ] } ] [ ASSOCIATEPU [ $line-name.
SCF Commands for SNAX/XF and SNAX/APN ALTER APPL Command The PASSWORD attribute can be specified only in the ADD APPL command; it cannot be specified in the ALTER command. To change the password, you must use the DELETE command to delete the APPL object, and then use the ADD command to add it again. The password is not displayed by the INFO APPL command. APPL objects apply to SNAX/APN only when the extended logon facility (XLF) is used.
SCF Commands for SNAX/XF and SNAX/APN ALTER LINE Command ALTER LINE Command The ALTER LINE command changes or removes the values of attributes defining characteristics of a LINE object. It is a sensitive command. ALTER [ / OUT file-spec / ] LINE object-name [, LIKE object-name ] [, attribute-spec ]... OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name.
SCF Commands for SNAX/XF and SNAX/APN ALTER LINE Command the SNAX/XF and SNAX/APN product calculates a new XPAGES value) or XPAGES n, where n is the number of XPOOL pages. If the value of MAXPUS or MAXLUS is increased using an SCF ALTER LINE command without also specifying XPAGES, an error is returned. If you are configuring SNAX/APN type 2.1 PUs to share a line with SNAX/XF type 2.0 PUs, a number of additional considerations apply. For details, see Considerations for Shared Lines on page 13-8.
SCF Commands for SNAX/XF and SNAX/APN ALTER LINE Command ALTER LINE Attributes (58,3) attribute-spec for the LINE object type/subtype 58,3 (X.25 line) in the ALTER command is one of the following attribute name and value combinations: [ APPLID [ ( ] IBM-appl-name [ , IBM-appl-name , ...
SCF Commands for SNAX/XF and SNAX/APN ALTER LINE Command ALTER LINE Attributes (58,4 and 58,6)) attribute-spec for the LINE object type/subtype 58,4 (Token-Ring line) and 58,6 (Ethernet line) in the ALTER command is one of the following attribute name and value combinations: [ ADDRESS integer ] [ APPLID [ ( ] IBM-appl-name [ , IBM-appl-name , ...
SCF Commands for SNAX/XF and SNAX/APN [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTER LINE Command AUTOACCEPT { ON | OFF } ] AUTOLOAD { ON | OFF } ] AUTOTESTRESP { ON | OFF } ] BINDENTRY "bind-table-entry-name" ] BINDTABLE bind-table-name ] CHARACTERSET { ASCII | EBCDIC | KATAKANA } ] DIALTYPE IN ] DSRTIMEMOUT integer ] DUPLEX { HALF | FULL } ] FCSERRREPORTFREQ integer ] FLAGFILL { ON | OFF } ] INTERFACE { RS232 | RS422 | V25 | X21 } ] IOPAGES integer ] L2OPTION1 {
SCF Commands for SNAX/XF and SNAX/APN ALTER LU Command ALTER LU Command The ALTER LU command changes or removes the values of attributes that define characteristics of an LU object. It is a sensitive command. ALTER [ / OUT file-spec / ] LU object-name [, LIKE object-name ] [, attribute-spec ]... attribute-spec is described on the following pages OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name.
SCF Commands for SNAX/XF and SNAX/APN ALTER LU Command Examples for SNAX/APN ->ALTER LU $APN1.#LL1, SNANAME AL37C101 ->ALTER LU $APN1.#crt,PROTOCOL CRT, SENDUNBIND01 YES All ALTER LU attributes and their values are described in Section 14, Attributes for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN ALTER LU Command Remote LU Object—XLF ILOGMGR LU attribute-spec for the ILOGMGR remote LU object type in the ALTER command is one of the following attribute name and value combinations: [ SNANAME snaname ] [ SNANETID snanetid ] [ TPF { LOW | MED | HI } ] Remote LU Object—XLF Acquired LU The XLF acquired remote LU object represents 3270 terminals and printers that applications on the NonStop node will acquire.
SCF Commands for SNAX/XF and SNAX/APN ALTER PU Command ALTER PU Command The ALTER PU command changes or removes the values of attributes that define characteristics of a PU object. An ALTER PU command can be performed only when the LINE object is in the STOPPED state. ALTER is a sensitive command. ALTER [ / OUT file-spec / ] PU object-name [, LIKE object-name ] [, attribute-spec ]...
SCF Commands for SNAX/XF and SNAX/APN ALTER PU Command LIKE object-name identifies an existing PU object whose attribute values serve as a model for the new values of the attributes of the object being altered. object-name must specify an existing object of the same type. attribute-spec is a specification of an attribute and a value to be assigned to it. If the LIKE syntax is used, attribute-spec overrides the setting derived from the LIKE object for that attribute.
SCF Commands for SNAX/XF and SNAX/APN ALTER SUBSYS Command ALTER SUBSYS Command The ALTER SUBSYS command changes the values of attributes defining characteristics of the SUBSYS object. It is a sensitive command.
SCF Commands for SNAX/XF and SNAX/APN ALTER SUBSYS Command Example for SNAX/XF ->ALTER SUBSYS $SSCP, SETTAB $SYSTEM.SET.
SCF Commands for SNAX/XF and SNAX/APN BOOT Command BOOT Command The BOOT command prepares one or more controllers for a microcode download. It is a sensitive command. The SCF BOOT LINE command is valid for SNAX line type 58,5. Once issued, the line continuously downloads until an SCF START LINE command is issued and the line is in the STARTED state. BOOT [ / OUT file-spec / ] { PROCESS } { SUBSYS } object-name [, object-name ]...
SCF Commands for SNAX/XF and SNAX/APN DELETE Command Examples ->BOOT PROCESS $SLINE ->BOOT SUBSYS $SSCP,SUB PROCESS DELETE Command The DELETE command removes objects from the SNAX/XF and SNAX/APN subsystems. It is a sensitive command. DELETE [ / OUT file-spec / ] { { { { { APPL LINE LU PU SUBSYS } } } } } { object-name } { ( object-name [, object-name ]...
SCF Commands for SNAX/XF and SNAX/APN DELETE Command Valid states for APPL objects are INACTIVE, OPENED, and CONNECTED. Valid states for other types of objects are ABORTING, DEFINED, DIAGNOSING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN. The object states are described in Section 12, Objects for SNAX/XF and SNAX/APN. Considerations The DELETE command is invalid for the local PU object type. An object must be in the STOPPED state before it can be deleted.
SCF Commands for SNAX/XF and SNAX/APN INFO Command INFO Command The INFO command displays the current values of configuration attributes for the specified object. It is a nonsensitive command. INFO [ / OUT file-spec / ] { { { { { APPL LINE LU PU SUBSYS } } } } } { object-name } { ( object-name [, object-name ]... ) } [, DETAIL ] [, SUB [ subtype ] ] [, SEL [ NOT ] state ] [, attribute-name ]... OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN INFO Command SEL [ NOT ] state directs the command to provide information only about objects in the specified state (if NOT is omitted) or only about objects not in the specified state (if NOT is specified). Valid states for APPL objects are INACTIVE, OPENED, and CONNECTED. Valid states for other types of objects are ABORTING, DEFINED, DIAGNOSING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Table 13-2.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Table 13-2. INFO Command Attribute Names (page 3 of 3) Object Type SUBSYS** * Attributes Attributes (continued) ADDRESS MAXLUS ASSOCIATESUBDEV MAXPTS AUTOLOGON NOACQ BINDENTRY PUIDBLK BINDTABLE PUIDNUM CALLADDR RECSIZE CALLVALIDATE REQDISCONTTYPE CONNID REQMS CPNAME SERVICECOUNT DYNAMIC SWPUTYPE * ESSTABLE TYPE L3RETRY WINDOW CPNAME SNANETID SSCPID VERSION * SETTAB XPAGES INFO display attribute only.
SCF Commands for SNAX/XF and SNAX/APN INFO Command INFO APPL Example The following example illustrates the INFO APPL command without the DETAIL option, and its returned display. Command Example: ->INFO APPL \SYS2.$SSCP.#APPL1 Returned Display: SNAX Info APPL: APPL \SYS2.$SSCP.#APPL1 *ApplFile \SYS2.$DATA.APPLS.APPL1 *Creator #CREATOR Display Descriptions: APPL is the name of the APPL object. All other INFO APPL display fields are described in Section 14, Attributes for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN INFO Command ApplType is always 6-LUNSCRE in a SNAX/APN environment, as described in Section 14, Attributes for SNAX/XF and SNAX/APN. Creator does not apply in a SNAX/APN environment. INFO LINE Example The following example illustrates an INFO LINE command without the DETAIL option, and its returned display. Command Example: ->INFO LINE $SNAP1 Returned Display: SNAX Info LINE: Line *Station *Switched *Duplex *Retries *Timeout \SYS2.$SNAP1 PRIMARY OFF HALF 3 00:00:05.
SCF Commands for SNAX/XF and SNAX/APN INFO Command The following examples shows a line that is added under one service-manager process, but its associated PU is added under a different service-manager process: SETMANAGER $SSCP1 ADD LINE $SNA1 SETMANAGER $SSCP2 ADD PU $SNA1.#PU1, ADDRESS 200, MAXLUS 100, & RECSIZE 265, TYPE (13,2) The result is that the line $SNA1 is added to service manager $SSCP1. However, the ADD PU command is rejected with the following error message: SNAX E-00111 Object \SNAX.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Returned Display: SNAX Detailed Info Line \SYS3.$SOXP8 *Applid........... *AssociateSubDev.. *AutoAccept....... *BindEntry........ BPoolPages....... *ConnectAppl...... *EssTable......... *IOPages.......... *LUOpMsg.......... MaxConfig........ *MaxLocalLUs...... *MaxPUs........... *MdmLossFatal..... *NoAcq............ *PuidNum.......... SMaxLUs.......... SmdmLossFatal.... *Switched......... *SwSessTimeout.... Version.......... *XPages...........
SCF Commands for SNAX/XF and SNAX/APN INFO Command ON set if the SCF DEVICE modifier MODEMLOSSFATAL is specified. If ON, the line handler brings the switched line down in case of modem failure. Type shows the line type and subtype (58,3). Version is the version of the line-handler process. If a mismatch occurs between the linehandler process and the service manager either in the SPR or RVU versions or when using multiple service managers, an error message is returned.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Returned Display: SNAX Detailed Info Line \SYS3.$TRP1 *Applid........... N/A *AutoAccept....... N/A *AutoLogon........ *BindEntry........ N/A *BindTable........ BPoolPages....... 868 *CharacterSet..... *ConnectAppl...... NONE *DialType......... *EssTable......... N/A *Interface........ *IOPages.......... 2 *Linkstationmode.. *LUOpMsg.......... OFF ServiceManager... MaxConfig........ OFF MaxConfigXPages.. *MaxLocalLUs...... 0 *MaxLUs........... *MaxPUs....
SCF Commands for SNAX/XF and SNAX/APN INFO Command ON set if the SCF DEVICE modifier MODEMLOSSFATAL is specified. If ON, this modifier has no meaning for an Ethernet line. Type shows the line type and subtype (58,4). Version is the version of the line-handler process. If a mismatch occurs between the linehandler process and the service manager either in the SPR or RVU versions or when using multiple service managers, an error message is returned. For more information, see Appendix C, Error Messages.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Returned Display: SNAX Detailed Info Line \SNA1.$AMAP1 *Program.......... \SNA1.$SYSTEM.CSS06.C8168P00 *Debug............ OFF *Applid........... *AssociateSubDev.. *AutoLoad......... *AutoTestResp..... *BindTable........ *CharacterSet..... *DialType......... *Duplex........... *FcsErrReportFreq. *Interface........ *L2Option1........ *LUOpMsg.......... MaxConfig........ *MaxLocalLUs...... *MaxPUs........... *MdmLossFatal..... *NetId............ *Pollint...
SCF Commands for SNAX/XF and SNAX/APN INFO Command manager, (b) the INFO LINE command is sent to the wrong service manager, or (c) an attempt is made to add a line to a second service manager if that same line was already added to one service manager. SMdmLossFatal displays the value of the SCF DEVICE modifier (NO)MODEMLOSSFATAL. OFF the default value, set if the SCF DEVICE modifier NOMODEMLOSSFATAL is specified. ON set if the SCF DEVICE modifier MODEMLOSSFATAL is specified.
SCF Commands for SNAX/XF and SNAX/APN INFO Command The Applid, AutoLogon, EssTable, LuOpmsg, and NoAcq fields do not apply to SNAX/APN. When SNAX/APN type 2.1 PUs share the line with SNAX/XF type 2.0 PUs, these fields can contain attribute values significant to SNAX/XF operation. The SpXID field does not apply to SNAX/APN. The ConnectAppl and SwSessTimeout fields have no meaning when SNAX/APN runs on a 3605/3650 line.
SCF Commands for SNAX/XF and SNAX/APN INFO Command ServiceManager displays the name of the service manager associated with the line, or “UNKNOWN” when a line has not been added to any service manager.
SCF Commands for SNAX/XF and SNAX/APN INFO Command INFO LU Example The following example illustrates the INFO LU command without the DETAIL option, and its returned display. Command Example: ->INFO LU $APN1.#LLU1 Returned Display: LU \SNACOM1.$APN1.#LLU1 *Address PuName 2 #PU1 *Charset *Type *Protocol *Snaname ASCII (14,21) SNALUXS CICS21 Display Descriptions: LU indicates the name of the LU object being reported. Address (for SNAX/APN only) is the LU address.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Returned Display: SNAX Detailed Info LU \SNA1.$AMAP1.#LUSCF1 *ActLU............ *AllowedMix....... *AutoLogon........ *BindTable........ *CharacterSet..... *DevType.......... *EssTable......... *LUDisabled....... *NoAcq............ *PassThru......... PUName........... *Static........... *Type............. COLD N/A N/A N/A EBCDIC 3278-2 N/A N/A N/A N/A #PUSCF1 OFF (14,2) *Address.......... *Associate........ *BindEntry........ *CDI.............. *Dbcs...
SCF Commands for SNAX/XF and SNAX/APN INFO Command Examples for SNAX/APN Local LU Object—APPC The following example illustrates the INFO LU command with the DETAIL option, and its returned display for a local LU used for APPC. Command Example: ->INFO LU $APN1.#LLU1, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#LLU1 *ApplFile......... *BindEntry........ *CDI.............. Creator......... *DevType.......... *DluName.......... Local............ *MaxReadCnt....... NT21............. PuName..
SCF Commands for SNAX/XF and SNAX/APN INFO Command Remote LU Object—APPC The following example illustrates the INFO LU command with the DETAIL option, and its returned display for a remote LU used for APPC. Command Example: ->INFO LU $APN1.#RLU1, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#RLU1 *ApplFile........ *BindEntry....... *CDI............. Creator......... *DevType......... *DluName......... Local........... *MaxReadCnt...... NT21............ PuName.......... *RecSize.........
SCF Commands for SNAX/XF and SNAX/APN INFO Command Local LU Object—XLF TLOGMGR LU The following example illustrates the INFO LU command with the DETAIL option, and its returned display for the TLOGMGR local LU. Command Example: ->INFO LU $APN1.#T16APP1, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#T16APP1 *ApplFile........ *BindEntry....... *CDI............. Creator......... *DevType......... *DluName......... Local........... *MaxReadCnt...... NT21............ PuName.......... *RecSize.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Remote LU Object—XLF ILOGMGR LU The following example illustrates the INFO LU command with the DETAIL option, and its returned display for the ILOGMGR remote LU. Command Example: ->INFO LU $APN1.#ILM, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#ILM *ApplFile........ *BindEntry....... *CDI............. Creator......... *DevType......... *DluName......... Local........... *MaxReadCnt...... NT21............ PuName.......... *RecSize.......
SCF Commands for SNAX/XF and SNAX/APN INFO Command Remote LU Object—XLF Acquired LU The following example illustrates the INFO LU command with the DETAIL option, and its returned display for an acquired remote LU. Command Example: ->INFO LU $APN1.#ITIA03A, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#ITIA03A *ApplFile........ *BindEntry....... *CDI............. Creator......... *DevType......... *DluName......... Local........... *MaxReadCnt...... NT21............ PuName..........
SCF Commands for SNAX/XF and SNAX/APN INFO Command Remote LU Object—LU Created by TLOGMGR The following example illustrates the INFO LU command with the DETAIL option, and its returned display for a remote LU created automatically by the TLOGMGR. Command Example: ->INFO LU $APN1.#ZR00001, DETAIL Returned Display: SNAX Detailed Info LU \SNACOM1.$APN1.#ZR00001 *ApplFile........ *BindEntry....... *CDI............. Creator......... *DevType......... *DluName......... Local........... *MaxReadCnt...... NT21...
SCF Commands for SNAX/XF and SNAX/APN INFO Command Command Example: ->INFO PU $S1.#P0 Returned Display: PU *Address *MaxLUs *Type *RecSize *Window *MaxPTS \SYS2.$S1.#P0 193 125 (13,2) 256 7 N/A Display Descriptions: PU indicates the name of the PU. MaxPTS has no meaning when SNAX/APN runs on a line. All other INFO PU display fields are described in Section 14, Attributes for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN INFO Command The name given at the end of the first line of the display is the name of the PU object. The following display field is not configurable with the ADD PU or ALTER PU command and is provided for information only: SwPuType indicates whether or not a switched PU is a floating device. ON means that the switched PU was defined as floating. OFF means that the switched PU was not defined as floating.
SCF Commands for SNAX/XF and SNAX/APN INFO Command INFO PU, DETAIL display fields for the local PU are described in Section 14, Attributes for SNAX/XF and SNAX/APN. The value of MaxLUs should equal the MaxLocalLUs specification for the LINE object. Remote PU Object For remote PUs, the following example illustrates the INFO PU command with the DETAIL option, and its returned display. Command Example: ->INFO PU $APN1.#PUSCFNT, DETAIL Returned Display: SNAX Detailed Info PU \SNA2.$APN1.#PUSCFNT *Address....
SCF Commands for SNAX/XF and SNAX/APN INFO Command Returned Display: SNAX Info SUBSYS: Name $SSCP SscpId Xpages Settab 1 32 $System.system.settab Display Descriptions: Name is the name of the SUBSYS object being reported. SscpId does not apply to SNAX/APN operation. When SNAX/APN type 2.1 PUs share the line with SNAX/XF type 2.0 PUs, this field can contain a value significant to SNAX/XF operation. All other INFO SUBSYS display fields are described in Section 14, Attributes for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN INFO Command Version is the version of the line-handler process. If there is a mismatch between the linehandler process and the service manager either in the SPR or RVU versions or when using multiple service managers, an error message is returned. For more information, see Appendix C, Error Messages, or the SNAX/XF and SNAX/APN Event Management Programming Manual. The CPName and SNANetId display fields do not apply to SNAX/XF.
SCF Commands for SNAX/XF and SNAX/APN NAMES Command The names given in the left-hand column of the display are the names of the objects about which information is being reported. The column headings identify the object type for each set of objects. All other INFO SUBSYS display fields are described in Section 14, Attributes for SNAX/XF and SNAX/APN. Note that this example corresponds to the subsystem configured in the examples listed under the ADD command.
SCF Commands for SNAX/XF and SNAX/APN NAMES Command SEL [ NOT ] state directs the command to provide only names of objects in the specified state (if NOT is omitted) or only names of objects not in the specified state (if NOT is specified). Valid states for APPL objects are INACTIVE, OPENED, and CONNECTED. Valid states for other types of objects are ABORTING, DEFINED, DIAGNOSING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN.
SCF Commands for SNAX/XF and SNAX/APN NAMES Command Examples The NAMES command display for the SUBSYS object type has the format shown in the following example (the display for the other object types is similar in form). Command Example: ->NAMES SUBSYS $SSCP Returned Display: SNAX Names SUBSYS \SYS2.$SSCP SUBSYS $SSCP APPL $SSCP.#CREATE $SSCP.#CI LINE $SBS41 $SLINK $SNA1 $SNA6 $SNA7 $SNA8 PU $SNA1.#P0 $SNA2.#P0 $SNA3.#PU1 $SNA6.#PU1 $SNA8.#PU1 LU $SNA1.#P0L000 $SNA1.#P0L004 $SNA1.#P1L003 $SNA1.
SCF Commands for SNAX/XF and SNAX/APN NAMES Command Returned Display: SNAX NAMES SUBSYS \SNAX.$SSCP1 SUBSYS $SSCP1 LINE $SNA1 PU $SNA1.#PU1 $SNA1.#PU2 LU $SNA1.#LU1 $SNA1.#LU2 Similarly, issuing the following commands returns all the objects under service manager $SSCP2.
SCF Commands for SNAX/XF and SNAX/APN NAMES Command NAMES LU, SUB ALL Example The NAMES LU, SUB ALL and NAMES LU, SUB SESSION commands can display the multiple and parallel sessions subordinate to a given LU. Command Example: ->NAMES LU $APN10.#LU1, SUB ALL Returned Display: SNAX Names LU \SNAX.$APN10.LU1 LU $APN10.#LU1 SESSION $APN10.#LU1.D95F195317EA70FE $APN10.#LU1.D95F195317EA70FF $APN10.#LU1.D95F195317EA7100 $APN10.#LU1.
SCF Commands for SNAX/XF and SNAX/APN PRIMARY Command PRIMARY Command The PRIMARY command changes which CPU is the primary CPU for a process. PRIMARY [ / OUT file-spec / ] { PROCESS } object-name { SUBSYS } , number OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name. If this option is not specified, the output is sent to the home terminal.
SCF Commands for SNAX/XF and SNAX/APN SETMANAGER Command SETMANAGER Command The SETMANAGER command allows you to explicitly set a subsystem service manager process name rather than having SCF determine the name. Using this command sets a specified service manager for subsequent SCF commands. This is a nonsensitive command. SETMANAGER [ / OUT file-spec / ] [ \system.]$process OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN SETMANAGER Command the system, an operator can use the SCF NAMES commands to determine objects added under each service-manager process. Considerations 1. If you omit $process, any previously entered SETMANAGER command is cleared. 2. First use the ASSUME command to set the object type or object name. This determines the subsystem to which subsequent commands are routed.
SCF Commands for SNAX/XF and SNAX/APN SETMANAGER Command Local Passthrough There is no restriction on local passthrough if the primary and secondary lines are added to the same service-manager process.
SCF Commands for SNAX/XF and SNAX/APN START Command START Command The START command initiates the operation of one or more objects. It is a sensitive command. START [ / OUT file-spec / ] { { { { LINE LU PU SUBSYS } } } } { object-name } { ( object-name [, object-name ]... ) } [, SUB [ subtype ] ] [, SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name.
SCF Commands for SNAX/XF and SNAX/APN START Command ->START LINE $SNAP4,SUB ALL ->START LINE $SNAP5,SUB ONLY ->START LINE ($SNAP6,$SNAP7),SUB PU ->START LU $SNAP1.#LU1 ->START PU $SNAS1.#PU1 ->START PU $SNAS1.#PU2,SUB ALL ->START PU $SNAS1.
SCF Commands for SNAX/XF and SNAX/APN STATS Command STATS Command The STATS command retrieves and displays statistics about an object and then, if the RESET option is specified, restores the statistics counters to their initial values. STATS is a sensitive command when issued with the RESET option, and a nonsensitive command when issued without the RESET option. STATS [ / OUT file-spec / ] { { { { LINE LU PU SUBSYS } } } } { object-name } [, RESET ] { ( object-name [, object-name ]...
SCF Commands for SNAX/XF and SNAX/APN STATS Command UNKNOWN. The object states are described in Section 12, Objects for SNAX/XF and SNAX/APN. Considerations The write retries counter produced using the STATS LINE command is not the same as the retries value created using the Measure LINE command. (Measure and SCF use entirely different methods of counter allocation.
SCF Commands for SNAX/XF and SNAX/APN STATS Command Returned Display: SNAX Stats LINE \SYS3.$SNA1 Sample Time: 06 Mar 2000, 18:32:34.007 Reset Time: 06 Mar 2000, 10:30:00.
SCF Commands for SNAX/XF and SNAX/APN STATS Command I-FRM Sent indicates the number of DLC I-frames successfully transmitted. I-FRM Recv indicates the number of DLC I-frames successfully received. PIUs Sent indicates the number of PIUs successfully sent from this line. PIUs Recv indicates the number of PIUs successfully received by this line. REJ Sent indicates the number of DLC Rejects (REJ) sent by this line. REJ Recv indicates the number of DLC Rejects (REJ) received by this line.
SCF Commands for SNAX/XF and SNAX/APN STATS Command LUs Active indicates the number of currently active LUs under the control of this particular line. LUs Defined indicates the number of LUs that have been defined with the ADD command that are under the control of the specified line. Buffer indicates the number of unavailable buffer errors associated with this line. Bad PIUs indicates the number of bad path information units (PIUs) received by this line.
SCF Commands for SNAX/XF and SNAX/APN STATS Command Note that the WRITE retries counter produced using the STATS LINE command is not the same as the retries value created using the Measure LINE command. (Measure and SCF use entirely different methods of counter allocation.) The value returned by the STATS command is maintained by the SNAX/XF and SNAX/APN process and is not constrained by any global definition imposed by Measure.
SCF Commands for SNAX/XF and SNAX/APN STATS Command Sample Time indicates the date and time the statistics counters were sampled. Opens indicates the number of OPENs currently outstanding for the specified LU. STATS PU Example The following example illustrates the STATS PU command and its returned display. Command Example: ->STATS PU $SNA1.#PU1 Returned Display: SNAX Stats PU \SYS5.$SNA1.#PU1 Sample Time: 09 Mar 2000, 12:17:28.344 Reset Time: 09 Mar 2000, 06:10:03.
SCF Commands for SNAX/XF and SNAX/APN STATS Command FRMR Sent indicates the number of DLC Frame Rejects (FRMR) sent because of an N(R) SEQ error (data without a command) or an invalid command. FRMR Recv indicates the number of DLC Frame Rejects (FRMR) received. I-FRM Sent indicates the number of DLC I-frames successfully transmitted. I-FRM Recv indicates the number of DLC I-frames successfully received. PIUs Sent indicates the number of PIUs successfully sent from this PU.
SCF Commands for SNAX/XF and SNAX/APN STATS Command LUs Active indicates the number of currently active LUs under the control of this particular PU. LUs Defined indicates the number of LUs that have been defined with the ADD command that are under the control of the specified PU. Bad PIUs indicates the number of bad path information units (PIUs) received by this PU. DCE indicates the number of DCE interrupts or other unexpected errors, such as DTR or CTS dropping, that have occurred for this PU.
SCF Commands for SNAX/XF and SNAX/APN STATS Command Returned Display: SNAX Stats SUBSYS \SYS1.$SSCP Sample Time: 06 Mar 2000, 18:32:34.007 Active Defined Pend Line PU SFPU PSPU LU APPL ActSFPU -------------------------------------------9 13 0 13 608 0 10 13 0 13 608 1 0 Curr Max Pool Alloc Alloc --------------------------------LOCAL 3016D 4326D EXTENDED 58490D 60572D Display Descriptions: Sample Time indicates the date and time that the statistics counters were sampled.
SCF Commands for SNAX/XF and SNAX/APN STATS Command PSPU Defined indicates the number of permanently subordinated PUs (not switched floating PUs) defined by the ADD command. LU Active indicates the number of currently active LUs under the control of the service manager. LU Defined indicates the number of LUs that have been defined with the ADD command that are under the control of the service manager. APPL Active indicates the number of active application programs under the control of the service manager.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command STATUS Command The STATUS command displays information about the current status of an object. It is a nonsensitive command. STATUS [ / OUT file-spec / ] { { { { { APPL LINE LU PU SUBSYS } } } } } { object-name } { ( object-name [, object-name ]... ) } [, DETAIL ] [, SUB [ subtype ] ] [, SEL [ NOT ] state ] [, info-item-name ]... OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command SEL [ NOT ] state directs the command to provide information only about objects in the specified state (if NOT is omitted) or only about objects not in the specified state (if NOT is specified). Valid states for APPL objects are INACTIVE, OPENED, and CONNECTED. Valid states for other types of objects are ABORTING, DEFINED, DIAGNOSING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Table 13-3.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Command Example: ->STATUS APPL #APPL1 Returned Display: SNAX Status APPL Name \SYS2.$SSCP.#APPL1 State STARTED Display Descriptions: Name is the name of the APPL object being reported on. State indicates the current state of the named object. For a description of the valid states for APPL objects, see Section 12, Objects for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command LineState indicates internal state information about this line. The following are valid values that may appear under the LineState heading: ABCONRSPPD indicates that the line is waiting for a response to an ABORT CONNECTION request. ACTIVE indicates that the line is ready to handle end-user data flows. ACTLRSPPD indicates that the line is waiting for a response to an SNA ACTLINK request.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Returned Display: SNAX Detailed Status LINE \SYS2.$SNXP1 Inuse.......... LineState...... I/O Addr....... Preferred IP... CMAPPL......... BkpTrace....... PriTraceFile... BkpTraceFile... OFF ACTLRSPPD 4,0, %3, %0 122.97.98.99 N/A INACTIVE N/A N/A DesiredState... Path........... Track ID....... Alternate IP... PriTrace....... State.......... Active A ABCDE 65.65.65.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command ACTLRSPPD indicates that the line is waiting for a response to an SNA ACTLINK request ALKRSPPD indicates that the line is waiting for a response to an SNA ADDLINK request. DACTLRSPPD indicates that the line is waiting for a response to an SNA DACTLINK request. DIAGACTIVE indicates that the line is in diagnostics mode, that is, diagnostic functions are currently active. INACTIVE indicates that the line has been added but is in a quiesced state.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Alternate IP indicates the alternate IP address used by the process. This attribute is not applicable to X.25 lines (type 58,3). CMAPPL does not apply to SNAX/APN. PriTrace indicates the current state of trace activity for this line (primary). Possible values are ACTIVE and INACTIVE. BkpTrace indicates the current state of trace activity for this line (backup). Possible values are ACTIVE and INACTIVE.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command STATUS LINE, SUB ALL Example The following example shows the STATUS LINE command with the SUB ALL option and its returned display for a line using SNAX/APN. Command Example: ->STATUS LINE $APN1, SUB ALL Returned Display: SNAX Status LINE Name \SYS1.$APN1 State STARTED Inuse ON LineState ACTIVE SNAX Status PU Name \SYS1.$APN1.#ZNT21 \SYS1.$APN1.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command LineState indicates internal state information about this line. For valid values, see STATUS LINE Example on page 13-97. STATUS LU Example The following example illustrates the STATUS LU command without the DETAIL option, and its returned display. Command Example 1: ->STATUS LU $SNA1.#LU1 Command Example 2: A wild-card character (*) can be used to display the status of all LUs subordinate to a line. ->STATUS LU $SNA1.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command NO SESS indicates that no session is currently active on this LU. STOPPING indicates that the LU-LU session is being stopped. SUSPENDED indicates that opens have been stopped and no session is active. SDN is the subdevice number of the LU. SessionCount is the number of sessions in which this LU is engaged. Detailed STATUS LU Example The following example illustrates the STATUS LU command with the DETAIL option, and its returned display.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command INACTIVE (Abort) indicates that an ABORT command has been issued for the LU. INACTIVE (Stop) indicates that a STOP command has been issued for the LU. LUSessState indicates the current state of the LU-LU session associated with this LU. The following are valid values that may appear under the LUSessState heading: ACT & SUSP indicates that a non-passthrough (that is, a NonStop application) session is active, but that further opens have been stopped.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command ACTLURSPPD indicates that the LU is waiting for a response to an SNA ACTLU request. Note that this state only applies to LUs on primary lines. CINITRSPPD indicates that the LU is waiting for a response to an SNA CINIT request. Note that this state only applies to LUs on primary lines. CTERMRSPPD indicates that the LU is waiting for a response to an SNA CTERM request. Note that this state only applies to LUs on primary lines.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command STOPPED indicates that OPEN procedure calls are forbidden for the LU; that is, any OPEN requests sent to this LU are rejected. SDN is the subdevice number of the LU. SessionCount is the number of sessions in which this LU is engaged. SessionCountMax keeps track of the highest number of sessions for a given LU. SessId indicates the logical subdevice number of the current LU.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command PriTrace indicates the current state of trace activity for this LU (primary). Valid values are ACTIVE and INACTIVE. BkpTrace indicates the current state of trace activity for this LU (backup). Valid values are ACTIVE and INACTIVE. Detailed STATUS LU, SUB ONLY Example (LU Used for APPC) The following example illustrates the STATUS LU command with the DETAIL and SUB ONLY options and shows its returned display.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Returned Display: SNAX Detailed Status Session D95F1953 17EA70FE TPF............ MED LU : Name........... SNAName........ Primary........ PriTrace....... \SYS1.$APN1.#LLU1 TAPPL1 SNANetid..... USPALO01 PRI INACTIVE Partner-LU : Name........... $APN1.#RLU1 SNAName........ AS4APPL1 SNANetid..... USPALO01 SNAX Detailed Status Session D95F1953 17EA70FF TPF............ MED LU : Name........... SNAName........ Primary........ PriTrace....... \SYS1.$APN1.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Display Descriptions: D95F1953 17EA70FE, D95F1953 17EA70FF, D95F1953 17EA7100, and D95F1953 17EA7101 are FQPCIDs that identify sessions. TPF indicates the transmission priority field (TPF) for the specified session. The following values can appear under the TPF heading: LOW specifies that this session has low priority relative to other sessions. MED specifies that this session has medium priority relative to other sessions.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Name is the configured subdevice name of the LU and the name of the line to which it is subordinate. SNAName is the SNA name of the LU. SNANetid is the SNA network identifier of the node in which this LU is located. Detailed STATUS LU, SUB ONLY Example (Acquired Remote LU) The following example illustrates the STATUS LU command with the DETAIL and SUB ONLY options and shows its returned display for an acquired remote LU.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command HI specifies that this session has high priority relative to other sessions. LU presents information about the LU object specified in the STATUS command. Name is the fully qualified name of the LU. SNAName is the SNA name of the LU. SNANetid is the SNA network identifier of the node in which this LU is located. Primary indicates whether the LU is primary or secondary in this session.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Name indicates the name of the line to which the corresponding PU is connected. This attribute is not returned unless the specified switched PU is connected. State indicates the current state of the PU object. For a description of the valid object states for PU objects, see Section 12, Objects for SNAX/XF and SNAX/APN. Test indicates whether diagnostic testing of the specified PU object is currently in progress.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command DISCRSPPD indicates that the PU is waiting for a response to an SNA DISCONTACT request. This state applies only to PUs on primary lines. INACTIVE indicates that the PU has been added but is in a quiesced state. MLKSTARSPPD indicates that the PU is waiting for a response to an SNA MODLINK STATION request. RQDISCRSPPD indicates that the PU is waiting for an SNA REQUEST DISCONTACT. Note that this state applies only to PUs on secondary lines.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command INACTIVE (Abort) indicates that an ABORT command has been issued for the PU. INACTIVE (Stop) indicates that a STOP command has been issued for the PU. PUState provides detailed internal state information pertaining to the specified PU. The following are valid values that may appear under the PUState heading: ACTIVE indicates that the PU has been defined and initialized. Consequently, it can transmit and receive end-user data.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command MLKSTARSPPD indicates that the PU is waiting for a response to an SNA MODLINK STATION request. RQDISCRSPPD indicates that the PU is waiting for an SNA REQUEST DISCONTACT request. Note that this state applies only to PUs on secondary lines. State indicates the current state of the PU object. For a description of the valid object states for PU objects, see Section 12, Objects for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command BkpTrace indicates the current state of trace activity for this PU (backup). Valid values are ACTIVE and INACTIVE. AssociateSubDev indicates the name of the X25AM process and subdevice currently assigned to this PU. This value is displayed only if (1) a SNAX/CM command is used with the PORT parameter and this PU is active, or (2) the PU is configured with ASSOCIATESUBDEV and has been started.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Test indicates whether diagnostic testing of the specified PU object is currently in progress. For valid values, see STATUS PU Example on page 13-112. PUState indicates detailed internal state information pertaining to this PU. For valid values, see STATUS PU Example on page 13-112. STATUS SESSION Example The following example shows the STATUS SESSION command and its returned display. Command Example: ->STATUS SESSION $APN1.#T16APP1.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Command Example: ->STATUS SESSION $APN1.#LLU1.E79F201700861167, DETAIL Returned Display: SNAX Detailed Status Session E79F2017 00861167 TPF.............MED LU : Name........... SNAName........ Primary........ PriTrace....... \SYS1.$APN1.#LLU1 TAPPL1 SNANetid..... USPALO01 PRI INACTIVE Partner-LU : Name........... $APN1.#RLU1 SNAName........ AS4APPL1 SNANetid.....
SCF Commands for SNAX/XF and SNAX/APN STATUS Command SNANetid is the SNA network identifier of the node in which the LU is located. Primary indicates whether the LU is primary or secondary in this session. PriTrace indicates the current state of trace activity for this LU (primary). Valid values are ACTIVE and INACTIVE. Partner-LU presents information about the LU that is engaged in this session with the LU specified in the LU fields.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Display Descriptions: E79F2017 0C71650E is the fully qualified procedure correlation identifier (FQPCID) of the session. TPF indicates the transmission priority field (TPF) for the specified session. The following values can appear under the TPF heading: LOW specifies that this session has low priority relative to other sessions. MED specifies that this session has medium priority relative to other sessions.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command STATUS SUBSYS Example The following example illustrates the STATUS SUBSYS command without the DETAIL option, and its returned display. Command Example: ->STATUS SUBSYS $SSCP Returned Display: SNAX Status SUBSYS Name \SYS3.$SSCP State STARTED PriTrace INACTIVE BkpTrace INACTIVE Display Descriptions: Name is the name of the SUBSYS object being reported. State indicates the current state of the SUBSYS object.
SCF Commands for SNAX/XF and SNAX/APN STATUS Command Returned Display: SNAX Detailed Status SUBSYS \SYS2.$SSCP PriTrace....... State.......... PriTraceFile... BkpTraceFile... ACTIVE BkpTrace...... ACTIVE STARTED \SYS2.$DATA2.TRACE.TRSSCPP \SYS2.$DATA2.TRACE.TRSSCPB Display Descriptions: PriTrace indicates the current state of primary trace activity for the subsystem. Valid values are ACTIVE and INACTIVE. BkpTrace indicates the current state of backup trace activity for the subsystem.
SCF Commands for SNAX/XF and SNAX/APN STOP Command STOP Command The STOP command terminates the activity of one or more objects. It is a sensitive command. STOP [ / OUT file-spec / ] { { { { { LINE LU PU SESSION SUBSYS } } } } } { object-name } { ( object-name [, object-name ]... ) } object-name [, object-name ]... [, { ORDERLY | FORCED } ] [, SUB [ subtype ] ] [, SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN STOP Command SEL [ NOT ] state directs the command to stop only objects in the specified state (if NOT is omitted) or only objects not in the specified state (if NOT is specified). Valid object states are ABORTING, DEFINED, DIAGNOSING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN. The object states are described in Section 12, Objects for SNAX/XF and SNAX/APN. The SEL option is valid only for SESSION objects.
SCF Commands for SNAX/XF and SNAX/APN STOP Command ->STOP LU $APN1.#LU1 ->STOP LU $SSCP.#LU2 ->STOP PU $APN1.#PU1 ->STOP PU $APN1.#PU2,SUB ALL ->STOP SESSION $APN1.#LU1.
SCF Commands for SNAX/XF and SNAX/APN STOPOPENS Command STOPOPENS Command The STOPOPENS command disallows the opening of LUs and stops applications from opening the devices. It is a sensitive command. STOPOPENS [ / OUT file-spec / ] { { { { LINE LU PU SUBSYS } } } } { object-name } { ( object-name [, object-name ]... ) } [, SUB [ subtype ] ] [, SEL [ NOT ] state ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNAX/XF and SNAX/APN STOPOPENS Command Consideration The STOPOPENS command does not disrupt current sessions: that is, only subsequent open requests are rejected. Considerations The STOPOPENS command does not disrupt current sessions. That is, only subsequent OPEN requests are rejected. The only types of LU for which the STOPOPENS command is valid are local LUs used for APPC and acquired remote LUs.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command TRACE Command The TRACE command requests the capture of certain information about the specified SNAX/XF and SNAX/APN line or subsystem that can help in problem determination. It also allows you to modify or stop the tracing activity previously specified for a line or subsystem. After capturing information with the TRACE command, you can view the information with the PTrace utility, as described in Section 15, PTrace Reference for SNAX/XF and SNAX/APN.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command STOP [, BACKUP ] discontinues the trace currently in progress. If BACKUP is specified along with STOP, only the trace in the backup line-handler or service-manager process is stopped. Otherwise, only the trace in the primary process is stopped. BACKUP when given as trace-option, specifies tracing of the backup line-handler or service-manager process.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command If you are starting a trace and do not specify LUSELECT, all LUs are traced. If you are modifying an existing trace and do not specify LUSELECT, the list of selected LUs does not change. NOCOLL specifies that trace data from the extended data segment is written to the disk file specified in TO file-name only when one of the following occurs: The trace is stopped.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command The OFF option is valid only for the LINE object type, and it has no meaning if neither LUSELECT nor PUSELECT is specified. PAGES pages designates how much memory space, in units of pages (2048 bytes), is to be allocated in the extended data segment used for tracing. This option can be specified only when a trace is being initiated—that is, when the TO option is specified. The value of pages must be an integer in the range 4 through 32766.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command SELECT select-spec specifies the types of trace records to be collected. If ALL is specified, all trace records for the specified line or service manager are included. If SELECT is not specified, the default value of ALL is assumed. The select-spec is one of the following specifications: { { { { keyword... } ( keyword [, keyword ]... ) } number... } ( number [, number ]...
SCF Commands for SNAX/XF and SNAX/APN TRACE Command ( s-name [, s-name]...) specifies a list of sessions to be traced. If you are starting a trace and do not specify SESSIONSELECT, all sessions are traced. If you are modifying an existing trace and do not specify SESSIONSELECT, the list of selected sessions does not change. Note. SESSIONSELECT tracing is limited to 10 session selections in a single TRACE command.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command Records 8, 9, 10, and 11 will be written to the disk file. These records will be placed in the disk file as records number 1, 2, 3, and 4, respectively. Records 5, 6, and 7 will not be written. If NOCOLL is not specified with WRAP when the trace is started, the trace collector process reads the trace records from the extended data segment and writes them to the disk file as they become available.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command X.25 Lines (Device Type 58,3) For X.25 lines, the select-spec is one or more of the following keywords: keyword L2DATA PIU BIU FILESYS MSGSYS LVL2 LVL3 LVL4 LVL5 LVL6 ASM BM LINESTD ALL (1) (2) (3) (4) (1) (1) (2) (1) (3) (4) (4) (4) (1) Can be traced selectively by using PUSELECT. Can be traced selectively by using LUSELECT. The state machine can be traced selectively by using PUSELECT. The state machine can be traced selectively by using LUSELECT.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command LVL2 (number = 10) specifies tracing for the level-2 dispatcher, scheduler, and state machine. This information can be traced selectively by also specifying PUSELECT. LVL3 (number = 11) specifies tracing for the level-3 dispatcher, scheduler, and state machine. The state-machine information can be traced selectively by also specifying PUSELECT. LVL4 (number = 12) specifies tracing for the level-4 dispatcher, scheduler, and state machine.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command SDLC Lines (Device Type 58,5) For device type 58,5, the select-spec is one or more of the following keywords: keyword L2DATA PIU (1) BIU (2) FILESYS MSGSYS LVL2 LVL3 (3) LVL4 (4) LVL5 (4) LVL6 (4) ASM (1) BM DI DO CSSLVL1 CSSLVL2 CCSTATE CCINTERF HOSTREQ PROCENTRY CCREQ CCPROCENTRY LINESTD CTLRALL ALL (1) (2) (3) (4) Can be traced selectively by using PUSELECT. Can be traced selectively by using LUSELECT.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command FILESYS (number = 6) specifies tracing for level-6 file-system requests and responses. MSGSYS (number = 8) specifies tracing for level-4 and SNAX/XF and SNAX/APN I/O subsystem (IOS) message-system traffic. LVL2 (number = 10) specifies tracing for the level-2 dispatcher, scheduler, and state machine. LVL3 (number = 11) specifies tracing for the level-3 dispatcher, scheduler, and state machine.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command CSSLVL1 (number = 20) specifies tracing for controller level-1 state machine events. CSSLVL2 (number = 21) specifies tracing for controller level-2 state machine events. CCSTATE (number = 24) specifies tracing for X.21 call-control state machine events. CCINTERF (number = 25) specifies tracing for the X.21 interface. HOSTREQ (number = 27) specifies tracing for SNAX/XF and SNAX/APN requests and responses.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command Service Manager (SUBSYS Object, Device Type 13,5) The select-spec for the SUBSYS object is one or more of the following keywords or their numeric equivalents: keyword LISTEN WRLINK LINK LDONE LOCPOOL EXTPOOL SPI CMDRESP ALL LISTEN (number = 0) specifies tracing of all messages received. WRLINK (number = 1) specifies tracing of all replies to messages. LINK (number = 2) specifies tracing of all messages sent from the service manager.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command Considerations The TRACE command for SNAX/XF and SNAX/APN differs from the TRACE command documented in the SCF Reference Manual for G-series RVUs, which provides three additional trace options for the LINE object: LUSELECT, PUSELECT, and OFF. If a PU or LU is configured after the trace session is started, the object will be traced only in the following configurations: The object is an LU and LUSELECT was not specified.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command first occurs, the source of the problem is often unknown, and it is likely that the problem will not be captured in a trace if only specific objects are selected. Once you have isolated the problem to a particular object or set of objects, you can selectively trace those objects.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command PTrace to collect the minimum amount of useful information for display, you must specify a RECSIZE of at least 100 bytes. In addition, internal trace records for the service manager capture all called procedures and sub-procedures in their order of invocation. These records are very important to HP support and development personnel in problem determination.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command modem problem, an SDLC protocol violation, or a CLIP or controller problem), then SELECT ALL is recommended. WRAP The use of this option is recommended in most situations. If you do not specify WRAP, tracing will stop when the disk trace file becomes full. This condition is not usually desirable, because it is likely that the trace will stop before the problem is captured.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command The following command deselects tracing of data for a specific LU, #LU1. When this command is issued after the previous command example, data for the other previously specified LUs (#LU2 and #LU3), as well as data for #PU4, will continue to be traced. ->TRACE LINE $SNAP2, LUSELECT #LU1, OFF The following command captures the first 100 trace records for a line: ->TRACE LINE $SLINK, TO $BETA.WORK.
SCF Commands for SNAX/XF and SNAX/APN TRACE Command In the second case, PUSELECT specifies the PU that is subsequently added: ->TRACE LINE $SNAP1, PUSELECT #PU2, TO $BETA.WORK.TRCEDATA ->ADD PU $SNAP1.#PU2, ADDRESS 200, MAXLUS 4, TYPE (13,2), & ->RECSIZE 265 The PU (#PU2) added in the ADD command is not traced. The situation illustrated above is likewise true when the object is an LU and the option is LUSELECT, or when a new session is initiated and the option is SESSIONSELECT.
SCF Commands for SNAX/XF and SNAX/APN VERSION Command VERSION Command The VERSION command retrieves and displays the subsystem version string. It is a nonsensitive command. VERSION [ / OUT file-spec / ] [ SUBSYS ] $SSCP [, DETAIL ] / OUT file-spec / causes any SCF output generated for this command to be directed to the specified file. file-spec must be a partially or fully qualified file name. If this option is not specified, the output is sent to the home terminal.
SCF Commands for SNAX/XF and SNAX/APN VERSION Command Returned Display: Detailed VERSION \SYS2.
SCF Commands for SNAX/XF and SNAX/APN VERSION Command SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 13-150
14 Attributes for SNAX/XF and SNAX/APN Attributes are the named, configurable characteristics of the objects for a subsystem. This section describes the attributes for the SNAX/XF and SNAX/APN subsystems, which are specified as parameters to one or more of the SCF commands ADD, ALTER, and INFO. The attributes are listed in alphabetic order.
Attributes for SNAX/XF and SNAX/APN ACTPU - for SNAX/XF Only The following values are valid for this attribute: COLD The ACTLU command should designate that a cold start is to be performed. No configuration or state information pertaining to the LU when it was last started is used during reinitialization. WARM The ACTLU command should designate that a warm start is to be performed.
Attributes for SNAX/XF and SNAX/APN ADDRESS (PU objects) The ADDRESS attribute is required for the LU object type. ADDRESS (PU objects) Default: None Value: %h01 - %hFE (1 - 254) Objects: PU For a PU object on line types 58,3 (X.25) or 58,5 (SDLC), ADDRESS specifies the SDLC address of the link station (PU). For PUs attached to primary lines of these types, the value must match the physical SDLC address assigned to the secondary PU.
Attributes for SNAX/XF and SNAX/APN APPLFILE with IBMKANJI. Otherwise, the default value for ALLOWEDMIX is computed using the following formula: lu-recsize + 2 ———————— + 1 3 where LUrecsize is the value defined for the LU’s RECSIZE attribute. If the DBCS attribute is specified as NONE, the ALLOWEDMIX attribute is ignored.
Attributes for SNAX/XF and SNAX/APN APPLID - for SNAX/XF Only APPLID - for SNAX/XF Only Default: Null string (" ") Value: Name or parenthesized list of names, as described in the following text Objects: LINE APPLID defines the ID names of host applications that can be accessed on a secondary line.
Attributes for SNAX/XF and SNAX/APN ASSOCIATE - for SNAX/XF Only Application types 2 (CONFIG), 3 (CNMAPPL), and 4 (CNMSERV) can be specified in combination for a single APPL object; however, application types 5 (LUNSAPPL), 6 (LUNSCRE), and 10 (CMAPPL) are mutually exclusive and cannot be specified in combination with any other application type. Subject to these restrictions, you can specify the type as one or more integers or one or more names, but you cannot mix integers and names.
Attributes for SNAX/XF and SNAX/APN ASSOCIATEPU - for SNAX/XF Only ASSOCIATEPU - for SNAX/XF Only Default: Null string (" ") Value: NonStop system file name of the form [$line-name.]pu-name Objects: APPL ASSOCIATEPU specifies the name of a PU that is to be associated with the CNM application program represented by an APPL object. The associate PU name is in external format and has the following syntax: [$line-name.]pu-name where line-name is the line name and pu-name is the SNAX/XF PU name.
Attributes for SNAX/XF and SNAX/APN ASSOCIATESUBDEV subordinate PU or with the line handler controlling a line to which switched floating PUs are temporarily subordinated. The X25AM SU object must already be configured. The process name and subdevice name must be unique for the pool of PUs under the control of one line-handler process. When this attribute is specified for an X.25 line, the following restrictions apply: You cannot remove this attribute by using the ALTER LINE command.
Attributes for SNAX/XF and SNAX/APN AUTOACCEPT AUTOACCEPT Default: OFF Value: ON | OFF Objects: LINE AUTOACCEPT specifies whether or not a switched SDLC line allows incoming calls after it is started. The default value for AUTOACCEPT is OFF. SNAX/XF applications using a switched line must issue CONTROL 11 to accept incoming calls if AUTOACCEPT OFF is specified. In the SNAX/APN environment, AUTOACCEPT ON must be specified for switched lines. The AUTOACCEPT attribute has no meaning on an X.
Attributes for SNAX/XF and SNAX/APN AUTOTESTRESP not specify the AUTOLOGON attribute in an ADD or ALTER LU command. If the line is to use switched floating PUs and LUs, or if the PU is a switched floating PU, the AUTOLOGON value must be specified in the ADD or ALTER LU command. The AUTOLOGON attribute has no meaning for a line or a PU. When this attribute is specified for a permanently subordinated LU, it overrides any value specified in the AUTOLOGON attribute for the superior line or PU.
Attributes for SNAX/XF and SNAX/APN BINDTABLE If the BINDENTRY attribute is specified for a LINE object or a PU object, all acquired remote LUs subordinate to that line or PU use that BIND image, unless the BINDENTRY attribute was specified for a particular LU. If the BINDENTRY attribute is specified for a PU, it overrides what was specified for the LINE object.
Attributes for SNAX/XF and SNAX/APN CALLADDR - for SNAX/XF Only LUs, or if the PU is a switched floating PU, the BINDTABLE attribute value must be specified in the ADD LU or ALTER LU command. If a BINDTABLE parameter is specified in an ESS table entry, it overrides the parameter specified in the ADD command.
Attributes for SNAX/XF and SNAX/APN CALLVALIDATE - for SNAX/XF Only CALLVALIDATE - for SNAX/XF Only Default: NONE Value: BOTH | CALLADDR | CONNID | NONE Objects: PU CALLVALIDATE specifies the type of call validation to be performed on incoming calls to the PU being configured. This attribute is valid only for PUs that use X.25 lines.
Attributes for SNAX/XF and SNAX/APN CHARACTERSET The following values are valid for the CDI attribute: NORMAL specifies that the CDI is generated when an application in the send state issues a READ procedure call or when an application issues a WRITE procedure call to send an outbound data stream to the device and the 3270 commands are read commands. In the latter case, the CDI is sent on a null RU.
Attributes for SNAX/XF and SNAX/APN CONNECTAPPL - for SNAX/XF Only For lines with permanently subordinated LUs, the CHARACTERSET attribute for the line is used as a default value for the LUs if no CHARACTERSET attribute was specified on an ADD or ALTER LU command. The CHARACTERSET attribute can be applied to a line, but has no meaning for the line itself. For lines with switched floating PUs and LUs, the CHARACTERSET attribute must be specified on the ADD or ALTER LU command for the switched floating LU.
Attributes for SNAX/XF and SNAX/APN CONNID - for SNAX/XF Only CONNID - for SNAX/XF Only Default: Null string (" ") Value: String of 1-8 alphanumeric characters Objects: PU CONNID specifies a connection identifier password. This attribute is valid only for PUs that use X.25 lines. If the CALLVALIDATE attribute for the PU specifies CONNID or BOTH, SNAX/XF validates this password against the connection identifier, which is contained in the call user data field of an incoming call.
Attributes for SNAX/XF and SNAX/APN CPNAME (SUBSYS Object) - for SNAX/APN Only alone. This is true only for remote PU’s configured as NNSERVER NONE or without the NNSERVER attribute. For a remote PU configured as NNSERVER, MAIN, BKUP, or OTHER, the CPNAME is an optional attribute. If not explicitly defined by the user, the CPNAME defaults to 8 blank characters. In such cases, the HP NonStop node extracts the CPNAME from the incoming Exchange Identification (XID) from the adjacent node.
Attributes for SNAX/XF and SNAX/APN CREATOR AS/400 systems: If the NonStop node is defined on the AS/400 system, the SCF CPNAME attribute of the SUBSYS object must match the specification for the RMTCPNAME in the AS/400 Controller Description. PS/2 systems running OS/2: The SCF CPNAME attribute of the SUBSYS object must match the Partner Node Name in the Configure Connection definition.
Attributes for SNAX/XF and SNAX/APN DBCS DBCS Default: NONE Value: IBMKANJI, IBM, or 1; IBMMIXED, MIXED, or 2; JEFKANJI, JEF, or 3; IBMADMIX or 4: NONE or 0 Objects: LU The following values are valid for the DBCS attribute: IBMKANJI or 1 specifies that SNAX/XF performs HP NonStop Kanji/IBM Kanji translation; it also signifies that each transition from single-byte data to double-byte data and from double-byte data to single-byte data causes the start of a new field.
DEVTYPE Attributes for SNAX/XF and SNAX/APN For IBM 3278-A1K/A2K display stations, SNAX/XF performs HP NonStop Kanji/EBCDIC Kanji translation on all Kanji data sent to the terminal (note that the user cannot enter Kanji data using a 3278 terminal). For IBM 5578-001/002 display stations, SNAX/XF performs HP NonStop Kanji/EBDIC Kanji translation on all Kanji data sent to and received from the terminal.
DIALTYPE Attributes for SNAX/XF and SNAX/APN meaning for LUs that are subordinate to a secondary line. DEVTYPE is a required attribute for all LUs to which it applies. For SNAX/APN, DEVTYPE applies only to LUs whose PROTOCOL attribute is CRT or ITI: that is, acquired remote LUs. For these LUs, DEVTYPE is a required attribute. Table 14-1 shows the IBM device types and models that are supported by SNAX/XF. Table 14-1.
Attributes for SNAX/XF and SNAX/APN DLUNAME - for SNAX/APN Only DLUNAME - for SNAX/APN Only Default: None Value: Subdevice name of a defined ILOGMGR, beginning with a pound sign (#): { #dluname Objects: | ( #dluname |, #dluname1 |, #dluname2 |, #dluname3 ) } LU DLUNAME specifies the destination Logon Manager for IBM Systems (ILOGMGR) with which the TLOGMGR LU is to have sessions. This attribute applies only to the TLOGMGR LU—that is, it is valid only when the PROTOCOL attribute is set to LOGON.
Attributes for SNAX/XF and SNAX/APN DUPLEX DUPLEX Default: HALF Value: FULL | HALF Objects: LINE DUPLEX specifies whether a LINE object is to be a half- or full-duplex line. This attribute applies only to line type 58,1. The following values are valid for this attribute: FULL specifies that the line operates as a full-duplex line. HALF specifies that the line operates as a half-duplex line.
Attributes for SNAX/XF and SNAX/APN ESSTABLE - for SNAX/XF Only ESSTABLE - for SNAX/XF Only Default: See following description Value: ESS table name of 1 through 8 characters Objects: LINE, PU, LU ESSTABLE specifies the name of an LU Network Services (LUNS) Enhanced System Service (ESS) table. SNAX/XF searches an ESS table for an LU when the LU enters an SNA character-coded command or sends an SNA INIT-SELF or TERM-SELF command.
Attributes for SNAX/XF and SNAX/APN FLAGFILL FLAGFILL Default: OFF Value: ON | OFF Objects: LINE FLAGFILL specifies whether or not the bit-synchronous controller is to transmit SDLC flags (%h7E) when the line is idle. FLAGFILL ON indicates that flags are to be sent; FLAGFILL OFF indicates that no SDLC flags are to be sent.
Attributes for SNAX/XF and SNAX/APN INTERFACE INTERFACE Default: RS232 Value: RS232 | RS422 | V25 | X21| X25 (INFO only) | TR (INFO only) Objects: LINE For line type 58,5 (SDLC), INTERFACE defines the physical interface between the controller and the modem or modem eliminator. The following values are valid for this attribute in an ADD or ALTER command: RS232 specifies that the line uses the RS-232 electrical interface. This value has no functional meaning for the SWAN concentrator.
Attributes for SNAX/XF and SNAX/APN L2OPTION1 L2OPTION1 Default: OFF Value: ON | OFF Objects: LINE L2OPTION1 indicates whether the rules used for station management (polling) and flow control (RNR) are modified. This token only applies to primary stations using line type 58,5 (SDLC). The default is OFF. ON causes the following polling to occur: Before acknowledging receipt of an I-frame from a secondary station, a primary station polls the other secondary stations on the poll list.
Attributes for SNAX/XF and SNAX/APN L3TIMEOUT level 3 that the PU is inoperative. When -1 is specified or taken as the default, the PU contact operation is retried indefinitely or until the PU is stopped, whichever occurs first. (The INFO LINE command displays a -1 value of this parameter in its unsigned form, 65535.
Attributes for SNAX/XF and SNAX/APN LINKSTATIONMODE LINKSTATIONMODE Default: NRM Value: NRM Objects: LINE LINKSTATIONMODE specifies the level-2 protocol to be used on the line. The value NRM specifies normal response mode. When adding line type 58,5 (SDLC), you should either omit this attribute or specify the value NRM. When adding line type 58,3 for X.25 lines, you should omit this attribute.
Attributes for SNAX/XF and SNAX/APN LNMAXRETRY LNMAXRETRY Default: 8 Value: 1 - 255 Objects: PU (Ethernet or Token-Ring only) LNMAXRETRY replaces the retired Token-Ring attribute TRMAXRETRY on page 14-71. LNMAXRETRY is the maximum number of times that an I- or S-frame can be retransmitted. It is used in conjunction with the LNT1 timer. Regardless of which attribute name is specified on an SCF ADD/ALTER command, the SCF INFO command displays LNMAXRETRY.
Attributes for SNAX/XF and SNAX/APN LNT1 LNT1 Default: 1 (second) Value: 0 - 65535 (seconds) Objects: PU (Ethernet or Token-Ring only) LNT1 replaces the retired Token-Ring attribute TRT1 on page 14-71. LNT1 is the reply timer used to detect the lack of a required response from a remote station. This attribute is optional. Regardless of which attribute name is specified on an SCF ADD/ALTER command, the SCF INFO command displays LNT1. LNT2 Default: 0.
Attributes for SNAX/XF and SNAX/APN LOCALSNANAME–SNAX/APN Only This attribute is valid in ADD and ALTER commands and required only when PROTOCOL is defined as CRT, ITI, or SNALU, or when configured for acquired remote LUs created by the TLOGMGR. Because no local LU is configured on the NonStop system when SNAX/APN is used to acquire devices, both the SNANAME and the LOCALSNANAME attributes must be configured for an acquired remote LU. PROTOCOL CRT or ITI The LOCALSNANAME attribute is required.
Attributes for SNAX/XF and SNAX/APN LUDISABLED - for SNAX/XF Only PROTOCOL LOGON The LOCALSNANAME attribute is rejected. The LOCALSNANAME attribute also appears in detailed INFO displays for remote LUs created by the TLOGMGR. For these LUs, the name displayed for LOCALSNANAME is the same as the name configured in the SNANAME attribute for the TLOGMGR LU, because dynamically added device LUs assume the SNA name of the TLOGMGR LU.
Attributes for SNAX/XF and SNAX/APN MAXLOCALLUS - for SNAX/APN Only MAXLOCALLUS - for SNAX/APN Only Default: 0 Value: 1 - 1024 Objects: LINE MAXLOCALLUS specifies the maximum number of local LUs allowed on the line. The value cannot exceed the value specified for MAXLUS. MAXLOCALLUS is a required attribute and should always be specified with a nonzero value. If MAXLOCALLUS is allowed to default, SNAX/APN cannot operate on the line. MAXLOCALLUS impacts the value of MAXLUS for the LINE object.
Attributes for SNAX/XF and SNAX/APN MAXPUS The valid range of values is 0 through the value specified for the MAXLUS attribute for this PU. When you add the PU, you need not specify a value for MAXPTS. In such a case, MAXPTS is set equal to the value specified for the MAXLUS attribute. Note, however, that any subsequent altering of the MAXLUS attribute does not change the value of MAXPTS. MAXPUS Default: 8 Value: 1 - 254 for nonswitched lines and for switched X.
Attributes for SNAX/XF and SNAX/APN MAXREADCNT - for SNAX/APN Only line. This line attribute is needed because, unlike type 2.0 PUs, the local PU object is not defined by the user for SNAX/APN operation. If MAXRCVSIZE is not specified, it defaults to the value given above. Unless the SNAX/APN BTUs need to be smaller than the BTUs for the type 2.0 PUs sharing the line, use the MAXRCVSIZE default value.
Attributes for SNAX/XF and SNAX/APN MDMLOSSFATAL MDMLOSSFATAL Default: OFF Value: ON | OFF Objects: LINE The default value is the value is OFF, and the MDMLOSSFATAL attribute has no effect. If the value is set to ON, the line handler brings the switched line down in case of modem failure. The value of the MDMLOSSFATAL attribute can be displayed using the SCF INFO LINE command. This attribute is ignored for nonswitched lines, SNAX lines over X.25 networks, or SNAX lines over Token-Ring networks.
Attributes for SNAX/XF and SNAX/APN NNSERVER NNSERVER Default: NONE Options: NONE, MAIN, BKUP, OTHER NNSERVER sets the priority of CP-CP session establishment with the network node server. An end node may communicate with multiple network nodes, but at any given time you may only have CP-CP sessions with one, your chosen network node server. You must select your primary NNS by using the option MAIN. If you want a backup NNS you must configure another remote PU object and use the option BKUP.
Attributes for SNAX/XF and SNAX/APN NONSNACA - for SNAX/APN Only value is not specified on an ADD or ALTER LU command for the LU. Switched floating LUs do not acquire the default specified for the subordinating line or PU. For switched floating LUs, the NOACQ attribute must be specified in an ADD or ALTER LU command.
Attributes for SNAX/XF and SNAX/APN PASSTHRU - for SNAX/XF Only names and addresses are assigned sequentially ascending numbers based on the root name and address supplied in the ADD LU command. For example, if the root name and address are (#XYZ008, 97), the next names and addresses would be (#XYZ009, 98), (#XYZ010, 99), (#XYZ011, 100), and so on. There is no relationship between an LU’s name and its address.
Attributes for SNAX/XF and SNAX/APN POLLINT The PASSWORD attribute has no meaning for an APPL object whose APPLTYPE value is LUNSAPPL (5). For SNAX/APN, PASSWORD specifies a password for the SNAX Creator-2 application process. If a password is specified for the APPL object, any password specified in the ADD SU command in the SCF configuration for the SNAX Creator-2 subsystem must match this APPL password. If the PASSWORD attribute is not specified, no password is used.
Attributes for SNAX/XF and SNAX/APN PROTOCOL and can be specified in uppercase or lowercase. SNAX/XF converts all lowercase letters to uppercase. The default value is $SYSTEM.CSSxx.C8448P00, where xx matches the last two characters in the subvolume containing the system image. PROTOCOL Default: None Value: CRT | ITI | LOGON | NAM | PRT | SNALU Objects: LU PROTOCOL specifies the application interface protocol that SNAX/XF uses when communicating with the corresponding LU.
Attributes for SNAX/XF and SNAX/APN LOGON PUIDBLK (LINE Objects) - for SNAX/APN Only specifies the interface the SNAX Creator-2 application and the SNAX/APN service manager use to communicate after the SNAX Creator-2 has issued the open request to the process. When PROTOCOL LOGON is specified, the LU is a TLOGMGR LU and the CREATOR attribute must also be specified.
Attributes for SNAX/XF and SNAX/APN PUIDBLK (PU Objects) - for SNAX/XF In some cases, the adjacent node might use the HP NonStop identification block and identification number for validation. In these cases, PUIDNUM and PUIDBLK must match the parameter or parameters in which the adjacent node defines the identification block and identification number it expects to receive from the link station on the NonStop system.
Attributes for SNAX/XF and SNAX/APN PUIDBLK (PU Objects) - for SNAX/APN The default value, %hFFF, indicates that SNAX/XF does not perform SDLC XID verification for a PU unless the PU is subordinate to a switched secondary line, in which case SNAX/XF sends the default value to the host in the SNAX/XF XID response. For nonswitched lines, XID exchanges are not supported, and only the default values for PUIDBLK and PUIDNUM are allowed.
Attributes for SNAX/XF and SNAX/APN PUIDNUM (LINE Objects) - for SNAX/APN PUIDNUM (LINE Objects) - for SNAX/APN Default: The NonStop system number in hexadecimal notation Value: %h00000 - %hFFFFF Objects: LINE When applied to a LINE object, PUIDNUM specifies the identification number of the local link station on the NonStop node. Together, the PUIDBLK and PUIDNUM attributes are used in link station role negotiation and can be used in Exchange Identification (XID) validation.
Attributes for SNAX/XF and SNAX/APN PUIDNUM (PU Objects) - for SNAX/APN PUIDNUM (PU Objects) - for SNAX/APN Default: %hFFFFF Value: %h00000 - %h00000 Objects: PU When applied to a PU, PUIDNUM specifies the identification number of the remote link station. Together, the PUIDBLK and PUIDNUM attributes can be used in Exchange Identification (XID) validation.
Attributes for SNAX/XF and SNAX/APN PUNAME (Local LU Objects) - for SNAX/APN The ALTER command cannot be used to change the PU name. The PU must already be defined. The PU name can be specified in uppercase or lowercase. SNAX/XF converts all lowercase letters to uppercase. PUNAME (Local LU Objects) - for SNAX/APN Default: #ZNT21 Value: #ZNT21 Objects: LU When applied to the TLOGMGR LU or to a local LU used for APPC, PUNAME specifies the name of the local PU, which must be #ZNT21.
Attributes for SNAX/XF and SNAX/APN RECSIZE (LINE Objects) The following values are valid for the QUEUE attribute: ON specifies that BIND requests from this LU are delayed if the intended partner is at its session limit or is unable to comply with the PLU/SLU specification in the BIND request. OFF specifies that BIND requests from this LU fail if the intended session partner is at its session limit or is unable to comply with the PLU/SLU specification in the BIND request.
Attributes for SNAX/XF and SNAX/APN RECSIZE (LU Objects) RECSIZE (LU Objects) Default: 1024 Value: 1 - 15996 depending on line type (See RECSIZE (LINE Objects) on page 14-49 Objects: LU When applied to an LU, RECSIZE specifies the length, in bytes, of a terminal or printer line, CRT screen, or RU, depending on the PROTOCOL attribute. For SNAX/APN, the RECSIZE attribute is valid only for LUs whose PROTOCOL attribute is CRT or ITI: that is, acquired remote LUs.
Attributes for SNAX/XF and SNAX/APN RECVLOCATE At least 2 bytes less than the value of RECSIZE specified for the SDLC, X.25, and Token-Ring line objects. For Ethernet PUs, the value must be 4 bytes less than the line’s RECSIZE. For PUs subordinate to a secondary line (or both PUs of a passthrough pair), RECSIZE should have the same value as the MAXDATA parameter specified for the NCP system generation. For Token-Ring PUs, RECSIZE must be less than (TLAM READBUFFERSIZE plus 103 bytes).
Attributes for SNAX/XF and SNAX/APN REQDISCONTTYPE REQDISCONTTYPE Default: IMMEDIATE Value: IMMEDIATE | NORMAL Objects: PU REQDISCONTTYPE determines whether a PU on a switched line is to be shut down in an orderly manner before the line is disconnected. IMMEDIATE specifies that when the line is to be disconnected, the PU is shut down immediately. All active LU-LU sessions are terminated before the PU is shut down.
Attributes for SNAX/XF and SNAX/APN RNRRECEIVE RETRIES and TIMEOUT work together and should be specified with values dependent upon the specification of RETRIES in the LINE or PU definition statements that define the HP NonStop entities in the host’s NCP system generation. Specify a RETRIES value so that when it is multiplied by TIMEOUT (in seconds), the product is greater than that produced by multiplying the “t” and “n” values specified in the RETRIES operand in the host’s NCP system generation.
Attributes for SNAX/XF and SNAX/APN RNRTIMER Disconnect Mode (DM) command to any received frame that is not a mode-setting command. The local station enters a Logical Disconnected State (LDS). RNRTIMER Default: 0 Value: 0 - 255 seconds (maximum value is 4 minutes and 15 seconds) Objects: LINE RNRTIMER specifies a value (in units of 1 second) for the RNR timer. This attribute applies only to line type 58,5 (SDLC).
Attributes for SNAX/XF and SNAX/APN RSPTYPEWR - for SNAX/APN Only RSPTYPEWR - for SNAX/APN Only Default: WRER Value: WRER | WRDR Objects: LU RSPTYPE specifies the response type to be used for data associated with the WRITE portion of a WRITEREAD request. This attribute applies only to protocol types ITI, CRT, and LOGON. The following values are valid for this attribute: WRER signifies exception (WRER) mode for WRITEREAD requests.
Attributes for SNAX/XF and SNAX/APN SCREENSIZE (TLOGMGR LU Only) If more than one SAP is defined, each SAP’s definition is separated by a semicolon (;). SCREENSIZE (TLOGMGR LU Only) Default: DEFAULT Value: DEFAULT | ALTERNATE Objects: TLOGMGR LU only SCREENSIZE specifies whether the Default or Alternate Screensize field of the CINIT will be used in the BIND sent to the terminal during XLF logon processing. DEFAULT specifies that the Default Screensize field of the CINIT will be used in the BIND.
Attributes for SNAX/XF and SNAX/APN SETTAB SERVICECOUNT has no meaning when only one PU belongs to a line. SERVICECOUNT does not affect the PU’s order or frequency of polling when no I-frames are queued for transmission. SERVICECOUNT has no meaning for Token-Ring lines. SETTAB Default: None Value: NonStop system file name Objects: SUBSYS SETTAB specifies the source file name of the LU Network Services (LUNS) session establishment (SET) table.
Attributes for SNAX/XF and SNAX/APN SNANAME (Remote LU Objects) - for SNAX/APN Only For the TLOGMGR LU used with XLF, the SNANAME specification for SNAX/APN must match an LU specification in the NCP line definition statement. Note. The TLOGMGR can create remote LU objects to represent remote devices. When you issue an INFO LU, DETAIL command to such an LU, the resulting display will show the SNA name of the TLOGMGR LU in a field called LocalSNAname.
Attributes for SNAX/XF and SNAX/APN SNANETID (Remote LU Objects) - for SNAX/APN Only However, if the remote LU is a terminal, a second BIND request to the same LU is rejected. PLU acquire: The SNANAME is used as the SLU name specified in the BIND request representing the remote LU (the SLU). If the application specifies the SLU name in its BIND request, the SLU name must match the SNANAME configured for the SNALU LU; otherwise, the BIND request is rejected.
Attributes for SNAX/XF and SNAX/APN SNANETID (PU Objects) - for SNAX/APN Only LOCALSNANAME TC17105, DEVTYPE “3278-2”, SNANETID USPALO03 & SNANETID (PU Objects) - for SNAX/APN Only Default: SNANETID value for the SUBSYS object Value: String of 1 through 8 characters in the SNA type 1134 character set Objects: PU When applied to a PU, SNANETID specifies the SNA network identifier of the adjacent node.
Attributes for SNAX/XF and SNAX/APN SNANETID (SUBSYS Object) - for SNAX/APN Only PS/2 systems running OS/2: The SCF SNANETID attribute of the remote PU object must match the Network ID in the Local Node Characteristics definition. Systems using NCP and VTAM: The SCF SNANETID attribute of the remote PU must match the NETID parameter in the VTAM Start-Up List. SNANETID cannot be altered if LUs are defined under the PU object.
Attributes for SNAX/XF and SNAX/APN SNRMIFDM SNRMIFDM Default: OFF Value: ON | OFF Objects: LINE SNRMIFDM specifies whether a primary station is to retry a Set Normal Response Mode (SNRM) request when it receives a Disconnect Mode (DM) command response from a device. This line attribute is applicable only to primary lines. ON indicates that the primary station is to respond to DM with a SNRM command. OFF indicates that the primary station is not to respond to DM.
Attributes for SNAX/XF and SNAX/APN SSCPID - for SNAX/XF Only SSCPID - for SNAX/XF Only Default: 0 Value: 0 - 65535 Objects: SUBSYS SSCPID alters the subsystem services control point identifier (SSCP ID) of the SNAX/XF subsystem. The SSCP ID identifies the SSCP (in this case, the SNAX/XF service–manager process) that issues the ACTPU command, and is contained in bytes 3 through 8 of the SNA ACTPU command. Any alterations to this attribute must be made before the service manager is started.
Attributes for SNAX/XF and SNAX/APN STATION STATION Default: PRIMARY Value: PRIMARY | SECONDARY | NEGOTIABLE Objects: LINE STATION specifies whether the line is to act as a primary or a secondary link station. The following values are valid for this attribute: PRIMARY specifies that the line is to act as a primary station. SECONDARY specifies that the line is to act as a secondary station.
Attributes for SNAX/XF and SNAX/APN SWITCHED SWITCHED Default: OFF Value: ON | OFF Objects: LINE SWITCHED specifies whether the line is a switched line or a nonswitched line. ON indicates that the line is switched. OFF indicates that the line is nonswitched. For SDLC lines (line type 58,5 (SDLC)), the term “switched” refers to physical switching. For X.25 lines, a switched line uses X25AM switched virtual circuits (SVCs), and a nonswitched line uses X25AM permanent virtual circuits (PVCs).
Attributes for SNAX/XF and SNAX/APN SWOPMSG For LUs on switched lines, CONTROL 12 or CLOSE is required in order to break communication. The CONTROL 11 is not completed until a connection is established over the line, which could be a long time (hours or even days). For lines other than X.21, auto-answer or manual-answer modems are required. Autodial operations are not supported for switched SDLC lines. PU Type 1 devices are not supported for switched SDLC lines.
Attributes for SNAX/XF and SNAX/APN TG n - for SNAX/APN Only If the timer expires before a session begins, an EMS event message is displayed after the interval specified using SWSESSTIMEOUT. If no session begins and the connection remains active, the time-out event is repeated at ten-minute intervals.
Attributes for SNAX/XF and SNAX/APN TGCAPACITY - for SNAX/APN Only TGCAPACITY - for SNAX/APN Only Default: 9600 Range: MIN, MAX, 1200, 2400, 4800, 7200, 9600, 14400, 19200, 48000, 56000, 64000, 4M, 10M, 16M Objects: PU This represents the effective capacity of the TG. It is the highest bit-transmission rate that the TG will be allowed to obtain before being considered overloaded. TGCONNCOST - for SNAX/APN Only Default: 0 Range: 0 - 255 Objects: PU This represents the cost per connect time.
Attributes for SNAX/XF and SNAX/APN TIMEOUT TIMEOUT Default: 5 seconds Value: 0.01 seconds - 5 minutes, 27.67 seconds Objects: LINE TIMEOUT specifies the retransmit time-out value. The TIMEOUT attribute defines the amount of time a SNAX line handler waits for a valid SDLC frame in response to a READ or AUTOPOLL (primary line only) operation. SNAX uses the TIMEOUT value to set the T1 timer.
Attributes for SNAX/XF and SNAX/APN TPF - for SNAX/APN Only TPF - for SNAX/APN Only Default: MED Value: LOW | MED | HI Objects: LU TPF (Transmission Priority Field), as defined by SNA, specifies the priority of sessions created on this LU relative to the priority of sessions on other LUs. TPF is an optional attribute. The following values are valid for the TPF attribute: LOW specifies that sessions created on this LU have a low priority relative to other sessions.
Attributes for SNAX/XF and SNAX/APN TRMAXRETRY TRMAXRETRY TRMAXRETRY is replaced by LNMAXRETRY on page 14-30. For backward compatibility with existing configurations, SCF accepts TRMAXRETRY on the ADD or ALTER PU command, but you are encouraged to use LNMAXRETRY for new and altered Token-Ring configurations. The SCF INFO PU, DETAIL always displays LNMAXRETRY; it no longer displays TRMAXRETRY. TRRMTADDR TRRMTADDR is replaced by LNRMTADDR on page 14-30.
Attributes for SNAX/XF and SNAX/APN TWS TWS Default: OFF Value: ON | OFF Objects: LINE TWS specifies whether or not two-way simultaneous communication can occur. ON indicates two-way simultaneous communication. OFF indicates two-way alternate communication. If TWS ON is specified, two-way, simultaneous communication can occur on the line. If TWS OFF is specified, only two-way, alternate (TWA) communication can occur.
Attributes for SNAX/XF and SNAX/APN TYPE (Local LU Objects) - for SNAX/APN 3650 Retail Store System 3660 Supermarket System 3730 Distributed Office Communication System 3790 Processor System 4700 Financial Communication System 8100 Processor System 1 defines the formats and protocols for SNA support of a Remote Job Entry (RJE) workstation operating in a batch environment.
Attributes for SNAX/XF and SNAX/APN TYPE (Remote LU Objects) - for SNAX/APN TYPE (Remote LU Objects) - for SNAX/APN Default: None Value: ( 14, { 0 | 1 | 2 | 3 | 4 | 21 } ) Objects: LU When applied to remote LU objects, TYPE specifies the device type (always 14) and subtype for a remote LU. For SNAX/APN, the subtype values include: 0 provides a generalized, user-definable process-to-process communications capability for applications.
Attributes for SNAX/XF and SNAX/APN WINDOW These integer values are specified following the number 13 and a comma and surrounded by parentheses such as TYPE (13, 2). The number 13 is the PU device type. WINDOW Default: 7 Value: 1 - 7 Objects: LINE, PU WINDOW specifies the maximum number of SDLC I-frames that SNAX can send to or receive from a remote station before SNAX must receive (or send) an acknowledgment of their error-free receipt.
Attributes for SNAX/XF and SNAX/APN X21NRDY X21NRDY Default: OFF Value: ON | OFF Objects: LINE This attribute only applies to unsupported X.21 switched lines. The attribute description is given because the attribute appears in SCF INFO LINE, DETAIL displays. X21NRDY specifies the type of DTE not ready signal the X.21 DTE sends when entering the quiescent state. ON indicates that the X.21 DTE sends a “DTE NOT READY—CONTROLLED” signal.
Attributes for SNAX/XF and SNAX/APN X21T3ATIMEOUT X21T3ATIMEOUT Default: 2 seconds Value: 0 - 10:55.35 Objects: LINE This attribute only applies to unsupported X.21 switched lines. The attribute description is given because the attribute appears in SCF INFO LINE, DETAIL displays. X21T3ATIMEOUT specifies the T3A time limit that the X.21 DTE uses when waiting for a DCE response during call establishment. T3A represents the T3A timer. This attribute applies only to SDLC lines.
Attributes for SNAX/XF and SNAX/APN X21T5TIMEOUT The valid range of values for this attribute is 0 through 10 minutes, 5 seconds, and 35 hundredths of a second (0 through 10:5.35). If the value specified is 0, ADCCP does not use the specific T4 timer during the X.21 call establishment process. X21T5TIMEOUT Default: 2 seconds Value: 0 - 10:55.35 Objects: LINE This attribute only applies to unsupported X.21 switched lines.
Attributes for SNAX/XF and SNAX/APN XMITIMEOUT X21T7TIMEOUT specifies the T7 time limit that the X.21 DTE uses when waiting for a DCE response during call establishment. T7 represents the T7 timer. This attribute applies only to SDLC lines. The valid range of values for this attribute is 0 through 10 minutes, 5 seconds, and 35 hundredths of a second (0 through 10:5.35). If the value specified is 0, ADCCP does not use the specific T7 timer during the X.21 call establishment process.
Attributes for SNAX/XF and SNAX/APN XPAGES (SUBSYS Object) XPAGES (SUBSYS Object) Default: EXTPOOLPAGES value in the PROFILE object, or 2000 Value: 1 - 8192 Objects: SUBSYS For the SUBSYS object, XPAGES specifies the maximum number of 1024-word pages of memory that can be allocated in the extended data segment. The extended data segment is used to store line, PU, and LU resource control blocks (RCBs). Because no swap file is defined to back up this memory, in-use pages are locked.
15 PTrace Reference for SNAX/XF and SNAX/APN This section provides information about the use of the PTrace utility to display information from traces of SNAX lines and the service manager. It includes subsystem-specific information about PTrace commands and displays. It also explains how the TRACE command and the PTrace utility work together.
PTrace Reference for SNAX/XF and SNAX/APN How to Record and Display Trace Data How to Record and Display Trace Data Figure 15-1 shows the four general steps used to record and format trace data. Figure 15-1. Recording and Formatting Trace Data Start the trace with the SCF TRACE command. Collect trace data. Stop the trace with the SCF TRACE command. Format the trace file with PTrace. VST1501.vsd 1. Start the trace using the SCF TRACE command.
PTrace Reference for SNAX/XF and SNAX/APN Device Types and Subtypes The following information is displayed: Ptrace - Trace Formatter - T9385G05 - (15APR03) - (06FEB03) Copyright Compaq Computer Corporation 1997-2000 Next, use PTrace commands to display selected trace records. The command used in the following example displays only level-4 Basic Information Units (BIUs) from the trace file specified in the earlier TRACE command: FROM $DATA.WORK.
PTrace Reference for SNAX/XF and SNAX/APN Using TRACE and PTrace for Line Traces When examining the trace file using PTrace, you can choose among a number of PTrace SELECT or SELMASK options to display only specified types of trace records. For service manager traces, you can also use FILTER options to limit the information displayed. Using TRACE and PTrace for Line Traces For all SNAX lines, the line handler traces upper-level activity and some lower-level activity.
PTrace Reference for SNAX/XF and SNAX/APN SNAX Architectural Overview be submitted to HP. In PTrace, you can either view all trace records (with the SELECT ALL command) or use the SELMASK command to select specific types of records. SNAX Architectural Overview SNAX traces record messages sent between processes and controllers on NonStop systems, and also messages sent and events occurring within various parts of the SNAX software.
PTrace Reference for SNAX/XF and SNAX/APN Message-System Overview LU Network Services (LUNS) Passthrough control The service manager receives protocol communications from the line handler through SNAX level 4. It receives SPI requests and responses, from SCF and other management applications, through the Subsystem Control Point (SCP). The service-manager functions do not generate separate trace-record types.
PTrace Reference for SNAX/XF and SNAX/APN PTrace Commands PTrace Commands The following PTrace commands are supported for SNAX traces: ALLOW COUNT DESELECT DETAIL EBCDIC ENV EXIT FC FILTER FIND FROM Fn HELP HEX LABEL LIMIT LOG NEXT OBEY OCTAL OUT PAGESIZE RECORD RESET SELECT SELMASK SETTRANSLATE STATETABLES TEXT TIMESTAMP TRANSLATE The DETAIL command applies only to line traces, not to service-manager traces, and is generally useful only to HP personnel.
PTrace Reference for SNAX/XF and SNAX/APN FILTER Command The syntax of the FILTER command for service-manager traces is as follows: FILTER filter-option filter-option is one of the following: INTTRACE { ON | OFF } MSGCB { ON | OFF } SPI { ON | OFF } SPIDETAIL { ON | OFF } DETAIL { ON | OFF } SHOW HELP INTTRACE { ON | OFF } enables (with ON) or disables (with OFF) display of the contents of an internal trace buffer that contains procedure and subprocedure calls.
PTrace Reference for SNAX/XF and SNAX/APN FILTER Command HELP displays a help screen for the FILTER options for service manager traces. Operational Notes For service manager traces, only one FILTER option can be specified per command. Setting a FILTER option flag to ON enables the display of the specified trace information; setting it to OFF disables the display of that information. In the case of SPI and SPIDETAIL, setting one flag to ON also automatically sets the other flag to OFF.
PTrace Reference for SNAX/XF and SNAX/APN FILTER Command The following example shows the information displayed for a service manager trace record when the SPI option is set to ON: 01/14/93 19:00:38.574969 >000.000000 #12 Record Type : 000 RQRCVD^TRACE^ID SVM +%52346 LISTEN WRITEREAD LCB: 027610 P1-P6: 140403 000474 000212 012000 000145 000000 LCB.
PTrace Reference for SNAX/XF and SNAX/APN FILTER Command The following example shows the information displayed for a service manager trace record when the SPIDETAIL option is set to ON: >000.000000 #12 Record Type : 000 RQRCVD^TRACE^ID SVM +%52346 LISTEN WRITEREAD LCB: 027610 P1-P6: 140403 000474 000212 012000 000145 000000 LCB.
PTrace Reference for SNAX/XF and SNAX/APN SELECT and SELMASK Commands To disable display of all special FILTER-option fields in service manager trace records, use the following PTrace command: FILTER DETAIL OFF SELECT and SELMASK Commands The SELECT and SELMASK commands in PTrace allow you to specify particular types of records in the trace file for display, thus reducing the number of records you see and limiting them to those that are likely to be of interest to you.
PTrace Reference for SNAX/XF and SNAX/APN SELECT and SELMASK Commands number is an integer identifying a SNAX trace-record type. The meaning of each type of SNAX trace record is explained in the last part of this section. Note that the interpretation of the trace-record type number depends on whether the trace file being examined is a line trace or a service manager trace. keyword is ALL, CURRENT, or one of the subsystem-specific keywords listed in Tables 5-2 through 5-7.
PTrace Reference for SNAX/XF and SNAX/APN SELECT and SELMASK Commands Table 15-2.
PTrace Reference for SNAX/XF and SNAX/APN SELECT and SELMASK Commands For the service manager, no subsystem-specific SELECT keywords are available; you must use the SELMASK command to select specific types of service manager trace records. (The SELECT ALL option is available, however, and in most cases this is the recommended selection for service manager traces.) Table 15-4.
PTrace Reference for SNAX/XF and SNAX/APN STATETABLES Command The following command selects the trace records for SPI requests and responses and the resulting control and inquiry responses in a SUBSYS (service manager) trace file: SELMASK %H03000000 The following command selects all trace records in any trace file: SELECT ALL (You can get the same result by omitting the SELECT ALL command, since SELECT ALL is the default.
PTrace Reference for SNAX/XF and SNAX/APN Trace-File Header Record The remainder of this section describes the displays of the trace-file header record and of each type of SNAX trace record. Note. The formatted trace files created for you by the SCF TRACE command may not be displayed exactly as documented in this manual. This manual covers both SNAX/XF and SNAX/APN subsystems. The example traces may have been derived from either product.
PTrace Reference for SNAX/XF and SNAX/APN Trace-File Header Record First trace entry: is the timestamp of the first data record in the file: that is, the date and time when the first trace record was captured. If this timestamp is significantly different from the timestamp given for Trace started:, a wrap condition may have occurred; for details, see the description of the TRACE command WRAP option in Section 12, Objects for SNAX/XF and SNAX/APN.
PTrace Reference for SNAX/XF and SNAX/APN Basic Parts of a Trace-Record Display Basic Parts of a Trace-Record Display The display of each individual SNAX trace record has several basic parts, which are shown in the following example: 11/05/92 12:00:29.229737 Record Type : 004 >000.
PTrace Reference for SNAX/XF and SNAX/APN Individual Trace-Record Descriptions first identify whether the trace is a service manager trace or a line trace. This is indicated by the device type and subtype in the trace-file header record. is the verbal identifier corresponding to the trace-record subtype, which further qualifies the type of information contained in the trace record. This field is included only for trace-record types that have subtypes. The possible subtypes depend on the trace-record type.
PTrace Reference for SNAX/XF and SNAX/APN Line-Handler Trace Records Line-Handler Trace Records The following pages describe the trace records generated by the line handler for all types of lines. 003: PIU^TRACE^ID (PIU In) This trace record contains the inbound path information unit (PIU) received by SNAX level 3 from SNAX level 2. This trace record consists of the transmission header (TH), the request/response header (RH), and the request/response unit (RU).
PTrace Reference for SNAX/XF and SNAX/APN 003: PIU^TRACE^ID (PIU In) flow indicator bit is 1. The origin address field is 2, the destination address field is 1, and the sequence number is 0. REQ FMD FI BC EC DR1I is a symbolic representation of the contents of the request/response header (RH), using the standard IBM abbreviations. This line is interpreted as follows: REQ, +RSP, or -RSP indicates a request, positive response, or negative response, respectively.
PTrace Reference for SNAX/XF and SNAX/APN 003: PIU^TRACE^ID (PIU Out) 003: PIU^TRACE^ID (PIU Out) This trace record contains the outbound path information unit (PIU) sent by SNAX level 3 to SNAX level 2. This trace record consists of the transmission header (TH), the request/response header (RH), and the request/response unit (RU). Record Type : 003 PIU^TRACE^ID PIU Out for PU index 193.
PTrace Reference for SNAX/XF and SNAX/APN +RSP SC 003: PIU^TRACE^ID (PIU Out) FI BC EC DR1I is a symbolic representation of the contents of the request/response header (RH), using the standard IBM abbreviations. This line is interpreted as follows: REQ, +RSP, or -RSP indicates a request, positive response, or negative response, respectively. FMD, NC, DFC, or SC indicates the request/response unit (RU) category.
PTrace Reference for SNAX/XF and SNAX/APN 004: BIU^TRACE^ID (BIU In) 004: BIU^TRACE^ID (BIU In) This trace record contains the inbound basic information unit (BIU) received by SNAX level 4 from SNAX level 3. The BIUthat is, the request/response header (RH) followed by the request/response unit (RU)is preceded by the first six bytes of the SNAX header described in the SNAX/XF Application Programming Manual and the SNAX/APN Application Programming Manual.
PTrace Reference for SNAX/XF and SNAX/APN 004: BIU^TRACE^ID (BIU Out) request or RU: nnnnnn if present, gives additional information from the beginning of the RU. If the BIU contains an SNA request (or a response to an SNA request) such as ACTPU, ACTLU, or BIND, the abbreviation for the request appears here. If the BIU contains invalid or unrecognized data, the display shows RU: followed by the first six bytes of the RU in hexadecimal.
PTrace Reference for SNAX/XF and SNAX/APN 004: BIU^TRACE^ID (BIU Out) OAF: #nnn gives the value of the origin address field. BIU bytes: nn gives the number of bytes of data in this trace record, including the BIU and the six bytes of SNAX header. This is the total length of the data, even if a small RECSIZE value in the TRACE command caused the data in the trace record to be truncated.
PTrace Reference for SNAX/XF and SNAX/APN 008: L2^SCHED^TRACE^ID 0380 80 is the RH. 35 471D ... is the RU. 008: L2^SCHED^TRACE^ID This trace record indicates that the scheduler within the line handler has dispatched a request to SNAX level 2 for processing. Record Type : 008 L2^SCHED^TRACE^ID DPCL: TSIOS -> L2 L2^OutIntrpt DPCL: indicates that an internal procedure was called within SNAX to dispatch the request. TSIOS -> L2 identifies the source and destination of the request within SNAX.
PTrace Reference for SNAX/XF and SNAX/APN 010: L4^SCHED^TRACE^ID Msg: %nnnnnn.nnnnnn is information for HP internal use. RscID: %nnnnnn is information for HP internal use. 010: L4^SCHED^TRACE^ID This trace record indicates that the scheduler within the line handler has dispatched a request to SNAX level 4 for processing. Record Type : 010 L4^SCHED^TRACE^ID DPCL: L5-T2 -> L4 L4^SendBIU Msg: %000022.
PTrace Reference for SNAX/XF and SNAX/APN 012: L6^SCHED^TRACE^ID CRT -> L5-T2 identifies the source and destination of the request within SNAX. In this case, the request is from the CRT protocol to level 5 (for PU type 2). L5^OutReq identifies the internal level-5 request being dispatched. Msg: %nnnnnn.nnnnnn is information for HP internal use. RscID: %nnnnnn is information for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN 014: L2^DISPQ^TRACE^ID 014: L2^DISPQ^TRACE^ID This trace record indicates that the line handler has queued a message from SNAX level 2 for eventual internal dispatch. Record Type : 014 L2^DISPQ^TRACE^ID Q IO: L2 -> L3 L3^LineUp Msg: %000000.000000 RscID: %000000 Q IO: identifies the internal queue to which this message has been added.
PTrace Reference for SNAX/XF and SNAX/APN Q 016: L4^DISPQ^TRACE^ID IO: identifies the internal queue to which this message has been added. The queue identifier is one of the following: IO I/O queue (highest priority) EXP Expedited queue (next-highest priority) NRM Normal queue (lowest priority) L3 -> L2 identifies the source and destination of the request within SNAX. In this case, the request is from level 3 to level 2. L2^Write identifies the internal request being queued. Msg: %nnnnnn.
PTrace Reference for SNAX/XF and SNAX/APN 017: L5^DISPQ^TRACE^ID L3^Send^Biu identifies the internal request being queued. Msg: %nnnnnn.nnnnnn is information for HP internal use. RscID: %nnnnnn is information for HP internal use. 017: L5^DISPQ^TRACE^ID This trace record indicates that the line handler has queued a message from SNAX level 5 for eventual internal dispatch. Record Type : 017 L5^DISPQ^TRACE^ID Q NRM: L5-T2 -> L4 L4^SendBIU Msg: %000022.
PTrace Reference for SNAX/XF and SNAX/APN 018: L6^DISPQ^TRACE^ID 018: L6^DISPQ^TRACE^ID This trace record indicates that the line handler has queued a message from SNAX level 6 for eventual internal dispatch. Record Type : 018 L6^DISPQ^TRACE^ID Q EXP: CRT -> L5-T2 L5^OutReq Msg: %000000.000000 RscID: %000002 Q EXP: identifies the internal queue to which this message has been added.
PTrace Reference for SNAX/XF and SNAX/APN 020: L2^STATE^TRACE^ID 020: L2^STATE^TRACE^ID This trace record indicates a state transition within the level-2 state machine. Each line type has a different state machine. Record Type : 020 L2^STATE^TRACE^ID L2 State: %014565 Event: #01 PU: C8 The contents of this trace record are for HP internal use. 021: L3^STATE^TRACE^ID This trace record indicates a state transition within the level-3 state machine.
PTrace Reference for SNAX/XF and SNAX/APN 034: MS^LINK^TRACE 034: MS^LINK^TRACE This trace record contains the results of a message-system LINK for a request sent by the line handler to the X25AM I/O process. It applies only to X.25 lines. Record Type : 034 MS^LINK^TRACE MSPROCS LINK TS -> X25 TSX25^SENDDATA LCB: 041742 P1-P6: 140460 000026 000001 000002 000024 000001 LCB.LTRAN: #0020 LCB.
PTrace Reference for SNAX/XF and SNAX/APN 035: MS^WRITELINK^TRACE P1-P6: nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn gives the values of the control fields in the MSGCB. These fields are for HP internal use. LCB.LTRAN: #nnnn has no meaning for D-series systems. LCB.LLIM: #nnnn has no meaning for D-series systems. 0000 2D00 ... is the data in the LINK message. This data is for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN 036: MS^LDONE^TRACE Matching Record Number Is: #nnnnn if present, identifies the record number (in this trace file) of the trace record for the corresponding message-system LISTEN. If no matching record is found, *** Matching Record Number Not Found *** is displayed. LCB: nnnnnn gives the address of the message-system control block (MSGCB) within SNAX. This address matches the MSGCB address displayed in the trace record for the corresponding request from X25AM.
PTrace Reference for SNAX/XF and SNAX/APN 038: MS^LCAN^OUTGOING^TRACE TSX25^SENDDATA identifies the corresponding level-2 request, which is one of the following: TSX25^ALLOW^CALLIN Allow call-in TSX25^ATTACH Attach TSX25^CALLACCEPT Call accept TSX25^CALLCLEAR Call clear TSX25^CALLOUT Call out TSX25^DETACH Detach TSX25^SENDDATA Send data Matching Record Number Is: #nnnnn if present, identifies the record number (in this trace file) of the trace record for the corresponding message-system LINK
PTrace Reference for SNAX/XF and SNAX/APN 039: MS^INCOMING^REQ^TRACE have been sent by SNAX level 2 to the X25AM I/O process for a particular path (PU-toX25AM-subdevice association). It applies only to X.25 lines. Record Type : 038 MS^LCAN^OUTGOING^TRACE MSPROCS LCAN OUTGOING LCB: 041742 P1-P6: 000000 000026 000001 000002 000000 000001 LCB.LTRAN: #0000 LCB.LLIM: #0000 MSPROCS is an identifier for HP internal use. LCAN indicates that the message-system LCAN function was invoked.
PTrace Reference for SNAX/XF and SNAX/APN 039: MS^INCOMING^REQ^TRACE L2 indicates that this is a request reported by SNAX level 2. MSCB RECEIVED indicates that level 2 received a message through its internal message interface. X25 -> TS identifies the source and destination of the message-system request. For this trace-record type, the source is always X25 (X25AM) and the destination is always TS (the line handler).
PTrace Reference for SNAX/XF and SNAX/APN 040: MS^REPLY^TRACE P1-P6: nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn gives the values of the control fields in the message-system control block (MSGCB). These fields are for HP internal use. REQ SIZE: #nnnn gives the length, in bytes, of the data received in the incoming request. MAX REPLY SIZE: #nnnn gives the maximum length, in bytes, allowed for outgoing reply data. 0100 1214 ... if present, is the data in the incoming request. This data is for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN 040: MS^REPLY^TRACE X25TS^RECDATA identifies the type of request being replied to, which is one of the following: X25TS^CALLCLEAR Call clear X25TS^RECDATA Data REQID: nnnnnn nnnnnn is the number used by the line handler to identify the request being replied to. This number matches the REQID displayed in the type 39 trace record for the corresponding request.
PTrace Reference for SNAX/XF and SNAX/APN 041: MS^SEND^DATA^TRACE 041: MS^SEND^DATA^TRACE This trace record contains outgoing data sent by SNAX level 2 to the X25AM I/O process. It applies only to X.25 lines.
PTrace Reference for SNAX/XF and SNAX/APN 042: MS^SEND^DATA^COMPLETION^TRACE Data for trace records displaying request type TSX25^SENDDATA, further identifies the type of request being sent to X25AM. This field has one of the following values: Data Data Disc Disconnect Setmode SETMODE Test Test message XID Exchange identification REQID: nnnnnn nnnnnn is a number used by the line handler to identify this request.
PTrace Reference for SNAX/XF and SNAX/APN 042: MS^SEND^DATA^COMPLETION^TRACE MSCB LDONE indicates that the message-system LDONE function was invoked through the internal message interface to SNAX level 2. ORIGINAL REQUEST introduces information about the original request being replied to. TS -> X25 identifies the source and destination of the original request being replied to. For this trace-record type, the source is always TS (the line handler), and the destination is always X25 (X25AM).
PTrace Reference for SNAX/XF and SNAX/APN 043: MS^OPEN^TRACE REQID: nnnnnn nnnnnn is the number used by the line handler to identify the request and its corresponding reply. This number matches the REQID for the corresponding request, as displayed above and in the corresponding type 41 trace record. P1-P6: nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn nnnnnn gives the values of the control fields in the message-system control block (MSGCB) for the reply. These fields are for HP internal use. nnnn nnnn ...
PTrace Reference for SNAX/XF and SNAX/APN LDEV 044: MS^CLOSE^TRACE nn gives the logical device (LDEV) number returned on the OPEN request. SYSNUM nnn gives the system number of the system where the X25AM subdevice resides. LFILE ID nnnn gives an internal reference number identifying the path (PU-to-X25AM-subdevice association) that has been established.
PTrace Reference for SNAX/XF and SNAX/APN 088: SNAXFLAGS^TRACE^ID 088: SNAXFLAGS^TRACE^ID This trace record is created every time one of the line state flags (called SNAXFLAGS) changes state.
PTrace Reference for SNAX/XF and SNAX/APN 106: DXX^FILEREP^ ITI identifies the protocol that initiated the request. This field displays one of the following: CRT CRT protocol CRT30 CRT protocol for 65xx devices ITI ITI protocol ITI30 ITI protocol for 65xx devices PRT Printer protocol SNALU SNALU protocol File Request indicates that this trace record contains information about a file-system request. SWITCH identifies the file-system request made on behalf of the application.
PTrace Reference for SNAX/XF and SNAX/APN 106: DXX^FILEREP^ ITI identifies the protocol that made the request being replied to. This field displays one of the following: CRT CRT protocol CRT30 CRT protocol for 65xx devices ITI ITI protocol ITI30 ITI protocol for 65xx devices PRT Printer protocol SNALU SNALU protocol WRITELINK indicates that the message-system WRITELINK function was invoked. FEMODEMERR is the literal associated with the file-system error number returned.
PTrace Reference for SNAX/XF and SNAX/APN 125: DXX^ANYONE^TO^TS 125: DXX^ANYONE^TO^TS This trace record indicates that the line handler has retrieved an incoming request from another process, such as the service manager or X25AM, via the message-system LISTEN function. Record Type : 125 DXX^ANYONE^TO^TS LISTEN GETMODE MSGCB: %000017.
PTrace Reference for SNAX/XF and SNAX/APN 127: DXX^TS^TO^TS TS -> SSCP identifies the source and destination of the request within SNAX. For this tracerecord type, the source is always TS (the line handler), and the destination is always SSCP (the service manager). WRITE identifies the type of service being requested by the line handler. This information is for HP internal use. MSGCB: %nnnnnn.nnnnnn gives the address of the message-system control block (MSGCB) within SNAX.
PTrace Reference for SNAX/XF and SNAX/APN 128: DXX^SVC^MGR^TO^TS If the trace record contains a checkpoint request, the text CHECKPOINT CODE = # nnnnn is displayed instead, providing information about the checkpoint. This information is for HP internal use. CONTROL identifies the type of service being requested. For a passthrough message, this field identifies the type of passthrough request, as listed in the description of tracerecord type 129.
PTrace Reference for SNAX/XF and SNAX/APN 129: DXX^PASSTHRU^MSG SSCP -> TS identifies the source and destination of the request within SNAX. For this tracerecord type, the source is always SSCP (the service manager) and the destination is always TS (the line handler). CONTROL identifies the service being requested by the service manager. This information is for HP internal use. MSGCB: %nnnnnn.nnnnnn gives the address of the message-system control block (MSGCB) within SNAX.
PTrace Reference for SNAX/XF and SNAX/APN 129: DXX^PASSTHRU^MSG TSPT^REQ is the trace-record subtype, identifying the type of passthrough message. The subtype is one of the following: TSPT^REQ Passthrough initiation request TSPT^RSP Passthrough initiation response TSPT^DATA Passthrough data TSPT^SON Notification of passthrough session outage PassThru Init identifies the current stage of passthrough communication.
PTrace Reference for SNAX/XF and SNAX/APN 130: DXX^OPEN^REQUEST 130: DXX^OPEN^REQUEST This trace record contains a file-system request to open a logical unit (LU), received by SNAX level 4 on behalf of an application. Record Type : 130 DXX^OPEN^REQUEST OPEN REQUEST OPEN MSGCB: %000017.
PTrace Reference for SNAX/XF and SNAX/APN 131: DXX^LDONE^TRACE^ID 0000 0000 ... is the contents of the open request. The LU name can be read in the ASCII display. 131: DXX^LDONE^TRACE^ID This trace record contains the results of the message-system LDONE function invoked by the line handler in completion of a message-system LINK. Record Type : 131 DXX^LDONE^TRACE^ID MSGCB LDONE FEINVALOP FOR Request: #0200 WRITE MSGCB: %000017.
PTrace Reference for SNAX/XF and SNAX/APN 171: ANYONE^TO^TS^NZERO MSGCB: %nnnnnn.nnnnnn gives the address of the message-system control block (MSGCB) within SNAX. This address matches the MSGCB address displayed in the corresponding LINK trace record. LINKER: #nn,#nnnn LISTENER: #nn,#nnnn gives internal message-system information. These fields are for HP internal use. 0000 0000 ... if present, is the data in the LDONE message.
PTrace Reference for SNAX/XF and SNAX/APN 172: FILRPL^TRACE^ID^NZERO This trace record applies only to line type 58,5. 04/15/96 22:57:36.105120 >000.
PTrace Reference for SNAX/XF and SNAX/APN 173: TS^TO^CONMGR 173: TS^TO^CONMGR This trace record contains a message sent by the line handler to the Concentrator Manager process. This trace record applies only to line type 58,5. 04/15/96 22:57:07.542029 >000.000000 #19 Record Type : 173 TS^TO^CONMGR LINK TS -> CONMGR IOP_CONMGR_ACTIVATE_PATH MSGCB: %000016.
PTrace Reference for SNAX/XF and SNAX/APN 249: CLB^OUT^TRACE^ID 01: is the link station identifier (station ID). ReceivedText is the CLB function: in this case, a response from the remote Synchronous Data Link Control (SDLC) station. A trace record with CLB function TextSent shows a reply from the CLIP indicating that an outgoing path information unit (PIU) has been sent correctly. Frame bytes: nn gives the total number of bytes of data received from the CLIP. 0186 012C ...
PTrace Reference for SNAX/XF and SNAX/APN 255: CLIP^TRACE^BLOCK The information in this trace record is divided into a number of subrecords of various types, representing level-1 and level-2 events occurring within the CLIP. Each subrecord begins with a timestamp, and the data, if any, is displayed in hexadecimal, ASCII, and EBCDIC form. The types of subrecords included depend on the selection criteria (SELECT keywords or SELMASK bits) given in the SCF TRACE command used to collect the trace.
PTrace Reference for SNAX/XF and SNAX/APN 255: CLIP^TRACE^BLOCK Record Type : 255 CLIP^TRACE^BLOCK ===== Clip Trace Block ==================================== 17:13:56.73 L2 State: #22 17:13:56.74 L1 State: #3 Event: #4 Event: #12 17:13:56.74 SDLC Out C8: I0,0 C800 2D00 0000 0002 6B80 0011 0101 0500 ! ! 0000 0000 ! ! - k Frame bytes: 20 !H , ! 17:13:56.75 U(08) DMA write completion. 17:13:56.75 L1 State: #4 Event: #7 17:13:56.75 L1 State: #3 Event: #11 17:13:56.
PTrace Reference for SNAX/XF and SNAX/APN 17:13:56.74 L1 255: CLIP^TRACE^BLOCK State: #3 Event: #12 is a subrecord indicating a state transition within the CLIP level-1 state machine. The information in this record is for HP internal use. 17:13:56.74 SDLC Out C8: I0,0 ... is a subrecord containing an outgoing SDLC frame. C8 is the address field (PU address) of the frame. I0,0 describes the contents of the control field.
PTrace Reference for SNAX/XF and SNAX/APN 17:13:56.75 U(08) 255: CLIP^TRACE^BLOCK DMA write completion. is a subrecord indicating that the SDLC frame data in the preceding subrecord has been successfully clocked out on the line. The next four subrecords are for additional CLIP level-1 and level-2 state-machine events, as previously described. 17:13:56.75 SDLC Out C8: RR0-P ... is another subrecord containing an outgoing SDLC frame.
PTrace Reference for SNAX/XF and SNAX/APN 255: CLIP^TRACE^BLOCK For an unnumbered frame, the abbreviation for the SDLC command or response (for example, SNRM or UA) appears following the letter U. For all three types of frames, the presence of the characters -P or -F indicates that the poll/final (P/F) bit is set; the absence of these characters indicates that the poll/final bit is not set.
PTrace Reference for SNAX/XF and SNAX/APN Service-Manager Trace Records Service-Manager Trace Records The following pages describe the trace records generated by the service manager. SVM 004: GETLOCPOOL^TRACE^ID This trace record indicates that the service manager has obtained memory pool space from the local (stack) pool. Record Type : 004 GETLOCPOOL^TRACE^ID NCS^CMP^PROCESS +%70313 GET^LPOOL ba: %022177 words: 111 The contents of this trace record are for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN SVM 009: OPIRSP^TRACE^ID from another process such as the Subsystem Control Facility (SCF) or an SPI management application. Record Type : 008 OPIREQ^TRACE^ID OPI^PROCESS +%16743 OPI^REQ %000010.007632 VERB: ZCOM^CMD^ADD OBJ TYPE: ZCOM^OBJ^LINE OBJ: $SNAP1 RVT^INDEX: 000 EXTENDED POOL ATTR^L %000010.
PTrace Reference for SNAX/XF and SNAX/APN SVM 010: NCS1^TRACE^ID SVM 010: NCS1^TRACE^ID This trace record contains the error code resulting from the service manager’s interpretation of a SPI request. There may be further status information pending if further processingfor example, by a line handleris under way or pending; such further processing is reported in a separate trace record of type 11. Record Type : 010 NCS1^TRACE^ID SVM +%76432 NCS^IMM^RSP REQ: %000010.
PTrace Reference for SNAX/XF and SNAX/APN SVM 014: RQB^TRACE^ID SVM 014: RQB^TRACE^ID This trace record contains control and data information for an outbound message. Record Type : 014 RQB^TRACE^ID SVM +%00007 Request Queue Block (RQB) P1-P6: 140452 000020 000031 000000 000310 RQB: 000010.
PTrace Reference for SNAX/XF and SNAX/APN SVM 017: RQSEND^NZERO^TRACE^ID RQBN The message was dequeued by SNAX without attempting to send it via LINK. RQBQ The message will be sent later via LINK. RQBR The message completed with LDONE and a retryable error. The LINK will be retried. SVM 017: RQSEND^NZERO^TRACE^ID This trace record contains information for an outbound message to the backup line handler. 04/12/96 10:52:02.977449 >000.
PTrace Reference for SNAX/XF and SNAX/APN SVM 018: RQLDON^NZERO^TRACE^ID SVM 018: RQLDON^NZERO^TRACE^ID This trace record contains a message-system LDONE message received by the service manager from another process, confirming that the other process has received and processed a message previously sent via LINK. 04/12/96 10:52:02.978573 >000.
PTrace Reference for SNAX/XF and SNAX/APN SVM 019: FILRPL^NZERO^TRACE^ID SVM 019: FILRPL^NZERO^TRACE^ID This trace record contains the results of a message-system WRITELINK from the service manager to another process, sent in reply to a previous request that arrived via LISTEN.
PTrace Reference for SNAX/XF and SNAX/APN SVM 020: RQRCVD^NZERO^TRACE^ID SVM 020: RQRCVD^NZERO^TRACE^ID This trace record signifies the receipt of a Sierra (DEVINFO) request from a PUP replacement process. 04/12/96 10:51:25.989112 >000.000000 #12 Record Type : 020 RQRCVD^NZERO^TRACE^ID LISTEN SYSTEMSTATUS_SYSMSG_WAIT MSGCB: %045000.
PTrace Reference for SNAX/XF and SNAX/APN Request: #0003 SVM 101: DXX^REPLY^REQ^TRACE^ID REQ_WRITEREAD indicates that a WRITEREAD file-system request was sent to the service manager. The numeric code corresponds to the literal for the request. MSGCB: %nnnnnn.nnnnnn gives the address of the message-system control block (MSGCB) within SNAX. This address matches the MSGCB address displayed in the WRITELINK or LDONE trace record for the incoming message. FFE4 1400 ... is the incoming data.
PTrace Reference for SNAX/XF and SNAX/APN SVM 102: DXX^SEND^REQ^TRACE^ID Matching Record Number Is: #nnnnn if present, identifies the record number (in this trace file) of the trace record for the corresponding message-system LISTEN. If no matching record is found, *** Matching Record Number Not Found *** is displayed. FFE4 13D6 ... is the data transferred in the WRITELINK. This data is for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN SVM 103: DXX^LDONE^REQ^TRACE^ID 0000 0000 ... is the data in the LINK message. If SNA abbreviations are displayed above the data, indicating that the message contains a PIU, the breakdown of this data is as explained in the description of trace records 3 and 103 (PIU In). Otherwise, this data is for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN P1X = %000000 P4X = %000002 P2X P5X = %000051 = %000000 SVM 103: DXX^LDONE^REQ^TRACE^ID P3X = %000001 P6X = %000001 gives the values of the control fields in the MSGCB. These fields are for HP internal use. nnnn nnnn ... if present, is the data in the LDONE message. This data is for HP internal use.
PTrace Reference for SNAX/XF and SNAX/APN SVM 103: DXX^LDONE^REQ^TRACE^ID SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 15-80
A Session Establishment This section documents the details of session establishment for each scenario. SNAX/XF Primary Lines On SNAX/XF primary lines, the SNAX/XF LU is always the primary LU. LU Acquire The sequence of events varies between SNALU applications (including SNAX/HLS and SNAX/APC) and applications using CRT, ITI or PRT, as shown in Figure A-1. Figure A-1.
Session Establishment SNAX/XF Primary Lines LU Accept Without a Creator Process The sequence of events varies between SNALU applications (including SNAX/HLS and SNAX/APC) and applications using CRT or ITI, as shown in Figure A-2. Figure A-2.
Session Establishment SNAX/XF Primary Lines LU Accept With a Creator Process Creator processes (SNAX Creator-2 or the original Creator) operate only with CRT or ITI applications. The sequence of events is shown in Figure A-3. Figure A-3. SNAX/XF Primary Line: LU Accept With a Creator Process SNAX/XF Remote LU Character-coded logon or INIT-SELF request Creator or SNAX Creator-2 Logon request (Start application) CRT/ITI Application OPEN WRITE/WRITEREAD (LU Object) (LU Object) BIND request VSTA03.
Session Establishment SNAX/XF Secondary Lines SNAX/XF Secondary Lines For SNAX/XF secondary lines, the SNA host LU is always the primary LU. The application protocol is always SNALU (the application may use SNALU, SNAX/HLS or SNAX/APC as the API). LU Acquire The sequence of events is shown in Figure A-4. Figure A-4.
Session Establishment SNAX/XF Passthrough SNAX/XF Passthrough For SNAX/XF passthrough, the SNA host LU is always the primary LU. Sessions Initiated by SNA Host LU The SNA host application sends a BIND request to a SNAX/XF gateway LU, as shown in Figure A-6. Figure A-6. SNAX/XF Passthrough: Session Initiated by SNA Host LU SNA Peripheral Node LU SNAX/XF SNA Host Application VTAM (Gateway LU object/ LU object for primary line) BIND request VSTA06.
Session Establishment SNAX/APN APPC SNAX/APN APPC For SNAX/APN APPC, whichever LU sends the BIND request is the primary LU. Unlike SNAX/XF, there is no correlation with whether the line is primary or secondary. LU Acquire The sequence of events is shown in Figure A-8. A SNAX/APC ALLOCATE verb has the same result when no session is available. Figure A-8.
Session Establishment SNAX/APN XLF SNAX/APN XLF ILOGMGR-TLOGMGR Session The Logon Manager for IBM Systems (ILOGMGR) must be running in the SNA host system for LU accept and (when the SNAX/APN LU is the secondary LU) for LU acquire. The ILOGMGR communicates with the TLOGMGR component of SNAX/APN line handler processes. When activated, the ILOGMGR sends each TLOGMGR in its control file a BIND request.
Session Establishment SNAX/APN XLF LU Acquire For CRT and ITI applications, the SNAX/APN LU must be the primary LU. For SNALU applications (including SNAX/HLS), the SNAX/APN LU can be the primary LU or a secondary LU. The sequence of events for the three cases is shown in Figure A-10. Figure A-10.
Session Establishment SNAX/APN XLF LU Accept Without SNAX Creator-2 The sequence of events varies between SNALU applications (including SNAX/HLS) and applications using CRT or ITI, as shown in Figure A-11. The SNAX/APN LU is always the primary LU. Figure A-11.
Session Establishment SNAX/APN XLF LU Accept With SNAX Creator-2 SNAX Creator-2 processes operates only with CRT or ITI applications. The sequence of events is shown in Figure A-12. The SNAX/APN LU is always the primary LU. Figure A-12.
B SNAX/XF and SNAX/APN BINDs SNALU applications, SNAX/HLS, and SNAX/APC provide BIND images that SNAX/XF or SNAX/APN forwards. For CRT, ITI, PRT, and NAM protocols, SNAX/XF or SNAX/APN constructs the BIND image. You can configure a BIND table for custom BINDs or use the default BINDs. Default BIND Table B-1 contains a summary of BIND byte numbers and default values. For more information about the parameters, see BIND Parameters on page B-5. Table B-1.
SNAX/XF and SNAX/APN BINDs Bytes 14-25 Table B-2. Presentation Services Profile — Bytes 14 Through 25 Byte Value 14 If non-6530, set to IBM SLU type from SCF ADD LU statement. %H70 (6530 — CRT protocol) %H71 (6530 — ITI protocol) 1519 %H0000000000 2024 %H0000000000 (6530 — ITI or CRT protocol) %H1850185002 (6530 — PRT protocol) %H1850185002 (3178 — all models) %H185018507F (3262, 3268, 3284, 3286, 3287, 3288, 3289 — all models.
SNAX/XF and SNAX/APN BINDs Custom BINDs PSERVIC Values for 3275 and 3276 Devices Byte Device/Model(s) 3275/11 3275/12 3276/2/12 3276/3/13 3276/4/14 20 %H0C %H18 %H18 %H18 %H18 21 %H28 %H50 %H50 %H50 %H50 22 %H0C %H18 %H18 %H20 %H2B 23 %H50 %H50 %H50 %H50 %H50 24 %H7F %H02 %H7F %H02 %H7F PSERVIC Values for 3277 and 3278 Devices Byte Device/Model 3277/1 3277/2 3278/1 3278/2 3278/3 3278/4 3278/5 20 %H0C %H18 %H0C %H18 %H18 %H18 %H18 21 %H50 %H50 %H28 %H
SNAX/XF and SNAX/APN BINDs Custom BINDs 2. Use SNAXUTL to add a BIND table and source file name to the SET table; for example: BEGIN SELECTFILE $SYSTEM.SYS01.SNXSET, TYPE SET ADD SETLOG BINDTAB1, FILENAME $SYSTEM.SYS01.LOGTAB1 END 3. Ensure that a SET table is defined for the SNAX subsystem; for example by the SCF command: ALTER SUBSYS $SSCP, SETTAB SNXSET 4.
SNAX/XF and SNAX/APN BINDs BIND Parameters BIND Parameters This subsection describes the BIND parameters mentioned in this appendix. TYPE type-value specifies the type of BIND command represented by this BIND image. Any hexadecimal values between %H00 and %H0F can be specified for type-value; however, only 0 and 1 are currently defined, where: %H00 = a negotiable BIND. %H01 = a non-negotiable BIND. (This is the default.
SNAX/XF and SNAX/APN BINDs BIND Parameters SSNDPAC ssndpac-value specifies the secondary receive pacing count (byte 8 of the BIND image). Any hexadecimal number in the range of %H00 to %H3F can be specified for ssndpac-value. The default value is %H00. SRCVPAC srcvpac-value specifies the secondary send pacing count (byte 9 of the BIND image). Any hexadecimal number in the range of %H00 to %H3F can be specified for srcvpac-value. The default value is %H00.
SNAX/XF and SNAX/APN BINDs BIND Parameters PSERVIC pservic-value specifies the logical unit presentation services profile and usage field (bytes 14 through 25 of the BIND image). The default values for pservic-value are found under Default BIND on page B-1. Note that if this command object is not specified, SNAX/XF generates values for PSERVIC and places them in the BIND image at run time.
SNAX/XF and SNAX/APN BINDs BIND Parameters If neither PLUNAME or USERDATA is specified, then the user-data length byte is not included in the BIND image. In this case, the last byte in the BIND image will be byte 27 (the length of plu-name, which is %H00). The value for user-data is specified as a hexadecimal string enclosed in parenthesis, with a maximum length of 221 bytes.
C Error Messages This appendix describes SCF error numbers and messages presented by the SNAX subsystem. SNAX/XF shares the same DSM subsystem ID and the same set of error messages with SNAX/APN; however, not all messages in the set apply to both products, and some messages have slightly different implications for the two products. SCF error messages from both subsystems are identified by the name SNAX. These errors all have positive error numbers.
Error Messages SNAX Error 00003 The object type in the SUB modifier specified a type of object that was not configured. For example, you issued STATUS LINE $SNA1, SUB LU, but no LUs subordinate to $SNA1 were configured. The select state in the SEL modifier specified a select state that no object was currently in. For example, you issued STATUS LINE $SNA1, SUB LU, SEL STARTING, but none of the LUs subordinate to $SNA1 were in the STARTING state. Effect. The command fails. Recovery. None.
Error Messages SNAX Error 00006 SNAX Error 00006 SNAX E-00006 Device Aborted: object-name Cause. A command was terminated prematurely because of a subsequent ABORT command issued for the same object. Effect. The command fails. Recovery. Retry the command. SNAX Error 00007 SNAX E-00007 DISCONTACT failed: object-name Cause. An SNA DISCONTACT command failed during processing of either a STOP command for a line or PU on a primary or secondary line, or an ABORT command for a line or PU on a secondary line.
Error Messages SNAX Error 00011 SNAX Error 00011 SNAX E-00011 Maximum number of LUs reached: object-name Cause. The maximum number of LUs has been used for a PU or LINE object. Effect. The command fails. Recovery. Delete unused LUs and retry the command, or reconfigure the LINE or PU object with a larger value for the MAXLUS attribute. SNAX Error 00012 SNAX E-00012 LU not stopped: object-name Cause.
Error Messages SNAX Error 00015 SNAX Error 00015 SNAX E-00015 PU not started: object-name Cause. A START LU command failed because the PU to which the LU was attached was not in the STARTED state. Effect. The LU is not started. Recovery. Start the PU and retry the command. SNAX Error 00016 SNAX E-00016 PU not stopped: object-name Cause. The command could not be executed because a PU was not in the STOPPED state.
Error Messages SNAX Error 00019 SNAX Error 00019 SNAX E-00019 Trace not stopped: object-name Cause. A DELETE LINE command failed because a trace was in progress on either the primary or the backup line-handler process. Effect. The line is not deleted. Recovery. Stop the trace before deleting the line. SNAX Error 00020 SNAX E-00020 IO Retry Error: object-name Cause. During the execution of a command, an I/O error occurred in the communication between the service manager and the line handler.
Error Messages SNAX Error 00023 SNAX Error 00023 SNAX E-00023 MODLINKSTA failed: object-name Cause. During processing of an SCF command, an SNA MODLINKSTA command failed. Effect. The SCF command fails. Recovery. Retry the command. SNAX Error 00025 SNAX E-00025 Line object-name inoperative. Cause. The referenced line is inoperative. This is usually due to a hardware error condition or a failure to receive SDLC frames from a remote SDLC station. Effect. The command fails. Recovery.
Error Messages SNAX Error 00028 SNAX Error 00028 SNAX E-00028 \system-name.line-name not added to Service Manager \system-name.$service-manager-name Cause. The referenced line has been configured with PROFILE, but it has not been added with SCF. Effect. The command fails. Recovery. Add the line and retry the command. When using multiple service managers, issue the INFO LINE command to determine the name of the service manager to which the line was added. SNAX Error 00029 SNAX E-00029 \system-name.
Error Messages SNAX Error 00032 SNAX Error 00032 SNAX E-00032 \system-name.$service-manager-name is started. Cause. An ALTER SUBSYS command failed because the specified service manager was in the STARTED state. You can alter the SSCPID and XPAGES attributes only when the service manager is in the STOPPED state. Effect. The ALTER SUBSYS command fails. Recovery. None. SNAX Error 00033 SNAX E-00033 LUNS Error: \system-name.$SSCP Cause.
Error Messages SNAX Error 00039 SNAX Error 00039 SNAX E-00039 Application is active: object-name Cause. A PRIMARY command was issued to change the primary processor for the service manager while an application was active. When an application is active, the primary and backup CPUs for the service manager cannot be switched. Effect. The PRIMARY command fails. Recovery. Stop the application and reissue the command. SNAX Error 00040 SNAX E-00040 Invalid Cpu Number for object-name Cause.
Error Messages SNAX Error 00043 SNAX Error 00043 SNAX E-00043 Unable to establish communication with Line Handler. Cause. An error occurred on the initial message from the service manager to a line handler. Effect. No commands are executed. Recovery. Contact your support provider. SNAX Error 00044 SNAX E-00044 DSC version mismatch between Service Manager and Line Handler. Cause. The service manager and the line handler are using incompatible DSC or SCF DEVICE versions. Effect. No commands are executed.
Error Messages SNAX Error 00045 SNAX Error 00045 SNAX E-00045 A mutually exclusive operation is taking place. Cause. Another operation is currently taking place on the object of this command or on one of its superior objects, and that operation is mutually exclusive with this command. Effect. The command fails. Recovery. Retry the command. SNAX Error 00046 SNAX E-00046 Too few XPAGES: Raise XPAGES value, or lower MAXLUS/MAXPUS values. Cause.
Error Messages SNAX Error 00048 SNAX Error 00048 SNAX E-00048 Too few IOPAGES: Raise IOPAGES value, or lower RECSIZE value. Cause. A conflict exists between the values specified for the IOPAGES attribute and the RECSIZE attribute for a line. The values of IOPAGES and RECSIZE are directly related. If the RECSIZE value is small, then the number of IOPAGES needed is small. If the RECSIZE value is large, then the number of IOPAGES needed is large. Effect. The command fails. Recovery.
Error Messages SNAX Error 00054 SNAX Error 00054 SNAX E-00054 Duplicate CALLADDR Cause. The value specified for the CALLADDR attribute is being used by another PU. Effect. The command fails. Recovery. Use a different value for the CALLADDR attribute. SNAX Error 00055 SNAX E-00055 Maximum number of APPLs reached. Cause. An attempt was made to add more than 100 APPL objects per system. Effect. The ADD command fails. Recovery. Delete APPL objects until there are fewer than 100.
Error Messages SNAX Error 00059 Recovery. Specify a unique attribute value for each object. Note that some attributes of switched lines affect the configuration of the PU attached to the line. To ensure that the PU attached to a line is properly configured, delete the PU before altering the line attributes. When the line configuration is stable, add the PU with properly verified PU attributes. SNAX Error 00059 SNAX 3-00059 The command is not applicable to this type of SNAX/APN LU. Cause.
Error Messages SNAX Error 00065 Effect. The session is not stopped. Recovery. Either reissue the STOP SESSION command with the FORCED modifier, or issue an ABORT SESSION command. SNAX Error 00065 SNAX E-00065 Rejected, another LINE on a MULTI process is STARTED Cause.
Error Messages SNAX Error 00069 SNAX Error 00069 SNAX E-00069 SAPINFO MAXLS value cannot be zero when adding a line. Cause. In an ADD LINE command for a Token-Ring or Ethernet line, the MAXLS value specified in the SAPINFO attribute for at least one service access point (SAP) had an invalid value of zero. Effect. The line is not added. Recovery. Change MAXLS to a nonzero value or eliminate it from the SAPINFO attribute.
Error Messages SNAX Error 00074 Recovery. An SNA SAP value must be in the range %H04 to %HFC and must be a multiple of %h04. Choose a valid SAP value in the correct range and retry the command. SNAX Error 00074 SNAX E-00074 Number of PUs using specified SAP cannot exceed line's SAPINFO value. Cause.
Error Messages SNAX Error 00079 Effect. The ALTER PU command fails. Recovery. Delete the subordinate LUs before altering SNANETID. SNAX Error 00079 SNAX E-00079 MAXRCVSIZE is invalid when MAXLOCALLUS is 0 or not specified. Cause. The user specified the MAXRCVSIZE attribute without first specifying a nonzero value for MAXLOCALLUS. MAXLOCALLUS is a required attribute that enables SNAX/APN operation. Effect. The command fails. Recovery. Specify MAXRCVSIZE only when MAXLOCALLUS is nonzero.
Error Messages SNAX Error 00082 SNAX Error 00082 SNAX E-00082 Cannot change the SNANETID of a SNAX/APN local LU. Cause. The user specified the SNANETID attribute in an ADD or ALTER command for a SNAX/APN local LU. Effect. The command fails. Recovery. The SNANETID attribute of local LUs is determined by the SNANETID attribute specified for the SUBSYS object. Do not specify the SNANETID attribute in an ADD or ALTER command for a local LU.
Error Messages SNAX Error 00085 Recovery. Specify PASSTHRU ON when trying to specify ASSOCIATE lu-name. Remove the lu-name value of ASSOCIATE by specifying ASSOCIATE “” when trying to set PASSTHRU to OFF. SNAX Error 00085 SNAX E-00085 Invalid FQPCID specified for SESSIONSELECT of TRACE command. Cause. In the SESSIONSELECT option in a TRACE command, one or more of the specified fully qualified procedure correlation identifiers (FQPCIDs) did not represent existing sessions. Effect.
Error Messages SNAX Error 00102 SNAX Error 00102 SNAX E-00102 SNAX/APN does not support floating LUs. Cause. The user attempted to add a switched floating LU to a SNAX/APN PU. Effect. The ADD LU command fails. Recovery. None. Switched floating LUs are not supported by SNAX/APN. SNAX Error 00103 SNAX E-00103 LOCALSNANAME is a required attribute. Cause.
Error Messages SNAX Error 00110 Recovery. First, use the SETMANAGER command to determine the service manager to which the line was added, then reissue the command that caused error. If you want to add the line to a different service manager, first delete the line, then add it to a different service manager. SNAX Error 00110 SNAX E-00110 Object \system-name.$service-manager-name. [ object-name ] conflicts with Service Manager \system-name.$service-manager-name Cause.
Error Messages SNAX Error 00113 SNAX Error 00113 SNAX E-00113 The object name specified is a reserved name. Cause. The object name specified must not be #ZNT21, #ZAPC21, or #ZRCPnn. Effect. The command fails. Recovery. Specify another name for the object. SNAX Error 00114 SNAX E-00114 The CPNAME on the remote PU must be unique. Cause. The CPNAME of the remote PU is the same as our CPNAME. Effect. The command fails. Recovery. Specify a different CPNAME for the remote PU.
Error Messages SNAX Error 00118 Recovery. Make sure APPN is set to YES when MAXLOCALLUS is non-zero. SNAX Error 00118 SNAX E-00118 REGISTER attribute is not compatible with NODETYPE of SUBSYS. Cause. The user specified the REGISTER attribute when NODETYPE is LEN or NONE. Effect. The command fails. Recovery. Change the NODETYPE of SUBSYS to EN. SNAX Error 00119 SNAX E-00119 REGISTER attribute value for SNAX/APN LUs with same SNANAME must match one another. Cause.
Error Messages SNAX Error 00122 Effect. The command fails. Recovery. Make sure the CPNAME of the PU matches the CPNAME of the adjacent node that has the same NNSERVER attribute. SNAX Error 00122 SNAX E-00122 SNAX/APN LEN or End Node function NOT installed Cause. An attempt was made to configure the Service Manager Subsys ($SSCP) as: NODETYPE EN without having installed the T0064 product, or NODETYPE LEN without having installed either the T9564 or T0064 products. Effect.
Error Messages SNAX Error 00501 Recovery. Reissue the command without the duplicate attribute. SNAX Error 00501 SNAX E-00501 Duplicate modifier modifier-name Cause. One of the modifiers entered in a command was a duplicate. The name of the modifier that was duplicated is modifier-name. Effect. The command fails. Recovery. Reissue the command without the duplicate modifier. SNAX Error 00502 SNAX E-00502 Internal error: Case out of range Cause. An internal error occurred because of an unexpected value.
Error Messages SNAX Error 00505 SNAX Error 00505 SNAX E-00505 Required attribute missing: attribute-name Cause. The required attribute named in attribute-name was missing from a command. Effect. The command fails. Recovery. Reissue the command with the attribute included. SNAX Error 00506 SNAX E-00506 Invalid value: attribute-name Cause. An invalid value was specified for the attribute named in attribute-name. Effect. The command fails. Recovery.
Glossary This glossary defines terms used and referred to in this manual. For abbreviations of terms specific to SNAX and HP NonStop products, the definition consists of a crossreference to the spelled-out term. In addition, several definitions have been borrowed from the IBM Dictionary of Computing and the IBM Network Program Products: General Information manual. ABORTING state. As defined by SCF or SPI, the state of an object when an ABORT command has been issued against that object but has not completed.
Glossary API API. See application program interface (API). APPC. See advanced program-to-program communication (APPC). APPL object type. An SCF or SPI object type that allows an installed application process of a given type to open the service-manager process using a specified subdevice name. application (A program or set of programs or routines designed to perform a specific task, usually involving specified operations on a database.
Glossary basic information unit (BIU) basic information unit (BIU). The unit of data and control information that consists of a request/response header (RH) followed by a request/response unit (RU). basic transmission unit (BTU). Information that the data link control sends over a link. A basic information unit can consist of one path information unit (PIU), several PIUs, or a part of a PIU. BIND command.
Glossary cluster controller cluster controller. A device that controls access (I/O operations) to a group of terminals or printers connected to it. A cluster controller may be controlled by a program stored and executed in the unit, or it may be entirely controlled by hardware. CNM interface. A SNAX communications network management interface. command. A demand for action by or information from a subsystem, or the operation demanded by an operator or application.
Glossary configured object configured object. A Subsystem Control Facility (SCF) object that exists at the time an SCF subsystem completes its initialization process, or an SCF object that is brought into existence by a command issued through the subsystem management interface. ConMgr. See concentrator manager process (ConMgr). Connection Manager. See SNAX Connection Manager (SNAX/CM). COUP. See Configuration Utility Program (COUP). Creator. NonStop software that starts applications on the NonStop system.
Glossary device control device control. A SNAX/XF feature that provides programmatic interfaces by which application processes executing in NonStop systems can control SNA devices residing throughout an Expand network, without an SNA host system present. device-initiated passthrough.
Glossary Dynamic System Configuration (DSC) Dynamic System Configuration (DSC). A utility used in D-series and earlier RVUs to make online changes to the configuration of devices and controllers. Its interactive utility is called the Configuration Utility Program (COUP). In G-series and H-series RVUs, DSC functions are performed by Subsystem Control Facility (SCF). E4SA. See Ethernet 4 ServerNet Adapter (E4SA). ELF. See Enhanced Logon Facility (ELF). EMS. See Event Management Service (EMS). end node.
Glossary exception response mode exception response mode. A mode in which a response from the device is sent only if an error is detected. See also definite response mode. Expand network. The NonStop Kernel operating system network that extends the concept of fault-tolerant operation to networks of geographically distributed NonStop systems. If the network is properly designed, communication paths are constantly available even if there is a single line failure or component failure.
Glossary Gigabit Ethernet ServerNet adapter (GESA) Gigabit Ethernet ServerNet adapter (GESA). A single-port ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ systems and Ethernet LANs. A GESA can be directly installed in slots 51 through 54 of an I/O enclosure and slots 53 and 54 of a processor enclosure. Two versions of the GESA are available: 3865 GESA-C (T523572): a single-port copper version compliant with the 1000 Base-T standard (802.
Glossary HP Tandem Logon Manager for IBM Systems (ILOGMGR) HP Tandem Logon Manager for IBM Systems (ILOGMGR). NonStop software that runs in IBM systems to support device logon using the SNAX/APN extended logon facility. See also TLOGMGR. ILOGMGR. See HP Tandem Logon Manager for IBM Systems (ILOGMGR). ILOGMGR control file.
Glossary LIF LIF. See logical interface (LIF). line. The specific hardware path over which data is transmitted or received. A line can also have a process name associated with it that identifies an input/output process (IOP) or logical device associated with that specific hardware path. line-at-a-time mode. A terminal operating mode in which data is read from the terminal and displayed on the terminal screen one line at a time. Contrast with block mode. line-handler process.
Glossary logical unit 6.2 (LU 6.2) printers, or application programs. Each LU supports a session between two end users (LU-LU session). SNA categorizes LUs according to the type of end-user services that the LU provides. logical unit 6.2 (LU 6.2). A type of logical unit that supports general communication between programs in a distributed processing environment. LU 6.
Glossary LUNS Presentation services protocols such as those associated with FMH use. LUNS. See LU network services (LUNS). mainframe. A large-system processor. SNAX/XF, SNAX/APN, and SNAX/CDF all allow NonStop systems to communicate with IBM mainframes running MVS and VTAM. See also host system. management application. In general, an application that monitors or controls another entity. In the context of DSM, an application process that opens a management or subsystem process to control a subsystem.
Glossary node node. (1) A station or physical device that allows for the transmission of data within a network. (2) In SNA, an endpoint of a link or junction common to two or more links in a network. There are peripheral and subarea nodes. Nodes include host processors, communication controllers, cluster controllers, or terminals. Nodes can vary in routing and other functional capabilities. Each SNA node must contain at least one NAU. See also node type (NT). node type (NT).
Glossary null object type null object type. In the context of SCF, a term indicating that a command can be issued without specifying an object type. For SNAX/XF, the null object type applies only to the VERSION command. OBEY file. A command file containing SCF commands. See command file. object. A NonStop resource as identified to DSM that can be configured, controlled, and inquired about by the operator. The objects identified for SNAX products include subsystems, lines, PUs, LUs, and applications.
Glossary Pathway application Pathway application. A set of programs that perform online transaction processing tasks in the Guardian environment, using interfaces defined by HP. PDN. Public data network. peer. An entity that communicates as an equal with another entity at the same protocol level. peripheral node. See SNA peripheral node. Peripheral Utility Program (PUP). A utility used in D-series and earlier RVUs to manage disks and other peripheral devices.
Glossary primary path primary path. A path enabled as the preferred path. When a primary path is disabled, an alternate path becomes the primary path. Contrast with alternate path. process. A program that has been submitted to the operating system for execution, or a program that is currently running in the computer. process pair. Two processes: a primary process that is active, and a secondary, backup process in another CPU that is ready to take over if the primary process fails. PROFILE object.
Glossary remote PU object remote PU object. An SCF object that represents the PU in an adjacent node. RH. A request or a response unit header. RU. Request/response unit. S-series. A version of hardware. The NonStop S-series servers run with G-series software. SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP). SDLC. Synchronous data link control. secondary link station.
Glossary session manager is provided as part of SNAX, and a single service manager can manage both products. session. A temporary logical connection between two network-addressable units (NAUs) 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. SESSION object . An SCF object that defines a session. session passthrough.
Glossary SNAX SNAX. A trademark pertaining to a family of NonStop products. In this manual, it is used to refer to SNAX/XF and SNAX/APN together. SNAX Advanced Peer Networking (SNAX/APN). A NonStop software product that enables a NonStop system to function as a type 2.1 LEN node. SNAX Advanced Program Communication (SNAX/APC). A NonStop API product that handles SNA flows for LU 6.2 communication (APPC) with other programs. SNAX/APC. See SNAX Advanced Program Communication (SNAX/APC). SNAX/APN.
Glossary SPI devices in a NonStop network and SNA hosts. SNAX/XF provides device control, session passthrough, and application-to-application communication. SPI. See Subsystem Programmatic Interface (SPI). SSCP. See system services control point (SSCP). SSCP-LU session. In SNA, a session between an SSCP and an LU that enables the LU to request the SCCP to help initiate LU-LU sessions. STARTED state. As defined by SCF or SPI, the state of an object that has been defined and initialized. STARTING state.
Glossary SUBSYS object SUBSYS object. An SCF object that defines the service-manager process. subsystem. In the context of the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS), a process or collection of processes that give users access to a set of related resources or services. A subsystem typically controls a cohesive set of objects. Subsystem Control Facility (SCF).
Glossary switched line it becomes temporarily subordinate to a LINE object because it is needed for a switched connection. switched line. A telecommunications line in which the connection is established by dialing. See also nonswitched line. switched virtual circuit (SVC). An X.25 virtual circuit that is established dynamically when needed. Contrast with permanent virtual circuit (PVC). system area network (SAN).
Glossary TLOGMGR LU object TLOGMGR LU object. A SNAX/APN local LU object that represents the TLOGMGR LU. token. In the context of networking protocols, a sequence of three bytes passed from node to node along the network. The middle field contains a token bit that indicates to a receiving node that the token is available to accept information. If that node has data to transmit, it appends that data to the token and changes the value of the bit. The token now becomes a frame. trace.
Glossary WAN subsystem and managing the WAN subsystem and the ServerNet wide area network (SWAN) concentrator. The WAN manager process is named $ZZWAN. WAN subsystem. See wide area network (WAN) subsystem. WANBoot process. The WANBoot process is provided as part of the WAN subsystem. The WANBoot process runs as a NonStop process pair in each CPU that supports a NonStop TCP/IP process that is supporting WAN communications. The WANBoot process implements the BOOTP protocol.
Glossary $SSCP SNAX/XF and SNAX/APN Configuration and Management Manual—425836-005 Glossary-26
Index Numbers 58,5 lines attributes of 13-12, 13-32, 13-54 CLIP program file for 14-41 controller tracing for 13-139, 15-4 downloading controllers on 14-9 interface for 14-25, 14-26 PTrace SELECT keywords for 15-14 PTrace SELMASK bits for 15-14 reference information 13-77 selecting trace records for viewing 15-4 trace records specific to 15-61, 15-61/15-67 TRACE select options for 13-138 tracing within 13-139 A ABCONRSPPD line state 13-98, 13-99 ABORT command 13-3 ABORTING object state 12-12 Acknowledgment
Index A Address space manager actions, tracing 13-137, 13-139 Adjacent node control point name of 14-16 SNA network identifier of 14-60 Advanced peer-to-peer networking 1-9 Advanced program-to-program communication 1-10, 6-1 AGGREGATE command 13-22 ALKRSPPD line state 13-98, 13-100 ALKSTARSPPD, PU state 13-113, 13-115 ALL keyword 11-8 PTrace SELECT command 15-3, 15-4, 15-12, 15-16 TRACE command LUSELECT option 13-130 OFF option 13-131 PUSELECT option 13-132 SELECT option 13-137, 13-140, 13-141 with SESSIO
Index B AS/400 systems (continued) CPNAME attribute of SUBSYS object 14-18 PUIDBLK attribute of remote PU 14-45 PUIDNUM attribute of remote PU 14-47 SNANETID attribute of remote PU 14-60 SNANETID attribute of SUBSYS object 14-61 description of 6-8 Attributes definition of 11-9, 14-1 descriptions of 14-1/14-80 for APPL objects 13-27 for LU objects 13-14 for PU objects 13-20 obtaining values of, for an object 13-44 of APPL objects 13-6, 13-45 of LINE objects 13-45 of LU objects 13-18, 13-34, 13-35, 13-45 of
Index C BM keyword TRACE command 13-137, 13-139 BOTH option, CALLVALIDATE attribute 14-13 Broadcast poll address 14-62 BTU, maximum number of bytes in 14-35 Buffer errors, statistics of 13-87 Buffer manager tracing 13-137, 13-139 Buffers, I/O, memory allocation for 14-26 C Call validation 14-12, 14-13 CALLADDR attribute 14-12 option, CALLVALIDATE attribute 14-13 CALLVALIDATE attribute 14-13 Cancellation of requests to X25AM, trace record for 15-39 CCINTERF keyword, TRACE command 13-140 CCPROCENTRY keywor
Index C CNM applications (continued) password for 14-40 PU objects associated with 14-7 CNM CONFIG 1-16 CNMAPPL object 1-17 CNMSERV object 1-17 COLD option ACTLU attribute 14-2 ACTPU attribute 14-2 Cold start 14-2 Collector, trace, enabling or disabling 13-131, 13-143 example 13-145 Commands 13-1/13-149 general description of 11-7 nonsensitive 11-7 See also individual command descriptions sensitive 11-7 STOPOPENS 13-127 syntax detailed 13-2/13-149 general 11-7 Command/control responses from SPI requests,
Index D COUNT option, TRACE command 13-130 examples 13-146 setting 13-142 COUNTRY modifier 2-7 CPNAME attribute for remote PU objects 14-16 for SUBSYS object 14-17 CPUs, switching 13-77 CREATOR attribute 14-18 Creator processes 1-16 Creator-2 process See SNAX Creator-2 process CRT 1-8 protocol 14-42 protocol module 15-5 CRT30 protocol module 15-5 CSSLVL1 keyword, TRACE command 13-140 CSSLVL2 keyword, TRACE command 13-140 CTERMRSPPD, LU state 13-106 CTLRALL keyword, TRACE command 13-140 CURRENT keyword, PT
Index D Device type and model of terminal 14-20 and subtype for local LUs 14-73 for LUs 14-72 for PUs 14-74 for remote LUs 14-74 in trace records 15-3 modifier for SNAX lines 2-10 DEVTYPE attribute 14-20 DFC argument of SAPINFO attribute 14-55 DFS argument of SAPINFO attribute 14-55 DFT argument of SAPINFO attribute 14-55 DI keyword, TRACE command 13-139 DIAG6204 program, diagnostics using 12-12 DIAGACTIVE line state 13-98, 13-100 DIAGNOSING object state 12-12 Diagnosing problems See TRACE command, PTrace
Index E DXX^LDONE^TRACE^ID trace record 15-58 DXX^OPEN^REQUEST trace record 15-57 DXX^PASSTHRU^MSG trace record 15-55 DXX^REPLY^REQ^TRACE^ID trace record 15-74, 15-76 DXX^SEND^REQ^TRACE^ID trace record 15-77 DXX^SVC^MGR^TO^TS trace record 15-54 DXX^TS^TO^CSM trace record 15-59, 15-61 DXX^TS^TO^SVC^MGR trace record 15-52 DXX^TS^TO^TS trace record 15-53 DYNAMIC attribute 14-23 role in creating remote LUs 12-5 E EBCDIC character translation from ASCII 14-14 command, PTrace 15-7 data, in PTrace displays 15-7
Index G File system reply, trace record for 15-50 request, trace record for 15-49 use of by SNAX/XF 15-6 FILESYS keyword, TRACE command 13-136, 13-139 FILTER command, PTrace 15-7 Finite state machine See State machine First trace entry, in PTrace displays 15-18 Fixed PU and LU objects 3-5 FLAGFILL attribute 14-25 Floating PUs and LUs, not supported 13-9 Flow control 14-27 Forbidding opens of LUs 13-127 FQPCID how to find, for SESSION objects 13-4, 13-76, 13-108/13-112, 13-125 identifier for SESSION object
Index J INACTIVE (continued) PU state 13-114, 13-115 PU test state 13-113, 13-116 Incoming request from X25AM, trace record for 15-40 to line handler, trace record for 15-52 to service manager trace record for 15-75 tracing 13-141 INFO command 13-44 attributes displayed in full descriptions 14-1/14-80 lists by object type 13-45 display for APPL objects 13-48 display for LINE objects nondetailed 13-49 SDLC lines 13-54 X.
Index L L5^STATE^TRACE^ID trace record 15-35 L6^DISPQ^TRACE^ID trace record 15-34 L6^SCHED^TRACE^ID trace record 15-30 L6^STATE^TRACE^ID trace record 15-35 Last trace entry, in PTrace displays 15-18 LCAN message-system function 15-6 trace records for 15-39 LDONE message-system function 15-6 trace records for 15-38, 15-58, 15-78 tracing, in service manager 13-141 example 13-146 LEN node 6-1, 6-4 Level 15-5 Level_1 in SNAX architecture 15-5 procedure entry, tracing 13-140 trace records for state machine 15-
Index L Level_6 (continued) scheduler dispatch 15-30 state machine 15-35 Limiting number of trace records 13-130 examples 13-146 Line handler architectural overview of 15-5 modifiers 2-7 obtaining version of 13-10, 13-30, 13-50, 13-52, 13-54, 13-56, 13-58, 13-60, 13-71, 13-79 process object type See PROCESS object profile 2-2 relationship to other components 11-4 switching primary CPU of 13-77 trace records generated by 15-21/15-67 LINE objects aborting 13-3 adding 13-8 allowing opens of LUs subordinate t
Index L LNMAXOUT attribute 14-29 LNMAXOUTINCR attribute 14-29 LNMAXRETRY attribute 14-30 LNRMTADDR attribute 14-30 LNSSAP attribute 14-30 LNT1 attribute 14-31 LNT2 attribute 14-31 LNTI attribute 14-31 Local LU objects descrition of 12-5 TLOGMGR LU 12-5 See also TLOGMGR LU object used for APPC attributes of 13-18, 13-35 configuration for 14-58 general information 12-5 STATUS LU display for 13-108 STATUS SESSION display for 13-118 #ZAPC21 14-38 Local pool storage calls by service manager trace records for 1
Index M LU objects (continued) obtaining statistics for 13-83, 13-88 obtaining status of 13-94, 13-103 obtaining status of subordinate objects 13-108, 13-111 primary or secondary role, displaying 13-118, 13-120, 13-121 remote 12-5 See also Remote LU objects representation 1-4 session state for 13-103, 13-105 specifying multiple LUs 13-15, 14-39 starting 13-81 stopping 13-124 stopping opens of 13-127 LUDISABLED attribute 14-33 LUNS applications 1-16 applications, configuring for 14-5 autologon 14-9 ESS tab
Index N Message system traffic, tracing 13-136, 13-139 use of by SNAX 15-6 Mismatch IPM or release version 13-10, 13-30, 13-50, 13-52, 13-54, 13-56, 13-58, 13-60, 13-71, 13-79 service manager 13-10, 13-30, 13-50, 13-52, 13-54, 13-56, 13-58, 13-60, 13-71, 13-79 MLKRSPPD line state 13-98, 13-100 MLKSTARSPPD, PU state 13-114, 13-116 Model number, of IBM terminal 14-20 Modem failure 13-51, 13-53, 13-56, 13-58, 14-37 timer 14-37 Modifiers, WAN subsystem COUNTRY 2-7 EXTPOOLPAGES 2-5 L1RETRY 2-8 line handler 2-7
Index O Naming conventions (continued) for LU objects 12-6, 14-39 for PROCESS objects 12-7 for PU objects 12-8 for SESSION objects 12-9 for SUBSYS object 12-10 NCP configuration for CPNAME attribute of remote PU 14-17 CPNAME attribute of SUBSYS object 14-18 PUIDBLK attribute of remote PU 14-45 PUIDNUM attribute of remote PU 14-47 SNANAME attribute of local LU 14-58 SNANAME attribute of remote LU 14-58 SNANETID attribute of remote PU 14-61 SNANETID attribute of SUBSYS object 14-61 definition 4-3 NCS1^TRACE
Index O Object states (continued) for the SUBSYS object 13-122, 13-123 for APPL objects 12-11 INACTIVE 12-11 OPENED 12-11 See also individual object states STARTED 12-13 STARTING 12-13 STOPPED 12-13 STOPPING 12-13 Object types APPL 12-3 in SCF commands 11-8 LINE 12-4 LU 12-5 null 12-2 PROCESS 12-6 PU 12-7 SESSION 12-9 SUBSYS 12-10 Objects aborting 13-3 adding 13-6/13-21 adding multiple LU objects 13-15, 14-39 allowing opens of 13-25 altering 13-27, 13-40 deleting 13-42 multiple service managers 13-78 obta
Index P OS/2 (continued) description of 6-10 OUT option, DIALTYPE attribute 14-21 Outbound message from service manager, trace record for 15-71, 15-72, 15-73, 15-75 Outgoing data to X25AM, trace record for 15-44 Outgoing LCAN, trace records for 15-39 Outgoing reply from service manager trace record for 15-74, 15-76 tracing 13-141 Outgoing request from service manager trace record for 15-77 tracing 13-141, 13-146 Output destinations, for SCF 11-10 Owner, subsystem 11-7 P PAGES option, TRACE command 13-132
Index P PIU I/O (continued) PIU Out 15-23 tracing 13-136, 13-138 examples 13-145 PIU keyword, TRACE command 13-136, 13-138 examples 13-145 PIU^TRACE^ID trace record PIU In 15-21 PIU Out 15-23 PLU accept SNAX/APN ELF 7-10 SNAX/APN XLF 7-6 PLU acquire SNAX/APN (Tandem appl is PLU) 7-2 Point-to-point line 1-7 Polling interval on lines 14-41 rules for 14-27 POLLINT attribute 14-41 Pool storage, statistics of 13-88 PORT parameter, in SNAX/CM commands 14-8 Presentation services 15-5 Primary CPU changing 13-77 f
Index P PTrace utility commands having no effect 15-7 commands supported 15-7 description of 13-129, 15-1/15-79 device types and subtypes shown by 15-3 FILTER command 15-7 general format of trace-record displays 15-19 individual trace-record displays for line handler 15-21/15-67 for service manager 15-68/15-79 overview 15-1/15-3 relationship to TRACE command 15-1/15-3 SELECT command 15-12 SELECT keyword and SEMASK mask bits 15-14 SELMASK command 15-12 starting 15-2 STATETABLES command 15-16 trace-file hea
Index Q Q QUEUE attribute 14-48 R Read count, maximum, for device logon or device acquire 14-36 Receiver Not Ready (RNR) commands and responses 13-86, 13-90 frames handling 14-53 sending 14-53 L2OPTION1 14-27 timer value 14-54 Reconfiguration 1-6 Record Type, in PTrace displays 15-19 RECSIZE attribute for LINE objects 14-49 for LU objects 14-50 for PU objects 14-50 RECSIZE option, TRACE command 13-132 example 13-146 setting 13-143 RECVLOCATE attribute 14-51 REGISTER 14-51 REJ modifier 2-9 Rejects (REJ),
Index S Request sent to X25AM, trace records for 15-36, 15-44 Resetting statistics counters 13-83 Resource limits 1-18 Response type, for requests 14-54, 14-55 Retransmit timeout for PU contact attempts 14-28 for response to READ or AUTOPOLL 14-69 RETRIES attribute 14-52 Retry limit for PU contact attempts 14-27 for READ or AUTOPOLL timeouts 14-52 RNRRECEIVE attribute 14-53 RNRSEND attribute 14-53 RNRTIMER attribute 14-54 RQB^TRACE^ID trace record 15-71, 15-72, 15-73, 15-75 RQDISCRSPPD, PU state 13-114, 1
Index S SCF attributes (continued) RECSIZE 9-24 SUBSYS XPAGES 14-38, 14-51 SCF subsystems differences between old and new 11-2 interface for S-Series Servers 11-4 Scheduler dispatch trace records for 15-28/15-30 tracing 13-137, 13-139 SCP relationship to SNAX components 11-4 role of, in relaying commands 11-9, 15-6 SCREENSIZE attribute 14-56 SDLC address, of PU 14-3 frame I/O idle line flags 14-25 tracing 13-139 tracing, examples 13-145 lines interface for 14-25, 14-26 trace records specific to 15-59 used
Index S Service manager (continued) trace records generated by 15-68/15-79 SERVICECOUNT attribute 14-56 Session establishment A-1 Session establishment table 1-5 See SET table Session identifier, displaying 13-107 Session initiation A-1 SESSION objects count of, for LU 13-107 description of 1-4 finding names of 13-4, 13-76, 13-108/13-112, 13-125 in SNAX 12-9 aborting 13-3 stopping 13-124 in TLAM subsystem 14-7 maximum count, for LU 13-107 naming 12-9 naming conventions 12-9 obtaining status of 13-118 Sess
Index S SNANETID attribute for PUs 14-60 for remote LUs 14-59 for SUBSYS object 14-61 SNAX 15-5 SNAX Connection Manager description of See SNAX/CM functions 3-8 processes 1-16 SNAX Creator 14-4, 14-18 password for 14-40 SNAX Creator-2 APPLFILE attribute 14-4 CREATOR attribute 14-18 password for SU object 14-40 starting applications 7-6 SNAX Creator-2 process APPL object 12-3 password for SU object 14-41 relationship of APPL object to 13-7 SNAX Extended Facility See SNAX/XF SNAX identifier, in SCF error me
Index S SNAX/XF (continued) message-system traffic, tracing 13-139 LINE objects shared with See Shared lines LU Network Services See LUNS passthrough description of 5-1 session initiation A-5 relationship to SNAX/APN 11-1 requests and responses, tracing SDLC lines 13-140 SNRMIFDM attribute 14-62 Sources of input for SCF 11-10 Specific poll address 14-62 specifies 13-136, 13-139 Specifying a SUBSYS object 13-78 SPEED attribute 14-62 Speed, of lines 14-62 SPI description of 11-6 in SNAX architecture 15-5 ke
Index S STOP command 13-124 option, TRACE command 13-130, 13-145 STOPOPENS command 13-127 STOPPED object state 12-13 obtaining counts of objects in 13-22 open state for LUs 13-107 switched LU state 13-107 switched PU state 13-116 STOPPING LU session state 13-104, 13-105 object state 12-13 Stopping a trace 13-130, 13-134, 13-145, 15-2 Stopping an object with the ABORT command 13-3 with the STOP command 13-124 Stopping opens of LUs 13-127 SU object, X25AM 14-7 SUB parameter 11-8 Subarea networking 1-9 Subde
Index T SWITCHED attribute 14-65 Switched floating PU and LU objects description of 3-6 description of PU objects 12-7 valid LU names 12-6 valid PU names 12-8 Switched floating PUs and LUs not supported 13-9 obtaining counts of 13-92, 13-93 Switched lines 14-37 calling or answering mechanism 14-21 controlled through SNAX/CM 3-8 description of 1-7 INFO command, example 13-51, 13-53, 13-56, 13-58 MDMLOSSFATAL attribute 14-37 names of 13-107, 13-116 operator messages 14-66 specifying 14-65 using subordinated
Index T TLOGMGR LU object (continued) effect when aborted 13-5 status information returned for 13-95 TLOGMGR-ILOGMGR session A-7 TMDS interface, diagnostics using 12-12 TO option, TRACE command 13-134 examples 13-145/13-146 Tokens 11-6 Token-Ring support early token release feature 9-8 LLC1 protocol 9-15 LLC2 protocol 9-15 MAC frame 9-17 medium access control (MAC) 9-8 PU address considerations 9-24 SCF attributes (optional) LNMAXIN 9-23 LNMAXOUT 9-23 LNMAXOUTINCR 9-23 LNMAXRETRY 9-23 LNT1 9-24 LNT2 9-24
Index V Tracing (continued) primary process 13-130 service manager 13-129 TRANSLATE command, PTrace 15-7 Translation of characters 14-14 Translation option, in PTrace displays 15-18 Transmission control 15-5 Transmission Priority Field See TPF TRMAXIN attribute 14-70 TRMAXOUT attribute 14-70 TRMAXOUTINCR attribute 14-70 TRMAXRETRY attribute 14-71 TRRMTADDR attribute 14-71 TRSSAP attribute 14-71 TRT1 attribute 14-71 TRT2 attribute 14-71 TRTI attribute 14-71 TS abbreviation, in traces 15-5 Two-way simultane
Index X WINDOW attribute 14-75 WRAP option, TRACE command 13-134 example 13-145 setting 13-145 Wrapping of trace records 13-134 Write retries counter, SNAX/XF versus Measure 13-84 statistics of 13-87 Write timeouts, statistics of 13-88 WRITELINK message-system function 15-6 trace records for 15-37, 15-50, 15-74, 15-76 tracing, in service manager 13-141 WRITE-COMPLETE interrupt, time to wait for 14-79 WRLINK keyword, TRACE command 13-141 X X21NRDY attribute 14-76, 14-77, 14-78 X25 displayed value, INTERFA
Index Special Characters SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006 Index-32
