X25AM Configuration and Management Manual

X25AM Configuration and Management Manual
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
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
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. Configuration Quick Start
Task Summary 1-1
Assumptions 1-1
Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information
Add the X25AM Profile 1-4
Add the X25AM I/O Processes 1-5
Start the X25AM I/O Processes and Lines 1-6
Add X25AM Subdevices 1-7
2. Overview of the X25AM Subsystem
Introduction to the X25AM Subsystem 2-1
Subsystem Components 2-1
X25AM I/O Process 2-1
X25AM Line 2-2
X25AM Subdevice 2-2
Packet Assembler/Disassembler (PAD) 2-4
Subscription Parameters 2-4
3. Configuring an X25AM Subsystem
SCF Interface to the WAN and X25AM Subsystems 3-1
WAN Subsystem Interface to the X25AM Subsystem 3-2
Hewlett-Packard Company—523424-004
i
1-2
Contents
3. Configuring an X25AM Subsystem (continued)
3. Configuring an X25AM Subsystem (continued)
Configuration Tasks 3-3
Task 1: Review Configuration Prerequisites 3-3
Task 2: Familiarize Yourself with Subsystems, Commands, and Attributes
Task 3: Add the X25AM Profile 3-5
Task 4: Determine the SWAN Configuration Information 3-6
Task 5: Add an X25AM I/O Process 3-7
Task 6: Start an X25AM I/O Process 3-8
Task 7: Start an X25AM Line 3-9
Task 8: Add X25AM Subdevices 3-10
Altering an X25AM I/O Process 3-11
List of X25AM I/O Process Modifiers 3-12
X25AM Modifier Dictionary 3-15
Numeric Range Validation 3-15
4. SCF Commands for the X25AM Subsystem
Subsystem Control Facility 4-1
Subsystem Control Point (SCP) 4-2
SCF Commands 4-2
How SCF Works 4-3
Running SCF 4-3
Input Sources and Output Destinations 4-3
General Command Format 4-4
SCF Online Help 4-4
Version Compatibility 4-4
SCF Interface to the X25AM Subsystem 4-5
X25AM Subsystem Objects 4-6
Object Types and Object Names 4-6
Object States 4-8
Object Attributes 4-9
Frequently Performed Tasks on X25AM Objects 4-9
Commands Supported by the X25AM Subsystem 4-10
Sensitive and Nonsensitive Commands 4-11
ABORT Command 4-12
Command Syntax for the ABORT Command 4-12
Examples of the ABORT Command 4-12
Considerations for the ABORT Command 4-13
X25AM Configuration and Management Manual—523424-004
ii
3-4
Contents
4. SCF Commands for the X25AM
Subsystem (continued)
4. SCF Commands for the X25AM Subsystem (continued)
ADD Command 4-13
Command Syntax for the ADD Command 4-13
Examples of the ADD Command 4-15
Considerations for the ADD Command 4-15
ALLOWOPENS Command 4-16
Command Syntax for the ALLOWOPENS Command 4-16
Examples of the ALLOWOPENS Command 4-17
Considerations for the ALLOWOPENS Command 4-17
ALTER Command 4-17
Command Syntax for the ALTER Command 4-18
Attribute-Spec for the ALTER LINE Command 4-19
Attribute-Spec for the ALTER SU Command 4-20
Examples of the ALTER Command 4-20
Considerations for the ALTER Command 4-22
DELETE Command 4-24
Command Syntax for the DELETE Command 4-24
Examples of the DELETE Command 4-24
Considerations for the DELETE Command 4-25
DISCONNECT Command 4-25
Command Syntax for the DISCONNECT Command 4-25
Examples of the DISCONNECT Command 4-25
Consideration for the DISCONNECT Command 4-25
INFO Command 4-26
Command Syntax for the INFO Command 4-26
Display for the INFO LINE Command 4-26
Display for the INFO SU Command 4-28
Examples of the INFO Command 4-29
Considerations for the INFO Command 4-30
NAMES Command 4-30
Command Syntax for the NAMES Command 4-30
Object-Spec for the NAMES Command 4-31
Examples of the NAMES Command 4-31
Considerations for the NAMES Command 4-31
PRIMARY Command 4-32
Command Syntax for the PRIMARY Command 4-32
Examples of the PRIMARY Command 4-32
Considerations for the PRIMARY Command 4-33
X25AM Configuration and Management Manual—523424-004
iii
Contents
4. SCF Commands for the X25AM
Subsystem (continued)
4. SCF Commands for the X25AM Subsystem (continued)
START Command 4-33
Command Syntax for the START Command 4-33
Examples of the START Command 4-34
Considerations for the START Command 4-34
STATS Command 4-35
Command Syntax for the STATS Command 4-35
Display for the STATS LINE Command 4-36
Display for the STATS SU Command 4-41
Examples of the STATS Command 4-42
Considerations for the STATS Command 4-42
STATUS Command 4-42
Command Syntax for the STATUS Command 4-43
Display for the STATUS LINE Command 4-43
Display for the STATUS SU Command 4-46
Examples of the STATUS Command 4-47
Considerations for the STATUS Command 4-47
STOP Command 4-48
Command Syntax for the STOP Command 4-48
Examples of the STOP Command 4-48
Considerations for the STOP Command 4-48
STOPOPENS Command 4-49
Command Syntax for the STOPOPENS Command 4-49
Examples of the STOPOPENS Command 4-49
Considerations for the STOPOPENS Command 4-50
SWITCH Command 4-50
Command Syntax for the SWITCH Command 4-50
Examples of the SWITCH Command 4-51
Considerations for the SWITCH Command 4-51
TRACE Command 4-51
Command Syntax for the TRACE Command 4-51
Examples of the TRACE Command 4-54
How to Use the TRACE Command to Troubleshoot X25AM Problems
VERSION Command 4-55
Command Syntax for the VERSION Command 4-55
Examples of the VERSION Command 4-56
X25AM Configuration and Management Manual—523424-004
iv
4-54
5. Attribute Descriptions
Contents
5. Attribute Descriptions
ACCEPTCHG 5-1
ASSOCIATELINE 5-1
BCUG 5-2
BPADPARMS 5-2
CALLINGADDR 5-2
CALLS 5-3
CHARACTERSET 5-3
CLOCKMODE 5-3
CLOCKSPEED CLOCKnnnn 5-3
CPADPARMS 5-3
CUD 5-4
CUG 5-4
CUGTYPE 5-4
DDNPREC 5-5
DDNSERVICE 5-5
DESTADDR 5-5
DEVTYPE 5-6
DSRTIMEOUT 5-6
EMSFORFRMR 5-7
EXTFORMAT and NOEXTFORMAT 5-7
FRAMEMODE 5-7
IDLETIMEOUT 5-8
INTERFACE 5-8
L3IMMEDIATERR 5-8
L3MOD 5-9
L3WINDOW 5-9
LOCALADDREXT 5-9
LOCALADDREXTTYPE 5-9
NEGOTIATE and NONEGOTIATE 5-10
NETID 5-10
NULLFILL 5-10
PAGE6520BLKSIZE 5-11
PARITY 5-11
PARITYCHK 5-11
PORT 5-12
PRICALL 5-12
PROGRAM 5-12
X25AM Configuration and Management Manual—523424-004
v
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. PTrace for the X25AM Subsystem
Recording and Displaying Trace Data
Determining the Subsystem 6-3
PTrace Commands 6-3
FILTER Command 6-4
SELECT Command 6-6
TEXT Command 6-7
Creating a Sample Trace File 6-8
Reading X25AM Traces 6-8
FIND Command 6-9
Tracing Level 2 6-9
What to Look for in Level 2 6-9
Level-2 Trace Example 6-11
Level-2 Trace Analysis 6-12
6-1
X25AM Configuration and Management Manual—523424-004
vi
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. X25AM Error Messages
Message Descriptions
00500 C-1
00501 C-2
00503 C-2
00504 C-2
00505 C-2
00507 C-3
00509 C-3
00510 C-3
00511 C-3
00512 C-4
00513 C-4
00516 C-4
00517 C-4
00518 C-5
20084 C-5
C-1
D. Using the NETID Modifier
Port Numbering (Subaddressing) D-2
Default PAD Profiles D-2
Special Network Requirements D-2
Detail-Set Specifications D-3
X25AM Configuration and Management Manual—523424-004
vii
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. Moving to G-Series or H-Series RVUs
WAN Subsystem E-1
SYSGEN-to-SCF Considerations E-2
CONFTEXT Paragraph Information E-2
Profile for G-Series X25AM Subsystem E-2
COUP-to-SCF Considerations E-3
Managing an X25AM Network E-3
F. Diagnostic and Cause Codes
ISO/IEC 8208 F-1
ITU-T Recommended Diagnostic Codes F-2
SNAX-Over-X.25 (SOX) Configuration Codes
F-5
G. Configuration Files for the X25AM Subsystem
Adding an X25AM Profile G-1
Adding X25AM I/O Processes G-2
Starting X25AM I/O Processes G-2
Starting X25AM Lines G-3
Adding Subdevices to an X25AM Line
G-4
X25AM Configuration and Management Manual—523424-004
viii
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.
X25AM Subsystem Components 2-3
SCF Interface to WAN and X25AM Subsystems 3-2
Adding an X25AM I/O Process 3-8
Starting an X25AM I/O Process 3-8
The START Command Issued to a LINE Object Controlled by an
X25AM I/O Process That Has Been Started 3-9
Making Persistent Changes to an X25AM I/O Process 3-12
DTE and DCE Functions 3-19
SCF Interface to WAN and X25AM Subsystems 4-2
Making Dynamic Changes to an X25AM Line 4-5
X25AM Object-Type Hierarchy 4-7
Call User Data (CUD) 5-19
Recording and Displaying Trace Data 6-2
X.25 Packet 6-13
Tables
Table i.
Table 1-1.
Table 2-1.
Table 3-1.
Table 3-2.
Table 3-3.
Table 3-4.
Table 3-5.
Table 4-1.
Table 4-2.
Table 4-3.
Table 4-4.
Table 4-5.
Table 4-6.
Table 4-7.
Table 4-8.
Summary of Contents xvii
Worksheet for Adding an X25AM I/O Process 1-5
Subscription Parameters Supported by the X25AM Subsystem 2-5
List of X25AM Modifiers and Defaults 3-12
Throughput Classes and Bits Per Second 3-26
Call Enabling and Call Disabling 3-32
Timeout and Retry Counter Default Values 3-33
X25AM I/O Process Modifiers for Timers 3-33
X25AM Object Specifications 4-8
Configuring and Managing X25AM Objects With SCF Commands 4-9
SCF Commands Supported by X25AM Subsystem 4-10
SCF Line Attributes and X25AM I/O Process Modifiers 4-23
Subdevice Types and Subtypes 4-28
Subdevice Types and Subtypes 4-47
Select-Spec for a LINE object 4-53
User-Request Parameters 4-55
X25AM Configuration and Management Manual—523424-004
ix
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.
DEVTYPE for an SU 5-6
X25AM Protocols and Connectivity 5-13
THRUPUT Values and Bits Per Second 5-17
Summary of PTrace Commands for the X25AM Subsystem 6-3
PTrace SELECT Command Keywords for the X25AM Subsystem 6-7
PTrace Select Masks 6-9
Packet Types 6-13
X.25 Configuration Parameters and X25AM I/O Process
Modifiers 6-27
X25AM I/O Process Modifiers and Line Attributes B-1
X25AM I/O Process Modifiers Without Line Attribute Equivalent B-2
Sources and Documentation of X25AM Error Messages C-1
X25 Detail-Set Specification D-3
X25NP (No Ports) D-3
X25SA (Subaddress) D-3
X25UD (User Data) D-4
X25XA (Extended Address) D-4
DATANET (Like X25XA) D-4
DATAPAC D-5
DATEX-P D-5
DDN (Like X25) D-5
DDXP (Like X25UD) D-6
PSS (Like X.25) D-6
TELENET (Like X.25) D-6
TRANSPAC (Like X25SA) D-7
TWINET (Like X25NP) D-7
TYMNET (Like X.25) D-7
UNINET (Like X25UD) D-8
Standard PAD Profiles for Conversational Mode D-8
Standard PAD Profiles for 6510 Terminal in Block Mode D-9
Standard PAD Profiles for 6520/6530 Terminal in Block Mode D-10
DATAPAC PAD Profiles for Conversational Mode D-11
DATAPAC PAD Profiles for 6510 Terminal in Block Mode D-12
DATAPAC PAD Profiles for 6520/6530 Terminal in Block Mode D-13
DATEX-P PAD Profiles for Conversational Mode D-14
DATEX-P PAD Profiles for 6510 Terminal in Block Mode D-15
DATEX-P PAD Profiles for 6520/6530 Terminal in Block Mode D-16
TELENET PAD Profiles for Conversational Mode D-17
X25AM Configuration and Management Manual—523424-004
x
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.
TELENET PAD Profiles for 6510 Terminal in Block Mode D-17
TELENET PAD Profiles for 6520/6530 Terminal in Block Mode D-18
TRANSPAC PAD Profiles for Conversational Mode D-19
TRANSPAC PAD Profiles for 6510 Terminal in Block Mode D-19
TRANSPAC PAD Profiles for 6520/6530 Terminal Block Mode D-20
Defining CONFTEXT Paragraph Information on G-Series Systems E-2
Coding of the Diagnostic Code Field F-1
No Additional Information Problems F-2
Packet Type Invalid Problems F-2
Packet Not Allowed Problems F-3
Time Expired F-3
Call Setup, Call Clearing, or Registration Problems F-4
Miscellaneous Diagnostic Codes F-4
International Problems F-5
Clear and Reset Diagnostic Codes for SOX Configuration F-5
X25AM Configuration and Management Manual—523424-004
xi
Contents
X25AM Configuration and Management Manual—523424-004
xii
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.03 and all
subsequent H-series RVUs until otherwise indicated in a new edition.
Part Number
Published
523424-004
July 2005
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
New and Changed Information
The following changes have been made for this edition:
•
•
•
This publication has been updated to reflect new product names, and product
names in graphic representations are consistent with the current product interface.
Updated About This Manual for Integrity NonStop NS-series and H-series
terminology and new manual titles.
Updated Section 1, Configuration Quick Start for Integrity NonStop NS-series and
SWAN 2 concentrator changes.
X25AM Configuration and Management Manual—523424-004
xiii
What’s New in This Manual
•
•
New and Changed Information
Updated Section 2, Overview of the X25AM Subsystem for NonStop NS-series
changes.
Updated the following Sections or Appendices for NonStop NS-series changes,
H-series terminology or new manual titles, Gigabit Ethernet 4-port ServerNet
adapter (G4SA), or SWAN 2 concentrator changes:
Section 3
°
°
°
°
°
°
°
°
Configuring an X25AM Subsystem on page 3-1
WAN Subsystem Interface to the X25AM Subsystem on page 3-2
Task 1: Review Configuration Prerequisites on page 3-3
Task 3: Add the X25AM Profile on page 3-5
Task 4: Determine the SWAN Configuration Information on page 3-6
Task 5: Add an X25AM I/O Process on page 3-7
PROGRAM on page 3-14
PROGRAM download-filename on page 3-30
Section 4
°
°
°
°
°
°
°
°
°
SCF Commands for the X25AM Subsystem on page 4-1
Subsystem Control Facility on page 4-1
Subsystem Control Point (SCP) on page 4-2
SCF Commands on page 4-2
Running SCF on page 4-3
Input Sources and Output Destinations on page 4-3
General Command Format on page 4-4
Object-Type Hierarchy on page 4-6
Commands Supported by the X25AM Subsystem on page 4-10
Note. Command syntax changes are only related to introducing a new manual (SCF
Reference Manual for H-Series RVUs).
°
°
°
°
°
Command Syntax for the ABORT Command on page 4-12
Command Syntax for the ADD Command on page 4-13
Command Syntax for the ALLOWOPENS Command on page 4-16
Command Syntax for the ALLOWOPENS Command on page 4-16
Command Syntax for the DELETE Command on page 4-24
X25AM Configuration and Management Manual—523424-004
xiv
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 STOPOPENS Command on page 4-49
Command Syntax for the SWITCH Command on page 4-50
Command Syntax for the TRACE Command on page 4-51
Command Syntax for the TRACE Command on page 4-51
Section 5
°
°
CHARACTERSET on page 5-3
PROGRAM on page 5-12
Appendices C, E, and G and the Glossary
°
°
°
°
X25AM Error Messages on page C-1
Moving to G-Series or H-Series RVUs on page E-1
Adding an X25AM Profile on page G-1
Glossary
X25AM Configuration and Management Manual—523424-004
xv
What’s New in This Manual
New and Changed Information
X25AM Configuration and Management Manual—523424-004
xvi
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.
A description of the SCF interactive interface to the X25AM subsystem, including
detailed reference information for each of the SCF commands to the X25AM
subsystem.
Who Should Use This Manual
This manual is intended primarily for system managers responsible for installing and
managing X25AM. It may also be used for reference by application programmers using
X25AM lines for data communications.
It is assumed that you are familiar with the G-series and H-series system-configuration
process and have access to the WAN Subsystem Configuration and Management
Manual and installation documentation.
What’s in This Manual
Table i. Summary of Contents (page 1 of 2)
Section
Title
This section . . .
1
Configuration Quick Start
Provides the basic information required to
enable you to quickly define and start the
X25AM subsystem.
2
Overview of the X25AM
Subsystem
Provides an overview of X25AM subsystem.
3
Configuring an X25AM Subsystem
Describes the X25AM configuration and the
I/O process modifiers.
4
SCF Commands for the X25AM
Subsystem
Describes the SCF commands to the X25AM
subsystem, sensitive and nonsensitive
commands, and detailed information about
each SCF command.
5
Attribute Descriptions
Describes the SCF line and subdevice
attributes for the X25AM subsystem.
6
PTrace for the X25AM Subsystem
Describes the X25AM Ptrace utility.
X25AM Configuration and Management Manual—523424-004
xvii
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.
D
Using the NETID Modifier
Discusses the use of the line modifier
NETID.
E
Moving to G-Series or H-Series
RVUs
Provides an overview of how the X25AM
subsystem has been adapted to work with
the Integrity NonStop NS-series or
NonStop S-series server.
F
Diagnostic and Cause Codes
Lists all ITU-T recommended diagnostic
codes for the X25AM subsystem.
G
Configuration Files for the X25AM
Subsystem
Shows example configuration files for the
X25AM subsystem.
This manual also contains a glossary of technical terms and abbreviations used
throughout the text.
Where to Get Other Information
Depending on the tasks you are performing, you might need the following manuals or
help systems:
•
•
•
•
•
•
•
•
•
•
•
•
Expand Configuration and Management Manual
NonStop NS-Series Planning and Configuration Guide
NonStop S-Series Planning and Configuration Guide
OSM User’s Guide
PTrace Reference Manual
SCF Reference Manual for G-Series RVUs
System Generation Manual for G-Series RVUs
SCF Reference Manual for the Kernel Subsystem
TSM Online User Guide
WAN Subsystem Configuration and Management Manual
WAN Wizard Pro User’s Guide
X25AM Programming Manual
X25AM Configuration and Management Manual—523424-004
xviii
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. For example:
file-name
[ ] Brackets. Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
INT[ERRUPTS]
A group of items enclosed in brackets is a list from which you can choose one item or
none. The items in the list may be arranged either vertically, with aligned brackets on
each side of the list, or horizontally, enclosed in a pair of brackets and separated by
vertical lines. For example:
LIGHTS [ ON
]
[ OFF
]
[ SMOOTH [ num ] ]
K [ X | D ] address-1
{ } Braces. A group of items enclosed in braces is a list from which you are required to
choose one item. The items in the list may be arranged either vertically, with aligned
braces on each side of the list, or horizontally, enclosed in a pair of braces and
separated by vertical lines. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
INSPECT { OFF | ON | SAVEABEND }
X25AM Configuration and Management Manual—523424-004
xix
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. Parentheses, commas, semicolons, and other symbols not previously
described must be entered as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must enter as shown. For example:
"[" repetition-constant-list "]"
Item Spacing. Spaces shown between items are required unless one of the items is a
punctuation symbol such as a parenthesis or a comma. For example:
CALL STEPMOM ( process-id ) ;
If there is no space between two items, spaces are not permitted. In the following
example, there are no spaces permitted between the period and any other items:
$process-name.#su-name
Line Spacing. If the syntax of a command is too long to fit on a single line, each
continuation line is indented three spaces and is separated from the preceding line by
a blank line. This spacing distinguishes items in a continuation line from items in a
vertical list of selections. For example:
ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]...
Change Bar Notation
Change bars are used to indicate substantive differences between this edition of the
manual and the preceding edition. Change bars are vertical rules placed in the right
margin of changed portions of text, figures, tables, examples, and so on. Change bars
highlight new or revised information. For example:
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
X25AM Configuration and Management Manual—523424-004
xx
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. If you want to change
your X25AM configuration, or if you want to complete the initial configuration without
using the default configuration values, refer to the appropriate sections of this manual.
Task Summary
1. Log On to the NonStop Server and Obtain SWAN/SWAN 2 Information on
page 1-2
2. Add the X25AM Profile on page 1-4
3. Add the X25AM I/O Processes on page 1-5
4. Start the X25AM I/O Processes and Lines on page 1-6
5. Add X25AM Subdevices on page 1-7
Assumptions
At the beginning of the procedure, the Integrity NonStop NS-series or
NonStop S-series server is in the following state:
•
•
•
•
•
•
•
The default software configuration is as shipped by manufacturing.
The initial TSM or OSM configuration is complete. Note that TSM is not supported
on Integrity NonStop NS-series servers.
The ServerNet LAN Systems Access (SLSA) subsystem has been defined and
started. Also, a LAN adapter (for example, a Gigabit Ethernet 4-port ServerNet
adapter (G4SA) has been installed and started). Note that the G4SA can only be
installed in an I/O Adapter Module (IOAM) enclosure. For more information, see
the Gigabit Ethernet 4-Port Adapter Installation and Support Guide.
A NonStop TCP/IP process has been defined and started. Note that
NonStop Parallel Library TCP/IP is not supported on Integrity NonStop NS-series
servers.
The WAN manager process ($ZZWAN) has been defined and started.
The WAN processes CONMGR process is defined and started. The WANBOOT,
TFTP, and SNMP are automatically started.
The SWAN/SWAN 2 concentrator has been installed, defined and started and has
an available WAN line.
X25AM Configuration and Management Manual—523424-004
1 -1
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.21 converter cable.
Log On to the NonStop Server and Obtain
SWAN/SWAN 2 Information
1. Log on to the NonStop NS-series or NonStop S-series server using the Super ID,
and enter the correct password at the Password: prompt.
> LOGON super.super
Password:
2. At the TACL prompt on the NonStop NS-series or NonStop S-series server, start
SCF.
> SCF
3. Determine the names of the SWAN/SWAN 2 concentrators on the system.
-> NAMES ADAPTER $ZZWAN.#*
ADAPTER
$ZZWAN.#S02
$ZZWAN.#S01
4. Determine where an available WAN line exists on one of the SWAN/SWAN 2
concentrators (for example, S01). The STATUS SERVER command lists the fields
you need when issuing the ADD DEVICE command; in the following example only
the display for the CLIP with available lines is shown.
-> STATUS SERVER $ZZWAN.#s01.*
WAN Manager STATUS SERVER for CLIP
State :......... STARTED
\TOYS2.$ZZWAN.#S01.3
Path A..........: CONFIGURED
Path B..........: CONFIGURED
Number of lines. 2
Line............ 0
Line............ 1
: FREE
: FREE
a. Record the name of the SWAN/SWAN 2 concentrator
(\system.$zzwan.#conc-name) in the adapter field in Table 1-1,
Worksheet for Adding an X25AM I/O Process, on page 1-5.
X25AM Configuration and Management Manual—523424-004
1 -2
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. Determine the processors in which the SWAN/SWAN 2 concentrator is configured.
a. Issue the INFO ADAPTER command. The INFO ADAPTER command lists the
name of the two TCP/IP processes in which the SWAN/SWAN 2 concentrator
is configured. For example:
-> INFO ADAPTER $ZZWAN.#s01
WAN MANAGER Detailed Info Adapter \TOYS2.$ZZWAN.#S01
*TrackId.......... X017JJ
*TCPIP Name.......$ZBPA
*ALTTCPIP Name.... $ZBPB
Concentrator Type. SYNC
KERNELCODE........ \TOYS2.$SYSTEM.CSS00.C7953P00
*SNMPCODE......... \TOYS2.$SYSTEM.CSS00.C7849P00
*HOSTIP Address... 192.168.005.081
*ALTHOSTIP Address 192.168.007.081
SUBNETMASK........ %HFFFFFF00
ALTSUBNETMASK..... %HFFFFFF00
b. Issue the STATUS PROCESS command for each TCP/IP process (in
boldface) to determine the primary CPU each process is running in. For
example:
-> STATUS PROCESS $xpba
TCPIP Status PROCESS \TOYS2.$ZBPA
Status: STARTED
PPID............ ( 0,106)
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................... ( 1,132)
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.0
Fport
*
*
*
*
*
*
*
*
*
X25AM Configuration and Management Manual—523424-004
1 -3
SendQ
0
0
0
0
0
0
0
0
0
RecvQ
0
0
0
0
0
0
0
0
0
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.0
Fport
*
*
*
*
*
*
*
*
*
SendQ
0
0
0
0
0
0
0
0
0
RecvQ
0
0
0
0
0
0
0
0
0
c. Record the PPID for the TCPIP Name and ALTTCPIP Name fields in the
STATUS PROCESS display (in boldface) in the cpu and altcpu fields in
Table 1-1, Worksheet for Adding an X25AM I/O Process, on page 1-5.
Repeat Steps 3 through 5 for each X25AM I/O process you need to configure.
Add the X25AM Profile
A profile defines modifiers, default values, and ranges of values for the X25AM
subsystem. The X25AM subsystem supports only one profile named PX250061. This
type 832 file is located in the sysnn subvolume. The file is part of the X25AM product.
The file contains all the attributes for X25AM I/O processes and provides the function
of SYSGEN macros for the NonStop NS-series or NonStop S-series server.
If you have already added this profile, you can skip this task.
1. Issue the following SCF command to see the profiles that have been added:
-> NAMES PROFILE $ZZWAN.*
The output of the NAMES command lists the profiles that have been added. If the
X25AM profile does not exist, you need to add it.
2. The program file must use the current sysnn. To obtain the current sysnn, type
the following:
-> STATUS *, USER
3. Add the X25AM profile using the following SCF command:
-> ADD PROFILE $ZZWAN.#PX250061, FILE $SYSTEM.SYSnn.PX250061
For more information about adding and modifying an X25AM profile, see Task 3: Add
the X25AM Profile on page 3-5.
X25AM Configuration and Management Manual—523424-004
1 -4
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. Worksheet for Adding an X25AM I/O Process
-> ADD DEVICE $ZZWAN.#__________, PROFILE PX250061, &
-> IOPOBJECT $SYSTEM.SYS00.X25OBJ, &
-> PROGRAM $SYSTEM.CSS00.C1096P00, &
-> TYPE (61,63), &
-> RECSIZE 32767, &
-> ADAPTER __________, &
(See Step 4a)
-> CLIP _____________, &
(See Step 4b)
-> LINE _____________, &
(See Step 4c)
-> PATH _____________, &
(See Step 4d)
-> CPU ______________, &
(See Step 5c)
-> ALTCPU ____________ &
(See Step 5c)
For a SWAN concentrator (T3880) replace C1096P00 with C0051P00 if you are implementing an X.21 interface
with an X.21 converter cable. For a SWAN 2 concentrator, replace C1096P00 with C0051Q00.
Example 1-1 shows the syntax used to create the X25AM I/O process named $X25P1.
X25AM Configuration and Management Manual—523424-004
1 -5
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.C1096P00, &
-> TYPE (61,63), &
-> RECSIZE 32767, &
-> ADAPTER ___S01______, &
(See Step 4a)
-> CLIP ______3______, &
(See Step 4b)
-> LINE ______1______, &
(See Step 4c)
-> PATH ______A______, &
(See Step 4d)
-> CPU _______0___, &
(See Step 5c)
-> ALTCPU ____1______ &
(See Step 5c)
Replace C1096P00 with C0051P00 if you are implementing an X.21 interface with an X.21 converter cable.
Repeat Add the X25AM I/O Processes on page 1-5 for each X25AM line you need to
configure.
For additional information about ADD DEVICE modifiers and values, see the WAN
Subsystem Configuration and Management Manual. For information about ADD
DEVICE modifiers that are specific to X25AM I/O processes, see the X25AM Modifier
Dictionary on page 3-15.
Start the X25AM I/O Processes and Lines
1. After adding the X25AM profile and I/O processes, issue the SCF START
command to the WAN subsystem to start each I/O process. For example:
-> START DEVICE $ZZWAN.#x25p1
Issue the STATUS DEVICE command to make sure the device has been started.
2. After the I/O process has been started, you start the line that it controls using the
SCF START LINE command to the X25AM subsystem. For example:
-> START LINE $x25p1
Issue the STATUS LINE command to make sure the line has been started.
Repeat Steps 1 and 2 for each X25AM I/O process you have added.
For information about the SCF START DEVICE command, see the WAN Subsystem
Configuration and Management Manual. For information about the START LINE
command, see START Command on page 4-33.
X25AM Configuration and Management Manual—523424-004
1 -6
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.#term, PROTOCOL ITI, DEVTYPE (6,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
The subdevice is started automatically.
Repeat the ADD SU command for each subdevice to be added to each line.
For information about the SCF ADD SU command and other SCF commands for
managing X25AM subdevices, see Section 4, SCF Commands for the X25AM
Subsystem.
X25AM Configuration and Management Manual—523424-004
1 -7
Configuration Quick Start
X25AM Configuration and Management Manual—523424-004
1 -8
Add X25AM Subdevices
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.
The X25AM subsystem works with any public or private PSDN that supports the 1980
or 1984 ITU-T X.25 Recommendations. X25AM has been certified for use with many
public networks around the world, including all those operated by European countries
that require certification of access software.
The X25AM subsystem supports Link Access Procedure-Balanced (LAPB), the
Data-Link Layer procedure generally used for X.25 connections. LAPB allows a
point-to-point connection between two stations, where each station can establish and
disconnect the link and initiate data transfers.
The X25AM subsystem can be configured for either data circuit-terminating equipment
(DCE) or data terminal equipment (DTE) operation, allowing
NonStop Integrity NS-series or NonStop S-series servers to be used as either end of a
switched or leased-line X.25 connection.
Subsystem Components
The X25AM subsystem consists of the following components (Figure 2-1 on page 2-3).
X25AM I/O Process
An X25AM I/O process is a program, running on an Integrity NonStop NS-series or
NonStop S-series server, that controls an X25AM line and all its subdevices. One
X25AM I/O process is required for each X25AM line; multiple lines require multiple
X25AM I/O processes.
Applications communicate with remote entities in a network by means of an X25AM I/O
process through file-system procedures. Other processes (including other HP
products) can also communicate with an X25AM I/O process for different types of
connectivity.
Multiple applications or other processes can communicate with a single X25AM I/O
process. For example, an Expand process, a SNAX process, and multiple user
X25AM Configuration and Management Manual—523424-004
2 -1
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. When you configure an X25AM I/O process,
you can specify basic line characteristics (subscription parameters), such as circuits,
timers, retries, frame size, default window size, default packet size, default throughput
class, and extended packet sequencing capability.
Detailed information about configuring X25AM I/O processes is provided throughout
this manual.
X25AM Line
X25AM lines can theoretically be configured for up to 510 circuits (510 subdevices). An
X25AM line, capable of supporting X.25 communications, is a physical entity attached
to a SWAN/SWAN 2 concentrator. A line is configured and controlled by its X25AM I/O
process.
When you configure an X25AM I/O process for a line you specify the number of circuits
for the line; the number of circuits determines the number of subdevices you can add
to each line. Each circuit can be used for call activity and is associated with a single
subdevice.
You use SCF commands to the X25AM subsystem to start, stop, alter, and monitor
X25AM lines.
X25AM Subdevice
An X25AM subdevice is a logical entity related to an X25AM line. A logical subdevice
can represent a physical object (a terminal or computer), or it can represent some
other software (an application or other process) residing in a computer system. Each
application or physical object communicating over an X25AM line must have a
subdevice defined for it. A subdevice provides a way for an application to communicate
over a switched virtual circuit (SVC) or a permanent virtual circuit (PVC) to another
application.
X25AM subdevices are added to the X25AM line(s), and their characteristics are
defined by using SCF commands to the X25AM subsystem. The maximum number of
subdevices that can be added to a line is determined by the maximum number of
circuits (CIRCUITS modifier) specified for the X25AM I/O process. The maximum
number of circuits allowable depends upon your network subscription.
An X25AM line can be configured for up to 510 circuits (510 subdevices). The number
of configurable subdevices depends on the modifiers PACKETSIZE and L3WINDOW.
For higher packet sizes (more than 256 bytes), the number of subdevices which can be
configured may be less than 510.
X25AM Configuration and Management Manual—523424-004
2 -2
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.
For detailed information about how to use SCF for the X25AM lines and subdevices,
see Section 4, SCF Commands for the X25AM Subsystem. For detailed information
about the SPI implementation for X25AM, see the X25AM Programming Manual.
Figure 2-1 illustrates the physical and logical components of the X25AM subsystem.
Figure 2-1. X25AM Subsystem Components
NonStop NS-series or NonStop S-series system
Application
Process
(X25AM
Subdevices)
Circuits
X25AM
Lines
X25AM
I/O Process
Application
Process
•
•
•
Application
Process
•
•
•
Application
Process
X.25
PSDN
SWAN
Concentrator
X25AM
I/O Process
Application
Process
•
•
•
Application
Process
•
•
•
VST0201.vsd
X25AM Configuration and Management Manual—523424-004
2 -3
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. Some input sources that can be used to communicate
through X3PAD are:
•
•
•
65xx terminals
HP emulator terminals
TELSERV-connected Network Virtual terminals
X3PAD passes data between the user terminal and the network. Functions performed
by X3PAD can be controlled by commands issued from the terminal or by PAD
messages issued from the network. X3PAD can also transfer data from NonStop
server files to the network or from the network to NonStop server files.
The X3PAD program is based on the ITU-T Recommendation X.3, which describes the
functions of a PAD and the parameters associated with the asynchronous terminals
accessing the PAD.
X3PAD also supports the procedures of Recommendation X.29, which describes the
communications between a PAD and a packet-mode DTE using a PSDN. For detailed
information about the default PAD parameter values for X3PAD, and the commands
you can use to change them, see the X25AM Programming Manual.
Subscription Parameters
The X.25 ITU-T Recommendation provides various configuration options that affect
how your connection to the network operates. The value or range of values for these
options depends on the network. These options are called subscription parameters or
user facilities. A few of the subscription parameters affect all calls.
Some of these subscription parameters are specified by X25AM I/O process modifiers
(see Table 2-1 on page 2-5) using SCF commands to the WAN subsystem; such
modifiers are described in Section 3, Configuring an X25AM Subsystem.
Most subscription parameters are requested on a per-call basis; such parameters can
be specified using:
•
SCF commands with line attributes to the X25AM subsystem
For information about these parameters, see Section 4, SCF Commands for the
X25AM Subsystem and Section 5, Attribute Descriptions.
•
File-system procedures
For information on subscription parameters that can be requested for each call,
see the X25AM Programming Manual
X25AM Configuration and Management Manual—523424-004
2 -4
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. Subscription Parameters Supported by the X25AM Subsystem
Subscription
Parameter
I/O Process
Modifier
Default
Setting for
Modifier
K
L2WINDOW
4
--
Number of
information
frames that can
be sent without an
acknowledgement
N2
L2RETRIES
10
RETRIES
Number of SABM
commands that
can be sent
without an
acknowledgement
T1
L2TIMEOUT
300
(3 seconds)
T1TIMEOUT
Time interval
spent waiting for a
response or ACK
before retrying a
request
T3
L2IDLETIMEOU
T
1500
(15 seconds)
IDLETIMEOUT
A timeout interval
R10-R13
Rxx
1
--
DCE retry
counters
R20-R23
Rxx
1
--
DTE retry
counters
T10, T12, T13
Txx
60 seconds
--
DCE timers
T11
Txx
180 seconds
--
DCE timer
T20, T22, T23
Txx
180 seconds
--
DTE timers
T21
Txx
200 seconds
--
DTE timer
Line Attribute
Description
X25AM Configuration and Management Manual—523424-004
2 -5
Overview of the X25AM Subsystem
Subscription Parameters
X25AM Configuration and Management Manual—523424-004
2 -6
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. WAN Wizard Pro is a graphical user
interface (GUI) that guides you step-by-step through the configuration process. To access
WAN Wizard Pro, from the desktop of your NonStop server system console select:
Start>Programs>HP WAN Wizard Pro>WAN Wizard Pro
•
•
The System Generation (SYSGEN) program is not used for NonStop NS-series or
NonStop S-series servers. All configuring and monitoring of the X25AM subsystem
is done using Subsystem Control Facility (SCF) commands to the WAN and
X25AM subsystems.
°
You use SCF commands to the WAN subsystem to define and start one or
more X25AM I/O processes. The WAN subsystem must be started before you
attempt to configure X25AM I/O processes.
°
You use SCF commands to the X25AM subsystem to define subdevices and to
start, stop, and monitor lines and subdevices. The SCF commands to the
X25AM subsystem are described in Section 4, SCF Commands for the X25AM
Subsystem, and Section 5, Attribute Descriptions.
The HP Nonstop operating system registered Type and Subtype for the X25AM
Subsystem are 61 and 63, respectively.
For information about configuring a SWAN concentrator or starting the WAN
subsystem, see the WAN Subsystem Configuration and Management Manual.
SCF Interface to the WAN and X25AM
Subsystems
SCF provides an operator interface to the Subsystem Control Point (SCP). The default
SCP process is known to the system as $ZNET. SCP, in turn, interfaces to the X25AM
subsystem’s operations and services as well as to the WAN subsystem. Figure 3-1 on
page 3-2 shows the SCF interface to the X25AM subsystem.
X25AM Configuration and Management Manual—523424-004
3 -1
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.vsd
WAN Subsystem Interface to the X25AM
Subsystem
For systems running G-series and H-series RVUs, the X25AM I/O processes (one for
each X25AM line) are configured and started by using SCF commands to the WAN
subsystem; the WAN subsystem provides the functions that COUP and SYSGEN
provided on the systems running on D-series RVUs. Specifically, the WAN subsystem
allows you to:
•
•
•
Configure X25AM I/O processes with the modifiers that affect their operation
Start, stop, alter, or delete X25AM I/O processes
Monitor the X25AM I/O processes and restart them if both the primary and backup
processes fail
You use SCF commands to the WAN subsystem to perform these functions. These
functions are persistent, even after a system restart because the WAN subsystem
stores changes, additions, and deletions in the system-configuration database.
X25AM Configuration and Management Manual—523424-004
3 -2
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.
Review configuration prerequisites
Familiarize Yourself with Subsystems, Commands, and Attributes
Add the X25AM profile
Determine the configuration information for the SWAN concentrator
Add the X25AM I/O processes (one for each line)
Start the X25AM I/O processes
Start the X25AM lines
Add the X25AM subdevices
Task 1: Review Configuration Prerequisites
You need the following:
•
•
•
Either an Integrity NonStop NS-series server using a Gigabit Ethernet 4-port
ServerNet adapter (G4SA) in an IOAM enclosure or a NonStop S-series server
using a Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet Adapter
(FESA), or Gigabit Ethernet ServerNet adapter (GESA).
NonStop operating system (G06.07 or later) installed on your system with the
latest WAN module software and correct version procedures (VPROCs). To use a
G4SA, your NonStop operating system must be G06.24 or later.
The WAN subsystem must be started before you attempt to configure the X25AM
subsystem.
°
°
°
The TCP/IP, LANMON, and TFTP processes running.
The WANMGR process running.
The WAN components WANBOOT and CONMGR running.
If any of these components is missing, see the WAN Subsystem Configuration and
Management Manual for complete instructions on how to add them.
X25AM Configuration and Management Manual—523424-004
3 -3
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. An X25AM I/O process is called an X25AM
DEVICE object in the WAN subsystem; the line that the X25AM I/O process controls is
an X25AM LINE object in the X25AM subsystem. Thus, the SCF command to
configure an I/O process is the ADD DEVICE command; the SCF command to start an
X25AM line is the START LINE command.
Required Modifiers for the ADD DEVICE Command
Some modifiers are required in the SCF ADD DEVICE command to the WAN
subsystem; others are optional. The following modifiers are required to configure an
X25AM I/O process:
•
•
•
•
•
•
ADAPTER, CLIP, LINE
CPU, ALTCPU
IOPOBJECT
PROFILE
RECSIZE
TYPE (must be 61), SUBTYPE (must be 63)
Note. PATH is optional; if not specified, PATH A is the default.
RECSIZE can be set to any 16-bit integer value (1 through 32767); the value does not
affect the maximum record size that you specify for any subdevice on the line
controlled by the I/O process. For information about these modifiers, see the WAN
Subsystem Configuration and Management Manual.
Required Attributes for the ADD SU Command
Some attributes are required in the SCF ADD SU command to the X25AM subsystem;
others are optional. The following attributes are required to configure an X25AM
subdevice on a line:
•
•
•
DEVTYPE
PROTOCOL
RECSIZE
For information about these modifiers, see Section 5, Attribute Descriptions.
X25AM Configuration and Management Manual—523424-004
3 -4
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. You can use SCF commands to the WAN subsystem to list profiles and to view the
modifiers contained in a profile. The INFO PROFILE command lists the devices that are using
a specified profile and lists modifiers and modifier values contained in the profile. The INFO
DEVICE command can display the profile used for the specified X25AM I/O process. For more
information about these SCF commands, see the WAN Subsystem Configuration and
Management Manual.
Task 3: Add the X25AM Profile
The default profile supported by the X25AM subsystem for use with a
NonStop NS-Series or NonStop S-series server is PX250061. This type 832 file is
located in $SYSTEM.SYSnn. The file is part of the X25AM product and contains all the
X25AM I/O process modifiers and their defaults for X25AM I/O processes. If you have
already added this profile, skip this step.
To see a list of profiles that have been added already, issue the following SCF
command:
-> NNAMES PROFILE $ZZWAN.*
The output from the NAMES command tells you the profiles that have been added. If
the profile does not exist, you must add it.
To add the default profile, issue the following SCF command to the WAN subsystem:
-> ADD PROFILE $ZZWAN.#PX250061, FILE $SYSTEM.[SYSnn].PX250061
If you want to change any of the X25AM I/O process modifiers in the default profile,
you can specify them as in the following command example:
-> ADD PROFILE $ZZWAN.#px25c510, FILE $SYSTEM.SYS00.PX250061, &
-> CIRCUITS 510
Notes.
•
•
•
You can assign any name to the profile in the ADD command as long as the name satisfies
the conditions for profile names: up to 10 characters, the first character being alphabetic.
HP recommends that you use the name px250061 as the profile name for an unmodified
profile.
You can have more than one X25am profile but each must have a unique name.
You cannot alter a profile after you have added it; you must delete it, then add it again
including the required changes. Note that it is more appropriate to alter the I/O processes
that use the profile.
X25AM Configuration and Management Manual—523424-004
3 -5
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.
To add an X25AM I/O process, you need to know:
•
•
•
•
SWAN concentrator name
CLIP number with an available line
Line number on the CLIP that the I/O process will control
Processors in which the TCP/IP processes for the SWAN concentrator are running
Ensure you have the following X25AM files:
For the SWAN Concentrator (T3880)
For the SWAN 2 Concentrator (T3881)
$SYSTEM.SYSnn.X25OBJ
$SYSTEM.SYSnn.X25OBJ
$SYSTEM.CSSnn.C1096P00
$SYSTEM.CSSnn.C1096Q00
If you are implementing an X.21 line with an X.21 converter cable, make sure you have
either:
•
•
$SYSTEM.CSSnn.C0051P00 (for the SWAN concentrator T3880)
$SYSTEM.CSSnn.C0051Q00 (for the SWAN 2 concentrator T3881)
The following commands show how to determine this information:
1. Find a SWAN/SWAN 2 concentrator name:
-> NAMES ADAPTER $ZZWAN.#*
lists the names of all concentrators on the system.
2. Find a SWAN CLIP with available lines:
-> STATUS SERVER $ZZWAN.#conc-name.*
displays the status of all lines on all clips on the SWAN concentrator conc-name.
3. Find the processors in which the SWAN TCP/IP processes are running:
-> INFO ADAPTER $ZZWAN.#conc-name
displays the names of the TCP/IP processes.
-> STATUS PROCESS $tcpip-process-name
-> STATUS PROCESS $alt-tcpip-process-name
displays the PPID of each TCP/IP process.
X25AM Configuration and Management Manual—523424-004
3 -6
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.#X25P1, PROFILE px250061, &
IOPOBJECT $SYSTEM.SYS00.x25obj, &
PROGRAM $SYSTEM.CSS00.C1096P00, &
TYPE (61, 63), RECSIZE 32767, &
ADAPTER s01, CLIP 3, LINE 0, PATH A, CPU 0, ALTCPU 1,&
CIRCUITS 510, MAXIOSIZE 32767, &
PACKETSIZE 258, EXTENDEDPOOLPAGES 2047, &
STARTDOWN
Notes.
•
•
PATH is optional; if not specified, PATH A is the default.
Replace C1096P00 with C0051P00 if you are implementing an X.21 interface that
uses an X.21 converter cable (for a SWAN concentrator T3880) or
C1096P00/C1096Q00 with C0051Q00 when implementing a X.21 converter cable for
a SWAN 2 concentrator T3881.
The following example configures the X25AM I/O process $X25S1 on line 1 of CLIP 5
of SWAN 2 concentrator S01 for DCE operations, and modifies the defaults for the
specified modifiers for this I/O process. This example uses the X25AM profile
px25c510, so that the specification of the number of circuits is unnecessary:
->
->
->
->
->
->
->
->
->
->
->
->
->
->
->
->
ADD DEVICE $ZZWAN.#X25S1, PROFILE px25c510, &
IOPOBJECT $SYSTEM.sys00.x25obj,
&
TYPE
(61,63),
&
PROGRAM
$system.CSS00.C1096Q00, &
RECSIZE
32767,
&
ADAPTER
S01
,
&
CLIP
5,
&
LINE
1,
&
PATH
A,
&
CPU
0,
&
ALTCPU
1,
&
MAXIOSIZE
32767,
&
EXTENDEDPOOLPGAES 2047,
&
PACKETSIZE
256,
&
DCE,&
STARTDOWN
For detailed information about using the ADD DEVICE command, see the WAN
Subsystem Configuration and Management Manual.
X25AM Configuration and Management Manual—523424-004
3 -7
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.#io-process-name
Examples of using the SCF START command to start X25AM I/O processes are:
-> START DEVICE $ZZWAN.#X25P1
-> START DEVICE $ZZWAN.#X25S1
Figure 3-3. Starting an X25AM I/O Process
1. START DEVICE $ZZWAN.#X25P1
Management
Information
Base (MIB)
DEVICE
Object
($ZZWAN.#X25P1)
WAN
Subsystem
$ZZWAN
2. Look up
parameters
X25AM
Subsystem
3. Launch
process
X25AM
I/O Process
($X25P1)
VST0303.vsd
For detailed information about using the START DEVICE command, see the WAN
Subsystem Configuration and Management Manual.
X25AM Configuration and Management Manual—523424-004
3 -8
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.
You start an X25AM line using the following command:
-> START LINE $io-process-name
Repeat the START LINE command to start each line that has a started X25AM I/O
process. Example commands for starting an X25AM line are:
-> START LINE $X25P1
-> START LINE $X25S1
Figure 3-4 on page 3-9 illustrates the START command issued to a LINE object
controlled by an X25AM I/O process that has been started.
Figure 3-4. The START Command Issued to a LINE Object Controlled by an
X25AM I/O Process That Has Been Started
Terminal
START LINE
$X25P1
X25AM
Subsystem
X25AM
I/O Process
VST0304.vsd
After the lines have been started, make sure that Activate Path is successful and that
download EMS messages appear in the EMS window.
To check if the line is up, issue the SCF STATUS LINE command. The following is an
example:
-> STATUS LINE $X25P1,DETAIL
X25AM Configuration and Management Manual—523424-004
3 -9
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....... ( 1,4 )
156
NumSU...... 0
510
Path....... B
ON
CTS........ ON
61
Sub-Type... 63
OFF
If a line is not in the STARTED READY state, check the following:
•
•
•
•
Framemode: If one side is DTE, the other side should be DCE.
If a line has been STARTED but is not READY, check the connection to the modem
and its related cables.
If the CLIP code cannot be downloaded (because the line is not going to a
STARTED state), check that you are using the correct version of the CLIP code.
Check that the TFTP process is running correctly.
Make any corrections and try the SCF START LINE command again.
If you have made all of the previous checks and attempts and only if the line does not
become STARTED, reset the SWAN/SWAN 2 concentrator and try the SCF START
LINE command again.
For more information about the SCF START LINE command and commands to
manage lines, see Section 4, SCF Commands for the X25AM Subsystem.
For examples of scripts and TACL macros, see the WAN Subsystem Configuration and
Management Manual.
Task 8: Add X25AM Subdevices
After starting an X25AM I/O process and its line, you can add the subdevices required
for the line by using SCF commands to the X25AM subsystem. To add an X25AM
subdevice, use the SCF ADD SU command. For example:
-> ADD SU $x25p1.#term, PROTOCOL ITI, DEVTYPE (6,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
The subdevice is started automatically.
Another example:
-> ADD SU $x25p1.#term1, PROTOCOL PTP, DEVTYPE (9,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
The first three attributes, PROTOCOL, DEVTYPE, and RECSIZE, are required; all
other attributes are optional. PROTOCOL and DEVTYPE are related; for descriptions
of all subdevice attributes, see Section 5, Attribute Descriptions.
X25AM Configuration and Management Manual—523424-004
3- 10
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. Perform these tasks:
1.
2.
3.
4.
5.
6.
Stop the line and its subdevices
Stop the I/O process
Change the I/O process modifiers
Start the I/O process
Start the line
Add the subdevices to the line
Figure 3-5 on page 3-12 illustrates making persistent changes to an X25AM I/O
process.
Caution. If you delete an X25AM I/O process by issuing the SCF DELETE DEVICE command
to the WAN subsystem, the X25AM line ceases to exist (it is deleted from the
system-configuration database when the I/O process is deleted).
After you have changed the I/O process, you need to restart it using SCF START
DEVICE command to the WAN subsystem and then start the line using the SCF
START LINE command to the X25AM subsystem. Then you can add the subdevices to
the line and resume interacting with the line using SCF commands to the X25AM
subsystem.
An example sequence of commands to alter an I/O process is:
-> STOP LINE $x25p1
-> STOP DEVICE $ZZWAN.#x25p1
-> ALTER DEVICE $ZZWAN.#x25p1, V25, FIFO, ENABLECALLEDADDREXT
-> START DEVICE $ZZWAN.#x25p1
-> START LINE $x25p1
-> ADD SU $x25p1.#term, PROTOCOL ITI, DEVTYPE (6,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
For information about the SCF STOP LINE, START LINE, ADD SU commands, see
Section 4, SCF Commands for the X25AM Subsystem headings for these commands.
For more information about SCF STOP DEVICE, START DEVICE, ALTER DEVICE
commands, see the WAN Subsystem Configuration and Management Manual.
X25AM Configuration and Management Manual—523424-004
3- 11
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. These modifiers are listed but are not described.
Where there is a choice of modifiers, they are listed by the default modifier. Default
values are shown where applicable.
Table 3-1. List of X25AM Modifiers and Defaults (page 1 of 4)
Modifier Name
(Default Listed First)
Default Setting
ASCII or EBCDIC
Not in effect
AUTOLOAD or
NOAUTOLOAD
AUTOLOAD
CALLUSERDATA or
NOCALLUSERDATA
CALLUSERDATA
Determines value for CUD
field in Call Request
packet.
CIRCUITS
32
Maximum is 510.
CLBDOWNLOADENTRIES
Not in effect
CLBSTATUSPROBETIME
Not in effect
CLBTIMER
Not in effect
Notes
-- Not applicable.
X25AM Configuration and Management Manual—523424-004
3- 12
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.)
DTE or DCE
DTE
EMSFORCLEAR or
NOEMSFORCLEAR
NOEMSFORCLEAR
EMSFORFRMR
Zero
Configured with a
non-zero value to enable
EMS message generation
when a link reset occurs
due to an FRMR (Frame
Reject) condition.
ENABLECALLEDADDREXT
Not set
Applies only to Call
Address Extension facility
users.
ENABLEPVCOUTOFORDER
or
DISABLEPVCOUTOFORDER
ENABLEPVCOUTOFORDER
Applies to PVC only.
EXTENDEDPOOLPAGES
50 (pages)
Replaces
LOCALPOOLPAGES.
FIFO
Not set
IDLERESPRR or
IDLECMDRR
IDLERESPRR
LINEQUALITYTHRESHOLD
500
L2DOWNLINE or
NOL2DOWNLINE
L2DOWNLINE
L2IDLETIMEOUT
1500
L2IFRAMERECOVERY
Not in effect
L2NODISC or L2DISC
L2NODISC
--
L2RETRIES
10
--
L2TIMEOUT
300 (3 sec.)
--
L2WINDOW
4
--
L3MOD8 or L3MOD128
L3MOD8
--
L3RECVTHRUPUT
4
--
Notes
nnnn is the speed
---
--
-- Not applicable.
X25AM Configuration and Management Manual—523424-004
3- 13
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.
PACKETSIZE
128
--
PAGE6520BLKSIZE
256
Profile^Version
Not set
--
PROGRAM
C1096P00
Modify the default using
C1096Q00 for SWAN 2
RS232, RS422
RS232
--
SENDCALLINGADDRESS or
NOSENDCALLINGADDRESS
SENDCALLINGADDRESS
--
SENDSTOP
Not set
Causes the modem
signals to be dropped
when ABORT or STOP
line is issued.
STRIPPARITY or
NOSTRIPPARITY
STRIPPARITY
--
SYNCS
Not in effect
TWOWAYCALLS
TWOWAYCALLS
For list of alternate
modifiers, see
TWOWAYCALLS on
page 3-32.
Txx and Rxx
Network-dependent
For default values, see
Table 3-4, Timeout and
Retry Counter Default
Values, on page 3-33.
-- Not applicable.
X25AM Configuration and Management Manual—523424-004
3- 14
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. Some of the X25AM modifiers listed are not supported but appear in the
X25AM profile object. These modifiers are listed as not in effect.
Caution. Some modifiers have default values that are in effect even if the modifier is not
specified.
Numeric Range Validation
X25AM automatically performs range checking for the minimum and maximum values
for all modifiers that have numeric values.
When an invalid value is detected, the WAN subsystem responds with the following
error message:
WAN E 00010 Modifier name’s value number is invalid.
ASCII
Note:
Not in effect (ASCII is not supported)
Alternate Modifier:
EBCDIC
ASCII and EBCDIC have no effect on the X25AM line handler process.
AUTOLOAD
Default:
AUTOLOAD
Units:
Not applicable
Alternate Modifier:
NOAUTOLOAD
AUTOLOAD and NOAUTOLOAD control the downloading of the SWAN concentrator
microcode to the communications line interface processor (CLIP).
X25AM Configuration and Management Manual—523424-004
3- 15
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.
CALLUSERDATA
Default:
CALLUSERDATA
Units:
Not applicable
Alternate Modifier:
NOCALLUSERDATA
CALLUSERDATA or NOCALLUSERDATA enables or disables the call user data (CUD)
field in a call request packet.
•
•
CALLUSERDATA: The default value is 4 bytes of zeroes (00 00 00 00).
NOCALLUSERDATA:
For an application using the process-to-process (PTP) protocol for a subdevice,
the default value is no bytes of user data.
For an application using the interactive terminal interface (ITI) protocol for a
subdevice, the default value is 4 bytes of zeroes (00 00 00 00).
The value can be altered with the SCF line attribute CUD.
CIRCUITS n
Default:
32
Units:
Integers
Range:
1 through 510
The CIRCUITS value determines the maximum number of subdevices (PVCs plus
SVCs) that can be added to a line. The subdevices must be added to a line through
SCF or SPI.
The number of configurable subdevices depends on the modifiers PACKETSIZE and
L3WINDOW. For higher packet sizes (more than 256 bytes), the number of subdevices
which can be configured may be less than 510.
All subdevices default to SVCs, beginning with 1. You can use SCF to alter the number
of PVC (SCF line attribute PVCRANGE) and SVC (SCF line attribute SVCRANGE)
assignments but not to change the total number of circuits.
X25AM Configuration and Management Manual—523424-004
3- 16
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.
CLBWINDOWEXT
Note:
Not in effect (CLBWINDOWEXT is not supported)
CLBWINDOWEXT has no effect on the X25AM line handler process.
CLOCKnnnn
Default:
600 (no leading 0)
Units:
Baud
Range:
600, 1200, 2400, 4800, 9600, 19200, 38400, 56000, 115200
You can use the SCF line attribute CLOCKSPEED to alter the clock speed.
DCE. See DTE
DCECLOCK
Default:
DCECLOCK
Units:
Not applicable
Alternate Modifier:
DTECLOCK
DCECLOCK disables the communications line interface processor (CLIP) clock.
DTECLOCK enables the CLIP clock. Use DTECLOCK if your system uses cabling
instead of a modem eliminator.
You can use the SCF line attribute CLOCKMODE to alter DTECLOCK and
DCECLOCK.
X25AM Configuration and Management Manual—523424-004
3- 17
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.67 seconds)
DSRTIMER is the time interval the SWAN/SWAN 2 concentrator waits to receive a
DATASET READY signal from the modem before returning a status message to the
X25AM I/O process.
The value can be altered with the SCF line attribute DSRTIMEOUT.
DTE
Default:
DTE
Units:
Not applicable
Alternate Modifier:
DCE
DTE and DCE control whether a line (that is, its I/O process) operates as a DTE or a
DCE. A line is usually configured as a DTE. You configure a line as a DCE for special
requirements (for example, loopback testing).
A DTE and a DCE have slightly different Link Layer addressing, Packet Layer LCN
selection, and call-collision processing (see Figure 3-6 on page 3-19).
This modifier can be altered with the SCF line attribute FRAMEMODE.
X25AM Configuration and Management Manual—523424-004
3- 18
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. See ASCII
EMSFORCLEAR
Default:
NOEMSFORCLEAR
Units:
Not applicable
Alternate Modifier:
EMSFORCLEAR
When EMSFORCLEAR is set, X25AM generates a clear message to indicate that a
connection has been cleared with either a diagnostic code or any cause code other
than zero. When the default, NOEMSFORCLEAR, is set, X25AM does not generate a
message.
EMSFORFRMR
Default:
Zero
Units:
Not Applicable
Range:
0 to 200
EMSFORFRMR is configured with a non-zero value to enable generation of the EMS
message when a link reset occurs due to an FRMR condition on an X25AM line. An
FRMR condition occurs when an illegal frame is received on an X25AM line.
X25AM Configuration and Management Manual—523424-004
3- 19
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.
•
•
If set, this modifier enables sending a Called Address Extension, even when the
previous Call Accept packet does not contain a Calling Address Extension.
If not set (or reset), a Called Address Extension is not sent if the previous Call
Accept packet does not contain the Calling Address Extension.
ENABLEPVCOUTOFORDER
Default:
ENABLEPVCOUTOFORDER
Units:
Not applicable
Alternate Modifier:
DISABLEPVCOUTOFORDER
Note:
Only applies to PVC subdevices
ENABLEPVCOUTOFORDER or DISABLEPVCOUTOFORDER specifies whether or
not the console messages 225 and 226 are generated when a permanent virtual circuit
(PVC) is out of order.
•
•
ENABLEPVCOUTOFORDER: Generates console messages 225 and 226 for a
PVC that is out of order.
DISABLEPVCOUTOFORDER: Does not generate console messages 225 and
226. When an out-of-order PVC is a normal (frequent) occurrence, you might not
want to generate these messages.
EXTENDEDPOOLPAGES
Default:
50
Units:
Pages (2048 bytes)
Range:
10 to 2047
EXTENDEDPOOLPAGES specifies the total amount of memory (in pages) needed for
all the circuits configured for the line.
Note. The EXTENDEDPOOLPAGES modifier replaces the LOCALPOOLPAGES modifier.
However, the LOCALPOOLPAGES value was calculated automatically by X25AM. You must
calculate a value for EXTENDEDPOOLPAGES.
X25AM Configuration and Management Manual—523424-004
3- 20
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.
The total amount of memory needed for a single circuit (N) is the sum of OCB^SIZE,
HOLDING^BUFFER^SIZE, and FILE^SYSTEM REQUEST^BUFFER^SIZE.
Calculations (in bytes) for each of these variables and for the total value (in pages) of
EXTENDEDPOOLPAGES are as follows:
HOLDING^BUFFER^SIZE =
(packet size + 7 ) * ( L3window size) + 48
= 318
(packet size 128, window 2)
= 1889
(packet size 256, window 7)
For PTP or ITI subdevices,
or READ or WRITE BUFFER^SIZE = MAXIOSIZE
Note: MAXIOSIZE defaults to 4096 bytes
For NAM subdevices, BUFFER SIZE =
(Expand packet size + 12) * [min (expand window size,7) + 1]
For QLLC subdevices, BUFFER SIZE =
(SNAX packet size + 16) * [min [(SNAX window size * 2 + 1), 7] + 1]
Size^Of^Bytes
for a single circuit
= HOLDING^BUFFER^SIZE
+ BUFFER SIZE
EXTENDEDPOOLPAGES =
[sum of Size^Of^Bytes for each circuit]/ 2048
(This value should be rounded up.)
Note. You need to add 10 pages to the calculated number of EXTENDEDPOOLPAGES to
accommodate memory fragmentation and the SPI reply buffer, which may require up to 5 KB.
Example:
This example of estimating EXTENDEDPOOLPAGES uses the values of 50 circuits
configured, 128-byte packet size, L3 window of 7 with five opens, and default
MAXIOSIZE. Two methods of calculation are provided. The first method provides a
conservative estimate, ensuring a configuration that is less likely to run out of memory.
HOLDING^BUFFER^SIZE = (128 + 7) * 7 + 48 = 993
FILE^SYSTEM^REQUEST^BUFFER^SIZE = 4096 + 6 = 4102
TOTAL BYTES PER CIRCUIT = 993 + 4102
= 5095
TOTAL PAGES PER CIRCUIT = 5095 / 2048 =
3 (rounded up)
50 circuits * 3 = 150
NUMBER OF EXTENDEDPOOLPAGES = 150 + 10 = 160 (conservative)
If you would like to reserve seven pages, you could use the following less-conservative
method of calculating extended pages:
(NUMBER OF CIRCUITS * TOTAL BYTES PER CIRCUIT) / 2048 =
NUMBER OF EXTENDEDPOOLPAGES
X25AM Configuration and Management Manual—523424-004
3- 21
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.
If not set (reset), X25AM send the L3 packets in the order of the scan (0, 1, ...) of
all SUs on the line.
IDLECMDRR. See IDLERESPRR
IDLERESPRR
Default:
IDLERESPRR
Units:
Not applicable
Alternate Modifier:
IDLECMDRR
IDLECMDRR or IDLERESPRR specifies whether an RR (receiver-ready) command
frame or an RR response frame is sent when an L2IDLETIMEOUT occurs.
•
•
IDLERESPRR: Sends an RR response frame. The poll bit is not set; therefore, no
reply is required.
IDLECMDRR: Sends an RR command frame. The poll bit is set; therefore, a reply
is required.
The value that is used depends on the network requirement.
X25AM Configuration and Management Manual—523424-004
3- 22
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.
The line-quality check number is reported (as a percentage) if there is a change of 1%
or more from the last line-quality check. Every time the line-quality number reflects a
change of 5% or more since the last check, a console message is written. Adjusting
the modifier affects the number of console messages that must be examined.
The value can be altered with the SCF line attribute THRESHOLD.
L2DISC. See L2NODISC
L2DOWNLINE
Default:
L2DOWNLINE
Units:
Not applicable
Alternate Modifier:
NOL2DOWNLINE
If L2DOWNLINE is set, X25AM checks the DSR timer status. If 50 DSR status
changes occur, the line is downed. If NOL2DOWNLINE is set, X25AM checks the DSR
timer status on a line at 1-minute intervals regardless of how many DSR status
changes it finds.
Note. This modifier has no effect in G-series or H-series RVUs.
L2IDLETIMEOUT n
Default:
1500
Units:
.01 seconds
Alternate Modifier:
0 through 32767 (5 minutes 27.67 seconds)
L2IDLETIMEOUT is a timeout interval. If no activity occurs during the specified time,
an RR (receiver-ready) command or response is sent. The link is idle.
Start with the network value. If timeouts occur too frequently, increase the value.
L2IDLETIMEOUT is the network subscription parameter T4.
The L2IDLETIMEOUT value can altered with the SCF line attribute IDLETIMEOUT.
X25AM Configuration and Management Manual—523424-004
3- 23
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.
When an X25AM I/O process wants to reset a link (all counters are set to zero and all
calls are cleared), the process issues Set Asynchronous Balanced Mode (SABM) or
disconnect (DISC) commands. If a response is not received, the process continues to
send either SABM or DISC commands.
If L2NODISC is specified, the process sends SABM commands.
If L2DISC is specified, the process sends DISC commands.
L2RETRIES n
Default:
10
Units:
Number of retries (in integers)
Range:
0 through 255
L2RETRIES is the number of frame-layer retry commands sent without receiving a
response executed before a link is considered disconnected and is reset (all counters
set to 0).
L2RETRIES is the network subscription parameter N2.
The value can be altered with the SCF line attribute RETRIES.
L2TIMEOUT n
Default:
300 (3 seconds)
Value:
.01 seconds
Range:
0 through 32767 (5 minutes, 27.67 seconds)
L2TIMEOUT is the time interval spent waiting for a frame-layer response before
retrying a frame-layer request.
L2TIMEOUT is the network subscription parameter T1.
The value can be altered with the SCF line attribute T1TIMEOUT.
X25AM Configuration and Management Manual—523424-004
3- 24
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. The packet-numbering sequence is 0 through 7 (and
then start at 0).
L3MOD128: Specifies modulo 128. The packet-numbering sequence is 0 through
127 (and then start at 0).
L3MOD8 and L3MOD128 are network subscription parameters.
The value can be altered with the SCF line attributes L3MOD8 or L3MOD128.
L3RECVTHRUPUT n
Default:
4
Units:
Integers
Range:
3 through 12
L3RECVTHRUPUT specifies the receiving 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 on page 3-26 lists the throughput classes and associated bits per second.
X25AM Configuration and Management Manual—523424-004
3- 25
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.25 Recommendation
2
Reserved according to the ITU-T X.25 Recommendation
3
75
4
150
5
300
6
600
7
1200
8
2400
9
4800
10
9600
11
19,200
12
48,000
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
L3WINDOW n
Default:
2
Units:
Integers
Range:
1 through 7 (used with L3MOD8); 1 through 15 (used with L3MOD128)
L3WINDOW specifies the default packet window size. The window size is the number
of data packets that can be sent before an acknowledgment is received. Window size
is a network-subscription parameter.
The value can be altered with the SCF line attribute L3WINDOW.
X25AM Configuration and Management Manual—523424-004
3- 26
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).
When an application sends READ or WRITE request, the maximum limit for the read or
write count is determined by the MAXIOSIZE value. If the read or write count exceeds
MAXIOSIZE, a file-system error is returned.
netid_selection
Default:
X25XA
Units:
Not applicable
Alternate Selections:
DATANET
PSS
UNINET
DATAPAC
TELENET
X25
DATEXP
TRANSPAC
X25NP
DDN
TWINET
X25SA
DDXP
TYMNET
X25UD
Note. When you specify this modifier, replace netid_selection with one of the alternate
modifiers. The keyword NETID does not appear.
NETID specifies a set of network options that are named by one of the NETID modifier
selections listed above. The alternate selections are for special port numbering, PAD
parameter profiles, and other network-dependent requirements.
For more information about SETPARAM commands related to NETID, see the X25AM
Programming Manual. For more information about NETID, see Appendix D, Using the
NETID Modifier. For more information about PAD parameter profiles, see Section 4,
SCF Commands for the X25AM Subsystem.
X25AM Configuration and Management Manual—523424-004
3- 27
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.
If you use the fast-select facility and the PACKETSIZE is less than 256 bytes, you must
set EXTFORMAT to ON in the profile (for G-series or H-series and later RVUs) or
configure the X25 line for extended format by SYSGEN (for D-series RVUs).
If the packet size is greater than or equal to 256, you can use the SCF line attribute
EXTFORMAT to alter the value of NOEXTFORMAT in X25AM.
NOINCOMINGCALLS. See TWOWAYCALLS
NOOUTGOINGCALLS. See TWOWAYCALLS
NOREPORTREDIRECT
Default:
NOREPORTREDIRECT
Units:
Not applicable
Alternate Modifier:
REPORTREDIRECTION
NOREPORTREDIRECT or REPORTREDIRECTION specifies whether a user-coded
application can retrieve a data terminal equipment (DTE) address by using a
SETPARAM 1 command.
NOSENDCALLINGADDRESS. See SENDCALLINGADDRESS
SENDSTOP
Default:
Not set
Units:
Not applicable
When set, this modifier causes the modem signals to be dropped when the SCF
ABORT/STOP command is issued.
X25AM Configuration and Management Manual—523424-004
3- 28
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. See TWOWAYCALLS
PACKETSIZE n
Default:
128
Units:
Byte
Range:
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096
PACKETSIZE sets the default packet size (data bytes for each packet, not total bytes
for each packet) for the circuits connected to the line and specifies the maximum
packet size that X25AM can accept without negotiation.
The optional network subscription parameter, NEGOTIATE PACKETSIZE, is specified
for each subdevice using SCF commands to the X25AM subsystem. If the X25AM
subsystem cannot find a subdevice with NEGOTIATE PACKETSIZE enabled, it cannot
process an incoming call that has a packet size greater than the value specified by the
PACKETSIZE modifier for the X25AM I/O process.
The optimum value for PACKETSIZE depends on your network.
PAGE6520BLKSIZE n
Default:
256
Units:
Bytes
Range:
256 through 8000
PAGE6520BLKSIZE specifies the terminal block size in bytes. Terminals that emulate
6520 and 6530 terminals (such as PCs that emulate a 6530) can be used, but they can
have different block sizes.
This is a terminal-dependent option; it can be found in the appropriate terminal
documentation. If a terminal has a configurable blocksize, the terminal blocksize
should be selected according to the specification in the terminal documentation.
PAGE6520BLKSIZE is used with ITI user-coded application programs.
The value can be altered with the SCF line attribute PAGE6520BLKSIZE.
X25AM Configuration and Management Manual—523424-004
3- 29
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.CSSnn.C1096Q00,
and $SYSTEM.CSSnn.C0051Q00
PROGRAM identifies the Kernel-based 510 microcode file, where the data link control
(DLC) task is located. This file is downloaded to the SWAN concentrator CLIP RAM
memory when the line is started.
Replace the default for PROGRAM only if you are:
•
•
Using a SWAN 2 concentrator (use modifier C1096Q00 instead)
Implementing an X.21 interface that has an X.21 converter cable (for SWAN
concentrator (T3880), use modifier C0051P00; for a SWAN 2 concentrator, use
modifier C0051Q00).
This modifier is listed only as C1096P00, C0051P00, C1096Q00, or C0051Q00 among
the device modifiers in the INFO DEVICE command’s output.
RS232
Default:
RS232
Units:
Not applicable
Alternate Modifiers:
RS422 (equivalent to RS449)
RS232 or RS422 selects the hardware protocol used for the line. The value is
determined by the electrical interface supported by the modem.
The value can be altered with the SCF line attribute INTERFACE.
X25AM Configuration and Management Manual—523424-004
3- 30
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. You should concatenate a port
number with the address specified with SRCADDR or NETADDR if allowed by the
network.
NOSENDCALLINGADDRESS: Uses a zero-length calling address.
The value can be altered with the SCF line attribute CALLINGADDR.
SENDSTOP
Default:
Not set
Units:
Not applicable
When set, this modifier causes the modem signals to be dropped when an SCF
ABORT/STOP command is issued.
STRIPPARITY
Default:
STRIPPARITY
Units:
Not applicable
Alternate Modifier:
NOSTRIPPARITY
Note:
Only applies to ITI subdevices set to conversation mode
STRIPPARITY or NOSTRIPPARITY specifies whether or not the parity bit is stripped
from data transferred to the application buffer. This is a subdevice-dependent option
(parity-setting and parity-checking are subdevice attributes). Parity applies only to ITI
subdevices set to conversation mode: it does not apply to PTP subdevices.
STRIPPARITY can also serve as a workaround for terminals that must transmit 8-bit
characters, such as accented vowels in some European languages.
X25AM Configuration and Management Manual—523424-004
3- 31
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.
NOCALLS is used for permanent virtual circuits (PVCs). The modifiers can be altered
with the SCF line attribute CALLS.
Table 3-3. Call Enabling and Call Disabling
Modifier
Incoming calls
Outgoing calls
TWOWAYCALLS
Accepted
Accepted
NOCALLS
Rejected
Rejected
INCOMINGCALLS
Accepted
Not Applicable
NOINCOMINGCALLS
Rejected
Not Applicable
OUTGOINGCALLS
Not Applicable
Accepted
NOOUTGOINGCALLS
Not Applicable
Rejected
The value can be altered with the SCF line attribute CALLS.
Txx n and Rxx n
Default:
See Table 3-4
Units:
Seconds
Range:
Txx n: 5 through 360; Rxx n: 0 through 15
Txx and Rxx are network-dependent parameters.
Txx is used for timeout modifiers and Rxx is used for retry counters. These values
account for network-specific delays and timing.
Table 3-4 lists Txx timeout values, which are the intervals before an operation can be
retried, and Rxx retry counter values, which are the numbers of times an operation can
X25AM Configuration and Management Manual—523424-004
3- 32
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. Timeout and Retry Counter Default Values
Operation
Timer
(Txx)
Default
Timeout Period
Retry Counter
(Rxx)
Default
Number of Retries
Line
Restart
T20
DTE
180 seconds
(5-360)
R20
1(0-15)
Call request
T21
DTE
200 seconds
(5-360)
Reset
T22
DTE
180 seconds
(5-360)
R22
1(0-15)
Clear
T23
DTE
180 seconds
(5-360)
R23
1(0-15)
Restart
T10
DCE
60 seconds
(5-360)
R10
1(0-15)
Call request
T11
DCE
180 seconds
(5-360)
Reset
T12
DCE
60 seconds
(5-360)
R12
1(0-15)
Clear
T13
DCE
60 seconds
(5-360)
R13
1(0-15)
0 (only value allowed)
0 (only value allowed)
The following are four different examples of Rxx n and Txx n entries:
T20 185,T21 220
R20 2,R22 2,R21 2
T20 185,R20 2,R22 2,T21 220,R21 2
T20 185,T21 220,R20 2,R22 2,R21 2
Table 3-5 lists all of the timers you can set using X25AM I/O process modifiers. For
details about a specific modifier, refer to its entry elsewhere in this section.
Table 3-5. X25AM I/O Process Modifiers for Timers
Timer
I/O Process Modifier
Default Value
Description
T
Txx n
See Table 3-4 on
page 3-33
Timeout modifiers
R
Rxx n
See Table 3-4 on
page 3-33
Retry counters
K
L3WINDOW n
4
Number of outstanding I-frames
X25AM Configuration and Management Manual—523424-004
3- 33
Numeric Range Validation
Configuring an X25AM Subsystem
Table 3-5. X25AM I/O Process Modifiers for Timers
Timer
I/O Process Modifier
Default Value
Description
N1
Related modifier:
PACKETSIZE n
If PACKETSIZE=128,
N1=1056
Maximum number of bits in an Iframe, including Address,
Control, and FCS bytes
N2
L2RETRIES n
10
Maximum retransmission count
T1
L2TIMEOUT n
3
Retransmission timer
UNSOLF
Default:
Not set
Units:
Not applicable
Alternate Modifier:
None; use RESET UNSOLF to reset this modifier
Note:
DTE must be set for this modifier to take effect.
UNSOLF allows an unsolicited F response to be ignored.
•
•
If UNSOLF is set, an unsolicited F response is ignored and does not reset the
LAPB connection.
If UNSOLF is not set (or reset), an unsolicited F response resets the LAPB
connection.
V25
Default:
Not set
Units:
Not applicable
Alternate Modifier:
None; use RESET V25 to reset this modifier
•
If V25 is set, the connection between the DTE and the DCE is switched using a
General Service Telephone Network (GSTN).
Before establishing the connection with the remote DTE, the application must
establish the connection with the DCE. For details, see the X25AM Programming
Manual.
•
If V25 is not set (or reset), the connection is assumed to be a direct connection
with a lease line.
You can set or reset this modifier with the SCF line attribute INTERFACE.
X25AM Configuration and Management Manual—523424-004
3- 34
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.
X25V1984 allows some ITU-T extended format packets with the following features:
°
The facilities field in Call Connected and Call Accepted packets can be 109
bytes long.
°
The address and facilities field can be present in the Clear Confirmation
packet.
°
Interrupt packets can have a data field of 1 to 32 bytes.
The value depends on the network.
X25AM Configuration and Management Manual—523424-004
3- 35
Configuring an X25AM Subsystem
Numeric Range Validation
X25AM Configuration and Management Manual—523424-004
3- 36
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.
Subsystem Control Facility
The Subsystem Control Facility (SCF) configures, controls, and collects information
about G-series and H-series data communications subsystems.
The WAN subsystem configures, starts and stops, and monitors X25AM I/O processes.
The WAN subsystem must be started before you attempt to configure the X25AM
subsystem. For information on using the WAN subsystem to configure and start data
communications processes in general, see the WAN Subsystem Configuration and
Management Manual and for information on X25AM in particular, see Section 3,
Configuring an X25AM Subsystem.
The WAN subsystem does not allow you to alter and manage X25AM entities such as
lines and subdevices; you manage these entities with SCF commands to the X25AM
subsystem.
SCF provides an operator interface to a process called the Subsystem Control Point
(SCP). SCP in turn provides an interface to the various subsystem processes
performing data communications operations and services (Figure 4-1 on page 4-2).
The default SCP process, known to the system as $ZNET, provides access for
application programs (whether local or remote) to monitor and control the X25AM
subsystem through the WAN Manager process.
SCF automatically opens and closes SCP. In most cases, the default SCP is the only
one you will need. If you should need to establish an SCF session through a specific
SCP other than the default SCP, you can start additional SCPs by using either the SCF
RUN command or the TACL RUN command.
X25AM Configuration and Management Manual—523424-004
4 -1
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.
SCP links SCF and other G-series and H-series data communications subsystems.
SCP provides security (by restricting access to sensitive commands), version control,
and tracing support for subsystems. SCP supports NonStop application process pairs.
SCF can only be used interactively.
SCF Commands
Many SCF commands operate on the objects belonging to a subsystem. For example,
you can use the INFO command to display the current attribute values for an X25AM
line, then use the ALTER command to change those attribute values.
Several commands display and change SCF session parameters. For example, the
OUT command controls the files used for display output. The ASSUME command sets
the default object type and object name.
X25AM Configuration and Management Manual—523424-004
4 -2
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.
How SCF Works
SCF performs most commands in the following sequence:
1. When SCF receives a command, it interprets the command and executes it. SCF
can handle some commands without interaction with SCP (for example, OUT).
2. If the command involves control or configuration of a subsystem object or a
request for information about an object, SCF produces a message that describes
the object and the operation. This message passes to an X25AM process through
SCP.
3. After the X25AM process has processed the message, it returns a completion
message (one or more messages, if the command is a request for information
about an object) to SCF through SCP. SCF displays the requested information, if
any, and then displays its prompt and waits for the next command. If the
completion message indicates an error condition, SCF displays an appropriate
message and then displays its prompt.
Running SCF
SCF resides in the file $SYSTEM.SYSTEM.SCF. To start SCF, use the RUN
command. For more information about the syntax of the RUN command, see the SCF
Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs.
Input Sources and Output Destinations
SCF accepts command input from a terminal or a disk file; it directs output to a disk
file, an application process, a terminal, or a printer. The RUN command that initiates
SCF determines the initial input source and output destination.
When an SCF line is active, you can change both the source and the destination
temporarily. For information about how to set the initial input source and output
destination and how to change them, see the SCF Reference Manual for G-Series
RVUs or SCF Reference Manual for H-Series RVUs.
X25AM Configuration and Management Manual—523424-004
4 -3
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.
For SCF commands that pertain to an object, an object type and an object name follow
the keyword. For example, the following command aborts the line object named
$LIN32:
-> ABORT LINE $LIN32
This command aborts a subdevice on that line:
-> ABORT SU $LIN32.#PC
To get additional information, follow the object name with a comma and the parameters
required to specify the action. For example, the following command changes the value
of the BCUG attribute for a line:
-> ALTER LINE $LIN32, BCUG 200
In commands that provide displayed information, such as the INFO and STATUS
commands, you can specify the DETAIL keyword to get a detailed information display.
The full syntax of each SCF command to the X25AM subsystem is given in this section
starting with the ABORT Command on page 4-12. The syntax of SCF commands that
are not subsystem-specific is given in the WAN Subsystem Configuration and
Management Manual and in the SCF Reference Manual for G-Series RVUs or
SCF Reference Manual for H-Series RVUs.
SCF Online Help
SCF provides online support when you use the HELP command (described fully in the
SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series
RVUs). If you enter the HELP command, SCF responds with a menu that guides you
through the help options; simply select from the options displayed in the menu for the
information you need.
Version Compatibility
The current version of X25AM is compatible with G-series and H-series servers.
X25AM Configuration and Management Manual—523424-004
4 -4
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.
Any of the SCF commands (START, STOP, ABORT, ACTIVATE, for example) can be
substituted for the ALTER command. These line-state and attribute changes are
dynamic; they exist until either a system restart or until a subsequent SCF change to
the line. For a table of all the SCF commands available for the X25AM subsystem, see
Table 4-3 on page 4-10.
An example command for starting an X25AM line is:
-> START LINE $x25p1
Figure 4-2. Making Dynamic Changes to an X25AM Line
Terminal
ALTER LINE $X25P1
X25AM
Subsystem
X25AM
I/O Process
VST0402.vsd
To make persistent changes to an X25AM line, you make the changes to the X25AM
I/O process that controls the line. Refer to Altering an X25AM I/O Process on
page 3-11.
Because subdevices are managed (added, deleted, and so forth) using SCF
commands to the X25AM subsystem, they are dynamic objects; after a system restart
you must add the subdevices to each of the X25AM lines with which you want them
associated.
X25AM Configuration and Management Manual—523424-004
4 -5
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.
The object type categorizes the object; the object name uniquely identifies each object
within the subsystem.
Object-Type Definition
An object-type is a subsystem-specific keyword that identifies the type of object.
LINE, null, PROCESS, and SU are the object-types for the X25AM subsystem. If
you omit the object-type, the X25AM subsystem may attempt to determine the
object-type. If an attempt to determine the object-type fails, X25AM displays an
error message. Refer to Appendix C, X25AM Error Messages.
Object-Type Hierarchy
The X25AM object types supported by SCF, in hierarchical order, are PROCESS,
LINE, and SU. The NAMES and VERSION commands require no object type. The
hierarchy is important when issuing commands to the X25AM subsystem for
processing. For example, because the LINE object type is subordinate to the
PROCESS object type, any commands pertaining to a LINE object can be issued only
when the PROCESS object is in the STARTED state.
In summary, the object types used by the X25AM subsystem are:
PROCESS
Refers to an X25AM I/O process running on a
NonStop NS-series or NonStop S-series server.
LINE
Refers to a data communications line connected through a
modem to an X.25 network. The LINE object name is the same
as that of the PROCESS object; for example, $X25PM. For
G-series or H-series RVUs, one line supports from 1 through
510 subdevices.
SU
Refers to an X25AM subdevice associated with a line.
Note. The VERSION and NAME commands require no object type.
Figure 4-3 on page 4-7 shows the hierarchy of object types for the X25AM subsystem.
X25AM Configuration and Management Manual—523424-004
4 -6
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. The recommended form for X25AM is
$identifier, where identifier consists of a letter followed by zero to six
alphanumeric characters with no embedded blanks, for example, $X25P1. The process
name is defined with the SCF ADD DEVICE command to the WAN subsystem.
•
LINE Object Names
LINE object names refer to data communications lines connected through a modem to
an X.25 network. The LINE object name is the same as that of the PROCESS object
name, for example, $X25P1.
•
SU Subdevice Object Names
SU object names refer to X25AM subdevices associated with a line. An SU object
name consists of the LINE object name plus an SU object qualifier. A typical SU object
name might be $X25P1.#TERM7.
Wild-Card Support
The wild-card characters are the asterisk (*) and the question mark (?). * denotes any
number of characters;? denotes any single character. When you use wild-card
notation, the first character of the name must be an alphabetic character, an asterisk,
or a question mark. The second, and any subsequent characters, can be any
alphanumeric character, *, or ?. The X25AM subsystem does not support wild-card
X25AM Configuration and Management Manual—523424-004
4 -7
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. X25AM Object Specifications
Object Type
Object Name
Object-Name Format
LINE
line-name
$line-name ($process-name)
null
process-name
$process-name
PROCESS
process-name
indirect-processname
process-name
SU
su-name
$line-name.#su-name
The variable object-spec appears throughout the command descriptions to
represent all variations of object references. The general form of object-spec is
[ object-type ] [object-name
[ (object-name [ , object-name ]... )
]
]
Object States
Objects can have operational states, such as STOPPING or STARTING. The exact
sequence of states an object goes through varies from object to object and from
subsystem to subsystem. Some subsystem commands recognize only a few states.
The operational state of an object at a given instant is important. For example, certain
commands have no effect on objects unless those objects are in a specific state.
The following states are recognized by the X25AM subsystem:
STOPPED
The object is not ready for normal operations. STOPPED is equivalent to
down, not ready, or killed.
STARTED
The object is initialized. The object is ready for normal data traffic when
LinkState is READY.
X25AM Configuration and Management Manual—523424-004
4 -8
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.
Each of these attributes identifies some characteristic of that object and has an
associated set of values. For example, you can change BCUG, a line attribute, by
using the ALTER command.
Depending on the action of the command, you may also be required to provide one or
more attribute specifiers (each consisting of an attribute name and value) to indicate
which of the object’s attributes are to be changed and what the new value is to be.
Default values exist for many attributes. For information about using the INFO
command to display the current attribute values for an object, see INFO Command on
page 4-26.
Required Attributes
Some attributes are categorized as required in the SCF ADD SU command and some
are categorized as optional by the X25AM subsystem. The following attributes are
required:
•
•
•
DEVTYPE
PROTOCOL
RECSIZE
For information about these attributes, see Section 5, Attribute Descriptions.
Frequently Performed Tasks on X25AM Objects
Table 4-2 lists the tasks you may perform frequently and indicates if they are
performed by SCF commands to the X25AM subsystem or to the WAN subsystem.
Table 4-2. Configuring and Managing X25AM Objects With SCF
Commands (page 1 of 2)
Task
X25AM Subsystem
WAN Subsystem
Add I/O processes*
No
Yes
Add subdevices
Yes
No
Alter I/O processes
No**
Yes
Alter lines
Yes
No
X25AM Configuration and Management Manual—523424-004
4 -9
Commands Supported by the X25AM Subsystem
SCF Commands for the X25AM Subsystem
Table 4-2. Configuring and Managing X25AM Objects With SCF
Commands (page 2 of 2)
Task
X25AM Subsystem
WAN Subsystem
Alter subdevices
Yes
No
Monitor I/O processes
No
Yes
Monitor lines
Yes
No
Monitor subdevices
Yes
No
* Adding an I/O process effectively adds an X25AM line
**You can switch an X25AM I/O process to another path, and you can make the backup processor the primary
processor
Commands Supported by the X25AM
Subsystem
This section describes the SCF commands supported by the X25AM subsystem (see
Table 4-3). For information about commands supported by other subsystems, see the
SCF manual for the specific subsystem, or see the SCF Reference Manual for GSeries RVUs or SCF Reference Manual for H-Series RVUs.
You can receive detailed syntax information on the X25AM object types and the
commands that apply to them when you enter the following SCF command:
-> HELP X25AM object-type [ command ]
For more detailed information about the online help facility, see the SCF Reference
Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs.
Table 4-3. SCF Commands Supported by X25AM Subsystem (page 1 of 2)
Command
PROCESS
ABORT
LINE
SU
X
X
ADD
X
ALLOWOPENS
X
X
ALTER
X
X
DELETE *
X
DISCONNECT
X
INFO
X
X
NAMES
X
X
PRIMARY
X
X
START
X
X
STATS
X
X
STATUS
X
X
X25AM Configuration and Management Manual—523424-004
4- 10
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. Commands that
request information or status but that do not affect operation are nonsensitive.
Only a user who has super-group access, the owner of the subsystem, or a member of
the group of the owner of the subsystem can issue a sensitive command.
The owner of a subsystem is the user who started that subsystem (or any user whose
application ID is the same as the server ID—the result of a PROGID option that
requires super-group access). Anyone can issue a nonsensitive command.
The following SCF commands for the X25AM subsystem are sensitive:
ABORT
ADD
ALLOWOPENS
ALTER
DELETE
DISCONNECT
PRIMARY
START
STOP
STOPOPENS
SWITCH
TRACE
The following SCF commands for X25AM are nonsensitive; you use them to determine
the status of SCF or to display information about an object.
INFO
NAMES
STATS
STATUS
VERSION
X25AM Configuration and Management Manual—523424-004
4- 11
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.
LINE line-name | SU su-name
designates the line or subdevice to be aborted. If you omit line-name or suname, the assumed object is aborted (for details about the ASSUME command,
see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for
H-Series RVUs). The objects you can abort are lines and subdevices.
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.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected. ALL specifies that the
named object and the subordinate objects are affected. If you omit subtype, ALL
is assumed.
Examples of the ABORT Command
The following command aborts the line $X25P1 as well as the subdevices on that line:
-> ABORT LINE $x25p1, SUB
The following command aborts the subdevice $X25P1.#TERM:
-> ABORT SU $x25p1.#term
The following command is a quick procedure that aborts a line and all the subdevices
on it; it has the same effect as the first example.
-> ABORT LINE $x25p1, SUB ALL
X25AM Configuration and Management Manual—523424-004
4- 12
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.
If you are terminating both a line and its subordinate subdevices, SCF terminates
the subdevices first and the line second.
X25AM supports the SUB option only for the LINE object type.
ADD Command
The ADD command defines a subdevice for an X25AM line. This is a sensitive
command.
To make persistent changes to an X25AM line, you must issue the ADD DEVICE
command through the WAN subsystem. The WAN subsystem stores changes,
additions, and deletions in the Management Information Base (MIB). Refer to the WAN
Subsystem Configuration and Management Manual.
Command Syntax for the ADD Command
Syntax:
ADD [ / OUT file-spec / ] [ 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.
SU su-name
designates the subdevice to be added. If you omit su-name, the assumed object is
added (refer to the ASSUME command in the SCF Reference Manual for G-Series
RVUs or SCF Reference Manual for H-Series RVUs). You can only add
subdevices.
LIKE object-name
identifies an existing object whose attribute values are adopted by the subdevice
being created. object-name must specify an existing object of the same type.
X25AM Configuration and Management Manual—523424-004
4- 13
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.
{ DEVTYPE ( integer,integer ) }
{ PROTOCOL { ITI | NAM | PTP | QLLC } }
{ RECSIZE
integer }
[ ACCEPTCHG
{ ON | OFF } ]
[ BCUG { integer | RESET } ]
[ BPADPARMS { ( integer,integer
[ integer,integer ]...) | RESET } ]
[ CPADPARMS { ( integer,integer
[ integer,integer ]...) | RESET } ]
[ CUD { “hex string” | RESET } ]
[ CUG { integer | RESET } ]
[ CUGTYPE { BASIC | EXT | BASICOA | EXTOA } ]
[ DDNPREC { integer | RESET } ]
[ DDNSERVICE { BASIC | STANDARD } ]
[ DESTADDR { “address” | RESET } ]
[ LOCALADDREXT { “address” | RESET } ]
[ LOCALADDREXTTYPE integer ]
[ NEGOTIATE { PKTSIZE | L3WINDOW | THRUPUT... } ]
[ NONEGOTIATE { PKTSIZE | L3WINDOW | THRUPUT... } ]
[ NULLFILL { ON | OFF } ]
[ PAGE6520BLKSIZE integer ]
[ PARITY { EVEN | ODD | NONE } ]
[ PARITYCHK { ON | OFF } ]
[ PORT integer ]
[ PRICALL { ON | OFF } ]
[ PVC { integer | RESET } ]
[ REMOTEADDREXT { “address” | RESET } ]
[ REMOTEADDREXTTYPE integer ]
[ REMOTENET { DATANET | DATAPAC | DATEXP | DDN | DDXP | PSS |
TELENET | TRANSPAC | TWINET | TYMNET | UNINET |
X25 | X25NP | X25UD | X25XA | X25SA } ]
[ REVERSECHG { ON | OFF } ]
[ REXMITTIMEOUT time ]
[ RPOA { integer | ( integer [, integer ]... ) | RESET } ]
[ THRUPUT ( integer,integer ) ]
[ TRANSITDELAY { time | RESET } ]
X25AM Configuration and Management Manual—523424-004
4- 14
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.#term, &
-> DESTADDR “11113333”,PORT 2
The following command adds an SU with the ITI protocol:
-> ADD SU $x25p1.#term, PROTOCOL ITI, DEVTYPE (6,0), &
-> RECSIZE 80, BCUG 125
The following command adds an SU named $X25S1.#TERM (use the INFO command
that follows the ADD command to check that your changes have been entered):
-> ADD SU $x25s1.#term, PROTOCOL ITI, DEVTYPE (6,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
-> INFO SU $x25s1.#term, DETAIL
The following command adds an SU with the QLLC protocol (use the INFO SU
command with the detail option that follows the ADD command to check the SU):
-> ADD SU $x25p1.#term, PROTOCOL QLLC, DEVTYPE (58,20), &
-> RECSIZE 80, TRANSITDELAY 1.0
-> INFO SU $x25p1.#term, DET
The following series of commands adds an SU with the NAM protocol, aborts the SU,
alters the RECSIZE of the SU then lets you check that your change was made:
-> ADD SU $x25s1.#term, PROTOCOL NAM, DEVTYPE (63,0), &
-> RECSIZE 80, TRANSITDELAY 1.0
-> ABORT SU $x25s1.#term
-> ALTER SU $x25s1.#term, RECSIZE 60
-> INFO SU $x25s1.#term, DETAIL
Considerations for the ADD Command
•
•
•
The maximum number of subdevices for an X25AM line is 510.
You cannot use the ADD command to add a line. A line is created when the I/O
process that controls it is configured using the SCF ADD DEVICE command to the
WAN subsystem. For information about configuring an I/O process, see Task 5:
Add an X25AM I/O Process on page 3-7.
When you add a subdevice, it is started automatically.
X25AM Configuration and Management Manual—523424-004
4- 15
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.
If you use the LIKE option, you must enter it before you enter any attributespec. The LIKE option creates another SU with the same attributes as the one you
name. The example below shows the LIKE option:
-> ADD SU $x25p1.#term2,LIKE $x25p1.#term, PORT 2
•
•
X25AM does not support the entry of multiple object names.
If you add an SU and realize you have made an error, use the STOP command to
stop the SU, and then use the ALTER command. After you fix the problem, use the
START command to restart the SU.
ALLOWOPENS Command
The ALLOWOPENS command allows opens to be issued to a subdevice. This
command reverses the effect of a STOPOPENS command. This is a sensitive
command.
Command Syntax for the ALLOWOPENS Command
Syntax:
ALLOWOPENS [ / 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 line or subdevice that is allowed to have opens issued to it. If you
omit line-name or su-name, the assumed object can have opens issued to it
(for details about the ASSUME command, see the SCF Reference Manual for GSeries RVUs or SCF Reference Manual for H-Series RVUs).
X25AM Configuration and Management Manual—523424-004
4- 16
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.#TERM and then
reverses the action of the STOPOPENS command:
-> STOPOPENS SU $x25p1.#term
-> ALLOWOPENS SU $x25p1.#term
The following command allows the subdevices on the line named $X25P1 to be
opened but does not allow the line itself to be opened:
-> ALLOWOPENS LINE $x25p1, SUB ONLY
Considerations for the ALLOWOPENS Command
•
•
•
If you use the object-type LINE, the SUB option must be present and it must be
SUB ONLY, which indicates that all the subdevices subordinate to the named line,
but not the line itself, are to be affected by the command.
X25AM does not support the SEL option.
X25AM supports the SUB option only for the LINE object type.
ALTER Command
The ALTER command changes the values of the attributes of a line or subdevice. This
command changes only the specified attributes of the target line(s) or subdevice(s).
This is a sensitive command.
To make persistent changes to an X25AM line, you must issue the SCF ALTER
command through the WAN subsystem. Refer to the WAN Subsystem Configuration
and Management Manual.
Note. Previously, the SCF ALTER CPADPARMS command on an X25AM line or subdevice did
not change the following PAD parameters: 2 (echo), 3 (forwarding char), and 13 (system LF).
These parameters can now be altered using SCF.
X25AM Configuration and Management Manual—523424-004
4- 17
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. If you omit the
line-name or su-name, SCF alters the attributes of the assumed object (for
information about the ASSUME command, see the SCF Reference Manual for GSeries RVUs).
LIKE object-name
identifies an existing object whose attribute values are adopted by the object being
created. object-name must specify an existing object of the same type.
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.
X25AM Configuration and Management Manual—523424-004
4- 18
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 ]... ) | RESET } ]
[ CALLINGADDR { ON | OFF } ]
[ CALLS { NONE | INCOMING | OUTGOING | TWOWAY } ]
[ CHARACTERSET { EBCDIC | ASCII } ]
[ CLOCKMODE { DCE | DTE } ]
[ CLOCKSPEED CLOCKnnnn ]
[ CPADPARMS { ( integer , integer
[ integer , integer ]... ) | RESET } ]
[ CUG { integer | RESET } ]
[ CUGTYPE { BASIC | BASICOA | EXT | EXTOA ]
[ DDNPREC { integer | RESET } ]
[ DDNSERVICE { BASIC | STANDARD } ]
[ DEBUG { ON | OFF } ]
[ DSRTIMEOUT time ]
[ EMSFORFRMR integer ]
[ EXTFORMAT { ON | OFF } ]
[ FRAMEMODE { DCE | DTE } ]
[ IDLETIMEOUT time ]
[ INTERFACE { RS232 | RS422 | V25 } ]
[ L3MOD integer ]
[ L3WINDOW integer ]
[ NETID { DATANET | DATAPAC | DATEXP | DDN | DDXP | PSS |
TELENET | TRANSPAC | TWINET | TYMNET | UNINET |
X25 | X25NP | X25SA | X25UD | X25XA } ]
[ PAGE6520BLKSIZE integer ]
[ PROGRAM file-spec ]
[ PVCRANGE { ( integer , integer ) | RESET } ]
[ RETRIES integer ]
[ RPOA { [ ( ] integer
[ , integer , ... ] [ ) ] | RESET } ]
[ SRCADDR { address | RESET } ]
[ SVCRANGE { ( integer [ , integer ] ) | RESET } ]
[ SYNCS integer ]
[ T1TIMEOUT time ]
[ THRESHOLD integer ]
[ TRANSITDELAY { time | RESET } ]
X25AM Configuration and Management Manual—523424-004
4- 19
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 ]... ) | RESET } ]
[ CUD { “hex string” | RESET } ]
[ CUG { integer | RESET } ]
[ CUGTYPE { BASIC | BASICOA | EXT | EXTOA } ]
[ DDNPREC { integer | RESET } ]
[ DDNSERVICE { BASIC | STANDARD } ]
[ DESTADDR { address | RESET } ]
[ DEVTYPE ( integer , integer ) ]
[ LOCALADDREXT { address | RESET } ]
[ LOCALADDREXTTYPE integer ]
[ NEGOTIATE { item | ( item [, item ]... ) } ]
[ NONEGOTIATE { item | ( item [, item ]... ) } ]
[ NULLFILL { ON | OFF } ]
[ PARITY { EVEN | ODD | NONE } ]
[ PARITYCHK { ON | OFF } ]
[ PORT integer ]
[ PRICALL { ON | OFF } ]
[ PROTOCOL { ITI | NAM | PTP | QLLC } ]
[ PVC { integer | RESET } ]
[ RECSIZE integer ]
[ REMOTEADDREXT { address | RESET } ]
[ REMOTEADDREXTTYPE integer ]
[ REMOTENET { DATANET | DATAPAC | DATEXP | DDN | DDXP | PSS |
TELENET | TRANSPAC | TWINET | TYMNET | UNINET |
X25 | X25NP | X25UD | X25XA | X25SA } ]
[ REXMITTIMEOUT time ]
[ REVERSECHG { ON | OFF } ]
[ RPOA { [ ( ] integer
[ , integer , ... ] [ ) ] | RESET } ]
[ THRUPUT ( integer , integer ) ]
[ TRANSITDELAY { time | RESET } ]
Examples of the ALTER Command
The following command alters the line named $X25P1, including the SVCRANGE, the
PVCRANGE, and the T1TIMEOUT value:
-> ALTER LINE $x25p1, SVCRANGE (41,50), PVCRANGE (1,2), &
-> T1TIMEOUT 10
X25AM Configuration and Management Manual—523424-004
4- 20
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. For example, if the CPADPARMS are set to
(1,1 2,15 3,2 4,0 13,0) and you want to change 13,0 to 13,4 and keep the remaining values the
same, then you use the command ALTER SU $X25P1.#TERM, CPADPARMS
(1,1 2,15 3,2 4,0 13,4). Otherwise, if you use ALTER SU $X25P1.#TERM, CPADPARMS
(13,4), you will lose your other values.
The following command resets the BCUG for the line named $X25P1:
-> ALTER LINE $x25p1, BCUG RESET
The following command alters CUG and CUGTYPE for the line named $X25P1:
-> ALTER LINE $x25p1, CUG 200, CUGTYPE EXTOA
The following command resets the CUG for the line named $X25P1:
-> ALTER LINE $x25p1, CUG RESET
The following command alters the RPOA for the line named $X25P1:
-> ALTER LINE $x25p1, RPOA (100, 200, 300)
The following command alters the BCUG for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, BCUG 200
The following command resets the BCUG for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, BCUG RESET
The following command alters the CUG for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, CUG 125
The following command resets the CUG for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, CUG RESET
The following command alters the RPOA for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, RPOA (200, 400, 600)
The following command alters the RPOA for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, RPOA 150
The following command resets the RPOA for the subdevice named $X25P1.#TERM:
-> ALTER SU $x25p1.#term, RPOA RESET
X25AM Configuration and Management Manual—523424-004
4- 21
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.
After you alter a line with the ALTER command, use the INFO command to check
the attributes, and then restart the line with the START command.
Use the INFO, DETAIL command to check which attributes are alterable. Attributes
with an asterisk (*) on the left side are alterable.
You must enter the LIKE object-name option before you enter any
attribute-spec.
NEGOTIATE can be applied only to switched virtual circuit (SVC) subdevices. If
you configure a permanent virtual circuit (PVC) incorrectly with the NEGOTIATE
attribute, X25AM does not issue an error message. However, the NEGOTIATE
attribute will have no effect on the subdevice.
The following is a list of X25AM I/O process modifiers for which there is no equivalent
SCF line attribute:
AUTOLOAD
L2DOWNLINE
NOSTRIPPARITY
DISABLEPVCOUTOFORDER
L2NODISC
PACKETSIZE
DRTIMEOUT
L2WINDOW
POOLPAGES
EMSFORCLEAR
L3RECVTHRUPUT
REPORTDIRECT
ENABLEPVCOUTOFORDER
L3SENDTHRUPUT
Rxx
ENABLECALLEDADDREXT
MAXIOSIZE
STRIPPARITY
EXTENDEDPOOLPAGES
NOAUTOLOAD
TYPE
FIFO
NOEMSFORCLEAR
Txx
IDLECMDRR
NOL2DOWNLINE
UNSOLF
IDLERESPRR
NOREPORTDIRECT
X25V
L2DISC
Table 4-4 on page 4-23 lists the attributes that you can configure with either the SCF
ALTER DEVICE command (X25AM I/O process modifiers) to the WAN subsystem or
the SCF ALTER LINE command (SCF line attributes) to the X25AM subsystem.
X25AM Configuration and Management Manual—523424-004
4- 22
SCF Commands for the X25AM Subsystem
Considerations for the ALTER Command
Table 4-4. SCF Line Attributes and X25AM I/O Process Modifiers
X25AM I/O Process Modifier
SCF Line Attribute
CALLUSERDATA
CUD
CIRCUITS
PVCRANGE
CLOCKnnnn
CLOCKSPEED
DCE
FRAMEMODE
DCECLOCK
CLOCKMODE
DSRTIMER
DSRTIMEOUT
DTE
FRAMEMODE
DTECLOCK
CLOCKMODE
EXTFORMAT
EXTFORMAT
INCOMINGCALLS
CALLS
LINEQUALITYTHRESHOLD
THRESHOLD
L2IDLETIMEOUT
IDLETIMEOUT
L2RETRIES
RETRIES
L2TIMEOUT
T1TIMEOUT
L3MOD8
L3MOD
L3MOD128
L3MOD
L3WINDOW
L3WINDOW
NETID
NETID
NOCALLS
CALLS
NOCALLUSERDATA
CUD
NOEXTFORMAT
EXTFORMAT
NOINCOMINGCALLS
CALLS
NOOUTGOINGCALLS
CALLS
NOSENDCALLINGADDR
CALLINGADDR
OUTGOINGCALLS
CALLS
PAGE6520BLKSIZE
PAGE6520BLKSIZE
PROGRAM
PROGRAM
RS232
INTERFACE
RS422
INTERFACE
SENDCALLINGADDR
CALLINGADDR
TWOWAYCALLS
CALLS
V25
INTERFACE
X25AM Configuration and Management Manual—523424-004
4- 23
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. If you
omit line-name or su-name, SCF deletes the assumed object (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 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 DELETE Command
The following command deletes the subdevices on the line named $X25P1, but not the
line itself:
-> DELETE LINE $x25p1, SUB ONLY
The following command deletes the subdevice named $X25P1.#TERM:
-> DELETE SU $x25p1.#term
X25AM Configuration and Management Manual—523424-004
4- 24
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.#term
•
•
•
If you use the object-type LINE, you must also use the SUB option and set to
SUB ONLY, which indicates that all the subdevices subordinate to the named line,
but not the line itself, are to be affected by the command.
X25AM does not support the SEL option.
X25AM supports the SUB option only for the LINE object type.
DISCONNECT Command
The DISCONNECT command breaks the connection between two or more subdevices.
If the subdevice presently has a call established, DISCONNECT will force a clear
request to be sent and the call will be cleared. This is a sensitive command.
Command Syntax for the DISCONNECT Command
Syntax:
DISCONNECT [ / OUT file-spec / ] [ SU su-name ]
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
SU su-name
designates the subdevice to be disconnected. If you omit su-name, the assumed
subdevice is disconnected (for information about the ASSUME command, see the
SCF Reference Manual for G-Series RVUs or SCF Reference Manual for H-Series
RVUs).
Examples of the DISCONNECT Command
The following command breaks the connection between an assumed object and an SU
named $X25P1.#TERM1:
-> DISCONNECT SU $x25p1.#term1
Consideration for the DISCONNECT Command
•
X25AM supports the use of only the first su-name; X25AM does not support the
use of more than one su-name.
X25AM Configuration and Management Manual—523424-004
4- 25
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. If you omit line-name or
su-name, SCF displays the attribute values for the assumed object (for information
about the ASSUME command, see the SCF Reference Manual for G-Series RVUs
or SCF Reference Manual for H-Series RVUs).
DETAIL
causes detailed information to be displayed. If you omit DETAIL, you only one line
of information for each object.
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.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected. ALL specifies that the
named object and the subordinate objects are affected. If you omit subtype, ALL
is assumed.
Display for the INFO LINE Command
The format of the display for the INFO LINE command without the DETAIL option is:
X25AM Info
Name
$X25P1
LINE
L3Window
2
PacketSize
256
Type
Retries
(61,63)
10
FrameMode
DTE
X25AM Configuration and Management Manual—523424-004
4- 26
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.
FrameMode
shows whether this is a DCE or DTE station.
The format of the display for the INFO LINE command with the DETAIL option is:
X25AM Detail Info LINE
$X25AZ1
*CallingAddr.. ON
*Threshold.. 500
*CharacterSet.
Debug........ OFF
*SYNCS...... 3
*DSRTimeout...
*Extformat.... OFF
*L3window... 15
*IdleTimeout..
*Interface.... RS232
*L3mod...... 128
*PVCrange.....
*Netid........ X25XA
*Retries.... 10
*SVCrange.....
*CUG..........
*Framemode.. DTE
*T1Timeout....
*CUGType...... BASIC
*BCUG.......
*Transitdelay.
*Calls........ TWO WAY
PacketSize. 512
Type.........
*Clockmode.... DCE
*Clockspeed. CLOCK600
*SrcAddr......
*Program...... $SYSTEM.CSS02.C1096QF1
*EmsForFrmr... 0
*RPOA..........
*Bpadparms....
*Cpadparms....
EBCDIC
0:20.00
0:15.00
(
1,510 )
0:03.00
(61,63)
Note. In the displays for the INFO command, an asterisk (*) indicates that the value of the
attribute can be changed with the ALTER command.
Blank fields in the display above indicate either that they were never set or that they
have been reset.
X25AM Configuration and Management Manual—523424-004
4- 27
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. 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 the SU can receive or transmit. This value
must be in the range 1 through 4095.
Destaddr
specifies the network address of the remote device, which the subdevice uses as
the called address in outgoing call request packets.
X25AM Configuration and Management Manual—523424-004
4- 28
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.......
*DestAddr.....
*Negotiate....
Associateline
*LocalAddrExt.
*RemoteAddrExt
*CUD..........
*RPOA..........125 , 300 , 5000
*Bpadparms....
*Cpadparms....
( 6,0 )
NONE
ITI
OFF
OFF
*Recsize..........
*Pricall..........
*ParityChk........
*Thruput..........
*RemoteNet........
*Transitdelay.....
*LocalAddrExtType.
*RemoteAddrExtType
*Page6520BlkSize
80
OFF
OFF
( 4,4 )
X25XA
0
0
256
Blank fields in the display above indicate either that they were never set or that they
have been reset.
Examples of the INFO Command
The following command gives you information about the line named $X25P1:
-> INFO LINE $x25p1
The following command gives you detailed information about the line named $X25P1:
-> INFO LINE $x25p1,DETAIL
The following command gives you information about the subdevice named
$X25P1.#TERM:
-> INFO SU $x25p1.#term
The following command gives you detailed information about the subdevice named
$X25P1.#TERM:
-> INFO SU $x25p1.#term,DETAIL
The following command gives you information about the subdevices named
$X25P1.#term1 and $X25P1.#term2:
-> ASSUME LINE $x25p1
-> INFO SU (#term1, #term2)
X25AM Configuration and Management Manual—523424-004
4- 29
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. This is a nonsensitive command.
Command Syntax for the NAMES Command
Syntax:
NAMES [ / OUT file-spec / ] [ object-spec ]
[ , SUB [ subtype ] ]
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
object-spec
designates the device names to be displayed. If you omit the object-spec, the
subordinate object names and types of the assumed object are displayed (for
information about the ASSUME command, see the SCF Reference Manual for GSeries RVUs or SCF Reference Manual for H-Series RVUs).
SUB [ subtype ]
selects the subordinate objects that the NAMES command affects. subtype can
be a subordinate object type or one of the keywords ONLY or ALL.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected. ALL specifies that the
named object and the subordinate objects are affected. If you omit subtype, ALL
is assumed.
X25AM Configuration and Management Manual—523424-004
4- 30
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.#TERM
The format of the display for the NAMES LINE command is:
X25AM Names LINE $X25P1
LINE
$X25P1
Examples of the NAMES Command
The following command gives you the names of the subdevices for the line named
$X25P1:
-> NAMES $x25p1
The following command also gives you the names of the subdevices for the line named
$X25P1:
-> NAMES $x25p1.#*
Considerations for the NAMES Command
•
•
X25AM does not support the SEL option.
X25AM supports the SUB option only for the LINE object type.
X25AM Configuration and Management Manual—523424-004
4- 31
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.
Command Syntax for the PRIMARY Command
Syntax:
PRIMARY [ / OUT file-spec / ]
[ PROCESS process-name | LINE line-name ] , number
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
PROCESS process-name | LINE line-name
designates the process or line that is to have its primary and backup CPUs
switched. If you omit process-name or line-name, the assumed object is
switched (for information about the ASSUME command, see the SCF Reference
Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs).
number
is the number of the CPU of the backup process.
Examples of the PRIMARY Command
The following command causes the backup CPU (CPU 1) to become the primary CPU
for the PROCESS object named $X25P1 (the primary process at the time you issue
the command becomes the backup process after you execute the command):
-> PRIMARY PROCESS $x25p1, 1
The following command causes the backup CPU (CPU 1) to become the primary CPU
for the LINE object named $X25P1 (the primary process at the time you issue the
command becomes the backup process after you execute the command):
-> PRIMARY LINE $x25p1, 1
X25AM Configuration and Management Manual—523424-004
4- 32
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.
When using Parallel Library TCP/IP the system manager can force a switch of the
processor or PATH (but not at the same time). To switch the processor (but not the
PATH) use the PRIMARY PROCESS command for X25AM.
For Conventional TCP/IP, standard IOP, and TCP/IP configuration (IOP primary,
backup processes, and TCP/IP – ALT TCP/IP processes configured on the same
CPU pair), the PRIMARY command switches the processor to the backup process
and simultaneously switches the PATH.
For other configurations of IOP and TCP/IP, the behavior might be different. The
CONMGR takes decisions on the path to use regardless of the request sent by the
IOP. In this case, a processor switch occurs but the PATH switch might not.
START Command
The START command initiates the operation of an object. The successful completion
of the START command leaves the object in the STARTED state. This is a sensitive
command.
To start an X25AM line for the first time, you must first issue the SCF START DEVICE
command to the WAN subsystem. Refer to the Task 6: Start an X25AM I/O Process on
page 3-8.
After the I/O process is started, you can start the line that it controls using the START
LINE command to the X25AM subsystem.
Command Syntax for the START Command
Syntax:
START [ / 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.
X25AM Configuration and Management Manual—523424-004
4- 33
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.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected. ALL specifies that the
named object and the subordinate objects are affected. If you omit subtype, ALL
is assumed.
Examples of the START Command
The following command starts the line named $X25P1. Use the STATUS LINE
command that follows to check the state of the line:
-> START LINE $x25p1
-> STATUS LINE $x25p1
The following command starts the subdevice named $X25P1.#TERM:
-> START SU $x25p1.#term
Considerations for the START Command
•
•
•
•
•
X25AM does not support the SEL option.
A non-error completion of the START command indicates only that the subsystem
was able to initiate processing for the START operation. It does not necessarily
indicate that the operation completed successfully.
This command downloads the CLIP code for the SWAN concentrator. Refer to the
WAN Subsystem Configuration and Management Manual.
X25AM supports the SUB option only for the LINE object type.
When you use the SUB ALL option, all subdevices on that line also start.
X25AM Configuration and Management Manual—523424-004
4- 34
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. The X25AM lines are listed in the “Names” column. To get the
names of the subdevices, enter NAMES LINE $line-name, SUB.
Command Syntax for the STATS Command
Syntax:
STATS [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , RESET ] [ , 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 statistical information you wish to display. If
you omit the line-name or su-name, the statistics for the assumed objects are
displayed (for information about the ASSUME command, see the SCF Reference
Manual for G-Series RVUs or SCF Reference Manual for H-Series RVUs).
RESET
if present, restores all the statistics counters to their initial values after the statistics
are displayed.
RESET is a sensitive option. That is, it can be specified in a STATS command only
by a user with super-group access, the owner of a subsystem, or a member of the
same group as the owner of the subsystem.
The owner of the subsystem is the user who started that subsystem or any user
whose application ID is the same as the server ID (this identical ID is the result of a
PROGID option that requires super-group access).
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.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected.
X25AM Configuration and Management Manual—523424-004
4- 35
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.034
Modem Error
0
10/14/99
Modem Overrun
0
[ Packet Level Information ]
Send
Rcvd
Data
0
0
Call
0
0
Send
Rcvd
0
0
Total Sent
0
Clear Reset Rstrt Intrp
Diag
0
0
0
0
0
0
0
0
0
0
[ Confirmation Packets ]
0
0
0
0
0
0
0
0
Total Rcvd
0
Invalids Rcvd
RR
0
0
0
RNR
0
0
REJ
0
0
Discarded
0
[ Frame Level Information ]
For CLIP Subsystem:
I^P I^NOP
RR
Send
0
0
0
Rcvd
0
0
0
FCS 0
T1 0
Size
RNR
0
0
[ CLIP Errors ]
Modem 0
Length 0
Nobuf 0
Addrs 0
510
REJ
0
0
SREJ
0
0
SABM
0
0
Overruns 0
Rvc Abrt 0
DISC
0
0
FRMR
0
0
UA
0
0
DM
0
0
[ DRIVER info ]
BCC Errs 0
Frames 0
No Buffs 0
Errors 0
[ Buffer Pool Information in pages ]
In use 4
High Water 5
Failures
0
Note. For statistical information about the CLIP, refer to the statistics listed in the display.
The statistics are described below in the order in which they appear on the screen. The
information listed in the statistics display apply only after the last RESET and/or system
restart.
Resettime
is the date and time the last reset operation was performed.
Sampletime
is the current date and time.
Line Quality
shows the value SCF uses to check the quality of the transmission. This value is a
percentage and is calculated as a function of the SCF THRESHOLD value.
X25AM Configuration and Management Manual—523424-004
4- 36
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.
You may also wish to check console messages for line-quality changes.
You can change the threshold value with the X25AM I/O process modifier
LINEQUALITYTHRESHOLD (ALTER DEVICE command) or the THRESHOLD
attribute (ALTER LINE command). For information about the THRESHOLD
attribute, see Section 5, Attribute Descriptions.
Modem Error
shows the total number of modem-signal handshaking errors.
Modem Overrun
shows the total number of frames received that were longer than the maximum
frame size specified.
Packet-Level Information
The information in this field is divided into statistics for packets sent and for packets
received.
Data
shows the number of data request packets sent and received.
Call
shows the number of call request packets sent and received.
Clear
shows the number of clear request packets sent and received.
Reset
shows the number of reset request packets sent and received.
Rstrt
shows the number of restart request packets sent and received.
Intrp
shows the number of interrupt request packets sent and received.
X25AM Configuration and Management Manual—523424-004
4- 37
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.25 uses the packets below to acknowledge the implementation of a previous
request.
Call
shows the number of call confirmation packets sent and received.
Clear
shows the total number of clear confirmation packets sent and received.
Reset
shows the total number of reset confirmation packets sent and received.
Restrt
shows the total number of restart confirmation packets sent and received.
Intrp
shows the number of interrupt confirmation packets sent and received.
Frame-Level Information
The section contains frame-level statistics that are meaningful for the CLIP on X25AM
lines. The frame-level send and receive information section consists of the following
fields:
I^P
shows the number of I-frames with the poll bit set that have been sent and
received.
X25AM Configuration and Management Manual—523424-004
4- 38
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.
REJ
shows the number of reject (REJ) frames sent and received.
SREJ
shows the number of reject frames (SREJ) sent and received. This frame is used
by the DTE or DCE to request retransmission of I-frames with the frame numbered
N(R).
SABM
shows the number of Set Asynchronous Balance Mode (SABM) frames sent and
received.
DISC
shows the number of disconnect (DISC) frames sent and received. DISC is used
by the DTE/DCE to indicate that the DTE/DCE is suspending operation.
FRMR
shows the number of Frame Reject frames (FRMR) sent and received.
UA
shows the number of Unnumbered Acknowledgment (UA) frames sent and
received.
DM
shows the number of Disconnect Mode (DM) frames sent and received.
X25AM Configuration and Management Manual—523424-004
4- 39
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. This counter does not
relate to file-system error 140 (which can be returned due to modem errors, calls
cleared or denied, and so on).
Length
shows the number of good frames received with an invalid length for the LAPB
protocol.
Overruns
shows the number of receiver overruns. This condition generally indicates that the
line is faster than the X.25 CLIP can handle.
T1
shows the number of frames that timed out before an acknowledgment was
received.
Nobuf
shows the number of buffer failures in the level-2 receive queue.
Addrs
shows the number of good frames received with bad address fields.
Rvc Abrt
shows the number of aborted frames detected by the CLIP.
Driver Information
The information in this field shows the number of errors in received frames. This field
includes the driver information listed below:
BCC Errs
shows the total number of Block-Check Character (BCC) errors detected in the
driver frames received.
X25AM Configuration and Management Manual—523424-004
4- 40
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. This field contains the following information:
Size
shows the total size of the buffer.
In use
shows the number of pages of pool currently in use.
High Water
shows the maximum number of pages of pool used at any point.
Failures
shows the number of times the X25AM subsystem was forced to wait to secure
pool space.
Display for the STATS SU Command
The format of the display for the STATS SU command is:
X25AM STATS SU $X25P1.#TERM
Resettime 0:00:00.000
CircuitNum
12/31/74
MsgSends
0
Sampletime 8:08:51.015
MsgReceives
10/14/99
0
Note. The STATS SU command displays the current count of messages sent and received for
a particular circuit. For SVC, stats is the count between establishment to clearing of the circuit.
Once the circuit is cleared, the statistics are reset. For PVC, the count is between the addition
and deletion of the SU.
Resettime
is the date and time that the last reset operation was performed.
X25AM Configuration and Management Manual—523424-004
4- 41
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.#TERM
The following command shows statistics for the line named $X25P1:
-> STATS LINE $x25p1
Considerations for the STATS Command
•
•
X25AM does not support the SEL option.
X25AM supports the SUB option only for the LINE object type.
STATUS Command
The STATUS command displays information about the current state of lines and
subdevices, such as the dynamic state, the last error, and modifiable values of the
specified object. It also displays specific subsystem attributes and values. This is a
nonsensitive command.
Note. Version mismatches between X25AM and SCF may cause errors for the STATUS LINE
and STATUS SU commands under certain conditions.
To issue the STATUS 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
X25AM. The X25AM lines are listed in the “Names” column. To get the names of the
subdevices, enter NAMES LINE $linename, SUB.
X25AM Configuration and Management Manual—523424-004
4- 42
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. If you
omit line-name or su-name, the status of the assumed object is displayed (for
information about the ASSUME command, see the SCF Reference Manual for GSeries RVUs or SCF Reference Manual for H-Series RVUs).
DETAIL
if present, returns complete status information. If you omit DETAIL, you only a
single line of data for each object name.
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.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected. ALL specifies that the
named object and the subordinate objects are affected. If you omit subtype, ALL
is assumed.
Display for the STATUS LINE Command
The display for the STATUS LINE command without the DETAIL option has the
following format:
X25AM STATUS
Name
$X25P1
LINE
State
STARTED
PPID
( 0,3 )
BPID
( 1,4 )
I/O ADDR
( 0,4,3,0)
T
61
S Pa Track ID
63 A X017JJ
Name
is the name of the line object.
X25AM Configuration and Management Manual—523424-004
4- 43
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.
Pa
indicates the primary path to the CLIP.
Track ID
indicates the unique hardware identification of the SWAN concentrator (adapter).
The display for the STATUS LINE command with the DETAIL option has the following
format:
X25AM Detail Status Line $X25X
Preferred IP....... 192.168.005.084
Track ID.... X017JJ
CMG........
State....... STARTED
PPIN.......
LinkState...READY
LDEV.......
InUse....... NO
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....... ( 1,4 )
156
NumSU...... 0
510
Path....... A
ON
CTS........ ON
61
Sub-Type... 63
OFF
Alternate IP
indicates the alternate IP address used by the process.
BkpTrace
indicates whether the backup is being traced.
X25AM Configuration and Management Manual—523424-004
4- 44
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.
DSR
shows whether the Data Set Ready (DSR) signal is on or off.
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.
InUse
indicates if any line’s subdevice is opened.
LDEV
is the logical device number of the line.
LinkState
is the current state of the line (READY or NOT READY).
NumSU
is the number of SUs associated with this LINE object.
Path
indicates the primary path to the CLIP.
X25AM Configuration and Management Manual—523424-004
4- 45
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).
Type
is the type of the X25AM line. Only type 61 is allowed.
Display for the STATUS SU Command
The display for the STATUS SU command has the following format (The X25AM
subsystem does not support the DETAIL option.):
X25AM STATUS
Name
$X25P1.#TERM
SU
State
STARTED
DevType
6,0
Recsize
80
SUnum
2
Port
0
LCNnum
Name
is the name of the SU object.
State
is the current summary state of the SU object.
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-6 describes
the possible types and subtypes:
X25AM Configuration and Management Manual—523424-004
4- 46
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.
LCNnum
is the number of the logical channel assigned to the SU if the SU is assigned to a
PVC; this field is blank if the SU is assigned to an SVC and the circuit is not yet
established.
Examples of the STATUS Command
The following command gives you the status of the line named $X25P1:
-> STATUS LINE $x25p1
The following command gives you the detailed status of the line named $X25P1:
-> STATUS LINE $x25p1,DETAIL
The following command gives you the status of the subdevice named $X25P1.#TERM:
-> STATUS SU $x25p1.#term
Considerations for the STATUS Command
•
•
X25AM does not support the SEL option.
X25AM supports the DETAIL option and the SUB option only for the LINE object
type.
X25AM Configuration and Management Manual—523424-004
4- 47
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.
Command Syntax for the STOP Command
Syntax:
STOP [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , SUB [ subtype ] ]OUT file-spec
STOP [ / 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 to be stopped. If you omit the line-name or
su-name, the assumed object is stopped (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 the keyword ONLY.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected.
Examples of the STOP Command
The following command stops the line named $X25P1:
-> STOP LINE $x25p1
The following command stops the subdevice named $X25P1.#TERM:
-> STOP SU $x25p1.#term
Considerations for the STOP Command
•
•
•
To terminate an object immediately, use the ABORT command.
X25AM does not support the SEL option.
X25AM supports the SUB option only for the LINE object type.
X25AM Configuration and Management Manual—523424-004
4- 48
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. This is a sensitive command.
Command Syntax for the STOPOPENS Command
Syntax:
STOPOPENS [ / 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 line or subdevice that is to have its opens stopped. If you omit
line-name or su-name, the assumed object has its opens stopped (for
information about the ASSUME command, see the SCF Reference Manual for GSeries 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 the keyword ONLY.
If you name a subordinate object type, only objects of that type are affected. ONLY
specifies that only the subordinate objects are affected.
Examples of the STOPOPENS Command
The following command prevents anyone else from opening the subdevice named
$X25P1.#TERM after you issue it:
-> STOPOPENS SU $x25p1.#term
X25AM Configuration and Management Manual—523424-004
4- 49
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.
SWITCH Command
The SWITCH command causes a backup-path object to become the primary-path
object and, simultaneously, a primary-path object to become the backup-path object.
Path objects that can be switched between primary and backup are defined by each
subsystem. 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.
Command Syntax for the SWITCH Command
Syntax:
SWITCH [ / OUT file-spec / ]
[ PROCESS process-name | LINE line-name ] , PATH { A | B }
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
PROCESS process-name | LINE line-name
designates the process or line to be switched. If you omit process-name or
line-name, SCF switches the assumed object (for information about the
ASSUME command, see the SCF Reference Manual for G-Series RVUs or SCF
Reference Manual for H-Series RVUs).
PATH { A | B }
causes the specified line or process to switch to the other path.
X25AM Configuration and Management Manual—523424-004
4- 50
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.
For Conventional TCP/IP, standard IOP and TCP/IP configuration, (IOP primary,
backup processes, and TCP/IP– ALT TCP/IP processes configured on the same
CPU pair) the PATH does not switch and IOP continues to use the same PATH.
This command is not recommended for Conventional TCP/IP.
For Parallel TCP/IP, the command forces a PATH switch without changing the
processor. The specified PATH must be different from the current PATH.
TRACE Command
The TRACE command initiates, modifies, or terminates the trace mode on an X25AM
line. Using the TRACE command, you can request the capture of target-defined data
items, alter trace parameters, and end tracing. This is a sensitive command.
An SCF trace produces a trace file that you can display using the commands available
in the PTrace program. SCP creates the trace file. For information on using PTrace to
interpret a trace file, see Section 6, PTrace for the X25AM Subsystem.
Command Syntax for the TRACE Command
Syntax:
TRACE [ / OUT file-spec / ] [ LINE line-name ]
{ , STOP [ , BACKUP ]
{ [ , BACKUP
[ , COUNT count
[ , NOCOLL
[ , PAGES pages
[ , RECSIZE size
[ , SELECT select-spec
[ , TO file-spec
[ , WRAP
}
]
]
]
]
]
]
]
]... }
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
X25AM Configuration and Management Manual—523424-004
4- 51
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.
BACKUP
specifies that the backup process should receive the trace request. The object
must be running as a process pair if you use this syntax. If the primary process is
being traced when a takeover by the backup process occurs, the trace of the
process continues. However, in this case, most events being traced before the
process switch are no longer traced because the process being traced is no longer
the primary process. If you omit BACKUP, SCF assumes the primary process.
COUNT count
specifies the number of trace records that you want to capture. count is an integer
in the range -1 through 32767. If you omit COUNT or if count equals -1, records
accumulate until you stop the trace.
NOCOLL
indicates that the trace collector process should not be initiated. Some subsystems
might select this option automatically.
PAGES pages
designates how much space, in pages, you want to allocate in the extended data
segment used for tracing. You can specify PAGES only when you initiate a trace.
pages is an integer in the range 4 through 1024 or equal to 0 (zero). If you omit
PAGES or if pages equals 0, SCF assumes the default value of 64 pages.
RECSIZE size
specifies the length of the data in the trace data records. size is an integer in the
range 16 through 4050 or equal to 0 (zero). The length of the trace header, which
is 8 bytes, is not included in size. If RECSIZE is omitted or if size equals 0, the
default value of 120 bytes is assumed.
Using the default value of 120 bytes in a CLIP trace could result in data being
truncated. When starting a CLIP trace, RECSIZE should be the larger of 150 bytes
or the L3 packet size plus 4 to avoid CLIP trace data from being truncated. In order
to capture all Level 2 events, RECSIZE should be 256.
X25AM Configuration and Management Manual—523424-004
4- 52
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. SCF purges any old data
before it initiates a trace. If the file does not exist, SCF creates one with an extent
size of 100 pages for the primary extent and 20 pages for the secondary extents.
WRAP
specifies that when the trace file end-of-file mark is reached, trace data wraps
around to the beginning of the file and overwrites any data there.
Table 4-7. Select-Spec for a LINE object
Keyword
Mask Bits
Meaning
IOS
0
Trace frames IN/OUT
DR
1
Trace X.25 IOP driver
L2
2
Trace level-2 events
L3
3
Trace level-3 events
L4
4
Trace level-4 events
CLBI
10
Trace CLB inbound
CLBO
11
Trace CLB outbound
CLIPDI
16
Trace CLIP inbound frames
CLIPDO
17
Trace CLIP outbound frames
CLIPL2
21
Trace CLIP level-2 events
ALL
0-31
Trace all items
X25AM Configuration and Management Manual—523424-004
4- 53
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. For example, FUP SET TYPE U, CODE 830,
EXT (100,100), MAXEXTENTS 978, BUFFERSIZE 4096.
How to Use the TRACE Command to Troubleshoot X25AM
Problems
The following tips can help you use the TRACE command to troubleshoot X25AM
problems:
•
•
•
•
•
•
When recording trace data, use SELECT ALL if you want a general trace. If the
trace collector overruns, delete SELECT DR and SELECT IOS, to limit the traces
logged to the trace file only for the DRIVER or IOS modules.
The L2 option usually provides enough information to determine which end of the
line has a frame-level problem.
The L3 and L4 options usually provide enough information to determine whether
the application, the X25AM packet level, or the network packet level is causing the
problem. Look at the L3 and L4 levels first unless you strongly suspect a framelevel problem.
When you troubleshoot a problem on a specific logical channel number (LCN), use
the FILTER LCN option. If you do not know the failing LCN, use the FIND
command to look at logon requests. You can use FILTER SDN 0 and RECORD
AFTER time to find incoming calls. Or you can use FILTER PACKET CALLS to list
both incoming and outgoing call requests.
When troubleshooting a problem with an application, use the FILTER SDN option.
To find the subdevice number, use the SCF STATUS SU command to display
subdevice status.
SCF traces application requests and responses at Layer 4. SCF labels requests
L4^LCB^IN. SCF labels responses L4WRITELINK. Use Table 4-8 on page 4-55 to
interpret the parameters in user requests; file-system internals are not included in
the table. The application buffer is not traced, but data packets contain most of the
application buffer contents.
For information on how to format your trace using PTrace, see Section 6, PTrace for
the X25AM Subsystem.
X25AM Configuration and Management Manual—523424-004
4- 54
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. This is a
nonsensitive command.
Command Syntax for the VERSION Command
Syntax:
VERSION [ / OUT file-spec / ]
object-name
[ , DETAIL ]
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
object-name
designates the object whose version you want to display.
DETAIL
designates the complete version information that is to be returned for the specified
object. If you omit DETAIL, you will refer to only a single line of version information
for the object.
The information displayed by the VERSION command without the DETAIL option has
the following format:
VERSION \TOYS2.$X25P1: X25AM - T9060F40 - 25JUN1999 - X25AM
X25AM Configuration and Management Manual—523424-004
4- 55
F40
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.
25JUN1999 is the version process (VPROC) date. 25JUN1999 is the binder stamp
date, which is the date is the date the software modules were bound together.
GUARDIAN - T9050 - (Q06)
T9050 shows the version number of the NonStop operating system. Q06 is an
internal version number.
SCF KERNEL - T9082G02 - (12JUL99) (15JUN99)
T9082G02 shows the product and version number as the SCF kernel. 12JUL99 is
the VPROC date. 15JUN99 is the binder stamp date.
X25AM PM - T9323F40 - (09APR99) - F40_AAI
T9323F40 shows the product and version number of the X25AM SCF product
module. 09APR99 is the VPROC date. F40_AAI indicates its version and IPM ID.
Examples of the VERSION Command
The version level of a line is the same version level as the process.
Use the following command to view the version level of the line named $X25P1:
-> VERSION $x25p1
Use the following command to view the detailed version level of the line named
$X25P1:
-> VERSION $x25p1,DETAIL
X25AM Configuration and Management Manual—523424-004
4- 56
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.
ACCEPTCHG
specifies whether an incoming call requesting that the recipient pay the charges will be
accepted. The default value is Off. On means accept charges for incoming calls; Off
means do not accept charges for incoming calls.
Default:
Off
Range:
On or Off
Objects:
Subdevices
ASSOCIATELINE
specifies the X.25 line that Expand and SNAX use. This line name appears in the
display for the INFO SU command only if the device type is NAM or 63,0. This attribute
cannot be set through SCF.
You can set ASSOCIATELINE using the EXPAND I/O process modifier,
ASSOCIATEDEV. This EXPAND modifier associates the logical device name of a NAM
process with an Expand-over-NAM line-handler process. The ASSOCIATEDEV
modifier declares the logical device name of the NAM process. For more information
about the ASSOCIATEDEV modifier, see the Expand Configuration and Management
Manual.
Default:
None
Range:
Name of line
Objects:
Subdevices
X25AM Configuration and Management Manual—523424-004
5 -1
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. If you do not specify BPADPARMS, SCF uses the
line’s BPADPARMS. If the line's BPADPARMS are not specified either, then X25AM
uses the standard PADPARMS according to the NETID. RESET means to delete all
existing BPADPARMS assignments. No BPADPARMS value is assigned by default.
Default:
Any existing PADPARMS.
Range:
For a list of parameters supported by ITI, see the X25AM
Programming Manual. For descriptions of standard PAD
profiles, see Appendix D, Using the NETID Modifier.
Objects:
Subdevices and lines.
Note. If you alter the BPADPARMS or CPADPARMS and you have several pairs of parameters
already configured, you must enter all the pairs or they are reset. For example, if your
configuration has the pairs of parameters (1,1 2,15 4,0 13,0) and you want to alter 13,0 to 13,4,
you must enter all the other pairs of parameters.
CALLINGADDR
causes the X25AM subsystem to send either an SRCADDR or a null calling address in
outgoing call request packets. Off means send a null address. Use a null address with
networks that fill in the DTE address when the DTE transmits a call request with a null
calling address. On means send SRCADDR as the calling address.
Default:
On
Range:
On or Off
Objects:
Lines
X25AM Configuration and Management Manual—523424-004
5 -2
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.
Default:
DTE
Range:
DCE, DTE
Objects:
Lines
DCE disables the communications line interface processor (CLIP) clock; no internal
clock is generated.
DTE enables the CLIP clock; an internal clock is generated and made available on the
interface clock pins. Use DTE if your system uses the clock from the DTE rather than
the clock generated by the DCE (or if the DCE clock is not available) as in the case of
a modem eliminator.
CLOCKSPEED CLOCKnnnn
sets the speed of the line.
Default:
600 (no leading 0)
Range:
600, 1200, 2400, 4800, 9600, 19200, 38400, 56000, 115200
Objects:
Lines
Caution. It is recommended that you do not set CLOCKSPEED greater than the maximum
speed of 19200 BAUD when using an RS232 interface; speeds over 19200 BAUD can cause
line or frame errors
CPADPARMS
specifies the conversational-mode X.3 PAD parameters. You must specify the value as
pairs of integers (the parameter number and its value). This attribute is valid only if the
PROTOCOL attribute value is ITI. If you do not specify the SU’s CPADPARMS, SCF
X25AM Configuration and Management Manual—523424-004
5 -3
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. The
(CUD) field appears only in call-setup packets, call-request packets, and incoming call
packets and is optional for these packets. The length permitted in the CUD field
depends on the protocol configured for the subdevice.
A maximum value of 32 hexadecimal characters can be specified for PTP subdevices.
The maximum value that can be specified for ITI subdevices is 24 characters (12 bytes
in the CUD field). The first 4 bytes are reserved for the protocol ID.
The RESET value means no call user data is in the CUD field. For more information
about the CUD field, see The Call User Data (CUD) Attribute on page 5-19.
Default:
None
Range:
Length depends on protocol configured for subdevice
Objects:
Subdevices
CUG
specifies the closed user group (CUG) ID that might be sent in the facilities field of a
call request packet. The range is 00 through 99 for basic CUG format and 0000
through 9999 for extended CUG format. The value for the line CUG is the default. If
you do not specify a CUG value for the subdevice, the line CUG default is used.
RESET deletes any existing CUG assignments.
Default:
None
Range:
00 through 99 for BASIC, 0000 through 9999 for EXT
Objects:
Lines or subdevices
CUGTYPE
specifies the type of closed user group (CUG) facility. BASIC selects the basic CUG
format. BASICOA selects the basic CUG format with outgoing access. EXT selects the
extended CUG format. EXTOA selects the extended CUG format with outgoing
access. If the CUG attribute value is larger than 99, CUGTYPE must be either EXT or
EXTOA.
X25AM Configuration and Management Manual—523424-004
5 -4
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.
Default:
Not set
Range:
0 (lowest priority) through 3 (highest priority)
Objects:
Lines and subdevices
The attribute setting for a subdevice overrides the setting for a line. RESET causes the
attribute to be deleted from the SU or LINE (not set).
This attribute is displayed by issuing the INFO DETAIL command; a setting of -1
indicates the attribute is not set (or reset).
DDNSERVICE
specifies the type of service for a DDN network. The feature is a non-ITU-T facility.
Basic service provides end-to-end call management as described in the ITU-T
Recommendation X.25. Standard service provides support for acknowledgement from
the local DTE to the local DCE.
Default:
BASIC
Range:
BASIC, STANDARD
Objects:
Lines and subdevices
The attribute setting for a subdevice overrides the setting for a line. To display this
attribute, use the INFO DETAIL command.
DESTADDR
specifies the network address of the remote device that the subdevice uses as the
called address in outgoing call request packets. address is a string of decimal digits
(0 through 9) up to 15 digits long. RESET means to delete any existing DESTADDR
assignment. No DESTADDR is assigned. DESTADDR must be passed in the program
X25AM Configuration and Management Manual—523424-004
5 -5
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.
Default:
Not applicable
Range:
Refer to Table 5-1
Objects:
Subdevices
Table 5-1 describes the possible DEVTYPES; the first integer is the type, the second is
the subtype.
Note. DEVTYPE differs from the TYPE and SUBTYPE (ADD DEVICE modifiers) specified for
an X25AM I/O process. The TYPE of an X25AM I/O process must always be 61. The
SUBTYPE of an X25AM I/O process must always be 63.
Table 5-1. DEVTYPE for an SU
6,0
ITI
Conversational-mode terminal
6,1
6510 (ADM-2) terminal
6,2
6520 (ZENTEC) terminal
6,4
6530 terminal
9,0
PTP
Not applicable
58,20
QLLC
Not applicable
63,0
NAM
Not applicable
DSRTIMEOUT
specifies the time interval that the CLIP waits to receive the data set ready (DSR)
signal from the modem. The value must in the range 0 through 5:27:67.
Default:
20 seconds
Range:
0 through 5:27:67
Objects:
Lines
X25AM Configuration and Management Manual—523424-004
5 -6
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.
Default:
Zero
Range:
0 to 200
Objects:
Lines
If this Modifier is set to:
0
Disables the generation of an EMS message during link reset due to an
FRMR condition.
1
Generates an EMS message for every FRMR which causes the X25AM link
reset.
2-200
Enables generation of EMS messages and controls the frequency at which
they are generated.
For example, if EMSFORFRMR is set to 10, an EMS message is generated
on every tenth link reset caused by an FRMR condition.
An FRMR condition occurs when an illegal frame is received on an X25AM line which
results in a X25AM link and line reset.
EXTFORMAT and NOEXTFORMAT
switches on or off the reception of larger-than-normal packets using the
fast-select feature. To turn on this feature using the ALTER LINE command, the
PACKETSIZE modifier must be 256 bytes or larger.
Default:
Off (EXTFORMAT not set)
Range:
On or Off
Objects:
Lines
FRAMEMODE
specifies either a DTE or DCE station. In a point-to-point configuration, such as in
X.25, one side must be a DCE and the other side must be a DTE; otherwise, error 171
occurs and the link state never goes to the READY state.
Default:
DTE
Range:
DTE or DCE
Objects:
Lines
X25AM Configuration and Management Manual—523424-004
5 -7
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. This modifier has no effect on X25AM Line
or I/O process. Regardless of the value of this modifier, you can configure the X25AM
line to use RS232, RS449, V25, or X21 interfaces.
You may not need to specify INTERFACE for the CLIP. If you specify INTERFACE
unnecessarily, SCF does not return an error.
You should specify RS422 only if you require speeds higher than 20 kilobytes per
second or a differential interface. You specify V25 only if you require the connection
between the DTE and DCE to be over a General Service Telephone Network (GSTN)
using the V.25 protocol.
Default:
RS232
Range:
RS232, RS422, or V25
Objects:
Lines
Caution. It is recommended that you do not set CLOCKSPEED greater than the maximum
speed of 19200 BAUD when using an RS232 interface; speeds over 19200 BAUD can cause
line or frame errors.
L3IMMEDIATERR
specifies when an RR (receiver-ready) packet should be sent.
L3IMMEDIATERR sends an RR packet each time a data packet is received and
accepted by a higher level.
Default:
Sends an RR packet when the number of data packets received
equals L3WINDOW.
X25AM Configuration and Management Manual—523424-004
5 -8
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.
Default:
2
Range:
For L3MOD = 8, 1 through 7. For L3MOD128, 1 through 15.
Objects:
Lines.
LOCALADDREXT
is the address that the OSI network uses to identify the local X25AM subsystem. The
address is a string of hexadecimal digits (0 through F) up to 40 digits long. RESET
deletes any existing LOCALADDREXT assignment.
Default:
None
Range:
A string of hexadecimal digits (0 through F) up to 40 digits long
Objects:
Subdevices
LOCALADDREXTTYPE
specifies whether the LOCALADDREXT NSAP is full (0), reserved (1), non-OSI (2), or
reserved (3).
Default:
0
Range:
0 through 3
Objects:
Subdevices
X25AM Configuration and Management Manual—523424-004
5 -9
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.
If L3WINDOW or THRUPUT has been defined as NONEGOTIATE, the subdevice will
accept a call containing a different value, but the subdevice uses the default value.
If PKTSIZE has been defined as NONEGOTIATE, the subdevice will reject a call
containing a value that differs from the default value for PKTSIZE.
The default specification is NONEGOTIATE for PKTSIZE, L3WINDOW, and
THRUPUT.
Note. If you configure a PVC incorrectly with the NEGOTIATE attribute, X25AM will not issue
an error message. You can, for example, specify the NEGOTIATE PKTSIZE attribute for a PVC
without having the X25AM subsystem issue an error message. However, optional user facilities
(per call facilities) such as NEGOTIATE PKTSIZE have no effect on the PVC subdevices.
Default:
NONEGOTIATE
Range:
NEGOTIATE or NONEGOTIATE
Objects:
Subdevices
NETID
specifies the method of determining network-specific requirements, such as the port
number for incoming calls. The NETID depends upon the X.25 network type. For
details about NETID and REMOTENET, see Appendix D, Using the NETID Modifier.
Default:
X25XA
Range:
DATANET, DATAPAC, DATEXP, DDN, DDXP, PSS, TELENET,
TRANSPAC, TWINET, TYMNET, UNINET, X25, X25NP, X25SA,
X25UD, X25XA
Objects:
Lines
NULLFILL
is valid only for subdevices configured with the ITI Protocol. This modifier indicates the
mode-setting control sequence sent to the terminal. ON is used for terminals using
microcode revision C and earlier. The default NULLFILL OFF is for terminals using
more current microcode revisions. The control sequences are as follows:
NULLFILL ON:
Conversation Mode = EOT NUL SOH “C” ETX
Page Mode = EOT NUL SOH “B” ETX
X25AM Configuration and Management Manual—523424-004
5- 10
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.
This is a terminal-dependent option; it can be found in the appropriate terminal
documentation. If a terminal has a configurable blocksize, the terminal blocksize
should be selected according to the specifications in the terminal documentation.
Default:
256
Range:
256 through 8000 bytes
Objects:
Subdevices
PARITY
specifies the parity of data characters transmitted to a terminal. The values can be
EVEN, ODD, or NONE. The default value is NONE (no parity is set).
The PARITY attribute has no meaning when using PTP mode. The parity attribute
applies only to conversational mode for ITI.
Default:
None
Range:
EVEN, ODD, or NONE
Objects:
Subdevices
PARITYCHK
switches on or off parity checking. The default value is Off, which switches off parity
checking.
Default:
Off
Range:
On or Off
Objects:
Subdevices
X25AM Configuration and Management Manual—523424-004
5- 11
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. To use PRICALL set to on, set NETID to DATAPAC.
Default:
Off
Range:
On or Off
Objects:
Subdevices
PROGRAM
specifies the program that is to be downloaded to the CLIP. The X25AM I/O process
modifier, PROGRAM, specifies the program that downloads the microcode file to the
CLIP. Replace the default for PROGRAM only if you are:
•
•
Using a SWAN 2 concentrator (use modifier C1096Q00 instead)
Implementing an X.21 interface that has an X.21 converter cable (for SWAN
concentrator (T3880), use modifier C0051P00; for a SWAN 2 concentrator, use
modifier C0051Q00).
Default:
C1096P00
Range:
C1096P00, C0051P00, C1096Q00, or C0051Q00
Objects:
Lines
PROTOCOL
specifies the protocol that the subdevice uses. The protocol can be ITI, NAM, PTP, or
QLLC. PROTOCOL is a required attribute for the ADD SU command.
Default:
None
Range:
ITI, NAM, PTP, or QLLC
Objects:
Subdevices
Table 5-2 on page 5-13 shows the X25AM protocols and their uses.
X25AM Configuration and Management Manual—523424-004
5- 12
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. For the
DEVTYPE value for each protocol, see Table 5-1 on page 5-6.
PVC
specifies the channel number of the permanent virtual circuit (PVC) with which the SU
is bound. This value must be within the current range limits defined by PVCRANGE for
the line. RESET means to delete any existing PVC assignment. The range is 1 through
4095 or 0 through 4095 (TRANSPAC). The default specification is no PVCs.
Subdevices are configured as SVCs by default when you configure your system. Use
the ALTER SU command to specify a subdevice as a PVC.
Default:
None
Range:
1 through 4095 or 0 through 4095 (TRANSPAC)
Objects:
Subdevices
PVCRANGE
alters the range of logical channels to use for a PVC. Each integer of the pair must
have a value in the range 1 through 4095, except for TRANSPAC, in which the range is
0 through 4095. Also, the first integer must be less than or equal to the second integer.
RESET deletes any existing PVCRANGE assignment.
Although 1 through 4095 is the possible range for the number of circuits, you cannot
effectively use 4095 circuits because the actual usable number is the number of
circuits to which you subscribe. This includes the total of PVCs plus SVCs.
The actual range of allowable circuits is 1 through 510.
Default:
None
Range:
1 through 4095 for each integer of the pair
Objects:
Lines
X25AM Configuration and Management Manual—523424-004
5- 13
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.
RESET means to delete any existing REMOTEADDREXT assignment.
Default:
None
Range:
String of hexadecimal digits (0 through F) up to 40 digits long
Objects:
Subdevices
REMOTEADDREXTTYPE
specifies whether the REMOTEADDREXT NSAP is full (0), reserved (1), non-OSI (2),
or reserved (3).
Default:
0
Range:
0 through 3
Objects:
Subdevices
REMOTENET
specifies the addressing conventions to be used when building the called address in
the call request packet. The default value is the value of the line NETID. Possible
values for REMOTENET are listed below under Range.
Default:
X25XA
Range:
DATANET, DATAPAC, DATEXP, DDN, DDXP, PSS, TELENET,
TRANSPAC, TWINET, TYMNET, UNINET, X25, X25NP, X25UD,
X25SA, X25XA
Objects:
Subdevices
X25AM Configuration and Management Manual—523424-004
5- 14
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. On indicates that the recipient will be requested to pay the charges. The
default value is Off.
Default:
Off
Range:
On or Off
Objects:
Subdevices
REXMITTIMEOUT
specifies the time interval within which an ITI block-mode terminal must respond. This
value must be in the range 0 through 5:27:67. The default value is 20 seconds.
Caution. The value of the REXMITTIMEOUT attribute for SUs is not displayed as it is entered.
It is rounded down to the nearest 5-second interval.
Default:
20 seconds
Range:
0 through 5:27:67
Objects:
Subdevices
RPOA
specifies the Registered Private Operating Agency (RPOA) transit network (or
networks) to be configured on the LINE object. You identify an RPOA transit network
with a data network identification code (DNIC) in the range 0 through 9999. If you
specify more than one DNIC, the DNIC entries must be separated by commas and
enclosed in parentheses. The maximum number of DNIC values that you can specify is
X25AM Configuration and Management Manual—523424-004
5- 15
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. SRCADDR specifies either the calling address used in a
currently connected call or an address defined by SCF.
Default:
None
Range:
A string of decimal digits (0 through 9) up to 15 digits long
Objects:
Lines
SVCRANGE
specifies the range of logical channels to use for switched virtual circuits (SVCs). The
number of circuits is defined by the CIRCUITS modifier. Each integer of the pair must
have a value in the range 1 through 4095, except for TRANSPAC, in which the range is
0 through 4095. The first integer must be greater than the highest value specified for
the modifier PVCRANGE. The second integer must be greater than the first integer
and less than 4096. If you omit the second integer, X25AM calculates the upper bound
based upon the circuits available. RESET means to delete any existing SVCRANGE
assignment.
Although 1 through 4095 is the range for the possible number of circuits, you cannot
effectively use 4095 circuits because the actual usable number is the number of
circuits to which you subscribe. This includes the total of permanent virtual circuits
(PVCs) plus switched virtual circuits (SVCs).
The actual range of circuits allowable is 1 through 510.
Default:
1 to the number of allowable circuits (depending on the RVU)
Range:
1 through 4095
Objects:
Lines
SYNCS
This attribute is not supported for systems running G-series RVUs.
X25AM Configuration and Management Manual—523424-004
5- 16
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. The THRESHOLD attribute is equivalent to the X25AM I/O process
modifier, LINEQUALITYTHRESHOLD. For more information on how line quality is
determined, see Section 4, SCF Commands for the X25AM Subsystem.
Default:
500
Range:
100 through 10000
Objects:
Lines
THRUPUT
specifies the throughput class limit for calls received and the throughput class limit for
calls initiated. Each integer of the pair must be in the range 3 through 12. There are 16
throughput classes (numbered from 0 through 15). The default value is 4,4.
Default:
4,4.
Range:
Each integer of the pair must be in the range 3 through 12.
Objects:
Subdevices.
Table 5-3. THRUPUT Values and Bits Per Second (page 1 of 2)
0
Reserved according to the ITU-T X.25 Recommendation
1
Reserved according to the ITU-T X.25 Recommendation
2
Reserved according to the ITU-T X.25 Recommendation
3
75
4
150
5
300
6
600
7
1200
8
2400
9
4800
X25AM Configuration and Management Manual—523424-004
5- 17
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). RESET
means to delete any existing TRANSITDELAY attribute. You must insert a leading zero
for values less than 1 second (for example, 0.45). TRANSITDELAY is not assigned (it
is blank) by default.
Default:
None
Range:
0.00 through 1:05.53
Objects:
Subdevices
X25AM Configuration and Management Manual—523424-004
5- 18
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. Call User Data (CUD)
Bits
Octet
1
8
7
6
5
4
0
D
S
N
3
2
1
Logical
Channel Identifier
2
Packet Type Identifier (PTI)
3
4
Calling DTE
Called DTE
DTE Addresses
0
Facility Length
0
Facility Fields
Call User Data 1–16 Octets
present in call request and
incoming call packets only
0 = The initial bit (Q bit) is set to zero in call-setup packets.
D = The delivery bit (D bit).
SN = Sequence numbering information
(either module 8 or modulo 128).
VST0501.vsd
For the Process-To-Process (PTP) protocol, the CUD field of a subdevice can:
•
•
•
Be totally absent
Contain a protocol ID (the first 4 bytes of the CUD)
Contain up to 16 bytes of user-defined information
For the Interactive Terminal Interface (ITI) protocol, the CUD field of a subdevice:
•
•
Always contains a protocol ID or 4 bytes of zeros (the default)
Can contain a protocol ID followed by up to 12 bytes of user-defined information
X25AM Configuration and Management Manual—523424-004
5- 19
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.
If NOCALLUSERDATA is configured, the default for PTP subdevices is no CUD field
and the default for ITI subdevices is a CUD field with 4 zero bytes (0000).
Dynamic and Static Values
The CUD value is static if you set it using the SCF ADD SU or ALTER SU command to
the X25AM subsystem. The CUD value is dynamic if you set it programmatically using
the SETPARAM 41 or SETMODE 28 procedure.
The static CUD value is the value present in the CUD field when a subdevice is first
opened, before the application issues a SETPARAM 41 or the SU receives an
incoming packet.
The dynamic CUD contains the values that may have been specified during a session
with a SETPARAM 41 procedure or that have been updated by the receipt of an
incoming packet with a CUD field. The dynamic CUD is the last CUD received or sent
in a call request packet or set by SETPARAM 41.
You can display the CUD value by using the INFO SU command with the DETAIL
option. If the static CUD values have not been overridden by a dynamic value, the SCF
INFO, DETAIL command displays the static CUD values. However, any incoming CUD
value overrides the CUD you set through SCF. The incoming value is the value that
you then see displayed.
The values of the dynamic CUD remain until the SU is closed and are not reset when a
call is cleared. If you want to reset the values of the CUD before the call is cleared, you
can use SETMODE 28 to reset the CUD to the static CUD.
For more information about setting the CUD programmatically, see the X25AM
Programming Manual.
Examples of the CUD Attribute
The following example adds the SU $X25P1.#TERM, gives it the protocol ITI, and sets
the CUD to a value of 123456789a:
-> ADD SU $x25p1.#TERM, PROTOCOL ITI, DEVTYPE (6,0),&
-> RECSIZE 80, CUD “123456789a”
The following example alters the value of the CUD for the SU $X25P1.#TERM:
-> ALTER SU $x25p1.#TERM, CUD “200”
X25AM Configuration and Management Manual—523424-004
5- 20
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.
Errors
SCF error 511 is returned if the SU has a REMOTENET of X25UD, DATAPAC, DDXP,
or UNINET.
If REMOTENET is not specified, the NETID values are used. With no REMOTENET,
the NETID values of X25UD, DATAPAC, DDXP, or UNINET are incompatible with the
specification of a CUD string.
The following attribute name and value can be used for an X25AM subdevice (SU)
object:
CUD { “hex string”| RESET }
You can specify the CUD as a hexadecimal string with a length of 0 to 32 characters by
using the ADD SU or ALTER SU command. (Two hexadecimal characters are
equivalent to 1 byte in the CUD. Thus, a maximum of 32 hexadecimal characters is
equivalent to a maximum of 16 bytes.)
A maximum value of 32 hexadecimal characters can be specified for PTP subdevices.
The maximum value that can be specified for ITI subdevices is 24 characters (12 bytes
in the CUD field). The first 4 bytes are reserved for the protocol ID.
If the hexadecimal string exceeds the maximum length, SCF issues the following error
message:
SCF E20084 Quoted string can be no more than 32 characters
long
If nonhexadecimal characters are specified in the string, SCF issues the following error
message:
X25AM E00507 Invalid value: CUD for object name
Using the ALTER SU command, you can specify the RESET option to delete the CUD
field from the SU. The RESET value means no call user data is present in CUD field.
X25AM Configuration and Management Manual—523424-004
5- 21
Errors
Attribute Descriptions
X25AM Configuration and Management Manual—523424-004
5- 22
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. This section includes how to:
•
•
•
•
•
•
Record and display trace data
Use PTrace to determine which subsystem generated a trace file
Use PTrace commands, along with any special considerations for using these
commands, with the X25AM subsystem
Use SELECT keywords and mask bits
Create a sample trace file
Analyze X25AM traces
For more information about PTrace, see the PTrace Reference Manual.
Recording and Displaying Trace Data
Trace files contain a record of the communications between processes. Each
subsystem determines what information is recorded in its trace files. The type of events
recorded, the amount of detail, and the subsystem-specific parameters may vary.
You generate a trace file using the SCF TRACE command. The trace files that SCF
creates are unstructured and cannot be printed or displayed directly. You use PTrace to
display and examine the trace files. The PTrace program formats the data stored in the
unstructured trace files for output to terminals, printers, or disk files. Figure 6-1 on
page 6-2 shows the four general steps involved in recording and displaying trace data.
X25AM Configuration and Management Manual—523424-004
6 -1
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. The TRACE command allows you
to specify parameters such as the size of the trace records and the name and
maximum size of the trace file. The command that follows traces the line $X25X
and puts the result of the trace in a file called MYFILE.
-> TRACE LINE $X25X,TO MYFILE,SELECT (CLIPL2)
-> PAGES 64, RECSIZE 2000
&
The PAGES option indicates that there are 64 units of space in the extended data
segment. The RECSIZE option indicates that there are 2000 bytes of data in a
trace data record.
2. Collect trace data while performing operations related to the problem you are
analyzing.
3. Stop the trace with another SCF TRACE command. The following command stops
the trace on line $X25X:
-> TRACE LINE $X25X, STOP
4. Display the trace file with PTrace. The following command displays the trace in the
file named MYFILE:
> PTRACE FROM MYFILE
X25AM Configuration and Management Manual—523424-004
6 -2
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.
This subsection describes only those details of the PTrace commands used to format
trace files generated by X25AM.
Table 6-1 describes the PTrace commands that can be used with the X25AM
subsystem. For additional information about these commands, see the PTrace
Reference Manual.
Table 6-1. Summary of PTrace Commands for the X25AM Subsystem
(page 1 of 2)
ALLOW
Specifies the number of errors or warnings permitted during the
execution of a command.
COUNT
Counts the records in the trace file.
DESELECT
Cancels selection criteria established by use of the SELECT command.
EBCDIC
Allows trace details to be translated into EBCDIC code.
ENV
(ENVironment) Displays the settings of PTrace session parameters.
EXIT
Terminates a PTrace session.
Fn
(Any 6530 function key) Performs a NEXT command.
FC
(Fix Command) Allows the last PTrace command line entered to be
corrected.
FILTER
Establishes filtering criteria for displaying trace records. PTrace
considers SELECT or SELMASK command criteria before filtering
criteria.
FIND
Searches the formatted output for a specified string.
FROM
Specifies the trace file to be displayed.
HELP
Displays information about PTrace commands.
HEX
Displays numbers in hexadecimal notation.
LIMIT
Limits the number of records displayed by a single command.
LISTPM
Provides information about each running product module.
LOG
Directs a copy of PTrace input and output to a file.
NEXT
Displays the next trace data record(s) in the trace file.
OBEY
Causes commands to be read from a different input file.
X25AM Configuration and Management Manual—523424-004
6 -3
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.
SELMASK
Selects the 32-bit mask trace-option value.
SETTRANSLATE
Changes the ASCII-to-EBCDIC translation table.
STATETABLES
Specifies the name of the file used for the display of state-machine
labels.
TEXT
Turns on the text display option.
TIMESTAMP
Displays trace record time in current system Local Civil Time, or in
original trace time.
The commands that you cannot use with the X25AM subsystem are:
DETAIL
LABEL
TRANSLATE
Note. Although the TRANSLATE command is no longer supported, it does still affect the
X25AM lines. It does not affect reading CALL, CLEAR, or RR packets, but it does allow you to
look for text.
The remainder of this subsection describes in detail the subsystem-specific commands
supported by the X25AM subsystem (FILTER, SELECT, and TEXT).
Each command description includes a brief description of the command, the
command’s syntax, and any special considerations applicable to the command. The
commands are described in alphabetical order.
For information on starting PTrace and entering PTrace commands, and for more
detailed descriptions of the PTrace commands available to all subsystems, see the
PTrace Reference Manual.
FILTER Command
The FILTER command selects records based on their content. Because some events
traced under X25AM may not be relevant, try to filter them out. For example, use
FILTER to select one logical channel number (LCN) or one subdevice (SDN) at a time,
which may make looking for subdevice-specific problems easier.
Another way to use FILTER is to search only for certain packet types and related
packet types. Searching for related packet types can greatly simplify your search. For
example, a call-request packet expects a call-accepted packet in response. Also, a
X25AM Configuration and Management Manual—523424-004
6 -4
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 ]...]
frame-type indicates the types of frames to be displayed. frame-type is one of
the following values:
[
[
[
[
[
[
I
NOTRR
REJ
RNR
RR
UNNUMBERED
]
]
]
]
]
]
NOTRR displays all frames but the RR frames. Omitting frame-type causes all
types to be displayed. All frame types are displayed by default.
HELP
displays the syntax of the X25AM filter options only after you have opened an
X25AM trace file.
LCN [ lcn-number ]
displays packets and level-3 state-machine entries for the specified logical channel
number (entered in decimal notation). LCN filtering has no effect on level-4 trace
records. Omitting lcn-number turns off filtering based on LCN. LCN is off by
default.
[NO]INTERNALS
indicates whether X25AM internals are to be displayed. INTERNALS displays
X25AM internals, which are used for debugging X25AM. NOINTERNALS
suppresses the display of internals. NOINTERNALS is the default specification.
[NO]SM
indicates whether state-machine entries are to be displayed. SM displays statemachine entries for the selected levels. NOSM suppresses the display of state
machine entries. NOSM is the default specification.
X25AM Configuration and Management Manual—523424-004
6 -5
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.
SDN [ subdevice-number ]
displays level-4 entries and packets and level-3 state-machine entries for the
specified subdevice number (entered in decimal notation). Omitting subdevicenumber turns off filtering based on SDN. By default, filtering by subdevice number
is off.
Considerations
•
•
•
FILTER LCN 0 finds restart packets; FILTER SDN 0 finds incoming call-request
packets.
FILTER PACKET CALL displays both incoming and outgoing call-request and callaccept packets.
While both LCN and SDN filtering can be in effect at the same time, only a few
combinations make sense. This filter command displays restarts and SDN xx:
? FILTER LCN 0; FILTER SDN xx
The following filter command displays restarts and incoming calls:
? FILTER LCN 0; FILTER SDN 0
•
Filter options require a corresponding select mask. For example, the restart
packets are level-3 data. To display only restart packets, you must issue the
SELECT L3 and FILTER PACKET RESTART commands.
SELECT Command
The SELECT command establishes the selection criteria that control which trace
records you want to display. To determine which records to display in response to a
NEXT, FIND, or RECORD command, PTrace checks its selection mask to determine
whether the record is a type that you want to display. PTrace also checks many other
session parameters, such as those established by the FILTER and LIMIT commands.
X25AM Configuration and Management Manual—523424-004
6 -6
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. PTrace SELECT Command Keywords for the X25AM Subsystem
DR
0
Driver calls and exits
IOS
1
IOS waits and wakeups, all LCBs
L2
2
Frame layer or CLB protocol for the CLIP
L3
3
Packet layer
L4
4
Application layer
CLIPL2
15, 21
CLIP frame layer
CLIPDI
15, 16
CLIP data in
CLIPDO
15, 17
CLIP data out
CLIPREQ
15,27
CLIP requests and responses
ALL
0-31
Selects all records
CURRENT
—
Maintains previous settings and add new ones
TEXT Command
The TEXT command controls the textual display of trace records, excluding the header
record. The TEXT command applies only to data packets.
The textual display appears below labeled data, the HEX display, and the OCTAL
display, if they are present. The display consists of ASCII characters, with control
codes represented by two-character or three-character mnemonics.
TEXT
[ ON ]
[ OFF ]
ON
turns on the textual display of trace records.
OFF
turns off the textual display of trace records.
X25AM Configuration and Management Manual—523424-004
6 -7
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. For example, if you have a problem when you start a line, you can
use the following steps to stop the line, start it again, and create a useful trace file:
1. Stop the line. The following command stops the line named $X25P1:
-> STOP LINE $x25p1
2. Start the line. The following command starts the line named $X25P1:
-> START LINE $x25p1
3. Start the trace with the SCF TRACE command and specify SELECT ALL, SPACE
64, WRAP. The WRAP option specifies that when the trace file end-of-file mark is
reached, trace data wraps around to the beginning of the file and overwrites any
data there. The following command starts a trace on the line named $SP1:
-> TRACE LINE $x25p1, TO filename, SELECT ALL, PAGES 64, WRAP
4. Wait for the X25AM line-ready console message.
5. Add a PTP subdevice suitable for use with X3PAD, as in the following example:
-> ADD SU $x25p1.#ptp, PROTOCOL PTP, DEVTYPE (9,0), &
-> RECSIZE 80, RPOA (125, 300, 5000)
6. Use X3PAD to place a call, send a few data packets, and then clear the call.
7. Stop the trace. The following command stops the trace on the line named $SP1:
-> TRACE LINE $x25p1, STOP
8. Use PTrace to format and display the trace records.
Reading X25AM Traces
The X25AM traces that you capture using the SCF TRACE command can be read
using PTrace. A trace can collect a significant amount of data, which requires sorting
before you can find the problem. Several options are available to you to make the job
easier, such as the PTrace SELECT command (described earlier in this section) and
the FIND command, described below.
X25AM Configuration and Management Manual—523424-004
6 -8
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. Then use
PTrace, SELECT (L3,L4), and the FIND command to look for the string “140”(FIND
“140”). After you find the error, look at the preceding packets to discover its cause. You
may find that the application has not opened the subdevice or that the subdevice was
configured with an incorrect address or port number.
X25AM traces the WRITELINK as well, so you can look for errors using FIND “FE#” in
PTrace. Whenever X25AM returns an error that is not FEOK (0) to an application,
PTrace shows it as a level-4 trace record with “FE #”. Thus, you can easily find all the
errors in PTrace by entering >FIND “FE #”. If there is more than one error, enter F
again to find the rest.
If level 3 can successfully send and receive packets, then there is probably no error on
level 2 (a level-2 data, or I-FRAME always contains a level-3 packet). In this case, you
can scan the traces more quickly by masking off the level-2 trace mask.
Tracing Level 2
The type of CLIP that you use determines how the level-2 protocol is implemented; the
tracing is different as a result of the CLIP. The CLIP can do the busywork prescribed by
the protocol and interrupt the host CPU only when actual data arrives or a significant
event (such as a line error) occurs. To view the relationship of level 2 to the protocol,
set your PTrace select mask for the trace type records shown in Table 6-3.
Table 6-3. PTrace Select Masks
PTrace Mask
SELECT L2
SELECT CLIPDI
SELECT CLIPDO
What to Look for in Level 2
When you use the SCF START command on an X25AM line, level 2 becomes active.
When you issue the START command, a message is sent to the console: “X.25 LINE
READY.” If you see a “LINE NOT READY” error on the console instead, then you
X25AM Configuration and Management Manual—523424-004
6 -9
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. X25AM may be trying to send the UA in response to
the SABM, but the modem may not be supplying the transmit clock to the CLIP. A
quick look at a datascope or breakout box should show DTR, DSR, RTS, CTS, and
Carrier Detect pins (20, 6, 4, 5, and 8) high, with Transmit and Receive Clocks
fluctuating at the proper speeds (pins 15 and 17). Also, TD and RD (pins 2 and 3)
should show some action every T1 timer interval. If they do not show any action,
there is a problem with the CLIP, cable, or modem. Run the diagnostics to isolate
the problem.
2. If both sides are sending SABMs, check the addresses. If both sides are sending
commands with the same address, then most likely they are both set as DTEs or
DCEs. In a typical X.25 setup, one side must be set for DCE (usually the network)
and the other side set for DTE (usually X25AM).
3. L2DISC is an option for DCEs that require a DISC command before the DCEs can
handle SABM commands. The default option is L2NODISC (do not send DISC
commands on SCF START). The default works for most networks.
4. An error-free level 2 should show I-frames (data) getting RR responses. You
generally do not want to encounter RNRs (buffer problems), FRMRs (illegal or
unaccepted command frames), REJs (out of sequence I-frames received), or
DISCs and DMs (one side disconnecting). If you encounter only I-frames and RRs
being sent and received, you can usually assume there is nothing wrong with level
2. Also, you can determine that level 2 is error-free by examining the level-2
statistics using the SCF command STATUS LINE $ldev, DETAIL.
5. The level-2 trace is the last place where you can see the frame written to the trace
file before it is sent to the communications line. However, seeing the frame traced
does not mean that it has been successfully sent.
Because the software does all the tracing and accumulates the statistics, the only
way to actually see what is sent on the line is to use a line monitor. You should
always look for a response to level-2 frames that the CLIP sends. If level-2 frames
are retried, a bad modem or cable may be the problem: either the data is not being
sent correctly or not being acknowledged from the remote side.
Note. The examples shown in this section are for illustrative purposes only.
X25AM Configuration and Management Manual—523424-004
6- 10
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.75
3230 5E32 3846 4542 3932 T9317C20^28FEB92
5042 5E41 414B 3033 4109 ^X25LAPB^AAK03A.
..
P/F=0
Seq 2
Len 13
N(R)=1
06/11/99 15:08:35.766494 >028.483272 #2
CSS LAPB Out
A/C($0321) DTE
000: 0321
RR
P/F=0
Seq 17
N(R)=1
Seq 25
UA
Time
15:07:41.36
CLIP Trace Blk
Len 13
06/11/99 15:08:50.882134 >015.115640 #3
CSS LAPB Out
A/C($0373) DTE
000: 0373
CLIP Trace Blk
Time
15:07:56.37
CLIP Trace Blk
Len 13
Time
15:08:24.84
F=1
CSS LAPB Out
A/C($0100) DCE IFRAME
000: 0100 1000 FB00
Seq 26
Len 18
P=0 N(S)=0 N(R)=0
00
Time
15:08:24.94
CSS LAPB In
A/C($0300) DTE IFRAME
000: 0300 1000 FB07
Seq 27
Len 18
P=0 N(S)=0 N(R)=0
00
Time
15:08:24.94
CSS LAPB Out
A/C($0321) DTE
000: 0321
CSS LAPB In
A/C($0121) DCE
000: 0121
Time
15:08:24.95
P/F=0
Seq 30
N(R)=1
Len 13
RR
Time
15:08:24.95
P/F=0
Seq 31
N(R)=1
Len 13
RR
06/11/99 15:09:05.890160 >015.008026 #4
CSS LAPB Out
A/C($0321) DTE
000: 0321
CSS LAPB In
A/C($0121) DCE
000: 0121
CLIP Trace Blk
Time
15:08:39.95
P/F=0
Seq 38
N(R)=1
Len 13
RR
Time
15:08:39.96
P/F=0
Seq 39
N(R)=1
Len 13
RR
X25AM Configuration and Management Manual—523424-004
6- 11
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.048527 #6
CSS LAPB In
A/C($0322) DTE IFRAME
000: 0322 1001 0B20
CSS LAPB Out
A/C($0341) DTE
000: 0341
RR
CSS LAPB In
A/C($0141) DCE
000: 0141
RR
Seq 59
Len 23
P=0 N(S)=1 N(R)=1
0000 0000 0000
P/F=0
CSS LAPB Out
A/C($0142) DCE IFRAME
000: 0142 1001 1300
CLIP Trace Blk
Seq 62
N(R)=2
Len 13
Seq 63
Len 18
P=0 N(S)=1 N(R)=2
81
P/F=0
Seq 64
N(R)=2
Len 13
Time
15:09:23.68
Time
15:09:23.68
Time
15:09:23.70
Time
15:09:23.71
End of Trace file.
Level-2 Trace Analysis
The L2-trace example comes from a single CLIP trace block that contains several
level-2 frames that were successfully sent and received. The I-frame (information) sent
at Sequence 63 shows the state of the DCE. The N(S) is sending an I-frame. The N(R)
value states that it has accepted and acknowledged the I-frame from the DTE, and it is
waiting for the next incoming frame.
At Sequence 64 in the trace block, an RR response frame is received from the DTE.
The N(R) value states that the DTE received the I-frame sent at Sequence 63 (which
contained the N(S) value of 1), and that the DTE is waiting for the next I-frame to be
sent.
The N(R) value always points to the next I-frame N(S) the sender expects to receive. It
acknowledges all frames received up to N(R)-1.
Note. An RR frame does not contain an N(S) field.
It is normal to find an RR frame returned with an N(R) that does not acknowledge the
last I-frame sent. However, if an RR frame is sent with the P bit set, the remote side
must respond with either an I-frame or RR frame that has the F bit set. This responding
relationship is called checkpointing, and it is usually done when one side’s L2 window
has been reached. Checkpointing allows the DTE to decide which frames have not
been acknowledged and, if necessary, to begin error recovery.
X25AM Configuration and Management Manual—523424-004
6- 12
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. The protocol
describes the basic handshaking used to send and acknowledge data for a number of
virtual circuits multiplexed over the same Data Link Layer (level 2). X.25 circuits are
defined by a distinct logical channel number (LCN), which is a 2-byte field that
immediately follows the address and control bytes of a level-2 I-frame.
Figure 6-2 shows an X.25 packet.
Figure 6-2. X.25 Packet
7E
A
Logical
Channel Number
C
Packet
Type
Optional
Data...
FCS
7E
X.25
Packet
VST0602.vsd
Packet Type identifies the kind of packet. See Table 6-4 for the most significant bits
(MSBs), the least significant bits (LSBs), and the hexadecimal values of the different
packet types.
Table 6-4. Packet Types (page 1 of 2)
Call Request
0000
1011
0B
Call Accepted
0000
1111
0F
Clear Request
0001
0011
13
Clear Confirmed
0001
0111
17
Diagnostic
1111
0001
F1
Interrupt
0010
0011
23
Interrupt Confirmed
0010
0111
27
Reset
0001
1011
1B
Reset Confirmed
0001
1111
1F
Restart
1111
1011
FB
Restart Confirmed
1111
1111
FF
Data*
RRRM
SSS0
* RRR = N(R) acknowledges all data packets received -1. SSS = N(S), number of data packets sent. M = More
bit (more data follows).
X25AM Configuration and Management Manual—523424-004
6- 13
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).
What to Look for in Level 3
The following example PTrace command allows you to view only the level-3 packets:
? SELECT L3; FILTER NOSM; FILTER NOINTERNALS
After level 2 is synchronized, you should see one restart packet sent and confirmed in
the trace, with level 3 synchronized. The level 3 appearance differs depending on
whether it is a permanent virtual circuit (PVC) or a switched virtual circuit (SVC).
If your side is a PVC, you may see data packets sent whenever the file-system call
warrants it (that is, WRITE = 1 data packet out) and RR received after WINDOW SIZE
is reached at the remote.
If your side is an SVC, data cannot be sent until the logical circuit is established. You
should see the SVC sending call request packets, with the correct called (destination)
and calling (source) addresses included. There might also be some user data and
facility fields appended at the end of the call request packet. The remote side checks
the called DTE address field of the call request packet it receives, verifies it against its
own configured subdevice addresses, and then responds with either a call accept
packet (if OK) or a clear packet (if not). The clear packet should contain a clear
diagnostic byte explaining why the call was cleared. However, for network-generated
clear packets are often specific to the PDN. Consult the PDN specification for
clarification.
Most X25AM problems are caused by wrongly cleared calls. These problems can
usually be traced to incorrectly configured subdevices or lines being set for an incorrect
NETADDR. Check the subdevices’ NETADDR and PORT values to be sure that the
values match. In some cases calls are cleared because the network was configured
with an incorrect NETID. The NETIDs (DATANET, DATAPAC, DATEXP, DDN, DDXP,
PSS, TELENET, TRANSPAC, TWINET, TYMNET, X25, X25NP, X25SA, X25UD, and
X25XA) specify different methods of addressing that support a variety of PDNs. See
Appendix D, Using the NETID Modifier.
In some cases, calls are cleared because the DCE cannot accept the call negotiation
values in the facility fields.
Another item to note is the usual default value for the line attribute EXTENDED. If
EXTENDED is off, then level 3 automatically clears any incoming packets with
extended user data in call, clear, or interrupt packets. The default value for
EXTENDED is off, which causes problems with some PDNs that require the extra data.
X25AM Configuration and Management Manual—523424-004
6- 14
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.TRL3LOG
?record 1,9999
06/11/99 15:16:33.882526 >000.000000 #27
L3 Pkt In
SDN #000/%000 LEN #0010 GFI(0001)
MOD8
LGN/LCN $001
Call^req
000: 1001 0B20 0000 0000 0000
CALLED ADDRESS
($0)
CALLING ADDRESS ($2)
00
FACILITIES
($00)
USER DATA
($04)
00000000
06/11/99 15:16:33.900621 >000.018095 #33
SDN #001/%001 LEN #0005 GFI(0001)
Call^conf
000: 1001 0F00 00
CALLED ADDRESS
($0)
CALLING ADDRESS ($0)
FACILITIES
($00)
06/11/99 15:17:15.447953 >041.547332 #63
Data M=0 P(S)=0 P(R)=0
000: 1001 0064 6A66 6A6B 6A66 6B6A
008: 646A 6B66 6A
06/11/99 15:18:38.218254 >082.770301 #113
SDN #000/%000 LEN #0005 GFI(0001)
Clear
000: 1001 1300 00
CAUSE CODE: $00
DIAGNOSTIC CODE: $00/#000
06/11/99 15:18:38.345233 >000.126979 #121
SDN #000/%000 LEN #0003 GFI(0001)
Clear^conf
000: 1001 17
MOD8
L3 Pkt Out
LGN/LCN $001
L3 Pkt Out
6B64
6A6B
MOD8
L3 Pkt Out
LGN/LCN $001
MOD8
L3 Pkt In
LGN/LCN $001
End of Trace file.
Level-3 Trace Analysis
Sequence #27 from the level-3 trace is shown here with the pertinent fields in boldface:
06/11/99 15:16:33.882526 >000.000000 #27
SDN #000/%000 LEN #0010 GFI(0001)
Call^req
000: 1001 0B20 0000 0000 0000
CALLED ADDRESS
($0)
CALLING ADDRESS ($2)
00
FACILITIES
($00)
USER DATA
($04)
MOD8
L3 Pkt In
LGN/LCN $001
00000000
X25AM Configuration and Management Manual—523424-004
6- 15
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). In X25AM, an LCN is roughly equivalent to a
subdevice.
The third byte of the packet, 0B, identifies the type of packet. In the example above, a
call request packet has arrived. The ensuing data depends on the type of packet. Here,
there is no called address (because the NETID happens to be TELENET). When this
packet comes into the local level 3, it must first match the configured line NETADDR
(set here at 0). Then, the remaining two digits are passed to level 4 to be matched to a
subdevice’s configured port number. Because a subdevice is configured to match the
incoming address, the local level 3 sends the call accepted packet in response, shown
at sequence #33.
At this point, the circuit is connected and data can be transferred for LCN 1. The full
address of the subdevice is no longer needed because the LCN number represents the
connection and is sufficient to identify the subdevice from now on.
At sequence #113, X25AM initiates circuit disconnection by issuing a clear packet (the
initiation begins because the application issued a CONTROL 12).
At sequence #121, the last trace record shows the network’s response: a clear
confirmed packet. At this point the circuit is cleared and the LCN (and thus the
subdevice) are free to be used again.
Sample Trace Reading of Calls Being Cleared
Trying to establish a call is a common problem in X25AM. X25AM and host DCEs clear
calls for several reasons. When a call is cleared, take a trace. You can usually pinpoint
the problem by looking at the packets. One side of the line issues a call request packet
to establish a call. The other side acknowledges the call with a call accept packet.
Either side can reject the call by returning a clear packet. Sometimes the clear packet
contains an extra byte of data, called a clear diagnostic byte.
The following example (Steps 1 through 9) shows a call being cleared as a result of a
failure:
X25AM Configuration and Management Manual—523424-004
6- 16
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. Look at the trace using PTrace:
Ptrace Log File:
$DATA2.PATRICIA.L3L4LOG
?record 1,9999
06/11/99 15:21:33.033975 >000.000000 #1
L4 WRITELINK
SDN #032/%040
FEOK
RSP 49E0 P1-6 %000000 %000035 %000440 %012000 %000130
%000000
06/11/99 15:21:53.051657 >020.017682 #16
L4^LCB^In
SDN #001/%001
Open
LCB 3576 P1-6 %140012 %000035 %050000 %000402 %000000
%177777
06/11/99 15:21:53.055215 >000.003558 #17
L4 WRITELINK
SDN #001/%001
FEOK
RSP 3576 P1-6 %000000 %000035 %004000 %000401 %000000
%177777
06/11/99 15:21:57.829978 >004.774763 #22
L4^LCB^In
SDN #001/%001
Control
LCB 2362 P1-6 %144000 %000035 %000000 %000013 %000001
%000000
06/11/99 15:22:24.407544 >026.577566 #40
L3 Pkt In
SDN #000/%000 LEN #0010 GFI(0001)
MOD8
LGN/LCN $001
Call^req
000: 1001 0B20 0000 0000 0000
CALLED ADDRESS
($0)
CALLING ADDRESS ($2)
00
FACILITIES
($00)
USER DATA
($04)
00000000
06/11/99 15:22:24.415838 >000.008294 #47
L4 WRITELINK
SDN #001/%001
FEOK
RSP 2362 P1-6 %000000 %000035 %000000 %000013 %000000
%000000
06/11/99 15:22:24.420839 >000.005001 #49
L3 Pkt Out
SDN #001/%001 LEN #0005 GFI(0001)
MOD8
LGN/LCN $001
Call^conf
000: 1001 0F00 00
CALLED ADDRESS
($0)
CALLING ADDRESS ($0)
FACILITIES
($00)
06/11/99 15:23:46.511069 >082.090230 #97
L4^LCB^In
SDN #001/%001
Write
LCB 3C44 P1-6 %144002 %000035 %000000 %000012 %000001
%000000
X25AM Configuration and Management Manual—523424-004
6- 17
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.988506 #129
SDN #001/%001 LEN #0005 GFI(0001)
Clear
000: 1001 1300 00
CAUSE CODE: $00
DIAGNOSTIC CODE: $00/#000
MOD8
L3 Pkt In
LGN/LCN $001
MOD8
L3 Pkt Out
LGN/LCN $001
06/11/99 15:24:35.511050 >000.007625 #136
SDN #000/%000 LEN #0003 GFI(0001)
Clear^conf
000: 1001 17
06/11/99 15:24:47.330836 >011.819786 #149
L4^LCB^In
SDN #001/%001
Close
LCB 391E P1-6 %144013 %000035 %000176 %000000 %000001
%000000
06/11/99 15:24:47.334473 >000.003637 #150
L4 WRITELINK
SDN #001/%001
FEOK
RSP 391E P1-6 %000000 %000035 %000176 %000000 %000000
%000000
06/11/99 15:25:11.922827 >024.588354 #165
SDN #000/%000 LEN #0010 GFI(0001)
Call^req
000: 1001 0B20 0000 0000 0000
CALLED ADDRESS
($0)
CALLING ADDRESS ($2)
00
FACILITIES
($00)
USER DATA
($04)
06/11/99 15:25:11.927281 >000.004454 #171
SDN #000/%000 LEN #0005 GFI(0001)
Clear
000: 1001 1300 81
CAUSE CODE: $00
DIAGNOSTIC CODE: $81/#129
06/11/99 15:25:11.962515 >000.035234 #179
SDN #000/%000 LEN #0003 GFI(0001)
Clear^conf
000: 1001 17
MOD8
L3 Pkt In
LGN/LCN $001
00000000
MOD8
L3 Pkt Out
LGN/LCN $001
MOD8
L3 Pkt In
LGN/LCN $001
06/11/99 15:26:20.836915 >068.874400 #215
L4^LCB^In
SDN #032/%040
Writeread LCB 4E0A P1-6 %144003 %000035 %000440 %012000 %000001
%000000
End of Trace file.
3. The clear packet (at sequence #171) contains the diagnostic byte 81, which means
no subdevice could accept the call. The diagnostic byte 81 is an X25AM internal
error, issued for any of the following reasons:
•
•
No subdevices were able to accept calls (CONTROL 11).
The subdevices’ port number did not match the call request number.
X25AM Configuration and Management Manual—523424-004
6- 18
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.
The diagnostic error 81 shows that the call request packet was in the correct L3
format for call requests, as required by the ITU-T. Level 4 checks the call request
parameters against the configured parameters for each subdevice. If no subdevice
is found to accept all of the previous requirements, a clear packet is returned with
the appropriate diagnostic error. For a list of X25AM SCF errors, see Appendix C,
X25AM Error Messages.
4. Because the local network is the destination of the call request (incoming packet),
check two things: first, that a subdevice is available to accept the call, and, second,
that the subdevice has the correct address configured to answer the call. As the
trace above indicates, subdevice $DATA2.#T1 has been opened and a CONTROL
11 (P4=%13) was posted in sequence #97. Thus, a subdevice is available to
accept the call.
Check the addresses to see whether the subdevice is correctly configured:
-> info line $x25p1, detail
X25AM Detail Info LINE
$X25P1
*CallingAddr.. ON
*Threshold.. 500
*CharacterSet.
Debug........ OFF
*SYNCS...... 3
*DSRTimeout...
*Extformat.... OFF
*L3window... 2
*IdleTimeout..
*Interface.... RS232
*L3mod...... 8
*PVCrange.....
*Netid........ DDN
*Retries.... 10
*SVCrange.....
*CUG..........
*Framemode.. DCE
*T1Timeout....
*CUGType...... BASIC
*BCUG.......
*Transitdelay.
*Calls........ TWO WAY
PacketSize. 128
Type.........
*Clockmode.... DTE
*Clockspeed. CLOCK600
*SrcAddr......
*Program...... $SYSTEM.CSS02.C1096AAF
*RPOA..........
*Bpadparms....
*Cpadparms....
*DDNService... BASIC
*DDNPrec...
EBCDIC
0:20.00
0:15.00
(
1,32
0:03.00
(61,63)
X25AM Configuration and Management Manual—523424-004
6- 19
)
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.....
*Protocol...
*ReverseChg.
*Nullfill...
*BCUG.......
( 9,0 )
NONE
PTP
OFF
OFF
*Recsize..........
*Pricall..........
*ParityChk........
*Thruput..........
*RemoteNet........
*Transitdelay.....
*LocalAddrExtType.
*RemoteAddrExtType
*Page6520BlkSize
128
OFF
OFF
( 4,12)
X25XA
0
0
0
6. The display from the INFO SU command reveals the problem. Because there is no
port number 4, level 3 is clearing the call. Alter the port number to correspond to
the incoming call request, and the call should then be accepted. Use the following
commands to alter the port number for the subdevice named #PTP:
-> ABORT SU #PTP
-> ALTER SU #PTP,PORT 4
-> START SU #PTP
Note. For port digits using X25 NETID, the port number is right justified with a padding 0, so
port 4 = 04.
Check that the subdevice has been correctly altered:
->
info su $x25p1.#ptp, detail
X25AM Detail Info SU
*AcceptChg.... OFF
*PVC..........
*Port......... 4
*RexmitTimeout 0:20.00
*CUG..........
*CUGType...... BASIC
*DestAddr.....
*Negotiate....
Associateline
*LocalAddrExt.
*RemoteAddrExt
*CUD..........
*RPOA..........
*Bpadparms....
$X25P1.#PTP
*DevType....
*Parity.....
*Protocol...
*ReverseChg.
*Nullfill...
*BCUG.......
( 9,0 )
NONE
PTP
OFF
OFF
*Recsize..........
*Pricall..........
*ParityChk........
*Thruput..........
*RemoteNet........
*Transitdelay.....
*LocalAddrExtType.
*RemoteAddrExtType
*Page6520BlkSize
128
OFF
OFF
( 4,12)
X25XA
0
0
0
7. Try the call again after you have changed the port number. Use the following
command to start the trace:
-> TRACE,TO TRX3,SELECT L3
X25AM Configuration and Management Manual—523424-004
6- 20
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.744765
Trace entry size limit: 120
L3 Pkt In Record 18D Seq 18 Type 51
Time 14:50:37.487673
SDN #000/%000 LEN #0014 GFI(QD_8) 0001 LGN/LCN $032
Call^req
000: 1032 0B55 2220 4111 0300 0000 0000
L3 Pkt Out Record 24D Seq 24 Type 50
Time 14:50:37.487673
SDN #001/%001 LEN #0005 GFI(QD_8) 0001 LGN/LCN $032
Call^conf
000: 1032 0F00 00
9. The call was accepted. If the port numbers were correct and the call was still
cleared the same method would still apply, for the most part. You would check the
call request packet for unsupported facilities, user data, missing calling address
fields, and so on.
Your HP representative also may be able to help you find out why calls are not
accepted. Using SCF, you can alter almost any field you want to get the calls to go
through. Also remember that most PDNs have their own specific addressing
requirements to which you must conform.
The Application Level
To determine application problems and their relation to level 3, use SELECT (L4,L3).
The application can communicate with X25AM using ITI for terminals connected to
PADs, PTP mode for transferring data directly to the PDN, NAM mode for multiple
NonStop systems using Expand with PSDN, and QLLC mode for SNA systems with
PSDN. The application communicates with X25AM by posting WRITEs, READs,
SETMODEs, CONTROLs, and so on to the subdevice. The NonStop file system
forwards each call to X25AM as a link control block (LCB). X25AM picks up each call
through LISTEN. When X25AM finishes the operation, it returns an appropriate FE
error (that is, 0= FEOK, 140= LCN cleared). Level 4 traces each LISTEN and
WRITELINK as X25AM detects it. The following example is a trace taken with level-3
X25AM Configuration and Management Manual—523424-004
6- 21
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.164537
Last trace entry:
01/28/90 09:25:33.765623
Trace entry size limit: 120
X25AM Configuration and Management Manual—523424-004
6- 22
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.487673
SDN #002/%002
ControlLCB 633E P1-6 %147400 %000026 %000000 %000013 %000020 %000000
L3 Pkt In Record 27D Seq 27 Type 51 Time 09:25:28.487673
SDN #000/%000 LEN #0015 GFI(0001)
MOD8
LGN/LCN $002
Call^req
000: 1002 0B66 1111 0322 2203 0000 0000 00
L4 WRITELINK
Record 30D
Seq 30
Type 71 Time 09:25:28.487673
SDN #002/%002
FEOK
RSP 633E P1-6 %000000 %000026 %000000 %000013 %000020 %000000
L3 Pkt Out
Record 36D
Seq 36
Type 50 Time 09:25:28.487673
SDN #002/%002 LEN #0005 GFI(0001)
MOD8
LGN/LCN $002
Call^conf
000: 1002 0F00 00
L3 Pkt Out
Record 40D
Seq 40
Type 50 Time 09:25:28.487673
SDN #002/%002 LEN #0020 GFI(1001) Q MOD8 LGN/LCN $002
Data M=0 P(S)=0 P(R)=0
000: 9002 0002 0101 0400 0715 0800 0A00 0201
008: 037E 0D04
L4^LCB^In Record 48D
Seq 48
Type 70 Time 09:25:28.487673
SDN #002/%002
Read LCB 674E P1-6 %147401 %000026 %000000 %000014 %000020 %000000
L3 Pkt In
Record 53D
Seq 53
Type 51 Time 09:25:28.487673
SDN #002/%002 LEN #0015 GFI(0001)
MOD8 LGN/LCN $002
Data M=0 P(S)=0 P(R)=1
000: 1002 2074 6572 6D69 6E61 6C20 4944 02
L4 WRITELINK
Record 56D
Seq 56
Type 71 Time 09:25:28.487673
SDN #002/%002
FEOK RSP 674E P1-6 %000000 %000026 %000000 %000014 %000014 %000000
L4^LCB^In Record 66D Seq 66 Type 70 Time 09:25:29.487673
SDN #002/%002
SetmodeLCB 6C14 P1-6 %147407 %000026 %000000 %000000 %000020 %000024
L4 WRITELINK Record 67D Seq 67 Type 71 Time 09:25:29.487673
SDN #002/%002
FEOK
RSP 6C14 P1-6 %000000 %000026 %000000 %000000 %000000 %000024
L4^LCB^In
Record 70D
Seq 70
Type 70 Time 09:25:29.487673
SDN #002/%002
Wtread LCB 6560 P1-6 %147403 %000026 %000036 %000005 %000020 %000000
L3 Pkt Out
Record 74D
Seq 74
Type 50 Time 09:25:29.487673
SDN #002/%002 LEN #0020 GFI(1001) Q MOD8 LGN/LCN $002
Data M=0 P(S)=1 P(R)=1
000: 9002 2202 0101 0400 0715 0800 0A00 0200
008: 037E 0D00
L3 Pkt Out
Record 78D
Seq 78
Type 50 Time 09:25:29.487673
SDN #002/%002 LEN #0033 GFI(0001) MOD8 LGN/LCN $002
Data M=0 P(S)=2 P(R)=1
000: 1002 2445 6E74 6572 2070 6173 7377 6F72
008: 6420 6174 2074 6865 2070 726F 6D70 743A
010: 20L3 Pkt In
Record 86D
Seq 86
Type 51 Time
09:25:29.487673
SDN #002/%002 LEN #0009 GFI(0001) MOD8
LGN/LCN $002
Data M=0 P(S)=1 P(R)=2
000: 1002 4243 7261 7368 07
L4 WRITELINK
Record 89D
Seq 89
Type 71 Time 09:25:29.487673
SDN #002/%002
FEOK
RSP 6560 P1-6 %000000 %000026 %000036 %000005 %000005 %000000
X25AM Configuration and Management Manual—523424-004
6- 23
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.487673
SDN #002/%002
Wtread LCB 715C P1-6 %147403 %000026 %000116 %000006 %000020 %000000
L3 Pkt Out
Record 107D Seq 107
Type 50 Time 09:25:29.487673
SDN #002/%002 LEN #0020 GFI(1001) Q
MOD8 LGN/LCN $002
Data M=0 P(S)=3 P(R)=2
000: 9002 4602 0101 0400 0715 0800 0A00 0201
008: 037E 0D04
L3 Pkt In
Record 115D Seq 115
Type 51 Time 09:25:29.487673
SDN #002/%002 LEN #0003 GFI(0001)
MOD8
LGN/LCN $002
RR
P(R)=4
000: 1002 81
L3 Pkt Out
Record 121D Seq 121
Type 50 Time 09:25:29.487673
SDN #002/%002 LEN #0081 GFI(0001)
MOD8
LGN/LCN $002
Data M=0 P(S)=4 P(R)=2
000: 1002 4857 656C 636F 6D65 2074 6F20 7468
008: 6520 776F 6E64 6572 6675 6C20 776F 726C
010: 6420 6F66 2074 6572 6D69 6E61 6C20 696E
018: 666F 726D 6174 696F 6E2C 0020 6865 7265
L3 Pkt In
Record 126D Seq 126
Type 51 Time 09:25:30.487673
SDN #002/%002 LEN #0009 GFI(0001) MOD8 LGN/LCN $002
Data M=0 P(S)=2 P(R)=4
000: 1002 844C 6F67 6F66 66
L4 WRITELINK
Record 129D Seq 129
Type 71 Time 09:25:30.487673
SDN #002/%002
FEOK
RSP 715C P1-6 %000000 %000026 %000116 %000006 %000006 %000000
L4^LCB^In
Record 136D Seq 136
Type 70 Time 09:25:30.487673
SDN #002/%002
Read
LCB 62F0 P1-6 %147401 %000026 %000000 %000024 %000020 %000000
L3 Pkt In
Record 139D Seq 139
Type 51 Time 09:25:32.487673
SDN #002/%002 LEN #0005 GFI(0001)
MOD8 LGN/LCN $002
Clear
000: 1002 1300 00
L4 WRITELINK Record 144D Seq 144
Type 71 Time 09:25:32.487673
SDN #002/%002
FE #140 RSP 62F0 P1-6 %000214 %000026 %000000 %000024 %000000 %000000
L3 Pkt Out
Record 147D Seq 147
Type 50 Time 09:25:32.487673
SDN #000/%000 LEN #0003 GFI(0001)
MOD8 LGN/LCN $002
Clear^conf
000: 1002 17
L4^LCB^In
Record 154D Seq 154
Type 70 Time 09:25:33.76487673
SDN
#002/%002
Close LCB 5588 P1-6 %147413 %000026 %001124 %000000 %000020 %000000
L4 WRITELINK Record 155D
Seq 155
Type 71 Time 09:25:33.487673
SDN #002/%002
FEOK
RSP 5588 P1-6 %000000 %000026 %001124 %000000 %000000 %000000
Application Trace Analysis
You may want to check that LISTEN (beginning of operation) and WRITELINK
(completion) are identified by a common LCB address. You can tell that the X25AM I/)
process started a WRITEREAD by the common LCB address. For example:
1. At record 70, it posted the LISTEN (address 6560) to get the operation
(WRITEREAD).
X25AM Configuration and Management Manual—523424-004
6- 24
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).
The Q packet was not sent immediately after the SETMODE because Q packets
are normally saved until a WRITE or READ operation is posted to allow X25AM to
do several SETMODEs with one Q packet.
3. At record 78, the WRITE portion of the WRITEREAD operation (found at record
70) is performed when level 3 sends out a data packet to the PAD, which then
writes the data to the terminal in asynchronous mode.
4. At record 86, the terminal responds with data and the PAD forwards it in a data
packet, which level 3 verifies and forwards to our level 4 (ITI mode).
5. At record 89, the data from the incoming packet is returned to the application in a
WRITELINK operation (note the same LCB address, 6560). Then the operation is
completed. The application can determine that the operation completed
successfully by the presence of error FEOK (0).
The following is one more analysis example from the same trace. In this case, an error
is detected by level 3 and passed to the application.
1. At record 136, the application posts a READ in order to receive data (LCB address
62F0).
2. At record 139, the application receives a clear packet instead of data, meaning that
the network disconnected the circuit prematurely.
3. At record 144, the READ is completed by X25AM, which returns error 140 (circuit
disconnected). The application now has to do its own error recovery, which
probably means posting another CONTROL to wait for a new terminal to log onto
the PAD. The PAD forwards the CONTROL as a call request packet.
4. At record 147, level 3 continues, as the protocol dictates, to respond to the clear
packet by sending a clear confirmed packet. When the network and PAD receive
this packet, they know that the circuit is officially cleared and is available to the
next user.
Terminals and PAD Parameters
In ITI mode, which usually has a PAD device as an interface, a common problem is
how to set the PAD parameters correctly so that the PAD can communicate with a
particular terminal. The BPADPARMS and CPADPARMS (block and conversational
PAD parameters, respectively) should be set to match the terminal’s requirements. You
can also use SETMODEs to set these parameters. In ITI mode, some SETMODES
cause a Q data packet to be sent which signals the PAD to configure itself to the
parameters in the data portion of the packet. The Q packets generally follow a
successful call request-call accept sequence. They can also appear later as a result of
the SETMODEs.
X25AM Configuration and Management Manual—523424-004
6- 25
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.
L3 Pkt Out
Record 40D
Seq 40
Type 50 Time 09:25:28.487673
SDN #002/%002 LEN #0020 GFI(1001) Q MOD8 LGN/LCN $002
Data M=0 P(S)=0 P(R)=0
000: 9002 0002 0101 0400 0715 0800 0A00 0201
008: 037E 0D04
0
Q bit set
0
Packet type (Data packet)
2
SET type Q packet (Configures PAD to following parameters for
conversational mode:
(1,1) (4,0) (7,15) (8,0) (10,0) (2,1) (3,126) (13,4)
The Q bit is set in bit <3> of the first byte of a data packet. The fourth byte determines
the type of Q packet being sent.
SET means that the PAD should configure itself to these parameters and not send a
response. The rest of the packet is for the PAD parameters.
PAD parameters are defined in pairs. The first number of the pair specifies the type of
PAD parameter (that is, 1=escape mode, 2=echo mode). The second number contains
a value that modifies the mode (that is, 2,1 means echo turned on). The parameters
are defined in the X.28 ITU-T standard. For more information about PAD parameters,
consult Support Note S87061, “X25AM ITI OPTIONS CPADPARMS AND
BPADPARMS.”
Some PDNs supply their own PADs. These PDNs usually have their own special
network-related PAD parameters. These parameters usually come after the standard
X.28 parameters, following a National Parameter Marker (NPM) of 2 bytes, the first one
being zero. For example, Telenet’s default conversational parameters are:
(1,1) (4,0) (7,21) (8,0) (10,0) (2,1) (3,126) (0,33) (0,0) (1,2)
The National Parameter Marker for Telenet is (0,33). Everything after the (0,33) is a
Telenet-specific parameter, meaning that the descriptions are not in the ITU-T
specification; consult the Public Data Network (PDN) for meanings. For more
information about NETID, REMOTENET, and PAD parameter values, see Appendix D,
Using the NETID Modifier.
X25AM Configuration and Management Manual—523424-004
6- 26
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. Some configuration parameters can be
modified by the SCF ALTER LINE command to the X25AM subsystem; these are
noted in the table as SCF line attributes.
You can alter the timers T10 through T23 using X25AM I/O process modifiers. R10 is
the retry counter for T10, R11 corresponds to T11, and so on. The Txx timeout value is
the interval before an operation can be retried. The Rxx retry counter is the number of
times an operation can be retried.
Table 6-5. X.25 Configuration Parameters and X25AM I/O Process Modifiers
(page 1 of 2)
Operation
Device Modifier/
Line Attribute
Name
X25AM
Parameter
Probable
Value
K
4
Number of I frames
outstanding.
L2WINDOW
N1
1056
Maximum number of bits
in an I-frame, including
Address, Control, and
FCS bytes.
PACKETSIZE Modifier (For
PACKETSIZE=128 bytes,
N1=1056 bits)
N2
10
Maximum retransmission
count.
L2RETRIES
RETRIES is the SCF line
attribute.
T1
3 seconds
Retransmission timer.
L2TIMEOUT
T1TIMEOUT is the SCF
line attribute.
Meaning
T2
L2IDLETIMEOUT
IDLETIMEOUT is the SCF
line attribute.
Restart
T10
60 seconds
Timer set at DCE issue
of restart indication.
Txx
Call request
T11
180
seconds
Timer set at DCE issue
of incoming call.
Txx
Reset
T12
60 seconds
Timer set at DCE issue
of reset indication.
Txx
Clear
T13
60 seconds
Timer set at DCE issue
of CLEAR indication.
Txx
X25AM Configuration and Management Manual—523424-004
6- 27
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.
Txx
Clear
T23
180
seconds
Timer set at DTE issue
of clear request.
Txx
Restart
R10
1 retry
Number of restart
requests sent before T10
times out.
Rxx
Call request
R11
0 retry
No retries allowed. Call
is cleared.
Rxx
Reset
R12
1 retry
Number of reset
requests sent before T12
times out.
Rxx
Clear
R13
1 retry
Number of clear
requests sent before T13
times out.
Rxx
Restart
R20
1 retry
Number of restart
requests sent before T20
times out.
Rxx
Call request
R21
0 retry
No retries allowed. Call
is cleared.
Rxx
Reset
R22
1 retry
Number of reset
requests sent before T22
times out.
Rxx
Clear
R23
1 retry
Number of clear
requests sent before T23
times out.
Rxx
X25AM Configuration and Management Manual—523424-004
6- 28
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 ]...
DELETE [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , SUB [ subtype ] ]
DISCONNECT [ / OUT file-spec / ] [ SU su-name ]
INFO [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , DETAIL ] [ , SUB [ subtype ] ]
NAMES [ / OUT file-spec / ] [ object-spec ]
[ , SUB [ subtype ] ]
PRIMARY [ / OUT file-spec / ]
[ PROCESS process-name | LINE line-name] , number
START [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , SUB [ subtype ] ]
STATS [ / OUT file-spec / ] [ LINE line-name | SU su-name ]
[ , RESET ] [ , SUB [ subtype ] ]
X25AM Configuration and Management Manual—523424-004
A- 1
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 size
[ , SELECT select-spec
[ , TO file-spec
[ , WRAP
}
]
]
]
]
]
]
]
]... }
VERSION [ / OUT file-spec / ]
object-name
[ , DETAIL ]
X25AM Configuration and Management Manual—523424-004
A- 2
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. Table B-2 on page B-2 lists the X25AM
I/O process modifiers that have no equivalent SCF line attribute.
Table B-1. X25AM I/O Process Modifiers and Line Attributes (page 1 of 2)
X25AM I/O Process Modifier
Line Attribute
CALLUSERDATA
CUD
CIRCUITS
PVCRANGE
CLOCKnnnn
CLOCKSPEED
DCE
FRAMEMODE
DCECLOCK
CLOCKMODE
DSRTIMER
DSRTIMEOUT
DTE
FRAMEMODE
DTECLOCK
CLOCKMODE
EMSFORFRMR
EMSFORFRMR
EXTFORMAT
EXTFORMAT
INCOMINGCALLS
CALLS
LINEQUALITYTHRESHOLD
THRESHOLD
L2IDLETIMEOUT
IDLETIMEOUT
L2RETRIES
RETRIES
L2TIMEOUT
T1TIMEOUT
L3MOD8
L3MOD
L3MOD128
L3MOD
L3WINDOW
L3WINDOW
NETID
NETID
NOCALLS
CALLS
NOCALLUSERDATA
CUD
NOEXTFORMAT
EXTFORMAT
NOINCOMINGCALLS
CALLS
X25AM Configuration and Management Manual—523424-004
B- 1
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. X25AM I/O Process Modifiers Without Line Attribute
Equivalent (page 1 of 2)
X25AM I/O Process Modifier
Line Attribute
AUTOLOAD
None
DISABLEPVCOUTOFORDER
None
DRTIMEOUT
None
EMSFORCLEAR
None
ENABLECALLEDADDREXT
None
ENABLEPVCOUTOFORDER
None
EXTENDEDPOOLPAGES
None
FIFO
None
IDLECMDRR
None
IDLERESPRR
None
L2DISC
None
L2DOWNLINE
None
L2NODISC
None
L2WINDOW
None
L3RECVTHRUPUT
None
L3SENDTHRUPUT
None
MAXIOSIZE
None
NOAUTOLOAD
None
NOEMSFORCLEAR
None
NOL2DOWNLINE
None
X25AM Configuration and Management Manual—523424-004
B- 2
X25AM I/O Process Modifiers and Related SCF Line
Attributes
Table B-2. X25AM I/O Process Modifiers Without Line Attribute
Equivalent (page 2 of 2)
X25AM I/O Process Modifier
Line Attribute
NOREPORTDIRECT
None
NOSTRIPPARITY
None
NOSUSPENDSTATE
None
PACKETSIZE
None
POOLPAGES
None
REPORTDIRECT
None
Rxx
None
SENDSTOP
None
STRIPPARITY
None
TYPE
None
Txx
None
UNSOLF
None
X25V
None
X25AM Configuration and Management Manual—523424-004
B- 3
X25AM I/O Process Modifiers and Related SCF Line
Attributes
X25AM Configuration and Management Manual—523424-004
B- 4
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.
File-system, SCP, and other errors originating outside the SCF environment are
described in the documentation supporting the particular source of the error and are
not described here. Depending on your RVU, the SCF Reference Manual for G-Series
RVUs or the SCF Reference Manual for H-Series RVUs lists SCF error messages that
are common to all data communications subsystems. Table C-1 lists the formats of the
error message numbers and directs you to where you can find more information about
them.
Table C-1. Sources and Documentation of X25AM Error Messages
Number
Generated By
Manual
-nnnnn
SCP
•
•
005nn
X25AM subsystem
this manual
20nnn
SCF
•
•
SCF Reference Manual for G-Series RVUs
SCF Reference Manual for H-Series RVUs
SCF Reference Manual for G-Series RVUs
SCF Reference Manual for H-Series RVUs
You can also get information about error messages by using the SCF HELP command
(for example, by typing HELP X25AM 501). For more information about online help,
see the SCF Reference Manual for G-Series RVUs or SCF Reference Manual for
H-Series RVUs.
Message Descriptions
The X25AM error messages are listed by message number, from lowest to highest.
00500
X25AM E00500 Duplicate Attribute
Cause. An attribute has been entered twice in the command.
Effect. Command is not executed.
Recovery. Remove the duplicate attribute, and reissue the command.
X25AM Configuration and Management Manual—523424-004
C- 1
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. Make sure all the required attributes are present, and reissue the
command.
00504
X25AM E00504 Invalid number
Cause. The integer is not valid for the command.
Effect. Command is not executed.
Recovery. Check the command for a valid integer, and reissue the command with a
valid integer.
00505
X25AM E00505 LIKE must be entered before any other attribute
Cause. The LIKE option must precede the first attribute in the command string.
Effect. Command is not executed.
Recovery. Reissue the command with the LIKE option specified before the first
attribute in the command string.
X25AM Configuration and Management Manual—523424-004
C- 2
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. Make sure the number of values given does not exceed the limit allowed
for this attribute, and re-issue the command.
00510
X25AM E00510 STOP command is not completed because the
subdevice is open
Cause. The subdevice is open. The STOP command is rejected if it is issued against
an open subdevice or against a line with an open subdevice.
Effect. Command is not executed.
Recovery. Use the ABORT command or close the subdevice, and reissue the STOP
command.
00511
X25AM E00511 attribute-name and attribute-name are
inconsistent
Cause. The named attributes are inconsistent.
Effect. Command is not executed.
Recovery. Check for the proper attributes, and reissue the command.
X25AM Configuration and Management Manual—523424-004
C- 3
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.
00516
X25AM E00516 Disconnect not completed; circuit is PVC
Cause. The DISCONNECT command is not supported when the circuit is a PVC.
Effect. Command is not executed.
Recovery. Use the DISCONNECT command only with an SVC.
00517
X25AM E00517 EXTFORMAT is not allowed because packetsize is
less than 256
Cause. EXTFORMAT cannot be altered by using the SCF ALTER LINE command if
PACKETSIZE is less than 256.
Effect. Command is not executed.
Recovery. Issue the SCF ALTER LINE command with EXTFORMAT ON or OFF only
if PACKETSIZE is greater than or equal to 256.
X25AM Configuration and Management Manual—523424-004
C- 4
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. Command is not executed.
Recovery. Reenter the hexadecimal string with 32 or fewer characters.
X25AM Configuration and Management Manual—523424-004
C- 5
20084
X25AM Error Messages
X25AM Configuration and Management Manual—523424-004
C- 6
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. Full descriptions are given later in this appendix:
DATANET
DDXP
TWINET
X25NP
DATAPAC
PSS
TYMNET
X25SA
DATEXP
TELENET
UNINET
X25UD
DDN
TRANSPAC
X25
X25XA
NETID is used with lines and REMOTENET with subdevices. However, they both refer
to the same set. For example, if X25 is appropriate for a network, the value for NETID
and REMOTENET is X25.
You specify REMOTENET if you want a different set of network conventions to be used
for call request packets from a particular subdevice. If you do not specify a value for
REMOTENET, the same set of networking conventions is applied to both incoming and
outgoing calls.
Whether you actually use special port numbering, default PAD parameter values, or
network-dependent requirements from a set depends on which of the above-listed
NETID or REMOTENET names you specify.
NETID is both an X25AM I/O process modifier for SCF ADD DEVICE and ALTER
DEVICE commands to the WAN subsystem and an line attribute for the SCF ALTER
LINE command to the X25AM subsystem; REMOTENET is an SCF subdevice (ADD
SU, ALTER SU) attribute only.
The following definitions are used in the tables in Detail-Set Specifications on
page D-3:
•
•
•
•
An incoming call (DCE to DTE) is a maintaining call.
An outgoing call (DTE to DCE) is a call request.
The called (remote) address is SU DESTADDR + SU PORT NUMBER.
The calling (local) address is LINE SRCADDR.
If the remote DTE address includes a port number, you configure it as the last digits of
SU DESTADDR.
LINE SRCADDR is the format the network specifies for incoming calls. In many cases
this can be DNIC + NTN (network terminal number).
Addresses are defined in terms of SCF attributes.
X25AM Configuration and Management Manual—523424-004
D- 1
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.
NETID also determines whether X25AM appends the calling subdevice port
number to the LINE SRCADDR to form the calling address in call requests.
REMOTENET determines the location for the called DTE’s port number in a call
request (DTE to DCE). The port number can either be part of the called address or
part of the call user data.
Default PAD Profiles
•
•
•
•
•
PAD profiles are associated only with REMOTENET.
Some networks require a default PAD profile that differs from the standard default
profile. Even though only some values may be different, an entire profile must be
available.
Default parameter sets have an internal and an external (actual) format. The
Interactive Terminal Interface (ITI) protocol constructs the internal format. ITI also
translates the actual format.
If you alter parameters, the alterations affect the internal format. ITI then translates
the altered internal format. The alteration to the internal format may not result in
the same alteration to the external format. The internal format and external (actual)
formats may be different. The external (actual) format is sent to the PAD.
Complete PAD profiles are described in PAD Profiles on page D-8.
Special Network Requirements
Network-dependent facilities are associated only with NETID.
The 1976 TELENET national facility for flow-control negotiation is an example of a
special network requirement. Only Telenet uses it.
X25AM Configuration and Management Manual—523424-004
D- 2
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.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR + SU PORT NUMBER.
PAD Profile:
Standard default.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
Table D-2. X25NP (No Ports)
Call Addressing:
Configured SU PORT NUMBER should always be 0.
Incoming Call:
All calls go to port number 0.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR.
PAD Profile:
Standard default.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
Table D-3. X25SA (Subaddress)
Call Addressing:
SU PORT NUMBER is 0 to 4 digits, from 0 to 9999.
Leading zeros are deleted.
Incoming Call:
Called address is 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.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
X25AM Configuration and Management Manual—523424-004
D- 3
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.
PAD Profile:
Standard default.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
Table D-5. X25XA (Extended Address)
Call Addressing:
SU PORT NUMBER is 0 to 4 digits, from 0 to 9999.
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.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
Table D-6. DATANET (Like X25XA)
Call Addressing:
SU PORT NUMBER is 0 to 4 digits, from 0 to 9999.
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.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
X25AM Configuration and Management Manual—523424-004
D- 4
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. 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.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
Performed by PAD.
Parameters:
Special and national.
Other:
Turns on 1980 format priority calls.
Table D-8. DATEX-P
Call Addressing:
Defined by the network.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
Parameters:
Special profile.
Other:
Call accept packet does not include address and facilities lengths
fields when EXTENDEDFORMAT is OFF.
Table D-9. DDN (Like X25)
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.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR + SU PORT NUMBER.
PAD Profile:
Standard default.
Linefeed Echo:
X25AM I/O process performs.
Editing:
X25AM I/O process performs.
X25AM Configuration and Management Manual—523424-004
D- 5
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.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
Table D-11. PSS (Like X.25)
Call Addressing:
SU PORT NUMBER is 0 to 2 digits.
Incoming Call:
Called address is LINE SRCADDR + SU PORT NUMBER.
A 0- to 2-digit port number is expected.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR + SU PORT NUMBER.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
Other:
Call accept.
Table D-12. TELENET (Like X.25)
Call Addressing:
SU PORT NUMBER is 0 to 2 digits.
Incoming Call:
Called address is LINE SRCADDR + SU PORT NUMBER.
A 0- to 2-digit port number expected.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR + SU PORT NUMBER.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
Parameters:
Special and national.
Other:
Special code for TELENET 1976 national facilities for packet size and
window negotiation. Use only for 1976 TELENET service. Use X25
for 1980 TELENET service.
X25AM Configuration and Management Manual—523424-004
D- 6
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.
Editing:
X25AM I/O process performs.
Other:
Allows LCN 0 for first PVC or first SVC LCN.
Table D-14. TWINET (Like X25NP)
Call Addressing:
Configured SU PORT NUMBER should always be 0.
PAD Profile:
All calls go to port number 0.
Linefeed Echo:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR.
Editing:
Standard default.
Parameters:
X25AM I/O process performs.
Other:
X25AM I/O process performs.
Table D-15. TYMNET (Like X.25)
Call Addressing:
SU PORT NUMBER is 0 to 2 digits.
Incoming Call:
Called address is LINE SRCADDR + SU PORT NUMBER.
A 0- to 2-digit port number is expected.
Call Request:
Called address is SU DESTADDR.
Calling address is LINE SRCADDR + SU PORT NUMBER.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
X25AM Configuration and Management Manual—523424-004
D- 7
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.
PAD Profile:
Standard default.
Linefeed Echo:
Performed by PAD.
Editing:
X25AM I/O process performs.
PAD Profiles
The two notes below apply to all of the PAD profile tables:
(*)
This is a configurable parameter. The parameter value depends on the
configuration of the subdevice.
(***)
The PAD parameter separator is used to differentiate between the
standard X.3 parameters and the network-specific parameters.
Parameters preceding the national options marker are standard X.3
parameters. Parameters following the parameter separator are networkspecific parameters used and defined only for that particular network.
Standard PAD Profiles
Table D-17, Table D-18 on page D-9, and Table D-19 on page D-10 provide
descriptions of the standard PAD profiles.
Conversational Mode
Table D-17. Standard PAD Profiles for Conversational Mode (page 1 of 2)
X.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0 or 1 (*)
Selection of data-forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
X25AM Configuration and Management Manual—523424-004
D- 8
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
Line feed insertion after receipt of carriage
return from terminal
13,0
13,0 or 4 (*)
X25AM Configuration and Management Manual—523424-004
D- 9
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,0
1,0
Echo
2,0
2,0
Selection of data forwarding conditions
3,0
3,0
Idle timer
4,2
4,2
Ancillary device control
5,0
5,0
Suppression of network messages
6,0
6,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Padding after receipt of carriage return from
terminal
9,0
9,0
Line folding
10,0
10,0
Flow control of PAD by terminal
12,0
12,0
Line feed insertion after receipt of carriage
return from terminal
13,0
13,0
DATANET PAD Profiles
Same as the Standard PAD Profiles on page D-8.
X25AM Configuration and Management Manual—523424-004
D -10
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0 or 2,1
Selection of data forwarding characters
3,126
3,126 or 3,2
Selection of idle timer delay
4,0
4,0
Ancillary device control
5,0
5,0
Control of PAD service signals
6,1
6,1
Selection of operation of PAD on receipt of
BREAK signal
7,21
7,21
Padding after carriage return
9,0
9,0
Flow control of PAD
12,0
12,0
Line feed insertion after carriage return
13,0
13,0
Editing
15,1
15,1
Character delete
16,0
16,0
Line delete
17,0
17,0
Line display
18,0
18,0
Editing PAD service signals
19,2
19,2
Parity treatment
21,3
21,3
X25AM Configuration and Management Manual—523424-004
D -11
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,126
3,126
Idle timer
4,0
4,0
Ancillary device control
5,0
5,0
Control of PAD service signals
6,1
6,1
Break handling
7,21
7,21
Padding after carriage return
9,0
9,0
Flow control of PAD
12,0
12,0
Line feed insertion after carriage return
13,4
13,4
Editing
15,1
15,1
Character delete
16,8
16,8
Line delete
17,24
17,24
Line display
18,0
18,0
Editing PAD service signals
19,2
19,2
Parity treatment
21,3
21,3
X25AM Configuration and Management Manual—523424-004
D -12
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,0
1,0
Echo
2,0
2,0
Selection of data forwarding conditions
3,0
3,0
Idle timer
4,2
4,2
Ancillary device control
5,0
5,0
Suppression of network messages
6,0
6,0
Break handling
7,21
7,0 or 21 (*)
Padding after receipt of carriage return from
terminal
9,0
9,0
Flow control of PAD by terminal
12,0
12,0
Line feed insertion
13,0
13,0
DATAPAC character delete parameter
15,0
15,0
DATAPAC line delete parameter
16,0
16,0
Additional data forwarding conditions
17,0
17,0
Additional data forwarding conditions
18,0
18,0
Parity treatment
19,0
19,0
Output pending timer
21,0
21,0
X25AM Configuration and Management Manual—523424-004
D -13
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0 or 1 (*)
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
Line feed insertion after receipt of carriage
return from terminal
13,4
PAD parameter separator
0,0
0,0 (***)
Additional data forwarding conditions
121,0
121,0
Additional data forwarding conditions
122,0
122,0
Line feed insertion after receipt of carriage
return from terminal
126,4
126,4
X25AM Configuration and Management Manual—523424-004
D -14
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
PAD parameter separator
0,0
0,0 (***)
Additional data forwarding conditions
121,0
121,0
Additional data forwarding conditions
122,0
122,0
X25AM Configuration and Management Manual—523424-004
D -15
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,0
3,0
Idle timer
4,2
4,2
Ancillary device control
5,0
5,0
Suppression of network messages
6,0
6,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Padding after receipt of carriage return from
terminal
9,0
9,0
Line folding
10,0
10,0
Flow control of PAD by terminal
12,0
12,0
PAD parameter separator
0,0
0,0 (***)
DATEX-P character delete parameter
118,0
118,0
Parameter
119,0
119,0
Line display
120,0
120,0
Additional data forwarding conditions
121,0
121,0
Additional data forwarding conditions
122,0
122,0
Parity treatment
123,1
123,1
Output pending timer
125,0
125,0
Line feed insertion after receipt of carriage
return from terminal
126,0
126,0
DATEX-P line delete
DDN PAD Profiles
Same as the Standard PAD Profiles on page D-8.
DDXP PAD Profiles
Same as the Standard PAD Profiles on page D-8.
PSS PAD Profiles
Same as theTRANSPAC PAD Profiles on page D-19.
X25AM Configuration and Management Manual—523424-004
D -16
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0 or 1 (*)
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
PAD parameter separator
0,33
0,33 (***)
Line feed insertion after receipt of carriage
return from terminal
1,0
1,0 or 4 (*)
6510 Terminal in Block Mode
Table D-27. TELENET PAD Profiles for 6510 Terminal in Block Mode
X.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
PAD parameter separator
0,33
0,33 (***)
Line feed insertion after receipt of carriage
return from terminal
1,0
1,0 or 4 (*)
X25AM Configuration and Management Manual—523424-004
D -17
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,0
1,0
Echo
2,0
2,0
Selection of data forwarding conditions
3,0
3,0
Idle timer
4,2
4,2
Ancillary device control
5,0
5,0
Suppression of network messages
6,0
6,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Padding after receipt of carriage return from
terminal
9,0
9,0
Line folding
10,0
10,0
Flow control of PAD by terminal
12,0
12,0
PAD parameter separator
0,33
0,33 (***)
Line feed insertion after receipt of carriage
return from terminal
1,0
1,0
Network message display
2,0
2,0
Line feed padding
10,0
10,0
Tab padding
11,0
11,0
Vertical terminal options
18,0
18,0
Network usage display
37,0
37,0
DCE to DTE flow control
41,0
41,0
DTE to DCE flow control
54,0
54,0
8-bit transparency
63,1
63,1
X25AM Configuration and Management Manual—523424-004
D -18
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0 or 1 (*)
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
Line feed insertion after receipt of carriage
return from terminal
13,0
13,4 (*)
6510 Terminal in Block Mode
Table D-30. TRANSPAC PAD Profiles for 6510 Terminal in Block Mode
X.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,1
1,1
Echo
2,0
2,0
Selection of data forwarding conditions
3,126
3,2 or 126 (*)
Idle timer
4,0
4,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Line folding
10,0
10,0
Line feed insertion after receipt of carriage
return from terminal
13,0
13,4 (*)
X25AM Configuration and Management Manual—523424-004
D -19
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.3 Parameter
Internal Parameter
Code,Value
Actual Parameter
Code,Value
Escape to command mode
1,0
1,0
Echo
2,0
2,0
Selection of data forwarding conditions
3,0
3,0
Idle timer
4,2
4,2
Ancillary device control
5,0
5,0
Suppression of network messages
6,0
6,0
Break handling
7,21
7,0 or 21 (*)
Discard output
8,0
8,0
Padding after receipt of carriage return from
terminal
9,0
9,0
Line folding
10,0
10,0
Flow control of PAD by terminal
12,0
12,0
Line feed insertion after receipt of carriage
return from terminal
13,0
13,0
TWINET PAD Profiles
Same as the Standard PAD Profiles on page D-8.
TYMNET PAD Profiles
Same as the Standard PAD Profiles on page D-8.
UNINET PAD Profiles
Same as the Standard PAD Profiles on page D-8.
X25AM Configuration and Management Manual—523424-004
D -20
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. Your application can execute successfully only if the
TELENET-specific parameter 57 with a value of 2 is sent to the PAD. Because a
network-specific parameter is required, you need to define a CPADPARMS list. The
CPADPARMS list must contain all of the default parameter codes as well as the
specific value 2 for parameter 57. Your application issues SETMODEs to change the
echo and line-feed insertion parameters. When you add the subdevice (with SCF), the
CPADPARMS parameter list is specified in the following format:
CPADPARMS (1,1 4,0 7,21 8,0 10,0 2,0 3,126 0,33 1,0 57,2)
2,0 is the echo parameter (X.3 parameter 2) and is in the format X25AM will recognize
for SETMODEs.
1,0 is the line-feed insertion parameter (TELENET parameter 1) and is in the format
X25AM will recognize for SETMODEs. The parameter code is preceded by the 0,0 flag
indicating that this is a modifiable parameter.
57,2 is the additional TELENET parameter required for the application. Note that this
parameter is not modifiable because X25AM does not recognize it.
DATAPAC Example
Suppose you need to define a 6510 block-mode terminal, subdevice type and subtype
6,1, that will be connected through a DATAPAC PAD. A DATAPAC-specific parameter,
parameter 100 with a value of 5, must be sent to the PAD if the application is to
execute successfully. Your application changes various parameter values with
SETMODE calls. When you add the subdevice (with SCF), the BPADPARMS
parameter list is specified in the following format:
BPADPARMS (1,1 2,0 4,0 7,21 8,0 10,0 3,0 100,5)
Standard Example
Suppose you need to define a standard 6530 block-mode terminal with a subdevice
type and subtype of 6,4. The terminal will be using the TRANSPAC network and no
special network-specific parameters are needed. The default list of parameters is
sufficient. In this case, it is not necessary to define a BPADPARMS list. The standard
default parameter list contains all of the required X.3 and network-specific parameters
in the format X25AM recognizes for SETMODEs.
X25AM Configuration and Management Manual—523424-004
D -21
Using the NETID Modifier
X25AM Configuration and Management Manual—523424-004
D -22
Standard Example
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.
In addition to this appendix, the following conversion information is available to help
you:
•
•
The MIGSCF program can automatically convert to SCF any Configuration Utility
Program (COUP) commands entered at the TACL prompt or found within a
command or OBEY file. MIGSCF documentation can be found in an appendix of
the SCF Reference Manual for G-Series RVUs, or at
$SYSTEM.ZMIGSCF.MANUAL, a read-only TEDIT file.
From within SCF, if you enter a COUP command, SCF displays information to help
you convert the command to its SCF equivalent.
WAN Subsystem
For systems running D-series RVUs, X25AM lines are created with the System
Generation (SYSGEN) program. SCF can be used to alter and monitor lines. The
Dynamic System Configuration’s (DSC) COUP program is used to start X25AM lines
and processes.
For systems running G-series RVUs, the X25AM I/O processes are configured and
started with SCF commands to the WAN subsystem. The WAN subsystem SCF
commands that are relevant to the X25AM subsystem are described briefly in
Section 3, Configuring an X25AM Subsystem. For detailed information about the WAN
subsystem, see the WAN Subsystem Configuration and Management Manual.
On systems running G-series RVUs, the WAN subsystem provides the functions that
COUP and SYSGEN provide on the systems running D-series RVUs. Specifically, the
WAN subsystem allows you to:
•
•
•
•
Define X25AM I/O processes with the modifiers that affect their operation
Start and stop X25AM I/O processes
Alter or delete X25AM I/O processes
Monitor X25AM processes and restart them if both the primary and backup
processes fail
X25AM Configuration and Management Manual—523424-004
E- 1
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. Defining CONFTEXT Paragraph Information on G-Series Systems
CONFTEXT Paragraph
G-Series Definition
CONTROLLERS
SWAN concentrator is configured through the WAN
subsystem.
DEFINES
Customizes a profile to be used later when configuring
DEVICE object type.
PATHS
This information is not applicable for systems running Gseries RVUs.
PERIPHERALS
I/O processes are configured with SCF commands to the
WAN subsystem.
ALLPROCESSORS
Still exists in G-series CONFTEXT file.
The DEFINES Paragraph
The DEFINES paragraph allows you to customize a profile to be used later when
configuring a DEVICE object type. You can summarize X25AM line modifiers that you
may wish to use repeatedly.
For more information about WAN subsystem configuration, see the WAN Subsystem
Configuration and Management Manual. For more information about Kernel subsystem
configuration, see the SCF Reference Manual for the Kernel Subsystem.
Profile for G-Series X25AM Subsystem
For systems running D-series RVUs, default values for line types are contained in
SYSGEN macros. For systems running G-series RVUs, profiles are used in a similar
way. However, for the X25AM subsystem, the only profile supported for use with
systems running G-series RVUs is called PX250061.
For more information about creating profiles, see Section 3,
Configuring an X25AM Subsystem and the WAN Subsystem Configuration and
Management Manual.
X25AM Configuration and Management Manual—523424-004
E- 2
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.
The following COUP commands have no SCF equivalent and cannot be used with
G-series systems:
CONFIG
INFO CONTROLLER
INFO MF_CONTROLLERS
INFO PATH
RESET
SHOW
TIME
For the X25AM subsystem, only the DEVICE object type has an equivalent SCF
DEVICE object type.
Managing an X25AM Network
For systems running G-series RVUs, the Subsystem Control Facility (SCF) for the
WAN subsystem replaces both PUP and DSC.
For NonStop S-series systems, Compaq TSM replaced the system maintenance
functions provided by the Syshealth toolkit, HP Tandem Maintenance and Diagnostic
Subsystem (TMDS), and the Remote Maintenance Interface (RMI) product. For more
information about TSM, see the TSM Online User Guide.
For G06.21, the HP Open System Management (OSM) product replaces TSM as the
system management tool of choice for NonStop S-series systems. OSM offers a
browser-based interface that improves scalability and performance and overcomes
other limitations that exist in TSM. TSM is still supported, but OSM is required to
support new functionality in G06.21 and later.
For more information about OSM, see the OSM Migration Guide and the OSM User’s
Guide.
X25AM Configuration and Management Manual—523424-004
E- 3
Moving to G-Series or H-Series RVUs
Managing an X25AM Network
X25AM Configuration and Management Manual—523424-004
E- 4
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. Coding of the Diagnostic Code Field
Cause Code Bits
Packet
8 7 6 5 4 3 2 1 Orginated By
Packet Type
CLEAR
REQUEST,
CLEAR
INDICATION,
RESET
REQUEST,
RESET
INDICATION
RESTART
REQUEST,
RESTART
INDICATION
Diagnostic Code
0 0 0 0 0 0 0 0 DTE
Specified in ITU-T
Recommended
Diagnostic Codes
1 0 0 0 0 0 0 0 DTE
DTE-specific diagnostics
0 [at least one 1]
Public packet
switched network
Specified in ITU-T
Recommended
Diagnostic Codes
1 [at least one 1]
Public packet
switched network
Specified in ITU-T
Recommended
Diagnostic Codes
0 0 0 0 0 0 0 0 DTE
Specified in ITU-T
Recommended
Diagnostic Codes
1 0 0 0 0 0 0 0 DTE
DTE-specific diagnostics
0 [at least one 1]
Public Network: specified
in ITU-T Recommended
Diagnostic Codes
Local network
(public or private)
Private Network: specified
in ITU-T Recommended
Diagnostic Codes
DIAGNOSTIC,
REGISTRATIONC
ONFIRMATION
DTE
Specified in ITU-T
Recommended
Diagnostic Codes
Local network
(public or private)
Public Network: specified
in ITU-T Recommended
Diagnostic Codes
Private Network: specified
in ITU-T Recommended
Diagnostic Codes
X25AM Configuration and Management Manual—523424-004
F-1
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).
The first diagnostic in each grouping is a generic diagnostic and can be used in place of the
more specific diagnostics within the grouping. The decimal 0 diagnostic code can be used in
situations where no additional information is available.
Table F-2. No Additional Information Problems
Hexadecimal
Decimal
Description
00
0
No additional information
01
1
Invalid P(S)
02
2
Invalid P(R)
Table F-3. Packet Type Invalid Problems
Hexadecimal
Decimal
Description
10
16
Packet type invalid
11
17
For state r1
12
18
For state r2
13
19
For state r3
14
20
For state p1
15
21
For state p2
16
22
For state p3
17
23
For state p4
18
24
For state p5
19
25
For state p6
1A
26
For state p7
1B
27
For state d1
1C
28
For state d2
1D
29
For state d3
X25AM Configuration and Management Manual—523424-004
F-2
ITU-T Recommended Diagnostic Codes
Diagnostic and Cause Codes
Table F-4. Packet Not Allowed Problems
Hexadecimal
Decimal
Description
20
32
Packet not allowed
21
33
Unidentifiable packet
22
34
Call on one-way logical channel
23
35
Invalid packet type on a PVC
24
36
Packet on unassigned logical channel
25
37
Reject not subscribed to
26
38
Packet too short
27
39
Packet too long
28
40
Invalid general format identifier
29
41
Restart or registration packet with nonzero in bits 1 to 4 of octet
1, or bits 1 to 8 of octet 2
2A
42
Packet type not compatible with facility
2B
43
Unauthorized interrupt confirmation
2C
44
Unauthorized interrupt
2D
45
Unauthorized reject
Table F-5. Time Expired
Hexadecimal
Decimal
Description
30
48
Time expired
31
49
For incoming call
32
50
For clear indication
33
51
For reset indication
34
52
For restart indication
35
53
For call deflection
X25AM Configuration and Management Manual—523424-004
F-3
ITU-T Recommended Diagnostic Codes
Diagnostic and Cause Codes
Table F-6. Call Setup, Call Clearing, or Registration Problems
Hexadecimal
Decimal
Description
40
64
Call setup, call clearing, or registration problem
41
65
Facility/registration code not allowed
42
66
Facility parameter not allowed
43
67
Invalid called DTE address
44
68
Invalid calling DTE address
45
69
Invalid facility/registration length
46
70
Incoming call barred
47
71
No logical channel available
48
72
Call collision
49
73
Duplicate facility requested
4A
74
Non-zero address length
4B
75
Non-zero facility length
4C
76
Facility no provided when expected
4D
77
Invalid ITU-T-specified DTE facility
4E
78
Maximum number of call redirections or call deflections
exceeded
Table F-7. Miscellaneous Diagnostic Codes
Hexadecimal
Decimal
Description*
50
80
Miscellaneous
51
81
Improper cause code from DTE
52
82
Nonoctet aligned
53
83
Inconsistent Q bit setting
54
84
NUI problem
* The meanings of these diagnostic codes are different if you are using a SNAX-over-X.25 (SOX) configuration.
Refer to Table F-9 on page F-5
X25AM Configuration and Management Manual—523424-004
F-4
SNAX-Over-X.25 (SOX) Configuration Codes
Diagnostic and Cause Codes
Table F-8. International Problems
Hexadecimal
Decimal
Description
70
112
International problem
71
113
Remote network problem
72
114
International protocol problem
73
115
International link out of order
74
116
International link busy
75
117
Transit network facility problem
76
118
Remote network facility problem
77
119
Temporary routing problem
78
120
Unknown called DNIC
79
121
Maintenance action*
* This diagnostic code may also apply to a maintenance action within a national network.
SNAX-Over-X.25 (SOX) Configuration Codes
The following codes replace the codes in Table F-7 on page F-4 only if you are using a
SNAX-over-X.25 (SOX) configuration.
Table F-9. Clear and Reset Diagnostic Codes for SOX Configuration
Hexadecimal
Decimal
Description
50
80
QLLC error (nonspecific)
51
81
QLLC undefined Control field
52
82
QLLC unexplained Control field
53
83
QLLC missing Information field
54
84
QLLC undefined Information field
55
85
QLLC Information field too long
56
86
QLLC Frame Reject (FRMR) received
57
87
QLLC HDR (Header) invalid
58
88
QLLC data received in the wrong state
59
89
QLLC timeout
EA
234
QLLC invalid protocol ID (Clear Diag only)
X25AM Configuration and Management Manual—523424-004
F-5
Diagnostic and Cause Codes
SNAX-Over-X.25 (SOX) Configuration Codes
X25AM Configuration and Management Manual—523424-004
F-6
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.
Adding an X25AM Profile
With SCF for the systems running G-series or H-series RVUs, the X25AM profile object
replaces the function of the system generation (SYSGEN) program. The following SCF
command file adds the default X25AM profile without modification:
ADD PROFILE $ZZWAN.#PX250061, FILE $SYSTEM.SYS00.PX250061
The following SCF command file adds the X25AM profile but modifies the default for
circuits from 32 to 510:
ADD PROFILE $ZZWAN.#px25c510, FILE $SYSTEM.SYS00.PX250061, &
CIRCUITS 510
X25AM Configuration and Management Manual—523424-004
G- 1
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.X25OBJ, &
TYPE (61,63)
PROGRAM $SYSTEM.CSS00.C1096P00, &
RECSIZE 128, &
CLIP 3, &
LINE 0, &
ADAPTER S01, &
PATH A, &
CIRCUITS 510 &
MAXIOSIZE 32767, &
EXTENDEDPOOLPAGES 2047, &
PACKETSIZE 256, &
STARTDOWN
ADD DEVICE $ZZWAN.#X25S1, &
CPU 0, &
ALTCPU 1, &
PROFILE PX25C510, &
IOPOBJECT $SYSTEM.SYS00.X25OBJ, &
TYPE (61,63)
PROGRAM $SYSTEM.CSS00.C1096P00, &
RECSIZE 128, &
CLIP 3, &
LINE 1, &
ADAPTER S01, &
PATH A, &
MAXIOSIZE 32767, &
EXTENDEDPOOLPAGES 2047, &
PACKETSIZE 256, &
DCE, &
STARTDOWN
Starting X25AM I/O Processes
After adding the X25AM profile and the X25AM I/O processes, you start the I/O
processes $ZZWAN.#X25P1 and $ZZWAN.#X25S1. The following example is an SCF
command file for starting both X25AM I/O processes.
START DEVICE $ZZWAN.#x25p1
START DEVICE $ZZWAN.#x25s1
STATUS DEVICE $ZZWAN.#x25p1
STATUS DEVICE $ZZWAN.#x25s1
X25AM Configuration and Management Manual—523424-004
G- 2
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............ 1
,302
Starting X25AM Lines
After starting the X25AM I/O processes, you start the X25AM lines that are controlled
by the I/O processes (in this example, $ZZWAN.#X25P1 and $ZZWAN.#X25S1). The
following example is an SCF command file for starting both X.25 lines.
START LINE $x25p1
START LINE $x25s1
STATUS LINE $x25p1, DETAIL
STATUS LINE $x25s1, DETAIL
The STATUS commands result in the following displays:
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,97)
BPIN....... ( 1,70)
156
NumSU...... 0
510
Path....... B
ON
CTS........ ON
61
Sub-Type... 63
OFF
X25AM Detail Status Line $X25S1
Preferred IP....... 192.168.005.084
Track ID.... X017JJ
CMG........
State....... STARTED
PPIN.......
LinkState... READY
LDEV.......
InUse....... NO
Circuits...
DCD......... ON
DSR........
CMG LDev.... 151
Type.......
PriTrace.... OFF
BkpTrace...
Alternate IP...... 192.168.007.084
$ZZW00
I/O ADDR.. ( 0,4,3,1)
( 0,77)
BPIN....... ( 1,2 )
146
NumSU...... 0
510
Path....... A
ON
CTS........ ON
61
Sub-Type... 63
OFF
X25AM Configuration and Management Manual—523424-004
G- 3
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.#term1, PROTOCOL PTP, DEVTYPE (9,0), &
RECSIZE 80, RPOA (125, 300, 5000)
STATUS SU $x25p1.#term1
INFO SU $x25p1.#term1, DETAIL
The STATUS and INFO commands for $X25P1.#TERM result in the following displays:
X25AM STATUS
Name
$X25P1.#TERM
SU
State
STARTED
X25AM Detail Info SU
DevType
6,0
Recsize
80
SUnum
2
Port
0
LCNnum
$X25P1.#TERM
*AcceptChg.... OFF
*DevType....
*PVC..........
*Parity.....
*Port......... 0
*Protocol...
*RexmitTimeout 0:20.00 *ReverseChg.
*CUG..........
*Nullfill...
*CUGType...... BASIC
*BCUG.......
*DestAddr.....
*Negotiate....
Associateline
*LocalAddrExt.
*RemoteAddrExt
*CUD..........
*RPOA..........125 , 300 , 5000
*Bpadparms....
*Cpadparms....
( 6,0 )
NONE
ITI
OFF
OFF
*Recsize..........
*Pricall..........
*ParityChk........
*Thruput..........
*RemoteNet........
*Transitdelay.....
*LocalAddrExtType.
*RemoteAddrExtType
*Page6520BlkSize
X25AM Configuration and Management Manual—523424-004
G- 4
80
OFF
OFF
( 4,4 )
X25XA
0
0
256
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.....
*Negotiate....
Associateline
*LocalAddrExt.
*RemoteAddrExt
*CUD..........
*RPOA..........125 , 300 , 5000
*Bpadparms....
*Cpadparms....
( 9,0 )
NONE
PTP
OFF
OFF
*Recsize..........
*Pricall..........
*ParityChk........
*Thruput..........
*RemoteNet........
*Transitdelay.....
*LocalAddrExtType.
*RemoteAddrExtType
*Page6520BlkSize
X25AM Configuration and Management Manual—523424-004
G- 5
80
OFF
OFF
( 4,4 )
X25XA
0
0
0
Configuration Files for the X25AM Subsystem
Adding Subdevices to an X25AM Line
X25AM Configuration and Management Manual—523424-004
G- 6
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. An I/O process that allows applications running on a NonStop NS-series or
NonStop S-series server to communicate with other systems or devices. X25AM is an
access method for X.25 communications.
address. Unique network designation that identifies a device, as described in X.121.
ASCII. American Standard Code for Information Interchange. Standard method of coding
data, consisting of 7 bits for each character plus 1 parity bit.
attribute. In SCF, an attribute is a characteristic that can be specified for an X25AM line or
subdevice. For example, most of the optional network facilities can be specified as
either a line or subdevice attribute, using SCF.
baud. Unit of signaling speed equal to the number of signal events per second. Not
necessarily bits per second (bps).
binary synchronous communications (BSC). Communications protocol using a standard
set of control characters and control character sequences for synchronous
communications.
bit.
Binary digit. Smallest unit of information, represented as a 1 or a 0.
block mode. A type of operation in which a device saves characters and attempts to
transmit them only when the ENTER or RETURN key is pressed. The block mode of a
terminal supports page-mode applications. See also conversation mode.
buffer. Area of storage temporarily reserved for performing an input/output (I/O) operation,
into which data is read or from which data is written.
byte. String of 8 bits.
call accepted packet. Packet that a remote entity sends to the network in response to an
incoming call packet, if a circuit can be established.
call clearing. Descriptive phrase for the activities required for disconnecting a virtual circuit.
X25AM Configuration and Management Manual—523424-004
Glossary- 1
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. Descriptive phrase for the activities required to establish a virtual circuit,
involving call request, incoming call, call accepted, and call connected packets. Data
transmission between the caller and the remote entity can begin after the circuit is
established.
called address. Network address of a remote device or system (the entity being called).
calling address. Network address of a local device or system (the entity making the call).
call user data (CUD). Optional field, which can be included in call setup packets, such as
call request and incoming call. In standard format packets, the CUD can be specified
for a maximum of 16 bytes, depending on the protocol configured for the particular
subdevice. If the extended packet format has been configured, a CUD field of up to
128 packets can be sent, using the fast select optional facility.
channel. A path over which data and messages are sent.
character. Letter, figure, number, punctuation mark, or another symbol contained in a
message or used in a control function.
circuit. Means of two-way communications between two network entities.
clear-confirmation packet. Packet sent by the network to the caller when a call has been
disconnected in response to the caller request to disconnect.
clear-indication packet. Packet sent by the network when a call is disconnected.
clear-request packet. Packet sent by the caller to disconnect the call.
CLIP. See communications line interface processor (CLIP).
clock. In synchronous transmission, the source for timing signals.
combined station. A station configuration, connecting a point-to-point link, where each
station shares link-management responsibility. Either station can transmit to the other
without first seeking permission to do so. This is the type of configuration prescribed by
LAPB for X.25 connections. See also primary station and secondary station.
common carrier. Company that furnishes communications services to the public and is
regulated by appropriate state or federal agencies.
X25AM Configuration and Management Manual—523424-004
Glossary- 2
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. Collection of hardware and software that provides a specific
communications function (for example, communications between a NonStop NS-series
or NonStop S-series server and an X.25 network).
CONFTEXT file. On G-series and H-series RVUs, the CONFTEXT file consists of one or
two paragraphs: DEFINES (optional) and ALLPROCESSORS.
conversation mode. Data transmission mode for a terminal. Transmitted data messages
consist of single characters instead of groups of characters.
CUD. See call user data (CUD).
CUG. Closed user group. Optional network facility that restricts calls to members assigned
to a group.
Data Network Identification Code (DNIC). Part of an ITU-T numbering scheme that
provides each network with a unique address. The DNIC contains a three-digit data
country code (DCC) and a one-digit network identification (NI) code. See also X.121.
data packet. Packet that contains data.
DCE. Data circuit-terminating equipment. In the context of the X.25 standard, the network is
identified as a DCE. X25AM can be configured as either DCE or DTE. The term DCE is
also used to refer to a modem.
destination address. See called address.
device. Physical or logical system component. For X25AM, a line is a device defined in the
CONFTEXT file.
DISC. Disconnect. Link-level frame used for call disconnection.
DNIC. See Data Network Identification Code (DNIC).
D-series system. A system running a D-series version of the NonStop Kernel operating
system. A D-series system can have more than 256 concurrent processes in a CPU.
DSR. Data set ready. Signal coming from a modem which usually indicates to the computer
equipment that the modem is powered on.
DTE. Data terminal equipment. The user’s computer system; that is, equipment connected
by data circuit-terminating equipment (DCE) to telephone company lines or data
circuits. A DTE is usually a terminal or a computer. With X.25AM, the
NonStop NS-series or NonStop S-series server can function as either DTE or DCE.
X25AM Configuration and Management Manual—523424-004
Glossary- 3
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. Message unit that consists of a sequence of bits bracketed by beginning and ending
flag sequences. It can contain packets.
frame layer. Also called the link level. It is the X.25 protocol description for the link access
procedures for the link between the network and the computers, terminals, or other
devices.
FRMR. Frame Reject. A response frame indicating the receipt of an invalid frame format,
invalid command, or invalid response.
full-duplex. Method of serial communications in which the data flow between two points can
occur in both directions simultaneously.
half-duplex. Method of serial communications in which the data flow between two points
can occur in only one direction at a time.
hex. Hexadecimal. Base-16 numbering system.
I-frame. Information frame. Link-level frame that contains a packet.
incoming call packet. Packet that the network sends to a remote entity in response to
receiving a call request packet addressed to that entity.
interface. Shared boundary defined by common interconnection characteristics.
International Organization for Standardization (ISO). International Organization for
Standardization. ISO is an international body that drafts, discusses, proposes, and
specifies standards for network protocols. ISO is best known for its seven-layer
reference model that describes the conceptual organization of protocols.
interrupt. Signal used by a device to stop the current task of a subordinate device. Once
stopped, the subordinate device waits for the primary device to send information to it.
invitation-to-clear packet. Sometimes sent as the last data packet or after the last data
packet to request the disconnection of the call, to solve the problem of having a clear
packet overtake a data packet (causing a call to be disconnected before all of the data
is received).
X25AM Configuration and Management Manual—523424-004
Glossary- 4
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. International Telecommunication Union (ITU), and its Telecommunication
Standardization Sector (ITU-T), which is responsible for studying technical, operating,
and tariff questions and issuing Recommendations on them with a view to
standardizing telecommunications on a worldwide basis.
LAP. See Link Access Procedure (LAP) and Link Access Procedure in a Balanced System
(LAP and LAPB).
LAPB. See Link Access Procedure (LAP) and Link Access Procedure in a Balanced System
(LAP and LAPB).
leased line. Telephone line reserved for exclusive (private) use of the leasing customer.
link. Call or transmission path (including all equipment) between a sender and receiver.
Link Access Procedure (LAP) and Link Access Procedure in a Balanced System (LAP
and LAPB). Procedures used in a packet-switching network for data interchange
across the access link between a network and the computers, terminals, or other
devices. Responsible for activities involving framing, synchronization control, and errordetection.
link layer. See frame layer.
logical channel. Means of two-way communications between two network entities.
logical channel number. Number assigned to a logical channel to uniquely identify it.
logical device. Device that can be accessed and addressed. It may not be equivalent to a
physical device.
management information base (MIB). An Enscribe indexed file used to hold the wide area
network (WAN) subsystem configuration records. The MIB is built, maintained, and
accessed by the WAN manager process.
message. Complete communications sent as a unit, able to be queued and assigned
priorities.
message control word. First 2 bytes (1 word) of a message in the application buffer; it
contains message control information. Used in a user-coded program utilizing the PTP
application protocol.
X25AM Configuration and Management Manual—523424-004
Glossary- 5
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. Packets are numbered 0 through
127.
NAM protocol. Network Access Method protocol. Used by the X25AM process when other
NonStop communications subsystems also using the NAM protocol want to use an
X.25 network or protocol for connection.
network. Group of nodes connected by communications lines.
node. Point of connection in a network. Usually consists of a computer or other peripheral
device that provides a switching or terminating point in the network.
NonStop operating system. The operating system for NonStop servers.
nonswitched line. Line configuration that provides a permanent path between two stations.
This path can be a privately owned cable or a dedicated path leased from a common
carrier. It is generally a leased line.
octal. Base-8 numbering system.
octet. 8 bits (1 byte).
operating system image. Specifies the configuration for the operating system and is
loaded onto a computer system to make it operational.
OSI. Open Systems Interconnection. Set of standards used for the interconnection of
heterogeneous computer systems that provides universal connectivity.
OSM. Stands for HP Open System Management (OSM) Interface. OSM replaces TSM as
the system management tool of choice for NonStop S-series servers. OSM provides
the same functionality as TSM while overcoming limitations of TSM. OSM is required
for support of new functionality in G06.21 and later, and is the only supported
management tool for Integrity NonStop NS-series servers.
packet. Group of bits arranged in a specific format within a frame, transmitted as a whole on
a packet-switching network. The message contains both control information (for
routing) and data.
X25AM Configuration and Management Manual—523424-004
Glossary- 6
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.
packet size. Number of bytes of user data in a data packet.
packetizing. Procedure by which a message is broken up into packets for transmission in a
packet-switching network.
packet switching. Method for transmitting information in packets in a network.
packet-switching data network (PSDN). A network providing packet-switching data
communications services. A PSDN can be either a public data network (PDN) or a
private packet-switching data network.
packet-switching exchanges. Computers in a packet-switching network.
PAD. See packet assembler/disassembler (PAD).
PAD profile. Group of PAD parameter settings.
page. Unit of memory consisting of 2048 bytes.
parity bit. Bit appended to a group of bits making an odd number of ones in the group (odd
parity) or an even number of ones in the group (even parity.)
parity checking. Testing a group of bits to determine whether the number of ones in the
group is odd or even.
PDN. See public data network (PDN).
permanent virtual circuit (PVC). Association between two entities for packet exchange. A
call consists of data transfer and does not require call setup and call clearing.
physical level. X.25 protocol description for the physical link between the network and the
computers, terminals, or other devices.
port number. Number assigned to a subdevice to link an address to a specific subdevice.
Sometimes referred to as a subaddress.
primary station. In an SDLC or ADCCP-NRM configuration, the primary station initiates a
data transfer and is in control during the exchange of messages. The primary station
notifies each secondary link station when the secondary station can transmit data and
when it should expect to receive data. This type of configuration is not used for X.25
connections. However, the combined station used for X.25 connections is logically
X25AM Configuration and Management Manual—523424-004
Glossary- 7
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. For X25AM, PTP is used by the X25AM
process when it exchanges data with a remote device.
public data network (PDN). A network providing (among other possible services) packetswitching services to the public.
point-to-point. A data-link configuration between only two stations. The X.25 standard
supports only point-to-point communications. In other types of communications, such
as SNA or BSC, it is possible to have multipoint configurations. In multipoint
configurations, one station is designated as a supervisor that controls multiple tributary
stations.
PVC. See permanent virtual circuit (PVC).
QLLC. Qualified Logical-Link Control protocol. A link-level IBM protocol that serves as an
X.25 interface for attaching SNA devices to packet-switching networks.
REJ. Reject. Link-level control frame or packet-level packet. As a packet, it requests the
retransmission of data.
restart packet. Packet sent by the network when a call is restarted.
RNR. Receiver not ready. Link-level frame or packet-level packet. As a packet, it
acknowledges the receipt of data and requests that packet transmission be halted.
RPOA. Registered private operating agency. Network provider providing some degree of
public service.
RR. Receiver ready. Link-level frame or packet-level packet. As a packet, it acknowledges
the receipt of data and requests that packet transmission continue.
RS-232. An industry standard defining the physical characteristics of the cable and 25-pin
connectors used for connecting DTE and DCE.
RS-422/449. An industry standard defining the physical characteristics of the cable and the
37-pin and 9-pin connectors used for connecting DTE and DCE.
SABM. Set asynchronous balanced mode. Link-level frame used for call connection.
X25AM Configuration and Management Manual—523424-004
Glossary- 8
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.25 connections is logically divided into a primary substation and a secondary
substation. See also primary station.
ServerNet wide area network (SWAN) concentrator. (1) An HP data communications
peripheral that provides connectivity to an Integrity NonStop NS-series or
NonStop S-series server. The SWAN concentrator supports both synchronous and
asynchronous data over RS-232, RS-449, X.21, and V.35 electrical and physical
interfaces. (2) A collective term for both SWAN concentrators and SWAN 2
concentrators when a distinction between the two is not required.
site update tape (SUT). One or more tapes that contain each target system’s site-specific
subvolume and various products. Each product contains a softdoc and a complete set
of files. A SUT is delivered with every new Integrity NonStop NS-series or
NonStop S-series system and can be ordered whenever a new release version update
(RVU) of the system software is available. A full SUT contains the current RVU of the
HP NonStop Kernel operating system and all product software that has been ordered
with it. A partial SUT contains a subset of products for the current software RVU.
SU. Name of an object used by SCF to refer to a subdevice.
subdevice. Logical component of X25AM that provides access to a circuit.
subscriber access link. Communications link between the local device or system and the
network.
Subsystem Control Facility. See SCF.
SUT. See site update tape (SUT).
SWAN concentrator. See ServerNet wide area network (SWAN) concentrator.
SYSGEN. For systems running D-series RVUs, SYSGEN is the program that generates a
system-image file. The SYSGEN program is usually invoked by Install.
SYSnn subvolume. A subvolume on the $SYSTEM volume where the new version of the
operating system image is located. Also located on the SYSnn subvolume is
system-dependent and RVU dependent software. nn is an octal number in the range
%00 through %77.
switched line. Line configuration for circuit-switched networks such as a public telephone
network. The physical configuration may vary for each usage as a message is routed
through switching stations.
X25AM Configuration and Management Manual—523424-004
Glossary- 9
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. A software product that provides the information needed to perform functions such as
querying resources and testing, provides notification of problems on the system, and
allows local or remote access to the system for service and maintenance. TSM
performs the same role as the HP Tandem Maintenance and Diagnostic System
(TMDS), RDF, Syshealth, and the Remote Maintenance Interface (RMI) on other
NonStop systems. TSM is not supported on Integrity NonStop NS-series servers. See
also OSM.
timeout. Time interval during which a specified action must occur.
transit delay selection or indication. Optional network facility for requesting the maximum
acceptable delay in the network in the call request packet. The network responds in a
call connected packet with the value or a lower acceptable value.
throughput. Amount of data traffic going through the network within a given time period.
Expressed in bits per second (bps).
UA. Unnumbered acknowledgment. Link-level frame used to respond to a SABM, DISC, or
RSET command.
user data. Data field contained in data packets. See also call user data (CUD).
V.25 bis. Standard related to synchronous and asynchronous automatic-dialing procedures
for switched networks. V.25 bis allows a DTE to connect to one of many DCEs in a
General Services Telephone Network (GSTN).
virtual circuit. Facilities provided by a packet-switching network that give the appearance
to the user of an actual connection.
WAN concentrator. See ServerNet wide area network (SWAN) concentrator.
WAN subsystem. See wide area network (WAN) subsystem.
WAN subsystem manager process. A process named $ZZWAN provided as part of the
wide area network (WAN) subsystem that starts and manages the WAN subsystem
objects, the WAN product process, and device objects. Subsystem Control Facility
(SCF) commands are directed to the WAN manager process for configuring and
managing the WAN subsystem and the ServerNet wide area network (SWAN)
concentrator.
X25AM Configuration and Management Manual—523424-004
Glossary -10
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. Recommendation for the physical layer interface, designed
for digital circuit-switched networks.
X.21 bis. Standard related to X.25. Recommendation for the physical layer interface,
functionally equivalent to the electrical interfaces RS-232-C and V.24. Also adapts to
provisions of RS-449 and ITU-T V.25.
X25AM. An HP product for X.25 communications. The X25AM product is a subsystem,
consisting of one or more I/O processes, the lines controlled by the I/O processes, and
the subdevice(s) associated with each line.
X.25. Set of international recommendations for the connection between computers,
terminals, or other devices and a public or private packet-switching network.
X.28. Standard related to X.25. Defines how an asynchronous device communicates with a
PAD in the same country.
X.29. Standard related to X.25. Defines how X25 DTE controls the operation of a PAD
during communications with an asynchronous DTE.
X.75. Standard related to X.25. Defines how to connect public packet-switching data
networks through a gateway interface.
X.121. Standard address format for X.25 connection. It uniquely identifies a country or
geographical area, a network, and a subscriber. An X.121 address can contain up to
15 digits. See also Data Network Identification Code (DNIC).
$ZZWAN. The process name of the wide area network (WAN) subsystem manager process.
X25AM Configuration and Management Manual—523424-004
Glossary -11
$ZZWAN
Glossary
X25AM Configuration and Management Manual—523424-004
Glossary -12
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 attribute 5-1
ASSUME command 4-2
Attribute specifications
ADD SU command 4-14
ALTER LINE command 4-19
ALTER SU command 4-20
Attributes
See individual attributes
Attributes, definition of 4-9
AUTOLOAD modifier 3-15
BCUG attribute 5-2
BPADPARMS
definition 5-2
Buffer pool information statistics 4-41
Buffer space 3-20
C
Calculating pages 3-21
Call Address Extension 3-20
Call Request packet 6-16
CALLINGADDR attribute 5-2
CALLS attribute 5-3
CALLUSERDATA modifier 3-16
CHARACTERSET attribute 5-3
CIRCUITS modifier 3-16, 5-16
CLBDOWNLOADENTRIES modifier 3-17
CLBSTATUSPROBETIME modifier 3-17
CLBTIMER modifier 3-17
CLBWINDOWEXT modifier 3-17
CLIP clock, disabling, enabling 5-3
CLIP code 3-30
CLIP errors 4-40
CLOCKMODE attribute 5-3
CLOCKnnnn modifier 3-17
CLOCKSPEED attribute 5-3
Command files
adding a profile G-1
adding an I/O process G-2
starting a line G-3
starting an I/O process G-2
Command format 4-4
X25AM Configuration and Management Manual—523424-004
Index -1
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 A-2
syntax 4-48
STOPOPENS 4-49
object-spec A-2
syntax 4-49, A-2
SWITCH
syntax 4-50
to determine status 4-11
TRACE
syntax 4-51, A-2
VERSION
object-spec A-2
syntax 4-55
Compatibility 4-4
Confirmation packet statistics 4-38
Conversation-mode subdevices 3-31
CPADPARMS attribute 5-3
CUD
adding 5-21
altering 5-21
attributes 5-21
definition 5-4, 5-19
deleting 5-21
displaying 5-20
dynamic 5-20
errors returned 5-21
PTP protocol 5-19
resetting values 5-20
SETPARAM 41 5-20
static value 5-20
CUD attribute 5-4
CUG attribute 5-4
CUGTYPE attribute 5-4
D
DATANET D-4
PAD profiles D-10
DATAPAC D-5
PAD profiles D-11
DATEX-P D-5
PAD profiles D-14
X25AM Configuration and Management Manual—523424-004
Index -2
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
Driver information statistics 4-40
DRTIMEOUT modifier 3-18
DSRTIMEOUT attribute 5-6
DSRTIMEOUT modifier 3-18
DTE modifier 3-18
DTECLOCK modifier 3-17, 3-19
E
EBCDIC modifier 3-15
Electrical interface, specifying 3-30
EMSFORFRMR attribute 5-7
EMSFORFRMR modifier 3-19
ENABLECALLEDADDREXT modifier 3-20
ENABLEPVCOUTOFORDER modifier 3-20
Error 140, in troubleshooting 6-9
Expand and X25AM lines 5-1
EXTENDEDPOOLPAGES modifier 3-20
EXTFORMAT attribute 5-7
EXTFORMAT modifier 3-28
F
FIFO modifier 3-22
Files, for SCF 4-3
Finding line or subdevice names 4-35, 4-42
Format of SCF commands 4-4
FRAMEMODE attribute 3-18, 5-7
FRMR 3-13, 3-19, 4-39, 5-7
G
General Service Telephone Network
(GSTN) 3-34, 5-8
H
Hardware protocol, specifying 3-30
Help
general description 4-3
online 4-4
I
IDLECMDPRR modifier 3-22
IDLERESPRR modifier 3-22
IDLETIMEOUT attribute 5-8
Incoming call request 5-1
INCOMINGCALLS modifier 3-32
INFO command
definition 4-30
syntax 4-26, A-1
Input file for SCF 4-3
Input sources, for SCF 4-3
Interactive mode, for SCF 4-3
INTERFACE attribute 5-8
ITI mode
PTrace 6-25
I/O process modifiers and line attributes
compared B-1
I/O process, defined 2-1
X25AM Configuration and Management Manual—523424-004
Index -3
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-10
NETID modifier 3-27
Network options 3-27
NOAUTOLOAD modifier 3-15
NOCALLS modifier 3-32
NOCALLUSERDATA modifier 3-16
NOEXTFORMAT modifier 3-28
NOINCOMINGCALLS modifier 3-32
NONEGOTIATE attribute 5-10
L
L21FRAMERECOVERY modifier 3-24
L2DISC modifier 3-24
L2DOWNLINE modifier 3-23
L2NODISC modifier 3-24
L2RETRIES modifier 3-24
L2TIMEOUT modifier 3-24
L2WINDOW modifier 3-25
L3 packets, order of sending 3-22
L3MOD attribute 5-9
L3MOD128 modifier 3-25
L3MOD8 modifier 3-25
L3RECVTHRUPUT modifier 3-25
L3SENDTHRUPUT modifier 3-26
L3WINDOW attribute 5-9
L3WINDOW modifier 3-26
Level 3, PTrace 6-13
Line attributes B-1
Line names, finding 4-35, 4-42
LINE object 4-6
Line quality, setting threshold 4-36, 5-17
LINEQUALITYTHRESHOLD modifier 3-23,
3-27, 5-17
Line, defined 2-2
LOCALADDREXT attribute 5-9
LOCALADDREXTTYPE attribute 5-9
LOCALPOOLPAGES modifier 3-20
M
MAXIOSIZE modifier 3-27
Memory 3-20
Memory fragmentation 3-21
Menus, help 4-4
X25AM Configuration and Management Manual—523424-004
Index -4
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-spec
STOP command A-2
STOPOPENS command A-2
VERSION command A-2
Object-spec syntax 4-8
Object-type
definition 4-6
hierarchy 4-6
Online help 4-4
OUT command, SCF 4-2
OUTGOINGCALLS modifier 3-32
Output destinations, for SCF 4-3
Output file for SCF 4-3
Owner, subsystem 4-11
P
Packet level information statistics 4-37
Packet types, searching for in PTrace 6-4
PACKETSIZE modifier 3-29
Packet-level window size 3-26
PAD
parameter examples D-16
parameters 2-4
PAD profiles
REMOTENET D-2
standard D-8
PAGE6520BLKSIZE attribute 5-11
PAGE6520BLKSIZE modifier 3-29
Parameters, in SCF commands 4-4
PARITY attribute 5-11
PARITYCHK attribute 5-11
PORT attribute 5-12
Port numbering
NETID D-2
REMOTENET D-2
PRICALL attribute 5-12
PRIMARY command
syntax 4-32, A-1
Priority attribute for DDN 5-5
PROCESS object 4-6
Profile^Version modifier 3-30
PROGID option 4-11
PROGRAM attribute 5-12
PROGRAM modifier 3-30
PROTOCOL attribute 3-4, 4-9, 5-12
PSS D-6
PAD profiles D-16
PTrace
application level 6-21
application trace analysis 6-24
commands not supported by
X25AM 6-3
X25AM Configuration and Management Manual—523424-004
Index -5
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 6-13
tracing the WRITELINK 6-9
UA response 6-9
PVC attribute 5-13
PVCRANGE attribute 5-13
PVC, error messages for 3-20
R
RECSIZE attribute 3-4, 4-9, 5-14
RECSIZE modifier 3-4
REMOTEADDREXT attribute 5-14
REMOTEADDREXTTYPE attribute 5-14
REMOTENET
DATANET D-4
DATAPAC D-5
DATEX-P D-5, D-6
DDN D-5
REMOTENET (continued)
DDXP D-6
definition D-1
PAD profiles D-2
port numbering D-2
PSS D-6
TELENET D-6
TRANSPAC D-7
TWINET D-7
TYMNET D-7
UNINET D-8
use with subdevices D-1
X25 D-3
X25NP D-3
X25SA D-3
X25UD D-4
X25XA D-4
REMOTENET attribute 5-14
Required attributes 3-4, 4-9
Required modifiers 3-4
Retries 3-24
RETRIES attribute 5-15
Retry counters 3-32
REVERSECHG attribute 5-15
REXMITTIMEOUT attribute 5-15
RPOA attribute 5-15
RR-frame 3-22, 3-25
RS232 modifier 3-30
RSIZE
See RECSIZE modifier
RUN command for starting SCF 4-3
Running modes for SCF 4-3
S
SCF 2-2, 4-4
file name of 4-3
help facility 4-4
running modes, starting 4-3
session parameters 4-2
X25AM Configuration and Management Manual—523424-004
Index -6
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
driver information 4-40
line quality 4-36
packet level information 4-37
STATS command
definition 4-35
syntax 4-35, A-1
STATS LINE command
format 4-36
STATS SU command
format 4-41
STATUS command
definition 4-42
object-spec 4-43
syntax 4-43, A-2
STATUS LINE command
display format 4-44
STATUS SU command
display format 4-46
STOP command
object-spec A-2
syntax 4-48
STOPOPENS command
definition 4-49
object-spec A-2
syntax 4-49, A-2
STRIPPARITY modifier 3-31
SU object 4-6
Subdevices 2-2, 3-16
CIRCUITS modifier 2-2
configuration 2-2
defined 2-2
finding names 4-35, 4-42
Subscription parameters 2-5
Subsystem Control Facility
See SCF
Subsystem Control Point
See SCP
Subsystem owner 4-11
Super-group access 4-11
Support
X25AM 2-1
SVCRANGE attribute 5-16
SWITCH command
syntax 4-50
SYNCS modifier 3-32
Syntax rules for object-specs 4-8
T
T1 subscription parameter 3-18, 3-24
T1TIMEOUT attribute 5-17
TELENET D-6
PAD profiles D-17
Terminals and PAD parameters
PTrace 6-25
Terminals, supported 2-4
THRESHOLD attribute 5-17
Throughput 3-26
THRUPUT attribute 5-17
X25AM Configuration and Management Manual—523424-004
Index -7
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
DCE or DTE 2-1
I/O process 2-1
I/O process modifiers 6-27
LAP 2-1
LAPB 2-1
scope of support 2-1
subdevice 2-2
X25AM and Expand lines 5-1
X25AM I/O process modifiers
with no equivalent SCF line
attribute 4-22
X25AM levels in PTrace 6-9
X25NP D-3
X25SA D-3
X25UD D-4
X25Vyyyy modifier 3-35
X25XA D-4
X3PAD 2-4
X.21 protocol, program for 3-6
X.29 2-4
X.3 2-4
Special Characters
V
$SYSTEM.SYSTEM.SCF 4-3
V25 modifier 3-34
Values, range validation 3-15
Version 3-35
VERSION command
object-spec A-2
syntax 4-55
V.25 protocol 3-34, 5-8
X25AM Configuration and Management Manual—523424-004
Index -8
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement