Asynchronous Terminals and Printer Processes Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the Asynchronous Terminals and Printer Processes (ATP6100) subsystem on HP Integrity Nonstop™ NS-series and HP NonStop S-series systems and includes the Subsystem Control Facility (SCF) commands used with this subsystem. Product Version F40 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs and H06.
Document History Part Number Product Version Published 420258-001 SCF F40 December 1998 424280-001 F40 May 2000 424280-002 F40 September 2003 424280-003 F40 July 2005
Asynchronous Terminals and Printer Processes Configuration and Management Manual Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information Examples Figures Tables vii About This Manual ix Who Should Use This Manual ix How this Manual Is Organized ix Where to Get More Information x Notation Conventions xi 1.
. Printer Profiles and Default Modifiers Contents Creating an ATP6100 Line-Handler Process (continued) Adding an ATP6100 Device 3-5 Starting the ATP6100 Line 3-7 4. Printer Profiles and Default Modifiers Printer Profiles 4-1 PATP5512 Profile 4-2 PATP5515 Profile 4-3 PATP5516 Profile 4-4 PATP5520 Profile 4-5 PATP5530 Profile 4-6 PATP5540 Profile 4-7 PATP5573 Profile 4-8 PATP5577 Profile 4-9 PATPPRT Profile 4-10 Printer Modifiers 4-11 5.
Contents 7.
A. ATP6100 Subsystem Error Messages Contents PTrace Commands (continued) STATETABLES Command 7-7 Trace Example 7-8 A. ATP6100 Subsystem Error Messages Common Versus Subsystem-Specific Errors Example of an ATP6100 Error A-1 Example of a Common Error A-1 About ATP6100 Errors A-2 A-1 B.
C. Moving to G-Series or H-Series RVUs Contents C. Moving to G-Series or H-Series RVUs WAN Subsystem C-1 SYSGEN-to-SCF Considerations C-2 CONFTEXT Paragraph Information Macro-Profile Comparison C-2 COUP-to-SCF Considerations C-3 Managing ATP6100 Lines C-4 C-2 Glossary Index Examples Example 1-1. Adding an ATP6100 Device 1-4 Figures Figure 6-1. Figure 6-2. Figure 7-1. SCF Interface to ATP6100 6-3 ATP6100 Subsystem Object Hierarchy 6-4 Recording and Displaying Trace Data 7-2 Tables Table 1.
Tables (continued) Contents Table 5-7. Table 5-8. PATP6524 Default Modifiers and Values PATP6530 Default Modifiers and Values 5-7 5-8 Tables (continued) Table 5-9. Table 5-10. Table 5-11. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 7-1. Table 7-2. Table 7-3. Table C-1. Table C-2.
What’s New in This Manual Manual Information Asynchronous Terminals and Printer Processes Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the Asynchronous Terminals and Printer Processes (ATP6100) subsystem on HP Integrity Nonstop™ NS-series and HP NonStop S-series systems and includes the Subsystem Control Facility (SCF) commands used with this subsystem. Product Version F40 Supported Release Version Updates (RVUs) This manual supports G06.
What’s New in This Manual • • • • • • • New and Changed Information Section 3, Configuring the ATP6100 Subsystem HIGHPIN OFF on page 4-17 NOLINE1FORMF on page 4-19 NORC on page 4-19 NOVFU72LINES on page 4-21 SPACINGPOST on page 4-23 HIGHPIN OFF on page 5-22 Note. The following command syntax changes are only related to introducing a new manual (SCF Reference Manual for H-Series RVUs).
About This Manual The Asynchronous Terminals and Printer Processes Configuration and Management Manual describes how to plan, configure, and manage the ATP6100 subsystem. This manual includes: • • • • A configuration “quick start” that provides the basic information required to enable you to quickly and easily define and start the ATP6100 subsystem. An explanation of the major features and capabilities of the ATP6100 subsystem.
Where to Get More Information About This Manual Table 1. Summary of Contents (page 2 of 2) Section Title This section . . . 5 Terminal Profiles and Default Modifiers Provides a brief overview and lists the contents of the terminal profiles, and describes all terminal modifiers 6 Managing ATP6100 Using the Subsystem Control Facility (SC F) Describes the SCF interface to the ATP6100 subsystem and the SCF commands used to manage the ATP6100 subsystem.
About This Manual Notation Conventions Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
About This Manual General Syntax Notation { } 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 can 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. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual 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 / ] LINE [ , attribute-spec ]… !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
About This Manual Notation for Management Programming Interfaces lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
About This Manual Change Bar Notation Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 xvi
1 Configuration Quick Start This section is a configuration quick start for the Asynchronous Terminals and Printer Processes (ATP6100) subsystem. This procedure explains how to set up the initial ATP6100 processes on an Integrity NonStop NS-series or NonStop S-series server.
Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information Configuration Quick Start Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information 1. Log on to the Integrity NonStop NS-series or NonStop S-series server using the Super ID and enter the correct password at the Password: prompt. > LOGON super.super Password: 2. At the TACL prompt on the Integrity NonStop NS-series or NonStop S-series server, start SCF: > SCF 3.
Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information Configuration Quick Start c. Record the available WAN line number in the line-num field in Example 1-1, Adding an ATP6100 Device. (For example: 1.) d. Record the configured path that you prefer to use in the path-name field in Example 1-1, Adding an ATP6100 Device. (For example: A.) You can only use paths that have been configured. The path name is optional. 4.
Add an ATP6100 Profile Configuration Quick Start Example 1-1. Adding an ATP6100 Device -> add device $zzwan.#atpp1, profile profter, & -> cpu ___________, & (See Step 6) -> altcpu ___________, & (See Step 6) -> iopobject $system.sysnn.
Configuration Quick Start Add an ATP6100 Device The program file must use the current sysnn. To obtain the current sysnn, type the following: ->status *, user Add an ATP6100 Device Before you add any ATP6100 devices, verify that all processes, profiles, and the SWAN/SWAN 2 concentrator have been added and started. During the Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information task, you recorded the information you need to issue the ADD DEVICE command to Example 1-1 on page 1-4.
Configuration Quick Start Start the ATP6100 Line Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 1 -6
2 Overview of the ATP6100 Subsystem This section provides an introduction to and describes the subsystem components of the ATP6100 subsystem and the protocols supported by ATP6100. This section contains the following topics: • • • Introduction to ATP6100 ATP6100 Subsystem Management Tools on page 2-1 Online Expansion and Reconfiguration on page 2-3 Introduction to ATP6100 The ATP6100 subsystem consists of the ATP6100 line-handler process and a protocol module.
Overview of the ATP6100 Subsystem Event Management Service (EMS) subsystem is described in Section 6, Managing ATP6100 Using the Subsystem Control Facility (SCF). Event Management Service (EMS) EMS is a DSM interface that provides event collection, logging, and distribution facilities. The ATP6100 subsystem reports events to EMS. ATP6100 subsystem events are described in the Operator Messages Manual. Compaq TSM Note. TSM is not supported on Integrity NonStop NS-series servers.
Online Expansion and Reconfiguration Overview of the ATP6100 Subsystem Online Expansion and Reconfiguration Reconfiguration of the ATP6100 subsystem is made online using the Subsystem Control Facility (SCF) interface to the ATP6100 and wide area network (WAN) subsystems. Table 2-1, Online Reconfiguration Tasks, on page 2-3 compares tasks that you may use frequently and indicates whether they are performed by SCF or the WAN subsystem.
Overview of the ATP6100 Subsystem Online Expansion and Reconfiguration Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 2 -4
3 Configuring the ATP6100 Subsystem This section provides an overview of the ATP6100 subsystem on an Integrity NonStop NS-series or NonStop S-series server and describes how to configure the ATP6100 subsystem .
Configuring the ATP6100 Subsystem WAN Subsystem Interface to ATP6100 WAN Subsystem Interface to ATP6100 For G-series systems, the ATP6100 line-handler process is defined and started with the Subsystem Control Facility (SCF) from the WAN subsystem. The WAN subsystem SCF commands that are relevant to ATP6100 configuration are described in Creating an ATP6100 Line-Handler Process on page 3-4.
Configuring the ATP6100 Subsystem Profile Object Files and Associated Protocols Profile Object Files and Associated Protocols The PROFILE object in the WAN subsystem specifies the device protocol to be used on that particular line. Profiles contain modifiers and default modifier values for the different ATP6100 devices. 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 ATP6100 Note.
Configuring the ATP6100 Subsystem Creating an ATP6100 Line-Handler Process Creating an ATP6100 Line-Handler Process To create an ATP6100 line-handler process, you must add a PROFILE object (“PROFILE” is the SCF object name for the profile file) to the WAN subsystem. Once the PROFILE object is defined in the WAN subsystem, use the ADD DEVICE command to define the DEVICE object to the WAN subsystem. Then use the START DEVICE command to start the line device.
Configuring the ATP6100 Subsystem Adding an ATP6100 Device existing-profile-name is the name of the existing profile, which is to be used as the base for creating profile-name. modifier-keyword and modifier-value are the modifiers and their values for the ATP6100 profile that is being created. Example The following is an example of adding the PATP6530 profile to the WAN subsystem. ADD PROFILE $ZZWAN.#PROFTER, FILE $SYSTEM.SYS00.
Configuring the ATP6100 Subsystem Adding an ATP6100 Device device-name is the device name of the ATP6100 line-handler process you want to add. Do not specify a leading $ sign or name template. conc-name is the SWAN/SWAN 2 concentrator to be used by this device. The concentrator must have been previously defined with an ADD ADAPTER command, as described in the WAN Subsystem Configuration and Management Manual. alt-cpu-num is the CPU number where the backup device will normally execute.
Configuring the ATP6100 Subsystem Starting the ATP6100 Line type and sub-type is the type and subtype for the specified device. download-file-name is the file that is downloaded to the SWAN/SWAN 2 concentrator. Example The following is an example of adding an ATP6100 device on CLIP 1, LINE 1 of a SWAN concentrator to the WAN subsystem: ADD DEVICE $ZZWAN.#ATPP1, CPU 0, ALTCPU 1, PROFILE PROFTER, & IOPOBJECT $SYSTEM.SYS00.
Configuring the ATP6100 Subsystem Starting the ATP6100 Line Once you have added and started the ATP6100 line-handler process in the WAN subsystem, you can alter the modifiers through the ATP6100 subsystem using SCF commands or Guardian procedure calls (see Section 6, Managing ATP6100 Using the Subsystem Control Facility (SCF)).
4 Printer Profiles and Default Modifiers This section gives an overview of ATP6100 printer profiles, lists the contents of each profile, and describes the default modifiers contained in each profile. Printer Profiles Printer profiles contain modifiers and default modifier values for different ATP6100 linehandler processes. You create a profile from an object file provided by HP or from a previously created profile.
PATP5512 Profile Printer Profiles and Default Modifiers PATP5512 Profile The PATP5512 profile provides default settings for the 5512 printer device. Table 4-2 lists the default modifiers and values for the PATP5512 profile provided by HP. Table 4-2.
PATP5515 Profile Printer Profiles and Default Modifiers PATP5515 Profile The PATP5515 profile provides default settings for the 5515 printer device. Table 4-3 lists the default modifiers and values for the PATP5515 profile provided by HP. Table 4-3.
PATP5516 Profile Printer Profiles and Default Modifiers PATP5516 Profile The PATP5516 profile provides default settings for the 5516 printer device. Table 4-4 lists the default modifiers and values for the PATP5516 profile provided by HP. Table 4-4.
PATP5520 Profile Printer Profiles and Default Modifiers PATP5520 Profile The PATP5520 profile provides default settings for the 5520 printer device. Table 4-5 lists the default modifiers and values for the PATP5520 profile provided by HP. Table 4-5.
PATP5530 Profile Printer Profiles and Default Modifiers PATP5530 Profile The PATP5530 profile provides default settings for the 5530 printer device. Table 4-6 lists the default modifiers and values for the PATP5530 profile provided by HP. Table 4-6.
PATP5540 Profile Printer Profiles and Default Modifiers PATP5540 Profile The PATP5540 profile provides default settings for the 5540 printer device. Table 4-7 lists the default modifiers and values for the PATP5540 profile provided by HP. Table 4-7.
PATP5573 Profile Printer Profiles and Default Modifiers PATP5573 Profile The PATP5573 profile provides default settings for the 5573 printer device. Table 4-8 lists the default modifiers and values for the PATP5573 profile provided by HP. Table 4-8.
PATP5577 Profile Printer Profiles and Default Modifiers PATP5577 Profile The PATP5577 profile provides default settings for the 5577 printer device. Table 4-9 lists the default modifiers and values for the PATP5577 profile provided by HP. Table 4-9.
PATPPRT Profile Printer Profiles and Default Modifiers PATPPRT Profile The PATPPRT profile provides default settings for a non-HP printer device. Table 4-10 lists the default modifiers and values for the PATPPRT profile provided by HP. Table 4-10.
Printer Profiles and Default Modifiers Printer Modifiers Printer Modifiers This subsection describes all modifiers contained in the printer profiles and all other modifiers that can be used with the ATP6100 printer profiles. 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 6, Managing ATP6100 Using the Subsystem Control Facility (SCF).
Printer Modifiers Printer Profiles and Default Modifiers BAUD n Application: Serial printers This modifier specifies the baud rate for the serial interface. The baud rate specified by each serial printer profile is listed below.
Printer Profiles and Default Modifiers Printer Modifiers CLBTIMEOUT n Application: SWAN/SWAN 2 concentrator Default: n = 800 (8 sec) Units: .01 seconds Range: 350 through 32767 This modifier specifies the CLB timeout. The default of 800 (8 seconds) allows optimal resource use. A value larger than the default may result in excessive timeouts. CLBWINDOW n Application: SWAN/SWAN 2 concentrator Default: n =1 Range: 1 through 8 This modifier specifies the number of CLB read buffers allocated.
Printer Profiles and Default Modifiers Printer Modifiers DEFLF n Application: Serial printers Default: n = 10 Units: ASCII characters Range: All characters in ASCII character set This modifier defines the ASCII character to be used as the line-feed (LF) character. DELAYTIME n Application: Serial printers Default: n=0 Units: .
Printer Modifiers Printer Profiles and Default Modifiers DEVSUBTYPE n Application: Serial printers See also: DEVTYPE This modifier allows you to specify a subtype for a specific subdevice connected to the line interface unit (LIU). The default DEVSUBTYPE specified by each profile is listed below.
Printer Profiles and Default Modifiers Printer Modifiers ETXFLOWCHAR n Application: Serial printers Default: n=3 Units: ASCII characters Range: All characters in ASCII character set See also: ETXFLOW This modifier specifies the ETX character used by the ETX(ENQ)/ACK flow-control handshake. EVEN Application: Serial printers See also: CHECK, NOCHECK, NONE, ODD This modifier specifies even parity for data sent from the concentrator to the serial printer.
Printer Profiles and Default Modifiers Printer Modifiers HIGHPIN OFF Application: Currently unsupported This modifier specifies that the IOP for the serial printer be configured at a low PIN so that the serial printer can be accessed by C-series RVUs. Note. The HIGHPIN OFF modifier has no effect on the ATP6100 line-handler process running on G-series or H-series RVUs.
Printer Profiles and Default Modifiers Printer Modifiers MODEM Application: Serial printers See also: HARD This modifier specifies that the concentrator is connected to the serial printer through a pair of modems. For a modem connection, you must specify MODEM and EIA and either BAUD n or DUAL212.
Printer Profiles and Default Modifiers Printer Modifiers NOAUTOANSWER Application: Serial printers See also: AUTOANSWER This modifier disables the AUTOANSWER function. NOAUTOLOAD Application: SWAN/SWAN 2 concentrator See also: AUTOLOAD This modifier specifies that the CONMGR will not automatically download the LIU if the LIU responds to a status probe with an error condition. NOETXFLOW Application: Serial printers See also: ETXFLOW This modifier disables ETX(ENQ)/ACK flow-control handshake.
Printer Profiles and Default Modifiers Printer Modifiers NORESETONOPEN Application: Serial printers This modifier directs the system to not reset the following parameters to their default values whenever an application process accesses the serial printer: Line Spacing Form Eject Horizontal Pitch Prespace Transparency Diagnostic mode If you don’t specify this option, an application can alter these parameters the first time it accesses the serial printer.
Printer Profiles and Default Modifiers Printer Modifiers NOVFU72LINES Application: Currently unsupported This modifier specifies 66 print lines per page. Note. The NOVFU72LINES modifier has no effect on the ATP6100 line-handler process running on G-series or H-series RVUs. ODD Application: Serial printers See also: CHECK, EVEN, NOCHECK, NONE This modifier directs the system to use odd parity with data it sends to the serial printer.
Printer Modifiers Printer Profiles and Default Modifiers RECSIZE n Application: SWAN/SWAN 2 concentrator Units: Characters (bytes) See also: DEVRSIZE (when configuring subdevices) This modifier specifies the record size, in bytes, for the printer. The record size is the maximum number of characters transferred in a line, after which the line is terminated (for example, with a CR and an LF). Newer graphics and dot-matrix printers may require a value greater than the default.
Printer Profiles and Default Modifiers Printer Modifiers RSIZE n Application: SWAN/SWAN 2 concentrator Default: n = 80 Units: Characters Although the record size for a SWAN/SWAN 2 concentrator is specified by default, you have the option of specifying the record size for documentation purposes. If you specify RSIZE for a SWAN/SWAN 2 concentrator, you must specify RSIZE 80.
Printer Modifiers Printer Profiles and Default Modifiers STOPBITS n Application: Serial printers Default: n=1 Range: 1, 2, 15 (15 = 1.5 stop bits) This modifier specifies the number of stop bits to be inserted following the data and parity bits. 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.
Printer Profiles and Default Modifiers Printer Modifiers XFERSIZE n Application: Serial printers Default: n = 0 except for PATP5540 and PATPPRT where n = 40 This modifier specifies the maximum number of characters that can be sent to the printer after an ACK is received and before the next ETX(ENQ) is sent. A maximum safe value for n is the printer buffer size minus the printer high-water mark.
Printer Profiles and Default Modifiers Printer Modifiers Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 4- 26
5 Terminal Profiles and Default Modifiers This section gives an overview of ATP6100 terminal profiles, lists the contents of each profile, and describes the default modifiers contained in each profile. Terminal Profiles Terminal profiles contain modifiers and default modifier values for different ATP6100 line-handler processes. You create a profile from an object file provided by HP or from a previously created profile.
PATP6401 Profile Terminal Profiles and Default Modifiers PATP6401 Profile The PATP6401 profile provides default settings for the 6401 terminal device. Table 5-2 lists the default modifiers and values for the PATP6401 profile provided by HP. Table 5-2.
PATP6402 Profile Terminal Profiles and Default Modifiers PATP6402 Profile The PATP6402 profile provides default settings for the 6402 terminal device. Table 5-3 lists the default modifiers and values for the PATP6402 profile provided by HP. Table 5-3.
PATP6511 Profile Terminal Profiles and Default Modifiers PATP6511 Profile The PATP6511 profile provides default settings for the 6511 terminal device. Table 5-4 lists the default modifiers and values for the PATP6511 profile provided by HP. Table 5-4.
PATP6512 Profile Terminal Profiles and Default Modifiers PATP6512 Profile The PATP6512 profile provides default settings for the 6512 terminal device. Table 5-5 lists the default modifiers and values for the PATP6512 profile provided by HP. Table 5-5.
PATP6520 Profile Terminal Profiles and Default Modifiers PATP6520 Profile The PATP6520 profile provides default settings for the 6520 terminal device. Table 5-6 lists the default modifiers and values for the PATP6520 profile provided by HP. Table 5-6.
PATP6524 Profile Terminal Profiles and Default Modifiers PATP6524 Profile The PATP6524 profile provides default settings for the 6524 terminal device. Table 5-7 lists the default modifiers and values for the PATP6524 profile provided by HP. Table 5-7.
PATP6530 Profile Terminal Profiles and Default Modifiers PATP6530 Profile The PATP6530 profile provides default settings for the 6530 terminal device. Table 5-8 lists the default modifiers and values for the PATP6530 profile provided by HP. Table 5-8.
PATP6603 Profile Terminal Profiles and Default Modifiers PATP6603 Profile The PATP6603 profile provides default settings for the 6603 terminal device. Table 5-9 lists the default modifiers and values for the PATP6603 profile provided by HP. Table 5-9.
PATP6604 Profile Terminal Profiles and Default Modifiers PATP6604 Profile The PATP6604 profile provides default settings for the 6604 terminal device. Table 5-10 lists the default modifiers and values for the PATP6604 profile provided by HP. Table 5-10.
PATPTERM Profile Terminal Profiles and Default Modifiers PATPTERM Profile The PATPTERM profile provides default settings for a non-HP terminal device. Table 5-11 lists the default modifiers and values for the PATPTERM profile provided by HP. Table 5-11.
Terminal Profiles and Default Modifiers Terminal Modifiers Terminal Modifiers This subsection describes all modifiers contained in the terminal profiles and all other modifiers that can be used with the ATP6100 terminal profiles. 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 6, Managing ATP6100 Using the Subsystem Control Facility (SCF).
Terminal Modifiers Terminal Profiles and Default Modifiers BAUD n Application: All terminals See also: DUAL212 This modifier specifies the baud rate for the serial interface. The baud rate specified by each terminal profile is listed below. Terminal Profile Baud Rate 6603, 6604 300 6511, 6512, 6520, 6524, 6530 9600 6401, 6402, 6604 19200 For a SWAN/SWAN 2 concentrator, the available baud rates and associated baud-rate modifiers are listed below.
Terminal Profiles and Default Modifiers Terminal Modifiers BSCRT Application: All terminals except 6603 and 6604 See also: BSERASE, BSHARD, NOBS This modifier specifies that the terminal is a video terminal for which each backspace is echoed. The backspace character must be a signal character. If the terminal does not erase when backspacing, the deleted characters are still displayed on the screen.
Terminal Profiles and Default Modifiers Terminal Modifiers For 6530 terminals, if CHAR8 and NONE are specified, NOCHECK must also be specified. CHECK Application: All terminals See also: EVEN, NOCHECK, NONE, ODD This modifier directs the system to perform parity checking on data sent from the terminal according to the specified parity modifier (EVEN or ODD).
Terminal Profiles and Default Modifiers Terminal Modifiers CLBWINDOW n Application: SWAN/SWAN 2 concentrator Default: n =1 Range: 1 through 8 This modifier specifies the number of CLB read buffers allocated. The default of 1 allows optimal resource use. A value larger than the default may result in excessive buffers. CMGLDEV Application: SWAN/SWAN 2 concentrator Default: 0 This modifier specifies the CONMgr logical device id and should not be altered.
Terminal Profiles and Default Modifiers Terminal Modifiers DEFBS n Application: All terminals Default: n =8 Units: ASCII characters Range: All characters in ASCII character set This modifier defines the ASCII character to be used as the backspace (BS) character. DEFCAN n Application: All terminals Default: n = 24 Units: ASCII characters Range: All characters in ASCII character set This modifier defines the ASCII character to be used as the cancel (CAN) character.
Terminal Profiles and Default Modifiers Terminal Modifiers DEFFF n Application: All terminals Default: n = 12 Units: ASCII characters Range: All characters in ASCII character set This modifier defines the ASCII character to be used as the form-feed (FF) character. DEFLF n Application: All terminals Default: n = 10 Units: ASCII characters Range: All characters in ASCII character set This modifier defines the ASCII character to be used as the line-feed (LF) character.
Terminal Modifiers Terminal Profiles and Default Modifiers For ETXFLOW, DELAYTIME n designates the interval that the system waits for an acknowledgment before it returns a NOT READY error to the application program. DEVPROT Application: SWAN/SWAN 2 concentrator Default: 0 This modifier specifies the protocol for the subdevice and should not be altered.
Terminal Profiles and Default Modifiers Terminal Modifiers DUAL212 Application: All terminals See also: MODEM This modifier specifies that the concentrator use the baud rate (1200 or 300) indicated by the Bell 212-type modem. When Secondary Receive Line Detect (SRLD) is set (HIGH) at the concentrator interface (pin 12), the concentrator interface operates at 1200 baud; when SRLD is reset (LOW), it operates at 300 baud.
Terminal Profiles and Default Modifiers Terminal Modifiers ETX n Application: All terminals Default: None Units: Bytes Range: 1 or 2 See also: ETB, ETXCHAR This modifier (end of text) specifies the number of characters in the checksum following a line-terminating ETX or ETB character; the checksum is returned to the application.
Terminal Profiles and Default Modifiers Terminal Modifiers HARD Application: All terminals See also: MODEM This modifier specifies that the concentrator is directly connected to the terminal through a set of wires (a cable).
Terminal Modifiers Terminal Profiles and Default Modifiers INTCHAR x n Application: All terminals Range: x = 1 through 4 n = the range of the ASCII character set Default: See table below See also: USERINTC This modifier allows specification of up to four interrupt character for terminals at the line or subdevice level.
Terminal Profiles and Default Modifiers Terminal Modifiers LINEERRDISABLE Application: SWAN/SWAN 2 concentrator This modifier specifies that console message 165, with a communications line interface processor (CLIP) status of 8, is not sent to the system console. LINETERM n Application: All terminals Default: n = 13 (carriage return) This modifier specifies the line-termination character, in this case a carriage return (CR).
Terminal Profiles and Default Modifiers Terminal Modifiers MODEMDISCERROFF Application: All terminals This modifier disables console message 165 (with a CLIP status of 5). Note. Do not use MODEMDISCERROFF on an individual subdevice.
Terminal Profiles and Default Modifiers Terminal Modifiers NOAUTOLOAD Application: SWAN/SWAN 2 concentrator See also: AUTOLOAD This modifier specifies that the CONMGR will not automatically download the LIU if the LIU responds to a status probe with an error condition. NOBS Application: 6603 and 6604 terminals only See also: BSHARD This modifier specifies that the hard-copy terminal is not to backspace over a character when the backspace key is pressed.
Terminal Profiles and Default Modifiers Terminal Modifiers For conversational mode, the interrupt characters are backspace (BS), line cancel (CAN), end-of-file (EOF), and carriage return (CR). For page mode, the interrupt character is the page-termination character. NOLINE1FORMF Application: Unsupported on terminals This modifier specifies that a printer is to advance four lines following a form feed (FF). Note.
Terminal Profiles and Default Modifiers Terminal Modifiers ODD Application: All terminals See also: CHECK, EVEN, NOCHECK, NONE This modifier directs the system to use odd parity with data it sends to the terminal. PAGE Application: All terminals See also: CONV This modifier specifies PAGE for the terminal transfer mode.
Terminal Profiles and Default Modifiers Terminal Modifiers PROFILEID Application: All terminals and printers Default: Depends on IBM Range: Default value cannot be altered This modifier keyword specifies the profile version. This is used to avoid IOPOBJECT and Profile Version mismatch.
Terminal Profiles and Default Modifiers Terminal Modifiers RESETONCONNECT Application: 6530 terminals only See also: EIA This modifier causes a terminal’s default mode to be set following a connection. This is an optional modifier. If not specified, it is FALSE; if specified, it is TRUE. RETRIES n Application: All terminals except 6401 and 6402 Default: n = 13 Range: 1 through 255 This modifier specifies the number of retries when you are using the ENQ/ACK flow-control handshake.
Terminal Profiles and Default Modifiers Terminal Modifiers SPACINGNONE Application: SWAN/SWAN 2 concentrator See also: LFSYS, SPACINGPOST, SPACINGPRE This modifier specifies that the system does not add a CR and an LF character to the line of text sent to the terminal. SPACINGPOST Application: SWAN/SWAN 2 concentrator See also: LFSYS, SPACINGNONE, SPACINGPRE This modifier specifies that the system is to add a CR and an LF character to the end of a line of text sent to the terminal.
Terminal Modifiers Terminal Profiles and Default Modifiers STOPBITS n Application: All terminals Default: n=1 Range: 1, 2, 15 (15 = 1.5 stop bits) This modifier specifies the number of stop bits to be inserted following the data and parity bits. 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.
Terminal Modifiers Terminal Profiles and Default Modifiers USERINTC Application: All terminals See also: INTCHAR1, INTCHAR2, INTCHAR3, INTCHAR4 For terminals at the line level or subdevice level, this modifier allows specification of the following default interrupt characters: Modifier Interrupt Character Default Decimal | Octal | Hexadecimal Value INTCHAR1 BS = Backspace 8 | %10 | %h08 INTCHAR2 CAN = Cancel 24 | %30 | %h18 INTCHAR3 EOF = End of File 25 | %31 | %h19 INTCHAR4 CR = Carriage
Terminal Profiles and Default Modifiers Terminal Modifiers XOFFCHAR n Application: All terminals Default: None Units: ASCII characters Range: All characters in ASCII character set See also: XONCHAR This modifier specifies the character the terminal uses to stop transmission from the system. Use a different value from that specified for XONCHAR.
6 Managing ATP6100 Using the Subsystem Control Facility (SCF) This section describes the Subsystem Control Facility (SCF) interface to the ATP6100 subsystem and provides SCF command syntax. Depending on your RVU, refer to the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs for general information about running SCF.
Managing ATP6100 Using the Subsystem Control Facility (SCF) Overview of the ATP6100 Subsystem SCF Interface Overview of the ATP6100 Subsystem SCF Interface The ATP6100 subsystem SCF interface is provided to configure, control, and display information about configured objects within the ATP6100 subsystem.
Managing ATP6100 Using the Subsystem Control Facility (SCF) SCF Interface to ATP6100 Figure 6-1. SCF Interface to ATP6100 Terminal OBEY File SCF Log File SCP WAN Subsyste m ATP6100 Subsystem WAN Manager ($ZZWAN) ATP6100 Process VST0601.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ATP6100 Subsystem Objects ATP6100 Subsystem Objects The SCF objects for the ATP6100 subsystem correspond to process components within the subsystem. There are three CP6100 object types: • • • PROCESS LINE SU Figure 6-2 shows the ATP6100 subsystem objects supported by SCF and their hierarchical order Figure 6-2. ATP6100 Subsystem Object Hierarchy PROCESS LINE SU VST0602.vsd PROCESS Object The PROCESS object defines an ATP6100 process.
Managing ATP6100 Using the Subsystem Control Facility (SCF) Object States SU Object The SU object defines a specific device of an ATP6100 LINE. The SU name identifies the specific subdevice configured on a single LINE. An SU name must be unique within a single line, be preceded by a pound sign (#), and consist of a maximum of seven alphanumeric characters; the first character must be alphabetic, for example, $ATPS1.#TERM.
Managing ATP6100 Using the Subsystem Control Facility (SCF) SCF Commands and Objects The following states are recognized by the ATP6100 subsystem: State Description DIAGNOSING The object is in a subsystem-defined test mode entered via the DIAGNOSE command. STARTED The object is initialized and ready for normal data traffic. No restrictions govern information flow to or from the object. STARTING The object is being initialized and is in transition to the STARTED state.
Managing ATP6100 Using the Subsystem Control Facility (SCF) Sensitive and Nonsensitive Commands Sensitive and Nonsensitive Commands SCF commands are either sensitive or nonsensitive. Sensitive commands can change the state or configuration of subsystem objects, start or stop tracing, or change the values of statistics counters; they can cause communications to cease if improperly used. Nonsensitive commands request information or status but do not affect operation.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ABORT Command In displays generated by the STATS command, HH is an integer in the range 0 through 23. MM and SS are integers in the range 0 through 59. hh is an integer in the range 0 through 99. For example, 5:27.02 is 5 minutes, 27 seconds, and 2 hundredths of a second. ABORT Command The ABORT command terminates the activity of the indicated object as quickly as possible. The ATP6100 subsystem supports the ABORT command on a LINE or an SU.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ABORT SU Command Considerations for the ABORT LINE Command • • • • • • The SEL option is not supported. If you are terminating both a line and its subordinate subdevices (for example, with the SUB ALL option), SCF halts the subdevices first and then halts the line. The ABORT 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.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ACTIVATE SU Command SU subdevice-name designates the subdevice to be aborted. If you omit subdevice-name, the assumed subdevice is aborted (see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs for details about the ASSUME command). Considerations for the ABORT SU Command • • • The SUB and SEL options are not supported. The final summary state after this command is executed is STOPPED.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ALTER Command Example of the ACTIVATE SU Command The following SCF command activates the subdevice $ATPS1.#TERM: ->ACTIVATE SU $ATPS1.#TERM ALTER Command The ALTER command changes the modifiers of an established object. The ATP6100 subsystem supports the ALTER command on a LINE or an SU. This command changes only the specified modifiers of the target object. ALTER is a sensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) ALTER SU Command ALTER SU Command The ALTER SU command is used to change a subdevice modifier. This command changes only the specified modifiers of the subdevice. ALTER SU is a sensitive command. Command Syntax for the ALTER SU Command The ALTER SU command has the following syntax: ALTER [ / OUT file-spec / ] [ SU subdevice-name ] {, attribute-spec } [, attribute-spec ] . . . SU subdevice-name designates the subdevice to be altered.
Managing ATP6100 Using the Subsystem Control Facility (SCF) [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ALTER SU Command PARITY { EVEN | NONE | ODD } SPECIALMODE { COUNT | NOCOUNT | RESET } SPECIALCHAR { 0 THROUGH 255 } STOPBITS { 1 | 1.
Managing ATP6100 Using the Subsystem Control Facility (SCF) INFO Command INFO Command The INFO command displays the current or default modifier values for a specified line or subdevice. Specifying DETAIL will cause more detailed information to be displayed. INFO is a nonsensitive command. INFO LINE Command The INFO LINE command displays the current modifier settings for the specified line. Specify DETAIL to display more detailed information.
Managing ATP6100 Using the Subsystem Control Facility (SCF) INFO LINE Command Display of the INFO LINE Command The format of the display for LINE object without the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to Section 4, Printer Profiles and Default Modifiers, and Section 5, Terminal Profiles and Default Modifiers. for detailed descriptions of these modifiers. ATP6100 INFO LINE Name $ATPS1 $ATPS1 Opclass ASYNC ASYNC *Program $SYSTEM.CSSnn.C1094P00 $SYSTEM.
Managing ATP6100 Using the Subsystem Control Facility (SCF) INFO SU Command Examples of the INFO LINE Command The following command displays information about the line $ATPS1: ->INFO LINE $ATPS1 The following command displays detailed information about the line $ATPS1: ->INFO LINE $ATPS1,DETAIL The following command displays detailed information about all the subdevices of the line $ATPS1: ->INFO LINE $ATPS1,SUB ALL,DETAIL INFO SU Command The INFO SU command displays the current modifier settings for the
Managing ATP6100 Using the Subsystem Control Facility (SCF) INFO SU Command Display of the INFO SU (ASYNC, TYPE 6) Command The format of the display for SU object without the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to Section 4, Printer Profiles and Default Modifiers, and Section 5, Terminal Profiles and Default Modifiers. for detailed descriptions of these modifiers. ATP6100 INFO SU Name $ATPS1.
Managing ATP6100 Using the Subsystem Control Facility (SCF) INFO SU Command Display of the INFO SU (PRINT, TYPE 5) Command The format of the display for SU object without the DETAIL option is shown below. Alterable modifiers are denoted with an asterisk. Refer to Section 4, Printer Profiles and Default Modifiers, and Section 5, Terminal Profiles and Default Modifiers. for detailed descriptions of these modifiers. ATP6100 INFO SU Name $ATPS1.
Managing ATP6100 Using the Subsystem Control Facility (SCF) LOAD LINE Command LOAD LINE Command The LOAD LINE command downloads the Data Link Control (DLC) task to the SWAN/SWAN 2 concentrator. LOAD LINE is a sensitive command. Command Syntax for the LOAD LINE Command The LOAD LINE command has the following syntax: LOAD [ /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 ATP6100 Using the Subsystem Control Facility (SCF) START Command START Command The START command initiates the operation of an object. The successful completion of the START command leaves the object in the STARTED state. START is a sensitive command. START LINE Command The START LINE command initiates the operation of a line. Successful completion of the START LINE command indicates that the subsystem was able to initiate processing to start the line. START LINE is a sensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) START SU Command Considerations for the START LINE Command • • • • • • If the SCF START command completes processing with no errors, the subsystem was able to initiate processing for the start operation. However, the absence of any error does not necessarily indicate that the start operation was completed successfully. A warning will be issued if the LINE is already in the STARTED state. The SEL option is not supported.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS Command SU subdevice-name designates the subdevice to be started. If you omit subdevice-name, the assumed subdevice is started (see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs for details about the ASSUME command). Considerations for the START SU Command • • • • The SUB and SEL options are not supported. A warning is returned if the SU is already in the STARTED state.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS LINE Command LINE line-name designates the line for which statistics are to be displayed. If you omit linename, statistics for the assumed line are displayed (see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs for details about the ASSUME command). SUB [ NONE | ALL | ONLY ] designates the subdevice to be aborted. NONE specifies that no subdevices are affected.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS LINE Command The statistics are described below. The information listed in the statistics display applies only after the last RESET and/or cold start. Reset Time is the date and time of the last reset operation. Sample Time is the current date and time. Total Frames is the number of frames sent at the CLB level. Frame Errors is the number of frame errors that have occurred at the CLB level. Pool Size is the size of the local pool in bytes.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS SU Command Line Errors is the number of line errors at the LIU level. Timeouts is the number of timeouts occurred. Invalid Responses is the number of invalid function frames received by the CLIP. Modem Errors is the number of modem errors encountered. Considerations for the STATS LINE Command • • If RESET is specified, all statistical counters are reset. The STATS command is not a sensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS SU Command SU subdevice-name designates the subdevice for which statistics are to be displayed. If you omit subdevice-name, statistics for the assumed subdevice are displayed (see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs for details about the ASSUME command). RESET If present, restores all the statistics counters to their initial values after the statistics are displayed.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATS SU Command Total I/O Operations is the number of I/O operations performed. LRC Errors is the number of LRC errors occurred on the SU. Parity Errors is the number of parity errors occurred for the SU. Message Overrun Errors is the number of message overruns occurred on the SU. NAKs Received is the number of NAKs received. Messages Received is the number of CLB frames received. Retries is the number of retries for block mode errors.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS Command Examples of the STATS SU Command The following SCF command displays the statistical information for the subdevice $ATPS1. #TERM: ->STATS SU $ATPS1.#TERM The following SCF command resets statistics counters for the subdevice $ATPS1.#TERM: ->STATS SU $ATPS1.#TERM,RESET STATUS Command The STATUS command displays dynamic information about the indicated object. STATUS is a nonsensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS LINE Command DETAIL If present, returns complete status information. If you omit DETAIL, only a single line of data is displayed for each object name. Display for the STATUS LINE Command The display for a LINE object without the DETAIL option is as follows: ATP6100 STATUS LINE Name $ATPS1 State STARTED PPID (2,62) BPID (3,62) I/O Addr 0,4,%3,%0 Track Id A00001 Name is the name of the line. State is the summary state of the line.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS LINE Command The display for a LINE object with the DETAIL option has the following format: ATP6100 Detail STATUS LINE line-name State.................STARTED PPid...............(2,62) Ldev..................68 BPid...............(3,62) Path..................A In Use.............NO I/O Addr..............0,4, %3, %0 CMG Ldev...........76 Track ID..............A00001 CMG................$ZZW01 CLB Frame Size........150 Dev Type...........
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS LINE Command Alternate IP indicates the alternate IP address used by the process. PPID indicates the CPU number and PIN of the primary ATP6100 process object associated with the line. BPID is the CPU number and PIN of the backup ATP6100 I/O process. In Use indicates if any subdevice of the line is opened. CMG Ldev is the LDEV of the CON Manager Process used.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS SU Command STATUS SU Command The STATUS SU command displays the dynamic information of a subdevice. STATUS SU is a nonsensitive command. Command Syntax for the STATUS SU Command The STATUS SU command has the following syntax: STATUS [ / OUT file-spec / ] SU subdevice-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STATUS SU Command SubdevNumber indicates the subdevice number. The display for a SU object with the DETAIL option has the following format: ATP6100 Detail STATUS SU subdevice-name Name..................$ATP1.#TERM State..............STARTED Path..................A DevType.............. (6,4) Inuse.................NO SubdevNumber.......1 Recsize............80 Name is the name of the line. Path is the primary path to the CLIP.
Managing ATP6100 Using the Subsystem Control Facility (SCF) STOP Command STOP Command The STOP command normally terminates the activity of an object. It nondisruptively deletes all connections to and from an object. Upon successful completion, configured objects are left in the STOPPED state. STOP is a sensitive command. STOP LINE Command The STOP LINE command terminates the activity of a line in a normal, orderly manner. The line is left in the STOPPED state. STOP is a sensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) • STOP SU Command Use the ABORT command to terminate an object immediately. Examples of the STOP Command The following command stops the line $ATPS1: ->STOP LINE $ATPS1 The following command stops all the subdevices as well as the line: ->STOP LINE $ATPS1, SUB ALL The following command stops only the subdevices: ->STOP LINE $ATPS1, SUB ONLY STOP SU Command The STOP SU command terminates the activate of a line in a normal, orderly manner.
Managing ATP6100 Using the Subsystem Control Facility (SCF) SUSPEND SU Command Example of the STOP SU Command The following SCF command stops the subdevice $ATPS1.#TERM: ->STOP SU $ATPS1.#TERM SUSPEND SU Command The SUSPEND command blocks the subdevice from accepting any 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 OPENer will be processed.
Managing ATP6100 Using the Subsystem Control Facility (SCF) SWITCH PROC Command SWITCH PROC Command The SWITCH PROC command causes the backup CIU path to become the primary CIU path and the primary CIU path to become the backup CIU path. SWITCH PROC is a sensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) TRACE LINE Command TRACE LINE Command The TRACE LINE command initiates, modifies, or terminates trace mode on ATP6100 lines. Using TRACE, you can request capture of target-defined data items, alter trace parameters, and end tracing. TRACE LINE 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.
Managing ATP6100 Using the Subsystem Control Facility (SCF) TRACE LINE 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 or until the end-of-file is reached if you do not select the WRAP option (described below).
Managing ATP6100 Using the Subsystem Control Facility (SCF) TRACE LINE Command keywords is subsystem-specific. See Table 6-4 for a list of the keywords that can be used with ATP6100. number is the numeric value represented by a keyword. TO file-spec specifies that a new trace is to be started and names the file to receive the trace information. An old file of that name is purged of data before the trace is initiated.
Managing ATP6100 Using the Subsystem Control Facility (SCF) TRACE LINE Command Note. Trace options can be specified as either keywords or corresponding numeric values. SCF accepts a combination of keywords and numeric values within a TRACE command. Also, numeric values are not verified by ATP6100—an undefined value has no effect and no warning is issued.
Managing ATP6100 Using the Subsystem Control Facility (SCF) VERSION Command VERSION Command The VERSION command displays the version level of a specified object. The command returns subsystem version information. VERSION is a nonsensitive command. VERSION PROC Command The VERSION PROC command displays the version level of the specified process. This is a nonsensitive command.
Managing ATP6100 Using the Subsystem Control Facility (SCF) VERSION PROC Command ATP6100 - T9337F40 - 20FEB96 - (NPV01A) T9337F40 shows the product and version number of the ATP6100 process. 20FEB96 is the VPROC (version process) date. NPV01A is the internal version number. GUARDIAN - T9050 - (F40) T9050 shows the version number of the NonStop Kernel operating system. The F40 is the internal version number.
Managing ATP6100 Using the Subsystem Control Facility (SCF) VERSION PROC Command Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 6- 44
7 PTrace Facility for ATP6100 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 ATP6100 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.
PTrace Facility for ATP6100 Determining the Subsystem 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. The command that follows traces the line $ATPL1 and puts the result of the trace in a file called MYFILE.
PTrace Commands for ATP6100 PTrace Facility for ATP6100 Table 7-1.
FROM Command PTrace Facility for ATP6100 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 7-2 lists the PTrace commands available for the ATP6100 subsystem. Table 7-2.
SELECT Command PTrace Facility for ATP6100 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.
STATETABLES Command PTrace Facility for ATP6100 Table 7-3.
PTrace Facility for ATP6100 Trace Example Trace Example The following commands will create a useful sample trace file. 1. Stop the asynchronous terminals and printers processes line: STOP LINE $ATPL1 2. Start the line: START LINE $ATPL1 3. Start the trace with the SCF TRACE command and specify SELECT ALL, PAGES 64, WRAP: TRACE LINE $ATPL1, TO , SELECT ALL, PAGES 64, WRAP 4. Wait for the ATP6100 line-ready console message: 5. Stop the trace: TRACE LINE $ATPL1, STOP 6.
A ATP6100 Subsystem Error Messages This appendix 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 ATP6100 subsystem are listed and described. These errors all have positive error numbers. Errors returned by the ATP6100 subsystem that have negative numbers are SCF errors common to all subsystems.
ATP6100 Subsystem Error Messages About ATP6100 Errors About ATP6100 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.
ATP6100 Subsystem Error Messages About ATP6100 Errors ATP6100 Error 00512 ATP6100 00512 START command rejected because of invalid combination of baudrate, interface, and controller type. Cause. The START command was rejected due to an inconsistent baud rate and interface to the SU, or inconsistent SU baud rate and LINE controller type, or inconsistent SU interface and LINE controller type. Effect. The START command is not executed. Recovery.
ATP6100 Subsystem Error Messages About ATP6100 Errors ATP6100 Error 00517 ATP6100 00517 START command failed due to CSM download error. Cause. The START command was rejected because of a CSM download error. The error could be caused by an improper download file. Effect. The START command is not executed. Recovery. Verify that the download file is correct. ATP6100 Error 00518 ATP6100 00518 STOP failed due to CLIP error. Cause. The ABORT or STOP SU command was rejected due to a CLIP error. Effect.
ATP6100 Subsystem Error Messages About ATP6100 Errors ATP6100 Error 00521 ATP6100 00521 Invalid attribute and subtype combination. LINE1FF is valid only for subtype 6 devices. Cause. The ALTER SU command failed because the LINE1FF modifier is valid only for subtype 6 devices. Effect. The ALTER SU command is not executed. Recovery. Alter the LINE1FF modifier only if the device is of subtype 6. ATP6100 Error 00522 ATP6100 00522 Invalid attribute and subtype combination.
ATP6100 Subsystem Error Messages About ATP6100 Errors ATP6100 Error 00525 ATP6100 00525 Altering ETXFLOWCHAR failed because either subtype is not 32 or ETXFLOW is disabled. Cause. The ALTER SU command for the ETXFLOWCHAR modifier failed because either subtype is not 32 or ETXFLOW is disabled. Effect. The ALTER SU command is not executed. Recovery. Alter the ETXFLOWCHAR modifier only if either the subtype is 32 or if ETXFLOW is enabled.
B SCF Command Summary for ATP6100 This appendix summarizes the syntax of the commands described in Section 6, Managing ATP6100 Using the Subsystem Control Facility (SCF). ABORT LINE Command The ABORT LINE command terminates the activity of the line as quickly as possible. ABORT [ /OUT file-spec / ] LINE line-name [ , SUB [ NONE | ALL | ONLY ] ] ABORT SU Command The ABORT SU command terminates the activity of the subdevice as quickly as possible.
SCF Command Summary for ATP6100 INFO LINE Command INFO LINE Command The INFO LINE command displays the current modifier settings for the specified line. INFO [ /OUT file-spec / ] LINE line-name [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ] INFO SU Command The INFO SU command displays the current modifier settings for the specified SU. INFO [ /OUT file-spec / ] SU subdevice-name [ , DETAIL ] LOAD LINE Command The LOAD LINE command downloads the Data Link Control (DLC) task to the SWAN/SWAN 2 concentrator.
STATS SU Command SCF Command Summary for ATP6100 STATS SU Command The STATS SU command displays statistical information for a subdevice. STATS [ /OUT file-spec / ] SU subdevice-name [ , RESET ] STATUS LINE Command The STATUS LINE command displays the dynamic information of a line. STATUS [ /OUT file-spec / ] LINE line-name [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ] STATUS SU Command The STATUS SU command displays the dynamic information of a subdevice.
SWITCH PROC Command SCF Command Summary for ATP6100 SWITCH PROC Command The SWITCH PROC command causes the backup CIU path to become the primary CIU path and the primary CIU path to become the backup CIU path. SWITCH [ / OUT file-spec / ] [ PROC proc-name ] TRACE LINE Command The TRACE LINE command initiates, modifies, or terminates trace mode on ATP6100 lines. Using TRACE, you can request capture of target-defined data items, alter trace parameters, and end tracing. TRACE LINE is a sensitive command.
C Moving to G-Series or H-Series RVUs Note. The ATP6100 subsystem subsystem is the same for G-series and H-series RVUs. There are no H-series migration considerations for the ATP6100 subsystem. This appendix discusses the differences between the ATP6100 subsystem on G-series and H-series RVUs and the ATP6100 subsystem on D-series and earlier RVUs.
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 or H-series RVUs.
COUP-to-SCF Considerations Moving to G-Series or H-Series RVUs Table C-2. ATP6100 Macro and Profile Correlations (page 2 of 2) D-Series Macros G-Series or H-series Profiles 5540 PATP5540 5573 PATP5573 5577 PATP5577 ASYNC_PRT PATPPRT 6401 PATP6401 6402 PATP6402 6511 PATP6511 6512 PATP6512 6520 PATP6520 6524 PATP6524 6530 PATP6530 6603 PATP6603 6604 PATP6604 ASYNC_TERM PATPTERM For more information on creating profiles, see the WAN Subsystem Configuration and Management Manual.
Moving to G-Series or H-Series RVUs Managing ATP6100 Lines Managing ATP6100 Lines The Peripheral Utility Program (PUP) and Dynamic System Configuration (DSC) of Distributed Systems Management (DSM) are not supported on G-series or H-series RVUs. The Subsystem Control Facility (SCF) replaces PUP and DSC for G-series and H-series RVUs. Note. TSM is not supported on Integrity NonStop NS-series servers. OSM is the supported system management tool for Integrity NonStop NS-series servers.
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).
Glossary command file 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.
Glossary ConMgr 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).
Glossary DSM/SCM 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.
Glossary fault tolerance 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.
Glossary IPM 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.
Glossary nonsensitive command 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.
Glossary Online Support Center (OSC) 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).
Glossary outage minutes 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.
Glossary problem incident report 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.
Glossary ServerNet adapter 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.
Glossary service connection 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).
Glossary super group 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.
Glossary TSM package 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 Integrity NonStop NS-series servers. TNSC.
Glossary $ZCNF $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.
Glossary $ZZWAN Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003 Glossary -16
Index A ABORT command definition 6-8 ABORT LINE command considerations 6-9 definition 6-8, B-1 syntax 6-8 ABORT SU command considerations 6-10 definition 6-9, B-1 syntax 6-9 ACTIVATE SU command considerations 6-10 definition 6-10, B-1 syntax 6-10 ALTER command definition 6-11 ALTER LINE command considerations 6-11 definition 6-11, B-1 syntax 6-11 ALTER SU command attribute-spec 6-12 considerations 6-13 definition 6-12, B-1 syntax 6-12 ASYNC modifier 4-11, 5-12 ATP6100 ADD DEVICE command 1-5, 3-5 ADD PROFILE
D Index Commands (continued) LOAD LINE 6-19, B-2 syntax 6-19 nonsensitive 6-7 sensitive 6-7 START 6-20 START LINE 6-20, B-2 syntax 6-20 START SU 6-21, B-2 syntax 6-21 STATS 6-22 STATS LINE 6-22, B-2 syntax 6-22 STATS SU 6-25, B-3 syntax 6-25 STATUS 6-28 STATUS LINE 6-28, B-3 syntax 6-28 STATUS SU 6-32, B-3 syntax 6-32 STOP 6-34 STOP LINE 6-34, B-3 syntax 6-34 STOP SU 6-35, B-3 syntax 6-35 SUSPEND SU 6-36, B-3 syntax 6-36 SWITCH PROC 6-37, B-4 syntax 6-37 TRACE LINE 6-38, B-4 select-spec 6-40 syntax 6-38 V
F Index ETXCHAR modifier 5-21 ETXFLOW modifier 4-15 ETXFLOWCHAR modifier 4-16 EVEN modifier 4-16, 5-21 F FULL modifier 4-16, 5-21 G G-series macro to profile correlation C-2 moving from D-series C-1 H HALF modifier 4-16, 5-21 HARD modifier 4-16, 5-22 HDTURN modifier 5-22 HIGHPIN OFF modifier 4-17, 5-22 I INFO command definition 6-14 INFO LINE command considerations 6-15 definition 6-14, B-2 syntax 6-14 INFO SU command considerations 6-18 definition 6-16, B-2 syntax 6-16 INTCHAR modifier 5-22 INTCHARx
O Index NOTPAUSE modifier 4-20 NOVFU72LINES modifier 4-21, 5-27 object files supported protocols 3-3 Object states 6-5 object-spec syntax 6-5 ODD modifier 4-21, 5-28 protocols associated object files 3-3 PROFILE objects 3-3 PTrace determining the subsystem 7-3 displaying trace data 7-3 formatting trace files 7-3 generating a trace file 7-2 recording trace data 7-3 P R PAGE modifier 5-28 PAGETERM modifier 5-28 PPOLL modifier 5-28 printer profiles 4-1 profiles PATP5512 4-2 PATP5515 4-3 PATP5516 4-4 PAT
T Index START SU command considerations 6-22 definition 6-21, B-2 syntax 6-21 STARTBOOT modifier 4-23, 5-31 STARTDOWN modifier 4-23, 5-31 States defined 6-5 object 6-5 summary ATP6100 6-6 STATS command definition 6-22 STATS LINE command considerations 6-25 definition 6-22, B-2 display with DETAIL option 6-23 syntax 6-22 STATS SU command considerations 6-27 definition 6-25, B-3 display with DETAIL option 6-26 syntax 6-25 STATUS command definition 6-28 STATUS LINE command considerations 6-31 definition 6-28
Index TPAUSE modifier 4-24, 5-32 Trace data displaying with PTrace 7-3 generating with PTrace 7-3 Trace file generating with PTrace 7-2 TRACE LINE command considerations 6-41 definition 6-38, B-4 select-spec 6-40 syntax 6-38 TYPE modifier 4-24, 5-32 U USERINTC modifier 5-33 V Values, time syntax 6-7 VERSION command definition 6-42 VERSION PROC command definition 6-42, B-4 display with DETAIL option 6-42 syntax 6-42 VTABD modifier 5-33 W WAN subsystem ATP6100 interface to 3-2 configuration prerequisites
