GA27 3136 9_SNA_Formats_Jun88 9 SNA Formats Jun88

GA27-3136-9_SNA_Formats_Jun88 GA27-3136-9_SNA_Formats_Jun88

User Manual: GA27-3136-9_SNA_Formats_Jun88

Open the PDF directly: View PDF .
Page Count: 420

Download
Open PDF In Browser	View PDF

---- - -- ----- -- ----_
----.-

Systems Network Architecture

Formats

GA27-3136-9

---- ------ ---- ---------,-

Systems Network Architecture

,R)

Formats

GA27-3136-9

Tenth Edition (June 1988)
This is a revision of GA27-3l36-8 1 which is now obsolete.
It is possible that this material may contain references tO or information about,
IBM products (machines and programs) or services that are not announced in your
country.
Such references or information must not be construed to mean that IBM
intends to announce such IBM products .or serVlces ln your country.
I

The following paragraph does not apply to the United Kingdom or any country where
such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
In the United States, some
states do not allow disclaimer of express or implied warranties in certain
transactions; therefore, this statement may not apply to you.
Publications are not stocked at the address given below; the licensed documents are
available to customers that have a product license.
A form for reader's comments is provided at the back of this publication.
If the
form has been removed, comments may be addressed to IBM Corporation, Information and
Interface Development Support, Department E01, P. O. Box 12195 1 Research Triangle
Park, North Carolina U.S.A.
27709.
IBM may use or distribute any of the
information you supply in any way it believes appropriate without incurring any
obligation whatever.
You maYI of course, continue to use the information you
supply.

(c) Copyright International Business Machines Corporation 1977 1 1988.
reserved.

All rights

PREFACE

ABOUT THE BOOK

This book describes the Systems Network Architecture (SNA) formats used between
subarea nodes and peripheral nodes, and between type 2.1 nodes using peer-to-peer
protocols.

HOW THIS BOOK IS ORGANIZED

This book identifies the formats and meanings of the bytes that a basic link unit
(BLU) contains.
A BLU is the basic unit of transmission at the data link and link
station level. The figure on page vii illustrates the organization of this book.
Chapter 1 identifies the formats and meanings of the bytes in a link header and a
link trailer.
Chapter 2 identifies the formats and meanings of the information-field bytes 1n an
SDLC and System/370 DLC Exchange Identification (XID) command and response.
Chapter 3 identifies the formats and meanings of the bytes 1n a transmission header.
Chapter 4 identifies the formats and meanings of the bytes 1n a request or response
header.
Chapter 5.1 identifies the formats and meanings of the bytes in a request unit.
Chapter 5.2 identifies the formats and meanings of the bytes in a response unit.
Chapter 6 explains the transmission services and function management profiles that
SNA defines to describe session characteristics.
Chapter 7 identifies the formats and meanings of the bytes 1n user-structured
subfields that appear in a request or response unit.
Chapter 8 identifies the formats and meanings of the control vectors, session keys,
and management services vectors that appear in a request or response unit.
Chapter 9 explains the meanings of the sense data defined by System Network
Architecture (SNA) that appear in a negative response units.
Chapter 10 presents the descriptions and formats of the different function
management headers.

Preface

111

Chapter 11 identifies the formats and meanings of the bytes in a presentation
services, header.
Chapter 12 identifies the formats and meanings of the general data stream (GDS)
variables that are specific to SNA service transaction programs.
Chapter 13 identifies the formats and meanings of the message units that SNA
Distribution Services transaction programs use.
ChQPter 14 identifies the general data stream (GDS) variables that are for general
use.
Appendix A provides a summary of SNA character sets and symbol-string types.
Appendix B provides a summary of general data stream identifier (GDS ID) value
assignments.
Appendix C lists the abbreviations and symbols that are used 1n this book.

RELATED PUBLICATIONS

Related publications, providing overview and protocol information, are:
•

Systems Network Architecture Concepts and Products (GC30-3072)

•

Systems Network Architecture Technical Overview (GC30-3073)

•

IBM Synchronous Data Link Control Concepts (GA27-3093)

•

Systems Network Architecture Format and Protocol Reference Manual:
Architectural Logic (SC30-3112)

•

Systems Network Architecture Type 2.1 Node Reference (SC30-3422)

•

Systems Network Architecture:

•

Systems Network Architecture Format and Protocol Reference Manual:
Logic for !J! Type 6.2 (SC30-3269)

Architecture

•

Systems Network Architecture Format and Protocol Reference Manual:
Services (SC30-3098)

Distribution

•

Systems Network Architecture Format and Protocol Reference Manual:
Services (SC30-3346)

Management

•

Token-Ring Network Architecture Reference (SC30-3374)

iv

SNA Formats

Sessions Between Logical Units (GC20-1868)

Preface

v

vi

SNA Formats

Message
Unit
Format

Chapter 1

BLU

Information Field

Chapter 2

(SOLe)

Chapter 3

PIU

RU

Chapter 4

BIU

Chapter 5.1

(Request)
~

Chapter 5.2

(Response)
\.

r~

~

~

Negative
Response

Positive
Response

SNA-Defined
Data

TS Profiles
FM Profiles

TS Profiles
FM Profiles

Chapter 6

Chapter 7

+

+

End-User
Data

Structured
Subfields

Chapter 8

Control Vectors

Chapter 9

Control Vectors
Session Keys
MS Vectors

Sense Data

Chapter 10

FM Headers

Chapter 11

PS Headers

Chapter 12

SNA STPs

Chapter 13

SNADS (DIU)

Chapter 14

GDS Variables
LH
LT
XID
TH
RH
RU
TS
FM
MS

=
=
=
=
=
=
=
=
=

Link Header
Link Trailer
Exchange Identification
Transmission Header
Request/Response Header
Request/Response Unit
Transmission Services
Function Management
Management Services

PS
STP
SNADS
DIU
GDS
BLU
PIU
BIU

=
=
=
=
=

Presentation Services
Service Transaction Program
SNA Distribution Services
Distribution Interchange Unit
General Data Stream
Basic Link Unit
Path Information Unit
Basic Information Unit

Preface

vii

This page intentionally left blank

viii

SNA Formats

CONTENTS

Chapter 1.

DLC Links

1-1

Synchronous Data Link Control (SDLC)
Link Header
....
Flag
Address
Control
Link Trailer
Frame Check Sequence
Flag
....
Token-Ring Network DLC
Chapter 2.

1-1
1-2
1-2

1-3
1-4
1-9
1-9

1-10
1-11

Exchange Identification (XID) Information Fields

2-1

DLC XID Information-Field Formats

2-1

Chapter 3.

3-1

Transmission Headers

Introduction
.... .
FID2 Layout
.... .
FID2 Field Descriptions

3-1
3-2
3-2

Chapter 4.

4-1

Request/Response Headers

Introduction
RH Formats
....
IPR, IPM, and EXR
. . . .
ISOLATED PACING RESPONSE (IPR)
ISOLATED PACING MESSAGE (IPM)
EXCEPTION REQUEST (EXR)
....
Chapter 5.1.

4-1
4-4

4-10
4-10

4-10
4-11

Request Units

5.1-1

Introduction to Request Units
Request Unit Summary Information
Summary of Request RUs by Category
Index of RUs by NS Headers and Request Codes
Descriptions of Request Units
....
ACTLU; SSCP-->LU, Exp; SC (ACTIVATE LOGICAL UNIT)
ACTPU; SSCP-->PU, ExPj SC (ACTIVATE PHYSICAL UNIT)
BID; LU-->LU, Norm; DFC (BID)
............ .
BIND; PLU-->SLU, Exp; SC (BIND SESSION)
... .
BISj LU-->LU, Norm; DFC (BRACKET INITIATION STOPPED)
CANCEL; LU-->LU, Norm; DFC (CANCEL)
CHASE; LU-->LU, Norm; DFC (CHASE)
....... .
CLEAR; PLU-->SLU, Exp; SC (CLEAR)
....... .
CRV; PLU-->SLU, Exp; SC (CRYPTOGRAPHY VERIFICATION)

S.l-l
S.1-3
S .1-3
S.1-4

S .1-S
S .1-S
S.l-S
S .1-S
S.1-6
S.l-lS
S .1-1S
S.l-lS
S.l-lS
S.1-1S

Contents

ix

DACTlU; SSCP-->lU, Exp; SC (DEACTIVATE lOGICAL UNIT)
.....
DACTPU; SSCP-->PU, PU-->SSCP, EXPi SC (DEACTIVATE PHYSICAL UNIT)
INIT-SElF Format 0; IlU-->SSCP, Normi FMD NS(s) (INITIATE-SELF)
INIT-SElF Format Ii IlU-->SSCP, Normi FMD NS(s) (INITIATE-SELF)
lUSTATi lU-->lU/SSCP, Normi DFC (lOGICAL UNIT STATUS)
NMVTi SSCP<-->PU Norm; FMD NS(ma) (NETWORK MANAGEMENT VECTOR TRANSPORT)
NOTIFYi SSCP<-->lU, Norm; FMD NS(s) (NOTIFY)
. . . .
lU-lU Session Services Capabilities
QCi lU-->lU, Norm; DFC (QUIESCE COMPLETE)
QECi lU-->LU, Exp; DFC (QUIESCE AT END OF CHAIN)
RECFMS; PU-->SSCp, Norm; FMD NS(ma) (RECORD FORMATTED MAINTENANCE
STATISTICS)
....................... .
RELQ; LU-->LU, Exp; DFC (RELEASE QUIESCE)
.......... .
REQMS; SSCP-->PU, Norm; FMD NS(ma) (REQUEST MAINTENANCE STATISTICS)
RQR; SlU-->PLU, Exp; SC (REQUEST RECOVERY)
RSHUTD; SLU-->PLU, Exp; DFC (REQUEST SHUTDOWN)
RTR; lU-->lU, Norm; DFC (READY TO RECEIVE)
SBI; LU-->LU, Exp; DFC (STOP BRACKET INITIATION)
SDT; PLU-->SLU, SSCP-->PU/SSCP, Exp; SC (START DATA TRAFFIC)
SHUTC; SLU-->PLU, EXPi DFC (SHUTDOWN COMPLETE)
SHUTDi PlU-->SLU, EXPi DFC (SHUTDOWN)
SIG; LU-->lU, EXPi DFC (SIGNAL)
........ .
STSN; PLU-->SLU, EXPi SC (SET AND TEST SEQUENCE NUMBERS)
TERM-SELF; TLU-~>SSCP, Norm; FMD NS(s) (TERMINATE-SELF)
TERM-SELFi TLU-->SSCP, Norm; FMD NS(s) (TERMINATE-SELF)
UNBIND; lU-->LU, Exp; SC (UNBIND SESSION)
Chapter 5.2.

Response Units

Introduction
Positive Response Uhits with Extended Formats
RSP(ACTLU); LU-->SSCP, Exp; SC
RSP(ACTPU)i PU-->SSCp, EXPi SC
RSP(BIND); SLU-->PlU, EXPi SC
RSP(STSN)i SLU-->PLU, EXPi SC
Chapter 6.

Profiles

Introduction
Transmission Services (TS) Profiles
TS Profile 1
TS Profile 2
TS Profile 3
TS Profile 4
TS Profile 7
Function Management (FM) Profiles
FM Profile 0
FM Profile 2
FM Profile 3
FM Profile 4
FM Profile 6
FM Profile 7
FM Profile 18
FM Profile 19

x

SNA Formats

5.1-16
5.1-16
5.1-17
5.1-18
5.1-20
5.1-21
5.1-22
5.1-22
5.1-22
5.1-23
5.1-23
5.1-37
5.1-37
5.1-38
5.1-38
5.1-39
5.1-39
5.1-39
5.1-39
5.1-39
5.1-39
5.1-40
5.1-40
5.1-41
5.1-42

5.2-1
5.2-1
5.2-3
5.2-3
5.2-3
5.2-4
5.2-6

6-1
6-1
6-2
6-3
6-3
6-4
6-4
6-5
6-6
6-7
6-7
6-8
6-9
6-10
6-11
6-12
6-13

Chapter 7.

User Data structured Subfields

7-1

Introduction
Descriptions
Unformatted Data
Session Qualifier
Mode Name
Session Instance Identifier
....
Network-Qualified PlU Network Name
Network-Qualified SlU Network Name
Random Data
Enciphered Data

7-1
7-2
7-2
7-2
7-2
7-2
7-3
7-3
7-3
7-4

Chapter 8.

8-1

Common Fields

8-1
8-2
8-2
8-2
8-2
8-2
8-2
8-2
8-3
8-4
8-4
8-4
8-4
8-5
8-5
8-5
8-6
8-6
8-6
8-6
8-6
8-8
8-9
8-9
8-9
8-10
8-10
8-11
8-14
8-14
8-15
8-15
8-15
8-15
8-15
8-16
8-16
8-16
8-20

Introduction
Substructure Encoding/Parsing Rules
Rules for Common Substructures
Partitioning of Key/Type Values
Category-Dependent Keys
Unique Keys
....
Context-Sensitive Keys
Parsing Rules
. . . .
Enclosing Rule for Substructures
Control Vectors
Introduction
Control Vector Formats
SSCP-LU Session Capabilities (X'OO')
PU FMD-RU-Usage (X'07')
.....
LU-LU Session Services Capabilities (X'OC')
Network Name (X'OE')
....
Product Set ID (X'lO')
XID Negotiation Error (X'22')
COS/TPF (X'2C')
.....
Mode (X'2D')
Extended Sense Data (X'3S')
Fully-qualified PCID (X'60')
Session Key
........
... .
Network or Uninterpreted Name (X'Ol')
URC (X'OA')
......... .
MS Major Vectors and Unique Subvectors
Introduction
. . . . . . . .
Alert (X'OOOO')
....
SDLC link Station Data (X'8C')
Current N(S)/N(R) Counts (X'Ol')
Outstanding Frame Count (X'02')
last SDLC Control Field Received (X'03')
Last SDLC Control Field Sent (X'04')
Sequence Number Modulus (X'OS')
link Station State (X'06')
lLC Reply Timer Expiration Count (X'07')
Last Received N(R) Count (X'08')
Basic Alert (X'91')
Generic Alert Data (X'92')

Contents

xi

Probable Causes (X'93')
User Causes (X'94')
User Causes (X'Ol')
Install Causes (X'95')
Install Causes (X'Ol')
Failure Causes (X'96')
Failure Causes (X'Ol')
Cause Undetermined (X'97')
Detailed Data (X'98')
Qualified Message Data (X'Ol')
Detail Qualifier (EBCDIC) (X'AO')
Detail Qualifier (Hexadecimal) (X'Al')
Network Alert (X'OOOO') Common Subfields
Recommended Actions (X'81')
Detailed Data (X'82')
Product Set ID Index (X'83')
Request Response Time Monitor (X'8080')
RTM Request (X'92')
... .
RTM Control (X'94')
... .
Response Time Monitor (X'0080')
RTM Status Reply (X'91')
RTM Data (X' 93' )
MS Common Subvectors
Text Message (X'OO')
Date/Time (X'Ol')
Local Date/Time (X'10')
Greenwich Mean Time Offset (X'20')
Hierarchy Name List (X'03')
SNA Address List (X'04')
Hierarchy/Resource List (X'OS')
Hierarchy Name List (X'lO')
Product Set ID (X'10')
....
Product Identifier (X'll')
Hardware Product Identifier (X'OO')
Emulated Product Identifier (X'Ol')
Software Product Serviceable Component Identifier (X'02')
Software Product Common Level (X'04')
..... .
Software Product Common Name (X'06')
Software Product Customization Identifier (X'07')
Software Product Program Number (X'08')
Software Product Customization Date and Time (X'09')
Microcode EC Level (X'OB')
....
Hardware Product Common Name (X'OE')
Self-Defining Text Message (X'31')
....
Coded Character Set ID (X'02')
National Language ID (X'll')
Sender ID (X'21')
Text Message (X'30')
Relative Time (X'42')
Data Reset Flag (X'45')
LAN Link Connection Subsystem Data (X'51')
Ring or Bus Identifier (X'02')
........ .
Local Individual MAC Address (X'03')
... .
Remote Individual MAC Address (X'04')

xii

SNA Formats

8-30
8-45
8-45
8-53
8-53
8-59
8-60
8-79
8-80
8-80
8-81
8-82
8-82
8-82
8-93
8-96
8-97
8-98
8-99
8-100
8-102
8-103
8-105
8-105
.8-105
8-105
8-106
8-106
8-107
8-108
8-108
8-110
8-110
8-112
8-114
8-114
8-114
8-115
8-115
8-115
8-115
8-116
8-116
8-116
8-117
8-117
8-118
8-118
8-118
8-119
8-119
8-119
8-120
8-120

LAN Routing Information (X'05')
Fault Domain Description (X'06')
Beaconing Data (X'07')
Single MAC Address (X'08')
Fault Domain Error Weight Pair (X'09')
Bridge Identifier (X'OA')
Local Individual MAC Name (X'23')
Remote Individual MAC Name (X'24')
Fault Domain Names (X'26')
Single MAC Name (X'28')
Link Connection Subsystem Configuration Data (X'52')
Port Address (X'Ol')
....
Remote Device Address (X'02')
Local Device Address (X'04')
LCS Link Station Attributes (X'06')
LCS Link Attributes (X'07')
LPDA Fault LSL Descriptor Subfield (X'08')
Sense Data (X'7D')

Chapter 9.

8-120
8-120
8-120
8-121
8-121
8-121
8-121
8-122
8-122
8-122
8-123
8-123
8-123
8-123
8-124
8-124
8-124
8-125

Sense Data

9-1

=

Request Reject (Category Code
X'08')
Request Error (Category Code = X'lO')
State Error (Category Code = X'20')
RH Usage Error (Category Code = X'40')
Path Error (Category Code = X'80')

9-2
9-42
9-53
9-55
9-57

Chapter 10.

10-1

Function Management Headers

FM
FM
FM
FM
FM

Header 1
Header 2
Header 3
Header 4
Header 5: Attach (LU 6.2)
Access Security Information Subfields
PIP Variable
. . . .
PIP Subfield
....
FM Header 5: Attach (Not LU 6.2)
FM Header 6
FM Header 7:
Error Description (LU 6.2)
FM Header 7:
Error Description (Not LU 6.2)
FM Header 8
FM Header 10
FM Header 12: Security

Chapter 11.

10-3
10-6
10-7
10-8
10-10
10-11
10-11
10-11
10-12
10-13
10-14
10-15
10-15
10-15
10-16

Presentation Services Headers

11-1

Presentation Services (PS) Headers
PS Header 10: Sync Point Control

11-1
11-2

Chapter 12.

12-1

GDS Variables for SNA Service Transaction Programs

List of SNA Service Transaction Programs
Descriptions of GDS Variables for SNA STPs

12-1
12-2

Contents

xiii

Change Number of Sessions (X'1210') GDS Variable
Exchange log Name (X'1211') GDS Variable
Compare States (X'1213') GDS Variable

Chapter 13.

SNA Distribution Services

Introduction
Interchange Unit Description
Distribute Interchange Unit
DISTIUi DSU ---> DSUi (DISTRIBUTE INTERCHANGE UNIT)
Acknowledge Interchange Unit
........... .
ACKIU; DSU ---> DSU; (ACKNOWLEDGE INTERCHANGE UNIT)
Names and Code Points
Specification of the Character-String Fields
Code Points Used by SNADS
....
Status Type Codes
. . . .
Transaction Program and Server Names

Chapter 14.

GDS Variables for General Use

Application Data (X'12FF') GDS Variable
Null Data (X'12Fl') GDS Variable
User Control Data (X'12F2') GDS Variable
Map Name (X'12F3') GDS Variable
Error Data (X'12F4') GDS Variable
Error log (X'12E1') GDS Variable

Appendix A.

SNA Character Sets and Symbol-String Types

12-2
12-3
12-4

13-1
13-1
13-2
13-2
13-2
13-34
13-34
13-41
13-41
13-42
13-44
13-45

14-1
14-3
14-3
14-3
14-3
14-4
14-5

A-1

Symbol-String Type
SNA Character Sets and Encodings

A-I
A-2

Appendix B.

B-1

GDS ID Description and Assignments

Structured Fields
length (ll) Description
Identifier (ID) Description
Identifier Registry

B-1
B-1
B-2
B-2

Appendix C.

C-1

List of Abbreviations and Symbols

Index

xiv

X-1

SNA Formats

LIST OF ILLUSTRATIONS

Chapter 1.

DLC Links

Figure 1-1.
Figure 1-2.
Figure 1-3.
Figure 1-4.
Figure 1-5.
Figure 1-6.
Figure 1-7.
Figure 1-8.
Figure 1-9.
Figure 1-10.

Flag Field of link Header
Shared Trailing/leading 0 in SDlC Flags
Address Field of link Header
Control Field of link Header
Control Fields for SDlC Commands and Responses--Modulus 8
Control Fields for SDlC Commands and Responses--Modulus 128
Information Field of the FRMR Response Frame
Frame Check Sequence Field of link Trailer
Flag Field of link Trailer
llC Commands and Responses

Chapter 2.

Exchange IdentiTication (XIDl InTormation Fields

Chapter 3.

Transmission Headers

Figure

Figure
Figure
Figure

Request/Response Headers
4-1. RH Formats
4-2. FMD Request/Response Combinations for Sessions between Two lU
6.2s
...........
. . . . . . . . . . .
4-3. Request/Response Combinations For TS Profile 4 Sync Points

Chapter 5.1.
Figure

Figure
Figure

Chapter 7.

4-2
4-6
4-8

Request units

5.1-1. RU Sizes Corresponding to Values X'ab' in BIND

Chapter 5.2.
Chapter 6.

3-2

3-1. Transmission Header for FID Type 2

Chapter 4.

1-2
1-2
1-3
1-4
1-6
1-7
1-8
1-9
1-10
1-11

5.1-14

Response Units
ProTiles
6-2
6-6

6-1. TS Profiles and Their Usage
6-2. FM Profiles and Their Usage

User Data structured Subfields

list of Illustrations

xv

Chapter 8.
Figure

Common Fields
8-1. Setting of Bits 1 and 3 of Byte 2 of the RTM Request (X'92')
Subvector

Chapter 9.
Figure
Figure

Sense Data
9-1. Sense Data Format
......................
9-2. Usage of X'1008' Sense Code Specific Information by LU Type

Chapter 10.
Figure
Figure
Figure
Figure

10-1.
10-2.
10-3.
10-4.

FM Header Contained in One RU
FM Header Contained in Two Contiguous RUs of a Chain
Usage of FM Headers
LU Types That Support FM Headers

Presentation Services Headers

Chapter 12.

GDS Variables for SNA Service Transaction Programs

12-1. SNA-Defined Service Transaction Programs

Chapter 13.
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
rigure

Figure

xvi

10-1
10-1
10-2
10-2

12-1

SNA Distribution Services

13-1.
13-2.
13-3.
13-4.
13-5.
13-6.
13-7.
13-8.
13-9.
13-10.
13-11.
13-12.
13-13.
13-14.
13-15.
13-16.

Chapter 14.

9-1
9-52

Function Management Headers

Chapter 11.

Figure

8-99

Structure of the Distribute IU
Interpretation of the Distribution Flags
Priority, Protection, and Capaci ty Subfield Values
Feedback Priority, Protection, and Capaci ty Subfield Values
Structure of the Destination Operands
Structure of the REN List
Structure of the DGN List
Structure of the DEN List
Distribution Status Operands Structure
SNADS St'atus Condition Codes
Structure of the DGN List of Specific Status
Structure of the DEN List of Specific Status
Structure of the Acknowledge IU
Exception Condition Codes
Exception Object Codes
Character-String Specification

13-3
13-8
13-9
13-12
13-15
13-16
13-17
13-19
13-21
13-25
13-27
13-28
13-35
13-37
13-38
13-41

GDS Variables for General Use

14-1. LU Type 6.2 GDS Variable Code Points

SNA Formats

14-1

Appendix A.
Figure

A-3

A-I. Character Sets A, AE, 930, and USS.

Appendix B.
Figure

SNA Character sets and Symbol-String Types

GDS ID Description and Assignments
B-1

B-1. GDS Structured Field

Appendix C.

List of Abbreviations and Symbols

list of Illustrations

xvii

This page intentionally left blank

xviii

SNA Formats

CHAPTER 1.

DLC LINKS

Two data link controls are described in this chapter: "Synchronous Data Link
Control (SDLC)", beginning on this page, and the "Token-Ring Network DLC" on page
1-11.

SYNCHRONOUS DATA LINK CONTROL (SDLC)

All transmissions on an SDLC link are organized

Frame

= BLU = LH

where:

~n

a specific format called a frame:

[,I-field], LT

BLU
LH
I-field
LT

= Basic Link Unit
= Link Header
= Information field
= Link Trailer

Link headers and link trailers contain data link control information for synchronous
data link control (SDLC) links. An SDLC frame begins with the link header (LH),
which has three fields:
the Flag, Address, and Control fields.
The link trailer
(LT) follows the Information field and is three bytes long. The first two bytes
make up the Frame Check Sequence field; the last byte, the closing Flag field.
The
following pages identify the formats and meanings of the bytes in a link header and
a link trailer.

Chapter 1.

DLC Links

1-1

LINK HEADER
(FLAG)

Information Field

LH

-,
I

L

F

A

LT

LH
LT
F
A
C

C

L _____________ ,

= Link Header
= Link Trailer
= Flag
= Address
= Control

I

o

1

1

1

Figure 1-1.

1

1

1

o

Flag Field of Link Header:

always XI7EI,

B I OIIIIII0 1

•

All frames begin with a Flag field.
The configuration of the flag is always
01111110 (X I 7EI).
Because frames also end with flags (see link trailer), the
trailing flag of one frame may serve as the leading flag of the next frame.
When
receiving, the last 0 in the trailing flag may also be the first 0 in the next
leading flag, as Figure 1-2 illustrates.

I--leading flag-I
1 111 1 1 0 1 1 1 1 1 1 0
I-trailing flag-I

o

Figure 1-2.

Shared Trailing/Leading 0 in SDLC Flags

Note:

Zero bit insertion between the beginning and ending flags prevents a flag
pattern from occurring anywhere else in the frame.

1-2

SNA Formats

LINK HEADER
(ADDRESS)

LH

Information Field

-,
I

L

F

A

-

- -- - - - - - - -

I

1

= Link Header
= Link Trailer
= Flag
= Address
= Control

I

I

I

LH
LT
F
A
C

C

L

~

r

LT

I

a

I

I

a

I

I

a

Figure 1-3.

I

I

a

I

I

a

I

I

I

a

I

a

I

a

Address Field of Link Header:

B'aaaaaaaa'

The second byte of the link header is the Address field.

This address can be:

•

a specific link station address -- to only one link station

•

a group address -- to one or more link stations

•

a broadcast address (X'FF', B'llllllll') -- to all link stations

•

a "no stations" address (X'OO').

The "no stations" address is reserved and should not be used for any link station or
group of link stations.

Note:

The specific link station address of the secondary is used when the
transmission is going from primary to secondary or from secondary to primary.

Chapter 1.

DLC Links

1-3

LINK HEADER
(CONTROL)

LH

Information Field

LT

--,

L

I
F

A

LH
LT
F
A
C

C

.J
L
- - - (Modulus 8 and Modulus 128)

r

I
I

I

c

I

I

I

I

I

Link Header
Link Trailer
Flag
Address
Control

,

----------

T

(Modulus 128 only)

I
I
I

=
=
=
=
=

I

I

I

I

I
I
I

I

I

I c I c I c I c I c I c I c I c I c I c I c I c I c I c I c I

Figure 1-4.

Control Field of link Header:
cccccccc' for modulus 128.

B'cccccccc' for modulus 8; B'cccccccc

The third byte (or third and fourth bytes) of the link header is the Control field.
The Control field contains either an SDLC command or a response. All frames
transmitted by a primary station are commands, while frames transmitted by a
secondary station are responses. There are three categories of SDLC commands and
responses:

•
•
•

Unnumbered Format
Supervisory Format
Information Format

Unnumbered Format: These commands and responses have a poll/final (P/F) bit that is
set to 1 to solicit a response (P bit) or when it is the last SDLC frame of a
transmission (F bit). This bit is a poll bit for commands and a final bit for
responses.
Each of the Unnumbered Format commands and responses have two possible
hex values:
one value for when the poll/final bit is 0 and another value for when
the poll/final bit is 1.
Supervisory Format:

These commands and responses have a varying number of possible
hex values. The number of possible hex values corresponds to the receive sequence
numbers assigned to this frame and the setting of the P/F bit. To increase the
sequence number modulus from 8 to 128, a two-byte extended Control field is used.

1-4

SNA Formats

Information Format: These commands and responses also vary in the number of
possible hex values. The number of possible hex values correspond to the send and
receive sequence numbers assigned to this frame and the setting of the P/F bit.
To
increase the sequence number modulus from 8 to 128, a two-byte extended Control
field is used.
The Information Format is identified by a 0 in the low-order bit of the first or
only byte of the Control field.
In an Information Format SDlC command or response,
the Information field contains a PIU (Path Information Unit). The remaining
chapters of this book, with the exception of Chapter 2, discuss the contents of the
PIU.

Figure 1-5 lists the SDlC commands and responses for modulus 8 (one-byte) Control
fields; Figure 1-6 lists them for modulus 128 (two-byte) Control fields.

Figure 1-7 describes the Information field of the Frame Reject (FRMR) response
frame, which is one of the unnumbered formats listed in Figure 1-5.

Chapter 1.

DlC links

1-5

Figure 1-5.

1-6

Control Fields for SDLC Commands and Responses--Modulus 8

SNA Formats

FORMAT

BINARY CONFIGURATION

I

I

HEX
I
I
IEQUIVALENTI

ACRO-I
NYM

COMMAND NAME

same as modulus 8 (one-byte), as in Figure 1-5.

Unnumbered
Format

X'Olxx'

Receive Ready

RR

X'05xx'

Receive Not Ready

RNR

0000 1001 RRRR RRR P/F

X'09xx'

Reject

REJ

Informationl SSSS SSSO RRRR RRR P/F
Format
I

X'xxxx'

Numbered Information
Present

Supervisoryl 0000 0001 RRRR RRR PJF
Format
I
I 0000 0101 RRRR RRR P/F

I
I
I

Notes:

P
F
RRR
SSS

Figure 1-6.

= Poll bit (sent to secondary station)
= Final bit (sent to primary station)
= Nr (receive count)
= Ns (send count)

Control Fields for SDLC Commands and Responses--Modulus 128

Chapter 1.

DLC Links

1-7

Information Field of the FRMR Response Frame

Modulus 8:
I

I

I

I

I

I

I

I

I

I

I

I

Nr 101

Control Field

Byte 0

I

I

I

.L

I

I

I

I

I

I

I

Byte 2

Byte 1

L

I

Ns 1010 0 0 Olz y x wi

.L

.J

Modulus 128:
I

I

I

I

I

I

I

I

Control Field
I

Byte 0
.L

Note:

Field

I

I

101

I

I

Nr

I

I

I

I

I

I

I

I

I

I

1010 0 0 Olz y x wi

I

Byte 1

L

I

Ns

Byte 2
.L

Byte 3
.L

Byte 4
.L

.J

For modulus 128, if control field causing FRMR is an unnumbered format
(one-byte), it is placed in byte 0 and byte 1 is set to all O's.

C

Description
Control Field

Explanation/Usage
Control field of the rejected command, as
received

Nr

Receive Count

This station's present receiver frame
count (the existing count prior to FRMR)

Ns

Send Count

This station's present transmitter frame
count (the existing count prior to FRMR)

z

Rejection Indicators:
Count

0 = no error
1 = Received Nr disagrees with transmitted Ns

y

Buffer

0 = no error
1 = Buffer overrun (I-field is too long)

x

I-field

0 = no error
1 = Prohibited I-field received

w

Command

0 = no error
1 = Invalid or nonimplemented command received

Figure 1-7.

1-8

Information Field of the FRMR Response Frame:
modulus 8 and modulus
128.
In each byte, the low-order bit is sent fi rst and the
high-order bit is sent last.

SNA Formats

LINK TRAILER
(FRAME CHECK SEQUENCE)

Information Field

LH

LT

r
I
FCS

r------------

F

--------------~

I
I
x

x

x

Figure 1-8.

x

x

x

x

x

x

x

x

x

x

x

x

x

Frame Check Sequence Field of Link Trailer

The Frame Check Sequence field carries information that the receiver uses to check
the received frame for errors that may have been introduced by the communication
channel. This field contains a 16-bit check sequence that is the result of a
computation on the contents of both the LH (with the exception of the flag) and the
Information field at the transmitter. Cyclic redundancy checking (CRC) is used to
perform this calculation.
The receiver performs a similar computation and checks its results.

Chapter 1.

DLC Links

1-9

LINK TRAILER
(FLAG)

LH

Information Field

LT

r

I
FCS

F

r-------------.J
I
I

o

Figure 1-9.

Flag Field of Link Trailer:

1

1

1

always X'7E',

1

1

1

o

B'01111110'.

All frames end with a Flag field.
The configuration of the ending (trailing) flag
is the same as that of the beginning (leading) flag that is present in the link
header:
01111110 (X'7E').

1-10

SNA Formats

TOKEN-RING NETWORK DLC

The token-ring network DLC consists of two sublayers:
the medium access control and
the logical link control.
The medium access control (MAC) sublayer controls the
routing of information between the physical layer and the logical link control
sublayer.
It provides the following functions:
address recognition, frame copying,
frame delimiting, and 32-bit frame check sequence generation and verification.
The
logical link control (LLC) sublayer provides sequential, connection-oriented data
transfer.
The following commands and responses, a subset of those shown 1n Figure 1-6, are
used by the LLC sublayer in the token-ring network:

Format

Command/Response Name

Unnumbered Format

DM Response
DISC Command
UA Response
SABME Command
FRMR Response
XID Command or Response
Test Command or Response

Supervisory Format

Receive Ready
Receive Not Ready
Reject

Information Format

Figure 1-10.

Numbered Information Present

LLC Commands and Responses

The code points associated with these commands and responses are the same as those
shown in Figure 1-6.
The token-ring network DLC, in contrast to SDLC, transmits the high-order bit first
and the low-order bit last within each byte.
Also, zero bit insertion is required
on the token-ring network, since the differential Manchester encoding technique is
used.

Chapter 1.

DLC Links

1-11

Additional information about the token-ring network Ole architecture is contained 1n
the Token-Ring Network Architecture Reference.

1-12

SNA Formats

CHAPTER 2.

EXCHANGE IDENTIFICATION (XIDl INFORMATION FIELDS

This chapter describes the formats of the information field of the DLC XID command
and response.

DLC XID INFORMATION-FIELD FORMATS

o

I

2-517
2-5

bits 0-3, format of XID I-field:
X'O' fixed format:
only bytes 0-5 are included
X'l' variable format (for Tl12.0 to T415 node exchanges):
bytes
O-p are included
X'2' reserved
X'3' variable format (for T2.1 to T2.1/BF and T2.0 to T5 node
exchanges):
bytes O-p are included
X'B'-X'F' defined for external standards organizations
bits 4-7, type of the XID-sending node:
X'l' Tl
X'2' T2
X'3' reserved
X'4' subarea node (T4 or T5)
length, in binary, of variable-format XID I-field (bytes O-p)j reserved
for fixed-format XID I-field
Node Identification
bits 0-11, block number: an IBM product specific number; see the
individual product specifications for the specific values used
Note:
The values all O's and alII's indicate that bytes 2-5
do not contain a unique node identifier.
bits 12-31, ID number: a binary value that, together with the block
number, identifies a specific station uniquely within a
customer network installation; the ID number can be assigned
in various ways, depending on the product; see the individual
product specifications for details
Note:
When the Block Number field does not contain all O's or
alII's, a value of all O's in the ID number indicates that no
ID number has been assigned.
Note:
For XID format 3, the contents of bytes 2-5 of the node
identification field are used in some instances as a
role-negotiation-value to resolve contention in protocol roles of nodes,
e.g., primary/secondary DlC roles or the ODAI value to be appended to the
(OAF', DAF') values assigned at a node. When a role-negotiation value is
needed and the node does not supply a unique node identification value, it
supplies a random value in the ID number field.
• End of Format 0

Chapter 2.

Exchange

tification (XID) Information Fields

2-1

XIn I-field

6-p

6-7
8
8

9

10-11

12

Format 1 Continuation
Reserved
Link Station and Connection Protocol Flags
bits 0-1, reserved
bit 2, link-station role of XIn sender:
o sender is a secondary link station (nonnegotiable)
1 sender is a primary link station (nonnegotiable)
bit 3, reserved.
bits 4-7, link-station transmit-receive capability:
X'O' two-way alternating
X'l' two-way simultaneous
Characteristics of the node of the XIn sender:
bits 0-1, reserved
bits 2-3, segment assembly capability of the path control element of the
node:
00 the Mapping field is ignored and PIUs are forwarded unchanged
01 segments are assembled on a link-station basis
10 segments are assembled on a session basis
11 only whole BIUs are allowed
bits 4-5, reserved
bit 6, short-hold status (reserved if byte 9, bit 7 is set to 0):
o sender not already engaged in a logical connection using
short-hold mode
1 sender already engaged in a logical connection using short-hold
mode
bit 7, short-hold capability of the XID sender:
o short-hold mode not supported
1 short-hold mode supported
Maximum I-field length that the XIn sender can receive:
bit 0, format flag:
Obits 1-15 contain the maximum I-field length (only value
defined)
bits 1-15, maximum I-field length, in binary
bits 0-3, reserved
bits 4-7, SDLC command/response profile:
X'O' SNA link profile (only value defined)
Note: These profiles refer to the mandatory
command/response support on an SDLC link, as follows:
•

2-2

SNA Formats

For an SnLC link in normal response mode (NRM/NRME),
having a point-to-point or multipoint configuration
(determined from system definition), the support
required is:

XID I-field
Commands

Responses

I-frames
RR
RNR
Test
XID
SNRM/SNRME
Disconnect

I-frames
RR
RNR
Test
XID
UA
DM
RO
Frame Reject
Reject

Reject

Note ~ The RD response is sent by the secondary
station if and only if the PU in its node receives a
DISCONTACT request from its CPo
Note 2:
Reject is required only if both sender and
receiver have two-way simultaneous transmit-receive
capability.
•

For an SDLC link in normal response mode (NRM), having a
loop configuration (determined from system definition),
the support required is:

Commands

Responses

I-frames
RR
RNR
Test
XID
SNRM
Disconnect
UP

I-frames
RR
RNR
Test
XID
UA
DM

Configure

Frame Reject
Configure
Beacon
RD

Note:
The RD response is sent by the secondary station
if and only if the PU in its node receives a DISCONTACT
request from its CPo
13

14-15

bits 0-1, reserved
bit 2, SOLC initialization mode options:
0 SIM and RIM not supported
1 SIM and RIM supported
bits 3-7, reserved
Reserved

Chapter 2.

Exchange Identification (XIO) Information Fields

2-3

XID I-field

16

17
18-p
18
19-p
18-p
18
19-n
19
20-n
n+l-p

n+l
n+2-p

6-p
6-7
8-9

2-4

bit 0, reserved
bits 1-7, maximum number of I-frames that can be received by the XID
sender before an acknowledgment is sent, with an implied modulus
for the send and receive sequence counts--less than 8 implies a
modulus of 8, 8 or greater implies a modulus of 128
Reserved
• For byte 9, bit 7 = 0 (short-hold mode not supported)
SDLC Address Assignment Field
Length (p minus 18), in binary, of the SDLC address to be assigned
Secondary station address to be assigned
• For byte 9, bit 7 = 1 (short-hold mode supported)
Short-Hold Mode Dependent Parameters
Reserved
Dial Digits of XID Sender
Number, in binary, of dial digits
Dial digits: a string of digits, each having the form X'Fn' (0~nS9)
Dial digits of an available short-hold mode port
Note:
This field is included only in an XID from a T4 or T5 node and only
for an incoming callan an already logically busy (byte 9, bit 6 = 1)
short-hold mode port.
If this field is not included, then p = n.
Number, in binary, of dial digits of an available short-hold mode port, if
one exists
Dial digits of an available short-hold mode port: a string of digits,
each having the form X'Fn' (0~n~9)
Note:
Byte n+l is set to the value X'OO' and the n+2-p field is not
included if no free alternate port is found.
In this case the station may
retry later on the same port used for the current XID.
• End of Format 1

Format 3 Continuation
Reserved
Characteristics of the node of the XID sender:
bit 0, INIT-SELF support:
o INIT-SELF may be sent to the XID sender
Note:
If the XID sender does not contain an SSCP, it forwards
any INIT-SELF received to the proper node for processing, which
returns the response to the originator of the request.
1 INIT-SElF (and character-coded logon) cannot be sent to the XID
sender
Note:
For bits 0-1, the value 11 is reserved.
bit 1, stand-alone BIND support:
o BIND may be sent to the XID sender without a prior INITIATE
sequence
1 BIND may not be sent to the XID sender
Note:
For bits 0-1, the value 11 is reserved.
bit 2, whole-BIND-PIUs generated indicator:
o this node can gener~te BIND PIU segments
1 this node does not generate BIND PIU segments
bit 3, whole-BIND-PIUs required indicator:
o this node can receive BIND PIU segments
1 this node cannot receive BIND PIU segments

SNA Formats

XID I-field

10

11-16
17

18-n
18

19
19

20
21-22

Note:
The value 10 for bits 2-3 is reserved.
bits 4-7, reserved
bit 8, ACTPU suppression indicator:
o ACTPU for an SSCP-PU session requested
1 ACTPU for an SSCP-PU session not requested
bits 9-11, reserved
bits 12-13, XID exchange state:
00 exchange state indicators not supported (set only by
implementations not at the current level of SNA)
01 negotiation-proceeding
10 prenegotiation exchange
11 nonactivation exchange
bits 14-15, reserved
BIND pacing support over the link:
bit 0, adaptive BIND pacing support as a BIND sender:
o adaptive BIND pacing as a BIND sender not supported
1 adaptive BIND pacing as a BIND sender supported
bit 1, adaptive BIND pacing support as a BIND receiver:
o adaptive BIND pacing as a BIND receiver not supported
1 adaptive BIND pacing as a BIND receiver supported
Note:
The combinations of values for bits 0 and 1 have the
following meanings:
00 means adaptive BIND pacing is not
supported; 01 means one-way adaptive BIND pacing is supported; 10
is not used; and 11 means adaptive BIND pacing is fully supported.
bits 2-7, reserved
Reserved
DLC type:
X'Ol' SDLC
X'02' System/370 channel to controller DLC
DLC Dependent Section
Length, in binary, of the DLe Dependent Section field (Length field
includes itself in the length specified.)
• For SDLC
Link Station and Connection Protocol Flags
bit 0, reserved
bit 1, ABM support indicator:
o XIn sender cannot be an ABM combined station
1 XIn sender can be an ABM combined station
bits 2-3, link-station role of XID sender:
00 sender is a secondary link station (nonnegotiable)
01 sender is a primary link station (nonnegotiable)
10 reserved
11 negotiable (primary or secondary capability)
Note:
For ABM stations, the value of bits 2-3 is used only for
the purposes of DAF'-DAF' assignment and deciding which node
sends the Set Mode command.
bits 4-5, reserved
bits 6-7, link-station transmit-receive capability:
00 two-way alternating
01 two-way simultaneous
Reserved
Maximum BTU length that the XID sender can receive:
bit 0, format flag:
Obits 1-15 contain the maximum BTU length (only value defined)

Chapter 2.

Exchange Identification (XID) Information Fields

2-5

XIO I-field

23

bits 1-15, maximum BTU length, in binary
bits 0-3, reserved
bits 4-7, SOlC command/response profile:
X'O' SNA link profile (only value defined)
Note: These profiles refer to the mandatory
command/response support on an SOlC link, as follows:
•

For an SOlC link in normal response mode (NRM/NRME),
having a point-to-point or multipoint configuration
(determined from system definition), the support
required is:

Commands

Responses

I-frames
RR
RNR
Test
XIO
SNRM/SNRME
Disconnect

I-frames
RR
RNR
Test
XIO
UA
DM
RD
Frame Rej ect
Reject

Reject

Note ~ The RD response is sent by the secondary
station if and only if the PU in its node receives a
DISCONTACT request from its CPo
Note 2:
Reject is required only if both sender and
receiver have two-way simultaneous transmit-receive
capability.
•

For an SDlC link in normal response mode (NRM), having a
loop configuration (determined from system definition),
the support required is:

Commands

Responses

I-frames
RR
RNR
Test
XIO
SNRM
Disconnect
UP

I-frames
RR
RNR
Test
XIO
UA
DM

Configure

2-6

SNA Formats

Frame Reject
Configure
Beacon
RO

XID I-field
Note:
The RD response is sent by the secondary station
if and only if the PU in its node receives a DISCONTACT
request from its CPo
•

For an SDLC link
(determined from
field), having a
support required

Commands
I-frames
RR
RNR
Reject
SABME
Disconnect
Test
XID

in asynchronous balanced mode (ABM)
the Link-Station Role of XID Sender
point-to-point configuration, the
is:

Responses

RR
RNR
Reject
UA
DM
Test
XID
Frame Reject

Note 1: All commands and responses are transmitted and
received in two-octet format (extended control field).
Note ~ Frame Reject is not required to be transmitted;
receive capability is required.
24

25-26
27

28(=n)

19-20

bits 0-1, reserved
bit 2, SDLC initialization mode options:
o SIM and RIM not supported
1 SIM and RIM supported
bits 3-7, reserved
Reserved
bit 0, reserved
bits 1-7, maximum number of I-frames that can be received by the XID
sender before an acknowledgment is sent, with an implied modulus
for the send and receive sequence counts--less than 8 implies a
modulus of 8, 8 or greater implies a modulus of 128
Reserved
End of DLC Dependent Section
• For Channel DLC (CDLC):
System/370 Channel between T4 and T2.1 nodes
Note:
The System/370 node always contains the primary link station for
CDLC; the controller always contains the secondary station.
Indicators:
bit 0, change CDLC parameters (may be set by the primary on a non
activation XID and echoed by the secondary; reserved for both
primary and secondary for other XID exchange types):
o do not change CDLC parameters
1 change CDLC parameters to the values in this XID; the parameters
that may be changed are buffer pre-fetch, number of read
commands, buffer size, blocking delay, Attention time-out, and
time units

Chapter 2.

Exchange Identification (XID) Information Fields

2-7

XIO I-field
bit

21-22
23
24-25
26-27

28-29

30-31

32-33

34-35

36(=n)

n+l-p

2-8

1, Attention time-out support (set by the secondary; reserved for the
primary):
o not supported
1 supported
bit 2, data streaming support specifies whether the XIO sender supports
channel data streaming:
o not supported
1 supported
bit 3, change COLC parameters support specifies whether the XIO sender
supports changing COLC parameters by means of a
nonactivation XIO exchange (see bit 0)
o not supported
1 supported
bits 4-15, reserved
Maximum Link PIU (LPIU) size:
length of the maximum LPIU that the XIO
sender can receive
Buffer pre-fetch:
number of buffers suggested for the secondary to
pre-allocate each time the secondary reads LPIUs from the primary
Number of Read commands:
number of Read CCWs the primary must include in
every read channel program used to read LPIUs
Buffer size:
for the primary, the size of the input area associated with
each Read CCW in channel programs used to read LPIUs; for the secondary,
the approximate number of bytes available for LPIU storage in each buffer
used for accepting LPIUs from the primary
Blocking delay: maximum interval that the secondary delays between the
time it has an LPIU to send to the primary and the time it presents an
Attention to the primary
Attention time-out (ATO): maximum interval that a secondary awaits a read
channel program after presenting an Attention to the primary; if the
time-out expires, a secondary-detected inoperative station condition is
declared. This time-out value is also used for idle detection (1/2 ATO is
used), second-chance Attention (1/2 ATO is used), and primary-detected
inoperative station (3/2 ATO is used)
Note:
The secondary has the option of presenting a second Attention,
called a second-chance attention to handle the case of loss of the first
Attention.
Previous number of Read commands: set by the secondary in an XIO sent in
reply to a change-COLC-parameters non activation XIO to specify the
number-of-read-commands parameter (see bytes 24-25) that was active prior
to the change; otherwise, reserved
Previous primary buffer size: set by the secondary in an XIO sent in
reply to a change-COLC-parameters non activation XIO to specify the
primary-buffer-size parameter (see bytes 26-27) that was active prior to
the change; otherwise reserved
Time units: specifies the time units used for Attention time-out and
blocking delay
X'OO' 100-millisecond time units
X'Ol' I-millisecond time units
End of OLC Oependent Section
Control vectors, as described in "Control Vectors" in Chapter 8
Note: The following control vectors may be included:
X'OE' PU Name control vector:
type X'Fl', not network-qualified PU name
(always present; the network identifier is always used, i.e., valid
lengths of the PU name are 1 to 8 bytes with an imbedded period)

SNA Formats

XIO I-field
X'OE' Network Name control vector:
type X'F4', network-qualified CP name
(always present; the network identifier is always used, i.e., valid
lengths of the CP name are 3 to 17 bytes with an imbedded period)
X'lO' Product Set 10 control vector (always present)
Note:
When included in XIO, the product set 10 is limited to 60
bytes or less in length.
X'22' XIO Negotiation Error control vector (present when an error during
XIO negotiation is detected; more than one may be present)

Chapter 2.

Exchange Identification (XIO) Information Fields

2-9

2-10

SNA Formats

CHAPTER 3.

TRANSMISSION HEADERS

INTRODUCTION
A transmission header (TH) is the leading, or only, field of every PIU.
The first
half-byte of any TH is the Format Identifier (FID) field.
FID2 corresponds to
hexadecimal value 2 in the FID field.
The FID2 TH is described below.

Chapter 3.

Transmission Headers

3-1

FID2

FID2 LAYOUT

Byte

o

FID2--Format Identification
MPF--Mapping Field
ODAI--OAF'-DAF' Assignor
Indicator
EFI--Expedited Flow Ind.

2

DAF'--Destination Address

4

SNF--Sequence Number Field

Figure 3-1.

Reserved Byte

OAF'--Origin Address

Transmission Header for FID Type 2

FID2 Field Descriptions
FID2 is the format used between a T4 or T5 node and an
adjacent T2 (i.e., T2.0 or T2.1) node, or between adjacent
T2.1 nodes.

o

3-2

bits 0~3, FID2--Format Identification:
0010
bits 4-5, MPF--Mapping Field. The MPF consists of bit 4, the Begin-BIU
(BBIU) bit, and bit 5, the End-BIU (EBIU) bit.
It specifies
whether the information field associated with the TH is a
complete or partial BIU, and, if a partial BIU, whether it is
the first, a middle, or the last segment.
10 first segment of a BIU (BBIU, -EBIU)
00 middle segment of a BIU (-BBIU, -EBIU)
01 last segment of a BIU (-BBIU, EBIU)
11 whole BIU (BBIU, EBIU)
bit 6, ODAI--OAF'-DAF' Assignor Indicator (used for T2.1 - T2.1IBF flows;
otherwise, reserved). The DDAI indicates which node assigned (at
session-activation time) the DAF'-DAF' values carried in the TH
(see SNA Format and Protocol Reference Manual: Architecture
----Logic for Type 2.1 Nodes for details). Together with the DAF' and
OAF' values, the ODAI value forms a 17-bit local-form session
identifier (LFSID); the DAF' and OAF' values used in the TH in one
direction are reversed in the other direction.
Note: See Chapter 4 for the discussion of the adaptive BIND
pacing IPM, which makes exceptional use of these fields.
bit 7, EFI--Expedited Flow Indicator. The EFI designates whether the PIU
belongs to the normal or expedited flow.
Normal-flow PIUs are
kept in order on a session basis by PC; so are expedited-flow
PIUs.
Expedited-flow PIUs can pass normal-flow PIUs flowing in
the same direction at queuing points in TC within half-sessions

SNA Formats

FID2
and boundary function session connectors.
meaning:
o normal flow
1 expedited flow
1

2
3

4-5

It has the following

Reserved
DAF'--Destination Address Field. See discussion above for ODAI.
OAF'--Origin Address Field. See discussion above for ODAI.
Note: The PU T2.0 is always assigned the local address value of O.
Therefore, BIUs to the physical unit always have the associated DAF' = 0;
BIUs from the physical unit always have the associated OAF' = o.
The OAF'
is also 0 for BIUs from the SSCP, and DAF' is 0 for BIUs to the SSCP.
For
T2.l nodes, an OAF' or DAF' can also be set to 0 for independent LU-LU
sessions (see SNA Type 2.1 Node Reference for details).
SNF--Sequence Number Field. The Sequence Number Field contains a
numerical identifier for the associated BIU; path control, when
segmenting, puts the same SNF value in each segment derived from the same
BIU.
The numerical identifier used depends on a number of factors. ·If
the TS profile indicates sequence numbers are not used, the SNF value is a
l6-bit identifier that distinguishes a request being sent or responded to
from any other outstanding request on the same flow.
If the TS profile
indicates sequence numbers are used, the flow is a factor.
Expedited-flow
requests (other than SIG for LU 6.2) carry l6-bit identifiers;
expedited-flow responses echo the SNF values of their corresponding
requests.
Normal-flow requests, other than between LU 6.2's, carry 16-bit
numerical values ranging in value from 1-65,535 (incremented by 1 for each
request) and wrapping through 0 thereafter; the corresponding responses
echo their SNF values. The table below defines the SIG and normal-flow
SNF usage between LU 6.2's.
Request

Response

------- -------FMDILUSTAT with
FMDILUSTAT with
BIS
RTR
SIG

BB
~BB

A
A
A
A
B

C
B
D
E

E

A: A 16-bit number (1-65,535) incremented by 1 for each request
and wrapping through 0 thereafter
B: Low-order 15 bits of the SNF in the request that carried the
last successful BB; the high-order bit identifies the
half-session that started the bracket (0 = secondary, 1 =
primary); in the case of the first bracket of a session, where
the BB is implied, not sent, the low-order 15 bits are 0 and
the high-order bit is 1.
C: low-order 15 bits of the SNF in the BB request being responded
to; the high-order bit identifies the sender of the BB request
(0 = secondary, 1 = primary).
D: The half-session does not respond to BIS.
E: Same value as the corresponding request.

Chapter 3.

Transmission Headers

3-3

FID2
Note:
For additional details of lU 6.2 processing, see SNA Format
and Protocol Reference Manual:
Architecture logic for lU Type
6.2.

3-4

SNA Formats

CHAPTER 4.

REQUEST/RESPONSE HEADERS

INTRODUCTION
This chapter identifies the formats and meanings of the request and response headers
(RH); Chapter 5.1 and Chapter 5.2 describe the request and response units (RU).
To distinguish between a request and a response, examine bit 0 in byte 0 of the RH:
If bit 0

= 0:

the RH is a request header and the associated RU is a request
unit.

If bit 0

= 1:

the RH is a response header and any associated RU 1S a response
unit.

Figure 4-1 on page 4-2 provides a summary of the bytes and field names 1n the RH.
Three message units--IPR, IPM, and EXR--which make use of the RH for special
purposes, are described at the end of this chapter.

Chapter 4.

Request/Response Headers

4-1

RH Formats
Request. Header
I

I

I

RU
RRII
=0 I Categoryl r

FI

I

I

I
I
I
SDII BCII ECII

Request

Byte 0
I

I

RU
RRII
=1 I Categoryl r

FI

I
SDII 1

Response

1

Request

I

I

I

I
I
IDRll1 r

I
I
I
IDR211 ERII r

I

I

I
I
IDRlll r

I
I
I
IDR2I1 RTI I r

I
I
I
I RLWI I QRll PI

Byte 1

Response

I

I

I

I
I r

I

I
QRII PI

I

I

I

Request

I

I

I
I
I
I
CSI I EDll PDIICEBII

I
I
I
BBII EBII CDII r

Byte 2
11

I

I

I

I

I

I

I

I

I rl = Reserved

I
I r

I
I r

I
I r

I
I r

I
I r

I
I r

I
I r

I
I r

Response

'--..J

Field
RRI

Description
Request/Response indicator

Explanation/Usage
o = request (RQ); 1 = response (RSP)

RU
Category

Request/Response Unit Category

00
01
10
11

Fl

Format indicator

o

= no FM header (~FMH), for LU-LU sessions;
or character-coded without an NS header
(~NSH), for network services (NS)
1 = FM header (FMH) follows, for LU-LU
sessions; or field-formatted with an
NS header (NSH), for NS

SDI

Sense Data Included indicator

o

BCI

Begin Chain indicator

o = not first in chain (~BC);
1 = first in chain (BC)

Figure 4-1.

4-2

=
=
=
=

= not included

RH Formats (continued next page)

SNA Formats

FM data (FMD)
network control (NC)
data flow control (DFC)
session control (SC)

(~SD);

1 = included (SD)

RH Formats
Explanation/Usage

Field
ECI

Description
End Chain indicator

DR1I

Definite Response 1 indicator

o = -DR1;

1

= DRI

DR2I

Definite Response 2 indicator

o = -DR2;

1

= DR2

ERI

Exception Response indicator

Used in conjunction with DR11 and DR2I
to indicate, in a request, the form of
response requested. Values and
meanings of DRIll, DR2l, ERI are:
000 = no-response requested
10010101110 = definite-response
requested
10110111111 = exception-response
requested

RTI

Response Type indicator

0 = positive (+); 1 = negative

RLWI

Request Larger Window
i,ndicator

0 = larger pacing window not requested

o = not last in chain (~EC);
1 = last in chain (EC)

(-)

(~RLW);

1 = larger pacing window requested (RLW)
QRI

Queued Response indicator

o
1

= response bypasses TC queues

= enqueue

(~QR);

response in TC queues (QR)

PI

Pacing indicator

0 = -PAC; 1 = PAC

BBI

Begin Bracket indicator

0 = ~BB; 1 = BB

EBI

End Bracket indicator

0 = -EB; 1 = EB
(reserved for LU type 6.2)

CDI

Change Direction indicator

0 = do not change direction
1 = change direction (CD)

CSI

Code Selection indicator

0

EDI

Enciphered Data indicator

0 = RU is not enciphered
1 = RU 1S enciphered (ED)

PDI

Padded Data indicator

0 = RU 1S not padded (~PD);
1 = RU is padded (PD)

CEBI

Conditional End Bracket
indicator

o = not conditional end bracket (~CEB);
1 = conditional end bracket (CEB) (used
for lU type 6.2; else, reserved)

Figure 4-1.

= code

(~CD);

0; 1 = code 1
(~ED);

RH Formats

Chapter 4.

Request/Response Headers

4-3

RH Formats

RH FORMATS
The request/response header (RH) is a 3-byte field; it may be a request header or a
response header. The RH control fields shown in Figure 4-1 on page 4-2 are
described below.
Request/Response Indicator (RRI):

Denotes whether this is a request or a response.

RU Category:
Denotes that the BIU belongs to one of four categories: session
control (SC), network control (NC), data flow control (DFC), or function management
data (FMD).
(The NC category is not supported by T2.1 nodes.)
Format Indicator:
Indicates which of two formats (denoted Format 1 and Format 0) is
used within the associated RU (but not including the sense data field, if any; see
Sense Data Included indicator, below).
For SC, NC, and DFC RUs, this indicator is always set to Format 1.
On FMD requests for SSCP-SSCP, SSCP-PU, and SSCP-LU sessions, Format 1 indicates
that the request RU includes a network services (NS) header and is field-formatted
(with various encodings, such as binary data or bit-significant data, in the
individual fields).
Format 0 indicates that no NS header is contained in the
request RU and the RU is character-coded.
The Format indicator value on a response
is the same as on the corresponding request.
For LU-LU sessions that support FM headers on FMD requests, Format 1 indicates that
an FM header begins in the RU (see "Chapter 10. Function Management Headers");
Format 0 indicates this is not the case. The Format indicator is always set to 0 on
positive responses; negative responses are implementation dependent.
For LU-LU sessions that do not support FM headers, the meaning of this indicator on
requests, positive responses, and negative responses is implementation dependent.
(A BIND session parameter indicates whether FM headers are supported by the session.
For further information, see Chapter 5.1 for details on BIND.)
Sense Data Included Indicator (SDI):
Indicates that
--------included in the associated RU.
The sense data field

a 4-byte sense data field is
(when present) always
immediately follows the RH and has the format and meaning described in Chapter 9.
Any other data contained in the RU follows the sense data field.
Sense data is
included on negative responses and on EXRs, where it indicates the type of condition
causing the exception.
(The Format indicator does not describe or affect the sense data, which is always 1n
the 4-byte format shown in Chapter 9.)
Chaining Control:
Indicates that a sequence of contiguous transmitted requests is
being grouped in a chain. Two indicators, Begin Chain indicator (BCI) and End Chain
indicator (ECI), together denote the relative position of the associated RU within a
chain. The 1 values of these indicators (BCI = 1 and ECI = 1) are referred to as BC
and EC, respectively.
(BC,

4-4

~EC)

= first

SNA Formats

RU in chain

RH Formats
(-BC, -EC)

= middle

(-BC, EC)

= last

RU in chain

(BC, EC)

= only

RU in chain

RU in chain

Responses are always marked "only RU in chain."
Form of Response Requested:
In a request header, defines the response protocol to
be executed by the request receiver.
Three bits in a request header specify the form of response that is desired.
They
are:
Definite Response 1 indicator (DRII), Definite Response 2 indicator (DR2I),
and the Exception Response indicator (ERI).
They can be coded to request:
1.

No-response, which means that a response will not be issued by the half-session
receiving the request.
(DRII,DR2I) = (0,0) = (-DRl,-DR2) and ERI=O is the only
coding possible; the abbreviation RQN refers to a request with this coding.
(A
special response, ISOLATED PACING RESPONSE [IPR], does set [DRll,DR2I,ERI] =
[0,0,0], but it is used independently of the other responses listed.
IPR is
sent in connection with session-level pacing; the sequence number in its
associated TH does not correlate it to any given request.)

2.

Exception response, which means that a negative response will be issued by the
half-session receiving the request only in the event of a detected exception (a
positive response will not be issued).
(DRll, DR2I) = (1,0)1(0,1)1(1,1) and
ERI=l are the possible codings; RQEl, RQE2, and RQE3 are the abbreviations,
respectively; the abbreviation RQE or RQE* refers to a request with any of these
codings.

3.

Definite response, which means that a response will always be issued by the
half-session receiving the request, whether the response is positive or
negative.
(DRIl, DR2I) = (1,0)1(0,1)1(1,1) and ERI=O are the possible codings;
RQDl, RQD2, and RQD3 are the abbreviations, respectively; the abbreviation RQD
or RQD* refers to a request with any of these codings.

A request that asks for an exception response or a definite response has one or both
of the DRI1 and DR21 bits set to 1 (three combinations); a response to a request
returns the same (DRll, DR21) bit combination (see Figure 4-2 on page 4-6).
The setting of the DRII, DR2l, and ERI bits varies by RU category.
In the case of
LU-LU sessions (e.g., LU 6.2), BIND parameters specify the form of response to be
requested during the session; Figure 4-2 on page 4-6 shows the values in table form.
For sessions that use sync point protocols with TS profile 4 (LU 6.1), RQD2 or RQE2
asks for the commitment of a unit of work that is to be shared between the session
partners; RQDl is used to request a response when the current unit of work is not to
be committed. The table for this set of values is given in Figure 4-3 on page 4-8.
For nonzero, non-LU 6.2, LU types that do not use sync point protocols, the specific
meanings of the DRI1 and DR21 bits are defined in SNA----Sessions Between Logical
Units; for LU type 0, the interpretations of the DRI1 and DR21 bits (and
distinctions among the three settings) are implementation-dependent.

Chapter 4.

Request/Response Headers

4-5

RH Formats
The (DRII, DR2I, ERI) = (0, 0, 1) combination is reserved.

REQUEST

VALID RESPONSE

MEANING OF RESPONSE

RQDI=(I,O,O)

+RSPI=(I,O,O)
-RSPI=(I,O,I)

positive response
negative response

implied +RSPI
-RSPI=(I,O,I)

reply received with no intervening response
negative response

RQD2=(O,I,O)

+RSP2=(O,I,O)
-RSP2=(O,I,I)

CONFIRMED verb issued
SEND_ERROR verb issued

RQE2=(O,I,I)

implied +RSP2
-RSP2=(O,I,I)

reply received with no intervening response
no CONFIRMED verb issued

RQD3=(I,I,O)

+RSP3=(I,I,O)
-RSP3=(I,I,I)

CONFIRMED verb issued
SEND_ERROR verb issued

RQE3=(I,I,I)

implied +RSP3

reply received with no inter-I
vening response
I
no CONFIRMED verb issued
I

(Used by DFC)

RQEI=(I,O,I)

(Used by
DFC and PS)

(Used by PS)

-RSP3=(O,I,I)
(Used by PS)

I
I

Notes:
1.

Values displayed in this·table are in the order (DRII,DR2I,ERI) for requests
and (DRlI,DR2I,RTI) for responses.

2.

All ... EC requests a re sent as RQEI.

3.

RQN=(O,O,O) is not used.

Figure 4-2.

4-6

FMD Request/Response Combinations for Sessions between Two LU 6.2s

SNA Formats

RH Formats
Queued Response Indicator (QRI):
In a response header for a normal-flow RU, the
Queued Response indicator denotes whether the response is to be enqueued in TC
queues (QRI=QR), or whether it is to bypass these queues (QRI=~QR).
In a request
header for a normal-flow RU, it indicates what the setting of the QRI should be on
the response, if any, to this request (i.e., the values on the request and response
are the same).
For expedited-flow RUs, this bit is reserved.
The setting of the QRI bit is the same for all RUs in a chain.
Response Type:
In a response header, two basic response types can be indicated:
positive response or negative response.
For negative responses, the RH is always
immediately followed by four bytes of sense data in the RU. Thus, RTI=NEG and
RTI=POS occur jointly with SDI=SD and SDI=~SD, respectively.

Chapter 4.

Request/Response Headers

4-7

RH Formats

REQUEST

VALID RESPONSE

MEANING OF RESPONSE

RQDl=(l,O,O)

+RSPl=(l,O,O)
-RSPl=(l,O,l)

positive response
negative response

RQEl=(l,O,l)

-RSPl=(l,O,l)

negative response

RQD2=(O,l,O)

+RSP2=(O,l,O)
-RSP2=(O,l,l)

positive sync point response
negative sync point response

RQE2=(O,l,l)

-RSP2=(O,l,l)

negative sync point response

RQD3=(l,l,O)

+RSP3=(l,l,O)
-RSP3=(l,l,l)

positive sync point response
negative sync point response

RQE3=(l,l,l)

-RSP3=(l,l,l)

negative sync point response

Notes:
1.

Values displayed in this table are in the order (DRll,DR2l,ERl) for requests
and (DRll,DR2l,RTl) for responses.

2.

Each definiteor exception-response chain
has the same setting of
(DRIl,DR2l)--either (1,0) or (O,l)--on all requests with ECl = ~EC. When DRll
= 1 on these requests, the End-Chain request can carry (DR1l,DR2l) =
(1,0)1(1,1). When DR2l = 1 on these requests, the End-Chain request can carry
only (DR1l,DR2l) = (0,1). ERl is 0 only for definite-response chains and when
ECl = EC.

3.

RQN=(O,O,O) is not used.

Figure 4-3.

Request/Response Combinations For TS Profile 4 Sync Points

Three kinds of positive and negative responses correspond to the three valid (DR1I,
DR~l) combinations allowed on requests.
The settings of the LRll and DR2l bits in a
response always equal the settings of the DRII and DR21 bits of the
form-of-response-requested field of the corresponding request header.
Pacing:
In a request header, the Pacing Request indicator denotes that the sender
can accept a Pacing Response indicator.
The Pacing Response indicator in a response header is used to indicate to the
receiver that additional requests may be sent on the normal flow.
In the case of

4-8

SNA Formats

RH Formats
nonadaptive session-level pacing, the Pacing Response indicator may be ~ 1n an RH
that is attached to a response RU on the normal flow; or, if desired, a separate, or
isolated, response header may be used, to which no RU is attached. This latter RH
signals only the pacing response; it is called an ISOLATED PACING RESPONSE (IPR);
isolated and non-isolated pacing responses are functionally equivalent.
In the case
of adaptive session-level pacing or adaptive BIND pacing, only an ISOLATED PACING
MESSAGE (IPM) is used as a pacing response; it is similar to an IPR, but carries
additional information.
IPR and IPM are discussed further in a later section of
this chapter.
Bracket Control:
Used to indicate the beginning or end of a group of exchanged
requests and responses called a bracket.
Bracket protocols are used only on LU-LU
sessions.
When used, BB appears on the first request in the first chain of a
bracket and denotes the beginning of the bracket; the end of the bracket is
indicated in one of two ways, depending on LU type.
•

For LU 6.2, CEB appears on the last request of the last chain of a bracket.
(When bracket usage is specified in BIND, the BIND request carries an implied
BB.) The bracket indicators are set only on LUSTAT and FMD requests, and are
thus sent normal-flow.

•

For other LU types, the end of bracket is delimited by setting EBI to EB in the
first request of the last chain in the bracket.

Change Direction Indicator (CDI):
Used when there is half-duplex (HDX) control of
the normal flows within a session (not to be confused with link-level HDX
protocols).
It permits a sending half-session to direct the receiving half-session
to send. The HDX protocol is useful to half-sessions with limited input/output
capabilities that cannot simultaneously send and receive user data.
When used, CD
appears only on the last request in a chain; it is set only on LUSTAT and FMD
requests.
Code Selection Indicator (CSI):
Specifies the encoding used for the associated FMD
RU.
When a session is activated, the half-sessions can choose to allow use of two
codes in their FMD RUs (e.g., EBCDIC and ASCII), which they designate as Code 0 and
Code 1.
FM headers and request and response codes are not affected by the Code
Selection indicator.
For SC, NC, and DFC RUs, this bit is reserved.
Enciphered Data Indicator (EDI):
Indicates that information in the associated RU is
enciphered under session-level cryptography protocols.
Padded Data Indicator (PDI):
Indicates that the RU was padded at the end,-before
encipherment, to the next integral multiple of a bytes in length; the last byte of
such padding is the count of pad bytes added, the count being a number (1-7
inclusive) in unsigned a-bit binary representation.
Request Larger Window Indicator (RLWI):
For a request with PI=PAC, indicates, for
adaptive pacing, that the receiver should increase its window size (as specified in
the most recently returned IPM) if it is possible to do so; otherwise, the bit is
reserved. Typically, the sender sets RLWI to RLW if its residual pacing count is 0
when it receives a solicited IPM and its send pacing queue is not empty, indicating
that it could make use of a larger window size; otherwise, it sets RLWI to ~RLW.

Chapter 4.

Request/Response Headers

4-9

RH Formats

IPR, IPM, AND EXR
Three special message units exist in SNA:
ISOLATED PACING RESPONSE (IPR), ISOLATED
PACING MESSAGE (IPM), and EXCEPTION REQUEST (EXR). These are explained below.

ISOLATED PACING RESPONSE (IPR)

An IPR is used on a session if BIND specifies nonadaptive session-level pacing is
used; it indicates a pacing response, and can be used even when operating under
no-response protocols.
The following fielqs of the TH and RH are set for an IPR:
TH:
Either the normal or expedited flow may be indicated. The sequence number is
undefined (it may be set to any value, and is not checked by the receiver).
RH:
An IPR is coded all
indicator, and the Chain
X'830100' by the sender;
DRII, DR2I, PI) = (1, 0,

O's except for the Request-Response indicator, the Pacing
indicators, which are set to lis; thus, the IPR RH is coded
the receiver identifies an IPR by detecting that (RRI,
0, 1) and ignoring the remaining bits

ISOLATED PACING MESSAGE (IPM)

An IPM is used on a session if BIND and RSP(BIND) specify adaptive session-level
pacing is used.
A solicited IPM is sent by a receiver of paced requests either (1)
in response to a pacing request it receives, or (2) after sending, and receiving an
acknowledgment to, an unsolicited IPM with a next-window size of 0, which allows the
sender to resume sending requests.
An unsolicited IPM is sent as a result of
congestion at the IPM-generating node; no additional IPM (solicited or unsolicited)
may be sent until the unsolicited IPM is acknowledged by a reset acknowledgment IPM.
Both solicited and unsolicited IPMs specify the next-window size; in addition, an
unsolicited IPM resets the current-window residual pacing count so that any queued
requests at the sender are counted in a subsequent window. A reset acknowledgment
IPM is sent immediately to respond to an unsolicited IPM, thereby delimiting the end
of the current window.
A Pacing Request indicator received while an unsolicited IPM
is outstanding is ignored.
An IPM is used on a link basis between a T2.1 node and an adjacent boundary node or
T2.1 node for adaptive BIND pacing if the XID3 exchange on the link so allows.
This
use of IPM is the same as for adaptive session-level pacing, except the pacing
window applies only to BINDs flowing over the link.
The following fields are set for an IPM.
TH:
The expedited flow is indicated. The sequence number is as defined for an IPR.
For an adaptive BIND pacing IPM, the ODAI bit is always set to 0; the OAF'-DAF' pair
is set according to the sender's normal setting of the ODAI bit in BIND:
the one

4-10

SNA Formats

RH Formats
that sets ODAI to 0 in BIND, sets OAF' to X'Ol' and OAF' to X'OO' in the BIND pacing
IPM, while the other sets them to the same values reversed.
IPM:
0-2
3-5
3

4-5

The IPM consists of the RH and a 3-byte extension shown below.
RH:
X'830l00' (same as for an IPR, with the same receiver-checking
mentioned above)
IPM Extension
bits 0-1, type:
00 solicited: sent in response to a pacing request, or after
receiving a reset acknowledgment IPM acknowledging an
unsolicited IPM that carried a zero next-window size (so
paced requests can resume flowing)
01 unsolicited:
can be sent at any time, except when a previous
unsolicited IPM is still outstanding (no reset acknowledgment
yet received)
10 reset acknowledgment: sent to acknowledge receipt of an
unsolicited IPM
11 reserved
bit 2, reset current-window residual-count indicator:
o do not reset the residual count
1 reset the residual count to 0 (i.e., terminate the current
window)
Note: Currently, this bit is set to 1 in an unsolicited IPM, and
o otherwise.
bits 3-7, reserved
Next-window information:
bit 0, format:
0 (only value defined)
bits 0-15, next-window size: a binary value in the range 1-32,767 in
solicited IPMs, and 0-32,767 in unsolicited IPMs; echoed from
unsolicited IPMs in reset acknowledgment IPMs (the echoed value
is not checked when received)

EXCEPTION REQUEST (EXR)

Two EXR types are defined:
those replacing requests, and those replacing too-long
path information units (PIUs) received by transmission group control (TGC) from an
upper layer (e.g., ERC in an intermediate routing node).
EXRs replacing requests are generated by some component between the origin and
intended destination ofa request found to be in error. The following fields are
set in the TH, RH, and RU.
TH: The sequence number remains the same as in the request being replaced.
The
data count is altered to properly record the new BIU size. The Mapping field is set
to (BBIU, EBIU); an EXR replaces a complete BIU, not just one segment of a segmented
BIU.
All other fields are left as received.
RH:

The Sense Data Included bit is set to 1.

All other fields are unchanged.

Chapter 4.

Request/Response Headers

4-11

RU:
Bytes 0-3 contain sense data defining the last error detected, and in the same
format as returned in negative responses. The sense data is followed by the
original RU, truncated to no more than three bytes, as described for negative
responses.
EXRs replacing too-long PIUs are formatted as follows.
TH:
Like EXRs replacing requests, EXRs replacing too-long PIUs change only the
Mapping field (to lis) and the data count (to 10 in this case).
RH:
If the PIU is a request, the SOl field is set to indicate sense data is
included; the remainder of the RH is unchanged.
If the PIU is a middle or last
segment of a multi-segment BIU, an RH is supplied and set to X'07BOOO'.
RU:
Bytes 0-3 always contain the sense data, X'800AOOOO'.
If the PIU contained a
request, bytes 4-6 contain up to the first three bytes of the original RU.
Note:
A too-long PIU may be found to be a response.
In the case of a positive
response, the first three bytes are retained and a sense data value of X'800AOOOO'
is inserted ahead of them; the RH is changed to indicate SO and negative response.
In the case of a negative response, the existing sense data value is changed to
X'800AOOOO' and the following three bytes of the RU are retained; the RH is
unchanged.
In both cases, the TH is set to indicate BBIU, EBIU, and OCF=lO.

4-12

SNA Formats

CHAPTER 5.1.

REQUEST UNITS

INTRODUCTION TO REQUEST UNITS
This section contains detailed formats of the request units, arranged in
alphabetical order.
Each format description begins with the following heading:
"ABBREVIATED RU NAME; Origin-NAU-->Destination-NAU, Normal (Norm) or Expedi1ed (Exp)
Flow; RU Category (RU NAME)"
Notes:
1.

"RU Category" is abbreviated as follows:
DFC

data flow control

SC

session control

NC

network control

FMD NS(ma)

function management data, network services, management services
(Note:
formerly maintenence services)

FMD NS(s)

function management data, network services, session services

2.

The formats of character-coded FMD NS requests are implementation dependent.
LU-->LU FMD requests (e.g., FM headers) are described in Chapter 10 .

3.

All values for field-formatted requests that are not defined in this section are
reserved.

4.

The request-code value X'FF' and the NS-header values X'(317IBIF)F****' and
X'**(317IBIF)F**' are set aside for implementation internal use, and will not be
otherwise defined in SNA.

5.

Throughout the format descriptions, reserved is used as follows:
reserved bits,
or fields, are ones that currently are set to O's (unless explicitly stated
otherwise); reserved values are those that currently are invalid. Correct usage
of reserved fields is enforced by the sender; no receive checks are made on
these fields.

6.

Throughout the format descriptions, retired fields and values are those that
were once defined in SNA but are no longer defined. To accommodate
implementations of back-level SNA, current implementations of SNA treat retired
fields as follows: send checks enforce the setting of retired fields to all O's
except where other unique values are required (described individually); no
receive checks are made on these fields, thereby accepting back-level settings

Chapter 5.1.

Request Units

5.1-1

Request Units
of these fields.
Special handling of retired fields, such as echoing or passing
on retired fields as received, is discussed where appropriate.
7.

User data, control vectors, and session keys referred to in the format
descriptions are described in Chapter 7 and Chapter 8.

8.

A type 2.1 (l2.1) node.contains a control point (CP) rather than a physical
unit (PU).
However, it can support SSCP-PU_T2.0 flows, in which case the
designations "SSCP<-->PU_T2" or "SSCP<-->PU" in the RU descriptions should be
assumed to apply to the T2.1 node as well.

5.1-2

SNA Formats

Request Units

REQUEST UNIT SUMMARY INFORMATION
The following is a categorized list of RU abbreviations, followed by a list of RUs
indexed by NS headers and request codes.

SUMMARY OF REQUEST RUS BY CATEGORY

Request RUs prefixed by an asterisk (*) require response RUs that, if positive, have
an extended format containing data in addition to the NS header or request code.
The RUs prefixed by a plus sign (+) are retired from SNA. See product documentation
for information and support.
SC Requests
*ACTLU
*ACTPU
*BIND
CLEAR

CRV
DACTLU
DACTPU
RQR

SDT
*STSN
UNBIND

QC
QEC
RELQ
RSHUTD
RTR

SBI
SHUTC
SHUTD
SIG

+RECFMS

+REQMS

DFC Requests
BID
BIS
CANCEL
CHASE
LUSTAT
FMD NS(ma) Requests
NMVT
FMD NS(s) Requests
INIT-SELF

NOTIFY

TERM-SELF

Chapter 5.1.

Request Units

5.1-3

Request Units
INDEX OF RUS BY NS HEADERS AND REQUEST CODES

Within DFC, NC, SC, or any specific FMD NS category, the request code is unique.
However, while a request code has only one meaning in a specific category, a given
code (e.g., X'05') can represent different requests in separate categories (e.g.,
DFC, NC, and configuration services).
FMD NS Headers (third byte is the request cQde)
X'OI068I'
X'OI0683'
X'4I038D'

INIT-SELF ( Format 0)
TERM-SELF ( Format 0)
NMVT

X'8I0620'
X'8I068I'
X'810683'

NOTIFY
INIT-SELF (Format 1)
TERM-SELF (Format 1)

X'83'
X'84'
X'AO'
X'AI'
X'A2'
X'A3'
X'CO'
X'CO'
X'CI'
X'C2'
X'C8'
X'C9'

CANCEL (DFC)
CHASE (DFC)
SDT (SC)
CLEAR (SC)
STSN (SC)
RQR (SC)
SHUTD (DFC)
CRV (SC)
SHUTC (DFC)
RSHUTD (DFC)
BID (DFC)
SIG (DFC)

DFC, NC, and SC Request Codes
X'04'
X'05'
X'OD'
X'OE'
X'II'
X'12'
X'31'
X'32'
X' 7 0'
X'7I'
X'80'
X'8I'
X'82'

5.1-4

LUSTAT (DFC)
RTR (DFC)
ACTLU (SC)
DACTLU (SC)
ACTPU (SC)
DACTPU (SC)
BIND (SC)
UNBIND (SC)
BIS (DFC)
SBI (DFC)
QEC (DFC)
QC (DFC)
RELQ (DFC)

SNA Formats

ACTLU
DESCRIPTIONS OF REQUEST UNITS

ACTLUi SSCP-->LU, EXPi SC (ACTIVATE LOGICAL UNIT)
ACTLU is sent from an SSCP to an LU to activate a session
between the SSCP and the LU and to establish common
session parameters.

o
1

2

X'OD' request code
Indicators:
bit 0, reserved
bit 1, static/dynamic address indicator (reserved if byte 1, bit 0
o sender considers the LU address to be static
1 sender considers the LU address to be dynamic
bits 2-S, reserved
bits 6-7, type activation requested:
10 ERP (only value defined)
bits 0-3, FM profile:
X'O' FM profile 0
X'6' FM profile 6
bits 4-7, TS profile:
X'I' TS profile 1 (only value defined)

=

0):

ACTPUi SSCP-->PU, Exp; SC (ACTIVATE PHYSICAL UNIT)
ACTPU is sent by the SSCP to activate a session with the
PU, and to obtain certain information about the PU.
0
1

2

3-8

X'II' request code
bits 0-3, format:
X'O' Format 0
bits 4-7, type activation requested:
X 'I ' cold
X'2' ERP
bits 0-3, FM profile:
X'O' FM profile 0
bits 4-7, TS profile:
X'l' TS profile 1
A six-byte field that specifies the ID of the SSCP issuing ACTPU; the
first four bits specify the format for the remaining bits:
bits 0-3, format:
0000 (only value defined)
bits 4-7, PU type of the node containing the CP
bits 8-47, implementation and installation dependent binary identification

BID; LU-->LU, Norm; DFC (BID)
BID is used by the bidder to request permission to
initiate a bracket, and is used only when using brackets.
This RU is not used for LU 6.2.

o

X'C8' request code

Chapter S.l.

Request Units

S.I-S

BIND

BIND; PLU-->SLU, Exp; SC (BIND SESSION)
BIND is sent from a primary LU to a secondary LU to
activate a session between the LUs.
The secondary LU uses
the BIND parameters to help determine whether it will
respond positively or negatively to BIND.

o
1

2

3

4

5

5.1-6

X'31' request code
bits 0-3, format:
0000 (only value defined)
bits 4-7, type:
0000 negotiable (only value defined for LU 6.2)
0001 nonnegotiable
FM profile:
X'02' FM profile 2
X'03' FM profile 3
X'04' FM profile 4
X'07' FM profile 7
X'12' FM profile 18
X'13' FM profile 19 (only value defined for LU 6.2)
TS profile:
X'02' TS profile 2
X'03' TS profile 3
X'04' TS profile 4
X'07' TS profile 7 (only value defined for LU 6.2)
FM Usage--Primary LU Protocols for FM Data
bit 0, chaining use selection:
o only single-RU chains allowed from primary LU half-session
1 multiple-RU chains allowed from primary LU half-session (only
value defined for LU 6.2)
bit 1, request control mode selection:
o immediate request mode (only value defined for LU 6.2)
1 delayed request mode
bits 2-3, chain response protocol used by primary LU half-session for FMD
requests; chains from primary will ask for:
00 no response
01 exception response
10 definite response
11 definite or exception response (only value defined for LU
6.2)
bit 4, 2-phase commit for sync point (reserved if any TS profile other
than 4):
o 2-phase commit not supported
1 2-phase commit supported
bit 5, reserved
bit 6, compression indicator (reserved for LU 6.2):
o compression will not be used on requests from primary
1 compression may be used
bit 7, send End Bracket indicator:
o primary will not send EB (only value defined for LU 6.2)
1 primary may send EB
FM Usage--Secondary LU Protocols for FM Data
bit 0, chaining use selection:
o only single-RU chains allowed from secondary LU half-session

SNA Formats

BIND

1 multiple-RU chains allowed from secondary LU half-session (only
value defined for LU 6.2)
1, request control mode selection:
o immediate request mode (only value defined for LU 6.2)
1 delayed request mode
bits 2-3, chain response protocol used by secondary LU half-session for
FMD requests; chains from secondary will ask for:
00 no response
01 exception response
10 definite response
11 definite or exception response (only value defined for LU
6.2)
bit 4, 2-phase commit for sync point (reserved if any TS profile other
than 4):
o 2-phase commit not supported
1 2-phase commit supported
bit 5, reserved
bit 6, compression indicator (reserved for LU 6.2):
o compression will not be used on requests from secondary
1 compression may be used
bit 7, send End Bracket indicator:
o secondary will not send EB (only value defined for LU 6.2)
1 secondary may send EB
FM Usage--Common LU Protocols
bit 0, whole-BIUs required indicator (reserved in nonextended non-LU 6.2
BINDs):
o the sending node supports receipt of segments on this session
1 the sending node does not support receipt of segments on this
session; the maximum sent-RU size specified in bytes 10 and 11
of BIND and RSP(BIND) are negotiated so that BIUs on this
seSS10n are not segmented when sent to a node requiring whole
BIUs
bit 1, FM header usage:
o FM headers not allowed
1 FM headers allowed (only value defined for LU 6.2)
bit 2, brackets usage and reset state:
o brackets not used if neither primary nor secondary will send EB,
i.e., if byte 4, bit 7 = 0 and byte 5, bit 7 = 0; brackets are
used and bracket state managers' reset states are INB (1) if
either primary or secondary, or both, may send EB, i.e., if
byte 4, bit 7 = 1 or byte 5, bit 7 = 1; or (2) if FM profile 19
is specified (only value defined for LU 6.2)
0 brackets are used and bracket state managers' reset states are
INB
1 brackets are used and bracket state managers' reset states are
BETB
bit 3, bracket termination rule selection (reserved if brackets not used,
i.e., if byte 6, bit 2 = 0, byte 4, bit 7 = 0, and byte 5,
bit 7 = 0; and if FM profile is not 19):
o Rule 2 (unconditional termination) will be used during this
session
1 Rule 1 (conditional termination) will be used during this
session (only value defined for LU 6.2)
bit 4, alternate code set allowed indicator:
bit

6

Chapter 5.1.

Request Units

5.1-7

BIND

7

5.1-8

o alternate code set will not be used
1 alternate code set may be used
bit 5, sequence number availability for sync point resynchronization
(reserved if any TS profile other than 4 is used):
o sequence numbers not available
1 sequence numbers available
Note: Sequence numbers are transaction processing program
sequence numbers from the previous activation of the session
with the same session name; they are associated with the last
acknowledged requests and any pending requests to commit a unit
of work.
If no previous activation existed, the numbers are 0,
and this bit is set to o.
bit 6; BIS sent (reserved for TS profiles other than 4):
OBIS not sent
1 BIS sent
bit 7, BIND queuing indicator:
o BIND cannot be queued (held, pending resource availability, thus
delaying the BIND response)
1 BIND sender allows the BIND receiver to queue the BIND for an
indefinite period, thus delaying the sending of the BIND
response
Note:
BIND sender may provide a timer or operator interface to
send UNBIND if session-activation time exceeds BIND sender's
implementation-defined limits.
BIND queuing is terminated by
sending UNBIND to the BIND receiver.
bits 0-1, normal-flow send/receive mode selection:
00 full-duplex
01 half-duplex contention
10 half-duplex flip-flop (only value defined for lU 6.2)
11 reserved
bit 2, recovery responsibility (reserved if normal flow send/receive mode
is FOX, i.e., if byte 7, bits 0-1 = 00):
o contention loser responsible for recovery (see byte 7, bit 3 for
specification of which half-session is the contention loser)
1 symmetric responsibility for recovery (only value defined for lU
6.2)
bit 3, contention winner/loser (reserved if normal flow send/receive mode
is FOX, i.e., if byte 7, bits 0-1 = 00; or if the normal flow
send/receive mode is HDX-FF, brackets are not used, FM profile is
not 19, and symmetric responsibility for recovery is used, i.e.,
if byte 7, bits 0-1 = 10, byte 4, bit 7 = 0, byte 5, bit 7 = 0,
byte 6, bit 2 = 0, and byte 7, bit 2 = 1):
o secondary is contention winner and primary 1S contention loser
1 primary is contention winner and secondary is contention loser
Note: Contention winner is also brackets first speaker if
brackets are used.
Note: Contention winner is also brackets first speaker.
bits 4-5, alternate code processing identifier (reserved unless Alternate
Code Set Allowed indicator (byte 6, bit 4) is 1):
00 process alternate code FMD RUs as ASCII-7
01 process alternate code FMD RUs as ASCII-8 (only value defined
for lU 6.2)
Note: When the Alternate Code Processing Identifier indicator
is set to the value 01, the entire FMD request RU is to be
SNA Formats

BIND

8

9

translated using the transforms defined by the ANSI X3.26
Hollerith Card Code.
bit 6, control vectors included indicator:
o control vectors are not included after the SLU name (bytes
r+l-s)
1 control vectors are included after the SLU name (bytes r+1-s)
bit 7, half-duplex flip-flop reset states (reserved unless (1)
normal-flow send/receive mode is half-duplex flip-flop (byte 7,
bits 0-1 = 10) and (2) brackets are not used or bracket state
manager's reset state is INB (byte 6, bit 2 = 0»:
o HDX-FF reset state is RECEIVE for the primary and SEND for the
secondary (e.g., the secondary sends normal-flow requests first
after session activation)
1 HDX-FF reset state is SEND for the primary and RECEIVE for the
secondary (e.g., the primary sends normal-flow requests first
after session activation) (only value defined for LU 6.2)
TS Usage
bit 0, staging indicator for session-level pacing of the
secondary-to-primary normal flow:
o the secondary send window size (byte 8, bits 2-7) and the
primary receive window size (byte 13, bits 2-7) are for
one-stage pacing (The secondary send window size is always equal
to the primary receive window size.)
1 the secondary send window size (byte 8, bits 2-7) and the
primary receive window size (byte 13, bits 2-7) are for
two-stage pacing
Note:
The meanings of 0 and 1 are reversed from the corresponding
staging indicator for the primary-to-secondary normal flow.
bit I, reserved
bits 2-7, secondary send window size, in binary, for session-level pacing
bit 0, adaptive session-level pacing support (reserved for nonextended
BIND, i.e., when control vector X'60' is not present):
o adaptive pacing not supported by the sending node: pacing
window values in bits 2-7 of bytes 8, 9, 12, and 13 specify the
fixed value implied in each pacing response; a zero value
specifies no pacing
1 adaptive pacing supported by the sending node:
pacing window
values in bits 2-7 of bytes 8, 9, 12, and 13 specify the
preferred minimum value for each ISOLATED PACING MESSAGE; a zero
value specifies that the preferred minimum value is as large as
possible; each adaptive pacing partner initializes its own send
window size to 1 at session activation
Note:
Adaptive pacing is supported only in conjunction with
one-stage session-level pacing.
If the PLU specifies adaptive
pacing in BIND, and the SLU is able to support adaptive pacing,
the SLU responds with this bit set to 1 in RSP(BIND).
If the
PLU indicates it does not support adaptive pacing, or if the SLU
does not support adaptive pacing, this bit will be set to 0 in
RSP(BIND).
See "Chapter 4. Request/Response Headers" for
further discussion of adaptive pacing.
bit I, reserved
bits 2-7, secondary receive window size, in binary, for session-level
pacing

Chapter 5.1.

Request Units

5.1-9

BIND
10

11
12

13

14

15
16-22

23

5.1-10

Maximum RU size sent on the normal flow by the secondary half-session:
if
bit 0 is set to 0, no maximum is specified and the remaining bits 1-7 are
ignored; if bit 0 is set to 1, and the byte 1S interpreted as X'ab' =
a.2**b (Notice that, by definition, a~8 and therefore X'ab' is a
normalized floating point representation.) See Figure 5.1-1 on page
5.1-14 for all possible values.
Maximum RU size sent on the normal flow by the primary half-session:
identical encoding as described for byte 10
bit 0, staging indicator for session-level pacing of the
primary-to-secondary normal flow:
0 the primary send window size (byte 12, bits 2-7) and the
secondary receive window size (byte 9, bits 2-7 ) are for
two-stage pacing
1 the primary send window size (byte 12, bits 2-7) and the
secondary receive window size (byte 9, bits 2-7) are for
one-stage pacing (The primary send window size is always equal
to the secondary receive window size.)
Note:
The meanings of 0 and 1 are reversed from the corresponding
staging indicator for the secondary-to-primary normal flow (byte
8, bit 0).
bit 1, reserved
bits 2-7, primary send window size, in binary, for session-level pacing
bits 0-1, reserved
bits 2-7, primary receive window size, in binary, for session-level pacing
PS Profile
bit 0, PS Usage field format:
a basic format (only value defined)
bits 1-7, lU type:
0000000 lU type 0
0000001 lU type 1
0000010 lU type 2
0000011 lU type 3
0000100 lU type 4
0000110 lU type 6
0000111 lU type 7
PS Usage field
Note:
The following format for bytes 15-25 applies only to lU 6.2; for
information on PS usage bytes 15-25 for other than lU 6.2 (indicated by
byte 14, bits 1-7 = 0000110 and byte 15 = 00000010), see SNA--Sessions
Between logical Units.
lU-6 level:
X'02' level 2 (i.e., lU 6.2)
Reserved
bits 0-2, retired
bit 3, conversation-level security support:
o Access Security Information field will not be accepted on
incoming FMH-5s
1 Access Security Information field will be accepted on incoming
FMH-5s
bits 4-5, reserved
bit 6, already-verified function support:
o Already Verified indicator will not be accepted on incoming
FMH-5s
1 Already Verified indicator will be accepted on incoming FMH-5s

SNA Formats

BIND

24

25
26-k
26

27

bit 7, reserved
bit 0, reserved
bits 1-2, synchronization level:
01 confirm is supported
10 confirm, sync point, and backout are supported
bit 3, reserved
bits 4-5, responsibility for session reinitiation (reserved unless bit 6
of this byte is set to 0):
00 operator controlled
01 primary half-session will reinitiate
10 secondary half-session will reinitiate
11 either may reinitiate
bit 6, parallel session support for LU-LU pair:
o not supported
1 supported
bit 7, Change Number of Sessions GDS variable flow support (set to 1 if
byte 24, bit 6 = 1):
o not supported
1 supported
Reserved
End of PS Usage Field
Cryptography Options
bits 0-1, private cryptography options (reserved for LU 6.2):
00 no private cryptography supported
01 private cryptography supported:
the session cryptography key
and cryptography protocols are privately supplied by the end
user
bits 2-3, session-level cryptography options:
00 no session-level cryptography supported
01 session-level selective cryptography supported; all
cryptography key management is supported by the SSCP and LU;
exchange (via +RSP(BIND)) and verification (via CRV) of the
cryptography session-seed value is supported by the LUs for
the session; all FMD requests carrying ED are
enciphered/deciphered by the rcs
10 reserved
11 session-level mandatory cryptography supported; all
cryptography key management is supported by the SSCP and LU;
exchange (via +RSP(BIND)) and verification (via CRV) of the
cryptography session-seed value is supported by the LUs for
the session; all FMD requests are enciphered/deciphered by rc
Only values 00 and 11 are defined for LU 6.2.
Note:
bits 4-7, session-level cryptography options field length:
X'O' no session-level cryptography specified; following
additional cryptography options fields (bytes 27-k) omitted
X'9' session-level cryptography specified; additional options
follow in next nine bytes
bits 0-1, session cryptography key encipherment method:
00 session cryptography key enciphered under SLU master
cryptography key using a seed value of 0 (only value defined)
bits 2-4, reserved
bits 5-7, cryptography cipher method:

Chapter 5.1.

Request Units

5.1-11

BIND

28-k

k+1-m
k+1
k+2-m

m+1-n
m+1

m+2-n
m+2

m+3-n
m+3-n
n+1-p
n+1
n+2-p
p+1-r
p+1
p+2-r

r+1-s

000 block chaining with seed and cipher text feedback, using the
Data Encryption Standard (DES) algorithm (only value
defined)
Session cryptography key enciphered under secondary LU master cryptography
key; an eight-byte value that, when deciphered, yields the session
cryptography key used for enciphering and deciphering FMD requests
Primary LU Name Field (always present)
Length of primary LU name (values 1 to 17 are valid)
Note:
Value 0 is retired.
Primary LU name or, if the secondary LU issued the INIT-SELF (or
INIT-OTHER), INIT-SELF, the uninterpreted name as carried in that RU (and
also in CDINIT for a cross-domain session)
User Data Field
Length of user data
Note:
X'OO' = no User Data field present; if unstructured user data
present, values 1 to 65 are valid.
User data
User data key:
X'OO' structured subfields follow (only value defined for LU 6.2)
Note:
Individual structured subfields may be omitted entirely.
When present, they appear in ascending subfield-number order.
~XIOOI first byte of unstructured user data
• For unstructured user data:
Remainder of unstructured user data
• For structured user data:
Structured subfields (For detailed definitions, see "Chapter 7.
User Data
Structured Subfields" in Chapter 7.)
User Request Correlation Field (present only if carried in INIT from SLU,
or if Secondary LU name field or control vectors are included)
Length of user request correlation (URC) field (values 0 to 12 are valid)
Note:
X'OO' = no URC present.
URC:
LU-defined identifier (present only if carried in INIT from SLU)
Secondary LU Name Field (present only for negotiable BINDs and for
non-negotiable BINDs that include control vectors)
Length of secondary LU name (values 1 to 17 are valid)
Note:
Value 0 is retired.
Secondary LU name
• Bytes r+l-s are included only if byte 7, bit 6 specified that control
vectors are included after the SLU name.
Control vectors, as described in "Control Vectors" in Chapter 8
Note:
The following control vectors may be included; they are parsed
according to subfield parsing rule KL:
X'OE' Network Name control vector:
PLU network name, X'F3' (present 1n
extended BINDs when bytes k+2-m contain an uninterpreted name)
X'2C' COS/TPF control vector (conditionally present)
X'2D' Mode control vector (conditionally present, used in non-LU6.2
extended BIND)
X'60' Fully-qualified PCID control vector (when present, the BIND is
called an extended BIND)
Note:
The receiving LU simply ignores unrecognized control vectors.

Note ~ The length of the BIND RU cannot exceed 256 or 512 bytes. The length of
the basic BIND RU is restricted to 256 bytes including the X'OE', X'2C', X'2D', and

5.1-12

SNA Formats

BIND
X'60' control vectors; any additional control vectors may cause the length to
increase up to 512 bytes.
Note ~ If the last byte of a format 0 request not having control vectors is a
length field and that field is 0, that byte may be omitted from the BIND request.

Chapter 5.1.

Request Units

5.1-13

I

I
Mantissa (a)

Exponent
(b)

1

I
I
I
I

8

9

A
(10)

B
(11)

C
(12)

D
(13)

E
(14)

F
(15)1
1

0

8

9

10

11

12

13

14

1

16

18

20

22

24

26

28

2

32

36

40

44

48

52

56

3

64

72

80

88

96

104

112

15 1
1
30 1
1
60 I
1
120 1

4

128

144

160

176

192

208

224

5

256

288

320

352

384

416

448

6

512

576

640

704

768

832

896

7

1024

1152

1280

1408

1536

1664

1792

960 1
1
1920 1

8

2048

2304

2560

2816

3072

3328

3584

3840 1

9

4096

4608

5120

5632

6144

6656

7168

7680 1

A (10)

8192

9216

10240

11264

12288

13312

14336

15360 1

B (11)

16384

18432

20480

22528

24576

26624

28672

30720 1

C (12)

32768

36864

40960

45056

49152

53248

57344

61440 1

D (13)

65536

73728

81920

90112

98304 106496 114688 122880 1

I

I
240 1
1
480 I

I

I
I
I
I
I
I
E (14)

131072 147456 163840 180224 196608 212992 229376 245760

F (15)

262144 294912 327680 360448 393216 425984 458752 491520

Note:

A value of X'ab' in byte 10 or byte 11 of BIND represents a-2**b.
example, X'C5' represents (in decimal) 12-2**5 = 384.

Figure 5.1-1.

5.1-14

I
I
I
I

RU Sizes Corresponding to Values X'ab' in BIND

SNA Formats

For

BIS

BIS; lU-->lU, Norm; DFC (BRACKET INITIATION STOPPED)
BIS is sent by ,a half-session to indicate that it will not
attempt to begin any more brackets.

o

X'70' request code

CANCEL; lU-->lU, Norm; DFC (CANCEL)
CANCEL may be'sent by a half-session to terminate a
partially sent chain of FMD requests.
CANCEL may be sent
only when a chain is in process. The sending half-session
may send CANCEL to end a partially sent chain if a
negative response is received for a request in the chain,
or for some other reason.
This RU is not used for lU 6.2.

o

X'83' request code

CHASE; lU-->lU, Norm; DFC (CHASE)
CHASE is sent by a half-session to request the receiving
half-session
to return
all outstanding
normal-flow
responses to requests previously received from the issuer
of CHASE.The receiver of CHASE sends the response to
CHASE after
processing (and
sending any
necessary
responses to) all requests received before the CHASE.
This RU is not used for lU 6.2.

o

X'84' request code

CLEAR; PLU-->SLU, Exp; SC (CLEAR)
CLEAR is sent by primary session control to reset the data
traffic FSMs and subtrees (for example, brackets, pacing,
sequence
numbers)
in
the
primary
and
secondary
half-sessions (and boundary function, if any). This RU is
not used for LU 6.2.

o

X'AI' request code

CRY; PlU-->SLU, Exp; SC (CRYPTOGRAPHY VERIFICATION)
CRV, a valid request only when session-level cryptography
was selected in BIND, is sent by the primary LU session
control to verify cryptography security and thereby enable
sending
and
receiving
of FMD
requests
by
both
half-sessions.

o
1-8

X'CO' request code
A transform of the (deciphered) cryptography session-seed value received
(enciphered) in bytes 28-k of +RSP(BIND), re-enciphered under the session
cryptography key using a seed value of 0; the transform is the
cryptography session-seed value with the first four bytes inverted

Chapter 5.1.

Request Units

5.1-15

CRV
Note:
The cryptography session-seed is used as the seed for all
session-level cryptography encipherment and decipherment provided for FMD
RUs.

DACTLU; SSCP-->LU, Exp; SC (DEACTIVATE LOGICAL UNIT)
DACTLU is sent to deactivate
and the LU.

o
Note:
I

2

the session between the SSCP

X'OE' request code
End of short (one-byte) request
Type of deactivation requested:
X'OI' normal deactivation
X'03' session outage notification (SON)
Cause (reserved if byte I t X'03'):
X'07' virtual route inoperative: the virtual route serving the SSCP-LU
session has become inoperative, thus forcing the deactivation of the
session
X'OB' route extension inoperative:
the route extension serving the
SSCP-LU session has become inoperative, thus forcing the
deactivation of the session
X'09' hierarchical reset:
the identified session is being deactivated
because of a +RSP(ACTPU, Cold)
X'OB' virtual route deactivated:
the SSCP-LU session is being deactivated
because of a forced deactivation of the virtual route being used by
the session
X'OC' SSCP or LU failure--unrecoverable:
the SSCP-LU session had to be
reset because of an abnormal termination; recovery from the failure
was not possible
X'OD' session override:
the SSCP-LU session has to be deactivated because
of a more recent session activation request for the SSCP to subarea
PU session over a different virtual route
X'OE' SSCP or LU failure--recoverable:
the SSCP-LU session had to be
deactivated because of an abnormal termination of the SSCP or LU of
the session; recovery from the failure may be possible
X'OF' cleanup:
the SSCP is resetting its half-session before receiving
the response from the LU being deactivated

DACTPU; SSCP-->PU, PU-->SSCP, Exp; SC (DEACTIVATE PHYSICAL UNIT)
DACTPU is sent to deactivate
and the PU.

o
I

2

5.1-16

the session between the SSCP

X'l2' request code
Type deactivation requested:
X'OI' final use, physical connection may be broken
X'02' not final use, physical connection should not be broken
X'03' session outage notification (SON)
Cause (not present if byte 1 t X'03'):
X'07' virtual route inoperative:
the virtual route for the SSCP-PU
session has become inoperative, thus forcing the deactivation of the
SSCP-PU session

SNA Formats

DACTPU
X'08' route extension inoperative:
the route extension serving the
SSCP-PU session has become inoperative, thus forcing the
deactivation of the SSCP-PU session
X'09' hierarchical reset:
the identified session is being deactivated
because of a +RSP(ACTPU, Cold)
X'OB' virtual route deactivated:
the identified SSCP-PU session is being
deactivated because of a forced deactivation of the virtual route
being used by the session
X'OC' SSCP or PU failure--unrecoverable:
the identified SSCP-PU session
had to be deactivated because of an abnormal termination of the SSCP
or PU of the session; recovery from the failure was not possible
X'OD' session override:
the SSCP-PU session has to be deactivated because
of a more recent session activation request for the SSCP to subarea
PU session over a different virtual route
X'OE' SSCP or PU failure--recoverable:
the identified SSCP-PU session had
to be deactivated because of an abnormal termination of the SSCP or
PU of the session; recovery from the failure may be possible
X'OF' cleanup: the SSCP is resetting its half-session before receiving
the response from the PU that is being deactivated
X'IO' ALS reset:
peripheral ALSs (and subordinate LUs and LU-LU sessions)
owned by the sending SSCP should be reset
X'll' give-back:
the sending SSCP relinquishes ownership of resources;
active LU-LU sessions should not be disrupted for LUs subordinate to
ALSs whose nodes support ACTPU(ERP)

INIT-SELF Format 0; ILU-->SSCP, Norm; FMD NS(s) (INITIATE-SELF)
INIT-SELF from the ILU requests that the SSCP authorize
and assist in the initiation of a session between the LU
sending the request (that is,
the ILU, which also becomes
the OLU) and the LU named in the request (the DLU).
This
RU is not used for LU 6.2; refer to INIT-SELF Format 1.
0-2
3

4-11

12-m
12
13

X'Ol0681' NS header
bits 0-3, format:
0000 Format 0: specifies a subset of the parameters shown in
Format 1 of INIT-SELF (described separately, because the NS
header differs in the first byte), with the receiver
supplying default values
bit 4, reserved
bit 5, reserved
bit 6, PLU/SLU specification:
o DLU is PLU
1 DLU is SLU
bit 7, 0 initiate only (I):
do not enqueue.
1 initiate/enqueue (I/Q):
enqueue the request if it cannot be
satisfied immediately
Mode name: an eight-character symbolic name (implementation and
installation dependent) that identifies the set of rules and protocols to
be used for the session; used by the SSCP(SLU) to select the BIND image
that will be used by the SSCP(PLU) to build the CINIT request
Uninterpreted Name of DLU
Type:
X'F3' logical unit
Length, in binary, of DlU name

Chapter 5.1.

Request Units

5.1-17

INIT-SELF Format 0
14-m
m+l-m+2
m+3-n
m+3
m+4-n
m+4

m+5-n
m+5-n

EBCDIC character string
Retired
User Field
-------Length, in binary, of user data
Note:
X'OO' = no user data is present.
User data:
user-specific data that is passed to the primary LU on the
CINIT request
User data key:
X'OO' structured subfields follow
~X'OO' first byte of unstructured user data
Note:
Individual structured subfields may be omitted entirely.
When present, they appear in ascending field number order.
• For unstructured user data
Remainder of unstructured user data
• For structured user data
Structured subfields (For detailed definitions, see "Chapter 7.
User Data
Structured Subfields" in Chapter 7.)

Note:
The following default values are supplied by the SSCP(ILU) receiving the
Format 0 INIT-SELF request:
•

Queuing conditions (if queuing is specified):
Enqueue if session limit exceeded.
Enqueue this request FIFO, i.e., the request will be dequeued after the
other requests already in the queue.

INIT-SELF Format 1; ILU-->SSCP, Norm; FMD NS(s) (INITIATE-SELF)
INIT-SELF from the ILU requests that the SSCP authorize
and assist in the initiation of a session between the LU
sending the request (that is,
the ILU, which also becomes
the OLU) and the LU named in the request (the DLU).
0-2
3

5

X'810681' NS header
bits 0-3, format:
0001 Format 1: specifies queuing, initiate or1g1n, and URC in
addition to the parameters in Format 0
bits 4-7, reserved
Type:
bits 0-1, 00 retired
01 initiate only (I):
do not enqueue
10 retired
11 initiate/enqueue (I/Q):
enqueue the request if it cannot be
satisfied immediately (See byte 5 for further specification
of queuing conditions.)
bits 2-3, retired
bit 4, reserved
bit 5, reserved
bit 6, PLU/SLU specification:
o DLU is PLU
1 DLU is SLU
bit 7, reserved
Queuing conditions for DLU:

5.1-18

SNA Formats

4

INIT-SELF Format 1
bit

01

0 do not enqueue if session limit exceeded
1 enqueue if session limit exceeded
bit 11 0 do not enqueue if DLU is not currently able to comply with the
PLU/SLU specification (as given in byte 41 bits 5-6)
1 enqueue if DLU is not currently able to comply with the PLU/SLU
specification
bit 21 reserved
bit 3 1 reserved
bit 41 reserved
bits 5-6, queuing position/service:
00 retired
01 enqueue this request FIFO, i.e., the request will be dequeued
after the requests already in the queue (only value defined
for LU 6.2)
10 enqueue this request LIFO, i.e., the request will be dequeued
before the requests already in the queue.
11 reserved
bit 7, reserved
Note:
Since queuing conditions are specified for the DLU only, the
following default values are used by SSCP(OLU) for the OLU:
• Enqueue if session limit exceeded.
• Enqueue this request at the foot of the queue (FIFO).
6
Reserved for LU 6.2; otherwise:
bits 0-2, reserved
bit 3, retired
bits 4-7, reserved
7
Reserved for LU 6.2; otherwise:
bits 0-1, retired
bits 2-7, reserved
8-15
Mode name: an eight-character symbolic name (implementation and
installation dependent) that identifies the set of rules and protocols to
be used for the session; used by the SSCP(SLU) to select the BIND image
that will be used by the SSCP(PLU) to build the CINIT request
16-n
Uninterpreted Name of DLU
16
Type:
X'F3' logical unit
17
Length, in binary, of DLU name
18-n
DLU name EBCDIC character string
n+l-n+2
Retired
n+3-r
User Field (reserved for LU 6.2)
-------n+3
Length, in binary, of user data
Note:
X'OO'
no user data is present.
n+4-r
User data:
user-specific data that is passed to the primary LU on the
CINIT request
n+4
User data key:
X'OO' structured subfields follow
~X'OO' first byte of unstructured user data
Note:
Individual structured subfields may be omitted entirely.
When present, they appear in ascending field number order.
• For unstructured user data
n+5-r
Remainder of unstructured user data
• For structured user data
n+5-r
structured subfields (For detailed definitions, see "Chapter 7.
User Data
Structured Subfields" in Chapter 7.)
r+l-s
User Request Correlation (URC) Field

=

Chapter 5.1.

Request Units

5.1-19

INIT-SElF Format 1
r+1
r+2-s

length, in binary, of URC
Note:
X'OO' = no URC.
(The length field is always present.)
URC:
lU-defined identifier; may be returned by the SSCP in a subsequent
NOTIFY to correlate a given session to this initiating request

LUSTATj lU-->lUISSCP, Norm; DFC (lOGICAL UNIT STATUS)

lUSTAT is used by one half-session to send up to four
bytes of status information to its paired half-session.
The RU format allows the sending of either end-user
information or lU status information.
If the high~order
two bytes of the status information are 0, the low-order
two bytes carry end-user information and may be set to any
value.
In general,
lUSTAT is used to report about
failures and error recovery conditions for a local device
of an lU.

o
1-4

5.1-20

X'04' request code
Status value + status extension field (two bytes each):
X'OOOO'+'uuuu' user status (no system-defined status) + user-defined field
X'OOOl'+'ccdd' component now available + component identification (see
Note)
X'0002'+'rrrr' sender will have no (more) FMD requests to transmit during
the time that this session remains active + reserved field
X'0003'+'ccdd' component entering attended mode of operation + component
identification (see Note)
X'0004'+'ccdd' component entering unattended mode of operation + component
identification (see Note)
X'0005'+'iiii' prepare to commit all resources required for the unit of
work + information field:
X'OOOl' request End Bracket be sent on next chain (only
value defined)
X'0006'+'rrrr' no-op (used to allow an RH to be sent when no other request
is available or allowed) + reserved field (only value
defined for lU 6.2)
X'0007'+'rrrr' sender currently has no FMD requests to transmit (but may
have later during the time that this session remains
active) + reserved field
X'0801'+'ccdd' component not available (e.g., not configured) + component
identification (see Note)
X'0802'+'ccdd' component failure (intervention required) + component
identification (see Note)
X'081C'+'ccdd' component failure (permanent error) + component
identification (see Note)
X'0824'+'rrrr' function canceled + reserved field
X'082B'+'ccdd' component available, but presentation space integrity lost
+ component identification (see Note)
X'0831'+'ccdd' component disconnected (power off or some other
disconnecting condition) + component identification (see
Note)
X'0848'+'rrrr' cryptography component failure + reserved field
X'400A'+'ssss' no-response mode not allowed + sequence number of the
request specifying no-response
Note:
Values for cc byte are:

SNA Formats

LUSTAT
X'OO'
X'FF'

~X'(OOIFF)'

LU itself rather than a specific LU component (For this cc
value, dd=X'OO'.)
The dd byte specifies the LU component medium class and device
address.
(See SNA--Sessions Between Logical Units for
definitions of these terms and usage of the values according to
LU type.)
LU component medium class and device address (For these cc
values, dd=X'OO'.)

NMVTi SSCP<-->PU Norm;

FMD NS(ma) (NETWORK MANAGEMENT VECTOR TRANSPORT)

NMVT carries management services (MS) requests and replies
between an SSCP and a PU.
0-2
3-4

5-6

7

X'41038D' NS header
Retired: set to network address by subarea node sender; set to 0, the PU
local address, by peripheral node sender; ignored by receivers
implementing the current level of SNA
bits 0-1, reserved
bits 2-3, retired: set to 01 by subarea PU sender; set to 00 by
peripheral node sender; ignored by receivers implementing the
current level of SNA
bits 4-15, procedure related identifier (PRID)
Note:
For unsolicited replies (byte 7, bit 0 = 0), the PRID
field contains X'OOO'.
For solicited replies (byte 7, bit 0 =
1), the PRID field echoes the PRID from the NMVT RU request.
For requests that need no replies, this field contains X'OOO'.
Flags:
bit 0, solicitation indicator: used only for PU-to-SSCP flow (reserved
for SSCP-to-PU flow):
o unsolicited NMVT
1 solicited NMVT
bits 1-2, sequence field--used only for PU-to-SSCP flow (reserved for
SSCP-to-PU flow):
00 only NMVT for this PRID
01 last NMVT for this PRID
10 first NMVT for this PRID
11 middle NMVT for this PRID
bit 3, SNA Address List subvector indicator:
o For the SSCP-to-PU flow: MS major vector in this NMVT does not
contain an SNA Address List subvector
For the PU-to-SSCP flow:
MS major vector in
contain an SNA Address List subvector, or it
Address List subvector that does not require
translation by the SSCP
1 For the SSCP-to-PU flow:
MS major vector in
an SNA Address List subvector

this NMVT does not
contains an SNA
address-to-name
this NMVT contains

For the PU-to-SSCP flow:
MS major vector in this NMVT contains
an SNA Address List subvector that requires address-to-name
translation by the SSCP
bits 4-7, reserved

Chapter 5.1.

Request Units

5.1-21

NMVT
8-m

One MS major vector, as described (using zero-origin indexing) in the
table in "MS Major Vectors and Unique Subvectors" in Chapter 8.

NOTIFY; SSCP<-->LU,

Norm; FMD NS(s) (NOTIFY)

NOTIFY is used to send information from an SSCP to another
SSCP or to an LU,
or from an LU to an SSCP.
NOTIFY
carries information in the form of a
(vector key, vector
data) pair.
0-2
0-2
3-p

X'810620' NS header (for SSCP-->LU and LU-->SSCP)
X'818620' NS header (for SSCP-->SSCP)
One NOTIFY vector as described in detail below
Note:
One of the following NOTIFY vectors is included.
X'Ol' retired
X'OC' LU-LU Session Services Capabilities:
used to inform the SSCP having
an active session with the sending LU of the current LU-LU session
services capability of that LU

NOTIFY vectors (described zero-origin)
LU-LU Session Services Capabilities NOTIFY Vector
Note:
This NOTIFY vector should not be confused with control vector X'OC', which
carries similar information.

o
1
2-m

2

3-4
5-7
8-15(=m)

Key:
X'OC'
Length of Vector Data field, encoded in binary
Vector Data
LU-LU session capability:
bits 0-3, (reserved)
bits 4-7, secondary LU capability:
0000 SLU capability is inhibited: sessions can neither be
queued nor started
0001 SLU capability is disabled: sessions can be queued but not
started
0010 reserved
0011 SLU capability is enabled: sessions can be queued or
started
Retired (set to X'OOOl')
Retired
Retired (set to X'4040404040404040' or omitted)

QC; LU-->LU, Norm; DFC (QUIESCE COMPLETE)
QC is sent by a half-session after receiving QEC, to
indicate that it has quiesced. This RU is not used for LU
6.2

o

X'8l' request code

5.1-22

SNA Formats

QEC

QEC; LU-->LU, Exp; DFC (QUIESCE AT END OF CHAIN)
QEC is sent by a half-session to quiesce its partner
half-session after it (the partner) finishes sending the
current chain (if any). This RU is not used for LU 6.2.

o

X'80' request code

RECFMS; PU-->SSCp, Norm; FMD NS(ma) (RECORD FORMATTED MAINTENANCE STATISTICS)
Retired
RECFMS permits
the passing
of maintenance
related
information from a PU to management services at the SSCP.
0-2
3-4
5-6

7

X'410384' NS header
CNM target ID, as specified in bytes 5-6, bits 2-3
bits 0-1, reserved
bits 2-3, CNM target ID descriptor:
00 byte 4 contains a local address for a PU or LU in a PU_T2
node or an LSID for a PU or LU in a PU_T1 node; byte 3 is
reserved
01 bytes 3-4 contain the element address of a link, adjacent
link station, PU, or LU in the origin subarea, if ENA is
supported; otherwise, its network address
bits 4-15, procedure related identifier (PRID) (see Note below)
Request-Specific Information
bit 0, solicitation indicator:
o unsolicited request
1 reply request
bit I, not last request indicator:
o last request in a series of related unsolicited or reply
requests, e.g., last reply request in a series corresponding to
a single soliciting request
1 not last request
bits 2-7, request-specific type code (see below)

Note:
For reply (i.e., solicited) requests, bytes 3-6 and byte 7, bits 2-7, echo
the corresponding fields in the CNM header received in the request that solicited
the reply requests.
For unsolicited requests, these fields--the CNM target ID descriptor, the CNM target
ID, the PRID, and the request-specific information--are generated by the request
sender.
For unsolicited requests, the PRID field contains X'OOO'.
The PU does not
interleave requests belonging to different series of related unsolicited requests
from the same target.
8-13
8-11

Node Identification
bits 0-11, block number: an IBM product specific number; see the
individual product specifications for the specific values used
bits 12-31, ID number: a binary value that, together with the block
number, identifies a specific station uniquely within a
customer network installation; the ID number can be assigned
in various ways, depending on the product; see the individual
product specifications for details

Chapter 5.1.

Request Units

5.1-23

RECFMS
12-13

Reserved

7-n

Alert (retired: supported only for PUs not at the current level of SNA)
bits 0-1, 00 (only value defined--Alert is always sent unsolicited and as
a single RU)
bits 2-7, type code:
000000
Node Identification
bits 0-11, block number
bits 12-31, 10 number
Reserved
Alert Classification
bits 0-1, format:
01 format 1 (only value defined)
bits 2-7, reserved
bits 0-3, Alert type:
indicates the reason for the Alert being generated
and differentiates between errors, operational problems,
performance problems, and other exceptional conditions; valid
Alert types are:
X'l' permanent error: cannot be retried or recovered without
help external to the SNA node
X'2' temporary error:
recovered within recovery procedure limit
X'3' performance:
exceeded performance parameter threshold
X'4' operational or procedure:
unsupported or invalid use, busy
X'S' application generated
X'6' operator triggered
X'7' SNA summary:
exceeded threshold count of SNA negative
responses
b~ts 4-7, major probable cause:
indicates the general category of the
probable cause, e.g., hardware, software, or protocol failure;
valid major probable cause (details of these causes are given in
specific implementation documentation):
X'l' hardware
X'2' software
X'3' link connection:
characterized by transmission medium,
modem, DIE-DCE cable, drivers,
X'4' protocol:
invalid response or command sequence, system
definition error
X'S' environment: thermal, installation restriction
X'6' removable media, e.g., paper, cards, tape, pack, diskette
X'7' hardware or software
X'8' logical
X'9' operator of sending product
X'F' undetermined
Minor probable cause:
indicates the lowest level category with which the
Alert may be associated, e.g., printer, power, program, X.2S network;
valid minor probable cause (details of these causes are given in specific
implementation documentation):
X'OI' base processor
X'02' service processor for support of maintenance services
X'03' microcode
X'04' main storage
X'OS' DASD drive
X'06' printer
X'07' card reader/punch

7

8-13
8-11
12-13
14-19
14
14
15

16

5.1-24

SNA Formats

RECFMS
X'08'
X'09'
X'OA'
X'OB'
X'OC'
X'OD'
X'OE'
X'OF'
X'IO'
X'll'
X'12'
X'13'
X'14'
X'IS'
X'l6'
X'17'
X'l8'
X'l9'
X'IA'
X'lB'
X'lC'
X'ID'
X'IE'
X'lF'
X'20'
X'21'
X'22'
X'23'
X'24'
X'2S'
X'26'
X'27'
X'28'
X'29'
X'2A'
X'2B'
X'2C'
X'2D'
X'2E'
X'2F'
X'30'
X'31'
X'32'
X'33'
X'34'
X'3S'
X'36'
X'37'
X'38'
X'39'
X'3A'

tape drive
keyboard
selector pen
magnetic stripe reader
display or printer
display unit
remote product:
error attributed to product at adjacent
link station on this link
power internal to this product
I/O attached controller if distinguishable from drive
communications controller scanner
communications link adapter
link adapter
channel adapter: secondary attachment to System/370
channel
loop adapter: attachment to loop communication link
adapter for directly attaching devices
miscellaneous adapter
System/370 channel
link:
transmission medium--ownership unknown
link: common carrier transmission medium
link:
customer transmission medium
loop:
transmission medium--ownership unknown
loop: common carrier transmission medium
loop:
customer transmission medium
X.21 link connection external to this product
X.2S network external to this product
local X.21 interface: DTE-DCE
local X.2S interface: DTE-DCE
local modem
remote modem
local modem interface: DTE-DCE
remote modem interface:
DTE-DCE
local probe
remote probe
local probe interface
remote probe interface
network connection
IBM host program if not distinguishable as control
program, application, or access method
IBM host application program supplied by IBM
IBM host telecommunication access method
customer host application program
IBM communication controller program
IBM control program
remote modem interface or remote product
transmission medium or remote modem
SDLC format exception
BSC format exception
start/stop format exception
SNA format exception
power external to product
thermal
paper

Chapter S.l.

Request Units

S.1-2S

RECFMS
X'3B'
X'3C'
X'3D'
X'3E'
X'3F'
X'40'
X'41'
X'42'
X'43'
X'44'
X'45'
X'46'
X'47'
X'48'
X'49'
X'4A'
X'4B'
X'4C'
X'4D'
X'4E'
X'4F'
X'50'
X'51'
X'FF'
17
18

19
20-m

m+l(=n)
7-17

7

8-13

12-13
14-15
16-17

5.1-26

tape
DASD:
removable media
card
magnetic stripe card
negative SNA response
system definition error (whether diskette loaded, keyed,
or otherwise customized)
installation restrictions
adjacent link station offline: no status received
adjacent link station busy (switched link)
controller or device
local probe or modem
tape or drive
card reader/punch or display/printer
controller application program
keyboard or display
storage control unit
channel or storage control unit
storage control unit or controller
control unit
DASD data or media or drive
DASD data or media
diskette
diskette or drive
undetermined

Reserved
User action code:
o reserved
~O a code associated with predefined text that describes user actions
appropriate to the cause
Reserved
Appended CNM vector(s) (described at the end of this RU):
zero or more
CNM vectors may be appended to the request to convey data available to the
PUMS when the Alert event was originated; appended vectors are ordered
according to the binary value of the Vector Type field (nondescending)
Note:
The sending of information in appended CNM vectors does not cause
reset of any counters.
X'OO' indicating end of appended vectors
SDLC Test Command/Response Statistics
bit 0, solicitation indicator (see above)
bit 1, not last request indicator (see above)
bits 2-7, type code:
000001; the CNM target ID identifies a PU_TlI2
Node identification
bits 0-11, block number
bits 12-31, ID number
Reserved
Counter:
the number of times the secondary SDLC station has received an
SDLC Test command with or without a valid FCS
Counter:
the number of times the secondary SDLC station has received an
SDLC Test command with a valid FCS and has transmitted an SDLC Test
response
Note:
All counters are in binary.

SNA Formats

RECFMS
7-22

7

8-13

12-13
14-16
14

IS
16

17-18

19-20

21-22

7-n

7

8-13

12-13
14

Summary ~ data
bit 0, solicitation indicator (see above)
bit 1, not last request indicator (see above)
bits 2-7, type code:
000010; the CNM target ID identifies a PU
Node identification
bits 0-11, block number
bits 12-31, ID number
Reserved
Summary counter validity mask:
bit 0, set to 1 if product error counter is valid
bit 1, set to 1 if communication adapter error counter is valid
bit 2, set to 1 if SNA negative response counter is valid
bits 3-7, reserved
Reserved
bits 0-6, reserved
bit 7, communications adapter error flag for products implementing
unsolicited RECFMS types 02 or 03; otherwise reserved
o no cumulative communications adapter errors
1 indicates presence of communications adapter errors not yet
reported by RECFMS 03
Product error counter: a count for the product identified by the Node
Identification field (bytes 8-13) of certain product-detected hardware
errors whose origins are failures designated as internal by that product's
own logic capability (The identified product has the responsibility for
further isolation of these failures using its own product-specific problem
determination and maintenance procedures.)
Communication adapter error counter for communication adapter errors whose
source is either external or internal to the product identified by the
node ID; this field is reserved in products reporting counter overflows
via unsolicited RECFMS type 02 or 03
Count of SNA negative responses originating at this node
Note:
All counters are in binary.
Communication Adapter Error Statistics: counts of selected errors, useful
for problem determination, that have been supplied by the communication
adapter (For these errors, the RECFMS Type 000010 communication adapter
error counter is always incremented; the RECFMS Type 000010 product error
counter is also incremented for those errors classified as internal errors
by the product identified by the node ID.)
bit 0, solicitation indicator (see above)
bit 1, not last request indicator (see above)
bits 2-7, type code:
000011; the CNM target ID identifies a PU_TlI2
Node identification
bits 0-11, block number
bits 12-31, ID number
Reserved
Communication adapter error counter sets:
X'Ol' counter set 1
X'02' counter set 2
X'03' counter set 3
X'04' counter set 4
X'OS' counter set S (retired: supported only for PUs not at the current
level of SNA)

Chapter 5.1.

Request Units

5.1-27

RECFMS

15-n

X'06' counter set 6 (Retired: supported only for PUs not at the current
level of SNA)
Data for Counter Sets 1 and 2
--------- - --- Communication adapter counter validity mask bytes
Mask byte 1 (bit is set to 1 if the counter is valid):
bit 0, nonproductive time-out or receive overrun counter
bit 1, idle time-out counter
bit 2, write retry counter
bit 3, overrun counter
bit 4, underrun counter
bit 5, connection problem counter
bit 6, FCS error counter
bit 7, primary station abort counter
Mask byte 2 (bit is set to 1 if the counter is valid):
bit 0, command reject counter
bit 1, SDLC DCE error counter
bit 2, write time-out counter
bit 3, invalid status counter
bit 4, communication adapter machine check counter
bits 5-7, reserved
Reserved
Nonproductive time-out counter:
no valid SDLC frames have been received
within the time interval specified by the communication adapter; or
receive overrun counter:
the line is "hung" or insufficient buffer space
has been allocated
Note:
Receive overrun applies only to counter set 2.
Idle time-out counter:
no SDLC Flag octets received for ~ seconds, where
~ is specified by the communication adapter
Write retry counter:
the number of retransmissions of one or more SDLC
I-frames
the number of times one or more received characters have
Overrun counter:
been overlaid
Underrun counter:
the number of times one or more characters have been
transmitted more than once
Connection problem counter:
incremented by ! for every ~ retries of
commands that establish connection with a station, when RLSD drops, or
whenever write retry is updated--~ is specified by the communication
adapter
FCS error counter:
the number of times a received SDLC frame had an
invalid FCS
Primary station abort counter:
number of times seven or more consecutive
one bits have been received
SDLC command reject counter
DCE error counter:
number of DCE interrupts or other unexpected
conditions (e.g., "data set ready" drops)
Write time-out counter:
number of time-outs during write operations,
e.g., because of transmit clock failures
Invalid status counter:
number of times status generated by the adapter
was not meaningful
Communication adapter machine check counter:
number of times the
communication adapter has been identified as causing a machine check
Note:
All counters are in binary.
Data for Counter Set 3

5.1-28

SNA Formats

15-n
15-17
15

16

17
18

19
20
21
22
23

24
25
26
27
28

29
30(=n)

RECFMS
15-17

Communication adapter counter validity mask (bit is set to 1 if the
counter is valid):
bit 0, total transmitted I-frames counter
15
bit 1, write retry counter
bit 2, total received I-frames counter
bit 3, FCS error counter
bit 4, SDLC command reject counter
bit 5, DCE error counter
bit 6, nonproductive time-out counter
bit 7, reserved
16-17
Reserved
18-19
Total transmitted I-frames counter:
the total number of SDLC I-frames
transmitted successfully
20-21
Write retry counter:
the number of retransmissions of one or more SDLC
I-frames
22-23
Total received I-frames counter:
the number of SDLC I-frames successfully
received
FCS error counter: the number of SDLC frames received with FCS errors
24-25
26-27
SDLC command reject counter
28-29
DCE error counter:
the number of DCE interrupts and other unexpected
conditions (e.g., "data set ready" drops)
30-31(=n) Nonproductive time-out counter:
the number of times an SDLC frame has not
been received within the time interval specified by the adapter
Note:
All counters are in binary.
15-n
Data for Counter Set 4
Note:
For a definition of adapter, control unit, and System/370 channel
commands, and orders see implementation documentation.
15-17
Adapter counter validity mask bytes
Mask byte 1 (bit is set to 1 if the counter is valid):
15
bit 0, command-reject-whi1e-not-initialized counter
bit 1, command-not-recognized counter
bit 2, sense-while-not-initialized counter
bit 3, channel-parity-check-during-selection-sequence counter
bit 4, channel-parity-check-during-data-write-sequence counter
bit 5, output-parity-check-at-control-unit counter
bit 6, input~parity-check-at-control-unit counter
bit 7, input-parity-check-at-adapter counter
16
Mask byte 2 (bit is set to 1 if the counter is valid):
bit 0, data-error-at-adapter counter
bit 1, data-stop-sequence counter
bit 2, short-frame-or-length-check counter
bit 3, connect-received-when-already-connected counter
bit 4, disconnect-received-while-PU-active counter
bit 5, long-RU counter
bit 6, connect-parameter-error counter
bit 7, Read-Start-Old-received counter
Reserved
17
Command-reject-while-not-initialized counter: an initial Control command
18
containing a valid Connect order was not received prior to a Restart
Reset, Read Start 0/1, Write Start 0/1, Read, Write, or Write Break
command
Command-not-recognized counter:
control unit channel adapter received a
19
command code that it did not recognize (invalid or not supported)

Chapter 5.1.

Request Units

5.1-29

RECFMS
20

21

22

23
24

25

26

27
28

29

30

31

32

33(=n)

15-n

15-17
15

16

5.1-30

Sense-while-not-initialized counter: Sense command was received in
response to the initial asynchronous interrupt (device-end, unit check), or
Sense command was received without a preceding unit check ending status
Channel-parity-check-during-selection-sequence counter:
control unit
channel adapter detected a parity error from the channel during the
selection sequence from the channel
Channel-parity-check-during-data-write-sequence counter: control unit
channel adapter detected a parity error on channel bus-out during a
channel Write operation
Output-parity-check-at-control-unit counter: control unit channel adapter
detected a control unit parity error during a channel Write operation
Input-parity-check-at-control-unit counter: control unit detected a
control unit parity error during a channel Read operation
Input-parity-check-at-adapter counter:
control unit channel adapter
detected that it transmitted bad parity on channel bus-in during a channel
Read operation
Data-error-at-adapter counter:
control unit detected a channel adapter
error during an internal channel adapter cycle-steal operation
Data-stop-sequence counter:
the number of data bytes accepted by the
System/370's Read command was less than that specified in Connect
Short-frame-or-Iength-check counter: a minimum four bytes have not been
transferred as a link header; or the byte count specified in the first two
bytes of the header did not equal the number of bytes received during a
Control, Write, or Write Break operation
Connect-received-when-already-connected counter: a Connect was received
when the control unit was already connected; this is an error condition
and the PU is deactivated
Disconnect-received-while-PU-active counter: a Disconnect order was
received from the System/370 while the PU is active (i.e., with no DACTPU
preceding the Disconnect); this is an error condition
Long-RU counter:
primary link station has sent an RU greater than the
secondary link station can accept
Connect-parameter-error counter:
the Connect was rejected because it
specified an odd-number buffer length, or it specified a buffer size
insufficient to hold the link header, TH, RH, and at least a 64-byte RU
Read-Start-Old-received counter:
the secondary link station received a
Read Start Old command
Note:
All counters are in binary.
Data for Counter Set 2 (for X.25 physical circuit) (Retired: supported
only for PUs not at the current level of SNA)
Note:
Sent only from the primary end of an X.25 physical circuit.
Communication adapter counter validity mask
Mask byte I (bit is set to 1 if the counter is valid):
bit 0, number of I-frames transmitted counter
bit 1, number of I-frames received counter
bit 2, number of RR frames transmitted counter
bit 3, number of RR frames received counter
bit 4, number of RNR frames transmitted counter
bit 5, number of RNR frames received counter
bit 6, number of REJ frames transmitted counter
bit 7, number of REJ frames received counter
Mask byte 2 (bit is set to 1 if the counter is valid):
bit 0, number of retransmissions counter
bit 1, number of frames received with FCS errors counter

SNA Formats

RECFMS
2, number of errors on receive side counter
bi t
3,
bit
number of overruns on receive side counter
bit 4, number of underruns on transmit side counter_
bits 5-7, reserved
17
Reserved
18-19
Number of I-frames transmitted
20-21
Number of I-frames received
22-23
Number of RR frames transmitted
24-25
Number of RR frames received
26-27
Number of RNR frames transmitted
28-29
Number of RNR frames received
30-31
Number of REJ frames transmitted
32-33
Number of REJ frames received
34-35
Number of retransmissions
36-37
Number of frames received with FCS errors
38-39
Number of errors on receive side
40-41
Number of overruns on receive side
42-43(=n) Number of underruns on transmit side
Note:
All counters are in binary.
15-n
Data for Counter Set 6 (for X.25 virtual circuit) (retired: supported
only for PUs not at the current level of SNA)
Note:
Sent only from the primary end of an X.25 virtual circuit.
15-17
Communication adapter counter validity mask
Mask byte 1 (bit is set to 1 if the counter is valid):
15
bit 0, number of data packets transmitted counter
bit 1, number of data packets received counter
bit 2, number of RR packets transmitted counter
bit 3, number of RR packets received counter
bit 4, number of RNR packets transmitted counter
bit 5, number of RNR packets received counter
bit 6, number of interrupt packets transmitted counter
bit 7, number of interrupt packets received counter
16
Mask byte 2 (bit is set to 1 if the counter is valid):
bit 0, number of connection requests counter
bit 1, number of connections counter
bit 2, number of reset indications counter
bit 3, number of clear indications counter
bit 4, number of data packets with D bit transmitted counter
bit 5, number of data packets with D bit received counter
bits 6-7, reserved
17
Reserved
18-19
Number of I packets transmitted
20-21
Number of I packets received
22-23
Number of RR packets transmitted
24-25
Number of RR packets received
26-27
Number of RNR packets transmitted
28-29
Number of RNR packets received
30-31
Number of interrupt packets transmitted
32-33
Number of interrupt packets received
34-35
Total number of connection requests (call request and incoming calls)
36-37
Total number of connections (calls connected and accepted)
38-39
Number of reset indications
40-41
Number of clear indications
42-43
Number of data packets with D bit transmitted

Chapter 5.1.

Request Units

5.1-31

RECFMS
44-45(=n) Number of data packets with D bit received
Note:
All counters are in binary.
7-n

7

8-13

12-13
14-n
7-n

7

8-13

12-13
14-n

7-n

7

8-13

12-13
14

15

16-17

5.1-32

PU/LU Dependent Data
bit 0, solicitation indicator (see above),
bit 1, not last request indicator (see above)
bits 2-7, type code:
000100; the CNM target ID identifies a PUILU
Node identification
bits 0-11, block number
bits 12-31, ID number
Reserved
PU/LU dependent data
Engineering Change Levels
bit 0, solicitation indicator (see above)
bit 1, not last request indicator (see above)
bits 2-7, type code:
000101; the CNM target ID identifies a PU
Node identification
bits 0-11, block number
bits 12-31, ID number
Reserved
Implementation defined data describing hardware, microcode, and
programming levels
Link Connection Subsystem Data (retired: supported only for PUs not at
the current level of SNA)
bit 0, solicitation indicator (see above)
bit 1, not last request indicator (see above)
bits 2-7, type code:
000110; the CNM target ID identifies an adjacent
link station in the origin subarea
Node identification:
bits 0-11, block number
bits 12-31, ID number
Reserved
Data selection, echoed from the soliciting REQMS command:
X'02' link status command sequence
X'03' remote DTE interface status
X'04' remote modem self test
Link connection subsystem type:
X'Ol' link type 1 (links that use 3863, 3864, or 3865 modems; also links
that use 5865, 5866, or 5868 modems running LPDA-l)
X'02' link type 2 (3867 link diagnostic unit)
Validity indicators, bits 0-9 (how the PU sending this RU views the data):
Note:
The values to follow are used in each of the validity indicator
fields.
00 data valid, from the modem
01 data invalid, no response from the modem
10 data invalid, response in error from the modem
11 data invalid, execution not attempted by the PU sending
this RU
bits 0-1, remote modem status
bits 2-3, local modem status
bits 4-5, modem self test

SNA Formats

RECFMS

18-19

20-21

22-24

Note:- If byte 14 = X'02', bits 4-5 are for local modem
self-test.
If byte 14 = X'04', bits 4-5 are for remote modem
self-test.
bits 6-7, reserved
bits 8-9 , remote DTE interface status
bits 10-13, reserved
bits 14-15, Link Connection Subsystem Data format indicator:
00 format 0
01 format 1: same as format 0, plus; remote modem self test
results, channelization status, local and remote modem
status extensions, and general status extensions
Remote modem status:
bits 0-5, hit count (noise spikes) for link type 1, reserved for link type
2
Note:
For bits 6-7 and 12-14 , when the condition exists, the bit value
will be 1.
bit 6, modem reinitia1ization was performed
bit 7, loss of receive line signal
bits 8-11, quadratic error value for link type 1, number of byte errors
during test for link type 2
bit 12, remote DTE power off detected
bit 13, Data Terminal Ready loss detected
bit 14, Switched-Network-Back-Up connected
bit 15, DTE streaming condition detected
Local modem status:
bits 0-5, hit count (noise spike) for link type 1, reserved for link type
2
Note:
For bits 6-7 and 12-14, when the condition exists, the bit value
will be 1.
bit 6, modem reinitialization was performed
bit 7, loss of receive line signal
bits 8-11, quadratic error value for link type 1, number of byte errors
during test for link type 2
bit 12, remote modem power loss detected
bit 13, speed,for link type 1 (always full for link type 2):
o half
1 full
bit 14, Switched-Network-Back-Up connected
bit 15, reserved
Local Modem Self-Test and Remote-Tone Results, or Remote Modem Self-Test
----- ------Results:
Note:
If byte 14 is X'02', link status command sequence, then bytes 22-24
pertain to the local modem. If byte 14 is X'04', remote modem self-test,
then bytes 22-24 pertain to the remote modem.
bits 0-2, model bits, concatenated to the right to the bit-string formed
by bits 18, 19, 8, and 15 (in this order) represents the modem
model returned as modem self-test result in the bit-string
formed by bits 2 and 3 of byte 3, bits 0 and 7 of byte 2, and
bits 0, 1, and 2 of byte 1 (in this order), see LPDA-1 Results
Message Information Fields in "IBM 5865/5866 Modem Models 2, 3
Maintenance Information and Parts Catalog", Document number
SY33-2048.
bit 3, link connection type:
o nonswitched

Chapter 5.1.

Request Units

5.1-33

RECFMS
1 switched
configuration:
o point to point
1 multipoint
bit 5~ modem role:
o primary or control modem
1 secondary or tributary modem
bit 6~ Clear To Send delay for link type 1 (reserved for link type 2):
o normal
1 exceptional
bit 7~ received line signal detector sensitivity for link type 1
(reserved for link type 2):
o normal
1 limited
bit 8~ model bit, see bits 0-2 specification
bit 9~ modem self-test result:
o passed
1 failed
bit 10~ remote tone test result for local modem self test (reserved for
remote modem self test):
o passed
1 failed
Note:
For the following bits, when the condition exists, the bit value
will be 1.
bit ll~ feature card suspected in error
bit 12, receiver card suspected in error for link type 1 (reserved for
link type 2)
bit 13~ receiver card extension suspected in error for link type 1
(reserved for link type 2)
bit 14~ front end card is suspected in error for link type 1 (reserved for
type 2)
bi t 15~ model bit, see bits 0-2 specification
bi t 16~ feature card installed (tone alarm card installed if nonswitched
link connection; integral protection coupler installed if switched
link connection)
bit 17, Switched-Network-Back-Up installed
bit 18~ model bit, see bits 0-2 specification; also if its value 1S 1 then
channelization feature installed
bit 19, model bit, see bits 0-2 specification; also if its value is 1 then
fan-out feature installed
bits 20-23~ microcode EC level
Remote DTE Interface Status
Current state of the RS-232C or V.24 interface leads (for bits 0-5 and 7~
when the condition exists, the bit value is set to 1):
bit O~ Request To Send
bit 1~ Clear To Send
bit 2~ Reserved
bit 3, Transmit Data
bit 4~ reserved
bit 5, Data Terminal Ready
bit 6, speed:
o half
1 full
bit 7, DTE power loss
bit

25-26
25

5.1-34

4~

SNA Formats

RECFMS
26

Indication of transition of RS-232C or V.24 leads since last test
occurrence (for the following bits, when the condition exists, the bit
value is set to 1):
bit 0, Request To Send changed at least once
bit 1, Clear To Send changed at least once
bit 2, Received Data changed state
bit 3, Transmit Data changed state
bit 4, Received Line Signal loss was detected at least once
bit 5, Data Terminal Ready dropped at least once
bit 6, modem speed was changed at least once
bit 7, DTE power loss was detected at least once
• End of format 0, Format 1 continues below.

27-29
27

28-29

30-37
30

31-37
38-45
38

Channelization status
Channelization and tailing flags (for the following bits, when the
condition exists, the bit value is set to 1):
bit 0, this data is associated with a channelized modem
bit 1, this data is associated with a tailed link of a channelized modem
bit 2, this data is associated with channel A of a channelized modem
bits 3-7, reserved
Channelization correlation number: a user assigned value used to
correlate link connections with a channelized modem. The same value may be
assigned to each of the link connections of a channelized modem so that
those link connections can be associated with that particular modem
Local Modem Status Extension
Local modem receive dB level (with all code points representing dB units):
X'OO'
function not supported
X'01'-X'40' ignore data
X'41'
not available
X'42'-X'4B' < -48 dB
X'4C'
-48 dB
-47 dB
X'4D'
-46 dB to -28 dB
X'4E'-X'60'
-27 dB
X'61'
-26 dB to -17 dB
X'62'-X'6B'
-16 dB
X'6C'
-15 dB to - 7 dB
X'6D'-X'75'
- 6 dB
X'76'
- 5 dB to + 1 dB
X'77'-X'7D'
X' 7 E'
+ 2 dB
X'7F'
> + 2 dB
X'80'-X'FF' ignore data
,reserved
Remote Modem Status Extension
Remote modem receive dB level (with all code points representing dB
uni ts) :
X'OO'
function not supported
X'01'-X'40' ignore data
X'41'
not available
X'42'-X'4B' < -48 dB
-48 dB
X'4C'
-47 dB
X'4D'
-46 dB to -28 dB
X'4E'-X'60'

Chapter 5.1.

Request Units

5.1-35

RECFMS
-27 dB
X'61'
X'62'-X'6B'
-26 dB to -17 dB
-16 dB
X '6C'
-IS dB to - 7 dB
X'6D'-X'7S'
- 6 dB
X' 76 '
- S dB to + 1 dB
X'77'-X'7D'
X '7 E'
+ 2 dB
X' 7 F'
> + 2 dB
X'80'-X'FF' ignore data
31-37
reserved
46-S3(=n) General status extension
Link-level address used to address the remote modem
46
47
Remote DTE Interface Extension
48-S3(=n) Reserved

CNM vectors (described zero-origin)
(Retired:

o
1

2-n
O-n

o
1

2-n
O-n

o
1

2

3
4-n

S .1-36

CNM vectors are supported only for PUs not at the current level of SNA)
Vector length: a binary count of the length in bytes of this vector
(bytes I-n)
Type field:
bits 0-1, reserved
bits 2-7, vector type: an identifier of the information contained in
bytes 2-n.
Vector data
Embedded Text Vector
Vector length: a binary count of the length in bytes of this vector
(bytes I-n)
Type field:
bits 0-1, reserved
bits 2-7, vector type:
000000 the vector contains a text message, composed of SCS
characters (only value defined)
Vector data in SCS text
Embedded Name List Vector
Vector length: a binary count of the length in bytes of this vector
(bytes I-n)
Type field:
bits 0-1, reserved
bits 2-7, vector type:
001100
Hierarchy name options!
X'OI' reserved
X'02' only value defined
X'03' retired
Number of name entries to follow
Hierarchy name list: identifies network elements for which there is no
name known to the controlling SSCP; examples of such elements are disk
drive, display head; the hierarchy name list can contain up to five
entries in hierarchy sequence; first is nearest to the PU; each entry has
the following format:

SNA Formats

RECFMS

o
I-m
m+l-m+4

O-n

o
1

2-n

Binary count of the length in bytes of the name
Name in EBCDIC (any SCS character string)
Resource type:
if byte m+l is not equal to X'OO', no translation is
required and the resource type is the EBCDIC value of the four bytes
(e.g., "loop," "disk," or "adapn); if byte m+l=X'OO' and byte m+2=X'00',
bytes m+3 and m+4 are assumed to contain an encoded value that can be
translated into resource type; if byte m+l=X'OO' and byte m+2=X'01', bytes
m+3 and m+4 are qualifiers of the Alert originator block number, creating
a unique type code by product
User Action Qualifier
Vector length: a binary count of the length in
(bytes I-n)
Type field:
bits 0-1, reserved
bits 2-7, vector type:
001101
User action qualifier: a product-defined value
characters that is to distinguish, for example,
of an element (e.g., reporting which scanner of

bytes of this vector

represented in SCS
among multiple instances
several has failed)

RELQ; LU-->LU, Exp; DFC (RELEASE QUIESCE)
RELQ is used to release a half-session from
state. This RU is not used for LU 6.2

o

a quiesced

X'82' request code

REQMS; SSCP-->PU, Norm; FMD NS(ma) (REQUEST MAINTENANCE STATISTICS)
Retired
REQMS requests the management services associated with the
PU to provide maintenance statistics for the resource
indicated by the CNM target ID in the CNM header.
0-2
3-4
5-6

7

X'4103Q4' NS header
CNM target ID, as specified in bytes 5-6, bits 2-3
bits 0-1, reserved
bits 2-3, CNM target ID descriptor:
00 byte 4 contains a local address for a PU or LU in a PU_T2
node or an LSID for a PU or LU in a PU_Tl node; byte 3 is
reserved
01 bytes 3-4 contain the element address of a link, adjacent
link station, PU, or LU in the destination subarea, if ENA is
supported; otherwise, its network address
bits 4-15, procedure related identifier (PRID): a CNM application program
generated value for CNM application program correlation, or an
SSCP generated value for SSCP routing
Request-Specific Information
bit 0, reset indicator (or reserved, as shown below for each Type code):
o do not reset data when RECFMS is sent in reply
1 reset data when RECFMS is sent in reply
bit 1, reserved
bits 2-7, request-specific type code (see below)

Chapter 5.1.

Request Units

5.1-37

REQMS
Note:
For reply (i.e.~ solicited) requests~ bytes 3-6 and byte 7~ bits 2-7~ echo
the corresponding fields in the CNM header received in the request that solicited
the reply requests.

7

7

7

7-n
7

8-n
7

7-8
7

8

SDLC Test Command/Response Statistics
bit O~ reset indicator
bit l~ reserved
bits 2-7~ type code:
000001; the CNM target ID identifies a PU_TlI2
Summary Error Data
bit O~ reset indicator
bit l~ reserved
bits 2-7, type code:
000010; the CNM target ID identifies a PU
Communication Adapter Data
bit 0, reset indicator
bit l~ reserved
bits 2-7, type code:
000011; the CNM target ID identifies a PU_TlI2
PU- ~ LU-Dependent Data
bit 0, reset indicator
bit 1, reserved
bits 2-7, type code:
000100; the CNM target ID identifies a PUILU
PU- or LU-dependent request parameters:
implementation dependent
information (See CNM application product specifications for details.)
Engineering Change Levels
bits 0-1, reserved
bits 2-7~ type code:
000101; the CNM target ID identifies a PU
Link Connection Subsystem Data (Retired: supported only for PUs not at
the current level of SNA)
bit O~ reset indicator
bit 1, reserved
bits 2-7, type code:
000110; the CNM target ID identifies an adjacent
link station in the destination subarea
Data selection requested:
X'02' link status command sequence
X'03" remote DTE interface status
X'04' remote modem self test

RQR; SLU-->PLU, Exp; SC (REQUEST RECOVERY)
RQR is sent by the secondary to request the primary to
initiate recovery for the session by sending CLEAR or to
deactivate the session. This RU is not used for LU 6.2.

o

X'A3' request code

RSHUTD; SLU-->PLU, Exp; DFC (REQUEST SHUTDOWN)
RSHUTD is sent from the secondary to the primary to
indicate that the secondary is ready to have the session
deactivated.
RSHUTD
does not
request a
shutdown;
therefore~ SHUTD is not a proper reply; RSHUTD requests an
UNBIND.
This RU is not used for LU 6.2.

o

X'C2' request code

5.1-38

SNA Formats

RTR
RTRj LU-->LU, Normj DFC (READY TO RECEIVE)
RTR indicates to the
initiate a bracket.
speaker.

o

bidder that it is now allowed to
RTR is sent only by the first

X'OS' request code

S8Ii LU-->LU, EXPi DFC (STOP BRACKET INITIATION)
SBI is sent by either half-session to request that the
receiving
half-session stop
initiating brackets
by
continued sending of BB and the BID request.
This RU is
not used for LU 6.2.

o

X'7l' request code

SDTi PLU-->SLU, SSCP-->PUISSCP, EXPi SC (START DATA TRAFFIC)
SDT is sent by the primary session control to the
secondary session control to enable the sending and
rece1v1ng of FMD and DFC requests and responses by both
half-sessions. This RU is not used for LU 6.2.

o

X'AO' request code

SHUTei SLU-->PLU, EXPi DFC (SHUTDOWN COMPLETE)
SHUTC is sent by a secondary to indicate that it is 1n the
shutdown (quiesced) state.
This RU is not used for LU
6.2.

o

X'Cl' request code

SHUTDi PLU-->SLU, EXPi DFC (SHUTDOWN)
SHUTD is sent by the primary to request that the secondary
shut down (quiesce) as soon as convenient. This RU is not
used for LU 6.2.

o

X'CO' request code

SIGi LU-->LU, EXPi DFC (SIGNAL)
SIG is an expedited request that can be sent between
half-sessions,
regardless of the status of the normal
flows.
It carries a four-byte value, of which the first
two bytes are the signal code and the last two bytes are
the signal extension value.

o
1-2

X'C9' request code
Signal code:
X'OOOO' no-op (no system-defined code)
X'OOOl' request to send (only value defined for LU 6.2)

Chapter 5.1.

Request Units

5.1-39

SIG

3-4

X'0002' assistance requested
X'0003' intervention required (no data loss)
Signal extension: set by the sending end user or NAU services manager, or
set to X'OOOI' for LU 6.2 by data flow control

STSN; PLU-->SLU, Exp; SC (SET AND TEST SEQUENCE NUMBERS)
STSN is sent by the primary half-session sync point
manager to resynchronize the values of the half-session
sequence numbers, for one or both of the normal flows at
both ends of the seSS10n. This RU is not used for LU 6.2.

o
1

2-3
4-5

X'A2' request code
bits 0-1, action code for S-->P flow (related data in bytes 2-3)
bits 2-3, action code for P-->S flow (related data in bytes 4-5)
Note:
Each action code is set and processed independently. Values for
either action code are:
00 ignore; this flow not affected by this STSN
01 set; the half-session value is set to the value in bytes 2-3
or 4-5, as appropriate
10 sense; secondary half-session's sync point manager returns
the transaction processing program's sequence number for this
flow in the response RU
11 set and test; the half-session value is set to the value in
appropriate bytes 2-3 or 4-5, and the secondary
half-session's sync point manager compares that value against
the transaction processing program's number and responds
accordingly
bits 4-7, reserved
Secondary-to-primary sequence number data to support S-->P action code
Primary-to-secondary sequence number data to support P-->S action code
Note:
For action codes 01 and 11, the appropriate bytes 2-3 or 4-5
contain the value to which the half-session value is set and against which
the secondary half-session's sync point manager tests the transaction
processing program's value for the respective flow.
For action codes 00
and 10, the appropriate bytes 2-3 or 4-5 are reserved.

TERM-SELF Format 0; TLU-->SSCP, Norm; FMD NS(s) (TERMINATE-SELF)
TERM-SELF from the TLU requests that the SSCP assist in
the termination of one or more sessions between the sender
of the request (TLU = OLU) and the DLU. This RU is not
used for LU 6.2; refer to TERM-SELF Format 1.
0-2
3

X'Ol0683' NS header
Type:
bits 0-1, 00 the request applies to active and pending-active sessions
01 the request applies to active, pending-active, and queued
sessions
10 the request applies to queued only sessions
11 reserved
bit 2, reserved if byte 3, bit. 4 = 1; otherwise:
o forced termination--session to be deactivated immediately and
unconditionally

5.1-40

SNA Formats

TERM-SELF Format 0
1 orderly termination--permitting an end-of-session procedure to
be executed at the PlU before the session is deactivated
bit 3, 0 do not send DACTLU to OLU; another session initiation request
will be sent for OlU
1 send DACTlU to OLU when appropriate; no further session
initiation request will be sent (from this sender) for OlU
bit 4, 0 orderly or forced (see byte 3, bit 2)
1 clean up
bits 5-6, 00 select session(s) for which DLU is PlU
01 select session(s) for which DLU is SlU
10 select session(s) regardless of whether DLU is SlU or PLU
11 reserved
bit 7, 0 indicates that the format of the RU is Format 0 and that byte 3
is the Type byte.
4-m
Uninterpreted Name of DLU
4
Type:
X'F3' logical unit
Length, in binary, of DLU name
5
Note:
If the length value of the DLU name is 0, then the TERM-SELF
applies to all sessions, as specified in the Type byte, where the TLU is a
partner.
6-m
EBCDIC character string
Note:
The following defaults are supplied by the SSCP receiving a Format 0
TERM-SELF:
•
•
•

Reason:
network user, normal
Notify:
do not notify
URC is not used in mapping to subsequent requests.

TERM-SELF Format Ii TLU-->SSCP, Norm; FMD NS(s) (TERMINATE-SELF)
TERM-SELF from the TLU requests that the SSCP assist in
the termination of one or more sessions between the sender
of the request (TlU = OlU) and the DLU.
0-2
3

4

X'810683' NS header
bits 0-3, format:
0001 Format 1 (only value defined)
bits 4-6, reserved
bit 7, 1 indicates that byte 3, bits 0-3, contain the format value
Type:
bits 0-1, 00 the request applies to active and pending-active sessions
01 the request applies to active, pending-active, and queued
sessions (only value defined for LU 6.2)
10 the request applies to queued sessions only
11 reserved
bit 2, reserved if byte 4, bit 7 = Ii otherwise:
o forced termination--session to be deactivated immediately and
unconditionally
1 orderly termination--permitting an end-of-session procedure to
be executed at the PlU before the session is deactivated
bit 3, 0 do not send DACTlU to OlU; another session initiation request
will be sent for OlU

Chapter 5.1.

Request Units

5.1-41

TERM-SELF Format 1

5

6

7

8-n

n+l-n+2
n+3-p
n+3
n+4-p

1 send DACTLU to OLU when appropriate; no furthe~ session
initiation request will be sent (from this sender) for OLU (only
value defined for LU 6.2)
bit 4, reserved
bits 5-6, 00 select session(s) for which DLU is PLU
01 select session(s) for which DLU is SLU
10 select session(s) regardless of whether DLU is SLU or PLU
11 reserved
bit 7, 0 orderly or forced (see byte 4, bit 2)
1 clean up
Reason:
bit 0, 0 network user (only value defined for LU 6.2)
1 network manager
bit 1, 0 normal termination
1 abnormal termination
bits 2-7, reserved
NOTIFY specifications (reserved for lU 6.2):
bits 0-5, reserved
bit 6, 0 do not notify TLU when the session takedown procedure is
complete
1 notify the TLU when the session takedown procedure is complete
bit 7, reserved
Reserved
Session key, as described in the section "Session Key" 1n Chapter 8
Note:
One of the following session keys is used:
X'Ol' uninterpreted name of DLU
Note:
If the length value is 0, then the TERM-SELF applies to all
sessions specified in the Type byte where the TLU is a partner.
X'OA' URC
Note: This URC is the one carried in the INIT issued previously by
the same LU (i.e., ILU = TLU), and differs from the one in bytes n+4
through p.
Retired
User Request Correlation (URC) Field
Length, in binary, of URC field
Note:
X'OO' = no URC.
URC:
LU-defined identifier; this value can be returned by the SSCP in a
subsequent NOTIFY to correlate the NOTIFY to this terminating request

UNBIND; LU-->LU, Exp; SC (UNBIND SESSION)
UNBIND is sent 1) to deactivate an active session between
the two LUs, 2) as a reply to a BIND that could not be
accepted.

o
1

5.1-42

X'32' request code
UNBIND type (for UNBIND types X'OO' through X'06' and X'80' through X'FF',
the session is ended when the response is received; for UNBIND types X'07'
through X'7F', the session is ended immediately):
X'Ol' normal end of session
X'02' BIND forthcoming; retain the node resources allocated to this
session, if possible

SNA Formats

UNBIND
X'06' invalid session parameters:
the BIND negotiation has failed because
the primary half-session cannot support parameters specified by the
secondary
X'07' virtual route inoperative:
the virtual route used by the lU-lU
session has become inoperative, thus forcing the deactivation of the
identified LU-LU session
X'08' route extension inoperative:
the route extension used by the LU-LU
session has become inoperative, thus forcing the deactivation of the
identified LU~LU session
X'09' hierarchical reset: the identified LU-LU session is being
deactivated because of a +RSP((ACTPU I ACTLU), Cold)
X'OA' SSCP gone:
the identified LU-LU session had to be deactivated
because of a forced deactivation of the SSCP-PU or SSCP-lU session
(e.g., DACTPU, DACTlU, or DISCONTACT was received)
X'OB' virtu~l route deactivated:
the identified LU-lU session had to be
deactivated because of a forced deactivation of the virtual route
being used by the LU-LU session
X'OC' LU failure--unrecoverable:
the identified LU-lU session had to be
deactivated because of an abnormal termination of the PlU or SlU;
recovery from the failure was not possible
X'OE' lU failure--recoverable:
the identified lU-LU session had to be
deactivated because of an abnormal termination of one of the LUs of
the session; recovery from the failure may be possible
X'OF' cleanup:
the node sending UNBIND is resetting its half-session
before receiving the response from the partner node
X'II' gateway node cleanup: a gateway node is cleaning up the session
because a gateway SSCP has directed the gateway node (via NOTIFY) to
deactivate the session (e.g., a session setup error or session
takedown failure has occurred)
X'12' XRF-backup hierarchical reset: the identified XRF-backup LU-lU
session is being deactivated because the related XRF-active session
terminated normally. The sending LU is resetting its half-session
before receiving the response from the partner LU.
X'13' XRF-active hierarchical reset: the identified XRF-active LU-LU
session is being deactivated because the related XRF-backup session
performed a takeover of this session (via SWITCH). The sending LU
is resetting its half-session before receiving the response from the
partner LU.
the sending LU is resetting its half-session before
receiving the response from the partner LU
X'FE' session failure:
the session has failed for a reason specified by
the associated sense data
• For sessions that were established with extended BIND, bytes 2-n are
included; otherwise, bytes 6-n are omitted and bytes 2-5 are included only
for Type = X'FE'.
2-5

6-n

Sense data: same value as generated at the time the error was originally
detected (e.g., for a negative response, receive check, or EXR)
Note:
For Type=X'FE' the Sense Data field in bytes 2-5 of the UNBIND RU
is the same as that in bytes 3-6 of the Extended Sense Data control
vector; otherwise, this field (bytes 2-5 of the UNBIND RU) is reserved.
Control vectors, as described in the section "Control Vectors" in Chapter
8

Chapter 5.1.

Request Units

5.1-43

UNBIND
Note:
The following control vectors may be included; they are parsed
according to subfield parsing rule KL:
X'35' Extended Sense Data control vector (present when the UNBIND Type is
X'FE' or is immediate, i.e., X'D7' through X'7F')
X'6D' Fully-qualified peID control vector (present on sessions that were
established with extended BIND)
Note:
An UNBIND is sent instead of a -RSP(BIND) as a reply to BIND (to reject the
BIND) only if the BIND is extended and no errors limit recognition of the BIND as
extended.

5.1-44

SNA Formats

CHAPTER 5.2.

RESPONSE UNITS

INTRODUCTION
Apart from the exceptions cited below, response units return the number of bytes
specified in the following table; only enough of the request unit is returned to
include the field-formatted request code or NS header.

RU Category of Response

Number of Bytes

DFC
SC
NC
FMD NS ( FI = I) (field-formatted)
FMD NS (FI=O) (character-coded)
FMD (lU-lU)

I
1
1
3
0
0

All negative responses return four bytes of sense data in the RU, followed by
either:
1.

The number of bytes specified in the table above, or

2.

Three bytes (or the entire request unit, if shorter than three bytes).

The second option applies where a sensitivity to SSCP-based sessions versus lU-lU
sessions does not necessarily exist and can be chosen for implementation simplicity.
Refer to Chapter 9 for sense data values and their corresponding meanings.
Some positive response units return the request code or NS header followed by
additional data.
"Positive Response Units with Extended Formats" on page 5.2-3
contains detailed formats of these response units, arranged in alphabetical order.
Each format description begins with the following heading:
"RSP(ABBREVIATED RU NAME); Origin-NAU-->Destination-NAU, Normal (Norm) or
Expedited (Exp) Flow; RU Category"
Notes:

1.

"RU Category" is abbreviated as follows:
DFC

data flow control

SC

sess10n control

NC

network control

Chapter 5.2.

Response Units

5.2-1

Response Units
FMD NS(ma)

function management data, network services, management services
(note:
formerly maintenance services)

FMD NS(s)

function management data, network services, session services

2.

Throughout the format descriptions, reserved is used as follows:
reserved bits,
or fields, are ones that currently are set to O's (unless explicitly stated
otherwise); reserved values are those that currently are invalid. Correct usage
of reserved fields is enforced by the sender; no receive checks are made on
these fields.

3.

Throughout the format descriptions, retired fields and values are those that
were once defined in SNA but are no longer defined. To accommodate
implementations of back-level SNA, current implementations of SNA treat retired
fields as follows: send checks enforce the setting of retired fields to all O's
except where other unique values are required (described individually); no
receive checks are made on these fields, thereby accepting back-level settings
of these fields.
Special handling of retired fields, such as echoing or passing
on retired fields as received, is discussed where appropriate.

4.

User data, control vectors, and control lists referred to in the format
descriptions are described in Chapter 7 and Chapter 8.

5.2-2

SNA Formats

RSPCACTlU)
POSITIVE RESPONSE UNITS WITH EXTENDED FORMATS

----- ----

RSP(ACTLU)j lU-->SSCP, Expj SC
o
X'OD' request code
I
Type of activation selected:
X'Ol' cold
X'02' ERP
2
bits 0-3, FM profile:
X'O' FM Profile 0
X'6' FM Profile 6
bits 4-7, TS profile: same as the corresponding request
Note:

Two versions of this RU are defined.

• A full response can be sent in which bytes O-m are present.
3-m

Control vectors as described in the section "Control Vectors" in Chapter 8
Note: The following control vectors may be includedj they are parsed
according to subfield parsing rule Kl. When present, they appear in the
order specified.
X'OO' SSCP-lU Session Capabilities control vector (always present, always
first)
X'OC' lU-lU Session Services Capabilities control vector (always present,
always second)
• A two-byte response may be receivedj it means maximum RU size = 256 bytes,
lU-lU session limit = I, the lU can act as a secondary lU, and all other
fields in control vectors X'OO' and X'OC' are defaulted to O's.

RSP(ACTPU]j PU-->SSCp, Exp; SC
o
X'll' requ~st code
I
bits 0-1, reserved
bits 2-3, format of response:
00 format 0
bits 4-7, type activation selected:
X'2' ERP
2-9
Contents ID: eight-character EBCDIC symbolic name of the load module
currently operating in the node; eight space (X'40') characters is the
default value

Chapter 5.2.

Response Units

5.2-3

RSPCBIND)

RSP(BINDJ; SLU-->PLU, Exp; SC
A +RSPCBIND) carries the session parameters as indicated
by the SLU or by intermediate nodes along the session
path.

•
•

•

•

A short
(I-byte)
response may
be sent
for a
nonextended nonnegotiable BIND request that specifies
no session-level cryptography.
A cryptography response (bytes O-k) may be sent for a
nonextended nonnegotiable BIND request that specifies
session-level cryptography.
A nonextended negotiable response (bytes O-r) may be
sent for an extended or nonextended negotiable BIND
request.
An extended response (bytes O-s) may be sent for an
extended (negotiable or nonnegotiable) BIND request.
Intermediate nodes along the session path may extend
short, cryptography, and negotiable responses.

a

X'31' request code

1

bits 0-3, format:
0000 (only value defined)
bits 4-7, type:
0000 negotiable (only value defined for LU 6.2)
0001 nonnegotiable
Bytes 2-25 of the BIND request:
for an extended or negotiable response,
the negotiated values may differ; for a cryptography response, the values
are the same as those received in the BIND request
Cryptography Options (see Note 3) for a nonnegotiable response, same value
returned as received in the for a nonnegotiable response or an LU 6.2
response, same value
bits 4-7, session-level cryptography options field length: same value
(Bytes 27-k are omitted if this length field is omitted or set
to 0.)
bits 0-1, session cryptography key encipherment method: same value
returned as received in the request, if present
bits 2-4, reserved
bits 5-7, cryptography cipher method: same value returned as received
An eight-byte implementation-chosen, nonzero, pseudo random session-seed
cryptography value enciphered under the session cryptography key, if
session-level cryptography is specified; otherwise, omitted
Retired: set to a by implementations at the current level of SNA
Length of user data
User data:
for an extended or negotiable response, the user data may
differ from that received on the BIND request
Length of URC
URC as received on the BIND request
Retired: set to a by implementations at the current level of SNA
Control vectors, as described in "Control Vectors" in Chapter 8
Note:
The following control vectors may be included; they are parsed
according to subfield parsing rule KL:

2-25

26-k

27

28-k

k+l(=m)
m+l
m+2-n
n+l
n+2-p
p+l(=r)
r+l-s

5.2-4

SNA Formats

RSP(BIND)
X'60' Fully-Qualified PCID control vector (present if received on the
BIND)
Note:
The receiving lU simply ignores unrecognized control vectors.

Note ~ On a response, if the last byte of a response without control vectors (byte
7, bit 6 = 0) is a length field and that field is 0, that byte may be dropped from
the response.
This applies also to byte 26 (where the count occupies only bits 4-7)
if bits 0-3 are also O--the entire byte may be dropped if no bytes follow.
Note ~ In negotiable or extended BIND responses, reserved fields in the BIND are
set by the SlU to binary O's in the RSP(BIND); any fields at the end of the BIND
that are not recognized by the SlU are discarded and not returned in the RSP(BIND).
Note 3: The first byte of the Cryptography Options field (byte 26) is returned on
the response for a nonextended nonnegotiable BIND only when session-level
cryptography was specified in the BIND.
Byte 26 is always present in any extended
response.
It is also present in any nonextended negotiable response if not
truncated as allowed in Note 1.
In all cases, however, the remaining bytes of the
Cryptography Options field (bytes 27-k) are present only if session-level
cryptography was specified in the BIND.
Note ~ On a response, when the adaptive session-level pacing support bit (byte 9,
bit 0) is set to 1 (adaptive session pacing supported), the window sizes (byte 8,
bits 2-7; byte 9, bits 2-7; byte 12, bits 2-7 and byte 13, bits 2-7) are all set to
O.

Note 5:
form:

o
1

2-5
6

7

8

9

An extended short responSe to a nonnegotiable BIND is of the following

X'31' request code
bits 0-3, format: 0000 (only value defined)
bits 4-7, 0001 nonnegotiable
Reserved
bit 0, whole-BIUs required indicator (reserved in nonextended non-lU6.2
BIND responses):
o the sending node (SLU-side of the session stage) supports
receipt of segments on this session
1 the sending node (SLU-side of the session stage) does not
support receipt of segments on this session; the maximum sent-RU
size specified in bytes 10 and 11 of RSP(BIND) are negotiated so
that BIUs on this session are not segmented when sent to a node
requiring whole BIUs
bits 1-7, reserved
bits 0-5, reserved
bit 6, control vectors included indicator:
1 control vectors are present (only value defined)
bit 7, reserved
bit 0, secondary-to-primary pacing staging indicator:
o pacing in the secondary-to-primary direction occurs in one stage
(only value defined)
bits 1-7, reserved
bit 0, adaptive session-level pacing support:

Chapter 5.2.

Response Units

5.2-5

RSPCBIND)

o adaptive pacing not supported by the sending node
1 adaptive pacing supported by the sending node
bits 1-7, reserved
Maximum RU size sent on the normal flow by the secondary side of the
10
session
Maximum RU size sent on the normal flow by the primary side of the session
11
bit 0, primary-to-secondary pacing staging indicator:
12
1 pacing in the primary-to-secondary direction occurs in one stage
(only value defined)
bits 1-7, reserved
13-30(=r) Reserved
r+l-s
Control vectors, as described in the section "Control Vectors" in Chapter
8

Note:
The following control vectors may be used; they are parsed
according to subfield parsing rule KL:
X'60' Fully-Qualified PCID control vector (always present)

RSP(STSN1; SLU-->PLU, Exp; SC

o
1

5.2-6

X'A2' request code
bits 0-1, result code for S-->P action code in the request (related data
in bytes 2-3)
bits 2-3, result code for P-->S action code in the request (related data
in bytes 4-5)
Note: Values for either result code are:
• For set or ignore action code:
01 ignore (other values reserved); appropriate bytes 2-3 or 4-5
reserved
• For sense action code:
00 for LU type 0:
user-defined meaning; for all other LU types:
reserved (appropriate bytes 2-3 or 4-5 reserved)
01 reserved
10 secondary half-session's sync point manager does not maintain
or cannot return a valid transaction processing program
sequence number (appropriate bytes 2-3 or 4-5 reserved)
11 transaction processing program sequence number, as known at
the secondary, is returned in bytes 2-3 or 4-5, as
appropriate
• For set and test action code:
00 for LU type 0:
user-defined meaning; for all other LU types:
invalid sequence numbers have been detected by the secondary
(appropriate bytes 2-3 or 4-5 return the secondary
transaction processing program sequence number)
Note: An invalid determination results when the sequence
For example, the
number indicated could not have occurred.
mounting of an incorrect sync point log tape by the operator
at one of the LUs would cause this condition.
01 value received in STSN request equals the transaction
processing program sequence number value as known at the
secondary (appropriate bytes 2-3 or 4-5 return the
secondary's value for the transaction processing program
sequence number)
10 secondary half-session's sync point manager does not maintain
or cannot return a valid transaction processing program
sequence number (appropriate bytes 2-3 or 4-5 reserved)

SNA Formats

RSP(STSN)
11 value received in STSN request does not equal the transaction
processing program sequence number value as known at the
secondary (appropriate bytes 2-3 or 4-5 return the
secondary's value for the transaction processing program
sequence number)
bits 4-7, reserved
2-3
Secondary-to-primary normal-flow sequence number data to support S-->P
result code, or reserved (see Note 1 above)
4-5
Primary-to-secondary normal-flow sequence number data to support P-->S
result code or reserved (see Note I above)
Note:
Where the STSN request specified as action codes two "sets," two "ignores,"
or a combination of "set" and "ignore," the positive 'response RU optionally may
consist of one byte--X'A2' (the STSN request code)--rather than all six bytes.

Chapter 5.2.

Response Units

5.2-7

This page intentionallY left blank

5.2-8

SNA Formats

CHAPTER 6.

PROFILES

INTRODUCTION
Some of the session protocols (such as for request and response control modes,
brackets, and pacing) are selectable at session activation.
Specific combinations
of these selectable protocol options are known as profiles.
Those profiles that refer to transmission control (TC) options are called
transmission services (TS) profiles; those profiles that refer to data flow control
(DFC) and function management data services (FMDS) options are called function
management (FM) profiles.
The TS and FM profiles to be used 1n any session are specified at the time of
session activation via parameters in the appropriate session activation request and
response (see ACTPU, ACTLU, BIND, and their responses in Chapter 5).

Chapter 6.

Profiles

6-1

TRANSMISSION SERVICES (TS] PROFILES
This section describes the transmission services (TS) profiles and their use for
LU-LU sessions, SSCP-LU sessions, and SSCP-PU sessions to Type I, 2, or 2.1 nodes.
Profile numbers not shown are reserved in these sessions.
Note:
If the TS Usage field in BIND specifies a value for a parameter, that value
is used unless it conflicts with a value specified by the TS profile. The TS
profile overrides the TS Usage field.

Figure 6-1 identifies the different sessions and logical unit (LU) types that use
each TS profile.

Session Types

TS Profile

1

LU Types

1

SSCP-PU(Tl!2),

SSCP-lU

2

LU-LU

0

3

LU-LU

0, I, 2, 3

4

LU-LU

0, 1, 6.1

7

LU-LU

0, 4, 6.2, 7

The boundary function serves 1n place of the PU type 1
to process ACTPU).

Figure 6-1.

6-2

TS Profiles and Their Usage

SNA Formats

(e.g.,

TS PROFILE 1

Profile 1 (used on SSCP-PU and SSCP-LU sessions) specifies the following session
rules:
•
•
•
•
•

No pacing.
Identifiers rather than sequence numbers are used on the normal flows (whenever
the TH format used includes a sequence number field).
SDT, CLEAR, RQR, STSN, and CRV are not supported.
Maximum RU size on the normal flow between an SSCP and a peripheral LU is 256,
unless a different value is specified in RSP(ACTLU) in control vector X'OO'.
Maximum RU size on the normal flow for an SSCP sending to a peripheral PU is
256; in the reverse direction it is 512.

There is no TS Usage field associated with this profile.

TS PROFILE 2

Profile 2 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•

Primary-to-secondary and secondary-to-primary normal flows are paced.
Sequence numbers are used on the normal flows (whenever the TH format used
includes a sequence number field).
CLEAR is supported.
SDT, RQR, STSN, and CRV are not supported.

The TS Usage subfields defining the options for this profile are:
•
•

Pacing window counts
Maximum RU sizes on the normal flows

Chapter 6.

Profiles

6-3

TS PROFILE 3

Profile 3 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•
•

Primary-to-secondary and secondary-to-primary normal flows are paced.
Sequence numbers are used on the normal flows (whenever the TH format used
includes a sequence number field).
CLEAR and SOT are supported.
RQR and STSN are not supported.
CRV is supported when session-level cryptography is selected (via a BIND
parameter).

The TS Usage subfields defining the options for this profile are:
•
•

Pacing window counts
Maximum RU sizes on the normal flows

TS PROFILE 4

Profile 4 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•

Primary-to-secondary and secondary-to-primary normal flows are paced.
Sequence numbers are used on the normal flows (whenever the TH format used
includes a sequence number field).
SOT, CLEAR, RQR, and STSN are supported.
CRV is supported when session-level cryptography is selected (via a BIND
parameter).

The TS Usage subfields defining the options for this profile are:
•
•

6-4

Pacing window counts
Maximum RU sizes on the normal flows

SNA Formats

TS PROFILE 7

Profile 7 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•

Primary-to-secondary and secondary-to-primary normal flows are optionally paced.
Sequence numbers are used on the normal flows (whenever the TH format used
includes a sequence number field).
SOT, CLEAR, RQR, and STSN are not supported.
CRV is supported when session-level cryptography is selected (via a BIND
parameter).

The TS Usage subfields in BIND defining the options for this profile are:
•
•

Pacing window counts
Maximum RU sizes on the normal flows

Chapter 6.

Profiles

6-5

FUNCTION MANAGEMENT (FMl PROFILES

This section describes the function management (FM) profiles and their use for
Profile numbers not shown are reserved.
lU-lU sessions; SSCP-PU sessions to Type I,
2, or 2.1 nodes; and SSCP-lU sessions.
Profile numbers not shown are reserved in
these sessions.
Note:
If the FM Usage field in BIND specifies a value for a parameter, that value
is used unless it conflicts with a value specified by the FM profile. The FM
profile overrides the FM Usage field.

Figure 6-2 identifies the different sessions and logical unit (lU) types that use
each FM profile.

Session Types

FM Profile

1

lU Types

0

SSCP-PU(TlI2),

SSCP-lU

2

lU-lU

0

3

lU-lU

0, 1, 2, 3

4

lU-lU

0, 1

6

SSCP-lU

7

lU-lU

0, 4, 7

18

lU-lU

0, 6.1

19

lU-lU

6.2

The boundary function serves 1n place of the PU type 1
to process ACTPU).

Figure 6-2.

6-6

FM Profiles and Their Usage

SNA Formats

(e.g.,

FM PROFILE 0

Profile 0 (used on SSCP-PU and SSCP-LU sessions) specifies the following session
rules:
•
•
•

•
•
•
•
•
•
•

Primary and secondary half-sessions use immediate request mode and immediate
response mode.
Only single-RU chains allowed.
Primary and secondary half-session chains indicate definite response.
Half-session chains generated by a boundary function on behalf of the LU may
indicate no-response or definite response.
No compression.
Primary half-session sends no DFC RUs.
Secondary LU half-session may send LUSTAT.
No FM headers.
No brackets.
No alternate code.
Normal-flow send/receive mode is full-duplex.

FM PROFILE 2

Profile 2 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•
•
•
•
•
•
•
•
•
•

Secondary LU half-session uses delayed request mode.
Secondary LU half-session uses immediate response mode.
Only single-RU chains allowed.
Secondary LU half-session requests indicate no-response.
No compression.
No DFC RUs.
No FM headers.
Secondary LU half-session is first speaker if brackets are used.
Bracket termination rule 2 is used if brackets are used.
Primary LU half-session will send EB.
Secondary LU half-session will not send EB.
Normal-flow send/receive mode is FDX.
Primary LU half-session is responsible for recovery.

The FM Usage fields defining the options for Profile 2 are:
•
•
•
•

Primary request control mode selection
Primary chain response protocol (no-response may not be used)
Brackets usage and reset state
Alternate code

Chapter 6.

Profiles

6-7

FM PROFILE 3

Profile 3 (used on lU-lU sessions) specifies the following session rules:
•
•

Primary LU half-session and secondary lU half-session use immediate response
mode.
Primary lU half-session and secondary lU half-session support the following DFC
functions:
CANCEL
SIGNAL
lUSTAT (allowed secondary-to-primary only)
CHASE
SHUTD
SHUTC
RSHUTD
BID and RTR (allowed only if brackets are used)

The FM usage fields defining the options for Profile 3 are:
•
•
•
•
•
•
•
•
•
•
•
•
•

6-8

Chaining use (primary and secondary)
Request control mode selection (primary and secondary)
Chain response protocol (primary and secondary)
Compression indicator (primary and secondary)
Send EB indicator (primary and secondary)
FM header usage
Brackets usage and reset state
Bracket termination rule
Alternate Code Set Allowed indicator
Normal-flow send/receive mode
Recovery responsibility
Contention winner/loser
Half-duplex flip-flop reset states

SNA Formats

FM PROFILE 4

Profile 4 (used on LU-LU sessions) specifies the following session rules:
•
•

Primary LU half-session and secondary LU half-session use immediate response
mode.
Primary LU half-session and secondary LU half-session support the following DFC
functions:
CANCEL
SIGNAL
LUSTAT
QEC
QC
RELQ
SHUTD
SHUTC
RSHUTD
CHASE
BID and RTR (allowed only if brackets are used)

The FM Usage fields defining the options for Profile 4 are:
•
•
•
•
•
•
•
•
•
•
•
•
•

Chaining use (primary and secondary)
Request control mode selection (primary and secondary)
Chain response protocol (primary and secondary)
Compression indicator (primary and secondary)
Send EB indicator (primary and secondary)
FM header usage
Brackets usage and reset state
Bracket termination rule
Alternate Code Set Allowed indicator
Normal-flow send/receive mode
Recovery responsibility
Contention winner/loser
Half-duplex flip-flop reset states

Chapter 6.

Profiles

6-9

FM PROFILE 6

Profile 6 (used on SSCP-LU sessions) specifies the following session rules:
•
•
•
•
•
•
•
•
•
•

6-10

Only single-RU chains allowed.
Primary and secondary half-sessions use delayed request mode and delayed
response mode.
Primary and secondary half-session chains may indicate definite response,
exception response, or no response.
Primary half-session sends no DFC RUs.
Secondary half-session may send LUSTAT.
No FM headers.
No compression.
No brackets.
No alternate code.
Normal-flow send/receive mode 1S full-duplex.

SNA Formats

FM PROFILE 7

Profile 7 (used on LU-lU sessions) specifies the following session rules:
•
•

Primary LU half-session and secondary LU half-session use immediate response
mode.
Primary LU half-session and secondary LU half-session support the following DFC
functions:
CANCEL
SIGNAL
lUSTAT
RSHUTD

The FM Usage fields defining the options for Profile 7 are:
•
•
•
•
•
•
•
•
•
•
•
•
•

Chaining use (primary and secondary)
Request control mode selection (primary and secondary)
Chain response protocol (primary and secondary)
Compression indicator (primary and secondary)
Send EB indicator (primary and secondary)
FM header usage
Brackets usage and reset state
Bracket termination rule
Alternate Code Set Allowed indicator
Normal-flow send/receive mode
Recovery responsibility
Contention winner/loser
Half-duplex flip-flop reset states

Chapter 6.

Profiles

6-11

FM PROFILE 18

Profile 18 (used on LU-LU sessions) specifies the following session rules:
•
•

Primary LU half-session and secondary LU half-session use immediate response
mode.
Primary LU half-session and secondary LU half-session support the following DFC
functions:
CANCEL
SIGNAL
LUSTAT
BIS and SBI (allowed only if brackets are used)
CHASE
BID and RTR (allowed only if brackets are used)

The FM Usage fields defining the options for Profile 18 are:
•
•
•
•
•
•
•
•
•
•
•
•
•

6-12

Chaining use (primary and secondary)
Request control mode selection (primary and secondary)
Chain response protocol (primary and secondary)
Compression indicator (primary and secondary)
Send EB indicator (primary and secondary)
FM header usage
Brackets usage and reset state
Bracket termination rule
Alternate Code Set Allowed indicator
Normal-flow send/receive mode
Recovery responsibility
Contention winner/loser
Half-duplex flip-flop reset states

SNA Formats

FM PROFILE 19

Profile 19 (used on LU-LU sessions) specifies the following session rules:
•
•
•
•
•
•
•
•
•
•
•
•

Primary LU half-session and secondary LU half-session use immediate request and
immediate response mode.
Multiple RU chains allowed.
Primary LU half-session and secondary LU half-session chains indicate definite
or exception response.
No compression.
Brackets are used.
FM headers (types 5, 7, and 12 only) are allowed.
Conditional termination for brackets (specified by CEB) will be used--primary
and secondary half-sessions may send CEB.
Normal-flow send/receive mode is half-duplex flip-flop.
Half-duplex flip-flop reset state is send for the primary LU half-session and
receive for the secondary LU half-session after RSP(BIND).
Symmetric responsibility for recovery.
Contention winner/loser polarity is negotiated at BIND time; the contention
winner is the first speaker and the contention loser is the bidder.
Primary and secondary half-sessions support the following DFC functions:
SIGNAL
LUSTAT
BIS
RTR

•

The following combinations of RQE, RQD, CEB, and CD are allowed on end-chain
RUs:
RQE*,
RQD2,
RQD3,
RQE1,
RQD*,
RQD*,

•

CD,
CD,
CD,

~CEB

~CD,
~CD,

CEB
CEB

~CD,

~CEB

~CEB
~CEB

Alternate code permitted.

The only FM Usage field defining options for Profile 19 is Contention Winner/Loser.

Chapter 6.

Profiles

6-13

This page intentionally left blank

6-14

SNA Formats

CHAPTER 7.

USER DATA STRUCTURED SUBFIELDS

INTRODUCTION
The structured subfields of the User Data field are defined as follows (shown with
zero-origin indexing of the subfield bytes--see the individual RU description for
the actual displacement within the RU).
Each subfield starts with a one-byte binary
length field and is identified by a subfield number in the following byte. The
length does not include the length byte itself. When more than one subfield is
included, they appear in ascending order by subfield number.
<

For LU type 6.2, the Structured User Data field of BIND and RSP(BIND) may contain
the Unformatted Data, Mode Name, Network-Qualified PlU Network Name,
Network-Qualified SlU Network Name, and Session Instance Identifier subfields.
Any
subfields received in the Structured User Data field of BIND that are not recognized
by the SlU are discarded and not returned as part of the Structured User Data field
of the RSP(BIND).

Chapter 7.

User Data Structured Subfields

7-1

User Data Subfields
DESCRIPTIONS

Unformatted Data structured Data Subfield
The Unformatted Data subfield may optionally be sent in
BIND, RSP(BIND), or any of the INITIATE RUs.
The content
is implementation-defined.

o
1
2-n

Length of the remainder of the Unformatted Data subfield:
values 1 to 17
(X'II') are valid for LU 6.2i otherwise, values 1 to 65 (X'4I') are valid
X'OO'
Unformatted data: a type-G symbol string

Session Qualifier Structured Data Subfield
The Session Qualifier subfield 1S used for LU 6.1.
It may
be carried in BIND, RSP(BIND), or any of the INITIATE RUs.

o
1

2
3-m
m+l
m+2-n

Length of the remainder of the Session Qualifier subfield (If Session
Qualifier subfield is present, values 3 to 19 (X'I3') are valid.)
X'OI'
Length of primary resource qualifier: values 0 to 8 are valid (X'OO'
means no primary resource qualifier is present)
Primary resource qualifier
Length of secondary resource qualifier: values 0 to 8 are valid (X'OO'
means no secondary resource qualifier is present)
Secondary resource qualifier

Mode Name Structured Data Subfield
The Mode Name subfield is pres~nt in both BIND and
RSP(BIND) if the PLU knows the mode name being used by the
session.

o
1
2-n

Length of the remainder of the Mode Name subfield:
valid

values 1 to 9 are

X'02'
Mode name:
0 to 8 type-A symbol-string characters with optional (but not
significant) trailing blanks

Session Instance Identifier Structured Data Subfield
The Session Instance Identifier subfield may be present 1n
both BIND and RSP(BIND).

o

Length of the remainder of the Session Instance Identifier subfield:
values 3 to 9 are valid

1

X'03'

2-n

Session instance identifier: a type-G symbol string
Note:
In BIND, the PLU sets a unique session instance identifier of
length 1 to 7 and appends it to X'OO'.
If known, the SLU compares its
network-qualified name with that of the PLUi if the PLU name> SLU name,
the SLU changes the first byte of the Session Instance Identifier subfield

7-2

SNA Formats

User Data Subfields
in the response from X'OO' to X'FO'; if the PlU name < SlU name, the
subfield is simply echoed.

Network-Qualified PLU Network Name Structured Data Subfield
BIND contains the Network-Qualified PlU
subfield (if the name is known by the PlU).

o
1
2-n

Network

Name

length of the remainder of the Network-Qualified PlU Network Name
subfield: values 2 to 18 (X'12') are valid
X'04'
Network-Qualified PlU network name
Note:
The network-qualified PlU network name 1S 1 to 17 bytes in length,
consisting of an optional 1- to 8-byte network ID and a 1- to 8-byte lU
name, both of which are type-A symbol strings.
When present, the network
ID is concatenated to the left of the lU name, using a separating period
and having the form "NWID.NAME"; when the network ID is omitted, the
period is also omitted.

Network-Qualified SLU Network Name Structured Data Subfield
The RSP(BIND) contains the Network-Qualified SlU Network
Name subfield (if the name is known by the SlU).

o
1
2-n

length of the remainder of the Network-Qualified SlU Network Name
subfield: values 2 to 18 (X'12') are valid
X'OS'
Network-Qualified SlU network name
Note:
The network-qualified SlU network name is 1 to 17 bytes in length,
consisting of an optional 1- to 8-byte network ID and a 1- to 8-byte lU
name, both of which are type-A symbol strings.
When present, the network
ID is concatenated to the left of the lU name, using a separating period
and having the form "NWID.NAME"; when the network ID is omitted, the
period is also omitted.

Random Data Structured Data Subfield
The Random Data subfield contains the random data used in
session-level security verification.
When session-level
security verification 1S in effect,
this subfield 1S
present in both BIND and RSP(BIND).

o
1

2
3-10

length of the remainder of the Random Data subfield:
10 1S the only valid
value
X'll'
Reserved
Random data: a type-G random value generated for subsequent checking in
RSPCBIND) or FMH-12

Chapter 7.

User Data Structured Subfields

7-3

User Data Subfields

Enciphered Data Structured Data Subfield
The Enciphered Data subfield is present in the RSP(BIND)
when session-level security verification is in effect.
This subfield contains the enciphered version of the clear
data received in BIND.

o

Length of the remainder of the Enciphered Data subfield:
valid value

1

X'12'

2-9

Enciphered version of the Clear Data field carried in BIND (using the DES
algorithm and the installation-defined LU-LU password as the cryptographic
key)

7-4

SNA Formats

9 is the only

CHAPTER 8.- COMMON FIELDS

INTRODUCTION

This chapter contains detailed formats of the following common fields used in
message units:
•

Control vectors

•

Session keys

•

Management services major vectors and subvectors

Chapter 8.

Common Fields

8-1

Encoding/Parsing Rules

SUBSTRUCTURE ENCODING/PARSING RULES

RULES FOR COMMON SUBSTRUCTURES

The following rules apply to encodings defined in this chapter; they govern the
encoding of SNA-defined RU substructures, i.e., structures that are carried within
some enclosing structure and that have one-byte keys identifying the substructures.
The terms key and type are used interchangeably here, since both terms are used in
the substructures to which the following rules apply.
~

Partitioning of Key/Type Values

The use of one-byte keys means that 256 values are available for defining
substructures.
The available values are partitioned as follows.

CATEGORY-DEPENDENT KEYS:

Within the category of control vectors, keys in the range
X'OO' to X'5F' are unique; within the independent category of management services
(MS) subvectors, they are also unique.

UNIQUE KEYS:

Keys in the range X'60' to X'7D' are unique across the composite
grouping of control vectors and MS subvectors, i.e., such a key has the same
meaning in both groups.

CONTEXT-SENSITIVE KEYS:

Keys in the range X'80' to X'FD' are context-sensitive.
These are unique only within the enclosing structure (e.g., a specific control
vector or GDS variable). Thus a subfield key X'80' may be defined for use within
control vector X'30' and also within control vector X'31', and the subfields may be
different.
The only exception to this rule is found in the management services
subfields.
Keys in the range X'OO' to X'7F' are unique only within the enclosing
subvector.
However, keys in the range X'80' to X'FF' are unique across the entire
group of unique subvectors defined for a given management services major vector.

Parsing Rules

Common substructures with variable length formats, such as control vectors may be
parsed in one of two ways. The parsing rule used is format specific-see the
individual format description for the parsing rule used:
KL

The Key field precedes the Length field and the length is the number of
bytes] in binary, of the substructure's Data field (e.g., Vector Data field).
The Length field value does not include the length of the substructure Header
field.

8-2

SNA Formats

Encoding/Parsing Rules
LT

The Length field precedes the Key field (also called the "type" field-hence
"LT") and the length is the number of bytes, in binary, of the substructure
including both the Header field and the Data field.

The general format of a control vector, for example, is shown as:
0-1
2-n

Vector header; Key=X'4S'
page 8-2)
Vector Data

(see "Substructure Encoding/Parsing Rules" on

When the enclosing structure indicates use of parsing rule KL, the first two bytes
are interpreted as:

o
1

Key
Length (n-I), 1n binary, of the Vector Data field (i.e., excluding the
length of the Vector Header field)

When the enclosing structure indicates use of parsing rule LT, the first two bytes
are interpreted as:

o
1

Length (n+I),-in binary, of the control vector (i.e, including the Vector
Header and Vector Data fields)
Type (=Key)

Enclosing Rule for Substructures

All substructures that are enclosed by other structures within an RU (e.g., another
substructure or a GDS variable) are constructed and parsed LT.
This is the case
even when, for example, an enclosing control vector is parsed KL.
This rule holds
true for all levels of nesting.
Consider the Product Set ID (X'lO') control vector as an example of this rule.
Imbedded within this substructure are other substructures, specifically Product
Identifier (X'II') MS common subvectors.
When the Product Set ID (X'IO') is present in XIO format 3, it is parsed KL, whereas
when it is present within a major vector in NMVT, it is parsed LT.
In both cases,
the Product Identifier (X'II') subvectors are parsed LT.

Chapter 8.

Common Fields

8-3

Control Vectors

CONTROL VECTORS

INTRODUCTION

The following table shows, by key value, the control vector and the message-unit
structures that can carry the control vector.

Key
X'OO'
X' 07'
X'OC'
X'OE'
X'lO'
X'22'
X'2C'
X'2D'
X'35'
X'60'

Control Vector
SSCP-lU Session Capabilities
PU FMD-RU-Usage
lU Session Services Capabilities
Network Name
Product Set ID
XID Negotiation Error
COS/TPF
COS/TPF
Extended Sense Data
Extended Sense Data

Applicable Message-Unit Structures
RSP(ACTlU)
RSP(ACTPU)
RSP(ACTlU)
XID, BIND
XID
XID
BIND
BIND
UNBIND
BIND, UNBIND, RSP(BIND)

CONTROL VECTOR FORMATS

The control vectors are defined as follows (with zero-or1g1n indexing of the vector
bytes--see the individual RU description for the actual displacement within the RU):
Note:
When more than one control vector may appear in an RU, unless otherwise
stated, the vectors may appear in any order.

SSCP-LU Session Capabilities (X'OO') Control Vector

o
1

2-3

8-4

Key:
X' 00'
Maximum RU size sent on the normal flow by either half-session:
if bit 0
is set to 0, then no maximum is specified and the remaining bits 1-7 are
ignored; if bit 0 is set to 1, then the byte is interpreted as X'ab' =
a·2**b (Notice that, by definition, a~8 and therefore X'ab' is a
normalized floating point representation.) See Figure 5.1-1 on page
5.1-14 for all possible values.
lU Capabilities
bit 0, character-coded capability:
o the SSCP may not send unsolicited character-coded requests; a
solicited request is a reply request or a request that carries
additional error information to supplement a previously sent
negative response or error information after a positive response
has already been sent
1 the SSCP may send unsolicited character-coded requests
bit 1, field-formatted capability:
o the SSCP may not send unsolicited field-formatted requests

SNA Formats

Control Vectors

4

1 the SSCP may send unsolicited field-formatted requests
bits 2-15, reserved
Reserved

PU FMD-RU-Usage (X'07') Control Vector

o
1

2-7

Key:
X'07'
bits 0-5, reserved
bit 6, adjacent PU load capability (initialized to 0 by the PU_T2):
o adjacent PU cannot load the T2 node
1 adjacent PU can load the T2 node (set by the boundary function
in the adjacent subarea node)
bit 7, FMD request capability of the node:
o PU cannot receive FMD requests from the SSCP
1 PU can receive FMD requests from the SSCP
Reserved

LU-LU Session Services Capabilities (X'OC') Control Vector
Note:
Do not confuse control vector X'OC' with NOTIFY vector X'OC', which carries
similar information.
0-1
2-m
2

3-4
5-6
7

Vector header; Key=X'OC' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
bits 0-3, (reserved)
bits 4-7, secondary LU capability:
0000 SLU capability is inhibited, sessions can neither be queued
nor started
0001 SLU capability is disabled, sessions can be queued but not
started
0010 reserved
0011 SLU capability is enabled, sessions can be queued or
started
X'OOOl' session limit of 1 (only value allowed for
LU-LU session limit:
peripheral LUs)
LU-LU session count:
the number of LU-LU sessions that are not reset for
this LU, and for which SESSEND will be sent to the SSCP
Reserved

Network Name (X'OE') Control Vector
0-1

2-n
2

3-n

Vector header; Key=X'OE' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Note:
A null X'OE' control vector consists of a vector header with no
vector data.
The length field is set appropriately.
Vector Data
Network name type:
X'Fl' PU name
X'F3' LU name
X'F4' CP name
X'F7' link station name (not network-qualified)
Network-qualified name: a 1- to 17-byte name consisting of an optional
qualifier concatenated to a 1- to 8-byte type-A symbol-string name; when
present, the qualifier contains a 1- to 8-byte type-A symbol-string
network identifier concatenated with a period (when the qualifier is not

Chapter 8.

Common Fields

8-5

Control Vectors
present, the period is omitted). The network-qualified name appears, for
example, as follows:
NETlD.NAME, with no imbedded blanks and with
optional (but not significant) trailing blanks.

Product set ID (X'10') Control Vector
0-1
2-n
2
3-n

Vector Header; Key=X'IO' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
Retired
Network product identifier: one or two Product Identifier (X'll') MS
common subvectors, as described in "MS Common Subvectors" on page 8-104 ,
one for each hardware product and software product in the implementation
of the node

XID Negotiation Error (X'22') Control Vector
0-1
2-n
2-3
4(=n)

Vector header; Key=X'22' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
Error byte offset:
the binary offset (zero-origin in the XID information
field) of the first byte of the field in error
Error bit offset:
the binary offset (zero-origin in the byte pointed to
in the Error Byte Offset field) of the first bit of the field in error

COS/TPF (X'2C') Control Vector
0-1
2-m
2

3

4-m

Vector header; Key=X'2C' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
bits 0-4, reserved
bit 5, network priority indicator:
o PIUs for this session flow at the priority specified in the
Transmission Priority field (bits 6-7).
1 PIUs for this session flow at network priority, which is the
highest transmission priority.
bits 6-7, transmission priority (reserved if byte 2, bit 5 = 1):
00 low priority
01 medium priority
10 high priority
11 reserved
length of COS Name field
COS name:
0 to 8 type-A symbol-string characters with optional (but not
significant) trailing blanks

Mode (X'2D') Control Vector
0-1
2-n

2
3-n

Vector header; Key=X'2D' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
length of Mode Name field
Mode name:
0 to 8 type-A symbol-string characters with optional (but not
significant) trailing blanks

Extended Sense Data (X'3S') Control Vector
0-1
2-p

8-6

Vector header; Key=X'35' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data

SNA Formats

Control Vectors
2-5

Sense data
Note: The shorter abbreviated form (now retired) of the control vector
ends here.

6-p
6

Extended Sense Information
bit 0, RU information included:
o RU information not included (bits 1-2 set to 00 and bytes 8-m
are not included)
1 RU information included (see bytes 8-m below)
bits 1-2, RU category (reserved when bit 0 = 0):
00 FMD
01 NC
10 DFC
11 SC
bit 3, reserved
bit 4, generator of Extended Sense Data control vector (reserved when
Termination Procedur~ Origin Name field not present):
o the termination procedure origin
1 a node other than the termination procedure origin
bit 5, contents of Termination Procedure Origin Name field (reserved when
Termination Procedure Origin Name field not present):
o termination procedure origin name
1 name of node other than termination procedure origin, as
described below; termination procedure origin name not known
bits 6-7, reserved
length of RU Identifier field (set to 0 when byte 6, bit 0 = 0)
RU identifier:
request code or NS header (If present, this field
identifies the request or response that triggered the generation of the
Extended Sense Data control vector.)
Note:
The longer abbreviated form of the control vector ends here.

7

8-m

m+l
m+2-n

n+l

length of Termination Procedure Origin Name field (values 3 to 26 are
valid)
Termination procedure origin name:
if the field contains the termination
procedure origin name (see byte 6, bit 5), network-qualified name of the
node that caused the session termination procedure to be executed;
otherwise, the network-qualified name of the node that generated the
Extended Sense Data control vector, with, when available, a local or
network name that indicates the direction from which the RU signaling the
termination procedure was received
Note ~ When the termination procedure origin is a CP, the
network-qualified CP name is used (e.g., NETID.CPNAME); when the
termination procedure origin is an SSCP and a T41T5 node caused the CP to
begin session ~ermination, the T41T5 name is included in the Related
Resource Name field; when a boundary function is the termination procedure
origin, the network-qualified BF PU name is used; when a boundary function
generates the Extended Sense Data control vector, but the termination
procedure origin name is unknown, the adjacent link station name is
appended to the network-qualified PU name with a period as the separator
(e.g., NETID.PUNAME[.AlSNAME]).
Note 2: The network identifier is always included in the termination
procedure origin name.
length of Related Resource Name field (values 0 to 17 are valid)

Chapter 8.

Common Fields

8-7

Control Vectors
n+2-p

Related resource name:
the name of a related resource used to identify
the source of the error (for example, the name of the PU that rejected the
RNAA for an address assignment error reported cross-domain)
Note: The name always belongs to the same network as the termination
procedure origin name;
therefore, the network identifier is not included.

Fully-qualified PCID (X'&O') Control Vector
0-1
2-n
2-9
10
Il-n

8-8

Vector header; Key=X'60' (see "Substructure Encoding/Parsing Rules" on
page 8-2)
Vector Data
PCID: a unique value used as a procedure identifier
Length of Network-Qualified CP Name field (values 3 to 17 are valid)
Network-qualified CP name (network identifier present)

SNA Formats

Session Keys

SESSION KEY
The following table shows, by key value, the session key and the message-unit
structures that can carry the session key.

Key

Session Key

X'OI' Network or Uninterpreted Name
X'OA' URC

Applicable Message-Unit Structures
TERM-SELF
TERM-SELF

The session keys are defined as follows, with zero-origin indexing of the key
bytes--see the individual RU description for the actual displacement within the RU.

Network or Uninterpreted Name (X'OI')

o
I

2
3-n

Key:
X'OI'
Type:
X'F3' logical unit
Length, in binary, of name
Network or Uninterpreted Name
Note:
For a Network Name session key, the name is a symbolic name; for an
Uninterpreted Name session key, the name is any EBCDIC character string.

URC (X'OA')

o
I

2-n

Key:
X'OA'
Length, in binary, of the URC
URC:
LU-defined identifier

Chapter 8.

Common Fields

8-9

MS Major Vectors

MS MAJOR VECTORS AND UNIQUE SUBVECTORS

INTRODUCTION

The following table shows, by key value, the MS major vectors that NMVT can carry.

Key

MS Major Vector

X'OOOO' Alert
X'0080' RTM
X'8080' Request RTM
Note:

The major vectors are defined as follows (using zero-origin indexing):

•

The description of each major vector includes a matrix indicating the subvectors
that may be included within it.

•

Subvectors with keys X'80' through X'FE' have a meaning that is unique to the
major vector 1n which they are used.
They are defined following each major
vector.

•

Subvectors with keys X'OO' through X'7F' are referred to as common subvectors.
Their meaning is independent of the major vector in which they are used.
They
are defined in "MS Common· Subvectors" on page 8-104.

•

Subvectors may appear in any order within a major vector unless otherwise
stated.

8-10

SNA Formats

MS Major Vectors

MS Major vector Formats
Alert (X'OOOO') MS Major Vector
pu-->SSCP
This major vector provides unsolicited notification of a
problem
or
impending
problem,
type
of
problem,
identification of the cause, and identification of the
component that caused the problem.
0-1
2-3
4-n

Length (n+l), in binary, of this MS major vector
Key:
X'OOOO'
MS subvectors, as described (using zero-origin indexing) in "MS Common
Subvectors" on page 8-104 for subvector keys X'OO' - X'7F', and in "Alert
MS Subvectors" on page 8-14 for subvector keys X'80' - X'FE'.
Note:

The following subvector keys may be used as indicated:

Chapter 8.

Common Fields

8-11

MS Major Vectors

Subvector

Text Message (X'OO')

o

Note 1

Date/Time (X'Ol)

CP

Note 2

Hierarchy Name List (X'03')

CP

Note 3

SNA Address List (X'04')

CP

Note 4

Hierarchy/Resource List (X'OS')

CP

Note 5

pen)

Note 6

Product Set ID (X'lO')
Self-Defining Text Msg. (X'31')

0

Relative Time (X'42')

CP

Note 7

LAN Link Connection
Subsystem Data (X'Sl')

CP

Note a

LCS Configuration Data (X'S2')

CP

Note 9

SDLC Link Station Data (X'aC')

CP

Note 10

Basic Alert (X I 91')

o

Note 11

Generic Alert Data (X'92')

P

Probable Causes (X'93')

P

User Causes (X I 94')

CP

Note 12

Install Causes (X'9S')

CP

Note 12

Failure Causes (X'96')

CP

Note 12

Cause Undetermined (X'97')

CP

Note 13

Detailed Data (X'9a')

o

Detail Qualifier
(X'AO' or X'AI')

P
pen)
CP

a-12

Presence in NMVT
Alert (X'OOOO')
Major Vector

O(n)

Present one time
Present one or more times
Conditionally present one time
conditions.)

SNA Formats

Note 14

(See Notes for

MS Major Vectors

o

Optionally present one time
Optionally present one or more times

O(n)

Notes:
1.

This subvector may be optionally included by an Alert sender, to
transport text in a single Alert major vector that can be processed by
both a non-generic Alert and a generic Alert focal point.
If this
subvector is present, the X'9l' subvector must also be present.

2.

If the PU sending the Alert major vector has the capability of
providing it, it places this subvector in the NMVT.
See Note 7.

3.

This subvector may be optionally included in the NMVT by an Alert
sender in order to create a single Alert major vector that can be
processed by both a non-generic Alert and a generic Alert focal point.
When it is present, this subvector identifies an origin of the Alert
condition that is not an SNA network addressable unit.
If this
subvector is present, the X'9l' subvector must also be present.

4.

This subvector is present when it is necessary to identify, with an
SNA address, the origin of the Alert condition.
If the origin of the
Alert condition is the PU sending the Alert, this subvector is not
present.

5.

This subvector 1S present in
the SNA Address List (X'04')
PU sending the Alert) of the
the SNA Address List (X'04')

6.

An instance of this subvector describing the PU sending the Alert is
always present. A second instance is present if the origin of the
Alert condition is a hardware or software product, and is not the PU
sending the Alert.
If a second instance is present, it is placed
immediately after the first instance of the X'lO' subvector.

the NMVT instead of, or in addition to,
subvector if the origin (other than the
Alert condition cannot be represented in
subvector.

In an Alert containing two instances of the Product Set ID subvector,
the following terms refer, respectively, to these two instances:
•

"Alert Sender PSID" identifies the PU sending the Alert

•

"Indicated Resource PSID" identifies the resource on which the
Alert is reporting

In an Alert with only one instance of the Product Set ID, this
instance is referred to both as the Alert Sender Product Set ID and as
the Indicated Resource Product Set ID.
7.

If the PU sending the Alert cannot provide a Date/Time (X'Ol')
subvector, it places this subvector in the NMVT instead.

8.

This subvector is present when the Alert reports an error on a LAN,
and the node sending the Alert is attached to the LAN.

Chapter 8.

Common Fields

8-13

MS Major Vectors
9.

This subvector is present when the Alert reports a problem with a
logical link using the SDLC or LAN LLC protocol.

10. This subvectoris present when the Alert reports a problem with a
logical link using the SDLC or LAN LLC protocol.
11. This subvector may be optionally included by an Alert sender in order
to create a single Alert major vector that can be processed by both a
non-generic Alert and a generic Alert focal point.
12. Any or all of these subvectors are present in an Alert, depending on
the probable causes of the Alert condition identified by the Alert
sender.
13. This subvector is present in an Alert if and only if none of the
X'94', X'9S', and X'96' subvectors is present.
14. Up to a total of three instances of these subvectors may be optionally
included by an Alert sender, in order to create a single Alert major
vector that can be processed by both a non-generic Alert and a generic
Alert focal point.
If either of these subvectors is present, the
X'91' subvector is also present.

Alert MS Subvectors
SDLC Link Station Data (X'SC') Alert MS Subvector
This subvector transports SOLC
failure information.

o
1

2-p

or LAN

LLC link

station

Length Cp+l), in binary, of the SOLC Link Station Oata subvector
Key:
x'ac'
Subfields containing SOLC link station data Clisted by key value below and
described in detail following):
X'Ol'
X'02'
X'03'
X'04'
X'OS'
X'06'
X'07'
X'08'

Current NCS)/NCR) Counts
Outstanding Frame Counts
Last SOLC Control Field Received
Last SOLC Control Field Sent
Sequence Number Modulus
Link Station State
LLC Reply Timer Expiration Count
Last Received NCR) Count

Current N(S)/N(R) Counts (X'Ol') SOLC Link Station Data Subfield
This subfield transports the current
for a link station.

o
1

2

8-14

NCS) and NCR) counts

Length Cq+l), in binary, of the Current NCS)/NCR) Counts subfield
Key:
X'Ol'
NCS) count, in binary

SNA Formats

MS Major Vectors
3(=q)

N(R) count, in binary

outstanding Frame Count (X'02') SDLC Link Station Data Subfield
This subfield transports the outstanding frame count.

o
1
2(=q)

Length (q+l), in binary, of the Outstanding Frame Count subfield
Key:
X'02'
Outstanding frame count, in binary

Last SDLC Control Field Received (X'03') SDLC Link Station Data Subfield
This subfield
received from
occurred.

o
1
2-3(=q)

transports the last SDLC control
the secondary station before the

field
error

Length (q+l), in binary, of the Last SDLC Control Field Received subfield
Key:
X'03'
Last SDLC control field received; if the SDlC control is only one byte
long then byte 3 value is X'OO'.

Last SDLC Control Field sent (X'04') SDLC Link Station Data Subfield
This subfield transports the last SDLC control field sent
to the secondary station before the error occurred.

o
1

2-3(=q)

Length (q+l), in binary, of the Last SDLC Control Field Sent subfield
Key:
X'04'
Last SDLC control field sent; if the SDLC control is only one byte long
then byte 3 value is X'OO'.

Sequence Number Modulus (X'OS') SDLC link Station Data Subfield
This subfield transports the modulus
number for the link station.

o
1

2(=q)

sequence

Subfie~d

This subfield indicates busy conditions
remote link station.

o

the

Length (q+l), in binary, of the Sequence Number Modulus subfield
Key: X'OS'
Modulus, in binary

Link Station state (X'OO') SDLC Link Station Data

1
2(=q)

of

at the

local or

Length (q+l), in binary, of the Link Station State subfield
Key: X'06'
Link station states:
bit 0, state of the local link station:

Chapter 8.

Common Fields

8-15

MS Major Vectors

o local link station not busy
1 local link station busy (RNR sent)
bit 1, state of the remote link station:
o remote link station not busy
1 remote link station busy (RNR received)
bits 2-7, reserved
LLC Reply Timer Expiration Count (X'07') SDLC Link Station Data Subfield
This subfield transports the number of times the LLC Reply
Timer (Tl) expired.

o
1
2-3

Length (q+l), in binary, of the LLC Reply Timer Expiration Count subfield
Key:
X'07'
Count, in binary, of LLC Reply Timer (TI) expirations

Last Received N(R) Count lX'08') SDLC Link Station Data Subfield
This subfield
count.

o
1
2(=q)

transports the most recently

received N(R)

Length (q+l), 1n binary, of the Last Received N(R) Count subfield
Key:
x'oa'
N(R) count, in binary

Basic Alert (X'91') Alert MS Subvector
This subvector transports Alert
index to predefined screens.

o
1

2

3

8-16

information, including an

Length (p+l), in binary, of the Basic Alert subvector
Key:
X'91'
Flags:
bit 0, initiation indicator:
o Alert not directly initiated by an operator action
1 Alert initiated by an operator action
bit 1, held-Alert indicator:
o Alert was sent when the problem was detected.
1 Alert condition was detected earlier, but the Alert was not sent
at that time because no session was available to send it on.
bits 2-3, reserved
bits 4-7, retired
Alert type:
X'OI' permanent loss of availability: a loss of availability to the end
user that is not recovered from without intervention external to the
reporting product
X'02' temporary loss of availability: a momentary loss of availability
that will probably be noticed by the end user, yet is recovered from
without intervention external to the reporting product
X'03' performance: a recognized measurement of response time has exceeded
a predetermined threshold

SNA Formats

MS Major Vectors

4

X'04' operator intervention required:
the intervention of an operator is
required to restore proper operational capability to the resource
X'05'-X'09' retired
X'OA' notification: a loss of availability to the end user is impending
but has not yet happened
X'OB'-X'OE' retired
X'OF' delayed:
the sender is reporting a previously detected alertable
condition that prevented reporting when detected
indicates the general classification and cause of the
General cause code:
exception condition:
X'Ol' hardware or microcode (not distinguished):
the Alert condition was
caused by either a hardware (machine or equipment) failure, or a
microcode failure, but the specific cause cannot be determined.
X'02' software: the Alert condition was caused by a software
(programming) failure or malfunction.
X'03' retired
X'04'-X'05' reserved
X'06' media (e.g., tape, disk, diskette, paper): a failure, imperfection,
or defect in the media
Note: This code is used for cases where a particular area of a
tape, disk or diskette cannot be read or written but other areas are
operational.
It is also used for torn or jammed forms or paper.
It
is not used for cases where the medium is not present or the wrong
medium, e.g., the wrong size forms, are present; these cases are
indicated by X'17' (operator intervention required).
X'07' hardware or software (not distinguished):
the Alert condition was
caused by either a hardware (machine or equipment) failure, or a
software (programming) failure but the specific cause cannot be
determined.
X'08'-X'09' retired
X'OA' media or hardware (not distinguished):
the Alert condition was
caused by either a hardware (machine or equipment) failure, or a
failure, imperfection, or defect in the media, but the specific
cause cannot be determined.
X'OB' hardware:
the Alert condition was caused by a hardware (machine or
equipment) failure or malfunction.
X'OC' microcode:
the Alert condition was caused by a microcode failure or
malfunction.
Note: This code is not used for ROS chips that are packaged in
field replaceable units (FRUs) or customer replaceable units (CRUs)
and are serviced in the same manner as hardware logic is serviced.
X'OB' (hardware) is used in those cases.
X'OD' protocol above link level: the Alert condition was caused by an SNA
protocol error.
Note: This code point reports protocol errors that are caused by
incorrect programming, for example, failure to include a BB bit on
the first RU when in BETB state on a session that uses bracket
protocol.
X'OE' link-level protocol:
the Alert condition was caused by a link-level
protocol error.
Note:
Errors such as send/receive count errors that can be caused
by missing a message because line hits do not fall into this
category; they are indicated by X'OB' (hardware).

Chapter 8.

Common Fields

8-17

MS Major Vectors

5-6

8-18

X'OF' undetermined:
the cause of the Alert condition cannot be
determined.
X'lO' external facilities change or restriction:
the number called is
temporarily unobtainable.
Note: This code point is used by X.21 networks.
X'll' user:
the Alert condition was caused by an incorrect action taken
by a user.
Note:
Unavailability due to a device being varied offline does not
fall into this category; it is indicated by X'13' (component
offline).
X'12' system generation, customization, or installation consistency
problem: the Alert condition was caused by an invalid system
definition or customizing parameter, or by a mismatch between a
system definition or customizing parameter and the hardware.
Note: This code is used only in those cases that typically are not
corrected by the action of the local operator.
the Alert condition was caused by a component
X'13' component offline:
being offline.
X'14' component busy:
the Alert condition was caused by a component being
busy.
X'15' external power failure:
the Alert condition was caused by an
external power failure.
X'16' thermal problem:
the Alert condition was caused by temperature that
is not within recommended specifications.
X'I7' operator intervention required:
the Alert condition was caused
because action is required by an operator.
Note:
Unattended devices will always Alert when operator
intervention is required. Attended devices will not Alert until the
local operator has time to perform the required action.
After the
device-allocated time has expired for attended devices, the device
has the optio~ of sending an Alert.
X'I8' microcode or software (not distinguished):
the Alert condition was
caused by either a software (programming) failure or malfunction or
a microcode failure but the specific cause cannot be determined.
Specific component code:
indicates the generic type of component,
subcomponent, or logical resource that can be most closely related to the
exception condition. The component indicated may be the generic type of
the "target" or it may be a subcomponent of the target. The terms "local"
and "remote" used below, refer to the perspective of the Alert originator.
Defined codes are:
X'OOOI' base processor
X'0002' service processor
X'0003' reserved
X'0004' main storage
X'0005' disk device
X'0006' printer
X'0007' card reader and/or punch
X'0008' tape device
X'0009' keyboard
X'OOOA' selector pen
X'OOOB' magnetic stripe reader
X'OOOC' display/printer
X'OOOD' display device

SNA Formats

MS Major Vectors
X'OOOE' remote product:
used when a product to which the Alert generator
is linked (in any form) has caused an Alert condition and the
generic product type cannot be determined
X'OOOF' power supply internal to this product
X'OOIO' I/O attached controller
X'OOII' communication controller scanner
X'OOI2' communication link adapter
X'OOI3' reserved
X'OOI4' channel adapter
X'OOI5' loop adapter
X'OOI6' adapter for directly attaching devices
X'OOI7' reserved
X'OOIB' channel (direct memory access channel)
X'OOI9' link:
used only when common-carrier equipment cannot be
distinguished from customer equipment
X'OOIA' link:
common-carrier equipment
X'OOIB' link:
customer equipment
X'OOIC' loop:
used only when common-carrier equipment cannot be
distinguished from customer equipment
X'OOID' loop:
common-carrier equipment
X'OOIE' loop:
customer equipment
X'OOIF' X.21 link connection external to this product
X'0020' X.25 network connection external to this product
X'0021' local X.21 interface (DTE-DCE)
X'0022' local X.25 interface (DTE-DCE)
X'0023' local modem
X'0024' remote modem
X'0025' local modem interface (DTE-DCE)
X'0026' remote modem interface (DTE-DCE)
X'0027' local modem link monitor
X'002B' remote modem link monitor
X'0029' local modem link monitor interface
X'002A' remote modem link monitor interface
X'002B'-X'0031' reserved
X'0032' remote modem or modem interface or remote product
X'0033' transmission medium or remote modem
X'0034' SDLC data link control component
X'0035' BSC data link control component
X'0036' start/stop data link control component
X'0037'-X'0043' reserved
X'0044' cluster controller or device
X'0045' local link monitor or modem interface
X'0046' reserved
X'0047' card reader/punch or display/printer
X'004B' controller application program
X'0049' keyboard or display
X'004A' storage control unit
X'004B' storage control unit or storage control unit channel
X'004C' storage control unit or controller
X'004D' control unit (other than storage control unit)
X'004E'-X'0051' reserved
X'0052' maintenance device
X'0053' maintenance device interface
X'0054' reserved

Chapter B.

Common Fields

B-19

MS Major Vectors

7-8

9-10

11-12

13(=p)

X'0055' control program
X'0056' application subsystem on top of control program
X'0057' telecommunication access method
X'0058' application program (other than application subsystem)
X'0059' communication controller program
X'005A'-X'005F' reserved
X'0060' X.25 network interface: DCE to first interface node in X.25
network
X'0061' disk device with nonremovable media
X'0062' disk device with removable media
X'0063' control tailed modem
X'0064' reserved
X'0065' remote tailed modem
X'0066' remote tailed modem interface
X'0067' sensor I/O unit
X'0068' magnetic stripe reader/encoder
X'0069' check (bank) reader
X'006A' document feed mechanism
X'006B' coin feed mechanism
X'006C' envelope depository
X'006D' timer adapter
X'006E' encryption/decryption adapter
X'006F' outboard, user programmable processor
X'0070' cable connecting local device to local adapter
X'0071'-X'007F' reserved
X'0080' token-ring LAN error
X'0081' Carrier Sense Multiple Access (CSMA/CD) LAN error
X'0082'-X'00FE' reserved
X'OOFF' undetermined (the problem cannot be isolated to one of the above
generic component types)
Alert description code: a code that provides an index to predefined text
that explains the condition that caused the Alert
Note:
This field is product dependent.
User Action Code: a code that provides an index to predefined screens
that can include predefined text and variable fields for MS User Action
Qualifier subvectors
Note:
This field is product dependent.
Detail text reference code: a code that provides an index to predefined
screens that can include predefined text and variable fields for MS Detail
Qualifier subvectors
Note:
This field is product dependent.
Retired

Generic Alert Data (X'92') Alert MS Subvector
This subvector transports Alert information in the form of
code points that correspond to strings of text stored at
the Alert receiver.
It also transports an Alert ID Number
that uniquely identifies a particular Alert.

o
1

2-3

8-20

Length (p+l), in binary, of the Generic Alert Data subvector
Key:
X'92'
Flags:
bit 0, initiation indicator:

SNA Formats

MS Major Vectors

4

o Alert not directly initiated by an operator action
1 Alert initiated by an operator action
bit I, held Alert indicator:
o Alert was sent when the problem was detected.
1 Alert condition was detected earlier, but the Alert was not sent
at that time because no session was available to send it on.
bit 2, delayed Alert indicator:
o Sender is not reporting a previously detected Alert condition
that prevented reporting when detected.
1 Sender is reporting a previously detected Alert condition that
prevented reporting when detected.
Note:
If the delayed Alert indicator is set to I, the held Alert
indicator is also set to 1.
bits 3-15, reserved
Alert type: a code point indicating the severity of the Alert condition:
X'OI' permanent loss of availability: a loss of availability to the end
user that is not recovered from without intervention external to the
reporting product
X'02' temporary loss of availability: a momentary loss of availability
that will probably be noticed by the end user, yet is recovered from
without intervention external to the reporting product
X'03' performance:
performance below what is considered an acceptable
level
X'II' impending problem: a loss of availability to the end user impending
but that has not yet happened
X'I2' unknown:
the severity of the Alert condition not assessable

5-6

Alert Description Code: A code point that provides an index to predefined
text describing the Alert condition. An Alert receiver has two options
for selecting text to display.
It can display the English text documented
with each code point, or its national language equivalent; or, for a
presentation to an operator of a lower skill level, it can choose the
following simpler text (shown all capitalized), or its national language
equivalent, based only on the first digit of the code point:
X'lxxx'
X'2xxx'
X'3xxx'
X'4xxx'
X'5xxx'
X'6xxx'
X'7xxx'
X'8xxx'
X'9xxx'
X'Axxx'
X'Bxxx'
X'Cxxx'
X'Fxxx'

HARDWARE
SOFTWARE
COMMUNICATIONS
PERFORMANCE
CONGESTION
MICROCODE
OPERATOR
SPECIFICATION
INTERVENTION REQUIRED
PROBLEM RESOLVED
NOTIFICATION
SECURITY
UNDETERMINED

Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order 2-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'

Chapter 8.

Common Fields

8-21

MS Major Vectors
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (corresponding to X'**OO' code points) if
it does not recognize the" more specific code point (e.g., because of
different release schedules).
X'lOOO' EQUIPMENT MALFUNCTION:

An internal machine error has occurred

X'lOOl' CONTROL UNIT MALFUNCTION
X'l002' DEVICE ERROR
Note: This code point is used only if the Alert sender is unable
to determine the nature of the affected device.
X'IOIO' ADAPTER ERROR: A hardware error has occurred in an
adapter, making it inoperable
X'lIOO' INPUT DEVICE ERROR
X'IIOI' MICR READER/SORTER ERROR: An error has been detected in a
magnetic ink character recognition reader/sorter
X'1200' OUTPUT DEVICE ERROR
X'120l' PRINTER ERROR
X'1202' PRINTER CASSETTE ERROR
X'1300' INPUT/OUTPUT DEVICE ERROR
X'130l' LOCAL CONSOLE ERROR
X'1302' REMOTE CONSOLE ERROR
Note: "Local" and "remote" are defined with respect to the system
with which the console communicates.
X'1311' DISK FAILURE: A disk unit is no longer usable
X'1312' DISK OPERATION ERROR: A disk operation has failed, but
the unit may still be usable
X'132l' DISKETTE DEVICE FAILURE: A diskette unit is no longer
usable
X'1322' DISKETTE OPERATION ERROR: A diskette operation has
failed, but the unit may still be usable
X'1331' TAPE DRIVE FAILURE: A tape drive is no longer usable
X'1332' TAPE OPERATION ERROR: A tape operation has failed, but
the tape drive may still be usable
X'1400' LOSS OF ELECTRICAL POWER: A source of electrical power, internal
or external, has been lost
X'1401'
X'1402'
X'1403'
X'1404'
X'14l0'
X'14ll'

8-22

SNA Formats

LOSS OF CHANNEL ADAPTER ELECTRICAL POWER
LOSS OF LINE ADAPTER ELECTRICAL POWER
LOSS OF LIC UNIT ELECTRICAL POWER
LOSS OF MOSS ELECTRICAL POWER
LOSS OF EXTERNAL ELECTRICAL POWER
POWER OFF DETECTED: A network component has detected a
notification signal announcing that the power of another
component was lost or turned off

MS Major Vectors
X'lSOO' LOSS OF EQUIPMENT COOLING OR HEATING:
A loss of equipment cooling
or heating has occurred
Note:
If loss of power has not been ruled out as a cause for the
loss of heating or cooling, then X'1400' (LOSS OF ELECTRICAL
POWER) should be sent instead of this code point.
X'lSOl' LOSS OF EQUIPMENT COOLING
X'lS02' LOSS OF MOSS EQUIPMENT COOLING
X'1600' SUBSYSTEM FAILURE: A failure in a set of components that jointly
provide a specified function; typically a subsystem includes a
controller, one or more interface adapters, physical connection
media, and attached devices
X'1601' STORAGE SUBSYSTEM FAILURE:
A failure in a subsystem that
supports locally-attached storage devices, such as hard
disk (DASD), diskette, and tape
X'1602' WORKSTATION SUBSYSTEM FAILURE:
A failure in a subsystem
that supports workstations directly attached to a node,
i.e., workstations not attached via telecommunications
links
X'1603' COMMUNICATIONS SUBSYSTEM FAILURE: A failure in a
subsystem that supports communication over
telecommunications links; these links may be implemented
via leased telephone lines, an X.2S network, a token-ring
LAN, or otherwise
X'16l1' IMPENDING STORAGE SUBSYSTEM FAILURE
X'16l2' IMPENDING WORKSTATION SUBSYSTEM FAILURE
X'16l3' IMPENDING COMMUNICATIONS SUBSYST FAILURE
X'2000' SOFTWARE PROGRAM ABNORMALLY TERMINATED:
A software program has
abnormally terminated due to some unrecoverable error condition
Note:
See also code point X'6000' (MICROCODE PROGRAM ABNORMALLY
TERMINATED).
X'2100' SOFTWARE PROGRAM ERROR: An error has occurred within a software
program that has caused incorrect results, but the program has not
terminated
Note: See also code point X'6l00' (MICROCODE PROGRAM ERROR).
X'2101' PROGRAM PROCEDURE IS INCORRECT:
A set of instructions
which originated in a computer program and are intended
to direct the operation of a device are incorrect.
X'3000' COMMUNICATION PROTOCOL ERROR: An architecturally defined
communication protocol has been violated
Note:
This code point is not used if one that identifies the
particular protocol involved is available.
X'3100' SNA PROTOCOL ERROR:

An SNA protocol has been violated

X'3110' XID PROTOCOL ERROR:
A protocol error related to XID
exchange has been detected

Chapter 8.

Common Fields

8-23

MS Major Vectors
X'3111' INVALID XID RECEIVED: An XID has been received that
contains either a format error or a value unacceptable to
the receiver
X'3200' LAN ERROR:

An error has been detected on a local area network

X'3203' LOOP ERROR:
An error has been detected on a communication
loop
X'3204' LOOP OPEN
X'3205' LOOP ADAPTER INOPERATIVE
X'3210' INITIALIZATION FAILURE: A LAN adapter has detected a
problem while being initialized
X'3211' OPEN FAILURE: A LAN adapter has detected a problem during
the insertion process; the insertion process did not
complete
X'3212' WIRE FAULT:
An error condition caused by a break in the
wires or a short between the wires (or shield) in a
segment of cable has been detected
Note:
The term "wire fault" applies only to failures on the lobes
of a token-ring LAN.
X'3213' AUTO REMOVAL: A station's adapter has left a LAN
token-ring or bus as part of an automatic-recovery
process.
For token-rings, this process is known as the
beacon automatic-recovery process.
X'3214' REMOVE ADAPTER COMMAND RECEIVED: The reporting station
received a Remove Adapter command from a LAN manager
and, as a result, left the LAN
X'3215' TOKEN RING INOPERATIVE: After the onset of beaconing, a
token-ring attempted and failed auto recovery; the
token-ring has been beaconing for more than 52 seconds,
and is still beaconing
X'32l6' TOKEN-RING TEMPORARY ERROR: The token-ring was in a
beaconing state for less than 52 seconds and then
recovered; the Alert sender has no knowledge whether a
station was removed to bypass the fault or the fault was
temporary
X'3220' CSMA/CD BUS INOPERATIVE
X'3221' CSMA/CD LAN COMMUNICATIONS LOST: A station is unable to
communicate over a CSMA/CD LAN
Note:
The problem may be local to the Alert sender, or it may
apply to the entire bus to which the Alert sender is attached
X'3230' LAN MANAGEMENT DATA LOST: A LAN management server has
become congested or incapacitated so it cannot handle its
data input.
As a result, management data from LAN
stations has been discarded
X'3300' LINK ERROR: An error has occurred on a network communication link
Note: This default code point covers all of the following:
Connections between subarea nodes, connections between subarea
nodes and peripheral nodes, connections between peripheral nodes,
and connections between peripheral nodes and the devices that are
hierarchically below them.
If the link is implemented by a local
area network, one of the X'32xx' code points is used instead.

8-24

SNA Formats

MS Major Vectors
X'330l' REMOTE SUPPORT FACILITY LINK ERROR: An error has occurred
on a communication link with the IBM Remote Support
Facility
X'3302' UNABLE TO COMMUNICATE WITH DEVICE
X'3303' UNABLE TO COMMUNICATE WITH PRINTER
X'3304' UNABLE TO COMMUNICATE WITH DISPLAY
X'330S' UNABLE TO COMMUNICATE WITH REMOTE NODE
X'3310' X.21 ERROR: An error has been detected on a communication
link operating according to the X.21 protocols.
X'331l' X.21 ERROR--SNA SECONDARY: An error has prevented an SNA
secondary link station from establishing an X.21
connection
X'33l2' X.21 ERROR--SNA PRIMARY: An error has prevented an SNA
primary link station from establishing an X.2l connection
X'3313' X.2l CONNECTION CLEARED
X'3320' X.2S ERROR: An error has been detected on a communication
link operating according to the X.25 protocols
X'3330' MANAGEMENT SERVER REPORTING LINK ERROR: A LAN manager has
detected an error on one of its reporting links with a
LAN management server
X'3400' ISDN ERROR: An error has occurred on an Integrated Services
Digital Network (ISDN) connection
X'340l' D-CHANNEL ISDN ERROR
X'3402' B-CHANNEL ISDN ERROR
X'3S00' LOCAL CONNECTION ERROR:
connection

An error has occurred on a local channel

X'3600' LINK CONNECTION ERROR
Note: A 'link connection' includes the interface between the DTE
and the DCE, any protocol used to communicate between the DTE and
the DCE (such as LPDA, the IBM Command Set, the AT Command Set,
etc.) and DCE provided information about the link.
X'3601'
X'3602'
X'3603'
X'3604'
X'360S'
X'3606'
X'3607'
X'3608'
X'3609'
X'360A'
X'360B'
X'360C'
X'360D'
X'360E'
X'360F'
X'3610'
X'361l'
X'3612'

NO LPDA RESPONSE RECEIVED
BAD FCS IN LPDA RESPONSE
INTERFACE ERROR DURING LPDA
CONFIGURATION MISMATCH
MODEM CONFIGURATION ERROR
DSU/CSU CONFIGURATION ERROR
MODEM ERROR
DSU/CSU ERROR
EQUIPMENT INCOMPATIBILITY
MODEM REINITIALIZED
DSU/CSU REINITIALIZED
MODEM FAILURE DETECTED
DSU/CSU FAILURE DETECTED
MODEM SPEEDS MISMATCH
TEST IN PROGRESS
STREAMING DETECTED
DTR DROPPED
EXTERNAL CLOCK NOT RUNNING

Chapter 8.

Common Fields

8-2S

MS Major Vectors
X'36l3'
X'36l4'
X'36lS'
X'36l6'
X'36l7'
X'36l8'
X'36l9'
X'36lA'
X'36lB'
X'36lC'
X'36lD'
X'36lE'
X'36lF'

BAD LINE QUALITY
RLSD OFF DETECTED
EXCESSIVE IMPULSE HITS DETECTED
EXCESSIVE BIPOLAR CODE ERRORS
DCE INTERFACE ERROR
UNEXPECTED RECEIVED CARRIER DETECTED
NO' LINE SIGNAL
OUT OF FRAME RECEIVED BY LOCAL DSU/CSU
OUT OF FRAME RECEIVED BY REMOTE DSU/CSU
OUT OF SERVICE RECEIVED BY LOCAL DSU/CSU
OUT OF SERVICE RECEIVD BY REMOTE DSU/CSU
DDS LOOPBACK DETECTED BY LOCAL DSU/CSU
DDS LOOPBACK DETECTED BY REMOTE DSU/CSU

X'4000' PERFORMANCE DEGRADED: Service or response time exceeds what is
considered an acceptable level
X'4001' EXCESSIVE TOKEN-RING ERRORS: Soft errors are occurring on
a token ring at an excessive rate
Note: The token-ring LAN term "soft error" is defined as an
intermittent error on a network that causes data to have to be
transmitted more than once to be received. The condition
identified by this code point is detected by Ring Error Monitor
(REM); REM also provides a fault domain to indicate the location
of most of the soft errors.
X'4003' EXCESSIVE CONTROL UNIT ERRORS
X'4010' ERROR TO TRAFFIC RATIO EXCEEDED: A computed ratio of
errors to total traffic has exceeded a specified
threshold
X'4021' EXCESSIVE STORAGE SUBSYSTEM ERRORS
X'4022' EXCESSIVE WORKSTATION SUBSYSTEM ERRORS
X'4023' EXCESSIVE COMMUNICATIONS SUBSYST ERRORS
X'SOOO' CONGESTION: A system or network component has either reached its
capacity or is approaching it
X'SOOl' NETWORK CONGESTION: There is excessive traffic in the
network
X'S002' RESOURCE NEARING CAPACITY: A resource is approaching its
capacity; it is still usable, but it threatens to become
unusable unless corrective action is taken
X'S003' CAPACITY EXCEEDED: A request has been received by a
component that, if granted, would require more resources
than the component has available to it
X'S004' OUT OF RESOURCES: A component has no more resources
available; it is no longer able to function
X'SOOS' WORKSTATION LIMIT EXCEEDED: More workstations than the
workstation subsystem supports being powered on have
attempted to power on simultaneously
X'SOlO' COMMUNICATIONS UNDERRUN: A link station element is unable
to write data to an adapter rapidly enough
X'SOll' COMMUNICATIONS OVERRUN: A MAC service user is unable to
read data from an adapter rapidly enough

8-26

SNA Formats

MS Major Vectors
X'SOI2' RECEIVE QUEUE OVERRUN: A receive queue in a node is
unable to receive data from a link station in the node
rapidly enough
X'SOI3' SLOWDOWN:
A device has exhausted its supply of available
buffers and has stopped accepting inbound data until it
can handle all outbound requests
X'S020' FILE NEEDS REORGANIZATION A file is approaching its
capacity, and will soon be unusable unless it is
reorganized
X'6000' MICROCODE PROGRAM ABNORMALLY TERMINATED:
A microcode program has
abnormally terminated due to some unrecoverable error condition
Note:
See also code point X'2000' (SOFTWARE PROGRAM ABNORMALLY
TERMINATED).
X'6100' MICROCODE PROGRAM ERROR:
An error has occurred within a microcode
program that has caused incorrect results, but the program was not
terminated
Note:
See also code point X'2l00' (SOFTWARE PROGRAM ERROR).
X'7000' OPERATOR PROCEDURAL ERROR:
An operator has attempted to initiate
an incorrect procedure, or has initiated a procedure incorrectly
X'7001' RESOURCES NOT ACTIVE: An operator has deactivated, or
failed to activate, resources required for a requested
operation
X'BOOO' CONFIGURATION OR CUSTOMIZATION ERROR:
A system or device
generation or customization parameter has been specified
incorrectly, or is inconsistent with the actual configuration
X'BOOI' CUSTOMIZATION IMAGE WARNING:
A customization image
parameter is incorrect and has been replaced by a valid
value.
X'9000' OPERATOR INTERVENTION REQUIRED:
A condition has occurred
indicating that operator intervention is required, and an operator
has not responded
Note: The X'90xx' code points are used only for conditions that
(1) require on-site intervention, and (2) can be resolved by
personnel that do not possess a high level of technical skill.
X'9001'
X'9002'
X'9003'
X'9004'
X'900S'
X'9010'

PRINTER RIBBON JAM
PAPER JAM
BILL/DOCUMENT JAM
COIN JAM
FILM/VIDEOTAPE NOT MOVING
DEVICE NOT READY: A device has indicated that it is not
ready for use, due to an unspecified
intervention-required condition
X'9011' PRINTER NOT READY:
A printer has indicated that it is not
ready for us~, due to an unspecified
intervention-required condition
X'9030' OUT OF FOCUS

Chapter 8.

Common Fields

8-27

MS Major Vectors
X'9031' SERVICE DOOR OPENED
Note:
Security and/or safety considerations may preclude normal
operation until the door is closed.
X'9100' STOCK LOW:
The stock of some required material (e.g., paper, ink,
coins) is low, but is not yet exhausted
X'9101'
X'9102'
X'9103'
X'9104'
X'910S'
X'9106'
X'9107'
X'9108'
X'9109'

LOW ON INK
LOW ON PAPER
LOW ON BILLS/DOCUMENTS
LOW ON COINS
LOW ON FILM/VIDEOTAPE
LOW ON TONER
LOW ON FUSER OIL
LOW ON STAPLES
DISKETTE FILE NEARLY FULL: An output file being written
to a diskette is almost full. Continued operation may
result in the file becoming full, which may result in
abnormal operation of the device.

X'9200' STOCK EXHAUSTED:
The stock of some required material (e. g. ,
paper, ink, coins) has been exhausted
X'920l'
X'9202'
X'9203'
X'9204'
X'920S'
X'9206'
X'9207'
X'9208'

OUT
OUT
OUT
OUT
OUT
OUT
OUT
OUT

OF
OF
OF
OF
OF
OF
OF
OF

INK
PAPER
BILLS/DOCUMENTS
COINS
FILM/VIDEOTAPE
TONER
FUSER OIL
STAPLES

X'9300' DEPOSITORY FULL:
A depository has become full, and thus cannot
receive any more deposits
X'930l' DEPOSITORY APPROACHING CAPACITY:
A depository is nearing
its capacity; if it is not emptied shortly, it will
become completely filled
X'AOOO' PROBLEM RESOLVED:
A problem has been resolved
Note:
The problem may have been reported earlier by an Alert.
X'AOOI' IMPENDING COOLING PROBLEM RESOLVED:
An impending cooling
problem, reported earlier by an Alert, has been resolved
without ever having impacted the availability of any
resource
X'BOOO' OPERATOR NOTIFICATION:
Problem-related information is being
conveyed to a network operator
Note:
A X'Bxxx' code point is used only if no more specific one
is available.
X'BOOI' MAINTENANCE PROCEDURE:
for maintenance

8-28

SNA Formats

A resource has been taken offline

MS Major Vectors
Note:
This code point is used to notify a network operator about
a disruptive maintenance procedure that was invoked locally;
otherwise, there would be an unexplained loss of a resource.
X'B002' OPERATOR TOOK PRINTER OFFLINE
X'B003' LAN BRIDGE TAKEN OFFLINE
X'COOO' SECURITY EVENT:
An event indicative of a possible security
exposure has been detected
X'COOl' INVALID REPORTING LINK PASSWORD
X'C002' UNAUTHORIZED LAN INSERTION ATTEMPTED
X'EOOO'-X'EFFF' Reserved
Note:
This range of code points is reserved for use by
non-IBM products and customer written applications.
No
IBM product will send a code point from within this range.
X'FEOO' UNDETERMINED ERROR:
An error condition has occurred that cannot
be related to a more specific error category
X'FEOl' RESOURCE UNAVAILABLE:
A resource has become unavailable,
but the Alert sender has no indication of why this has
happened
Note:
This code point should be used only if the Alert sender
cannot determine, with any degree of certainty, that another Alert
description code is applicable to the event being reported.
7-10(=p)

Alert ID number:
Stage 1:
vector:

•
•

•
•
•
•
•
•
•

A 4-byte hexadecimal value computed as follows:

Assemble (in order) the following input from the Alert major

Alert Type
Alert Description Code code point
All Probable Causes code points, in order
The delimiter X'FFFF'
All User Causes code points, in order, if any are present
The delimiter X'FFFF'
All Install Causes code points, 1n order, if any are present
The delimiter X'FFFF'
All Failure Causes code points, in order, if any are present

Stage 2:

Apply to this input the 32 bit CRC algorithm:
R(X)

=
G(X)

Q(X)+
G(X)

where I(X) = the polynomial represented by the input (with the convention
that the first bit of the input represents the coefficient of this
polynomial's highest order term), L(X) = the polynomial X**3l + X**30 +
... + X + 1 (i.e., the polynomial represented by 32 l's), k = the number
of bits in the input, and G(X) = the generator polynomial X**32 + X**26 +
X**23 + X**22 + X**16 + X**12 + X**ll + X**lO + X**8 + X**7 + X**5 + X**4

Chapter 8.

Common Fields

8-29

MS Major Vectors
+ X**2 + X**l + 1. The Alert ID number is defined to be the complement of
the number representing the remainder polynomial R(X).

Probable Causes (X'93') Alert MS Subvector
This subvector contains one or more code points denoting
probable causes of the Alert condition. The probable
causes appear in order of decreasing probability.

o
1
2-p

Length (p+l), in binary, of the Probable Causes subvector
Key:
(X'93')
One or more two-byte probable cause code points, defined below.
Each code
point provides an index to predefined text denoting the probable cause.
An Alert receiver has the option of displaying, for each code point it
receives:
either the text associated with that code point, or its
national language equivalent; or the text associated with the default code
point (not indented) above it, or its national language equivalent.
Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order 2-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (correspon~ing to X'**OO' code points) if
it does not recognize the more specific code point (e.g., because of
different release schedules).
X'OOOO' PROCESSOR:
The equipment used to interpret and process programmed
instructions. These instructions may be programmed in either
software or microcode
X'OOOl' MOSS (Maintenance and Operation Subsystem): A service
processor for a communication controller
X'0003' PROCESSOR SWITCH: A component within a hardware product
used to switch buses and the resources attached to them
among processors
X'0004' CONTROL PANEL
X'OOOS' SYSTEM I/O BUS
X'OOlO' LAN MANAGER: A network component responsible for managing
a local area network
X'OOll' PRINTER SERVER: A network component that controls the
operation of a printer
Note:
In the current implementation, the printer server is a PC
that stands between a printer and the host applications that
communicate with it.
X'0030' SYSTEM MICROCODE: The specific microcode was not
identified.
X'003l' SYSTEM STORAGE MICROCODE
Note:
See also code point X'042l' (STORAGE CONTROLLER MICROCODE)
X'0032' SYSTEM DISPLAY MICROCODE
Note:
See also code point X'0422' (WORKSTATION CONTROLLER
MICROCODE)
X'0033' SYSTEM COMMUNICATION MICROCODE

8-30

SNA Formats

MS Major Vectors
Note:
See also code point X'0423' (COMM SUBSYSTEM CONTROLLER
MICROCODE)
X'0034' SYSTEM PRINTER MICROCODE
Note:
See also code point X'0422' (WORKSTATION CONTROLLER
MICROCODE)
X'OlOO' STORAGE:
The random access memory (RAM) or read only memory (ROM)
accessible by a processor and by peripheral devices
X'OlOl' MAIN STORAGE: Storage from which instructions and other
data can be loaded directly into registers for subsequent
execution or processing
X'Ol02' AUXILIARY STORAGE:
Storage that can not be directly
addressed by a processor, such as external or secondary
storage
X'Ol03' NON-VOLATILE STORAGE
X'0200' POWER SUBSYSTEM: The subsystem within a hardware product that
provides electrical power to the different components within the
product that require it
X'0201' INTERNAL POWER UNIT:
An element of the power subsystem
providing electrical power to a specific component
X'0202' INTERNAL POWER CONTROL UNIT:
An element of the power
subsystem that controls the internal power units
X'0203' POWER CABLE
X'0204' POWER CORD
X'0205' POWER SUBSYSTEM PROCESSOR:
A processor within the power
subsystem responsible for its operation
X'0210' BATTERY
X'0211' MOSS BATTERY
X'0220' MAIN AC POWER SUPPLY
X'0300' COOLING OR HEATING SUBSYSTEM:
The subsystems within a hardware
product responsible for maintaining a temperature at which the
product can operate
X'0301' COOLING FAN
X'0310' AIR FLOW DETECTOR
X'0311' THERMAL DETECTOR
X'0400' SUBSYSTEM CONTROLLER: A unit within a subsystem that interfaces
between a processor and the devices in the subsystem
Note:
See Alert Description X'1600', SUBSYSTEM FAILURE, for
descriptions of the particular subsystems mentioned here
X'0401' STORAGE CONTROLLER
Note:
This code point is contrasted with X'3131', DASD CONTROL
UNIT and X'3l32', TAPE CONTROL UNIT.
A storage controller is
typically a component within a larger node that provides for the
node's communication with a variety of storage devices; a DASD or
tape control unit is typically a separate device providing
communication with storage devices.
X'0402' WORKSTATION CONTROLLER

Chapter 8.

Common Fields

8-31

MS Major Vectors
X'0403' COMMUNICATIONS SUBSYSTEM CONTROLLER
Note:
This code point should be contrasted with X'3111',
COMMUNICATION CONTROLLER.
A communication controller is typically
a stand-alone node within a network, for example, a 3725; a
communications subsystem controller is typically a component
within a larger node that provides for the node's communication
with nodes remote from it.
X'0421' STORAGE CONTROLLER MICROCODE
X'0422' WORKSTATION CONTROLLER MICROCODE
X'0423' COMM SUBSYSTEM CONTROLLER MICROCODE
X'0441' STORAGE CONTROLLER INTERFACE:
The interface between a
storage controller and the main processor in its node
X'0442' WORKSTATION CONTROLLER INTERFACE:
The interface between a
workstation controller and the main processor in its node
X'0443' COMM SUBSYSTEM CONTROLLER INTERFACE: The interface
between a communications subsystem controller and the
main processor in its node
X'0500' SUBSYSTEM: A set of components that jointly provide a specified
function; typically a subsystem includes a controller, one or more
interface adapters, physical connection media, and attached
devices
Note:
See Alert Description X'1600', SUBSYSTEM FAILURE, for
descriptions of the particular subsystems mentioned here
X'0501' STORAGE SUBSYSTEM
X'0502' WORKSTATION SUBSYSTEM
X'0503' COMMUNICATIONS SUBSYSTEM
X'IOOO' SOFTWARE PROGRAM:
A program implemented in software, as
distinguished from one implemented in microcode
Note:
For this code point, and for the replacement code points
under it, an Alert receiver has two options:
It may ~isplay the
English text (or its national language equivalent) dobumented with
the code points, or it may display the software produ~t common
name from the first software Product Identifier (X'll') subvector
within the indicated resource Product Set ID.
X'IOOI' APPLICATION PROGRAM:
A program written for or by a user
that applies to the user's work.
A program used to
connect and communicate with devices in a network,
enabling users to perform application-orientated
activities
X'IOIO' HOST PROGRAM:
A program running in a host processor that
is a primary or controlling program in a system
X'IOII' PRINTER SERVER PROGRAM:
A program running in a printer
server that controls a printer
Note:
See also Probable Cause X'OOII' (PRINTER SERVER).
X'1020' CONTROL PROGRAM:
A computer program designed to schedule
and supervise the execution of programs in a computer
system
X'1021' COMMUNICATION CONTROLLER CONTROL PROGRAM:
A software
program designed to schedule and supervise the execution
of programs in a communication controller

8-32

SNA Formats

MS Major Vectors
X'1022' COMMUNICATIONS PROGRAM: A software program designed to
provide direct assistance to a node in communicating with
other nodes
X'1023' COMMUNICATIONS PROGRAM IN REMOTE NODE
X'1024' COMMUNICATION ACCESS METHOD
X'1030' LAN MANAGER PROGRAM: The software program in a LAN
manager
X'103l' LAN MANAGEMENT SERVER: A data collection and distribution
point for a single LAN segment token-ring or bus.
A LAN
management server forwards data received from stations on
its token-ring or bus and possibly results from
preliminary analysis performed by the server (on that
data) to the LAN manager.
LAN management servers also
send data to stations on their token-rings or busses.
Note: The LAN management servers that are currently defined are:
Ring Error Monitor (REM), Configuration Report Server (CRS), Ring
Parameter Server (RPS), LAN Bridge Server(LBS), and LAN Reporting
Mechanism (LRM).
X'1040' I/O ACCESS METHOD
X'2000' COMMUNICATIONS: The facility used to permit data flow from one
location to another
Note: This code point, and the replacement code points under it,
is used only when a more appropriate probable cause cannot be
determined.
X'200l' START/STOP COMMUNICATIONS: Asynchronous transmission in
which a group of signals representing a character is
preceded by a start element and is followed by a stop
element; for example, ASCII
X'ZOOZ' BINARY SYNCHRONOUS COMMUNICATIONS:
Synchronous
transmission of binary-coded data between stations, using
a standard set of control characters and control
character sequences
X'2003' SNA COMMUNICATIONS: Communication according to the
Systems Network Architecture formats, protocols, and
operational sequences
X'Z004' SDLC COMMUNICATIONS:
(Synchronous Data Link
Control)--synchronous, code-transparent, serial-by-bit
information transfer over a link connection
X'2005' X.21 NETWORK: A network implementing the X.Zl protocols.
These protocols defing an interface between Data Terminal
Equipment (DTE) and Data Circuit-terminating Equipment
(DCE) for synchronous operation on circuit switched
public data networks
X'2006' X.25 NETWORK:
A packet switch~ng data network implemented
according to the recommendation developed by the CCITT
which provides a standard interface for the connection of
processing equipment
X'Z007' LAN LLC COMMUNICATIONS:
(Logical Link
Control)--error-free, in sequence information transfer
over a LAN
X'200S' X.25 COMMUNICATIONS: Communications according to CCITT
recommendation X.25 for a packet switching data network.

Chapter S.

Common Fields

S-33

MS Major Vectors
Note:
Use code point X'2006' (X.2S NETWORK) if the problem is
known to be in X.2S network.
X'2009' X.21 COMMUNICATIONS:
Communications according to CCITT
recommendation X.21 for a circuit switching data network.
Note:
Use code point X'200S' (X.21 NETWORK) if the problem is
known to be in X.21 network.
X'200A' ISDN NETWORK:
A network implementing the Integrated
Services Digital Network protocols
X'2010' DDS NETWORK:
A network implementing the Digital Data
Service, e.g., DATAPHONEl Digital Service (DDS).
X'202l' BANKING LOOP:
A network configuration, specifically
designed for the finance industry, in which there is a
single path between all devices and the path is a closed
circuit terminating in a controller
X'2022' STORE LOOP:
A network configuration, specifically
designed for the retail industry, in which there is a
single path between all devices and the path is a closed
circuit terminating in a controller
X'2031' LINE:
The telephone line or transmission link connecting
two or more components in the network
X'2033' LINE/REMOTE MODEM:
A line or the modem on it remote from
the Alert sender
X'2034' LINE/REMOTE LDM:
A line or the limited distance modem on
it remote from the Alert sender
X'203S' LINE/REMOTE DIGITAL DATA DEVICE:
A line or the digital
data device (DDD) on it remote from the Alert sender
X'2036' LINE/REMOTE DCE A line or the Data Circuit-Terminating
Equipment (DCE) on it remote from the Alert sender
Note:
This code point is used only if the Alert sender is unable
to determine whether the DeE is a modem or a DDD; see code points
X'2033' and X'203S'.
X'2037' DCE-DSE CONNECTION:
The telephone line connecting the
calling DCE to its local DSE
X'20A7' OUTBOUND LINE: The equipment that connects the transmit
circuits of the local DCE (i.e., the DCE local to the
node sending error notification) to the receive circuits
of the remote DeE.
X'20A8' INBOUND LINE:
The equipment that connects the receive
circuits of the local DeE (i.e., the DCE local to the
node sending the error notification) to the transmit
circuits of the remote DCE.
X'2040' INTER-EXCHANGE NETWORK:
A network providing services
between two local exchange areas
X'2041' PRIVATE NETWORK REACHED:
The private network containing
the called DTE
X'2080' HOST COMMUNICATIONS
Note:
If the Alert sender is aware of the protocol being used for
communication with the host, it uses a code point identifying that
protocol.

1

8-34

DATAPHONE is the Registered Service Mark of AT&T Company.

SNA Formats

MS Major Vectors
X'2l00' COMMUNICATIONS/REMOTE NODE:
Either a communications facility
denoted by a X'20xx' code point or a remote node denoted by a
X'22xx' code point
Note:
This code point is used only when a more specific probable
cause cannot be determined.
X'2l0l'
X'2l02'
X'2l04'
X'2l0S'
X'2l06'
X'2l07'
X'2l0A'
X'2l30'

START/STOP COMMUNICATIONS/REMOTE NODE
BSC COMMUNICATIONS/REMOTE NODE
SDLC COMMUNICATIONS/REMOTE NODE
X.2l COMMUNICATIONS/CALLED DTE
X.2S COMMUNICATIONS/REMOTE NODE
LAN LLC COMMUNICATIONS/REMOTE NODE
ISDN COMMUNICATIONS/REMOTE NODE
LINE/REMOTE NODE

X'2200' REMOTE NODE:
The node at the remote end of a link connection
Note:
"Remote" is defined from the point of view of the node
detecting the Alert condition.
X'220l' CALLED DTE:
On a switched telephone connection, the data
terminal equipment (DTE) to which the telephone call to
establish the connection was placed
X'2204' OTHER REMOTE NODE:
On a multipoint link, the remote node
interfering with the link activity but not part of the
logical connection for which the error was detected
X'2300' CONNECTION NOT ESTABLISHED:
A telephone connection required for
the requested operation has not been established
X'230l' CALLED NUMBER BUSY:
The telephone number dialed for a
teleprocessing connection was busy
X'2302' CALLED NUMBER DID NOT ANSWER:
The telephone number dialed
for a teleprocessing connection did not answer
X'2303' CALLED NUMBER OUT OF ORDER:
The telephone number dialed
for a teleprocessing connection is inoperative
X'2304' INCORRECT NUMBER CALLED:
The telephone number dialed for
a teleprocessing connection was incorrect
X'2305' MANUAL DIAL REQUIRED: The operator must establish a
manual dial connection to a remote device before normal
operation can continue
X'2306' CHANGED NUMBER:
The called DTE has recently been assigned
a new number (unique X.2l status provides this
information)
X'2307' INVALID REQUEST:
In the course of attempting to set up a
telephone connection~ the caller has made an invalid
request
X'2308' ACCESS BARRED: The calling DTE is not allowed to connect
to the called DTE
X'2309' LINK AND/OR AUTO-CALL UNIT IN USE:
An auto-call attempt
failed because either the link or the attached auto-call
unit was in use.
X'230A' CALL COLLISION:
An outgoing call was not completed
because it collided with an incoming calIon the same
link.

Chapter 8.

Common Fields

8-35

MS Major Vectors

X'2600' ELECTRICAL INTERFERENCE: An electrical disturbance in a
communication system that interferes with or prevents reception of
a signal or of information
X'3000' CHANNEL: The equipment that is used to direct data to and from
input/output devices and locally-attached control units
Note:
This code point applies only to the channel itself.
If the
channel interface cable is intended, code point X'3411' (CHANNEL
INTERFACE CABLE) is used instead.
X'3100' CONTROLLER: A communication device that controls other devices
and the flow of information to and from them
Note:
For this code point, and for the replacement code points
under it, an Alert receiver has two options:
It may display the
English text (or its national language equivalent) documented with
the code points; or it may display the machine type, or, if one is
present, the hardware product common name, from the first hardware
Product Identifier (X'll') subvector within the indicated resource
Product Set ID.
X'3111' COMMUNICATION CONTROLLER:
A communication device that
controls the transmission of data over links in a network
Note:
In SNA, a communication controller is a type 4 node.
X'3112' SENDING NODE:
The node detecting the error and sending
the error notification for it.
X'3113' SENDING NODE AND MODEMS CONFIGURATION
X'3114' SENDING NODE AND DSU/CSU'S CONFIGURATION
X'3115' SENDING NODE/TAILED-CIRCUIT CABLE:
The error notification
sender configuration is incorrect or the tailed-circuit
attachment cable is not connected or present
X'3121' TERMINAL CONTROL UNIT:
A communication device that
controls the transmission of data to and from terminals
Note:
In SNA, a terminal control unit is a type 2.0 or 2.1 node.
X'3l22' FINANCE CONTROLLER: A terminal control unit specifically
designed for the banking industry
X'3123' STORE CONTROLLER:
A terminal control unit specifically
- designed for the retail industry
X'3131' DASD CONTROL UNIT:
A device that controls the transfer of
data to and from a direct access storage device such as
disk or drum
X'3l32' TAPE CONTROL UNIT:
A device that controls the transfer of
data to and from tape drives
X'3200' COMMUNICATIONS INTERFACE:
The equipment connecting a node to the
component in a link connection with which it exchanges physical
control signals
Note:
This code point covers (1) the receivers and drivers in the
node, (2) the cable, and (3) the component in the link connection
that responds to the physical control signals from the node (e.g.,
a modem). This code point is used only when a more specific
probable cause cannot be determined.

8-36

SNA Formats

MS Major Vectors
X'3220' LOCAL TOKEN-RING ADAPTER INTERFACE: The programming
interface for the local token-ring adapter
X'322l' CSMA/CD ADAPTER INTERFACE:
The programming interface for
the local CSMA/CD adapter
X'3222' ISDN ADAPTER INTERFACE: The programming interface for the
local ISDN adapter
X'3223' TOKEN-RING ADAPTER INTERFACE:
The programming interface
for a token-ring adapter
X'3224' LOCAL AUTO-CALL UNIT INTERFACE
X'32Dl' LOCAL DCE COMMUNICATIONS INTERFACE: The communications
interface between the Alert sender and the local Data
Circuit-Terminating Equipment (DCE)
X'32D2' REMOTE DCE COMMUNICATIONS INTERFACE:
The communications
interface between the Data Circuit-Terminating Equipment
(DCE) remote from the Alert sender and the remote node
X'32D3' DCE EMULATION INTERFACE:
The communications interface
between the Alert sender and the DCE emulation cable that
attaches it to a device's DCE interface cable
X'3300' ADAPTER:
The part of a device that interfaces between a processor
in the device and one or more attached devices
Note:
The processor referred to here could be either the main
processor in the node containing the adapter or a processor in,
e.g., a communication subsystem controller.
X'330l' CHANNEL ADAPTER
X'3302' COMMUNICATIONS ADAPTER
X'3309' LINE ADAPTER
Note:
A line adapter in a communication controller is often
referred to as a scanner.
X'330F' HPTSS ADAPTER:
A high-speed processor transmission
subsystem adapter in a communication controller
X'33l0' LOCAL ISDN ADAPTER:
An adapter that attaches the Alert
sender to an ISDN network
Note:
See also code point X'3532' LOCAL ISDN TERMINAL ADAPTER.
A
terminal adapter is distinguished from an ISDN adapter by the
presence of a defined interface (e.g., RS-232C) between itself and
the node that it serves; an ISDN adapter is typically integrated
within its node.
X'33ll' REMOTE ISDN ADAPTER:
An adapter that attaches to an ISDN
network a node with which the Alert sender has a logical
connection using the network
Note:
See also code point X'3533' REMOTE ISDN TERMINAL ADAPTER.
X'3320' LOCAL TOKEN-RING ADAPTER:
An adapter that attaches the
Alert sender to a token-ring LAN
X'3322' LOCAL CSMA/CD ADAPTER: An adapter that attaches the Alert
sender to a CSMA/CD LAN
X'3323' REMOTE CSMA/CD ADAPTER: An adapter that attaches a node
other than the Alert sender to a CSMA/CD LAN
X'3325' CSMA/CD ADAPTER
X'3330' ADAPTER HARDWARE: The hardware comprising an adapter
X'333l' ADAPTER MICROCODE: The microcode executing in an adapter
X'3380' ROTARY GROUP:
A number of ports on a device that are all
reached via the same telephone number; a rotary group is

Chapter 8.

Common Fields

8-37

MS Major Vectors

X'3381'
X'33Cl'
X'33C2'
X'33C3'

sometimes referred to as MLSA (multiple lines at same
address)
X.21 ROTARY GROUP
LINE ADAPTER HARDWARE
LINE ADAPTER MICROCODE
LINE INTERFACE COUPLER (LIC)

X'3400' CABLE:
A cable or its connectors used to electrically connect
devices together
X'340l' LOCAL DCE INTERFACE CABLE:
The cable, or its connectors,
between the Alert sender and the local Data
Circuit-Terminating Equipment (DCE)
X'3403' REMOTE DCE INTERFACE CABLE:
The cable, or its connectors,
between the Alert sender's remote DCE and the device
attached to it.
(The device could be another DCE, e.g.,
the local DCE on a second link segment.)
X'3404' DCE EMULATION CABLE: The cable, or its connectors,
between the Alert sender and a DCE interface cable
attached to a device
Note:
The end of the DCE emulation cable remote from the Alert
sender plugs directly into the DCE interface cable attached to the
device.
X'34l1' CHANNEL INTERFACE CABLE:
The cable or cables, or their
connectors, between a channel and a locally attached
device
X'3426' CSMA/CD LAN CABLES:
The cables of a CSMA/CD LAN. These
include the cable attaching the Alert sender to the
CSMA/CD bus and the bus itself.
X'3436' LOCAL CSMA/CD ADAPTER CABLE:
The cable attaching the
Alert sender to the CSMA/CD bus
X'344l' LOOP CABLE:
A cable connecting the nodes attached to a
communication loop
X'345l' DEVICE CABLE:
A cable connecting a device directly to a
communication controller or a control unit
Note:
This code point also covers any passive distribution
assembly that, externally, is indistinguishable from the cable
itself.
X'3452' STORAGE DEVICE CABLE: A cable directly connecting a local
storage device to its adapter/controller
X'3460' INTERNAL CABLE
X'3461' CABLE TERMINATOR
X'3462' LOCAL DCE LOOP:
the DCE loop local to the error
notification sender.
Note:
A DCE loop is the equipment comprised of cables,
converters, etc., that connect the DCE with the nearest central
office exchange; this equipment does not include the customer
premises wiring.
X'3463' REMOTE DCE LOOP: The DCE loop remote from the error
notification sender.
X'3464' TELECOMMUNICATION CABLE CONNECTION:
The connection of the
telecommunication cable with the local DCE or with the
telephone connecting block provided by the
telecommunications facility.

8-38

SNA Formats

MS Major Vectors

X'3500' COMMUNICATION EQUIPMENT:
External equipment used to connect
devices or other system components
Note:
If the attaching equipment is known to be a modem, then a
modem code point (X'36xx') is sent instead of this code point.
Note:
LAN components are not reported with X'35xx' code points;
see the X'3700' code point for a discussion of how they are
reported.
X'3502' TERMINAL MULTIPLEXER: The equipment used to connect
multiple devices to a single cable
X'3503' LINE SWITCH:
A device that on demand allows Data
Circuit-terminating Equipment (DCE) to be attached to
different Data Terminal Equipment (DTE) ports.
The
device supports both digital switching for the DCE-DTE
interface and also the switching of the analog interface
between the DCE and the communication facility
(transmission medium).
X'3504' TIME DIVISION MULTIPLEXER:
A device that combines digital
data streams from different tributary channels into one
data stream on a common channel; a separate periodic time
interval is allocated to each tributary channel in the
common channel.
It also performs the reverse process of
demultiplexing the composite data stream from the common
channel into its constituent component data streams for
the tributary channels
X'3505' STATISTICAL MULTIPLEXER:
A device that combines digital
data streams from different tributary channels into one
data stream for the common channel; it takes advantage of
the bursty nature of information on the tributary
channels to interleave information from these channels
onto the common channel.
It also performs the reverse
process of demultiplexing the composite data stream into
its constituent component data streams
X'3506' LOCAL DIGITAL DATA DEVICE:
The digital data device (DDD)
connected to the Alert sender
X'3507' REMOTE DIGITAL DATA DEVICE: The digital data device (DDD)
remote from the Alert sender
X'3508' LOCAL AUTO-CALL UNIT
X'35l0' CALLED DCE
Note:
See also code point X'3542' REMOTE DCE. X'35l0' is used
when reporting a problem encountered during an attempt to
establish a switched connection. X'3542' is used when the problem
is not related to the establishment of a switched connection.
X'3530' ISDN NETWORK COMPONENT
X'353l' ISDN NETWORK TERMINATION (NTl): A device, normally
residing on the user's premises, that provides
conversion, for basic-rate ISDN service, between the
4-wire interface seen by the user and the 2-wire
interface seen by the ISDN service provider
X'3532' LOCAL ISDN TERMINAL ADAPTER: The terminal adapter local
to the Alert sender
Note:
See also code point X'33l0' LOCAL ISDN ADAPTER.
A terminal
adapter is distinguished from an ISDN adapter by the presence of a

Chapter 8.

Common Fields

8-39

MS Major Vectors
defined interface (e.g., RS-232C) between itself and the node that
it serves; an ISDN adapter is typically integrated within its
node.
X'3533' REMOTE ISDN TERMINAL ADAPTER:
The terminal adapter that
attaches to an ISDN network a node with which the Alert
sender has a logical connection utilizing the network
Note:
See also code point X'33Il' REMOTE ISDN ADAPTER.
X'3534' LOCAL DSU/CSU: The DSU/CSU local to the error
notification sender
Note:
DSU/CSU is a signal converter which implements the function
of a Data Service Unit (DSU) and Channel Service Unit (CSU) to
provide the DTE interface and the line interface, respectively,
with a Digital Data Service (DDS).
Note:
For a multi-segment link connection, this text does not
indicate which segment is involved. This information is typically
communicated by means of a qualifier associated with a Failure
Cause.
X'3535' REMOTE DSU/CSU: The DSU/CSU remote from the error
notification sender.
Note:
For a multi-segment link connection, this text does not
indicate which segment is involved. This information is typically
communicated by means of a qualifier associated with a Failure
Cause.
X'3536' LOCAL AND REMOTE DSU/CSU'S
Note:
For a multi-segment link connection, .this text does not
indicate which segment is involved. This information is typically
communicated by means of a qualifier associated with a Failure
Cause.
X'354l' LOCAL DCE: The Data Circuit-Terminating Equipment (DCE)
connected to the Alert sender
Note:
This code point is used, only if the Alert sender is unable
to determine whether the DCE is a modem or a DDD; see code points
X'3506' and X'360l'.
X'3542' REMOTE DCE: The Data Circuit-Terminating Equipment (DCE)
remote from the Alert sender
Note:
This code point is used only if the Alert sender is unable
to determine whether the DCE is a modem or a DDD; see code points
X'3507' and X'3603'.
See also code point X'35l0' CALLED DCE.
X'3600' MODEM: A device or functional unit that modulates and demodulates
signals transmitted over data communication facilities
X'360l' LOCAL MODEM:
On a particular link segment, the modem
nearer to the Alert sender
X'3602' LOCAL LINK DIAGNOSTIC UNIT:
A device that connects to
both sides of a local modem and provides Link Problem
Determination Aid (LPDA) data for digital and analog
links with non-intelligent IBM or non-IBM modems
X'3603' REMOTE MODEM:
On a particular link segment, the modem
farther from the Alert sender
X'3604' REMOTE LINK DIAGNOSTIC UNIT:
A device that connects to
both sides of a remote modem and provides Link Problem
Determination Aid (LPDA) data for digital and analog
links with non-intelligent IBM or non-IBM modems

8-40

SNA Formats

MS Major Vectors
X'360S' LOCAL AND REMOTE MODEMS
Note:
For a multi-segment link connection, this text does not
indicate which segment is involved.
This information is typically
communicated by means of a qualifier associated with a Failure
Cause.
X'3611' LOCAL LDM: The limited distance modem nearer to the Alert
sender
X'3613' REMOTE LDM: The limited distance modem farther from the
Alert sender
X'3621' LOCAL ENHANCED MODEM: The enhanced modem connected to the
Alert sender
Note:
An enhanced modem is a modem that can provide functions
other than modulation/demodulation, such as establishing switched
connections and storing dial digits.
X'3700' LAN COMPONENT:
A component of a local area network.
On a
token-ring LAN, the LAN components include the adapters, bridges,
access units, repeaters, repeater/amplifiers, and the LAN cable.
On a CSMA/CD LAN, the LAN components include the adapters,
bridges, cables, taps, splitters, amplifiers, and translator
units.
Note: This default code point is used to indicate that some
unspecified LAN component is a probable cause.
Individual LAN
components are denoted by replacement code points under X'3700',
with the exception of the LAN adapters, which fall under ADAPTER
(X'3300'), and the CSMA/CD LAN cables, which fall under CABLE
(X'3400').
X'3701' TOKEN-RING LAN COMPONENT
X'3702' TOKEN-RING LOBE:
An adapter, the lobe cables connecting
it to its access unit, and a portion of the access unit
X'3703' TOKEN-RING FAULT DOMAIN:
An adapter, its nearest active
upstream neighbor, and the token-ring media between them;
the token-ring media consists of the lobe cables,
portions of one or more access units, and possibly a
portion of the LAN cable
X'3704' TOKEN-RING DUPLICATE STATION ADDRESS
X'370S' TOKEN-RING REMOVE COMMAND RECEIVED:
An adapter received a
Remove Ring Station MAC frame
X'3714' REMOTE TOKEN-RING lOBE:
A lobe attaching a node other
than the Alert sender to the token-ring
X'3721' CSMA/CD LAN COMPONENT
X'3724' CSMA/CD DUPLICATE STATION ADDRESS
X'372S' CSMA/CD REMOVE COMMAND RECEIVED
X'3740' LAN BRIDGE: A network component that interconnects, at
the medium access sublayer (of the DLC layer, two
token-rings, two busses, or a token-ring and a bus
Note:
The busses involved may use either the CSMA/CD protocol or
the token bus protocol
X'4000' PERFORMANCE DEGRADED
X'4001' STORAGE SUBSYSTEM OVERLOADED
X'4002' WORK STATION SUBSYSTEM OVERLOADED

Chapter 8.

Common Fields

8-41

MS Major Vectors
X'4003' COMMUNICATIONS SUBSYSTEM OVERLOADED
X'SOOO' MEDIA:
A tape, disk, diskette, or paper (or other data medium)
that is required to read data from or write data on
X'SOOl' DASD MEDIA:
The media used in a direct access storage
device; it may be either removable or non-removable
X'S002' DISKETTE: A thin, flexible magnetic disk in a semi-rigid
protective jacket, in which the disk is permanently
enclosed; also termed a floppy diskette
X'S003' TAPE:
A recording medium in the form of a ribbon that has
one or more tracks along its length; magnetic recordings
can be made on either one or both sides
X'S004' OPTICAL DISK:
A DASD medium on which data is encoded
optically
X'6000' DEVICE: An input, output, or input/output device (e.g., a
terminal or disk drive)
Note:
An Alert sender may be unable to distinguish a
directly-attached device from an attached protocol converter or
media conversion unit by which devices are attached to it.
Thus
this code point covers these additional components as well.
X'6l00' INPUT DEVICE:

A device that is used to enter data into a system

X'6110' KEYBOARD:
An arrangement of alphanumeric, special
character and function keys laid out in a specified
manner and used to enter information into a terminal, and
thereby into a system
X'6l11' KEYPAD: A specialized keyboard with an arrangement of a
limited number of alphanumeric, special character and/or
function keys
X'61l2' SELECTOR PEN:
A light sensitive pen used in display
operations
X'6113' MICR READER/SORTER:
A magnetic ink character recognition
reader/sorter
X'6114' MAGNETIC STRIPE READER:
A device that reads data from,
and in some cases writes data to, a card containing a
magnetic stripe
X'6200' OUTPUT DEVICE:

A device that receives data from a system

X'62l0' PRINTER: An output device that produces durable and
optically viewable output in the form of characters (and
optionally graphics) by a means other than by drawing
with one or more pens
Note: Contrast with code point X'6213' PLOTTER.
X'62ll' COPIER: An output device that produces one or more copies
of an original without affecting the original
X'62l2' CAMERA: An output device that combines electronic data
with a visual image on a single visual medium
X'62l3' PLOTTER: An output device that produces graphic and/or
character output by means of one or more pens that draw
on the surface of the output medium

8-42

SNA Formats

MS Major Vectors
Note: Contrast with code point X'62l0' PRINTER.
X'6220' PRINTER CASSETTE: A removable container for inputting
paper to a printer
X'6300' INPUT/OUTPUT DEVICE: A device whose parts can be performing an
input process and output process at the same time, such as a card
reader/punch
X'630l' DISPLAY/PRINTER: A device that has either of the
characteristics of a display or printer or both. This
code point is used only when the Alert sender cannot
determine whether the attached device is a display or
printer
X'6302' DISPLAY: A workstation that requires a host connection in
order to function; typically a display includes both a
monitor and a keyboard
X'63l0' DASD DEVICE: A device in which the access time is
effectively independent of the location of the data.
The
device may use either removable or non-removable media
X'63ll' DISKETTE DEVICE: A direct access storage device that uses
a diskette as the storage medium
X'63l2' OPTICAL DISK DEVICE: A direct access storage device that
uses an optical disk as the storage medium.
The disk may
be either removable or non-removable
X'63l3' TERMINAL: A device in a system or network at which data
can either enter or leave. A terminal is usually
equipped with a keyboard and a display device, and 1S
capable of sending and receiving information
X'63l4' TAPE DRIVE: An input/output device used for moving
magnetic tape and controlling its movement
X'63lS' CONSOLE: A terminal used for communication between an
operator and a processor
X'6400' DEPOSITORY:

A device that receives items into a system

X'640l' ENVELOPE DEPOSITORY: A device that receives into a system
items sealed in an envelope. The envelope is not opened,
nor are its contents examined by the system; the envelope
is stored for human action
X'6402' CHECK DEPOSITORY: A device that receives checks into a
system, then reads and retains them.
It may also
transfer information to a check and return the check to a
user
X'6403' CARD DEPOSITORY: A device that retains credit, personal
banking, or other cards used to access a personal banking
machine (PBM)
X'6S00' DISPENSER:

A device that dispenses items to a user of a system

X'6S0l' DOCUMENT DISPENSER:
primarily bills
X'6502' TICKET DISPENSER
X'6503' KEY DISPENSER
X'6504' COIN DISPENSER

A device that dispenses documents,

Chapter 8.

Common Fields

8-43

MS Major Vectors

X'6600' SELF-SERVICE TERMINAL: A device that allows a customer of a
business to perform a transaction that would otherwise require
assistance by personnel of the business
X'6601' PERSONAL BANKING MACHINE:
A self-service terminal for
financial transactions
X'6630' TELLER ASSIST UNIT: A terminal that assists a financial
teller in transactions
Note:
This device does not fit the strict definition of a
self-service terminal, since it is used by personnel of a
financial institution; it is included in this range becuase it is
very close in function to other self-service terminals.
X'7000' PERSONNEL:
personnel

Action on the part of customer, service, or other

X'7001' LOCAL SYSTEM OPERATOR: A person (or program) co-located
with a system and responsible for the operation of all or
part of it, or responsible for performing system
orientated procedures
X'7002' REMOTE SYSTEM OPERATOR: A person (or program) not
co-located with a system and responsible for the
operation of all or part of it, or responsible for
performing system orientated procedures
X'7003' NETWORK OPERATOR: A person (or program) responsible for
the operation of all or part of the network, or
responsible for performing network orientated procedures
X'7004' USER:
Anyone who requires the services of a computer
system, such as an "end user"
X'700S' SYSTEM PROGRAMMER
X'7006' CUSTOMER PERSONNEL
X'7007' SERVICE REPRESENTATIVE
X'7010' PRINTER OPERATOR
X'7011' TERMINAL CONTROL UNIT OPERATOR
X'7012' LAN BRIDGE OPERATOR
X'7013' LAN MANAGER OPERATOR
x'aooo' CONFIGURATION
x'aOOl'
X'a002'
X'a003'
X'a004'

STORAGE CONFIGURATION
WORK STATION CONFIGURATION
COMMUNICATION CONFIGURATION
CUSTOMIZATION IMAGE: The set of rules which helps direct
the operation of a device is suspected of causing the
Alert condition.

X'EOOO'-X'EFFF' Reserved
Note:
This range of code points is reserved for use by
non-IBM products and customer written applications.
No
IBM product will send a code point from within this range.
X'FEOO' UNDETERMINED:
condition

a-44

SNA Formats

No probable cause can be determined for this Alert

MS Major Vectors
X'FFFF' Reserved

User Causes (X'94') Alert MS Subvector
This subvector transports code points for stored text
detailing the probable user causes for the Alert condition
and the recommended actions to be taken in connection with
these causes.
It may also transport additional detailed
data, to be inserted into the text indexed by the user
cause and/or recommended action code points.

o
1
2-p

Length (p+l), in binary, of the User Causes subvector
Key:
X'94'
Two or more subfields containing user cause data, as described below for
keys X'OO'-X'7F' and in "Network Alert (X'OOOO') Common Subfields" on page
8-82 for keys X'80'-X'FE'.
X'OI' User Causes
X'81' Recommended Actions
X'82' Detailed Data
X'83' Product Set ID Index
Note:
Subfields X'OI' and X'81' are always present.
One or more
instances of the X'82' and/or X'83' subfields may be present, depending on
the code points present in the X'Ol' and X'8l' subfields.

User Causes (X'Ol') User Causes Subfield
This subfield contains one or more code points denoting
probable user causes of the Alert condition, listed in
order of decreasing probability. A user cause is defined
to be a condition that an operator can resolve without
contacting any service organization.

o
1
2-q

Length (q+l), in binary, of the User Causes subfield
Key:
X'Ol'
Two-byte user cause code points.
Each code point provides an index to
predefined text, describing the user cause, that is displayed at the focal
point. An Alert receiver has the option of displaying, for each code
point it receives:
either the text associated with that code point, or
its national language equivalent; or the text associated with the default
code point above it, or its national language equivalent.
Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order Z-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (corresponding to X'**OO' code points) if
it does not recognize the more specific code point (e.g., because of
different release schedules).
The expression "(sf82 qualifier)" in the English text indicates a
variable-length gap, to be filled 1n with data passed in a Detailed Data
(X'82') subfield. The one or more necessary X'8Z' subfields follow

Chapter 8.

Common Fields

8-45

MS Major Vectors
immediately after this subfield in the X'94' subvector, in the order in
which they are to be ~ssociated with the gaps specified in the X'Ol'
subfield.
The expression "(sf83 product text)" in the English text similarly
indicates a variable-length gap, to be filled in with product
identification data from the Product Identifier X'II' subvector indicated
by a Product Set ID Index (X'83') subfield. The necessary X'83' subfields
follow immediately after the X'OI' subfieId, in the same subvector, in the
order in which they are to be associated with the gaps specified in the
X'OI' subfield. The third digit of each user cause code point indicates
the number of succeeding X'82' subfields that are associated with the code
point, or whether a X'83' subfieid is associated with it, as follows:
X'xxOx'-X'xx9x':

No X'82' subfields.

XCxxAx'-X'xxBx':

One X'82' subfield.

X'xxCx':

Two X'82' subfields.

X'xxDx':

Three X'82' subfields.

X'xxEx':

One X'83' subfield.

X'xxFx':

Reserved: code points will not be assigned 1n
this range.

Defined user cause codes are:
X'OlOO' STORAGE CAPACITY EXCEEDED: A request has been received requiring
more storage than is currently available
X'Olll' THE PORTION OF MAIN STORAGE MADE AVAILABLE BY THE USER FOR
A PARTICULAR OPERATION HAS BEEN EXHAUSTED
X'OI12' A USER-SPECIFIED THRESHOLD, INDICATING THAT AVAILABLE
AUXILIARY STORAGE IS NEARLY FULL, HAS BEEN REACHED
X'0200' POWER OFF: The equipment is powered off and will require operator
action to power on and prepare equipment for use
X'020l'
X'0202'
X'0203'
X'0204'
X'0205'
X'0206'
X'0207'
X'0208'
X'0209'
X'020A'
X'020B'
X'020C'
X'020D'
X'020E'

8-46

SNA Formats

LOCAL DCE POWER OFF
REMOTE DCE POWER OFF
LOCAL DIGITAL DATA DEVICE POWER OFF
REMOTE DIGITAL DATA DEVICE POWER OFF
LOCAL MODEM POWER OFF
REMOTE MODEM POWER OFF
LOCAL LINK DIAGNOSTIC UNIT POWER OFF
REMOTE LINK DIAGNOSTIC UNIT POWER OFF
REMOTE DEVICE POWER OFF
LOCAL TERMINAL ADAPTER (TA) POWER OFF
REMOTE TERMINAL ADAPTER (TA) POWER OFF
LOCAL CONTROLLER POWER OFF
REMOTE CONTROLLER POWER OFF
PRINTER POWER OFF

MS Major Vectors
X'020F' COMMUNICATION EQUIPMENT POWER OFF
X'0210' CALLING DCE POWER OFF
X'0211' CALLED DCE POWER OFF
X'0212' CALLED DTE POWER OFF
•
X'0213' MODEM POWER OFF
X'0214' TERMINAL MULTIPLEXER POWER OFF
X'0220' DEVICE POWER OFF
X'0221' CONSOLE POWER OFF
X'0222' LAN MANAGER POWER OFF
X'0223' REMOTE NODE POWER OFF
X'0224' LOCAL DSU/CSU POWER OFF
X'022S' REMOTE DSU/CSU POWER OFF
X'02Al' (sf82 qualifier) LOCAL MODEM POWER OFF
Note: The qualifier identifies the link segment level
which the local modem belongs.
X'02A2' (sf82 qualifier) REMOTE MODEM POWER OFF
Note: The qualifier identifies the link segment level
which the remote modem belongs.
X'02A3' (sf82 qualifier) LOCAL DSU/CSU POWER OFF
Note: The qualifier identifies the link segment level
which the local DSU/CSU belongs.
X'02A4' (sf82 qualifier) REMOTE DSU/CSU POWER OFF
Note: The qualifier identifies the link segment level
which the remote DSU/CSU belongs.

(LSL) on

(LSL) on

(LSL) on

(LSL) on

X'2200' REMOTE NODE: The node at the remote end of a link connection
Note: "Remote" is defined from the point of view of the node
detecting the Alert condition.
X'220l' CALLED DTE TAKEN OUT OF SERVICE
X'2210' REMOTE NODE CONTROL PROGRAM IPL HAS OCCURRED
X'2300' CONNECTION NOT ESTABLISHED: A telephone connection required for
the requested operation has not been established
X'2301' CALLED NUMBER BUSY
X'2304' INCORRECT TELEPHONE NUMBER SPECIFIED
X'2308' CALLING DTE DOES NOT SUBSCRIBE TO THIS FACILITY: The
calling DTE has requested a service that it does not
subscribe to
X'2310' X.21 CONNECTION INTENTIONALLY CLEARED BY TERMINAL CONTROL
UNIT OPERATOR
X'23AO' CONNECTION NOT ESTABLISHED: (sf82 qualifier)
Note: The qualifier indicates the telephone number for the
connection that could not be established.
X'2400' BUSY:

A requested resource was unavailable because it was in use

X'2401' THE MAXIMUM NUMBER OF WORKSTATIONS SUPPORTABLE BY THE
LOCAL WORKSTATION CONTROLLER HAS BEEN EXCEEDED
X'2S00' LINE NOT ENABLED:
data transmission

A communication link has not been prepared for

Chapter 8.

Common Fields

8-47

MS Major Vectors
X'250l' PORT DEACTIVATED
X'25l0' LINE NOT ENABLED AT CALLED DTE
X'25ll' PORT DEACTIVATED AT CALLED DTE
X'3300' ADAPTER NOT READY:

An adapter has not been made ready for use

X'3380' AN OPERATOR HAS DEACTIVATED ALL PORTS IN A ROTARY GROUP
X'338l' AN OPERATOR HAS DEACTIVATED ALL PORTS IN A ROTARY GROUP
USED BY AN X.2l SHORT HOLD MODE SESSION

X'3400' CABLE NOT CONNECTED:

A cable is either loose or disconnected

X'340l' CABLING INSTALLED INCORRECTLY
X'3402' KEYBOARD UNPLUGGED
X'3403' LINE SWITCHED TO INCORRECT POSITION
X'345l' DEVICE CABLE NOT CONNECTED
X'34AO' CABLE NOT CONNECTED: (sf82 qualifier)
Note; The qualifier specifies the disconnected cable by, for
example, specifying the number of the port to which it should be
attached.
X'34Al' CABLE NOT INSTALLED: (sf82 qualifier)
Note: The qualifier specifies the cable that was not installed.
X'34A2' CABLE UNPLUGGED: (sf82 qualifier)
Note: The qualifier specifies the cable that is unplugged.
l

X'3800' LPDA DCE: A DCE that supports link problem determination aid
functions, e.g., IBM LPDA-2 modem and IBM LPDA-2 DSU/CSU.
X'380l' SNBU HAS BEEN DISCONNECTED
X'3802' TC LEAD ACTIVE ON REMOTE NODE INTERFACE
X'3803' TC LEAD ACTIVE ON OTHER REMOTE NODE INTERFACE
X'38AI' SPEED MISMATCH BETWEEN MODEMS ON (sf82 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'38A2' SPEED MISMATCH BETWEEN DSU/CSU'S ON (sf82 qualifier)
Note: The qualifier identifies the the link segment level (LSL)
on which the DSU/CSUs belong.
X'38A3' (sf82 qualifier) LOCAL MODEM IN TEST MODE
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'38A4' (sf82 qualifier) LOCAL DSU/CSU IN TEST MODE
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'38A5' (sf82 qualifier) REMOTE MODEM IN TEST MODE
Note: The qualifier identifies the link segment level (LSL) on
which the remote modem belongs.
X'38A6' (sf82 qualifier) REMOTE DSU/CSU IN TEST MODE
Note: The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'38A7' (sf82 qualifier) LOCAL MODEM REINITIALIZED
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'38A8' (sf82 qualifier) LOCAL DSU/CSU REINITIALIZED

8-48

SNA Formats

MS Major Vectors
Note: The qualifier identifies the link segment level (LSL) on
which the local DSI/CSU belongs.
X'38A9' (sf82 qualifier) LOCAL DSU/CSU DETECTED DDS LOOPBACK
ACTIVE IN THE LAST 2 MINUTES
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'38AA' (sf82 qualifier) REMOTE DSU/CSU DETECTED DDS LOOPBACK
ACTIVE IN THE LAST 2 MINUTES
Note:
The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'38AB' (sf82 qualifier) LOCAL MODEM POWER OFF THEN ON
Note:
The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'3aAC' (sf82 qualifier) REMOTE MODEM POWER OFF THEN ON
Note: The qualifier identifies the link segment level (LSL) on
which the remote modem belongs.
X'38AD' (sf82 qualifier) LOCAL DSU/CSU POWER OFF THEN ON
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'38AE' (sf82 qualifier) REMOTE DSU/CSU POWER OFF THEN ON
Note:
The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'38AF' (sf82 qualifier) REMOTE DSU/CSU IN CONFIGURATION MODE
Note:
The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'4000' PERFORMANCE DEGRADED
X'400l' STORAGE SUBSYSTEM OVERLOADED:
The number of attached
devices is not sufficient to handle the current work load
without performance degredation.
X'4002' WORK STATION SUBSYSTEM OVERLOADED:
The combination of
work stations attached and/or the current applications
are causing an excessive work load resulting in
performance degredation.
X'4003' COMMUNICATION SUBSYSTEM OVERLOADED:
The number of lines,
maximum aggregate data rate, or number of attached
devices is in excess of that which can be handled without
performance degredation.
X'SlOO' MEDIA DEFECTIVE: The medium (tape, disk, diskette, paper, e.g.)
is defective and must be replaced or corrected to continue
processing
X'SlOl' IMPROPER DISKETTE INSERTED: There is a usable diskette in
the diskette drive, but it is not the required one
X'Sl02' NO DISKETTE OR DEFECTIVE DISKETTE INSERTED:
There is no
diskette in the diskette drive, or the diskette in the
drive is unusable
X'SllO' NON-DUPLEX PAPER IN CASSETTE
X'S200' MEDIA JAM:
The medium (usually paper, forms, or cards) is jammed
in the machine and operator action is required to correct the
problem

Chapter 8.

Common Fields

8-49

MS Major Vectors
X'S201'
X'S202'
X'S203'
X'S204'

CARD JAM
FORMS JAM
PAPER JAM
FILM JAM:
There is a jam condition 1n the media for a
camera device.

X'S300' MEDIA SUPPLY EXHAUSTED: The medium (usually paper, forms, or
cards) supply has been consumed and operator action is required to
replenish the supply and continue operation
X'S30l'
X'S302'
X'S303'
X'S304'

OUT OF CARDS
OUT OF FORMS
OUT OF PAPER
OUT OF FILM:
The media for a camera devi ce has been
exhausted.
The media for a document
X'S30S' OUT OF BILLS OR DOCUMENTS:
feeding device has been exhausted.
X'S313' CASSETTE OUT OF PAPER
X'S400' OUT OF SUPPLIES: A device is out of supplies required for it to
perform its function
X'S40l' END OF RIBBON ENCOUNTERED:
end of the print ribbon
X'S402' OUT OF INK
X'S403' OUT OF TONER
X'S404' OUT OF FUSER OIL
X'S40S' OUT OF STAPLES

A printer has encountered the

X'SSOO' MEDIA SUPPLY LOW:
The medium (usually paper, forms, or cards)
supply is low and operator action is required to replenish the
supply and continue operation
X'SSOl'
X'SS02'
X'SS03'
X'SS04'

LOW ON CARDS
LOW ON FORMS
LOW ON PAPER
LOW ON FILM:
The media for a camera device is nearly
exhausted.
The media for a document
X'SSOS' LOW ON BILLS OR DOCUMENTS:
feeding device is nearly exhausted.

X'S600' LOW ON SUPPLIES: A device is low on supplies required for it to
perform its function
X'S602'
X'S603'
X'S604'
X'S60S'

LOW
LOW
LOW
LOW

ON
ON
ON
ON

INK
TONER
FUSER OIL
STAPLES

X'6000' DEVICE NOT READY:

A device has not been made ready for operation

X'6001' DEVICE OFFLINE: The device requested has been varied
offline by the operator and must be varied online for
processing to continue

8-S0

SNA Formats

MS Major Vectors
X'60l0'
X'60ll'
X'6012'
X'60l3'
X'60l4'
X'60l5'
X'60l6'
X'60l7'
X'60l8'
X'60l9'
X'6020'

DASD DEVICE NOT READY
DISKETTE NOT READY
TAPE NOT READY
PRINTER NOT READY
BIN COVER OPEN
PRINTER DOOR OPEN
OUTPUT HOPPER FULL
TELEPHONE SET NOT IN DATA MODE
REMOTE NODE OFFLINE
REMOTE NODE REINITIALIZED
SERVICE DOOR OPEN: The door which provides access to the
interior of the machine has been opened.

X'6400' DEPOSITORY:
A device that receives items into a system.
X'6401' DEPOSITORY NEARLY FULL: A cartridge or other container
used to collect items such as checks, envelopes, or
documents is approaching the limit of it's capacity.
X'6402' DEPOSITORY FULL: A cartridge or other container used to
collect items such as checks, envelopes, or documents has
reached it's capacity.
X'7000' OPERATOR INTERVENTION REQUIRED: Operator action is required to
return the machine to operational status
X'7001' NO CASSETTE IN PRINTER
X'7002' CARTRIDGE NOT INSTALLED CORRECTLY: A cartridge used to
collect or dispense documents is not installed correctly.
X'7003' OUT OF FOCUS: An operator is required to make an
adjustment to a camera device.
X'7004' USER NEEDS ASSISTANCE: Someone who uses the services of a
computer system, such as an "end user", requires
assistance in this usage.
X'7100' INCORRECT PROCEDURE:

An appropriate procedure was not followed

X'710l' TOKEN-RING REMOVE ADAPTER COMMAND RECEIVED
X'7102' PAPER INSTALLED INCORRECTLY
X'7103' LAN MANAGER OPERATOR ENTERED INCORRECT PASSWORD
X'7104' UNAUTHORIZED ACCESS TO LAN MANAGEMENT SERVER ATTEMPTED
X'7105' UNAUTHORIZED USER ATTEMPTED INSERTION INTO LAN
X'7106' ADAPTER ADDRESS NOT ENTERED IN AUTHORIZATION LIST
X'7107' CSMA/CD REMOVE ADAPTER COMMAND RECEIVED
X'7109' LAN BRIDGE OPERATOR TOOK BRIDGE OFFLINE
Note: When this condition occurs, the bridge can no longer
forward frames.
X'710A' LAN MANAGER OPERATOR TOOK BRIDGE OFFLINE
Note: When this condition occurs, the bridge can no longer
forward frames.
X'710B' USER INCAPACITATED LAN MANAGEMENT SERVER PROGRAM: A user
has caused the LAN management server program to become
inactive, but its processor is still able to process
interrupts

Chapter 8.

Common Fields

8-51

MS Major Vectors
X'7l10' LOCAL X.25 PROCEDURE ERROR: An error has occurred at the
side of the X.25 network nearer the Alert sender during
an attempt by the Alert sender to establish an X.25
connection
X'7lll' REMOTE X.25 PROCEDURE ERROR: An error has occurred at the
side of the X.25 network remote from the Alert sender
during an attempt by the Alert sender to establish an
X.25 connection
X'7l20' INCORRECT TEST TOOL USED: The test tool used for
servicing the device is incorrect.
X'7200' DUMP REQUESTED:
A machine readable copy of processor storage has
been obtained at the request of an operator, user, or programmed
procedure
X'720l' MICROCODE DUMP REQUESTED
X'7202' SOFTWARE DUMP REQUESTED
X'7300' FILE FULL: A requested operation cannot be performed because the
file to be used for the operation does not have space available to
contain the data
X'730l' DISKETTE OR DIRECTORY FULL: There is no more diskette
space or directory space on the diskette.
X'73AO' FILE FULL Csf82 qualifier): A requested operation cannot
be performed because the file to be used for the
operation does not have space available to contain the
data
Note:
The qualifier specifies the name, or other unique
identifier, of the file that is full.
X'73Al' FILE NEEDS REORGANIZATION Csf82 qualifier):
A file is
approaching its capacity, and will soon be unusable
unless it is reorganized
Note:
The qualifier specifies the name, or other unique
identifier, of the file needing reorganization.
X'7400' CONTAMINATION:
Dirt or some other contamination is suspected as
the cause of the problem.
The operator should perform routine
cleaning actions required for this equipment
X'740l' DIRTY READ/WRITE HEAD
X'74Al' BLOCKED AIR FILTER Csf82 qualifier)
Note:
The qualifier identifies the air filter number.
X'EOOO'-X'EFFF' Reserved
Note: This range of code points is reserved for use by
non-IBM products and customer written applications.
No
IBM product will send a code point from within this range.
Note:
The following code points specify extended messages, that provide
additional information on one or more user causes that have already been
specified.
An Alert receiver that displays only default text provides no
display for these code points.

8-52

SNA Formats

MS Major Vectors
X'FOOO' (no display):

Additional message data

X'FBOO' (no display): Additional message data
Note:
The X'FBxx' range is used for additional messages that are
identical for User, Install, and Failure Causes.
X'FBCO' FAILING COMPONENT IS IDENTIFIED BY (sfB2 qualifier) (sf82
qualifier)
Note:
The qualifiers identify the failing component by means of
its logical location, e.g., its port number and device address.
X'FBDO' PROBLEM IS RELATED TO THE CONTROLLER LOCATED AT (sfB2
qualifier) (sfB2 qualifier) (sfB2 qualifier)
Note:
The qualifiers identify the controller location as follows:
QI
Q2
Q3

= RACK
= UNIT
= CARD

(within a rack)
SLOT (within a unit)

X'FBEO' FAILING COMPONENT IS IDENTIFIED BY (sfB3 product text)
X'FFFF' Reserved

Install Causes (X'9S') Alert MS Subvector
This subvector transports code points for stored text
detailing the probable install causes for the Alert
condition and the recommended actions to be taken in
connection with these causes.
It may also transport
additional detailed data, to be inserted into the text
indexed by the install cause and/or recommended action
code points.

o
I

2-p

Length (p+l), in binary, of the Install Causes subvector
Key:
X'95'
Two or more subfields containing install cause data, as described below
for keys X'OO'-X'7F' and in "Network Alert (X'OOOO') Common Subfields" on
page B-B2 for keys X'BO'-X'FE'.
X'OI' Install Causes
X'BI' Recommended Actions
X'B2' Detailed Data
X'B3' Product Set ID Index
Note:
Subfields X'OI' and X'BI' are always-present.
One or more
instances of the X'B2' and/or X'B3' subfields may be present, depending on
the code points present in the X'OI' and X'BI' subfields.

Install Causes (X'Ol') Install Causes Subfield
This subfield contains one or more code points denoting
probable install causes of the Alert condition, listed in
order of decreasing probability.
An install cause is
defined to be a condition that resulted from the initial
installation or set-up of some equipment.

o

Length (q+l), in binary, of the Install Causes subfield

Chapter B.

Common Fields

B-53

MS Major Vectors

1
2-q

Key:
X'Ol'
Two-byte install cause code points.
Each code point provides an index to
predefined text, describing the install cause, that is displayed at the
Alert receiver. An Alert receiver has the option of displaying, for each
code point it receives: either the text associated with that code point,
or its national language equivalent; or the text associated with the
default code point above it, or its national language equivalent.
Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order 2-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (corresponding to X'**OO' code points) if
it does not recognize the more specific code point (e.g., because of
different release schedules).
The expression "(sf8Z qualifier)" 1n the English text indicates a
variable-length gap, to be filled 1n with data passed in a Detailed Data
(X'8Z') subfield. The one or more necessary X'82' subfields follow
immediately after this subfield in the X'95' subvector, in the order in
which they are to be associated with the gaps specified in the X'OI'
subfield.
The expression "(sf83 product text)" in the English text similarly
indicates a variable-length gap, to be filled in with product
identification data from the Product Identifier X'll' subvector indicated
by a Product Set ID Index (X'83') subfield. The necessary X'83' subfields
follow immediately after the X'OI' subfield, in the same subvector, in the
order in which they are to be associated with the gaps specified in the
X'OI' subfield. The third digit of each user cause code point indicates
the number of succeeding X'8Z' subfields that are associated with the code
point, or whether a X'83' subfield is associated with it, as follows:
X'xxOx'-X'xx9x':

No X'8Z' subfields.

X'xxAx'-X'xxBx':

One X'8Z' subfield.

X'xxCx':

Two X'8Z' subfields.

X'xxDx':

Three X'8Z' subfields.

X'xxEx':

One X'83' subfield.

X'xxFx':

Reserved:
code points will not be assigned in
this range.

Defined install cause codes are:
X'IZOO' INCORRECT HARDWARE CONFIGURATION:
The hardware has been installed
incorrectly and the requested function cannot be performed
X'IZOZ' LOCAL MODEM: The modem connected to the Alert sender
X'IZ03' REMOTE MODEM:
The modem remote from the Alert sender

8-54

SNA Formats

MS Major Vectors
X'l204' LOCAL DIGITAL DATA DEVICE: The digital data device (DDD)
connected to the Alert sender
X'l20S' REMOTE DIGITAL DATA DEVICE: The digital data device (DDD)
remote from the Alert sender
X'1206' LOCAL DCE: The Data Circuit-Terminating Equipment (DCE)
connected to the Alert sender
Note: This code point is used only if the Alert sender is unable
to determine whether the DCE is a modem or a DDD; see code points
X'1202' and X'1204'.
X'1207' REMOTE DCE: The Data Circuit-Terminating Equipment (DCE)
remote from the Alert sender
Note: This code point is used only if the Alert sender is unable
to determine whether the DCE is a modem or a DDD; see code points
X'1203' and X'120S'.
X'1300' INCORRECT SOFTWARE GENERATION: A program has been installed
incorrectly and the requested function cannot be performed
X'13EI' INCORRECT SOFTWARE GENERATION:
X'l400' MISMATCH BETWEEN HARDWARE AND SOFTWARE:
the hardware configuration and software

(sf83 product text)
A conflict exists between

X'1401' MISMATCH BETWEEN HARDWARE CONFIGURATION AND SOFTWARE
GENERATION
X'1402' MISMATCH BETWEEN HARDWARE AND SOFTWARE CONFIGURATIONS:
the hardware configuration represented in a software
product does not match the actual hardware configuration
X'ISOO' MISMATCH BETWEEN HARDWARE AND MICROCODE: A conflict exists
between the hardware configuration and microcode
X'ISOI' INCORRECT CUSTOMIZATION PARAMETERS
X'IS02' INCORRECT MICROCODE FIX
X'1600' MISMATCH BETWEEN SOFTWARE AND MICROCODE: A conflict exists
between a software program and a microcode program
X'l601' INCORRECT CUSTOMIZATION IMAGE: The software customization
image is incompatible with the actual microcode
configuration
X'l602' INCORRECT APPLICATION PROGRAM: An application software
program is at the wrong level for the actual microcode
configuration, or the wrong application software program
is attempting to communicate with the microcode
X'l6AI' INCORRECT SOFTWARE LEVEL
Note: The qualifier specifies a generation parameter.
X'1700' INCORRECT VALUE SPECIFIED: An incorrect value has been specified
for a system operational parameter
X'1701' INTERVENTION TIMER VALUE TOO SMALL
X'1702' RTS ACTIVATION LIMIT PARAMETER OF THE SENDING NODE IS
INCORRECT

Chapter 8.

Common Fields

8-SS

MS Major Vectors
X'l703'
X'l704'
X'1705'
X'l706'
X'l707'
X'1708'

REMOTE NODE TEST TIMEOUT TOO SHORT
OTHER REMOTE NODE TEST TIMEOUT TOO SHORT
REMOTE NODE HOLDING RTS ACTIVE
OTHER REMOTE NODE HOLDING RTS ACTIVE
MULTIPOINT TRIBUTARIES WITH SAME ADDRESS
MISMATCH BETWEEN 2-WIRE, HALF DUPLEX COUPLER ON MODEMS AND
RTS CONFIGURED FOR FULL DUPLEX BY REMOTE NODE
X'17CO' THRESHOLD VALUE SET TOO LOW (sf82 qualifier) (sf82
- qualifier)
Note: The first qualifier identifies the configuration
object/record which contains the parameter. The second qualifier
identifies the threshold parameter that is set to low.
X'2600' SYSTEM OR TRANSMISSION MEDIA INSTALLED NEAR ELECTRICAL
INTERFERENCE
X'3400' CABLE INSTALLED INCORRECTLY:
installed

A cable has been incorrectly

X'3401'
X'3402'
X'3403'
X'3404'
X'3405'
X'3406'
X'3407'
X'3451'
X'34AO'

LOCAL DCE INTERFACE CABLE INSTALLED INCORRECTLY
LINE ADAPTER MULTIPLEXER CABLE INSTALLED INCORRECTLY
REMOTE DCE INTERFACE CABLE INSTALLED INCORRECTLY
DCE EMULATION CABLE INSTALLED INCORRECTLY
LOCAL TELECOMMUNICATION CABLE NOT PROPERLY CONNECTED
REMOTE TELECOMMUNICATION CABLE NOT PROPERLY CONNECTED
PHYSICAL LINE CONNECTIONS
DEVICE CABLE INSTALLED INCORRECTLY
(sf82 subfield) LOCAL DCE INTERACE CABLE NOT PROPERLY
CONNECTED
Note: The qualifier identifies the link segment level (LSL) on
which the local DCE belongs.
X'34Al' (sf82 subfield) REMOTE DCE INTERACE CABLE NOT PROPERLY
CONNECTED
Note: The qualifier identifies the link segment level (LSL) on
which the remote DCE belongs.
X'3500' COMMUNICATION EQUIPMENT INSTALLED INCORRECTLY: Some communication
equipment has been installed incorrectly; the Alert sender aannot
determine the precise nature of this equipment
X'3501' MULTI-SEGMENT LINK DEFINED AND TAILED-CIRCUIT ATTACHMENT
CABLE NOT CONNECTED
X'35AO' (sf82 qualifier) LOCAL MODEM EXTERNAL CLOCK NOT PROVIDED
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'35Al' (sf82 qualifier) REMOTE MODEM EXTERNAL CLOCK NOT PROVIDED
Note: The qualifier identifies the link segment level (LSL) on
which the remote modem belongs.
X'35A2' 2-WIRE, HALF DUPLEX COUPLER ON THE (sf82 qualifier) LOCAL
MODEM ON A 4-WIRE, FULL DUPLEX LINE
Note: The qualifier identifies the link segment level (LSL) on
which the remote modem belongs.
X'35A3' (sf82 qualifier) MODEMS SPEED MISMATCH

8-56

SNA Formats

MS Major Vectors
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'35A4' (sf82 qualifier) DSU/CSU'S SPEED MISMATCH
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSUs belong.
X'35A5' (sf82 qualifier) INCOMPATIBLE MODEMS
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'35A6' SENDING NODE AND (sf82 qualifier) MODEMS CONFIGURATION
MISMATCH
Note:
The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'35A7' SENDING NODE AND (sf82 qualifier) DSU/CSU'S CONFIGURATION
MISMATCH
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSUs belong.
X'3700' LAN CONFIGURATION ERROR:
A configuration parameter for a local
area network has been specified incorrectly
X'3704' TOKEN-RING DUPLICATE STATION ADDRESS ASSIGNED
X'3724' CSMA/CD DUPLICATE STATION ADDRESS ASSIGNED
X'3800' LPDA CONFIGURATION ERROR:
A configuration parameter for an LPDA
link has been specified incorrectly
X'38AO' (sf82 qualifier) LOCAL MODEM ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
which the local modem belongs.
X'38Al' (sf82 qualifier) LOCAL DSU/CSU ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
which the local DSU/CSU belongs.
X'38A2' (sf82 qualifier) REMOTE MODEM ADDRESS INCORRECT
Note:
The qualifier identifies the link segment level (LSL)
which the remote modem belongs.
X'38A3' (sf82 qualifier) REMOTE DSU/CSU ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
which the remote DSU/CSU belongs.
X'38A4' (sf82 qualifier) LOCAL MODEM LPDA-2 DISABLED
Note: The qualifier identifies the link segment level (LSL)
which the local modem belongs.
X'38A5' (sf82 qualifier) LOCAL DSU/CSU LPDA-2 DISABLED
Note: The qualifier identifies the link segment level (LSL)
which the local DSU/CSU belongs.
X'38A6' (sf82 qualifier) LOCAL MODEM NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
which the local modem belongs.
X'38A7' (sf82 qualifier) REMOTE MODEM NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
which the remote modem belongs.
X'38A8' (sf82 qualifier) LOCAL DSU/CSU NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
which the local DSU/CSU belongs.
X'38A9' (sf82 qualifier) REMOTE DSU/CSU NOT CONFIGURED

Chapter 8.

Common Fields

on

on

on

on

on

on

on

on

on

8-57

MS Major Vectors
Note: The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'38AA' (sf82 qualifier) LOCAL MODEM CONFIGURED AS SECONDARY OR
TRIBUTARY
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'38AB' (sf82 qualifier) LOCAL DSU/CSU CONFIGURED AS SECONDARY OR
TRIBUTARY
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'38AC' (sf82 qualifier) LOCAL MODEM CONFIGURED AS CONTROL
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'38AD' (sf82 qualifier) LOCAL DSU/CSU CONFIGURED AS CONTROL
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'38CO' SPEED MISMATCH BETHEEN (sf82 qualifier) AND (sf82
qualifier)
Note:
The qualifiers identify the link segment levels (LSL) where
the speed mismatch is.
X'38Cl' (sf82 qualifier) LOCAL MODEM HAS A 2-WIRE COUPLER AND THE
(sf82 qualifier) REMOTE MODEM HAS A 4-WIRE COUPLER
Note:
The qualifiers identify the link segment levels (LSL) where
the modems belong.
X'8000' CONFIGURATION ERROR:
A system or device generation or
customization parameter has been specified incorrectly or
inconsistent with the actual configuration.

1S

X'80Cl' STORAGE CONFIGURATION ERROR (sf82 qualifier) (sf82
qualifier):
The actual device configuration does not
match the configuration records.
Note: The first qualifier identifies the configuration
object/record. The second qualifier identifies the incorrect
configuration parameter.
X'80C2' LOCAL HORK STATION CONFIGURATION ERROR (sf82 qualifier)
(sf82 qualifier):
The actual controller and/or work
station configuration does not match the configuration
records.
Note:
The first qualifier identifies the configuration
object/record. The second qualifier identifies the incorrect
configuration parameter.
X'80C3' REMOTE WORK STATION CONFIGURATION ERROR (sf82 qualifier)
(sf82 qualifier):
The actual controller and/or work
station configuration does not match the configuration
records.
Note:
The first qualifier identifies the configuration
object/record. The second qualifier identifies the incorrect
configuration parameter.
X'80C4' COMMUNICATION CONFIGURATION ERROR (sf82 qualifier) (sf82
qualifier):
The actual communication configuration does
not match the configuration records.

8-58

SNA Formats

MS Major Vectors
Note: The first qualifier identifies the configuration
object/record. The second qualifier identifies the incorrect
configuration parameter.

X'EOOO'-X'EFFF' Reserved
Note: This range of code points is reserved for use by
non-IBM products and customer written applications.
No
IBM product will send a code point from within this range.
Note: The following code points specify extended messages, that provide
additional information on one or more install causes that have already
been specified. An Alert receiver that displays only default text
provides no display for these code points.
X'FOOO' (no display):

Additional message data

X'F800' (no display): Additional message data
Note: The X'F8xx' range is used for additional messages that are
identical for User, Install, and Failure Causes.
X'F8CO' FAILING COMPONENT IS IDENTIFIED BY (sf82 qualifier) (sf82
qualifier)
Note: The qualifiers identify the failing component by means of
its logical location, e.g., its port number and device address.
X'F8DO' PROBLEM IS RELATED TO THE CONTROLLER LOCATED AT (sf82
qualifier) (sf82 qualifier) (sf82 quqlifier)
Note: The qualifiers identify the controller location as follows:
Ql
Q2
Q3

= RACK
= UNIT
= CARD

(within a rack)
SLOT (within a unit)

X'F8EO' FAILING COMPONENT IS IDENTIFIED BY (sf83 product text)
X'FFFF' Reserved

Failure Causes (X'96') Alert MS Subvector
This subvector transports code points for stored text
detailing the probable failure causes for the Alert
condition and the recommended actions to be taken in
connection with these causes.
It may also transport
additional detailed data, to be inserted into the text
indexed by the failure cause and/or recommended action
code points.

o
1

2-p

ength (p+l), in binary, of the Failure Causes subvector
Key:
X'96'
Two or more subfields containing failure cause data, as described below
for keys X'OO'-X'7F' and in "Network Alert (X'OOOO') Common Subfields" on
page 8-82 for keys X'80'-X'FE'.
X'Ol' Failure Causes

Chapter 8.

Common Fields

8-59

MS Major Vectors
X'BI' Recommended Actions
X'B2' Detailed Data
X'B3' Product Set ID Index
Note:
Subfields X'OI' and X'BI' are always present.
One or more
instances of the X'B2' and/or X'B3' subfields may be present, depending on
the code points present in the X'OI' and X'BI' subfields.

Failure Causes (X'Ol') Failure Causes Subfield
This subfield contains one or more code points denoting
probable failure causes of the Alert condition, listed in
order of decreasing probability. A failure cause is
defined to be a condition resulting from the failure of a
resource.

o
I

2-q

Length (q+l), in binary, of the Failure Causes subfield
Key:
X'OI'
Two-byte failure cause code points.
Each code point provides an index to
predefined text, describing the failure cause, that is displayed at the
Alert receiver. An Alert receiver has the option of displaying, for each
code point it receives:
either the text associated with that code point,
or its national language equivalent; or the text associated with the
default code point above it, or its national language equivalent.
Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order 2-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (corresponding to X'**OO' code points) if
it does not recognize the more specific code point (e.g., because of
different release schedules).
The expression "(sfB2 qualifier)" in the English text indicates a
variable-length gap, to be filled in with data passed in a Detailed Data
(X'B2') subfield. The one or more necessary X'B2' subfields follow
immediately after this subfield in the X'96' subvector, in the order in
which they are to be associated with the gaps specified in the X'OI'
subfield.
The expression "(sfB3 product text)" in the English text similarly
indicates a variable-length gap, to be filled in with product
identification data from the Product Identifier X'll' subvector indicated
by a Product Set ID Index (X'B3') subfield. The necessary X'B3' subfields
follow immediately after the X'OI' subfield, in the same subvector, in the
order in which they are to be associated with the gaps specified in the
X'OI' subfield. The third digit of each user cause code point indicates
the number of succeeding X'B2' subfields that are associated with the code
point, or whether a X'B3' subfield is associated with it, as follows:

B-60

X'xxOx'-X'xx9x':

No X'B2' subfields.

X'xxAx'-X'xxBx':

One X'B2' subfield.

SNA Formats

MS Major Vectors
X'xxCx':

Two X'82' subfields.

X'xxDx':

Three X'82' subfields.

X'xxEx':

One X'83' subfield.

X'xxFx':

Reserved:
code points will not be assigned in
this range.

Defined failure cause codes are:
X'OOOO' PROCESSOR:
The equipment used to interpret and process programmed
instructions
X'OOOl' MOSS HARDWARE:
A hardware failure in MOSS (Maintenance
and Operation Subsystem), the service processor for a
communication controller
X'0002' MOSS MICROCODE:
A microcode failure in MOSS (Maintenance
and Operation Subsystem), the service processor for a
communication controller
X'0003' PROCESSOR SWITCH: A component within a hardware product
used to switch busses and the resour~es attached to them
among processors
X'0004' CONTROL PANEL
X'OOOS' SYSTEM I/O BUS
X'0006' PROCESSOR MACHINE CHECK: A failure in the processor which
precludes it from continuing operation.
X'0007' CARD ENCLOSURE AND/OR BOARD: The enclosure and boards
used to hold circuit cards and provide power and/or
signal connections for the cards.
X'OOIO' LAN MANAGER PROCESSOR
X'OOII' PRINTER SERVER: A network component that controls the
operation of a printer
Note:
In the current implementation, the printer server is a PC
that stands between a printer and the host applications that
communicate with it.
X'0020' EXCESSIVE LOAD ON PROCESSOR: The processor is not able to
keep up with incoming requests for service.
Internal
buffers may be filled with queued tasks and not able to
accept more requests, which may be asynchronous, and
thus, discarded.
X'0030' SYSTEM MICROCODE: The specific microcode was not
identified.
X'0031' SYSTEM STORAGE MICROCODE
Note:
See also code point X'0421' (STORAGE CONTROLLER MICROCODE)
X'0032' SYSTEM DISPLAY MICROCODE
Note:
See also code point X'0422' (WORK STATION CONTROLLER
MICROCODE)
X'0033' SYSTEM COMMUNICATION MICROCODE
Note:
See also code point X'0423' (COMM SUBSYSTEM CONTROLLER
MICROCODE)
X'0034' SYSTEM PRINTER MICROCODE
Note:
See also code point X'0422' (WORK STATION CONTROLLER
MICROCODE)

Chapter 8.

Common Fields

8-61

MS Major Vectors
X'OOEl' (sf83 product text) PROCESSOR
X'OIOO' STORAGE: The random access memory (RAM) or read only memory (ROM)
accessible by a processor and by peripheral devices
X'OIOl' MAIN STORAGE: Storage from which instructions and other
data can be loaded directly into registers for subsequent
execution or processing
X'OI02' AUXILIARY STORAGE: Storage that can not be directly
addressed by a processor, such as external or secondary
storage
X'OI03' MAIN STORAGE MACHINE CHECK:
A failure in main storage
which precludes it from continuing operation.
X'OllO STORAGE CONTROL: The component that controls access to
storage
X'Olll NUMBER OF LAN MANAGEMENT FRAMES RECEIVED EXCEEDS BUFFER
CAPACITY: Management frames from stations on a local LAN
token-ring or bus are arriving faster than the LAN
management server can process them
X'OlEl' (sf83 product text) MAIN STORAGE
X'0200' POWER SUBSYSTEM: The subsystem within a hardware product that
provides electrical power to the different components within the
product that require it
X'0201' INTERNAL POWER UNIT:
An element of the power subsystem
providing electrical power to a specific component
X'0202' INTERNAL POWER CONTROL UNIT:
An element of the power
subsystem that controls the internal power units
X'0203' POWER CABLE
X'0204' POWER CORD
X'020S' POWER SUBSYSTEM PROCESSOR:
A processor within the power
subsystem responsible for its operation
X'0210' BATTERY
X'02ll' MOSS BATTERY
X'0220' MAIN AC POWER SUPPLY
X'02CO' INTERNAL POWER UNIT FOR (sf82 qualifier) (sf82 qualifier)
Note:
The qualifiers identify the adapter numbers of the adapters
served by the failing internal power unit.
X'0300' COOLING OR HEATING SUBSYSTEM: The subsystems within a hardware
product responsible for maintaining a temperature at which the
product can operate
X'030l' COOLING FAN
X'0310' AIR FLOW DETECTOR
X'0311' THERMAL DETECTOR
X'0400' SUBSYSTEM CONTROLLER: A unit within a subsystem that interfaces
between a processor and the devices in the subsystem
Note:
See Alert Description X'l600', SUBSYSTEM FAILURE, for
descriptions of the particular subsystems mentioned here.
X'0401' STORAGE CONTROLLER

8-62

SNA Formats

MS Major Vectors
X'0402' WORKSTATION CONTROLLER
X'0403' COMMUNICATIONS SUBSYSTEM CONTROLLER
Note:
Contrast this code point with X'3lll', COMMUNICATION
CONTROLLER.
A communication controller is typically a stand-alone
node within a network, for example, a 3725; a communication
subsystem controller is typically a component within a larger node
that provides for the node's communication with nodes remote from
it.
X'04ll' INTERMITTENT STORAGE CONTROLLER ERROR
X'04l2' INTERMITTENT WORKSTATION CONTROLLER ERROR
X'04l3' INTERMITTENT COMMUNICATIONS SUBSYSTEM CONTROLLER ERROR
X'042l' lOADABlE STORAGE CONTROllER MICROCODE
X'0422' LOADABlE WORKSTATION CONTROLLER MICROCODE
X'0423' lOADABLE COMMUNICATIONS SUBSYSTEM CONTROLLER MICROCODE
X'044l' STORAGE CONTROLLER INTERFACE: The interface between a
storage controller and the main processor in its node
X'0442' WORKSTATION CONTROllER INTERFACE:
The interface between a
workstation controller and the main processor in its node
X'0443' COMMUNICATIONS SUBSYSTEM CONTROLLER INTERFACE:
The
interface between a communication subsystem controller
and the main processor in its node
X'0500' SUBSYSTEM:
A set of components that jointly provide a specified
function; typically a sUbsystem includes a controller, one or more
interface adapters, physical connection media, and attached
devices
Note:
See Alert Description X'l600', SUBSYSTEM FAILURE, for
descriptions of the particular subsystems mentioned here
X'050l' STORAGE SUBSYSTEM
X'0502' WORKSTATION SUBSYSTEM
X'0503' COMMUNICATIONS SUBSYSTEM
X'lOOO' SOFTWARE PROGRAM:
A program implemented 1n software, as
distinguished from one implemented in microcode
X'lOOF' PROGRAM CHECK:
An error in a program, detected by a
processor's circuitry or microcode or by another software
program, that would cause erroneous or catastrophic
results if allowed to execute uncorrected.
X'lOlO' HOST PROGRAM:
A program running in a host processor that
is a primary or controlling program in a system
X'lOll' PRINTER SERVER PROGRAM:
A program running in a printer
server that controls a printer
Note:
See also Failure Cause X'OOll', PRINTER SERVER.
X'102l' COMMUNICATION CONTROLLER CONTRUL PROGRAM:
A software
program that is designed to schedule and supervise the
execution of programs in a communication controller
X'1022' COMMUNICATIONS PROGRAM:
A software program designed to
provide direct assistance to a node in communicating with
other nodes
X'1023' COMMUNICATIONS PROGRAM IN REMOTE NODE
X'1024' COMMUNICATIONS ACCESS METHOD:
A software program in a
host that provides access to a telecommunications network

Chapter 8.

Common Fields

8-63

MS Major Vectors
X'I030' LAN MANAGER PROGRAM:
The software program in a LAN
manager
X'1031' LAN MANAGEMENT SERVER: A data collection and distribution
point for a single LAN token-ring or bus.
A LAN
management server forwards data received from stations on
its LAN token-ring or bus and possibly results from
preliminary analysis performed by the server (on that
data) to the LAN manager.
LAN management servers also
send data to stations on their LAN token-rings or busses
Note: The LAN management servers that are currently defined are
Ring Error Monitor (REM), Configuration Report Server (CRS), Ring
Parameter Server (RPS), LAN Bridge Server(LBS), and LAN Reporting
Mechanism (LRM).
X'1032' RING ERROR MONITOR:
The LAN management server responsible
for receiving and processing error reports from the
stations on its token-ring
X'1040' I/O ACCESS METHOD ERROR:
An error in a program that
provides access to I/O (e.g., DASD, tape, terminals,
printer, telecommunications network, etc.).
X'lOAl' UNABLE TO BUILD ALERT REQUESTED BY (sf82 qualifier)
Note:
An Alert builder utility could not complete a request from
the the program identified by the qualifier.
X'lOEl' SOFTWARE PROGRAM (sf83 product text)
X'2000' COMMUNICATIONS ERROR:
facility

An error has occurred on a communication

X'200l'
X'2002'
X'2003'
X'2004'
X'2005'
X'2006'
X'2007'
X'2008'
X'2009'
X'200A'
X'200E'

START/STOP COMMUNICATIONS ERROR
BINARY SYNCHRONOUS COMMUNICATIONS ERROR
SNA COMMUNICATIONS ERROR
SDLC COMMUNICATIONS ERROR
X.21 NETWORK
X.25 COMMUNICATIONS ERROR
LAN COMMUNICATIONS ERROR
BANKING LOOP ERROR
STORE LOOP ERROR
ISDN COMMUNICATIONS ERROR
LOCAL DCE LOOP:
the DCE loop local to the error
notification sender.
Note: A DCE loop is the equipment comprised of cables,
converters, and the like that connect the DCE with the nearest
central office exchange; this equipment does not include the
customer premises wiring.
X'200F' REMOTE DCE LOOP: The DCE loop remote from the error
notification sender.
X'2010' DDS NETWORK:
A network implementing the Digital Data
Services, e.g., the DATAPHONE2 Digital Service (DDS).
X'2040' INTER-EXCHANGE NETWORK:
A network providing services
between two local exchange areas
X'204l' PRIVATE NETWORK REACHED:
The private network containing
the called DTE

2

8-64

DATAPHONE is the Registered Service Mark of AT&T Company.

SNA Formats

MS Major Vectors
X'2050' X.21 NETWORK HAS INITIATED A TEST lOOP
Note:
The different test loops defined for X.21 networks are
documented in the CCITT X.150 Recommendation.
X'2051' ISDN NETWORK HAS INITIATED A TEST lOOP
X'2052' X.25 NETWORK HAS INITIATED A TEST lOOP
X'20AO' NO RESPONSE FROM THE X.21 NETWORK -- (sf82 qualifier)
EXPIRED
Note: The qualifier specifies the X.2l timer that has expired.
X'20AI' NO RESPONSE FROM THE ISDN NETWORK -- (sf82 qualifier)
EXPIRED
Note:
The qualifier specifies the ISDN timer that has expired.
X'20A3' SNA COMMUNICATIONS ERROR (sf82 qualifier)
X'20A4' NO RESPONSE FROM THE X.2S NETWORK -- (sf82 qualifier)
EXPIRED
Note:
The qualifier specifies the X.2S timer that has expired.
X'20AS' NO RESPONSE FROM THE X.2S NETWORK -- (sf82 qualifier)
RETRY COUNT EXPIRED
Note:
The qualifier specifies the X.2S timer for which the retry
count has expired.
X'20A6' (sf82 qualifier) LINE: The telephone line or transmission
link connecting two or more components in the network
Note:
The qualifier identifies the link segment level (LSL) on
which the line belongs.
X'20A7' (sf82 qualifier) OUTBOUND LINE:
The equipment that
connects the transmit circuits of the local DCE (i.e.,
the DCE local to the error notification sending node) to
the receive circuits of the remote DCE.
Note:
The qualifier identifies the link segment level (LSL) on
which the inbound line belongs.
X'20A8' (sf82 qualifier) INBOUND LINE:
The equipment that
connects the receive circuits of the local DCE (i.e., the
DCE local to the error notification sending node) to the
transmit circuits of the remote DCE.
Note:
The qualifier identifies the link segment level (LSL) on
which the outbound line belongs.
X'20Bl' X.25 COMMUNICATIONS ERROR -- THE FOLLOWING DIAGNOSTIC
PACKET WAS RECEIVED FROM THE NETWORK (sf82 qualifier)
Note:
The qualifier specifies the diagnostic code.
X'20B2' X.2S PROTOCOL VIOLATION DETECTED (sf82 qualifier)
Note:
The qualifier specifies the diagnostic code.
X'20CI' X.25 COMMUNICATIONS ERROR -- THE FOLLOWING INDICATION
PACKET WAS RECEIVED FROM THE NETWORK (sf82 qualifier)
(sf82 qualifier)
Note:
The first qualifier specifies the packet type (reset,
restart, or clear) and the cause code.
The second qualifier
specifies the diagnostic code. This code point is sent when an
error is detected after end-to-end LLC communication has been
established.
Contrast with code point X'23CI'.
X'20C2' X.2S COMMUNICATIONS ERROR -- THE DTE SENT THE FOLLOWING
REQUEST PACKET TO THE NETWORK (sf82 qualifier) (sf82
qualifier)
Note:
The first qualifier specifies the packet type (reset,
restart, or clear) and the cause code. The second qualifier
specifies the diagnostic code. This code point is sent when an

Chapter 8.

Common Fields

8-6S

MS Major Vectors
error is detected after end-to-end LLC communication has been
established. Contrast with code point X'23C2'.
X'2l00' COMMUNICATIONS/REMOTE NODE: Either a communication facility
denoted by a X'20xx' code point or a remote node denoted by a
X'22xx' code point
Note: This code point is used only when a more specific probable
cause cannot be determined.
X'2l0l'
X'2l02'
X'2l04'
X'2l07'
X'2l0A'

START/STOP COMMUNICATIONS/REMOTE NODE
BINARY SYNCHRONOUS COMMUNICATIONS/REMOTE NODE
SDLC COMMUNICATIONS/REMOTE NODE
LAN LLC COMMUNICATIONS/REMOTE NODE
ISDN COMMUNICATIONS/REMOTE NODE

X'2200' REMOTE NODE: The node at the remote end of a link connection
Note: "Remote" is defined from the point of view of the node
detecting the Alert condition.
X'220l' CALLED DTE
X'2202' CALLED DTE SIGNALLING CONTROLLED NOT READY: The called
DTE has indicated that it is temporarily unable to accept
incoming calls for circuit-switched service
Note: This condition is unique to X.2l.
X'2203' CALLED DTE SIGNALLING UNCONTROLLED NOT READY: The called
DTE has indicated that it is unable to enter an
operational state for accepting an incoming call
Note: This condition is unique to X.21.
X'2204' OTHER REMOTE NODE: On a multidrop link, the remote node
interfering with the link activity but not part of the
logical connection for which the error was detected.
X'22AO' REMOTE NODE (sf82 qualifier)
X'2300' CONNECTION NOT ESTABLISHED: A telephone connection required for
the requested operation has not been established
X'2306' NEW TELEPHONE NUMBER ASSIGNED TO CALLED DTE
X'2307' CALLED NUMBER OUTSIDE OF NUMBERING PLAN OR UNKNOWN BY THE
NETWORK
X'2308' ACCESS BARRED: The calling DTE is not allowed to connect
to the called DTE
X'2309' SPEED CLASSES INCOMPATIBLE: The called DTE is operating
at a different speed from the calling DTE
X'230A' USER CLASSES OF SERVICE INCOMPATIBLE: The user class of
s~rvice of the called DTE is incompatible with that of
the calling DTE
X'23Cl' X.25 COMMUNICATIONS NOT ESTABLISHED -- THE FOLLOWING
INDICATION PACKET WAS RECEIVED FROM THE NETWORK (sf82
qualifier) (sf82 qualifier)
Note: The first qualifier specifies the packet type (reset,
restart, or clear) and the cause code. The second qualifier
specifies the diagnostic code. This code point is sent when an
error is detected before end-to-end LLC communication has been
established. Contrast with code point X'20Cl'.

8-66

SNA Formats

MS Major Vectors
X'23C2' X.2S COMMUNICATIONS NOT ESTABLISHED -- THE DTE SENT THE
FOLLOWING REQUEST PACKET TO THE NETWORK (sf82 qualifier)
(sf82 qualifier)
Note: The first qualifier specifies the packet type (reset,
restart, or clear) and the cause code. The second qualifier
specifies the diagnostic code. This code point is sent when an
error is detected before end-to-end LLC communication has been
established. Contrast with code point X'20C2'.
X'2600' INTERFERENCE: An electric disturbance in a communication system
that interferes with or prevents reception of a signal or of
information

X'3000' CHANNEL FAILURE:
The equipment that is used to direct data to and
from input/output devices and locally attached control units has
experienced a failure
X'3100' CONTROLLER FAILURE: A communication device that controls other
devices and the flow of information to and from them has
experienced a failure
X'311l' COMMUNICATION CONTROLLER:
A communication device that
controls the transmission of data over lines in a network
Note:
In SNA a communication controller is a type 4 node.
X'3l2l' TERMINAL CONTROL UNIT: A communication device that
controls the transmission of data to and from terminals
X'3200' COMMUNICATIONS INTERFACE: The equipment connecting a node to the
component in a link connection with which it exchanges physical
control signals
X'3220' LOCAL TOKEN-RING ADAPTER INTERFACE: The programming
interface for the local token-ring adapter
X'3221' CSMA/CD ADAPTER INTERFACE: The programming interface for
the local CSMA/CD adapter
X'32D1' LOCAL DCE COMMUNICATIONS INTERFACE (sf82 qualifier) (sf82
qualifier) (sf82 qualifier): The communication interface
between the Alert sender and the local Data
Circuit-Terminating Equipment (DCE)
Note:
The qualifiers identify the standards, protocols, and other
characteristics that characterize the interface, e.g., RS-232C,
1200 BPS, V.24.
X'32D2' REMOTE DCE COMMUNICATIONS INTERFACE (sf82 qualifier) (sf82
qualifier) (sf82 qualifier): The communication interface
between the Data Circuit-Terminating Equipment (DCE)
remote from the Alert sender and the remote node
Note:
The qualifiers identify the standards, protocols, and other
characteristics that characterize the interface, e.g., RS-232C,
1200 BPS, V.24.
X'32D3' REMOTE DCE COMMUNICATIONS INTERFACE (sf82 qualifier) (sf82
qualifier) (sf82 qualifier): The communication interface
between the Alert sender and the DCE emulation cable that
attaches it to a device's DCE interface cable

Chapter 8.

Common Fields

8-67

MS Major Vectors
Note:
The qualifiers identify the standards, protocols, etc. that
characterize the interface, e.g., RS-232C, 1200 BPS, V.24.
X'3300' ADAPTER: The part of a device that interfaces between a processor
in the device and one or more attached devices
Note:
The processor referred to here could be either the main
processor in the node containing the adapter or a processor in,
e.g., a communication subsystem controller.
X'3301'
X'3302'
X'3303'
X'3304'
X'330S'
X'3306'
X'3307'
X'3309'
X'330A'
X'330B'
X'330C'
X'330D'
X'330E'
X'330F'

CHANNEL ADAPTER
COMMUNICATIONS ADAPTER
DASD ADAPTER
DISPLAY/PRINTER ADAPTER
DIRECT-ATTACHED ADAPTER
DISKETTE ADAPTER
ENCRYPTION/DECRYPTION ADAPTER
LINE ADAPTER
LOOP ADAPTER
PARALLEL INTERFACE ADAPTER
SERIAL INTERFACE ADAPTER
TAPE ADAPTER
CONSOLE ADAPTER
HPTSS ADAPTER:
A high-speed processor transmission
subsystem adapter in a communication controller
X'3310' LOCAL ISDN ADAPTER:
An adapter that attaches the Alert
sender to an ISDN network
Note:
See also code point X'3S32' LOCAL ISDN TERMINAL ADAPTER.
A
terminal adapter is distinguished from an ISDN adapter by the
presence of a defined interface (e.g., RS-232C) between itself and
the node that it serves; an ISDN adapter is typically integrated
within its node.
X'3311' REMOTE ISDN ADAPTER:
An adapter that attaches to an ISDN
network a node with which the Alert sender has a logical
connection utilizing the network
Note:
See also code point X'3S33' REMOTE ISDN TERMINAL ADAPTER.
X'3320' LOCAL TOKEN-RING ADAPTER:
An adapter that attaches the
Alert sender to a token-ring LAN
X'3321' REMOTE TOKEN-RING ADAPTER:
An adapter that attaches a
node other than the Alert sender to a token-ring LAN
X'3322' LOCAL CSMA/CD ADAPTER:
An adapter that attaches the Alert
sender to a CSMA/CD LAN
X'3323' REMOTE CSMA/CD ADAPTER:
An adapter that attaches a node
other than the Alert sender to a CSMA/CD LAN
X'3324' TOKEN-RING ADAPTER:
An adapter that attaches a node to a
token-ring LAN
X'332S' CSMA/CD ADAPTER:
An adapter that attaches a node to a
CSMA/CD LAN
X'33AO' LINE ADAPTER MULTIPLEXER (sf82 qualifier):
A line adapter
(scanner) multiplexer in a communication controller
Note:
The qualifier identifies the line address for the failing
multiplexer.
X'33CO' LINE ADAPTER (sf82 qualifier) (sf82 qualifier):
A line
adapter (scanner) in a communication controller

8-68

SNA Formats

MS Major Vectors
Note:
The qualifiers identify the line adapter number and the
line address range for the failing adapter.
X'33Cl' LINE ADAPTER HARDWARE (sf82 qualifier) (sf82 qualifier):
The hardware comprising a line adapter (scanner) in a
communication controller
Note:
The qualifiers identify the line adapter number and the
line address range for the failing adapter.
X'33C2' LINE ADAPTER MICROCODE (sf82 qualifier) (sf82 qualifier):
The microcode executing .in a line adapter (scanner) in a
communication controller
Note:
The qualifiers identify the line adapter number and the
line address range for the failing adapter.
X'33C3' LINE INTERFACE COUPLER (LIC) (sf82 qualifier) (sf82
qualifier)
Note:
The qualifiers identify the line address and the LIC
position for the failing LIC.
X'3400' CABLE LOOSE OR DEFECTIVE:
A cable or its connectors used to
electrically connect devices together is loose or defective
X'340l' LOCAL DCE INTERFACE CABLE: The cable, or its connectors,
between the Alert sender and the local Data
Circuit-Terminating Equipment (DCE)
X'3403' REMOTE DCE INTERFACE CABLE:
The cable, or its connectors,
between the Alert sender's remote DCE and the device
attached to it.
X'3404' DCE EMULATION CABLE: The cable, or its connectors,
between the Alert sender and a DCE interface cable
attached to a device
Note:
The end of the DCE emulation cable remote from the Alert
sender plugs directly into the DCE interface cable attached to the
device.
X'34ll' CHANNEL INTERFACE CABLE:
The cable or cables, or their
connectors, between a channel and a locally attached
device
X'3426' CSMA/CD LAN CABLES:
The cables in a CSMA/CD LAN.
These
include the cable attaching the alert sender to the
CSMA/CD bus and the bus itself
X'3434' LOCAL LOBE CABLES:
The cables between the reporting node
and its access unit on a token-ring LAN
X'3435' REMOTE LOBE CABLES:
The cables between a remote node and
its access unit on a token-ring LAN
X'3436' LOCAL CSMA/CD ADAPTER CABLE: The cable attaching the
Alert sender to the CSMA/CD bus
X'344l' LOOP CABLE:
A cable connecting the nodes attached to a
communication loop
X'345l' DEVICE CABLE:
A cable connecting a device directly to a
communication controller or a control unit
X'3452' STORAGE DEVICE CABLE: A cable directly connecting a local
storage device to its adapter/controller
X'3460' INTERNAL CABLE
X'346l' LINE ADAPTER MULTIPLEXER CABLE
X'3480' TWINAXIAL CABLE DISTRIBUTION ASSEMBLY

Chapter 8.

Common Fields

8-69

MS Major Vectors
X'34AO' Csf82 qualifier) LOCAL DCE INTERFACE CABLE:
On a
particular link segment, the DCE interface cable nearer
to the error notification sender
Note:
The qualifier identifies the link segment level CLSL) on
which the DCE belongs.
X'34AI' Csf82 qualifier) REMOTE DCE INTERFACE CABLE On a
particular link segment, the DCE interface cable farther
from the error notification sender
Note:
The qualifier identifies the link segment level CLSL) on
which the DCE belongs.
X'3500' COMMUNICATION EQUIPMENT:
External equipment used to connect
devices or other system components
Note:
If the attaching equipment is known to be a modem, then a
modem code point (X'36xx') is sent instead of this code point.
X'350l' PROTOCOL CONVERTER:
A device that converts one protocol
data stream to another. This code point applies to a
protocol converter providing conversion between any two
data streams regardless of whether attached via a
communications link and/or a local attachment link such
as 327X coaxial link or 525X twinaxial link. Protocols
involved can include SDLC, BISYNC, ASYNC, 327X and 525X.
Note:
This code point is not to be used for a X.25 Packet
Assembler-Disassembler CX.25 Pad).
X'3502' TERMINAL MULTIPLEXER: The equipment used to connect
multiple devices to a single cable
X'3503' LINE SWITCH:
A device that on demand allows Data
Circuit-Terminating Equipment (DCE) to be attached to
different Data Terminal Equipment" (DTE) ports. The device
supports both digital switching for the DCE-DTE interface
and also the switching of the analog interface between
the DCE and the communication facility (line).
X'3504' AUTO-CALL UNIT:
A stand-alone or integrated unit used to
establish connection on a switched communication line and
connected in parallel with the modem used for data
transmission but connected to the DTE via a separate
interface (i.e., EIA-366/CCITT V.25).
X'3506' LOCAL DIGITAL DATA DEVICE:
On a particular link segment,
the digital data device (DDD) nearer to the Alert sender
X'3507' REMOTE DIGITAL DATA DEVICE:
On a particular link segment,
the digital data device (DDD) farther from the Alert
sender
X'35l0' CALLED DCE
X'35ll' LINE: The telephone line or transmission link connecting
two or more components in the network
X'35l2' THE CONNECTION BETWEEN THE CALLING DCE AND ITS LOCAL DSE
X'35l3' LOCAL LOOP ASSOCIATED WITH THE CALLED DTE
X'3520' X.2l NETWORK COMPONENT
X'352l' TEMPORARY LACK OF RESOURCES IN THE X.2l NETWORK
X'3522' LONG-TERM LACK OF RESOURCES IN THE X.2l NETWORK
X'3530' ISDN NETWORK COMPONENT
X'353l' ISDN NETWORK TERMINATION (NTl):
A device, normally
residing on the user's premises, that provides

8-70

SNA Formats

MS Major Vectors
conversion, for basic-rate ISDN service, between the
4-wire interface seen by the user and the 2-wire
interface seen by the ISDN service provider
X'3532' LOCAL ISDN TERMINAL ADAPTER:
The terminal adapter local
to the Alert sender
Note:
See also code point X'3310' LOCAL ISDN ADAPTER.
A terminal
adapter is distinguished from an ISDN adapter by the presence of a
defined interface (e.g., RS-232C) between itself and the node that
it serves; an ISDN adapter is typically integrated within its
node.
X'3533' REMOTE ISDN TERMINAL ADAPTER: The terminal adapter that
attaches to an ISDN network a node with which the Alert
sender has a logical connection utilizing the network
Note:
See also code point X'3311' REMOTE ISDN ADAPTER.
X'3534' TEMPORARY LACK OF RESOURCES IN THE ISDN NETWORK
X'3535' LONG-TERM LACK OF RESOURCES IN THE ISDN NETWORK
X'3541' LOCAL DCE: The Data Circuit-Terminating Equipment (DCE)
nearer to the error notification sender
Note:
This code point is used only if the Alert sender is unable
to determine whether the DCE is a modem or a DOD; see code points
X'3506' and X'3601'.
X'3542' REMOTE DCE: The Data Circuit-Terminating Equipment (DCE)
farther from the error notification sender
Note:
This code point is used only if the Alert sender is unable
to determine whether the DCE is a modem or a DDD; see code points
X'3507' and X'3603'.
X'3550' X.25 NETWORK COMPONENT
X'3551' SHORT-TERM CONGESTION IN THE X.25 NETWORK
X'3552' LONG-TERM CONGESTION IN THE X.25 NETWORK
X'35AO' (sf82 qualifier) LOCAL DSU/CSU:
On a particular link
segment, the DSU/CSU nearer to the error notification
sender
Note:
The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'35Al' (sf82 qualifier) REMOTE DSU/CSU:
On a particular link
segment, the DSU/CSU farther from the error notification
sender
Note:
The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'35A2' (sf82 qualifier) LOCAL DCE:
On a particular link segment,
the DCE nearer to the error notification sender
Note:
The qualifier identifies the link segment level (LSL) on
which the DCE belongs.
X'35A3' (sf82 qualifier) REMOTE DCE:
On a particular link
segment, the DCE farther from the error notification
sender
Note:
The qualifier identifies the link segment level (LSL) on
which the DCE belongs.
X'3600' MODEM:
A device or functional unit that modulates and demodulates
signals transmitted over data communication facilities
X'3601' LOCAL MODEM:
The modem connected to the error
notification sender

Chapter 8.

Common Fields

8-71

MS Major Vectors

\~'

X'3602' LOCAL LINK DIAGNOSTIC UNIT:
A device that connects to
both sides of a local modem and provides Link Problem
Determination Aid (LPDA) data for digital and analog
links with non-intelligent IBM or non-IBM modems
X'3603' REMOTE MODEM: The modem remote from the error
notification sender
X'3604' REMOTE LINK DIAGNOSTIC UNIT:
A device that connects to
both sides of a remote modem and provides Link Problem
Determination Aid (LPDA) data for digital and analog
links with non-intelligent IBM or non-IBM modems
X'3621' LOCAL ENHANCED MODEM:
The enhanced modem connected to the
Alert sender
Note:
An enhanced modem can provide functions in addition to
modulation/demodulation, such as establishing switched connections
and storing dial digits.
X'~6~O' (sf82 qualifier) LOCAL MODEM:
On a particular link
segment, the modem nearer to the error notification
sender
Note:
The qualifier identifies the link segment level (LSL) on
which the modem belongs.
X'36AI' (sf82 qualifier) REMOTE MODEM:
On a particular link
segment, the modem farther from the error notification
sender
Note:
The qualifier identifies the link segment level (LSL) on
which the modem belongs.
X'36A2' Csf82 qualifier) LOCAL MODEM FEATURE(S)
Note:
The qualifier identifies the link segment level (LSL) on
which the modem belongs.
X'36A3' Csf82 qualifier) REMOTE MODEM FEATURECS)
Note:
The qualifier identifies the link segment level (LSL) on
which the modem belongs.
\

X'3700' LAN COMPONENT:
A component of a local area network.
On a
token-ring LAN, the LAN components include the adapters, bridges,
access units, repeaters, repeater/amplifiers, and the LAN cable.
On a CSMA/CD LAN, the LAN components include the adapters,
bridges, LAN cables, taps, splitters, amplifiers, and translator
units.
Note:
This default code point is used to indicate that some
unspecified LAN component is a failure cause.
Individual LAN
components are denoted by repla~ement code points under X'3700',
with the exception of the LAN cable, which falls under CABLE LOOSE
OR DEFECTIVE (X'3400'), and the LAN adapters, which fall under
ADAPTER (X'3300').
X'3701' TOKEN-RING LAN COMPONENT
X'3703' TOKEN-RING FAULT DOMAIN:
An adapter, its nearest active
upstream neighbor, and the token-ring media between them;
the token-ring media consists of the lobe cables,
portions of one or more access units, and possibly a
portion of the LAN cable
X'371l' LOCAL ACCESS UNIT:
The access unit by which the Alert
sender is attached to a token-ring LAN

8-72

SNA Formats

MS Major Vectors
Note: An access unit is an active or passive wiring concentrator
on a token-ring LAN.
X'37l2' LOCAL TOKEN-RING LOBE: A token-ring lobe attaching the
Alert sender to a token-ring
X'37l3' REMOTE ACCESS UNIT:
An access unit by which a node other
than the Alert sender is attached to a token-ring LAN
X'372l' CSMA/CD LAN COMPONENT
X'3722' CSMA/CD LAN TRANSLATOR UNIT:
A component at the head end
of a CSMA/CD bus, which accepts input at one frequency
and transmits the same data at a different frequency
X'374l' CONGESTION IN LAN BRIDGE:
Frames are arriving at a bridge
faster than they can be forwarded by that bridge and, as
a result, some frames are discarded
X'5000' MEDIA: A tape, disk, diskette, or paper (or other data medium)
that is required to read data from or write data on
X'500l' DASD MEDIA: The medium used in a direct access storage
device; it may be either removable or non-removable
X'5002' DISKETTE: A thin, flexible magnetic disk in a semi-rigid
protective jacket, in which the disk is permanently
enclosed; also termed a floppy diskette
X'5003' TAPE: A recording medium in the form of a ribbon that has
one or more tracks along its length; magnetic recordings
can be made on either one or both sides
X'5200' MEDIA JAM:
The medium (usually paper, forms or cards) 1S jammed
in the machine and operator action is required to correct the
problem.
X'S20l'
X'5202'
X'5203'
X'5204'

CARD JAM
FORMS JAM
PAPER JAM
FILM JAM

X'6000' DEVICE: An input, output, or input/output device (e.g., a
terminal or disk drive)
X'6100' INPUT DEVICE:

A device that is used to enter data into a system

X'6ll0' KEYBOARD:
An arrangement of alphanumeric, special
character, and function keys laid out in a specified
manner and used to enter information into a terminal, and
thereby into a system
X'6111' KEYPAD:
A specialized keyboard with an arrangement of a
limited number of alphanumeric, special character, and/or
function keys
X'6ll2' SELECTOR PEN: A light-sensitive pen used in display
operations
X'6ll3' MICR READER/SORTER:
A magnetic ink character recognition
reader/sorter
X'6l14' MAGNETIC STRIPE READER (MSR):
A device that reads data
from a card containing a magnetic stripe

Chapter 8.

Common Fields

8-73

MS Major Vectors
X'6200' OUTPUT DEVICE:

A device that receives data from a system

X'62l0' PRINTER:
An output device that produces durable and
optically viewable output in the form of characters (and
optionally graphics) by a means other than by drawing
with one or more pens
Note:
Contrast with code point X'62l3' PLOTTER.
X'62ll' COPIER:
An output device that produces one or more copies
of an original without affecting the original
X'62l2' CAMERA:
An output device that combines electronic data
with a visual image on a single visual medium
X'62l3' PLOTTER: An output device that produces graphic and/or
character output by means of one or more pens that draw
on the surface of the output medium
Note:
Contrast with code point X'62l0' PRINTER.
X'6220' PRINTER CASSETTE:
A removable container for feeding paper
to a printer
X'6300' INPUT/OUTPUT DEVICE:
A device whose parts can be performing an
input process and output process at the same time, such as a card
reader/punch
X'630l' DISPLAY/PRINTER:
A device that has either of the
characteristics of a display or printer or both.
This
code point is used only when the Alert sender cannot
determine whether the attached device is a display or
printer
X'6302' DISPLAY: A workstation that requires a host connection in
order to function; typically a display includes both a
monitor and a keyboard
X'6309' STORAGE DEVICE:
The device cannot be specifically
identified as disk, tape, optical, etc.
X'63l0' DISK DRIVE:
The primarily mechanical component of a DASD
device, directly involved with transferring data to and
from the medium
X'63l1' DISKETTE DRIVE:
The primarily mechanical component of a
diskette device, directly involved with transferring data
to and from the medium
X'63l2' OPTICAL DISK DEVICE:
A direct access storage device that
uses an optical disk as the storage medium.
The disk may
be either removable or non-removable
X'63l3' TERMINAL:
A device in a system or network at which data
can either enter or leave. A terminal is usually
equipped with a keyboard and a display device, and is
capable of sending and receiving information
X'63l4' TAPE DRIVE:
The primarily mechanical component of a tape
drive, directly involved with transferring data to and
from the medium
X'63lS' CONSOLE: A terminal used for communication between an
operator and a processor
X'63l7' MAGNETIC STRIPE READER/ENCODER:
A device that reads data
from, and in some cases writes data to, a card containing
a magnetic stripe

8-74

SNA Formats

MS Major Vectors
X'6330' DISK DRIVE ELECTRONICS: The electronic components of a
DASD device
X'6350' LOCAL CONSOLE
X'635l' REMOTE CONSOLE
Note: "Local" and "remote" are defined with respect to the system
with which the console communicates.
X'6400' DEPOSITORY:

A device that receives items into a system

X'640l' ENVELOPE DEPOSITORY:
A device that receives into a system
items sealed in an envelope. The envelope is not opened,
nor are its contents examined by the system; the envelope
is stored for human action
X'6402' CHECK DEPOSITORY: A device that receives checks into a
system, then reads and retains them.
It may also
transfer information to a check and return the check to a
user
X'6403' CARD DEPOSITORY: A device that retains credit, personal
banking, or other cards used to access a PBM
X'6500' DISPENSER:

A device that dispenses items to a user of a system

X'6501' DOCUMENT DISPENSER:
primarily bills
X'6502' TICKET DISPENSER
X'6503' KEY DISPENSER
X'6504' COIN DISPENSER

A device that dispenses documents,

X'6600' SELF-SERVICE TERMINAL: A device that allows a customer of a
business to perform a transaction that would otherwise require
assistance by personnel of the business
X'660l' PERSONAL BANKING MACHINE:
A self-service terminal for
financial transactions
X'6630' TELLER ASSIST UNIT: A terminal that assists a financial
teller in transactions
Note: This device does not fit the strict definition of a
self-service terminal, since it is used by personnel of a
financial institution; it is included in this range becuase it is
very close in function to other self-service terminals.

X'EOOO'-X'EFFF' Reserved
Note: This range of code points is reserved for use by
non-IBM products and customer written applications.
No
IBM product will send a code point from within this range.
Note: The following code points specify extended messages, that provide
additional information on one or more failure causes that have already
been specified. An Alert receiver that displays only default text
provides no display for these code points.
X'FOOO' (no display):

Additional message data

Chapter 8.

Common Fields

8-75

MS Major Vectors
X'FOOl'
X'FOOZ'
X'F003'
X'FOOC'
X'FOOD'
X'FOOE'
X'FOOF'
X'FOIO'
X'FOll'
X'FOIZ'
X'F013'
X'F014'
X'F015'
X'F016'
X'F017'
X'F018'
X'F019'
X'FOIA'
X'FOIB'
X'FOIC'
X'FOID'
X'FOIE'
X'FOIF'
X'FOZO'
X'FOZl'
X'F02Z'
X'FOZ3'
X'F030'
X'F031'
X'F03Z'
X'F033'
X'F034'
X'F035'
X'F036'
X'F037'
X'F038'
X'F039'
X'F03A'
X'F03B'
X'F03C'
X'F03D'
X'F040'
X'F041'
X'F04Z'
X'F043'
X'F044'
X'F050'
X'F051'
X'F05Z'
X'F053'

8-76

SNA Formats

UNSOLICITED INTERRUPT RECEIVED
DATA LOST DURING RESTORE TO DISK
IPL OCCURRED DUE TO A HARD WAIT
CRC/LRC RETRY LIMIT REACHED
IDLE DETECT TIMEOUT RETRY LIMIT REACHED
NON-PRODUCTIVE RECEIVE TIMEOUT RETRY LIMIT REACHED
RNR RECEIVED THRESHOLD REACHED
FRAME REJECT RECEIVED: INVALID/UNSUPPORTED COMMAND OR
RESPONSE SENT
FRAME REJECT RECEIVED: I-FIELD SENT WHEN NOT PERMITTED
FRAME REJECT RECEIVED: INVALID N(R) SENT
FRAME REJECT RECEIVED: MAXIMUM I-FIELD LENGTH EXCEEDED
FRAME REJECT RECEIVED: NO REASON SPECIFIED
SNRM RECEIVED WHILE IN NRM
SABME RECEIVED WHILE IN ABME
POLL COUNT EXHAUSTED
XID POLL COUNT EXHAUSTED
INACTIVITY TIMER EXPIRED
DM RECEIVED
RECEIVE WINDOW SIZE EXCEEDED
LLC LEVEL CRC OR CHECK SUM ERROR THRESHOLD REACHED
LREJ RECEIVED THRESHOLD REACHED
LREJ SENT THRESHOLD REACHED
PASSWORD NOT FOUND
INVALID/UNSUPPORTED COMMAND OR RESPONSE RECEIVED
I-FIELD RECEIVED WHEN NOT PERMITTED
INVALID N(R) RECEIVED
RECEIVED I-FIELD EXCEEDED MAXIMUM LENGTH
CTS DROPPED
CTS FAILED TO DROP
DSR FAILED TO DROP
RTS NOT RAISED BUT CTS IS ACTIVE
CTS FAILED TO RISE
DSR DROPPED
DSR IS PRESENT BEFORE DTR IS RAISED
DSR NOT PRESENT AFTER DTR IS RAISED
CARRIER DETECT LOST
DLO INITALLY ON
DLO DID NOT COME ACTIVE DURING CALL REQUEST
PND FAILED TO COME ACTIVE IN THE REQUIRED TIME
DSC DID NOT COME ACTIVE AFTER A CALL REQUEST WAS COMPLETED
DSR DID NOT COME ACTIVE WHILE ATTEMPTING AN AUTO-CALL
CONNECTION
TRANSMISSION UNDERRUN THRESHOLD REACHED
EXCESSIVE TRANSMIT PROCEDURE TIMEOUTS
RECEIVE OVERRUN THRESHOLD REACHED
EXCESSIVE RECEIVE PROCEDURE TIMEOUTS
RECEIVE QUEUE OVERRUN
DCE NOT READY
DCE CLEAR INDICATION DURING CALL ESTABLISHMENT
PERSISTENT DCE CLEAR INDICATION DURING CALL ESTABLISHMENT
(T6 TIMER EXPIRED)
DCE CONTROLLED NOT READY DURING CALL ESTABLISHMENT

MS Major Vectors
X'F054' PERSISTENT DCE CONTROLLED NOT READY DURING CALL
ESTABLISHMENT (T6 TIMER EXPIRED)
X'F055' DCE FAULT CONDITION DURING CALL ESTABLISHMENT
X'F056' DCE CLEAR INDICATION RECEIVED DURING DATA PHASE
X'F057' PERSISTENT DCE CLEAR INDICATION RECEIVED DURING DATA PHASE
(T6 TIMER EXPIRED)
X'F05B' UNRECOGNIZED CALL PROGRESS SIGNAL RECEIVED FROM THE
NETWORK
X'F059' INVALID CALL PROGRESS SIGNAL RECEIVED FROM THE NETWORK
X'F05A' DSR OR CTS DROPPED
X'F05B' FAN-OUT FEATURE IN ERROR
X'F060' DATA BLOCKS IN ERROR THRESHOLD REACHED
X'F06l' TTD'S TRANSMITTED THRESHOLD REACHED
X'F062' WACK'S TRANSMITTED THRESHOLD REACHED
X'F063' SYNC TIMEOUT THRESHOLD REACHED
X'F064' CONTINUOUS SYNC TIMEOUT RETRY LIMIT REACHED
X'F065' NO SYNC RECEIVED TIMEOUT RETRY LIMIT REACHED
X'F066' NO DATA RECEIVED TIMEOUT RETRY LIMIT REACHED
X'F067' INVALID RESPONSE TO TTD RETRY LIMIT REACHED
X'F06B' INVALID RESPONSE TO WACK RETRY LIMIT REACHED
X'F069' TTD/WACK NO RESPONSE TIMEOUT RETRY LIMIT REACHED
X'F06A' TRANSMIT RETRY LIMIT REACHED
X'F06B' ENQ RECEIVED TO ACK SENT RETRY LIMIT REACHED
X'F06C' UNRECOGNIZABLE DATA RECEIVED RETRY LIMIT REACHED
X'FOAl' ERROR OCCURRED READING FROM FILE (sfB2 qualifier)
X'FOA2' ERROR OCCURRED WRITING TO FILE (sfB2 qualifier)
X'FOA3' FAILURE OCCURRED ON (sfB2 qualifier)
Note: The qualifier identifies the location of the failure being
reported. It may identify the processor on which a failure
occurred e.g.1 the failing communication control unit in a
communication controller.
X'FOA4' XID NEGOTIATION FAILED WITH (sfB2 qualifier)
Note: The qualifier specifies the SNA sense data identifying why
the negotiation failed.
X'FOA5' COMPONENT OF (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the equipment or service belongs.
X'FOA6' BAD LINE QUALITY ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the line belongs.
X'FOA7' BOTH MODEMS DETECTED IMPULSE HITS ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the impulse hits were detected.
X'FOAB' NO LPDA RESPONSE FROM THE LOCAL MODEM ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the local modem belongs.
X'FOA9' NO LPDA RESPONSE FROM THE REMOTE MODEM ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the remote modem belongs.
X'FOAA' NO LPDA RESPONSE FROM THE LOCAL DSU/CSU ON (sfB2
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
l

Chapter B.

Common Fields

B-77

MS Major Vectors
X'FOAB' NO LPDA RESPONSE FROM THE REMOTE DSU/CSU ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'FOAC' INCORRECT LPDA RESPONSE FROM THE LOCAL DSU/CSU ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'FOAD' INCORRECT LPDA RESPONSE FROM THE REMOTE DSU/CSU ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'FOAE' BIPOLAR ERRORS DETECTED BY LOCAL DSU/CSU ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the local DSU/CSU belongs.
X'FOAF' BIPOLAR ERRORS DETECTED BY REMOTE DSU/CSU ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the remote DSU/CSU belongs.
X'FOBO' IMPULSE HITS DETECTED BY THE LOCAL MODEM ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the hits were detected.
X'FOBl' LOCAL DSU/CSU DETECTED REMOTE DSU/CSU FAILURE ALARM ON
(sf82 qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'FOB2' LOCAL MODEM DETECTED REMOTE MODEM FAILURE TONE ON (sf82
qualifier)
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'FOB3' MODEMS ON (sf82 qualifier) IN BACKUP SPEED
Note: The qualifier identifies the link segment level (LSL) on
which the modems belong.
X'FOB4' Csf82 qualifier) LOCAL DSU/CSU RECEIVED OUT OF FRAME DDS
NETWORK CODE
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'FOBS' (sf82 qualifier) REMOTE DSU/CSU RECEIVED OUT OF FRAME DDS
NETWORK CODE
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'FOB6' (sf82 qualifier) LOCAL DSU/CSU RECEIVED OUT OF SERVICE DDS
NETWORK CODE
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'FOB7' (sf82 qualifier) REMOTE DSU/CSU RECEIVED OUT OF SERVICE
DDS NETWORK CODE
Note: The qualifier identifies the link segment level (LSL) on
which the DSU/CSU belongs.
X'FOB8' (sf82'qualifier) LOCAL DSU/CSU DETECTED DDS NETWORK
LOOPBACK ACTIVE

8-78

SNA Formats

MS Major Vectors
Note:
The qualifier identifies
which the DSU/CSU belongs.
X'FOB9' (sf82 qualifier) REMOTE
LOOPBACK ACTIVE
Note: The qualifier identifies
which the DSU/CSU belongs.
X'FOBA' INCORRECT LPDA RESPONSE
qualifier)
Note: The qualifier identifies
which the local modem belongs.
X'FOBB' INCORRECT LPDA RESPONSE
qualifier)
Note: The qualifier identifies
which the remote modem belongs.

the link segment level (LSL) on
DSU/CSU DETECTED DDS NETWORK
the link segment level (LSL) on
FROM THE LOCAL MODEM ON (sf82
the link segment level (LSL) on
FROM THE REMOTE MODEM ON (sf82
the link segment level (LSL) on

X'F800' (no display): Additional message data
Note: The X'F8xx' range is used for additional messages that are
identical for User? Install, and Failure Causes.
X'F8CO' FAILING COMPONENT IS IDENTIFIED BY (sf82 qualifier) (sf82
qualifier)
Note: The qualifiers identify the failing component by means of
its logical location? e.g., its port number and device address.
X'F8DO' PROBLEM IS RELATED TO THE CONTROLLER LOCATED AT (sf82
qualifier) (sf82 qualifier) (sf82 quqlifier)
Note: The qualifiers identify the controller location as follows:
QI
Q2
Q3

= RACK
= UNIT

(within a rack)
CARD SLOT (within a unit)

X'F8EO' FAILING COMPONENT IS IDENTIFIED BY (sf83 product text)
X'FFFF' Reserved

Cause Undetermined (X'97') Alert MS Subvector
This subvector transports code points for stored text
detailing the recommended actions to be taken when no
probable user?
install? or failure causes for the Alert
condition can be identified.
It may also transport
additional detailed data? to be inserted into the text
indexed by the recommended action code points.

o
I

2-p

Length (p+l)? in binary, of the Cause Undetermined subvector
Key: X'97'
One or more subfields containing recommended action data, as described 1n
"Network Alert (X'OOOO') Common Subfields" on page 8-82.
X'8l' Recommended Actions
X'82' Detailed Data
X'83' Product Set ID Index
Note:
Subfield X'81' is always present.
One or more instances of the
X'82' and/or X'83' subfields may be present? depending on the code points
present in the X'81' subfield.

Chapter 8.

Common Fields

8-79

MS Major Vectors

Detailed Data (X'9S') Alert MS Subvector
This subvector transports product specific detailed data.

o
1

2-p

length (p+l), in binary, of the Detailed Data subvector
Key:
X'98'
One or more subfields containing detailed data, as described below for
keys X'OO'-X'7F' and in "Network Alert (X'OOOO') Common Subfields" on page
8-82 for keys X'80'-X'FE'.
X'OI' Qualified Message Data
X'82' Detailed Data
Note:
Any number of instances of the X'OI' and X'82' subfields may be
present.
Each X'OI' subfield contains a number indicating how many
subsequent X'82' subfields are associated with it.

Qualified Message Data (X'Ol') Detailed Data Subfield
This subfield contains an index to a complete message
stored at an Alert receiver, as well as an indication of
how many qualifiers are to be inserted into the message.

o
1

2

length (q+l), in binary, of the Qualified Message Data subfield
Key:
X'Ol'
Product 10 code: The structure of this field is identical to that present
in the Product Set 10 Index (X'83') subfield.
bits 0-3, product 10 subvector code: a code point that specifies (1) the
type of Product 10 subvector being indexed (hardware or
software), and (2) the particular data to be extracted from this
subvector
Note: See "Product Identifier (X'II') MS Common Subvector" on
page 8-110 for the criteria distinguishing hardware and software
Product 10 subvectors.
X'O'-X'l' reserved
X'2' machine type or hardware product common name from a
hardware Product 10 subvector
Note: The hardware product common name is used if it 1S
present; otherwise, the machine type is used.
X'5' machine type or hardware product common name plus model
number from a hardware Product 10 subvector
Note: The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'9' software product common name from a software Product 10
subvector
bit 4, product set 10 indicator: An indication of which Product Set 10
(PSID) contains the Product 10 subvector being indexed
o Alert sender PSID
1 indicated resource PSID
bits 5-7, Count: A three-digit binary number that indicates which Product
10 subvector, of the type specified by the Product 10 Subvector
Code, is being indexed within the PSID specified by the Product
Set 10 Indicator.

8-80

SNA Formats

MS Major Vectors
Note: This count applies only to Product ID Subvectors of the
type specified by the Product ID Subvector Code.
If, for
example, the code is X'2' (specifying a hardware Product ID)
then only hardware X'll's are counted: a count of X'3' would
thus index the third hardware Product ID within the PSID
indicated by the Product Set ID Indicator.
3

Data ID:
A code point indicating the type of the message to be
constructed from the data carried in the subfield.
The English text
associated with each code point, or its national language equivalent, is
displayed in conjunction with the message.
Defined codes are:
X'OI' OPERATOR ERROR MESSAGE
X'EO'-X'EF' Reserved
Note: This range of code points is reserved for use by
non-IBM products and customer written applications.
No IBM
product will send a code point from within this range.

4

5

6-q

Message code encoding: a code point indicating how the accompanying
message code is encoded. This data is included because an Alert receiver
has the option of displaying the message code itself in addition to the
message that it indexes.
Defined codes are:
X'OO' hexadecimal:
the message code is to be displayed as hexadecimal
digits
X'II'
Coded Graphic Character Set 00640-00500 plus:
The data is to be
decoded using Coded Graphic Character Set 00640-00500, documented 1n
"Appendix A. SNA Character Sets and Symbol-String Types" , plus
three additional code points:
X'5B' = "$" (dollar sign); X'7B' =
"I" (pound or number sign); X'7C' = "@" (at sign)
Qualifier count: a binary number indicating how many qualifiers are
associated with this message
Note:
The qualifiers are specified in X'82' subfields following this
X'OI' subfield, and are substituted into the message in the order in which
the X'82' subfields are present.
Message code, encoded as specified in byte 4 above
Note:
This message code is limited to eight bytes.

Detail Qualifier (EBCDIC) (X'AO') Alert MS Subvector

This subvector supplies variables for the Alert function
in EBCDIC form that can be inserted on the Alert Detail
screens.
This
subvector and
the Detail
Qualifier
(hexadecimal) subvector (X'AI') are identical in function
and format except that this subvector contains EBCDIC
codes.
Note:
The Detail
Qualifier
(X'AO'-X'AI')
subvectors are displayed in the order that they appear in
the Alert major vector.

o
I

2-p

Length (p+l), in binary, of the Detail Qualifier subvector
Key:
X'AO'
Detail qualifier: a type-AE symbol-string that qualifies a reference on
the Alert Detail screen

Chapter 8.

Common Fields

8-81

MS Major Vectors
Each qualifier is p-l bytes in length, but only one qualifier is
Note:
used per Detail Qualifier subvector. All qualifiers include only codes,
numbers, or internationally recognized terms that do not require
translation. The coding is not interpreted by the Alert display
mechanism.

Detail

Quali~ier

(Hexadecimal) (X'Al') Alert MS Subvector

This subvector supplies variables for the Alert function
in hexadecimal form that can be inserted on the Alert
Detail screens.
This subvector and the Detail Qualifier
(EBCDIC) subvector (X'AO') are identical in function and
format except that this subvector contains codes in
hexadecimal.
Note: The Detail Qualifier (X'AO'-X'AI')
subvectors are displayed in the order that they appear in
the Alert major vector.

o
1

2-p

Length (p+l), in binary, of the Detail Qualifier subvector
Key:
X'Al'
Detail qualifier: a type-G symbol-string

Network Alert (X'OOOO') Common

Sub~ields

The following table shows, by key value, the subfields common to the Network Alert
subvectors, and the subvectors in which each can occur.

Key

Subfield

X'8l'

Recommended Actions

X'82'

Detailed Data

X'83'

Product Set ID Index

Applicable Network Alert Subvectors
User Causes subvector, Install Causes
subvector, Failure Causes subvector, Cause
Undetermined subvector
User Causes subvector, Install Causes
subvector, Failure Causes subvector, Cause
Undetermined subvector, Detailed Data
subvector
User Causes subvector, Install Causes
subvector, Failure Causes subvector, Cause
Undetermined subvector

Recommended Actions (X'Sl') Network Alert Common Subfield
This subfield contains code
describing recommended actions
Alert condition.

o
1

2-q

8-82

points for stored text
to be taken to rectify an

Length (q+l), in binary, of the Recommended Actions subfield
Key:
X'8l'
Two-byte recommended action code points.
Each code point provides an
index to predefined text, describing the recommended action, that is
displayed at the Alert receiver.
An Alert receiver has the option of
displaying, for each code point it receives:
either the text associated
with that code point, or its national language equivalent; or the text

SNA Formats

MS Major Vectors
associated with the default code point above it, or its national language
equivalent.
Specific defined codes and the corresponding displayed text (shown all
capitalized) are listed below. Note that the codes are grouped by the
high-order two hex digits; a low-order 2-digit value of X'OO' represents a
more general description than a non-X'OO'; for this reason, the non-X'OO'
codes are shown indented, but any of the codes can be sent. The receiver
displays the more general text (corresponding to X'**OO' code points) if
it does not recognize the more specific code point (e.g., because of
different release schedules).
The expression "(sf82 qualifier)" in the English text indicates a
variable-length gap, to be filled in with data passed in a Detailed Data
(X'82') subfield. The one or more necessary X'82' subfields follow
immediately after this subfield in the X'94' subvector, in the order in
which they are to be associated with the gaps specified in the X'81'
subfield.
The expression "(sf83 product text)" in the English text similarly
indicates a variable-length gap, to be filled in with product
identification data from the Product Identifier X'II' subvector indicated
by a Product Set ID Index (X'8~') subfield. The necessary X'83' subfields
follow immediately after the X'81' subfield, in the same subvector, in the
order in which they are to be associated with the gaps specified in the
X'81' subfield. The third digit of each user cause code point indicates
the number of succeeding X'82' subfields that are associated with the code
point, or whether a X'83' subfield is associated with it, as follows:
X'xxOx'-X'xx9x':

No X'82' subfields.

X'xxAx'-X'xxBx':

One X'82' subfield.

X'xxCx':

Two X'82' subfields.

X'xxDx':

Three X'82' subfields.

X'xxEx':

One X'83' subfield.

X'xxFx':

Reserved:
code points will not be assigned in
this range.

Defined codes are:
X'OOOO' PERFORM PROBLEM DETERMINATION PROCEDURES:
Refer to the problem
determination documentation provided for this condition and follow
the specified procedures
X'OOOI'
X'0002'
X'0003'
X'0004'
X'0005'
X'0006'

RUN ONLINE PROBLEM DETERMINATION
INVOKE INTENSIVE MODE RECORDING
DETERMINE THE REASON FOR THE LINE SHUTDOWN
DETERMINE THE REASON FOR THE LOOP SHUTDOWN
PERFORM SNA DATA STREAM PROBLEM DETERMINATION PROCEDURES
USE MICROCODE DUMP AND SYSTEM PROCEDURES TO CREATE AN APAR

Chapter 8.

Common Fields

8-83

MS Major Vectors
X'0007'
X'0008'
X'0009'
X'OOOA'
X'OOOB'
X'OOOC'
X'OOOD'
X'OOOE'
X'OOOF'
X'OOIO'
X'OOII'
X'OOI2'
X'OOI3'
X'OOI4'
X'OOI5'

PERFORM REMOTE MODEM PROBLEM DETERMINATION
PERFORM REMOTE DSU/CSU PROBLEM DETERMINATION
PERFORM OUTBOUND LINE PROBLEM DETERMINATION
PERFORM INBOUND LINE PROBLEM DETERMINATION
DETERMINE RESOURCE NAME OF THE OTHER REMOTE NODE
RUN MODEM SELF TEST WITH WRAP PLUG FROM KEYPAD
RUN DSU/CSU SELF TEST WITH WRAP PLUG FROM CONTROL PANEL
RUN MODEM AND LINE STATUS TEST
RUN DSU/CSU AND LINE STATUS TEST
RUN LINE TEST
RUN LINE ANALYSIS TEST
RUN TRANSMIT/RECEIVE TEST
RUN REMOTE NODE TEST
RUN REMOTE NODE-DCE INTERFACE WRAP TEST
INVESTIGATE INTERFERENCE FROM OTHER PORT ON LOCAL MODEM,
IF FAN-OUT INSTALLED
X'OOI6' REVIEW MODEM AND LINE STATUS DATA
X'OOI7' RUN VERIFY COMMAND
X'OOAO' PERFORM TRANSMISSION LINE PROBLEM DETERMINATION PROCEDURES
ON (sf82 qualifier)
Note: The qualifier identifies the failing transmission line.
X'OOBO' PERFORM PROBLEM DETERMINATION PROCEDURE FOR (sf82
qualifier)
Note: The qualifier identifies a value, such as a system
reference code, that selects a problem determination procedure to
be performed.
X'OOBI' PERFORM PROBLEM DETERMINATION PROCEDURE AT THE REPORTING
LOCATION FOR (sf82 qualifier)
Note: This code point differs from X'OOBO' in that it specifies
that the indicated problem determination procedure is one that
must be performed locally, at the site of the failure.
X'OOB2' RUN THE FOLLOWING AT THE REPORTING LOCATION (sf82
qualifier)
Note: The qualifier identifies the command, program, error
recovery procedure, etc.
X'OOCO' RUN SELF TEST WITH WRAP PLUG ON (sf82 qualifier) REMOTE
MODEM AND (sf82 qualifier) LOCAL MODEM FROM MODEM KEYPADS
Note: The qualifiers identify the link segment level (LSL) on
which the modems belong.
X'OOCI' RUN SELF TEST WITH WRAP PLUG ON (sf82 qualifier) REMOTE
DSU/CSU AND (sf82 qualifier) LOCAL DSU/CSU FROM DSU/CSU
CONTROL PANELS
Note: The qualifiers identify the link segment level (LSL) on
which the DSU/CSUs belong.
X'OOC2' RUN SELF TEST WITH WRAP PLUG ON (sf82 qualifier) REMOTE
MODEM (FROM KEYPAD) and (sf82 qualifier) LOCAL DSU/CSU
(FROM CONTROL PANEL)
Note: This code point is used on a multi-segment link with modems
on one segment and DSU/CSUs on the other segment.
X'OOC3' RUN SELF TEST WITH WRAP PLUG ON (sf82 qualifier) REMOTE
DSU/CSU (FROM CONTROL PANEL) and (sf82 qualifier) LOCAL
MODEM (FROM KEYPAD)
Note: The qualifiers identify the link segment level (LSL) on
which the equipment belongs. This code point is used on a

8-84

SNA Formats

MS Major Vectors
multi-segment link with modems on one segment and DSU/CSUs on the
other segment.
X'OOC4' RUN DSU/CSU AND LINE STATUS TEST ON (sf82 qualifier) AND
(sf82 qualifier)
Note: The qualifiers identify the link segment level (LSL) on
which the lines belong.
X'OOCS' RUN DCE AND LINE STATUS TEST ON (sf82 qualifier) AND (sf82
qualifier)
Note: The qualifiers identify the link segment level (LSL) on
which the lines belong.
X'OOEl' PERFORM (sf83 product text) PROBLEM DETERMINATION
PROCEDURES
X'OIOO' VERIFY
X'OlOl'
X'OlO2'
X'OlO3'
X'OlO4'
X'OlOS'
X'OlO6'
X'OlO7'
X'OlO8'
X'OlO9'
X'OlOA'
X'OlOB'
X'OlOC'

VERIFY X.2S SUBSCRIPTION NUMBER
VERIFY ADAPTER ADDRESS DEFINITION
VERI FY TELEPHONE NUMBER
CHECK FOR CORRECT MICROCODE FIX
REQUEST VERIFICATION OF MANAGEMENT SERVER REPORTING LINKS
CHECK REMOTE NODE FOR TC ACTIVE
CHECK OTHER REMOTE NODE FOR TC ACTIVE
CHECK REMOTE NODE FOR RTS ACTIVE
CHECK OTHER REMOTE NODE FOR RTS ACTIVE
CHECK CONFIGURATION OF THE SENDING NODE
CHECK CONFIGURATION OF THE SENDING NODE AND OF THE MODEMS
CHECK CONFIGURATION OF THE SENDING NODE AND OF THE
DSU/CSU'S
X'OlOD' CHECK CONFIGURATION OF THE REMOTE NODE
X'OlOF' CHECK CONFIGURATION OF THE OTHER REMOTE NODE
X'OllO' CHECK CONFIGURATION OF THE REMOTE NODE AND REMOTE MODEM
X'Olll' CHECK RTS GENERATION PARAMETER
X'Oll2' VERIFY THAT THE FAN-OUT FEATURE IS INSTALLED
X'Oll3' VERIFY THAT REMOTE NODE PROVIDES THE DCE EXTERNAL CLOCK
X'OlCO' CHECK FOR CONFIGURATION MISMATCH BETWEEN THE (sf82
qualifier) REMOTE MODEM AND (sf82 qualifier) LOCAL MODEM
Note: The qualifiers identify the link segment level (LSL) on
which the modems belong.
X'OlCl' CHECK FOR CONFIGURATION MISMATCH BETWEEN THE (sf82
qualifier) REMOTE MODEM AND (sf82 qualifier) LOCAL
DSU/CSU
Note: The qualifiers identify the link segment level (LSL) on
which the modem and the DSU/CSU belong. This code point is used
on a multi-segment link with modems on one segment and DSU/CSUs on
the other segment.
X'0200' CHECK POWER:

Check the electrical power supply for the device

X'0300' CHECK FOR DAMAGE:
X'030l'
X'0302'
X'0303'
X'0306'

CHECK
CHECK
CHECK
CHECK

Check for damage to the specified resource

CABLE AND ITS CONNECTIONS
CABLES AND THEIR CONNECTIONS
PHYSICAL INSTALLATION
TAPE PATH TO READ/WRITE HEAD FOR OBSTRUCTION

Chapter 8.

Common Fields

8-8S

MS Major Vectors
X'0400' RUN APPROPRIATE TEST: Refer to the appropriate documentation for
this condition and run the tests specified for this problem
X'040l' RUN CONSOLE TEST
X'0402' RUN CONSOLE LINK TEST
X'0403' RUN MODEM TESTS
X'0500' RUN APPROPRIATE TRACE: Refer to the appropriate documentation for
this condition and run the traces specified for this proble~.
X'050l' RUN COMMUNICATION LINE DATA TRACE
X'0600' OBTAIN DUMP: Perform the required operations to obtain a storage
dump (copy to external storage of the processor main storage).
The dump will be required by support personnel or service
personnel in order to resolve the problem
X'060l'
X'0602'
X'0603'
X'0604'
X'0605'
X'06l0'
X'06ll'
X'06l2'
X'06l3'
X'06l4'

TRANSFER AND PRINT MOSS DUMP
TRANSFER AND PRINT CONTROL PROGRAM DUMP
TRANSFER AND PRINT LINE ADAPTER DUMP
TRANSFER AND PRINT CHANNEL ADAPTER DUMP
TRANSFER AND PRINT TOKEN RING COUPLER DUMP
DUMP CONTROL PROGRAM
DUMP CHANNEL ADAPTER MICROCODE
DUMP LINE ADAPTER MICROCODE
DUMP MOSS MICROCODE
DUMP TOKEN RING COUPLER

X'0700' NO ACTION NECESSARY: For a given cause, no action is necessary,
e.g., the problem caused was transitory
X'070l' IF SNBU JUST DISCONNECTED THEN IGNORE
X'lOOO' PERFORM PROBLEM RECOVERY PROCEDURES: Refer to the problem
recovery documentation provided for this condition and follow the
specified procedures
X'lOOl'
X'1002'
X'1003'
X'1004'
X'1005'
X'1006'
X'1007'
X'1008'
X'1009'
X'lOOA'
X'IOOB'
X'IOOC'
X'IOOD'
X'IOOE'
X'lOlO'
8-86

SNA Formats

REFER TO OPERATOR'S GUIDE FOR CORRECTIVE ACTION
FOLLOW LOCAL BACKUP PROCEDURE
PERFORM LOOP PROBLEM RECOVERY PROCEDURES
PERFORM LAN PROBLEM RECOVERY PROCEDURES
PERFORM DISK FILE ERROR RECOVERY PROCEDURES
FOR SINGLE DRIVE FAILURES, MOVE PACK TO ANOTHER DRIVE AND
RERUN SAME JOB
REQUEST RESET OF RING ERROR MONITOR COMPONENT
REQUEST REINITIALIZATION OF LAN MANAGER
ATTEMPT TO REOPEN THE ADAPTER AFTER 30 SECONDS
REORGANIZE THE FILE
LEAVE THE ADDITIONAL WORKSTATION POWERED OFF
POWER OFF ANOTHER WORKSTATION ATTACHED TO THIS CONTROLLER
TRANSFER THE ADDITIONAL WORKSTATION TO ANOTHER CONTROLLER
LOCATE AND ELIMINATE THE SOURCE OF ELECTRICAL INTERFERENCE
REDUCE AMOUNT OF AUXILIARY STORAGE USED

MS Major Vectors
X'lOll'
X'1012'
X'1013'
X'1014'
X'1015'
X'1016'

INCREASE AMOUNT OF AUXILIARY STORAGE AVAILABLE
INCREASE AMOUNT OF MAIN STORAGE AVAILABLE
POWER OFF REMOTE MODEM
POWER OFF REMOTE DSU/CSU
POWER OFF THEN POWER ON AUTO-CALL UNIT
REDUCE THE NUMBER OF LINES/DEVICES ATTACHED TO THE
SUBSYSTEM: The subsystem is overloaded.
X'lOAl' PERFORM (sf82 qualifier)
Note: The qualifier specifies a problem recovery procedure to be
performed.
X'lOA2' FOLLOW PROBLEM RECOVERY PROCEDURE INDICATED AT PRINTER FOR
(sf82 qualifier)
Note: The qualifier specifies a value that indexes a local
problem recovery procedure.
X'lOA3' FOLLOW PROBLEM RECOVERY PROCEDURE INDICATED AT PRINTER
SERVER FOR (sf82 qualifier)
Note: The qualifier specifies a value that indexes a local
problem recovery procedure.
X'lOA4' FOR CORRECTIVE ACTION REFER TO (sf82 qualifier)
Note: The qualifier identifies the publication number of a
document where corrective actions are described and may only be
used when the implementing product will provide a single version
of the publication (i.e.1 the publication will never be translated
and therefor the publication number will never be changed).
X'llOO' VARY OFFLINE
X'1200' RETRY
X'120l' MOVE THE PAGING DATA SETS TO ANOTHER SUBSYSTEM
X'1202' MOVE PACK TO ANOTHER DRIVE AND RERUN THE SAME JOB
X'1203' RESTART JOB
X'1204' ATTEMPT TO REESTABLISH THE CONNECTION
X'1205' RERUN THE APPLICATION PROGRAM
X'1206' WAIT THEN RETRY
X'12CO' RETRY AFTER Csf82 qualifier) (sf82 qualifier)
Note: The two qualifiers indicate a date and time after which the
operation should be retried.
X'1300' CORRECT THEN RETRY: The operator should correct the condition
referred to and retry the operation
X'130l'
X'1310'
X'13ll'
X'1320'
X'1330'
X'1331'
X'1332'
X'13AO'

READY THE DEVICE THEN RETRY
VERIFY THAT AIR VENTS ARE NOT COVERED
CHECK FOR DIRTY FILTER
CHECK CABLE CONNECTION AND RETRY
ACTIVATE PORT THEN RETRY
ENABLE LINE THEN RETRY
REACTIVATE LINE
ACTIVATE ONE OR MORE PORTS IN THE ROTARY GROUP ASSOCIATED
WITH (sf82 qualifier)
Note: The qualifier identifies the telephone number associated
with the rotary group.
X'13Al' ACTIVATE RESOURCES ATTACHED TO (sf82 qualifier)

Chapter 8.

Common Fields

8-87

MS Major Vectors
X'l3A2' DEACTIVATE RESOURCES ATTACHED TO (sf82 qualifier)
X'1400' RESTART: Perform the appropriate restart operation on the
indicated resource
X'l40l' RE-IML MOSS: Reload the MOSS microcode
X'l402' RE-IPL THE COMMUNICATION CONTROLLER: Reload the system
software program in the communication controller
X'l403' RE-IPL THE SECONDARY FINANCE CONTROLLER
X'l404' RE-IML THE CONTROL UNIT
X'l40S' REACTIVATE LAN MANAGEMENT SERVER PROGRAM
X'1406' FOLLOW ALERT SENDERS PROCEDURES FOR RESOURCE ACTIVATION
X'l4l0' RESUME OPERATION ON BACKUP PU: Automatic problem bypass
has been successful, and a backup PU is now available;
operation should be resumed using this PU
X'1500' CORRECT INSTALLATION PROBLEM: It will be necessary to correct the
installation error before continuing operation
X'ISOl'
X'IS02'
X'IS03'
X'IS04'
X'ISOS'
X'IS06'
X'IS07'
X'IS08'
X'IS09'
X'ISOA'
X'ISOB'
X'ISOC'
X'ISOD'
X'ISOE'
X'ISOF'

CORRECT GENERATION PROBLEM
CORRECT CUSTOMIZATION PARAMETERS
CORRECT CONFIGURATION
APPLY CORRECT SOFTWARE LEVEL
LOAD THE REQUIRED OPTIONAL MODULE
INCREASE INTERVENTION TIMER VALUE
CORRECT ADDRESS FROM MODEM KEYPAD
CORRECT ADDRESS FROM DSU/CSU CONTROL PANEL
ENABLE LPDA-2 FROM MODEM KEYPAD
ENABLE LPDA-2 FROM DSU/CSU CONTROL PANEL
CONFIGURE MODEM
CONFIGURE DSU/CSU
CONFIGURE LOCAL MODEM AS PRIMARY OR CONTROL
CONFIGURE LOCAL DSU/CSU AS PRIMARY OR CONTROL
CHECK THRESHOLD LIMIT AND CHANGE IF SET TOO LOW

X'1600' REPLACE MEDIA
X'160l'
X'l602'
X'1603'
X'1604'
X'160S'
X'1606'

FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PLACE BACKUP DISKETTE IN DRIVE
CHANGE DISKETTE AND RETRY
PUT CORRECT PAPER IN CASSETTE
PUT CASSETTE IN PRINTER
ADD PAPER

X'1700' REPLENISH SUPPLIES
X'l701'
X'1702'
X'l703'
X'1704'
X'l70S'
X'l706'

REPLACE RIBBON
ADD INK
ADD TONER
CHANGE ALL AIR FILTERS
ADD FUSER OIL
ADD STAPLES

X'l800' REPLACE DEFECTIVE EQUIPMENT
8-88

SNA Formats

MS Major Vectors

REPLACE KEYBOARD
REPLACE MODULE
REPLACE CARD
REPLACE DEVICE
REPLACE BATTERY
REPLACE PRINTER
REPLACE DISPLAY CONTROL MODULE
REPLACE MSR OR MSRE:
Replace the magnetic stripe reader
or magnetic stripe reader/encoder
X'18l1' REPLACE STORAGE CONTROLLER
X'18l2' REPLACE WORKSTATION CONTROLLER
X'18l3' REPLACE COMMUNICATIONS SUBSYSTEM CONTROLLER
X'18AO' REPLACE THE CARD IDENTIFIED BY (sf82 qualifier)
Note: The qualifier identifies the card to be replaced, e.g., by
its part number.
X'18Al' REPLACE CABLE IDENTIFIED BY (sf82 qualifier)
X'18CO' REPLACE THE BATTERY IDENTIFIED BY (sf82 qualifier) (sf82
qualifier)
Note: The two qualifiers identify the battery to be replaced,
e.g., by giving its type and location.
X'180l'
X'1802'
X'1803'
X'1804'
X'180S'
X'1806'
X'1807'
X'1808'

X'1900' PERFORM PROBLEM BYPASS PROCEDURES:
Refer to the problem bypass
documentation provided for this condition and follow the specified
procedures
X'1901' REPLACE MODEM
X'1902' REPLACE DSU/CSU
X'1903' CHANGE TO BACKUP SPEED
X'1904' ACTIVATE SNBU, IF AVAILABLE
X'190S' DISCONNECT AND RE-DIAL SNBU LINE
X'19Al' PERFORM MANUAL FALLBACK TO (sf82 qualifier)
Note: The qualifier identifies the communication control unit
(CCU) within the communication controller to which the fallback is
to be done.
X'2000' (Review detailed data):
Refer to the detailed data presentation
for additional messages and information
Note: There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'2001' (Report detailed data):
Report the information that was
transported in the Detailed Data subvector
Note: There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
Note:
An Alert receiver has the option of displaying the data
from the Detailed Data (X'82') subvector either in conjunction
with this text or in another display that can be reached from the
display containing this text.
X'2002' (Review most recent traffic statistics):
Report the
information in the statistics subvectors kept for the
link stations

Chapter 8.

Common Fields

8-89

MS Major Vectors
Note:
There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'2010' (Review link detailed data):
Review the information that
was transported in those of the X'Sx' subvectors flowing
in this Alert
Note:
There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'201l' (Review hexadecimal display of the Alert record):
Review
the screens providing a hexadecimal display of the entire
Alert record
Note:
There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'2l00' (review recent Alerts for this resource):
Note:
There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'2l0l' (review recent statistical records for this resource):
Note:
There is no text string defined for this code point; the
Alert receiver indicates the action to be taken in terms of its
own screen design and command structure.
X'2200' REVIEW DATA LOGS:
data logs

Review the specified records in one or more

REVIEW REMOTE DEVICE LOGS
REVIEW DEVICE STATISTICAL LOG AT ALERT SENDER
REVIEW SUPPORTING DATA AT ALERT SENDER
REVIEW SENDING DEVICE LOG (sf82 qualifier) (sf82
qualifier)
Note:
The first qualifier is the log identification and the
second qualifier is the data to be reviewed (i.e.~ System Message
Log).
X'220l'
X'2202'
X'2203'
X'22CO'

X'3000' CONTACT APPROPRIATE SERVICE REPRESENTATIVE: This Alert condition
has been caused by a hardware or software failure.
The operator
is directed to contact the person, organization, or vendor
responsible to provide service for this product.
X'300l' CONTACT CONSUMER SERVICE REPRESENTATIVE:
Contact the
customer representative who is responsible for dealing
with consumer users of the device.
X'3002' CONTACT SECURITY CONTROL REPRESENTATIVE:
Contact the
customer representative who is responsible for dealing
with security concerns for the device.
X'30El' CONTACT SERVICE REPRESENTATIVE FOR (sf83 product text)
X'3100' CONTACT ADMINISTRATIVE PERSONNEL:
Contact personnel with
administrative responsibility for one or more network resources
X'3101' CONTACT TOKEN-RING ADMINISTRATOR RESPONSIBLE FOR THIS LAN

8-90

SNA Formats

MS Major Vectors
X'3102' CONTACT CSMA/CD ADMINISTRATOR RESPONSIBLE FOR THIS LAN
X'3103' CONTACT LAN ADMINISTRATOR RESPONSIBLE FOR THIS LAN
X'3l04' CONTACT NETWORK INFORMATION SERVICE FOR PRIVATE NETWORK
CALLED
X'310S' CONTACT X.2l NETWORK INFORMATION SERVICE
X'3l06' CONTACT ISDN NETWORK INFORMATION SERVICE
X'3107' CONTACT X.2S NETWORK INFORMATION SERVICE
X'3ll0' CONTACT COMMUNICATIONS SYSTEMS PROGRAMMER
X'3120' CONTACT PRINTER OPERATOR
X'3l21' CONTACT TERMINAL CONTROL UNIT OPERATOR
X'3l22' CONTACT CALLED DTE'S OPERATOR
X'3l23' CONTACT REMOTE DTE'S OPERATOR
X'3l24' CONTACT PBM NETWORK OPERATOR: Contact the operator who
has specific responsibility for controlling the personal
banking machine (PBM) network for the reporting device.
X'3200' REPORT THE FOLLOWING
Note: Since replacement code points for reporting one, two, and
three (sf82 qualifiers)'s are all required, the X'32xx' code
points violate the usual rule of defining only one replacement
code point, in the range indicating three qualifiers. Three
separate replacement code points are defined, and should be used
by Alert senders, depending on the number of qualifiers to be
passed.
X'32AO' REPORT THE FOLLOWING (sf82 qualifier)
X'32CO' REPORT THE FOLLOWING (sf82 qualifier) (sf82 qualifier)
X'32DO' REPORT THE FOLLOWING (sf82 qualifier) (sf82 qualifier)
(sf82 qualifier)
X'3300' IF PROBLEM REOCCURS THEN DO THE FOLLOWING: After performing the
previous actions, try the operation again. If you experience
another problem, then perform the following actions
X'330l' IF PROBLEM PERSISTS THEN DO THE FOLLOWING
X'3302' IF PROBLEM CONTINUES TO OCCUR REPEATEDLY THEN DO THE
FOLLOWING
X'3303' IF UNSUCCESSFUL THEN DO THE FOLLOWING
X'3400' WAIT FOR ADDITIONAL MESSAGE BEFORE TAKING ACTION: An additional
message will be forthcoming, indicating the action to be taken
X'3S00' REFER TO PRODUCT DOCUMENTATION FOR ADDITIONAL INFORMATION
X'3SEO' REFER TO (sf83 product text) PRODUCT DOCUMENTATION FOR
ADDITIONAL INFORMATION
X'EOOO'-X'EFFF' Reserved
Note: This range of code points is reserved for use by
non-IBM products and customer written applications. No
IBM product will send a code point from within this range.

Chapter 8.

Common Fields

8-91

MS Major Vectors
Note: The following code points specify extended messages. An Alert
receiver that displays only default text provides no display for these
code points.
X'FOOO' (no display): Additional message data
X'FOOI' MULTIPLE FAILURES INDICATE CHANNEL FAILURE
X'F002' MULTIPLE FAILURES INDICATE CONTROLLER FAILURE
X'F003' MULTIPLE DRIVE FAILURES ON SAME CONTROLLER INDICATE
CONTROLLER FAILURE
X'F004' MULTIPLE FAILURES INDICATE CONTROL UNIT FAILURE
X'FOOS' MULTIPLE FAILURES INDICATE TERMINAL MULTIPLEXER FAILURE
X'F006' REOCCURRENCE OF SAME ERROR INDICATES MEDIA FAILURE
X'F007' REOCCURRENCE OF PROBLEM INDICATES DEVICE OR ATTACHMENT
ERROR
X'F008' REOCCURRENCE INDICATES MEDIA PROBLEM
X'F009' NON REOCCURRENCE OF FAILURE INDICATES ORIGINAL DRIVE
FAILURE
X'FOOA' MULTIPLE FAILURES INDICATE LINE ADAPTER MULTIPLEXER
FAILURE
X'FOII' NO FURTHER ACTION REQUIRED UNLESS PROBLEM PERSISTS
X'F012' THIS ALERT IDENTIFIES THE CAUSE OF A PREVIOUS ERROR WHICH
HAS BEEN RECOVERED
X'F013' SERVICE CAN BE SCHEDULED AT A LATER TIME UNLESS REPEATED
FAILURES PREVENT NORMAL OPERATION
X'F014' RESUME OPERATION
X'FOSO' IPL CAPABILITIES LIMITED
X'F051' NO IPL CAPABILITIES
X'F052' NORMAL OPERATIONS CAN CONTINUE BUT IF AUXILIARY STORAGE IS
EXHAUSTED ONSITE ACTION WILL BE NECESSARY
X'F060' TO RECOVER LOST RESOURCE
X'FOAO' FOR (sf82 qualifier)
X'FODO' FAILING COMPONENT LOCATION (sf82 qualifier) (sf82
qualifier) (sf82 qualifier)
Note: The qualifiers identify the failing component location in
one of two ways:
Method 1:
Ql
Q2
Q3

= RACK

= UNIT

= CARD

(within a rack)
SLOT (within a unit)

Method 2:
QI = RACK/UNIT (with no delimiter between the rack and unit
numbers)
Q2 = CARD SLOT (within a unit)
Q3 = CABLE POSITION (on a card)
Method 2 is used only in those cases where cable position on a
card is meaningful.
X'FOEI' PREPARE FOR AUTOMATIC SHUTDOWN OF (sf83 product text)
X'FFFF' Reserved

8-92

SNA Formats

MS Major Vectors

Detailed Data (X'82') Network Alert Common Subfield
This subfield contains product specific detailed
be displayed at an Alert receiver.

o
I

2

data to

length (q+l), in binary, of the Detailed Data subfield
Note:
length = X'02' indicates that the Product ID Code, Data ID, Data
Encoding, and Detailed Data fields are not present.
Key:
X'82'
Product ID code: a code indicating what product identification, if any,
must be displayed in conjunction with the data type and data.
The
structure of this field is identical to that present in the Product Set ID
Index (X'83') subfield.
A value of X'OO' in this byte indicates that no product identification
data is displayed in conjunction with the data type and detailed data.
bits 0-3, Product ID subvector code: a code point that specifies (1) the
type of Product ID subvector being indexed (hardware or
software), and (2) the particular data to be extracted from this
subvector
Note:
See "Product Identifier (X'll') MS Common Subvector" on
page 8-110 for the criteria distinguishing hardware and software
Product ID subvectors.
X'O'-X'I' reserved
X'2' (machine type or hardware product common name) from a
hardware Product ID Subvector
Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'5' (machine type or hardware product common name) plus model
number from a hardware Product ID Subvector
Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'9' software product common name from a software Product ID
subvector
bit 4, product set ID indicator: an indication of which Product Set ID
(PSID) contains the Product ID subvector being indexed
o Alert sender PSID
1 Indicated resource PSID
bits 5-7, count: a three-digit binary number that indicates which Product
ID subvector, of the type specified by the Product ID subvector
code, is being indexed within the PSID specified by the Product
Set ID Indicator.
Note:
This count applies only to Product ID subvectors of the
type specified by the Product ID subvector code.
If, for
example, the code is X'2' (specifying a hardware Product ID)
then only hardware X'll's are counted: a count of X'3' would
thus index the third hardware Product ID within the PSID
indicated by the Product Set ID Indicator.

3

Data ID: a code point indicating the type of data carried in the
subfield. The English text associated with each code point, or its
national language equivalent, is displayed in conjunction with the
detailed data.
Defined codes are:

Chapter 8.

Common Fields

8-93

MS Major Vectors
X'OO'
X'Ol'
X'02'
X'03'
X'04'
X' 07 •
X'09'
X'OA'
X'OB'
X'OC'
X'OD'
X'OE'
X'OF'
X'lO'
X'll'
X'12'
X'13'
X'14'
X'lS'
X'16'
X'17'
X'18'
X'lA'

X'lB'

X'lC'

X'lD'
X'20'
X'21'
X'22'
X'23'
X'24'
X'30'
X'31'
X'32'
X'33'
X'34'
X'3S'
X'36'
X'37'

8-94

(no display)
ABEND CODE
ADAPTER CHECK STATUS
ADAPTER RETURN CODE
BOP CODE
ERROR CODE
EVENT CODE
LLC ERROR CODE
MACHINE CHECK CODE
MALFUNCTION CODE
PROGRAM CHECK CODE
REASON CODE
RETURN CODE
SENSE CODE
SENSE DATA
SOFTWARE ERROR CODE
STATUS CODE
SYMPTOM CODE
SNA SENSE DATA
BUS STATUS CODE
RING STATUS CODE
CALL PROGRESS SIGNAL: A notification from an X.21 network to a DTE,
indicating why a connection could not be established
X.2S CLEAR PACKET, CAUSE CODE: A code to or from an X.2S network
indicating the reason that a CLEAR request or indication packet was
sent
Note: This indicates the reason that a network connection was lost
or could not be established.
X.2S RESET PACKET, CAUSE CODE: A code to or from an X.2S network
indicating the reason that a RESET request or indication packet was
sent
Note: This indicates the reason that a network connection was lost
or could not be established.
X.2S RESTART PACKET, CAUSE CODE: A code to or from an X.2S network
indicating the reason that a RESTART request or indication packet
was sent
Note: This indicates the reason that a network connection was lost
or could not be established.
X.2S DIAGNOSTIC CODE: A code to or from an X.25 network providing
additional information about why a Diagnostic packet or a Clear,
Reset, or Restart request or indication packet was sent
MESSAGE CODE
PANEL ERROR MESSAGE CODE
SYSTEM MESSAGE CODE
MESSAGE SEVERITY
WAIT STATE CODE
REFERENCE CODE
SYSTEM REFERENCE CODE
REPLACEABLE UNIT CODE
COMPONENT ID
COMMUNICATION CONTROL UNIT
TYPE
LOCATION
PART NUMBER

SNA Formats

MS Major Vectors
X'3A'
X'3B'
X'3C'
X'3D'
X'3E'
X'40'
X'4l'
X'SO'
X'Sl'
X'S2'
X'S3'
X'S4'
X'SS'
X'60'
X'6l'
X'62'
X'63'
X'64'
X'6S'
X'66'
X'70'
X'80'
X'8l'
X'82'
X'83'
X'84'
X'8S'
X'86'

X'90'
X'9l'
X'92'
X'AO'
X'Al'
X'A2'
X'A3'
X'A4'
X'AS'
X'A6'
X'BO'
X'Bl'
X'B8'
X'B9'
X'BA'
X'DO'
X'Dl'
X'D2'
X'D3'
X'D4'
X'DS'

RACK/UNIT
RACK
UNIT
CARD SLOT
CABLE POSITION
ERROR RECOVERY PROCEDURE
PDP CODE
CHANNEL UNIT ADDRESS
DEVICE ADDRESS
LINE ADDRESS
LINE ADDRESS RANGE
ADAPTER AT ADDRESS
LINE
PORT NUMBER
ADAPTER NUMBER
CHANNEL ADAPTER NUMBER
LINE ADAPTER NUMBER
LINE INTERFACE COUPLER (LIC) POSITION
BUS NUMBER
TOKEN RING INTERFACE COUPLER NUMBER
GENERATION PARAMETER
NODE
LINK STATION
CP
PU
LU
TRANSACTION PROGRAM
LSL: Link Segment Level of a multi-segment link connection
Note: In a multi-segment link connection, link segments are
numbered in ascending order, from the error notification sender
outwards; thus the link segment immediately adjacent to the error
notification sender is Link Segment Levell, the one adjacent to it
is Link Segment Level 2, etc.
YEAR/MONTH/DAY
TIME
JULIAN DATE
BYTE OFFSET
BIT OFFSET
DETECTING MODULE
FAILING MODULE
MAINTENANCE LEVEL
COMMAND
PROGRAM
EIA STANDARD
CCITT STANDARD
LINE SPEED (BITS PER SECOND)
LINE SPEED (KILOBITS PER SECOND)
LINE SPEED (MEGABITS PER SECOND)
FILE NAME
LOG RECORD NUMBER
CARTRIDGE: A component that holds items to be dispensed
AIR FILTER NUMBER
TELEPHONE NUMBER
CALLING TELEPHONE NUMBER
Chapter 8.

Common Fields

8-9S

MS Major Vectors
X'D6' TELEPHONE NUMBER CALLED
X'D7' REPORTING TELEPHONE NUMBER: The telephone number of the Alert
sender
X'D8' TIMER
X'D9' LOG RECORD TYPE
X'DA' LOG ID
X'DB' PUBLICATION NUMBER
X'EO'-X'EF' reserved
Note:
This range of code points is reserved for use by
non-IBM products and customer written applications.
No IBM
product will send a code point from within this range.
X'FO' PRODUCT ALERT REFERENCE CODE: A code that identifies an Alert in a
user-friendly way. The product Alert reference code is used to
index documentation provided by the Alert sending product. This
documentation can group the Alerts into natural categories and
provide extended explanations or diagnostic information.

4

5-q

Data Encoding: a code point indicating how the accompanying detailed data
is encoded, and, thus, how it is to be displayed.
Defined code are:
X'OO' hexadecimal: The data is to be displayed as hexadecimal digits.
X'Ol' binary: The data is the binary representation of an unsigned
integer value (8, 16, 24, or 32 bits in length). The decimal
equivalent is to be displayed.
For example, the value B'11111111'
(X'FF') is to be displayed as 255.
X'll' Coded Graphic Character Set 00640-00500 plus: The data is to be
decoded using Coded Graphic Character Set 00640-00500,
documented
in "Appendix A. SNA Character Sets and Symbol-String Types" , plus
three additional code points:
X'5B' = "$" (dollar sign); X'7B' =
"I" (pound or number sign); X'7C' = "@" (at sign).
Note:
Detailed data encoded in this way is limited to codes, numbers, or
internationally recognized terms that do not require translation.
Detailed data, encoded as specified in byte 4
Note:
Maximum length of the detailed data is 44 bytes.

Product Set ID Index (X'83') Network Alert Common Subfield
This subfie1d contains a code point and a count that
jointly specify a particular Product ID (X'11') subvector
within a particular Product Set ID (X'10') subvector in
the Alert major vector.

o
1

2(=q)

8-96

Length (q+1), in binary, of the Product Set ID Index subfie1d
Key:
X'83'
Product ID code
bits 0-3, product 10 subvector code:
A code point that specifies (1) the
type of Product ID subvector being indexed (hardware or
software), and (2) the particular data to be extracted from this
subvector
Note: See "Product Identifier (X'll') MS Common Subvector" on
page 8-110 for the criteria distinguishing hardware and software
Product ID subvectors.
X'O'-X'l' reserved
X'2' (machine type or hardware product common name) from a
hardware Product 10 subvector

SNA Formats

MS

M~jor

Vectors

Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'3' serial number or repair 10 number, whichever is present,
from a hardware Product 10 subvector
X'4' (machine type or hardware product common name) plus serial
number or repair ID number, whichever is present, from a
hardware Product ID subvector
Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'5' (machine type or hardware product common name) plus model
number from a hardware Product 10 subvector
Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'6' (machine type or hardware product common name) plus model
number plus serial number or repair ID number, whichever is
present, from a hardware Product 10 subvector
Note:
The hardware product common name is used if it is
present; otherwise, the machine type is used.
X'9' software product common name from a software Product ID
subvector
bit 4, product set ID indicator: An indication of which Product Set ID
contains the Product 10 subvector being indexed
o Alert sender PSID
I indicated resource PSID
bits 5-7, count: a three-digit binary number that indicates which Product
ID subvector, of the type specified by the Product ID Subvector
Code, is being indexed within the PSID specified by the Product
Set ID Indicator.
Note: This count applies only to Product 10 subvectors of the
type specified by the Product 10 Subvector Code.
If, for
example, the code is X'2' (specifying a hardware Product 10)
then only hardware X'll's are counted: a count of X'3' would
thus index the third hardware Product 10 within the PSIO
indicated by the Product Set 10 Indicator.

Request Response Time Monitor (X'SOSO') MS Majo,r Vector
SSCP-->PU T2
This
major vector enables or disables response time
monitoring, transports RTM parameters, and transports a
request for RTM data and status from a device.
0-1
2-3
4-n

length (n+l), in binary, of this MS major vector
Key: X'8080'
MS subvectors, as described (using zero-origin indexing) in "MS Common
Subvectors" on page 8-104 for subvector keys X'OO' - X'7F', and in
"Request Response Time Monitor Subvectors" on page 8-98 for subvector
keys X'80' - X'FE'
Note:

The following subvector keys may be used as indicated:

Chapter 8.

Common Fields

8-97

MS Major Vectors
I

Presence in NMVTI
Request RTM
I

(X'8080')
Subvector

Major Vector

SNA Address List (X'04')

CP

*RTM Request (X'92')
RTM Control (X'94')

*
P
CP

I
I
I

Note 1

P
CP

I
I
I

Note

I
2 I

Command Subvector (for PU parsing)
Present one time
Conditionally present one time (See Notes for
conditions.)

Notes:

1.

This subvector is present in the NMVT containing an X'8080' major
vector when the request is for a specific LU (i.e., identified in the
X'04' subvector) associated with the PU processing the request. This
subvector is not present when the request is to apply to all LUs
associated with the PU processing the request.

2.

This subvector is present when RTM parameters are being set.
If
present, it immediately follows the RTM Request (X'92' subvector).

Request Response Time Monitor Subvectors
RTM Request (X'92') Request RTM MS Subvector
This subvector requests RTM data and status or accompanies
an RTM control subvector.

o
1
2

8-98

Length (p+l), in binary, of this subvector
Key:
X'92'
Request indicators (bit is set to 1 to request that the function be
performed):
bit 0, Reset RTM data for the target LU upon reply transmission or
immediately if no reply is requested.
bit 1, Retrieve data and status for all LUs with accumulated RTM data.
See Figure 8-1.
bit 2, retired
bit 3, Retrieve data and status for the LU specified in the SNA Address
List (X'04') MS common subvector also included in this major
vector.
See Figure 8-1.
bit 4, Apply the RTM Control (X'94') MS subvector also included in this
major vector to all LUs.

SNA Formats

MS Major Vectors

3(=p)

Note:
If this bit is set to I, the RTM Control (X'94') MS
subvector will be present.
If this bit is set to 0 and the RTM
Control (X'94') subvector is present, the SNA Address List (X'04')
MS common subvector will be present.
bits 5-6, retired
Reserved

Request Type

Subvectors present
in the Request RTM
(X'8080') major vector

Retrieve data for all LUs with
accumulated data

92

Bits
Bl

B3

1

0

Retrieve for specified LU

92, 04

0

1

Set parameters for all LUs

92, 94

0

0

Set parameters for specified LU

92, 94, 04

0

0

Figure 8-1.

Setting of
Subvector

Bits

1

and

3

of

Byte

2

of

the

RTM Request (X'92')

RTM Control (X'94') Request RTM MS Subvector
This subvector controls RTM data accumulation.

o
1
2-3

4-5

6

Length (p+l), in binary, of this sUbvector
Key:
X'94'
RTM status and control change mask (bit is set to 1 if the setting
specified by the corresponding RTM status and control indicator in bytes
4-5 should be used):
bits 0-8, mask bits corresponding respectively to indicator bits 0-8 in
bytes 4-5
bits 9-15, reserved
RTM status and control indicators (bit is set to 1 to activate the
function or 0 to deactivate it):
bit 0, RTM measurement active
bit I, return data unsolicited on session deactivation
2, return data unsolicited on counter overflow
3, retired
4, set the RTM
bit 5, set the RTM response time measurement boundaries using bytes 9 and
16-m
bi t
6, retired
bit 7, local display of RTM data
bi t
8, reti red
bits 9-15, reserved
Reserved

Chapter 8.

Common Fields

8-99

MS Major Vectors

7
8

9

10-15
16

17-p

17-18
19-20
21-p

Retired
RTM measurement definition--defines when the response-time measurement
will begin and end for each exchange between session partners:
X'Ol' measured from the Attention or Action key depression to the arrival
back at the lU of the first character that can alter the
presentation space
X'02' measured from the Attention or Action key depression until the lU is
ready to accept input from its end user
X'03' measured from the Attention or Action key depression to the receipt
and processing back at the lU of Change Direction (CD) or End
Bracket (EB)
X'04' measured from the Attention or Action key depression to the receipt
of the last character of the last message received prior to the next
Attention or Action key depression
Response-time unit of measure:
X'OO' 100 milliseconds
X'01'-X'7F' retired
X'90' retired
X'AO' retired
X'CO' retired
X'DO' retired
Reserved
RTM data collection parameters:
bits 0-3, reserved
bits 4-7, binary number of 2-byte boundaries in bytes l7-p
A set of response-time measurement boundaries, specified in binary (as
units of response-time units of measure described by byte 9) and
increasing in order of magnitude;
thus, response-time data is collected
for intervals (0 < rl <= bl*u), (bl*u < r2 <= b2*u),
up to (b4 <
r5), where bi is the value of the boundary i, ri is the response-time
being measured for interval i, and u is the unit of measure described by
byte 9.
Boundary 1
Boundary 2
Additional boundaries as required (the total number is defined by byte 16,
bits 4-7), up to a maximum of 4

Response Time Monitor (X'0080') MS Major Vector
PU T2-->SSCP
This major vector transports RTM data.
This data includes
the collected response time data and current RTM status.
0-1
2-3
4-n

length (n+l), in binary, of this MS major vector
Key:
X'0080'
MS subvectors, as described (using zero-origin indexing) in "MS Common
Subvectors" on page 8-104 for subvector keys X'OO' - X'7F', and in
"Response Time Monitor Subvectors" on page 8-102 for subvector keys X'80'
- X'FE'
Note:

8-100

The following subvector keys may be used as indicated:

SNA Formats

MS Major Vectors

Subvector

Presence in NMVT
RTM (X'0080')
Major Vector

Date/Time (X'OI)

CP

Note 1

SNA Address List (X'04')

CP

Note 2

Relative Time (X'42')

CP

Note 3

Data Reset Flag (X'45')

CP

Note 4

Sense Data (X'7D' )

CP

Note 5

RTM Status Reply (X'9l')

CP

Note 6

RTM Data (X'93')

CP

Note 7

P
CP

Present one time
Conditionally present one time
conditions.)

(See Notes for

Notes:
1.

If the PU sending the X'0080' major vector has the capability of
providing it, it places this subvector in the NMVT.

2.

This subvector is present when positively replying to a request for
RTM data and status if RTM data has been accumulated.

3.

If the PU sending the X'0080' cannot provide a Date/Time subvector, it
places this subvector in the NMVT instead.

4.

This subvector is present in an X'0080' major vector when a set of
counters has been reset, either as a result of a request or when sent
unsolicited.

5.

This subvector 1S present when a Request RTM major vector cannot be
processed, or when requested data cannot be gathered and the PU
sending this major vector has elected to send sense data in a reply
instead of a negative response.

6.

This subvector is present when replying to a request for RTM data and
status when data is present or when the reply is for the last LU (sent
as a result of a request to retrive data for all LUs with accumulated
data) and no data is present.

Chapter 8.

Common Fields

8-101

MS Major Vectors
7.

This subvector is present when positively replying to a request for
RTM data and status if RTM data has been accumulated.

Response Time Monitor Subvectors
RTM status Reply (X'91') RTM MS Subvector
This subvector transports
function for a device.

°
1

2

3

4

5-6

8-102

the

current

status

of

RTM

length (p+l), in binary, of this subvector
Key:
X'91'
Reply indicators (bit is set to 1 to indicate that the assertion is true):
bit 0, reserved
bit 1, data not included
bit 2, an RTM data request has been issued for an lU that has its RTM
function disabled
bit 3, this is the first RTM reply since session activation (used to
initiate a recording of the session partner names and the
correlation value in bytes 7-8 of this subvector while there is
reasonable assurance that the session is active); on subsequent
replies the correlation value will be used to associate data from
the same lU-lU session
bit 4, an lU-lU session activation or deactivation has occurred at least
once while the included RTM data was being accumulated
bits 5-7, reserved
Reason for unsolicited reply, if any (bit 1S set to 1 to indicate the
appropriate reason):
bit 0, the session for this resource has ended and 1S enabled
unsolicited-reply-on-session-deactivation
bit 1, a counter for this lU has overflowed and
unsolicited-reply-on-counter-overflow is enabled
bit 2, retired
bits 3-5, reserved
bit 6, retired
bit 7, reserved
Reason for potential loss of RTM data, if any (bit is set to 1 to indicate
the reason):
bit 0, reserved
bit 1, an overflow has occurred on at least one counter and updating for
all of this lU's counters has been stopped to retain the relative
significance of the data
bit 2, this lU has been reset since the last reply was sent
bit 3, a new session was activated before data for the previous session
could be transmitted:
loss of data for the new session may have
occurred; updating for all of this lU's counters has been stopped
to retain the relative significance of the data
bit 4, the RTM definition or response time measurement boundaries have
been changed by a request that did not solicit the RTM data and
RTM accumulation was active for this lU:
any data collected since
the last data request has been lost
bits 5-7, reserved
RTM status when this subvector was constructed (a bit set to 1 indicates
that the function was active):

SNA Formats

MS Major Vectors

7-8(=p)

bit 0, RTM measurement active
bit 1, data to be sent unsolicited on session deactivation
bit 2, data to be sent unsolicited on counter overflow
bit 3, retired
bit 4, RTM definition was set by the control point
bit 5, RTM boundaries were set by the control point
bit 6, retired
bit 7, local display of RTM data
bit 8, retired
bits 9-15, reserved
Correlation value: a unique 2-byte value, generated by the PU, that is
retained and used in all RTM replies dealing with the same LU-LU session
from session activation through the subsequent session deactivation

RTM Data (X'93') RTM MS Subvector
This subvector transports
data.

o
1

2

3

4-5
6-7
8

9-p

solicited

or unsolicited

RTM

Length (q+9), in binary, of this subvector
Key:
X'93'
RTM measurement definition in effect:
X'Ol' measured from the Attention or Action key depression to the arrival
back at the LU of the first character that can alter the
presentation space
X'02' measured from the Attention or Action key depression until the LU is
ready to accept input from its end user
X'03' measured from the Attention or Action key depression to the receipt
and processing back at the LU of Change Direction (CD) or End
Bracket (EB)
X'04' measured from the Attention or Action key depression to the receipt
of the last character of the last message received prior to the next
Attention or Action key depression.
Response time unit of measure:
X'OO' 100 milliseconds
X'Ol'-X'7F' retired
X'90' retired
X'AO' retired
X'CO' retired
X'DO' retired
Reserved
Retired
RTM data collection parameters:
bits 0-3, the number, in binary, of response time measurement boundaries
returned; all boundaries that were set previously will be
returned in this subvector
bits 4-7, the number, in binary, of boundary sets for which valid data was
collected (overflow data--a count of response times exceeding
the maximum boundary--is not included in this number but is
always present)
A set of response-time measurement boundaries as previously set at the LU
or by the RTM Control (X'94') MS subvector (specified in binary as units
of response-time units of measure described by byte 9) and increasing in
order of magnitude;
thus, response-time data is collected for intervals

Chapter 8.

Common Fields

8-103

MS Major Vectors

9-10
11-12
13-p
p+l-q

p+l-p+2
p+3-p+4
p+5-q
q+l-q+2
q+3-q+6

q+7-q+8

8-104

(0 < rl <= bl*u), (bl*u < r2 <= b2*u),
up to (b4 < r5), where bi is
the value of the boundary i, ri is the response-time being measured for
interval i, and u is the unit of measure described by byte 9
Boundary 1
Boundary 2
Additional boundaries as required to equal the number of boundaries set
previously and specified by byte 8, bits 0-3
The number of measured exchanges for each response-time interval:
the
number of exchanges whose duration was within an interval's boundaries is
reported in binary separately for each interval
Number of exchanges in the (O,bl) range
Number of exchanges in the (bl+l , b2) range
Additional excha"nge counts to satisfy the number of boundaries defined 1
up to a maximum of 4
Overflow:
the number of exchange durations greater than the maximum
boundary specified
Total of all individual times for all exchanges measured and reported by
this record , including overflowl in the measurement units defined by byte
3
Last measured exchange duration in the measurement units defined by byte 3

SNA Formats

MS Common Subvectors

MS Common Subvectors
The common MS subvectors are defined as follows (using zero-origin indexing):

Text Message (X'OO') MS Common Subvector
This MS common subvector transports EBCDIC data.

o
I
2-p

length (p+l)~ in binary~ of the Text Message subvector
Key:
X'OO'
Text message in EBCDIC
Note:
The coded character set that may be transported in this field is
dependent on the implementation that provided the text or allowed an
operator to input the text~ as well as the output device used by the Alert
processor.
The installation management ensures the compatibility of these
products.

Date/Time (X'Ol') MS Common Subvector
This MS
common subvector is
used by the
time-stamping the NMVT in which it is carried.

o
I

2-p

PU

for

length (p+l)~ in binary~ of the Date/Time subvector
Key:
X'OI'
One or more of the following subfields:
X'IO' local Date/Time (required subfield)
X'20' Greenwich Mean Time Offset

Local Date/Time (X'lO') Date/Time Subfield
This subfield transports the local
creation of the major vector.

o
1
2-4

2
3
4
5-q
5
6
7

8-q

date and time

of the

Length (q+l)~ in binary~ of the local Date/Time subfield
Key:
X'IO'
local date
Year~ in binary~ consisting of the last two digits of the year
Month~ in binary (X'OI'-X'OC')
Day~ in binary (X'OI'-X'IF')
local time
Hours~ in binary (X'00'-X'17')
Minutes, in binary (X'00'-X'3B')
Seconds, in binary (X'00'-X'3B')
Optional extension of time: a binary value to provide finer granularity
than seconds

Chapter 8.

Common Fields

8-105

MS Common Subvectors

Greenwich Mean Time Offset (X'20') Date/Time Subfield
This subfield transports the Greenwich Mean Time (GMT)
offset of the node that originated the management services
RU (i.e., the origin node).
It is optionally included in
a major vector by the origin node or by the control point
in whose domain the origin node resides.

o
1
2-3(=q)

Length (q+l), in binary, of the Greenwich Mean Time Offset subfield
Key:
X'20'
Time zone adjustment to Greenwich Mean Time: an interval of time to be
added to, or subtracted from, the local time given in the Local Date/Time
(X'lO') subfield to adjust that time to Greenwich Mean Time
bit 0, positive or negative adjustment indicator:
o adjustment to be added to the local time (i.e., all time zones
westward, between the Greenwich time zone and the International
Date Line)
1 adjustment to be subtracted from the local time (i.e., all time
zones eastward, between the Greenwich time zone and the
International Date Line)
bits 1-3, reserved
bits 4-7, number of hours of adjustment, in binary (X'O'-X'C')
bits 8-15, number of minutes of adjustment, in binary (X'OO'-X'3B')

Hierarchy Name List (X'03') MS Common Subvector
This MS common subvector identifies target resources,
other than the reporting PU,
that are within the same
domain as the origin PU, but cannot be represented in the
SNA Address List subvector.

o
1
2
3
4-p

Length (p+l), in binary, of the Hierarchy Name List subvector
Key: X'03'
Reserved
Number, in binary, of name entries in the hierarchy name list.
Hierarchy Name List Entries (1 to 5 entries may be present)

Note:
Each entry contains a Name field and a Resource Type field, and has the
following form (shown zero-origin):

o
l-q

q+l-q+4

8-106

Length (q+l), in binary, of the following name plus this Length field
Name of resource in upper-case alphanumeric EBCDIC characters
Note:
Resource name never exceeds eight characters.
Resource type identifier:
category in which the resource (named in bytes
l-q) belongs:
X'CIC4CID7' adapter
X'C2D9C4C7' LAN bridge
X'C3C2E740' computerized branch exchange
X'C3C2E4E2' carrier-sense multiple-access with collision detection
(CSMA/CD) bus
X'C3C8CIDS' channel
X'D3C9DSCS' communication link
X'C3E3D9D3' controller

SNA Formats

MS Common Subvectors
X'C4C9E2D2'
X'C4E2D2E3'
X'D2E8C2C4'
X'D3CIDS40'
X'D3C3D6DS'

X'D3D6D6D7'
X'D7C2D440'
X'D7D6E240'
X'D7C2E740'
X'D7D3E3D9'
X'D7D9E3D9'
X'D9C9DSC7'
X'E2D74040'
X'E3FID9D4'
X'E3CID7CS'
X'E3CIE440'
X'E3C2E4E2'
X'E3C5D9D4'
X'C4C5E540'

disk
diskette
keyboard
local area network (LAN)
link connection
Note: This resource type is used for logical link connections
not known to SNA, such as a LAN manager's connection with a
management server.
loop
personal banking machine
point-of-sale unit
private branch exchange
plotter
printer
token-ring
service point
Tl resource manager
tape
teller assist unit
token bus
terminal
unspecified device

SNA Address List (X'04') MS Common Subvector
This MS common subvector is used 1n both request and data
NMVTs.
In a request NMVT, it identifies one or more
destinations of the MS request when the destination is not
the PU addressed in the transmission header (TH).
In a
data NMVT, it identifies the resource associated with the
data when the resource is not the PU addressed in the TH.
If present, this subvector is the first
the MS major vector.

o
1

2

3

4-p

subvector within

ength (p+l), in binary, of the SNA Address List subvector
Key:
X'04'
Address Count:
For address entity format types X'OO', X'40', X'80', and
X'CO', a binary number indicating the number of individual addresses
present in the X'04' subvector. This field is set to X'OO' for all other
address entity format types.
Note: This field provides a count of individual addresses; thus for
format X'40', each pair of addresses counts as two.
Address entity format type:
X'OO' address format is one or more single local addresses
X'40' address format is one or more pairs of session-partner local
addresses, each pair identifying a session
X'80' address format is one or more single network addresses
X'AO' address format is one or more network-qualified address pairs, each
pair identifying a session
X'CO' address format is one or more pairs of session partner network
addresses, each pair identifying a session
Address entities: one or more address entities, each having one of the
formats defined below (zero-origin):

Chapter 8.

Common Fields

8-107

MS Common Subvectors

0-4
5

• For a single local address (byte 3
Reserved
local address

•
0-4
5
6
7-11
12

0-5

For a pair of session-partner local addresses '(byte 3 = X'40'):
Reserved
local address of SlU
Retired
Reserved
Session index (local address of PlU)

• For a single network address (byte 3
Network address

= X'80'):

•

For a network-qualified address pair (byte 3 = X'AO'):
Network address of NAU1
Network address of NAU2
Network ID of the subnetwork in which the above addresses are valid

•

For a pair of session-partner network addresses (byte 3
Network address 1
X'80'
Network address 2

0-5
6-11
12-19

0-5
6
7-12

= X'OO'):

= X'CO'):

Hierarchy/Resource List (X'OS') MS Common Subvector
This
MS
common
subvector
identifies
hierarchically below the sending PU,
that
represented in the SNA Address list subvector.

o
1
2-p

resources,
cannot be

Length (p+1), in binary, of the Hierarchy/Resource list subvector
Key:
X' 05'
The following subfield containing a hierarchical list of resources (listed
by key value below and described in detail following):
X'10' Hierarchy Name List

Hierarchy Name List (X'10') Hierarchy/Resource List Subfield
This subfield contains a list specifying the names of
resources in a
hierarchy.
The last name in the list
specifies the resource to which the data present in the
major vector pertains.

o
1
2

3-q

Length (q+1), in binary, of the Hierarchy Name List subfield
Key:
X 'I 0'
Always set to X'80'
Hierarchy Name list Entries (entries left to right indicate resources down
the hierarchy)

Note:
Each entry contains a length field, a Name field, a Flags byte and a Resource
Type field, and has the following form (shown zero-origin):

8-108

SNA Formats

MS Common Subvectors

o
l-r

r+l

r+2

Length (r+l), in binary, of the following name plus this length field
Name of resource in upper-case alphanumeric EBCDIC characters
Note:
Resource name never exceeds eight characters.
Flags
bit 0, reserved
bit 1, display resource name indicator:
o This name should be displayed if the receiver elects to display
a single resource name and type as part of its presentatio~ of
the MSU containing this subvector.
1 This name should not be displayed if the receiver elects to
display a single resource name and type as part of its
presentation of the MSU containing this subvector.
bits 2-7, reserved
category to which the resource (named 1n bytes
Resource type identifier:
l-r) belongs:
X'OO' unspecified device
X'll' disk
X'13' printer
X'16' tape
X'17' terminal
X'18' transaction program name
X'20' storage device
X' 21' adapter
X'2S' diskette
X'27' loop
X'29' keyboard
X'2B' plotter
X'2C' transmission group
X'2D' line group
X'2E' token-ring
X'2F' computerized branch exchange
X'30' Tl resource manager
X'31' private branch exchange
X'32' carrier-sense multiple-access with collision detection (CSMA/CD) bus
X'33' token bus
X'34' printer server
X'3S' personal banking machine
X'36' teller assist unit
X'37' point-of-sale unit
X'38' local controller
X'39' local area network (LAN)
X'3A' LAN bridge
X'3B' logical link connection
Note:
See also Resource Type Identifier X'F9' (link).
Identifier
X'3B' is used for logical link connections not known to SNA, such as
a LAN manager's connection with a management server.
Identifier
X'F9' is used for logical link connections that are known to SNA.
X'3C' management server
X'3F' port
X'80' controller
X'81' service point
X'82' communication controller
X'83' central processing unit

Chapter 8.

Common Fields

8-109

MS Common Subvectors
X'FO'
X'FI'
X'F3'
X'F4'
X'FS'
X' F7 '
X'F8'
X'F9'

boundary function physical unit
physical unit
logical uni t
control point
network ID
link station
SNA channel
link

Product set ID (X'10') MS Common Subvector
This MS common subvector identifies one or
that implement a network component.

o
I

2
3-p

more products

Length (p+I), in binary, of the Product Set ID subvector
Key: X'IO'
Retired
Network product identifier consisting of one or more Product ID (X'II') MS
common subvectors, as described below (using zero-origin indexing).
Each
Product ID (X'II') MS Common Subvector uniquely identifies a product.
Products fall into two categories:
hardware (with or without microcode)
and software.

Product IdentiTier (X'11') MS Common Subvector
This MS common subvector uniquely identifies a single
product. A product may consist of electronic circuitry
(hardware), executable instructions (software), or both
(in the case of hardware containing microcode).

o
I

2

3-q

8-110

Length (q+I), in binary, of the Product Identifier subvector
Key:
X'II'
bits 0-3, reserved
bits 4-7, product classification:
XiIi IBM hardware
X'3' IBM or non-IBM hardware (not distinguished)
X'4' IBM software
X'9' non-IBM hardware
X'C' non-IBM software
X'E' IBM or non-IBM software (not distinguished)
One or more subfields containing product- and installation-specific
information on hardware, microcode, and software.
Note:
The subfields may be used as indicated in the table on the
following page.

SNA Formats

MS Common Subvectors

Subfield
X'OO'
X'Ol'
X'OB'
X' OE'
X'02'
X'04'
X' 06'
X' 07'
X'08'
X'09'

HW or SW X'OOOO' Alert
XID3
FMH 7
(Note 2)
X'II '
(Note 1) Sender IResource (Note 3) (LU6.2)
I
P
P
HW
P
P
I
I
HW
CP
CP
CP
Note 4
I CP
I
HW
0
0
0
0
I
I
HW
0
0
0
0
I
I
SW
CP
CP
CP
INote 5
I CP
I
I
SW
CP
CP
CP
INote 6
I CP
I
I
P
SW
P
0
P
I
I
I
I
SW
CP
0
INote 7
I CP
I
I
SW
CP
CP
CP
INote 6
I CP
I
I
SW
CP
0
INote 7
I CP

Conditions of Subfield Presence 1n Product Identifier Subvector

P
CP

o

Not present
Present one time
Conditionally present one time
Optionally present one time

Subfield Names:
X'OO'
X'Ol'
X'02'
X'04'
X'06'
X'07'
X'08'
X'09'
X'OB'
X'OE'

Hardware Product Identifier
Emulated Product Identifier
Software Product Serviceable Component Identifier
Software Product Common Level
Software Product Common Name
Software Product Customization Identifier
Software Product Program Number
Software Product Customization Date and Time
Microcode EC Level
Hardware Product Common Name

Notes:

Chapter 8.

Common Fields

8-111

MS Common Subvectors

1.

The hardware (HW) X'II' Product Identifier subvector is present when
the product classification nibble (byte 2, bits 4-7) is X'I', X'3', or
X'9'.
The software (SW) X'lI' Product Identifier subvector is present
when this nibble is X'4', X'C', or X'E'.

2.

If a PU is sending an Alert for itself, a single Product Set ID
(X'lO') subvector is present. This is the "Indicated Resource" for
purposes of reading this matrix.
If the PU is reporting on an Alert
for an attached device, two X'IO' subvectors are present, in the
following order:
a.

"Alert Sender"--identifies the PU sending the Alert

b.

"Indicated Resource"--identifies the resource that the Alert is
reporting upon

3.

In XID3, the Hardware and Software X'II' subvectors are carried 1n the
X'IO' control vector rather than the X'IO' MS Common subvector.

4.

This subfield is present in the hardware X'II' when a product is
emulating another hardware product.

5.

This subfield is present in the software X'll' for products assigned a
component ID by the IBM National Service Division.
For products not
assigned a component 10, the X'04' and x'oa' subfields are present.
See note 6.

6.

The X'04' and x'oa' subfields are present in the software X'II' if the
X'02' subfield is not present. They are optional when the X'02' is
present. See Note 5.
If, however, the software identified is a
customer-written application, only the x'oa' subfield is present.

7.

One of the X'07' and X'09' subfields is required in the software X'll'
for software products modified by the customer.

Hardware Product Identifier (X'OO') Product Identifier Subfield
This subfield uniquely
hardware product.

o
1
2

a-112

identifies

an

instance

Length (r+l), in binary, of the Hardware Product
Key:
X'OO'
Format type:
X'IO' product instance is identified by a serial
manufacture and sequence number) unique by
X'II' product instance is identified by a serial
manufacture and sequence number) unique by
number
X'I2' product instance is identified by a serial
manufacture and sequence number) unique by
format X'IO' above).
This format provides

SNA Formats

of

a

Identifier subfield

number (i.e., plant of
machine type
number (i.e., plant of
machine type and model
number (i.e., plant of
machine type (as in
the model number not to

MS Common Subvectors

X'13'
X'20'
X'2l'

X'22'

X'40'
X'4l'
3-r

3-6
7-8
9-lS(=r)

uniquely identify a product instance but, for the purpose of
additional information only.
retired
product instance is identified by a repair ID number (i.e., plant of
manufacture and sequence number) unique by machine type
product instance is identified by a repair ID number (i.e., plant of
manufacture and sequence number) unique by machine type and model
number
product instance is identified by a repair ID number (i.e., plant of
manufacture and sequence number} unique by machine type (as in
format X'lO' above). This format provides the model number not to
uniquely identify a product instance but for the purpose of
additional information only.
retired
retired

Product identification
Note:
The originator of a message unit (e.g., NMVT, XID), reporting for
another product that does not supply information required for the Hardware
Product Identifier subfield, inserts binary O's into the appropriate
fields (except for the Machine Type field where EBCDIC O's [X'FO'] are
inserted) of the Product Identification field to indicate that no
identification information is available.
• Format X'lO'
Machine type:
four numeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters
Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') fill on the left

•
3-6
7-9
10-11
l2-l8(=r)

Format X'lI'
Machine type:
four numeric EBCDIC characters
Machine model number:
three upper-case alphanumeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters
Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') filIon the left

•
3-6
7-9
10-11
l2-I8(=r)

Format X'12'
Machine type:
four numeric EBCDIC characters
Machine model number:
three upper-case alphanumeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters
Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') fill on the left

3-6
7-8
9-lS(=r)

3-6
7-9
10-11

• Format X'20'
Machine type:
four numeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters
Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') fill on the left
• Format X'2l'
Machine type:
four numeric EBCDIC characters
Machine model number:
three upper-case alphanumeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters

Chapter 8.

Common Fields

8-113

MS Common Subvectors
12-18(=r) Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') filIon the left
•
3-6
7-9
10-11
12-18(=r)

Format X'22'
Machine type:
four numer1C EBCDIC characters
Machine model number:
three upper-case alphanumeric EBCDIC characters
Plant of manufacture:
two numeric EBCDIC characters
Sequence number: seven upper-case alphanumeric EBCDIC characters,
right-justified, with EBCDIC O's (X'FO') filIon the left

Emulated Product Identifier (X'Ol') Product Identifier Subfield
This subfield identifies the hardware of the product being
emulated
in
sufficient
detail
to
allow
problem
determination

o
1
2-5
6-8(=r)

Length (r+l), in binary, of the Emulated Product Identifier subfield
Key:
X'Ol'
Machine type of product being emulated:
four numeric EBCDIC characters
Model number of product being emulated:
three upper-case alphanumeric
EBCDIC characters

Software Product Serviceable Component Identifier (X'02') Product Identifier
Subfield
This
subfield
identifier and
personnel.

component
transports
the serviceable
release level as assigned by service

o

Length (r+l), in binary, of the Software Product Serviceable Component
Identifier subfield
Key:
X'02'
1
Serviceable component identifier: nine upper-case alphanumeric EBCDIC
2-10
characters
11-13(=r) Serviceable component release level:
three numeric EBCDIC characters

Software Product Common Level (X'04') Product Identifier Subfield
This subfield transports the
modification level numbers
announcement documentation.

o
1

2-3

4-5
6-7(=r)

8-114

common version, release, and
as
given 1n the product

Length (r+l), in binary, of the Software Product Common Level subfield
Key:
X'04'
Common version identifier: numeric EBCDIC characters, right-justified with
X'FO' fill on lef~
Common release identifier: numeric EBCDIC characters, right-justified with
X'FO' filIon left
Common modification identifier: numeric EBCDIC characters, right-justified
with X'FO' filIon left

SNA Formats

MS Common Subvectors

Software Product Common Name (X'06') Product Identifier Subfield
This subfield transports the software common name as given
in the product announcement documentation.

o
1
2-r

length (r+1), in binary, of the Software Product Common Name subfield
Key:
X'06'
Up to thirty characters identifying the software product common name.
The
name is to be decoded using Coded Graphic Character Set 01134-00500,
documented in "Appendix A. SNA Character Sets and Symbol-String Types",
plus three additional code points:
X'48' = " " (period); X'60' = "-"
(minus sign); X'61' = "/" (slash).

Software Product Customization Identifier (X'07') Product Identifier Subfield
This subfield identifies a set of executable instructions,
customized to the user's environment.

o
1
2-r

length (r+1), in binary, of the Software Product Customization Identifier
subfield
Key:
X'07'
Customization identifier:
up to eight upper-case alphanumeric EBCDIC
characters

Software Product Program Number (X'08') Product Identifier Subfield
This subfield transports either the program product number
as assigned by distribution personnel,
or a substitute
value supplied by a user-written software program.

o
1

2-8(=r)

length (r+1), in binary, of the Software Product Program Number subfield
Key:
X'08'
Program product number: seven upper-case alphanumeric EBCDIC characters
Note:
A user-written application program does not send a program product
number in this field.
Instead it sends one of 16 substitute values
comprised of seven upper-case alphanumeric EBCDIC characters having the
following form:
characters 1-4 are the letters USER; character 5 is one
of the characters 0-9, or A-F; characters 6-7 are space (X'40')
characters.
Installation managers have the sole responsibility for
managing the usage of these substitute values within their networks.

Software Product Customization Date and Time (X'09') Product Identifier Subfield
This subfield identifies
executable instructions
environment.

o
1

the date and time that a set of
was customized to the user's

length (r+l), in binary, of the Software Product Customization Date and
Time subfield.
Key:
X' 09'

Chapter 8.

Common Fields

8-115

MS Common Subvectors
2

3-4
5
6(=r)

Year in unsigned packed decimal (i.e., one hex digit for each decimal
digit)
Julian day in unsigned packed decimal, right-justified with O's as fill
Hour in unsigned packed decimal (24-hour clock)
Minute in unsigned packed decimal

Microcode EC Level (X'OB') Product Identifier Subfield
This subfield identifies the engineering change (EC) level
of the failing microcode
component (e.g.,
microcode
feature EC level or microcode subsystem level such as
channel, power, or storage)

o
1
2-r

Length (r+1), in binary, of the Microcode EC Level subfield.
Key:
X'OB'
Microcode EC Level:
up to eight upper-case alphanumeric EBCDIC characters

Hardware Product Common Name (X'OE') Product Identifier Subfield
This subfield provides the hardware common name
in the product announcement documentation

o
1
2-r

as given

Length (r+1), in binary, of the Hardware Product Common Name subfield
Key:
X' 0 E'
Up to fifteen upper-case alphanumeric EBCDIC characters identifying the
hardware product common name

Self-Defining Text Message (X'31') MS Common Subvector
This MS common subvector transports a text message,
additional data identifying the nature of the message
sender, the language of the message, and how the message
is encoded.

o
1
2-p

8-116

Length (p+1), in binary, of the Self-Defining Text Message subvector
Key:
X'31'
Subfields containing a text message, as well as additional information
characterizing the message.
Note:
The following subfield keys are used as indicated:

SNA Formats

MS Common Subvectors

Subfield

Presence in Self-Defining
Text Message (X'31')
Common Subvector

Coded Character Set ID (X'02')

Required

National Language ID (X'll')

Required

Sender ID (X'21')

Required

Text Message (X'30')

Required

Coded Character set ID (X'02') Self-Defining Text Message Subfield
This subfield identifies the coded
the text message is encoded.

o
1
2-5

character set in which

Length (q+l), in binary, of the Coded Character Set ID subfield
Key:
X'02'
Coded character set ID:
two 4-digit hexadecimal numbers that specify
uniquely the coded character set in which the accompanying user text
message is encoded.
Bytes 2-3 contain a 4-digit hexadecimal number
identifying a character set, while bytes 4-5 contain a 4-digit hexadecimal
number identifying a code page. Receivers are responsible for documenting
the coded character set IDs, as well as the coded character sets
themselves, that they support in this subvector.

National Language ID (X'll') Self-Defining Text Message Subfield
This subfield identifies the national language in which
the text message is written.
A national language is
identified by the conjunction of a generic language code
(e.g., English) and a country code (e.g., US, UK, Canada).

o
1
2-3

4-6

Length (q+l), in binary, of the National Language ID subfield
Key: X'll'
Country Code: a code point indicating the country component of the
national language ID.
A value of X'OOOO' indicates that no country code
is specified, i.e., that the sender is specifying only a generic language
code.
Nonzero values are the hexadecimal equivalents of the three decimal
digit country codes specified in the ISO International Standard (IS) 3166.
For example, the United States would be identified in this field as
X'0348', since it is identified in IS 3166 as 840.
Generic language code: a code point indicating the generic language
component of the national language ID. This code point is based on the
representation in the ISO Draft International Standard (DIS) 639.2.
For
the purpose of this encoding, the period in DIS 639.2 is treated not as a
decimal point, but as a delimiter between two decimal integers.
The first

Chapter 8.

Common Fields

8-117

MS Common Subvectors
two bytes of the generic language code are the hexadecimal equivalent of
the decimal integer before the period; the third byte of the generic
language code is the hexadecimal equivalent of the decimal integer after
the period.
For example, the Hungarian language would be identified in
this field as X'03BIOB', since it is identified in DIS 639.2 as 945.11.
English would be identified as X'001400', since it is identified in DIS
639.2 as 20.

Sende~

ID (X'21') Self-Defining Text Message Subfield
This subfield identifies, in generic terms, the nature of
the entity that sent the text message.
This information
will be displayed by the receiver of the message.

o
1

2

Length (q+l), in binary, of the Sender ID subfield
Key:
X'2l'
Sender ID code: a code point characterizing the sender of the text
message.
Defined codes are:
X'Ol' terminal user:
A person who, when entering the message, is solely a
consumer of system resources, i.e., plays no role in providing them
X'02' operator: A person who, when entering the message, is in some way
involved in providing or managing system resources
X'll' application program: A program written for or by an end user that
applies to the end user's work
Note:
This program may be implemented in either software or
microcode.
X'12' control program:
A program that controls other system resources.
Note:
This program may be implemented in either software or
microcode

Text Message (X'30') Self-Defining Text Message Subfield
This subfield transports a text message.

o
1
2-q

Length (q+l), in binary, of the Text Message subfield
Key:
X'30'
Text message

Relative Time (X'42') MS Common Subvector
This MS common subvector indicates when a record
by
created relative
to other
records created
originating component.

o
1

2

8-118

was
the

Length (p+l), in binary, of the Relative Time subvector
Key:
X'42'
Time units:
X'OO' tenths of a second
X'01'-X'7F' a number that, when divided into the timer data (in bytes
3-6), converts the value to seconds
X'90' microseconds

SNA Formats

MS Common Subvectors
X'AO'
X'CO'
X'DO'
X'EF'

3-6(=p)

milliseconds
minutes (not used in Alerts)
hours (not used in Alerts)
indicates time value is purely a sequence indicator showing relative
order only
Time, in binary, in the units defined by byte 2

Data Reset Flag (X'4S') MS Common Subvector

This MS common subvector acknowledges
function has been performed.

o
l(=p)

that

the

reset

Length (p+l), in binary, of the Data Reset Flag subvector
Key:
X'4S'

LAN Link Connection Subsystem Data (X'Sl') MS Common Subvector
This MS common subvector transports data on
of the LAN link connection.

o
1
2-p

the elements

Length (p+l), in binary, of the LAN Link Connection SUbsystem Data
subvector
Key:
X'Sl'
One or more subfields containing data specific to the link connection
elements (listed by Key value below and described in detail following):
X'02'
X'03'
X'04'
X'OS'
X'06'
X'07'
X'08'
X'09'
X'OA'
X'23'
X'24'
X'26'
X'28'

Ring or Bus Identifier
Local Individual MAC Address
Remote Individual MAC Address
LAN Routing Information
Ring Fault Domain Description
Beaconing Data
Single MAC Address
Fault Domain Error Weight Pair
Bridge Identifier
Local Individual MAC Name
Remote Individual MAC Name
Fault Domain Names
Single MAC Name

Ring or Bus Identifier (X'02') LAN Link Connection Subsystem Data Subfield
This subfie1d transports the ring number (for a token-ring
LAN) or the bus number (fo~ a CSMA or token-bus LAN).

o
1

2-3(=q)

Length (q+l), in binary, of the ring or bus identifier subfield
Key:
X'02'
Ring or bus number, in hexadecimal

Chapter 8.

Common Fields

8-119

MS Common Subvectors

Local Individual MAC Address (X'03') LAN Link Connection Subsystem Data Subfield
This subfield transports the address of the MAC within the
node sending the MS major vector.

o
1

2-7(=q)

Length (q+l), in binary, of the local individual MAC address subfield
Key:
X'03'
Local individual MAC address, in hexadecimal

Remote Individual MAC Address (X'04') LAN Link Connection Subsystem Data Subfield
This subfield transports the address of the MAC, part of
the link connection, within the adjacent node.

o
1
2-7(=q)

Length (q+l), in binary, of the remote individual MAC address subfield
Key:
X'04'
Remote individual MAC address, in hexadecimal

LAN Routing Information (X'OS') LAN Link Connection Subsystem Data Subfield
This subfield transports the routing information used by a
link.

o
1

2-q

Length (q+l), in binary, of the LAN routing information subfield
Key:
X'OS'
Routing information, not to exceed 18 bytes, in hexadecimal. For details,
see the Routing Information field in IBM Token-Ring Network Architecture
Reference, SC30-3374.

Fault Domain Description (X'06') LAN Link Connection Subsystem Data Subfield
This subfield identifies a pair of LAN token-ring stations
as a fault domain, i.e., the upstream and the downstream
LAN token-ring stations and the cable between them.

o
1
2-7
8-13(=q)

Length (q+l), in binary, of the Ring Fault Domain Description subfield
Key:
X'06'
Individual MAC address of downstream station, in hexadecimal
Individual MAC address of upstream station, in hexadecimal

Beaconing Data (X'07') LAN Link Connection Subsystem Data Subfield
This subfield specifies the type of beacon detected by the
LAN adapter.

o
1
2(=q)

8-120

Length (q+l), in binary, of the Beaconing Data subfield
Key:
X'07'
Beaconing type:
X'OI' type 1, recovery mode set
X'02' type 2, signal loss

SNA Formats

MS Common Subvectors
X'03' type 3, streaming signal

single MAC Address (X'OS') LAN Link Connection SUbsystem Data Subfield
This subfield transports the address
associated with the failure.

o
I

2-7(=q)

of the

MAC element

Length (q+l), in binary, of the Single MAC Address subfield
Key:
X'OB'
Single MAC address, in hexadecimal

Fault Domain Error Weight Pair (X'09') LAN Link Connection Subsystem Data Subfield
This subfield indicates the severity of the problems
reported by two MAC elements (LAN stations) belonging to a
fault domain.
0
I

2-3

4-5(=q)

Length (q+l), in binary, of the Fault Domain Error Weight Pair subfield
Key:
X'09'
Severity weight, in binary, for the downstream MAC element (LAN station)
problems
Severity weight, in binary, for the upstream MAC element (LAN station)
problems

Bridge Identifier (X'OA') LAN Link Connection Subsystem Data Subfield
This subfield
bridge.

o
I

2-5

transports the bridge

identifier of

a LAN

Length (q+l), in binary, of the Bridge Identifier subfield
Key:
X'OA'
Bridge identifier, composed of three hexadecimal parts: a ring or bus
number, followed by a bridge number, followed by another ring or bus
number. The ring or bus with the lower number is always identified first.
The bridge identifier occupies less than 4 bytes, the amount less
depending on the partitioning of the LAN routing information field.
The
bridge identifier is left-justified, with the remaining portion of the
subfield being O's.

Note: The partitioning df this field into its three parts is not
specified, but is necessarily unique within a LAN.
Local Individual MAC Name (X'23') LAN Link Connection Subsystem Data Subfield
This subfield transports
within the sending node.

o
1

the

name

of the

MAC

element

Length (q+l), in binary, of the Local Individual MAC Name subfield
Key:
X'23'

Chapter 8.

Common Fields

8-121

MS Common Subvectors
2-q

Local individual MAC name: a string of no more than 16 upper-case
alphanumeric EBCDIC characters plus four additional code points:
X'SB'
X'6C'
X' 7 B'
X'7C'

= "$"
= "X"
= "I"
= "@"

(dollar sign)
(percent sign)
(pound or number sign)
(at sign)

Remote Individual MAC Name (X'24') LAN Link Connection Subsystem Data Subfield
This subfield transports the name of the MAC element, part
of the link connection, within the adjacent node.

o
I

2-q

Length (q+l), in binary, of the Remote Individual MAC Name subfield
Key:
X'24'
Remote individual MAC name: a string of no more than 16 upper-case
alphanumeric EBCDIC characters plus four additional code points:
X'SB'
X'6C'
X'7B'
X'7C'

= "$"
= "X"
= "I"
= "@"

(dollar sign)
(percent sign)
(pound or number sign)
(at sign)

Fault Domain Names (X ' 26') LAN Link Connection Subsystem Data Subfield
This subfield transports the names of the upstream and the
downstream LAN ring stations belonging to a fault domain.

o
1
2-q

Length (q+l), in binary, of the Ring Fault Domain Names subfield
Key:
X'26 1
Pair of Entries

Note:

o
l-r

Each entry contains a Length field and a Name field; the first
entry is for the downstream MAC element, and the second entry is for the
upstream MAC element. Each entry has the following form (shown
zero-origin).
Length (r+l), in binary, of the following name plus this length field
Individual MAC name: a string of no more than 16 upper-case alphanumeric
EBCDIC characters plus four additional code points:
X'SB' = I $ I
X ' 6C' = I X '
X'7B' = I I '
X'7C' = 'Ol'

(dollar sign)
(percent sign)
(pound or number sign)
(at sign)

Single MAC Name (X'28') LAN Link Connection Subsystem Data Subfield
This subfield
the failure.

o
1
2-q

8-122

transports the name

of the MAC

related to

Length (q+l), in binary, of the Single MAC Name subfield
Key:
X'28'
Single MAC name: a string of no more than 16 upper-case alphanumeric
EBCDIC characters plus four additional code points:

SNA Formats

MS Common Subvectors
X'SB'
X'6C'
X'7B'
X'7C'

=
=
=
=

'$ ,

(dollar sign)
(percent sign)
, I' (pound or number sign)
'@ , (at sign)
'% '

Link Connection Subsystem Configuration Data (X'52') MS Common Subvector
This MS
common
connections.

o
1
2-p

subvector

transports

for

data

link

Length (p+l), in binary, of the LCS Configuration Data subvector
Key:
X'S2'
One or more subfields containing LCS configuration data (listed by key
value below and described in detail following):
X'Ol'
X'02'
X'04'
X'06'
X'07'
X'08'

Port Address
Remote Device Address
Local Device Address
LCS Link Station Attributes
LCS Link Attributes
LPDA Fault LSL Descriptor

Port Address (X'Ol') Link Connection Subsystem Configuration Data Subfield
This subfield transports
connection.

o
1

2-3(=q)

the port

address

of the

link

Length (q+l), 1n binary, of the Port Address subfield
Key:
X' 01'
Port address, 1n binary

Remote Device Address (X'02') Link Connection Subsystem Configuration Data Subfield
This subfield
link station.

o
1
2(=q)

transports the

DLC address

of the

remote

Length (q+l), in binary, of the Remote Device Address subfield
Key:
X'02'
Remote link station DLC address, in hexadecimal; e.g., for a LAN, the
destination link service access point (DSAP) address

Local Device Address (X'04') Link Connection Subsystem Configuration Data Subfield
This subfield
station.

o
1

2(=q)

transports the

address of

the local

link

Length (q+l), 1n binary, of the Local Device Address subfield
Key:
X'04'
Local link station DLC address, in hexadecimal; e.g., for a LAN, the
source service access point (SSAP) address

Chapter 8.

Common Fields

8-123

MS Common Subvectors

LCS Link Station Attributes (X'Ob') Link Connection Subsystem Configuration Data
Subfield
This subfield identifies link station attributes.

o
1
2

3(=q)

Length (q+l)1 in binarYI of the LCS Link Station Attributes subfield
Key:
X'06'
Link station role:
X'Ol' primary
X'02' secondary
X'03' negotiable
Node type for the remote link station:
X'Ol' type 1
X'02' type 2.0
X'03' type 4
X'04' type 2.1
X'80' non-SNA I e.g'l used for BSC links

LCS Link Attributes (X'07') Link Connection Subsystem Configuration Data Subfield
This subfield transports LCS link connection attributes.

o
I

2

3

4

S(=q)

Length (q+l)1 in binarYI of the LCS Link Attributes subfield
Key:
X'07'
Link connection type used:
X'OI' nonswitched
X'02' switched
Half- or full-duplex:
X'OI' half-duplex
X'02' full-duplex
DLC protocol type:
X'Ol' SDLC
X'02' BSC
X'02' start-stop
Point-to-point or multipoint:
X'Ol' point-to-point
X'02' multipoint

LPDA Fault LSL Descriptor Subfield (X'OS') Link Connection Subsystem Configuration
Data Subfield
This subfield transports the link segment identifier, also
referred to as level, of the multi-segment LPDA link where
the failure occurred.

o
1
2

8-124

Length (q+l), in binary, of the LPDA Fault LSL Descriptor subfield
Key:
X'08'
LPDA fault link segment level (LSL) descriptor value, in binary

SNA Formats

MS Common Subvectors

Sense Data (X'7D') MS Common Subvector
This MS common subvector transports error information back
to the control point that initiated an MS request.
The
subvector contains a 4-byte field for sense data.

o
1

2-5(=p)

length (p+1), in binary, of the Sense Data subvector
Key:
X' 7D'
Sense data, as defined in "Chapter 9. Sense Data"

Chapter 8.

Common Fields

8-125

This page intentionally left blank

8-126

SNA Formats

CHAPTER 9.

SENSE DATA

The sense data included with an EXCEPTION REQUEST (EXR), a negative response, an
UNBIND request, a Sense Data (X'7D') MS common subvector, a function management
header type 7 (FMH-7), or an extended sense data control vector (X'3S') is a
four-byte field (see Figure 9-1) that includes a one-byte category value, a one-byte
modifier value, and two bytes of sense code specific information, whose format is
defined along with the sense code definition, below.

Byte

1
1<
1
1<

Figure 9-1.

o

Byte
1

Byte
2

Category

Modifier

Byte
3

Sense-code specific
information

Sense Code-->1
>

Sense Data

Sense Data Format

Together, the category byte 0, the modifier byte 1, and the sense code specific
bytes 2 and 3 hold the sense data defined for the exception condition that has
occurred.
The following categories are defined; all others are reserved:

VALUE

CATEGORY

X'OO'
X'OS'
X'lO'
X'20'
X'40'
X'SO'

User Sense Data Only
Request Reject
Request Error
State Error
Request Header (RH) Usage Error
Path Error

Chapter 9.

Sense Data

9-1

The category User Sense Data Only (X'OO') allows the end users to exchange sense
data in bytes 2-3 for conditions not defined by SNA within the other categories (and
perhaps unique to the end users involved).
The modifier value is also X'OO'.
In earlier versions of SNA, user data (as well as implementation-specific data)
generally could be carried in bytes 2-3 for all categories.
This is no longer the
case.
Bytes 2-3 are used generally only for SNA-defined conditions for nonzero
categories; exceptions for implementation-specific use are documented in the
appropriate product publications.
The sense codes for the other categories are discussed below.

REQUEST REJECT (CATEGORY CODE

= X'OS')

This category indicates that the request was delivered to the intended component and
was understood and supported, but not executed.
Category and modifier (in hexadecimal):
0801

Resource Not Available:
RU is not available.

The LU, PU, link station, or link specified in an

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

9-2

0000

No specific code applies.

0001

Independent LU Does Not Receive ACTLU:
An ACTLU has been sent
by the SSCP to an independent LU (sent by BF).

0002

Reserved Resources Requested for Sessions Exceed Allowable
Maximum:
The resource reservation request in RNAA exceeds the
maximum allowed by system definition.
The address was not
assigned and no change was made to the current reservation of
resources for the LU.

0003

Name aliasing cannot be performed because the name alias
function is not available.

0004

A switched connection currently exists for the link being
activated, and the SSCP or the subarea PU does not support the
protocols necessary to allow take over of such a link.

0005

A SETCV has been received for a resource that is still
represented in the pool of available control blocks.

0006

The line is not associated with a line adapater.

SNA Formats

0007

The line is associated with a line adapter that is not
installed or not attached to a communications processor.

0008

The line is associated with a line adapter that is
inoperative.

0009

The lU is not available because it is not ready to accept
sessions.

OOOA

The PlU is not available b~cause it is being taken down, and
is therefore not accepting new sessions.
The initiation
request should not be retried.

OOOB

The PlU is not available because it is unable to
the PlU-SlU role specification.

comply

with

OOOC

The SLU is not available because it is unable to
the PLU-SlU role specification.

comply

with

0000

The LU is not available because its SSCP is in the process
of being taken down, and is therefore not allowing new
sessions to be started. The initiation request should not be
retried.

OOOE

The LU is not available because an intermediate gateway SSCP
is in the process of being taken down, and is therefore not
allowing new sessions to be started.

OOOF

The SLU is not available because it is being taken down, and
is therefore not accepting new sessions. The initiation
request should not be retried.

4001-4002

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0802

Intervention Required: Forms or cards are required at an output device, or
a device is temporarily in local mode, or other conditions require
intervention.

0803

Missing Password: The required password was not supplied.

0804

Invalid Password: Password was not valid.

0805

Session Limit Exceeded: The requested session cannot be activated, as one
of the NAUs is at its session limit, for example, the lU-lU session limit
or the (LU, mode) session limit. This sense code applies to ACTCDRM,
INIT, BIND, and CINIT requests.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

Chapter 9.

Sense Data

9-3

0001

If accepted~ the BIND request would prevent either the receiving LU
or the sending LU from activating the number of contention winner
sessions to the partner LU that were agreed upon during a
change-number-of-sessions procedure.

0002

If accepted, the BIND request would cause the XRF-backup session
limit to be exceeded.

0003

If accepted, the BIND request would cause the XRF-active sessionlimit to be exceeded.
Note:
The session limit for XRF-active sessions is 1. An
XRF-active BIND is valid only if there are no XRF-active or
XRF-backup sessions with the receiving SLU.

0806

0009

If accepted, the request would cause the PLU session limit to be
exceeded.

OOOA

If accepted, the request would cause the SLU session limit to be
exceeded.

OOOB

The request was rejected because a session already exists between
the same LU pair, and at least one of the LUs does not support
parallel sessions.

Resource Unknown:
For example, the request contained a name or address
not identifying a PU, LU, SSCP, link, or link station known to the
receiver or the sender.
Note:
In an interconnected network environment, this sense code may be
set by an SSCP in whose subnetwork and domain the LU was expected to
reside; it is not set by an SSCP that is only an intermediary on the
session-setup path.
A gateway SSCP examines the Resource Identifier
control vector in a session setup request (for example, COINIT), to
determine whether the LU is in the SSCP's subnetwork and domain.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

The resources identified in an SNA Address List (X'04') MS common
subvector are unknown to the PU receiving the request.
Note:
When this sense data flows in a -RSP(NMVT), the referenced
X'04' subvector is the one that was present in the corresponding
request NMVT. When this sense data flows in a Sense Data (X'70') MS
common subvector, the referenced X'04' subvector is present with the
X'70' subvector in the same major vector.

0002

9-4

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

SNA Formats

0007

The lU address in bytes 8-9 of RNAA type X'4' is already in the free
pool.

OOOA

The configuration identifier specified in a management services
command is not recognized by the DlC manager at the receiving node.

0011

An unknown OlU name was specified in the request.

0012

An unknown DlU name was specified in the request.

0013

An unknown SlU name was specified 1n the request.

0014

An unknown PlU name was specified in the request.

0015

An unknown OlU address was specified 1n the request.

0016

An unknown DLU address was specified in,the request.

0017

An unknown SlU address was specified in the request.

0018

An unknown PlU address was specified in the request.

0021

The session-initiation request specified that the receiving SSCP
is the SSCP having the DLU in its domain, but the DLU is unknown
to the receiving SSCP.

0022

The originator of the request is unknown to the receiver.

0023

The destination of the request or response is unknown to the sender.

0024

An unknown LUI name was specified in the request.

0025

An unknown lU2 name was specified in the request.

0026

The SSCP does not have a session with the boundary function PU of an
independent LU.

0027

The PU associated with a switched SlU is unknown.
processing for the switched SLU cannot proceed.

0028

NAUI network address is unknown.

0029

NAU2 network address is unknown.

002A

The NAU name in the CONTACT or ACTlU does not correspond to the
resource at the target address.

Session setup

0807

Resource Not Available--lUSTAT Forthcoming: A subsidiary device will be
unavailable for an indeterminate period of time.
LUSTAT will be sent when
the device becomes available.

0808

Invalid Contents ID: The contents ID contained on the ACTCDRM request was
found to be invalid.

Chapter 9.

Sense Data

9-5

0809

Mode Inconsistency: The requested function cannot be performed in the
present state of the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

9-6

0000

No specific code applies.

0001-0000

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

OOOE

The resource to be ORed is a sysgenned resource and
as not OR-deletable.

000F-0013

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0014

ANS mismatch discovered.

0015

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0016

The PU type on SETCV does not match the actual PU type.

0017,0018

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0019

A SETCV was received containing a value for the SOLC BTU send
limit that conflicts with the previous value received.

OOlA,OOlB

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

OOlC

The RNAA request contains a network 10 that is not known to
the gateway PU.

0010

An address pair session key in a Network-Qualified Address
Pair control vector (X'15') is not known to the gateway PU.

OOlE

A gateway PU received an RNAA request for a cross-network
session and all possible address transforms for the named
resource are allocated.

001F

Retired

0020

The gateway node receiving an RNAA request cannot support
another session between the named resource pair.

SNA Formats

1S

defined

080A

0021-0023

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0024

A PU received an ACTPU request with the SSCP-PU Session
Capabilities control vector (X'OB') indicating that the
sending SSCP does not support ENA, but the PU does not know
the SSCP's maximum subarea address value.

0025

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0026

A SETCV was received containing an SDlC BTU send limit of

0027

A request for a function was received by a component but the
function was not enabled or activated.

0028

Cleanup termination of an LU-LU session has been converted to
a forced termination by the lU.
The SSCP must wait for
session ended signals before deleting its session awareness
records of the session.

0030

An FNA was received for an LU that has an active SSCP-LU
session.

0031

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0032

A BFSESSINFO was received when the LU was not pending
BFSESSINFO;
the reported sessions will be terminated, and the
associated network addresses will be freed.
This sense data
is also included in the BFCLEANUP when the sessions are
terminated.

0033

A BIND with the same lFSID as an existing pending-reset
session has been received by a boundary function from a
peripheral PlU.

0034

A termination request has been received for a resource that
has been taken over by an SSCP. The termination type is not
strong enough to apply to the resources.
The termination
type needs to be Forced or Cleanup.

0035

A cross-domain resource,
active,
is inactive.

which

was

expected

to

o.

be

Permission Rejected: The receiver has denied an implicit or explicit
request of the sender; when sent in response to BIND, it implies either
that the secondary lU will not notify the SSCP when a BIND can be
accepted, or that the SSCP does not recognize the NOTIFY vector key X'OC'.
(See the X'0845' sense code for a contrasting response.)

Chapter 9.

Sense Data

9-7

oaOB

Bracket Race Error: Loss of contention within the bracket protocol.
error can arise when bracket initiation/termination by both NAUs is
allowed

This

oaoc

Procedure Not Supported:
A procedure (Test, Trace, IPL, REQMS type, MS
major vector key) specified in an RU is not supported by the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001-0003

Set aside for implementation specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0005

The MS major vector key is not supported by the receiver.

0006

The MS major vector is identified as one that contains a
command,
but the receiver does not recognize or support the
command subvector.
(See the X'Oa6C' sense code for the case
in which the command subvector is identified, but an
additional required subvector is missing.)

0007

A request for a function is supported by the receiver, but the
resource identified in the request does not support that
function (no function is specifically indicated).

0009

A request for session information retrieval for an independent
LU was received in an REQMS; such requests are permitted only
in an NMVT.

OOOA

A request was received containing an address list MS subvector
with multiple entries, but the receiver supports only a single
entry in such a subvector.

0010

Reserved

4001,4003

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

oaOD

NAU Contention: A request to activate a session was received while the
receiving half-session was awaiting a response to a previously sent
activation request for the same session;
for example, the SSCP receives
an ACTCDRM from the other SSCP before it receives the response for an
ACTCDRM that it sent to the other SSCP and the SSCP ID in the received
ACTCDRM was less than or equal to the SSCP ID in the ACTCDRM previously
sent.

oaOE

NAU Not Authorized:
requested resource.

9-a

SNA Formats

The requesting NAU does not have access to the

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

080F

0000

No specific code applies.

0001

The PU, according to its system definition, does not accept an ACTPU
from any SSCP having the network ID of the sending SSCP.

0003

The link station received a CONTACT from an unauthorized SSCP.

0004

A BFClEANUP was received from an unauthorized SSCP.

0005

An RNAA was received from an unauthorized SSCP.

End User Not Authorized:
the requested resource.

The requesting end user does not have access to

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

6051

Access Security Information Invalid: The request specifies an
Access Security Information field that is unacceptable to the
receiver; for security reasons, no further detail on the error is
provided. This sense data is sent in FMH-7 or UNBIND.

0810

Missing Requester ID: The required requester ID was missing.

0811

Break: Asks the receiver of this sense code to terminate the present chain
with CANCEL or with an FMD request carrying EC. The half-session sending
the Break sense code enters chain-purge state when Break is sent; the
half-session receiving the Break sense code discards the terminated chain
without ever retransmitting it.

0812

Insufficient Resource:
Receiver cannot act on the request because of a
temporary lack of resources.
Bytes 2 and 3 may contain the following sense code specific information:
0000

No specific code applies.

0001

More PUs or lUs are requested by RNAA than are present in the pool.

0002

More PUs or lUs are requested by RNAA than attachment resource will
hold.

0003

Resources are not currently available to support an XRF session.

0004

The RNAA request indicates that the requested address must be
pre-ENA compatible, but no pre-ENA compatible address is available.

0005

The Requested Reserved Resources for Sessions Are Not Available:
In
RNAA, a reservation of session resources exceeded those available;

Chapter 9.

Sense Data

9-9

no address was assigned and no change was made to the LUis current
reservation.

0813

0007

Insufficient resources are available for LU address allocation.

OOOB

A BFSESSINFO was received for an unknown LU.

OOOD

Insufficient buffers exist to activate a session.

0011

Insufficient storage is available to the SNA component to satisfy
the request at this time.

Bracket Bid Reject--No RTR Forthcoming:
BID (or BB) was received while
the first speaker was in the in-bracket state, or while the first speaker
was in the between-brackets state and the first speaker denied permission.
RTR will not be sent.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

Bracket Bid Reject: The component was in the in-bracket state when
a bracket request was received.

0002

Bracket Bid Reject: The component was in the between-bracket state
when a bracket request was received.

0814

Bracket Bid Reject--RTR Forthcoming: BID (or BB) was received while the
first speaker was in the in-bracket state, or while the first speaker was
in the between-brackets state and the first speaker denied permission.
RTR will be sent.

0815

Function Active: A request to activate a network element or procedure was
received, but the element or procedure was already active.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

A session activation request was received by a boundary function to
activate a session that was already active.

0002

A session activation request was received by a gateway function to
activate a cross-network session that was already active.

0003

Processing for another management services request in progress.
Sender should retry the request.
Note: This sense data is sent only by a type 2 node, which may lack
sufficient queuing space.

9-10

SNA Formats

0004

A BIND was received from a T2.1 node when the session is already
active; i.e., the lFSID is in use. The receiver rejects the BIND.

0005

An IPl function (the loading or storing of a load module) is in
progress.

0816

Function Inactive: A request to deactivate a network element or procedure
was received, but the element or procedure was not active.

0817

link or link Resource Inactive: A request requires the use of a link or
link resource that is not active.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0818

0000

No specific code applies.

0001

link inactive.

0002

link station inactive.

0003

Switched link connection inactive.

4001

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

link Procedure in Process: CONTACT, DISCONTACT, IPl, or other link
procedure in progress when a conflicting request was received.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001,0002

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see implementation documentation
for details of usage.

0003

CONTACT Not Serialized, Retry: An initial CONTACT procedure
is in progress and a nonactivation CONTACT was received by the
PU.
The nonactivation CONTACT is rejected until the initial
CONTACT procedure is completed.

0004

Set aside for implementation-specific use, and will not be
otherwise defined in SNA; see imp~ementation documentation
for details of usage.

0005

link problem determination test for a modem in progress.

0006

Online terminal test in progress.

0007

SDlC link test, level 2, in progress.

Chapter 9.

Sense Data

9-11

0009

Test initiated from the modem panel is in progress.

0819

RTR Not Required:

Receiver of Ready To Receive has nothing to send.

081A

Request Sequence Error:

Invalid sequence of requests.

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings_allowed are:
0000

No specific code applies.

0001

An ACTLU was received and no SSCP-PU session exists.

0002

An IPL or DUMP RU sequence error has occurred.

0004

An NC-ER-TEST was to be sent as a result of receiving a ROUTE-TEST
request. The ROUTE-TEST was sent in one subnetwork, the NC-ER-TEST
was to be sent in another. The SSCP sending the ROUTE-TEST did not
have a required alias address within the subnetwork where the
NC-ER-TEST was to be sen~.
(Before sending ROUTE-TEST, the SSCP
sends RNAA, or the installation predefines the alias address, so
that an origin SSCP address is available within the subnetwork of
the route being tested.
This address is then specified in the
NC-ER-TEST RU.)

0006

RNAA Rejected:
If the PU of the node to which an LU is to be added
was RNAA added and a control vector has not been received, the RNAA
is rejected. A SETCV for the PU has not been received and
processed.

081B

Receiver in Transmit Mode:
A race condition exists: a normal-flow
request was received while the half-duplex contention state was
not-receive, (*S,~R), or while resources (such as buffers) necessary for
handling normal-flow data were unavailable.
(Contrast this sense code
with X'2004', which signals a protocol violation.)

08lC

Request Not Executable: The requested function cannot be executed,
because of a permanent error condition in the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-12

0000

No specific code applies.

0001

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

0002

The receiver has an error resulting from a software problem that
prevents execution of the request.

OOBI

An SDLC error was detected during link problem determination for a
modem.

SNA Formats

00B2

A modem error (for example, modem check) was detected during link
problem determination.

00B3

A timeout threshold was exceeded for a link problem determination
aid modem response.

00B4

An overrun or underrun occurred in the node using the link
connection during link problem determination for a modem.

00B5

Data Check was signaled during lPOA-2 test.

00B6

Format exception was signaled during LPOA-2 test.

00B7

lPOA-2 modem test was attempted and failed because of a
communication controller equipment (for example, scanner) error.

OnOm

An error was detected by the OLC manager of the receiving node
during the execution of a management services request.
If n=X'A',
the lin~ connection status has not changed from the state previous
to the execution; if n=X'B', the link connection status was modified
from the state existing previous to the execution. The error is
specified as follows: m=X'l' for volatile storage error, m=X'2' for
nonvolatile storage (e.g., file access error), m=X'3' for link
connection component (e.g., modem) interface error, and m=X'4' for
unspecified software error conditions.

Sense code specific information settings 0004, 0008, OOOC, 0010, 0014,
0018, 0020, 0028, 0030, 0034, 0038, 003C, 0040, 0072, 0098, OOAB,
0100-0109, 0120-0125, 0149, 0189-0191, 0200-0209, 0220-0225, 0290, 0291,
07**, and 08** are all set aside for implementation-specific use, and will
not be otherwise defined in SNA; see implementation documentation for
details of usage.
0810

Invalid Station/SSCP ID: The station ID or SSCP 10 in the request was
found to be invalid.

081E

Session Reference Error: The request contained reference to a half-session
that either could not be found or was not in the expected state (generally
applies to network services requests).
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

No Session Found: The session identified in the BFCLEANUP was not
found; the BFCLEANUP is rejected.

0002

The session identified in the BFCINIT was not found; the BFCINIT is
rejected.

0003

No session was found
services request.

during the

processing

Chapter 9.

of a

session

Sense Data

9-13

0004

The appropriate session was found during processing of a
session services request, but the session is not in the expected
state.

081F

Reserved

0820

Control Vector Error:
Invalid data for the control vector specified by
the target network address and key.

0821

Invalid Session Parameters: Session parameters were not valid or not
supported by the half-session whose activation was requested.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0003

The primary half-session requires cryptography,
but
secondary half-session does not support cryptography.

the

0004

The secondary half-session requires cryptography, but
primary half-session does not support cryptography.

the

0005

Selective or required cryptography is specified, but no SLU
cryptographic data key is provided.

0822

Link Procedure Failure: A link-level procedure has failed due to link
equipment failure, loss of contact with a link station, or an invalid
response to a link command.
(This is not a path error, since the request
being rejected was delivered to its destination.)

0823

Unknown Control Vector:
The control vector specified by a network address
and key is not known to the receiver.

0824

Logical Unit of Work Aborted: The current unit of work has been aborted;
when sync point protocols are in use, both sync point managers are to
revert to the previously committed sync point.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

For LU 6.2, Backout Initiated: A transaction program or its LU has
initiated backout. The protected resources for the distributed
logical unit of work are to be restored to the previously committed
sync point. This sense data is sent only in FMH-7.
For non-LU 6.2, no specific code applies.

0825

Component Not Available: The LU component (a device indicated by an FM
header) is not available.

0826

FM function not supported:
supported by the receiver.

9-14

SNA Formats

A function requested in an FMD RU is not

0827

Intermittent Error--Retry Requested:
An error at the receiver caused an
RU to be lost. The error is not permanent, and retry of the RU (or chain)
is requested.

0828

Reply Not Allowed: A request requires a normal-flow reply, but the
outbound data flow for this half-session is quiesced or shut down, and
there is no delayed reply capability.

0829

Change Direction Required: A request requires a normal-flow reply, but
the half-duplex flip-flop state (of the receiver of the request) is
not-send, and CD was not set on the request. Therefore, there is no
delayed reply capability.

082A

Presentation Space Alteration:
Presentation space altered by the end user
while the half-duplex state was not-send, (~S,*R);
request executed.

082B

Presentation Space Integrity Lost:
Presentation space integrity lost (for
example, cleared or changed) because of a transient condition--for
example, because of a transient hardware error or an end user action such
as allowing presentation services to be used by the SSCP.
(Note:
The
end-user action described under X'082A' and X'084A' is excluded here.)

082C

Resource-Sharing Limit Reached: The request received from an SSCP was to
activate a half-session, a link, or a procedure, when that resource was at
its share limit.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

Invalid Request: The specified link station has already received a
CONTACT and is therefore under the control of another SSCP.
This
CONTACT would exceed the share limit (=1).

0820

LU Busy: The LU resources needed to process the request are being used;
for example, the LU resources needed to process the request received from
the SSCP are being used for the LU-LU session.

082E

Intervention Required at LU Subsidiary Device: A condition requiring
intervention, such as out-of-paper, power-off, or cover interlock open,
exists at a subsidiary device.

082F

Request Not Executable because of LU Subsidiary Device: The requested
function cannot be executed, due to a permanent error condition in one or
more of the receiver's subsidiary devices.

0830

Session-Related Identifier Not Found: The receiver could not find a
session-related identifier for a specified session.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

Chapter 9.

Sense Data

9-15

0001

PCID not found for the specified resources.

0002

lSID not found for the specified session.

0831

lU Component Disconnected: An lU component is not available because of
power-off or some other disconnecting condition.

0832

Invalid Count Field: A count field contained in the request indicates a
value too long or too short to be interpreted by the receiver, or the
count field is inconsistent with the length of the remaining fields.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
nnnn

Bytes 2 and 3 contain a binary count that indexes (zero-origin) the
first byte of the invalid count field.

Note: This sense code is not used for a BIND error because the
displacement of fields within the BIND may not be the same at both ends of
a session when the BIND was affected by name transformations--for example,
after the BIND has passed tnrough a gateway.
Sense code X ' 0835' is used
to specify a displacement for a BIND error.
0833

Invalid Parameter (with Pointer and Complemented Byte):
One or more
parameters contained in fixed- or variable-length fields of the request
are invalid or not supported by the NAU that received the request.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
nnmm

Byte 2 contains a binary value that indexes (zero-origin) the first
byte that contained an invalid parameter.
Byte 3 contains a transform of the first byte that contained an
invalid parameter:
the bits that constitute the one or more invalid
parameters are complemented, and all other bits are copied.

Note: This sense code is not used for a BIND error because the
displacement of fields within the BIND may not be the same at both ends of
a session when the BIND was affected by name transformations--for example,
after the BIND has passed through a gateway.
Sense code X ' 0835 1 is used
to specify a displacement for a BIND error.
0834

RPO Not Initiated: A power-off procedure for the specified node was not
initiated because one or more other SSCPs have contacted the node, or
because a CONTACT, DUMP, IPl, or DISCONTACT procedure is in progress for
that node.

0835

Invalid Parameter (with Pointer Only): The request contained a fixed- or
variable-length field whose contents are invalid or not supported by the
NAU that received the request.

9-16

SNA Formats

nnnn

Bytes 2 and 3 contain a two-byte binary count that indexes
(zero-origin) the first byte of the fixed- or variable-length field
having invalid contents.

Note: This sense code is not used to report an invalid value in an MS
major vector.
If the invalid value occurs in a formatted MS subvector,
sense code X'086B' 1S used.
If it occurs 1n an unformatted subvector,
sense code X'0870' 1S used.
0836

PlU/SlU Specification Mismatch: For a specified lU-lU session, both the
origin lU (OlU) and the destination LU (DlU) have only the primary
capability or have only the secondary capability.

0837

Queuing limit Exceeded: For an lU-lU session initiation request (INIT,
CDINIT, or INIT-OTHER-CD) specifying (1) Initiate or Queue (if Initiate
not possible) or (2) Queue Only, the queuing limit of either the OlU or
the DlU, or both, was exceeded.

0838

Reserved

0839

lU-lU Session Being Taken Down or lU being Deactivated.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

083A

0000

No specific code applies.

0001

During session-initiation processing, a session-termination request
has caused the LU-lU session to be taken down.

0002

RNAACType 3) received for a session during the process of session
deactivation. The RNAA should be retried.

0003

SSCP detected that this session should no longer exist and requested
its termination.
For example, a BFSESSINFO was received reporting a
subject lU address that the SSCP believed already belonged to an
other-domain resource.

lU Not Enabled: At the time an lU-lU session initiation request is
received at the SSCP, at least one of the two lUs, although having an
active session with its SSCp, is not ready to accept CINIT or BIND
requests.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

083B

0000

No specific code applies.

0001

The PlU is not enabled.

0002

The SlU is not enabled.

Invalid PCID:
the received PCID for a new session duplicated the PCID
assigned to another session, or the received PCID intended as an

Chap{er 9.

Sense Data

9-17

identifier for an existing session could not be associated with such an
existing session.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

The PCID contained in CDINIT(Initiate or Queue), INIT-OTHER-CD, or
CDTAKED duplicates a PCID received previously in one of these
requests.

083C

Domain Takedown Contention:
While waiting for a response to a CDTAKED, a
CDTAKED request is received by the SSCP containing the SSCP-SSCP primary
half-session. Contention is resolved by giving preference to the CDTAKED
sent by the primary half-session.

083D

Dequeue Retry Unsuccessful--Remo~ed from Queue: The SSCP cannot
successfully honor a CDINIT(Dequeue) request (which specifies "leave on
queue if dequeue-retry is unsuccessful") to dequeue and process a
previously queued CDINIT request (for example, because the LU in its
domain is still not available for the specified session), and removes the
queued CDINIT request from its queue.

083E

Reserved

083F

Terminate Contention: While waiting for a response to a CDTERM, a CDTERM
is received by the SSCP of the SLU. Contention is resolved by giving
preference to the CDTERM sent by the SSCP of the SLU.

0840

Procedure Invalid for Resource: The named RU is not supported in the
receiver for this type of resource (for example, (1) SETCV specifies
boundary function support for a type 1 node but the capability is not
supported by the receiving node, or (2) the PU receiving an EXECTEST or
TESTMODE is not the primary PU for the target link.)
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000 .No specific code applies.

9-18

0003

Invalid Link: The link to which the PU is to be added is not an SNA
link.
Only SNA links are supported.

0004

Invalid Link: A request that is allowed only for a nonswitched link
was received for a link that is defined to the receiver as switched.

0005

Resource Not Dynamically Added: This request works only with
resources that were added through dynamic reconfiguration.

0009

RNAA(Move) was received for a resource that was added through
dynamic reconfigurationi such a resource may not be moved through
RNAA(Move).

SNA Formats

0841

0010

A SETCV with control vector X'43' was received for a nonswitched
resource.

0011

A dynamically added or a switched resource has not yet been
activated.

Duplicate Network Address:
In an LU-LU session initiation request, one of
the specified LUs has a duplicate network address already in use.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

0842

0000

The SSCP of the DLU determines that the OLU network address
specified in the CDINIT request is a duplicate of an LU network
address assigned to a different LU name.

0001

A duplicate SLU address is found during session initiation.

0002

A duplicate PLU address is found during seSS10n initiation.

0003

An SSCP finds a duplicate network address for the DLU on the OlU
side of the gateway.

0004

An SSCP finds a duplicate network address for the DlU on the DlU
side of the gateway.

0005

An SSCP finds a duplicate network address for the OlU on the OLU
side of the gateway.

0006

An SSCP finds a duplicate network address for the OlU on the DLU
side of the gateway.

Session Not Active.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

SSCP-SSCP Session Not Active:
The SSCP-SSCP session, which is
required for the processing of a network services request, is not
active;
for example, at the time an LU-LU session initiation or
termination request is received, at least one of the following
conditions exists:

•

The SSCP of the IlU and the SSCP of the OLU do not have an
active session with each other, and therefore INIT-OTHER-CD
cannot flow.

•

The SSCP of the OLU and the SSCP of the DLU do not have an
active session with each other, and therefore CDINIT or CDTERM
cannot flow.

Note:
This value is used if there is not enough data to select one
of the more specific codes listed below.

Chapter 9.

Sense Data

9-19

0002

For a session-initiation request, an SSCP does not have an
SSCP-SSCP session with an SSCP in the direction of the DLU.

0003

For a session-initiation request, an SSCP does not have an
SSCP-SSCP session with an SSCP in the direction of the OLU.

0004

An intermediate SSCP has lost connectivity with an SSCP in the
session setup path for an LU-LU session.
This sense data is used
when the SSCP previously lost connectivity with one or more
participating gateway nodes so that it cannot learn that the LU-LU
session is ended by receiving a NOTIFY RU from a gateway node.

0843

Required Synchronization Not Supplied:
For example, a secondary LU (LU
type 2 or 3) received a request with Write Control Code = Start Print,
along with RQE and ~CD.

0844

Initiation Dequeue Contention: While waiting for a response to a
CDINIT(Dequeue), a CDINIT(Dequeue) is received by the SSCP of the SLU.
Contention is resolved by giving preference to the CDINIT(Dequeue) sent by
the SSCP of the SLU.

0845

Permission Rejected--SSCP Will Be Notified: The receiver has denied an
implicit or explicit request of the sender; when sent in response to BIND,
it implies that the secondary LU will notify the SSCP (via NOTIFY vector
key X'OC') when a BIND can be accepted, and the SSCP of the SLU supports
the notification.
(See the X'080A' sense code for a contrasting
response.)

0846

ERP Message Forthcoming: The received request was rejected for a reason
to be specified in a forthcoming request.

0847

Restart Mismatch:
Sent in response to STSN, SDT, or BIND to indicate that
the secondary half-session is trying to execute a resynchronizing restart
but has received insufficient or incorrect information.

0848

Cryptography Function Inoperative: The receiver of a request was not able
to decipher the request because of a malfunction in its cryptography
facility.

0849

Reserved

084A

Presentation Space Alteration: The presentation space was altered by the
end user while the half-duplex state was not-send, (~S,*R); request not
executed.

084B

Requested Resources Not Available:
Resources named in the request, and
required to honor it, are not currently available.
It is not known when
the resources will be made available.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

9-20

No specific code applies.

SNA Formats

084C

0001

BIND Queuing Not Supported--Retry: The SLU is not available and the
sender of the UNBIND does not support BIND queuing as requested by
the PLU.

0003

The application transaction program specified in the request is not
available.

6002

The resource identified by the destination program name (DPN) is not
supported.

6003

The resource identified by the primary resource name (PRN) is not
supported.

6031

Transaction Program Not Available--Retry Allowed:
The FMH-5 Attach
command specifies a transaction program that the receiver is unable
to start.
Either the program is not authorized to run or the
resources to run it are not available at this time.
The condition
is temporary.
The sender is responsible for subsequent retry.
This
sense data is sent only in FMH-7.

Permanent Insufficient Resource:
Receiver cannot act on the request
because resources required to honor the request are permanently
unavailable. The sender should not retry immediately because the
situation is not transient.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

For LU 6.2, Transaction Program Not Available--No Retry:
The FMH-5
Attach command specifies a transaction program that the receiver is
unable to start. The condition is not temporary.
The sender should
not retry immediately. This sense data is sent only in FMH-7.
For non-LU 6.2, no additional information is specified.

0001

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

hnnn

where h~8, 1.e., the high-order bit in byte 2 is set to 1.
The 15
low-order bits of bytes 2 and 3 contain a binary count that indexes
(zero-origin) the first byte of the field found to be in error.

084D

Retired

084E

Invalid Session Parameters--PRI: A positive r~sponse to an activation
request (for example, BIND) was received and was changed to a negative
response because of invalid session parameters carried in the response.
The LU receiving the response will send a deactivation request for the
corresponding session.

084F

Resource Not Available:
the given request.

A requested resource 1S not available to service

Chapter 9.

Sense Data

9-21

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

The receiver's disk is full;
cannot be stored.

therefore, a received load module

0850

Link-Level Operation Cannot Be Performed: An IPL, dump, or RPO cannot be
performed through the addressed link station because the system definition
or current state of the hardware configuration does not allow it.

0851

Session Busy: Another session that is needed to complete the function
being requested on this session is temporarily unavailable.

0852

Duplicate Session Activation Request:
Two session activation requests
have been received with related identifiers. The relationship of the
identifiers and the resultant action varies by request.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

If the RU is an ACTPU or ACTCDRM, it means that a session has
already been activated for the subject destination-origin pair by a
session activation request that carried a larger activation request
identifier than the current request; the current request is refused.
If the RU is a BIND, it means that the BIND request was received
with the same session instance identifier (in the structured
subfield X'03' of the User Data field) as an active session's;
the
current request is refused.

0001

A second BIND has been received from a peripheral node PLU while the
session was still in the activation process.

0853

TERMINATE(Cleanup) Required: The SSCP cannot process the termination
request, as it requires cross-domain SSCP-SSCP services that are not
available.
(The corresponding SSCP-SSCP session is not active.)
TERMINATE(Cleanup) is required.

0854

Retired

0855

Reserved

0856

SSCP-SSCP Session Lost: Carried in the Sense Data field in a NOTIFY
(Third-Party Notification vector, X'03') or -RSP(INIT_OTHER) sent to an
ILU to indicate that the activation of the LU-LU session is uncertain
because the SSCPCILU)-SSCP(OLU) session has been lost.
(Another sense
code, X'0842', is used when it is known that the LU-LU session activation
cannot be completed.)

0857

SSCP-LU Session Not Active: The SSCP-LU session, required for the
processing of a request, is not active;
for example, in processing

9-22

SNA Formats

REQECHO, the SSCP did not have an active session with the target LU named
in the REQECHO RU.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

The SSCP-SlU session is 1n the process of being reactivated.

0002

The SSCP-PlU session is inactive.

0003

The SSCP-SlU session is inactive.

0004

The SSCP-PlU session 1S in the process of being reactivated.

0858

Reserved

0859

REQECHO Data length Error: The specified length of data to be echoed (in
REQECHO) violates the maximum RU size limit for the target LU.

085A
through
085F
0860

Reserved

Function Not Supported--Continue Session:
The function requested is not
supported; the function may have been specified by a request code or some
other field, control character, or graphic character in an RU.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
nnnn

0861

Bytes 2 and 3 contain a two-byte binary count that indexes
(zero-origin) the first byte in which an error was detected.
This
sense data is used to request that the session continue, thereby
ignoring the error.

Invalid COS Name:
The class of service (COS) name, either specified by
the ILU or generated by the SSCP of the SLU from the mode table is not in
the "COS name to VR identifier list" table used by the SSCP of the PlU.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

COS name was generated by the SSCP.

0001

COS name was generated by the IlU.

0003

The CDINIT request or response contains a Session Initiation control
vector that has Class of Service (COS) Name fields that have not
been properly specified.

Chapter 9.

Sense Data

9-23

0862

Medium Presentation Space Recovery: An error has occurred on the current
presentation space.
Recovery consists of restarting at the top of the
current presentation space.
The sequence number returned is of the RU in
effect at the top of the current presentation space.
nnnn

0863

Bytes 2 and 3 following the sense code contain the byte offset from
the beginning of the RU t6 the first byte of the RU that is
displayed at the top of the current presentation space.

Referenced Local Character Set Identifier (LCrD) Not Found:
character set does not exist.

A referenced

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0864

0000

No specific code appplies.

hnnn

where h~8, i.e., the high-order bit in byte 2 is set to 1. The 15
low-order bits of bytes 2 and 3 contain a binary count that indexes
(zero-origin) the first byte of the field found to be in error.

Function Abort: The conversation was terminated abnormally.
Other
terminations may occur after repeated reexecutions; the request sender is
responsible to detect such a loop.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

For LU 6.2, Premature Conversation Termination: The conversation is
terminated abnormally; for example, the transaction program may have
issued a DEALLOCATE_ABEND verb, or the program may have terminated
(normally or abnormally) without explicitly terminating the
conversation. This sense data is sent only in FMH-7.
For non-LU 6.2, no additional information is specified.

0001

0002

System Logic Error--No Retry: A system logic error has been
detected.
No retry of the conversation should be attempted.
sense data is sent only in FMH-7.

Excessive Elapsed Time--No Retry:
Excessive time has elapsed while
waiting for a required action or event. For example, a transaction
program has failed to issue a conversation-related protocol boundary
verb.
No retry of the conversation should be attempted. This sense
data is sent in UNBIND when there is no chain to respond to;
otherwise, it is sent in FMH-7.

0865

Retired

0866

Retired

0867

Sync Event Response:
Indicates a required negative response to an
(RQE,CD) synchronizing request.

9-24

This

SNA Formats

0868

No Panels Loaded:
Referenced format not found because no panels are
loaded for the display.

0869

Panel Not Loaded:

086A

Subfield Key Invalid:
A subfield key in an MS subvector was not valid in
the conditions under which it was processed.

The referenced panel is not loaded for the display.

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
nnmm

086B

Byte 2 following the sense code contains the subvector key (nn) of
the subvector containing the unrecognized subfield, and byte 3
contains the unidentified subfield key (mm).

A value in a subfield within an MS major vector
Subfield Value Invalid:
is invalid for the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
nnmm

Byte 2 following the sense code contains the subvector key (nn) of
the subvector containing the subfield with the invalid value, and
byte 3 contains the subfield key (mm) of the subfield with the
invalid value.

Note:
See sense code X'0870' for the case in which the invalid value
occurs in an unformatted subvector, that is, one not containing subfields
with keys and lengths, or in the unformatted portion of a partially
formatted subvector.
086C

Required Subvector Missing:
One or more MS subvectors that are required
by the receiver to perform some function are missing from the received
list of subvectors, or are not present in the required position.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
nnOO

Byte 2 following the sense code contains the subvector key (nn) of
one of the subvectors that is missing, or improperly positioned.
Byte 3 is reserved (00).
Note:
See the X'080C0006' sense data for the case in which the
major vector key is recognized but a subvector representing the
function to be performed cannot be identified.

086D

Required Subfield Missing:
An MS subvector lacks one or more subfield
keys that are required by the receiver to perform the function requested.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

Chapter 9.

Sense Data

9-25

nnmm

086E

Byte 2 following the sense code contains the subvector key (nn) of
the subvector lacking a required subfield, and byte 3 contains the
subfield key (mm) of a missing subfield.

Invalid Subvector Combination: Two or more subvectors, each permissible
by itself, are present in a combination that is not allowed.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
nnmm

086F

Bytes 2 and 3 following the sense code contain the subvector keys
(nn) and (mm) of two of the subvectors that should not be jointly
present.

Length Error:
A length field within an MS major vector is invalid, or two
or more length fields are incompatible.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0870

0000

No specific code applies.

0001

The MS major vector length is incompatible with the RU length.

0002

The sum of the MS subvector lengths is incompatible with the MS
major vector length.

nn03

The sum of the subfield lengths in a MS subvector is incompatible
with the subvector length.
Byte 2 following the sense code contains
the subvector key (nn).

nn05

MS subvector length invalid.
Byte 2 following the sense code
contains the relevant subvector key (nn).
(This is specified only
if the sum of the subvector lengths is compatible with the major
vector length.)

nn06

Subfield length invalid.
Byte 2 following the sense code contains
the subvector key (nn) of the MS subvector containing the invalid
subfield length.
(This is specified only if the sum of the subfield
lengths is compatible with the subvector length.)

Unformatted Subvector Value Invalid:
A value in an unformatted MS
subvector, or in an unformatted portion of a partially formatted MS
subvector, is invalid.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
nnxx

9-26

Byte 2 following the sense code contains the subvector key (nn) of
the MS subvector containing the invalid value.
Byte 3 contains a
one-byte binary count that indexes the first byte in which the
invalid value falls.
The indexing is zero-origin, from the
beginning of the subvector.

SNA Formats

Note:
See sense code X'086B' for the case in whic-h the invalid value
occurs in a formatted MS subvector, that is, one containing subfields with
keys and lengths, or in the formatted portion of a partially formatted
subvector.
0871

Read Partition State Error: A Read Partition structured field was
received while the display was in the retry state.

0872

Orderly Deactivation Refused:
An NC_DACTVR(Orderly) request has been
received, but sessions are assigned to the VR and it will not be
deactivated.

0873

Virtual Route Not Defined:

0874

ER Not in a Valid State: The ER supporting the requested VR is not in a
state allowing VR activation.

0875

Incorrect or Undefined Explicit Route Requested:
The reverse ERNs
specified in the NC-ACTVR do not contain the ERN defined to be used for
the VR requested, or the ERN designated to be used for the VR is not
defined.

0876

Nonreversible Explicit Route Requested: The ERN used by the NC-ACTVR does
not use the same sequence of transmission groups (in reverse order) as the
ERN that should be used for the RSP(NC-ACTVR).

0877

Resource Mismatch: The receiver of a request has detected a mismatch
between two of the following:
(1) its definition of an affected resource,
(2) the actual configuration, and (3) the definition of the resource as
implied in the request.

No ERN is designated to support this VRN.

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

Link Defined as Switched Is Nonswitched:
A link defined to an
ACTLINK receiver as being switched was found to be nonswitched
during the activation attempt.

0002

Link Defined as SDLC Is Non-SDLC: A link defined to an ACTLINK
receiver as being SDLC was found to be non-SDLC during the
activation attempt.

0003

Link Defined as Having Automatic Connect-04t Capability Does Not:
A
link defined to an ACTLINK receiver as having automatic connect-out
capability was found to lack it during the activation attempt.

0004

ACTLINK Received for a Resource Other Than a Link:
An ACTLINK was
received that resolved to a local device address representing a
device other than a link.

0005

Link defined as X.21 is not X.2l.

Chapter 9.

Sense Data

9-27

9-28

0006

Link defined as LPDA-capable is configured in NRZI mode.

0007

A request that is allowed only for a primary link station was
received for a link station that is defined to the receiver as
secondary.

0008

A request for link problem determinatio~ for modems was received for
a link that is defined to the receiver as not supporting link
problem determination for modems.

0009

A request for link problem determination for modems was received for
a link that is defined to the receiver as supporting link problem
determination for modems, but no link station supporting link
problem determination for modems was found on the link.

OOOA

A request that is allowed only for a nonswitched link was received
for a link that is defined to the receiver as switched.

OOOB

A request that is allowed only for a link with a modem not using the
multiplexed links feature was received for a link that is defined to
the receiver as having a modem using the multiplexed links feature.

OOOC

Resource Definition Mismatch for Modems:
A request that is allowed
only for a link with a non-tailed modem was received for a link that
is defined to the receiver as having a tailed modem.

OOOD

The sending SSCP and the receiving T4 node have conflicting system
definitions.
A BIND has been received for an LU address that is
currently being used by an active LU-LU session. The LU address is
primary on this active session. The LU address cannot be used for a
secondary role on a new session.

OOOE

The sending SSCP and the receiving T4 node have conflicting system
definitions.
A BIND has been received for an independent LU, but
the LU specified is not in a T2.1 node.

OOOF

The sending SSCP and the receiving T4 node have conflicting system
definitions.
The SSCP owner is the same as the SSCP sending the
nonactivation CONTACT PIU, but the node to be contacted is not a
T2.1. The CONTACT is for a T2.1 node, but the node to be contacted
is not defined as a T2.1 to the receiver.

0010

The BFCLEANUP is for an independent LU, but the LU specified
an independent LU.

0011

The subarea address portion of an addressed lU is not equal to the
subarea address of the T4 node. The LU is not in the same subarea
as the T4 node.

0012

A BFCLEANUP is for a resource that is not a BF LU, and hence the
request is rejected.
This is a situation where the function is not
supported by the target resource.
It can be caused by a system
definition mismatch between the T4 node and the SSCP.

SNA Formats

1S

not

0013

The network ID in the BIND SLU name is not equal to the network ID
of the boundary function, or the SLU name is not equal to the LU
name in the boundary function control block for the LU.

0014

The LU specified in the FNA is not associated with the PU specified
in the FNA; that is, an LU address (byte 7-n) is not associated with
the PU target address specified.

0015

BFCINIT Name Mismatch: The BIND cannot be built from the BFCINIT
because the network-qualified PLU name does not match.
The session
activation is rejected by the boundary function with a BFTERM.

0016

Invalid Target Address:

Either of the following conditions holds:

•

The PU with which the specified LUs are to be associated is not
type I or type 2; i.e., the SSCP attempts to add an LU to a PU,
but the boundary function has defined that PU as a type 4.

•

The SSCP sent an RNAA assignment type X'O' or X'S' with a PU or
LU specified instead of a link.
This is caused by a system
definition mismatch.

0017

An entire network address including subarea and element is required
for Pre-ENA address assignment:
If an entire network address 1S
not specified and an RNAA requesting a pre-ENA address is
received, the RNAA is rejected.

0018

An RNAA type 4 was received requesting an auxiliary address on a
dependent LU.

OOlA

The target LU specified in BFCLEANUP or BFCINIT is not associated
with the same link station that is associated with the session
indicated in the URC control vector.

OOlB

The target link station specified in a BFCLEANUP 1S not the same
link station as the session indicated in the URC control vector.

OOIC

Resource Definition Mismatch for BFCINIT: The sending SSCP and the
receiving T4 node have conflicting system definition.
A BFCINIT has
been received for an LU address that is currently being used by an
active LU-LU session. The LU address is primary on this already
active session. The LU address cannot be used for a secondary role
on a new session.

OOlD

The LU address 1n a BFCINIT is a secondary address; the BFCINIT is
rejected.

OOIE

The subject LU specified in a BFSESSINFO RU is not defined to the
SSCP as an independent LUj this is a mismatch between the SSCP and
the BF.

OOIF

A dependent LU is attached to a PU that indicates ACTPU is to be
suppressed; the SSCP cannot activate the LU because ACTLU is not
supported.

Chapter 9.

Sense Data

9-29

9-30

0020

A peripheral node supporting independent LUs has received an ACTLU
request for an LU. This request is rejected, as an independent LU
does not support ACTLU.

0021

An RNAA(Add) was received by a boundary function for a resource
defined at system definition time, which is not allowed.

0025

The receiving node is unable to process a BIND for the LU type
specified for the given LU name.

0028

An RNAA(Move) was received for a link station, and the link
station's primary-secondary role is incompatible with the target
link.
on the target link are defined with a different link station
role (primary or secondary) than those of the source.

0029

The RU refers to a resource, and the sender and receiver disagree
about its status.
One considers it a static resource, the other a
dynamic resource.

002C

BFSESSINFO received reporting a subject LU in another network.

002D

BFSESSINFO received for an (independent) subject LU, but the
reported LU is considered by the receiver as a dependent LU.

002E

BFSESSINFO received reporting a dynamic subject LU that the receiver
considers to be located under a different ALS than that reported in
the BFSESSINFO.
The SSCP will attempt to correct this configuration
mismatch.

002F

BFSESSINFO received reporting a subject LU that the receiver
considers to be located under a different ALS than that reported in
the BFSESSINFO.
The SSCP cannot correct this configuration
mismatch.

0030

BFSESSINFO received for a subject LU, but the receiver has the
address associated with a different LU, which it considers to be
static.

0031

BFSESSINFO received for a subject LU, but the receiver has the
address associated with anything other than a static LU or an
other-domain resourc

0032

BFSESSINFO received for an LU. The subject LU is verified, but, for
a given session, either the partner LU is reported as the primary
and the receiver does not consider that LU to be primary capable, or
the partner LU is reported as the secondary and the receiver does
not consider that LU to be secondary capable.

0033

Upon receipt of BFSESSINFO, the receiver considers the control block
associated with a partner LU to be for an other-domain resource that
is not active or an application program that is not active.

SNA Formats

0878

0034

An SSCP is unable to associate the information received in a
BFSESSINFO with an LU, an other-domain resource, or an application
program.

0035

A network address was returned in RSP(RNAA) that the receiver
believes is already associated with a different resource.

0036

BFSESSINFO received containing an invalid ALS address.
the ALS does not represent a T2.1 node.

0037

BFSESSINFO received for a subject LU, where the secondary address
specified in the BFSESSINFO does not match the secondary address the
SSCP believes is associated with the LU.

0038

The subject LU specified in the BFSESSINFO RU is not defined to the
SSCP as an LU or an other-domain resource.

0039

A request that is valid only for a switched subarea link was
received for a link that is not subarea capable.

003A

A request that is valid only for a nonswitched subarea link was
received for a subarea dial link.

003B

An RNAA(Add) was received for an LU; however, an LU with the same
name but a different local address already exists under the
specified ALS.

0041

Takeover processing completed, but the SSCP did not receive a
BFSESSINFO for a resource that the SSCP believed to be a static,
independent LU.

For example,

Insufficient Storage: The storage resource required for a data format
not available.

1S

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0879

0000

No specific code applies.

0001

CONNOUT contained more dial digits than can be stored by the
receiving product.

Storage Medium Error: A permanent error has occurred involving a storage
medium.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

087A

0000

No specific code applies.

0001

Disk I/O error.

Format Processing Error:
formatting.

A processing error occurred during data

Chapter 9.

Sense Data

9-31

087B

Resource Unknown:
The request contains a session key that does not
identify a session known to some gateway node; for example, a session
activation request arrives at a gateway node after it has released the
address transform for the intended session.

087C

SSCP-PU Session Not Active:
A gateway SSCP-PU session that is needed to
establish an address transform for the intended cross-network LU-LU
session was not active.

087D

Session Services Path Error:
A seSS10n services request cannot be
rerouted along a path of SSCP-SSCP sessions. This capability is required,
for example, to set up a cross-network LU-LU session.
Bytes 2 and 3 contain sense code specific information that indicates the
specific reason for not rerouting the request.
Settings allowed are:
0000

No specific code applies.

0001

An SSCP has attempted unsuccessfully to reroute a session services
request to its destination via one or more adjacent SSCPs; this
value is sent by a gateway SSCP when it has exhausted
trial-and-error rerouting.
Note:
This code is used when SSCP rerouting fails completely.
Th
codes are used for failures to reroute to a particular SSCP.
For
example, they are associated with specific SSCPs when information
about a rerouting failure is displayed in the node that was trying
to reroute.

9-32

0002

An SSCP is unable to reroute a session services request because a
necessary routing table is not available; that is, no adjacent SSCP
table corresponds to the rerouting key in the Resource Identifier
control vector.
The receiver of this value will, if possible, try
rerouting to another SSCP.

0003

This SSCP has no predefinition for an LU, but an adjacent SSCP does
not support dynamic definition in partner SSCPs.
As a result, this
SSCP cannot both dynamically define the LU and reroute to that
adjacent SSCP.

0005

Retired

0006

Retired

0008

The adjacent SSCP does not support the requested CDINIT function
(for example, notification of resource availability or XRF).

OOOA

An SSCP is unable to reroute a session services request because the
request has been routed through the same SSCP twice.

OOOB

The DLU specified in the CDINIT is unknown to the receiving SSCP,
and the receiving SSCP cannot reroute the CDINIT.

SNA Formats

087E

SSCP Visit Count Exceeds Limit: The SSCP visit count specified in the
session services request--CDINIT, INIT_OTHER_CD, or DSRLST--has been
decremented to O. The session services request has been routed through an
excessive number of SSCPs.
(The SSCPs are not necessarily distinct.)

087F

Reserved

0880

Reserved

0881

ACTCDRM Failure--REQACTCDRM Sent: An SSCP-SSCP session-activation
request, ACTCDRM, cannot be rerouted to a gateway SSCP because, at some
gateway PU, the necessary transform is not complete and the gateway PU has
sent REQACTCDRM to the gateway SSCP.

0882

Reserved

0883

Reserved

0884

ACTCDRM Failure--No REQACTCDRM Sent: An SSCP-SSCP session activation
request, ACTCDRM, cannot be rerouted to the destination SSCP because, at
some gateway node PU, the necessary transform is not complete and
REQACTCDRM cannot be sent to the destination SSCP because the gateway
SSCP-PU session is not active or the intended SSCP session partner does
not provide gateway services.

0885

Reserved

0886

Subnetwork Rerouting Not Supported: An SSCP received a session serV1ces
request--CDINIT, INIT_OTHER_CD, NOTIFY(Vector Key=X'Ol'), or DSRLST--from
an SSCP in its subnetwork that, if rerouted, would not cross a subnetwork
boundary. The SSCP does not support rerouting within a subnetwork.

0887

Dequeue Retry Unsuccessful--Session Remains Queued: The SSCP cannot
successfully honor a CDINIT(Dequeue) request.
The request specifies
"leave on queue if dequeue-retry is unsuccessful." The SSCP has left the
queued session on its queue.

0888

Name Conflict: A name specified in an RU is unknown, or is known and
does not have the required capabilities,
or is a duplicate resource
for the specified resource type. When a name conflict is detected,
further name checking ceases; multiple name conflicts are not reported or
detected.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

The specified DLU real network name is known, but identifies a
resource that is not LU-LU session capable.

0002

The specified DLU alias network name is known, but identifies a
resource that is not LU-LU session capable.

Chapter 9.

Sense Data

9-33

0889

0003

The specified OlU real network name is known, but identifies a
resource that is not lU-lU session capable.

0004

The specified OlU alias network name is known, but identifies a
resource that 1S not lU-lU session capable.

0005

Name translation was invalid; that is, a different lU name was
returned with the same network ID as the original lU name.

0006

The specified DlU real network name
resource.

0007

The specified DlU alias network name is known, but is a duplicate
resource.

0008

The specified OlU real network name
resource.

0009

The specified OlU alias network name
resource.

OOOB

A cross-network DlU name is defined as a shadow resource, but shadow
resources are not supported for cross-network sessions.

OOOC

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

OOOD

When processing a session initiation RU, an SSCP has found two
different resource definitions for the OlU, one with the real OlU
name and one with the alias OlU name.

OOOE

When processing a session initiation RU, an SSCP has found two
different resource definitions for the DlU, one with the real DlU
name and one with the alias DlU name.

Transaction Program Error:

1S

1S

1S

known, but is a duplicate

known, but is a duplicate

known, but is a duplicate

The transaction program has detected an error.

This sense code is sent only in FMH-7.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

Program Error--No Data Truncation: The transaction program sending
data detected an error but did not truncate a logical record.
Program Error--Purging: The transaction program receiving data
detected an error. All remaining information, if any, that the
receiving program had not yet received, and that the sending program
had sent prior to being notified of the error, is discarded.

0001

9-34

Program Error--Data Truncation:
The transaction program sending
data detected an error and truncated the logical record it was
sending.

SNA Formats

0100

Service Transaction Program Error--No Data Truncation:
The service
transaction program sending data detected an error and did not
truncate a logical record.
Service Transaction Program Error--Purging: The service transaction
program receiving data detected an error. All remaining
information, if any, that the receiving service transaction program
had not yet received, and that the sending service transaction
program had sent prior to being notified of the error, is discarded.

0101

088A

Service Transaction Program Error--Data Truncation: The service
transaction program sending data detected an error and truncated the
logical record it was sending.

Resource Unavailable--NOTIFY Forthcoming: The SSCP cannot satisfy the
request because a required resource is temporarily unavailable.
When the
required resource becomes available, NOTIFY NS(s) key X'07' or X'08' will
be sent.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

SSCP-SSCP Session Not Active: A SSCP-SSCP session required to
reroute the cross-network request was not active.

0003

SSCP-LU session not active:
session with the DLU.

0004

LU session limit exceeded: The DLU is currently at its session
limit and the requested session would cause the limit to be
exceeded.

The SSCP(DLU) is currently not in

088B

BB Not Accepted--BIS Reply Requested: Sent in response to a BB (either an
LUSTAT bid or an Attach) to indicate that the receiver has sent a BIS
request and wishes to terminate the session without processing any more
conversations, but without sending an UNBIND. A BIS reply is requested so
that the negative response sender may send a normal UNBIND. This sense
code is sent only by LUs not supporting change-number-of-session
protocols.

088C

Missing Control Vector:
expected to appear.

The RU did not contain a control vector that was

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
nnOO

A required control vector is missing.
Byte 2 contains the key (nn)
of the required control vector that is missing.
If more than one
control vector is missing, only the first omission is reported.
The
second byte of the sense code specific field is set to X'OO'.

Chapter 9.

Sense Data

9-35

088D

Duplicate Network Name:
An SSCP has detected a violation of the
requirement that network names used across multiple domains be unique
within the multiple-domain network. For examplel the SSCpeDLU) has
detected that the OLU name received in CDINIT is currently also defined in
the domain of the SSCpeDLU).

088E

ENA Address Mismatch: An SSCP detected that an ENA LU has an address too
large for one of the pre-ENA components CLU or SSCP) involved in the
session to support.
Bytes 2 and 3 following the sense code contains sense code specific
information.
Settings allowed are:

088F

0000

A resource encountered during LU-LU session initiation is not
ENA-capable; the session initiation request may be rerouted.

0001

A resource encountered during LU-LU session initiation is not
ENA-capable; the session initiation request should not be rerouted.

0002

An SSCP has requested a "pre-ENA compatible" SLU address for an SLU
that already has an ENA address.

0003

The gateway node selected by the gateway SSCP from the gateway node
list is not ENA-capable when an ENA-capable gateway node is
required. Another gateway node may be tried.

XRF Procedure Error: A request was received for an XRF-active or
XRF-backup session and was not acted on.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

9-36

0000

No specific code applies.

0003

A SWITCH request specifying a switch to the already existing state
was received.

0004

A SWITCH request was received that was invalid.

0005

The SLU has received SWITCHCConditional l to backup) and no current
XRF-backup sessions exist that can replace this session (that iS I
become the XRF-active.)

0006

An INITIATE request for an XRF-backup session was received that
allowed queuing eXRF-backup and session queuing are mutually
exclusive functions.)

0007

A CDINIT or INITIATE request was received specifying an XRF-backup
session, and the DLU does not support XRF sessions.

0008

An XRF-active BIND was received with a session correlation
identifier that duplicates a session correlation identifier
associated with an existing XRF session.

SNA Formats

0009

An XRF-backup BIND was received for an lU that currently does not
have an XRF session.

OOOA

Cryptography Not Supported:
cryptography.

OOOB

An INITIATE request was received specifying an XRF-backup session,
and the OlU does not support XRF sessions.
This is a system
definition mismatch between the OlU and the SSCP(OLU).

OOOF

Invalid backup command.

0010

An XRF-backup BIND was received with a session correlation
identifier that does not match the session correlation identifier
associated with the existing XRF session with that LU.

0890

Reserved

0891

Invalid Network 10 (NETID)

An XRF BIND was received indicating

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

0892

0000

No specific code applies.

0001

PLU NETID Invalid:
the SSCP(PLU).

0002

Invalid NETID:
The NETID field in CONNOUT does not match the NETID
defined in the link station receiving the CONNOUT.

0003

Invalid NETID:
The NETID field in the RNAA is not the same as the
native NETID.
There is a mismatch between the system definitions of
the SSCP and the type 4 node.

The NETID of the PLU

1S

not the same as that of

Automatic network shutdown (ANS) has occurred.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

Session Reset After Loss of an SSCP:
The SSCP controlling an LU has
been lost.
The session will be terminated because the T4 node, by
system definition, terminates such sessions for this LU upon loss of
the SSCP.

0002

The LU-LU session was in pending-active state when the SSCP failed.
Although the T4 node, by system definition, continues an active
LU-LU session upon loss of the SSCP, the session was not completely
set up, and thus it was reset.

Chapter 9.

Sense Data

9-37

0003

0893

XRF-backup Session Reset. The XRF-backup session was reset because
the T4 node resets the session upon loss of the SSCP.

Takeover Not Complete
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0894

0895

0000

No specific code applies.

0001

PlU lacking an SSCP--Retry: The PlU is not currently receiving
network services from a control point. The BIND is rejected because
the session cannot be established. This sense data is returned by
the boundary function of the PlU.

0002

SlU lacking an SSCP--Retry: The SlU is not currently receiving
network services from a control point. The BIND is rejected because
the session cannot be established. This sense data is returned by
the boundary function of the SlU.

0003

Sequence Error: The SSCP should not send an RNAA for an independent
lU until the takeover sequence is complete for the link station,
that is, until all BFSESSINFOs for that lU have been received and
accepted.

Migration Support Error: The sender of the request is relying on
migration support that is not available.
Bytes 2 and 3 may contain the
following sense code specific information:
0000

No specific code applies.

0001

BIND cannot be extended: A BIND that is not an lU6.2 BIND was
received and cannot be extended by the receiver.

Control Vector Error:
error.
xxyy

0896

0897

9-38

The RU contained a control vector that was in

The first byte (xx) of the sense code specific data contains the hex
key of the control vector first detected in error.
If more than one
control vector is in error, only the first erroneous one is
reported. The second byte (yy) of the sense code specific data
contains the (zero-origin) byte offset of the error within the
control vector.

Control Vector Too long.
0000

No specific code applies.

0001

Network Name (X'OE') control vector is too long; the vector data
portion is greater than 18 bytes long.

System Definition Mismatch: The requested function is not supported by
the receiver, or there is a mismatch between the sending and receiving
system definitions.

SNA Formats

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0898

0000

No specific code applies.

0001

The BFCLEANUP specifies that it is for an independent LU, but the LU
specified is not an independent LU. This also could be caused by a
resource mismatch.

0002

The target LU is not in the same subarea as the type 4 node.

0003

The function is not supported by the target resource.

0004

Invalid SLU Name: The network ID (if present) in the SLU Name
field, is not equal to the network ID of the type 4 node, or the SLU
name is not equal to the LU name contained in the T4 node system
definition.

0005

The LU address specified in the FNA is not associated with the PU
target address specified in the FNA.

0006

The SSCP has no predefinition for an LU and does not support dynamic
resource definition.

0007

The receiving SSCP has a system-defined name for the SSCPCDLU) that
differs from the SSCPCDLU) name in the session initiation request.

0008

In a gateway with three gateway SSCPs, a gateway SSCP on the OLU
side of the gateway was specified as having predesignated control 1n
the CDINIT.
In this configuration, only the middle gateway SSCP may
have predesignated control.

0009

In a gateway with three gateway SSCPs, none of which is
predesignated, the gateway node believes that one is predesignated.
As a result, the gateway node receives gateway control RUs such as
RNAA from an unexpected SSCP.

OOOA

The PU of an independent PLU named in BFINIT does not have the same
element address as the one in the ALS field of BFINIT.

OOOB

An SSCP has detected a specification of gateway responsibility in
the CDINIT request that is not consistent with its own
definition.
For example,
two gateway SSCPs in the same gateway
are both predefined to be predesignated.

OOOC

The receiver is unable to interpret the DLU name.

0010

An adjacent SSCP has the same SSCP name as the SSCP that controls
the DLU, but a different network identifier from the DLU.

Session Reset:

The XRF session is being reset.

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

Chapter 9.

Sense Data

9-39

0899

0000

No specific code applies.

0001

The XRF-active session has been reset because the XRF-backup PLU
forced a takeover.

0002

XRF-backup Hierarchical Reset: The identified XRF-backup LU-LU
session is being deactivated because the related XRF-active session
terminated normally. The LU sending this sense data is resetting
its half-session before receiving the response from the partner LU.
(See UNBIND type X'12'.)

0003

XRF-active Hierarchical Reset: The identified XRF-active LU-LU
session is being deactivated because the related XRF-backup session
performed a forced takeover of this session (via SWITCH).
The LU
sending this sense data is resetting its half-session before
receiving the response from the partner LU.
(See UNBIND type
X'13' .)

Invalid Address:
An address modifying a control function
outside the range allowed by the receiver.

1S

invalid, or

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

089A

0000

No specific code applies.

0002

If the address requested in the RNAA is an existing address and an
FNA has been received for this address, reject the RNAA.

Invalid File or File Not Found:
found to be an invalid file.

The requested file was not found, or was

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

089B

0000

No specific code applies.

0001

Requested file not found.

0002

The specified load module already exists and, therefore, cannot be
added.

Session Correlation Exception: The session correlation procedure detected
an exceptional condition at the SLU.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

9-40

0000

No specific code applies.

0001

RUs Out of Order:
A BIND request with the correlating
fully-qualified PCID control vector (X'SF') arrived before
UNBIND(Type X'02') was received for the correlated session.

SNA Formats

This

sense data is sent in an UNBIND that terminates the correlated
session.
0002

Correlator Not Found: A BIND request with the correlating
fully-qualified control vector (X'5F') cannot be correlated to any
previous session.

089C

Reserved

089D

Gateway Node Error Detected during Cross-Network Session Initiation.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

08AO

0000

No specific code applies.

0001

The gateway node list used to select a gateway node to cross a
network boundary is exhausted.

0003

RNAA has failed;

0004

Address conversion based on the subarea/element address split was
unsuccessful.

0005

The gateway node selected by one gateway SSCP is not known to
another gateway SSCP in the same gateway.
This can be a system
definition error in the gateway SSCP that does not recognize the
gateway node.

0006

A gateway SSCP has found that a gateway node has assigned duplicate
addresses.

Session Reset:

another gateway node should be tried.

An LU or PU

1S

resetting an LU-LU session.

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

08A2

0000

No specific code applies.

0001

The LU is sending an UNBIND with a reason code of X'OA' (SSCP gone);
the identified LU-LU session had to be deactivated because of a
forced deactivation of the associated SSCP-PU or SSCP-LU session,
for example, because of a DACTPU, DACTLU, or DISCONTACT.

0003

The gateway node is sending UNBIND with a reason code of X'll'
(gateway node cleanup); a gateway node is cleaning up the session
because a gateway SSCP has directed the gateway node (via NOTIFY) to
deactivate the session, for example, a session setup error or
session takedown failure had occurred.

Resource Active. The requested function must be performed on an inactive
resource, and the resoUrce is active.

Chapter 9.

Sense Data

9-41

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

RNAA(MOVE) was received for an active resource.

REQUEST ERROR (CATEGORY CODE

= X'lO']

This category indicates that the RU was delivered to the intended NAU component, but
could not be interpreted or processed. This condition represents a mismatch of NAU
capabilities.
Category and modifier (in hexadecimal):
1001

RU Data Error:
Data in the request RU is not acceptable to the receiving
component; for example, a character code is not in the set supported, a
formatted data field is not acceptable to presentation services, or a
value specified in the length field (ll) of a structured field is invalid.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

9-42

0000

No specific code applies.

0001

The request contains a subarea address of a or a subarea address
greater than the maximum subarea value within the specified or
implied network.

0002

The network ID specified in the ACTPU is unknown, or is not valid on
the link over which the ACTPU was received.

0003

Isolated Pacing Message (IPM) Format Error:
formatted IPM was received.

0005

An RNA A type 4 was received, in which the local address field length
is greater than 1. The implementation does not support a length
other than 1.

0006

An RNAA type 4 was received, in which the link station address field
length is greater than 1. The implementation does not support a
length other than 1.

0007

On BFCINIT, the network name portion of the network qualified name
field has a format error.

0008

An invalid character code was found.

0009

The formatted data field is unacceptable to presentation services.

OOOA

An invalid length field for a structured field was found.

SNA Formats

An incorrectly

OOOB

The value 1n the name length field is too great.

OOOC

The value 1n the cryptography key length field is too great.

0000

The URC field length is invalid.

OOOE

The control vector length field is inconsistent with the control
vector data.

OOOF

A PLU or SLU role specification encoding is invalid.

0020

Too many session keys are present.

0021

A control vector or session key data is invalid.

0022

A BIND image in a session services RU is invalid.

0023

A device characteristics field is invalid.

hnnn

where h~8, i.e., the high-order bit in byte 2 is set to 1. The 15
low-order bits of bytes 2 and 3 contain a binary count that indexes
(zero-origin) the first byte of the field found to be in error.

1002

RU Length Error: The request RU was too long or too short.

1003

Function Not Supported: The function requested is not supported.
The
function may have been specified by a formatted request code, a field in
an RU, or a control character.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

0001

The half-session receiving the request did not perform the function
because it is not capable of doing so.
The requesting half-session
requested a function that the receiver does not support and the
receiver did not specify that it was capable of supporting the
function at session activation; consequently, there is an apparent
mismatch of half-session capabilities.
Note:
This is to cover a system error.
For example, if the PU
receiving a SETCV(Vector Key=X'lS') is not a gateway PU--that is,
the PU did not indicate in the ACTPU response that it is a gateway
PU--the PU reports to the SSCP that sent the SETCV that there is an
apparent mismatch of half-session capabilities.

0002

The half-session receiving the request did not perform the function,
though it is capable of doing so.
The requesting half-session did
not specify at session activation that it was capable of supporting
the function; consequently, there is an apparent mismatch of
half-session capabilities.

Chapter 9.

Sense Data

9-43

Note: This is to cover a system error.
For example, if the SSCP
sending a SETCV(Vector Key=X'15') is not known to the receiving PU
as a gateway SSCP, that is, the SSCP did not indicate in ACTPU that
it is a gateway SSCP, the PU reports a mismatch of capabilities.
Note:
0001 and 0002 are also assigned for implementation-specific
use; see implementation documentation for details of usage.

9-44

0003

The component received an unsupported normal-flow DFC command.

0004

The component received an unsupported expedited-flow DFC command.

0005

The component received a network control command during an LU-SSCP
session.

0006

The component received an unsupported session control command during
an LU-SSCP session.

0007

The component received an unsupported data flow control command with
LU-SSCP session specified.

OOOB

A BIND specifying delayed request mode was received from a non-6.2
type LU, but delayed request mode is not supported in the receiver.

OOOC

A stand-alone BIND is received from a node that 1S served by an SSCP
that does not support stand-alone BINDs.

OOOD

The function identified in the request is not supported by the
processing application transaction program.

0010

The RU is not known to session services.

0011

A session key 1S not supported.

0012

A control vector is not supported.

0014

Cryptography is not supported but a nonzero length was specified for
the cryptography key.

0015

Queuing not supported for this seSS10n request.

0020

A session initiation request specified an OLU and DLU that are the
same LU. An LU cannot establish a session with itself.

0021

There is a mismatch between session initiation request type and lU
type (independent or dependent).
For example, a session initiation
request other than BFINIT identifies an independent LU as a
seSS10n partner.

6002

The resource identified by the destination program name (DPN) is not
supported.

6003

The resource identified by the primary resource name (PRN) 1S not
supported.

SNA Formats

Note:
This sense code can also be used instead of sense code
X'0826' .
1004

Reserved

1005

Parameter Error:
A parameter modifying a control function
outside the range allowed by the receiver.

1S

invalid, or

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

For NMVT, the address type field in an SNA Address List subvector
does not match the address type required by the command subvector.

0002

Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of
usage.

0004

Invalid display type was requested.

0005

Invalid storage length for display type requested.

0006

Invalid storage address; out of specified range.

0008 and 0121-0229 Set aside for implementation-specific use, and will not
be otherwise defined in SNA; see implementation documentation for
details of usage.
1006

Required Field or Parameter Is Missing.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

One or more required COS names were omitted.

0002

A required name was omitted.

0003

A required network identifier was omitted.

0004

A required session key was omitted.

0005

A required control vector was omitted.

0006

A required subfield of a control vector was omitted.

0007

The TG number field was omitted.

0008

The system-defined ID number, used within the Node Identification
field of an XID, was omitted.

Chapter 9.

Sense Data

9-45

1007

Category Not Supported: DFC, SC, NC, or FMD request was received by a
half-session not supporting any requests in that category; or an NS
request byte 0 was not set to a defined value, or byte 1 was not set to an
NS category supported by the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

1008

0000

No specific code applies.

0001

Invalid NS header received.
defined value.

An NS request byte 0 was not set to a

Invalid FM Header: The FM header was not understood or translatable by
the receiver, or an FM header was expected but not present.
For LU 6.2,
this sense code is sent in FMH-7 or UNBIND.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Figure 9-2 on page 9-52 shows the usage of the allowed
values by LU type. Settings allowed are:

9-46

0000

No specific code applies.

0801

The function code parameters are invalid.

0803

The forms functions cannot be performed.

0805

The copy function cannot be performed.

0806

Compaction table outside the supported set: The number of
master characters is not within the valid range.

0807

The PDIR (peripheral data information record) identifier is
invalid.

0808

The printer train function cannot be performed.

0809

The FCB (forms control block) load function cannot be
performed.

080A

The FCB (forms control block) load function

080B

The compaction table name is invalid.

080C

The ACCESS is invalid.

0800

The RECLEN

080E

The NUMRECS is invalid.

080F

The data set is in use.

0810

The data set cannot be found.

SNA Formats

1S

invalid.

1S

not supported.

0811

The password is invalid.

0812

The function
data set.

0813

The record

0814

The data set is full.

0815

The RECID is invalid.

0816

Reserved

0817

The VOLID format is invalid.

0818

The maximum number of logical records per chain

0819

The data set exists.

081A

No space is available.

081B

The VOLID is invalid.

081C

The DSACCESS is invalid.

081D

The RECTYPE is invalid or the dataset cannot be found.

081E

The resolution space is insufficient.

081F

The key technique is invalid.

0820

The key displacement is invalid.

0821

The key is invalid.

0822

There is an Invalid N (number of records.)

0823

The KEYIND is invalid.

0824

The SERID is invalid.

0825

Disk Error:
An error was detected while reading from, or
writing on, the disk.

0826

The RECID format is invalid.

0827

The password has not been supplied.

0828

The record ID has not been supplied.

0829

The Volume ID has not been supplied.

082A

The PGMNAME is invalid.

1S

1S

not allowed for the destination or for the

too long.

Chapter 9.

1S

exceeded.

Sense Data

9-47

9-48

1204

Set aside for implementation-specific uSe, and will not be
otherWise defined in SNAi see implementation documentation
for details of usage.

2001

The destination (active) is invalid.

2002

The destination (inactive) is invalid.

2003

The destination (suspended) is invalid.

2004

The suspend-resume sequence is invalid.

2005

There has been an interruption level violation.

2006

The resume properties are invalid.

2007

The destination is not available.

2008

The end sequence is invalid.

2009

The FM header length is invalid.

200A

Invalid field setting: The reserved field is set to 1 or the
setting is not defined.

200B

Invalid destination:

200C

The ERCL is invalid.

200D

The DST is invalid.

200E

Invalid Concatenation Indicator:
The concatenation indicator
1S on, but concatenation is not allowed.

200F

FM data 1S not allowed for the header.

2010

The FM header set specified 1n the BIND has been violated.

2011-2013

Reserved

2014

The FM header was not sent concatenated.

2015-2018

Reserved

2019

The stack reference indicator (SRI) is invalid.

201A

The CMI modification could not be accepted.

201B

The CPI modification could not be accepted.

201C

The ECRL modification could not be accepted.

201D

FM Header and Associated Data Mismatch:
The FM header
indicated associated data would or would not follow (for

$NA Formats

The destination does not exist.

example, FM header 7 followed by log data, or FM header 5
followed by program initialization parameters), but this
indication was in error; or a previously received RU (for
example, -RSP(X'0846')) implied that an FM header would
follow, but none was received.
4001

Invalid FM Header Type for this lU:
is other than 5, 7, or 12.

The type of the FM header

4002

The FMH code is invalid.

4003

Compression is not supported.

4004

Compaction is not supported.

4005

Basic exchange is not supported.

4006

Only basic exchange is supported.

4007

The medium is not supported.

4008

There has been a code selection compression violation.

4009

FMHC is not supported.

400A

Demand select is not supported.

400B

DSNAME is not supported.

400C

The media subaddress field is invalid.

400D

There are insufficient resources to perform the requested
function.

400E

DSP select 1S not supported.

6000

FM Header l~ngth Not Correct: The value in the FM header
length field differs from the sum of the lengths of the
subfields of the FM header.

6001

The deblocking algorithm (DBA) is invalid.

6004

The queue name length is invalid.

6005

Access Security Information length Field Not Correct:
The
value in the Access Security Information Length field differs
from the sum of the lengths of the Access Security -Information
subfields.

6006

Th~

6007

The FMH-7 is not preceded by a negative response carrY1ng the
X'0846' sense code.

data stream profile (PSP) is invalid.

Chapter 9.

Sense Data

9-49

9-50

6008

The Attach access code is invalid.

6009

Invalid Parameter Length: The field that specifies the length
of fixed-length parameters has an invalid setting.

600A

This is not the first FMH-5, the interchange unit type is not
the same as the old, and the interchange unit end indicator is
off.

600B

Unrecogized FM Header Command Code:
The partner LU received
an FM header command code that it does not recognize.
For LU
6.2 this sense data is sent only in FMH-7.

600C

A null sequence field is required.

600D

User to user program transition is not allowed.

600E

User to non-SNA defined program transition is not allowed.

600F

The FMH-5 reset attached program (RAP) was not sent properly.

6010

The FMH-5 reset attached program (RAP) was sent with an
inactive Attach register.

6011

Invalid Logical Unit of Work (LUW):
The LUW Length field (in
a Compare States GDS variable or an FMH-5) is incorrect, or
the length field is invalid, or a LUW ID is not present but is
required by the setting of the synchronization level field.

6021

Transaction Program Name Not Recognized:
The FMH-5 Attach
command specifies a transaction program name that the receiver
does not recognize. This sense data is sent only in FMH-7.

6031

PIP Not Allowed: The FMH-5 Attach command specifies program
initialization parameter (PIP) data is present, but the
receiver does not support PIP data for the specified
transaction program. This sense data is sent only in FMH-7.

6032

PIP Not Specified Correctly: The FMH-5 Attach command
specifies a transaction program name that requires program
initialization parameter (PIP) data, and either the FMH-5
specifies PIP data is not present or the number of PIP
subfields present does not agree with the number required for
the program. This sense data is sent only in FMH-7.

6034

Conversation Type Mismatch:
The FMH-5 Attach command
specifies a conversation type that the receiver does not
support for the specified transaction program. This sense
data is sent only in FMH-7.

6040

Invalid Attach Parameter: A parameter in the FMH-5 Attach
command conflicts with the statement of LU capability
previously provided in the BIND negotiation.

SNA Formats

6041

Synchronization Level Not Supported:
The FMH-5 Attach command
specifies a synchronization level that the receiver does not
support for the specified transaction program.
This sense
data is sent only in FMH-7.

COOO

The header is not supported.

COOl

The header length is invalid.

C002

There has been a logical message services block-level error.

C003

There

~s

a version ID mismatch.

Chapter 9.

Sense Data

9-51

Range

LU 1

LU 4

0801-0824

X

0825

X

0826-082A

X

X

200l-200D

X

X

200E

X

X

200F-20lC

X

X

LU 6.1

X

X

20lD

X

4001-400E

X

X

6000

X

6001,6004

X

6005

X

6006-6008

X

6009

X

600A

X

600B

X

600C-60l0

X

6011-6034
6040

X

X

X

X
X

6041

X
X

COOO-C003

Figure 9-2.

LU 6.2

X

Usage of X'1008' Sense Code Specific Information by LU Type

1009

Format Group Not Selected:
No format group was selected before issuing a
Present Absolute or Present Relative Format structured field to a display.

1011

RNAA Request Error: The RNAA is rejected because there is a mismatch
between the sending and receiving nodes' system definitions, or
capabilities.

9-52

SNA Formats

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

No Available Pre-ENA Addresses: An RNAA that requests an address
that is pre-ENA compatible is rejected, as no pre-ENA addresses are
available.

0002

RNAA Takeover Error:
In a takeover situation, a system definition
mismatch was detected between the SSCP currently controlling a
resource and the SSCP taking over.
For example, an RNAA will be
rejected if the LU name in the RNAA is not the same as the LU name
contained in the T4 node system definition; or an exist~ng LU with
the same local address is found, but the LU is system-defined (not
dynamically added); or if the adjacent link station name given in
the RNAA does not match the link station name provided in the T4
system definition.

0003

Invalid Network ID:
If the network ID field in the RNAA 1S not the
same as the native network ID of the receiving node, the RNAA is
rejected.

0004

Invalid PU or LU Type: The RNAA is rejected if the PU to which the
LUs are to be added is not type 1 or type 2, but instead was defined
at the receiving PU as a type 4, or if the type of request is
appropriate for a link station, but the resource specified in the
request is a PU or an LU.

0005

Pre-ENA Address Cannot Be Assigned:
An RNAA requesting a pre-ENA
address assignment has been received and rejected because the system
definition required for pre-ENA address assignment is missing.

STATE ERROR (CATEGORY CODE

= X'20')

This category indicates a sequence number error, or an RH or RU that is not allowed
for the receiver's current session control or data flow control state.
These errors
prevent delivery of the request to the intended component.
Category and modifier (in hexadecimal):
2001

Sequence Number: Sequence number received on normal-flow request was not 1
greater than the last.

2002

Chaining:
Error in the sequence of the chain indicator settings (BCI,
ECl), such as first, middle, first.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

No specific code applies.

Chapter 9.

Sense Data

9-53

2003

0001

The receiver received a middle or end-chain request when in the
in-chain state.

0002

The receiver received a begin-chain request when in the in-chain
state.

Bracket:
Error resulting from failure of sender to enforce bracket rules
for session.
(This error does not apply to contention or race
conditions.)
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

The receiver received a begin-bracket request before receiving a
response to its own previously sent begin-bracket request.

0002

The receiver received a begin-bracket request not specifying
begin-bracket when in the between-bracket state.

0003

The receiver received an out-of-sequence LUSTAT command.

2004

Direction: Error resulting from a normal-flow request received while the
half-duplex flip-flop state was not Receive.

2005

Data Traffic Reset:
An FMD or normal-flow DFC request received by a
half-session whose session activation state was active, but whose data
traffic state was not active.

2006

Data Traffic Quiesced: An FMD or DFC request received from a half-session
that has sent QUIESCE COMPLETE or SHUTDOWN COMPLETE and has not responded
to RELEASE QUIESCE.

2007

Data Traffic Not Reset: A session control request (for example, STSN),
allowed only while the data traffic state is reset, was received while the
data traffic state was not reset.

2008

No Begin Bracket: An FMD request specifying BBI=BB was received after the
receiver had previously received a BRACKET INITIATION STOPPED request.

2069

Session Control Protocol Violation: An SC protocol has been violated; a
request, allowed only after a successful exchange of an SC request and its
associated positive response, has been received before such successful
exchange has occurred (for example, an FMD request has preceded a required
CRYPTOGRAPHY VERIFICATION request).
The request code of the particular SC
request or response required, or X'OO' if undetermined, appears in the
fourth byte of the sense data.

200A

Immediate Request Mode Error:
been violated by the request.

200B

Queued Response Error: The Queued Response protocol has been violated by a
request, i.e., QRI=-QR when an outstanding request had QRI=QR.

9-54

SNA Formats

The immediate request mode protocol has

200C

ERP Sync Event Error: The ERP sync event protocol in DFC has been
violated; for example, after receiving a negative response to a chain, a
request other than a request soliciting a synchronization event response
was sent to DFC_SEND and rejected.

2000

Response Owed Before Sending Request: An attempt has been made in
half-duplex (flip-flop or contention) send/receive mode to send a
normal-flow request when a response to a previously received request has
not yet been sent.

200E

Response Correlation Error: A response was received-that cannot be
correlated to a previously sent request.

200F

Response Protocol Error:
A violation has occurred in the response
protocol; e.g., a +RSP to an RQE chain was generated.

2010

BIS Protocol Error:
A BIS protocol error was detected; for example, a BIS
request was received after a previous BIS was received and processed.

2011

Pacing Protocol Error.

2012

0000

A normal-flow request was received by a half-session after the
pacing count had been reduced to 0 and before a pacing response had
been sent.

0001

Unexpected Isolated Pacing Message (IPM) Received:
An IPM was
received when the receiver was in a state that did not allow it.

0002

Unexpected Pacing Request Received:
A request with the pacing
indicator set was received when the receiver was in a state that did
not allow it.

Invalid Sense Code Received: A negative response was received that
contains an SNA-defined sense code that cannot be used for the sent
request.

RH USAGE ERROR [CATEGORY CODE

= X'40')

This category indicates that the value of a field or combination of fields in the RH
violates architectural rules or previously selected BIND options. These errors
prevent delivery of the request to the intended component and are independent of the
current states of the session. They may result from the failure of the sender to
enforce session rules.
Detection by the receiver of each of these errors is
optional.
Category and modifier (in hexadecimal):
4001

Invalid SC or NC RH: The RH of a session control (SC) or network control
(NC) request was invalid.
For example, an SC RH with pacing request
indicator set to I is invalid.

Chapter 9.

Sense Data

9-55

4002

Reserved

4003

BB Not Allowed: The Begin Bracket indicator (BBI) was specified
incorrectly, for example, BBI=BB with BCI=-BC.

4004

CEB or EB Not Allowed: The Conditional End Bracket indicator (CEBI) or End
Bracket indicator (EBI) was specified incorrectly, for example, CEBI=CEB
when EC1=-EC or EBI=EB with BCI=-BC, or by the primary half-session when
only the secondary may send EB, or by the secondary when only the primary
may send EB.

4005

Incomplete RH: Transmission shorter than full TH-RH.

4006

Exception Response Not Allowed: Exception response was requested when not
permitted.

4007

Definite Response Not Allowed: Definite response was requested when not
permitted.

4008

Pacing Not Supported: The Pacing indicator was set on a request, but the
receiving half-session or boundary function half-session does not support
pacing for this seSS10n.

4009

CD Not Allowed: The Change Direction indicator (CDI) was specified
incorrectly, for example, CDI=CD with ECI=-EC, or CD1=CD with EB1=EB.

400A

No-Response Not Allowed: No-response was specified on a request when not
permitted. (Used only on EXR.)

400B

Chaining Not Supported: The chaining indicators (BCI and ECI) were
specified incorrectly, for example, chaining bits indicated other than
(BC,EC), but multiple-request chains are not supported for the session or
for the category specified in the request header.

400C

Brackets Not Supported: The bracket indicators (BBI, CEBI, and EBI) were
specified incorrectly, e.g., a bracket indicator was set (BB1=BB,
CEBI=CEB, or EB1=EB), but brackets are not used for the session.

400D

CD Not Supported: The Change-Direction indicator was set, but is not
supported.

400E

Reserved

400F

Incorrect Use of Format Indicator:
The Format indicator (F1) was
specified incorrectly, for example, F1 was set with BC1=-BC, or FI was not
set on a DFC request.

4010

Alternate Code Not Supported: The Code Selection indicator (CSI) was set
when not supported for the session.

4011

Incorrect Specification of RU Category: The RU Category indicator was
specified incorrectly, for example, an expedited-flow request or response
was specified with RU Category indicator = FMD.

9-56

SNA Formats

4012

Incorrect Specification of Request Code: The request code on a response
does not match the request code on its corresponding request.

4013

Incorrect Specification of (501, RTI): The Sense Oata Included indicator
(501) and the Response Type indicator (RTI) were not specified properly on
a response. The proper value pairs are (501=50, RTI=negative) and
(SOI=~SO, RTI=positive).

4014

Incorrect Use of (DRII, DR2I, ERI): The Definite Response 1 indicator
(DRII), Definite Response 2 indicator (DR2I), and Exception Response
indicator (ERI) were specified incorrectly, for example, a SIGNAL request
was not specified with DRII=DRI, DR2I=~DR2, and ERI=~ER.

4015

Incorrect Use of QRI: The Queued Response indicator (QRI) was specified
incorrectly, for example, QRI=QR on an expedited-flow request.

4016

Incorrect Use of EDI: The Enciphered Data indicator (EDI) was specified
incorrectly, for example, EDI=ED on a DFC request.

4017

Incorrect Use of PDI: The Padded Data indicator (PDI) was specified
incorrectly, for example, PDI=PD on a DFC request.

4018

Incorrect Setting of QRI with Bidder's BB: The first speaker half-session
received a BB chain requesting use of a session (via lUSTAT(X'0006')), but
the QRI was specified incorrectly, that is, QRI = ~QR.

4019

Incorrect Indicators with last-In-Chain Request:
A last-in-chain request
has specified incompatible RH settings, for example, RQE*, CEBI=~CEB, and
CDI=~CD.

401A
through
4020
4021

Reserved

QRI Setting in Response Different From That in Request:
The QRI setting
in the response differs from the QRI setting in the corresponding request.

PATH ERROR (CATEGORY CODE

= X'SO']

This category indicates that the request could not be delivered to the intended
receiver, because of a path outage, an invalid sequence of activation requests, or
one of the listed path information unit (PIU) errors.
Some PIU errors fall into
other categories; for example, sequence number errors are sense code category X'20'.
A path error received while the session is active generally indicates that the path
to the session partner has been lost.
Category and modifier (in hexadecimal):
8001

Intermediate Node Failure: Machine or program check in a node providing
intermediate routing function.
A response mayor may not be possible.

Chapter 9.

Sense Data

9-57

8002

link Failure: Data link failure.

8003

NAU Inoperative: The NAU is unable to process requests or responses; for
example, the NAU has been disrupted by an abnormal termination.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

8004

0000

No specific code applies.

0001

Hierarchical Reset: The identified lU-lU session is being
deactivated; an ACTlU/ACTPUCCold) or DACTlU/DACTPU was received, or
the PU has failed.

0003

Unrecoverable lU Failure: The identified lU-lU session had to be
deactivated because of an abnormal termination of the PlU or SlU;
recovery from the failure was not possible.

0004

Recoverable lU Failure:
The identified lU-lU session had to be
deactivated because of an abnormal termination of one of the lUs of
the session; recovery from the failure may be possible.

0005

Hierarchical Reset:
hierarchical reset.

Backup session reset resulted from a

Unrecognized Destination: A node in the path has no routing information
for the destination specified either by the SLU name in a BIND request or
by the TH.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:

8005

0000

No specific code applies.

0001

A request was received by a gateway function that could not be
rerouted because of invalid or incomplete routing information.

No Session:
No half-session is active in the receiving end node for the
indicated origination-destination pair, or no boundary function session
connector is active for the origin-destination pair in a node providing
the boundary function.
A session activation request is needed.
Bytes 2 and 3 following the sense code contain sense code specific
Settings allowed are:
information.

9-58

0000

No specific code applies.

0001

The receiver received a request other than session control request
when no lU-lU session was active.

0002

The receiver received a request other than session control request
when no lU-SSCP session was active.

SNA Formats

0003

The receiver received a session control request other than
BIND/UNBIND when no LU-LU session was active.

0004

The receiver received an UNBIND when no LU-LU session was active.

0005

The receiver received a session control request other than
ACTLU/DACTLU for the LU-SSCP session when no LU-SSCP session was
active.

0006

The receiver received DACTLU when no LU-SSCP session was active.

0007

Session not activated: A BIND was received for a dependent LU that
has not received an ACTLU to activate the SSCP-LU session.

8006

Invalid FlO: Invalid FlO for the receiving node. (See Note 1 located at
the end of this chapter).

8007

Segmenting Error:
First BIU segment had less than 10 bytes; or Mapping
field sequencing error, such as first, last, middle; or segmenting not
supported and Mapping field not set to BBIU, EBIU.
(See Note 2 located at
the end of this chapter).
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

The node does not support receipt of segments, and a Mapping field
value other than BBIU, EBIU was received. Sent in UNBIND.

0002

Interleaved BIND Segments Not Allowed: A BIND receiver that 1S 1n
the middle of receiving segments of one BIND receives a segment from
a different BIND; the receiver rejects both BINDs and disconnects
the link.

8008

PU Not Active: The SSCP-PU
has not been activated and
half-session; for example,
not have an active SSCP-PU
addressed LU.

secondary half-session in the receiving node
the request was not ACTPU for this
the request was ACTLU from an SSCP that does
session with the PU associated with the

8009

LU Not Active: The destination address specifies an LU for which the
SSCP-LU secondary half-session has not been activated and the request was
not ACTLU.

800A

Too-Long PIU: Transmission was truncated by a receiving node because the
PIU exceeded a maximum length or sufficient buffering was not available.

800B

Incomplete TH: Transmission received was shorter than a TH.
located at the end of this chapter),

800C

DCF Error:

(See Note 1

Data Count field inconsistent with transmission length.

Chapter 9.

Sense Data

9-59

800D

Lost Contact: Contact with the link station for which the transmission
was intended has been lost, but the link has not failed.
If the
difference between link failure and loss of contact is not detectable,
link failure (X'8002') is sent.

800E

Unrecognized Origin:
recognized.

800F

The address combination is invalid.

The origin address specified in the TH was not

Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
0000

The (DAF',DAF') (FID2) combination or the LSID (FID3) specified an
invalid type of session, for example, a PU-LU combination.

0001

The FID2 DDAI setting in a received BIND is incorrect;
rejected.

the BIND is

8010

Segmented RU Length Error:
An RU was found to exceed a maximum length, or
required buffer allocation that might cause future buffer depletion.

8011

ER Inoperative or Undefined:
A PIU was received from a subarea node that
does not support ER and VR protocols, and the explicit route to the
destination is inoperative or undefined.

8012

Subarea PU Not Active or Invalid Virtual Route: A session-activation
request for a peripheral PU or LU cannot be satisfied because there is no
active SSCP-PU session for the subarea node providing boundary function
support, or the virtual route for the specified SSCP-PU (type 1 or type 2
nodes) or SSCP-LU session is not the same as that used for the SSCP-PU
session of the type 1 or type 2 node's PU or the LU's subarea PU.

8013

COS Not Available:
A session activation request cannot be satisfied
because none of the virtual routes requested for the session is available.
Bytes 2 and 3 following the sense code contain sense code specific
information.
Settings allowed are:
Byte 2 indicates the environment in which the failure was detected:
00

Single network

01

Interconnected network:
Failure was detected at a node in a
subnetwork other than that of the NAU sending the activation
request.

Byte 3 indicates the reason for the session-activation failure:
00

9-60

No Specific Code Applies: This means an error occurred, but none of
the conditions listed below applies.

SNA Formats

01

No Mapping Specified: A session-activation request cannot be
satisfied because for each VR in the VR identifier list for the
session, no VR to ER mapping is specified.

02

No Explicit Routes Defined: A session-activation request cannot be
satisfied because each VR in the VR identifier list for the session
maps to a corresponding ER that is not defined.

03

No VR Resource Available:
A session-activation request cannot be
satisfied because each VR specified in the VR identifier list for
the session requires a node resource that is not available.

04

No Explicit Routes Operative: A session-activation request cannot
be satisfied because no underlying ER is operative for any VR
specified in the VR identifier list for the session.

05

No Explicit Route Can Be Activated: A session-activation request
cannot be satisfied because no VR specified in the VR identifier
list for the session mapped to a defined and QPerative ER that could
be activated.

06

No Virtual Route Can Be Activated:
A session-activation request
cannot be satisfied because no VR specified in the VR identifier
list for the session can be activated by the PU, though for at least
one VR an underlying ER is defined, operative, and activated.

07

No Virtual Route Identifier List Available:
A session-activation
request cannot be satisfied because a VR identifier list is not
available.

Note:
If none of the virtual routes specified in the VR identifier list
for the session is active or can be activated, the reported reason is set
based on a hierarchy of failure events. The "highest" of the failures
that occurred within the set of virtual routes is returned on the
response.
For example, if the VR manager receives a negative response to
an NC-ACTVR request for a VR specified in the VR identifier list and for
all other VRs in the list no VR to ER mapping is specified, then reason
X'06' is reported.
The hierarchy of the failure reasons is in ascending
numeric order, that is, reason X'02' is higher than reason X'OI'.

8014
through
8016

Reserved

8017

PIU from Adjacent Pre-ER-VR Subarea Node Rejected:
A PIU that requires
intermediate path-control routing was received by a subarea node from an
adjacent subarea node that does not support ER-VR protocols, but the
receiving subarea node does not support intermediate path-control routing
for adjacent subarea nodes that do not support ER-VR protocols.

8018

Management Services component is unable to find or recognize the name of
the application transaction program specified in the request.

Chapter 9.

Sense Data

9-61

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

8020

0000

No specific code applies.

0001

The application transaction program specified in the request is not
recognized by PUMS.

Session Reset: The LU-LU session identified in the UNBIND is being
deactivated because of a reset condition.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

Virtual Route Inoperative: The virtual route used by the LU-LU
session has become inoperative, thus forcing the deactivation of the
identifed LU-LU session.

0002

Hierarchical Reset of Both XRF-active and XRF-backup Sessions: The
XRF-backup session has failed; therefore, both the XRF-active and
XRF-backup session are being reset.

0003

Virtual Route Deactivated: The identified LU-LU session had to be
deactivated because of a forced deactivation of the virtual route
being used by the LU-LU session.

0004

Route Extension Failure: The route extension used by the LU-LU
session has become inoperative, thus forcing the deactivation of the
identified LU-LU session.

0005

Route Extension Failure: The route extension used by the XRF-backup
LU-LU session has become inoperative, thus forcing the deactivation
of the identified XRF-backup LU-LU session.

0006

Virtual Route Inoperative: The virtual route used by the LU-LU
session has become inoperative, thus forcing the deactivation via
VR-INOP of the identifed XRF-backup LU-LU session.

Notes:
1.

It is generally not possible to send a response for this exception condition,
since information (FID, addresses) required to generate a response is not
available.
It is logged as an error if this capability exists in the receiver.

2.

If segmenting is not supported, a negative response is returned for the first
segment only, since this contains the RH.
Subsequent segments are discarded.

9-62

SNA Formats

CHAPTER 10.

FUNCTION MANAGEMENT HEADERS

The request header (RH) contains a format indicator (FI) that, when
that an FM header is at the beginning of the request unit (RU).

~,

indicates

FM headers appearl only at the beginning of an RU.
An RU containing an FM header
may appear anywhere within a chain. When the FM header is longer than one RU will
hold, the header is continued in as many additional RUs of a chain as needed to hold
it.
Figure 10-1 and Figure 10~2 show the placement of FM headers within an RU:

RH:

Figure 10-1.

RH:

FMH, *BC,*EC

Data

FM Header Contained in One RU

FMH, *BC, ... EC

RH: ... FMH, ... BC,*EC

Figure 10-2.

FM header

First of FM header

Rest of FM header

Data

FM Header Contained in Two Contiguous RUs of a Chain

Chapter 10.

Function Management Headers

10-1

Figure 10-3 shows some instances where FM headers are used and Figure 10-4
identifies the logical unit (LU) types that use each FM Header.

TH

RH

FMH

TH

RH

FMH

Data

TH

RH

FMH

FMH

Data

(see Note)

TH

RH

FMH

GDS

Data

GDS

FMH
GDS
TH
RH

Function Management (FM) Header
General Data Stream identifier
Transmission Header
Request/Response Header

:hp5.Note:ehp5.:
Figure 10-3.

Data

In LU type 6.2 a maximum of one FM header per RU is allowed.

Usage of FM Headers

I

LU Type

Figure 10-4.

10-2

FM Header Type

0

None required, but may use any

1

I, 2, 3

2

None

3

None

4

I, 2, 3

6.1

4, 5, 6, 7, 8, 10

6.2

5, 7, 12

7

None

LU Types That Support FM Headers

SNA Formats

I
I
header I
I
I
I
I
I
I
I
I
I
I
I
I
----i
I

FM Header 1
This header is used to select a destination within a logical unit (LU).
A
destination may be represented by a device, a data set residing on a device, or
merely a data stream. The LU initiates, interrupts, resumes, and concludes data
traffic for the half-session using the FMH-l.

a
1

2

3

Length, in binary, of FMH-l, including this Length byte
bit 0, FMH concatenation:
a no FMH follows this FMH-l
1 another FMH follows this FMH-1
bits 1-7, type:
0000001
bits 0-3, select desired medium for data (see Notes 1 and 2):
0000 console
0001 exchange
0010 card
0011 document
0100 nonexchange disk
0101 extended document
0110 extended card
0111 data set name select destination (see Note 3)
1000 word processing (WP) media 1
1001 WP media 2
1010 WP media 3
1011 reserved
1100 WP media 4
1101 reserved
1110 reserved
1111 reserved
bits 4-7, logical subaddress (see Note 2):
0000-1110 specific device in medium class
1111 any device in medium class (see Note 3)
bit 0, SRI: stack reference indicator:
a stack to be used 1S the sender's send stack
1 stack to be used is the receiver's send stack
bit 1, demand select:
a receiver may direct data to alternate medium/subaddress
1 receiver must direct data to specified medium/subaddress
(spooling is prohibited)
bits 2-3, reserved
bits 4-7, nsps:
da.ta stream profiles:
0000 default (the nsp is implied by the Medium Select field)
0001 base
0010 general
0011 job
0100 WP raw-form text
0101 WP exchange diskette
0110 reserved
0111 Office Information Interchange level 2
1000 reserved
1001 reserved
1010 document interchange
1011 structured field
1100 reserved

Chapter 10.

Function Management Headers

10-3

1101 reserved
1110 reserved
1111 reserved
FMH-l properties
bits 0-2, DSSEL:
destination selection:
000 resume
001 end
010 begin
011 begin/end
100 suspend
101 end-abort
110 continue
III reserved
data set transmission (see Note 6):
bit 3, DST:
o transmission exchange format
1 basic exchange format
bit 4, reserved
bit 5, CMI:
compression indicator (see Notes 4 and 5):
o no compression
1 compression (the first byte following FMH(s) is a string control
byte)
bit 6, CPI:
compaction indicator (see Notes 4 and 5):
o no compaction
1 compaction (the first byte following the FMH(s) 1S a string
control byte)
bit 7, reserved
bits 0-7, ECRL:
exchange record length if medium select = exchange or
card; otherwise, reserved.
For medium select = card, a
hexadecimal value indicates maximum card length:
00000000 80-column length
Reserved (optional)
DSLEN:
length of destination name (optional)
DSNAME:
destination name (optional; reserved when DSSEL = continue)

4

5

6-7
8

9-n
Note 1:

The data stream profile (DSP) defaults for the Medium Select field are:

FMH-l MEDIUM SELECT

DEFAULT DSP

Console, X'O'
Exchange, X'l'
Card, X'2'
Document, X'3'
Nonexchange Disk, X'4'
Extended Document,X'5'
Extended Card, X'6'
WP Medium I, X'8'
WP Medium 2, X'9'
WP Medium 3, X'A'
WP Medium 4, X'C'

Base
DST field of FMH-l
SCS (IRS, TRN)
Subset 2 (RJE)
DST field of FMH-I
Subset 2 (RJE)
SCS (IRS, TRN)
WP Raw Form
WP Raw Form
WP Raw Form
WP Raw Form

An LU requiring any other DSP value associated with Medium Select does so by
specifying the desired DSP in byte 3, bits 4-7 of the FMH-l. This selection
adheres to those DSPs allowed on the session as specified in the BIND parameters.

10-4

SNA Formats

Note ~ Medium Select and Logical Subaddress fields are reserved when the
Destination Selection (DSSEL) field is set to 110 (continue), 001 (end), 100
(suspend), or 101 (end-abort).

=

Note ~ Medium Select
X'7' and Logical Subaddress
(DSNAME) field is used to select destination.

= X'F',

the Destination Name

Note 4: CMI, CPI, and ERCL indicators are meaningful and valid only when specified
in a Begin, Begin/end, or Continue FMH-l.
Note 5: CMI, CPI, and ERCL information received when DSSEL = Continue overlays the
settings of the Begin FMH-l or the last-received Continue FMH-l.
Note ~ When Medium Select is not equal to Exchange, this field is reserved.
Receiver may do spooling and exchange-medium creation locally.
When Medium Select =
Exchange, specifying 0 preserves chain boundaries while spooling, but nonsequential
allocation techniques may be used.
Specifying 1 does not preserve chain boundaries,
but uses sequential medium allocation.

Chapter 10.

Function Management Headers

10-5

FM Header 2
Once a destination has been selected using a FMH-l, this header handles the data
management tasks for that destination.

o

Length, in binary, of FMH-2, including this Length byte
bit 0, FMH concatenation:
o no FMH follows this FMH-2
1 another FMH follows this FMH-2
bits 1-7, type:
0000010
bit 0, SRI: stack reference indicator (see Note below):
o FMH-2 pertains to the active destination of the sending
half-session's send stack and the receiving half-session's
receive stack
1 FMH-2 pertains to the active destination of the receiving
half-session's send stack and the sending half-session's receive
stack
bits 1-7, FMH-2 function to be performed (see Note):
nnnnnnn identifies the function that this FMH-2 is to perform
Parameter fields (These fields provide the information needed to perform
the selected function.
They are different for each FMH-2 function, and
are described in Sessions Between Logical Units.)

1

2

3-n

Note:
Byte 2 of the FMH-2 contains the Stack Reference indicator (SRI) and defines
the function to be performed. The valid combinations of SRI and function codes are:

Function
Code
X'Ol'
X'02'
X'04'
X'07'
X'20'
X'21'
X'22'
X ' 23 1
X'24'
X ' 25

1

X'26'
X' 27 1
X ' 28

1

X ' 29 1
X'2B'
X'2C'
X'2D'
X'2E'
X'AA'

10-6

Function
Peripheral data information record (PDIR)
Compaction table
Prime compression character
Execute program offline
Create data set
Scratch data set
Erase data set
Password
Add
Replace
Add replicate
Replace replicate
Query for data set
Note
Record ID
Erase record
Scratch all data sets
Volume ID
Note reply (SRI is always on)

SNA Formats

FM Header 3
This header handles data management tasks that are common to all destinations in the
lU-lU session.
The FMH-3 format is identical to the FMH-2 format except that an FMH-3 does not have
a Stack Reference indicator (SRI) in byte 2.
An FMH-3 is used when information is
needed or used by all destinations managed by the half-session.
By contrast, an
FMH-2 is used for a specific destination.
Two functions, the Compaction Table FMH and the Prime Compression Character FMH, can
be sent as an FMH-2 or FMH-3.
They are sent as an FMH-2 when they apply to a
specific destination at the half-session and as an FMH-3 when they apply to all
destinations at the half-session.
The FMH-3 functions are as follows:

Function
Code
X'02'
X'03'
X'04'
X'05'
X'06'

Function
Compaction table
Query for compaction table
Prime compression character
Status
Series 10

Chapter 10.

Function Management Headers

10-7

FM Header 4
This header carries a logical block command and its parameters that, together with
information, apply to a logical block within a logical message as defined for
Logical Message Service.

o
1
2

3

4
5

6

7

10-8

Length, in binary, of FMH-4, including this Length byte
bit 0, FMH concatenation (must be 0)
bits 1-7, type:
0000100
FMH4FXCT:
length of fixed length parameters excluding the length of
FMH4FXCT.
The first nonfixed parameter position is FMH4LBN.
The minimum
value of FMH4FXCT is 3, the maximum is 4.
FMH4TT1:
block transmission type:
X'OO' inherit code (from MM-TT register)
X'01'-X'3F' reserved
X'40' FFR-FNI record
X'41' FFR-FS record
X'42' FFR-FS2 record
X'43'-X'4F' reserved
X'50'-X'FE' reserved
X'FF' reserved
Note:
FFR=field formatted record, FNI=fixed fields without
field separators, FS=fixed fields with field separators,
FS2=fixed fields with or without field separators.
FMH4TT2:
block transmission type qualifier:
reserved except for
FMH4TTl=X'4l' or X'42', in which case it holds the separator value
FMH4CMD:
command:
X'OO' CRT-NU-BLK
X'02' CRT-SU-BLK
X'03' CRT-SN-BLK
X 'I 0' CONT-NU-BLK
X'12' CONT-SU-BLK
X'13' CONT-SN-BLK
X'23' DEL-SN-BLK
X'32' UPD-SU-BLK
X'33' UPD-SN-BLK
X'42' RPL-SU-BLK
X'43' RPL-SN-BLK
Other reserved
Note:
NU=nonshared, unnamed; SU=shared, unnamed; SN=shared,
named; NN=nonshared, named
FMH4FLAG:
flags (if omitted, X'OO' is assumed):
bits 0-1, reserved
bits 2-3, F4RDESCR:
record descriptor flag:
00 no logical record headers (LRHs) in transmission block
01 LRHs present, with implicit lengths
10 reserved
11 reserved
bits 4-5, reserved
bit 6, FMH4BDTF:
block data transform flag:
o FMH4BDT absent
1 FMH4BDT present
bit 7, FMH4RDTF:
reserved
FMH4LBN:
length of FMH4BN (X'OO', or omitted, if unnamed block)

SNA Formats

8-m
m+l
m+2-n
n+l
n+2-p

FMH4BN: name of block
FMH4LBDT: length of FMH4BDT (X'OO if FMH4BDTF is 0)
FMH4BDT: block data transform
FMH4LVID: length of FMH4VID
FMH4VID: version identifier

Chapter 10.

Function Management Headers

10-9

FM Header 5:

Attach (LU 6.21

LU type 6.2 uses this header to carry a request for a conversation to be established
between two transaction programs. This header identifies the transa~tion program
that is to be put into execution and connected to the receiving half-session.
When a transaction program issues an ALLOCATE verb naming a transaction program to
be run at the other end of the conversation, an Attach FMH-S carries the transaction
program name (TPN) to the receiving LU.

o
1

2-3

4

S

6-j
6

7
8(=j)

j+l-p
j+l-k
j+l
j+2-k

k+l-m
k+l
k+2-m
m+l-n
m+l
m+2-n
m+2
m+3-w
w+l-w+6

10-10

Length, in binary, of FMH-5, including this Length byte
bit 0, reserved
bits 1-7, type:
0000101
Command code:
X'02FF' (Attach)
bit 0, security indicator:
o user ID is not already verified
1 user ID is already verified
bits 1-3, reserved
bit 4, program initialization parameter (PIP) presence:
o PIP not present following this FMH-5
1 PIP present following this FMH-S (see "PIP Variable " on page
10-11 for format)
bits 5-7, reserved
Length (j-S), in binary, of Fixed Length Parameters field (currently
3--future expansion possible)
Fixed Length Parameters
Resource type:
X'DO' basic conversation
X'Dl' mapped conversation
Reserved
bits 0-1, synchronization level:
00 none
01 confirm
10 confirm, sync point, and backout
11 reserved
bits 2-7, reserved
Variable Length Parameters
Transaction Program Name Field:
Length (values 1 to 64 are valid), in binary, of transaction program name
Transaction program name: a symbol string identifying a transaction
program name known at the receiver; receivers may constrain such names to
be type A, AE, GR, or DB, depending on the implementation
Access Security Information Field:
Length (0 or m-k-l), in binary, of Access Security Information subfields
Zero or more Access Security Information subfields (see "Access Security
Information Subfields " on page 10-11 for format)
Logical-Unit-of-Work Identifier Field:
Length (values 0 and 10 to 26 are valid), in binary, of
Logical-Unit-of-Work Identifier field
Logical-Unit-of-Work Identifier
Length (values 1 to 17 are valid), in binary, of network-qualified LU name
Network-qualified LU network name (format described in "Chapter 7. User
Data Structured Subfields")
Logical-unit-of-work instance number, in binary

SNA Formats

w+7w+8(=n)
n+1-p
n+1
n+2-p

Logica1-unit-of-work sequence number, in binary
Conversation Correlator Field:
Length (values 0 to 8 are valid), in binary, of conversation correlator of
sender
Conversation correlator of the sending transaction: a 1- to 8-byte
symbol-string type G identifier (unique between partner LUs) of the
conversation being allocated via FMH-S (an example construction of this
field would be the composition of a transaction program instance
identifier and a resource identifier)

Note:
Trailing length fields (bytes n+l, m+1, and k+1) that have value X'OO' can be
omitted.

Access Security Information Subfields
The Access Security Information subfields in FMH-S have the following formats:

o

length (valid values are 1 to 11), in binary, of remainder of
subfield--does not include this length byte
Subfield type:
1
X'OO' profile
X'Ol' password
X'02' user ID
2-i
Data: a symbol string identifying access security information known at
the receiver; receivers may constrain such information to be type A, AE,
GR, or DB, depending on the implementation.
Note: The length of the symbol string may be less than the length of the
Data field; in this case, the symbol string is left-justified within the
Data field and the Data field is filled out to the right with space (hex
40) characters. Space characters, if present, are not part of the symbol
string.
Note:
The Access Security Information subfields may appear in any order in the
Access Security Information field of the FMH-S.

PIP Variable
The PIP variable following FMH-S Attach has the following format:
0-1
2-3
4-n

length (4 or n+l), in binary, of PIP variable, including this Length field
GDS indicator: X'12FS'
Zero or more PIP subfields, each of which has the following format (shown
in "PIP Subfield " using zero-origin)

PIP Subfield
Zero or more of these subfields are contained in a PIP variable (see "PIP Variable
")

.

0-1
2-3
4-m

Length, in binary, of PIP subfield, including this length field
GDS indicator: X'12E2'
PIP subfield data:
type-G symbol string is valid

Chapter 10.

Function Management Headers

10-11

FM Header S:

Attach (Not LU 6.21

This header flows from the program using the sending half-session to the attach
manager of the receiving half-session.
This header identifies the program at the
receiving LU that it wishes to have attached.
An FMH-S can be followed by other
FMHs (for example, FMH-6, FMH-8, and FMH-4), a logical record header (LRH), and FM
data.
Optionally, it can be sent with CD or EB.

o
1

2-3

4
S

6
7
8-n

10-12

length, in binary, of FMH-S, including this length byte
bit 0, FMH concatenation:
o no FMH follows this FMH-S
1 another FMH follows this FMH-S
bits 1-7, type:
0000101
FMHSCMD:
command code:
X'0202' attach transaction program
X'0204' reset attached process
X'0206' data descriptor
FMH5MOD:
modifier
FMH5FXCT:
fixed-length parameters:
X'OO' reset attached process
X'02' attach transaction program, data descriptor
ATTDSP
ATTDBA
Resource names

SNA Formats

FM Header &
This header flows from a currently active transaction program using a sending
half-session to a currently active transaction program using a receiving
half-session.

o
1

2-3

4

5-n

n+l-m
m+l-p

p+l-q

Length, in binary, of FMH-6, including this Length byte
bit 0, FMH concatenation:
o no FMH follows this FMH-6
1 another FMH follows this FMH-6
bits 1-7, type:
0000110
Command code (CC2):
For service transaction programs, the first byte of
the command code identifies a transaction program and the second byte
identifies a function within a transaction program.
FMH6MOD: modifier
bit 0, FMH6LNSZ:
length of parameter length fields:
o I-byte field
1 2-byte field
bits 1-7, reserved
Fixed:
total length of fixed length parameters (LF): This field contains
the sum of the lengths of all fixed length parameters that are mandatory
for the particular command code located in bytes 2 and 3. This field is
either one byte or two bytes in length based on the setting of FMH6LNSZ (0
= one byte; 1 = two bytes).
Fixed length parameters (FDy):
the fixed length parameters are positional
by command code
Variable:
length field of first, positional variable-length parameter
(LVI):
This field is either one byte or two bytes in length based on the
setting of FMH6LNSZ (0 = one byte; 1 = two bytes).
If the Length field
(LVx) is equal to 0, then the variable parameter is omitted.
The next
positional variable-length parameter length (LV2) occurs in byte q+l.
Variable-length positional parameter (VD).
The LV and VD fields are
replicated to represent x number of variable-length parameters according
to command code.

Chapter 10.

Function Management Headers

10-13

FM Header 7:

Error Description (LU 6.2)

LU type 6.2 uses this header, following negative response (0846), to carry
information that relates to an error on the session or conversation. For example,
an FMH-7 and additional error information are sent when an FMH-5 (Attach) specifies
a nonexistent transaction program name.

o

Length (7), in binary, of FMH-7, including this Length byte
bit 0, reserved
bits 1-7, type: 0000111
SNA-defined sense data (see below)
bit 0, error log variable presence:
o no error log variable follows this FMH-7
1 error log GDS variable follows this FMH-7
bits 1-7, reserved

1
2-5
6

Note: Only the following sense data (in hexadecimal) can be sent in an LU 6.2
FMH-7. Sense data carried in non-LU 6.2 FMH-7 varies by implementation. See
"Chapter 9. Sense Data" for additional details on sense data. The phrases following
the sense data are the symbolic return codes provided to the application program in
lU 6.2 verbs (see SNA Transaction Programmer's Reference Manual for lU Type 6.2)
when the sense data is received.

Sense ---Data
-----

Return Code

l008600B
10086021
10086031
10086032
10086034
10086041
080F6051
08240000
084B6031
084COOOO
08640000
08640001
08640002
08890000
08890001
08890100
08890101

RESOURCE FAILURE_NO_RETRY
AlLOCATION_ERROR--TPN_NOT_RECOGNIZED
AlLOCATION_ERROR--PIP_NOT_ALlOWED
AlLOCATION_ERROR--PIP_NOT_SPECIFIED_CORRECTlY
AlLOCATION_ERROR--CONVERSATION_TYPE_MISMATCH
AllOCATION_ERROR--SYNC_lEVEL_NOT_SUPPORTED_BY_PGM
AlLOCATION_ERROR--SECURITY_NOT_VALID
BACKED_OUT
AllOCATION_ERROR--TRANS_PGM_NOT_AVAIl RETRY
AlLOCATION_ERROR--TRANS_PGM_NOT_AVAIl_NO_RETRY
DEALLOCATE_ABEND_PROG
DEALlOCATE_ABEND_SVC
DEALLOCATE_ABEND_TIMER
PROG_ERROR_NO_TRUNC or PROG_ERROR_PURGING
PROG_ERROR_TRUNC
SVC_ERROR_NO_TRUNC or SVC_ERROR_PURGING
SVC_ERROR_TRUNC

10-14

SNA Formats

FM Header 7:

Error Description (Not LU 6.2)

This header is sent after a negative response (0846) to provide further information
about an error.

o
1

2-5
6-7

Length, in binary, of FMH-7, including this Length byte
bit 0, FMH concatenation:
o no FMH follows this FMH-7
1 reserved
bits 1-7, type:
0000111
ERPSENSE:
SNA-defined sense data, which would appear on error response
(see "Chapter 9. Sense Data" in Chapter 9)
ERPSEQ: sequence number of RU chain in which error was detected

FM Header 8

This header is used only with IMS/VS logical message services that use LU type 6.1
protocols.
Refer to the IMS publications for the formats and meanings of the bytes
in this header.

FM Header 10
This header is sent to prepare the session for a sync point.
It may be sent with
data.
The RU chain has CD set on so that the receiver may, on the next flow,
request a sync point or abort the unit of work.

o
1

2-3
4-5

length, in binary, of FMH-IO, including this length byte
bit 0, FMH concatenation:
o no FMH follows this FMH-IO
1 another FMH follows this FMH-IO
bits 1-7, type:
0001010
SPCCMD: sync point command:
X'0202' Prepare command
SPCMOD: sync point modifier
For a Prepare command (FMH-I0), the modifier indicates RH settings to be
returned on the first RU chain sent by the FMH-I0 receiver.
X'OOOO' *CD, *EB: The sender of FMH-IO does not care what RH settings are
returned on the reply.
X'OOOI' EB: The sender of FMH-lO requires an EB on the reply.
X'0002' CD, -EB: The sender of FMH-IO requires a CD on the reply.

Chapter 10.

Function Management Headers

10-15

FM Header 12:

Security

LU type 6.2 uses this header during LU-LU verification.
This header is used to
return to the partner LU the enciphered version of the clear random data received in
+RSP(BIND).
The function management header 12 (FMH-12) has the following format:

o
1

2-9

10-16

Length (10), in binary, of FMH-12, including this Length byte.
bit 0, reserved
bits 1-7, type:
0001100
Enciphered version of the random data received in RSP(BIND)

SNA Formats

CHAPTER 11.

PRESENTATION SERVICES HEADERS

PRESENTATION SERVICES (PS) HEADERS

Presentation services (PS) headers convey information between PS component sync point
managers when the conversation using the session is allocated wi th the sync-point
synchronization level. These headers are used only by LU type 6.2.
Transaction program data is delimited using a 2-byte length field called an LL,
containing a value that is the number of bytes contained in the transaction program
data plus 2 (the length of the LL field itself).

LL

transaction program data

All PS headers are identified by an LL of X'OOOl' immediately preceding the header.
X'OOOl' is an invalid LL value for use by transaction programs because the LL's value
must include the length of itself, which is 2 bytes. Therefore, all LLs indicating a
length of less than 2 are reserved for use by the LU. The format of PS headers is
shown below.

Chapter 11.

Presentation Services Headers

11-1

PS Header 10:

Sync Point Control

Presentation services header 10 (Sync Point Control) has the following format:

o
1
2-3

4-5

11-2

Length, in binary, of PS header, including this length field
bit 0, reserved
bits 1-7, type: 0001010 sync point control (only value defined)
Sync point command type:
X'0005' Prepare
X'0006' Request Commit
X'0007' Committed
X'OOOg' Forget
X'0009' Heuristic Mixed
Modifier specifying next flow (present only if bytes 2-3 = X'0005' or
X'0006'; reserved when bytes 2-3 = X'0006' and 2-phase sync point being
used) :
X'OOOO' request RECEIVE
X'OOOl' request DEALLOCATE
X'0002' request SEND
Note:
Bytes
4-5
affect the Change Direction indicator
(CDI)
and
Conditional End Bracket indicator (CEBI) settings of the RH for the last PS
header in the sync point sequence, for example, Forget command type when
Prepare was the first PS header received, a~d Committed command type when
Request Commit was the first PS header received.

SNA Formats

CHAPTER 12.

GDS VARIABLES FOR SNA SERVICE TRANSACTION PROGRAMS

-- --

LIST OF SNA SERVICE TRANSACTION PROGRAMS
Logical Unit type 6.2 service transaction programs are identified by a transaction
program name (TPN) that begins with a value of X'06'.
Other SNA service transaction
programs are identified similarly.
Figure 12-1 identifies the transaction program
names that SNA currently defines. These TPNs are specified in an FM header type 5
(FMH5 Attach').

TP Description

TP Name
X' 06 F1****'
X' 06 F2****'

LU 6.2 Change Number of Sessions
LU 6.2 Sync Point Resynchronization

X'07FOFOF1'

DDM Synchronous Conversation

X'20FOFOFO'
X'20FOFOF1'

DIA PROCESS Destination TP
DIA SERVER TP

X'21FOFOF1'
X'21FOFOF2'
X'21FOFOF3'
X'21FOFOF6'

DS
DS
DS
DS

*

Figure 12-1.

= any

SEND TP
RECEIVE TP
ROUTER DIRECTOR TP
General Server TP

hexadecimal digit

SNA-Defined Service Transaction Programs

Refer to "Chapter 13. SNA Distribution Services" for additional SNADS information
and refer to "Chapter 14. GDS Variables for Gener~l Use" for information about GDS
variables that are not specific to SNA service transaction programs.

Chapter 12.

GDS Variables for SNA Service Transaction Programs

12-1

GDS Variables for SNA STPs

DESCRIPTIONS OF GDS VARIABLES FOR SNA STPS
Change Number of Sessions (X'1210') GDS Variable GDS Variable
0-1
2-3
4

5

6

7

8

9-10

11-12

13-14

15

12-2

Length (17 or n+l), in binary, of Change Number of Sessions GDS variable,
including this Length field
GDS I D: X' 1210'
Service flag:
bits 0-3, reserved
bits 4-7, request/reply indicator:
0010 request
1000 reply, function completed abnormal
1010 reply, function accepted but not yet completed
Reply modifier (reserved if byte 4, bits 4-7 = 0010):
X'OO' normal--no negotiation performed
X'Ol' abnormal--command race detected
X'02' abnormal--mode name not recognized
X'03' reserved
X'04' normal--negotiated reply
X'OS' abnormal--(LU,mode) session limit is 0
Action:
X'OO' set (LU,mode) session limits
X'Ol' reserved
X'02' close
Drain immediacy:
bits 0-2, reserved
bit 3, source LU drain (reserved if byte 6 ~= 02):
o no (send BIS at next opportunity)
1 yes
bits 4-6, reserved
bit 7, target LU drain (reserved if byte 6 ~= 02):
o no (send BIS at next opportunity)
1 yes
Action flags:
bits 0-6, reserved
bit 7, session deactivation responsibility:
o sender of Change Number of Sessions request (source LU)
1 receiver of Change Number of Sessions request (target LU)
Note:
Bytes 9-14 are reserved if byte 6 ~= O.
(LU,mode) session limit:
bit 0, reserved
bits I-IS, maximum (LU,mode) session count, 1n binary
Source LU contention winners:
bit 0, reserved
bits 1-15, guaranteed minimum number of contention W1nner sessions at
source LU, in binary
Target LU contention winners:
bit 0, reserved
bits 1-15, guaranteed minimum number of contention winner sessions at
target LU, in binary
Mode name selection:
bits 0-6, reserved
bit 7, mode names affected by this command:

SNA Formats

GDS Variables for SNA STPs

16
17-n

o a single mode name is affected
1 all mode names are affected
length (values 0 to 8 are valid; reserved if byte 15, bit 7
binary, of mode name
Mode name (omitted if byte 16 = X'OO')

= 1),

in

Exchange Log Name (X'1211') GDS Variable GDS Variable
0-1
2-3

4

5

6
7-n
n+l
n+2-p

length (p+l), in binary, of Exchange log Name GDS variable, including this
length field
GDS ID:
X'1211'
Service flag:
bits 0-3, reserved
bits 4-7, request/reply indicator:
0010 request
1000 reply, function completed abnormally
1001 reply, function completed normally
Sync point manager flags:
bits 0-6, reserved
bit 7, log status:
o cold
1 warm
length (values 1 to 17 are valid), in binary, of network-qualified lU
network name
Network-qualified lU name (format described in "Chapter 7. User Data
Structured Subfields" )
length (values 1 to 64 are valid), in binary, of log name
log name: a type AE symbol string

Chapter 12.

GDS Variables for SNA Service Transaction Programs

12-3

GDS Variables for SNA STPs

Compare states (X'1213') GDS Variable GDS Variable
0-1
2-3

4

5

6
7
8-n
8

8-w
w+l-w+6
w+7w+8(=n)
n+l
n+2-q
q+l
q+2-p

12-4

Length, in binary, of Compare States GDS variable, including this Length
field
GDS ID:
X'l2l3'
Service flag:
bits 0-3, reserved
bits 4-7, request/reply indicator:
0010 request
1000 reply, function completed abnormally
1001 reply, function completed normally
Sync point manager state:
X'Ol' RESET
X'02' SYNC_POINT_MANAGER_PENDING
X'03' IN_DOUBT
X'04' COMMITTED
X'05' HEURISTIC_RESET
X'06' HEURISTIC_COMMITTED
X'07' HEURISTIC_MIXED
Reserved
Length, in binary, of Logical-Unit-of-Work Identifier field (values 10 to
26 are valid)
Logical-Unit-of-Work Identifier
Length, in binary, of network-qualified LU name (values 1 to 17 are valid)
Network-qualified LU name (format described in "Chapter 7. User Data
Structured Subfields")
Logical-unit-of-work instance number, in binary
Logical-unit-of-work sequence number, in binary
Length (values 0 to 8 are valid), in binary, of conversation correlator
Conversation correlator of transaction program that allocated the
conversation that failed:
see FMH-5 for format of this correlator
Length (values 2 to 8 are valid), of session instance identifier
Session instance identifier of session being used by conversation at time
of failure (See "Chapter 7. User Data Structured Subfields" for the format
of this identifier.)

SNA Formats

CHAPTER 13.

SNA DISTRIBUTION SERVICES

INTRODUCTION
This chapter presents the encodings of the SNA Distribution Services (SNADS)
interchange units (IUs) used to transport information and control between the
distribution service units (DSUs).
It has two parts:
•

"Interchange Unit Description" on page 13-2 presents the format and the
semantics of the IUs

•

"Names and Code Points" on page 13-41 presents all the IU code points,
transaction program names, and the server names

The syntax of the IUs follows the Distribution Interchange Architecture:
IUs
contain a prefix, command, object (optionally), and a suffix. The IUs are sent
between DSUs on LU 6.2 conversations. Some of the SNADS IUs may be segmented.

Chapter 13.

SNA Distribution Services

13-1

INTERCHANGE UNIT DESCRIPTION

DISTRIBUTE INTERCHANGE UNIT

DISTIUj DSU ---> DSUj (DISTRIBUTE INTERCHANGE UNIT)
DISTIU carries data and status
more users.

for distribution to one or

DISTIU consists of a sequence of GDS variables as follows:
•
•
•
•

A
A
A
A

prefix
command
distribution object (optional)
suffix

See Figure 13-1 on page 13-3.

13-2

SNA Formats

DISTIU

DISTRIBUTE INTERCHANGE UNIT:

I
Prefix
Command:
GDSID Field

I
Service Description Operands:
Distribution Identifier: Origin RGN, REN, DGN, DEN,
Sequence Number, Date-and-Time, Origin Correlation
Distribution General Options: Distribution Flags,
Destination Hop Count, Service Level Parameters,
Distribution Object Count, Destination TP Name
Feedback Address: RGN, REN, DGN, and DEN
Feedback Options: Service Level, TP Name
Destination Application Parameters
Destination Operands
Distribution Status Operands
Distribution Object:
Prefix: Object Size,
Server Name and Parameters
Object Data
Suffix
1
1

GDS
t------,.

t-I--t-I---t-----t-----t--------.. I

COOl IICI05
II
I
•I
.1
.1
•
II
I GDSI DII GDS ... II GDS ... II GDS ... I

II

I

II

I i + 1 x I I x+ 1

II

o

II
y I Iy+ 1

L - - _ - - ' I II -- - - - ' I

II
z I I z+ 1

1-1- - - - ' I

1 II
j I

1-1- - - - '

II

II

II
II

II

I
I

I

illi+l
jllj+l
kllk+l
pi
____________________________________
I ' - -_ _
___

'--_---'I

~I

Figure 13-1.

Key:

II

• 1-1----,.

I IGDS ... I ICFOI orl
II
IICF02
I
II
II
I

~I

~I

~I

~

Structure of the Distribute IU

"GDS ... " means one or more GDS (Generalized Data Stream) variables.

Note: The identifiers (e.g., COOl, CI05) above are shown to identify portions of
the data stream. The two identifier bytes are always preceded by two length bytes
in the encoded data stream.

Chapter 13.

SNA Distribution Services

13-3

DISTIU
O-i

Prefix
Required GDS variable, identifies the beginning of an interchange unit
(IU)
Length (i+l), in binary, of the GDS variable, including this Length field
(values from 5 to 21 are valid)
Identifier: X'COOl'
Format:
X'02' no segmentation descriptor follows
Interchange unit identifier, optional subfield, a 1- to 16-byte correIa tor
of the sending DSU.
If an error occurs, the receiving DSU returns this
value in an Acknowledge IU; see "Acknowledge Interchange Unit" on page
13-34.
Note:
A particular correlator value is optional and is used by a
send-receive DSU pair; it has no meaning through the entire SNADS network.

0-1
2-3

4
5-i

i+l-j

Command
Required sequence of one or more GDS variables that contains:
•
•
•

i+l-x
i+l-i+2

i+3-i+4
i+5

i+6-i+8
i+6

i+7-i+8

A sequence of Service Description operands
A sequence of Destination operands
A sequence of Distribution Status operands

See Figure 13-1 on page 13-3.
GDSID field
Length ej-i), in binary, of the GDS variable, including this Length field
Note:
The maximum length of the command, including all segments, is 32511
bytes.
Identifier: X'Cl05'
Format:
X'02' no segmentation descriptor follows
X'82' segmentation descriptor follows
Segmentation Descriptor
(present only if Format=X'82')
Position in the command:
X'OO' last or only segment (this is the last or only command segment sent)
X'20' not the last segment of the command eat least one more command
segment follows contiguously on this conversation l )
Segment sequence number:
X'OOOO' segment sequence numbering not used

x=(i+5)lei+8) for i+5 containing X'02'IX'82', respectively
x+l-y

Service Description Operands
Required set of GDS variables containing:
•

Distribution Identifier

SNADS command and distribution object data may be divided into smaller segments
to send across the conversation.
The last segment is sent before any other
different GDS variable is sent.

13-4

SNA Formats

DISTIU
•
•
•
•

Distribution General Options
Feedback Address (optional)
Feedback Options (optional)
Destination Application Parameters (optional)

The above components can be in any order.
See Figure 13-1 on page 13-3.
Note: Throughout the DISTIU and ACKIU presentation, the offset of the
first byte of a subfield is reset to 0 if the subfield can appear in
positions (within the field) different from the position shown in the
offset-stream field description.
O-n

Distribution Identifier
Required GDS variable. It contains the following LT-subfields:

•
•
•
•
•
•
•

Origin
Origin
Origin
Origin
Origin
Origin
Origin

RGN (optional)
REN
DGN
DEN
Sequence number
Date and time
Correlation (optional)

See Figure 13-1 on page 13-3.
0-1

2-3

4

O-nl

o
1
2-nl

0-n2

o
1
2-n2

The LT-subfields can be in any order.

Length (n+l), in binary, of the GDS variable, including this Length field
(values from 28 to 107 are valid)
Note:
The quadruple (origin DGN, origin DEN, Sequence number, Date and
time) is the unique distribution identifier (UDI) in the whole SNADS
network.
Identifier: X'C340'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Origin RGN
Optional LT-subfield
Length (nl+l), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'Ol'
First part of the name of the DSU where DISTIU originated, obtained from
the origin directory (see "Specification of the Character-String Fields"
on page 13-41 for the encoding of the graphic characters used)
Origin REN
Required LT-subfield
Length (n2+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'02'
Second part of the name of the DSU where DISTIU originated, obtained from
the origin directory (see "Specification of the Character-String Fields"
on page 13-41 for the encoding of the graphic characters used)

Chapter 13.

SNA Distribution Services

13-5

DISTIU
0-n3

o
1
2-n3

0-n4

o
1
2-n4

0-5

o
1
2-5

0-9

Origin DGN
Required IT-subfield
length (n3+1), in binary, of the subfield, including this length field
(values from 2 to 10 are valid)
Type:
X' 03'
First part of the distribution user name (DUN) that initiated DISTIU (see
"Specification of the Character-String Fields" on page 13-41 for the
encoding of the graphic characters used); passed by DISTRIBUTE_DATA or
DISTRIBUTE_STATUS verbs
Note:
The name is null (i.e., the length of the IT-subfield is 2) if
DISTIU is a status DISTIU generated by a DSU.
Origin DEN
Required IT-subfield
length (n4+1), ~n binary, of the subfield, including this Length field
(values from 2 to 10 are valid)
Type:
X'04'
Second part of the distribution user name (DUN) that initiated DISTIU (see
"Specification of the Character-String Fields" on page 13-41 for the
encoding of the graphic characters used); passed by DISTRIBUTE_DATA or
DISTRIBUTE_STATUS verbs
Note:
The name is null (i.e., Length of the IT-subfield is 2) if DISTIU
is a status DISTIU generated by a DSU.
Origin Sequence Number
Required LT-subfield
Length (6), in binary, of the subfield, including this Length field
Type:
X'05'
Integer in base 10, 4-numeric EBCDIC encoded character string (values from
'FOFOFOFl' to 'F9F9F9F9' generated by modulo-lOOOO incrementing counter
[with 1, 2, 3, ... , 9999 as states] for DISTIUs of type=DATA, and
'FOFOFOFO' for DISTIUs of type=STATUS), when the distribution verb is
invoked or for STATUS DISTIU, when the feedback is generated
Origin Date and Time

9

Required IT-subfield, contains the date and time generated by SNADS when
the distribution verb was issued.
length (10), in binary, of the subfield, including this length field
Type:
X'06'
Date:
Year, in binary (e.g., year 1983 is encoded as X'07BF')
Month of the year, in binary (values from 1 to 12 are valid)
Day of the month, in binary (values from 1 to 31 are valid)
Time:
Hour of the day, in binary (values from 0 to 23 are valid)
Minute of the hour, in binary (values from 0 to 59 are valid)
Second of the minute, in binary (values from 0 to 59 are valid)
Hundredth of the second, in binary (values from 0 to 99 are valid)

0-n5

Origin Correlation

o
1

2-5
2-3
4
5
6-9
6
7
8

13-6

SNA Formats

DISTIU

2-n5

Optional LT-subfield
Length (n5+l), in binary, of the subfield, including this Length field
(values from 3 to 46 are defined)
Type:
X'07'
String supplied by application transaction programs, not used by SNADS

O-n

Distribution General Options

o
1

Required GDS variable, describes the processing SNADS performs upon the
DISTIU.
It contains the following LT-subfields:
•
•
•
•
•

Distribution Flags
Destination Hop Count
Service Level parameters
Distribution Object Count
Destination TP Name

See Figure 13-1 on page 13-3.
0-1
2-3

4

0-2

o
1

2

2

The LT-subfields can be in any order.

Length (n+l), in binary~ of the GDS variable, including this Length field
(values from 30 to 114 are valid)
Identifier: X'C33D'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Distribution Flags
Required LT-subfield, services indicated specified by the application
transaction
Length (3), in binary, of the subfield, including this Length field
Type:
X'Ol'
Flags:
bit 0, no-feedback request bit:
o SNADS is requested to generate feedback in case of error
1 no SNADS feedback for this DISTIU is requested
bit 1, DISTIU type bit:
o DISTIU is a data distribution
1 DISTIU is a status distribution
bit 2, reserved, DISTIU not rejected whatever its value
'bits 3-7, reserved 2
Note: The functions encoded by the Flags field are described in
Figure 13-2 on page 13-8.

Reserved fields are to be used for later releases; unless specified otherwise,
their values are passed unchanged by the intermediate nodes, and, if not 0,
rejected by the destination nodes.

Chapter 13.

SNA Distribution Services

13-7

DISTIU

Flag
(hex)1
00
80
CO

I
I
I
I

Interpretation of the Flag

Data distribution with feedback
Data distribution with no feedback
status distribution with no feedback

Figure 13-2.

0-3

o
1
2-3

O-nl

o
1

2-4

Interpretation of the Distribution Flags

Destination Hop Count
Required LT-subfield
Length (4), in binary, of the subfield, including this Length field
Type:
X'02'
Number, in binary, of hops that may not be exceeded by DISTIU on its way
toward its destination DSU; set by the DSU where DISTIU originated and
decremented by 1 every time the DISTIU is sent to another DSU.
When its
value is 0 and this DSU is not the final destination of the DISTIU, the
DISTIU has a "hop count" error.
Service Level Parameters
Required LT-subfield, provided by the application transaction program to
describe the requested functions for the DISTIU
length (nl+l), in binary, of the subfield, including this Length field
(values 11, 14, 17, ... 32 are valid)
Type:
X'03'
Priority parameter, priority level to be given to the distribution, 1n
decreasing priority order:
X'OICOFO' FAST priority
X'OICODO' STATUS priority
X'0IC080', ... , X'OICOxx', ... , and X'0IC008' data priority levels, where
'xx' is the value of the priority level DATA_i, and 'xx'=
[(8
i) in hexadecimal]; e.g., 'xx'='80' for i=16, and
'xx'='08' for i=l
Note:
If only two data priorities are honored, then the high data
priority maps to priorities DATA_16 to DATA_9, and the low data priority
to priorities DATA_8 to DATA_I.
Protection parameter, requirement for minimum protection against
distribution losses in the data store:
X'02COI0' no protection required, distribution object can be stored on
volatile storage
X'02C030' protection required, distribution object must be stored on
nonvolatile storage
Capacity parameter, requirement for a route that can provide the storage
of distribution data of specified size:
X'03COOO' NONE capacity, used for DISTIUs without distribution objects
X'03COOC' 4K capacity, used for DISTIUs with distribution objects whose
sizes are smaller than 4096 bytes
X'03EOFF' INDEF capacity, used for DISTIUs with distribution objects whose
sizes are relatively large, for example larger than 4096 bytes

*

5-7

8-10

13-8

SNA Formats

DISTIU
Notes:
1. The capacity requirement is for the distribution object, and does not
include the capacity needed to store and handle the control subfields of
the DISTIU.
For example, the 3K required to handle one distribution
object of 3K byte size is above the storage needed to store the associated
command.
2. The defined values for (priority, protection, capacity) parameters are
shown in Figure 13-3.
3. Implementations may accept other service levels as long as they can
route IUs responsibly.

Service Level Parameter
Comments
Priority

Protection

Capacity

I
I
I
OlCOFO
02COlO
03COOC
Data or Status DISTIU with priority=FAST, I
no protection, and 4K capacity requested I
I
OlCODO
02C030
03COOC
Status DISTIU with priority=STATUS,
I
protected, and 4K capacity requested
I
I
OlCODO
02C030
03COOO
Status DISTIU with priority=STATUS,
I
protected, and no capacity requested
I
I
OlCOxx
02C030
03EOFF
Data DISTIU with priority=DATA-i (see
I
Note) protected, and indefinite capacity I
I
Note: 'xx'=[(8*i)], in hexadecimal, is the priority level
I
corresponding to DATA_i, where i=l, 2, ... , 15, 16.
I
OlCOFO

02COlO

Figure 13-3.

ll-n1

0-2

o
1

2

03COOO

Data or Status DISTIU with priority=FAST,
no protection, and no capacity requested

Priority, Protection, and Capacity Subfield Values

Optional Service Level Parameters
An optional stream of up to 7 3-byte fields with the following structure:
Optional parameter
Parameter identifier: any value larger than X'03'
Comparison operator:
X'OO'-'OF' optional request, ignored by a receiving product in the
intermediate role that allows the transfer of the DISTIU
~ X'lO' mandatory request, if not recognized by a product results in the
"function not supported" error condition, and the DISTIU is rejected
Parameter value:
defined by each product, refer to its specifications for
the definition of the field

Chapter 13.

SNA Distribution Services

13-9

DISTIU
0-3

o
1
2-3

0-n2

o
1

2-n2

O-n

Distribution Object Count
Required IT-subfield
length (4), in binary, of the subfield, including this length field
Type:
X'04'
Number, in binary, of distribution objects present in this DISTIU (values
o and 1 defined)
Destination TP Name

---

Required IT-subfield
length (n2+1), in binary, of the subfield including this length field
(values from 3 to 66 are valid)
Type:
X'05'
Name of the transaction program started by the destination DSU after the
DISTIU is enqueued for delivery (see "Specification of the
Character-String Fields" on page 13-41 for the encoding of the graphic
characters used)
Feedback Address
Optional GDS variable, valid only if DISTIU type is DATA, contains:
•
•
•
•

0-1
2-3
4

O-nl

o
1
2-nl

0-n2

o
1

2-nl

13-10

Feedback
Feedback
Feedback
Feedback

RGN (optional)
REN
DGN
DEN

The IT-subfields can be in any order.
See Figure 13-1 on page 13-3.
length (n+l), in binary, of the GDS variable, including this length field
(values 14 to 45 are valid)
Identifier: X'C360'
Format:
X'41' no segmentation descriptor follows; contains IT-subfields
Feedback RGN
Optional IT-subfield
length, in binary, of the subfield, including this length field (values
from 3 to 10 are valid)
Type:
X' 01'
First part of the name of the DSU where the feedback is requested to be
sent (see "Specification of the Character-String Fields" on page 13-41 for
the encoding of the graphic characters used)
Feedback REN
Required IT-subfield
length (n2+1), in binary, of the subfield, including this length field
(values from 3 to 10 are valid)
Type:
X'02'
Second part of the name of the DSU where the feedback is requested to be
sent (see "Specification of the Character-String Fields" on page 13-41 for
the encoding of the graphic characters used)

SNA Formats

DISTIU
0-n3

o
1
2-n3

0-n4

o
1
2-n4

O-n

Feedback DGN
Required LT-subfield
length (n3+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'03'
First part of the distribution user name (DUN) to whom feedback is
requested to be sent (see "Specification of the Character-String Fields"
on page 13-41 for the encoding of the graphic characters used)
Feedback DEN
Required LT-subfield
Length (n4+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'04'
Second part of the distribution user name (DUN) to whom feedback is
requested to be sent (see "Specification of the Character-String Fields"
on page 13-41 for the encoding of the graphic characters used)
Feedback Options
Optional GDS variable, valid only if the distribution is of type DATA,
defined by the application transaction to specify the functions needed for
the feedback DISTIU, containing:
•
•

0-1
2-3

4

0-n1

o
1

2-4

5-7

Feedback Service Level (optional)
Feedback TP Name (optional)

See Figure 13-1 on page 13-3. The LT-subfields can be in any order.
Length (n+l), in binary, of the GDS variable, including this Length field
(values 8 to 103 are valid)
Identifier: X'C343'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Feedback Service Level
Optional LT-subfield.
If omitted, the service level of the feedback
DISTIU is calculated as follows:
The priority is FAST if this DISTIU has
priority FAST, the priority is STATUS for other priorities, the protection
is the same as the protection of this DISTIU, and the capacity is 4K or
NONE.
Length (nl+l), in binary, of the subfield, including this Length field
(values 11, 14, 17, ... 32 are valid)
Type:
X'Ol'
Feedback priority parameter, priority level to be given to the feedback
DISTIU, in decreasing priority order:
X'OlCOFO' FAST priority
X'OlCODO' STATUS priority
Feedback protection parameter, requirement for m1n1mum protection against
feedback distribution object losses in the data store:
X'02COIO' no protection required, feedback distribution object can be
stored on volatile memory

Chapter 13.

SNA Distribution Services

13-11

DISTIU
X'02C030' protection required, feedback distribution object must be stored
on nonvolatile memory
Feedback capacity parameter, requirement for a route that can provide the
storage of feedback distribution data of specified size:
X'03COOO' NONE capacity, used for DISTIUs without feedback distribution
objects
X'03COOC' 4K capacity, used for DISTIUs with feedback distribution objects
whose sizes are smaller than 4096 bytes

8-10

Note:
The feedback capacity requirement 1S for the distribution object
and does not include the capacity needed to store and handle the control
subfields of the feedback DISTIU.
The defined values for the feedback priority, feedback protection, and
feedback capacity parameters are shown in Figure 13-4.

Feedback Service Level Parameter
Comments
Priority

Protection

Capaci ty

OlCOFO

02C010

03COOO

Feedback with priority=FAST, no protection and no capacity requested

01COFO

02C010

03COOC

Feedback with priority=FAST, no protection and 4K capacity requested

01CODO

02C030

03COOC

Feedback with priority=STATUS, protected,
and 4K capacity requested

01CODO

02C030

03COOO

Feedback with priority=STATUS, protected,
and no capacity requested

Figure 13-4.

11-n1

0-2

o
1

2

0-n2

13-12

Feedback Priority, Protection, and Capacity Subfield Values

Feedback Optional Service Level Parameter
An optional stream of up to seven 3-byte fields with the following
structure:
Optional parameter
Parameter identifier: any value larger than X'03'
Comparison operator:
X'OO'-'OF' optional request, is ignored by a receiving product in the
intermediate role that allows the transfer of the DISTIU
~ X'lO' mandatory request, if not recognized by an implementation, results
in the "function not supported" error condition, and the DISTIU is
rejected
Parameter value: defined by product; refer to its specifications for the
definition of the field
Feedback TP Name

SNA Formats

DISTIU

o
1

2

O-n

0-1
2-3

4
S-n

y+1

Optional LT-subfie1d; if omitted the transaction application program to be
started after the feedback is queued for delivery is given by the
Destination TP Name within Distribution General Options GDS variable
Length (n2+1), in binary, of the subfield, including this Length field
(values from 3 to 66 are valid)
Type:
X'02'
Name of the application transaction program to be started after the
feedback is queued for delivery (see "Specification of the
Character-String Fields" on page 13-41 for the encoding of the graphic
characters used)
Destination Application Parameters (see Figure 13-1 on page 13-3)
Optional GDS variable
Length (n+1), in binary, of the GDS variable, including this Length field
(values from 6 to S17 are valid)
Identifier: X'C32D'
Format:
X'Ol' no segmentation descriptor follows
Parameters supplied by the application transaction program that invoked
the distribution verb and passed as a returned parameter when
RECEIVE_DISTRIBUTION is issued
replaced by bl
Notes:
1. Offset y+1 will be replaced by bl in order to simplify the stream
description.
2. Offsets bi and ei+l are used for the first byte of the beginning and
the end of a list, as it follows:
bl, el+l for Destination operands, b2,
e2+1 for REN List, b3, e3+1 for DGN List, and b4, e4 for DEN List.

b1-e1+S

Destination Operands
List of destinations of the DISTIU, no larger than 2S6 destinations if
DISTIU is of type DATA and exactly one destination if the DISTIU is of
type STATUS, encoded as a list of factored lists of DUNs and DSUNs.
The
identical RGNs, RENs, and DGNs are factored out of the Destination
operands, REN, and DGN lists. The Destination operands list may be fully
factored, partially factored, or unfactored (see the following example).
Example:
Following is a list of destinations (qualified by
RGN.REN.DGN.DEN):
A.K.DA.U1, A.K.DA.U2, A.K.DB.U3, A.K.DB.U4,
A.L.DC.US, A.L.DC.U6, A.L.DD.U7, A.L.DD.U8,
B.M .. DE.U9, B.M.DE.UIO, B.M.DF.Ull, B.M.DF.U12,
B.N.DG.U13, B.N.DG.U14, B.N.DH.U1S, and B.N.DH.U16.
The list may appear factored in Destination operands as follows:
•

completely factored:
(A(K(DA(U1 U2) DB(U3 U4))

Chapter 13.

SNA Distribution Services

13-13

DISTIU
LCDCCU5 U6) DDCU7 U8»)
BCM(DECU9 UI0) DFCUll UI2»
NCDGCU13 U14) DHCU15 UI6»))
•

partially factored:
CACKCDACUl) DACU2) DBCU3 U4»
LCDCCU5 U6» LCDDCU7 U8»)
BCMCDECU9 UI0) DFCU11 U12»
NCDGCU13» NCDGCU14) NCDHCU15 UI6»)

•

not factored~ equivalent to the initial list:
CACKCDACUl)) ACKCDACU2))) ACKCDBCU3»)) ACKCDBCU4»)) ACLCDCCU5»)
ACLCDCCU6») ACLCDDCU7») ACLCDDCU8)) BCMCDECU9») BCMCDECUI0»)
BCMCDFCU11») BCMCDFCUI2)) BCNCDGCUI3») BCNCDGCU14») BCNCDH(U15))
BCNCDHCU16»»

In the above lists~ "(" and ")" represent the beginning and the end of a
1ist~ respectively.
CInner parentheses have precedence over outer
parentheses.)
End of Example
The Destination operands are a required sequence of:
•
•
•

Beginning of Destination operands field
Sequence of pairs of RGN and REN List Csee Figure 13-6 on page 13-16)
End of Destination operands field

See Figure 13-1 on page 13-3 and Figure 13-5 on page 13-15.

13-14

SNA Formats

DISTIU

Destination Operands
1

Beginning
RGN
1

End
REN List

1

1
1

GDS ...
1

I

j

I

1

1

IC35l

1

1
1

IC3501
IC3521
1
1
1
1
1
1
1
1

1

1

Ibl+8

1

1 1-1------.
1 1C352
1 1
1 1bl+8 bl+n 1

I

1GDS ... 1
1
1
Ib2 e2+51

1

I· . ·1

1
1
e2+51

1

I
1

bl=y+l

el+5=z

Figure 13-5.

b1-bl+7

Structure of the Destination Operands

Beginning of Destination Operands

Required GDS variable
bl-bl+l
Length (8), in binary, of the GDS variable, including this Length field
bl+2-bl+3 List beginning identifier: X'C350'
bl+4
Format:
X'OI' no segmentation descriptor follows; does not contain LT-subfields
bl+5-bl+6 RGN identifier: X'C352'
bl+7
Format:
X'OI' no segmentation descriptor follows
Note:
RGN and REN List (the stream from offset bl+8 through e2+5) may be
repeated.
bl+8-b1+n RGN
Required GDS variable; its content may be null
bl+8-b1+9 Length (n+l), in binary, of the GDS variable, including this Length field
(values from 5 to 13 are valid)
b1+10-b1+l1 Identifier:
X'C352'
b1+l2
Format:
X'01' no segmentation descriptor follows; does not contain LT-subfields
b1+l3-b1+n First part of the destination DSU name obtained from the origin directory
(see "Specification of the Character-String Fields" on page 13-41 for the
encoding of the graphic characters used)
b2-e2+5

REN List

Chapter 13.

SNA Distribution Services

13-15

DISTIU
Required sequence of:
•
•
•

Beginning of REN List
Sequence of pairs of REN and DGN list (see Figure 13-7 on page 13-17)
End of REN list

See Figure 13-6 and Figure 13-5 on page 13-15.

REN List

I
Beginning
REN

I
GDS ...

I

I

I

IC3501
IC3531

I

I
I
I
I
I

I
I
I
I
I

II.--- - - - - ,
I I C353

I I
I I b2+8 b2+n I

I
Ib2+8

b2

Figure 13-6.

b2-b2+7

Structure of the REN List

Beginning of REN List

Required GDS variable
b2-b2+1
Length (8), in binary, of the GDS variable, including this Length field
b2+2-b2+3 List beginning identifier: X'C350'
b2+4
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
b2+5-b2+6 REN identifier: X'C353'; with X'C350' represents the identifier of the
Beginning of REN List
b2+7
Format:
X'Ol' no segmentation descriptor follows
Note:
REN and DGN List (the stream from offset b2+8 through e3+5) may be
repeated.
b2+8-b2+n REN
Required GDS variable

13-16

SNA Formats

DISTIU
b2+8-b2+9 Length (n+1), in binary, of the GDS variable, including this Length field
(values from 6 to 13 are valid)
b2+10-b2+11 Identifier: X'C353'
b2+12
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
b2+13-b2+n Second part of the destination DSU name obtained from the origin
directory (see "Specification of the Character-String Fields" on page
13-41 for the encoding of the graphic characters used)
b2+n+1
Note:
Offset b2+n+1 will be replaced by b3 in order to simplify the
stream description
b3-e3+5

DGN List
Required sequence of:
•
•
•

Beginning of DGN List
Sequence of pairs of DGN and DEN List (see Figure 13-8 on page 13-19)
End of DGN List

See Figure 13-6 on page 13-16 and Figure 13-7.

DGN List

I
Beginning
DGN

I

End
DEN List

I

I
I

b3-b3+7

Beginning of DGN List

b3-b3+1

Required GDS variable
Length (8), in binary, of the GDS variable, including this Length field

Chapter 13.

SNA Distribution Services

13-17

DISTIU
b3+2-b3+3 List beginning identifier: X'C350'
b3+4
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
b3+5-b3+6 DGN identifier: X'C354'; with X'C350' represents the identifier of the
Beginning of the DGN List
b3+7
Format:
X'Ol' no segmentation descriptor follows
Note:
DGN and DEN list (the stream from offset b3+8through e4+5) may be
repeated
b3+8-b3+n DGN
Required GDS variable
b3+8-b3+9 Length, in binary, of the GDS variable, including this Length field
(values from 6 to 13 are valid)
b3+10-b3+11 Identifier:
X'C354'
b3+12
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
b3+13-b3+n First part of the destination distribution user name (see "Specification
of the Character-String Fields" on page 13-41 for the encoding of the
graphic characters used).
It is provided either in the DESTINATION_DUN
parameter of the DISTRIBUTE_DATA or DISTRIBUTE_STATUS verb, if DISTIU was
generated by the issue of the DISTRIBUTE_DATA or DISTRIBUTE_STATUS verb,
or in the Feedback DGN subfie1d (or the Origin DGN subfield if Feedback
Address is missing) of the DISTIU for which the feedback was generated, if
this DISTIU is a feedback.
b3+n+1
Note:
Offset b3+n+1 will be replaced by b4 in order to simplify the
stream description.
b4-e4+5

DEN List
Required sequence of:
•
•
•

Beginning of DEN List
Sequence of DENs
End of DEN List

See Figure 13-7 on page 13-17 and Figure 13-8 on page 13-19.

13-18

SNA Formats

DISTIU

DEN list

I
Beginning

I

DEN

End

I

I

IC355

IC351

I

I

I

IGDS ...

I

I

I
I

I C350 I
I C3551

I

I
e4+51

Ib4

Figure 13-8.

b4-b4+7

Structure of the DEN list

Beginning of DEN list

Required GDS variable
b4-b4+1
length (8), in binary, of the GDS variable, including this length field
b4+2-b4+3 list beginning identifier: X'C350'
b4+4
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
b4+5-b4+6 DEN identifier:
X'C355'; with X'C350' represents the identifier of the
beginning of the DEN list
b4+7
Format:
X'Ol' no segmentation descriptor follows
Note:
DEN GDS variable (the stream from offset b4+8 through e4) may be
repeated.
b4+8-b4+n DEN
Required GDS variable
b4+8-b4+9 length, in binary, of the GDS variable, including this length field
(values from 6 to 13 are valid)
b4+10-b4+11 Identifier:
X'C355'
b4+12
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
b4+13-b4+n Second part of the destination distribution user name (see "Specification
of the Character-String Fields" on page 13-41 for the encoding of the
graphic characters used).
It is provided either in the DESTINATION_DUN
parameter of DISTRIBUTE_DATA or DISTRIBUTE_STATUS verb, if DISTIU was
generated by the issue of the DISTRIBUTE_DATA or DISTRIBUTE_STATUS verb,
or in the Feedback DEN subfield (or the Origin DEN subfield if Feedback
Address is missing) of the DISTIU for which the feedback was generated, if
this DISTIU is a feedback.
e4+l-e4+5 End of DEN list

Chapter 13.

SNA Distribution Services

13-19

DISTIU
Required GDS variable
e4+1-e4+2 Length (5), in binary, of the GDS variable, including this Length field
e4+3-e4+4 Identifier: X'C351'
e4+5
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
e3+1-e3+5 End of DGN list
Required GDS variable
e3+1-e3+2 Length (5), in binary, of the GDS variable, including this Length field
e3+3-e3+4 Identifier: X'C351'
e3+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
e2+1-e2+5 End of REN List
Required GDS variable
e2+1-e2+2 length (5), in binary, of the GDS variable, including this length field
e2+3-e2+4 Identifier: X'C351'
e2+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
el+1-e1+5 End of Destination Operands
Required GDS variable
el+l-e1+2 length (5), in binary, of the GDS variable, including this Length field
el+3-el+4 Identifier: X'C35l'
el+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields

z
Note:
Offset z will replace e1+5 1n order to simplify the stream
description.
z+l-j

Distribution Status Operands
Required and allowed if and only if DISTIU is of type STATUS (i.e., the
value of bit 1 of Distribution Flags of Distribution General Options is
1.).
It may include SNADS status, application status, or both, along with
fields to identify DISTIU for which the status is being reported and
transported to the originator or its designate, sequence of:
•
•
•
•

Status operands
General SNADS Status (optional)
General Application Status (optional)
Specific Status

See Figure 13-1 on page 13-3 and Figure 13-9 on page 13-21.

13-20

SNA Formats

DISTIU

Distribution Status Operands
Status Operands

I
I
I

Status Correlation: Origin DGN, DEN, Sequence Number,
I Date and Time, Correlation
Receiving DSUN:

RGN, REN

General SNADS Status

I
I

Status Type

I
I

Status Contents

General Application
I Status: Type
and Contents
Specific
Status

GDS ...

I

I
GDS ...

GDS ...

I

ilr----~

IC340
IIC361 I
111111111111111.11
1101101101101101111011011
1131141151161171111111211

I L...J

L...J L...J L...J L...J

I'

I I L...J
III

L...-_ _ _ _ _ _-..JI1

sl=z+l

L...J

I

II
s2

h
ICI
131
151
161
I I
I I

I
IC357 I
111111
110 II 0 II
11111211
I L..J L...J I
I
I

L...J

I

52+1

I

s3

z+l

GDS ...
1111
ICIICI
131131
151151
161171
I II I
I II I

GDS ...

L...J L...J

s3+1

s4

s4+1 s5
j=s5

Figure 13-9.

Distribution Status

Operand~

Structure

z+l
Note: Offset z+l will be replaced by sl in order to simplify the stream
description. Offsets sl, s2, s3, s4, and s5 are used to describe the
Distribution Status operands stream.
51-52

Status Operands
Required set of:

Chapter 13.

SNA Distribution Services

13-21

DISTIU
•
•

Status Correlation
Receiving DSUN (optional)

The above components can be in any order.
and Figure 13-9 on page 13-21.

O-n

See Figure 13-1 on page 13-3

Status Correlation
Required GDS variable, contains LT-subfields with information to identify
the DISTIU for which status information (provided either by SNADS if this
DISTIU is generated by SNADS, or by the application transaction if DISTIU
is generated through the issue of DISTRIBUTE_STATUS) is reported:

•
•
•
•
•

Origin
Origin
Origin
Origin
Origin

DGN
DEN
Sequence Number
Date and Time
Correlation (optional)

See Figure 13-9 on page 13-21.
0-1
2-3

4

0-n1

o
1

2-nl

0-n2

o
1

2-n2

The LT-subfields can be in any order.

Length (n+l), in binary, of the GDS variable, including this length field
(values from 27 to 87 are valid)
Identifier: X'C340'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Origin DGN
Required LT-subfield
Length (nl+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'03'
First part of the distribution user name (DUN) that initiated the
data-DISTIU for which this status-DISTIU is returned (see "Specification
of the Character-String Fields" on page 13-41 for the encoding of the
graphic characters used)
Origin DEN
Required LT-subfield
Length (n2+1), in binary, of the subfie1d, including this Length field
(values from 3 to 10 are valid)
Type:
X'04'
Second part of the distribution user name (DUN) that initiated the
data-DISTIU for which this status-DISTIU is returned (see "Specification
of the Character-String Fields" on page 13-41 for the encoding of the
graphic characters used)

0-5

Origin Sequence Number

o

Required LT-subfield
Length (6), in binary, of the subfield, including this Length field
Type:
X'05'

1

13-22

SNA Formats

DISTIU
2-5

Integer in base 10, 4-numeric EBCDIC-encoded character string (values from
X'FOFOFOFl' to X'F9F9F9F9'), equal to the corresponding subfield in the
Distribution Identifier of the data distribution for which this DISTIU is
returned

0-9

Origin Date and Time

1
2-5
2-3
4
5
6-9
6
7
8
9

Required LT-subfield, equal to the corresponding subfield in the
Distribution Identifier of the data-DISTIU for which this DISTIU is
returned (see Figure 13-1 on page 13-3)
Length (10), in binary, of the subfield, including this Length field
Type:
X'06'
Date:
Year, in binary (e.g., year 1983 is encoded as X'07BF')
Month of the year, in binary (values from 1 to 12 are valid)
Day of the month, in binary (values from 1 to 31 are valid)
Time:
Hour of the day, in binary (values from 0 to 23 are valid)
Minute of the hour, in binary (values from 0 to 59 are valid)
Second of the minute, in binary (values from 0 to 59 are valid)
Hundredth of the second, in binary (values from 0 to 99 are valid)

0-n3

Origin Correlation

o

o
1

2-n3

O-n

Optional LT-subfield, equal to the corresponding subfield in the
Distribution identifier of the data-DISTIU for which this status-DISTIU
returned.
Length (n3+1), in binary, of the subfield, including this Length field
(values from 3 to 46 defined)
Type:
X' 07'
Origin Correlation, byte string generated and used by application
transaction program

1S

Receiving DSUN
Optional GDS variable if this status-DISTIU is returned because of receive
time errors.
It contains the name of the receiving DSU if the
transmission error was detected by the receiving DSU.
•
•

0-1
2-3
4

O-nl

Receiving RGN (optional)
Receiving REN

See Figure 13-9 on page 13-21. The positions of its two LT-subfields are
arbitrary.
Length (n+l), in binary, of the GDS variable, including this Length field
(values from 8 to 25 are valid)
Identifier: X'C361'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Receiving RGN
Optional LT-subfield

Chapter 13.

SNA Distribution Services

13-23

DISTIU

o
1

2-nl

0-n2

o
1
2-n2

Length (nl+l), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'OI'
First part of the name of the DSU that detected the receive-time error
(see "Specification of the Character-String Fields" on page 13-41 for ~he
encoding of the graphic characters used)
Receiving REN
Required LT-subfield
Length (n2+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'02'
Second part of the name of the DSU that detected the receive-time error
(see "Specification of the Character-String Fields" on page 13-41 for the
encoding of the graphic characters used)

s2+1-s4

General Status
Note:
New SNADS DSUs will not generate both General SNADS Status and
General Application Status in a single IU.
However, older SNADS DSUs may
generate both SNADS and Application General Status fields in a single lU,
and all SNADS DSUs receive such IUs without error.
DSUs may ignore the
General Application Status field if General SNADS Status is present.

s2+1-s3

General SNADS Status
Optional pair (elements in required order) of GDS variables, used if
Specific SNADS status in Specific Status is missing, describes the SNADS
status applicable to all DUNs in the Specific Status when no SNADS status
is indicated along with them (i.e., Specific SNADS Status elements
[described in the stream from offset s2+1 up to s3 below within Specific
Status subfield] are missing):
•
•

Status Type
Status Contents

See Figure 13-9 on page 13-21.
s2-s2+6

Status Type

Required GDS variable
s2-s2+l
Length (7), in binary, of the GDS variable, including this Length field
s2+2-s2+3 Identifier: X'C356'
s2+4
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
s2+5-s2+6 Status type:
X'OOOl' for SNADS Status
s2+7-s3

Status Contents

Required GDS variable; it contains the SNADS Condition Code
s2+7-s2+8 Length, in binary, of the GDS variable, including this Length field (value
is 9)
s2+9-s2+10 Identifier: X'C357'

13-24

SNA Formats

DISTIU
s2+ll

Format:
X'4l' no segmentation descriptor follows; contains LT-subfields

s2+l2-s2+l5 SNADS Condition Code
Required LT-subfield
Length (4), in binary, of the subfield, including this Length field
s2+l2
s2+l3
Type:
X'Ol'
s2+l4-s2+l5 Values are listed in Figure 13-10.

0000, OOOA, OOOB, and 0014 up to FFFF

Figure 13-10.

s3+1-s4

are reserved

SNADS Status Condition Codes

General Application Status
Optional pair (elements in required order) of GDS variables, describes the
application status applicable to all DUNs in the Specific Status (the
interpretation of both general and specific application status information
is defined by the application):
•
•

Status Type
Status Contents

s3+l-s3+7 Status Type
Required GDS variable
s3+l-s3+2 Length (7), in binary, of the GDS variable, including this Length field

Chapter 13.

SNA Distribution Services

13-25

DISTIU
53+3-53+4 Identifier: X'C356'
53+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
s3+6-s3+7 Status type:
not equal to X'OOOl'; see "Status Type Codes" on page 13-44
s3+7-s4

Status Contents

Required GDS variable
s3+7-s3+8 length, in binary, of the GDS variable, including this length field
(values from 7 to 69 are valid)
Note:
Older SNADS DSUs may generate IUs with lengths of up to 517. All
SNADS DSUs receive such IUs without error.
However, DSUs may modify such
IUs to force the length to be 69 or less.
s3+9-s3+10 Identifier: X'C357'
s3+11
Format:
X'41' no segmentation descriptor follows; contains IT-subfields
s3+12-s4
s4+5

Status content, application defined bit string
Note:
The Specific Status has a
Destination operands; the offset
respectively.
Offsets b3, e3+1,
DGN and DEN lists beginnings and

b3-e3+5

list structure similar to DGN list of
s4+5 and j are replaced by b3 and e3+5
and b4, e4+1 point to the corresponding
ends.

Specific Status
Required sequence of GDS variables (see Figure 13-9 on page 13-21 and
Figure 13-11 on page 13-27), lists all the names of the recipient users of
the distribution for whom the DISTIU reports the status, along with SNADS
and/or application status information. It is structured as a DGN list:
•
•
•
•

13-26

DGN list Beginning
DGN
DEN list (see Figure 13-12 on page 13-28)
End list

SNA Formats

DISTIU

Specific Status

1
DGN List Beginning

1
DGN
I

GDS ...
/
I
IC350/
IC3541
I
I
I
/
I
I
I
I
I
I

List End

DEN List
I

I

I

I
I I
I
1
I IC354
I I
1
I /b3+8 b3+nl
I
Ib3+8

/
I
IGDS ...
I
/b4 e4+5/

1

I
I·
I
I
e4+5/

I
/C351
I
I

·1

I
I
I
e3+5

b3

Figure 13-11.

b3-b3+7

Structure of the DGN List of Specific Status

DGN List Beginning

Required GDS variable
b3-b3+1
Length (8), in binary, of the GDS variable, including this Length field
b3+2-b3+3 List beginning identifier: X'C350'
b3+4
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
b3+5-b3+6 DGN identifier:
X'C354'
b3+7
Format:
X'Ol' no segmentation descriptor follows
Note:
DGN and DEN list (the stream from offset b3+8 through e4+5) can be
repeated.
b3+8-b3+n DGN
Required GDS variable
b3+8-b3+9 Length (n+l), in binary, of the GDS variable, including this Length field
(values from 5 to 13 are valid)
b3+10-b3+11 Identifier:
X'C354'
b3+12
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
b3+13-b3+n First part of the distribution user name of one of the intended
recipients of the distribution (see "Specification of the Character-String
Fields" on page 13-41 for the encoding of the graphic characters used)
b3+n+l

Chapter 13.

SNA Distribution Services

13-27

DISTIU
Note: Offset b3+n+1 will be replaced by b4 in order to simplify the
stream description.
b4-e4+5

DEN list
Required sequence of:

•
•
•
•
•

DEN list Beginning
DEN
Specific SNADS Status (optional)
Specific Application Status (optional)
List End

See Figure 13-11 on page 13-27 and Figure 13-12.

DEN List

I
DEN list Beginning

I
DEN

I
Specific SNADS
I Status: type,
contents

Specific Application
I Status: type,
contents

I
I
I

GDS

I I
ICI
131
151
151
I I
I I
I I
I I

GDS ...

L-...J

s2+1

t-----.

GDS ...

11

I

r-1

r-1

ICI
131
151
161
I I
I I

IC357
I Illl
I 10 110 I
I 111121
I L-...J L-...J

ICI
131
151
161
I I
I I

ICI
131
151
171
I I
I I

L-...J

L....J

I

L-...J

s3

s3+1

s4

b4

I
I
IC3511
I
I
I
I
I
I
I
I
I
I
I
I

I

I

L---J

e4+5

Figure 13-12.

b4-b4+7

I
I
I

h
C350
C355

List End

Structure of the DEN list of Specific Status

DEN List Beginning

Required GDS variable
b4-b4+1
length (8), in binary, of the GDS variable, including this length field
b4+2-b4+3 list beginning identifier: X'C350'

13-28

SNA Formats

DISTIU
b4+4

Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
b4+5-b4+6 DEN identifier: X'C355'
b4+7
Format:
X'Ol' no segmentation descriptor follows
Note:
DEN GDS variable (the stream from offset b4+8 through e4) may be
repeated.
b4+8-b4+n DEN
Required GDS variable
b4+8-b4+9 Length (n+l), in binary, of the GDS variable, including this length field
(values from 5 to 13 are valid)
b4+10-b4+11 Identifier: X'C355'
b4+12
Format:
X'OI' no segmentation descriptor follows; does not contain IT-subfields
b4+13-b4+n Second part of the distribution user name of one of the intended
recipients of the distribution (see "Specification of the Character-String
Fields" on page 13-41 for the encoding of the graphic characters used)
Note:
DGN is null if and only if DEN is null.
In this case, this null
addressee (i.e., DGN and DEN null) is the only addressee permitted.
DGN
and DEN are null if either the General or Specific SNADS Status subfields
are present with the SNADS Condition Code X'OOOD', or if either the
General or Specific Application Status of type X'FEFF' are present.
b4+n
Note:

Offset b4+n is replaced by s2.

s2+1-s4

Specific Status
Note:
New SNADS DSUs will not generate both Specific SNADS Status and
Specific Application Status for a single destination.
However, older
SNADS DSUs may generate both SNADS and Application Specific Status fields
for a single destination, and all SNADS DSUs receive such IUs without
error.
DSUs may ignore the Specific Application Status field if Specific
SNADS Status is present.

s2+1-s3

Specific SNADS Status
Optional pair (elements in required order) of GDS variables, used if
General SNADS Status information does not apply to this DUN:
•
•

s2-s2+6

Status Type
Status Contents

Status Type

Required GDS variable
s2-s2+1
Length (7), in binary, of the GDS variable, including this length field
s2+2-s2+3 Identifier: X'C356'
s2+4
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
s2+5-s2+6 Status type:
X'OOOl' for SNADS Status

Chapter 13.

SNA Distribution Services

13-29

DISTIU
s2+7-s3

Status Contents

Required GDS variable; it contains the SNADS Condition Code
s2+7-s2+8 length, in binary, of the GDS variable, including this length field (value
is 9)
s2+9-s2+l0 Identifier: X'C357'
s2+11
Format:
X'41' no segmentation descriptor follows; contains IT-subfields
s2+12-s2+15 SNADS Condition Code
Required IT-subfield
s2+12
length (4), in binary, of the subfie1d, including this length field
s2+13
Type:
X'Ol'
s2+14-s2+15 Values are listed in Figure 13-10 on page 13-25.
s3+1-s4

Specific Application Status
Optional pair (elements in required order) of GDS variables, (the
interpretation of both general and specific application status information
is defined by the application):
•
•

Status Type
Status Contents

s3+1-s3+7 Status Type
Required GDS variable
s3+1-s3+2 length (7), in binary, of the GDS variable, including this length field
s3+3-s3+4 Identifier: X'C356'
s3+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
s3+6-s3+7 Status type:
not equal to X'OOOl', sea "Status Type Codes" on page 13-44
s3+7-s4

Status Contents

Required GDS variable
s3+7-s3+8 length, in binary, of the GDS variable, including this length field
(values from 7 to 69 are valid)
Note:
Older SNADS DSUs may generate IUs with lengths of up to 517. All
SNADS DSUs receive such IUs without error.
However, DSUs may modify such
IUs to force the length to be 69 or less.
s3+9-s3+10 Identifier: X'C357'
s3+11
Format:
X'41' no segmentation descriptor follows; contains IT-subfields
s3+12-s4

Status content:

application-defined bit string

e4+1-e4+5 DEN list End
Required GDS variable
e4+1-e4+2 length (5), in binary, of the GDS variable, including this length field

13-30

SNA Formats

DISTIU
e4+3-e4+4 Identifier:
X'C35l'
e4+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
e3+1~e3+5

DGN list End

Required GDS variable
e3+1-e3+2 length (5), in binary, of the GDS variable, including this length field
e3+3-e3+4 Identifier: X'C35l'
e3+5
Format:
X'Ol' no segmentation descriptor follows; does not contain IT-subfields
j

Note:
j+l-k

Offset e3+5 is replaced by j.

Distribution Object
Optional sequence of GDS variables (required order), containing:
•
•

Distribution Object Prefix
Data

See Figure 13-1 on page 13-3.
j+l-j+n

Distribution Object Prefix
Required GDS variable containing:
•
•
•

j+l-j+2
j+3-j+4
j+5

0-9

o
1

2-9

O-nl

o
1

2-nl

Object Size (optional)
Server Name
Server Parameters (optional)

length (n), in binary, of the subfield, including this length field
(values from 8 to 336 are valid)
Identifier: X'C90A'
Format:
X'4l' no segmentation descriptor follows; contains IT-subfields
Object Size
Optional IT-subfield
length (10), in binary, of the subfield, including this length field
Type:
X'Ol'
Unsigned number of bytes, in binary, of all the segments of the
distribution object; need not be accurate
Server Name
Required IT-subfield
length, in binary, of the subfield, including this length field (values
from 3 to 66 are valid)
Type:
X'02'
Name of the server to be used at the destination to store the Data GDS
variable; supplied as a parameter of the DISTRIBUTE_DATA or

Chapter 13.

SNA Distribution Services

13-31

DISTIU
DISTRIBUTE_STATUS verb (see "Specification of the Character-String Fields"
on page 13-41 for the encoding of the graphic characters used)
O-n2

o
1

2-n2

Server Parameters
Optional LT-subfield
Length, in binary, of the subfield l includi'ng this Length field (values
from 3 to 255 are valid)
Type:
X'03'
Stream of bytes representing the values of the parameters to be used by
the destination server; supplied as a parameter of the DISTRIBUTE_DATA or
DISTRIBUTE_STATUS verb

j+n+l

Replaced by b
Note:
The stream from offset b through e may be repeated.

b-e

Data

b-b+l

b+2-b+3
b+4

b+5-b+7
b+5

b+6-b+7
q

q-e
e

k+l-p

k+l-k+2
k+3-k+4

13-32

Required sequence of one or more GDS variables
Length, in binarYI of the GDS variablel including this Length field
(values from 6 to 32511 are valid if there is no segmentation descriptor;
values from 9 to 32511 are valid if there is a segmentation descriptor and
if this is not the last segment, or if this segment is the only segment;
values from 8 to 32511 are valid if there is a segmentation descriptor,
and if this is the last and not the only segment)
Identifier: X'C908'
Format:
X'OI' no segmentation descriptor follows; does not contain LT-subfields
X'81' segmentation descriptor follows; does not contain LT-subfields
Segmentation Descriptor
Position of this GDS variable in the Data field
X'OO' last or only segment (this is the last or only segment sent)
X'20' not the last segment of the Data field (at least one more segment
follows contiguously on this conversation)
Segment sequence number:
X'OOOO' segment sequence numbering not used
q = (b+5)I(b+8) for b+4 containing X'Ol'IX'81'1 respectively
Data stream
e = k for b+4 and b+5 containing X'81' and X'OO'I respectivelYI or b+4
containing X'OI'.
e < k for b+4 and b+5 containing X'81' and X'20'I
respectively.
Suffix
Required GDS variable, either Type 1 or Type 2
Length, in binary, of the GDS variable, including this Length field (value
5 is valid if Suffix is Type 1; value 8 is valid if Suffix is Type 2)
Type identifier:
X'CFOl' Suffix Type 1:
indicates that no exception condition has occurred
sending the DISTIU
X'CF02' Suffix Type 2:
indicates that an exception condition was detected
by the sender of the DISTIU (The Suffix Type 2 may follow after
any subfield within DISTIU after the exception condition occurs.)

SNA Formats

DISTIU

k+5

k+6-k+8

k+6

Note:
FMH-7 (see Chapter 10) is sent over the conversation before the
Suffix Type 2 is sent. This is the result of issuing the SEND_ERROR verb
(see SNA Transaction Programmer's Reference Manual for LU Type 6.2 ) by
the DS_SEND transaction program of the sending DSU.
Format:
X'OO' no segmentation descriptor follows, f~r Suffix Type 1
X'OI' no segmentation descriptor follows, for Suffix Type 2
Exception Code
Required subfield for a Type 2 suffix (otherwise, omitted), describing the
type of error detected:
Exception Class:
bits 0-1, severity of error:
11 catastrophic error; request not processed
bits 2-7, class of error:
000101 sender error

k+7

Exception Condition Code, indicating the reason for the exception:
are defined in Figure 13-14 on page 13-37

k+8

Exception Object, indicating the syntactical entity in error: values are
defined in Figure 13-15 on page 13-38
p = k+5 or k+8 as the Suffix is Type 1 or Type 2 respectively.

p

Chapter 13.

SNA Distribution Services

values

13-33

ACKNOWLEDGE INTERCHANGE UNIT

ACKIU; DSU ---> DSU; (ACKNOWLEDGE INTERCHANGE UNIT)
ACKIU flows between pairs of DSUs, to acknowledge or to
notify the DSU that sent a DISTIU that the receiving DSU
found errors while processing the DISTIU. It is not
forwarded through the SNADS network. It contains:
•
•
•

Prefix
Command
Suffix

See Figure 13-13 on page 13-35.

13-34

SNA Formats

ACKIU

ACKNOWLEDGE INTERCHANGE UNIT:

I
Prefix
Command
Correlation
Exception Code

I
I

Reply Data

I
Receiving DSUN
SNADS Status:

Type, Contents

I
Application Status:
IType, Contents

I
I

Suffix

I
I
I
GDS
COOl

CIOI
I
I
IC
I
13
I
12
I
18
I
I
I
I
I
I
I
110 kl

C
3
2
2

I
I
I
I
IC345
t----.
I
IC I
I
13 I
I
16 I
I
11 I
I

I

L--..J

CFOI

r-, r-,
IC
13
15
16

CI
31
51
71

L-....I

IC
13
15
16

CI
31
51
71

L-....I

I

L--.....J

o

Figure 13-13.

4

5

p

p+l p+5

Structure of the Acknowledge IU

0-4

Prefix

0-1
2-3
4

Required GDS variable
Length (5), in binary, of the GDS variable, including this Length field
Identifier: X'COOl'
Format:
X'02' no segmentation descriptor follows

Chapter 13.

SNA Distribution Services

13-35

ACKIU
5-p

Command
Required GDS variable of:
•
•
•

5-6
7-8
9

10-k

10-11
12-13
14
15

16
17-k

O-m

Correlation
Exception Code
Reply Data

See Figure 13-13 on page 13-35. Reply Data may appear after or before the
Exception Code.
Length, in binary, of the GDS variable, including this Length field
(values from 49 to 853 are valid)
Identifier: X'C101', identifies this IU as an ACKIU
Format:
X'Ol' no segmentation descriptor follows
Correlation
Required GDS variable (see Figure 13-13 on page 13-35)
Length, in binary, of the GDS variable, including this Length field
(values from 7 to 23 are valid)
Identifier: X'C328'
Format:
X'Ol' no segmentation descriptor follows
Reply indicator:
X'OO' ACKIU is the last reply to the referenced DISTIU, see "Distribute
Interchange Unit" on page 13-2
Command position, in binary, in the IU command se~uence:
X'Ol' for SNADS
Interchange unit identifier (optional field):
a 0- to 16-byte identifier
provided by the prefix of the DISTIU for which this ACKIU is a
notification equal to the IU identifier (see "Distribute Interchange Unit"
on page 13-2)
Exception Code
Required GDS variable, contains error classification information and,
optionally, the DISTIU subfield found in error:
•
•
•
•

0-1
2-3
4

5

Exception
Exception
Exception
Exception

Class
Condition Code
Object
Data (optional)

Length (m+l), in binary, of the GDS variable, including this Length field
(values from 8 to 255 are valid)
Identifier: X'C322'
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
Exception Class
Contains severity and error class:
bits 0-1, severity
11 catastrophic error; request not processed

13-36

SNA Formats

ACKIU
bits 2-7, class
000011 semantic error
000010 syntactic error
000100 process error
Exception Condition Code:
in Figure 13-14

6

indicates reason for exception; values defined

I

ICode
I (hex)

Description

I
I
01
02
04

06
07
08
OA

DB
DC

DE
OF
10
11
15

16
17
18

Allowed
in DISTIU
Suffix

Function not supported
Data not supported
Resource not available
Execution terminated
Data not found
Segmentation
Sequence
I/O error
ID invalid
Format invalid
Length invalid
Indicator invalid
Range exceeded
Subfield length invalid
Subfield type invalid
Invalid parameters
Content error

yes

yes

yes

yes

Allowed
in ACKIU

yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes

All other values are reserved

Figure 13-14.

7

Exception Condition Codes

Exception Object:
indicates the syntactical entity in error; values
defined in Figure 13-15 on page 13-38

Chapter 13.

SNA Distribution Services

13-37

ACKIU
I

Exception Object

ICode
I (hex)

I
I
01
02
07
08
09
OC
OD
OE
OF
10
11
12
13
14

allowed
in DISTIU
Suffix

allowed
in ACKIU

yes

yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes

IU prefix
IU identifier
Command
Command operand
Operand value
Document unit
Document unit identifier
Document profile
Document profile parameter
Document content introducer
Document content control
Document content data
IU suffix
Segment
Unsupported subfield
Unknown subfield
Distribution object prefix
Distribution object data

16
17
lA

IB

yes

yes

yes

yes
yes
yes

All other values are reserved.

Figure 13-15.

8-m

Exception Object Codes

Exception Data (optional field):

contains the DISTIU subfield in error

O-p
Required GDS variable, information to be used by the DSU to create the
feedback:
•
•
•

0-1
2-3
4

5-n2

13-38

Receiving DSUN
SNADS Status
Application Status (optional)

See Figure 13-13 on page 13-35.
Note:
Unless otherwise specified, the receiving DSU is the DSU that
receives the DISTIU; likewise, the sending DSU is the DSU that sends the
DISTIU.
Length (p+l), in binary, of the GDS variable, including this Length field
(values from 29 to 570 are valid)
Identifier:
X'C345'
Format:
X'OI' no segmentation descriptor follows; does not contain LT-subfields
Receiving DSUN

SNA Formats

ACKIU
Required GDS variable, the name of the rece1v1ng the DSU that detected the
error, and the name of the sender of the ACKIU, contains:
•
•

5-6
7-8
9

O-nl

o
1
2-nl

0-n2

o
1
2-n2

n2+1-n3

Receiving RGN (optional)
Receiving REN

The above LT-subfields can be in any order.
Length, in binary, of the GDS variable, including this Length field
(values from 8 to 25 are valid)
Identifier: X'C36l'
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
Receiving RGN
Optional LT-subfield
Length (n1+1), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'Ol'
First part of the name of the detecting DSU (see "Specification of the
Character-String Fields" on page 13-41 for the encoding of the graphic
characters used)
Receiving REN
Required LT-subfield
Length (n2+l), in binary, of the subfield, including this Length field
(values from 3 to 10 are valid)
Type:
X'02'
Second part of the name of the detecting DSU (see "Specification of the
Character-String Fields" on page 13-41 for the encoding of the graphic
characters used)
SNADS Status
Required pair of GDS variables:
•
•

Status Type
Status Contents

See Figure 13-13 on page 13-35:
n2+l-n2+7 Status Type
Required GDS variable
n2+1-n2+2 Length (7), in binary, of the GDS variable, including this Length field
n2+3-n2+4 Identifier: X'C356'
n2+5
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
n2+6-n2+7 Status type:
X'OOOl' for SNADS Status
n2+8-n2+16 Status Contents

Chapter 13.

SNA Distribution Services

13-39

ACKIU

.

Required GDS variable
n2+8-n2+9 Length (9), in binary, of the GDS variable, including this length field
n2+l0-n2+11 Identifier: X'C357'
n2+12
Format:
X'41' no segmentation descriptor follows; contains LT-subfields
n2+13-n2+16 SNADS Condition Code

-----

----

Required IT-subfield
n2+13
length (4), in binary, of the subfield , including this length field
Type:
X'Ol'
n2+14
n2+15-n2+16 Values are listed in Figure 13-10 on page 13-25.
n2+17-p

Application Status
Optional pair of GDS variables:
•
•

Status Type
status Contents

Note:
When generating a DIST IU with Status information supplied by an
ACKIU , the Reporting DSU may ignore Application Status.
n2+17-n2+l8 Status Type
Required GDS variable
n2+17-n2+18 Length (7), in binary, of the GDS variable, including this Length field
n2+19-n2+20 Identifier: X'C356'
n2+21
Format:
X'Ol' no segmentation descriptor follows; does not contain LT-subfields
n2+22-n2+23 Status type:
X'0200'-X'06FF' are valid for applications
n2+24-p

Status Contents

Required GDS variable
n2+24-n2+25 Length, in binary, of the GDS variable, including this Length field
(values from 7 to 517 are valid)
n2+26-n2+27 Identifier: X'C357'
n2+28
Format:
X'4l' no segmentation descriptor follows; contains LT-subfields
n2+29-p
Status content: application-defined bit string
p+l-p+5

Suffix

p+1-p+2
p+3-p+4
p+5

Required GDS variable
Length (5), in binary, of the GDS variable, including this Length field
Identifier: X'CF01'
Format:
X'OO' Only value defined

13-40

SNA Formats

NAMES AND CODE
------

POINTS

SPECIFICATION OF THE CHARACTER-STRING FIELDS

Figure 13-16 defines the character sets, string rules, and string lengths used to
encode the SNADS interchange units.
For more details, see the semantic
descriptions.
The character strings are specified for two cases:
character string (ECS) option subset.

the base and the enhanced

I

Character Set
Field Name
Base

ECS Opt

Base

DGN
DEN

A
A

930
930

none
none

Origin RGN
Destination RGN
Origin REN
Destination REN

A
A
A
A

A
930
A
930

none
none
none
none

Destination TP Name,
Feedback TP Name,
and Server Name

AE (Note 2)

Origin Sequence Number

I String Length
I
I
ECS Opt I
Min
I Max
I
I
(Note 1)1 1 (Note 1) I 8
(Note 1)1 1 (Note 1) I 8
I
I
1
none
I
I 8
(Note 1) I
1
I 8
1
none
I
I 8
(Note 1) I
1
I 8
I
I
I
I
I
I
none
I
1
I 64
I
I
I
I
n/a
I
4
I 4

String Rules

Numerics of A:
(FO, Fl,
F9)

Notes:
1. - DGN and DEN minimum length is 0 if the DISTIU is
of type STATUS and is generated by SNADS.
Leading space (X'40') characters are not used,
trailing space (X'40') characters are not significant,
and imbedded space (X'40') characters are significant.
2. The first character of an SNA service transaction program name
is a byte ranging in value from X'OO' through X'3F'.

Figure 13-16.

Note:

Character-String Specification

Appendix A defines the codes of the graphic character sets A, AE, and 930.

Chapter 13.

SNA Distribution Services

13-41

CODE POINTS USED BY SNADS

The values of the ID component of the LLIDF field as used for SNADS GDS variables
are shown below: 3
ID

Subfield Name
In DIA, IU PREFIX; in SNADS, Prefix for Distribute IU and Acknowledge IU
in DIA, IU CMD NO REPLY ACKNOWLEDGE; in SNADS, Command of the Acknowledge IU
Command, Distribute IU

CI05

in DIA, IU OPERAND IMM DATA EXCEPTION-CODE; in SNADS, Exception Code, within
Acknowledge IU
in DIA, IU OPERAND IMM DATA DATA CORRELATION; in SNADS, Correlation, within
Acknowledge IU
in DIA, IU OPERAND IMM DATA USER-DATA; in SNADS, Destination Application
Parameters, within Distribute IU
in DIA, IU OPERAND IMM DATA STATUS-INFORMATION; in SNADS, Distribution
General Options, within Distribute IU
in DIA, IU OPERAND IMM DATA DISTRIBUTION-IDENTIFIER; in SNADS, Distribution
Identifier, within Distribute IU
in DIA, IU OPERAND IMM DATA GENERAL-ROUTING-DATA; in SNADS, Feedback
Options, within Distribute IU
in DIA, IU OPERAND IMM DATA REPLY DATA; in SNADS, Reply Data, within
Acknowledge IU
C350

Beginning of Destination Operand Lists, of the Specific Status Lists, within
Distribute IU

C351

End of Destination Operands Lists, of the Specific Status Lists, within
Distribute IU

C352

Routing Group Name (RGN) of Destination Operands, within Distribute IU

C353

Routing Element Name (REN) of REN List, within Distribute IU

C354

Distribution Group Name (DGN) of DGN List, within Distribute IU

C355

Distribution Element Name (DEN) of DEN List, within Distribute IU

C356

Status Type, within Distribute IU

3

The asterisk following the ID indicates that that identifier
(Document Interchange Architecture) and SNADS.

13-42

SNA Formats

1S

used by both DIA

C357

Status Contents, within Distribute IU

C360

Feedback Address, within Distribute IU

C361

Receiving Distribution Service Unit Name, within Distribute IU

C908

Data, Distribution Object, within Distribute IU

C90A

Distribution Object Prefix, Distribute IU

CF01*

in DIA, IU SUFFIX NORMAL-TERMINATION; in SNADS, Suffix Type 1

CF02*

in DIA, IU SUFFIX ABNORMAL-TERMINATION; in SNADS, Suffix Type 2

Chapter 13.

SNA Distribution Services

13-43

STATUS TYPE CODES

SNADS uses the following status type code as a subfield of the General and Specific
Status subfields of the DISTIUs:
Code

Meaning

X'OOOO'

Reserved

X'OOOl'

SNADS errors

X'OOO2'-X'OlFF'

Reserved

X'0200'

DIA application errors

X'0201'-X'FFFF'

Reserved

13-44

SNA Formats

TRANSACTION PROGRAM AND SERVER NAMES

Following is a list of all transaction program and server names defined for SNADS,
in the FM header 5 (Attach), in the Distribute IU, or used internally in the
distribution service unit (DSU).
Code

Meaning

X'20FOFOFO'

DIA PROCESS Destination Transaction Program Name

X'20FOFOF1'

DIA SERVER Name

X'21FOFOF1'

DS SEND Transaction Program Name

X'21FOFOF2'

DS_RECEIVE Transaction Program Name

X'21FOFOF3'

DS ROUTER DIRECTOR Transaction Program Name

X'21FOFOFb'

SNADS General Server Name

Chapter 13.

SNA Distribution Services

13-45

This page intentionally left blank

13-46

SNA Formats

CHAPTER 14.

GDS VARIABLES FOR GENERAL USE

The following chart indicates (using an "X") each GDS variable code point (with
first byte = X'12') used by LU 6.2.

rFirst hexadecimal digit
rSecond hexadecimal digit

I
I
I
I
I
I

I
I
I

I

I

I

I

L->I 0 I 1 I 2 I 3
I I
I
I
I
L-> 101
I
I
I
I I
I
I
I
III X I X I
I X
I I
I
I
I
121
I
I
I
I I
I
I
I
131
I
I
I
I I
I
I
I
141
1 I
I
I 1 I
I
I
151
I
I
I
I I
I
I
I
161
1 1 I
I I
I
I
I
171
I
I
I
I I
I
I
I
181
I
I
I
I I
I
I
I
191
I
I
I
I
I
I
I I
IAI X I
I
I
I I
I
I
1
IBI
I
I
I
I 1 I
1 I
ICI
I
I
I
I
I I
I
I
I DI
I
I
I
I
I I
I
I
I X I X I
lEI
I
I I
I
I
I FI
I X I X I X
I

I

I

I 4 I 5
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1 1
1 I
I
I
I
I
I
I
I
I
I
1
I
I
I
I
I
I
I
I
I
I
I X I X

I

I

I

I 6 I 7 I 8
I
I
I
1 1 I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1 1 1
I
I
I
I
I
I
I
I
I
I
I
I
1 1 I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1
1
I
I
I
I
I
I
I
1
I
I
I
I
I
I
I
I
I
I
I
I
I
I

I

9 I A
I
I
I
I
I
I
I
I
1
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

I

B

I

I

I

I CI DI E I F
1 1 I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1 I
1
I
I
I
I
I
I
I
I
I
I
I
I
1 I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1 1 I
I
I
I
I
I
1 1 1 1
1 I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
1 I
1
I
I
1 I
!
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I X
I
I

I

I
I
I
I
I
I
I
I
I
1
I
I
I
I
I
I
I
I
I
1
I
1
I
I
I
I
1
I
I
I
I
I
I

I

Figure 14-1.

LU Type 6.2 GDS Variable Code Points
Chapter 14.

GDS Variables for General Use

14-1

The code points used by lU 6.2 are:
X'1210'
X'1211'
X'1213'
X'12AO'
X'12E1'
X'12E2'
X'12F1'
X'12F2'
X'12F3'
X'12F4'
X'12FS'
X'12FF'

Change Number of Sessions (see Note 1)
Exchange log Name (see Note 1)
Compare States (see Note 1)
Workstation Display Passthrough
Error log
PIP Subfield Data (see Note 2)
Null Data
User Control Data
Map Name
Error Data
PIP Data (see Note 2)
Application Data

Notes:
1.

See "Chapter 12. GDS Variables for SNA Service Transaction Programs" for the
formats and meanings of these GDS variables.

2.

See "Chapter 10. Function Management Headers" for the formats and meanings of
these GDS variables.

14-2

SNA Formats

Application Data (X'12FF') GDS Variable

The Application Data GDS variable, ID X'l2FF', contains application data.
The
application transaction program's data as specified in the MC_SEND_DATA verb is
(optionally) mapped and then sent as X'l2FF' variables.

Null Data (X'l2Fl') GDS Variable

The Null Data GDS variable, ID X'12Fl', contains no application data.
This variable
may optionally be generated to carry certain control information (e.g., Confirm)
when no application data is available.

User Control Data (X'12F2') GDS Variable

The User Control Data GDS variable, ID X'12F2', contains user control data.
The
meaning of this data is known only to the LU services component programs or the
transaction programs and their mapping programs. This data can be used, for
example, as prefix control information for an Application Data GDS variable ~hat
follows it or to carry FM header data for a mapped conversation transaction.

Map Name (X'12F3') GDS Variable

The Map Name GDS variable, ID X'12F3', is followed by a 0- to 64-byte map name.

Chapter 14.

GDS Variables for General Use

14-3

Error Data (X'12F4') GDS Variable
The Error Data GDS variable, ID X'12F4', is used to convey information about mapping
errors.
It is sent using the SEND_DATA verb following a SEND_ERROR verb.
Its
format is:
0-1
2-3
4-7

8

9-n

14-4

length (n+1), in binary, of Error Data GDS variable, including this length
field
GDS ID: X'12F4'
Error code:
X'00010000' Invalid GDS ID:
The mapped conversation verb component
encountered a GDS ID that it did not recognize.
X'00030001' Map Not Found: The specified map was not available at the
target, or access to the referenced map could not be
completed.
X'00030002' Map Execution Failure: The map program was not able to
process the data stream.
length (n-8), in binary, of error parameter
Error parameter: for a mapping failure, the map name carried in the GDS
variable for which the error occurred;· for an invalid GDS ID, the 2-byte
GDS ID that was not recognized

SNA Formats

Error Log (X'12El') GDS Variable
The Error Log GDS variable, ID X'12El', following an FMH-7 conveys
implementation-specific error information to an LU, where it is added to the system
error log for use in debugging and error recovery.
It is not used by SNA-defined
service transaction programs (other than to log it) since it contains
implementation-specific data. The Error Log variable is sent as a consequence of
issuing the SEND_ERROR verb, but is not passed to the receiving transaction program.
Its format is:

0-1
2-3
4-m
4-5

6-m
m+l-n
m+l-m+2

m+3-n

Length (n+l), in binary, of Error Log GDS variable, including this Length
field
GDS ID: X'12El'
Product Set ID
Length, in binary, of Product Set ID, including this Length field (values
2 to 32,767 are valid)
Note: The Length field is always present; a value of 2 indicates no
Product Set ID subvector follows.
Product Set ID (X'lO') subvector (format described in "Chapter 8. Common
Fields")
Message Text
Length, in binary, of message text, including this Length field (values 2
to 32,767 are valid)
Note: The Length field is always present; a value of 2 indicates no
message text follows.
Message text data:
implementation-specific data

Chapter 14.

GDS Variables for General Use

14-5

This page intentionally left blank

14-6

SNA Formats

APPENDIX A.

SNA CHARACTER ---SETS --AND SYMBOL-STRING TYPES

This appendix describes the character sets and symbol-string types used for the
following fields:
•

LU name

•

Network-qualified LU name

•

Mode name

•

Transaction program name

•

Access security information subfields

•

Program initialization parameters (PIP) subfields

•

Map name

•

SNADS server, user (DGN, DEN), and service unit (RGN, REN) names

The detailed syntax of these strings is described in other chapters where their
usage within individual message units is defined.

SYMBOL-STRING TYPE
The symbol-string type specifies the set of code points and corresponding characters
from which the strings listed above are composed, as follows:
•

Type A (Assembler oriented): a character string consisting of one or more
characters from character set A. The first character of a type-A symbol string
is not a numeric; i.e., it is different from X'FO', X'FI', ... , or X'F9'.

•

Type AE (A extended): a character string consisting of one or more characters
from character set AE, with no restriction on the first character.

•

Type 930 (distribution services oriented): a character string consisting of one
or more characters from character set 930, with the following rules:
No leading space (X'40') characters are used, but no other restrictions
exist on the first character.
Imbedded space (X'40') characters are significant.
Trailing space (X'40') characters are not significant.

Appendix A.

SNA Character Sets and Symbol-String Types

A-I

•

Type USS (unformatted system services oriented, used for character-coded
requests): a character string consisting of one or more characters from
character set USS, with no restriction on the first character.

•

Type GR (EBCDIC graphics): a byte string consisting of one or more bytes within
the range X'41' through X'FE', with no restriction on the first byte.

•

Symbol-string type G (general): a byte string consisting of one or more bytes
within the range X'OO· through X'FF', with no restriction on the first byte.

SNA CHARACTER SETS AND ENCODINGS
A character set is a set of graphic characters, such as letters, numbers, and
special symbols.
SNA formats make use of a variety of character sets. Character
sets A, AE, 930, and USS define the characters that are allowed in the corresponding
symbol-strings.
Each character set is encoded using a code page. A code page is the specification
of code points, or hexadecimal values, for one or more character sets. All
character sets used by SNA are encoded using IBM code page 00500, the relative
encodings of which are shown in Figure A-I.
For current and future SNA formats, two new character sets are used:
character sets
00640 and 01134, both encoded using code page 00500. Character sets encoded using a
specific code page are officially denoted by the concatenation of their character
set and code page numbers, such as 00640-00500 and 01134-00500. The concatenation
of these two numbers specifies a coded graphic character set. The older character
sets--A, AE, 930, and USS--and their encodings continue to be supported but not for
new formats, which now use 00640-00500 and 01134-00500.
Figure A-Ion page A-3 defines the character sets and encodings for A, AE, 930, USS,
01134-00500, and 00640-00500. The code points that do not belong to any of these
sets are not shown.

A-2

SNA Formats

Figure A·1 (Page 1 of 2). Character Sets A, AE, 930, USS, 1134 and 640
Hex
Code
15
40
48
4C
40
4E
50
59
58
5C
5D
5E
60
61
62
63
64
65
66
67
68
69
68
6C
6D

Set
Graphic

<
(

+
&

P
$
*

)
;

/

A
A
A
A
A

A
Q
N
%

-

6E
6F
71
72
73
74
75
76

>

77

'j
j

78
7A
78
7C
7D
7E
7F
80
81
82
83
84
85
86
87
88
89
91
92
93
94
95
96
97
98
99
9A

?

E
E
E
E
i
I

#
@

,

=

"
(2)

a
b
c
d
e
f
g
h
i
j
k
I
m
n
0

P
q
r
~

Description
Line Feed
Space
Period
Less Than Sign
Left Parenthesis
Plus Sign
Ampersand
Sharp S
Dollar Sign
Asterisk
Right Parenthesis
Semicolon
Minus Sign
Slash
A Circumflex, Capital
A Dieresis, Capital
A Grave, Capital
A Acute, Capital
A Tilde, Capital
A Overcircle, Capital
C Cedilla, Capital
N Tilde, Capital
Comma
Percent Sign
Underline
Greater Than Sign
Question Mark
E Acute, Capital
E Circumflex, Capital
E Dieresis, Capital
E Grave, Capital
I Acute, Capital
I Circumflex, Capital
I Dieresis, Capital
I Grave, Capital
Colon
Number Sign
At Sign
Apostrophe
Equal Sign
Quotation Marks
o Slash, Capital
a, Small
b, Small
c, Small
d, Small
e, Small
f, Small
g, Small
h, Small
i, Small
j, Small
k, Small
I, Small
m,Small
n, Small
0, Small
p, Small
q, Small
r, Small
a Underscore, Small

Appendix A.

A

X

AE

930

USS

X

X
X

X
X
X

X

X
X
X

X
X
X
X
X
X
X
X
X
X
X

1134

640

X
X
X
X
X
X
X
X

X

X
X
X
X
X
X

X
X
X
X
X

X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X

X
X

X
X
X

X
X
X
X

X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

SNA Character Sets and Symbol-String Types

A-3

Figure A-1 (Page 2 of 2). Character Sets A, AE, 930, USS, 1134 and 640
Hex
Code
9B
9D
9E
AO
A2
A3
A4
A5
A6
A7
A8
A9
AC
AD
AE
C1
C2
C3
C4
C5
C6
C7
C8
C9
D1
D2
D3
D4
D5
D6
D7
D8
D9
DF
E2
E3
E4
E5
E6
E7
E8
E9
EB
EC
ED
EE
EF
FO
F1
F2
F3
F4
F5
F6
F7
F8
F9
FB
FC
FD
FE

A-4

Set
Graphic
Q

C;

fE
J1..

s
t
u
v
W

x

Y

z
f)

'f
D
A
B
C
D
E
F
G
H
I
J
K
L
M
N
0
P
Q

R

Y
S
T
U
V
W
X
Y
Z

6
0
6
0
0
0
1
2

3
4
5

6
7
8

9

0

0
CJ

0

Description
o Underscore, Small
Cedilla
AE Diphthong, Capital
Micro, Mu
s, Small
t, Small
u, Small
v,Smali
w,Smali
x, Small
y, Small
Z, Small
D Stroke, Capital
Y Acute, Capital
Thorn, Capital
A, Capital
B, Capital
C, Capital
D, Capital
E, Capital
F, Capital
G, Capital
H, Capital
I, Capital
J, Capital
K, Capital
L, Capital
M, Capital
N, Capital
0, Capital
P, Capital
Q, Capital
R, Capital
y, Dieresis, Small
S, Capital
T, Capital
U, Capital
V, Capital
W, Capital
X, Capital
Y, Capital
Z, Capital
Circumflex, Capital
Dieresis, Capital
Grave, Capital
Acute, Capital
Tilde, Capital
Zero
One
Two
Three
Four
Five
Six
Seven
Eight
Nine
U Circumflex, Capital
U Dieresis, Capital
U Grave, Capital
U Acute, Capital

A

930

USS

1134

640

X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X

X
X
X
X

X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X

X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

X

X
X

X

X
X
X
X
X
X
X
X

X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

o
o
o
o
o

IBM SNA Network Product Formats

AE

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

X
X
X
X
X
X
X
X
X
X

X
X
X

X
X
X

X
X
X

X
X
X

X
X
X
X
X
X

APPENDIX B.

GDS ID DESCRIPTION AND ASSIGNMENTS

This appendix defines the general data stream (GDS), which is used in a variety of
ways in SNA.
For instance, it is used to encode the Document Interchange
Architecture (DIA) message units. The basic structural unit in GDS is the
structured field, a string of bytes preceded by a length and beginning with a GDS
identifier (ID) that defines the structure of the remainder of the field.
Some
structured fields are used by components of SNA; these fields are defined in
"Chapter 12. GDS Variables for SNA Service Transaction Programs", "Chapter 14. GDS
Variables for General Use" , "Chapter 5.1. Request Units", "Chapter 5.2. Response
Units", and "Chapter 10. Function Management Headers". GDS IDs are assigned,
generally in blocks of consecutive values, to different layers and components of SNA
and to other interconnection architectures.
For a complete listing of these block
assignments, see below.
The general data stream applies to data exchanged between nodes over links and to
data exchanged via removable storage media or shared storage facilities.

STRUCTURED FIELDS

Each structured field has the format shown in Figure B-1.

~--------~-------------r----------//------------~

LENGTH
(LL)

IDENTIFIER
(ID)

INFORMATION

~--------~------------~----------//------------~

Byte

0

Figure B-1.

2

4

N

GDS Structured Field

LENGTH (ll) DESCRIPTION
The LLID is a 4-byte field in which the two LL bytes are used to indicate the length
of the LLID field itself (4 bytes) plus the data following the LLID; up to 32,763
bytes of data may follow the LLID. Values 0 and 1 of the LL are reserved for use as
escape sequences; values 2 and 3 are not used.
For example, a value of X'OOOl'
indicates a presentation services header, which is used for sync point management.

Appendix B.

GDS ID Description and Assignments

B-1

Bit 0 (high-order bit) of byte 0 is used as a length continuation (or not-last
segment) indicator.
If that bit is set to 1, the logical record is continued by a
2-byte LL; the ID occurs only following the first LL.
The continuing Ll is located
immediately following the information bytes encompassed by the first LL.
The
continuing lL might itself be continued.
In other words, the length specified by
the continuing LL might not be the entire remainder of the logical record; it might
be followed by yet another LL.
The amount of data spanned by each continuing Ll can
be any size convenient to the sender (including 0).
Eventually, the chain of
continuing lLs is ended by a final lL, i.e., one with the high-order (not-last) bit
set to o.
The final lL may indicate a null information field follows (length
2).

=

When an lLID encompasses a string of logical records identified by full LlIDs, the
length of the string, determined by summing the (nested) encompassed Lls, equals the
length definer of the (outer) encompassing LlID less 4 (this applies at each level
of nesting).
If the encompassing LlID is continued by segmenting, the length of the
string of segments equals the sum of the initial Ll and all continuing LLs of the
encompassing ID less 4 for the initial LLID and 2 for each continuing LL.
The 2-byte ID values, irrespective of the level of nesting at which they occur, are
defined uniquely across all levels of nesting, with the following exception.
The ID
values X'FFOO' through X'FFFF' are used only within an encompassing LlID (which is
not necessarily the immediate parent structure); their meaning is defined by the
architecture that owns the higher-level ID and it applies only within the context of
that ID.
In other words, ID values in the X'FF**' range are context dependent.
All
other ID values are context independent.

IDENTIFIER (ID) DESCRIPTION
The 2-byte identifier that follows the length field indicates the format and meaning
of the data that follows.
Sometimes additional values appearing in the information
field are needed to completely specify the information field's content.
The
uniqueness of the identifier (with the exceptions noted above) makes it easy to
decode structured fields in line traces, and also to make it easier to create
composite data streams by including elements of several architectures.
DIA carried
by SNADS is an example of such a use.

IDENTIFIER REGISTRY

The identifiers that have been assigned for specific use are listed below.
Identifiers are assigned in blocks; not all identifiers in a block are necessarily
currently used by the owner.

GDS ID

Structured Field Owner
3270
3270

B-2

SNA Formats

03~n~

06**
09**
OB**
OC**
OD**
OE**

3270
3270
3270
3270
3270
3270
3270

OFOO-OFFF

3270

1010-101F

3270

1030-1034

Print Job Restart

1100-1104

SNA Character String

1200-12FF

LU 6.2 (APPC)

1300-13FF

Management Services

1400-140F

3820 Page Printer

1570-158F

SNA Distribution Services

40**
41**
4A**
4B**
4C**

3270
3270
3270
3270
3270

7100-71FF

3250
3270

8100-81FF

3270

COOO-COOF

Document Interchange Architecture

C100-C104

Document Interchange Architecture

C105

SNA Distribution Services

C10A-C122

Document Interchange Architecture

C123-C124

SNA Distribution Services

C219

Document Interchange Architecture

C300-C345

Document Interchange Architecture

C350-C359

SNA Distribution Services

C366-C3FF

Document Interchange Architecture

Appendix B.

GDS ID Description and Assignments

B-3

B-4

C400-C46F

Document Interchange Architecture

C500-C56F

Document Interchange Architecture

C600-C66F

Document Interchange Architecture

C700-C7FF

Graphical Display Data Manager

C800-C87F

Document Interchange Architecture

C900-C97F

Document Interchange Architecture

C980-C9FF

Document Interchange Architecture

CAOO-CA7F

Document Interchange Architecture

CA80-CAFF

Document Interchange Architecture

CBOO-CBOF

Document Interchange Architecture

CCOO-CC3F

Document Interchange Architecture

CDOO-CD3F

Document Interchange Architecture

CFOO-CFOF

Document Interchange Architecture

DOOO-DOFF

Distributed Data Management

D300-D3FF

Document Content Architecture

D600-D6FF

Intelligent Printer Data Stream

D780-D7BF

Facsimile Architecture

EIOO-EIOF

Level-3 Document Content Architecture

E200-E20F

Level-3 Document Content Architecture

E300-E30F

Level-3 Document Content Architecture

E400-E40F

Level-3 Document Content Architecture

E500-E50F

Level-3 Document Content Architecture

E600-E60F

Level-3 Document Content Architecture

E7 0 O-E7 OF

Level-3 Document Content Architecture

E800-E80F

Level-3 Document Content Architecture

E900-E90F

Level-3 Document Content Architecture

EAOO-EAOF

Level-3 Document Content Architecture

SNA Formats

EFFF

IBM Token-Ring Network PC Adapter

FOOO-FEFF

Non-IBM Reserved Block

FFOO-FFFF

Context-Dependent Block

Appendix B.

GDS ID Description and Assignments

B-5

This page intentionally left blank

B-6

SNA Formats

APPENDIX C.

LIST OF ABBREVIATIONS AND SYMBOLS

ACT

address (SOLC)
active, activate

Bl nnnn '
BB
BBI
BC
BCI
BETB
BF
BIU
BLU
BSC
BTU

binary digits (usually shown simply as nnnn)
begin bracket
begin bracket indicator
begin chain
begin chain indicator
between brackets
boundary function
basic information unit
basic link unit
Binary Synchronous Communication
basic transmission unit

(c)

configuration services
control (SOLC)
communication controller adapter
International Telegraph and Telephone Consultative Committee
cross-domain, change direction
change direction indicator
cross-domain resource manager
conditional end bracket
conditional end bracket indicator
Customer Information Control System/Virtual Storage
compression indicator
change 'number of sessions
contention
class of service
control point
compaction indicator
cyclic redundancy check
cryptography verification
code selection indicator
control sequence prefix

A

C

CCA
CCITT
CD
CDI
CDRM
CEB
CEBI
CICS/VS
CMI
CNOS
CONT
COS

CP
CPI
CRC
CRV
CSI

CSP

OAF
OCE
OCF

00
ddd

destination address field
data circuit-terminating equipment
data count field
day of month
day of year

Appendix C.

List of Abbreviations and Symbols

C-l

DEF
DEN
DES
DFC
DGN
DISC
DISOSS
DISTIU
DLC
DLU
DM
DPN
DQ
DRlI
DR2I
DSAF
DSP
DST
DSU
DTE

destination element address field
distribution user element name (SNADS)
Date Encryption Standard
data flow control
distribution user group name (SNADS)
Disconnect (SDLC)
Distributed Office Support System
distribution interchange unit (SNADS)
data link control
destination logic unit
Disconnected Mode (SDLC)
destination program name
dequeue
definite response 1 indicator
definite response 2 indicator
Destination Subarea Address Field
data stream profile
data services task or device service task
distribution service unit (SNADS)
data terminal equipment

EB
EBCDIC
EBI
EC
ECI
ED
EDI
EFI
ENA
ENP
ER
ERP
ERCL
ERI
ERN
ERP
Exp
EXR

end bracket
extended binary coded decimal interchange code
end bracket indicator
end chain
end chain indicator
enciphered data
enciphered data indicator
expedited flow indicator
extended network addressing
Enable Presentation
explicit route
error recovery procedures
exchange record length
exception response indicator
explicit route number
error recovery procedures
expedited flow
EXCEPTION REQUEST

F

flag (SDLC)
forms control block
frame check sequence (SDLC)
full-duplex data flow
flip-flop direction control
field-formatted record
format indicator
format identification
first-in, first-out
function management

FCB
FCS
FDX

FF
FFR
FI
FID
FIFO
FM

C-2

SNA Formats

FMD
FMDS
FMH
FMHC
FNI
FRMR
FS
FS2

function management data
function management data services
function management header
function management header concatenation
fixed fields without field separators
Frame Reject (SDLC)
fixed fields with field separators
fixed fields with or without field separators

GDS

general data stream

HDX
hex
HH
HPCA

half-duplex data flow
hexadecimal
hours
High-Performance Communication Adapter

I

ID
IERN
ILU
IMS/VS
INB
INP
IPL
IPM
IPR
I/Q
IRS
ISO
IU

information (SDLC), initiate only
identification
initial explicit route number
initiating logical unit
Information Management Systems/Virtual Storage
in bracket
Inhibit Presentation
initial program load
ISOLATED PACING MESSAGE
ISOLATED PACING RESPONSE
initiate or queue
interchange record separator
International Organization for Standardization
interchange unit (SNADS)

KEYIND

key indicator

LAN
LCID
LH
LIFO
LL
LMS
LRH
LT
LSID
LU

local-area network
local coded graphic character set identifier
link header
last-in, first-out
logical record length (prefix)
logical messages services
logical record header
link trailer
local session identification
logical unit

Appendix C.

List of Abbreviations and Symbols

C-3

LVx
LVI

variable length parameter
variable length parameter, first position

(ma)
MGR
MM
MPC
MPF
MPl

maintenance services
manager
month, minutes
maximum presentation column
mapping field (BIU segments)
maximum presentation line

NA
NAU
NC
Norm
NS
NUMRECS

network address
network addressable unit
network control
normal flow
network services
number of records

OAF
ODAI
OEF
011
OlU
OSAF

origin address field
OAF'-DAF' assignor indicator
origin element field
office information interchange
originating logical unit
origin subarea field

P
PC
PCID
PD
PDI
PDIR
PI
PIP
PIU
PlU
POC
PPU
PRI
PRID
PRN
PRTY
PS
PSH
PU
PUCP
P/F

primary
path control
procedure correlation identifier
padded data
padded data indicator
peripheral data information record
pacing indicator
program initialization parameter
path information unit
primary logical unit
Program Operator Communication
primary physical unit
primary
procedure related identifier
primary resource name
priority
presentation services
presentation services header
physical unit
physical unit control point
poll/final (SDLC)

C-4

SNA Formats

QC
QEC
QR
QRI

queue
quiesce complete
quiesce at end of chain
queued response
queued response indicator

RCV
RO
REC
RECLEN
RECIO
RECTYPE
REJ
RELQ
REN
REQECHO
RH
RIM
RJE
RLSO
RNR
RQ
RQO
RQE
RQR
RR
RRI
RSP
RTI
RTR
RU

receive
Request ~isconnect (SOLC)
receive
record length
record identification
record type
Reject (SOLC)
release quiesce
routing element name (SNAOS)
Request Echo Test
request/response header
Request Initialization Mode (SOLC)
remote job entry
released
Receive Not-Ready (SOLC)
request
definite-response request
exception request
request recovery
Receive Ready (SOLC)
request/response indicator
response
response type indicator (+/-)
Ready To Receive (SOLC)
request/response unit

S

secondary
session services
session control
string control byte
SNA character string
~ense data included indicator
Synchronous Oata Link Control
secondary
session
Set Initialization Mode (SOLC)
secondary logical unit
Systems Network Architecture
sense code
sequence number field
SNA network interconnection

Q

(s)

SC
SCB
SCS
SOl
SOLC
SEC
SESS
SIM
SLU
SNA
SNC
SNF
SNI

Appendix C.

List of Abbreviations and Symbols

C-5

SNADS
SNRM
SPC
SPU
SQN
SRI
SS
SSCP
STP
SU
SVC

SNA distribution services
Set Normal Response Mode (SDLC)
sync point command
secondary physical unit
sequence number
stack reference indicator
seconds
system services control point
service transaction program
shared; unnamed
services

Tl
T2
T2.0
T2.1
T4
T5
TC
TERM
TEST

TWX

type-l (node)
T2.0 or T2.1 (node)
type-2.0 (node)
type-2.1 (node)
type-4 (node)
type-5 (node)
transmission control
terminate
Test (SDLC)
transmission group
transmission group number
transmission header
terminating logical unit
transmission priority field
transaction program name
transparent
transmission services
teletypewriter exchange service

UA
UI
UNAVL
UP
URC

Unnumbered Acknowledgment (SDLC)
Unnumbered Information (SDLC)
unavailable
Unnumbered Poll (SDLC)
user request correlation

VD
VOLID
VR
VRID
VRN
VRPRQ
VRPRS
VT

variable-length positional parameter
volume identification
virtual route
virtual route identifier
virtual route number
virtual route pacing request
virtual route pacing response
vertical tab

TG
TGN
TH

TLU
TPF
TPN
TRN
TS

C-6

SNA Formats

WP

word processing

XID
X'n ... n'
XMIT
XRF

Exchange Identification (SDLC)
hexadecimal digits
transmit
Extended Recovery Facility

YY

year

(vertical stroke) exclusive or
(asterisk) any value
(not sign) logical not

**

exponential operator
(underscore) separates multiple terms, or qualifiers, in a phrase

Appendix C.

List of Abbreviations and Symbols

C-7

This page intentionally left blank

C-8

SNA Formats

INDEX

r--1

I

A

I

'----'

Access Security Information
Subfields 10-11
format 10-11
ACK
See acknowledge
ACKIU 13-5, 13-34, 13-42
See also ACKNOWLEDGE INTERCHANGE UNIT
acknowledge
semantics 13-4, 13-34, 13-35
syntax 13-42
ACKNOWLEDGE INTERCHANGE UNIT
(ACKIU) 13-34
ACTIVATE LOGICAL UNIT (ACTLU) 5.1-5
ACTIVATE PHYSICAL UNIT (ACTPU) 5.1-5
ACTLU 5.1-5
See also ACTIVATE LOGICAL UNIT
ACTPU 5.1-5
See also ACTIVATE PHYSICAL UNIT
Alert (X'OOOO') MS Major Vector 8-11
Alert MS Subvector
Basic Alert (X'91') 8-16
Cause Undetermined (X'97') 8-79
Detail Qualifier (EBCDIC)
(X'AO') 8-81
Detail Qualifier (Hexadecimal)
(X'Al') 8-82
Detailed Data (X'98') 8-80
Failure Causes (X'96') 8-59
Generic Alert Data (X'92') 8-20
Install Causes (X'95') 8-53
Probable Causes (X'93') 8-30
SDLC Link 'Station Data (X'8C') 8-14
User Causes (X'94') 8-45
application transaction program (ATP)
destination TP name 13-3, 13-7,
13-10, 13-13, 13-25
asynchronous
feedback
See feedback
ATP
See application transaction program
(ATP)
Attach FM header (FMH-5) 10-10

Basic Alert (X'91') Alert MS
Subvector 8-16
BBI
See Begin Bracket indicator (BBI)
BCI
See Begin Chain indicator (BCI)
Beaconing Data (X'07') LAN Link
Connection Subsystem Data
Subfield 8-120
Begin Bracket indicator (BBI) 4-3, 4-9
Begin Chain indicator (BCI) 4-2, 4-4
BID 5.1-5
BIND 5.1-6
See also BIND SESSION
BIND SESSION (BIND) 5.1-6
BIS 5.1-15
See also BRACKET INITIATION STOPPED
BRACKET INITIATION STOPPED (BIS) 5.1-15
Bridge Identifier (X'OA') LAN Link
Connection Subsystem Data
Subfie1d 8-121

r--1

I

C

I

~

CANCEL 5.1-15
capacity parameter 13-8, 13-9, 13-11,
13-12
category value, sense code 9-1
See also sense data
Cause Undetermined (X'97') Alert MS
Subvector 8-79
COl
See Change Direction indicator (COl)
CEBI
See Conditional End Bracket indicator
(CEBI)
Change Direction indicator (CDI) 4-3,
4-9
Change Number of Sessions (CNOS)
command format 12-2

Index

X-I

Change Number of Sessions (X'1210') GDS
Variable GDS Variable 12-2
character-coded request A-2
character sets 13-41, A-3
CHASE S.l-IS
CLEAR S.l-IS
Code Selection indicator (CSI) 4-3, 4-9
Coded Character Set ID (X'02')
Self-Defining Text Message
Subfield 8-117
compare states
command format 12-4
Compare States (X'1213') GDS Variable
GDS Variable 12-4
Conditional End Bracket indicator
(CEBI)
4-3, 4-9
Control Vector
COS/TPF (X'2C') 8-6
Extended Sense Data (X'3S') 8-6
Fully-qualified PCID (X'60') 8-8
LU-LU Session Services Capabilities
(X'OC') 8-5
Mode (X'2D') 8-6
Network Name (X'OE') 8-S
Product Set ID (X'10') 8-6
PU FMD-RU-Usage (X'07') 8-5
SSCP-LU Session Capabilities
(X'OO') 8-4
XID Negotiation Error (X'22') 8-6
conversation-level security
Access Security Information
subfields 10-11
COS/TPF (X'2C') Control Vector 8-6
CRV S.1-15
See also CRYPTOGRAPHY VERIFICATION
CRYPTOGRAPHY VERIFICATION (CRV) 5.1-15
CSI
See Code Selection indicator (CSI)
Current N(S)/N(R) Counts (X'Ol') SDLC
Link Station Data Subfield 8-14

r---1

I

D

I

DACTLU S.1-16
See also DEACTIVATE LOGICAL UNIT
DACTPU S.1-16
See also DEACTIVATE PHYSICAL UNIT
data
distribution object 13-3, 13-31
DIU (DISTIU) type 13-6, 13-7, 13-10,
13-11, 13-13

X-2

SNA Formats

priority service level 13-8, 13-9
Data Reset Flag (X'4S') MS Common
Subvector 8-119
date and time 13-3, 13-S, 13-6, 13-21,
13-22, 13-23
Date/Time (X'Ol') MS Common
Subvector 8-10S
Date/Time Subfield
Greenwich Mean Time Offset
(X'20') 8-106
Local Date/Time (X I I0') 8-10S
DEACTIVATE LOGICAL UNIT (DACTLU) S.1-16
DEACTIVATE PHYS~CAL UNIT
(DACTPU) S.1-16
Definite Response 1 indicator
(DRII) 4-3, 4-S
Definite Response 2 indicator
(DR2I) 4-3, 4-5
DEN (distribution user element
name) 13-3, 13-5, 13-6, 13-10, 13-11,
13-13, 13-17, 13-18, 13-19, 13-21,
13-22, 13-26, 13-27, 13-28
- DEST_TPN 13-41
destination application
parameters 13-3, 13-5, 13-13
destination hop count 13-7, 13-8
destination operands 13-3, 13-4, 13-13,
13-14, 13-15, 13-20, 13-26
destination TP name 13-3, 13-7, 13-10,
13-13, 13-2S, 13-45
Detail Qualifier (EBCDIC) (X'AO') Alert
MS Subvector 8-81
Detail Qualifier (Hexadecimal) (X'A1')
Alert MS Subvector 8-82
Detailed Data (X'82') Network Alert
Common Subfield 8-93
Detailed Data (X'98') Alert MS
Subvector 8-80
Detailed Data Subfield
Qualified Message Data (X'Ol') 8-80
DGN (distribution user group
name) 13-3, 13-5, 13-6, 13-10, 13-13,
13-16, 13-17, 13-18, 13-21, 13-22,
13-26, 13-27, 13-29
DIA (Document Interchange
Architecture) 13-42
DISTIU 13-2, 13-S, 13-6, 13-34, 13-41
See also DISTRIBUTE INTERCHANGE UNIT
DISTRIBUTE INTERCHANGE UNIT
(DISTIU) 13-2
distribution
interchange units (DIUs)
See distribution interchange unit
(DIU)

user element name (DEN) 13-3, 13-5,
13-6, 13-10, 13-11, 13-13, 13-17,
13-18, 13-19, 13-21, 13-22, 13-26,
13-27, 13-28, 13-29, 13-30
user group name (DGN) 13-3, 13-5,
13-6, 13-10, 13-11, 13-13, 13-16,
13-17, 13-18, 13-21, 13-22, 13-26,
13-27, 13-29
user name (DUN) 13-6, 13-11
distribution flags 13-3, 13-7, 13-8,
13-20
distribution general options 13-3,
13-4, 13-7, 13-20
distribution identifier 13-3, 13-4,
13-5, 13-22, 13-23
distribution interchange unit (DIU)
data
semantic 13-2
status
semantic 13-2
distribution object 13-2, 13-3, 13-8,
13-25, 13-31
distribution object count 13-3, 13-7,
13-10
DISTRI BUTION_OBJ ECT _PREFI'X 13-31
distribution object prefix (DOP) 13-31,
13-43
distribution service unit (DSU)
name (DSUN) 13-13, 13-22, 13-23,
13-35, 13-38
DISTRIBUTION_STATUS_OPERANDS 13-3,
13-4, 13-21
DIU
See distribution interchange unit
(DIU)
Document Interchange Architecture
(DIA) 13-42
DRI1
See Definite Response 1 indicator
(DRII)
DR21
See Definite Response 2 indicator
(DR2I)
DSL
See service level
DSL FLDS
See service level
DSU
See distribution service unit (DSU)
DSUN (distribution service unit
name) 13-13, 13-22
DUN (distribution user name) 13-6,
13-11, 13-13

r-1

I

E

I

-----..

EBI
See End Bracket indicator (EBI)
ECI
See End Chain indicator (ECI)
EDI
,See Enciphered Data indicator (EDI)
Emulated Product Identifier (X'Ol')
Product Identifier Subfield 8-114
Enciphered Data indicator (EDI) 4-3,
4-9
Enciphered Data Structured Data
Subfield 7-4
End Bracket indicator (EBI) 4-3, 4-9
End Chain indicator (ECI) 4-3, 4-4
enhanced character string option
subset 13-41
ERI
See Exception Response indicator
(ERI)
error category
See sense data
Error Data (X'12F4') GDS Variable 14-4
Error Log (X'12El') GDS Variable 14-5
error processing
feedback
See feedback
exception class 13-33, 13-36
exception code 13-33, 13-35, 13-36
exception condition 13-33, 13-37
exception condition code 13-37
exception object code 13-38
EXCEPTION REQUEST (EXR) 4-11
Exception Response indicator (ERI) 4-3,
4-5
Exchange Log Name
command format 12-3
Exchange Log Name (X'1211') GDS Variable
GDS Variable 12-3
EXR
See EXCEPTION REQUEST (EXR)
EXR (EXCEPTION REQUEST)
sense data included with 9-1
Extended Sense Data (X'35') Control
Vector 8-6
extended sense data control vector
(X'35')
sense data included with 9-1

Index

X-3

r--l

I

F

I

------..

Failure Causes (X'Ol') Failure Causes
Subfield 8-60
Failure Causes (X'96') Alert MS
Subvector 8-59
Failure Causes Subfield
Failure Causes (X'Ol') 8-60
Fault Domain Description (X'06') LAN
Link Connection Subsystem Data
Subfield 8-120
Fault Domain Error Weight Pair (X'09')
LAN Link Connection Subsystem Data
Subfield 8-121
Fault Domain Names (X'26') LAN Link
Connection Subsystem Data
Subfield 8-122
feedback
address 13-3, 13-5, 13-10
options 13-3, 13-5, 13-11
service level 13-3, 13-11, 13-12
TP name 13-3, 13-11, 13-12
FI
See Format indicator (FI)
FID (Format Identifier) fields 3-1
FID2 3-2
FID2 Field Descriptions 3-2
FM (function management)
profiles 6-6
Usage field 6-6
FM Header 1 10-3
FM Header 10 10-15
FM Header 12: Security 10-16
FM Header 2 10-6
FM Header 3 10-7
FM Header 4 10-8
FM Header 5: Attach (LU 6.2) 10-10
FM Header 5: Attach (Not LU 6.2) 10-12
FM Header 6 10-13
FM Header 7:
Error Description (LU
6.2) 10-14
FM Header 7:
Error Description (Not LU
6.2) 10-15
FM header 8 10-15
FM Usage field 6-6
Format indicator (FI) 4-2, 4-4
Fully-qualified PCID (X'60') Control
Vector 8-8
function management (FM) headers 10-1
introduction 10-1
placement within RU 10-1
function management (FM) profiles 6-6

X-4

SNA Formats

function management header type 7
(FMH-7)
sense data included with 9-1
function option subsets
See subsets of function options

r--I
I G I

GDS
See general data stream
GDS Variable
Change Number of Sessions (X'1210')
GDS Variable 12-2
Compare States (X'1213') GDS
Variable 12-4
Exchange Log Name (X'1211') GDS
Variable 12-3
GEN_SNADS_STATUS 13-21
general application status 13-20,
13-21, 13-25, 13-29, 13-30
general data stream B-1
general data stream variable B-1
Application Data 14-3
Error Data 14-4
Error Log 14-5
Map Name 14-3
Null Data 14-3
User Control Data 14-3
general SNADS status 13-20, 13-21,
13-24, 13-29
Generic Alert Data (X'92') Alert MS
Subvector 8-20
Greenwich Mean Time Offset (X'20')
Date/Time Subfield 8-106

r--I
I H I
L..--....I

Hardware Product Common Name (XIOE')
Product Identifier Subfield 8-116
Hardware Product Identifier (X'OO')
Product Identifier Subfield 8-112
Hierarchy Name List (X'03') MS Common
Subvector 8-106
Hiera~chy Name List (X'10')
Hierarchy/Resource List Subfield 8-108
Hierarchy/Resource List (X'05') MS
Common Subvector 8-108
Hierarchy/Resource List Subfield

Hierarchy Name List (X'10') 8-108
hop count 13-3
See also destination hop count

r--1

I

I

I

~

I-frame
maximum number of 2-7
I-frames, maximum number of 2-4
INIT-SELF Format 0 5.1-17
See also INITIATE-SELF
INIT-SELF Format 1 5.1-18
See also INITIATE-SELF
INITIATE-SELF (INIT-SELF Format
0) 5.1-17
INITIATE-SELF (INIT-SELF Format
1) S.1-18
Install Causes (X'Ol') Install Causes
Subfield 8-S3
Install Causes (X'9S') Alert MS
Subvector 8-53
Install Causes Subfield
Install Causes (X'OI') 8-S3
IPM
See ISOLATED PACING MESSAGE (IPM)
IPR
See ISOLATED PACING RESPONSE (IPR)
ISOLATED PACING MESSAGE (IPM) 4-10
ISOLATED PACING RESPONSE (IPR) 4-10
IU code points 13-1, 13-42
IU segmentation 13-4, 13-32, 13-37

r--1

I

L

I

~

LAN Link Connection Subsystem Data
(X'Sl') MS Common Subvector 8-119
LAN Link Connection Subsystem Data
Subfield
Beaconing Data (X'07') 8-120
Bridge Identifier (X'OA') 8-121
Fault Domain Description
(X'06') 8-120
Fault Domain Error Weight Pair
(X'09') 8-121
Fault Domain Names (X'26') 8-122
LAN Routing Information
(X'OS') 8-120

Local Individual MAC Address
(X'03') 8-120
Local Individual MAC Name
(X'23') 8-121
Remote Individual MAC Address
(X'04') 8-120
Remote Individual MAC Name
(X'24') 8-122
Ring or Bus Identifier (X'02') 8-119
Single MAC Address (X'08') 8-121
Single MAC Name (X'28') 8-122
LAN Routing Information (X'OS') LAN Link
Connection Subsystem Data
Subfield 8-120
Last Received N(R) Count (X'08') SDLC
Link Station Data Subfield 8-16
Last SDlC Control Field Received (X'03')
SDlC link Station Data Subfield 8-15
last SDlC Control Field Sent (X'04')
SDlC link Station Data Subfield 8-15
lCS link Attributes (X'07') link
Connection Subsystem Configuration Data
Subfield 8-124
lCS link Station Attributes (X'06') link
Connection Subsystem Configuration Data
Subfield 8-124
length prefix (ll) B-1
link Connection Subsystem Configuration
Data (X'S2') MS Common Subvector 8-123
link Connection Subsystem Configuration
Data Subfield
lCS link Attributes (X'07') 8-124
lCS link Station Attributes
(X'06') 8-124
local Device Address (X'04') 8-123
LPDA Fault LSl Descriptor Subfield
(X'08') 8-124
Port Address (X'OI') 8-123
Remote Device Address (X'02') 8-123
link header 1-1, 1-2, 1-3, 1-4
link Station State (X'06') SDLC Link
Station Data Subfield 8-15
link trailer 1-1, 1-9, 1-10
lLC Reply Timer Expiration Count (X'07')
SDlC Link Station Data Subfield 8-16
Local Date/Time (X'10') Date/Time
Subfield 8-105
Local Device Address (X'04') link
Connection Subsystem Configuration Data
Subfield 8-123
local Individual MAC Address (X'03') LAN
Link Connection Subsystem Data
Subfield 8-120

Index

X-S

Local Individual MAC Name (X'23') LAN
Link Connection Subsystem Data
Subfield 8-121
LOGICAL UNIT STATUS (LUSTAT) 5.1-20
LPDA Fault LSL Descriptor Subfield
(X'08') Link Connection Subsystem
Configuration Data Subfield 8-124
LPIU
Maximum size 2-8
LU-LU Session Services Capabilities
(X'OC') Control Vector 8-5
LU-LU Session Services Capabilities
NOTIFY Vector 5.1-22
LUSTAT S.1-20
See also LOGICAL UNIT STATUS

Maximum
I-field length 2-2
RU size 6-3, 6-4, 6-5
Microcode EC Level (X'OB') Product
Identifier Subfield 8-116
Mode (X'2D') Control Vector 8-6
Mode Name Structured Data Subfield 7-2
modifier value, sense code 9-1
See also sense data
MS Common Subvector
Data Reset Flag (X'4S') 8-119
Date/Time (X'Ol') 8-10S
Hierarchy Name List (X'03') 8-106
Hierarchy/Resource List
(X'05') 8-108
LAN Link Connection Subsystem Data
(X'Sl') 8-119
Link Connection Subsystem
Configuration Data (X'S2') 8-123
Product Identifier (X'II') 8-110
Product Set ID (X'10') 8-110
Relative Time (X'42') 8-118
Self-Defining Text Message
(X'31') 8-116
Sense Data (X'7D') 8-12S
SNA Address List (X'04') 8-107
Text Message (X'OO') 8-10S
MS Major Vector
Alert (X'OOOO') 8-11
Request Response Time Monitor
(X'8080') 8-97
Response Time Monitor
(X'0080') 8-100

X-6

SNA Formats

r--1

I

N

I

L-.--.I

National Language ID (X'll')
Self-Defining Text Message
Subfield 8-117
negative response
format S.2-1
sense data included with 9-1
Network Alert Common Subfield
Detailed Data (X'82') 8-93
Product Set ID Index (X'83') 8-96
Recommended Actions (X'81') 8-82
NETWORK MANAGEMENT VECTOR TRANSPORT
(NMVT) 5.1-21
Network Name (X'OE') Control Vector 8-5
Network or Uninterpreted Name
(X'Ol') 8-9
Network-Qualified PLU Network Name
Structured Data Subfield 7-3
Network-Qualified SLU Network Name
Structured Data Subfield 7-3
NMVT 5.1-21
See also NETWORK MANAGEMENT VECTOR
TRANSPORT
NOTIFY S.1-22
NOTIFY Vector
LU-LU Session Services
Capabilities S.1-22

option subsets
See subsets of function options
ORIG_DEN 13-21
ORIG_DGN 13-21
ORIG_DTM 13-22
ORIG_REN 13-41
ORIG_RGN 13-41
ORIG_SEQNO 13-6, 13-21, 13-41
origin correlation 13-3, 13-5, 13-6,
13-22, 13-23
origin DEN 13-3, 13-S, 13-6, 13-19,
13-21, 13-22
origin DGN 13-3, 13-S, 13-6, 13-18,
13-21, 13-22
origin REN 13-3, 13-5
origin RGN 13-3, 13-S
Outstanding Frame Count (X'02') SDLC
Link Station Data Subfield 8-15

r-1

I

P

I

'-----I

Pacing indicator (PI) 4-3, 4-8
Padded Data indicator (POI) 4-3, 4-9
POI
See Padded Data indicator (POI)
PI
See Pacing indicator (PI)
PIP Subfield 10-11
PIP Variable 10-11
PIU (Path Information Unit) 1-5
Port Address (X'Ol') Link Connection
Subsystem Configuration Data
Subfield 8-123
PREFIX 13-2, 13-3, 13-4, 13-31, 13-34,
13-35, 13-36, 13-38, 13-42
presentation services (PS) headers
definition 11-1
format 11-1
priority parameter 13-8, 13-9, 13-11,
13-12
priority service levels
data 13-8, 13-9
fast 13-8, 13-9, 13-11, 13-12
status 13-9, 13-11, 13-12
Probable Causes (X'93') Alert MS
Subvector 8-30
Product Identifier (X'll') MS Common
Subvector 8-110
Product Identifier Subfield
Emulated Product Identifier
(X'Ol') 8-114
Hardware Product Common Name
(X'OE') 8-116
Hardware Product Identifier
(X'OO') 8-112
Microcode EC Level (X'OB') 8-116
Software Product Common Level
(X'04') 8-114
Software Product Common Name
(X'06') 8-115
Software Product Customization Date
and Time (X'09') 8-115
Software Product Customization
Identifier (X'07') 8-115
Software Product Program Number
(X'08') 8-115
Software Product Serviceable
Component Identifier (X'02') 8-114
Product Set 10 (X'10') Control
Vector 8-6

Product Set 10 (X'10') MS Common
Subvector 8-110
Product Set 10 Index (X'83' ) Network
Alert Common Subfield 8-96
profiles
FM (function management) 6-6
FM p,rofile 0 6-7
FM profile 18 6-12
FM profile 19 6-13
FM profile 2 6-7
FM profile 3 6-8
FM profile 4 6-9
FM profile 6 6-10
FM profile 7 6-11
TS (transmission services) 6-2
TS profile 1 6-3
TS profile 2 6-3
TS profile 3 6-4
TS profile 4 6-4
TS profile 7 6-5
protection parameter 13-8, 13-9, 13-11,
13-12
PS Header 10: Sync Point Control 11-2
PU FMD-RU-Usage (X'07') Control
Vector 8-5

r--1
Q I

I

~

QC

5.1-22
See also QUIESCE COMPLETE
QEC 5.1-23
See also QUIESCE AT END OF CHAIN
QRI
See Queued Response indicator (QRI)
Qualified Message Data (X'Ol') Detailed
Data Subfield 8-80
Queued Response indicator (QRI) 4-3,
4-6
QUIESCE AT END OF CHAIN (QEC) 5.1-23
QUIESCE COMPLETE (QC) 5.1-22

r--1
R I

I

~

Random Data Structured Data
Subfield 7-3
READY TO RECEIVE (RTR) 5.1-39
RECEIVING_DSUN 13-21, 13-22, 13-23,
13-35, 13-38

Index

X-7

RECFMS 5.1-23
See also RECORD FORMATTED MAINTENANCE
STATISTICS
Recommended Actions (X'81') Network
Alert Common Subfield 8-82
RECORD FORMATTED MAINTENANCE STATISTICS
(RECFMS) 5.1-23
Relative Time (X'42') MS Common
Subvector 8-118
RELEASE QUIESCE (RELQ) 5.1-37
RELQ 5.1-37
See also RELEASE QUIESCE
Remote Device Address (X'02') Link
Connection Subsystem Configuration Data
Subfield 8-123
Remote Individual MAC Address (X'04')
LAN Link Connection Subsystem Data
Subfield 8-120
Remote Individual MAC Name eX'24') LAN
Link Connection Subsystem Data
Subfield 8-122
REPLY_DATA 13-35, 13-36, 13-38, 13-42
REQMS 5.1-37
See also REQUEST MAINTENANCE
STATISTICS
request header 4-1
Request Larger Window indicator
(RLWI) 4-3, 4-9
REQUEST MAINTENANCE STATISTICS
(REQMS) 5.1-37
request no feedback 13-7
REQUEST RECOVERY (RQR) 5.1-38
request/response header (RH) 4-2, 4-4
discussion of bit usage and
values 4-4-4-9
format and bit settings 4-2
Request/Response Indicator eRRI) 4-2,
4-4
Request Response Time Monitor (X'8080')
MS Major Vector 8-97
Request/Response Unit Category 4-2, 4-4
Request RTM MS Subvector
RTM Control (X'94') 8-99
RTM Request (X'92') 8-98
REQUEST SHUTDOWN (RSHUTD) 5.1-38
reserved
bits and fields 5.1-1
values 5.1-1
Response Time Monitor (X'0080') MS Major
Vector 8-100
Response Type indicator (RTI) 4-3, 4-7
RGN (routing group name) 13-13
RH
See request/response header (RH)

X-8

SNA Formats

Ring or Bus Identifier (X'02') LAN Link
Connection Subsystem Data
Subfield 8-119
RLWI
See Request Larger Window indicator
(RLWI)
RQR 5.1-38
See also REQUEST RECOVERY
RRI
See Request/Response Indicator eRRI)
RSHUTD 5.1-38
See also REQUEST SHUTDOWN
RSP(ACTLU) 5.2-3
RSP(ACTPU) 5.2-3
RSP(BIND) 5.2-4
RSP(STSN) 5.2-6
RTI
See Response Type indicator (RTI)
RTM Control (X'94') Request RTM MS
Subvector 8-99
RTM Data (X'93') RTM MS Subvector 8-103
RTM MS Subvector
RTM Data (X'93') 8-103
RTM Status Reply (X'91') 8-102
RTM Request (X'92') Request RTM MS
Subvector 8-98
RTM Status Reply (X'91') RTM MS
Subvector 8-102
RTR 5.1-39
See also READY TO RECEIVE
RU Category
See Request/Response Unit Category
RU size, maximum 6-3, 6-4, 6-5

r---1
S I

I
SBI

5.1-39
See also STOP BRACKET INITIATION

SDI
See Sense Data Included indicator
(SDI)
SDLC frames 1-1
link header (LH) 1-1
address 1-3
control field 1-4
flag 1-2
link trailer (LT) 1-1
flag 1-10
frame check sequence 1-9
SDLC Link Station Data (X'8C') Alert MS
Subvector 8-14

SDLC Link Station Data Subfield
Current N(S)/N(R) Counts
(X'OI') 8-14
Last Received N(R) Count
(X'08') 8-16
Last SDLC Control Field Received
(X'03') 8-1S
Last SDLC Control Field Sent
(X'04') 8-1S
Link Station State (X'06') 8-1S
LLC Reply Timer Expiration Count
(X'07') 8-16
Outstanding Frame Count (X'02') 8-1S
Sequence Number Modulus (X'OS') 8-1S
SDT S .1-39
See also START DATA TRAFFIC
Self-Defining Text Message (X'31') MS
Common Subvector 8-116
Self-Defining Text Message Subfield
Coded Character Set ID (X'02') 8-117
National Language ID (X'll') 8-117
Sender ID (X'21') 8-118
Text Message (X'30') 8-118
Sender ID (X'21') Self-Defining Text
Message Subfield 8-118
sense code
See sense data
sense data 9-1
format of 9-1
sense code
category X'OO' (user sense data
only) 9-1, 9-2
category X'08' (request
reject) 9-2, 9-1
category X'10' (request
error) 9-42, 9-1
category X'20' (state
error) 9-S3, 9-1
category X'40' (RH usage
error) 9-SS, 9-1
category X'80' (path error) 9-S7,
9-1
modifier 9-1
modifier value of X'OO' 9-2
sense-code specific information 9-1
user-defined data 9-2
Sense Data (X'7D') MS Common
Subvector 8-12S
sense data included with 9-1
Sense Data Included indicator
(SDI) 4-2, 4-4
sequence number 13-3, 13-S, 13-6,
13-21, 13-22, 13-41

Sequence Number Modulus (X'OS') SDLC
Link Station Data Subfield 8-1S
SERVER_NAME 13-3, 13-2S, 13-31, 13-41,
13-4S
SERVER_PARMS 13-2S
service level
parameter description
capacity 13-8, 13-12
priority 13-8, 13-11
protection 13-8, 13-11
Session Instance Identifier Structured
Data Subfield 7-2
Session Keys
table of 8-9
session-level security
FMH-12 10-16
Session Qualifier Structured Data
Subfield 7-2
SET AND TEST SEQUENCE NUMBERS
(STSN) S.1-40
SHUTC S.1-39
See also SHUTDOWN COMPLETE
SHUTD 5.1-39
See also SHUTDOWN
SHUTDOWN (SHUTD) S.1-39
SHUTDOWN COMPLETE (SHUTC) S.1-39
SIG S.1-39
See also SIGNAL
SIGNAL (SIG) S.1-39
Single MAC Address (X'08') LAN Link
Connection Subsystem Data
Subfield 8-121
Single MAC Name (X'28') LAN Link
Connection Subsystem Data
Subfield 8-122
SNA Address List (X'04') MS Common
Subvector 8-107
SNF processing 3-3
Software Product Common Level (X'04')
Product Identifier Subfield 8-114
Software Product Common Name (X'06')
Product Identifier Subfield 8-11S
Software Product Customization Date and
Time (X'09') Product Identifier
Subfield 8-11S
Software Product Customization
Identifier (X'07') Product Identifier
Subfield 8-11S
Software Product Program Number (X'08')
Product Identifier Subfield 8-11S
Software Product Serviceable Component
Identifier (X'02') Product Identifier
Subfield 8-114

Index

X-9

specific application status 13-25,
13-28, 13-29, 13-30
specific SNADS status 13-24, 13-28,
13-29
SSCP-LU Session Capabilities (X'OO')
Control Vector 8-4
stack reference indicator (SRI)
contained in FMH-2
functions and codes 10-6
START DATA TRAFFIC (SDT) 5.1-39
STAT_CaRREL 13-21
status
DIU (DISTIU) type 13-6, 13-7, 13-13,
13-20
priority service level 13-8, 13-9,
13-11, 13-12
status correlation 13-21, 13-22
STOP BRACKET INITIATION (SBI) 5.1-39
Structured Data Subfield
Enciphered Data 7-4
Mode Name 7-2
Network-Qualified PLU Network
Name 7-3
Network-Qualified SLU Network
Name 7-3
Random Data 7-3
Session Instance Identifier 7-2
Session Qualifier 7-2
Unformatted Data 7-2
structured fields B-1
See also general data stream
STSN 5.1-40
See also SET AND TEST SEQUENCE
NUMBERS
subsets of function options
enhanced character string option
subset 13-41
SUFFIX 13-2, 13-3, 13-32, 13-34, 13-35,
13-37, 13-38, 13-40, 13-42
Suffix type 1 13-32, 13-43
Suffix type 2 13-32, 13-43
suffix T2 13-32, 13-33
Symbol-String Types A-I
sync point protocols
RH bit settings 4-6, 4-8
Synchronous Data Link Control
See SDLC

TERM-SELF 5.1-40, 5.1-41
See also TERMINATE-SELF
TERM-SELF Format 0
See TERMINATE-SELF
TERM-SELF Format 1
See TERMINATE-SELF
TERMINATE-SELF (TERM-SELF) 5.1-40,
5.1-41
Text Message (X'OO') MS Common
Subvector 8-105
Text Message (X'30') Self-Defining Text
Message Subfield 8-118
token-ring network DLC 1-1, 1-11
transmission header (TH)
FID2 3-2
transmission services (TS) profiles 6-2
TS (transmission services)
profiles 6-2
Usage field 6-2
TS Usage field 6-2

r--1

I

U

I

'-----'

UNBIND 5.1-42
See also UNBIND SESSION
sense data included with 9-1
UNBIND SESSION (UNBIND) 5.1-42
Unformatted Data Structured Data
Subfield 7-2
URC (X'OA~) 8-9
User Causes (X'Ol') User Causes
Subfield 8-45
User Causes (X'94') Alert MS
Subvector 8-45
User Causes Subfield
User Causes (X'Ol') 8-45
USS symbol-string type A-2

r--1

I

X

I

'-----'

XID Negotiation Error (X'22') Control
Vector 8-6

X-I0

SNA Formats

Reader's Comment Form
Systems Network Architecture
Formats
Publication No. GA27 -3136-9
This manual is part of a library that serves as a reference source for systems
analysts, programmers, and operators of IBM systems. You may use this form to
communicate your comments about this publication, its organization, or subject .
matter, with the understanding that IBM may use or distribute whatever information
you supply in any way it believes appropriate without incurring any obligation to
you.
Note: Copies of IBM Publications are not stocked at the location to which this form
is addressed. Please direct any requests for copies of publications, or for
assistance in using your IBM system, to your IBM representative or to the IBM
branch office serving your locality.
Possible topics for comment are: clarity, accuracy, completeness, organization,
coding, retrieval, and legibility.
Comments:

What is your occupation?
If you wish a reply, give your name, company, mailing address, and date:

Thank you for your cooperation. No postage stamp necessary if mailed in the
U.S.A. (Elsewhere, an IBM office representative will be happy to forward your
comments or you may mail directly to the address in the Edition Notice on the back
of the title page.)

PDR3136

PAGE:

2

PRINTED:

JUNE 1,

1988

16:0"

GA27 -3136-9

Reader's Comment Form

Please Do Not Staple

Fold and tape

Fold and tape

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY MAIL
FIRST CLASS

PERMIT NO. 40

ARMONK, N.Y.

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines Corporation
Dept. E95
P.O. Box 12195
Research Triangle Park, N.C. 27709-9990

Fold and tape

--- -- -----------, ®

-

Please Do Not Staple

Fold and tape

---- ---- ------- --

--_ .-

Publication Number

GA27-3136-9
Printed in USA

GA27 - 3 1 36 - 09



---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37
Create Date                     : 2013:01:08 18:18:03-08:00
Modify Date                     : 2013:01:08 18:40:49-08:00
Metadata Date                   : 2013:01:08 18:40:49-08:00
Producer                        : Adobe Acrobat 9.52 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:bec6b516-248f-403b-acbd-19a1af923cc4
Instance ID                     : uuid:45002cf5-5e10-4dfb-be7e-7962184036db
Page Layout                     : SinglePage
Page Mode                       : UseOutlines
Page Count                      : 420

EXIF Metadata provided by EXIF.tools