EnvoyACP/XF Configuration and Management Manual Abstract This manual describes EnvoyACP/XF subsystem configuration on HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers. This manual is intended primarily for system managers responsible for configuring and managing EnvoyACP/XF. Application programmers using EnvoyACP/XF to communicate over bit-synchronous lines also need to refer to this manual for information about modifiers.
Document History Part Number Product Version Published 139913 EnvoyACP/XF F40 February 1998 424004-001 EnvoyACP/XF F40 December 1999 429232-001 EnvoyACP/XF F40 March 2001 429232-002 EnvoyACP/XF F40 May 2002 429232-003 EnvoyACP/XF F40 October 2005
EnvoyACP/XF Configuration and Management Manual Glossary Index What’s New in This Manual ix Manual Information ix New and Changed Information Examples Figures Tables ix About This Manual xi Who Should Use This Manual xi How This Manual is Organized xi Where to Get More Information xii Notation Conventions xvi 1.
2. Introduction to EnvoyACP/XF (continued) Contents 2. Introduction to EnvoyACP/XF (continued) PROCESS, DEVICE, and PROFILE Objects 2-11 WAN Subsystem Configuration Database 2-11 SCF Command Routing 2-11 3. WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Profile Files and Associated Protocols 3-1 Required Modifiers 3-1 Optional Modifiers 3-2 Functional Categories 3-2 Modifiers That Can Be Changed 3-3 Optional Modifier Descriptions 3-7 Restricted Modifiers 3-48 4.
4. Subsystem Control Facility (SCF) for EnvoyACP/XF (continued) Contents 4. Subsystem Control Facility (SCF) for EnvoyACP/XF (continued) EnvoyACP/XF Object Types and Object Names EnvoyACP/XF Object States 4-14 4-13 5.
A. Converting EnvoyACP/XF Configuration Information to SCF Contents A.
Examples (continued) Contents Examples (continued) Example 1-8. Example 1-9. Example 1-10. Example 1-11. Example 1-12. Example 1-13. Example 1-14. Example 1-15. Example 5-1. Example 5-2. Example 5-3. Example 5-4. Example 5-5. Example 5-6. Example 5-7. Example 5-8. Example 5-9. Example 5-10. Example 5-11. Example 5-12. Example 5-13. Example 5-14. Example 5-15. Example 5-16. Example 5-17. Example 5-18. Example 5-19. Example 5-20. Example 5-21. Example 5-22. Example 5-23. Example 5-24. Example 5-25.
Examples (continued) Contents Examples (continued) Example 5-30. VERSION PROCESS, DETAIL Command 5-40 Figures Figure 1-1. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 3-7. Figure 3-8. Figure 3-9. Figure 3-10. Figure 3-11. Figure 3-12. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6.
Tables (continued) Contents Tables (continued) Table 4-1. Table 5-1. Table 5-2. Table A-1. Table A-2. Table A-3. Table A-4. Table A-5. Table A-6. Table A-7. Table A-8. Table A-9. Table A-10. Table A-11.
Tables (continued) Contents EnvoyACP/XF Configuration and Management Manual—429232-003 viii
What’s New in This Manual Manual Information EnvoyACP/XF Configuration and Management Manual Abstract This manual describes EnvoyACP/XF subsystem configuration on HP NonStop™ S-series servers and HP Integrity NonStop™ NS-series servers. This manual is intended primarily for system managers responsible for configuring and managing EnvoyACP/XF. Application programmers using EnvoyACP/XF to communicate over bit-synchronous lines also need to refer to this manual for information about modifiers.
What’s New in This Manual • • New and Changed Information Update Guardian 90 references to NonStop operating system (first occurrence) and NonStop OS (subsequent occurrences) Section 4, Subsystem Control Facility (SCF) for EnvoyACP/XF: • • Add or update manual references (for instance, add reference to SCF Reference Manual for H-Series RVUs) Replace instance of TSM with OSM EnvoyACP/XF Configuration and Management Manual—429232-003 x
About This Manual This manual describes configuration of an EnvoyACP/XF subsystem running on a NonStop S-series server or an Integrity NonStop NS-series server. Who Should Use This Manual This manual is intended primarily for system managers responsible for configuring and managing EnvoyACP/XF. It also can be used for reference by application programmers using EnvoyACP/XF to communicate over bit-synchronous communications lines.
Where to Get More Information About This Manual Where to Get More Information The manuals in the NonStop S-series server and Integrity NonStop NS-series server manual set provide references for system managers, operators, analysts, and others who install, configure, operate, manage, and support NonStop S-series servers and Integrity NonStop NS-series servers. Table i.
Where to Get More Information About This Manual This guide explains how to plan for and configure NonStop S-series servers and how to plan and prepare your site, operational environment, and hardware and software configurations. In addition, the guide describes the ServerNet system area network (ServerNet SAN) and the available hardware and system configurations.
Where to Get More Information About This Manual This manual describes how to monitor, modify, and control the wide area network (WAN) subsystem and configure a ServerNet wide area network (SWAN and SWAN 2) concentrator on a NonStop S-series server or Integrity NonStop NS-series server. This manual includes SCF commands used with the WAN subsystem and is written for anyone who configures, manages, or maintains this subsystem and a SWAN concentrator.
WAN Wizard Pro About This Manual Online help for the OSM Event Viewer application, which is a component of the OSM software that lets you set up criteria to view log files in several ways, enabling you to rapidly assess service problems. The OSM Event Viewer is launched from within the OSM LLL and the OSM Service Connection.
Standards Documents About This Manual Standards Documents For additional information on the protocols supported by EnvoyACP/XF, see the following standards documents: Protocol Document HDLC ISO International Standard (IS) 3309, “Data Communications–High-Level Data Link Control Procedures–Frame Structure” (1979) ISO International Standard (DIS) 4335, “Data Communications–High-Level Data Link Control Procedures–Elements of Procedure” (1979) ISO–4335/DAD1, “HDLC, Addendum 1 to ISO-4335” ISO–4335/DAD2, “HD
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Change Bar Notation About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]... !i and !o.
1 Configuration Quick Start This section provides a concise example of creating and starting an EnvoyACP/XF line. For an introduction to EnvoyACP/XF, see Section 2, Introduction to EnvoyACP/XF. For information about the SCF command syntax, see Section 5, Subsystem Control Facility (SCF) Commands for EnvoyACP/XF. You can use the WAN Wizard Pro configuration tool to help you to configure EnvoyACP/XF and the ServerNet wide area network (SWAN) concentrator.
Task 1: Create a PROFILE Object for the Line-Handler Process Configuration Quick Start Task 1 uses PEXFANRM as the profile. Table 1-1.
Configuration Quick Start Task 2: Create the Line-Handler Process name must start with the pound sign (#) and can have up to eight alphanumeric characters). PENFANRM is the name of the template file, or disk file, that HP supplies for the ADCCP-NRM communications protocol. $ZZWAN is the name of the WAN subsystem and $SYSTEM.SYS01 is a sample file location. Example 1-1. Adding a Profile -> ADD PROFILE $ZZWAN.#MYANRM, FILE $SYSTEM.SYS01.
Configuration Quick Start Task 2: Create the Line-Handler Process ALTCPU altcpunumber indicates the processor where the backup EnvoyACP/XF line-handler process normally executes. TYPE (11,n) is the device type and subtype for this EnvoyACP/XF line-handler. Possible subtypes are: 40 (SDLC), 41 (HDLC), 42 (ADCCP). RSIZE rsize specifies the record length in bytes. The RSIZE value determines the maximum read and write counts that the user application can specify for the line.
Configuration Quick Start Task 2: Create the Line-Handler Process PATH { A | B } is the Ethernet path (A or B) on the CLIP, specified by clipnum, that you prefer. This path must have been previously defined through the WAN subsystem SCF ADD PATH command. For information about defining Ethernet paths, refer to the WAN Subsystem Configuration and Management Manual. modifier_keyword is the name of an optional modifier in profile_name.
Configuration Quick Start Task 3: Start the Line-Handler Process 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.#device_name $ZZWAN device_name is the device name of the EnvoyACP/XF line-handler process. Issue the SCF START DEVICE command to the WAN subsystem, as shown in Example 1-3.
Reconfiguring Existing Communications Lines Configuration Quick Start Table 1-2. Persistence of Line Attribute Changes Change Method SCF commands to the WAN Persistence subsystem. Changes persist until you change the DEVICE and/or the PROFILE object in the WAN subsystem. SCF commands to the EnvoyACP/XF subsystem. Changes persist until you change the attributes, change the modifiers in the PROFILE, stop the DEVICE in the WAN subsystem, or until the system is coldloaded.
Reconfiguring Existing Communications Lines Configuration Quick Start Figure 1-1. Configuration Commands to the EnvoyACP/XF Subsystem Terminal OBEY File SCF Log File SCP EnvoyACP/XF Subsystem Line Handler Process Line VST025.vsd To reconfigure an existing EnvoyACP/XF 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 EnvoyACP/XF Subsystem Using SCF on page 1-11 Changing LINE Object Attributes in the EnvoyACP/XF Subsystem Using NonStop OS Procedur
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.#EXF01, TYPE (11, 42), IOPOBJECT $SYSTEM.SYS01.BSPROCO, PROFILE MYANRM, CLIP 1, LINE 0, CPU 0, ALTCPU 1, ADAPTER CONC1, RECSIZE 536, PATH A 5. Start the DEVICE object as shown in Example 1-9: Example 1-9. Starting the Device -> START DEVICE $ZZWAN.#EXF01 Changing the Modifier Definitions in the DEVICE Object 1.
Configuration Quick Start Changing LINE Object Attributes in the EnvoyACP/XF Subsystem Using SCF Changing LINE Object Attributes in the EnvoyACP/XF Subsystem Using SCF 1. Stop the LINE object by issuing an SCF STOP LINE command to the Envoy subsystem as in Example 1-13: Example 1-13. Stopping the Line to Change the Line Object Attribute -> STOP LINE $EXF01 2. Use the SCF ALTER LINE command to change the attribute as in Example 1-14: Example 1-14.
Configuration Quick Start Changing LINE Object Attributes in the EnvoyACP/XF Subsystem Using NonStop OS EnvoyACP/XF Configuration and Management Manual—429232-003 1- 12
2 Introduction to EnvoyACP/XF EnvoyACP/XF is a data-link level interface for bit-synchronous communications. By using EnvoyACP/XF, you can establish data links between your HP system and a variety of remote computers, automatic teller machines, and bit-synchronous terminals (Figure 2-1). Each machine is a station within a data communications network.
Introduction to EnvoyACP/XF • • • Protocols Supported Advanced Data Communications Control Procedures (ADCCP). Developed by the American National Standards Institute (ANSI), this mode enables a choice of either Normal Response Mode (NRM) or Asynchronous Balanced Mode (ABM). Synchronous Data Link Control (SDLC). In this mode, one station is configured as the primary and the other station as the secondary. The primary station initiates data transfer and is in control during the exchange of messages.
Point-to-Point Data Link Introduction to EnvoyACP/XF SDLC and HDLC are subsets of the broader ADCCP protocol standard: SDLC Developed by IBM and a de facto standard within the field of bit-synchronous data communications, SDLC is analogous to ADCCPNRM where a primary station is in control of the data link. Like ADCCP, SDLC can use extended control fields. However, the SDLC protocol does not support extended address fields (see the IBM Synchronous Data Link Control Information Manual).
Point-to-Point Data Link Introduction to EnvoyACP/XF up connection, because a temporary connection is established when one station dials the other station's number (see Figure 2-3). Figure 2-3. Point-to-Point Switched Line Station Station Station Modem VST005.vsd A nonswitched line (Figure 2-4), on the other hand, provides a permanent path between stations.
Multipoint Data Link Introduction to EnvoyACP/XF Figure 2-4. Point-to-Point Nonswitched Line Station Station Privately Owned Cable or Nonswitched Line VST006.vsd 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. In a multipoint data link (Figure 2-5), one station is the supervisor.
Half-Duplex and Full-Duplex Lines Introduction to EnvoyACP/XF Figure 2-5. Multipoint Data Link Tributary Supervisor Station A Nonswitched Multipoint Line (Half-Duplex or Full-Duplex) Station B Station C Station D Tributary Tributary Tributary VST007.vsd Half-Duplex and Full-Duplex Lines An EnvoyACP/XF, point-to-point or multipoint data link can use either half-duplex or full-duplex line facilities.
Half-Duplex and Full-Duplex Lines Introduction to EnvoyACP/XF Figure 2-6. Half-Duplex Lines Send Time Receive VST008.vsd Full-duplex facilities, on the other hand, can pass data in both directions simultaneously, without physical line turnaround (Figure 2-7). Figure 2-7. Full-Duplex Lines Send Receive VST009.vsd Communications pass over a full-duplex line like two-way traffic passes over a divided highway.
Introduction to EnvoyACP/XF The Architecture of NonStop S-Series Servers and Integrity NonStop NS-Series Servers simultaneously in both directions whenever appropriate. EnvoyACP/XF supports both two-way alternate and two-way simultaneous transmission. The Architecture of NonStop S-Series Servers and Integrity NonStop NS-Series Servers This subsection describes the EnvoyACP/XF subsystem relationship to some of the other components of NonStop S-series servers and Integrity NonStop NS-series servers.
Introduction to EnvoyACP/XF ServerNet WAN Concentrator The CLIP is the major programmable device within the SWAN concentrator, providing link-level protocol and a software interface to the server. The CLIP stores and implements specific communications protocols. There are three CLIPs on one SWAN concentrator and each CLIP supports two serial ports. The resulting six lines can support any combination of the following interfaces: • • • • RS-232 RS-449 V.35 X.
Introduction to EnvoyACP/XF ServerNet WAN Concentrator ServerNet WAN Concentrator Features The ServerNet WAN concentrator supports: • • • Six half-duplex or six full-duplex lines for each ServerNet WAN concentrator Bit-oriented devices using the HDLC, SDLC, or ADCCP protocols Bell 201, 208, 209, or 212 modems (or equivalents) (All of these modems must be strapped to provide external clocking; also the 212type modem must be strapped for synchronous operation.
Introduction to EnvoyACP/XF EnvoyACP/XF Lines and Line-Handler Processes Electrical Interfaces The following electrical interfaces are available with the ServerNet WAN concentrator: RS-232 RS-422 EnvoyACP/XF Lines and Line-Handler Processes Each EnvoyACP/XF line has an associated line-handler process; that is, a one-to-one correspondence exists between EnvoyACP/XF lines and EnvoyACP/XF line-handler processes.
Introduction to EnvoyACP/XF SCF Command Routing EnvoyACP/XF Configuration and Management Manual—429232-003 2- 12
3 WAN Subsystem Profiles and Modifiers for EnvoyACP/XF This section describes the WAN subsystem profiles and modifiers or EnvoyACP/XF. Topics described in this section include the following: • • • • Profile Files and Associated Protocols on page 3-1 Required Modifiers on page 3-1 Optional Modifiers on page 3-2 Restricted Modifiers on page 3-48 Profile Files and Associated Protocols Profiles specify the characteristics for a group of communications lines.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifiers SUBTYPE n Default: Depends on protocol (see below) Units: N/A Range: N/A Specifies the type of XF line based on the protocol used: Subtype Protocol Profile Name 40 SDLC PEXFSDLC 41 HDLC PEXFHDLC 42 ADCCP PEXFAABM, PEXFANRM Optional Modifiers To customize your configuration, you can specify some of the following modifiers. Most of these modifiers have default values that come with the profile files in your system.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Modifiers That Can Be Changed Table 3-1.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Modifiers That Can Be Changed Table 3-2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Modifiers That Can Be Changed Table 3-2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Modifiers That Can Be Changed Table 3-2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Table 3-2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions ABM/NRM Default: ABM (for PEXFAABM, PEXFHDLC) NRM (for PEXFANRM, PEXFSDLC) Units: N/A Range: N/A Specifies the protocol mode for this particular EnvoyACP/XF line-handler process. EnvoyACP/XF automatically supplies default values according to the specified PROFILE object. You may specify the appropriate modifier in the PROFILE object for reference.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions ADDRESSn Default: n =1: ADDRESS1 (Octet 1) = 1 for PEXFAABM and PEXFHDLC n=2: ADDRESS2 (Octet 2) = 3 for PEXFAABM and PEXFHDLC n=3-4: ADDRESS3 through ADDRESS4 = 0 for PEXFAABM and PEXFHDLC n=3: ADDRESS1 (Octet 1) = 193 for PEXFANRM and PEXFSDLC n=2-4: ADDRESS2 through ADDRESS4 = 0 for PEXFANRM and PEXFSDLC Units: N/A Range: ADDRESS1 (Octet 1) = 1 through 254 for ABM and HDLC ADDRESS2 (Octet 2) = 1 through 254 for ABM
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions To specify an extended address, enable the extended address format by specifying the ADDRESSSIZE modifier. Note the following restrictions: • • • Extended address fields are not supported by SDLC. You can use the ADDRESS modifier for a point-to-point ADCCP-NRME configuration to specify an extended address of up to 4 octets.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions AUTOLOAD/NOAUTOLOAD Default: AUTOLOAD Units: N/A Range: N/A Alternate Modifier: NOAUTOLOAD or AUTOLOAD The AUTOLOAD modifier specifies that when a processor is reloaded, buffer pools will be initialized, the communications line interface processor (CLIP) will be downloaded, and the line connection will be made for leased lines. This modifier also specifies that when a CLIP error occurs, the CLIP will be downloaded.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Figure 3-1. AUTOTESTRESP Versus NOAUTOTESTRESP AUTOTESTRESP Application TEST-Frame TEST-Frame Secondary Station Primary Station NOAUTOTESTRESP Application TEST-Frame Primary Station Secondary Station VST013.vsd The modifiers AUTOTESTRESP/NOAUTOTESTRESP are ignored for a primary station.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF • Optional Modifier Descriptions If the station receiving a TEST frame is in the Logical Disconnect State (ADCCP LDS/SDLC NRM) or the Information Transfer State (ADCCP ITS/SDLC NRM), the TEST frame is handled according to the modifier settings and the following circumstances: • • • • If the TEST frame has the P-bit off, the receiving station in LDS/NRM ignores the TEST frame.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions CONTCF/NOCONTCF Default: NOCONTCF Units: N/A Range: N/A Note: Only for switched lines. Specifies that the controlled carrier for the modem is monitored. If CONTCF is specified, EnvoyACP/XF does not transmit when input carrier (CD) is detected; instead, it accepts the incoming call first.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions DSRTIMER affects the use of the CONTROL 17,1 and CONTROL 11 procedure calls. (See the EnvoyACP/XF Application Programming Manual for further information on these calls.) If DSR does not appear before this interval expires, the function terminates with a timeout error, and data terminal ready (DTR) resets. DSRTIMER defaults to 4 seconds. If n is specified as 0, no timeout occurs and DSR waits indefinitely.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions You can set or override this modifier by issuing a SETMODE 19 call in an application or by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem. FLAGFILL/NOFLAGFILL Default: NOFLAGFILL (Flag characters are not transmitted continuously.) Units: N/A Range: N/A Causes flag characters to be transmitted continuously between frames after a modem connection has been established and the first frame has been sent.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions FULL/HALF Default: FULL (for PEXFHDLC, PEXFAABM) HALF (for PEXFANRM, PEXFSDLC) Units: N/A Range: N/A See also: TWS/TWA The FULL modifier specifies full-duplex operation on the physical level. To use this modifier, you must have a full-duplex modem. Specifying the FULL modifier enables the line to carry communications in opposite directions at the same time.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Thus, with IBM extended control, only the following numbered frames contain a 2-byte control field: • • • • • Information frames (I-frames) Receive Ready frames (RR-frames) Receive Not Ready frames (RNR-frames) Reject frames (REJ-frames) Selective Reject frames (SREJ-frames) The default setting for this modifier is NOIBMEXTENDED which specifies that the IBM extended control format is not enabled.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions You can set or override these modifiers by issuing a SETMODE 16 call in an application or by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem. IDLERESPRR See IDLECMDRR/IDLERESPRR. IDLETIMER Default: 50 (0.5 second) Units: .01 seconds Range: 2 through 32767 See also: IDLECMDRR/IDLERESPRR and L2HEARTBEAT/NOL2HEARTBEAT Specifies a timer for the communications link.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions The IDLETIMER modifier works with ABM configurations only if you also enable one of the following pairs of modifiers: • • L2HEARTBEAT and IDLECMDRR L2HEARTBEAT and IDLERESPRR Figure 3-2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions You can set or override IDLETIMER by issuing a SETMODE 16 call in an application or by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem. IGNOREDSR/NOIGNOREDSR Default: NOIGNOREDSR Units: N/A Range: N/A Alternate modifier: IGNOREDSR or NOIGNOREDSR IGNOREDSR modifier specifies that DSR will not be checked for an OFF condition before completing a disconnection of a leased line.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions L2HEARTBEAT/NOL2HEARTBEAT Default: NOL2HEARTBEAT. Units: N/A Range: N/A See also: IDLECMDRR/IDLERESPRR and IDLETIMER Specifies a heartbeat RR frame at IDLETIMER intervals when an ABM mode line is idle (see Figure 3-4). This modifier affects the use of IDLECMDRR and IDLERESPRR (both these modifiers affect the transmission of RR frames).
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions L2RETRY Default: 3 Units: Level-2 retries Range: 0 through 255 See also: IDLECMDRR/IDLERESPRR, IDLETIMER, and T1TIMER Specifies the maximum number of station protocol-level, error-recovery attempts that can be made before an error is reported to the application. These errors include frames not acknowledged and poll-response timeouts.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions LOCALPOOLPAGES Default 60 Units Pages (1024 words per page) Range 2 through 127 pages Specifies the number of pages that the line uses for its local pool. The local pool provides space for data and trace buffers. The default value is 60 pages; however, EnvoyACP/XF automatically allocates additional local pool pages as needed. Do not specify this modifier; allow EnvoyACP/XF to allocate pages as necessary. Caution.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions MODEMLOSSFATAL/NOMODEMLOSSFATAL Default: NOMODEMLOSSFATAL (Modem error statistics are kept, but modem loss is not fatal to the link.) Units: N/A Range: N/A Note: Only for full-duplex, nonswitched lines. Specifies that a modem error (loss of CTSDCD) causes EnvoyACP/XF to immediately report the modem status and put the link in the disconnect state.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions NOIBMEXTENDED See IBMEXTENDED/NOIBMEXTENDED on page 3-17. NOL2HEARTBEAT Disables L2HEARTBEAT/NOL2HEARTBEAT on page 3-22. NOMODEMLOSSFATAL See MODEMLOSSFATAL/NOMODEMLOSSFATAL on page 3-25. NOOPTION1 See OPTION1/NOOPTION1 on page 3-27. NOOPTION2 See OPTION2/NOOPTION2 on page 3-30. NORECVRNRRETRY See RECVRNRRETRY/NORECVRNRRETRY on page 3-32. NOREJ See REJ/NOREJ on page 3-32.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions NOV25 See V25/NOV25 on page 3-47. NRM See ABM/NRM on page 3-8. Specifies that the line type is not X.21. The line type is RS232 if RS232 is specified or RS422 if RS422 is specified. (See RS422/RS232.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Figure 3-5. OPTION1: Delayed I-Frame Acknowledgment Tributary Stations Supervisor Station (Nr/Ns) 01 RR-P 1 01 I-F 3 5 (0) (0, 0) 02 RR-P (0) 02 RR-F (0) 2 4 (1) 01 RR-P Legend 1 The supervisor station polls tributary station 01 by sending it an RR-frame with the poll bit set. 2 Tributary station 01 responds by sending back an I-frame with the final bit set.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Figure 3-6. NOOPTION1: Immediate I-Frame Acknowledgment Tributary Stations Supervisor Station (Nr/Ns) 01 RR-P 1 3 4 01 I-F (0, 0) 01 RR (1) 02 RR-P (0) 02 RR-F 6 (0) 2 (0) 5 (1) 01 RR-P Legend 1 The supervisor station polls tributary station 01 by sending it an RR-frame with the poll bit set. 2 Tributary station 01 responds by sending back an I-frame with the final bit set.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions OPTION2/NOOPTION2 Default: NOOPTION2 Units: N/A Range: N/A Note: Only for SDLC. OPTION2 enables an alternate form of station management to support the link establishment characteristics necessary to interface with an IBM SDLC Loop (Token Ring) Controller.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions OPTION6 This is applicable only in NRM mode. When set, in LDS state, the primary station will not set poll bit unless application sets the poll bit. Note. 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 EnvoyACP/XF Optional Modifier Descriptions RECVRNRRETRY/NORECVRNRRETRY Default: RECVRNRRETRY Units: N/A Range: N/A Note: Only for stations receiving Runners. See also: RNRTIMER, SENDRNRRETRY/NOSENDRNRRETRY Applies only to a station receiving RNRs (remote RNR state). The default is RECVRNRRETRY. When NORECVRNRRETRY is set and RNR is received from a remote station, the following actions occur: 1. If the local station is a primary station, it sends a DISC.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions This modifier also selects two-way simultaneous operation for ADCCP and SDLC full-duplex lines. If you do not specify this modifier (defaults to NOREJ), REJ is not transmitted, and the reception of REJ results in the transmission of a FRMRCMDR frame. You can set or override this modifier by issuing a SETMODE 16 call in an application or by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Figure 3-7.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions The default value of the RNRTIMER is zero. When the value is zero, EnvoyACP/XF allows the RNR state to persist (no error condition is reported). A zero value has the same effect on both the local RNR state (caused by local buffer depletion) and the remote RNR state (receipt of an RNR from a remote station). Note. The RNRTIMER value is specified on a line basis.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions 3. Some remote stations are disconnected. 4. The local station enters LDS. Note. When this timer expires, a primary station sends a DISC. A secondary station sends a DM to any received frame that is not a mode-setting command. RNRTIMER is supported only through the WAN subsystem. There is no SETMODE function to allow an application to modify the RNRTIMER value dynamically.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF • Optional Modifier Descriptions A station can be forced to enter RNR state if an application issues a CONTROL procedure. For example, an application might place the station in RNR state so that the station can have time to process already received transactions before receiving more transactions.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions If NOSENDRNRRETRY is specified, the local station does not send RNRs when it is in a buffer-depletion RNR state. Instead, the following actions occur (see Figure 3-9): 1. If the local station is a primary station, it sends DISC upon entering the local RNR state. If the local station is a secondary station, it sends DM to any received frame that is not a mode-setting command. 2.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions When the application sets the local RNR state, the receive RNR state is unaffected. Thus, when an application sets the local RNR state, the remote station can enter RNR state and remain in that state long enough to cause the RNR timer to expire. New functions are provided by the modifiers SENDRNRRETRY and RNRTIMER. Thus, the specification of SENDRNRRETRY and RNRTIMER could cause new behavior.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions STATISTICSON/STATISTICSOFF Default: STATISTICSOFF Units: N/A Range: N/A Alternate modifier: STATISTICSOFF or STATISTICSON STATISTICSON modifier specifies the routing of statistics messages for the line; STATISTICSOFF deactivates the routing of statistics messages for the line. SUPR/TRIB Default: SUPR Units: N/A Range: N/A Note: Only for NRM.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions You can set or override this modifier by issuing a SETMODE 16 call in an application or by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem. SWITCHED/NOSWITCH Default: NOSWITCH Units: N/A Range: N/A SWITCHED specifies switched-line modem operation.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions T1TIMER Default: 500 (5 seconds) Units: .01 seconds Range: 10 through 32767 Specifies a timer for the communications link. Set n to a value longer than twice the time required for the transmission of a frame FRAMESIZE bytes in length, plus the time required by delays in processing at each end of the link. T1TIMER takes different definitions, depending on the protocol mode, as described below.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions NRM Protocol—Secondary Station According to the NRM protocol standard, there is no timer for secondary stations; however, EnvoyACP/XF does implement a timer for secondary stations (Figure 3-11). When T1TIMER is configured for a secondary station, T1TIMER specifies the period that a secondary station waits for a primary station to poll.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions Figure 3-12. T1TIMER and ABM Line I-Frame ABM Primary Substation RR Frame Sent with P-Bit Set Secondary Substation I-Frame Secondary Substation Primary Substation RR Frame Sent with P-Bit Set TITIMER specifies how long the primary or secondary substation waits to receive a response from the other station before sending an RR frame with the P-bit set. VST024.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions TRANSLATE Default: Not specified Units: N/A Range: N/A Alternate Modifier: None. See also EBCDIC and ASCII. Specifies that data in the information field is to be translated to and from EBCDIC. You can set or override the setting for EBCDIC translation by issuing a SETMODE 19 call. Note. The TRANSLATE modifier appears when you specify the EBCDIC modifier.To remove the TRANSLATE modifier, specify the ASCII modifier.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions TRNSOFFSET Default: 0 Units: Octets Range: 0 to the value of FRAMESIZE See also: TRNSLENGTH When used with the XLATE attribute (described in XLATE on page 5-17), TRNSOFFSET specifies the offset into the information field at which the translation begins. Translation continues for the number of octets specified by the TRNSLENGTH modifier, or to the end of the information field if TRNSLENGTH is 0.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Optional Modifier Descriptions You can alter this modifier by issuing an SCF ALTER LINE command to the EnvoyACP/XF subsystem but not by issuing a SETMODE procedure call in an application. V25/NOV25 Default: NOV25 Units: N/A Range: N/A Specifies that this line can be used with a V.25 bis-compatible modem for serial automatic calling. You can use this capability with both NRM and ABM protocol configurations.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF Restricted Modifiers XPAGES Default: 0 Units: Pages. Range: No programmatic limit. Specifies the number of extended memory pool pages. X21/NOX21 Default: NOX21 Units: N/A Range: N/A X21 specifies that the line type is X.21; NOX21 specifies that the line type is not X.21. The line type is RS232 if RS232 is specified or RS422 if RS422 is specified.
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF IOWORDSn Default: 0 Units: N/A Range: N/A Alternate modifier: N/A NOACI1 Default: NOACI1 Units: N/A Range: N/A Alternate modifier: ACI1 NOAUTOACCEPT Default: NOAUTOACCEPT Units: N/A Range: N/A Alternate modifier: AUTOACCEPT NOOPTION4 Default: NOOPTION4 Units: N/A Range: N/A Alternate modifier: OPTION4 NRDYCTRL Default: NRDYUNCTRL Units: N/A Range: N/A Alternate modifier: NRDYUNCTRL EnvoyACP/XF Configuration and Man
WAN Subsystem Profiles and Modifiers for EnvoyACP/XF NRDYUNCTRL Default: NRDYUNCTRL Units: N/A Range: N/A Alternate modifier: NRDYCTRL OPTION4 Default: NOOPTION4 Units: N/A Range: N/A Alternate modifier: NOOPTION4 PROGRAM1n Default: C8169P00 Units: N/A Range: N/A Alternate modifier: N/A PROG9367n Default: C8169P00 Units: N/A Range: N/A Alternate modifier: N/A PROG9370n Default: C8169P00 Units: N/A Range: N/A Alternate modifier: N/A EnvoyACP/XF Configuration and Manag
4 Subsystem Control Facility (SCF) for EnvoyACP/XF EnvoyACP/XF works with a user application to create a complete access method enabling HP 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 EnvoyACP/XF 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 EnvoyACP/XF Tasks You Can Perform Using SCF process. These are described in further detail in EnvoyACP/XF Object Types and Object Names on page 4-13.
Subsystem Control Facility (SCF) for EnvoyACP/XF Stopping a LINE Object Stopping a LINE Object To make changes to the LINE object, first stop or abort the line, then change it and restart it. The following example shows how to stop a line by issuing an SCF command: -> STOP LINE $EXF01 Changing a LINE Object You can change line attributes by issuing SCF commands directly to the EnvoyACP/XF subsystem.
Subsystem Control Point (SCP) Subsystem Control Facility (SCF) for EnvoyACP/XF Figure 4-2 shows the relationships between DSM and the subsystem environment. Figure 4-2. Overview of DSM Architecture Management Services Operations Environment DSM Applications Management Applications Operators Subsystem Environment Tandem Subsystems Objects DSM Services Business Applications DSM Tools Objects Subsystem Programmatic Interface (SPI) VST026.vsd SCF is a DSM tool in the operations environment.
Subsystem Control Facility (SCF) for EnvoyACP/XF 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 EnvoyACP/XF 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.
Subsystem Control Facility (SCF) for EnvoyACP/XF Object States In commands that provide displayed information, such as the INFO and STATUS commands, you can specify the DETAIL keyword to get a detailed information display. The full syntax of each subsystem-specific SCF command for EnvoyACP/XF is given in Section 5, Subsystem Control Facility (SCF) Commands for EnvoyACP/XF.
Subsystem Control Facility (SCF) for EnvoyACP/XF Running SCF the completion message indicates an error condition, SCF displays an appropriate message and then displays its prompt. 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.
Subsystem Control Facility (SCF) for EnvoyACP/XF PROCESS, DEVICE, and PROFILE Objects handler processes. To add an EnvoyACP/XF line, you add an EnvoyACP/XF linehandler process object; a corresponding LINE object is defined automatically. 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.
SCF Command Routing Subsystem Control Facility (SCF) for EnvoyACP/XF 1. Read about EnvoyACP/XF profile files and modifiers in Section 3, WAN Subsystem Profiles and Modifiers for EnvoyACP/XF, of this manual. 2. Add a PROFILE object to the WAN subsystem. a. Select the disk file name that corresponds to the communications protocol you will use for the new line-handler process. b. Use the SCF command ADD PROFILE to create a PROFILE object.
SCF Command Routing Subsystem Control Facility (SCF) for EnvoyACP/XF This command causes the WAN subsystem to create an EnvoyACP/XF line-handler process named $EXF01. Figure 4-4. Starting a Process for the First Time 1. START DEVICE $ZZWAN.#EXF01 Configuration Data Base WAN Subsystem EnvoyACP/XF Subsystem $ZZWAN DEVICE Object ($ZZWAN.#EXF01) 2. Look up modifiers 3. Launch process Line Handler Process ($EXF01) VST011.
SCF Command Routing Subsystem Control Facility (SCF) for EnvoyACP/XF Figure 4-5. SCF Commands to the EnvoyACP/XF Subsystem Terminal SNAX Application OBEY File SCF Commands SCF Guardian Procedure Calls Log File SCP EnvoyACP/XF Subsystem EnvoyACP/XF Line Handler Process Line VST010.vsd To reconfigure an existing EnvoyACP/XF communications line, first decide whether you want: • • • The line-attribute definition always to revert to the change stored in the WAN subsystem configuration database.
Subsystem Control Facility (SCF) for EnvoyACP/XF • • Objects for EnvoyACP/XF Changing attributes in the EnvoyACP/XF subsystem. Programmatically changing attributes in the EnvoyACP/XF subsystem. These procedures are described below. Changing Line Attributes in the EnvoyACP/XF Subsystem by Using Guardian Procedure Calls In this manual, Table 3-2, Changing Optional Modifiers, on page 3-4, provides a quick reference for changing EnvoyACP/XF line attributes by procedure call number.
Subsystem Control Facility (SCF) for EnvoyACP/XF EnvoyACP/XF Object Types and Object Names EnvoyACP/XF Object Types and Object Names PROFILE The WAN subsystem contains several SCF objects, including the DEVICE and PROFILE objects. The PROFILE object is a user-created, SCF object containing default modifier values pertaining to the communications line. You build the PROFILE object from disk files, or templates, which come with the EnvoyACP/XF product.
Subsystem Control Facility (SCF) for EnvoyACP/XF EnvoyACP/XF Object States How to Determine EnvoyACP/XF Object Names To determine the names assigned to PROCESS and LINE objects, enter one of the following command at the SCF prompt: -> LISTDEV TYPE 11 -> LISTDEV ENVOYACX Note. ENVOYACX is the EnvoyACP/XF subsystem keyword for online help. EnvoyACP/XF Object States LINE objects can be in the following states: STARTED The LINE object enters the STARTED state when the START command completes successfully.
Subsystem Control Facility (SCF) for EnvoyACP/XF EnvoyACP/XF Object States STOPPING The object is in a STOPPING state when it is processing a STOP command. In this state, any established links are being broken and applications cannot establish new links. STARTING The object is in the STARTING state when it has received a START command and the object is in the process of starting. The STARTING state is a transition state between the STOPPED and STARTED states.
Subsystem Control Facility (SCF) for EnvoyACP/XF EnvoyACP/XF Object States EnvoyACP/XF Configuration and Management Manual—429232-003 4- 16
5 Subsystem Control Facility (SCF) Commands for EnvoyACP/XF This section describes SCF commands available for EnvoyACP/XF. Note. “CPU” and “processor” are used interchangeably in this section. Table 5-1 identifies which SCF commands can be executed on which EnvoyACP/XF objects. Table 5-1.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ABORT Command Table 5-2 identifies which SCF commands provide EnvoyACP/XF subsystem management in the WAN subsystem. 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 EnvoyACP/XF ACTIVATE Command Considerations • • • The command is rejected with an error if the line is in the DIAGNOSING state. A warning is returned if the line is in the STOPPED state. All application OPEN requests are aborted. ACTIVATE Command The ACTIVATE command is a sensitive command that activates a line that is in the suspended state.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ADD DEVICE Command ADD DEVICE Command The WAN subsystem ADD DEVICE command provides a method for creating EnvoyACP/XF lines. This enables you to associate profiles with the process. See Profile Files 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 EnvoyACP/XF ADD DEVICE Command RSIZE rsize specifies the record length in bytes. RSIZE (RECSIZE) specifies the maximum amount of information transferred between the EnvoyACP/XF 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 EnvoyACP/XF line handler process.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ADD PROFILE Command Example The following command adds the device called $EXF01. Example 5-3. ADD DEVICE Command -> ADD DEVICE $ZZWAN.#EXF01, 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.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER Command Example Example 5-4, ADD PROFILE Command, on page 5-7shows 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 #MYANRM. PEXFANRM is the name of the template file, or disk file, that HP supplies for the ADCCP-NRM communications protocol. $ZZWAN is the name of the WAN subsystem and $SYSTEM.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER DEVICE Command CLIP clip-num indicates which CLIP the DEVICE object will use. Possible values are 1, 2, or 3. HIGHPIN ON | OFF indicates whether the data communications subsystem object is to be run highpin. The default is ON. IOPOBJECT object-file-name indicates the file name of the executable object code for the data communications subsystem object. LINE line-num selects the line number on the selected CLIP to be used by the DEVICE.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER DEVICE Command Examples The following command alters the modifier TIMEOUT to its default value: Example 5-5. ALTER DEVICE Command to Reset TIMEOUT Modifier -> ALTER DEVICE $ZZWAN.#EXF01, RESET TIMEOUT The following command alters the BUFFER modifier from POOLED to DEDICATED: Example 5-6. ALTER DEVICE Command to Alter BUFFER Modifier -> ALTER DEVICE $ZZWAN.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command ALTER LINE Command The ALTER LINE command applies to the EnvoyACP/XF subsystem and changes the attributes of the line. Changes made using ALTER LINE persist only as long as the line is running. ALTER LINE is a sensitive command.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command OUT file-spec causes any SCF output generated for this command to go to the specified file. file-spec must be a partially or fully qualified file name. If you do not specify this option, the output goes to the home terminal. object-name is the name of the line to be altered. ABMSETP specifies whether EnvoyACP/XF automatically sets the P/F-bit in supervisory frames.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command ADDRESS4 specifies the address of the remote station. The range depends on the protocol used. Default 0 Range 0 to 254 ADDRSIZE specifies the maximum number of octets found in the address field of each frame. Default 1 for SDLC, HDLC, ABM 4 for NRM Range 1 to 4 BROADCAST Enables the #BDCAST virtual subdevice for a line.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command EXTENDEDCONTROL specifies the selection of a basic or extended control field for frames transferred on the communication link. Default OFF Range ON | OFF FLAGFILL specifies whether flag characters are transmitted continuously between frames. Default OFF Range ON | OFF FRAMESIZE specifies the maximum size, in words, of read and write buffers for the line.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command L1RETRY specifies the maximum link-level, error recovery attempts. Default 3 Range 0 to 255 L2HEARTBEAT specifies that an RR frame is sent at every period specified in IDLETIMER time (if the line is idle). Default OFF Range ON | OFF L2RETRY specifies the maximum protocol-level, error-recovery attempts.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command RCVRNRRETRY specifies how the primary station handles an RNR (receiver not ready) condition from a remote station. If this field is ON, then the primary station will reply to an RNR received from the remote station with either DISC or FRMR depending on whether the station is primary or secondary. Default OFF Range ON | OFF REJECT specifies whether the line supports REJ frame transmission and reception.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command STATION specifies whether the station is primary or secondary. Default SECONDARY Range PRIMARY | SECONDARY SWINCARRIER specifies that CD is expected to rise before a remote station starts a transmission, and is expected to fall once the remote station completes the transmission. Default ON for ABM OFF for NRM Range ON | OFF SWITCHED specifies whether a switched line modem operation is selected.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER LINE Command T1TIMER specifies the time between output completion and when a frame containing the P/F bit receives a response (for a primary station). This timer is not used for a secondary station. Default 500 Range 10 to 32767 Units 10 milliseconds V25 specifies that the EnvoyACP/XF line is used with a V.25 bis modem. It also implies that this is a switched line.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF ALTER PROFILE Command Example The following command changes the V25 attribute from OFF (the default value) to ON. Example 5-7. ALTER LINE Command -> ALTER LINE $ACPXF, V25 ON Considerations The line must be in the STOPPED state before you can alter its attributes. ALTER PROFILE Command The ALTER PROFILE command changes attributes in a the specified PROFILE object in the WAN subsystem.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO Command Considerations • • You must stop the DEVICE object with the STOP DEVICE command before you can delete it. Only DEVICE objects that were added with the WAN subsystem ADD command can be deleted. INFO Command The INFO command is a nonsensitive command that displays the static configuration attribute values for a data communications subsystem object.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO DEVICE Command DETAIL specify this attribute to display detailed information about the DEVICE object. IOPOBJECT specify this attribute to display only the SWAN concentrator IOPOBJECT. LINE specify this attribute to display only the SWAN concentrator LINE. PATH specify this attribute to display only the SWAN concentrator PATH. PROFILE specify this attribute to display only the PROFILE object.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO DEVICE Command Following are definitions for the display fields not defined under the command syntax: Unit is a logical entity that facilitates the configuration of MULTI lines. For more information, refer to the information about full-duplex protocols in the EnvoyACP/XF Application Programming Manual. Alternate Cpu indicates the number of the alternate CPU. Preferred Cpu indicates the number of the preferred CPU.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO LINE Command INFO LINE Command The INFO LINE command is a nonsensitive command that displays the current information of the specified line. INFO [ / OUT file-spec / ] LINE object-name [ , DETAIL ] (If DETAIL is specified, all the following attributes are displayed. If you specify any of the following attributes, only that attribute is displayed.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO LINE Command OUT file-spec causes any SCF output generated for this command to go to the specified file. file-spec must be a partially or fully qualified file name. If you do not specify this option, the output goes to the home terminal. object-name is the name of the line for which you are requesting information. See the attribute definitions for the ALTER command starting with ABMSETP on page 5-11.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO LINE Command Example 5-12. INFO LINE, DETAIL Command 13 -> INFO LINE $ACPXF, DETAIL Envoy ACP/XF Detailed Info Line \SYS1.$ACPXF *Abmsetp................. OFF *Address1................ 0 *Address2................ 0 *Address3................ 0 *Address4................ 0 *Addrsize................ 1 *Autoload................ ON *Broadcast............... OFF *Controlcarrier.......... ON *Dsrtimer................ 400 *Duplex..................
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF INFO PROFILE Command Protocol Identifies the communications protocol for the LINE. For alterable attribute definitions, see the descriptions under ALTER Command on page 5-7. Example 5-13 shows how to inquire about specific parameters on a LINE object. Example 5-13. INFO LINE Command for Specified Parameters -> INFO LINE $ACPXF, ABMSETP, T1TIMER Envoy ACP/XF Detailed Info Line \SYS1.$ACPXF *Abmsetp.................. OFF *T1timer...............
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF NAMES Command OBEYFORM causes the INFO command to display the information about the profile in the form ADD PROFILE commands. Example The format of the display for the INFO PROFILE command is shown in Example 5-14. Example 5-14. INFO PROFILE Command 22-> info profile #sdlc WAN MANAGER Info profile \IDC12.$ZZWAN.#SDLC FILE.............. \IDC12.$SYSTEM.SYS02.PEXFSDLC Devices using this profile Device.......... 1 : $XF2S Device..........
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF START Command specified in the ADD DEVICE command. You can use the asterisk (*) to specify all configured DEVICE objects. DEVICE shows a list of the configured data communications subsystem objects. Example The format of the display for the NAMES DEVICE command is shown in Example 5-15. Example 5-15. NAMES DEVICE Command 27-> names device $zzwan.#* WANMgr Names DEVICE $ZZWAN.#* DEVICE $ZZWAN.#EXF01 $ZZWAN.#ATPP1 $ZZWAN.#ATPP2 $ZZWAN.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF START DEVICE Command Example This command line starts the LINE object named $ACPXF. Example 5-16. START LINE Command -> START LINE $ACPXF Considerations • • • • A non-error completion of START indicates only that the subsystem initiated processing for the START operation; it does not indicate whether the START operation completed successfully. A warning appears if the LINE object is already in the STARTED state.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STATS Command Considerations • • • EnvoyACP/XF does not support the SEL or SUB options. A non-error completion of the START command indicates only that the subsystem was able to initiate processing for the START operation. It does not necessarily indicate that the operation completed successfully. A warning is issued if the LINE is already in the STARTED state.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STATS Command Example 5-18. STATS LINE Command -> STATS LINE $ACPXF Example 5-19 displays statistical information for a line named $ACPXF then resets the statistics counters to their initial values. Note. The reset option is sensitive. Example 5-19. STATS LINE Command, RESET Option 14-> STATS LINE $ACPXF,RESET EnvoyACPXF Detailed STATS LINE $ACPXF Reset Time............... 18 Nov 1996, 17:46:52.336 Sample Time.............. 19 Nov 1996, 11:01:42.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STATUS Command Line Path Errors shows the number of line errors at the LIU level. STATUS Command The STATUS command is a nonsensitive command that is used to display current status and configuration information for a specified object. STATUS DEVICE Command The WAN subsystem STATUS DEVICE command displays current status and configuration information about a data communications subsystem object.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STATUS LINE Command OUT file-spec causes any SCF output generated for this command to go to the specified file. file-spec must be a partially or fully qualified file name. If you do not specify this option, the output goes to the home terminal. object-name is the name of the line for which you are requesting status information. Example 5-21 displays the status of the LINE object $ACPXF. Example 5-21.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STOP Command LDEV is the logical device number of the line. Path indicates the primary path to the CLIP. PPID is the processor number and PIN of the primary EnvoyACP/XF process. Primary Trace indicates whether the primary process is being traced. State is the current object state. SWAN LINE is the adapter name, CLIP number, and WAN line number on which the line is configured.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF STOP DEVICE Command Considerations • • • • The subsystem issues a warning if the line is already in the stopped state. The subsystem rejects STOP if the line is in the DIAGNOSING state. You must stop the line before issuing an ALTER LINE command. Any attributes previously altered through the ALTER LINE command will remain intact when you restart the line.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF SUSPEND Command SUSPEND Command The SUSPEND command is a sensitive command that blocks the object from accepting subsequent OPEN requests from the application programs. Current OPEN requests are not affected. SUSPEND [ / OUT file-spec / ] LINE object-name OUT file-spec causes any SCF output generated for this command to go to the specified file. file-spec must be a partially or fully qualified file name.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF SWITCH Command CPU cpu-number selects the new the processor number. With conventional TCP/IP, CPU forces the processor and path switch; cpu-number must be the processor of the backup process. With PTCPIP, CPU forces the processor switch without changing the path; cpu-number must be the processor of the backup process. PATH A | B selects the new path for the process.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF TRACE Command TRACE Command The TRACE command is a sensitive command that initiates trace mode on the specified object. You can use traces as diagnostic tools. TRACE [ / OUT file-spec / ] LINE object-name { , STOP [ , BACKUP ] } { [ , COUNT count ] [ , NOCOLL ] [ , PAGES pages ] [ , RECSIZE sizes ] [ , SELECT select-name ] [ , WRAP ] , TO file-spec } OUT file-spec causes any SCF output generated for this command to go to the specified file.
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF TRACE Command PAGES pages designates how much memory space, in units of pages (2,048 bytes), is allocated in the extended data segment used for tracing. The value of pages must be an integer in the range 4 through 32766. If PAGES is omitted, the extended datasegment size is set to 64 pages. RECSIZE sizes specifies the length of the data in the trace-data records. Byte length is an integer in the range 16 through 4,050 or equal to 0 (zero).
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF Option Meaning DI Data In DO Data Out CLBI CLB frame in trace CLBO CLB frame out trace CLIP CLIP trace CLIPDI CLIP In trace CLIPDO CLIP Out trace CLIPL1 CLIP level-1 protocol trace CLIPL2 CLIP level-2 protocol trace CLIPL3 CLIP level-3 protocol trace CLIPL4 CLIP level-4 protocol trace CLIP-REQ CLIP Requests CLIPCTI CLIP Control In CLIPCTO CLIP Control Out TRACE Command TO file-spec specifies the file to hold the trace
Subsystem Control Facility (SCF) Commands for EnvoyACP/XF VERSION Command VERSION Command The VERSION command is a nonsensitive command that displays EnvoyACP/XF subsystem version information and level of support for security and tracing. VERSION [ / OUT file-spec / ] PROCESS object-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to go to the specified file. file-spec must be a partially or fully qualified file name.
A Converting EnvoyACP/XF Configuration Information to SCF This appendix describes how to convert the following configuration files from D-series releases to G-series releases.
Converting EnvoyACP/XF Configuration Information to SCF CMI-to-SCF Conversion Guide Table A-1. Configuration Programs for D-Series and G-Series RVUs (page 2 of 2) D-Series RVUs G-Series RVUs Capability SYSGENR COUP CMI SYSGENR SCF to WAN Subsystem Can stop individual terminals or printers configured with the MULTI attribute N.A. No Yes No No No Changes survive system load Yes Yes No Yes Yes No Changes survive processor reload Yes Yes No N.A.
Converting EnvoyACP/XF Configuration Information to SCF Converting Comment Text in Command (OBEY) Files Table A-2. Comparison of CMI and SCF Commands (page 2 of 2) CMI Command SCF Command STATUS STATUS STATUS, DETAIL STATS * STATUS, RESET STATS, RESET * STOP STOP SUSPEND SUSPEND TRACE TRACE * This SCF command can be used to achieve a similar, but not identical, function as the CMI command.
Converting EnvoyACP/XF Configuration Information to SCF Default Values for COUP Macros Table A-3. Comparison of COUP and SCF Object Types COUP Object Type SCF Subsystem CONTROLLER no conversion DEVICE WAN PATH no conversion SCF Object Type DEVICE Default Values for COUP Macros Table A-4 correlates D-series COUP macros with G-series WAN subsystem profiles for EnvoyACP/XF. Table A-4.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPABMXF Macro to the PEXFAABM Profile Table A-5.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPABMXF Macro to the PEXFAABM Profile Table A-5. COUP ADCCPABMXF Macro Comparison to the PEXFAABM Profile (page 3 of 5) D-Series COUP Modifier D-Series Default Value G-Series SCF Attribute G-Series Default Value IOPOBJECT $SYSTEM. SYSnn. BSPROCO $SYSTEM. SYSnn.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPABMXF Macro to the PEXFAABM Profile Table A-5.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPNRMXF Macro to the PEXFANRM Profile Table A-5. COUP ADCCPABMXF Macro Comparison to the PEXFAABM Profile (page 5 of 5) D-Series COUP Modifier D-Series Default Value G-Series SCF Attribute G-Series Default Value X21/NOX21 NOX21 None None XFERTIMER 0 XFERTIMER 0 XPAGES 0 XPAGES 0 * This SCF attribute is required on G-series releases. ** This SCF attribute is specified in the DEVICE object in the WAN subsystem.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPNRMXF Macro to the PEXFANRM Profile Table A-6.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the ADCCPNRMXF Macro to the PEXFANRM Profile Table A-6.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the HDLCXF Macro to the PEXFHDLC Profile Table A-6.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the HDLCXF Macro to the PEXFHDLC Profile Table A-7.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the HDLCXF Macro to the PEXFHDLC Profile Table A-7.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the HDLCXF Macro to the PEXFHDLC Profile Table A-7.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the SDLCXF Macro to the PEXFSDLC Profile Table A-7.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the SDLCXF Macro to the PEXFSDLC Profile Table A-8.
Converting EnvoyACP/XF Configuration Information to SCF Comparing the SDLCXF Macro to the PEXFSDLC Profile Table A-8.
Converting EnvoyACP/XF Configuration Information to SCF COUP Command Conversion Table A-8.
Converting EnvoyACP/XF Configuration Information to SCF COUP Command Conversion Table A-9.
Converting EnvoyACP/XF Configuration Information to SCF COUP Conversion Examples COUP Conversion Examples The following examples show how COUP configuration commands convert to an SCF configuration file: Example 1 The following COUP commands for configuration of an ADCCP-ABM line on a 3605 controller are similar to the following SCF command file. (For more information about the attributes in this example, see the WAN Subsystem Configuration and Management Manual.
Converting EnvoyACP/XF Configuration Information to SCF COUP Conversion Examples Example 2 The following COUP commands for configuration of an ADCCP-NRM line on a 6110 controller are similar to the following SCF command file. (For more information about the attributes in this example, see the WAN Subsystem Configuration and Management Manual.
Converting EnvoyACP/XF Configuration Information to SCF COUP Conversion Examples SCF Command File ASSUME SUBSYS $ZZWAN ADD PROFILE #MYHDLC, FILE $SYSTEM.SYSnn.PEXFHDLC ADD DEVICE #HDLC4, & TYPE (11, 41), & IOPOBJECT $SYSTEM.SYS01.BSPROCO , & PROFILE MYHDLC, & CLIP 2, & LINE 1, & CPU 0, & ALTCPU 1, & ADAPTER SWAN001A, & RECSIZE 256 START #HDLC4 For SWAN hardware clip-num will be 1 to 3. For SWAN 2 hardware clip-num will be 1 to 6.
Converting EnvoyACP/XF Configuration Information to SCF SYSGEN-to-SCF Conversion Guide SYSGEN-to-SCF Conversion Guide For the G01.00 release, most devices are preconfigured. This subsection explains, for those processes that you can configure, how D-series CONFTEXT paragraphs correspond to G-series SCF object types for the EnvoyACP/XF subsystem. CONFTEXT Paragraph Conversion Table A-10 correlates D-series CONFTEXT paragraphs with their corresponding G-series SCF object types.
Converting EnvoyACP/XF Configuration Information to SCF Default Values for SYSGEN Macros Default Values for SYSGEN Macros Table A-11 correlates D-series SYSGEN macros with G-series WAN subsystem profiles for the EnvoyACP/XF subsystem. Table A-11. SYSGEN Macro-to-Profile Correlation D-Series Macro G-Series Profile SCF Attributes and Default Values ADCCPABMXF PEXFAABM Same as Table A-5 on page A-4. ADCCPNRMXF PEXFANRM Same as Table A-6 on page A-8. HDLCXF PEXFHDLC Same as Table A-7 on page A-12.
Converting EnvoyACP/XF Configuration Information to SCF SYSGEN Conversion Examples Example 2 The following SYSGEN configuration for an SDLC line attached to a 6110 controller is equivalent to the following SCF command: SYSGEN File Defines: C3651^SDLC = SDLCXF TYPE 11, SUBTYPE 40, INTERRUPT BS^6100^INTERRUPT^XF, RSIZE 128, FULL #; Controllers: CIU1 6110 CIU2 6110 Paths: CSSA1 CSSA1 CIU1-CIU2 CIU1-CIU2 00,01 01,00 Peripherals: $CSM1 CSSA1.0 $CLIP14 CSSA1.
Converting EnvoyACP/XF Configuration Information to SCF SYSGEN Conversion Examples EnvoyACP/XF Configuration and Management Manual—429232-003 A -26
B SCF Command Syntax Summary for EnvoyACP/XF This appendix summarizes the SCF command syntax for EnvoyACP/XF. Commands are listed in alphabetical order.
SCF Command Syntax Summary for EnvoyACP/XF ALTER [ / OUT file-name / ] LINE object-name , attribute-spec attribute-spec is one or more of the following: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ABMSETP { OFF | ON } ADDRESS1 integer ADDRESS2 integer ADDRESS3 integer ADDRESS4 integer ADDRSIZE integer BROADCAST { OFF | ON } CONTROLCARRIER { OFF | ON } DSRTIMER integer DUPLEX { HALF | FULL }
SCF Command Syntax Summary for EnvoyACP/XF INFO [ / OUT file-name / ] LINE object-name [ , DETAIL ] (If DETAIL is specified, all the following attributes are displayed. If you specify any of the following attributes, only that attribute is displayed.
SCF Command Syntax Summary for EnvoyACP/XF STATS STATUS [ / OUT file-name / ] LINE object-name [ RESET ] [ / OUT file-name / ] LINE object-name [ , DETAIL ] STOP [ / OUT file-name / ] LINE object-name SUSPEND [ / OUT file-name / ] LINE object-name SWITCH [ / OUT file-spec / ] PROCESS object-name [ , PATH {A | B} ] [ , CPU cpu-number ] TRACE [ / OUT file-name / ] LINE object-name { , STOP [ , BACKUP ] } { [ , BACKUP ] [ , COUNT count ] [ , NOCOLL ] [ , PAGES pages ] [ , RECSIZE sizes ] [ , SELECT sel
C SCF Error Messages for EnvoyACP/XF This appendix describes SCF error numbers and messages presented by the EnvoyACP/XF subsystem. These errors all have positive error numbers. Errors returned by the EnvoyACP/XF subsystem that have negative error numbers are SCF errors common to many subsystems. Negative-numbered SCF error messages are described in the SCF Reference Manual for G-Series RVUs.
SCF Error Messages for EnvoyACP/XF 502 Resource not configured Cause. The specified CPU/PATH is unavailable. Effect. The command could not be completed. Recovery. Configure the CPU/PATH. 503 Already using the resource Cause. The subsystem is already using the specified CPU/PATH. Effect. The command had no effect. Recovery. None. 504 Resource not available Cause. The specified CPU/PATH is unavailable. Effect. The command could not be completed. Recovery. Contact your HP service provider.
SCF Error Messages for EnvoyACP/XF 507 Invalid value supplied for specified attribute Cause. The value is out of range for the specified attribute. Effect. The command could not be completed. Recovery. Supply a value for the attribute that is within range. 508 Attributes supplied along with DETAIL are redundant Cause. If DETAIL has been supplied, all parameters are returned. Effect. The command completed. Recovery. Do not supply the parameter DETAIL if all information is not required.
SCF Error Messages for EnvoyACP/XF EnvoyACP/XF Configuration and Management Manual—429232-003 C- 4
D PROFILE Displays PEXFAABM -> ADD PROFILE $ZZWAN.#PEXFAABM, FILE $SYSTEM.SYS00.PEXFAABM -> INFO PROFILE $ZZWAN.#PEXFAABM WAN MANAGER Info profile \WILLOW.$ZZWAN.#PEXFAABM No devices or processes are using this profile.
PEXFAABM PROFILE Displays ADDRESS1 1 ADDRESS2 3 ADDRESS3 0 ADDRESS4 0 SPEED 96 RNRTIMER 0 NOAUTOACCEPT NRDYUNCTRL MAXPUS 1 NOOPTION1 NOOPTION2 OPTION3 NOIBMEXTENDED NOABMSETP NOAUTOTESTRESP NOOPTION4 NOACI1 MODEMTIMER 0 RETRIES 3 TIMEOUT 500 POLLINT 50 RNRRETRY WINDOW 7 EnvoyACP/XF Configuration and Management Manual—429232-003 D- 2
PEXFANRM PROFILE Displays PEXFANRM -> ADD PROFILE $ZZWAN.#PEXFANRM, FILE $SYSTEM.SYS00.PEXFANRM -> INFO PROFILE $ZZWAN.#PEXFANRM WAN MANAGER Info profile \WILLOW.$ZZWAN.#PEXFANRM No devices or processes are using this profile.
PEXFANRM PROFILE Displays SPEED 96 RNRTIMER 0 NOAUTOACCEPT NRDYUNCTRL MAXPUS 1 NOOPTION1 NOOPTION2 OPTION3 NOIBMEXTENDED NOABMSETP NOAUTOTESTRESP NOOPTION4 NOACI1 MODEMTIMER 0 RETRIES 3 TIMEOUT 500 POLLINT 50 RNRRETRY WINDOW 7 EnvoyACP/XF Configuration and Management Manual—429232-003 D- 4
PEXFHDLC PROFILE Displays PEXFHDLC -> ADD PROFILE $ZZWAN.#PEXFHDLC, FILE $SYSTEM.SYS00.PEXFHDLC -> INFO PROFILE $ZZWAN.#PEXFHDLC WAN MANAGER Info profile \WILLOW.$ZZWAN.#PEXFHDLC No devices or processes are using this profile.
PEXFHDLC PROFILE Displays SPEED 96 RNRTIMER 0 NOAUTOACCEPT NRDYUNCTRL MAXPUS 1 NOOPTION1 NOOPTION2 OPTION3 NOIBMEXTENDED NOABMSETP NOAUTOTESTRESP NOOPTION4 NOACI1 MODEMTIMER 0 RETRIES 3 TIMEOUT 500 POLLINT 50 RNRRETRY WINDOW 7 EnvoyACP/XF Configuration and Management Manual—429232-003 D- 6
PEXFSDLC PROFILE Displays PEXFSDLC -> ADD PROFILE $ZZWAN.#PEXFSDLC, FILE $SYSTEM.SYS00.PEXFSDLC -> INFO PROFILE $ZZWAN.#PEXFSDLC WAN MANAGER Info profile \WILLOW.$ZZWAN.#PEXFSDLC No devices or processes are using this profile.
PEXFSDLC PROFILE Displays ADDRESS4 0 SPEED 96 RNRTIMER 0 NOAUTOACCEPT NRDYUNCTRL MAXPUS 1 NOOPTION1 NOOPTION2 OPTION3 NOIBMEXTENDED NOABMSETP NOAUTOTESTRESP NOOPTION4 NOACI1 MODEMTIMER 0 RETRIES 3 TIMEOUT 500 POLLINT 50 RNRRETRY WINDOW 7 EnvoyACP/XF Configuration and Management Manual—429232-003 D- 8
Glossary ABM. Asynchronous Balanced Mode. A mode of communications within the ADCCP protocol in which two combined stations communicate on a point-to-point link. Either or both stations can issue commands to set up or dissolve the link. During data transmission, the stations function as peers. This mode is also used by the HDLC protocol. ADCCP. Advanced Data Communications Control Procedures. This is the general standard for bit-synchronous protocols. It includes two major modes of operation—ABM and NRM.
CTS Glossary CTS. Clear to send. A signal that comes from a modem, indicating to the computer equipment that the modem is ready to accept data for transmission. DCE. Data circuit-terminating equipment. DCE generally refers to the modem to which a terminal or host computer (called the DTE) is connected. DSC. Dynamic System Configuration. This is an online configuration program introduced in the C-series Guardian 90 operating system. It allows the user to add peripherals to a running system.
information frame Glossary information frame. A frame format used to pass data between two stations. IOP. Input output process. EnvoyACP/XF is considered an IOP. It is an input-output process controlling a bit-synchronous communications line. MCW. Message control word. The first 2 bytes (one word) of the application buffer, used by EnvoyACP/XF to build the control and address fields of the frame. modulo.
RTS Glossary RTS. Request to send. A signal from the host computer or terminal (DTE) to the modem (DCE) requesting permission to transmit data. Permission is granted when the modem turns CTS to ON. SABM. Set Asynchronous Balanced Mode. In ADCCP-ABM and HDLC, the unnumbered frame sent by one station to establish a data link with another station. SDLC. Synchronous Data-Link Control. One of the bit-synchronous communications protocols.
V.25 bis Glossary V.25 bis. A CCITT recommendation for a protocol for setting up a data connection on the general switched telephone network, using a serial modem with automatic calling capability. WAN subsystem. The software that provides access to the ServerNet wide area network concentrator and provides configuration functions for the subsystems attached to the network. window. The window size indicates the maximum number of I-frames that can be sent without acknowledgment.
zero-bit insertion Glossary EnvoyACP/XF Configuration and Management Manual—429232-003 Glossary- 6
Index Numbers 10Base-T Ethernet connections 2-8 3604 controller 2-8 3605 controller 2-8 6100 controller 2-8 Attributes (continued) See also individual attributes 4-6 AUTOACCEPT modifier 3-48 AUTOLOAD modifier 3-11 Automatic calling, V.
D Index Commands nonsensitive 4-5 overview 4-5 sensitive 4-5 Commands, SCF comparison with CMI A-2/A-3 comparison with COUP A-3/A-22 Comments in text COMMENT command A-3 == characters A-3 Communications line interface processor (CLIP) See CLIP Compatibility 4-7 CONFIGURABLE modifier 3-13 CONFTEXT paragraph conversion A-23 ConMgr Ldev 5-32 CONTCF modifier 3-14 Control field, size 3-15 CONTROLCARRIER attribute 5-12 Controllers, communications 2-8 Control, IBM extended 3-17 Converting CMI commands to SCF A-2
F Index Extended addresses 3-10 Extended control 3-17/3-18 EXTENDEDCONTROL attribute 5-13 EXTENDEDCONTROL modifier 3-15 F Files SCF input 4-7 SCF object 4-7 SCF output 4-7 File-system procedures 1-7 FLAGFILL attribute 5-13 FLAGFILL modifier 3-16 Flag, characters 3-16 Format command 4-5 LINE object 4-13 PROCESS object 4-13 FRAMESIZE attribute 5-13 FRAMESIZE modifier 3-16 FULL modifier 3-17 Functional categories, modifiers 3-2/3-3 H HALF modifier 3-17 HDLC protocol 2-3 Help general description 4-5 online
M Index Line-handler process 5-4 associated with each Envoy line 2-11 changing modifiers 2-11 Link-level protocol 2-9 LOCALPOOLPAGES modifier 3-24 Log file, SCF 4-4 M Macro conversion to profiles A-24 Management services, DSM 4-3 MAXLOCALAREA modifier 3-24 MAXPUS modifier 3-24 Menus, help 4-7 Messages, error C-1/C-3 Messages, SPI 4-4 Modem controlled carrier 3-14 full-duplex and half-duplex 3-17 V.
O Index O OBEY files, comment text in A-3 Objects aborting 5-2 attributes 4-6 starting, stopping, and changing 1-6 determining names of 4-14 hierarchy of 4-12 stopping 5-2 subordinate 4-12 Online help 4-7 OPEN procedure 1-7 Operation of SCF 4-6 Operations environment, DSM 4-3 OPTION1 modifier 3-27 OPTION2 modifier 3-30 OPTION3 modifier 3-30 OPTION4 modifier 3-50 OPTION5 modifier 3-30 OPTION6 modifier 3-31 OUT command 4-5 Output destinations, for SCF 4-7 Overview DSM 4-3 SCF 4-3/4-7 SCP 4-4 Owner, subsyste
S Index Retries (continued) level 2 3-23 receiving RNR 3-32 sending RNR 3-26 RNRTIMER attribute 5-15 RNRTIMER modifier 3-33 RR frames enabling 3-18, 3-22 timer 3-19 RS232 modifier 3-36 RS232/RS449 interface 2-8 RS422 modifier 3-36 RSIZE value 5-5 RS-232 interface 2-9, 2-11 RS-422 interface 2-11 RS-449 interface 2-9 RUN command, for starting SCF 4-7 Running modes for SCF 4-7 S SCF attributes definition of 4-6 basic information about 4-3/4-7 error messages, for EnvoyACP/XF C-1/C-3 file name of 4-7 function
T Index Subsystem environment, DSM 4-3 keyword 4-7, 4-14 owner 4-5 Subsystem Control Point See SCP 4-4 Subsystem Programmatic Interface See SPI SUBTYPE modifier 3-2 Supervisor station 2-5 Super-group access 4-5 SUPR modifier 3-40 SUSPEND command 5-35 SUSPEND LINE command 5-35 SUSPENDED state 4-14 SWAN concentrator 5-5 line 2-8 SWINCARRIER attribute 5-16 SWINCARRIER modifier 3-40 SWITCH command 5-35 SWITCH PROCESS command 5-36 SWITCHED attribute 5-16 SWITCHED modifier 3-41 SWOUTCARRIER attribute 5-16 SWOUT
X Index X X21 modifier 3-48 XFERTIMER attribute 5-17 XFERTIMER modifier 3-47 XLATE attribute 5-17 XLATELENGTH attribute 5-17 XLATEOFFSET attribute 5-17 XPAGES modifier 3-48 X.21 driver 2-8 X.21 interface 2-8, 2-9 Special Characters $SYSTEM.SYSTEM.
