Envoy Configuration and Management Manual Abstract The Envoy subsystem provides general-purpose protocol support that enables application programs or terminals to communicate over communications lines on a ServerNet wide area network (SWAN) concentrator. This manual describes the processes involved in configuring and managing the Envoy subsystem. Product Version Envoy F40 Supported Releases This manual supports G03.00 and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 429861-001 Envoy April 2001 427131-000 Envoy November 2000 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
Envoy Configuration and Management Manual Glossary Index Examples Figures Tables What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Who Should Use This Manual How This Manual Is Organized xi xi Related Documents and Online Tools xii Your Comments Invited xvi Notation Conventions xvii 1.
2. Introduction to Envoy (continued) Contents 2. Introduction to Envoy (continued) PROCESS, DEVICE, and PROFILE Objects WAN Subsystem Configuration Database 2-5 2-5 2-5 SCF Command Routing Protocols Supported 2-5 Point-to-Point Data Links 2-6 Multipoint Data Link 2-8 Polling (Invitation to Send) 2-9 Selection (Request to Send) 2-9 2-10 Half-Duplex and Full-Duplex Lines 3.
4. Subsystem Control Facility (SCF) for Envoy (continued) Contents 4. Subsystem Control Facility (SCF) for Envoy (continued) Objects for Envoy 4-6 Envoy Object Types and Names Envoy Object States 4-6 4-7 5.
5. Subsystem Control Facility (SCF) Commands for Envoy (continued) Contents 5. Subsystem Control Facility (SCF) Commands for Envoy (continued) STOP DEVICE Command 5-49 STOP LINE Command 5-50 5-51 TRACE LINE Command VERSION Command 5-56 6.
B. Envoy Event Messages Contents B.
D. S-Series Changes to Envoy (continued) Contents D. S-Series Changes to Envoy (continued) FDX Line Changes D-4 No Support for Auto-Call Unit D-4 Glossary Index Examples Example 1-1. Adding a Profile 1-3 Example 1-2. Adding a Line-Handler Process Example 1-3. Starting the Line-Handler Process 1-6 Example 1-4. Starting the Line Example 1-5. Stopping the Device 1-9 Example 1-6. Deleting the Device 1-9 Example 1-7.
Examples (continued) Contents Examples (continued) Example 5-10. STATS LINE Command 5-43 Example 5-11. STATUS DEVICE Command 5-45 Example 5-12. STATUS LINE Command Example 5-13. STATUS LINE DETAIL Command Example 5-14. VERSION Command Example 5-15. VERSION DETAIL Command 5-46 5-47 5-56 5-56 Figures Figure i. NonStop Himalaya S-Series Configuration and Management Manual Set xii Figure ii. TSM Manuals and Online Help Figure 1-1.
Tables (continued) Contents Tables (continued) Table 5-5. Types, Subtypes, Protocols, and Profiles of Envoy Lines 5-30 Table 5-6. Select Specification for a LINE Object Table 6-1. Summary of PTrace Commands Common to All Subsystems 6-3 Table 6-2. PTrace Commands for Envoy 6-5 Table 6-3. Select Option Keywords for Envoy 6-8 Table B-1. Envoy Event Messages B-1 Table B-2. Envoy Event Messages Defined by Other Subsystems Table B-3.
What’s New in This Manual Manual Information Envoy Configuration and Management Manual Abstract The Envoy subsystem provides general-purpose protocol support that enables application programs or terminals to communicate over communications lines on a ServerNet wide area network (SWAN) concentrator. This manual describes the processes involved in configuring and managing the Envoy subsystem. Product Version Envoy G-Series Supported Releases This manual supports G03.
What’s New in This Manual New and Changed Information Envoy Configuration and Management Manual—429861-001 x
About This Manual This manual describes configuration and management of an Envoy subsystem running on a Compaq NonStop™ Himalaya S-series server. Who Should Use This Manual This manual is written for those who provide the following services for the server and the software environment at a particular site: • Planning • Installation and configuration • Maintenance, optimization, and troubleshooting How This Manual Is Organized This manual has the following sections: Section Title This Section...
Related Documents and Online Tools About This Manual Related Documents and Online Tools This manual is part of the NonStop Himalaya S-series configuration and management manual set. Figure i shows the manuals you need to consult to run Envoy on NonStop Himalaya S-series servers. This manual is highlighted in the figure. Figure i.
Stem Manual About This Manual Stem Manual • Himalaya S-Series Planning and Configuration Guide This guide describes planning considerations and is part of the NonStop Himalaya S-series server manual set. Core Configuration Manuals • DSM/SCM User’s Guide The Distributed Systems Management/Software Configuration Manager (DSM/SCM) is a system for the centralized planning, management, and installation of software on standalone and distributed Compaq systems.
Envoy Subsystem Manuals About This Manual • SCF Reference Manual for the Storage Subsystem This manual describes how to use the Subsystem Control Facility (SCF) to configure, control, and inquire about storage devices on a NonStop Himalaya S-series server.
TSM Manuals and Online Help About This Manual TSM Manuals and Online Help TSM manuals and online help provide information about using the TSM package to bring up and maintain NonStop Himalaya S-series servers. Figure ii shows the TSM manuals and online help. Figure ii.
WAN Wizard Installation and Configuration Tool About This Manual • TSM Low-Level Link Application online help TSM Low-Level Link online help is a Microsoft Windows online help system for the TSM Low-Level Link Application. TSM Low-Level Link Application online help describes how to perform tasks using the TSM Low-Level Link Application and provides quick-reference information, including how to use commands and dialog boxes.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i. In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Change Bar Notation About This Manual Envoy Configuration and Management Manual—429861-001 xxii
1 Configuration Quick Start This section provides a concise example of creating a profile, configuring new and existing Envoy communications lines, and starting a line. For an introduction to Envoy, see Section 2, Introduction to Envoy. For information about the SCF command syntax, see Section 5, Subsystem Control Facility (SCF) Commands for Envoy. You can use the WAN Wizard configuration tool to help you to configure Envoy and the ServerNet wide area network (SWAN) concentrator.
Task 1: Create a PROFILE Object for the Line-Handler Process Configuration Quick Start Table 1-1.
Configuration Quick Start Task 2: Create the Line-Handler Process Adding a PROFILE Object The following Example 1-1 shows how to add a PROFILE object. The PROFILE name can be any name that conforms to the naming guidelines in the WAN Subsystem Configuration and Management Manual. In this example, the PROFILE name is #ENV01. PENVBSC is the name of the template file, or disk file, that Compaq supplies for the BISYNC communications protocol. $ZZWAN is the name of the WAN subsystem and $SYSTEM.
Configuration Quick Start Task 2: Create the Line-Handler Process PROFILE profile_name is the name of the profile you created for this Envoy line-handler process in Task 1: Create a PROFILE Object for the Line-Handler Process. CPU cpunumber indicates the processor where this Envoy line-handler process normally executes. ALTCPU altcpunumber indicates the processor where the backup Envoy line-handler process normally executes. TYPE (7,n) is the device type and subtype for this Envoy line-handler.
Configuration Quick Start Task 2: Create the Line-Handler Process LINE linenum is the line number (0 or 1) on the selected CLIP specified by clipnum. linenum must not have been previously selected for use by another line-handler process. PATH { A | B } is the Ethernet path (A or B) on the CLIP, specified by clipnum. This path must have been previously defined through the WAN subsystem SCF ADD PATH command.
Configuration Quick Start Task 3: Start the Line-Handler Process Example 1-2. Adding a Line-Handler Process -> ADD DEVICE $ZZWAN.#ENV01, TYPE (7, 0), IOPOBJECT $SYSTEM.SYS01.OENVOY, PROFILE PENVBSC, CLIP 1, LINE 0, CPU 0, ALTCPU 1, ADAPTER CONC1, RSIZE 512, PATH A, Task 3: Start the Line-Handler Process To start a line-handler process, use the WAN subsystem SCF START DEVICE command. The command syntax is as follows: START DEVICE $ZZWAN.
Configuration Quick Start Reconfiguring Existing Communications Lines Example 1-4. Starting the Line -> START LINE $ENV01 Reconfiguring Existing Communications Lines Once the process exists in the configuration database (as a DEVICE object) and you start the process by using START DEVICE, you can start, stop, and change the associated line OBJECT’s attributes directly through the Envoy subsystem. (You can also start, stop, and change the DEVICE object in the WAN subsystem.
Reconfiguring Existing Communications Lines Configuration Quick Start Figure 1-1. Configuration Commands to the Envoy Subsystem Terminal Envoy Application OBEY File SCF Commands Guardian Procedure Calls SCF Log File SCP Envoy Subsystem Envoy Line-Handler Process Line CDT409.CDD To reconfigure an existing Envoy communications line, first decide whether you want: • • • The line attribute definition always to revert to the change stored in the configuration database.
Configuration Quick Start Changing the Modifier Definitions in the PROFILE Object Based on how you want to make the change, choose one of the following methods, described later in this section: • • • • Changing the Modifier Definitions in the PROFILE Object on page 1-9 Changing the Modifier Definitions in the DEVICE Object on page 1-10 Changing LINE Object Attributes in the Envoy Subsystem Using SCF on page 1-11 Changing LINE Object Attributes in the Envoy Subsystem Using Guardian Procedure Calls on pag
Configuration Quick Start Changing the Modifier Definitions in the DEVICE Object Example 1-8. Re-Adding the DEVICE Object, Associating the Modified PROFILE Object -> ADD DEVICE $ZZWAN.#ENV01, TYPE (7, 40), IOPOBJECT $SYSTEM.SYS01.OENVOY, PROFILE MYPROF, CLIP 1, LINE 0, CPU 0, ALTCPU 1, ADAPTER CONC1, RECSIZE 512, PATH A Step 5: Starting the New DEVICE Object Start the DEVICE object as shown in Example 1-9: Example 1-9. Starting the Device -> START DEVICE $ZZWAN.
Configuration Quick Start Changing LINE Object Attributes in the Envoy Subsystem Using SCF Changing LINE Object Attributes in the Envoy Subsystem Using SCF Step 1: Stopping the Line Stop the LINE object by issuing an SCF STOP LINE command to the Envoy subsystem as in Example 1-13: Example 1-13.
Configuration Quick Start Changing LINE Object Attributes in the Envoy Subsystem Using Guardian Procedure Calls Envoy Configuration and Management Manual—429861-001 1- 12
2 Introduction to Envoy The Envoy subsystem provides general-purpose protocol support that enables application programs or terminals to communicate over communications lines on a ServerNet wide area network (SWAN) concentrator.
Envoy Communications Interface Introduction to Envoy Envoy Communications Interface The Envoy subsystem provides a data-link-level interface between transaction-oriented applications and data communications networks that use byte-synchronous or asynchronous communications lines. Using Envoy, you can establish data links between your Compaq system and a variety of remote computers and terminals (Figure 2-1). Figure 2-1.
ServerNet WAN Concentrator Introduction to Envoy Envoy accesses the SWAN concentrator through Compaq NonStop TCP/IP and the ServerNet LAN Systems Access (SLSA) subsystems. The SWAN concentrator connects to the NonStop Himalaya S-series server through dual 10Base-T Ethernet connections, which provide fault tolerance if an Ethernet link or controller fails. The SWAN concentrator replaces the 3602 byte-synchronous and the 3603 asynchronous controllers.
Envoy Lines and Line-Handler Processes Introduction to Envoy • • • Conversion of ASCII code to EBCDIC code, and EBCDIC to ASCII Automatic polling of multipoint tributary stations Point-to-point or multipoint transmission modes Multipoint Polling In Envoy multipoint configurations, the ServerNet WAN concentrator also handles some polling functions. When used as the supervisor station, the ServerNet WAN concentrator manages the polling of the lines.
PROCESS, DEVICE, and PROFILE Objects Introduction to Envoy PROCESS, DEVICE, and PROFILE Objects In the WAN subsystem, you can change the line-handler process modifiers in two ways: • • By defining a new PROFILE object and using the ADD PROFILE command to specify the modifiers. By using the ADD DEVICE command to specify the modifiers. See the WAN Subsystem Configuration and Management Manual for details about these two methods of changing line-handler process modifiers.
Point-to-Point Data Links Introduction to Envoy Table 2-1.
Point-to-Point Data Links Introduction to Envoy Figure 2-2. Point-to-Point Switched Line Station A Station C Station B Public Data Network Modem Modem CDT005.CDD A nonswitched line (Figure 2-3), on the other hand, provides a permanent path between stations. This path can be a privately owned cable (often the case when a terminal is connected to a computer) or a dedicated path leased from a common carrier, such as the public telephone network.
Introduction to Envoy Multipoint Data Link Figure 2-3. Point-to-Point Nonswitched Line Station Station Privately Owned Cable or Nonswitched Line CDT006.CDD Multipoint Data Link A somewhat more complex network consists of several terminals or computers connected in parallel to a single communications line. This configuration is a multipoint data link; each terminal or computer is a station in the network.
Introduction to Envoy Polling (Invitation to Send) Polling (Invitation to Send) To solicit data transfers from the tributary stations, the supervisor station periodically polls each tributary station in the multipoint link. Polling is performed by transmitting a tributary’s polling sequence and then waiting momentarily for a response from the tributary. If the tributary has no data to transmit, the next tributary station in the multipoint link is polled.
Introduction to Envoy Half-Duplex and Full-Duplex Lines Half-Duplex and Full-Duplex Lines An Envoy, point-to-point or multipoint data link can use either half-duplex or fullduplex line facilities. For half-duplex facilities, the transmission lines can physically pass data in only one direction at any given time (Figure 2-5). The direction of the data flow can be switched only by a line turnaround: one station disables its read unit and enables its write unit while the other station does the opposite.
Introduction to Envoy Half-Duplex and Full-Duplex Lines Figure 2-6. Full-Duplex Lines Send Receive CDT 009.CDD Besides being either half-duplex or full-duplex, communications are affected by logical states that enable either two-way alternate or two-way simultaneous transmission. Twoway alternate transmission can occur over either half-duplex or full-duplex lines; the protocol never attempts to transmit simultaneously in both directions.
Introduction to Envoy Half-Duplex and Full-Duplex Lines Envoy Configuration and Management Manual—429861-001 2- 12
3 WAN Subsystem Profiles and Modifiers for Envoy This section describes the WAN subsystem profile disk files and modifiers for the Envoy subsystem. Topics described in this section include the following: • • • • Profiles and Associated Protocols on page 3-1 Required Modifiers on page 3-3 Optional Modifiers on page 3-3 Modifier Descriptions on page 3-3 Profiles and Associated Protocols Profiles disk files specify the characteristics for a group of communications lines.
WAN Subsystem Profiles and Modifiers for Envoy Profiles and Associated Protocols Table 3-2.
WAN Subsystem Profiles and Modifiers for Envoy Required Modifiers Required Modifiers You must specify the following modifiers for each full-duplex Envoy line-handler process.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Table 3-3.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Table 3-3.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Table 3-3.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Table 3-3.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions ACKOFF Default: ACKOFF Units: Not applicable Range: Not applicable Alternate modifier: ACKON This modifier applies to BSC lines only. It enables EBCDIC ACK to compare sequences. ACKON Default: ACKOFF Units: Not applicable Range: Not applicable Alternate modifier: ACKOFF This modifier applies to BSC lines only. It enables ASCII ACK to compare sequences.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions BREAKENA Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to SIMPLEX and ASC lines only. It enables break detection during receive and transmit operations. This modifier can be altered with a call to SETMODE 15. Once this modifier is added to the device record, it can only be removed by using the SCF ALTER DEVICE command with the RESET modifier option.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions You specify the value for RSIZE/RECSIZE on the Configure Modifier Information dialog box in WAN Wizard Pro. CBSENSEOFF Default: CBSENSEOFF Units: Not applicable Range: Not applicable Alternate modifier: CBSENSEON This modifier applies to BSC lines only. It disables monitoring of the Clear-to-Send (CB) signal during data transmission.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to BSC lines only. It disables monitoring of the carrier signal (CF) during transmission. CFSENSEON Default: CFSENSEOFF Units: Not applicable Range: Not applicable Alternate modifier: CFSENSEOFF This modifier applies to BSC lines only. It enables monitoring of the carrier signal (CF) during transmission. If a signal loss is detected, a modem error is reported.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions CL Default: EIA Units: Not applicable Range: Not applicable Alternate modifier: EIA This modifier applies to ADM, TINET, SIMPLEX, and ASC lines only. It defines the electrical connection type as current-loop. CLEARCA Default: CLEARCA Units: Not applicable Range: Not applicable Alternate modifier: NOCLEARCA This modifier applies to BSC lines only. It specifies to clear the CA from write to send.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions CRC16 Default: CRC16 Units: Not applicable Range: Not applicable Alternate modifier: LRC8, CCITTON This modifier applies to BSC lines only. It causes CRC-16 block-check characters to be generated. CTLTERM1 or CTLTERM2 Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: The other CTLTERM modifier This modifier applies to SIMPLEX and ASC lines only. It determines how a read is terminated.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions CTRLCF Default: CTRLCF Units: Not applicable Range: Not applicable Alternate modifier: NOCTRLCF This modifier applies to BSC lines only. It specifies that the carrier wait to drop before raising CA. CTLR6297 Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to BSC lines only. It causes the KATAKANA character set to be used. Inbound data is translated from KATAKANA to ASCII.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions DEDICATED is specified, the BUFSIZE n modifier, which defines the size of the dedicated buffer, must also be specified. You must specify this modifier for full-duplex BSC lines (device types (7,30), (7,31), (7,32), and (7,33)). DSRSENSE Default: ON Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to SIMPLEX and ASC lines only. It enables DSRSENSE capability for the asynchronous protocol.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to SIMPLEX and ASC lines only. It enables DSRSENSE capability for the asynchronous protocol. The loss of the DSR modem signal is sensed and reported as an error during a READ or WRITE operation. DTROFF Default: DTRON Units: Not applicable Range: Not applicable Alternate modifier: DTRON This modifier applies to BSC lines only. It sets the Data-Terminal-Ready (DTR) signal off.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Once this modifier is added to the device record, it can only be removed by using the SCF ALTER DEVICE command with the RESET modifier option. EBCDIC Default: ASCII Units: Not applicable Range: Not applicable Alternate modifier: ASCII This modifier applies to BSC lines only. It specifies the transmission code as EBCDIC. Inbound data is translated from EBCDIC to ASCII. Outbound data is translated from ASCII to EBCDIC.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to all Envoy line types. It causes all event messages to be sent to the console, regardless of the value of the ZEMS-TKN-CONSOLE-PRINT token. EMSOFF Default: EMSOFF Units: Not applicable Range: Not applicable Alternate modifier: EMS This modifier applies to all Envoy line types. It causes event messages to be sent to the console as determined by the value of the ZEMS-TKN-CONSOLE-PRINT token.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Alternate modifier: ODD, NONE This modifier applies to ADM, TINET, SIMPLEX, and ASC lines only. It specifies even parity. FULL Default: HALF for BSC lines; FULL for ADM, TINET, SIMPLEX, and ASC lines Units: Not applicable Range: Not applicable Alternate modifier: HALF This modifier applies to all Envoy line types. It specifies a full-duplex line. When used for BSC lines, the FULL modifier does not affect the line.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions IDLETIMER n Default: 1000 Units: 0.01 seconds Range: 300 to 32727 Alternate modifier: None This modifier applies to all Envoy line types. It specifies the interval for probing the status of the data link control (DLC) task during periods of inactivity between the Envoy line-handler process and the DLC task.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions KATAKANA Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to BSC lines only. It causes the KATAKANA character set to be used. Inbound data is translated from KATAKANA to ASCII. Outgoing data is translated from ASCII to KATAKANA. CTLR6297 appears automatically when you specify the KATAKANA modifier.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to BSC lines only. It specifies that the 8-bit LRC block-check character is used. MONITORCD Default: ON Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to BSC lines only. It enables monitoring of the carrier signal (CF) during transmission. If a signal loss is detected, a modem error is reported. The MONITORCD modifier should be used only for full-duplex lines.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions MPTRIB Default: MPTRIB for BSC lines; MPSUPV for BSC, ADM and TINET lines; and PPNSW for SIMPLEX and ASC lines Units: Not applicable Range: Not applicable Alternate modifiers: PPNSW, PPSW, MPSUPV This modifier applies to all Envoy line types. It is required for a multipoint tributary line. The SWITCH modifier is removed when you specify the MPTRIB modifier.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions MULTI Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: None This modifier specifies that the process which controls the $dev-name also controls this line. Although it is possible to have the same process control different types of Envoy lines by using the MULTI modifier, you should not mix asynchronous and byte-synchronous lines.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions NOCLEARCA Default: CLEARCA Units: Not applicable Range: Not applicable Alternate modifier: CLEARCA This modifier applies to BSC lines only. It specifies not to clear a Request-to-Send (CA) on a switch from write to read. NOCTLRCF Default: CTRLCF Units: Not applicable Range: Not applicable Alternate modifier: CTLRCF This modifier applies to BSC lines only. It specifies that the carrier not wait to drop before raising CA.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions NOERRDIFF Default: NOERRDIFF Units: Not applicable Range: Not applicable Alternate modifier: ERRDIFF This modifier applies to BSC lines only. It causes error 171 to be returned for noresponse conditions. NOLEADEOT Default: LEADEOT Units: Not applicable Range: Not applicable Alternate modifier: LEADEOT This modifier applies to BSC lines only. It specifies that both a poll and a select are not preceded with an EOT.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions NOSETMODEDTRCTRL Default: SETMODEDTRCTRL Units: Not applicable Range: Not applicable Alternate modifier: SETMODEDTRCTRL This modifier applies to BSC, SIMPLEX, and ASC lines only. It specifies that SETMODE 16 will not affect the state of the DTR lead. NUMBLOCKS Default: 2 Units: Not applicable Range: 2 through 15 Alternate modifier: None This modifier applies to BSC lines only.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Alternate modifier: TWOUNIT This modifier applies to all Envoy line types. It specifies one unit per logical line. For full-duplex BSC lines (device types (7,30), (7,31), (7,32), and (7,33)), you configure two Envoy line-handler processes on the same SWAN concentrator line, one for the outgoing line (UNIT 0) and one for the incoming line (UNIT 1). You must specify the ONEUNIT modifier for these line types.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Once this modifier is added to the device record, it can only be removed by using the SCF ALTER DEVICE command with the RESET modifier option. POLLSELSEQ Default: EOT Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to BSC lines only. It specifies that both a poll and a select are preceded with EOT. Note. This modifier is similar to the LEADEOT/NOLEADEOT device modifiers.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions PPSW Default: PPNSW for SIMPLEX and ASC lines; MPSUPV for BSC, ADM, and TINET lines Units: Not applicable Range: Not applicable Alternate modifier: PPNSW, MPSUPV This modifier applies to all Envoy line types. It specifies a point-to-point, switched line. The SWITCH modifier appears when you specify the PPSW modifier.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to all Envoy line types. It is for internal use only and should not be modified. RAISERTS Default: ON Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to BSC lines only. It specifies that the carrier wait to drop before raising CA. Note. This modifier is similar to the CTRLCF/NOCTRLCF device modifiers.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Read-only lines can also be specified by calling the SETMODE 16 procedure: SETMODE 16 parm1.13 0 = normal, 1 = READCONT The following read termination modifiers are ignored for read-only lines: TCHAR1 through TCHAR4, CLTERM1, and CLTERM2. Read-only lines require a dedicated buffer to be defined. See the description of the DEDICATED modifier for more information.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions RSIZE Default: None Units: BYTES Range: 512 through 4096 Alternate modifier: None RSIZE (or RECSIZE) specifies the maximum amount of information transferred between the Envoy line-handler process and the DLC (running in the SWAN concentrator) in one operation.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to BSC lines only. It specifies the first character of a station's select address. The address is defined by specifying the ASCII character or the octal equivalent of the ASCII character. This modifier is used only for tributary stations and is required for line operation.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions STOPBITON Default: STOPBITOFF Units: Not applicable Range: Not applicable Alternate modifier: STOPBITOFF This modifier applies to TINET, SIMPLEX, ADM, and ASC lines only. It specifies that an extra stop bit is generated. Each character has either 1.5 or 2 stop bits depending on the baud rate. SUBTYPE Default: None Units: Not applicable Range: Not applicable Alternate modifier: Not applicable This modifier identifies each Envoy line.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions SWITCH can be altered with a call to SETMODE 16. SWITCH appears when you specify the PPSW modifier. To remove SWITCH, specify the PPNSW modifier, the MPSUPV modifier, or the MPTRIB modifier. SYNCS n Default: 3 Units: Number of SYN characters Range: 0 to 15 Alternate modifier: None This modifier applies to BSC lines only. It specifies the number of leading SYN characters.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions Table 3-4.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions TPAUSE Default: Not specified Units: Not applicable Range: Not applicable Alternate modifier: None This modifier applies to SIMPLEX and ASC lines only. It causes the communications line interface processor (CLIP) to monitor for SCTS during data transmission. If the SCTS signal is present, the CLIP resumes transmission when SCTS is dropped.
WAN Subsystem Profiles and Modifiers for Envoy Modifier Descriptions This modifier applies to all Envoy line types. It specifies two units per logical line. Use the TWOUNIT modifier when configuring a BSC line connected to two units. TYPE Default: None Units: Not applicable Range: Not applicable Alternate modifier: Not applicable This modifier identifies each Envoy line. Table 3-2 on page 3-2 shows the TYPE and SUBTYPE values for Envoy lines. Envoy lines are always TYPE 7.
WAN Subsystem Profiles and Modifiers for Envoy Envoy Configuration and Management Manual—429861-001 3- 40 Modifier Descriptions
4 Subsystem Control Facility (SCF) for Envoy Envoy works with a user application to create a complete access method enabling Compaq systems to access I/O devices (such as ATMs). Each device is a station within a data communications network. This manual describes the SCF interface to the Envoy subsystem; it does not describe the SCF interface to the WAN subsystem. For information about the SCF interface to the WAN subsystem, see the WAN Subsystem Configuration and Management Manual.
Subsystem Control Facility (SCF) for Envoy Tasks You Can Perform Using SCF The Envoy subsystem has two objects: the LINE object, which represents the communications line, and the PROCESS object, which represents the line-handler process. These are described in further detail in Envoy Object Types and Names on page 4-6.
Subsystem Control Facility (SCF) for Envoy Changing a LINE Object Changing a LINE Object You can change line attributes by issuing SCF commands directly to the Envoy subsystem. These changes persist until you stop the DEVICE (in the WAN subsystem) associated with the line, until after a system load or processor reload, or until an application procedure call overrides the attributes.
Subsystem Control Facility (SCF) for Envoy SCF Commands SCF Commands Many SCF commands operate on the objects belonging to a subsystem. For example, you can use the INFO LINE command to display the current attribute values for an Envoy line, then use the ALTER LINE command to change those attribute values. Several commands display and change SCF line attributes. For example, the OUT command controls the files used for display output. The ASSUME command sets the default object type and object name.
Subsystem Control Facility (SCF) for Envoy Object States The full syntax of each subsystem-specific SCF command for Envoy is given in Section 5, Subsystem Control Facility (SCF) Commands for Envoy. The syntax of SCF commands that are not subsystem-specific is given in the SCF Reference Manual for G-Series Releases. SCF controls many data-communications subsystems whose individual components are objects. Each object has an object type and an object name.
Subsystem Control Facility (SCF) for Envoy Running SCF Running SCF SCF resides in the file $SYSTEM.SYSTEM.SCF. To start SCF, use the TACL RUN command. SCF can be run in either of two modes: interactive or noninteractive. For more information about the syntax of the RUN command and these two modes of operation, see the SCF Reference Manual for G-Series Releases.
Subsystem Control Facility (SCF) for Envoy Envoy Object States DEVICE For Envoy, the DEVICE object represents the line-handler process. Starting the DEVICE object in the WAN subsystem launches the line-handler process object in the Envoy subsystem. The line-handler process inherits the DEVICE object’s modifier and attribute definitions. The DEVICE object has attributes specifying how the DEVICE runs as a process, such as which CPU the process runs in and which concentrator the process uses.
Subsystem Control Facility (SCF) for Envoy Envoy Object States SUSPENDED An Envoy line enters the SUSPENDED state when the line-handling process cannot download CLIP code to the SWAN box successfully and if the line state was SUSPENDED or STARTED previously. In this state, if the line-handling process gets the controller power ON or processor power ON signal, it again downloads the CLIP code and tries to start the line. The SUSPENDED state supports a multi-system environment.
5 Subsystem Control Facility (SCF) Commands for Envoy This section describes the Subsystem Control Facility (SCF) interface to the Envoy subsystem and provides SCF command syntax. You should refer to the SCF Reference Manual for G-Series Releases for general information about running SCF. Table 5-1 identifies which SCF commands can be executed on which Envoy objects. Table 5-1.
Subsystem Control Facility (SCF) Commands for Envoy The WAN subsystem commands in Table 5-2 provide Envoy support in the WAN subsystem. Section 1, Configuration Quick Start provides examples of how several WAN subsystem commands are used to configure communications lines in Envoy. For detailed information concerning syntax and options for WAN subsystem commands, refer to the WAN Subsystem Configuration and Management Manual. Table 5-2.
Subsystem Control Facility (SCF) Commands for Envoy ABORT LINE Command ABORT LINE Command The ABORT command terminates the operation of objects as quickly as possible. Only enough processing is done to ensure the security of the subsystem. The object is left in the STOPPED state. This is a sensitive command. The command syntax is as follows: ABORT [ / OUT file-spec / ] [ LINE line-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Subsystem Control Facility (SCF) Commands for Envoy ADD DEVICE Command ADD DEVICE Command The WAN subsystem ADD DEVICE command provides a method for creating Envoy lines. This enables you to associate profiles with the process. See Profiles and Associated Protocols on page 3-1 for a selection of profile templates that you can use. The command syntax is as follows: ADD , , , , , , , , , , [, DEVICE $ZZWAN.#device_name IOPOBJECT $SYSTEM.SYSnn.
Subsystem Control Facility (SCF) Commands for Envoy ADD DEVICE Command RSIZE rsize specifies the record length in bytes. RSIZE (RECSIZE) specifies the maximum amount of information transferred between the Envoy line-handler process and the DLC (running in the SWAN concentrator) in one operation. The attribute is required for the WAN Manager program; however, the RSIZE value does not have any actual function in configuring an Envoy line handler process.
Subsystem Control Facility (SCF) Commands for Envoy ADD DEVICE Command Considerations • • Not all modifiers have associated values. The modifier_keyword and modifier_value parameters do not add the specified modifier, or a modifier and its associated value, to the profile used by the device. Use the ADD PROFILE command to add a modifier, or a modifier and its associated value, to a profile.
Subsystem Control Facility (SCF) Commands for Envoy ADD PROFILE Command ADD PROFILE Command To create a profile from the PENVBSC profile (or any of the other profiles for Envoy) provided by Compaq, use the WAN subsystem SCF ADD PROFILE command. The command syntax is as follows: ADD PROFILE $ZZWAN.#profile_name , FILE $SYSTEM.SYSnn.object_filename [, modifier_keyword [ modifier_value ] ] ... $ZZWAM.
Subsystem Control Facility (SCF) Commands for Envoy ALTER DEVICE Command ALTER DEVICE Command Use the WAN subsystem SCF ALTER DEVICE command to change the values of a data communications subsystem object, such as a modifier. The ALTER DEVICE command changes only the specified attributes of the target object. The command syntax is as follows: ALTER DEVICE $ZZWAN.
Subsystem Control Facility (SCF) Commands for Envoy ALTER DEVICE Command modifier-keyword [ modifier-value ] modifier-keyword and modifier-value specify product-specific characteristics for the DEVICE object. modifier-keyword specifies a keyword defined in profile-name, and modifier-value specifies a string of characters associated with the specified modifier-keyword. PATH path-name indicates which Ethernet path on the SWAN concentrator you prefer the device to use. The possible values are A or B.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE Command ALTER LINE Command The ALTER command changes the values of the attributes of a line. This command changes only the specified attributes of the target line. This is a sensitive command. The command syntax is as follows: ALTER [ / OUT file-spec / ] [ LINE line-name ] , attribute-set-spec { ASC | ASCBURPTP | ASCNET } { BSCBURPTP | BSCMPSUPV | BSCMPTRIB } { BSCPTP | FDX } [ , attribute-spec ]...
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE Command Table 5-3 and Table 5-4 show the ALTER attribute-set specifications for Envoy line types: Table 5-3. ALTER Attribute-Spec for Asynchronous Lines Envoy Line Type Subtype Driver/Protocol Alter Attribute Set ADM-2 multipoint supervisor 8 ASYNC/ADM2 ASCNET TINET multipoint supervisor 9 ASYNC/TINET ASCNET Burroughs multipoint 10 ASYNC/BURR ASCBURPTP ASC SIMPLEX 40 SIMPLEX/ASYNC ASC Table 5-4.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE ASC Command ALTER LINE ASC Command The attribute-spec for the ALTER LINE ASC command (asynchronous lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy. [ [ { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ CONNTYPE { PPSW | PPNSW } ] BAUD { 50 | 75 | 110 | 134.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE ASCBURPTP Command ALTER LINE ASCBURPTP Command The attribute-spec for the ALTER LINE ASCBURPTP command (Burroughs asynchronous point-to-point lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy. [ [ { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ CONNTYPE { PPSW | PPNSW } ] BAUD { 50 | 75 | 110 | 134.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE ASCNET Command ALTER LINE ASCNET Command The attribute-spec for the ALTER LINE ASCNET command (ADM2 or TINET asynchronous point-to-point lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy. [ { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ BAUD { 50 | 75 | 110 | 134.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE BSCBURPTP Command ALTER LINE BSCBURPTP Command The attribute-spec for the ALTER LINE BSCBURPTP command (Byte-synchronous Burroughs point-to-point lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE BSCMPSUPV Command ALTER LINE BSCMPSUPV Command The attribute-spec for the ALTER LINE BSCMPSUPV command (byte-synchronous multipoint supervisor or Burroughs multipoint supervisor lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE BSCMPTRIB Command ALTER LINE BSCMPTRIB Command The attribute-spec for the ALTER LINE BSCMPTRIB command (byte-synchronous multipoint tributary lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE BSCPTP Command ALTER LINE BSCPTP Command The attribute-spec for the ALTER LINE BSCPTP command (byte-synchronous point-topoint lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy.
Subsystem Control Facility (SCF) Commands for Envoy ALTER LINE FDX Command ALTER LINE FDX Command The attribute-spec for the ALTER LINE FDX command (standard full-duplex or NASDAQ full-duplex lines) is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 3, WAN Subsystem Profiles and Modifiers for Envoy.
Subsystem Control Facility (SCF) Commands for Envoy DELETE DEVICE Command DELETE DEVICE Command Use the WAN subsystem DELETE DEVICE command to remove the definition of a data communications subsystem object from the configuration database. The command syntax is as follows: DELETE DEVICE $ZZWAN.#device-name $ZZWAN.
Subsystem Control Facility (SCF) Commands for Envoy INFO Command INFO Command The INFO command displays the current values of the attributes for lines and adapters. This is not a sensitive command. The command syntax is as follows: INFO [ / OUT file-spec / [ LINE line-name | ADAPTER conc-name ] [ , DETAIL ] ] OUT file-spec directs SCF output generated for this command to the specified file. LINE line-name | ADAPTER conc-name specifies information for a particular line or adapter.
Subsystem Control Facility (SCF) Commands for Envoy INFO DEVICE Command INFO DEVICE Command Use the WAN subsystem INFO DEVICE command to display the static configuration attribute values for a data communications subsystem object. The command syntax is as follows: INFO [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , OUT file-spec ] DEVICE $ZZWAN.
Subsystem Control Facility (SCF) Commands for Envoy INFO DEVICE Command PATH specify this attribute to display only the SWAN concentrator PATH. PROFILE specify this attribute to display only the PROFILE object. RECSIZE specify this attribute to display only the RECSIZE attribute. TYPE for the INFO DEVICE command, specify this attribute to display only the type and subtype for the DEVICE. OBEYFORM causes the INFO command to display the information about the device in the form of ADD DEVICE commands.
Subsystem Control Facility (SCF) Commands for Envoy INFO DEVICE Command HIGHPIN indicates whether the data communications subsystem object is to be run highpin ON or OFF. The format of the display for the INFO DEVICE command with the DETAIL option is shown in Example 5-2. Example 5-2. INFO DEVICE DETAIL Command 8-> info device #asca,detail WAN MANAGER Detailed Info Device \IDC12.$ZZWAN.#ASCA *Adapter Name..... *Line ............ *Path ............ *RecSize.......... Alternate Cpu..... *HIGHPIN..........
Subsystem Control Facility (SCF) Commands for Envoy INFO DEVICE Command TRACEOFF causes the Envoy subsystem not to begin a trace when the Envoy line-handler process is started. DEDICATED causes Envoy to allocate a dedicated I/O buffer at process initialization. BUFSIZE used to dedicate a buffer.
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command INFO LINE Command Refer to the INFO Command on page 5-21 for the command syntax, field descriptions, and considerations. Examples The format of the display for the INFO LINE command without the DETAIL option is shown in Example 5-3. Example 5-3. INFO LINE Command 10-> info line $asca Envoy INFO LINE Name $ASCA Type/SubType (7 ,40) Recsize 512 DLC Type ASYNC Program $SYSTEM.CSS02.C0017P00 Name indicates the name of the line.
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command BSCMPTRIB FDX See ALTER LINE Command on page 5-10 for more information on the ALTER attribute sets. Example 5-4. INFO LINE DETAIL Command for ASC Alter Attribute Set 11-> info line $asca,detail Envoy Detail INFO LINE \IDC12.$ASCA Type/SubType..... DLC Type......... Program.......... Driver........... Interrupt Handler *Buffering Mode... (7 ,40) Recsize.......... ASYNC Number of Units.. $SYSTEM.CSS02.C0017P00 SIMPLEX Protocol.........
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command Driver indicates the name of the driver module. Protocol indicates the name of the communications protocol. Interrupt Handler indicates the interrupt handler being used. The term NO^SPECIAL listed next to Interrupt Handler indicates that the system’s interrupt handler is being used, rather than an Envoy interrupt handler. Buffering Mode indicates whether the mode of buffering is DEDICATED or POOLED.
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command No Parity Check indicates if no parity check is ON or OFF. Break Enable indicates if break enable is turned ON or OFF. TPause indicates whether the communications line interface processor (CLIP) should monitor for SCTS during data transmission. If the SCTS signal is present, the CLIP will resume transmission when SCTS is dropped.
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command Timeout specifies the processor input/output (I/O) timeout. Threshold specifies the statistics threshold value used to generate statistics events. Note. In the displays for the INFO command, an asterisk (*) indicates that the value of the attribute can be changed with the ALTER command.
Subsystem Control Facility (SCF) Commands for Envoy INFO LINE Command Table 5-5.
Subsystem Control Facility (SCF) Commands for Envoy INFO PROFILE Command INFO PROFILE Command Use the WAN subsystem INFO PROFILE command to return, for the specified PROFILE, a list of the DEVICE objects configured to use the profile and a list of the modifier keywords and corresponding modifier values contained in the profile. The command syntax is as follows: INFO [ , OUT file-spec ] PROFILE $ZZWAN.#profile-name [ , modifier-keyword [ modifier-keyword ] ]...
Subsystem Control Facility (SCF) Commands for Envoy INFO PROFILE Command Example 5-5. INFO PROFILE Command 12-> info profile #penvsim WAN MANAGER Info profile \IDC12.$ZZWAN.#PENVSIM Devices using this profile Device.......... 1 : $ASCA DEVICE SPECIFIC MODIFIERS: ONEUNIT INSPECTOFF EMSOFF TRACEOFF DEDICATED BUFSIZE 1024 CHECK DSRSENSEON . . . . . Following are definitions for the display fields not defined under the command syntax: DEVICE SPECIFIC MODIFIERS: ONEUNIT specifies one unit per logical line.
Subsystem Control Facility (SCF) Commands for Envoy INFO PROFILE Command DEDICATED causes Envoy to allocate a dedicated I/O buffer at process initialization. CHECK enables incoming message parity checking. DSRSENSEON enables DSRSENSE capability. The loss of the DSR modem signal is sensed and reported as an error during a READ or WRITE operation.
Subsystem Control Facility (SCF) Commands for Envoy NAMES Command NAMES Command The NAMES command returns a list of the subordinate object types and names for the specified object. This is not a sensitive command. The command syntax is as follows: NAMES [ / OUT file-spec / ] [ PROCESS process-name | LINE line-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS process-name | LINE line-name designates the process or line to be displayed.
Subsystem Control Facility (SCF) Commands for Envoy NAMES DEVICE Command NAMES DEVICE Command The WAN subsystem NAMES DEVICE command displays a list of the names of all configured data communications subsystem objects. The command syntax is as follows: NAMES DEVICE $ZZWAN.#device-name $ZZWAN.#device-name indicates the name of the DEVICE object in the configuration database and is also the name of the corresponding data-communications subsystem object, as specified in the ADD DEVICE command.
Subsystem Control Facility (SCF) Commands for Envoy NAMES LINE Command NAMES LINE Command Refer to the NAMES Command on page 5-35 for the command syntax, field descriptions, and considerations. Example The format of the display for the NAMES LINE command is shown in Example 5-8. Example 5-8. NAMES LINE Command 35-> names line $asca ENVOY Names LINE \IDC12.$ASCA LINE \IDC12.
Subsystem Control Facility (SCF) Commands for Envoy NAMES PROCESS Command NAMES PROCESS Command Refer to the NAMES Command on page 5-35 for the command syntax, field descriptions, and considerations.
Subsystem Control Facility (SCF) Commands for Envoy PRIMARY PROCESS Command PRIMARY PROCESS Command The PRIMARY command causes the backup CPU to become the primary CPU, and the primary CPU to become the backup CPU. This is a sensitive command. The command syntax is as follows: PRIMARY [ / OUT file-spec / ] [ PROCESS process-name ] , number OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS process-name designates the process to be switched.
Subsystem Control Facility (SCF) Commands for Envoy START DEVICE Command START DEVICE Command To start a line-handler process, use the WAN subsystem SCF START DEVICE command. This command creates the specified Envoy line-handler process and allocates a logical device (LDEV) number. The command syntax is as follows: START DEVICE $ZZWAN.#device_name $ZZWAN device_name is the device name of the Envoy line-handler process. Considerations • • • Envoy does not support the SEL or SUB options.
Subsystem Control Facility (SCF) Commands for Envoy START LINE Command START LINE Command The START LINE command initiates the operation of an line. The successful completion of the START LINE command leaves the line in the STARTED state. This is a sensitive command. The command syntax is as follows: START [ / OUT file-spec / ] [ LINE line-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name designates the line to be started.
Subsystem Control Facility (SCF) Commands for Envoy STATS LINE Command STATS LINE Command The STATS command displays statistical information about the execution history of lines. It shows dynamic information such as the number of messages sent and received and the number of format errors. In addition to the statistical information, Envoy returns a timestamp to show the time the sample was taken. This is not a sensitive command. To issue the STATS command, first you need the name of the line.
Subsystem Control Facility (SCF) Commands for Envoy STATS LINE Command The following command resets statistics counters for the line $ASCA: -> STATS LINE $ASCA, RESET The format of the display for the STATS LINE command is shown in Example 5-10. Example 5-10. STATS LINE Command 21-> stats line $asca ENVOY Stats LINE \IDC12.$ASCA Sampletime........ 04 Aug 2000, 18:43:10.360 Resettime......... 04 Aug 2000, 18:39:04.853 Msgs Sent......... Blks Inuse Hi Cnt. Naks Received..... Format Errors..... Retries.....
Subsystem Control Facility (SCF) Commands for Envoy STATS LINE Command BCC Errors shows the total number of block-check character (BCC) errors detected by Envoy. Format Errors shows the number of format errors detected by Envoy between the last reset and the current sample time. Text Errors shows the total number of times a framing error occurred. Retries shows the number of times a retry occurred. No Blks shows the number of times that no buffer space was available.
Subsystem Control Facility (SCF) Commands for Envoy STATUS DEVICE Command STATUS DEVICE Command The WAN subsystem STATUS DEVICE command displays current status and configuration information about a data communications subsystem object. The command syntax is as follows: STATUS DEVICE $ZZWAN.#device-name $ZZWAN.
Subsystem Control Facility (SCF) Commands for Envoy STATUS LINE Command STATUS LINE Command The STATUS command displays information about the current state of lines, such as the dynamic state, the backup I/O address, and other relevant subsystem-specific attributes and values. This is not a sensitive command. The command syntax is as follows: STATUS [ / OUT file-spec / ] [ LINE line-name ] [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Subsystem Control Facility (SCF) Commands for Envoy STATUS LINE Command PPID is the CPU number and PIN of the primary Envoy I/O process. CLIP clipnum is the communications line interface processor (CLIP) on the SWAN concentrator specified by concname. LINE linenum is the line number (0 or 1) on the selected CLIP specified by clipnum. BPID is the CPU number and PIN of the backup Envoy I/O process. Track Id is the unique number that represents a SWAN concentrator box.
Subsystem Control Facility (SCF) Commands for Envoy STATUS LINE Command CMG Ldev indicates the logical device number of the DEVICE object in the configuration database. CMG indicates the name of the DEVICE object in the configuration database and is also the name of the corresponding data communications subsystem object, as specified in the ADD DEVICE command. Preferred IP indicates the preferred IP address. Alternate IP indicates the alternate IP address.
Subsystem Control Facility (SCF) Commands for Envoy STOP DEVICE Command STOP DEVICE Command The WAN subsystem STOP DEVICE command stops a data communications subsystem object. The command syntax is as follows: STOP DEVICE $ZZWAN.#device-name device-name indicates the name of the DEVICE object in the configuration database and is also the name of the corresponding data communications subsystem object, as specified in the ADD DEVICE command.
Subsystem Control Facility (SCF) Commands for Envoy STOP LINE Command STOP LINE Command The STOP command terminates the operation of lines in a normal manner. Upon the successful completion of the STOP command, objects are left in the STOPPED state. This is a sensitive command. The command syntax is as follows: STOP [ / OUT file-spec / ] [ LINE line-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Subsystem Control Facility (SCF) Commands for Envoy TRACE LINE Command TRACE LINE Command The TRACE command initiates, modifies, or terminates the trace mode on an Envoy line. Using the TRACE command, you can request the capture of target-defined data items, alter trace parameters, and end tracing. This is a sensitive command. An SCF trace produces a trace file that you can display using the commands available in the PTrace program. SCP creates the trace file.
Subsystem Control Facility (SCF) Commands for Envoy TRACE LINE Command COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If you omit COUNT or if count equals -1, records accumulate until the line trace is stopped. The trace can be stopped by the user, or if WRAP is not specified, when the file is full. NOCOLL indicates that the trace collector process should not be initiated.
Subsystem Control Facility (SCF) Commands for Envoy TRACE LINE Command WRAP specifies that when the trace disk file end-of-file mark is reached, trace data wraps around to the beginning of the file and overwrites any data there. If WRAP is omitted, the trace stops when the end-of-file mark is reached. Table 5-6. Select Specification for a LINE Object (page 1 of 2) Keyword Value Enables tracing of...
Subsystem Control Facility (SCF) Commands for Envoy TRACE LINE Command Table 5-6. Select Specification for a LINE Object (page 2 of 2) Keyword Value Enables tracing of...
Subsystem Control Facility (SCF) Commands for Envoy TRACE LINE Command The following command traces the backup process of the line named $ENVY: -> TRACE LINE $ENVY, BACKUP, TO TRCBACK, SELECT ALL & RECSIZE 256, WRAP Envoy Configuration and Management Manual—429861-001 5- 55
Subsystem Control Facility (SCF) Commands for Envoy VERSION Command VERSION Command The VERSION command displays the version level of the specified object. This is not a sensitive command. The command syntax is as follows: VERSION [ / OUT file-spec / ] object-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. object-name designates the object whose version you want to display.
Subsystem Control Facility (SCF) Commands for Envoy VERSION Command GUARDIAN - T9050 - (Q06) T9050 shows the version number of the Guardian Operating System. The Q06 is an internal version number. SCF KERNEL - T9082G02 - (26JUN00) (20MAR00) T9082G02 shows the product and version number as the SCF kernel. 26JUN00 is the VPROC (version process) date. 20MAR00 is the binder stamp date. ENVOY PM - T9679G03 - (04NOV98) - (0.21) T9679G03 shows the product and version number of the ENVOY SCF Product Module.
Subsystem Control Facility (SCF) Commands for Envoy Envoy Configuration and Management Manual—429861-001 5- 58 VERSION Command
6 Tracing This section describes the PTrace interface, command syntax, and fields of sample trace records.
Tracing Recording and Displaying Trace Data Recording and Displaying Trace Data Trace files contain a record of the communications between processes. Each subsystem determines what information is recorded in its trace files. The type of events recorded, the amount of detail, and the subsystem-specific parameters may vary. You generate a trace file using the SCF TRACE command. The trace files that SCF creates are unstructured and cannot be printed or displayed directly.
Tracing Determining the Subsystem 1. The following general description of the steps involved in recording and displaying trace data specifies a page size of and a record size of 256. -> TRACE LINE $ENVY1, TO MYFILE, SELECT (EVYALL) & PAGES 64, RECSIZE 256 The PAGES option indicates that there are 64 units of space in the extended data segment. The RECSIZE option indicates that there is a maximum of 256 bytes of data in a trace data record. 2.
Tracing PTrace Commands for Envoy Table 6-1. Summary of PTrace Commands Common to All Subsystems (page 2 of 2) Command Description FC (Fix Command) Allows the last PTrace command line entered to be corrected. FIND Searches the formatted output for a specified string. Fn Performs a NEXT command. (Any Compaq 6530 function key) FROM Specifies the trace file to be displayed. HELP Displays information about PTrace commands. HEX Displays numbers in hexadecimal notation.
Tracing FROM Command Table 6-2. PTrace Commands for Envoy Command Description FROM Command on page 6-5 Specifies the trace file to be displayed. NEXT Command on page 6-6 Displays the next trace data record(s) in the trace file. RECORD Command on page 6-6 Displays the record(s) selected by record number. SELECT Command on page 6-7 Establishes selection criteria for displaying trace records.
Tracing • • NEXT Command The FROM command automatically displays the trace-file header record (record 0) when it opens the new trace file. The FROM command does not close a log file if one is specified. NEXT Command The NEXT command displays records starting from the next record in the trace file. The number of records displayed by a single NEXT command never exceeds the number set by the LIMIT command. Records that do not meet the current selection criteria are not counted and are not displayed.
Tracing SELECT Command first is an integer that specifies the record number of the first, or only, record to be displayed. last is an integer that specifies the record number of the last record in a range of records to be displayed. ALL specifies that all records in the trace file are to be displayed. Considerations • • • The first record in the trace file, the trace-file header record, is record number 0. The first data record is record number 1.
Tracing SELECT Command number is an integer that specifies an enumerated value corresponding to a specific keyword. number can be specified in decimal, octal, hexadecimal, or binary notation. When you specify a number, the number is saved as an enumerated value. The formats and ranges are listed as follows: decimal: 0 - 32767 octal: %0 - %7777 hexadecimal: %H0 - %H7FFF binary: %B0 - %B11111111111111 keyword is one of the keywords listed in Table 6-3. Table 6-3 lists the valid SELECT keywords. Table 6-3.
Tracing STATETABLES Command Table 6-3. Select Option Keywords for Envoy (page 2 of 2) Keyword Value Enables tracing of...
Tracing Trace Examples Trace Examples The following steps will create a useful sample trace file: 1. Stop the Envoy line. STOP LINE 2. Start the line. START LINE 3. Start the trace by using the SCF TRACE command and specify SELECT ALL, PAGES 64, WRAP. TRACE LINE $LDEV, TO filename, SELECT ALL, PAGES 64, WRAP 4. Wait for the Envoy line-ready console message. 5. Stop the trace. TRACE LINE $LDEV, STOP 6. Use PTrace to format and display the trace records. Note.
A Envoy Subsystem Error Messages This section describes network-related operator console and common file-system error messages, such as those that might occur because of a typographical error. All subsystem-specific SCF error messages returned by the Envoy subsystem are listed and described. These errors all have positive error numbers. Errors returned by the Envoy subsystem that have negative numbers are SCF errors common to all subsystems.
Envoy Subsystem Error Messages About Envoy Errors About Envoy Errors Each error listed includes a description of the probable cause of the error condition, an explanation of the effect of the error, and a recommended recovery action. Error messages are listed in numerical order. The user can receive error messages through SCF. The messages are generated by the file system, SCP, and so forth.
Envoy Subsystem Error Messages E00009 E00009 ENVOY E00009 Bounds error. Cause. The command is not being issued in the correct summary state with the line. Effect. The command is rejected. Recovery. Change the line summary state to a correct state and retry the command. E000011 ENVOY E000011 Alter command rejected; attribute attr conflicts with adapter type. Cause. ALTER command rejected; attribute conflicts with adapter type. Effect. The attribute will not be changed to the new value that you entered.
Envoy Subsystem Error Messages E000014 E000014 ENVOY E000014 Alter command rejected; attribute attr value is not supported. Cause. ALTER command rejected; attribute attr value is not supported. Effect. The attribute will not be changed to the new value that you entered. Recovery. Make sure that the correct value is being specified for the attribute. E000015 ENVOY E000015 Alter command rejected; the attribute set name specified is invalid for this line. Cause.
B Envoy Event Messages This section describes the content and meaning of all event messages generated by the Envoy subsystem. In this section, object types and all tokens and their values are represented in Data Definition Language (DDL). Subsystem Processes That Report Events The Envoy subsystem process generates its own event messages, common data communications (ZCOM) event messages, and common diagnostic ZCDG event messages. Table B-1 lists the event messages defined by Envoy. Table B-1.
Envoy Event Messages ZENV Subsystem ID Table B-2 lists the Envoy-generated event messages defined by other subsystems. Table B-2. Envoy Event Messages Defined by Other Subsystems Event Number and Symbolic Name Description -00003: ZCOM-EVT-SUMSTATE-CHANGE A line state transition has occurred. -00001: ZCOM-EVT-CPU-SWITCH The backup I/O PROCESS has become the primary I/O PROCESS. -10003: ZCDG-EVT-PON-INTRPT A power-on interrupt was detected.
Envoy Event Messages Event-Message Descriptions Table B-3. Header Tokens That Appear in All Envoy Event Messages (page 2 of 2) Header Tokens Token Type ZEMS-TKN-PIN UINT ZEMS-TKN-SYSTEM UINT ZEMS-TKN-USERID BYTE-PAIR The data-portion tokens that appear in all Envoy event messages are listed in Table B-4. Table B-4.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS the display format text is the same as the console-compatible format. For further information on the EMSTEXT procedure, event-message text formats, and the standard event-message header, refer to the EMS Manual. The event-message text box is followed by descriptions of the event-message tokens, which are defined in the same order as they appear in the box. The descriptions of simple tokens in this section do not identify the token numbers of the tokens.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS Token Descriptions ZEMS-TKN-EMPHASIS Has the value TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT Has the value FALSE, indicating that this event message is not routed to the operator console. ZENV-TKN-ABENDCODE Each abend code is followed by its possible causes and the error-dependent portion for each abend code. Conditional tokens returned for each abend code are also listed.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS ZENV-VAL-ABEND-DEF-POOL A call to DEFINEPOOL to define local pool space has failed. The errordependent portion of the message displays the requested pool size: Return Error #error number ZENV-VAL-ABEND-DEVTYPE The device type specified for the line is not an Envoy type 7.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS ZENV-VAL-ABEND-INTHDLR-DRV The special interrupt handler specified for the line does not work with the specified driver. The error-dependent portion of the message displays the interrupt handler name and driver name: Interrupt Handler interrupt handler Driver driver ZENV-VAL-ABEND-LOCK-MEM Unable to lock memory.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS ZENV-VAL-ABEND-OMR-GET Unable to get OMR through IOPRM. The error-dependent portion of the message displays the error number: Returned Error #error number ZENV-VAL-ABEND-PROCESS-INFO Unable to get Envoy phandle. The error-dependent portion of the message displays the error number: Returned Error #error number ZENV-VAL-ABEND-UNITS-ERR For a line defined with two units, the I/O process was not able to locate the Write and Read unit pairs.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS SCOM6201INTERRUPT^NAQ SCOM6201INTERRUPT ASYNC^INTERRUPT ZENV-VAL-ABEND-UNKWN-PROTO An unknown protocol handler was defined for the line. There is no errordependent portion. The possible protocol handlers are: ADM2^PROTOCOL ASYNC^PROTOCOL BSC^PROTOCOL BURROUGHS^PROTOCOL FDX^PROTOCOL SWIFT^PROTOCOL TINET^PROTOCOL ZENV-BAL-ABEND-USE-SEG A call to use the IOPRM segment failed. The error dependent portion of the message displays the segment number.
Envoy Event Messages 5: ZENV-EVT-IOPROCABENDMESS ZENV-TKN-INT-NAME Contains the enumerated value indicating the interrupt handler name. ZENV-TKN-NUM-UNITS Contains the number of units. ZENV-TKN-POOL-SIZEB Contains the pool size in bytes. ZENV-TKN-SU-TYPE Identifies whether device is IOPRM device or subdevice. ZENV-TKN-SEG-NO Identifies IOPRM segment number. ZENV-TKN-RET-STATUS Contains the return status from a call.
Envoy Event Messages 6: ZENV-EVT-INTERNALERRMESS 6: ZENV-EVT-INTERNALERRMESS This is a critical event. An internal error was detected. The affected Envoy process terminates abnormally. This event is equivalent to pre-EMS console message 74.
Envoy Event Messages 6: ZENV-EVT-INTERNALERRMESS ZENV-TKN-INTL-ERR-CODE Each internal error code is followed by its possible causes: ZENV-VAL-INTL-ALLOC-SEG A call to ALLOCATESEGMENT failed. The error-dependent portion of the message displays the return status from the call to ALLOCATESEGMENT, the segment to be allocated, and the segment size: Status ret status Segment No segment number Segment Size segment size Bytes ZENV-VAL-INTL-BAD-ACT-ROUTINE The action routine malfunctioned.
Envoy Event Messages 6: ZENV-EVT-INTERNALERRMESS ZENV-VAL-INTL-LOCK-MEM A call to LOCKMEMORY failed. The error-dependent portion of the message displays the return status from the call to LOCKMEMORY, the segment number, and the size of the segment: Status ret status Segment No. segment number Segment Size segment size Bytes ZENV-VAL-INTL-NO-DEDICATED-BUF A dedicated buffer was not specified for the line. There is no error-dependent portion for the message.
Envoy Event Messages 6: ZENV-EVT-INTERNALERRMESS ZENV-TKN-SM-STATE Contains the state number. ZENV-TKN-SM-EVENT Contains the event number. ZENV-TKN-SM-MAPPED-EVENT Contains a mapped event number. ZENV-TKN-UNKWN-EVT Received an event from IOPRM. ZENV-TKN-CASE-SELECTOR Contains the case selector number.
Envoy Event Messages 1000: ZENV-EVT-UNKWN 1000: ZENV-EVT-UNKWN This is a critical event. The generation of an unknown or undefined event was requested.
Envoy Event Messages 1001: ZENV-EVT-BADEIOSTATUS ZENV-TKN-PREGISTER Contains the P-register (program counter) at the time. Probable Cause The generation of an event unknown to the process was requested. System Action None. Recovery Report the event to your Compaq representative. 1001: ZENV-EVT-BADEIOSTATUS This is a critical event. The Envoy subsystem detected an error while issuing an EIO. The affected Envoy process terminates abnormally, then a CPU switch occurs.
Envoy Event Messages 1001: ZENV-EVT-BADEIOSTATUS Token Descriptions ZEMS-TKN-EMPHASIS Has the value TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT Has the value FALSE, indicating that this event message is not routed to the operator console. ZEMS-MAP-EXIOADDR Contains the physical I/O address. ZCDG-TKN-EIO-LAC Contains the EIO command word. ZCDG-TKN-EIO-LPRM Contains the EIO LPRM status. ZCDG-TKN-EIO-RDST Contains the EIO device status.
Envoy Event Messages 1001: ZENV-EVT-BADEIOSTATUS ZENV-VAL-DRV-REQ-SEL ZENV-VAL-DRV-REQ-FREE-BLK ZENV-VAL-DRV-REQ-STOP-RD ZENV-VAL-DRV-REQ-SET-RD ZENV-VAL-DRV-REQ-GET-LB-INFO ZENV-VAL-DRV-REQ-GET-AB-INFO ZENV-VAL-DRV-REQ-GET-MCODE-ID ZENV-VAL-DRV-REQ-OWN-DELAY Probable Cause An EIO error was detected. File-system error numbers must be in the range 214 through 225. The following errors are possible: • FECHTIMEOUT = 214 Channel timeout.
Envoy Event Messages 1002: ZENV-EVT-BADIIOSTATUS 1002: ZENV-EVT-BADIIOSTATUS This is a critical event. An interrupt error occurred. The affected Envoy process terminates abnormally. This event and the preceding event (ZENV-EVTBADEIOSTATUS) are equivalent to pre-EMS console message 3.
Envoy Event Messages 1002: ZENV-EVT-BADIIOSTATUS ZCDG-TKN-IIO-RIST Contains the interrupt status word. RIST is the Read Interrupt Status word. ZCDG-TKN-RESIDUE Contains the residue transfer count. ZENV-TKN-FILE-ERR Contains the file-system error code.
Envoy Event Messages • 1002: ZENV-EVT-BADIIOSTATUS FEMEMPARITY = 217 Memory parity error during this I/O. • FEINTTIMEOUT = 218 Interrupt timeout occurred. • FEILRECON = 219 Illegal device reconnect received. • FEPROTECT = 220 Protection violation detected. • FEHANDSHAKE = 221 Controller handshake violation (path error) • FEBADIIOSTAT = 223 Bad channel status from I/O instruction. • FECTLERR = 224 Controller error. System Action A CPU switch occurs.
Envoy Event Messages 1003: ZENV-EVT-BADIIOCAUSE 1003: ZENV-EVT-BADIIOCAUSE This is a critical event. An interrupt was detected upon the completion of a data transfer I/O, and the cause of the interrupt contained an interrupt cause which was not expected. The affected Envoy process terminates abnormally. This event is equivalent to pre-EMS console message 4.
Envoy Event Messages 1003: ZENV-EVT-BADIIOCAUSE Token Descriptions ZEMS-TKN-EMPHASIS Has the value TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT Has the value FALSE, indicating that this event message is not routed to the operator console. ZEMS-MAP-EXIOADDR Contains the physical I/O address. ZCDG-TKN-IIO-RIC Contains the expected interrupt cause word. ZCDG-TKN-RESIDUE Contains the residue transfer count. ZENV-TKN-FILE-ERR Contains the file-system error code.
Envoy Event Messages 1004: ZENV-EVT-STATS-LINE ZENV-TKN-EXP-IIO-DATA-RIC Contains the expected data interrupt cause word for asynchronous controllers only. ZENV-TKN-EXP-IIO-MODEM-RIC Contains the expected modem interrupt cause word for asynchronous controllers only. Probable Cause A communications line error (such as a loss of modem signals) was detected. System Action None. Recovery Not applicable. Considerations This event is equivalent to the EMS-defined common event ZEMS-EVT-ERRORMESS.
Envoy Event Messages 1004: ZENV-EVT-STATS-LINE Event-Message Text Timestamp \system.pid TANDEM.ENVOY.F40 Event number TANDEM.ENVOY.F40 \ system.
Envoy Event Messages 1005: ZENT-EVT-TRACE ZENV-MAP-STATS-LINE Contains statistics information. Conditional Token Descriptions ZEMS-MAP-EXIOADDR Contains the physical I/O address. Probable Cause Communications line errors have exceeded the designated threshold value (or were closed, and non-zero device statistics were recorded). System Action None. Recovery Not applicable. Considerations • • • • This event is an Envoy-defined event.
Envoy Event Messages 1005: ZENT-EVT-TRACE Event-Message Text Timestamp \system.pid TANDEM.ENVOY.F40 Event number TANDEM.ENVOY.F40 \ system.line name LDEV ldev Trace status ENVOY Trace Types: %177777 %177777 IOPRM Trace Types: %377 Status: 0 0 Token Descriptions ZEMS-TKN-EMPHASIS Has the value FALSE, indicating that this is a noncritical event. ZEMS-TKN-CONSOLE-PRINT Has the value FALSE, indicating that this event message is not routed to the operator console.
Envoy Event Messages 1006: ZENV-EVT-CONFIG-CHG 1006: ZENV-EVT-CONFIG-CHG This is a noncritical event. This event indicates that the configuration parameters have been modified.
Envoy Event Messages 1006: ZENV-EVT-CONFIG-CHG ZENV-VAL-CONFIG-INT The interrupt configuration has been changed. ZENV-VAL-CONFIG-PROTO The protocol configuration has been changed. ZENV-VAL-CONFIG-DEDICATED The dedicated buffer configuration has been changed. Conditional Token Descriptions ZENV-TKN-BUF-SIZEW Contains the old value of the dedicated buffer. ZENV-TKN-BUF-SIZEW-NEW Contains the new value of the dedicated buffer. ZENV-TKN-DRV-NAME Contains the old driver name.
Envoy Event Messages -00003: ZCOM-EVT-SUMSTATE-CHANGE Recovery Not applicable. Considerations This event is an Envoy-defined event. -00003: ZCOM-EVT-SUMSTATE-CHANGE This is not a critical event. A line state transition has occurred.
Envoy Event Messages -00003: ZCOM-EVT-SUMSTATE-CHANGE ZCOM-TKN-OLD-OBJSTATE Contains the previous summary state of the process, which could be one of the following values: ZCOM-VAL-SUMSTATE-STOPPED ZCOM-VAL-SUMSTATE-STARTED ZCOM-TKN-CAUSE-SUMSTATE-CHG Indicates the cause of the state change, which could be one of the following values: ZCOM-VAL-HW Hardware-caused state change ZCOM-VAL-OP-REQ Operator-request state change ZCOM-VAL-UKWN Unknown cause ZEMS-MAP-EXIOADDR Contains the physical I/O address.
Envoy Event Messages -00001: ZCOM-EVT-CPU-SWITCH -00001: ZCOM-EVT-CPU-SWITCH This is a noncritical event. The backup I/O PROCESS has become the primary I/O PROCESS.
Envoy Event Messages -10003: ZCDG-EVT-PON-INTRPT ZCOM-VAL-OP-REQ Operator requested a switch. ZCOM-VAL-TAKOVR A take over by the primary caused a switch. ZCOM-VAL-UKNWN Unknown cause. ZEMS-MAP-EXIOADDR contains the physical I/O address. Probable Cause The primary I/O PROCESS has received an operator-initiated request to switch CPUs and has successfully executed the request or has detected an EIO error. Ownership has been given to the backup process.
Envoy Event Messages -10003: ZCDG-EVT-PON-INTRPT Event-Message Text Timestamp TANDEM.ENVOY.F40 Event number Controller Powered On. Device: \ system.line name Token Descriptions ZEMS-TKN-EMPHASIS Has the value FALSE, indicating that this is a noncritical event. ZEMS-MAP-EXIOADDR Contains the physical I/O address. Probable Cause An I/O power-on interrupt was detected. System Action The I/O PROCESS executes its I/O power-on interrupt-processing logic. Recovery Not applicable.
C Envoy SCF Command Syntax Summary This appendix summarizes the SCF command syntax for Envoy. Commands are listed in alphabetical order. ABORT [ / OUT file-spec / ] [ LINE line-name ] ADD , , , , , , , , , , [, DEVICE $ZZWAN.#device_name IOPOBJECT $SYSTEM.SYSnn.OENVOY PROFILE profile_name CPU cpunumber ALTCPU altcpunumber TYPE (n,n) RSIZE rsize ADAPTER concname CLIP clipnum LINE linenum PATH { A | B } modifier_keyword [ modifier_value ] ] ... ADD PROFILE $ZZWAN.#profile_name , FILE $SYSTEM.SYSnn.
Envoy SCF Command Syntax Summary ALTER [ / OUT file-spec / ] [ LINE line-name ] , attribute-set-spec { ASC | ASCBURPTP | ASCNET } { BSCBURPTP | BSCMPSUPV | BSCMPTRIB } { BSCPTP | FDX } [ , attribute-spec ]... DELETE DEVICE $ZZWAN.#device-name INFO [ / OUT file-spec / [ LINE line-name | ADAPTER conc-name ] [ , DETAIL INFO [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , ] ] , OUT file-spec ] DEVICE $ZZWAN.
Envoy SCF Command Syntax Summary PRIMARY [ / OUT file-spec / ] [ PROCESS process-name ] , number START DEVICE $ZZWAN.#device_name START [ / OUT file-spec / ] [ LINE line-name ] STATS [ / OUT file-spec / ] [ LINE line-name ] [ , RESET ] STATUS DEVICE $ZZWAN.#device-name STATUS [ / OUT file-spec / ] [ LINE line-name ] [ , DETAIL ] STOP DEVICE $ZZWAN.#device-name STOP [ / OUT file-spec / ] [ LINE line-name ] TRACE [ / OUT file-spec / ] [ LINE line-name ] { , STOP [ , BACKUP ] } { {, trace-option}...
Envoy SCF Command Syntax Summary Envoy Configuration and Management Manual—429861-001 C- 4
D S-Series Changes to Envoy The NonStop Himalaya S-series server architecture affects I/O processes such as Envoy because a single data-communications concentrator replaces all former communications controllers. In addition, the management subsystem that controls the concentrator required changes to configuration operations. These basic changes mostly affect SYSGEN configuration and SCF.
S-Series Changes to Envoy LEOTRESYN and NOLEOTRESYN Modifiers Set CBSENSEOFF and CFSENSEOFF if monitoring of MODEM signals is not needed while a READ is in progress. LEOTRESYN and NOLEOTRESYN Modifiers D-series versions of Envoy Supports both LEOTRESYN and NOLEOTRESYN. G-series versions of Envoy Supports only LEOTRESYN. It does not support NOLEOTRESYN.
S-Series Changes to Envoy Reporting of Parity Error Reporting of Parity Error D-series versions of Envoy The 3603 controller does not return parity error. G-series versions of Envoy When data is received with parity error, error 120 is reported to the application. Half-Duplex Support for Asynchronous Lines D-series versions of Envoy Asynchronous lines can be either FULL or HALF duplex. G-series versions of Envoy HALF duplex is not supported for asynchronous lines.
S-Series Changes to Envoy Unit Numbers Unit Numbers While adding the device, unit number is not required, except for lines of subtype 30, 31, 32 and 33. FDX Line Changes Starting from this release, FDX lines (Write and Read) need to be MULTIed on a single line of any CLIP so as to get the same effect as that of COUPing these lines on units n and n+1 of a 3602 controller (where n = 0, 2, 4, 6) No Support for Auto-Call Unit ACU is not supported in G-series releases.
Glossary $ZZLAN. The process name of the ServerNet LAN systems access (SLSA) subsystem manager process that is started by the $ZZKRN Kernel subsystem manager process and maintained by the $ZPM persistence manager process. See also LAN manager (LANMAN) process. $ZZWAN. The process name of the wide area network (WAN) subsystem manager process. 3602. A communications controller supporting Envoy byte-synchronous protocols in CLX and Cyclone systems. This controller works only with Envoy. 3603.
Glossary Burroughs Point-to-Point Protocol. Burroughs Point-to-Point Protocol. A protocol that enables an application process to act as a station in a Burroughs dedicated point-to-point contention network. byte-synchronous data transmission (BISYNC). A data communications environment in which stations synchronize with each other by means of synchronous idle (SYN) characters. The stations communicate by using a standard set of control characters and control character sequences.
Glossary data link control (DLC). data link control (DLC). A set of functions associated with Layer 2 of the Open Systems Interconnection (OSI) reference model. These functions are responsible for reliable communication between two physically connected nodes. data link control (DLC) task. WAN DLC tasks support the equivalent to level 2 of the ISO/OSI Seven-Layer Model. The WAN DLC tasks execute in the SWAN concentrator communications line interface processor (CLIP).
Glossary Electronics Industries Association (EIA) interface standard RS-232-B or C. Electronics Industries Association (EIA) interface standard RS-232-B or C. A standardized method adopted by the Electronic Industries Association to ensure uniformity of interface between data communications equipment and data processing terminal equipment. This standard has been generally accepted in business equipment. See also RS-232. EMS. See Event Management Service (EMS). end of text (EOT; ETX).
Glossary Guardian Guardian. An environment available for interactive or programmatic use with the NonStop Kernel. Processes that run in the Guardian environment use the Guardian system procedure calls as their application program interface. half-duplex. A method of serial communications in which the data flow between two points can occur in only one direction at a time. This concept refers to the physical capability of the line. high PIN. A PIN that is greater than 255. See also low PIN.
Glossary local area network (LAN) local area network (LAN). A network that is located in a small geographical area and whose communications technology provides a high-bandwidth, low-cost medium to which low-cost nodes can be connected. One or more LANs can be connected to the system such that the LAN users can access the system as if their workstations were connected directly to it. logical device number. A number that identifies a particular I/O device in the system.
Glossary persistence. name. The object type describes the type of the object, such as LINE, SU (subdevice), PROCESS, and so forth. The object name uniquely identifies an object within the system. persistence. For the Subsystem Control Facility (SCF), the capability of a generic process to restart automatically if it was stopped abnormally. You configure this capability by specifying a nonzero AUTORESTART value in an ADD command. point-to-point. A data-link configuration between two stations.
Glossary select address. select address. Specifies the address that must be transmitted by a multipoint supervisor station to send data to a multipoint tributary station. sensitive command. One that can be issued only by a user with super-group access, by the owner of the subsystem, or by a member of the group of the owner of the subsystem.
Glossary Subsystem Programmatic Interface (SPI). features, version compatibility, support for tracing, and support for applications implemented as process pairs. Subsystem Programmatic Interface (SPI). A common, message-based interface that can build and decode messages used for communication between requesters (for example, a management application) and servers (Compaq subsystems). supervisor. The controlling station in a centralized, multipoint, data link. SWAN concentrator.
Glossary WAN subsystem WAN subsystem. The WAN subsystem is used to configure and manage I/O processes and provides access to the SWAN concentrator. The WAN subsystem consists of several components including the WAN manager process, the ConMgr and WANBoot processes, and the WAN subsystem SCF interface. wide area network (WAN). A communication system that connects geographically dispersed sites or local area networks (LANs).
Index Numbers 10Base-T Ethernet connections 2-3 3602 byte-synchronous controller 2-3, D-1 3602 controller emulator 2-3 3603 asynchronous controller 2-3, D-1 3603 controller emulator 2-3 A ABORT command 5-3 ACKOFF modifier 3-8 ACKON modifier 3-8 ADD ADAPTER command 1-4 ADD command 5-20 ADD DEVICE command 1-3, 1-5, 2-5, 5-4, 5-20 ADD PATH command 1-5, 5-5 ADD PROFILE command 1-2, 1-9, 5-6/5-7 ADM communication protocol 3-1 ADM-2 multipoint supervisor line type 5-11 protocol 2-6 ALTER attribute-spec 5-11 ALTE
Index C Byte-synchronous communications line 2-2 concentrator type 2-6 devices 2-2 C CBSENSEOFF modifier 3-10 CBSENSEON modifier 3-10 CCITTON modifier 3-10 Centralized multipoint data link description 2-8 CFSENSEOFF modifier 3-10 CFSENSEON modifier 3-11 CHAR modifier 3-11 CHECK modifier 3-11 CL modifier 3-12 CLEARCA modifier 3-12 CLEARRTS modifier 3-12 Clear-to-send (CTS) signal 3-16 CLIP 1-4, 2-3, 3-30, D-1 CLOSE procedure 1-7 Code conversion (ASCII and EBCDIC) 2-4 Command format 4-4 Commands nonsensiti
Index E DSM 4-3 DSRSENSE modifier 3-15 DSRSENSEOFF modifier 3-15 DSRSENSEON modifier 3-15 DTROFF modifier 3-16 DTRON modifier 3-16 DUAL212 modifier 3-16 E EBCDIC character code 2-4 modifier 3-17 translation 2-4 ECHO modifier 3-17 EIA modifier 3-17 EMS modifier 3-17 EMSOFF modifier 3-18 End-of-Text (ETX) termination character 3-18 Enquiry (ENQ) control character 2-7 EOT character 3-13 ERRDIF modifier 3-18 Error messages A-2 Ethernet link 2-3 path 5-5 ETX character 3-13 modifier 3-18 termination function 3
Index K Interactive mode, for SCF 4-6 ITBSIZE modifier 3-20 K KATAKANA modifier 3-21 Keyword 4-4 L LEADEOT modifier 3-21 Leased See switched line LEOTRESYN modifier 3-21 LIKE attribute 1-9 Line attribute changes 1-7 attribute modification persistence 1-7 configurations 2-5 facilities 2-7 object attributes, changing 1-11, 4-3 switched 2-7 turnaround 2-10 types 3-1 LINE object 4-2, 4-7 Line type full-duplex 2-10 half-duplex 2-10 Line-handler process 5-4 associated with each Envoy line 2-4 changing modifie
Index O NOLEADEOT modifier 3-26 NOLEOTRESYN modifier 3-26 NONE modifier 3-26 Noninteractive mode, for SCF 4-6 Nonsensitive commands 4-4 NonStop Kernel architecture 2-2 compatible versions of 4-6 Nonswitched line 2-7 NOSETMODEDTRCTRL modifier 3-27 NUMBLOCKS modifier 3-27 O Object attributes 4-5 starting, stopping, and changing 1-7 determining names of 4-7 states 4-7/4-8 types and names 4-6 ODD modifier 3-27 ONEUNIT modifier 3-27 Online help 4-6 OPEN procedure 1-7 Operation of SCF 4-5 Operations environmen
Index R NEXT command 6-6 program 6-1 RECORD command 6-6 SELECT command 6-7 SELECT keywords 6-8 STATETABLES command 6-5, 6-9 Public data network (PDN) 2-6 R RAISERTS modifier 3-31 READ calls 1-7 READCONT modifier 3-31 READONLY modifier 3-31 Record length in bytes (RSIZE or RECSIZE) 5-5 RECSIZE (RSIZE) modifier 3-33 Request-to-send (RTS) signal 3-16 Response time 2-10 RETRIES modifier 3-32 RS232 modifier 3-32 RS422 modifier 3-32 RSIZE modifier 3-33 value 1-4, 5-5 RS-232 2-3, 2-4 RS-422 2-4 RS-449 interface
Index T State-machine labels table 6-9 Station supervisor 2-8 tributary 2-8 Statistics threshold value 3-37 STATUS LINE command 2-5 STOP DEVICE command 1-9, 1-10 STOP LINE command 1-11, 4-2 STOPBITOFF modifier 3-34 STOPBITON modifier 3-35 STOPPED state 4-7 STX character 3-13 Subsystem keyword 4-6/4-7 owner 4-4 Subsystem Control Process (SCP) See SCP Subsystem environment, DSM 4-3 Subsystem Programmatic Interface (SPI) 4-3 SUBTYPE modifier 3-35 Supervisor station 2-4/2-5, 2-8 Super-group access 4-4 SUSPEND
Index X WANENVASC DLC task 2-3 WANENVBSC D-1 WANENVBSC DLC task 2-3 WRITE calls 1-7 X XLATE modifier 3-17 X.21 interface 2-3 Special Characters $SYSTEM.SYSTEM.
