GA27 3136 10_SNA_Formats_Jun89 10 SNA Formats Jun89

GA27-3136-10_SNA_Formats_Jun89 GA27-3136-10_SNA_Formats_Jun89

User Manual: GA27-3136-10_SNA_Formats_Jun89

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

Download
Open PDF In Browser	View PDF

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

Systems Network Architecture

Formats

GA27-3136-10

----- -- -----'- -- --------cr

~ .....

----

{
\

'--

Systems Network Architecture

Formats

GA27-3136-10

Eleventh Edition (June 1989)

This edition, GA27-3136-10, is a major revision of the previous edition, GA27-3136-9, and obsoletes that
edition; it applies until otherwise indicated in a new edition. Consult Part 3 of the latest edition of IBM
System/370, 30xx. and 4300 Processors - Bibliography, GC20-0001, for current information on this communication architecture. For a summary of the changes in this book, see "Summary of Changes."
The following statement does not apply to the United Kingdom or any country where such provisions
are inconsistent with local law: International Business Machines 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. Within the United States, some states do
not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement
may not apply to iou.
II

Order publications through your IBM representative or the IBM branch office serving your locality.
Publications are not stocked at the address given below.
A form for your comments is provided at the back of this publication. If the form has been removed,
address your comments to:
IBM Corporation
Department E89
P.O. Box 12195
Research Triangle Park, North Carolina 27709, U.S.A.
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you or restricting your use
of it.
Note to US Government users - Documentation related to Restricted Rights - Use, duplication, and disClosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.

Special Notices
References in this publication to IBM products, programs or services do not
imply that IBM intends to make these available in all countries in which IBM
operates.
Any reference to an IBM licensed program or other IBM product in this publication is not intended to state or imply that only IBM's program or other product
may be used.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license
to use these patents. You can send license inquiries, in writing, to the IBM
Director of Commercial Relations, IBM Corporation, Purchase, New York 10577.
This publication may include references to microcode. Some IBM products
contain microcode classified as Licensed Internal Code. Licensed Internal
Code is provided under terms and conditions set forth in IBM agreements, such
as the Agreement for Purchase of IBM Machines and the Agreement for Lease
or Rental of IBM Machines.
IBM is a registered trademark of the International Business Machines Corporation.

"'-.

Special Notices

iii

SNA Formats

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. Figure 1-1 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 in
an SOLC and System/370 OLC Exchange Identification (XIO) command and
response.
Chapter 3 identifies the formats and meanings of the bytes in a transmission
header.

1,---

Chapter 4 identifies the formats and meanings of the bytes in a request or
response header.
Chapter 5 identifies the formats and meanings of the bytes in request units and
response units.
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 in 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, for example, in negative response units.
Chapter 10 presents the descriptions and formats of the different function management headers.
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
(GOS) variables that are specific to SNA service transaction programs.

Preface

Chapter 13 identifies the formats and meanings of the message units that
SNA/Oistribution Services transaction programs use.
Chapter 14 identifies the general data stream (GOS) variables that are for
general use.
Chapter 15 identifies the formats and meanings of the message units that
SNA/File Services transaction programs use.
Appendix A provides a summary of SNA character sets and symbol-string
types.
Appendix B provides a summary of general data stream identifier (GOS 10)
value assignments.
Appendix C lists the abbreviations and symbols that are used in 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: Sessions Between Logical Units (GC20-1868)
• Systems Network Architecture: Transaction Programmer's Reference
Manual for LU Type 6.2 (GC30-3084)

• Systems Network Architecture Format and Protocol Reference Manual:
Architecture LogiC for LU Type 6.2 (SC30-3269)
• Systems Network Architecture LU 6.2 Reference: Peer Protocols
(SC30-6808)
• Systems Network Architecture/Distribution Services Reference (SC30-3098)
• Systems Network Architecture/File Services Reference (SC31-6807)
• Systems Network Architecture/Management Services Reference (SC30-3346)
• Token-Ring Network Architecture Reference (SC30-3374)
• Document Interchange Architecture: Technical Reference (SC23-0781)
• IBM Implementation of X.21 Interface General Information Manual
(GA27-3287)

SNA Formats

Messago
Unit
Format
Chapter 1

Inla,matlan Field

I LH I

Chapter 2

(SDLC)

Chapter 3

Chapter 4

IRHI

~
(Response)

Negative
Response

"-Chapter 6

•
RU

.....

Positive
Response

SNA-Deflned
Data

TS Profiles
FM Profiles

Control Vectors

End-User
Data

Control Vectors
Session Keys
MS Vectors

Sense Data

Chapter 10

FM Headers

Chapter 11

PS Headers

Chapter 12

SNASTPs

Chapter 13

SNA/DS (MU)

Chapter 14

GDS Variables

Chapter 15

SNA/FS (MU)
LH
LT
XID
TH
RH
RU
TS
FM
MS

Figure

..,J

Structured
Subfields

Chapter 8

..-'

..,J

Chapter 7

BIU

(Request)

RU
.....

RU
........

Chapter 9

PIU

Chapter 5

BLU

I LT I

=
=
=
=

=
=
=

=
=

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

PS
STP
SNA/DS
MU
GDS
BLU
PIU
BIU
SNA/FS

= Presentation Services
= Service Transaction Program
= SNA/Distribution Services
= Message Unit

= General Data Stream
=
=
=
=

Basic Link Unit
Path Information Unit
Basic Information Unit
SNA/File Services

1-1. Organization of thi s Book

Preface

vii

viii

SNA Formats

Summary of Changes
Additions for GA27·3136·10:
This edition includes information about:
• Network Asset Management
• Change Management
• Common Operations Services
• SNA/File Services

Changes from the previous edition:
• The style of presentation of the formats has been changed.
• An enhanced format set has been provided for SNAIDistribution Services
• Chapters 5.1 and 5.2 have been combined into Chapter 5.

Summary of Changes

SNA Formats

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

1-1
1-1
1-1
1-2
1-3
1-5
1-7
1-7

Chapter 2. Exchange Identification (XID) Information Fields . . . . . . . . . . . . . . . . . . . . . . . . 2-1
DLC XID Information-Field Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Chapter 3. Transmission Headers (THs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FID2 Layout
...................................................
FID2 Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

"'-.

"--

3-1
3-1
3-1
3-1

Chapter 4. Request/Response Headers (RHs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
RH Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
IPR, IPM, and EXR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
ISOLATED PACING RESPONSE (IPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
ISOLATED PACING MESSAGE (IPM)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
EXCEPTION REQUEST (EXR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Chapter 5. Request/Response Units (RUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 (ACTIVATE LOGICAL UNIT)
...................................
ACTPU (ACTIVATE PHYSICAL UNIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BID (BID)
...................................................
BIND (BIND SESSION)
...........................................
BIS (BRACKET INITIATION STOPPED) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CANCEL (CANCEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHASE (CHASE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLEAR (CLEAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CRV (CRYPTOGRAPHY VERIFICATION) . . . . . . . . . '. . . . . . . . . . . . . . . . . . . . . ..
DACTLU (DEACTIVATE LOGICAL UNIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DACTPU (DEACTIVATE PHYSICAL UNIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INIT-SELF Format 0 (INITIATE-SELF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INIT-SELF Format 1 (INITIATE-SELF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LUSTAT (LOGICAL UNIT STATUS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NMVT (NETWORK MANAGEMENT VECTOR TRANSPORT) . . . . . . . . . . . . . . . . . . . . .
NOTIFY (NOTIFY)
.............................................
NOTIFY Vectors (Described O-origin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILU/TLU Notification NOTIFY Vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
LU-LU Session Services Capabilities NOTIFY Vector
......................
NSPE (NS PROCEDURE ERROR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1
5-1
5-2
5-2
5-2
5-4
5-4
5-4
5-5
5-5
5-15
5-16
5-16
5-16
5-17
5-17
5-18
5-19
5-21
5-22
5-23
5-24
5-25
5-25
5-26
5-27

Contents

QC (QUIESCE COMPLETE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QEC (QUIESCE AT END OF CHAIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RECFMS (RECORD FORMATTED MAINTENANCE STATISTICS) . . . . . . . . . . . . . . . . .
RELQ (RELEASE QUIESCE)
......................................
REQDISCONT (REQUEST DISCONTACT)
..............................
REQMS (REQUEST MAINTENANCE STATISTICS)
.........................
RQR (REQUEST RECOVERY)
......................................
RSHUTD (REQUEST SHUTDOWN)
...................................
RTR (READY TO RECEIVE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SBI (STOP BRACKET INITIATION)
...................................
SDT (START DATA TRAFFIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHUTC (SHUTDOWN COMPLETE)
...................................
SHUTD (SHUTDOWN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIG (SIGNAL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STSN (SET AND TEST SEQUENCE NUMBERS) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TERM-SELF Format 0 (TERMINATE-SELF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TERM-SELF Format 1(TERMINATE-SELF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNBIND (UNBIND SESSION) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Response Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Positive Response Units with Extended Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSP(ACTLU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSP(ACTPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSP(BIND)
.................................................
RSP(STSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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
Chapter 7. User Data Structured Subfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Descriptions
.................................................
Unformatted Data Structured Data Subfield . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Qualifier Structured Data Subfield . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mode Name Structured Data Subfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Instance Identifier Structured Data Subfield . . . . . . . . . . . . . . . . . . . . . .
Network-Qualified PLU Network Name Structured Data Subfield . . . . . . . . . . . . . . .
Network-Qualified SLU Network Name Structured Data Subfield . . . . . . . . . . . . . . .
Random Data Structured Data Subfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enciphered Data Structured Data Subfield

xii

SNA Formats

.
.

. ..
. ..
.
.

5-28
5-29
5-29
5-29
5-30
5-30
5-30
5-31
5-31
5-31
5-32
5-32
5-32
5-33
5-33
5-34
5-35
5-37
5-39
5-41
5-41
5-41
5-42
5-44

6-1
6-1
6-1
6-2
6-2
6-2
6-2

6-3
6-3
6-4
6-4
6-4
6-5

6-6
. ..

6-6

6-6
6-7

.
.
.
.
.
.
.
.

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

Chapter 8. Common Fle!ds
Introduction . . . . . . . . .
Substructure Encoding/Parsing Rules
Rules for Common Substructures
Partitioning of Key/Type Values
Category-Dependent Keys
Context-Sensitive Keys
......... .
Parsing Rules
Enclosing Rule for Substructures
Control Vectors . . . . . . .
Introduction
Control Vector Formats . . . . . . . . . . . . . . . . . . . . . . . . . . .
SSCP-LU Session Capabilities (XIOOI) Control Vector
LU-LU Session Services Capabilities (XIOCI) Control Vector
Network Name (XIOEI) Control Vector ... .
Prod u ct Set 10 (X I 10 I) Control Vector . . . . . .
XID Negotiation Error (X 122 I) Control Vector
COS/TPF (X I 2C I) Control Vector . . . . . . .
Mode (X 120 I) Control Vector . . . . . . . . .
Extended Sense Data (X 135 1) Control Vector
Fully-qualified PCID (X 160 I) Control Vector .
Session Key
..................... .
Network Name Pair or Uninterpreted Nam~ Pair (X I 06 1) Session Key
URC (XIOAI) Session Key . . . . . . . . . . . .
. ...... .
MS Major Vectors and Unique Subvectors
Introduction . . . . . . . . . . . . . .
MS Major Vector Formats
Alert (X 10000 I) MS Major Vector
Alert MS Subvectors . . . . . . .
SDLC Link Station Data (X I 8CI) Alert MS Subvector
...... .
Current N(S)/N(R) Counts (X 101 1) SDLC Link Station Data Subfield
Outstanding Frame Count (X 1021) SDLC Link Station Data Subfield
Last SDLC Control Field Received (X 103 1) SDLC Link Station Data Subfield
Last SDLC Control Field Sent (X I 041) SDLC Link Station Data Subfield
Sequence Number Modulus (X 105 1) SDLC Link Station Data Subfield ... .
Link Station State (X 106 1) SDLC Link Station Data Subfield . . . . . . . . . .
LLC Reply Timer Expiration Count (X 107 1) SDLC Link Station Data Subfield
Last Received N(R) Count (X 108 1) SDLC Link Station Data Subfield
Basic Alert (X 1911) Alert MS Subvector
Generic Alert Data (X 192 I) Alert MS Subvector
Probable Causes (X 193 1) Alert MS Subvector
User Causes (X 1941) Alert MS Subvector
User Causes (X I 011) User Causes Subfield
Install Causes (X 195 1) Alert MS Subvector
Install Causes (X 1011) Install Causes Subfield
Failure Causes (X 196 1) Alert MS Subvector ...
Failure Causes (X 1011) Failure Causes Subfield
Cause Undetermined (X 197 1) Alert MS Subvector
Detailed Data (X 198 I) Alert MS Subvector . . . . .
Qualified Message Data (X 1011) Detailed Data Subfield
Detail Qualifier (EBCDIC) (X I AO I) Alert MS Subvector
Detail Qualifier (Hexadecimal) (X I A11) Alert MS Subvector
Network Alert (X 10000 I) Common Subfields . . . . . . . . .

8-1
8-1
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-6
8-6
8-7
8-7
8-8
8-8
8-10
8-11
8-11
8-11
8-12
8-12
8-13
8-13
8-16
8-16
8-16
8-16
8-17
8-17
8-17
8-18
8-18
8-19
8-19
8-24
8-35
8-52
8-53
8-62
8-63
8-70
8-70
8-93
8-94
8-94
8-96
8-96
8-97

Contents

xiii

Recommended Actions (X 1811) Network Alert Common Subfield
Detailed Data (X 182 I) Network Alert Common Subfield
Product Set 10 Index (X 183 I) Network Alert Common Subfield
Request Change Control (X I 8050 1) MS Major Vector ..
Request Change Control MS Subvectors . . . . . . . . .
Install (X 1811) Request Change Control MS Subvector
Removability (X 120 I) Install Subfield
Activation Use (X 130 I) Install Subfield
Pre-Test (X 140 I) Install Subfield
Automatic Removal (X I 50 1) Install Subfield
Post-Test (X I 60 1) Install Subfield . . . . . .
Automatic Acceptance (X 170 I) Install Subfield .
Remove (X 183 1) Request Change Control MS Subvector
Post-Test (X 160 I) Remove Subfield
.......... .
Accept (X 185 1) Request Change Control MS Subvector .
Corequisite Change (X 187 1) Request Change Control MS Subvector
Change Control (X I 0050 1) MS Major Vector . . . . . . . . . . .
Change Control MS Subvectors . . . . . . . . . . . . . . . . . . .
Reporting Installation (X 182 I) Change Control MS Subvector
Installation Status (X 110 I) Reporting Installation Subfield
Removability Status (XI201) Reporting Installation Subfield
Activation Use Status (X 130 I) Install Subfield . . . . . . . .
Pre-Test Status (X 140 I) Reporting Installation Subfield
Automatic Removal Status (X 150 I) Reporting Installation Subfield
.... .
Post-Test Status (X 160 I) Reporting Installation Subfield . . . . . . . ... .
Automatic Acceptance Status (X 170 I) Reporting Installation Subfield ... .
Reporting Removal (X 1841) Change Control MS Subvector
Removal Status (X 110 I) Reporting Removal Subfield . . . .
Post-Test Status (X I 60 1) Reporting Removal Subfield
Reporting Acceptance (X 186 I) Change Control MS Subvector
Accept Status (X 110 I) Reporting Acceptance Subfield· ...
Reported Change Name (X 188 I) Change Control MS Subvector
Reporting Secondary Installation (X 18A I) Change Control MS Subvector
Installation Status (X 110 I) Reporting Secondary Installation Subfield
Activation Use Status (X 130 I) Reporting Secondary Installation Subfield
Secondary Installation Change Name (X 18C I) Change Control MS Subvector
Reporting Back-Level Status (X 18E I) Change Control MS Subvector .
Back-Level Status (X 110 I) Reporting Back-Level Status Subfield
Back-Level Change Name (X 190 I) Change Control MS Subvector
Reporting Deletion (X 192 I) Change Control MS Subvector ..
Deletion (X 110 I) Reporting Deletion Subfield
........ .
Deleted Change Name (X 1941) Change Control MS Subvector
Detailed Data (X 198 I) Change Control MS Subvector
...... .
Execute Command (X I 80611) MS Major Vector
Reply to Execute Command (X 100611) MS Major Vector .
Analyze Status (X 180621) MS Major Vector . . . . .
Reply to Analyze Status (X 100621) MS Major Vector
Query Resource Data (X 18063 I) MS Major Vector .
Reply to Query Resource Data (X 10063 I) MS Major Vector
Test Resource (X I 80641) MS Major Vector . . . . . . . .
Test Resource Subvectors . . . . . . . . . . . . . . . . . .
Test Setup Data (X I 80 1) Test Resource MS Subvector

xiv

SNA Formats

8-97
8-109
8-114
8-115
8-116
8-116
8-117
8-117
8-118
8-118
8-118
8-119
8-119
8-120
8-120
8-120
8-121
8-123
8-123
8-123
8-124
8-124
8-125
8-125
8-126
8-126
8-126
8-127
8-127
8-128
8-128
8-128
8-129
8-129
8-130
8-130
8-130
8-131
8-131
8-131
8-132
8-132
8-132
8-133
8-133
8-134
8-135
8-136
8-137
8-138
8-138
8-138

Test Request Count (X 101 1) Test Setup Data Subfield . . . . . . . . . .
Reply to Test Resource (X 10064 1) MS Major Vector
Reply to Test Resource Subvectors . . . . . . . . . . . . . . . . . . .
Test Result Data (X 1811) Reply to Test Resource MS Subvector
Test Execution Result (X 101 1) Test Result Data Subfield
Test Type (X I 021) Test Result Data Subfield . . . . . .
Test Request Count (X I 03 1) Test Result Data Subfield
Test Executed Count (X I 041) Test Result Data Subfield
Request Activation (X 18066 I) MS Major Vector
Request Activation MS Subvectors . . . . . . . . . . .
....... .
Activate (X I 811) Request Activation MS Subvector
Force Indication (X 110 I) Activate Subfield
........ .
Change Management Activation Use (X 120 I) Activate Subfield .
Reply Activation Acceptance (X 10066 1) MS Major Vector . . . . . . .
Activation Acceptance MS Subvectors
................. .
Activation Acceptance (X 1821) Activation Acceptance MS Subvector
Attempt Status (X 110 I) Activation Acceptance Subfield
Send Message to Operator (X 1006F I) MS Major Vector
Request Response Time Monitor (X 18080 I) MS Major Vector
Request Response Time Monitor Subvectors
RTM Request (X I 921) Request RTM MS Subvector
RTM Control (X I 94 1) Request RTM MS Subvector
Response Time Monitor (X I 0080 1) MS Major Vector
Response Time Monitor Subvectors . . . . . . . .
RTM Status Reply (X I 91 1) RTM MS Subvector
RTM Data (X I 93 I) RTM MS Subvector . . . . .
Request Product Set ID (X 18090 I) MS Major Vector
Request Product Set ID Subvectors . . . . . . . . .
Node Identification (X 1811) Request PSID MS Subvector
Node and Port-Attached Devices Identification (X 183 1) Request PSID MS Subvector
Reply Product Set ID (X I 0090 1) MS Major Vector . . . . . . . . . . . . . . . . . . . . . .
Reply Product Set ID Subvectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port-Attached Device Configuration Description (X 1821) Reply PSID MS Subvector
Port Number (X 110 I) Port-Attached Device Config. Des. Subfield
........ .
Power-on Status (X 120 I) Port-Attached Device Config. Des. Subfield . . . . . . .
Power-on Since Last Solicitation (X 130 I) Port-Attached Device Config. Des. Subfield
Text Data (XI1300 1) MS Parameter Major Vector
Structured Data (X 11307 1) MS Parameter Major Vector
Structured Data Subvectors . . . . . . . . . . . . . . . .
Resource Data (X 180 I) Structured Data MS Subvector
Resource Item Name (X 1011) Resource Item Name Subfield
Resource Item Hex Value (X I 02 I) Resource Data Subfield
Resource Item Character Value (X 103 1) Resource Data Subfield
Resource Item Integer Value (X 1041) Resource Data Subfield
Resource Item Bit String Value (X I 05 1) Resource Data Subfield
Transparent Coded Datastream(X 11309 I) MS Parameter Major Vector
Begin Data Parameters (X 1130A I) MS Parameter Major Vector
Begin Data Parameters Subvectors . . . . . . . . . . . . . . . . . . .
Resource State (X 182 I) Begin Data Parameters MS Subvector
Probable Causes (X I 93 I) Begin Data Parameters MS Subvector
End Parameter Data (X 1130B I) MS Parameter Major Vector
MS Common Subvectors . . . . . . . . . . . . . . . .
Text Message (XIOOI) MS Common,Subvector . . . . . . . . . . . . .
Contents

8-139
8-139
8-140
8-140
8-141
8-141
8-142
8-142
8-142
8-143
8-143
8-143
8-144
8-144
8-145
8-145
8-145
8-146
8-147
8-148
8-148
8-148
8-150
8-151
8-151
8-153
8-154
8-155
8-155
8-156
8-156
8-157
8-157
8-158
8-158
8-158
8-159
8-160
8-160
8-160
8-161
8-161
8-162
8-162
8-162
8-163
8-163
8-164
8-164
8-164
8-165
8-165
8-165
XV

Date/Time (X I 011) MS Common Subvector . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Date/Time (XI101) Date/Time Subfield . . . . . . . . . . . . . . . . . . . . . . . . .
Greenwich Mean Time Offset (XI201) Date/Time Subfield
. . . . .
Hierarchy Name List (X 103 I) MS Common'Subvector . . . .
. . . . .
SNA Address List (X 1041) MS Common Subvector . . . . . .
Hierarchy/Resource List (X I 05 1) MS Common Subvector . .
Hierarchy Name List (X 110 I) Hierarchy/Resource List Subfield
Name List (X I 06 1) MS Common Subvector . . . . . . . . . . .
Associated Resource Name List (X 1011) Name List Subfield
Destination Application Name (X I 50 1) Name List Subfield .
Qualified Message (XIOAI) MS Common Subvector . . . .
. . . . . . . .
Message 10 (X 1011) Qualified Message Subfield
. . . . . .
Replacement Text (X 1021) Qualified Message Subfield
. . . . . .
Product Set 10 (XI101) MS Common Subvector . . . . . .
. . . . .
Product Identifier (X 1111) MS Common Subvector . . . .
. . . . . .
Hardware Product Identifier (XIOOI) Product 10 Subfield
. . . . . .
Emulated Product Identifier (X 101 1) Product 10 Subfield . . . . . . . . . . .
Software Product Serviceable Component Identifier (X 1021) Product 10 Subfield
Software Product Common Level (X I 041) Product 10 Subfield
.....
1
Software Product Common Name (X 106 ) Product 10 Subfield . . . . . . .
Software Product Customization Identifier (X I 071) Product 10 Subfield
Software Product Program Number (X I 08 1) Product 10 Subfield . . . . . .
Software Product Customization Date and Time (X I 09 1) Product 10 Subfield
Microcode EC Level (XIOB I) Product 10 Subfield . . . . . . . . . . . . .
Hardware Product Common Name (X 10E I) Product 10 Subfield
Self-Defining Text Message (X 1311) MS Common Subvector . . . . . . . .
Coded Character Set 10 (X 102 I) Self-Defining Text Message Subfield .
National Language 10 (X 112 I) Self-Defining Text Message Subfield
Sender 10 (X 1211) Self-Defining Text Message Subfield
. . . . .
Text Message (X 130 I) Self-Defining Text Message Subfield
. . . . . . . . . . . .
Relative Time (X 142 I) MS Common Subvector . . . . . . . . .
. . . . .
Data Reset Flag (XI45 1) MS Common Subvector . . . . . . . .
.... . . .
Supporting Data Correlation (X 148 I) MS Common Subvector
. . . . . . .
Fully-qualified Session PCID (X 160 I) Supporting Data Correlation Subfield
Detailed Data (X 182 I) Supporting Data Correlation Subfield
........
LAN Link Connection Subsystem Data (XI 51 I) Supporting Data Correlation Subfield
Ring or Bus Identifier (X 1021) LAN Link Connection Subsystem Data Subfield
Local Individual MAC Address (X 103 1) LAN Link Connection Subsystem Data Subfield
Remote Individual MAC Address (X 104 1) LAN Link Connection Subsystem Data
Subfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Routing Information (X 105 I) LAN Link Connection Subsystem Data Subfield
Fault Domain Description (X 106 1) LAN Link Connection Subsystem Data Subfield
Beaconing Data (X I 07 1) LAN Link Connection Subsystem Data Subfield . . . . .
Single MAC Address (X 108 1) LAN Link Connection Subsystem Data Subfield ..
Fault Domain Error Weight Pair (X 109 1) LAN Link Connection Subsystem Data Subfield
Bridge Identifier (X lOA I) LAN Link Connection Subsystem Data Subfield
.......
Local Individual MAC Name (X 123 I) LAN Link Connection Subsystem Data Subfield
Remote Individual MAC Name (X 1241) LAN Li nk Connection Subsystem Data Subfield
Fault Domain Names (XI26 1) LAN Link Connection Subsystem Data Subfield
Single MAC Name (X 128 I) LAN Link Connection Subsystem Data Subfield
Link Connection Subsystem Configuration Data (X 1521) MS Common Subvector
Port Address (X I 011) Link Connection Subsystem Config. Data Subfield

xvi

SNA Formats

8-165
8-166
8-166
8-167
8-168
8-170
8-170
8-172
8-172
8-173
8-173
8-174
8-175
8-175
8-175
8-178
8-180
8-180
8-181
8-181
8-181
8-182
8-182
8-183
8-183
8-184
8-184
8-185
8-185
8-186
8-186
8-187
8-187
8-188
8-188
8-189
8-189
8-190
8-190
8-190
8-191
8-191
8-191
8-192
8-192
8-193
8-193
8-193
8-194
8-194
8-195

Remote Device Address (X 1021) Link Connection Subsystem Config. Data Subfield
Local Device Address (X 104 1) Link Connection Subsystem Config. Data Subfield .
LCS Link Station Attributes (X I 06 1) Link Connection Subsystem Config. Data Subfield
LCS Link Attributes (X I 071) Link Connection Subsystem Config. Data Subfield
LPDA Fault LSL Descriptor (X 108 1) Link Connection Subsystem Config. Data Subfield
Sense Data (XI7DI) MS Common Subvector

8-195
8-196
8-196
8-196
8-197
8-197

Chapter 9. Sense Data . . . . . . . . . . . . . . . . . .
...... .
Request Reject (Category Code = X 108 1)
.... .
Request Error (Category Code = X1101)
State Error (Category Code
X 120 I)
.... .
RH Usage Error (Category Code = X 140 I) . . . . .
X 180 I) . . . . . . . .
Path Error (Category Code

. 9-1
. 9-2
9-44
9-59
9-61
9-63

Chapter 10. Function Management (FM) Headers
FM Header 1 . . . . . . . . . .
. ....... .
FM Header 2
FM Header 3
FM Header 4 . . . . . . . . . .
FM Header 5: Attach (LU 6.2)
Access Security Information Subfields
PIP Variable
........... .
PI P 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 .

10-1
10-2
10-5
10-6
10-7
10-8
10-10
10-10
10-11
10-11
10-12
10-13
10-14
10-15
10-15
10-15

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

11-1
11-1
11-1

Chapter 12. GDS Variables for SNA Service Transaction Programs (STPs)
List of SNA Service Transaction Programs . . . . . . . . .
Descriptions of GDS Variables for SNA STPs . . . . . . . .
Change Number of Sessions (XI12101) GDS Variable
Exchange Log Name (X 112111) GDS Variable
Control Point Management Services Unit (X112121) GDS Variable
Compare States (X 11213 1) GDS Variable

12-1
12-1
12-1
12-1
12-3
12-4
12-4

Chapter 13. SNA/Distribution Services (OS)
Introduction . . . . . . . . . .
Structure Classifications . . . .
Length-bounded Structures
Atomic Structures . . . . . .
Parent and Child Structures
Length-Bounded Parent Structures
Delimited Parent Structures
Implied Parent Structures
Segmented Structures
Properties of Parent Structures

13-1
13-1
13-1
13-1
13-1
13-1
13-2
13-2
13-2
13-2
13-2
Contents

xvii

Order
Unrecognized Children " " " " " " " " " " " " " " " " " " " " "
Number of Children " " " " " " " " " , . " ... , " " , . , " " " ' , . , '
Header Description Table , . , " " " " " " " " " " " " " " " " " " ' "
Structure Name " " " " " " " " " " " " ' , . , " " " " " " " , . , '
Structure Reference (Struct Ref) " " " " " " " " " " " " " " " " , . , '
Structure Class (Struct Class) " " " " ' , . , " " " " " " " " " " , . , . , '
IOIT
""""""""',.,"""',.,"""""""""',.,'
Length " " " " " , . , " " " " ' , .. , " " , .. , " , . , " " " ' , . , . , '
Occurrences " " " " " " " " " " " " " ' , . , " " " " " " " , . , '
Children " " " " " " " " " " " " " " " " " " " " " " ' , . , . , '
Unrecognized Children Allowed (Unrec) " " ' , . , " " " " " " " " " , . , '
Order " " " " ' , . , " " " " " " " " " " " " " " " " " ' , .. ,
Number (Num)
"',.,""""""""",.,""""""",.,'
Subtable " " " " " " " " " " , . , ' , . " .. , " " " " " " " " "
. Structure Description
" " " " " " " " " ' , . , ' , . , " " " , . , " " ' , .. ,
Header Description Tables for FS2 Message Units
"""',.,"""""""""
DISTRIBUTION TRANSPORT MESSAGE UNIT (DTMU) . , " , . , " " " " " " " , . , '
DISTRIBUTION REPORT MESSAGE UNIT (DRMU)
"""""""""""',.,'
DISTRIBUTION CONTINUATION MESSAGE UNIT (DCMU) " " " " " " " " " " ' "
SNA CONDITION REPORT " " " " " " " " " " " " " " " " " " " ' "
SENDER EXCEPTION MESSAGE UNIT (SEMU) " " " " " " " ' , . , " " " " ' "
RECEIVER EXCEPTION MESSAGE UNIT (REMU)
"""""""""""",.,
COMPLETION QUERY MESSAGE UNIT (CQMU) " " " " " " " " " " " " ' , . ,
COMPLETION REPORT MESSAGE UNIT (CRMU) " " " ' , . , " " " " " " " , . ,
PURGE REPORT MESSAGE UNIT (PRMU) " " " " " ' , . , " " " , . , " , . , ' "
RESET REQUEST MESSAGE UNIT (RRMU) " .. , " " " , . , " , . , " " " " " "
RESET ACCEPTED MESSAGE UNIT (RAMU) " " ' , . , " " " " " " " " " " "
FS2 Structure Descriptions " ' , . , " " " " " " " " " " " " " " " " " "
Header Description Tables for FS1 Message Units
"""""""""'.""'"
DISTRIBUTION MESSAGE UNIT (DIST_MU)
""""",.,"""""""'"
DIST REPORT OPERANDS
"""""""""",.,"""""',.,'"
SENDER EXCEPTION MESSAGE UNIT (TYPE FS1)
""",.,"""""',.,'"
RECEIVER EXCEPTION MESSAGE UNIT (TYPE FS1)
"""""""""""'"
FS1 Structure Descriptions " " " " " " ' , . , " " " " " " " " " " " , . , '
Transaction Program and Server Names " " " " " " " " " " " " " " " ' "
Code Points Used by SNA/DS FS2
""""""""',.,"""""""'"
Code Points Used by SNA/DS FS1
""""",.,""""""""",.".,
Terminology Mappings " " " " " " " " " " " " , . , " " " " , . , " " "

13-2
13-3
13-3
13-3
13-3
13-3
13-3
13-4
13-4
13-4
13-4
13-4
13-4
13-4
13-5
13-5
13-6
13-6
13-8
13-9
13-10
13-11
13-11
13-11
13-12
13-12
13-12
13-12
13-13
13-49
13-49
13-51
13-52
13-52
13-53
13-71
13-72
13-73
13-75

Chapter 14. GOS Variables for General Use " " " " " ' , . , " " " " " ' , . , " "
Application Data (X '12FF I) GDS Variable " ' , . , " " " " " " " " " " " ' "
Null Data (X '12F11) GDS Variable
"",.,"""',.,"""""""""
User Control Data (X '12F21) GDS Variable " " " " " " " " " , . , ' , . , " ' "
Map Name (X '12F3 1) GDS Variable , , " " " " " " " " ' , " " ' , . . . . . . . .
Error Data (X'12F4') GDS Variable .. , " " " ' , . " . , .. " . , " ' , . , . . . . " .
Error Log (X '12E11) GDS Variable " , . , " , . " . , ' , . , . . . . . ,." .. , . " . , .

14-1
14-2
14-2
14-2
14-2
14-2
14-3

Chapter 15. SNA/File Services (FS)
.,',.,.,..,.,..."..,.,",..,...,",.
Encoding Rules and Representations
" ... , " " " " " , . " .. , .. " . " ... " .
Structure Classifications " . . . . , , , . , . , . , .. , , , , , . , , . , , , , . . . . . . . . . .
Length-bounded Structures .. , .. , .. , .. , ' , . " . , ' , .. , . . . . , ' , . . . . . . ,.
Atomic Structures . . . . , " " ' , . , . , . " . , . , " , . , . , ' , . . . . . . . . , . , . , '
Parent and Child Structures . . . . , ... " . , " " " " , . , . , " " " ' , .. , . , .

15-1
15-1
15-1
15-1
15-1
15-1

xviii

SNA Formats

Length-Bounded Paient StiUctuies . . . . . . . . . . . . . . . . . . . . . . . . .
Delimited Parent Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Implied Parent Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ....
Segmented Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Properties of Parent Structures
.................................
Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unrecognized Children . . . . . . . .
Number of Children . . . . . . . . . .
Header Description Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure Reference (Struct Ref) . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure Class (Struct Class) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ID/T
....................................................
Length ...
Occurrences
Children ..
Unrecognized Children Allowed (Unrec) . . . . . . . . . . . . . . . . . . . . . . . . .
Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Number (Num)
....................................... .
Subtable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure Description
...........................................
SNA/FS Usage of SNA/DS Encodings
...................................
SNA/FS Requests and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Header Description Tables for SNA/FS Encodings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit of Work Correlator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNA/FS Agent Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ....
SNA/FS Server Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ....
SNA/FS Agent Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ....
SNA/FS Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ....
Subtables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. ...
Global Names . . . . . . . . . . .
Allocation Information
Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNA Condition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure Descriptions
....................................... .
Server Instructions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Token Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fetching Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNA/FS Data Object Classification Codes . . . . . . . . . . . . . . . . . . . . . .
. ..... .
Code Points Used by SNA/FS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transaction Program and Server Names . . . . . . . . . . . . . . . . . . . . . .
Global Name Registration
....................
. ........ .

.
.
.
.

.
.

.
.
.
.
.
.
.
.
.
.

15-2
15-2
15-2
15-2
15-2
15-2
15-2
15-3
15-3
15-3
15-3
15-3
15-3
15-4
15-4
15-4
15-4
15-4
15-4
15-4
15-5
15-5
15-5
15-6
15-6
15-6
15-7
15-8
15-8
15-9
15-9
15-9
15-10
15-11
15-12
15-20
15-24
15-25
15-26
15-35
15-35
15-36
15-36

Appendix A. SNA Character Sets and Symbol-String Types
Symbol-String Type . . . . . . . . .
. ...... .
SNA Character Sets and Encodings
............. .

A-1
A-1
A-2

Appendix B. GDS 10 Description and Assignments . . . . . . . . . . . . . . . . . . .
Structured Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Length (LL) Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifier (10) Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifier Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1
8-1
8-1
8-2
8-2

Appendix C. List of Abbreviations and Symbols

C-1

.................. .
Contents

xix

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

SNA Formats

Figures
1-1.
1-1.
1-2.
1-3.
1-4.
1-5.
1-6.
1-7.
1-8.
1-9.
1-10.
3-1.
4-1.
4-2.
4-3.
5-1.
6-1.
6-2.
8-1.
9-1.
9-2.
10-1.
10-2.
10-3.
10-4.
12-1.
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.
14-1.
15-1.
15-2.
15-3.
15-4.

Organization of this Book . . . . . . . . . . . . . . . . . . . . . . . . . vii
Flag Field of Link Header . . . . . . . . . . . . . . . . . . . .
1-1
..... .
Shared Trailing/Leading 0 in SDLC Flags
1-2
Address Field of Link Header . . . . . . . . . . . . . . . . . .
1-2
Control Field of Link Header . . . . . . . . . . . . . . . . . .
1-3
Control Fields for SDLC Commands and Responses-Modulus 8
1-4
Control Fields for SDLC Commands and Responses-Modulus 128 1-5
Information Field of the FRMR Response Frame
1-6
Frame Check Sequence Field of Link Trailer . . . . . . .
1-5
Flag Field of Link Trailer . . . . . . . . . . . . . . . . . . . .
1-7
LLC Commands and Responses . . . . . . . . . . . . . .
1-8
Transmission Header for FID Type 2
...........
3-1
RH Formats
............................
4-2
FMD RequesUResponse Combinations for Sessions between Two
LU 6.2s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
Request/Response Combinations For TS Profile 4 Sync Points
4-7
RU Sizes Corresponding to Values XI ab 1 in BIND
5-15
TS Profiles and Their Usage
...................
6-1
FM Profiles and Their Usage . . . . . . . . . . . . . . . . . . .
6-3
1
Setting of Bits 1 and 3 of Byte 2 of the RTM Request (X 1 92 )
Subvector
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148
Sense Data Format . . . . . . . . . . . . . . . . . . . . . . . . . .
9-1
Usage of X'1008' Sense Code Specific Information by LU Type
9-54
FM Header Contained in One RU
..............
10-1
FM Header Contained in Two Contiguous RUs of a Chain
10-1
Usage of FM Headers
.............
10-1
LU Types That Support FM Headers . . . . . . . . . . . . .
10-2
SNA-Defined Service Transaction Programs . . . . . . . .
12-1
Distribution Transport Message Unit
. . . . . . .
13-6
Distribution Report Message Unit . . . . . . . . . . . .
13-8
Distribution Continuation Message Unit . . . . . . . . .
13-9
SNA Condition Report . . . . . . .
... . . . .
13-10
Sender Exception Message Unit
............
13-11
Receiver Exception Message Unit . . . . . . . . . . . .
13-11
Completion Query Message Unit . . . . . . . . . . . . .
13-11
Completion Report Message Unit
. . . . . . . . . .
13-12
Purge Report Message Unit . . . . .. . . . . . . . .
13-12
Reset Request Message Unit . . . . .
.... . . . .
13-12
Reset Accepted Message Unit
. . . . . . .
13-12
Distribution Message Unit (DIST_MU) . . . . . . .
13-49
Distribution Report Operands . . . . . . . . . . . .
13-51
Sender Exception Message Unit (type FS1)
13-52
Receiver Exception Message Unit (type FS1)
13-52
Terminology Mappings . . . . . . . . . . . . . . . . . . .
13-75
LU Type 6.2 GDS Variable Code Points . . . . . . . . . .
14-1
The SNA/FS Use of the SNA/DS Agent_Correl. . . . . .
15-6
The ~NA/FS Use of the SNA/DS Agent_Object for Agent
15-6
Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SNA/FS Use of the SNA/DS Server_Object for Server
Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15-7
The SNA/FS Use of the SNA/DS Agent_Object for Agent Reports. 15-8
Figures

xxi

15-5.
15-6.
15-7.
15-8.
15-9.
15-9.
A-1.
8-1.
8-2.

xxii

SNA Formats

The SNA/FS Use of the SNA/DS Server_Object for Server
................................
Reports.
Subtable Encoding of the SNA/FS Global Name.
..........
Subtable Encoding of the Allocation Information. . . . . . . . . . .
Subtable Encoding of the Global Name Tokens. . . . . . . . . . .
SNA Condition Report . . . . . . . . . . . . . . . . . . . . . .
.
The SNA/FS Use of the SNA_Condition_Report
.
Character Sets A, AE, 930, USS, 1134, and 640 . . . . . . .
GDS Structured Field . . . . . . . . . . . . . . . . . . . . . . .
Identifier Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15-8
15-9
15-9
15-10
15-11
15-11
A-3
8-1
8-2

Chapter 1. OLC Links .
Two data link controls are described in this chapter: "Synchronous Data Link
Control (SOLC)," beginning on this page, and the "Token-Ring Network OLC" on
page 1-7.

Synchronous Data Link Control (SDLC)
All transmissions on an SOLC link are organized in a specific format called a
frame:
Frame
where:

= BLU = LH [,I-field], LT
BLU = Basic Link Unit
LH = Link Header
I-field = Information field
LT = Link Trailer

Link headers and link trailers contain data link control information for synchronous data link control (SOLC) links. An SOLC 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.

Link Header (Flag)

L--L_H-.L._ _ _In_f_onn_at_io_n_F_i_el_d__ •••

l-l

1 F 1A 1

I l-------------1

LH • Link Header
LT • Link Trailer
F • Flag

A • Address
C • Control

10111111111111101

Figure

1-1. Flag Field of Link Header. Always X'7E', 8'01111110'.

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

Chapter 1. OLC Links

1-1

I--leading flag-I
1 1 1 1 110
I-trailing flag-I

o1 1 1 1 1 1 0

Figure

1-2. Shared Trailing/Leading 0 in SDLe Flags

Note: Zero bit insertion between the beginning and ending flags prevents a flag

pattern from occurring anywhere else in the frame.

Link Header (Address)

Information Field

l-l

I F I AI CI

rJ l-----------1
I

Figure

LH a Link Header
LT = Link Trailer
F = Fl ag
A = Address
C = Control

1-3. Address Field of Link Header.

B I aaaaaaaa I

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', 8 1111111111) -- to all link stations
• a "no stations" address (X100I).
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 trans-

mission is going from primary to secondary or from secondary to primary.

1-2

SNA Formats

Link Header (Control)

Information Field

LH " Link Header
LT .. Link Trailer
F "Flag
A Address
II

___ j

l_ ________ __________C_ ~ :o:t~o I

r (Hodulus 8 and Hodulus 128)

(Hodulus 128 only)

Iclclclclclclclclclclclclclclclcl
Figure

1-4. Control Field of Link Header.
ecce ecce I for modulus 128.

B I cccccccc I for modulus 8; B I cccccccc

The third byte (or third ?nd fourth bytes) of the link header is the Control field.
The Control field contains either an SOLC 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 SOLC 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 SOLC 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.
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 twobyte 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 SOLC command or
response, the Information field contains a PIU (Path Information Unit). The

Chapter 1. OLC Links

1-3

remaining chapters of this book, with the exception of Chapter 2, discuss the
contents of the PIU.
Figure 1-5 lists the SOLC 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 toe Information field of the Frame Reject (FRMR) response
frame, which is one of the unnumbered formats listed in Figure 1-5.
HEX EQUIVALENT
BINARY
CONFIGURATION P/F off,P/F on

FORHAT

X' 03 " X' 13 '

Unnumbered Information

000 F

0111

X' 07', X' 17 '

Request Initialization
Hode

RIH

000 P

0111

X' 07', X' 17 '

Set Initialization Hode

SIH

000 F

1111

X'OF', X'lF'

Disconnect Hode

001 P

0011

X' 23 " X' 33 '

Unnumbered Po 11

010 F

0011

X' 43 " X' 53 '

Request Disconnect

010 P

0011

X' 43 " X' 53 '

Disconnect

DISC

011 F

0011

X' 63 " X' 73 '

Unnumbered Acknowledgment

100 P

0011

X' 83 " X' 93 '

Set Normal Response Hode

SNRH

100 F

0111

X' 87 " X' 97 '

Frame Reject

FRHR

101 P/F 1111

X' AF', X' BF'

Exchange Identification

XID

110 P/F 0111

X'C7', X'07'

Configure

CFGR

110 P

1111

X'CF', X'OF'

Set Normal Response Hode
Extended

SNRHE

III P/F 0011

X' E3 " X' F3 '

Test

TEST

III F

1111

X'EF', X'FF'

Beacon

BCN

Supervisory RRR P/F 0001
Format
RRR P/F 0101

X'xl', X'xl'

Receive Ready

X' x5 " X' x5 '

Receive Not Ready

RNR

RRR P/F 1001

X'x9', X'x9'

Reject

REJ

Information RRR P/F SSSO
Format

X' xx " X' xx '

Numbered Information
Present

Notes:

Figure

SNA Formats

ACRONYH

000 P/F 0011

Unnumbered
Format

1-4

COHHAND NAHE

P
F
RRR
SSS

•
•
•
•

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

1-5. Control Fields for SOLC Commands and Responses-Moduh,ls 8

FORMAT

HEX
EQUIVALENT

BINARY CONFIGURATION

COMMAND NAME

ACRONYH

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

Unnumbered
Fonnat

Supervisory 0000 0001 RRRR RRR P/F
Fonnat
0000 0101 RRRR RRR P/F

X'Olxx'

Receive Ready

X'05xx'

Receive Not Ready

RNR

0000 1001 RRRR RRR P/F

X'09xx'

Reject

REJ

Infonnation SSSS SSSO RRRR RRR P/F
Fonnat

X'xxxx'

Numbered Infonnation
Present

P ~ Poll bit (sent to secondary station)
F ~ Final bit (sent to primary station)
RRR = Nr (receive count)
SSS ~ Ns (send count)

Notes:

Figure

1-6. Control Fields for SDLC Commands and Responses-Modulus 128

'-ink Trailer (Frame Check Sequence)

Infonnation Field

IFI

FCS

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

Figure

1-8. Frame Check Sequence Field of Link Trailer

The Frame Check Sequence field carries information that the receiver uses to
checl< 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-5

Information Field of the FRMR Response Frame
Modulus 8:

Modulus 128:

Note:

Field

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.

Description
Control Field

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

Receive Count

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

Send Count

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

Rejection Indicators:
Count

o • no

error
1 • Received Nr disagrees with transmitted Ns

Buffer

I-field

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

Command

1-6

SNA Formats

II
II

o ..
1

Figure

no error
Prohibited I-field received
no error
Invalid or nonimplemented command received

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

Information Field

•••

~
r- J

FCS

IFI

r------------ J
10111111111111101

Figure

1-9. Flag Field of Link Trailer. Always X I 7EI, 8 1 01111110 1 •

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

Token-Ring Network OLe
The token-ring network OLC 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 in Figure 1-6,
are used by the LLC sublayer in the token-ring network:

Chapter 1. OLC Links

1-7

Format

Command/Response Name

Unnumbered Format

DH Response
DISC Command
UA Response
SABHE Command
FRHR Response
XID Command or Response
Test Command or Response

Supervisory Format

Receive Ready
Receive Not Ready
Reject

Information Format

Figure

Numbered Information Present

1-10. 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 OLe, in contrast to SOLe, 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.
Additional information about the token-ring network OLe architecture is contained in the Token-Ring Network Architecture Reference.

1-8

SNA Formats

XID I-field

Chapter 2. Exchange Identification (XID) Information Fields
This chapter describes the formats of the information field of the DLC XID
command and response.
Throughout this book, reserved is used as follows: reserved bits, or fields, are
currently 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.

DLe XID Information-Field Formats
OLC XIO Information Field
Byte

Bit

Content

0-3

Format of XID I-field:
X 10 1 fixed format: only bytes 0 - 5 are included
X 111
variable format (for T112.0 to T415 node exchanges): bytes O-p are
included
reserved
XI 2I
X 13 1 variable format (for T2.1 to T2.1/BF and T2.0 to T5 node exchanges):
bytes O-p are included
X 18 I - X I F I
defined for external standards organizations
Type of the XID-sending node:
X I 1 1 T1
X ' 2 1 T2
X 13 1 reserved
X ' 4 1 subarea node (T4 or T5)

4 -7

Length, in binary, of variable-format XID I-field (bytes O-p); reserved for fixedformat XID I-field

2-517

Node Identification

2- 5

0 -11

12 - 31

Block number: an IBM product specific number; see the individual product
specifications for the specific values used
Note: The values all O's and all 1's indicate that bytes 2 - 5 do not contain a
unique node identifier.
10 number: a binary value that, together with the block number, identifies a
specific station uniquely within a customer network installation; the 10 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 all 1's, a value of
all O's in the 10 number indicates that no 10 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', OAF') values assigned at a node. When a rolenegotiation value is needed and the node does not supply a unique node identification value, it supplies a random value in the 10 number field.

End of Format 0

Chapter 2. XID Information Fields

2-1

XID I-field

OLC XID Information Field
Byte

Bit

Content

6-p

Format 1 Continuation

6-7

Reserved

Link Station and Connection Protocol Flags
0-1
2

4-7

0-1

2-3

4-5
6

10-11

o
1-15

2-2

0-3
4-7

SNA Formats

Reserved
Link-station role of XID sender:
o sender is a secondary link station (nonnegotiable)
1
sender is a primary link station (nonnegotiable)
Reserved
Link-station transmit-receive capability:
X'O' two-way alternating
X'1' two-way simultaneous
Characteristics of the node of the XID sender:
Reserved
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
Reserved
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
on this port
1
sender already engaged in a logical connection using short-hold mode on
this port
Short-hold capability of the XID sender:
o short-hold mode not supported
short-hold mode supported
1
Maximum I-field length that the XID sender can receive:
Format flag:
Obits 1-15 contain the maximum I-field length (only value defined)
Maximum I-field length, in binary
Reserved
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:

XIO I-field

OLC XIO Information Field
Byte

Bit

Content
For an SDLC link in normal response mode (NRM/NRME), having a pointto-point or multipoint configuration (determined from system definition), the
support required is:
Commands
Responses
I-frames
I-frames
RR
RR
RNR
RNR
Test
Test
XID
XID
SNRM/SNRME UA
Disconnect
DM
RD
Frame Reject
Reject
Reject

•

Note 1: 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 SDLe link in normal response mode (NRM), having a loop configuration (determined from system definition), the support required is:
Commands
I-frames
RR
RNR
Test
XID
SNRM
Disconnect
UP
Configure

Responses
I-frames
RR
RNR
Test
XID
UA
DM
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

0-1
2

3-7
14-15
16

Reserved
SDLC initialization mode options:
o SIM and RIM not supported
1
SIM and RIM supported
Reserved
Reserved

0
1-7

Reserved
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

Chapter 2. XID Information Fields

2-3

XID I-field

DLC XID Information Field
Byte

Bit

For byte 9, bit 7

Content

= 0 (short-hold mode not supported)

18-p

SDLC Address Assignment Field

Length (p minus 18), in binary, of the SDLC address to be assigned

19-p'

Secondary station address to be assigned

For byte 9, bit 7 = 1 (short-hold mode supported)

18-p

Short-Hold Mode Dependent Parameters

Reserved

19-n

Dial Digits of XID Sender

Number, in binary, of dial digits

20-n

Dial digits: a string of digits, each having the form X I Fn I

n+1-p

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 call on an already logically busy (byte 9, bit 6 = 1) short-hold mode
port. If this field is not included, then p = n.

n+1

Number, in binary, of dial digits of an available short-hold mode port, if one
exists

n+2-p

Dial digits of an available short-hold mode port: a string of digits, each having
the form X I Fn I (0~nS9)
Note: Byte n + 1 is set to the value X 100 I 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.

(0~n~9)

End of Format 1

6-p

Format 3 Continuation

6-7

Reserved

8-9

Characteristics of the node of the XID sender:
INIT-SELF support:
a 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.
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.
Whole-BIND-PIUs generated indicator:
o this node can generate BIND PIU segments
1
this node does not generate BIND PIU segments

2-4

SNA Formats

XID I-field

OLC XID Information Field
Byte

Bit

Content

Whole-BIND-PIUs required indicator:
this node can receive BIND PIU segments
1
this node cannot receive BIND PIU segments
Note: The value 10 for bits 2 - 3 is reserved.
Reserved
ACTPU suppression indicator:
o ACTPU for an SSCP-PU session requested
1
ACTPU for an SSCP-PU session not requested
Reserved
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
Reserved

4-7
8

9-11
12-13

14-15
10

2-7

BIND pacing support over the link:
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
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.
Reserved

11-16

Reserved

DLC type:
X'01'
SDLC
X '02'
System/370 channel to controller DLC

18-n

DLC Dependent Section

Length, in binary, of the DLC Dependent Section field (Length field includes
itself in the length specified.)

For SDLC

Link Station and Connection Protocol Flags

19
19

o
1

Reserved
ABM support indicator:
o XID sender cannot be an ABM combined station
1
XID sender can be an ABM combined station

Chapter 2. XID Information Fields

2-5

XID I-field

OLC XIO Information Field
Byte

Bit

Content

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
OAF'-DAF' assignment and deciding which node sends the Set Mode command.
Reserved
Link-station transmit-receive capability:
00
two-way alternating
01
two-way simultaneous

4-5
6 -7

Reserved

21-22
0
1-15
23

0-3

4-7

Maximum BTU length that the XID sender can receive:
Format flag:
Obits 1 -15 contain the maximum BTU length (only value defined)
Maximum BTU length, in binary
Reserved
SDLC command/response profile:
X'O'
SNA link profile (on.ly value defined)
Note: These profiles refer to the mandatory command/response support on an
SDLC link, as follows:
•
For an SDLC link in normal response mode (NRM/NRME), having a pointto-point or multipoint configuration (determined from system definition), the
support required is:
Commands
Responses
I-frames
I-frames
RR
RR
RNR
RNR
Test
Test
XID
XID
SNRM/SNRME UA
DM
Disconnect
RD
Frame Reject
Reject
Reject

2-6

SNA Formats

XID I-field

OLC XIO Information Field
Byte

Bit

Content
•

For an SDLC link in normal response mode (NRM), having a loop configuration (determined from system definition), the support required is:
Commands
I-frames
RR
RNR
Test
XID
SNRM
Disconnect
UP
Configure

•

Responses
I-frames
RR
RNR
Test
XID
UA
OM
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 DISCONT ACT request from its CPo
For an SDLC link in asynchronous balanced mode (ABM) (determined from
the Link-Station Role of XID Sender field). having a point-to-point configuration, the support required is:

Commands
I-frames
RR
RNR
Reject
SABME
Disconnect
Test
XID

Responses

RR
RNR
Reject
UA
OM
Test
XID
Frame Reject
Note 1: All commands and responses are transmitted and received in two-octet
format (extended control field).
Note 2: Frame Reject is not required to be transmitted; receive capability is
required.

0-1
2

3-7
25-26
27

28{ =n)

Reserved
SOLC initialization mode options:
o SIM and RIM not supported
SIM and RIM supported
1
Reserved
Reserved

0
1-7

Reserved
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 SDLC

Chapter 2. XID Information Fields

2-7

XID I-field

OLC XIO Information Field
Byte

Bit

Content

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 COLC;
the controller always contains the secondary station.

19-20

4-15

Indicators:
Change COLC parameters (may be set by the primary on a nonactivation XIO
and echoed by the secondary; reserved for both primary and secondary for
other XIO exchange types):
o do not change COLC 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
Attention time-out support (set by the secondary; reserved for the primary):
o not supported
1 . supported
Channel data streaming support by the XIO sender:
o not supported
1
supported
Change COLC parameters support by the XIO sender by means of a nonactivation XIO exchange (see bit 0):
o not supported
1
supported
Reserved

21-22

Maximum link PIU (LPIU) size: length of the maximum LPIU that the XID 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

24-25

Number of Read commands: number of Read CCWs the primary must include
in every read channel program used to read LPIUs

26-27

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

28-29

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

30-31

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.

32-33

Previous number of Read commands: set by the secondary in an XIO sent in
reply to a change-COLC-parameters nonactivation XID to specify the number-ofRead-commands parameter (see bytes 24 - 25) that was active prior to the
change; otherwise, reserved

2-8

SNA Formats

XIO I-field

OLC XID Information Field
Byte

Bit

Content

34-35

Previous primary buffer size: set by the secondary in an XID sent in reply to a
change-CDLC-parameters non activation XID to specify the primary-buffer-size
parameter (see bytes 26 - 27) that was active prior to the change; otherwise
reserved

36( = n)

Time units used for Attention time-out and blocking delay:
100-millisecond time units
X 100 I
X 1011
1-millisecond time units
End of DLC Dependent Section for Channel DLC

n+1-p

Control vectors, as described in "Control Vectors" on page 8-4
Note: The following control vectors may be included:
X'OE I PU Name control vector: type X I F1 1, not network-qualified PU name
(maximum of 8 bytes may be sent from a T4/T5 node)
X IDE I Network Name control vector: type X I F4 1, 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)
Product Set 10 control vector (always present)
X 110 I
Note: When included in XID, the product set 10 is limited to 60 bytes or
less in length.
X ' 22 1 XID Negotiation Error control vector (present when an error during XID
negotiation is detected; more than one may be present)

Chapter 2. XID Information Fields

2-9

XID I-field

2-10

SNA Formats

FID2

Chapter 3. Transmission Headers (THs)

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 (FlO) field. FI02 corresponds to
hexadecimal value 2 in the FlO field. The FI02 TH is described below.

FID2 Layout
Byte

FID2--Fonmat Identification
HPF--Happing Field
ODAI--OAF'-DAF' Assignor
Indicator
EFI--Expedited Flow Ind.

DAF'--Destination Address

SNF--Sequence Number Field

Figure

Reserved Byte

OAF'--Origin Address

3-1. Transmission Header for FlO Type 2

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

FID2 Field Descriptions
Byte

Bit

Content

0-3

FI02--Format Identification: 0010
~PF.;...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)
Note: For all responses (RRI field of the RH is set to 1) and expedited requests
(EFI is set to 1). with the exception of BIND and RSP(BINO). the MPF is set to 11.
Le. no segmenting of responses and expedited requests is performed.

4-5

Chapter 3. Transmission Headers (THs)

3-1

FID2

FID2 Field Descriptions
Byte

Bit

Content

OOAI-OAF'-OAF' Assignor Indicator (used for T2.1 - T2.11 BF flows; otherwise,
reserved). The OOAI indicates which node assigned (at session-activation time)
the OAF'-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 OAF' and OAF' values, the OOAI value forms a 17-bit local-form session
identifier (LFSID); the OAF' and OAF' values used in the TH in one direction are
reversed in the other direction.
Note: See "ISOLATED PACING MESSAGE (IPM)" on page 4-9 for the discussion
of the adaptive BIND pacing IPM, which makes exceptional use of these fields.
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 normalflow PIUs flowing in the same direction at queuing points in TC within halfsessions and boundary function session connectors. It has the following
meaning:
o normal flow
1
expedited flow

Reserved

OAF'-Destination Address Field. See discussion above for OOAI.

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 OAF' = 0; BIUs from the
physical unit always have the associated OAF' = O. The OAF' is also 0 for BIUs
from the SSCP, and OAF' is 0 for BIUs to the SSCP. For T2.1 nodes, an OAF' or
OAF' can also be set to 0 for independent LU-LU sessions (see SNA Type 2.1
Node Reference for details).

4-5

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 16-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 16-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 normalflow SNF usage between LU 6.2s.

(FMDILU5TAT) with BB
(FMD LUSTAT) with -'BB
BIS
RTR
SIG
A:

3-2

SNA Formats

Reguest Resl20nse
A
C
A
B
A
D
A
E
B
E

A 16-bit number (1 - 65,535) incremented by 1 for each request and wrapping through 0 thereafter

FID2

FID2 Field Descriptions
Byte

Bit

Content
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).
0:
The half-session does not respond to BIS.
E:
Same value as the corresponding request.
Note: For additional details of LU 6.2 processing, see SNA LU 6.2 Reference:
Peer Protocols.

Chapter 3. Transmission Headers (THs)

3·3

FID2

3-4

SNA Formats

RH Formats

Chapter 4. Request/Response Headers (RHs)

Introduction
This chapter identifies the formats and meanings of the request and response
headers (RH); "Descriptions of Request Units" on page 5-4 and "Positive
Response Units with Extended Formats" on page 5-41 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 is a
response unit.
Figure 4-1 on page 4-2 provides a summary of the bytes and field names in 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 (RHs)

4-1

RH Formats

Request/Response Header
Request
Byte 0
Response

Request
Byte
Response

Request

G·

Byte 2
Reserved

Field
RRI

Response

Description
Request/Response indicator

Explanation/Usage
request (RQ); 1 " response (RSP)

o•

RU
Request/Response Unit Category 00·
Category
01 •
10 "
11 "
FI

Format indicator

0 • no FH header (~FHH), for LU-LU sessions;
or character-coded without an NS header
(~NSH), for network services (NS)
1 • FH header (FHH) follows, for LU-LU
sessions; or field-formatted with an
NS header (NSH), for NS

SOl

Sense Data Included indicator

o·

BCI

Begin Chain indicator

0 • not first in chain (~BC);
1 • first in chain (BC)

Figure

4-2

SNA Formats

FH data (FHO)
network control (NC)
data flow control (OFC)
session control (SC)

4·1 (Part 1 of 2). RH Formats

not included

(~SO);

1 • included (SO)

RH Formats

Field
ECI

Description
End Chain indicator

Explanation/Usage
0 • not last in chain
1 • last in chain (EC)

DR11

Definite Response 1 indicator

o·

~DR1j

1 • DR1

DR21

Definite Response 2 indicator

o·

~DR2j

1 • DR2

ERI

Exception Response indicator

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

RTI

Response Type indicatDr

0 • positive (+); 1 • negative (-)

RLWI

Request Larger Window
indicator

0 • larger pacing window not requested

(~EC)j

(~RLW)j

1 • larger pacing window requested (RLW)
QRI

Queued Response indicator

0 • response bypasses TC queues (~QR);
1 • enqueue response in TC queues (QR)

Pacing indicator

0•

~PACj

BBI

Begin Bracket indicator

0•

~BBj

EBI

End Bracket indicator

0 • ~EBj 1 • EB
(reserved for LU type 6.2)

1 • PAC
1 • BB

. Change Direction indicator

CSI

Code Selection indicator

0 • code OJ 1 • code 1

EDI

Enciphered Data indicator

0 • RU is not enciphered
1 • RU is enciphered (ED)

POI

Padded Data indicator

0 • RU i~ not padded (~PD)j
1 • RU is padded (PO)

CEBI

Conditional End Bracket
indicator

0 • not conditional end bracket (~CEB);
1 • conditional end bracket (CEB) (used
for LU type 6.2; else, reserved)

Figure

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

(~CD);

COl

(~Eo)j

4-1 (Part 2 of 2). RH Formats

Chapter 4. Request/Response Headers (RHs)

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 to which of four categories the BIU belongs: 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 (FM) 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 "BIND (BIND SESSION)"
on page 5-5 for details on BIND.)
Sense Data Included Indicator (SDI): Indicates that a 4-byte sense data field is
included in the associated RU. The sense data field (when present) always
immediately follows the RH and has the format and meaning described in
Chapter 9, "Sense Data" on page 9-1. 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 in the 4-byte format shown in Chapter 9, "Sense Data" on page 9-1.)
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.

4-4

SNA Formats

RH Formats

(BC,

~EC)

= first RU in chain

(~BC, ~EC) =

EC)
(BC, EC)
(~BC,

middle RU in chain

= last RU in chain
=

only 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 (DR11), Definite Response 2 indicator
(DR21), 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(O,O)
DR1,...., DR2) and
session receiving the request. (DR1I,DR21)
ERI =0 is the only coding possible; the abbreviation RQN refers to a request
with this coding. (Two special responses, ISOLATED PACING RESPONSE
[IPR] and ISOLATED PACING MESSAGE [IPM). set [DR1I,DR2I,ERI] =
[0,0,0], but they are used independently of the other responses listed. For
both IPR and IPM, 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). (DR1I, DR21) =
(1,O)I(O,1)1{1,1) and ERI = 1 are the possible codings; RQE1, 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. (DR1I, DR21) = (1,O)l{O,1)1(1,1) and ERI =0 are the possible
codings; RQD1, 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 DR11 and DR21 bits set to 1 (three combinations); a response to a
request returns the same (DR1I, DR21) bit combination (see Figure 4-2 on
page 4-6).
The setting of the DR11, DR21, 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
tabular 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; RQD1 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-7.
'",---

For nonzero, non-LU 6.2, LU types that do not use sync point protocols, the specific meanings of the DR11 and DR21 bits are defined in SNA: Sessions Between

Chapter 4. Request/Response Headers (RHs)

4-5

RH Formats

Logical Units; for LU type a, the interpretations of the DR11 and DR21 bits (and
distinctions among the three settings) are implementation-dependent.

The (DR1I, DR21, ERI) = (a, a, 1) combination is reserved.
REQUEST

VALID RESPONSE

MEANING OF RESPONSE

RQD1-(1,a,a)

+RSP1- (1, a, a)
-RSP1" (1, a, 1)

positive response
negative response

imp li ed +RSP1
-RSP1-(1,a,1)

reply received with no intervening response
negative response

RQD2-(a,1,a)

+RSP2- (a, 1, a)
-RSP2-(a,1,1)

CONFIRMED verb issued
SEND_ERROR verb issued

RQE2-(a,1,1)

implied +RSP2
-RSP2-(a,1,1)

reply received with no intervening response
no CONFIRMED verb issued

RQD3- (1,1, a)

+RSP3-(1,1,a)
-RSP3-(1,1,1)

CONFIRMED verb issued
SEND_ERROR verb issued

RQE3-(l,1,1)

implied +RSP3

reply received with no intervening response
no CONFIRMED verb issued

(Used by DFC)

RQEl-(1,a,1)

(Used by
DFC and PS)

(Used by PS)

-RSP3-(a,1,1)
(Used by PS)

Notes:
1. Values displayed in this table are in the order (DR1I,DR2I,ERI) for requests and (DR1I,DR2I,RTI)
for responses.
2. All ...., EC requests are sent as RQE1.
3. RQN = (0,0,0) is not used.

Figure

4-2. FMD Request/Response Combinations for Sessions between Two LU 6.2s

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 (Le., 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

4-6

SNA Formats

RH Formats

RH is always immediately followed by four bytes of sense data in the RU. Thus,
RTI NEG and RTI POS occur jointly with 501 SO and 501
SO, respectively.

REQUEST

VALID RESPONSE

MEANING OF RESPONSE

RQDl-(1,O,O)

+RSPl-(I,O,O)
-RSPl-(1,O,I)

positive response
negative response

RQEl- (1, 0,1)

-RSPl- (1,0,1)

negative response

RQDZ-(O,I,O)

+RSPZ-(O,I,O)
-RSP2- (0,1,1)

positive sync point response
negative sync point response

RQE2-(0,1,1)

-RSP2-(0,1,1)

negative sync point response

RQD3- (1, 1, 0)

+RSP3- (1,1,0)
-RSP3-(1,1,1)

positive sync point response
negative sync point response

RQE3-(1,1,1)

-RSP3-(1,I,I)

negative sync point response

=-,

Notes:

1. Values displayed In this table are in the order (DR1I,DR2I,ERI) for requests and (DR1I,DR2I,RTI)
for responses.
2. Each deflnite- or exception-response chain has the same setting of (DR1I,DR21)-either (1,0) or
(O,1)-on all requests with ECI = -,EC. When DR11 = 1 on these requests, the End-Chain
request can carry (DR1I,DR21) = (1,0)1(1,1). When DR21 = 1 on these requests, the End-Chain
request can carry only (DR1I,DR21) = (0,1). ERI is 0 only for definite-response chains and
when ECI = EC.
3. RQN = (0,0,0) 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, DR21) combinations allowed on requests. The settings of the DR11 and
DR21 bits in a response always equal the settings of the DR11 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 nonadaptive session-level pacing, the Pacing Response indicator may be on
in 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.

Chapter 4. Request/Response Headers (RHs)

4-7

RH Formats

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., EBCDI,C 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 8 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 8-bit binary representation.
Request Larger Window Indicator (RLW/): 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.

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.

4·8

SNA Formats

RH Formats

ISOLATED PACING RESPONSE (lPR)

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 fields 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 O's except for the Request/Response indicator, the
Pacing indicator, and the Chain indicators, which are set to 1's; thus, the IPR
RH is coded X 1830100 1 by the sender; the receiver identifies an I PR by
detecting that (RRI, DR11, DR21, PI) = (1, 0, 0, 1) and ignoring the remaining
bits.

ISOLATED PACING MESSAGE (lPM)
An IPM is used on a session if BIND and RSP(BIND) specify adaptive sessionlevel pacing is used. Three types of IPM exist: solicited IPMs, unsolicited IPMs,
and reset acknowledgment IPMs.
A receiver of paced requests sends a solicited IPM to a sender of paced
requests to grant the sender permission to send a group (or window) of paced
requests; the solicited IPM explicitly specifies the number of requests in the
window as the next-window size. A receiver of paced requests sends a solicited I PM either (1) after receiving a pacing request, or (2) after sending an unsolicited IPM with a next-window size of 0 and receiving a reset acknowledgment
IPM.
A receiver of paced requests sends an unsolicited IPM to a sender of paced
requests to withdraw from the sender previously granted permission to send
paced requests, typically because of congestion detected by the receiver of
paced requests. Upon receiving an unsolicited IPM, a sender of paced requests
(1) resets previously granted windows so that any queued requests are sent as
part of a subsequent window, and (2) sends a reset acknowledgment IPM to the
receiver of paced requests to delimit the end of the current truncated window.
The unsolicited IPM also specifies a next-window size that grants a new
window; the next-window size may be any value, including 0 (no new window).
After sending an unsolicited IPM, a receiver of paced requests ignores any
Pacing Request indicator it receives until it receives a reset acknowledgment
IPM.
Besides its use for session-level pacing, an IPM is also 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: Expedited flow is indicated except for a reset acknowledgment IPM, which
is always sent normal-flow (because it delimits the current window). The
sequence number is undefined (may be set to any value, and is not checked by
Chapter 4. Request/Response Headers (RHs)

4-9

RH Formats

the receiver). For an adaptive BIND pacing IPM, ODAI is always set to 0, and
OAF' and OAF' are set according to the sender's normal setting of ODAI in
BIND: a node that sets ODAI to 0 in BIND sets OAF' to X 101 1 and OAF' to X1001
in the BIND pacing IPM, while a node that sets ODAI to 1 in BIND sets OAF' to
X1001 and OAF' to X101 1 in the BIND pacing IPM.
IPM

The IPM consists of the RH and a 3-byte extension shown below.

IPM (ISOLATED PACING MESSAGE)
Byte

Bit

Content

0-2

RH: X ' 830100 ' (same as for an IPR, with the same receiver-checking mentioned
above)

3-5

IPM Extension

0-1

3-7

4-5

o
1-15

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
Reset current-window residual-count indicator:
o do not reset the residual count
1
reset the residual count to 0 (Le., terminate the current window)
Note: Currently, this bit is set to 1 in an unsolicited IPM, and 0 otherwise.
Reserved
Next-window information:
Format: 0 (only value defined)
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 toolong 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 of a 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.

4-10

SNA Formats

RH Formats

RH: The Sense Data Included bit is set to 1. All other fields are unchanged.
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 1's) 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 DCF 10.

Chapter 4. Request/Response Headers (RHs)

4-11

RH Formats

4-12

SNA Formats

Request Units

Chapter 5. Request/Response Units (RUs)

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 (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

session control

network control * subarea type RUs only

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 7, "User Data Structured Subfields" and Chapter 8, "Common
Fields."
3. All values for field-formatted requests that are not defined in this section
are reserved.
4. The request-code value X I FF I and the NS-header values X I (317IBIF)F* * * *
and X 1* *(317IBIF)F* * I 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 D'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
implement~tions of back-level SNA, current implementations of SNA treat
retired fields as follows: send checks enforce the setting of retired fields to
all D's except where other unique values are required (described individually); no receive checks are made on these fields, thereby accepting backlevel settings 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 7-1 and 8-1.

Chapter 5. Request/Response Units (RUs)

5-1

Request Units

8. A type 2.1 (T2.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.

Request Unit Summary Informati()n
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(c) Requests
REQDISCONT

FrV:D NS(ma) Requests
NMVT

FMD NS(s) Requests
INIT-SELF
NOTIFY

NSPE

TERM-SELF

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 105 1) can represent different requests in separate
categories (e.g., DFC, NC, and configuration services).

5-2

SNA Formats

Request Units

FMD NS Headers (third byte is the request code)
X ' 01021B'
X ' 010604 1
X ' 010681 1
X ' 010683 1

REQDISCONT
NSPE
INIT-SELF (Format 0)
TERM-SELF (Format 0)

X ' 41038D'
X ' 810620 '
X ' 810681 1
X ' 810683 1

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

DFC, NC, and SC Request Codes
X ' 04 1
X ' 05 1
X'OD'
X'OE'
X I 11 1
X ' 12 1
X ' 31 1
X ' 32 1
X ' 70 '
X ' 71 1
X ' 80 '
X ' 81 1
X ' 82 1

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)

X ' 83 1
X ' 84 1
X'AO'
X'A1 1
X'A2 1
X'A3 1
XICOI
XICOI
XIC1 1
X'C2 1
X'C8 1
X'C9 1

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

Chapter 5. Request/Response Units (RUs)

5-3

ACTPU

Descriptions of Request Units
ACTLU (ACTIVATE LOGICAL UNIT)
SSCP -+ LU, Exp; SC
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.

ACTLU (ACTIVATE LOGICAL UNIT)
Byte

Bit

Content

X '00' request code

1
0-5

6-7
0-3

Indicators:
Reserved
Type activation requested:
10
ERP (only value defined)
FM profile:
FM profile 0
TS profile:
X'1' TS profile 1 (only value defined)

X'O'

4-7

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

ACTPU (ACTIVATE PHYSICAL UNIT)
Byte

Bit

0
1

Content

X'11' request code
0-3

Format:

4-7

Format 0
Type activation requested:
X'2' ERP

X'O'

0-3

FM profile:
FM profile 0
TS profile:
X'1' TS profile 1

X'O'

4-7

5-4

SNA Formats

BIND

ACTPU (ACTIVATE PHYSICAL UNIT)
Byte

Bit

Content

0-3

A 6-byte field that specifies the 10 of the SSCP issuing ACTPU; the first four bits
specify the format for the remaining bits:
Format: 0000 (only value defined)
PU type of the node containing the SSCP
Implementation and installation dependent binary identification

3-8

4-7
8-47

BID (BID)
LU -. LU, Norm; DFC
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.

BID (BID)
Byte

Bit

Content
X' C8' request code

BIND (BIND SESSION)
PLU -. SLU, Exp;SC
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.
The description below is complete for LU 6.2; for other LU types, see SNA:
Sessions between Logical Units for additional details.

BIND (BIND SESSION)
Byte

Bit

o
1

Content
X '31' request code

0-3

4-7

Format: 0000 (only value defined)
Type:
0000
negotiable (only value defined for LU 6.2)
0001
nonnegotiable

Chapter 5. Request/Response Units (RUs)

5-5

BIND

BIND (BIND SESSION)

Byte

Bit

Content
FM profile:
X 102 I
FM
X103 I FM
X104 1 FM
X ' 07 1 FM
X1121 FM
X113 1 FM

profile
profile
profile
profile
profile
profile

2
3
4
7
18
19 (only value defined for LU 6.2)

TS profile:
X 102 I
TS
X103 I TS
X ' 04 1 TS
X107 1 TS

profile
profile
profile
profile

2
3
4
7 (only value defined for LU 6.2)

FM Usage-Primary LU Protocols for FM Data
4

2-3

5
6

Chaining use selection:
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)
Request control mode selection:
a immediate request mode (only value defined for LU 6.2)
1
delayed request mode
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)
2-phase commit for sync point (reserved if any TS profile other than 4):
a 2-phase commit not supported
1
2-phase commit supported
Reserved
Compression indicator (reserved for LU 6.2):
a compression will not be used on requests from primary
1
compression may be used
Send End Bracket indicator:
a 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
5

5-6

SNA Formats

Chaining use selection:
only single-RU chains allowed from secondary LU half-session
1
multiple-RU chains allowed from secondary LU half-session (only value
defined for LU 6.2)
Request control mode selection:
a immediate request mode (only value defined for LU 6.2)
1
delayed request mode

BIND

BIND (BIND SESSION)

Byte·

Bit

Content

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)
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
Reserved
Compression indicator (reserved for LU 6.2):
o compression will not be used on requests from secondary
1
compression may be used
Send End Bracket indicator:
o secondary will not send EB (only value defined for LU 6.2)
1
secondary may send EB

5
6

FM Usage-Common LU Protocols

Whole-BIUs required indicator (reserved in nonextended, non-LU 6.2 BINDs, i.e.,
when control vector X 160 I is not present):
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 session are not segmented when sent
to a node requiring whole BIUs
FM header usage:
o FM headers not allowed
FM headers allowed (only value defined for LU 6.2)
1
Brackets usage and reset state:
o The value of this bit should be 0 if either condition (1) or condition (2) is
true.
1. Brackets are not used if neither primary nor secondary will send EB
(byte 4, bit 7 = 0 and byte 5, bit 7 = 0).
2. Brackets are used and the bracket state managers' reset states are
INB if:
• either primary or secondary, or both, may send EB (byte 4, bit 7 =
1 or byte 5, bit 7 = 1).
• FM profile 19 is specified (byte 2 = XI13 1).

(only value defined for LU 6.2)
1
brackets are used and bracket state managers' reset states are BETB
Bracket termination rule selection:
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)
Note: This bit is reserved if both of the following conditions are true.
1. Brackets are not used (byte 4, bit 7 = 0, byte 5, bit 7
= 0).
2. The FM profile is not 19 (byte 2 XI13 1).

and byte 6, bit 2

Chapter 5. Request/Response Units (RUs)

5-7

BIND

BIND (BIND SESSION)
Byte

Bit

Content

Alternate code set allowed indicator:
alternate code set will not be used
1
alternate code set may be used
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.
BIS sent (reserved for TS profiles other than 4):
OBIS not sent
1
BIS sent
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 implementationdefined limits. BIND queuing is terminated by sending UNBIND to the BIND
receiver.

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
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)
Contention winner/loser:
o secondary is contention winner and primary is contention loser
1
primary is contention winner and secondary is contention loser
Note: This bit is reserved if either condition (1) or condition (2) holds.
1. The normal-flow send/receive mode is FOX (byte 7, bits 0 - 1 = 00).
2. All of the following are true.
• The normal-flow send/receive mode is HDX-FF (byte 7, bits 0 - 1 = 10).
• Brackets are not used (byte 4, bit 7 = 0, byte 5, bit 7 = 0 , and byte 6,
bit 2 = 0).
• The FM profile is not 19 (byte 2 ::/= X'13 1 ).
• Symmetric responsibility for recovery is used (byte 7, bit 2
1).
Note: Contention winner is also brackets first speaker.

5-8

SNA Formats

BIND

BIND (BIND SESSION)

Byte

Bit

Content

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-B (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 translated using the transforms
defined by the ANSI X3.26 Hollerith Card Code.
Control vectors included indicator:
o control vectors are not included after the SLU name (bytes r+ 1-s)
1
control vectors are included after the SLU name (bytes r+ 1-s)
Half-duplex flip-flop reset states:
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
HDX-FF reset state is SEND for the primary and RECEIVE for the secondary,
1
e.g., the primary sends normal-flow requests first after session activation
(only value defined for LU 6.2)
Note: This bit is reserved unless both of the following are true.

1. The normal-flow send/receive mode is half-duplex flip-flop (byte 7, bits 0-1
= 10).
2. Brackets are not used or the bracket state manager's reset state is INB
(byte 6, bit 2 = 0).
TS Usage

1
2-7

Staging indicator for session-level pacing of the secondary-to-primary normal
flow:
o the secondary send window size (byte B, 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.)
the secondary send window size (byte B, 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.
Reserved
Secondary send window size, in binary, for session-level pacing: a value of 0
indicates that there will be no pacing of requests flowing from the secondary.
Note: If pacing on a session stage in a particular direction is not to be performed, the values for the window size on that stage are set to O. For example,
if there is to be no pacing in the secondary to primary direction, the primary
receive and secondary send window sizes are both set to O.
Adaptive session-level pacing support (reserved for nonextended BIND, i.e.,
when control vector X 160 I is not present):
o adaptive pacing not supported by the sending node: pacing window values
in bits 2 -7 of bytes B, 9, 12, and 13 specify the fixed value implied in each
pacing response; a 0 value in those fields specifies no pacing
adaptive pacing supported by the sending node: pacing window values in
bits 2 -7 of bytes B, 9, 12, and 13 specify the preferred minimum value for
each ISOLATED PACING MESSAGE; a 0 value in those fields 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

Chapter 5. Request/Response Units (RUs)

5·9

BIND

BIND (BIND SESSION)
Byte

Bit

2-7

Content
Note: Adaptive pacing is supported only in conjunction with one-stage sessionlevel 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 (RHs)" for further discussion of
adaptive pacing.
Reserved
Secondary receive window size, in binary, for session-level pacing: a value of 0
causes the boundary function to substitute the value set by a system definition
pacing parameter (if the system definition includes such a parameter) before it
sends the BIND RU toward the secondary node; a value of 0 received at the
secondary is interpreted to mean no pacing of requests flowing to the secondary. When fixed session-level pacing is used (byte 9, bit 0
0), this value
is the fixed window size for the primary-to-secondary direction of the session
stage. When adaptive session-level pacing is used (byte 9, bit 0 = 1), this
value is the preferred minimum window size the primary end of the session
stage recommends the secondary end of the session stage place in the IPMs it
sends.

Maximum RU size sent on the normal flow by the secondary half-session. Bit 0
is interpreted as follows.

1. If bit 0 is set to 0, no maximum is specified and the remaining bits 1-7 are
ignored.
2. If bit 0 is set to 1 (only value defined for LU 6.2), the byte is interpreted as
X'ab '
a x 2b (Notice that, by definition, a~8 and therefore X'ab ' is a normalized floating point representation.) See Figure 5-1 on page 5-15 for all
possible values.

11
12

Maximum RU size sent on the normal flow by the primary half-session: identical encoding as described for byte 10

1
2 -7

5-10

SNA Formats

Staging indicator for session-level pacing of the primary-to-secondary normal
flow:
o 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).
Reserved
Primary send window size, in binary, for session-level pacing: a value of 0
causes the value set by a system definition pacing parameter (if the system
definition includes such a parameter) to be assumed for the session; if this is
also 0, it means no pacing of requests flowing from the primary (For one-stage
pacing in the primary-to-secondary direction, this field is redundant with, and
will indicate the same value as, the secondary receive window size-see byte 9,
bits 2 -7, above.)

BIND

BIND (BIND SESSION)
Byte

Bit

Content

0-1

Reserved
Primary receive window size, in binary, for session-level pacing: a value of 0
means no pacing of requests flowing to the primary (For one-stage pacing in the .
secondary-to-primary direction, this field is redundant with, and will indicate the
same value as, the secondary send window size-see byte 8, bits 2 -7, above.)

2-7

PS Profile
14

o
1-7

PS Usage field format:
basic format (only value defined)
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
LU type 7
0000111

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
0000110 and byte 15
00000010), see SNA: Sessions Between Logical
1 -7
Units.

LU-6 level:
Level 2 (Le., LU 6.2)

X' 02 1
16-22

Reserved
0-2
3

4-5
6

Retired
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
Reserved
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
Reserved
Note: This byte is used for security information only.

Chapter 5. Request/Response Units (RUs)

5-11

BIND

BIND (BIND SESSION)
Byte

Bit

Content

Reserved
Synchronization level:
01
confirm is supported
10
confirm, sync point, and backout are supported
Reserved
Responsibility for session reinitiation (reserved when bit 6 of this byte is set to
1):
00
operator controlled
01
primary half-session will reinitiate
10
secondary half-session will reinitiate
11
either may reinitiate
Parallel session support for LU-LU pair:
o not supported
1
supported
Change Number of Sessions GDS variable flow support (set to 1 if byte 24, bit 6
= 1):
o not supported
1
supported

1-2

4-5

o
1

2-7

Reserved
Limited resource indicator:
o the contention-winner LU will not deactivate the limited resource session
1
the contention-winner LU will deactivate the limited resource session when
it is no longer busy
Reserved
End of PS Usage Field

26-k
26

Cryptography Options

0-1

Private cryptography options (reserved for LU 6.2):
no private cryptography supported
private cryptography supported: the session cryptography key and
cryptography protocols are privately supplied by the end user
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 TCs
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 TC
Note: Only values 00 and 11 are defined for LU 6.2.
Session-level cryptography options field length:
X·O· no session-level cryptography specified; following additional
cryptography options fields (bytes 27 - k) omitted
X' g.
session-level cryptography specified; additional options follow in next
nine bytes

00
01

2-3

4-7

5-12

SNA Formats

BIND

BIND (BIND SESSION)
Byte

Bit

Content

0-1

Session cryptography key encipherment method:
00
session cryptography key enciphered under SLU master cryptography key
using a seed value of a (only value defined)
Reserved
Cryptography cipher method:
000
block chaining with seed and cipher text feedback, using the Data
Encryption Standard (DES) algorithm (only value defined)

2-4
5-7

28-k

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

k+1-m

Primary LU Name Field (always present)

k+1

Length of primary LU name (values 1 to 17 are valid)
Note: Value a is retired.

k+2-m

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)

m+1-n

User Data Field

m+1

Length of user data
Note: X I 00 I = no User Data field present; if unstructured user data present,
values 1 to 65 are valid.

m+2-n

User data

m+2

User data key:
XIOOI
structured subfields follow (only value defined for LU 6.2)
.., X 100 I first byte of unstructured user data
Note: Individual structured subfields may be omitted entirely. When present,
they appear in ascending subfield-number order.

For unstructured user data:
m+3-n

Remainder of unstructured user data

For structured user data:
m+3-n

Structured subfields (For detailed definitions, see Chapter 7, "User Data Structured Subfields. ")

n+1-p

User Request Correlation Field (present only if carried in INIT from SLU, or if
Secondary LU name field or control vectors are included)

n+1

Length of user request correlation (URC) field (values 0 to 12 are valid)
Note: XIOOI
no URC present.

n+2-p

URC: LU-defined identifier (present only if carried in INIT from SLU)

p+1-r

Secondary LU Name Field (present only for negotiable BINDs and for nonnegotiable BINDs that include control vectors)

p+1

Length of secondary LU name (values 1 to 17 are valid)
Note: Value 0 is retired.

p+2-r

Secondary LU name

Chapter 5. Request/Response Units (RUs)

5-13

BIND

BIND (BIND SESSION)

Byte

Bit

Content

Bytes r + 1 - s are included only if byte 7, bit 6 specified that control vectors are included after the SLU
name.

r+1-s

Control vectors, as described in "Control Vectors" on page 8-4
Note: The following control vectors may be included; they are parsed according
to subfield parsing rule KL:
X I OE I
Network Name control vector: PLU network name, X I F3 1 (present in
extended BINDs when bytes k + 2 - m contain a non-network-qualified
name)
X'OE I Network Name control vector: CP network name, XI F41 (conditionally
present: used in extended BINDs when neither the Fully-Qualified PCID
[X I 60 I] control vector nor the Route Selection [X I 2B I] control vector
contains the CP[PLU] name)
X ' 2C' COS/TPF control vector (conditionally present)
X 120 I Mode control vector (conditionally present, used in non-LUB.2 extended
BIND)
X 160 I
Fully-qualified PCID control vector (when present, the BIND is called an
extended BIND)
Note: The receiving LU simply ignores unrecognized control vectors.

Note 1:

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
X 160 I control vectors; any additional control vectors may cause the length to
increase up to 512 bytes.

Note 2:

If the last byte of a format a BIND request not having control vectors is a length
field' and that field is 0, that byte may be omitted from the BIND request.

5-14

SNA Formats

81S

Hant f ssa (a)

Exponent

(b)

B
(11)

(10)

(12)

(13)

E
(14)

F
(15)

104

112

120

128

144

160

176

192

208

224

240

256

288

320

352

384

416

448

480

512

576

640

704

768

832

896

960

1024

1152

1280

1408

1536

1664

1792

1920

2048

2304

2560

2816

3072

3328

3584

3840

4096

4608

5120

5632

6144

6656

7168

7680

A (10)

8192

9216 10240 11264 12200 13312 14336 15360

B (11)

16384 18432 20480 22528 24576 26624 28672 30720

C (12)

32768 36864 40960 45056 49152 53248 57344 61440

o (13)

65536 73728 81920 90112 98304 106496 114688 122880

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)( 2b.

For example, X'CS' represents (in decimal) 12)( 25

Figure

384.

5-1. RU Sizes Corresponding to Values X1ab l in BIND

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

BIS (BRACKET INITIATION STOPPED)
Byte

Bit

Content
X ' 70 ' request code

Chapter 5. Request/Response Units (RUs)

5-15

CLEAR

CANCEL (CANCEL)
LU -. LU, Norm; DFC
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.

CANCEL (CANCEL)
Byte

Bit

Content
X'83' request code

CHASE (CHASE)
LU -. LU, Norm; DFC
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.

CHASE (CHASE)
Byte

Bit

Content
X'84' request code

CLEAR (CLEAR)
PLU -. SLU, EXPiSC
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.

CLEAR (CLEAR)
Byte

Bit

5·16

Content
X' A1' request code

SNA Formats

DACTLU

CRV (CRYPTOGRAPHY VERi FiCAiiOi.Jj
PLU

SLU, Exp;SC
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 halfsessions.

CRV (CRYPTOGRAPHY VERIFICATION)
Byte

Bit

Content

XICOI

1-8

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
Note: The cryptography session-seed is used as the seed for all session-level
cryptography encipherment and decipherment provided for FMD RUs.

reque~code

DACTLU (DEACTIVATE LOGICAL UNIT)
SSCP

LU,Exp;SC
DACTLU is sent to deactivate the session between the SSCP and the LU.

DACTLU (DEACTIVATE LOGICAL UNIT)
Byte

Bit

Content

X'OE' request code

Note:

End of short (1-byte) request

Type of deactivation requested:
X 101 1
normal deactivation
XI 03 1
session-outage notification (SON)

Chapter 5. Request/Response Units (RUs)

5-17

DACTPU

DACTLU (DEACTIVATE LOGICAL UNIT)

Bit

Byte

Content

Cause (reserved if byte 1 X I 031):
X I 07 1
virtual route inoperative: the virtual route serving the SSCP-LU session
has become inoperative, thus forcing the deactivation of the session
1
route extension inoperative: the route extension serving the SSCP-LU
X 108
session has become inoperative, thus forcing the deactivation of the
session
hierarchical reset: the identified session is being deactivated because
X 109 I
of a + RSP(ACTPU, Cold)
X lOB I virtual route deactivated: the SSCP-LU session is being deactivated
because of a forced deactivation of the virtual route being used by the
session
XIOCI 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 100 I 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
SSCP or LU failure-recoverable: the SSCP-LU session had to be deacX 10E I
tivated because of an abnormal termination of the SSCP or LU of the
session; recovery from the failure may be possible
X 10F I
cleanup: the 'SSCP is resetting its half-session before receiving the
response from the LU being deactivated

DACTPU (DEACTIVATE PHYSICAL UNIT)
SSCP

PU, PU

SSCP, Exp; SC

OACTPU is sent to deactivate the session between the SSCP and the PU.

DACTPU (DEACTIVATE PHYSICAL UNIT)

Byte

Bit

Content

X I 12 1 request code

Type deactivation requested:
X 1011
final use, physical connection may be broken
X 1021 . not final use, physical connection should not be broken
X 103 I
session-outage notification (SON)

5-18

SNA Formats

INIT-SELF Format 0

DACTPU (DEACTIVATE PHYSICAL UNIT)
Byte

Bit

Content
Cause (not present if byte 1 =1= X 103 1):
X107 1 virtual route inoperative: the virtual route for the SSCP-PU session has
become inoperative, thus forcing the deactivation of the SSCP-PU
session
X 108 1 route extension inoperative: the route extension serving the SSCP-PU
session has become inoperative, thus forcing the deactivation of the
SSCP-PU session
X I 09 I
hierarchical reset: the identified session is being deactivated because
of a + RSP{ACTPU, Cold)
X I OB I 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 I OC I 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 100 I 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 I OE I
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 10F I
cleanup: the SSCP is resetting its half-session before receiving the
response from the PU that is being deactivated
X110 I ALS reset: peripheral ALSs (and subordinate LUs and LU-LU sessions)
owned by the sending SSCP should be reset
X 1111
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 (INITIATE-SELF)
ILU -+ SSCP, Norm; FMD NS(s)
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 OLU).
This RU is not used for LU 6.2; refer to INIT-SELF Format 1.

INIT-SELF Format 0 (INITIATE-SELF)
Byte
0-2

Bit

Content
X I 010681 1 NS header

Chapter 5. Request/Response Units (RUs)

5-19

INIT.. SELF Format 0

INIT·SELF Format 0 (INITIATE·SELF)
Byte

Bit

Content

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
Reserved
PLU/SLU specification:
a DLU is PLU (only value defined)
a initiate only (I): do not enqueue.
1
initiate/enqueue (I/Q): enqueue the request if it cannot be satisfied immediately

4-5

4-11

Mode name: an a-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

12-m

Uninterpreted Name of DLU

Type: X IF3 1 logical unit

Length, in binary, of DLU name

14-m

EBCDIC character string

m+1-m+2

Retired

m+3-n

User Field

m+3

Length, in binary, of user data
Note: XIOOI = no user data is present.

m+4-n

User data: user-specific data that is passed to the primary LU on the CINIT
request

m+4

User data key:
structured subfields follow
X 100 I
--, X 100 I 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
m+5-n

Remainder of unstructured user data

For structured user data
m+5-n

Structured subfields (For detailed definitions, see Chapter 7, "User Data Structured Subfields" on page 7-1.)
The following default values are supplied by the SSCP(ILU) receiving the Format

Note:

a 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.

5·20

SNA Formats

INIT-SELF Format 1

INIT-SELF Formal 1 (INITIATE-SELF)
ILU

SSCP, Norm; FMD NS(s)
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).

INIT-SELF Format 1 (INITIATE-SELF)
Byte

Bit

X 1810681 1 NS header

0-2
3

0-3
4-7

Content

0-1

2-3
4
5

6
7
5

2-4
5-6

Format:
0001
Format 1
Reserved
Type:
01
initiate only (I): do not enqueue
11
initiate/enqueue (I/Q): enqueue the request if it cannot be satisfied immediately (See byte 5 for further specification of queuing conditions.)
Reserved
Reserved
Reserved
PLU/SLU specification:
o DLU is PLU (only value defined)
Reserved
Queuing conditions for DLU:
do not enqueue if session limit exceeded
1
enqueue if session limit exceeded
o do not enqueue if DLU is not currently able to comply with the PLU/SLU
specification (as given in byte 4, bit 6).
enqueue if DLU is not currently able to comply with the PLU/SLU specification
Reserved
Queuing position/service:
01
enqueue this request FIFO, i.e., the request will be dequeued after the
requests already in the queue
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-7

Reserved

8-15

Mode name: an 8-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

Chapter 5. Request/Response Units (RUs)

5-21

LUSTAT

INIT·SELF Format 1 (INITIATE·SELF)

Byte

Bit

Content

Type: X I F3 I logical unit

Length, in binary, of DLU name

18-n

EBCDIC character string

n+1-n+2

Retired

n + 3 - r(

=n + 3)

Reserved

r+1-s

User Request Correlation lURC) Field

r+1

Length, in binary, of URC
Note: X100 I
no URC. (The length field is always present.)

r+2-s

URC: LU-defined identifier; may 'be returned by the SSCP in a subsequent
NOTIFY to correlate a given session to this initiating request

LUSTAT (LOGICAL UNIT STATUS)
LU -. LU, Norm; DFC

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 a, 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.

LUSTAT (LOGICAL UNIT STATUS)

Byte

Bit

Content

X ' 04 1 request code

1-4

Status value + status extension field (two bytes each):
X 10000 I + I uuuu I user status (no system-defined status) + user-defined field
X 100011 + I ccdd I component now available + component identification (see
Note)
sender will have no (more) FMD requests to transmit during
X 100021 + I rrrri
the time that this session remains active + reserved field
X ' 0003 1+ 'ccdd ' component entering attended mode of operation + component identification (see Note)
X 100041 + I ccdd I component entering unattended mode of operation + component identification (see Note)
X 10005 1+ I iiii I
prepare to commit all resources required for the unit of work
+ information field:
X 100011
request End Bracket be sent on next chain (only
value defined)

5·22

SNA Formats

NMVT

LUSTAT (LOGICAL UNIT STATUS)

Byte

Bit

Content

X 10006 1+ I rrrri

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 1+ I rrrri
sender currently has no FMD requests to transmit (but may
have later during the time that this session remains active)
+ reserved field
X 108011 + 'ccdd I component not available (e.g., not configured) + component
identification (see Note)
X I 0802 1+ I ccdd I component failure (intervention required) + component
identification (see Note)
X ' 081C ' + 'ccdd I component failure (permanent error) + component identification (see Note)
X 10824 1+ I ccdd I function canceled + reserved field
X 10828 I + I ccdd I component available, but presentation space integrity lost +
component identification (see Note)
X ' 0831 1+ 'ccdd I component disconnected (power off or some other disconnecting condition) + component identification (see Note)
X 10848 1+ I rrrri
cryptography component failure + reserved field
X '400A I + I ssss I no-response mode not allowed + sequence number of the
request specifying no-response
Note: Values for cc byte are:
X100 I LU itself rather than a specific LU component (For this cc value,
dd=X'OO'.)
X I FF I
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.)
...., X I (001 FF) I LU component medium class and device address (For these cc
values, dd=X'OO'.)

NMVT (NETWORK MANAGEMENT VECTOR TRANSPORT)
SSCP ..---. PU Norm; FMC NS(ma)

NMVT carries management services (MS) requests and replies between an
SSCP and a PU.

NMVT (NETWORK MANAGEMENT VECTOR TRANSPORT)

Byte

Bit

Content

0-2

X ' 41038D' NS header

3-4

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

Chapter 5. Request/Response Units (RUs)

5-23

NOTIFY

NMVT (NETWORK MANAGEMENT VECTOR TRANSPORT)
Byte

Bit

Content

5-6

0-1

Reserved
Retired: Set to 01 by subarea PU sender; set to 00 by peripheral node sender;
ignored by receivers implementing the current level of SNA
Procedure related identifier (PRID)
Note: For unsolicited replies (byte 7, bit 0
0), the PRID field contains X 1000 I.
For solicited replies (byte 7, bit a
1), the PRID field echoes the PRID from the
NMVT RU request. For requests that need no replies, this field contains X 1000 I.

2-3
4-15

1-2

4-7
8-m

Flags:
Solicitation indicator: used only for PU-to-SSCP flow (reserved for SSCP-to-PU
flow):
o unsolicited NMVT
solicited NMVT
1
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
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 this NMVT does not contain
an SNA Address List subvector, or it contains an SNA Address List subvector that does not require address-to-name translation by the SSCP
1
For the SSCP-to-PU flow: MS major vector in this NMVT contains an SNA
Address List subvector
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
Reserved
One or more MS major vectors, as described (using a-origin indexing) in the
table in "MS Major Vectors and Unique Subvectors" on page 8-12.

NOTIFY (NOTIFY)
SSCP

4-~

LU, Norm; FMD NS(s)
NOTIFY is used to send information from an SSCP to an LU, or from an LU
to an SSCP. NOTIFY carries information in the form of a (vector key, vector
data) pair.

NOTIFY (NOTIFY)
Byte

Bit

X 1810620' NS header

0-2

5..24

Content

SNA Formats

NOTIFY

NOTIFY (NOTIFY)
Byte

Bit

3-p

Content
One NOTIFY vector as described in detail below:
X 103 1 ILU/TLU Notification: used to inform the sender of an INIT or TERM
request of the status of the procedure
X10C I 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 ().orlgln)

ILUITLU Notification NOTIFY Vector

ILU/TLU Notification NOTIFY Vector
Byte

Bit

Content
Key: XI 03 1

Status:

X100 I
X1011
X1021
X103 1

SSCP(OLU) and SSCP(DLU) not logically connected, i.e., no session or
session setup path (if rerouting is required) exists between them
session terminated
session set up
procedure error

2-9

Reserved

Reason (defined
Note: There are
•
If bit 4
0,
•
If bit 4 = 1,

o
1
2
3
4
5
6
7

for Status field value of X 103 1 only)
two encodings of the Reason byte:
the Reason byte is encoded for a setup procedure error.
the Reason byte is encoded for a takedown procedure error.

Setup Procedure Error
1
CINIT error in reaching the PLU
1
BIND error in reaching the SLU
1
setup reject at the PLU
1
setup reject at the SLU
0
setup procedure error
Reserved
1
setup reject at SSCP
Reserved

I
\"---

Chapter 5. Request/Response Units (RUs)

5-25

NOTIFY

ILUITLU Notification NOTIFY Vector
Byte

Bit

o
1
2
3
4
5

6
7

Content
Takedown Procedure Error
1
CTERM error in reaching the PLU
1
UNBIND error in reaching the SLU
1
takedown reject at the PLU
1
takedown reject at the SLU
1
takedown procedure error
1
takedown reject at the SSCP
o (see following Note)
Reserved
Note: For bits 4 and 6, the bit combination of 11 is set aside for implementation
internal use and will not be otherwise defined.

11-14

Sense data (defined for Status value of X 103 1 only)

15-m

Session key, as described in "Session Key" on page 8-11
Note: The following session key is used:
X 106 1 network name pair: PLU and SLU

m+1-n

User Request Correlation (URC) Field

m+1

Length, in binary, of the URC

m+2-n

URC: the URC carried in the URC field in INIT (bytes r+ 1- s) or TERM (bytes
n + 3 - p); used to correlate the NOTIFY to the initiating or terminating requests

LU·LU Session Services Capabilities NOTIFY Vector
Note: This NOTIFY vector should not be confused with control vector X I OC I,
which carries similar information.

LU·LU Session Services Capabilities NOTIFY Vector
Byte

Bit

Content

Key: XIOCI

Length of Vector Data field, encoded in binary

2-m

Vector Data

2
0-3
4-7

LU-LU session capability:
Reserved
Secondary LU capability:
0000
SLU capability is inhibited: sessions can be neither 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

3-4

Retired (set to X 100011)

5 -7

Retired

5-26

SNA Formats

NSPE

LU·LU Session Services Capabiiiiies NOTiFY Vecior
Byte

Bit

8-15( =m)

Content
Retired (set to all space (X'40') characters, or omitted)

NSPE (NS PROCEDURE ERROR)
SSCP -. ILU or TLU, Norm; FMD NS(s)

NSPE is used by the SSCP to inform an ILU or TLU that a session initiation
or termination attempt has failed after a positive response has been sent to
the corresponding initiation or termination request. (NSPE is used only if
Format 0 of INIT-SELF or TERM-SELF was issued. Otherwise, NOTIFY is
used.)

NSPE (NS PROCEDURE ERROR)

Byte

Bit

Content

0-2

X'010604' NS header

Note:

The remainder of this RU has two formats: a comprehensive form and a condensed form, based upon the setting of bit 7 of the Reason byte (byte 3). The
choice is implementation-dependent.
Comprehensive Format

Reason
Note: There are two encodings of the Reason byte in the comprehensive
format:
•
If bit 4
0, the Reason byte is encoded for a setup procedure error.
•
If bit 4 = 1, the Reason byte is encoded for a takedown procedure error.

o
1
2
3
4
5
6
7

Setup Procedure Error
1
CINIT error in reaching the PLU
1
BIND error in reaching the SLU
1
setup reject at the PLLI
1
setup reject at the SLU
0
setup procedure error
Reserved
1
setup reject at SSCP
1
comprehensive format of Reason byte

Chapter 5. Request/Response Units (RUs)

5-27

NSPE (NS PROCEDURE ERROR)

Byte

Bit

o
1

2
3
4
5
6
7

Content
Takedown Procedure Error
1
CTERM error in reaching the PLU
1
UNBIND error in reaching the SLU
1
takedown reject at the PLU
1
takedown reject at the SLU
1
takedown procedure error
1
takedown reject at SSCP
o see following Note
1
comprehensive format of Reason byte
Note: The bit combination of 11 for bits 4 and 6 is set aside for implementation
internal use and will not be otherwise defined.

4-7

Sense data

8-n

Session key. as described in the section "Session Key" on page 8-11
Note: One of the following session keys is used:
uninterpreted name pair: PLU and SLUt respectively (only value
X 106 1
defined)
Condensed Format

3
0
1
2
3
4
5
6
7

Reason:
CINIT error in reaching the PLU
1
1
BIND error in reaching the SLU
1
setup reject at the PLU
1
setup reject at the SLU
1
takedown failure
1
takedown reject at SSCP
1
setup reject at SSCP
o condensed format

4-m

Uninterpreted name of PLU

Type: X I F3 1 logical unit

Length. in binary. of PLU name

6-m

EBCDIC character string

m+1-n

Uninterpreted name of SLU

m+1

Type: X I F3 1 logical unit

m+2

Length. in binary. of SLU name

m+3-n

EBCDIC character string

QC (QUIESCE COMPLETE)
LU -+ LU, Norm; DFC

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

5-28

SNA Formats

RELQ

QC (QUiESCE COiviPLETE)

Byte

Bit

Content
X 1811 request code

QEC (QUIESCE AT END OF CHAIN)
LU

LU, Exp; DFC
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.

.....

QEC (QUIESCE AT END OF CHAIN)
Byte

Bit

Content
X 180 I request code

RECFMS (RECORD FORMATTED MAINTENANCE STATISTICS)
PU

SSCP, Norm; FMD NS(ma)
(Retired RU)
RECFMS has been retired from SNA for T2 nodes. Consult product documentation for further information and support.

RELQ (RELEASE QUIESCE)
LU

LU, Exp; DFC
RELQ is used to release a half-session from a quiesced state. This RU is
not used for LU 6.2

RELQ (RELEASE QUIESCE)
Byte

Bit

Content
X 1821 request code

Chapter 5. Request/Response Units (RUs)

5-29

RQR

REQDISCONT (REQUEST DISCONTACT)
PU T112

SSCP, Norm; FMD NS(c)
With REQDISCONT, the PU T112 requests the SSCP to start a procedure that
will ultimately discontact the secondary station in the T112 node.

REQDISCONT (REQUEST DISCONTACn
Byte

Bit

0-2

Content
X'01021B' NS header

0-3

4-7

Type:
X'O'
normal
X'8'
immediate
CONTACT information:
X'O'
do not send CONTACT immediately
X'1'
send CONTACT immediately
Note: Bits 4 -7 are reserved for switched connections.

REQMS (REQUEST MAINTENANCE STATISTICS)
SSCP

PU, Norm; FMD NS(ma)
(Retired RU)
REQMS has been retired from SNA for T2 nodes. Consult product documentation for further information and support.

RQR (REQUEST RECOVERY)
SLU

PLU, Exp;SC
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.

RQR (REQUEST RECOVERY)
Byte

Bit

5-30

Content
X'A3' request code

SNA Formats

S81

RSHUTD (REQUEST SHUTDOWNj
SLU

PLU, Exp;DFC

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.

RSHUTD (REQUEST SHUTDOWN)
Byte

Bit

Content

X'C2 1 request code

RTR (READY TO RECEIVE)
LU

LU, Norm; DFC

RTR indicates to the bidder that it is now allowed to initiate a bracket. RTR
is sent only by the first speaker.

RTR (READY TO RECEIVE)
Byte

Bit

Content
X10SI request code

SBI (STOP BRACKET INITIATION)
LU

LU,Exp;DFC

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.

SBI (STOP BRACKET INITIATION)
Byte

Bit

Content

X 171' request code

Chapter 5. Request/Response Units (RUs)

5-31

SHUTD

SDT (START DATA TRAFFIC)
PLU -. SLU, SSCP -. PUISsCP, Exp; SC

SOT is sent by the primary session control to the secondary session control
to enable the sending and receiving of FMO and OFC requests and
responses by both half-sessions. This RU is not used for LU 6.2.

SOT (START DATA TRAFFIC)

Byte

Bit

Content
X I AO I request code

SHUTC (SHUTDOWN COMPLETE)
SLU -. PLU, Exp;DFC

SHUTe is sent by a secondary to indicate that it is in the shutdown (quiesced) state. This RU is not used for LU 6.2.

SHUTC (SHUTDOWN COMPLETE)

Byte

Bit

Content
X I C1

request code

SHUTD (SHUTDOWN)
PLU -. SLU, Exp; DFC

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.

SHUTD (SHUTDOWN)

Byte

Bit

5-32

Content
XICO' request code

SNA Formats

STSN

SIG (SIGNAL)
LU ... LU, Exp; DFC

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.

SIG (SIGNAL)
Byte

Bit

Content

XI C9 1 request code

1-2

Signal code:
no-op (no system-defined code)
X '0000'
X 10001 1 request to send (only value defined for LU 6.2)
XI 0002 1 assistance req uested
XI 0003 1 intervention required (no data loss)

3-4

Signal extension: set by the sending end user or NAU services manager, or set
to X 100011 for LU 6.2 by data flow control

STSN (SET AND TEST SEQUENCE NUMBERS)
PLU ... SLU, Exp;SC

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 session. This RU is not used for LU 6.2.

STSN (SET AND TEST SEQUENCE NUMBERS)
Byte

Bit

Content
X'A2 1 request code

Chapter 5. Request/Response Units (RUs)

5·33

TERM-SELF Format 0

STSN (SET AND TEST SEQUENCE NUMBERS)
Byte

Bit

Content

0-1

Action code for S ~ P flow (related data in bytes 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
Reserved

2-3

4-7
2-3

Secondary-to-primary sequence number data to support S

P action code

4-5

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 halfsession'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 (TERMINATE-SELF)
TLU

SSCP, Norm; FMD NS(s)

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.

TERM-SELF Format 0 (TERMINATE-SELF)
Byte

Bit

0-2

X'010683' NS header
Type:

3
0-1

5-34

Content

SNA Formats

00
01
10
11

the request applies to active and pending-active sessions
the request applies to active, pending-active, and queued sessions
the request applies to queued only sessions
reserved

TERM-SELF Format 1

TERM-SELF Format 0 (TERMINATE-SELF)
Byte

Bit

Content

Reserved if byte 3, bit 4
1; otherwise:
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
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
0
orderly or forced (see byte 3, bit 2)
1
clean up
00
select sessions for which DLU is PLU
01
select sessions for which DLU is SLU
10
select sessions regardless of whether DLU is SLU or PLU
11
reserved
0
indicates that the format of the RU is Format 0 and that byte 3 is the Type
byte.

5- 6

4-5

Uninterpreted Name of DLU (retired):

Type: XI F3 I logical unit

Length: X 100 I only value allowed, and always present
Note: Because the length value of the DLU name is 0, the TERM-SELF applies
to all sessions, as specified in the Type byte, where the TLU is a partner.

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 1 (TERMINATE-SELF)
TLU -+ SSCP, Norm; FMD NS(s)
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.

TERM·SELF Format 1 (TERMINATE·SELF)
Byte

Bit

X1810683 1 NS header

0-2
3

Content

0-3

4-6
7

Format:
0001
Format 1 (only value defined)
Reserved
1
indicates that byte 3, bits 0 - 3, contain the format value

Chapter 5. Request/Response Units (RUs)

5-35

TERM-SELF Format 1

TERM-SELF Format 1 (TERMINATE-SELF)

Bit

Byte

0-1

4
5- 6

5
0
1

2-7
6

0-5
6

Content

Type:
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
Reserved if byte 4, bit 7
1; 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
o 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 (only value defined for LU
6.2)
Reserved
00
select sessions for which DLU is PLU
01
select sessions for which DLU is SLU
10
select s~ssions rega~dless of whether DLU is SLU or PLU
11
reserved
0
orderly or forced (see byte 4., bit 2)
1
clean up

Reason:
network user
1
network manager
o normal termination
1
abnormal termination
Reserved

NOTIFY specifications (reserved for LU 6.2):
Reserved
o do not notify TLU when the session takedown procedure is complete
1
notify the TLU when the session takedown procedure is complete
Reserved

Reserved

8-n

Session key, as described in the section "Session Key" on page 8-11
X'OA' URC
Note: This URC is the one carried in the INIT issued previously by the
same LU (Le., ILU = TLU), and differs from the one in bytes n +4
through p.

n+1-n+2

Retired

n+3-p

User Request Correlation CURC) Field

n+3

Length, in binary, of URC field
Note: X1001 = no URC.

n+4-p

URC: LU-defined identifier; this value can be returned by the SSCP in a subsequent NOTIFY to correlate the NOTIFY to this terminating request

5-36

SNA Formats

UNBIND

UNBIND (UNBIND SESSION)
LU -. LU, Exp;SC
UNBIND is sent to deactivate an active session between the two LUs.

UNBIND (UNBIND SESSION)

Byte

'---

Bit

Content
X 1321 request code
UNBIND type (for UNBIND types XIOOI through X ' 06 1 and X'BO' through X'FF',
the session is ended when the response is received; for UNBIND types X 107 1
through X '7F I , the session is ended immediately):
X 101 1 normal end of session
X 1021
BIND forthcoming; retain the node resources allocated to this session,
if possible
X I 06 I
invalid session parameters: the BIND negotiation has failed because
the primary half-session cannot support parameters specified by the
secondary
X 107 1 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
route
extension inoperative: the route extension used by the LU-LU
X'OB'
session has become inoperative, thus forcing the deactivation of the
identified LU-LU session
1
hierarchical reset: the identified LU-LU session is being deactivated
X ' 09
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' 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
XIOCI
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
LU failure-recoverable: the identified LU-LU session had to be deactiX'OE'
vated because of an abnormal termination of one of the LUs of the
session; recovery from the failure may be possible
cleanup: the node sending UNBIND is resetting its half-session before
X'OF'
receiving the response from the partner node
X I 11 1 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 I FE I session failure: the session has failed for a reason specified by the
associated sense data

For session stages 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 I FE I.

Chapter 5. Request/Response Units (RUs)

5-37

UNBIND

UNBIND (UNBIND SESSION)
Byte

Bit

Content

2-5

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 2 - 5 of the Extended Sense Data control vector; otherwise, this field (bytes 2 - 5 of the UNBIND RU) is reserved.

6-n

Control vectors, as described in the section "Control Vectors" on page 8-4
Note:' The following control vectors may be included; they are parsed according
to subfield parsing rule KL:
X 135 1 Extended Sense Data control vector (present when the UNBIND Type is
X ' 06 1, X'FE', or is immediate, i.e., X ' 07 1 through X'7F')
X 160 I
Fully-qualified PCID control vector (present on session stages 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-38

SNA Formats

Response Units

Introduction to Response Units
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
1
DFC
SC
1
NC
1
3
FMD NS (FI 1) (field-formatted)
a
FMD NS (FI 0) (character-coded)
FMD (LU-LU)
a

=
=

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, "Sense Data" on page 9-1 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-41 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

session control

network control

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 a'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 a's except where other unique values are required (described individChapter 5. Request/Response Units (RUs)

5-39

Response Units

ually); no receive checks are made on these fields, thereby accepting backlevel 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, "User Data Structured Subfields"
on page 7-1 and Chapter 8, "Common Fields" on page 8-1.

5-40

SNA Formats

RSP(ACTPU)

Positive Response Units with Extended Formats
RSP(ACTLU)
~

SSCP, Exp;SC

RSP(ACTLU)

Byte

Bit

Content

X'OD' request code

Type of activation selected:
XI 02 1 ERP (only value defined)

0-3
4-7

2
Note:

FM profile: Same as the corresponding request
TS profile: same as the corresponding request
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" on page 8-4
Note: The following control vectors may be included; they are parsed according
to subfield parsing rule KL. When present, they appear in the order specified.
X1001
SSCP-LU Session Capabilities control vector (always present, always
first)
X10CI
LU-LU Session Services Capabilities control vector (always present,
always second)

A two-byte response may be received; it means maximum RV size
256 bytes, LV-LV session limit
1, the LV can act as a secondary LV, and all other fields in control vectors X1001 and X10CI are
defaulted to 0' s.

RSP(ACTPU)

SSCP, Exp; SC

RSP(ACTPU)

Byte

Bit

o
1

X 1111 request code
0-1

2-3
4-7
2-9

Content

Reserved
Format of response:
00
format 0 (only value defined)
Type activation selected:
X 12 1 ERP (only value defined)
Contents ID: eight-:character EBCDIC symbolic name of the load module currently operating in the node; eight space (X 140 I) characters is the default value

Chapter 5. Request/Response Units (RUs)

5-41

RSP(BIND)

SLU

PLU, EXPiSC
A + RSP(BIND) carries the session parameters as indicated by the SLU or
by intermediate nodes along the session path.
• A short (1-byte) response may be sent for a non extended nonnegotiable
BIND request that specifies no session-level cryptography.
• A cryptography response (bytes 0 - k) may be sent for a nonextended
nonnegotiable BIND request that specifies session-level cryptography.
• A nonextended negotiable response (bytes 0 - r) may be sent for an
extended or nonextended negotiable BIND request.
• An extended response (bytes 0 - 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.

RSP(BIND)
Byte

Bit

Content
X 1311 request code

0-3
4-7

Format: 0000 (only value defined)
Type:
0000
negotiable (only value defined for LU 6.2)
0001
nonnegotiable

2-25

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

26-k

Cryptography Options (see Note 3) for a nonnegotiable response, same value
returned as received for a nonnegotiable response or an LU 6.2 response
Session-level cryptography options field length: same value as in BIND (Bytes
27 - k are omitted if this length field is omitted or set to 0.)

4-7
0-1

2-4
5-7

Session cryptography key encipherment method: same value returned as
received in the request, if present
Reserved
Cryptography cipher method: same value returned as received

28-k

An 8-byte implementation-chosen, nonzero, pseudo-random session-seed
cryptography value enciphered under the session cryptography key, if sessionlevel cryptography is specified; otherwise, omitted

k+1(=m)

Retired: set to 0 by implementations at the current level of SNA

m+1

Length of user data

m+2-n

User data: for an extended or negotiable response, the user data may differ
from that received on the BIND request

n+1

Length of URC

n+2-p

URC as received on the BIND request

5-42

SNA Formats

RSP(BIND)

RSP(el~JO)

Byte
p + 1(

Bit

=r)

Content

Retired: set to 0 by implementations at the current level of SNA

r+1-s

Control vectors, as described in "Control Vectors" on page 8-4
Note: The following control vectors may be included; they are parsed according
to subfield parsing rule KL:
X10E I Network Name control vector: CP network name (conditionally present,
used in extended BIND responses when neither the Fully-Qualified
PCID [X 160'] control vector nor the Route Selection [X' 2B'] control
vector contain the CP(PLU) name)
X' 60'
Fully-Qualified PCID control vector (present if received on the BIND)

Note 1:

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 2:

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 non extended 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 4:

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:

An extended short response to a nonnegotiable BIND is of the following form:

X' 31' request code

0-3

4-7
2-5
6

Reserved

1-7
7

Format: 0000 (only value defined)
0001
nonnegotiable

0-5
6
7

Whole-BIUs required indicator (reserved in nonextended non-LU6.2 BIND
responses):
o the sending n,ode (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
Reserved
Reserved
Control vectors included indicator:
1
control vectors are present (only value defined)
Reserved
Chapter 5. Request/Response Units (RUs)

5-43

RSP(STSN)

RSP(BIND)
Byte

Bit

0
1-7
0

Content
Secondary-to-primary pacing staging indicator:
pacing in the secondary-to-primary direction occurs in one stage (only
value defined)
Reserved

Adaptive session-level pacing support:
adaptive pacing not supported by the sending node
1
adaptive pacing supported by the sending node
Reserved

o
1-7
10

Maximum RU size sent on the normal flow by the secondary side of the session

Maximum RU size sent on the normal flow by the primary side of the session

0
1-7

Primary-to-secondary pacing staging indicator:
1
pacing in the primary-to-secondary direction occurs in one stage (only
value defined)
Reserved

13 - 30( = r)

Reserved

r+1-s

Control vectors, as described in the section "Control Vectors" on page 8-4
Note: The following control vectors may be used; they are parsed according to
subfield parsing rule KL:
Fully-Qualified PCID control vector (always present)
X 160 I

RSP(STSN)
SLU

PLU, Exp;SC

RSP(STSN)
Bit

5-44

Content
XIA2 1 request code

SNA Formats

RSP(STSN)

RSP(STSt~)

Byte

Bit

Content

0-1

Result code for S -+ P action code in the request (related data in bytes 2 - 3)

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 number indicated could not have occurred. For example, the 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)
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)
Reserved

4-7
2-3

Secondary-to-primary normal-flow sequence number data to support S -+ P
result code, or reserved (see Note above)

4-5

Primary-to-secondary normal-flow sequence number data to support P -+ S
result code or reserved (see Note 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. Request/Response Units (RUs)

5-45

RSP(STSN)

5-46

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 in 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).

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 1, 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.

TS Profit e

Sess;on Types

SSCP-PU(TI12),l SSCP-LU

LU-LU

0, I, 2, 3

LU-LU

I, 6.1

LU-LU

4, 6.2, 7

LU Types

The boundary funct;on serves ;n place of the PU type 1 (e.g ••
to process ACTPU).

Figure

6-1. TS Profiles and Their Usage

Chapter 6. Profiles

6-1

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).
• SOT, CLEAR, RQR, STSN, and CRY 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.
No TS Usage field is 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.
• SOT, RQR, STSN, and CRY are not supported.
The TS Usage subfields defining the options for this profile are:
• Pacing window counts
• Maximum RU sizes on the normal flows

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.
• CRY 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.
• CRY is supported when session-level cryptography is selected (via a BIND
parameter).

6-2

SNA Formats

The TS Usage subfields defining the options for this profile are:
• Pacing window counts
• Maximum RU sizes on the normal flows

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.
• CRY 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

Function Management (FM) Profiles
This section describes the function management (FM) profiles and their use for
LU-LU sessions; SSCP-PU sessions to Type 1, 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.

FH Profile

Session Types

LU Types

SSCP-PU(T112),l SSCP-LU

LU-LU

0, 1, 2, 3

LU-LU

0, 1

.SSCP-LU

LU-LU

0, 4, 7

LU-LU

0, 6.1

LU-LU

6.2

The boundary function serves in place of the PU type 1 (e.g.,
to process ACTPU).

Figure

6-2. FM Profiles and Their Usage

Chapter 6. Profiles

6-3

FM Profile 0
Profile a (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. Halfsession 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 OFC RUs.
• 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 OFC 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 FOX.
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

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 OFC functions:
CANCEL
SIGNAL
LUSTAT (allowed secondary-to-primary only)
CHASE
SHUTO
SHUTC
RSHUTD

6-4

SNA Formats

BID and RTR (allowed only if brackets are used)

The FM usage fields defining the options for Profile 3 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

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:
•
•
•
•
•
•
•
•
•
•
•
•
•
\" ....

Chapter 6. Profiles

6-5

FM Profile 6
Profile 6 (used on SSCP-LU sessions) specifies the following session rules:
• 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.
• No FM headers.
• No compression.
• No brackets.
• No alternate code.
• Normal-flow send/receive mode is full-duplex.

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:
•
•
•
•
•
•
•
•
•
•
•
•
•

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:
-

6-6

SNA Formats

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:
•
•
•
•
•
•
•
•
•
•
•
•
•

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 endchain RUs:
RQE'" , CD, ...,CEB
RQD2, CD, ..., CEB
RQD3, CD, ..., CEB
RQE1, ...,CD, CEB
RQD"', ...,CD, CEB
RQD"', ...,CD, ...,CEB
• Alternate code permitted.

Chapter 6. Profiles

6-7

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

6-8

SNA Formats

User Data Subflelds Introduction

Chapter 7. User Data Structured Subfields

Introduction
The structured subfields of the User Data field are defined as follows (shown
with O-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, Session Qualifier, Random Data,
Enciphered Data, 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 Subflelds

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

Unformatted Data Structured Data Subfleld
Bit

Byte

Content
Length of the remainder of the Unformatted Data subfield: values 1 to 17
(XI111) are valid for LU 6.2; otherwise, values 1 to 65 (X'411) are valid
X100I

2-n

Unformatted data: a type-G symbol string

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

Session Qualifier Structured Data Subfleld
Bit

Byte

Content

Length of the remainder of the Session Qualifier subfield (If Session Qualifier
subfield is present, values 3 to 19 (X 113 1) are valid.)

X 101'

Length of primary resource qualifier: values 0 to 8 are valid (X 100 1 means no
primary resource qualifier is present)

3-m

Primary resource qualifier

m+1

Length of secondary resource qualifier: values 0 to 8 are valid (X 100' means no
secondary resource qualifier is present)

m+2-n

Secondary resource qualifier

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

7 -2

SNA Formats

User Data Subfields

Mode Name Structured Data Subfleld
Byte

Bit

Content

Length of the remainder of the Mode Name subfield: values 1 to 9 are valid

X' 02 1
2-n

Mode name: 0 to 8 Type-1134 symbol-string characters (a character string consisting of one or more EBCDIC uppercase letters A through Z; numerics 0
through 9; the first character of which is an uppercase letter). The symbol
string may be assigned to a longer field and padded with blanks on the right,
but these trailing blanks are not considered part of the Mode name.

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

Session Instance Identifier Structured Data Subfleld
Byte

Bit

Content

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

X' 03 1

2-n

Session Instance Identifier

Format:
X1001
retired in BIND, used in RSP(BIND) only when Format X1001 was used
in BIND and PLU name ~ SLU name
X 101 1 used in BIND only
X 1021
used in RSP(BIND) only in response to Format X 1011 in BIND
XI FO 1 used in RSP(BIND) only when Format XI 00 1 was used in BIND and PLU
name > SLU name

3-n

Type-G symbol string identifying the session instance (generated by PLU;
echoed by SLU, except for Format X 1021): null for Format X 1021; otherwise, 1 to
7 bytes.

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

Chapter 7. User Data Structured Subfields

7-3

User Data Subflelds

Network-Qualified PLU Network Name Structured Data Subfield
Byte

Bit

Content

Length of the remainder of the Network-Qualified PLU Network Name subfield:
values 2 to 18 (X'121) are valid

X ' 04 1

2-n

Network-Qualified PLU network name
Note: The network-qualified PLU network name is 1 to 17 bytes in length. consisting of an optional 1- to 8-byte network 10 and a 1- to 8-byte LU name, both of
which are type-1134 symbol strings (a character string consisting of one or
more EBCDIC uppercase letters A through Z; numerics 0 through 9; the first
character of which is an uppercase letter). When present, the network 10 is
concatenated to the left of the LU name, using a separating period and having
the form "NETIO.NAME"; when the network 10 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).

Network-Qualified .SLU Network Name Structured Data Subfield
Byte

Bit

Content

Length of the remainder of the Network-Qualified SLU Network Name subfield:
values 2 to 18 (X 1121) are valid

X ' 05 1

2-n

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 10 and a 1- to 8-byte LU name, both of
which are type-1134 symbol strings (a character string consisting of one or
more EBCDIC uppercase letters A through Z; numerics 0 through 9; the first
character of which is an uppercase letter). When present, the network 10 is
concatenated to the left of the LU name, using a separating period and having
the form "NETIO.NAME"; when the network io 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 is in effect,
this subfield is present in both BIND and RSP(BINO).

7-4

SNA Formats

User Data Subfields

Random Data Structured Data Subiield
Byte

Bit

Content

Length of the remainder of the Random Data subfield: 10 is the only valid value

Xl 11 1

Reserved

3-10

Random data: a type-G random value generated for subsequent checking in
RSP(BIND) or FMH-12

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

Enciphered Data Structured Data Subfleld
Byte

Bit

Content

Length of the remainder of the Enciphered Data subfield: 9 is the only valid
value

X ' 12 1

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)

Chapter 7. User Data Structured Subfields

7-5

User Data Subfields

7-6

SNA Formats

Common Fields

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 XIOOI to X ' 7F' are unique; within the independent category of management services (MS) subvectors, they are also unique.
Context-Sensitive Keys: Keys in the range X 180 I to X I FD I are contextsensitive. These are unique only within the enclosing structure (e.g., a specific
control vector or GDS variable). Thus, a subfield key X 180 I may be defined for
use within control vector X 130 I and also within control vector X 131 1, and the
subfields may be different. The only exception to this rule is found in the management services subfields. Keys in the range X 100 I to X '7F I are unique only
within the enclosing subvector. However, keys in the range X 180 I to X I FF I 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.

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

Example of common substructure format
Byte

Bit

Content

The general format of a control vector, for example, is shown as:

0-1

Vector header; Key=X'45 1 (see "Substructure Encoding/Parsing Rules")

2-n

Vector Data

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

8-2

Key

SNA Formats

Encoding/Parsing Rules

Example of common substructure format
Byte

Bit

Content
Length (n-1), in binary, of the Vector Data field (Le., excluding the length of the
Vector Header field)

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

Length (n + 1), in binary, of the control vector (Le, 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 10 (X 110 1) control vector as an example of this rule.
Imbedded within this substructure are other substructures, specifically Product
Identifier (X 1111) MS common subvectors.
When the Product Set 10 (X 110 I) is present in XID 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 1111) 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 messageunit structures that can carry the control vector.
Key

Control Vector

Applicable Message-Unit Structures

X1001
X10CI
X'OE'
X I 10 1
X ' 22 1
X ' 2C'
X ' 2D'
X ' 35 1
X ' 60 '

SSCP-LU Session Capabilities
LU Session Services Capabilities
Network Name
Product Set ID
XID Negotiation Error
COS/TPF
Mode
Extended Sense Data
Fully Qualified PCID

RSP(ACTLU)
RSP(ACTLU)
XID, BIND
XID
XID
BIND
BIND
UNBIND
BIND, UNBIND, RSP(BIND)

Control Vector Formats
The control vectors are defined as follows (with O-origin 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' 00') Control Vector

SSCP·LU Session Capabilities (X' 00') Control Vector
Byte

Bit

Content

Key: X1001

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 I ab I = a x 2b (Notice that, by
definition, a~8 and therefore X I ab I is a normalized floating point representation.) See Figure 5-1 on page 5-15 for all possible values.

8-4

SNA Formats

Control Vectors

SSCp·LU Session Capabilities (X' 00') Control Vector
Byte

Bit

2- 3

2 -15

Content
LU Capabilities:
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 informa~ion after a positive response has already been sent
the SSCP may send unsolicited character-coded requests
Field-formatted capability:
o the SSCP may not send unsolicited field-formatted requests
1
the SSCP may send unsolicited field-formatted requests
Reserved
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.

LU·LU Session Services Capabilities (X' OC') Control Vector
Byte

Bit

Content

0-1

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

2-m

Vector Data

0-3
4-7

(reserved)
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

3-4

LU-LU session limit:
0001
session limit of 1 (only value allowed for peripheral LUs)

5-6

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

Chapter 8. Common Fields

8-5

Control Vectors

Network Name (X' OE') Control Vector

Network Name (X' OE ') Control Vector
Byte

Bit

Content

0-1

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.

2-n

Vector Data

Network name type:
X'F1 1 PU name
X'F3 1 LU name
X'F4 1 CP name
XI F71

3-n

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-1134 symbol-string name; when present, the
qualifier contains a 1- to 8-byte type 1134-symbol string network identifier concatenated with a period (when the qualifier is not present, the period is
omitted). The network-qualified name appears, for example, as follows:
NETID.NAME, with no imbedded blanks and with optional (but not significant)
trailing blanks.

Product Set 10 (X '10 ') Control Vector

Product Set 10 (X' 10') Control Vector
Byte

Bit

Content

0-1

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

2- n

Vector Data

Retired

3- n

Network product identifier: one or two Product Identifier (X 1111) MS common
subvectors, as described in "MS Common Subvectors" on page 8-165, one for
each hardware product and software product in the implem'entation of the node

8-6

SNA Formats

Control Vectors

XID Negotiation Error (X' 22') Control Vector

XID Negotiation Error (X' 22') Control Vector
Byte

Bit

Content

0-1

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

2-n

Vector Data

2-3

Error byte offset: the binary offset (a-origin in the XID information field) of the
first byte of the field in error

4( =n)

Error bit offset: the binary offset (a-origin in the byte pointed to in the Error Byte
Offset field) of the first bit of the field in error

COS/TPF (X I 2C ') Control Vector

COSITPF (X' 2C ') Control Vector
Byte

Bit

Content

0-1

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

2-m

Vector Data

0-4
5

6-7

Reserved
Network priority indicator:
a
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.
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

4-m

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

Chapter 8. Common Fields

8-7

Control Vectors

Mode (X' 2D ') Control Vector

Mode (X' 2D') Control Vector
Byte

Bit

Content

0-1

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

2-n

Vector Data

Length of Mode Name field

3-n

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

Extended Sense Data (X' 35') Control Vector

Extended Sense Data (X' 35') Control Vector
Byte

Bit

Content

0-1

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

2-p

Vector Data

2-5

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

6-p

Extended Sense Information

1-2

8-8

SNA Formats

RU information included:
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)
RU category (reserved when bit 0 = 0):
00
FMD
01
NC
10
DFC
11
SC
FMD message-unit type (reserved when RU category is not FMD):
o FMD message unit is not a GDS variable
FMD message unit is a GDS variable
1
Generator of Extended Sense Data control vector (reserved when Termination
Procedure Origin Name field not present):
o the termination procedure origin
1
a node other than the termination procedure origin

Control Vectors

Extended Sense Data (X' 35') Control Vector
Byte

Bit

Content

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
Reserved

6-7

= 0)

Length of RU or GDS Variable Identifier field (set to 0 when byte 6, bit 0

8-m

Identifier: request code, NS header, or GDS variable identifier (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.

m+1

Length of Termination Procedure Origin Name field (values 3 to 26 are valid)

m+2-n

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
Notet: 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 termination, 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]).
Note2: The network identifier is always included in the termination procedure
origin name.

n+1-p

Related resource (If the length in byte n + 1 is 0, the Related Resource field may
be omitted.)

n+1

Length of Related Resource Name field (values 0 to 17 are valid)

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.

Chapter 8. Common Fields

8-9

Control Vectors

Fully-qualified PCID (X' 60') Control Vector

Fully-qualified PCID (X'60') Control Vector
Byte

Bit

Content

0-1

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

2-n

Vector Data

2-9

PCID: a unique value used as a procedure identifier

Length of Network-Qualified CP Name field (values 3 to 17 are valid)

11-n

Network-qualified CP name (network identifier present)

8-10

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

Applicable Message-Unit Structures

X 1 06 1

Uninterpreted Name Pair

NOTIFY. NSPE

URC

TERM-SELF

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

Network Name Pair or Uninterpreted Name Pair (X' 06') Session Key

Network Name Pair or Unlnterpreted Name Pair (X' 06') Session Key
Byte

Bit

Content

Key: X 106 1

Type: XI F3 1 logical unit

Length. in binary. of PLU (or OLU or LU1) name

3-m

Name in EBCDIC characters (see Note below)

m+1

Type: XI F3 I logical unit

m+2

Length. in binary. of SLU (or DLU or LU2) name

m+3-n

Name in EBCDIC characters (see Note below)

Note:

For a Network Name Pair session key. the names consist of type-1134 symbolstring characters; for an Uninterpreted Name Pair session key. the names are
any EBCDIC strings.

IURC (X'OA ') Session Key
URC (X' OA ') Session Key
Byte

Bit

Content

Key: X10AI

Length. in binary. of the URC

2-n

URC: LU-defined identifier

Chapter 8. Common Fields

8-11

MS Major Vectors

MS Major Vectors and Unique Subvectors
Introduction
The following table shows, by key value, the MS major vectors that an NMVT or
CP-MSU can carry.
Key

MS Major Vector

Applicable Message-Unit Structures

XIOOOOI
X ' 0050 '
X ' 0061 1
X ' 0062 1
X ' 0063 1
X ' 0064 1
X ' 0066 1
X ' 006F'
X ' 0080 '
X ' 0090 '
X ' 8050 '
X ' 8061 1
X ' 8062 1
X ' 8063 1
X ' 8064 1
X ' 8066 1
X ' 8080 '
X ' 8090 '

Alert
Change Control
Reply to Execute Command
Reply to Analyze Status
Reply to Query Resource Data
Reply to Test Resource
Reply Activation Acceptance
Send Message To Operator
RTM
Reply Product Set 10
Request Change Control
Execute Command
Analyze Status
Query Resource Data
Test Resource
Request Activation
Request RTM
Request Product Set 10

NMVT
CP-MSU
NMVT
NMVT
NMVT
NMVT
CP-MSU
NMVT
NMVT
NMVT
CP-MSU
NMVT
NMVT
NMVT
NMVT
CP-MSU
NMVT
NMVT

Note: The major vectors are defined as follows (using O-origin indexing):
• The description of each major vector includes a matrix indicating the subvectors that may be included within it.
• Subvectors with keys X 180 I through X I FE I have a meaning that is unique to
the major vector in which they are used. They are defined following each
major vector.
• Subvectors with keys X 100 I through X '7F I 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-165.
• Subvectors may appear in any order within a major vector unless otherwise
stated.

8·12

SNA Formats

MS Major Vectors

MS Major Vector Formats

Alert (X I 0000 I) 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.

Alert (X' 0000') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X' 0000'

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X'OO' -X'7F', and in "Alert MS
Subvectors" on page 8-16 for subvector keys X'80' -X'FE'.
Note: The following subvector keys may be used as indicated:

Chapter 8. Common Fields

8-13

MS Major Vectors

Subvector

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

Text Message (X'OO')

Note 1

Date/Time (X'Ol)

Note 2

Hierarchy Name List (X'03')

Note 3

SNA Address List (X'04')

Note 4

Hierarchy/Resource List (X' 05')

Note 5

Set ID (X'10')

Pen)

Note 6

Self-Defining Text Msg. (X '31')

Relative Time (X'42')

Note 7

Supporting Data Correl. (X'48')

Note 8

LAN Link Connection
Subsystem Data (X'51')

Note 9

LCS Configuration Data (X'52')

Note 10

SDLC link Station Data (X'8C')

Note 11

Basic Alert (X'91')

Note 12

Generic Alert Data (X'92')

Probable Causes (X'93')

User Causes (X'94')

Note 13

Insta 11 Causes (X'95')

Note 13

Fa il ure Causes (X '96')

Note 13

Cause Undetermined (X'97')

Note 14

Detailed Data (X'98')

Pro~uct

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

P
CP(n)
CP

o
O(n)

O(n)

Note 15

Present one time
Present one or more times
Conditionally present one time (See Notes for
conditions.)
Optionally present one time
Optionally present one or more times

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 nongeneric Alert and a generic Alert focal point. If this subvector is present.
the X 1911 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.

8-14

SNA Formats

MS Major Vectors

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 1911 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 is present in the NMVT instead of, or in addition to, the SNA
Address List (X I 041) 5ubvector if the origin (other than the PU sending the
Alert) of the Alert condition cannot be represented in the SNA Address List
(X I 041) subvector.
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 I 10 1 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 101 1) subvector, it
places this subvector in the NMVT instead.
8. This subvector is present if the Alert sender has preserved supporting data,
e.g., a storage dump, to which the Alert must be correlated.
9. This subvector is present when the Alert reports an error on a LAN, and the
node sending the Alert is attached to the LAN.

10. This subvector is present when the Alert reports a problem with a logical
link using the SDLC or LAN LLC protocol.
11. This subvector is present when the Alert reports a problem with a logical
link using the SDLC or LAN LLC protocol.
12. 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 nongeneric Alert and a generic Alert focal point.
13. 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.

14. This subvector is present in an Alert if and only if none of the X 194 1, X 195 1,
and X 196 I subvectors is present.
15. 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

Chapter 8. Common Fields

8-15

MS Major Vectors

point. If either of these subvectors is present, the X 1911 subvector is also
present.

Alert MS Subvectors
SOLC Link Station Data (X' 8C ') Alert MS Subvector
This subvector transports SOLC or LAN LLC link station failure information.

SOLe Link Station Data (X'8C') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the SOLC Link Station Data subvector

Key: X ' 8C'

2-p

Subfields containing SOLC link station data (listed by key value below and
described in detail following):
X1011 Current N(S)/N(R) Counts
X1021 Outstanding Frame Counts
XI 03 1
Last SOLC Control Field Received
1
X ' 04
Last SOLC Control Field Sent
XI 05 1
Sequence Number Modulus
XI 06 1
Link Station State
X ' 07 1
LLC Reply Timer Expiration Count
1
XI 08
Last Received N(R) Count

Current N(S)/N(R) Counts (X 1011) SDLC Link Station Data Subfield
This subfield transports the current N(S) and N(R) counts for a link station.

Current N(S)/N(R) Counts (X' 01') SDLC Link Station Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Current N(S)/N(R) Counts subfield

Key: X 1 01

N(S) count, in binary

3( =q)

N(R) count, in binary

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

8-16

SNA Formats

MS Major Vectors

Outstanding Frame Count (X' 02') SDle link Station Data Subfield
Byte

Bit

Content

Length (q + 1). in binary, of the Outstanding Frame Count subfield

Key: X102 '

2( =q)

Outstanding frame count, in binary

Last SDLC Control Field Received (X '03 ' ) SDLC Link Station Data Subfield
This subfield transports the last SOLC control field received from the secondary station before the error occurred.

Last SOLC Control Field Received (X' 03') SDLC Link Station Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Last SOLC Control Field Received subfield

Key: X 103 '

2-3(=q)

Last SOLC control field received; if the SOLC control is only one byte long, then
byte 3's value is X '00 I.

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

Last SOLC Control Field Sent (X' 04') SOLC Link Station Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Last SOLC Control Field Sent subfield

Key: X 104 '

2-3(=q)

Last SOLC control field sent; if the SOLC control is only one byte long, then byte
3's value is X '00 I.

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

Chapter 8. Common Fields

8:"17

MS Major Vectors

Sequence Number Modulus (X' 05') SDLC Link Station Data Subfleld
Byte

Bit

Content

Length (q + 1). in binary. of the Sequence Number Modulus subfield

Key: X10SI
. Modulus. in binary

2( =q)

Link Station State (X ' 06 1) SDLC Link Station Data Subfield

This subfield indicates busy conditions at the local or remote link station.

Link Station State (X'06') SDLC Link Station Data Subfleld
Byte

Bit

Content

Length (q + 1). in binary. of the Link Station State subfield

Key: X ' 06 1

2(=q)

o
1

2-7

Link station states:
State of the local link station:
o local link station not busy
1
local link station busy (RNR sent)
State of the remote link station:
o remote link station not busy
1
remote link station busy (RNR received)
Reserved

LLC Reply Timer Expiration Count (X ' 071) SDLC Link Station Data Subfield

This subfield transports the number of times the LLC Reply Timer (T1)
expired.

LLC Reply Timer Expiration Count (X'07') SOLC Link Station Data Subfield
Byte

Bit

Content

Length (q + 1). in binary. of the LLC Reply Timer Expiration Count subfield

Key: X ' 07 1

2-3

Count. in binary. of LLC Reply Timer (T1) expirations

8-18

SNA Formats

MS Major Vectors

Last Received N(R) Count (X 108 1) SDLC Link Station Data Subfield

This subfield transports the most recently received N(R) count.

Last Received N(R) Count (X' 08') SOLC Link Station Data Subfield
Byte

Bit

Content
Length (q + 1). in binary. of the Last Received N(R) Count subfield
Key: X I 08 1

2(=q)

N(R) count. in binary

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

Basic Alert (X' 91') Alert MS Subvector
Byte

Bit

Content

Length (p + 1). in binary. of the Basic Alert subvector

Key: X I 91

o
1

2-3

4-7
3

Flags:
Initiation indicator:
o Alert not directly initiated by an operator action
1
Alert initiated by an operator action
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.
Reserved
Retired
Alert type:
X 1011
permanent loss of availability: a loss of availability to the end user that
is not recovered from without intervention external to the reporting
product
temporary loss of availability: a momentary loss of availability that will
X 1021
probably be noticed by the end user. yet is recovered from without
intervention external to the reporting product
X 103 1 performance: a recognized measurement of response time has
exceeded a predetermined threshold
X I 04 1 operator intervention required: the intervention of an operator is
required to restore proper operational capability to the resource

Chapter 8. Common Fields

8-19

MS Major Vectors

Basic Alert (X' 91 ') Alert MS Subvector
Byte

Bit

Content
X 105 1- X 109 I
retired
X lOA I notification: a loss of availability to the end user is impending but has
not yet happened
XIOBI -XIOEI
retired
X I OF I delayed: the sender is reporting a previously detected alertable condition that prevented reporting when detected
General cause code: indicates the general classification and cause of the
exception condition:
X I 01 1 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.
Note: Microcode may be classified as IBM Licensed Internal Code.
See "Special Notices" at the beginning of this document for more information.
X 102 1 software: the Alert condition was caused by a software (programming)
failure or malfunction.
X 103 I
retired
X I 04 1_XIOSI
reserved
X 106 1 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 1171
(operator intervention required).
X 107 1 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.
retired
X 108 1- X I 09 I
X I OA I 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 I OB I hardware: the Alert condition was caused by a hardware (machine or
equipment) failure or malfunction.
X 10C I 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 repl~ceable units (CRUs) and are
serviced in the same manner as hardware logic is serviced. X lOB I
(hardware) is used in those cases.
X 100 I protocol above link level: the Alert condition was caused by an SNA
protocol error above the link level.
Note: This code point reports protocol errors that are caused by incorrect programming. for example, failure to include a 88 bit on the first
RU when in 8ETB state on a session that uses bracket protocol.

8-20

SNA Formats

MS Major Vectors

Basic Alert (X' 91 ') Alert MS Subvector
Byte

Bit

Content
XI OE 1

X 1 OF 1
X 110 1

X 111'

X 1121

X 113 1
X 114'
X 115'
X 116 1
X 1171

X 118 1

5-6

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).
undetermined: the cause of the Alert condition cannot be determined.
external facilities change or restriction: the number called is temporarily unobtainable.
Note: This code point is used by X.21 networks.
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).
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.
component offline: the Alert condition was caused by a component
being offline.
component busy: the Alert condition was caused by a component
being busy.
external power failure: the Alert condition was caused by an external
power failure.
thermal problem: the Alert condition was caused by temperature that
is not within recommended specifications.
operator intervention required: the Alert condition was caused
because action is required by an operator.
Note: Unattended devices will always Signal Alert when operator intervention is required. Attended devices will not signal 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 option of sending an Alert.
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 10001'
base processor
service processor
X ' 0002'
reserved
X'0003'
main storage
X ' 0004'
1
disk device
X ' 0005
X'0006 1 printer
X ' 0007 1 card reader and/or punch
X ' 0008 1 tape device

Chapter 8. Common Fields

8-21

MS Major Vectors

Basic Alert (X' 91 ') Alert MS Subvector
Byte

Bit

Content

keyboard
selector pen
magnetic stripe reader
display/printer
display device
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
power supply internal to this product
X'OOOF'
I/O attached controller
X'0010'
communication controller scanner
X'0011'
communication link adapter
X'0012'
reserved
X'0013'
channel adapter
X'0014'
loop adapter
X'0015'
adapter for directly attaching devices
X'0016'
reserved
X'0017'
channel (direct memory access channel)
X'0018'
link: used only when common-carrier equipment cannot be distinX'0019'
guished from customer equipment
X'001A' link: common-carrier equipment
X'001B' link: customer equipment
X'001C' loop: used only when common-carrier equipment cannot be distinguished from customer equipment
X'001D' loop: common-carrier equipment
loop: customer equipment
X'001E'
X.21 link connection external to this product
X'001F'
X.25 network connection external to this product
X'0020'
local X.21 interface (DTE-DCE)
X'0021'
local X.25 interface (DTE-DCE)
X'0022'
modem
local
X'0023'
remote modem
X'0024'
local modem interface (DTE-DCE)
X'0025'
remote modem interface (DTE-DCE)
X'0026'
local modem link monitor
X'0027'
remote
modem link monitor
X'0028'
local modem link monitor interface
X'0029'
X'002A' remote modem link monitor interface
reserved
X '002B' - X '0031'
remote
modem
or modem interface or remote product
X'0032'
transmission medium or remote modem
X'0033'
SDLC data link control component
X'0034'
BSC data link control component
X'0035'
start/stop
data link control component
X'0036'
reserved
X'0037' -X'0043'
cluster controller or device
X'0044'
local link monitor or modem interface
X'0045'
reserved
X'0046'
card reader/punch or display/printer
X'0047'
X'OO09'
X'OOOA'
X'OOOB'
X'OOOC'
X'OOOD'
X'OOOE'

8-22

SNA Formats

MS Major Vectors

Basic Alert (X' 91 ') Alert MS Subvector
Byte

Bit

Content

X 10048 1 controller application program
X ' 0049 1 keyboard or display
X '004A I storage control unit
X 10048 I
storage control unit or storage control unit channel
X '004C I
storage control unit or controller
X 10040 I
control unit (other than storage control unit)
X ' 004E' -X ' 0051 1
reserved
X 100521
maintenance device
X 10053 1 maintenance device interface
X I 0054 1 reserved
X ' 0055 1 control program
X 10056 1 application subsystem on top of control program
X 10057 1 telecommunication access method
X 10058 1 application program (other than application subsystem)
X I 0059 I
communication controller program
reserved
X '005A I - X '005F I
X ' 0060 '
X.25 network interface: OCE to first interface node in X.25 network
X ' 0061 1 disk device with nonremovable media
X ' 0062 1 disk device with removable media
X ' 0063 1 control tailed modem
X ' 0064 1 reserved
X ' 0065 1 remote tailed modem
X ' 0066 1 remote tailed modem interface
X ' 0067 1 sensor I/O unit
X ' 0068 1 magnetic stripe reader/encoder
X ' 0069 1 check (bank) reader
X ' 006A' document feed mechanism
X ' 0068 1 coin feed mechanism
X ' 006C'
envelope depository
X 10060 I timer adapter
encryption/decryption adapter
X '006E I
outboard, user programmable processor
X '006F I
X 10070 1 cable connecting local device to local adapter
X 100711 - X '007F I
reserved
X ' 0080 '
token-ring LAN error
X 100811
Carrier-Sense-Multiple-Access/Collision-Oeletion (CSMA/CO) LAN
error
X I 0082 I - X I OOFE I
reserved
X 'OOFF I
undetermined (the problem cannot be isolated to one of the above
generic component types)

''--

,-'

7-8

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.

9-10

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.

Chapter 8. Common Fields

8-23

MS Major Vectors

Basic Alert (X' 91 ') Alert MS Subvector
Byte

Bit

Content

11-12

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.

13( = p)

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 10 Number that uniquely identifies a particular Alert.

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Generic Alert Data subvector

Key: X ' 92 1

2-3

o
1

3 -15
4

8-24

Flags:
Initiation indicator:
o Alert not directly initiated by an operator action
1
Alert initiated by an operator action
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.
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 1, the held Alert indicator is
also set to 1.
Reserved
Alert type: a code point indicating the severity of the Alert condition:
X 1 01 1
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 102 1 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
XI 03 1 performance: performance below what is considered an acceptable
level
retired

SNA Formats

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content
X 1111
X 1121
X 113 1

5-6

impending problem: a loss of availability to the end user impending
but that has not yet happened
unknown: the severity of the Alert condition not assessable
retired

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:
XI1xxxi
HARDWARE
SOFTWARE
X'2xxx'
COMMUNICATIONS
X ' 3xxx'
PERFORMANCE
X'4xxx'
CONGESTION
X ' 5xxx'
MICROCODE
X ' 6xxx'
OPERATOR
X'7xxx'
SPECIFICATION
X ' 8xxx'
INTERVENTION REQUIRED
X ' 9xxx'
PROBLEM RESOLVED
X'Axxx'
NOTIFICATION
X'Bxxx'
XICXXX I SECURITY
X I Fxxx I
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 100 I represents a more general
description than a non-X 100 I; for this reason, the non-X 100 I codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to X I **00 1 code pOints) if it does not recognize the
more specific code point (e.g., because of different release schedules).
X I 1000 1

EQUIPMENT MALFUNCTION: An internal machine error has
occurred
X 11001 1
X 11002 I

X ' 1003 1
X 11004 1
X 11005 1

X 11010 I
\

'----

X I 1100 1

CONTROL UNIT MALFUNCTION
DEVICE ERROR
Note: This code point is used only if the Alert sender is
unable to determine the nature of the affected device.
CPC HARDWARE FAILURE: A hardware failure has
occurred in a central processor complex (CPC).
TIME OF DAY CLOCK FAILURE: A failure in a mechanism
which keeps time.
BACK-UP RESOURCE FAILURE: A failure on a resource
which has been designated as a back-up. The back-up
capability has been lost.
ADAPTER ERROR: A hardware error has occurred in an
adapter, making it inoperable

INPUT DEVICE ERROR

Chapter 8. Common Fields

8-25

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content
X 1 1101 '

X ' 1200 '

OUTPUT DEVICE ERROR
X 1 1201 '
X 1 1202 '

X ' 1300 '

X ' 1311 '
X ' 1312 '
X ' 1321 1
X ' 1322 1
X ' 1331 1
X ' 1332 1

SNA Formats

LOSS OF EQUIPMENT COOLING
LOSS OF MOSS EQUIPMENT COOLING

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 '

8-26

LOSS OF CHANNEL ADAPTER ELECTRICAL POWER
LOSS OF LINE ADAPTER ELECTRICAL POWER
LOSS OF LlC 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

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 11400 1 (LOSS OF ELECTRICAL POWER)
should be sent instead of this code point.
X 11501 '
X ' 1502 1

X 11600 1

LOCAL CONSOLE ERROR
REMOTE CONSOLE ERROR
Note: "Local" and "remote" are defined with respect to
the system with which the console communicates.
DISK FAILURE: A disk unit is no longer usable
DISK OPERATION ERROR: A disk operation has failed,
but the unit may still be usable
DISKETTE DEVICE FAILURE: A diskette unit is no longer
usable
DISKETTE OPERATION ERROR: A diskette operation has
failed, but the unit may still be usable
TAPE DRIVE FAILURE: A tape drive is no longer usable
TAPE OPERATION ERROR: A tape operation has failed,
but the tape drive may still be usable

LOSS OF ELECTRICAL POWER: A source of electrical power,
internal or external, has been lost
X ' 1401 '
X ' 1402 1
X ' 1403 '
X ' 1404 1
X ' 1410 '
X ' 1411 1

X ' 1500 '

PRINTER ERROR
PRINTER CASSETTE ERROR

INPUT/OUTPUT DEVICE ERROR
X'1301 '
X 1 1302 '

X 1 1400 '

MICR READER/SORTER ERROR: An error has been
detected in a magnetic ink character recognition
reader/sorter

STORAGE SUBSYSTEM FAILURE: A failure in a subsystem that supports locally-attached storage devices,
such as hard disk (DASD), diskette, and tape

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content

X'1602'

X'1603'

X'160B'

X'1611'
X'1612'
X'1613'
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 '2001'

X'2100'

WORKSTATION SUBSYSTEM FAILURE: A failure in a subsystem that supports workstations directly attached to a
node, i.e., workstations not attached via telecommunications links
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
SERVICE SUBSYSTEM FAI LURE: A failure in a subsystem
that performs IPL functions, maintenance functions,
machine initialization or recovery, and provides problem
determination capabilities.
IMPENDING STORAGE SUBSYSTEM FAILURE
IMPENDING WORKSTATION SUBSYSTEM FAILURE
IMPENDING COMMUNICATIONS SUBSYST FAILURE

CPC ENTERED HARD WAIT: A failure has occurred that
resulted in all central processing units (CPUs) of a central
processing complex (CPC) entering into a wait state with
interrupts disabled.

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 '6100' (MICROCODE PROGRAM
ERROR).
X '2101'

PROGRAM PROCEDURE IS INCORRECT: A set of
instructions that 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'
X '3111'

X '3200'

XID PROTOCOL ERROR: A protocol error related to XID
exchange has been detected
INVALID XID RECEIVED: An XID has been received that
contains either a format error or a value unacceptable to
the receiver

LAN ERROR: An error has been detected on a local-area network

Chapter B. Common Fields

8-27

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content

X'3203'
X'3204'
X'3205'
X'3210'
X'3211'
X'3212'

X'3213'

X'3214'
X'3215'

X'3216'

X'3217'

X'3218'
X'3219'
X'3220'
X'3221'

X'3230'

8-28

SNA Formats

LOOP ERROR: An error has been detected on a communication loop
LOOP OPEN
LOOP ADAPTER INOPERATIVE
INITIALIZATION FAILURE: A LAN adapter has detected a
problem while being initialized
OPEN FAILURE: A LAN adapter has detected a problem
during the insertion process; the insertion process did not
complete
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.
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.
REMOVE ADAPTER COMMAND RECEIVED: The reporting
station received a Remove Adapter command from a
LAN "manager and, as a result, left the LAN.
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.
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.
OPTICAL FIBER CONVERTERS HAVE WRAPPED: An
optical fiber subsystem has wrapped the primary path
onto the secondary path due to an error condition on the
primary path.
BACK.. UP PATH INOPERATIVE: The back-up path of a
subsystem has failed leaving only the main path operational.
MAIN PATH WRAPPED TO BACK-UP PATH: The main
path has failed and the back-up path is being used to continue operation.
CSMA/CD BUS INOPERATIVE
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.
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.

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content

X ' 3231

X ' 3240 '
X 13300 1

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.
X'3301 1

X ' 3302 1
X'3303'
X ' 3304 1
X ' 3305 1
X'3310 '
X ' 3311 1
X ' 3312 1
X ' 3313 1
X ' 3320 '
X ' 3330 '

X 13400 1

MONITORED STATION LEFT LAN: A monitored station is
one that an operator at the LAN Manager has designated
as a critical resource. The station is monitored for its disappearance from the LAN.
TOKEN-BUS COMMUNICATIONS LOST

REMOTE SUPPORT FACILITY LINK ERROR: An error has
occurred on a communication link with the IBM Remote
Support Facility
UNABLE TO COMMUNICATE WITH DEVICE
UNABLE TO COMMUNICATE WITH PRINTER
UNABLE TO COMMUNICATE WITH DISPLAY
UNABLE TO COMMUNICATE WITH REMOTE NODE
X.21 ERROR: An error has been detected on a communication link operating according to the X.21 protocols.
X.21 ERROR-SNA SECONDARY: An error has prevented
an SNA secondary link station from establishing an X.21
connection
X.21 ERROR-SNA PRIMARY: An error has prevented an
SNA primary link station from establishing an X.21 connection
X.21 CONNECTION CLEARED
X.25 ERROR: An error has been detected on a communication link operating according to the X.25 protocols
MANAGEMENT SERVER REPORTING LINK ERROR: A
LAN manager has detected an error on one of its
reporting links with a LAN management server

ISDN ERROR: An error has occurred on an Integrated Services
Digital Network (ISDN) connection
X 13401 1
X ' 3402 1

D-CHANNEL ISDN ERROR
B-CHANNEL ISDN ERROR

X'3500 '

LOCAL CONNECTION ERROR: An error has occurred on a local
channel connection

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, or the AT Command
Set) and DCE provided information about the link.
X 13601'
X 13602 1

NO LPDA RESPONSE RECEIVED
BAD FCS IN LPDA RESPONSE
Chapter 8. Common Fields

8-29

MS Major Vectors

Generic Alert Data (X'92') Alert MS Subvector
Byte

Bit

Content
X'3603'
X'3604'
X'3605'
X'3606'
X'3607'
X'3608'
X'3609'
X'360A'
X'360B'
X'360C'
X'360D'
X'360E'
X'360F'
X'3610'
X'3611'
X'3612'
X'3613'
X'3614'
X'3615'
X'3616'
X'3617'
X'3618'
X'3619'
X'361A'
X'361B'
X'361C'
X'361D'
X'361E'
X'361F'
X'4000'

PERFORMANCE DEGRADED: Service or response time exceeds
what is considered an acceptable level
X'4001'

X'4003'
X'4010'

X '4011'
X'4021'
X'4022'
X'4023'

8-30

SNA Formats

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
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 LOOP BACK DETECTED BY LOCAL DSU/CSU
DDS LOOP BACK DETECTED BY REMOTE DSU/CSU

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.
EXCESSIVE CONTROL UNIT ERRORS
ERROR TO TRAFFIC RATIO EXCEEDED: A computed ratio
of errors to total traffic has exceeded a specified
threshold
THRESHOLD HAS BEEN EXCEEDED
EXCESSIVE STORAGE SUBSYSTEM ERRORS
EXCESSIVE WORKSTATION SUBSYSTEM ERRORS
EXCESSIVE COMMUNICATIONS SUBSYST ERRORS

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content
X ' 5000 '

CONGESTION: A system or network component has either reached
its capacity or is approaching it
X ' 5001 1
X ' 5002 1
X 15003 I

X ' 5004 1
X 15005 I

X ' 5010 '
X ' 5011

X ' 5012 1
X 15013 1

X ' 5020 '

NETWORK CONGESTION: There is excessive traffic in the
network
RESOURCE NEARING CAPACITY: A resource is
approaching its capacity; it is still usable, but it threatens
to become unusable unless corrective action is taken
CAPACITY EXCEEDED: A request has been received by a
component that, if granted, would require more resources
than the component has available to it
OUT OF RESOURCES: A component has no more
resources available; it is no longer able to function
WORKSTATION LIMIT EXCEEDED: More workstations
than the workstation subsystem supports being powered
on have attempted to power on simultaneously
COMMUNICATIONS UNDERRUN: A link station element is
unable to write data to an adapter rapidly enough
COMMUNICATIONS OVERRUN: A MAC service user is
unable to read data from an adapter rapidly enough
RECEIVE QUEUE OVERRUN: A receive queue in a node is
unable to receive data from a link station in the node
rapidly enough
SLOWDOWN: A device has exhausted its supply of available buffers and has stopped accepting inbound data until
it can handle all outbound requests
FILE NEEDS REORGANIZATION A file is approaching its
capacity, and will soon be unusable unless it is reorganized

X 16000 I

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 16100 I

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 ' 2100 ' (SOFTWARE PROGRAM ERROR).

X ' 7000 '

OPERATOR PROCEDURAL ERROR: An operator has attempted to
initiate an incorrect procedure, or has initiated a procedure incorrectly
X 170011

X 18000 I

RESOURCES NOT ACTIVE: An operator has deactivated,
or failed to activate, resources required for a requested
operation

CONFIGURATION OR CUSTOMIZATION ERROR: A system or device
generation or customization parameter has been specified incorrectly, or is inconsistent with the actual configuration

Chapter 8. Common Fields

8-31

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content
X ' 8001 1

X 19000 I

OPERATOR INTERVENTION REQUIRED: A condition has occurred
indicating that operator intervention is required, and an operator has
not responded
Note: The X '90xx I 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 1
X ' 9002 1
X ' 9003 1
X ' 9004 1
X ' 9005 1
X 19010 I

X 190111

X ' 9030 '
X 190311

X 19100 1

X ' 910A I

SNA Formats

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.
LOW ON ENVELOPES

STOCK EXHAUSTED: The stock of some required material (e.g.,
paper, ink, coins) has been exhausted
X ' 9201 1
X ' 9202 1
X 19203 1
X 19204 1
X ' 9205 1
X ' 9206 1

8-32

PRINTER RIBBON JAM
PAPER JAM
BILUDOCUMENT 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
PRINTER NOT READY: A printer has indicated that it is
not ready for use, due to an unspecified interventionrequired condition
OUT OF FOCUS
SERVICE DOOR OPENED
Note: Security and/or safety considerations may preclude
normal operation until the door is closed.

STOCK LOW: The stock of some required material (e.g., paper, ink,
coins) is low, but is not yet exhausted
X 19101 1
X 19102 I
X 19103 1
X 19104 1
X ' 9105 1
X ' 9106 1
X ' 9107'
X ' 910B'
X 19109 1

X ' 9200 '

CUSTOMIZATION IMAGE WARNING: A customization
image parameter is incorrect and has been replaced by a
valid value.

OUT
OUT
OUT
OUT
OUT
OUT

OF
OF
OF
OF
OF
OF

INK
PAPER
BILLS/DOCUMENTS
COINS
FILM/VIDEOTAPE
TONER

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content
X'9207'
X'9208'
X ' 920A'
X 19300 1

DEPOSITORY FULL: A depository has become full, and thus cannot
receive any more deposits
X I 9301 1

X'AOOO'

X'B002 1
XI B003 1
X' B004 1

X'BOOS'
X'B006 1
XI B007 1
XI B008 ,
X'B009 1
X I COOO I

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

OPERATOR NOTIFICATION: Problem-related information is being
conveyed to a network operator
Note: An X I Bxxx I code point is used only if no more-specific one is
available.
X' B001'

DEPOSITORY APPROACHING CAPACITY: A depository is
nearing its capacity; if it is not emptied shortly, it will
become completely filled

PROBLEM RESOLVED: A problem has been resolved
Note: The problem may have been reported earlier by an Alert.
X'A001 1

X I BOOO I

OUT OF FUSER OIL
OUT OF STAPLES
OUT OF ENVELOPES

MAINTENANCE PROCEDURE: A resource has been taken
off-line for maintenance
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.
OPERATOR TOOK PRINTER OFF-LINE
LAN BRIDGE TAKEN OFF-LINE
RESOURCES REQUIRE ACTIVATION: Some resources are
not active. The operator must activate these resources to
make the system fully operational.
SERVICE SUBSYSTEM TAKEN OFF-LINE
LINE ADAPTER DISCONNECTED
TOKEN RING ADAPTER DISCONNECTED
HIGH SPEED LINE ADAPTER DISCONNECTED
CHANNEL ADAPTER MAINTENANCE PROCEDURE: A
channel adapter has been taken off-line for maintenance.

SECURITY EVENT: An event indicative of a possible security exposure has been detected
XI C001'
X'C002'
X I COOS'

INVALID REPORTING LINK PASSWORD
UNAUTHORIZED LAN INSERTION ATTEMPTED
UNKNOWN OSI MANAGEMENT SERVICES REQUEST: An
OSI system is attempting to solicit management services
from another system without being properly identified.

(
' ........ _- .

Chapter 8. Common Fields

8-33

MS Major Vectors

Generic Alert Data (X' 92') Alert MS Subvector
Byte

Bit

Content

X'C006 1
X'EOOO' -X'EFFF'

X I FEOO I

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.

UNDETERMINED ERROR: An error condition has occurred that
cannot be related to a more specific error category
X'FE01

7-10(=p)

INVALID PASSWORD

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.

Alert 10 number: A 4-byte hexadecimal value computed as follows:
Stage 1: Assemble (in order) the following input from the Alert major vector:
•
•
•
•
•
•
•
•
•

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

Stage 2: Apply to this input the 32-bit CRC algorithm:

x 32 /(x)

+ xkL(x)

G(x)

R(x)
= Q(x)

G(x)

where:
31

L(x)

LX;

G(x)

Di for i

;=0

= 32, 26, 23, 22, 16, 12, 11, 10, 8, 7, 5, 4, 2, 1,0

I(x)

The polynomial represented by the input to the CRC algorithm (with the
convention that the first bit of the input represents the coefficient of this
polynomial's highest-order term)

number of bits in the input polynomial I(x)

The Alert 10 number is the complement of the remainder polynomial R(x)
(sometimes represented as Alert ID = R(x»). The reader should remember that
all arithmetic is modulo 2, and that the degree of the remainder polynomial,
R(x), is less than 32.

8-34

SNA Formats

MS Major Vectors

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.

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Probable Causes subvector

Key: (X I 93 I)

2-p

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 100 I represents a more general
description than a non-XIOO'; for this reason, the non-XIOOI codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to X 1* *00 1 code points) if it does not recognize the
more specific code point (e.g., because of different release schedules).
X 10000 I

PROCESSOR: The equipment used to interpret and process programmed instructions. These instructions may be programmed in
either software or microcode
X I 0001 1
X ' 0002 1
X ' 0003 1
X ' 0004 1
X ' 0005 1
X I 0010 1
X 10011 1

X I 0030 I
X 10031 1

MOSS (Maintenance and Operation Subsystem): A
service processor for a communication controller
VECTOR PROCESSOR: The vector processing element
associated with a central processing unit (CPU)
PROCESSOR SWITCH: A component within a hardware
product used to switch buses and the resources attached
to them among processors
CONTROL PANEL
SYSTEM I/O BUS
LAN MANAGER: A network component responsible for
managing a local area network
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.
SYSTEM MICROCODE: The specific microcode was not
identified.
SYSTEM STORAGE MICROCODE
Note: See also code point X I 0421 1 (STORAGE CONTROLLER MICROCODE)

Chapter 8. Common Fields

8-35

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X ' 0032 1
X ' 0033 1
X ' 0034 1

X ' 0040 '
X 10100 1

STORAGE: The random access memory (RAM) or read only memory
(ROM) accessible by a processor and by peripheral devices
X 10101 1

X 10102 1

X ' 0103 1
X 10104 1
X 1010S 1
X ' 0200 '

X' 0202 1
X' 0203 1
X' 0204 1
X' 020S '
X' 0210 '
X' 0211 1
X ' 0220 '
X' 0240 '

SNA Formats

COOLING OR HEATING SUBSYSTEM: The SUbsystems within a hardware product responsible for maintaining a temperature at which the
product can operate

X' 0301 1
X' 0302 1
X' 0310 '
X' 0311 1

8-36

MAIN STORAGE: Storage from which instructions and
other data can be loaded directly into registers for subsequent execution or processing
AUXILIARY STORAGE: Storage that can not be directly
addressed by a processor, such as external or secondary
storage
NON-VOLATILE STORAGE
EXPANDED STORAGE: A specific type of auxiliary storage
used for data and program paging
CRITICAL SYSTEM STORAGE: A specifiC portion of main
storage used only by the machine

POWER SUBSYSTEM: The subsystem within a hardware product that
provides electrical power to the different components within the
product that require it

X10201 1

X ' 0300 '

SYSTEM DISPLAY MICROCODE
Note: See also code point X ' 0422 1 (WORKSTATION CONTROLLER MICROCODE)
SYSTEM COMMUNICATION MICROCODE
Note: See also code point X ' 0423 1 (COMM SUBSYSTEM
CONTROLLER MICROCODE)
SYSTEM PRINTER MICROCODE
Note: See also code point X ' 0422 1 (WORKSTATION CONTROLLER MICROCODE)
INITIAL PROGRAM LOAD

COOLING FAN
AIR FILTER
AIR FLOW DETECTOR
THERMAL DETECTOR

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content

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'

X'0402'
X '0403'

X '0421'
X'0422'
X '0423'
X '0441'

X'0442'

X '0443'
',~

X'0500'

STORAGE CONTROLLER
Note: This code point is contrasted with X '3131', DASD
CONTROL UNIT and X'3132', 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.
WORKSTATION CONTROLLER
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 ~ypically a component within a larger node that provides for the node's communication with nodes remote
from it.
STORAGE CONTROLLER MICROCODE
WORKSTATION CONTROLLER MICROCODE
COMM SUBSYSTEM CONTROLLER MICROCODE
STORAGE CONTROLLER INTERFACE: The interface
between a storage controller and the main processor in
its node
WORKSTATION CONTROLLER INTERFACE: The interface
between a workstation controller and the main processor
in its node
COMM SUBSYSTEM CONTROLLER INTERFACE: The
interface between a communications subsystem controller
and the main processor in its node

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'
X'0502'
X'0503'
X'0504'

X'0505'
X'0506'

STORAGE SUBSYSTEM
WORKSTATION SUBSYSTEM
COMMUNICATIONS SUBSYSTEM
LOGICAL X.25 DCE: A communications subsystem which
is configured as a logical DCE, as opposed to a network
DCE.
X.25 DTE: A communications sUbsystem which is configured as a DTE.
CHANNEL SUBSYSTEM: A sUbsystem that processes
channel operations, routes I/O interruptions and moves
data between main storage and an I/O interface
Chapter 8. Common Fields

8-37

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X 11000 1

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 display the English text
(or its national language equivalent) documented with the code
points, or it may display the software product common name from
the first software Product Identifier (X 1111) subvector within the indicated resource Product Set ID.

X11001 1

XI 1010 1
X11011 1

X11012 1
X11020 1
XI 1021 1
XI 1022 1
X11023 1
X11024 1
X I 1030 1
X11031 1

X I 1040 1

8-38

SNA Formats

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
HOST PROGRAM: A program running in a host processor
that is a primary or controlling program in a system
PRINTER SERVER PROGRAM: A program running in a
printer server that controls a printer
Note: See also Probable Cause X10011 1 (PRINTER
SERVER).
SOFTWARE DEVICE DRIVER: A program designed to
control a device.
CONTROL PROGRAM: A computer program designed to
schedule and supervise the execution of programs in a
computer system
COMMUNICATION CONTROLLER CONTROL PROGRAM:
A software program designed to schedule and supervise
the execution of programs in a communication controller
COMMUNICATIONS PROGRAM: A software program
designed to provide direct assistance to a node in communicating with other nodes
COMMUNICATIONS PROGRAM IN REMOTE NODE
COMMUNICATION ACCESS METHOD
LAN MANAGER PROGRAM: The software program in a
LAN manager
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).
I/O ACCESS METHOD

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X' 2000 I

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 I 2001 1

X I 2002 1

X 12003 I

X I 2004 1

X 12005 I

X 12006 1

X 12007 1
X 12008 I

X 12009 1

X I 200A I
X 1200B I
X I 2010 I

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
BINARY SYNCHRONOUS COMMUNICATIONS: Synchronous transmission of binary-coded data between stations,
using a standard set of control characters and control
character sequences
SNA COMMUNICATIONS: Communication according to
the Systems Network Architecture formats, protocols, and
operational sequences
SDLC COMMUNICATIONS: Synchronous, codetransparent, serial-by-bit information transfer over a link
connection
X.21 NETWORK: A network implementing the X.21 protocols. These protocols define an interface between Data
Terminal Equipment (DTE) and Data Circuit-terminating
Equipment (DeE) for synchronous operation on circuit
switched public data networks
X.25 NETWORK: A packet switching data network implemented according to the recommendation developed by
the CCITT which provides a standard interface for the connection of processing eqUipment
LAN LLC COMMUNICATIONS: Error-free, in-sequence
information transfer over a LAN
X.25 COMMUNICATIONS: Communications according to
CCITT recommendation X.25 for a packet switching data
network.
Note: Use code point X 12006 I (X.25 NETWORK) if the
problem is known to be in X.25 network.
X.21 COMMUNICATIONS: Communications according to
CCITT recommendation X.21 for a circuit switching data
network.
Note: Use code point X 12005 I (X.21 NETWORK) if the
problem is known to be in X.21 network.
ISDN NETWORK: A network implementing the Integrated
Services Digital Network protocols
OSI COMMUNICATIONS: Communications according to
OSI and CCITT standards
DDS NETWORK: A network implementing the Digital Data
Service, e.g., DATAPHONE l Digital Service (DDS).
1 DATAPHONE is the Registered Service Mark of AT&T
Company.

Chapter 8. Common Fields

8-39

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content

X'2021'

X'2022'

X'2031'
X'2033'
X'2034'
X'2035'

X'2036'

X'2037'
X'20A7'

X'20A8'

X'2040'
X'2041'
X'2050'
X'2051'
X'2052'
X'2080'

X'2100'

COMMUNICATIONS/REMOTE NODE: Either a communications facility
denoted by an X '20xx' code point or a remote node denoted by an
X'22xx' code point
Note: This code point is used only when a more specific probable
cause cannot be determined.
X'2101'
X'2102'

8-40

SNA Formats

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
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
LINE: The telephone line or transmission link connecting
two or more components in the network
LINE/REMOTE MODEM: A line or the modem on it remote
from the Alert sender
LINE/REMOTE LDM: A line or the limited distance modem
on it remote from the Alert sender
LINE/REMOTE DIGITAL DATA DEVICE: A line or the
digital data device (DDD) on it remote from the Alert
sender
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 DCE is a modem or a
DDD; see code points X'2033' and X'2035'.
DCE-DSE CONNECTION: The telephone line connecting
the calling DCE to its local DSE
OUTBOUND LINE: The equipment that connects the
transmit circuits of the local DCE (Le., the DCE local to the
node sending error notification) to the receive circuits of
the remote DCE.
INBOUND LINE: The equipment that connects the receive
circuits of the local DCE (Le., the DCE local to the node
sending the error notification) to the transmit circuits of
the remote DCE.
INTER-EXCHANGE NETWORK: A network providing services between two local exchange areas
PRIVATE NETWORK REACHED: The private network containing the called DTE
PACKET LAYER CONTROL
LINK ACCESS PROTOCOL BALANCED
LOGICAL LINK CONTROL
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.

START/STOP COMMUNICATIONS/REMOTE NODE
BSC COMMUNICATIONS/REMOTE NODE

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content

X 12104 1
X 12105 I
X ' 2106 1
X 12107 1
X '210A I
X'2130 '
X 12200 I

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 12201 1

X 12204 1

X 12300 I

CALLED DTE: On a switched telephone connection, the
data terminal equipment (DTE) to which the telephone call
to establish the connection was placed
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

CONNECTION NOT ESTABLISHED: A telephone connection required
for the requested operation has not been established
X 12301 1
X ' 2302 1

X 12303 I

X ' 2304 1
X ' 2305 1
X '2306 '
X ' 2307 1
X 12308 I
X 12309 I

X '230A I

X ' 230B'
X 12600 I

SDLC COMMUNICATIONS/REMOTE NODE
X.21 COMMUNICATIONS/CALLED DTE
X.25 COMMUNICATIONS/REMOTE NODE
LAN LLC COMMUNICATIONS/REMOTE NODE
ISDN COMMUNICATIONS/REMOTE NODE
LINE/REMOTE NODE

CALLED NUMBER BUSY: The telephone number dialed
for a teleprocessing connection was busy
CALLED NUMBER DID NOT ANSWER: The telephone
number dialed for a teleprocessing connection did not
answer
CALLED NUMBER OUT OF ORDER: The telephone
number dialed for a teleprocessing connection is inoperative
INCORRECT NUMBER CALLED: The telephone number
dialed for a teleprocessing connection was incorrect
MANUAL DIAL REQUIRED: The operator must establish a
manual dial connection to a remote device before normal
operation can continue
CHANGED NUMBER: The called DTE has recently been
assigned a new number (unique X.21 status provides this
information)
INVALID REQUEST: In the course of attempting to set up
a telephone connection, the caller has made an invalid
request
ACCESS BARRED: The calling DTE is not allowed to
connect to the called DTE
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.
CALL COLLISION: An outgoing call was not completed
because it collided with an incoming call on the same
link.
LINK SET UP FAILURE

ELECTRICAL INTERFERENCE: An electrical disturbance in a communication system that interferes with or prevents reception of a signal
or of information

Chapter 8. Common Fields

8-41

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X' 3000 1

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 134111 (CHANNEL
INTERFACE CABLE) is used instead.

X 13100 1

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 1111) subvector within the indicated resource Product Set
10.
X '310F 1

X ' 3110'

X ' 3111 1

X ' 3112 1
X ' 3113 1
X ' 3114'
X ' 3115 1
X ' 3121 1

X ' 3122 1
X'3.123 1

8-42

SNA Formats

COMMUNICATION CONTROLLER RECOVERY: A process
which recovers resources from a back-up processor in a
communication controller.
Note~ This code point is used to notify the network operator about a maintenance procedure that was invoked
locally or initiated automatically which results in the availability of additional resources.
COMMUNICATION CONTROLLER BACK-UP: A process
which switches resources from one processor to a
back-up processor in a communication controller.
Note: This code point is used to notify the network operator about a maintenance procedure that was invoked
locally or initiated automatically which results in the availability of additional resources.
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.
SENDING NODE: The node detecting the error and
sending the error notification for it.
SENDING NODE AND MODEMS CONFIGURATION
SENDING NODE AND DSU/CSU'S CONFIGURATION
SENDING NODE/TAILED-CIRCUIT CABLE: The error notification sender configuration is incorrect or the tailedcircuit attachment cable is not connected or present
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.
FINANCE CONTROLLER: A terminal control unit specifically designed for the banking industry
STORE CONTROLLER: A terminal control unit specifically
designed for the retail industry

MS Major Vectors

Prcb~blc c~uscs

Byte

Bit

(X' 93') l\lert MS Subvector
Content
X 13131 1

X 13132 1
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.
X I 3220 1
X 132211
X 132221
X I 3223 1
X I 3224 1
X'32D1'

XI 32D2 1

X l 32D3 1

X 13300 1

DASD CONTROL UNIT: A device that controls the transfer
of data to and from a direct access storage device such
as disk or drum
TAPE CONTROL UNIT: A device that controls the transfer
of data to and from tape drives

LOCAL TOKEN-RING ADAPTER INTERFACE: The programming interface for the local token-ring adapter
CSMAlCD ADAPTER INTERFACE: The programming interface for the local CSMA/CD adapter
ISDN ADAPTER INTERFACE: The programming interface
for the local ISDN adapter
TOKEN-RING ADAPTER INTERFACE: The programming
interface for a token-ring adapter
LOCAL AUTO-CALL UNIT INTERFACE
LOCAL DCE COMMUNICATIONS INTERFACE: The communications interface between the Alert sender and the
local Data Circuit-Terminating Equipment (DCE)
REMOTE DCE COMMUNICATIONS INTERFACE: The communications interface between the Data CircuitTerminating Equipment (DCE) remote from the Alert
sender and the remote node
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

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 133011
X ' 3302 1
X I 3309 1

X ' 330F'

CHANNEL ADAPTER
COMMUNICATIONS ADAPTER
LINE ADAPTER
Note: A line adapter in a communication controller is
often referred to as a scanner.
HPTSS ADAPTER: A high-speed processor transmission
subsystem adapter in a communication controller

Chapter 8. Common Fields

8-43

MS Major Vectors

Probable Causes (X I 93 ') Alert MS Subvector
Byte

Bit

Content

X ' 3310 '

X ' 3311 1

X ' 3320 '
X ' 3321 1
X ' 3322 1
X ' 3323 1
X ' 3325 1
X ' 3326 1
X ' 3330 '
X ' 3331 1
X ' 3380 '

X ' 3381 1
X ' 33C1 1
X ' 33C2 1
X ' 33C3 1
X 13400 1

CABLE: A cable or its connectors used to electrically connect
devices together
X ' 3401 1
X 13403 1

8-44

SNA Formats

LOCAL ISDN ADAPTER: An adapter that attaches the
Alert sender to an ISDN network
Note: See also code point X 13532 1 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.
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 paint X 13533 1 REMOTE ISDN TERMINAL ADAPTER.
LOCAL TOKEN-RING ADAPTER: An adapter that attaches
the Alert sender to a taken-ring LAN
REMOTE TOKEN-RING ADAPTER: An adapter that
attaches a node other than the Alert sender to a tokenring node
LOCAL CSMA/CD ADAPTER: An adapter that attaches
the Alert sender to a CSMA/CD LAN
REMOTE CSMA/CD ADAPTER: An adapter that attaches a
node other than the Alert sender to a CSMAlCD LAN
CSMA/CD ADAPTER
TOKEN BUS ADAPTER
ADAPTER HARDWARE: The hardware comprising an
adapter
ADAPTER MICROCODE: The microcode executing in an
adapter
ROTARY GROUP: A number of ports on a device that are
all reached via the same telephone number; a rotary
group is sometimes referred to as MLSA (multiple lines at
same address)
X.21 ROTARY GROU P
LINE ADAPTER HARDWARE
LINE ADAPTER MICROCODE
LINE INTERFACE COUPLER (LlC)

LOCAL DCE INTERFACE CABLE: The cable, or its connectors, between the Alert sender and the local Data CircuitTerminating Equipment (DCE)
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.)

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X ' 3404 1

X ' 3411 1
X ' 3426 1
X ' 3436 1
X ' 3441 1
X ' 3451 1

X ' 3452 1
X ' 3460 '
X ' 3461 1
X ' 3462 1

X ' 3463 1
X ' 3464 1

.~-

X ' 3500 '

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.
CHANNEL INTERFACE CABLE: The cable or cables, or
their connectors, between a channel and a locally
attached device
CSMAlCD 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.
LOCAL CSMA/CD ADAPTER CABLE: The cable attaching
the Alert sender to the CSMA/CD bus
LOOP CABLE: A cable connecting the nodes attached to
a communication loop
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.
STORAGE DEVICE CABLE: A cable directly connecting a
local storage device to its adapter/controller
INTERNAL CABLE
CABLE TERMINATOR
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.
REMOTE DCE LOOP: The DCE loop remote from the error
notification sender.
TELECOMMUNICATION CABLE CONNECTION: The connection of the telecommunication cable with the local DCE
or with the telephone connecting block provided by the
telecommunications facility.

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 I) is sent instead of this code point.
Note: LAN components are not reported with X '35xx I code points;
see the X 13700 I code point for a discussion of how they are
reported.
X ' 3502 1

TERMINAL MULTIPLEXER: The equipment used to
connect multiple devices to a single cable

Chapter 8. Common Fields

8-45

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X 13503 1

X ' 3504 1

X ' 3505 1

X ' 3506 1
X ' 3507 1
X ' 3508 1
X'3510'

X ' 3530'
X ' 3531 1

X ' 3532 1

8-46

SNA Formats

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).
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
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
LOCAL DIGITAL DATA DEVICE: The digital data device
(DDD) connected to the Alert sender
REMOTE DIGITAL DATA DEVICE: The digital data device
(DDD) remote from the Alert sender
LOCAL AUTO-CALL UNIT
CALLED DCE
Note: See also code pOint X ' 3542 1 REMOTE DCE.
X ' 3510 ' is used when reporting a problem encountered
during an attempt to establish a switched connection.
X 13542' is used when the problem is not related to the
establishment of a switched connection.
ISDN NETWORK COMPONENT
ISDN NETWORK TERMINATION (NT1): 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
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.

MS Major Vectors

Prob::blo C::U::c:; (X'!l3') Alert MS Subvectoi
Byte

Bit

Content

X ' 3533 1

X ' 3534 1

X 13535 1

X 13536 1

X ' 3541 1

X ' 3542 1

X ' 3600 '

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 133111 REMOTE ISDN
ADAPTER.
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.
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.
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.
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 13506 1 and X 136011.
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 1 and X ' 3603 1. See also
code point X ' 3510 ' CALLED DCE.

MODEM: A device or functional unit that modulates and demodulates signals transmitted over data communication facilities
X 136011
X 136021

X 13603 1

LOCAL MODEM: On a particular link segment, the
modem nearer to the Alert sender
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
REMOTE MODEM: On a particular link segment, the
modem farther from the Alert sender

Chapter 8. Common Fields

8-47

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X ' 3604 1

X ' 3605 1

X ' 3611 1
X ' 3613 1
X ' 3621 1

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 13700 I, with
the exception of the LAN adapters, which fall under ADAPTER
(X 13300 I), and the CSMA/CD LAN cables, which fall under CABLE
(X 13400 1).
X ' 3701 1
X ' 3702 1
X ' 3703 1

X ' 3704 1
X ' 3705 1
X ' 3706 1
X ' 3707 1
X ' 370A'
X ' 370B'

8-48

SNA Formats

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
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.
LOCAL LDM: The limited distance modem nearer to the
Alert sender
REMOTE LDM: The limited distance modem farther from
the Alert sender
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.

TOKEN-RING LAN COMPONENT
TOKEN-RING LOBE: An adapter, the lobe cables connecting it to its access unit, and a portion of the access
unit
TOKEN-RING FAULT DOMAIN: An adapter, its nearest
active upstream neighbor, and the token-ring media
between them; the token-ring media consist of the lobe
cables, portions of one or more access units, and possibly
a portion of the LAN cable
TOKEN-RING DUPLICATE STATION ADDRESS
TOKEN-RING REMOVE COMMAND RECEIVED: An adapter
received a Remove Ring Station MAC frame
OPTICAL FIBER CONVERTER: A device that converts
electrical signals into optical signals and vice-versa
TOKEN-RING LAN CABLES
TOKEN BUS LAN
TOKEN BUS DU PLICATE MAC ADDRESS: MAC sublayer
fault indicated when the MAC sublayer has detected that
there is another MAC entity on the network which has the
same MAC address as the current value of the variable in
this station.

MS Major Vectors

Prob::blo
Byte

C::us~s

Bit

(X' 03') Alert MS Slibvactoi"

Content
X ' 3714 1
X ' 3721 1
X ' 3724 1
X 13725 I
X 13740 I

X ' 4000 '

PERFORMANCE DEGRADED
X ' 4001 1
X ' 4002 1
X ' 4003 1

X 15000 I

REMOTE TOKEN-RING LOBE: A lobe attaching a node
other than the Alert sender to the token-ring
CSMA/CD LAN COMPONENT
CSMA/CD DUPLICATE STATION ADDRESS
CSMA/CD REMOVE COMMAND RECEIVED
LAN BRIDGE: A network component that interconnects. at
the medium access sublayer (of the DLC layer. two tokenrings. 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

STORAGE SUBSYSTEM OVERLOADED
WORK STATION SUBSYSTEM OVERLOADED
COMMUNICATIONS SUBSYSTEM OVERLOADED

MEDIA: A tape. disk. diskette. or paper (or other data medium) that
is required to read data from or write data on
X 150011
X 150021

X 15003 I

X I 5004 1
X ' 5005 1

DASD MEDIA: The media used in a direct access storage
device; it may be either removable or non-removable
DISKETTE: A thin. flexible magnetic disk in a semi-rigid
protective jacket. in which the disk is permanently
enclosed; also termed a floppy diskette
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
OPTICAL DISK: A DASD medium on which data is
encoded optically
ID RECORDING SURFACE: The recording media on an
Identification Card Reader (ICR) card is defective. missing
or the reading device has failed.

X 16000 1

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 directlyattached 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 ' 6100 '

INPUT DEVICE: A device th,at is used to enter data into a system
X 16110 I

X 161111

X 161121
X 16113 1

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
KEYPAD: A specialized keyboard with an arrangement of
a limited number of alphanumeric. special character
and/or function keys
SELECTOR PEN: A light sensitive pen used in display
operations
MICR READER/SORTER: A magnetic ink character recognition reader/sorter
Chapter 8. Common Fields

8-49

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X 161141

X ' 6115 1

X ' 6200 '

OUTPUT DEVICE: A device that receives data from a system
X ' 6210 '

X ' 6211 1
X ' 6212 1
X ' 6213 1

X ' 6220 '
X ' 6300 '

X ' 6302'
X ' 6310 '
X ' 6311 1
X ' 6312 1
X ' 6313 1

X ' 6314 1
X ' 6315 1

SNA Formats

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 16213 1 PLOTTER.
COPIER: An output device that produces one or more
copies of an original without affecting the original
CAMERA: An output device that combines electronic data
with a visual image on a single visual medium
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 16210 1 PRINTER.
PRINTER CASSETTE: A removable container for inputting
paper to a printer

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 ' 6301 1

8-50

MAGNETIC STRI PE READER: A device that reads data
from, and in some cases writes data to, a card containing
a magnetic stripe
ID CARD READER: An Identification Card Reader (ICR) is
a device which can read data from or write data to a magnetic stripe or an electronic chip on a consumer's identification card.

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
DISPLAY: A workstation that requires a host connection
in order to function; typically a display includes both a
monitor and a keyboard
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
DISKETTE DEVICE: A direct access storage device that
uses a diskette as the storage medium
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
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
TAPE DRIVE: An input/output device used for moving
magnetic tape and controlling its movement
CONSOLE: A terminal used for communication between
an operator and a processor

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content
X' 6400 I

DEPOSITORY: A device that receives items into a system
X 16401 1

X 16402 1

X 16403 1

X 16500 1

DISPENSER: A device that dispenses items to a user of a system
X ' 6501 1
X ' 6502 1
X I 6503 1
X ' 6504 1
X 16505 1

X 16600 1

X I 6630 1

PERSONAL BANKING MACHINE: A self-service terminal
for financial transactions
TELLER ASSIST UNIT: A terminal that assists a financial
teller in transactions
Note: This device does not fit the strict definition of a selfservice terminal, since it is used by personnel of a financial institution; it is included in this range because it is
very close in function to other self-service terminals.

SECURITY PROBLEM
X 167011
X 167021

X I 7000 1

DOCUMENT DISPENSER: A device that dispenses documents, primarily bills
TICKET DISPENSER
KEY DISPENSER
COIN DISPENSER
ENVELOPE DISPENSER

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 166011

X ' 6700 '

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
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
CARD DEPOSITORY: A device that retains credit, personal banking, or other cards used to access a personal
banking machine (PBM)

AUDIBLE ALARM: A device which emits an audible
sound.
PROTECTIVE DOOR: An electronically or mechanically
operated covering for access to a device.

PERSONNEL: Action on the part of customer, service, or other personnel
X 170011

X 170021

LOCAL SYSTEM OPERATOR: A person (or program) colocated with a system and responsible for the operation of
all or part of it, or responsible for performing system orientated procedures
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

Chapter 8. Common Fields

8-51

MS Major Vectors

Probable Causes (X' 93') Alert MS Subvector
Byte

Bit

Content

X 17003 1

X 170041
X 17005 1
X ' 7006 1
X ' 7007 1
X ' 7010 '
X ' 7011 1
X ' 7012 1
X ' 7013 1
X ' 7014 1

X ' 8000 '

NETWORK OPERATOR: A person (or program) responsible for the operation of all or part of the network, or
responsible for performing network orientated procedures
USER: Anyone who requires the services of a computer
system, such as an "end user"
SYSTEM PROGRAMMER
CUSTOMER PERSONNEL
SERVICE REPRESENTATIVE
PRINTER OPERATOR
TERMINAL CONTROL UNIT OPERATOR
LAN BRIDGE OPERATOR
LAN MANAGER OPERATOR
LAN TRACE TOOL OPERATOR: A person (or program)
responsible for the operation of a tool that allows a LAN
user to monitor the traffic on the LAN.

CONFIGURATION
X 180011
X ' 8002 1
X ' 8003 1
X 180041

X'EOOO'-X'EFFF'

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.
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.

XI FEOO 1

UNDETERMINED: No probable cause can be determined for this
Alert condition

XI FFFF 1

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.

User Causes (X' 94') Alert MS Subvector
Byte

Bit

o
8-52

Content

Length (p + 1), in binary, of the User Causes subvector

SNA Formats

MS Major Vectors

User Causes (X' 94') Alert MS Subvector
Byte

Bit

Content

Key: X ' 94 1

2-p

Two or more subfields containing user cause data, as described below for keys
XIOOI -X'7F' and in "Network Alert (XIOOOOI) Common Subfields" on page 8-97
for keys X ' 80 ' -X'FE'.
XI 01 1 User Causes
X1811 Recommended Actions
X182 I Detailed Data
X' 83 1 Product Set ID Index
Note: Subfields X I 01 1 and X ' 81 1 are always present. One or more instances of
the X 182 I and/or X 183 I subfields may be present, depending on the code points
present in the X101 1 and X1811 subfields.

User Causes (X 101 1) 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.

User Causes (X' 01') User Causes Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the User Causes subfield

Key: X 1011

Chapter 8. Common Fields

8-53

MS Major Vectors

User Causes (X' 01 ') User Causes Subfield
Byte

Bit

2-q

Content
2-byte user cause co de 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 2-digit value of X 100 I represents a more general
description than a non-X'OOI; for this reason, the non-XIOOI codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to XI **00 1 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 1821) subfield. The
one or more necessary X 1821 subfields follow immediately after this subfield in
the X 1941 subvector, in the order in which they are to be associated with the
gaps specified in the X 1011 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 1111 subvector indicated by a Product Set 10 Index (X 183 1)
subfield. The necessary X 183 1 subfields follow immediately after the X 1011 subfield, in the same subvector, in the order in which they are to be associated
with the gaps specified in the X 1011 subfield.
The third digit of each user cause code point indicates the number of succeeding X 1821 subfields that are associated with the code point, and whether a
X 183 1 subfield is associated with it, as follows:
X IXXOX I -X l xx9x l :

No X 182' subfields.

X'xxAxl -X'xxBx':

One X' 82' subfield.

XIXXCX I :

Two X 182 I subfields.

XlxxDxl:

Three X 182 I subfields.

XlxxExl:

One X' 83 I subfield.

XlxxFxl:

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

Defined user cause codes are:
X '0100 1

STORAGE CAPACITY EXCEEDED: A request has been received
requiring more storage than is currently available
X I 0111 1

8-54

SNA Formats

THE PORTION OF MAIN STORAGE MADE AVAILABLE BY
THE USER FOR A PARTICULAR OPERATION HAS BEEN
EXHAUSTED

MS Major Vectors

User Causes (X' 01') User Causes Subiield
Byte

Bit

Content
X'0112'

X ' 0200 '

A USER-SPECIFIED THRESHOLD, INDICATING THAT
AVAILABLE AUXILIARY STORAGE IS NEARLY FULL, HAS
BEEN REACHED

POWER OFF: The equipment is powered off and will require operator
action to power on and prepare equipment for use
X '0201 1
X '0202 1
X'0203 1
X'0204'
X '0205 1
X '0206'
X'0207'
X '020B 1
X'0209'
X'020A'
X'020B'
X'020C'
X '0200'
X '020E 1
X'020F'
X '0210 1
X '0211'
X '0212 1
X '0213 1
X'0214 1
X'0220 '
X '0221 1
X '0222 1
X '0223 I
X '0224 1
X '0225 1
X '0226'

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
COMMUNICATION EQUIPMENT POWER OFF
CALLING DCE POWER OFF
CALLED DCE POWER OFF
CALLED DTE POWER OFF
MODEM POWER OFF
TERMINAL MULTIPLEXER POWER OFF
DEVICE POWER OFF
CONSOLE POWER OFF
LAN MANAGER POWER OFF
REMOTE NODE POWER OFF
LOCAL DSU/CSU POWER OFF
REMOTE DSU/CSU POWER OFF
OPTICAL FIBER CONVERTER POWER OFF: A device
which converts electrical signals into optical signals and
vice-versa.
X'02A1'
(sfB2 qualifier) LOCAL MODEM POWER OFF
Note: The qualifier identifies the link segment level (LSL) on which the local
modem belongs.
(sfB2 qualifier) REMOTE MODEM POWER OFF
X'02A2'
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.
(sfB2 qualifier) LOCAL DSU/CSU POWER OFF
X ' 02A3'
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.

Chapter 8. Common Fields

8-55

MS Major Vectors

User Causes (X' 01') User Causes Subfield
Byte

Bit

Content
X '02A4 1

X 12200 1

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 12201 1
X ' 2210 '

X 12300 1

X ' 2310 '
X ' 23AO'

X ' 3381 1

S NA Formats

AN OPERATOR HAS DEACTIVATED ALL PORTS IN A
ROTARY GROUP
AN OPERATOR HAS DEACTIVATED ALL PORTS IN A
ROTARY GROUP USED BY AN X.21 SHORT HOLD MODE
SESSION

CABLE NOT CONNECTED: A cable is either loose or disconnected
X ' 3401 1
X'3402 1
X ' 3403 1
X ' 3451 1

8-56

PORT DEACTIVATED
LINE NOT ENABLED AT CALLED DTE
PORT DEACTIVATED AT CALLED DTE

ADAPTER NOT READY: An adapter has not been made ready for
use
X ' 3380 '

X 13400 1

THE MAXIMUM NUMBER OF WORKSTATIONS SUPPORTABLE BY THE LOCAL WORKSTATION CONTROLLER HAS
BEEN EXCEEDED

LINE NOT ENABLED: A communication link has not been prepared
for data transmission
X 12501 1
X ' 2510 '
X ' 2511 1

X 13300 1

CALLED NUMBER BUSY
INCORRECT TELEPHONE NUMBER SPECIFIED
CALLING DTE DOES NOT SUBSCRIBE TO THIS FACILITY:
The calling DTE has requested a service that it does not
subscribe to
X.21 CONNECTION INTENTIONALLY CLEARED BY TERMINAL CONTROL UNIT OPERATOR
CONNECTION NOT ESTABLISHED: (sf82 qualifier)
Note: The qualifier indicates the telephone number for
the connection that could not be established.

BUSY: A requested resource was unavailable because it was in use
X ' 2401 1

X 12500 1

CALLED DTE TAKEN OUT OF SERVICE
REMOTE NODE CONTROL PROGRAM IPL HAS
OCCURRED

CONNECTION NOT ESTABLISHED: A telephone connection required
for the requested operation has not been established
X 12301 1
X 12304'
X ' 2308 1

X 12400 1

(sf82 qualifier) REMOTE DSU/CSU POWER OFF
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.

CABLING INSTALLED INCORRECTLY
KEYBOARD UNPLUGGED
LINE SWITCHED TO INCORRECT POSITION
DEVICE CABLE NOT CONNECTED

MS Major Vectors

User Causes (X' 01 ') User Causes Subfield
Byte

Bit

Content

X '34AO'

X'34A1'

X '34A2'
X '3800'

CABLE NOT CONNECTED: (sfB2 qualifier)
Note: The qualifier specifies the disconnected cable, by,
for example, specifying the number of the port to which it
should be attached.
CABLE NOT INSTALLED: (sfB2 qualifier)
Note: The qualifier specifies the cable that was not
installed.
CABLE UNPLUGGED: (sfB2 qualifier)
Note: The qualifier specifies the cable that is unplugged.

LPDA DCE: A DCE that supports link problem determination aid
functions, e.g., IBM LPDA-2 modem and IBM LPDA-2 DSU/CSU.
X '3B01'
X '3B02'
X '3B03'
X'3BA1'

X '3BA2'

X '3BA3'

X '3BA4'

X '3BA5'

X '3BA6'

X '3BA7'

X '3BAB'

X '3BA9'

X '38AA'

X '38AB'

SNBU HAS BEEN DISCONNECTED
TC LEAD ACTIVE ON REMOTE NODE INTERFACE
TC LEAD ACTIVE ON OTHER REMOTE NODE INTERFACE
SPEED MISMATCH BETWEEN MODEMS ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
SPEED MISMATCH BETWEEN DSU/CSU'S ON (sfB2 qualifier)
Note: The qualifier identifies the the link segment level
(LSL) on which the DSU/CSUs belong.
(sf82 qualifier) LOCAL MODEM IN TEST MODE
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sfB2 qualifier) LOCAL DSU/CSU IN TEST MODE
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
(sf82 qualifier) REMOTE MODEM IN TEST MODE
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.
(sf82 qualifier) REMOTE DSU/CSU IN TEST MODE
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
(sf82 qualifier) LOCAL MODEM REINITIALIZED
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sf82 qualifier) LOCAL DSU/CSU REINITIALIZED
Note: The qualifier identifies the link segment level (LSL)
on which the local DSI/CSU belongs.
(sfB2 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.
(sfB2 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.
(sf82 qualifier) LOCAL MODEM POWER OFF THEN ON
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.

Chapter 8. Common Fields

8-57

MS Major Vectors

User Causes (X' 01 ') User Causes Subfleld
Byte

Bit

Content
X '38AC 1 (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 1 (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 1 (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 1 (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 '38BO 1 (sf82 qualifier) LOCAL DSU/CSU IN CONFIGURATION
MODE
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
X 14000 1

PERFORMANCE DEGRADED
X 14001 1

X ' 4002 1

X ' 4003 1

X 15100 1

MEDIA DEFECTIVE: The medium (tape, disk, diskette, paper, e.g.) is
defective and must be replaced or corrected to continue processing
X ' 5101 1
X 15102 1

X'5110 '
X' 5111 1

X ' 5200 '

SNA Formats

IMPROPER DISKETTE INSERTED: There is a usable
diskette in the diskette drive, but it is not the required one
NO DISKETTE OR DEFECTIVE DISKETTE INSERTED: There
is no diskette in the diskette drive, or the diskette in the
drive is unusable
NON-DUPLEX PAPER IN CASSETTE
ID CARD RECORDING SURFACE: The recording media on
an Identification Card Reader (ICR) card is defective,
missing or the reading device has failed.

MEDIA JAM: The medium (usually paper, forms, or cards) is
jammed in the machine and operator action is required to correct the
problem
X ' 5201 1
X 15202'
X ' 5203 1

8-58

STORAGE SUBSYSTEM OVERLOADED: The number of
attached devices is not sufficient to handle the current
work load without performance degredation.
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.
COMMUNICATION SUBSYSTEM OVERLOADED: The
number of lines, maximum aggregate data rate, or
number of attached devices i"s in excess of that which can
be handled without performance degredation.

CARD JAM
FORMS JAM
PAPER JAM

MS Major Vectors

User Causes (X' 01') User Causes Subfleld
Byte

Bit

Content
X 15204 1
X 15300 1

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 153011
X ' 5302 1
X ' 5303 1
X ' 5304 1
X ' 5305 1
X 15306 1
X ' 5313 1

X ' 5400 '

FILM JAM: There is a jam condition in the medium for a
camera device.

OUT OF CARDS
OUT OF FORMS
OUT OF PAPER
OUT OF FILM: The medium for a camera device has been
exhausted.
OUT OF BILLS OR DOCUMENTS: The medium for a document feeding device has been exhausted.
OUT OF ENVELOPES
CASSETTE OUT OF PAPER

OUT OF SUPPLIES: A device is out of supplies required for it to
perform its function
X 15401 1

END OF RIBBON ENCOUNTERED: A printer has encounter~d the end of the print ribbon
X ' 5402 1 OUT OF INK
X 15403 lOUT OF TONER
XI 5404 lOUT OF FUSER 01 L
XI 5405 1 OUT OF STAPLES

X ' 5500 '

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 ' 5501 1
X ' 5502 1
X ' 5503 1
X ' 5504 1
X ' 5505 1
X ' 5506 1

X 15600 1

LOW ON SU PPLlES: A device is low on supplies required for it to
perform its function
X ' 5602 1
X ' 5603 1
X ' 5604 1
X 15605 1

X 16000 1

LOW ON CARDS
LOW ON FORMS
LOW ON PAPER
LOW ON FILM: The medium for a camera device is nearly
exhausted.
LOW ON BILLS OR DOCUMENTS: The medium for a document feeding device is nearly exhausted.
LOW ON ENVELOPES

LOW
LOW
LOW
LOW

ON
ON
ON
ON

INK
TONER
FUSER 01 L
STAPLES

DEVICE NOT READY: A device has not been made ready for operation
X 160011

X'6010'

DEVICE OFFLINE: The device requested has been varied
offline by the operator and must be varied online for processing to continue
DASD DEVICE NOT READY

Chapter 8. Common Fields

8-59

MS Major Vectors

User Causes (X' 01 ') User Causes Subfield
Byte

Bit

Content
X ' 6011 1
X ' 6012 1
X ' 6013 1
X ' 6014 1
X ' 6015 1
X ' 6016 1
X ' 6017 1
X ' 6018 1
X ' 6019 1
X ' 6020 '
X 16400 1

DEPOSITORY: A device that receives items into a system.

X ' 6401 1
X 16402 1

X ' 7000 '

X 17003 1
X 170041

X 17005 1

X 17010 1

X 17104'
X'7105'
X 17106'
X'7107 1
X 17108 1

SNA Formats

NO CASSETTE IN PRINTER
CARTRIDGE NOT INSTALLED CORRECTLY: A cartridge
used to collect or dispense documents is not installed correctly.
OUT OF FOCUS: An operator is required to make an
adjustment to a camera device.
USER NEEDS ASSISTANCE: Someone who uses the services of a computer system, such as an "end user",
requires assistance in this usage.
DEVICE IS NOT IN THE PROPER POSITION: A device is
not in the correct operating position when an attempt is
made to use it.
CALL AUTHORIZATION REQUIRED

INCORRECT PROCEDURE: An appropriate procedure was not followed

X'7101 1
X ' 7102 1
X'7103 1

8-60

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.
DEPOSITORY FULL: A cartridge or other container used
to collect items such as checks, envelopes, or documents
has reached it's capacity.

OPERATOR: Operator action is required to return the machine to
operational status

X ' 7001 1
X 170021

X ' 7100'

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

TOKEN-RING REMOVE ADAPTER COMMAND RECEIVED
PAPER INSTALLED INCORRECTLY
LAN MANAGER OPERATOR ENTERED INCORRECT PASSWORD
UNAUTHORIZED ACCESS TO LAN MANAGEMENT
SERVER A TTEM PTED
UNAUTHORIZED USER ATTEMPTED INSERTION INTO LAN
ADAPTER ADDRESS NOT ENTERED IN AUTHORIZATION
LIST
CSMA/CD REMOVE ADAPTER COMMAND RECEIVED
OPERATOR ENTERED INCORRECT PASSWORD

MS Major Vectors

User Causes (X' 01') User Causes Subfield
Byte

Bit

Content

X ' 7109'
X ' 710A'
X ' 710B'

X '710C 1
X 17110 1

X ' 7111 1

X ' 7120 '
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 ' 7201 1
X ' 7202 1

X ' 7300 '

MICROCODE DUMP REQUESTED
SOFTWARE DUMP REQUESTED

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 173011
X '73AO 1

X ' 73A1 1

X ' 7400 '

LAN BRIDGE OPERATOR TOOK BRIDGE OFFLINE
Note: When this condition occurs, the bridge can no
longer forward frames.
LAN MANAGER OPERATOR TOOK BRIDGE OFFLINE
Note: When this condition occurs, the bridge can no
longer forward frames.
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
UNAUTHORIZED TRACE TOOL IN LAN: A tool that allows
a LAN user to monitor the traffic on the LAN.
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
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
INCORRECT TEST TOOL USED: The test tool used for servicing the device is incorrect.

DISKETTE OR DIRECTORY FU LL: There is no more
diskette space or directory space on the diskette.
FI LE FU LL (sf82 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.
FILE NEEDS REORGANIZATION (sf82 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.

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 ' 7401 1

DIRTY READ/WRITE HEAD

Chapter 8. Common Fields

8·61

MS Major Vectors

User Causes (X' 01 ') User Causes Subfield
Byte

Bit

Content
X'74A1'
X' EOOO ' - X' EFFF '

BLOCKED AIR FILTER (sfB2 qualifier)
Note: The qualifier identifies the air filter number.
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.

X' FOOO'

(no display): Additional message data

X' FBOO'

(no display): Additional message data
No{e: The X' FBxx' range is used for additional messages that are
identical for User, Install, and Failure Causes.
X'FBCO'

X'FBDO'

FAILING COMPONENT IS IDENTIFIED BY (sfB2 qualifier)
(sfB2 qualifier)
Note: The qualifiers identify the failing component by
means of its logical location, e.g., its port number and
device add ress.
PROBLEM IS RELATED TO THE CONTROLLER LOCATED
AT (sfB2 qualifier) (sfB2 qualifier) (sfB2 qualifier)
Note: The qualifiers identify the controller location as
follows:
Q1
Q2
Q3

X'FBEO'
X' FFFF '

= RACK
= UNIT (within a rack)
= CARD SLOT (within a unit)

FAILING COMPONENT IS IDENTIFIED BY (sfB3 product
text)

Reserved

Install Causes (X' 95') Alert MS Subvector
This subvector transports code points for stored text detailing the probable
install causes for t'he 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.

8-62

SNA Formats

MS Major Vectors

Install Causes (X' 95') Alert WiS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Install Causes subvector

Key: X '95'

2-p

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 8-97 for keys X'80' -X'FE'.
X '01'
Install Causes
Recommended Actions
X '81'
X '82'
Detailed Data
Product Set ID Index
X '83'
Note: Subfields X'01' 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 '01' and X '81' subfields.

Install Causes (X' 01') 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.

Install Causes (X' 01') Install Causes Subfield
Byte

Bit

Content

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

Key: X'01'

2-q

2-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 '00' represents a more general
description than a non-X' 00'; for this reason, the non-X' 00' codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to X' * *00' code points) if it does not recognize the
more specific code point (e.g., because of different release schedules).

Chapter 8. Common Fields

8-63

MS Major Vectors

Install Causes (X' 01') Install Causes Subfield
Byte

Bit

Content

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 '95' subvector, in the order in which they are to be associated with the
gaps specified in the X'01' 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 '11' subvector indicated by a Product Set 10 Index (X '83')
subfield. The necessary X '83' subfields follow immediately after the X '01' subfield, in the same subvector, in the order in which they are to be associated
with the gaps specified in the X '01' subfield.
The third digit of each install 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 install cause codes are:
X'1200'

INCORRECT HARDWARE CONFIGURATION: The hardware has been
installed incorrectly and the requested function cannot be performed
X'1201'

X'1202'
X'1203'
X'1204'
X'1205'
X'1206'

8-64

SNA Formats

OPTICAL FIBER CONVERTER CONFIGURATION: A device
which converts electrical signals into optical signals and
vice-versa, is not configured correctly.
LOCAL MODEM: The modem connected to the Alert
sender
REMOTE MODEM: The modem remote from the Alert
sender
LOCAL DIGITAL DATA DEVICE: The digital data device
(DOD) connected to the Alert sender
REMOTE DIGITAL DATA DEVICE: The digital data device
(DOD) remote from the Alert sender
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
DOD; see code pOints X '1202' and X '1204'.

MS Major Vectors

Install Causes (X' 01') Install Causes Subiield
Byte

Bit

Content
X'1207'

X'1300'

INCORRECT SOFTWARE GENERATION: A program has been
installed incorrectly and the requested function cannot be performed
X'13E1'

X'1400'

X'1402'

X'1602'

X'16A1'

'- . .

INCORRECT CUSTOMIZATION IMAGE: The software
customization image is incompatible with the actual
microcode configuration
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
INCORRECT SOFTWARE LEVEL (sf82 qualifier)
Note: The qualifier specifies a generation parameter.

INCORRECT VALUE SPECIFIED: An incorrect value has been specified for a system operational parameter
X'1701'
X'1702'

(

INCORRECT CUSTOMIZATION PARAMETERS
INCORRECT MICROCODE FIX

MISMATCH BETWEEN SOFTWARE AND MICROCODE: A conflict
exists between a software program and a microcode program
X'1601'

X'1700'

MISMATCH BETWEEN HARDWARE CONFIGURATION AND
SOFTWARE GENERATION
MISMATCH BETWEEN HARDWARE AND SOFTWARE CONFIGURATIONS: The hardware configuration represented
in a software product does not match the actual hardware
confi g uration

MISMATCH BETWEEN HARDWARE AND MICROCODE: A conflict
exists between the hardware configuration and microcode
X'1501'
X'1502'

X'1600'

INCORRECT SOFTWARE GENERATION: (sf83 product text)

MISMATCH BETWEEN HARDWARE AND SOFTWARE: A conflict
exists between the hardware configuration and software
X'1401'

X'1500'

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
DOD; see code points X'1203' and X'1205'.

X'1703'
X'1704'
X'1705'
X'1706'
X'1707'
X'1708'

INTERVENTION TIMER VALUE TOO SMALL
RTS ACTIVATION LIMIT PARAMETER OF THE SENDING
NODE IS INCORRECT
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

Chapter 8. Common Fields

8-65

MS Major Vectors

Install Causes (X' 01') Install Causes Subfield
Byte

Bit

Content
X ' 17CO'

X ' 2600 '

SYSTEM OR TRANSMISSION MEDIA INSTALLED NEAR ELECTRICAL
INTERFERENCE

X ' 3400 '

CABLE INSTALLED INCORRECTLY: A cable has been incorrectly
installed
X ' 3401 1
X ' 3402 1
X 13403 1
X ' 3404 1
X 13405 1
X 13406 1
X 13407 1
X ' 3408 1
X 13451 1
X 134AO 1

X '34A 11

X ' 3500 '

X '35AO 1

X '35A 11

SNA Formats

LOCAL DCE INTERFACE CABLE INSTALLED INCORRECTLY
LINE ADAPTER MULTIPLEXER CABLE INSTALLED INCORRECTLY
REMOTE DCE INTERFACE CABLE INSTALLED INCORRECTLY
DeE EMULATION CABLE INSTALLED INCORRECTLY
LOCAL TELECOMMUNICATION CABLE NOT PROPERLY
CONNECTED
REMOTE TELECOMMUNICATION CABLE NOT PROPERLY
CONNECTED
PHYSICAL LINE CONNECTIONS
OPTICAL FIBER CABLE INSTALLED INCORRECTLY
DEVICE CABLE INSTALLED INCORRECTLY
(sf82 subfield) LOCAL DCE INTERFACE CABLE NOT PROPERLY CONNECTED
Note: The qualifier identifies the link segment level (LSL)
on which the local DCE belongs.
(sf82 subfield) REMOTE DCE INTERFACE CABLE NOT
PROPERLY CONNECTED
Note: The qualifier identifies the link segment level (LSL)
on which the remote DCE belongs.

COMMUNICATION EQUIPMENT INSTALLED INCORRECTLY: Some
communication equipment has been installed incorrectly; the Alert
sender cannot determine the precise nature of this equipment
X ' 3501 1

8-66

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.

MULTI-SEGMENT LINK DEFINED AND TAILED-CIRCUIT
ATTACHMENT CABLE NOT CONNECTED
(sf82 qualifier) LOCAL MODEM EXTERNAL CLOCK NOT
PROVIDED
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sf82 qualifier) REMOTE MODEM EXTERNAL CLOCK NOT
PROVIDED
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.

MS Major Vectors

Install Causes (X' 01 ') Install Causes Subfleld
Byte

Bit

Content
X'3SA2'

X '3SA3'

X'3SA4'

X'3SAS'

X'3SA6'

X '3SA7'

X '3700'

LAN CONFIGURATION ERROR: A configuration parameter for a
local-area network has been specified incorrectly
X'3704'
X'3724'

X '3800'

X'38A1'

X'38A2'

X'38A3'

X'38A4'

X'38AS'

TOKEN-RING DUPLICATE STATION ADDRESS ASSIGNED
CSMA/CD DUPLICATE STATION ADDRESS ASSIGNED

LPDA CONFIGURATION ERROR: A configuration parameter for an
LPDA link has been specified incorrectly
X'38AO'

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.
(sf82 qualifier) MODEMS SPEED MISMATCH
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
(sf82 qualifier) DSU/CSU'S SPEED MISMATCH
Note: The qualifier identifies the link segment level (LSL)
on which the DSU/CSUs belong.
(sf82 qualifier) INCOMPATIBLE MODEMS
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
SENDING NODE AND (sf82 qualifier) MODEMS CONFIGURATION MISMATCH
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
SENDING NODE AND (sf82 qualifier) DSU/CSU'S CONFIGURATION MISMATCH
Note: The qualifier identifies the link segment level O.. SL)
on which the DSU/CSUs belong.

X'38A6'

(sf82 qualifier) LOCAL MODEM ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sf82 qualifier) LOCAL DSU/CSU ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
(sf82 qualifier) REMOTE MODEM ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.
(sf82 qualifier) REMOTE DSU/CSU ADDRESS INCORRECT
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
(sf82 qualifier) LOCAL MODEM LPDA-2 DISABLED
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sf82 qualifier) LOCAL DSU/CSU LPDA-2 DISABLED
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
(sf82 qualifier) LOCAL MODEM NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.

Chapter 8. Common Fields

8·67

MS Major Vectors

Install Causes (X' 01 ') Install Causes Subfield
Byte

Bit

Content

X'3BA7'

X '3BAB'

X' 3BA9'

X '3BAA I

X '3BAB I

X'3BAC'

X' 3BAD I

X ' 3BCO'

X ' 3BC1 1

X'BOOO'

CONFIGURATION ERROR: A system or device generation or
customization parameter has been specified incorrectly or is inconsistent with the actual configuration.
X 'BOC1

X'BOC2 1

8-68

SNA Formats

(sfB2 qualifier) REMOTE MODEM NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.
(sfB2 qualifier) LOCAL DSU/CSU NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
(sfB2 qualifier) REMOTE DSU/CSU NOT CONFIGURED
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
(sfB2 qualifier) LOCAL MODEM CONFIGURED AS SECONDARY OR TRIBUTARY
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sfB2 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.
(sfB2 qualifier) LOCAL MODEM CONFIGURED AS
CONTROL
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
(sfB2 qualifier) LOCAL DSU/CSU CONFIGURED AS
CONTROL
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
SPEED MISMATCH BETWEEN (sfB2 qualifier) AND (sfB2
qualifier)
Note: The qualifiers identify the link segment levels (LSL)
where the speed mismatch is.
(sfB2 qualifier) LOCAL MODEM HAS A 2-WIRE COUPLER
AND THE (sfB2 qualifier) REMOTE MODEM HAS A 4-WIRE
COUPLER
Note: The qualifiers identify the link segment levels (LSL)
where the modems belong.

STORAGE CONFIGURATION ERROR (sfB2 qualifier) (sfB2
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.
LOCAL WORK STATION CONFIGURATION ERROR (sfB2
qualifier) (sfB2 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.

MS Major Vectors

Install Causes (X' 01') Install Causes Subflllid
Byte

Bit

Content

X '80C3 I

X 180C4 '

X'EOOO' -X'EFFF'

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.
COMMUNICATION CONFIGURATION ERROR (sf82 qualifier) (sf82 qualifier): The actual communication configuration does not match the configuration records.
Note: The first qualifier identifies the configuration
object/record. The second qualifier identifies the incorrect
configuration parameter.
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 I FOOO I

(no display): Additional message data

X I F800 I

(no display): Additional message data
Note: The X I F8xx I range is used for additional messages that are
identical for User, Install, and Failure Causes.
X' F8CO'

XIF8DO'

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.
PROBLEM IS RELATED TO THE CONTROLLER LOCATED
AT (sf82 qualifier) (sf82 qualifier) (sf82 quqlifier)
Note: The qualifiers identify the controller location as
follows:
Q1
Q2
Q3

X' F8EO'
X I FFFF I

= RACK
= UNIT (within a rack)
= CARD SLOT (within a unit)

FAILING COMPONENT IS IDENTIFIED BY (sf83 product
text)

Reserved

Chapter 8. Common Fields

8·69

MS Major Vectors

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.

Failure Causes (X' 96') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Failure Causes subvector

Key: X'96'

2-p

Two or more subfields containing failure cause data, as described below for
keys X'OO' -X'7F' and in "Network Alert (X 10000 I) Common Subfields" on
page 8-97 for keys X ' 80' -X'FE'.
X 101'
Failure Causes
Recommended Actions
X '81'
X ' 82 1 Detailed Data
X 183'
Product Set 10 Index
Note: Subfields X 101' and X 181' are always present. One or more instances of
the X '82' and/or X 183 I subfields may be present, depending on the code points
present in the X 1011 and X '81 1 subfields.

Failure Causes (X'D11) 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.

Failure Causes (X' 01 ') Failure Causes Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the Failure Causes subfield

Key: X I 01

2- q

2-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.

8-70

SNA Formats

MS Major Vectors

Fallura Causes
Byte

(~' 01')

Bit

Fallura Causes Subfield
Content
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' 00' represents a more general
description than a non-X' 00'; for this reason, the non-X' 00' codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to X' * *00' code points) if it does not recognize the
more specific code point (e.g., because of different release schedules).
The expression U(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' 96' subvector, in the order in which they are to be associated with the
gaps specified in the X'01' subfield.
The expression U(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 '11' subvector indicated by a Product Set ID Index (X '83')
subfield. The necessary X '83' subfields follow immediately after the X '01' subfield. in the same subvector. in the order in which they are to be associated
with the gaps specified in the X' 01' subfield.
The third digit of each failure 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 failure cause codes are:
X'OOOO'

PROCESSOR: The equipment used to interpret and process programmed instructions
X'OOO1'

X'OO02'

X'OO03'

I
\.

X'OO04'
X'OOO5'
X'OOO6'

MOSS HARDWARE: A hardware failure in MOSS (Maintenance and Operation Subsystem), the service processor
for a communication controller
MOSS MICROCODE: A microcode failure in MOSS (Maintenance and Operation Subsystem), the service processor
for a communication controller
PROCESSOR SWITCH: A component within a hardware
product used to switch busses and the resources attached
to them among processors
CONTROL PANEL
SYSTEM I/O BUS
PROCESSOR MACHINE CHECK: A failure in the
processor which precludes it from continuing operation.
Chapter 8. Common Fields

8-71

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfield
Byte

Bit

Content
X'0007'

X'0008'

X'0009'

X'OOOA'
X'0010'
X'0011'

X'0020'

X'0030'
X'0031'

X'0032'

X'0033'

X'0034'

X'00E1'
X'0100'

STORAGE: The random-access memory (RAM) or read-only memory
(ROM) accessible by a processor and by peripheral devices
X '0101'

X '0102'

X'0103'
X '0104'
X'0110'

8-72

SNA Formats

CARD ENCLOSURE AND/OR BOARD: The enclosure and
boards used to hold circuit cards and provide power
and/or sig nal connections for the cards.
VECTOR PROCESSOR: The vector processing element
associated with a central processing unit (CPU) has failed
and is in a reserved state.
SYSTEM CHECK STOP
SERVICE PROCESSOR: A maintenance, service and
support processor; sometimes called a process controller
LAN MANAGER PROCESSOR
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.
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.
SYSTEM MICROCODE: The specific microcode was not
identified.
SYSTEM STORAGE MICROCODE
Note: See also code point X '0421' (LOADABLE STORAGE
CONTROLLER MICROCODE)
SYSTEM DISPLAY MICROCODE
Note: See also code point X '0422' (LOADABLE WORK
STATION CONTROLLER MICROCODE)
SYSTEM COMMUNICATION MICROCODE
Note: See also code point X '0423' (LOADABLE COMMUNICATIONS SUBSYSTEM CONTROLLER MICROCODE)
SYSTEM PRINTER MICROCODE
Note: See also code point X '0422 1 (LOADABLE WORK
STATION CONTROLLER MICROCODE)
(sf83 product text) PROCESSOR

MAIN STORAGE: Storage from which instructions and
other data can be loaded directly into registers for subsequent execution or processing
AUXILIARY STORAGE: Storage that can not be directly
addressed by a processor, such as external or secondary
storage
MAIN STORAGE MACHINE CHECK: A failure in main
storage which precludes it from continuing operation.
EXPANDED STORAGE: A specific type of auxiliary storage
used for data and program paging
STORAGE CONTROL: The component that controls
access to storage

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content
X 10111 1

X '01E1 1
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 1
X ' 0202 1
X ' 0203 1
X ' 0204 1
X ' 0205 1
X ' 0210 '
X ' 0211 1
X ' 0220 '
X ' 02CO'

X ' 0230 '
X 10231 1
X ' 0240 '
X ' 0300 '

X 103211
X ' 0400 '

INTERNAL POWER UNIT: An element of the power subsystem providing electrical power to a specific component
INTERNAL POWER CONTROL UNIT: An element of the
power subsystem that controls the internal power units
POWER CABLE
POWER CORD
POWER SUBSYSTEM PROCESSOR: A processor within
the power subsystem responsible for its operation
BATTERY
MOSS BATTERY
MAIN AC POWER SUPPLY
INTERNAL POWER UNIT FOR (sf82 qualifier) (sfB2 qualifier)
Note: The qualifiers identify the adapter numbers of the
adapters served by the failing internal power unit.
POWER DISTRIBUTION UNIT
MOTOR GENERATOR
INTERNAL CLOCK: A mechanism that keeps time.

COOLING OR HEATING SUBSYSTEM: The subsystems within a hardware product responsible for maintaining a temperature at which the
product can operate
X ' 0301 1
X ' 0302 1
X ' 0310 '
X ' 0311 1
X ' 0320 '

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
(sf83 product text) MAIN STORAGE

COOLING FAN
AIR FILTER
AIR FLOW DETECTOR
THERMAL DETECTOR
COOLANT DISTRIBUTION UNIT: A unit that distributes
chilled water for cooling purposes, usually circulated in a
closed system, has failed.
THERMAL LIMITS EXCEEDED: The acceptable thermal
limits for normal operation have been exceeded.

SUBSYSTEM CONTROLLER: A unit within a subsystem that interfaces between a processor and the devices in the subsystem
Note: See Alert Description X 11600 1, SUBSYSTEM FAILURE, for
descriptions of the particular subsystems mentioned here.
X ' 0401 1
X ' 0402 1

STORAGE CONTROLLER
WORKSTATION CONTROLLER

Chapter 8. Common Fields

8-73

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfield
Byte

Bit

Content

X ' 0403 1

X ' 0411 1
X ' 0412 1
X ' 0413 1
X'0421 1
X ' 0422 1
X ' 0423'
X'0441 1

X ' 0442 1
X ' 0443 1

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 105011
X ' 0502'
X ' 0503 1
X ' 0506 1

X I 1000 1

X ' 100F'

X 11010'
X 11011'

SNA Formats

STORAGE SUBSYSTEM
WORKST ATION SUBSYSTEM
COMMUNICATIONS SUBSYSTEM
CHANNEL SUBSYSTEM: A channel subsystem or a
shared element within a channel subsystem has failed.
The failing resource consists of more than just a single
channel path.

SOFTWARE PROGRAM: A program implemented in software, as distinguished from one implemented in microcode
X ' 100A'

8-74

COMMUNICATIONS SUBSYSTEM CONTROLLER
Note: Contrast this code point with X 13111 1, 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.
INTERMITTENT STORAGE CONTROLLER ERROR
INTERMITTENT WORKSTATION CONTROLLER ERROR
INTERMITTENT COMMUNICATIONS SUBSYSTEM CONTROLLER ERROR
LOADABLE STORAGE CONTROLLER MICROCODE
LOADABLE WORKSTATION CONTROLLER MICROCODE
LOADABLE COMMUNICATIONS SUBSYSTEM CONTROLLER MICROCODE
STORAGE CONTROLLER INTERFACE: The interface
between a storage controller and the main processor in
its node
WORKSTATION CONTROLLER INTERFACE: The interface
between a workstation controller and the main processor
in its node
COMMUNICATIONS SUBSYSTEM CONTROLLER INTERFACE: The interface between a communication subsystem controller and the main processor in its node

COMMUNICATIONS PROGRAM ABNORMALLY TERMINATED
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.
HOST PROGRAM: A program running in a host processor
that is a primary or controlling program in a system
PRINTER SERVER PROGRAM: A program running in a
printer server that controls a printer
Note: See also Failure Cause X 10011 1, PRINTER SERVER.

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfleld
Byte

Bit

Content
X 11012 1
X 11021 1

X 11022 1

X ' 1023 1
X 11024 1

X ' 1030 '
X 11031 1

X ' 1032 1

X ' 1040 '
X ' 10A1 1
X ' 10E1 1
X 12000 1

SOFTWARE DEVICE DRIVER: A program designed to
control a device.
COMMUNICATION CONTROLLER CONTROL PROGRAM:
A software program that is designed to schedule and
supervise the execution of programs in a communication
controller
COMMUNICATIONS PROGRAM: A software program
designed to provide direct assistance to a node in communicating with other nodes
COMMUNICATIONS PROGRAM IN REMOTE NODE
COMMUNICATIONS ACCESS METHOD: A software
program in a host that provides access to a telecommunications network
LAN MANAGER PROGRAM: The software program in a
LAN manager
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).
RING ERROR MONITOR: The LAN management server
responsible for receiving and processing error reports
from the stations on its token-ring
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.).
UNABLE TO BUILD ALERT REQUESTED BY (sf82 qualifier)
Note: An Alert builder utility could not complete a request
from the program identified by the qualifier.
SOFTWARE PROGRAM (sf83 product text)

COMMUNICATIONS ERROR: An error has occurred on a communication facility
X ' 2001 1
X ' 2002 1
X ' 2003 1
X ' 2004 1
X ' 2005 1
X ' 2006 1
X ' 2007 1
X ' 2008 1
X ' 2009 1
X ' 200A'

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
Chapter 8. Common Fields

8-75

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content
X'200E'

X'200F'
X'2010'

X'2040'
X'2041'
X'2050'

X'2051'
X'2052'
X'20AO'

X '20A1'

X'20A2'

X'20A3'
X'20A4'

X'20A5'

X'20A6'

X'20A7'

8-76

SNA Formats

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.
REMOTE DCE LOOP: The DCE loop remote from the error
notification sender.
DDS NETWORK: A network implementing the Digital Data
Services, e.g., the DATAPHONE 1 Digital Service (DDS).
1 DATAPHONE is the Registered Service Mark of AT&T
Company.
INTER-EXCHANGE NETWORK: A network providing services between two local exchange areas
PRIVATE NETWORK REACHED: The private network containing the called DTE
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.
ISDN NETWORK HAS INITIATED A TEST LOOP
X.25 NETWORK HAS INITIATED A TEST LOOP
NO RESPONSE FROM THE X.21 NETWORK - (sf82 qualifier) EXPI RED
Note: The qualifier specifies the X.21 timer that has
expired.
NO RESPONSE FROM THE ISDN NETWORK - (sf82 qualifier) EXPIRED
Note: The qualifier specifies the ISDN timer that has
expired.
OSI PROTOCOL ERROR (sf82 qualifier)
Note: The qualifier specifies the protocol code that
defines the error condition which has occurred.
SNA COMMUNICATIONS ERROR (sf82 qualifier)
NO RESPONSE FROM THE X.25 NETWORK - (sf82 qualifier) EXPIRED
Note: The qualifier specifies the X.25 timer that has
expired.
NO RESPONSE FROM THE X.25 NETWORK - (sf82 qualifier) RETRY COUNT EXPIRED
Note: The qualifier specifies the X.25 timer for which the
retry count has expired.
(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.
(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.

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content
X 120A8 1

X '20B1 1

X 120B21
X ' 20C1 1

X '20C2 1

X '20C3 1

X ' 20C4 1

X '20CS'

(sf82 qualifier) INBOUND LINE: The equipment that connects the receive circuits of the local DCE (Le., 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.2S COMMUNICATIONS ERROR - THE FOLLOWING
DIAGNOSTIC PACKET WAS RECEIVED FROM THE
NETWORK (sf82 qualifier)
Note: The qualifier specifies the diagnostic code.
X.2S PROTOCOL VIOLATION DETECTED (sf82 qualifier)
Note: The qualifier specifies the diagnostic code.
X.2S 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'"23C1 1.
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 error is detected after end-to-end LLC communication has been established. Contrast with code point
X ' 23C2 1.
X.2S COMMUNICATIONS ERROR - THE FOLLOWING
DIAGNOSTIC PACKET WAS RECEIVED FROM THE
NETWORK (sf82 qualifier) (sf82 qualifier)
Note: The first qualifier specifies the diagnostic code and
the second qualifier specifies the diagnostic explanation.
X.2S COMMUNICATIONS ERROR - THE FOLLOWING INDICATION PACKET WAS SENT BY THE NETWORK (sf82
qualifier) (sf82 qualifier)
Note: The first qualifier specifies the packet type (reset,
restart, or clear) and cause code and the second qualifier
specifies the diagnostic code.
X.2S COMMUNICATIONS ERROR - THE NETWORK
RECEIVED THE FOLLOWING REQUEST PACKET FROM
THE DTE (sf82 qualifier) (sf82 qualifier)
Note: The first qualifier specifies the packet type (reset,
restart, or clear) and cause code and the second qualifier
specifies the diagnostic code.

Chapter 8. Common Fields

8-77

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfleld
Byte

Bit

Content
X 12001 1

X ' 2100 '

COMMUNICATIONS/REMOTE NODE: Either a communication facility
denoted by a X '20xx 1 code point or a remote node denoted by a
X '22xx 1 code point
Note: This code point is used only when a more specific probable
cause cannot be determined.
X ' 2101 1
X ' 2102 1
X'2104 1
X ' 2107 1
X'210A 1

X ' 2200 '

X 12203 1

X ' 2204 1

X '22AO 1

X 12308 1
X ' 2309 1
X ' 230A'

SNA Formats

CALLED DTE
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.21.
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.
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.
REMOTE NODE (sf82 qualifier)

CONNECTION NOT ESTABLISHED: A telephone connection required
for the requested operation has not been established
X 12306 1
X ' 2307 1

8-78

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

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 12201 1
X 12202 1

X ' 2300 '

NO RESPONSE FROM THE X.2S NETWORK - (sf82 qualifier) EXPIRED (sf82 qualifier) (sf82 qualifier)
Note: The first qualifier specifies the timer. The second
qualifier specifies the retry count and the third qualifier
specifies the timer setting.

NEW TELEPHONE NUMBER ASSIGNED TO CALLED DTE
CALLED NUMBER OUTSIDE OF NUMBERING PLAN OR
UNKNOWN BY THE NETWORK
ACCESS BARRED: The calling DTE is not allowed to
connect to the called DTE
SPEED CLASSES INCOMPATIBLE: The called DTE is
operating at a different speed from the calling DTE
USER CLASSES OF SERVICE INCOMPATIBLE: The user
class of service of the called DTE is incompatible with that
of the calling DTE

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfleld
Byte

Bit

Content

X ' 23C1 1

X ' 23C2 1

X.2S 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 ' 20C1 1.
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 1.

X 12600 1

INTERFERENCE: An electric disturbance in a communication system
that interferes with or prevents reception of a signal or of information

X 13000 1

CHANNEL FAI LURE: 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 ' 3110 '

X ' 3111 1

X ' 3121 1
X 13200 1

COMMUNICATION CONTROLLER BACK-UP: A process
which switches resources from one processor to a
back-up processor in a communication controller.
Note: This code point is used to notify the network operator about a maintenance procedure that was invoked
locally or initiated automatically which results in the availability of additional resources.
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.
TERMINAL CONTROL UNIT: A communication device that
controls the transmission of data to and from terminals.

COMMUNICATIONS INTERFACE: The equipment connecting a node
to the component in a link connection with which it exchanges physical control signals
X ' 3220 '
X ' 3221 1

LOCAL TOKEN-RING ADAPTER INTERFACE: The programming interface for the local token-ring adapter
CSMA/CD ADAPTER INTERFACE: The programming interface for the local CSMA/CD adapter
Chapter 8. Common Fields

8-79

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content
X' 3201'

X'32D2'

X' 3203'

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'3305'
X'3306'
X'3307'
X'3309'
X'330A'
X'330B'
X'330C'
X'330D'
X'330E'
X '330F'
X'3310'

8-80

SNA Formats

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.
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.
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
Note: The qualifiers identify the standards, protocols, etc.
that characterize the interface, e.g., RS-232C, 1200 BPS,
V.24.

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
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.

MS Major Vectors

F~iluro C~uscs

Byte

(X' 01') Failure Causes Subfield

Bit

Content
X ' 3311 1

X ' 3320 '
X ' 3321 1
X ' 3322 1
X ' 3323 1
X ' 3324 1
X ' 3325 1
X ' 3326 1
X 133271
X ' 33AO'

X ' 33CO'

X ' 33C1 1

X ' 33C2 1

X ' 33C3 1

X ' 3400 '

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 13533 1 REMOTE ISDN TERMINAL ADAPTER.
LOCAL TOKEN-RING ADAPTER: An adapter that attaches
the Alert sender to a token-ring LAN
REMOTE TOKEN-RING ADAPTER: An adapter that
attaches a node other than the Alert sender to a tokenring LAN
LOCAL CSMA/CD ADAPTER: An adapter that attaches
the Alert sender to a CSMA/CD LAN
REMOTE CSMA/CD ADAPTER: An adapter that attaches a
node other than the Alert sender to a CSMA/CD LAN
TOKEN-RING ADAPTER: An adapter that attaches a node
to a token-ring LAN
CSMA/CD ADAPTER: An adapter that attaches a node to
a CSMAlCD LAN
TOKEN BUS ADAPTER
DEFECTIVE TRANSMITTER
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.
LINE ADAPTER (sf82 qualifier) (sf82 qualifier): 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.
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.
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.
LINE INTERFACE COUPLER (LlC) (sf82 qualifier) (sf82 qualifier)
Note: The qualifiers identify the line address and the LlC
position for the failing LlC.

CABLE LOOSE OR DEFECTIVE: A cable or its connectors used to
electrically connect devices together is loose or defective
X 13401'

LOCAL DCE INTERFACE CABLE: The cable, or its connectors, between the Alert sender and the local Data CircuitTerminating Equipment (DCE)

Chapter 8. Common Fields

8-81

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content
X'3403'

X'3404'

X'3411'

X'3426'

X'3434'
X'3435'
X'3436'
X'3441'
X'3451'
X'3452'
X'3460'
X'3461'
X'3480'
X'34AO'

X'34A1'

X'3500'

8-82

SNA Formats

REMOTE DCE INTERFACE CABLE: The cable, or its connectors, between the Alert sender's remote DCE and the
device attached to it.
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.
CHANNEL INTERFACE CABLE: The cable or cables, or
their connectors, between a channel and a loca"y
attached device
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
LOCAL LOBE CABLES: The cables between the reporting
node and its access unit on a token-ring LAN
REMOTE LOBE CABLES: The cables between a remote
node and its access unit on a token-ring LAN
LOCAL CSMA/CD ADAPTER CABLE: The cable attaching
the Alert sender to the CSMA/CD bus
LOOP CABLE: A cable connecting the nodes attached to
a communication loop
DEVICE CABLE: A cable connecting a device directly to a
communication controller or a control unit
STORAGE DEVICE CABLE: A cable directly connecting a
local storage device to its adapter/controller
INTERNAL CABLE
LINE ADAPTER MULTIPLEXER CABLE
TWINAXIAL CABLE DISTRIBUTION ASSEMBLY
(sf82 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 (LSL)
on which the DCE belongs.
(sf82 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 (LSL)
on which the DCE belongs.

MS Major Vectors

Failure Causes (i\' 01 ') Failure Causes Subfield
Byte

Bit

Content
X'3501'

X'3502'
X'3503'

X'3504'

X'3506'

X'3507'

X'3510'
X'3511'
X'3512'
X'3513'
X'3520'
X'3521'
X'3522'
X'3530'
X'3531'

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 (X.25 Pad).
TERMINAL MULTIPLEXER: The equipment used to
connect multiple devices to a single cable
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).
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 (Le., EIA-366/CCITT V.25).
LOCAL DIGITAL DATA DEVICE: On a particular link
segment, the digital data device (DOD) nearer to the Alert
sender
REMOTE DIGITAL DATA DEVICE: On a particular link
segment, the digital data device (DOD) farther from the
Alert sender
CALLED DCE
LINE: The telephone line or transmission link connecting
two or more components in the network
THE CONNECTION BETWEEN THE CALLING DCE AND ITS
LOCAL DSE
LOCAL LOOP ASSOCIATED WITH THE CALLED DTE
X.21 NETWORK COMPONENT
TEMPORARY LACK OF RESOURCES IN THE X.21
NETWORK
LONG-TERM LACK OF RESOURCES IN THE X.21
NETWORK
ISDN NETWORK COMPONENT
ISDN NETWORK TERMINATION (NT1): 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

Chapter 8. Common Fields

8-83

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfleld
Byte

Bit

Content
X 135321

X 13533 I

X ' 3534 1
X 13535 I
X 135411

X 135421

X ' 3550 '
X ' 3551 1
X ' 3552 1
X '35AO I

X '35A11

X '35A2 I

X '35A3 1

8-84

SNA Formats

LOCAL ISDN TERMINAL ADAPTER: The terminal adapter
local to the Alert sender
Note: See also code pOint X 13310 I 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.
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 133111 REMOTE ISDN
ADAPTER.
TEMPORARY LACK OF RESOURCES IN THE ISDN
NETWORK
LONG-TERM LACK OF RESOURCES IN THE ISDN
NETWORK
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
DDD; see code points X 13506 I and X 136011.
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 1 arid X ' 3603 1.
X.25 NETWORK COMPONENT
SHORT-TERM CONGESTION IN THE X.25 NETWORK
LONG-TERM CONGESTION IN THE X.25 NETWORK
(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.
(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.
(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.
(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.

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfleld
Byte

Bit

Content
X '3600'

MODEM: A device or functional unit that modulates and demodulates signals transmitted over data communication facilities
X '3601'
X '3602'

X '3603 1
X '3604'

X '3621'

X '36AO'

X '36A1'

X '36A2'

X '36A3'

X I 3700 1

LOCAL MODEM: The modem connected to the error
notification sender
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
REMOTE MODEM: The modem remote from the error
notification sender
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
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.
(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.
(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.
(sf82 qualifier) LOCAL MODEM FEATURE(S)
Note: The qualifier identifies the link segment level (LSL)
on which the modem belongs.
(sf82 qualifier) REMOTE MODEM FEATURE(S)
Note: The qualifier identifies the link segment level (LSL)
on which the modem belongs.

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 replacement code points under X 13700 I, with the
exception of the LAN cable, which falls under CABLE LOOSE OR
DEFECTIVE (X 13400 I). and the LAN adapters, which fall under
ADAPTER (X I 3300 1).
X 13701'

TOKEN-RING LAN COMPONENT

Chapter 8. Common Fields

8-85

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content

X ' 3703 1

X ' 3706 1
X ' 3707 1
X ' 370C'

X 137111

X ' 3712 1
X ' 3713 1
X ' 3721 1
X ' 3722 1

X 137411

X 15000 I

MEDIA: A tape, disk, diskette, or paper (or other data medium) that
is required to read data from or write data on
X 150011

X 150021

X 15003 1

X ' 5200 '

SNA Formats

DASD MEDIA: The medium used in a direct access
storage device; it may be either removable or nonremovable
DISKETTE: A thin, flexible magnetic disk in a semi-rigid
protective jacket, in which the disk is permanently
enclosed; also termed a floppy diskette
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

MEDIA JAM: The medium (usually paper, forms or cards) is jammed
in the machine and operator action is required to correct the
problem.
X'5201 1
X ' 5202 1
)(15203 1
X ' 5204 1

8-86

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
OPTICAL FIBER CONVERTER: A device which converts
electrical signals into optical signals and vice-versa
TOKEN-RING LAN CABLES
INVALID SYMBOL RECEIVED FROM MAC: The physical
layer transmits symbols presented to it by the medium
access control (MAC) sublayer entity. This fault is issued
when the physical layer cannot encode one of the MAC
symbols as specified in the IEEE 802.4 standard.
LOCAL ACCESS UNIT: The access unit by which the Alert
sender is attached to a token-ring LAN
Note: An access unit is an active or passive wiring
concentrator on a token-ring LAN.
LOCAL TOKEN-RING LOBE: A token-ring lobe attaching
the Alert sender to a token-ring
REMOTE ACCESS UNIT: An access unit by which a node
other than the Alert sender is attached to a token-ring
LAN
CSMA/CD LAN COMPONENT
CSMAlCD 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
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

CARD JAM
FORMS JAM
PAPER JAM
FILM JAM

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfleld
Byte

Bit

Content
X 16000 I

DEVICE: An input, output, or input/output device (e.g., a terminal or
disk drive)

X I 6100 1

INPUT DEVICE: A device that is used to enter data into a system
X 16110 I

X 161111

X '6112 I
X 16113 I
X I 6114 1
X 16115 I

X '6200'

OUTPUT DEVICE: A device that receives data from a system
X 16210 I

X 162111
X 162121
X 16213 1

X 16220 I
X I 6300 1

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
KEYPAD: A specialized keyboard with an arrangement of
a limited number of alphanumeric, special character,
and/or function keys
SELECTOR PEN: A light-sensitive pen used in display
operations
MICR READER/SORTER: A magnetic ink character recognition reader/sorter
MAGNETIC STRIPE READER (MSR): A device that reads
data from a card containing a magnetic stripe
ID CARD READER: An Identification Card Reader (lCR) is
a device which can read data from or write data to a magnetic stripe or an electronic chip on a consumer's identification card.

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 16213 1 PLOTTER.
COPIER: An output device that produces one or more
copies of an original without affecting the original
CAMERA: An output device that combines electronic data
with a visual image on a single visual medium
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 '6210 I PRINTER.
PRINTER CASSETTE: A removable container for feeding
paper to a printer

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 163011

X '6302 1

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
DISPLAY: A workstation that requires a host connection
in order to function; typically a display includes both a
monitor and a keyboard

Chapter 8. Common Fields

8-87

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subfield
Byte

Bit

Content

X' 6309'
X '6310'

X '6311'

X'6312'

X'6313'

X '6314'

X '6315'
X '6317'

X'6330'
X'6350'
X '6351'

X '6400'

DEPOSITORY: A device that receives items into a system
X '6401'

X '6402'

X '6403'
X'6500'

X'6502'
X' 6503'
X'6504'

SNA Formats

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
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
CARD DEPOSITORY: A device that retains credit, personal banking. or other cards used to access a PBM

DISPENSER: A device that dispenses items to a user of a system
X '6501'

8-88

STORAGE DEVICE: The device cannot be specifically
identified as disk, tape, optical, etc.
DISK DRIVE: The primarily mechanical component of a
DASD device, directly involved with transferring data to
and from the medium
DISKETTE DRIVE: The primarily mechanical component of
a diskette device, directly involved with transferring data
to and from the medium
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
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
TAPE DRIVE: The primarily mechanical component of a
tape drive, directly involved with transferring data to and
from the medium
CONSOLE: A terminal used for communication between
an operator and a processor
MAGNETIC STRI PE READER/ENCODER: A device that
reads data from, and in some cases writes data to, a card
containing a magnetic stripe
DISK DRIVE ELECTRONICS: The electronic components of
a DASD device
LOCAL CONSOLE
REMOTE CONSOLE
Note: "Local" and "remote" are defined with respect to
the system with which the console communicates.

DOCUMENT DISPENSER: A device that dispenses documents, primarily bills
TICKET DISPENSER
KEY DIS PENSER
COIN DISPENSER

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfield
Byte

Bit

Content
X 16600 1

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 1
X 16630 1

X ' 6700 '

SECURITY PROBLEM
X 167011
X 167021

X'EOOO' -X'EFFF'

AUDIBLE ALARM: A device which emits an audible sound
PROTECTIVE DOOR: An electronically or mechanically
operated covering for access to a device.
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.
XI FOOO 1

(no display): Additional message data
X'F001'
X'F002 1
X'F003 1
X'FOOA'
X'FOOC'
X'FOOD'
X'FOOE'
X'FOOF'
X'F010 '
X'F011 1
X'F012 1
X'F013'
X'F014 1
X'F015'
X'F016 1
X'F017'
X'F018'
XI F019 1
X' F01A'

UNSOLICITED INTERRUPT RECEIVED
DATA LOST DURING RESTORE TO DISK
IPL OCCURRED DUE TO A HARD WAIT
RETRY LIMIT REACHED
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
OM RECEIVED
Chapter 8. Common Fields

8-89

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfield
Byte

Bit

Content
X'F01B'
X'F01C'
X' F01 0'
X' F01E'
X'F01F'
X'F020'
X' F021 ,
X' F022'
X' F023 ,
X'F030'
X' F031 ,
X' F032 ,
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'F042'
X' F043 ,
X' F044 ,
X' F050'
X'F051'
X'F052'
X' F053'
X' F054'
X'F055'
X'F056'
X'F057'
X' F058 ,
X'F059'
X'F05A'
X' F05B'

8-90

SNA Formats

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 INITIALLY 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
PERSISTENT DCE CONTROLLED NOT READY DURING
CALL ESTABLISHMENT (T6 TIMER EXPIRED)
DCE FAULT CONDITION DURING CALL ESTABLISHMENT
DCE CLEAR INDICATION RECEIVED DURING DATA PHASE
PERSISTENT DCE CLEAR INDICATION RECEIVED DURING
DATA PHASE (T6 TIMER EXPIRED)
UNRECOGNIZED CALL PROGRESS SIGNAL RECEIVED
FROM THE NETWORK
INVALID CALL PROGRESS SIGNAL RECEIVED FROM THE
NETWORK
DSR OR CTS DROPPED
FAN-OUT FEATURE IN ERROR

MS Major Vectors

Failure Causes (X' 0'1') Failure Causes Subiield
Byte

Bit

Content
XIF060 '
XIF061 '
XIF062 '
X I F063 '
XIF064 '
XIF065 '
XIF066 '
XIF067 '
XIF06B'
XIF069 '
XIF06A'
XIF06B'
XIF06C'
XIFOA1'
XIFOA2 '
XIFOA3 '

XIFOA4 '

XIFOA5 '

XIFOA6 '

XIFOA7 '

X'FOAB'

XIFOA9 '

X'FOAA'

X'FOAB'

DATA BLOCKS IN ERROR THRESHOLD REACHED
TTD'S TRANSMITTED THRESHOLD REACHED
WACK'S TRANSMITTED THRESHOLD REACHED
SYNC TIMEOUT THRESHOLD REACHED
CONTINUOUS SYNC TIMEOUT RETRY LIMIT REACHED
NO SYNC RECEIVED TIMEOUT RETRY LIMIT REACHED
NO DATA RECEIVED TIMEOUT RETRY LIMIT REACHED
INVALID RESPONSE TO TTD RETRY LIMIT REACHED
INVALID RESPONSE TO WACK RETRY LIMIT REACHED
TTD/WACK NO RESPONSE TIMEOUT RETRY LIMIT
REACHED
TRANSMIT RETRY LIMIT REACHED
ENQ RECEIVED TO ACK SENT RETRY LIMIT REACHED
UNRECOGNIZABLE DATA RECEIVED RETRY LIMIT
REACHED
ERROR OCCURRED READING FROM FILE (sfB2 qualifier)
ERROR OCCURRED WRITING TO FILE (sfB2 qualifier)
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., the failing communication control
unit in a communication controller.
XID NEGOTIATION FAILED WITH (sfB2 qualifier)
Note: The qualifier specifies the SNA sense data identifying why the negotiation failed.
COMPONENT OF (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the eqUipment or service belongs.
BAD LINE QUALITY ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the line belongs.
BOTH MODEMS DETECTED IMPULSE HITS ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the impulse hits were detected.
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.
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.
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.
NO LPDA RESPONSE FROM THE REMOTE DSU/CSU ON
(sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
Chapter 8. Common Fields

8-91

MS Major Vectors

Failure Causes (X' 01') Failure Causes Subfield
Byte

Bit

Content
X' FOAC I

X I FOAD I

X I FOAE I

X'FOAF'

X'FOBO'

X'FOB1

X'FOB2 1

X I FOB3 1

X I FOB4 1

X I FOBS I

X I FOB6 I

X I FOB7 1

X I FOBB'

8-92

SNA Formats

INCORRECT 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.
INCORRECT LPDA RESPONSE FROM THE REMOTE
DSU/CSU ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
BIPOLAR ERRORS DETECTED BY LOCAL DSU/CSU ON
(sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the local DSU/CSU belongs.
BIPOLAR ERRORS DETECTED BY REMOTE DSU/CSU ON
(sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the remote DSU/CSU belongs.
IMPULSE HITS DETECTED BY THE LOCAL MODEM ON
(sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the hits were detected.
LOCAL DSU/CSU DETECTED REMOTE DSU/CSU FAILURE
ALARM ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
LOCAL MODEM DETECTED REMOTE MODEM FAILURE
TONE ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
MODEMS ON (sfB2 qualifier) IN BACKUP SPEED
Note: The qualifier identifies the link segment level (LSL)
on which the modems belong.
(sfB2 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.
(sfB2 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.
(sfB2 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.
(sfB2 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.
(sfB2 qualifier) LOCAL DSU/CSU DETECTED DDS
NETWORK LOOPBACK ACTIVE
Note: The qualifier identifies the link segment level (LSL)
on which the DSU/CSU belongs.

MS Major Vectors

Failure Causes (X' 01 ') Failure Causes Subiield
Byte

Bit

Content
X I FOB9 1

X I FOBA I

X I FOBB I

X I FBDO I

(sfB2 qualifier) REMOTE DSU/CSU DETECTED DDS
NETWORK LOOPBACK ACTIVE
Note: The qualifier identifies the link segment level (LSL)
on which the DSU/CSU belongs.
INCORRECT LPDA RESPONSE FROM THE LOCAL MODEM
ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the local modem belongs.
INCORRECT LPDA RESPONSE FROM THE REMOTE
MODEM ON (sfB2 qualifier)
Note: The qualifier identifies the link segment level (LSL)
on which the remote modem belongs.

(no display): Additional message data
Note: The X I FBxx I range is used for additional messages that are
identical for User, Install, and Failure Causes.
XI FBCO'

X I FBDO I

FAILING COMPONENT IS IDENTIFIED BY (sfB2 qualifier)
(sfB2 qualifier)
Note: The qualifiers identify the failing component by
means of its logical location, e.g., its port number and
device address.
PROBLEM IS RELATED TO THE CONTROLLER LOCATED
AT (sfB2 qualifier) (sfB2 qualifier) (sfB2 qualifier)
Note: The qualifiers identify the controller location as
follows:
Q1
Q2
Q3

X'FBEO'
X I FFFF I

= RACK

= UNIT (within a rack)

= CARD SLOT (within a unit)

FAILING COMPONENT IS IDENTIFIED BY (sfB3 product
text)

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.

Cause Undetermined (X'97') Alert MS Subvector
Byte

Bit

Content
Length (p + 1), in binary, of the Cause Undetermined subvector

Chapter 8. Common Fields

8-93

MS Major Vectors

Cause Undetermined (X' 97') Alert MS Subvector
Byte

Bit

Content

Key: X'97'

2-p

One or more subfields containing recommended action data, as described in
"Network Alert (X'OOOO') Common Subfields" on page 8-97.
X '81'
Recommended Actions
X'82'
Detailed Data
Product Set ID Index
X '83'
Note: Subfields X' 01' and X '81 1 are always present. One or more instances of
the X '82 I and/or X '83' subfields may be present, depending on the code points
present in the X '81' subfield.

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

Detailed Data (X' 98') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Detailed Data subvector

Key: X'98'

2-p

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

Qualified Message Data (X'OI') 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.

Qualified Message Data (X' 01') Detailed Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Qualified Message Data subfield

Key: X'01'

8-94

SNA Formats

MS Major Vectors

Qualified Message Data (X' 01 ') Detailed Data Subfleld
Byte

Bit

2
0-3

5-7

Content
Product ID code: The structure of this field is identical to that present in the
Product Set 10 Index (X 183 1) subfield.
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 (XI111) MS Common Subvector" on page 8-175
for the criteria distinguishing hardware and software Product ID subvectors.
XIOI -X111
reserved
X ' 2 1 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 15 I 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.
Xigi
software product common name from a software Product ID subvector
Product set 10 indicator: An indication of which Product Set ID (PSID) contains
the Product 10 subvector being indexed
o Alert sender PSID
1
indicated resource PSID
Count: A 3-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 10 Subvector Code. If, for example, the code is X 12 I (specifying a
hardware Product ID) then only hardware X 1111 S are counted: a count of X 13 1
would thus index the third hardware Product ID within the PSID indicated by the
Product Set ID Indicator.

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'01 1 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.

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 100 I
hexadecimal: the message code is to be displayed as hexadecimal
digits
X I 11 1 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 I = "$" (dollar sign);
X' 7B' = "#" (pound or number sign); X '7C' = "@" (at sign)

Chapter 8. Common Fields

8-95

MS Major Vectors

Qualified Message Data (X' 01 ') Detailed Data Subfield
Byte

Bit

Content

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 '01' subfield, and are substituted into the message in the order in which the X '82' subfields are present.

6-q

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 1 A 11) are identical in function and
format except that this subvector contains EBCDIC codes. Note: The Detail
Qualifier (XIAOI-X'A1') subvectors are displayed in the order that they
appear in the Alert major vector.

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

Bit

Content

Length (p + 1), in binary, of the Detail Qualifier subvector

Key: X'AO'

2-p

Detail qualifier: a type-AE symbol-string that qualifies a reference on the Alert
Detail screen
Note: Each qualifier is p-1 bytes in length, but only one qualifier is 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 Qualifier (Hexadecimal) (X' A 1 ') 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 1 AO ') are identical in function and
format except that this subvector contains codes in hexadecimal. Note:
The Detail Qualifier (X 1AO 1 - X 1 A 1') subvectors are displayed in the order
that they appear in the Alert major vector.

8-96

SNA Formats

MS Major Vectors

Detail Qualifier (Hexadecimal) (X' A 1 ') Alert MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Detail Qualifier subvector

Key: XIA1 1

2-p

Detail qualifier: a type-G symbol-string

Network Alert (X'OOOO') Common Subfields
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 1811 Recommended Actions

X 182 1 Detailed Data

X 183 I 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 1811) Network Alert Common Subfield

This subfield contains code points for stored text describing recommended
actions to be taken to rectify an Alert condition.

Recommended Actions (X' 81 ') Network Alert Common Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Recommended Actions subfield

Key: X I 81

2-q

2-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 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 100 I represents a more general
description than a non-X 100 I; for this reason, the non-X 100 I codes are shown
indented, but any of the codes can be sent. The receiver displays the more
general text (corresponding to X 1* *00 I code points) if it does not recognize the
more specific code point (e.g., because of different release schedules).

Chapter 8. Common Fields

8-97

MS Major Vectors

Recommended Actions (X' 81 ') Network Alert Common Subfield
Byte

Bit

Content
The expression U(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 U(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 '11' subvector indicated by a Product Set ID Index (X '83')
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 recommended action code point indicates the number of
succeeding X '82' subfields that are associated with the code point. and
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'0001'
X '0002'
X '0003'
X'0004'
X'0005'
X '0006'
X'0007'
X'0008'
X'0009'
X'OOOA'
X'OOOB'
X'OOOC'
X'OOOD'
X'OOOE'

8·98

SNA Formats

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
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

MS Major Vectors

necommeiided Actions (X' 31') Networi< Aleri Common Subiield
Byte

Bit

Content
X'OOOF'

X1 0010 1
X1 0011 1
X' 0012 1
X' 0013 1
X' 0014 1
X' 0015 1
X' 0016 1
X' 0017 1
X'OOAO'

X100C1 1

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 INSTA
REVIEW MODEM AND LINE STATUS DATA
RUN VERIFY COMMAND
PERFORM TRANSMISSION LINE PROBLEM DETERMINATION PROCEDURES ON (sf82 qualifier)
Note: The qualifier identifies the failing transmission line.
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.
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.
RUN THE FOLLOWING AT THE REPORTING LOCATION
(sf82 qualifier)
Note: The qualifier identifies the command, program,
error recovery procedure, etc.
PERFORM (sf82 qualifier) PROBLEM DETERMINATION VIA
A REMOTE CONSOLE SESSION: Interactive product error
analysis is required.
Note: The qualifier identifies the scope the problem determination procedure is expected to be.
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.
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.
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.

Chapter 8. Common Fields

8-99

MS Major Vectors

Recommended Actions (X' 81 ') Network Alert Common Subfield
Byte

Bit

Content
X'00C3'

X'00C4'

X'OOCS'

X'00E1'
X'0100'

VERIFY
X'0101'
X'0102'
X'0103'
X'0104'
X'010S'
X'0106'
X'0107'
X'010B'
X'0109'
X'010A'
X'010B'
X'010C'
X '010D'
X'010F'
X'0110'
X'0111'
X'0112'
X'0113'
X'01CO'

8-100

SNA Formats

RUN SELF TEST WITH WRAP PLUG ON (sfB2 qualifier)
REMOTE DSU/CSU (FROM CONTROL PANEL) and (sfB2
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 multi-segment link with modems on one segment
and DSU/CSUs on the other segment.
RUN DSU/CSU AND LINE STATUS TEST ON (sfB2 qualifier)
AND (sfB2 qualifier)
Note: The qualifiers identify the link segment level (LSL)
on which the lines belong.
RUN DCE AND LINE STATUS TEST ON (sfB2 qualifier) AND
(sfB2 qualifier)
Note: The qualifiers identify the link segment level (LSL)
on which the lines belong.
PERFORM (sfB3 product text) PROBLEM DETERMINATION
PROCEDURES

VERIFY X.2S SUBSCRIPTION NUMBER
VERIFY ADAPTER ADDRESS DEFINITION
VERIFY 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
CHECK CONFIGURATION OF THE REMOTE NODE
CHECK CONFIGURATION OF THE OTHER REMOTE NODE
CHECK CONFIGURATION OF THE REMOTE NODE AND
REMOTE MODEM
CHECK RTS GENERATION PARAMETER
VERIFY THAT THE FAN-OUT FEATURE IS INSTALLED
VERIFY THAT REMOTE NODE PROVIDES THE DCE
EXTERNAL CLOCK
CHECK FOR CONFIGURATION MISMATCH BETWEEN THE
(sfB2 qualifier) REMOTE MODEM AND (sfB2 qualifier)
LOCAL MODEM
Note: The qualifiers identify the link segment level (LSL)
on which the modems belong.

MS Major Vectors

Recommended Actions (X' 31') Neb,.Juik Alert Common Subfleld

Byte

Bit

Content
X 101C1 1

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 This code point is
used on a multi-segment link with modems on one
segment and DSU/CSUs on the other segment.

XI 0200 1

CHECK POWER: Check the electrical power supply for the device

X 10300 1

CHECK FOR DAMAGE: Check for damage to the specified resource
X ' 0301 1
X 103021
X ' 0303 1
X ' 0306 1

X ' 0400 '

RUN APPROPRIATE TEST: Refer to the appropriate documentation
for this condition and run the tests specified for this problem
X ' 0401 1
X 10402 1
X ' 0403 1

X ' 0500 '

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

NO ACTION NECESSARY: For a given cause, no action is necessary,
e.g., the problem caused was transitory
X 107011

X l 1000 1

RUN COMMUNICATION LINE DATA TRACE

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 106011
X ' 0602 1
X ' 0603 1
X ' 0604 1
X ' 0605 1
X ' 0610 '
X ' 0611 1
X ' 0612 1
X ' 0613 1
X'0614 1

X ' 0700 '

RUN CONSOLE TEST
RUN CONSOLE LINK TEST
RUN MODEM TESTS

RUN APPROPRIATE TRACE: Refer to the appropriate documentation
for this condition and run the traces specified for this problem.
X ' 0501 1

X ' 0600 '

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

IF SNBU JUST DISCONNECTED THEN IGNORE

PERFORM PROBLEM RECOVERY PROCEDURES: Refer to the
problem recovery documentation provided for this condition and
follow the specified procedures

Chapter 8. Common Fields

8-101

MS Major Vectors

Recommended Actions (X' 81 ') Network Alert Common Subfleld
Byte

Bit

Content

X I 1001 1
X ' 1002 1
X ' 1003 1
X ' 1004 1
X ' 1005 1
X ' 1006 1
X ' 1007 1
X ' 100B'
X ' 1009 1
X ' 100A'
X'100B I
X I 100CI
X ' 100D'
X ' 100E'
X I 1010 1
X I 1011 1
X ' 1012 1
X ' 1013 1
X ' 1014 1
X ' 1015 1
X ' 1016 1
X ' 10A1 1

X ' 10A2 1

X ' 10A3 1

X ' 10A4 1

8-102

SNA Formats

REFER TO OPERATOR'S GUIDE FOR CORRECTIVE
ACTION
FOLLOW LOCAL BACKU P 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
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.
PERFORM (sfB2 qualifier)
Note: The qualifier specifies a problem recovery procedure to be performed.
FOLLOW PROBLEM RECOVERY PROCEDURE INDICATED
AT PRINTER FOR (sfB2 qualifier)
Note: The qualifier specifies a value that indexes a local
problem recovery procedure.
FOLLOW PROBLEM RECOVERY PROCEDURE INDICATED
AT PRINTER SERVER FOR (sfB2 qualifier)
Note: The qualifier specifies a value that indexes a local
problem recovery procedure.
FOR CORRECTIVE ACTION REFER TO (sfB2 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 (Le., the publication will never be translated and therefore the publica~
tion number will never be changed).

X I 1100 1

VARY OFFLINE

X ' 1200 '

RETRY

MS Major Vectors

Recommended Actions (X' 81') Network Alert Common Subfield
Byte

Bit

Content
X'1201'
X'1202'
X'1203'
X'1204'
X'1205'
X'1206'
X'12CO'

X '1300'

CORRECT THEN RETRY: The operator should correct the condition
referred to and retry the operation
X'1301'
X'1310'
X'1311'
X'1320'
X'1330'
X'1331'
X'1332'
X'13AO'

X'13A1'
X'13A2'
X '1400'

MOVE THE PAGING DATA SETS TO ANOTHER SUBSYSTEM
MOVE PACK TO ANOTHER DRIVE AND RERUN THE SAME
JOB
RESTART JOB
ATTEMPT TO REESTABLISH THE CONNECTION
RERUN THE APPLICATION PROGRAM
WAIT THEN RETRY
RETRY AFTER (sf82 qualifier) (sf82 qualifier)
Note: The two qualifiers indicate a date and time after
which the operation should be retried.

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.
ACTIVATE RESOURCES ATTACHED TO (sf82 qualifier)
DEACTIVATE RESOURCES ATTACHED TO (sf82 qualifier)

RESTART: Perform the appropriate restart operation on the indicated resou rce
X'1401'
X'1402'
X'1403'
X'1404'
X'1405'
X'1406'
X'1410'

X'14AO'

X'14A1'

RE-IML MOSS: Reload the MOSS microcode
RE-IPL THE COMMUNICATION CONTROLLER: Reload the
system software program in the communication controller
RE-IPL THE SECONDARY FINANCE CONTROLLER
RE-IML THE CONTROL UNIT
REACTIVATE LAN MANAGEMENT SERVER PROGRAM
FOLLOW ALERT SENDERS PROCEDURES FOR RESOURCE
ACTIVATION
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
VARY OR CONNECT (sf82 qualifier) ON-LINE: Start the
identified element via local target system control program
facilities.
Note: The qualifier identifies the target functional
element.
IML the (sf82 qualifier): Initialize the central processor
complex (CPC) or a resource within the CPC.
Note: The qualifier identifies the IML target element.

Chapter 8. Common Fields

8-103

MS Major Vectors

Recommended Actions (X' 81') Network Alert Common Subfield
Byte

Bit

Content
X '14A2 1

X '14DO 1

X 11500 '

CORRECT INSTALLATION PROBLEM: It will be necessary to correct
the installation error before continuing operation
X 11501 '
X 11502 '
X 11503 '
X 11504 '
X 11505 '
X 11506 '
X 11507 '
X 1150B'
X 11509 '
X'150A 1
X 1150B'
X 1150C'
X 1150D'
X'150E 1
X'150F 1
X 11510 '

X 11600 '

SNA Formats

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

REPLACE DEFECTIVE EQUIPMENT
X 11B01 '
X 11B02 '
X '1B03 1

8-104

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

REPLENISH SUPPLIES
X 11701 '
X 11702 '
X '1703 1
X 11704 '
X 11705 '
X '1706 1

X I 1BOO'

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
CORRECT THE ADDRESS

REPLACE MEDIA
X 11601 '
X 11602 '
X 11603 '
X 11604 '
X 11605 '
X ' 1606 '

X 11700 '

ACTIVATE (sfB2 qualifier): Issue the Activate command to
attempt to bring the target system on-line.
Note: The qualifier identifies the activation target.
IPL (sfB2 qualifier) FROM (sfB2 qualifier) WITH (sfB2 qualifier): Load the system control program.
Note: The first qualifier identifies the IPL target CPU. The
second qualifier identifies the IPL device address and the
third qualifier identifies an IPL parameter.

REPLACE KEYBOARD
REPLACE MODULE
REPLACE CARD

MS Major Vectors

Recommended Actions (X' 81 ') Network Alert Common Subfield
Byte

Bit

Content
X ' 1804 1
X ' 1805 1
X 11806 1
X ' 1807 1
X 11808 1
X 11811 1
X ' 1812 1
X 11813 1
X '18AO 1

X '18A1 1
X '18CO 1

X ' 1900 '

PERFORM PROBLEM BYPASS PROCEDURES: Refer to the problem
bypass documentation provided for this condition and follow the
specified procedures
X ' 1901 1
X ' 1902 1
X ' 1903 1
X ' 1904 1
X 11905 1
X 11 906 1
X 11 9AO 1

X'19A1'

X '2000'

REPLACE DEVICE
REPLACE BATTERY
REPLACE PRINTER
REPLACE DISPLAY CONTROL MODULE
REPLACE MSR OR MSRE: Replace the magnetic stripe
reader or magnetic stripe reader/encoder
REPLACE STORAGE CONTROLLER
REPLACE WORKSTATION CONTROLLER
REPLACE COMMUNICATIONS SUBSYSTEM CONTROLLER
REPLACE THE CARD IDENTIFIED BY (sf82 qualifier)
Note: The qualifier identifies the card to be replaced. e.g .•
by its part number.
REPLACE CABLE IDENTIFIED BY (sf82 qualifier)
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.

REPLACE MODEM
REPLACE DSU/CSU
CHANGE TO BACKUP SPEED
ACTIVATE SNBU. IF AVAILABLE
DISCONNECT AND RE-DIAL SNBU LINE
USE ALTERNATE PORT OR LINE
QUIESE AND MOVE THE (sf82 qualifier) WORKLOAD TO
ANOTHER SYSTEM: Move work to another equivalent
resource prior to imminent shutdown or until the resource
is restored.
Note: The qualifier identifies the system image name.
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.

(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 182 I) subvector either in
conjunction with this text or in another display that can be
reached from the display containing this text.
Chapter 8. Common Fields

8-105

MS Major Vectors

Recommended Actions (X' 81') Network Alert Common Subfield
Byte

Bit

Content
X 12002 1

X ' 2010 '

X 12011 1

X 12100 1

(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 12101 1

X 12200 1

X I 3002 1

SNA Formats

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 (Le., System
Message Log).

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 130011

8-106

(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.

REVIEW DATA LOGS: Review the specified records in one or more
data logs
X 12201 1
X I 2202 1
X I 2203 1
X 122CO 1

X ' 3000 '

(Review most recent traffic statistics): Report the information in the statistics subvectors kept for the link stations
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.
(Review link detailed data): Review the information that
was transported in those of the X '5x 1 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.
(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.

CONTACT CONSUMER SERVICE REPRESENTATIVE:
Contact the customer representative who is responsible
for dealing with consumer users of the device.
CONTACT SECURITY CONTROL REPRESENTATIVE:
Contact the customer representative who is responsible
for dealing with security concerns for the device.

MS Major Vectors

Rccomm~ndcd

Byte

Actions (X' 81')

Bit

NetVJOi~

Alert Common Subfield

Content
X '30AO'

X'30EO'

X'30E1'
X'3100'

CONTACT ADMINISTRATIVE PERSONNEL: Contact personnel with
administrative responsibility for one or more network resources
X'3101'
X'3102'
X'3103'
X'3104'
X'3105'
X'3106'
X'3107'
X'3110'
X'3120'
X'3121'
X'3122'
X'3123'
X'3124'

X '3200'

CONTACT TOKEN-RING ADMINISTRATOR RESPONSIBLE
FOR THIS LAN
CONTACT CSMA/CD ADMINISTRATOR RESPONSIBLE
FOR THIS LAN
CONTACT LAN ADMINISTRATOR RESPONSIBLE FOR THIS
LAN
CONTACT NETWORK INFORMATION SERVICE FOR
PRIVATE NETWORK CALLED
CONTACT X.21 NETWORK INFORMATION SERVICE
CONTACT ISDN NETWORK INFORMATION SERVICE
CONTACT X.25 NETWORK INFORMATION SERVICE
CONTACT COMMUNICATIONS SYSTEMS PROGRAMMER
CONTACT PRINTER OPERATOR
CONTACT TERMINAL CONTROL UNIT OPERATOR
CONTACT CALLED DTE'S OPERATOR
CONTACT REMOTE DTE'S OPERATOR
CONTACT PBM NETWORK OPERATOR: Contact the operator who has specific responsibility for controlling the' personal banking machine (PBM) network for the reporting
device.

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'
X'32CO'
X '32DO'

X'3300'

DIAL (sf82 qualifier) AND REPORT THE MACHINE INFORMATION: Hardware remote support was unable to contact
the service organization.
Note: The qualifier identifies a telephone number to call
for hardware service.
PROVIDE REMOTE SERVICE CALL AUTHORIZATION FOR
(sf83 product text): Hardware remote support requires
authorization to proceed with the automatic call for
service.
CONTACT SERVICE REPRESENTATIVE FOR (sf83 product
text)

REPORT THE FOLLOWING (sf82 qualifier)
REPORT THE FOLLOWING (sf82 qualifier) (sf82 qualifier)
REPORT THE FOLLOWING (sf82 qualifier) (sf82 qualifier)
(sf82 qualifier)

IF PROBLEM RECURS THEN DO THE FOLLOWING: After performing
the previous actions, try the operation again. If you experience
another problem, then perform the following actions
X'3301'

IF PROBLEM PERSISTS THEN DO THE FOLLOWING
Chapter 8. Common Fields

8-107

MS Major Vectors

Recommended Actions (X' 81') Network Alert Common Subfield
Byte

Bit

Content
X '3302'
X'3303'
X'3400'

WAIT FOR ADDITIONAL MESSAGE BEFORE TAKING ACTION: An
additional message will be forthcoming. indicating the action to be
taken
X '3401'

X'3500'

IF PROBLEM CONTINUES TO OCCUR REPEATEDLY THEN
DO THE FOLLOWING
IF UNSUCCESSFUL THEN DO THE FOLLOWING

EXPECT A CALL FROM THE SERVICE ORGANIZATION TO
PROVIDE AN ESTIMATED TIME OF ARRIVAL

REFER TO PRODUCT DOCUMENTATION FOR ADDITIONAL INFORMATION
X '35EO'

X'EOOO'-X'EFFF'

REFER TO (sf83 product text) PRODUCT DOCUMENTATION FOR ADDITIONAL INFORMATION
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. An Alert receiver
that displays only default text provides no display for these code points.
X' FOOO'

(no display): Additional message data
X'F001'
X'F002'
X'F003'
X'F004'
X'F005'
X' F006'
X'F007'
X'F008'
X'F009'
X'FOOA'
X'F011'
X' F012'
X'F013'
X'F014'
X'F050'
X'F051'
X'F052'

8-108

SNA Formats

MULTIPLE FAILURES INDICATE CHANNEL FAILURE
MULTIPLE FAILURES INDICATE CONTROLLER FAILURE
MULTIPLE DRIVE FAILURES ON SAME CONTROLLER
INDICATE CONTROLLER FAILURE
MULTIPLE FAILURES INDICATE CONTROL UNIT FAILURE
MULTIPLE FAILURES INDICATE TERMINAL MULTIPLEXER
FAILURE
RECURRENCE OF SAME ERROR INDICATES MEDIA
FAILURE
RECURRENCE OF PROBLEM INDICATES DEVICE OR
ATTACHMENT ERROR
RECURRENCE INDICATES MEDIA PROBLEM
NON RECURRENCE OF FAILURE INDICATES ORIGINAL
DRIVE FAILURE
MULTIPLE FAILURES INDICATE LINE ADAPTER
MULTIPLEXER FAILURE
NO FURTHER ACTION REQUIRED UNLESS PROBLEM
PERSISTS
THIS ALERT IDENTIFIES THE CAUSE OF A PREVIOUS
ERROR WHICH HAS BEEN RECOVERED
SERVICE CAN BE SCHEDULED AT A LATER TIME UNLESS
REPEATED FAILURES PREVENT NORMAL OPERATION
RESUME OPERATION
IPL CAPABILITIES LIMITED
NO IPL CAPABILITIES
NORMAL OPERATIONS CAN CONTINUE BUT IF AUXILIARY STORAGE IS EXHAUSTED ONSITE ACTION WI LL BE
NECESSARY

MS Major Vectors

Recommended Actions (X' 81') Network Alert Common Subfleld
Byte

Bit

Content

X' F060 1
X' FOAO 1
X'FODO'

TO RECOVER LOST RESOURCE
FOR (sf82 qualifier)
FAILING COMPONENT LOCATION (sf82 qualifier) (sf82
qualifier) (sf82 qualifier)
Note: The qualifiers identify the failing component
location in one of two ways:
Method 1:
Q1
Q2
Q3

= RACK

= UNIT (within

a rack)

= CARD SLOT (within a unit)

Method 2:

Q1
RACK/UNIT (with no delimiter between the rack
and unit numbers)
Q2 = CARD SLOT (within a unit)
Q3 = CABLE POSITION (on a card)

X' FOEO 1
XIFOE1 '
X' FFFF 1

Method 2 is used only in those cases where cable position on a card is meaningful.
FOR (sf83 product text)
PREPARE FOR AUTOMATIC SHUTDOWN OF (sf83 product
text)
Reserved

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

Detailed Data (X' 82') Network Alert Common Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Detailed Data subfield
X' 02 ' indicates that the Product 10 Code, Data 10, Data
Note: Length
Encoding, and Detailed Data fields are not present.

Key: X 1 82 '

Product 10 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 10 Index (X '83 ' ) subfield.

A value of X' 00 1 in this byte indicates that no product identification data is displayed in conjunction with the data type and detailed data.

Chapter 8. Common Fields

8-109

MS Major Vectors

Detailed Data (X' 82') Network Alert Common Subfleld
Byte

Bit

Content

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 1111) MS Common Subvector" on page 8-175
for the criteria distinguishing hardware and software Product ID subvectors.
XIOI -X111
reserved
X 12 I (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 151
(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 19 1 software product common name from a software Product ID subvector
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
Count: a 3-digit binary number that indicates which Product ID subvector, of the
type specified by the Product 10 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 12 I (specifying a
hardware Product ID), then only hardware X 1111 S are counted: a count of X 13 I
would thus index the third hardware Product ID within the PSID indicated by the
Product Set ID Indicator.

5-7

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:
XIOOI
(no display)
X 1011
ABEND CODE
X ' 02 1 ADAPTER CHECK STATUS
X ' 03 1 ADAPTER RETURN CODE
X ' 04 1 BOP CODE
X ' 05 1 PROTOCOL CODE
X ' 07 1 ERROR CODE
X ' 09 1 EVENT CODE
X'OA' LLC ERROR CODE
X'OB' MACHINE CHECK CODE
XIOCI MALFUNCTION CODE
X'OD' PROGRAM CHECK CODE
REASON CODE
X'OE'
RETURN CODE
X'OF'
X I 10 1 SENSE CODE
X I 11 1 SENSE DATA
X ' 12 1 SOFTWARE ERROR CODE
X ' 13 1 STATUS CODE
X ' 14 1 SYM PTOM CODE
X ' 15 1 SNA SENSE DATA

8-110

SNA Formats

MS Major Vectors

Detailed Data (X' 92') Network Alert Common Subileld
Byte

Bit

Content
X ' 16 1
X' 17 1
X ' 18 1

X' 1A'

X ' 1B'

XI 1CI

X ' 1D'

X ' 1E'
X ' 20 '
X ' 21 1
X ' 22 1
X ' 23 1
X ' 24 1
X ' 30 '
X ' 31 1
X ' 32 1
X ' 33 1
X ' 34 1
X ' 35 1
X ' 36 1
X ' 37 1
X ' 3A'
X ' 3B'
X ' 3C'
X ' 3D'
X ' 3E'
X ' 40 '
X ' 41 1
X ' 50 '
X ' 51 1
X ' 52 1
X ' 53 1
X ' 54 1
X ' 55 1
X ' 56 1

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.25 CLEAR PACKET, CAUSE CODE: A code to or from an X.25
network indicatin9 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.25 RESET PACKET, CAUSE CODE: A code to or from an X.25 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.25 RESTART PACKET, CAUSE CODE: A code to or from an X.25
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.25 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.
DIAGNOSTIC EXPLANATION
MESSAGE CODE
PANEL ERROR MESSAGE CODE
SYSTEM MESSAGE CODE
MESSAGE SEVERITY
WAIT STATE CODE
REFERENCE CODE
SYSTEM REFERENCE CODE
REPLACEABLE UNIT CODE
COMPONENT 10
COMMUNICATION CONTROL UNIT
TYPE
LOCATION
PART NUMBER
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
DTE ADDRESS CALLED

Chapter 8. Common Fields

8-111

MS Major Vectors

Detailed Data (X' 82') Network Alert Common Subfield
Byte

Bit

Content
X ' 57 1
X ' 58 1
X ' 60 '
X ' 61 1
X ' 62 1
X ' 63 1
X ' 64 1
X ' 65 1
X ' 661
X ' 67 1
X ' 68 1
X ' 70 '
X ' 71 1
X ' 72 1
X ' 73 1
X ' 74 1
X ' 7A'
X ' 7B'
X ' 7C'
X ' 7D'
X ' 7E'
X ' 7F'
X ' 80 '
X ' 81 1
X ' 82 1
X ' 83 1
X ' 84 1
X ' 85 1
X ' 86 1

X I 90 I
X ' 91 1
X ' 92 1
X ' 93 1
X I AO I
X'A1 1
X'A2 1
X'A3 1
X'A4 1
X'A5 1
X'A61
X I BO I
X'B1 1
X'B61

8-112

SNA Formats

DTE ADDRESS CALLING
LOCAL DTE ADDRESS
PORT NUMBER
ADAPTER NUMBER
CHANNEL ADAPTER NUMBER
LINE ADAPTER NUMBER
LINE INTERFACE COUPLER (LlC) POSITION
BUS NUMBER
TOKEN RING INTERFACE COUPLER NUMBER
LOCALLY-INITIATED LOGICAL CHANNEL
REMOTELY-INITIATED LOGICAL CHANNEL
GENERATION PARAMETER
THRESHOLD PARAMETER
CONFIGURATION 'OBJECT/RECORD: Identifies the configuration object
or record which contains one or more user settable parameters.
CONFIGURATION PARAMETER
IPL PARAMETER
CENTRAL PROCESSOR COMPLEX
CENTRAL PROCESSING UNIT: The CPU includes its associated vector
element processor.
LOGICAL PARTITION NAME
SUBCHANNEL NUMBER
CHANNEL PATH 10
I/O PROCESSING ELEMENT 10
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 Level 1, the one adjacent to it is Link Segment Level 2,
and so forth.
YEAR/MONTH/DA Y
TIME
JULIAN DATE
MINUTES
BYTE OFFSET
BIT OFFSET
DETECTING MODULE
FAILING MODULE
MAINTENANCE LEVEL
COMMAND
PROGRAM
EIA STANDARD
CCITT STANDARD
RETRY COUNT

MS Major Vectors

Detailed Data (X' 82') Network Alert Common Subfield
Byte

Bit

Content
X ' 87 1
X'B8 1
X'B9 1
X'BA'
X'DO'
X'D1 1
X'D2 1
X'D3 1
X'D4 1

TIMER SEETING
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
X'D5 1 CALLING TELEPHONE NUMBER
X'D6 1 TELEPHONE NUMBER CALLED
X'D7 1 REPORTING TELEPHONE NUMBER: The telephone number of the Alert
sender
X'D8 1 TIMER
X'D9 1 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.

Data Encoding: a code point indicating how the accompanying detailed data is
encoded, and, thus, how it is to be displayed. Defined code are:
XIOOI
hexadecimal: The data is to be displayed as hexadecimal digits.
X I 01 1 . 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 8'11111111' (X 1FF I) is to be displayed as 255.
X 1111
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 I
"$" (dollar sign):
X '7B 1
"#" (pound or number sign): X '7C I
u@" (at sign).
Note: Detailed data encoded in this way is limited to codes, numbers,
or internationally recognized terms that do not require translation.

5-q

Detailed data, encoded as specified in byte 4
Note: Maximum length of the detailed data is 44 bytes.

Chapter 8. Common Fields

8-113

MS Major Vectors

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

Product Set 10 Index (X' 83') Network Alert Common Subfield

Byte

Bit

Content

Length (q + 1), in binary, of the Product Set 10 Index subfield

Key: X l 83 1

2( =q)

0-3

8-114

SNA Formats

Product 10 code
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 '11') MS Common Subvector" on page 8-175
for the criteria distinguishing hardware and software Product 10 subvectors.
X 10' - X 111
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 is present; otherwise, the machine type is used.
X 13 1 serial number or repair 10 number, whichever is present, from a hardware Product 10 subvector
X I 4 1 (machine type or hardware product common name) plus serial number
or repair 10 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 151
(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 16 I
(machine type or hardware product common name) plus model number
plus serial number or repair 10 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 1 software product common name from a software Product 10 subvector
Product set 10 indicator: An indication of which Product Set 10 contains the
Product 10 subvector' being indexed
o Alert sender PSIO
1
indicated resource PSIO

MS Major Vectors

Product Set ID Index (j{' 83') Neiwork Aleti Common Subileld
Byte

Bit

Content

5 -7

Count: a 3-digit binary number that indicates which Product 10 subvector, of the
type specified by the Product 10 Subvector Code, is being indexed within the
PSIO specified by the Product Set 10 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' 21 (specifying a
hardware Product 10) then only hardware X 1111 S are counted: a count of X 13 1
would thus index the third hardware Product 10 within the PSIO indicated by the
Product Set 10 Indicator.

Request Change Control (X' 8050') MS Major Vector
LU -+ LU

This major vector is used to request that a change control function be performed.

Request Chan!]e Control (X' 8050') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1). in binary, of this MS major vector

2-3

Key: XI 8050 1

4-n

MS subvectors. as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X100I -X'7F', and in "Request
Change Control MS Subvectors" on page 8-116 for subvector keys
X ' 80 ' -X'FE'
Note: The following subvector keys may be used as indicated:

Chapter 8. Common Fields

8-115

MS Major Vectors

Presence in
Request Change Control
(X'80S0') Major Vector
Subvector

CP-MSU

Install (X'Sl')

Note 1

Remove (X'83')

Note 2

Accept (X'8S')

Note 3

Corequisite Change (X'S7')

Note 4

P
CP
On

Present one time
Conditionally present one time
(See notes for conditions.)
Optionally present one or more times

Notes:

1. This subvector is used to install changes. If this subvector is present, the
X 183 1 and X 185 1 subvectors are not present.

2. This subvector is used to remove changes. If this subvector is present, the
X 1811 and X 185 1 subvectors are not present.
3. This subvector is used to accept changes. If this subvector is present, the
X 1811 and X 183 1 subvectors are not present.
4. This subvector is used to name a corequisite change. It is optionally
present one to six times, but if present, the X1811 subvector must be
present.

Request Change Control MS Subvectors
Install (X' 81 ') Request Change Control MS Subvector

The Install subvector requests that a change be installed, and carries relevant parameters.

Install (X' 81') Request Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Install subvector

Key: X I 81

8·116

SNA Formats

MS Major Vectors

Install (X' 81') Request Change Control MS Subvector
Byte

Bit

2-p

Content

One or more subfields (listed by Key value below and described in detail following):
X ' 20 '
Removability
XI 30 1 Activation Use
X ' 40 '
Pre-Test
X ' 50 '
Automatic Removal
X ' 60 '
Post-Test
X170 1 Automatic Acceptance

Removability (X'20') Install Subfield
This subfield indicates the type of removability requested. It is present
once.

Removability (X' 20') Install Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Removability subfield

Key: X' 20 '

2{ =q)

Removability:
yes
desired
no

XI 10 1
X' 20 '
X' 30 '

Activation Use (X 130 1) Install Subfield
This subfield indicates which type of activation will cause components
altered by this change to be used. It is present once.

Activation Use (X'30') Install Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Activation Use subfield

Key: X ' 30 '

2{ =q)

Activation use:
X 110 1 trial- the altered components are used during trial activation (only),
instead of production versions
X ' 20 '
production -the altered components are used during any activation
unless superseded by trial versions
Chapter 8. Common Fields

8-117

MS Major Vectors

Pre-Test (X ' 40 ' ) Install Subfield
This subfield indicates the type of pre-test requested. It is present once.

Pre-Test (X'40') Install Subfleld
Byte

Bit

Content

Length (q + 1). in binary. of the Pre-Test subfield

Key: X ' 40 '

2( =q)

Pre-test:
X I 10 1 yes
X ' 20 '
desired
X ' 30 '
no

Automatic Removal (X ' 50 ' ) Install Subfield
This subfield indicates the type of automatic removal requested. It is
present once, unless removability is prohibited.

Automatic Removal (X' 50') Install Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the Automatic Removal subfield

Key: X ' 50 '

2( =q)

Automatic removal:
X I 10 1 yes
X ' 20 '
desired
X ' 30 '
no

Post-Test (X ' 60 ' ) Install Subfield
This subfield indicates the type of post-test requested. It is present once.

Post-Test (X'60') Install Subfleld
Byte

Bit

o
8-118

Content
Length (q + 1). in binary, of the Post-Test subfield

SNA Formats

MS Major Vectors

Post-Test (X' 60') Install Subfleld
Byte

Bit

Content

Key: X ' 60 '

2( =q)

Post-test:
X I 10 1 yes
X ' 20 '
desired
X ' 30 '
no

Automatic Acceptance (X 170 I) Install Subfield
This subfield indicates the type of automatic acceptance requested. It is
present once, unless removability is prohibited.

Automatic Acceptance (X' 70') Install Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Automatic Acceptance subfield

Key: X ' 70 '

2(=q)

Automatic acceptance:
X I 10 1 yes
X ' 20 '
desired
X ' 30 '
no

Remove (X' 83') Request Change Control MS Subvector
The Remove subvector requests that a change be removed, and carries relevant parameters.

Remove (X' 83') Request Change Control MS Subvector
Byte

Bit

Content
Length (p + 1), in binary, of the Remove subvector
Key: X ' 83 1

2-p

One subfield (listed by Key value below and described in detail following):
XI 60 1
Post-Test

Chapter 8. Common Fields

8-119

MS Major Vectors

Post-Test (X'60') Remove Subfield
This subfield indicates the type of post-test requested. It is present once.

Post·Test (X'60') Remove Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Post-Test subfield

Key: X'60'

2( =q)

Post-test:
X'10' yes
X'20' desired
X'30'
no

Accept (X' 85') Request Change Control MS Subvector
The Accept subvector re,quests that resources necessary to maintain
removability of a change be relinquished (immediately).

Accept (X' 85') Request Change Control MS Subvector
Byte

Bit

Content

Length (p + 1). in binary, of the Accept subvector

1( = p)

Key: X'85'

Corequisite Change (X'87') Request Change Control MS Subvector
This subvector identifies the SNA/File Services file name of a corequisite
change (a change that must be handled as part of the same process as that
required to handle the change file identified in the server object).

Corequisite Change (X' 87') Request Change Control MS Subvector
Byte

Bit

Content

Length (p + 1). in binary, of the Corequisite Change subvector

Key: X'8?'

8-120

SNA Formats

MS Major Vectors

Corequisite Change (X' 87') Request Change Control MS Subvector
Byte

Bit

2-p

Content
An SNA/File Services file name, as defined by SNA/File Services within the registered GDS code point X 11538 1 (does not include the LLiD for Data Object Identifier or the encapsulating LT for Token String, starts with the LT for First
. Identifier)

Change Control (X' 0050') MS Major Vector
LU -+ LU

This major vector is used to return the results of a change that was
requested by a focal point in a Request Change Control (X 18050 I) major
vector.

Change Control (X'0050') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1). in binary, of this MS major vector

2-3

Key: X 10050 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X ' 00'-X'7F'. and in "Change
Control MS Subvectors" on page 8-123 for subvector keys X ' 80 ' -X'FE'
Note: The following subvector keys may be used as indicated:

Chapter 8. Common Fields

8-121

MS Major Vectors

Presence in
Change Control
(X'0050') Major Vector
Subvector

CP-MSU

Date/Time (X'OI')

Reporting Installation (X'S2')

Note 1

Reporting Removal (X'S4')

Note 2

Reporting Acceptance (X'S6' )

Note 3

Reported Change Name (X 'SS')

CPn

Note 4

Reporting Secondary
Installation (X'SA')

Note 5

Secondary Installation
Change Name (X'SC')

CPn

Note 6

Reporting Back-Level
Status (X'SE')

Note 7

Back-Level Change Name (X'90')

CPn

Note S

Reporting Deletion (X'92')

Note 9

Deleted Change Name (X'94')

CPn

Note 10

Detailed Data (X'9S')

P
CP
CPn

o
On

Not present
Present one time
Conditionally present one time
Conditionally present more than one time
(See notes for conditions.)
Optionally present one time
Optionally present more than one time

Notes:

1. This subvector is used to report installation of changes. If this subvector is
present, the X J 84 J and X J 86 J subvectors are not present.
2. This subvector is used to report removal of changes. If this subvector is
present, the X J 82 J and X J 86 J subvectors are not present.
3. This subvector is used to report that a change was accepted. If this subvector is present, the X J 82 J and X J 84 J subvectors are not present.
4. This subvector is conditionally present one to seven times. At least one is
present if one of these subvectors is present: X J 82 J, X J 84 J, or X J 86 J. An
instance of this subvector is present for each change referred to in the
request.
5. This subvector is present if a change neither referred to in the request nor
one of its corequisites was installed as part of the operation being reported.
If it is present, then one or more Secondary Installation Change Name
(X J8E J) subvectors are present.

8-122

S NA Formats

MS Major Vectors

6. This subvector is conditionally present one to seven times. An instance of
this subvector is present for each change not referred to in the request, but
installed as part of the operation being reported.
7. This subvector is present if a change not referred to in the request was put
into back-level state as part of the operation being reported. If it is present,
then one or more Back-Level Change Name (X '90') subvectors are present.
8. This subvector is conditionally present one to seven times. An instance of
this subvector is present for each change not referred to in the request, but
put into back-level state as part of the operation being reported.
9. This subvector is present if a change not referred to in the request was
deleted as part of the operation being reported. If it is present, then one or
more Deleted Change Name (X '94') subvectors are present.
10. This subvector is conditionally present one to seven times. An instance of
this subvector is present for each change not referred to in the request, but
deleted as part of the operation being reported.

Change Control MS Subvectors
Reporting Installation (X' 82') Change Control MS Subvector
The Reporting Installation subvector reports the results of an Install request.

Reporting Installation (X'82') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Reporting Installation subvector

Key: X'82'

2-p

One or more subfields (listed by Key value below and described in detail following):
X '10'
Installation Status
X'20'
Removability Status
X '30'
Activation Use Status
X'40'
Pre-Test Status
X '50'
Automatic Removal Status
X '60 '
Post-Test Status
X '70'
Automatic Acceptance Status

Installation Status (X' 10') Reporting Installation Subfield
This subfield reports the results of an install. It is always present once.

Chapter 8. Common Fields

8-123

MS Major Vectors

I nstallation Status (X' 10') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Installation Status subfield

Key: X'10'

Status:
X '10'
successful
X'20'
attempted, but not successful
X '30'
not attempted and will not attempt

3( =q)

When effective:
X '10'
changed components are now in use
X '20'
components are changed, but activation is required
X '30'
not applicable (because install not attempted)

Removability Status (X '20') Reporting Installation Subfield
This subfield reports the removability status. It is present once.

Removability Status (X' 20') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Removability Status subfield

Key: X'20'

2( =q)

Status:
X '10'
X '20'
X '30'

installed removably
installed, but not removably
not installed

Activation Use Status (X '30') Install Subfield
This subfield indicates which type of activation will cause components
altered by this change to be used. It is present once.

Activation Use Status (X' 30') Install Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Activation Use subfield

Key: X'30'

8-124

SNA Formats

MS Major Vectors

Activation Use Status (X '30') Install Subfield
Byte

Bit

2( =q)

Content
Activation use:
X I 10 1
trial
X ' 20 '
production
X 130 1 installation was unsuccessful

Pre-Test Status (X 140 1) Reporting Installation Subfield
This subfield reports the results of a pre-test. It is present once if a pre-test
was required or desired.

Pre-Test Status (X '40') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Pre-Test Status subfield

Key: X ' 40 '

2( =q)

Status:
X 110 1 successful
X 120 1 not successful
X 130 1 not atte m pted

Automatic Removal Status (X ' 50 ' ) Reporting Installation Subfield
This subfield reports the results of an automatic removal. It is present once
if automatic removal was required or desired.

Automatic Removal Status (X' 50') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Automatic Removal Status subfield

Key: X ' 50 '

Status:
X 110 1 successful
X 120 1 not successful
X '30 1
not attempted

3{ =q)

When effective:
X 110 1 changed components are now in use
X 120 1 components are changed, but activation is required
X 130 1 not applicable

Chapter 8. Common Fields

8-125

MS Major Vectors

Post-Test Status (X'60') Reporting Installation Subfield
This subfield reports the results of a post-test. It is present once if a posttest was required or desired.

Post-Test Status (X'60') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Post-Test Status subfield

Key: X'60'

2( =q)

Status:
successful
X'10'
not successful
X'20'
not attempted
X'30'

Automatic Acceptance Status (X' 70') Reporting Installation Subfield
This subfield reports the results of an automatic acceptance. It is present
once if automatic acceptance was required or desired.

Automatic Acceptance Status (X' 70') Reporting Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Automatic Acceptance Status subfield

Key: X'70'

2( =q)

Status:
successful
X'10'
not successful
X'20'
not
attempted and will not attempt
X'30'

Reporting Removal (X' 84') Change Control MS Subvector
The Reporting Removal subvector reports the results of a Remove request.

Reporting Removal (X' 84') Change Control MS Subvector
Byte

Bit

Length (p + 1), in binary, of the Reporting Removal subvector

o
8-126

Content

SNA Formats

MS Major Vectors

ReporUng Removal (X' 84') Change Control MS Subvector
Byte

Bit

Content
Key: X ' 84 1

2-p

One or more subfields (listed by Key value below and described in detail following):
Removal Status
X I 10 1
X ' 60 '
Post-Test Status

Removal Status (XI101) Reporting Removal Subfield
This subfield reports the results of the removal. It is always present once.

Removal Status (X'10') Reporting Removal Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Removal Status subfield

Key: X 110 1

Status:
X 110 I
X ' 20 '

3( =q)

successful
not successful

When effective:
X 110 I
changed components are now in use
X 120 I
components are changed, but activation is required
X ' 30 '
not applicable

Post-Test Status (X 160 1) Reporting Removal Subfield
This subfield reports the results of a post-test. It is present once if a posttest was required or desired.

Post·Test Status (X'60') Reporting Removal Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Post-Test Status subfield

Key: X ' 60 '

2( =q)

Status:
X 110 I
X ' 20 '
X 130 I

successful
not successful
not attempted

Chapter 8. Common Fields

8-127

MS Major Vectors

Reporting Acceptance (X' 86') Change Control MS Subvector
This subvector reports the results of an Accept request.

Reporting Acceptance (X' 86') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Reporting Acceptance subvector

Key: X I 86 1

2-p

One subfield (listed by Key value below and described in detail following):
X 110 I
Accept Status

Accept Status (X 110 1) Reporting Acceptance Subfield
This subfield reports the results of an accept. It is always present once.

Accept Status (X'10') Reporting Acceptance Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Accept Status subfield

Key: X 110 1

2{ =q)

Status:
X 110 I
X I 20 1

successful
not successful

Reported Change Name (X' 88') Change Control MS Subvector
This subvector identifies the SNA/File Services file name of the change file
that is being reported on.

Reported Change Name (X' 88') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Reported Change Name subvector

Key: X'8BI

8-128

SNA Formats

MS Major Vectors

Reported Change Name (X' 88') Change Control MS Subvector
Byte

Bit

2-p

Reporting Secondary Installation (X' SA ') Change Control MS Subvector
The Reporting Secondary Installation subvector reports installation of a
change that resulted from a request referring to a different change.

Reporting Secondary Installation (X' SA') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Reporting Secondary Installation subvector

Key: X' 8A'

2-p

One or more subfields (listed by Key value below and described in detail following):
X I 10 1 Installation Status
X 130 1 Activation Use Status

Installation Status (X 110 1) Reporting Secondary Installation Subfield
This subfield reports the results of an install. It is always present once.

Installation Status (X '10') Reporting Secondary Installation Subfield
Byte

Bit

Content

Length (q + 1). in binary, of the Installation Status subfield

Key: X I 10 1

Status:
X 110 1 successful

3( =q)

When effective:
X 110 1 changed components are now in use
X 120 1 components are changed, but activation is required

Chapter 8. Common Fields

8-129

MS Major Vectors

Activation Use Status (X 130 1) Reporting Secondary Installation Subfield
This subfield indicates which type of activation will cause components
altered by this change to be used. It is present once.

Activation Use Status (X 130') Reporting Secondary Installation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Activation Use subfield

Key: X ' 30 '

2(=q)

Activation use:
trial
production

XI 10 1
X120 1

Secondary Installation Change Name (X I BC') Change Control MS Subvector

This subvector identifies the SNA/File Services file name of the change file
that is being reported on.

Secondary Installation Change Name (X' BC') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Secondary Installation Change Name subvector

Key: X ' 8C'

2-p

An SNA/File Services file name, as defined by SNA/File Services within the registered GDS code point X 11538 1 (does not include the LLiD for Data Object Identifier or the encapsulating LT for Token String, starts with the LT for First
Identifier)

Reporting Back-Level Status (X' BE ') Change Control MS Subvector

The Reporting Back-Level Status subvector reports that a change was put in
back-level state as the result of a request referring to a different change.

Reporting Back-Level Status (X' BE' ) Change Control MS Subvector
Byte

Bit

Content
/

Length (p + 1), in binary, of the Reporting Back-Level Status subvector

Key: X ' 8E'

8-130

SNA Formats

MS Major Vectors

Reporting Back-Level Status (X' BE ') Change Control MS Subvector
Byte

Bit

2-p

Content
One subfield (listed by Key value below and described in detail following):
X '10'
Back-Level Status

Back-Level Status (X '10')

~eporting

Back-Level Status Subfield

This subfield reports the back-level status. It is always present once.

Back-Level Status (X'10') Reporting Back-Level Status Subfleld
Byte

Bit

Content

Length (q + 1). in binary. of the Back-Level Status subfield

1{ =q)

Key: X'10'

Back-Level Change Name (X' 90') Change Control MS Subvector
This subvector identifies the SNA/File Services file name of the change file
that is being reported on.

Back-Level Change Name (X' 90') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1). in binary. of the Back-Level Change Name subvector

Key: X ' 90'

2-p

An SNA/File Services file name. as defined by SNA/File Services within the registered GDS code point X'1538' (does not include the LLiD for Data Object Identifier or the encapsulating LT for Token String. starts with the LT for First
Identifier)

Reporting Deletion (X' 92') Change Control MS Subvector
The Reporting Deletion subvector reports that a change was deleted as the
result of a request referring to a different change.

Chapter 8. Common Fields

8-131

MS Major Vectors

Reporting Deletion (X' 92') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Reporting Deletion subvector

Key: X ' 92 1

2-p

One subfield (listed by Key value below and described in detail following):
XI 10 1 Deletion Status

Deletion (X 110 I) Reporting Deletion Subfield
This subfield reports the deletion. It is always present once.

Deletion (X' 10 1 ) Reporting Deletion Subfield
Byte

Bit

Content

Length (q + 1), in binary" of the Deletion subfield

1( =q)

Key: XI 10 1

Deleted Change Name (X' 94') Change Control MS Subvector
This subvector identifies the SNA/File Services file name of the change file
that is being reported on.

Deleted Change Name (X'94') Change Control MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Deleted Change Name subvector

Key: X ' 94 1

2-p

Detailed Data (X' 98') Change Control MS Subvector
This subvector transports product-specific detailed data.
Note: The format of this subvector is defined under the Alert (X 10000 I) major
vector.

8-132

SNA Formats

MS Major Vectors

Execute Command (X' 8061 ') MS Major Vector
SSCP -+ PU
This major vector requests that the message it contains be interpreted and
executed as a command.

Execute Command (X' 8061 ') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X 180611

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X ' 00'-X'7F'.
Note: The following subvector keys may be used as indicated:

Presence in NMVT
Execute Corrmand
(X'8061') Major Vector

Subvector
Name List (X'06')

Self-Defining Text Msg (X'31')

Present one time

Reply to Execute Command (X' 0061 ') MS Major Vector
PU -+ SSCP
This major vector transports the reply provided in response to a previous
Execute Command. It is followed by a management services parameter
major vector except when it returns sense data.

Reply to Execute Command (X' 0061') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: XI 0061

Chapter 8. Common Fields

8-133

MS Major Vectors

Reply to Execute Command (X' 0061 ') MS Major Vector
Byte

Bit

4-n

Content
MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys XIOOI -X'7F'.
When the Sense Data (X '7D I) subvector is not present, this major vector is followed by one of the following management services parameter major vectors:
X ' 1300 '
X 11307 1
X 11309 1
Note: The

Text Data
Structured Data
Transparent Coded Datastream
following subvector keys may be used as indicated:

Presence in NMVT
Reply to Execute Command
(X'0061') Major Vector

Subvector
Sense Data (X'7D')

Note 1

Conditionally present one time (See Notes for
conditions.)

Notes:
1. This subvector is present only when sense data is returned to the
requesting application. When it is present, no MS parameter major vector
follows in the NMVT.

Analyze Status (X' 8062') MS Major Vector
SSCP

This major vector requests the gathering of information about one or more
listed resources, analysis of that information, and the return of the result in
a reply that reports the joint state of all indicated resources.

Analyze Status (X' 8062') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X ' 8062 1

4- n

MS subvector, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys XIOOI - X'7F'.
Note: The following subvector key is used as indicated:

8-134

SNA Formats

MS Major Vectors

Subvector

Presence in NMVT
Analyze Status
(X'8062') Major Vector

Name List (X'06')

Present one time

Reply to Analyze Status (X' 0062') MS Major Vector
PU -. SSCP
This major vector transports the reply to a previous Analyze Status request.
It is followed by management services parameter major vectors except
when it is used to return sense data.

Reply to Analyze Status (X' 0062') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1). in binary, of this MS major vector

2-3

Key: XI 0062 1

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors'! on page 8-165 for subvector keys X1001 - X'7F'.
When the Sense Data (X 170 I) subvector is not present. this major vector is followed by the following management services parameter major vectors. The
Begin Data Parameters (X '130A I) is used to begin the set, one Structured Data
(X 11307 1) is present for each resource included in the report, and the set is terminated with the End Parameter Data (X '130B I).
X ' 130A'
X 11307 1
x'130B'
Note: The

Begin Data Parameters
Structured Data (zero or more)
End Parameter Data
following subvector keys may be used as indicated:

Chapter 8. Common Fields

8-135

MS Major Vectors

Presence in NMVT
Reply to Analyze Status
(X'0062') Major Vector

Subvector
Sense Data (X '70')

Note 1

Conditionally present one time (See Notes for
conditions.)

Notes:
1. This subvector is present only when sense data is returned to the
requesting application. When it is present, no MS parameter major vectors
follow in the NMVT.

Query Resource Data (X' 8063') MS Major Vector
SSCP

--+

This major vector requests the gathering of information from one or more
resources and reporting of that information in a reply.

Query Resource Data (X' 8063') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary. of this MS major vector

2-3

Key: X' 8063 '

4-n

MS subvector, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X'OO' -X'7F'.
Note: The following subvector key is used as indicated:

Subvector
Name List (X'06')

8-136

SNA Formats

Present one time

Presence in NMVT
Query Resource Data
(X'8063') Major Vector
P

MS Major Vectors

Reply to Query Resource Data (X' 0063 ') MS Major Vector
PU --. SSCP
This major vector transports the reply to a previous Query Resource Data
request. It is followed by management services parameter major vectors
except when it is used to return sense data.

Reply to Query Resource Data (X' 0063') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X I 0063 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X'OO' -X'7F'.
When the Sense Data (XI7D') subvector is not present, this major vector is followed by the following management services parameter major vectors. The
Begin Data Parameters (X '130A ') is used to begin the set, one Structured Data
(X'1307 ' ) is present for each resource included in the report, and the set is terminated with the End Parameter Data (X '130B ').
X'130A I
X 1 1307 '
X ' 130B'

Begin Data Parameters
Structured Data (one or more)
End Parameter Data

At least one Structured Data (X '1307') major vector must be present between
the X ' 130A' and 130B' major vectors.
Note: The following subvector keys may be used as indicated:

Subvector
Sense Data (X'7D' )

Presence in NMVT
Reply to Query Resource Data
(X'0063') Major Vector
CP

Note 1

Conditionally present one time (See Notes for
conditions.)

Notes:
1. This subvector is present only when sense data is returned to the
requesting application. When it is present, no MS parameter major vectors
follow in the NMVT.

Chapter 8. Common Fields

8-137

MS Major Vectors

Test Resource (X' 8064') MS Major Vector
SSCP --. PU
This major vector requests the testing of one or more resources, the gathering of information from the test and provision of the results as a reply
which reports the state of each resource.

Test Resource (X' 8064') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X I 8063 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X1001 -X'7F', and in "Test
Resource Subvectors" for subvector keys X I 80 I - X I FF I.
Note: The following subvector keys are used as indicated:

Subvector

Presence in NMVT
Test Resource
(X'8064') Major Vector

Name List (X'06')

Test Setup Data (X'80')

Present one time

Test Resource Subvectors
Test Setup Data (X'80') Test Resource MS Subvector
This Test Resource subvector transports the details of the requested test to
be performed.

Test Setup Data (X'80') Test Resource MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Test Setup Data subvector

Key: X ' 80 '

8-138

SNA Formats

MS Major Vectors

Test Setup Data (X '80') Test Resource MS Subvector
Byte

Bit

2-p

Content
One subfield containing the number of times the test is to be executed
Note: The following subfield key is used as described in detail following:
X 1011
Test Request Count

Test Request Count (X 1011) Test Setup Data Subfield

This subfield transports the count of iterations requested for the test.

Test Request Count (X' 01') Test Setup Data Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the Test Request Count subfield

Key: X I 01

2-3( =q)

Test request count: an integer value from 1 to 32727. The receiver is requested
to repeat the identified test this many times or until a failure is detected.

Reply to Test Resource (X' 0064') MS Major Vector
PU --. SSCP
This major vector transports the reply to a previous Test Resource request.
It is followed by management services parameter major vectors except
when it returns sense data.

Reply to Test Resource (X' 0064') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X 10064 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys XIOOI -X'7F', and in "Reply to
Test Resource Subvectors" on page 8-140 for subvector keys X ' 80 ' -X'FF'.

Chapter 8. Common Fields

8-139

MS Major Vectors

Reply to Test Resource (X' 0064') MS Major Vector
Byte

Bit

Content
When the Sense Data (X '70 ') subvector is not present, this major vector is followed by the following management services parameter major vectors. The
Begin Data Parameters (X '130A I) is used to begin the set, one Structured Data
(X'13071) is present for each resource included in the report, and the set is terminated with the End Parameter Data (X ' 130B').

X' 130A'
X11307 1

Begin Data Parameters
Structured Data (zero or more)
x'130B'
End Parameter Data
Note: The following subvector keys may be used as indicated:

Presence in NMVT
Reply to Test Resource
(X'0064') Major Vector

Subvector
Sense Data (X'7D')

Note 1

Test Result Data (X'81')

Note 2

Conditionally present one time (See Notes for
condit ions.)

Notes:
1. This subvector is present only when sense data is returned to the
requesting application. When it is present, no MS parameter major vectors
follow in the NMVT.
2. This subvector is present only when the receiving application has executed
the specified test.

Reply to Test Resource Subvectors
Test Result Data (X' 81 ') Reply to Test Resource MS Subvector
This subvector transports the results of a requested test that was performed.

Test Result Data (X' 81 ') Reply to Test Resource MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Test Result Data subvector

Key: X ' 81

8-140

SNA Formats

MS Major Vectors

Test Resuli Data (X' 81') Reply to Test Resource MS Subvector
Byte

Bit

2-p

Content
Subfields containing the test type and test results
Note: The following subfield keys are used as described in detail following:
X101 1 Execution Result
X 1021
Test Type
1
XI 03
Test Request Count
X ' 04 1
Test Executed Count

Test Execution Result (X 101 1) Test Result Data Subfield

This subfield transports the result of the requested test.

Test Execution Result (X' 01') Test Result Data Subfield
Byte

Bit

Content

Length (q + 1), in binary" of the Test Execution Result subfield

Key: X 1 01

2( =q)

Test execution result:
XI 00 1
no errors detected
X 1 01 1
errors detected
X ' 02 1
indeterminate results

Test Type (X 1021) Test Result Data Subfield

This subfield transports the type of test requested.

Test Type (X' 02') Test Result Data Subfield
Byte

Bit

Content
Length (q + 1), in binary, of the Test Type subfield
Key: X ' 02 1

2( =q)

Test type: a code that indicates which type of test is requested.
XI 00 1
background self-test (a test of the resource is to be scheduled at the
first opportunity that will be nondisruptive to normal operation).
X 1011
immediate self-test (the resource is to be tested immediately even if
such action will be disruptive).

Chapter 8. Common Fields

8-141

MS Major Vectors

Test Request Count (X ' 03 1) Test Result Data Subfield
This subfield transports the count of iterations requested for the test.

Test Request Count (X' 03') Test Result Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Test Request Count subfield

Key: X ' 03 1

2-3( =q)

Test request count: an integer value from 1 to 32727. This returns the value
contained in the matching request.

Test Executed Count (X ' 041) Test Result Data Subfield
This subfield transports the count of iterations executed for the test.

Test Executed Count (X' 04') Test Result Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Test Executed Count subfield

Key: X'04 1

2-3(=q)

Test executed count: an integer value from 1 to 32727. This returns the number
of executions of the test attempted before failure occured. If no failure occured
it is the same value as Test Request Count.

Request Activation (X' 8066') MS Major Vector
LU

This major vector is used to request that an activation procedure be performed.

Request Activation (X' B066') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X'8066'

8-142

SNA Formats

MS Major Vectors

Request Activation (X' 8066') MS Major Vector
Byte

Bit

4-n

Content
MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X100I -X'7F', and in "Request
Change Control MS Subvectors" on page 8-116 for subvector keys
X ' 80 ' -X'FE'
Note: The following subvector key's may be used as indicated:

Presence ;n
Request Act;vat;on
(X'8066') Major Vector
Subvector
Act;vate (X'81')

CP-HSU
P

Present one t;me

Request Activation MS Subvectors
Activate (X' 81') Request Activation MS Subvector
The Activate subvector requests MS to cause reactivation of the node in
which its LU resides. For example, an initial microprogram load (IML) of the
node containing the LU may be performed.

Activate (X' 81') Request Activation MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Activate subvector

Key: X ' 81 1

2-p

One or more subfields (listed by Key value below and described in detail following):
X 110 1 Force Indication
X 120 1 Change Management Activation Use

Force Indication (X 110 1) Activate Subfield
This subfield indicates whether to perform the activation if sessions are
active. It is always present.

Chapter 8. Common Fields

8-143

MS Major Vectors

Force Indication (X' 10') Activate Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Force Indication subfield

Key: X I 10 1

2( =q)

Force indication:
X 110 I
no (do not force) - reject if sessions are active
X 120 I yes (force) - activate even if sessions are active

Change Management Activation Use (X 120 I) Activate Subfield
This subfield indicates which installed changes to activate. It is optional.

Change Management Activation Use (X'20') Activate Subfield
Byte

Bit

Content

Length (q + ;), in binary, o( the Change Management Activation Use subfield

Key: X ' 20 '

2{ =q)

Activation use:
X 110 I trial and production - use changes that are installed on a trial basis
before using changes installed in production
X120 I production only - use changes that are installed in production only

Reply Activation

Acceptan~e

l:.U

(X' 0066') MS Major Vector

This major vector is used to reply to Request Activation (X 18066 I), to indicate initial acceptance or rejection of the request.

Reply Activation Acceptance (X' 0066') MS Major Vector
Byte

Bit

Content

0-1

Length. (n + 1), in binary, of this MS major vector

2-3

Key: X ' 0066'

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys XIOOI -X'7F', and in "Change
Control MS Subvectors" on page 8-123 for subvector keys X ' 80 ' -X'FE'
Th,.,. f"'I1"', .. i ......
III"""

8-144

SNA Formats

I""'II...., ... III~

C' . .

h\lo,..t" ..

WW"'."""""~I

I£O\lC

n'l~\1 h~ 1Ie:~ri

::Ie: inriir.::Itp.rt·

"-J- " ' - J - - - - - - - - ···---"-----1--

MS Major Vectors

Presence in Reply
Activation Acceptance
(X'0066') Major Vector
CP-MSU

Subvector
Date/Time (X'Ol')
Activation Acceptance

(X'82' )

Detailed Data (X'98')

P
On

Present one time
Optionally present more than one time

Activation Acceptance MS Subvectors
Activation Acceptance (X' 82') Activation Acceptance MS Subvector
The Activation Acceptance subvector reports whether or not an activation
will be attempted as requested.

Activation Acceptance (X' 82') Activation Acceptance MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Activation Acceptance subvector

Key: X I 82 1

2-p

One or more subfields (listed by Key value below and described in detail following):
X'101
Attempt Status

Attempt Status (X 110 1) Activation Acceptance Subfield
This subfield reports whether or not activation will be attempted as
requested. It is always present once.

Attempt Status (X '10') Activation Acceptance Subfield
Byte

Bit

Content

Length (q + 1), in binary. of the Attempt Status subfield

Key: X I 10 1

Chapter 8. Common Fields

8-145

MS Major Vectors

Attempt Status (X' 10') Activation Acceptance Subfield
Byte

Bit

Content
Acceptance:
X' 10'
will attempt
X ' 20 '
will not attempt

2( =q)

Send Message to Operator (X'006F ') MS Major Vector
PU -+ SSCP
This major vector sends an unsolicited request to the host operator named.
It is followed by a management services parameter major vector.

Send Message to Operator (X' 006F') MS Major Vector
Byte

Bit

Content
Length (n + 1), in binary, of this MS major vector

2-3

Key: XI 006F 1

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X1001 -X'7F'.
This major vector is followed by one of the following management services
parameter major vectors:
X 11300 1
X 11307 1
X 11309 1
Note: The

Text Data
Structured Data
Transparent Coded Datastream
following subvector keys may be used as indicated:

Subvector
Name List (X'06')

8-146

SNA Formats

Present one time

Presence in NMVT
Send Message to Operator
(X'006F') Major Vector
P

MS Major Vectors

Request Response Time Monitor (X '8080') MS Major 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.

Request Response Time Monitor (X '8080') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X I 8080 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X1001 -X'7F', and in "Request
Response Time Monitor Subvectors" on page 8-148 for subvector keys
X ' 80 ' -XIFEI
Note: The following subvector keys may be used as indicated:

Subvector
SNA Address List (X'04')

*RTM Request (X'92')

RTM Control (X'94')

Presence in NMVT
Request RTM
(X '8080')
Major Vector
Note 1

Note 2

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 18080 I major vector
when the request is for a specific LU (i.e., identified in the X I 04 1 subvector)
associated wit,h 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 I 92 1 subvector).

Chapter 8. Common Fields

8-147

MS Major Vectors

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.

RTM Request (X' 92') Request RTM MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of this subvector

Key: X'92'

o
1
2
3

5-6

Request indicators (bit is set to 1 to request that the function be performed):
Reset RTM data for the target LU upon reply transmission or immediately if no
reply is requested.
Retrieve data and status for all LUs with accumulated RTM data. See
Figure 8-1.
Retired
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.
Apply the RTM Control (X '94') MS subvector also included in this major vector
to all LUs.
Note: If this bit is set to 1, the RTM Control (X I 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.
Retired
Reserved

3( =p)

Request Type

Retrieve data for all LUs with
accumulated data

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

92, 04

Set parameters for all LUs

92, 94

Set parameters for specified LU

92, 94, 04

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

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

SNA Formats

Retrieve for specified LU

Figure

8-148

Bits

MS Major Vectors

RTM Control (X' 94') Request RTM MS Subvecior
Byte

Bit

Content
Length (p + 1), in binary. of this subvector
Key: X'94'

2-3

0-8
9-15

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):
Mask bits corresponding respectively to indicator bits 0 - 8 in bytes 4 - 5
Reserved

0
1
2
3
4
5
6
7
8
9-15

RTM status and control indicators (bit is set to 1 to activate the function or 0 to
deactivate it):
RTM measurement active
Return data unsolicited on session deactivation
Return data unsolicited on counter overflow
Retired
Set the RTM measurement definition using byte 8
Set the RTM response time measurement boundaries using bytes 9 and 16 - m
Retired
Local display of RTM data
Retired
Reserved

4-5

Reserved

Retired

RTM measurement definition-defines when the response-time measurement
will begin and end for each exchange between session partners:
X' 01'
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
measured from the Attention or Action key depression until the LU is
X '02'
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) or CEB
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' 00'
100 milliseconds
X'01' -X'7F'
retired
X '90'
retired
X'AO'
retired
X'CO'
retired
X' DO'
retired

10-15

Reserved

16
0-3
4-7

RTM data collection parameters:
Reserved
Binary number of 2-byte boundaries in bytes 17-p

Chapter 8. Common Fields

8-149

MS Major Vectors

RTM Control (X' 94') Request RTM MS Subvector
Byte

Bit

Content

17-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 < r1 ::;; b1 xu).
(b1 xu < r2 ::;; b2xu).... 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.

17-18

Boundary 1

19-20

Boundary 2

21-p

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 inciudes the collected
response time data and current RTM status.

Response Time Monitor (X' 0080') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1). in binary. of this MS major vector

2 -3

Key: X ' 0080 '

4- n

MS subvectors. as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X100I -X'7F', and in "Response
Time Monitor Subvectors" on page 8-151 for subvector keys X ' 80 ' -X'FE'
Note: The following subvector keys may be used as indicated:

8-150

SNA Formats

MS Major Vectors

Subvector

Presence ;n NMVT
RTM (x'ooao')
Major Vector

Date/T;me (X'Dl)

Note 1

Note 2

Relative T;me (X'42')

Note 3

Data Reset Flag (X'4S')

Note 4

Sense Data (X'7D')

Note 5

RTM Status Reply (X'9i')

Note 6

RTM Data (X'93')

Note 7

. SNA Address List (X'D4')

P
CP

Present one t;me
Cond;t;onally present one t;me
condH;ons.)

(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, or when RTM data and status are sent unsolicited.
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 is 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 positively replying to a request for RTM
data and status, or when RTM data and status are sent unsolicited.
7. This subvector is present when positively replying to a request for RTM
data and status if RTM data has been accumulated, or when RTM data and
status are sent unsolicited.

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

Chapter 8. Common Fields

8-151

MS Major Vectors

RTM Status Reply (X' 91') RTM MS Subvector
Byte

Bit

Content

Length (p + 1). in binary, of this subvector

Key: X'91'

o
1
2
3

5-7
3
n

3-5
6

7
4
0
1
2

5 -7

8-152

SNA Formats

Reply indicators (bit is set to 1 to indicate that the assertion is true):
Reserved
Data not included
An RTM data request has been issued for an LU that has its RTM function disabled
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
An LU-LU session activation or deactivation has occurred at least once while
the included RTM data was being accumulated
Reserved
Reason for unsolicited reply, if any (bit is set to 1 to indicate the appropriate
reason):
The session fai this iesaUice has ended and is enabled unsolicited-reply-onsession-deactivation
A counter for this LU has overflowed and unsolicited-reply-on-counter-overflow
is enabled
Retired
Reserved
Retired
Reserved
Reason for potential loss of RTM data, if any (bit is set to 1 to indicate the
reason):
Reserved
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
This LU has been reset since the last reply was sent
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
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
Reserved

MS Major Vectors

RTM Status Reply (X' 91') RTM MS Subvector
Byte

Bit

5-6

o
1

2
3
4
5
6
7
8
9-15
7-8(=p)

Content
RTM status when this subvector was constructed (a bit set to 1 indicates that
the function was active):
RTM measurement active
Data to be sent unsolicited on session deactivation
Data to be sent unsolicited on counter overflow
Retired
RTM definition was set by the control point
RTM boundaries were set by the control point
Retired
Local display of RTM data
Retired
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 solicited or unsolicited RTM data.

RTM Data (X' 93') RTM MS Subvector
Byte

Bit

Content

Length (q + 9), in binary, of this subvector

Key: X'93 1

RTM measurement definition in effect:
X '01 1 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 1 measured from the Attention or Action key depression until the LU is
ready to accept input from its end user
1
X 103
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) or CEB
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 101 1-X'7F'
retired
X 190 1 retired
X'AO'
retired
XICOI
retired
X 1DO 1 retired
Chapter 8. Common Fields

8-153

MS Major Vectors

RTM Data (X'93') RTM MS Subvector
Byte

Bit

Content

4-5

Reserved

6-7

Retired

8
0-3
4-7

RTM data collection parameters:
The number, in binary, of response time measurement boundaries returned; all
boundaries that were set previously will be returned in this subvector
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)

9-p

A set of response-time measurement boundaries as previously set at the LU or
by the RTM Control (X 1 94 1 ) 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 (0 < r1 ~ b1 xu),
(b1 xu < r2 ~ b2xu),... 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

9-10

Boundary 1

11-12

Boundary 2

13-p

Additional boundaries as required to equal the number of boundaries set previously and specified by byte 8, bits 0 - 3

p+1-q

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

p+1-p+2

Number of exchanges in the (O,b1) range

p+3-p+4

Number of exchanges in the (b1 + 1,b2)

p+5-q

Additional exchange counts to satisfy the number of boundaries defined, up to a
maximum of 4

q+1-q+2

rang~

Overflow: the number of exchange durations greater than the maximum
. boundary specified

q+3-q+6

Total of all individual times for all exchanges measured and reported by this
record, including overflow, in the measurement units defined by byte 3

q+7-q+8

Last measured exchange duration in the measurement units defined by byte 3

Request Product Set 10 (X' 8090') MS Major Vector
SSCP -+ PU
This major vector transports a request for product identification from a
network component.

8-154

SNA Formats

MS Major Vectors

Rcque~t

Byte

f'rcduct Set 10 (X' aOnO') MS M"jOi Vectoi

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X I8090 I

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X100I -X'7F', and in "Request
Product Set 10 Subvectors" on page 8-155 for subvector keys X ' 80 ' -X'FE'
Note: The following subvector keys may be used as indicated:

Presence in NMVT
Request PSID (X'S090')
Major Vector

Sub vector
*Node Identification (X'Sl')

Note 1

*Node and Port-Attached
Oevices Identification
(X'S3')

Note 2

Command subvector (for PU parsing)
Conditionally present one time. (See notes for conditions.)

Notes:
1. This subvector is present when requesting the PSIO for just the node (PU)
the major vector is sent to.
2. This subvector is present when requesting the PSIO for the node (PU) the
major vector is sent to and its port-attached devices.

Request Product Set 10 Subvectors
Node Identification (X' 81') Request PSIO MS Subvector
This subvector requests product identification for the node receiving the
request.

Request Product Set 10 (X' 81') Request PSIO MS Subvector
Byte

o
1(

Bit

Content
Length (p + 1), in binary, of this subvector

=p)

Key: X ' 81

Chapter 8. Common Fields

8-155

MS Major Vectors

Node and Port-Attached Devices Identification (X 183 1) Request PSID MS Subvector
This subvector requests product identification from the node the major
vector is sent to. The node must build one Reply Product Set 10 (X 10090 1)
major vector for itself and one for each port-attached device for which the
node has product identification.

Node and Port-Attached Devices Identification (X ' 83 1 ) Request PSID MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of this subvector

1( = p)

Key: X ' 83 1

Reply Product Set 10 (X '0090 ') MS Major Vector
PU -. SSCP
This major vector transports product identification information that was
requested by the Request Product Set 10 (X 18090 I) major vector.

Reply Product Set ID (X I 0090') MS Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X ' 0090 '

4- n

MS subvectors, as described (using zero-origin indexing) in MS Common
Subvectors" on page 8-165 for subvector keys XIOOI -X'7F', and in "Reply
Product Set 10 Subvectors" on page 8-157 for subvector keys X ' 80 ' -X'FE'
X ' 80 '
X'FE'.
Note: The following subvector keys may be used as indicated:
II

8-156

SNA Formats

MS Major Vectors

Subvector

Presence in NHVT
Reply PSID (X'OO90')
Major Vector

Date/Time (X'Ol)

SNA Address List (X'04')

Product Set ID (X'lO')

Relative Time (X'42')

Note 3

Port-Attached Device
Configuration Description
(X'82' )

Note 4

P
CP

Present one time
Conditionally present one time
conditions.)

Note 1
Note 2

(See Notes for

Notes:

1. If the PU sending the XI 0090 1 major vector has the capability of providing it,
this subvector is placed in the NMVT.

2. This subvector is present when the major vector is reporting on a portattached device. The address present in this subvector identifies the LU
most closely associated with the device.
3. If the PU sending the X10090 1 cannot provide a Date/Time subvector, it
places this subvector in the NMVT instead~

4. This subvector is present when the major vector is reporting on a portattached device.

Reply Product Set 10 Subvectors
Port-Attached Device Configuration Description (X' 82') Reply PSID MS Subvector
This MS subvector describes the configuration of a device port-attached to
the node to which the Request PSID major vector was sent.

Port-Attached Device Configuration Description (X' 82') Reply PSID MS Subvector
Byte

Bit

Content

Length (p + 1). in binary, of this subvector.

Key: X ' 82 1

2-p

The following subfields are required:
X I 10 1
Port number
XI 20 1
Power-on status
X 130 1 Power-on since last solicitation

Chapter 8. Common Fields

8-157

MS Major Vectors

Port Number (X 110 1) Port-Attached Device Config. Des. Subfield
This subfield contains the port number the device is attached to. The port
number is associated with the "parent" node (the node to which the Request
Product Set 10 major vector was sent).

Port Number (X'10') Port-Attached Device Config. Des. Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of this subfield

Key: X I 10 1

2-q

Number of the port the device is attached to: numeric characters from Coded
Graphic Character Set 01134-00500, documented in Appendix A, "SNA Character Sets and Symbol-String Types."

Power-on Status (XI201) Port-Attached Device Config. Des. Subfield
This subfield transports the power-on status of the attached device.

Power-on Status (X' 20') Port-Attached Device Config. Des. Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of this subfield

Key: X I 20 1

2( =q)

Power-on Status of the device:
X 1011 device is currently powered on
X 1021 device is currently powered off

Power-on Since Last Solicitation (X I 30 1) Port-Attached Device Config. Des. Subfield
This subfield states whether the device was powered on since the last
solicition (Le., since the last time a Reply PSIO major vector was sent by
this node).

Power-on Since Last Solicitation (X'30') Port-Attached Device Config. Des. Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of this subfield

Key: X I 30 1

8-158

SNA Formats

MS Parameter Major Vectors

Power-on Since Last Solicitation (X' 30') Port-Attached Device Config. Des. Subiield
Byte

Bit

2( =q)

Content
Power-on since last solicitation
X 1011 device was powered on (from a power-off position) at least once

X102 I device was not powered on (although it may have been powered on
before the previous solicitation and remained powered on) since the last solicitation

Text Data (X' 1300') MS Parameter Major Vector
PU

-+-

SSCP

This MS parameter major vector accompanies one of two MS major vectors:
Reply to Execute Command (X 100611) and Send Message to Operator
(X 1006F I). It transports one or more messages.

Text Data (X'1300') MS Parameter Major Vector
Byte

Bit

Content

0-1

Length (n + 1L in binary, of this MS major vector

2-3

Key: X 11300 1

4-n

MS subvectors, as described (using zero-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X 100 I - X 17F I.
Note: The following subvector keys may be used as indicated:

Subvector

Presence in NMVT
Message Data Parameters
(X'1300') Major Vector

Qualified Message (X'0A')

CP(n)

Note 1

Self-Defining Text Msg (X'31')

CP(n)

Note 2

CP(n) Conditionally present one or more times
(See notes for conditions.)

Notes:

1. This subvector is present one or more times when the Self-Defining Text
Message subvector is not present. One of the two is required.
2. This subvector is present one or more times when the Qualified Message
subvector is not present. One of the two is required.
Chapter 8. Common Fields

8-159

MS Parameter Major Vectors

Structured Data (X' 1307') MS Parameter Major Vector
PU -+ SSCP
This MS parameter major vector accompanies one of five MS major vectors:
Reply to Execute Command (X 10061 1), Reply to Analyze Status (X 10062 1),
Reply to Query Resource Data (X 10063 1), Reply to Test Resource (X 100641),
and Send Message to Operator (X '006F I). It transports one or more
resource data items.

Structured Data (X '1307') MS Parameter Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X 11307 1

4-n

MS subvectors, as described (using O-origin indexing) in "MS Common
Subvectors" on page 8-165 for subvector keys X1001 -X'7F'.
Note: The following subvector keys may be used as indicated:

Subvector

Presence in NMVT
Structured Data
(X'1307') Major Vector

Hierarchy/Resource List (X'05')
Resource Data (X'80')

P
CP(n)

P
eP(n)

Present one time
Conditionally present one or more times.
condit ions.)

(See Note for

Note:
1. This subvector is present one or more times when the Structured Data MS
parameter major vector follows the Reply To Test Resource (X 10064') MS
major vector or the Reply To Query Resource Data (X ' 0063 1) MS major
vector.

Structured Data Subvectors
Resource Data (X'80') Structured Data MS Subvector
This Structured Parameter subvector transports data about a single
resource.

8-160

SNA Formats

MS Parameter Major Vectors

Resource Data (X' 80') Structured Data MS Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Resource Data subvector

Key: X'BO'

2-p

Subfields containing a resource name and data related to the resource. The
X '01' subfield is always present. One of the remaining four subfields is also
present.
Note: The following subfield keys are used as indicated:
(X'01') Resource Item Name
(X '02') Resource Item Hex Value
(X '03') Resource Item Character Value
(X'04') Resource Item Integer Value
(X'OS') Resource Item Bit String Value

Resource Item Name (X'D1') Resource Item Name Subfield
This subfield transports the name of the resource data item, i.e. a label.
One of the following may be used: Resource Item Name, Resource Item
Address, or Resource Item 10.

Resource Item Name (X' 01') Resource Item Name Subfield
Byte

Bit

Content
Length (q + 1), in binary, of the Resource Item Name subfield

Key: X'01'

2-q

Resource item name: a string of characters from Coded Graphic Character Set

01134-00500, documented in Appendix A, "SNA Character Sets and SymbolString Types"

Resource Item Hex Value (X' 02') Resource Data Subfield
This subfield transports hexadecimal data to be displayed as hex digits.

Resource Item Hex Value (X' 02') Resource Data Subfield
Byte

Bit

Content
Length (q + 1), in binary, of the Resource Item Hex Value subfield
Key: X'02'

2-q

Resource item hex value: a string of hexadecimal bytes

Chapter 8. Common Fields

8-161

MS Parameter Major Vectors

Resource Item Character Value (X '03') Resource Data Subfield
This subfield transports character data.

Resource Item Character Value (X' 03') Resource Data Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the Resource Item Character Value subfield

Key: X'03'

2-q

Resource item character value: a string of characters from Coded Graphic
Character Set 01134-00500, documented in Appendix A, "SNA Character Sets
and Symbol-String Types"

Resource Item Integer Value (X'04') Resource Data Subfield
This subfield transports 'integer data.

Resource Item Integer Value (X'04') Resource Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Resource Item Integer Value subfield

Key: X'04'

2-q

Resource Item Integer Value: a one to four byte integer value

Resource Item Bit String Value (X'OS') Resource Data Subfield
This subfield transports hexadecimal data to be displayed as a string of 1's
and O's.

Resource Item Bit String Value (X' 05') Resource Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Resource Item Bit String Value subfield

Key: X'05'

2- q

Resource item bit string value: a string of hexadecimal bytes

8-162

SNA Formats

MS Parameter Major Vectors

Transparent Coded Datastream(X' 1309 ') MS Parameter Major Vector
PU -+ SSCP
This MS parameter major vector accompanies one of two MS major vectors:
Reply to Execute Command (X '0061 ') and Send Message to Operator
(X '006F I). It contains data whose structure is not defined by SNA, but that
is known by the sending and receiving applications.

Transparent Coded Datastream(X'1309') MS Parameter Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X' 1309'

4-n

Data of an architecturally undefined structure

Begin Data Parameters (X' 130A ') MS Parameter Major Vector
PU -+ SSCP
This MS parameter major vector accompanies one of three MS major
vectors: Reply to Analyze Status (X '0062 '), Reply to Query Resource Data
(X'0063'), and and Reply to Test Resource (X'0064'). It serves as a starting
delimiter for a sequence of other MS parameter major vectors, as well as
transporting failure data itself.

Begin Data Parameters (X' 130A ') MS Parameter Major Vector
Byte

Bit

Content

0-1

Length (n + 1), in binary, of this MS major vector

2-3

Key: X '130A'

4-n

MS subvectors, as described below.
Note: The following subvector keys may be used as indicated:

Chapter 8. Common Fields

8-163

MS Parameter Major Vectors

Subvector

Presence in NMVT
Begin Data Parameters
(X'13DA') Major Vector

Resource State (X'82')

Note 1

Probable Causes (X'93')

Note 1

Conditionally present one time.
conditions.)

(See Note for

Note:
1. This subvector is present one time whenever the Begin Data Parameters
MS parameter major vector follows the Reply To Analyze Status (X 100621)
MS major vector.

Begin Data Parameters Subvectors
Resource State (X' 82') Begin Data Parameters MS Subvector
This Begin Data Parameters subvector transports the state of an analyzed
resource or set of resources.

Resource State (X' 82') Begin Data Parameters MS Subvector
Byte

Bit

Content

Length (3), in binary, of the Resource State subvector

Key: X I 82 1

A value
X 100 I
X 1011
X 1021
X 103 1
X 104 1
X 105 1

indicating the resource state:
no failure detected
detected failure with failing resource isolated
detected failure with location not isolated
detected failure upstream from the managed resource set
detected failure within the managed resource set
detected failure downstream from the managed resource set

Probable Causes (X' 93') Begin Data Parameters MS Subvector
This subvector contains one or more code points denoting probable causes
of a failure. The probable causes appear in order of decreasing probability.
Note: The format of this subvector is defined under the Alert (X 10000 I) major
vector.

8-164

SNA Formats

MS Common Subvectors

End Parameter Data (X' 1308') MS Parameter Major Vector
PU

SSCP

This MS parameter major vector accompanies one of three MS major
vectors: Reply to Analyze Status (X 10062 I), Reply to Query Resource Data
(X ' 0063 1), and and Reply to Test Resource (X ' 00641). It serves as an
ending delimiter for a sequence of other MS parameter major vectors.

End Parameter Data (X' 130B') MS Parameter Major Vector
Byte

Bit

Content

0-1

Length (4). in binary. of this MS major vector

2-3

Key: X ' 130B I

MS Common Subvectors
The common MS subvectors are defined as follows (using O-origin indexing):
Text Message (X'OO') MS Common Subvector
This MS common subvector transports EBCDIC data.

Text Message (X'OO') MS Common Subvector
Byte

Bit

Content

Length (p + 1). in binary, of the Text Message subvector

Key: X1001

2-p

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' 01 ') MS Common Subvector
This MS common subvector is used by the PU for time-stamping the NMVT
in which it is carried.

Chapter 8. Common Fields

8-165

MS Common Subvectors

DatelTime (X' 01 ') MS Common Subvector
Byte

Bit

Content

Length (p + 1). in binary. of the Date/Time subvector

Key: XI 01

2-p

One or more of the following subfields:
X 110 I
Local Date/Time (requi red subfield)
X ' 20 '
Greenwich Mean Time Offset

Local Date/Time (X 110 1) Date/Time Subfield
This subfield transports the local date and time of the creation of the major
vector.

Local DatelTime (X'10') DatelTime Subfield
Byte

Bit

Content

Length (q + 1). in binary. of the Local Date/Time subfield

Key: X I 10 1

2-4

Local date

Year. in binary. consisting of the last two digits of the year

Month. in binary (X I 01 1_XIOCI)

Day. in binary (X ' 011-X'1F')

5-q

Local time

Hours. in binary (XIOOI -X'171)
Minutes. in binary (XIOOI -X ' 38 1)
Seconds. in binary (X ' OO'-X ' 38 1)

8-q

Optional extension of time: a binary value to provide finer granularity than
seconds

Greenwich Mean Time Offset (X 120 I) Date/Time Subfield
This subfield transports the Greenwich Mean Time (GMT) offset of the node
that originated the management services RU (Le .• 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.
/'

8-166

SNA Formats

MS Common Subvectors

Grcon,,",ich MO:2n Time Off::et (X' 20') DatclTlme Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Greenwich Mean Time Offset subfield

Key: X ' 20 '

2 -3( =q)

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 110 I) subfield to adjust that time to Greenwich Mean Time
Positive or negative adjustment indicator:
a
adjustment to be added to the local time (Le., all time zones westward,
. between the Greenwich time zone and the International Date Line)
1
adjustment to be subtracted from the local time (Le., all time zones eastward, between the Greenwich time zone and the International Date Line)
Reserved
Number of hours of adjustment, in binary (XIOI _XICI)
Number of minutes of adjustment, in binary (X 100 I - X '3B I)

1-3
4-7

8-15

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.

Hierarchy Name List (X' 03') MS Common Subvector
Byte

Bit

Content

Length (p + 1). in binary, of the Hierarchy Name List subvector

Key: X ' 03 1

Reserved

Number, in binary, of name entries in the hierarchy name list.

4-p

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 a-origin):

Length (q + 1), in binary, of the following name plus this Length field

1-q

Name of resource in upper-case alphanumeric EBCDIC characters
Note: Resource name never exceeds eight characters.

q+1-q+4

Resource type identifier: category in which the resource (named in bytes 1- q)
belongs:
X ' C1C4C1D7 1 adapter
X'C2D9C4C7 1 LAN bridge
X'C3C2E740 ' computerized branch exchange
X I C3C2E4E2 I carrier-sense multiple-access with collision detection
(CSMA/CD) bus

Chapter 8. Common Fields

8-167

MS Common Subvectors

Hierarchy Name List (X' 03') MS Common Subvector
Byte

Bit

Content
X'C3C8C105 1
XI 03C905C5 1
XI C3E30903 1
X'C4C9E202 1
X'C4E202E3 1
X ' 02E8C2C4 1
XI 03C1 0540 1
XI 03C30605 1

X ' 03060607 1
XI 07C20440 1
XI 0706E240 1
XI 07C2E740 1
XI 0703E309 1
XI 0709E309 1
XI 09C905C7 1
XI E2074040 1
X'E3F10904 1
XI E3C1 07C5 1
XI E3C1 E440 1
XI E3C2E4E2 1
XI E3C50904 1
XI C4C5E540 1

channel
communication link
controller
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
T1 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 in 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 subvector within the MS major vector.

SNA Address List (X '04') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the SNA Address List subvector

Key: X ' 04 1

8-168

SNA Formats

MS Common Subvectors

SNA Address List (X' 04') MS Common Subvector
Byte

Bit

Content

Address Count: For address entity format types X100I, X ' 40 ' , X ' 80 ' , and XICOI,
a binary number indicating the number of individual addresses present in the
X ' 04 1 subvector. This field is set to X 100 I for all other address entity format
types.
Note: This field provides a count of individual addresses; thus, for format X 140 1,
each pair of addresses counts as two.

Address entity format type:
XIOOI
address format is one or more single local addresses
X 140 I
address format is one or more pairs of session-partner local
addresses, each pair identifying a session
address format is one or more single network addresses
X 180 I
X I AO 1 address format is one or more network-qualified address pairs, each
pair identifying a session
X I CO I address format is one or more pairs of session partner network
addresses, each pair identifying a session

4-p

Address entities: one or more address entities, each having one of the formats
defined below (O-origin):

For a single local address (byte 3

= X 100 I):

0-4

Reserved

Local address

For a pair of session-partner local addresses (byte 3

= X 140 I):

0-4

Reserved

Local address of SLU

Retired

7-11

Reserved

Session index (local address of PLU)

For a single network address (byte 3

0-5

= X 180 I):

Network address

For a network-qualified address pair (byte 3

= X I AD I):

0-5

Network address of NAU1

6-11

Network address of NAU2

12-19

Network 10 of the subnetwork in which the above addresses are valid

For a pair of session-partner network addresses (byte 3 = X I CO I):

0-5

Network address 1

X' 80 '

7-12

Network.address 2

Chapter 8. Common Fields

8-169

MS Common Subvectors

Hierarchy/Resource List (X' 05') MS Common Subvector
This MS common subvector identifies resources, hierarchically below the
sending PU, that cannot be represented in the SNA Address List subvector.

Hierarchy/Resource List (X' 05') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Hierarchy/Resource List subvector

Key: XIOSI

2-p

The following subfield containing a hierarchical list of resources (listed by key
value below and described in detail following):
X 110 I Hierarchy Name List

Hierarchy Name List (X 110 1) Hierarchy/Resource List Subfield
This subfield contains a list specifying the names of resources in a hieiarchy. The last name in the list specifies the resource to which the data
present in the major vector pertains.

Hierarchy Name List (X'10') Hierarchy/Resource List Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Hierarchy Name List subfield

Key: X I 10 1

Always set to X I 80 I

3- q

Hierarchy Name List Entries (transmission order of entries indicates resources
down the hierarchy, i.e., first-sent is highest in 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 O-origin):

Length (r+ 1), in binary, of the following name plus this length field

1- r

Name of resource in upper-case alphanumeric EBCDIC characters
Note: Resource name never exceeds eight characters.

8-170

SNA Formats

MS Common Subvectors

Hierarchy Name List (X'10') Hierarchy/Resource List Subiield
Byte

Bit

r+1

o
1

2-7
r+2

Content
Flags
Reserved
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 presentation 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.
Reserved
Resource type identifier: category to which the resource (named in bytes 1 - r)
belongs:
unspecified device
X'OO'
X'11'
disk
X'13'
printer
X'16'
tape
X'17'
terminal
X'18' transaction program name
program product
X'19'
storage device
X'20'
adapter
X'21'
X'25' diskette
loop
X'27'
keyboard
X'29'
X'28' plotter
X'2C' transmission group
X'2D' line group
token-ring
X'2E'
X'2F' computerized branch exchange
T1 resource manager
X'30'
private branch exchange
X'31'
X'32' carrier-sense multiple-access with collision detection (CSMA/CD) bus
token bus
X'33'
printer server
X'34'
personal banking machine
X'35'
teller assist unit
X'36'
point-of-sale unit
X'37'
local controller
X'38'
network (LAN)
local-area
X'39'
LAN
bridge
X'3A'
X '38' logical link connection
Note: See also Resource Type Identifier X' F9' (link). Identifier X '38'
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'3D' line
X'3E'
domain
Chapter 8. Common Fields

8-171

MS Common Subvectors

Hierarchy Name List (X'10') Hierarchy/Resource List Subfield
Byte

Bit

Content

X'3F'
X'80'
X'81'
X'82'
X'83'
X'FO'
X'F1'
X'F2'
X'F3'
X'F4'
X'F5'
X'F7'
X'F8'
X'F9'

port
controller
service point
communication controller
central processing unit
boundary function physical unit
physical unit
OSI management server
logical unit
control poi nt
network 10
link station
SNA channel
link

Name List (X' 06') MS Common Subvector
This MS common subvector is used in requests, to identify one or more
resources to which the request pertains. It may also contain the name of a
network management application or network operator to which the receiver
is to route the request.

Name List (X' 06') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Name List subvector

Key: X'06'

2-p

One or more subfields containing a hierarchy and/or a list of peer resources
(listed by key value below and described in detail following):
X '01'
Associated Resource Name List
X '50'
Destination Application Name

Associated Resource Name List (X'01') Name List Subfield

This subfield contains a list specifying the names of associated resources.
The relationship among the resources is not defined.

8-172

SNA Formats

MS Common Subvectors

A~~oci~tcd

Byte

Rc:;ourco
Bit

N~mo

Li:;t (X' 01 ')

N~mo

Li:;t Subfiold

Content

Length (q + 1). in binary, of the Associated Resource Name List subfield

Key: X 1 01

2-q

Associated Resource Name List Entries

Note:

Each entry contains Length and Name fields and has the following form (shown
O-origin):

Length (r+ 1), in binary, of the following name field plus this length field

1-r

Name of resource: a string of characters from Coded Graphic Character Set
01134 - 00500 ,documented in Appendix A, "SNA Character Sets and SymbolString Types"
Note: Resource name never exceeds eight characters.

Destination Application Name (X ' 50 ' ) Name List Subfield

This subfield identifies either a network management application or a
network/system operator at the destination to which the request is to be
routed.

Destination Application Name (X' 50') Name List Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Destination Application Name subfield

Key: X ' 50 '

2-q

Name of destination application (or network/system operator): a string of characters from Coded Graphic Character Set 01134-00500, documented in
Appendix A, "SNA Character Sets and Symbol-String Types"
Note: Application name never exceeds eight characters.

Qualified Message (X' OA') MS Common Subvector
This MS common subvector contains a formatted identifier for a message
stored at the receiver. It also contains a number of replacement text strings
to be inserted into the message. The particular message being indexed
determines how many text strings are included.

Qualified Message (X' OA ') MS Common Subvector
Byte

Bit

Content
Length (p + 1), in binary, of the Qualified Message subvector
Chapter 8. Common Fields

8-173

MS Common Subvectors

Qualified Message (X' OA ') MS Common Subvector
Byte

Bit

Content

Key: X'OA'

2-p

Subfields containing a formatted message identifier, and possibly one or more
strings of text to be inserted into the message indexed by the identifier.
Note: The following subfield keys are used as indicated:

Subfield

Presence in Qualified
Message (X'OA')
Common Subvector

Message 10 (X'Ol')
Replacement Text (X'02')

P
CP(n)

Note 1

P
Present one time
CP(n) Conditionally present one or more times
(See notes for conditions.)

Notes:

1. The number of instances of this subfield present in the X'OA' subvector is
determined by the number of strings of text required for insertion into the
message indexed by the X '01' subfield.
Message ID (X'D1') Qualified Message Subfield

This subfield contains a formatted identifier that indexes a message stored
at the receiver. The exact format of the identifier is at the discretion of the
sending and receiving applications.

Message ID (X' 01') Qualified Message Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Message 10 subfield

Key: X'01'

2- q

Message 10: A string of characters from Coded Graphic Character Set
01134-00500, documented in Appendix A, "SNA Character Sets and SymbolString Types," identifying a text message stored at the receiver. The format of
the message 10 is left up to the discretion of the sender and the receiver.

8-174

SNA Formats

MS Common Subvectors

Replacement Text (X ' 021) Qualified Message Subfield
This subfield transports replacement text, to be substituted by the receiver
into the message indexed by the Message 10 (X 1011) subfield.

Replacement Text (X' 02') Qualified Message Subfield
Byte

Bit

Content

Length (q + 1). in binary, of the Text Message subfield

Key: X ' 02 1

2-q

Replacement text: A string of characters from Coded Graphic Character Set
00640-00500, documented in Appendix A, "SNA Character Sets and SymbolString Types," to be substituted into the message indexed by the Message 10
(X 1011) subfield

Product Set 10 (X'10') MS Common Subvector
This MS common subvector identifies one or more products that implement
a network component.

Product Set 10 (X'10') MS Common Subvector
Byte

Bit

Content

Length (p + 1). in binary, of the Product Set 10 subvector

Key: X I 10 1

Retired

3-p

Network product identifier consisting of one or more Product 10 (X 1111) MS
common subvectors, as described below (using O-origin indexing). Each
Product 10 (X 1111) MS Common Subvector uniquely identifies a product. Products fall into two categories: hardware (with or without microcode) and software.

Product Identifier (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).

Chapter 8. Common Fields

8-175

MS Common Subvectors

Product Identifier (X' 11') MS Common Subvector
Byte

Bit

Content

Length (q + 1), in binary, of the Product Identifier subvector

Key: X I 11 1

0-3
4-7

3-q

8-176

Reserved
Product classification:
IBM hardware
X 111
1
IBM or non-IBM hardware (not distinguished)
X 13
X ' 4 1 IBM software
Xigi
non-IBM hardware
XICI non-IBM software
XI E 1 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

FMH 7
HW or SW X'QQQQ' Alert
XID3
X'll'
(Note 2)
(Note 1) Sender Resource (Note 3) (LU6.2)

X'OO'

X'Ol'

X'OS'

X'OE'

X'02'

Note 5

X'04'

Note 6

X'06'

X'07'

Note 7

X'OS'

Note 6

X'09'

Note 7

Note 4

Conditions of Subfield Presence in Product Identifier Subvector

P
CP

Not present
Present one time
Conditionally present one time
Optionally present one time

Subfield Names:
X'OO'
X'01'
X'02'
X'04'
X'06'
X'07'
X'OS'
X'09'
X'OS'
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:

1. The hardware (HW) X 1111 Product Identifier subvector is present when the
Product Classification field (byte 2. bits 4 -7) is X 11 1, X 13 1, or X 19 1. The
software (SW) X 1111 Product Identifier subvector is present when this field
is X141. X'CI, or XIEI.
2. If a PU is sending an Alert for itself, a single Product Set 10 (X 110 I) 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 110 1 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 XI03, the Hardware and Software X 1111 subvectors are carried in the
X '10' control vector rather than the X '10' MS Common subvector.
Chapter 8. Common Fields

8-177

MS Common Subvectors

4. This subfield is present in the hardware X '11' when a product is emulating
another hardware product.
5. This subfield is present in the software X '11' for IBM products assigned a
component 10 by the IBM National Service Division. For products not
assigned a component 10, the X'04' and X'08' subfields are present. See
Note 6.
6. The X 104' and X'08' subfields are present in the software X'11' if the
X '02' subfield is not present. They are optional when the X 1021 is present.
See Note 5. If, however, the software identified is a customer-written application, only the X '08' subfield is present.
7. One of the X 107' and X'Ogl subfields is required in the software X'111 for
software products modified by the customer.

Note: Unless otherwise indicated, characters in these subfields are to be
decoded using Coded Graphic Character Set 01134-00500, documented in
Appendix A, "SNA Character Sets and Symbol-String Types."
Hardware Product Identifier (X'OO') Product 10 Subfield

This subfield uniquely identifies an instance of a hardware product.

Hardware Product Identifier (X '00') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1), in binary, of the Hardware Product Identifier subfield

Key: XIOO'

Format type:
X '10'
product instance is identified by a serial number (Le., plant of manufacture and sequence number) unique by machine type
X'11'
product instance is identified by a serial number (Le., plant of manufacture and sequence number) unique by machine, type and model
number
product instance is identified by a serial number (Le., plant of manufacX 112'
hire and sequence number) unique by machine type (as in format .
X '10' above). This format provides the model number not to uniquely
identify a product instance but, for the purpose of additional information
only.
X'13'
retired
X 120'
product instance is identified by a repair 10 number (Le., plant of manufacture and sequence number) unique by machine type
X '21'
product instance is identified by a repair 10 number (Le., plant of manufacture and sequence number) unique by machine type and model
number
X '22 I
product instance is identified by a repair 10 number (Le., plant of manufacture and sequence number) unique by machine type (as in format
X '10' above). This format provides the model number not to uniquely
identify a product instance but for the purpose of additional information
only.
retired
X '40 I

8-178

SNA Formats

MS Common Subvectors

Hardware Product Identiiier (X 100 1) Product 10 Subiield
Byte

Bit

Content
X ' 41

3-r

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 I FO I] are inserted) of the Product Identification field to indicate that no identification information is available.

Format X I 10 I

3-6

Machine type: four numeric characters

7-8

Plant of manufacture: two characters

9-15{=r)

Sequence number: seven characters, right-justified, with EBCDIC O's (X I FO I) fill
on the left

Format X I 11 1

3-6

Machine type: four numeric characters

7-9

Machine model number: three characters

10-11

Plant of manufacture: two characters

12-18{=r)

Sequence number: seven characters, right-justified, with EBCDIC O's (X I FO I) fill
on the left

Format X ' 12 1

3-6

Machine type: four numeric characters

7-9

Machine model number: three characters

10-11

Plant of manufacture: two characters

12-18(=r)

Sequence number: seven characters, right-justified, with EBCDIC O's (X I FO I) fill
on the left

Format X 120 I

3-6

Machine type: four numeric characters

7-8

Plant of manufacture: two characters

9-15( =r)

Sequence number: seven characters, right-justified, with EBCDIC O's (X I FO I) fill
on the left

Format X 1211

3-6

Machine type: four numeric characters

7-9

Machine model number: three characters

10-11

Plant of manufacture: two characters

12 -18( = r)

Sequence number: seven characters, right-justified, with EBCDIC O's (X I FO I) fill
on the left

Format X I 221

Chapter 8. Common Fields

8-179

MS Common Subvectors

Hardware Product Identifier (X' 00') Product 10 Subfield
Byte

Bit

Content

3-6

Machine type: four numeric characters

7-9

Machine model number: three characters

10-11

Plant of manufacture: two characters

12 -18( =r)

Sequence number: seven characters, right-justified, with EBCDIC O's (XI FOI) fill
on the left

Emulated Product Identifier (X 1011) Product ID Subfield
This subfield identifies the hardware of the product being emulated in sufficient detail to allow problem determination

Emulated Product Identifier (X '01 ') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1), in binary, of the Emulated Product Identifier subfield

Key: X I 011

2-5

Machine type of product being emulated: four numeric characters

6 -8( =r)

Model number of product being emulated: three characters

Software Product Serviceable Component Identifier (X I 021) Product ID Subfield
This subfield transports the serviceable component identifier and release
level as assigned by service personnel.

Software Product Serviceable Component Identifier (X' 02') Product 10 Subfleld
Byte

Bit

Content

Length (r+ 1), in binary, of the Software Product Serviceable Component Identifier subfield

Key: X I 02 1

2-10

Serviceable component identifier: nine characters

11-13( = r)

Serviceable component release level: three numeric characters

8-180

SNA Formats

MS Common Subvectors

Software Product Common Level (X ' 041) Product 10 Subfield
This subfield transports the common version, release, and modification level
numbers as given in the product announcement documentation.

Software Product Common Level (X' 04') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1), in binary, of the Software Product Common Level subfield

Key: X' 04 1

2-3

Common version identifier: numeric characters, right-justified with X I FO I fill on
left

4-5

Common release identifier: numeric characters, right-justified with X I FO I fill on
left

6 -7{ =r)

Common modification identifier: numeric characters, right-justified with XI FO I fill
on left

Software Product Common Name (X ' 06 1) Product 10 Subfield
This subfield transports the software common name as given in the product
announcement documentation.

Software Product Common Name (X' 06') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1), in binary, of the Software Product Common Name subfield

Key: X ' 06 1

2-r

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 148 1 = ". (period); X 160 I
(minus sign);
1
X ' 61
(slash).
II

= "-"

= "/"

Software Product Customization Identifier (X 107 1) Product 10 Subfield
This subfield identifies a set of executable instructions, customized to the
user's environment.

Chapter 8. Common Fields

8-181

MS Common Subvectors

Software Product Customization Identifier (X'07') Product 10 Subfield
Byte

Bit

Content

Length (r + 1), in binary, of the Software Product Customization Identifier subfield

Key: X ' 07 1

2-r

Customization identifier: up to eight characters

Software Product Program Number (X 108 1) Product ID 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.

Software Product Program Number (X' 08') Product 10 Subfleld
Byte

Bit

Content

Length (r+ 1), in binary, of the Software Product Program Number subfield

Key: X ' 08 1

2 -8( =r)

Program product number: seven 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 characters from Coded Graphic Character Set 01134-00500, documented
in Appendix A, "SNA Character Sets and Symbol-String Types, 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 140 I) characters. Installation managers have the sole responsibility for managing the usage of these
substitute values within their networks.
II

Software Product Customization Date and Time (X ' 09 1) Product ID Subfield
This subfield identifies the date and time that a set of executable
instructions was customized to the user's environment.

Software Product Customizatlon Date and Time (X' 09') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1), in binary, of the Software Product Customization Date and Time
subfield.

Key: X ' 09 1

Year in unsigned packed decimal (Le., one hex digit for each decimal digit)

8-182

SNA Formats

MS Common Subvectors

Software Product Customization Date and Time (X' 09') Product 10 Subfleld
Byte

Bit

Content

3-4

Julian day in unsigned packed decimal, right-justified with O's as fill

Hour in unsigned packed decimal (24-hour clock)

= r)

Minute in unsigned packed decimal

Microcode EC Level (X lOB I) Product ID 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)

Microcode EC Level (X' OB ') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1). in binary, of the Microcode EC Level subfield.

Key: X'OB'

2-r

Microcode EC Level: up to eight characters

Hardware Product Common Name (X'OE') Product ID Subfield

This subfield provides the hardware common name as given in the product
announcement documentation

Hardware Product Common Name (X' OE') Product 10 Subfield
Byte

Bit

Content

Length (r+ 1). in binary, of the Hardware Product Common Name subfield

Key: X'OE'

2-r

Up to fifteen characters identifying the hardware 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 1 = "." (period); X ' 60 ' = "_" (minus sign);
X I 61 1 = "/" (slash).
II

Chapter 8. Common Fields

8-183

MS Common Subvectors

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.

Self-Defining Text Message (X' 31') MS Common Subvector
Byte

Bit

Content

Length (p + 1). in binary. of the Self-Defining Text Message subvector

Key: X'31'

2-p

Subfields containing a text message. as well as additional information characterizing the message.
Note: The following subfield keys are used as indicated:

Subficld

Presence in Self-Defining
Text Message (X'31')
Cammon Subvector·

Coded Character Set 10 (X'02')

National Language 10 (X'12')

Note 1

Sender 10 (X'21')

Note 1

Text Message (X'30')

P
CP

Present one time
Conditionally present one time
conditions.)

(See Notes for

Notes:

1. This subfield is present in an Alert.
Coded Character Set ID (X I 02') Self-Defining Text Message Subfield

This subfield identifies the coded character set in which the text message is
encoded.

Coded Character Set 10 (X '02') Self-Defining Text Message Subfield
Byte

Bit

Content

Length (q + 1). in binary. of the Coded Character Set 10 subfield

Key: X I 02 '

8-184

SNA Formats

MS Common Subvectors

Coded Character Set 10 (X'02') Self-Defining Text Message Subfield
Byte

Bit

2 -5( =q)

Content
Coded character set 10: 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 1121) Self-Defining Text Message Subfield
This subfield identifies the coded national language in which the text
message is written.

National Language 10 (X'12') Self-Defining Text Message Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the National Language 10 subfield

Key: X ' 12 1

2-4( =q)

National Language Code: a code point indicating the national language in
which the text message is written. A national language is identified by three
upper-case alpha EBCDIC characters from Coded Graphic Character Set
01134 -00500. The three character 10's are defined in Volume 2 of the National
Language Information and Design Guide, SE09 - 8002. For example, the American English would be identified in this field as XI C505E4 1 , which is decoded as
ENU. Other examples are: OEU for German, FRC for Canadian French and ENG
for UK English. Receivers are responsible for documenting the national language 10's that they support in this subvector.

Sender ID (X 1211) 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.

Sender 10 (X' 21') Self-Defining Text Message Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Sender 10 subfield

Key: X ' 21

Chapter 8. Common Fields

8-185

MS Common Subvectors

Sender ID (X' 21') Self-Defining Text Message Subfleld
Byte

Bit

Content

Sender 10 code: a code point characterizing the sender of the text message.
Defined codes are:
X 1 01 ' 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
application program: A program written for or by an end user that
X 1 11 '
applies to the end user's work
Note: This program may be implemented in either software or microcode.
X 1 12 '
control program: A program that controls other system resources.
Note: This program may be implemented in either software or microcode

2(=q)

Text Message (X I 30 ' ) Self-Defining Text Message Subfield

ihis subfield tiansports a text message.

Text Message (X' 30') Self-Defining Text Message Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Text Message subfield

Key: X 1 30 '

2-q

Text message

Relative Time (X' 42') MS Common Subvector

This MS common subvector indicates when a record was created relative to
other records created by the originating component.

Relative Time (X' 42') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Relative Time subvector

Key: X ' 42'

8-186

SNA Formats

MS Common Subvectors

Relative Time (X' 42') iViS Common Subvecior
Byte

Bit

Content

Time units:
X' 00'
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
microseconds
X'90'
X'AO' milliseconds
X'CO' minutes (not used in Alerts)
X'DO' hours (not used in Alerts)
X'EF' indicates time value is purely a sequence indicator showing relative
order only

3-6( =p)

Time, in binary, in the units defined by byte 2

Data Reset Flag (X'45') MS Common Subvector
This MS common subvector acknowledges that the reset function has been
performed.

Data Reset Flag (X' 45') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Data Reset Flag subvector

1( =p)

Key: X'45'

Supporting Data Correlation (X' 48') MS Common Subvector
This MS common subvector transports one or more tokens to be used by a
receiver for retrieval of additional data related to the event reported by the
Management Services Unit containing this subvector.

Supporting Data Correlation (X' 48') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Supporting Data Correlation subvector

Key: X'48'

2-p

One or more subfields, each containing one correlation token
Note: The following subfield keys are used as indicated:

Chapter 8. Common Fields

8-187

MS Common Subvectors

Presence in
Supporting Data
Correlator (X'48')
Corrrnon Sub vector

Subfield
Fully-qualified Session PCID (X'60')
Detailed Data (X'82')

Note 1

O(n)

Note 2

Conditions of Subfield Presence in Supporting Data Correlation Subvector

o
O(n)

Optionally present one time
Optionally present one or more times

Notes:

1. This subfield is present to indicate that the Alert sender has stored supporting data that can be retrieved by use of the Fully-qualified PCID present
in the subfield.
2. This subfield is present to indicate that the Alert sender has stored supporting data that can be accessed by use of the file or record identifier
present in the subfield.
Ful/y-qualified Session PCID (X' 60') Supporting Data Correlation Subfield
This subfield specifies the fully-qualified procedure correlation identifier
used to uniquely identify a session. When it flows in an Alert, this correlator
can then be used by the Alert receiver to retrieve session data from nodes
in the session path via the Request Trace (X' 8010 ')major vector-see SIR.

Fully-qualified Session PCID (X' 60') Supporting Data Correlation Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Fully-qualified Session PCID subfield

Key: X'60'

'2-9

PCID

Length, in binary, of network-qualified CP name (values 3 to 17 are valid)

11-q

Network-qualified CP name (NETID is not elided)

Detailed Data (X'82') Supporting Data Correlation Subfield
This subfield identifies either a file containing supporting data, or one or
more records within such a file. In both cases the identifications are meaningful to the Alert sender. The techniques needed to access or retrieve supporting data by means of the identifier contained in this subfield are not
defined by the architecture.

8-188

SNA Formats

MS Common Subvectors

Note: The format of this subfield is defined under the Alert (X' 0000') major
vector, in the section entitled "Network Alert (X'OOOO') Common Subfields" on
page 8-97.

LAN Link Connection Subsystem Data (X' 51 ') Supporting Data Correlation Subfield
This MS common subvector transports data on the elements of the LAN link
connection.

LAN Link Connection Subsystem Data (X' 51') Supporting Data Correlation Subfield
Byte

Bit

Content

Length (p + 1), in binary, of the LAN Link Connection Subsystem Data subvector

Key: X'51'

2-p

One or more subfields containing data specific to the link connection elements
(listed by Key value below and described in detail following):
X' 02'
Ring or Bus Identifier
X'03'
Local Individual MAC Address
Remote Individual MAC Address
X'04'
LAN Routing Information
X'05'
Ring Fault Domain Description
X'06'
Beaconing Data
X'07'
Single MAC Address
X'08'
Fault Domain Error Weight Pair
X'09'
X'OA' Bridge Identifier
Local Individual MAC Name
X'23'
Remote
Individual MAC Name
X'24'
Fault Domain Names
X'26'
Single MAC Name
X'28'

Ring or Bus Identifier (X'02') LAN Link Connection Subsystem Data Subfield
This subfield transports the ring number (for a token-ring LAN) or the bus
number (for a CSMA or token-bus LAN).

Ring or Bus Identifier (X' 02') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the ring or bus identifier subfield

Key: X'02'

2 -3( =q)

Ring or bus number, in hexadecimal

Chapter 8. Common Fields

8-189

MS Common Subvectors

Local Individual MAC Address (X 103 1) LAN Link Connection Subsystem Data Subfield

This subfield transports the address of the MAC within the node sending the
MS major vector.

Local Individual MAC Address (X' 03') LAN Link Connection Subsystem Data Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the local individual MAC address subfield

Key: X ' 03 1

2-7( =q)

Local individual MAC address, in hexadecimal

Remote Individual MAC Address (X 104') LAN Link Connection Subsystem Data Subfield

This subfield transports the address Qf the MAC, part of the link connection,
within the adjacent node.

Remote Individual MAC Address (X'04') LAN Link Connection Subsystem Data Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the remote individual MAC address subfield

Key: X ' 04 1

2-7( =q)

Remote individual MAC address, in hexadecimal

LAN Routing Information (X10SI) LAN Link Connection Subsystem Data Subfield

This subfield transports the routing information used by a link.

LAN Routing Information (X'OS') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the LAN routing information subfield

Key: X10SI

2 -q

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.

8-190

SNA Formats

MS Common Subvectors

Fault Domain Description (X 106 1) 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.

Fault Domain Description (X I 06 1 ) LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Ring Fault Domain Description subfield

Key: X ' 06 1

2-7

Individual MAC address of downstream station, in hexadecimal

8 -13( =q)

Individual MAC address of upstream station, in hexadecimal

Beaconing Data (X ' 071) LAN Link Connection Subsystem Data Subfield
This subfield specifies the type of beacon detected by the LAN adapter.

Beaconing Data (X ' 071) LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1). in binary, of the Beaconing Data subfield

Key: X ' 07 1

2(=q)

Beaconing type:
X I 01 1 type 1, recovery mode set
X 102 1 type 2, signal loss
X 103 1 type 3, streaming signal

Single MAC Address (X ' 08 1) LAN Link Connection Subsystem Data Subfield
This subfield transports the address of the MAC element associated with the
failure.

Single MAC Address (X' 08') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content
Length (q + 1). in binary. of the Single MAC Address subfield

Chapter 8. Common Fields

8-191

MS Common Subvectors

Single MAC Address (X' 08') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Key: X ' 08 1

2-7{=q)

Single MAC address, in hexadecimal

Fault Domain Error Weight Pair (X ' 09 1) 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.

Fault Domain Error Weight Pair (X'09') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Fault Domain Error Weight Pair subfield

Key: X ' 09 1

2-3

Severity weight, in binary, for the downstream MAC element (LAN station) problems

4-5{ =q)

Severity weight, in binary, for the upstream MAC element (LAN station) problems

Bridge Identifier (X lOA I) LAN Link Connection Subsystem Data Subfield
This subfield transports the bridge identifier of a LAN bridge.

Bridge Identifier (X' OA ') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Bridge Identifier subfield

Key: X'OA'

2-5

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 ,of this field into its three parts is not specified, but is
necessarily unique within a LAN.

8-192

SNA Formats

MS Common Subvectors

Local Individual MAC Name (X 123 1) LAN Link Connection Subsystem Data Subfield

This subfield transports the name of the MAC element within the sending
node.

Local Individual MAC Name (X' 23') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1). in binary, of the Local Individual MAC Name subfield

Key: X ' 23 1

2-q

Local individual MAC name: a string of no more than 16 upper-case alphanumeric E8CDIC four additional code points:
X 158 I
X '6C I
X 178 I
X '7C'

= $ (dollar sign)
= % (percent sign)
= # (pound or number sign)
= @ (at sign)

Remote Individual MAC Name (X'241) LAN Link Connection Subsystem Data Subfield

This subfield transports the name of the MAC element, part of the link connection, within the adjacent node.

Remote Individual MAC Name (X' 24') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Remote Individual MAC Name subfield

Key: X ' 24 1

2-q

Remote individual MAC name: a string of no more than 16 upper-case alphanumeric E8CDIC four additional code points:
X 158 I = $ (dollar sign)
X '6C I = % (percent sign)
# (pound or number sign)
X 178 I
@ (at sign)
X ' 7C'

=
=

Fault Domain Names (X'26 1) 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.

Chapter 8. Common Fields

8-193

MS Common Subvectors

Fault Domain Names (X' 26') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Ring Fault Domain Names subfield

Key: X'26'

2-q

Pair of Entries
Note: 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 a-origin).

Length (r+ 1), in binary, of the following name plus this length field

1-r

Individual MAC name: a string of no more than 16 upper-case alphanumeric
E8CDIC charac four additional code points:

$ (dollar sign)
X '58'
X'6C' = % (percent sign)
X '78' = # (pound or number sign)
X'7C' = @ (at sign)

Single MAC Name (X'2B') LAN Link Connection Subsystem Data Subfield

This subfield transports the name of the MAC related to the failure.

Single MAC Name (X' 28') LAN Link Connection Subsystem Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Single MAC Name subfield

Key: X'28'

2-q

Single MAC name: a string of no more than 16 upper-case alphanumeric
E8CDIC characters four additional code points:

X '58'
$ (dollar sign)
X '6C' = % (percent sign)
X '78' = # (pound or number sign)
X'7C'
@ (at sign)

Link Connection Subsystem Configuration Data (X' 52') MS Common Subvector
This MS common subvector transports data for link connections.

8-194

SNA Formats

MS Common Subvectors

Link Connection Subsystem Coniiguration Data (X' 52') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the LCS Configuration Data subvector

Key: X ' 52 1

2-p

One or more subfields containing LCS configuration data (listed by key value
below and described in detail following):
X I 01 1
Port Address
X ' 02 1 Remote Device Address
X ' 04 1
Local Device Address
X 106 1 LCS Link Station Attributes
X ' 07 1
LCS Link Attributes
X ' 08 1
LPDA Fault LSL Descriptor

Port Address (X'D11) Link Connection Subsystem Config. Data Subfield
This subfield transports the port address of the link connection.

Port Address (X' 01') Link Connection Subsystem Config. Data Subfleld
Byte

Bit

Content

Length (q + 1), in binary, of the Port Address subfield

Key: X I 01

2-3(=q)

Port address, in hexadecimal

Remote Device Address (X'D21) Link Connection Subsystem Config. Data Subfield
This subfield transports the DLC address of the remote link station.

Remote Device Address (X' 02') Link Connection Subsystem Config. Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the Remote Device Address subfield

Key: X ' 02 1

2( =q)

Remote link station DLC address, in hexadecimal; e.g., for a LAN, the destination link service access point (DSAP) address

....... -

Chapter 8. Common Fields

8-195

MS Common Subvectors

Local Device Address (X'04') Link Connection Subsystem Config. Data Subfield

This subfield transports the address of the local link station.

Local Device Address (X' 04') Link Connection Subsystem Config. Data Subfield

Byte

Bit

Content

Length (q + 1), in binary, of the Local Device Address subfield

Key: X'04'

2( =q)

Local link station DLC address, in hexadecimal; e.g., for a LAN, the source
service access point (SSAP) address

LCS Link Station Attributes (X'06') Link Connection Subsystem Config. Data Subfield

This subfield identifies link station attributes.

LCS Link Station Attributes (X' 06') Link Connection Subsystem Config. Data Subfield

Byte

Bit

Content

Length (q + 1), in binary, of the LCS Link Station Attributes subfield

Key: X'06'

Link station role:
X '01'
primary
secondary
X '02'
X '03'
negotiable

3( =q)

Node type for the remote link station:
X'01'
type 1
type 2.0
X '02'
X'03'
type 4
type 2.1
X '04'
X '80'
non-SNA, e.g., used for SSC links

LCS Link Attributes (X' 07') Link Connection Subsystem Config. Data Subfield

This subfield transports LCS link connection attributes.

8-196

SNA Formats

MS Common Subvectors

LCS Link Attributes (X' 07') Link Conr.ectlon Subsystem Conflg. D:lt:1 Subficld
Byte

Bit

Content

Length (q + 1). in binary, of the LCS Link Attributes subfield

Key: X ' 07 1

Link connection type used:
X I 01 1
nonswitched
X 102 I
switched

Half- or full-duplex:
X I 01 1
half-duplex
1
X ' 02
full-duplex

DLC protocol type:
X I 01 1
SDLC
X ' 02 1
sse
X ' 03 1
start-stop
X ' 04 1
LAPS

5(=q)

Point-to-point or multipoint:
X I 01 1
point-to-point
1
X ' 02
multipoint

LPDA Fault LSL Descriptor (X 108 1) Link Connection Subsystem Config. Data Subfield
This subfield transports the link segment identifier, also referred to as level,
of the multi-segment LPDA link where the failure occurred.

LPDA Fault LSL Descriptor (X' 08') Link Connection Subsystem Config. Data Subfield
Byte

Bit

Content

Length (q + 1), in binary, of the LPDA Fault LSL Descriptor subfield

Key: X ' 08 1

LPDA fault link segment level (LSL) descriptor value, in binary

Sense Data (X' 70 ') 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.

Chapter 8. Common Fields

8-197

MS Common Subvectors

Sense Data (X' 70 ') MS Common Subvector
Byte

Bit

Content

Length (p + 1), in binary, of the Sense Data subvector

Key: X ' 7D'

2-5{=p)

Sense data, as defined in Chapter 9, "Sense Data"

8-198

SNA Formats

Chapter 911 Sense Data
The sense data included with an EXCEPTION REQUEST (EXR), a negative
response, an UNBIND request, a Sense Data (X '7D I) MS common subvector, a
function management header type 7 (FMH-7), an extended sense data control
vector (X ' 35 1), or a SNA report code is a 4-byte field (see Figure 9-1) that
includes a 1-byte category value, a 1-byte modifier value, and two bytes of
sense code specific information, whose format is defined along with the sense
code definition, below.

Byte

Category

Modifier

Byte
3

Sense-code specific
infonnation

~Sense cOde~1
I.-------Sense D a t a - - - - - . I
Figure

9-1. 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

X'OO'
X'08'
X'10'
X'20'
X'40'
X'80'

CATEGORY
User Sense Data Only
Request Reject
Request Error
State Error
Request Header (RH) Usage Error
Path Error

The category User Sense Data Only (X1001) 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 XI 00 I. User Sense Data may not be sent on LU 6.2 sessions.
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.

Chapter 9. Sense Data

9-1

Request Reject (Category Code = X I 08 I)
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: The LU, PU, link station, or link specified in
an RU is not available.
8ytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-2

SNA Formats

0000

No specific code applies.

0003

Name aliasing cannot be performed because the name
alias function is not available~

0006

The line is not associated with a line adapater.

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 because it is being taken
down, and is therefore not accepting new sessions.
The initiation request should not be retried.

0008

The PLU is not available because it is unable to
comply with the PLU-SLU role specification.

OOOC

The SLU is not available because it is unable to
comply with the PLU-SLU role specification.

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.

0010

Switched subarea connection cannot be established
because no switched subarea links have been defined.

0011

Switched subarea connection to another network
cannot be established because no switched subarea
links have been defined within the gateway PU.

0014

A switched connection cannot be established. Call
Request Verification was requested, but is not supported for this configuration. This condition will result
from conflicting system definition.

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.

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-sess"ions 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
session limit 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.

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.
OOOC An LU-LU session was not established because a session
already exists between the SLU and the session-controller
PLU.

0806

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 inter-

Chapter 9. Sense Data

9-3

mediary on the session-setup path. A gateway SSCP examines the
Resource Identifier control vector in a session setup request (for
example, CDINIT), 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 anSNA Address List (X 1041) MS
common subvector are unknown to the PU receiving the
request.
Note: When this sense data flows in a -RSP(NMVT), the refer-

enced X 1041 subvector is the one that was present in the corresponding request NMVT. When this sense data flows in a
Sense Data (X 170 I) MS common subvector, the referenced
X 104 1 subvector is present with the X I 7DI subvector in the
same major vector.
0002

Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for
details of usage.

0007

The LU address in bytes 8 - 9 of RNAA type X 141 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.

9-4

SNA Formats

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 in the request.

0014

An unknown PLU name was specified in the request.

0015

An unknown OLU address was specified in 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
ssep is the SSCP having the DLU in its domain, but the
DLU is unknown to the receiving ssep.

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 LU1 name was specified in the request.

0025

An unknown LU2 name was specified in the request.

0026

The ssep does not have a session with the boundary function
PU of an independent LU.

0027

The PU associated with a switched SLU is unknown.
Session setup processing for the switched SLU cannot
proceed.

0028

NAU1 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.
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 10: The contents 10 contained on the ACTCORM
request was found to be invalid.

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:
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 dynamically reconfigured (ORed)
was defined at system-definition time and is defined 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.

001 A,001 B

Set aside for implementation-specific use, and will not
be otherwise defined in SNA; see implementation documentation for details of usage.

001 C

The RNAA request contains a network 10 that is not
known to the gateway PU.

Chapter 9. Sense Data

9-5

9-6

SNA Formats

001 D

An address pair session key in a Network-Qualified
Address Pair control vector (X 115 I) is not known to the
gateway PU.

001E

A gateway PU received an RNAA request for a crossnetwork session and all possible address transforms
for the named resource are allocated.

001 F

Retired

0020

The gateway node receiving an RNAA request cannot
support another session between the named resource
pair.

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 lOB I) 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 O.

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 receipt of 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 pendingreset 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.
Cleanup.
0035
080A

The termination type needs to be Forced or

A cross-domain resource, which was expected to
be active, is inactive.

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 10C I. (See the
X 10845 I sense code for a contrasting response.)
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

An SSCP has denied permission to establish a session
through its gateway resources; the receiving SSCP should not
attempt to reroute the request to another SSCP.

0002

An SSCP has denied permission to establish a session
through its gateway resources; the receiving SSCP should
attempt to reroute the request to another SSCP.

080B

Bracket Race Error: Loss of contention within the bracket protocol.
This error can arise when bracket initiation/termination by both
NAUs is allowed

080C

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 ' 086C'
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.

Chapter 9. Sense Data

9-7

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.

0000

An MS Request Change Control major vector was
received requesting post-test, but the receiver does not
support that function.

OOOE

An MS Request Change Control major vector was
received prohibiting automatic removal of a change, but
the receiver does not support that function.

OOOF

An Activate MS major vector was received from a
change management focal pOint specifying use of
changes installed in production only, but the receiver
supports such a request only when it is received
locally.

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.

oaoo

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 ACTCORM from the other SSCP before it receives the
response for an ACTCORM that it sent to the other SSCP and the
SSCP 10 in the received ACTCORM was less than or equal to the
SSCP 10 in the ACTCORM previously sent.

oaOE

NAU Not Authorized: The requesting NAU does not have access to
the requested resource.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

OaOF

0000

No specific code applies.

0001

The PU, according to its system definition, does not accept an
ACTPU from any SSCP having the network 10 of the sending
SSCP.

0002

A gateway T4 node received a request that is not valid from
an SSCP that is not in the native network of the gateway T4
node.

0003

The link station received a CONTACT from an unauthorized
SSCP.

0004

A BFCLEANU P was received from an unauthorized SSCP.

0005

An RNAA was received from an unauthorized SSCP.

End User Not Authorized: The requesting end user does not have
access to the requested resource.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

9-8

SNA Formats

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, UNBIND, or in
negative response to BIND.

0810

Missing Requester 10: The required requester 10 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 halfsession 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 the 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; no address was assigned and no
change was made to the LU's current reservation.

0007

Insufficient resources are available for LU address allocation.

OOOB A BFSESSINFO was received for an unknown LU.
0000 Insufficient buffers exist to activate a session.
0011
0813

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.
Note: For LU 6.2, this is the only setting defined.

0001

Bracket Bid Reject: The component was in the in-bracket
state when a bracket request was received.

Chapter 9. Sense Data

9-9

0002
0814

Bracket Bid Reject: The component was in the betweenbracket state when a bracket request was received.

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.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.
Note: For LU 6.2, this is the only setting defined.

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 thai 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.

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:

9-10

SNA Formats

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.

0818

Link Procedure in Process: CONTACT, DISCONTACT, IPL, or other
procedure in progress when a conflicting request was received.

lin~<

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 implementation 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.

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 sent. (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.

Chapter 9. Sense Data

9-11

0818

Receiver in Transmit Mode: A race condition exists: a normal-flow
request was received while the half-duplex contention state was notreceive, (*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.)

081C

Request Not Executable: The requested function cannot be executed, because of a permanent error condition in the receiver.
8ytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
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.

0081

An SOLC error was detected during link problem determination for a modem.

0082 A modem error (for example, modem check) was detected
during link problem determination.
0083 A timeout threshold was exceeded for a link problem determination aid modem response.
0084 An overrun or underrun occurred in the node using the link
connection during link problem determination for a modem.
0085 Data Check was signaled during LPOA-2 test.
0086 Format exception was signaled during LPOA-2 test.
0087 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 link connection status has not changed from
the state previous to the execution; if n = X' 8 I, the link connection status was modified from the state eXisting previous
to the execution. The error is specified as follows: m X111
for volatile storage error, m X' 2' for nonvolatile storage
(e.g., file access error), m X' 3 I for link connection component (e.g., modem) interface error, and m X 14' 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, 00A8,
0100-0109,0120-0125,0149,0189-0191, 0200-0209, 0220-0225,
0290,0291,07**, and 08** are all set aside for implementationspecific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0810

9-12

SNA Formats

Invalid Station/SSCP 10: The station 10 or SSCP 10 in the request
was found to be invalid.

081E

Session Reference Error: The request contained reference to a halfsession 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 during the processing of a session
services request.

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 Sessic;m 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 the
secondary half-session does not support cryptography.

0004

The secondary half-session requires cryptography, but the
primary half-session does not support cryptography.

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.

Chapter 9. Sense Data

9-13

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: A function requested in an FMD RU is
not supported by the receiver.

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
(fOi 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).

9·14

SNA Formats

082D

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.

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 (O-origin)
the first byte of the invalid count field.
Note: This sense code is not used for a BIND error because the dis-

placement 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 10835 1 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 (O-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 dis-

placement 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 XI 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.

Chapter 9. Sense Data

9-15

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.
nnnn Bytes 2 and 3 contain a two-byte binary count that indexes
(O-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 1086B 1 is used. If it occurs in an unformatted
subvector, sense code X 10870 1 is used.
0836

PLU/SLU Specification Mismatch: "For a specified LU-LU session,
both the origin LU (OLU) and the destination LU (OLU) have only the
primary capability or have only the secondary capability.

0837

Queuing Limit Exceeded: For an LU-LU session initiation request
(INIT, COINIT, or INIT-OTHER-CO) specifying (1) Initiate or Queue (if
Initiate not possible) or (2) Queue Only, the queuing limit of either
the OLU or the OLU, or both, was exceeded.

0838

Request Not Executable Because of Resource or Component State
Incompatibility: The request is not executable because it is not compatible with the state of a resource or component in the receiver.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-16

SNA Formats

0000

No specific code applies.

0001

The change referred to in a Request Change Control
MS major vector or Report-FS-Action command cannot
be deleted or replaced because it is installed marked
removable.

0002

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed,
removed, or accepted because they are in back-level
state (see Note).

0003

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
marked on-trial because they are already installed
marked on-trial (see Note).

0004

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
marked on-trial or in-production because they are
already installed marked in-production removably.
They can, however, be accepted if desired (see Note).

0005

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
marked on-trial or in-production because they are
already installed marked in-production and
non removable. The only possibility is to perform data
object renewal using Send-and-Install with removability
prohibited or desired-but not required (see Note).

0006

One or more of the changes referred to in a Request
Change Control MS major vector cannot be removed or
accepted because they are installed marked
nonremovable (see Note).

0007

One or more of the changes referred to in a Request
Change Control MS major vector cannot be removed or
accepted because they are not installed (see Note).

0008

Pre-test is not applicable to one or more of the changes
referred to in a Request Change Control MS major
vector (see Note).

OOOA

Automatic removal is not applicable to one or more of
the changes referred to in a Request Change Control
MS major vector (see Note).

0008

Post-test is not applicable to one or more of the
changes referred to in a Request Change Control MS
major vector (see Note).

0000

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
marked in-production because they are installed
marked on-trial with a set of corequisites different from
those requested on this install request.
One or more reported-on token strings are used to
identify the the corequisite changes currently installed
when the report code is carried in an SNA condition
report.

DaDE

One or more of the changes referred to in a Request
Change Control MS major vector cannot be accepted
because they are installed marked on-trial (see Note).

OOOF

One or more of the changes referred to in a Request
Change Control MS major vector or Report-FS-Action
command cannot be replaced or deleted because they
are critical system components that must always have
an installed instance. The only possibility is to perform
data object renewal using Send-and-Install with
removability prohibited or desired-but not required
(see Note).

0010

One or more of the changes referred to in a Request
Change Control MS major vector or Report-FS-Action
command cannot be stored or installed because an
implementation-defined limit on the number of changes
has been exceeded (see Note).

0011

One or more of the changes referred to in a Request
Change Control MS major vector or Report-FS-Action
command cannot be deleted or replaced because they
are required in order to maintain removability of other
changes. They may be in backup state or installed
marked in-production (see Note).

Chapter 9. Sense Data

9-17

0012

One or more of the corequisite changes referred to in a
Request Change Control MS major vector are missing
or are in a state incompatible with the request (see
Note).

0013

The change referred to in a Request Change Control
MS major vector or Report-FS-Action command cannot
be replaced because it is installed marked inproduction and non-removable and another change is
not being installed in this operation (see Note).

0014

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
because a precluded combination of values in the
Removability, Automatic Removal, Automatic Acceptance, or Activation Use subfields was specified (see
Note).

0015

One or more of the changes referred to in a Request
Change Control MS major vector cannot be installed
because one or more changes already installed are still
removable for one or more components to be altered
by these changes (see Note).

0016

One or more of the changes referred to in a Request
Change Control MS major vector or Report-FS-Action
command cannot be replaced because they would be
required for removable installation, and removability is
required (see Note).

Note: One or more reported-on token strings are used to identify
these changes when the report code is carried in an SNA condition
report.
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

RNAA(Type 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:
0000

9-18

SNA Formats

No specific code applies.

083B

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 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(lnitiate 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-Removed 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.

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
rink 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 reconfiguration; such a resource may not be
moved through RNAA(Move).

Chapter 9. Sense Data

9-19

0841

0010

A SETCV with control vector X ' 43 1 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 session 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 I LU 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.

9-20

SNA Formats

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(Oequeue) 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, SOT, 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

User Names Lost: An exception condition has resulted in the loss of
user names associated with the identified message unit.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

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

No specific code applies.

0003

The application transaction program specified in the request
is not available.

0005

Controller resource is not available.

6002

The resource identified by the destination program name
(OPN) is not supported.

6003

The resource identified by the primary resource name (PRN)
is not supported.

Chapter 9. Sense Data

9-21

6031

084C

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.

9-22

SNA Formats

0001

Set aside for implementation-specific use, and will not be otherwise d~fined in SNA; see implementation documentation for
details of usage.

0002

Creating Allocation Exception: The receiver is unable to
create the specified data object as a result of an insufficient
storage condition that occurred at allocation time. When this
SNA report code is used in an SNA condition report, it is
accompanied by one or more structure reports that identify
the allocation requests that failed.

0003

Replacing Allocation Exception: The receiver is unable to
replace the specified data object as a result of an insufficient
storage condition that occurred at allocation time. When this
SNA report code is used in an SNA condition report. it is
accompanied by one or more structure reports that identify
the allocation requests that failed.

0004

Reserved

0005

Reserved

0006

Data-Object Storing Exception: The receiver is unable to store
the specified data object as a result of an insufficient storage
condition that occurred during the storing process. When this
SNA report code is used in an SNA condition report. it is
accompanied by one or more structure reports that identify
containing the allocation requests that failed.

0007

Data-Object Classification Code Not Supported: The receiver
is unable to satisfy the allocation requirements of the specified data-object classification code. When this SNA report
code is used in an SNA condition report. it is accompanied by
a supplemental report containing the data-object classification
code that failed.

0008

Volume Not Mounted: The receiver is unable to perform the
requested allocation/storing operation because the required
volume is not mounted. When this SNA report code is used in
an SNA condition report. it is accompanied by a supplemental
report identifying the volume that was not mounted.

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 (O-origin) the first byte of the field found to be in error.
0840

Retired

084E

Invalid Session Parameters-PRI: A positive response 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: A requested resource is not available to
service the given request.
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; therefore. a received load module
cannot be stored.

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
0853

A second BIND has been received from a peripheral node
PLU while the session was still in the activation process.

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.

Chapter 9. Sense Data

9-23

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 SSCP(ILU)-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
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 in the process of being reactivated.

0002

The SSCP-PLU session is inactive.

0003

The SSCP-SLU session is inactive.

0004

The SSCP-PLU session is 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

Specific Server Exception: An architecturally defined or customerdefined server that is sensitive to data object contents, has detected
an exception.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

085B

No specific code applies.

Unknown Resource Name: The identified resource, required to complete the requested unit-of-work, is not known to the SNA node.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

085C

0000

No specific code applies.

0001

Unknown server name. When this SNA report code is used in
an SNA condition report, it is accompanied by a supplemental
report containing the server name.

0002

Unknown agent.

System Exception: The node experiences an exception condition
within a resident system or subsystem that inhibits subsequent processing by the SNA component.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-24

SNA Formats

085D

0000

No specific code applies.

0001

The exception is identifiable as a system-related problem.

0002

The exception is identifiable as a permanent system-related
problem.

The MUJD could not be accepted in the MUJD registry.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

085E

0001

The MUJD is a duplicate. When this SNA_REPORT_CODE is
used in an SNA_CONDITION_REPORT, it is accompanied by
three SUPPLEMENTAL_REPORTs that identify information
about the receiver's MUJD registry:
SUPPLEMENTAL_REPORT 1 contains the lowest MUJD the
receiver would accept; SUPPLEMENTAL_REPORT 2 contains
the highest MUJD the receiver would accept; .
SUPPLEMENTAL_REPORT 3 contains the time stamp of the
receiver's MUJD registry.

0002

The MUJD value is greater than expected. When this
SNA_REPORT_CODE is used in an SNA_CONDITION_REPORT,
it is accompanied by three SUPPLEMENTAL_REPORTs that
. identify information about the receiver's MUJD registry:
SUPPLEMENTAL_REPORT 1 contains the lowest MUJD the
receiver would accept; SUPPLEMENTAL_REPORT 2 contains
the highest MUJD the receiver would accept;
SUPPLEMENTAL_REPORT 3 contains the time stamp of the
receiver's MUJD registry.

0003

A temporary condition prevents acceptance of the MUJD.

0004

A permanent condition prevents acceptance of the MUJD.

0005

The MUJD registry is not initialized.

Operator Intervention
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

The operator has suspended the transmission of the message
unit.

0002

The operator has purged the message unit.

085F

Reserved

0860

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:

Chapter 9. Sense Data

9-25

nnnn Bytes 2 and 3 contain a 2-byte binary count that indexes
(O-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.
0861

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:

0862

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.

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 Bytes 2 and 3 following the sense code contain the byte offset
from the beginning of the RU to the first byte of the RU that is
displayed at the top of the current presentation space.

0863

Referenced Local Character Set Identifier (LCID) Not Found: A referenced character set does not exist.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
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 (O-origin) the first byte of the field found to be in error.
0864

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

9-26

SNA Formats

System Logic Error-No Retry: A system logic error has been
detected. No retry of the conversation should be attempted.
This sense data is sent only in FMH-7.

0002

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

Reti red

0866

Retired

0867

Sync Event Response: Indicates a required negative response to an
(RQE,CD) synchronizing request.

0868

No Panels Loaded: Referenced format not found because no panels
are loaded for the display.

0869

Panel Not Loaded: The referenced panel is not loaded for the
display.

086A

Subfield Key Invalid: A subfield key in an MS subvector was not
valid in the conditions under which it was processed.
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 unrecognized subfield,
and byte 3 contains the unidentified subfield key (mm).

086B

Subfield Value Invalid: A value in a subfield within an MS major
vector 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 1 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.

Chapter 9. Sense Data

9-27

0860

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:
nnmm 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.

086E

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 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.

086F

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:
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).

0870

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-28

SNA Formats

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.

Note: See sense code X 1086B I for the case in which 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

Explicit or Implied Orderly Deactivation Refused
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

An NC_DACTVR(Orderly) request has been received,
but sessions are assigned to the VR and it will not be
deactivated.

0001

An MS major vector specifying orderly deactivation of
the receiving node has been received, but sessions are
active and their implied deactivation is not allowed; the
requested activation will not proceed.

0002

An MS major vector specifying deactivation of the
receiving node has been received, but the receiver
cannot determine if sessions are active; the requested
activation will not proceed.

0873

Virtual Route Not Defined: No ERN is designated to support this
VRN.

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.
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.

Chapter 9. Sense Data

9-29

0003

Link Defined as Having Automatic Connect-Out 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.21.

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 determination 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.
0000 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.

9-30

SNA Formats

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 is not 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.

0013

The network 10 in the BIND SLU name is not equal to the
network 10 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 (bytes 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 1 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 10 1 or X 15 I
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 is 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.

001A 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.
001 B The target link station specified in a BFCLEANU P is not the
same link station as the session indicated in the URC control
vector.
001 C 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.

Chapter 9. Sense Data

9-31

001 D The LU address in a BFCINIT is a secondary address; the
BFCINIT is rejected.
001E

The subject LU specified in a BFSESSINFO RU is not defined
to the SSCP as an independent LU; this is a mismatch
between the SSCP and the BF.

001 F 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.
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.

9-32

SNA Formats

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 resource.

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 otherdomain resource that is not active or an application program
that is not active.

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. For
example, 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 linlt
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

0878

Takeover processing completed, but the SSCP did not receive
a BFSESSINFO for a resource that the SSCP believed to be a
static, independent LU.

Insufficient Storage: The storage resource required for a data format
is not available.
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 Exception: An exception has occurred involving a
storage medium.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

087 A

0000

No specific code applies.

0001

Disk I/O error.

0002

A non-recoverable I/O exception has been encountered.

Format Processing Error: A processing error occurred during data
formatting.

Chapter 9. Sense Data

9-33

0878

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 crossnetwork LU-LU session was not active.

0870

Session Services Path Error: A session 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.
8ytes 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 com-

pletely. 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.
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.

0004

Reserved

0005

Reti red

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.
0008 The DLU specified in the CDINIT is unknown to the receiving
SSCP, and the receiving SSCP cannot reroute the CDINIT.
087E

9-34

SNA Formats

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 sessionactivation 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
services request-CDINIT, INIT_OTHER_CD, NOTIFY(Vector
Key XI 01 1 ), 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.

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 is 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.

Chapter 9. Sense Data

9-35

0006

The specified DLU real network name is known, but is a duplicate resource.

0007

The specified DLU alias network name is known, but is a
duplicate resource.

0008

The specified OLU real network name is known, but is a duplicate resource.

0009

The specified OLU alias network name is known, but is a
duplicate resource.

0008 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.
0000 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

0889

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: The transaction program has detected
an error.
This sense code is sent only in FMH-7.
8ytes 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

Program Error-Data Truncation: The transaction program
sending data detected an error and truncated the logical
record it was sending.

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.

9-36

SNA Formats

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 107 I or X 108 I 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: The SSCP(DLU) is currently not
in 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.

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: The RU did not contain a control vector that
was expected to appear.
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 100 I •

0880

Duplicate Network Name: An SSCP has detected a violation of the
requirement that network names used across r11ultiple domains be
unique within the multiple-domain network. For example, the
SSCP(DLU) has detected that the OLU name received in CDINIT is
currently also defined in the domain of the SSCP(DLU).

088E

Capability Mismatch: A network component detected a capability
mismatch between different resources involved in the same network
function. For example, an SSCP detects that an LU has been
assigned a subarea address too large for one of the other resources
involved in the session initiation to support.
Bytes 2 and 3 following the sense code contains sense code specific
information. Settings allowed are:
0000

A resource encountered during LU-LU session initiation is not
ENA-capable; the session initiation request may be rerouted.

Chapter 9. Sense Data

9-37

088F

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.

0004

During a dynamic path update, the SSCP detected that the
update contained a path definition with an ER number greater
than 7 and that the target node does not support extended
subarea addresses. Therefore, the dynamic path update information for this destination subarea' was not forwarded to the
target node.

0005

The session could not be established because a specified
extended subarea address exceeded that allowed at a node
along the selected session setup path. The gateway SSCP
doing gateway node selection may retry the session setup by
selecting another gateway node having a larger subarea
address limit in the network containing the DLU.

0006

The session could not be established because a specified
extended subarea address exceeded that allowed at a node
along the selected session setup path. The gateway SSCP
doing gateway node selection may retry the session setup by
selecting another gateway node that uses a smaller subarea
address in the network containing the DLU.

0007

During a dynamic path update, the SSCP detected that the
update contained a path definition with a subarea address
above 255 and that the target node does not support extended
subarea addresses. Therefore, the dynamic path update information for the destination subarea was not forwarded to the
target node.

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-38

SNA Formats

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 SWITCH(Conditional, to backup) and no
current XRF-backup sessions exist that can replace this
session (that is, become the XRF-active.)

0006

An INITIATE request for an XRF-backup session was received
that allowed queuing (XRF-backup and session queuing are
mutually exclusive functions.)

0007

A COINIT or INITIATE request was received specifying an
XRF-backup session, and the OLU does not support XRF sessions.

0008

An XRF-active BINO was received with a session correlation
identifier that duplicates a session correlation identifier associated with an existing XRF session.

0009

An XRF-backup BINO was received for an LU that currently
does not have an XRF session.

OOOA Cryptography Not Supported: An XRF BINO was received indicating 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 (NETIO)
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

0892

0000

No specific code applies.

0001

PLU NETIO Invalid: The NETIO of the PLU is not the same as
that of the SSCP(PLU).

0002

Invalid NETIO: The NETIO field in CONNOUT does not match
the NETIO defined in the link station receiving the CONNOUT.

0003

Invalid NETIO: The NETIO field in the RNAA is not the same
as the native NETIO. There is a mismatch between the
system definitions of the SSCP and the type 4 node.

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.

0003

XRF-backup Session Reset. The XRF-backup session was
reset because the T4 node resets the session upon loss of the
SSCP.

Chapter 9. Sense Data

9-39

0893

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: The RU contained a control vector that was in
error.
xxyy

0896

0897

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 I OE I) 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.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-40

SNA Formats

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 10 (if present) in the SLU
Name field. is not equal to the networl< 10 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
SSCP(DLU) that differs from the SSCP(DLU) 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 in 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

0898

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:
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 1121.)

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

Chapter 9. Sense Data

9-41

resetting its half-session before receiving the response from
the partner LU. (See UNBIND type X'13'.)
0899

Invalid Address: An address modifying a control function is invalid,
or outside the range allowed by the receiver.
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: The requested file was not found, or
was found to be an invalid file.
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:
0000

No specific code applies.

0001

RUs Out of Order: A BIND request with the correlating fullyqualified PCID control vector (X 'SF') arrived before
UNBIND(Type X '02') was received for the correlated session.
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 'SF') cannot be correlated to
any previous session.

089C

Reserved

0890

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:

9-42

SNA Formats

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; another gateway node should be tried,

0004

Address conversion based on the subarea/element address
split was unsuccessful.

089E

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.

Identified Data Object Already Exists
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

08AO

0001

A request to create a new data object has failed
because the identified data-object already exists at the
target node.

0002

A request to replace a data object has failed because it
specifies a to-be-deleted data object different from the
to-be-stored data object; however, the to-be-stored data
object already exists.

Session Reset: An LU or PU is 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 lOA I
(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.

0002

The LU is sending UNBIND with a reason code of X 10F I
(cleanup).

0003

The gateway node is sending UNBIND with a reason code of
X 1111 (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.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

08A4

0000

No specific code applies.

0001

RNAA(MOVE) was received for an active resource.

Token-Match Exception: Partial name matching is unsuccessful
during the required find or store operation. The canonical identifier
involved in the exception is reported in the FS server report.
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-43

08A6

0001

One or more must-match tok~ns were not specified. When
this report code is used in an SNA condition report, it is
accompanied by a structure report containing the token-match
indicators, as specified in the request plus a supplemental
report containing the token attributes, as they appear in the
report's directory.

0002

Specified token-match indicators yield multiple directory
matches. When this report code is used in an SNA condition
report, it is accompanied by a structure report containing the
token-match indicators, as specified in the request plus a supplemental report containing the token attributes, as they
appear in the report's directory.

Object Not Found: An exception has occurred when the general
server attempted to process the server object, but the server object
could not be found.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0001

Server object not found.

Reauest Error (Cateaorv
Code
,~

= X'10'l.

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-44

SNA Formats

0000

No specific code applies.

0001

The request contains a subarea address of 0 or a subarea
address greater than the maximum subarea value within the
specified or implied network.

0002

The network 10 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: An incorrectly
formatted IPM was received.

0005

An RNAA 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.
0008 The value in the name length field is too great.

oooe

The value in 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.

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.
8ytes 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'15 1 ) 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 halfsession did not specify at session activation that it was
capable of supporting t~e function: consequently, there is an
apparent mismatch of half-session capabilities.

Chapter 9. Sense Data

9-45

Note: This is to cover a system error. For example, if the

SSCP sending a SETCV(Vector Key=X'15 1 ) 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.
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.

0000 The function identified in the request is not supported by the
processing application transaction program.

9·46

SNA Formats

0010

The RU is not known to session services.

0011

A session key is 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 a session-controller PLU.

0016

Service parameter not supported. When this SNA report code
is used in an SNA condition report, it is accompanied by a
supplemental report containing the one or more service
parameter triplets that are not supported.

0017

Service parameter level not supported. When this SNA report
code is used in an SNA condition report, it is accompanied by
a supplemental report containing the one or more service
parameter triplets that are not supported.

0018

Destination-role function not supported. When this SNA report
code is used in an SNA condition report, it is accompanied by
a structure report identifying the structure and containing the
contents that specified the one or more unsupported functions. Whenever the structure report is not sufficient to identify the, unsupported functions, the supplemental report may
also be present.

0019

All-role function not supported. When this SNA report code is
used in an SNA condition report, it is accompanied by a structure report identifying the structure and containing the contents that specified the one or more unsupported functions.
Whenever the structure report is not sufficient to identify the

unsupported functions, the supplemental report may also be
present.
001A Reserved.
001B Unable to initiate Agent.
001C Function conflicts with the SNA/DS Format Set 1 encodings.
When this SNA report code is used in an SNA condition
report, it is accompanied by a structure report identifying the
structure and containing the contents that specified the conflicting function.
001 D Reserved
001 E Reserved
001F

Multiple-destination traffic not supported. The reporting
location is a specialized, end-only role implementation that
supports single-destination traffic only.

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 the protocols (SSCP-independent or SSCP-dependent)
used by the designated LU partner. For example, a session
initiation request other than BFINIT identifies an independent
LU as a session partner.

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.
Note: This sense code can also be used instead of sense

code X ' OB26 1 •
1004

Reserved

1005

Parameter Error: A parameter modifying a control function is
invalid, or outside the range allowed 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

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.

Chapter 9. Sense Data

9-47

0007

The command in a Request Change Control MS major vector
is incompatible with the SNA/FS server instruction.

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:

1007

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 'Nithin the Node Idcntification field of an XID, was omitted.

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. An NS request byte 0 was not set
to a defined value.

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 indicated in UNBIND.
Bytes 2 and 3 following the sense code contain sense code specific
information. Figure 9-2 on page 9-54 shows the usage of the
allowed values by LU type. Settings allowed are:

9-48

SNA Formats

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 is not supported.

080B

The compaction table name is invalid.

080C

The ACCESS is invalid.

0800

The RECLEN is invalid.

080E

The NUMRECS is invalid.

080F

The data set is in use.

0810

The data set cannot be found.

0811

The password is invalid.

0812

The function is not allowed for the destination or for the
data set.

0813

The record is too long.

0814

The data set is full.

0815

The RECIO is invalid.

0816

Reserved

0817

The VOLIO format is invalid.

0818

The maximum number of logical records per chain is
exceeded.

0819

The data set exists.

081A

No space is available.

081 B

The VOLIO is invalid.

081C

The OS ACCESS is invalid.

0810

The RECTYPE is invalid or the data set cannot be
found.

081 E

The resolution space is insufficient.

081 F

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 KEYINO is invalid.

0824

The SERIO is invalid.

0825

Disk Error: An error was detected while reading from,
or writing on, the disk.

0826

The RECIO format is invalid.

0827

The password has not been supplied.

Chapter 9. Sense Data

9-49

9-50

SNA Formats

0828

The record 10 has not been supplied.

0829

The Volume 10 has not been supplied.

082A

The PGMNAME is invalid.

1204

Set aside for implementation-specific use, and will not
be otherwise defined in SNA; 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
s~tting is not defined.

200B

Invalid destination: The destination does not exist.

200C

The ERCL is invalid.

2000

The OST is invalid.

200E

Invalid Concatenation Indicator: The concatenation
indicator is on, but concatenation is not allowed.

200F

FM data is not allowed for the header.

2010

The FM header set specified in 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.

201 B

The CPI modification could not be accepted.

201C

The ECRL modification could not be accepted.

2010

FM Header and Associated Data Mismatch: The FM
header indicated associated data would or would not
follow (for 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 10846 1)) implied
that an FM header would follow, but none was received.

4001

Invalid FM Header Type for this LU: The type of the FM
header is other than 5, 7, or 12.

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.

4000

There are insufficient resources to perform the
requested function.

400E

DSP select is not supported.

6000

FM Header Length 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

The data stream profile (DSP) is invalid.

6007

The FMH-7 is not preceded by a negative response carrying the X 10846 1 sense code.

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.

6008

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.

6000

User to user program transition is not allowed.

Chapter 9. Sense Data

9-51

9-52

SNA Formats

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.

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.

6046

An SNA/DS transaction program is unable to allocate a
conversation with an SNA/DS partner.

6047

An SNA/DS transaction program in conversation with
an adjacent SNA/DS transaction program has detected
from LU 6.2 PS a return code of RESOURCE_FAILURE ..

6048

An SNAIDS transaction program in conversation with
an adjacent SNA/DS transaction program has detected
from LU 6.2 PS a return code of DEALLOCATE
Type(Abend).

COOO

The header is not supported.

C001

The header length is invalid.

C002

There has been a logical message services block-level
error.

C003

There is a version 10 mismatch.

1009

Format Group Not Selected: No format group was selected before
issuing a Present Absolute or Present Relative Format structured
field to a display.

100A

Unknown User Name
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0001

100B

The specified user name (e.g., origin, destination, or report-to)
cannot be identified with an entry in the directory.

Format Exception
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

No specific code applies.

0001

Required structure absent. When this SNA report code is
used in an SNA condition report, it is accompanied by a structure report that identifies the absent structure.

0002

Precluded structure present. When this SNA report code is
used in an SNA condition report, it is accompanied by a structure report that identifies the precluded structure.

0003

Multiple occurrences of a nonrepeatable structure. When this
SNA report code is used in an SNA condition report, it is
accompanied by a structure report that identifies and contains
the second occurrence of the structure.

0004

Excess occurrences of a repeatable structure. When this SNA
report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the
occurrence of the structure that exceeded the maximum, plus
a supplemental report that contains the allowed maximum
number of occurrences.

0005

Unrecognized structure present where precluded. When this
SNA report code is used in an SNA condition report, it is
accompanied by a structure report that identifies and contains
the precluded unrecognized structure, plus a sibling list of all
the allowed structures.

0006

Length outside specified range. This code assumes that the
length arithmetic balances and that the sender intended to
send the structure at that length. When this SNA report code
is used in an SNA condition report, it is accompanied by a
structure report that identifies and contains the header of the
excessively long structure, plus a supplemental report that
contains the allowed maximum length.

0007

Length exception. Length arithmetic is out of balance. When
this SNA report code is used in an SNA condition report, it is
accompanied by a structure report that identifies and contains
Chapter 9. Sense Data

9-53

Range

LU 1

LU 4

0801-0824

0825

0826-082A

2001-2000

200E

200F-20lC

LU 6.1

2010

4001-400E

6000

6001,6004

6005

6006-6008

6009

UUUI\

600B

600C-6010

I! f"'In

LU 6.2

6011-6034

6040

6041

6046

6047

6048

COOo-C003
Figure

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

the header of the structure that exceeded its parent's
boundary.

9-54

SNA Formats

0008

Required combination of structures absent. When this SNA
report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures that make
up the combination, indicating for each whether it was present
or absent.

0009

Precluded combination of structures present. When this SNA
report code is used in an SNA condition report. it is' accompanied by structure reports that identify the structures that make
up the precluded combination.

OOOA Required combination of structures and data values absent.
When this SNA report code is used in an SNA condition
report. it is accompanied by structure reports that identify the
structures and data values that are present. plus structure
reports that identify the absent structures needed to complete
the combination.
0008 Precluded combination of structures and data values present.
When this SNA report code is used in an SNA condition
report. it is accompanied by structure reports that identify the
structures and data values that make up the precluded combination.
OOOC Unknown or unsupported data value. When this SNA report
code is used in an SNA condition report. it is accompanied by
a structure report that identifies the structure and contains the
unknown or unsupported data value.
0000 Incompatible data values. When this SNA report code is used
in an SNA condition report. it is accompanied by structure
reports that identify the structures and the incompatible data
values.
OOOE

Precluded character present. When this SNA report code is
used in an SNA condition report. it is accompanied by a structure report that identifies the structure. indicates the· byte
offset of the offending byte. and includes the byte containing
the precluded code point.

OOOF

Data-value out of range. When this SNA report code is used
in an SNA condition report. it is accompanied by a structure
report that identifies the structure and contains the offending
data value. plus a supplemental report that contains the
maximum value allowed within the range (if a maximum range
value is applicable).

0010

Segmentation present where precluded. When this SNA
report code is used in an SNA condition report. it is accompanied by a structure report that identifies the structure that
should not have been segmented.

0011

Precluded data value. When this SNA report code is used in
an SNA condition report. it is accompanied by a structure
report that identifies the structure and contains the offending
data value.

0012

Recognized but unsupported structure. When this SNA report
code is used in an SNA condition report. it is accompanied by
a structure report that identifies the structure.

0013

None of several possible structures found. When this SNA
report code is used in an SNA condition report. it is accompanied by a structure report that identifies the parent of the
absent structure and may contain an unrecognized structure
that was found in the place of the absent structure. The structure report also contains a sibling list of the possible structures.

Chapter 9. Sense Data

9-55

0014

100C

Incorrect order of child structures found. When this SNA
report code is used in an SNA condition report, it is accompanied by a structure report that identifies the parent of the
incorrectly ordered child structures.

Unrecognized Message Unit
Bytes 2 and 3 following the sense code contain sense code specific
information. Specific settings allowed are:
0001

100D

The received byte stream could not be identified by the
receiving SNA component. When this SNA report code is
used in an SNA condition report, it is accompanied by a structure report identifying and containing the unrecognized
message unit, plus a sibling list of the allowed message units.

Request Inconsistency: The control information provided for the
request is not consistent with other information in the request.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

100E

0000

No specific code applies.

0001

Server object size is incompatible with service level. When
this SNA report code is used in an SNA condition report, it is
accompa.nied by one structure report containing the capacity
service parameter triplet and one supplemental report containing the server object size.

Directing Exception: A node is unable to perform the required
directing or redirecting function for a request as a result of insufficient directory support, or incompatibility between TP name and
presence/absence of a user name.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

100F

0000

No specific code applies.

0001

Agent name known but not supported for specified user destination.

0002

Agent name known but not supported for specified node destination.

0003

Agent name is known at this DSU but is not available.

Improper SNA/DS Usage of LU 6.2
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0001

1011

An SNA/DS transaction program in conversation with an adjacent SNA/DS transaction program has detected an improper
sequence of LU 6.2 basic conversation verbs.

RNAA Request Error: The RNAA is rejected because there is a mismatch between the sending and receiving nodes' system definitions,
~r capabilities.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-56

SNA Formats

1012

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 existing 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 10: If the network 10 field in the RNAA is not
the same as the native network 10 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.

SNA/OS Receiver Exception MU Format Exception: Parsing or
building of the SNA/DS Receiver Exception MU Format was unsuccessful.

Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000
1013

No specific code applies.

Unknown Server Parameters: The specified parameters are not
recognized by the server.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

1018

No specific code applies.

MU Sequence Exception: An SNA/OS transaction program has
detected an improper sequence of SNA/DS MUs.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0001

A OMU has been received, but the MUJO has already been
terminated.

0002

The MUJO state received from the partner is incompatible
with the state in the MUJO registry.

0003. Reserved

Chapter 9. Sense Data

9-57

1019

0004

A previous terminate conversation indication has been
ignored.

0005

An RRMU was received but was not followed by a
Change_Direction Indicator (Le., the Receive_And_Wait verb
issued after receiving the RRMU, returned something other
than What_Received = Send).

Invalid Restart Byte Position:
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-58

SNA Formats

0001

The restart byte position value specified in the DCMU is
greater than 1 plus the value of the last byte received in the
CRMU. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports
that identify the invalid restart byte position in the DCMU and
the values specified in the CRMU. Supplemental report 1 contains the restart byte position value in the DCMU. Supplemental report 2 contains the last structure received value in
the CRMU. Supplemental report 3 contains the last byte
received value in the CRMU. If this value was not specified in
the CRMU, this report will be omitted.

0002

The receiver does not support the byte-count restart elective,
and the restart byte position value specified in the DCMU is
not the beginning of the LLID structure following the last successfully received LLID structure. When this SNA report code
is used in an SNA condition report, it is accompanied by three
supplemental reports that identify the invalid restart byte position in the DCMU and the values specified in the CRMU: Supplemental report 1 contains the restart byte position value in
the DCMU. Supplemental report 2 contains the last structure
received value in the CRMU. Supplemental report 3 contains
the last byte received value in the CRMU. If this value was
not specified in the CRMU, the report will be omitted.

0003

The receiver supports the byte-count restart elective, and the
restart byte position value specified in the DCMU is not equal
to 1 and is less than or equal to the last byte received value
specified in the CRMU. When this SNA report code is used in
an SNA condition report, it is accompanied by three supplemental reports that identify the invalid restart byte position in
the DCMU and the values specified in the CRMU; Supplemental report 1 contains the restart byte position value in the
DCMU. Supplemental report 2 contains the last structure
received value in the CRMU. Supplemental report 3 contains
the last byte received value in the CRMU. If this value was
not specified in the CRMU, the report will be omitted.

State Error (CategonJ Code = X I 20 I)
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.
For LU 6.2, this category will be indicated within UNBIND or on negative
response to BIND.
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,
ECI), such as first, middle, first.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

2003

0000

No specific code applies.

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 inchain '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
information. Settings allowed are:

specifi~

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-$ession 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 halfsession 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.

Chapter 9. Sense Data

9-59

2008

No Begin Bracket: An FMD request specifying BBI = BB was
received after the receiver had previously received a BRACKET INITIATION STOPPED request.

2009

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 I 00 I if undetermined, appears in the fourth byte of the
sense data.

200A

Immediate Request Mode Error: The immediate request mode protocol has 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.

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

9-60

SNA Formats

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' Cede = }{ 140 I)
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 1 is invalid.

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 ECI = --, 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 session.

4009

CD Not Allowed: The Change Direction indicator (COl) was specified
incorrectly; for example, COl = CD with ECI = -, EC, or COl = CD with
EBI=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
(B81 = BB, CEBI = CEB, or EBI = EB), but brackets are not used for the
session.

4000

CD Not Supported: The Change-Direction indicator was set, but is
not supported.

400E

Reserved

Chapter 9. Sense Data

9-61

400F

Incorrect Use of Format Indicator: The Format indicator (FI) was
specified incorrectly; for example, FI was set with BCI = ..., BC, or FI
was not set on a OFC 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 = FMO.

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 (SOl, RTI): The Sense Data Included indicator (SOl) and the Response Type indicator (RTI) were not specified
properly on a response. The proper value pairs are (SOl = SO,
RTI = negative) and (SOl =..., SO, RTI = positive).

4014

Incorrect Use of (OR1I, OR21, ERI): The Definite Response 1 indicator
(OR11), Definite Response 2 indicator (OR21), and Exception
Response indicator (ERI) were specified incorrectly; for example, a
SIGNAL request was not specified with OR11 = OR1, OR21 = ..., OR2,
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 EOI: The Enciphered Data indicator (EOI) was speci.
fied incorrectly; for example, EOI =EO on a OFC request.

4017

Incorrect Use of POI: The Padded Data indicator (POI) was specified
incorrectly; for example, POI = PO on a OFC request.

4018

Incorrect Setting of QRI with Bidder's BB: The first speaker halfsession received a BB chain requesting use of a session (via
LUSTAT(X 10006 I)), 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 COl = ..., CD.

401A
through
4020
4021

9-62

SNA Formats

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

80 I )

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 120 I. 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.

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 ACTLUI ACTPU(Cold) 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: Backup session reset resulted from a
hierarchical reset.

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.

Chapter 9. Sense Data

9-63

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 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.

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:

9-64

SNA Formats

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 is in 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 secondary half-session in the receiving
node has not been activated and the request was not ACTPU for this
half-session; for example, the request was ACTLU from an SSCP that
does not have an active SSCP-PU session with the PU associated
with the addressed LU.

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. (See
Note 1 located at the end of this chapter).

800C

DCF Error: Data Count field inconsistent with transmission length.

8000

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 18002 I) is sent.

800E

Unrecognized Origin: The origin address specified in the TH was not
recognized.

800F

The address combination is invalid.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
0000

The (OAF', OAF') (FID2) combination or the LSID (FID3) specified an invalid type of session, for example, a PU-LU combination.

0001

The FID2 ODAI setting in a received BIND is incorrect; the
BIND is rejected.

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 ther'e
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 activatio~ 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

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

No Specific Code Applies: This means an error occurred, but
none of the conditions listed below applies.

Chapter 9. Sense Data

9-65

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.

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.

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.

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.

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 operative ER that could be activated.

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.

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 106 1 is reported. The hierarchy of the failure
reasons is in ascending numeric order, that is, reason X 1021 is
higher than reason X I 01 1 •

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.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

9-66

SNA Formats

8019

0000

No specific code applies.

0001

The application transaction program specified in the request
is not recognized by PUMS.

Routing Exception: A node is unable to perform the required routing
function for a request.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:

801C

0000

No specific code applies.

0001

Unknown routing group name.

0002

Unknown routing group name, routing element name combination.

0003

Reserved

0004

No connection is available for level of service required. When
this SNA report code is used in an SNA condition report, it is
accompanied by a supplemental report containing the one or
more service parameter triplets for which a connection could
not be found.

Hop Count Exhausted
0001

8020

The request has been forwarded by an excessive number of
nodes (e.g., the count has been decremented at each node
and has reached 0) and, therefore, the request could not be
delivered to one or more destinations. Typically, this exception indicates that one or more nodes have incorrectly routed
or directed the request. The exception may also indicate that
the routing/directing count was not appropriately initiated
according to network size.

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.

Chapter 9. Sense Data

9-67

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 (FlO, 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-68

SNA Formats

Chapter 10. Function Management (FM) Headers
The request header (RH) contains a format indicator (FI) that, when on, indicates that an FM header is at the beginning of the request unit (RU).
FM headers appear 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:

I RH:

FHH, *BC,*EC

FH header

Data

Figure 10-1. FM Header Contained in One RU

I RH:
RH:

FHH,

*BC,~EC

First of FH header

Rest of FH header

~FHH,~BC,*EC

Data

Figure 10-2. FM Header Contained in Two Contiguous RUs of a Chain

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.

FHH

I
I

FHH

I FHH I Data

FHH

FHH
GDS
TH
RH

-----

Note:

Data

GDS

(see Note)

I Data I GDS I Data

Function Hanagement (FH) Header
General Data Stream identifier
Transmission Header
Request/Response Header
In lU type 6.2 a maximum of one FH header per RU is allowed.

Figure 10-3. Usage of FM Headers

Chapter 10. Function Management (FM) Headers

10-1

LU Type

FM Header Type

None required, but may use any header

1, 2, 3

None

1, 2, 3

6.1

4, 5, 6, 7, 8, 10

6.2

5, 7, 12

None

Figure 10-4. LU Types That Support FM Headers

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-1.

FM Header 1
Byte

Bit

o
1

Length, in binary, of FMH-1, including this Length byte

o
1-7

10-2

Content

SNA Formats

FMH concatenation:
no FMH follows this FMH-1
1
another FMH follows this FMH-1
Type: 0000001

FM Header 1

Byte

Bit

Content

0-3

Select desired medium for data (see Notes 1 and 2):
0000
console
0001
exchange
0010
card
0011
document
0100
non exchange 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
Logical subaddress (see Note 2):
0000-1110
specific device in medium class
1111
any device in m~dium class (see Note 3)

4-7

o
1

2-3
4-7

SRI: stack reference indicator:
stack to be used is the sender's send stack
1
stack to be used is the receiver's send stack
Demand select:
o receiver may direct data to alternate medium/subaddress
1
receiver must direct data to specified medium/subaddress (spooling is prohibited)
Reserved
DSPs: data stream profiles:
0000
default (the DSP 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
1101
reserved
1110
reserved
1111
reserved

Chapter 10. Function Management (FM) Headers

10-3

FM Header 1
Byte

Bit

4
0-2

4
5

7
5

0 -7

Content
FMH-1 properties
DSSEL: destination selection:
000
resume
001
end
010
begin
011
begin/end
100
suspend
101
end-abort
110
continue
111
reserved
DST: data set transmission (see Note 6):
o transmission exchange format
1
basic exchange format
. Reserved
CMI: compression indicator (see Notes 4 and 5):
o no compression
1
compression (the first byte following FMH(s) is a string control byte)
CPI: compaction indicator (see Notes 4 and 5):
o no compaction
;
compaction (the first byte foiiowing the FMH(s) is a siring coniroi byte)
Reserved

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

6-7

Reserved (optional)

DSLEN: length of destination name (optional)

g-n

DSNAME: destination name (optional; reserved when DSSEL

Notes:

= continue)

1. The data stream profile (DSP) defaults for the Medium Select field are:
FMH-1 MEDIUM SELECT

DEFAULT DSP

Console, XIOI
Exchange, X 111
Card, X 121
Document, X I 3 1
Nonexchange Disk, X 141
Extended Document,X 15 I
Extended Card, X 16 I
WP Medium 1, X I 8 1
WP Medium 2, Xigi
WP Medium 3, XIAI
WP Medium 4, XICI

Base
DST field of FMH-1
SCS (I RS, TRN)
Subset 2 (RJE)
DST field of FMH-1
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-1. This
selection adheres to those DSPs allowed on the session as specified in the
BIND parameters.

10-4

SNA Formats

FM Header 1
Syta

Sit

Content

2. 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).
3. If Medium Select = X 17 1 and Logical Subaddress = XI F I, the Destination
Name (DSNAME) field is used to select destination.
4. CMI, CPI, and ERCL indicators are meaningful and valid only when specified
in a Begin, Begin/end, or Continue FMH-1.
5. CMI, CPI, and ERCL information received when DSSEL = Continue overlays
the settings of the Begin FMH-1 or the last-received Continue FMH-1.
6. When Medium Select is not equal to Exchange, this field is reserved.
Receiver may do spooling and exchange-medium creation locally. When
Exchange, specifying 0 preserves chain boundaries while
Medium Select
spooling, but nonsequential allocation techniques may be used. Specifying
1 does not preserve chain boundaries, but uses sequential medium allocation.

FM Header 2
Once a destination has been selected using a FMH-1, this header handles
the data management tasks for that destination.

FM Header 2
Byte

Bit

o
1

Length, in binary, of FMH-2, including this Length byte

o
1-7

1-7
3-n

Content

FMH concatenation:
no FMH follows this FMH-2
1
another FMH follows this FMH-2
Type: 0000010

SRI: stack reference indicator (see Note below):
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
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 SNA: Sessions Between Logical Units.)

Chapter 10. Function Management (FM) Headers

10-5

FM Header 2
Byte

Bit

Content
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:

Note:

Function Code
X 1 01

X ' 02 1
X ' 04 1
X ' 07 1
X ' 20 '
X ' 21 1
X ' 22 1
X ' 23 1
X ' 24 1
X ' 25 1
X ' 26 1
X ' 27 1
X ' 28 1
X ' 29 1
Xl 2BI

X' 2C'
X ' 20 '

X ' 2E'
X'AA'

Function
Peripheral data information record (POIR)
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 10
Note reply (SRI is always on)

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 1
X ' 03 1
X ' 04 1
X ' 05 1
X ' 06 1

10-6

SNA Formats

Function
Compaction table
Query for compaction table
Prime compression character
Status
Series 10

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.

FM Header 4
Byte

Bit

o
1

Content
Length, in binary, of FMH-4, including this Length byte

o
1-7

FMH concatenation (must be 0)
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 100 I
inherit code (from MM-TT register)
I
1
X 01 -X ' 3F'
reserved
X ' 40 '
FFR-FNI record
X ' 41 1 FFR-FS record
X 1421
FFR-FS2 record
1
reserved
X 143 -X '4F I
X ' 50 ' -X'FE'
reserved
X I FF I 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
FMH4TT1 =X ' 41 1 or X ' 42 1, in which case it holds the separator value

FMH4CMD: command:
XIOOI
CRT-NU-BLK
1
X ' 02
CRT-SU-BLK
X 103 I
CRT-SN-B LK
X I 10 1 CONT-NU-BLK
X ' 12 1 CONT-SU-BLK
X ' 13 1 CONT-SN-BLK
X 123 I
DEL-SN-BLK
U PD-SU-BLK
X 132 I
X 133 I
U PD-SN-BLK
X ' 42 1 RPL-SU-BLK
X ' 43 1 RPL-SN-BLK
Note: NU = nonshared, unnamed; SU = shared, unnamed; SN = shared, named;
NN = nonshared, named

Chapter 10. Function Management (FM) Headers

10-7

FM Header 4
Byte

Bit

0-1

2-3

4-5
6

Content
FMH4FLAG: flags (if omitted, X I 00 I is assumed):
Reserved
F4RDESCR: record descriptor flag:
00
no logical record headers (LRHs) in transmission block
01
LRHs present, with implicit lengths
10
reserved
11
reserved
Reserved
FMH4BDTF: block data transform flag:
a FMH4BDT absent
1
FMH4BDT present
FMH4RDTF: reserved

FMH4LBN: length of FMH4BN (X 100 1, or omitted, if unnamed block)

8-m

FMH4BN: name of block

m+1

FMH4LBDT: length of FMH4BDT (XIOOI if FMH4BDTF is 0)

m+2-n

FMH4BDT: block data transform

n+1

FMH4LVID: length of FMH4VID

n+2-p

FMH4VID: version identifier

FM Header 5: Attach (LU 6.2)
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
transaction 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-5 carries the transaction program name (TPN) to the receiving LU.

FM Header 5: Attach (LU 6.2)
Byte

Bit

a
1

Length, in binary, of FMH-5, including this Length byte

o
1-7

Reserved
Type: 0000101
. Command code: X I 02FFI (Attach)

2-3

10-8

Content

SNA Formats

FM Header 5: Attach (LU 0.2)
Byte

Bit

Content

Security indicator:
user ID is not already verified
1
user ID is already verified
Reserved
Program initialization parameter (PIP) presence:
o PIP not present following this FMH-5
1
PIP present following this FMH-5 (see" PIP Variable" on page 10-10 for
format)
Reserved

1-3
4

5-7

Length (j-5), in binary, of Fixed Length Parameters field (currently 3-future
expansion possible)

6-j

Fixed Length Parameters

Resource type:
X 1DO 1 basic conversation
XI D11
mapped conversation

Reserved

8{ =j)

0-1

2-7

Synchronization level:
00
none
01
confirm
10
confirm, sync point, and backout
11
reserved
Reserved

j+1-p

Variable Length Parameters

j+1-k

Transaction Program Name Field:

j +1

Length (values 1 to 64 are valid), in binary, of transaction program name

j+2-k

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

k+1-m

Access Security Information Field:

k+1

Length (O or m-k-1), in binary, of Access Security Information subfields

k+2-m

Zero or more Access Security Information subfields (see "Access Security Information Subfields" on page 10-10 for format)

m+1-n

Logical-Unit-of-Work Identifier Field:

m+1

Length (values 0 and 10 to 26 are valid), in binary, of Logical-Unit-of-Work Identifier field

m+2-n

Logical-Unit-of-Work Identifier

m+2

Length (values 1 to 17 are valid), in binary, of network-qualified LU name

m+3-w

Network-qualified LU network name (format described in Chapter 7, "User Data
Structured Subfields")

w+1-w+6

Logical-unit-of-work instance number, in binary

Chapter 10. Function Management (FM) Headers

10-9

FM Header 5: Attach (LU 6.2)
Byte

Bit

Content

w+7-w+8{=n)

Logical-unit-of-work sequence number, in binary

n+1-p

Conversation Correlator Field:

n+1

Length (values 0 to 8 are valid), in binary, of conversation correlator of sender

n+2-p

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+1, m+1, and k+1) that have value X1001 can be
omitted.

Access Security Information Subfields
The Access Security Information subfields in FMH-S have the following formats:

Access Security Information Subfields
Byte

Bit

Content

Length (valid values are 1 to 11), in binary, of remainder of subfield-does not
include this Length byte

Subfield
XI 00 1
X 101 1
X ' 02 1

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 (X'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.

type:
profile
password
user 10

PIP Variable
The PIP variable following FMH-S Attach has the following format:

10-10

SNA Formats

PIP Vailabla
Byte

Bit

Content

0-1

Length (4 or n + 1), in binary, of PIP variable, including this Length field

2-3

GDS indicator: X I 12F5 1

4-n

Zero or more PIP subfields, each of which has the following format (shown in
"PIP Subfield" using O-origin)

PIP Subfleld: Zero or more of these subfields are contained in a PIP variable (see" PIP Variable").

PIP Subfleld
Byte

Bit

Content

0-1

Length, in binary, of PIP subfield, including this Length field

2-3

GDS indicator: X112E21

4-m

PIP subfield data: type-G symbol string is valid

FM Header 5: Attach (Not LU 6.2)
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-5 can
be followed by other FMHs (for example, FMH-6, FMH-B, and FMH-4), a
logical record header (LRH), and FM data. Optionally, it can be sent with
CD or EB.

FM Header 5: Attach (Not LU 6.2)
Byte

Bit

o
1

Content
Length, in binary, of FMH-5, including this Length byte

o
1-7

FMH concatenation:
no FMH follows this FMH-5
1
another FMH follows this FMH-5
Type: 0000101

2-3

FMH5CMD: command code:
X 10202 1 attach transaction program
X 10204 1 reset attached process
X 10206 1 data descriptor

FMH5MOD: modifier

Chapter 10. Function Management (FM) Headers

10-11

FM Header 5: Attach (Not LU 6.2)
Byte

Bit

Content
FMH5FXCT: fixed-length parameters:
reset attached process
X '02'
attach transaction program, data descriptor

X'OO'
6

ATTDSP

ATTDBA

8-n

Resource names

FM Header 6
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.

FiVi Header 6
Byte

Bit

o
1

Content
Length, in binary, of FMH-6, including this Length byte

o
1-7

2-3

FMH concatenation:
no FMH follows this FMH-6
1
another FMH follows this FMH-6
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.

o
1-7

FMH6MOD: modifier
FMH6LNSZ: length of parameter length fields:
o 1-byte field
1
2-byte field
Reserved

5-n

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).

n+1-m

Fixed length parameters (FDy): the fixed length parameters are positional by
command code

m+1-p

Variable: length field of first, positional variable-length parameter (LV1): 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 + 1.

10-12

SNA Formats

FM Header 6
Byte

Bit

p+1-q

Content

Variable-length positional parameter (VO). The LV and VO fields are replicated
to represent x number of variable-length parameters according to command
code.

FM Header 7: Error Description (LU 6.2)
LU type 6.2 uses this header, following a 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.

FM Header 7: Error Description (LU 6.2)
Byte

Bit

o
1

Length (7), in binary, of FMH-7, including this Length byte

o
1-7

2-5
6

Content

Reserved
Type: 0000111
SNA-defined sense data (see below)

o
1-7

Error log variable presence:
no error log variable follows this FMH-7
1
error log GOS variable follows this FMH-7
Reserved

Chapter 10. Function Management (FM) Headers

10-13

FM Header 7: Error Description (LU 6.2)
Byte

Bit

Note:

Content
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 LV Type 6.2) when the sense data is received.

Sense Data
1008600B
10086021
10086031
10086032
10086034
10086041
080F6051
08240000
084B6031
084COOOO
08640000
08640001
08640002
08890000
08890001
08890100
08890101

Return Code
RESOU RCE_FAI LURE_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_SU PPORTED_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

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.

FM Header 7: Error Description (Not LU 6.2)
Byte

Bit

o
1

Content
Length, in binary, of FMH-7, including this Length byte

o
1-7

FMH concatenation:
no FMH follows this FMH-7
1
reserved
Type: 0000111

2-5

ERPSENSE: SNA-defined sense data, which would appear on error response
(see Chapter 9. "Sense Data" on page 9-1)

6-7

ERPSEQ: sequence number of RU chain in which error was detected

10-14

SNA Formats

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.

FM Header 10
Byte

Bit

Length. in binary. of FMH-10. including this length byte

Content

1-7

FMH concatenation:
no FMH follows this FMH-10
1
another FMH follows this FMH-10
Type: 0001010

2-3

SPCCMD: sync point command:
X 10202 1 Prepare command

4-5

SPCMOD: sync point modifier
For a Prepare command (FMH-10). the modifier indicates RH settings to be
returned on the first RU chain sent by the FMH-10 receiver.
X100001
wCD. wEB: The sender of FMH-10 does not care what RH settings
are returned on the reply.
X 100011
EB: The sender of FMH-10 requires an EB on the reply.
X 100021
CD • ...., EB: The sender of FMH-10 requires a CD on the reply.

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:

FM Header 12: Security
Byte

Bit

Content
Length (10). in binary. of FMH-12. including this Length byte.

Chapter 10. Function Management (FM) Headers

10-15

FM Header 12: Security
Byte

Bit

Content

Reserved
Type: 0001100

1-7
2- 9

10-16

Enciphered version of the random data received in RSP(BIND)

SNA Formats

Chapter 11. Presentation Servic2s (PS) 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 with
the sync-point synchronization level. These headers are used only by LU type
B.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).

transaction program data

All PS headers are identified by an LL of X 100011 immediately preceding the
header. X 100011 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.

PS Header 10: Sync Point Control
Presentation services header 10 (Sync Point Control) has the following
format:

PS Header 10: Sync Point Control
Byte

Bit

o
1

Length, in binary, of PS header, including this length field

o
1-7

2-3

Content

Reserved
Type: 0001010 sync point control (only value defined)
Sync point command type:
X ' 0005 1 Prepare
X'OOOB'
Request Commit
X ' 0007 1 Committed
X ' 0008 1
Forget
X 10009 1 Heuristic Mixed

Chapter 11. Presentation Services (PS) Headers

11-1

PS Header 10: Sync Point Control
Byte

Bit

Modifier specifying next flow (present only if bytes 2-3 = X ' 0005 1 or X ' 0006 1;
reserved when bytes 2 - 3 = X 10006 I and 2-phase sync point being used):
XIOOOOI
request RECEIVE
X I 0001 1 request DEALLOCATE
request SEND
X 100021
Note: Bytes 4 - 5 affect the Change Direction indicator (COl) 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, and Committed command type when Request Commit
was the first PS header received.

4-5

11-2

Content

S NA Formats

GDS Variables for SNA STPs

Chapter 12. GDS Variables for SNA Service Transaction
Programs (STPs)

List of SNA Service Transaction Programs
Logical Unit type 6.2 service transac1ion programs are identified by a transaction program name (TPN) that begins with a value of X 106 1. 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 (FMH-5 Attach).

TP Name

TP Description

X'06F1'
X'06F2'

LU 6.2 Change number of sessions
LU 6.2 SYNC POINT resynchronization

X' 07FOFOFl'

DOH Synchronous Conversation

X'20FOFOFO'
X'20FOFOFl'
X'20FOFOF2'

DIA Process Destination TP
DIA Server TP
DIASTATUS TP

X'21FOFOFl'
X'21FOFOF2'
X'21FOFOF3'
X'21FOFOF6'
X'21FOFOF7'
X'21FOFOFB'
X'24FOFOFO'
X'30FOFOF2'
X' 30FOFOF3 '

OS SEND TP
(FS1)
DS:RECEIVE TP (FS1)
OS ROUTER DIRECTOR TP
OS-General Server TP
os SEND TP (FS2)
DS:RECEIVE TP (FS2)
FS server TP
Object Distribution TP
Object Distribution Server TP

Figure 12-1. SNA-Defined Service Transaction Programs

Refer to Chapter 13, "SNA/Oistribution Services (OS)" for additional SNADS
information and refer to Chapter 14, "GDS Variables for General Use" for information about GOS variables that are not specific to SNA service transac1ion
programs.

Descriptions of GDS Variables for SNA STPs
Change Number of Sessions (X' 1210') GDS Variable

Chapter 12. GDS Variables for SNA STPs

12-1

GDS Variables for SNA STPs

Change Number of Sessions (X' 1210') GDS Variable
Byte

Bit

Content

0-1

Length (17 or n + 1), in binary, of Change Number of Sessions GDS variable,
including this Length field

2-3

GDS 10: X ' 1210 '

4
0-3

4-7

Service flag:
Reserved
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 100 I
normal-no negotiation performed
X 1011
abnormal-command race detected
X ' 02 1 abnormal-mode name not recognized
rese rved
X 103 I
normal-negotiated reply
X 104 I
1
X 105
abnormal-(LU,mode) session limit is 0

Action:
set (LU,mode) ses'sion limits
X 100 I
I
1
reserved
X 01
X ' 02 1 close

7
0-2
3

4-6
7

0-6
7

Drain immediacy:
Reserved
Source LU drain (reserved if byte 6 02):
o no (send BIS at next opportunity)
1
yes
Reserved
Target LU drain (reserved if byte 6 02):
o no (send BIS at next opportunity)
1
yes

Action flags:
Reserved
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.

9-10

o
1-15
11-12

o
1-15

12-2

SNA Formats

(LU,mode) session limit:
Reserved
Maximum (LU,mode) session count, in binary
Source LU contention winners:
Reserved
Guaranteed minimum number of contention winner sessions at source LU, in
binary

GDS Variables for SNA STPs

Change Number of Sessions (X' 1210') GOS Variable
Byte

Bit

Content

0
1-15

Target LU contention winners:
Reserved
Guaranteed minimum number of contention winner sessions at target LU, in
binary

13-14

15
0-6
7

Mode name selection:
Reserved
Mode names affected by this command:
o a single mode name is affected
1
all mode names are affected (valid if byte 6

= 02)

Length (values 0 to 8 are valid; reserved if byte 15, bit 7
mode name

17-n

Mode name (omitted if byte 16 = X 100 I)

= 1), in binary, of

Exchange Log Name (X '1211 ') GDS Variable

Exchange Log Name (X' 1211 ') GOS Variable
Byte

Bit

Content

0-1

Length (p + 1), in binary, of Exchange Log Name GOS variable, including this
Length field

2-3

GOS 10: X I 1211 1

0-3

4-7

5
0-6
7

Service flag:
Reserved
Request/reply indicator:
0010
request
1000
reply, function completed abnormally
1001
reply, function completed normally
Sync point manager flags:
Reserved
Log status:
o cold
1
warm

Length (values 1 to 17 are valid), in binary, of network-qualified LU network
name

7-n

Network-qualified LU name (format described in Chapter 7, "User Oata Structured Subfields")

n+1

Length (values 1 to 64 are valid), in binary, of log name

n+2-p

Log name: a type-AE symbol string

Chapter 12. GDS Variables for SNA STPs

12-3

GDS Variables for SNA STPs

Control Point Management Services Unit (X' 1212') GOS Variable
CP-MSU carries MS requests and data in general data stream (GOS) format.

Control Point Management Services Unit (X'1212') GOS Variable
Byte

Bit

Content

0-1

Length (m + 1), in binary, of the CP-MSU.

2-3

GOS 10: X ' 1212 1

4-m

One MS major vector, as described (using O-origin indexing) in "MS Major
Vector Formats" on page 8-13, and/or one or more of the following GOS variables if appropriate:
X 11532 1 SNA Condition Report: documented in Chapter 15, "SNA/File Services (FS)." Present if an SNA-registered condition was recognized
by the management services SNA/OS agent at the sending node,
except in the case of SNA/File Services errors (when the report is
contained within the FS Action Summary).
X 11548 1 FS Action Summary: defined by SNA/File Services. Present in a
management services reply MU if a server object requesting SNA/FS
action was present in the management services request MU.
Note: For some conditions (for example, parsing errors where the command is
not recognized, or SNA/File Services errors that occur prior to MS command
execution), the major vector may be omitted.

Compare States (X' 1213') G OS Variable

Compare States (X'1213') GOS Variable
Byte

Bit

Content

0-1

Length, in binary, of Compare States GOS variable, including this Length field

2-3

GOS 10: X ' 1213 1

0-3

4-7

12-4

SNA Formats

Service flag:
Reserved
RequesUreply indicator:
0010
request
1000
reply, function completed abnormally
1001
reply, function completed normally

GOS Variables for SNA STPs

Compare States (X' 1213') GOS Variable
Byte

Bit

Content

Sync point manager state:
X 101 1 RESET
X 1021
SYNC_POINT_MANAGER_PENDING
X ' 03 1 IN_DOUBT
X 1041
COMMITTED
X ' 05 1
HEURISTIC_RESET
1
HEURISTIC_COMMITTED
X ' 06
X ' 07 1 HEURISTIC_MIXED

Reserved

Length, in binary, of Logical-Unit-of-Work Identifier field (values 10 to 26 are
valid)

8-n

Logical-Unit-of-Work Identifier

Length, in binary, of network-qualified LU name (values 1 to 17 are valid)

8-w

Network-qualified LU name (format described in Chapter 7, "User Data Structured Subfields")

w+1-w+6

Logical-unit-of-work instance number, in binary

w+7-w+8(=n)

Logical-unit-of-work sequence number, in binary

n+1

Length (values 0 to 8 are valid). in binary, of conversation correlator

n+2-q

Conversation correlator of transaction program that allocated the conversation
that failed: see FMH-5 for format of this correlator

q+1

Length (values 2 to 8 are valid), of session instance identifier

q+2-p

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.)

Chapter 12. GDS Variables for SNA STPs

12-5

GOS Variables for SNA STPs

12-6

SNA Formats

Chapt~r

13. SNA/Distribution Services (DS)

Introduction
This appendix contains the format descriptions of the FS1 and FS2 message
units. The format descriptions are comprised of two parts: header description
tables and structure descriptions. A header description table contains the
header information for each structure associated with a particular message
unit. A structure description contains a prose description of the structure, bitlevel representations, and any presence rules or length restrictions associated
with a particular structure.
The definition of SNA/Oistribution Services (OS) requires a byte-accurate
description of the formats that must be understood by all OSUs. The OS
formats are described in terms of encoded fields referred to as "structures" and
the hierarchical relationship between these structures. In this appendix, the
header description tables show each structure and its header. Elsewhere in
this book, the header length is assumed not to be part of the overall structure
length (e.g., SNA_report_code).

Structure Classifications
Fields and groupings of fields are known as structures. They are categorized in
terms of their hierarchical position ("atomic," "child," or "parent"), the method
by which their beginning and endings are determined, (length-bounded, delimited, or implied) and which kind of header is used to identify them (LT or LLlO).
Only certain combinations of characteristics are possible.

Length-bounded Structures
Length-bounded structures consist of a header and usually some following
information. A header may be either two bytes in length, referred to as an "LT"
(length and type), or four bytes in length, referred to as an "LLlO" (length and
GOS codepoint). In either case, the length bytes include the length of the
header itself and the following information, if any. For FS1, a header may be
either two bytes in length, referred to as an "LT," or five bytes in length,
referred to as an "LLlOF" (length, GOS codepoint, and format byte).

Atomic Structures
In many cases, a structure consists only of its own header followed by data.
These structures cannot be decomposed, and therefore they are called
"atomic." Atomic structures are always length-bounded and may have either
LT or LLIO headers.

Parent and Child Structures
Structures can contain other structures within them. The containing structure is
known as a parent structure and the contained structures are known as
children. These terms are relative, since a nonatomic child structure itself contains other structures and is a parent to them. Children of the same parent are
siblings of each other. Parent structures may be length-bounded, delimited, or
implied; and may be identified by LTs or LLlOs.

Chapter 13. SNA/Distribution Services (DS)

13-1

Length-Bounded Parent Structures
In this case, the parent structure has its own header, either an LT or an LLiD.
Its length includes the lengths of all its children plus the length of its own
header. A length-bounded parent exists both as a logical grouping of its children and as an explicit encoded structure at its own encoding level.

Delimited Parent structures
Sometimes it is convenient to define a group of related structures as existing
within a parent structure without having that parent structure appear as a
length-bounded structure in the message. The beginning and end of the parent
are defined by its first and last children. These children are known as delimiters, the first child is the prefix delimiter and the last is the suffix delimiter.
Delimiter children are length-bounded and must be present. They may be null,
that is, with an LT of length = 2 or an LLiD of length =4. When the children's
headers are LTs, the parent is classified as a delimited LT structure. When
they are LLlDs, the parent is a delimited LLiD structure.

Implied Parent Structures
It is possible to define a set of related structures as children of a parent structure where the existence and boundaries of the parent are implied by the existence and order of certain child structures. This set of children may occur
within the parent structure, either ordered or unordered, until a structure occurs
that is not an element of this set. This break in sequence implies the boundary
between parent structures. Depending on its children's headers, an implied
parent is classified as either implied LT or implied LLiD.

Segmented Structures
Length-bounded LLiD Structures may be either segmentable or nonsegmentable. For segmentable structures, the most significant bit of the LL
bytes indicates whether any particular segment is the last (bit is equal to 0) or
not last (bit is equal to 1) segment of the structure. The 10 bytes of the
segmentable structure are present on the first segment only.
For FS1, segmentation is indicated by the contents of the F byte (the fifth byte
of the LLlDF header). Structures may be segmented when the most significant
bit of the F byte is on. If the most significant bit is on, then three more bytes,
the ISS bytes, follow the LLlDF header. The ISS bytes indicate whether a
particular segment is the last segment of a structure. In each segment except
the last segment of a structure, the I byte contains X'20'. In the last segment of
a structure, the I byte contains X'OO'. The SS bytes contain X'OOOO'.

Properties of Parent Structures
Order
A parent structure may have either ordered or unordered children. Ordered
children occur in the parent structure in the same order as they are described
in the format description table. Unordered children may occur in the parent
structure in any order.

13-2

SNA Formats

Unrecognized Children
Future enhancements to the formats might add structures that will not be recognized by implementations of the current format definitions. The current format
must specify for each parent whether or not unrecognized child structures are
allowed. If they are allowed, the definition must specify how long they might
be. When unrecognized structures are found where they are allowed, they
must be passed through without change at intermediate locations and gracefully ignored at final destinations. Unrecognized structures are identified by
either LT or LLiO headers, being of the same type as their siblings.

Number of Children
The number of children within a parent may range from a required minimum to
an allowed maximum. For example, a parent might have several children, each
defined with an occurrence of 0-1, and a number of children defined as 1. This
means that anyone, but only one, child is allowed.

Header Description Table
The header information and primary syntax associated with each structure are
formally described in tabular form. These header description tables represent
the formatting information required to either parse or build OS structures.

Structure Name
The first column of the header description table identifies OS structures, by
name, and illustrates their hierarchical relationship by indentation of the
column entries. The order of the structure entries in the table represents,
unless specified otherwise, the order in which the structures appear in a OS
message unit.

Structure Reference (Struct Ref)
As header information and primary syntax are described in the header
description of a particular table, the semantics, bit representations, presence
rules, and other characteristics are described formally in the structure
description. This column contains a reference page number to where this
structure information is found.

Structure Class (Struct Class)
Structures are classified as either length-bounded LLiOs (IO), lengthbounded LTs (T), delimited LLiOs (Oel-IO), delimited LTs (Oel-T), implied LLiOs
(Imp-IO), or implied LTs (Imp-T).
A structure classified as delimited must contain at least two required, lengthbounded children that act as the prefix (pfx) and suffix (sfx) of the delimited
structure. The "/pfx" notation indicates the length-bounded child structure that serves as the prefix for its parent delimited structure. The "/sfx"
notation indicates the length-bounded structure that serves as the suffix for
its parent delimited structure.
A structure classified as implied uses an identified child to identify the beginning of a sequence of children. The "/idc" notation indicates the lengthbounded structure that serves as an identified child of its parent implied
structure.
The same notation is applied to the Format Set 1 encodings .. Structures in
FS1 are classified as either length-bounded LLiOFs (IOF), length-

Chapter 13. SNA/Distribution Services (DS)

13-3

bounded LTs (T), delimited LLlDFs (Del-IDF), delimited LTs (Del-T), implied
LLlDFs (Imp-IDF), or implied LTs (Imp-T).
The "/seg" notation indicates that segmentation is allowed.

IDfT
This column contains the ID or T value within the header, in hexadecimal. To
indicate that a delimited structure is identified by its prefix, the notation "pfx" is
used. To indicate that an implied structure is identified by one of its children,
the notation "idc," for identified child, is used.

Length
This column describes the length verification that would be appropriate at presentation services time. The range of length values specifies the minimum and
maximum lengths of structures that an implementation is required to receive.
For structures that allow unrecognized children, the maximum length value
accommodates the possibility of these yet-to-be-defined structures. On the
sending side, the maximum length value for a particular structure may be
determined by subtracting the unrecognized reserve, if unrecognized children
are allowed, from the maximum length.
Note: An asterisk denotes length restrictions for a particular structure. Length
restrictions are detailed in the corresponding structure description.

Occurrences
Multiple occurrences of DS structures mayor may not be permitted. A value of
"1 - < some number>" in this column indicates the allowed range of occurrences of the corresponding structure. A value of "~1" indicates that there is
no architecturally defined maximum. A value of "1" in this column indicates
that only a single instance of the corresponding structure is appropriate. A
value of"O - 1" indicates that an instance of the corresponding structure is
optional.
Note: An asterisk denotes presence rules for a particular structure. Presence
rules are detailed in the corresponding structure description.

Children
Unrecognized Children Allowed (Unrec): An entry of "Y" in the "Unrec" column
indicates that the corresponding structure tolerates unrecognized child structures. An entry of "N" indicates that the particular structure tolerates only the
architecturally-defined child structures. An entry of "-" indicates that unrecognized children are not applicable to the particular structure. By definition,
atomic structures do not contain children, recognized or not.
Order: A value of "Y" in this column indicates that children are ordered, a
value of "N" indicates that children are unordered, and a value of "-" indicates
that no children are present.
Note: If a structure is atomic, this column is not applicable.
Number (Num): Each parent structure contains a certain number of different
children. This column specifies the minimu~ and maximum number of different
children for a particular parent structure. The maximum number also accounts
for unrecognized children, if they are allowed within the parent structure. This
column does not account for multiple occurrences of a particular child structure

13-4

S NA Formats

within the parent structure. The number of occurrences of each child is indicated in the "Occurrences" column.
Subtable: Sometimes the need to divide large tables into subtables becomes

apparent, particularly when common children appear frequently within different
header description tables. This column contains a reference page number to
where these common children are described.

Structure Description
The structure description is referenced by a page number appearing in the
"Structure Reference" column corresponding to each structure in the header
description table. This description contains information pertaining to the data
portion of a particular structure. Prose descriptions, presence rules, and
semantics associated with the corresponding entry in the header description
table may appear in the structure description.

Chapter 13. SNA/Oistribution Services (OS)

13-5

Header Description Tables for FS2 Message Units

DISTRIBUTION TRANSPORT MESSAGE UNIT (DTMU)
Figure 13-1 (Page 1 of 2). Distribution Transport Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Di st_Transport_MU

13·13

Del·ID

pfx

~53*

4·12

Transport_Prefix

13·13

ID/pfx

1570

8-18

1·3

Hop_Count

13·13

MU-,D

13·13

0·1*

13·13

0·1*

MU-'nstance_Number

13·13

ID/seg

1571

29·4096*

Transport_Command
Dist_Flags

13·14

0·1

Service_Parms

13·15

5·32

0·1

Server_ObL8yte_Count

13·18

0·1*

Origin_Agent

13·18

3-10

Server

13-18

3-10

0·1*

Origin_DSU

13·18

8·22

3·30

Sub
Table

Origin_RGN

13-19

3·10

Origin_REN

13·19

3·10

13-19

8·22

0·1

Origln_DGN

13-19

3·10

Origin_DEN

13-20

3·10

Seqno_DTM

13·20

14·17*

Supplemental_DisUnfol

13-21

3·10

0·1

Agent_Correl

13·22

3·130

0·1

Report· To_DSU

13·22

8·22

0-1

Report·To_RGN

13·22

3·10

Report·To_REN

13-22

3·10

13·23

8·22

0-1

Report·To_DGN

13·23

3·10

Report·To_DEN

13·23

3·10

Report_Service_Parms

13·24

5·32

0-1

Report-To_Agent

13·26

3·10

0·1

Dest_Agent

13·27

3·10

0·1

Unrecognized_Reserve

13·48

2·3728

Dest_Llst

13·27

ID/seg

1572

12·11268

Dest

13·27

Imp·T

idc

8·5654

1·2

13·27

T/ldc

8-22

Dest_RGN

13·28

3·10

13·28

3·10

Dest_REN

13·28

8-22

13·28

3-10

Origin_User

Report-To_User

Dest_DSU

Dest_User
Dest_DGN

13-6

SNA Formats

Figure 13-1

(P~ge

2 of 2). Distribution

Tr~nsport Mcss~gc

Unit
Children

Structure Nama

Struct
Rof Pg

Struct
CI01SS

Length

IOIT

Occurrancos

Unrec

13-29

3-10

Agent_Object

13-29

10/seg

1573

5-32767

0-1

Server_Object

13-29

10/seg

1574

0-1

Supplemental_OI sUnf02

13-29

10/seg

1580

5-32767

0-1

Unrecognized_Reserve

13-48

10/seg

4-32767

OS_Suffix

13-29

10/sfx

157F

Oest_OEN

Note:

Order

Num

Sub
Table

.. Refer to FS2 Structure Oescrlptions starting on page 13-13 for presence rules and length restrictions.

Chapter 13. SNA/Distribution Services (DS)

13-7

DISTRIBUTION REPORT MESSAGE UNIT (DRMU)
Figure 13-2. Distribution Report Message Unit
Children
Structure Name

Di st_Report_MU

Struct
Ref Pg
13-30

Struct
Class
Del-ID

IOIT
ph<

Length

~77·

Occurrences
1

Unrec

Sub
Table

Order

Num

6-12

1-3

Report_Prefix

13-30

ID/pfx

157C

8-18

Hop_Count

13-13

MU_ID

13-13

0-1

MU_lnstance_Number

13-13

0-1·

Report_Command

13-30

ID/seg

1575

25-4096*

Servlce_Parms

13-15

5-32

0-1

13-26

3-10

Report-To_Agent

Reporti ng_DS U

13-30

8-22

Reportlng_RGN

13-30

3-10

Reporti ng_REN

13-30

3-10

13-31

10-13*

Unrecognized_Reserve

13-48

2-4015

Report_DTM

13-32

1583

12-48

1-2

1~-""

8-22

Report-To_RGN

13-22

3-10

Report-To_REN

13-22

3-10

13-23

8-22

0-1

Report-To_DGN

13-23

3-10

Report-To_DEN

13-23

3-10

ReportJnformation

13-32

ID/seg

1576

18-4096

1-24

13-32

8-22

0-1·

Reported-On_Origin_RGN

13-32

3-10

Reported-On_Origin_REN

13-32

3-10

13-33

8-22

0-1*

Reported-On_Origin_DGN

13-33

3-10

Reported-On_Origi n_DEN

13·33

3-10

Reported-On_Seqno_DTM

13-34

14-17

Reported-On_Supp_Dlst_lnf01

13·35

3-10

0-1·

Reported-On_Agent_Correl

13·36

3-130

0-1

Reported·On_Origi n_Agent

13·36

3-10

0-1*

Reported-On_Dest_Agent

13·36

3·10

0-1*

Receivi ng_DSU

13·44

8-22

0-1

Recelvi ng_RGN

13·44

3-10

Receiving_REN

13·45

3·10

13·48

2-3849

SNA~Condition_Report

13·37

ID/seg

1532

10·32767

Reported-On_Supp_DisUnf02

13·36

ID/seg

1582

5·32767

0-1·

Unrecognized_Reserve

13-48

ID/seg

4-32767

OS_Suffix

13·29

I DIsh<

157F

Report-To_DSU_User
R~pcrt·To_DSU

Report-To_User

Reported-On_Origi n_DSU

Reported-On_Origin_User

Unrecognized_Reserve

Note:

13-8

.. Refer to FS2 Structure Descriptions starting on page 13-13 for presence rules and length restrictions.

SNA Formats

3-20

1-10

13-10

DISTRIBUTION CONTINUATION

rv~ESSAGE

UN;T

(DCiv~U)

Figure 13-3. Distribution Continuation Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Sub
Table

Oist_Contlnuation_MU

13-37

Oel-IO

pf><

~18

2-10

Continuation_Prefix

13-37

10/pf><

1578

14-24

2-3

MUJ"

13-13

MUJnstance_Number

13-13

Restartlng_8yte_Position

13-37

0-1

Agent_Object

13-29

10/seg

1573

5-32767

0-1

13-29

10/seg

1574

0-1

Supplemental_OI sU nf02

13-21

10/seg

1580

5-32767

0-1*

Unrecognized_Reserve

13-48

10/seg

4-32767

Servor_Object

OS_Suffix

13-29

10/sf><

157F

Note:

.. Refer to FS2 Structure Descriptions starting on page 13-13 for presence rules.

Chapter 13. SNA/Distribution Services (OS)

13-9

SNA CONDITION REPORT
Figure 13-4. SNA Condition Report
Children
Structure Name

Struct
Ref Pg

Struct
Class

Length

IOIT

Occurrences

Unrec

Order

Num

1-10

SNA_Condition_Report

13-37

1532

10-32767

SNA_Report_Code

13-37

Structure_Report

13-38

14-255

0-10·

2-10

Structure_State

13-38

Structure_Contents

13-38

3-100

0-1·

Parent_Spec

13-38

5-17

0-7

1-4

13-39

3-4

Parent_ID_Or_T
Parrnt_Class

13-39

0-1·

Parent_Position

13-39

0-1

Parent_Instance

13-39

0-1

13-40

5-17

0-1·

1-4

Structure_ID_Or_T

13-40

3-4

0-1·

13-40

0-1·

Structure_Class

Structure_Position

13-40

0-1

Structure_Instance

13-41

0-1

Structure_Segment_Number

13-41

0-1·

Structure_Syte_Offset

13-41

0-1

Sibling_List

13-41

3-100

0-1·

Unrecognized_Reserve

13-48

2-241

13-41

Del-T

pfx

12-11268

0-1·

Reported-On _ Dest_p refix

13-41

T/pfx

Reported-On_Dest

13-42

Imp/T

idc

8-5654

1-2

Structure_Spec

Reported-On_Dest_Li st

13-42

Tlidc

2-22

0-2

13-42

3-10

0-1·

13-42

3-10

0-1·

Reported-On_Dest_REN

13-42

8-22

Reported-On_Dest_DGN

13-43

3-10

Reported-Oil_Dest_DEN

13-43

3-10

Reported-On_Dest_ User

13-43

Supplemental_Report

13-44

3-255

0-5·

Unrecognized_Reserve

13-48

2-17664

Reported-On_Dest_Suffix

13-10

Reported-On_Dest_RGN

Reported-On_Dest_DSU

Note:

Sub
Table

• Refer to FS2 Structure Descriptions starting on page 13-13 for presence rules and length restrictions.

SNA Formats

SENDER EXCEPTION rv.ESSAGE

U.~li

(SErv.U)

Figure 13-5. Sender Exception Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
ClaDS

IOIT

Length

Occurrencos

Unrec

Order

Num

Sub
Table

1-10

Sender_Exception_MU

13-44

1578

10-256

SNA_Report_Codo

13-37

MU_ID

13-13

0-1

MUJnstance_Number

13-13

0-1·

Unrecognized_Reserve

13-48

2-236

Note:

Order

Num

Sub
Table

• Refer to FS2 Structure Descriptions starting on page 13-13 for presence rules.

RECEIVER EXCEPTION MESSAGE UNIT (REMU)
Figure 13-6. Receiver Exception Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

Length

IOIT

Occurrences

Unrec

13-44

Del-ID

pfx

~25

2-10

13-44

ID/pfx

1577

15-512

2-8

Sender_Retry_Acti on

13-44

MUJD

13-13

0-1

MUJnstance_Number

13-13

0-1·

Receiving_DSU

13-44

8-22

Rcceivi ng_RGN

13-44

3-10

Receivi ng_REN

13-45

3-10

13-48

2-473

Unrecognized_Reserve

13-48

SNA_Condition_Report

13-37

ID/sfx

1532

10-1024

1-10

Receiver_Exception_MU
Receiver_Exceptl on_Command

Unrecognized_Reserve

Note:

13-10

• Refer to FS2 Structure Descriptions starting on page 13-13 for presence rules.

COMPLETION QUERY MESSAGE UNIT (CQMU)
Figure 13-7. Completion Ouery Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Sub
Table

2-10

13-45

1579

14-256

13-13

MU _I nstance_Number

13-13

Unrecognized_Reserve

13-48

2-242

Completion_Query_MU
MUJD

Chapter 13. SNA/Oistribution Services (OS)

13-11

COMPLETION REPORT MESSAGE UNIT (CRMU)
Figure 13-8. Completion Report Message Unit
Children
Structure Name

Completion_Report_MU
Indicator_Flags
MU_ID

Struct
Ref Pg

Struct
Class

Length

IOIT

Occurrences

Unrec

Order

Num
1-10

157A

7·256

13·45

13·13

0·1

0·1*

13·45

MUJnstance_Number

13·13

Last_Structure_Received

13·46

Last_Byte_Received

13·46

0·1*

Unrecognized_Reserve

13·4B

2·225

Note:

Sub
Table

* Refer to FS2 Structure Descriptions starting on page 13·13 for presence rules.

PURGE REPORT MESSAGE UNIT (PRMU)
Figure 13-9. Purge Report Message Unit
Children
Structure Name

Purge_Report_MU

Struct
Ref Pg

Struct
Class

13·46

MU_ID

13·13

Unrecognized_Reserve

13·4B

Length

IOIT

Occurrences'

Unrec

Order

Num

1·10

157E

10·256

2·246

Sub
T~b!e

RESET REQUEST MESSAGE UNIT (RRMU)
Figure 13-10. Reset Request Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

Length

IOIT

Occurrences

Unrec

Order

Num

Sub
Table

13·46

15B5

21·23

MUJD

13·13

Reset_DTM

13·46

11·13

Reset_Request_MU

RESET ACCEPTED MESSAGE UNIT (RAMU)
Figure 13-11. Reset Accepted Message Unit
Children
Structure Name

Struct
Ref Pg

Struct
Class

Length

JOlT

Occurrences

Unrec

Order

Num
2

13·47

15B6

21-23

MUJD

13·13

Reset_DTM

13-46

11-13

Reset_Accepted_MU

13-12

SNA Formats

Sub
Table

FS2 Structure Descriptions
Clst_Tiaiispait_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The distribution_transport_message_unit transports agent and/or server
objects for distribution to one or more users or application programs.

Length Restriction:

The minimum length of a dist_transport_MU originated by an FS2 DSU is 54
bytes. This is due to the length restriction on the Seqno_DTM.

Transport_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Description:

The transportyrefix identifies the beginning of the dis·t_transport_MU. This
structure carries information that changes from DSU to DSU.

Hop_Count - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The hop_count is the remaining number of hops that may be traversed by a
OS distribution on its way toward its destination DSUs. The hop_count is set
by the origin DSU in the DTMUs and by the reporting DSUs for the DRMUs.
The hop_count is decremented by 1 in every DSU through which the
distribution passes. If the hop_count reaches 0 at an intermediate DSU,
exception processing is 'invoked.

Format:

Signed binary integer (1-origin)

MU_ID -------------------------------------------------------------------------------------------~

Descri ption:

The message_unit_identifier is a number that uniquely identifies a distribution
MU throughout its existence. An MU exists for only one hop, from one DSU to
the adjacent DSU. In REMUs and SEMUs, the MU-,D refers to a distribution
MU. An MU_ID is unique only for a particular LU name, mode name combination.

Presence Rule:

If the MU_ID is absent, exception reporting may not be requested.

Format:

Signed binary integer (1-origin)

MU_lnsmnC8_Number - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Descri ption:

The message_unit_instance_number identifies the instance of a particular distribution message unit and its corresponding MU_ID.

Presence Rule:

Precluded if an MV_ID is not present; otherwise, required.

Format:

Signed binary integer (1-origin)

Transport_Command - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Description:

The transport_command contains the control information used by the distribution service to transport the distribution.

Length Restriction:

The minimum length of a transport_command originated by an FS2 DSU is 30
bytes. This is due to the length restriction on the Seqno_DTM.

Chapter 13. SNA/Oistribution Services (OS)

13-13

Dist_Flags - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The distribution_flags indicate services requested by the origin agent.

Note:

If exception reporting is requested, the MU_ID is always present.

Format:

Bit string

Byte

Bit

0-1

LT header

1-7

Flags (bits 0-7) that must be understood and honored
by all DSUs
Exception report flag indicating whether an exception
report is to be sent if the distribution is aborted:
o no exception report to be sent (default)
1 exception report to be sent
Reserved

0-7

Flags (bits 0-7) that must be understood and honored
by destination DSUs, but that can be ignored by intermediate DSUs
Reserved

0-7

Flags (bits 0-7) that are ignored by DSUs if not understood
Reserved

13-14

SNA Formats

Content

5crvlco_P~rms

Description:

-------------------------------.....,
The service""parameters structure describes the types and levels of service
requested for the distribution. The parameters in this structure are provided
by the origin agent. The service""parameters used in the DTMU and the DRMU
are similar; the differences in such usage and the default values used for
absent service""parameter (SP) triplets are discussed under the individual triplets below. The default values specified below are assumed for absent
service""parameter (SP) triplets.
In FS1, the service""parameters are specified by the origin agent in Dist_MU
type TRANSPORT. The specification for deriving the service""parameters for
Dist_MU type REPORT is found in the description of report_service""parameters
on page 13-24.

Format:

Special format consisting of ordered, optional, SP triplets of the following
general structure:

Byte

Bit

Content

Parameter type:
All parameter type byte values are defined by or
reserved for SNA/DS.

1
0-3

4-7
2

Comparison operator:
1100
REQUIRE_LEVEL_GE
1110
REQUIRE_SUPPORT_FOR
Note: All other values for bits 0-3 are reserved.
Reserved
Value:
The meaning of this byte depends on the parameter
type.

Byte

Content

0-1

LT header

2-31

Up to 10 different service""parameter (SP) triplets may be carried
in one distribution. Each triplet, when present, appears in
ascending sequence of parameter type. For FS2, the capacity
triplet is not used in the DRMU. For FS1, the capacity triplet is
used. For FS2, all service parameters are optional in both the
DTMU and the DRMU. For FS1, the first three parameters are
present in both Dist_MU types TRANSPORT and REPORT. Thearchitecturally defined service parameters are given below:

Chapter 13. SNA/Distribution Services (DS)

13-15

Priority SP Triplet
Byte

Content

X'01'

X'CO'

X'FO' FAST
(default)
X'DO' CONTROL
X'80' DATA_16
(can be treated as DATAHI)
X'78' DATA_15
(can be treated as DATAHI)
X'70' DATA_14
(can be treated as DATAHI)
X'68' DATA_13
(can be treated as DATAHI)
X'BO' DATA_12
(DATAHI)
X'58' DATA_11
(can be treated as DATAHI)
X'50' DATA_10
(can be treated as DATAHI)
(can be treated as DATAHI)
X'48' DATA_9
X'40' DATA_8
(can be treated as DATALO)
X'38' DATAJ
(can be treated as DATALO)
X'30' DATA_6
(can be treated as DATALO)
X'28' DATA_5
(can be treated as DATALO)
X'20' DATA_4
(DATALO)
X'18' DATA_3
(can be treated as DATALO)
X'10' DATA_2
(can be treated as DATALO)
X'08' DATA_1
(can be treated as DATALO)
Note: All other values are reserved.

REQUIRE_LEVEL_GE

Protection SP Triplet

13-16

SNA Formats

Byte

Content

X'02'

X'10'

(default when Priority SP is GE X'EO'):
safe store may be performed.
X'30' LEVEL2 (default when Priority SP is LT X'EO'):
safe store must be performed.
Note: All other values are reserved.
LEVEL1

C:lp::~ity

Trip!~t

Byte

Content

X'03'

Capacity value is the exponent of the power of 2 that represents
the value of the required capacity for the server_object in the
DTMU:
X'OO'

ZERO

(default when Priority SP is GE X'EO')
used if there is no server_object
in dist_transport_MU.
one megabyte

X'14' 1MB
X'16' 4MB
(default when Priority SP is LT X'EO')
X'18' 16MB
Note: All other values are reserved.
1.

In FS2. the Capacity SP triplet occurs only in a
DTMU.

Receiving FS2 DSUs are always able to
receive a capacity level of INDEFINITE (designated
by X'EOFF' in bytes 1-2).
Originating FS2 DSUs never generate the
capacity level of INDEFINITE. The level
replacing INDEFINITE is 16MB (X'C018').

The capacity requirement is for the
server_object. and does not include the
capacity needed to store and handle the
other structures of the DTMU.

Implementations may accept other capacity
levels as long as they can route the
distribution responsibly.

Security SP Triplet
Byte

Content

X'04'

X'01' LEVEL1 (default): security is not required.
X'20' LEVEL2: security is required.
Note: All other values are reserved.

Chapter 13. SNA/Distribution Services (OS)

13-17

Server_ObLByte_Count - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The server_object_byte..;..count is the number of bytes of all the segments of
the server_object. An FS2-capable DSU originating a distribution either supplies a correct byte count, or omits the field completely; for FS1, the byte
count need not be accurate.

Presence Rule:

Optional when the server_object is present; otherwise, precluded.

Format:

Unsigned binary integer (1-origin)

Origin_Agent - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The origin_agent is the transaction program at the DSU at which the distribution originated.

Format:

Character string, except for first byte

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ianges in value fiom X'OO' to X'3F'. Vilhan the first
byte ranges in value from X'41' to X'FF', the transaction
program is not SNA registered. X' 40' is not a valid first
byte.

Se~er --------------------------------------~

Description:

The server is the name to be used to store the server_object at the destination.

Presence Rule:

In FS2, optional when the server_object is present; otherwise, precluded. If
optional and absent, the general server TP name is the default. In FS1,
required when the server_object is present.

Format:

Character string, except for first byte

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ranges in value from X'OO' to X'3F'. When the first
byte ranges in value from X'41' to X'FF', the transaction
program is not SNA registered. X'40' is not a valid first
byte.

Origln_DSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . . . . . ,

Description:

13-18

SNA Formats

The origin_DSU is the name of the DSU at which the distribution originated.

Origin_RGN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The origin_RGN is the first part of the name of the DSU at which the distribution originated. This is typically, but not necessarily, the network 10.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

Orlgin_REN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The origin_REN is the second part of the name of the DSU at which the distribution originated. This is typically, but not necessarily, the LU name.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

Origin_User - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The origin_user is the user name of the originator of the distribution.

Orlgin_DGN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The origin_DGN is the first part of the user name of the distribution originator.

Note:

For FS1, when the Dist_MU is of type REPORT and the distribution report was
generated by OS, null user names will occur.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:
Base

Leading, imbedded, and trailing space (X' 40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

Chapter 13. SNA/Oistribution Services (OS)

13-19

Origin_DEN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Description:

The origin_DEN is the second part of the user name of the distribution originator.

Note:

For FS1, when the Dist_MU is of type REPORT and the distribution report was
generated by DS, null user names will occur.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:
Base

Leading, imbedded, and trailing space (X' 40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

Seqno_DTM ------------------------------------------------------------------------------------------~

Description:

The sequence_numberldate-time, in combination with the origin_agent,
origin_user, and origin_DSU, uniquely identifies the distribution. The
sequence number is the number assigned to the distribution by the origin
agent. For FS2, the number ranges from 1 to (2**31)-1. For FS1, the number
ranges from 0 (fer report MUs) to 9999. The date of the distribution is
assigned by the origin agent; the time of the distribution is assigned by the
origin DSU. The offset from GMT for local time is included.

Note:

FS2 tolerates sequence numbers with value 0 in message units that had, at
some point, come from an FS1 network and had already specified a sequence
number of 0 (i.e., DIA application status reports). However, sequence
numbers with value 0 are never originated from within an FS2 network.

Length Restriction:

Originating FS2 DSUs generate a GMT-based time. The minimum length for
seqno_DTM is therefore 15 (1-origin).

Format:

Byte string

13·20

SNA Formats

Byte

Content

0-1

LT header

2-5

SEQNO
Signed binary integer limited to {2**31)-1
DATE
Year, in binary (e.g., 1989 is encoded as X'07C5')
. 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)

6-7
8
9

10
11
12
13

GMT FLAGS
Indicates that specified TIME is GMT and identifies whether offsets
from GMT are required to calculate local time. (Equivalent
EBCDIC characters are shown in parentheses.)
(2)
no offset required
X'E9'
(+) add required offset to GMT to get
X' 4E'
local time
X'60'
(-)
subtract required offset from GMT to get
local time
Note: All other values are reserved.

X'E9'
Hour offset from GMT, in binary, occurs when GMT flag
(values from 0 to 23 are valid)
Minute offset from GMT, in binary, occurs when GMT flag
X'E9'
(values from 0 to 59 are valid)

Examples:
A 9-byte date-time encoding is a date-time followed immediately by an EBCDIC
"Z" and is considered to be GMT. Thus, 12:00GMT on 2 January 1988 would be

X' S7C4S1S2SCSSSSSSE9 1
yyyyMMddHHmmsshhZ
An 11-byte date-time encoding is a date-time followed immediately by an
EBCDIC" +" or "-" and two 1-byte binary numbers, and is considered to be
GMT and the offset from GMT to local time. Thus, 7:00am on 2 January 1988 in
New York would be 12:00GMT - 5 hours, or

X'S7C4S1S2SCSSSSSS6SS5SS '
yyyyMMddHHmmsshh- HHmm

Descri ption:

The supp/ementa'-distJnfo1 structure is reserved for future use.

Format:

Character string

Chapter 13. SNA/Distribution Services (DS)

13-21

Agent_Correl

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

Description:

The agent_correlation is a string supplied by the origin agent. OS is not
aware of its contents.

Format:

Undefined byte string

Report-To_DSU
Description:

Report-To_RGN

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

The report-to_DSU is the name of the DSU to which distribution reports are to
be sent. If both report-to_DSU and report-to_user are absent in the DTMU, the
values generated in the DRMU for these structures default to the origin. If
only report-to_DSU is present in the DTMU, then any report is sent to that
DSU. If only report-to_user is present in the DTMU, then the reporting DSU
will refer to its directory to determine report-to_DSU. For FS1, this information
is valid only if Dist_MU is of type TRANSPORT.

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

Description:

The report-to_RGN is the first part of the DSU name to which distribution
reports are to be sent. For FS1, this information is valid only if Dist_MU is of
type TRANSPORT. This is typically, but not necessarily, the network 10.

Format:

Character string

Report-To_REN

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

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

Description:

The report-to_REN is the second part of the DSU name to which distribution
reports are to be sent. For FS1, this information is valid only if Dist_MU is of
type TRANSPORT. This is typically, but not necessarily, the LU name.

Format:

Character string

13-22

SNA Formats

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

Note:

If a product chooses to implement DGN = REN, the
enhanced character set (ECS) subset is implemented in a
particular network, and any DGN contains an ECS character that is not an element of character set AR, then ECS
characters may occur in this structure.

Report-To_User
Description:

Report-To_DGN

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

The report-to_user is the name of the user to which distribution reports are to
be sent. If both report-to_user and report-to_DSU are absent in the DTMU, the
values generated in the DRMU for these structures default to the origin. If
only report-to_user is present in the DTMU the reporting DSU refers to its
directory to determine rep ort-to_DS U. For FS1, this information is valid only if
Dist_MU is of type TRANSPORT.

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

Description:

The report-to_DGN is the first part of the user name to which distribution
reports are to be sent. For FS1, this information is valid only if Dist_MU is of
type TRANSPORT.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:

Report-To_DEN

Base

Leading, imbedded, and trailing space (X' 40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

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

Description:

The report-to_DEN is the second part of the user name to which distribution
reports are to be sent. For FS1, this information is valid only if Dist_MU is of
type TRANSPORT.

Format:

Character stri ng

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:
Base

Leading, imbedded, and trailing space (X' 40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

Chapter 13. SNA/Oistribution Services (OS)

13-23

Repon_SeNice_Parms
Description:

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

The report_serviceJJarameters structure describes the service requested for
the distribution report by the origin "agent when the agent wants to override
the serviceJJarameters that would be routinely generated by the reporting
DSU for the report MU. If report_serviceJJarameters are specified, they are
used as the serviceJJarameters in any DRMUs that are generated as part of
the distribution. If the origin agent does not specify one or more of the
report_serviceJJarameters. a DSU that generates a report derives appropriate
serviceJJarameters for the DRMU from the serviceJJarameters in the DTMU.
For FS2, the comparison operators and values derived for the protection and
security parameters are the same as those specified (explicitly or implicitly) in
the DTMU. For FS1, the comparison operators and values derived for the protection, capacity, and security parameters are the same as those specified in
the Dist_MU type TRANSPORT.
For the priority service parameter, the value derived is either FAST or CONTROL.
is used if the DTMU specified FAST priority; CONTROL is used if the DTMU
specified a DATA_N priority. CONTROL priority is used only in DRMUs; it may not
be specified for the priority service parameter in a DTMU. If the origin agent
explicitly specifies a value for the priority report service parameter, the value
may be FAST, CONTROL, or DATA_N. The comparison operator for the priority
service parameter is always REQUIRE_LEVEL_GE.
FAST

Format:

13-24

SNA Formats

Special format consisting of ordered, optional report_serviceJJarameter triplets of the same general structure as for serviceJJarameters. See
serviceJJarameters on page 13-15.

Byte

Content

0-1

LT header

2-31

Up to 10 different report_serviceJJarameter (RSP) triplets may be
carried in one distribution. Each triplet, when present, appears in
ascending sequence of parameter type. For FS2, the capacity
triplet is not used in the DRMU. and therefore the capacity RSP is
never specified. For FS1, the capacity triplet is used. For FS2, all
service parameters are optional in both the DTMU and the DRMU.
For FS1, the first three parameters-priority, protection, and
capacity-are present if report service parameters are to be specified.

Priority RSP Triplet
Byte

Content

X'01'

X'FO' FAST
X'DO' CONTROL
X'80' DATA_16
(can be treated as DATAHI)
X'78' DATA_15
(can be treated as DATAHI)
X'70' DATA_14
(can be treated as DATAHI)
X'68' DATA_13
(can be treated as DATAHI)
X'60' DATA_12
(DATAHI)
X'58' DATA_11
(can be treated as DATAHI)
X'50' DATA_10
(can be treated as DATAHI)
X'48' DATA_9
(can be treated as DATAHI)
X'40' DATA_8
(can be treated as DATALO)
X'38' DATAJ
(can be treated as DATALO)
X'30' DATA_6
(can be treated as DATALO)
X'28' DATA_5
(can be treated as DATALO)
X'20' DATA_4
(DATALO)
X'18' DATA_3
(can be treated as DATALO)
X'10' DATA_2
(can be treated as DATALO)
X'08' DATA_1
(can be treated as DATALO)
Note: All other values are reserved.

Protection RSP Triplet
Byte

Content

X'02'

X'10' LEVEL1: safe store may be performed.
X'30' LEVEL2: safe store must be performed.
Note: All other values are reserved.

Chapter 13 .. SNA/Oistribution Services (OS)

13-25

Capacity RSP Triplet (not present in FS2)
Byte

Content

X'03'

X'OO'

ZERO

Notes: All other values are reserved.
Also, All FS1 implementations are able to receive
distribution reports of FOUR_K capacity (X'OC').
New FS1 implementations always send
distribution reports of ZERO capacity.

Security RSP Triplet
Byte

Content

X'04'

X'01' LEVEL1: security is not required.
X'20' LI:'JI:L2: security is required.
Note: All other values are reserved.

Report-To_Agent ----------------------------------------------------------~
Description:

The report-to_agent is the name of the application transaction program to be
started after the report is queued for delivery. If report-to_agent is absent in
the DTMU, the value specified in the DTMU for origin_agent is used in the
DRMU for report-to_agent.

Format:

Character string, except for first byte.

CGCSGID:

01134-00500 (character setAR)

String Conventions:

13-26

SNA Formats

Des~Agent --------------------------------------------------------------~

Description:

The destination_agent is the transaction program at the destination DSU
to which the distribution is to be delivered. If dest_agent is absent in
the DTMU, the value specified for origin_agent is assumed to be the
dest_agent.

Format:

Character string, except for first byte

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ranges in value from X'OO' to X'3F'. When the first
byte ranges in value from X' 41' to X'FF', the transaction
program is not SNA registered. X' 40' is not a valid first
byte.

Dest_List -------------------------------------------------------------,
Descri ption:

The destination_list is the list of destinations for the distribution, which can
contain up to 256 destinations. Each destination is a dest_DSU with or without
a dest_user, expressed as (dest_DSU (.dest_user)). For single-destination distributions and distribution reports, the dest_list contains only one destination.
Either a flat destination list, of the form
(dest_DSU (desCuser)) , ... , (dest_DSU (des t_user)) , ...

or a factored destination list, of the form
(dest_DSU (dest_user, dest_user, ... )), (dest_DSU (dest_user, ... ))

may be present. For example, a flat destination list might contain
(DSU_A USER_1), (DSU_A USER_2), (DSU_A), (DSU_B USER_3), (DSU_B USER_4)

whereas a factored destination list would contain

Dest -------------------------------------------------------------------~
Description:

The destination associates dest_users with a dest_DSU. For flat destination
lists, there are zero or one user names per dest. For factored destination
lists, there can be multiple user names per dest.

Dest_DSU --------------------------------------------------------------~
Descri ption:

The destination_DSU is the name of one of the DSUs to which the distribution
is to be sent.

Chapter 13. SNA/Distribution Services (DS)

13-27

Des~RGN ------------------------------------------------------------~

Description:

The destination_RGN is the first part of a dest_DSU name. This is typically,
but not necessarily, the network ID.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters are not allowed.

Des~REN --------------------------------------------------------------~

Description:

The destination_REN is the second part of a desCDSU name. This is typically,
but not necessarily, the LU name.

Format:

Character string

Dest_User

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Note:

if a product chooses to impiement DGN = REN, the
enhanced character set (ECS) subset is implemented in a
particular network, and any DGN contains an ECS character that is not an element of character set AR, then ECS
characters may occur in this structure.

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

Description:

The destination_user is the name of one of the users to which the distribution
is to be sent.

Des~DGN ------------------------------------------------------------~

Description:

The destination_DGN is the first part of the name of a dest_user.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:

13-28

SNA Formats

Base

Leading, imbedded, and trailing space (X'40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

Dast_DEN ----------------------------------------~----------------------~

Descri ption:

The destination_DEN is the second part of the name of a dest_user.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:
Base

Leading, imbedded, and trailing space (X'40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not
allowed, trailing space characters are not significant, and imbedded space characters are
significant.

Agent_Object - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The agent_object is directly supplied by the origin agent. It is never parsed by
the distribution service and is directly delivered, unchanged, to the agent at
each destination.

Format:

Undefined byte string

SeNer_ObJect ------------------------------------------------------------~
Description:

The server_object is identified by the origin agent and is fetched by the origin
server when sending the dist_transport_MU. For FS1, the server_object is
fetched by the origin server during transmission of the Dist_MU type TRANSPORT. At each destination, the server_object is stored by the destination
server and a notification of its receipt is delivered to the destination agent.

Length Restriction:

The maximum segment size for FS1 is 32511.

Format:

Undefined byte string

Descri ption:

The supp/ementa'-distJnfo2 structure is reserved for future use.

Format:

Undefined byte string

OS_Suffix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_services_suffix contains no information and marks the end of
the dist_transport_MU, dist_report_MU, or dist_continuation_MU.

Chapter 13. SNA/Distribution Services (DS)

13-29

Dlst_Report_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_report_message_unit carries information reporting on the
state of the distribution. Typically, for a multiple destination distribution, a
dist_report_MU will report on only a portion of the distribution. The report is
delivered to the report-to destination if one was specified in the reported-on
DTMU; otherwise, it is delivered to the distribution originator.

Length Restriction:

The minimum length of a dist_report_MU originated by an FS2 DSU is 78
bytes. This is due to the length restriction on the Report_DTM.

Report_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The reportyrefix identifies the beginning of dist_report_MU. This structure
carries information that changes from DSU to DSU.

Report_Command -----------------------------~

Description:

The report_command contains the control information for the distribution
report.

Length Restriction:

The minimum length of a dist_report_MU originated by an FS2 DSU is 26
bytes. This is due to the length restriction on the Report_DTM.

Reportlng_DSU

The reporting_DSU is the name of the DSU that geneiated the ieport.

Reporting_RGN -----------------------------~

Descri ption:

The reporting_RGN is the first part of the name of the DSU that generated the
report. This is typically, but not necessarily, the network ID.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X'40') characters
are not allowed.

Reporting_REN -----------------------------~

Descri ption:

The reporting_REN is the second part of the name of the DSU that generated
the report. This is typically, but not necessarily, the LU name.

Format:

Character string

13-30

SNA Formats

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X'40') characters
are not allowed.

Repor~DTM ------------------------------------------------------------~

Description:

The report_date-time contains the date and time at which the reporting DSU
generated the report. FS2 products support the offset from GMT for local
time.

Length Restriction:

Originating FS2 DSUs always generate a GMT-based time. The minimum
length for report_DTM is therefore 11 (1-origin).

Format:

Byte string

Byte

Content

0-1

LT header

2-3
4
5

DATE
Year, in binary (e.g., 1989 is encoded as X'07C5')
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)

6
7
8
9

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)
GMT FLAGS
Indicates that specified TIME is GMT and identifies whether offsets
from GMT are required to calculate local time. (Equivalent
EBCDIC characters are shown in parentheses.)
(2)
no offset required
X'E9'
(+) add required offset to GMT to get
X'4E'
local time
X'60'
(-)
subtract required offset from GMT to get
local time
Note: All other values are reserved.

Hour offset from GMT, in binary, occurs when GMT flag
X'E9'
(values from 0 to 23 are valid)
Minute offset from GMT, in binary, occurs when GMT flag
X'E9'
(values from 0 to 59 are valid)

Examples:
A 9-byte date-time encoding is a date-time followed immediately by an EBCDIC
is considered to be GMT. Thus, 12:00GMT on 2 January 1988 would be

"z" and

X' 07C401020COOOOOOE9 1
yyyyMMddHHmmsshhZ
An 11-byte date-time encoding is a date-time followed immediately by an
EBCDIC" +" or "-" and two 1-byte binary numbers, and is considered to be
GMT and the offset from GMT to local time. Thus, 7:00am on 2 January 1988 in
New York would be 12:00GMT - 5 hours, or

X'07C401020C000000600500 '
yyyyMMddHHmmsshh- HHmm

Chapter 13. SNA/Distribution Services (DS)

13-31

Report-To_DSU_User ------------------------------------------------------~
Description:

The report-to_DSU_user is the DSU or user to which the distribution report is
being sent.

Report_Information ---------------------------------------------------,
Description:

The report_information identifies the distribution (or portion thereof) being
reported on.

Reported-On_Orlgin_DSU - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,
Description:

The reported-on_origin_DSU is the name of the DSU at which the distribution
was originated.

Presence Rules:

If reported-on_origin_DSU is present, and reported-on_origin_user is absent,
then the, distribution was originated by a DSU; if reported-on_origin_user is
present and reported-on_DSU is absent, then the report either originated in or
passed through an FS1 subnetwork. If both reported-on_origin_DSU and
reported-on_origin_user are present, then the report is not going to the originator of the distribution; if both reported-on_origin_DSU and reportedon_origin_user are absent, then they default to report-to_DSU and, if
applicable, report-to_user.

Desc,ri ption:

The reported-on_origin_RGN is the first part of the DSU name at which the distribution originated. This is typically, but not necessarily, the network 10.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X' 40') characters
are not allowed.

Reported-On_Orlgin_REN - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . ,
Description:

The reported-on_origin_REN is the second part of the DSU name at which the
distribution originated. This is typically, but not necessarily, the LU name.

Format:

Character string

13-32

SNA Formats

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X' 40') characters
are not allowed.

Reported-On_Origin_User - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The reported-on_origin_user is the name of the user that originated the distribution.

Presence Rules:

If reported-on_origin_DSU is present, and reported-on_origin_user is absent,
then the distribution was originated by a DSU; if reported-on_origin_user is
present and reported-on_DSU is absent, then the report either originated in or
passed through an FS1 subnetwork. If both reported-on_origin_DSU and
reported-on_origin_user are present, then the report is not going to the originator of the distribution; if both reported-on_origin_DSU and reportedon_origin_user are absent, then they default to report-to_DSU and, if
applicable, report-to _user.

Reported-On_Origin_DGN - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The reported-on_origin_DGN is the first part of the name of the user that originated the distribution.

Format:

Character string

CGCSGIDs:

01134-00500 (base). 00930-00500 (enhanced char set)

String Conventions:
Base

Leading, trailing, and imbedded space (X' 40')
characters are not allowed.

ECS

Leading space (X'40') characters are disallowed, trailing space characters are not significant, and imbedded space characters are
significant.

Reported-On_Origin_DEN - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The reported-on_origin_DEN is the second part of the name of the user that
originated the distribution.

Format:

Character string

CGCSGIDs:

01134-00500 (base), 00930-00500 (enhanced char set)

String Conventions:
Base

Leading, trailing, and imbedded space (X'40')
characters are not allowed.

ECS

Leading space (X' 40 /) characters are disallowed, trailing space characters are not significant, and imbedded space characters are
significant.

Chapter 13. SNA/Distribution Services (DS)

13-33

Reported-On_Seqno_DTM

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

Description:

The reported-on_sequence_numberldate-time, in combination with the origin
agent, origin DSU, and origin user, is the unique identifier of the distribution.
The origin agent, origin DSU, and origin user are specified in the appropriate
reported-on or report-to structures. The sequence number is the number
assigned to the distribution by the origin agent. For FS2, the number ranges
from 1 to (2**31)-1. For FS1, the number ranges from 1 to 9999. The date-time
is the date and time generated at the origin of the distribution. FS2 products
support the offset from GMT for local time.

Length Restriction:

Originating FS2 DSUs always generate a GMT-based time. The minimum
length for reported-on_seqno_DTM is 15 (1-origin).

Format:

Byte string

13-34

SNA Formats

Byte

Content

0-1

LT header

2-5

SEQNO
Signed binary integer limited to (2**31)-1

6-7
8
9

DATE
Year, in binary (e.g., 1989 is encoded as X'07C5')
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)

10
11
12
13

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)
GMT FLAGS
Indicates that specified TIME is GMT and identifies whether offsets
from GMT are required to calculate local time. (Equivalent
EBCDIC characters are shown in parentheses.)
X'E9'
(z)
no offset required
(+) add required offset to GMT to get
X'4E'
local time
(-)
subtract required offset from GMT to get
X'60'
local time
Note: All other values are reserved.

Hour offset from GMT, in binary, occurs when GMT flag =t= X'E9'
(values from 0 to 23 are valid)
.
Minute offset from GMT, in binary, occurs when GMT flag =t= X'E9'
(values from 0 to 59 are valid)

15
16

Examples:
A 9-byte date-time encoding is a date-time followed immediately by an EBCDIC
HZ" and is considered to be GMT. Thus, 12:00GMT on 2 January 1988 would be

X'07C401020COOOOOOE9'
yyyyMMddHHmmsshhZ
An 11-byte date-time encoding is a date-time followed immediately by an
EBCDIC" +" or "-" and two 1-byte binary numbers, and is considered to be
GMT and the offset from GMT to local time. Thus, 7:00am on 2 January 1988 in
New York would be 12:00GMT - 5 hours, or

X'07C401020C000000600500'
yyyyMMddHHmmsshh- HHmm

Reported-On_Supp_DlsClnfo1 - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The reported-on_supp_disCinfol structure is reserved for future use.

Format:

Character string

Chapter 13. SNA/Oistribution Services (OS)

13-35

Reponed-On_Agent_Correl --------------------------------------------------~
Description:

The reported-on_agent_corre/ation is a string that was supplied by the origin
agent at the origin DSU.

Format:

Undefined byte string

Reponed-On_Origin_Agent

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

Des,cription:

The reported-on_origin_agent is the name of the transaction program at the
origin DSU that originated the distribution that is being reported on.

Presence Rule:

Occurs when report-to_agent is different from origin_agent. If third-party
reporting has been requested and a report was generated in or flowed
through an FS1 subnetwork, the reported-on_origin_agent structure is discarded.

Format:

Character string, except for first byte

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X' 40') characters
are not allowed.
The first byie of an SNA-registered transaciion program
name ranges in value from X'OO' to X'3F'. When the first
byte ranges in value from X'41' to X'FF', the transaction
program is not SNA registered. X'40' is not a valid first
byte.

Reponed-On_Dest_Agent ------------------------------------------------~
Description:

The reported-on_destination_agent is the name of the transaction program at
the destination DSU that was specified for the reported-on distribution.

Presence Rule:

Occurs when dest_agent was specified in the reported-on DTMU.

Format:

Character string, except for first byte

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, trailing, and imbedded space (X'40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ranges in value from X'OO' to X'3F'. When the first
byte ranges in value from X' 41' to X'FF', the transaction
program is not SNA registered. X' 40' is not a valid first
byte.

Reponed-On_Supp_Dist_lnfo2 ----------------------------------------------,
Descri ption:

The reported-on_supp_dist_info2 structure is reserved for future use.

Format:

Undefined byte string

13-36

SNA Formats

Dlst_Contlnuatlon_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The distribution_continuation_message_unit is used by a sending DSU to continue transmission of a suspended MU.

Continuation_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The continuationyrefix identifies the beginning of a DCMU.

Restartlng_Byte_Positlon - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The restarting_byteyosition indicates where the sender is beginning
retransmission of the first structure being re-sent. The byte count begins with
the first byte of atomic data (Le., no LLs included) within the encompassing
structure. Absence of this structure is equivalent to the presence of a 1 in this
structure, implying that the first structure present in the DCMU is being
re-sent in its entirety. 0 is not allowed.

Format:

Unsigned binary integer (1-origin)

SNA_Condition_Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The SNA_condition_repQrt describes the condition being reported. The condition is always identified by an SNA_report_code.
Certain conditions can be more fully described by supplementary information.
Conditions pertaining to one or more structures in a format can have the
location and contents of each of those structures specified by a
structure_report. Certain conditions arise from inconsistencies among mUltiple portions of the MU. Each portion is described by a separate
structure_report .

SNA_Report_Code -------------------------------~

Description:

The SNA_report_code is an SNA registered code identifying the condition that
is being reported. Refer to Chapter 9, "Sense Data" on page 9-1 for allowable values and descriptions.

Format:

Byte string

Byte

Content

0-1

LT header

2-3

Primary report code

4-5

Subcode

Chapter 13. SNA/Oistribution Services (OS)

13-37

Structure_Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_report reports on a structure involved in a format-related condition. Depending on the condition, the structure_report may describe a structure that was present in, or absent from, the reported-on MU.
A format condition has its location in the MU pinpointed by a structure_spec
and a list of parent_specs that define a line-of-descent. The line-of-descent
begins with the MU and continues down the parent-child hierarchy to a level
as low as the particular condition warrants. A registered 10 always appears
in a structure_report; if the reported-on structure is not itself a registered 10,
its line-of-descent is traced up to include a registered ancestor.

Presence Rule:

Presence governed by the SNA_report_code.

Structure_State - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure_state indicates whether the reported-on structure was present
or absent.

Format:

Hexadecimal code

Byte

Content

0-1

LT header

X'01' STRUCTURE_PRESENT
X'02' STRUCTURE_ABSENT
Note: All other values are reserved.

Structure_Contents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_contents is the portion of the MU that is relevant to the detected
condition. Typically, the structure_contents contains the header of the structure and at least the beginning of its contents. When the condition can be
isolated to a portion of the structure, the structure_contents contains only that
portion of the structure relevant to the condition. In this case, the
structure_segment_number and structure_byte_offset locate the portion of the
structure relevant to the condition.

Presence Rule:

Allowed only when structure_state

Format:

Undefined byte string

= STRUCTURE_PRESENT.

Parent_Spec - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

13-38

SNA Formats

The parent_specification contains the identifier (10 or T) and the class of a
parent structure. For a parent structure that occurs multiple times, the
instance may also be included. The value of the parent_instance identifies the
particular instance. The position of this parent structure within its parent (if
one exists) may also be included. This would typically be done when this
parent structure is an unordered child of its parent.

ParentJD_Or_T - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The parent_ID_or_T is the ID or T value of a parent structure. ID values are
the registered GDS codepoints. T values are architecture-specific values relative to the encompassing ID.

Format:

Undefined byte string

Parent_Class - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The parent_class is the class of a parent structure.

Presence Rule:

If absent, defaults to LENGTH~BOUNDED_LT_sTRucTuRE.

Format:

Hexadecimal code

Byte

. Content

0-1

LT header

2·

X'01'
X'02'
X'03'
X'04'

LENGTH-BOUNDED_LlID_STRUCTURE (ID)
LENGTH-BOUNDED_LT_STRUCTURE (T)

(default)

DELIMITED_LLlD_STRUCTURE (DEL-ID)
DELIMITED_LT_STRUCTURE (DEL-T)

X'OS'
1MPlIED_LlID_STRUCTURE (IMP-ID)
X'OB'
IMPlIED_LT_STRUCTURE (IMP-T)
Note: All other values are reserved.
Parent_Position - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The parentyosition is the position of this parent structure within its parent (if
one exists) in this particular MU. Multiple consecutive instances of a repeatable parent structure share a single position, and can be distinguished by
parent_instance.

Format:

Signed binary integer

Parent_Instance ------------------------------~

Description:

The parent_instance is used when a parent structure occurs multiple times.
The value of parent_instance identifies the particular instance within a position.

Format:

Signed binary integer

Chapter 13. SNA/Distribution Services (OS)

13-39

Structure_Spec - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,
Description:

The structure_specification contains the identifier (10 or T) and the class of a
structure. For a structure that occurs multiple times, the instance may also be
included. The value of the structure_instance identifies the particular
instance. The position of this structure within its parent structure may also be
included. This would typically be done when the parent structure contains
unordered children.

Presence Rule:

Absent only when the structure_class is the default and the sibling_list contains all pertinent 10 or T values.

Structure_ID_Or_T - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_'D _or_T is the 10 or T value of the structure. ID values are the
registered GOS codepoints. T values are architecture-specific values relative
to the encompassing ID.

Presence Rule:

Required except when sibling-,ist contains all pertinent 10 or T values. In this
case, the structures specified by sibling_list are the structures being reported
on.

Format:

Undefined byte string

' - Structure_Class

Description:

The structure_class is the class of the reported-on structure and any siblings
identified in sibling_list.

Presence Rule:

If absent, defaults to

Format:

Hexadecimal code

LENGTH-BOUNDED_LT_STRUCTURE.

Byte

Content

0-1

LT header

X'01'
LENGTH-BOUNDED_LLlD_STRUCTURE (10)
X'02'
LENGTH-BOUNDED_LT_STRUCTURE (T) (default)
X'03'
DELIMITED_LLlD_STRUCTURE (DEL-ID)
X'04'
DELIMITED_LT_STRUCTURE (DEL-T)
X'OS'
IMPLlED_LLlD_STRUCTURE (IMP-ID)
X'OB'
IMPLlED_LT_STRUCTURE (IMP-T)
Note: All other values are reserved.

Structure_Position - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structureyosition is either the actual or expected position of this structure within its parent in this particular MU. Multiple consecutive instances of
a repeatable structure share a single position, and can be distinguished by
structure_instance.

Format:

Signed binary integer (1-origin)

13-40

SNA Formats

Structure_lnstanco - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure_instance is used when the structure is one of multiple occurrences of a repeatable structure. The value of structure_instance identifies
the particular instance within a position.

Format:

Signed binary integer (1-origin)

Structure_Segment_Number - - - - - - - - - - - - - - - - - - - - - - - - - - . . . . . ,
Description:

The structure_segment_number is the segment of the structure in which the
condition was detected.

Presence Rule:

Occurs when the beginning of structure_contents was not contained in the first
segment of the reported-on structure.

Format:

Signed binary integer (1-origin)

Structure_Byte_Offset - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_byte_offset marks the start of structure_contents within the
reported-on structure. If structure_segmenCnumber is present, this value is
the offset from the start of the indicated segment; otherwise, it is the offset
from the beginning of the structure.

Format:

Signed binary integer (O-origin)

Sibling_list - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The sibling_list contains a string of ID or T values necessary to describe the
detected condition. The structures identified in sibling_list are children of the
parent identified in parent_spec and/or siblings of the structure identified in
structure_spec. The class of the sibling structures is the same as
structure_class. The expected position, when applicable, is given by
structureyosition.

Presence Rule:

Presence is governed by the SNA_report_code.

Format:

Byte string

Reported-On_Dest_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . . . ,
Descri ption:

The reported-on_destination_list contains the portion of the distribution destinations that are being reported on.

Presence Rule:

Presence is governed by the SNA_report_code.

Descri ption:

The reported-on_destinationyrefix is the prefix of the reportedon_destination_list.

Chapter 13. SNA/Oistribution Services (OS)

13-41

Reported-On_Dest
Description:

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

The reported-on_destination associates reported-on_dest_users with a
reported-on_dest_DSU for those destinations specified in the original distribution request being reported on. For nat destination lists (i.e., lists containing
only DSUs and/or DSU-user pairs),' there are zero or one user names per DSU
list. For factored destination lists, there can be multiple user names per DSU
list.

Reported-On_Dest_DSU
Descri ption:

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

The reported-on_destination_DSU is one of the original destination DSUs
being reported on.

Reported-On_Dest_RGN

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

Description:

The reported-on_destination_RGN is the first part of the name of one of the
original destination DSUs being reported on. This is typically, but not necessarily, the network 10.

Presence Rule:

Absent when passed through an FS1 subnetwork.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

Reported-On_Dest_REN

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

Descri ption:

The reported-on_destination_REN is the second part of the name of one of the
original destination DSUs being reported on. This is typically, but not necessarily, the LU name.

Presence Rule:

Absent when passed through an FS1 subnetwork.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Note:

If a product chooses to implement DGN =REN, the ECS
subset is implemented in a particular network, and any
DGN contains an ECS character that is not an element of
Character Set AR, then ECS characters may occur in this
structure.

Reported-On_Dest_User
Description:

13-42

SNA Formats

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

The reported-on_destination_user is the name of one of the original destination users being reported on.

Reported-On_Dest_DGN

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

Description:

The reported-on_destination_DGN is the first part of the name of one of the
original destination users being reported on.

Note:

In FS1, for a OS condition code of X'OOOD' (lost user names), user names will
be null.

Format:

Character string

CGCSGID:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:

Reported-On_Dest_DEN

Base

Leading, imbedded, and trailing space (X' 40')
characters are not allowed.

ECS

Leading space (X' 40') characters are not allowed,
trailing space characters are not significant, and
imbedded space characters are significant.

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

Description:

The reported-on_destination_DEN is the second part of the name of one of the
original destination users being reported on.

Note:

In FS1, for a OS condition code of X'OOOD' (lost user names), user names will
be null.

Format:

Character string

CGCSGID:

01134-00500 (base), 00930-00500 (enhanced character set)

String Conventions:
Base

Leading, imbedded, and trailing space (X'40')
characters are not allowed.

ECS

Leading space (X'40') characters are not allowed,
trailing space characters are not significant. and
imbedded space characters are significant.

Reported-On_Dest_Suffix ------------------------------------------------,
Description:

The reported-on_destination_suffix is the suffix of the reportedon_destination_list.

Chapter 13. SNA/Oistribution Services (OS)

13-43

Supplemental_Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The supplemental_report contains other information pertaining to a condition.
The contents of the supplemental_report are governed by the
SNA_reporCcode.

Presence Rule:

Presence is governed by the SNA_reporCcode.

Sender_Exception_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The sender_exception_MU is sent from the sender to the receiver when the
sender detects an exception while sending a dist_transport_MU, a
dist_report_MU, or a dist_continuation_MU.

Descri ption:

The receiver_exception_MU is sent from the receiver to the sender when the
receiver detects an exception while receiving a dist_transport_MU, a
dist_report_MU, or a disCcontinuation_MU.

Receiver_Exception_Command - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The receiver_exception_command is the prefix identifying the
receiver_exception_MU.

Sender_Retry_Action - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ptio,;:

The sender_retry_action is the receiver's recommendation to the sender as to
whether to retry the transmission of the MU.

Format:

Hexadecimal code

Byte

Content

0-1

LT header

X'01'
RETRY_PRECLUDED
X'02'
RETRY_ALLOWED
X'03'
RETRY_EXPECTED_USING_DCMU
Note: All other values are reserved.

Receiving_DSU --------------------------------~

Descri ption:

13-44

SNA Formats

The receiving_DSU is the name of the DSU to which a distribution was being
sent.

Recelvlng_RGN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The receiving_RGN is the first part of the name of the DSU to which a distribution was being sent. This is typically, but not necessarily, the network 10.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Recelvlng_REN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,
Description:

The receiving_REN is the second part of the name of the DSU to which a distribution was being sent. This is typically, but not necessarily, the LU name.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Note:

If a product chooses to implement DGN =REN, the
enhanced character set (ECS) subset is implemented in a
particular network, and any DGN contains an ECS character that is not an element of SNA Character Set AR,
then ECS characters may occur in this structure.

Completlon_Query_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - . . ,
Description:

The completion_query_message_unit is sent by the sending DSU to query the
completion status of a particular MU at the receiving DSU.

Completlon_Report_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The completion_report_message_unit is sent by the receiving DSU to report on
the completion status of a particular MU or to control traffic flow on a conversation.

Indicator_Flags - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The indicator_flags structure contains a 1-byte flag, to indicate the completion
status of the MU)D identified in a compJetion_report_MU, or to control traffic
flow on a conversation.

Format:

Bit string

Note:

Conversation control flags (bits 2 and 3) may be used in conjunction with flow
control flags (Not Received, In Transit, Suspended, Terminated, Completed,
Purged).

Chapter 13. SNA/Oistribution Services (OS)

13-45

Bit Map

Architecturally-Defined
Value

x
x

0
0

0
1

x
x

Default-Normal OS flow
Terminate Conversation

0
0
0
0
1
x

0
0
1
1
0
x

0
1
0
1
1
x

Not Received
In Transit
Suspended
Completed
Terminated
Purged

0
x
0
x
0
x
0
x
0
x
1
x
Note: x

x
x
x
x
x
x

x
0
x
0
x
0
x
0
0
x
x
x
any value

Last_Structure_Received - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

Last_structure_received is the codepoint of the structure the receiving DSU
identifies as the last structure received before the MU was suspended. This
structure must be a length-bounded LLiD structure at the .highest level of the
MU.

Presence Rule:

If indicator_flags

Format:

Hexadecimal code

= SUSPENDED, then last_structure_received is present.

Last_Byte_Received - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

Last_byte_received is the last byte received by the receiving DSU before the
MU was suspended. The byte count begins with the first byte of atomic data
within the encompassing structure. A byte count of X'FFFFFFFFFFFFFFFF' indicates that the structure was fully received. The byte count contains only
atomic data and does not contain the segmenting LLs for segmented structures.

Presence Rules:

If indicator_flags
SUSPENDED, last_structure_received is present, and
last_byte_received is absent, then the structure was received.

Format:

Unsigned binary integer (1-origin)

Purge_Report_MU -------------------------------------------------....,
Description:

The purge_report_message_unit indicates to the receiving DSU that the
sending DSU has marked a particular MU-,D PURGED, and that the receiving
DSU may flag that MU_ID as PURGED.

Reset_Request_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

13-46

SNA Formats

The reset_request_message_unit is sent from OS_Send to OS_Receive.
OS_Send issues the reset_request_MU to request that OS_Receive reset its
MU-,D registry.

Reset_DTM --------------------------------------------------------------~
Description:

The reset_date-time contains the date and time at which the reset_requesCMU
was generated. Both sender and receiver store it as the "time of last reset" of
their MU_ID registries.

Length Restriction:

Originating FS2 DSUs always generates a GMT-based time. The minimum
length for reset_DTM is 11 (1-origin).

Format:

Byte string

Byte

Content

0-1

LT header

2-3
4
S-

DATE
Year, in binary (e.g., 1989 is encoded as X'07CS')
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)

6
7
8
9

TIME
Hour of the day, in binary (values from 0 to 23 are valid)
Minute of the hour, in binary (values from 0 to S9 are valid)
Second of the minute, in binary (values from 0 to S9 are valid)
Hundredth of the second, in binary (values from 0 to 99 are valid)
GMT FLAGS
Indicates that specified TIME is GMT and identifies whether offsets
from GMT are required to calculate local time. (Equivalent
EBCDIC characters are shown in parentheses.)
X'E9'
(2)
no offset required
(+) add required offset to GMT to get
X'4E'
local time
X'60'
(-)
subtract required offset from GMT to get
local time
Note: All other values are reserved.

Hour offset from GMT, in binary, occurs when GMT flag =f= X'E9'
(values from 0 to 23 are valid)
Minute offset from GMT, in binary, occurs when GMT flag =f= X'E9'
(values from 0 to S9 are valid)

11
12

Examples:
A 9-byte date-time encoding is a date-time followed immediately by an EBCDIC
"z" and is considered to be GMT. Thus, 12:00GMT on 2 January 1988 would be

X' 07C401020C0eeeeeE9 1
yyyyMMddHHmmsshhZ
An 11-byte date-time encoding is a date-time followed immediately by an
EBCDIC" +" or "-" and two 1-byte binary numbers, and is considered to be
GMT and the offset from GMT to local time. Thus, 7:00am on 2 January 1988 in
New York would be 12:00GMT - S hours, or

X' 07C40102eCeeeeee6eeSee '
yyyyMMddHHmmsshh- HHmm

Chapter 13. SNA/Oistribution Services (OS)

13-47

Reset_Accepted_MU --------------------------------------------------------~

Oescri ption:

The reset_accepted_message_unit is sent from OS_Receive to OS_Send.
OS_Receive issues the reseCaccepted_MU in response to a reseCrequesCMU
to inform OS_Send that DS_Receive has reset its MUJO Registry.

Unrecognized_Reserve - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Oescri ption:

The unrecognized_reserve is the number of bytes reserved for unrecognized
structures. An unrecognized structure occurs within its parent structure.
The number of unrecognized structures allowable for a particular parent
structure is limited by the number of children allowable for that parent
structure.
Intermediate FS2 OSUs pass unrecognized_reserve structures through
unchanged in outgoing OMUs.

Format:

13-48

SNA Formats

Undefined byte string

Header Description Tables for FS1 Message Units
DISTRIBUTION MESSAGE UNIT (DIST_MU)
Figure 13-12 (Page 1 of 2). Distribution Message Unit (DIST_MU)
Children
Structure Name

Struct
Ref Po

Struct
Class

I oFIT

Lenoth

Occurrences

Unrec

Order

Num
3-4

Sub
Table

Olst_MU

13-53

Oel-IOF

pf><

~148

Prefix

13-53

IOF/pf><

C00102

5-21

Dist_Command

13-53

IDF/seg

Cl0502

138-32511

2-3

13-53

Imp-IDF

Ide

58-774

2-5

Servieo_Dese_Operand s

13-53

IOF/ide

C34041

28-107

5-7

Origin_RGN

13-19

3-10

0-1

Origln_REN

13-19

3-10

Origin_DGN

13-19

2-10

Origin_DEN

13-20

2-10

Origln_Seqno

13-54

Origln_DTM
Agent_Correl

13-22

3-46

0-1

Dist_Gen_Options

13-54

IDF

C33D41

30-58

Dist_Flags (FS1)

13-55

Hop_Count

13-13

Serviee_Parms

13-15

11-32

Server_Obj ect) nd

13-55

Origin_Agent

13-18

3-10

Report-To_Address

13-55

IDF

C36041

14-45

0-1'"

3-4

Report-To_RGN

13-22

3-10

0-1

Report-To_REN

13-22

3-10

DlsUD

Report-To_DGN

13-23

3-10

Report-To_DEN

13-23

3-10

Report-To_Options

13-56

IDF

C34341

8-47

0-1'"

1-2

Report_Servlee_Parms

13-24

11-32

0-1

Report-To_Agent

13-26

3-10

0-1

13-29

IDF

C32D01

6-517

0-1

13-56

Imp-IDF

ide

~75

8egin_Dest_Operands

13-57

IDFlide

C35001

De st_RGN_Li st

13-57

Imp-IDF

ide

~62

Dest_RGN

13-28

IDF/ide

C35201

5-13

Agent_Object
Desti nati on_Operand s

8egin_REN_List

13-57

IDF

C35001

Dest_REN_LI st

13-57

Imp-IDF

ide

~44

Dest_REN

13-28

IDF/ide

C35301

6-13

13-57

IDF

C35001

8egin_DGN_List

Dest_DGN_List

13-58

Del-IDF

pf><

~25

Dest_DGN

13-28

IDF/pf><

C35401

6-13

8egi n_DEN_Li st

13-58

IDF

C35001

Dest_DEN

13-29

IDF

C35501

6-13

Chapter 13. SNA/Distribution Services (OS)

13-49

Figure 13-12 (Page 2 of 2). Distribution Message Unit (DI5T_MU)
Children
Slruct
Class

IDFIT

13-58

I OF/sf><

C35101

13-58

10F

C35101

13-58

10F

C35101

End_Oest_Operands

13-58

10F

C35101

Olst_Report_Operands

13-59

Imp-IOF

idc

~63

0-1*

Slructuro Name

End_DEN_List
End_OGN_Llst
End_REN_Llst

Struct
Ref Pg

Length

Occurrences

Unrec

Order

Num

Sub
Table

2·4

13·51

13-58

Imp-IOF

idc

~14

0-1*

13-58

10F/idc

C90A41

8-280

1-3

Server_ObLByte_Count

13-18

0-1

Server

13-18

3-10

13-58

3-255

0-1

Server_Object

13-29

10F/seg

C90801

~6*

Server_Parms

OS_Suffix (FS 1)

13-59

10F

CF0100

01 st_Server_Operand s
Server_Prefix

Nole:
• * Refer to FS1 Structure Descriptions starting on page 13-53 for presence rules and length restrictions.

• Dist_Repart_Operands does not occur for Olst_MU type TRANSPORT.
• Agent_Carrel, Report-To_Address, Repart-To_Optlons. AgenCObject. and Dlst_Server_Operands do not occur for Oist_MU type REPORT.
;0

DesCRGN_List, Dest_REN_List, Dest_DGN_List. and Dest_DEN occur only one time for DisUviU type REPORT.

13·50

5NA Formats

015T REPORT OPERANDS
Figure 13-13. Distribution Report Operands
Children
Structure Nama

Struct
Ref Pg

Struct
Class

Length

IDFIT

Occurronces

Unrec

Order

Num

Sub
Table

01 st_Report_Operands

13-59

Imp-IOF

Ide

~63

0-1

2-4

Report_Operands

13-59

Imp-IOF

Ide

27-112

1-2

13-59

10F/lde

C34041

27-87

4-5

Reported-On_Orl 9 I n_DGN

13-33

3-10

Reported-On_Orlgln_DEN

13-33

3-10

Reported-On_Seqno

13-59

Reported-On_DTM

13-60

Reported-On_Agent_Correl

13-36

3-46

0-1

13-44

10F

C36141

8-25

0-1

1-2

13-44

3-10

0-1

Ropo"_Corrol atl on

Reeeivi ng_OSU

Reeeiving_REN

13-45

3-10

Gen_SNAOS_Report

13-60

Imp-IDF

Ide

0-1'"

Gen_SNADS_Type

13·60

IDF/ldc

C35601

Gen_SNADS_Contents

13-61

10F

C35741

13-61

Gen_DIA_Report

13-61

Imp-IDF

ide

14-524

0-1'"

Gen_DIA_Type

13-62

IDF/lde

C35601

Gen_DIA_Contents

13-62

IDF

C35741

7-517'"

13-62

Imp-IDF

Ide

~36

Receivi ng_RGN

Gen_SNADS_Cond_Codo

13-63

Imp-IDF

idc

5-553

1-3

Reported-On_Dest_OEN

13-43

IDF/ide

C35501

5-13

Spec_SNAOS_Report

13-63

Imp-IOF

Idc

0-1'"

Spec_SNADS_Type

13-63

IDF/idc

C35601

Spec _S NADS _ Cont

13-63

IDF

C35741

13-64

Spee_DIA_Report

13-64

Imp-IOF

Ide

14-524

0-1'"

Spee_DIA_Type

13-65

IDF/ldc

C35601

Spec_DIA_Contents

13-65

IDF

C35741

7-517'"

13-65

10F

C35101

13-65

IDF

C35101

Specific_Report

Begin_Report_DGN_Llst

13-62

IDF/ide

C35001

Report_OGN_Li st

13-62

Imp-IDF

Idc

~23

Reported-On_Dest_DGN

13-43

10F/ldc

C35401

5-13

13-62

IDF

C35001

Begi n_Report_DEN_LI st
Report_DEN_LI st

Spec_SNADS_CC

End_Report_OEN_Li st
End_Report_OGN_Llst

Note:

'" Refer to FS1 Structure Descriptions starting on page 13-53 for presence rules and length restrictions.

Chapter 13. SNA/Distribution Services (OS)

13-51

SENDER EXCEPTION MESSAGE UNIT (TYPE FS1)
Figure 13-14. Sender Exception Message Unit (type FS1)
Children
Structure Name

Sender_Exception_MU (FS 1)

Struct
Ref Pg
13·66

Struct
CI.ass
IOF

IDFIT

CF0201

Length

Occurrences
1

Unrec

Order

Num

Sub
Table

RECEIVER EXCEPTION MESSAGE UNIT (TYPE FS1)
Figure 13-15. Receiver Exception Message Unit (type FS1)
Children
Structure Name

Struct
Ref Pg

Struct
Class

I oFIT

Length

Occurrences

Unrec

Order

Num

Sub
Table

13·44

Oel·IOF

pf><

59-863

Prefix

13·53

IOF/pf><

C00102

Receiver_Exception_Command

13·66

IOF

C10101

49·853

Receiver_Exception_Correl

13·67

IOF

C32801

7-23

Exception_And_Reply_Oata

13·67

Imp-IOF

ide

37·825

Receiver_Exception_Code

13·67

IOF/ide

C32201

8·255

13~SS

IDF

C34S01

29-570

"'""+ ...
""'''''7_'''~·W

Receiver_Exception_MU (FS1)

C .... ",h.

...,

,"'1'1

...

13·44

IOF

C36141

8·25

1-2

Reeeiving_RGN

13·44

3·10

0·1

13·45

3-10

Recelving_REN

13·69

Imp·IOF

Ide

SNAOS_Report_Type

13·69

IOF/ide

C35601

SNAOS _Report_Cont

13·69

IOF

C35741

13·69

13·70

Imp·IOF

ide

14-524

0·1

13·70

IOF/ide

C35601

13·70

IOF

C35741

7-517

13·59

I OF/sf><

CF0100

Reeeivi ng_OSU

SNAOS_Report

SNAOS_Report_CC
OIA_Report
OIA_Report_Type
OIA_Report_Cont
OS_Suffix (FS1)

13-52

SNA Formats

FS1 Structure Descriptions
Dlst_MU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,

Description:

The distribution_message_unit transports user information to one or more distribution service users. A Dist_MU can be one of two types based on the
value of dist_flags (type FS1): TRANSPORT or REPORT. A Dist_MU type TRANSPORT transports agent and/or server objects. A Dist_MU type REPORT transports information reporting on the state of the distribution.

Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The prefix identifies the beginning of a message unit and may contain a
message-unit identifier.

Format:

Undefined byte string

Dlst_Command - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The distribution_command contains all information used by each DSU to transport the distribution for a Dist_MU type TRANSPORT. For a Dist_MU type
REPORT, the distribution_command contains the control information for the distribution report.

Service_Desc_Operands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The service_description_operands contain all the information, except for the
destination list, required by each DSU to transport the distribution.

DlstJD - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_identifier contains information corresponding to the distribution originator.

Chapter 13. SNA/Oistribution Services (OS)

13-53

Origin_Seqno - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The origin_sequence_number is the number assigned to the distribution by the
origin_DSU. The value ranges from 1 to 9999 for a Dist_MU type TRANSPORT,
and is always 0 for a Dist_MU type REPORT.

Format:

Character string; each character is the EBCDIC representation of one digit of
the sequence number.

Byte

Content

0-1
2-5
Notes:

LT header
Sequence number

• For Dist_MU type
• For Dist_MU type

values range from X'FOFOFOF1' to X'F9F9F9F9'.
value is X'FOFOFOFO'.

TRANSPORT,
REPORT,

Origin_DTM - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The origin_date-time is the date and time the distribution was originated by
the origin DSU. Time is assumed to be local.

Format:

Byte string

Byte

Content

0-1

LT header

2-3
4
5

DATE
Year, in binary (e.g., 1989 is encoded as X'07C5')
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)

7
8
9

Example:
The date-time encoding for 12:00 noon on 2 January 1988 is:

X' 07C4S1S2scsseeee '
yyyyMMddHHmmsshh

Dist_Gen_Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . . . ,
Description:

13-54

SNA Formats

The distribution_genera/_options contains structures used by DS to condition
its processing of the distribution.

Dlst_Flags (type FS1) - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_flags indicate reporting services requested by the origin
agent.

Format:
Bit

Content

2-7

Exception Report bit:
DS is requested to generate a report in case
of an exception.
1 A report will not be generated by DS for this
distribution.
Distribution Message Unit type bit:
o Distribution is of type TRANSPORT.
1 Distribution is of type REPORT.
Reserved

Byte

Content

0-1

LT header

X'OO'
X'80'
X'CO'
Note:

Dist_MU type TRANSPORT with report requested
Dist_MU type TRANSPORT with no report requested
Dist_MU type REPORT with no report requested
All other values are reserved.

Server_Object_lnd - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The server_objecCindicator indicates whether a server_object is present or
not. The only values supported are 0 and 1.

Presence Rule:

Contains X'0001' only for Dist_MU type

Format:

Hexadecimal code

TRANSPORT.

Byte

Content

0-1

LT header

2-3

X'OOOO' no server_object present in this MU
X'0001' a server_object present in this MU
Note: All other values are reserved.

Report-To_Address -------------------------------~

Description:

The report-to _address contains the name of the DSU and user to which any
distribution reports are sent.

Presence Rule:

This information may be present only in Dist_MU type

TRANSPORT.

Chapter 13. SNA/Distribution Services (DS)

13-55

Report-To_Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,
Descri ption:

The report-to_options contains information involved in processing any reports
generated as part of the distribution.

Presence Rule:

This information may be present only in Dist_MU type

TRANSPORT.

Destination_Operands - - - - - - - - - - - - - - - - - - - - - - - - - - . . . ,
Descriptiqn:

The destination_operands are the list of destinations for the distribution. Up to
256 destinations are allowed if the distribution is of type TRANSPORT; exactly
one destination, if the distribution is of type REPORT. The destinations are
encoded as a fully factored, partially factored, or unfactored list of users and
DSUs (see the following example).

Example: The 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.U5, A.LDC.U6, A.L.DD.U7, A.L.DD.U8,
B.M.DE.U9, B.M.DE.U10, B.M.DF.U11, B.M.DF.U12,
B.N.OG.U13, B.N.DG.U14, B.N.DH.U15, and B.N.DH.U16.
The list may appear factored in destination_operands as follows:
• Fully factored:
A(K(DA(U1 .
U2)
DB(U3
I I iI\\

U"tll

L(DC(U5
U6)
DD(U7
U8)))
B(M(DE(U9
U10)
DF(U11
U12))
N(DG(U13
U14)
DH(U15
U16))))
• Partially factored:
(A(K(DA(U1)
DA(U2)
DB(U3
U4))
L(DC(U5
U6))
L(DD(U7
U8)))
B(M(DE(U9
U10)
DF(U11
U12))
N(DG(U13))
N(DG(U14))

13-56

SNA Formats

N(DH{U15
U16))))
• Unfactored. equivalent to the initial list:
(A{K(DA(U1)))
A(K{DA(U2)))
A(K(D8(U3)))
A(K(D8(U4)))
A(L(DC(U5)))
A(L(DC(U6)))
A{L(DD(U7)))
A(L(DD(UB)))
8{M(DE(U9)))
8(M(DE(U10)))
8(M(DF(U11)))
8(M(DF(U12)))
8(N(DG(U13)))
8(N(DG(U14)))
8(N(DH(U15)))
8(N(DH(U16))))
In the above lists. "(" represents begin_dest_operands. begin_REN_list. begin_DGN_list. or
begin_DEN_list. ")" represents end_DEN_list. end_DGN-'ist. en d_REN_lis t. or end_dest_operands.
(Inner parentheses have precedence over outer parentheses.)
Begln_Dest_Operands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The beginning_of_the_destination_operands marks the beginning of the
destination_list.

Format:

Constant byte string; value is X'C35201'

Dest_RGN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Description:

The destination_RGN_list associates one destination RGN with at least one
destination REN.

Begin_REN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The beginning_of_the_destination_REN_list marks the beginning of a list of one
or more dest_REN(s).

Format:

Constant byte string; value is X'C35301'

Dest_REN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The destination_REN-'ist associates one destination REN with at least one
destination DGN.

Begin_DGN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The beginning_of_the_destination_DGN_list marks the beginning of a list of
one or more dest_DGN(s).

Format:

Constant byte string; value is X'C35401'

Chapter 13. SNA/Oistribution Services (OS)

13-57

Dest_DGN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,

Description:

The destination_DGN_list associates one dest_DGN with at least one
dest_DEN.

8egin_DEN_Llst - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . ,

Descri ption:

The beginning_o'-the_destination_DEN_list marks the beginning of a list of one
or more dest_DEN(s).

Format:

Constant byte string; value is X'C35501'

End_DEN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,

Descri ption:

The end_destination_DEN_list marks the end of the list begun by the corresponding begin_DEN_list.

End_DGN_Llst --------------------------------------------------------...,

Descri ption:

The end_destination_DGN_list marks the end of the list begun by the corresponding begin_DGN_list.

End_REN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The end_destination_REN-'ist marks the end of the list begun by the corresponding begin_REN_list.

End_Dest_Operands ---------------------------~------~

Descri ption:

The end_destination_operands marks the end of the destination_list.

Dist_Server_Operands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_server_operands structure contains the server-prefix and the
server_object.

Presence Rule:

This information occurs only in Dist_MU type
server_objectjnd =X'0001'.

TRANSPORT

when

Server_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . ,

Description:

The server-prefix contains information associated with the server_object.

Server_Parms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . . . ,

Description:

The server-parameters structure contains parameters passed by DS to the
destination server. This structure is never sent. and is retired in FS2.

Format:

Undefined byte string

13-58

SNA Formats

OS_Suffix (FS1) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The distribution_services_suffix contains no information and marks the end of
the message unit.

Dlst_Report_Operands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The distribution_report_operands structure contains all the report information
describing the condition of a particular distribution.

Presence Rule:

This information occurs only when Dist_MU is of type REPORT.

Report_Operands ------------------------------------------------------------~
Description:

The report_operands structure contains all information pertaining to the originator of the distribution and the detector of an exception.

Report_Correlation -----------------------------------------------------------.
Description:

The report_correlation contains information that uniquely identifies a distribution being reported on.

Reported-On_Seqno ------------------------------------------------------~
Descri ption:

The reported-on_origin_sequence_number is the sequence number of the distribution being reported on.

Format:

Character string; each character represents the EBCDIC representation of
one digit of the sequence number.

Byte

Content

0-1

LT header

2-5

Sequence number
Note: Values range from X'FOFOFOF1' to X'F9F9F9F9'.

Chapter 13. SNA/Oistribution Services (OS)

13-59

Reported-On_DTM
Description:

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

The reported-on_date-time is the date and time the distribution was originated.

Byte

Content

0-1

LT header

2-3
4
5

DATE
Year, in binary (e.g., 1989 is encoded as X'07C5')
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 O·to 59 are valid)
Hundredth of the second, in binary (values from 0 to 99 are valid)

6
7

8
9

Example:
The date-time encoding for 12:00 noon on 2 January 1988 is:

x 07C40102eceeeeee
I

yyyyMMddHHmmsshh

Gen_SNADS_Report

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

Description:

The genera/_SNADS_report contains the DS report applicable to each user
specified in specific_report for which a spec_SNADS_report is not supplied.

Note:

Older DSUs may generate both gen_SNADS_report and gen_DIA_report in a
single MU. All DSUs are able to receive such MUs. However, DSUs may
ignore gen_DIA_report if gen_SNADS_report is present. A sending DSU never
generates both a DIA report and a DS report for multiple destinations.

Presence Rule:

This information occurs when gen_SNADS_type

= X'0001'.

Gen_SNADS_Type --------------------------------------------------------,
Descri ption:

The genera,-SNADS_type indicates that a DS condition is being reported.

Format:

Hexadecimal code

13-60

SNA Formats

Byte

Content

0-4

LLlDF header

5-6

X'0001' DS report
Note: Any other value indicates that this is not a
gen_SNADS_report.

Gen_SNADS_Content
Descri ption:

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

The genera,-SNADS_contents contains information describing the condition
being reported on.

Gen_SNADS_Cond_Code

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

Description:

The genera,-SNADS_condition_code is the particular condition being reported
on.

Format:

Hexadecimal code

Gen_DIA_Report

Byte

Content

0-1

LT header

2-3

X'0001'
X'0002'
X'0003'
X'0004'
X'OOOS'
X'0006'
X'0007'
X'0008'
X'OOOg'
X'OOOC'
X'OOOD'
X'OOOE'
X'OOOF'
X'0010'
X'0011'
X'0012'
X'0013'

routing exception
unknown user name
hop count exhausted
format exception
function not supported
specific-server exception
unknown resource name (specific server)
invalid server parameters
unknown resource name (destination agent)
operator intervention (purging)
user names lost
resource not available
system exception
insufficient resource
storage-medium exception
REMU exception
server object size incompatible with capacity
level
Note: All other values are reserved.

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

Description:

The general_DIA_report describes an application-layer condition. The
gen_DIA_report applies to all users specified in specific_report. The interaction between gen_DIA_report and spec_DIA_report is defined by DIA.

Note:

Older DSUs may generate both gen_SNADS_report and gen_DIA_report in a
single MU. All DSUs can receive such MUs. However, OSUs may ignore
gen_DIA_report if gen_SNADS_report is present. A sending OSU never generates both a OIA report and a OS report for multiple destinations.

Presence Rule:

This information occurs when gen_DIA_type

=1=

X'0001'.

Chapter 13. SNA/Oistribution Services (OS)

13-61

Gen_DIA_Type ----------------------------------------------------------~
Description:

The general_DIA_type indicates the type of DIA condition being reported.

Format:

Hexadecimal code

Byte

Content

0-4

LLlDF header

5-6

X'0001' indicates this is not a gen_DIA_report
X'0200' DIA application exceptions
X'FEFF' reserved for 5520 migration
Note: All other values are reserved.

Gen_DIA_Contenb --------------------------------------------------------~
Description:

The general_DIA_contents structure contains a DIA-defined byte string.

Length Restriction:

Older DSUs may generate MUs with length of up to 517. All DSUs receive
such MUs without generating an exception. However, DSUs may modify such
MUs to force the length to be 69 or less. For gen_DIA_type of X'0200' (DIA
application exceptions), the truncation algorithm is given in the DIA Transaction Programmer's Guide. The length is at least 7, since gen_DIA_contents
contains at least a null LT '(an LT of length 2).

Format:

Undefined byte string

Specific_Report -----------------------------------------------------------,
Description:

The specific_report contains the portion of the destination users that are being
reported on. Any specific OS and/or DIA reports are also specified within this
structure.

8egln_Report_DGN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The beginning_of_report_DGN_list marks the beginning of the specific_report.

Format:

Constant byte string; value is X'C35401'

Report_DGN_List --------------------------------------------------------~
Description:

The report_DGN_list associates one reported-on_dest_DGN with at least
one reported-on_dest_DEN.

Begin_Report_DEN_List -----------------------------------------------------,
Descri ption:

The beginning_o'-report_DEN-'ist marks the beginning of a list of one or more
reported-on_dest_DENs.

Format:

Constant byte string; value is X'C35501'

13·62

SNA Formats

Report_DEN_Llst
Description:

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

The report_DEN-'ist associates one reported-on_dest_DEN with a specific DS
and/or DIA report.

Spec_SNADS_Report------------------------------------------------------~

Descri ption:

The specific_SNADS_report is a report on one particular user. This report
overrides the gen_SNADS_report, if one exists, for that particular user.

Note:

Older DSUs may generate both spec_SNADS_report and spec_DIA_report in a
single MU. All DSUs can receive such MUs. However, DSUs may ignore
spec_DIA_report if spec_SNADS_report is present. A sending DSU never generates both a DIA report and a DS report for multiple destinations.

Presence Rule:

This information occurs when spec_SNADS_type

Spec_SNADS_Type

= X'0001'.

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

Description:

The specific_SNADS_type indicates that a DS condition is being reported.

Format:

Hexadecimal code

Byta

Contont

0-4

LLlDF header

5-6

X'0001' DS report
Note: Any other value indicates that this is not a
spec _SNADS _report.

Spec_SNADS_Cont
Descri ption:

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

The specific_SNADS_contents contains information describing a condition
being reported on.

Chapter 13. SNA/Oistribution Services (OS)

13-63

Spec_SNADS_CC

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

Oescri ption:

The specific_SNADS_condition_code describes the particular condition being
reported on.

Format:

Hexadecimal code

Spec_DIA_Report

Byte

Content

0-1

LT header

2-3

X'0001'
X'0002'
X'0003'
X'0004'
X'OOOS'
X'0006'
X'OOO?'
X'0008'
X'0009'

routing exception
unknown user name
hop count exhausted
format exception
function not supported
specific-server exception
unknown resource name (specific server)
invalid server parameters
unknown resource name (destination agent)
x'oooe' operator intervention (purging)
X'OOOD' user names lost
X'OOOE' resource not available
X'OOOF' system exception
X'0010' insufficient resource
X'0011' storage-medium exception
X'0012' REMU exception
X'0013' server object size incompatible with capacity
level
Note: All other values are reserved.

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

Descri ption:

The specific_DIA_report describes a OIA-specific report on one particular
user.

Note:

Older OSUs may generate both spec_SNADS_report and spec_DIA_report in a
single MU. All DSUs can receive such MUs. However. OSUs may ignore
spec_DIA_report if spec_SNADS_report is present. A sending OSU never generates both a DIA report anda OS report for multiple destinations.

Presence Rule:

This information occurs when spec_DIA_type

13-64

SNA Formats

=1=

X'0001'.

Spac_DIA_Typa ----------------------------------------------------------~
Description:

The specific_DIA_type indicates the type of DIA condition being reported.

Format:

Hexadecimal code

Byte

Content

0-4

LLlDF header

5-6

X'0001' indicates this is not a spec_DIA_report
X'0200' DIA application exceptions
X'FEFF' reserved for 5520 migration
Note: All other values are reserved.

Spec_DIA_Conten~ --------------------------------------------------------~

Description:

The specific_DIA_contents structure contains a DIA-defined byte string.

Length Restriction:

Older DSUs may generate MUs with length of up to 517. All DSUs receive
such MUs without generating an exception. However, DSUs may modify such
MUs to force the length to be 69 or less. For spec_DIA_type of X'0200' (DIA
application exceptions), the truncation algorithm is given in the DIA Transact/on Programmer's Gu/de. The length is at least 7, since spec_DIA_contents
contains at least a null LT (an LT of length 2).

Format:

Undefined byte string

End_Report_DEN_List - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The end_reporCDEN_list marks the end of the list begun by
b egin_rep orCDEN_lis t.

End_Report_DGN_Llst - - - - - - - - - - - - - - - - - - - - - - - - - - - - . ,
Descri ption:

Chapter 13. SNA/Oistribution Services (OS)

13-65

Description:

The sender_exception_MU (type FS1) is sent from the sender to the receiver
when the sender detects an exception while sending a Dist_MU.

Format:

Byte string

Byte

Bit

0-4

LLlDF header

0-1

Severity:
11
catastrophic

2-7

Class:
000101 sender

Content

Exception condition code:
X'06'
execution terminated
X'OB' 110 error
X'OF'
length invalid
X'18'
content error

Exception object:
X'01'
IU prefix
X'07'
command
X'OC' document unit
X'13'
IU suffix
X'17'
unknown subfield
X'1A' distribution object prefix
X'1 B' distribution object data
Note: Other values and their corresponding meanings are represented under
receiver_exception_code.
7

Descri ption:

The receiver_exception_MU (type FS1) is sent from the receiver to the sender
when the receiver detects an exception while receiving a Dist_MU.

Description:

The receiver_exception_command contains all information used for identifying
the exception that occurred.

13-66

SNA Formats

Recelver_Exceptlon_Correl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The receiver_exception_correlation contains the prefix ID value from the
rejected Dist_MU.

Format:

Byte string

Byte

Content

0-4

LLlDF header

Correlation field:
X'OO'
Note: All other values are reserved.

Command sequence number:
X'01'
Note: All other values are reserved.

7-22

Correlation MU ID; value from the prefix of the Dist_MU

Exceptlon_And_Reply_Data - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The exception_and_reply_data contains information pertaining to the exception
causing the rejection of the Dist_MU.

Description:

The receiver_exception_code identifies the type of exception encountered and,
conditionally, the portion of the Dist_MU containing the exception.

Format:

Byte string

Byte

Bit

Content

0-4·

LLlDF header

Severity:
11
catastrophic
Note: All other values for bits 0-1 are reserved.

0-1

2-7

Class:
000010 syntactic
000011 semantic
000100 process
Note: All other values for bits 2-7 are reserved or
defined elsewhere.
Exception condition code
(indicates reason for exception):
X'01'
function not supported
X'02'
data not supported
X'04'
resource not available
X'06'
execution terminated
Chapter 13. SNA/Oistribution Services (OS)

13·67

Byte

Bit

Content

data not found
X'07'
X'OB'
segmentation
X'OA' sequence
X'OB' I/O error
X'OC' ID invalid
X'OE'
format invalid
length invalid
X'OF'
invalid
indicator
X'10'
X'11'
range exceeded
subfield length invalid
X'15'
subfield type invalid
X'16'
invalid parameters
X'17'
content error
X'1B'
Note: All other values are reserved.

Exception object
(indicates the syntactical entity in error):
X'01'
IU prefix
X'02'
IU identifier
command
X'07'
X'OB'
command operand
nnot'!:Inn
\ I !:I It
X'09'
"-',.,"" ............... w ....
X/~C'
document unit
X'OD' document unit identifier
document profile
X'OE'
document profile parameter
X'OF'
document content introducer
X'10'
X'11'
document content control
document content data
X'12'
IU suffix
X'13'
segment
X'14'
unsupported subfield
X'16'
X'17'
unknown subfield
X'1A' distribution object prefix
X'1B' distribution object data
Note: All other values are reserved.
10

B-254

Exception data
contains the Dist_MU structures in error

Reply_Data - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

13-68

SNA Formats

The reply_data describes which DSU rejected the Dist_MU and why the
Dist_MU was rejected.

SNADS_Report
Description:

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

The SNADS_report contains information describing the particular DS exception
that caused the Dist_MU to be rejected.

SNADS_Report_Type

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

Description:

The SNADS_report_type indicates that a DS exception is being reported.

Format:

Hexadecimal code

Byte

Content

0-4

LLIOF header

5-6

X'0001' OS report
Note: Any other value indicates that this is not a SNA DS_rep ort.

SNADS_Rep~rt_Cont--------------------------------------------------------~

Descri ption:

The SNADS_report_contents structure contains information describing the type
of OS condition in the Oist_MU.

SNADS_Report_CC
Description:
Format:

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

The SNADS_report_condition_code describes the particular OS condition that
. caused the Oist_MU to be rejected.
Hexadecimal code

Byte

Content

0-1

LT header

2-3

X'0001'
X'0002'
X'0003'
X'0004'
X'OOOS'
X'0006'
X'0007'
X'0008'
X'0009'
X'OOOE'
X'OOOF'
X'0010'
X'0011'
X'0013'

routing exception
unknown user name
hop count exhausted
format exception
function not supported
specific-server exception
unknown resource name (specific server)
invalid server parameters
unknown resource name (destination agent)
resource not available
system exception
insufficient resource
storage-medium exception
server object size incompatible with capacity
level
Note: All other values are reserved.

Chapter 13. SNA/Distribution Servic~s (DS)

13-69

DIA_RepOM

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

Description:

The DIA_report describes a DIA condition being reported.

Note:

When generating a Dist_MU type REPORT with report information supplied by a
REMU (type FS1), the reporting DSU may ignore DIA_report.

Presence Rule:

This information occurs when gen_DIA_type

DIA_RepoM_Type

=1=

X'0001'.

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

Description:

The DIA_report_type indicates the type of DIA condition being reported.

Format:

Hexadecimal code

DIA_RepOM_Cont

Byte

Content

0-4

LLlDF header

5-6

X'0001' indicates this is not a DIA_report
X'0200' DIA application exceptions
X'FEFF' reserved for 5520 migration
Note: All other values are reserved.

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

Description:

The DIA_report_contents structure contains a DIA-defined byte string.

Format:

Undefined byte string

13-70

SNA Formats

Transaction Program and Server Names
Following is a list of all transaction program and server names defined for
SNA/DS, in the FM header 5 (Attach), in the Distribution MU, 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'20FOFOF2'

DIASTATUS transaction program name

X'21FOFOF1'

OS_SEND transaction program name (FS1)

X'21 FOFOF2'

OS_RECEIVE transaction program name (FS1)

X'21FOFOF3'

DS_ROUTER_DIRECTOR transaction program name

X'21 FOFOF6'

SNA/DS general server name

X'21 FOFOF7'

OS_SEND transaction program name (FS2)

X'21 FOFOF8'

OS_RECEIVE transaction program name (FS2)

X'23FOFOFO'

SNA/MS Change Management agent TP name

X'24FOFOFO'

SNA/File Services server name

X'30FOFOF2'

Object Distribution transaction program for IBM System 36 and
System 38.

X'30FOFOF3'

Object Distribution server transaction program for IBM System
36 and System 38.

Chapter 13. SNA/Distribution Services (DS)

13-71

Code Points Used by SNA/DS FS2
The values of the 10 component of the LLiD structure as used for SNA/DS GOS
variables are shown below:

13-72

SNA Formats

Structure Name

1532

SNA Condition Report

1570

Transport Prefix

1571

Transport Command

1572

Destination List

1573

Agent Object

1574

Server Object

1575

Report Command

1576

Report Information

1577

Receiver Exception Command

1578

Sender Exception Message Unit (type FS2)

1579

Completion Query Message Unit

157A

Completion Report Message Unit

1578

Continuation Prefix

157C

Report Prefix

157E

Purge Report Message Unit

157F

Suffix

1580

Supplemental Distribution Inf02

1582

Reported-On Supplemental Distribution Inf02

1583

Report-To DSU/User

1585

Reset Request Message Unit

1586

Reset Accepted Message Unit

Code Points Used by SNA/DS FS1
The values of the 10 component of the LLlDF structure as used for SNA/DS GDS
variables are shown below: 1

Structure Name

C001*

In DIA, MU PREFIX: in OS, Prefix within DIST_MU or within REMU (type
FS1)
,

C101*

in DIA, MU CMD NO REPLY ACKNOWLEDGE: in OS, Command within
REMU (type FS1)

C105

Command, DIST_MU

C322*

in DIA, MU OPERAND IMM DATA EXCEPTION-CODE: in OS, Exception
Code, within REMU (type FS1)

C32S*

in DIA, MU OPERAND IMM DATA DATA CORRELATION: in OS, Correlation, within REMU (type FS1)

C320*

in DIA, MU OPERAND IMM DATA USER-DATA; in OS, Agent Object
within DIST_MU

C330*

in DIA, MU OPERAND IMM DATA STATUS-INFORMATION: in OS, Distribution General Options, within DIST_MU

C340*

in DIA, MU OPERAND IMM DATA DISTRIBUTION-IDENTIFIER: in OS,
Distribution Identifier, within DIST_MU

C343*

in DIA, MU OPERAND IMM DATA GENERAL-ROUTING-DATA; in OS,
Report-To Options within DIST_MU

C345*

in DIA, MU OPERAND IMM DATA REPLY DATA; in OS, Reply Data,
within REMU (type FS1)

C350

Beginning of Destination Operand Lists, of the Specific Report Lists,
within DIST_MU

C351

End of Destination Operands Lists, of the Specific Report Lists, within
DIST_MU

C352

Routing Group Name (RGN) of Destination Operands, within DIST_MU

C353

Routing Element Name (REN) of REN List, within DIST_MU

C354

Distribution Group Name (DGN) of DGN List, within DIST_MU

C355

Distribution Element Name (DEN) of DEN List, within DIST_MU

C356

Report Type, within DIST_MU

C357

Report Contents, within DIST_MU

C360

Report-To Address, within DIST_MU

C361

Receiving DSU, within DIST_MU or within REMU (type FS1)

C90S

Server Object, within DIST_MU

C90A

Server Prefix, within DIST_MU

The asterisk following the 10 indicates that that identifier is used by both OIA (Document Interchange Architecture) and 05.
Chapter 13. sNA/Oistribution Services (05)

13-73

13-74

SNA Formats

CF01*

in DIA, MU SUFFIX NORMAL-TERMINATION; in OS, Suffix within
DIST_MU or within REMU (type FS1)

CF02*

in DIA, MU SUFFIX ABNORMAL-TERMINATION; in OS, SEMU (type FS1)

Terminology Mappings
Figure 13-16 (Page 1 of 3). Terminology Mappings
FS2 TERMINOLOGY

Current FS1 TERMINOLOGY

Old FS1 TERMINOLOGY

Dist_Transport_MU
Transport_Prefix
Hop_Count

Dist_MU (type Transport)
Prefix
Hop_Count

DistJU (type Data)
Prefix
Dist_Dest_Hops

MUJD
Transport_Command
Dist_Flags
Service_Parms
Server_ObLByte_Count
Origin_Agent
Server
Origin_DSU
Origin_RGN
Origin_REN
Origin_User
Origin_DGN
Origin_DEN
Seqno_DTM
Supplemental_DistJnfo1
Agent_Carrel
Report-To_DSU
Report-To_RGN
Report-To_REN
Report-To_User
Report-TO_DGN
Report-To_DEN
Report_Servic'e_Parms
Report-To_Agent
Dest_Agent
Unrecognized_Reserve
Dest_List
Dest
Dest_DSU
Dest_RGN
Dest_REN
Dest_User
Dest_DGN
Dest_DEN
Agent_Object
Server_Object
Supplemental_DistJnfo2
DS_Suffix
Dist Report MU

Dist_Command
Dist_Flags (FS1)
Service_Parms
Server_ObLByte_Count
Origin_Agent
Server

Dist_CMD
Dist_Flags
DSL
Data_Size
Dest_TPN
Server_Name

Origin_RGN
Origin_REN

Orig_RGN
Orig_REN

Origin_DGN
Origin_DEN
Origin_Seq no, Origin_DTM

Orig_DGN
Orig_DEN
Orig_Seqno, Orig_DTM

Agent_Carrel

Orig_Correl

Report-To_RGN
Report-To_REN

Fdbk_RGN
Fdbk_REN

Report-To_DGN
Report-To_DEN
Report_Service_Parms
Report-To_Agent

Fdbk_DGN
Fdbk_DEN
Fdbk_DSL
Fdbk_TPN

Destination_Operands

Dest_RGN
Dest_REN

Dest_DGN
Dest_DEN
Agent_Object
Server_Object

Dest_DGN
Dest_DEN
Dest_Appl_Parms
Distrib_Object_Data

DS_Suffix
Dist MU (type Report)

Suffix
Dist IU (type Status)

Chapter 13, SNA/Oistribution Services (OS)

13-75

Figure 13-16 (Page 2 of 3). Terminology Mappings
FS2 TERMINOLOGY

Current FS1 TERMINOLOGY

Old FS1 TERMINOLOGY

Report_Prefix
Report_Command
Reporting_DSU
Reporting_RGN
Reporting_REN
Report_DiM
Report-To_DSU_User
ReportJnformation
Reported-On_Origin_DSU
Reported-On_Origin_RGN
Reported-On_Origin_REN
Reported-On_ Origin_User
Reported-On_Origin_DGN
Reported-On_Origin_DEN
Reported-On_Seqno_DTM

Reported-On_Supp_DistJnfo1
Reported-On_Supp_DistJnfo2
Reported-On _Ag ent_Carrel
Reported-On_Dest_Agent
SNA_Condition_Report
SNA_Report_Code
Structure_Report
Stru ctu re _State
Structure_Contents
Parent_Spec
ParentJD_Or_T
Parent_Class
Parent_Position
ParentJnstance
Structure_Spec
StructureJD_Or_T
Structure_Class
Structure_Position
StructureJnstance
Structure_Segment_Num
Structure_Byte_Offset
Sibling_List
Reported-On_Dest_List
Reported-On_Dest_Pfx
Reported-On_Dest
Reported-On_Dest_DSU
Reported-On_Dest_RGN
Reported-On_Dest_REN
Reported-On Dest User

13-76

SNA Formats

Reported-On_Origi n.:.,.DGN
Reported-On_Origi n_DEN
Reported-On_Seqno,
Reported-On_DTM

Orig_DGN
Orig_DEN
Orig_Seqno, Orig_DTM

Reported-On_Agent_ Carrel

Orig_Carrel

Specific_Report

Specific_Status

Figure 13·16 (Page 3 of 3). Terminology Mappings

FS2 TERMINOLOGY

Current FS1 TERMINOLOGY

Old FS1 TERMINOLOGY

Reported-On_Dest_DGN
Reported-On_Dest_DEN
Reported-On_Dest_Sf><
Supplemental_Report
Dist_Continuation_MU
Conti nuation _Prefix
Restartlng_Byte_Position
Sender_Exception_MU
Receiver_Exception_MU
Receiver_Exception_Com mand
Sender_Retry_Action
Receiving_DSU
Receiving_RGN
Receiving_REN
Completion_ Query_MU
Completion_Report_MU
Indicator_Flags
Last_Structure_Received
Last_Byte _Received
Purge_Report_MU
Reset_Request_MU
Reset_DTM
Reset Accepted MU

Reported-On_Dest_DGN
Reported-On_Dest_DEN

Stat_DGN
Stat_DEN

Sender_Exception_MU
Receiver_Exception_MU
Receiver_Exception_Command

Suffix (type 2)
AckJU
Ack_Cmd

Receivin9_DSU
Receivin9_RGN
Receivin9_REN

Rcv_DSUN
Rcv_DSUN_RGN
Rcv_DSUN_REN

Chapter 13. SNA/Oistribution Services (OS)

13-77

13-78

SNA Formats

.•.

.,.~

...." ,.. ,r "";..z;:

Chapter 14. GDS Variables for General Use
The following chart indicates (using an "X") each GDS variable code point (with
X '12') used by LU 6.2.
first byte

First hexadecimal digit
~cond hexadecimal digit

1 X

2
3

5
6

8
9

A X
B
C

Figure 14-1. LU Type 6.2 GDS Variable Code Points

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'12F5'
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
PI P Data (see Note 2)
Application Data

Chapter 14. GDS Variables for General Use

14-1

Notes:
1. See Chapter 12, "GDS Variables for SNA Service Transaction Programs
(STPs)" for the formats and meanings of these GDS variables.
2. See Chapter 10, "Function Management (FM) Headers" for the formats and
meanings of these GDS variables.

Application Data (X '12FF ') GDS Variable
The Application Data GDS variable, 10 X '12FF I, 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 '12FF I variables.

Null Data (X'12F1 ') GDS Variable
The Null Data GDS variable, 10 X '12F1 1 , 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, 10 X'12F2 1 , 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 that follows it or to carry FM header data for a mapped conversation
transaction.

Map Name (X' 12F3 ') GDS Variable
The Map Name GDS variable, 10 X'12F3 I, is followed by a 0- to 64-byte map
name.

Error Data (X'12F4') GDS Variable
The Error Data GDS variable, 10 X'12F4 1 , is used to convey information about
mapping errors. It is sent using the SEND_DATA verb following a SEND_ERROR
verb. Its format is:
Error Data (X'12F4') GDS Variable
Byte

Bit

Content

0-1

Length (n + 1), in binary, of Error Data GDS variable, including this Length field

2-3

GDS 10: X ' 12F4 1

4-7

Error code:

X100010000 1
X100030001 1

X100030002 I

Invalid GDS 10: The mapped conversation verb component
encountered a GDS 10 that it did not recognize.
Map Not Found: The specified map was not available at the
target, or access to the referenced map could not be completed.
Map Execution Failure: The map program was not able to
process the data stream.

Length (n-8), in binary, of error parameter

9- n

Error parameter: for a mapping failure, the map name carried in the GDS variable for which the error occurred; for an invalid GDS 10, the 2-byte GDS 10 that
was not recognized

14-2

SNA Formats

Error Leg (X '12E1') GDS Variable
The Error Log GDS variable, ID X '12E1', 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:
Error Log (X' 12E1 ') GOS Variable
Byte

Bit

Content

0-1

Length (n + 1). in binary, of Error Log GDS variable, including this Length field

2-3

GDS ID: X'12E1'

4-m

Product Set ID

4-5

Length, in binary, of Product Set ID, including this Length field (values 2 to
32,767 are val id)
Note: The Length field is always present; a value of 2 indicates no Product Set
ID subvector follows.

6-m

Proouct Set ID (X '10') subvector (format described in Chapter 8, "Common
Fields")

m+1-n

Message Text

m+1-m+2

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.

m+3-n

Message text data: implementation-specific data

Chapter 14. GDS Variables for General Use

14-3

14·4

SNA Formats

Chapter 15. SNA/File Services (FS)
This appendix contains the format descriptions for the SNA/FS data streams.
The format descriptions are comprised of two parts, header description tables
and structure descriptions. A header description table contains the header
information for each structure. A structure description contains a prose
description of the structure, bit-level representations, and any presence rules or
length restrictions associated with a particular structure.

Encoding Rules and Representations
The definition of SNA/FS requires a byte-accurate description of the formats
that must be understood by all SNA/FS-capable agents and servers. The
SNA/FS formats are described in terms of encoded fields referred to as "structures" and the hierarchical relationship between these structures. In this
appendix, the header description tables show each structure and its header.
Elsewhere in this book, the header length is assumed not to be part of the
overall structure length (e.g., SNA_report_code).

Structure Classifications
Fields and groupings of.fields are known as structures. They are categorized in
terms of their hierarchical position ("atomic," "child," or "parent"), the method
by which their beginning and endings are determined, (length-bounded, delimited, or implied) and which kind of header is used to identify them (LT or LLlD).
Only certain combinations of characteristics are possible.

Length-bounded Structures
Length-bounded structures consist of a header and usually some following
information. A header may be either two bytes in length, referred to as an "LT"
(length and type), or four bytes in length, referred to as an "LLlD" (length and
GDS code point). In either case, the length byte(s) include the length of the
header itself and the following information, if any.
I

Parent and Child Structures
Structures can contain other structures within them. The containing structure is
known as a parent structure and the contained structures are known as children. These terms are relative, since a non-atomic child structure itself contains other structures and is a parent to them. Children of the same parent are
siblings of each other. Parent structures may be length-bounded, delimited, or
implied; and may be identified by LTs or LLiDs.

Chapter 15. SNA/File Services (FS)

15-1

Delimited Parent Structures
Sometimes it is convenient to define a group of related structures as existing
within a parent structure without having that parent structure appear as a
length-bounded structure in the message. The beginning and end of the parent
are defined by its first and last children. These children are known as delimiters, the first child is the prefix delimiter and the last is the suffix delimiter.
Delimiter children are length-bounded and must be present. They may be nUll,
that is, with an LT of length = 2 or an LLiD of length =4. When the children's
headers are LTs, the parent is classified as a delimited LT structure. When
they are LLlDs, the parent is a delimited LLiD structure.

Implied Parent Structures
It is possible to define a set of related structures as children of a parent structure where the existence and boundaries of the parent are implied by the existence and order of certain child structures. This set of children may occur
within the parent structure, either ordered or unordered, until a structure occurs
that is not an element of this Set. This bieak in sequence implies the boundary'
between parent structures. Depending on its children's headers, an implied
parent is classified as either implied LT or implied LLiD.

Segmented Structures
Length-bounded LLiD structures may be either segmentable or nonsegmentable. For segmentable structures, the most significant bit of the LL
bytes indicates whether any particular segment is the last (bit is equal to 0) or
not last (bit is equal to 1) segment of the structure. The 10 bytes of the
segmentable structure are present on the first segment only.

Unrecognized Children
Future enhancements to the formats might add structures that will not be recognized by implementations of the current format definitions. The current format
must specify for each parent whether or not unrecognized child structures are
allowed. If they are allowed, the definition must specify how long they might
be. When unrecognized structures are found where they are allowed, they
must be passed through without change at intermediate locations and gracefully ignored at final destinations. Unrecognized structures are identified by
either LT or LLiD headers, being of the same type as their siblings.

15-2

SNA Formats

Structure Name
The first column of the header description table identifies SNA/FS structures, by
name, and illustrates their hierarchical relationship by indentation of the
column entries. The order of the structure entries in the table represents,
unless specified otherwise, the order in which the structures appear in the
SNAIFS datastream.

Structure Reference (5truct Ref)
As header information and primary syntax are described in the header
description of a particular table, the semantics, bit representations, presence
rules, and other characteristics are described formally in the structure
description. This column contains a reference page number to where this
structure information is found.

Structure Class (5truct Class)
Structures are classified as either length-bounded LLiOs (10), length-bounded
LTs (T), delimited LLiOs (Oel-IO). delimited LTs (Oel-T), implied LLiOs (Imp-IO).
or implied LTs (Imp-T).
A structure classified as delimited must contain at least two required, lengthbounded children that act as the prefix (pfx) and suffix (sfx) of the delimited
structure. The" /pfx" notation indicates· the length-bounded child structure that
serves as the prefix for its parent delimited structure. The "/sfx" notation indicates the length-bounded structure that serves as the suffix for its parent delimited structure.
A structure classified as implied uses an identified child to identify the beginning of a sequence of children. The "/idc" notation indicates the lengthbounded structure that serves as an identified child of its parent implied
structure.
The "/seg" notation indicates that segmentation is allowed.

IDIT
This column contains the 10 or T value within the header, in hexadecimal. To
indicate that a delimited structure is identified by its prefix, the notation "pfx" is
used. To indicate that an implied structure is identified by one of its children,
the notation "idc," for identified child, is used.

Chapter 15. SNA/File Services (FS)

15-3

Length
This column describes the length verification that would be appropriate at presentation services time. The range of length values specifies the minimum and
maximum lengths of structures which an implementation is required to receive.
For structures that allow unrecognized children, the maximum length value
accommodates the possibility of these yet-to-be-defined structures. On the
sending side, the maximum length value for a particular structure may be
determined by subtracting the unrecognized reserve, if unrecognized children
are allowed, from the maximum length.
Note: An asterisk denotes length restrictions for a particular structure. Length
restrictions are detailed in the corresponding structure description.

Occurrences
Multiple occurrences of SNA/FS structures mayor may not be permitted. A
value of"1 - < some number>" in this column indicates the allowed range of
occurrences of the corresponding structure. A value of "~1" indicates that
there is no architecturally defined maximum. A value of "1" in this column indicates that only a single instance of the corresponding structure is appropriate.
A value of"O - 1" indicates that an instance of the corresponding structure is
optional.
Note: An asterisk denotes presence rules for a particular structure. Presence
rules are detailed in the cOiiesponding stiuctuie deSCiiption.

Children
Unrecognized Children Allowed (Unrec): An entry of "Y" in the "Unrec" column
indicates that the corresponding structure tolerates unrecognized child structures. An entry of "N" indicates that the particular structure tolerates only the
architecturally-defined child structures. An entry of "-" indicates that unrecognized children are not applicable to the particular structure. By definition,
atomic structures do not contain children, recognized or not.
Order: A value of "Y" in this column indicates that children are ordered, a
value of "N" indicates that children are unordered, and a value of "-" indicates
that no children are present.
Note: If a structure is atomic, this column is not applicable.
Number (Num): Each parent structure contains a certain number of different
children. This column specifies the minimum and maximum number of different
children for a particular parent structure. The maximum number also accounts
for unrecognized children, if they are allowed within the parent structure. This
column does not account for multiple occurrences of a particular child structure
within the parent structure. The number of occurrences of each child is indicated in the "Occurrences" column.
Subtable: Sometimes the need to divide large tables into subtables becomes
apparent, particularly when common children appear frequently within different
header description tables. This column contains a reference page number to
where these common children are described.

15-4

SNA Formats

SNA/FS Usage of SNA/DS Encodings
SNA/FS requires the services of SNA/DS implementations to transport SNA/FS
encodings between SNAIFS-capable DSUs. The SNA/DS architecture is able to
transport SNA/FS-defined encodings within three different SNA/DS-defined
envelopes. The SNA/DS agent_correl envelope is used by SNA/FS to identify
the SNAIFS unit-of-work. All SNA/DS distributions relating to one particular
SNA/FS unit-of-work will carry the same agent_correl envelope. The SNA/DS
agent_object envelope is used by SNA/FS to carry agent commands targeted
for SNAIFS-capable agents. The SNA/DS server_object is used by SNA/FS to
carry server instructions and data objects targeted for SNA/FS servers. An
SNAIFS unit-of-work may require either or both of these two types of objects.

SNA/FSRequests and Reports
An SNA/FS unit-of-work may result in multiple SNA/DS distributions. These
SNA/DS distributions can carry either an SNA/FS request or anSNA/FS report.
An SNA/FS request solicits SNA/FS services from agents and/or servers at
other DSUs. An SNA/FS report describes the relative success of the SNA/FS
agent/server in performing a requested function. Since the distinction is significant from an encoding perspective, SNA/FS requests and SNA/FS reports are
described in separate header description tables.

Chapter 15. SNA/File Services (FS)

15-5

Header Description Tables for SNA/FS Encodings
Unit of Work Correlator
Figure 15-1. The SNA/FS Use of the SNA/DS Agent_Correl.
Children
Structure Name

Agent_Unit_oCWork

Struct
Ref Pg

Struct
Class

IOIT

Length

Occur·
rencel

15·12

1549

27·128

Unrec

Order

Num

Sub
Table
Page

2·8

15-12

8·22

U_oCW_Requester_RGN

15·12

3·10

U_oCW_Requester_REN

15-12

3·10

15·12

8·22

0·1

U_oCW_Requester_DGN

15·13

3-10

15-13

3-10

U_of_W_Requester_DEN
U_oCW_Requester_Agent

15-13

3·10

0-1*

U_oCW_Seqno_DTM

15-13

15-17

Unrecognized_Reserve

15-15

2·53

U_oCW_Requester_DSU

U_of_W_Requester_User

Note:

'" Refer to the structure description for Pii:S6iiC6 rU!6(s).

SNA/FS Agent Request
Figure 15-2. The SNA/FS Use of the SNA/DS Agent_Object for Agent Requests.
Children
Structure Name

FS_Agent_Request

IOIT

Length

Occur·
rencel

Unrec

Order

Num

Sub
Table
Page

1·2

1530

9-13321

15-15

1546

15-15

1547

7-13312

0·1

1-15

Source_Reporting_Action

15-16

0-1*

Target_Agent

15-16

3-10

0·1*

Target_Reporting_Action

15-16

0-1*

Report·To_Agent

15-17

3-10

0-1*

Report-To_DSU

Command_Parms

15-17

8-22

0·1*

Report-To_RGN

15-18

3-10

15·18

3-10

Report-To_REN

15-18

8-22

0·1

Report-To_DGN

15·18

3-10

15·18

3-10

15-15

2-13238

Report-To_DEN

Report-To_User

Unrecognized_Reserve
Note:

15-15

Struct
Class

Command

15-6

Struct
Ref Pg

* Refer to the structure description for presence rule(s)

SNA Formats

SNA/FS Server Request
Figure 15-3. The SNA/FS Use of the SNA/DS Server_Object for Server Requests.
Children
Structuro Nama

FS_Server_Request
FS_Server_RequesCPreflx

Struct
Ref Pg

Struct
Class

Length

IOIT

Occurrenccs

Unrcc

Order

Num

Sub
Tabla
Page

15-19

Del-ID

pfx

~28

3-11

15-19

ID/pfx

1531

8·19

1·3

Decoder_Instruction

15·19

4·5

0·1·

15·19

4·5

0·1·

TargeUnstruction

15·19

4·5

0·1·

SourceJ nstruction

15·20

Del·ID

pfx

~16

3·5

Group_Prefix

15·20

ID/pfx

1533

Supplemental_FSJnfol

15·21

1534

4·1024

0·1

1·9

15·15

2-1020

15·21

1535

8·32767

0·1

Data_Object_Group

Unrecognlzed_Roserve
Supplemental_FS_lnfo2

Suppiemental_FSJnf03

15·21

153C

9·283

0·1

Supplemental_FSJnfo4

15·21

1550

12·2048

0-1

Unrecognized_Reservo

15·15

4·30432

15·21

Del·IO

pfx

~18

O_O_Prcfix

15·21

ID/prn

153G

0_0_Acceptance

15·21

1537

10·1024

1·9

15·21

Data_Object

3·19

15·15

2·1014

D_O_Global_Name

15·21

1538

9·283

1·7

Supplemontal]S_lnf05

15·21

1539

12·2048

0·1

D_O_Allocation_lnfo

15·21

153F

14·1024

0·1·

1-7

O_O_Class
Unrecognized_Roservo

D_O_Contents

15·22

ID/seg

1541

0·1·

Unrecognized_Reserve

15·15

4·32767

D_O_Suffix

15·22

iO/sfx

1542

Group_Suffix

15·22

ID/sfx

1543

Unrecognized_Reserve

15·15

4·32767

FS_Suffix

15·22

ID/sfx

154C

Note:

1·15

15·9

• Refer to the structure description for presence rule(s)

Chapter 15. SNA/File Services (FS)

15-7

SNA/FS Agent Report
Figure 15-4. The SNA/FS Use of the SNA/OS Agent_Object for Agent Reports.
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Sub
Table
Page

2-3

15-22

154A

14-32763

Command

15-15

1546

SNA_Conditlon_Report

15-28

1532

10-32749

0-1·

FS_Action_Summary

15-22

1548

FS_Agent_Report

Note:

1-10

15-11

Sub
Table

.. Refer to the structure descri ptlon for presence rule(s)

SNA/FS Server Report
Figure 15-5. The SNA/FS Use of the SNA/OS Server_Object for Server Reports.
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

15-23

Oel-IO

pfx

~22

3-4

FS_Server_Report_Prefix

15-23

10/pfx

1548

8-9

OecodeU nstructi on

FS_Server_Report

15-19

4-5

SNA_Condition_Report

15-28

10/seg

1532

10-32749

0-1·

1-10

15-11

Oata_Obj ect_Group

15-20

Oel-IO

pfx

~16

0-1·

3-4

Group_Prefix

15-20

10/pfx

1533

Supplemental_FSJnf02

15-21

1535

8-32767

0-1

1-7

15-21

153C

9-360

0-1

Supplemental_FS_lnf04

15-21

1550

9-2045

0-1

15-15

4-30358

Unrecognized_Reserve

15-21

Oel-IO

pfx

O_O_Preflx

15-21

10/pfx

1536

Supplemental_FS_lnf03

Data_Object

O_O_Global_Name

15-21

1538

9-360

1-8

15-21

1539

9-2045

0-1

Unrecognized_Reserve

15-15

4-30354

15-22

10/sfX

1542

15-22

10/sfx

1543

O_O_Suffix

15-22

10/sfX

154C

FS_Suffix

15-8

Supplemental_FS_'nf05

G_Suffix

Note:

2-13

• Refer to the structure description for presence rule(s)

SNA Formats

15-9

Subtables
Global Names
Figure 15-6. Subtable Encoding of the SNA/FS Global Name.
Children
Structuro Nama

Struct
Rof Pg

Slruct
Class

IOIT

Lenglh

Occurrences

Unrec

Order

Num

Sub
Table
Page

Global_Names
Token_Attri butes

15·23

3·12

0·1*

To_8a]etched_Name

15·24

5·77"

0·1"

Fetchl ng_Match_Flags

15·24

3·12

0·1"

To_8e_Stored_Name

15·25

5·77*

0·1*

1·10

15·10

TO_8e_Deleted_Name

15·25

5·77"

0·1"

1·10

15·10

1·10

15·10

Del etl ng_Match_FI ag s

15·26

3·12

0·1"

Supplemental_FSJnf06

15·21

3·12

0·1*

Fetched_Name

15·26

5·77"

0·1"

1·10

15·10

Stored_Name

15·26

5·77"

0·1"

1·10

15·10

Deleted_Name

15·27

5·77"

0·1"

1·10

15·10

Roportcd·On_Nilmo

15·27

5·77"

0·1"

1·10

15·10

Noles:

1. The to_be_fetched_name and a fetched_name are mutually exclusive.
2.
3.
4.
5.

The to_be_de/eted_name and a deleted_name are mutually exclusive.
The to_be_stored_name and a stored_name are mutually exclusive.
This subtable Is referenced by the FS_serverJequest and the FS_serverJeport.
" Refer to the structure description for presence rule(s) and length restriction.

Allocation Information
Figure 15-7. Subtable Encoding of the Allocation Information.
Children
Slruclure Name

Slrucl
Ref Pg

Slrucl
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Sub
Table
Page

Allocation_Info
Transfer_Size

15·27

Unrecognized_Reserve

15·15

2·1010

Note:

This subtable is referenced by the FS_serverJequest.

Chapter 15. SNA/File Services (FS)

15-9

Tokens
Figure 15-8. Subtable Encoding of the Global Name Tokens.
Children
Structure Name

Struct
Ref Pg

Struct
Class

IOIT

Length

Occurrences

Unrec

Order

Num

Sub
Table
Page

Tokens

Fourlh_Token

15·28

3-18

0-1

Fifth_Token

15·28

3-18

0-1

Sixth_Token

15·28

3-18

0-1

Seventh_Token

15·28

3-18

0-1

Eighth_Token

15·28

3-18

0-1

Ninth_Token

15·28

3-18

0-1

Tenth_Token

15·28

3-18

0-1

First_Token

15·27

3-18

Second_Token

15·27

3-18

0-1

Third_Token

15·28

3-18

0-1

Note:

15-10

This subtable is referenced by the global_names table.

SNA Formats

SNA Condition Report
Figure 15-9. The SNA/FS Use of the SNA_Condition_Report
Children
Struct
Ref Pg

Structure Name

Struct
Clall

101T

Length

Occurrences

Unrec

Order

Num

Sub
Tablo

1-10

SNA_Condltlon_Roport

15-28

1532

10-32749

0-1"

SNA_Report_Code

15-28

Structure_Report

15-29

14-255

0-10"

Structure_State

15-29

Structure_Contents

15-29

3-100

0-1"

Parent_Spec

15-29

5-17

0-7

1-4

2-10

ParenUo_Or_T

15-30

3-4

Parent_Class

15-30

0-1"

Parent_Position

15-30

0-1

Parent_Instance

15-30

0-1

15-31

5-17

0-1"

1-4

StructureJo_Or_T

15-31

3-4

0-1"

Structure_Class

15-31

0-1"

15-31

0-1

15-32

0-1

Structure_Spec

Structure_Position
Structure_Instance

Structure_Segment_Number

15-32

0-1"

Structure_8yte_Offset

15-32

0-1

Sibling_List

15-32

3-100

0-1"

Unrecognlzed_Reservo

15-15

2-241

Reported-On_oest_L1 st

15-32

oel-T

pfx

12-11268

0-1"

Reported-On_oest_Prefix

15-32

T/pfx

Reported-On_oest

15-33

ImplT

idc

8-5654

1-2

15-33

TIlde

2-22

0-2

Reported-On_oest_RGN

15-33

3-10

0-1'"

Reported-On_oest_REN

15-33

3-10

0-1"

Reported-On_oest_oSU

Reported-On_oest_U ser

15-33

8-22

15-33

3-10

15-34

3-10

Reported-On_oest_Suffix

15-34

Reported-On_Token_Stri ng

15-34

5-182

0-10'"

Supplemental_Report

15-34

3-255

0-5'"

Unrecognized_Reserve

15-15

2-15826

Reported-On_oest_oGN
Reported-On_oest_oEN

Note:

1-10

15-10

'" Refer to the structure description for presence rule(s) and length restriction.

Chapter 15. SNA/Fi Ie Services (FS)

15-11

Structure Descriptions
Agent_Unit_of_Work - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The agenCuniCof_work, assigned by the requesting agent, provides the basis
to track the progress of a particular defined task. The unit-of-work request is
uniquely identified by the combination of u_o'-w_requester_DSU,
u_of_w_requester_user, u_o'-w_requester_agent, and u_of_w_sequence
number/date-time.
In SNA/FS, the unit of work identifies one or more generated SNA/DS distributions as belonging to the same SNAIFS defined task.

U_of_W_Requester_DSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

. Description:

The unit_o'-work_requester_DSU is the name of the DSU at which the unit-ofwork was requested.

U_of_W_Requester_RGN - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The uniCo'-work_requester_RGN is the first part of the name of the DSU at
which the unit-of-woik was isquested. This is typically, but not necessarily,
the network ID.

Format:

Character string

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

U_of_W_Requester_REN - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The unit_o'-work_requester_REN is the second part of the name of the DSU at
which the unit-of-work was requested. This is typically, but not necessarily,
the LU name.

Format:

Character string

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

U_of_W_Requester_User - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

15-12

SNA Formats

The unit_o'-work_requester_user is the user name of the originator of the unitof-work request.

Description:

The uniCo'-work_requester_DGN is the first part of the user name of the unitof-work originator.

Format:

Character string

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

U_of_W_Requester_DEN - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The unit_o'-work_requester_DEN is the second part of the user name of the
unit-of-work originator.

Format:

Character string

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

U_of_Y/_Requester_Agent - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The unit_o'-work_requester_agent identifies the transaction program that originated the unit-of-work request.

Presence Rule:

When the unit_o'-work_requester_agent is absent, the origin_agent specified
in the SNA/DS distribution is the default.

Format:

Character string, except for first byte

CGCSGID:

01134-00500

(Character Set AR)

String Convention:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ranges in value from X'OO to X'3F'. When the first
byte ranges in value from X'41' to X'FF', the transaction
program is not SNA-registered. X'40' is not a valid firstbyte value.

U_oCW_Seqno_DTM ------------------------------------------------------~

Description:

The sequence number is the number assigned to the unit-of-work request by
the SNA/FS originating agent. The value ranges from 1 to (2 31 )-1. The date of
the unit-of-work request is assigned by the u_of_w_requester_agent; the time
of the unit-of-work request is assigned by the u_of_w_requester_DSU. The
offset from GMT for local time is included.

Format:

Byte string

Chapter 15. SNA/File Services (FS)

15-13

Byte

Contents

0-1
2-5

LT header
Sequence number
Signed binary integer limited to (2 31 )-1.

6-7
8
9

DATE
Year. in binary (e.g .• year 1989 is encoded as X'07C5')
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)

10
11
12
13

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)

15
16

GMT FLAG
Indicates that specified TIME is GMT and identifies whether offsets from GMT are
required to calculate local time. (Equivalent EBCDIC characters are shown in parentheses.)
X'E9' (Z)
no offset required
X'4E' (+)
add requin~d offset to GMT to get local time
X'60' (-)
subtract required offset from GMT to get local time
OFFSET
Hour offset from GMT in binary. occurs when GMT_flag =1= Z (values from 0 to 23 are
valid)
Minute offset from GMT in binary. occurs when GMT_flag =1= Z (values from 0 to 59 are
valid)
Examples
A 9-byte date/time encoding is a date/time followed immediately by an EBCDIC 'Z', and is
considered to be GMT. Thus, 12:00 GMT on 2 January 1988 would be

. X'e7C4eHl2eceeeeeeE9

yyyymmddhhmmsshhZ
An 11-byte date/time encoding is a date/time followed immediately by an EBCDIC' +' or
'-' and two one-byte binary numbers, and is considered to be GMT and the offset from
GMT to local time. Thus, 7:00 a.m. on 2 January 1988 in New York would be 12:00 GMT 5 hours, or

X'e7C4ele2eCeeeeee6eeSee '
yyyymmddhhmmsshh- hhmm

15-14

SNA Formats

Unrecognized_Reserve - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
The unrecognized_reserve is the number of bytes reserved for unrecognized
structures. An unrecognized structure occurs within its parent structure. The
number of unrecognized structures allowable for a particular parent structure
is limited by the number of children allowable for that parent structure.

Description:

SNAIFS servers pass unrecognized_reserve structures through unchanged in
the outgoing server_object.
Undefined byte string

Format.:

FS_Agent_Request ------------------------------------------------~
The FS_agent_request contains the control information that describes the
SNAIFS agent action to be performed.

Descri ption:

Command - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The command specifies the type of SNA/FS request or SNA/FS reporting
action.

Format:

Byte string

Byte

Content

0-3
4

X'10'

LLID header
REPORT_FS_ACTION

X'11'

REPORTING_FS_ACTION

X'12'

TRANSFER_TO_REQUESTER

Notes:
1. All other values are reserved.
2. REPORTING_FS_ACTION is valid only in reporting flows, while the other values are valid only in
requesting flows.

Command_Parms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The commandyarameters contain and qualify the control information for the
command.

Chapter 15. SNA/File Services (FS)

15-15

Source_Reportlng_Actlon - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The source_reporling_action describes the type of reporting the source agent
performs.

Presence Rule:

Occurs when the requesting agent requires reports from the source, and the
command is TRANSFER_TO_REQUESTER; otherwise, precluded.

Format:

Byte string

Note:

The reporting action requested of the agent cannot be more demanding than
that requested of the server.

Byte

Contents

0-1

LT header

X'01'

DETAILED

X'10'

SUMMARY_OR_EXCEPTIONS

X'11'

ON LYJF_EXCEPTIONS

Note: All other values are reserved.

Taig6t_Ag~nt ---------------------------------------~

Description:

The target_agent is the transaction program at the target location.

Presence Rule:

Occurs when the target_agent is different from the source agent, and the
command is TRANSFER_TO_REQUESTER; otherwise. precluded. When the
target_agent is absent. the dest_agent specified in the SNA/DS distribution is
the default.

Format:

Character string, except for the first byte

CGCSGID:

01134-00500

(Character Set AR)

String Convention:

Leading, imbedded. and trailing space (X'40') characters
are not allowed.
The first byte of an SNA-registered transaction program
name ranges in value from X'DO to X'3F'. When the first
byte ranges in value from X'41' to X'FF'. the transaction
program is not SNA-registered. X'40' is not a valid firstbyte value.

Target_Reportlng_Actlon - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The targeCreporling"-action describes the type of reporting the target agent
performs.

Presence Rule:

Occurs when the requester requires target reporting. and the command is
REPORT_FS_ACTION or TRANSFER_TO_REQUESTER; otherwise. precluded.

Format:

Byte string

15-16

SNA Formats

Byte

Contents

0-1
2

X'01'

DETAILED

X'10'

SUMMARY_OR_EXCEPTIONS

X'11'

ONLYJF_EXCEPTIONS

LT header

Note: All other values are reserved.

Report-To_Agent ----------------------------------------------------------~
Description:

The report-to_agent is the name of the transaction program to which reports
are to be delivered after the SNA/FS activity has concluded.

Presence Rule:

Occurs when the requester requires reporting to a third-party agent that is different from the requesting agent, and the command is REPORT_FS_ACTION or
TRANSFER_TO_REQUESTER; otherwise, precluded. When the report-to_agent is
absent and reporting is required, the dest_agent specified in the SNA/DS distribution is the default.

Format:

Character string, except for the first byte

CGCSGID:

01134-00500

(Character Set AR)

String Convention:

Report-To_DSU ----------------------------------------------------------~
Description:

The report-to_DSU is the name of the DSU to which the SNA/FS reports are to
be delivered.

Presence Rule:

Occurs when the requester requires reporting and requests the reports be
delivered to a DSU other than the default DSU. When the report-to_DSU is
absent, the report-to_DSU specified in the SNA/DS distribution is the default.
If the report-to_DSU is also absent, the origin_DSU is the default. Typically
the SNA/DS distributions between the source and target locations normally
carry the requesting DSU as the SNA/OS report-to_DSU.

Chapter 15. SNA/File Services (FS)

15-17

Repon-To_RGN

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

Description:

The report-to_RGN is the first part of the DSU name to which the SNA/FS
reports are to be delivered. This is typically, but not necessarily, the network
10.

Format

Character string

Repon-To_REN

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X' 40') characters
are not allowed.

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

Descri ption:

The report-to_REN is the second part of the DSU name to which the SNA/FS
reports are to be delivered. This is typically, but not necessarily, the LU
name.

Format

Character string

Repon-To_User
Descri ption:

Repon-To_DGN

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading. imbedded, and trailing space (X'40') characters
are not allowed.

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

The report-to_user is the name of the user to which the SNA/FS reports are to
be delivered.

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

Descri ption:

The report-to_DGN is the first part of the user name to which the SNA/FS
reports are to be delivered.

Format:

Character string

Repon-To_DEN

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

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

Descri ption:

The report-to_DEN is the second part of the user name to which the SNA/FS
reports are to be delivered.

Format:

Character string

15-18

SNA Formats

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

FS_Seroer_Request ----------------------------------------------------------~

Description:

The FS_server_request describes the action to be performed by the server,
and may also contain object identifiers and object contents.

FS_Server_Request_Prefix ----------------------------------------------------,

Descri ption:

The FS_server_requestyrefix identifies the beginning of the
FS _server_request.

Decoder_Instruction -----------------------------------------------------------.,

Description:

The decoder_instruction describes the server action to be performed by the
decoder-role server at either the source location or report-to location.

Presence Rules:

Occurs when:
• The TRANSFER_TO_REQUESTER agent command and its accompanying server
request flow from the requesting location to the source location.
• The REPORTING_FS_ACTION agent command and its accompanying server
report flow from the target location to the report-to location.

Format:

Bit string

Note:

The values for the decoderjnstruction are described on page 15-20.

Source_Instruction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The source_instruction describes the action to be performed by the sourcerole server at the source location.

Presence Rule:

Occurs when the TRANSFER_TO_REQUESTER agent command and its accompanying server request flow from the requesting location to the source location.

Format:

Bit string

Note:

The values for the source_instruction are described on page 15-20.

Target_Instruction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The target_instruction describes the server action to be performed by the
target-role server at the target location.

Presence Rules:

Occurs when:
• The TRANSFER_TO_REQUESTER agent command and its accompanying server
request flow from the requesting location to the source location.
• A server request containing a data object flows from the source location
to the target location.
• A server request for a deletion flows from the requesting location to the
target location.

Format:

Bit string

Note:

The values for the target_instruction are described on page 15-20.

Chapter 15. SNA/File Services (FS)

15-19

Server Instructions:
Byte

Bit

Contents

Server Role

LT header

0-1

0-3

4-7

0-3

4-7

0-3

4-7

Server instruction:
0001

FETCH

0010

DECODE

0011

CREATE_LOAD_OR_REPLACE

0100

DELETE

0101

REPLACE

0110

CREATE_LOAD

source
decoder
target
target
target
target

Exception action:
0001

ABEND

decode~

0010

BACKOUT

target

source, or target

Reporting action:
0001

DETAILED

0010

SUMMARY_OR_EXCEPTIONS

0011

ONLY-,F_EXCEPTIONS

source or target
decoder, source, or target
source or target

Reserved:
Intention

(see Note 2):

0001

EXECUTING

0011

STORING

0100

NOT APPLICABLE

target
target
decoder, source, or target

Reserved

Notes:
1. All other values are reserved.
2. Byte 4 is optional and may be omitted.

Data_Object_Group - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The data_object_group defines the overall characteristics about the data
object.

Presence Rules:

Required in:
• The FS_server_request.
• The FS_server_report whenever the SNA_condition_report is absent; otherwise, optional.

Group_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

15-20

SNA Formats

The data_object_groupyrefix identifies the beginning of the
data_objecCgroup.

Supplemental_FS_lnfo1-Supplemental_FS_lnfo6 - - - - - - - - - - - - - - - - - - . . . . . . ,

Description:

The supplemental_FS_info1 - supplemental_FS_info6 structures are reserved
for future use.

Data_Object ------------------------------------~

Description:

The data_object is the basic entity managed by SNA/FS.

D_O_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The data_objectyrefix identifies the beginning of the data_object.

D_O_Acceptance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The data_object_acceptance contains information about the contents of the
data object that the SNA/FS server uses to determine whether the server can
honor the request.

D_O_Class - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The data_object_class identifies the class of the data object by means of a
hierarchical structure of codes. The classification and intention information
are used by the server to determine whether or not the request can be
honored.

Format:

Byte string

Note:

Refer to "SNA/FS Data Object Classification Codes" on page 15-35 for the
value descriptions.

D_O_Global_Name

Description:

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

The data_object_global_name is the unique, system-independent identifier for
the data object. The name is assigned according to naming conventions
established by the using architecture. The canonical identifier consists of a
string of tokens, where the leftmost tokens are more significant. A higherorder token identifies the naming authority that issues or manages the values
of the lower-order tokens.

D_O_Allocation_lnfo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The data_object_al/ocation_info provides the target location with space
requirements needed to store the data object.

Presence Rule:

Occurs when data_object_contents is present.

Chapter 15. SNA/File Services (FS)

15-21

D_O_Conten~ ------------------------------------------------------------~

Description:
Presence Rule:

The data_object_contents is the byte contents of the data_object.
Precluded when the decoder_instruction is present or the target_instruction is
DELETE.

Format:

Undefined byte string

D_O_Suffix ------------------------------------------------------------~

Description:

The data_objecCsuffix contains no information and marks the end of the
data_object.

G_Sufflx ------------------------------------------------------------,

Descri ption:

The data_object_group_suffix contains no information and marks the end of
the data_objecCgroup.

~ FS Suffix

I Description:

The FS_suffix contains no information and marks the end of the FS_request or
the FS_report.

FS_Agent_Report ------------------------------------------------------------~

Descri ption:

The FS_agenCreport provides a summary on the relative success of a previous SNA/FS request.

FS_Action_Summary -------------------------------------------------------~

Description:

The FS_action_summary indicates whether the actions requested of the server
were successfully performed.

Format

Bit string

15-22

SNA Formats

Byto

Bit

0-3

Contents
LLiD header

0-1

01
11

ALL_SUCCESSFUL
NONE_SUCCESSFUL

(see Note 2)

2-3

4-5

00
01

6-7

SERVER_ABEND

Reserved

Notes:
1. All other values are reserved.
2. If this value (ALL SUCCESSFUL) is present, all subsequent bits are O.

FS_SeNer_Report ----------------------------------------------------------~
Description:

The FS_server_report provides information on the relative success of one or
more server operations.

FS_SeNer_Report_Prefix ---------------------------------------------,
Descri ption:

The FS_server_report..,prefix identifies the beginning of the FS_server_report.

Token_Attributes -----------------------------------------------------------,
Description:

The token_attributes define for each token in the canonical name how that
token can be used in partial matching or token value generation. These attributes are stored in the SNA/FS catalog.

Presence Rule:
\'-.. -

Occurs when the server instruction is performing a create operation (e.g.,
and the data object is to. be involved in
partial matching or token value generation.

CREArE_LOAD; CREATE_LOAD_OR_REPLACE),

Bit string

Format:

Byte

Contents

0-1
2-11

LT header
Up to 10 different token attributes can be specified.

Chapter 15. SNA/File Services (FS)

15-23

Token Attribute Values
For each token in the token string, there will be a single byte of attribute information, as follows:
Bit

Contents

MUST_MATCH
NEED_NOT_MATCH

NOT_GENERABLE
GENERABLE

Reserved

3-7

00000

UNSPECIFIED TYPE,

00001

NETID

00010

LU-NAME

$16 CHARACTERS

00011

SYSTEM_TYPE

10000

ORDERED,

$16 CHARACTERS

10001

ORDERED,

$16 DECIMAL NUMERICS

10010

ORDERED,

DATE

10011

ORDERED,

TIME

10100

ORDERED,

GOOVOO

Notes:
1. All other values are reserved.
2. The target SNA/FS server is obligated to preserve the attribute characteristic in the catalog at the
target node and to honor subsequent deletion requests based on this characteristic. If all bits in
the catalog entry attribute byte are 0, i.e., MUST_MATCH the corresponding identifier must be exactly
matched for deleting and replacing operations.

To_Be_Fetched_Name ---------------------------------------------------------------------------------------,

Description:

The to_be_fetched_name is the name of the object, at the source location, that
is to be fetched by the SNA/FS server.

Presence Rule:

Occurs in:
• The FS_server_request when an object is to be fetched from the source
location.
• The FS_server_report when the fetch server operation was unsuccessful
or not attempted, and reporting was requested.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Fetchin9_Match_Flags - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The fetching_match_flags govern the partial matching operation at fetch time.

Presence Rule:

Occur when partial matching is required at fetch time.

Format:

Byte string

15-24

SNA Formats

Byte

Contents

0-1
2-11

LT header
For each token in the token string, up to a maximum of 10 tokens, a single byte describes
that token's use in a fetch operation.

Fetching Flag Values
Values
X'OO'

FIND_A_MATCH

X'01'

IGNORE

X'02'

SELECT_HIGHEST

X'03'

SELECT_LOWEST

Note: All other values are reserved.

To_Be_Stored_Name ---------------------------------------------------------------------------------~
Description:

The to_be_stored_name is the name of the object that is to be stored at the
target location. Typically, the source-role server will obtain the name at fetch
time.

Presence Rule:

Occurs in:
• The FS_server_request flow between the source and target locations when
an object is to be stored at the target location. The requester can also
specify parts of a to_be_stored_name; therefore, in this case, -the structure
is present between the requesting and source locations.
• The FS_server_report when the storing operation was unsuccessful or not
attempted, and reporting was requested.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

To_Be_Deleted_Name -------------------------------------------------------------------------------------..,
Description:

The to_be_deleted_name is the name of the object, at the target location, that
is to be deleted by the SNA/FS server.

Presence Rule:

Occurs in:
• The FS_server_request when an object is to be deleted from the target
location.
• The FS_server_report when the delete operation was unsuccessful or not
attempted, and reporting was requested.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Note

For a replace operation, the to_be_deleted name needs to contain only the
tokens that differ from the values in the identifier of the
to_be_stored data objects.
NEED_NOT_MATCH

Chapter 15. SNA/File Services (FS)

15-25

Oeleting_Match_Flags - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The deleting_match_flags govern the matching operation, at the target
location, of the object to be deleted.

Presence Rule:

Occurs when partial matching is required to identify the to_be_deleted object.

Format:

Byte string

Byte

Contents

0-1
2-11

LT header
For each token in the token string, up to a maximum of 10 tokens, a single byte describes
that token's use in a delete operation.

Deleting Flag Values
Values
X'QQ'
X'Q1'

FIND_A_MATCH
IGNORE

X'Q2'

SELECT_HIGHEST

X'Q3'

SELECT_LOWEST

Note: All other values are reserved.

Fetched_Name ------------------------------------------------------------~
Description:

The fetched_name is the name of the object fetched by the SNA/FS server.

Presence Rule:

Occurs only in the FS_server_report when the source agent reports that an
object has been fetched.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Stored_Name --------------------------------------------------------------~
Descri ption:

The stored_name is the name of the object stored by the SNA/FS server.

Presence Rules:

Occurs:
• In the FS_server_report when the target agent reports that an object has
been stored.
• When the request is being used to convey a data object name.

Length Restriction:

15-26

SNA Formats

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Deleted_Name - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The deleted_name is the name of the object deleted by the SNA/FS server.

Presence Rule:

Occurs only in the FS_server_report when the target agent reports that an
object has been deleted.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Reported-On_Name -------------------------------~

Description:

The reported-an_name is the name of the object being reported by the SNA/FS
server. The reported-an_name is used in cases when the state of the object
being reported on cannot be determined.

Presence Rule:

Occurs only in the FS_server_report.

Length Restriction:

The maximum length for the global name is 65-n, where n is the number of
tokens in the name.

Transfer_Size - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The transfer_size is an estimate of the number of bytes in the data_contents.
It can be larger or smaller than the actual size; however, it should be accurate
enough for the target location to use for space decisions.

Format:

Unsigned binary integer (1-origin)

First_Token - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The first_token is the highest level part of the data object name. Its values
are assigned and registered by SNA.

Format:

Character string

CGCSGID:

01134-00500

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

(Character Set AR)

Second_Token - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The second_token is the second-highest level part of the data object name.
The values of this token are assigned by the authority identified by the name
in first_token.

Format:

Character stri ng

Chapter 15. SNA/File Services (FS)

15-27

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading. imbedded. and trailing space (X' 40') characters
are not allowed.

Third_Token-Tenth_Token - - - - - - - - - - - - - - - - - - - - - - - - - - - . . ,

Description:

The third_to_tenth_tokens are the nth highest-level part of the data object
name. The value of the nth token is assigned by the authority identified by the
name in the (n-1)th token.

Format

Character string

CGCSGID:

01134-00500

(Character Set AR)

String Conventions:

Leading, imbedded. and trailing space (X' 40') characters
are not allowed.

SNA_Condition_Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

The SNA_condition_report describes the condition being reported. The condition is always identified by an SNA_report_code.

Description:

Certain conditions can be more fully described by supplementary information.
Conditions pertaining to one or more structures in a format can have the
iocation and contents of each of those structures specified by a
structure_report. Certain conditions arise from inconsistencies among mUltiple portions of the MU. Each portion is described by a separate
structure_report .
Data objects related to the reported-on condition can be specified in a
reported-on_token_string. Other information related to the condition can be
specified in a supp/ementa'-report.
Presence Rule:

Occurs when a reportable condition was detected by the agent/server and the
agent has determined that reporting is appropriate.

SNA_Report_Code -------------------------------------~

Description:

The SNA_report_code is an SNA registered code identifying the condition that
is being reported. Refer to Chapter 9. "Sense Data" on page 9-1 for allowable values and descriptions.

Format:

Byte string

Byte

Content

0-1
2-3
4-5

LT header
Primary report code
Subcode

15-28

SNA Formats

Structure_Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure_report reports on a structure involved in a format-related condition. Depending on the condition, the structure_report may describe a structure that was present in, or absent from, the reported-on MU.
A format condition has its location in the MU pinpointed by a structure_spec
and a list of parent_specs that define a line-of-descent. The line-of-descent
begins with the MU and continues down the parent-child hierarchy to a level
as low as the particular condition warrants. A registered 10 always appears
in a structure_report: if the reported-on structure is not itself a registered 10,
its line-of-descent is traced up to include a registered ancestor.

Presence Rule:

Presence governed by the SNA_report_code.

Structure_State - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_state indicates whether the reported-on structure was present
or absent.

Format:

Hexadecimal code

Byte

Content

0-1

LT header
X'01' STRUCTURE_PRESENT
X'02' STRUCTURE_ABSENT
Note: All other values are reserved.

Structure_Contents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

Presence Rule:

Allowed only when structure_state

Format:

Undefined byte string

= STRUCTURE_PRESENT.

Parent_Spec - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The parent_specification contains the identifier (10 or T) and the class ora
parent structure. For a parent structure that occurs multiple times, the
instance may also be included. The value of the parent_instance identifies the
particular instance. The position of this parent structure within its parent (if
one exists) may also be included. This would typically be done when this
parent structure is an unordered child of its parent.

Chapter 15. SNA/File Services (FS)

15-29

ParentJD_Or_T - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The parent_'D_or_T is the 10 or T value of a parent structure. 10 values are
the registered GDS code points. T values are architecture-specific values relative to the encompassing 10.

Format:

Undefined byte string

Parent_Class - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The parenCclass is the class of a parent structure.

Presence Rule:

If absent, defaults to

Format:

Hexadecimal code

Byte

LENGTH-BOUNDED_LT_STRUCTURE.

Content

0-1
2

LT header
X'01'
LENGTH-BOUNDED_LLlD_STRUCTURE (ID)
X'02'
LENGTH-BOUNDED_LT_STRUCTURE (T) (default)
X'03'
DELIMITED_LLlD_STRUCTURE (DEL-I D)
X'04'
DELIMITED_LT_STRUCTURE (DEL-T)
X'OS'
IMPLlED_LLlD_STRUCTURE (IMP-ID)
X'OB'
IMPLlED_LT_STRUCTURE (IMP-T)
Note: All other values are reserved.

Parent_Position - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

Format:

Signed binary integer

Parent_Instance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The parent_instance is used when a parent structure occurs multiple times.
The value of parent_instance identifies the particular instance within a position.

Format:

Signed binary integer

15-30

SNA Formats

Structure_Spec - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure_specification contains the identifier (ID or T) and the class of a
structure. For a structure that occurs multiple times, the instance may also be
included. The value of the structure_instance identifies the particular
instance. The position of this structure within its parent structure may also be
included. This would typically be done when the parent structure contains
unordered children.

Presence Rule:

Absent only when the structure_class is the default and the sibling_list contains all pertinent ID or T values.

Structure_ID_Or_T - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure_ID_or_T is the 10 or T value of the structure. ID values are the
registered GOS code points. T values are architecture-specific values relative
to the encompassing ID.

Presence Rule:

Required except when sibling_list contains all pertinent ID or T values. In this
case, the structures specified by sibling_list are the structures being reported
on.

Format:

Undefined byte string

Structure_Class - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Description:

The structure_class is the class of the reported-on structure and any siblings
identified in sibling-,ist.

Presence Rule:

If absent, defaults to

Format:

Hexadecimal code

Byte

LENGTH-BOUNDED_LT_STRUCTURE.

Content

LT header
X'01'
LENGTH-BOUNDED_LlID_STRUCTURE (ID)
X'02'
LENGTH-BOUNDED_LT_STRUCTURE (T) (default)
X'03'
DELIMITED_LlID_STRUCTURE (DEL-ID)
X'04'
DELIMITED_LT_STRUCTURE (DEL-T)
X'OS'
IMPlIED_LLlD_STRUCTURE (IMP-ID)
X'06'
IMPlIED_LT_STRUCTURE (IMP-T)
Note: All other values are reserved.

0-1
2

Structure_Position - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The structure..p0sition is either the actual or expected position of this structure within its parent in this particular MU. Multiple consecutive instances of
a repeatable structure share a single position, and can be distinguished by
structure_instance.

Format:

Signed binary integer (1-origin)

Chapter 15. SNA/File Services (FS)

15-31

Structure_Instance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .

Description:

The structure_instahce is used when the structure is one of multiple occurrences of a repeatable structure. The value of structureJnstance identifies
the particular instance within a position.

Format:

Signed binary integer (1-origin)

Structure_Segment_Number - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

The structure_segment_number is the segment of the structure in which the
condition was detected.

Presence Rule:

Occurs when the beginning of structure_contents was not contained in the first
segment of the reported-on structure.

Format:

Signed binary integer (1-origin)

Structure_Byte_Offset

Description:

The structure_byte_offset marks the start of structure_contents within the
reported-on structure. If structure_segment_number is present, this value is
the offset from the start of the indicated segment; otherwise, it is the offset
fiom the beginning of the stiuctUiS.

Format:

Signed binary integer (O-origin)

Sibling_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The sibling_list contains a string of 10 or T values necessary to describe the
detected condition. The structures identified in sibling-,ist are children of the
parent identified in parenCspec and/or siblings of the structure identified in
structure_spec. The class of the sibling structures is the same as
structure_class. The expected position, when applicable, is given by
structure"'position.

Presence Rule:

Presence is governed by the SNA_reporCcode.

Format:

Byte string

Reported-On_Dest_List - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Description:

The reported-on_destination_list contains the portion of the distribution destinations that are being reported on.

Presence Rule:

Presence is governed by the SNA_report_code.

Reported-On_Dest_Prefix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,

Descri ption:

15-32

SNA Formats

The reported-on_destination...prefix is the prefix of the reportedon_destination_'ist.

Reported-On_Dest
Description:

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

The reported-on_destination associates reported-on_dest_users with a
reported-on_desCDSU for those destinations specified in the original distribution request being reported on. For flat destination lists (Le., lists containing
only DSUs and/or DSU-user pairs), there are zero or one user names per DSU
list. For factored destination lists, there can be multiple user names per DSU
list.

Reported-On_Dest_DSU - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
Descri ption:

The reported-on_destination_DSU is one of the original destination DSUs
being reported on.

Reported-On_Dest_RGN

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

Description:

The reported-on_destination_RGN is the first part of the name of one of the
original destination DSUs being reported on. This is typically, but not necessarily, the network 10.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Reported-On_Dest_REN

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

Descri ption:

The reported-on_destination_REN is the second part of the name of one of the
original destination DSUs being reported on. This is typically, but not necessarily, the LU name.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Reported-On_Dest_User
Descri ption:

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

The reported-on_destination_user is the name of one of the original destination users being reported on.

Reported-On_Dest_DGN

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

Description:

The reported-on_destination_DGN is the first part of the name of one of the
original destination users being reported on.

Format:

Character string

Chapter 15. SNA/File Services (FS)

15-33

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Reported-On_Dest_DEN --------------------------------------------~------~

Description:

The reported-on_destination_DEN is the second part of the name of one of the
original destination users being reported on.

Format:

Character string

CGCSGID:

01134-00500 (character set AR)

String Conventions:

Leading, imbedded, and trailing space (X'40') characters
are not allowed.

Reported-On_Dest_Suffix ------------------------------------------------,

Descri ption:

The reported-on_destination_suffix is the suffix of the reportedon_destination_list.

Reported-On_Token_String -----------------------------------------------------,

Description:

The reported-on_token_string contains the FS canonical identifier of a data
object related to the detected condition.

Presence Rule:

Presence is governed by the SNA_rep ort_c 0 de.

Supplemental_Report ---------------------------------------------------,

Description:

The supp/ementaCreport contains other information pertaining to a condition.
The contents of the supp/ementa'-report are governed by the
SNA_report_code.

Presence Rule:

Presence is governed by the SNA_report_code.

15-34

SNA Formats

SNA/FS Data Object Classification Codes

SNAlFS Data Object Classes
Level 1

Level 2

Executable

System
Microcode

Level 3

Level 4

Unspecified
Product Specific

10
10

Fix

Unspecified
Product Specific

10
10

20
20

Suffix_EC

Unspecified
Product Specific

10
10

30
30

Unspecified
Product Specific

10
10

40
40

Unspecified
Product Specific

10
10

50
50

Unspecified
Product Specific

10
10

60
60

00
00
00

Patch
1

Maint_EC
Funct_EC
Feature

Unspecified

Hex Codes

Microcode
Customization

Unspecified
Product Specific

Unspecified
Unspecified

10
10

20
20

Unspecified

Unspecified
Product Specific
Customer Specific

00
00
00

Ex
Ex
Ex
Ex
Ex
Ex

00
Ex
Fx

Code Points Used by SNA/FS
The values of the 10 component of the LLiD structures as used for SNA/FS GDS
variables are shown below:

Structure Name

1530

FS Agent Request

1531

FS Server Request Prefix

1532

SNA Condition Report

1533

Data Object Group Prefix

1534

Supplemental FS Info1

1535

Supplemental FS Info2

1536

Data Object Prefix

1531

Data Object Acceptance

1538

Data Object Global Name

Microcode may be classified as IBM Licensed Internal Code. See "Special Notices" at the beginning of this
document for more information.
Chapter 15. SNA/File Services (FS)

15-35

1539

Supplemental FS Inf05

153C

Supplemental FS Inf03

153F

Data Object Allocation Info

1541

Data Object Contents

1542

Data Object Suffix

1543

Data Object Group Suffix

1546

Command

1547

Command Parms

1548

FS Action Summary

1549

Agent Unit of Work Correlator

154A

FS Agent Report

1548

FS Server Report Prefix

154C

FS Suffix

1550

Supplemental FS Inf04

Transaction Program and Server Names
The following is a list of the SNA/FS-defined server name, the SNA/FS-defined
transaction program name, and the names of other SNA/FS-capable transaction
programs.
Code

Meaning

X'24FOFOFO'

SNA/FS server name

X'23FOFOFO'

SNA/MS change management agent TP name

Global Name Registration
The following is a list of the first identifier tokens that have been registered by
SNA/FS on behalf of SNA/FS-capable agents.

15-36

SNA Formats

First Identifier

Agent

C'MCODE'

SNA/MS change management

C'MCUST'

SNA/MS change management

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 I FO I, X I F1 1, ... , or X I F9 I.
• 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 140 I) characters are used, but no other restrictions
exist on the first character.
Imbedded space (X 140 I) characters are significant.
Trailing space (X 140 I) characters are not significant.
• 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 1411 through X I FE I, with no restriction on the first byte.
• Symbol-string type G (general): a byte string consisting of one or more
bytes within the range XIOOI through XIFFI, with no restriction on the first
byte.

Appendix A. SNA Character Sets and Symbol-String Types

A-1

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-1.
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-1 on page A-3 defines the character sets and encodings for A, AE,
930, USS, 01134-00500, and 00640-00500. The code paints that do not belong to
any of these sets are not shown.

A-2

SNA Formats

Figure
Hex
Coda

A-1 (Page 1 of 3). Character Sets A, AE, 930, USS, 1134, and 640
Graphic

Description

Line Feed

Space

48
4C

Set
A

930

USS

1134

640

X
X

Period

X
X
X

Less Than Sign

(

Left Parenthesis

Plus Sign

Ampersand

Sharp s

Dollar Sign

•

Asterisk

)

Right Parenthesis

;

Semicolon

Minus Sign

Slash

A Circumflex, Capital

A Diaeresis, Capital

A
A
A

A Grave, Capital

A Acute, Capital

A
A

A Tilde, Capital

A Overcircle, Capital

<;:

C Cedilla, Capital

N Tilde, Capital

X
X
X

Comma

Percent Sign

Underline

Greater Than Sign

Question Mark

E Acute, Capital

E
E
E

E Circumflex, Capital

E Diaeresis, Capital

E Grave, Capital

I Acute, Capital

I Circumflex, Capital

i
i

I Diaeresis, Capital

I Grave, Capital

73
74

Colon

Number Sign

At Sign

Apostrophe

a Slash, Capital

a, Small

b, Small

70
7E
7F

X
X

Equal Sign

X
X

Quotation Marks

Appendix A. SNA Character Sets and Symbol-String Types

A-3

Figure

A-1 (Page 2 of 3). Character Sets A, AE, 930, USS, 1134, and 640

Hex
Code

Graphic

Description

Set

c, Small

930

USS

1134

640

p, Small

X
X
X
X
X
X
X
X
X
X
X
X
X
X

q, Small

r, Small

a Underscore, Small

d, Small

e, Small

f, Small

g, Small

h, Small

i, Small

j, Small

k, Small

X
X

I, Small

m, Small

n, Small

Small

o Underscore, Small

AE Dipthong, Capital

Micro, Mu

Small

t, Small

u, Small

v, Small

Small

X
X

x, Small

y, Small

Small

[)

D Stroke, Capital

Y Acute, Capital

Thorn, Capital

A, Capital

B, Capital

C, Capital

D, Capital

E, Capital

X
X
X
X

F, Capital

X
X

G, Capital

H, Capital

I, Capital

J, Capital

K, Capital

L, Capital

M, Capital

A-4

SNA Formats

Figure

Hex
Code

A-1 (Page 3 of 3). Character Sets A, AE, 930, USS, 1134, and 640
Graphic

Set

Description
A

930

USS

1134

640

X
X
X
X
X

N, Capital

0, Capital

P, Capital

Q, Capital

R, Capital

y Diaeresis, Small

S, Capital

T, Capital

U, Capital

X
X

V, Capital

W, Capital

X, Capital

Y, Capital

Z, Capital

ED
EF

0
6
6

o Circumflex, Capital
o Diaeresis, Capital
o Grave, Capital
o Acute, Capital
o Tilde, Capital

Zero

X
X
X
X
X
X
X
X

X
X
X
X
X

Three

X
X
X
X

Four

Five

Six

Seven

Eight

X
X

X
X
X
X
X

One

Two

Nine

U Circumflex, Capital

0
0

U Diaeresis, Capital

U Grave, Capital

U Acute, Capital

Appendix A. SNA Character Sets and Symbol-String Types

A-S

A-6

SNA Formats

Appendix B. GDS ID Description and Assignments
This appendix defines the general data stream (GOS), 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 (STPs),"
Chapter 14, "GDS Variables for General Use," Chapter 5, "Request/Response
Units (RUs)," and Chapter 10, "Function Management (FM) 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.

LENGTH
(LL)

INFDRMAT~~~

IDENTIFIER

••.

(ID)

1.-.-_----'-_ _ _---1..._ _ _ /

Byte

Figure

8-1. 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 LLlD; 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 10001 1 indicates a presentation services header, which is used for
sync point management.
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).
Appendix B. GDS 10 Description and Assignments

B-1

When an LLiO encompasses a string of logical records identified by full LLlOs,
the length of the string, determined by summing the (nested) encompassed LLs,
equals the length definer of the (outer) encompassing LLiO less 4 (this applies
at each level of nesting). If the encompassing LLiO 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 10 less 4 for the initial LLiO and 2 for each
continuing LL.
The 2-byte 10 values, irrespective of the level of nesting at which they occur,
are defined uniquely across all levels of nesting, with the following exception.
The 10 values X I FFOO I through X I FFFF I are used only within an encompassing
LLiO (which is not necessarily the immediate parent structure); their meaning is
defined by the architecture that owns the higher-level 10 and it applies only
within the context of that 10. In other words, 10 values in the X I FF* * I range
are context dependent. All other 10 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. OIA 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.
Figure

B-2

SNA Formats

8-2 (Page 1 of 3). Identifier Registry

GDSID

Structured Field Owner

00**
01**
03**
06**
09**
08**
OC**
00**
OE**

3270
3270
3270
3270
3270
3270
3270
3270
3270

OFOO-OFFF

3270

1010-101F

3270

1030-1034

Print Job Restart

Figure

B-2 (Page 2 of 3). Identifier Registry

GDSID

Structured Field Owner

1100-1104

SNA Character String

1200-12FF

LU 6.2 (APPC)

1300-13FF

SNA/Management Services

1400-140F

3820 Page Printer

1570-158F

SNA/Distribution Services

40**
41**
4A**
48**
4C**

3270
3270
3270
3270
3270

7100-71FF

3250

80**

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-C361

SNA/Distribution Services

C366-C3FF

Document Interchange Architecture

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

C90Q-C97F

Document Interchange Architecture

',-

Appendix B. GDS 10 Description and Assignments

8-3

Figure

8-4

SNA Formats

B-2 (Page 3 of 3). Identifier Registry

GDS I D

Structured Field Owner

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

0820-0821

AS/400 (5250)

D930-D95F

AS/400 (5250)

E100-E10F

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

E700-E70F

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

EFFF

IBM Token-Ring Network PC Adapter

FOOO-FEFF

Non-IBM Reserved Block

FFOO-FFFF

Context-Dependent Block

Appendix C. lisi oi Abbreviaiions and Symbols
A
A

ACT

address (SOLC)
active, activate

B
B'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
(e)

CCA
CCITT
CD

COl
CORM
CEB
CEBI
CICSNS
CMI
CNOS
CaNT

cos
CP
CPI

CRC
CRY
CS
CSI

CSP
CV

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; common operations services
control point
compaction indicator
cyclic redundancy check
cryptography verification
configuration services
code selection indicator
control sequence prefix
control vector

D
DAF
DCE

DCF
DO
ddd
DEF
DEN

destination address field
data circuit-terminating equipment
data count field
day of month
day of year
destination element address field
distribution user element name (SNAOS)
Appendix C. List of Abbreviations and Symbols

C-1

DES
DFC
DGN
DISC
DISOSS
DISTIU

DLC
DLU
DM

DPN
DQ
DR11
DR21

DS
DSAF

DSP
DST
DSU

DTE

Date Encryption Standard
data flow control
distribution user group name (SNAOS)
Disconnect (SOLC)
Distributed Office Support System
distribution interchange unit (SNAOS)
data link control
destination logic unit
Disconnected Mode (SOLC)
destination program name
dequeue
definite response 1 indicator
definite response 2 indicator
distribution services
Destination Subarea Address Field
data stream profile
data services task or device service task
distribution service unit (SNAOS)
data terminal equipment

E
EB
EBCDIC
EBI

EC
ECI

ED
EDI
EFI
ENA

ENP
ER
ERP

ERCL
ERI
ERN

ERP
Exp
EXR

end bracket
extended binary coded decimai 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
F

FCB
FCS
FDX

FFR
FI

FlO
FIFO
FM
FMD
FMDS
FMH

C-2

SNA Formats

flag (SOLC)
forms control block
frame check sequence (SOLC)
full-duplex data flow
flip-flop direction control
field-formatted record
format indicator
format identification
first-in, first-out
function management
function management data
function management data services
function management header

FMHC
FNI
FRMR
FS
FS2

function management header concatenation
fixed fields without field separators
Frame Reject (SDLC)
fixed fields with field separators
fixed fields with or without field separators

G
GDS
GE

general data stream
greater than or equal to

H
HDX

hex
HH
HPCA

ID
IERN
ILU
IMS/VS
INS
INP
IPL
IPM
IPR

I/Q
IRS
ISO
IU

half-duplex data flow
hexadecimal
hours
High-Performance Communication Adapter

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)

K
KEYIND

key indicator

L
LAN
LCID
LH
LIFO
LL
LMS
LRH
LT
LSID
LU
LVx
LV1

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; less than
local session identification
logical Ul1it
variable length parameter
variable length parameter, first position

M
(ma)
MGR

maintenance services
manager
Appendix C. List of Abbreviations and Symbols

C-3

MM
MPC
MPF
MPL

month, minutes
maximum presentation column
mapping field (BIU segments)
maximum presentation line

N
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'-OAF' assignor indicator
origin element field
office information interchange
originating logical unit
origin subarea field

p
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 (SOLC)

Q
Q
QC
QEC
QR
QRI

R
C-4

SNA Formats

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
RQD
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 (+ 1-)
Ready To Receive (SOLC)
request/response unit

s
S

(s)

SC
SCB
SCS
SOl
SOLC
SEC
SESS
SIM
SLU
SNA·
SNC
SNF
SNI
SNAOS
SNRM
SPC
SPU
SQN
SRI
SS
SSCP
STP
SU
SVC

secondary
session services
session control
string control byte
SNA character string
sense data included indicator
Synchronous Data Link Control
secondary
session
Set Initialization Mode (SOLC)
secondary logical unit
Systems Network Architecture
sense code
sequence number field
SNA network interconnection
SNA distribution services
Set Normal Response Mode (SOLC)
sync point command
secondary physical unit
sequence number
stack reference indicator
seconds
system services control point
service transaction program
shared; unnamed
services

Appendix C. List of Abbreviations and Symbols

C-S

T
T1
T2
T2.0
T2.1
T4
T5

TC
TERM
TEST
TG
TGN
TH

TlU
TPF
TPN

TRN
TS
TWX

type-1 (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 (SOLe)
transmission group
transmission group number
transmission header
terminating logical unit
transmission priority field
transaction program name
transparent
transmission services
teletypewriter exchange service

u_
UA
UI

UNAVl
UP
URC

Unnumbered
Unnumbered
unavailable
Unnumbered
user request

Acknow!edgment (SDLe)
Information (SOLe)
Poll (SOLe)
correlation

V
VO

vaLiD
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

w
WP

word processing

X
XIO
X'n ... n'
XMIT

XRF

Exchange Identification (SOLe)
hexadecimal digits
transmit
Extended Recovery Facility

v
YY

year

Special Characters
I
C-6

S NA Formats

(vertical stroke) exclusive or

(asterisk) any value
(not sign) logical not
(underscore) separates multiple terms, or qualifiers, in a phrase

Appendix C. List of Abbreviations and Symbols

C-7

C-8

SNA Formats

~ndelt

A
Accept Status (X 11 0 I) Reporting Acceptance
Subfield 8-128
Accept (X I 85 I) Request Change Control MS Subvector 8-120
Access SQcurity Information subfields 10-10
format 10-10
ACTIVATE LOGICAL UNIT (ACTLU) 5-4
ACTIVATE PHYSICAL UNIT (ACTPU) 5-4
Activate Subfield
Change Management Activation Use
(X ' 20 I) 8-144
Force Indication (X 11 0 I) 8-143
Activate (X I 81 I) Request Activation MS
Subvector 8-143
Activation Acceptance MS Subvector
Activation Acceptance (X 182 I) 8-145
Activation Acceptance Subfield
Attempt Status (X I 10 I ) 8-145
Activation Acceptance (X 182 I ) Activation Acceptance
MS Subvector 8-145
Activation Use Status (X 130 I) Install Subfield 8-124
Activation Use Status (X 130 I) Reporting Secondary
Installation Subfield 8-130
Activation Use (X 130 I) Install Subfield 8-117
ACTLU 5-4
See also ACTIVATE LOGICAL UNIT
ACTPU 5-4
See also ACTIVATE PHYSICAL UNIT
agent correlation 13-22
agent report
encoding table 15-8
agent request
encoding table 15-6
Alert MS Subvector
Basic Alert (X ' 911) 8-19
Cause Undetermined (X 197 I) 8-93
Detail Qualifier (EBCDIC) (X lAO I) 8-96
Detail Qualifier (Hexadecimal) (X IA 11) 8-96
Detailed Data (X 198 I ) 8-94
Failure Causes (X 196 I ) 8-70
Generic Alert Data (X 192 I ) 8-24
Install Causes (X 195 I ) 8-62
Probable Causes (X 193 I ) 8-35
SDLC Link Station Data (X ' 8C') 8-16
User Causes (X 194 I) 8-52
Alert (XIOOOOI) MS Major Vector 8-13
allocation information
encoding table 15-9

Analyze Status (X ' 80621) MS Major Vector 8-134
Associated Resource Name List (X I 011) Name List
Subfield 8-172
Attach FM header (FMH-5) 10-8
Attempt Status (X 110 I) Activation Acceptance Subfield 8-145
Automatic Acceptance Status (X 170 I) Reporting
Installation Subfield 8-126
Automatic Acceptance (X 170 I) Install Subfield 8-119
Automatic Removal Status (X 150 I) Reporting Installation Subfield 8-125
Automatic Removal (X 150 I) Install Subfield 8-118

B
Back-Level Change Name (X 190 I) Change Control MS
Subvector 8-131
Back-Level Status (X 110 I) Reporting Back-Level
Status Subfield 8-131
Basic Alert (X I 91 I) Alert MS Subvector 8-19
BBI
See Begin Bracket indicator (BBI)
BCI
See Begin Chain indicator (BCI)
Beaconing Data (X I 07 I) LAN Link Connection Subsystem Data Subfield 8-191
Begin Bracket indicator (BBI) 4-3, 4-7
Begin Chain indicator (BCI) 4-2, 4-4
Begin Data Parameters MS Subvector
Probable Causes (X 193 I ) 8-164
Resource State (X I 82 I ) 8-164
Begin Data Parameters (X '130A I) MS Parameter
Major Vector 8-163
BID 5-5
BIND 5-5
See also BIND SESSION
BIND SESSION (BIND) 5-5
BIS 5-15
See also BRACKET INITIATION STOPPED
bits and fields
BRACKET INITIATION STOPPED (BIS) 5-15
Bridge Identifier (X I OA I) LAN Link Connection Subsystem Data Subfield 8-192

C
CANCEL 5-16
capacity service parameter 13-17
category value, sense code 9-1
See also sense data
Cause Undetermined (X 197 1) Alert MS
Subvector 8-93

Index

X-1

CDI
See Change Direction indicator (CDI)
CEBI
See Conditional End Bracket indicator (CEBI)
Change Control MS Subvector
Back-Level Change Name (X'SO') 8-131
Deleted Change Name (X'S4') 8-132
Detailed Data (X 'S8') 8-132
Reported Change Name (X' 88 ') 8-128
Reporting Acceptance (X '86') 8-128
Reporting Back-Level Status (X'8E') 8-130
Reporting Deletion (X 'S2') 8-131
Reporti ng In stall ation (X' 82 ' ) 8-123
Reporting Removal (X'84') 8-126
Reporting Secondary Installation (X '8A') 8-12S
Secondary Installation Change Name
(X' 8C ' ) 8-130
Change Control (X' 0050') MS Major Vector 8-121
Change Direction indicator (CDI) 4-3, 4-8
Change Management Activation Use (X '20') Activate
Subfield 8-144
Change Number of Sessions (CNOS)
command format 12-1
Change Number of Sessions (X'1210') GDS
character-coded request A-1
CHASE 5-16
child 13-1, 15-1
CLEAR 5-16
code points
FS1 13-73
FS2 13-72
SNA/FS 15-35
Code Selection indicator (CSI) 4-3, 4-8
Coded Character Set I D (X' 02') Self-Defining Text
Message Subfield 8-184
compare states
command format 12-4
Compare States (X'1213') GDS Variable 12-4
comparison operator 13-15
Completion Query Message Unit (CQMU) 13-11
Completion Report Message Unit (CRMU) 13-12
Conditional End Bracket indicator (CEBI) 4-3, 4-7
Control Point Management Services Unit (X '1212')
GDS Variable 12-4
Control Vector
COSITPF (X '2C ' ) 8-7
Extended Sense Data (X' 35 ' ) 8·8
Fully-qualified PCID (X '60') 8-10
LU-LU Session Services Capabilities (X' OC') 8-5
Mode (X'2D') 8-8
Network Name (X'OE') 8-6
Product Set 10 (X '10') 8-6
SSCP-LU Session Capabilities (X '00') 8-4
XID Negotiation Error (X '22') 8·7

X-2

SNA Formats

conversation-level security
Access Security Information subfields 10-10
Corequisite Change (X '87') Request Change Control
MS Subvector 8-120
COSITPF (X '2C') Control Vector 8-7
CQMU 13-11
CRMU 13-12
CRV 5-17
See also CRYPTOGRAPHY VERIFICATION
CRYPTOGRAPHY VERIFICATION (CRV) 5-17
CSI
See Code Selection indicator (CSI)
Current N(S)/N(R) Counts (X' 01') SDLC Link Station
Data Subfield 8-16

D
DACTLU 5-17
See also DEACTIVATE LOGICAL UNIT
DACTPU 5-18
See also DEACTIVATE PHYSICAL UNIT
Data Reset Flag (X'45') MS Common
Subvector 8-187
DatelTime Subfield
Greenwich Mean Time Offset (X'20') 8-166
Loca! DatelTime (X '1 0') 8-166
DatelTime (X'01') MS Common Subvector 8-165
DCMU 13-S
DEACTIVATE LOGICAL UNIT (DACTLU) 5-17
DEACTIVATE PHYSICAL UNIT (DACTPU) 5-18
Definite Response 1 indicator (DR11) 4-3, 4-5
Definite Response 2 indicator (DR21) 4-3, 4-5
Deleted Change Name (X '94') Change Control MS
Subvector 8-132
Deletion (X '1 0') Reporting Deletion Subfield 8-132
destination
list 13-27
Destination Application Name (X '50') Name List Subfield 8-173
Detail Qualifier (EBCDIC) (X' AO ' ) Alert MS
. Subvector 8·96
Detail Qualifier (Hexadecimal) (X' A 1') Alert MS Subvector 8-S6
Detailed Data Subfield
Qualified Message Data (X '01') 8-94
Detailed Data (X '82') Network Alert Common
Subfield 8-109
Detailed Data (X '82') Supporting Data Correlation
Subfield 8-188
Detailed Data (X '98') Alert MS Subvector 8-94
Detailed Data (X '98') Change Control MS
Subvector 8-132
distribution
flags 13-14
Distribution Continuation Message Unit (DCMU) 13-S

Distribution Message Unit (DMU) 13-49
Distribution Report Message Unit (ORMU) 13-8
Distribution Report Operands 13-51
Distribution Transport Message Unit (DTMU) 13-6
DMU 13-49
DRMU 13-8
DRll
See Definite Response 1 indicator (DR11)
DR21
See Definite Response 2 indicator (DR21)
DTMU 13-6

E
EBI
See End Bracket indicator (EBI)
ECI
See End Chain indicator (ECI)
EDI
See Enciphered Data indicator (EDI)
Emulated Product Identifier (X' 01') Product ID Subfield 8-180
Enciphered Data indicator (EDI) 4-3, 4-8
Enciphered Data Structured Data Subfield 7-5
encodings for SNA/FS 15-1
End Bracket indicator (EBI) 4-3, 4-7
End Chain indicator (ECI) 4-3, 4-4
End Parameter Data (X' 130B ') MS Parameter Major
.
Vector 8-165
ERI
See Exception Response indicator (ERI)
error category
See sense data
Error Data (X'12F4') GDS Variable 14-2
Error Log (X'12E1') GDS Variable 14-3
exception report
flag 13-14
EXCEPTION REQUEST (EXR) 4-10
Exception Response indicator (ERI) 4-3, 4-5
Exchange Log Name
command form'at 12-3
Exchange Log Name (X '1211') GDS Variable 12-3
Execute Command (X '8061') MS Major Vector 8-133
EXR
See EXCEPTION REQUEST (EXR)
EXR (EXCEPTION REQUEST)
sense data included with 9-1
extended sense data control vector (X '35 1 )
sense data included with 9-1
Extended Sense Data (X '35 ' ) Control Vector 8-8

F
Failure Causes Subfield
Failure Causes (X' 01') 8-70
Failure Causes (X 1 01 ' ) Failure Causes Subfield

8-70

Failure Causes (X '96') Alert MS Subvector 8-70
Fault Domain Description (X' 06') LAN Link Connection Subsystem Data Subfield 8-191
Fault Domain Error Weight Pair (X' 09') LAN Link Connection Subsystem Data Subfield 8-192
Fault Domain Names (X '26') LAN Link Connection
Subsystem Data Subfield 8-193
FI
See Format indicator (FI)
FlO (Format Identifier) fields 3-1
FID2 3-1
FID2 Field Descriptions 3-1
FM Header 1 10-2
FM Header 10 10-15
FM Header 12: Security 10-15
FM Header 2 10-5
FM Header 3 10-6
FM Header 4 10;.7
FM Header 5: Attach (LU 6.2) 10-8
FM Header 5: Attach (Not LU 6.2) 10-11
FM Header 6 10-12
FM Header 7: Error Description (LU 6.2) 10-13
FM Header 7: Error Description (Not LU 6.2) 10-14
FM header 8 10-15
FM Usage field 6-3
FM (function management)
profiles 6-3
Usage field 6-3
Force Indication (X '1 0') Activate Subfield 8-143
Format indicator (FI) 4-2, 4-4
format set 1 (FS1)
message units 13-49
structure descriptions 13-53
termi nology 13-75
format set 2 (FS2)
message units 13-6
structure descriptions 13-13
termi nology 13-75
Fully-qualified PCID (X '60') Control Vector 8-10
Fully-qualified Session PCID (X '60') Supporting Data
Correlation Subfield 8-188
function management header type 7 (FMH-7)
sense data included with 9-1
function management (FM) headers 10-1
introduction 10-1
placement within RU 10-1
function management (FM) profiles 6-3

G
GDS
See general data stream
GDS code points
FSl 13-73
FS2 13-72
GDS Variable
Change Number of Sessions (X '121 0')

12-1

Index

X-3

GDS Variable (continued)
Compare States (X I 1213 I) 12-4
Control Point Management Services Unit
(X'12121) 12-4
Error Data (X'12F41) 14-2
Error Log 14-3
Error Log (X I 12Ell) 14-3
Exchange Log Name (X'12111) 12-3
general data stream B-1
general data stream variable B-1
Application Data 14-2
Error Data 14-2
Map Name 14-2
Null Data 14-2
User Control Data 14-2
Generic Alert Data (X 192 I) Alert MS Subvector 8-24
global names
encodings 15-9
registered values 15-36
GMT offset 13-20-13-21, 13-35
Greenwich Mean Time Offset (X 120 I) DatelTime Subfield 8-166

H
H~rdv.'are

Product Common Name (X·OE 1 ) Product !D
Subfield 8-183
Hardware Product Identifier (X I 00 I) Product 10 Subfield 8-178
header description table 13-3, 15-3
children
number 13-4, 15-4
order 13-4, 15-4
subtable 13-5, 15-4
unrecognized children allowed 13-4, 15-4
IDIT 13-4, 15-3
length 13-4, 15-4
occurrences 13-4, 15-4
structure class 13-3, 15-3
structure name 13-3, 15-3
structure reference 13-3, 15-3
Hierarchy Name List (X I 03 I) MS Common
Subvector 8-167
Hierarchy Name List (X 110 I) Hierarchy/Reso~rce List
Subfield 8-170
Hierarchy/Resource List Subfield
Hierarchy Name List (X 110 I) 8-170
Hierarchy/Resource List (X I 05 1) MS Common Subvector 8-170

I-frame
maximum number of 2-7
I-frames, maximum number of 2-3
ILUITLU Notification NOTIFY Vector

X-4

SNA Formats

5-25

INIT-SELF Format 0 5-19
See also INITIATE-SELF
INIT-SELF Format 1 5-21
See also INITIATE-SELF
INITIATE-SELF (INIT-SELF Format 0) 5-19
INITIATE-SELF (INIT-SELF Format 1) 5-21
Install Causes Subfield
Install Causes (X I 01 1) 8-63
Install Causes (X I 01 I) Install Causes Subfield 8-63
Install Causes (X 195 1) Alert MS Subvector 8-62
Install Subfield
Activation Use Status (X 130 I ) 8-124
Activation Use (X I 30 I ) 8-117
Automatic Acceptance (X 170 I) 8-119
Automatic Removal (X I 50 I) 8-118
Post-Test (X 160 I) 8-118
Pre-Test (X'40') 8-118
Removability (X 120 I ) 8-117
Install (X I 81 I) Request Change Control MS
Subvector 8-116
Installation Status (X 110 I) Reporting Installation Subfield 8-123
Installation Status (X 11 0 I) Reporting Secondary
Installation Subfield 8-129
IPM
See ISOLATED PACING MESSAGE (IPM)
IPR
See ISOLATED PACING RESPONSE (IPR)
ISOLATED PACING MESSAGE (IPM) 4-9
ISOLATED PACING RESPONSE (IPR) 4-9

L
LAN Link Connection Subsystem Data Subfield
Beaconing Data (X I 07 I ) 8-191
Bridge Identifier (X I OA I ) 8-192
Fault Domain Description (X I 06 I) 8-191
Fault Domain Error Weight Pair (X I 09 1) 8-192
Fault Domain Names (X 126 1) 8-193
LAN Routing Information (X 105 1) 8-190
Local Individual MAC Address (X ' 03 1) 8-190
Local Individual MAC Name (X 123 1) 8-193
Remote Individual MAC Address (X ' 041) 8-190
Remote Individual MAC Name (X'241) 8-193
Ring or Bus Identifier (X I 02 I ) 8-189
Single MAC Address (X ' 08 1) 8-191
Single MAC Name (X 128 I) 8-194
LAN Link Connection Subsystem Data (X 151 I) Supporting Data Correlation Subfield 8-189
LAN Routing Information (X I 05 I) LAN Link Connection
Subsystem Data Subfield 8-190
Last Received N(R) Count (X I 08 I) SDLC Link Station
Data Subfield 8-19

Last SDLC Control Field Received (X I 03 I) SDLC Link
Station Data Subfield 8-17
Last SDLC Control Field Sent (X ' 041) SDLC Link
Station Data Subfield 8-17
LCS Link Attributes (X I 07 I) Link Connection Subsystem Config. Data Subfield 8-196
LCS Link Station Attributes (X I 06 I) Link Connection
Subsystem Config. Data Subfield 8-196
length prefix (LL) 8-1
Link Connection Subsystem Configuration Data
(X 152 I) MS Common Subvector 8-194
Link Connection Subsystem Config. Data Subfield
LCS Link Attributes (X I 07 I) 8-196
LCS Link Station Attributes (X' 06') 8-196
Local Device Address (X ' 041) 8-196
LPDA Fault LSL Descriptor (X 108 1) 8-197
Port Address (X 101 I) 8-195
Remote Device Address (X 102 I) 8-195
link header 1-1, 1-2, 1-3
Link Station State (X I 06 I) SDLC Link Station Data
Subfield 8-18
link trailer 1-1, 1-5, 1-7
LLC Reply Timer Expiration Count (X 107 1) SDLC Link
Station Data Subfield 8-18
LLiD 13-1, 15-1
Local DatelTime (X 110 I) DatelTime Subfield 8-166
Local Device Address (X' 04 I) Link Connection Subsystem Config. Data Subfield 8-196
Local Individual MAC Address (X I 03 I) LAN Link Connection Subsystem Data Subfield 8-190
Local Individual MAC Name (X'23 1) LAN Link Connection Subsystem Data Subfield 8-193
LOGICAL UNIT STATUS (LUSTAT) 5-22
LPDA Fault LSL Descriptor (X 108 1) Link Connection
Subsystem Config. Data Subfield 8-197
LPIU
Maximum size 2-8
LT 13-1, 15-1
LU name 13-19
LU-LU Session Services Capabilities NOTIFY
Vector 5-26
LU-LU Session Services Capabilities (X I OC I) Control
Vector 8-5
LUSTAT 5-22
See also LOGICAL UNIT STATUS

M
Maximum
I-field length 2-2
RU size 6-2, 6-3
Message 10 (X ' Ol') Qualified Message
Subfield 8-174
message unit (M U)
identifier 13-13
instance number 13-13

Microcode EC Level (X'08') Product 10
Subfield 8-183
Mode Name Structured Data Subfield 7-2
Mode (X 120 I) Control Vector 8-8
modifier value, sense code 9-1
See also sense data
MS Common Subvector
Data Reset FI ag (X '45 I ) 8-187
DatelTime (X ' Oll) 8-165
Hierarchy Name List (X ' 03 1) 8-167
Hierarchy/Resource List (X I 05 1) 8-170
Link Connection Subsystem Configuration Data
(X 152 I ) 8-194
Name List (X'06 1) 8-172
Product Identifier (X 1111) 8-175
Product Set 10 (X ' l0') 8-175
Qualified Message (X I OA I ) 8-173
Relative Time (X'421) 8-186
Self-Defining Text Message (X ' 311) 8-184
Sense Data (X '70 I) 8-197
SNA Address List (X ' 041) 8-168
Supporting Data Correlation (X 148 I) 8-187
Text Message (X' 00') 8-165
MS Major Vector
Alert (X I 0000 I) 8-13
Analyze Status (X I 8062 I ) 8-134
Change Control (X' 0050 I ) 8-121
Execute Command (X 180611) 8-133
Query Resource Data (X 18063 I) 8-136
Reply Activation Acceptance (X I 0066 I ) 8-144
Reply Product Set 10 (X I 0090 I) 8-156
Reply to Analyze Status (X' 0062 I) 8-135
Reply to Execute Command (X 10061 I) 8-133
Reply to Query Resource Data (X 10063') 8-137
Reply to Test Resource (X I 0064') 8-139
Request Activation (X I 8066 I ) 8-142
Request Change Control (X '8050') 8-115
Request Product Set I D (X' 8090 I ) 8-154
Request Response Time Monitor (X' 8080 ' ) 8-147
Response Time Monitor (X 10080') 8-150
Send Message to Operator (X'006F') 8-146
Test Resource (X 180641) 8-138
MS Parameter Major Vector
8egin Data Parameters (X I 130A ') 8-163
End Parameter Data (X I 1308' ) 8-165
Structured Data (X' 1307' ) 8-160
Text Data (X 11300 I) 8-159
Transparent Coded Datastream(X I 1309 I ) 8-163
MUJD
definition 13-13

Index

X-S

N
Name List Subfield
Associated Resource Name List (X'01') 8-172
Destination Application Name (X '50') 8-173
Name List (X' 06') MS Common Subvector 8-172
National Language 10 (X'12') Self-Defining Text
Message Subfield 8-185
negative response
format 5-39
sense data included with 9-1
Network Alert Common Subfield
Detailed Data (X '82') 8-109
Product Set 10 Index (X '83') 8-114
Recommended Actions (X' 81 ' ) 8-97
network identifier 13-19
NETWORK MANAGEMENT VECTOR TRANSPORT
(NMVT) 5-23
Network Name Pair or Uninterpreted Name Pair
(X' 06 ') Session Key 8-11
Network Name (X' OE') Control Vector 8-6
Network-Qualified PLU Network Name Structured Data
Subfield 7-3
Network-Qualified SLU Network Name Structured Data
NMVT 5-23
See also NETWORK MANAGEMENT VECTOR
TRANSPORT
Node and Port-Attached Devices Identification (X' 83' )
Request PSID MS Subvector 8-156
Node Identification (X' 81') Request PS I 0 MS Subvector 8-155
NOTIFY 5-24
NOTIFY Vector
I LUITLU Notification 5-25
LU-LU Session Services Capabilities 5-26
NS PROCEDURE ERROR (NSPE) 5-27
NSPE 5-27
See also NS PROCEDURE ERROR

o
Outstanding Frame Count (X '02') SDLC Link Station
Data Subfield 8-16

p
Pacing indicator (PI) 4-3, 4-7
Padded Data indicator (POI) 4-3, 4-8
parent
structure 13-1, 15-1
POI
See Padded Data indicator (POI)
PI
See Pacing indicator (PI)
PIP Subfield 10-11

X-6

SNA Formats

PIP Variable 10-10
PIU (Path Information Unit) 1-3
Port Address (X' 01') Link Connection Subsystem
Config. Data Subfield 8-195
Port Number (X' 10') Port-Attached Device Config.
Des. Subfield 8-158
Port-Attached Device Configuration Description
(X'82') Reply PSID MS Subvector 8-157
Port-Attached Device Config. Des. Subfield
Port Number (X '1 0') 8-158
Power-on Since Last Solicitation (X '30') 8-158
Power-on Status (X'20') 8-158
Post-Test Status (X '60') Reporting Installation Subfield 8-126
Post-Test Status (X '60') Reporting Removal
Subfield 8-127
Post-Test (X'60') Install Subfield 8-118
Post-Test (X'60') Remove Subfield 8-120
Power-on Since Last Solicitation (X '30') Port-Attached
Device Config. Des. Subfield 8-158
Power-on Status (X '20') Port-Attached Device Config.
Des. Subfield 8-158
Pre-Test Status (X '40') Reporting Installation
Subfie!d 8-125
Pre-Test (X '40') Install Subfield 8-118
presentation services (PS) headers
definition 11-1
format 11-1
priority service parameter 13-16
PRMU 13-12
Probable Causes (X' 93 ') Alert MS Subvector 8-35
Probable Causes (X '93') Begin Data Parameters MS
Subvector 8-164
Product 10 Subfield
Emulated Product Identifier (X'01') 8-180
Hardware Product Common Name (X'OE') 8-183
Hardware Product Identifier (X' 00' ) 8-178
Microcode EC Level (X' OB') 8-183
Software Product Common Level (X' 04 ' ) - 8-181
Software Product Common Name (X'06') 8-181
Software Product Customization Date and Time
(X' 09 ' ) 8-182
Software Product Customization Identifier
(X ' 07 ' ) 8-181
Software Product Program Number (X' 08') 8-182
Software Product Serviceable Component Identifier
(X' 02 ' ) 8-180
Product Identifier (X' 11 ') MS Common
Subvector 8-175
Product Set 10 Index (X'83') Network Alert Common
Subfield 8-114
Product Set 10 (X' 10 ') Control Vector 8-6
Product Set 10 (X' 10 ') MS Common Subvector 8-175

profiles
FM profile 0 6-4
FM profile 18 6-6
FM profile 19 6-7
FM profile 2 6-4
FM profile 3 6-4
FM profile 4 6-5
FM profile 6 6-6
FM profile 7 6-6
FM (function management) 6-3
TS profile 1 6-2
TS profile 2 6-2
TS profile 3 6-2
TS profile 4 6-2
TS profile 7 6-3
TS (transmission services) 6-1
protection service parameter 13-16
PS Header 10: Sync Point Control 11-1
Purge Report Message Unit (PRMU) 13-12

Q
QC 5-28
See also QUIESCE COMPLETE
QEC 5-29
See also QUIESCE AT END OF CHAIN
QRI
See Queued Response indicator (QRI)
Qualified Message Data (X I 01 1) Detailed Data Subfield 8-94
Qualified Message Subfield
Message ID (X I 01 1) 8-174
Replacement Text (X 1021) 8-175
Qualified Message (X I OA I) MS Common
Subvector 8-173
Query Resource Data (X 18063 I) MS Major
Vector 8-136
Queued Response indicator (QRI) 4-3,4-6
QUIESCE AT END OF CHAIN (QEC) 5-29
QUIESCE COMPLETE (OC) 5-28

R
RAMU 13-12
Random Data Structured Data Subfield 7-4
READY TO RECEIVE (RTR) 5-31
Receiver Exception Message Unit (REMU)
FS1 13-52
FS2 13-11
RECFMS 5-29
See also RECORD FORMATTED MAINTENANCE
STATISTICS
Recommended Actions (X I 81 I) Network Alert
Common Subfield 8-97
RECORD FORMATTED MAINTENANCE STATISTICS
(RECFMS) 5-29
Relative Time (X'421) MS Common Subvector 8-186

RELEASE QUIESCE (RELQ) 5-29
RELQ 5-29
See also RELEASE QUIESCE
Remote Device Address (X I 02 I) Link Connection Subsystem Config. Data Subfield 8-195
Remote Individual MAC Address (X 1041) LAN Link
Connection Subsystem Data Subfield 8-190
Remote Individual MAC Name (X'241) LAN Link Connection Subsystem Data Subfield 8-193
Removability Status (X 120 I) Reporting Installation
Subfield 8-124
Removability (X'20') Install Subfield 8-117
Removal Status (X 110 I) Reporting Removal
Subfield 8-127
Remove Subfield
Post-Test (X 160 I) 8-120
Remove (X I 83 I) Request Change Control MS Subvector 8-119
REMU
FS1 13-52
FS2 13-11
Replacement Text (X I 02 I) Qualified Message
Subfield 8-175
Reply Activation Acceptance (X I 0066 I) MS Major
Vector 8-144
Reply Product Set I D (X I 0090 I) MS Major
Vector 8-156
Reply PSID MS Subvector
Port-Attached Device Configuration Description
(X I 82 I ) 8-157
Reply to Analyze Status (X I 0062 I) MS Major
Vector 8-135
Reply to Execute Command (X'0061I ) MS Major
Vector 8-133
Reply to Query Resource Data (X 10063 1) MS Major
Vector 8-137
Reply to Test Resource MS Subvector
Test Result Data (X ' 811) 8-140
Reply to Test Resource (X I 0064 1) MS Major
Vector 8-139
report service parameters 13-24
derivation of. from service_parms 13-24
Reported Change Name (X 188 I) Change Control MS
Subvector 8-128
Reporting Acceptance Subfield
Accept Status (X 110 I) 8-128
Reporting Acceptance (X 186 I) Change Control MS
Subvector 8-128
Reporting Back-Level Status Subfield
Back-Level Status (X 110 I ) 8-131
Reporting Back-Level Status (X '8E I) Change Control
MS Subvector 8-130
Reporting Deletion Subfield
Deletion (X 11 0 I) 8-132

Index

X-7

Reporting Deletion (X 192 I) Change Control MS Subvector 8-131
Reporting Installation Subfield
Automatic Acceptance Status (X 170 I ) 8-126
Automatic Removal Status (X I 50 I ) 8-125
Installation Status (XI101) 8-123
Post-Test Status (X ' 60 ' ) 8-126
Pre-Test Status (X 140 I) 8-125
Removability Status (X 120 I) 8-124
Reporting Installation (X 182 I) Change Control MS
Subvector 8-123
Reporting Removal Subfield
Post-Test Status (X 160 I) 8-127
Removal Status (X I 10 I ) 8-127
Reporting Removal (X 184 I) Change Control MS Subvector 8-126
Reporting Secondary Installation Subfield
Activation Use Status (X 130 I) 8-130
Installation Status (XI101) 8-129
Reporting Secondary Installation (X '8A I) Change
Control MS Subvector 8-129
REQDISCONT 5-30
See also REQUEST DISCONTACT
REQMS 5-30
See also REQUEST MAINTENANCE STATISTICS
Request Activation MS Subvector
Activate (X ' 811) 8-143
Request Activation (X 18066 I) MS Major Vector 8-142
Request Change Control MS Subvector
Accept (X 185 1) 8-120
Corequisite Change (X 187 I) 8-120
Install (X ' 811) 8-116
Remove (X ' 83 1) 8-119
Request Change Control (X 18050 I) MS Major
Vector 8-115
REQUEST DISCONTACT (REQDISCONT) 5-30
request header 4-1
Request Larger Window indicator (RLWI) 4-3,4-8
REQUEST MAINTENANCE STATISTICS (REQMS) 5-30
Request Product Set I D (X I 8090 I) MS Major
Vector 8-154
Request PSID MS Subvector
Node and Port-Attached Devices Identification
(X ' 83 1) 8-156
Node Identification (X I 81 I) 8-155
REQUEST RECOVERY (RQR) 5-30
Request Response Time Monitor (X 18080 I) MS ~ajor
Vector 8-147
Request RTM MS Subvector
RTM Control (X 194 I ) 8-148
RTM Request (X 192 I ) 8-148
REQUEST SHUTDOWN (RSHUTD) 5-31
request/response header (RH) 4-2, 4-4
discussion of bit usage and values 4-4-4-8

x-a

SNA Formats

request/response header (RH) (continued)
format and bit settings 4-2
Request/Response Indicator (RRI) 4-2, 4-4
Request/Response Unit Category 4-2, 4-4
reserved 5-1
Reset Accepted Message Unit (RAMU) 13-12
Reset Request Message Unit (RRMU) 13-12
Resource Data Subfield
Resource Item Bit String Value (X ' 05 1) 8-162
Resource Item Character Value (X ' 03 1) 8-162
Resource Item Hex Value (X ' 021) 8-161
Resource Item Integer Value (X ' 041) 8-162
Resource Data (X 180 I) Structured Data MS
Subvector 8-160
Resource Item Bit String Value (X I 05 I) Resource Data
Subfield 8-162
Resource Item Character Value (X 103 I) Resource
Data Subfield 8-162
Resource Item Hex Value (X I 02 I) Resource Data Subfield 8-161
Resource Item Integer Value (X I 04 I) Resource Data
Subfield 8-162
Resource Item Name Subfield
Resource Item Name (X I 01 I) 8-161
Resource Item Name (X I 01 1) Resource Item Name
Subfield 8-161
Resource State (X 182 I) Begin Data Parameters MS
Subvector 8-164
Response Time Monitor (X I 0080 I) MS Major
Vector 8-150
Response Type indicator (RTI) 4-3, 4-6
RH
See request/response header (RH)
Ring or Bus Identifier (X 102 I) LAN Link Connection
Subsystem Data Subfield 8-189
RLWI
See Request Larger Window indicator (RLWI)
RQR 5-30
See also REQUEST RECOVERY
RRI
See Request/Response Indicator (RRI)
RRMU 13-12
RSHUTD 5-31
See also REQUEST SHUTDOWN
RSP(ACTLU) 5-41
RSP(ACTPU) 5-41
RSP(BIND) 5-42
RSP(STSN) 5-44
RTI
See Response Type indicator (RTI)
RTM Control (X 194 I) Request RTM MS
Subvector 8-148
RTM Data (X 193 I) RTM MS Subvector 8-153
RTM MS Subvector
RTM Data (X ' 93 1) 8-153
RTM Status Reply (X ' 911) 8-151

RTM Request (X 192 I) Request RTM MS
Subvector 8-148
RTM Status Reply (X ' 911) RTM MS Subvector
RTR 5-31
See also READY TO RECEIVE
RU Category
See Request/Response Unit Category
RU size, maximum 6-2,6-3

8-151

S
SBI 5-31
See also STOP BRACKET INITIATION
SOl
See Sense Data Included indicator (SOl)
SDLC frames 1-1
link header (LH) 1-1
address 1-2
control field 1-3
flag 1-1
link trailer (LT) 1-1
flag 1-7
frame check sequence 1-5
SDLC Link Station Data Subfield
Current N(S)/N(R) Counts (X 1011) 8-16
Last Received N(R) Count (X ' 08 1) 8-19
Last SDLC Control Field Received (X ' 03 1) 8-17
Last SDLC Control Field Sent (X ' 041) 8-17
Link Station State (X I 06 I) 8-18
LLC Reply Timer Expiration Count (X ' 071) 8-18
Outstanding Frame Count (X 1021) 8-16
Sequence Number Modulus (X ' 05 1) 8-17
SDLC Link Station Data (X '8C I) Alert MS
Subvector 8-16
SOT 5-32
See also START DATA TRAFFIC
Secondary Installation Change Name (X '8C I) Change
Control MS Subvector 8-130
security service p'arameter 13-17
Self-Defining Text Message Subfield
Coded Character Set 10 (X 102 I ) 8-184
National Language 10 (X 112 I) 8-185
Sender ID (X I 21 I) 8-185
Text Message (X ' 30 ' ) 8-186
Self-Defining Text Message (X ' 311) MS Common Subvector 8-184
SEMU
FS1 13-52
FS2 13-11
Send Message to Operator (X I 006F I) MS Major
Vector 8-146
Sender Exception Message Unit (SEMU)
FS1 13-52
FS2 13-11
Sender 10 (X'211) Self-Defining Text Message Subfield 8-185

sense code
See sense data
sense data 9-1
format of 9-1
sense code
category X'OO' (user sense data only) 9-1
category X'08' (request reject) 9-1
category X'10' (request error) 9-1
category X'20' (state error) 9-1
category X'40' (RH usage error) 9-1
category X'80' (path error) 9-1
category XIOO I (user sense data only) 9-1
category X I 08 I (request reject) 9-2
category X I 10 1 (request error) 9-44
category X 120 I (state error) 9-59
category X 140 I (RH usage error) 9-61
category X 180 I (path error) 9-63
modifier 9-1
modifier value of XIOO I 9-1
sense-code specific information 9-1
user-defined data 9-1
Sense Data Included indicator (SOl) 4-2, 4-4
Sense Data (X I 70 I) MS Common Subvector 8-197
sense data included with 9-1
sequence number 13-20
Sequence Number Modulus (X I 05 I) SDLC Link Station
Data Subfield 8-17
server names
registered values 15-36
server report
encoding table 15-8
server request
encoding table 15-7
service parameters 13-15
Session Instance Identifier Structured Data
Subfield 7-3
Session Key
Network Name Pair or Uninterpreted Name Pair
(X I 06 I ) 8-11
URC (X'OA I) 8-11
Session Keys
table of 8-11
Session Qualifier Structured Data Subfield 7-2
session-level security
FMH-12 10-15
SET AND TEST SEQUENCE NUMBERS (STSN) 5-33
SHUTC 5-32
See also SHUTDOWN COMPLETE
SHUTD 5-32
See also SHUTDOWN
SHUTDOWN COMPLETE (SHUTC) 5-32
SHUTDOWN (SHUTD) 5-32
SIG 5-33
See also SIGNAL
SIGNAL (SIG) 5-33
Single MAC Address (X 108 I) LAN Link Connection
Subsystem Data Subfield 8-191

Index

X-9

Single MAC Name (X 128 1) LAN Link Connection Subsystem Data Subfield 8-194
SNA Address List (X 1041) MS Common
Subvector 8-168
SNA condition report (SNACR) 13-10,15-11
SNA report code 13-37, 15-28
SNF processing 3-2-3-3
Software Product Common Level (X 104 1) Product ID
Subfield 8-181
Software Product Common Name (X ' 06 1) Product ID
Subfield 8-181
Software Product Customization Date and Time
(X 109 1) Product ID Subfield 8-182
Software Product Customization Identifier (X 107 1)
Product ID Subfield 8-181
Software Product Program Number (X 108 1) Product I D
Subfield 8-182
Software Product Serviceable Component Identifier
(X 102 1) Product I D Subfield 8-180
SSCP-LU Session Capabilities (X 100 1) Control
Vector 8-4
stack reference indicator (SRI)
contained in FMH-2
functions and codes 10-6
START DATA TRAFFIC (SDT) 5-32
STOP BRACKET INITIATION (S81) 5-31
structure
classification 13-1, 15-1
atomic 13-1, 15-1
child 13-1, 15-1
delimited parent 13-2, 15-2
implied parent 13-2, 15-2
length-bounded 13-1, 15-1
length-bounded parent 13-2, 15-2
parent 13-1, 15-1
segmented 13-2, 15-2
description 13-5, 15-5
properties of parent 13-2, 15-2
number of children 13-3, 15·3
order 13-2, 15-2
unrecognized children 13·3, 15·2
structure names
Agent_Correl 13·22
Agent_Object 13·29
Agent_Unit_oCWork 15·12
8egin_DEN_List 13·58
8egin_Dest_Operands 13·57
Begin_DGN_List 13-57
Begin_REN_List 13-57
8egin_Report_DEN_List 13-62
8egin_Report_DGN_List 13·62
Command 15-15
Command_Parms 15-15
Completion_Query_M U 13-45
Completion_Report_M U 13-45
Continuation_Prefix 13·37
Data_Object 15-21

X-10

SNA Formats

structure names (continued)
Data_Object_Group 15-20
Decoder-'nstruction 15-19
Deleted_Name 15-27
Deleting_Match_Flags 15-26
Dest 13-27
Destination_Operands 13-56
Dest_Agent 13-27
Dest_DEN 13-29
Dest_DGN 13-28
Dest_DGN_List 13-58
Dest_DSU 13-27
Dest_List 13-27
Dest_REN 13-28
Dest_REN_List 13-57
Dest_RGN 13-28
Dest_RGN_List 13-57
Dest_ User 13·28
DIA_Report 13-70
DIA_Report_Cont 13-70
DIA_Report_Type 13·70
Dist_Command 13·53
Dist_Continuation_MU 13-37
Dist_Flags 13-14
Dist_Flags (FS1) 13-55
Dist_Gen_Options 13-54
DistJD i3-53
Dist_MU 13·53
Di st_Report_M U 13-30
Dist_Report_Operands 13·59
Dist_Server_Operands 13-58
Dist_Transport_MU 13-13
DS_Suffix 13-29
DS_Suffix (FS1) 13-59
D_0_Acceptance 15-21
D_O_Allocation_lnfo 15-21
D_O_Contents 15-22
D_O_Global_Name 15-21
D_O_Prefix 15-21
D_O_Suffix 15..22
D_O_Type 15-21
End_DEN_List 13-58
End_Dest_Operands 13-58
End_DGN_List 13-58
End_REN_List 13-58
End_Report_DEN_List 13-65'
End_Report_DGN_List 13-65
Exception_And_Reply_Data 13-67
Fetched_Name 15-26
Fetching_Match_Flags 15-24
First_Token 15-27
FS_Action_Summary 15-22
FS_Agent_Report 15-22
FS_Agent_Request 15-15
FS_Server_Report 15-23
FS_Server_Report_Prefix 15-23
FS_Server_Request 15-19
FS_Server_Request_Prefix 15-19

structure names (continued)
FS_Suffix 15-22
Gen_DIA_Contents 13-62
Gen_DIA_Report 13-61
Gen_DIA_Type 13-62
Gen_SNADS_Cond_Code 13-61
Gen_SNADS_Content 13-61
Gen_SNADS_Report 13-60
Gen_SNADS_Type 13-60
Group_Prefix 15-20
Group_Suffix 15-22
Hop_Count 13-13
Indicator_Flags 13-45
Last_Byte_Received 13-46
Last_Structure_Received 13-46
MUJD 13-13
MUJnstance_Number 13-13
Origin_Agent 13-18
Origin_DEN 13-20
Origin_DGN 13-19
Origin_DSU 13-18
Origin_DTM 13-54
Origin_REN 13-19
Origin_RGN 13-19
Origin_Seqno 13-54
Origin_User 13-19
Parent_Class 13-39, 15-30
Parent_ID_Or_T 13-39,15-30
ParentJnstance 13-39, 15-30
Parent_Position 13-39, 15-30
Parent_Spec 13-38, 15-29
Prefix 13-53
Purge_Report_MU 13-46
Receiver_Exception_Code 13-67
Receiver_Exception_Command 13-44
Receiver_Exception_Command (FS1) 13-66
Receiver_Exception_Carrel 13-67
Receiver_Exception_MU 13-44
Receiver_Exception_MU (Type FS1) 13-66
Receiving_DSU 13-44
Receiving_REN 13-45
Receiving_RGN 13-45
Reply_Data 13-68
Report-To_Address 13-55
Report-To_Agent 13-26, 15-17
Report-To_DEN 13-23,15-18
Report-To_DGN 13-23,15-18
Report-To_DSU 13-22, 15-17
Report-To_DSU_User 13-32
Report-To_Options 13-56
Report-To_REN 13-22, 15-18
Report-To_RGN 13-22,15-18
Report-To_User 13-23, 15-18
Reported-On_Agent_Carrel 13-36
Reported-On_Dest 13-42, 15-33
Reported-On_Dest_Agent 13-36
Reported-On_Dest_DEN 13-43, 15-34
Reported-On_Dest_DGN 13-43, 15-33

structure names (continued)
Rcportcd-On_Dc5t_DSU 13-42, 15-33
Reported-On_Dest_List 13-41, 15-32
Reported-On_Dest_Prefix 13-41, 15-32
Reported-On_Dest_REN 13-42, 15-33
Reported-On_Dest_RGN 13-42, 15-33
Reported-On_Dest_Suffix 13-43, 15-34
Reported-On_Dest_ User 13-42, 15-33
Reported-On_DTM 13-60
Reported-On_Name 15-27
Reported-On_Origin_Agent 13-36
Reported-On_Origin_DEN 13-33
Reported-On_Origin_DGN 13-33
Reported-On_Origin_DSU 13-32
Reported-On_Origin_REN 13-32
Reported-On_Origin_RGN 13-32
Reported-On_Origin_User 13-33
Reported-On_Seqno 13-59
Reported-On_Seqno_DTM 13-34
Reported-On_Supp_Dist_lnfo1 13-35
Reported-On_Supp_Dist_lnfo2 13-36
Reported-On_Token_String 13-44, 15-34
Reporting_DSU 13-30
Reporting_REN 13-30
Reporting_RGN 13-30
Report_Command 13-30
Report_Correlation 13-59
Report_DEN_List 13-63
Report_DGN_List 13-62
Report_DTM 13-31
ReportJnformation 13-32
Report_Operands 13-59
Report_Prefix 13-30
Report_Service_Parms 13-24
Reset_Accepted_M U 13-48
Reset_DTM 13-47
Reset_Request_M U 13-46
Restarting_Byte_Position 13-37
Second_Token 15-27
Sender_Exception_M U 13-44
Sender_Exception_MU (Type FS1) 13-66
Sender_Retry_Action 13-44
Seqno_DTM 13-20
Server 13-18
Server_Object 13-29
Server_ObjectJnd 13-55
Server_ObLByte_Count 13-18
Server_Parms 13-58
Server_Prefix 13-58
Service_Desc_Operands 13-53
Service_Parms 13-15
Sibling_Li st 13-41, 15-32
SNADS_Report 13-69
SNADS_Report_CC 13-69
SNADS_Report_Cont 13-69
SNADS_Report_Type 13-69
SNA_Condition_Report 13-37, 15-28
SNA_Report_Code 13-37, 15-28

L(,.lndex

X-11

structure names (continued)
Source_Instruction 15-19
Source_Reporting_Action 15-16
Specific_Report 13-62
Spec_DIA_Contents 13-65
Spec_DIA_Report 13-64
Spec_DIA_Type 13-65
Spec_SNADS_CC 13-64
Spec_SNADS_Cont 13-63
Spec_SNADS_Report 13-63
Spec_SNADS_Type 13-63
Stored_Name 15-26
Structure_Byte_Offset 13-41, 15-32
Structure_Class 13-40, 15-31
Structure_Contents 13-38, 15-29
StructureJD_Or_T 13-40,15-31
StructureJnstance 13-41, 15-32
Structure_Position 13-40, 15-31
Structure_Report 13-38, 15-29
Structure_Segment_Number 13-41,15-32
Structure_Spec 13-40, 15-31
Structure_State 13-38, 15-29
Supplemental_DistJnfo1 13-21
Supplemental_DistJnfo2 13-29
Supplemental_File_lnfo1-Supplemental_File_lnfo6
Supplemental_Report 13-44, 15-34
Target_Agent 15-16
TargetJnstruction 15-19
TargeCReporting_Action 15-16
Third_Token-Tenth_Token 15-28
Token_Attributes 15-23
To_Be_Deleted_Name 15-25
To_Be_Fetched_Name 15-24
To_Be_Stored_Name 15-25
Transfer_Size 15-27
Transport_Command 13-13
Transport_Prefix 13-13
Unrecognized_Reserve 13-48,15-15
U_oCW_Requester_Agent 15-13
U_oCW_Requester_DEN 15-13
U_of_W_Requester_DGN 15-13
U_oCW_Requester_DSU 15-12
U_of_W_Requester_REN 15-12
U_oCW_Requester_RGN 15-12
U_oCW_Requester_User 15-12
U_oCW_Seqno_DTM 15-13
Structured Data MS Subvector
Resource Data (X' 80 ' ) 8-160
Structured Data Subfield
Enciphered Data 7-5
Mode Name 7-2
Network-Qualified PLU Network Name 7-3
Network-Qualified SLU Network Name 7-4
Random Data 7-4
Session Instance Identifier 7-3
Session Qualifier 7-2
Unformatted Data 7-2

X-12

SNA Formats

Structured Data (X '1307') MS Parameter Major
Vector 8-160
structured fields B-1
See also general data stream
STSN 5-33
See also SET AND TEST SEQUENCE NUMBERS
Supporting Data Correlation Subfield
Detailed Data (X '82') 8-188
Fully-qualified Session PCID (X '60') 8-188
LAN Link Connection Subsystem Data
(X'51') 8-189
Supporting Data Correlation (X '48') MS Common
Subvector 8-187
Symbol-String Types A-1
Sync Point Control
PS Header 10: 11-1
sync point protocols
RH bit settings 4-6, 4-7
Synchronous Data Link Control
See SDLC

T
TERM-SELF
15-21
See TERMINATE-SELF
TERM-SELF Fformat 1
See TERMINATE-SELF
TERM-SELF Format 0 5-34
TERM-SELF Format 1 5-35
TERMINATE-SELF Format 0 (TERM-SELF) 5-34
TERMINATE-SELF Format 1(TERM-SELF) 5-35
terminology 13-75
Test Executed Count (X'04') Test Result Data
Subfield 8-142
Test Execution Result (X' 01') Test Result Data Subfield 8-141
Test Request Count (X' 01') Test Setup Data
Subfield 8-139
Test Request Count (X' 03' ) Test Result Data
Subfield 8-142
Test Resource MS Subvector
Test Setup Data (X '80') 8-138
Test Resource (X '8064') MS Major Vector 8-138
Test Result Data Subfield
Test Executed Count (X'04') 8-142
Test Execution Result (X'01') 8-141
Test Request Count (X' 03' ) 8-142
Test Type (X '02') 8-141
Test Result Data (X'81') Reply to Test Resource MS
Subvector 8-140
Test Setup Data Subfield
Test Request Count (X'01') 8-139
Test Setup Data (X '80' ) Test Resource MS
Subvector 8-138
Test Type (X '02') Test Result Data Subfield 8-141

Text Data (X 11300 1) MS Parameter Major
Vector 8-159
Text Message (X1001) MS Common Subvector 8-165
Text Messago (X 130 1) Self-Defining Text Message
Subfield 8-186
token-ri ng network DLC 1-1, 1-7
tokens
encoding table 15-10
TP names
registered values 15-36
transmission header (TH)
FID2 3-1
transmission services (TS) profiles 6-1
Transparent Coded Datastream(X 11309 1) MS Parameter Major Vector 8-163
TS Usage field 6-1
TS (transmission services)
profiles 6-1
Usage field 6-1

U
UNBIND 5-37
See also UNBIND SESSION
sense data included with 9-1
UNBIND SESSION (UNBIND) 5-37
Unformatted Data Structured Data Subfield 7-2
Uninterpreted Name Pair or Network Name Pair
Session Key 8-11
Unit of Work Correlator
encoding table 15-6
unrecognized structures
definition 13-3, 15-2
URC (X'OA') Session Key 8';11
usage of SNA/DS 15-5
User Causes Subfield
User Causes (X 101 I) 8-53
User Causes (X 1011) User Causes Subfield 8-53
User Causes (X 194 I) Alert MS Subvector 8-52
USS symbol-string type A-1
',---

V
values

X
XID Negotiation Error (X'221) Control Vector

8-7

Index

X-13

Reader's Comment Form
Systems Networl< Architecture
Formats
Publication No. GA27-3136-10
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.)

GA27-3136-10

Reader's Comment Form

Please Do Not Staple

Fold and tape

·. . . . . . . ..
I
Fold and tape

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines Corporation
Dept. E89
P.O. Box 12195
Research Triangle Park, N.C. 27709-9990

.......................................................................................
Please Do Not Staple

Fold and tape

----- ---- -------- - -----,~--

Fold and tape

What Is your occupation?
If you wish a reply, give your name, company, mailing address, and date:

GA27-3136-10

Reader's Comment Form

Please Do Not Staple

Fold and tape

·. . . . . . . ..
I
Fold and tape

NO POSTAGE
NECESSARY
IF MAILED
INTHE
UNITED STATES

'!HE
~D DIf"OD.D ... " " "

CUwGD\1c.,,~
FIRST CLASS

1fI''-'''1 "

• • A II

nCr'L' IVIAIL

PERMIT NO. 40

ARMONK, N.Y.

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines Corporation
Dept. E89
P.O. Box 12195
Research Triangle Park, N.C. 27709-9990

Please Do Not Staple

Fold and tape

-----------------,®

Fold and tape

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

Publication Number
GA27-3136-10
Printed in USA

GA27-3136-10

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
Producer                        : Adobe Acrobat 9.31 Paper Capture Plug-in
Modify Date                     : 2010:03:19 14:14:37-08:00
Create Date                     : 2010:03:19 14:14:37-08:00
Metadata Date                   : 2010:03:19 14:14:37-08:00
Format                          : application/pdf
Document ID                     : uuid:13ce34b5-5470-4364-a79d-f5c77ff253a4
Instance ID                     : uuid:7f934f0f-64f2-4cb1-9c18-374fa90846bc
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 562

EXIF Metadata provided by EXIF.tools

GA27 3136 10_SNA_Formats_Jun89 10 SNA Formats Jun89

GA27-3136-10_SNA_Formats_Jun89 GA27-3136-10_SNA_Formats_Jun89

Navigation menu

Versions of this User Manual:

Views

Navigation