Networking and Data Communications Library Tandem Logon Manager for IBM Systems (ILOGMGR) Manual Abstract This manual describes how to install, configure, and manage the Tandem Logon Manager for IBM Systems (ILOGMGR). The ILOGMGR works with the SNAX/APN extended logon facility (XLF), and enables 3270-type terminals controlled by SNA host systems to log onto applications on Tandem NonStop systems. Product Version ILOGMGR D21 (T6919D21) Supported Releases This manual supports release D42.
Document History Edition Part Number Product Version Earliest Supported Release Published First 098299 ILOGMGR D21 D72.00 based on D20.01 April 1994 Second 105787 ILOGMGR D21 D30.00 December 1994 Third 114891 ILOGMGR D21 D30.02 July 1995 Fourth 127335 ILOGMGR D21 D42.00 August 1996 New editions incorporate any updates since the previous edition.
New and Changed Information The following changes have been made in this edition of the Tandem Logon Manager for IBM Systems (ILOGMGR) Manual: • • With earlier versions of ILOGMGR, the SNAX/APN linehandler process did not send sense data when it rejected a logon from a device. The result was that a user could not determine the reason for the rejection. A new error code, T0025, has been added to ILOGMGR to provide this information to the user.
New and Changed Information iv 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
Contents New and Changed Information iii About This Manual vii Notation Conventions xi Abbreviations xv 1. Introduction to the ILOGMGR Device Logon 1-2 TLOGMGR and ILOGMGR Naming Correspondences 1-10 2. Installing the ILOGMGR Copying ILOGMGR File From DSV to Tape 2-1 Link-Editing ILOGMGR File to a Load Module Library Using an Optional JCL Procedure 2-1 2-1 3.
A. Error Messages and Sense Codes Contents A. Error Messages and Sense Codes Error and Informational Messages A-1 SNA Sense Codes and User’s Terminal Messages A-12 B. Logical Flows and Internal Formats Logical Flows B-1 Internal Formats B-3 PROGRAM_START_REQ Record B-3 PROGRAM_START_REPLY Record B-4 PROGRAM_START_ABORT Record B-4 Glossary Index Glossary-1 Index-1 Examples Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 3-1. Figure 3-2. Figure 3-3. Figure B-1.
About This Manual This manual describes the Tandem Logon Manager for IBM Systems (ILOGMGR), a Tandem software product running on IBM host systems. The ILOGMGR allows users of IBM 3270-type terminals in an SNA network to access applications running on a Tandem system. The ILOGMGR also allows a SNAX Application Logical Unit (SNALU) on a Tandem system to access applications located on an IBM host.
Related Information About This Manual Note that all terms shown in boldface type can be found in the glossary. Related Information The following manuals may help you understand the concepts of SNA, VTAM configuration, the Multiple Virtual Storage (MVS) operating system, and the job control language (JCL).
About This Manual Your Comments Invited Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Tandem CD Read disc. You can either FAX or mail the card to us. The FAX number and mailing address are provided on the card.
Your Comments Invited x About This Manual 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets.
General Syntax Notation Notation Conventions An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Notation Conventions Notation for Messages !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text.
Notation for Management Programming Interfaces Notation Conventions % Percent Sign. A percent sign precedes a number that is not in decimal notation. The %þnotation precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes a hexadecimal number. For example: %005400 P=%p-register E=%e-register Notation for Management Programming Interfaces UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown.
Abbreviations Tandem Logon Manager for IBM Systems (ILOGMGR) Manual—127335 xv
Abbreviations xvi 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
1 Introduction to the ILOGMGR The Tandem Logon Manager for IBM Systems (ILOGMGR) allows dependent logical units, such as 3270-type terminals, to gain access to applications running on a Tandem system by using a logon procedure. The ILOGMGR is an application program for the Virtual Telecommunications Access Method (VTAM) that uses standard VTAM programming interfaces to receive logon requests from dependant LUs requesting sessions with Tandem applications.
Device Logon Introduction to the ILOGMGR Device Logon The logon procedure is handled by the extended logon facility (XLF). XLF requires the interaction of four software components: • The ILOGMGR Resides on the SNA host. This process intercepts logon requests from devices and forwards those requests to the SNAX/APN subsystem. • The SNAX Creator-2 process Resides on the Tandem system.
Introduction to the ILOGMGR Device Logon Figure 1-1.
Device Logon Introduction to the ILOGMGR Figure 1-2 shows how the ILOGMGR and the TLOGMGR interact to establish a session. Upon activation, the ILOGMGR examines its control file and finds a TLOGMGR whose SNA LU name is tn1. The ILOGMGR then sends a BIND request to the appropriate TLOGMGR (tn1). SNAX/APN receives the BIND request and creates a remote LU object to represent the ILOGMGR (ibm1), thus establishing an LU-LU session (type 6.2) between the ILOGMGR and the TLOGMGR.
Introduction to the ILOGMGR Device Logon Figure 1-2.
Device Logon Introduction to the ILOGMGR Figure 1-3 shows what happens when the terminal (lua1) logs on to the application tcl1, a name that represents an application residing on the Tandem system. The terminal (lua1) logs on with the following command: LOGON APPLID (tcl1) Figure 1-3.
Introduction to the ILOGMGR Device Logon In Figure 1-4, VTAM checks to see if the ILOGMGR (ibm1) has issued an OPEN for the application (tcl1). If the ILOGMGR (ibm1) has issued an OPEN, the logon request is forwarded to the ILOGMGR (ibm1). The request identifies the target application (tcl1) and the terminal logging on (lua1). See Section 3, “Configuring for the ILOGMGR,” for detailed information about configuring the VTAM. Figure 1-4.
Device Logon Introduction to the ILOGMGR Figure 1-5 shows the ILOGMGR forwarding a Program Start Request (PROGRAM_START_REQ) to the TLOGMGR. The TLOGMGR automatically configures a remote LU object to represent the 3270 device (lua1). At this time, the LU representing the remote device is started, and the requested application (tcl1) sends a BIND to the 3270 device (lua1). Note. Program Start Requests can also be generated by the TLOGMGR.
Introduction to the ILOGMGR Device Logon Figure 1-6 shows SNAX/APN issuing a BIND request to the terminal. Once the BIND request is received, the LU-LU session begins between the application (tcl1) and the terminal (lua1). Figure 1-6.
Introduction to the ILOGMGR TLOGMGR and ILOGMGR Naming Correspondences TLOGMGR and ILOGMGR Naming Correspondences For communication between the ILOGMGR and the TLOGMGR to work, certain names must be configured to match exactly. Table 1-1 lists these as they are specified in the appropriate list or configuration file. Table 1-1.
2 Installing the ILOGMGR The ILOGMGR is distributed as a single file on the SNAX/APN release subvolume. This file must be moved to the IBM system and link-edited into a link library. The file is an entry-sequenced file of 80 byte records, with a block length of 1600 bytes. Copying ILOGMGR File From DSV to Tape The ILOGMGR file may be moved to the IBM system through methods such as Exchange/SNA or tape.
Using an Optional JCL Procedure // //STEP1 //STEPLIB //SYSPRINT //SYSUDUMP //CTLIN // 2- 2 EXEC DD DD DD DD PEND Installing the ILOGMGR CMEM=ILOGCTL PGM=&PNM,TIME=1440 DSN=&SLIB,DISP=SHR SYSOUT=&SOUT SYSOUT=&SOUT DSN=&CLIB(&CMEM),DISP=SHR 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
3 Configuring for the ILOGMGR This section describes how to configure your environment to use the ILOGMGR. You need to configure the following items: • • • The control file, which supports the ILOGMGR The VTAM list, which supports VTAM The NCP configuration, which supports the SNA communication controller This section also describes how to configure a system for multiple ILOGMGRs, TLOGMGRs, SNAX/APN lines, or some combination of the three.
Control Record Syntax Configuring for the ILOGMGR Control Record Syntax The control file contains the following control records, which define the various names and values that can be referred to by the ILOGMGR. VTAM APPL Name Control Record The VTAM APPL name defines the ILOGMGR to VTAM. The syntax for this control record is: ILOGMGR=iname where iname is a valid VTAM APPL name. The control record must begin in the first column. There can be only one VTAM APPL name control record in the control file.
Configuring for the ILOGMGR • Control Record Syntax TLOGMGR=tname TDMAPPLS=(appl-name-1,appl-name-2, appl-name-3,appl-name-4,…appl-name-n) where tname is a valid VTAM name that represents a TLOGMGR LU, and appl-name is any valid VTAM name defined as a VTAM application. If the TDMAPPLS control record appears in the TLOGMGR name control record, it must follow TLOGMGR tname, as shown in the first two examples above.
Control Record Syntax Configuring for the ILOGMGR If a request timeout is not specified, the default request timeout value is 30 seconds. Retry Open Control Record The retry open control record specifies the amount of time the ILOGMGR waits before retrying opening an access method control block (ACB). The form of this control record is: RETRYOPEN=wait-value where wait-value is a value that represents the amount of time (in seconds) the ILOGMGR waits before retrying the open.
Configuring for the ILOGMGR Using a CTLOUT Data Set Control File Example The following is an example of an ILOGMGR control file: * The following statement specifies ILOGMGR VTAM APPL name: ILOGMGR=ibm1 * The following statement identifies a SNAX/APN logon manager * and two Tandem applications that can be logged on to: TLOGMGR=tn1,TDMAPPLS=(tcl1,tcl2) * The following statement identifies a second SNAX/APN logon * manager and its associated application: TLOGMGR=tn2,TDMAPPLS=tcl3 * Note that ROUTCDE=, RTIMEO
Configuring the VTAM List Configuring for the ILOGMGR Examples of CTLOUT statements are shown below: //CTLOUT DD DSNAME=USER.CTLOUT,DISP=(OLD,KEEP) //CTLOUT DD DSNAME=USER.CTLOUT,DISP=(OLD,KEEP)5 // DCB=(RECFM=FB,LRECL=120,BLKSIZE=1200) X Note. CTLOUT closes at ILOGMGR termination. Configuring the VTAM List The following is an example of VTAM APPL definitions.
Configuring for the ILOGMGR TN1 VTAM Appl Definition File Example PUTYPE=2, XID=YES, MODETAB=MODETAB1, DLOGMOD=CICSLU62 LOCADDR=0,RESSCB=10 LU For additional information on configuring VTAM lists, see the IBM manual, Network Control Programming Resource Definition Reference. Example ILOGMGR Configurations For Token-Ring The following examples show you how to configure ILOGMGR for use with Token-Ring.
Control File (ILOGCNTL) For ILOGMGR Example PATH1 APPL Configuring for the ILOGMGR ACBNAME=PATH1, AUTH=(ACQ,SPO,PASS) x Control File (ILOGCNTL) For ILOGMGR Example The control file in the following example is called “ILOGCNTL.” ILOGMGR=ILM3 * TLOGMGR=TDMLGR1,TDMAPPLS=(TACL,PATH1) ROUTCDE=(8,11,12) RTIMEOUT=30 ILM3, TACL, and PATH1 are VTAM appl names that must be defined in a VTAM application definition file. See “VTAM Appl Definition File Example” above to see where those names are specified.
Configuring for the ILOGMGR Multiple Instances of ILOGMGR and TLOGMGR == Local TLOGMGR LU - required ADD LU #tlm3 ,TYPE (14,21), SNANAME TDMLGR1,PROTOCOL LOGON, & DLUNAME #ILM3 , CREATOR #joe,APPLFILE $SYSTEM.SYSTEM.TACL == Remote ILOGMGR LU - optional ADD LU #ILM3 , TYPE (14,21), SNANAME ILM3 , PUNAME #PU01 START LINE $TRP1,SUB ALL Note that configuring the remote ILOGMGR LU is optional.
Multiple Instances of ILOGMGR and TLOGMGR Configuring for the ILOGMGR Figure 3-1. A TLOGMGR Communicating With More Than One ILOGMGR ILOGMGR1 TLOGMGR1 line1 ILOGMGR2 007 In the above configuration, the control file and NCP are configured just as they are when a single ILOGMGR is used since each ILOGMGR is communicating with a single TLOGMGR over one SNAX/APN line. The TLOGMGR, however, must be configured to account for the two ILOGMGRs.
Configuring for the ILOGMGR Multiple Instances of ILOGMGR and TLOGMGR In this configuration, the control files and the NCP must be configured for the additional TLOGMGR. Any applications that are to be accessed through either of the TLOGMGRs also must be associated with the appropriate TLOGMGR.
Multiple Instances of ILOGMGR and TLOGMGR Configuring for the ILOGMGR Figure 3-3. An ILOGMGR in Session With Two TLOGMGRs on Separate Lines tcl1 TLOGMGR1 line1 ILOGMGR1 TLOGMGR2 line2 tcl2 014 In this configuration, the control file and the NCP must be configured for both TLOGMGRs. Any applications that are accessed through either of the TLOGMGRs must also be associated with the appropriate TLOGMGR.
4 Operating the ILOGMGR Starting ILOGMGR The ILOGMGR logon manager is started as a job under Multiple Virtual Storage (MVS). You use the MVS START command with the appropriate procedure library member name; in the following example, the name is ILOGMGR1. S is the short form of the MVS START command. S ILOGMGR1 In response, ILOGMGR1 sends the following reply: T0100-ILOGMGR(ILOGMGR1) - T6919D21 (02/16/94) 94.
Stopping ILOGMGR Operating the ILOGMGR Stopping ILOGMGR You stop the ILOGMGR by using the MVS STOP command, and the ILOGMGR responds by processing a normal termination of all active sessions. The following example shows the command for stopping the ILOGMGR, where P instructs the named ILOGMGR to stop. P is the short form of the STOP command.
Operating the ILOGMGR Controlling TLOGMGR Operation In the above example, the command processor is instructed to attempt to establish a session with the TLOGMGR named tn. This command causes a BIND to be sent to the TLOGMGR. REPLY nn,STOP TLOGMGR * In the above example, the command processor is instructed to attempt terminating the sessions with all active TLOGMGRs. The ILOGMGR checks all commands for proper syntax.
Controlling TLOGMGR Operation 4- 4 Operating the ILOGMGR 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
5 Reporting Problems If a problem occurs while using the ILOGMGR, one or more error messages are returned to the console operator. Information about ILOGMGR messages is included along with recovery information in Appendix A, “Error Messages and Sense Codes,” of this manual. Support of the ILOGMGR is typically done by IBM Data Center support personnel. If you encounter an abnormal termination, save the abend dump produced to the SYSUDUMP data set and forward the abend dump to Tandem support personnel.
Reporting Problems 5- 2 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
A Error Messages and Sense Codes Error and Informational Messages The ILOGMGR may issue the following numbered error and informational messages to the destinations specified in the routing code control record. See “Routing Code Control Record” on page 3-3 for information about routing code control record configuration. For information about sense codes and other information that are displayed at the user’s terminal, see “SNA Sense Codes and User’s Terminal Messages,” later in this section.
Error and Informational Messages Error Messages and Sense Codes T0004 T0004 - OPEN ERROR FOR tdmappls-object, CODE=acb-open-error-code tdmappls-object is the name of the TDMAPPLS object. acb-open-error-code is a VTAM access method control block (ACB) open error code. Cause. A VTAM OPEN request for the displayed TDMAPPLS object has failed with the displayed VTAM ACB open error code. This TDMAPPLS object will not be available for sessions. Effect. ILOGMGR processing continues. Recovery.
Error Messages and Sense Codes Error and Informational Messages Cause. After a logon request was processed from device-name, the displayed VTAM return code was encountered while executing the displayed VTAM request. Effect. ILOGMGR processing continues. Recovery. Report the logon error to VTAM support personnel. T0007 T0007 - LOGON device-name TO appl-name DENIED, device-name is the name of the terminal or other device that generated the logon request.
Error and Informational Messages Error Messages and Sense Codes T0009 T0009 - TIME OUT CID=cid-identifier cid-identifier is the communication identifier (CID). Cause. This warning message follows T0007 explaining that the session request identified by the displayed communication identifier (CID) has timed out while waiting for a Program Start Request from the TLOGMGR. Effect. ILOGMGR processing continues. Recovery. Report the problem to Tandem system support personnel.
Error Messages and Sense Codes Error and Informational Messages Cause.
Error and Informational Messages Error Messages and Sense Codes Cause.
Error Messages and Sense Codes Error and Informational Messages T0017 T0017 - STATUS TLOGMGR tlogmgr-name,SESSION { YES | NO } tlogmgr-name is the name of the TLOGMGR for which a STATUS command was issued. Cause. This information message follows a STATUS command and displays the current session status for the displayed TLOGMGR. Effect. The ILOGMGR continues processing. Recovery. Informational message only; no corrective action is needed. T0018 T0018 - COMMAND ACCEPTED Cause.
Error and Informational Messages Error Messages and Sense Codes T0025 T0025 - LOGON ERR - PLU=plu-name, SLU=slu-name, TANDEM CODE=error-code, sense-data plu-name is the name of the PLU associated with the logon error. slu-name is the name of the SLU associated with the logon error. error-code is a unique Tandem error code and its associated sense data. sense-data is the sense data associated with the Tandem error code. The error codes listed below describe user-recoverable actions.
Error Messages and Sense Codes Error and Informational Messages 2. Define the LU 3. Add PROTOCOL LOGON to the LU LN4800, %H08010000 Cause. The application could not be started, or communication with the application did not occur. Effect. The logon request is rejected. Recovery. To recover, do one or more of the following: 1. Start Pathmon 2. Check the Creator’s configuration 3. Check to see if the server is running LS0009, %H08010000 Cause.
Error and Informational Messages Error Messages and Sense Codes The OPEN is retried at intervals specified in the retry open control record if any of the OPEN ACB errors listed below occur. For information about the retry open control record, see “Retry Open Control Record” on page 3-4.
Error Messages and Sense Codes Error and Informational Messages Cause. This information message is displayed whenever the ILOGMGR is started. It cannot be suppressed. Effect. ILOGMGR processing continues. Recovery. Informational message only; no corrective action is needed. T0200 T0200 - ILOGMGR job-name - ACCEPTING COMMANDS >> job-name is the job name associated with this execution of the ILOGMGR. Cause. This information message is to notify the operator that an ILOGMGR is accepting commands.
SNA Sense Codes and User’s Terminal Messages Error Messages and Sense Codes T0400 T0400 - CLTOUT LOGGING STOPPED - SYNAD EXIT Cause. This message is to notify the operator that an uncorrectable I/O error occurred, and the SYNAD routine was given control. Effect. The CLTOUT data set is closed, and ILOGMGR processing continues. Recovery. Informational message only; no corrective action is needed. T0500 T0500 - CLTOUT LOGGING STOPPED - DCB EXIT Cause.
B Logical Flows and Internal Formats This appendix contains information about internal communication between the TLOGMGR, the ILOGMGR, VTAM, and the terminal. Logical Flows This subsection provides illustrations of the logical flows typical of the communication between a TLOGMGR and an ILOGMGR. Records of this communication are found in GTF traces, which are used for troubleshooting if improper processing occurs while the ILOGMGR is operational.
Logical Flows Logical Flows and Internal Formats In Figure B-2, the TLOGMGR is not available. Therefore, a termination message is sent to the terminal with a sense code indicating to the user that permission has been denied. Figure B-2. Inactive TLOGMGR Logical Flow APPLICATION TLOGMGR ILOGMGR VTAM TERMINAL Logon Logon Exit Terminate With Sense Negative Response (X'080A0101') 009 In Figure B-3, the program start request is rejected by the TLOGMGR.
Logical Flows and Internal Formats PROGRAM_START_REQ Record In Figure B-4, the time specified in the request timeout control record has elapsed before the TLOGMGR could process the request. As a result, the request is aborted, and a termination message is sent to the terminal with a sense code indicating to the user that permission has been denied. Figure B-4.
PROGRAM_START_REPLY Record Logical Flows and Internal Formats Table B-1.
Logical Flows and Internal Formats PROGRAM_START_ABORT Record Table B-3.
PROGRAM_START_ABORT Record B- 6 Logical Flows and Internal Formats 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
Glossary This glossary defines terms used and referred to in this manual. Several definitions have been borrowed from the IBM Dictionary of Computing and the IBM VTAM Programming Manual. ACB. See access method control block. access method control block (ACB). A control block that links an application program to VTAM. BIND command. The Systems Network Architecture (SNA) command that includes information necessary to establish a session between two logical units (LUs). CID. See communication identifier.
extended logon facility (XLF) Glossary extended logon facility (XLF). A configuration of SNAX/APN that allows communication between 3270 devices in an SNA subarea network and Tandem 3270 applications. This configuration requires the Tandem Logon Manager for IBM Systems and SNAX Creator-2 as corequisite software. GTF trace. IBM’s Generalized Trace Facility trace utility. host. In an SNA network, the processing unit that contains a subsystem services control point (SSCP). ILOGMGR.
Glossary Tandem Logon Manager for IBM Systems (ILOGMGR) Pathway transaction processing environment. A run-time environment consisting of Tandem’s transaction-processing products for the Guardian operating environment. This term is often shortened to “Pathway environment.” The major components of the Pathway environment are NonStop TS/MP and the run-time portions of Pathway/TS (the TCP and the SCREEN COBOL run-time environment). PROGRAM_START_ABORT.
TCP Glossary TCP. See terminal control process (TCP). terminal control process (TCP). A process used for terminal management and transaction control, provided by Tandem as part of the Pathway/TS product. A TCP is a multithreaded process that interprets compiled SCREEN COBOL requester programs (screen programs) in the user’s application, executing the appropriate program instructions for each I/O device or process the TCP is configured to handle.
Index Numbers 3270 type terminals 1-1 A Abend dump 5-1 ACB 1-1, 1-4, 3-4 Access method control block See ACB Application name parameters 3-2 B BIND image message A-5 SNA sense code X'080A0102' A-12 BIND request 1-4 C CANCEL command CID message A-4 Command processor 4-2 Commands CANCEL See CANCEL command HELP See HELP command START See START command STATUS See STATUS command STOP See STOP command syntax validation 4-3 Comment fields 3-1 Comment records 3-1 Communication identifier message See CID message
F Index F J File Utility Program commands See FUP commands FUP commands 2-1 JCL installing ILOGMGR 2-1 running ILOGMGR 4-1 Job control language See JCL G Generalized Trace Facility See GTF trace GTF trace 5-1, B-1 L LERAD exit routine message A-1 Line-handler process 1-9, 3-9 Logon exit 1-4 Logon request message A-2, A-3, A-5 SNA sense code X'080A0109' A-12 LU session request 1-8 H HELP command 4-3 messages A-7 I IBM Logon Manager See ILOGMGR ILOGMGR command processor 4-2 defined 1-1 installation e
Index Messages (continued) T0009 A-4 T0010 A-4 T0011 A-4 T0012 A-5 T0013 A-5 T0014 A-5 T0015 A-6 T0016 A-6 T0017 A-7 T0018 A-7 T0019 A-7 T0020 4-3, A-7 T0021 4-3, A-7 T0022 4-3, A-7 T0023 4-3, A-7 T0024 4-3, A-7 T0025 A-8, A-12, B-2 T0026 A-9 T0100 4-1, A-10 T0200 A-11 T0300 3-5, A-11 T0400 A-12 T0500 3-5, A-12 TDMAPPLS A-2, A-3, A-9 user data A-5 VTAM ACB name A-6 VTAM ACB OPEN command A-2, A-9 VTAM request code A-1, A-2, A-4 VTAM return code A-1, A-2, A-4 VTAM type code A-4, A-5 Multiple Virtual Storage
R Index PROGRAM_START_REQ records (continued) request code B-3 request timeout control record 3-3, 3-4 SLU name B-3 SNA sense code X'080A0107' A-12, B-3 SNA sense code X'080A0108' A-12 user data B-3 VTAM’s CID B-3 PROTOCOL LOGON error A-8 R Request timeout control record See Control records Retry open control record See Control records Routing code control record See Control records T S SCF configuration for multiple ILOGMGRs 3-11 for multiple TLOGMGRs 3-11, 3-12 for Token-Ring 3-8 Sense codes See indi
Index U User data message A-5 SNA sense code X'080A0103' A-12 V Virtual Telecommunications Access Method See VTAM VTAM ACB name message A-6 ACB OPEN command message A-2, A-9 GTF trace 5-1 request code A-1 message A-2, A-4 return code A-1 message A-2, A-4 type code message A-4, A-5 VTAM APPL definitions 3-6 file example for Token-Ring 3-7 VTAM APPL name control record See Control records VTAM list 1-2, 1-4, 1-7 APPL definitions in 3-6 example for Token-Ring 3-7 Special Characters X'080A0103' sense code X
Special Characters Index- 6 Index 127335—Tandem Logon Manager for IBM Systems (ILOGMGR) Manual
