Networking and Data Communications Library Exchange/RJE Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual describes Exchange/RJE and how to use it. Exchange/RJE provides batch-oriented data communications by emulating an IBM 2780 or 3780 Data Communications Terminal. 104698 Fourth December 1994 Exchange/RJE 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 84172 30091 062295 081193 104698 Exchange/RJE C10 Exchange/RJE C20 Exchange/RJE C21 Exchange/RJE D10 Exchange/RJE 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 This edition of the Exchange/RJE Manual (part number 104698) incorporates many changes and additions to the previous version (part number 081193). All changes and additions are indicated by change bars. The major changes are as follows: The Guardian 90 operating system is now called the Tandem NonStop Kernel. There is a new DEFAULT definition under the step-by-step instructions in Section 4, “Using the Exchange/RJE Programmatic Interface.
New and Changed Information (This page left intentionally blank) iv 104698 Tandem Computers Incorporated
Contents About This Manual xv Notation Conventions Section 1 xvii Introduction Exchange/RJE Components 1-1 The Command Interpreter 1-1 The Send/Receive Server 1-1 The Line Server 1-2 The Trace Server 1-2 Component Diagram 1-3 Underlying Communications Subsystems Data Communications Lines 1-4 1-4 Controlling Exchange/RJE 1-4 The Command Interpreter 1-5 The Programmatic Interface 1-5 Operational Features 1-6 2780- and 3780-Emulation Modes Block Mode 1-7 Section 2 1-6 Using the Exchange/RJE Command I
Contents Step 6 Stop the Command Interpreter 2-6 Example Operations 2-6 Using a Nonswitched Line 2-6 Using a Switched Line With an Automatic Calling Unit 2-7 Using an Existing Line Server to Send Binary Data 2-8 Using a Data Communications Line on Another System 2-9 Section 3 Exchange/RJE Commands RJECIR Command 3-1 Considerations 3-3 Examples 3-5 ABORT Command 3-6 Line Activity 3-6 Considerations 3-6 Examples 3-7 COMMENT Command 3-8 Line Activity 3-8 Considerations 3-8 Example 3-8 CONNECT Command 3-9
Contents FC Command 3-25 Line Activity 3-25 Considerations 3-25 Example 3-26 HELP Command 3-27 Line Activity 3-27 Considerations 3-27 Examples 3-27 INTERRUPT Command 3-28 Line Activity 3-28 Considerations 3-28 Example 3-29 OBEY Command 3-30 Line Activity 3-30 Considerations 3-30 Example 3-31 RECEIVE Command 3-32 Line Activity 3-37 Considerations 3-38 Examples 3-45 RESET Command 3-47 Considerations 3-48 Examples 3-49 SEND Command 3-50 Line Activity 3-53 Considerations 3-54 Examples 3-58 SET Command 3-60 Lin
Contents STATUS Command 3-73 Line Activity 3-73 Considerations 3-73 Example 3-74 TRACE Command 3-76 Line Activity 3-77 Considerations 3-77 Examples 3-77 Section 4 Using the Exchange/RJE Programmatic Interface Command Summary 4-1 System Procedure Call Summary 4-1 Programming Considerations 4-2 Using the User Library 4-2 Wait and Nowait I/O Operations Error Handling 4-4 Block Mode 4-7 The Trace Server 4-8 4-2 Step-by-Step Instructions 4-8 Step 1 Start the Line Server 4-9 Step 2 Open the Line Server 4
Contents Section 5 Exchange/RJE System Procedure Calls RJESV Command 5-2 Considerations 5-6 AWAITIO Procedure 5-7 Line Activity 5-8 Considerations 5-8 CANCEL Procedure 5-9 Line Activity 5-9 Considerations 5-9 CANCELREQ Procedure 5-10 Line Activity 5-10 Considerations 5-10 CLOSE Procedure 5-11 Line Activity 5-11 Considerations 5-11 CONTROL Procedure 5-12 Line Activity 5-13 Considerations 5-13 End of Text 5-13 End of Transmission 5-13 DEVICEINFO Procedure 5-15 Line Activity 5-15 Considerations 5-16 FILEINFO
Contents SETMODE Procedure 5-27 Line Activity 5-28 Considerations 5-28 WRITE Procedure 5-37 Line Activity 5-38 Considerations 5-39 WRITEREAD Procedure 5-40 Line Activity 5-41 Considerations 5-42 Section 6 Installation and Configuration Exchange/RJE Files 6-1 Configuring Data Communications Lines Envoy Lines 6-2 CP6100 Lines 6-4 CMI/CMP Commands Appendix A 6-6 Exchange/RJE Messages Message Format A-1 Trace Server Messages A-2 Command Interpreter Messages A-2 Send/Receive Server Messages A-19
Contents Appendix C BSC Line Control BSC Line-Control Characters C-1 The SYN Character C-1 The ENQ Character C-1 The ACK 0 Character C-1 The ACK 1 Character C-2 The STX Character C-2 The NAK Character C-3 The TTD Character C-3 The WACK Character C-3 The ETB Character C-4 The ETX Character C-4 The RVI Character C-5 The EOT Character C-5 The Pad Character C-5 BSC Line-Control Sequence Examples C-6 Normal Message Transmission C-6 Contention for the Line C-7 Unanswered Line Bid C-8 Retransmission Accepted (Te
Contents Appendix E D-Series Operating System Considerations Overview of D-Series Exchange/RJE E-1 Compatibility and Networking Restrictions Conversion of C-Series Applications E-1 E-2 File Names, Device Names, and Process Names File-Name Syntax E-2 Error Message E-2 E-2 Glossary Glossary–1 Index Figures Index–1 Figure 1-1. Tables Table 2-1. xii Exchange/RJE Components Command Summary 1-3 2-1 Table 3-1. The Trace Record FLAGS Field Table 3-2.
Contents Table 4-1. System Procedure Call Summary 4-1 Table 4-2. Exchange/RJE Line Server Errors 4-6 Table 5-1. Exchange/RJE Line Types and Subtypes Table B-1.
Contents (This page left intentionally blank) xiv 104698 Tandem Computers Incorporated
About This Manual This manual describes Exchange/RJE and how to use it. Exchange/RJE provides bytesynchronous, batch-oriented communications between a Tandem NonStop system and a variety of remote systems by emulating an IBM 2780 or 3780 Data Communications Terminal. Three additional modes of operation, collectively called block mode, are able to transfer records up to 4084 bytes long.
About This Manual Organization Organization This manual is organized as follows: Section 1 introduces Exchange/RJE and provides an overview of how you can use it. Section 2 provides instruction on how to use the Exchange/RJE command interpreter, including the use of command files to automate repetitive operations. Section 3 describes each Exchange/RJE command in detail. Section 4 provides instruction on how to use the Exchange/RJE 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) xviii 104698 Tandem Computers Incorporated
1 Introduction Exchange/RJE provides byte-synchronous, batch-oriented communications between Tandem systems and remote systems.
Introduction Exchange/RJE Components The Line Server The Exchange/RJE line server provides a record-oriented interface (using standard file-system procedure calls) that is independent of the underlying communications process, either Envoy or CP6100. The line server performs the functions required to send and receive records over the data communications line using BSC protocols.
Introduction Exchange/RJE Components Component Diagram Figure 1-1 illustrates the connections between the components of Exchange/RJE. Figure 1-1.
Introduction Underlying Communications Subsystems Underlying Exchange/RJE uses one of two underlying communications subsystems to handle Communications some of the BSC protocols and the interface with the data communications line. These Subsystems two communications subsystems are: Envoy with a byte-synchronous controller CP6100 with a 6100 communications subsystem Which one your system uses depends on your particular installation.
Introduction Underlying Communications Subsystems Block mode contains three individual modes of operation: block mode with 2780-blocking block mode with 3780-blocking block mode without blocking Exchange/RJE typically appears to the remote system as a card reader, a printer, or a card punch (these being the devices supported by 2780 and 3780 data communications terminals). Exchange/RJE is not limited to these types of devices and can use any type of device or file supported by the operating system.
Introduction Operational Features Operational Features As noted above, Exchange/RJE can operate in five different modes. The major features of these modes are presented here. Both the 2780-emulation mode and 3780emulation modes are very similar; they are discussed together first. Following that, the three individual block modes are discussed.
Introduction Operational Features 3780-emulation mode supports the compression of multiple consecutive blanks during send operations if you so specify. During receive operations, compressed blanks are automatically expanded by the line server. 2780-emulation mode does not support the compression of multiple consecutive blanks during send operations, nor does it expand compressed blanks during receive operations.
Introduction Operational Features For more information on the RJECIR, SET, and CONNECT commands, see Section 3. For more information on the RJESV and SETMODE 41 commands, see Section 5. Block Mode With 2780 and 3780 Blocking Block mode with 2780 blocking and block mode with 3780 blocking function the same as 2780-emulation mode and 3780-emulation mode, respectively, with the following exceptions: The allowed range of block sizes for both send and receive operations is from 2 to 4084 bytes.
2 Using the Exchange/RJE Command Interpreter This section provides instruction on how to use the Exchange/RJE command interpreter to send files to and receive files from a remote system. This section covers the following information: A summary of the commands Operational considerations Step-by-step instructions Example operations Command Summary Table 2-1 lists the Exchange/RJE commands and briefly describes each one. Table 2-1.
Using the Exchange/RJE Command Interpreter Operational Considerations Operational Considerations There are a number of operational considerations you need to be aware of when using the Exchange/RJE command interpreter. These considerations are discussed below. Single User Only Exchange/RJE does not support multiple concurrent users over a single data communications line.
Using the Exchange/RJE Command Interpreter Operational Considerations You can use the SHOW command to determine whether a send or receive operation is in progress. When a send or receive operation is completed, the command interpreter displays a message that shows the number of records transferred. The BREAK Key If you press the BREAK key while using the Exchange/RJE command interpreter, control of your terminal is passed back to the operating system command interpreter, which is usually TACL.
Using the Exchange/RJE Command Interpreter Operational Considerations With the OBEY command, you can enter commands interactively before and after the commands in the command file are executed. This lets you use command files to perform partial tasks, such as setting up a standard configuration, as well as complete tasks. For a detailed description of the OBEY command, see Section 3.
Using the Exchange/RJE Command Interpreter Sending and Receiving Files Using the Command Interpreter Sending and Receiving This subsection provides an overview on how to use the Exchange/RJE command Files Using the interpreter to send files to and receive files from a remote system. Command Interpreter Most uses of the command interpreter follow the same general sequence of steps. These steps are outlined below. 1. Start the command interpreter. 2. Set the configuration parameters. 3.
Using the Exchange/RJE Command Interpreter Example Operations As part of establishing the connection, the CONNECT command starts the send/receive server. If you have set the configuration parameters so that a new line server is to be used instead of an existing line server, the CONNECT command also starts the line server. The CONNECT command can start a temporary line server or a named line server depending on how you have set the configuration parameters.
Using the Exchange/RJE Command Interpreter Example Operations 3. Establish the connection with the data communications line, and specify the type of emulation to perform. >CONNECT 3780 The above CONNECT command starts the send/receive server and a temporary line server. 4. Send the job to the remote system. >SEND $DATA1.JOBS.J135C If you do not specify otherwise in the SEND command, the record size is assumed to be 80 bytes and the file is sent as normal text (as opposed to transparent text).
Using the Exchange/RJE Command Interpreter Example Operations 5. Receive the output produced by the job. >RECEIVE $DATA1.RESULTS.OJ135C 6. Disconnect from the data communications line. >DISCONNECT 7. Exit from the Exchange/RJE command interpreter. >EXIT Using an Existing Line Server to Send Binary Data This example uses an existing line server, called $SRV1, to send binary data to a remote system over a nonswitched data communications line.
Using the Exchange/RJE Command Interpreter Example Operations Using a Data Communications Line on Another System This example uses a nonswitched data communications line on another system in an EXPAND network of Tandem systems. This example starts a temporary line server on the same system as the one on which the data communications line resides. This example uses the RECEIVE command with the ALL parameter to receive a number of data files from the remote system. 1.
Using the Exchange/RJE Command Interpreter Example Operations (This page left intentionally blank) 2–10 104698 Tandem Computers Incorporated
3 Exchange/RJE Commands This section describes the RJECIR command, which starts the Exchange/RJE command interpreter, and the individual Exchange/RJE commands. The RJECIR command is described first; then the Exchange/RJE commands are described. The Exchange/RJE commands are presented in alphabetic order for easy reference. Note RJECIR Command In Exchange/RJE commands, parameters are separated from one another by either a comma, one or more blanks, or a comma and one or more blanks.
Exchange/RJE Commands RJECIR Command IN filename specifies the name of a file containing Exchange/RJE commands. If this option is specified, the command interpreter reads its input from this file. When the end of the file is reached, and all outstanding send and receive operations are processed, the command file executes an implicit EXIT; the Exchange/RJE command interpreter stops and returns control to the operating system command interpreter.
Exchange/RJE Commands RJECIR Command If you omit this option, the Exchange/RJE command interpreter writes its output to the command interpreter’s output file, which is your terminal if you are running the Exchange/RJE command interpreter interactively. parameter is one of the following terms. See the SET command for more information about these parameters: A[CU] [\system.]$acu BLOCKI[NG] { ON | OFF } BLOCKS[IZE] size C[PUS] E[BCDICNL] { ON | OFF } L[INE] [\system.
Exchange/RJE Commands RJECIR Command Starting a Remote, Temporary Line Server If you want the first CONNECT command to start a temporary line server on a system other than the system on which the Exchange/RJE command interpreter resides, specify the system on which you want to start the line server in the PROGRAM parameter. You also need to specify in the PROGRAM parameter the volume and subvolume on that system that contain the RJESV program file (usually $SYSTEM.SYSTEM). Omit the SERVER parameter.
Exchange/RJE Commands RJECIR Command The data communications line and the ACU specifications current at the time of the CONNECT command must be the same data communications line and ACU that were specified when the line server was started. Stopping a Temporary Line Server A temporary line server, local or remote, is stopped by a DISCONNECT command or an EXIT command. Stopping a Named Line Server A named line server, local or remote, is not stopped by a DISCONNECT command or an EXIT command.
Exchange/RJE Commands ABORT Command ABORT Command The ABORT command stops a send or receive operation. A[BORT] Line Activity Considerations The ABORT command sends an EOT (end of transmission) character to the remote system. This tells the remote system that the local system is unable to continue the operation. In the case of a receive operation, the remote system may or may not stop sending data depending on how it is programmed. The ABORT command stops the current send or receive operation.
Exchange/RJE Commands ABORT Command Examples 1. This example shows the use of the ABORT command to stop a send operation. >SEND d RJSR09W RJSR00 RJSR00* >ABORT RJSR14 RJSR07 RJSR07* 2. FILE RECORD SIZE(144) GREATER THAN LINE RECORD SIZE(80) FILE '$DATA3.TEST9135.D' IS BEING SENT TO '$Z721' AT 15:51:56 ON 6/08/91 FILE TRANSMISSION HAS BEEN ABORTED RECORDS 182, SIZE 70:18:63, TIME 0:00:15, RATE11.4 TRUNCATED 0 This example shows the use of the ABORT command to stop a receive operation.
Exchange/RJE Commands COMMENT Command COMMENT Command The COMMENT command identifies a comment line in a file of Exchange/RJE commands. COM[MENT] text text is the text of the comment. It can be at most 122 characters long and must be separated from the word COMMENT by one or more blanks. The maximum length of the complete command is 130 characters. Line Activity Considerations None. The COMMENT command identifies a comment line in a file of Exchange/RJE commands.
Exchange/RJE Commands CONNECT Command CONNECT Command The CONNECT command establishes a connection between the Exchange/RJE command interpreter, the send/receive server, the line server, and the data communications line. This command also starts the line server if it does not already exist. CON[NECT] { emulation-type [ parameter ]... | ! } emulation-type specifies the type of emulation to perform.
Exchange/RJE Commands CONNECT Command < Specifies the end of the telephone number. The end of the telephone number must be specified in many European telephone systems, but it is not specified in North American telephone systems. If no ACU is present and a user library has not been specified, the DIAL parameter displays a message on the operator’s console that tells the operator to dial the specified telephone number (perform a manual dial-up operation).
Exchange/RJE Commands CONNECT Command The PRIMARY or SECONDARY status of a system controls the behavior of that system in the event that both the local and the remote system bid for the line at the same time. A system that is designated SECONDARY waits three seconds (typically) between bids for the line. The system that is designated PRIMARY waits one second (typically) between bids for the line.
Exchange/RJE Commands CONNECT Command LOGON Parameter The LOGON parameter operates exactly like a SEND command. It transmits the specified file to the remote system. See the SEND command later in this section for more information on send operations. Considerations The CONNECT command establishes a connection between the command interpreter, the send/receive server, the line server, and the data communications line.
Exchange/RJE Commands CONNECT Command The line server’s mode of operation (2780 or 3780) is determined by the emulation type, BLOCKSIZE, and BLOCKING parameters. Note, however, that the emulation type is ignored if you specify BLOCKSIZE and BLOCKING OFF in either the RJECIR or SET command. If you specify BLOCKING ON in either the RJECIR or SET command, you must also specify BLOCKSIZE; otherwise, an error occurs when you issue a CONNECT command. Examples 1.
Exchange/RJE Commands DISCONNECT Command DISCONNECT The DISCONNECT command ends the connection between the Exchange/RJE Command command interpreter, the send/receive server, the line server, and the data communications line. DI[SCONNECT] Line Activity Considerations The DISCONNECT command sends a DLE EOT (disconnect sequence) to the remote system.
Exchange/RJE Commands DISCONNECT Command If the line server is a named line server, the DISCONNECT command does not stop the line server. The line server remains available for use until it is stopped. To stop a named line server, you can use the TACL STOP command. For information about the STOP command, see the TACL Reference Manual. Configuration Parameters Changed The DISCONNECT command resets all configuration parameters (except ACU and LINE) to their default values.
Exchange/RJE Commands DUMP Command DUMP Command The DUMP command formats and lists the contents of a trace file. D[UMP] F[ROM] 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/RJE TRACE command. If you omit the volume name, the default volume is your current default volume.
Exchange/RJE Commands DUMP Command O[CTAL] lists the trace records in octal. Each word (16 bits) is listed as six octal digits. If you omit the MODE parameter, only the length of each trace record (one block sent or received) is listed. No data or control characters are listed. O[UT] output-file specifies the name of the file where you want to write the output of the DUMP command.
Exchange/RJE 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 (see above) in the same DUMP command. After each record is displayed, a prompt (?) is displayed. You can respond to the prompt in the following ways: displays the next record from the trace file. If you press the RETURN key after the last record has been displayed, an error message is displayed.
Exchange/RJE Commands DUMP Command L[ENGTH] displays only the length of each block transmitted or received. No data or control characters are displayed. This is the default display mode. O[CTAL] displays the trace records in octal. Each word (16 bits) is displayed as six octal digits. Q[UIT] | EX[IT] stops STEP mode and returns control to the Exchange/RJE command interpreter. Line Activity Considerations None. The DUMP command formats and lists the contents of a trace file.
Exchange/RJE Commands DUMP Command FLAGS Field Each trace record contains a one-word bit map called FLAGS. The meaning of each bit is listed in Table 3-1. Table 3-1. The Trace Record FLAGS Field Bits Meaning .<0> .<1> .<2> Is set to 1 if the block was received from the remote system. Otherwise, it is set to 0. Is set to 1 if the block was sent to the remote system. Otherwise, it is set to 0. Is set to 1 if the trace record is for a call to CONTROL for an Envoy line.
Exchange/RJE Commands DUMP Command Examples 1. This example shows the DUMP command with the STEP parameter. >dump from trace,step RJCI56 ======================================================================= E X C H A N G E / R J E TIME L I N E DATE SERVER $Y874 6/09/91 LINE $RJE3 ACU PHONE NUMBER LINE BUFFERS 1 BLOCKSIZE 400 EBCDIC YES TRANSPARENCY NO PROGRAM FILE: $DATA3.AGW9135.RJESV ACCESSOR: GROUP.
Exchange/RJE Commands DUMP Command %0360 167 170 171 172 060 061 062 063 064 065 066 067 070 071 101 102 %0400 103 104 105 106 107 110 111 112 113 114 115 116 117 120 121 122 %0420 123 124 125 126 127 130 131 132 041 100 031 027 ?control RJCI43 XMIT BLOCK 0, TIME 16:41:38.
Exchange/RJE Commands DUMP Command ^00E0 8788 8991 9293 9495 9697 9899 A2A3 A4A5 'ghijklmnopqrstuv' ^00F0 A6A7 A8A9 F0F1 F2F3 F4F5 F6F7 F8F9 C1C2 'wxyz0123456789AB' ^0100 C3C4 C5C6 C7C8 C9D1 D2D3 D4D5 D6D7 D8D9 'CDEFGHIJKLMNOPQR' ^0110 E2E3 E4E5 E6E7 E8E9 4F7C 1926 'STUVWXYZ!@..' ?octal RJCI43 XMIT BLOCK 0, TIME 16:41:38.
Exchange/RJE Commands EXIT Command EXIT Command The EXIT command stops the Exchange/RJE command interpreter and returns control to the operating system command interpreter. E[XIT] Line Activity Considerations The EXIT command causes no line activity, unless you choose to exit while still connected. If you do issue the EXIT command while still connected, the command performs an implicit disconnect operation.
Exchange/RJE Commands FC Command FC Command The FC command edits the last command and allows the edited command to be executed. FC Line Activity Considerations None. The FC command lets you edit your last command. You can then execute the edited command. After you enter the FC command, your last command is displayed. On the line below, a prompt (“.”) is displayed. You use the space bar to move the cursor under the part of the command you want to edit.
Exchange/RJE Commands FC Command Returns control to the Exchange/RJE command interpreter without submitting the edited command to the Exchange/RJE command interpreter for execution. 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/RJE Commands HELP Command HELP Command The HELP command displays a list of the Exchange/RJE commands or the syntax of individual commands. H[ELP] [ command ]... [ OU[T] output-file ] command is an Exchange/RJE command or the abbreviation for one. If you omit this parameter, a list of all Exchange/RJE commands is displayed. If you specify one or more individual commands, the syntax of each specified command is displayed.
Exchange/RJE Commands INTERRUPT Command INTERRUPT Command The INTERRUPT command requests the remote system to stop transmitting data to the local system. I[NTERRUPT] Line Activity The INTERRUPT command sends an EOT in response to the first block received after the command is entered. Subsequent blocks (if any) are acknowledged with an ACK 1 or ACK 0 (or NAK) as appropriate. The receive operation continues until stopped by the remote system.
Exchange/RJE Commands INTERRUPT Command Example This example shows the INTERRUPT command followed by a RECEIVE command with the ALL parameter specified. The RECEIVE ALL command is then stopped with an ABORT command. >receive pr RJSR00 PRINT FILE '$DATA3.TEST9135.
Exchange/RJE Commands OBEY Command OBEY Command The OBEY command executes a series of Exchange/RJE commands read from a file. O[BEY] command-file command-file is the file containing the Exchange/RJE 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/RJE command interpreter and you can again enter commands interactively. Typically, command-file is a standard EDIT-format text file.
Exchange/RJE Commands OBEY Command To return to the Exchange/RJE command interpreter, enter the TACL PAUSE command. The PAUSE command returns control of your terminal to the Exchange/RJE command interpreter, and execution of the command file continues from where it left off. For more information about the PAUSE command, see the TACL Reference Manual. Example The following example shows the OBEY command. The commands in the command file are displayed as they are executed. >obey hqjobs.
Exchange/RJE Commands RECEIVE Command RECEIVE Command The RECEIVE command receives records from the remote system and appends them to the specified file. REC[EIVE] [ print-file | ( print-file, punch-file ) ] [ parameter ]... print-file is the name of the file where you want to write the records received from the remote system. If the file does not exist, an EDIT-format file is created. If the file already exists, the new records are appended to the end of the file.
Exchange/RJE Commands RECEIVE Command A file from the remote system that is to be written to the punch file is identified by a device select sequence at the beginning of the file. The recognized device select sequences are: Symbols EBCDIC Code ASCII Code 2780 ESC 4 %H27 F4 %H1B 34 3780 DC2 DC3 %H12 %H13 %H12 %H13 To be recognized, the device select sequences must be the first characters in the first block of the file. The first block must also be transmitted as normal text, not transparent text.
Exchange/RJE Commands RECEIVE Command If you specify EBCDICNL ON, the NL character is passed on as ASCII data (%H85) and not interpreted as a record separator for the duration of the RE command. If you specify EBCDICNL OFF, the NL character functions as a record separator for the duration of the RECEIVE command. If you omit this parameter, the global mode of the line server remains in effect. This parameter is ignored for block mode without blocking operations.
Exchange/RJE Commands RECEIVE Command The RAWDATA parameter captures only message blocks that are received from the remote system, and thus captures only half of the communication between the local and the remote system. If you want to capture the complete communication between the two systems, use the TRACE command to capture the communication and the DUMP command to format and list the captured data. For more information, see the TRACE command and the DUMP command in this section.
Exchange/RJE Commands RECEIVE Command The RETRIESEOT value can be set in both the SET and RECEIVE commands; if you specify it in both places, Exchange/RJE uses the value in the RECEIVE command. If you omit this parameter in this command, but include it in the SET command, Exchange/RJE uses the value in the SET command. This parameter can be reset to the default value by using the RESET command; it is automatically reset to the default value after a DISCONNECT or EXIT command.
Exchange/RJE Commands RECEIVE Command If you specify TRANSLATE and the remote system sends the data as transparent text (each text block begins with DLE STX), the data is translated from EBCDIC to ASCII before it is written to the print file. This translation takes place even if the data communications line is defined as an ASCII line. If you omit this parameter, the default value is TRANSLATE. Line Activity The RECEIVE command does not itself initiate any line activity.
Exchange/RJE Commands RECEIVE Command Considerations The RECEIVE command receives records from the remote system and appends those records to the end of the specified file. Before you can use the RECEIVE command, you must have established a connection between Exchange/RJE and the data communications line by using the CONNECT command. For information on establishing a connection, see the CONNECT command earlier in this section.
Exchange/RJE Commands RECEIVE Command Table 3-3. 3780-Emulation Mode RECEIVE Command Block Formats Normal-Text Block Format All blocks except last: Last block: Maximum block size: Maximum record size: STX record [ IRS record ]... IRS ETB STX record [ IRS record ]... IRS ETX 520 bytes (includes 1 byte each for STX and ETB/ETX) 146 bytes for the print file 80 bytes for the punch file Records cannot contain any BSC control characters.
Exchange/RJE Commands RECEIVE Command Table 3-4. Block Mode With 2780 Blocking RECEIVE Command Block Formats Normal-Text Block Format All blocks except last: Last block: Maximum block size Maximum record size: STX record [ EM ] [ ITB record [ EM ] ]... ETB STX record [ EM ] [ ITB record [ EM ] ]... ETX 4086 bytes (includes 1 byte each for STX and ETB/ETX) BLOCKSIZE for the print file 80 bytes for the punch file Records cannot contain any BSC control characters.
Exchange/RJE Commands RECEIVE Command Table 3-5. Block Mode With 3780 Blocking RECEIVE Command Block Formats Normal-Text Block Format All blocks except last: Last block: Maximum block size Maximum record size: STX record [ IRS record ]... IRS ETB STX record [ IRS record ]... IRS ETX 4086 bytes (includes 1 byte each for STX and ETB/ETX) BLOCKSIZE - 1 for the print file 80 bytes for the punch file Records cannot contain any BSC control characters.
Exchange/RJE Commands RECEIVE Command Table 3-6. Block Mode Without Blocking RECEIVE Command Block Formats Normal-Text Block Format All blocks except last: Last block: Maximum block size Maximum record size: STX record ETB STX record ETX 4086 bytes (includes 1 byte each for STX and ETB/ETX) BLOCKSIZE for the print file 80 bytes for the punch file Records cannot contain any BSC control characters. Block mode without blocking treats each block received as a single record.
Exchange/RJE Commands RECEIVE Command Translation of Normal Text Whether data that Exchange/RJE receives as normal text is translated from EBCDIC to ASCII depends on how the data communications line was defined during system generation. There are two cases to consider: data communications lines defined as EBCDIC lines and those defined as ASCII lines. Each case is discussed below.
Exchange/RJE Commands RECEIVE Command The first additional byte contains the number of the file received from the remote system that contains that record. The numbers begin with 0 (zero) and are incremented by 1 for each file received. The numbers are reset to 0 with each new RECEIVE command.
Exchange/RJE Commands RECEIVE Command Vertical Forms-Control Escape Codes Table 3-7 lists the escape codes for vertical forms control that are recognized by Exchange/RJE. Table 3-7.
Exchange/RJE Commands RECEIVE Command 2. This example shows the use of the RECEIVE command to write the received data to a spooler location. >RECEIVE $S.#JOBPR RJSR00 PRINT FILE '$S.#JOBPR' IS BEING RECEIVED FROM RJSR00* '$Z074' AT 13:37:46 ON 6/17/91 RJSR14 FILE TRANSMISSION HAS BEEN COMPLETED RJSR07 PRINT RECORDS 94, SIZE 107:1:60, TIME 0:00:06, RATE 13.5 RJSR07* PUNCH RECORDS 0, SIZE 0:0: 0, TIME 0:00:00, RATE 0.0 RJSR07* TOTAL RECORDS 94, TIME 0:00:06, RATE 13.5 3.
Exchange/RJE Commands RESET Command RESET Command The RESET command sets one or more configuration parameters to their default values. RES[ET] { * | parameter [, parameter] ...} * sets all configuration parameters to their default values. See the list of terms under parameter below for a list of the configuration parameters and their default values. parameter is one of the following terms: ACU blanks out the ACU name, with the effect that no ACU is used. BLOCKI[NG] sets BLOCKING to OFF.
Exchange/RJE Commands RESET Command PRI[ORITY] sets the line server’s execution priority to the same priority as the Exchange/RJE command interpreter. PRO[GRAM] sets the program file from which a line server is started to the RJESV file on the system, volume, and subvolume on which the Exchange/RJE command interpreter resides. RETRIESE[OT] resets the value of RETRIESEOT to -1, indicating that the remote station can send an EOT with no preceding text an unlimited number of times.
Exchange/RJE Commands RESET Command Examples 1. This example shows the use of the RESET command to reset the ACU configuration parameter. >RESET ACU 2. This example shows the use of the RESET command to reset all configuration parameters.
Exchange/RJE Commands SEND Command SEND Command The SEND command sends a file to the remote system. SEN[D] [ send-file ] [ parameter ]... send-file is the name of the file to be sent to the remote system. The file you specify must exist. If you include the NOTRANSLATE parameter or the TRANSPARENT parameter in the SEND command, the send file must contain fixed-length, 80-byte records. If you omit the volume name, the default volume is your current default volume.
Exchange/RJE Commands SEND Command D[ROPEM] suppresses the appending of an end-of-media (EM) character to records less than 80 bytes long in 2780-emulation mode and block mode with 2780 blocking. This parameter does not apply to 3780-emulation mode, block mode with 3780 blocking, or block mode without blocking. (No end-of-media character is used in 3780-emulation mode.) If you omit this parameter, an end-of-media (EM) character is appended to all records less than 80 bytes in length.
Exchange/RJE Commands SEND Command TRANSL[ATE] | NOTRANSL[ATE] controls the translation of data from ASCII to EBCDIC. If you specify NOTRANSLATE, the data is not translated from ASCII to EBCDIC before it is transmitted and the data is transmitted as transparent text. Use NOTRANSLATE when you want to transmit non-ASCII-coded data, such as object code. NOTRANSLATE requires fixed-length, 80-byte records.
Exchange/RJE Commands SEND Command If you specify NOTRANSPARENT and NOTRANSLATE, the data is transmitted as transparent text and the data is not translated before it is transmitted. NOTRANSLATE always takes precedence over NOTRANSPARENT or TRANSPARENT. Whenever the data is transmitted as transparent text (TRANSPARENT or NOTRANSLATE is specified), the data must be in fixed-length, 80-byte records (except for block mode without blocking). If you omit this parameter, the default value is NOTRANSPARENT.
Exchange/RJE Commands SEND Command Considerations The SEND command transmits records from the specified file to the remote system. Before you can use the SEND command, you must first have established a connection between Exchange/RJE and the data communications line using the CONNECT command. For information on establishing a connection, see the CONNECT command earlier in this section. Block and Record Formats The SEND command reads records from the send file one at a time.
Exchange/RJE Commands SEND Command Table 3-9. 3780-Emulation Mode SEND Command Block Formats Normal-Text Block Format All blocks except last: STX record [ IRS record ]... IRS ETB Last block: STX record [ IRS record ]... IRS ETX Maximum block size: 512 bytes (includes 1 byte each for STX and ETB/ETX) Maximum record size: 144 bytes Records cannot contain any BSC control characters.
Exchange/RJE Commands SEND Command Table 3-10. Block Mode, 2780 Blocking SEND Command Block Formats Normal-Text Block Format All blocks except last: STX record [ ITB record ]... ETB Last block: STX record [ ITB record ]... ETX Maximum block size: 4086 bytes (includes 1 byte each for STX and ETB/ETX) Maximum record size: BLOCKSIZE Records less than 80 bytes in length have an EM character appended to them unless you specify DROPEM in the SEND command. Records cannot contain any BSC control characters.
Exchange/RJE Commands SEND Command Table 3-11. Block Mode, 3780 Blocking SEND Command Block Formats Normal-Text Block Format All blocks except last: STX record [ IRS record ]... IRS ETB Last block: STX record [ IRS record ]... IRS ETX Maximum block size: 4086 bytes (includes 1 byte each for STX and ETB/ETX) Maximum record size: BLOCKSIZE - 1 Records cannot contain any BSC control characters.
Exchange/RJE Commands SEND Command Table 3-12. Block Mode Without Blocking SEND Command Block Formats Normal-Text Block Format All blocks except last: STX record ETB Last block: STX record ETX Maximum block size: 4086 bytes (includes 1 byte each for STX and ETB/ETX) Maximum record size: BLOCKSIZE Block mode without blocking treats each block as a single record. It does not support the use of ITB characters or IRS characters as record separators within a block.
Exchange/RJE Commands SEND Command 2. This example shows the SEND command with the NOTRANSLATE parameter. >SEND dprebcdc, NOTRANSLATE RJSR00 FILE '$DATA3.TEST9135.DPREBCDC' IS BEING SENT TO RJSR00* '$Z086' AT 13:47:35 ON FILE TRANSMISSION HAS BEEN COMPLETED RJSR07 RECORDS RJSR07* TRUNCATED 3. 6/17/91 RJSR14 13, SIZE 80: 80: 80, TIME 0:00:01, RATE 12.5 0 This example shows the SEND command with the TRUNCATE and RECSIZE parameters.
Exchange/RJE Commands SET Command SET Command The SET command specifies values for the configuration parameters. SET parameter [ parameter ]... parameter is one of the following terms: A[CU] [\system.]$acu specifies the name of the automatic calling unit (ACU) and, optionally, the system on which it resides. This parameter specifies the ACU associated with the data communications line specified in the LINE parameter.
Exchange/RJE Commands SET Command BLOCKI[NG] { ON | OFF } BLOCKING ON specifies block mode with 2780 or 3780 blocking. You select the type of blocking, 2780 or 3780, as a parameter in the CONNECT command. BLOCKING ON requires that BLOCKSIZE also be specified. Otherwise, an error occurs when you issue a CONNECT command. If you do not specify BLOCKING, the default is BLOCKING OFF. Specify BLOCKING OFF (or accept the default) and specify BLOCKSIZE for block mode without blocking.
Exchange/RJE Commands SET Command E[BCDICNL] { ON | OFF } specifies whether the Exchange/RJE line server treats the EBCDIC NL character as a record separator or as data. You may also use the RJECIR command to specify this parameter. If you specify EBCDICNL ON, the line server does not recognize the NL character as a record separator; the NL character is passed on as ASCII data (%H85). RECEIVE EBCDICNL OFF overrides this parameter for the duration of a RECEIVE command.
Exchange/RJE Commands SET Command \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/RJE command interpreter is running. The data communications line and the ACU, if any, must reside on the same system. If the data communications line resides on the same system as the line server, you can omit \system.
Exchange/RJE Commands SET Command This parameter cannot be used to change the name of the program file. The line server is always started from a program file called RJESV. If you omit \system, the default system is the system on which the Exchange/RJE command interpreter resides. If you omit $volume, the default volume is the volume on which the command interpreter resides. If you omit subvolume, the default subvolume is the subvolume on which the command interpreter resides.
Exchange/RJE Commands SET Command station is not sending any data) before terminating the read operation. Valid values for this parameter are -1 and from 0 through 32767. Specifying -1 indicates an unlimited number of retries. If you specify a value from 0 through 32767, the specified number of retries are allowed, after which the read operation is terminated.
Exchange/RJE Commands SET Command If you specify TRACE OFF, the Exchange/RJE trace server need not be started before the connection is established. This does not prevent you from using the TRACE command; it merely makes it optional. If you omit this parameter, the default value is TRACE OFF. U[SERLIB] filename specifies the name of the user library file that contains the user-exit procedure, USER^EXIT^MODEM^SUPPORT. The specified user library must reside on the same system as the line server.
Exchange/RJE Commands SET Command All configuration parameters can also be specified in the RJECIR command that starts the Exchange/RJE command interpreter. All configuration parameters except ACU and LINE are reset to their default values by the DISCONNECT command. The following paragraphs discuss the use of the SERVER parameter and the PROGRAM parameter to control whether the next CONNECT command starts a new line server or connects to an existing line server.
Exchange/RJE Commands SET Command Starting a Remote, Named Line Server If you want the next CONNECT command to start a named line server on a system other than the system on which the Exchange/RJE command interpreter resides, specify the system on which you want to start the line server in the PROGRAM parameter. You also need to specify in the PROGRAM parameter the volume and subvolume on that system that contain the RJESV program file (usually $SYSTEM.SYSTEM).
Exchange/RJE Commands SET Command >SET LINE $RJE3 2. This example shows how to specify the data communications line and an associated ACU with the SET command. >SET LINE $RJE3, ACU $ACU3 3. This example shows how to use the SET command to set the configuration parameters so the next CONNECT command starts a named line server on a remote system. >SET PROGRAM \PHAR.$SYSTEM.SYSTEM.RJESV, SERVER \PHAR.$RJE >SET LINE \PHAR.
Exchange/RJE Commands SHOW Command SHOW Command The SHOW command displays the values of the configuration parameters, information about the Exchange/RJE line server, or information about any send or receive operation that may be in progress. SH[OW] [ parameter ] [ O[UT] output-file ] parameter If you omit parameter, the SHOW command displays the current values of the configuration parameters. parameter is one of the following terms: L[INE] displays information about the Exchange/RJE line server.
Exchange/RJE Commands SHOW Command Line Activity Considerations Examples None. The SHOW command displays the values of the configuration parameters, information about the Exchange/RJE line server, or information about any send or receive operation that may be in progress. 1. This example shows the default SHOW command.
Exchange/RJE Commands SHOW Command 3. This example shows the SHOW command with the * parameter. >SHOW * RJCI62 ======================================================================= S E N D / R E C E I V E SERVER $Z503 I N F O R M A T I O N TYPE 2780 DEVICE FILE STATE OPTIONS READER $DATA3.TEST9135.SHORT COMPLETED NOTRUNCATE PRINTER $DATA3.TEST9135.
Exchange/RJE Commands STATUS Command STATUS Command The STATUS command displays statistics about all send and receive operations performed during the current connection. ST[ATUS] [ O[UT] output-file ] O[UT] output-file specifies the name of the file where you want to write the output of the STATUS command. If you omit this parameter, output is written to the file specified in the OUT option of the RJECIR command that started the Exchange/RJE command interpreter.
Exchange/RJE Commands STATUS Command Example This example shows the STATUS command and the display it produces. >STATUS RJCI49 ======================================================================= E X C H A N G E / R J E S T A T I S T I C S R E C E I V E PRINT FILES TRANSMITTED: TRANSMISSION RATE: MAXIMUM RECORD SIZE: TOTAL 0 1 19 0 19 0:00:01 0:00:00 0:00:01 15.0 0.0 15.
Exchange/RJE Commands STATUS Command SEND FILES TRANSMITTED The cumulative number of files transmitted RECORDS TRANSMITTED The cumulative number of records transmitted TIME REQUIRED The time required for the preceding file sent, truncated to the nearest second TRANSMISSION RATE The transmission rate for the previous file sent, in records/second (the calculation is made before TIME REQUIRED is truncated) MAXIMUM RECORD SIZE Based on the last file sent MINIMUM RECORD SIZE Based on the last file se
Exchange/RJE Commands TRACE Command . TRACE Command The TRACE command starts and stops the Exchange/RJE trace server, which logs the activity on the data communications line. T[RACE] { T[O] trace-file [ parameter ]... | S[TOP] } T[O] 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/RJE Commands TRACE Command C[YCLES] 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 cycles times. For example, if you specify one cycle, the trace stops as soon as the trace file fills up. If you specify six cycles, the trace stops after the writing of blocks has cycled through the trace file six times.
Exchange/RJE Commands TRACE Command (This page left intentionally blank) 3–78 104698 Tandem Computers Incorporated
4 Using the Exchange/RJE Programmatic Interface This section provides instruction on how to use the Exchange/RJE programmatic interface to send files to and receive files from a remote system. This section covers the following information: System procedure call summary Programming considerations Step-by-step instructions System Procedure Call The programmatic interface lets your program control and communicate with the Summary Exchange/RJE line server through standard system procedure calls.
Using the Exchange/RJE Programmatic Interface Programming Considerations Programming Considerations This subsection discusses those programming considerations that apply particularly to writing programs that use the Exchange/RJE programmatic interface. For a general discussion of programming on Tandem NonStop systems, see the Guardian Programmer’s Guide. Using the User Library The user library contains the user-exit procedure USER^EXIT^MODEM^SUPPORT. The default procedure shipped in RJELIB does nothing.
Using the Exchange/RJE Programmatic Interface Programming Considerations 3. After the message initiating the I/O operation has been sent, the operating system resumes the execution of your program. 4. The process performs the I/O operation. Concurrently, your program continues executing. 5. When the process has finished the I/O operation, it passes a message to the operating system indicating the completion of the I/O operation. This step may happen after Step 6 below. 6.
Using the Exchange/RJE Programmatic Interface Programming Considerations Disadvantage of Wait I/O. The disadvantage of wait I/O operations is that your program cannot do anything until the I/O operation completes. This is a disadvantage only if there is some useful work to be done while the I/O operation is in progress.
Using the Exchange/RJE Programmatic Interface Programming Considerations The following fragment of TAL code illustrates the typical method of checking for errors and the subsequent call to FILEINFO in the event of an error. CALL READ (fnum, buffer, 80, count_read); IF <> THEN BEGIN !error or warning occurred CALL FILEINFO (fnum, error); !identify the error ... !perform recovery !if possible !else exit END; ...
Using the Exchange/RJE Programmatic Interface Programming Considerations Table 4-2. Exchange/RJE Line Server Errors (Page 1 of 2) Standard Error Messages 0 1 2 12 16 21 28 40 60 66 70 140 156 157 160 161 162 163 164 165 166 167 168 169 171 172 173 4–6 No error occurred; the operation completed successfully. An EOF was read, or an ETX was received from the remote system. You have attempted an operation that is not allowed on the type of file you specified. The file you specified is in use.
Using the Exchange/RJE Programmatic Interface Programming Considerations Table 4-2. Exchange/RJE Line Server Errors (Page 2 of 2) Standard Error Messages (continued) 174 200 201 210 211 219 A WACK was received. The remote system is temporarily unable to receive. The device is owned by the other port. The system is unable to communicate over this path. Ownership of the device changed during the operation. The CPU failed during the operation. An illegal reconnect occurred.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions Block Mode With 2780/3780 Blocking Block mode with 2780 blocking and block mode with 3780 blocking provide all features of the standard 2780-emulation and 3780-emulation modes, respectively.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions 8. Perform the operation. 9. Disconnect from the data communications line. 10. Close the line server. Each step is explained in detail below. Step 1: Start the Line Server Before your program can use the programmatic interface, the line server must be started. There are three ways to start the line server: Use the CONNECT command from the command interpreter. Use the RJESV command from the operating system command interpreter.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions The BLOCKSIZE parameter, together with the default value BLOCKING OFF, specifies that the line server is to operate in block mode without blocking; it also specifies the maximum block size, which is 2048 bytes in this example. Using the NEWPROCESS Procedure Your program can start the Exchange/RJE line server by calling the NEWPROCESS procedure.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions The line server is always opened for exclusive access regardless of the type of access you specify in the call to OPEN. If your program attempts to open an existing line server and that line server is being used by another program, the call to OPEN will fail and return error number 12 (file in use).
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions Startup Message Contents The following list names each structure that makes up the startup message and describes the contents of each structure. The structures are identified by the names given in the preceding sample TAL code. MSG^CODE Must be assigned the value -1 to identify the message as a startup message. DEFAULT This field is used by the line server.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions m = (n/2) -1, where n is the value specified for the STRING BYTES count in the startup message. The following example shows the minimum set of parameters required to start a block-mode (without blocking) line server with a maximum block size of 4000 bytes. ! fill PARAMS with zeroes ! STARTMSG.PARAMS ’:=’ 0 & STARTMSG.PARAMS FOR m; ! specify the line and block-mode operations ! ! max block size = 4000 bytes ! STARTMSG.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions Step 6: Establish a Connection Your program must establish a connection between the line server and the data communications line before your program can use the line server to communicate over the line. To do this, call the SETMODE procedure with the function parameter equal to 41.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions 3. Call WRITE (or WRITEREAD) and pass the record to the line server for transmission to the remote system. 4. Repeat steps 2 and 3 until the end of the file is reached. 5. Call the CONTROL procedure with the operation parameter equal to 2. This sends an ETX (end of text or file) to the remote system.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions 1. Call READ and read the first record received from the remote system. This is a wait I/O operation. 2. Call WRITE and write the record that was received from the remote system by the line server to the file. This is a nowait I/O operation. 3. Call READ and read the next record received from the remote system. This is a wait I/O operation.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions Sending and Receiving in the Same Program If your program both sends and receives, the following rules govern the actions required to switch operations. Switching from Sending to Receiving. To switch from sending to receiving, your program must perform the following steps. 1.
Using the Exchange/RJE Programmatic Interface Step-by-Step Instructions Disconnecting After Receiving If your program has been receiving data from the remote system, the remote system initiates the disconnect by sending an EOT (end of transmission) possibly followed by a DLE EOT (disconnect message). In either case (EOT or EOT followed by DLE EOT), your program should simply close the line server (see “Step 8: Close the Line Server”).
5 Exchange/RJE System Procedure Calls This section describes the RJESV command, which starts the Exchange/RJE line server, and the system procedure calls that an application program can use to communicate with the 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/RJE are described here. These descriptions focus on how the procedures are used with Exchange/RJE.
Exchange/RJE System Procedure Calls RJESV Command RJESV Command The RJESV command starts the Exchange/RJE line server. RJESV / option [ , option ]... / parameter [ parameter ]... option is an option of the TACL RUN command. Four options are described below, two of which are required. For a complete list of all options, see the RUN command in the Tandem Advanced Command Language (TACL) Reference Manual. CPU primary specifies the CPU in which the Exchange/RJE line server is to run.
Exchange/RJE System Procedure Calls RJESV Command If you omit this option, Exchange/RJE uses the last user library specified. If the LIB option has never been used, Exchange/RJE uses the default user library RJELIB. To return to the default user library RJELIB, you must explicitly specify that file name. Once the RJESV file is open, subsequent calls to start a new line server must specify the same user library as specified by the first opener.
Exchange/RJE System Procedure Calls RJESV Command If the ACU resides on the same system as the line server, you can omit \system. However, if the line server and the ACU do not reside on the same system as the command interpreter, the location of the ACU is more apparent from the RJESV command if you specify the system name even though it is not required. BA[CKUPCPU] backup specifies the CPU in which the line server backup process is to run.
Exchange/RJE System Procedure Calls RJESV Command If you omit this parameter: 2780-emulation mode sends and receives blocks up to 400 bytes long. 3780-emulation mode sends blocks up to 512 bytes long and receives blocks up to 520 bytes long. Operation in block mode is not possible. E[BCDICNL] {ON | OFF} specifies whether the Exchange/RJE line server treats the EBCDIC NL character as a record separator or as data.
Exchange/RJE System Procedure Calls RJESV Command \system must be the name of an existing Tandem system that is part of the same EXPAND network as the system on which the line server is running. The data communications line and the ACU, if any, must reside on the same system. If the data communications line resides on the same system as the line server, you can omit \system.
Exchange/RJE 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 the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server.
Exchange/RJE System Procedure Calls AWAITIO 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. time-limit INT(32):ref:1 specifies whether the call to AWAITIO should check for completion of the I/O operation and return immediately, or wait for completion of the I/O operation.
Exchange/RJE 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 the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server. Line Activity Considerations None. The CANCEL procedure cancels the oldest outstanding I/O operation on the specified file.
Exchange/RJE 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 the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server.
Exchange/RJE System Procedure Calls CLOSE Procedure CLOSE Procedure The CLOSE procedure terminates access to the Exchange/RJE line server. CLOSE ( filenum ); filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server. Line Activity Considerations None. The CLOSE procedure terminates access to the Exchange/RJE line server. Your program should call CLOSE after it has finished using the line server.
Exchange/RJE System Procedure Calls CONTROL Procedure CONTROL Procedure The CONTROL procedure sends an end-of-text (ETX), end-of-transmission (EOT), or disconnect (DLE EOT) message to the remote system. filenum , operation , [ param ] , [ tag ] ); CALL CONTROL ( filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server. operation INT:value specifies the operation to perform.
Exchange/RJE System Procedure Calls CONTROL 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. Line Activity Considerations The line activity depends on the value of operation.
Exchange/RJE System Procedure Calls CONTROL Procedure End of Transmission The end-of-transmission operation (operation = 13) has two functions. Normally, it tells the remote system that your program has finished transmitting. The operation also gives up control of the line, returning both systems to the control state. In the control state, either system can bid for the line (that is, bid for the right to transmit to the other system).
Exchange/RJE System Procedure Calls DEVICEINFO Procedure DEVICEINFO The DEVICEINFO procedure returns the type and subtype of the specified data Procedure communications line and the record size specified for that line during system generation. linename , linetype , recsize ); CALL DEVICEINFO ( linename INT:ref:12 is an array containing the name of the data communications line on which you want information.
Exchange/RJE System Procedure Calls DEVICEINFO Procedure Considerations The DEVICEINFO procedure returns the type and subtype of the specified data communications line and the record size specified for that line during system generation. Table 5-1 below shows the types and subtypes that are valid for lines used with Exchange/RJE. Table 5-1. Exchange/RJE Line Types and Subtypes 5–16 linetype.<4:9> linetype.
Exchange/RJE System Procedure Calls FILEINFO Procedure FILEINFO Procedure The FILEINFO procedure returns the number of the last error reported by the Exchange/RJE line server. filenum , error ); CALL FILEINFO ( filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server.
Exchange/RJE System Procedure Calls NEWPROCESS Procedure NEWPROCESS The NEWPROCESS procedure starts the Exchange/RJE line server. Procedure CALL NEWPROCESS ( , , , , filename [ priority ] [ server-id ] [ error ] server-name ); filename INT:ref:12 or INT:ref:36 is the internal name of the Exchange/RJE line server program file. The name can be in the form of an internal file name or an internal network file name. In either case, filename [8:11] must be RJESV, left-justified, and blank-filled on the right.
Exchange/RJE System Procedure Calls NEWPROCESS Procedure error INT:ref:1 returns a number indicating whether or not an error occurred. If error.<0:7> equals 0 (zero), no error occurred and the line server was started. Otherwise, an error occurred. Depending on the error, the line server may not have been started. For a list of the numbers and the corresponding errors, see the Guardian Procedure Calls Reference Manual.
Exchange/RJE System Procedure Calls OPEN Procedure OPEN Procedure The OPEN procedure establishes communication between your program and the Exchange/RJE line server. filename , filenum , [ flags ] ); CALL OPEN ( filename INT:ref:12 is the name (in internal name format) of the Exchange/RJE line server. The line server must already exist before you can establish communication with it.
Exchange/RJE System Procedure Calls OPEN Procedure Assuming your program will both send and receive data, specify 0 for read/write access. .<6:7> Must be 0. .<8> Specifies whether the open message is sent to the Exchange/RJE 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. .
Exchange/RJE System Procedure Calls OPEN Procedure Considerations The OPEN procedure establishes communication between your program and the Exchange/RJE line server. The above description of the OPEN procedure describes the minimum requirements for establishing communication with the Exchange/RJE line server. This description omits a number of parameters that may be useful in your particular situation.
Exchange/RJE System Procedure Calls READ Procedure READ Procedure The READ procedure reads a record received by the line server from the remote system. CALL READ ( , , , , filenum buffer read-count [ count-read ] [ tag ] ); filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server. buffer INT:ref:* is an array in which the record read from the line server is returned.
Exchange/RJE System Procedure Calls READ Procedure count-read INT:ref:1 returns the number of bytes in the record read from the line server. This parameter is used only for wait I/O. For nowait I/O, you can omit this parameter; the number of bytes read is returned in the count-transferred parameter of the AWAITIO procedure that completes the read operation.
Exchange/RJE System Procedure Calls READ Procedure Receiving ETX, EOT, and DLE EOT The remote system ends the transmission of a file by sending a block that ends in ETX (or DLE ETX for transparent text) instead of ETB (or DLE ETB for transparent text). When your program has read the last record in the last block, the next call to READ returns with error number 1, which indicates an ETX (or DLE ETX) has been received (the end of the file has been reached).
Exchange/RJE System Procedure Calls READ Procedure Receiving Transparent Data When you are receiving transparent data, you can receive several error numbers in response to your READ call. These errors are: 301 If the call to READ returns error number 301, it means that the line server is returning a control message rather than data. When your application receives error 301, it should check the value in the reply buffer, which is 1 word long.
Exchange/RJE System Procedure Calls SETMODE Procedure SETMODE Procedure The SETMODE procedure sets parameters that control the operation of the Exchange/RJE line server. filenum , function , [ param1 ] , [ param2 ] ); CALL SETMODE ( filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server. function INT:value specifies the operation to be performed.
Exchange/RJE System Procedure Calls SETMODE Procedure Line Activity Considerations None. The SETMODE procedure sets parameters that control the operation of the Exchange/RJE line server. The SETMODE procedure can also be used to determine the current state of the line server. The particular 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.
Exchange/RJE System Procedure Calls SETMODE Procedure This field can have the following values: 0 The status specified during system generation 1 SECONDARY status 2 PRIMARY status 3 PRIMARY status (specifies both SECONDARY and PRIMARY status, but PRIMARY takes precedence) The PRIMARY or SECONDARY status of a system controls the behavior of that system in the event that both the local and the remote system bid for the line at the same time.
Exchange/RJE System Procedure Calls SETMODE Procedure If a user-library file name is specified, Exchange/RJE passes the phone number directly to the user-exit procedure; it does not parse the number to remove parentheses, hyphens, blanks, or slashes. If you are using an ACU, Exchange/RJE removes parentheses, hyphens, blanks, and slashes before passing the telephone number to Envoy, which in turn passes the telephone number to the automatic calling unit for dialing.
Exchange/RJE System Procedure Calls SETMODE Procedure If you specify NOTRANSPARENT and NOTRANSLATE, the data is transmitted as transparent text and the data is not translated before it is transmitted. NOTRANSLATE always takes precedence over NOTRANSPARENT or TRANSPARENT.
Exchange/RJE System Procedure Calls SETMODE Procedure 1 COMPRESS If you specify COMPRESS, groups of 2 to 63 consecutive blanks are replaced by an IGS (EBCDIC) or GS (ASCII) character and a space-count character that specifies the number of blanks that were removed by the compression. The remote system (provided it supports compression) replaces the IGS or GS character and the space-count character with the indicated number of blanks.
Exchange/RJE System Procedure Calls SETMODE Procedure param2.<15> suppresses the appending of an end-of-media (EM) character to records less than 80 bytes long in 2780-emulation mode or block mode with 2780 blocking. This parameter does not apply to 3780-emulation mode, block mode with 3780 blocking, or block mode without blocking; no end-of-media character is used in these cases.
Exchange/RJE System Procedure Calls SETMODE Procedure param1.<14> controls the inclusion of BSC control characters in the records returned to your program by the line server, as follows: 0 RAWDATA OFF If you specify RAWDATA OFF, the line server removes all BSC control characters from each record before returning the record to your program. Your program receives only the data.
Exchange/RJE System Procedure Calls SETMODE Procedure 1 = NOTRANSLATE If you specify NOTRANSLATE and the remote system sends the data as transparent text (each text block begins with DLE STX), no translation takes place and the data is returned to your program exactly as received.
Exchange/RJE System Procedure Calls SETMODE Procedure SETMODE Function 45 This function returns the current state of the line server in a return code. To get the return code, you must call FILEINFO after calling SETMODE. The number returned by FILEINFO in the error parameter indicates the state of the line server. The following codes can be returned: 0 DISCONNECTED.
Exchange/RJE System Procedure Calls WRITE Procedure WRITE Procedure The WRITE procedure writes a record from your program to the Exchange/RJE line server for transmission to the remote system. CALL WRITE ( , , , , filenum buffer write-count [ count-written ] [ tag ] ); filenum INT:value is the file number of the Exchange/RJE line server. This number is returned by the call to OPEN that established communication with the line server.
Exchange/RJE System Procedure Calls WRITE 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/RJE System Procedure Calls WRITE Procedure All blocks transmitted with an error (the remote system responded with an NAK) are automatically transmitted again. The number of retries allowed before the write operation is terminated is specified for the data communications line during system generation. Considerations The WRITE procedure writes a record from your program to the Exchange/RJE line server for transmission to the remote system. You can also use the WRITEREAD procedure to do this.
Exchange/RJE System Procedure Calls WRITEREAD Procedure WRITEREAD Procedure The WRITEREAD procedure either writes a record from your program to the Exchange/RJE line server for transmission to the remote system or reads a record received by the line server from the remote system. CALL WRITEREAD ( , , , , , filenum buffer write-count read-count [ count-read ] [ tag ] ); filenum INT:value is the file number of the Exchange/RJE line server.
Exchange/RJE System Procedure Calls WRITEREAD Procedure The following are the maximum record sizes that the line server can receive: 2780/3780-emulation mode: 1 through 146 bytes Block mode with 2780 blocking: 1 through BLOCKSIZE Block mode with 3780 blocking: 1 through BLOCKSIZE - 1 Block mode without blocking: 1 through BLOCKSIZE (BLOCKSIZE is specified in the RJESV command.) If the record is larger than read-count bytes, the record is truncated to readcount bytes.
Exchange/RJE System Procedure Calls WRITEREAD Procedure Read Operations For read operations, WRITEREAD works exactly the same as READ. See the READ procedure earlier in this section for the line activity associated with a read operation. Considerations The WRITEREAD procedure writes a record from your program to the Exchange/RJE line server for transmission to the remote system or reads a record received by the line server from the remote system.
6 Installation and Configuration This section describes the files that make up the Exchange/RJE product and provides information on the system generation definitions required for data communications lines to be used with Exchange/RJE.
Installation and Configuration Configuring Data Communications Lines Configuring Data This section outlines the configuration requirements for Envoy and CP6100 data Communications Lines communications lines. Envoy Lines For information about the hardware and system generation definitions required when using Exchange/RJE with Envoy data communications lines, see the System Generation Manual. When configuring an Envoy line for Exchange/RJE, you need to specify the following values.
Installation and Configuration Configuring Data Communications Lines PPNSW or PPSW specify PPNSW (point-to-point nonswitched line) for a leased line. Specify PPSW (point-to-point switched line) for a switched—dial in or out—line. Also note that the value specified for RSIZE is informational only—it does not affect the block size that can be transmitted.
Installation and Configuration Configuring Data Communications Lines PUP Commands When a load system procedure finishes, the Exchange/RJE lines should be up (in the online condition). If the lines are not up, use the PUP command to check the status of the lines and, if necessary, place them online.
Installation and Configuration Configuring Data Communications Lines BSCCONNECTTO n specifies the connect timeout. This is the amount of time, in 10-millisecond units, that CP6100 waits for Data-Set-Ready (CC) to come on after Data-Terminal-Ready (CD) is asserted. Unless the modem is always on, the value should be long enough to allow an operator to establish the connection.
Installation and Configuration CMI/CMP Commands CMI/CMP Commands If the input to SYSGEN specified STARTBOOT off and STARTDOWN on, you must start the data communications lines through CMI/CMP commands.
Appendix A Exchange/RJE Messages This appendix lists the messages displayed by Exchange/RJE. 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/RJE that you cannot solve by yourself.
Exchange/RJE Messages Trace Server Messages Trace Server This subsection describes the message issued by the Exchange/RJE 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/RJE Messages Trace Server Messages RJCI03E ILLEGAL command-type OPTION Problem. You have specified a parameter that is invalid in the given command. Solution. Refer to Section 3 for a list of the parameters that are valid in each command. Enter the command again using only valid parameters. RJCI04E 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/RJE Messages Trace Server Messages RJCI08W 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. RJCI09E COMMAND ERROR Problem. The command interpreter does not recognize what you entered as a command. Solution. Refer to Section 3 for a list of valid commands. Enter a valid command. RJCI10E ILLEGAL FILE NAME Problem.
Exchange/RJE Messages Trace Server Messages RJCI12E $server TERMINATED WHILE ATTEMPTING TO DO THE CONNECT Problem. The Exchange/RJE line server stopped during the execution of the CONNECT command. Generally, this is due to the incorrect values for the configuration parameters. Solution. Use the SHOW command to verify the values of the configuration parameters. Correct the values, and enter the CONNECT command again. RJCI13E $server IS THE INCORRECT LINE SERVER TYPE Problem.
Exchange/RJE Messages Trace Server Messages RJCI16E CONNECTION TO $server STILL EXISTS RJCI16* ISSUE A 'DISCONNECT' TO BREAK CONNECTION Problem. You have entered a CONNECT command while the command interpreter is still connected to a line server. Solution. Use the existing line server and connection (if suitable), or enter a DISCONNECT command and then enter the CONNECT command again. RJCI17E COULD NOT CREATE A UNIQUE SERVER NAME FOR SYSTEM system-name, system-number Problem.
Exchange/RJE Messages Trace Server Messages RJCI20E param1 AND param2 MUST BE ON THE SAME SYSTEM RJCI20* param1 IS ON system-name, system-number RJCI20* param2 IS ON system-name, system-number Problem. param1 and param2 are LINE and ACU, PROGRAM and SERVER, or PROGRAM and USERLIB. Each of these parameter pairs must be specified as being on the same system. Solution. If a system name is specified for LINE and ACU, PROGRAM and SERVER, or PROGRAM and USERLIB, specify the same system for both parameters.
Exchange/RJE Messages Trace Server Messages RJCI24E PROCESS ERROR message Problem. The call to the NEWPROCESS system procedure to start the line server, the send/receive server, or the trace server failed. The reason for the failure is given in the message. If message is LIBRARY CONFLICT, the RJESV object file is already in use and you have attempted to specify a user library for a new line server that is different from the library specified by the first opener of RJESV. Solution.
Exchange/RJE Messages Trace Server Messages RJCI28 COMMUNICATION LINK HAS BEEN ESTABLISHED WITH LINE line-name Comment. This message is issued when a new line server is started, and it indicates that the connection has been established between the command interpreter, the send/receive server, the line server, and the data communications line. This message does not necessarily mean that the data communications line is working and Exchange/RJE can communicate with the remote system.
Exchange/RJE Messages Trace Server Messages RJCI34E 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. RJCI35 TRACE PROCESS $server HAS BEEN STOPPED Comment. The trace server has been stopped. RJCI36W NO TRACE PROCESS ACTIVE ON $server Problem. You entered a command (such as TRACE STOP) that requires an existing trace server, and no trace server was running. Solution.
Exchange/RJE Messages Trace Server Messages RJCI39 HELP INFORMATION - version-string Comment. This message is a heading for the output of the HELP command. RJCI41E INVALID DUMP RANGE SPECIFIED 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 command again with beginning and ending sequence numbers that are in the correct range.
Exchange/RJE Messages Trace Server Messages RJCI44E PROGRAM FILE MUST BE RJESV Problem. The SET PROGRAM command must include RJESV, optionally preceded by \system.$volume.subvolume. RJESV is the Exchange/RJE line server program file. Solution. Re-issue the command, including RJESV. RJCI45E file-name EXISTS BUT IS NOT A VALID line/acu/program Problem. You have entered a SET command with the ACU, LINE, or PROGRAM parameters.
Exchange/RJE Messages Trace Server Messages RJCI48E 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. RJCI49 message Comment. No action is required.
Exchange/RJE Messages Trace Server Messages RJCI52E RECORD SIZE MUST BE GREATER THAN ZERO (0) Problem. You have entered a record size less than one (1) in a SEND or RECEIVE command. Solution. Enter the command again, and specify a record size of at least 1. RJCI53E 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. RJCI54E TRACE FILE filename IS EMPTY Problem.
Exchange/RJE Messages Trace Server Messages RJCI56 trace-header Comment. This message is the heading for the output produced by the dump command. RJCI57W send/receive SERVER name HAS stopped/aborted Comment. The specified server has been stopped. No action is required. RJCI59E NUMERIC VALUE IS EITHER ERRONEOUS OR NOT WITHIN TRACE RANGE Problem. You have entered a DUMP command in which the beginning or ending sequence number is out of range.
Exchange/RJE Messages Trace Server Messages RJCI62 ============= ... Comment. The heading for the output of the SHOW command. RJCI65 DIALING PHONE NUMBER number Comment. The specified telephone number is being dialed. No action is required. RJCI66 DATASET IS NOT READY - name Comment. No action is required. RJCI67E RECSIZE MUST BE 80 WHEN USING send/receive OPTION [ NOTRANSLATE | TRANSPARENT ] Problem.
Exchange/RJE Messages Trace Server Messages RJC169E type FILE NAME WAS NOT SUPPLIED AND RJCI69* NO PREVIOUS type FILE NAME EXISTS Problem. You have not specified a file when one is required. Solution. Enter the command (SEND or RECEIVE) again, and specify a file (the send file or the print file). RJCI70E THERE IS A SEND OR RECEIVE ALREADY ACTIVE Problem. You have entered a command that cannot be executed while a send or receive operation is in progress. Solution.
Exchange/RJE Messages Trace Server Messages RJCI75E DIAL PARAMETER MUST NOT BE SPECIFIED FOR NONSWITCHED LINE Problem. You have entered a DIAL parameter in the CONNECT command and the line is nonswitched. The operation is aborted. Solution. Remove the DIAL parameter from the CONNECT command specification when you are connecting to a nonswitched line. RJCI76 NO DATA BLOCK FOUND FOR THIS REQUEST Comment. A trace record was specified that does not exist within the specified trace file.
Exchange/RJE Messages Send/Receive Server Messages RJCI81E RETRIES COUNT MUST BE -1, ZERO, OR POSITIVE INTEGER Problem. You have entered an invalid value for the RETRIESEOT or RETRIESIDLE parameter. Solution. Enter the command again, specifying a valid value. RJCI82E A REMOTE SYSTEM NAME MUST BE SPECIFIED IN BOTH PROGRAM AND USERLIB Problem. You have entered both the PROGRAM and USERLIB parameters with a remote system name specified in only one of the two parameters.
Exchange/RJE Messages Send/Receive Server Messages RJSR01E CAN'T OPEN FILE - name RJSR01* FILE MANAGEMENT SYSTEM ERROR - number Problem. The send/receive server was unable to open the specified file due to the filesystem error indicated by number. Solution. Correct the cause of the error, and then try the operation again. RJSR02E INSUFFICIENT STORAGE - SERVER ABORTED Problem. There is not enough memory to run the send/receive server. Solution. Contact your local Tandem support office.
Exchange/RJE Messages Send/Receive Server Messages RJSR06W TRUNCATION ERROR IN FILE filename RJSR06* ONE OR MORE RECORDS HAVE BEEN TRUNCATED TO num BYTES Problem. One or more records that were received from the remote system are larger than the record size of the file to which they are being written. The records that are too large are truncated. Solution.
Exchange/RJE Messages Send/Receive Server Messages RJSR09W FILE RECORD SIZE (size1), GREATER THAN LINE RECORD SIZE (size2) Comment: The record size of the file to be sent is larger than the record size specified for the send operation. (If no record size was specified, the default record size is 80 bytes.) If the actual records are larger than the record size specified for the send operation, the records are truncated before they are sent to the remote system.
Exchange/RJE Messages Send/Receive Server Messages RJSR13E REMOTE STATION HAS FAILED TO ACKNOWLEDGE RECEIPT OF A TRANSMISSION RJSR13* FILE MANAGEMENT SYSTEM ERROR - number Problem. The remote system has failed to acknowledge a transmission from Exchange/RJE. This can happen because the data communications line failed (or never worked) or the remote system failed. Solution. Correct the indicated error, and try the operation again. RJSR14 FILE TRANSMISSION HAS BEEN completed/aborted /interrupted Comment.
Exchange/RJE Messages Send/Receive Server Messages RJSR17E TIMED OUT WAITING FOR TRANSMISSION FROM HOST RJSR17* FILE MANAGEMENT SYSTEM ERROR - number Problem. Exchange/RJE was expecting the remote system to send data, and the remote system did not send any data to Exchange/RJE within the allowed time. The operation has been aborted. Solution. Check the connection and the remote system for problems. Correct any problems that are found, and try the operation again.
Exchange/RJE Messages Send/Receive Server Messages RJSR20E RECEIVE OPERATION TERMINATED AFTER SPECIFIED NUMBER OF RETRIES RJSR20* RETRIESEOT COUNT (number) REACHED. Problem. After receiving an EOT without receiving any text, Exchange/RJE has retried the read operation the number of times specified by the RETRIESEOT parameter. The operation is aborted. Solution. The action to be taken is application dependent.
Exchange/RJE Messages Line Server Messages Line Server Messages This subsection lists the messages issued by the Exchange/RJE line server. 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. Before calling the office, please gather the information outlined in the section “Before Contacting Tandem,” later in this appendix.
Exchange/RJE Messages Line Server Messages RJSV05F INVALID FILE/DEVICE - filename Problem. You specified an invalid or misspelled file name. Solution. Enter the command again, and specify the correct file name. RJSV06E I/O ERROR ON FILE filename RJSV06* FILE MANAGEMENT SYSTEM ERROR - number Problem. A file-system error occurred during an I/O operation on the specified file. The error that occurred is indicated by number. Solution. Correct the indicated error, and try the operation again.
Exchange/RJE Messages Line Server Messages RJSV10F UNABLE TO READ THE INITIAL OPEN MESSAGE Problem. A problem has occurred with an application's handling of the startup protocol. Solution. Correct the cause of the error in the application. Repeat Exchange/RJE operations as necessary. RJSV11F UNABLE TO READ THE STARTUP MESSAGE Problem. A problem has occurred with an application's handling of the startup protocol. Solution. Correct the cause of the error in the application.
Exchange/RJE Messages Line Server Messages RJSV14F REQUEST TO RECEIVE CANCEL MESSAGES FAILED Problem. An internal error has occurred. Solution. Contact your local Tandem support office. RJSV15F NO USER LIBRARY FILE NAME SPECIFIED Problem. You have not specified a user-library file name (or the parameter contains all blanks) in either the LIB option in the RJESV command or in the 36-word file name parameter in the NEWPROCESS call. Solution.
Exchange/RJE Messages Line Server Messages RJSV18W ILLEGAL PARAMETER NAME keyword, PROCEEDING Problem. You have entered a command that included an invalid or misspelled parameter. The Exchange/RJE line server process is continuing. Solution. Refer to Section 3 for information about the parameters for each command. Stop the line server, then enter the command again and specify the correct parameter. RJSV97F FATAL ERROR OCCURRED - LINE SERVER STOPPED Problem.
Exchange/RJE 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/RJE Messages Before Contacting Tandem Step 3. Collect Additional Information as Necessary In general, you need to be prepared to report what Exchange/RJE was attempting to do at the time of the failure. Some useful information includes: The commands being executed by Exchange/RJE A copy of the command file, if you are using one 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.
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/RJE, 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/RJE uses to Translation Table translate from ASCII to EBCDIC and back when sending and receiving transparent data. 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.
Appendix C BSC Line Control This appendix briefly reviews the BSC control characters and their use in the linecontrol protocol. BSC Line-Control The following paragraphs list the BSC line-control characters, briefly describe the Characters function of each, and show the corresponding codes. Each character is described in terms of the station that is receiving the character.
BSC Line Control The ACK 1 Character An ACK 0 is transmitted as shown: The ACK 1 Character ASCII line code EBCDIC line code pad SYN SYN DLE 0 pad pad SYN SYN DLE %H 70 pad The ACK 1 (affirmative acknowledgment 1) character is not used in the control state. In the message state, ACK 1 is the positive response to receipt of an odd-numbered block. It means that the last block was received and validated (the BCC calculated at the receiving station agreed with the BCC transmitted with the block).
BSC Line Control The WACK Character The NAK Character The NAK (negative acknowledgment) character is a negative response. In the control state, a NAK character in response to a bid for the line means that permission to transmit is not granted. In the message state, a NAK in response to a block means the last block was received with an error and should be transmitted again. The NAK character is also used in several other line-control operations.
BSC Line Control The ETB Character The WACK character is transmitted as shown: The ETB Character ASCII line code EBCDIC line code pad SYN SYN DLE ; pad pad SYN SYN DLE , pad The ETB (end of transmission block) character is not used in the control state. In the message state, the ETB character terminates a block and is immediately followed by a block-check character (BCC). The ETB character always causes a line turnaround (the station receiving the ETB transmits next).
BSC Line Control The Pad Character The RVI Character In both the control state and the message state, the RVI (reverse interrupt) character is a positive acknowledgment that requests the station receiving the RVI to stop transmitting and let the station sending the RVI transmit. The RVI character always causes a line turnaround (the station receiving the RVI transmits next).
BSC Line Control Normal Message Transmission BSC Line-Control The following examples illustrate typical BSC line-control sequences. Sequence Examples Normal Message Transmission This figure shows the BSC line-control sequence during transmission of a normal message.
BSC Line Control Contention for the Line Contention for the Line This figure shows the BSC line-control sequence during a transmission where there is contention for the line.
BSC Line Control Unanswered Line Bid Unanswered Line Bid This figure shows the BSC line-control sequence where a bid for the line is not answered.
BSC Line Control Retransmission Rejected (Terminal to Terminal) Retransmission Rejected (Terminal-to-Terminal) This figure shows the BSC line-control sequence between two terminals during a transmission where the retransmission is rejected.
BSC Line Control Retransmission Rejected (Terminal to Processor) Retransmission Rejected (Terminal-to-Processor) This figure shows the BSC line-control sequence between a terminal and a processor during a transmission where the retransmission is rejected by the processor.
BSC Line Control Retransmission Rejected (Processor to Terminal) Retransmission Rejected (Processor-to-Terminal) This figure shows the BSC line-control sequence between a terminal and a processor during a transmission where the retransmission is rejected by the terminal.
BSC Line Control Transmission Delay (Receiver-Initiated) Transmission Delay (Receiver-Initiated) This figure shows the BSC line-control sequence between two stations during a transmission where the receiving station initiates a transmission delay.
BSC Line Control Transmission Delay (Transmitter-Initiated) Transmission Delay (Transmitter-Initiated) This figure shows the BSC line-control sequence between two stations during a transmission where the transmitting station initiates a transmission delay.
BSC Line Control Transmission Error, Block Ignored by Receiving Station Transmission Error, Block Ignored by Receiving Station This figure shows the BSC line-control sequence between two stations during a transmission where there is an error because the transmitted block is ignored by the receiving station. The ignored block causes the transmission to time out. The transmitting station bids again for the line; the second time, the transmission is successful.
BSC Line Control Mismatched Acknowledgment Mismatched Acknowledgment This figure shows the BSC line-control sequence between two stations during a transmission where the receiving station responds with the wrong acknowledgment.
BSC Line Control Data Link Aborted (No Response From Receiver) Data Link Aborted (No Response From Receiver) This figure shows the BSC line-control sequence between two stations during a transmission where the receiving station stops unexpectedly. Eventually, the data link is aborted.
BSC Line Control Failure at Transmitting Station Data Link Stalemate (No Continuation by Transmitter) This figure shows the BSC line-control sequence between two stations during a transmission where the transmitting station unexpectedly does not continue the transmission. If Auto Answer is installed on the receiving station, it will disconnect the line after 20 seconds.
BSC Line Control Failure at Receiving Station Failure at Receiving Station This figure shows the BSC line-control sequence between two stations during a transmission where the receiving station discovers an error and aborts the transmission.
Appendix D Example Programs This appendix presents two example programs: one showing the programmatic interface, the other an example user-exit procedure. Send/Receive Program This example program sends and receives a job using the programmatic interface. It Example assumes that Exchange/RJE is communicating over a nonswitched (leased) data communications line with an IBM host system that is running OS/MVS and JES2. Page 1 [1] $RJE.EXCHAPPL.
Example Programs Send/Receive Program Example Page 2 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 GLOBAL DECLARATIONS 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.
Example Programs Send/Receive Program Example Page 3 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 GLOBAL DECLARATIONS 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. 124. 125. 130.
Example Programs Send/Receive Program Example Page 4 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 PROC START^IT 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.
Example Programs Send/Receive Program Example Page 6 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 CREATE^LINE^SERVER 190. 191. 192. 193. 194. 195. 196. 197. 198. 199. 200. 201. 202. 203. 204. 205. 206. 207. 208. 209. 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.
Example Programs Send/Receive Program Example Page 7 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 CREATE^LINE^SERVER 247. 248. 249. 250. 251. 252. 253. 254. 255. 256. 257. 258. 259. 260. 261. 262. 263. 264. 265. 266. 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.
Example Programs Send/Receive Program Example Page 8 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 CREATE^LINE^SERVER 304. 305. 306. 307. 308. 309. 310. 311. 312. 313. 314. 315. 316. 317. 318. 319. 320. 321. 322. 323. 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.
Example Programs Send/Receive Program Example Page 9 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 CREATE^LINE^SERVER 360. 361. 362. 363. 364. 365. 366. 367. 368. 369. 370. 371. 372. 373. 374. 375. 376. 377. 378. 379. 380. 381. 382. 383. 384. 385. 386. 387. 388. 389. 390.
Example Programs Send/Receive Program Example Page 10 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 SEND TEST 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. 419. 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.
Example Programs Send/Receive Program Example Page 11 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 SEND TEST 449. 450. 451. 452. 453. 454. 455. 456. 457. 458. 459. 460. 461. 462. 463. 464. 465. 466. 467. 468. 469. 470. 471. 472. 473. 474. 475. 476. 477. 478. 479. 480. 481. 482. 483. 484. 485. 486. 487. 488. 489. 490. 491. 492. 493. 494. 495. 496. 497. 498. 499. 500. 501. 502. 503. 504. 505.
Example Programs Send/Receive Program Example Page 12 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 SEND TEST 506. 507. 508. 509. 510. 511. 512. 513. 514. 515. 516. 517. 518. 519. 520. 521. 522. 523. 524. 525. 526. 527. 528. 529. 530. 531. 532. 533. 534. 535. 536. 537. 538. 539. 540. 541. 542. 543. 544. 545. 546. 547. 548. 549. 550. 551. 552. 553. 554. 555. 556. 557. 558. 559. 560. 561. 562.
Example Programs Send/Receive Program Example Page 13 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 SEND TEST 563. 564. 565. 566. 567. 568. 569. 570. 571. 572. 573. 574. 575. 576. 577. 578. 579.
Example Programs Send/Receive Program Example Page 14 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 RECEIVE TEST 581. 582. 583. 584. 585. 586. 587. 588. 589. 590. 591. 592. 593. 594. 595. 596. 597. 598. 599. 600. 601. 602. 603. 604. 605. 606. 607. 608. 609. 610. 611. 612. 613. 614. 615. 616. 617. 618. 619. 620. 621. 622. 623. 624. 625. 626. 627. 628. 629. 630. 631. 632. 633. 634. 635. 636. 637.
Example Programs Send/Receive Program Example Page 15 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 RECEIVE TEST 638. 639. 640. 641. 642. 643. 644. 645. 646. 647. 648. 649. 650. 651. 652. 653. 654. 655. 656. 657. 658. 659. 660. 661. 662. 663. 664. 665. 666. 667. 668. 669. 670. 671. 672. 673. 674. 675. 676. 677. 678. 679. 680. 681. 682. 683. 684. 685. 686. 687. 688. 689. 690. 691. 692. 693. 694.
Example Programs Send/Receive Program Example Page 16 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 RECEIVE TEST 695. 696. 697. 698. 699. 700. 701. 702. 703. 704. 705. 706. 707. 708. 709. 710. 711. 712. 713. 714. 715. 716. 717. 718. 719. 720. 721. 722. 723. 724. 725. 726. 727. 728. 729. 730. 731. 732.
Example Programs Send/Receive Program Example Page 17 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 MAIN PROCEDURE 734. 735. 736. 737. 738. 739. 740. 741. 742. 743. 744. 745. 746. 747. 748. 749. 750. 751. 752. 753. 754. 755. 756. 757. 758. 759. 760. 761. 762. 763. 764. 765. 766. 767. 768. 769. 770. 771. 772. 773. 774. 775. 776. 777. 778. 779. 780. 781. 782. 783. 784. 785. 786. 787. 788. 789. 790.
Example Programs Send/Receive Program Example Page 18 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 MAIN PROCEDURE 791. 792. 793. 794. 795. 796. 797. 798. 799. 800. 801. 802. 803. 804. 805. 806. 807. 808. 809. 810. 811. 812. 813. 814. 815. 816. 817. 818. 819. 820. 821. 822. 823. 824. 825. 826. 827. 828. 829. 830. 831. 832. 833. 834. 835. 836. 837. 838. 839. 840. 841. 842. 843. 844. 845. 846. 847.
Example Programs Send/Receive Program Example Page 19 [1] $RJE.EXCHAPPL.RJEPROG 1991-06-17 11:05:47 1991-06-17 11:05:47 MAIN PROCEDURE 848. 849. 850. 851. 852. 853. 854. 855. 856. 857. 858. 859. 860. 861. 862. 863. 864. 865. 866. 867. 868. 869. 870. 871. 872.
Example Programs User-Exit Procedure User-Exit Procedure User-Exit Procedure Interface Specification This section contains information about the interface to the user-exit procedure, some guidelines for writing your own user-exit procedure, and an example user exit procedure. The function of the user-exit procedure is to instruct an autodial modem to dial the telephone or perform other special processing (such as dialing a non-standard ACU) to establish the connection over the switched line.
Example Programs User-Exit Procedure phone^number^len This is the length of the telephone number, including leading blanks if any. The line server does not scan the telephone number to get the length. The length is obtained from the write count that is passed when the programmatic interface or the Exchange/RJE command interpreter calls WRITE to pass the telephone number to the line server. out^file^name This is the name, in internal-name format, of the line server’s out file.
Example Programs User-Exit Procedure Errors in the range 450 through 510 and greater than 1000 are considered retryable and the command interpreter retries the dialing operation a maximum of five times with a delay of ten seconds between two retries. If the error persists at the end of five retries, the CONNECT operation is aborted. If you want to delay longer than ten seconds between retries for a specific error, you can code your user exit procedure to delay before returning.
Example Programs User-Exit Procedure User-Exit Procedure Example Page 1 [1] This example procedure contains a skeleton user-exit procedure. $RJE.JOSHI.UESRC 1991-06-13 TAL - T9250C30 - (01DEC90) Copyright Tandem Computers Incorporated 1976, 1978, 1981-83, 1985, 1987-90 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60.
Example Programs User-Exit Procedure Page 2 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 1991-06-13 13:25:30 LITERALS 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. Page 3 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 [1] 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 !2.
Example Programs User-Exit Procedure Page 4 [1] $RJE.JOSHI.UESRC 1991-06-13 LOCAL VARIABLE DECLARATIONS 87. 88. 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. 124. 125. 126. 127. 128. 129. 130. 131. 132. 133. 134. 135. 136. 137. 138.
Example Programs User-Exit Procedure Page 5 [1] $RJE.JOSHI.UESRC 1991-06-13 SUBPROC 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. 168. 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.
Example Programs User-Exit Procedure Page 6 [1] $RJE.JOSHI.UESRC 1991-06-13 SUBPROC 197. 198. 199. 200. 201. 202. 203. 204. 205. 206. 207. 208. 209. 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.
Example Programs User-Exit Procedure Page 7 [1] $RJE.JOSHI.UESRC 1991-06-13 SUBPROC 254. 255. 256. 257. 258. 259. 260. 261. 262. 263. 264. 265. 266. 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.
Example Programs User-Exit Procedure Page 8 [1] $RJE.JOSHI.UESRC 1991-06-13 SUBPROC DISCONNECT^LINE 311. 312. 313. 314. 315. 316. 317. 318. 319. 320. 321. 322. 323. 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.
Example Programs User-Exit Procedure Page 9 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 SUBPROC ANALYZE^MODEM^RESPONSE 365. 366. 367. 368. 369. 370. 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. 419. 420. 421.
Example Programs User-Exit Procedure Page 10 [1] $RJE.JOSHI.UESRC 1991-06-13 SUBPROC ANALYZE^MODEM^RESPONSE 422. 423. 424. 425. 426. 427. 428. 429. 430. 431. 432. 433. 434. 435. 436. 437. 438. 439. 440. 441. 442. 443.
Example Programs User-Exit Procedure Page 11 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 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. 471. 472. 473. 474. 475. 476. 477. 478. 479. 480. 481. 482. 483. 484. 485. 486. 487. 488. 489. 490. 491. 492. 493. 494. 495. 496. 497. 498. 499. 500. 501.
Example Programs User-Exit Procedure Page 12 [1] $RJE.JOSHI.UESRC 1991-06-13 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 502. 503. 504. 505. 506. 507. 508. 509. 510. 511. 512. 513. 514. 515. 516. 517. 518. 519. 520. 521. 522. 523. 524. 525. 526. 527. 528. 529. 530. 531. 532. 533. 534. 535. 536. 537. 538. 539. 540. 541. 542. 543. 544. 545. 546. 547. 548. 549. 550. 551. 552. 553. 554. 555. 556. 557. 558.
Example Programs User-Exit Procedure Page 13 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 559. 560. 561. 562. 563. 564. 565. 566. 567. 568. 569. 570. 571. 572. 573. 574. 575. 576. 577. 578. 579. 580. 581. 582. 583. 584. 585. 586. 587. 588. 589. 590. 591. 592. 593. 594. 595. 596. 597. 598. 599. 600. 601. 602. 603. 604. 605. 606. 607. 608. 609. 610. 611. 612. 613. 614. 615.
Example Programs User-Exit Procedure Page 14 [1] $RJE.JOSHI.UESRC 1991-06-13 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 616. 617. 618. 619. 620. 621. 622. 623. 624. 625. 626. 627. 628. 629. 630. 631. 632. 633. 634. 635. 636. 637. 638. 639. 640. 641. 642. 643. 644. 645. 646. 647. 648. 649. 650. 651. 652. 653. 654. 655. 656. 657. 658. 659. 660. 661. 662. 663. 664. 665. 666. 667. 668. 669. 670. 671. 672.
Example Programs User-Exit Procedure Page 15 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 673. 674. 675. 676. 677. 678. 679. 680. 681. 682. 683. 684. 685. 686. 687. 688. 689. 690. 691. 692. 693. 694. 695. 696. 697. 698. 699. 700. 701. 702. 703. 704. 705. 706. 707. 708. 709. 710. 711. 712. 713. 714. 715. 716. 717. 718. 719. 720. 721. 722. 723. 724. 725. 726. 727. 728. 729.
Example Programs User-Exit Procedure Page 16 [1] $RJE.JOSHI.UESRC 1991-06-13 13:25:30 1991-06-13 13:25:30 PROC USER^EXIT^MODEM^SUPPORT: PROCEDURE BODY 730. 731. 732. 733. 734. 735. 736. 737. 738. 739. 740. 741. 742. 743. 744. 745. 746. 747. 748.
Appendix E Supplemental Information for D-Series Systems D-series Exchange/RJE 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/RJE product relevant to the Exchange/RJE Manual.
Supplemental Information for D-Series Systems Conversion of C Series Applications Conversion of In pre-C30 software, the line server returns a reply code of 0 (FEOK) to the startup C-Series Applications message when you start the line server (RJESV) with a call to NEWPROCESS. D-series Exchange/RJE returns a reply code of 70. To convert a pre-C-30 application modify its code so that it recognizes the reply code of 70.
Index 2780 emulation See also Transmission block format EM character 3-51 features 1-6/7 specifying in CONNECT command 3-9 in SETMODE procedure 5-28 3780 emulation See also Transmission block format blank compression 3-50, 3-55 expansion of compressed blanks 3-39 features 1-6/7 specifying in CONNECT command 3-9 in SETMODE procedure 5-28 6100 CSS See CP6100 A ABORT command 3-6/7 ACK 0 C-1 ACK 1 C-2 ACU errors 3-10 example of use with command interpreter 2-7/8 specifying in RJESV command 5-3 in SET command 3-
Index Autodial modem controlling 1-2 Automatic calling unit See ACU Automatic calling unit (ACU) and user-exit routine 2-2 AWAITIO procedure 5-7/8 B Backup process, line server 3-63, 5-4 Bid for the line See BSC Binary Synchronous Communications See BSC Blanks compression 3-50, 3-55 expansion when compressed 3-39 truncation 3-53 Block mode See also Transmission block format features 1-7/8 starting line server 4-9 Blocks, transmission See Transmission block format BREAK key during command file execution 2-4
Index BSC (continued) line control codes (continued) ETX C-4, 3-37, 4-5, 5-13, 5-25 including in received data 3-34 NAK C-3 pad C-5 RVI C-5 STX C-2 SYN C-1 TTD C-3 WACK C-3 protocol examples abort by receiver C-18 abort by transmitter C-17 block lost in transmission C-14 delay of transmission by receiver C-12 delay of transmission by transmitter C-13 line contention C-7 mismatched acknowledgment C-15 normal message transmission C-6 receiver stops unexpectedly C-16 retransmission accepted C-8 retransmission
Index Command files BREAK key, using during execution 2-4, 3-31 comment lines 3-8 error handling 2-4, 3-30 format 2-4 overview of use 2-3 use with the OBEY command 2-4, 3-30 use with the RJECIR command IN option 2-3, 3-2 Command interpreter BREAK key 2-3 concurrent operations 2-2 connecting to line server 3-4, 3-12 CPU specification 3-1 editing commands 3-25/26 error messages A-2/19 examples sending and receiving, nonswitched line 2-6/7 sending and receiving, switched line 2-7/8 sending data without transl
Index Commands ABORT 3-6/7 COMMENT 3-8 CONNECT 3-9/13 DISCONNECT 3-14/15 DUMP 3-16/23 editing 3-25/26 EXIT 3-24 FC 3-25/26 HELP 3-27 OBEY 3-30/31 parameters, separation of 3-1 RECEIVE 3-32/46 RESET 3-47/49 RJECIR 3-1/5 RJESV 4-9, 5-2/6 SEND 3-50/59 SET 3-60/69 SHOW 3-70/72 STATUS 3-73/75 summary 2-1 syntax note 3-1 TRACE 3-76/77 COMMENT command 3-8 Communications lines See Data communications lines Communications Management Interface See CMI commands Communications subsystems CP6100 1-4 differences between
Index Configuration parameters ACU 3-60, 5-3 BACKUPCPU 5-4 BLOCKING 3-61, 5-4 BLOCKSIZE 3-61, 5-4 changed by DISCONNECT command 3-15 changed by RESET command 3-47 CPUS 3-61 displaying 3-70 EBCDICNL 3-62, 5-5 LINE 3-62, 5-5 minimum requirements 2-5 NONSTOP 3-63 PRIORITY 3-63 PROGRAM 3-63 restrictions on changing 3-67 SERVER 3-65 setting 2-5 TRACE 3-65 USERLIB 3-66 CONNECT command 2-5, 3-9/13 Connection changing, with command interpreter 3-12 duration, when established by CONNECT command 3-12 ending with DIS
Index D Data communications lines ASCII 1-4 ASCII or EBCDIC, specifying 6-4 concurrent use of 2-2 configuration 6-2 connecting to with CONNECT command 2-5, 3-9 with SETMODE procedure 5-28/30 EBCDIC 1-4 required specification 2-5 specifying 3-62, 5-5 switched 2-5 disconnecting 3-14 telephone number, specifying 3-9, 5-29 types 5-16 Data, translation 3-36, 3-43, 3-52, 5-34 Designing user-exit procedures D-20 DEVICEINFO procedure 5-15/16 DIAL parameter and user-exit routine 2-2 DISCONNECT command 3-14/15 Disco
Index Emulation, 3780 See 3780 emulation End of text See ETX End of transmission See EOT End-of-media character See EM ENQ C-1, 3-53 ENVOY 1-4 EOT C-5, 3-6, 3-28, 3-53, 4-18, 5-13, 5-25 Error handling error numbers 4-5/7 in command files 2-4, 3-30 nowait I/O procedure calls 4-5 programmatic interface 4-4 Error messages command interpreter A-2/19 format A-1 line server A-26/30 send/receive server A-19/25 trace server A-2 Error values 301 4-16, 5-26 310 5-26 312 5-30 70 4-13 negative values and user-exit pro
Index Examples BSC protocol abort by receiver C-18 abort by transmitter C-17 block lost in transmission C-14 delay of transmission by receiver C-12 delay of transmission by transmitter C-13 line contention C-7 mismatched acknowledgment C-15 normal message transmission C-6 receiver stops unexpectedly C-16 retransmission accepted C-8 retransmission rejected C-9, C-10, C-11 transmitter stops unexpectedly C-17 unanswered line bid C-8 command interpreter sending and receiving, nonswitched line 2-6/7 sending and
Index EXIT command 3-24 Exit procedure user library, specifying 3-66 Expansion of compressed blanks 3-39 F FC command 3-25/26 Features 1-1 FILEINFO procedure 5-17 Files command See Command files print See Print files program See Program files punch See Punch files receiving See Receive operations sending See Send operations sent to the remote system 3-50 trace 3-16, 3-76 FLAGS field, trace record 3-20 Format See also Transmission block format command files 2-4 error messages A-1 writing unstructured disk f
Index H HELP command 3-27 I i.
Index Line server (continued) starting block mode 4-9 for programmatic use 4-9 with CONNECT command 2-6, 3-3, 3-4, 3-12, 3-67 with NEWPROCESS procedure 4-10, 5-18 with RJESV command 5-2 startup message 4-10, 4-11/13 stopping with CLOSE procedure 5-35 with CONTROL procedure 5-13, 5-14 with DISCONNECT command 2-6, 3-5, 3-15, 3-68 with EXIT command 3-5, 3-68 with TACL STOP command 3-5, 3-15, 3-68 temporary 2-6 user-exit procedure errors D-20 Lines, data communications See Data communications lines Logon comma
Index OBEY file See Command file OPEN procedure 4-10, 4-13, 5-20/22 Operation, modes of 2780 emulation 1-6/7 3780 emulation 1-6/7 block mode 1-7/8 choosing between 2780 and 3780 modes 1-7 specifying 3-9, 5-28 Output command interpreter 3-2 P Pad C-5 Parameters for user-exit procedure 4-14 separation of 3-1 PAUSE, TACL command 2-4, 3-31 Peripheral Utility Program See PUP commands PRIMARY status 3-10, 5-28 Print files 3-32 open mode 3-43 unstructured disk files 3-43 Priority of line server execution 3-63 Pro
Index Procedures (continued) WRITE 5-37/39 WRITEREAD 5-40/42 Process ID, line server 5-18 Process names See Names, process Program files command interpreter 6-1 installation 6-1 line server 3-63, 5-18, 6-1 send/receive server 6-1 trace server 6-1 Programmatic interface aborting a receive operation 5-13 ACU, specifying 5-29 components of 1-2 disconnecting after receiving 4-18 after sending 4-18 DLE EOT, receiving 5-25 end of file, sending 5-13 ending a send operation 5-13 EOT, receiving 5-25 error handling
Index Programmatic interface (continued) receiving files 4-15 send operation parameters 5-30/33 sending files 4-14 setting operation parameters 4-14 specifying mode of operation 5-28 switching from receiving to sending 4-17 switching from sending to receiving 4-17 telephone number, specifying 5-29 trace server, using 4-8 using overview 1-5 step-by-step instructions 4-8 wait I/O operations 4-2 Punch files 3-32/33 open mode 3-43 receiving transparent text 3-43 PUP commands for Envoy data communications lines
Index Record size command file 2-4 files sent to the remote system 3-51 print file 3-32 punch file 3-32 Remote system logon commands 3-10 RESET command 3-47/49 Return values negative values and user-exit procedures D-19 RJECIR command 3-1/5 using command files with the IN option 2-3, 3-2 RJELIB default user library 1-2 using D-19 RJESV command 4-9, 5-2/6 RJESV file user exit considerations 2-2 RUN, TACL command 3-1, 3-3, 4-9 RVI C-5 S SECONDARY status 3-10, 5-28 SEND command 3-50/59 Send operations using c
Index Send/receive server CPU specification 3-1 error messages A-19/25 overview 1-1 program file 6-1 starting 2-6, 3-12 stopping 2-6, 3-12, 3-14 SET command 3-60/69 restrictions on use 3-67 SETMODE procedure 4-14, 5-27/36 user-exit procedure parameters 5-28 SHOW command 3-70/72 Stacker selection, punch file 3-33 Startup message error 70 in response 4-13 line server 4-10, 4-11/13 Statistics, displaying 3-73 Status See System status STATUS command 3-73/75 STX C-2 SYN C-1 Syntax, meaning of commas 3-1 SYSGEN
Index Telephone number, specifying user-exit procedure requirements 3-9 with CONNECT command 3-9 with programmatic interface 5-29 TRACE command 3-76/77 Trace file 3-16, 3-76 Trace record FLAGS field 3-20 Trace server error messages A-2 making its use mandatory 3-65 overview 1-2 program file 6-1 using 3-76 with programmatic interface 4-8 Translation of data 3-36, 3-43, 3-52 Translation tables modifying B-10 Transmission block format 2780 emulation normal text, received 3-38 normal text, sent 3-54 transparen
Index Transmission block format (continued) block mode without blocking normal text, received 3-42 normal text, sent 3-58 transparent text, received 3-42 transparent text, sent 3-58 Transparent data receiving 5-26 Transparent text receiving 3-43, 4-16 sending 3-52 Truncation of trailing blanks 3-53 TTD C-3 U User exit general considerations 2-2 User library 1-2 parameters 4-14 specifying 3-66, 5-2 User-exit procedure calling, requirements 3-9 error values D-20 User-exit procedures design guidelines D-20 in
Index W WACK C-3 Wait I/O procedure calls 4-2 compared to nowait I/O 4-3 WRITE procedure 5-37/39 WRITEREAD procedure 5-40/42 Special characters ! parameter in CONNECT command 3-11 * parameter in RESET command 3-47 in SHOW command 3-70 Index–20 104698 Tandem Computers Incorporated
