CP6100 Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the CP6100 subsystem on HP Integrity Nonstop™ NS-series servers and HP Nonstop™ S-series servers. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the CP6100 subsystem and a quick-reference section showing the command syntax. Product Version F40 Supported Release Version Updates (RVUs) This manual supports G06.
Document History Part Number Product Version Published 420007-001 SCF F40 August 1998 426741-001 F40 May 2000 426741-002 F40 September 2003 426741-003 F40 June 2005
CP6100 Configuration and Management Manual Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information About This Manual ix Who Should Use This Manual What’s in This Manual ix Notation Conventions x Examples Figures Tables vii ix 1. Configuration Quick Start Task Summary 1-1 Assumptions 1-1 Log On to the NonStop Server and Obtain SWAN Information Add a CP6100 Profile 1-4 Add a CP6100 Device 1-4 Start the CP6100 Line 1-5 2.
3. Configuring the CP6100 Subsystem (continued) Contents 3. Configuring the CP6100 Subsystem (continued) Creating a CP6100 Line-Handler Process Adding a CP6100 Profile 3-4 Adding a CP6100 Device 3-5 Starting the CP6100 Line 3-7 3-3 4. ADCCP Protocol and Modifiers PCP6ADCP Profile 4-1 ADCCP Modifiers 4-2 5. BSC Protocol and Modifiers PCP6BSC Profile 5-1 BSC Modifiers 5-2 6. MPS-B Protocol and Modifiers PCP6MPSB Profile 6-1 MPS-B Modifiers 6-1 7.
Contents 8.
9.
B. SCF Command Summary for CP6100 Contents B. SCF Command Summary for CP6100 ABORT Command B-1 ACTIVATE Command B-1 ALTER Command B-1 INFO Command B-1 START Command B-1 STATS Command B-2 STATUS Command B-2 STOP Command B-2 SUSPEND Command B-2 SWITCH Command B-2 TRACE Command B-3 VERSION Command B-3 C.
Tables (continued) Contents Tables (continued) Table 4-1. Table 5-1. Table 6-1. Table 7-1. Table 8-1. Table 8-2. Table 8-3. Table 8-4. Table 9-1. Table 9-2. Table 9-3. Table C-1. Table C-2.
What’s New in This Manual Manual Information CP6100 Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the CP6100 subsystem on HP Integrity Nonstop™ NS-series servers and HP Nonstop™ S-series servers. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the CP6100 subsystem and a quick-reference section showing the command syntax.
What’s New in This Manual • • • • • • New and Changed Information Section 3, Configuring the CP6100 Subsystem HIGHPIN OFF on page 7-7 Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF) Appendix A, CP6100 Subsystem Error Messages Appendix C, Moving to G-Series or H-Series RVUs Glossary CP6100 Configuration and Management Manual—426741-003 viii
About This Manual The CP6100 Configuration and Management Manual describes how to plan, configure, and manage the CP6100 subsystem and includes: • • • • A configuration “quick start” that provides the basic information required to enable you to quickly and easily define and start the CP6100 subsystem An explanation of the major features and capabilities of the CP6100 subsystem An explanation of how to configure the CP6100 subsystem A description of the Subsystem Control Facility (SCF) interactive interfac
Where to Get More Information About This Manual Table 1. Summary of Contents (page 2 of 2) Section Title This section . . . 6 MPS-B Protocol and Modifiers Provides a brief overview of the MPSB protocol, lists the contents of the PCP6MPSB profile, and describes all MPSB modifiers. 7 LIU Protocol and Modifiers Provides a brief overview of the LIU protocol, lists the contents of the PCP6LIU profile, and describes all LIU modifiers.
General Syntax Notation About This Manual UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words.
General Syntax Notation About This Manual … 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}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
Notation for Messages About This Manual !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. For example: error := FILENAME_COMPARE_ ( filename1:length , filename2:length ) ; !i:i !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
Change Bar Notation About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
1 Configuration Quick Start This section is a configuration quick start for the CP6100 subsystem. This procedure explains how to set up the initial CP6100 processes on an Integrity NonStop NS-series or NonStop S-series server. For an overview of the CP6100 subsystem, see Section 2, Overview of the CP6100 Subsystem To help you complete the configuration tasks quickly, this section recommends you accept the default values provided by the CP6100 subsystem.
Log On to the NonStop Server and Obtain SWAN Information Configuration Quick Start Log On to the NonStop Server and Obtain SWAN Information 1. Log on to the Integrity NonStop NS-series or NonStop S-series server using the super ID (SUPER.SUPER), and enter the correct password at the Password: prompt. > logon super.super Password: 2. Start SCF at the TACL prompt on the Integrity NonStop NS-series or NonStop S-series server: > scf 3.
Log On to the NonStop Server and Obtain SWAN Information Configuration Quick Start c. Record the available WAN line number in the line-num field in Example 1-1, Adding a CP6100 Device. (For example: 1.) d. Record the configured path that you prefer to use in the path-name field in Example 1-1, Adding a CP6100 Device. (For example: A.) You can only use paths that have been configured. The path name is optional. 4.
Configuration Quick Start Add a CP6100 Profile Add a CP6100 Profile A profile defines different modifiers, default values, and ranges of values for the CP6100 subsystem. The CP6100 subsystem supports the following four profiles: PCP6ADCP, PCP6BSC, PCP6MPSB, AND PCP6LIU (Refer to CP6100 Subsystem Management Tools on page 2-6 for the protocols supported by each profile. These type 832 files are located in the sysnn subvolume. The files are released as part of the CP6100 product.
Start the CP6100 Line Configuration Quick Start You can create one or more line devices with the ADD DEVICE command. The following example shows the syntax used to create a CP6100 process named $CP6S1. Example 1-1. Adding a CP6100 Device -> add device $zzwan.#cp6s1, profile profadcp, & -> cpu ___________, & (Step 4b) -> altcpu ___________, & (Step 4b) -> iopobject $system.sysnn.
Configuration Quick Start CP6100 Configuration and Management Manual—426741-003 1 -6 Start the CP6100 Line
2 Overview of the CP6100 Subsystem This section provides an introduction to and describes the subsystem components of the CP6100 subsystem and the protocols supported by CP6100.
Introduction to CP6100 Overview of the CP6100 Subsystem Figure 2-1. The CP6100 Environment CPU 0 CPU 1 Application Application CP6100 CP6100 Y Fabric X Fabric LAN Adapter Ethernet LAN A Ethernet LAN B SWAN Concentrator Protocol Task VST0201.vsd With CP6100, you can establish data links between your NonStop NS-series and NonStop S-series systems and a variety of remote systems, automated teller machines (ATMs), and terminals.
CP6100 Supported Protocols Overview of the CP6100 Subsystem CP6100 Supported Protocols CP6100 supports several different protocols, line configurations, and station types. Table 2-1 summarizes the various combinations of protocols, line configurations, and station types that CP6100 supports. Table 2-1.
Primary CP6100 Protocols Overview of the CP6100 Subsystem Following is a brief description of each of these protocols. Protocol Description ADCCP Developed by the American National Standards Institute (ANSI). The ADCCP line protocol allows a choice of either Normal Response Mode (NRM), Asynchronous Balanced Mode (ABM), or Asynchronous Response Mode (ARM). Each of these ADCCP modes can have extended control or address fields.
Other CP6100 Protocols Overview of the CP6100 Subsystem Protocol Description ARM In this mode, the secondary station can initiate data transmission without explicit permission from the primary station; no poll is required from the primary station. The primary station is responsible for setting up and dissolving the link; otherwise the stations function essentially as peers. Asynchronous response mode applies only to point-to-point lines.
Overview of the CP6100 Subsystem CP6100 Subsystem Management Tools Protocol Description BSCT Provides software for byte-synchronous tributary functions. GFDX Is intended as an enhanced replacement for Envoy Asynchronous Line Supervisor and Envoy Full-Duplex protocols. SWIFT Developed by the Society for Worldwide Interbank Financial Telecommunications.
Event Management Service (EMS) Overview of the CP6100 Subsystem Event Management Service (EMS) EMS is a DSM interface that provides event collection, logging, and distribution facilities. The CP6100 subsystem reports events to EMS. CP6100 subsystem events are described in the Operator Messages Manual. Compaq TSM Note. TSM is not supported on NonStop NS-series servers. OSM is the supported system management tool for NonStop NS-series servers.
Overview of the CP6100 Subsystem Online Expansion and Reconfiguration CP6100 Configuration and Management Manual—426741-003 2 -8
3 Configuring the CP6100 Subsystem This section provides an overview of the CP6100 subsystem and describes how to configure the CP6100 subsystem on NonStop NS-series or NonStop S-series servers.
Configuring the CP6100 Subsystem Concentrators Supported Concentrators Supported For Integrity NonStop NS-series or NonStop S-series servers, the supported concentrators are the SWAN concentrator and the SWAN 2 concentrator. For information about configuring the SWAN or SWAN 2 concentrator, see the WAN Subsystem Configuration and Management Manual.
Profile Object Files and Associated Protocols Configuring the CP6100 Subsystem Profile Object Files and Associated Protocols The PROFILE object in the WAN subsystem specifies the protocol to be used on that particular line. Profiles contain modifiers and default modifier values for the different CP6100 protocols. You create a profile from an object file provided by HP or from a previously created profile. This subsection introduces the object files provided by HP for CP6100 Note.
Configuring the CP6100 Subsystem Adding a CP6100 Profile Adding a CP6100 Profile You can create a profile for a CP6100 line-handler process using one of the profiles listed in Table 3-1. You can also create a new profile from an existing profile, or you can create your own profile. For complete information about profiles, refer to the WAN Subsystem Configuration and Management Manual. This subsection describes how to create a profile using the PCP6ADCP profile.
Configuring the CP6100 Subsystem Adding a CP6100 Device The following is an example of how to alter the default value of the MAXFRAME modifier when adding the PCP6ADCP profile to the WAN subsystem. ADD PROFILE $ZZWAN.#PCP6ADCP, FILE $SYSTEM.SYS00.PCP6ADCP, MAXFRAME 200 For information on the syntax of this SCF command, refer to the ADD command in the WAN Subsystem Configuration and Management Manual.
Configuring the CP6100 Subsystem Adding a CP6100 Device alt-cpu-num is the CPU number where the backup device will normally execute. clip-num is the CLIP to be used by this device. cpu-num is the CPU number where the device will normally execute. obj-file-name is the name of the HP-supplied object file for the selected line type. line-num is the line number on the selected CLIP to be used by this device. line-num must not have been previously selected for use by another device.
Configuring the CP6100 Subsystem Starting the CP6100 Line CLIP 1, LINE 1, ADAPTER SWAN002A, PATH A, SWOUTCARRIER, FLAGIDLE For information on the syntax of this SCF command, refer to the ADD command in the WAN Subsystem Configuration and Management Manual. Starting the CP6100 Line You start a CP6100 line-handler process by starting it in the WAN subsystem. START DEVICE Command To start a CP6100 line-handler process, use the WAN subsystem SCF START DEVICE command.
Configuring the CP6100 Subsystem Starting the CP6100 Line CP6100 Configuration and Management Manual—426741-003 3 -8
4 ADCCP Protocol and Modifiers This section gives a brief overview of the ADCCP protocol and describes the modifiers you can use to modify the functions of an ADCCP communications line. PCP6ADCP Profile The PCP6ADCP profile configures the line for the Advanced Data Communications Control Procedure (ADCCP) protocol, which is a bit-synchronous data communications line protocol developed by the American National Standards Institute (ANSI) and defined in ANSI Standard X3.66-1979.
ADCCP Modifiers ADCCP Protocol and Modifiers ADCCP Modifiers This subsection describes each modifier contained in the PCP6ADCP profile and all other modifiers that can be used with the ADCCP protocol. For detailed information on using the Subsystem Control Facility (SCF) to alter the default values for the duration of the current session, refer to Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF).
ADCCP Protocol and Modifiers ADCCP Modifiers Figure 4-1. Address Field Format When the address field is greater than 1 byte in length, the last byte must contain an odd value. An odd value in any byte other than the last byte (which makes the least significant bit a 1) will cause unpredictable results. You should use the default setting for this modifier unless some addresses are greater than 1 byte (octet), in which case variable-length addresses are required.
ADCCP Protocol and Modifiers ADCCP Modifiers ARMMODE See ABMMODE, ARMMODE, or NRMMODE on page 4-2. AUTOCLOSE Default: AUTOCLOSE Units: None See also: NOAUTOCLOSE This modifier specifies that CP6100 CAP will CLOSE all file system OPENs if the CLIP must be downloaded for error-recovery.
ADCCP Protocol and Modifiers ADCCP Modifiers download file, the operation terminates. BITSYNC is the default operational class for the PCP6ADCP profile. When the BITSYNC modifier is included in the PROFILE file, the ConMgr process checks to make sure that the operational modifier specified in the microcode file matches the line configuration. If they do not match, the microcode download does not occur; however, you will not receive an SCF error.
ADCCP Protocol and Modifiers ADCCP Modifiers CLBWINDOW n Default: 1 Units: Read buffers Range: 1 through 8 This modifier specifies the number of read buffers allocated. The value n is the size of the window. CLIPTRACEREC n Default: 32 Units: Bytes Range: 16 through 256 See also: CLBFRAMESIZE n on page 4-5 This modifier specifies the maximum number of bytes to be placed in an LIU trace record. The CLIPTRACEREC value may not exceed CLBFRAMESIZE.
ADCCP Protocol and Modifiers ADCCP Modifiers DSRTIMER n Default: 300 Units: 0.01 seconds Range: 0 through 32767 This modifier specifies the time interval that the LIU waits for a data set ready (DSR) signal to appear following a data terminal ready (DTR) signal. If DSR does not appear before the interval expires, the function is terminated and DTR is reset. The default timeout is 3 seconds. If n is 0, no interval occurs and the LIU waits indefinitely for DSR.
ADCCP Protocol and Modifiers ADCCP Modifiers HALFDUPLEX Default: Full Duplex Units: None Range: N/A This modifier selects half-duplex modem operation. The request-to-send (RTS) modem signal is turned on before sending a frame and is reset immediately after sending the last frame. HIGHPIN OFF Default: Currently unsupported Units: None Range: N/A This modifier allows the CP6100 subsystem to function at either a low process identification number (PIN) or a high PIN.
ADCCP Protocol and Modifiers ADCCP Modifiers L2RETRY n Default: n=3 Units: None Range: 0 through 255 This modifier specifies the number of times the ADCCP protocol requests an acknowledgment when the remote station does not respond to a link command or a poll (that is, when the T1TIMER expires). This modifier does not apply to the modesetting commands such as Set Normal Response Mode (SNRM), Set Asynchronous Balanced Mode (SABM), Set Initialization Mode (SIM), and Disconnect (DISC).
ADCCP Protocol and Modifiers ADCCP Modifiers MULTI $Line-name Default: None Units: None Range: N/A This modifier assigns multiple lines to one CP6100 line-handler process and allows one CP6100 I/O process to control as many as six LIUs on a SWAN concentrator. Specify MULTI for up to six lines that you want to group under a single CP6100 linehandler process, except for the first line in the group.
ADCCP Protocol and Modifiers ADCCP Modifiers NOCARRFATAL Default: NO Units: None Range: NO/YES See also: SWINCARRIER on page 4-14 This modifier causes the modem status to be reported immediately when a modem error occurs (loss of CTS or DCD) and the link goes to the disconnect state. DSR is always required. By default, CSS ADCCP continues operating. The NOCARRFATAL modifier applies only to links specified as full-duplex, with a private connection, and SWINCARRIER not selected.
ADCCP Protocol and Modifiers ADCCP Modifiers NRMMODE See ABMMODE, ARMMODE, or NRMMODE on page 4-2. POLL Default: POLL Units: None Range: N/A See also: IDLETIMER n on page 4-8 This modifier determines whether periodic polls are sent to a remote station when the link is idle. POLL enables a heartbeat RR frame for ABM and ARM support at IDLETIMER intervals when the link is idle. By default, the POLL modifier is in effect.
ADCCP Protocol and Modifiers ADCCP Modifiers RSIZE 80 Default: None Units: Bytes Range: N/A This modifier specifies the record length in bytes, which is always 80 bytes for CP6100. SNAXLATE Default: No SNAX translation Units: None Range: N/A See also: TRANSLATE on page 4-16 This modifier specifies that the TRANSLATE modifier is on and that the requester not ready (RNR) timer for SNA is set to 255 seconds. By default, SNAXLATE is off.
ADCCP Protocol and Modifiers ADCCP Modifiers STARTDOWN Default: None Units: None Range: N/A See also: STARTBOOT on page 4-13 This modifier specifies that when the system is cold-started, the LIU is not logically started but rather is left in the stopped state. You can use SCF to start the LIU. If you specify this modifier you must also specify STARTBOOT.
ADCCP Protocol and Modifiers ADCCP Modifiers request from the application; the request completes when the DSR signal indicates an incoming call. A MODEM CONTROL disconnect request causes DTR to drop, disconnecting the call. If the line is not switched, the START or MODEM CONTROL request may cause the ADCCP protocol task to assert DTR through the modem. If the DSR signal does not appear within the interval specified for DSRTIMER, the START request completes with a timeout.
ADCCP Protocol and Modifiers ADCCP Modifiers TESTINT Default: 1000 Units: .01 seconds Range: 0 through 32767 This modifier specifies the interval for probing the status of the line. A value of zero means the line is never probed. THRESHOLD n Default: n = 500 Units: None Range: 100 through 32767 This modifier specifies the transmit and receive frame count that triggers the asynchronous reporting of line quality statistics.
ADCCP Protocol and Modifiers ADCCP Modifiers TWA Default: TWS Units: None Range: N/A See also: TWS on page 4-17 This modifier selects two-way alternate (TWA) frame transmission, which requires a carrier drop or a link idle condition before a frame is sent. This modifier is meaningful only for Normal Response Mode (NRM). TWS Default: TWS Units: None Range: N/A See also: TWA on page 4-17 This modifier selects two-way simultaneous (TWS) frame transmission and is only meaningful for NRM.
ADCCP Protocol and Modifiers ADCCP Modifiers WINDOW n Default: n=3 Units: None Range: 1 through 7 (basic control mode) 1 through 127 (extended control mode) See also: MAXFRAME n on page 4-9 This modifier specifies the maximum number of I-frames that can be sent without receiving an acknowledgment. The value of WINDOW depends on the value of the MAXFRAME modifier. XFERTIMER n Default: n = 100 Units: .
ADCCP Protocol and Modifiers ADCCP Modifiers XOFFSET n Default: n=0 Units: Bytes Range: 0 through 2045 See also: TRANSLATE on page 4-16, and XLENGTH This modifier specifies an offset into the I-field at which to begin EBCDIC-to-ASCII translation.
ADCCP Protocol and Modifiers CP6100 Configuration and Management Manual—426741-003 4- 20 ADCCP Modifiers
5 BSC Protocol and Modifiers This section gives a brief overview of the BSC protocol and describes the modifiers that you can use to modify the functioning of a BSC communications line. Note. The PCP6BSC profile is used to configure CP6100 for BSC point-to-point operation. For multipoint BSC-Supervisory or BSC-Tributary protocols, you must use the corresponding protocol download module (DLM) and the PCP6LIU profile.
BSC Protocol and Modifiers BSC Modifiers BSC Modifiers This subsection describes each modifier contained in the PCP6BSC profile and all other modifiers that can be used with the BSC protocol. For detailed information on using the Subsystem Control Facility (SCF) to alter the default values for the duration of the current session, refer to Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF).
BSC Modifiers BSC Protocol and Modifiers BSCASCII Default: EBCDIC This modifier specifies ASCII for the transmission code and control characters. Even if the line uses EBCDIC, the application uses ASCII for its data and special characters. The BSC protocol translates the output buffer from ASCII to EBCDIC and translates data arriving on the line from EBCDIC to ASCII. Only transparent text is not subject to translation.
BSC Protocol and Modifiers BSC Modifiers BSCCONTROLCF Default: NOBSCCONTROLCF Units: None Range: N/A The BSCCONTROLCF modifier specifies that if half-duplex mode is used, the bisynchronous driver waits for the data carrier detect (DCD) signal to drop before raising the request to send (RTS) signal. The BSCCONTROLCF option is in effect if you specify it at system generation or set it with a procedure call.
BSC Protocol and Modifiers BSC Modifiers BSCHALF Default: BSCHALF Units: None Range: N/A See also: BSCFULL on page 5-4 This modifier specifies a half-duplex line. For half-duplex lines, CP6100 raises the RTS signal before each transmission and waits for the CTS signal before transmitting data. The CTS signal drops after the RTS signal drops.
BSC Protocol and Modifiers BSC Modifiers BSCLRC8 Default: Frame-checking sequence (FCS) is CRC16 Units: None Range: N/A This modifier specifies that LRC is used for the FCS. By default, this modifier is not in effect (that is, CRC16 is used for the FCS). BSCLRC8 can be used only with ASCII code. BSCNONSTOPOFF Default: BSCNONSTOPOFF Units: None Range: N/A See also: BSCNONSTOPON on page 5-6 This modifier disables the fault-tolerant processing in the CLIP.
BSC Protocol and Modifiers BSC Modifiers BSCPPSW Default: BSCPPNSW Units: None Range: N/A This modifier specifies a switched line. For switched lines, CP6100 sends a DLE EOT and drops the DTR signal when a disconnect or stop line request is received. When a DLE EOT is received, CP6100 drops the DTR signal and rejects I/O requests. When the DTR signal is cleared, CP6100 waits until the DSR signal drops or a timeout occurs.
BSC Protocol and Modifiers BSC Modifiers BSCSECONDARY Default: Primary station Units: None Range: N/A This modifier specifies the station as a secondary station. By default, the station is primary. BSCSYNCS n Default: 3 Units: None Range: 3 through 255 This modifier specifies the number of SYN characters that precede a transmission. This number includes the initial PAD characters that begin and end each message.
BSC Protocol and Modifiers BSC Modifiers CLBFRAMESIZE n Default: 128 Units: Words Range: 150 through 600 See also: CLIPTRACEREC n on page 5-10 This modifier changes the framesize sent to the CLIP. The value n specifies the maximum number of words to be transferred in a frame. If you specify a value larger than the range, the software changes the value to the maximum allowed. Likewise, if you specify a value smaller than the range, the application uses the minimum value.
BSC Protocol and Modifiers BSC Modifiers CLIPTRACEREC n Default: 80 Units: Bytes Range: 16 through 256 See also: CLBFRAMESIZE n on page 5-9 This modifier specifies the maximum number of bytes to be placed in an LIU trace record. The CLIPTRACEREC value may not exceed CLBFRAMESIZE. Any attempt to exceed this value results in CLIPTRACEREC being limited automatically to the same value as CLBFRAMESIZE.
BSC Protocol and Modifiers BSC Modifiers HIGHPIN OFF Default: Currently unsupported Units: None Range: N/A This modifier allows the CP6100 subsystem to function at either a low process identification number (PIN) or a high PIN. The CP6100 subsystem defaults to running at a high PIN if the CPU was configured for more than 256 PINs and the high PINs have not already been assigned to other processes. Note.
BSC Protocol and Modifiers BSC Modifiers MULTI $Line-name Default: None Units: None Range: N/A This modifier assigns multiple lines to one CP6100 line-handler process and allows one CP6100 I/O process to control as many as six LIUs on a SWAN concentrator. Specify MULTI for up to six lines that you want to group under a single CP6100 linehandler process, except for the first line in the group.
BSC Protocol and Modifiers BSC Modifiers PROGRAM filename Default: C1095P00 Units: None Range: N/A This modifier supplies the simple file name of the NonStop Kernel microcode file to substitute for the one defined by the profile. RETRIES Default: 3 Units: None Range: 0 through 63 This modifier specifies the number of times the I/O process is to try a request before reporting an error.
BSC Protocol and Modifiers BSC Modifiers STARTDOWN Default: None Units: None Range: N/A See also: STARTBOOT on page 5-13 This modifier specifies that when the system is cold-started, the LIU is not logically started but rather is left in the stopped state. You can use SCF to start the LIU. If you specify this modifier you must also specify STARTBOOT. TESTINT Default: 1000 Units: .01 seconds Range: 0 through 32767 This modifier specifies the interval for probing the status of the line.
6 MPS-B Protocol and Modifiers This section gives a brief overview of the MPS-B protocol and describes the modifiers that you can use to modify the function of an MPS-B communications line. PCP6MPSB Profile The PCP6MPSB profile configures the line for the 6100 Multipoint SupervisorBurroughs (MPS-B) protocol, which allows an application process executing in a NonStop system to act as the supervisor station on a multipoint asynchronous or bytesynchronous line.
MPS-B Protocol and Modifiers MPS-B Modifiers using the Subsystem Control Facility (SCF) to alter the default values for the duration of the current session, refer to Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF). For detailed information on permanently altering the modifier default values contained in the PCP6MPSB profile or creating a new profile, refer to the WAN Subsystem Configuration and Management Manual.
MPS-B Protocol and Modifiers MPS-B Modifiers AUTOLOAD Default: AUTOLOAD Units: None See also: NOAUTOLOAD This modifier specifies that the CLIP software is to be automatically downloaded if the CLIP sends a STATUS PROBE message with a status error greater than 1. Note. AUTOLOAD will prevent you from obtaining a CLIP dump if the CLIP crashes, because the autoload will occur before the dump can be obtained.
MPS-B Protocol and Modifiers MPS-B Modifiers CLBWINDOW n Default: 1 Units: Read buffers Range: 1 through 8 This modifier specifies the number of read buffers allocated. The value n is the size of the window. CLIPTRACEREC n Default: 90 Units: Bytes Range: 16 through 256 See also: CLBFRAMESIZE n on page 6-3 This modifier specifies the maximum number of bytes to be placed in an LIU trace record.
MPS-B Protocol and Modifiers MPS-B Modifiers HIGHPIN OFF Default: Currently unsupported Units: None Range: N/A This modifier allows the CP6100 subsystem to function at either a low process identification number (PIN) or a high PIN. The CP6100 subsystem defaults to running at a high PIN if the CPU was configured for more than 256 PINs and the high PINs have not already been assigned to other processes. Note.
MPS-B Modifiers MPS-B Protocol and Modifiers MPSBAUTODISABLE Default: MPSBNOAUTODISABLE Units: None Range: N/A This modifier specifies that stations are automatically disabled upon completion of a normal read operation. MPSBBAUDn Default: 1200 Units: None Range: N/A This modifier specifies the baud rate for the LIU-supplied transmission (Tx) clock.
MPS-B Protocol and Modifiers MPS-B Modifiers MPSBCHARACTERSIZE n Default: 7 (parity not included) Units: Bits Range: 0 through 8 This modifier specifies the number of bits that make up a character during transmission. The recommended character size for even and odd parity is 7. For no parity, it is 8. If you specify a character size of 0, the character size is 7. MPSBCONNECTTIMEOUT n Default: 3000 (30 seconds) Units: .
MPS-B Protocol and Modifiers MPS-B Modifiers MPSBFULL Default: MPSBHALF Units: None Range: N/A This modifier specifies full-duplex mode (that is, RTS is always on). MPSBHALF Default: MPSBHALF Units: None Range: N/A See also: MPSBFULL on page 6-8 This modifier specifies half-duplex (that is, switched RTS) operation for the line. By default, the operation is half-duplex.
MPS-B Protocol and Modifiers MPS-B Modifiers MPSBNONE Default: MPSBEVEN Units: None Range: N/A See also: MPSBODD on page 6-9 This modifier specifies that parity-checking is not performed for the line. MPSBNONSTOPOFF Default: MPSBNONSTOPOFF Units: None Range: N/A This modifier specifies that the CLIP does not support fault-tolerant processing.
MPS-B Protocol and Modifiers MPS-B Modifiers MPSBPACE n Default: 0 Units: None Range: 0 through 32767 This modifier specifies the maximum number of consecutive write requests that can be performed by MPS-B before all stations are polled again. If n is zero, the application must issue a Halt Poll request prior to any write request. MPSBPARITY n Default: MPSBEVEN Units: None Range: 0 through 2 This modifier specifies the parity.
MPS-B Protocol and Modifiers MPS-B Modifiers MPSBSWITCHED Default: MPSBLEASED Units: None Range: N/A This modifier specifies a switched line with a modem (controlled DTR). MPSBSYNC n Default: 0 Units: Characters Range: 0, 3 to 255 This modifier specifies the number of leading synchronization characters (SYNs) inserted on transmission. A value of 0 for n specifies asynchronous operation. MPSBTIMEOUT n Default: 270 (2.7 seconds) Units: .
MPS-B Protocol and Modifiers MPS-B Modifiers When using the MULTI modifier, remember the following: • • Do not mix asynchronous and synchronous lines. Do not allow different data communications products to be controlled by the same line-handler process. NOAUTOCONF Default: AUTOCONF Units: None Range: N/A See also: AUTOCONF on page 6-2 This modifier causes the CP6100 line-handler process to send the current configuration block to the LIU only in response to a WRITEREAD file-system request.
MPS-B Protocol and Modifiers MPS-B Modifiers RETRIES Default: 3 Units: None Range: 0 through 63 This modifier specifies the number of times the I/O process is to try a request before reporting an error. RSIZE 80 Default: None Units: Bytes Range: N/A This modifier specifies the record length in bytes, which is always 80 bytes for CP6100.
MPS-B Protocol and Modifiers MPS-B Modifiers TESTINT Default: 1000 Units: .01 seconds Range: 0 through 32767 This modifier specifies the interval for probing the status of the line. A value of zero means the line is never probed. TIMEOUT Default: 3000 Units: .01 seconds Range: 0 through 32767 This modifier specifies the interval that the I/O process is to wait for a response to a request before retrying.
7 LIU Protocol and Modifiers This section gives a brief overview of the LIU protocol and describes the modifiers you can use to modify the functions of an LIU communications line PCP6LIU Profile The PCP6LIU profile is a generic profile used with all CP6100 CLIP protocol download modules and user-developed CLIP protocols. Table 7-1 lists the default modifiers and values for the PCP6LIU profile provided by HP. Table 7-1.
LIU Protocol and Modifiers LIU Modifiers LIU Modifiers This subsection describes each modifier contained in the PCP6LIU profile and all other modifiers that can be used with the LIU protocol. For detailed information on using the Subsystem Control Facility (SCF) to alter the default values for the duration of the current session, refer to Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF).
LIU Protocol and Modifiers LIU Modifiers AUTOCLOSE Default: AUTOCLOSE Units: None See also: NOAUTOCLOSE on page 7-8 This modifier specifies that CP6100 CAP will CLOSE all file system OPENs if the CLIP must be downloaded for error-recovery.
LIU Protocol and Modifiers LIU Modifiers BITSYNC Default: ANY Units: None Range: N/A See also: ASYNC on page 7-2, and BYTESYNC on page 7-4 This modifier is an operational class modifier that specifies the operational class of the LIU download module as bit-synchronous. If an appropriate module is not found in the download file, the operation terminates. BITSYNC is the default operational class for the PCP6ADCP profile.
LIU Protocol and Modifiers LIU Modifiers CLBFRAMESIZE n Default: 256 words Units: Words Range: 150 through 600 (for LIU-1) See also: CLIPTRACEREC n on page 7-6 This modifier changes the framesize sent to the CLIP. The value n specifies the maximum number of words to be transferred in a frame. If you specify a value larger than the range, the software changes the value to the maximum allowed. Likewise, if you specify a value smaller than the range, the software uses the minimum value.
LIU Protocol and Modifiers LIU Modifiers CLIPTRACEREC n Default: 32 Units: Bytes Range: 16 through 256 See also: CLBFRAMESIZE n on page 7-5 This modifier specifies the maximum number of bytes to be placed in an LIU trace record. The CLIPTRACEREC value may not exceed CLBFRAMESIZE. Any attempt to exceed this value results in CLIPTRACEREC being limited automatically to the same value as CLBFRAMESIZE.
LIU Protocol and Modifiers LIU Modifiers HIGHPIN OFF Default: Currently unsupported Units: None Range: N/A This modifier allows the CP6100 subsystem to function at either a low process identification number (PIN) or a high PIN. The CP6100 subsystem defaults to running at a high PIN if the CPU was configured for more than 256 PINs and the high PINs have not already been assigned to other processes. Note.
LIU Protocol and Modifiers LIU Modifiers MULTI $Line-name Default: None Units: None Range: N/A This modifier assigns multiple lines to one CP6100 line-handler process and allows one CP6100 I/O process to control as many as six LIUs on a SWAN concentrator. Specify MULTI for up to six lines that you want to group under a single CP6100 line-handler process, except for the first line in the group.
LIU Protocol and Modifiers LIU Modifiers NOAUTOLOAD Default: AUTOLOAD Units: None Range: N/A This modifier specifies that the CLIP software is not to be automatically downloaded after system generation. NOAUTOSTOP Default: See description Unit: None Range: N/A This modifier specifies that the CP6100 CAP will not send a line task STOP message to the CLIP when the last OPEN performs a CLOSE. This modifier is not in effect by default.
LIU Protocol and Modifiers LIU Modifiers RSIZE 80 Default: None Units: Bytes Range: N/A This modifier specifies the record length in bytes, which is always 80 bytes for CP6100. STARTBOOT Default: None Units: None Range: N/A See also: STARTDOWN on page 7-10 This modifier specifies that when the system is cold-started, the LIU is not downloaded automatically but rather is left in the boot state. You can use SCF to load and start the LIU.
LIU Protocol and Modifiers LIU Modifiers TIMEOUT Default: 3000 Units: .01 seconds Range: 0 through 32767 This modifier specifies the interval that the I/O process is to wait for a response to a request before retrying. TYPE (m,n) Default: m must be 51; n must be 0 Units: None Range: N/A For SWAN concentrators, this modifier is mandatory and must be TYPE (51,0), indicating that the concentrator is managed by the CP6100 subsystem.
LIU Protocol and Modifiers CP6100 Configuration and Management Manual—426741-003 7- 12 LIU Modifiers
8 Managing CP6100 Using the Subsystem Control Facility (SCF) This section describes the Subsystem Control Facility (SCF) interface to the CP6100 subsystem and provides SCF command syntax. Depending on your RVU, refer to the SCF Reference Manual for G-Series RVUs or the SCF Reference Manual for G-Series RVUs for general information about running SCF.
Managing CP6100 Using the Subsystem Control Facility (SCF) Overview of the CP6100 Subsystem SCF Interface Overview of the CP6100 Subsystem SCF Interface The CP6100 subsystem SCF interface is provided to configure, control, and display information about configured objects within the CP6100 subsystem.
Managing CP6100 Using the Subsystem Control Facility (SCF) CP6100 Subsystem Objects Figure 8-1. SCF Interface to CP6100 Terminal OBEY File SCF Log File SCP WAN Subsystem m CP6100 Subsystem WAN Manager ($ZZWAN) CP6100 Process VST0801.vsd CP6100 Subsystem Objects The SCF objects for the CP6100 subsystem correspond to process components within the subsystem.
Managing CP6100 Using the Subsystem Control Facility (SCF) Object States PROCESS Object The PROCESS object defines a CP6100 process. The PROCESS name is the same as the name of the LINE it controls. The PROCESS can be addressed by using line-name as follows: PROCESS line-name. LINE Object LINE is a communications line. The LINE name identifies the specific CP6100 line configured in the system and assigned through the WAN subsystem.
Managing CP6100 Using the Subsystem Control Facility (SCF) SCF Commands and Objects The following states are recognized by the CP6100 subsystem: State Description ABORTING The object is being aborted. The object is responding to an ABORT command or some type of malfunction. In this state, no new links are allowed and drastic measures may be underway to reach the STOPPED state. This state is irrevocable. DIAGNOSING The object is in a subsystem-defined test mode entered via the DIAGNOSE command.
Managing CP6100 Using the Subsystem Control Facility (SCF) Sensitive and Nonsensitive Commands Table 8-2. CP6100 Commands and Object Types Object Types CP6100 Command PROCESS LINE STATUS X STOP X SUSPEND X SWITCH X TRACE VERSION X X Sensitive and Nonsensitive Commands SCF commands are either sensitive or nonsensitive.
Managing CP6100 Using the Subsystem Control Facility (SCF) Wild-Card Support Table 8-3 lists the sensitive and nonsensitive CP6100 SCF commands. Table 8-3. Sensitive and Nonsensitive CP6100 SCF Commands Sensitive Commands Nonsensitive Commands ABORT INFO ACTIVATE STATS (without the RESET option) ALTER STATUS START VERSION STATS (with the RESET option) STOP SUSPEND SWITCH TRACE Wild-Card Support The CP6100 subsystem does not support any wild-card notation.
Managing CP6100 Using the Subsystem Control Facility (SCF) ABORT Command ABORT Command The ABORT command terminates the operation of LINE objects as quickly as possible—only enough processing is done to ensure the security of the subsystem. The objects are left in the STOPPED state. ABORT is a sensitive command.
Managing CP6100 Using the Subsystem Control Facility (SCF) ACTIVATE Command ACTIVATE Command The ACTIVATE command removes restrictions imposed by a SUSPEND command and returns the LINE to the STARTED state. ACTIVATE is a sensitive command. Command Syntax for the ACTIVATE Command The ACTIVATE command has the following syntax: ACTIVATE [ /OUT file-spec / ] [ LINE line-name ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Managing CP6100 Using the Subsystem Control Facility (SCF) ALTER Command ALTER Command The ALTER command changes the values of the modifiers of an existing object. This command changes only the specified modifiers of the target object. ALTER is a sensitive command.
Managing CP6100 Using the Subsystem Control Facility (SCF) Modifier Set for the ALTER LINE ADCCP Command Modifier Set for the ALTER LINE ADCCP Command The modifier set for the ALTER LINE ADCCP is one or more of the following modifier name and value combinations. The modifiers are listed alphabetically and are described in Section 4, ADCCP Protocol and Modifiers.
Managing CP6100 Using the Subsystem Control Facility (SCF) Modifier Set for the ALTER LINE BSC Command Modifier Set for the ALTER LINE BSC Command The modifier set for the ALTER LINE BSC is one or more of the following modifier name and value combinations. The modifiers are listed alphabetically and are described in Section 5, BSC Protocol and Modifiers.
Managing CP6100 Using the Subsystem Control Facility (SCF) Modifier Set for the ALTER LINE LIU Command Modifier Set for the ALTER LINE LIU Command The modifier set for the ALTER LINE LIU is one or more of the following modifier name and value combinations. The modifiers are listed alphabetically and are described in Section 7, LIU Protocol and Modifiers.
Managing CP6100 Using the Subsystem Control Facility (SCF) Modifier Set for the ALTER LINE MPSB Command Modifier Set for the ALTER LINE MPSB Command The modifier set for the ALTER LINE MPSB is one or more of the following modifier name and value combinations. The modifiers are listed alphabetically and are described in Section 6, MPS-B Protocol and Modifiers.
Managing CP6100 Using the Subsystem Control Facility (SCF) Command Syntax for the INFO Command Command Syntax for the INFO Command The INFO command has the following syntax: INFO [ /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. LINE line-name specifies information for a particular line.
Managing CP6100 Using the Subsystem Control Facility (SCF) INFO LINE Command Display for the ADCCP Subtype INFO LINE Command Display for the ADCCP Subtype The format of the display for the INFO LINE command for the ADCCP subtype with the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to the applicable protocol section of this manual, for detailed descriptions of these modifiers. CP6100 DETAIL INFO LINE $CPA1 *Opclass...........BITSYNC *Program...........$SYSTEM.
Managing CP6100 Using the Subsystem Control Facility (SCF) INFO LINE Command Display for the BSC Subtype INFO LINE Command Display for the BSC Subtype The format of the display for the INFO LINE command for the BSC subtype with the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to the applicable protocol section of this manual, for detailed descriptions of these modifiers. CP6100 DETAIL INFO LINE $CPB2 *Opclass...........BISYNC *Program...........$SYSTEM.CSS01.
Managing CP6100 Using the Subsystem Control Facility (SCF) INFO LINE Command Display for the LIU Subtype INFO LINE Command Display for the LIU Subtype The format of the display for the INFO LINE command for the LIU subtype with the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to the applicable protocol section of this manual, for detailed descriptions of these modifiers. CP6100 DETAIL INFO LINE $CPL1 *Opclass...........ANY *Program...........$SYSTEM.CSS01.
Managing CP6100 Using the Subsystem Control Facility (SCF) INFO LINE Command Display for the MPSB Subtype INFO LINE Command Display for the MPSB Subtype The format of the display for the INFO LINE command for the MPSB subtype with the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to the applicable protocol section of this manual, for detailed descriptions of these modifiers. CP6100 DETAIL INFO LINE $CPM4 *Opclass...........ASYNC *Program...........$SYSTEM.CSS01.
Managing CP6100 Using the Subsystem Control Facility (SCF) START Command START Command The START command initiates the operation of a LINE. The successful completion of the START command leaves the LINE in the STARTED state. START is a sensitive command. Command Syntax for the START Command The START command has the following syntax: 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.
Managing CP6100 Using the Subsystem Control Facility (SCF) STATS Command STATS Command The STATS command displays statistical information for the specified line. In addition to the statistical information, a timestamp is also returned that indicates when the statistics were last reset for the line. STATS is a nonsensitive command.
Managing CP6100 Using the Subsystem Control Facility (SCF) Display for the STATS LINE Command Display for the STATS LINE Command The display for the STATS LINE command has the following format: CP6100 DETAIL STATS LINE $CPT5 ResetTime....... 13 JUN 1995, 16:32:10.866 SampleTime...... 16 JUN 1995, 10:49:17.936 Total Frames..........47734 Frame Errors..........0 Pool Size.............55098 Max Usage.............450 Status Probe Errors...0 No Buffer Errors......0 Invalid Fun Errors....0 Modem Errors.........
Managing CP6100 Using the Subsystem Control Facility (SCF) Display for the STATS LINE Command No Buffer Errors is the number of requests that have failed because no buffers were available. Invalid Fun Errors is the number of invalid function frames received by the CLIP. Modem Errors is the number of modem errors encountered. Input Msgs is the number of input messages at the LIU level. Input Errors is the number of input errors at the LIU level.
Managing CP6100 Using the Subsystem Control Facility (SCF) Considerations for the STATS Command Output Errors is the number of output errors at the LIU level. Considerations for the STATS Command • • If RESET is specified, all statistical counters are reset. The STATS command alone is not a sensitive command. However, the STATS command with the RESET option is sensitive.
Managing CP6100 Using the Subsystem Control Facility (SCF) STATUS Command STATUS Command The STATUS command displays the dynamic information for a line. STATUS is a nonsensitive command. Command Syntax for the STATUS Command The STATUS command has the following syntax: 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.
Managing CP6100 Using the Subsystem Control Facility (SCF) Display for the STATUS LINE Command BPID is the CPU number and the backup PID number of the line. I/O ADDR is the address for the CP6100 line. The four fields displayed are, from left to right, CHANNEL, PATYPE, CLIPNUMBER, and LINENUMBER. The CHANNEL field is no longer used. A value of 4 in the PATYPE field indicates that the line is an IP node.
Managing CP6100 Using the Subsystem Control Facility (SCF) Display for the STATUS LINE Command Path is the primary path to the communications line interface processor (CLIP). Preferred IP is the preferred IP address used by the process. Alternate IP is the alternate IP address used by the process. CLB Frame Size is the CLB frame size in bytes. Primary Trace states whether the primary process is being traced. Type/Subtype gives the type and subtype of the line.
Managing CP6100 Using the Subsystem Control Facility (SCF) Examples of the STATUS Command Examples of the STATUS Command The following SCF command gives you the status of the line $CPL1: - > STATUS LINE $CPL1 The following SCF command gives you the detailed status of the line $CPL1: - > STATUS LINE $CPL1, DETAIL STOP Command The STOP command normally terminates the activity of an object. It nondisruptively deletes all connections to and from an object.
Managing CP6100 Using the Subsystem Control Facility (SCF) SUSPEND Command SUSPEND Command The SUSPEND command blocks the LINE from accepting more OPEN requests from the application programs. Nothing will be done to the current OPENers. All outstanding requests will be processed and all further requests from the current OPENers will be honored. SUSPEND is a sensitive command.
Managing CP6100 Using the Subsystem Control Facility (SCF) SWITCH Command SWITCH Command The SWITCH command causes the backup CIU path to become the primary CIU path and the primary CIU path to become the backup CIU path. SWITCH is a sensitive command. Command Syntax for the SWITCH Command The SWITCH command has the following syntax: SWITCH [ / OUT file-spec / ] [ PROC proc-name ] , PATH { A | B } OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Managing CP6100 Using the Subsystem Control Facility (SCF) TRACE Command TRACE Command The TRACE command requests the capture of target-defined data items, alters trace parameters, or ends tracing. TRACE is a sensitive command. An SCF trace produces a trace file that can be displayed using PTrace commands. The trace file is created by SCF. The PTrace utility is described in Section 9, PTrace Facility for CP6100.
Managing CP6100 Using the Subsystem Control Facility (SCF) Command Syntax for the TRACE Command COUNT count specifies the number of trace records that you want to capture. count is an integer in the range -1 through 32767. If you omit COUNT or if count equals -1, records accumulate until you stop the trace. NOCOLL indicates that the trace collector process should not be initiated. The disk file is to be written to by the operating system.
Managing CP6100 Using the Subsystem Control Facility (SCF) Considerations for the TRACE Command WRAP specifies that when the trace file end-of-file mark is reached, trace data will wrap around to the beginning of the file and overwrite any data there. If WRAP is not specified, the trace is stopped when the end-of-file mark is reached. You cannot change the specification of the WRAP option during an ongoing trace. Table 8-4.
Managing CP6100 Using the Subsystem Control Facility (SCF) Examples of the TRACE Command Examples of the TRACE Command The following command starts the trace of the line $CPL1, puts the results in a file named TRCL1, selects all trace options, and specifies 300 bytes as the length of the data in the trace data record: - > TRACE LINE $CPL1, TO TRCL1, SELECT ALL, RECSIZE 300 The following command starts the trace of the line $CPL1, puts the results in a file named TRCL2, and selects the L2 and CLBI trace
Managing CP6100 Using the Subsystem Control Facility (SCF) Examples of the VERSION Command The display for a VERSION PROC command with the DETAIL option has the following format: CP6100 VERSION PROC \IDC2.$CPL1 System \IDC2 CP6100 - T9338F40 - (20FEB96) - (AAA01A) GUARDIAN - T9050 - (F40) SCF Kernel - T9082D30 - (31OCT94) (15AUG94) CP6100 PM - T8162F40 - (20FEB96) - 0.1 CP6100 - T9338F40 - 20FEB96 - (NPV01A) T9338F40 shows the product and version number of the CP6100 process.
Managing CP6100 Using the Subsystem Control Facility (SCF) Examples of the VERSION Command CP6100 Configuration and Management Manual—426741-003 8- 36
9 PTrace Facility for CP6100 This section describes the PTrace interface, command syntax, and fields of sample trace records. This section contains the following topics: • • • • • About PTrace Recording and Displaying Trace Data Determining the Subsystem PTrace Commands Trace Example About PTrace The print trace (PTrace) utility formats data that is stored in unstructured trace files for output to terminals, printers, and disk files. Trace files contain records of the communications between processes.
PTrace Facility for CP6100 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.
Determining the Subsystem PTrace Facility for CP6100 The following general description of the steps involved in recording and displaying trace data selects CLIP level-2 trace information. 1. Start the trace with the SCF TRACE command, which allows you to specify parameters such as the size of the trace records and the name and maximum size of the trace file.
PTrace Commands for CP6100 PTrace Facility for CP6100 Table 9-1.
PTrace Commands for CP6100 PTrace Facility for CP6100 description of the command, the command’s syntax, and any special considerations that apply to the command. The commands are described in alphabetical order. Table 9-2 lists the PTrace commands available for the CP6100 subsystem. Table 9-2.
PTrace Commands for CP6100 PTrace Facility for CP6100 response to a NEXT, FIND, or RECORD command, it checks its selection mask to determine whether or not the record is of a type that you want to display. PTrace also checks many other session parameters, such as those established by LIMIT.
PTrace Commands for CP6100 PTrace Facility for CP6100 Table 9-3.
PTrace Facility for CP6100 Trace Example Trace Example The following commands will create a useful sample trace file: 1. Stop the CP6100 line: STOP LINE $CPL1 2. Start the line: START LINE $CPL1 3. Start the trace with the SCF TRACE command and specify SELECT ALL, PAGES 64, WRAP: TRACE LINE $CPL1, TO , SELECT ALL, PAGES 64, WRAP 4. Wait for the CP6100 line-ready console message. 5. Stop the trace. For example: TRACE LINE $CPL1, STOP 6. Use PTrace to format and display the trace records. Note.
A CP6100 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 CP6100 subsystem are listed and described. These errors all have positive error numbers. Errors returned by the CP6100 subsystem that have negative numbers are SCF errors common to all subsystems.
CP6100 Subsystem Error Messages About CP6100 Errors About CP6100 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, Subsystem Control Point (SCP), and so on.
CP6100 Subsystem Error Messages CP6100 Error 00003 CP6100 Error 00003 CP6100 00003 START LINE command failed due to CSM download error. Cause. The START command was rejected because of a CSM download error. The error might be caused by an improperly downloaded file. Effect. The specified line is not started. Recovery. Check that the downloaded file is correct. CP6100 Error 00004 CP6100 00004 STOP LINE command was rejected due to CLIP error. Cause.
CP6100 Subsystem Error Messages CP6100 Error 00007 CP6100 Error 00007 CP6100 00007 ALTER LINE, ADCCP SNAXLATE is being turned ON when TRANSLATE is OFF. Cause. The ADCCP modifier TRANSLATE should be ON for SNAXLATE to be turned on. Effect. The modifer is not altered. Recovery. Use the ALTER command to set TRANSLATE and SNAXLATE to ON. CP6100 Error 00008 CP6100 00008 ALTER LINE, BSC INTERNALCLK should be set to YES for baud rate to be specified. If INTERNALCLK is set to NO, baud rate cannot be specified.
B SCF Command Summary for CP6100 This appendix summarizes the syntax of the commands described in Section 8, Managing CP6100 Using the Subsystem Control Facility (SCF).
SCF Command Summary for CP6100 STATS Command STATS Command Displays statistical information for the specified line. STATS [ / OUT file-spec / ] [ LINE line-name ] [ , RESET ] STATUS Command Displays the dynamic information for a line. STATUS [ / OUT file-spec / ] [ LINE line-name ] [ , DETAIL ] STOP Command Terminates the activity of an object and nondisruptively deletes all connections to and from an object.
TRACE Command SCF Command Summary for CP6100 TRACE Command Requests the capture of target-defined data items, alters trace parameters, or ends tracing. TRACE is a sensitive command. An SCF trace produces a trace file that can be displayed using PTrace commands. The trace file is created by SCF. The PTrace utility is described in Section 9, PTrace Facility for CP6100.
SCF Command Summary for CP6100 CP6100 Configuration and Management Manual—426741-003 B- 4 VERSION Command
C Moving to G-Series or H-Series RVUs Note. The CP6100 subsystem is the same for G-series and H-series RVUs. There are no H-series migration considerations for the CP6100 subsystem. This appendix discusses the differences between the CP6100 subsystem on G-series RVUs and the CP6100 subsystem on D-series.
SYSGEN-to-SCF Considerations Moving to G-Series or H-Series RVUs You use the SCF interface to the WAN subsystem to perform these functions. The WAN subsystem and the SCF interface to the WAN subsystem are described in detail in the WAN Subsystem Configuration and Management Manual. SYSGEN-to-SCF Considerations The System Generation (SYSGEN) program is not used for G-series and H-series RVUs.
COUP-to-SCF Considerations Moving to G-Series or H-Series RVUs Table C-2. CP6100 Macro and Profile Correlations D-Series Macros G-Series or H-Series Profiles MPSB PCP6MPSB TINET Not Supported LIU PCP6LIU For more information about creating profiles, see the WAN Subsystem Configuration and Management Manual. COUP-to-SCF Considerations The COUP interface is no longer supported for G-series or H-series RVUs. The COUP functions are replaced by SCF.
Moving to G-Series or H-Series RVUs Managing CP6100 Lines For the G06.21 RVU, HP Open System Management (OSM) replaces TSM as the system management tool of choice for NonStop S-series systems.
Glossary adapter. See ServerNet adapter. adapter cable. (1) A cable that connects components that have incompatible electrical interfaces. (2) For the ServerNet wide area network (SWAN) concentrator, one of four types of cable that can connect any of the six 50-pin WAN ports to one of the supported electrical interfaces (RS-232, RS-449, X.21, or V.35). API. See application program interface (API). application program interface (API).
command file Glossary command file. An EDIT file that contains a series of commands and serves as a source of command input. communications line. A two-way link consisting of processing equipment, I/O devices, protocol conventions, and cables that connect a computer to other computers. communications line interface processor (CLIP). The major programmable device within the ServerNet wide area network (SWAN) concentrator, providing link-level protocol and a software interface to the host.
ConMgr Glossary ConMgr. See concentrator manager process (ConMgr). connection. (1) The path between two protocol modules that provides reliable stream delivery service. console message. See operator message. controller. See ServerNet addressable controller (SAC). COUP. See Configuration Utility Program (COUP). current configuration file. See configuration file. data communications equipment (DCE).
DSM/SCM Glossary DSM/SCM. See Distributed Systems Management/Software Configuration Manager (DSM/SCM). DTE. See data terminal equipment (DTE). dynamic information. Information that represents the set of resources that actually exist in the current configuration of a NonStop S-series server. Dynamic information is gathered from a server through the process of discovery. Contrast with static information. dynamic process configuration.
fault tolerance Glossary fault tolerance. The ability of a NonStop S-series system to continue processing despite the failure of any single software or hardware component within the system. firmware. Code in memory that is necessary for the power-up initialization and communication with a host or device. The software for components of the ServerNet architecture (for example, an adapter) is called firmware. Some firmware for ServerNet components is downloaded when the system or component is loaded.
IPM Glossary local address, which identifies a host within a network. A network address is concatenated with a host address to form the IP address and uniquely identify a host within a network. IP routes data between source and destination IP addresses. IPM. See interim product modification (IPM). Kernel subsystem.
nonsensitive command Glossary nonsensitive command. A command that can be issued by any user or program that is allowed access to the subsystem—that is, a command on which the subsystem imposes no further security restrictions. For Subsystem Control Facility (SCF) subsystems, nonsensitive commands are those that cannot change the state or configuration of objects; most of them are information commands. Contrast with sensitive command. null object type.
Online Support Center (OSC) Glossary communications line might temporarily affect applications that use the communications line. Contrast with offline change. Online Support Center (OSC). The group of support specialists within the HP Global Customer Support Center (GCSC) who respond to telephone calls regarding system problems and diagnose malfunctioning systems using remote diagnostic links. See also Global Customer Support Center (GCSC). Open Systems Interconnection (OSI).
outage minutes Glossary an application being used is not available. See also planned outage and unplanned outage. outage minutes. A metric for measuring outages that translates percentages into minutes of downtime per year. output destination. The resource to which Subsystem Control Facility (SCF) sends its responses to commands. SCF can direct output to a disk file, an application process, a terminal, or a printer.
problem incident report Glossary problem incident report. A type of incident report that reports a problem in the server. A problem incident report is generated when changes occur on the server that could directly affect the availability of system resources. process. A program that has been submitted to the operating system for execution, or a program that is currently running in the computer. PROCESS object type.
ServerNet adapter Glossary requester. Servers are designed to receive request messages from clients or requesters; perform the desired operations, such as database inquiries or updates, security verifications, numerical calculations, or data routing to other computer systems; and return reply messages to the clients or requesters. A server process is a running instance of a server program. ServerNet adapter.
service connection Glossary service connection. A connection between the TSM client software running on a TSM workstation and the TSM server software running on a NonStop S-series server. A service connection can be used only to communicate with the server when the NonStop Kernel operating system is running. A service connection provides a comprehensive service and maintenance picture of the server and is used to perform most service management tasks. site update tape (SUT).
super group Glossary super group. The group of user IDs that have 255 as the group number. This group has special privileges; many HP utilities have commands or functions that can be executed only by a member of the super group. super-group user. A user who can read, write, execute, and purge most files on the system. Super-group users have user IDs that have 255 as the group number. super ID. A privileged user who can read, write, execute, and purge all files on the system.
TSM package Glossary TSM package. A software product for NonStop S-series servers that provides the information needed to perform functions such as querying resources and testing, provides notification of problems on the system, and allows local or remote access to the system for service and maintenance. TSM performs the same role as that of TMDS, Syshealth, and Remote Maintenance Interface (RMI) on earlier NonStop systems. TSM is not supported on NonStop NS-series servers. TNSC.
$ZCNF Glossary $ZCNF. The process name of the configuration utility process. $ZNET. The process name of the Subsystem Control Point (SCP) management process. $ZPM. The process name of the persistence manager process that starts generic processes in G-series and H-series RVUs and manages their persistence. ZSYSCONF subvolume. The subvolume on the $SYSTEM disk that contains the system configuration database. $ZZKRN. The process name of the Kernel subsystem manager process. $ZZWAN.
$ZZWAN Glossary CP6100 Configuration and Management Manual—426741-003 Glossary -16
Index A ABM general 2-4 ABORT command considerations 8-8 definition 8-8, B-1 syntax 8-8 ACTIVATE command considerations 8-9 definition 8-9, B-1 syntax 8-9 ADCCP lines ABMMODE modifier 4-2 address field 4-2, 4-3 ADDRESS modifier 4-3 AFLD modifier 4-2, 4-3 ARMMODE modifier 4-2 AUTOCLOSE modifier 4-4 AUTOCONF modifier 4-4 AUTOLOAD modifier 4-4 BITSYNC modifier 4-4 CLBFRAMESIZE modifier 4-5 CLBRETIRES modifier 4-5 CLBTIMEOUT modifier 4-5 CLBWINDOW modifier 4-6 CLIPTRACEREC modifier 4-6 CONFIGSIZE modifier 4-6 D
B Index ADCCP lines (continued) TRANSLATE modifier 4-11, 4-13, 4-16 TWA modifier 4-17 TWS modifier 4-17 TYPE modifier 4-17 WINDOW modifier 4-18 XFERTIMER modifier 4-8, 4-18 XLENGTH modifier 4-16, 4-18 XOFFSET modifier 4-16, 4-19 ADCCP protocol defined 4-1 See also protocols address field 4-3 ALTER command considerations 8-10 definition 8-10, B-1 syntax 8-10 ALTER LINE ADCCP attribute-spec 8-11 BSC attribute-spec 8-12 LIU attribute-spec 8-13 MPSB attribute-spec 8-14 ANSI Standard X3.28 6-1 X3.
C Index BISYNC lines (continued) MAXLOCALAREA modifier 5-11 MULTI modifier 5-12 NOAUTOCONF modifier 5-12 PROFILEID modifier 5-12 PROGRAM modifier 5-13 RETRIES modifier 5-13 RSIZE modifier 5-13 STARTBOOT modifier 5-13 STARTDOWN modifier 5-14 TESTINT modifier 5-14 TIMEOUT modifier 5-14 TYPE modifier 5-14 Bisync Multipoint Supervisor See protocols Bisync Multipoint Tributary See protocols BSC See protocols BSC protocol defined 5-1 See also protocols BSCS See protocols BSCT See protocols C carrier frequency
D Index configuration process CP6100 subsystem ADD DEVICE syntax 1-5, 3-5 ADD PROFILE syntax 1-4, 3-4 START DEVICE syntax 1-5, 3-7 Quick Start 1-1 SCF commands 3-3, 3-5 CP6100 ADD DEVICE command 1-4, 3-5 ADD PROFILE command 1-4, 3-4 configuration quick start 1-1 error messages A-1 object files 3-3 START DEVICE command 1-5, 3-7 subsystem configuration 3-3 subsystem monitoring 2-6 supported protocols 2-3 CTS 4-15 D Data Carrier Detect See DCD Data terminal ready (DTR) See DTR DCD 6-7 Device type for CP6100
L Index L line configurations 2-3 Line interface units See LIU lines leased 6-7, 6-8, 6-11 switched 4-14, 6-7 LIU 2-1, 4-6, 4-13, 5-10, 5-13, 6-4, 6-13, 7-6, 7-10 LIU protocol ANY modifier 7-2 ASYNC modifier 7-2 AUTOCLOSE modifier 7-3 AUTOCONF modifier 7-3 AUTOLOAD modifier 7-3 BITSYNC modifier 7-4 BYTESYNC modifier 7-4 CLBFRAMESIZE modifier 7-5 CLBRETIRES modifier 7-5 CLBTIMEOUT modifier 7-5 CLBWINDOW modifier 7-5 CLIPTRACEREC modifier 7-6 CMGLDEV modifier 7-6 CONFIGSIZE modifier 7-6 defined 7-1 HIGHPIN
N Index MPS-B lines (continued) MPSBNONSTOPOFF modifier 6-9 MPSBNONSTOPON modifier 6-9 MPSBODD modifier 6-9 MPSBPACE modifier 6-10 MPSBPARITY modifier 6-10 MPSBPOLLINTERVAL modifier 6-10 MPSBRETRIES modifier 6-10 MPSBSWITCHED modifier 6-11 MPSBSYNC modifier 6-11 MPSBTIMEOUT modifier 6-11 MULTI modifier 6-11 NOAUTOCONF modifier 6-12 PROFILEID 6-12 PROGRAM modifier 6-12 RETRIES modifier 6-13 RSIZE modifier 6-13 STARTBOOT modifier 6-13 STARTDOWN modifier 6-13 TESTINT modifier 6-14 TIMEOUT modifier 6-14 TYPE
R Index protocols (continued) download modules 2-5 Generalized Full Duplex 2-6 GFDX 2-6 LIU 7-1 MPS-B 2-5, 6-1 Multipoint Supervisor-Burroughs 2-5 PROFILE objects 3-3 Society for Worldwide Interbank Finacial Telecommunications 2-6 SWIFT 2-6 PTrace determining the subsystem 9-3 displaying trace data 9-3 formatting trace files 9-3 generating a trace file 9-2 recording trace data 9-3 R read operation 6-6, 6-8 Request to Send See RTS retries 6-10, 6-11 RTS 4-15, 6-8 S SCF interface to CP6100 8-2 interface t
T Index SUSPEND command considerations 8-29 definition 8-29, B-2 syntax 8-29 SWIFT Society for Worldwide Interbank Finacial Telecommunications See protocols SWITCH command considerations 8-30 definition 8-30, B-2 syntax 8-30 switched 6-8 synchronous characters MPS-B protocol 6-11 synchronous operation MPS-B lines 6-11 Syntax time values 8-7 System configuration 8-2 CP6100 subsystem 3-3 system monitoring TSM 2-7 T Time values syntax 8-7 timeout 6-11 TRACE command considerations 8-33 definition 8-31, B-3 L
