X25AM Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

X25AM Configuration

and Management

Manual

Abstract

This manual describes how to configure and manage the X25AM subsystem on

HP Integrity Nonstop™ NS-series and HP NonStop S-series systems and is for system

managers who install and manage X.25 lines or application programmers who use

X.25 lines for data communications.

Product Version

X25AM F40

Supported Release Version Updates (RVUs)

This manual supports G06.24 and all subsequent G-series RVUs and H06.03 and all

subsequent H-series RVUs until otherwise indicated in a new edition.

Part Number Published

523424-004 July 2005

Summary of content (248 pages)

PAGE 1
X25AM Configuration and Management Manual Abstract This manual describes how to configure and manage the X25AM subsystem on HP Integrity Nonstop™ NS-series and HP NonStop S-series systems and is for system managers who install and manage X.25 lines or application programmers who use X.25 lines for data communications. Product Version X25AM F40 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs and H06.
PAGE 2
Document History Part Number Product Version Published 137478 X25AM F40 February 1998 424910-001 X25AM F40 December 1999 523424-001 X25AM F40 February 2002 523424-002 X25AM F40 September 2003 523424-003 X25AM F40 April 2004 523424-004 X25AM F40 June 2005
PAGE 3
X25AM Configuration and Management Manual Glossary Index What’s New in This Manual xiii Manual Information xiii New and Changed Information Examples Figures Tables xiii About This Manual xvii Who Should Use This Manual xvii What’s in This Manual xvii Where to Get Other Information xviii Notation Conventions xix 1.
PAGE 4
Contents 3. Configuring an X25AM Subsystem (continued) 3.
PAGE 5
Contents 4. SCF Commands for the X25AM Subsystem (continued) 4.
PAGE 6
Contents 4. SCF Commands for the X25AM Subsystem (continued) 4.
PAGE 7
5. Attribute Descriptions Contents 5.
PAGE 8
5. Attribute Descriptions Contents 5. Attribute Descriptions PROTOCOL 5-12 PVC 5-13 PVCRANGE 5-13 RECSIZE 5-14 REMOTEADDREXT 5-14 REMOTEADDREXTTYPE 5-14 REMOTENET 5-14 RETRIES 5-15 REVERSECHG 5-15 REXMITTIMEOUT 5-15 RPOA 5-15 SRCADDR 5-16 SVCRANGE 5-16 SYNCS 5-16 T1TIMEOUT 5-17 THRESHOLD 5-17 THRUPUT 5-17 TRANSITDELAY 5-18 The Call User Data (CUD) Attribute 5-19 Default Values for the CUD 5-20 Dynamic and Static Values 5-20 Examples of the CUD Attribute 5-20 Errors 5-21 6.
PAGE 9
6. PTrace for the X25AM Subsystem (continued) Contents 6. PTrace for the X25AM Subsystem (continued) Tracing Level 3 6-13 What to Look for in Level 3 6-14 Level-3 Trace Example 6-15 Level-3 Trace Analysis 6-15 Sample Trace Reading of Calls Being Cleared The Application Level 6-21 Application Trace Analysis 6-24 Terminals and PAD Parameters 6-25 Common X.25 Terms 6-27 6-16 A. SCF Command Summary B. X25AM I/O Process Modifiers and Related SCF Line Attributes C.
PAGE 10
D. Using the NETID Modifier (continued) Contents D. Using the NETID Modifier (continued) PAD Profiles D-8 Standard PAD Profiles D-8 DATANET PAD Profiles D-10 DATAPAC PAD Profiles D-11 DATEX-P PAD Profiles D-14 DDN PAD Profiles D-16 DDXP PAD Profiles D-16 PSS PAD Profiles D-16 TELENET PAD Profiles D-17 TRANSPAC PAD Profiles D-19 TWINET PAD Profiles D-20 TYMNET PAD Profiles D-20 UNINET PAD Profiles D-20 PAD Parameter Examples D-21 TELENET Example D-21 DATAPAC Example D-21 Standard Example D-21 E.
PAGE 11
Glossary Contents Glossary Index Examples Example 1-1. Syntax to Create an X25AM I/O Process 1-6 Figures Figure 2-1. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 4-1. Figure 4-2. Figure 4-3. Figure 5-1. Figure 6-1. Figure 6-2.
PAGE 12
Tables (continued) Contents Tables (continued) Table 5-1. Table 5-2. Table 5-3. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 6-5. Table B-1. Table B-2. Table C-1. Table D-1. Table D-2. Table D-3. Table D-4. Table D-5. Table D-6. Table D-7. Table D-8. Table D-9. Table D-10. Table D-11. Table D-12. Table D-13. Table D-14. Table D-15. Table D-16. Table D-17. Table D-18. Table D-19. Table D-20. Table D-21. Table D-22. Table D-23. Table D-24. Table D-25. Table D-26.
PAGE 13
Tables (continued) Contents Tables (continued) Table D-27. Table D-28. Table D-29. Table D-30. Table D-31. Table E-1. Table F-1. Table F-2. Table F-3. Table F-4. Table F-5. Table F-6. Table F-7. Table F-8. Table F-9.
PAGE 14
Contents X25AM Configuration and Management Manual—523424-004 xii
PAGE 15
What’s New in This Manual Manual Information X25AM Configuration and Management Manual Abstract This manual describes how to configure and manage the X25AM subsystem on HP Integrity Nonstop™ NS-series and HP NonStop S-series systems and is for system managers who install and manage X.25 lines or application programmers who use X.25 lines for data communications. Product Version X25AM F40 Supported Release Version Updates (RVUs) This manual supports G06.24 and all subsequent G-series RVUs and H06.
PAGE 16
What’s New in This Manual • • New and Changed Information Updated Section 2, Overview of the X25AM Subsystem for NonStop NS-series changes.
PAGE 17
What’s New in This Manual ° ° ° ° ° ° ° ° ° ° ° ° New and Changed Information Command Syntax for the DISCONNECT Command on page 4-25 Command Syntax for the INFO Command on page 4-26 Command Syntax for the NAMES Command on page 4-30 Command Syntax for the PRIMARY Command on page 4-32 Command Syntax for the START Command on page 4-33 Command Syntax for the STATS Command on page 4-35 Command Syntax for the STATUS Command on page 4-43 Command Syntax for the STOP Command on page 4-48 Command Syntax for the ST
PAGE 18
What’s New in This Manual New and Changed Information X25AM Configuration and Management Manual—523424-004 xvi
PAGE 19
About This Manual The X25AM Configuration and Management Manual describes how to configure and manage the X25AM subsystem and includes: • • • • A configuration quick start that provides the basic information required to quickly and easily define and start an X25AM subsystem. An explanation of the major features and capabilities of the X25AM subsystem. An explanation of how to configure the X25AM subsystem using the Subsystem Control Facility (SCF) interactive interface to the WAN subsystem.
PAGE 20
Where to Get Other Information About This Manual Table i. Summary of Contents (page 2 of 2) Section Title This section . . . A SCF Command Summary Summarizes the syntax for the SCF commands to the X25AM subsystem. B X25AM I/O Process Modifiers and Related SCF Line Attributes Shows the relationship between X25AM I/O process modifiers and SCF line attributes. C X25AM Error Messages Describes network-related operator console and file-system error messages.
PAGE 21
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in 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.
PAGE 22
Change Bar 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.
PAGE 23
1 Configuration Quick Start This section is a configuration quick start for the ServerNet X25AM subsystem. This procedure explains how to set up the initial X25AM processes on an Integrity NonStop NS-series or NonStop S-series server. To help you complete the configuration tasks quickly, this section recommends you accept the default values provided by the X25AM subsystem.
PAGE 24
Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information Configuration Quick Start • Use the FILEINFO command to verify that you have the following X25AM files: ° ° ° $SYSTEM.SYSnn.X25OBJ $SYSTEM.SYSnn.PX250061 $SYSTEM.CSSnn.C1096P00 or $SYSTEM.CSSnn.C0051P00 (for T3880 SWAN concentrator) or $SYSTEM.CSSnn.C1096Q00 or $SYSTEM.CSSnn.C0051Q00 (for T3881 SWAN 2 concentrator) You need C0051P00 or C0051Q00 only if you are implementing an X.21 interface on a SWAN/SWAN 2 concentrator that has an X.
PAGE 25
Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information Configuration Quick Start b. Record the CLIP containing an available WAN line in the clip-num field in Table 1-1. c. Record an available WAN line number in the line-num field in Table 1-1. d. Record the path you prefer to use in the path-name field in Table 1-1. You can only use a path that has been configured. Note. PATH is optional; if not specified, PATH A is the default. 5.
PAGE 26
Add the X25AM Profile Configuration Quick Start -> STATUS PROCESS $zbpb TCPIP Status PROCESS \TOYS2.$ZBPB Status: STARTED PPID............ ( 1,134) Proto State TCP LISTEN TCP LISTEN TCP LISTEN TCP LISTEN TCP LISTEN UDP UDP UDP UDP Laddr 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 BPID................... ( 0,109) Lport 9000 telnet ftp finger echo 1025 68 67 69 Faddr 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.
PAGE 27
Add the X25AM I/O Processes Configuration Quick Start Add the X25AM I/O Processes Before adding any X25AM I/O processes, verify that all WAN processes, profiles, and a SWAN/SWAN 2 concentrator are added and started. During the Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information task (see Steps 3 through 5 of this task) you added the necessary information for executing the ADD DEVICE command to Table 1-1. Execute the ADD DEVICE command using the information in Table 1-1. Table 1-1.
PAGE 28
Configuration Quick Start Start the X25AM I/O Processes and Lines . Example 1-1. Syntax to Create an X25AM I/O Process -> ADD DEVICE $ZZWAN.#x25p1, PROFILE PX250061, & -> IOPOBJECT $SYSTEM.SYS00.X25OBJ, & -> PROGRAM $SYSTEM.CSS00.
PAGE 29
Configuration Quick Start Add X25AM Subdevices For information about other SCF commands for managing X25AM lines, see Section 4, SCF Commands for the X25AM Subsystem. Add X25AM Subdevices After starting an X25AM I/O process and its line, you can add the line’s required subdevices by using SCF commands for the X25AM subsystem. To add an X25AM subdevice, use the ADD SU command. For example: -> ADD SU $x25p1.
PAGE 30
Configuration Quick Start X25AM Configuration and Management Manual—523424-004 1 -8 Add X25AM Subdevices
PAGE 31
2 Overview of the X25AM Subsystem This section provides a brief introduction to the X25AM communications subsystem and describes the various configuration and monitoring programs that can be used with the X25AM product. Introduction to the X25AM Subsystem The X25AM communications subsystem connects Integrity NonStop NS-series or NonStop S-series servers to public or private packet switching data networks (PSDNs) or other computer systems using the X.25 standard set of networking conventions.
PAGE 32
Overview of the X25AM Subsystem X25AM Line applications can all communicate through a single X25AM I/O process and a single X25AM line. An X25AM I/O process is configured as a device using Subsystem Control Facility (SCF) commands to the WAN subsystem.
PAGE 33
X25AM Subdevice Overview of the X25AM Subsystem Subdevices are configured with the following characteristics: • • • • An X25AM protocol, indicating the desired type of connectivity. Circuit type, either a PVC or a switched virtual circuit SVC. A logical channel if the subdevice is on a PVC. Optional user facilities may be specified if the subdevice is on an SVC. You use SCF commands to the X25AM subsystem to start, stop, alter, and monitor X25AM subdevices.
PAGE 34
Overview of the X25AM Subsystem Packet Assembler/Disassembler (PAD) Packet Assembler/Disassembler (PAD) X25AM comes with its own software PAD application for your convenience. The X.3 Packet Assembler/Disassembler (X3PAD) program enables a user at an interactive (conversation-mode) terminal connected to an Integrity NonStop NS-series or NonStop S-series server to access other systems through a PSDN. X3PAD does not support block-mode terminals.
PAGE 35
Subscription Parameters Overview of the X25AM Subsystem Table 2-1 on page 2-5 lists the required subscription parameters supported by the X25AM subsystem. Table 2-1.
PAGE 36
Overview of the X25AM Subsystem Subscription Parameters X25AM Configuration and Management Manual—523424-004 2 -6
PAGE 37
3 Configuring an X25AM Subsystem When configuring the X25AM subsystem for Integrity NonStop NS-series or NonStop S-series servers, note that: • For systems running G-series and H-series RVUs, controllers are not supported. The ServerNet wide area network (SWAN) concentrator provides access to the WAN subsystem. . Note. To configure one or more SWAN concentrators, you can use WAN Wizard Pro as an alternative to using multiple SCF commands.
PAGE 38
WAN Subsystem Interface to the X25AM Subsystem Configuring an X25AM Subsystem Figure 3-1. SCF Interface to WAN and X25AM Subsystems Terminal OBEY File SCF Log File SCP WAN Subsystem X25AM Subsystem WAN Manager ($ZZWAN) X25AM I/O Process VST0301.
PAGE 39
Configuring an X25AM Subsystem Configuration Tasks The SCF commands to the WAN subsystem that are relevant to X25AM configuration are described in this section. The WAN subsystem and the SCF commands to the WAN subsystem are described in the WAN Subsystem Configuration and Management Manual. Configuration Tasks To configure the X25AM subsystem, perform the following tasks: 1. 2. 3. 4. 5. 6. 7. 8.
PAGE 40
Configuring an X25AM Subsystem Task 2: Familiarize Yourself with Subsystems, Commands, and Attributes Task 2: Familiarize Yourself with Subsystems, Commands, and Attributes Accessing the WAN Subsystem When issuing a command, you specify the subsystem in the line name (for example, $ZZWAN.#X25P1). SCP then routes the command to the correct subsystem (in this example, the WAN Manager). SCF commands manipulate objects.
PAGE 41
Configuring an X25AM Subsystem Task 3: Add the X25AM Profile X25AM Profile Object The PROFILE object in the WAN subsystem specifies the protocol to be used by a particular I/O process on the line it controls. An X25AM profile contains modifiers and default modifier values for the X.25 protocol. You create a profile from an object file provided on the SUT or from a previously created profile. The object file that is provided for X25AM is PX250061; the file is located in $SYSTEM.SYSnn. Note.
PAGE 42
Task 4: Determine the SWAN Configuration Information Configuring an X25AM Subsystem For detailed information about using the ADD PROFILE command, see the WAN Subsystem Configuration and Management Manual. Task 4: Determine the SWAN Configuration Information Before you add any X25AM I/O process, verify that all the WAN subsystem processes, profiles, and the SWAN concentrator have been added and started.
PAGE 43
Configuring an X25AM Subsystem Task 5: Add an X25AM I/O Process Task 5: Add an X25AM I/O Process To configure an X25AM I/O process, issue the SCF ADD DEVICE command to the WAN subsystem (see Figure 3-2 on page 3-8). The following example configures the X25AM I/O process $X25P1 as a DTE (the default) on line 0 of CLIP 3 of SWAN concentrator S01. It uses the default profile but modifies the defaults in the profile for the specified modifiers for this I/O process: -> -> -> -> -> -> -> -> ADD DEVICE $ZZWAN.
PAGE 44
Task 6: Start an X25AM I/O Process Configuring an X25AM Subsystem Figure 3-2. Adding an X25AM I/O Process 1. ADD DEVICE $ZZWAN.#X25P1 Management Information Base (MIB) DEVICE Object ($ZZWAN.#X25P1) WAN Subsystem $ZZWAN 2. Create object VST0302.vsd Task 6: Start an X25AM I/O Process After adding the X25AM profile and I/O processes, issue the SCF START command to the WAN subsystem (see Figure 3-3 on page 3-8) to start each I/O process: -> START DEVICE $ZZWAN.
PAGE 45
Task 7: Start an X25AM Line Configuring an X25AM Subsystem Task 7: Start an X25AM Line After an X25AM I/O process exists in the system-configuration database (as a DEVICE object) and has been started, you start the line that the I/O process controls using the SCF START LINE command to the X25AM subsystem. Starting a line is a dynamic change; the change remains in effect only until either a system restart or a subsequent SCF change to the line.
PAGE 46
Task 8: Add X25AM Subdevices Configuring an X25AM Subsystem The format for the output of the STATUS LINE command with the DETAIL option is: X25AM Detail Status Line $X25P1 Preferred IP....... 192.168.005.084 Track ID.... X017JJ CMG........ State....... STARTED PPIN....... LinkState... READY LDEV....... InUse....... YES Circuits... DCD......... ON DSR........ CMG LDev.... 151 Type....... PriTrace.... OFF BkpTrace... Alternate IP...... 192.168.007.084 $ZZW00 I/O ADDR.. ( 0,4,3,0) ( 0,3 ) BPIN.......
PAGE 47
Configuring an X25AM Subsystem Altering an X25AM I/O Process For more information about the SCF ADD SU command and commands to manage subdevices, see Section 4, SCF Commands for the X25AM Subsystem. This completes the X25AM configuration procedure. Altering an X25AM I/O Process After an X25AM I/O process and its line are started, you might need to make changes to the I/O process. To make persistent changes to an X25AM I/O process, you must issue the SCF ALTER DEVICE command to the WAN subsystem.
PAGE 48
List of X25AM I/O Process Modifiers Configuring an X25AM Subsystem Figure 3-5. Making Persistent Changes to an X25AM I/O Process Terminal Management Information Base (MIB) ALTER DEVICE $ZZWAN.X25P1 WAN Subsystem Object ($ZZWAN.#X25P1) $ZZWAN VST0305.vsd List of X25AM I/O Process Modifiers The current X25AM I/O process modifiers are listed in Table 3-1 on page 3-12 in alphabetical order. Note. Some X25AM modifiers that are listed are not supported but appear in the X25AM profile object.
PAGE 49
List of X25AM I/O Process Modifiers Configuring an X25AM Subsystem Table 3-1. List of X25AM Modifiers and Defaults (page 2 of 4) Modifier Name (Default Listed First) Default Setting CLBWINDOWNEXT Not in effect CLOCKnnnn 600 DCECLOCK or DTECLOCK DCECLOCK DRTIMEOUT 300 (3 seconds) DSRTIMER 2000 (20 sec.
PAGE 50
List of X25AM I/O Process Modifiers Configuring an X25AM Subsystem Table 3-1. List of X25AM Modifiers and Defaults (page 3 of 4) Modifier Name (Default Listed First) Default Setting Notes L3SENDTHRUPUT 4 -- L3WINDOW 2 -- MAXIOSIZE 4096 -- NOEXTFORMAT or EXTFORMAT NOEXTFORMAT -- NOREPORTDIRECT or REPORTDIRECT NOREPORTDIRECT -- NOSUSPENDSTATE Not set Determines whether the X25AM line enters the STOPPED or SUSPENDED state when the SWAN box is switched off.
PAGE 51
X25AM Modifier Dictionary Configuring an X25AM Subsystem Table 3-1. List of X25AM Modifiers and Defaults (page 4 of 4) Modifier Name (Default Listed First) Default Setting UNSOLF Not set V25 Not set If V25 is set, a relationship between the DTE and a GSTN DCE is assumed. X25V X25V1980 -- Notes -- Not applicable. X25AM Modifier Dictionary This subsection lists in alphabetical order the modifiers used in configuring X25AM I/O processes.
PAGE 52
Configuring an X25AM Subsystem • • Numeric Range Validation AUTOLOAD: The microcode for the CLIP is downloaded when the CLIP sends a status probe with an error status or when X25AM detects an error in the CLIP. NOAUTOLOAD: The microcode for the CLIP is not downloaded when the CLIP sends a status probe with an error status or when X25AM detects an error in the CLIP.
PAGE 53
Configuring an X25AM Subsystem Numeric Range Validation CLBDOWNLOADENTRIES Note: Not in effect (CLBDOWNLOADENTRIES is not supported) CLBDOWNLOADENTRIES has no effect on the X25AM line handler process. CLBSTATUSPROBETIME Note: Not in effect (CLBSTATUSPROBETIME is not supported) CLBSTATUSPROBETIME has no effect on the X25AM line handler process. CLBTIMER Note: Not in effect (CLBTIMER is not supported) CLBTIMER has no effect on the X25AM line handler process.
PAGE 54
Configuring an X25AM Subsystem Numeric Range Validation DISABLEPVCOUTOFORDER. See ENABLEPVCOUTOFORDER DRTIMEOUT n Default: 300 (3 seconds) Value: .01 seconds Range: 0 through 32767 (5 minutes, 27.67 seconds) DRTIMEOUT is the driver (I/O) timer. This is the maximum time interval allowed for a driver response before retrying a driver request. DSRTIMER n Default: 2000 (20 seconds) Value: .01 seconds Range: 0 through 32767 (5 minutes, 27.
PAGE 55
Numeric Range Validation Configuring an X25AM Subsystem Figure 3-6. DTE and DCE Functions Calling DTE Called DTE Call Request, Clear Request, or Data Packet Network Local DCE Call Connected, DCE Clear Confirm, Data Packet, or RR Remote DCE Incoming Call, Clear Indication, or Data Packet Call Accepted, DTE Clear Confirm, Data Packet, or RR VST0306.vsd DTECLOCK. See DCECLOCK EBCDIC.
PAGE 56
Configuring an X25AM Subsystem Numeric Range Validation ENABLECALLEDADDREXT Default: Not set Units: Not applicable Alternate Modifier None; use RESET ENABLECALLEDADDREX to reset this modifier Note: Only applies to Call Address Extension facility users ENABLECALLEDADDREXT specifies whether a Called Address Extension can be sent if the previous Call Accept packet does not contain this facility.
PAGE 57
Numeric Range Validation Configuring an X25AM Subsystem The default value of 50 pages should be sufficient for most customer configurations. However, for large server configurations, you should calculate the total amount of memory needed for all level-3 holding buffers to ensure that enough EXTENDEDPOOLPAGES are reserved. If there are not enough pool pages reserved, file-system error 33 (I/O process is unable to obtain buffer space) is returned.
PAGE 58
Configuring an X25AM Subsystem Numeric Range Validation (50 * 5095) / 2048 254,750 /2048 = 124.3 Ý 128 + 10 = 135 (less conservative) EXTFORMAT. See NOEXTFORMAT FIFO Default Not set Units: Not applicable Alternate Modifier: None; use RESET FIFO to reset this modifier This modifier allows X25AM to send L3 packets from SUs in the order they are generated. • • If set, X25AM sends the L3 packets in the order the application sends the data.
PAGE 59
Numeric Range Validation Configuring an X25AM Subsystem INCOMINGCALLS. See TWOWAYCALLS LINEQUALITYTHRESHOLD n Default: 500 Units: Frames Range: 100 through 10000 LINEQUALITYTHRESHOLD is the number of frames that the SWAN concentrator must send or receive before making a line quality check. The default value of 500 means that 500 frames are checked and then a line quality check number is reported.
PAGE 60
Configuring an X25AM Subsystem Numeric Range Validation L2IFRAMERECOVERY Note: Not in effect (L2IFRAMERECOVERY is not supported) L2IFRAMERECOVERY has no effect on the X25AM line handler process. L2NODISC Default: L2NODISC Units: Not applicable Alternate Modifier: L2DISC L2DISC or L2NODISC specifies whether or not a DISC (disconnect) command is sent when an X25AM I/O process wants to reset a link across a line.
PAGE 61
Configuring an X25AM Subsystem Numeric Range Validation L2WINDOW n Default: 4 Units: Integers Range: 1 through 7 L2WINDOW is the number of information (I) frames that can be sent before the first one is acknowledged. L2WINDOW is the network subscription parameter K. L3MOD128. See L3MOD8 L3MOD8 Default: L3MOD8 Units: Not applicable Alternate Modifier: L3MOD128 L3MOD8 or L3MOD128 determines the packet-numbering sequence. • • L3MOD8: Specifies modulo 8.
PAGE 62
Configuring an X25AM Subsystem Numeric Range Validation L3SENDTHRUPUT n Default: 4 Units: Integers Range: 3 through 12 L3SENDTHRUPUT specifies the sending throughput class for the line. The default value is 4 (150 bps). There are 16 throughput classes (numbered from 0 through 15). The value depends on the network. Table 3-2. Throughput Classes and Bits Per Second Throughput Class Bits Per Second (bps) 0 Reserved according to the ITU-T X.25 Recommendation 1 Reserved according to the ITU-T X.
PAGE 63
Numeric Range Validation Configuring an X25AM Subsystem MAXIOSIZE Default: 4096 Units: Bytes Range: 1 through 32767 The value of MAXIOSIZE determines the maximum size of a message that an application accessing the X25AM process can transmit or receive. The value sets the maximum I/O buffer size. When used with PTP subdevices, the size does not include the Message Control Word (MCW).
PAGE 64
Configuring an X25AM Subsystem Numeric Range Validation NOAUTOLOAD. See AUTOLOAD NOCALLS. See TWOWAYCALLS NOCALLUSERDATA. See CALLUSERDATA NOEXTFORMAT Default: NOEXTFORMAT Units: Not applicable Alternate Modifier: EXTFORMAT NOEXTFORMAT or EXTFORMAT specifies whether to enable or disable extended format packets for Call Request, Call Accepted, Clear, and Clear Confirmation packets. NOEXTFORMAT disables extended packets. X25AM rejects these extended format packets. EXTFORMAT enables extended packets.
PAGE 65
Configuring an X25AM Subsystem Numeric Range Validation NOSTRIPPARITY. See STRIPPARITY NOSUSPENDSTATE Default: Not set Units: Not applicable When this modifier is set, the X25AM line goes to the STOPPED state when the SWAN box is switched off, instead of going to the SUSPENDED state. OUTGOINGCALLS.
PAGE 66
Configuring an X25AM Subsystem Numeric Range Validation POOLPAGES. See EXTENDEDPOOLPAGES Profile^Version Default: Not set Units: Not applicable Range: None Profile^Version gives a version to the profile configured for use by an X25AM I/O process. The profile version must match the version with which the X25AM I/O process is configured to be used. PROGRAM download-filename Default: filename = $SYSTEM.CSSnn.C1096P00 Units: Not applicable Alternate Modifiers: $SYSTEM.CSSnn.C0051P00, $SYSTEM.
PAGE 67
Configuring an X25AM Subsystem Numeric Range Validation RS422. See RS232 Rxx n. See Txx n SENDCALLINGADDRESS Default: SENDCALLINGADDRESS Units: Not applicable Alternate Modifier: NOSENDCALLINGADDRESS SENDCALLINGADDRESS or NOSENDCALLINGADDRESS specifies whether or not a default address is used in the calling address field of outgoing call request packets. • • SENDCALLINGADDRESS: Uses the address assigned to the line (with the SCF line attribute SRCADDR) as the calling address.
PAGE 68
Numeric Range Validation Configuring an X25AM Subsystem SYNCS Note: Not in effect (SYNCS is not implemented) SYNCS has no effect on the X25AM line handler process. TWOWAYCALLS Default: TWOWAYCALLS Units: Not applicable Alternate Modifiers: NOCALLS INCOMINGCALLS or NOINCOMINGCALLS OUTGOINGCALLS or NOOUTGOINGCALLS TWOWAYCALLS and the alternate modifiers enable and disable calls. Call requests are allowed even if LINE SRCADDR or SUBDEVICE DESTADDR, or both, are null.
PAGE 69
Numeric Range Validation Configuring an X25AM Subsystem be retried. xx is the modifier number listed in the Timer or Retry Counter column in the table. n is the value of the modifier. Ranges are shown in parentheses. Table 3-4.
PAGE 70
Numeric Range Validation Configuring an X25AM Subsystem Table 3-5.
PAGE 71
Configuring an X25AM Subsystem Numeric Range Validation X25V yyyy Default: X25V1980 Units: Not applicable Alternate Modifier: X25V1984 X25V yyyy is the version modifier identifying the X.25 standard that must be supported by the X25AM process. X.25 standards are identified by year. There is no modifier name—you specify only the value. • • X25V1980 allows 1976 and 1980 extended formats and standards and 1984 standards not requiring extended formats.
PAGE 72
Configuring an X25AM Subsystem Numeric Range Validation X25AM Configuration and Management Manual—523424-004 3- 36
PAGE 73
4 SCF Commands for the X25AM Subsystem This section contains the following: • • • • An overview of the Subsystem Control Facility (SCF), its features and operation A description of the SCF interface to the X25AM subsystem A description of the X25AM objects Descriptions of SCF commands for the X25AM subsystem For additional information about SCF, see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs.
PAGE 74
Subsystem Control Point (SCP) SCF Commands for the X25AM Subsystem Figure 4-1. SCF Interface to WAN and X25AM Subsystems Terminal OBEY File SCF Log File SCP WAN Subsystem X25AM Subsystem WAN Manager ($ZZWAN) X25AM I/O Process VST0401.vsd Subsystem Control Point (SCP) The subsystem control point (SCP) is a network-management process for receiving and redistributing the messages that SCF sends to certain data communications subsystems.
PAGE 75
SCF Commands for the X25AM Subsystem How SCF Works You can use the HELP command to display a list of the available SCF commands and to request additional specific information, such as command syntax. Commands that operate on the X25AM subsystem objects are described in this section. Commands such as OUT, ASSUME, and HELP are not subsystem-specific and are described in the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs.
PAGE 76
SCF Commands for the X25AM Subsystem General Command Format General Command Format An SCF command always begins with a keyword that identifies it (such as ADD, START, or STATS). SCF controls many data communications subsystems whose individual components are objects. Each object has an object type and an object name. The object type describes the type of the object, such as LINE or PROCESS. The object name uniquely identifies an object within the system.
PAGE 77
SCF Interface to the X25AM Subsystem SCF Commands for the X25AM Subsystem SCF Interface to the X25AM Subsystem An X25AM subsystem consists of one or more I/O processes residing on a single NonStop system (node). After an X25AM I/O process exists in the MIB (as a DEVICE object) and has been started, you can start, stop, and alter the line it controls with SCF commands to the X25AM subsystem. For example, Figure 4-2 illustrates the ALTER command issued to a LINE object.
PAGE 78
SCF Commands for the X25AM Subsystem X25AM Subsystem Objects X25AM Subsystem Objects This section describes the following topics: • • • • Object types and object names Object states Object attributes and attribute specifiers Frequently performed tasks on X25AM objects Object Types and Object Names You can manipulate the X25AM subsystem using SCF commands that act on one or more X25AM subsystem objects. Each object has an object type and an object name.
PAGE 79
Object Types and Object Names SCF Commands for the X25AM Subsystem Figure 4-3. X25AM Object-Type Hierarchy PROCESS LINE SU SU SU VST0403.vsd Object Names When you configure the X25AM I/O process or when you add subdevices, you specify names that you use later in management commands. The names you assign must conform to the following conventions. • PROCESS Object Names When you assign a name to a PROCESS object, you must make sure it conforms to the conventions for process names.
PAGE 80
Object States SCF Commands for the X25AM Subsystem notation at the subdevice level. For a more complete description of wild-card notation, see the TACL Reference Manual. Object-Spec Syntax This subsection describes the syntax rules for an object-spec, which is a combination of an object-type and an object-name. Table 4-1.
PAGE 81
Object Attributes SCF Commands for the X25AM Subsystem SUSPENDED The LINE object is in a STARTED state but loses contact with the SWAN CLIP and is unable to contact it. SU objects do not change state when the line they are associated with becomes suspended. Object Attributes Attributes are the named, configurable characteristics of objects. X25AM objects have an associated set of attributes that can be set or altered using the ADD or ALTER commands.
PAGE 82
Commands Supported by the X25AM Subsystem SCF Commands for the X25AM Subsystem Table 4-2.
PAGE 83
Sensitive and Nonsensitive Commands SCF Commands for the X25AM Subsystem Table 4-3. SCF Commands Supported by X25AM Subsystem (page 2 of 2) Command PROCESS LINE SU STOP X X STOPOPENS X X SWITCH X X TRACE X VERSION X X * Supported for LINE object with SUB ONLY option. Sensitive and Nonsensitive Commands Because some commands can have detrimental effects if improperly used, special qualification is required to use them. These commands are sensitive.
PAGE 84
SCF Commands for the X25AM Subsystem ABORT Command ABORT Command The ABORT command terminates the operation of objects as quickly as possible. Only enough processing is done to ensure the security of the subsystem. The object is left in the STOPPED state. This is a sensitive command. Command Syntax for the ABORT Command ABORT [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 85
SCF Commands for the X25AM Subsystem Considerations for the ABORT Command Considerations for the ABORT Command • • • • • • For more controlled termination of lines and subdevices, use the STOP command. To initiate the operation of lines and subdevices, use the START command. X25AM does not support the SEL option. When you use the ABORT command, all activities being performed by the lines and subdevices come to a halt, and files and listings can be left in an inconsistent or incomplete state.
PAGE 86
SCF Commands for the X25AM Subsystem Command Syntax for the ADD Command attribute-spec is a specification of an attribute and a value to be assigned to it. If you use the LIKE option, attribute-spec overrides the value assigned to the attribute by the LIKE option. The attribute-spec for an SU object is one of the following attribute-name-andvalue combinations. Note that X25AM requires the first three attributes. The attributes are listed alphabetically in Section 5, Attribute Descriptions.
PAGE 87
SCF Commands for the X25AM Subsystem Examples of the ADD Command Examples of the ADD Command The following command adds an SU: -> ADD SU $x25p1.#term, PROTOCOL ITI, DEVTYPE (6,0), & -> RECSIZE 80, PORT 1, CPADPARMS (1,1 2,15 3,2 4,0), & -> DESTADDR “00009901” The following command adds a new SU named $X25P1.#TERM1 and gives it the same attributes as the SU named $X25P1.#TERM: -> ADD SU $x25p1.#term1,LIKE $x25p1.
PAGE 88
SCF Commands for the X25AM Subsystem • • • • • ALLOWOPENS Command The name you give to an added subdevice must be unique. X25AM does not support the SUB or SEL option. A given attribute can appear only once in a single ADD command. If you do not specify an attribute specification for a given object in the ADD command, SCF uses the default value for that attribute. However, some attributes do not have default values; these attributes must be specified in the ADD command.
PAGE 89
SCF Commands for the X25AM Subsystem Examples of the ALLOWOPENS Command SUB [ subtype ] selects the subordinate objects that the command affects. subtype can be a subordinate object type or the keyword ONLY. If you select a subordinate object type, only objects of that type are affected. ONLY specifies that only the subordinate objects are affected. Examples of the ALLOWOPENS Command The following command stops any opens on the SU named $SX1.
PAGE 90
SCF Commands for the X25AM Subsystem Command Syntax for the ALTER Command Command Syntax for the ALTER Command Syntax: ALTER [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , LIKE object-name ] [ , attribute-spec ]... OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name | SU su-name designates the line or subdevice whose attributes you want to alter.
PAGE 91
SCF Commands for the X25AM Subsystem Attribute-Spec for the ALTER LINE Command Attribute-Spec for the ALTER LINE Command The attribute-spec for a LINE object is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 5, Attribute Descriptions. [ BCUG { integer | RESET } ] [ BPADPARMS { ( integer , integer [ integer , integer ]...
PAGE 92
SCF Commands for the X25AM Subsystem Attribute-Spec for the ALTER SU Command Attribute-Spec for the ALTER SU Command The attribute-spec for an SU object is one of the following attribute name and value combinations. The attributes are listed alphabetically in Section 5, Attribute Descriptions. [ ACCEPTCHG { ON | OFF } ] [ BCUG { integer | RESET } ] [ BPADPARMS { ( integer , integer [ integer , integer ]... ) | RESET } ] [ CPADPARMS { ( integer , integer [ integer , integer ]...
PAGE 93
SCF Commands for the X25AM Subsystem Examples of the ALTER Command The following command alters the line named $X25P1 to resemble the line named $X25S1: -> ALTER LINE $x25p1, LIKE $x25s1 The following commands alter the CPADPARMS for an SU: -> INFO SU $x25p1.#term, DETAIL -> ALTER SU $x25p1.#term, CPADPARMS (1,1 2,15 3,2 4,0 13,0) Note. When you alter CPADPARMS or BPADPARMS, you must specify the values for all the pairs, not just the one pair you want to alter.
PAGE 94
Considerations for the ALTER Command SCF Commands for the X25AM Subsystem The following command sets the CUD for the subdevice named $X25P1.#TERM: -> ALTER SU $x25p1.#term, CUD “1234” Considerations for the ALTER Command • • • • • • The line or subdevice must be in the STOPPED state before you can alter its attributes. An attribute can appear only once in a single ALTER command.
PAGE 95
SCF Commands for the X25AM Subsystem Considerations for the ALTER Command Table 4-4.
PAGE 96
SCF Commands for the X25AM Subsystem DELETE Command DELETE Command The DELETE command removes subdevices from the X25AM subsystem. This is a sensitive command. Command Syntax for the DELETE Command Syntax: DELETE [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name | SU su-name designates the subdevices or the line whose subdevices are to be deleted.
PAGE 97
SCF Commands for the X25AM Subsystem Considerations for the DELETE Command Considerations for the DELETE Command • A subdevice must be in the STOPPED state before it can be deleted. For example, to stop and then delete a subdevice, use the following commands: -> STOP SU $SIP2.#term -> DELETE SU $SIP2.
PAGE 98
INFO Command SCF Commands for the X25AM Subsystem INFO Command The INFO command displays the current values of the attributes for lines and subdevices. This is a nonsensitive command. Command Syntax for the INFO Command Syntax: INFO [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , DETAIL ] [ , SUB [ subtype ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name | SU su-name specifies information for a particular line or subdevice.
PAGE 99
SCF Commands for the X25AM Subsystem Display for the INFO LINE Command Name shows the name of the LINE object. L3Window shows the number of packets that can be outstanding without an acknowledgment from the network. The range is 1 through 15. PacketSize shows the size, in bytes, of each packet. Type shows the LINE object's type and subtype. Retries shows the number of level-2 retries (N2) to be attempted before a disconnect. This value must be in the range 0 through 255.
PAGE 100
Display for the INFO SU Command SCF Commands for the X25AM Subsystem Display for the INFO SU Command The format of the display for the INFO SU command without the DETAIL option is: X25AM Info SU Name $X25P1.#TERM Protocol ITI DevType ( 6,0 ) Recsize 80 Destaddr Name is the name of the SU object. Protocol shows the protocol the subdevice uses. DevType shows the device type and subtype for the SU. The device type depends on the protocol. The subtype depends on the protocol and terminal. Table 4-5.
PAGE 101
Examples of the INFO Command SCF Commands for the X25AM Subsystem The format of the display for the INFO SU command with the DETAIL option is given below. An asterisk in the display denotes an alterable attribute. The attributes are listed alphabetically in Section 5, Attribute Descriptions. X25AM Detail Info SU $X25P1.#TERM *AcceptChg.... OFF *DevType.... *PVC.......... *Parity..... *Port......... 0 *Protocol... *RexmitTimeout 0:20.00 *ReverseChg. *CUG.......... *Nullfill... *CUGType...... BASIC *BCUG.
PAGE 102
SCF Commands for the X25AM Subsystem Considerations for the INFO Command Considerations for the INFO Command • • • You can now display the entire Call User Data (CUD) field by using the SCF INFO SU, DETAIL command. X25AM does not support the SEL option, the DEFAULT option, or the attribute-name option. X25AM supports the SUB option only for the LINE object type. NAMES Command The NAMES command returns a list of the subordinate object types and names for the specified object.
PAGE 103
Object-Spec for the NAMES Command SCF Commands for the X25AM Subsystem Object-Spec for the NAMES Command The NAMES command has the following object-spec: object-type object-name null LINE SU process-name line-name su-name The format of the display for the NAMES command is: X25AM NAMES $X25P1.#* SU $X25P1.#XNAM $X25P1.#TERM $X25P1.#TERM2 LINE $X25P1 The format of the display for the NAMES SU command is: X25AM Names SU $X25P1.#TERM $X25P1.
PAGE 104
SCF Commands for the X25AM Subsystem PRIMARY Command PRIMARY Command The PRIMARY command causes the backup CPU to become the primary CPU and the primary CPU to become the backup CPU. This is a sensitive command. Caution. Exercise caution when using the PRIMARY or SWITCH command. Either command causes all SVCs to clear and PVCs to reset. Before you use either command, it is a good idea to warn other users so they can close any open files.
PAGE 105
SCF Commands for the X25AM Subsystem Considerations for the PRIMARY Command Considerations for the PRIMARY Command • • • • If the specified CPU is not the CPU of the backup process, X25AM rejects the command. A non-error completion of the PRIMARY command indicates only that the subsystem was able to initiate processing for the PRIMARY operation. It does not necessarily indicate that the operation completed successfully.
PAGE 106
SCF Commands for the X25AM Subsystem Examples of the START Command LINE line-name | SU su-name designates the line or subdevice to be started. If you omit line-name or su-name, the assumed object is started (for information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs). SUB [ subtype ] selects the subordinate objects that the command affects. subtype can be a subordinate object type or one of the keywords ONLY or ALL.
PAGE 107
SCF Commands for the X25AM Subsystem STATS Command STATS Command The STATS command displays statistical information on the execution history of lines and subdevices. It shows dynamic information such as the number of packets sent and received and the number of errors. This is a nonsensitive command. Note. To issue the STATS command, first you need the name of the line or subdevice. To find the names of your X25AM lines, enter LISTDEV TYPE 61 at the SCF prompt. TYPE 61 refers to the X25AM subsystem.
PAGE 108
Display for the STATS LINE Command SCF Commands for the X25AM Subsystem ALL specifies that the named object and the subordinate objects are affected. If you omit subtype, ALL is assumed. Display for the STATS LINE Command The format of the display for the STATS LINE command is: X25AM STATS Line $X25P1 Resettime 7:04:59.023 10/12/99 Line Quality 100 Sampletime 8:07:22.
PAGE 109
SCF Commands for the X25AM Subsystem Display for the STATS LINE Command For example, if the THRESHOLD value is 500, each 500 frames are compared to the last block of 500 frames. If there are 5 errors (1 percent of 500), the line quality drops to 99. With a THRESHOLD value of 500, 0 to 4 errors gives 100 percent line quality, 5 to 9 errors gives 99 percent line quality, 10 to 14 errors give 98 percent line quality, and so on. A change in value of less than 1 percent does not appear.
PAGE 110
SCF Commands for the X25AM Subsystem Display for the STATS LINE Command Diag shows the number of diagnostic request packets received. RR shows the number of receive ready packets sent and received. RNR shows the number of receive not ready packets sent and received. REJ shows the number of reject packets sent and received. Confirmation Packets The information in this field shows confirmation-packet send and receive information. X.
PAGE 111
SCF Commands for the X25AM Subsystem Display for the STATS LINE Command I^NOP shows the number of I-frames without the poll bit set that have been sent and received. RR shows the number of receive ready frames sent and received. Receive Ready frames are used by the DTE/DCE to indicate it is ready to receive. RNR shows the number of receive not ready frames sent and received. Receive Not Ready (RNR) frames are used by the DCE/DTE to indicate a busy condition.
PAGE 112
SCF Commands for the X25AM Subsystem Display for the STATS LINE Command CLIP Errors Errors on the line between the I/O and the CLIP are reported under CLIP errors. The information in this field shows the CLIP error information listed below: FCS shows the number of frames received with errors in the frame-check sequence (FCS). Modem shows the number of modem-signal handshaking errors.
PAGE 113
Display for the STATS SU Command SCF Commands for the X25AM Subsystem Frames shows the total number of frames handled. No Buffs shows the total number of buffer-allocation errors. Errors shows the total number of received frames that contained errors. Buffer Pool Information in Pages The information in this field shows the memory pool statistics for all lines. This information is related to the actual amount of memory space required by the X25AM subsystem for buffers.
PAGE 114
SCF Commands for the X25AM Subsystem Examples of the STATS Command Sampletime is the current date and time. CircuitNum is the circuit number associated with this SU object. MsgSends is the current count of messages sent on this circuit. MsgReceives is the current count of messages received on this circuit. Examples of the STATS Command The following command shows statistics for the subdevice named $X25P1.#TERM: -> STATS SU $x25p1.
PAGE 115
Command Syntax for the STATUS Command SCF Commands for the X25AM Subsystem Command Syntax for the STATUS Command Syntax: STATUS [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , DETAIL ] [ , SUB [ subtype ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LINE line-name | SU su-name designates the line or subdevice whose status information is to be displayed.
PAGE 116
Display for the STATUS LINE Command SCF Commands for the X25AM Subsystem State is the current summary state of the line object. PPID is the CPU number and PIN of the primary X25AM I/O process. BPID is the CPU number and PIN of the backup X25AM I/O process. I/O ADDR is the primary I/O address, in the form (channel, physical address type, clip number, line number). Channel is no longer used. T is the type. Only type 61 is allowed. S is the subtype. Only subtype 63 is allowed.
PAGE 117
SCF Commands for the X25AM Subsystem Display for the STATUS LINE Command BPIN is the CPU and PIN of the backup X25AM I/O process. Circuits is the number of circuits on the line. CMG is the name of the Concentrator Manager process associated with the I/O process. CMG Ldev is the LDEV of the Concentrator Manager process. CTS shows whether the Clear To Send (CTS) signal is on or off. DCD indicates whether the Data Carrier Detect (DCD) signal is on or off.
PAGE 118
Display for the STATUS SU Command SCF Commands for the X25AM Subsystem PPIN indicates the CPU and PIN of the primary X25AM I/O process. Preferred IP indicates the preferred IP address used by the process. State indicates the current summary state of the LINE object. Subtype is the subtype of the X25AM line. Only subtype 63 is allowed. PriTrace shows whether trace is turned on or off for the primary process. Track ID indicates the unique hardware identification of the SWAN concentrator (adapter).
PAGE 119
Examples of the STATUS Command SCF Commands for the X25AM Subsystem Table 4-6. Subdevice Types and Subtypes Type Protocol Subtype Terminal 6 ITI 0 Conversational-mode terminal 1 6510 (ADM-2) terminal 2 6520 (ZENTEC) terminal 4 6530 terminal 9 PTP 0 Not applicable 58 QLLC 20 Not applicable 63 NAM 0 Not applicable Recsize shows the maximum length of records received or transmitted by the SU. This value is in the range 1 through 4095. SUnum is the number of the SU object.
PAGE 120
SCF Commands for the X25AM Subsystem STOP Command STOP Command The STOP command terminates the activity of an object in a normal manner. It deletes all connections to and from the object in a nondisruptive way. Upon successful completion of the STOP command, configured objects are left in the STOPPED state and nonconfigured objects are deleted. This is a sensitive command.
PAGE 121
SCF Commands for the X25AM Subsystem • • • • STOPOPENS Command You cannot stop a LINE object in the STARTING state by using the STOP command. You can stop a LINE object or an SU object only when it does not have any connections. You cannot stop a LINE object if a subdevice on the line is open. You cannot stop an SU object if the subdevice is open. STOPOPENS Command The STOPOPENS command prevents any more opens from being issued to an object, without disrupting any of the current activity.
PAGE 122
SCF Commands for the X25AM Subsystem Considerations for the STOPOPENS Command The following command prevents anyone else from opening all subdevices on the line named $X25P1 after you issue it: -> STOPOPENS LINE $x25p1, SUB ONLY Considerations for the STOPOPENS Command • • • X25AM does not support the SEL option. X25AM supports the SUB option only for the LINE object type. If you use the object-type LINE, you must also use the SUB option set to SUB ONLY.
PAGE 123
Examples of the SWITCH Command SCF Commands for the X25AM Subsystem Examples of the SWITCH Command The following command causes the process $X25P1 to switch to PATH B: -> SWITCH PROCESS $x25p1, PATH B The following command causes the line $X25P1 to switch to PATH A: -> SWITCH LINE $x25p1, PATH A Considerations for the SWITCH Command • • • X25AM does not support the SUB or SEL option.
PAGE 124
SCF Commands for the X25AM Subsystem Command Syntax for the TRACE Command LINE line-name designates the line to be traced. If you omit line-name, SCF traces the assumed line (for information about the ASSUME command, see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs). STOP [ , BACKUP ] discontinues the trace currently in progress. If you specify BACKUP, SCF stops only the trace of the backup process.
PAGE 125
Command Syntax for the TRACE Command SCF Commands for the X25AM Subsystem SELECT select-spec select-spec is one of the following specifications: { { { { keyword (keyword [ , keyword ]...) number (number [ , number ]... ) } } } } keyword is subsystem-specific. For a list of the keywords that can be used with X25AM, see Table 4-7. number is the numeric value that a keyword represents. TO file-spec specifies the file that SCF writes trace information to.
PAGE 126
SCF Commands for the X25AM Subsystem Examples of the TRACE Command Examples of the TRACE Command The following command starts a trace on the line, puts the results in a file named TRCFILE, and selects the IOS, CLIPDI, CLIPDO trace options: -> TRACE LINE $x25p1,TO trcfile, SELECT (IOS,CLIPDI,CLIPDO) -> PAGES 64, RECSIZE 2000 & The following command stops the trace of the line named $X25P1: -> TRACE LINE $x25p1, STOP Note. You can also create a trace file with FUP.
PAGE 127
VERSION Command SCF Commands for the X25AM Subsystem Table 4-8. User-Request Parameters Request Value Parameter Use CONTROL 0 p4.<3:15> Function control number READ 1 p4.<1:15> Read count WRITE 2 p4.<1:15> Write count WRITEREAD 3 p3.<1:15> p4.<1:15> Write count Read count SETMODE 7 p3 First parameter of SETMODE p4 Second parameter of SETMODE p5 Open file-name ID p6 SETMODE function number VERSION Command The VERSION command displays the version level of the specified object.
PAGE 128
Examples of the VERSION Command SCF Commands for the X25AM Subsystem The information displayed by the VERSION command with the DETAIL option has the following format: Detailed VERSION \TOYS2.$X25P1 SYSTEM \TOYS2 X25AM - T9060F40 - 25JUN1999 - X25AM F40 GUARDIAN - T9050 - (Q06) SCF KERNEL - T9082G02 - (12JUL99) (15JUN99) X25AM PM - T9323F40 - (09APR99) - F40_AAI X25AM - T9060F40 - 25JUN1999 - X25AM F40 T9060F40 shows the product and version number of the X25AM process.
PAGE 129
5 Attribute Descriptions This section contains the following: • • A description of each attribute used in the SCF commands to the X25AM subsystem A description of the Call User Data (CUD) feature, including an illustration The attributes are listed in alphabetical order. The syntax for these attributes is given in Command Syntax for the ADD Command on page 4-13, Attribute-Spec for the ALTER SU Command on page 4-20, and Attribute-Spec for the ALTER LINE Command on page 4-19.
PAGE 130
BCUG Attribute Descriptions BCUG specifies the bilateral closed user group (BCUG) ID. The value must be in the range 0 through 9999. RESET means to delete any existing BCUG attribute. The default is no BCUG ID. Default: Not applicable Range: 0 through 9999 Objects: Subdevices BPADPARMS specifies the block-mode X.3 PAD parameters. The value must be specified as pairs of integers (the parameter number and its value). This attribute is valid only if the PROTOCOL attribute value is ITI.
PAGE 131
CALLS Attribute Descriptions CALLS declares whether calls cannot be connected (NONE), can be initiated by a DTE (OUTGOING), can be received by a DTE (INCOMING) or can be initiated and received by a DTE (TWOWAY). Default: TWOWAY Range: NONE, OUTGOING, INCOMING, or TWOWAY Objects: Lines CHARACTERSET This attribute is not supported for systems running G-series or H-series RVUs. CLOCKMODE sets the mode of the clock.
PAGE 132
CUD Attribute Descriptions uses the line’s CPADPARMS. If the line’s CPADPARAMS are not specified either, then X25AM uses the standard PADPARMS according to the NETID. RESET means to delete all CPADPARMS assignments. Default: Determined by network. Range: (3,2)/(3,126). For descriptions of standard PAD profiles, see Appendix D, Using the NETID Modifier. Objects: Subdevices and lines. CUD specifies the call user data (CUD) field (up to 16 bytes) in a call-request packet.
PAGE 133
DDNPREC Attribute Descriptions If you omit CUGTYPE and CUG is less than 99, the CUGTYPE default value is BASIC. If you omit CUGTYPE and CUG is greater than 99, the CUGTYPE default value is EXT. When you select RESET for the CUG attribute, CUGTYPE reverts to its default value (BASIC). Default: BASIC Range: BASIC, BASICOA, EXT, or EXTOA Objects: Lines and Subdevices DDNPREC specifies the priority or the precedence negotiated by an X.25 DTE.
PAGE 134
DEVTYPE Attribute Descriptions using SETPARAM or CALL^REQ in PTP mode 2. If no DESTADDR is present, the packet is sent with a called address length of zero (0). Default: None Range: String of decimal digits (0 through 9) up to 15 digits long Objects: Subdevices DEVTYPE specifies the device type and subtype for an SU. The device type depends on the protocol you use. The subtype depends on the protocol and the terminal. DEVTYPE is a required attribute for the ADD SU command.
PAGE 135
EMSFORFRMR Attribute Descriptions EMSFORFRMR displays an EMS message when a link reset occurs due to a Frame Reject (FRMR) condition on an X25AM line. The modifier accepts values in the range 0 to 200. By default, this feature is disabled. Configure this modifier with a non-zero value to enable generation of an EMS message during an FRMR condition.
PAGE 136
IDLETIMEOUT Attribute Descriptions IDLETIMEOUT is the network subscription parameter T3. IDLETIMEOUT specifies how long the link can remain without transmissions before transmitting a level-2 receive ready (RR) frame to find out if the other station is still capable of receiving and sending transmissions. This value must be in the range 0 through 5:27:67. Default: 15 seconds Range: 0 through 5:27:67 Objects: Lines INTERFACE specifies the electrical interface of the CLIP.
PAGE 137
L3MOD Attribute Descriptions L3MOD defines whether the module for the packet counters is 8 or 128. Default: 8 Range: 8 or 128 Objects: Lines L3WINDOW specifies the number of packets that can be outstanding without an acknowledgment from the network. L3WINDOW is the number of packets that can be sent before an acknowledging packet-receive count (Pr) is received. The range of values depends on L3MOD. If L3MOD is 8, the range for L3WINDOW is 1 through 7; otherwise, the range is 1 through 15.
PAGE 138
NEGOTIATE and NONEGOTIATE Attribute Descriptions NEGOTIATE and NONEGOTIATE specify the action to be taken when a call request with a value different from the default value for PKTSIZE, L3WINDOW, or THRUPUT has been received. If PKTSIZE, L3WINDOW, or THRUPUT has been defined as NEGOTIATE, the subdevice will accept a call containing a value that differs from the default value.
PAGE 139
PAGE6520BLKSIZE Attribute Descriptions NULLFILL OFF: Conversation Mode = EOT PAD SOH “C” ETX Page Mode = EOT PAD SOH “B” ETX Default: Off Range: On or Off Objects: Subdevices PAGE6520BLKSIZE specifies the terminal block size, in bytes, used in the ITI protocol. This modifier supports terminals that emulate the 6520 or 6530 terminal with a nonstandard block size in block mode. The range of values is 256 through 8000. The default value is 256 bytes.
PAGE 140
PORT Attribute Descriptions PORT specifies the logical port number to be used by the subdevice. This value must be in the range 0 through 9999. The default is zero (0). The range for the port is defined by the NETID. Default: Zero (0) Range: 0 through 9999 Objects: Subdevices PRICALL specifies whether you can make priority calls. This modifier is only applicable if NETID is DATAPAC. If off, outgoing calls do not include the DATAPAC national parameter for priority calls.
PAGE 141
PVC Attribute Descriptions Table 5-2. X25AM Protocols and Connectivity ITI Remote asynchronous terminals to NonStop S-series server using Packet Switched Data Network (PSDN) NAM Links Expand nodes with X.25 circuits PTP Other hosts, local area networks (LANs), or local asynchronous terminals using PSDN QLLC Link-level protocol used as an X.25 interface for attaching SNA devices to packet-switched data networks (SNAX) The protocol you select affects the DEVTTPE attribute for a subdevice.
PAGE 142
RECSIZE Attribute Descriptions RECSIZE specifies the maximum length of records that the SU receives or transmits. This value must be in the range 1 through 4095. This is a required attribute for the ADD SU command. Default: Not applicable Range: 1 through 4095 Objects: Subdevices REMOTEADDREXT is the address that the OSI network uses to identify the remote X25AM subsystem. REMOTEADDREXT is a string of hexadecimal digits (0 through F) up to 40 digits long.
PAGE 143
RETRIES Attribute Descriptions RETRIES specifies the number of frame-layer (level-2) retries (N2) executed (that is, commands sent without receiving a response) before a link is considered to be disconnected and is reset (all counters are set to 0). This value must be in the range 0 through 255. Default: 10 Range: 0 through 255 Objects: Lines REVERSECHG specifies whether an outgoing call request will request that the recipient pay the charges.
PAGE 144
SRCADDR Attribute Descriptions 7. RESET means to delete any existing RPOA attribute. No RPOA is assigned by default. Default: None. Range: DNIC codes range from 0 through 9999. Maximum number of DNIC values is 7. Objects: Lines and subdevices. SRCADDR specifies the X25AM network address for your system. The address is a string of decimal digits (0 through 9) up to 15 digits long. RESET deletes any existing SRCADDR assignment.
PAGE 145
T1TIMEOUT Attribute Descriptions T1TIMEOUT is the time interval to wait for a frame-level response before retrying the frame-level request. This value must be in the range 0 through 5:27:67 (5 minutes, 27 seconds, and 67 hundredths of a second). The ITU-T equivalent parameter is T1. Default: 3 seconds Range: 0 through 5:27:67 Objects: Lines THRESHOLD specifies the number of frames that X25AM transmits and receives before checking the line quality.
PAGE 146
TRANSITDELAY Attribute Descriptions Table 5-3. THRUPUT Values and Bits Per Second (page 2 of 2) 10 9600 11 19200 12 48000 13 Reserved according to the ITU-T X.25 Recommendation 14 Reserved according to the ITU-T X.25 Recommendation 15 Reserved according to the ITU-T X.25 Recommendation TRANSITDELAY specifies a transit delay time value in the range 0.00 through 1:05.53 (0 hundredths of a second through 1 minute, 5 seconds, and 53 hundredths of a second).
PAGE 147
The Call User Data (CUD) Attribute Attribute Descriptions The Call User Data (CUD) Attribute The Call User Data (CUD) attribute is present only in incoming calls and call requests. Figure 5-1.
PAGE 148
Default Values for the CUD Attribute Descriptions Default Values for the CUD The default values for the CUD are configured by the X25AM I/O process modifiers CALLUSERDATA and NOCALLUSERDATA. CALLUSERDATA is the default specification. If CALLUSERDATA is configured for the I/O process, the default for the CUD field is 4 zero bytes (0000) for both PTP and ITI protocol devices.
PAGE 149
Errors Attribute Descriptions The following example resets the value of the CUD for the SU $X25P1.#TERM: -> ALTER SU $x25p1.#TERM, CUD RESET The following example alters the value of the CUD for the SU $X25P1.#TERM2: -> ALTER SU $x25p1.#term2, CUD “0123456789abcdef” Hexadecimal characters beyond 9 can be either uppercase or lowercase letters. If the called network (REMOTENET) does not require a port number in the CUD, you can set or alter the CUD field of a subdevice with the ADD SU and ALTER SU commands.
PAGE 150
Errors Attribute Descriptions X25AM Configuration and Management Manual—523424-004 5- 22
PAGE 151
6 PTrace for the X25AM Subsystem This section describes how to analyze traces using PTrace. It provides the PTrace command syntax and fields of sample trace records.
PAGE 152
PTrace for the X25AM Subsystem Recording and Displaying Trace Data Figure 6-1. Recording and Displaying Trace Data Start the Trace with the SCF TRACE command. Collect trace data. Stop the trace with the SCF TRACE command. Display the trace file with PTrace. VST0601.vsd The following general description of the steps involved in recording and displaying trace data selects level-2, level-3, and level-4 trace information. 1. Start the trace with the SCF TRACE command.
PAGE 153
PTrace for the X25AM Subsystem Determining the Subsystem Determining the Subsystem PTrace uses the device type (61) and subtype (63) to determine the hardware interface for which it is formatting records. PTrace reads this information when it opens the trace file. PTrace Commands You use PTrace commands to format trace files generated by a subsystem. Some PTrace commands are common to all subsystems, and others are subsystem-specific.
PAGE 154
FILTER Command PTrace for the X25AM Subsystem Table 6-1. Summary of PTrace Commands for the X25AM Subsystem (page 2 of 2) OCTAL Displays numbers in octal notation. OUT Redirects the PTrace output. PAGESIZE Sets the terminal screen size for interactive mode. RECORD Displays record(s) selected by record number. RESET Resets session parameters to their default values and closes the trace file. SELECT Establishes selection criteria for displaying trace records.
PAGE 155
FILTER Command PTrace for the X25AM Subsystem clear packet expects a clear-confirmed packet in response, and a data packet expects a receive-ready (RR) packet to be returned within the configured level-3 window size value. FILTER [ [ [ [ [ [ [ [ FRAME [ frame-type ] [, frame-type ] ...] HELP LCN [ lcn-number ] [NO]INTERNALS [NO]SM PACKET [ packet-type ], [ packet-type] RESET SDN [ subdevice-number ] ] ] ] ] ] ] ] ] FRAME [ frame-type [ , frame-type ]...
PAGE 156
PTrace for the X25AM Subsystem SELECT Command PACKET [ packet-type [, packet-type ] ] ... packet-type is one of the following values: CALL CLEAR DATA DIAGNOSTIC INTERRUPT NOTRR REJ RESET RESTART RNR RR NOTRR displays all packets but RR packets. Omitting packet-type causes all types to be displayed. All packet types are displayed by default. RESET resets the filter options to their default values.
PAGE 157
TEXT Command PTrace for the X25AM Subsystem You can select specific records in the following two ways: • Through a keyword that is translated into an enumerated value or through a number that is saved as an enumerated value • Through a 32-bit selection mask Table 6-2 shows the keywords and mask bits for formatting trace files generated by X25AM. Table 6-2.
PAGE 158
PTrace for the X25AM Subsystem Creating a Sample Trace File Creating a Sample Trace File You can trace a line while it is running. In most cases, you probably do not need to stop a line to create a useful trace file. The example below selects only levels 3 and 4. If you do not wish to stop the line, you can use the following SCF command: -> TRACE $ldev, TO filename, SELECT (L3,L4) If you have a particular problem, you will probably want to recreate it and make a sample trace file.
PAGE 159
PTrace for the X25AM Subsystem FIND Command FIND Command The FIND command can be very useful for reading X25AM traces. In general, you look for problems from the higher levels to the lower levels. The three major components of the X25AM environment are: • • • Level 4 (the application level, with programmatic calls such as READ and WRITE) Level 3 (the packet level) Level 2 (the bit-synchronous frames and modem signals) If the program is receiving spurious error 140s, take a trace of the problem.
PAGE 160
PTrace for the X25AM Subsystem What to Look for in Level 2 probably have a level-2 problem. You should look for the following states in the level-2 frames from PTrace: 1. On startup, you should see one side sending SABM and the other responding with UA, which synchronizes level 2. If you do not see the UA response, there is a level-2 problem or a modem problem. Check to see whether the SABM is being retried every timeout interval.
PAGE 161
Level-2 Trace Example PTrace for the X25AM Subsystem Level-2 Trace Example This example trace comes from a file produced by the following SCF TRACE command: -> TRACE LINE $ldev, TO filename, SELECT CLIPDI, CLIPDO Ptrace Log File: $DATA2.MELVIN.CLWN2LOG ?record 1,9999 06/11/99 15:08:07.283222 >000.000000 #1 User Trace Record 000: 5439 3331 3743 010: 5E58 3235 4C41 020: 0209 CSS LAPB In A/C($0121) DCE 000: 0121 RR Seq 1 Len 42 Time 15:07:33.
PAGE 162
Level-2 Trace Analysis PTrace for the X25AM Subsystem 06/11/99 15:09:34.619807 >028.729647 #5 CLIP Trace Blk CSS LAPB In A/C($0121) DCE 000: 0121 Time 15:08:54.95 P/F=0 Seq 47 N(R)=1 Len 13 RR CSS LAPB Out A/C($0321) DTE 000: 0321 Time 15:09:09.95 P/F=0 Seq 54 N(R)=1 Len 13 RR CSS LAPB In A/C($0121) DCE 000: 0121 Time 15:09:09.95 P/F=0 Seq 55 N(R)=1 Len 13 RR 06/11/99 15:09:34.668334 >000.
PAGE 163
Tracing Level 3 PTrace for the X25AM Subsystem If the DTE does not receive a frame within the level-2 timeout value, the DTE sends an RR command frame with the P bit set, demanding that the remote side respond. If the DTE receives nothing within the level-2 retries value, level 2 initiates error recovery. Tracing Level 3 The packet level follows the X.25 protocol as required by the ITU-T.
PAGE 164
What to Look for in Level 3 PTrace for the X25AM Subsystem Table 6-4. Packet Types (page 2 of 2) Receive Ready* RRR0 0001 Receive Not Ready* RRR0 0101 Reject* RRR0 1001 * RRR = N(R) acknowledges all data packets received -1. SSS = N(S), number of data packets sent. M = More bit (more data follows).
PAGE 165
Level-3 Trace Example PTrace for the X25AM Subsystem An RR packet is used to acknowledge received data packets. However, the X25AM level 3 waits to receive the number given by the configured L3 window size of incoming packets before it sends an RR packet to acknowledge them all. If the L3 window is 2, an RR packet is sent after every second packet is received. Level-3 Trace Example The following trace was taken with all trace record types selected: Ptrace Log File: $DATA2.PATRICIA.
PAGE 166
PTrace for the X25AM Subsystem Sample Trace Reading of Calls Being Cleared 001 Logical channel number (LCN) 0B Packet type 2 Number of digits in source address 0 Number of digits in destination address The first 2 bytes of the packet describe the LCN 001, bits 4:16. The first 2 bytes distinguish the circuit from the many that can be multiplexed on a common level-2 link layer. Bits <0:3> are packet control identifiers, such as the D bit (delivery packet) and the Q bit (PAD packet identifier).
PAGE 167
PTrace for the X25AM Subsystem Sample Trace Reading of Calls Being Cleared 1. X25AM is operating as a DCE and is rejecting the incoming calls with a clear packet. To discover why, take a trace by issuing the following SCF commands: -> ASSUME LINE $DATA2 Assumed object: LINE \SLUGO.$DATA2 -> TRACE,TO TRX,SELECT (L3,L4) The application runs, then the remote side attempts a call (either a terminal, PAD, or remote process). Stop the trace: -> TRACE,STOP 2.
PAGE 168
PTrace for the X25AM Subsystem Sample Trace Reading of Calls Being Cleared 06/11/99 15:23:46.513989 >000.002920 #101 L4 WRITELINK SDN #001/%001 FEOK RSP 3C44 P1-6 %000000 %000035 %000000 %000012 %000012 %000000 06/11/99 15:23:46.514919 >000.000930 #102 SDN #001/%001 LEN #0013 GFI(0001) MOD8 Data M=0 P(S)=0 P(R)=0 000: 1001 0031 3233 3435 3637 3839 30 L3 Pkt Out LGN/LCN $001 06/11/99 15:24:35.503425 >048.
PAGE 169
Sample Trace Reading of Calls Being Cleared PTrace for the X25AM Subsystem • • • The caller requested that the receiver accept the charges (through the facility field) but the subdevice was configured for reverse charges. The caller requested negotiate packet size but the subdevice was configured NONEGOTIATE packet size. You are using the QLLC protocol and did not specify a protocol ID of 3 in the Call User Data (CUD) field.
PAGE 170
Sample Trace Reading of Calls Being Cleared PTrace for the X25AM Subsystem 5. Check the port number of the subdevice to make sure it has been correctly configured: -> info su $x25p1.#ptp, detail X25AM Detail Info SU *AcceptChg.... OFF *PVC.......... *Port......... 3 *RexmitTimeout 0:20.00 *CUG.......... *CUGType...... BASIC *DestAddr..... *Negotiate.... Associateline *LocalAddrExt. *RemoteAddrExt *CUD.......... *RPOA.......... *Bpadparms.... *Cpadparms.... $X25P1.#PTP *DevType.... *Parity.....
PAGE 171
PTrace for the X25AM Subsystem The Application Level Run the application again. When it has finished processing, stop the trace: -> TRACE,STOP 8. Check the trace to make sure that it worked (run PTrace from SCF). >PTRACE FROM TRX3 ?SELECT L3; RECORD ALL Trace of: \SLUGO.$DATA2, Type (61,0). Ptrace Data File: \SLUGO.$SIGN.EDX25.TRX3 Trace started: 02/12/99 14:50:16.624765 First trace entry: 02/12/99 14:50:16.624765 Last trace entry: 02/12/99 14:50:40.
PAGE 172
PTrace for the X25AM Subsystem The Application Level packets and level-4 application calls selected. Each operation results in a specific packet(s) being sent to the network. :PTRACE ?FROM TRL4 ?SELECT (L3,L4); FILTER NOSM; FILTER NOINTERNALS; FILTER LCN 2 Ptrace Select mask: 0001 1000 0000 0000 0000 0000 0000 0000 ?RECORD ALL Trace of: \SLUGO.$X251, Type (61,0). Ptrace Data File: $SIGN.EDX25LAB.TRL4 Trace started: 01/28/90 09:24:48.164532 First trace entry: 01/28/90 09:24:48.
PAGE 173
PTrace for the X25AM Subsystem The Application Level L4^LCB^In Record 20D Seq 20 Type 70 Time 09:25:26.487673 SDN #002/%002 Open LCB 6698 P1-6 %140012 %000026 %040000 %001000 %000000 %177777 L4 WRITELINK Record 21D Seq 21 Type 71 Time 09:25:26.487673 SDN #002/%002 FEOK RSP 6698 P1-6 %000000 %000026 %007400 %001020 %000000 %177777 L4^LCB^In Record 24D Seq 24 Type 70 Time 09:25:26.
PAGE 174
PTrace for the X25AM Subsystem Application Trace Analysis L4^LCB^In Record 99D Seq 99 Type 70 Time 09:25:29.487673 SDN #002/%002SetmodeLCB 6B10 P1-6 %147407 %000026 %000001 %000000 %000020 %000024 L4 WRITELINK Record 100D Seq 100 Type 71 Time 09:25:29.487673 SDN #002/%002 FEOK RSP 6B10 P1-6 %000000 %000026 %000001 %000000 %000000 %000024 L4^LCB^In Record 103D Seq 103 Type 70 Time 09:25:29.
PAGE 175
PTrace for the X25AM Subsystem Terminals and PAD Parameters 2. At record 74, it sent the saved Q packet because the SETMODE posted at record 66. This Q packet is different from the initial one sent at record 40 because it sends parameter (2,0), which should turn off echo mode at the PAD (the default value of 2,1 means echo on).
PAGE 176
PTrace for the X25AM Subsystem Terminals and PAD Parameters If calls are being accepted but the terminals do not work quite right, a PAD parameter problem may exist. Once the Q packets have been sent and the PAD has configured itself to those parameters, the terminal can communicate with the X25AM-ITI subdevice as if the subdevice were an actual terminal process. To analyze the Q packet, look at the following display, which is record 40 from the previous trace.
PAGE 177
Common X.25 Terms PTrace for the X25AM Subsystem Common X.25 Terms The X.25 standard as defined by the ITU-T allows various configuration modifiers to be set by the PDNs. The vendor often requests these values at subscription time. The X25AM subsystem has descriptive names for these values. You can set any of the configuration parameters in Table 6-5 by using the SCF ADD DEVICE or ALTER DEVICE command to the WAN subsystem and specifying the corresponding X25AM I/O process modifier.
PAGE 178
Common X.25 Terms PTrace for the X25AM Subsystem Table 6-5. X.25 Configuration Parameters and X25AM I/O Process Modifiers (page 2 of 2) Device Modifier/ Line Attribute Name Operation X25AM Parameter Probable Value Meaning Restart T20 180 seconds Timer set at DTE issue of restart request. Txx Call request T21 200 seconds Timer set at DTE issue of call request. Txx Reset T22 180 seconds Timer set at DTE issue of reset request.
PAGE 179
A SCF Command Summary This appendix summarizes the syntax of the commands described in Section 4, SCF Commands for the X25AM Subsystem. ABORT [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] ADD [ / OUT file-spec / ] [ SU su-name ] [ , LIKE object-name ] [ , attribute-spec ]... ALLOWOPENS [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] ALTER [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , LIKE object-name ] [ , attribute-spec ]...
PAGE 180
SCF Command Summary STATUS [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , DETAIL ] [ , SUB [ subtype ] ] STOP [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] STOPOPENS [ / OUT file-spec / ] [ LINE line-name | SU su-name ] [ , SUB [ subtype ] ] SWITCH [ / OUT file-spec / ] [ PROCESS process-name | LINE line-name ] , PATH { A | B } TRACE [ / OUT file-spec / ] [ LINE line-name ] { , STOP [ , BACKUP ] { [ , BACKUP [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE s
PAGE 181
B X25AM I/O Process Modifiers and Related SCF Line Attributes Some X25AM I/O process modifiers that you specify with the SCF ADD DEVICE or ALTER DEVICE commands to the WAN subsystem can also be specified with SCF ALTER LINE command to the X25AM subsystem. For more information about using this SCF command, see ALTER Command on page 4-17. Table B-1 lists the X25AM I/O process modifiers that you can specify as an SCF line attribute with the SCF ALTER LINE command.
PAGE 182
X25AM I/O Process Modifiers and Related SCF Line Attributes Table B-1. X25AM I/O Process Modifiers and Line Attributes (page 2 of 2) X25AM I/O Process Modifier Line Attribute NOOUTGOINGCALLS CALLS NOSENDCALLINGADDR CALLINGADDR OUTGOINGCALLS CALLS PAGE6520BLKSIZE PAGE6520BLKSIZE PROGRAM PROGRAM RS232 INTERFACE RS422 INTERFACE SENDCALLINGADDR CALLINGADDR TWOWAYCALLS CALLS V25 INTERFACE Table B-2.
PAGE 183
X25AM I/O Process Modifiers and Related SCF Line Attributes Table B-2.
PAGE 184
X25AM I/O Process Modifiers and Related SCF Line Attributes X25AM Configuration and Management Manual—523424-004 B- 4
PAGE 185
C X25AM Error Messages This appendix describes network-related operator console error messages and common file-system error messages. Cause and recovery information for each error message is included. This appendix only includes messages issued by the X25AM subsystem. The user can receive, through SCF, error messages generated by the file system, SCP, and so on.
PAGE 186
00501 X25AM Error Messages 00501 X25AM E00501 INTERNAL ERROR: Case value out of range Cause. An invalid case value was generated with no associated case label. Effect. Command is not executed. Recovery. Contact your HP representative immediately. 00503 X25AM E00503 A Required Attribute (RECSIZE, DEVTYPE, PROTOCOL) is missing Cause. One or more of the required attributes (RECSIZE, DEVTYPE, and PROTOCOL) is missing. Effect. Command is not executed. Recovery.
PAGE 187
00507 X25AM Error Messages 00507 X25AM E00507 Invalid Value: attribute-name for Object name Cause. The value entered for the named attribute on the specified object name is not valid. Effect. Command is not executed. Recovery. Check the valid values for this attribute, and reissue the command with a valid value. 00509 X25AM E00509 Too many values given Cause. The number of values given to this attribute exceeds the limit. Effect. Command is not executed. Recovery.
PAGE 188
00512 X25AM Error Messages 00512 X25AM E00512 Object name object-name is not supported Cause. The named object is not supported by the X25AM subsystem. Effect. Command is not executed. Recovery. Choose a valid object name, and reissue the command. 00513 X25AM E00513 The values of attribute-name and attribute-name are inconsistent Cause. The combination of values of the named attributes is inconsistent. Effect. Command is not executed. Recovery. Check for the proper values, and reissue the command.
PAGE 189
00518 X25AM Error Messages 00518 X25AM E00518 L3WINDOW is not altered because there are SU(s) on PVC(s) Cause. L3WINDOW cannot be altered with the SCF ALTER LINE command if the line has SUs configured with PVCs. Effect. Command is not executed. Recovery. Use SCF to DELETE any SUs that are configured with PVCs, then reissue the ALTER LINE L3WINDOW command. 20084 X25AM 20084 Quoted string can be no more than 32 characters long Cause. The hexadecimal string exceeds the maximum length. Effect.
PAGE 190
20084 X25AM Error Messages X25AM Configuration and Management Manual—523424-004 C- 6
PAGE 191
D Using the NETID Modifier X25AM provides the NETID/REMOTENET feature to specify a set of network characteristics. Historically, these sets were given network-specific names such as DATAPAC, because they pertained to only one network. More recently, however, more general names are used because each set can now pertain to more than one network. A list of set names follows.
PAGE 192
Using the NETID Modifier Port Numbering (Subaddressing) Port Numbering (Subaddressing) • • • • For NETID and REMOTENET, port numbers are often referred to as subaddresses. NETID determines the location for the called (in this case the local DTE) DTE’s port number in an incoming call: the port number can be either part of the called address or part of the call user data. When a port number cannot be found or calculated, it is assumed to be zero.
PAGE 193
Detail-Set Specifications Using the NETID Modifier Detail-Set Specifications Table D-1 on page D-3 through Table D-16 on page D-8 provide a description of special port numbers, default PAD parameter values, and network-dependent facility requirements for each set. Table D-1. X25 Detail-Set Specification Call Addressing: SU PORT NUMBER is 0 to 99 digits; leading zeros are included. Incoming Call: Called address is LINE SRCADDR + SU PORT NUMBER. A 0- to 2-digit port number is expected.
PAGE 194
Detail-Set Specifications Using the NETID Modifier Table D-4. X25UD (User Data) Call Addressing: SU PORT NUMBER is 0 to 99. Incoming Call: Called address is not used by X25AM. The port number is the fifth byte of call user data (%H41 = port 1,%H42 = port 2, and so on). Call Request: Called address is SU DESTADDR minus its last two digits. The last two digits plus%H40 are placed in the fifth byte of the call user data field (01 =%H41, 02 =%H42, and so on). Calling address is LINE SRCADDR.
PAGE 195
Detail-Set Specifications Using the NETID Modifier Table D-7. DATAPAC Call Addressing: SU PORT NUMBER is from 0 to 99. Incoming Call: Uses the fifth byte of the call user data as the called port number. Port number 0 is the default. Call Request: If both LINE NETID and SU REMOTENET are DATAPAC, then called address is SU DESTADDR. If only SU REMOTNET is DATAPAC, then called address is SU DESTADDR minus the last two digits.
PAGE 196
Detail-Set Specifications Using the NETID Modifier Table D-10. DDXP (Like X25UD) Call Addressing: SU PORT NUMBER is from 0 to 99. Incoming Call: Called address is LINE SRCADDR + SU PORT NUMBER. The port number is the fifth byte of call user data. The default is 0. Call Request: Called address is SU DESTADDR minus its last digits. The last two digits plus %H40 are placed in the fifth byte of the call user data field (01 = %H41, 02 = %H42, and so on). Calling address is LINE SRCADDR.
PAGE 197
Detail-Set Specifications Using the NETID Modifier Table D-13. TRANSPAC (Like X25SA) Call Addressing: SU PORT NUMBER is 0 to 4 digits. Leading zeros are deleted. Incoming Call: Called address is LINE SRCADDR + SU PORT NUMBER. A 0- to 4-digit PORT NUMBER is expected. Call Request: Called address is SU DESTADDR. Calling address is LINE SRCADDR + SU PORT NUMBER. PAD Profile: Standard default. Clearing: Uses Invitation To Clear. Linefeed Echo: X25AM I/O process performs.
PAGE 198
PAD Profiles Using the NETID Modifier Table D-16. UNINET (Like X25UD) Call Addressing: SU PORT NUMBER is from 0 to 99. Incoming Call: Called address is LINE SRCADDR + SU PORT NUMBER. The port number is the fifth byte of call user data. The default is 0. Call Request: Called address is SU DESTADDR minus its last digits. The last two digits plus %H40 are placed in the fifth byte of the call user data field (01 = %H41, 02 = %H42, and so on). Calling address is LINE SRCADDR.
PAGE 199
Standard PAD Profiles Using the NETID Modifier Table D-17. Standard PAD Profiles for Conversational Mode (page 2 of 2) X.3 Parameter Internal Parameter Code,Value Actual Parameter Code,Value Discard output 8,0 8,0 Line folding 10,0 10,0 Line feed insertion after receipt of carriage return from terminal 13,4 13,4 (*) 6510 Terminal in Block Mode Table D-18. Standard PAD Profiles for 6510 Terminal in Block Mode X.
PAGE 200
DATANET PAD Profiles Using the NETID Modifier 6520/6530 Terminal in Block Mode Table D-19. Standard PAD Profiles for 6520/6530 Terminal in Block Mode X.
PAGE 201
DATAPAC PAD Profiles Using the NETID Modifier DATAPAC PAD Profiles Table D-20, Table D-21 on page D-12, and Table D-22 on page D-13 provide descriptions of the three DATAPAC PAD profiles. Conversational Mode Table D-20. DATAPAC PAD Profiles for Conversational Mode X.
PAGE 202
DATAPAC PAD Profiles Using the NETID Modifier 6510 Terminal in Block Mode Table D-21. DATAPAC PAD Profiles for 6510 Terminal in Block Mode X.
PAGE 203
DATAPAC PAD Profiles Using the NETID Modifier 6520/6530 Terminal in Block Mode Table D-22. DATAPAC PAD Profiles for 6520/6530 Terminal in Block Mode X.
PAGE 204
DATEX-P PAD Profiles Using the NETID Modifier DATEX-P PAD Profiles Table D-23, Table D-24 on page D-15, and Table D-25 on page D-16 provide descriptions of the DATEX-P PAD profiles. Conversational Mode Table D-23. DATEX-P PAD Profiles for Conversational Mode X.
PAGE 205
DATEX-P PAD Profiles Using the NETID Modifier 6510 Terminal in Block Mode Table D-24. DATEX-P PAD Profiles for 6510 Terminal in Block Mode X.
PAGE 206
DDN PAD Profiles Using the NETID Modifier 6520/6530 Terminal in Block Mode Table D-25. DATEX-P PAD Profiles for 6520/6530 Terminal in Block Mode X.
PAGE 207
TELENET PAD Profiles Using the NETID Modifier TELENET PAD Profiles Table D-26, Table D-27, and Table D-28 on page D-18 provide descriptions of the TELENET PAD profiles. Conversational Mode Table D-26. TELENET PAD Profiles for Conversational Mode X.
PAGE 208
TELENET PAD Profiles Using the NETID Modifier 6520/6530 Terminal in Block Mode Table D-28. TELENET PAD Profiles for 6520/6530 Terminal in Block Mode X.
PAGE 209
TRANSPAC PAD Profiles Using the NETID Modifier TRANSPAC PAD Profiles Table D-29, Table D-30, and Table D-31 on page D-20 provide descriptions of the TRANSPAC PAD profiles. Conversational Mode Table D-29. TRANSPAC PAD Profiles for Conversational Mode X.
PAGE 210
TWINET PAD Profiles Using the NETID Modifier 6520/6530 Terminal in Block Mode Table D-31. TRANSPAC PAD Profiles for 6520/6530 Terminal Block Mode X.
PAGE 211
Using the NETID Modifier PAD Parameter Examples PAD Parameter Examples Following are narrative examples of the contents of a TELENET PAD profile, a DATAPAC PAD profile, and a standard PAD profile. TELENET Example Suppose you are using the TELENET network. The terminal is conversation-mode only. The subdevice must be configured for REMOTENET TELENET, with a subdevice type and subtype of 6,0.
PAGE 212
Using the NETID Modifier X25AM Configuration and Management Manual—523424-004 D -22 Standard Example
PAGE 213
E Moving to G-Series or H-Series RVUs Note. There X25AM subsystem on G-series and H-series RVUs are the same. There are no G-series to H-series migratory considerations for this subsystem. This appendix describes the differences between the X25AM subsystem on NonStop S-series servers and the X25AM software on systems running D-series RVUs.
PAGE 214
SYSGEN-to-SCF Considerations Moving to G-Series or H-Series RVUs SYSGEN-to-SCF Considerations This subsection explains how information that is configured in SYSGEN CONFTEXT paragraphs on systems running D-series RVUs is defined on systems running G-series RVUs. CONFTEXT Paragraph Information Table E-1 lists the CONFTEXT paragraphs that are relevant to X25AM configuration and how the information in each paragraph is defined on systems running G-series RVUs. Table E-1.
PAGE 215
Moving to G-Series or H-Series RVUs COUP-to-SCF Considerations COUP-to-SCF Considerations The COUP interface is no longer supported for G-series RVUs; the COUP functions are replaced by SCF. Although most COUP commands have a direct SCF equivalent, the method of configuration on systems running G-series RVUs is very different from systems running D-series RVUs.
PAGE 216
Moving to G-Series or H-Series RVUs Managing an X25AM Network X25AM Configuration and Management Manual—523424-004 E- 4
PAGE 217
F Diagnostic and Cause Codes This section documents all the ITU-T Recommended Diagnostic Codes for X.25 and the Cause Codes for ISO 8208. ISO/IEC 8208 Table F-1.
PAGE 218
ITU-T Recommended Diagnostic Codes Diagnostic and Cause Codes ITU-T Recommended Diagnostic Codes Note. Not all diagnostic codes need apply to a specific network, but those used are as coded in the tables. A given diagnostic need not apply to all packet types (that is, reset indication, clear indication, restart indication, registration confirmation and diagnostic packets).
PAGE 219
ITU-T Recommended Diagnostic Codes Diagnostic and Cause Codes Table F-4.
PAGE 220
ITU-T Recommended Diagnostic Codes Diagnostic and Cause Codes Table F-6.
PAGE 221
SNAX-Over-X.25 (SOX) Configuration Codes Diagnostic and Cause Codes Table F-8.
PAGE 222
Diagnostic and Cause Codes SNAX-Over-X.
PAGE 223
G Configuration Files for the X25AM Subsystem You can use SCF interactively by entering individual commands at a terminal. You can also use SCF programmatically to create commonly used sequences of commands (Obey files). Before adding the X25AM profile object, all the components of the ServerNet wide area network (SWAN) concentrator and the WAN subsystem must be running. If you need more information on configuring and managing the WAN subsystem, see the WAN Subsystem Configuration and Management Manual.
PAGE 224
Configuration Files for the X25AM Subsystem Adding X25AM I/O Processes Adding X25AM I/O Processes The following SCF command file adds two X25AM I/O processes to the third CLIP of the SWAN concentrator S01. The I/O process for line 0, $X25P1, is configured for DTE operations (the default) and uses the default profile. The I/O process for line 1 is configured for DCE operations and uses the modified profile. ADD DEVICE $ZZWAN.#X25P1, & CPU 0, & ALTCPU 1, & PROFILE PX250061, & IOPOBJECT $SYSTEM.SYS00.
PAGE 225
Starting X25AM Lines Configuration Files for the X25AM Subsystem The STATUS commands result in the following displays: WAN Manager STATUS DEVICE for DEVICE State :......... STARTED \TOYS2.$ZZWAN.#X25P1 LDEV number..... 156 PPIN............ 0 ,297 BPIN............ 1 WAN Manager STATUS DEVICE for DEVICE State :......... STARTED LDEV number..... 146 PPIN............ 0 ,277 ,270 \TOYS2.$ZZWAN.#X25S1 BPIN............
PAGE 226
Adding Subdevices to an X25AM Line Configuration Files for the X25AM Subsystem Adding Subdevices to an X25AM Line After starting an X25AM line, you can configure its associated subdevices. Subdevices are started automatically when you add them. The following SCF command file adds two subdevices to the $X25P1 line. ADD SU $x25p1.#term, PROTOCOL ITI, DEVTYPE (6,0), & RECSIZE 80, RPOA (125, 300, 5000) STATUS SU $x25p1.#term INFO SU $x25p1.#term, DETAIL ADD SU $x25p1.
PAGE 227
Adding Subdevices to an X25AM Line Configuration Files for the X25AM Subsystem The STATUS and INFO commands for $X25P1.#TERM1 result in the following displays: X25AM STATUS Name $X25P1.#TERM1 SU State STARTED X25AM Detail Info SU DevType 9,0 Recsize 80 SUnum 3 Port 0 LCNnum $X25P1.#TERM1 *AcceptChg.... OFF *DevType.... *PVC.......... *Parity..... *Port......... 0 *Protocol... *RexmitTimeout 0:20.00 *ReverseChg. *CUG.......... *Nullfill... *CUGType...... BASIC *BCUG....... *DestAddr.....
PAGE 228
Configuration Files for the X25AM Subsystem Adding Subdevices to an X25AM Line X25AM Configuration and Management Manual—523424-004 G- 6
PAGE 229
Glossary This glossary includes a selection of terms used in this manual. ABEND. Abnormal termination of a process. ABM. Asynchronous Balanced Mode. A mode of communications within the ADCCP protocol whereby two combined stations communicate on a point-to-point link. Either or both stations can issue commands to set up or dissolve the link. During data transmission, the stations function as peers. This mode is also used by the HDLC protocol. access method.
PAGE 230
call connected packet Glossary call connected packet. Packet that the network sends to a caller in response to receiving a call accepted packet from a remote entity. call redirection. Optional network facility that allows the network to pass a call to another subscriber number. call request packet. Packet that a caller sends to a network addressed to a remote entity to initiate a call. call setup.
PAGE 231
communications line interface processor (CLIP) Glossary 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. The CLIP stores and implements specific communications protocols. communications subsystem.
PAGE 232
EBCDIC Glossary EBCDIC. Extended binary-coded decimal interchange code. Standard method of coding data, consisting of 8 bits of data with no parity bit for each character. fast select. Optional network facility allowing call setup packets to contain a call user data (CUD) field of up to 128 octets. flow control. Mechanism by which the recipient of incoming data notifies the sender to stop or start transmitting data depending on the state (full or empty) of the recipient’s incoming data buffer. frame.
PAGE 233
IOP Glossary IOP. I/O process. System process that controls input and output, usually to and from a device. ISO. See International Organization for Standardization (ISO). ITI protocol. Interactive terminal Interface protocol. For X25AM, it is used by the X25AM process when an application exchanges data with a remote terminal connected to an X.25 packet-switching network with a PAD. ITU.
PAGE 234
MIB Glossary MIB. See management information base (MIB). modem. Modulator Demodulator. Hardware that converts digital data to an analog signal for transmission over a telephone channel, or that converts an analog signal into digital data. modem eliminator. Device that allows data communications equipment to be connected without modems and telephone lines. modulo8. A repeating packet-numbering sequence. Packets are numbered 0 through 7. modulo128. A repeating packet-numbering sequence.
PAGE 235
packet assembler/disassembler (PAD) Glossary packet assembler/disassembler (PAD). Device that enables an asynchronous terminal or personal computer to access a PSDN. It assembles or disassembles communications packets. The device serves as an interface between a terminal or computer and a packetizing network. It can be hardware or software. packet level. X.25 protocol description for packet formats and transmission of data across the link between the network and the computers, terminals, or other devices.
PAGE 236
process Glossary divided into a primary substation and a secondary substation. See also secondary station. process. When a program on a NonStop Kernel operating system is being executed, it is called a process. program. Set of coded instructions residing on a disk. protocol. Set of rules for assembling, sending, and receiving data. PSDN. See packet-switching data network (PSDN). PTP protocol. Process-to-process protocol.
PAGE 237
SCF Glossary SCF. Subsystem Control Facility. A subsystem used for issuing configuration and information requests between the user and some communications subsystems. secondary station. In an SDLC or ADCCP-NRM configuration, the station that is contacted by the primary station and is controlled by the primary message in a message exchange. The secondary station cannot initiate a communication. This type of configuration is not used for X.25 connections. However, the combined station used for X.
PAGE 238
switched virtual circuit (SVC) Glossary switched virtual circuit (SVC). Association between two entities for packet exchange. Set up by a call, it is terminated after each call. A call requires setup before data transfer and clearing after data transfer. SVC. See switched virtual circuit (SVC). system disk. Disk that contains the operating system image. TSM.
PAGE 239
Glossary wide area network (WAN) subsystem wide area network (WAN) subsystem. The Subsystem Control Facility (SCF) subsystem for configuration and management of wide area network (WAN) objects on NonStop S-series servers. window size. Maximum number of packets or frames that can be transmitted without being acknowledged. X3PAD. Program provided with X25AM that supports communications from a local terminal to remote entities in the network by means of an X25AM process. X.21. Standard related to X.25.
PAGE 240
$ZZWAN Glossary X25AM Configuration and Management Manual—523424-004 Glossary -12
PAGE 241
Index A B ABORT command definition 4-12 object-spec 4-12 syntax 4-12, A-1 ACCEPTCHG attribute 5-1 ADD command definition 4-13 SU attribute-spec 4-14 syntax 4-13, A-1 Adding a profile G-1 Adding an I/O process G-2 ALLOWOPENS command definition 4-16 syntax 4-16, A-1 ALTER command 4-17 using with line attributes B-1 ALTER LINE command attribute-spec 4-19 ALTER SU command attribute-spec 4-20 Application level in PTrace 6-21 Application process, communicating with X25AM 2-1 ASCII modifier 3-15 ASSOCIATELINE at
PAGE 242
D Index Commands ABORT 4-12 object-spec 4-12 syntax 4-12, A-1 ADD 4-13 attribute-spec 4-14 syntax 4-13, A-1 ALLOWOPENS syntax 4-16, A-1 ALTER 4-17 ALTER LINE attribute-spec 4-19 ALTER SU attribute-spec 4-20 DELETE 4-24 syntax 4-24, A-1 DISCONNECT object-spec 4-25 syntax 4-25, A-1 INFO syntax 4-26, A-1 NAMES 4-30 nonsensitive 4-11 overview 4-2 PRIMARY syntax 4-32, A-1 sensitive 4-11 START syntax 4-33, A-1 STATS definition 4-35 syntax 4-35, A-1 STATUS 4-42 object-spec 4-43 syntax 4-43, A-2 STOP object-spec
PAGE 243
E Index DCE modifier 3-18 DCECLOCK modifier 3-17, 3-19 DDN D-5 attributes for 5-5 PAD profiles D-16 DDNPREC attribute 5-5 DDNSERVICE attribute 5-5 DDXP D-6 PAD profiles D-16 DELETE command 4-24 syntax 4-24, A-1 DESTADDR attribute 5-5 Destinations of output for SCF 4-3 DETAIL option, overview of 4-4 Device type for X25AM 6-3 DEVTYPE attribute 3-4, 4-9, 5-6 DISABLEPVCOUTOFORDER modifier 3-20 Disabling, enabling CLIP clock 5-3 DISCONNECT command object-spec 4-25 syntax 4-25, A-1 Disconnect command 3-24 Drive
PAGE 244
K Index K N Keyword, in SCF commands 4-4 N2 subscription parameter 3-24, 5-15 NAMES command display format 4-31 object-spec 4-30 NEGOTIATE attribute and SVC subdevices 4-22 definition 5-10 NEGOTIATE PACKETSIZE attribute 3-29 NETID DATANET D-4 DATAPAC D-5 DATEX-P D-5, D-6 DDN D-5 DDXP D-6 definition D-1 port numbering D-2 PSS D-6 special network requirements D-2 TELENET D-6 TRANSPAC D-7 TWINET D-7 TYMNET D-7 UNINET D-8 use with lines D-1 X25 D-3 X25NP D-3 X25SA D-3 X25UD D-4 X25XA D-4 NETID attribute 5-
PAGE 245
O Index Nonsensitive commands 4-11 NonStop Kernel, compatible versions of 4-4 NOOUTGOINGCALLS modifier 3-32 NOREPORTDIRECT modifier 3-28 NOSENDCALLINGADDRESS modifier 3-31 NOSTRIPPARITY modifier 3-31 NULLFILL attribute 5-10 O Object attributes 4-9 names 4-6 types 4-6 Object file for SCF 4-3 Object specifications ABORT command 4-12 DISCONNECT command 4-25 STATUS command 4-43 STOP command A-2 STOPOPENS command A-2 VERSION command A-2 Objects 4-6 LINE 4-6 PROCESS 4-6 SU 4-6 Object-name, assigning 4-7 object
PAGE 246
R Index PTrace (continued) commands supported by X25AM 6-3 determining the subsystem 6-3 displaying trace data 6-2 FILTER command 6-4 FILTER command considerations 6-6 FIND command 6-9 formatting trace files 6-3 generating a trace file 6-1 HDLC–LAPB protocol 6-9 ITI mode 6-25 level 2 6-9 level 3 6-14 packet type 6-13 reading X25AM traces 6-8 recording trace data 6-2 SABM 6-9 searching for packet types 6-4 SELECT command 6-6 select mask 6-9 terminals and PAD parameters 6-25 TEXT command 6-7 tracing level 3
PAGE 247
T Index SCF attributes, defined 4-9 SCF NEGOTIATE PACKETSIZE 3-29 SENDCALLINGADDRESS modifier 3-31 Sensitive commands 4-11 Service attribute for DDN 5-5 Session, SCF, parameters for 4-2 Sources of input for SCF 4-3 Special network requirements and NETID D-2 SRCADDR attribute 5-16 Standard PAD profiles D-8 START command object-spec 4-33 syntax 4-33, A-1 Starting a line command file G-3 Starting an I/O process command file G-2 Starting SCF 4-3 Statistics buffer pool information 4-41 confirmation packet 4-38
PAGE 248
U Index Timeout 3-18, 3-24 Timeout values 3-32 TRACE command definition 4-51 syntax 4-51, A-2 Trace data displaying with PTrace 6-2 generating with PTrace 6-2 Trace file creating sample 6-8 generating with PTrace 6-1 TRANSITDELAY attribute 5-18 Transmission line quality 4-36 TRANSPAC D-7 PAD profiles D-19 TWINET D-7 TWOWAYCALLS modifier 3-32 TYMNET D-7 PAD profiles D-20 U UNINET D-8 PAD profiles D-20 UNSOLF modifier 3-34 unsolicited F response 3-34 User facilities 2-5 X X25 D-3 X25AM 2-2 components 2-1