Networking and Data Communications Library Exchange/SNA Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual describes Exchange/SNA and how to use it. Exchange/SNA provides batch-oriented data communications by emulating an IBM SNA Workstation. 104700 Fourth November 1994 Exchange/SNA D30 D30 This manual supports D30.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second Third Update 1 Fourth 84174 18997 062294 081194 104700 Exchange/SNA C10 Exchange/SNA C20 Exchange/SNA C21 Exchange/SNA D10 Exchange/SNA D30 C10 C20 C21 D10 D30 May 1988 December 1989 July 1991 February 1993 December 1994 New editions incorporate any updates issued since the previous edition.
New and Changed Information The major changes to this edition of the Exchange/RJE Manual (part number 104700) are as follows: The Guardian 90 operating system is now the Tandem NonStop Kernel. Section 3, “Exchange/SNA Commands,” has a new AUTOLOGON feature for the HELP, RESET, SET, and SHOW commands. In Section 3, there are numerous changes in the line parameter for the SHOW command. In Appendix A, “Exchange/SNA Messages,” there are numerous additions to the command interpreter and line server messages.
New and Changed Information (This page left intentionally blank) iv 104700 Tandem Computers Incorporated
Contents About This Manual xiii Notation Conventions Section 1 xv Introduction IBM 3770 SNA MLU Terminals 1-1 Devices Supported 1-1 Terminal Control Unit 1-2 Communications Capabilities 1-2 Exchange/SNA Overview 1-3 Subdevices 1-3 Communications Capabilities 1-3 Exchange/SNA Components 1-6 The Command Interpreter 1-6 The Send/Receive Server 1-6 The Line Server 1-6 The Trace Server 1-7 Component Diagram 1-8 Controlling Exchange/SNA 1-9 The Command Interpreter 1-9 The Programmatic Interface 1-9 Operati
Contents Step 4 Perform the Operation 2-8 Step 5 End the Connection 2-11 Step 6 Stop the Exchange/SNA Command Interpreter Example Operations 2-12 Starting a New Line Server 2-12 Using an Existing Line Server 2-12 Using an Existing Line Server on Another System Sending Multiple Files 2-14 Section 3 Exchange/SNA Commands RJECIS Command 3-1 Considerations 3-3 Examples 3-3 ABORT Command 3-4 Considerations 3-4 Examples 3-5 COMMENT Command 3-6 Considerations 3-6 Example 3-6 CONNECT Command 3-7 Consideratio
Contents FC Command 3-27 Considerations 3-27 Example 3-28 HELP Command 3-29 Considerations 3-29 Examples 3-29 LOG Command 3-31 Considerations 3-32 Examples 3-32 OBEY Command 3-33 Considerations 3-33 Example 3-33 RECEIVE Command 3-34 Considerations 3-37 Example 3-39 RESET Command 3-41 Considerations 3-43 Examples 3-43 SEND Command 3-44 Considerations 3-47 Example 3-47 SET Command 3-49 Considerations 3-58 Examples 3-59 SHOW Command 3-60 Considerations 3-61 Examples 3-62 STATS Command 3-64 Considerations 3-65
Contents Considerations 3-71 Examples 3-72 Section 4 Using the Exchange/SNA Programmatic Interface System Procedure Call Summary 4-1 Programming Considerations 4-2 Wait and Nowait I/O Operations 4-2 Designing Console Programs 4-5 Error Handling 4-6 The Trace Server 4-9 Step-by-Step Instructions 4-10 Step 1 Start the Line Server 4-10 Step 2 Open a Subdevice Supported by the Line Server Step 3 Set the Operational Parameters 4-11 Step 4 Perform the Operation 4-12 Step 5 Close the Subdevice 4-14 Using Exch
Contents Considerations 5-15 READ Procedure 5-16 Considerations 5-17 SETMODE Procedure 5-18 Considerations 5-19 WRITE Procedure 5-22 Considerations 5-23 WRITEREAD Procedure 5-24 Considerations 5-25 Section 6 Installation and Configuration Exchange/SNA Files 6-1 Configuring SNAX/XF for Exchange/SNA 6-2 Defining SNAX/XF Data Communications Lines SNAX/XF SCF Commands 6-3 Configuring SNAX/CDF for Exchange/SNA Configuration Requirements 6-5 Example Configuration 6-6 6-5 Configuring the IBM Host System 6
Contents Appendix C Exchange/SNA Bind Parameters Appendix D Type 1 Function Management Headers Appendix E Example Programs Send/Receive Program Example Console Program Example Appendix F E-1 E-12 Supplemental Information for D-Series Systems Overview of D-Series Exchange/SNA F-1 Compatibility and Networking Restrictions Starting High PINs F-1 F-1 Conversion of C-Series Applications F-2 File Names, Device Names, and Process Names File Name Syntax F-2 Error Message F-2 F-2 Appendix G Using
Contents Tables Table 2-1. Exchange/SNA Command Summary 2-2 Table 3-1. Finite State Machine Encoding 3-20 Table 3-2. The Trace Record FLAGS Field 3-21 Table 3-3. Vertical Forms-Control Escape Sequences Table 4-1. System Procedure Call Summary Table 4-2. Exchange/SNA Line Server Errors Table B-1. ASCII-to-EBCDIC Code Conversion B-1 Table C-1. Exchange/SNA BIND Requirements C-1 Table D-1.
Contents (This page left intentionally blank) xii 104700 Tandem Computers Incorporated
About This Manual This manual describes Exchange/SNA and how to use it. Exchange/SNA provides bit-synchronous, batch-oriented communications between a Tandem NonStop system and IBM host systems by emulating an IBM 3770-type Systems Network Architecture (SNA) Multiple Logical Unit (MLU) terminal. Audience This manual is written primarily for programmers and system analysts who design and implement communications with host systems using Exchange/SNA.
About This Manual Organization Organization This manual is organized as follows: Section 1 introduces Exchange/SNA and provides an overview of how you can use it. Section 2 provides instruction on how to use the Exchange/SNA command interpreter, including the use of command files to automate repetitive operations. Section 3 describes each Exchange/SNA command in detail. Section 4 provides instruction on how to use the Exchange/SNA programmatic interface.
Notation Conventions The following list summarizes the conventions for syntax presentation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. Lowercase italic letters represent variable items that you supply. Brackets enclose optional syntax items. A group of vertically aligned items enclosed in brackets represents a list of selections from which you can choose one or none. Braces enclose required syntax items.
Notation Conventions (This page left intentionally blank) xvi 104700 Tandem Computers Incorporated
1 Introduction Exchange/SNA provides batch data communications between Tandem systems and IBM host systems in a Systems Network Architecture (SNA) environment. Exchange/SNA provides batch data communications by emulating—in software on the Tandem system—an IBM 3770-type SNA Multiple Logical Unit (MLU) terminal. From the point of view of the host system with which Exchange/SNA is communicating, Exchange/SNA looks like an IBM 3770-type SNA MLU terminal, such as an IBM 3777 Model 3 or 4.
Introduction IBM 3770 SNA MLU Terminals Card Punches Card punches are an optional output device used by the IBM 3770 SNA MLU terminals. Output from the host system is sent to a card punch attached to an IBM 3770 SNA MLU terminal for punching on cards at the remote site. Card punches are used when the remote site requires the output in machine-readable form.
Introduction Exchange/SNA Overview Exchange/SNA Overview Exchange/SNA emulates IBM 3770 SNA MLU terminals. The purpose of Exchange/SNA is the same as the purpose of the IBM terminals being emulated—to provide batch communications for remote job entry applications with an IBM host system. Like the IBM terminals, Exchange/SNA can be used to submit jobs to a central host system and to receive output from the host.
Introduction Exchange/SNA Overview Figure 1-1 shows an overview of Exchange/SNA and the other major components required for RJE applications in an SNA environment. Note the inclusion of a communications controller between the Tandem system and the host system. In most SNA environments, a communications controller, such as an IBM 3704/3705 controller, performs network management and communications for the host system.
Introduction Exchange/SNA Overview Figure 1-1.
Introduction Exchange/SNA Components Exchange/SNA Exchange/SNA has the following components: Components Command interpreter Send/receive server Line server Trace server Each of these components is described below. The Command Interpreter The Exchange/SNA command interpreter provides a command-driven interface that enables access to all the communication capabilities of Exchange/SNA.
Introduction Exchange/SNA Components The Line Server and the Programmatic Interface The Exchange/SNA line server provides a programmatic interface. When you write a program that uses Exchange/SNA, you use standard system procedure calls to communicate with the line server. Your program passes records to and receives records from the line server, which in turn handles the communications with the host system.
Introduction Exchange/SNA Components Component Diagram Figure 1-2 illustrates the connections between the components of Exchange/SNA. Figure 1-2.
Introduction Operational Features Controlling You can control Exchange/SNA in two ways: Exchange/SNA Through commands, using the command interpreter Through file-system procedure calls, using the programmatic interface Each of these methods is described in the following sections. The Command Interpreter You can use the command interpreter in two ways: You can enter commands interactively through a terminal.
Introduction Operational Features Exchange/SNA supports the following function management headers: Sends and receives type 1 function management headers Receives type 3 function management headers For information about the BIND requirements of Exchange/SNA, see Appendix C. Function Management Protocols SNA type 1 function management headers (FMH1) are used to begin and end data streams to and from the host, except for console data (commands to the host RJE subsystem).
2 Using the Exchange/SNA Command Interpreter This section describes on how to use the Exchange/SNA command interpreter to send files to and receive files from a host system.
Using the Exchange/SNA Command Interpreter Command Summary Command Summary Table 2-1 lists the Exchange/SNA commands and briefly describes each one. Table 2-1. Exchange/SNA Command Summary Command Function ABORT Stops one or more send or receive operations initiated by the current Exchange/SNA command interpreter. identifies a comment line in a file of Exchange/SNA commands. Establishes a connection between the Exchange/SNA command interpreter, the Exchange/SNA line server, and the host.
Using the Exchange/SNA Command Interpreter Operational Considerations Operational Considerations There are a number of operational considerations you need to be aware of when using the Exchange/SNA command interpreter. These considerations are discussed below. Nowait Operation The Exchange/SNA command interpreter performs send and receive operations as nowait I/O. When you execute a SEND or RECEIVE command, you see the command interpreter’s prompt as soon as the send or receive operation has started.
Using the Exchange/SNA Command Interpreter Operational Considerations The IN Option If you use the IN option in the RJECIS command, the Exchange/SNA command interpreter reads all its input from the specified command file. When the end of the command file is reached and all outstanding send and receive operations are processed, the command file executes an implicit EXIT command; the command interpreter stops and control returns to the command interpreter (usually TACL).
Using the Exchange/SNA Command Interpreter Step 2: Set the Configuration Parameters of a line in a command file is 130 characters. Blank lines are ignored and can be included in a command file to improve readability. You can use the COMMENT command to include documentation in your command files. See the COMMENT command in Section 3 for more information.
Using the Exchange/SNA Command Interpreter Step 2: Set the Configuration Parameters Configuration Parameters When Starting a New Line Server When you intend to start a new line server by using a subsequent CONNECT command, you must specify the following configuration parameters: LINE Specifies the data communications line that you want to use. HOST Specifies the RJE subsystem on the host system. LOGON Specifies the file that contains the command required to log on to the host system.
Using the Exchange/SNA Command Interpreter Step 3: Establish the Connection CONNECT With an Exclamation Point (CONNECT !). This form of the CONNECT command does not require that the current configuration parameters match the configuration of the specified line server. Only the name must match; that is, you must specify the name of the line server in the NAME parameter of the SET command (or the RJECIS command that started the command interpreter).
Using the Exchange/SNA Command Interpreter Step 4: Perform the Operation The line server to host LU-LU sessions remain as long as the line server remains. An Exchange/SNA line server maintains a continuous connection with the host system. None of the sessions are terminated until the line server is stopped. To stop the line server, use the STOP command. When a line server is started, it records the accessor ID (user ID) of the command interpreter that started it.
Using the Exchange/SNA Command Interpreter Step 4: Perform the Operation Sending Multiple Files. To send multiple files to the host as a single stream of data, use the SEND command with the END DEFER parameter. This suppresses the sending of an end-of-file character to the host at the end of the send operation. A separate SEND command is then used to send each separate file to the host. Each SEND command must use the same subdevice.
Using the Exchange/SNA Command Interpreter Step 4: Perform the Operation Receiving a Single File. To receive a single file from the host, use the RECEIVE command with the END IMMED parameter. This stops the receive operation as soon as the host sends a type 1 function management header for the given destination subdevice with end destination selection (EDS) set, which indicates the end of the data stream (file) for the specified subdevice. Receiving Multiple Files.
Using the Exchange/SNA Command Interpreter Step 6: Stop the Exchange/SNA Command Interpreter The Command Character. The COMMAND configuration parameter is used to define a command character. When you define a command character, you define a single character that identifies a command to be sent to the host RJE subsystem. To be recognized, the command character must be the first character of a command you enter at the command interpreter’s prompt.
Using the Exchange/SNA Command Interpreter Example Operations Example Operations This subsection provides examples of how to send files to and receive files from a host system using the Exchange/SNA command interpreter. These examples do not explain the commands in detail, but merely show how the commands are used together to perform typical operations. For a detailed description of each command, refer to Section 3. Also, these examples do not show the messages displayed by the command interpreter.
Using the Exchange/SNA Command Interpreter Example Operations 4. Receive the file from the host system: >RECEIVE $DATA1.HOST1.J1OUT:#PR1 The above RECEIVE command uses default values for all parameters except the file to receive the data and the associated subdevice. 5. Disconnect from the line server: >DISCONNECT 6.
Using the Exchange/SNA Command Interpreter Example Operations Sending Multiple Files This example uses an existing line server to send three files to the host as a single data stream. 1. Start the Exchange/SNA command interpreter: > RJECIS 2. Specify the name of the existing line server: >SET NAME $L1SV 3. Establish a connection with that line server: >CONNECT ! 4. Send the first file to the host system: >SEND $DATA1.HOST1.
3 Exchange/SNA Commands This section describes the RJECIS command, which starts the Exchange/SNA command interpreter, and the individual Exchange/SNA commands. The RJECIS command is described first; then the Exchange/SNA commands are described. The Exchange/SNA commands are presented in alphabetical order for easy reference. Note In Exchange/SNA commands, parameters are separated from one another by either a comma, one or more blanks, or a comma and one or more blanks.
Exchange/SNA Commands RJECIS Command The command file can be an EDIT-format file, an unstructured disk file, a device, or another process. The maximum record size of a command file is 130 characters. If you omit this option, the Exchange/SNA command interpreter reads its input from the command interpreter’s input file, which is your terminal if you are running the Exchange/SNA command interpreter interactively.
Exchange/SNA Commands RJECIS Command Considerations The RJECIS command starts the Exchange/SNA command interpreter and is an implied TACL RUN command. For complete information on the TACL RUN command, see the TACL Reference Manual. The Exchange/SNA command interpreter cannot be run as a NonStop process pair. All the RUN command options that relate to NonStop process pairs and backup processes do not apply to the RJECIS command.
Exchange/SNA Commands ABORT Command ABORT Command The ABORT command stops one or more send or receive operations initiated by the current Exchange/SNA command interpreter. ABORT [ #subdevice | * ] #subdevice specifies an individual subdevice or a class of subdevices, such as printer subdevices. All active send and receive operations initiated by this Exchange/SNA command interpreter on the specified individual subdevice or the specified class of subdevices are stopped.
Exchange/SNA Commands ABORT Command When a receive operation is aborted, Exchange/SNA responds to the next frame in the data stream from the host system with a Request Reject Error - Break (sense data %H0811) if PURGE ON was specified, or with a Request Not Executable (sense data %H081C) if PURGE OFF was specified. Sense code %H0811 causes the host device to purge the job and leaves the device’s state unchanged; as soon as the operation is aborted, the subdevice is available for use in other operations.
Exchange/SNA Commands COMMENT Command COMMENT Command The COMMENT command identifies a comment line in a file of Exchange/SNA commands. COMMENT text text is the text of the comment line. The text must be separated from COMMENT by one or more blanks. The maximum length of the complete line is 130 characters. Considerations The COMMENT command identifies a comment line in a file of Exchange/SNA commands.
Exchange/SNA Commands CONNECT Command CONNECT Command The CONNECT command establishes a connection between the Exchange/SNA command interpreter and the Exchange/SNA line server. CONNECT [ ! ] ! specifies that, when using the CONNECT command to establish a connection with an existing line server, the current values of the configuration parameters specified in the command interpreter need not match the configuration parameters in effect when the line server was started.
Exchange/SNA Commands CONNECT Command After you have specified the required configuration parameters, use the CONNECT command to start the new line server. The CONNECT command starts the line server using the configuration parameters you have specified and establishes a connection between the command interpreter and the line server. Additionally, a connection is established between the line server and the host.
Exchange/SNA Commands CONNECT Command Duration of the Connection With the Host When the CONNECT command starts a new line server, a connection is established between the new line server and the host. The connection between the line server and the host lasts until the line server is stopped by using the Exchange/SNA STOP command.
Exchange/SNA Commands CONNECT Command Examples 1. This example shows the use of the CONNECT command to start a new line server: >set line $sna5.#luc101 >set host jes2 >set name $snl5 >set logon rdcom.logrmt19 >set logoff rdcom.
Exchange/SNA Commands DISCONNECT Command DISCONNECT The DISCONNECT command ends the connection between the Exchange/SNA Command command interpreter and the line server. DISCONNECT Considerations The DISCONNECT command ends the connection between the Exchange/SNA command interpreter and the Exchange/SNA line server. The DISCONNECT command also resets the configuration parameters to their default values. This command does not stop the command interpreter or the line server.
Exchange/SNA Commands DOWN Command DOWN Command The DOWN command takes the specified subdevice(s) out of service. DOWN [ ! ] { #subdevice | * } ! specifies that the subdevices are to be taken out of service immediately, even if send and receive operations are in progress on the subdevices. This aborts all send and receive operations on the specified subdevices. If you omit this parameter, no subdevice is taken out of service until the send or receive operation on that subdevice has completed.
Exchange/SNA Commands DOWN Command Considerations The DOWN command takes the specified subdevices out of service. After a subdevice has been taken out of service, that subdevice cannot be used by any process, including other Exchange/SNA command interpreters, until it is put back in service with the UP command. See the UP command, later in this section, for more information.
Exchange/SNA Commands DOWN Command Examples 1. This example shows the use of the DOWN command to take a single subdevice out of service. If an operation is in progress on the specified subdevice, the subdevice is not taken out of service until the operation has completed: >down #pu1 SNCI46 SUBDEVICE '#PU1' HAS BEEN DOWNED 2. This example shows the use of the DOWN command to take all subdevices out of service.
Exchange/SNA Commands DUMP Command DUMP Command The DUMP command formats and lists the contents of a trace file. DUMP FR[OM] trace-file [ parameter ]... trace-file is the name of the trace file whose contents you want to list. The file you specify must have been created by the Exchange/SNA TRACE command. If you omit the volume name, your current default volume is used. If you omit both the volume and subvolume names, your current default volume and subvolume are used.
Exchange/SNA Commands DUMP Command STE[P] displays the records from the trace file on the home terminal one at a time. You cannot include this parameter and the OUT parameter in the same DUMP command. After each record is displayed, a prompt (?) is displayed. You can respond to the prompt in the following ways: If you press the RETURN key, the next record from the trace file is displayed. If you press the RETURN key after the last record has been displayed, an error message is displayed.
Exchange/SNA Commands DUMP Command Additionally, the CONTROL format displays, in hexadecimal, the following fields: Transmission header (TC) (partial) SNALU status Sequence number Request/response header (RH) Request/response unit (RU) EB[CDIC] displays the trace records in EBCDIC. Nonprintable characters are displayed as periods. FL[OW] displays one line for each trace record.
Exchange/SNA Commands DUMP Command Request/response header (RH) Request/response unit (RU) For information about how the states of the finite-state machines are encoded, see “Considerations,” below. OC[TAL] displays the trace records in octal. Each word (16 bits) is displayed as six octal digits. LE[NGTH] displays only the length of each trace record, which is the length of RU plus 13. No data or control fields are displayed.
Exchange/SNA Commands DUMP Command If you omit the MODE parameter, only the length of each trace record (the length of the RU plus 13) is listed. No data or control fields are listed. LU { lu-number | ALL } specifies the logical units (LUs) whose trace records are to be listed. You can examine the low-order three bits of the FLAGS field to determine which LU is being used for a given data stream.
Exchange/SNA Commands DUMP Command FSM State Encoding The following table shows the codes used to represent the states of the finite-state machines (FSM) displayed by the hexadecimal format. Table 3-1.
Exchange/SNA Commands DUMP Command FLAGS. Each trace record contains a one-word bit map called FLAGS. The meaning of each bit is listed in Table 3-2. Table 3-2. The Trace Record FLAGS Field Bits Meaning .<0> .<1> .<2> Is set to 1 if the block was received from the host; otherwise, it is set to 0. Is set to 1 if the block was sent to the host; otherwise, it is set to 0. Is set to 0 for data streams from Exchange/SNA to the host (inbound).
Exchange/SNA Commands DUMP Command ?3 SNCI43 RCV BLOCK 3, TIME 15:16:39.26, ERROR 000, FLAGS 1010100000000110 LENGTH 0426 ?byte SNCI43 RCV SC: 3-3 TC: 0000 BLOCK DT: 3-3 3, TIME 15:16:39.
Exchange/SNA Commands DUMP Command RU: ^0090 0D0C 8182 8384 8586 8788 8991 9293 9495 '..abcdefghijklmn' RU: ^00A0 9697 9899 A2A3 A4A5 A6A7 A8A9 F0F1 F2F3 'opqrstuvwxyz0123' RU: ^00B0 F4F5 F6F7 F8F9 C1C2 C3C4 C5C6 C7C8 C9D1 '456789ABCDEFGHIJ' RU: ^00C0 D2D3 D4D5 D6D7 D8D9 E2E3 E4E5 E6E7 E8E9 'KLMNOPQRSTUVWXYZ' RU: ^00D0 4F7C 1515 8283 8485 8687 8889 9192 9394 '.@..
Exchange/SNA Commands DUMP Command RU: ^0100 D1D2 D3D4 D5D6 D7D8 D9E2 E3E4 E5E6 E7E8 'JKLMNOPQRSTUVWXY' RU: ^0110 E94F 7C7B 1515 1583 8485 8687 8889 9192 'Z.@#...cdefghijk' RU: ^0120 9394 9596 9798 99A2 A3A4 A5A6 A7A8 A9F0 'lmnopqrstuvwxyz0' RU: ^0130 F1F2 F3F4 F5F6 F7F8 F9C1 C2C3 C4C5 C6C7 '123456789ABCDEFG' RU: ^0140 C8C9 D1D2 D3D4 D5D6 D7D8 D9E2 E3E4 E5E6 'HIJKLMNOPQRSTUVW' RU: ^0150 E7E8 E94F 7C7B 5B15 1515 1584 8586 8788 'XYZ.@#$....
Exchange/SNA Commands DUMP Command 2. This example shows the DUMP command using the OUT parameter to direct the listing to a spooler: >dump from extrace, mode flow, out $s.#extrace SNCI56 ======================================================================= E X C H A N G E TIME L I N E T R A C E 15:16:30 DATE SERVER $SNL5 6/05/91 LINE $SNA5.
Exchange/SNA Commands EXIT Command EXIT Command The EXIT command stops the Exchange/SNA command interpreter and returns control to the command interpreter. E[XIT] Considerations The EXIT command stops the Exchange/SNA command interpreter and returns control to the command interpreter. The EXIT command is the only way to make an orderly exit from the Exchange/SNA command interpreter. Use the EXIT command when you have finished using the Exchange/SNA command interpreter.
Exchange/SNA Commands FC Command FC Command The FC command lets you edit the most recent command and enables the edited command to be executed. FC Considerations The FC command lets you edit your most recent command. You can then execute the edited command. After you enter the FC command and press RETURN, your last command is displayed. On the line below, a prompt (“.”) is displayed. Use the space bar to move the cursor under the part of the command you want to edit.
Exchange/SNA Commands FC Command If you press the BREAK key, control is returned to the Exchange/SNA command interpreter and the edited command is not executed. This lets you exit the FC command without executing the edited command. // Stops an insertion or replacement, which lets you perform another editing operation on the same line. For example, IDDD//D inserts three Ds and deletes the character above the fourth (and last) D.
Exchange/SNA Commands HELP Command HELP Command The HELP command displays a list of all the Exchange/SNA commands, or the syntax of individual commands, as specified. HELP [ command ]... [ OU[T] output-file ] command is an Exchange/SNA command name or the abbreviation for one. If you omit this parameter, a list of all Exchange/SNA commands is displayed. If you specify one or more individual commands, the syntax of each specified command is displayed.
Exchange/SNA Commands HELP Command 2.
Exchange/SNA Commands LOG Command LOG Command The LOG command specifies the information to be logged and the file to receive the information. LOG { parameter [ parameter ] | STOP } parameter is one of the following terms: TO log-file specifies the file to receive the information that is logged. If you specify a log file, the old file is closed, log-file is opened, and all information to be logged is written to log-file.
Exchange/SNA Commands LOG Command In addition to the commands themselves, the home terminal or input file that was the source of the command is also logged. This allows you to determine which of possibly several Exchange/SNA command interpreters was the source of the command. CO[NS] specifies that messages sent from Exchange/SNA to the host system’s console and messages sent from the host to the Exchange/SNA console are to be logged. AL[L] specifies that all the above types of information are to be logged.
Exchange/SNA Commands OBEY Command OBEY Command The OBEY command executes a series of Exchange/SNA commands read from a file. O[BEY] command-file command-file is the file containing the Exchange/SNA commands that you want to execute. The commands in the file are read and executed until the end of the file is reached, at which point control returns to the Exchange/SNA command interpreter and you can again enter commands interactively.
Exchange/SNA Commands RECEIVE Command RECEIVE Command The RECEIVE command receives records from the host and appends them to the specified file. RECEIVE [receive-file][:#subdevice] [ parameter ]... receive-file is the name of the file to which the records received from the host are written. If the file does not exist, an EDIT-format file is created. If the file already exists, the new records are appended to the file.
Exchange/SNA Commands RECEIVE Command parameter is one of the following terms: EN[D] { IM[MED] | DE[FER] | TI[MED] } specifies the condition that ends the receive operation. When the receive operation ends, the receive file is closed and the subdevice that was used by the receive operation becomes available for use by another receive operation.
Exchange/SNA Commands RECEIVE Command If you specify FORMS ON, vertical forms-control information is written to the receive file. If the receive file is a spooler location or a process, the vertical forms-control information is translated to the appropriate CONTROL and SETMODE procedure calls.
Exchange/SNA Commands RECEIVE Command If you omit this parameter and the receive file is an existing file of any type other than an unstructured disk file, the records are written to the receive file as received with no added blanks or truncation, provided the records are less than or equal to the record size of the receive file. Any records larger than the record size of the receive file are truncated.
Exchange/SNA Commands RECEIVE Command Magnetic Tape Files For magnetic tape files, an EOF is written at the end of each file (which is true for all types of files). Two EOFs are written at the end of the last file. The last file is the last file received in a single RECEIVE command. Escape Sequences If you specify FORMS OFF, no vertical forms-control information is written to the receive file. Multiple EBCDIC NLs cause n-1 blank lines.
Exchange/SNA Commands RECEIVE Command Examples 1. This example shows the RECEIVE command with the END IMMED parameter, which receives a single file from the host system: >receive pr:#pr1, end immed SNCI61 RECEIVE SERVER '$Z390' ( 5, 45) HAS BEEN CREATED SNSR00 FILE '$DATA3.TEST9134.PR'(DISC(EDIT)) IS BEING RECEIVED SNSR00* FROM '$SNAX1.#PR1'(SNAXSV) AT 9:46:44 ON 2/09/88 SNSR08W END-OF-FILE HAS OCCURRED ON '$SNAX1.#PR1' SNSR07 FILE '$DATA3.TEST9134.
Exchange/SNA Commands RECEIVE Command 3. This example shows the timeout value set to 45 seconds using the SET ENDTIMED parameter, and then a RECEIVE command with the END TIMED parameter (which receives files from the host system until 45 seconds elapse without a file being sent by the host system): >set endtimed 45 >receive $s.#pr1:#pr1, recsize 132, end timed SNCI61 RECEIVE SERVER '$Y391' ( 3,113) HAS BEEN CREATED SNSR00 FILE '$S.#PR1'(SPOOLER) IS BEING RECEIVED SNSR00* FROM '$SNL5.
Exchange/SNA Commands RESET Command RESET Command The RESET command sets one or more configuration parameters to their default values. RESET { * | parameter [ parameter ]... } * sets all configuration parameters to their default values. See the description of parameter, below, for a list of the configuration parameters and their default values.
Exchange/SNA Commands RESET Command LOGOF[F] sets the LOGOFF file specification to an undefined state. In this case, the STOP command sends a single record to the host that contains the command LOGOFF. The record is filled with blanks on the right to a length of 80 bytes. LOGON sets the LOGON file specification to an undefined state. A LOGON file must be specified before you start a new line server. NA[ME] sets the line server’s name to an undefined state.
Exchange/SNA Commands RESET Command TH[ROTTLE] resets the delay value to zero seconds. TRAC[E] sets TRACE off. In this case, the trace server need not be started before the connection with the host is established. TRANSP[ARENT] sets TRANSPARENT OFF. In this case, all data is sent to the host as nontransparent data. For a more complete description of the configuration parameters, see the SET command later in this section.
Exchange/SNA Commands SEND Command SEND Command The SEND command sends a file to the host. SEND [send-file][:#subdevice] [ parameter ]... send-file is the name of the file to be sent to the host. The file you specify must exist. It can be a disk file, a magnetic tape file, a device file (such as a terminal), or another process; in short, the send file can be any type of file supported by the operating system. If you omit the volume name, your current default volume is used.
Exchange/SNA Commands SEND Command parameter is one of the following terms: RE[CSIZE] size specifies the maximum size, in bytes, of the records to be sent to the host. The allowed range is from 1 through 255 unless your host subsystem is JES2, in which case the allowed range is from 1 through 254. The size you specify need not be the same as the size of the records in the send file.
Exchange/SNA Commands SEND Command CO[MPRESS] { AL[L] | BL[ANKS] | NON[E] | TRAI[LING] } specifies the type of data compression to perform, if any. The allowed types are the following: AL[L] specifies that the following types of data compression are performed: Trailing blanks are truncated. Three to sixty-three consecutive nonblank characters are compressed to a string control byte (SCB) character followed by the nonblank character that was compressed.
Exchange/SNA Commands SEND Command DE[FER] does not send an end-of-file message to the host at the end of the send file. Use this when the send file is not the last file in a multiple-file job. All files in a multiple-file job must be sent using the same subdevice and should specify the same COMPRESS and RECSIZE parameter values. The default value is END IMMED. Considerations The SEND command transmits records from the specified file to the host.
Exchange/SNA Commands SEND Command 2. This example shows the use of the SEND command to send a several files to the host system as a single job. Note the use of the END DEFER parameter on all the SEND commands except the last. >send test9135.short,end defer SNCI61 SEND SERVER '$Z585' ( 7, 50) HAS BEEN CREATED SNSR00 FILE '$DATA3.TEST9135.SHORT'(DISC(EDIT)) IS BEING SENT SNSR00* TO '$SNAX1.#RD1'(SNAXSV) AT 11:06:25 ON 2/09/88 SNSR08W END-OF-FILE HAS OCCURRED ON '$DATA3.TEST9135.SHORT' SNSR07 FILE '$DATA3.
Exchange/SNA Commands SET Command SET Command The SET command specifies values for the configuration parameters. SET parameter [ parameter ]... parameter is one of the following terms: COM[MAND] { ( chr [ , { SEN[D] | NOSE[ND] } ] ) | chr } specifies a single character that identifies commands to be sent to the host RJE subsystem. chr can be any single, printable character other than a closing parenthesis, a single quote, or a comma.
Exchange/SNA Commands SET Command Exchange/SNA line server. If defined, the console subdevice is shared by all processes using that line server. Any messages sent from the host to the console subdevice are received by all processes that are using the line server (and have opened the console subdevice). name is the name of the console subdevice. The name can be up to six alphanumeric characters, of which the first must be a letter. If you omit name, the default name is CN.
Exchange/SNA Commands SET Command LI[NE] [\system.]$location specifies the data communications line that you want to use. \system must be the name of an existing Tandem system that is part of the same Expand network as the system on which the Exchange/SNA command interpreter is running. If the line server is on the same system as the SNAX/XF data communications line or as the SNAX/CDF process, you can omit \system.
Exchange/SNA Commands SET Command In either form, $line must name an existing data communications line that was defined during system generation. lu specifies which logical unit on the data communications line the line server uses. lu can be up to six alphanumeric characters, of which the first must be a letter and the last must be the number 1. lu must be the name of an LU that has been defined for the given data communications line.
Exchange/SNA Commands SET Command If you omit this parameter, the STOP command sends a single record to the host. For SNAX/XF, Exchange/SNA sends a character-coded record that contains the command LOGOFF and is padded with blanks to a length of 80 bytes. For SNAX/CDF, the default record is a field-formatted TERM-SELF command with no parameters specified. LOGON filename names a file that is sent to the host when the CONNECT command that starts the line server is executed.
Exchange/SNA Commands SET Command system must name a Tandem system in the same Expand network as the system on which the Exchange/SNA command interpreter is running. If system is omitted, the default system is the system on which the Exchange/SNA command interpreter resides. If you specify a remote system for \system in the PROGRAM parameter, you must name the line server and specify the same remote system in the NAME parameter.
Exchange/SNA Commands SET Command PRIO[RITY] priority specifies the execution priority of the Exchange/SNA line server. priority can be a number between 1 (lowest priority) and 199 (highest priority), inclusive. priority can also be 0, which specifies that the line server is to run with the same priority as the Exchange/SNA command interpreter. See the GUARDIAN Programmer’s Guide for suggested values for priority.
Exchange/SNA Commands SET Command PUN[CH] { ( [ number ] [, class-name ] ) | number } specifies the class name of punch subdevices and the number of punch subdevices supported by the line server. Each individual punch subdevice is identified by the class name of punch subdevices and a unit number. For example, if the class name of punch subdevices is PU, then PU3 specifies the third (unit number 3) punch subdevice.
Exchange/SNA Commands SET Command RE[ADER] { ( [ number ] [, class-name ] ) | number } specifies the class name of card-reader subdevices and the number of cardreader subdevices supported by the line server. Each individual card-reader subdevice is identified by the class name of card-reader subdevices and a unit number. For example, if the class name of card-reader subdevices is RD, then RD3 specifies the third (unit number 3) card-reader subdevice.
Exchange/SNA Commands SET Command If you specify TRACE OFF, the Exchange/SNA trace server need not be started after the first CONNECT command. This does not prevent you from using the TRACE command; it merely makes it optional. If you omit this parameter, the default specification is TRACE OFF. TRANSP[ARENT] { ON | OFF } specifies whether the line server should send all data streams as transparent data.
Exchange/SNA Commands SET Command In addition to the SET command, you can specify the configuration parameters in the RJECIS command that starts the Exchange/SNA command interpreter. You can set one or more configuration parameters to their initial or default values with the RESET command; see the RESET command description earlier in this section.
Exchange/SNA Commands SHOW Command SHOW Command The SHOW command displays information about the configuration parameters, the line server, or individual subdevices. SHOW [ parameter ] [ OU[T] output-file ] parameter If you omit parameter, the SHOW command displays the current values of the configuration parameters. You can use the SET command to change the current values of the configuration parameters.
Exchange/SNA Commands SHOW Command The Exchange/SNA command interpreter must be connected to a line server in order for this form of the SHOW command to work. If the command interpreter is not connected to a line server, an error message is displayed. Use the CONNECT command to connect the command interpreter to a line server. * displays information about all subdevices that are in service. A subdevice is taken out of service by the DOWN command and placed back in service by the UP command.
Exchange/SNA Commands SHOW Command Examples 1. This example shows the SHOW command with no parameters: >show SNCI62 ======================================================================= S E T I N F O R M A T I O N SERVER $SNL5 LINE $SNA5.
Exchange/SNA Commands SHOW Command 3. This example shows the SHOW command with the #subdevice parameter: >show #rd1 SNCI62 ======================================================================= S U B D E V I C E SUBDEVICE #RD1 PRIMARY PROCESS BACKUP PROCESS PRIMARY SUBDEVICE #RD1 4. ACCESSOR GROUP.USER, (nnn,nnn) $Y442 FILE NUMBER: SNCI62 I N F O R M A T I O N BACKUP 3 ACTION SEND 0 FILE $RJE.RDCOM.
Exchange/SNA Commands STATS Command STATS Command The STATS command displays statistics about the data communications line, active send operations, or active receive operations. STATS [parameter] [ OU[T] output-file ] parameter is one of the following terms: LI[NE] [ , RES[ET] ] displays statistics about the data communications line. If you include RESET, the statistics are reset to zero after they are displayed.
Exchange/SNA Commands STATS Command Considerations The STATS command displays statistics about the data communications line, all active send operations that were started by this command interpreter, or all active receive operations that were started by this command interpreter. The Exchange/SNA command interpreter must be connected to a line server before you can use the STATS command. If the command interpreter is not connected to a line server, an error message is displayed.
Exchange/SNA Commands STATS Command STATS LINE Fields The following describes the fields in the STATS LINE display: 3–66 BIUs SENT This counter is incremented when the line server process sends a buffer to SNAX/XF or SNAX/CDF. The buffer sent contains a single BIU (plus the SNAX/XF or SNAX/CDF header). The BIU consists of a request/response header (RH) and, if required, a request/response unit (RU). This count includes both requests and responses.
Exchange/SNA Commands STOP Command STOP Command The STOP command stops the Exchange/SNA line server. STOP [ ! ] ! specifies that the line server is to be stopped immediately, even if send and receive operations are active. Any active send and receive operations are aborted.
Exchange/SNA Commands STOP Command Examples 1. This example shows the use of the STOP command without the exclamation point when one or more operations are in progress. >stop SNCI63W SNCI63* >y SNCI27 SNCI46 SNCI46 SNCI46 SNCI46 SNCI46 SNCI46 SNCI46 SNSV14 SNSV14* SNCI27 > 2.
Exchange/SNA Commands TRACE Command TRACE Command The TRACE command starts and stops the Exchange/SNA trace server, which logs the activity on the data communications line. T[RACE] { TO {trace-file | *} [ parameter ]... | ST[OP] } TO trace-file specifies the name of the file where you want to log the line activity. If the file does not exist, one is created with a file code of 904. If the file already exists, it is purged and a new one is created.
Exchange/SNA Commands TRACE Command CY[CLES] cycles specifies the maximum number of cycles that you want to allow. The trace is stopped automatically when the writing of blocks has cycled through the trace file the number of times you specify here. For example, if you specify one, the trace stops as soon as the trace file fills up. If you specify six, the trace stops after the writing of blocks has cycled through the trace file six times.
Exchange/SNA Commands UP Command UP Command The UP command places the specified subdevices back in service. UP { #subdevice | * } #subdevice specifies an individual subdevice or a class of subdevices, such as printer subdevices, to be placed back in service. subdevice consists of the name of a class of subdevices and, optionally, the unit number of an individual subdevice within the specified class of subdevices. The unit number must immediately follow the subdevice class name with no intervening blanks.
Exchange/SNA Commands UP Command Examples 1. This example shows the use of the UP command to place a single subdevice back in service. >up #pr1 SNCI46 SUBDEVICE '#PR1' HAS BEEN UPPED 2. This example shows the use of the UP command to place all subdevices back in service.
4 Using the Exchange/SNA Programmatic Interface This section provides instruction on how to use the Exchange/SNA programmatic interface to send files to and receive files from a host system.
Using the Exchange/SNA Programmatic Interface Programming Considerations Programming Considerations This subsection discusses those programming considerations that apply particularly to writing programs that use the Exchange/SNA programmatic interface. For a general discussion of programming on Tandem NonStop systems, see the Guardian Programmer’s Guide.
Using the Exchange/SNA Programmatic Interface Programming Considerations 6. Your program calls AWAITIO to wait for (or check on) the completion of the I/O operation initiated in Step 1. Depending on how you code the call to AWAITIO, your program can wait (suspend) until the I/O operation is completed or your program can continue executing even if the I/O operation is not yet complete (in which case your program must call AWAITIO again to complete the I/O operation). 7.
Using the Exchange/SNA Programmatic Interface Programming Considerations Advantages and Disadvantages An important decision in the design of any program is the choice between wait and nowait I/O operations. Each file used by your program can be opened for wait or nowait I/O operations. A single program can perform nowait I/O operations on some files while performing wait I/O operations on other files. Advantage of Wait I/O. The advantage of wait I/O operations is their simplicity.
Using the Exchange/SNA Programmatic Interface Programming Considerations Designing Console Programs You use a console application to exchange console messages with the host. You may design your program to both send and receive console messages or to only receive messages. You cannot use the application only to send messages because Exchange/SNA expects all console applications to read the messages, which are queued in buffers.
Using the Exchange/SNA Programmatic Interface Programming Considerations Error Handling Your program must check the condition code after each I/O operation to determine whether or not the I/O operation completed successfully. Failure to do so can result in undetected errors and the unpredictable operation of your program.
Using the Exchange/SNA Programmatic Interface Programming Considerations Nonrecoverable Errors You generally cannot program your applications to recover from data communications errors or problems communicating with the host, especially if a transmission is in process at the time of the failure. If you receive a serious error, such as error 140 (modem problem) or 183 (session ended), you need to intervene to: Stop the line server, if it is not already shutting down or terminated.
Using the Exchange/SNA Programmatic Interface Programming Considerations Table 4-2. Exchange/SNA Line Server Errors (Page 2 of 2) No. Meaning 22 The parameter or buffer address is out of bounds. Typically, this means that the specified buffer address is out of bounds. You called AWAITIO while there were no outstanding nowait I/O operations. This operation would exceed the number of outstanding nowait I/O operations allowed on the specified file.
Using the Exchange/SNA Programmatic Interface Programming Considerations The Trace Server You can use the Exchange/SNA trace server to log the communication between your program and the host system. To use the trace server with your programs, follow the steps below: 1. Start the Exchange/SNA command interpreter. 2. Start a named line server or connect to an existing line server using the CONNECT command. 3. Start the trace server using the TRACE command. 4.
Using the Exchange/SNA Programmatic Interface Step-by-Step Instructions Step-by-Step Most uses of the Exchange/SNA programmatic interface follow the same general Instructions sequence of steps. This sequence is outlined below. 1. Start the line server. 2. Open a subdevice supported by the line server. 3. Set the operational parameters (does not apply to console operations). 4. Perform the operation. 5. Close the subdevice. Each step is explained in detail below.
Using the Exchange/SNA Programmatic Interface Step-by-Step Instructions Each subdevice, other than the console subdevice, must be opened for exclusive access. The console subdevice can be opened for shared access. The following table shows the type of access for which you should open each type of subdevice.
Using the Exchange/SNA Programmatic Interface Step-by-Step Instructions Step 4: Perform the Operation This step is the performance of your program’s task, be it sending files, receiving files, both sending and receiving files, or controlling the console. Sending Files Use the WRITE procedure to pass records to the subdevice for transmission to the host system. The basic procedure for sending a file is outlined below.
Using the Exchange/SNA Programmatic Interface Step-by-Step Instructions Receiving Files Use the READ procedure to read the records sent from the host system to the specified subdevice (that is, the subdevice you opened). The basic procedure for receiving a file is outlined below. These steps assume you have already performed steps 1 (start line server), 2 (open device for read-only access), and 3 (set operational parameters), as outlined above. 1.
Using the Exchange/SNA Programmatic Interface Step-by-Step Instructions Console Operations This section outlines the basic procedures for a console application. These steps assume you have already performed steps 1 (start line server) and 2 (open device for read-only or read/write access), as outlined above. The console subdevice must be opened for nowait I/O. 1. Call READ with nowait I/O and wait for any console output from the host. 2.
Using the Exchange/SNA Programmatic Interface Using Exchange/SNA with Existing Programs Using Exchange/SNA The Exchange/SNA programmatic interface is a standard file-system interface.
Using the Exchange/SNA Programmatic Interface Using Exchange/SNA with Existing Programs (This page left intentionally blank) 4–16 104700 Tandem Computers Incorporated
5 Exchange/SNA System Procedure Calls This section describes the system procedure calls that an application program can use to communicate with the Exchange/SNA line server. Not all procedures that can be used are included; only those procedures that are most commonly used and have considerations specific to their use with Exchange/SNA are described here. These descriptions focus on how the procedures are used with Exchange/SNA. For examples of how the procedures are used with Exchange/SNA, see Appendix E.
Exchange/SNA System Procedure Calls AWAITIO Procedure AWAITIO Procedure The AWAITIO procedure completes (or checks for the completion of) a previously initiated nowait I/O operation. CALL AWAITIO ( filenum ,[ buffer-addr ] ,[ count-transferred ] ,[ tag ] ,[ time-limit ] ); filenum INT:ref:1 is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls AWAITIO Procedure tag INT(32):ref:1 returns a unique, application-defined value that your program uses to identify a particular I/O operation when performing nowait I/O. The value returned is the value supplied by your program when the nowait I/O operation was initiated. This parameter is required to identify individual I/O operations when a single file can have two or more nowait I/O operations outstanding at the same time.
Exchange/SNA System Procedure Calls AWAITIO Procedure Considerations You must call AWAITIO to complete a nowait I/O operation. With nowait I/O operations, control is returned to your program as soon as the operation has started without waiting for the operation to complete. A subsequent call to AWAITIO completes the nowait I/O operation and returns the results of the operation to your program.
Exchange/SNA System Procedure Calls AWAITIO Procedure You specify wait or nowait I/O in the call to OPEN that opens the subdevice (file) on which you are performing I/O operations. Wait or nowait I/O is selected on the basis of files. After you have opened a file and specified wait or nowait I/O, all subsequent I/O operations on that file are wait or nowait I/O operations according to what you specified when you opened the file.
Exchange/SNA System Procedure Calls CANCEL Procedure CANCEL Procedure The CANCEL procedure cancels the oldest outstanding I/O operation against a file opened for nowait I/O. CALL CANCEL ( filenum ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls CANCELREQ Procedure CANCELREQ The CANCELREQ procedure cancels a specific I/O operation against a file opened for Procedure nowait I/O. CALL CANCELREQ ( filenum [, tag ] ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls CLOSE Procedure CLOSE Procedure The CLOSE procedure terminates access to a previously opened subdevice supported by the Exchange/SNA line server. CLOSE ( filenum ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls CONTROL Procedure CONTROL Procedure The CONTROL procedure sends an end-of-file message, an abort transmission message, or terminates the sessions with the host and stops the line server. filenum , operation , , [ tag ] ); CALL CONTROL ( filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls CONTROL Procedure End of File The end-of-file operation (operation = 2) signals the end of the data stream to the host by sending a type 1 function management header with end of destination selection (EDS) specified. This operation is usually performed at the end of each file sent to the host or at the end of the last file in a multiple file data stream.
Exchange/SNA System Procedure Calls FILEINFO Procedure FILEINFO Procedure The FILEINFO procedure returns the number of the last error reported by the Exchange/SNA line server on the specified subdevice. CALL FILEINFO ( filenum , error ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls OPEN Procedure OPEN Procedure The OPEN procedure establishes communication between your program and a subdevice supported by the Exchange/SNA line server. filename , filenum , [ flags ] ); CALL OPEN ( filename INT:ref:12 is the name (in internal name format) of the Exchange/SNA line server and the subdevice that you want to use. The line server must already exist before you can establish communication with it.
Exchange/SNA System Procedure Calls OPEN Procedure The name you specify for the line server must be the name assigned to that line server when it was started. Typically, you would use the NAME parameter in the RJECIS command or the Exchange/SNA SET command to assign a name to the line server. See the RJECIS command and the SET command in Section 3 for more information.
Exchange/SNA System Procedure Calls OPEN Procedure .<8> Specifies whether the open message is sent to the Exchange/SNA line server in nowait I/O mode or not. 0 = The open message is sent in wait I/O mode. The open operation is complete when control is returned to your program. 1 = The open message is sent in nowait I/O mode. The open operation must be completed by a subsequent call to AWAITIO. .<9> Must be 0. .<10:11> Specifies the exclusion mode in which the Exchange/SNA line server is opened.
Exchange/SNA System Procedure Calls OPEN Procedure Considerations The OPEN procedure establishes communication between your program and a subdevice supported by the Exchange/SNA line server. The above description of the OPEN procedure describes the minimum requirements for establishing communication with an Exchange/SNA subdevice. This description omits a number of parameters that might be useful in your particular situation.
Exchange/SNA System Procedure Calls READ Procedure READ Procedure The READ procedure reads a record sent by the host to the specified subdevice. CALL READ ( , , , , filenum buffer read-count [ count-read ] [ tag ] ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls READ Procedure tag INT(32):value identifies individual nowait I/O operations when a single file can have two or more nowait I/O operations outstanding at the same time. The value of tag is a unique, arbitrary value that your program defines for each nowait I/O operation. A subsequent call to AWAITIO that completes this I/O operation returns this value to your program, identifying this I/O operation as the nowait I/O operation that just completed.
Exchange/SNA System Procedure Calls SETMODE Procedure SETMODE Procedure The SETMODE procedure sets the parameters for send and receive operations. filenum , function , param1 , [ param2 ] ); CALL SETMODE ( filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice. function INT:value specifies the operation to be performed.
Exchange/SNA System Procedure Calls SETMODE Procedure Considerations The SETMODE procedure sets parameters for send and receive operations. The function to be performed is determined by the value you specify in function. The SETMODE procedure always operates as a wait I/O operation, even if you opened the line server for nowait I/O. If you want to perform a nowait SETMODE operation, you must use the SETMODENOWAIT procedure. In this case, you must complete the operation with a call to AWAITIO.
Exchange/SNA System Procedure Calls SETMODE Procedure param1.<15> specifies whether the data sent to the host is translated from ASCII to EBCDIC before being transmitted. This parameter controls the translation of both transparent data and nontransparent data. This parameter can have the following values: 0 TRANSLATE ON The data is translated from ASCII to EBCDIC before being transmitted to the host.
Exchange/SNA System Procedure Calls SETMODE Procedure SETMODE Function 43 This function specifies the parameters that control a subsequent receive operation (calls to READ or WRITEREAD). You call SETMODE function 43 to set explicitly the parameters that control a receive operation. The section below lists the parameters you can set. param1.<13> specifies whether vertical forms-control information sent from the host is removed from the data or translated to BSC vertical forms-control escape sequences.
Exchange/SNA System Procedure Calls WRITE Procedure WRITE Procedure The WRITE procedure writes a record from your program to the specified subdevice for transmission to the host. CALL WRITE ( , , , , filenum buffer write-count [ count-written ] [ tag ] ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server. The number you specify here is the number returned by the call to OPEN that opened the subdevice.
Exchange/SNA System Procedure Calls WRITE Procedure If your program has no more than one outstanding nowait I/O operation against a single file at one time, you can omit this parameter. In this case, the file number returned by AWAITIO uniquely identifies the I/O operation that was completed. If you opened the line server for wait I/O operations, omit this parameter. Considerations The WRITE procedure writes a record from your program to the specified subdevice for transmission to the host.
Exchange/SNA System Procedure Calls WRITEREAD Procedure WRITEREAD Procedure The WRITEREAD procedure writes a record from your program to the specified subdevice for transmission to the host, or reads a record sent by the host to the specified subdevice. CALL WRITEREAD ( , , , , , filenum buffer write-count read-count [ count-read ] [ tag ] ); filenum INT:value is the file number of a previously opened subdevice supported by the Exchange/SNA line server.
Exchange/SNA System Procedure Calls WRITEREAD Procedure count-read INT:ref:1 For a wait read operation, count-read returns the number of bytes in the record received from the host (and now in buffer). For a nowait read operation, count-read is not used and can be omitted. The size of the record received from the host is returned in the count-transferred parameter of the call to AWAITIO that completes the read operation. For a write operation, count-read is not used and can be omitted.
Exchange/SNA System Procedure Calls WRITEREAD Procedure (This page left intentionally blank) 5–26 104700 Tandem Computers Incorporated
6 Installation and Configuration This section describes the files that make up the Exchange/SNA product and provides information about the Tandem system generation definitions required for Exchange/SNA. Additionally, this section provides an example of how to define Exchange/SNA on an IBM host system using JES2 and VTAM.
Installation and Configuration Configuring SNAX/XF for Exchange/SNA Configuring SNAX/XF This subsection outlines the system generation definition requirements and SCF for Exchange/SNA commands required to use a SNAX/XF data communications line with Exchange/SNA. Note Defining SNAX/XF Data Communications Lines If you are using SNAX/CDF rather than SNAX/XF, do not follow the instructions in this section. Instead refer to the subsection “Configuring SNAX/CDF for Exchange/SNA,” later in this section. .
Installation and Configuration Configuring SNAX/XF for Exchange/SNA PU Definitions You need to specify the following values as part of the definition for the physical unit. Only those parameters for which Exchange/SNA requires a specific value are listed. TYPE (13,2) is required for Exchange/SNA PUs. ADDRESS must match the NCP PU macro specification. RECSIZE must match the NCP PU macro specification. MAXLUS must match the number of LUs defined (up to six).
Installation and Configuration Configuring SNAX/XF for Exchange/SNA Example The following example shows an SCF session that starts the SNAX/XF service manager process, defines and starts a SNAX/XF communications line named $SNAS1, and defines and starts a physical unit (PU2) and its associated logical units: == Start the SNAX/XF service manager process. ALLOW ALL ERRORS START SUBSYS $SSCP == Add the SNAX/XF communications line $SNAS1.
Installation and Configuration Configuring SNAX/CDF for Exchange/SNA Configuring This subsection outlines the system generation definition requirements and the SCF SNAX/CDF for commands to configure SNAX/CDF to be used by Exchange/SNA. Exchange/SNA Before you can configure SNAX/CDF for Exchange/SNA, you need to configure the EnvoyACP/XF SDLC line for SNAX/CDF and then use the RUN command to start the SNAX/CDF process. For more information, see the SNAX/CDF Configuration and Control Manual.
Installation and Configuration Configuring SNAX/CDF for Exchange/SNA Example Configuration The following example shows how to use SCF to configure the SNAX/CDF process. ASSUME PROCESS $CDF ADD ENTRY logmode.bindexch, TBLTYPE LOGMODE, ... == The above example of the ADD ENTRY command is incomplete. == Use the command to create an entry in the logon mode == table for the Exchange/SNA BIND image required by your == installation.
Installation and Configuration IBM Host System Configuration Configuring the IBM This subsection describes typical generation statements and commands used to define Host System and start Exchange/SNA communications on an IBM host system. NCP Generation The following sample Network Control Program (NCP) generation statements are typical of what is required in the host configuration. For more detailed installation information, refer to the IBM publication IBM 3770 Installation Guide.
Installation and Configuration IBM Host System Configuration LU22C202 LU LOCADDR=2,BATCH=YES,PACING=7,VPACING=0 * LOCADDR=3,BATCH=YES,PACING=7,VPACING=0 * LOCADDR=4,BATCH=YES,PACING=7,VPACING=0 * LOCADDR=5,BATCH=YES,PACING=7,VPACING=0 * LOCADDR=6,BATCH=YES,PACING=7,VPACING=0 * * LU22C203 LU * LU22C204 LU * LU22C205 LU * LU22C206 LU * * ********************************************************* * MODE TABLES FOR MODE3770 * ********************************************************* * MODE3770 MOD
Installation and Configuration IBM Host System Configuration PSNDPAC=X'04', (12) PSERVIC=X'011000009100400000010040' (14-25) + * MODEEND END * JES2 Generation The following sample JES2 generation statements (processed within the host) show only those statements required for Exchange/SNA. For detailed installation information, refer to the IBM System Programming Library: JES2 Installation, Initialization and Tuning.
Installation and Configuration IBM Host System Configuration Starting the Line, PUs, and LUs in the Host Start the line, PUs, and LUs in the Tandem side before issuing the corresponding VTAM commands to start the PUs and LUs. If the line, PUs, and LUs have not been started in the Tandem side first, the VTAM commands will fail.
Appendix A Exchange/SNA Messages This appendix lists the messages displayed by Exchange/SNA. In those cases where the message indicates an error, the probable source of the error is given, along with suggested actions to take to recover from the error. This appendix also contains a section outlining what you should do before contacting Tandem in the event you have a problem with Exchange/SNA that you cannot solve by yourself.
Exchange/SNA Messages Exchange/SNA Trace Server Messages Trace Server This subsection describes the message issued by the Exchange/SNA trace server. Messages EXTR01E FILE ERROR error HAS OCCURRED IN TRACE PROCESS Problem. The trace server has failed due to a file-system error (whose error number is error). Solution. Determine the nature of the file-system error and correct the problem. You can use the command-interpreter ERROR command to see the text associated with the error number.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI03E ILLEGAL command-type OPTION Problem. You have specified a parameter that is invalid in the given command. Solution. Enter the command again using only valid parameters. Refer to Section 3 for a list of the parameters that are valid in each command. SNCI04E SYNTAX ERROR Problem. You have entered a command with invalid syntax. Solution. Refer to Section 3 for the syntax of each command. Enter the command again using the correct syntax.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI08W MISSING PARENTHESIS ASSUMED Problem. The command interpreter expected a parenthesis in the command that was not there. The command interpreter has inserted the missing parenthesis. Solution. No action is necessary. SNCI09E COMMAND ERROR Problem. The command interpreter does not recognize what you entered as a command. Solution. Enter a valid command. Refer to Section 3 for a list of valid commands. SNCI10E ILLEGAL FILE NAME Problem.
Exchange/SNA Messages Exchange/SNA Trace Server Messages Solution. Use the SHOW command to verify the values of the configuration parameters. Correct the values, and enter the CONNECT command again. SNCI13E $server IS THE INCORRECT LINE SERVER TYPE. Problem. You have specified in the NAME configuration parameter the name of a process other than an Exchange/SNA line server. Solution. Specify the name of an existing Exchange/SNA line server in the NAME configuration parameter, or start a new line server.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI17E COULD NOT CREATE A UNIQUE SERVER NAME FOR SYSTEM system-name, system-number. Problem. The operating system was unable to create the process. Solution. Try the operation again at a later time. SNCI18E parameter-name HAS NOT BEEN SPECIFIED. Problem. The indicated parameter (parameter name) must first be specified before you can perform the operation.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI22E CPU cpu-number DOES NOT EXIST OR IS DOWN. Problem. You have specified a CPU that does not exist or is down. Solution. Enter the command again, and specify a CPU that exists and is up. SNCI24E PROCESS ERROR message. Problem. Exchange/SNA is unable to start a new line server or send/receive server. The nature of the error is indicated in message. Solution.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI28 COMMUNICATION LINK HAS BEEN ESTABLISHED WITH HOST Comment. This message is issued when a new line server is started, and it indicates that the connection has been established with the host system. SNCI29 ENTER message TEXT 0 1 2 3 4 5 12345678901234567890123456789012345678901234567890 Comment. Enter the requested text. SNCI30 DISCONNECTED FROM LINE SERVER $server. Comment.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI33E COULD NOT CREATE A UNIQUE $server NAME. Problem. The operating system was unable to start one of the Exchange/SNA components because a unique name could not be created for the component process. Solution. Try the command at a later time. SNCI34E COULD NOT STOP TRACE PROCESS $server. Problem. The operating system was unable to stop the trace server. Solution. Try the command at a later time. SNCI35 TRACE PROCESS $server HAS BEEN STOPPED.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI38E UNKNOWN COMMAND. Problem. You have entered an unknown command. Often, this error is due to a misspelled command. Solution. Refer to Section 3 for a list of the supported commands. SNCI39 HELP INFORMATION - version-string. Comment. This message is a heading for the output of the HELP command. SNCI40E CONSOLE SERVICE INACTIVE OR NOT SUPPORTED Problem.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI42E COULD NOT LOCATE TRACE BLOCK NUMBER number. Problem. You have entered a DUMP command in which the beginning or ending sequence number is out of range. That is, the trace file does not contain records with the sequence numbers you specified. Solution. Enter the DUMP again with beginning and ending sequence numbers that are in the correct range.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI48E OPTION CAN NOT BE action WHILE CONNECTED TO A LINE SERVER. Problem. You have attempted to change a configuration parameter while connected to a line server. Configuration parameters cannot be changed while connected to a line server. Solution. Use the DISCONNECT command to disconnect from the line server, and then change the configuration parameter using the SET command. SNCI49 message. Comment. No action is required.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI53E FILE filename IS NOT A TRACE FILE. Problem. You have entered a DUMP command in which the specified file is not a trace file. Solution. Enter the DUMP command again, and specify a trace file. SNCI54E TRACE FILE filename IS EMPTY. Problem. The specified trace file is empty. Either no communications occurred over the line, or the TRACE STOP command has not been executed and all trace records are still in the trace server's buffers. Solution.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI57W send/receive SERVER name HAS stopped/aborted. Comment. The specified server has been stopped. No action is required. SNCI58W SEND SERVER line-server-name IS WAITING FOR CONTINUATION SEND Problem. You specified END DEFER in the SEND command and the send/receive server is waiting for you to send the next file. Solution. Enter another SEND command, and send the next file to the host.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI61 SEND/RECEIVE SERVER name (cpu, pin) HAS BEEN CREATED. Comment. The specified send/receive server has been started. SNCI62 ============= ... Comment. The heading for the output of the SHOW command. SNCI63W THERE ARE ACTIVE PROCESSES USING LINE SERVER SNCI63* DO YOU STILL WANT TO STOP? (Y/N) Problem. You have entered the STOP command while other processes are using the line server. Solution.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI73 SUBDEVICE CLASS-NAME MUST BE UNIQUE Problem. A subdevice name is not unique. Duplicate class-names have been given or one of the supplied class-names is a duplicate of a default name. Solution. Use the SHOW command to determine what the current assigned class-name is for each subdevice. SNCI71 heading-for-HELP-information. Comment. This message is a heading for the output of the HELP command.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI72F EXCHANGE MICROCODE NOT INSTALLED ON CPU number. Problem. The microcode necessary to run Exchange/SNA is not installed on the named CPU. Solution. Install the microcode, and start the Exchange/SNA command interpreter again. SNCI73E SUBDEVICE CLASS-NAME MUST BE UNIQUE Problem. A subdevice name is not unique. Duplicate class names have been given or one of the supplied class names is a duplicate of a default name. Solution.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI78 SERVER server-name CONNECT PROCESSING COMPLETED Comment. The specified line server established a connection with the host system. SNCI79E TRACE COMMAND IS REQUIRED TO COMPLETE CONNECT. Problem. The TRACE configuration parameter has been set ON, which requires that the trace server be started before the connection can be completed, and the trace server has not been started. Solution. Use the TRACE command to start the trace server.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI83W CONNECTED, IGNORING EXTRANEOUS CHARACTERS Comment. This warning message is displayed when CONNECT or CONNECT ! is followed by extraneous characters. SNCI84W PARAMETER NOT APPLICABLE IN EXCHANGE/SNA Comment. This warning message is displayed when you have specified parameters in the SET command that do not apply to Exchange/SNA. Common offending parameters are ACU, BACKUPCPU, BLOCKSIZE, BUFFERS, DIAL, MEMORY, and NONSTOP.
Exchange/SNA Messages Exchange/SNA Trace Server Messages SNCI99F INTERNAL PROGRAM ERROR - number Problem. number represents an internal error that should not occur. Solution. Contact your local Tandem support office.
Exchange/SNA Messages Exchange/SNA Send/Receive Server Messages Send/Receive Server This subsection lists the messages issued by the Exchange/SNA send/receive server. Messages Some of the messages are shown here on two lines even though the messages are displayed on a single line on your screen. Some message explanations indicate that you should contact your local Tandem support office.
Exchange/SNA Messages Exchange/SNA Send/Receive Server Messages SNSR04E NO CONNECT PARAMETERS PASSED. Problem. The Exchange/SNA command interpreter did not pass any connection parameters to the send/receive server. Solution. Contact your local Tandem support office. SNSR05E I/O ERROR ON FILE name SNSR05* FILE MANAGEMENT SYSTEM ERROR - number. Problem. A file-system error occurred while performing I/O on the specified file. The error that occurred is indicated by number. Solution.
Exchange/SNA Messages Exchange/SNA Send/Receive Server Messages SNSR09 SERVER TERMINATED DUE TO TIME REQUEST Comment. The specified time for END TIMED in a RECEIVE command has elapsed, and the send/receive server has stopped. SNSR10W DUPLICATE RECORD IN FILE name SNSR10* ONE OR MORE RECORDS HAVE BEEN DISCARDED. Problem. A record with a duplicate key has been found when writing the received records to a key-sequenced file. The record with the duplicate key has been discarded. Solution.
Exchange/SNA Messages Exchange/SNA Send/Receive Server Messages SNSR14E INCOMPATIBLE BINARY/COMPRESS OPTIONS SNSR14* SEND HAS BEEN ABORTED Problem. In a SEND command, you have specified TRANSLATE OFF and some value for COMPRESS other than NONE. TRANSLATE OFF requires COMPRESS NONE. This message applies only to the second or later files of a SEND END DEFER command. Solution.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSR18F EXCHANGE MICROCODE IS NOT INSTALLED ON CPU number. Problem. The required microcode is not installed. Solution. Install the required microcode, and then try the operation again. SNSR19E READY FILE name TO CONTINUE Problem. The specified files require manual intervention before the operation can continue. Typically, the specified file is a device, such as a printer, that needs to be placed online or otherwise made ready for operation. Solution.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV01F CAN'T OPEN type FILE filename SNSV01* FILE MANAGEMENT SYSTEM ERROR number SNSV01* LINE SERVER TERMINATED Problem. The line server was unable to open the specified file due to the file-system error indicated by number. Solution. Correct the cause of the error, and then try the operation again.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV02F INSUFFICIENT STORAGE SNSV02* LINE SERVER TERMINATED Problem. There is not enough memory to run the Exchange/SNA line server. This message may occur because you have configured too many subdevices for the line. Solution. Use a configuration with fewer subdevices. If this does not solve the problem, contact your local Tandem support office. SNSV03F MEMORY MANAGEMENT ERROR SNSV03* LINE SERVER TERMINATED Problem.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV06E I/O ERROR ON FILE filename SNSV06* message Problem. An I/O error occurred on the specified LU. The error is indicated by message, which contains text followed by two numbers. The first number is the number of times this error has occurred. The second number is the total number of RUs transmitted over the LU specified by filename at the time of the error. SNSV07F INVALID OUTBOUND RECORD FORMAT SNSV07* LU # ABORTED Problem.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV11F EXCHANGE MICROCODE IS NOT INSTALLED ON CPU number SNSV11* LINE SERVER TERMINATED Problem. The microcode required by Exchange/SNA is not installed. Solution. Install the required microcode and run Exchange/SNA again, or run Exchange/SNA on a processor that has the required microcode. SNSV12 CLOSE PROCESSING HAS BEEN COMPLETED SNSV12* FILE - filename Comment. The processing required to close the specified file has finished.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV16 message Comment. This message displays messages that are being placed in the system log (for example, operator commands that have been entered by other processes). SNSV17F BUFFER MANAGEMENT PROBLEM SNSV17* LINE SERVER TERMINATED Problem. Exchange/SNA is out of buffers. Solution. Specify outbound (host-to-Tandem) pacing to prevent Exchange/SNA from running out of buffers. Then restart the line server and receive the job again.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV21F COMMUNICATION FSM ERROR SNSV21* FILE - filename - ERROR %Hsense Problem. An error occurred in the finite state machine (FSM) processing of Exchange/SNA (or SNAX/XF or SNAX/CDF). filename is the LU on which the error occurred and sense is the sense data being sent or received from the host. Solution. Check sense data in the appropriate IBM SNA manual or contact your local Tandem support office.
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV26F INVALID DEVICE CONFIGURATION SNSV26* LINE SERVER TERMINATED Problem. You specified an invalid configuration of subdevices (console, printers, punches, and card readers). Solution. Use the SET command and specify a valid configuration of subdevices. See Section 3 for information on the allowed number of subdevices. SNSV27F INTERNAL ERROR - nnn ON SNSV27* SNAX LINE filename Problem. A WRITEREAD call has returned the indicated error.
Exchange/SNA Messages Exchange/SNA Line Server Messages Messages SNSV31 through SNSV54 represent the same basic problem in that the BIND request received from the host does not meet the requirements of Exchange/SNA: SNSV31 SNSV32 SNSV33 SNSV34 SNSV35 SNSV36 SNSV37 SNSV38 SNSV39 SNSV40 SNSV41 SNSV42 SNSV43 SNSV44 SNSV45 SNSV46 SNSV47 SNSV48 SNSV49 SNSV50 SNSV51 SNSV52 SNSV53 SNSV54 BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE BYTE 01 0
Exchange/SNA Messages Exchange/SNA Line Server Messages SNSV58F TRAP CODE number AT OCTAL LOCATION location SNSV58* LINE SERVER TERMINATED ABNORMALLY Problem. A critical error condition occurred during the running of this process. number is the trap code number and location is the octal offset within SNAXSV where the trap occurred. Solution. See the Guardian Programmer’s Guide for detailed information on trap handling. Save the SAVEABEND file and contact your local Tandem support office.
Exchange/SNA Messages Before Contacting Tandem Before Contacting Some of the error message explanations indicate that you need to contact your local Tandem Tandem support office to solve the problem. This section outlines the information you need to have available before you contact Tandem. Step 1.
Exchange/SNA Messages Before Contacting Tandem The history of the problem: has it happened before? If so, when, and under what conditions? Can you reproduce it? If so, state how to reproduce the problem. A list of any recent changes to the system, including but not limited to new or changed configuration parameters, new or upgraded software modules, new hardware components, or changed command files. In addition, for the following conditions, you need to prepare the additional information indicated.
Exchange/SNA Messages Before Contacting Tandem Problems After Connection. If you have a problem after successfully connecting to the host, please include the following: The information specified for connection problems. If you are reporting an Abend, include the SAVE file of the server that abnormally terminated. If you are using an application rather than the command interpreter, describe in as much detail as possible the interaction between the application and the line server.
Exchange/SNA Messages Before Contacting Tandem (This page left intentionally blank) A–38 104700 Tandem Computers Incorporated
Appendix B Character Set Translation This appendix contains the default ASCII-EBCDIC translation table and instructions for modifying this table. ASCII-EBCDIC Table B-1 shows the default correspondence between ASCII and EBCDIC. Values are Translation Table given for each in both octal and hexadecimal. If you need to modify the character translation performed by Exchange/SNA, follow the instructions in the section “Modifying Your Translation Table,” later in this appendix. Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation ASCII-EBCDIC Translation Table Table B-1.
Character Set Translation Modifying Your Translation Table Modifying Your This section explains how to modify the translation tables that Exchange/SNA uses to Translation Table translate from ASCII to EBCDIC and back. You may want to modify these tables to support a national character set other than USASCII or to implement a translation other than the supplied translation. The Exchange/SNA line server (SNAXSV) uses two tables for translating from ASCII to EBCDIC and back.
Character Set Translation Modifying Your Translation Table Step 4. Modify Your File Use the MODIFY command to change the table entries. For this example, change the entry for an exclamation point (!) in the EBCDIC^TO^ASCII table from a right square bracket (]) to an exclamation point as follows: 1. Determine the correct offset into the table. The EBCDIC code for an exclamation point is %132. The offset then is %132 / 2 = %55.
Character Set Translation Modifying Your Translation Table (This page left intentionally blank) B–12 104700 Tandem Computers Incorporated
Appendix C Exchange/SNA BIND Parameters This appendix describes the SNA BIND request parameters required by Exchange/SNA. For more information on the SNA BIND request, see the IBM manual Systems Network Architecture Formats. Table C-1. Exchange/SNA BIND Requirements (Page 1 of 6) Offset Field Description 00 Request Code %H31 BIND request code. Format and Type 0000.... ....0001 Format 0. Non-negotiable BIND request. FM Profile %H03 FM profile type 3. TS Profile %H03 TS profile type 3.
Exchange/SNA BIND Parameters Table C-1. Exchange/SNA BIND Requirements (Page 2 of 6) C–2 Offset Field Description 05 FM Usage 0....... 1....... .0...... ..01.... ..10.... ..11.... ....00.. ......0. ......1. .......1 SLU Protocol Only single RU chains allowed. Multiple RU chains allowed. Immediate-request mode. Exception-response mode. Definite-response mode. Exception- response or definite-response mode. (reserved) Compression not used by secondary. Compression used by secondary.
Exchange/SNA BIND Parameters Table C-1. Exchange/SNA BIND Requirements (Page 3 of 6) Offset Field Description 10 TS Usage %H85 or %H86 Secondary RU Size Secondary maximum RU size specification (256 bytes). TS Usage %H85 or %H86 Primary RU Size Primary maximum RU size specification (256 bytes). 12 TS Usage 0....... 1....... .0...... ..000nnn Primary Pacing Two-stage pacing used. One-stage pacing used. (reserved) Primary send pacing count. 13 TS Usage 00...... ..
Exchange/SNA BIND Parameters Table C-1. Exchange/SNA BIND Requirements (Page 4 of 6) C–4 Offset Field Description 18 PLU Usage 0....... 1....... .0...... .1...... ..0..... ..1..... ...0.... ...1.... ....0... ....1... .....0.. ......0. ......1. .......0 .......1 Data Stream Flags BS, CR, INP, ENP, LF, HT, and VT must not be sent. BS, CR, INP, ENP, LF, HT, and VT can be sent. SHF must not be sent. SHF can be sent. SVF must not be sent. SVF can be sent. SVF (Chan) and SEL must not be sent.
Exchange/SNA BIND Parameters Table C-1. Exchange/SNA BIND Requirements (Page 5 of 6) Offset Field Description 21 SLU Usage 0....... .0...... ..0..... ...0.... ....0... .....0.. ......0. .......0 FMH Flags Two destinations outstanding. Compacted data must not be sent. PDIR unsupported. Keyed direct data set unsupported. Sequential data set unsupported. Sequential access to direct data set unsupported. Series ID unsupported. Add and replace replicate unsupported. 22 SLU Usage 0...0000 .0...... ..0....
Exchange/SNA BIND Parameters Table C-1. Exchange/SNA BIND Requirements (Page 6 of 6) Offset Field Description 25 SLU Usage 0....... .0...... .1...... ..0..... ...0.... ....0... .....0.. ......0. .......0 Media Flags Document output unsupported. Card format not allowed. Card format allowed. Exchange media unsupported. Disk data format unsupported. Extended card unsupported. Extended document unsupported. SLU can send CD every EDS. (reserved) 26 CRYPTO 0000.... ....
Appendix D Type 1 Function Management Headers This appendix describes the SNA type 1 function management (FM) header. The type 1 FM header is a six-byte control field that begins and ends all data streams from Exchange/SNA to the host system other than console data. Console data is sent to the host system without type 1 FM headers. All data streams from the host system should begin and end with type 1 FM headers.
Type 1 Function Management Headers (This page left intentionally blank) D–2 104700 Tandem Computers Incorporated
Appendix E Example Programs This appendix presents two example programs. The programs assume that Exchange/SNA is connected to an IBM host system that is running OS/MVS and JES2. Send/Receive Program This program uses the programmatic interface to send and receive jobs to and from the Example host. The example program requires a line server named $SNAX1, which you must start before you run the program: Page 1 [1] $RJE.EXCHAPPL.
Example Programs Send/Receive Program Example Page 2 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87.
Example Programs Send/Receive Program Example Page 3 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 13:36:52 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. 100. 101. 102. 103. 104. 105. 106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123. 128. 129. 130.
Example Programs Send/Receive Program Example Page 4 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 132. 133. 134. 135. 136. 137. 138. 139. 140. 141. 142. 143. 144. 145. 146. 147. 148. 149. 150. 151. 152. 153. 154. 155. 156. 157. 158. 159. 160. 161. 162. 163. 164. 165. 166. 167.
Example Programs Send/Receive Program Example Page 5 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 13:36:52 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 169. 170. 171. 172. 173. 174. 175. 176. 177. 178. 179. 180. 181. 182. 183. 184. 185. 186. 187. 188. 189. 190. 191. 192. 193. 194. 195. 196. 197. 198. 199. 200. 201. 202. 203. 204. 205. 206. 207. 208.
Example Programs Send/Receive Program Example Page 6 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 210. 211. 212. 213. 214. 215. 216. 217. 218. 219. 220. 221. 222. 223. 224. 225. 226. 227. 228. 229. 230. 231. 232. 233. 234. 235. 236. 237. 238. 239. 240. 241. 242. 243. 244. 245. 246. 247. 248. 249. 250. 251. 252. 253. 254. 255. 256. 257. 258. 259. 260. 261. 262. 263. 264. 265. 266.
Example Programs Send/Receive Program Example Page 7 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 13:36:52 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 267. 268. 269. 270. 271. 272. 273. 274. 275. 276. 277. 278. 279. 280. 281. 282. 283. 284. 285. 286. 287. 288. 289. 290. 291. 292. 293. 294. 295. 296. 297. 298. 299. 300. 301. 302. 303. 304. 305. 306. 307. 308. 309. 310. 311. 312. 313. 314. 315. 316. 317. 318. 319. 320. 321. 322. 323.
Example Programs Send/Receive Program Example Page 8 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 324. 325. 326. 327. 328. 329. 330. 331. 332. 333. 334. 335. 336. 337. 338. 339. 340. 341. 342. 343. 344. 345. 346. 347. 348. 349. 350. 351. 352. 353. 354. 355. 356. 357. 358. 359. 360. 361. 362. 363. 364. 365. 366. 367. 368. 369.
Example Programs Send/Receive Program Example Page 9 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 13:36:52 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 371. 372. 373. 374. 375. 376. 377. 378. 379. 380. 381. 382. 383. 384. 385. 386. 387. 388. 389. 390. 391. 392. 393. 394. 395. 396. 397. 398. 399. 400. 401. 402. 403. 404. 405. 406. 407. 408. 409. 410. 411. 412. 413. 414. 415. 416. 417. 418.
Example Programs Send/Receive Program Example Page 10 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 420. 421. 422. 423. 424. 425. 426. 427. 428. 429. 430. 431. 432. 433. 434. 435. 436. 437. 438. 439. 440. 441. 442. 443. 444. 445. 446. 447. 448. 449. 450. 451. 452. 453. 454. 455. 456. 457. 458. 459. 460. 461. 462. 463. 464. 465. 466. 467. 468. 469. 470.
Example Programs Send/Receive Program Example Page 11 [1] $RJE.EXCHAPPL.EXAPPL 1991-06-04 13:36:52 1991-06-04 13:36:52 EXCHANGE/SNA PROGRAMMATIC EXAMPLE 472. 473. 474. 475. 476. 477. 478. 479. 480. 481. 482. 483. 484. 485. 486. 487.
Example Programs Console Program Example Console Program This section contains an example Exchange/SNA console application program: Example Page 1 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 TAL - T9250C30 - (01DEC90) Copyright Tandem Computers Incorporated 1976, 1978, 1981-83, 1985, 1987-90 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47.
Example Programs Console Program Example Page 2 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98.
Example Programs Console Program Example Page 3 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 101. 102. 103. 104. 105. 106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 129. 130. 131. 132. 133. 134. 135. 136. 137. 138. 139. 140. 141. 142. 143. 144. 145. 146. 147. 148. 149. 150. 151. 152. 153. 160. 168. 169. 188.
Example Programs Console Program Example Page 4 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 189. 190. 192. 192.1 193. 195. 196. 197. 198. 199. 200. 201. 204. 205. 206. 207. 209. 210. 211. 212. 216. 218. 219. 220. 221. 222. 223. 224. 225. 226. 227. 228. 229. 230. 231. 232. 233. 234. 237. 238. 239. 240. 242. 243. 244. 245. 246.
Example Programs Console Program Example Page 5 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 249. 250. 251. 252. 253. 254. 255. 256. 257. 258. 260. 261. 264. 265. 266. 267. 268. 271. 272. 275. 276. 277. 278. 279. 280. 282. 283. 286. 287. 288. 289. 291. 292. 293. 294. 298. 300. 301.
Example Programs Console Program Example Page 6 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 304. 305. 306. 307. 308. 309. 310. 311. 312. 313. 314. 315. 316. 320. 321. 322. 323. 325. 326. 327. 328. 332. 334. 335.
Example Programs Console Program Example Page 7 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 339. 340. 341. 342. 343. 344. 345. 346. 347. 348. 349. 350. 351. 352. 353. 356. 357. 358. 359. 360. 361. 362. 363. 364. 365. 366. 367. 368. 369. 370. 371. 372. 373. 374. 377. 378. 379. 380. 381. 382. 383. 384. 385. 386. 387. 388. 389. 390. 391. 394.
Example Programs Console Program Example Page 8 [1] $RJE.EXCHAPPL.CONSRC 1991-05-29 13:38:20 EXCHANGE/SNA CONSOLE APPLICATION EXAMPLE 395. 396. 397. 398. 399. 400. 401. 402. 403. 404. 405. 406. 409. 410. 411. 412. 413. 416. 417. 418. 419. 420. 421. 422. 423. 424. 425. 426.
Example Programs Console Program Example (This page left intentionally blank) E–20 104700 Tandem Computers Incorporated
Appendix F Supplemental Information for D-Series Systems D-series Exchange/SNA runs on Tandem’s D-series operating system and supports the features in the D-series operating system. This appendix provides specific information about the D-series Exchange/SNA product relevant to the Exchange/SNA Manual.
Supplemental Information for D-Series Systems Conversion of C Series Applications Conversion of Applications written for pre-D-series software can run on D-series software but must C-Series Applications be assigned to a low PIN. File Names, Device D-series Exchange/SNA supports the naming conventions and restrictions defined in Names, and Process C-series software for disk files, processes, disk volumes, and devices.
Appendix G Using Exchange/SNA in LU Configurations This appendix lists the new LU configurations and operations for Exchange/SNA. This appendix presents the following information: Single-LU Configuration Comparison of Single- and Multiple-LU Operations Single-LU The new AUTOLOGON feature requires support for single-LU configurations because Configuration the JES2 AUTOLOGON feature for remote workstations issues a BIND request for a single LU only.
Using Exchange/SNA in LU Configurations Using Exchange/SNA in a Single-LU Configuration contained the BDS also began a bracket (BB is set on in the RH), the BDS request is rejected with sense data %H0813, Bracket Bid Reject. If the BIU did not begin a bracket, the BDS request is rejected with sense data %H0825 (component not available). When a BDS is rejected, the host does not immediately send the BDS again.
Index 3770 SNA MLU terminals See IBM 3770 SNA MLU terminals A ABORT command 3-4/5 Abort destination selection (ADS) 3-4, 5-10 Access permissions, for subdevices 4-11 Application program interface See Programmatic interface Applications, console example E-12, E-19 program flow 4-14 Applications,console designing 4-5 ASCII character set B-1/10 ASCII-to-EBCDIC translation, modifying B-10 Asynchronous messages handling with console 4-5 AUTOLOGON configuration parameter 3-29, 3-41, 3-49, 3-60 AUTOLOGON feature G
Index Card punch subdevices See Punch subdevices Card punches, IBM 3770 SNA MLU terminals 1-2 Card readers, IBM 3770 SNA MLU terminals 1-1 Card-reader subdevices 3-57 access permissions 4-11 specifying 3-42 Character sets ASCII B-1/10 EBCDIC B-1/10 modifying translation tables B-10/11 translation table B-1 CLOSE procedure 5-8/9 Command character 2-11, 3-41, 3-49 COMMAND configuration parameter 3-41, 3-49 Command files blank lines 3-6 BREAK key, use during execution of 2-4, 3-33 comment lines 3-6 error hand
Index Command interpreter (continued) program file 6-1 receiving files See Receive operations sending commands to host 3-41, 3-49 sending files See Send operations starting 2-5, 3-1/3 starting line server 3-7 stopping 2-11, 3-26 stopping line server 3-67/69 use of BREAK key 2-3 using 2-1/14 overview 1-9 step-by-step instructions 2-5/11 using command files 2-3 Commands ABORT 3-4/5 COMMENT 3-6 CONNECT 3-7/10 DISCONNECT 3-11 DOWN 3-12/14 DUMP 3-15/25 editing 3-27/28 EXIT 3-26 FC 3-27/28 HELP 3-29/30 LOG 3-31/
Index Commands, host See Host commands Commands, TACL See TACL COMMENT command 3-6 Communication capabilities Exchange/SNA 1-3 IBM 3770 SNA MLU terminals 1-2 Compression of data using command interpreter 3-46 using programmatic interface 5-19 Condition code 4-6 Configuration parameters AUTOLOGON 3-29, 3-41, 3-49, 3-60 automatically reset to default values 3-11 COMMAND 3-41, 3-49 CONSOLE 3-41, 3-49 default values 2-6 displaying current values 3-60 ENDTIMED 3-41, 3-50 HOST 3-41, 3-50 LINE 3-41, 3-51 LOGOFF 3
Index Configuration, data communications lines host 6-7/10 SNAX/CDF 6-5 SNAX/XF 6-2 CONNECT command 3-7/10 Connections command interpreter and line server duration 3-9 ending 2-11, 3-11 establishing 2-7/8, 3-7 line server and host 2-7 duration 3-9 establishing 3-8 Considerations command interpreter use 2-3 designing console applications 4-5 programming 4-2/9 Console applications asynchronous messages 4-5 design considerations 4-5 example application program E-12/19 using programmatic interface 4-14 CONSOLE
Index D Data compression using command interpreter 3-46 using programmatic interface 5-19 console See Console data SNA sense 3-5, 5-10 translation See Translation of data transparent 3-43, 3-58 Data communications lines configuration host 6-7/10 SNAX/CDF 6-5 SNAX/XF 6-2 Tandem displaying statistics about 3-64 SCF commands 6-3/4 specification 3-41, 3-51 system generation definitions 6-2, 6-5 Data streams ending 3-46 maximum number concurrently 1-3 multiple files in single data stream 2-9 use of function man
Index End destination selection (EDS) 1-10, 4-7, 5-10 End-of-file message sending using command interpreter 3-46 sending using programmatic interface 5-10 ENDTIMED configuration parameter 3-41, 3-50 Error handling during execution of command files 2-4, 3-33 nowait I/O procedure calls 4-6 programmatic interface 4-6 Error messages command interpreter A-2/20 format A-1 line server A-25/34 send/receive server A-21/25 trace server A-2 Error numbers 4-7/8 Errors deleting host job after 3-56 nonrecoverable 4-7 re
Index Exchange/SNA (continued) diagram of communications 1-5 diagram of components 1-8 function management header support 1-10 line server See Line server overview 1-3 overview of use 1-9 relation to SNAX/CDF 1-3 relation to SNAX/XF 1-3 send/receive server See Send/receive server SNA BIND request requirements C-1/6 SNA characteristics 1-9 See Subdevices trace server See Trace server EXIT command 3-26 F FC command 3-27/28 FILEINFO procedure 5-11/12 Files associated with subdevices 1-3 command See Command fi
Index Format command files 2-4, 3-2 error messages A-1 nontransparent data, records of 3-58 transparent data, records of 3-43, 3-58 type 1 function management headers D-1 writing to unstructured disk files 3-37 Forms control, vertical 3-35, 3-38, 5-21 Function management headers and console data 1-10 supported by Exchange/SNA 1-10 type 1-1, 3-1, 4-1, 5-1, D-1 abort destination selection (ADS) 3-4, 5-10 begin destination selection (BDS) 1-10 end destination selection (EDS) 1-10, 4-7, 5-10 format D-1 overvie
Index J JES2 (Job Entry System 2) example commands 6-10 example generation statements 6-9 K Keyboard, IBM 3770 SNA MLU terminals 1-2 L LINE configuration parameter 3-41, 3-51 Line server command interpreter connection, duration 3-9 connection with host 2-7 duration 3-9 establishing 3-8 CPU specification 3-1 default configuration 2-6 displaying information about 3-60 error messages A-25/34 execution priority 3-42, 3-55 modifying translation tables B-10 multiple, concurrent users 1-7 name specification 3-42,
Index Logical units default name 3-52 limiting number of subdevices 3-3, 3-59 number used 3-52 relation to subdevices 1-3 sessions between host and Exchange/SNA 2-7 specification 3-41, 3-51 LOGOFF configuration parameter 3-42, 3-52 Logon commands, host See Host commands LOGON configuration parameter 3-42, 3-53 LU See Logical units LU definitions SNAX/XF 6-3 M MLU See Multiple logical unit Multiple logical unit (MLU) configuration compared with single logical unit (SLU) configuration G-1/2 Multiple logical
Index Operation, multiple logical unit See Multiple logical unit operation Operation, single logical unit See Single logical unit operation P Pacing specified in BIND C-1 THROTTLE parameter 3-43, 3-57 Parameters, configuration See Configuration parameters Parameters, separation of 3-1 PAUSE command, TACL 2-3 Physical unit 3-52 PRINTER configuration parameter 3-42, 3-54 Printer subdevices 3-42, 3-54 Printers, access permissions 4-11 Printers, IBM 3770 SNA MLU terminals 1-1 Priority line server execution 3-5
Index PROGRAM configuration parameter 3-42, 3-55 Program examples console E-12/19 send/receive E-1/11 Program files command interpreter 6-1 line server 3-42, 3-55, 6-1 send/receive server 6-1 trace server 6-1 where to install 6-1 Program, examples E-1 Programmatic interface aborting operations 5-10 console operations 4-14 console, example program E-12/19 error handling 4-6 error numbers 4-7/8 example program E-1/11 line server starting 4-10 stopping 5-10 nowait I/O 4-2 procedures See Procedures programming
Index Programmatic interface (continued) setting operational parameters 4-11 subdevices closing 4-14, 5-8 correspondence with type of operation 4-11, 4-13 opening 4-10, 5-12/15 use by existing programs 4-15 using overview 1-9 step-by-step instructions 4-10/14 using the trace server with 4-9 wait I/O 4-2 Programming considerations 4-2 PU 3-52 PU definitions, SNAX/XF 6-3 PUNCH configuration parameter 3-42, 3-56 Punch subdevices access permissions 4-11 specifying 3-42, 3-56 Punches, IBM 3770 SNA MLU terminals
Index Receive operations (continued) using command interpreter (continued) receiving output from host commands 2-10/11 record size 3-36 single files 2-10 subdevice used 3-34 translation of data 3-36 vertical forms control 3-35, 3-38 writing to magnetic tape files 3-38 writing to unstructured disk files 3-37 using programmatic interface 4-13, 5-16/18 aborting 5-10 nowait I/O 4-13 record size 5-16 setting operational parameters 4-11, 5-21 translation of data 5-21 vertical forms control 5-21 wait I/O 4-13 Rec
Index Send operations examples See Examples nontransparent data, characters not allowed in 3-58 sending data from your terminal to host 3-44 transparent data 3-43, 3-58 using command interpreter 3-44/48 aborting 3-4 data compression 3-46 displaying statistics about 3-64 end-of-file message 3-46 file to be sent 3-44 files with blocked records 3-47 multiple files as one data stream 2-9 overview 2-8 record size 3-45 sending commands to host 2-10/11 single files 2-8 subdevice used 3-44 translation of data 3-45
Index SNA BIND request Exchange/SNA requirements C-1/6 Exchange/SNA characteristics 1-9 MLU terminals See IBM 3770 SNA MLU terminals multiple logical unit (MLU) protocol 1-2, 1-3 sense data 3-5, 5-10 SNAX data communications lines See Data communications lines SNAX/CDF relation to Exchange/SNA 1-3 SNAX/CDF process LINE configuration 3-51 SNAX/XF LU definitions 6-3 PU definitions 6-3 relation to Exchange/SNA 1-3 STATS command 3-64/67 STOP command 3-67/69 Subdevices aborting operations on 3-4 associated file
Index Synchronous data link control protocol See SDLC SYSGEN See System generation definitions System generation definitions data communications lines 6-2 System generation definitions, data communications lines 6-5 System procedure calls See Procedures used by Exchange/SNA 5-1 system procedure calls used by Exchange/SNA 5-1 T TACL PAUSE command 2-3 RUN command 3-1, 3-3 Tandem Advanced Command Language See TACL Tandem, information to gather before contacting A-35 Terminal control unit, IBM 3770 SNA MLU ter
Index Translation of data when receiving using command interpreter 3-36 using programmatic interface 5-21 when sending using command interpreter 3-45 using programmatic interface 5-19 Translation tables example modification B-10 modifying B-10/11 TRANSPARENT configuration parameter 3-43, 3-58 Transparent data 3-43, 3-58 Type 1 function management headers See Function management headers U UP command 3-71/72 V Vertical forms control 3-35, 3-38, 5-21 VTAM example commands 6-10 W Wait I/O procedure calls 4-2 c
