OS/390 eNetwork Communications Server IBM

SNA Operation
Version 2 Release 6

SC31-8567-01
OS/390 eNetwork Communications Server IBM

SNA Operation
Version 2 Release 6

SC31-8567-01
 Note:
Before using this information and the product it supports, be sure to read the general information under “Appendix B.
Notices” on page 491.

Second Edition (September 1998)

This edition applies to OS/390 V2R6 (Program Number 5647-A01).
Publications are not stocked at the address given below. If you want more IBM publications, ask your IBM
representative or write to the IBM branch office serving your locality.
A form for your comments is provided at the back of this document. If the form has been removed, you may address
comments to:
IBM Corporation
Department CGMD
P.O. Box 12195
Research Triangle Park, North Carolina 27709
U.S.A.
If you prefer to send comments electronically, use one of the following methods:
Fax (USA and Canada):
1-800-227-5088
Internet e-mail:
[email protected]
World Wide Web:
http://www.s390.ibm.com/os390
IBMLink:
CIBMORCF at RALVM17
IBM Mail Exchange:
USIB2HPD at IBMMAIL
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1984, 1998. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is
subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About This Book . . . . . . . . . . . . . . . . . . . . . . . xi

Who Should Use This Book . . . . . . . . . . . . . . . . . . . . xi
How to Use This Book . . . . . . . . . . . . . . . . . . . . . . xi
How This Book Is Organized . . . . . . . . . . . . . . . . . . xi
Artwork Used in This Book . . . . . . . . . . . . . . . . . . . xii
How to Contact IBM Service . . . . . . . . . . . . . . . . . . . xiii
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . xiv
Summary of Changes for SC31-8567-01 . . . . . . . . . . . . . . xiv
Summary of Changes for SC31-8567-00 . . . . . . . . . . . . . . xiv
Where to Find Related Information on the Internet . . . . . . . . . . . xiv

Chapter 1. Introducing an Operator to VTAM . . . . . . . . . . . . 1

Introducing an Operator to VTAM . . . . . . . . . . . . . . . . . . 1
Monitoring VTAM . . . . . . . . . . . . . . . . . . . . . . . 2
Controlling VTAM. . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. VTAM Operator Commands . . . . . . . . . . . . . . . 9

VTAM Operator Commands . . . . . . . . . . . . . . . . . . . . 9
Command Fundamentals . . . . . . . . . . . . . . . . . . . . 9
DISPLAY ADJCLUST Command . . . . . . . . . . . . . . . . . . 18
DISPLAY ADJCP Command. . . . . . . . . . . . . . . . . . . . 20
DISPLAY ADJSSCPS Command . . . . . . . . . . . . . . . . . . 23
DISPLAY APING Command . . . . . . . . . . . . . . . . . . . . 29
DISPLAY APINGDTP Command . . . . . . . . . . . . . . . . . . 34
DISPLAY APPLS Command. . . . . . . . . . . . . . . . . . . . 35
DISPLAY APPNTOSA Command . . . . . . . . . . . . . . . . . . 40
DISPLAY BFRUSE Command . . . . . . . . . . . . . . . . . . . 41
DISPLAY BNCOSMAP Command . . . . . . . . . . . . . . . . . 47
DISPLAY CDRMS Command . . . . . . . . . . . . . . . . . . . 49
DISPLAY CDRSCS Command . . . . . . . . . . . . . . . . . . . 53
DISPLAY CLSTRS Command . . . . . . . . . . . . . . . . . . . 59
DISPLAY CNOS Command . . . . . . . . . . . . . . . . . . . . 64
DISPLAY CONVID Command . . . . . . . . . . . . . . . . . . . 67
DISPLAY COS Command . . . . . . . . . . . . . . . . . . . . 70
DISPLAY CSM Command . . . . . . . . . . . . . . . . . . . . 72
DISPLAY DIRECTRY Command . . . . . . . . . . . . . . . . . . 75
DISPLAY DISK Command . . . . . . . . . . . . . . . . . . . . 79
DISPLAY DLURS Command . . . . . . . . . . . . . . . . . . . 81
DISPLAY EXIT Command . . . . . . . . . . . . . . . . . . . . 82
DISPLAY GROUPS Command. . . . . . . . . . . . . . . . . . . 85
DISPLAY ID Command . . . . . . . . . . . . . . . . . . . . . 89
DISPLAY LINES Command . . . . . . . . . . . . . . . . . . . . 126
DISPLAY LMTBL Command. . . . . . . . . . . . . . . . . . . . 131
DISPLAY LUGROUPS Command. . . . . . . . . . . . . . . . . . 134
DISPLAY MAJNODES Command. . . . . . . . . . . . . . . . . . 138
DISPLAY MODELS Command . . . . . . . . . . . . . . . . . . . 140
DISPLAY NCPSTOR Command . . . . . . . . . . . . . . . . . . 143
DISPLAY NETSRVR Command . . . . . . . . . . . . . . . . . . 145
DISPLAY PATHS Command. . . . . . . . . . . . . . . . . . . . 149

© Copyright IBM Corp. 1984, 1998 iii

 DISPLAY PATHTAB Command. . . . . . . . . . . . . . . . . . . 151
DISPLAY PENDING Command . . . . . . . . . . . . . . . . . . 153
DISPLAY ROUTE Command . . . . . . . . . . . . . . . . . . . 155
DISPLAY RSCLIST Command . . . . . . . . . . . . . . . . . . . 160
DISPLAY SAMAP Command . . . . . . . . . . . . . . . . . . . 168
DISPLAY SATOAPPN Command . . . . . . . . . . . . . . . . . . 169
DISPLAY SESSIONS Command . . . . . . . . . . . . . . . . . . 170
DISPLAY SNSFILTR Command . . . . . . . . . . . . . . . . . . 178
DISPLAY SRCHINFO Command . . . . . . . . . . . . . . . . . . 179
DISPLAY STATIONS Command . . . . . . . . . . . . . . . . . . 186
DISPLAY STATS Command . . . . . . . . . . . . . . . . . . . . 190
DISPLAY STORUSE Command . . . . . . . . . . . . . . . . . . 195
DISPLAY TABLE Command . . . . . . . . . . . . . . . . . . . . 201
DISPLAY TERMS Command . . . . . . . . . . . . . . . . . . . 205
DISPLAY TGPS Command . . . . . . . . . . . . . . . . . . . . 210
DISPLAY TOPO Command . . . . . . . . . . . . . . . . . . . . 213
DISPLAY TRACES Command . . . . . . . . . . . . . . . . . . . 221
DISPLAY TRL Command . . . . . . . . . . . . . . . . . . . . . 229
DISPLAY TSOUSER Command . . . . . . . . . . . . . . . . . . 232
DISPLAY USERVAR Command . . . . . . . . . . . . . . . . . . 233
DISPLAY VTAMOPTS Command . . . . . . . . . . . . . . . . . . 235
DISPLAY VTAMSTOR Command . . . . . . . . . . . . . . . . . . 243
HALT Command . . . . . . . . . . . . . . . . . . . . . . . . 248
HALT CANCEL Command . . . . . . . . . . . . . . . . . . . . 249
HALT QUICK Command . . . . . . . . . . . . . . . . . . . . . 250
MODIFY ALSLIST Command . . . . . . . . . . . . . . . . . . . 251
MODIFY APINGDTP Command . . . . . . . . . . . . . . . . . . 254
MODIFY CDRM Command . . . . . . . . . . . . . . . . . . . . 255
MODIFY CHKPT Command . . . . . . . . . . . . . . . . . . . . 257
MODIFY CNOS Command . . . . . . . . . . . . . . . . . . . . 259
MODIFY COMPRESS Command . . . . . . . . . . . . . . . . . . 264
MODIFY CSALIMIT Command. . . . . . . . . . . . . . . . . . . 266
MODIFY CSM Command. . . . . . . . . . . . . . . . . . . . . 268
MODIFY DEFAULTS Command . . . . . . . . . . . . . . . . . . 269
MODIFY DEFINE Command . . . . . . . . . . . . . . . . . . . 271
MODIFY DIRECTRY Command . . . . . . . . . . . . . . . . . . 275
MODIFY DR Command . . . . . . . . . . . . . . . . . . . . . 278
MODIFY DUMP Command . . . . . . . . . . . . . . . . . . . . 283
MODIFY ENCR Command . . . . . . . . . . . . . . . . . . . . 290
MODIFY EXIT Command. . . . . . . . . . . . . . . . . . . . . 292
MODIFY IMR Command . . . . . . . . . . . . . . . . . . . . . 296
MODIFY IOPD Command . . . . . . . . . . . . . . . . . . . . 298
MODIFY IOPURGE Command. . . . . . . . . . . . . . . . . . . 299
MODIFY LINEDEF Command . . . . . . . . . . . . . . . . . . . 301
MODIFY LL2 Command . . . . . . . . . . . . . . . . . . . . . 302
MODIFY LOAD Command . . . . . . . . . . . . . . . . . . . . 305
MODIFY MSGMOD Command. . . . . . . . . . . . . . . . . . . 313
MODIFY NEGPOLL Command . . . . . . . . . . . . . . . . . . 314
MODIFY NOTNSTAT Command . . . . . . . . . . . . . . . . . . 315
MODIFY NOTRACE Command . . . . . . . . . . . . . . . . . . 316
MODIFY POLL Command . . . . . . . . . . . . . . . . . . . . 330
MODIFY PPOLOG Command . . . . . . . . . . . . . . . . . . . 331
MODIFY PROFILES Command . . . . . . . . . . . . . . . . . . 332
MODIFY QUERY Command . . . . . . . . . . . . . . . . . . . 333
MODIFY RESOURCE Command . . . . . . . . . . . . . . . . . . 334
MODIFY RTP Command . . . . . . . . . . . . . . . . . . . . . 339

iv SNA Operation
MODIFY SECURITY Command . . . . . . . . . . . . . . . . . . 340
MODIFY SESSION Command . . . . . . . . . . . . . . . . . . . 343
MODIFY SUPP Command . . . . . . . . . . . . . . . . . . . . 344
MODIFY TABLE Command . . . . . . . . . . . . . . . . . . . . 346
MODIFY TGP Command . . . . . . . . . . . . . . . . . . . . . 353
MODIFY TNSTAT Command . . . . . . . . . . . . . . . . . . . 355
MODIFY TOPO Command . . . . . . . . . . . . . . . . . . . . 357
MODIFY TRACE Command . . . . . . . . . . . . . . . . . . . . 361
MODIFY USERVAR Command . . . . . . . . . . . . . . . . . . 381
MODIFY VTAMOPTS Command . . . . . . . . . . . . . . . . . . 385
START Command . . . . . . . . . . . . . . . . . . . . . . . 392
VARY ACQ Command . . . . . . . . . . . . . . . . . . . . . . 407
VARY ACT Command . . . . . . . . . . . . . . . . . . . . . . 410
VARY ANS Command . . . . . . . . . . . . . . . . . . . . . . 439
VARY CFS Command . . . . . . . . . . . . . . . . . . . . . . 440
VARY DIAL Command . . . . . . . . . . . . . . . . . . . . . . 442
VARY DRDS Command . . . . . . . . . . . . . . . . . . . . . 443
VARY HANGUP Command . . . . . . . . . . . . . . . . . . . . 446
VARY INACT Command . . . . . . . . . . . . . . . . . . . . . 447
VARY INOP Command . . . . . . . . . . . . . . . . . . . . . 458
VARY LOGON Command . . . . . . . . . . . . . . . . . . . . 459
VARY NOLOGON Command . . . . . . . . . . . . . . . . . . . 462
VARY PATH Command . . . . . . . . . . . . . . . . . . . . . 464
VARY REL Command . . . . . . . . . . . . . . . . . . . . . . 466
VARY TERM Command . . . . . . . . . . . . . . . . . . . . . 469

Chapter 3. Logon Manager Operator Commands . . . . . . . . . . . 473

Logon Manager Operator Commands . . . . . . . . . . . . . . . . 473
Command Fundamentals . . . . . . . . . . . . . . . . . . . . 473
MODIFY HELP Command . . . . . . . . . . . . . . . . . . . . 475
MODIFY INFO Command . . . . . . . . . . . . . . . . . . . . 476
MODIFY MEMBER Command . . . . . . . . . . . . . . . . . . . 478
MODIFY MINLINK Command . . . . . . . . . . . . . . . . . . . 479
MODIFY STOP Command . . . . . . . . . . . . . . . . . . . . 480
START Command . . . . . . . . . . . . . . . . . . . . . . . 481

Appendix A. Cross-Reference for VTAM DISPLAY Commands . . . . . . 483

Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . . 491

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 493

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 495
eNetwork Communications Server for OS/390 V2R6 Publications . . . . . . 495
Softcopy Information . . . . . . . . . . . . . . . . . . . . . 495
Marketing Information . . . . . . . . . . . . . . . . . . . . . 495
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Installation, Resource Definition, Configuration, and Tuning . . . . . . . 496
Operation . . . . . . . . . . . . . . . . . . . . . . . . . 496
Customization . . . . . . . . . . . . . . . . . . . . . . . . 497
Writing Application Programs . . . . . . . . . . . . . . . . . . 497
Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . 498
Messages and Codes . . . . . . . . . . . . . . . . . . . . . 499
APPC Application Suite . . . . . . . . . . . . . . . . . . . . 499
Multiprotocol Transport Networking (MPTN) Architecture Publications . . . . 500
OS/390 Publications . . . . . . . . . . . . . . . . . . . . . . 500

Contents v
 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Readers’ Comments — We’d Like to Hear from You. . . . . . . . . . 517

vi SNA Operation
Figures
1. Conventions Used in Network Illustrations . . . . . . . . . . . . . xiii
2. Sample VTAM Network . . . . . . . . . . . . . . . . . . . 2
3. DISPLAY TOPO Topology Example 1 . . . . . . . . . . . . . . 214
4. DISPLAY TOPO Topology Example 2 . . . . . . . . . . . . . . 214
5. Resource and Trace Reference . . . . . . . . . . . . . . . . 370
6. Valid Resource Types for VARY ACT . . . . . . . . . . . . . . 416
7. Mutually Exclusive (X) Operands for VARY ACT . . . . . . . . . . 417
8. Valid Resource Types for VARY INACT . . . . . . . . . . . . . . 450
9. DISPLAY Output Cross Reference (A-E) . . . . . . . . . . . . . 484
10. DISPLAY Output Cross Reference (G-P) . . . . . . . . . . . . . 486
11. DISPLAY Output Cross Reference (P-W) . . . . . . . . . . . . . 488

© Copyright IBM Corp. 1984, 1998 vii

viii SNA Operation
Tables
1. Buffer Pools . . . . . . . . . . . . . . . . . . . . . . . . 43
2. Active and Inactive Status Requirements for MODIFY DR for an NCP . . 279
3. Active and Inactive Status Requirements for MODIFY DR for Local
Peripheral Nodes . . . . . . . . . . . . . . . . . . . . . . 280
4. Relationship between ACTION and IPLTIME Operands . . . . . . . . 308
5. Examples of Time Specifications for IPLTIME . . . . . . . . . . . 310
6. Precedence of Values When SAVEMOD and DUMPLOAD Are Specified 418
7. Results When LOADFROM=HOST or LOADFROM Is Not Specified . . . 419
8. Results When LOADFROM=EXT Is Specified . . . . . . . . . . . 420
9. Actions to Be Taken for Unsuccessful DUMP and LOAD . . . . . . . 420
10. Active and Inactive Status Requirements for Dynamic Reconfiguration of
an NCP . . . . . . . . . . . . . . . . . . . . . . . . . 435
11. Active and Inactive Status Requirements for Dynamic Reconfiguration for
a Local SNA Major Node . . . . . . . . . . . . . . . . . . . 436
12. Active and Inactive Status Requirements for VARY DRDS for an NCP . . 443
13. Active and Inactive Status Requirements for VARY DRDS for Local SNA
Major Nodes . . . . . . . . . . . . . . . . . . . . . . . 444

© Copyright IBM Corp. 1984, 1998 ix

x SNA Operation
About This Book
This is the second edition of this book. It is intended to help network operators use
VTAM* commands and messages to control and maintain a telecommunication
network. It contains descriptions of VTAM commands.

Who Should Use This Book

This book is primarily a reference manual for network operators. It also contains
introductory material intended for a new operator. The system programmer can use
this manual as a reference about command syntax and function to write a local
operating procedure.

To make the best use of this manual, both the operator and the system programmer
should be familiar with the local operating system.

As a VTAM operator, you should have background knowledge of VTAM as well as a

background knowledge of IBM’s network programs. Information in System Network
Architecture Technical Overview might also be of use to a new operator.

A more experienced operator might want to consult OS/390 eNetwork

Communications Server: SNA Network Implementation Guide .

A system programmer preparing a local operating procedure should know how to

plan a VTAM installation, include VTAM in an MVS operating system, and define a
VTAM domain. A prerequisite publication for system programmers who use this
manual is OS/390 eNetwork Communications Server: SNA Network Implementation
Guide.

How to Use This Book

You can use this book as a reference for specific operator commands and as
background reading to help understand how to operate VTAM.

How This Book Is Organized

The manual is divided into three basic sections:
v The first chapter, “Introducing an Operator to VTAM” on page 1, provides an
overview of how an operator controls VTAM.
v The following chapters contain VTAM operator command descriptions and the
syntax required to enter these commands. The description of each command
includes the command format, a summary of the purpose of the command, and a
description of each operand. The commands are arranged within each chapter
alphabetically by operation and operand. (For example, VARY is considered an
operation, and ACT in VARY ACT is considered the operand.) These chapters
are:
– “Chapter 2. VTAM Operator Commands” on page 9, which contains
descriptions and the syntax of VTAM operator commands.
– “Logon Manager Operator Commands” on page 473, which contains
descriptions and the syntax of logon manager operator commands.
v The final section of the book includes the appendixes, bibliography, and index.

© Copyright IBM Corp. 1984, 1998 xi

 – “Appendix A. Cross-Reference for VTAM DISPLAY Commands” on page 483
contains a cross-reference of the output from VTAM operator commands.
– “Appendix B. Notices” on page 491 contains notices and trademarks of the
IBM Corporation and of other companies.
– “Bibliography” on page 511 describes the books in the VTAM library and lists
the titles and order numbers of other books related to this book or cited by
name in this book.
– “Index” on page 501 helps you find information in this book.

Artwork Used in This Book

Figure 1 on page xiii shows the conventions used in this book to illustrate the parts
of a network.

xii SNA Operation

 NETA NETB
Network Boundary

Host Processor SSCP-SSCP

Session Disk/DASD
3090 3090
Interchange Node
VTAM
Composite VTAM VTAM
VTAMLST
Network Node
User
Central Directory Application
Server CDS
ATM LU
Network
LU-LU
IBM S/390 Session
Open Systems
Adapter Terminals
CP-CP Sessions
SDLC Modems
Link 3745
NCP NCP NCP
NCP
3274
PU
Data Flow

Subarea
Connection ESCON
NN ESCD Director
Ethernet (ES/9000)
Token Ring
EN
Network Node PS/2 Virtual
Node
End Node
3172
AS/400 ESCON
Connection

APPN Connection Packet Switched

Data Network
(PSDN) VTAM
APPN
Network

Communication
Adapter Non-SNA
Device

SNA Device Coupling Facility

running in a
sysplex

Figure 1. Conventions Used in Network Illustrations

How to Contact IBM Service

For telephone assistance in problem diagnosis and resolution (in the United States
or Puerto Rico), call the IBM Software Support Center anytime (1-800-237-5511).
You will receive a return call within 8 business hours (Monday – Friday, 8:00 a.m. –
5:00 p.m., local customer time).

Outside of the United States or Puerto Rico, contact your local IBM representative
or your authorized IBM supplier.

About This Book xiii

Summary of Changes

Summary of Changes for SC31-8567-01

The following contains a summary of changes for the current release:
v DISPLAY ID Command — New syntax diagram for IP address
v DISPLAY ID Command — New samples added for Enterprise Extender
v DISPLAY ID Command — New displays added for IP addresses
v DISPLAY NETSRVR Command — Displays added for preferred network node
server
v DISPLAY SAMAP Command — New section on SAMAP tables
v DISPLAY VTAMOPTS Command — Displays updated and NNSPREF added to
related various FUNCTION groups
v MODIFY VTAMOPTS — NNSPREF, IPADDR, and TCPNAME syntax diagrams
added.
v START OPTIONS — NNSPREF, IPADDR, and TCPNAME syntax diagrams
added.
v VARY ACT — Update to DWACT=YES function
v VARY INACT — Update to the Valid Resource Types for VARY INACT table
under the TYPE=FORCE column

Summary of Changes for SC31-8567-00

The following contains a summary of changes from the previous release:
v DISPLAY APING command — updated password syntax
v DISPLAY BFRUSE command — updated Buffer Pool Table
v DISPLAY ID command — updated several displays to include VTAMTOPO
statement
v DISPLAY MODELS command — updated several displays to include
VTAMTOPO statement
v DISPLAY STATS — updated displays
v DISPLAY STORUSE — updated displays
v DISPLAY TRACE, MODIFY TRACE and MODIFY NOTRACE commands —
added new user Exit buffer trace options
v MODIFY RESOURCE — added new modify syntax and added updates for
MODSRCH command
v MODIFY TRACE — Changed default options to SAVE=YES
v MODIFY TRACE and MODIFY NOTRACE — updated IO TRACE feature
v MODIFY TRACE and START OPTIONS — updated VTAM syntax for internal
trace
v MODIFY VTAMOPTS — modified OSITOPO syntax to remove LLINES and
NOLLINEs

Where to Find Related Information on the Internet

You may find the following information helpful.

xiv SNA Operation

Note: Any pointers in this publication to websites are provided for convenience only
and do not in any manner serve as an endorsement of these websites.

You can read more about VTAM, TCP/IP, OS/390, and IBM on these Web pages:
Home Page Uniform Resource Locator (URL)
IBM eNetwork Communications Server
http://www.software.ibm.com/enetwork/commserver/
VTAM and TCP/IP
http://www.software.ibm.com/enetwork/commserver/about/csos390.html
IBM eNetwork Communications Server Support
http://www.software.ibm.com/enetwork/commserver/support/
OS/390 http://www.s390.ibm.com/os390/
IBM http://www.ibm.com/

For definitions of the terms and abbreviations used in this book, you can view or
download the latest IBM Networking Softcopy Glossary at the following URL:
v http://www.networking.ibm.com/nsg/nsgmain.htm

About This Book xv

xvi SNA Operation
Chapter 1. Introducing an Operator to VTAM
Introducing an Operator to VTAM
The most common types of operator tasks are those associated with monitoring and
controlling the network. The portion of a network that you can control varies from
one organization to another.

Sphere of control refers to the portion of the network you control and what
operations you can perform on that portion of the network. Your sphere of control is
limited by any restrictions on which portions of the network you can affect and
which commands you can issue. Within your sphere of control, you can both
monitor and control VTAM’s domain. This means that you can view what is
happening in your network and make changes to network status as needed.

Your individual network will differ from that of other operators. The following
sections about monitoring and controlling VTAM’s domain include a few examples
of results of commands issued by an operator in the sample network.

Assume the sample network consists of the resources shown in Figure 2 on page 2.
This picture shows:
v Two sessions. One is between application CICS01 and logical unit L3A3767A.
The other is between CICS01 and logical unit L3A3278A.
v Two cluster controllers. They are physical units P3A3767A and P3A3274A.
v Four workstations, identified as LUs.

© Copyright IBM Corp. 1984, 1998 1

Introduction

PU

CICS01 LU

VTAM SSCP

Channel 321
PU

NCP3AA1

Session between CICS01 and L3A3278A

Session between CICS01 and L3A3767A

LN3A1

PU PU

P3A3767A P3A3274A

Not Active

LU LU LU LU

L3A3767A L3A3278A L3A3278B L3A3290A

Figure 2. Sample VTAM Network

Monitoring VTAM
The term monitor means to watch something change, in order to ensure that the
network is operating as planned. As you monitor VTAM, you can check on the
status of the sessions between resources by using the various DISPLAY
commands. A DISPLAY command enables VTAM to show information on your
workstation screen.

This chapter does not provide details of what each of the commands can do. You
can find details about specific commands in “Chapter 2. VTAM Operator
Commands” on page 9.

The DISPLAY commands let you see the status of the network or its resources.
Status shows whether the network or its individual resources are up (active) or
down (inactive). DISPLAY commands also provide information on which resources
have been defined to VTAM and where they are in the network hierarchy.

2 SNA Operation
 Introduction
The following example illustrates the use of a DISPLAY command. The operator for
the sample network shown in Figure 2 on page 2 enters the following DISPLAY
command:
d net,id=CICS01,scope=all

Note: VTAM allows the operator to use the abbreviation “d” instead of “DISPLAY”
in the command DISPLAY NET,ID=CICS01,SCOPE=ALL.

Within this chapter, the abbreviated forms of commands (d=DISPLAY,

v=VARY, and f=MODIFY) are used. VTAM accepts commands in either
lowercase or uppercase.

The displays shown in the scenarios might differ from what you would see in
your network. For example, if the MSGMOD=YES start option is specified in
your network, the output would differ from these samples, which reflect
MSGMOD=NO.

When you enter this command, VTAM shows all active sessions with the CICS01
application program. Details about this and other commands used in this scenario
are provided in “Chapter 2. VTAM Operator Commands” on page 9.

The display shows VTAM’s response:

d net,id=CICS01,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.CICS01, TYPE = APPL
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = APPL1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = ECHO, STEPNAME = ECHO, DSPNAME = 0AAACIST
IST228I ENCRYPTION = OPTIONAL
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST171I ACTIVE SESSIONS = 0000000002, SESSION
REQUESTS = 0000000000
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I L3A3278A ACTIV-S EAABEEC3FF8D8965 0000
0000 4 0 NETA
IST635I L3A3767A ACTIV-P F6ABEEC3028D8998 0000
0000 4 0 NETA
IST314I END

Note: The highlighted fields and values in this and later samples are explained in
the text.

In this display:
v IST486I indicates that the application program is active with sessions (ACT/S)
and that the desired state for this application program is active.
v IST171I shows that there are two sessions with this application program and that
no session requests are pending.
v IST635I lists the logical units that are in session with this application program.

In your network, you can also display information about physical and logical
resources, check to see whether your domain’s VTAM is connected to any other
VTAM domains, and view routes (logical connections) that are being used.

Chapter 1. Introducing an Operator to VTAM 3

Introduction
The operator enters another DISPLAY command as follows:
d net,id=LN3A1,scope=all

The operator uses this command to display line LN3A1 and the resources that are
attached to the line.

The display shows VTAM’s response:

d net,id=LN3A1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = LN3A1, TYPE = LINE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = SDLC
IST134I GROUP = GRP3A1, MAJOR NODE = NCP3AA1
IST084I NETWORK NODES:
IST089I P3A3767A TYPE = PHYSICAL UNIT , ACTIV
IST089I L3A3767A TYPE = LOGICAL UNIT , ACTIV
IST089I P3A3274A TYPE = PHYSICAL UNIT , ACTIV
IST089I L3A3278A TYPE = LOGICAL UNIT , ACTIV
IST089I L3A3278B TYPE = LOGICAL UNIT , NEVAC
IST089I L3A3290A TYPE = LOGICAL UNIT , ACTIV
IST314I END

In this display:
v IST087I indicates that the line is a leased (nonswitched) line.
v IST089I shows two physical units and four logical units attached to the
communication controller.
v One of the logical units (L3A3278B) has never been activated (NEVAC).

The operator enters another DISPLAY command as follows:

d net,id=L3A3278B,scope=all

VTAM displays the following information about logical unit L3A3278B:

d net,id=L3A3278B,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.L3A3278B, TYPE = LOGICAL UNIT
IST486I STATUS= NEVAC, DESIRED STATE= INACT
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=MODETAB2 USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT 00000001
IST081I LINE NAME = LN3A1, LINE GROUP = GRP3A1, MAJNOD = NCP3AA1
IST135I PHYSICAL UNIT = P3A3274A
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

In this display, IST486I indicates that the current state of the logical unit is NEVAC,
which means the logical unit was never activated, and that the desired state is
INACT. It indicates that VTAM is not attempting to activate its subordinate resources
because no request was made to do so.

4 SNA Operation
 Introduction
Controlling VTAM
The term control, within VTAM, means that VTAM can be started or stopped, or
that VTAM and the network resources can be changed. The types of commands
that you use to start, stop, or change VTAM are:
v START
v HALT
v VARY
v MODIFY.

Starting VTAM
You use the START command to activate VTAM. This command uses some
defaults set by the system programmer (as part of the network definition). When
you use the START command, you might be required to enter changes or additions
to the defaults. If this is the case, your system programmer can tell you what
commands to enter.

The defaults for the START command are contained in the configuration list and
start list that are defined by the system programmer. The configuration list
contains a list of VTAM resources. VTAM uses this list to find out what resources to
activate when VTAM is first started. A network can have more than one
configuration list; this allows different configurations to be brought up at start time.

The start list contains VTAM operating system options. For example, it defines how
storage is to be used and indicates whether VTAM suppresses or shows messages.
The start list also identifies which configuration list is to be used for startup.

Stopping VTAM
The HALT commands allow you to shut down (deactivate) the network.

The different versions of HALT commands cause varying degrees of disruption to a

network. In selecting which HALT command to use, be sure to check your local
operating procedure to ensure that you use the appropriate command for your
situation.

One reason for being cautious with use of the HALT command is that you could
interrupt productive work for everyone using the system. The results of halting
VTAM are similar to disconnecting all phone lines for an office building.

Changing VTAM with VARY Commands

One way you can change VTAM is by using a VARY command. The VARY
commands affect the status of each physical resource and session. They enable
you to activate and deactivate individual resources or sessions. In addition to
allowing you to change the status of all resources, the VARY commands let you
change VTAM internal operations, such as path definitions.

In an earlier scenario, the inactive logical unit L3A3278B was shown as being
downstream from NCP3AA1. To review the status of this LU, the operator enters:
d net,id=L3A3278B,scope=all

The display shows that the logical unit is still inactive.

Chapter 1. Introducing an Operator to VTAM 5

Introduction

d net,id=L3A3278B,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.L3A3278B, TYPE = LOGICAL UNIT
IST486I STATUS= NEVAC, DESIRED STATE= INACT
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=MODETAB2 USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT 00000001
IST081I LINE NAME = LN3A1, LINE GROUP = GRP3A1, MAJNOD = NCP3AA1
IST135I PHYSICAL UNIT = P3A3274A
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

To activate the previously inactive logical unit, the operator enters:

v net,act,id=L3A3278B

The display shows:

v net,act,id=L3A3278B
IST097I VARY ACCEPTED
IST093I L3A3278B ACTIVE

If the operator reissues the DISPLAY command, the display changes as shown:
d net,id=L3A3278B,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.L3A3278B, TYPE = LOGICAL UNIT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=MODETAB2 USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU ENABLED ,SESSION LIMIT 00000001
IST081I LINE NAME = LN3A1, LINE GROUP = GRP3A1, MAJNOD = NCP3AA1
IST135I PHYSICAL UNIT = P3A3274A
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

In this display, IST486I indicates that the desired and current states are now active.

Changing VTAM with MODIFY Commands

You can use the MODIFY commands to change the start list options and other
operating system options, such as: mode table definitions, how storage is to be
used, and what type of trace is to be used.

To display an input or output (I/O) trace for the host PU specified in the start options
(in this case, ISTPUS), the operator enters:
d net,id=ISTPUS,scope=all

The display shows:

6 SNA Operation
 Introduction

d net,id=ISTPUS,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTPUS, TYPE = PU T4/5 060
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST596I IRN TRACE = OFF
IST1656I VTAMTOPO = INCLUDE, NODE REPORTED - YES
IST484I SUBAREA = 1
IST925I DYNAMIC PATH DEFINITION PATH1A STATUS = ACTIV
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST170I LINES:
IST080I 091C-L ACTIV----I
IST314I END

To start the trace, the operator enters:

f net,trace,type=io,id=istpus

Note: The abbreviation for MODIFY is “f” and the procedure name (procname) is
NET. See “Command Fundamentals” on page 9 for an explanation about the
purpose and use of procname.

The display shows:

f net,trace,type=io,id=istpus
IST097I MODIFY ACCEPTED
IST1515I IO TRACE ACTIVE
IST513I TRACE INITIATED FOR NODE ISTPUS
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = INT, SIZE = 200 PAGES 066
IST199I OPTIONS = API APPC CFS CIO CMIP CSM ESC HPR LCS LOCK MSG NRM
IST199I OPTIONS = PIU PSS SMS SSCP TCP VCNS XBUF XCF
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = EXT, SIZE = 002 BUFFERS
IST199I OPTIONS = NONE
IST314I END

If the operator reissues the DISPLAY command, the display changes:

d net,id=ISTPUS,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTPUS, TYPE = PU T4/5 070
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST596I IRN TRACE = OFF
IST1656I VTAMTOPO = INCLUDE, NODE REPORTED - YES
IST484I SUBAREA = 1
IST925I DYNAMIC PATH DEFINITION PATH1A STATUS = ACTIV
IST654I I/O TRACE = ON, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST170I LINES:
IST080I 091C-L ACTIV----I
IST314I END

Chapter 1. Introducing an Operator to VTAM 7

Introduction

8 SNA Operation
Chapter 2. VTAM Operator Commands
VTAM Operator Commands
This chapter is a reference to VTAM operator commands. It provides a description
of the format and the applicable operands of each command. The commands are
arranged alphabetically.

Command Fundamentals
A VTAM operator command consists of the command name or its abbreviation, and
various operands that describe the operation to perform. Each VTAM operator
command has a procedure name, referred to as procname in the command syntax,
which tells the operating system to route the command to VTAM for processing.
Values for procname vary according to the command and the operating system but
procname must always appear as the first operand of a command.

For example, the following command includes the verb (DISPLAY) and the
procname (NET):
DISPLAY NET,LMTBL,ID=applname,TYPE=LUNAME,LUNAME=luname
v The value of procname for VTAM commands, other than the MODIFY command,
is NET.
The value of procname for the MODIFY commands depends on the value
specified in the START command:
– If procname was specified in the START command in the form
startname.ident, where startname is the name of the VTAM start procedure
and ident is an optional procedure name identifier, then procname can be
specified as either startname.ident or simply ident for the MODIFY command.
For example, if the specification in the START command uses the .ident
extension (NETID.ident), then the MODIFY command can use either of the
following specifications:
MODIFY NETID.ident,NOTRACE,TYPE=BUF,ID=name,SCOPE=ONLY

MODIFY ident,NOTRACE,TYPE=BUF,ID=name,SCOPE=ONLY
– If procname was specified in the START command in the form startname,
where startname is the name of the VTAM start procedure, then it must also
be specified as startname for the MODIFY command.
So, if the procname specified in the START command is NETID, the MODIFY
command shown in the following sample must also have the same procname
specification:
MODIFY NETID,NOTRACE,TYPE=BUF,ID=name,SCOPE=ONLY

To avoid needless repetition, the NET operand is not described for every command.
However, for MODIFY commands whose procnames depend upon the type of
operating system used, each possibility is described.

How to Read the Syntax Diagrams

This section describes how to read the syntax diagrams used in this book.
v Read the diagrams from left-to-right, top-to-bottom, following the main path line.
Each diagram begins on the left with double arrowheads (ÊÊ) and ends on the
right with two arrowheads facing each other (ÊÍ).

© Copyright IBM Corp. 1984, 1998 9

 ÊÊ Syntax Diagram ÊÍ

v If a diagram is longer than one line, the first line ends with a single arrowhead (Ê)
and the second line begins with a single arrowhead.

ÊÊ First Line ÊÍ

ÊÊ Second Line ÊÍ

v Required operands and values appear on the main path line.

ÊÊ REQUIRED_OPERAND ÊÍ

You must code required operands and values.

If there is more than one mutually exclusive required operand or value to choose
from, they are stacked vertically in alphanumeric order.

ÊÊ REQUIRED_OPERAND_OR_VALUE_1 ÊÍ
REQUIRED_OPERAND_OR_VALUE_2

v Optional operands and values appear below the main path line.

ÊÊ ÊÍ
OPERAND

You can choose not to code optional operands and values.

If there is more than one mutually exclusive optional operand or value to choose
from, they are stacked vertically in alphanumeric order below the main path line.

ÊÊ ÊÍ
OPERAND_OR_VALUE_1
OPERAND_OR_VALUE_2

v An arrow returning to the left above an operand or value on the main path line
means that the operand or value can be repeated. The comma means that each
operand or value must be separated from the next by a comma.

ÊÊ » REPEATABLE_OPERAND ÊÍ

v An arrow returning to the left above a group of operands or values means more
than one can be selected, or a single one can be repeated.

ÊÊ ÊÍ
,

» REPEATABLE_OPERAND_OR_VALUE_1
REPEATABLE_OPERAND_OR_VALUE_2

v A word in all uppercase is an operand or value you must spell exactly as shown.
In this example, you must code OPERAND.

10 SNA Operation
 Note: VTAM commands are not case sensitive. You can code them in uppercase
or lowercase.

ÊÊ OPERAND ÊÍ

If an operand or value can be abbreviated, the abbreviation is discussed in the

text associated with the syntax diagram.
v If a diagram shows a character that is not alphanumeric (such as parentheses,
periods, commas, and equal signs), you must code the character as part of the
syntax. In this example, you must code OPERAND=(001,0.001).

ÊÊ OPERAND=(001,0.001) ÊÍ

v If a diagram shows a blank space, you must code the blank space as part of the
syntax. In this example, you must code OPERAND=(001 FIXED).

ÊÊ OPERAND=(001 FIXED) ÊÍ

v Default operands and values appear above the main path line. VTAM uses the
default if you omit the operand entirely.

DEFAULT
ÊÊ ÊÍ
OPERAND

v A word in all lowercase italics is a variable. Where you see a variable in the
syntax, you must replace it with one of its allowable names or values, as defined
in the text.

ÊÊ variable ÊÍ

v References to syntax notes appear as numbers enclosed in parentheses above

the line. Do not code the parentheses or the number.

(1)
ÊÊ OPERAND ÊÍ

Notes:
1. An example of a syntax note.
v Some diagrams contain syntax fragments, which serve to break up diagrams that
are too long, too complex, or too repetitious. Syntax fragment names are in
mixed case and are shown in the diagram and in the heading of the fragment.
The fragment is placed below the main diagram.

ÊÊ Reference to Syntax Fragment ÊÍ

Syntax Fragment

1ST_OPERAND,2ND_OPERAND,3RD_OPERAND

Chapter 2. VTAM Operator Commands 11

 Entering Operator Commands
Operator commands are entered and VTAM messages are received at the system
console or the remote network console.

VTAM operator commands and their formats are described later in this chapter.

The length of a VTAM operator command that can be entered at a console is

limited by operator command input devices, certain operator application programs,
the VTAM program operator interface, and VTAM itself. In most cases, VTAM
requires operator commands to be entered on a single input line. Two exceptions
are:
v If you need to enter more start options than will fit on one input line, end the line
with a comma. Then VTAM prompts you for additional start options.
v If a command that exceeds VTAM’s command length limit is entered on the input
line, the command is rejected even though it might fit on the input line. A
message indicating the additional length limitation imposed by VTAM is issued.
VTAM’s command length limit can be reduced if PPOLOG=YES is specified in
the START or MODIFY PPOLOG commands.

Valid and Not Valid Commands: VTAM issues messages that tell you whether
the commands you entered were accepted or rejected. The acceptance of a
command does not imply command completion. When a command is entered
correctly, with valid operands, VTAM issues a message of acknowledgment. If a
syntax error is made in entering a command, VTAM issues one or more error
messages and rejects the command.

See OS/390 eNetwork Communications Server: SNA Messages for an explanation

of error messages you might encounter.

Command Verification Exit Routine: VTAM allows you to use a command

verification exit routine (ISTCMMND) to screen and manipulate commands issued
by a VTAM operator. (The term operator includes a program operator.) The primary
purpose of this installation-wide exit routine is to screen command requests that
impact critical nodes in the network.

See the “MODIFY EXIT Command” on page 292 for information about modifying an
installation-wide exit routine. See OS/390 eNetwork Communications Server: SNA
Customization for information about the command verification exit routine.

NetView Command Tree Facility

The NetView command tree facility guides you through the process of building a
command. After you select the command options that you want, the command tree
facility generates a command string that you can send to a specified destination.
You need not remember details such as option names, the order of options, or
punctuation to build a command. eNetwork Communications Server for OS/390
V2R6 supplies a command set library for the command tree facility.

The command tree facility draws a tree structure that branches to show a product’s
commands and command options. In addition to issuing VTAM commands, you can
use the command tree facility to:
v Add commands to a command tree
v Create and save your own commands (including CLISTs)

12 SNA Operation
v Display a list of commands already sent
v Set up a command set library.

For more information on the command tree facility, see Using Command Tree/2
available on the IBM Networking Softcopy Collection Kit CD-ROM. Installation
instructions for the VTAM command set library are in the OS/390 eNetwork
Communications Server: SNA Planning and Migration Guide. Use of the VTAM
command set library requires the command tree facility to be installed on the
operator’s workstation.

Controlling Operator Messages

The message-flooding prevention facility, shipped under object-code-only (OCO)
protection since VTAM V3R1, identifies and suppresses duplicate messages which
could overrun the operator console and conceal critical information. VTAM bases its
suppression on the similarity of variable text in an original and subsequent message
and a specified time interval between the two messages.

VTAM provides an external message-flooding prevention table that can be modified

with the FLDTAB, FLDENT, and FLDEND macros. Using the FLDTAB start option or
the MODIFY TABLE command, you can tell VTAM to use the default table supplied
by IBM, use a user-defined table, or deny message-flooding prevention.

Note: You can only specify one message-flooding prevention table per VTAM.

The message-flooding prevention table identifies a list of messages that are

candidates for flooding suppression. For each candidate message, the table
identifies the criteria that must be met before VTAM suppresses duplicate
messages. The suppression criteria include:
v The amount of time between the original and subsequent message
v An indication of which variable text fields are to be compared
v Whether a message is suppressed from the system hardcopy log.

If the message is reissued within the specified time interval and the specified
variable text fields contain the same information, VTAM suppresses the message.

You do not have to code anything to get message-flooding prevention; VTAM uses
an internal default table when VTAM is initialized. To specify a user-defined table,
code the name of that table under the FLDTAB start option. This table is built
dynamically when VTAM is initialized. If errors are found while building the table,
VTAM issues a message indicating that the table has errors and uses the internal
default table. If you code FLDTAB=NONE as a start option, VTAM does not provide
any message-flooding prevention.

You can also use the MODIFY TABLE command to replace the table, or to change
or delete resource associations to the table without affecting other VTAM
operations. While VTAM is building the new message-flooding prevention table, it
uses the current table. When VTAM verifies that the new table has been
successfully built, VTAM replaces the existing table and begins using the new table.
If you issue the MODIFY TABLE command to build a message-flooding prevention
table, and there are fatal errors in the table, VTAM continues using the previous
message-flooding prevention table (if one was in use) until the new table
successfully builds.

Chapter 2. VTAM Operator Commands 13

 While you are using a message-flooding prevention table, be aware of the effect on
problem determination. If a command is issued twice within the time span specified
in the message-flooding prevention table, any message sent to the operator by that
command that is also a member of the table is suppressed for the second
command. Because the table prevents messages from being issued by VTAM, this
could affect CLISTS or automated operations facilities.

For messages that are part of a message group, VTAM searches the
message-flooding prevention table for the header message of the group. If the
header message is found and meets the suppression criteria, VTAM suppresses the
whole message group. If the header message is not found in the table, VTAM will
not suppress any message in the message group, including those that are listed in
the table.

Using Wildcard Names

A wildcard is a character used to represent an unspecified resource name or an
unspecified part of a resource name. It is used by the VTAM operator to broaden
the scope of a display or to find the name of a resource. Depending on the value of
the DSPLYWLD start option, the use of wildcards might be allowed in the value
specified for the ID operand of the following DISPLAY commands:
DISPLAY APPLS
DISPLAY CDRMS
DISPLAY CDRSCS
DISPLAY CLSTRS
DISPLAY GROUPS
DISPLAY LINES
DISPLAY RSCLIST
DISPLAY STATIONS
DISPLAY TERMS
DISPLAY TGPS
DISPLAY TOPO
DISPLAY TRACES
Notes:
1. For most of the referenced DISPLAY commands, the ID operand identifies the
name of a major node. The use of wildcards in the value of the ID operand
does not extend the display to include subordinate nodes. To display the
subordinate nodes, use the DISPLAY RSCLIST command with the IDTYPE
operand.
2. Multiple wildcards are not allowed on the DISPLAY TOPO command.

The use of wildcards is also allowed in the value specified for the EXCLUDE
operand of the DISPLAY RSCLIST command.

Attention: Specifying a wildcard name might degrade performance because VTAM

checks every resource of a particular type in the network, depending on the
command and operands issued.

VTAM recognizes two wildcard characters for these commands:

asterisk (*)
represents a string of unspecified characters

14 SNA Operation
question mark (?)
represents a single unspecified character.

Following are several examples of how wildcard names are used with the DISPLAY
RSCLIST command:
ID=* displays all resource names
ID=APP*
displays resource names that start with APP
ID=*01
displays resource names that end with 01
ID=APPL*01
displays resource names that begin with APPL and end with 01
ID=APPL0??
displays resource names that begin with APPL0 followed by exactly two
characters
ID=A*P?1
displays resource names that start with A and end with Px1 where x is any
single character
ID=?APP*
displays resource names that begin with any single character followed by
APP and followed by any other characters
ID=??*
displays resource names of two or more characters
ID=(AA00,APP*,*01)
displays the first resource, then all resource names that start with APP,
then all resources names that end with 01.

Following are several examples of how wildcard names can be used with
network-qualified names (DISPLAY RSCLIST, DISPLAY TOPO, and DISPLAY
TRACES,TYPE=NODES commands):
ID=NETA.APP*
displays resource names in NETA that begin with APP
ID=NET*.A*
displays resource names that start with A and have a network-qualified
name that begins with NET
ID=N*A.A01
displays all resources with the name A01 with a network-qualified name that
begins with N and ends with A
ID=NETA.*
displays all resources in NETA
ID=*.??
displays resources in any network with exactly two characters
ID=(A*,NETB.AP*,APPL2,*.T??)
displays:
v Resource names that begin with A
v Resource names in NETB that begin with AP
v APPL2

Chapter 2. VTAM Operator Commands 15

 v Resources in any network whose name begins with T followed by exactly
two characters

Using MVS System Symbols

You can use the following MVS system symbols in the values you specify on VTAM
network operator commands:
&SYSCLONE
Represents a 1–2-character shorthand notation for the name of the system
&SYSNAME
Represents a 1–8-character system name
&SYSPLEX
Represents a 1–8-character sysplex name
&SYSR1
Represents a 1–6-character sysres volume
&installation-defined system symbol
Represents a 1–8-character identifier. You can define this symbol to be any
identifier you want.

The substitution text for these system symbols is defined in MVS and is substituted
by MVS in place of the symbols when commands are processed. Refer to OS/390
MVS Initialization and Tuning Reference for information about how to define the
symbols in MVS.

MVS system symbols can be used to eliminate the need to know the exact name of
a resource on the system from which a command is issued.

Unformatted System Services (USS) Command Syntax

The unformatted system services (USS) table defines the format or syntax of
commands that the operator enters. USS commands that can be found in this table
include all:
v DISPLAY commands
v MODIFY commands
v VARY commands.

When one of the preceding commands is entered by a VTAM operator (including a

program operator), USS does the following:
v Supplies default values for omitted operands.
v Detects duplicate or conflicting operands. In either case the command is rejected
and an error message is issued.
v Converts abbreviations or user-defined keywords into keywords acceptable to
VTAM command processors. For example, if OPT=CIO is entered on the
MODIFY TRACE command, USS converts it to OPTION=CIO because OPT is
defined as an abbreviation for the OPTION operand.

The command conversions that are to be done by USS are defined in the
IBM-supplied USS table, ISTINCNO. The system programmer can supply a
modified syntax for these commands by using USS facilities. If the syntax of a
command has been changed, it is the responsibility of the system programmer to

16 SNA Operation
supply the operator with an explanation of the new command syntax. For more
information on USS tables, see the OS/390 eNetwork Communications Server: SNA
Resource Definition Reference.

Enter the procedure name or procname as the first operand in a USS command.
You can enter additional operands in any order. Exceptions to this include operands
that normally contain a keyword, but can be abbreviated with a single value (for
example, SCOPE=ALL can be abbreviated as ALL on the VARY ACT command and
TYPE=IMMED can be abbreviated as IMMED or I on the VARY INACT command).
In cases when an operand is coded using an abbreviation and the abbreviation
does not include the keyword, the operand must not immediately follow the
procedure name.

Chapter 2. VTAM Operator Commands 17

DISPLAY ADJCLUST

DISPLAY ADJCLUST Command

,SCOPE=ONLY
ÊÊ DISPLAY NET,ADJCLUST ÊÍ
,NETID=netid ,SCOPE= ONLY
ALL

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY ADJCLUST (adjacent cluster table) command displays the adjacent
cluster (routing) tables and their entries in the order to be used for APPN searches.
The entries in the tables include all user-defined entries, along with any dynamic
entries that have been added, based on the current value of the BNDYN start
option.

Note: The order of the entries for a search can be affected by APPN directory
entries and the directory services management exit.

Operands
NETID=netid
specifies the destination network for the adjacent cluster table to be displayed.
SCOPE
determines the range of adjacent cluster tables to be displayed.
SCOPE=ALL
specifies that all adjacent cluster tables are to be displayed. This option is
ignored if the NETID operand is specified.
SCOPE=ONLY
v If the NETID operand is specified, VTAM displays adjacent cluster
definitions that match the destination network.
v If the NETID operand is not specified, VTAM displays adjacent cluster
definitions for the default destination network.

Resulting Display
The resulting display shows whether the table is a user-defined, default, or
dynamically-built table, the level of dynamics used for the table, and the status of
each entry. Defined entries are displayed regardless of their current status. If a
defined entry is displayed as inactive, it will not be included in a search. Dynamic
entries are displayed only if they are active.

18 SNA Operation
 DISPLAY ADJCLUST
v A user-defined table indicates that adjacent cluster definition statements exist for
the specified NETID.
v A default routing table is used when no defined entries exist for the specified
NETID, but a default table has been coded. A default table indicates how to route
requests when the specified NETID is not defined.
v A dynamically-built routing table is created when no defined or default routing
table exists. This table is created completely from active dynamic routing
information.

Examples
Displaying the user-defined adjacent cluster table for a specific network:
d net,adjclust,netid=neta
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CLUSTER TABLE
IST1325I DEFINED TABLE FOR NETA DYNAMICS = LIMITED
IST1326I CP NAME TYPE STATE STATUS SNVC
IST1327I NETA.BN3 DEFINED ACTIVE FOUND 003
IST1327I NETA.BN2 DEFINED NOT ACTIVE NOT SEARCHED 003
IST1327I NETA.BN1 DYNAMIC ACTIVE NOT SEARCHED N/A
IST314I END

Displaying a default adjacent cluster table for a specific network:

d net,adjclust,netid=netb
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CLUSTER TABLE
IST1325I DEFAULT TABLE FOR NETB DYNAMICS = LIMITED
IST1326I CP NAME TYPE STATE STATUS SNVC
IST1327I NETB.BN4 DEFINED ACTIVE NOT SEARCHED 004
IST1327I NETB.BN5 DYNAMIC ACTIVE NOT SEARCHED 003
IST314I END

Displaying a dynamically-built adjacent cluster table:

d net,adjclust,netid=netc
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CLUSTER TABLE
IST1325I DYNAMIC TABLE FOR NETC DYNAMICS = LIMITED
IST1326I CP NAME TYPE STATE STATUS SNVC
IST1327I NETC.BN6 DYNAMIC ACTIVE FOUND 003
IST314I END

Chapter 2. VTAM Operator Commands 19

DISPLAY ADJCP

DISPLAY ADJCP Command

,SCOPE=ONLY
ÊÊ DISPLAY NET,ADJCP ,ID=adjacent_cp_name ÊÍ
,SCOPE= ALL
ONLY

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY ADJCP (adjacent control point) command displays the attributes of a
specific adjacent node and the connections in which it is currently involved.

Note: With high performance routing (HPR), a control point does not have to be
physically adjacent to be displayed by this command. Each endpoint of an
RTP connection considers the other endpoint an adjacent control point, even
though there may be intermediate ANR-capable nodes between the two
endpoints.

This command is valid only when it is issued at an APPN node (network node, end
node, interchange node, or migration data host).

Operands
ID=adjacent_cp_name
specifies the network-qualified name of the adjacent control point. If the network
identifier is not provided, it is assumed to be the issuing network’s network
identifier. You can specify * (or *NETWORK) as the network ID portion of a
network-qualified adjacent CP name in order to display adjacent CPs that do
not currently have a network identifier assigned to them. For example, the
following command is valid if A01N currently does not have a network ID
associated with it:
D NET,ADJCP,ID=*.a01n
SCOPE
specifies the desired scope of the display.
SCOPE=ONLY
displays the status and the major node name for the adjacent control point.
SCOPE=ALL
displays the status, the major node name, the node type, and detailed
connection information for the adjacent control point.

20 SNA Operation
 DISPLAY ADJCP
Resulting Display
The resulting VTAM display shows:
v For SCOPE=ONLY, the status and the major node name for the adjacent control
point.
v For SCOPE=ALL:
– Status of the adjacent CP
– Major node name
– Node type
– Number of connections
– Number of CP-CP capable connections
– An indication of whether the node being displayed is in the same subnetwork
as the node where you are issuing the display
– Resource name and status
– TG number
– An indication of CP-CP session capability,
– TG characteristics
– Rapid transport protocol (RTP) summary.

For a byte-by-byte explanation of the TG characteristics, see the “DISPLAY TGPS

Command” on page 210.

Examples
Displaying an adjacent CP:
d net,adjcp,id=a01n,scope=only
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CONTROL POINT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1197I ADJCP MAJOR NODE = ISTADJCP
IST314I END

Displaying detailed information for a physically adjacent CP with no RTP

connection:
d net,adjcp,id=sscpaa,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CONTROL POINT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV - TRACE= OFF
IST1197I ADJCP MAJOR NODE = ISTADJCP
IST1101I ADJCP DISPLAY SUMMARY FOR NETA.SSCPAA
IST1102I NODENAME NODETYPE CONNECTIONS CP CONNECTIONS N
IST1103I NETA.SSCPAA NN 1 1 *
IST1104I CONNECTION SUMMARY FOR NETA.SSCPAA
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I PU1A7B4 AC/R 21 YES 988D0000000000000000017100808
IST1493I RTP SUMMARY FOR NETA.SSCPAA COUNT = 0
IST172I NO RTPS FOUND
IST314I END

Displaying detailed information for a physically adjacent CP with an RTP

connection:
d net,adjcp,id=sscp2a,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CONTROL POINT 396
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV

Chapter 2. VTAM Operator Commands 21

DISPLAY ADJCP
IST1197I ADJCP MAJOR NODE = ISTADJCP
IST1101I ADJCP DISPLAY SUMMARY FOR NETA.SSCP2A
IST1102I NODENAME NODETYPE CONNECTIONS CP CONNECTIONS NATIVE
IST1103I NETA.SSCP2A NN 1 1 *NA*
IST1104I CONNECTION SUMMARY FOR NETA.SSCP2A
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I AHHCPU1 AC/R 21 YES 988D0000000000000000014C00808080
IST1500I STATE TRACE = OFF
IST1493I RTP SUMMARY FOR NETA.SSCP2A COUNT = 1
IST1486I RTP NAME STATE DESTINATION CP MNPS TYPE
IST1487I CNR00001 CONNECTED NETA.SSCP2A NO CPCP
IST314I END

Displaying detailed information for a CP that is not physically adjacent, but has an
RTP connection:
d net,adjcp,id=sscpaa,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT CONTROL POINT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV - TRACE= OFF
IST1197I ADJCP MAJOR NODE = ISTADJCP
IST1101I ADJCP DISPLAY SUMMARY FOR NETA.SSCPAA
IST1102I NODENAME NODETYPE CONNECTIONS CP CONNECTIONS N
IST1103I NETA.SSCPAA NN 0 0 *
IST1104I CONNECTION SUMMARY FOR NETA.SSCPAA
IST172I NO CONNECTIONS FOUND
IST1493I RTP SUMMARY FOR NETA.SSCPAA COUNT = 1
IST1493I RTP SUMMARY FOR NETA.SSCPAA COUNT = 2
IST1486I RTP NAME STATE DESTINATION CP MNPS TYPE
IST1487I CNR00001 CONNECTED NETA.SSCPAA NO CPCP
IST314I END

22 SNA Operation
 DISPLAY ADJSSCPS

DISPLAY ADJSSCPS Command

Display user-defined and dynamic adjacent SSCP tables:

ÊÊ DISPLAY NET,ADJSSCPS Ê
,CDRM=sscp_name

,MAX=DSPLYDEF_start_option_value
Ê Ê
,MAX= * ,NETID=netid
number_of_resources

,SCOPE=ONLY
Ê ÊÍ
ALL
,SCOPE=

ALL
ONLY

Display the adjacent SSCP table for a specific cross-domain resource:

ÊÊ DISPLAY NET,ADJSSCPS ,CDRSC=cdrsc_name Ê

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Display a specific list of adjacent CDRMs used for session requests:

ÊÊ DISPLAY NET,ADJSSCPS ,ADJLIST=list_name Ê

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Display all lists of adjacent CDRMs:

,MAX=DSPLYDEF_start_option_value
ÊÊ DISPLAY NET,ADJSSCPS ,ADJLIST=* ÊÍ
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D

Chapter 2. VTAM Operator Commands 23

DISPLAY ADJSSCPS
Operand Abbreviation
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY ADJSSCPS (adjacent system services control points) command
displays user-defined and dynamically built adjacent SSCP tables and user-defined
adjacent CDRM lists. If a user-defined adjacent SSCP table or CDRM list exists,
VTAM displays information from that table or list. If no user-defined table exists, or if
there is a table, but it does not contain any applicable entries, VTAM displays
information from the dynamic adjacent SSCP table.

If you specify a CDRSC on this command, VTAM displays the dynamic adjacent
SSCP table for the cross-domain resource, along with status information for the
resource.

Operands
ADJLIST
specifies that one or more lists of adjacent CDRMs are to be displayed. If you
specify ADJLIST, do not specify any other operands on the command.
ADJLIST=list_name
displays the list of adjacent CDRMs identified by list_name.
ADJLIST=*
displays all lists of adjacent CDRMs.
CDRM=sscp_name
specifies that information is to be displayed about the adjacent SSCP table or
tables for the specified CDRM. The sscp_name may not be a network-qualified
name; however, you can use the NETID operand to specify the network. If you
specify CDRM, do not specify CDRSC on the same command.
CDRSC=cdrsc_name
specifies that information is to be displayed about the adjacent SSCP table that
is used to establish a session with the specified CDRSC. You can specify
CDRSC as a network-qualified name. If you specify CDRSC, do not specify
CDRM, NETID, or SCOPE on the same command.

The setting of the NQNMODE start option might have an effect on how VTAM
processes this operand. See the OS/390 eNetwork Communications Server:
SNA Resource Definition Reference for an explanation of this start option.
MAX
specifies the maximum number of adjacent SSCP tables or adjacent CDRM
lists that VTAM displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.

24 SNA Operation
 DISPLAY ADJSSCPS
MAX=number_of_resources
specifies the number of adjacent SSCP tables or adjacent CDRM lists to
display for this command. The valid range is 1–value of DSPLYMAX. The
default is the value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer adjacent SSCP tables or adjacent
CDRM lists are found than you have specified on MAX, VTAM displays only
the adjacent SSCP tables or adjacent CDRM lists that are found.
NETID=netid
specifies the destination network for the adjacent SSCP table or tables to be
displayed. If you specify NETID, do not specify CDRSC on the same command.
SCOPE
determines the domain of the search for an adjacent SSCP table or tables.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.

If you specify SCOPE, do not specify CDRSC on the same command.

SCOPE=ALL
v If neither NETID nor CDRM is specified:
1. VTAM displays all user-defined ADJSSCP tables.
2. If no user-defined tables exist, VTAM displays the dynamic table if it
exists.
v If you specify NETID (and not CDRM):
1. VTAM displays all ADJSSCP tables for all CDRMs for the specified
network.
2. If there are no tables for individual CDRMS in the specified network,
VTAM displays the default table for the specified network.
3. If there is no default table for the specified network, VTAM displays
the dynamic table if it exists.
v If you specify CDRM (and not NETID):
1. VTAM displays all ADJSSCP tables for the specified CDRM in all
networks.
2. If there are no tables for the specified CDRM, VTAM displays the
default table for all networks.
3. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.
v If you specify both NETID and CDRM:
1. VTAM displays the ADJSSCP for the specified CDRM in the specified
network.
2. If there is no table for the specified CDRM in the specified network,
VTAM displays the default table for the specified network.
3. If there is no default table for the specified network, VTAM displays
the ADJSSCP table for the specified CDRM in the default network.
4. If there is no table for the specified CDRM, VTAM displays the default
table for all networks.

Chapter 2. VTAM Operator Commands 25

DISPLAY ADJSSCPS
5. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.
SCOPE=ONLY
v If you specify neither NETID nor CDRM:
1. VTAM displays the default table for all networks.
2. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.
v If you specify NETID (and not CDRM):
1. VTAM displays the default table for the specified network.
2. If there is no default table for the specified network, VTAM displays
the default table for all networks.
3. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.
v If you specify CDRM (and not NETID):
1. VTAM displays the ADJSSCP table for the specified CDRM in the
default network.
2. If there is no table for the specified CDRM in the default network,
VTAM displays the default table for all networks.
3. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.
v If you specify both NETID and CDRM:
1. VTAM displays the ADJSSCP for the specified CDRM in the specified
network.
2. If there is no table for the specified CDRM in the specified network,
VTAM displays the default table for the specified network.
3. If there is no default table for the specified network, VTAM displays
the ADJSSCP table for the specified CDRM in the default network.
4. If there is no table for the specified CDRM, VTAM displays the default
table for all networks.
5. If there is no default table for all networks, VTAM displays the
dynamic table if it exists.

Resulting Display
The resulting display differs depending on the operands specified.

If you specify the ADJLIST operand, the resulting display shows the appropriate
adjacent CDRM list.

If you specify the CDRM or CDRSC operands, the resulting display shows the
appropriate adjacent SSCP table. VTAM first searches for a user-defined table that
satisfies the command. If a user-defined table is not found and the DYNASSCP
start option has been set to YES, the dynamic adjacent SSCP table is displayed.

When DISPLAY ADJSSCPS is issued with the CDRSC operand, VTAM builds an
adjacent SSCP table as if the resource were the target of a session initiation
request. The table displayed is a combination of learned adjacent SSCPs which
have been saved for the CDRSC and the appropriate user-defined or dynamic
adjacent SSCP table. VTAM displays this table without invoking the session
management exit routine for adjacent SSCP selection.

26 SNA Operation
 DISPLAY ADJSSCPS
See the OS/390 eNetwork Communications Server: SNA Network Implementation
Guide for more information on dynamically defined adjacent SSCP tables.

Examples
Examples of the DISPLAY ADJSSCPS command are presented in a scenario
because the output of the command depends on the situation.
v Suppose that no adjacent SSCP tables are defined and no LU-LU sessions exist,
but a dynamic table was created when an SSCP-SSCP session was established
with SSCP2A. To display the dynamically created table, issue:
d net,adjsscps (with any other operands except CDRSC)
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST623I DYNAMIC ADJACENT SSCP TABLE
IST624I SSCP2A
IST314I END
v Later you establish an LU-LU session with APPL2 in SSCP2A. To display the
dynamically created, session-specific adjacent SSCP table, issue:
d net,adjsscps,cdrsc=appl2
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR APPL2 IN NETA
IST1220I SSCPNAME NETID CURRENT STATE ROUTING STATUS
IST624I SSCP2A NETA ACTIV SUCCESS
IST314I END
v Next you activate the following user-defined ADJSSCP table:
ADJTAB VBUILD TYPE=ADJSSCP
/* Default table for all networks */
SSCP1D ADJCDRM
/* CDRM SSCPD in default table for all networks */
SSCPD CDRM
SSCP2D ADJCDRM
/* Default table for NETA */
NETA NETWORK NETID=NETA
SSCP1A ADJCDRM
/* CDRM SSCPA in default table for NETA */
SSCPA CDRM
SSCP2A ADJCDRM
/* Default table for NETB */
NETB NETWORK NETID=NETB
/* CDRM SSCPA in default table for NETB */
SSCPA CDRM
SSCP2A ADJCDRM
/* Define adjacent list */
LIST1 ADJLIST
SSCPD1 ADJCDRM
SSCP2A ADJCDRM
LIST2 ADJLIST
SSCP1A ADJCDRM

To display the user-defined, default ADJSSCP table for all networks, issue:
d net,adjsscps
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST623I DEFAULT ADJACENT SSCP TABLE
IST624I SSCP1D
IST314I END
v To display all user-defined ADJSSCP tables, issue:

Chapter 2. VTAM Operator Commands 27

DISPLAY ADJSSCPS
d net,adjsscps,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR SSCPA IN NETB
IST624I SSCP2A
IST611I ADJACENT SSCP TABLE FOR SSCPA IN NETA
IST624I SSCP2A
IST623I DEFAULT ADJACENT SSCP TABLE FOR NETA
IST624I SSCP1A
IST611I ADJACENT SSCP TABLE FOR SSCPD
IST624I SSCP2D
IST623I DEFAULT ADJACENT SSCP TABLE
IST624I SSCP1D
IST314I END
v To display the user-defined table for a specific CDRM in the default ADJSSCP
table for all networks, issue:
d net,adjsscps,cdrm=sscpd
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR SSCPD
IST624I SSCP2D
IST314I END
v To display the user-defined table for a specific CDRM in a specific network,
issue:
d net,adjsscps,cdrm=sscpa,netid=neta
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR SSCPA IN NETA
IST624I SSCP2A
IST314I END
v To display all user-defined ADJSSCP tables for a specific CDRM in all networks,
issue:
d net,adjsscps,cdrm=sscpa,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR SSCPA IN NETB
IST624I SSCP2A
IST611I ADJACENT SSCP TABLE FOR SSCPA IN NETA
IST624I SSCP2A
IST314I END
v Displaying the user-defined adjacent CDRM list for a specific CDRSC:
d net,adjsscps,adjlist=list1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST1333I ADJLIST = LIST1
IST624I SSCPD1
IST624I SSCP2A
IST314I END
v Displaying all user-defined adjacent CDRM lists:
d net,adjsscps,adjlist=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST1333I ADJLIST = LIST2
IST624I SSCP1A
IST1333I ADJLIST = LIST1
IST624I SSCPD1
IST624I SSCP2A
IST314I END

28 SNA Operation
 DISPLAY APING

DISPLAY APING Command

ÊÊ DISPLAY NET,APING ,ID=resource_name Ê

,CONSEC=1 ,ECHO=YES
Ê Ê
,CONSEC=number_of_consecutive_packets ,ECHO= NO
YES

,ITER=2
Ê Ê
,ITER=number_of_send_and_receive_iterations

,LOGMODE=#INTER ,SIZE=100
Ê Ê
,LOGMODE=logon_mode_name ,PASSWORD ,SIZE=size_of_packet

,TP=APINGD
Ê ÊÍ
,TP=transaction_program_name ,USERID=userid

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY APING command tests whether a route to another LU 6.2 resource or
control point is available and displays performance information for the route if the
resource supports an APING server.

See the OS/390 eNetwork Communications Server: SNA Network Implementation

Guide for more information on APING.

Operands
CONSEC=number_of_consecutive_packets
specifies the number of consecutive packets to be sent per iteration. The value
for CONSEC can be any integer in the range 0–32763. The default is 1.

If you specify CONSEC=0, no data is sent or returned; only a version exchange

between the transaction programs occurs.
ECHO
specifies whether data is returned to the sending transaction program, if the
server transaction program supports ECHO.
ECHO=NO
specifies that data is not returned to the sending transaction program.
ECHO=YES
specifies that data is returned to the sending transaction program.

Chapter 2. VTAM Operator Commands 29

DISPLAY APING
ID=resource_name
specifies the name of the resource for which the APING transaction is
requested.
ITER=number_of_send_and_receive_iterations
specifies the number of times that consecutive packets are sent to the receiving
transaction program and returned. The value for ITER can be any integer in the
range 0–32763. The default is 2.

If you specify ITER=0, no data is sent or returned; only a version exchange

between the transaction programs occurs.
LOGMODE=logon_mode_name
specifies the logon mode name from the default logon mode table (ISTINCLM)
to be used when the session is started.

Note: The logon mode names CPSVCMG, CPSVRMGR, and SNASVCMG are
not valid for LOGMODE.
PASSWORD
specifies the password if conversation level security is requested.

This operand is valid only from a MVS console. A command with the
PASSWORD operand will be rejected if it is entered from a Program Operator
Application (POA) as there is no capability to suppress the password from
displaying via the Program Operator Interface.

When this operand is entered from a system console, the operator will be
prompted to enter the password with message IST1660A ENTER PASSWORD
FOR DISPLAY APING. When the password is entered in reply to IST1660A, it
will not be displayed on the system console or in the system log, but will be
replaced in the display with the word SUPPRESSED.

The value for PASSWORD can contain 1–8 characters.

SIZE=size_of_packet
specifies the size (in bytes) of the packets to be sent. The value for SIZE can
be any integer in the range 1–32763. The default is 100.
TP=transaction_program_name
specifies the name of the transaction program to which data is to be sent. The
default transaction program name is APINGD.

The value for TP can contain 1–64 characters.

USERID=userid
specifies the userid if conversation level security is requested.

The value for USERID can contain 1–8 characters.

Resulting Display
The resulting VTAM display shows performance information and routing information
in two separate message groups.

The performance information includes the following information:

v The specified destination LU and the session identifier (SID)
v An indication of whether the ECHO was performed

30 SNA Operation
 DISPLAY APING
v The elapsed time for conversation allocation and version exchange
v The data rate calculations for each iteration and the data rate calculations for all
iterations
v The elapsed time for each iteration and the total elapsed time for all iterations
v The minimum, maximum, and average elapsed time for each iteration.

Note: No decimal values are displayed for data rate calculations in messages. If
the data rate calculation includes a decimal, the value is truncated to the
whole number. If the data rate calculation is less than one, zero is displayed.

If a session is allocated for the DISPLAY APING command, VTAM also displays the
following routing information:
v The destination LU and the session identifier (SID)
v The class-of-service table entry and logon mode entry used

Note: If the session cannot be established with the requested LOGMODE, the
session is established with a default logon mode of *BLANK*.
v If the destination LU is found in or through a subarea network, VTAM displays:
– The origination subarea number and the destination subarea number of the
first node in the route
– The virtual route and explicit route numbers
v If the destination LU is found in or through an APPN network, VTAM displays:
– The APPN class-of-service toward the SLU
– The transmission group number and type for APPN
– The destination CP name for the TG.

The routing information can be correlated to the performance information using the
session identifier (SID).

Note: The name of the destination LU in the routing information might not match
the name of the destination LU in the performance information if any name
translation has occurred on the route between the LUs.

Examples
Displaying APING information when a session to the destination already exists and
is using the requested logon mode:
d net,aping,id=sscp2a
IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)
IST1490I DLU=NETA.SSCP2A SID=EAABEEC3710FD9E7
IST1462I ECHO IS ON
IST1463I ALLOCATION DURATION 17717 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 81 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 74 200 2 0
IST1467I 19543 200 0 0
IST1468I TOTALS: 19617 400 0 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 74 AVERAGE = 9808 MAXIMUM = 19543
IST314I END

Displaying APING information when the destination is in the same APPN network:

Chapter 2. VTAM Operator Commands 31

DISPLAY APING
d net,aping,id=sscp1a
IST097I DISPLAY ACCEPTED
IST1489I APING SESSION INFORMATION
IST1490I DLU=NETA.SSCP1A SID=F6ABEEC3742C592E
IST933I LOGMODE=#INTER , COS=*BLANK*
IST875I APPNCOS TOWARDS SLU = #INTER
IST1460I TGN CPNAME TG TYPE HPR
IST1461I 21 NETA.SSCP1A APPN RTP
IST314I END

IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)

IST1490I DLU=NETA.SSCP1A SID=F6ABEEC3742C592E
IST1462I ECHO IS ON
IST1463I ALLOCATION DURATION 834 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 174 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 119 200 1 0
IST1467I 6088 200 0 0
IST1468I TOTALS: 6207 400 0 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 119 AVERAGE = 3103 MAXIMUM = 6088
IST314I END

Displaying APING information when the destination is in an adjoining subarea

network:
d net,aping,id=sscp1a
IST097I DISPLAY ACCEPTED
IST1489I APING SESSION INFORMATION
IST1490I DLU=NETA.SSCP1A SID=EAABEE18C8567C6A
IST933I LOGMODE=#INTER , COS=*BLANK*
IST875I APPNCOS TOWARDS SLU = #INTER
IST1460I TGN CPNAME TG TYPE HPR
IST1461I 21 NETA.SSCP2A APPN ANR
IST1461I 254 SSCP1A INTERCHANGE *NA*
IST314I END

IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)

IST1490I DLU=NETA.SSCP1A SID=EAABEE18C8567C6A
IST1462I ECHO IS ON
IST1463I ALLOCATION DURATION 8208 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 35 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 26 200 7 0
IST1467I 22 200 9 0
IST1468I TOTALS: 48 400 8 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 22 AVERAGE = 24 MAXIMUM = 26
IST314I END

Displaying APING information when the destination is reached through a VRTG:

d net,aping,id=sscp2a
IST097I DISPLAY ACCEPTED
IST1489I APING SESSION INFORMATION
IST1490I DLU=NETA.SSCP2A SID=EAABEEC379DA83D2
IST933I LOGMODE=#INTER , COS=*BLANK*
IST875I APPNCOS TOWARDS SLU = #INTER
IST1460I TGN CPNAME TG TYPE HPR
IST1461I 255 NETA.SSCP2A VRTG RTP
IST314I END

IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)

IST1490I DLU=NETA.SSCP2A SID=EAABEEC379DA83D2
IST1462I ECHO IS ON

32 SNA Operation
 DISPLAY APING
IST1463I ALLOCATION DURATION 414 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 210 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 622 200 0 0
IST1467I 4246 200 0 0
IST1468I TOTALS: 4868 400 0 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 622 AVERAGE = 2434 MAXIMUM = 4246
IST314I END

Displaying APING information when the destination is in a connecting subarea

network:
d net,aping,id=sscp2a
IST097I DISPLAY ACCEPTED
IST1489I APING SESSION INFORMATION
IST1490I DLU=NETA.SSCP2A SID=EAABEEC3710FD9E7
IST933I LOGMODE=#INTER , COS=*BLANK*
IST1458I ORIGIN ADJSUB VR TP ER REVERSE ER
IST1459I 1 2 2 0 3 4
IST314I END

IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)

IST1490I DLU=NETA.SSCP2A SID=EAABEEC3710FD9E7
IST1462I ECHO IS ON
IST1463I ALLOCATION DURATION 17717 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 81 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 74 200 2 0
IST1467I 19543 200 0 0
IST1468I TOTALS: 19617 400 0 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 74 AVERAGE = 9808 MAXIMUM = 19543
IST314I END

Displaying APING information when the destination is in a non-native network:

d net,aping,id=netb.sscp7b
IST097I DISPLAY ACCEPTED
IST1489I APING SESSION INFORMATION
IST1490I DLU=NETB.SSCP7B SID=F6ABEEC374364CA8
IST933I LOGMODE=#INTER , COS=*BLANK*
IST875I APPNCOS TOWARDS SLU = #INTER
IST1460I TGN CPNAME TG TYPE HPR
IST1461I 21 NETA.SSCP1A APPN ANR
IST1461I 21 NETB.SSCP7B ISL ANR
IST314I END

IST1457I VTAM APING VERSION 2R33 (PARTNER TP VERSION 2R33)

IST1490I DLU=NETB.SSCP7B SID=F6ABEEC374364CA8
IST1462I ECHO IS ON
IST1463I ALLOCATION DURATION 360 MILLISECONDS
IST1464I PROGRAM STARTUP AND VERSION EXCHANGE: 262 MILLISECONDS
IST1465I DURATION DATA SENT DATA RATE DATA RATE
IST1466I (MILLISECONDS) (BYTES) (KBYTE/S) (MBIT/S)
IST1467I 334 200 0 0
IST1467I 108 200 1 0
IST1468I TOTALS: 442 400 0 0
IST1469I DURATION STATISTICS:
IST1470I MINIMUM = 108 AVERAGE = 221 MAXIMUM = 334
IST314I END

Chapter 2. VTAM Operator Commands 33

DISPLAY APINGDTP

DISPLAY APINGDTP Command

ÊÊ DISPLAY NET,APINGDTP ÊÍ

Purpose
The DISPLAY APINGDTP command displays the number of APINGD transaction
programs permitted to run concurrently for responding to APING requests from
other nodes.

Resulting Display
The resulting VTAM display shows the number of APINGD transaction programs
permitted to run concurrently for responding to APING requests from other nodes.

Examples
Displaying the number of transaction programs permitted to run concurrently:
d net,apingdtp
IST097I DISPLAY ACCEPTED
IST1474I APINGD TP CONCURRENT INSTANCE LIMIT = 10
IST314I END

34 SNA Operation
 DISPLAY APPLS

DISPLAY APPLS Command

ÊÊ DISPLAY NET,APPLS Ê
(1)
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
Ê ÊÍ
,MAX= * ALL
number_of_resources ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY APPLS (applications) command displays the status of active
application program major nodes in the domain along with their subordinate
application program minor nodes.

Chapter 2. VTAM Operator Commands 35

DISPLAY APPLS
Note: To display application program minor nodes independently of the major
nodes that contain them, use the DISPLAY RSCLIST command with
IDTYPE=APPLS.

Operands
ID=name
specifies the name of one or more active application program major nodes
whose subordinate resources are to be displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every application major node in the network.
MAX
specifies the maximum number of application program minor nodes that VTAM
displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of application program minor nodes to display for this
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer application program minor nodes are
found than you have specified on MAX, VTAM displays only the application
program minor nodes that are found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable application program minor nodes within the specified major
nodes (or within all major nodes if the ID operand is omitted). If this display
is undesirably large, you can use SCOPE=ACTONLY or SCOPE=CONCT
to further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all application program
minor nodes in an active state within the specified major nodes (or within all
major nodes if the ID operand is omitted). The display does not include
application programs in pending or connectable states. If no applications
are found in an active state, you can use SCOPE=ACT to broaden the
scope of the display to active, connectable, and pending applications.

36 SNA Operation
 DISPLAY APPLS
SCOPE=ACTSESS
specifies that information is to be displayed about all application program
minor nodes that are active with sessions within the specified major nodes
(or within all major nodes if the ID operand is omitted).
SCOPE=ALL
specifies that information is to be displayed about all application program
minor nodes (regardless of their status) within the specified major nodes (or
within all major nodes if the ID operand is omitted).
SCOPE=CONCT
specifies that information is to be displayed about all application program
minor nodes in a CONCT (connectable) state within the specified major
nodes (or within all major nodes if the ID operand is omitted). If no
applications are found in a connectable state, you can use SCOPE=ACT to
broaden the scope of the display to active, connectable, and pending
applications.
SCOPE=INACT
specifies that information is to be displayed about all inactive application
program minor nodes within the specified major nodes (or within all major
nodes if the ID operand is omitted). If this display is undesirably large, you
can use SCOPE=INACTONLY or SCOPE=RESET to further limit the
display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive application
program minor nodes within the specified major nodes (or within all major
nodes if the ID operand is omitted). Resources in a RESET state are not
included in the SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending application
program minor nodes within the specified major nodes (or within all major
nodes if the ID operand is omitted). A pending state is:
v A transient state to or from the fully active state
v A state of “recovery pending” or “recovery in progress” for application
programs that have been retained due to the failure or takeover of an
application program enabled for persistence.
SCOPE=RESET
specifies that information is to be displayed about all application program
minor nodes in a RESET state within the specified major nodes (or within
all major nodes if the ID operand is omitted).

Resulting Display
The resulting VTAM display shows:
v The name and status of the specified active application program major nodes (or
all active application program major nodes if the ID operand is omitted). Inactive
application program major nodes are not known to VTAM and are therefore not
displayed.
v For each active application program major node, the name and status of each
subordinate application program minor node (limited to active, connectable,
inactive, or pending minor nodes if specified on the SCOPE operand).
If a model application program has been defined in the major node being
displayed, the model application program will be included in the display. In

Chapter 2. VTAM Operator Commands 37

DISPLAY APPLS
addition, any dynamic application programs that have been built from the model
application program definition will also be included in the display.

Note: Dynamic application programs that have been deactivated are not
displayed. This is because dynamic application programs cannot exist in
an inactive state. When a dynamic application program is deactivated and
CLOSE macro processing is complete for the dynamic application
program, the definition of the dynamic application program is deleted. The
dynamic application program is no longer known by VTAM and will not
appear in the output of any DISPLAY commands.

If a channel-attached host is used as an intermediate routing node for either a

primary or backup extended recovery facility (XRF) session, the session through the
channel-attached host might fail without notifying the XRF host. In that case, a
DISPLAY APPLS command issued from either the primary or alternate host shows
the failed session across the channel attachment as active.

Examples
Displaying all application program major nodes and their minor nodes:
d net,appls
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = APPL MAJ NODES/NAMES
IST089I VTAMSEG TYPE = APPL SEGMENT , ACTIV
IST360I APPLICATIONS:
IST080I ISTATA00 CONCT ISTNOP ACTIV ISTPDCLU ACT/S
IST080I A01N ACT/S
IST089I A01APPLS TYPE = APPL SEGMENT , ACTIV
IST360I APPLICATIONS:
IST080I A01NV ACTIV A01NVPPT ACTIV A01NV000 CONCT
IST080I A01NV001 ACTIV A01NV002 ACTIV A01NV003 ACTIV
IST080I A01NV004 ACTIV A01NV005 ACTIV A01NV006 ACTIV
IST080I A01NV007 CONCT A01NV008 CONCT A01NV009 CONCT
IST080I A01TFOPT CONCT A01TFO0 CONCT A01TFO1 CONCT
IST080I A01TFO2 CONCT A01TFO3 CONCT A01TFO4 CONCT
IST080I A01TF00 CONCT A01TF01 CONCT A01TF02 CONCT
IST080I A01TF03 CONCT A01TF04 CONCT A01TF05 CONCT
IST080I A01TF06 CONCT A01TF07 CONCT A01TF08 CONCT
IST080I A01TF09 CONCT AAUTSKLP CONCT AAUTCNMI ACTIV
IST080I DSICRTR ACTIV DSIAMLUT ACT/S A01NVLUC ACT/S
IST080I A01NVSPT ACTIV BNJHWMON ACTIV ALIASAPL CONCT
IST080I DSIGDS ACTIV APPLR02 CONCT APPLA01 CONCT
IST080I APPL01 CONCT APPL0102 CONCT A01MVSNO CONCT
IST080I A01MVSOP CONCT A01MVSRE CONCT WORM CONCT
IST080I DIAL01 CONCT CAPPL01O CONCT CAPPL01C CONCT
IST080I CAPPL01N CONCT ECHO01 CONCT ECHOX01 CONCT
IST080I ECHOA01 CONCT APPCA01 CONCT A01AP08 CONCT
IST080I A01SPAP8 CONCT A01SPAP9 CONCT NPMA01M CONCT
IST080I NPMA01MA CONCT TPNS02 CONCT TPNSA01 CONCT
IST080I IMS02 CONCT MHCICS02 CONCT CICS02A CONCT
IST080I TCAM02 CONCT TSO02 ACTIV TSO0201 ACT/S
IST080I TSO0202 CONCT TSO0203 CONCT TSO0204 CONCT
IST080I TSO0205 CONCT TSO0206 CONCT TSO0207 CONCT
IST080I TSO0208 CONCT TSO0209 CONCT TSO0210 CONCT
IST080I VMA01 CONCT VMA011 CONCT VMA012 CONCT
IST080I VMA013 CONCT VMA014 CONCT VMA015 CONCT
IST080I VMA016 CONCT VMA017 CONCT VMA018 CONCT
IST080I VMA019 CONCT
IST089I A01ECHOC TYPE = APPL SEGMENT , ACTIV

38 SNA Operation
 DISPLAY APPLS
IST360I APPLICATIONS:
IST080I ECHO01A ACT/S ECHO01B ACTIV ECHO01C ACT/S
IST080I ECHO01D CONCT ECHO01E CONCT
IST314I END

Displaying a specific application program major node and its minor nodes, including
model application programs and dynamic application programs built from those
models:
d net,appls,id=a01appls
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = APPL MAJ NODES/NAMES
IST089I A01APPLS TYPE = APPL SEGMENT , ACTIV
IST360I APPLICATIONS:
IST080I APPL1 CONCT APPLA* CONCT APPL2 CONCT
IST080I APPLQ? CONCT APPLQ1 ACTIV APPL3 CONCT
IST080I APPL01 CONCT APPL0102 CONCT A01MVSNO CONCT
IST1454I 9 RESOURCE(S) DISPLAYED FOR ID=A01APPLS
IST314I END

Displaying application program major nodes and their minor nodes, limiting output
to 5 resources:
d net,appls,max=5
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = APPL MAJ NODES/NAMES
IST089I VTAMSEG TYPE = APPL SEGMENT , ACTIV
IST360I APPLICATIONS:
IST080I ISTATA00 CONCT ISTNOP ACTIV ISTPDCLU ACTIV
IST080I SSCP1A ACTIV
IST089I APPL1A TYPE = APPL SEGMENT , ACTIV
IST360I APPLICATIONS:
IST080I ADRAPL01 CONCT
IST1315I DISPLAY TRUNCATED AT MAX = 5
IST1454I 5 RESOURCE(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 39

DISPLAY APPNTOSA

DISPLAY APPNTOSA Command

ÊÊ DISPLAY NET,APPNTOSA ÊÍ

Purpose
The DISPLAY APPNTOSA command displays the APPN-to-subarea class-of-service
mapping table.

Resulting Display
The resulting VTAM display shows the APPN-to-subarea class-of-service mapping
table.

Examples
Displaying the APPN-to-subarea class-of-service mapping table:
d net,appntosa
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = APPNTOSA
IST1321I TABLE FOR APPNTOSA
IST1431I APPNCOS SUBAREA COS
IST1323I #CONNECT COSAPPL1
IST1323I #BATCH COSAPPL2
IST1323I #BATCHSC COSAPPL3
IST1323I #INTER COSAPPL4
IST1323I #CONNECT COSAPPL5 DEFAULT
IST1323I #INTERSC ISTCOSDF
IST314I END

40 SNA Operation
 DISPLAY BFRUSE

DISPLAY BFRUSE Command

,BUFFER=*
ÊÊ DISPLAY NET,BFRUSE ÊÍ
,BUFFER= *
SHORT
SUMMARY
buffid
( buffid )
,SUMMARY

Abbreviations
Operand Abbreviation
DISPLAY D
BUFFER=* BUF=*
BUFFER=buffid BUF=buffid
BUFFER=SHORT BUF=SH
BUFFER=SUMMARY BUF=SUMM

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
BUFFER=SHORT, code only BUF=SH. Do not code BUFFER=SH.

Purpose
The DISPLAY BFRUSE (buffer use) command displays information about VTAM
buffer use. It also displays storage usage summary information for VTAM modules.

Operands
BUFFER
specifies the buffers to display.

Table 1 on page 43 shows, for each buffer pool, the buffer pool ID, its name,
and its abbreviation.
BUFFER=*
displays all buffer pools and information along with:
v Common service area (CSA) usage for buffers
v Intermediate routing node buffer usage limit (IRNLIMIT)
v VTAM private storage usage for buffers
v Common service area (CSA) usage for modules
v VTAM private storage usage for modules.
BUFFER=SHORT
displays a shortened format of buffer-related information. Five digits are
shown instead of 10. If the number is too large for display in 5 digits, then 5
asterisks (*****) are displayed. To view the data for that buffer, you can use
the BUFFER=buffid operand.

The SHORT operand displays buffer pool information, along with:

Chapter 2. VTAM Operator Commands 41

DISPLAY BFRUSE
v CSA usage for buffers
v IRNLIMIT buffer usage
v VTAM private storage usage for buffers
v CSA usage for modules
v VTAM private storage usage for modules.
BUFFER=SUMMARY
displays information about:
v CSA usage for buffers
v IRNLIMIT buffer usage
v VTAM private storage usage for buffers
v CSA usage for modules
v VTAM private storage usage for modules.

The information supplied by SUMMARY is independent of the information

supplied by buffid. SUMMARY can be specified with or without buffid.
BUFFER=buffid
displays buffer pool count information for one or more standard VTAM
buffer pools. Buffer pool count information will be displayed for the specified
pools. A buffer name can be the full name, the buffer ID, or an abbreviation.

Resulting Display
For each buffer pool requested, the resulting VTAM display shows:
v The buffer pool identification (name of the buffer pool).
v Queued buffer requests (indicated by a Q after the buffer pool identification). The
message display shows the expansion limit for the Q buffer and the number of
buffers needed to satisfy the queued requests.
v Whether an expansion attempt has failed (indicated by an F after the buffer pool
identification). The message display shows the expansion limit for the F buffer
and the number of buffers needed to satisfy the queued requests.
v The size, in bytes, of each buffer. (Note that for certain buffer pools, such as
IOBUF, the size displayed might not match the size specified in the buffer pool
start options because VTAM increases the size of some buffers for buffer
headers that must be added.
v The number of buffers currently assigned to the pool.
v The number of buffers currently available for use.
v The maximum number of buffers ever assigned to the pool (since the last SMS
trace record was written, if an SMS trace is active).
v The maximum number of buffers ever used within the pool (since the last SMS
trace record was written, if an SMS trace is active).
v The number of times that the buffer pool has been expanded (since the last SMS
trace record was written, if an SMS trace is active).
v The number of available buffers at or below which expansion will occur.
v The number of available buffers at or above which contraction will be attempted.
v The number of buffers to be added during each expansion. This field contains
“NA” (not applicable) if the dynamic buffer expansion function is not being used.

42 SNA Operation
 DISPLAY BFRUSE
VTAM displays additional storage usage information when the BUFFER operand is
not coded, when BUFFER=*, when BUFFER=SHORT, or when
BUFFER=SUMMARY is specified:
v For VTAM’s common service area (CSA), including 24-bit and 31-bit addressable
storage:
– The usage limit for buffers
– The current usage for buffers and modules

Note: Current usage for buffers is shown in message IST449I. Current usage
for modules is shown in message IST1565I.
– The maximum CSA usage for buffers since the last DISPLAY BFRUSE
command
– The maximum CSA usage for buffers since VTAM was started
v For 24-bit addressable CSA storage:
– The usage limit for buffers
– The current usage for buffers and modules

Note: Current usage for buffers is shown in message IST449I. Current usage
for modules is shown in message IST1565I.
– The maximum CSA usage for buffers since the last DISPLAY BFRUSE
command
– The maximum CSA usage for buffers since VTAM was started

Note: If VTAM requests 31-bit addressable storage and the operating system
cannot honor the CSA storage request, the operating system provides
VTAM with 24-bit addressable storage. The resulting display, however,
shows the explicit storage request.
v VTAM’s intermediate routing node buffer usage limit (IRNLIMIT), current buffer
usage, and maximum buffer usage
v Current VTAM private storage usage for buffers and modules and the maximum
amount of VTAM private storage for buffers ever in use since VTAM was started.

Note: The private storage amount includes storage allocated by VTAM’s storage
management services, plus the storage for VTAM tables and
installation-wide exit routines. Releases prior to V4R1 displayed only the
amount of storage allocated by VTAM’s storage management services.

Current usage for buffers is shown in message IST981I. Current usage for
modules is shown in message IST1565I.

For more information about using VTAM buffer use data, see the OS/390 eNetwork
Communications Server: SNA Diagnosis.

Table 1 shows the IDs, names and abbreviated names of the buffer pools. For
descriptions of VTAM buffer pools, see the OS/390 eNetwork Communications
Server: SNA Network Implementation Guide.
Table 1. Buffer Pools
ID Name Abbrev
IO00 IOBUF IO
BS00 BSBUF BS
LP00 LPBUF LP

Chapter 2. VTAM Operator Commands 43

DISPLAY BFRUSE
Table 1. Buffer Pools (continued)
ID Name Abbrev
XD00 XDBUF XD
LF00 LFBUF LF
CRPL CRPLBUF CR
SF00 SFBUF SF
SP00 SPBUF SP
AP00 APBUF AP
TI00 TIBUF TI
CRA4 CRA4BUF CRA4
CRA8 CRA8BUF CRA8

Examples
Displaying VTAM buffer usage for a specific buffer:
d net,bfruse,buffer=io00
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BUFFER POOL DATA
IST920I IO00 BUFF SIZE 334 EXP INCREMENT 55
IST921I TIMES EXP 0 EXP/CONT THRESH 36 / *NA*
IST922I CURR TOTAL 110 CURR AVAILABLE 110
IST923I MAX TOTAL 110 MAX USED 1
IST989I EXP LIMIT 2147483647 BUFFS REQUESTED 0
IST314I END

Displaying a storage usage summary:

d net,bfruse,buffer=summary
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BUFFER POOL DATA
IST449I CSALIMIT = NOLIMIT, CURRENT = 1388K, MAXIMUM = 1388K
IST790I MAXIMUM CSA USED = 1388K
IST449I CSA24 LIMIT = NOLIMIT, CURRENT = 76K, MAXIMUM = 76K
IST790I MAXIMUM CSA24 USED = 76K
IST595I IRNLIMIT = NOLIMIT, CURRENT = 0K, MAXIMUM = 0K
IST981I VTAM PRIVATE: CURRENT = 4550K, MAXIMUM USED = 4603K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 40K
IST1565I PRIVATE MODULES = 5205K
IST314I END

Displaying VTAM buffer usage for a buffer pool and a storage usage summary:
d net,bfruse,buffer=(io00,summary)
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BUFFER POOL DATA
IST920I IO00 BUFF SIZE 334 EXP INCREMENT 55
IST921I TIMES EXP 0 EXP/CONT THRESH 36 / *NA*
IST922I CURR TOTAL 110 CURR AVAILABLE 110
IST923I MAX TOTAL 110 MAX USED 1
IST989I EXP LIMIT 2147483647 BUFFS REQUESTED 0
IST924I -------------------------------------------------------------
IST449I CSALIMIT = NOLIMIT, CURRENT = 1388K, MAXIMUM = 1388K
IST790I MAXIMUM CSA USED = 1388K
IST449I CSA24 LIMIT = NOLIMIT, CURRENT = 76K, MAXIMUM = 76K
IST790I MAXIMUM CSA24 USED = 76K
IST595I IRNLIMIT = NOLIMIT, CURRENT = 0K, MAXIMUM = 0K
IST981I VTAM PRIVATE: CURRENT = 4550K, MAXIMUM USED = 4603K

44 SNA Operation
 DISPLAY BFRUSE
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 40K
IST1565I PRIVATE MODULES = 5205K
IST314I END

Displaying a VTAM buffer usage summary in table format and a storage usage
summary:
d net,bfruse,buffer=short
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BUFFER POOL DATA 648
IST632I BUFF BUFF CURR CURR MAX MAX TIMES EXP/CONT EXP
IST633I ID SIZE TOTAL AVAIL TOTAL USED EXP THRESHOLD INCR
IST356I IO00 338 110 109 110 18 0 36/----- 55
IST356I BS00 298 24 24 24 0 0 12/----- 12
IST356I LP00 2032 64 61 64 5 0 22/----- 4
IST356I XD00 697 5 5 5 0 0 4/----- 5
IST356I LF00 120 120 116 120 4 0 33/----- 30
IST356I CRPL 144 200 198 200 2 0 10/----- 25
IST356I SF00 112 64 62 64 2 0 10/----- 32
IST356I SP00 176 42 42 42 0 0 1/----- 21
IST356I AP00 56 56 56 56 0 0 3/----- 56
IST356I TI00 632 60 60 60 0 0 29/----- 60
IST356I CRA4 4080 12 10 12 2 0 2/----- 6
IST356I CRA8 8176 12 12 12 0 0 2/----- 6
IST924I -------------------------------------------------------------
IST449I CSALIMIT = NOLIMIT, CURRENT = 1698K, MAXIMUM = 1698K
IST790I MAXIMUM CSA USED = 1698K
IST449I CSA24 LIMIT = NOLIMIT, CURRENT = 56K, MAXIMUM = 56K
IST790I MAXIMUM CSA24 USED = 57K
IST595I IRNLIMIT = NOLIMIT, CURRENT = 0K, MAXIMUM = 0K
IST981I VTAM PRIVATE: CURRENT = 691K, MAXIMUM USED = 698K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1456K
IST1565I CSA24 MODULES = 32K
IST1565I PRIVATE MODULES = 5823K
IST314I END

Displaying VTAM buffer usage for all buffers and a storage usage summary:
d net,bfruse
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BUFFER POOL DATA
IST920I IO00 BUFF SIZE 334 EXP INCREMENT 55
IST921I TIMES EXP 0 EXP/CONT THRESH 36 / *NA*
IST922I CURR TOTAL 110 CURR AVAILABLE 110
IST923I MAX TOTAL 110 MAX USED 1
IST989I EXP LIMIT 2147483647 BUFFS REQUESTED 0
IST924I -------------------------------------------------------------
IST920I BS00 BUFF SIZE 216 EXP INCREMENT 17
IST921I TIMES EXP 0 EXP/CONT THRESH 17 / *NA*
IST922I CURR TOTAL 34 CURR AVAILABLE 34
IST923I MAX TOTAL 34 MAX USED 0
IST924I -------------------------------------------------------------
IST920I LP00 BUFF SIZE 2032 EXP INCREMENT 4
IST921I TIMES EXP 0 EXP/CONT THRESH 22 / *NA*
IST922I CURR TOTAL 64 CURR AVAILABLE 60
IST923I MAX TOTAL 64 MAX USED 4
IST924I -------------------------------------------------------------
IST920I XD00 BUFF SIZE 681 EXP INCREMENT 5
IST921I TIMES EXP 0 EXP/CONT THRESH 5 / *NA*
IST922I CURR TOTAL 10 CURR AVAILABLE 10
IST923I MAX TOTAL 10 MAX USED 0
IST924I -------------------------------------------------------------
IST920I LF00 BUFF SIZE 120 EXP INCREMENT 30
IST921I TIMES EXP 0 EXP/CONT THRESH 33 / *NA*

Chapter 2. VTAM Operator Commands 45

DISPLAY BFRUSE
IST922I CURR TOTAL 120 CURR AVAILABLE 118
IST923I MAX TOTAL 120 MAX USED 2
IST924I -------------------------------------------------------------
IST920I CRPL BUFF SIZE 160 EXP INCREMENT 23
IST921I TIMES EXP 0 EXP/CONT THRESH 10 / *NA*
IST922I CURR TOTAL 207 CURR AVAILABLE 207
IST923I MAX TOTAL 207 MAX USED 1
IST924I -------------------------------------------------------------
IST920I SF00 BUFF SIZE 112 EXP INCREMENT 32
IST921I TIMES EXP 0 EXP/CONT THRESH 10 / *NA*
IST922I CURR TOTAL 64 CURR AVAILABLE 62
IST923I MAX TOTAL 64 MAX USED 2
IST924I -------------------------------------------------------------
IST920I SP00 BUFF SIZE 144 EXP INCREMENT 25
IST921I TIMES EXP 0 EXP/CONT THRESH 1 / *NA*
IST922I CURR TOTAL 50 CURR AVAILABLE 50
IST923I MAX TOTAL 50 MAX USED 0
IST924I -------------------------------------------------------------
IST920I AP00 BUFF SIZE 56 EXP INCREMENT 56
IST921I TIMES EXP 0 EXP/CONT THRESH 3 / *NA*
IST922I CURR TOTAL 56 CURR AVAILABLE 56
IST923I MAX TOTAL 56 MAX USED 0
IST924I -------------------------------------------------------------
IST920I TI00 BUFF SIZE 632 EXP INCREMENT 60
IST921I TIMES EXP 0 EXP/CONT THRESH 29 / *NA*
IST922I CURR TOTAL 60 CURR AVAILABLE 60
IST923I MAX TOTAL 60 MAX USED 0
IST924I -------------------------------------------------------------
IST920I CRA4 BUFF SIZE 4080 EXP INCREMENT 6
IST921I TIMES EXP 0 EXP/CONT THRESH 2 / *NA*
IST922I CURR TOTAL 12 CURR AVAILABLE 12
IST923I MAX TOTAL 12 MAX USED 2
IST924I -------------------------------------------------------------
IST920I CRA8 BUFF SIZE 8176 EXP INCREMENT 6
IST921I TIMES EXP 0 EXP/CONT THRESH 2 / *NA*
IST922I CURR TOTAL 12 CURR AVAILABLE 12
IST923I MAX TOTAL 12 MAX USED 0
IST924I -------------------------------------------------------------
IST449I CSALIMIT = NOLIMIT, CURRENT = 1388K, MAXIMUM = 1388K
IST790I MAXIMUM CSA USED = 1388K
IST449I CSA24 LIMIT = NOLIMIT, CURRENT = 76K, MAXIMUM = 76K
IST790I MAXIMUM CSA24 USED = 76K
IST595I IRNLIMIT = NOLIMIT, CURRENT = 0K, MAXIMUM = 0K
IST981I VTAM PRIVATE: CURRENT = 4554K, MAXIMUM USED = 4603K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 40K
IST1565I PRIVATE MODULES = 5205K
IST314I END

46 SNA Operation
 DISPLAY BNCOSMAP

DISPLAY BNCOSMAP Command

,SCOPE=ONLY
ÊÊ DISPLAY NET,BNCOSMAP ÊÍ
,NETID=netid ,SCOPE= ONLY
ALL

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY BNCOSMAP (border node class-of-service mapping) command
displays native and nonnative COS mappings defined for a border node.

Operands
NETID=netid
specifies the destination network for which native and nonnative border node
COS mappings are to be displayed.
SCOPE
indicates the range of border node COS mappings to be displayed. It is
meaningful only if NETID is not specified.
SCOPE=ALL
displays the COS mappings for all networks served by this border node.
SCOPE=ONLY
displays border node COS mappings for the default NETID.

Resulting Display
The resulting display shows:
v If NETID is specified, all border node COS mappings for the specified network
v If NETID is not specified:
– For SCOPE=ALL, all COS mappings defined for this border node
– For SCOPE=ONLY, all border node COS mappings for the default network.

Examples
Displaying border node COS mappings for the default network:
d net,bncosmap
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BNCOSMAP

Chapter 2. VTAM Operator Commands 47

DISPLAY BNCOSMAP
IST1321I TABLE FOR BNCOSMAP DEFAULT_NETID
IST1322I NON-NATIVE NATIVE
IST1323I COS1 COS2
IST1323I COS3 COS2
IST1323I COS4 COS5
IST314I END

Displaying all border node COS mappings:

d net,bncosmap,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BNCOSMAP
IST1321I TABLE FOR BNCOSMAP NETB
IST1322I NON-NATIVE NATIVE
IST1323I COSB3 COSC
IST1323I COSB2 COSB
IST1323I COSB1 COSA
IST924I -------------------------------------------------------------
IST1321I TABLE FOR BNCOSMAP NETC
IST1322I NON-NATIVE NATIVE
IST1323I COSC3 COSD
IST1323I COSC2 COSC
IST1323I COSC1 COSB
IST314I END

48 SNA Operation
 DISPLAY CDRMS

DISPLAY CDRMS Command

ÊÊ DISPLAY NET,CDRMS Ê
(1)
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
Ê ÊÍ
,MAX= * ALL
number_of_resources ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY CDRMS (cross-domain resource managers) command displays the
status of active cross-domain resource manager (CDRM) major nodes and their
subordinate minor nodes.

Chapter 2. VTAM Operator Commands 49

DISPLAY CDRMS
Note: To display cross-domain resource managers independently of the major
nodes that contain them, use the DISPLAY RSCLIST command with
IDTYPE=CDRMS.

Operands
ID=name
specifies the name of one or more active CDRM major nodes whose
subordinate resources are to be displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every CDRM major node in the network.
MAX
specifies the maximum number of CDRM minor nodes that VTAM displays for
this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of CDRM minor nodes to display for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer CDRM program minor nodes are found
than you have specified on MAX, VTAM displays only the CDRM minor
nodes that are found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable CDRM minor nodes within the specified major nodes (or within
all major nodes if the ID operand is omitted). If this display is undesirably
large, you can use SCOPE=ACTONLY or SCOPE=CONCT to further limit
the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all CDRM minor nodes in
an active state within the specified major nodes (or within all major nodes if
the ID operand is omitted). The display does not include CDRMs in pending
or connectable states. If no CDRMs are found in an active state, you can
use SCOPE=ACT to broaden the scope of the display to include those in
active, connectable, and pending states.

50 SNA Operation
 DISPLAY CDRMS
SCOPE=ACTSESS
specifies that information is to be displayed about all CDRM minor nodes
that are active with sessions within the specified major nodes (or within all
major nodes if the ID operand is omitted).
SCOPE=ALL
specifies that information is to be displayed about all CDRM minor nodes
(regardless of their status) within the specified major nodes (or within all
major nodes if the ID operand is omitted).
SCOPE=CONCT
specifies that information is to be displayed about all CDRM minor nodes in
a CONCT (connectable) state within the specified major nodes (or within all
major nodes if the ID operand is omitted). If no CDRMs are found in a
connectable state, you can use SCOPE=ACT to broaden the scope of the
display to include those in active, connectable, and pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive CDRM minor
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). If this display is undesirably large, you can use
SCOPE=INACTONLY or SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive CDRM minor
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). Resources in a RESET state are not included in the
SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending CDRM minor
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). A pending state is a transient state to or from the fully
active state.
SCOPE=RESET
specifies that information is to be displayed about all CDRM minor nodes in
a RESET state within the specified major nodes (or within all major nodes if
the ID operand is omitted).

Resulting Display
The resulting display shows:
v The name and status of the specified active CDRM major nodes (or all active
CDRM major nodes if the ID operand is omitted).
v For each active CDRM major node:
– The name, status, subarea number, element address, and network
identification is displayed for each minor node. This is limited to active,
inactive, or pending minor nodes if specified on the SCOPE operand.
– The network address within the gateway NCP used for the cross-network
SSCP-SSCP session is displayed if you are displaying a CDRM in another
network.

Examples
Displaying all CDRM major nodes and their minor nodes:

Chapter 2. VTAM Operator Commands 51

DISPLAY CDRMS
d net,cdrms
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRMS
IST089I CDRM1A TYPE = CDRM SEGMENT , ACTIV
IST1546I CDRM STATUS SUBAREA ELEMENT NETID SSCPID
IST1547I SSCP1A ACTIV 1 1 NETA 1
IST1547I SSCPAA NEVAC 10 1 NETA N/A
IST1547I SSCP2A NEVAC 2 1 NETA N/A
IST1547I SSCPBA NEVAC 11 1 NETA N/A
IST1547I SSCPCA NEVAC 12 1 NETA N/A
IST1547I SSCP7B ACTIV 5 1 NETB 7
IST1547I SSCP9C ACTIV 8 3 NETC 9
IST1454I 7 RESOURCE(S) DISPLAYED
IST314I END

Displaying a specific CDRM major node and its minor nodes:

d net,cdrms,id=cdrm1a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRMS
IST089I CDRM1A TYPE = CDRM SEGMENT , ACTIV
IST1546I CDRM STATUS SUBAREA ELEMENT NETID SSCPID
IST1547I SSCP1A ACTIV 1 1 NETA 1
IST1547I SSCPAA NEVAC 10 1 NETA N/A
IST1547I SSCP2A NEVAC 2 1 NETA N/A
IST1547I SSCPBA NEVAC 11 1 NETA N/A
IST1547I SSCPCA NEVAC 12 1 NETA N/A
IST1547I SSCP7B ACTIV 5 1 NETB 7
IST1547I SSCP9C ACTIV 8 3 NETC 9
IST1454I 7 RESOURCE(S) DISPLAYED
IST314I END

Displaying CDRM major nodes and their minor nodes, limiting output to 5
resources:
d net,cdrms,max=5
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRMS
IST089I CDRM1A TYPE = CDRM SEGMENT , ACTIV
IST1546I CDRM STATUS SUBAREA ELEMENT NETID SSCPID
IST1547I SSCP1A ACTIV 1 1 NETA 1
IST1547I SSCPAA NEVAC 10 1 NETA N/A
IST1547I SSCP2A NEVAC 2 1 NETA N/A
IST1547I SSCPBA NEVAC 11 1 NETA N/A
IST1547I SSCPCA NEVAC 12 1 NETA N/A
IST1454I 5 RESOURCE(S) DISPLAYED
IST314I END

52 SNA Operation
 DISPLAY CDRSCS

DISPLAY CDRSCS Command

ÊÊ DISPLAY NET,CDRSCS Ê
(1)
,ID= name
( name )

,MAX=DSPLYDEF_start_option_value
Ê Ê
,MAX= * ,NETID=
number_of_resources netid
*NONE

,SCOPE=ALL
Ê ÊÍ
ALL
,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Chapter 2. VTAM Operator Commands 53

DISPLAY CDRSCS
Purpose
The DISPLAY CDRSCS (cross-domain resources) command displays information
about cross-domain resources, including independent LUs.

Note: To display cross-domain resources independently of the major nodes that

contain them, use the DISPLAY RSCLIST command with IDTYPE=CDRSCS.

Operands
ID=name
specifies the name of one or more active CDRSC major nodes whose
subordinate resources are to be displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every CDRSC major node in the network.
MAX
specifies the maximum number of CDRSC minor nodes that VTAM displays for
this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of CDRSC minor nodes to display for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer CDRSC minor nodes are found than
you have specified on MAX, VTAM displays only the CDRSC minor nodes
that are found.
NETID
specifies the network identifier for which VTAM is to display CDRSCs.

If you do not specify the NETID operand, CDRSCs are displayed regardless of
their network.

If you specify the NETID operand, but do not identify a specific network (that is,
a value for netid is not entered), CDRSCs within the host network are
displayed.
NETID=netid
specifies that VTAM display CDRSCs within the indicated network.
NETID=*NONE
specifies that VTAM display only CDRSCs with unknown network identifiers.

54 SNA Operation
 DISPLAY CDRSCS
Note: While sessions exist between VTAM and a cross-domain resource
that was predefined without a network identifier, the resource is
displayed with its real network identifier. When all sessions with the
cross-domain resource have ended, the resource returns to having
an unknown network identifier.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable CDRSC minor nodes within the specified major nodes (or
within all major nodes if the ID operand is omitted). If this display is
undesirably large, you can use SCOPE=ACTONLY or SCOPE=CONCT to
further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all CDRSC minor nodes
in an active state within the specified major nodes (or within all major nodes
if the ID operand is omitted). The display does not include CDRSCs in
pending or connectable states. If no CDRSCs are found in an active state,
you can use SCOPE=ACT to broaden the scope of the display to include
those in active, connectable, and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all CDRSC minor nodes
that are active with sessions within the specified major nodes (or within all
major nodes if the ID operand is omitted).
SCOPE=ALL
specifies that information is to be displayed about all CDRSC minor nodes
(regardless of their status) within the specified major nodes (or within all
major nodes if the ID operand is omitted).
SCOPE=CONCT
specifies that information is to be displayed about all CDRSC minor nodes
in a CONCT (connectable) state within the specified major nodes (or within
all major nodes if the ID operand is omitted). If no CDRSCs are found in a
connectable state, you can use SCOPE=ACT to broaden the scope of the
display to include those in active, connectable, and pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive CDRSC minor
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). If this display is undesirably large, you can use
SCOPE=INACTONLY or SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive CDRSC minor
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). Resources in a RESET state are not included in the
SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending CDRSC minor

Chapter 2. VTAM Operator Commands 55

DISPLAY CDRSCS
nodes within the specified major nodes (or within all major nodes if the ID
operand is omitted). A pending state is a transient state to or from the fully
active state.
SCOPE=RESET
specifies that information is to be displayed about all CDRSC minor nodes
in a RESET state within the specified major nodes (or within all major
nodes if the ID operand is omitted).

Resulting Display
The resulting display shows:
v If ID is specified, the name and status of the specified CDRSC major node or
nodes. Inactive CDRSC major nodes are not known to VTAM and are therefore
not displayed.
v If ID is not specified, the name and status of each active CDRSC major node in
the domain. Inactive CDRSC major nodes are not known to VTAM and are
therefore not displayed.
v For each CDRSC major node, the name, status, owning CDRM, and NETID
(where applicable) of each subordinate CDRSC minor node (limited to active,
inactive, or pending minor nodes if specified on the SCOPE operand).

Examples
Displaying cross-domain resources for a specific network:
d net,cdrscs,netid=neta
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRSCS
IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
IST483I A04I0421 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0422 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0423 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I C23I92C5 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV
IST483I C25NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST1185I NAME = NETA.A04P885A - DIRECTORY ENTRY = REGISTERED EN
IST1185I NAME = NETA.A04P886A - DIRECTORY ENTRY = REGISTERED EN
IST1185I NAME = NETA.A04P888A - DIRECTORY ENTRY = REGISTERED EN
IST1185I NAME = NETY.A04P882A - DIRECTORY ENTRY = REGISTERED EN
IST314I END

Displaying a specific cross-domain resource major node and its subordinate

resources:
d net,cdrscs,id=istpdilu
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRSCS
IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
IST483I A31I3621 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3622 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3623 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3624 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3625 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3631 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3632 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3633 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3634 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I3635 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A31I4821 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88B3 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88B4 ACTIV , CDRM = ***NA***, NETID = ***NA***

56 SNA Operation
 DISPLAY CDRSCS
IST483I A03I88B5 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88C1 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88C2 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88C3 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88C4 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A03I88C5 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST314I END

Displaying all cross-domain resources:

d net,cdrscs
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRSCS
IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
IST483I A04I0421 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0422 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0423 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0424 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I A04I0425 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I C23I92C2 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I C23I92C3 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I C23I92C4 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST483I C23I92C5 ACTIV , CDRM = ***NA***, NETID = ***NA***
IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV
IST483I C25NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I B01NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I A81NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I A03D207F ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I C23D92CE ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D48CC ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D921D ACT/S----Y, CDRM = A01N , NETID = NETX
IST483I C23D527B ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D48CD ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D486B ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D486D ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D92AD ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I A03D203B ACT/S----Y, CDRM = A01N , NETID = NETZ
IST483I A03D167C ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A03D883D ACT/S----Y, CDRM = A01N , NETID = NETZ
IST483I C23D486E ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D48AC ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D52CD ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I A31D926C ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A31D48CC ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A04D209B ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I C23D527F ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C23D483F ACT/S----Y, CDRM = A01N , NETID = NETZ
IST483I C23D524F ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I C01NVLUC ACT/S----Y, CDRM = A01N , NETID = NETC
IST483I A02NVLUC ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I ECHO02A ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A50NVLUC ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A500N ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A02N ACT/S----Y, CDRM = A01N , NETID = NETA
IST314I END

Displaying cross-domain resources limiting output to 5 resources:

d net,cdrscs,max=5
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRSCS
IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
IST1358I NO QUALIFYING MATCHES
IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV
IST1358I NO QUALIFYING MATCHES
IST089I CDRSC1A TYPE = CDRSC SEGMENT , ACTIV
IST483I APPL8 ACTIV--S--, CDRM = SSCP1A , NETID = ***NA***
IST483I APPL9 NEVAC--S--, CDRM = SSCP1A , NETID = ***NA***

Chapter 2. VTAM Operator Commands 57

DISPLAY CDRSCS
IST483I L4A3278A ACTIV , CDRM = SSCP2A , NETID = NETA
IST483I L4A3279A ACTIV , CDRM = SSCP2A , NETID = NETA
IST483I L4A3767D ACTIV , CDRM = SSCP2A , NETID = NETA
IST1315I DISPLAY TRUNCATED AT MAX = 5
IST1454I 5 RESOURCE(S) DISPLAYED
IST314I END

58 SNA Operation
 DISPLAY CLSTRS

DISPLAY CLSTRS Command

ÊÊ DISPLAY NET,CLSTRS Ê
(1)
,ID= name
,

( » name )

,IDTYPE=* ,MAX=DSPLYDEF_start_option_value
Ê Ê
,IDTYPE= LCLSNA ,MAX= *
PUT45 number_of_resources
SWSEG
*

,SCOPE=ALL
Ê ÊÍ
,OWNER= host_name ALL
*NONE ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Chapter 2. VTAM Operator Commands 59

DISPLAY CLSTRS
Purpose
The DISPLAY CLSTRS (clusters) command displays the status of physical units
(PUs) subordinate to an NCP node, a local SNA node, or a switched subarea node.

Note: To display physical units independently of the major nodes that contain them,
use the DISPLAY RSCLIST command with IDTYPE=CLSTRS.

Operands
ID=name
specifies the name of one or more active NCP, local SNA, or switched major
nodes whose subordinate PUs are to be displayed.

If OWNER is also specified on this command, the value of ID must match the
name of an NCP major node.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every NCP, local SNA, and switched major node in the network.
IDTYPE
specifies the type of major node that the ID operand names. If several types of
resources share the same name, IDTYPE can be used to identify which
resource the command should act on. The default is IDTYPE=*.
IDTYPE=LCLSNA
displays only the subordinate PUs defined in local SNA major nodes.
IDTYPE=PUT45
displays only the subordinate PUs defined in PU type 4 and PU type 5
major nodes.
IDTYPE=SWSEG
displays only the subordinate PUs defined in switched major nodes.
IDTYPE=*
displays the subordinate PUs defined in NCP major nodes, local SNA major
nodes, and switched major nodes.
MAX
specifies the maximum number of PUs that VTAM displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of PUs to display for this command. The valid range is
1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output

60 SNA Operation
 DISPLAY CLSTRS
generated by the command. If fewer PUs are found than you have specified
on MAX, VTAM displays only the PUs that are found.
OWNER
specifies whether PUs defined with the OWNER operand are to be displayed.
This operand is only valid when the name or the wildcard value specified on the
ID operand matches the name of an NCP major node.
OWNER=host_name
specifies that only PUs whose owning SSCP (as determined by the
OWNER operand on the GROUP, LINE, or PU definition statements)
matches the host_name specified are to be displayed.
OWNER=*NONE
specifies that only PUs without an OWNER operand on the GROUP, LINE,
or PU definition statements are to be displayed.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable PUs within the specified major nodes (or within all NCP, local
SNA, and switched major nodes if the ID operand is omitted). The
information is displayed for the major node as well. If this display is
undesirably large, you can use SCOPE=ACTONLY or SCOPE=CONCT to
further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all PUs in an active state
within the specified major nodes (or within all NCP, local SNA, and switched
major nodes if the ID operand is omitted). The display does not include
PUs in pending or connectable states. If no PUs are found in an active
state, you can use SCOPE=ACT to broaden the scope of the display to
include those in active, connectable, and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all PUs that are active
with sessions within the specified major nodes (or within all NCP, local SNA,
and switched major nodes if the ID operand is omitted).
SCOPE=ALL
specifies that information is to be displayed about all PUs (regardless of
status) within the specified major nodes (or within all NCP, local SNA, and
switched major nodes if the ID operand is omitted). The information is
displayed for the major node as well.
SCOPE=CONCT
specifies that information is to be displayed about all PUs in a CONCT
(connectable) state within the specified major nodes (or within all NCP, local
SNA, and switched major nodes if the ID operand is omitted). If no PUs are
found in a connectable state, you can use SCOPE=ACT to broaden the
scope of the display to include those in active, connectable, and pending
states
SCOPE=INACT
specifies that information is to be displayed about all inactive PUs within the
specified major nodes (or within all NCP, local SNA, and switched major

Chapter 2. VTAM Operator Commands 61

DISPLAY CLSTRS
nodes if the ID operand is omitted). The information is displayed for the
major node as well. If this display is undesirably large, you can use
SCOPE=INACTONLY or SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive PUs within the
specified major nodes (or within all major nodes if the ID operand is
omitted). Resources in a RESET state are not included in the
SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending PUs within
the specified major nodes (or within all NCP, local SNA, and switched major
nodes if the ID operand is omitted). A pending state is a transient state to or
from the fully active state.
SCOPE=RESET
specifies that information is to be displayed about all PUs in a RESET state
within the specified major nodes (or within all NCP, local SNA, and switched
major nodes if the ID operand is omitted).

Resulting Display
The resulting display shows:
v For each active major node defining physical units, the major node name, status,
and type, the names of the active, inactive, pending, or all physical units (as
determined by the SCOPE operand) associated with the major node, and the
status and node type for each subordinate resource listed.
v For local SNA major nodes, the channel device name for every physical unit in
the local SNA major node.

Examples
Displaying all physical units (clusters) subordinate to a specific major node:
d net,clstrs,id=c23smnc
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CLUSTERS/PHYS UNITS
IST089I C23SMNC TYPE = SW SNA MAJ NODE , ACTIV
IST089I C23P922 TYPE = PU_T2 , CONCT
IST089I C23P923 TYPE = PU_T2 , CONCT
IST089I C23P925 TYPE = PU_T2 , CONCT
IST089I C23P926 TYPE = PU_T2 , CONCT
IST089I C23P928 TYPE = PU_T2 , CONCT
IST089I C23P929 TYPE = PU_T2 , CONCT
IST089I C23P92B TYPE = PU_T2 , CONCT
IST089I C23P92C TYPE = PU_T2 , CONCT
IST314I END

Displaying all physical units (clusters) owned by a specific SSCP:

d net,clstrs,owner=sscp1a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CLUSTERS/PHYS UNITS
IST089I NCP3AA1 TYPE = PU T4/5 , PCTD1
IST089I P3A3767A TYPE = PU_T1 , NEVAC
IST089I P3A3274A TYPE = PU_T2 , NEVAC
IST089I P3A4956A TYPE = PU_T2 , NEVAC
IST089I P3A3767D TYPE = PU_T1 , NEVAC
IST089I P3A4956G TYPE = PU_T2 , NEVAC
IST089I P3A3767C TYPE = PU_T1 , NEVAC
IST089I P3A4956E TYPE = PU_T2 , NEVAC

62 SNA Operation
 DISPLAY CLSTRS
IST089I P3A4956F TYPE = PU_T2 , NEVAC
IST089I P3A4956C TYPE = PU_T2 , NEVAC
IST089I P3A3274B TYPE = PU_T2 , NEVAC
IST089I P3A3767B TYPE = PU_T1 , NEVAC
IST089I P3A4956D TYPE = PU_T2 , NEVAC
IST089I P3A3274C TYPE = PU_T2 , NEVAC
IST314I END

Displaying all physical units (clusters):

d net,clstrs
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CLUSTERS/PHYS UNITS
IST089I ISTDSWMN TYPE = SW SNA MAJ NODE , ACTIV
IST089I A04P88A TYPE = PU_T2 , ACTIV---X-
IST089I A04P887 TYPE = PU_T2 , ACTIV---X-
IST089I A04P884 TYPE = PU_T2 , ACTIV---X-
IST089I A04P881 TYPE = PU_T2 , ACTIV---X-
IST089I C23SMNC TYPE = SW SNA MAJ NODE , ACTIV
IST089I C23P922 TYPE = PU_T2 , CONCT
IST089I C23P923 TYPE = PU_T2 , CONCT
IST089I C23P925 TYPE = PU_T2 , CONCT
IST089I C23P926 TYPE = PU_T2 , CONCT
IST089I C23P928 TYPE = PU_T2 , CONCT
IST089I C23P929 TYPE = PU_T2 , CONCT
IST089I C23P92B TYPE = PU_T2 , CONCT
IST089I C23P92C TYPE = PU_T2 , CONCT
IST089I A04SMNC TYPE = SW SNA MAJ NODE , ACTIV
IST089I A04P882 TYPE = PU_T2 , ACTIV--L--
IST089I A04P883 TYPE = PU_T2 , ACTIV--L--
IST089I A04P885 TYPE = PU_T2 , ACTIV--L--
IST089I A04P886 TYPE = PU_T2 , ACTIV--L--
IST089I A04P888 TYPE = PU_T2 , ACTIV--L--
IST089I A04P889 TYPE = PU_T2 , ACTIV--L--
IST089I A04P88B TYPE = PU_T2 , ACTIV--L--
IST089I A04P88C TYPE = PU_T2 , ACTIV--L--
IST089I SMNA01C TYPE = SW SNA MAJ NODE , ACTIV
IST089I A50NETNA TYPE = PU_T2 , ACTIV--L--
IST089I A02NETNA TYPE = PU_T2 , ACTIV--L--
IST089I A02NETNB TYPE = PU_T2 , ACTIV--L--
IST089I A0462ZC TYPE = PU T4/5 , ACTIV
IST089I A04C001 TYPE = PU_T2 , NEVAC
IST089I A04C002 TYPE = PU_T2 , NEVAC
IST089I A04C011 TYPE = PU_T2 , NEVAC
IST089I A04C012 TYPE = PU_T2 , NEVAC
IST089I A04C031 TYPE = PU_T2 , NEVAC
IST089I A04C032 TYPE = PU_T2 , NEVAC
IST089I A04NXXX TYPE = PU_T2 , NEVAC----T
IST089I A04P041 TYPE = PU_T2 , NEVAC
IST089I A04P042 TYPE = PU_T2 , NEVAC
IST089I A04P043 TYPE = PU_T2 , NEVAC
IST314I END

Displaying physical units (clusters), limiting output to 3 resources:

d net,clstrs,max=3
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CLUSTERS/PHYS UNITS
IST089I NCP3AA1 TYPE = PU T4/5 , PCTD1
IST089I P3A3767A TYPE = PU_T1 , NEVAC
IST089I P3A3274A TYPE = PU_T2 , NEVAC
IST1315I DISPLAY TRUNCATED AT MAX = 3
IST1454I 3 RESOURCE(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 63

DISPLAY CNOS

DISPLAY CNOS Command

ÊÊ DISPLAY NET,CNOS ,ID=appl_name ,LUNAME=lu_name Ê

Ê ÊÍ
,LOGMODE=logon_mode_name

Abbreviations
Operand Abbreviation
DISPLAY D
LOGMODE LOG
LUNAME LU

Purpose
The DISPLAY CNOS (change number of sessions) command displays LU 6.2
information associated with an application program and a partner LU and logon
mode.

Operands
ID=appl_name
specifies the name of the LU 6.2 application program about which the
information is requested. The value specified for appl_name cannot be a
network-qualified name.
LOGMODE=logon_mode_name
specifies the logon mode name for which the requested LU 6.2 information
applies. If you do not specify a logon mode name, SESSCAP, CONVSECL,
CONVSECP, and SYNCLVL are the only fields shown for the partner LU.
LUNAME=lu_name
specifies the name of the partner LU about which the LU 6.2 information is
requested. The name can be a network-qualified name in the form of
netid.luname.

If PARMS=(NQNAMES=NO) is coded on the ACB macro of the resource named

on the ID operand, and a network-qualified name is specified, the network
identifier is ignored.

If PARMS=(NQNAMES=YES) is coded on the ACB macro, luname can be

either a non-network-qualified name or a network-qualified name. If luname is a
non-network-qualified name, the command is processed against all LUs with
that non-network-qualified name across all networks. If luname is a
network-qualified name, the command is processed against the LU in the
specified network.

Resulting Display
The resulting VTAM display shows:
v The LU 6.2 application program name, LU name, and logon mode name of the
requested session

64 SNA Operation
 DISPLAY CNOS
v The negotiation values and security level values.

Examples
Displaying CNOS for all logon modes:
d net,cnos,id=appcap05,luname=appcap06
IST097I DISPLAY ACCEPTED
IST1001I ID= APPCAP05 LUNAME= NETA.APPCAP06
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I SYNCLVL =SYNCPT CONVCAP =FDX
IST314I END

Displaying CNOS for a specific logon mode:

d net,cnos,id=appcap05,luname=appcap06,logmode=batch
IST097I DISPLAY ACCEPTED
IST1001I ID= APPCAP05 LUNAME= NETA.APPCAP06 LOGMODE= BATCH
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I DRAINL =NO DRAINR =NO DDRAINL =NALLOW
IST1005I SESSCNT = 0 FREECNT = 0 QALLOC = 0
IST1005I WINLCNT = 0 WINRCNT = 0 AUTOSES = 0
IST1005I DRESPL =NALLOW RESP =***NA*** DELETE =NALLOW
IST1005I SYNCLVL =SYNCPT CONVCAP =FDX
IST1003I SESSLIM CNOS= 2 DEFINE= 2
IST1003I MINWINL CNOS= 1 DEFINE= 1
IST1003I MINWINR CNOS= 1 DEFINE= 1
IST314I END

Displaying CNOS for all logon modes and partner LU name is found in more than
one network:
d net,cnos,id=appcap05,luname=appcap06
IST097I DISPLAY ACCEPTED
IST1001I ID= APPCAP05 LUNAME= NETB.APPCAP06
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I SYNCLVL =SYNCPT CONVCAP =HDX
IST1001I ID= APPCAP05 LUNAME= NETA.APPCAP06
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I SYNCLVL =SYNCPT CONVCAP =HDX
IST314I END

Displaying CNOS for a specific logon mode and the partner LU is found in more
than one network:
d net,cnos,id=appcap05,luname=appcap06,logmode=batch
IST097I DISPLAY ACCEPTED
IST1001I ID= APPCAP05 LUNAME= NETB.APPCAP06 LOGMODE= BATCH
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I DRAINL =NO DRAINR =NO DDRAINL =NALLOW
IST1005I SESSCNT = 1 FREECNT = 0 QALLOC = 0
IST1005I WINLCNT = 1 WINRCNT = 0 AUTOSES = 0
IST1005I DRESPL =NALLOW RESP =***NA*** DELETE =NALLOW
IST1005I SYNCLVL =SYNCPT CONVCAP =HDX
IST1003I SESSLIM CNOS= 2 DEFINE= 2
IST1003I MINWINL CNOS= 1 DEFINE= 1
IST1003I MINWINR CNOS= 1 DEFINE= 1
IST1001I ID= APPCAP05 LUNAME= NETA.APPCAP06 LOGMODE= BATCH
IST1002I RCPRI=0000 RCSEC=0000
IST1005I SESSCAP =PARALLEL CONVSECL=AVPV CONVSECP=AVPV
IST1005I DRAINL =NO DRAINR =NO DDRAINL =NALLOW
IST1005I SESSCNT = 1 FREECNT = 0 QALLOC = 0

Chapter 2. VTAM Operator Commands 65

DISPLAY CNOS
IST1005I WINLCNT = 1 WINRCNT = 0 AUTOSES = 0
IST1005I DRESPL =NALLOW RESP =***NA*** DELETE =NALLOW
IST1005I SYNCLVL =SYNCPT CONVCAP =HDX
IST1003I SESSLIM CNOS= 2 DEFINE= 2
IST1003I MINWINL CNOS= 1 DEFINE= 1
IST1003I MINWINR CNOS= 1 DEFINE= 1
IST314I END

66 SNA Operation
 DISPLAY CONVID

DISPLAY CONVID Command

,ETIME=0
ÊÊ DISPLAY NET,CONVID ,ID=appl_name Ê
,ETIME=number_of_minutes

Ê ÊÍ
,LOGMODE=logon_mode_name ,LUNAME=lu_name

Abbreviations
Operand Abbreviation
DISPLAY D
LOGMODE LOG
LUNAME LU

Purpose
The DISPLAY CONVID (conversation ID) command provides information about
active conversations with the specified application program. You can limit display of
information to conversations that have had no activity for a specified period of time.

Note: This command causes VTAM to check every conversation and could have
an adverse effect on VTAM performance.

You can use this command during problem determination to view a record of
conversation information between logical unit (LU) partners.

Conversations that are in the process of allocating and deallocating are temporarily
suspended while this command is being processed. Conversations that are sending
or receiving continue to operate while this command is running.

Operands
ETIME=number_of_minutes
specifies the minimum amount of time that can elapse with no API activity
before VTAM displays its record of conversations between the LU partners.

For example, if you specify ETIME=5, VTAM displays only information about
conversations that have had no activity for at least 5 minutes.

You can specify 0–999 minutes as a value for ETIME. If you use 0 (the default),
VTAM displays a record of all conversations.
ID=appl_name
identifies the name of the LU 6.2 application to which the requested
conversation information applies. This value cannot be a network-qualified
name.
LOGMODE=logon_mode_name
specifies the logon mode name to which the requested conversation information
applies. Active conversations that use the specified logon mode name are
displayed.

Chapter 2. VTAM Operator Commands 67

DISPLAY CONVID
LUNAME=lu_name
specifies the name of the partner LU to which the requested conversation
information applies. Active conversations with the specified partner LU are
displayed. The name can be a network-qualified name in the form of
netid.luname.

If PARMS=(NQNAMES=NO) is coded on the ACB macro of the resource named

on the ID operand, and a network-qualified name is specified, the network
identifier is ignored.

If PARMS=(NQNAMES=YES) is coded on the ACB macro, luname can be

either a non-network-qualified name or a network-qualified name. If luname is a
non-network-qualified name, the command is processed against all LUs with
that non-network-qualified name across all networks. If luname is a
network-qualified name, the command is processed against the LU in the
specified network.

Resulting Display
The resulting VTAM display shows:
v The names of the partner LUs in the conversations
v Each partner LU’s logon mode name
v Each conversation’s identifier
v Each conversation’s session identifier
v The availability of HPDT services at the time the session was established
v Each conversation’s status
v Each conversation’s elapse time.

Examples
Displaying active conversations with a specific partner LU:
d net,convid,id=appcap05,luname=appcap06
IST097I DISPLAY ACCEPTED
IST1040I CONVERSATION(S) FOUND FOR APPCAP05
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000003, STATUS = F_SR, ETIME = 2
IST1009I SID = D5376DF41F2EDFF2, HPDT = NO
IST924I -------------------------------------------------------------
IST314I END

Displaying all active conversations for a specific LU:

d net,convid,id=appcap05
IST097I DISPLAY ACCEPTED
IST1040I CONVERSATION(S) FOUND FOR APPCAP05
IST1007I PARTNER = NETB.APPCAP07, LOGMODE = BATCH
IST1008I CONVID = 01000009, STATUS = SEND, ETIME = 2
IST1009I SID = E7F33883005B53C7, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000008, STATUS = SEND, ETIME = 2
IST1009I SID = E7F33883005B53C6, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000006, STATUS = SEND, ETIME = 4
IST1009I SID = E7F33883005B53C5, HPDT = YES
IST924I -------------------------------------------------------------
IST314I END

68 SNA Operation
 DISPLAY CONVID
Displaying active conversations for a specific logmode:
d net,convid,id=appcap05,logmode=interact
IST097I DISPLAY ACCEPTED
IST1040I CONVERSATION(S) FOUND FOR APPCAP05
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = INTERACT
IST1008I CONVID = 01000011, STATUS = SEND, ETIME = 10
IST1009I SID = EAABEEC32CD34A3E, HPDT = NO
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = INTERACT
IST1008I CONVID = 0100000C, STATUS = SEND, ETIME = 14
IST1009I SID = EAABEEC32CD34A3B, HPDT = NO
IST924I -------------------------------------------------------------
IST314I END

Displaying active conversations for a specific logmode and partner LU:

d net,convid,id=appcap05,luname=appcap06,logmode=batch
IST097I DISPLAY ACCEPTED
IST1040I CONVERSATION(S) FOUND FOR APPCAP05
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000008, STATUS = SEND, ETIME = 18
IST1009I SID = EAABEEC32CD34A39, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000006, STATUS = SEND, ETIME = 20
IST1009I SID = EAABEEC32CD34A38, HPDT = YES
IST924I -------------------------------------------------------------
IST314I END

Displaying active conversations with no API activity for more than 2 minutes and the
partner LU is found in more than one network:
d net,convid,id=appcap05,luname=appcap06,etime=2
IST097I DISPLAY ACCEPTED
IST1040I CONVERSATION(S) FOUND FOR APPCAP05
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = INTERACT
IST1008I CONVID = 01000011, STATUS = SEND, ETIME = 11
IST1009I SID = EAABEEC32CD34A3E, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = HOLLY
IST1008I CONVID = 0100000F, STATUS = SEND, ETIME = 13
IST1009I SID = EAABEEC32CD34A3D, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = INTERACT
IST1008I CONVID = 0100000C, STATUS = SEND, ETIME = 15
IST1009I SID = EAABEEC32CD34A3B, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETB.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000008, STATUS = SEND, ETIME = 18
IST1009I SID = EAABEEC32CD34A39, HPDT = YES
IST924I -------------------------------------------------------------
IST1007I PARTNER = NETA.APPCAP06, LOGMODE = BATCH
IST1008I CONVID = 01000006, STATUS = SEND, ETIME = 20
IST1009I SID = EAABEEC32CD34A38, HPDT = YES
IST924I -------------------------------------------------------------
IST314I END

Chapter 2. VTAM Operator Commands 69

DISPLAY COS

DISPLAY COS Command

ÊÊ DISPLAY NET,COS ÊÍ
,ID=pu_name ,NETID= *
netid

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY COS (class-of-service) command displays the class-of-service (COS)
table name for a particular network or all networks associated with a specified PU
type 4 or 5.

If a COS table is not defined for a network, VTAM displays the default table name
(ISTSDCOS). If the default table is not loaded, VTAM indicates that the default
algorithm will be used to determine the class of service.

Operands
ID=pu_name
identifies the physical unit type 4 or type 5 for which the COS table is displayed.
If pu_name is not specified, ID defaults to the host physical unit name specified
on the HOSTPU start option. If HOSTPU was not specified in the start option
list, then ISTPUS is used as the default.

The resource identified by pu_name must be active for the display to occur.

If an ID is specified, the results displayed are with respect to the issuing VTAM
host.
NETID
specifies whether the COS table for a particular network or all networks is
displayed. If omitted, NETID defaults to the network from which the command
was entered.

Note: If a model network is defined by using COPIES= as part of the network

definition, then *NETWORK is used as the network ID of the model
network for the DISPLAY COS command.
NETID=netid
displays the COS table for the named network.
NETID=*
displays the COS table for all networks.

Resulting Display
The resulting display shows the requested networks paired with the applicable COS
tables.

70 SNA Operation
 DISPLAY COS
Examples
Displaying a class-of-service table for a specific PU:
d net,cos,id=istpus
IST097I DISPLAY ACCEPTED
IST354I PU T4/5 MAJOR NODE = ISTPUS
IST862I NETID = NETA COSTABLE = ISTSDCOS
IST314I END

Chapter 2. VTAM Operator Commands 71

DISPLAY CSM

DISPLAY CSM Command

ÊÊ DISPLAY NET,CSM ÊÍ
,OWNERID= ALL
ownerid

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY CSM command allows you to monitor the use of storage managed by
the communications storage manager (CSM). You can use this command to
determine how much CSM storage is in use for ECSA and data space storage
pools. This command also provides information about specific applications that are
using CSM-managed storage pools. This command is routed to CSM so that VTAM
does not have to be operational when you issue this command.

Operands
OWNERID
specifies whether to display information about the amount of storage owned by
all owners or a specific owner. The owner ID is the half-word address space
identifier (ASID) of a CSM buffer owner. ASID values are in hexadecimal format
and range from 1 – 7FFF. If OWNERID is not specified, this command displays
the total storage allocated to the pool by storage pool source.
OWNERID=ALL
produces a display by each ownerid showing the amount of storage owned
in each storage pool and the cumulative total for each ownerid across all
pools.

Note: The sum of the total of the storage allocated to all users of a
particular pool may be greater than the total amount of storage
allocated to that pool. This is due to the existence of multiple
instances of a buffer created when an application program issues the
IVTCSM ASSIGN_BUFFER macro. The storage displayed for each
OWNERID indicates the amount of storage that must be freed by the
user to enable the storage to be returned to the buffer pool.
OWNERID=ownerid
specifies that the storage owned by the specified owner ID be displayed.
The cumulative total across all pools is also displayed.

Resulting Display
The resulting VTAM display shows:
v The size of a buffer residing in a data space
v The size of a buffer residing in ECSA
v If OWNERID is specified, the amount of storage allocated to the owner

72 SNA Operation
 DISPLAY CSM
v If OWNERID is not specified, information about storage usage for each buffer
pool
v The maximum current values for fixed and ECSA storage.

Storage amounts are displayed in units of K (kilobytes) or M (megabytes).

Examples
Displaying information about storage managed and used by CSM for all owners:
d net,csm
IVT5508I DISPLAY ACCEPTED
IVT5529I PROCESSING DISPLAY CSM COMMAND - OWNERID NOT SPECIFIED 042
IVT5530I BUFFER BUFFER
IVT5531I SIZE SOURCE INUSE FREE TOTAL
IVT5532I ------------------------------------------------------
IVT5533I 4K ECSA 0M 256K 256K
IVT5533I 16K ECSA 0M 0M 0M
IVT5533I 32K ECSA 0M 0M 0M
IVT5533I 60K ECSA 0M 0M 0M
IVT5534I 180K ECSA POOL DOES NOT EXIST
IVT5535I TOTAL ECSA 0M 256K 256K
IVT5532I ------------------------------------------------------
IVT5533I 4K DATA SPACE 0M 256K 256K
IVT5533I 16K DATA SPACE 0M 0M 0M
IVT5533I 32K DATA SPACE 0M 0M 0M
IVT5533I 60K DATA SPACE 0M 0M 0M
IVT5534I 180K DATA SPACE POOL DOES NOT EXIST
IVT5535I TOTAL DATA SPACE 0M 256K 256K
IVT5532I ------------------------------------------------------
IVT5536I TOTAL ALL SOURCES 0M 512K 512K
IVT5538I FIXED MAXIMUM = 120M FIXED CURRENT = 272K
IVT5539I ECSA MAXIMUM = 120M ECSA CURRENT = 365K
IVT5559I CSM DATA SPACE 1 NAME: 00000CSM
IVT5599I END

Displaying information about CSM storage allocated to a specific owner:

d net,csm,ownerid=01F6
IVT5508I DISPLAY ACCEPTED
IVT5549I PROCESSING DISPLAY CSM COMMAND - OWNERID SPECIFIED
IVT5530I BUFFER BUFFER
IVT5551I SIZE SOURCE STORAGE ALLOCATED TO OWNER
IVT5552I ------------------------------------------------------
IVT5553I 4K ECSA 256K
IVT5554I TOTAL ECSA 256K
IVT5553I 4K DATA SPACE 128K
IVT5554I TOTAL DATA SPACE 128K
IVT5556I TOTAL FOR OWNERID 384K
IVT5557I OWNERID: ASID = 001A JOBNAME = VTAMAPPL
IVT5599I END

Displaying information about CSM storage allocated to all owners:

d net,csm,ownerid=all
IVT5508I DISPLAY ACCEPTED
IVT5549I PROCESSING DISPLAY CSM COMMAND - OWNERID SPECIFIED
IVT5530I BUFFER BUFFER
IVT5551I SIZE SOURCE STORAGE ALLOCATED TO OWNER
IVT5532I ------------------------------------------------------
IVT5553I 4K ECSA 256K
IVT5554I TOTAL ECSA 256K
IVT5553I 4K DATA SPACE 128K
IVT5554I TOTAL DATA SPACE 128K
IVT5556I TOTAL FOR OWNERID 384K
IVT5557I OWNERID: ASID = 001A JOBNAME = VTAMAPPL

Chapter 2. VTAM Operator Commands 73

DISPLAY CSM
IVT5532I ------------------------------------------------------
IVT5530I BUFFER BUFFER
IVT5551I SIZE SOURCE STORAGE ALLOCATED TO OWNER
IVT5532I ------------------------------------------------------
IVT5553I 4K DATA SPACE 128K
IVT5553I 16K DATA SPACE 1M
IVT5554I TOTAL DATA SPACE 1M
IVT5556I TOTAL FOR OWNERID 1M
IVT5557I OWNERID: ASID = 001B JOBNAME = VTAMAPPL
IVT5599I END

74 SNA Operation
 DISPLAY DIRECTRY

DISPLAY DIRECTRY Command

Display information about a resource:

,SCOPE=ONLY
ÊÊ DISPLAY NET,DIRECTRY ,ID=name ÊÍ
,SCOPE= ALL
ONLY
NSEARCH

Display a resource name in any network:

,MAX=DSPLYDEF_start_option_value
ÊÊ DISPLAY NET,DIRECTRY ,ID=*.name Ê
,MAX= *
number_of_resources

,SCOPE=ONLY
Ê ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY DIRECTRY (directory) command displays information from the
directory database about a resource and the resources that it serves and owns. For
example, you can display a network node along with the end nodes that it serves
and the LUs that it owns. This command is valid only when it is issued at a network
node or an interchange node.

Operands
ID=resource_name
specifies the name of a network node, end node, or LU in the directory
database. The resource name can be network-qualified. If you do not specify
the network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify * (or *NETWORK) as the network ID portion of a

network-qualified name. The * is useful for displaying a resource for which you
do not know the network ID. The * is also useful for displaying several
resources with the same name that are found in multiple networks, provided
that you also specify the MAX operand on the command.

Chapter 2. VTAM Operator Commands 75

DISPLAY DIRECTRY
MAX
specifies the maximum number of resources to display when the resource name
on the ID operand is specified as being in “any network”. That is, the network
ID portion of the network-qualified resource name is specified as * (or
*NETWORK). For example, ID=*.a01n can be specified. MAX is valid only when
an “any network” resource name is specified on the ID operand.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the maximum number of resources that VTAM displays for this
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

The resource name might exist in more networks than the number you
specify on the MAX operand. However, VTAM searches only for the number
of instances that you have specified. When that number is found, VTAM
does not search any further. This saves processing time for the command
and gives you control over the amount of display output generated by the
command. If fewer resources are found than you have specified on MAX,
VTAM displays only the resources that are found.
SCOPE
specifies the desired scope of the display.
SCOPE=ALL
displays information for the resource specified on the ID operand and the
resources it serves or owns, if any. If the specified resource is a network
node, VTAM displays information about the network node, the end nodes it
serves, and the LUs it owns. If the specified resource is an end node,
VTAM displays information about the end node and the LUs it serves. If the
specified resource is an LU, the display output is the same for SCOPE=ALL
and SCOPE=ONLY.

SCOPE=ALL is not valid if you specify ID=*.name.

Attention: In a large network, displaying a network node or end node with

SCOPE=ALL might generate an undesirably large display.
SCOPE=NSEARCH
specifies that a network search is to be performed for the resource
specified on the ID operand. The command returns all instances of the
resource in the local domain and the first instance where the resource is
found in other domains and subnetworks. The network search uses all
possible search types (subarea, adjacent SSCP list, central directory server,
broadcast, and cross-subnetwork) to find a resource that may go
undetected by the search logic of individual session requests.
SCOPE=ONLY
displays information only for the resource specified on the ID operand.

Resulting Display
The resulting VTAM display shows:

76 SNA Operation
 DISPLAY DIRECTRY
v For SCOPE=ONLY, the entry type (registered, dynamic, or defined), the resource
type (network node, end node, or LU), the name of the owning CP, and the name
of the network node server.
v For SCOPE=ALL, the same information as SCOPE=ONLY, and additionally, the
name, entry type, and resource type of the served end nodes and owned LUs.
v For SCOPE=NSEARCH, the network-qualified name of the resource specified by
the ID operand, the owning control point name, the network node server as it is
known in the native subnetwork, and the found type.

If the resource type that is displayed is EN, the node might actually be a network
node, end node, or SSCP. This is because in a mixed APPN and subarea network,
CPs and SSCPs that are found in or through a subarea network are represented in
this host (the host from which you are issuing this command) as end nodes that are
served by the interchange node through which the resource was found.

The DISPLAY DIRECTRY command might show a resource name appearing in

several networks even though the resource actually exists in only one network. This
can happen if intermediate SSCPs are pre-V4R1 and they pass only the
8-character resource name. The real network ID is therefore lost and other network
IDs might be subsequently assumed.

Examples
Displaying an end node with SCOPE=ALL:
d net,directry,id=neta.sscp1a,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = DIRECTORY
IST1186I DIRECTORY ENTRY = REGISTERED EN
IST1184I CPNAME = NETA.SSCP1A NETSRVR = NETD.SSCP2A
IST1185I NAME = NETB.ECHOB91 - DIRECTORY ENTRY = REGISTERED LU
IST1185I NAME = NETB.ECHOB92 - DIRECTORY ENTRY = REGISTERED LU
IST1185I NAME = NETA.NMVTAPPL - DIRECTORY ENTRY = REGISTERED LU
IST1185I NAME = NETA.APPL2V - DIRECTORY ENTRY = REGISTERED LU
IST1185I NAME = NETA.APPL1V - DIRECTORY ENTRY = REGISTERED LU
IST1185I NAME = NETA.TSO1 - DIRECTORY ENTRY = REGISTERED LU
IST314I END

Displaying an end node with SCOPE=ONLY:

d net,directry,id=neta.sscp1a,scope=only
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = DIRECTORY
IST1186I DIRECTORY ENTRY = REGISTERED EN
IST1184I CPNAME = NETA.SSCP1A NETSRVR = NETD.SSCP2A
IST314I END

Displaying an LU:
d net,directry,id=neta.lu1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = DIRECTORY
IST1186I DIRECTORY ENTRY = REGISTERED LU
IST1184I CPNAME = NETA.SSCP1A NETSRVR = NETD.SSCP2A
IST314I END

Displaying the results of a network search:

d net,directry,id=lu1,scope=ns
IST350I DISPLAY TYPE = NETWORK SEARCH
IST1427I NAME = NETA.LU1 FOUND TYPE = OWNER
IST1184I CPNAME = NETA.NN3 - NETSRVR = ***NA***
IST924I -------------------------------------------------------------

Chapter 2. VTAM Operator Commands 77

DISPLAY DIRECTRY
IST1427I NAME = NETA.LU1 FOUND TYPE = SURROGATE
IST1184I CPNAME = NETA.NN1 - NETSRVR = ***NA***
IST924I -------------------------------------------------------------
IST1427I NAME = NETA.LU1 FOUND TYPE = WILDCARD
IST1184I CPNAME = NETA.NN2 - NETSRVR = ***NA***
IST314I END

78 SNA Operation
 DISPLAY DISK

DISPLAY DISK Command

ÊÊ DISPLAY NET,DISK ,ID=ncp_name ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY DISK command provides information about an IBM 3720 or 3745
Communication Controller’s disk contents.

The DISPLAY DISK command displays the following information about the contents
of IBM 3720 and 3745 Communication Controller external disk storage:
v Information about each load module, including:
– Load module name
– Date and time the load module was stored on disk
– Stability of the load module (stored, storing, or suspended)
– Indication of whether a load module on disk is the same as the load module
currently active in the communication controller
– Module name, requested IPL time, and estimated IPL time (if IPL was
specified).
v Information regarding dumps, including:
– Dump name
– Date and time the dump was stored on disk.

Note: Dump information is not displayed until the complete dump has been
stored on the hard disk. If you do not receive dump information, retry the
command at a later time.
v An indication of whether the load module is coded to receive automatic IPL.
This is determined by the value of Auto Dump/Load, which controls automatic
dumping and reloading of an NCP to or from the hard disk in the event of an
NCP abend. See the DUMPLOAD operand on the VARY ACT command on page
421 for more information.

Operands
ID=ncp_name
identifies the name of the NCP currently active in the IBM 3720 or 3745
Communication Controller. The contents of that communication controller’s
external disk storage are displayed.

Note: Although the IBM 3745-410 Communication Controller disk can contain
up to four load modules and two dumps, the maximum per CCU is two
load modules and one dump. DISPLAY DISK displays only the 3745
storage relative to the NCP specified in the ID operand.

Chapter 2. VTAM Operator Commands 79

DISPLAY DISK
Resulting Display
The resulting display provides load module and dump information. Load module and
dump source are not provided. To view dump source, use the DISPLAY NCPSTOR
command, shown in the “DISPLAY NCPSTOR Command” on page 143.

Examples
Displaying a disk containing a load module:
d net,disk,id=a0362zc
IST097I DISPLAY ACCEPTED
IST951I DISPLAY DISK INFORMATION FOR A0362ZC
IST954I LOAD MODULE DATE TIME STORE STATUS
IST955I A04AT 02/06/92 15:11:54 STORED
IST965I AUTO DUMP/LOAD: NO
IST314I END

Displaying a disk containing a dump and two load modules:

d net,disk,id=a0362zc
IST097I DISPLAY ACCEPTED
IST951I DISPLAY DISK INFORMATION FOR A0362ZC
IST952I DUMP NAME DATE TIME
IST953I A0362ZC 09/25/92 10:30:52
IST924I -------------------------------------------------------------
IST954I LOAD MODULE DATE TIME STORE STATUS ACTIVE
IST955I A04AT 02/06/92 15:11:54 STORED NO
IST955I A0362ZC 09/25/92 10:23:43 STORED YES
IST965I AUTO DUMP/LOAD: YES
IST314I END

80 SNA Operation
 DISPLAY DLURS

DISPLAY DLURS Command

ÊÊ DISPLAY NET,DLURS ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
DLURS DLUR

Purpose
The DISPLAY DLURS (dependent LU requesters) command displays all DLURs for
which this host acts as dependent LU server (DLUS). Only DLURs that have a
CPSVRMGR session with the host are displayed. The host (the DLUS) always
sends data on a contention-winner session and receives data on a contention-loser
session. Likewise, the DLUR sends data on a contention-winner session and
receives data on a contention-loser session.

This command is valid only when it is issued at a network node or an interchange

node.

Resulting Display
The resulting display shows:
v The name of each DLUR
v The status of each end of the CPSVRMGR session. Pending active and pending
inactive states should be temporary. If the session remains in pending active or
pending inactive state, it might be hung.

Examples
Displaying dependent LU requesters:
d net,dlurs
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = DLURS
IST1352I DLUR NAME DLUS CONWINNER STATE DLUS CONLOSER STATE
IST1353I NETA.NNCPA1 ACTIVE ACTIVE
IST314I END

Chapter 2. VTAM Operator Commands 81

DISPLAY EXIT

DISPLAY EXIT Command

,ID=*
ÊÊ DISPLAY NET,EXIT Ê
,ID= *
exit_name

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY EXIT command displays the name, exit level, module name, and
status of installation-wide exit routines.

Operands
ID specifies which installation-wide exit routine to display.
ID=exit_name
specifies one of the following installation-wide exit routines:
ISTCMMND
Command verification exit routine
ISTEXCAA
Session management exit routine
ISTEXCCS
Configuration services XID exit routine
ISTEXCDM
Directory services management exit routine
ISTEXCGR
Generic resource resolution exit routine
ISTEXCPM
Performance monitor exit routine
ISTEXCSD
Selection of definitions for dependent logical units (SDDLU) exit
routine
ISTEXCUV
USERVAR exit routine
ISTEXCVR
Virtual route selection exit routine
ID=*
specifies all installation-wide exit routines.

82 SNA Operation
 DISPLAY EXIT
MAX
specifies the maximum number of installation-wide exit routines that VTAM
displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of installation-wide exit routines to display for this
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer installation-wide exit routines are found
than you have specified on MAX, VTAM displays only the installation-wide
exit routines that are found.

Resulting Display
The resulting display shows the exit routine name, the exit level, the module name
for the exit, and the status of the exit at the time the command was issued.

If ISTEXCAA is specified on the ID operand and the exit is active, the resulting
display also shows the active functions of the session management exit routine.

Note: For ISTEXCPM, the base exit instance is always displayed regardless of its
status, and is displayed before any multiple exit. Multiple exit instances are
not displayed if they are inactive.

See the OS/390 eNetwork Communications Server: SNA Customization for

information about the exit level.

Examples
Displaying all installation-wide exit routines:
d net,exit
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EXIT
IST1250I NAME LEVEL MODULE STATUS
IST1251I ISTCMMND ***NA*** INACTIVE
IST1251I ISTEXCUV ***NA*** ISTEXCUV ACTIVE
IST1251I ISTEXCCS ***NA*** ISTEXCCS ACTIVE
IST1251I ISTEXCSD ***NA*** ISTEXCSD ACTIVE
IST1251I ISTEXCAA ***NA*** INACTIVE
IST1251I ISTEXCVR ***NA*** INACTIVE
IST1251I ISTEXCPM ***NA*** INACTIVE
IST1251I ISTEXCDM ***NA*** INACTIVE
IST1251I ISTEXCGR ***NA*** ISTEXCGR ACTIVE
IST314I END

Displaying the ISTEXCPM installation-wide exit routine:

d net,exit,id=istexcpm
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EXIT
IST1250I NAME LEVEL MODULE STATUS

Chapter 2. VTAM Operator Commands 83

DISPLAY EXIT
IST1251I ISTEXCPM ***NA*** INACTIVE
IST1251I ISTEXCPM ***NA*** P1 ACTIVE
IST1251I ISTEXCPM ***NA*** P2 ACTIVE
IST1251I ISTEXCPM ***NA*** P3 ACTIVE
IST314I END

Displaying the ISTEXCAA installation-wide exit routine:

d net,exit,id=istexcaa
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EXIT
IST1250I NAME LEVEL MODULE STATUS
IST1251I ISTEXCAA ***NA*** ISTEXCAA ACTIVE
IST199I OPTIONS = BEGIN INITAUTH SECAUTH ACCTING GWPATH END
IST199I OPTIONS = XRF ADJSSCP ADJ_DSRL INITA_IO ALIAS ALS
IST199I OPTIONS = ALS_DSRL ALS_CDRS
IST314I END

84 SNA Operation
 DISPLAY GROUPS

DISPLAY GROUPS Command

ÊÊ DISPLAY NET,GROUPS Ê
(1)
,ID= name
( name )

,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
Ê ÊÍ
,MAX= * ALL
number_of_resources ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY GROUPS command provides information about line groups.

Note: To display line groups independently of the major nodes that contain them,
use the DISPLAY RSCLIST command with IDTYPE=GROUPS.

Chapter 2. VTAM Operator Commands 85

DISPLAY GROUPS
Operands
ID=name
specifies the name of one or more active NCP, channel-attachment, or XCA
major nodes whose subordinate line groups are to be displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every NCP, channel-attachment, and XCA major node in the
network.
MAX
specifies the maximum number of line groups that VTAM displays for this
command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of line groups that VTAM displays for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer line groups are found than you have
specified on MAX, VTAM displays only the line groups that are found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable line groups within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted). If
this display is undesirably large, you can use SCOPE=ACTONLY or
SCOPE=CONCT to further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all line groups in an
active state within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).
The display does not include line groups in pending or connectable states.
If no line groups are found in an active state, you can use SCOPE=ACT to
broaden the scope of the display to include those in active, connectable,
and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all line groups that are
active with sessions within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).

86 SNA Operation
 DISPLAY GROUPS
SCOPE=ALL
specifies that information is to be displayed about all line groups (regardless
of status) within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).
SCOPE=CONCT
specifies that information is to be displayed about all line groups in a
CONCT (connectable) state within the specified major nodes (or within all
NCP, channel-attachment, and XCA major nodes if the ID operand is
omitted). If no line groups are found in a connectable state, you can use
SCOPE=ACT to broaden the scope of the display to include those in active,
connectable, and pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive line groups
within the specified major nodes (or within all NCP, channel-attachment, and
XCA major nodes if the ID operand is omitted). If this display is undesirably
large, you can use SCOPE=INACTONLY or SCOPE=RESET to further limit
the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive line groups
within the specified major nodes (or within all major nodes if the ID operand
is omitted). Resources in a RESET state are not included in the
SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending line groups
within the specified major nodes (or within all NCP, channel-attachment, and
XCA major nodes if the ID operand is omitted). A pending state is a
transient state to or from the fully active state.
SCOPE=RESET
specifies that information is to be displayed about all line groups in a
RESET state within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).

Resulting Display
The resulting display lists the group’s major node with its type and status, and the
name, type, and status of each line group subordinate to the major node.

Examples
Displaying all line groups:
d net,groups
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = GROUPS
IST089I ISTPUS TYPE = PU T4/5 , ACTIV
IST089I ISTGROUP TYPE = LINE GROUP , ACTIV
IST089I A0462ZC TYPE = PU T4/5 , ACTIV
IST089I A04LBNNB TYPE = LINE GROUP , ACTIV
IST089I A04XNPAX TYPE = LINE GROUP , ACTIV
IST089I A04DBNNS TYPE = LINE GROUP , ACTIV
IST089I A04LBNNS TYPE = LINE GROUP , ACTIV
IST089I A04GPRI TYPE = LINE GROUP , ACTIV
IST089I A04GSEC TYPE = LINE GROUP , ACTIV
IST089I A04LINNS TYPE = LINE GROUP , ACTIV
IST089I A04BPGRP TYPE = LINE GROUP , ACTIV
IST089I A04BLG1 TYPE = LINE GROUP , ACTIV

Chapter 2. VTAM Operator Commands 87

DISPLAY GROUPS
IST089I A04BLG2 TYPE = LINE GROUP , ACTIV
IST089I A04XCA0 TYPE = LINE GROUP , ACTIV
IST089I C2362ZC TYPE = PU T4/5 , ACTIV
IST172I NO GROUPS EXIST
IST314I END

Displaying line groups within a specific major node:

d net,groups,id=a0362zc
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = GROUPS
IST089I A0362ZC TYPE = PU T4/5 , ACTIV
IST089I A03LBNNB TYPE = LINE GROUP , ACTIV
IST089I A03XNPAX TYPE = LINE GROUP , ACTIV
IST089I A03L56KP TYPE = LINE GROUP , ACTIV
IST089I A03LBNNS TYPE = LINE GROUP , ACTIV
IST089I A03FID2 TYPE = LINE GROUP , ACTIV
IST089I A03BPGRP TYPE = LINE GROUP , ACTIV
IST089I A03BLG1 TYPE = LINE GROUP , ACTIV
IST089I A03BLG2 TYPE = LINE GROUP , ACTIV
IST089I A03XCA0 TYPE = LINE GROUP , ACTIV
IST314I END

Displaying line groups, limiting output to 3 resources:

d net,groups,max=3
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = GROUPS
IST089I ISTPUS TYPE = PU T4/5 , ACTIV
IST089I ISTGROUP TYPE = LINE GROUP , ACTIV
IST089I NCP3AA1 TYPE = PU T4/5 , PCTD1
IST089I GRP3A1 TYPE = LINE GROUP , NEVAC
IST089I GRP3A6 TYPE = LINE GROUP , NEVAC
IST1315I DISPLAY TRUNCATED AT MAX = 3
IST1454I 3 RESOURCE(S) DISPLAYED
IST314I END

88 SNA Operation
 DISPLAY ID

DISPLAY ID Command
Display a resource:

,IDTYPE=RESOURCE
ÊÊ DISPLAY NET,ID=name Ê
,IDTYPE= CDRM ,NETID=netid
CP
DIRECTRY
GENERIC
LUALIAS
RESOURCE
SHADOW
SSCP
USERVAR
XCFCP

,SCOPE=ONLY
Ê ÊÍ
ALL
,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
ONLY
PENDING
RESET

Display a resource name in any network:

,IDTYPE=RESOURCE
ÊÊ DISPLAY NET,ID=*.name Ê
,IDTYPE= DIRECTRY
RESOURCE

,MAX=1 ,SCOPE=ONLY
Ê ÊÍ
,MAX=number_of_resources ALL
,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
ONLY
PENDING
RESET

| Display a resource name using an IP address:

Chapter 2. VTAM Operator Commands 89

DISPLAY ID
ÊÊ DISPLAY NET,ID=ipaddress,IDTYPE=IPADDR ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=ONLY NONE or N
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY ID command provides information about a particular major node,
minor node, or directory entry. Additional information can be displayed about the
node’s subordinate resources.

Note: This command applies only to active major nodes and minor nodes within
active major nodes.

Inactive subarea nodes (for example, NCP major nodes) that have been contacted
by VTAM as a result of the activation of a cross-subarea link station can be
displayed, if the name of the given subarea node is known to VTAM. Both the NCP
being displayed and the NCP containing the link station must be an NCP V1R3 or
later release level. In all other cases, inactive major nodes and their minor nodes
are not known to VTAM and are therefore not displayed.

When the operator specifies:

v A switched line, the display indicates whether the line is dial-in, dial-out, or both
dial-in and dial-out. For a dial-in line, the answer mode is indicated.
v An application program minor node or LU name, the associated USS, interpret,
and logon-mode table names and the default logon-mode entry are displayed.

Note: Specifying ISTNOP, the name of the application program that represents
the network operator, also displays the names of the message-flooding
prevention table and the session awareness (SAW) data filter table.
v An NCP or host physical unit name, the following are displayed:
– The name and status of the associated dynamic path update members
– The load module name of the NCP that was loaded (if different from the NCP
PU name)

90 SNA Operation
 DISPLAY ID
– An indication of whether a nondisruptive load (MODIFY LOAD) is currently in
progress
– An indication of whether an NCP, MOSS, or CSP dump transfer (MODIFY
DUMP) is currently in progress.
v The name of a FRSESET definition statement, a FRSESET display is issued.
The display includes a message that shows how the FRSESET was defined,
statically or dynamically. (Statically means that it was included in the NCP
generation.)
v An application program minor node, the compression-level values are displayed.
v An application program, LU, or cross-domain resource name, the security data
for data encryption and message authentication are displayed.

Operands
ID=name
specifies the name of a major node, minor node, USERVAR, generic resource
name, LUALIAS, or resource in the directory database.

The name can be a network-qualified name. Regardless of whether you specify

a network-qualified name on the ID operand, the resource name in the display
output is network-qualified only for application programs, SSCPs, CDRSCs, and
LUs. The resource name in the display output is not network-qualified for any
other type of resource.

To display information about a dynamic XCF local SNA PU representing the

connection to another VTAM, you can specify one of the following:
v The name of the PU
v The CP name of the other VTAM with IDTYPE=XCFCP.
Notes:
1. If the name is an NCP major node, the name used must be the name
specified on the ID operand when the NCP was activated. If PUNAME was
specified on the BUILD definition statement, then name is the PUNAME.
2. If the name is an application program in this domain, the ID operand can
specify either the application program minor node name or the name under
which the application program opened its ACB.
3. For an application program minor node, you can specify the name of a
conventionally defined application program, a model application program, or
a dynamic application program built from a model application program
definition.
You can use wildcard characters in the name you specify. The use of
wildcard characters on the ID operand of the DISPLAY ID command does
not depend on the value of the DSPLYWLD start option. Unlike wildcard
characters in other commands, the wildcard characters you specify on the
ID operand of the DISPLAY ID command do not represent unspecified
characters. They are interpreted as the actual characters, * and ?.
Therefore, if you specify DISPLAY ID=APPL*, VTAM will display information
about the model application program definition named APPL*, but it will not
display information about any other application programs whose names
begin with APPL, followed by zero to four valid characters in length. It will
also not display information about any dynamic application programs built
from the model application program definition named APPL*.
In other words, using wildcard characters in the name you specify on the ID
operand of the DISPLAY ID command will result in the display of at most

Chapter 2. VTAM Operator Commands 91

 DISPLAY ID
one model application program. If you want to display information about all
application programs whose names match a pattern established by the
placement of wildcard characters, use the DISPLAY RSCLIST command.
4. For a CDRM, you can specify a network-qualified name, but this does not
remove the restriction that the non-network-qualified CDRM name must be
unique across networks.
5. If the name is a non-network-qualified CDRSC, VTAM will use the network
ID of the host from which the command is issued. If two or more CDRSCs
exist with the same resource name, but different network identifiers, and
DISPLAY ID=non-network-qualified_name is issued, then one of the
following occurs:
v Only one CDRSC is displayed. The displayed CDRSC is either:
– The one that has been defined with VTAM’s network identifier, or
– The one that has been defined as cross-network, but specified with
NQNMODE=NAME, either on its CDRSC definition or by the
NQNMODE start option.
v None of the CDRSCs will be displayed if they are all specified with
NQNMODE=NQNAME, either on their CDRSC definitions or by the
NQNMODE start option.
6. If you specify a non-network-qualified USERVAR name, VTAM uses the
network ID of the host from which you issue the command.
7. You can specify * (or *NETWORK) as the network ID portion of a
network-qualified name. The * is useful for displaying a resource for which
you do not know the network ID. The * is also useful for displaying several
resources with the same name that are found in multiple networks, provided
that you also specify the MAX operand on the command.
8. If the name is a generic resource name, the output will list all the members
known by that generic resource name.
| 9. If the name is a TN3270 client IP address in dotted decimal form (for
| example, ID=192.5.48.122) and there is an associated CS/390 Telnet server
| APPL or LU minor resource name, it is displayed.
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE can be used to identify which
resource the command should act on. IDTYPE differs from MAX in that IDTYPE
displays several representations of the same resource, whereas MAX displays
several different resources with the same name.
IDTYPE=CDRM
displays information only about the SSCP (represented as a CDRM).
IDTYPE=CP
displays information only about the host CP (represented as an application)
or an adjacent CP (represented as a CDRSC).
IDTYPE=DIRECTRY
displays information from the directory database for the specified resource.
The DISPLAY ID command with IDTYPE=DIRECTRY is valid only when it is
issued at a network node or an interchange node.
IDTYPE=GENERIC
displays the names of application program network names that are also
generic resources.

92 SNA Operation
 DISPLAY ID
| IDTYPE=IPADDR
| displays the IP address of the currently connected TN3270 client
| applications and LUs. The IP address accepts a fully-qualified dotted
| decimal format.

| Note: The ID keyword and IDTYPE=IPADDR are both required.

IDTYPE=LUALIAS
displays information only about the CDRSC whose name is associated with
the LUALIAS. If a network-qualified name is specified, VTAM does not
search for an LUALIAS with that resource name. For more information on
CDRSCs that are defined with an LUALIAS, see the OS/390 eNetwork
Communications Server: SNA Resource Definition Reference.
IDTYPE=RESOURCE
displays information about the resource named on the ID operand. VTAM
searches for the resource in the following order:
1. VTAM searches for an SSCP (CDRM), a host CP (application), or an
adjacent CP (CDRSC) by the name specified on the ID operand and
displays information for any or all of these resources it finds. If the
resource is found and it is not the host CP, and you are issuing this
command at a network node or interchange node, the display includes
information from the directory database.
2. If VTAM does not find an SSCP, a host CP, or an adjacent CP, it
searches for a resource with the name specified on the ID operand and
displays information for the resource, if it finds it. If the resource is a
CDRSC, and you are issuing this command at a network node or
interchange node, the display includes information from the directory
database.
3. If VTAM does not find a resource by that name, it searches for a
USERVAR with the name specified on the ID operand and displays
information for the resource, if it finds it.
4. If VTAM does not find a USERVAR by that name, or a USERVAR is
found but the resource defined as the value of the USERVAR is not
found, it searches for an LUALIAS with the name specified on the ID
operand and displays information for the CDRSC, if it finds it.
5. If no resource is found with the name specified on the ID operand, and
you are issuing this command at a network node or interchange node,
VTAM displays information about the resource from the directory
database, if it finds it.
6. If no resource is found and no entry exists in the directory database
with the specified name, the command fails.
IDTYPE=SHADOW
displays information only about a shadow resource, if it exists. Included in
the information displayed is the real resource that caused the displayed
resource to become a shadow resource.

For more information on shadow resources, see the OS/390 eNetwork

Communications Server: SNA Network Implementation Guide
IDTYPE=SSCP
displays information only about the SSCP (represented as a CDRM).
IDTYPE=USERVAR
displays information only about the resource whose name is associated with
the USERVAR.

Chapter 2. VTAM Operator Commands 93

DISPLAY ID
IDTYPE=XCFCP
displays information only about the dynamic XCF local SNA PU
representing the connection to another VTAM in the XCF group, when the
ID operand specifies the CP name of the other VTAM.
MAX=number_of_resources
specifies the maximum number of resources to display when the resource name
on the ID operand is specified as being in “any network”. That is, the network
ID portion of the network-qualified resource name is specified as * (or
*NETWORK). For example, ID=*.a01n can be specified. MAX is valid only when
the following conditions are both true:
1. An “any network” resource name is specified on the ID operand
2. IDTYPE=RESOURCE or IDTYPE=DIRECTRY is used.

The value for MAX can be any integer from 1 to 200. The default is 1.

The resource name might exist in more networks than the number you specify
on the MAX operand. However, VTAM searches only for the number of
instances that you have specified. When that number is found, VTAM does not
search any further. This saves processing time for the command and gives you
control over the amount of display output generated by the command. If fewer
resources are found than you have specified on MAX, VTAM displays only the
resources that are found.

The display might show the same resource more than once if both subarea
information and APPN directory information are available for a particular
resource. The value specified for MAX does not take into consideration this
duplication of information for a particular resource, so you could specify a value
such as MAX=3 and receive a display of up to six resources.
NETID=netid
is valid only for CDRSC major nodes and limits the scope of the display to
CDRSCs within the indicated network and CDRSCs defined without a network
identifier (not associated with any particular network). If you specify the NETID
operand, but do not identify a specific network (that is, a value for netid is not
entered), all CDRSCs in the major node are displayed. CDRSCs are displayed
in the order in which they were defined or added within the major node.

To display minor nodes and independent LUs, specify a network-qualified name

on the ID operand, and do not use the NETID operand.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.

The SCOPE operand is ignored for frame relay PUs or FRSESETs. Nor does
SCOPE have any effect when you display resources in the directory database.

These values specify whether information is to be provided about the specified

node’s subordinate resources in addition to the information about the node
itself. They are meaningful only for resources that have subordinate resources.
SCOPE=ACT
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its active, pending, and connectable subordinate

94 SNA Operation
 DISPLAY ID
resources, if any, are to be displayed. If this display is undesirably large,
you can use SCOPE=ACTONLY or SCOPE=CONCT to further limit the
display.
SCOPE=ACTONLY
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its active subordinate resources, if any, are to be
displayed. The display does not include resources in pending or
connectable states. If no resources are found in an active state, you can
use SCOPE=ACT to broaden the scope of the display to active,
connectable, and pending resources.
SCOPE=ACTSESS
specifies that, in addition to the resource specified on the ID operand, the
name of all its subordinate resources that are active with sessions, if any,
are to be displayed.
SCOPE=ALL
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its subordinate resources, if any, are to be displayed
(regardless of their status).
SCOPE=CONCT
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its subordinate resources in a CONCT (connectable)
state, if any, are to be displayed. If no resources are found in a connectable
state, you can use SCOPE=ACT to broaden the scope of the display to
active, connectable, and pending resources.
SCOPE=INACT
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its inactive subordinate resources, if any, are to be
displayed. If this display is undesirably large, you can use
SCOPE=INACTONLY or SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its inactive subordinate resources, if any, are to be
displayed. Resources in a RESET state are not included in the
SCOPE=INACTONLY display.
SCOPE=ONLY
tells VTAM not to display the name and status of any subordinate
resources.
SCOPE=PENDING
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its pending subordinate resources, if any, are to be
displayed. A pending state is a transient state to or from the fully active
state.
SCOPE=RESET
specifies that, in addition to the resource specified on the ID operand, the
name and status of all its subordinate resources in a RESET state, if any,
are to be displayed.

Chapter 2. VTAM Operator Commands 95

DISPLAY ID
Resulting Display
The resources that are displayed depend on their relationship within the hierarchy
that is specified on the ID operand. The following lists show what resources are
displayed for each major node or minor node.

Note: Independent LUs that are defined under a PU do not always appear in this
output. Only independent LUs that are currently using the PU as a boundary
function for multiple concurrent sessions are displayed.

A DISPLAY ID command issued at an APPN node might show a resource name

appearing in several networks even though the resource actually exists in only one
network. This can happen if intermediate SSCPs are pre-V4R1 and they pass only
the 8-character resource name. The real network ID is therefore lost and other
network IDs might be subsequently assumed.

For a DISPLAY ID command with IDTYPE=RESOURCE or IDTYPE=DIRECTRY, if

the resource type that is displayed is EN, the node might actually be a network
node, end node, or SSCP. This is because in a mixed APPN and subarea network,
CPs and SSCPs that are found in or through a subarea network are represented in
this host (the host where you are issuing this command) as end nodes which are
served by the interchange node through which the resource was found.

Note: If model application program definitions are included in the display, any
dynamic application programs built from those models that have been
deactivated are not displayed. This is because dynamic application programs
cannot exist in an inactive state. When a dynamic application program is
deactivated and CLOSE macro processing is complete for the dynamic
application program, the definition of the dynamic application program is
deleted. The dynamic application program is no longer known by VTAM and
will not appear in the output of any DISPLAY commands.
v Major nodes:
– For ID=ADJCP major node, its subordinate nodes
– For ID=application program major node, its subordinate applications:
- Conventially defined application programs
- Model application programs
- Dynamic application programs built from model application program
definitions
– For ID=CDRM major node, its subordinate CDRMs
– For ID=CDRSC major node, its subordinate CDRSCs
– For ID=channel-attachment major node, its subordinate links
– For ID=external communications adapter (XCA) major node, its subordinate
links
– For ID=hostpu, its subordinate cross-subarea links
– For ID=local non-SNA 3270 major node, its subordinate logical units
– For ID=local_sna_major_node:
- Each PU providing local SNA connectivity and its subordinate logical units
- Each PU providing APPN host-to-host connectivity
– For ID=lugroup major node, its model LU groups, and their model LUs
– For ID=model major node, its subordinate logical units and the physical units
to which the logical units are subordinate

96 SNA Operation
 DISPLAY ID
– For ID=NCP major node, its subordinate links
– For ID=rapid transport protocol major node (ISTRTPMN), its dynamic physical
units
– For ID=switched major node, its subordinate logical units and the physical
units to which the logical units are subordinate
v Minor nodes:
– For ID=conventionally defined application program or ACB name:
- For SCOPE=ACT, the established sessions with the application program
- For SCOPE=INACT, the names of logical units waiting for sessions with the
application program
- For SCOPE=ALL, the information provided for both ACT and INACT, as
described above
- An indication if the application is a VCNS user
– For ID=model application program
- An indication that the application program is a model
- A list of dynamic application programs that have been built from this model,
or an indication that no dynamic application programs have been built from
this model
- An indication if the model application program definition specifies that any
dynamic application programs built from the model are to be VCNS users
– For ID=dynamic application program
- An indication that the application program is a dynamic application program
- The name of the model application program definition used to build the
dynamic application program
- For SCOPE=ACT, the established sessions with the dynamic application
program
- For SCOPE=ALL, the established sessions with the dynamic application
program
- An indication if the dynamic application program is a VCNS user
– For ID=CDRSC minor node:
- For SCOPE=ACT, the established sessions with the cross-domain resource
- For SCOPE=INACT, the names of logical units waiting for sessions with the
cross-domain resource
- For SCOPE=ALL, the information provided for both ACT and INACT, as
described in the preceding
– For ID=host CDRM name, the host’s network ID (where applicable), subarea
and element addresses, and only the external CDRM session partner and
session status for established sessions with the host CDRM
– For ID=same-network external CDRM name:
- HPR capability, if the same-network external CDRM is active
- For SCOPE=ACT, active cross-domain resources owned by the external
CDRM
- For SCOPE=INACT, inactive cross-domain resources owned by the
external CDRM
- For SCOPE=ALL, all active or inactive cross-domain resources owned by
the external CDRM
– For ID=cross-network external CDRM name:

Chapter 2. VTAM Operator Commands 97

DISPLAY ID
- For SCOPE=ACT, active cross-network resources owned by the external
CDRM
- For SCOPE=INACT, inactive cross-network resources owned by the
external CDRM
- For SCOPE=ALL, all active or inactive cross-network resources owned by
the external CDRM
– For ID=line group:
- For SCOPE=ALL, lines and PUs
- For SCOPE=ACT, all active lines and all active PUs
- For SCOPE=INACT, all inactive lines, all inactive PUs, and all active lines
that have inactive PUs
- For SCOPE=ONLY, only line group
– For ID=link:
- Its subordinate link stations, or
- Its subordinate physical units and dependent logical units
– For ID=physical_unit:
- Its subordinate logical units
- For a PU providing APPN host-to-host connectivity, the name, current
status, and line control as specified by the TRLE operand on the PU
definition statement
- For a PU supported by a DLUR, the name of the DLUR and the switched
major node that defines the PU
- For a dynamic rapid transport protocol (RTP) PU, the data flow rate and the
end-to-end route
- For an HPR-capable PU in a type 2.1 node, the HPR capability.
v Resources in the directory database:
– The name of the resource
– The entry type, such as dynamic
– The resource type, such as network node
– The owning CP
– The network node server.
v Generic resource names:
– Member name
– Owning CP name
– Whether the resource is currently available to be selected during resolution.
NO indicates that the generic resource is on an end node that does not have
a CP-CP session with its network node server, and is therefore not selected.
– APPC value.

Examples
Displaying an adjacent CP major node:
d net,id=istadjcp,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTADJCP, TYPE = ADJCP MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1100I ADJACENT CONTROL POINTS FROM MAJOR NODE ISTADJCP

98 SNA Operation
 DISPLAY ID
IST1102I NODENAME NODETYPE CONNECTIONS CP CONNECTIONS NATIVE
IST1103I NETB.VN1 VN 0 0 N/A
IST1103I NETA.VN1 VN 1 0 N/A
IST314I END

Displaying an application program major node, including model application

programs and dynamic application programs built from those models:
d net,id=a01appls,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A01APPLS, TYPE = APPL SEGMENT
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST360I APPLICATIONS:
IST080I APPL01 CONCT APPL0102 CONCT A01MVSNO CONCT
IST080I APPL1 CONCT APPLA* CONCT APPL2 CONCT
IST080I APPLQ? CONCT APPL3 CONCT APPLQ1 ACTIV
IST314I END

Displaying a CDRM major node:

d net,id=cdrm1a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = CDRM1A, TYPE = CDRM SEGMENT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST477I CDRMS:
IST1546I CDRM STATUS SUBAREA ELEMENT NETID SSCPID
IST1547I SSCP1A ACTIV 1 1 NETA 1
IST1547I SSCPAA NEVAC 10 1 NETA N/A
IST1547I SSCP2A NEVAC 2 1 NETA N/A
IST1547I SSCPBA NEVAC 11 1 NETA N/A
IST1547I SSCPCA NEVAC 12 1 NETA N/A
IST1547I SSCP7B ACTIV 5 1 NETB 7
IST1547I SSCP9C ACTIV 8 3 NETC 9
IST1500I STATE TRACE = OFF
IST314I END

Displaying a CDRSC major node:

d net,id=istcdrdy,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTCDRDY, TYPE = CDRSC SEGMENT
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST478I CDRSCS:
IST483I C25NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I B01NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I A81NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
IST483I A03D207F ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A02NVLUC ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I ECHO02A ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A50NVLUC ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A500N ACT/S----Y, CDRM = A01N , NETID = NETA
IST483I A02N ACT/S----Y, CDRM = A01N , NETID = NETA
IST314I END

Displaying a CDRSC major node for a specific network:

d net,id=a99cdrsc,netid=netc,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A99CDRSC, TYPE = CDRSC SEGMENT
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST478I CDRSCS:
IST483I CECHO01 ACTIV , CDRM = C01M , NETID = NETC
IST483I TPNSC01 ACTIV , CDRM = C01M , NETID = NETC
IST483I C01NVLUC ACTIV , CDRM = C01M , NETID = NETC
IST483I TSO11 ACTIV , CDRM = ***NA***, NETID = NETC
IST483I ECHO11 ACTIV , CDRM = C11M , NETID = NETC
IST483I C11NVLUC ACTIV , CDRM = C11M , NETID = NETC

Chapter 2. VTAM Operator Commands 99

DISPLAY ID
IST483I TSO255 ACTIV , CDRM = ***NA***, NETID = NETC
IST483I ECHO255 ACTIV , CDRM = C255M , NETID = NETC
IST483I C255NLUC ACTIV , CDRM = C255M , NETID = NETC
IST314I END

Displaying a dependent LU requester:

d net,id=nncpa1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.NNCPA1, TYPE = ADJACENT CP
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=CPSVCMG USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST1044I ALSLIST = ISTAPNPU
IST1131I DEVICE = ILU/CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = NNCPA1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000004, SESSION REQUESTS = 000000004
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = P3A4956K
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I SSCP1A ACTIV/DL-S E2C5E2E2D6D5000B 001C 0000 0 0 NETA
IST635I SSCP1A ACTIV/CP-S E2C5E2E2D6D50005 0004 0001 0 0 NETA
IST635I SSCP1A ACTIV/DL-P EAABEEC3361D945A 0000 0012 0 0 NETA
IST635I SSCP1A ACTIV/CP-P EAABEEC3361D9458 0001 0005 0 0 NETA
IST1355I PHYSICAL UNITS SUPPORTED BY DLUR NETA.NNCPA1
IST089I AA1PUA TYPE = PU_T2 , ACTIV
IST089I AA1PUB TYPE = PU_T2 , ACTIV
IST924I --------------------------------------------------------
IST075I NAME = NETA.NNCPA1, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC NN
IST1184I CPNAME = NETA.NNCPA1 - NETSRVR = ***NA***
IST314I END

Displaying a local SNA major node:

d net,id=a50lsna,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A50LSNA, TYPE = LCL SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST084I NETWORK NODES:
IST089I PUA TYPE = PU_T2 , ACTIV ,CUA=0770
IST089I LSNALU1 TYPE = LOGICAL UNIT , ACTIV
IST089I LSNALU2 TYPE = LOGICAL UNIT , ACTIV
IST089I LSNALU3 TYPE = LOGICAL UNIT , ACTIV
IST089I LSNALU4 TYPE = LOGICAL UNIT , ACTIV
IST314I END

Displaying a local SNA major node for each PU providing APPN host-to-host
connectivity:
d net,id=lsna1a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = LSNA1A, TYPE = LCL SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST084I NETWORK NODES:
IST1316I PU NAME = AHHCPU1 STATUS = NEVAC TRLE = ML1A2A2
IST1316I PU NAME = AHHCPU2 STATUS = NEVAC TRLE = ML1A2A3
IST1316I PU NAME = AHHCPU3 STATUS = NEVAC TRLE = ML1A2A4
IST314I END

Displaying the dynamic XCF local SNA major node:

100 SNA Operation

 DISPLAY ID
d net,id=istlsxcf,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTLSXCF, TYPE = LCL SNA MAJ NODE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST084I NETWORK RESOURCES:
IST1316I PU NAME = ISTP0001 STATUS = ACTIV--LX- TRLE = ISTT0001
IST1500I STATE TRACE = OFF
IST314I END

Displaying a local non-SNA 3270 major node:

d net,id=a01local,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A01LOCAL, TYPE = LCL 3270 MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST355I LOGICAL UNITS:
IST089I A01A741 TYPE = LOGICAL UNIT , NEVAC ,CUA=0741
IST089I A01A742 TYPE = LOGICAL UNIT , NEVAC ,CUA=0742
IST089I A01A743 TYPE = LOGICAL UNIT , NEVAC ,CUA=0743
IST089I A01A744 TYPE = LOGICAL UNIT , NEVAC ,CUA=0744
IST089I A01A745 TYPE = LOGICAL UNIT , NEVAC ,CUA=0745
IST089I A01A746 TYPE = LOGICAL UNIT , NEVAC ,CUA=0746
IST089I A01A747 TYPE = LOGICAL UNIT , NEVAC ,CUA=0747
IST089I A01A748 TYPE = LOGICAL UNIT , NEVAC ,CUA=0748
IST089I A01A721 TYPE = LOGICAL UNIT , ACT/S ,CUA=0721
IST089I A01A722 TYPE = LOGICAL UNIT , ACTIV ,CUA=0722
IST089I A01A723 TYPE = LOGICAL UNIT , ACTIV ,CUA=0723
IST089I A01A724 TYPE = LOGICAL UNIT , ACTIV ,CUA=0724
IST089I A01A725 TYPE = LOGICAL UNIT , ACTIV ,CUA=0725
IST089I A01A726 TYPE = LOGICAL UNIT , NEVAC ,CUA=0726
IST314I END

Displaying an NCP major node:

d net,id=a0462zc,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A0462ZC, TYPE = PU T4/5
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST247I LOAD/DUMP PROCEDURE STATUS = RESET
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST484I SUBAREA = 4
IST391I ADJ LINK STATION = 0017-S, LINE = 0017-L, NODE = ISTPUS
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST077I SIO = 50078 CUA = 0017
IST675I VR = 0, TP = 2
IST170I LINES:
IST080I A04B00 NEVAC A04B01 NEVAC A04B03 NEVAC
IST080I A04B32 NEVAC A04B33 NEVAC A04B35 NEVAC
IST080I A04VXX NEVAC----T A04S02 NEVAC A04S34 NEVAC
IST080I A04S04 NEVAC A04S16 NEVAC A04S20 NEVAC
IST080I A04S36 NEVAC A04S48 NEVAC A04S52 NEVAC
IST080I A04S128 NEVAC A04S136 NEVAC A04PT88 ACTIV
IST080I A04C00 NEVAC A04C02 NEVAC
IST314I END

Displaying the host physical unit:

d net,id=istpus,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTPUS, TYPE = PU T4/5 060
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST596I IRN TRACE = OFF
IST1656I VTAMTOPO = INCLUDE, NODE REPORTED - YES
IST484I SUBAREA = 1
IST925I DYNAMIC PATH DEFINITION PATH1A STATUS = ACTIV
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF

Chapter 2. VTAM Operator Commands 101

DISPLAY ID
IST1500I STATE TRACE = OFF
IST170I LINES:
IST080I 091C-L ACTIV----I
IST314I END

Displaying the rapid transport protocol (RTP) major node:

d net,id=istrtpmn,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTRTPMN, TYPE = RTP MAJOR NODE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1486I RTP NAME STATE DESTINATION CP MNPS TYPE
IST1487I CNR00004 CONNECTED NETA.SSCP2A NO LULU
IST1487I CNR00003 CONNECTED NETA.SSCP2A NO RSTP
IST1487I CNR00002 CONNECTED NETA.SSCP2A NO CPCP
IST1487I CNR00001 CONNECTED NETA.SSCP2A NO CPCP
IST314I END

Displaying a switched major node:

d net,id=a04smnc,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04SMNC, TYPE = SW SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST084I NETWORK NODES:
IST089I A04P882 TYPE = PU_T2 , ACTIV--L--
IST089I A04P883 TYPE = PU_T2 , ACTIV--L--
IST089I A04D8831 TYPE = LOGICAL UNIT , ACTIV
IST089I A04D8832 TYPE = LOGICAL UNIT , ACTIV
IST089I A04D8833 TYPE = LOGICAL UNIT , ACT/S
IST089I A04D8834 TYPE = LOGICAL UNIT , ACTIV
IST089I A04D8835 TYPE = LOGICAL UNIT , ACTIV
IST089I A04D8836 TYPE = LOGICAL UNIT , ACT/S
IST089I A04D8837 TYPE = LOGICAL UNIT , ACT/S
IST089I A04P885 TYPE = PU_T2 , ACTIV--L--
IST089I A04P886 TYPE = PU_T2 , ACTIV--L--
IST089I A04D8861 TYPE = LOGICAL UNIT , ACT/S
IST089I A04D8862 TYPE = LOGICAL UNIT , ACT/S
IST089I A04D8863 TYPE = LOGICAL UNIT , ACTIV
IST089I A04D8864 TYPE = LOGICAL UNIT , ACTIV
IST314I END

Displaying a channel-attachment major node:

d net,id=ctcbc0t3,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = CTCBC0T3 , TYPE = CA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST170I LINES:
IST232I CTCLBC03, ACTIV----E, CUA = BC0
IST314I END

Displaying an XCA major node with its subordinate resources:

d net,id=xca1a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = XCA1A, TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1021I MEDIUM=RING,ADAPNO= 1,CUA=0500,SNA SAP= 8
IST1324I VNNAME = NETA.CN1 VNGROUP = GP1A2A
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I XCA1A AC/R 21 NO 902D0000000000000000017100808080
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST170I LINES:
IST232I LN1A2A , ACTIV

102 SNA Operation

 DISPLAY ID
IST232I LN1A7B , NEVAC
IST232I LN1A9C , NEVAC
IST232I LN1AAA , NEVAC
IST232I LN1ABA , NEVAC
IST232I LN1ACA , NEVAC
IST232I LN1ADA , NEVAC
IST232I LN1AEA , NEVAC
IST314I END

Displaying an XCA major node without its subordinate resources:

d net,id=x50rbf4a
IST097I DISPLAY ACCEPTED
IST075I NAME = X50RBF4A, TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1021I MEDIUM=RING,ADAPNO= 0,CUA=0BF4,SNA SAP= 4
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST314I END

Displaying an XCA major node that defines a native ATM port:

d net,id=xcaosa1a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = XCAOSA1A, TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1557I MEDIUM = ATM, PORT NAME = OSA11
IST1559I ATM ADDRESS TYPE FORMAT
IST1553I 1111111111111111111111111111111111111100 LOCAL NSAP
IST1324I VNNAME = NETA.SSCPVN VNGROUP = GP1A2AC
IST1559I ATM ADDRESS TYPE FORMAT
IST1553I 2111111111111111111111111111111111111110 GATEWAY NSAP
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I XCAOSA1A AC/R 21 NO 10750000000000000000014C00808080
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST170I LINES:
IST232I LN1A2A ACTIV
IST232I LNP1A2A1 ACTIV
IST232I LN1A2AC1 ACTIV
IST314I END

Displaying an XCA major node group that defines a transmission group (TG) to a
native ATM connection network:
d net,id=gp1a2ac,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = GP1A2AC, TYPE = LINE GROUP
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST231I XCA MAJOR NODE = XCAOSA1A
IST1485I DLCADDR SUBFIELDS FOR GP1A2AC
IST1318I 1,C'ATMSVCNETA.SSCPVNEXCLUSIVE'
IST1318I 7,BCD'03000000 40000000 40000000 536000'
IST1318I 8,X'0003'
IST1318I 21,X'00022111 11111111 11111111 11111111 11111111 1110'
IST084I NETWORK RESOURCES:
IST089I LN1A2AC1 TYPE = LINE , ACTIV
IST314I END

| Displaying an XCA major node that defines Enterprise Extender:

| d net,id=xcahpr1a,scope=all
| IST097I DISPLAY ACCEPTED
| IST075I NAME = XCAHPR1A, TYPE = XCA MAJOR NODE
| IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
| IST1679I MEDIUM = HPRIP
| IST1685I TCP/IP JOB NAME = TCPR6A
| IST1680I LOCAL IP ADDRESS 223.254.254.254

Chapter 2. VTAM Operator Commands 103

 DISPLAY ID
| IST1324I VNNAME = NETA.SSCPVN VNGROUP = GP1A2AC
| IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
| IST1106I XCAHPR1A AC/R 21 NO 10750000000000000000014C00808080
| IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
| IST170I LINES:
| IST232I LN1A2A ACTIV
| IST232I LNP1A2A1 ACTIV
| IST232I LN1A2AC1 ACTIV
| IST314I END
|

Displaying an adjacent CP (CDRSC minor node):

d net,id=neta.sscp2a,idtype=cp,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.SSCP2A, TYPE = ADJACENT CP
IST1046I SSCP NETA.SSCP2A ALSO EXISTS
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = SSCP1A, VERIFY OWNER = NO
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST1044I ALSLIST = ISTAPNPU
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000002
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = P3A21
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I SSCP1A ACTIV/CP-S F6ABEEC38077021A 0002 0001 0 0 NETA
IST635I SSCP1A ACTIV/CP-P EAABEEC37D76FABF 0001 0002 0 0 NETA
IST314I END

Displaying an SSCP (CDRM minor node) with virtual-route-based transmission

group support:
d net,id=neta.sscp2a,idtype=sscp,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.SSCP2A, TYPE = CDRM
IST1046I CP NETA.SSCP2A ALSO EXISTS
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = CDRM1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST476I CDRM TYPE = EXTERNAL
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST675I VR = 0, TP = 0
IST389I PREDEFINITION OF CDRSC = OPT
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I SSCP2A AC/R 255 YES 982D0000000000000000017100808080
IST636I CDRSCS OWNED BY SSCP2A -
IST080I L4A3278A ACTIV L4A3279A ACTIV L4A3767D ACTIV
IST080I L4A3278B ACTIV L4A3279B ACTIV L4A3287B ACTIV
IST080I L4A3767E ACTIV L4A4956D ACTIV L4A4956E ACTIV
IST080I L4A4956F ACTIV NETAPPL1 ACTIV NETAPPL2 ACTIV
IST080I NETAPPL3 ACTIV NETAPPL4 ACTIV APLMDSEC ACTIV
IST080I TSO2 ACTIV
IST314I END

Displaying an SSCP (CDRM) and adjacent CP (CDRSC) with the same name from
a network node:

104 SNA Operation

 DISPLAY ID
d net,id=sscp2a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.SSCP2A, TYPE = CDRM
IST1046I CP NETA.SSCP2A ALSO EXISTS
IST486I STATUS= NEVAC, DESIRED STATE= INACT - TRACE= OFF
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = CDRM1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST476I CDRM TYPE = EXTERNAL
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST389I PREDEFINITION OF CDRSC = OPT
IST636I CDRSCS OWNED BY SSCP2A -
IST080I NETAPPL1 PNF/S
IST924I -------------------------------------------------------------
IST075I NAME = NETA.SSCP2A, TYPE = ADJACENT CP
IST1046I SSCP NETA.SSCP2A ALSO EXISTS
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = SSCP1A, VERIFY OWNER = NO
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST1044I ALSLIST = ISTAPNPU
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000002
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = P3A21
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I SSCP1A ACTIV/CP-S F6ABEEC38077021A 0006 0001 0 0 NETA
IST635I SSCP1A ACTIV/CP-P EAABEEC37D76FABF 0001 0006 0 0 NETA
IST924I -------------------------------------------------------------
IST075I NAME = NETA.SSCP2A, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC NN
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST314I END

Displaying an SSCP (CDRM) and a host CP (application) with the same name:
d net,id=neta.sscp1a,idtype=resource,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.SSCP1A, TYPE = CDRM
IST1046I CP NETA.SSCP1A ALSO EXISTS
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST476I CDRM TYPE = HOST, GATEWAY CAPABLE
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST388I DYNAMIC CDRSC DEFINITION SUPPORT = YES
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST924I -------------------------------------------------------------
IST075I NAME = NETA.SSCP1A, TYPE = HOST CP
IST1046I SSCP NETA.SSCP1A ALSO EXISTS
IST486I STATUS= ACT/S , DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = VTAM , STEPNAME = VTAM , DSPNAME = 0AAABIST

Chapter 2. VTAM Operator Commands 105

DISPLAY ID
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = SSCP1A CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I SSCP2A ACTIV/CP-S EAABEEC3F11FF31F 0002 0001 NETA
IST635I SSCP2A ACTIV/CP-P F6ABEEC3F4203D93 0001 0002 NETA
IST314I END

Displaying the host (this command works for any host). This display shows an
interchange node:
d net,id=vtam
IST097I DISPLAY ACCEPTED
IST075I NAME = VTAM, TYPE = CDRM 404
IST1046I CP NETA.SSCP1A ALSO EXISTS
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST599I REAL NAME = NETA.SSCP1A
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST476I CDRM TYPE = HOST GATEWAY CAPABLE
IST637I SUBAREA = 1 ELEMENT = 1 SSCPID = 1
IST388I DYNAMIC CDRSC DEFINITION SUPPORT = YES
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST924I -------------------------------------------------------------
IST075I NAME = NETA.SSCP1A, TYPE = HOST CP
IST1046I SSCP NETA.SSCP1A ALSO EXISTS
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = NO
IST1501I XCF TOKEN = 010000B7000F0001
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST1632I VPACING = 63
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST271I JOBNAME = VTAM550T, STEPNAME = NET, DSPNAME = ISTEAF13
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = SSCP1A CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST1633I ASRCVLM = 1999999
IST1634I DATA SPACE USAGE: CURRENT = 0 MAXIMUM = 272
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000000
IST314I END

Displaying a CDRSC (no SSCP, adajcent CP, or host CP was found with this name)
from a network node:
d net,id=neta.netappl1,idtype=resource,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.NETAPPL1, TYPE = CDRSC
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = CDRSC1A
IST479I CDRM NAME = SSCP2A, VERIFY OWNER = NO

106 SNA Operation

 DISPLAY ID
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST1044I ALSLIST = ISTAPNPU
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000001
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = P3A21
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I APPL1 ACTIV-P EAABEEC37D76FAC1 0000 0000 0 0 NETA
IST924I -------------------------------------------------------------
IST075I NAME = NETA.NETAPPL1, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC LU
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST314I END

Displaying directory information for a resource (no SSCP, adjacent CP, host CP, or
other resource was found with this name) and the command was issued at a
network node or interchange node:
d net,id=neta.lu71,idtype=resource,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.LU71, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC LU
IST1184I CPNAME = NETA.NN3 - NETSRVR = ***NA***
IST314I END

Displaying only directory information for a resource:

d net,id=sscp2a,idtype=directry,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.SSCP2A, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC NN
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST314I END

Displaying a conventionally defined application program:

d net,id=appl1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.APPL1, TYPE = APPL
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST1632I VPACING = 7
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = APPL1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST271I JOBNAME = ECHO, STEPNAME = ECHO, DSPNAME = IST6D2D6
IST228I ENCRYPTION = OPTIONAL
IST1563I CKEYNAME = APPL1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST1633I ASRCVLM = 2000000
IST1634I DATA SPACE USAGE: CURRENT = 0 MAXIMUM = 0
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000001
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I NETAPPL1 ACTIV-S EAABEEC37D76FAC1 0000 0000 0 0 NETA
IST314I END

Displaying a model application program:

d net,id=appl*,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.APPL*, TYPE = MODEL APPL

Chapter 2. VTAM Operator Commands 107

DISPLAY ID
IST486I STATUS= CONCT, DESIRED STATE= CONCT - TRACE= OFF
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NON
IST231I APPL MAJOR NODE = APPL1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME = ***NA
IST228I ENCRYPTION = OPTIONAL
IST1563I CKEYNAME = APPL* CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST1424I APPLICATIONS DEFINED USING THIS MODEL:
IST080I APPL1 ACTIV
IST314I END

Displaying a multinode persistent session application program from a remote node

connected to the MNPS coupling facilty structure could result in any of the
following:
d net,id=mapplx1,e
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.MAPPLX1, TYPE = APPL
IST1549I OWNER = NETA.SSCP2A MNPS STATE = DISABLED
IST924I -------------------------------------------------------------
IST075I NAME = NETA.MAPPLX1, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = REGISTERED LU
IST1184I CPNAME = NETA.SSCP1A - NETSRVR = NETA.SSCPAA
IST314I END
d net,id=mapplx1,e
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.MAPPLX1, TYPE = CDRSC
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = SSCPAA, VERIFY OWNER = NO
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = MAPPLX1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = CNR00005
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I APPLAA1 ACTIV-P EAABEE185A59FD67 0000 0000 0 0 NETA
IST924I -------------------------------------------------------------
IST075I NAME = NETA.MAPPLX1, TYPE = APPL
IST1549I OWNER = NETA.SSCP2A MNPS STATE = ENABLED
IST924I -------------------------------------------------------------
IST075I NAME = NETA.MAPPLX1, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC LU
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST314I END
d net,id=mappl1,e
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.MAPPL1, TYPE = CDRSC
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV

108 SNA Operation

 DISPLAY ID
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = SSCP1A, VERIFY OWNER = NO
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = MAPPL1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = CNR00003
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I APPL1 ACTIV-P EAABEEC30C061090 0000 0000 0 0 NETA
IST924I -------------------------------------------------------------
IST075I NAME = NETA.MAPPL1, TYPE = APPL
IST1549I OWNER = NETA.SSCP2A MNPS STATE = DISABLED
IST314I END
d net,id=mapplx1,e
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.MAPPLX1, TYPE = APPL
IST486I STATUS= CONCT, DESIRED STATE= CONCT
IST1447I REGISTRATION TYPE = CDSERVR
IST1550I MNPS STATE = DEFINED
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST1632I VPACING = 7
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = APPLMG2
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME = ***NA***
IST228I ENCRYPTION = OPTIONAL
IST1563I CKEYNAME = MAPPLX1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST1633I ASRCVLM = 1000000
IST1634I DATA SPACE USAGE: CURRENT = ***NA*** MAXIMUM = ***NA***
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST924I -------------------------------------------------------------
IST075I NAME = NETA.MAPPLX1, TYPE = APPL
IST1549I OWNER = NETA.SSCP1A MNPS STATE = DISABLED
IST314I END

Displaying a dynamic application program:

d net,id=appl1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.APPL1, TYPE = DYNAMIC APPL
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST1632I VPACING = 7
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NON
IST231I APPL MAJOR NODE = APPL1A
IST1425I DEFINED USING MODEL APPL*
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF

Chapter 2. VTAM Operator Commands 109

DISPLAY ID
IST1500I STATE TRACE = OFF
IST271I JOBNAME = ECHO, STEPNAME = ECHO, DSPNAME = IST75874
IST228I ENCRYPTION = OPTIONAL
IST1563I CKEYNAME = APPL1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST1633I ASRCVLM = 2000000
IST1634I DATA SPACE USAGE: CURRENT = 0 MAXIMUM = 0
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000
IST314I END

Displaying the application program representing the network operator:

d net,id=istnop
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.ISTNOP, TYPE = APPL
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1395I FLDTAB = ISTMSFLD FILTER = ISTMGC10
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME = ***NA***
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = ISTNOP CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST314I END

Displaying a dynamic same-network CDRSC:

d net,id=applaa3,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.APPLAA3, TYPE = CDRSC
IST486I STATUS= ACTIV----Y, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = ***NA***, VERIFY OWNER = NO
IST1184I CPNAME = NETA.SSCPAA - NETSRVR = ***NA***
IST082I DEVTYPE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = APPLAA3 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST314I END

Displaying a dynamic cross-network CDRSC:

d net,id=netb.applb11,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETB.APPLB11, TYPE = CDRSC
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE

110 SNA Operation

 DISPLAY ID
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = SSCP7B, VERIFY OWNER = NO
IST1184I CPNAME = NETB.SSCP7B - NETSRVR = ***NA***
IST082I DEVTYPE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = APPLB11 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I APPL1 ACTIV-S C2BB19BC74339803 0016 0016 0 0 NETA
IST635I APPL1 ACTIV-P EAABEEC34604F7E2 0009 000A 0 0 NETA
IST314I END

Displaying a predefined CDRSC for a specific network:

d net,id=applb11,netid=netb,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = APPLB11, TYPE = CDRSC
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = CDRSC1A
IST479I CDRM NAME = SSCP7B, VERIFY OWNER = NO
IST082I DEVTYPE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = APPLB11 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST314I END

Displaying a predefined CDRSC without network (no sessions):

d net,id=netappl2,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.NETAPPL2, TYPE = CDRSC
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV - TRACE= OFF
IST1447I REGISTRATION TYPE = NO
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = CDRSC1A
IST479I CDRM NAME = SSCP2A, VERIFY OWNER = NO
IST082I DEVTYPE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST314I END

Displaying an independent logical unit:

d net,id=l3270a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = L3270A, TYPE = CDRSC
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST599I REAL NAME = ***NA***
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST1333I ADJLIST = ***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***

Chapter 2. VTAM Operator Commands 111

DISPLAY ID
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTPDILU
IST1044I ALSLIST = AHHCPU1
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = L3270A CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST924I -------------------------------------------------------------
IST075I NAME = NETA.L3270A, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = REGISTERED LU
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = NETA.SSCP1A
IST314I END

Displaying the host CDRM:

d net,id=a01n,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.A01N, TYPE = CDRM
IST1046I CP NETA.A01N ALSO EXISTS
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST476I CDRM TYPE = HOST, GATEWAY CAPABLE
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST388I DYNAMIC CDRSC DEFINITION SUPPORT = YES
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST924I -------------------------------------------------------------
IST075I NAME = NETA.A01N, TYPE = HOST CP
IST1046I SSCP NETA.A01N ALSO EXISTS
IST486I STATUS= ACT/S , DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = VTAMSEG
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = NET41B , STEPNAME = NET , DSPNAME = 00000IST
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST171I ACTIVE SESSIONS = 0000000014, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I A04P882A ACTIV/CP-S E7F3895623BE5C86 000D 0001 0 0 NETY
IST635I A04P888A ACTIV/CP-S E7F3895623BE5C85 053E 0001 0 0 NETA
IST635I A04P886A ACTIV/CP-S E7F3895623BE5C84 0721 0001 0 0 NETA
IST635I A04P885A ACTIV/CP-S E7F3895623BE5C83 03AE 0001 0 0 NETA
IST635I A04P889A ACTIV/CP-S E7F3895623BE5C82 0727 0001 0 0 NETA
IST635I A04P883A ACTIV/CP-S E7F3895623BE5C81 01C5 0001 0 0 NETZ
IST635I A02N ACTIV/CP-S E7F3895623BE56A5 1055 0001 0 0 NETA
IST635I A02N ACTIV/CP-P E7E3F9563F1747D7 0001 1047 0 0 NETA
IST635I A04P882A ACTIV/CP-P F3342BAB9019C2B2 0001 000E 0 0 NETY
IST635I A04P883A ACTIV/CP-P E36D478882B602AB 0001 01C6 0 0 NETZ
IST635I A04P885A ACTIV/CP-P EF0E04F6C768DD2E 0001 03AF 0 0 NETA
IST635I A04P886A ACTIV/CP-P EF0E07F6C768E02F 0001 0722 0 0 NETA
IST635I A04P888A ACTIV/CP-P EF0E09F6C768E230 0001 053F 0 0 NETA
IST635I A04P889A ACTIV/CP-P EF0E08F6C768E131 0001 0728 0 0 NETA
IST314I END

Displaying an active, same-network, external CDRM:

d net,id=A02n,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.A02N, TYPE = CDRM
IST1046I CP NETA.A02N ALSO EXISTS

112 SNA Operation

 DISPLAY ID
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = A01CDRMC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST476I CDRM TYPE = EXTERNAL
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST675I VR=0, TP=0
IST389I PREDEFINITION OF CDRSC = OPT
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I A02N AC/R 255 YES 982D0000000000000000017100808080
IST1482I HPR= NO - OVERRIDE = YES - CONNECTION = YES
IST636I CDRSCS OWNED BY A02N -
IST172I NO CDRSCS EXIST
IST924I -------------------------------------------------------------
IST075I NAME = NETA.A02N, TYPE = ADJACENT CP
IST1046I SSCP NETA.A02N ALSO EXISTS
IST486I STATUS= ACT/S----Y, DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = ISTCDRDY
IST479I CDRM NAME = A01N , VERIFY OWNER = NO
IST1044I ALSLIST = ISTAPNPU
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000002, SESSION REQUESTS = 0000000000
IST206I SESSIONS:
IST1081I ADJACENT LINK STATION = A02NETNA
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I A01N ACTIV/CP-S E7E3F9563F1747D7 1055 0001 0 0 NETA
IST635I A01N ACTIV/CP-P E7F3895623BE56A5 0001 105F 0 0 NETA
IST924I -------------------------------------------------------------
IST075I NAME = NETA.A02N, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC NN
IST1184I CPNAME = NETA.A02N - NETSRVR = ***NA***
IST314I END

Displaying a cross-network external CDRM:

d net,id=c01n,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETC.C01N, TYPE = CDRM
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST815I AUTOMATIC RECOVERY IS SUPPORTED
IST231I CDRM MAJOR NODE = A50CDRMC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST476I CDRM TYPE = EXTERNAL
IST637I SUBAREA= 2 ELEMENT= 1 SSCPID = 2
IST675I VR = 0, TP = 2
IST638I ADJNETSA = 1, ADJNETEL = 1
IST675I VR = 0, TP = 2
IST639I GWN = A0362ZC , ADJNET = NETC
IST640I A500N ADDR IN ADJNET - SA = 31, EL = 11
IST641I GATEWAY PATH SELECTION LIST -
IST642I ADJNET GWN SUBAREA ELEM ADJNETSA ADJNETEL
IST643I NETC A0362ZC 3 1 1 1
IST643I NETC 255 3 1 1
IST898I GWSELECT = YES
IST389I PREDEFINITION OF CDRSC = OPT
IST636I CDRSCS OWNED BY C01N -
IST080I C01NVLUC ACT/S----Y
IST924I -------------------------------------------------------------

Chapter 2. VTAM Operator Commands 113

DISPLAY ID
IST075I NAME = NETC.C01N, TYPE = DIRECTORY ENTRY
IST1186I DIRECTORY ENTRY = DYNAMIC EN
IST1184I CPNAME = NETC.C01N - NETSRVR = NETA.A01N
IST314I END

Displaying a peripheral BSC line group:

d net,id=a03lbnnb,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A03LBNNB , TYPE = LINE GROUP
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST354I PU T4/5 MAJOR NODE = A0362ZC
IST084I NETWORK NODES:
IST089I A03B00 TYPE = LINE , NEVAC
IST089I A03C001 TYPE = PU_T2 , NEVAC
IST089I A03C002 TYPE = PU_T2 , NEVAC
IST089I A03B01 TYPE = LINE , NEVAC
IST089I A03C011 TYPE = PU_T2 , NEVAC
IST089I A03C012 TYPE = PU_T2 , NEVAC
IST089I A03B32 TYPE = LINE , NEVAC
IST089I A03C321 TYPE = PU_T2 , NEVAC
IST089I A03C322 TYPE = PU_T2 , NEVAC
IST089I A03B33 TYPE = LINE , NEVAC
IST089I A03C331 TYPE = PU_T2 , NEVAC
IST089I A03C332 TYPE = PU_T2 , NEVAC
IST314I END

Displaying a peripheral SDLC line group:

d net,id=a03lbnns,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A03LBNNS , TYPE = LINE GROUP
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST354I PU T4/5 MAJOR NODE = A0362ZC
IST084I NETWORK NODES:
IST089I A03S16 TYPE = LINE , ACTIV
IST089I A03P161 TYPE = PU_T2 , PREQC
IST089I A03P162 TYPE = PU_T2 , PREQC
IST089I A03P163 TYPE = PU_T2 , PREQC
IST089I A03P164 TYPE = PU_T2 , PREQC
IST089I A03S20 TYPE = LINE , ACTIV
IST075I NAME = A03LBNNS , TYPE = LINE GROUP
IST089I A03P201 TYPE = PU_T2 , PREQC
IST089I A03P202 TYPE = PU_T2 , PREQC
IST089I A03P203 TYPE = PU_T2 , PREQC
IST089I A03P204 TYPE = PU_T2 , PREQC
IST089I A03P205 TYPE = PU_T2 , PREQC
IST089I A03P206 TYPE = PU_T2 , PREQC
IST314I END

Displaying a peripheral SDLC switched line group:

d net,id=grp3a9,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = GRP3A9, TYPE = LINE GROUP
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST354I PU T4/5 MAJOR NODE = NCP3AB5
IST084I NETWORK NODES:
IST089I LN3A9 TYPE = LINE , ACTIV
IST089I P3A4956K TYPE = PU_T2 , ACTIV--L--
IST089I L3A4956A TYPE = LOGICAL UNIT , ACT/S
IST089I LN3A10 TYPE = LINE , ACTIV
IST089I P3A4956L TYPE = PU_T2 , ACTIV--L--
IST089I L3A4956A TYPE = LOGICAL UNIT , ACT/S
IST089I LN3A11 TYPE = LINE , ACTIV
IST089I P3A4956M TYPE = PU_T2 , NEVAC
IST314I END

114 SNA Operation

 DISPLAY ID
Note: Independent LU L3A4956A is shown under two PUs because it has active
sessions through these PUs.

Displaying a peripheral BSC link:

d net,id=a03b00,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A03B00 , TYPE = LINE
IST486I STATUS= NEVAC , DESIRED STATE= INACT
IST087I TYPE = LEASED , CONTROL = BSC , HPDT = *NA*
IST134I GROUP = A03LBNNB, MAJOR NODE = A0362ZC
IST650I POLL = 000, NEGPOLL = 010, SESSION(S) = 032
IST084I NETWORK NODES:
IST089I A03C001 TYPE = PU_T2 , NEVAC
IST089I A03T0011 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0012 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0013 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0014 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0015 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0016 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0017 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0018 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0019 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001A TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001B TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001C TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001D TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001E TYPE = LOGICAL UNIT , NEVAC
IST089I A03T001F TYPE = LOGICAL UNIT , NEVAC
IST089I A03C002 TYPE = PU_T2 , NEVAC
IST089I A03T0021 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0022 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0023 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0024 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0025 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0026 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0027 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0028 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T0029 TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002A TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002B TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002C TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002D TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002E TYPE = LOGICAL UNIT , NEVAC
IST089I A03T002F TYPE = LOGICAL UNIT , NEVAC
IST314I END

Displaying an SDLC link (multidrop INN):

d net,id=a04in01,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04IN01, TYPE = LINE
IST486I STATUS= ACTIV----E , DESIRED STATE = ACTIV
IST087I TYPE = LEASED , CONTROL = SDLC, HPDT = *NA*
IST134I GROUP = A04MPRI, MAJOR NODE = A04N43A
IST084I NETWORK NODES:
IST089I A04P013 TYPE = PU_T2 , NEVAC
IST089I A04L013A TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013B TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013C TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013D TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013E TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013F TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013G TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013H TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013I TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013J TYPE = LOGICAL UNIT , NEVAC

Chapter 2. VTAM Operator Commands 115

DISPLAY ID
IST089I A04L013K TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013L TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013M TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013N TYPE = LOGICAL UNIT , NEVAC
IST089I A04L013O TYPE = LOGICAL UNIT , NEVAC
IST089I A04I013A TYPE = LOGICAL UNIT , NEVAC
IST089I A04I013B TYPE = LOGICAL UNIT , NEVAC
IST089I A04I013C TYPE = LOGICAL UNIT , NEVAC
IST089I A04I013D TYPE = LOGICAL UNIT , NEVAC
IST089I A04I013E TYPE = LOGICAL UNIT , NEVAC
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A04P014 NEVAC 2 2 0
IST397I A04P015 NEVAC 2 2 0
IST397I A04P016 NEVAC 2 2 0
IST397I A04P017 ACTIV----E 2 2 A31N52B 31
IST397I A04P018 ACTIV----E 2 2 A71N43A 71
IST397I A04P019 NEVAC 2 2 0
IST397I A04P01A NEVAC 2 2 0
IST397I A04P01B NEVAC 2 2 0
IST397I A04P01C NEVAC 2 2 0
IST314I END

Displaying a peripheral SDLC link:

d net,id=ln3atr10,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = LN3ATR10, TYPE = LINE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = SDLC, HPDT = *NA*
IST1440I USE = NCP, SPARE RESOURCE, CAN BE REDEFINED
IST134I GROUP = GP3ATRP1, MAJOR NODE = NCP3AB7
IST1324I VNNAME = NETA.VN1 VNGROUP = GP3ATR10
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I LN3ATR10 AC/R 21 NO 90750000000000000000017100808080
IST084I NETWORK NODES:
IST089I P3ATR10 TYPE = PU_T2 , ACTIV
IST314I END

Displaying a cross-subarea SDLC switched link:

d net,id=a04hdx00,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04HDX00, TYPE = LINE
IST486I STATUS= ACTIV , DESIRED STATE = ACTIV
IST087I TYPE = SWITCHED DIAL-INOUT, CONTROL = SDLC, HPDT = *NA*
IST936I ANSWER MODE = ENABLED
IST134I GROUP = A04SADG1, MAJOR NODE = A04S43A
IST084I NETWORK NODES:
IST089I A31A TYPE = LINK STATION , ACTIV
IST314I END

Displaying a peripheral SDLC switched link:

d net,id=j0004001,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME =J00004001, TYPE = LINE
IST486I STATUS= ACTIV , DESIRED STATE = ACTIV
IST087I TYPE = SWITCHED DIAL-INOUT, CONTROL = SDLC, HPDT = *NA*
IST936I ANSWER MODE = ENABLED
IST134I GROUP = A04TRLG1, MAJOR NODE = A04S43A
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST172I NO NETWORK NODES EXIST
IST314I END

Displaying an NTRI line in an NCP:

116 SNA Operation

 DISPLAY ID
d net,id=ln3atr11
IST097I DISPLAY ACCEPTED
IST075I NAME = LN3ATR11, TYPE = LINE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = SWITCHED DIAL-INOUT, CONTROL = SDLC, HPDT = *NA*
IST936I ANSWER MODE = ENABLED
IST1440I USE = NCP, DEFINED RESOURCE, CANNOT BE REDEFINED
IST134I GROUP = GP3ATR10, MAJOR NODE = NCP3AB8
IST1500I STATE TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - NO
IST1657I MAJOR NODE VTAMTOPO = IGNORE
IST314I END

Displaying a logical line in an XCA major node:

d net,id=ln1a2a
IST097I DISPLAY ACCEPTED
IST075I NAME = LN1A2A, TYPE = LINE
IST486I STATUS= NEVAC, DESIRED STATE= INACT
IST087I TYPE = SWITCHED DIAL-INOUT, CONTROL = SDLC, HPDT = *NA*
IST936I ANSWER MODE = RESET
IST134I GROUP = GP1A2A, MAJOR NODE = XCA1A
IST1500I STATE TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST1657I MAJOR NODE VTAMTOPO = REPORT
IST314I END

Displaying a switched major node:

d net,id=swxca1a,e
IST097I DISPLAY ACCEPTED
IST075I NAME = SWXCA1A, TYPE = SW SNA MAJ NODE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST084I NETWORK RESOURCES:
IST089I SW1A2A TYPE = PU_T2 , CONCT
IST089I SW1A7B TYPE = PU_T2 , CONCT
IST089I SW1A9C TYPE = PU_T2 , CONCT
IST089I SW1AAA TYPE = PU_T2 , CONCT
IST089I SW1ABA TYPE = PU_T2 , CONCT
IST089I SW1ACA TYPE = PU_T2 , CONCT
IST089I SW1ADA TYPE = PU_T2 , CONCT
IST089I SW1AEA TYPE = PU_T2 , CONCT
IST1500I STATE TRACE = OFF
IST314I END

Displaying a switched PU in this Switched major node:

d net,id=sw1a2a
IST097I DISPLAY ACCEPTED
IST075I NAME = SW1A2A, TYPE = PU_T2
IST486I STATUS= CONCT, DESIRED STATE= CONCT
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST136I SWITCHED SNA MAJOR NODE = SWXCA1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1656I VTAMTOPO = NOREPORT, NODE REPORTED - YES
IST1657I MAJOR NODE VTAMTOPO = INCLUDE
IST314I END

Displaying a cross-subarea SDLC link:

d net,id=a04c08,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04C08, TYPE = LINE
IST486I STATUS= NEVAC , DESIRED STATE= INACT
IST087I TYPE = LEASED , CONTROL = SDLC, HPDT = *NA*

Chapter 2. VTAM Operator Commands 117

DISPLAY ID
IST134I GROUP = A04XCA0, MAJOR NODE = A0462ZC
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A04P08A NEVAC 1 1 0
IST314I END

Displaying a cross-subarea channel link:

d net,id=012-l,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = 012-L, TYPE = LINE
IST486I STATUS= ACTIV----I , DESIRED STATE = ACTIV
IST087I TYPE = LEASED , CONTROL = NCP , HPDT = *NA*
IST134I GROUP = ISTGROUP, MAJOR NODE = A99MPU
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I 012-S ACTIV----I 1 1 A03N43A 3
IST314I END

Displaying a cross-subarea channel link station:

d net,id=012-s,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = 012-S, TYPE = LINK STATION
IST486I STATUS= ACTIV----I , DESIRED STATE = ACTIV
IST081I LINE NAME = 012-L, LINE GROUP = ISTGROUP, MAJNOD = A99MPU
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I 012-S ACTIV----I 1 1 A03N43A 3
IST610I LINE 012-L - STATUS ACTIV----I
IST314I END

Displaying a cross-subarea SDLC link station:

d net,id=a03p644,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A03P644, TYPE = LINK STATION
IST486I STATUS= NEVAC , DESIRED STATE = INACT
IST081I LINE NAME = A03IN64, LINE GROUP = A03MPRI, MAJNOD = A03N43A
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A03P644 NEVAC 2 2 0
IST610I LINE A03IN64 - STATUS NEVAC
IST314I END

Displaying a physical unit:

d net,id=a03p011,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A03P011, TYPE = PU_T2.1
IST486I STATUS= ACTIV , DESIRED STATE = ACTIV
IST081I LINE NAME = A03IN01, LINE GROUP = A03MPRI, MAJNOD = A03N43A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST355I LOGICAL UNITS:
IST080I A03L011A NEVAC A03L011B NEVAC A03L011C NEVAC
IST080I A03L011D NEVAC A03L011E NEVAC A03L011F NEVAC
IST080I A03L011G NEVAC A03L011H NEVAC A03L011I NEVAC
IST080I A03L011J NEVAC A03L011K NEVAC A03L011L NEVAC
IST080I A03L011M NEVAC A03L011N NEVAC A03L011O NEVAC
IST314I END

Displaying a physical unit with APPN host-to-host connectivity:

d net,id=ahhcpu1
IST097I DISPLAY ACCEPTED
IST075I NAME = AHHCPU1, TYPE = PU_T2.1 388
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I AHHCPU1 AC/R 21 YES 988D0000000000000000014C00808080
IST1482I HPR = RTP - OVERRIDE = N/A - CONNECTION = YES

118 SNA Operation

 DISPLAY ID
IST1510I LLERP = REQUIRED - RECEIVED = REQUIRED
IST136I LOCAL SNA MAJOR NODE = LSAHHC1
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1314I TRLE = TRLE1A STATUS = ACTIV CONTROL = MPC
IST314I END

Displaying a physical unit with DLUR support:

d net,id=aa1pua,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = AA1PUA, TYPE = PU_T2
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1043I CP NAME = ***NA***, CP NETID = NETA, DYNAMIC LU = YES
IST1354I DLUR NAME = NNCPA1 MAJNODE = SWDLR1A
IST136I SWITCHED SNA MAJOR NODE = SWDLR1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST355I LOGICAL UNITS:
IST080I AA1LUA1 ACT/S AA1LUA2 ACTIV AA1LUA3 ACTIV
IST080I AA1LUA4 ACTIV
IST314I END

Displaying a rapid transport protocol (RTP) physical unit:

| d net,id=cnr00001,scope=all
| IST097I DISPLAY ACCEPTED
| IST075I NAME = CNR00001, TYPE = PU_T2.1
| IST1392I DISCNTIM = 00010 DEFINED AT PU FOR DISCONNECT
| IST486I STATUS= ACTIV--LX-, DESIRED STATE= ACTIV
| IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
| IST1589I XNETALS = YES
| IST875I APPNCOS TOWARDS RTP = CPSVCMG
| IST1476I TCID X'333A9CA800000069' - REMOTE TCID X'333A9E6100000031'
| IST1481I DESTINATION CP NETA.SSCP2A - NCE X'D400000000000000'
| IST1587I ORIGIN NCE X'D400000000000000'
| IST1477I ALLOWED DATA FLOW RATE = 1600 KBITS/SEC
| IST1516I INITIAL DATA FLOW RATE = 1600 KBITS/SEC
| IST1511I MAXIMUM NETWORK LAYER PACKET SIZE = 16413 BYTES
| IST1478I NUMBER OF UNACKNOWLEDGED BUFFERS = 0
| IST1479I RTP CONNECTION STATE = CONNECTED - MNPS = NO
| IST1697I RTP PACING ALGORITHM = ARB RESPONSIVE MODE
| IST1480I RTP END TO END ROUTE - PHYSICAL PATH
| IST1460I TGN CPNAME TG TYPE HPR
| IST1461I 21 NETA.SSCP2A APPN RTP
| IST231I RTP MAJOR NODE = ISTRTPMN
| IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
| IST1500I STATE TRACE = OFF
| IST355I LOGICAL UNITS:
| IST080I SSCP2A ACT/S----Y
| IST314I END

Displaying an HPR-capable PU:

d net,id=p3a21aa1
IST097I DISPLAY ACCEPTED
IST075I NAME = AHHCPU1, TYPE = PU_T2.1 388
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I AHHCPU1 AC/R 21 YES 988D0000000000000000014C00808080
IST1482I HPR = RTP - OVERRIDE = N/A - CONNECTION = YES
IST1510I LLERP = REQUIRED - RECEIVED = REQUIRED
IST136I LOCAL SNA MAJOR NODE = LSAHHC1
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1314I TRLE = TRLE1A STATUS = ACTIV CONTROL = MPC
IST314I END

Chapter 2. VTAM Operator Commands 119

 DISPLAY ID
Displaying a switched link station:
d net,id=swpux2a1,e
IST097I DISPLAY ACCEPTED
IST075I NAME = SWPUX2A1, TYPE = PU_T2.1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I SWPUX2A1 AC/R 22 YES 982D0000000000000000017100808080
IST1482I HPR = NONE - OVERRIDE = N/A - CONNECTION = NO
IST136I SWITCHED SNA MAJOR NODE = SWND3AB8
IST081I LINE NAME = LN3AXN11, LINE GROUP = GP3AXN10, MAJNOD = NCP3AB8
IST1068I PHYSICAL RESOURCE (PHYSRSC) = P3AXN10
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1656I VTAMTOPO = NOREPORT, NODE REPORTED - YES
IST1657I MAJOR NODE VTAMTOPO = INCLUDE
IST172I NO LOGICAL UNITS EXIST
| IST314I END

Displaying a switched PU type 2:

d net,id=a04p501,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04P501, TYPE = PU_T2
IST486I STATUS= CONCT , DESIRED STATE = CONCT
IST136I SWITCHED SNA MAJOR NODE = A04SG1
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST1657I MAJOR NODE VTAMTOPO = INCLUDE
IST355I LOGICAL UNITS:
IST080I A04L501A CONCT A04L501B CONCT A04L501C CONCT
IST080I A04L501D CONCT A04L501E CONCT A04L501F CONCT
IST080I A04L501G CONCT A04L501H CONCT A04L501I CONCT
IST080I A04L501J CONCT A04L501K CONCT A04L501L CONCT
IST080I A04L501M CONCT A04L501N CONCT A04L501O CONCT
IST314I END

Displaying a switched PU type 2.1 (AS/400):

d net,id=a04p882,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A04P882, TYPE = PU_T2.1
IST486I STATUS= ACTIV--L-- , DESIRED STATE= ACTIV
IST1043I CP NAME = A04P882A, CP NETID = NETY, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I A04P882 AC/R 21 YES 802D0000000000000000017100000000
IST136I SWITCHED SNA MAJOR NODE = A04SMNC
IST081I LINE NAME = J000401B, LINE GROUP = A04BLG1, MAJNOD = A0462ZC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST355I LOGICAL UNITS:
IST080I A04I8823 ACT/S A04I8822 ACT/S A04P882A ACT/S----Y
IST080I A04I8821 ACT/S
IST314I END

Displaying a local SNA physical unit:

d net,id=pua,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = PUA, TYPE = PU_T2
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST136I LOCAL SNA MAJOR NODE = A50LSNA
IST077I SIO = *NA* CUA = 0770
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF

120 SNA Operation

 DISPLAY ID
IST355I LOGICAL UNITS:
IST080I LSNALU1 ACTIV LSNALU2 ACTIV LSNALU3 ACTIV
IST080I LSNALU4 ACTIV
IST314I END

Displaying a dynamic XCF local SNA physical unit:

d net,id=istp0001,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTP0001, TYPE = PU_T2.1
IST486I STATUS= ACTIV--LX-, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I ISTP0001 AC/R 21 YES 988D0000000000000000014C0080808
IST1482I HPR = NONE - OVERRIDE = N/A - CONNECTION = NO
IST136I LOCAL SNA MAJOR NODE = ISTLSXCF
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1314I TRLE = ISTT0001 STATUS = ACTIV----E CONTROL = XCF
IST355I LOGICAL UNITS:
IST080I SSCP2A ACT/S----Y
IST314I END

Displaying a dynamic XCF local SNA physical unit, specifying the control point
name:
d net,id=sscp2a,idtype=xcfcp
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTP0001, TYPE = PU_T2.1
IST486I STATUS= ACTIV--LX-, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I ISTP0001 AC/R 21 YES 988D0000000000000000014C00808080
IST1482I HPR = NONE - OVERRIDE = N/A - CONNECTION = NO
IST136I LOCAL SNA MAJOR NODE = ISTLSXCF
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1314I TRLE = ISTT0001 STATUS = ACTIV----E CONTROL = XCF
IST314I END

Displaying a logical unit under an NCP:

d net,id=a04dxxx1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.A04DXXX1, TYPE = LOGICAL UNIT
IST486I STATUS= NEVAC----T , DESIRED STATE= INACT
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT 00000001
IST081I LINE NAME = A04VXX, LINE GROUP = A04XNPAX, MAJNOD = A0462ZC
IST135I PHYSICAL UNIT = A04NXXX
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

Displaying a switched logical unit:

d net,id=a3ld0711,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = A31D0711, TYPE = LOGICAL UNIT
IST486I STATUS= NEVAC , DESIRED STATE= INACT
IST1447I REGISTRATION TYPE = CDSERVR

Chapter 2. VTAM Operator Commands 121

DISPLAY ID
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=CRYPTLOG USSTAB=AUSSTAB LOGTAB=INTERP
IST934I DLOGMOD=REQENCRP USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT 00000001
IST136I SWITCHED SNA MAJOR NODE = SMNDDNN
IST135I PHYSICAL UNIT = A31P021
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

Displaying a local SNA logical unit:

d net,id=lsnalu1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.LSNALU1, TYPE = LOGICAL UNIT
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=AMODETAB USSTAB=AUSSTAB LOGTAB=***NA***
IST934I DLOGMOD=D4A32782 USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT 00000001
IST136I LOCAL SNA MAJOR NODE = A50LSNA
IST135I PHYSICAL UNIT = PUA , CUA = 0770
IST082I DEVTYPE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END

Displaying a local non-SNA logical unit:

d net,id=a50a721,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.A50A721, TYPE = LOGICAL UNIT
IST486I STATUS= ACT/S , DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=AMODETAB USSTAB=AUSSTAB LOGTAB=INTERP
IST934I DLOGMOD=M23270I USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU ENABLED ,SESSION LIMIT 00000001
IST351I LOCAL 3270 MAJOR NODE = A50LOCAL
IST077I SIO = 00010 CUA = 0721
IST1131I DEVICE = LU
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000001
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I ECHOC1C ACTIV-P D73BC0750F6AE8F3 0000 0001 0 0 NETC
IST635I ECHO50B PREALC-P ECC39EEE2AA3BC6E NETA
IST314I END

Displaying a native ATM permanent virtual channel (PVC):

d net,id=lnp1a2a1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = LNP1A2A1, TYPE = LINE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = SDLC, HPDT = *NA*
IST1554I PVCNAME = PV11211
IST134I GROUP = GPP1A1, MAJOR NODE = XCAOSA1A
IST1500I STATE TRACE = OFF
IST084I NETWORK RESOURCES:
IST089I PP1A2A1 TYPE = PU_T2.1 , ACTIV
IST314I END

122 SNA Operation

 DISPLAY ID
Displaying a remote node connected through a native ATM PVC:
d net,id=pp1a2a1,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = PP1A2A1, TYPE = PU_T2.1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I PP1A2A1 AC/R 21 YES 182D0000000000000000017100808080
IST1482I HPR = RTP - OVERRIDE = N/A - CONNECTION = YES
IST1510I LLERP = REQUIRED - RECEIVED = REQUIRED
IST1555I VPCI/VCI = 010100
IST081I LINE NAME = LNP1A2A1, LINE GROUP = GPP1A1, MAJNOD = XCAOSA1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST172I NO LOGICAL UNITS EXIST
IST314I END

Displaying a remote node connected through a native ATM switched virtual channel
(SVC):
d net,id=sw1a2a,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = SW1A2A, TYPE = PU_T2.1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
IST1589I XNETALS = YES
IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
IST1106I SW1A2A AC/R 22 YES 182D0000000000000000017100808080
IST1482I HPR = RTP - OVERRIDE = N/A - CONNECTION = YES
IST1510I LLERP = REQUIRED - RECEIVED = REQUIRED
IST1559I ATM ADDRESS TYPE FORMAT
IST1553I 1111111111111111111111111111111111111100 LOCAL NSAP
IST1553I 2111111111111111111111111111111111111110 REMOTE NSAP
IST1555I VPCI/VCI = 010200
IST136I SWITCHED SNA MAJOR NODE = SWXCA1A
IST081I LINE NAME = LN1A2A, LINE GROUP = GP1A2A, MAJNOD = XCAOSA1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST1656I VTAMTOPO = NOREPORT, NODE REPORTED - YES
IST1657I MAJOR NODE VTAMTOPO = INCLUDE
IST355I LOGICAL UNITS:
IST080I SW1A2AL NEVAC
IST314I END

| Displaying a remote node connected through Enterprise Extender:

| d net,id=sw1a2a,scope=all
| IST097I DISPLAY ACCEPTED
| IST075I NAME = SW1A2A, TYPE = PU_T2.1
| IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
| IST1043I CP NAME = SSCP2A, CP NETID = NETA, DYNAMIC LU = YES
| IST1589I XNETALS = YES
| IST1105I RESOURCE STATUS TGN CP-CP TG CHARACTERISTICS
| IST1106I SW1A2A AC/R 22 YES 182D0000000000000000017100808080
| IST1482I HPR = RTP - OVERRIDE = N/A - CONNECTION = YES
| IST1510I LLERP = REQUIRED - RECEIVED = REQUIRED
| IST1680I LOCAL IP ADDRESS 9.18.100.2
| IST1680I REMOTE IP ADDRESS 223.254.254.1
| IST136I SWITCHED SNA MAJOR NODE = SWXCA1
| IST081I LINE NAME = LN1A2A, LINE GROUP = GP1A2A, MAJNOD = XCAHPR1A
| IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
| IST1500I STATE TRACE = OFF
| IST355I LOCAL UNITS:
| IST080I SW1A2AL NEVAC
| IST314I END
|

Chapter 2. VTAM Operator Commands 123

DISPLAY ID

Displaying a resource name that is known in several networks:

d net,id=*.applb12,max=3
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.APPLB12, TYPE = APPL
IST486I STATUS= CONCT , DESIRED STATE= CONCT
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NONE
IST231I APPL MAJOR NODE = APPL1A
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME = ***NA***
IST228I ENCRYPTION = OPTIONAL
IST1563I CKEYNAME = APPLB12 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST924I -------------------------------------------------------------
IST075I NAME = NETB.APPLB12, TYPE = CDRSC
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = CDRSC1A
IST479I CDRM NAME = SSCP7B , VERIFY OWNER = NO
IST1131I DEVICE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = APPLB12 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST924I -------------------------------------------------------------
IST075I NAME = NETC.APPLB12, TYPE = CDRSC
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT NONE
IST231I CDRSC MAJOR NODE = CDRSC1A
IST479I CDRM NAME = SSCP9C , VERIFY OWNER = NO
IST1131I DEVICE = CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = APPLB12 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST314I END

Displaying a generic resource name:

d net,id=A0418863,idtype=generic
IST097I DISPLAY ACCEPTED
IST075I NAME = GRAPPL, TYPE = GENERIC RESOURCE
IST1359I MEMBER NAME OWNING CP SELECTABLE APPC
IST1360I NETA.NETAPPL1 SSCP2A YES NO
IST1360I NETA.APPL1 SSCP1A NO NO
IST1360I NETA.APPLAA1 SSCPAA YES NO
IST1393I GENERIC RESOURCE NAME RESOLUTION EXIT IS ISTEXCGR
IST314I END

124 SNA Operation

 DISPLAY ID
| Displaying an IP address in dotted decimal format when there is only one
| TN3270-client connected at this IP address.
| D NET,IDTYPE=IPADDR,ID=9.37.82.125
| IST097I DISPLAY ACCEPTED
| IST075I NAME = NETA.TCPM1004, TYPE = APPL 367
| IST486I STATUS= ACT/S , DESIRED STATE=ACTIV
| IST1447I REGISTRATION TYPE=NO
| IST977I MDLTAB=***NA*** ASLTAB=***NA***
| IST861I MODETAB= USSTAB= LOGTAB=
| IST934I DLOGMODE= USS LANGTAB=
| IST597I CAPABILITY-PLU ENABLED, SLU ENABLED, SESSION
| LIMIT 000000 01
| IST231I APPL MAJOR NODE = TCPMS0US
| IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
| IST1500I STATE TRACE = OFF
| IST271I JOBNAME =
| IST1050I MAXIMUM COMPRESSION LEVEL -
| IST1669I IPADDR..PORT 9.37.82.125..1785
| IST171I ACTIVE SESSIONS = 0000000001, SESSION
| REQUESTS = 0000000000
| IST317I END
|
|

| Displaying a TN3270 connected client.

| D NET,ID=TCPM1004
| IST097I DISPLAY ACCEPTED
| IST075I NAME = NETA.TCPM1004, TYPE = APPL 367
| IST486I STATUS= ACT/S , DESIRED STATE=ACTIV
| IST1447I REGISTRATION TYPE=NO
| IST977I MDLTAB=***NA*** ASLTAB=***NA***
| IST861I MODETAB= USSTAB= LOGTAB=
| IST934I DLOGMODE= USS LANGTAB=
| IST597I CAPABILITY-PLU ENABLED, SLU ENABLED, SESSION
| LIMIT 000000 01
| IST231I APPL MAJOR NODE = TCPMS0US
| IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
| IST1500I STATE TRACE = OFF
| IST271I JOBNAME =
| IST1050I MAXIMUM COMPRESSION LEVEL -
| IST1669I IPADDR..PORT 9.37.82.125..1785
| IST171I ACTIVE SESSIONS = 0000000001, SESSION
| REQUESTS = 0000000000
| IST317I END
|
|

| Displaying an IP address with multiple TN3270-client connections.

| D NET,IDTYPE=IPADDR,ID=9.37.82.123
| IST097I DISPLAY ACCEPTED
| IST1668I LUNAME IPADDR..PORT
| IST1670I NETA.TCPM1004 9.37.82.123..1785
| IST1670I NETA.TCPM1002 9.37.82.123..1802
| IST1670I NETA.TCPM1001 9.37.82.123..1775
| IST314I END

Chapter 2. VTAM Operator Commands 125

DISPLAY LINES

DISPLAY LINES Command

ÊÊ DISPLAY NET,LINES Ê
(1)
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value
Ê Ê
,MAX= * ,OWNER= host_name
number_of_resources *NONE

,SCOPE=ALL
Ê ÊÍ
ALL ,USE= DEFINED
,SCOPE= SPARE

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
USE=DEFINED DEFINED
USE=SPARE SPARE
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

126 SNA Operation

 DISPLAY LINES
Purpose
The DISPLAY LINES command displays the status of lines and channel links in the
domain.

Note: To display lines and channel links independently of the major nodes that
contain them, use the DISPLAY RSCLIST command with IDTYPE=LINES.

Operands
ID=name
specifies the name of one or more active NCP, channel-attachment, or XCA
major nodes whose subordinate lines and channel links are to be displayed.

If OWNER is also specified on this command, the value of ID must match the
name of an NCP major node.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every NCP, channel-attachment, and XCA major node in the
network.
MAX
specifies the maximum number of lines and channel links that VTAM displays
for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of lines and channel links that VTAM displays for this
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer lines or channel links are found than
you have specified on MAX, VTAM displays only the lines and channel links
that are found.
OWNER
specifies whether lines and channel links defined with the OWNER operand are
to be displayed. This operand is only valid when the name or the wildcard value
specified on the ID operand matches the name of an NCP major node.
OWNER=host_name
specifies that only lines and channel links whose owning SSCP (as
determined by the OWNER operand on the GROUP or LINE definition
statements) matches the host_name specified are to be displayed.
OWNER=*NONE
specifies that only lines and channel links without an OWNER operand on
the GROUP or LINE definition statements are to be displayed.

Chapter 2. VTAM Operator Commands 127

DISPLAY LINES
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable lines and channel links within the specified major nodes (or
within all NCP, channel-attachment, and XCA major nodes if the ID operand
is omitted). If this display is undesirably large, you can use
SCOPE=ACTONLY or SCOPE=CONCT to further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all lines and channel links
in an active state within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).
The display does not include lines and channel links in pending or
connectable states. If no lines or channel links are found in an active state,
you can use SCOPE=ACT to broaden the scope of the display to include
those in active, connectable, and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all lines and channel links
that are active with sessions within the specified major nodes (or within all
NCP, channel-attachment, and XCA major nodes if the ID operand is
omitted).
SCOPE=ALL
specifies that information is to be displayed about all lines and channel links
(regardless of their status) within the specified major nodes (or within all
NCP, channel-attachment, and XCA major nodes if the ID operand is
omitted).
SCOPE=CONCT
specifies that information is to be displayed about all lines and channel links
in a CONCT (connectable) state within the specified major nodes (or within
all NCP, channel-attachment, and XCA major nodes if the ID operand is
omitted). If no lines or channel links are found in a connectable state, you
can use SCOPE=ACT to broaden the scope of the display to include those
in active, connectable, and pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive lines and
channel links within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted). If
this display is undesirably large, you can use SCOPE=INACTONLY or
SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive lines and
channel links within the specified major nodes (or within all major nodes if
the ID operand is omitted). Resources in a RESET state are not included in
the SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending lines and
channel links within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted). A
pending state is a transient state to or from the fully active state.

128 SNA Operation

 DISPLAY LINES
SCOPE=RESET
specifies that information is to be displayed about all lines and channel links
in a RESET state within the specified major nodes (or within all NCP,
channel-attachment, and XCA major nodes if the ID operand is omitted).
USE
specifies whether information is to be displayed about lines that are currently
designated as DEFINED or SPARE. If you do not specify USE, information
about both spare and defined lines is displayed.
USE=DEFINED
specifies that information is to be displayed only about lines that are
currently usable.
USE=SPARE
specifies that information is to be displayed only about spare lines.

Resulting Display
VTAM displays the name and status of each line within the specified major node (or
within all major nodes containing lines if ID is omitted). The display is limited to
active, inactive, or pending minor nodes if specified on the SCOPE operand.

Examples
Displaying all lines:
d net,lines
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LINES
IST354I PU T4/5 MAJOR NODE = ISTPUS
IST170I LINES:
IST080I 0016-L ACTIV----I 0017-L ACTIV----I
IST354I PU T4/5 MAJOR NODE = A0462ZC
IST170I LINES:
IST080I A04B00 NEVAC A04B01 NEVAC A04B03 NEVAC
IST080I A04B32 NEVAC A04B33 NEVAC A04B35 NEVAC
IST080I A04VXX NEVAC----T A04S02 NEVAC A04S34 NEVAC
IST080I A04S04 NEVAC A04S16 NEVAC A04S20 NEVAC
IST080I A04S36 NEVAC A04S48 NEVAC A04S52 NEVAC
IST080I A04S128 NEVAC A04S136 NEVAC A04PT88 ACTIV
IST080I A04PT89 NEVAC A04PT92 NEVAC J0004001 ACTIV
IST080I J0004003 ACTIV J0004005 ACTIV J0004007 ACTIV
IST080I J0004009 ACTIV J000400B ACTIV J000400D ACTIV
IST080I J000400F ACTIV J0004011 ACTIV J0004013 ACTIV
IST080I A04C00 NEVAC A04C02 NEVAC
IST314I END

Displaying all lines within a specific major node:

d net,lines,id=a0362zc
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LINES
IST354I PU T4/5 MAJOR NODE = A0362ZC
IST170I LINES:
IST080I A03B00 NEVAC A03B01 NEVAC A03B32 NEVAC
IST080I A03B33 NEVAC A03VXX NEVAC----T A03S02 NEVAC
IST080I A03S16 ACTIV A03S20 ACTIV A03S128 NEVAC
IST080I A03PT88 ACTIV A03PT89 ACTIV J0003001 ACTIV
IST080I J0003003 ACTIV J0003005 ACTIV J0003007 ACTIV
IST080I J0003009 ACTIV J000300B ACTIV J000300D ACTIV
IST080I J000300F ACTIV J0003011 ACTIV J0003013 ACTIV
IST080I J0003015 ACTIV J0003017 ACTIV J0003019 ACTIV
IST080I J000301B ACTIV J000301D ACTIV J000301F NEVAC

Chapter 2. VTAM Operator Commands 129

DISPLAY LINES
IST080I J0003021 NEVAC J0003023 NEVAC J0003025 NEVAC
IST080I J0003027 NEVAC J0003029 NEVAC J000302B NEVAC
IST080I J000302D NEVAC J000302F NEVAC J0003031 ACTIV
IST080I J0003033 ACTIV J0003035 ACTIV J0003037 ACTIV
IST080I J0003039 ACTIV J000303B ACTIV J000303D ACTIV
IST080I J000303F ACTIV J0003041 ACTIV J0003043 ACTIV
IST080I J0003045 ACTIV J0003047 ACTIV J0003049 ACTIV
IST080I J000304B ACTIV J000304D ACTIV J000304F NEVAC
IST080I A03C08 NEVAC A03C10 NEVAC A03C00 NEVAC
IST080I A03C02 NEVAC
IST314I END

Displaying all lines owned by a specific SSCP:

d net,lines,owner=sscp1a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LINES
IST354I PU T4/5 MAJOR NODE = NCP3AA1
IST170I LINES:
IST080I LN3A1 NEVAC LN3A7 NEVAC LN3A4 NEVAC
IST080I LN3A4A1 NEVAC LN3A4A2 NEVAC LN3A4A3 NEVAC
IST080I LN3A4A4 NEVAC LN3A4AM NEVAC LN3A5A1 NEVAC
IST080I LN3A5A2 NEVAC LN3A8A1 NEVAC
IST314I END

Displaying lines, limiting output to 3 resources:

d net,lines,max=3
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LINES
IST354I PU T4/5 MAJOR NODE = NCP3AA1
IST170I LINES:
IST080I LN3A1 NEVAC LN3A6 NEVAC LN3A7 NEVAC
IST1315I DISPLAY TRUNCATED AT MAX = 3
IST1454I 3 RESOURCE(S) DISPLAYED
IST314I END

130 SNA Operation

 DISPLAY LMTBL

DISPLAY LMTBL Command

Display partner LUs in LU-mode table:

,SCOPE=ONLY
ÊÊ DISPLAY NET,LMTBL ,ID=appl_name ,TYPE=LUNAME ÊÍ
ALL
,SCOPE=

ONLY
ALL

Display logon mode names in LU-mode table:

ÊÊ DISPLAY NET,LMTBL ,ID=appl_name ,LUNAME=lu_name ,TYPE=LOGMODE ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
LUNAME LU
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

Purpose
The DISPLAY LMTBL (LU-mode table) command displays information contained in
the LU-mode table. It shows either all logon mode names defined for an application
program and its partner LU or the names of all partner LUs for the specified
application program.

Operands
ID=appl_name
specifies the name of the LU 6.2 application program to which the requested
information applies. appl_name cannot be a network-qualified name.
LUNAME=lu_name
specifies the name of the partner LU to which the requested logon mode
information applies. LUNAME is required for TYPE=LOGMODE. The name can
be a network-qualified name in the form of netid.luname.

If PARMS=(NQNAMES=NO) is coded on the ACB macro of the resource named

on the ID operand, and a network-qualified name is specified, the network
identifier is ignored.

If PARMS=(NQNAMES=YES) is coded on the ACB macro, luname can be

either a non-network-qualified name or a network-qualified name. If luname is a
non-network-qualified name, the command is processed against all LUs with
that non-network-qualified name across all networks. If luname is a
network-qualified name, the command is processed against the LU in the
specified network.

Chapter 2. VTAM Operator Commands 131

DISPLAY LMTBL
SCOPE
specifies the desired scope of the display. SCOPE is valid only when
TYPE=LUNAME is specified.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ALL
specifies that additional information is to be displayed about the partner LUs
stored in the LU-mode table.
SCOPE=ONLY
specifies that additional information is not to be displayed.
TYPE
specifies the type of information you want to display.
TYPE=LUNAME
displays the names of all partner LUs that are defined in the LU-mode table
for the LU 6.2 application program specified.
TYPE=LOGMODE
displays the logon mode names defined in the LU-mode table for the
application program and partner LU specified.

Resulting Display
The resulting VTAM display shows:
v For TYPE=LUNAME:
– SCOPE=ONLY
- The name of the specified application program
- The name of each partner LU associated with the specified application
program
– SCOPE=ALL
- The type of LU entry which contains the partner LU definitions
- The other name, if any, the partner LU is known by
v For TYPE=LOGMODE:
– The name of the specified application program and partner LU
– The name of logon modes associated with the partner LUs of the specified
application program.

Examples
Displaying logon mode names in LU-mode table:
d net,lmtbl,type=logmode,id=echo50b,luname=netc.echoc1a
IST097I DISPLAY ACCEPTED
IST1006I LOGMODE NAMES DEFINED IN LU NETC.ECHOC1A FOR ECHO50B
IST988I SNASVCMG BATCH
IST314I END

Displaying partner LUs in LU-mode table:

d net,lmtbl,type=luname,id=echo50b
IST097I DISPLAY ACCEPTED
IST1006I LU NAMES DEFINED FOR ECHO50B
IST1154I NETC.ECHOC1A
IST314I END

132 SNA Operation

 DISPLAY LMTBL
Displaying partner LUs in LU-mode table with LU entry types and associated
names:
d net,lmtbl,type=luname,id=appcap06,scope=all
IST097I DISPLAY ACCEPTED
IST1006I LU NAMES DEFINED FOR APPCAP06 397 00003
IST1409I NETA.APPCAP05 ASSOC = NETA.TOM ETYPE = SUPPLIED
IST1409I NETA.TOM ASSOC = NETA.APPCAP05 ETYPE = VARIANT
IST314I END

Chapter 2. VTAM Operator Commands 133

DISPLAY LUGROUPS

DISPLAY LUGROUPS Command

Display all LUGROUP major nodes:

ÊÊ DISPLAY NET,LUGROUPS Ê

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources

Display a specific LUGROUP major node:

ÊÊ DISPLAY NET,LUGROUPS ,ID=lugroup_major_node_name Ê

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources

Display a model LU group:

ÊÊ DISPLAY NET,LUGROUPS ,ID=model_lu_group Ê

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources

Display a model LU:

ÊÊ DISPLAY NET,LUGROUPS ,ID=model_lu_name ,GROUP=model_lu_group Ê

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources

134 SNA Operation

 DISPLAY LUGROUPS
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY LUGROUPS (logical unit groups) command provides information
about LUGROUP major nodes, model LU groups, and specific model LUs within an
LU group.

Operands
GROUP=model_lu_group
specifies the name of a model LU group. This operand is valid only if the ID
operand specifies a model LU. It is required if the ID operand specifies a model
LU to indicate which model LU group to search. Because two different model
LU groups can contain model LUs with the same name, this specification of
which model LU group to search is necessary.
ID=name
specifies the name of one the following:
v LUGROUP major node
v Model LU group
v Model LU.
MAX
specifies the maximum number of resources that VTAM displays for this
command.

The MAX operand is only valid when SCOPE=ALL is specified.

MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of resources to display for this command. The valid
range is 1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer resources are found than you have
specified on MAX, VTAM displays only the resources that are found.

Chapter 2. VTAM Operator Commands 135

DISPLAY LUGROUPS
SCOPE
specifies what LUGROUP resources are displayed. The results depend on
whether an ID is specified and whether SCOPE is specified as ONLY or ALL.
SCOPE=ALL
specifies that the requested node and all its subordinate nodes be
displayed.
SCOPE=ONLY
specifies that only the requested nodes be displayed.

Resulting Display
The resulting VTAM display shows:
v If ID is not specified:
– For SCOPE=ONLY, all LUGROUP major nodes
– For SCOPE=ALL, all LUGROUP major nodes, their model LU groups, and
their model LUs
v If ID specifies an LUGROUP major node:
– For SCOPE=ONLY, each of the LU groups within the specified LUGROUP
major node
– For SCOPE=ALL, the specified LUGROUP major node, its model LU groups,
and their model LUs
v If ID specifies a model LU group:
– For SCOPE=ONLY, the specified model LU group, verifying that it is active
– For SCOPE=ALL, the specified model LU group and its model LUs
v If ID specifies a model LU and GROUP specifies a model LU group:
– For SCOPE=ONLY, the specified model LU, verifying that it exists within the
specified model LU group
– For SCOPE=ALL, the characteristics of the specified model LU.

Examples
Displaying all LU groups:
d net,lugroups,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LUGROUP MAJOR NODES
IST1060I LUGROUP MAJOR NODE = LUGRP50
IST075I NAME = LARRY, TYPE = MODEL LU GROUP
IST355I LOGICAL UNITS:
IST080I 3194@00 3194000 @@90001
IST080I 329000@ 327@@01 9373@
IST080I 9375@ 3270@ @
IST075I NAME = CURLY, TYPE = MODEL LU GROUP
IST355I LOGICAL UNITS:
IST080I 3194@ 3290@ 3270001
IST080I 3270@ @
IST075I NAME = MOE, TYPE = MODEL LU GROUP
IST355I LOGICAL UNITS:
IST080I 3194@ 3290@ 3270001
IST080I 3270@ @
IST314I END

Displaying a specific LUGROUP major node:

136 SNA Operation

 DISPLAY LUGROUPS
d net,lugroups,id=lugrp50
IST097I DISPLAY ACCEPTED
IST1060I LUGROUP MAJOR NODE = LUGRP50
IST075I NAME = LARRY, TYPE = MODEL LU GROUP
IST075I NAME = CURLY, TYPE = MODEL LU GROUP
IST075I NAME = MOE, TYPE = MODEL LU GROUP
IST314I END

Displaying a model LU group:

d net,lugroups,id=larry,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = LARRY, TYPE = MODEL LU GROUP
IST355I LOGICAL UNITS:
IST080I 3194@00 3194000 @@90001
IST080I 329000@ 327@@01 9373@
IST080I 9375@ 3270@ @
IST314I END

Displaying a model LU:

d net,lugroups,id=3194@00,group=larry,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.3194@00, TYPE = MODEL LU
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=***NA*** USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = 3194@00 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST314I END

Chapter 2. VTAM Operator Commands 137

DISPLAY MAJNODES

DISPLAY MAJNODES Command

,MAX=DSPLYDEF_start_option_value
ÊÊ DISPLAY NET,MAJNODES ÊÍ
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY MAJNODES (major nodes) command displays the status of all active
major nodes in the domain.

This command displays the status of all active major nodes, which include the
following major node types:
v Adjacent CP
v Application program
v Cross-domain resource manager (CDRM); in a multiple-domain network
v Channel-attachment
v Cross-domain resource (CDRSC); in a multiple-domain network (including
independent logical units)
v External communication adapter (XCA)
v Local SNA
v Local non-SNA
v LUGROUP
v Model
v NCP
v Rapid transport protocol (ISTRTPMN)
v Switched.

Note: NCP major nodes, which are type 4 physical units, are listed in the display
as PU T4/5 major nodes. The VTAM host physical unit, which is a type 5
physical unit, is listed in the display as a PU T4/5 major node.
Channel-attachment major nodes are listed in the display as CA major
nodes.

Operands
MAX
specifies the maximum number of active major nodes that VTAM displays for
this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of active major nodes that VTAM displays for this

138 SNA Operation

 DISPLAY MAJNODES
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer active major nodes are found than you
have specified on MAX, VTAM displays only the active major nodes that are
found.

Resulting Display
The resulting display gives the name, type, and status of each known major node.

Examples
Displaying major nodes:
d net,majnodes
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MAJOR NODES
IST089I VTAMSEG TYPE = APPL SEGMENT , ACTIV
IST089I ISTPUS TYPE = PU T4/5 , ACTIV
IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
IST089I ISTADJCP TYPE = ADJCP MAJOR NODE , ACTIV
IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV
IST089I ISTTRL TYPE = TRL MAJOR NODE , ACTIV
IST089I APPC1A TYPE = APPL SEGMENT , ACTIV
IST089I APPL1A TYPE = APPL SEGMENT , ACTIV
IST089I CDRM1A TYPE = CDRM SEGMENT , ACTIV
IST089I CDRSC1A TYPE = CDRSC SEGMENT , ACTIV
IST089I DSIAPPL1 TYPE = APPL SEGMENT , ACTIV
IST089I LOCAL1A TYPE = LCL 3270 MAJ NODE, ACTIV
IST089I ISTLSXCF TYPE = LCL SNA MAJ NODE , ACTIV
IST1454I 13 RESOURCE(S) DISPLAYED
IST314I END

Displaying major nodes: limiting output to 2 resources:

d net,majnodes,max=2
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MAJOR NODES
IST089I VTAMSEG TYPE = APPL SEGMENT , ACTIV
IST089I ISTPUS TYPE = PU T4/5 , ACTIV
IST1315I DISPLAY TRUNCATED AT MAX = 2
IST1454I 2 RESOURCE(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 139

DISPLAY MODELS

DISPLAY MODELS Command

,SCOPE=ONLY
ÊÊ DISPLAY NET,MODELS ÊÍ
,ID=model_name ,SCOPE= ONLY
ALL

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY MODELS command provides information about model resources,
excluding model applications.

VTAM can dynamically define switched PUs and LUs by defining a model major
node with descriptions of model PUs and LUs. When a switched device that has not
been defined to VTAM requests connection, VTAM copies these model descriptions
to build dynamic switched PUs and LUs. The DISPLAY MODELS command allows
you to view the models as defined by VTAM.

Operands
ID=model_name
specifies the model whose definition you want to view. This includes the model
major node and the individual model PU and LU devices.
SCOPE
specifies which model resources to display. The results depend on whether an
ID is specified and whether SCOPE is specified as ONLY or ALL.
SCOPE=ALL
If ID is not specified, SCOPE=ALL displays all model major nodes, model
PUs, and model LUs defined to VTAM.

If ID specifies a model major node name, SCOPE=ALL displays that major

node and its model PUs and LUs.

If ID specifies a model PU or LU, SCOPE=ALL displays information about

that model PU or LU.
SCOPE=ONLY
If ID is not specified, SCOPE=ONLY displays all model major nodes defined
to VTAM. No model PUs or LUs are displayed.

140 SNA Operation

 DISPLAY MODELS
If ID specifies a model major node name, SCOPE=ONLY displays
information about that major node. Its model PUs and LUs are not
displayed.

If ID specifies a model PU or LU, SCOPE=ONLY displays information about

that model PU or LU.

Resulting Display
The resulting VTAM display shows:
v If ID is specified:
– For SCOPE=ONLY, the name and type of the model node specified
– For SCOPE=ALL, the name and type of the model node specified and, for a
model major node, the name, type, and status its subordinate nodes
v If ID is not specified:
– For SCOPE=ONLY, all model major nodes
– For SCOPE=ALL, all model major nodes and the name, type, and status of
their subordinate nodes.

Examples
Displaying all model major nodes:
d net,models
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MODELS
IST1018I MODEL MAJOR NODE = A03MMNC
IST314I END

Displaying all model major nodes and their subordinate resources:

d net,models,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MODELS
IST1018I MODEL MAJOR NODE = A03MMNC
IST1017I MODELS:
IST089I A03MMNPU TYPE = PU_T2 , RESET
IST089I A03MMNLU TYPE = LOGICAL UNIT , RESET
IST314I END

Displaying a specific model major node and its subordinate resources:

d net,models,id=a03mmnc,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MODELS
IST075I NAME = A03MMNC, TYPE = MODEL MAJOR NODE
IST1656I VTAMTOPO = REPORT, NODE REPORTED - YES
IST1017I MODELS:
IST089I A03MMNPU TYPE = PU_T2 , RESET
IST089I A03MMNLU TYPE = LOGICAL UNIT , RESET
IST314I END

Displaying a specific PU in a model major node:

d net,models,id=a03mmnpu
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MODELS
IST075I NAME = A03MMNPU , TYPE = PHYSICAL UNIT
IST1018I MODEL MAJOR NODE = A03MMNC
IST314I END

Chapter 2. VTAM Operator Commands 141

DISPLAY MODELS
Displaying a specific LU in a model major node:
d net,models,id=a03mmnlu
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = MODELS
IST075I NAME = .A03MMNLU , TYPE = LOGICAL UNIT
IST1018I MODEL MAJOR NODE = A03MMNC
IST977I MDLTAB=MDLTAB1 ASLTAB=ASLTAB1
IST861I MODETAB=AMODETAB USSTAB=AUSSTAB LOGTAB=INTERP
IST934I DLOGMOD=M23278I USS LANGTAB=***NA***
IST1131I DEVICE = LU
IST228I ENCRYPTION = NONE
IST1563I CKEYNAME = A03MMNLU CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST314I END

142 SNA Operation

 DISPLAY NCPSTOR

DISPLAY NCPSTOR Command

ÊÊ DISPLAY NET,NCPSTOR ,ADDR=address ,ID=ncp_name Ê

,LENGTH=32 ,STORAGE=MAIN
Ê ÊÍ
,LENGTH=number_of_bytes ,STORAGE= DUMPMAIN
DUMPVEC
MAIN

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY NCPSTOR (NCP storage) command displays either the storage
contents of a communication controller running an NCP, or an NCP dump stored in
an IBM 3720 or 3745 Communication Controller. This command displays up to 256
(decimal) bytes from any address within the communication controller or the dump
stored in the IBM 3720 or 3745 Communication Controller.

Operands
ADDR=address
specifies the address (in hexadecimal) of the first byte of data to be displayed.
ID=ncp_name
specifies the name of the NCP whose storage is to be displayed.
LENGTH=number_of_bytes
specifies the number of bytes of NCP storage to be displayed. Any decimal
integer 1–256 can be specified. If LENGTH is omitted, VTAM displays 32 bytes
(the default).
STORAGE
specifies the type of storage to be displayed.
STORAGE=MAIN
displays the storage contents of an IBM 3720 or 3745 Communication
Controller running an NCP.
STORAGE=DUMPVEC
displays the state vector (also called the dump header) of the NCP stored in
the IBM 3720 or 3745 Communication Controller. The state vector contains
items such as the NCP registers, storage keys, program state, and
instruction addresses. The state vector is storage that is linearly
addressable in the range 0–511, depending on the communication controller
unit model. If the sum of the number_of_bytes specified for LENGTH and
the address specified for ADDR is greater than 511, then LENGTH is
modified to display the state vector from the address specified for ADDR to
511.
STORAGE=DUMPMAIN
displays the main part of an NCP dump stored on the IBM 3270 or 3745

Chapter 2. VTAM Operator Commands 143

DISPLAY NCPSTOR
Communication Controller. This dump portion is mapped byte for byte to the
main storage of the communication controller. The displayable address
range starts at main storage address 0 and ends at the address one byte
lower than the maximum storage installed on the communication controller
external storage.

Resulting Display
The resulting display shows:
v The type of storage
v The name of the NCP
v The contents of storage, in hexadecimal, with addresses.

Examples
Displaying the NCP storage executing in the controller:
d net,ncpstor,id=a0362zc,addr=0,storage=main
IST097I DISPLAY ACCEPTED
IST244I NCP MAIN STORAGE FOR ID = A0362ZC
IST245I 000000 714C01AA 719C09A8 B900000D B806B568
IST245I 000010 00000000 00000000 00000000 00000000
IST314I END
IST241I D NCPSTOR COMMAND COMPLETE FOR A0362ZC

Displaying the state vector of a dump stored on the controller:

d net,ncpstor,id=a0362zc,storage=dumpvec,addr=0
IST097I DISPLAY ACCEPTED
IST244I NCP DUMP VECTOR STORAGE FOR ID = A0362ZC
IST245I 000000 00800C02 011257AE 0001E088 00155994
IST245I 000010 00156648 001257A8 00155D40 0004D5E0
IST314I END
IST241I D NCPSTOR COMMAND COMPLETE FOR A0362ZC

Displaying the main portion of a dump stored on the controller:

d net,ncpstor,id=a0362zc,storage=dumpmain,addr=512,length=64
IST097I DISPLAY ACCEPTED
IST244I NCP DUMP MAIN STORAGE FOR ID = A0362ZC
IST245I 000512 2742 68140910 17180728 27BE9001
IST245I 000520 28D02539 CD0435D0 A8022458 BF40047A
IST245I 000530 A80E2539 D440E3E1 35D025B9 BF40047A
IST245I 000540 00700070 6513E47F 21390458 5180F560
IST245I 000550 8846
IST314I END
IST241I D NCPSTOR COMMAND COMPLETE FOR A0362ZC

144 SNA Operation

 DISPLAY NETSRVR

DISPLAY NETSRVR Command

,SCOPE=ALL
ÊÊ DISPLAY NET,NETSRVR ÊÍ
,SCOPE= ALL
ONLY

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY NETSRVR (network node server) command displays information
about network node servers. Enter this command at the end node whose server
information you want to display. This command is valid only when it is issued at an
end node or migration data host.

Operands
SCOPE
specifies the desired scope of the display.
SCOPE=ONLY
displays the network node server list that is currently active and displays
the current network node server.
SCOPE=ALL
displays, in addition to the information shown for SCOPE=ONLY, other
network nodes known to the end node that can act as network node
servers. Other network nodes are allowed as servers only if the current
network node server list contains a nameless entry.

Resulting Display
The resulting display shows:
v The contents of the active network node server list.
v For each network node in the list, an indication of whether support for
SLU-initiated sessions is required or optional in order to establish a CP-CP
session with this end node.
v If the list contains explicit entries, the order in which the entries are used (FIRST
or NEXT).
v If SCOPE=ALL is specified, other network nodes known to this end node that are
allowed as network node servers. Other network nodes are allowed as servers
only if the current list contains a nameless entry.
v The name of the current network node server.

Chapter 2. VTAM Operator Commands 145

 DISPLAY NETSRVR
| v The name of the preferred network node server if one has been specified.

For more information on how to code a network node server list, see the OS/390
eNetwork Communications Server: SNA Resource Definition Reference.

Examples
| Displaying a network node server list with one nameless entry and no explicit
| entries using SCOPE=ALL (no preferred network node server has been defined):
| d net,netsrvr,scope=all
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2J
| IST1253I ****NAMELESS**** SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NONE
| IST314I END

| Displaying a network node server list with one nameless entry and no explicit
| entries using SCOPE=ONLY (no preferred network node server has been defined):
| d net,netsrvr,scope=only
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2J
| IST1253I ****NAMELESS**** SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NONE
| IST314I END

| Displaying a network node server list with one explicit entry and no nameless entry
| using SCOPE=ALL (no preferred network node server has been defined):
| d net,netsrvr,scope=all
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2B
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1254I SERVER LIST PROCESSED ORDER = FIRST
| IST924I -------------------------------------------------------------
| IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
| IST1253I NONE
| IST924I -------------------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NONE
| IST314I END

146 SNA Operation

 DISPLAY NETSRVR
| Displaying a network node server list with one explicit entry and no nameless entry
| using SCOPE=ONLY (no preferred network node server has been defined):
| d net,netsrvr,scope=only
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2B
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1254I SERVER LIST PROCESSED ORDER = FIRST
| IST924I -------------------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = OPT
| IST924I -------------------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NONE
| IST314I END

| Displaying the preferred network node server using SCOPE=ALL. A network node
| server list has not been activated.
| D NET,NETSRVR,SCOPE=ALL
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NONE
| IST1253I NONE
| IST924I ---------------------------------------------------
| IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I ---------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I ---------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST314I END

| Displaying the preferred network node server using SCOPE=ONLY. A network node
| server list has not been activated.
| D NET,NETSRVR,SCOPE=ONLY
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NONE
| IST1253I NONE
| IST924I ---------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I ---------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST314I END

| Displaying a network node server list with four explicit entries and one nameless
| entry using SCOPE=ALL. A preferred network node server has been defined.
| D NET,NETSRVR,SCOPE=ALL
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2A
| IST1253I NETA.SSCPBA SLUINIT = OPT
| IST1253I NETA.SSCPCA SLUINIT = REQ
| IST1253I NETA.SSCPDA SLUINIT = OPT
| IST1253I NETA.SSCPEA SLUINIT = REQ
| IST1253I ****NAMELESS**** SLUINIT = REQ
| IST924I ---------------------------------------------------

Chapter 2. VTAM Operator Commands 147

 DISPLAY NETSRVR
| IST1254I SERVER LIST PROCESSED ORDER = FIRST
| IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I ---------------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I ----------------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST314I END
|

| Displaying a network node server list with seven explicit entries and no nameless
| entry using SCOPE=ALL. A preferred network node server has been defined.
| D NET,NETSRVR,SCOPE=ALL
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
| IST1252I DEFINED NETWORK NODE SERVER LIST, NAME = NNSL2B
| IST1253I NETA.SSCPXX SLUINIT = REQ
| IST1253I NETA.SSCPAA SLUINIT = REQ
| IST1253I NETC.SSCP9C SLUINIT = REQ
| IST1253I NETA.SSCPBA SLUINIT = OPT
| IST1253I NETA.SSCPCA SLUINIT = REQ
| IST1253I NETA.SSCPDA SLUINIT = OPT
| IST1253I NETA.SSCPEA SLUINIT = REQ
| IST924I -----------------------------------------------
| IST1254I SERVER LIST PROCESSED ORDER = FIRST
| IST924I -----------------------------------------------
| IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I -----------------------------------------------
| IST1256I CURRENT NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST924I -----------------------------------------------
| IST1677I PREFERRED NETWORK NODE SERVER
| IST1253I NETA.SSCP1A SLUINIT = REQ
| IST314I END

148 SNA Operation

 DISPLAY PATHS

DISPLAY PATHS Command

ÊÊ DISPLAY NET,PATHS ,ID=switched_pu_name ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
PATHS P

Purpose
The DISPLAY PATHS command displays dial-out path information about a switched
physical unit.

Operands
ID=switched_pu_name
specifies the name of a switched physical unit.

Resulting Display
The resulting display shows the physical unit name, line groups, telephone number
or line name, path identifier, group identifier, retry count, availability of the path, and
user-defined DLCADDR subfields (if any) containing additional dial information.

If the DLCADDR subfields are coded in binary-coded decimal (BCD) or

hexadecimal (X) and contain an odd number of digits, the display is padded on the
left with zeros. If the data type is BCD or X, a blank separates every eight
characters of data.

Examples
Displaying dial-out path information:
d net,paths,id=pu1
IST097I DISPLAY ACCEPTED
IST148I DIAL OUT PATH INFORMATION FOR PHYSICAL UNIT PU1
IST149I LINE GRP TELEPHONE NUMBER OR LINE NAME PID GID CNT
IST168I GRP1 PATH21A-890-3333 001 001 003 AVA
IST168I GRP1 002 000 003 AVA
IST1575I DIALNO FOR PID: 002
IST1318I 1ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890
IST168I GRP1 003 001 003 AVA
IST1575I DIALNO FOR PID: 003
IST1318I 123456789012345678901234567890123456789012345678901234567345
IST1319I 678901234567890123456789012345678901234567890123456789012
IST1319I 345678901234567890123456789012345678901234561234567890123
IST1319I 456789012345678901234567890123456789012345612345678901234
IST1319I 56789012345
IST168I GRP1 004 000 003 AVA
IST168I GRP1 005 000 003 AVA
IST1317I DLCADDR SUBFIELDS FOR PID: 004
IST1318I 1,C'TR'
IST1318I 20,C'9192545056'
IST1317I DLCADDR SUBFIELDS FOR PID: 005

Chapter 2. VTAM Operator Commands 149

DISPLAY PATHS
IST1318I 1,C'SAMPLE'
IST1318I 20,C'1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890123456789
IST1319I 012345678901234567890'
IST314I END

150 SNA Operation

 DISPLAY PATHTAB

DISPLAY PATHTAB Command

ÊÊ DISPLAY NET,PATHTAB Ê
,ADJSUB=subarea_number
,DESTSUB=subarea_number

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY PATHTAB (path table) command displays the status of explicit routes
and their associated virtual routes for this host. You can use this command to
display information about all routes, or you can limit it by specifying the ADJSUB or
DESTSUB operands. The DISPLAY PATHTAB command provides information
similar to the “DISPLAY ROUTE Command” on page 155, but in a different format.
However, the DISPLAY ROUTE command provides some additional information not
provided by the DISPLAY PATHTAB command.

Operands
ADJSUB=subarea_number
specifies that information about routes passing through the named adjacent
subarea is the only information to be displayed.
DESTSUB=subarea_number
specifies that information about routes going to the named destination subarea
is the only information to be displayed.
MAX
specifies the maximum number of routes that VTAM displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of routes to display for this command. The valid range
is 1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer routes are found than you have
specified on MAX, VTAM displays only the routes that are found.

Chapter 2. VTAM Operator Commands 151

DISPLAY PATHTAB
Resulting Display
The resulting display shows the host path table contents. Included in the display are
the destination subarea, the adjacent subarea (through which the listed explicit
route flows), the explicit route number, the status (the current state of the listed
explicit route as known to the host), the virtual route number, and the transmission
group number.

Examples
Displaying routes going to a destination subarea:
d net,pathtab,destsub=2
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = PATH TABLE CONTENTS
IST516I DESTSUB ADJSUB TGN ER ER STATUS VR(S)
IST517I 2 4 1 5 INOP 1
IST517I 2 4 1 2 INACT 0
IST517I 2 4 1 1 INOP 2
IST517I 2 4 1 0 INOP 3
IST517I 2 4 1 3 PDEFO
IST517I 2 4 1 4 PDEFO
IST517I 2 4 1 6 PDEFO
IST314I END

Displaying routes passing through an adjacent subarea:

d net,pathtab,adjsub=310
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = PATH TABLE CONTENTS
IST516I DESTSUB ADJSUB TGN ER ER STATUS VR(S)
IST517I 1 310 1 4 INOP 2
IST517I 1 310 1 3 INOP 3
IST517I 1 310 1 0 INACT 0
IST517I 1 310 1 1 PDEFO
IST517I 2 310 1 4 INOP 3
IST517I 2 310 1 3 INOP 4
IST517I 2 310 1 0 INACT 0
IST517I 2 310 1 1 PDEFO
IST517I 2 310 1 5 PDEFO
IST517I 3 310 1 5 INOP 2
IST517I 3 310 1 3 INOP 3
IST517I 3 310 1 2 INOP 1
IST517I 4 310 1 5 INOP 3
IST517I 4 310 1 3 INOP 2
IST517I 4 310 1 0 INACT 0
IST517I 4 310 1 1 PDEFO
IST517I 310 310 1 14 PDEFO
IST517I 310 310 1 15 PDEFO
IST314I END

152 SNA Operation

 DISPLAY PENDING

DISPLAY PENDING Command

ÊÊ DISPLAY NET,PENDING Ê
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY PENDING command displays information about resources in the
domain that are in a “pending” state. A resource can be a major node, a minor
node, an application program, a PU, or an LU.

You can limit the amount of display output (and the amount of time to process this
command) by specifying one or more resources on the ID operand whose pending
subordinate resources are to be displayed.

Attention: If you leave out the ID operand, this command causes VTAM to check
every resource and could have an adverse effect on VTAM performance.

A pending state is:

v A transient state to or from a fully active state
v A state of “recovery pending” or “recovery in progress” for application programs
that have been retained due to the failure or takeover of an application program
enabled for persistence. To observe these recovery states, enter the DISPLAY
command on the system in which the application program resides.

Operands
ID=name
specifies the name of one or more active major nodes, groups, lines, or PUs
whose pending resources are to be displayed.
MAX
specifies the maximum number of resources that VTAM displays for this
command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.

Chapter 2. VTAM Operator Commands 153

DISPLAY PENDING
MAX=number_of_resources
specifies the number of resources that VTAM displays for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer resources are found than you have
specified on MAX, VTAM displays only the resources that are found.

Resulting Display
The resulting display shows the name and status of each node in a pending state.

Examples
Displaying all nodes in a pending state:
d net,pending
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = PENDING
IST159I THE FOLLOWING NODES ARE IN A PENDING STATE
IST080I C04T0011 PACTL C04T0012 PACTL C04T0013 PACTL
IST080I C04T0014 PACTL C04T0015 PACTL C04T0021 PACTL
IST080I C04T0025 PACTL
IST314I END

Displaying all nodes under a specific resource that are in a pending state:
d net,pending,id=a0362zc
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = PENDING
IST089I A0362ZC TYPE = PU T4/5 , ACTIV
IST159I THE FOLLOWING NODES ARE IN A PENDING STATE
IST080I A03P161 PREQC A03P162 PREQC A03P163 PREQC
IST080I A03P164 PREQC A03P165 PREQC A03P166 PREQC
IST080I A03P167 PREQC A03P168 PREQC A03P169 PREQC
IST080I A03P16A PREQC A03P16B PREQC A03P16C PREQC
IST080I A03P201 PREQC A03P202 PREQC A03P203 PREQC
IST080I A03P204 PREQC A03P205 PREQC A03P206 PREQC
IST080I A03P207 PREQC A03P208 PREQC A03P209 PREQC
IST080I A03P20A PREQC A03P20B PREQC A03P20C PREQC
IST314I END

154 SNA Operation

 DISPLAY ROUTE

DISPLAY ROUTE Command

,ER=ALL
ÊÊ DISPLAY NET,ROUTE ,DESTSUB=subarea_number Ê
,COSNAME=name
,ER=ALL
,ER=er_number
,VR=vr_number

,TEST=NO
Ê ÊÍ
,NETID=netid ,ORIGIN=subarea_pu_name ,TEST= NO
YES

Abbreviations
Operand Abbreviation
DISPLAY D
DESTSUB DESTSA

Purpose
The DISPLAY ROUTE command displays the status of explicit routes and virtual
routes and tests whether a route is operational.

Operands
Route selection
specifies which explicit routes or virtual routes are to be displayed. A blank COS
entry is used when no COSNAME entry has been coded in the LOGMODE
table for LU-LU sessions or when an ISTVTCOS entry for SSCP-type sessions
cannot be found.
COSNAME=name
specifies a class-of-service name. If this operand is specified, all virtual
routes to the specified destination subarea within this class of service are
displayed.

The class-of-service table associated with the origin node (where

applicable) and the netid specified in the ORIGIN and NETID operands are
used to resolve the class-of-service name to a list of virtual routes.

If COSNAME is specified, neither the VR nor the ER operands can be

specified.
DESTSUB=subarea_number
specifies the subarea address of the destination subarea of the routes to be
displayed.
ER=er_number
specifies the explicit route number (an integer 0–15). If this operand is
specified, all the explicit routes identified by this explicit route number that
are defined to VTAM through activation of a path definition statement are
displayed. An explicit route becomes known to VTAM either by having been
defined at one time (through the activation of a path definition set defining

Chapter 2. VTAM Operator Commands 155

DISPLAY ROUTE
the ER), or by having been operative at one time (through the receipt of an
ER_OP request unit from the network).

If ER is specified, neither the COSNAME nor the VR operands can be

specified.
ER=ALL
specifies that every explicit route to the specified destination subarea is to
be displayed.

If ER is specified, neither the COSNAME nor the VR operands can be

specified.

If none of the COSNAME, ER, or VR options is specified, ER=ALL is

assumed.
VR=vr_number
specifies the virtual route number (an integer 0–7). If this operand is
specified, the virtual routes identified by this virtual route number to the
specified destination subarea are displayed. There can be up to three
virtual routes identified by the virtual route number, with one route for each
of the three transmission priority levels.

If VR is specified, neither the COSNAME nor the ER operands may be

specified.
NETID=netid
specifies the network attached to the origin node that contains the routes.
VTAM sends the requested NETID to the origin node in the route test request.
The request succeeds if the origin node can recognize the NETID. NETID is a
required start option.

If the netid specified is not the network in which the command is issued, or the
host is not gateway capable, the ORIGIN operand is required for the command
to succeed.

If you do not specify a NETID, the default is the network identifier supplied by
the NETID option at start time.
ORIGIN=subarea_pu_name
specifies the node where the route starts. VTAM must have an SSCP-PU
session with this node to forward the route display request to the node. In
addition, the node must be an NCP subarea node or the host physical unit
name (as specified in the HOSTPU start option). The command fails if you
specify an external host subarea node because VTAM has no SSCP-PU
session with the physical unit in another host subarea.

The default for the ORIGIN operand is the host physical unit specified in the
HOSTPU start option.
TEST
specifies whether an explicit route test is to be performed for a route to a
destination subarea. Testing is not supported for APPN routes.
TEST=YES
specifies that VTAM is to perform an explicit route test for each explicit
route contained in the requested display. That is, if the VR operand is
specified, the explicit route defined to be used by the specified virtual route
is tested; if the COSNAME operand is specified, those explicit routes

156 SNA Operation

 DISPLAY ROUTE
defined to be used by the virtual routes within the specified class of service
are tested. When the test results are received, these test results are sent to
the operator that requested the display; however, these test results are sent
separately from the initial display results. The test results include a display
number that allows the results to be correlated to the original status display.

For an explicit route to be tested, it must be known to VTAM, either by

having been defined at one time (through the activation of a path definition
set defining the ER), or by having been operative at one time (through the
receipt of an ER_OP request unit from the network).

If a node or link along a route becomes inoperative after the ER test

request unit has been sent, VTAM might never receive any test results for
that explicit route.
TEST=NO
specifies that the requested route status is to be displayed, but that no
explicit route test is to be performed.

Resulting Display
The resulting display shows:
v The subarea number of the nodes
v The origin of the physical unit (PU) name (if known)
v The destination of the PU name (if known)
v The network ID (where applicable) of the network attached to the origin PU that
contains the routes
v The virtual route
v The transmission priority, status, explicit route number, adjacent subarea and its
status, and the transmission group number.

Examples
Displaying one virtual route to a destination subarea:
d net,route,destsub=01,netid=netc,origin=c0453le,vr=0
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 8 FROM SA 4 TO SA 1
IST808I ORIGIN PU = C0453LE DEST PU = C01NPU NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 0 ACTIV 5 1 1 ACTIV3
IST537I 0 1 INACT 5 1 1 ACTIV3
IST537I 0 2 INACT 5 1 1 ACTIV3
IST314I END

Displaying one explicit route to a destination subarea:

d net,route,destsub=01,netid=netc,origin=a03n43a,er=5
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 7 FROM SA 4 TO SA 1
IST808I ORIGIN PU = C0453LE DEST PU = C01NPU NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 0 ACTIV 5 1 1 ACTIV3
IST537I 0 1 INACT 5 1 1 ACTIV3
IST537I 0 2 INACT 5 1 1 ACTIV3
IST314I END

Displaying all virtual routes in a class of service to a destination subarea:

Chapter 2. VTAM Operator Commands 157

DISPLAY ROUTE
d net,route,destsub=01,netid=netc,origin=a0362zc,cosname=ist
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 4 FROM SA 31 TO SA 1
IST808I ORIGIN PU = A0362ZC DEST PU = ***NA*** NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 2 ACTIV 0 1 1 ACTIV3
IST537I 1 2 INACT 1 1 1 ACTIV1
IST537I 2 2 INACT 2 1 1 ACTIV1
IST537I 3 2 INACT 3 1 1 ACTIV1
IST537I 4 2 INACT 4 1 1 ACTIV1
IST537I 5 2 UNDEF
IST537I 6 2 UNDEF
IST537I 7 2 UNDEF
IST537I 0 1 INACT 0 1 1 ACTIV3
IST537I 1 1 INACT 1 1 1 ACTIV1
IST537I 2 1 INACT 2 1 1 ACTIV1
IST537I 3 1 INACT 3 1 1 ACTIV1
IST537I 4 1 INACT 4 1 1 ACTIV1
IST537I 5 1 UNDEF
IST537I 6 1 UNDEF
IST537I 7 1 UNDEF
IST537I 0 0 ACTIV 0 1 1 ACTIV3
IST537I 1 0 INACT 1 1 1 ACTIV1
IST537I 2 0 INACT 2 1 1 ACTIV1
IST537I 3 0 INACT 3 1 1 ACTIV1
IST537I 4 0 INACT 4 1 1 ACTIV1
IST537I 5 0 UNDEF
IST537I 6 0 UNDEF
IST537I 7 0 UNDEF
IST314I END

Displaying and testing all virtual routes in a class of service to a destination

subarea:
d net,route,destsub=01,netid=netc,origin=a0362zc,cosname=ist,test=yes
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 6 FROM SA 31 TO SA 1
IST808I ORIGIN PU = A0362ZC DEST PU = ***NA*** NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 2 ACTIV 0 1 1 ACTIV3
IST537I 1 2 INACT 1 1 1 ACTIV1
IST537I 2 2 INACT 2 1 1 ACTIV1
IST537I 3 2 INACT 3 1 1 ACTIV1
IST537I 4 2 INACT 4 1 1 ACTIV1
IST537I 5 2 UNDEF
IST537I 6 2 UNDEF
IST537I 7 2 UNDEF
IST537I 0 1 INACT 0 1 1 ACTIV3
IST537I 1 1 INACT 1 1 1 ACTIV1
IST537I 2 1 INACT 2 1 1 ACTIV1
IST537I 3 1 INACT 3 1 1 ACTIV1
IST537I 4 1 INACT 4 1 1 ACTIV1
IST537I 5 1 UNDEF
IST537I 6 1 UNDEF
IST537I 7 1 UNDEF
IST537I 0 0 ACTIV 0 1 1 ACTIV3
IST537I 1 0 INACT 1 1 1 ACTIV1
IST537I 2 0 INACT 2 1 1 ACTIV1
IST537I 3 0 INACT 3 1 1 ACTIV1
IST537I 4 0 INACT 4 1 1 ACTIV1
IST314I END
IST538I ROUTE TEST 6 IN PROGRESS
IST533I ER 0 SUCCEEDED IN ROUTE TEST 6
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST533I ER 0 SUCCEEDED IN ROUTE TEST 6
IST534I 31 1 1 1 1

158 SNA Operation

 DISPLAY ROUTE
IST798I NETC
IST533I ER 1 SUCCEEDED IN ROUTE TEST 6
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST534I 31 1 1 1 1
IST798I NETC
IST533I ER 2 SUCCEEDED IN ROUTE TEST 6
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST534I 31 1 1 1 1
IST798I NETC
IST314I END

Displaying and testing one explicit route to a destination subarea:

d net,route,destsub=01,netid=netc,origin=c0453le,er=5,test=yes
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 11 FROM SA 4 TO SA 1
IST808I ORIGIN PU = C0453LE DEST PU = C01NPU NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 0 ACTIV 5 1 1 ACTIV3
IST537I 0 1 INACT 5 1 1 ACTIV3
IST537I 0 2 INACT 5 1 1 ACTIV3
IST314I END

Displaying and testing all explicit routes to a destination subarea:

d net,route,destsub=01,netid=netc,origin=a0362zc,test=yes
IST097I DISPLAY ACCEPTED
IST535I ROUTE DISPLAY 8 FROM SA 31 TO SA 1
IST808I ORIGIN PU = A0362ZC DEST PU = ***NA*** NETID = NETC
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I 0 0 ACTIV 0 1 1 ACTIV3
IST537I 0 1 INACT 0 1 1 ACTIV3
IST537I 0 2 ACTIV 0 1 1 ACTIV3
IST537I 1 0 INACT 1 1 1 ACTIV1
IST537I 1 1 INACT 1 1 1 ACTIV1
IST537I 1 2 INACT 1 1 1 ACTIV1
IST537I 2 0 INACT 2 1 1 ACTIV1
IST537I 2 1 INACT 2 1 1 ACTIV1
IST537I 2 2 INACT 2 1 1 ACTIV1
IST537I 3 0 INACT 3 1 1 ACTIV1
IST537I 3 1 INACT 3 1 1 ACTIV1
IST537I 3 2 INACT 3 1 1 ACTIV1
IST537I 4 0 INACT 4 1 1 ACTIV1
IST537I 4 1 INACT 4 1 1 ACTIV1
IST537I 4 2 INACT 4 1 1 ACTIV1
IST314I END
IST538I ROUTE TEST 8 IN PROGRESS
IST533I ER 0 SUCCEEDED IN ROUTE TEST 8
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST533I ER 0 SUCCEEDED IN ROUTE TEST 8
IST534I 31 1 1 1 1
IST798I NETC
IST533I ER 1 SUCCEEDED IN ROUTE TEST 8
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST534I 31 1 1 1 1
IST798I NETC
IST533I ER 2 SUCCEEDED IN ROUTE TEST 8
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I A0362ZC TG ***NA*** ***NA***
IST534I 31 1 1 1 1
IST798I NETC
IST314I END

Chapter 2. VTAM Operator Commands 159

DISPLAY RSCLIST

DISPLAY RSCLIST Command

(1)
ÊÊ DISPLAY NET,RSCLIST ,ID= name Ê
( name )

,IDTYPE=*
Ê Ê
,EXCLUDE= name ,IDTYPE= ADJCPS
, ADJCPSEG
APPLDYN
( » name ) APPLMOD
APPLS
APPLSEG
CDRMS
CDRMSEG
CDRSCS
CDRSCSEG
CLSTRS
GROUPS
LCLSNA
LCL3270
LINES
LINKSTA
LUGROUPS
MAJNODES
MODELSEG
PUT45
SWSEG
TCPIPSEG
TERMS
TRLSEG
XCASEG
*

,MAX=DSPLYDEF_start_option_value
Ê Ê
,MAJNODE=nodename ,MAX= *
number_of_resources

,SCOPE=ALL
Ê ÊÍ
ALL
,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

160 SNA Operation

 DISPLAY RSCLIST
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using abbreviations in commands, code the abbreviation exactly as shown in

the table. Do not use the operand name in the command unless it is shown as part
of the abbreviation in the table. For example, when coding the abbreviation for
SCOPE=ALL, use E or EVERY. SCOPE=E is not a valid option.

Purpose
The DISPLAY RSCLIST command displays information about resources whose
names match a particular pattern.

Operands
EXCLUDE=name
specifies a maximum of five names or patterns of resources to be excluded
from the display. The names or patterns can be network-qualified. If you do not
specify the network identifier, VTAM uses the identifier of the host from which
you are issuing the command.

You can specify wildcard values for this operand, but * and *.* are not valid for
the list of resources to be excluded. For more information about using
wildcards, see “Using Wildcard Names” on page 14.
ID=name
specifies the name of one or more resources to be displayed. The resource
name can be network-qualified. If you do not specify the network identifier,
VTAM uses the identifier of the host from which you are issuing the command.

You can specify * as the network ID portion of a network-qualified name. The *

is useful for displaying information about a resource for which you do not know
the network ID. The * is also useful for displaying information about several
resources with the same name that are found in multiple networks, provided
that you also specify the MAX operand on the command.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Chapter 2. VTAM Operator Commands 161

DISPLAY RSCLIST
Attention: Specifying a wildcard name might degrade performance because
VTAM checks every resource in the network, depending on the value of the
IDTYPE operand.

Note: If model application program definition names match the pattern you
specify on the ID operand of the DISPLAY RSCLIST command when
IDTYPE specifies * or APPLS, those model application program names
will appear in your display output. In addition, any dynamic application
programs built from those model application program definitions will also
appear in your display output.

A model application program will be identified in the TYPE column of message

IST1418I as MODEL APPL. A dynamic application program will be identified in
the TYPE column of message IST1418I as DYNAMIC APPL.

For example, if you issue the following command:

DISPLAY NET,RSCLIST,ID=APPL*,IDTYPE=APPLS

and model application programs have been defined using names that match the
pattern specified on the ID operand (APPL*), you will get the following output:
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1417I NETID NAME STATUS TYPE MAJNODE
IST1418I NETA APPLA* CONCT MODEL APPL APPL1A
IST1418I NETA APPLQ? CONCT MODEL APPL APPL1A
IST1418I NETA APPL1 ACT/S APPL APPL1A
IST1418I NETA APPLA01 ACTIV--S-- DYNAMIC APPL APPL1A
IST1418I NETA APPLQ1 ACTIV--S-- DYNAMIC APPL APPL1A
IST1454I 5 RESOURCE(S) DISPLAYED FOR ID=APPL*
IST314I END

The wildcard character used in APPL* on the ID operand of the DISPLAY

RSCLIST command tells VTAM to display any resource whose name begins
with APPL, followed by zero to four valid characters in length. The names
APPLA* and APPLQ?, even though they contain wildcard characters, both
begin with APPL, followed by zero to four valid characters in length (* and ? are
valid characters in an application program minor node name). Therefore, they
are included in the display output, as are the dynamic application programs
(APPLA01 and APPLQ1) built from APPLA* and APPLQ?.

To limit the display to model application program definitions, specify

IDTYPE=APPLMOD when you issue the DISPLAY RSCLIST command. To limit
the display to dynamic application programs, specify IDTYPE=APPLDYN when
you issue the DISPLAY RSCLIST command.
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE can be used to identify which
resource the command should act on. The default is IDTYPE=*.
IDTYPE=ADJCPS
displays only adjacent control points.
IDTYPE=ADJCPSEG
displays only adjacent control point major nodes.
IDTYPE=APPLDYN
displays only dynamic application programs.

162 SNA Operation

 DISPLAY RSCLIST
IDTYPE=APPLMOD
displays only model application programs.
IDTYPE=APPLS
displays only application minor nodes, including model application program
definitions and dynamic application programs.
IDTYPE=APPLSEG
displays only application major nodes.
IDTYPE=CDRMS
displays only cross-domain resource managers known to this host
processor.
IDTYPE=CDRMSEG
displays only CDRM major nodes.
IDTYPE=CDRSCS
displays only cross-domain resources known to this domain.
IDTYPE=CDRSCSEG
displays only CDRSC major nodes.
IDTYPE=CLSTRS
displays only physical units in this domain.
IDTYPE=GROUPS
displays only groups in this domain.
IDTYPE=LCLSNA
displays only local SNA major nodes.
IDTYPE=LCL3270
displays only local non-SNA major nodes.
IDTYPE=LINES
displays only lines in this domain.
IDTYPE=LINKSTA
displays only link stations in this domain.
IDTYPE=LUGROUPS
displays only LU group major nodes.
IDTYPE=MAJNODES
displays only major nodes.
IDTYPE=MODELSEG
displays only model major nodes.
IDTYPE=PUT45
displays only type 4 and type 5 PUs.
IDTYPE=SWSEG
displays only switched major nodes.
IDTYPE=TCPIPSEG
displays only TCP/IP major nodes. This option is used only with the AnyNet*
function.
IDTYPE=TERMS
displays only logical units.
IDTYPE=TRLSEG
displays only the transport resource list (TRL) major node.

Chapter 2. VTAM Operator Commands 163

DISPLAY RSCLIST
IDTYPE=XCASEG
displays only external communication adapter (XCA) major nodes.
IDTYPE=*
displays all resources, including model application program definitions and
dynamic application programs.
MAJNODE=nodename
specifies the name of the major node to be searched for resources matching
the ID operand. The nodename cannot be a network-qualified name.

You can specify a wildcard value for the MAJNODE operand. For more
information about using wildcards, see “Using Wildcard Names” on page 14.
MAX
specifies the maximum number of resources that VTAM displays for this
command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of resources that VTAM displays for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer resources are found than you have
specified on MAX, VTAM displays only the resources that are found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable resources. If this display is undesirably large, you can use
SCOPE=ACTONLY or SCOPE=CONCT to further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all resources in an active
state. The display does not include resources in pending or connectable
states. If no resources are found in an active state, you can use
SCOPE=ACT to broaden the scope of the display to active, connectable,
and pending resources.
SCOPE=ACTSESS
specifies that information is to be displayed about all resources that are
active with sessions.
SCOPE=ALL
specifies that information is to be displayed about all resources (regardless
of their status).

164 SNA Operation

 DISPLAY RSCLIST
SCOPE=CONCT
specifies that information is to be displayed about all resources in a CONCT
(connectable) state. If no applications are found in a connectable state, you
can use SCOPE=ACT to broaden the scope of the display to active,
connectable, and pending resources.
SCOPE=INACT
specifies that information is to be displayed about all inactive resources. If
this display is undesirably large, you can use SCOPE=INACTONLY or
SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive resources.
Resources in a RESET state are not included in the SCOPE=INACTONLY
display.
SCOPE=PENDING
specifies that information is to be displayed about all pending resources. A
pending state is a transient state to or from the fully active state.
SCOPE=RESET
specifies that information is to be displayed about all resources in a RESET
state.

Resulting Display
The resulting VTAM display shows:
v The NETID and name of each resource that matches the pattern specified on the
ID operand and the status specified on the SCOPE operand
v The current resource status
v The resource type
v The name of the major node where the resource is defined.

Note: If model application program definitions are included in the display, any
dynamic application programs built from those models that have been
deactivated are not displayed. This is because dynamic application programs
cannot exist in an inactive state. When a dynamic application program is
deactivated and CLOSE macro processing is complete for the dynamic
application program, the definition of the dynamic application program is
deleted. The dynamic application program is no longer known by VTAM and
will not appear in the output of any DISPLAY commands.

Examples
Displaying all active resources in this network with names starting with “app”,
including dynamic application programs built from model application program
definitions. Note that model application programs do not appear in the display
output because they are always in a connectable (CONCT) state.
d net,rsclist,id=app*,scope=actonly
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1417I NETID NAME STATUS TYPE MAJNODE
IST1418I NETA APPLAA3 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLAA2 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLCA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLBA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLDA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPL1A ACTIV APPL SEGMENT APPL1A

Chapter 2. VTAM Operator Commands 165

DISPLAY RSCLIST
IST1418I NETA APPL1 ACT/S APPL APPL1A
IST1418I NETA APPL8 ACTIV--S-- CDRSC CDRSC1A
IST1418I NETA APPLAA1 ACTIV CDRSC CDRSC1A
IST1418I NETA APPLA01 ACTIV--S-- DYNAMIC APPL APPL1A
IST1418I NETA APPLQ1 ACTIV--S-- DYNAMIC APPL APPL1A
IST1454I 11 RESOURCE(S) DISPLAYED FOR ID=APP*
IST314I END

Displaying all active, pending, and connectable resources in this network with
names starting with “app”, including model application programs and dynamic
application programs built from those models:
d net,rsclist,id=app*,scope=act
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1417I NETID NAME STATUS TYPE MAJNODE
IST1418I NETA APPLAA3 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLAA2 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLCA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLBA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLDA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPL1A ACTIV APPL SEGMENT APPL1A
IST1418I NETA APPLA* CONCT MODEL APPL APPL1A
IST1418I NETA APPLQ? CONCT MODEL APPL APPL1A
IST1418I NETA APPL1 ACT/S APPL APPL1A
IST1418I NETA APPLQ1 ACTIV--S-- DYNAMIC APPL APPL1A
IST1418I NETA APPLA01 ACTIV--S-- DYNAMIC APPL APPL1A
IST1418I NETA APPL8 ACTIV--S-- CDRSC CDRSC1A
IST1418I NETA APPLAA1 ACTIV CDRSC CDRSC1A
IST1454I 13 RESOURCE(S) DISPLAYED FOR ID=APP*
IST314I END

Displaying all model application program definitions in this network with names
starting with “app”:
d net,rsclist,id=app*,idtype=applmod,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1418I NETA APPLA* CONCT MODEL APPL APPL1A
IST1418I NETA APPLQ? CONCT MODEL APPL APPL1A
IST1454I 2 RESOURCE(S) DISPLAYED FOR ID=APP*
IST314I END

Displaying all dynamic application programs in this network built from model
application program definitions whose names start with “app”:
d net,rsclist,id=app*,idtype=appldyn,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1418I NETA APPLQ1 ACTIV--S-- DYNAMIC APPL APPL1A
IST1418I NETA APPLA01 ACTIV--S-- DYNAMIC APPL APPL1A
IST1454I 2 RESOURCE(S) DISPLAYED FOR ID=APP*
IST314I END

Displaying resources in this network with names starting with “app”, limiting output
to 6 resources:
d net,rsclist,id=app*,max=6
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1417I NETID NAME STATUS TYPE MAJNODE
IST1418I NETA APPLAA3 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLAA2 ACTIV CDRSC ISTPDILU
IST1418I NETA APPLCA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLBA1 ACT/S----Y CDRSC ISTCDRDY
IST1418I NETA APPLDA1 ACT/S----Y CDRSC ISTCDRDY

166 SNA Operation

 DISPLAY RSCLIST
IST1418I NETA APPL1A ACTIV APPL SEGMENT APPL1A
IST1315I DISPLAY TRUNCATED AT MAX = 6
IST1454I 6 RESOURCE(S) DISPLAYED FOR ID=APP*
IST314I END

Displaying all active rapid transport protocol (RTP) connections for high
performance routing (HPR):
d net,rsclist,id=cnr*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = RSCLIST
IST1417I NETID NAME STATUS TYPE MAJNODE
IST1418I NETA CNR00004 ACTIV--LX- PU_T2.1 ISTRTPMN
IST1418I NETA CNR00003 ACTIV--LX- PU_T2.1 ISTRTPMN
IST1418I NETA CNR00002 ACTIV--LX- PU_T2.1 ISTRTPMN
IST1418I NETA CNR00001 ACTIV--LX- PU_T2.1 ISTRTPMN
IST1454I 4 RESOURCE(S) DISPLAYED FOR ID=CNR*
IST314I END

Chapter 2. VTAM Operator Commands 167

 DISPLAY SAMAP
|
| DISPLAY SAMAP Command
| ÊÊ DISPLAY NET,SAMAP ÊÍ
|

| Purpose
| The DISPLAY SAMAP command displays the subarea mapping table from an ICN
| host.

| Resulting Display
| The resulting VTAM display shows the subarea mapping table from an ICN host.

| Examples
| Displaying the subarea mapping table:
| d net,samap
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = SAMAP
| IST1321I TABLE FOR SAMAP
| IST1671I SA20 MAPSTO SA10
| IST1671I SA10 MAPSTO SA20
| IST314I END

168 SNA Operation

 DISPLAY SATOAPPN

DISPLAY SATOAPPN Command

ÊÊ DISPLAY NET,SATOAPPN ÊÍ

Purpose
The DISPLAY SATOAPPN command displays the subarea-to-APPN class-of-service
mapping table.

Resulting Display
The resulting VTAM display shows the subarea-to-APPN class-of-service mapping
table.

Examples
Displaying the subarea-to-APPN class-of-service mapping table:
d net,satoappn
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SATOAPPN
IST1321I TABLE FOR SATOAPPN
IST1514I SUBAREA COS APPNCOS
IST1323I COSAPPL1 #CONNECT
IST1323I COSAPPL2 #BATCH
IST1323I COSAPPL3 #BATCHSC
IST1323I COSAPPL4 #INTER
IST1323I COSAPPL5 #CONNECT DEFAULT
IST1323I ISTCOSDF #INTERSC
IST314I END

Chapter 2. VTAM Operator Commands 169

DISPLAY SESSIONS

DISPLAY SESSIONS Command

Display all sessions:

ÊÊ DISPLAY NET,SESSIONS Ê
,LU1=lu_name
,LU2=lu_name
,LU2=lu_name
,LU1=lu_name
,PLU=plu_name
,SLU=slu_name
,SLU=slu_name
,PLU=plu_name

,LIST=COUNT ,SCOPE=ALL
Ê ÊÍ
,LIST= ALL operand ,SCOPE= ACT
COUNT ALL
SUMMARY PENDING
Q

ALL operand

ALL MAX operand

MAX operand

,MAX=DSPLYDEF_start_option_value

,MAX= *
number_of_resources

Display a specific session:

ÊÊ DISPLAY NET,SESSIONS ,SID=session_id ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ALL EVERY or E
SCOPE=PENDING SCOPE=PEND or PEND
SESSIONS SESSION

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

170 SNA Operation

 DISPLAY SESSIONS
Purpose
The DISPLAY SESSIONS command displays LU-LU session status information.
The command can display status information for:
v A single session identified by its session identifier
v All sessions in which a specified logical unit is the primary session partner
v All sessions in which a specified logical unit is the secondary session partner
v All sessions in which a pair of logical units have a specified primary/secondary
relationship as session partners
v All sessions in which a specified logical unit is a session partner (without regard
to its primary or secondary status)
v All sessions between a pair of logical units regardless of their primary/secondary
relationship as session partners
v All sessions known to VTAM, limited with the SCOPE operand to all pending
sessions, all queued sessions, or all active sessions.
Notes:
1. To display sessions between specified logical units, one of the session partners
must reside in the host VTAM network.
2. If you issue the DISPLAY SESSIONS command at a network node server that is
not an interchange node, control point, or SSCP for either session partner, this
command might show duplicate information for some sessions. This might occur
briefly during BIND processing in a normal session setup or it might indicate a
hung session. If subsequent displays continue to show duplicate information for
the same session, the session might be hung.

Operands
LIST
specifies the level of detail to display.
LIST=ALL
displays all session status information for sessions with the status specified
in the SCOPE operand. If SCOPE=ALL, the display includes active,
pending, and queued sessions.
LIST=COUNT
displays only the total number of sessions with the status specified in the
SCOPE operand. If SCOPE=ALL, the number includes all sessions,
regardless of whether they are active, pending, or queued.
LIST=SUMMARY
displays the total number of sessions with the status specified in the
SCOPE operand (same as LIST=COUNT), plus the actual session state
codes for pending and queued sessions. For a description of possible
session initiation and termination states, see OS/390 eNetwork
Communications Server: SNA Messages.
LU1=lu_name
identifies the logical unit for which sessions are displayed. lu_name can be
specified as a network-qualified name. If you also specify the LU2 operand, the
command displays only sessions involving both named logical units.

If lu_name is a generic resource name, VTAM will display session status

information for all members known by that generic name.

Chapter 2. VTAM Operator Commands 171

DISPLAY SESSIONS
LU2=lu_name
identifies the logical unit for which sessions are displayed. lu_name can be
specified as a network-qualified name. If you also specify the LU1 operand, the
command displays only sessions involving both named logical units.

If lu_name is a generic resource name, VTAM will display session status

information for all members known by that generic name.
MAX
specifies the maximum number of sessions that VTAM displays for this
command. This operand is only valid with LIST=ALL.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of sessions that VTAM displays for this command. The
valid range is 1–value of DSPLYMAX. The default is the value specified for
the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer sessions are found than you have
specified on MAX, VTAM displays only the sessions that are found.
PLU=plu_name
identifies the logical unit that is the primary session partner. plu_name can be
specified as a network-qualified name. If you specify the PLU operand, the
command displays only sessions in which this logical unit is the primary session
partner. If you also specify the SLU operand, the command displays only
sessions involving both named logical units in the specified primary/secondary
relationship.

If plu_name is a generic resource name, VTAM will display session status

information for all members known by that generic name.
SCOPE
specifies the status of the sessions to display. See OS/390 eNetwork
Communications Server: SNA Messages for a description of the initiation states
“queued”, “pending active”, and “active” for each session status. You cannot use
this operand with the SID operand.
SCOPE=ACT
displays only active sessions.
SCOPE=ALL
displays all sessions, whether active, pending, or queued.
SCOPE=PENDING
displays only pending sessions. A pending state is:
v A transient state to or from a fully active state.
v A state of “recovery pending” or “recovery in progress” for sessions that
have been retained due to the failure or takeover of an application
enabled for persistence.

172 SNA Operation

 DISPLAY SESSIONS
Note: In either situation, the state of the half-session as seen by the
PLU is the status reported for the session. Because of this, you
must enter the DISPLAY command on the system in which the
application resides.
SCOPE=Q
displays only queued sessions.
SID=session_id
identifies the VTAM LU-LU session to display. To display the session identifier
named in this operand, issue either the DISPLAY SESSIONS,SCOPE=ALL
command or a DISPLAY ID=resource name,SCOPE=ALL command. The
session ID is identified by SID on the display and is 16 characters long.

If you specify the SID operand, you cannot specify SCOPE or LIST on the
same command.
SLU=slu_name
identifies the logical unit that is the secondary session partner. slu_name can be
specified as a network-qualified name. If you specify the SLU operand, the
command displays only sessions in which this logical unit is the secondary
session partner. If you also specify the PLU operand, the command displays
only sessions involving both named logical units in the specified
primary/secondary relationship.

If slu_name is a generic resource name, VTAM will display session status

information for all members known by that generic name.

Resulting Display
The resulting display shows:
v For LIST=COUNT:
– The number of sessions with the status specified in the SCOPE operand,
optionally limited by LU1, LU2, PLU, or SLU.
– A summary of active SSCP sessions, showing the number of SSCP-LU
sessions, the number of SSCP-PU sessions, and the number of SSCP-SSCP
sessions. This includes both active and pending sessions. These counts of
SSCP sessions are not included in the number of total sessions (message
IST878I). This summary of active SSCP sessions does not appear if the
display has been limited by the LU1, LU2, PLU, or SLU operands, or if
SCOPE excludes active sessions.
v For LIST=SUMMARY:
– The number of sessions with the status specified in the SCOPE operand,
optionally limited by LU1, LU2, PLU, or SLU.
– For queued and pending sessions, the number of sessions with each status
code.
– For active sessions, the number of LU-LU sessions, the number of CP-CP
contention winner sessions, and the number of CP-CP contention loser
sessions.
– A summary of active SSCP sessions, showing the number of SSCP-LU
sessions, the number of SSCP-PU sessions, and the number of SSCP-SSCP
sessions. This includes both active and pending sessions. These counts of
SSCP sessions are not included in the number of total sessions (message

Chapter 2. VTAM Operator Commands 173

DISPLAY SESSIONS
IST878I). This summary of active SSCP sessions does not appear if the
display has been limited by the LU1, LU2, PLU, or SLU operands, or if
SCOPE excludes active sessions.
v For LIST=ALL:
– The names of the resources in the sessions.
– Each session’s identifier.
– Each session’s status code.
– The number of sessions with the status specified in the SCOPE operand,
optionally limited by LU1, LU2, PLU, or SLU.
– For queued and pending sessions, the number of sessions with each status
code.

Note: If the value of the MAX operand is exceeded, count displays ten
asterisks (**********).
– For active sessions, the number of LU-LU sessions, the number of CP-CP or
CPSVRMGR contention winner sessions, and the number of CP-CP or
CPSVRMGR contention loser sessions.

Note: If the value of the MAX operand is exceeded, count for the LU-LU
sessions displays ten asterisks (**********).
– A summary of active SSCP sessions, showing the number of SSCP-LU
sessions, the number of SSCP-PU sessions, and the number of SSCP-SSCP
sessions. This includes both active and pending sessions. These counts of
SSCP sessions are not included in the number of total sessions (message
IST878I). This summary of active SSCP sessions does not appear if the
display has been limited by the LU1, LU2, PLU, or SLU operands, or if
SCOPE excludes active sessions.
v For SID:
– The real and alias (if available) names of the primary session partner.
– The real and alias (if available) names of the secondary session partner.
– The session status.
– The adjacent SSCP toward the PLU or SLU, if cross-domain (if available).
– The rapid transport protocol (RTP) physical unit as the ALSNAME toward the
PLU or SLU, if the session is using high performance routing (HPR).
– The gateway NCP toward the PLU or SLU, if cross-network (if available).
– The signals needed to complete a session, if the session is pending session
setup or takedown.
– The class-of-service table entry and logon mode entry used.
– The APPN class-of-service toward the PLU or SLU, (if available).
– Compression information, if compression is being used on the session in
either the PLU-to-SLU or the SLU-to-PLU direction.
- The compression-level values (0–4) in use for input and output messages
- The percentage of reduction in length for input and output messages
- The indicator “NA” (not applicable) if there has been no message traffic or if
compression is not being used on either the inbound or outbound
half-session.

If compression is not being used in either direction, this information is not

displayed.

174 SNA Operation

 DISPLAY SESSIONS
Examples
Displaying a specific session:
d net,sessions,sid=eaabeec3e5a79ccb
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST879I PLU/OLU REAL = NETA.APPL2 ALIAS = ***NA***
IST879I SLU/DLU REAL = NETA.APPL1 ALIAS = ***NA***
IST880I SETUP STATUS = ACTIV
IST933I LOGMODE=INTERACT, COS=*BLANK*
IST1635I PLU HSCB TYPE: FMCB LOCATED AT ADDRESS X'0155F5B8'
IST1635I SLU HSCB TYPE: FMCB LOCATED AT ADDRESS X'0155F720'
IST1636I PACING STAGE(S) AND VALUES:
IST1637I PLU--STAGE 1--SLU
IST1638I STAGE1: PRIMARY TO SECONDARY DIRECTION - ADAPTIVE
IST1639I PRIMARY SEND: CURRENT = 7 NEXT = 8
IST1640I SECONDARY RECEIVE = 32767
IST1641I STAGE1: SECONDARY TO PRIMARY DIRECTION - ADAPTIVE
IST1642I SECONDARY SEND: CURRENT = 7 NEXT = 8
IST1643I PRIMARY RECEIVE = 32767
IST314I END

Displaying all sessions:

d net,sessions,scope=all,list=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST873I PLU SLU SID STATUS
IST874I NETA.SSCP1A NETA.ENCPA4 EAABEEC3297ED9FC ACTIV/DL
IST874I NETB.SSCP7B NETA.SSCP1A C2BB19BC57AD196C ACTIV/CP
IST874I NETA.SSCP1A NETB.SSCP7B EAABEEC3297ED9FA ACTIV/CP
IST874I NETA.SSCP2A NETA.SSCP1A F6ABEEC32C7EDA76 ACTIV/CP
IST874I NETA.SSCP1A NETA.SSCP2A EAABEEC3297ED9F8 ACTIV/CP
IST874I NETA.ENCPA4 NETA.SSCP1A E2C5E2E2D6D50013 ACTIV/DL
IST924I -------------------------------------------------------------
IST878I NUMBER OF PENDING SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF ACTIVE SESSIONS = 6
IST1162I LU-LU = 2
IST1162I CP-CP CONWINNER = 2
IST1162I CP-CP CONLOSER = 2
IST924I -------------------------------------------------------------
IST878I NUMBER OF QUEUED SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF TOTAL SESSIONS = 6
IST924I -------------------------------------------------------------
IST1161I SSCP SESSIONS
IST1162I SSCP-LU = 6
IST1162I SSCP-PU = 4
IST1162I SSCP-SSCP = 0
IST314I END

Displaying sessions, limiting output to 6 sessions:

d net,sessions,list=all,max=6
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS 141
IST873I PLU SLU SID STATUS
IST874I NETA.MECHZ1A NETA.ECHOZHA D9F389C8E5517F35 ACTIV/MI
IST874I NETA.MECHZ1A NETA.ECHOZHA D9F389C8E5517F38 ACTIV/MI
IST874I NETA.ECHOZIA NETA.ECHOZHA E7F38956127BB9F6 ACTIV
IST874I NETA.ECHOZIA NETA.ECHOZHA E7F38956127BB9F4 ACTIV
IST874I NETA.MECHZIA NETA.ECHOZHA E7F38956127BB9F3 ACTIV/M
IST874I NETA.MECHZIA NETA.ECHOZHA E7F38956127BB9F1 ACTIV/M
IST1315I DISPLAY TRUNCATED AT MAX = 6
IST924I -------------------------------------------------------------

Chapter 2. VTAM Operator Commands 175

DISPLAY SESSIONS
IST878I NUMBER OF PENDING SESSIONS = **********
IST924I -------------------------------------------------------------
IST878I NUMBER OF ACTIVE SESSIONS = **********
IST1162I LU-LU = **********
IST1162I CP-CP CONWINNER = 1
IST1162I CP-CP CONLOSER = 1
IST924I -------------------------------------------------------------
IST878I NUMBER OF QUEUED SESSIONS = **********
IST924I -------------------------------------------------------------
IST878I NUMBER OF TOTAL SESSIONS = **********
IST924I -------------------------------------------------------------
IST1161I SSCP SESSIONS
IST1162I SSCP-LU = 25
IST1162I SSCP-PU = 1
IST1162I SSCP-SSCP = 0
IST314I END

Displaying a summary of all sessions:

d net,sessions,scope=all,list=summary
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST924I -------------------------------------------------------------
IST878I NUMBER OF PENDING SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF ACTIVE SESSIONS = 4
IST1162I LU-LU = 2
IST1162I CP-CP CONWINNER = 1
IST1162I CP-CP CONLOSER = 1
IST924I -------------------------------------------------------------
IST878I NUMBER OF QUEUED SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF TOTAL SESSIONS = 4
IST924I -------------------------------------------------------------
IST1161I SSCP SESSIONS
IST1162I SSCP-LU = 10
IST1162I SSCP-PU = 4
IST1162I SSCP-SSCP = 0
IST314I END

Displaying all sessions for a specific LU:

d net,sessions,lu1=appl0001,scope=all,list=summary
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST924I -------------------------------------------------------------
IST878I NUMBER OF PENDING SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF ACTIVE SESSIONS = 1
IST924I -------------------------------------------------------------
IST878I NUMBER OF QUEUED SESSIONS = 0
IST924I -------------------------------------------------------------
IST878I NUMBER OF TOTAL SESSIONS = 1
IST314I END

Displaying active sessions for a specific LU:

d net,sessions,lu1=appl1,scope=act,list=count
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST878I NUMBER OF ACTIVE SESSIONS = 1
IST314I END

Displaying pending sessions for a specific LU:

d net,sessions,lu1=appl1,scope=pending,list=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS

176 SNA Operation

 DISPLAY SESSIONS
IST873I PLU SLU SID STATUS
IST874I NETA.APPL1 NETA.NETAPPL1 EAABEEC3FD825DEA PSEST/B
IST878I NUMBER OF PENDING SESSIONS = 1
IST1237I PSEST = 1
IST314I END

Displaying queued sessions between two LUs:

d net,sessions,lu1=appl1,lu2=appl0001,scope=q,list=count
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST1284I LUALIAS APPL0001 IS NETA.NETAPPL1 FOR APPLICATIONS
IST878I NUMBER OF QUEUED SESSIONS = 2
IST314I END

Displaying a count of active sessions with a USERVAR:

d net,sessions,lu1=echo01a,scope=act,list=count
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST113I ECHO01A IS A USERVAR WITH VALUE ECHO01A IN NETWORK NETA
IST1057I NETA.ECHO01A IS ALSO A REAL RESOURCE
IST878I NUMBER OF ACTIVE SESSIONS = 61
IST314I END

Displaying a generic resource name for LU1:

d net,sessions,lu1=cics,list=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SESSIONS
IST1364I CICS IS A GENERIC RESOURCE NAME FOR:
IST1154I NETA.CICS1 NETA.CICS2 NETA.CICS3
IST924I -------------------------------------------------------------
IST873I PLU SLU SID STATUS
IST874I NETA.CICS1 NETA.APPL1A2 EAABEEC3F8FE476C ACTIV
IST874I NETA.APPL1A1 NETA.CICS2 EAABEEC3F8FE476B ACTIV
IST874I NETA.APPL1A1 NETA.CICS2 EAABEEC3F8FE476A ACTIV
IST874I NETA.CICS3 NETA.APPL1A5 EAABEEC3F8FE4769 ACTIV
IST874I NETA.CICS3 NETA.APPL1A9 EAABEEC3F8FE4768 ACTIV
IST878I NUMBER OF PENDING SESSIONS = 0
IST878I NUMBER OF ACTIVE SESSIONS = 5
IST878I NUMBER OF QUEUED SESSIONS = 0
IST878I NUMBER OF TOTAL SESSIONS = 5
IST314I END

Chapter 2. VTAM Operator Commands 177

DISPLAY SNSFILTR

DISPLAY SNSFILTR Command

ÊÊ DISPLAY NET,SNSFILTR ÊÍ

Purpose
The DISPLAY SNSFILTR command displays the current active SAW sense filter.

Resulting Display
The resulting VTAM display shows the current active SAW sense filter.

Examples
Displaying the SAW sense filter:
d net,snsfiltr
IST350I DISPLAY TYPE = SNSFILTR
IST1321I TABLE FOR SAW SENSE FILTER
IST1551I 0857**** 087D0001 087D0002 087D0003 087D0004
IST1551I 087D0005 087D0006 087D0007 087D0008 087D0009
IST1551I 089D0001 8013****
IST314I END

178 SNA Operation

 DISPLAY SRCHINFO

DISPLAY SRCHINFO Command

Display summary information about outstanding subarea and APPN searches:

(3)
,TYPE=SUBAREA
(2)
,TYPE=APPN
(1)
,LIST=SUMMARY ,TYPE=ALL
ÊÊ DISPLAY NET,SRCHINFO Ê
,TYPE= ALL
APPN
SUBAREA

(4)
Ê Ê
,FROMCP=cp_name ,FROMSSCP=sscp_name
,TOCP=cp_name ,TOSSCP=sscp_name

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_searches

Notes:
1. TYPE=ALL is the default when the HOSTSA and NODETYPE start options are
specified.
2. TYPE=APPN is the default when the NODETYPE start option is specified
without the HOSTSA start option.
3. TYPE=SUBAREA is the default when the HOSTSA start option is specified
without the NODETYPE start option.
4. These operands are valid with TYPE=APPN or TYPE=ALL.

Display detailed information about outstanding subarea and APPN searches:

Chapter 2. VTAM Operator Commands 179

DISPLAY SRCHINFO

ÊÊ DISPLAY NET,SRCHINFO ,LIST=ALL Ê

,DLU=lu_name
,OLU=lu_name
,OLU=lu_name
,DLU=lu_name
,LU1=lu_name
,LU2=lu_name
,LU2=lu_name
,LU1=lu_name

(3)
,TYPE=SUBAREA
(2)
,TYPE=APPN
(1)
,TYPE=ALL (4)
Ê Ê
,TYPE= ALL ,FROMCP=cp_name ,FROMSSCP=sscp_name
APPN ,TOCP=cp_name ,TOSSCP=sscp_name
SUBAREA

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_searches

Notes:
1. TYPE=ALL is the default when the HOSTSA and NODETYPE start options are
specified.
2. TYPE=APPN is the default when the NODETYPE start option is specified
without the HOSTSA start option.
3. TYPE=SUBAREA is the default when the HOSTSA start option is specified
without the NODETYPE start option.
4. These operands are valid with TYPE=APPN or TYPE=ALL.

Display search information about a specific search request:

(3)
,TYPE=SUBAREA
(2)
,TYPE=APPN
(1)
,TYPE=ALL
ÊÊ DISPLAY NET,SRCHINFO ,SID=session_identifer Ê
,TYPE= ALL
APPN
SUBAREA

180 SNA Operation

 DISPLAY SRCHINFO

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_searches

Notes:
1. TYPE=ALL is the default when the HOSTSA and NODETYPE start options are
specified.
2. TYPE=APPN is the default when the NODETYPE start option is specified
without the HOSTSA start option.
3. TYPE=SUBAREA is the default when the HOSTSA start option is specified
without the NODETYPE start option.

Abbreviations
Operand Abbreviation
DISPLAY D
SID PCID

Purpose
The DISPLAY SRCHINFO command displays information about outstanding APPN
and subarea search requests.

Note: The DISPLAY SRCHINFO,LIST=ALL and the DISPLAY

SESSIONS,LIST=ALL commands will not always show the same session
identifiers (SIDs). There are sessions (for example, INQUIRE APPSTAT) that
do not involve sessions. Once session setup has progressed beyond the
search for the DLU, the SID of the session will not appear in the DISPLAY
SRCHINFO output.

Operands
DLU
specifies the name of a destination LU. Display results for both subarea and
APPN are limited by specifing this operand.

lu_name can be specified as a network-qualified name. If you do not specify the

network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
FROMCP
specifies the name of a control point (CP).

cp_name can be specified as a network-qualified name. If you do not specify

the network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

Chapter 2. VTAM Operator Commands 181

DISPLAY SRCHINFO
You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
FROMSSCP
specifies the name of a subsystem control point (SSCP).

The value specified for sscp_name cannot be a network-qualified name.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
LIST
specifies the level of detail to display.
LIST=ALL
for TYPE=SUBAREA or TYPE=ALL, displays information concerning
outstanding CDINIT, DSRLST, and INIT_OTHER CD (IOCD) search
requests. For TYPE=APPN or TYPE=ALL, displays information concerning
outstanding locate requests. One line of information is provided for each
outstanding request.
LIST=SUMMARY
for TYPE=SUBAREA or TYPE=ALL, displays summary information
concerning outstanding CDINIT, DSRLST, and INIT_OTHER CD (IOCD)
search requests. For TYPE=APPN or TYPE=ALL, displays summary
information concerning the number of outstanding search requests with all
adjacent control points (CPs).
LU1
specifies the name of a logical unit. If this operand is specified, the information
displayed is limited to outstanding search requests sent to or received from the
specified LU.

lu_name can be specified as a network-qualified name. If you do not specify the

network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.

LU1 and LU2 can be used in place of DLU and OLU when it is not known
which partner is the destination or originating LU.
LU2
specifies the name of a logical unit.

lu_name can be specified as a network-qualified name. If you do not specify the

network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.

LU1 and LU2 can be used in place of DLU and OLU when it is not known
which partner is the destination or originating LU.
MAX
specifies the maximum number of searches that VTAM displays for this
command.

182 SNA Operation

 DISPLAY SRCHINFO
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_searches
specifies the maximum number of searches that VTAM displays for this
command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output; VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command.

For TYPE=ALL, the MAX operand is applied separately to the subarea and
APPN displays.
OLU
identifies the LU that is the origin of a search request.

lu_name can be specified as a network-qualified name. If you do not specify the

network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
SID
identifies the session ID (SID) of a specific search to be displayed. The SID is
also known as the procedure-correlation identifier (PCID). Both subarea and
APPN information will be provided, based on the TYPE operand.

If you specify the SID operand, do not specify LIST.

The SID may be obtained from the output of DISPLAY SRCHINFO,LIST=ALL

(search-related requests) or DISPLAY SESSIONS,LIST=ALL (session-related
requests).
TOCP
identifies an adjacent CP for a search request.

cp_name can be specified as a network-qualified name. If you do not specify

the network identifier, VTAM uses the identifier of the host from which you are
issuing the command.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
TOSSCP
identifies the destination SSCP for a search request.

You can specify wildcard values for this operand. For more information about
using wildcards, see “Using Wildcard Names” on page 14.
TYPE
identifies the type of information desired.

Chapter 2. VTAM Operator Commands 183

DISPLAY SRCHINFO
TYPE=ALL
indicates that both APPN and subarea search information will be displayed.
TYPE=ALL is the default for interchange nodes and migration data hosts.
TYPE=APPN
indicates that APPN search information will be displayed. Subarea search
information will not be displayed.
TYPE=SUBAREA
indicates that subarea search information will be displayed. APPN search
information will not be displayed.

Resulting Display
Specifying the DLU operand limits the display to outstanding search requests sent
to the specified LU.

Specifying the OLU operand limits the display to outstanding search requests sent
from the specified LU.

Specifying the FROMCP operand limits the display to outstanding search requests
sent from the specified CP.

Specifying the FROMSSCP limits the display to the outstanding search requests
sent from the specified SSCP.

Specifying the LU1 or LU2 operand limits the display to the outstanding search
requests sent to or received from the specified LU.

Specifying the TOCP operand limits the display to the outstanding search requests
sent to the specified CP.

Specifying the TOSSCP operand limits the subarea information displayed to those
search requests targeted for a particular SSCP.

Examples
Displaying summary of outstanding search requests.
D NET,SRCHINFO,LIST=SUMMARY
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SRCHINFO
IST1520I SUBAREA SEARCH INFORMATION:
IST1521I TOSSCP NAME CDINIT DSRLST IOCD INITOT TOTAL
IST1522I SSCP1A 0 1 0 2 3
IST1525I TOTAL NUMBER OF OUTSTANDING SEARCHES = 3
IST1454I 1 SSCP NAME(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1526I APPN SEARCH INFORMATION:
IST1527I TOCP NAME TYPE STATUS BROADCAST DIRECTED TOTAL
IST1528I NETA.SSCPAA NN OPEN 2 1 3
IST1525I TOTAL NUMBER OF OUTSTANDING SEARCHES = 3
IST1454I 1 CP NAME(S) DISPLAYED
IST314I END

Displaying detail information about outstanding requests.

D NET,SRCHINFO,LIST=ALL
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SRCHINFO
IST1520I SUBAREA SEARCH INFORMATION:

184 SNA Operation

 DISPLAY SRCHINFO
IST1523I OLU DLU SID RU
IST1524I NETA.APPL1 NETA.SSCP1A ****NA**** DSRLST
IST1524I NETA.APPL2 NETA.SSCP1A ****NA**** INITOT
IST1524I NETA.SSCP1A NETA.SSCP1A ****NA**** INITOT
IST1454I 3 PAIR(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1526I APPN SEARCH INFORMATION:
IST1529I OLU DLU SID LOCATE
IST1530I NETA.SSCP1A NETA.SSCP2A EAABEEC3C6093893 1
IST1530I NETB.SSCP7B NETA.NETAPPL2 C2BB19BCF437741D 1
IST1530I NETB.SSCP7B NETA.NETAPPL1 C2BB19BCF437741C 1
IST1525I TOTAL NUMBER OF OUTSTANDING SEARCHES = 3
IST1454I 3 PAIR(S) DISPLAYED
IST314I END

Displaying outstanding information about a specific request.

D NET,SRCHINFO,SID=EAABEEC3C6093891
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SRCHINFO
IST1520I SUBAREA SEARCH INFORMATION:
IST1531I SID = EAABEEC3C6093891 CP(OLU) = SSCP1A
IST1532I OLU = NETA.APPL1 DLU = NETA.NETAPPL1
IST1540I SEARCH STATUS = PDSRLST SSCP(OLU) = SSCP1A
IST1539I PCID MODIFIER = 00000000000000000000
IST1534I SSCP/CP IN OLU DIRECTION = NETA.SSCP1A
IST1533I SEARCH CONCENTRATED = NO RDS = NO
IST894I ADJSSCPS TRIED FAILURE SENSE ADJSSCPS TRIED FAILURE SENSE
IST895I SSCP2A 08420000
IST1454I 1 ADJSSCP(S) DISPLAYED
IST1537I AWAITING REPLY FROM THE FOLLOWING NODE(S):
IST1538I NETA.ISTAPNCP
IST924I -------------------------------------------------------------
IST1526I APPN SEARCH INFORMATION:
IST1531I SID = EAABEEC3C6093891 CP(OLU) = NETA.SSCP1A
IST1532I OLU = NETA.APPL1 DLU = NETA.NETAPPL1
IST1539I PCID MODIFIER = 10000000000000000000
IST1545I NODE ROLE VECTOR = X'A000'
IST1541I LOCATES PENDING = 0 CURRENT TASK = X'0B'
IST1533I SEARCH CONCENTRATED = YES RDS = NO
IST1534I SSCP/CP IN OLU DIRECTION = NETA.SSCP1A
IST1535I REPLY RETURNED TO ORIGINATING CP = NO
IST1536I CONCENTRATED BEHIND C2BB19BCF437741C 22100000000000000000
IST924I -------------------------------------------------------------
IST1531I SID = C2BB19BCF437741C CP(OLU) = NETB.SSCP7B
IST1532I OLU = NETB.SSCP7B DLU = NETA.NETAPPL1
IST1539I PCID MODIFIER = 22100000000000000000
IST1545I NODE ROLE VECTOR = X'2000'
IST1541I LOCATES PENDING = 1 CURRENT TASK = X'17'
IST1533I SEARCH CONCENTRATED = NO RDS = YES
IST1548I BROADCAST = YES DIRECTED = NO
IST1534I SSCP/CP IN OLU DIRECTION = NETB.SSCP7B
IST1535I REPLY RETURNED TO ORIGINATING CP = NO
IST1537I AWAITING REPLY FROM THE FOLLOWING NODE(S):
IST1538I NETA.SSCPAA
IST1543I REQUESTS CONCENTRATED BEHIND THIS SEARCH = 1
IST314I END

Chapter 2. VTAM Operator Commands 185

DISPLAY STATIONS

DISPLAY STATIONS Command

ÊÊ DISPLAY NET,STATIONS Ê
(1)
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
Ê ÊÍ
,MAX= * ALL
number_of_resources ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY STATIONS command displays the status of all cross-subarea link
stations for active major nodes.

186 SNA Operation

 DISPLAY STATIONS
Operands
ID=name
specifies the name of one or more major nodes, groups, lines, or link stations. If
this operand is specified, information is displayed about only the link stations
associated with the specified nodes. If this operand is omitted, information is
displayed about all link stations in every active major node.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every major node, group, line, and link station in the network.
MAX
specifies the maximum number of cross-subarea link stations that VTAM
displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of cross-subarea link stations that VTAM displays for
this command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer cross-subarea link stations are found
than you have specified on MAX, VTAM displays only the stations that are
found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable cross-subarea link stations within each major node or
associated with a specific node. If this display is undesirably large, you can
use SCOPE=ACTONLY or SCOPE=CONCT to further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all cross-subarea link
stations in an active state within each major node or associated with a
specific node. The display does not include link stations in pending or
connectable states. If no link stations are found in an active state, you can
use SCOPE=ACT to broaden the scope of the display to include those in
active, connectable, and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all cross-subarea link
stations that are active with sessions within each major node or associated
with a specific node.

Chapter 2. VTAM Operator Commands 187

DISPLAY STATIONS
SCOPE=ALL
specifies that information is to be displayed about all cross-subarea link
stations within each major node or associated with a specific node
(regardless of their status).
SCOPE=CONCT
specifies that information is to be displayed about all cross-subarea link
stations in a CONCT (connectable) state within each major node or
associated with a specific node. If no link stations are found in a
connectable state, you can use SCOPE=ACT to broaden the scope of the
display to include those in active, connectable, and pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive cross-subarea
link stations within each major node or associated with a specific node. If
this display is undesirably large, you can use SCOPE=INACTONLY or
SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive cross-subarea
link stations within each major node or associated with a specific node.
Resources in a RESET state are not included in the SCOPE=INACTONLY
display.
SCOPE=PENDING
specifies that information is to be displayed about all pending cross-subarea
link stations within each major node or associated with a specific node. A
pending state is a transient state to or from the fully active state.
SCOPE=RESET
specifies that information is to be displayed about cross-subarea link
stations in a RESET state within each major node or associated with a
specific node.

Resulting Display
The resulting display shows:
v For each major node containing physical units that have subordinate link stations
(host PU, NCP major node, or channel-attachment major node), or a node with
subordinate or associated link stations:
– The name of the major node
– The subarea address of the major node (if it has one)
v For each link station:
– The name and status of the link.
– The name and status of the link station.
– The current transmission group number.
– The defined transmission group number. (If no specific transmission group
number was defined, it is displayed as 0.)
– The name (if known) and subarea (if known) of any adjacent NCP or host with
which the link station is currently associated, and the name of the network in
which the adjacent NCP or host reside.

Examples
Displaying a specific cross-subarea link station:

188 SNA Operation

 DISPLAY STATIONS
d net,stations,id=a31p04a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATIONS
IST393I PU T4/5 MAJOR NODE A3162ZC, SUBAREA = 310
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A31P04A NEVAC 1 1 0
IST610I LINE A31C04 - STATUS NEVAC
IST314I END

Displaying all cross-subarea link stations:

d net,stations
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATIONS
IST393I PU T4/5 MAJOR NODE ISTPUS , SUBAREA = 500
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I 0016-S ACTIV----I 1 1 A3162ZC 310 NETA
IST610I LINE 0016-L - STATUS ACTIV----I
IST397I 0015-S ACTIV----I 1 1 A0362ZC 3 NETA
IST610I LINE 0015-L - STATUS ACTIV----I
IST393I PU T4/5 MAJOR NODE A0362ZC, SUBAREA = 3
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A03P08A NEVAC 0 0 0
IST610I LINE A03C08 - STATUS NEVAC
IST397I A03P10A NEVAC 1 1 0
IST610I LINE A03C10 - STATUS NEVAC
IST393I PU T4/5 MAJOR NODE A3162ZC, SUBAREA = 310
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I A31P00A NEVAC 1 1 0
IST610I LINE A31C00 - STATUS NEVAC
IST397I A31P01A NEVAC 1 1 0
IST610I LINE A31C01 - STATUS NEVAC
IST397I A31P02A NEVAC 1 1 0
IST610I LINE A31C02 - STATUS NEVAC
IST397I A31P03A NEVAC 1 1 0
IST610I LINE A31C03 - STATUS NEVAC
IST397I A31P04A NEVAC 1 1 0
IST610I LINE A31C04 - STATUS NEVAC
IST397I A31P05A NEVAC 1 1 0
IST610I LINE A31C05 - STATUS NEVAC
IST397I A31P06A NEVAC 1 1 0
IST610I LINE A31C06 - STATUS NEVAC
IST314I END

Displaying cross-subarea link stations, limiting output to 6 resources:

d net,stations,max=6
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATIONS
IST393I PU T4/5 MAJOR NODE ISTPUS, SUBAREA = 1
IST1358I NO QUALIFYING MATCHES
IST393I PU T4/5 MAJOR NODE NCP3AA1, SUBAREA = 3
IST394I ADJACENT LINK STATIONS NOT OWNED BUT AWAITING ACTIVATION
IST395I LS4A3A4 LS4A3A3 LS4A3A2 LS4A3A1
IST396I LNKSTA STATUS CTG GTG ADJNODE ADJSA NETID ADJLS
IST397I LS3A4A1 NEVAC 2 2
IST610I LINE LN3A4A1 - STATUS NEVAC
IST397I LS3A4A2 NEVAC 2 2
IST610I LINE LN3A4A2 - STATUS NEVAC
IST1315I DISPLAY TRUNCATED AT MAX = 6
IST1454I 6 RESOURCE(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 189

DISPLAY STATS

DISPLAY STATS Command

Display resource statistics:

,MAX=DSPLYDEF_start_option_value
ÊÊ DISPLAY NET,STATS ,TYPE=VTAM ÊÍ
, MAX = *
NUM number_of_resources

Display data compression statistics:

ÊÊ DISPLAY NET,STATS ,TYPE=COMPRESS ÊÍ

Display coupling facility structure statistics:

,STRNAME=STRGR_start_option_value
ÊÊ DISPLAY NET,STATS ,TYPE=CFS ÊÍ
,STRNAME= structure_name
*

Abbreviations
Operand Abbreviation
DISPLAY D
STRNAME STRNM

Purpose
The DISPLAY STATS (statistics) command displays information about the network,
such as the number of resources of each type, the values of certain start options,
the MVS coupling facility structure, and data compression.

This information can be used with the OS/390 eNetwork Communications Server:
SNA Planning and Migration Guide to calculate the amount of storage required for
VTAM. For information on how to use the host-based storage information in this
display, see the OS/390 eNetwork Communications Server: SNA Planning and
Migration Guide.

Attention: Depending on the size and configuration of your network, issuing this
command from the console or from the ISTSTATS program operator might affect
system performance. Issuing the DISPLAY STATS command from the console is
not recommended.

Operands
MAX
specifies the maximum number of output lines that VTAM displays for this
command. MAX is valid only when TYPE=VTAM is specified.

Attention: MAX=* might generate an undesirably large display. Do not use

MAX=* until you understand the potential effect of this command on your
console.

190 SNA Operation

 DISPLAY STATS
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_output_lines
specifies the maximum number of statistics to display. The valid range is
1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.
NUM
is a synonym for the MAX operand.
STRNAME
specifies which VTAM coupling facility structure to display.
STRNAME=structure_name
specifies the name of a VTAM coupling facility structure to display. The
structure name can be 1 to 16 characters long.
STRNAME=*
specifies that all VTAM structures are to be displayed.
TYPE
specifies what type of statistical information to display.
TYPE=VTAM
displays information about the type and number of resources in the network
and the values of certain start options.
TYPE=COMPRESS
displays information about data compression.
TYPE=CFS
displays attributes for the MVS coupling facility structure.

Resulting Display
The resulting display shows:
v For TYPE=VTAM, a function ID for each resource type, the number of resources
of each type, and the values of certain start options.
v For TYPE=COMPRESS, the number of half-sessions by active compression level
that use data compression on input and output flows.
Output values for adaptive compression levels are split into BASIC and FROZEN.
BASIC indicates the number of half-sessions currently using compression tables
in the adaptive mode. FROZEN indicates the number of half-sessions currently
using static compression tables.
Output values for sessions using run-length encoding (RLE) compression levels
are also split into BASIC and FROZEN. BASIC indicates the number of
half-sessions currently using compression tables in the basic mode. FROZEN
does not apply to RLE compression.
v For TYPE=CFS, the attributes for the MVS coupling facility structure identified on
the STRNAME operand.

Examples
Displaying statistical information:
d net,stats,type=vtam,max=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=VTAM

Chapter 2. VTAM Operator Commands 191

DISPLAY STATS
IST1349I COMPONENT ID IS 5695-11701-401
IST1345I ID VALUE DESCRIPTION
IST1227I 151 0 = DEPENDENT LU TOTAL FOR ISTPUS
IST1227I 151 32 = DEPENDENT LU TOTAL FOR NCP3AB7
IST1227I 11 0 = CHANNEL-TO-CHANNEL ATTACHMENTS
IST1227I 61 0 = SNA DATA COMPRESSION SESSIONS
IST1227I 63 20 = RECOVERABLE SESSIONS
IST1227I 56 6 = TOTAL APPL SESSIONS
IST1227I 58 6 = LU6.2 SESSIONS
IST1227I 60 0 = ICSF ENCRYPTION SERVICES
IST1227I 67 0 = PU STATEMENTS UNDER SW LINES
IST1227I 15 0 = SNA PU TOTAL MAXBFRU
IST1227I 21 0 = ICA DEVICES
IST1227I 51 40 = ACTIVE LU TOTAL
IST1227I 10 0 = TOTAL LINE STATEMENTS FOR XCA MAJOR NODES
IST1227I 14 0 = CA CLUSTER CONTROLLER TOTAL
IST1227I 2 200 = VIT TABLE SIZE
IST1227I 65 61 = NUMBER OF LINES DEFINED
IST1227I 3 256 = IOBUF SIZE
IST1227I 47 511 = MAXIMUM SUBAREA
IST1227I 48 88 = DEFINED PU TOTAL
IST1227I 49 5 = ACTIVE PU TOTAL
IST1227I 16 0 = LOCAL NON-SNA TERMINALS
IST1227I 80 28 = NETWORK INDEPENDENT LU TOTAL
IST1227I 81 0 = DYNAMICALLY DEFINED LU TOTAL
IST1227I 6 16 = MAXBFRU FOR CHANNEL-ATTACHED CONTROLLERS
IST1227I 8 0 = XCA MAJOR NODES
IST1227I 74 0 = CROSS NETWORK APPL SESSIONS
IST1227I 17 0 = NETVIEW PIU TRACE BUFFER SIZE
IST1227I 18 2 = NETVIEW PIU TRACE BUFFERS
IST1227I 19 0 = NETVIEW SAW BUFFER SIZE
IST1227I 68 0 = MAXNO OPERAND
IST1227I 46 27 = INDEPENDENT LU TOTAL
IST1227I 52 0 = ACTIVE DEPENDENT LU TOTAL
IST1227I 66 2 = SWNET STATEMENTS
IST1227I 69 0 = MXGRP OPERAND
IST1227I 99 ICN = VTAM CONFIGURATION
IST1227I 70 7 = PATH STATEMENTS
IST1227I 77 6 = SAME DOMAIN LU6.2 SESSIONS
IST1227I 78 0 = CROSS DOMAIN LU6.2 SESSIONS
IST1227I 79 0 = CROSS NETWORK LU6.2 SESSION
IST1227I 50 76 = DEFINED LU TOTAL
IST1227I 57 1 = LU6.2 APPLICATIONS
IST1227I 53 0 = LOCAL LU-LU SESSIONS
IST1227I 55 0 = LU TOTAL TSO SESSIONS
IST1227I 71 0 = APPL - LU SESSIONS
IST1227I 73 0 = CROSS DOMAIN LU SESSIONS
IST1227I 5 2 = CHANNEL-ATTACHED CONTROLLERS
IST1227I 12 0 = TOTAL MAXBFRU FOR CTC ATTACHMENTS
IST1227I 13 0 = CTC TOTAL MAXBFRU CROSS DOMAIN
IST1227I 54 0 = PERSISTENT LU-LU SESSIONS
IST1227I 20 0 = NETVIEW SAW BUFFERS
IST1227I 22 2 = DESTINATION SUBAREAS
IST1227I 101 NO = CENTRAL DIRECTORY SERVER SUPPORT
IST1227I 123 0 = MPC READ BUFFER
IST1227I 64 6 = CURRENT NUMBER OF SESSION PARTNERS
IST1227I 100 2 = DYNAMIC DIRECTORY ENTRIES
IST1227I 102 1 = REGISTERED DIRECTORY ENTRIES
IST1227I 103 0 = SYSTEM DEFINED DIRECTORY ENTRIES
IST1227I 104 0 = ADJACENT END NODES
IST1227I 106 0 = CENTRAL DIRECTORY SERVER
IST1227I 107 1 = ADJACENT NETWORK NODES
IST1227I 108 7 = APPN CLASS OF SERVICE
IST1227I 109 3 = NETWORK NODES IN THE NETWORK
IST1227I 111 0 = CONNECTION NETWORKS
IST1227I 116 0 = INTERMEDIATE ROUTED SESSIONS
IST1227I 119 0 = CROSS NETWORK LU SESSIONS

192 SNA Operation

 DISPLAY STATS
IST1227I 120 0 = MULTIPATH CHANNEL MAJOR NODES
IST1227I 121 0 = MPC READ SUBCHANNEL ADDRESSES
IST1227I 122 0 = MPC WRITE SUBCHANNEL ADDRESSES
IST1227I 124 0 = MPC WRITE BUFFER
IST1227I 125 0 = APPLICATION SESSIONS
IST1227I 113 0 = PARALLEL SESSION PER LU
IST1227I 112 0 = CROSS DOMAIN APPL SESSIONS
IST1227I 130 NO = ANYNET/MVS SNA OVER TCP/IP INSTALLED
IST1227I 127 0 = TCP/IP MAJOR NODES
IST1227I 128 0 = MAXIMUM TCB VALUE FOR TCP/IP MAJOR NODES
IST1227I 129 0 = TCP/IP LU-LU SESSIONS
IST1227I 140 2147483647 = MAXIMUM DIRECTORY SIZE
IST1227I 141 100 = MAXIMUM TRS ROUTING TREES
IST1227I 142 0 = END NODE TRANSMISSION GROUPS
IST1227I 143 1 = NETWORK NODE TRANSMISSION GROUPS
IST1227I 144 0 = VIRTUAL NODE TRANSMISSION GROUPS
IST1227I 152 2 = ACTIVE DEPENDENT LU REQUESTERS
IST1227I 153 3 = ACTIVE DLUR SERVED PU TOTAL
IST1227I 154 12 = ACTIVE DLUR SERVED LU TOTAL
IST1227I 155 0 = VR-BASED TRANSMISSION GROUPS
IST1227I 156 0 = CONNECTION NETWORK DYNAMIC TGS
IST1227I 157 0 = TRANSPORT RESOURCE LIST ENTRIES
IST1227I 159 UNKNOWN = ADJACENT CLUSTER TABLE CPNAME ENTRIES
...
IST1227I 163 1 = VIT DATA SPACE TABLE SIZE
IST314I END

Displaying statistical information, limiting output to 5 resources:

d net,stats,type=vtam,max=5
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=VTAM
IST1349I COMPONENT ID IS 5695-11701-401
IST1345I ID VALUE DESCRIPTION
IST1227I 151 0 = DEPENDENT LU TOTAL FOR ISTPUS
IST1227I 11 0 = CHANNEL-TO-CHANNEL ATTACHMENTS
IST1227I 61 0 = SNA DATA COMPRESSION SESSIONS
IST1227I 63 2 = RECOVERABLE SESSIONS
IST1227I 56 0 = TOTAL APPL SESSIONS
IST1315I DISPLAY TRUNCATED AT MAX = 5
IST314I END

Displaying data compression statistics:

d net,stats,type=compress
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=COMPRESS
IST1435I LEVEL INPUT OUTPUT
IST1176I BASIC FROZEN
IST1177I 0 13910 13800 **NA**
IST1177I 1 489 164 **NA**
IST1177I 2 701 833 404
IST1177I 3 286 55 20
IST1177I 4 90 147 53
IST314I END

Displaying the default coupling facility structure:

d net,stats,type=cfs
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE ISTGENERIC
IST1371I STRUCTURE TYPE = LIST - VERSION NUMBER = AD757CBBFFC67504
IST1517I LIST HEADERS = 4 - LOCK HEADERS = 4
IST1373I STORAGE ELEMENT SIZE = 1024
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT

Chapter 2. VTAM Operator Commands 193

DISPLAY STATS
IST1375I STRUCTURE SIZE 10240K 25088K 0
IST1376I STORAGE ELEMENTS 0 972 0
IST1377I LIST ENTRIES 1 48595 0
IST314I END

Displaying all coupling facility structures:

d net,stats,type=cfs,strname=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE ISTMNPS
IST1371I STRUCTURE TYPE = LIST - VERSION NUMBER = AD757CB8DD617C85
IST924I -------------------------------------------------------------
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE ISTGENERIC
IST1371I STRUCTURE TYPE = LIST - VERSION NUMBER = AD757CBBFFC67504
IST314I END

Displaying a multinode persistent session coupling facility structure:

d net,stats,type=cfs,strname=istmnps
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS 457
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE ISTMNPS
IST1371I STRUCTURE TYPE = LIST - VERSION NUMBER = AD757CB8DD617C85
IST1517I LIST HEADERS = 256 - LOCK HEADERS = 0
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 10240K 25088K 7
IST1376I STORAGE ELEMENTS 1188 25401 4
IST1377I LIST ENTRIES 1050 12700 8
IST314I END

Displaying a multinode persistent session coupling facility structure with alternate

structures:
d net,stats,type=cfs,strname=istmnps
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS 230
IST1370I NETA.A81N IS CONNECTED TO STRUCTURE ISTMNPS
IST1371I STRUCTURE TYPE = LIST - VERSION NUMBER = AD885DB859A3A084
IST1517I LIST HEADERS = 256 - LOCK HEADERS = 0
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 6144K 12288K 11
IST1376I STORAGE ELEMENTS 3617 15422 23
IST1377I LIST ENTRIES 696 7711 9
IST924I -------------------------------------------------------------
IST1519I ALTERNATE STRUCTURES ARE:
IST1567I ISTMNPS02 ISTMNPS01
IST314I END

194 SNA Operation

 DISPLAY STORUSE

DISPLAY STORUSE Command

Display storage usage for applications:

ÊÊ DISPLAY NET,STORUSE ,APPL= * Ê

,

»( appl_name )

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
, MAX = *
NUM number_of_resources

Display storage usage for application jobs:

ÊÊ DISPLAY NET,STORUSE ,JOBNAME= * Ê

,

»( appl_job_name )

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
, MAX = *
NUM number_of_resources

Display storage usage for data spaces:

ÊÊ DISPLAY NET,STORUSE ,DSPNAME= * Ê

,

( » data_space_name )

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
, MAX = *
NUM number_of_resources

Display storage usage for storage pools:

ÊÊ DISPLAY NET,STORUSE Ê

,POOL=*
Ê Ê
,POOL= *
SUMMARY
,

( » storage_pool_name )
,SUMMARY

Chapter 2. VTAM Operator Commands 195

DISPLAY STORUSE
,LIST=ALL ,MAX=DSPLYDEF_start_option_value
Ê Ê
,LIST= ALL , MAX = *
INUSE NUM number_of_resources

,POOLTYPE=ALL
Ê ÊÍ
,POOLTYPE= ALL
CSA
PRIVATE

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY STORUSE (storage usage) command provides storage usage
information for VTAM data spaces, modules, and storage pools.

You can specify the name of any one of the following:

v Application
v Application job
v Data space
v Storage pool.

Operands
APPL
specifies the applications for which storage usage will be displayed.
APPL=appl_name
displays storage usage for one or more applications.
APPL=*
displays storage usage for all applications.
DSPNAME
specifies the data spaces for which storage usage information will be displayed.
DSPNAME=data_space_name
displays storage usage for one or more VTAM data spaces.
DSPNAME=*
displays storage usage for all VTAM data spaces.
JOBNAME
specifies the VTAM application jobs for which storage usage will be displayed.
JOBNAME=appl_job_name
displays storage usage for one or more VTAM application jobs.
JOBNAME=*
displays storage usage for all VTAM application jobs.
LIST
specifies whether storage information should be displayed about all pools or
only those currently in use.

196 SNA Operation

 DISPLAY STORUSE
The LIST operand is valid only when all GETBLK pools are being displayed and
the POOL, DSPNAME, APPLNAME, and JOBNAME operands are omitted from
the DISPLAY STORUSE command.
LIST=ALL
displays storage information about all pools, regardless of whether storage
is currently allocated from that storage pool.
LIST=INUSE
displays storage information only for pools that have been currently
allocated from that storage pool.
MAX
specifies the maximum number of output lines that VTAM displays for this
command.
MAX=*
specifies that the value of the DSPLYMAX start option limits the display
output.
MAX=number_of_resources
specifies the number of applications, application jobs, data spaces, or
storage pools for which VTAM displays storage usage. The valid range is
1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified, stopping when it reaches that
number. VTAM does not search any further. This saves processing time and
gives you control over the amount of display output generated by the
command. If fewer applications, application jobs, data spaces, or storage
pools are found than you have specified on MAX, VTAM displays only the
storage usage information for those found.
NUM
is a synonym for the MAX operand.
POOL
specifies the VTAM storage pools for which storage usage will be displayed.
Use * to display a list of valid pool names available in your system.
POOL=storage_pool_name
displays storage usage for one or more VTAM storage pools.
POOL=SUMMARY
displays storage usage collectively for all storage pools and modules.

The information supplied by SUMMARY is independent of the information

supplied by storage_pool_name. SUMMARY can be specified with or
without storage_pool_name.
POOL=*
displays storage usage collectively and individually for all VTAM storage
pools, and collectively for all VTAM modules.

For descriptions of the functions and characteristics of the storage pools

displayed, see the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide.
POOLTYPE
specifies the type of pools for which storage information is to be displayed.

Chapter 2. VTAM Operator Commands 197

DISPLAY STORUSE
The POOLTYPE operand is valid only when all GETBLK pools are being
displayed and the POOL, DSPNAME, APPLNAME, and JOBNAME operands
are omitted from the DISPLAY STORUSE command.
POOLTYPE=ALL
displays storage information about all pools.
POOLTYPE=CSA
displays storage information only for pools in common service area (CSA)
storage.
POOLTYPE=PRIVATE
displays storage information only for pools in VTAM private storage.

Resulting Display
The resulting display shows:
v Pool name or data space name
v Job name
v Application name
v Number of applications
v Current storage
v Maximum storage.

Examples
Displaying storage usage for a specific pool:
d net,storuse,pool=sibext
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1242I POOL CURRENT MAXIMUM
IST1243I SIBEXT 128 128
IST1454I 1 POOL(S) DISPLAYED
IST314I END

Displaying storage usage for pools, limiting output to 5 resources:

d net,storuse,max=5
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1242I POOL CURRENT MAXIMUM POOL CURRENT MAXIMUM
IST1243I ACDEB 4 4 ACPCB 0 0
IST1243I ADJCP 8 8 ADJNODE 0 0
IST1243I ANDCB 0 0
IST1315I DISPLAY TRUNCATED AT MAX = 5
IST1454I 5 RESOURCE(S) DISPLAYED
IST924I --------------------------------------------------------
IST1244I TOTAL PRIVATE POOL STORAGE USAGE: 228 228
IST1244I TOTAL COMMON POOL STORAGE USAGE: 64 64
IST924I -------------------------------------------------------------
IST981I VTAM PRIVATE: CURRENT = 5208K, MAXIMUM USED = 5253K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 40K
IST1565I PRIVATE MODULES = 5205K
IST314I END

Displaying storage usage for pools, in CSA storage that have been currently
allocated from that storage pool:

198 SNA Operation

 DISPLAY STORUSE
d net,storuse,pooltype=csa,list=inuse
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1242I POOL CURRENT MAXIMUM POOL CURRENT MAXIMUM
IST1243I COS 16 16 CPWACSA 4 4
IST1243I CPWAPVT 4 4 EPTDVT 8 8
IST1243I ERICPOOL 8 8 ERTE 4 4
IST1243I FMCB 16 16 NDREC 8 8
IST1243I RUPEPRIV 16 16 UTILPVTS 20 20
IST1454I 10 POOL(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1244I TOTAL PRIVATE POOL STORAGE USAGE: 220 220
IST1244I TOTAL COMMON POOL STORAGE USAGE: 68 68
IST924I -------------------------------------------------------------
IST981I VTAM PRIVATE: CURRENT = 585K, MAXIMUM USED = 639K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 32K
IST1565I PRIVATE MODULES = 5500K
IST314I END

Displaying storage usage for pools, in private storage that have been currently
allocated from that private storage pool:
d net,storuse,pooltype=private,list=inuse
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1242I POOL CURRENT MAXIMUM POOL CURRENT MAXIMUM
IST1243I ACDEB 4 4 CDRSC 32 32
IST1243I DECB 4 4 DISKIO 8 8
IST1243I DMTSQ 4 4 FMCBEXT 4 4
IST1243I LMTABLE 4 4 NIDCB 4 4
IST1243I PAQ 8 8 POWEPRIV 8 8
IST1243I POWMPRIV 8 8 PULURDTE 4 4
IST1243I RUPECOMM 4 4 SRTE 20 20
IST1243I SSCPFMCB 16 16 UTILCSAL 4 4
IST1243I UTILCSAS 20 20 UTILPVTL 20 20
IST1243I WREEID 8 8
IST1454I 19 POOL(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1244I TOTAL PRIVATE POOL STORAGE USAGE: 220 220
IST1244I TOTAL COMMON POOL STORAGE USAGE: 68 68
IST924I -------------------------------------------------------------
IST981I VTAM PRIVATE: CURRENT = 585K, MAXIMUM USED = 639K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 32K
IST1565I PRIVATE MODULES = 5500K
IST314I END

Displaying storage usage for all data spaces, limiting output to 7 resources:
d net,storuse,dspname=*,max=7
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1238I DSPNAME CURRENT MAXIMUM QUEUED
IST1239I ISTNMPDS 0 0 0
IST1239I ISTNMSDS 0 0 0
IST924I -------------------------------------------------------------
IST1240I DSPNAME CURRENT MAXIMUM JOBNAME APPL COUNT
IST1241I ISTFC8E0 8 8 VTAM SSCP1A 1
IST1241I IST68072 0 0 ECHO APPL1 1
IST1241I IST72596 0 0 ECHO APPL2 1
IST1241I IST30B99 0 0 ECHO APPL3 1
IST1241I ISTITDS1 0 0
IST1454I 7 DSPNAME(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 199

DISPLAY STORUSE
Displaying storage usage for a specific data space:
d net,storuse,dspname=istnmsds
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1238I DSPNAME CURRENT MAXIMUM QUEUED
IST1239I ISTNMSDS 0 0 0
IST1454I 1 DSPNAME(S) DISPLAYED
IST314I END

Displaying storage usage for all applications, limiting output to 4 resources:

d net,storuse,appl=*,max=4
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1240I DSPNAME CURRENT MAXIMUM JOBNAME APPL COUNT
IST1241I ISTFC8E0 8 8 VTAM SSCP1A 1
IST1241I IST68072 0 0 ECHO APPL1 1
IST1241I IST72596 0 0 ECHO APPL2 1
IST1241I IST30B99 0 0 ECHO APPL3 1
IST1315I DISPLAY TRUNCATED AT MAX = 4
IST1454I 4 APPL(S) DISPLAYED
IST314I END

Displaying storage usage for a specific job:

d net,storuse,jobname=echo31e
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1240I DSPNAME CURRENT MAXIMUM JOBNAME APPL COUNT
IST1241I 00002IST 0 0 ECHO31E ECHO50A 1
IST1241I 00003IST 0 0 ECHO31E ECHO50 1
IST314I END

Displaying storage usage for a specific application:

d net,storuse,appl=echo02a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1240I DSPNAME CURRENT MAXIMUM JOBNAME APPL COUNT
IST1241I 00001IST 4 16 ECHO31E ECHO02A 1
IST314I END

Displaying storage usage summary information:

d net,storuse,pool=summary
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STORAGE USAGE
IST1244I TOTAL PRIVATE POOL STORAGE USAGE: 228 228
IST1244I TOTAL COMMON POOL STORAGE USAGE: 76 76
IST924I -------------------------------------------------------------
IST981I VTAM PRIVATE: CURRENT = 4550K, MAXIMUM USED = 4603K
IST924I -------------------------------------------------------------
IST1565I CSA MODULES = 1384K
IST1565I CSA24 MODULES = 40K
IST1565I PRIVATE MODULES = 5205K
IST314I END

200 SNA Operation

 DISPLAY TABLE

DISPLAY TABLE Command

ÊÊ DISPLAY NET,TABLE ,ID=table_name Ê

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
This command displays the table type and the number of resources that are
associated with the table (use count) and identifies the users of a table. The tables
displayed include:
v Associated LU (ASLTAB)
v Class-of-service (COSTAB)
v Logon interpret (LOGTAB)
v Logon mode (MODETAB)
v Message-flooding prevention (FLDTAB)
v Model name (MDLTAB)
v USS (USSTAB).
Notes:
1. SAW data filter tables are not displayed by this command.
2. The CMIP services directory definition file is not displayed by this command.

Operands
ID=table_name
specifies the name of the table.
MAX
specifies the maximum number of resources that VTAM displays for this
command.

The MAX operand is only valid when SCOPE=ALL is specified.

Chapter 2. VTAM Operator Commands 201

DISPLAY TABLE
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of resources to display for this command. The valid
range is 1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer resources are found than you have
specified on MAX, VTAM displays only the resources that are found.
SCOPE
specifies whether to display a list of users of the table.
SCOPE=ALL
displays the name of each resource associated with the table. For a COS
table, the use count might be higher than the number of user resource
names displayed for SCOPE=ALL, if the COS table is used by a type 4 or
type 5 physical unit for multiple networks.
SCOPE=ONLY
does not display the names of the resources associated with the table.

Resulting Display
The resulting display shows:
v For SCOPE=ONLY, the table name, type, and use count
v For SCOPE=ALL, the table name, type, use count, and the resources associated
with the table.

Note: If the ID operand specifies the current value of the DYNMODTB start
option, ISTCDRDY is displayed as a resource using the table.

Examples
Displaying all resources for an associated LU table:
d net,table,id=asltab1,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=ASLTAB1 TYPE=ASLTAB USE COUNT=62
IST987I THE RESOURCES THAT USE THE TABLE ARE:
IST988I A04D88A1 A04D88A2 A04D88A3
IST988I A04D8817 A04D8818 A04D8819
IST988I A04D881A A04D881B A04D881C
IST988I A04D881D A04D881E A04D881F
IST988I C23MMNLU A04MMNLU
IST314I END

Displaying all resources for a class-of-service table:

d net,table,id=istsdcos,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=ISTSDCOS TYPE=COSTAB USE COUNT=1
IST987I THE RESOURCES THAT USE THE TABLE ARE:
IST988I ISTPUS
IST314I END

202 SNA Operation

 DISPLAY TABLE
Displaying all resources for a message-flooding prevention table:
d net,table,id=istmsfld,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=ISTMSFLD TYPE=FLDTAB USE COUNT=1
IST987I THE RESOURCES THAT USE THE TABLE ARE:
IST988I ISTNOP
IST314I END

Displaying the use count for a logon interpret table:

d net,table,id=interp,scope=only
IST097I DISPLAY ACCEPTED
IST986I TABLE=INTERP TYPE=LOGTAB USE COUNT=832
IST314I END

Displaying all resources for a logon mode table:

d net,table,id=amodetab,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=AMODETAB TYPE=MODETAB USE COUNT=1227
IST987I THE RESOURCES THAT USE THE TABLE ARE:
IST988I A04I0421 A04I0422 A04I0423
IST988I A04I0424 A04I0425 A04I0431
IST988I A04D52AA A04D52AB A04D52AC
IST988I A04D52AD A04D52AE A04D52AF
IST988I A04D52C1 A04D52C2 A04D52C3
IST988I A04D52C4 A04D52C5 A04D52C6
IST988I A04D52C7 A04D52C8 A04D52C9
IST988I A04D52CA A04D52CB A04D52CC
IST988I A04D52CD A04D52CE A04D52CF
IST314I END

Displaying all resources for a model name table:

d net,table,id=mdltab1,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=MDLTAB1 TYPE=MDLTAB USE COUNT=61
IST987I THE RESOURCES THAT USE THE TABLE ARE:
IST1154I NETA.A03D88A1 NETA.A03D88A2 NETA.A03D88A3
IST1154I NETA.A03D88A4 NETA.A03D88A5 NETA.A03D88A6
IST1154I NETA.A03D88A7 NETA.A03D88A8 NETA.A03D88A9
IST1154I NETA.A03D88AA NETA.A03D88AB NETA.A03D88AC
IST1154I NETA.A03D88AD NETA.A03D88AE NETA.A03D88AF
IST1154I NETA.A03D8871 NETA.A03D8872 NETA.A03D8873
IST1154I NETA.A03D8874 NETA.A03D8875 NETA.A03D8876
IST1154I NETA.A03D8877 NETA.A03D8878 NETA.A03D8879
IST1154I NETA.A03D887A NETA.A03D887B NETA.A03D887C
IST1154I NETA.A03D887D NETA.A03D887E NETA.A03D887F
IST1154I NETA.A03D8841 NETA.A03D8842 NETA.A03D8843
IST1154I NETA.A03D8844 NETA.A03D8845 NETA.A03D8846
IST1154I NETA.A03D8847 NETA.A03D8848 NETA.A03D8849
IST1154I NETA.A03D884A NETA.A03D884B NETA.A03D884C
IST1154I NETA.A03D884D NETA.A03D884E NETA.A03D884F
IST1154I NETX.A03D8811 NETX.A03D8812 NETX.A03D8813
IST1154I NETX.A03D8814 NETX.A03D8815 NETX.A03D8816
IST1154I NETX.A03D8817 NETX.A03D8818 NETX.A03D8819
IST1154I NETX.A03D881A NETX.A03D881B NETX.A03D881C
IST1154I NETX.A03D881D NETX.A03D881E NETX.A03D881F
IST1154I NETA.A03MMNLU
IST314I END

Displaying all resources for a USS table:

d net,table,id=ausstab,scope=all
IST097I DISPLAY ACCEPTED
IST986I TABLE=AUSSTAB TYPE=USSTAB USE COUNT=912
IST987I THE RESOURCES THAT USE THE TABLE ARE:

Chapter 2. VTAM Operator Commands 203

DISPLAY TABLE
IST988I A04D88A1 A04D88A2 A04D88A3
IST988I A04D88A4 A04D88A5 A04D88A6
IST988I A04D52CD A04D52CE A04D52CF
IST988I A04PT88A A04PT89A A04PT92A
IST314I END

204 SNA Operation

 DISPLAY TERMS

DISPLAY TERMS Command

ÊÊ DISPLAY NET,TERMS Ê
(1)
,ID= name
,

( » name )

,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
Ê ÊÍ
,MAX= * ALL
number_of_resources ,SCOPE=

ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RESET

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ACT ACT or A
SCOPE=ACTONLY ACTONLY
SCOPE=ACTSESS ACTSESS
SCOPE=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The DISPLAY TERMS (terminals) command displays the status of device-type
logical units (terminals) that are in active major nodes. The command does not
display information about independent LUs.

Chapter 2. VTAM Operator Commands 205

DISPLAY TERMS
Notes:
1. In a domain that has many terminals, this command might result in an
undesirably large display, especially if the SCOPE=ALL operand, which is the
default, is used. You can limit the display by using a more restrictive SCOPE
value and by specifying the desired major node or nodes on the ID operand.
2. To display device-type logical units independently of the major nodes that
contain them, use the DISPLAY RSCLIST command with IDTYPE=TERMS.

Operands
ID=name
specifies the name of one or more active NCP, local SNA, local non-SNA, or
switched major nodes whose device-type LUs are to be displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every major node in the network.
MAX
specifies the maximum number of terminals that VTAM displays for this
command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of terminals that VTAM displays for this command.
The valid range is 1–value of DSPLYMAX. The default is the value specified
for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer terminals are found than you have
specified on MAX, VTAM displays only the terminals that are found.
SCOPE
specifies the desired scope of the display.

Note: If you specify the SCOPE operand without specifying a value

SCOPE=ALL is assumed.
SCOPE=ACT
specifies that information is to be displayed about all active, pending, and
connectable device-type logical units within the specified major nodes (or
within all major nodes if the ID operand is omitted). If this display is
undesirably large, you can use SCOPE=ACTONLY or SCOPE=CONCT to
further limit the display.
SCOPE=ACTONLY
specifies that information is to be displayed about all device-type logical
units in an active state within the specified major nodes (or within all major
nodes if the ID operand is omitted). The display does not include terminals

206 SNA Operation

 DISPLAY TERMS
in pending or connectable states. If no terminals are found in an active
state, you can use SCOPE=ACT to broaden the scope of the display to
include terminals in active, connectable, and pending states.
SCOPE=ACTSESS
specifies that information is to be displayed about all device-type logical
units that are active with sessions within the specified major nodes (or
within all major nodes if the ID operand is omitted).
SCOPE=ALL
specifies that information is to be displayed about all device-type logical
units (regardless of their status) within the specified major nodes (or within
all major nodes if the ID operand is omitted).
SCOPE=CONCT
specifies that information is to be displayed about all device-type logical
units in a CONCT (connectable) state within the specified major nodes (or
within all major nodes if the ID operand is omitted). If no terminals are
found in a connectable state, you can use SCOPE=ACT to broaden the
scope of the display to include terminals in active, connectable, and
pending states.
SCOPE=INACT
specifies that information is to be displayed about all inactive device-type
logical units within the specified major nodes (or within all major nodes if
the ID operand is omitted). If this display is undesirably large, you can use
SCOPE=INACTONLY or SCOPE=RESET to further limit the display.
SCOPE=INACTONLY
specifies that information is to be displayed about all inactive device-type
logical units within the specified major nodes (or within all major nodes if
the ID operand is omitted). Resources in a RESET state are not included in
the SCOPE=INACTONLY display.
SCOPE=PENDING
specifies that information is to be displayed about all pending device-type
logical units within the specified major nodes (or within all major nodes if
the ID operand is omitted). A pending state is a transient state to or from
the fully active state.
SCOPE=RESET
specifies that information is to be displayed about all device-type logical
units in a RESET state within the specified major nodes (or within all major
nodes if the ID operand is omitted).

Resulting Display
For each major node with terminals, the resulting display shows:
v The major node name
v The line name and status (if the terminal is attached over a line)
v The name and status of the associated physical unit (if any)
v The name and status of the logical unit.

Note: Physical units and logical units in a switched major node are always listed
under the switched major node and never under the NCP or
channel-attachment major node containing the switched link through which

Chapter 2. VTAM Operator Commands 207

DISPLAY TERMS
they are attached. To determine the name of this NCP or channel-attachment
major node and line, enter a “DISPLAY ID Command” with ID=pu_name or
ID=lu_name.

Examples
Displaying terminals within a specific node:
d net,terms,id=a50local
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LOGICAL UNITS/TERMS
IST351I LOCAL 3270 MAJOR NODE = A50LOCAL
IST089I A50A720 TYPE = LOGICAL UNIT , NEVAC ,CUA=0720
IST089I A50A721 TYPE = LOGICAL UNIT , ACTIV ,CUA=0721
IST089I A50A722 TYPE = LOGICAL UNIT , ACT/S ,CUA=0722
IST089I A50A723 TYPE = LOGICAL UNIT , ACTIV ,CUA=0723
IST089I A50A724 TYPE = LOGICAL UNIT , ACTIV ,CUA=0724
IST089I A50A725 TYPE = LOGICAL UNIT , ACTIV ,CUA=0725
IST089I A50A726 TYPE = LOGICAL UNIT , NEVAC ,CUA=0726
IST314I END

Displaying all terminals:

d net,terms
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LOGICAL UNITS/TERMS
IST353I SWITCHED SNA MAJOR NODE = ISTDSWMN
IST146I LINE NAME = J000400B, STATUS = ACTIV
IST359I ATTACHMENT = SWITCHED
IST089I A04P88A TYPE = PU_T2 , ACTIV---X-
IST355I LOGICAL UNITS:
IST080I A04D88A1 ACTIV---X- A04D88A2 ACTIV---X- A04D88A3 ACT/S---X-
IST080I A04D88A4 ACTIV---X- A04D88A5 ACTIV---X- A04D88A6 ACTIV---X-
IST080I A04D88A7 ACTIV---X- A04D88A8 ACTIV---X- A04D88A9 ACTIV---X-
IST080I A04D88AA ACTIV---X- A04D88AB ACT/S---X- A04D88AC ACT/S---X-
IST080I A04D88AD ACT/S---X- A04D88AE ACT/S---X- A04D88AF ACT/S---X-
IST146I LINE NAME = J0004011, STATUS = ACTIV
IST359I ATTACHMENT = SWITCHED
IST089I A04P887 TYPE = PUT_2 , ACTIV---X-
IST355I LOGICAL UNITS:
IST080I A04D8871 ACTIV---X- A04D8872 ACTIV---X- A04D8873 ACTIV---X-
IST080I A04D8874 ACTIV---X- A04D8875 ACTIV---X- A04D8876 ACTIV---X-
IST080I A04D8877 ACTIV---X- A04D8878 ACTIV---X- A04D8879 ACTIV---X-
IST080I A04D887A ACTIV---X- A04D887B ACT/S---X- A04D887C ACT/S---X-
IST080I A04D887D ACT/S---X- A04D887E ACT/S---X- A04D887F ACT/S---X-
IST146I LINE NAME = J0004017, STATUS = ACTIV
IST359I ATTACHMENT = SWITCHED
IST089I A04P884 TYPE = PUT_2 , ACTIV---X-
IST355I LOGICAL UNITS:
IST080I A04D8841 ACTIV---X- A04D8842 ACT/S---X- A04D8843 ACT/S---X-
IST080I A04D8844 ACT/S---X- A04D8845 ACTIV---X- A04D8846 ACTIV---X-
IST080I A04D8847 ACTIV---X- A04D8848 ACTIV---X- A04D8849 ACTIV---X-
IST080I A04D884A ACTIV---X- A04D884B ACT/S---X- A04D884C ACT/S---X-
IST080I A04D884D ACT/S---X- A04D884E ACT/S---X- A04D884F ACT/S---X-
IST146I LINE NAME = J000401D, STATUS = ACTIV
IST359I ATTACHMENT = SWITCHED
IST089I A04P881 TYPE = PUT_2 , ACTIV---X-
IST355I LOGICAL UNITS:
IST080I A04D8811 ACTIV---X- A04D8812 ACT/S---X- A04D8813 ACTIV---X-
IST080I A04D8814 ACTIV---X- A04D8815 ACT/S---X- A04D8816 ACTIV---X-
IST080I A04D8817 ACTIV---X- A04D8818 ACTIV---X- A04D8819 ACTIV---X-
IST080I A04D881A ACTIV---X- A04D881B ACTIV---X- A04D881C ACTIV---X-
IST080I A04D881D ACT/S---X- A04D881E ACT/S---X- A04D881F ACTIV---X-
IST314I END

Displaying terminals, limiting output to 3 resources:

208 SNA Operation

 DISPLAY TERMS
d net,terms,max=3
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LOGICAL UNITS/TERMS
IST354I PU T4/5 MAJOR NODE = NCP3AA1
IST146I LINE NAME = LN3A1, STATUS = NEVAC
IST359I ATTACHMENT = LEASED
IST089I P3A3767A TYPE = PU_T1 , NEVAC
IST355I LOGICAL UNITS:
IST080I L3A3767A NEVAC
IST089I P3A3274A TYPE = PU_T2 , NEVAC
IST355I LOGICAL UNITS:
IST080I L3A3278A NEVAC L3A3279A NEVAC
IST1315I DISPLAY TRUNCATED AT MAX = 3
IST1454I 3 RESOURCE(S) DISPLAYED
IST314I END

Chapter 2. VTAM Operator Commands 209

DISPLAY TGPS

DISPLAY TGPS Command

ÊÊ DISPLAY NET,TGPS Ê
(1)
,ID= tg_profile_name
,

»( tg_profile_name )

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Abbreviations
Operand Abbreviation
DISPLAY D
TGPS TGP

Purpose
The DISPLAY TGPS (transmission group profiles) command displays the currently
defined TG profiles by name, along with the transmission group characteristics that
they represent. For more information on defining a transmission group profile, see
the OS/390 eNetwork Communications Server: SNA Resource Definition Reference.
This command is valid only when it is issued at an APPN node (network node, end
node, interchange node, or migration data host).

Operands
ID=tg_profile_name
specifies the name of one or more transmission group profiles to display. If you
omit the ID operand, all profiles are displayed.

Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand. For more information about using wildcards, see “Using
Wildcard Names” on page 14.

Attention: Specifying a wildcard name might degrade performance because

VTAM checks every transmission group profile in the network.
MAX
specifies the maximum number of transmission group profiles that VTAM
displays for this command.
MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.

210 SNA Operation

 DISPLAY TGPS
MAX=number_of_resources
specifies the number of transmission group profiles that VTAM displays for
this command. The valid range is 1–value of DSPLYMAX. The default is the
value specified for the DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer transmission group profiles are found
than you have specified on MAX, VTAM displays only the transmission
group profiles that are found.

Resulting Display
The resulting display shows the TG profile names and the TG characteristics that
are defined to VTAM. The TG characteristics are shown in a 16-byte hex string.
Byte Description
1 Flag byte. This byte is zero when you display a TG profile, but other values
might appear when you display the TG characteristics for an active
resource (for example, the output of the DISPLAY ADJCP command).
2 Capacity. This value corresponds to the CAPACITY value coded in the TGP
definition statement. The displayed value is an internal representation of the
coded value. For more information on how the CAPACITY value coded in
the TG profile is mapped to the internal representation used by VTAM, see
the OS/390 eNetwork Communications Server: SNA Resource Definition
Reference.
3–7 Reserved (zero)
8 Cost per unit time. This value corresponds to the COSTTIME value coded
in the TGP definition statement.
9 Cost per byte. This value corresponds to the COSTBYTE value coded in
the TGP definition statement.
10 Reserved (zero)
11 Security. This value corresponds to the SECURITY value coded in the TGP
definition statement as follows:
X'01' UNSECURE
X'20' PUBLIC
X'40' UNDERGRO
X'60' SECURE
X'80' GUARDED
X'A0' ENCRYPT
X'C0' SHIELDED
12 Propagation delay. This value corresponds to the PDELAY value coded in
the TGP definition statement as follows:
X'4C' NEGLIGIB
X'71' TERRESTR

Chapter 2. VTAM Operator Commands 211

DISPLAY TGPS
X'91' PACKET
X'99' LONG
13 Reserved (zero)
14–16 User-defined. These values correspond to the values coded for UPARM1,
UPARM2, and UPARM3 respectively in the TGP definition statement.

Examples
Displaying a specific transmission group profile:
d net,tgps,id=secure
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TGPS
IST1107I TGP NAME TG CHARACTERISTICS
IST1108I SECURE 00750000000000969600604C00000000
IST314I END

Displaying all transmission group profiles:

d net,tgps
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TGPS
IST1107I TGP NAME TG CHARACTERISTICS
IST1108I UNSECURE 00750000000000646400014C00000000
IST1108I UNDERGRO 007500000000007D7D00404C00000000
IST1108I SECURE 00750000000000969600604C00000000
IST1108I GUARDED 00750000000000C8C800804C00000000
IST1108I SHIELDED 00750000000000C8FF00C04C00000000
IST1108I TGPL11 00750000000000000000014C00000000
IST1108I TGPL12 00B40000000000000000604C00808080
IST1108I TGPL21 00430000000000000000014C00000000
IST1108I TGPL22 00B400000000000A0A006071003C3C3C
IST1108I TGPL31 00520000000000000000204C003D3D3D
IST1108I TGPL32 00B400000000000A0A00409100808080
IST1108I LOWSWCH 002D00000000003CB400207100808080
IST1108I MEDSWCH 002D0000000000787800207100808080
IST1108I HIGHSWCH 002D0000000000B43C00207100808080
IST1108I LOWLEASE 002D0000000000507800017100808080
IST1108I MEDLEASE 002D0000000000645000017100808080
IST1108I HIGHLEAS 002D0000000000782800017100808080
IST1108I TRINGLOW 007500000000000A1400014C00808080
IST1108I TRINGHI 008500000000000A1400014C00808080
IST1108I CHANNEL 002D0000000000050500604C00808080
IST1108I CHANESCA 002D0000000000050A00604C00808080
IST1108I TGPTESTA 00140000000000FF0000804C00818181
IST1108I TGPTESTB 004A0000000000640000014C003D3D3D
IST1108I TGPTESTC 005200000000000A0000204C003D3D3D
IST1108I TGPLOW 00140000000000FFC800804C00818181
IST1108I TGPMED 004A0000000000006400014C003D3D3D
IST314I END

Displaying transmission group profiles, limiting output to 3 resources:

d net,tgps,max=3
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TGPS
IST1107I TGP NAME TG CHARACTERISTICS
IST1108I PROFILE1 002D0000000000082000014C00808080
IST1108I PROFILE2 003C0000000000000000017100808080
IST1108I PROFILE3 002D0000000000000000019100808080
IST1315I DISPLAY TRUNCATED AT MAX = 3
IST1454I 3 RESOURCE(S) DISPLAYED

212 SNA Operation

 DISPLAY TOPO

DISPLAY TOPO Command

Display a summary of the topology database:

,LIST=SUMMARY
ÊÊ DISPLAY NET,TOPO ÊÍ

Display a specific node:

ÊÊ DISPLAY NET,TOPO ,ID=cp_name ÊÍ

,APPNCOS=cos_name ,LIST=ALL

Display adjacent nodes:

ÊÊ DISPLAY NET,TOPO ,ID=cp_name ,LIST=ADJ ÊÍ

,APPNCOS=cos_name

Display nodes of a specific type:

ÊÊ DISPLAY NET,TOPO ,LIST= BN Ê

CDSERVR ,APPNCOS=cos_name
EN
ICN
NN
VN

,ID=*.*
Ê ÊÍ
(1)
,ID= name
*

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Display a specific TG or TGs:

ÊÊ DISPLAY NET,TOPO ,ORIG=cp_name ,DEST=cp_name Ê

,TGN=tg_number

Ê ,TGN=tg_number ÊÍ
,APPNCOS=cos_name

Abbreviations
Operand Abbreviation
DISPLAY D

Chapter 2. VTAM Operator Commands 213

DISPLAY TOPO
Purpose
The DISPLAY TOPO (topology) command displays information about the topology
of an APPN network. This command is valid only when it is issued at a network
node or an interchange node.

This command displays only the information that is found in the topology database.
Some resources might not be displayed for the following reasons:
v No CP-CP session path exists between the resource and the node from which
this command is issued.
v Information about end nodes and the resources they own is not broadcast to the
network.
v Information between two non-native connections is limited to keep them from
being used as intermediate nodes.

When you display transmission group (TG) information, the order in which you
specify the origin and destination can make a difference. ORIG=A,DEST=B does
not necessarily display the same results as ORIG=B,DEST=A.

The following examples illustrate how this command works.

NN1 NN2

ENA

Figure 3. DISPLAY TOPO Topology Example 1

In Figure 3, end node A (ENA) has a CP-CP session with network node 1 (NN1)
and an active link to network node 2 (NN2). Also, a CP-CP session exists between
NN1 and NN2. The command:
D NET,TOPO,ORIG=NN2,DEST=ENA

issued from NN2 displays the requested TG information. However, the command:
D NET,TOPO,ORIG=ENA,DEST=NN2

issued from NN2 causes an error message, RESOURCE NOT FOUND. Because
ENA is an end node, its TGs are not broadcast to the network, so NN2 does not
know that ENA has a TG from ENA to NN2.

NN1 NN2 NN3

Figure 4. DISPLAY TOPO Topology Example 2

In Figure 4, CP-CP sessions exist between NN1 and NN2 and between NN2 and
NN3. Suppose the link between NN2 and NN3 goes down. The command:

214 SNA Operation

 DISPLAY TOPO
D NET,TOPO,ORIG=NN2,DEST=NN3

issued from NN1 indicates that the TG is inactive, but the command:
D NET,TOPO,ORIG=NN3,DEST=NN2

issued from NN1 indicates that the TG is still active. This is because the link
between NN2 and NN3 appears to VTAM’s topology component to be two one-way
TGs, and there is no CP-CP session path available to NN1 so that NN3 can report
that the TG from NN3 to NN2 is inactive.

Operands
APPNCOS=cos_name
specifies the class of service to be used to calculate the node weight or the TG
weight.
DEST=cp_name
specifies the destination node (a control point) for a transmission group (TG).
ID specifies the name of the resource to display.
ID=cp_name
specifies the name of a control point to display.
ID=name
specifies the name of a resource to display when used with the following
operands:
v LIST=BN
v LIST=CDSERVR
v LIST=EN
v LIST=ICN
v LIST=NN
v LIST=VN.

Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand. For more information about using wildcards, see
“Using Wildcard Names” on page 14.
ID=*
specifies that all resources are to be displayed.
LIST
specifies the type of information to be displayed.
LIST=ADJ
displays information about nodes that are adjacent to the node specified on
the ID operand. (For the purpose of this command, a node is considered to
be adjacent if it is attached by an active transmission group.)
LIST=ALL
displays detailed information about the node specified on the ID operand. If
you omit LIST=ALL, VTAM displays brief information about the node.
LIST=BN
displays information about the border nodes specified on the ID operand. If
you omit the ID operand, information about all border nodes is displayed.

Chapter 2. VTAM Operator Commands 215

DISPLAY TOPO
LIST=CDSERVR
displays information about the central directory servers specified on the ID
operand. If you omit the ID operand, information about all central directory
servers is displayed.
LIST=EN
displays information about the end nodes specified on the ID operand,
including migration data hosts (MDH). If you omit the ID operand,
information about all end nodes is displayed.
LIST=ICN
displays information about the interchange nodes specified on the ID
operand. If you omit the ID operand, information about all interchange
nodes is displayed.
LIST=NN
displays information about the network nodes specified on the ID operand,
including interchange nodes (ICN). If you omit the ID operand, information
about all network nodes is displayed.
LIST=VN
displays information about the virtual nodes specified on the ID operand. If
you omit the ID operand, information about all virtual nodes is displayed.
LIST=SUMMARY
displays a summary, including how many nodes of each type are in the
database. LIST=SUMMARY is the default.
ORIG=cp_name
specifies the origin node (a control point) for a transmission group (TG).
TGN=tg_number
specifies the transmission group number of the route to be displayed. The
number must be an integer 1–255.

Resulting Display
The resulting display depends on the kind of information that was requested.
v For a summary of the topology, VTAM displays:
– The time and date of the last database checkpoint
– The number of adjacent nodes
– The number of network nodes
– The number of end nodes with a direct APPN connection to this node
– The number of end nodes served
– The number of central directory servers
– The number of interchange nodes
– The number of border nodes.
v For brief information for a specific node, VTAM displays:
– The network-qualified name of the control point
– The node type
– The route addition resistance value
– Whether the node is congested
– The current weight of the node, if the class of service was specified.
v For detailed information for a specific node, VTAM displays the short form plus
the following:

216 SNA Operation

 DISPLAY TOPO
– An indication of whether the node is a border node
– An indication of whether the node is a central directory server
– An indication of whether the node is an interchange node
– The resource sequence number
– The number of days remaining until the node entry is removed from the
topology database
– All TGs owned by the node
– An indication of the level of HPR support provided by the node.
v For a display of adjacent nodes, VTAM displays the short form of node
information for all nodes known to be adjacent to the node specified on the ID
operand. If ID specifies the name of (a) the node from which you are issuing this
command, or (b) a node immediately adjacent to the node from which you are
issuing this command, the display indicates whether a CP-CP session exists
between this node and the adjacent nodes. The existence of a CP-CP session is
not displayed if there is one or more nodes between the node from which the
command is issued and the node that is named on the ID operand.
If ID specifies the name of the node from which you are issuing this command, it
is possible for the display to indicate TDU congestion, which means that a large
number of topology update transactions are in progress on the CP-CP session
with an adjacent node. This is a transient condition; the congestion should clear
in a short time.
v For a display of one or more TGs, VTAM displays:
– The network-qualified name of the origin control point.
– The network-qualified name of the destination control point.
– The TG number.
– The TG status.
– The TG type.
– An indication of CP-CP session support.
– The current weight of the TG, if a class of service was specified on the
command. If the origin or destination of the TG is a virtual node, the weight of
the TG is divided by two. This smaller weight value is shown in the display.
– The resource sequence number.
– The number of days remaining until the TG is removed from the topology
database
– An indication of whether the TG is HPR-capable
– The capacity (line speed) of the TG. The value displayed for capacity might
not exactly match the value you coded for the resource. See the OS/390
eNetwork Communications Server: SNA Resource Definition Reference for
information about how VTAM maps the defined value to the value it actually
uses.
– The propagation delay.
– The cost per unit time.
– The cost per byte.
– The security level of the TG.
– Three user-defined parameters (default is zero).
v For a display of a particular type of node, VTAM displays the short form of node
information for each node in the topology database that matches the pattern
specified on the ID operand and the type specified on the LIST operand (BN,
CDSERVR, EN, ICN, NN, or VN).

Chapter 2. VTAM Operator Commands 217

DISPLAY TOPO
Examples
Displaying a summary of the topology database:
d net,topo,list=summary
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1306I LAST CHECKPOINT ADJ NN EN SERVED EN CDSERVR ICN BN
IST1307I NONE 2 3 0 0 0 2 2
IST314I END

Displaying brief information for a specific node:

d net,topo,id=a01n
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.A01N NN 1 NONE YES *NA*
IST314I END

Displaying brief information for a specific node, including its weight:

d net,topo,id=a01n,appncos=#connect
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.A01N NN 1 NONE YES 115
IST314I END

Displaying detailed information for a specific node:

d net,topo,id=sscp2a,list=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.SSCP2A NN 1 NONE YES *NA*
IST1579I ------------------------------------------
IST1297I ICN/MDH CDSERVR RSN HPR
IST1298I NO NO 8 RTP
IST1579I ------------------------------------------
IST1223I BN NATIVE TIME LEFT
IST1224I NO YES 12
IST1299I TRANSMISSION GROUPS ORIGINATING AT CP NETA.SSCP2A
IST1357I CPCP
IST1300I DESTINATION CP TGN STATUS TGTYPE VALUE WEIGHT
IST1301I NETA.SSCP1A 255 OPER INTERM VRTG YES *NA*
IST314I END

Displaying nodes that are adjacent to the specified node:

d net,topo,id=a01n,list=adj,appncos=#connect
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.A02N NN 1 NONE YES 65
IST1296I NETA.A500N NN 1 NONE YES 145
IST314I END

Displaying border nodes:

d net,topo,list=bn
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.SSCP1A NN 1 NONE YES *NA*
IST1296I NETB.SSCP7B NN 128 NONE NO *NA*
IST314I END

218 SNA Operation

 DISPLAY TOPO
Displaying central directory servers:
d net,topo,list=cdservr,appncos=#connect
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.A500N NN 1 NONE YES 5
IST314I END

Displaying end nodes whose names begin with “CM2” and end with “A”:
d net,topo,list=en,id=cm2*a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.CM2AA EN *NA* *NA* YES *NA*
IST1296I NETA.CM2BA EN *NA* *NA* YES *NA*
IST1296I NETA.CM2CDA EN *NA* *NA* NO *NA*
IST314I END

Displaying interchange nodes:

d net,topo,list=icn
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.A500N NN 1 NONE YES *NA*
IST1296I NETA.A02N NN 1 NONE *NA* *NA*
IST1296I NETA.A01N NN 1 NONE NO *NA*
IST314I END

Displaying network nodes:

d net,topo,list=nn
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.SSCP1A NN 1 NONE *NA* *NA*
IST1296I NETA.SSCP2A NN 1 NONE YES *NA*
IST1296I NETA.SSCP7B NN 128 NONE NO *NA*
IST314I END

Displaying virtual nodes:

d net,topo,list=vn
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.VN1 VN 128 NONE *NA* *NA*
IST314I END

Displaying transmission group information:

d net,topo,orig=sscp1a,dest=sscp2a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1299I TRANSMISSION GROUPS ORIGINATING AT CP NETA.SSCP1A
IST1357I CPCP
IST1300I DESTINATION CP TGN STATUS TGTYPE VALUE WEIGHT
IST1301I NETA.SSCP2A 21 OPER INTERM YES *NA*
IST1579I ------------------------------------------
IST1163I RSN HPR TIME LEFT
IST1164I 26 YES 12
IST1579I ------------------------------------------
IST1302I CAPACITY PDELAY COSTTIME COSTBYTE
IST1303I 32M TERRESTR 0 0

Chapter 2. VTAM Operator Commands 219

DISPLAY TOPO
IST1579I ------------------------------------------
IST1304I SECURITY UPARM1 UPARM2 UPARM3
IST1305I UNSECURE 128 128 128
IST314I END

Displaying transmission group information for a specific class of service:

d net,topo,orig=sscpca,dest=sscpba,tgn=21,appncos=#connect
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1299I TRANSMISSION GROUPS ORIGINATING AT CP NETA.SSCPCA
IST1357I CPCP
IST1300I DESTINATION CP TGN STATUS TGTYPE VALUE WEIGHT
IST1301I NETA.SSCPBA 21 OPER INTERM YES 210
IST1579I ------------------------------------------
IST1163I RSN HPR TIME LEFT
IST1164I 26 YES 12
IST1579I ------------------------------------------
IST1302I CAPACITY PDELAY COSTTIME COSTBYTE
IST1303I 8K TERRESTR 0 0
IST1579I ------------------------------------------
IST1304I SECURITY UPARM1 UPARM2 UPARM3
IST1305I UNSECURE 0 0 0
IST314I END

Displaying information about virtual-route-based transmission groups:

d net,topo,orig=sscp2a,dest=sscp1a,tgn=255
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1299I TRANSMISSION GROUPS ORIGINATING AT CP NETA.SSCP2A
IST1357I CPCP
IST1300I DESTINATION CP TGN STATUS TGTYPE VALUE WEIGHT
IST1301I NETA.SSCP1A 255 OPER INTERM VRTG YES *NA*
IST1579I ------------------------------------------
IST1163I RSN HPR TIME LEFT
IST1164I 26 YES 12
IST1579I ------------------------------------------
IST1302I CAPACITY PDELAY COSTTIME COSTBYTE
IST1303I 8K TERRESTR 0 0
IST1579I ------------------------------------------
IST1304I SECURITY UPARM1 UPARM2 UPARM3
IST1305I UNSECURE 128 128 128
IST314I END

220 SNA Operation

 DISPLAY TRACES

DISPLAY TRACES Command

Display the status of BUF, GPT, IO, LINE, SIT, STATE, and TG traces:

ÊÊ DISPLAY NET,TRACES ,TYPE=NODES Ê

Ê ,ID= * ÊÍ
(*)
(1) ,IDTYPE=RESOURCE
name
, ,IDTYPE= CP
SSCP
( » name ) RESOURCE

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Display the status of communication network management traces:

ÊÊ DISPLAY NET,TRACES ,TYPE=CNM ÊÍ

Display the status of the user Exit buffer trace:

ÊÊ DISPLAY NET,TRACES ,TYPE=EXIT ,ID= ISTEXCAA ÊÍ

ISTEXCCS
ISTEXCDM

Display the status of a module trace:

ÊÊ DISPLAY NET,TRACES ,TYPE=MODULE ÊÍ

Display the status of a network controller line trace:

ÊÊ DISPLAY NET,TRACES ,TYPE=NETCTLR ,ID=3710_pu_name ÊÍ

Display the status of an SMS (buffer use) trace:

,ID=VTAMBUF
ÊÊ DISPLAY NET,TRACES ,TYPE=SMS ÊÍ

Display the status of a resource state trace:

ÊÊ DISPLAY NET,TRACES ,TYPE=STATE ÊÍ

Display the status of a TSO user trace:

Chapter 2. VTAM Operator Commands 221

DISPLAY TRACES
ÊÊ DISPLAY NET,TRACES ,TYPE=TSO ,ID= * ÊÍ
(*)
(1)
user_id
,

( » user_id )

Notes:
1. Depending on the value of the DSPLYWLD start option, wildcard values can be
used for this operand.

Display the status of the VTAM internal trace:

,TYPE=VTAM
ÊÊ DISPLAY NET,TRACES ÊÍ

Display the status of all active traces:

ÊÊ DISPLAY NET,TRACES ,TYPE=ALL ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
TRACES TRACE
TYPE=NODES TYPE=NODE

Purpose
The DISPLAY TRACES command displays the status of a trace.

Operands
ID specifies a value that varies depending on the type of trace.
v For TYPE=NODES, ID specifies the name of one or more resources whose
trace status is to be displayed. The ID operand is required with
TYPE=NODES. You can specify major or minor node names. Resource
names can be network-qualified.
Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand. However, if you specify a wildcard, trace status
information is displayed only for resources that match the wildcard value, and
not for subordinate resources. For more information about using wildcards,
see “Using Wildcard Names” on page 14.
Attention: Specifying a wildcard name might degrade performance because
VTAM checks every major or minor node in the network.

Note: If model application program definition names match the pattern you
specify on the ID operand of the DISPLAY TRACES command when
TYPE specifies NODES, those model application program names will

222 SNA Operation

 DISPLAY TRACES
appear in your display output. In addition, any dynamic application
programs built from those model application program definitions will
also appear in your display output.

A model application program will be identified in message IST1041I as

MODEL APPL. A dynamic application program will be identified in
message IST1041I as DYNAMIC APPL.

For example, if you issue the following command:

DISPLAY NET,TRACES,ID=APPL*,TYPE=NODES

and model application programs have been defined using names that
match the pattern specified on the ID operand (APPL*), you will get
the following output:
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES
IST075I NAME = APPL1A, TYPE = APPL SEGMENT
IST1041I NETA.APPL1 APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST1041I NETA.APPL1V APPL
IST1042I IO = ON - AMOUNT = **NA** - SAVED = NO
IST924I --------------------------------------------------------
IST075I NAME = TESTAPPL, TYPE = APPL SEGMENT
IST1041I NETA.APPL1* MODEL APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST1041I NETA.APPL1Q DYNAMIC APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST314I END

The wildcard character used in APPL* on the ID operand of the

DISPLAY TRACES command tells VTAM to display the trace status of
any resource whose name begins with APPL, followed by zero to four
valid characters in length. The name field of the network-qualified
name NETA.APPL1*, even though it contains a wildcard character,
begins with APPL, followed by zero to four valid characters in length (*
and ? are valid characters in an application program minor node
name). Therefore, it is included in the display output, as is the
dynamic application program (NETA.APPL1Q) built from APPL1*.

See the “MODIFY TRACE Command” on page 361 for information about
which trace types are applicable to various VTAM resource types.
v For TYPE=CNM, the ID operand is not valid.
v For TYPE=EXIT, ID=ISTEXCAA, ISTEXCCS and ISTEXCDM are the only
valid values for the ID operand. ID = must be specified.
v For TYPE=MODULE, the ID operand is not valid.
v For TYPE=NETCTLR, ID specifies the name of the 3710 physical unit that is
to perform the trace. The ID operand is required and wildcard names are not
valid for TYPE=NETCTLR.
v For TYPE=SMS, ID=VTAMBUF is the only valid value for the ID operand.
ID=VTAMBUF can be specified or assumed by default.
v For TYPE=STATE, the ID operand is not valid.
v For TYPE=TSO, ID specifies the user IDs for which trace status is to be
displayed. The ID operand is required with TYPE=TSO. User IDs that do not
have an active TSO trace are not displayed. Network-qualified names are not
allowed with TYPE=TSO.

Chapter 2. VTAM Operator Commands 223

DISPLAY TRACES
Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand. For more information about using wildcards, see
“Using Wildcard Names” on page 14.
Attention: Specifying a wildcard name might degrade performance because
VTAM checks every TSO user ID in the network.
v For TYPE=VTAM, the ID operand is not valid.
v For TYPE=ALL, the ID operand is not valid.
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE identifies which resource the
command should act on. The IDTYPE operand is valid only when
TYPE=NODES is specified and the ID operand specifies a value other than an
asterisk (*).
IDTYPE=CP
displays information for the CP with the name specified on the ID operand.
The control point that is displayed can be the host CP or a CDRSC
representing an adjacent CP.
IDTYPE=RESOURCE
displays information for a CP, an SSCP, or another resource with the name
specified on the ID operand. If both an SSCP and a CP are found, VTAM
displays information for both of them.
IDTYPE=SSCP
displays information for the SSCP with the name specified on the ID
operand.
TYPE
If TYPE is not specified, TYPE=VTAM is used by default.
TYPE=CNM
displays information about communication network management (CNM)
traces.
TYPE=EXIT
displays information about the session management exit (SME) buffer trace.
TYPE=MODULE
displays information about a module trace.
TYPE=NODES
displays information about BUF, GPT, IO, LINE, SIT, STATE, and TG traces
for the resources named on the ID operand.
BUF Buffer contents trace
GPT Generalized PIU trace
IO Input/output trace
LINE NCP line trace
SIT Scanner interface trace
STATE
Resource state trace
TG Transmission group trace
TYPE=NETCTLR
displays information about a 3710 Network Controller line trace.

224 SNA Operation

 DISPLAY TRACES
TYPE=SMS
displays information about the storage management services (SMS) buffer
use trace.
TYPE=STATE
displays information about the resource types being traced.
TYPE=TSO
displays trace information for the TSO user IDs specified on the ID operand.
This function is similar to that provided by the “DISPLAY TSOUSER
Command” on page 232.
TYPE=VTAM
displays information about the VTAM internal trace (VIT).
TYPE=ALL
displays information for the following types of traces, if they are active:
v TYPE=CNM
v TYPE=EXIT
v TYPE=MODULE
v TYPE=NODES,ID=*
v TYPE=SMS
v TYPE=STATE
v TYPE=TSO,ID=*
v TYPE=VTAM.

No information is displayed for the CNM, TSO, EXIT, MODULE, SMS,

STATE, and VTAM traces if they are not active.

Resulting Display
The resulting display shows information specific to the trace type and ID specified.
v For TYPE=CNM, the resulting display shows the status for session awareness
and problem determination PIU buffer traces (on or off).
v For TYPE=EXIT, the resulting display shows the functions of the session
management exit (SME) for which tracing is active.
v For TYPE=MODULE, the resulting display shows the types of modules for which
tracing is active.
v For TYPE=NODES, the resulting display shows:
– For ID=major node name, the resources subordinate to the named resource
that have an active BUF, GPT, IO, LINE, SIT, STATE, or TG trace.
– For ID=minor node name, the status of BUF, GPT, IO, LINE, SIT, STATE, or
TG tracing for this resource.
– For ID=*, all resources that have an active BUF, GPT, IO, LINE, SIT, STATE,
or TG trace, along with the name of the resource’s major node.
– For ID=wildcard name, the status of BUF, GPT, IO, LINE, SIT, STATE, or TG
tracing for the resources that match the wildcard value.

Note: For ID=name in any form, the display also shows whether BUF, IO, and
STATE trace requests are saved, with saved trace requests for unknown
resources.

Chapter 2. VTAM Operator Commands 225

DISPLAY TRACES
v For TYPE=NETCTLR, the resulting display shows the name of the 3710
performing the trace, and the PU name and line name of each resource being
traced.
v For TYPE=SMS, the resulting display shows the trace status (on or off).
v For TYPE=STATE, the resulting display shows the resource types for which
resource state tracing is active.
v For TYPE=TSO, the resulting display shows:
– For ID=name, the trace status for the named user ID (on or off).
– For ID=*, all user IDs that have an active trace.
v For TYPE=VTAM, the resulting display shows the mode (internal or both internal
and external), the trace table size (applicable only to MODE=INT), and the
user-specified trace options that are currently in effect. The default trace options
are active, but are not displayed unless you explicitly specified them on the
TRACE,TYPE=VTAM start option or the MODIFY TRACE command.
v For TYPE=ALL, the resulting display shows all of the information for the following
traces, if they are active:
– TYPE=CNM
– TYPE=EXIT
– TYPE=MODULE
– TYPE=NODES,ID=*
– TYPE=TSO,ID=*
– TYPE=SMS
– TYPE=STATE
– TYPE=VTAM.

Examples
Displaying the status of communication network management (CNM) traces:
d net,traces,type=cnm
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=CNM
IST655I PDPIUBUF TRACE STATUS = ON
IST655I SAWBUF TRACE STATUS = ON
IST314I END

Displaying the status of the session management exit (SME) buffer trace:
d net,traces,type=exit,id=istexcaa
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTEXCAA, TYPE = EXIT
IST199I OPTIONS = BEGIN INITAUTH VRSEL END
IST314I END

Displaying the status of the module trace:

d net,traces,type=module
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=MODULE
IST199I OPTIONS = COMMAND CONNECTION INTERFACES SESSION
IST314I END

Displaying node traces for a few resources with saved trace requests:
d net,traces,type=nodes,id=(appl1,appl2,netappl1,noapp1)
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES
IST075I NAME = APPL1A, TYPE = APPL SEGMENT

226 SNA Operation

 DISPLAY TRACES
IST1041I NETA.APPL1 APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = YES
IST1042I STATE = ON - AMOUNT = **NA** - SAVED = YES
IST1041I NETA.APPL2 APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST1042I STATE = ON - AMOUNT = **NA** - SAVED = NO
IST924I -------------------------------------------------------------
IST075I NAME = CDRSC1A, TYPE = CDRSC SEGMENT
IST1041I NETA.NETAPPL1 CDRSC
IST1042I IO = ON - AMOUNT = **NA** - SAVED = YES
IST1042I STATE = ON - AMOUNT = **NA** - SAVED = YES
IST924I -------------------------------------------------------------
IST1422I SAVED TRACE REQUESTS FOR NETA.NOAPP1
IST1041I NETA.NOAPP1 N/A
IST1042I BUF = SAVED - AMOUNT = PARTIAL
IST1042I STATE = SAVED - AMOUNT = **NA**
IST314I END

Displaying node traces for all resources:

d net,traces,type=nodes,id=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES 506
IST075I NAME = A50CDRMC, TYPE = CDRM SEGMENT
IST1041I C01N CDRM
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST924I -------------------------------------------------------------
IST075I NAME = A0362ZC, TYPE = PU T4/5
IST1041I A03S16 LINE
IST1042I LINE = TRACT
IST314I END

Displaying node traces for a control point:

d net,traces,type=nodes,id=a500n,idtype=cp
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES
IST075I NAME = NETA.A500N, TYPE = APPL
IST1041I NETA.A500N APPL
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST314I END

Displaying node traces for an SSCP:

d net,traces,type=nodes,id=a500n,idtype=sscp
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES
IST075I NAME = A500N, TYPE = CDRM
IST1041I A500N CDRM
IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
IST314I END

Displaying the status of the SMS trace:

d net,traces,type=sms
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=SMS
IST655I SMS TRACE STATUS = OFF
IST314I END

Displaying the status of the resource state trace:

d net,traces,type=state
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=STATE
IST199I OPTIONS = ADJCP APPL CDRM CDRSC GROUP LINE LU NCP PU
IST314I END

Chapter 2. VTAM Operator Commands 227

DISPLAY TRACES
Displaying a TSO user trace:
d net,traces,type=tso,id=user1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=TSO
IST1200I USER1 TSO USERID TRACE = OFF
IST314I END

Displaying the status of the VTAM internal trace:

d net,traces,type=vtam
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=VTAM
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = INT, SIZE = 050
IST199I OPTIONS = API APPC CFS CIO CMIP CSM ESC HPR LCS LOCK MSG NRM
IST199I OPTIONS = PIU PSS SMS SSCP TCP VCNS XBUF XCF
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = EXT, SIZE = 002
IST199I OPTIONS = API APPC CFS CIO CMIP CSM ESC HPR LCS LOCK MSG NRM
IST199I OPTIONS = PIU PSS SMS SSCP TCP VCNS XBUF XCF
IST314I END

Displaying all active traces:

d net,traces,type=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRACES,TYPE=NODES 549
IST075I NAME = A50CDRMC, TYPE = CDRM SEGMENT
IST1041I C01N CDRM
IST1042I BUF = ON - AMOUNT = PARTIAL
IST924I -------------------------------------------------------------
IST075I NAME = A0362ZC, TYPE = PU T4/5
IST1041I A03S16 LINE
IST1042I LINE = TRACT
IST924I -------------------------------------------------------------
IST075I NAME = ISTEXCAA, TYPE = EXIT
IST199I OPTIONS = BEGIN INITAUTH VRSEL END
IST924I -------------------------------------------------------------
IST350I DISPLAY TYPE = TRACES,TYPE=VTAM
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = INT, SIZE = 050
IST199I OPTIONS = API APPC CFS CIO CMIP CSM ESC HPR LCS LOCK MSG NRM
IST199I OPTIONS = PIU PSS SMS SSCP TCP VCNS XBUF XCF
IST315I VTAM INTERNAL TRACE ACTIVE - MODE = EXT, SIZE = 002
IST199I OPTIONS = API APPC CFS CIO CMIP CSM ESC HPR LCS LOCK MSG NRM
IST199I OPTIONS = PIU PSS SMS SSCP TCP VCNS XBUF XCF
IST924I -------------------------------------------------------------
IST350I DISPLAY TYPE = TRACES,TYPE=STATE
IST199I OPTIONS = ADJCP APPL CDRM CDRSC GROUP LINE LU NCP PU
IST924I -------------------------------------------------------------
IST350I DISPLAY TYPE = TRACES,TYPE=MODULE
IST199I OPTIONS = COMMAND CONNECTION INTERFACES SESSION
IST314I END

228 SNA Operation

 DISPLAY TRL

DISPLAY TRL Command

Display the entries in the TRL major node:

,CONTROL=ALL
ÊÊ DISPLAY NET,TRL Ê
,CONTROL= ALL
MPC
TCP
,ULPID=name
XCF

,MAX=DSPLYDEF_start_option_value
Ê ÊÍ
,MAX= *
number_of_resources

Display information about a specific user-defined TRLE:

ÊÊ DISPLAY NET,TRL ,TRLE=trl_entry_name ÊÍ

Display information about a dynamic XCF TRLE:

ÊÊ DISPLAY NET,TRL ,XCFCP=cp_name ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY TRL (transport resource list) command provides information about the
TRL major node or about a single TRLE (transport resource list entry). TRLEs
define the connectivity characteristics of PUs that provide APPN host-to-host
channel connection.

Operands
CONTROL
specifies the type of connections to display.
CONTROL=ALL
specifies that information is to be displayed about all TRLEs.
CONTROL=MPC
specifies that information is to be displayed about user-defined TRLEs only.
CONTROL=TCP
specifies that information is to be displayed about dynamic TCP/IP TRLEs
only.

Chapter 2. VTAM Operator Commands 229

DISPLAY TRL
CONTROL=XCF
specifies that information is to be displayed about dynamic XCF TRLEs
only.
MAX
specifies the maximum number of TRLEs that VTAM displays for this command.

If you specify the MAX operand, do not specify TRLE.

MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of TRLEs to display for this command. The valid range
is 1–value of DSPLYMAX. The default is the value specified for the
DSPLYDEF start option.

Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer TRLEs are found than you have
specified on MAX, VTAM displays only the TRLEs that are found.
TRLE=trl_entry_name
specifies the name of the user-defined TRLE to be displayed.
ULPID=name
specifies the name of a CS OS/390 upper-layer protocol (ULP) to be displayed,
for example, the TCP/IP procedure name. The ULPID operand is only valid with
CONTROL=TCP.
XCFCP=cp_name
specifies that information is to be displayed about the TRLE representing the
connection to another VTAM in the XCF group. cp_name is the CP name of the
other VTAM.

Resulting Display
The resulting display shows:
v The name and status of all TRLEs in the TRL major node if the TRLE operand is
not specified
v The name and status of the TRLE specified on the TRLE operand. If the status is
active, the display also includes the address and operational status of WRITE
and READ subchannels and the name of the physical resource associated with
this TRLE.
v The capability of the connection to perform channel I/O directly to or from
communications storage manager (CSM) buffers.

Examples
Displaying all TRL entries:
d net,trl
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRL
IST1314I TRLE = ML1A2A1 STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = ML1A2A2 STATUS = NEVAC CONTROL = MPC

230 SNA Operation

 DISPLAY TRL
IST1314I TRLE = ML1A2A3 STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = ML1A2A4 STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = ISTT0001 STATUS = ACTIV----E CONTROL = XCF
IST1454I 5 TRLE(S) DISPLAYED
IST314I END

Displaying an active TRL entry:

d net,trl,trle=tod02
IST097I DISPLAY ACCEPTED
IST075I NAME = TOD02, TYPE = TRLE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES
IST1577I HEADER SIZE = 4092 DATA SIZE = 20 STORAGE = ***NA***
IST1221I WRITE DEV = 0BE0 STATUS = ACTIVE STATE = ONLINE
IST1221I WRITE DEV = 0BE1 STATUS = ACTIVE STATE = ONLINE
IST1577I HEADER SIZE = 4092 DATA SIZE = 20 STORAGE = ECSA
IST1221I READ DEV = 0BC0 STATUS = ACTIVE STATE = ONLINE
IST1221I READ DEV = 0BC1 STATUS = ACTIVE STATE = ONLINE
IST314I END

Displaying an active XCF TRL entry:

d net,trl,trle=istt0001
IST097I DISPLAY ACCEPTED
IST075I NAME = ISTT0001, TYPE = TRLE 381
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = XCF , HPDT = *NA*
IST1503I XCF TOKEN = 02000080000F0002 STATUS = ACTIVE
IST1502I ADJACENT CP = NETA.SSCP2A
IST314I END

Displaying an inactive TRL entry:

d net,trl,trle=ml1a2a1
IST097I DISPLAY ACCEPTED
IST075I NAME = ML1A2A1, TYPE = TRLE
IST486I STATUS= NEVAC, DESIRED STATE= INACT
IST087I TYPE = LEASED , CONTROL = MPC , HPDT = *NA*
IST314I END

Chapter 2. VTAM Operator Commands 231

DISPLAY TSOUSER

DISPLAY TSOUSER Command

ÊÊ DISPLAY NET,TSOUSER ,ID=user_id ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D
TSOUSER U

Purpose
The DISPLAY TSOUSER (TSO user) command displays the status of a TSO user
ID.

Operands
ID=user_id
specifies the TSO user ID about which information is to be displayed. Data for
all address spaces started by a TSO user is shown if ID is specified.

Resulting Display
The resulting display shows:
v The name and status of the TSO user ID
v An indication of whether the TSO trace is active for this user ID
v The application program name associated with the TSO user space
v The device-type logical unit the TSO user is using.

Examples
Displaying a TSO user ID:
d net,tsouser,id=user1
IST097I DISPLAY ACCEPTED
IST075I NAME = USER1, TYPE = TSO USERID
IST486I STATUS= ACTIV, DESIRED STATE= N/A
IST576I TSO TRACE = OFF
IST1212I ACBNAME = TSO0001 STATUS = ACT/S
IST1212I LUNAME = NETA.A50A722 STATUS = ACT/S
IST314I END

232 SNA Operation

 DISPLAY USERVAR

DISPLAY USERVAR Command

Display all USERVARs:

,MAX=DSPLYDEF_start_option_value
ÊÊ DISPLAY NET,USERVAR ÊÍ
,MAX= *
number_of_resources

Display a specific USERVAR:

ÊÊ DISPLAY NET,USERVAR ,ID=uservar_name ÊÍ

Abbreviations
Operand Abbreviation
DISPLAY D

Purpose
The DISPLAY USERVAR command displays the VTAM application names
associated with a specified USERVAR, or all known USERVARs and the application
names associated with them.

Network-qualified USERVAR values can be displayed in the output of the DISPLAY

USERVAR command. If the VALUE operand on the MODIFY USERVAR command
is a network-qualified name, or if the class of USERVAR is automatic
(VTAM-managed), the output from the DISPLAY USERVAR command for that
USERVAR has the network-qualified name in it. If the VALUE operand on the
MODIFY USERVAR command is a non-network-qualified name, the output from the
DISPLAY USERVAR command for that USERVAR does not have the
network-qualified name in it.

Operands
ID=uservar_name
specifies the name of a USERVAR.

If you specify the ID operand, do not specify MAX.

MAX
specifies the maximum number of application names that VTAM displays for this
command.

If you specify the MAX operand, do not specify ID.

MAX=*
specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_resources
specifies the number of application names to display for this command. The
valid range is 1–value of DSPLYMAX. The default is the value specified for
the DSPLYDEF start option.

Chapter 2. VTAM Operator Commands 233

DISPLAY USERVAR
Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
VTAM does not search any further. This saves processing time for the
command and gives you control over the amount of display output
generated by the command. If fewer application names are found than you
have specified on MAX, VTAM displays only the application names that are
found.

Resulting Display
The resulting display shows:
v The named USERVAR and its corresponding VTAM application program name. If
you omit ID=uservar_name, VTAM displays all known USERVARs and the
application program names associated with them.
v The USERVAR class (automatic or user-managed) and the type of USERVAR
(static, dynamic, or volatile).
v Whether an installation-wide exit (UVEXIT) routine is used for the USERVAR.

Examples
Displaying all USERVARs:
d net,uservar
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = USERVAR
IST1019I USERVAR VALUE CLASS TYPE EXIT APPC
IST1029I APPL2 NETB.APPLB22 USER DYNAMIC NO NO
IST1029I APPL1 NETB.APPLB11 USER DYNAMIC NO NO
IST314I END

Displaying a specific USERVAR:

d net,uservar,id=echo01a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = USERVAR
IST1019I USERVAR VALUE CLASS TYPE EXIT APPC
IST1029I ECHO01A ECHO01A USER DYNAMIC NO NO
IST314I END

234 SNA Operation

 DISPLAY VTAMOPTS

DISPLAY VTAMOPTS Command

Display selected start options:

,FORMAT=CURRENT
ÊÊ DISPLAY NET,VTAMOPTS Ê
,FORMAT= CURRENT
COMPLETE
MODIFIED

,OPTION=*
Ê ÊÍ
,OPTION= *
(*)
option
,

( » option )

Display a group of related start options:

,FORMAT=CURRENT
ÊÊ DISPLAY NET,VTAMOPTS ,FUNCTION= APPNCHAR ÊÍ
,FORMAT= CURRENT CONNECT
COMPLETE MESSAGES
MODIFIED PERFTUNE
RECSTATS
SECURITY
SESSCONT
SSCPCP
STORAGE
TRACDUMP
VTAMINIT
ZAPCON

Abbreviations
Operand Abbreviation
DISPLAY D
FORMAT=COMPLETE COMP
FORMAT=CURRENT CUR
FORMAT=MODIFIED MOD
OPTION OPT

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
FORMAT=CURRENT, code only CUR. Do not code FORMAT=CUR.

Purpose
The DISPLAY VTAMOPTS (VTAM start options) command displays information
about VTAM start options. The VTAM version and release, the date and time when
VTAM was started, the component ID, and VTAM’s node type are also displayed.

Chapter 2. VTAM Operator Commands 235

 DISPLAY VTAMOPTS
Operands
FORMAT
specifies the type of information to be displayed.
FORMAT=CURRENT
displays the current value of one or more start options.
FORMAT=COMPLETE
displays detailed information about one or more start options. For each start
option, VTAM displays the current value, the value that VTAM initialized
with, and the source of the value that VTAM initialized with. The source can
be a value specified in an ATCSTRxx start option list, a value entered by
the operator during VTAM start, or a default value used in the absence of
any other specification.
FORMAT=MODIFIED
displays information about start options that have been modified since
VTAM initialization. If an option has not been modified, it is not displayed.

For each modified start option, VTAM displays the current value, the value
that VTAM initialized with, and the source of the value that VTAM initialized
with. The source can be a value specified in an ATCSTRxx start option list,
a value entered by the operator during VTAM start, or a default value used
in the absence of any other specification.
FUNCTION
specifies a group of related start options to display. If you specify FUNCTION,
do not specify OPTION on the same command.
FUNCTION=APPNCHAR
displays the start options that define APPN characteristics. The start options
displayed using FUNCTION=APPNCHAR are also displayed using other
specifications for FUNCTION. The start options displayed using
FUNCTION=APPNCHAR are:

APPNCOS BN BNDYN
BNORD CDSERVR CDSREFER
CONNTYPE CPCP DIRSIZE
DIRTIME DUPDEFS DYNADJCP
HPR HPRNCPBF HPRPST
| INITDB IOPURGE IPADDR
| MAXLOCAT NETID NNSPREF
NODETYPE NUMTREES PSRETRY
RESUSAGE ROUTERES SECLVLCP
SNVC SORDER SRCHRED
SRCOUNT SRTIMER SSCPNAME
| SSEARCH TCPNAME VERIFYCP
VFYRED VFYREDTI VRTG
VRTGCPCP XCFINIT

FUNCTION=CONNECT
displays the start options that affect connectivity. The start options displayed
using FUNCTION=CONNECT are:

236 SNA Operation

 DISPLAY VTAMOPTS
ALSREQ AUTHLEN CONNTYPE
CPCP DISCNTIM DYNHPPFX
DYNPUPFX DYNVNPFX HPR
| HPRNCPBF NNSPREF SNVC
SSDTMOUT VRTG VRTGCPCP
XCFINIT XNETALS

FUNCTION=MESSAGES
displays the start options that affect messages. The start options displayed
using FUNCTION=MESSAGES are:

ASIRFMSG CNMTAB DSPLYDEF

DSPLYMAX DSPLYWLD ESIRFMSG
FLDTAB FSIRFMSG IOMSGLIM
MSGLEVEL MSGMOD PLUALMSG
SIRFMSG SLUALMSG SUPP
FUNCTION=PERFTUNE
displays the start options that affect performance and tuning. The start
options displayed using FUNCTION=PERFTUNE are:

AUTOTI BSCTMOUT CACHETI

CDRSCTI CINDXSIZ DIRSIZE
DIRTIME HNTSIZE HPRPST
HSRTSIZE IOINT IOPURGE
MAXLOCAT MAXLURU MIHTMOUT
MXSAWBUF MXSSCPRU NCPBUFSZ
NUMTREES NSRTSIZE OSIEVENT
OSITOPO OSRTSIZE PDTRCBUF
PIUMAXDS PSRETRY SAWMAXDS
SAWMXQPK SONLIM SRCHRED
SRCOUNT SRTIMER UPDDELAY
VFYRED VFYREDTI VTAMEAS
FUNCTION=RECSTATS
displays the start options that affect recording and statistics. The start
options displayed using FUNCTION=RECSTATS are:

BSCMDRS NMVTLOG PPOLOG

SDLCMDRS TNSTAT

FUNCTION=SECURITY
displays the start options that affect session security. The start options
displayed using FUNCTION=SECURITY are:

ENCRPREF ENCRYPTN SECLVLCP

VERIFYCP

FUNCTION=SESSCONT
displays the start options that affect session control. The start options
displayed using FUNCTION=SESSCONT are:

Chapter 2. VTAM Operator Commands 237

 DISPLAY VTAMOPTS
APPNCOS ASYDE AUTORTRY
BNDYN BNORD CDRDYN
CMPMIPS CMPVTAM CPCDRSC
| DIALRTRY DLRORDER DUPDEFS
DYNADJCP DYNASSCP DYNDLGMD
DYNLU DYNMODTB HOTIOTRM
ISTCOSDF RESUSAGE ROUTERES
SMEAUTH SORDER SSCPDYN
SSCPORD SSEARCH SWNORDER
FUNCTION=SSCPCP
displays the start options that define SSCP or CP characteristics. The start
options displayed using FUNCTION=SSCPCP are:

BN CDSERVR DATEFORM
ENHADDR GWSSCP HOSTPU
HOSTSA LIMINTCP MAINTLVL
MAXSSCPS MAXSUBA MXSUBNUM
| NETID NNSPREF NODETYPE
NQNMODE SSCPID SSCPNAME
STRGR STRMNPS TRANSLAT
USSTAB

FUNCTION=STORAGE
displays the start options that define storage usage, except for the buffer
pool start options. The start options displayed using FUNCTION=STORAGE
are:

CSALIMIT CSA24 DLRTCB

IRNSTRGE

FUNCTION=TRACDUMP
displays the start options that affect traces and dumps. The start options
displayed using FUNCTION=TRACDUMP are:

INOPDUMP PSSTRACE SNAPREQ

FUNCTION=VTAMINIT
displays the start options that affect VTAM initialization. The start options
displayed using FUNCTION=VTAMINIT are:

COLD CONFIG INITDB

LIST NODELST OSIMGMT
WARM

FUNCTION=ZAPCON
displays the start options that once were zappable constants. The start
options displayed using FUNCTION=ZAPCON are also displayed using
other specifications for FUNCTION. The start options displayed using
FUNCTION=ZAPCON are:

238 SNA Operation

 DISPLAY VTAMOPTS
ASIRFMSG BSCTMOUT CINDXSIZ
ESIRFMSG FSIRFMSG HNTSIZE
HSRTSIZE INOPDUMP IOMSGLIM
IRNSTRGE MAXLURU MAXSSCPS
MIHTMOUT MXSAWBUF MXSSCPRU
MXSUBNUM NCPBUFSZ OSRTSIZE
PDTRCBUF PIUMAXDS PLUALMSG
PSSTRACE SAWMAXDS SAWMXQPK
SDLCMDRS SIRFMSG SLUALMSG
SNAPREQ SSDTMOUT TRANSLAT
VTAMEAS

OPTION=option
specifies one or more start options to display. If you specify OPTION, do not
specify FUNCTION on the same command. If OPTION=* is specified or
assumed by default, VTAM displays information about all start options except
PROMPT, NOPROMPT, LISTBKUP, and the trace and buffer pool start options.
The DISPLAY TRACES command and the DISPLAY BFRUSE command can be
used to display trace and buffer pool information. See the OS/390 eNetwork
Communications Server: SNA Resource Definition Reference for a description
of each start option.

For OPTION=LIST, VTAM displays the name of the start option list used during start
processing. The value can be a supplemental list, such as LIST=1A. However, if the
supplemental list contains errors and VTAM reverts to using defaults during start
processing because LISTBKUP=DEFAULTS is in effect, the user-defined default list
will be displayed. You can also issue a D NET,VTAMOPTS,FORMAT=COMPLETE
command to find out the origin of the start option values.

For OPTION=CNMTAB, VTAM displays *BLANKS* if a user defined table was not
loaded. You can issue a D NET,VTAMOPTS,FORMAT=COMPLETE command to
find out the origin of the start option value.

For OPTION=ENCRYPTN, the display might not exactly match the value specified
for the ENCRYPTN start option.

The following list shows the values that can be displayed for ENCRYPTN for each
value specified on the start option:
Start value
Display value
NO NO
YES, 24, or 31
24 or 31
CCA CCA_24 or CCA_31
CUSP CUSP_24 or CUSP_31

For OPTION=OSIMGMT, VTAM displays only the value of the OSIMGMT start
option. It does not indicate whether CMIP services is active.

For OPTION=STRGR or OPTION=STRMNPS, if no coupling facility is in use, this

command shows the value as ***NA***. See OS/390 MVS Setting Up a Sysplex for
more information about coupling facilities and CFRM.

Chapter 2. VTAM Operator Commands 239

 DISPLAY VTAMOPTS
See the OS/390 eNetwork Communications Server: SNA Network Implementation
Guide for more information about the sources of start options and which source
takes precedence.

Resulting Display
The resulting display shows:
v The VTAM version and release
v The time and date that VTAM was started
v The component ID
v The node type
v Information about the specified start options.

If a start option is not applicable to your configuration, it is displayed with ***NA***.

For example, ROUTERES is applicable only when VTAM is a network node. At an
end node, it would be displayed as ROUTERES=***NA***.

Examples
Displaying start options that have been modified:
D NET,VTAMOPTS,OPT=(DSPLYDEF,CMPVTAM,CPCP),FORMAT=MODIFIED
IST097I DISPLAY ACCEPTED
| IST1188I ACF/VTAM V4R5 STARTED AT 13:36:57 ON 04/20/98
| IST1349I COMPONENT ID IS 5695-11701-501
| IST1348I VTAM STARTED AS INTERCHANGE NODE
| IST1309I START OPTION CURRENT VALUE ORIGINAL VALUE ORIGIN
IST1310I CMPVTAM 2 0 DEFAULT
IST1310I CPCP NO YES ATCSTR1A
IST1310I DSPLYDEF 32767 65535 ATCSTR00
IST314I END

Displaying complete information about selected start options:

D NET,VTAMOPTS,OPT=(DYNLU,DSPLYDEF,CMPVTAM,SUPP,CPCP),FORMAT=COMPLETE
IST097I DISPLAY ACCEPTED
| IST1188I ACF/VTAM V4R5 STARTED AT 13:36:57 ON 04/20/98
| IST1349I COMPONENT ID IS 5695-11701-501
| IST1348I VTAM STARTED AS INTERCHANGE NODE
| IST1309I START OPTION CURRENT VALUE ORIGINAL VALUE ORIGIN
IST1310I CMPVTAM 2 0 DEFAULT
IST1310I CPCP NO YES ATCSTR1A
IST1310I DSPLYDEF 32767 65535 ATCSTR00
IST1310I DYNLU YES YES ATCSTR1A
IST1310I SUPP NOSUP NOSUP ATCSTR00
IST314I END

| Displaying all VTAM start options:

| D NET,VTAMOPTS
| IST097I DISPLAY ACCEPTED
| IST1188I ACF/VTAM V4R5 STARTED AT 13:36:57 ON 04/20/98
| IST1349I COMPONENT ID IS 5695-11701-501
| IST1348I VTAM STARTED AS INTERCHANGE NODE
| IST1189I ALSREQ = NO APPNCOS = NONE
| IST1189I ASIRFMSG = OLUSSCP ASYDE = TERM
| IST1189I AUTHLEN = YES AUTORTRY = AUTOCAP
| IST1189I AUTOTI = 0 BN = NO
| IST1189I BNDYN = ***NA*** BNORD = ***NA***
| IST1189I BSCMDRS = (STATS,INOPS) BSCTMOUT = 286
| IST1189I CACHETI = 8 CDRDYN = YES
| IST1189I CDRSCTI = 480S CDSERVR = NO

240 SNA Operation

 DISPLAY VTAMOPTS
| IST1189I CDSREFER = 1 CINDXSIZ = 8176
| IST1189I CMPMIPS = 100 CMPVTAM = 0
| IST1189I CNMTAB = *BLANKS* COLD = YES
| IST1189I CONFIG = 1A CONNTYPE = APPN
| IST1189I CPCDRSC = NO CPCP = YES
| IST1189I CSALIMIT = 1887436K CSA24 = NOLIMIT
| IST1189I DATEFORM = MDY DIALRTRY = YES
| IST1189I DIRSIZE = 0 DIRTIME = 691200S
| IST1189I DISCNTIM = (15,0) DLRORDER = STATNID
| IST1189I DLRTCB = 10 DSPLYDEF = 65535
| IST1189I DSPLYMAX = 65535 DSPLYWLD = FULLWILD
| IST1189I DUPDEFS = ALL DYNADJCP = YES
| IST1189I DYNASSCP = YES DYNDLGMD = NONE
| IST1189I DYNHPPFX = *BLANKS* DYNLU = YES
| IST1189I DYNMODTB = NONE DYNPUPFX = *BLANKS*
| IST1189I DYNVNPFX = *BLANKS* ENCRPREF = NONE
| IST1189I ENCRYPTN = 24 ENHADDR = YES
| IST1189I ESIRFMSG = ALLSSCP FLDTAB = ISTMSFLD
| IST1189I FSIRFMSG = OLUSSCP GWSSCP = YES
| IST1189I HNTSIZE = 4080 HOSTPU = ISTPUS
| IST1189I HOSTSA = 1 HOTIOTRM = 0
| IST1189I HPR = (RTP,RTP) HPRNCPBF = NO
| IST1189I HPRPST = LOW 480S HPRPST = MEDIUM 240S
| IST1189I HPRPST = HIGH 120S HPRPST = NETWRK 60S
| IST1189I HSRTSIZE = 9973 INITDB = ALL
| IST1189I INOPDUMP = OFF IOINT = 180
| IST1189I IOMSGLIM = 2147483647 IOPURGE = 0
| IST1189I IPADDR = 0.0.0.0 IRNSTRGE = 0
| IST1189I ISTCOSDF = INDLU LIMINTCP = ***NA***
| IST1189I LIST = 1A MAINTLVL = *BLANKS*
| IST1189I MAXLOCAT = 5000 MAXLURU = 6144
| IST1189I MAXSSCPS = 10 MAXSUBA = 255
| IST1189I MIHTMOUT = 1800 MSGLEVEL = BASE
| IST1189I MSGMOD = NO MXSAWBUF = 10000
| IST1189I MXSSCPRU = 4096 MXSUBNUM = 511
| IST1189I NCPBUFSZ = 512 NETID = NETA
| IST1189I NMVTLOG = NPDA NNSPREF = ***NA***
| IST1189I NODELST = *BLANKS* NODETYPE = NN
| IST1189I NQNMODE = NAME NSRTSIZE = *BLANKS*
| IST1189I NUMTREES = 100 OSIEVENT = PATTERNS
| IST1189I OSIMGMT = NO OSITOPO = ILUCDRSC
| IST1189I OSRTSIZE = 43 PDTRCBUF = 2
| IST1189I PIUMAXDS = 200 PLUALMSG = NOSUPP
| IST1189I PPOLOG = NO PSRETRY = LOW 0S
| IST1189I PSRETRY = MEDIUM 0S PSRETRY = HIGH 0S
| IST1189I PSRETRY = NETWRK 0S PSSTRACE = NORB
| IST1189I RESUSAGE = 100 ROUTERES = 1
| IST1189I SAWMAXDS = 100 SAWMXQPK = 0
| IST1189I SDLCMDRS = (STATS,INOPS) SECLVLCP = ***NA***
| IST1189I SIRFMSG = ALLSSCP SLUALMSG = NOSUPP
| IST1189I SMEAUTH = DISCARD SNAPREQ = 1000
| IST1189I SNVC = ***NA*** SONLIM = (60,30)
| IST1189I SORDER = APPN SRCHRED = OFF
| IST1189I SRCOUNT = 10 SRTIMER = 30S
| IST1189I SSCPDYN = YES SSCPID = 1
| IST1189I SSCPNAME = SSCP1A SSCPORD = PRIORITY
| IST1189I SSDTMOUT = 30 SSEARCH = YES
| IST1189I STRGR = ***NA*** STRMNPS = ***NA***
| IST1189I SUPP = NOSUP SWNORDER = CPNAME
| IST1189I TCPNAME = *BLANKS* TNSTAT = OFF
| IST1189I TRANSLAT = (0,1,2,3,4,5,6,7) UPDDELAY = 60S
| IST1189I USSTAB = *BLANKS* VERIFYCP = NONE
| IST1189I VFYRED = YES VFYREDTI = OFF
| IST1189I VRTG = NO VRTGCPCP = YES
| IST1189I VTAMEAS = 32001 WARM = NO
| IST1189I XCFINIT = ***NA*** XNETALS = NO
| IST314I END

Chapter 2. VTAM Operator Commands 241

DISPLAY VTAMOPTS

242 SNA Operation

 DISPLAY VTAMSTOR

DISPLAY VTAMSTOR Command

Display storage contents associated with a storage address:

ÊÊ DISPLAY NET,VTAMSTOR ,ADDRESS=storage_address Ê

,LENGTH=32
Ê ÊÍ
,LENGTH=decimal_number_of_bytes
,XLENGTH=hex_number_of_bytes

Display storage contents associated with a module:

ÊÊ DISPLAY NET,VTAMSTOR ,MODULE=module_name ÊÍ

Display storage contents associated with a network address:

ÊÊ DISPLAY NET,VTAMSTOR Ê

,X
Ê ,NETADDR=( element_address ) Ê
subarea_address , ,D
,X

Ê ÊÍ
,NETID=network_id

Display storage contents associated with a resource name:

,TYPE=RESOURCE
ÊÊ DISPLAY NET,VTAMSTOR ,RESOURCE=resource_name ÊÍ
,TYPE= CDRM
CP
LUALIAS
RESOURCE
SHADOW
SSCP
USERVAR
XCFCP

Abbreviations
Operand Abbreviation
ADDRESS ADDR
DISPLAY D
LENGTH LEN
MODULE MOD
RESOURCE RSC

Chapter 2. VTAM Operator Commands 243

DISPLAY VTAMSTOR
Operand Abbreviation
XLENGTH XLEN

Purpose
The DISPLAY VTAMSTOR command displays storage contents associated with
VTAM modules and resources.

Operands
ADDRESS
specifies the address (in hexadecimal). The storage address must be in the
range of 0–7FFFFFFF.
LENGTH
specifies the number of bytes in decimal to display. The valid range is 1–value
of DSPLYMAX multiplied by 16.
MODULE
specifies a module name (or CSECT name). The module name must be eight
characters in length and begin with the VTAM prefixes ACY, IST, IUT, or IVT.
NETADDR
specifies the network address of a resource.
subarea_address
specifies the subarea portion of the network address. Leading zeros are
acceptable but not required. If omitted, subarea_address defaults to the
subarea number of the host. Acceptable values are 1–FFFF in hexadecimal;
1–65535 in decimal.
element_address
specifies the element portion of the network address. Leading zeroes are
acceptable but not required. Acceptable values range from 0–7FFF in
hexadecimal; 0–32767 in decimal.
D indicates the subarea and element addresses are specified in decimal.
X indicates the subarea and element addresses are specified in hexadecimal.
NETID
specifies the network identifier. If omitted, the network identifier of the host is
used.
RESOURCE
specifies the network-qualified name of the resource for which the resource
definition table entry is to be displayed. If the network identifier is omitted, the
network of the host is used.
TYPE
specifies the type of resource that the RESOURCE operand identifies. This
operand is only valid when used with the RESOURCE operand. If several types
of resources share the same name, TYPE can be used to identify which
resource the command should act on.
TYPE=CDRM
displays the resource definition table entry for the SSCP (represented as a
CDRM).

244 SNA Operation

 DISPLAY VTAMSTOR
TYPE=CP
displays the resource definition table entry for the host CP (represented as
an application) or an adjacent CP (represented as a CDRSC)
TYPE=LUALIAS
displays the resource definition table entry for the CDRSC whose name is
associated with the LUALIAS. If a network-qualified name is specified,
VTAM does not search for an LUALIAS with that resource name. For more
information on CDRSCs that are defined with an LUALIAS, see the OS/390
eNetwork Communications Server: SNA Resource Definition Reference.
TYPE=RESOURCE
displays the resource definition table entry for the resource named on the
RESOURCE operand. VTAM searches for the resource in the following
order:
1. VTAM searches for an SSCP (CDRM), a host CP (application), or an
adjacent CP (CDRSC) by the name specified on the RESOURCE
operand and displays the resource definition table entry for the first
resource found.
2. If VTAM does not find an SSCP, a host CP, or an adjacent CP, it
searches for a resource with the name specified on the RESOURCE
operand and displays the resource definition table entry for the
resource, if it finds it.
3. If VTAM does not find a resource by that name, it searches for a
USERVAR with the name specified on the RESOURCE operand and
displays the resource definition table entry for the resource, if it finds it.
4. If VTAM does not find a USERVAR by that name, or a USERVAR is
found but the resource defined as the value of the USERVAR is not
found, it searches for an LUALIAS with the name specified on the
RESOURCE operand and displays the resource definition table entry for
the CDRSC, if it finds it.
TYPE=SHADOW
displays the resource definition table entry for a shadow resource, if it
exists. Included in the information displayed is the real resource that caused
the displayed resource to become a shadow resource.

For more information on shadow resources, see the OS/390 eNetwork

Communications Server: SNA Network Implementation Guide.
TYPE=SSCP
displays the resource definition table entry for the SSCP (represented as a
CDRM).
TYPE=USERVAR
displays the resource definition table entry for the resource whose name is
associated with the USERVAR.
TYPE=XCFCP
displays the resource definition table entry for the dynamic XCF local SNA
PU representing the connection to another VTAM in the XCF group, when
the RESOURCE operand specifies the CP name of the other VTAM.
XLENGTH
specifies the number of bytes in hexadecimal to display. The valid range is
1–value of DSPLYMAX multiplied by 16, converted to hexadecimal.

Chapter 2. VTAM Operator Commands 245

DISPLAY VTAMSTOR
Resulting Display
The resulting display differs depending on the operands specified.
If the ADDRESS operand is specified, the command displays the contents of
storage at the specified address.
If the MODULE operand is specified, the command displays:
– the entry point address of the module
– the service level of the module
– the first 32 bytes of the module
If the NETADDR operand is specified, the command displays:
– the name of the associated resource
– the resource definition table entry
If the RESOURCE operand is specified, the command displays:
– the resource definition table entry.

Examples
Displaying storage contents associated with a storage address:
d net,vtamstor,address=d7d000,length=256
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = VTAMSTOR
IST1573I STORAGE DISPLAY BEGINS AT LOCATION 00D7D000
IST1574I -010 00000010 00000001 8000083C 00D057C0 *................
IST1574I +000 E5C5F4F4 40404040 001FFFFF 01434020 *VE44 ...... .
IST1574I +010 00000000 001FFFFF 11280000 00000000 *................
IST1574I +020 01CF2070 00000000 00000000 00000000 *................
IST1574I +030 00D7D32C 00000000 13201000 07F00010 *.PL..........0..
IST1574I +040 11280000 00000000 01CF2070 00000000 *................
IST1574I +050 00000000 00000000 00D7D2D4 00000000 *.........PKM....
IST1574I +060 0C281000 07F00010 00000000 81C63AB0 *.....0.......F..
IST1574I +070 11400000 00000000 01CF2070 00000000 *. ..............
IST1574I +080 01E9DCB8 00000000 019BE0A0 00000000 *.Z..............
IST1574I +090 10321000 07F00010 00000000 00000000 *.....0..........
IST1574I +0A0 00000000 00000000 00000000 00000000 *................
IST1574I +0B0 11300000 00000000 01CF2070 00000000 *................
IST1574I +0C0 00000000 00000000 01A200C4 00000000 *...........D....
IST1574I +0D0 0B211000 07F00010 00000000 00000000 *.....0..........
IST1574I +0E0 11280000 00000000 01CF2070 00000000 *................
IST1574I +0F0 00000000 00000000 00D7DC5C 01914010 *.........P.*.. .
IST314I END

Displaying storage contents associated with a module:

d net,vtamstor,module=istinm01
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = VTAMSTOR
IST1571I ISTINM01 ENTRY POINT IS 01EA00E8 LEVEL IS 96.184
IST1574I +000 47F0F014 0FC9E2E3 C9D5D4F0 F140F9F6 *.00..ISTINM01 96
IST1574I +010 4BF1F8F4 90ECD00C 18CF41B0 CFFF50D0 *.184..........&.
IST314I END

Displaying storage contents associated with a network address:

d net,vtamstor,netaddr=(7,1),netid=netb
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = VTAMSTOR
IST075I NAME = NETB.SSCP7B, TYPE = CDRM
IST1620I SUBAREA = X'00000007' ( 7) ELEMENT = X'0001' ( 1)
IST1573I RDTE STORAGE DISPLAY BEGINS AT LOCATION 0141E9C0
IST1574I +000 E2E2C3D7 F7C24040 80000000 1F400600 *SSCP7B ..... ..

246 SNA Operation

 DISPLAY VTAMSTOR
IST1574I +010 00000000 00000000 00000000 0141EA70 *................
IST1574I +020 0141EA28 00000630 000001D0 00000000 *................
IST1574I +030 0141E008 00000000 00000000 00030003 *................
IST1574I +040 00000000 00000000 00000000 00000000 *................
IST1574I +050 00000000 00000000 C06D0000 00800000 *........._......
IST1574I +060 00000000 00000000 00000000 00000000 *................
IST1574I +070 00000000 00000000 00000000 00000000 *................
IST1574I +080 3F013F01 00000000 00000000 00000000 *................
IST1574I +090 00000000 00000000 00000000 00000000 *................
IST1574I +0A0 00000000 00000000 00000000 00000000 *................
IST1574I +0B0 00000000 0141EAE0 00000000 00000000 *................
IST1574I +0C0 00000000 00000000 00000000 00000000 *................
IST1574I +0D0 00000000 00000000 00000000 00000000 *................
IST1574I +0E0 00000000 00000000 00000000 00000000 *................
IST1574I +0F0 00000000 00000000 00000000 00000000 *................
IST1574I +100 00000000 00000000 00000000 00000000 *................
IST1574I +110 00000000 00000000 00000000 00000000 *................
IST1574I +120 00000000 00000000 00000000 00000000 *................
IST1574I +130 0141EB90 D5C5E3C2 40404040 00000000 *....NETB ....
IST1574I +140 00000000 00000000 00000000 00000000 *................
IST1574I +150 00000000 40404040 40404040 00000000 *.... ....
IST1574I +160 00000000 00000000 00000000 00000000 *................
IST1574I +170 00000000 00000000 00000000 00000000 *................
IST1574I +180 00000000 00000000 00000000 400000C8 *............ ..H
IST1574I +190 00000000 00000000 80000000 00000000 *................
IST1574I +1A0 00000000 00000000 00000000 00000000 *................
IST1574I +1B0 00000000 00000000 00004000 00000000 *.......... .....
IST1574I +1C0 00000000 00000000 00000000 00000000 *................
IST314I END

Displaying storage contents associated with a resource name:

d net,vtamstor,resource=neta.appl8
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = VTAMSTOR
IST075I NAME = NETA.APPL8, TYPE = APPL
IST1046I SHADOW NETA.APPL8 ALSO EXISTS
IST1620I SUBAREA = X'00000001' ( 1) ELEMENT = X'0026' ( 38)
IST1573I RDTE STORAGE DISPLAY BEGINS AT LOCATION 01305970
IST1574I +000 C1D7D7D3 F8404040 80000000 00550200 *APPL8 ........
IST1574I +010 00000000 00010026 00000000 01305A20 *..............!.
IST1574I +020 013059D8 00000120 00000120 00000000 *...Q............
IST1574I +030 01304008 00000000 00000000 02000200 *.. .............
IST1574I +040 00010008 10010010 00050900 00000000 *................
IST1574I +050 00000504 00000000 C06D0000 00800000 *........._......
IST1574I +060 00000000 00000000 00000000 00000000 *................
IST1574I +070 00000000 00000000 00000000 00000000 *................
IST1574I +080 07010701 00750000 08800000 01305850 *...............&
IST1574I +090 01305A90 00000000 00000000 20080400 *..!.............
IST1574I +0A0 00000000 00000000 01310010 00000000 *................
IST1574I +0B0 00000000 00000000 00000000 00000000 *................
IST1574I +0C0 01FD0000 00010026 0000A000 0001C000 *................
IST1574I +0D0 C1D7D7D3 F8404040 40404040 40404040 *APPL8
IST1574I +0E0 00000000 00000000 00000000 00000000 *................
IST1574I +0F0 00000000 00000000 00000000 00000000 *................
IST1574I +100 00000000 00000000 00000000 00000000 *................
IST1574I +110 40404040 40404040 000F4240 00000000 * ... ....
IST924I -------------------------------------------------------------
IST1573I RDTE PROFILE STORAGE DISPLAY BEGINS AT LOCATION 01310010
IST1574I +000 00000047 00000000 00000000 00000000 *................
IST1574I +010 00000000 00000000 00000000 00000000 *................
IST1574I +020 00000000 00000000 00000000 00000000 *................
IST1574I +030 00000000 00000000 00000000 00000000 *................
IST1574I +040 00000000 00000000 00000000 00000000 *................
IST1574I +050 00000000 00000000 *........
IST314I END

Chapter 2. VTAM Operator Commands 247

HALT

HALT Command
,CDLINK=ACT
ÊÊ HALT NET ÊÍ
,CDLINK= ACT
INACT

Abbreviations
Operand Abbreviation
HALT Z

Purpose
The HALT command requests a normal halt of VTAM without disrupting active
LU-LU sessions. (See also the HALT CANCEL Command and the HALT QUICK
Command.)

CS OS/390 upper layer protocol (ULP) service access points (SAPs) will also not
be disrupted.

This command causes sessions to terminate. Multinode persistent sessions are not
recoverable.

If VTAM was defined as a network node or interchange node and a checkpoint data
set is available, VTAM takes checkpoints of the directory database and the topology
database during normal HALT processing.

Operands
CDLINK
specifies whether any active, leased, cross-domain SDLC links between NCPs
are to remain active after the NCPs have been deactivated.

This operand is effective only on the first HALT command. Any CDLINK
specifications on subsequent HALT commands are ignored.
CDLINK=ACT
specifies that any active cross-domain SDLC links are to remain active after
the NCP major nodes are deactivated, so that information being routed
through the NCPs can continue to be so routed. That is, any cross-domain
sessions that use the NCPs as transit nodes can continue.
CDLINK=INACT
specifies that cross-domain SDLC links are to be deactivated, along with
the rest of the domain. This disrupts any sessions through those
cross-domain links.

248 SNA Operation

 HALT CANCEL

HALT CANCEL Command

,DUMP=NO
ÊÊ HALT NET,CANCEL ÊÍ
,DUMP= NO
YES

Abbreviations
Operand Abbreviation
HALT Z

Purpose
The HALT CANCEL command should be used if the HALT and HALT QUICK
commands do not terminate VTAM. This command depends only on the proper
functioning of the operating system’s abnormal termination facilities.

CS OS/390 upper layer protocol (ULP) service access points (SAPs) will be
abnormally terminated.

This command does not terminate multinode persistent sessions; therefore, the
sessions are recoverable

The HALT CANCEL command results in an abend of VTAM with a system

completion code of X'0A9'. No further I/O operations are performed. VTAM
application programs having a TPEND exit are notified of a VTAM shutdown, and
data in the process of being transmitted might be lost. If the TPEND exit cannot be
scheduled, the application program is abnormally terminated. In extraordinary
circumstances, the operator might have to cancel some application programs. It is a
good idea to shut down application programs (have them close their VTAM ACB)
before you issue the HALT CANCEL command.

It is possible that the MVS operator console might be hung after you issue a HALT
CANCEL command, for example if a message group is truncated before it can be
displayed. You can clear the console by issuing the MVS command K Q.

VTAM does not take checkpoints of the directory database and the topology
database during HALT CANCEL processing.

Operands
DUMP
specifies whether a console dump is to be written to a SYS1.DUMP dataset
before VTAM is terminated.
DUMP=YES
specifies that a console dump is to be written before VTAM is terminated.
DUMP=NO
specifies that a console dump is not to be written before VTAM is
terminated.

Chapter 2. VTAM Operator Commands 249

HALT QUICK

HALT QUICK Command

,CDLINK=ACT
ÊÊ HALT NET,QUICK ÊÍ
,CDLINK= ACT
INACT

Abbreviations
Operand Abbreviation
HALT Z

Purpose
You can use the HALT QUICK command to halt VTAM more quickly than with a
normal HALT command. However, HALT QUICK disrupts LU-LU sessions. In a
session using multiple resources, you must wait for any deactivation requests to
complete before you issue this command. Otherwise, you will have to issue the
VARY INACT command to force deactivation of the session. (See the
TYPE=FORCE operand of the VARY INACT command on page 455 for more
information on forced deactivation.)

VTAM will initiate deactivation of CS OS/390 upper layer protocol (ULP) service
access points (SAPs).

This command causes sessions to terminate. Multinode persistent sessions are not
recoverable.

If a VTAM dump, load, or restart subtask is active when a HALT QUICK command
is issued, the subtask is detached and a system completion code of X'13E' or
X'33E' results. VTAM termination continues.

If VTAM was defined as a network node or interchange node and a checkpoint data
set is available, VTAM takes checkpoints of the directory database and the topology
database during HALT QUICK processing.

Operands
CDLINK
specifies whether any active cross-domain SDLC links between NCPs are to
remain active after the NCPs have been deactivated.

This operand is effective only on the first HALT QUICK command. Any CDLINK
specifications on subsequent HALT QUICK commands are ignored.
CDLINK=ACT
specifies that any active, leased, cross-domain SDLC links are to remain
active after the NCP major nodes are deactivated, so that information being
routed through the NCPs can continue to be so routed. That is, any
cross-domain sessions that use the NCPs as transit nodes can continue.
CDLINK=INACT
specifies that cross-domain SDLC links are to be deactivated, along with
the rest of the domain. This disrupts any sessions through these
cross-domain links.

250 SNA Operation

 MODIFY ALSLIST

MODIFY ALSLIST Command

Add an entry to an adjacent link station list:

ÊÊ MODIFY procname,ALSLIST ,ACTION=ADD ,ID= * Ê

cdrsc_major_node
cdrsc_name

Ê ,NEWALS=adjacent_link_station_name ÊÍ

Delete an entry from an adjacent link station list:

ÊÊ MODIFY procname,ALSLIST ,ACTION=DELETE ,ID= * Ê

cdrsc_major_node
cdrsc_name

Ê ,OLDALS=adjacent_link_station_name ÊÍ

Replace an entry in an adjacent link station list:

ÊÊ MODIFY procname,ALSLIST ,ACTION=REPLACE ,ID= * Ê

cdrsc_major_node
cdrsc_name

Ê ,NEWALS=adjacent_link_station_name ,OLDALS=adjacent_link_station_name ÊÍ

Create a dynamic CDRSC and add entry in adjacent link station list:

ÊÊ MODIFY procname,ALSLIST ,ACTION=CREATE ,ID=cdrsc_name Ê

Ê ,NEWALS=adjacent_link_station_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F
ACTION=CREATE ACTION=CRE
ACTION=DELETE ACTION=DEL
ACTION=REPLACE ACTION=REP
NEWALS NEW
OLDALS OLD

Purpose
The MODIFY ALSLIST (adjacent link station list) command enables you to create or
change an entry in the default adjacent link station list for an independent LU. A
change to the adjacent link station list affects only sessions established after the
change is made. It does not affect active or pending active sessions.

Chapter 2. VTAM Operator Commands 251

MODIFY ALSLIST
Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ACTION
specifies whether VTAM is to create a dynamic cross-domain resource, add a
PU to the adjacent link station list, delete a PU from the list, or replace a PU
currently named in the adjacent link station list with another PU.
ACTION=ADD
adds a new PU to the adjacent link station list for the already existing
independent LU specified. Specify the name of the PU on the NEWALS
operand.

Note: You can code NEWALS=ISTAPNPU instead of a real adjacent link

station name. ISTAPNPU is a generic representation for any
APPN-capable adjacent link station. If VTAM finds ISTAPNPU in the
adjacent link station list for an independent LU, VTAM treats
ISTAPNPU as if it were any active APPN-capable adjacent link
station when trying to determine whether to attempt routing through
the APPN network.
ACTION=CREATE
creates a dynamic cross-domain resource for the independent LU specified
on the ID operand. The dynamic cross-domain resource is created only if
the independent LU does not already exist. If the independent LU already
exists or if it is dynamically created, the adjacent link station list for the
independent LU is updated to include the specified adjacent link station
(ALS).

If the specified independent LU is dynamic (that is, it was created as a

dynamic cross-domain resource and ACTION=ADD or ACTION=CREATE
added an ALS to the list, or, ACTION=CREATE created the resource), but
the ALS (PU) has DYNLU=NO specified on its definition statement, the ALS
will be added to the ALS list but it will not be usable for sessions with the
dynamically defined independent LU.

The CDRSCTI start option determines how long the newly created dynamic
cross-domain resource can remain without active sessions before it is
deleted.

Specify the name of the PU to be created on the NEWALS operand.

ACTION=DELETE
deletes an existing PU from the adjacent link station list. Specify the name
of the PU to be deleted on the OLDALS operand.

Note: You can code OLDALS=ISTAPNPU instead of a real adjacent link

station name. ISTAPNPU is a generic representation for any
APPN-capable adjacent link station. If VTAM finds ISTAPNPU in the
adjacent link station list for an independent LU, VTAM treats

252 SNA Operation

 MODIFY ALSLIST
ISTAPNPU as if it were any active APPN-capable adjacent link
station when trying to determine whether to attempt routing through
the APPN network. This command does not delete any real PU
names that are APPN-capable; it only deletes the ISTAPNPU entry.
ACTION=REPLACE
adds a new PU to the adjacent link station list and deletes an existing PU
from that list. Specify the name of the PU to be added on the NEWALS
operand and the name of the PU to be deleted on the OLDALS operand.
Both the NEWALS and the OLDALS operands are required if
ACTION=REPLACE.

Note: You can code NEWALS=ISTAPNPU or OLDALS=ISTAPNPU instead

of a real adjacent link station name. ISTAPNPU is a generic
representation for any APPN-capable adjacent link station. If VTAM
finds ISTAPNPU in the adjacent link station list for an independent
LU, VTAM treats ISTAPNPU as if it were any APPN-capable
adjacent link station when trying to determine whether to attempt
routing through the APPN network.
ID specifies the cross-domain resources that are to be changed.
ID=cdrsc_major_node
specifies that this command applies to all cross-domain resources that
apply to that major node.
ID=cdrsc_name
specifies that this command applies to the specified cross-domain resource
(independent LU) that is to be created or changed. You can specify a
network-qualified name for the independent LU.
ID=*
specifies that this command applies to all cross-domain resources.
NEWALS=adjacent_link_station_name
specifies the name of the new adjacent link station (PU) for the independent LU
specified. You use this operand to add a PU or to identify a new PU that will
replace an existing one in the adjacent link station list.
OLDALS=adjacent_link_station_name
specifies the name of the existing adjacent link station (PU) for the independent
LU specified. You use this operand to delete a PU or to identify an existing PU
that is to be replaced by another PU in the adjacent link station list.

Chapter 2. VTAM Operator Commands 253

MODIFY APINGDTP

MODIFY APINGDTP Command

ÊÊ MODIFY procname,APINGDTP ,INSTANCE= UNLIMITED ÊÍ
value

Purpose
The MODIFY APINGDTP command allows you to change the number of APINGD
transaction programs permitted to run concurrently for responding to APING
requests from other nodes.

See the OS/390 eNetwork Communications Server: SNA Network Implementation

Guide for more information on APING.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
INSTANCE
specifies the number of APINGD transaction programs permitted to run
concurrently for responding to APING requests from other nodes.
INSTANCE=UNLIMITED
specifies that there is no limit to the number of transaction programs
permitted to run concurrently for responding to APING requests from other
nodes.
INSTANCE=value
specifies the number of transaction programs permitted to run concurrently
for responding to APING requests from other nodes.

Specifying INSTANCE=0 causes APING requests from other nodes to fail.

254 SNA Operation

 MODIFY CDRM

MODIFY CDRM Command

ÊÊ MODIFY procname,CDRM= new_cdrm Ê

(new_cdrm)
(new_cdrm,old_cdrm)

,TYPE=NORM
Ê ,ID= * ÊÍ
cdrsc_major_node_name ,TYPE= IMMED
cdrsc_minor_node_name NORM

Abbreviations
Operand Abbreviation
MODIFY F
TYPE=IMMED IMMED or I or TYPE=I
TYPE=NORM NORM or N or TYPE=N

Purpose
The MODIFY CDRM (cross-domain resource manager) command tells VTAM which
SSCP (CDRM) is the owner of a particular cross-domain resource (CDRSC) or set
of CDRSCs. Ongoing sessions of CDRSCs affected by this command are not
disrupted. The command changes only the name of the external CDRM responsible
for all future session setups with these CDRSCs.

DISPLAY commands issued before a new name takes effect show the old owner
CDRM name.

If the cross-domain resource affected by the MODIFY CDRM command was

predefined with a CDRM coded on the CDRSC definition statement, the MODIFY
CDRM command changes the CDRM that owns the CDRSC for the current and
subsequent sessions. If the CDRSC was not predefined with CDRM coded, the
change is temporary. After such new or existing sessions terminate, the CDRM is
changed back to having no predefined CDRM coded.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CDRM
specifies the new CDRM to be associated with the CDRSCs, and the CDRM
that it replaces.

Chapter 2. VTAM Operator Commands 255

MODIFY CDRM
Note: For a CDRM, you can specify a network-qualified name, but this does
not remove the restriction that the non-network-qualified CDRM name
must be unique across networks.
CDRM=new_cdrm
specifies the name of the new CDRM to associate with the CDRSCs.
CDRM=(new_cdrm,old_cdrm)
specifies both the new CDRM to associate with the CDRSCs and the
CDRM that was previously associated with the CDRSCs. If old_cdrm is
specified, only the CDRM names that match this old cdrm name are
changed.
ID identifies the CDRSC major or minor node for which the owning CDRM name is
to be changed.
ID=cdrsc_major_node_name
changes the owning CDRM for all CDRSCs in the hierarchy under the
major node. The major node name can be specified as a network-qualified
name.
ID=cdrsc_minor_node_name
changes the owning CDRM for only the specified minor node. The minor
node name can be specified as a network-qualified name.
ID=*
changes the owning CDRM for all CDRSCs known to VTAM.
TYPE
indicates whether CDRM takeover occurs without waiting for any sessions that
are present to end.
TYPE=IMMED
indicates that the CDRM is to be changed immediately, regardless of the
presence of sessions.
TYPE=NORM
indicates that the MODIFY CDRM command waits until all sessions have
ended before changing the CDRM. If no session exists for a CDRSC
affected by the MODIFY CDRM command, the CDRM is changed
immediately (as with TYPE=IMMED).

If sessions are active or queued for a specific CDRSC affected by a

MODIFY CDRM command, the current owning CDRM remains in effect until
all active and queued sessions with the resource have been terminated. At
that time, the owning CDRM name is changed and the new CDRM name
takes effect.

256 SNA Operation

 MODIFY CHKPT

MODIFY CHKPT Command

,TYPE=ALL
ÊÊ MODIFY procname,CHKPT ÊÍ
,TYPE= ALL
DIR
TOPO

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY CHKPT (checkpoint) command saves a copy of the directory
database or the topology database (or both) to a checkpoint data set. During a
VTAM recycle, you can restart VTAM with a current list of resources. (VTAM also
takes checkpoints during HALT and HALT QUICK processing, but not during HALT
CANCEL.) As the checkpoint for each affected data set is completed, a message is
issued that indicates whether the checkpoint was successful. The message
provides the name of the data set that was updated.

This command is valid only when it is issued at a network node or an interchange

node.

When you issue this command for the directory database (TYPE=DIR or
TYPE=ALL), VTAM first cleans up the database, then saves it. Cleanup means that
dynamic resources that have not been used in some period of time (default 8 days)
are deleted from the database. Only dynamic resources that have been the target
of a search are then saved. You can change the period of time by using the
MODIFY VTAMOPTS command to reset the DIRTIME start option. For more
information about the MODIFY VTAMOPTS command, see the “MODIFY
VTAMOPTS Command” on page 385. For more information about the DIRTIME
start option, see the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
TYPE
identifies the APPN database to save via a checkpoint.
TYPE=DIR
Writes the directory database to a data set.

Chapter 2. VTAM Operator Commands 257

MODIFY CHKPT
TYPE=TOPO
Writes the topology database to a data set.
TYPE=ALL
Writes both the directory database and the topology database to a data set.

258 SNA Operation

 MODIFY CNOS

MODIFY CNOS Command

Set session limits to zero for one logon mode:

ÊÊ MODIFY procname,CNOS ,ID=appl_name ,LIMITS=(0,0,0) Ê

,DRAINL=NO
Ê ,LOGMODE=logon_mode_name ,LUNAME=lu_name Ê
,DRAINL= NO
YES

,DRAINR=NO ,NBRMODE=ONE ,RESP=LOCAL

Ê Ê
,DRAINR= NO ,RESP= LOCAL
YES REMOTE

,SNGSESLU=NO
Ê ÊÍ
,SNGSESLU= NO
YES

Set session limits to zero for all logon modes:

ÊÊ MODIFY procname,CNOS ,ID=appl_name ,LIMITS=(0,0,0) ,LUNAME=lu_name Ê

,DRAINL=NO ,DRAINR=NO
Ê ,NBRMODE=ALL Ê
,DRAINL= NO ,DRAINR= NO
YES YES

,RESP=LOCAL ,SNGSESLU=NO
Ê ÊÍ
,RESP= LOCAL ,SNGSESLU= NO
REMOTE YES

Set session limits to non-zero:

ÊÊ MODIFY procname,CNOS ,ID=appl_name ,LIMITS=(sesslim,minwinl,minwinr) Ê

Ê ,LOGMODE=logon_mode_name ,LUNAME=lu_name Ê
,CONVSECL= NONE
CONV
ALREADYV
PERSISTV
AVPV

,NBRMODE=ONE ,RESP=LOCAL ,SNGSESLU=NO

Ê ÊÍ
,RESP= LOCAL ,SNGSESLU= NO
REMOTE YES

Chapter 2. VTAM Operator Commands 259

MODIFY CNOS
Use existing session limits:

ÊÊ MODIFY procname,CNOS ,ID=appl_name ,LOGMODE=logon_mode_name Ê

,NBRMODE=ONE
Ê ,LUNAME=lu_name Ê
,CONVSECL= NONE
CONV
ALREADYV
PERSISTV
AVPV

,SNGSESLU=NO
Ê ÊÍ
,SNGSESLU= NO
YES

Abbreviations
Operand Abbreviation
MODIFY F
CONVSECL=ALREADYV CONVSECL=A or CSECL=ALREADYV or
CSECL=A
CONVSECL=AVPV CONVSECL=V or CSECL=AVPV or
CSECL=V
CONVSECL=CONV CONVSECL=C or CSECL=CONV or
CSECL=C
CONVSECL=NONE CONVSECL=N or CSECL=NONE or
CSECL=N
CONVSECL=PERSISTV CONVSECL=P or CSECL=PERSISTV or
CSECL=P
DRAINL=NO DRAINL=N or DRL=NO or DRL=N
DRAINL=YES DRAINL=Y or DRL=YES or DRL=Y
DRAINR=NO DRAINR=N or DRR=NO or DRR=N
DRAINR=YES DRAINR=Y or DRR=YES or DRR=Y
LOGMODE LOG
LUNAME LU
NBRMODE=ALL NBRMODE=A or NBM=ALL or NBM=A
NBRMODE=ONE NBRMODE=O or NBM=ONE or NBM=O
RESP=LOCAL RESP=L or RSP=LOCAL or RSP=L
RESP=REMOTE RESP=R or RSP=REMOTE or RSP=R
SNGSESLU=NO SNGSESLU=N or SNG=NO or SNG=N
SNGSESLU=YES SNGSESLU=Y or SNG=YES or SNG=Y

Purpose
The MODIFY CNOS (change number of sessions) command initiates a CNOS
transaction with a partner LU for the specified application program.

260 SNA Operation

 MODIFY CNOS
Using this command, you can modify session limits, request a partner LU to drain
its queue of allocation requests, or request a partner LU to be responsible for
deactivating the session. The MODIFY CNOS command does the same thing as
the APPCCMD CONTROL=OPRCNTL,QUALIFY=CNOS macro, which is described
in the OS/390 eNetwork Communications Server: SNA Programmers LU 6.2
Reference.

Note: For operands that are optional and that do not have a default value, the
default values used are obtained from a value already established for the
specified LU-mode pair or from the APPL definition of the application
specified.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CONVSECL
specifies the conversation security level that the local LU accepts.

The CONVSECL field is used only for a CNOS request that initializes session
limits to a non-zero value for a partner LU. Subsequent CNOS requests for the
same partner LU ignore this setting.

There are four sources for CONVSECL:

1. Security manager profile
2. CNOS
3. User BIND
4. SECACPT operand on APPL definition statement.

The order of this list indicates the selection hierarchy if no security manager
profile is provided. If a security manager profile exists, the value in that profile
sets the upper limit of conversation-level security that can be specified by the
other three sources. If no security manager profile exists, the value in the
CNOS takes precedence over any other sources of conversation security level.
If no value was specified in the CNOS, and a user BIND is provided, then the
value from the BIND is used.

If no conversation-level security value is available in either the CNOS or user

BIND, then the default that is used is derived from the SECACPT parameter on
the APPL statement.
CONVSECL=NONE
indicates that the LU does not accept conversation-level security (FMH-5s
that include security subfields).
CONVSECL=CONV
indicates that the LU accepts conversation-level security (FMH-5s that
include security subfields).

Chapter 2. VTAM Operator Commands 261

MODIFY CNOS
CONVSECL=ALREADYV
indicates that the LU accepts conversation-level security (FMH-5s that
include security subfields) and that the application program accepts the
“already verified” indicator on conversation requests it receives from the
partner LU.
CONVSECL=PERSISTV
indicates that the LU supports conversation-level security (FMH-5s that
include security subfields) and accepts the “persistent verification” indicators
on conversation requests it receives from the partner LU.
CONVSECL=AVPV
indicates that the LU supports conversation-level security (FMH-5s that
include security subfields) and accepts both the “persistent verification”
indicators and the “already verified” indicator on conversation requests it
receives from the partner LU.
DRAINL
specifies whether the source side can drain its allocation requests. This
operand is valid only if the session limits are being reset to zero.
DRAINL=YES
specifies that the source side can drain its allocation requests.
DRAINL=NO
specifies that the source side cannot drain its allocation requests.
DRAINR
specifies whether the target side can drain its allocation requests. This operand
is valid only if the session limits are being reset to zero.
DRAINR=YES
specifies that the target side can drain its allocation requests.
DRAINR=NO
specifies that the target side cannot drain its allocation requests.
ID=appl_name
specifies the name of the LU 6.2 application program to which the change in
the session limit and contention-winner polarity values apply. This value cannot
be a network-qualified name.
LIMITS=(sesslim,minwinl,minwinr)
overrides all other sources of session limits. VTAM performs negotiation if
necessary.
sesslim
specifies the maximum number of parallel sessions between the source
side and the target side. It uses the logon mode name specified in the
LOGMODE operand. The valid range is 0–32767.
minwinl
specifies the minimum number of parallel sessions for which the source
side is guaranteed to be the contention winner. It uses the logon mode
name specified in the LOGMODE operand. The valid range is 0–32767.
minwinr
specifies the minimum number of parallel sessions for which the partner LU
is guaranteed to be the contention winner. It uses the logon mode name
specified in the LOGMODE operand. The valid range is 0–32767.
LOGMODE=logon_mode_name
specifies the name of the logon mode entry for which session limit and polarity

262 SNA Operation

 MODIFY CNOS
values are to be changed. When NBRMODE=ONE is specified or assumed by
default, LOGMODE is required. When NBRMODE=ALL is specified, LOGMODE
is not needed, and it is ignored if you specify it.
LUNAME=lu_name
specifies the name of the partner LU to which the change in the session limit
and contention-winner polarity values apply. The name can be a
network-qualified name in the form of netid.luname.

If lu_name is an ACB name, and the ACB name matches the name on the
APPL definition statement, then you can use a network-qualified ACB name.

If PARMS=(NQNAMES=NO) is coded on the ACB macro, and a

network-qualified name is specified, the network identifier is ignored.

If PARMS=(NQNAMES=YES) is coded on the ACB macro, luname must be a

network-qualified name.
NBRMODE
specifies whether the setting of the session limit and the contention-winner
polarity values applies only for the specified logon mode name or for all logon
mode names that apply to the partner LU.
NBRMODE=ONE
specifies that the session limit and contention-winner polarity values for only
the logon mode name specified in the LOGMODE operand are to be set.
NBRMODE=ALL
specifies that the session limit and contention-winner polarity values for all
logon mode names that apply to the partner LU are to be reset to zero,
except for SNASVCMG, which remains unchanged. NBRMODE=ALL is
valid only when LIMITS=(0,0,0) is specified.
RESP
specifies which LU is responsible for deactivating the sessions as a result of
resetting the session limit or for changing the contention-winner polarity values
for parallel session connections.
RESP=LOCAL
specifies the local LU is responsible for deactivating the sessions as a
result of resetting the session limit or changing the contention-winner
polarity values for parallel session connections.
RESP=REMOTE
specifies the remote LU is responsible for deactivating the sessions as a
result of resetting the session limit or changing the contention-winner
polarity values for parallel session connections.
SNGSESLU
specifies whether the partner LU is a single-session LU, which does not support
parallel sessions. VTAM uses the value specified on this operand to determine
the indication of parallel-session support and CNOS support it specifies in the
BIND requests. This operand is examined by VTAM only when the partner LU
parallel-session capability has not been established.
SNGSESLU=YES
specifies that the partner LU is a single-session LU which does not support
parallel sessions.
SNGSESLU=NO
specifies that the partner LU supports parallel sessions.

Chapter 2. VTAM Operator Commands 263

MODIFY COMPRESS

MODIFY COMPRESS Command

Change the compression levels set by the APPL definition statement:

ÊÊ MODIFY procname,COMPRESS ,ID=appl_name Ê

Ê ,CMPAPPLI=input_limit ÊÍ
,CMPAPPLO=output_limit
,CMPAPPLI=input_limit,CMPAPPLO=output_limit

Change the compression level set by start option:

ÊÊ MODIFY procname,COMPRESS ,CMPVTAM=overall_limit ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY COMPRESS command allows you to change the value of the data
compression levels originally set by the CMPVTAM start option or by an APPL
definition statement.

The levels of compression available are in the range 0–4:

0 No compression
1 Run-length encoding (RLE)
2 Small adaptive compression table
3 Medium adaptive compression table
4 Large adaptive compression table

See the OS/390 eNetwork Communications Server: SNA Network Implementation

Guide for additional information about compression.

Note: You can use the “MODIFY VTAMOPTS Command” on page 385 (CMPVTAM
operand) to change the compression level set by the start option.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CMPAPPLI=input_limit
specifies the input compression limit for the application. This operand allows

264 SNA Operation

 MODIFY COMPRESS
compression-level limits for a specific application to be set lower than the
overall limit specified by the CMPVTAM start option.

The valid range is 0–4. Zero specifies no compression.

The valid range is 0–1. Zero specifies no compression.

The limit specified by this operand is in effect only during sessions for which the
application acts as the PLU and when the limit is lower than that specified by
the CMPVTAM start option.
CMPAPPLO=output_limit
specifies the output compression limit for the application. This operand allows
compression-level limits for a specific application to be set lower than the
overall limit specified by the CMPVTAM start option.

The valid range is 0–4. Zero specifies no compression.

The valid range is 0–1. Zero specifies no compression.

The limit specified by this operand is in effect only during sessions for which the
application acts as the PLU and when the limit is lower than that specified by
the CMPVTAM start option.
CMPVTAM=overall_limit
specifies the overall compression limit for VTAM sessions. The new
compression limit takes effect on new sessions that are started after you issue
this command. Sessions that were started prior to this command are not
changed.

The valid range is 0–4. Zero specifies no compression.

The valid range is 0–1. Zero specifies no compression.

ID=appl_name
specifies the name of the application to which compression applies. This allows
modification of the compression limit for the session as set in the APPL
definition statement. The ID operand is required when either CMPAPPLI or
CMPAPPLO is specified.

Chapter 2. VTAM Operator Commands 265

MODIFY CSALIMIT

MODIFY CSALIMIT Command

,OPTION=TOTAL
ÊÊ MODIFY procname,CSALIMIT= value ÊÍ
(value ) ,OPTION= BELOW
,F TOTAL

Abbreviations
Operand Abbreviation
MODIFY F
OPTION=BELOW OPT=BELOW
OPTION=TOTAL OPT=TOTAL

Purpose
The MODIFY CSALIMIT command allows you to dynamically change the amount of
common service area (CSA) storage that VTAM is allowed to use.
Notes:
1. You can use the “MODIFY VTAMOPTS Command” on page 385 (CSALIMIT and
CSA24 operands) to perform the same function as this command. Use
CSALIMIT for OPTION=TOTAL and CSA24 for OPTION=BELOW.
2. MODIFY CSALIMIT may not function if VTAM’s available CSA is exhausted to
the point that the LPBUF buffer pool cannot expand.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CSALIMIT
specifies the maximum amount of common service area (CSA) storage to be
used by VTAM (value) and whether VTAM is to be forced to use that value (F).
The actual amount of storage used by VTAM for the CSA can be less than or
equal to the CSALIMIT. Use the “DISPLAY BFRUSE Command” on page 41 to
display the current CSALIMIT and VTAM’s current storage usage for the CSA.
CSALIMIT=value
specifies the maximum amount of CSA storage to be used by VTAM. The
value operand can be specified in any of the following forms:
0 specifies that no limit is enforced on the amount of CSA used by VTAM.
n or nK
n is a decimal integer that specifies VTAM’s CSA usage limit in units of
K (1024 bytes). For example, if CSALIMIT=4 or CSALIMIT=4K is
specified, a CSA limit of 4096 is assigned. The maximum value that can
be specified is 2097152K bytes.

266 SNA Operation

 MODIFY CSALIMIT
If the value specified for n is not a multiple of 4, it is rounded to the
next page-size multiple (4K bytes).

Note: If the number specified is greater than the available CSA, no

limit is enforced.
qM
q is a decimal integer that specifies VTAM’s CSA usage limit in units of
M (1048576 bytes, or 1024K bytes). For example, if CSALIMIT=4M is
specified, a CSA limit of 4194304 bytes is assigned. The maximum
value that can be specified is 2048M.

Note: If the number specified is greater than the available CSA, no

limit is enforced.
CSALIMIT=(value,F)
forces the specified value, n, nK, or qM, to be used as the CSA usage limit,
regardless of how much CSA storage is currently allocated to VTAM. If
VTAM’s current CSA value is greater than a newly specified CSALIMIT
value, all subsequent CSA requests by VTAM components are rejected until
the current CSA value falls below the CSALIMIT value.

If F is not specified, and the operator has specified a limit smaller than the
amount of CSA storage currently allocated to VTAM, a request to change
the CSA limit is rejected. If F is specified, these restrictions do not apply,
and the request to change the CSA will be successful.

Note: If a CSA limit is specified that is too low and the operator forces this
limit to take effect (by using F), the operator is prevented from using
VTAM commands until the CSA usage falls below the specified limit,
because CSA storage is needed to process all VTAM operator
commands except HALT CANCEL. If the CSA usage does not fall
below the specified CSA limit, VTAM must be canceled and restarted
with a more appropriate CSALIMIT value specified.
OPTION
specifies the area to be limited.
OPTION=TOTAL
designates the maximum amount of 24-bit or 31-bit addressable CSA
storage VTAM can use.
OPTION=BELOW
specifies that the MODIFY CSALIMIT command designates the maximum
amount of 24-bit addressable storage VTAM can use. OPTION=BELOW
corresponds to the CSA24 start option.

Note: OPTION=BELOW limits only the amount of explicitly requested 24-bit

addressable storage (for example, GETMAIN LOC=BELOW). If
VTAM is not specific about the location of the storage desired (for
example, GETMAIN LOC=ANY), and the operating system returns
24-bit addressable storage, that storage is not subject to
OPTION=BELOW limitations. Instead, it is treated as 31-bit
addressable storage in DISPLAY command output.

Chapter 2. VTAM Operator Commands 267

MODIFY CSM

MODIFY CSM Command

ÊÊ MODIFY procname,CSM ÊÍ
,ECSA=maxecsa ,FIXED=maxfix

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY CSM command is used to dynamically change the amount of storage
used by the communications storage manager (CSM). It can also be used to
activate changes made to the CSM parmlib member without requiring an IPL.
v To temporarily change the amount of storage used by CSM, issue this command
and specify the parameters you want to change on the ECSA and FIXED
operands.
v To permanently change the amount of storage used by CSM or tuning
parameters for CSM buffer pools, edit the CSM parmlib member and issue this
command without specifying any operands.

Note: Changing a parameter that decreases the specification of a limit may not
take effect immediately. Reducing the usage of the resource to comply to the
new limit may require users to free buffers to contract a storage pool’s size.
This type of change could also result in a CSM constraint condition being
indicated to users that are monitoring CSM resource usage.

For more information about the CSM parmlib member, see the OS/390 eNetwork
Communications Server: SNA Planning and Migration Guide .

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ECSA=maxecsa
specifies the maximum number of bytes of ECSA storage to be dedicated for
use by CSM. maxecsa is a decimal integer and must be specified in either
kilobytes (K) or megabytes (M) ranging from 1024K to 2048M.
FIXED=maxfix
specifies the maximum number of bytes of fixed storage to be dedicated for use
by CSM. maxfix is a decimal integer and must be specified in either kilobytes
(K) or megabytes (M) ranging from 1024K to 2048M.

268 SNA Operation

 MODIFY DEFAULTS

MODIFY DEFAULTS Command

Modify the DLOGMOD value for a resource:

ÊÊ MODIFY procname,DEFAULTS ,ID=resource_name ,DLOGMOD= ÊÍ

logon_mode_name

Change the delay timer for disconnection of a switched PU:

ÊÊ MODIFY procname,DEFAULTS ,ID=resource_name ,DISCNTIM=time_period ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F
DLOGMOD DLOG

Purpose
The MODIFY DEFAULTS command allows you to change the current value of the
DLOGMOD operand of a definition statement for an LU, application program, or
cross-domain resource without deactivating the entire major node.

The MODIFY DEFAULTS command also allows you to change the delay timer for
disconnection of a switched PU.

When VTAM receives the MODIFY DEFAULTS command, it overlays the existing
value for the specified operand with the new value.
Notes:
1. If you use the MODIFY DEFAULTS command to change the DLOGMOD
specification, be aware that later use of a VARY ACT,UPDATE=ALL command
for dynamic reconfiguration can undo the effects of the MODIFY DEFAULTS
command. This is because the DLOGMOD value in the definition file overrides
the value that was established with the MODIFY DEFAULTS command. Even if
no DLOGMOD is coded in the definition file, VTAM assumes a null value for
DLOGMOD and the null value overrides the MODIFY DEFAULTS value. To
prevent the new DLOGMOD specification from being deleted unintentionally,
code the DLOGMOD definition statement with the desired value.
2. You can use the MODIFY RESOURCE command to perform the same function
as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.

Chapter 2. VTAM Operator Commands 269

MODIFY DEFAULTS
DISCNTIM=time_period
specifies the amount of time that VTAM delays deactivation of the SSCP-PU
session when there are no outstanding LU-LU session requests.

You can specify the time in seconds (S). Specify the number of seconds as an
integer in the range 5–65535.

DISCNTIM is valid only for PU types 2 and 2.1 that have DISCNT=DELAY
specified on the PU definition statement.
DLOGMOD=logon_mode_name
specifies the new value for the logon mode. If DLOGMOD is specified with a
null value (left blank), the predefined DLOGMOD value is deleted.

Note: If DLOGMOD is specified with an unknown logon mode, a warning

message is issued indicating that it is unknown and the change is
accepted.
ID=resource_name
specifies the name of the resource to which the command applies. The name
can be a network-qualified name. If the name specified on the ID operand is
network-qualified, this name is considered to be the real name of the resource.

Note: If the resource name is a cross-network CDRSC which is defined with

NQNMODE=NQNAME (either by definition statement or start option), be
sure to use its network-qualified name on this command.

270 SNA Operation

 MODIFY DEFINE

MODIFY DEFINE Command

Set session limits to zero:

ÊÊ MODIFY procname,DEFINE ,ID=appl_name ,DLIMITS=(0,0,0) Ê

Ê ,LOGMODE=logon_mode_name ,LUNAME=lu_name Ê

,DELETE=NALLOW
Ê Ê
,AUTOSES=number_of_winner_sessions ,DELETE= ALLOW
NALLOW

Ê ÊÍ
,DDRAINL= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW

Set session limits to non-zero:

ÊÊ MODIFY procname,DEFINE ,ID=appl_name Ê

Ê ,DLIMITS=(dseslim,dminwinl,dminwinr) ,LOGMODE=logon_mode_name Ê

Ê ,LUNAME=lu_name Ê
,AUTOSES=number_of_winner_sessions

,DELETE=NALLOW
Ê ÊÍ
,DELETE= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW

Use existing session limits:

ÊÊ MODIFY procname,DEFINE ,ID=appl_name ,LOGMODE=logon_mode_name Ê

Ê ,LUNAME=lu_name Ê
,AUTOSES=number_of_winner_sessions

,DELETE=NALLOW
Ê ÊÍ
,DELETE= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW

Delete an unusable LU-mode entry:

ÊÊ MODIFY procname,DEFINE ,ID=appl_name ,LUNAME=lu_name ,DELETE=UNUSE ÊÍ

Chapter 2. VTAM Operator Commands 271

MODIFY DEFINE
Abbreviations
Operand Abbreviation
MODIFY F
AUTOSES AUTO
DELETE=ALLOW DELETE=A or DEL=ALLOW or DEL=A
DELETE=NALLOW DELETE=N or DEL=NALLOW or DEL=N
DELETE=UNUSE DELETE=U or DEL=UNUSE or DEL=U
DDRAINL=ALLOW DDRAINL=A or DDRL=ALLOW or DDRL=A
DDRAINL=NALLOW DDRAINL=N or DDRL=NALLOW or DDRL=N
DRESPL=ALLOW DRESPL=A or DRSP=ALLOW or DRSP=A
DRESPL=NALLOW DRESPL=N or DRSP=NALLOW or DRSP=N
LOGMODE LOG
LUNAME LU

Purpose
The MODIFY DEFINE command establishes new entries, modifies existing entries,
or deletes unusable entries in the LU-mode table for the specified application
program. The DEFINE values stored in the LU-mode table are used when VTAM
processes a CNOS transaction originated by the partner LU or when a CNOS
request is issued from the application program (local LU) without a CNOS structure.

When VTAM receives the MODIFY DEFINE command, it overlays the existing entry
with the values specified.

Note: For operands that are optional and that do not have a default value, the
default values used are obtained from a value already established for the
specified LU-mode pair or from the APPL definition statement of the
application program specified.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
AUTOSES=number_of_winner_sessions
specifies the number of contention-winner sessions to activate automatically,
rather than by allocation requests from the application program. The valid range
is 0–32767. If AUTOSES is not coded on the APPL statement, the default is
zero.
DDRAINL
specifies whether the source side can drain its allocation requests when the
application program is a target of a CNOS request that resets the session limits
to zero. This operand is valid only if the session limits are being reset to zero.

272 SNA Operation

 MODIFY DEFINE
DDRAINL=ALLOW
specifies that the application program is allowed to drain its allocation
requests when the application program is the target of a CNOS request that
resets the session limits to zero.
DDRAINL=NALLOW
specifies that the application program is not allowed to drain its allocation
requests.
DELETE
specifies whether a mode name entry can be deleted from the LU-mode table.
DELETE=ALLOW
specifies that a mode name entry can be deleted from the LU-mode table.
DELETE=NALLOW
specifies that a mode name entry cannot be deleted from the LU-mode
table.
DELETE=UNUSE
specifies that an unusable mode name entry is to be deleted from the
LU-mode table.

Note: DELETE=UNUSE is valid only for applications programs defined with

OPERCNOS=ALLOW and APPC=YES on the APPL definition
statement in the application program major node.
DLIMITS=(dseslim,dminwinl,dminwinr)
specifies the negotiation limits that are allowed between the source side and
target side. If DLIMITS is not coded on the APPL statement, the default is
(2,1,1).
dseslim
specifies the maximum number of sessions between the source side and
the target side. This number applies uniquely to each logon mode name for
which sessions can be established with a partner LU. The valid range is
0–32767.
dminwinl
specifies the minimum number of parallel sessions for which the source
side is guaranteed to be the contention winner. This number applies
uniquely to each logon mode name for which sessions can be established
with a partner LU. The valid range is 0–32767.
dminwinr
specifies the minimum number of parallel sessions for which the partner LU
is guaranteed to be the contention winner. This number applies uniquely to
each logon mode name for which sessions might be established with a
partner LU. The valid range is 0–32767.
DRESPL
specifies whether the LU is allowed to assume responsibility for deactivating
sessions if a CNOS request is received identifying the LU as the responsible
LU.
DRESPL=ALLOW
specifies that VTAM accepts a CNOS request specifying that the LU is
responsible for deactivating sessions.
DRESPL=NALLOW
specifies that VTAM does not accept a CNOS request specifying that the
LU is responsible for deactivating sessions.

Chapter 2. VTAM Operator Commands 273

MODIFY DEFINE
ID=appl_name
specifies the name of the LU 6.2 application program to which the command
applies. appl_name cannot be a network-qualified name.
LOGMODE=logon_mode_name
specifies the name of the logon mode entry for which session limit and
contention-winner polarity values are to be changed. The SNASVCMG
LOGMODE name is not allowed in the operand. The SNASVCMG LOGMODE
is managed internally by VTAM.
LUNAME=lu_name
specifies the name of the partner LU to which the change in the session limit
and contention-winner polarity values apply. The name can be a
network-qualified name in the form of netid.luname.

If lu_name is an ACB name, and the ACB name matches the name on the
APPL definition statement, then you can use a network-qualified ACB name.

If PARMS=(NQNAMES=NO) is coded on the ACB macro, and a

network-qualified name is specified, the network identifier is ignored.

If PARMS=(NQNAMES=YES) is coded on the ACB macro, luname must be a

network-qualified name.

274 SNA Operation

 MODIFY DIRECTRY

MODIFY DIRECTRY Command

Change the ownership of APPN resources in the directory database:

ÊÊ MODIFY procname,DIRECTRY ,FUNCTION=UPDATE ,ID= cdrsc_major_node_name Ê

resource_name

Ê ,CPNAME= new_cp_name ÊÍ
(new_cp_name,old_cp_name)
,NETSRVR=server_name
,CPNAME= new_cp_name ,NETSRVR=server_name
(new_cp_name,old_cp_name)

Delete a resource from the directory database:

ÊÊ MODIFY procname,DIRECTRY ,FUNCTION=DELETE ,ID= cdrsc_major_node_name ÊÍ

resource_name

Abbreviations
Operand Abbreviation
MODIFY F
FUNCTION=DELETE DELETE
FUNCTION=UPDATE UPDATE

Purpose
The MODIFY DIRECTRY (directory) command performs the following functions for
the directory database:
v Changes the ownership of APPN resources in the directory database. Logical
units are owned by control points. (Both end nodes and network nodes can be
control points.) End nodes are owned or served by network nodes. You can
specify a new end node or network node as the owner of a logical unit, or you
can specify a new network node as the owner of an end node. You can even
specify a new end node as the owner of an LU and a new network node as the
owner of that end node on a single command, in which case all of the logical
units under the end node also are associated with the new network node.
The information in the directory database is updated automatically when VTAM
receives new information about a resource. For example, if you specify a new
end node as the owner of an LU, and then VTAM finds that the LU has moved to
a different location, the database is updated with the LU’s new location.

Note: If you change the network node server for an LU, all the other LUs under
the same end node will also have their network node server changed.

You cannot change the resource type with this command. For example, you
cannot turn a network node into an end node. If the resource specified by
CPNAME or NETSRVR has a resource type that conflicts with the resource
specified by ID, the update fails and an error message is issued.

Chapter 2. VTAM Operator Commands 275

MODIFY DIRECTRY
The CPNAME and NETSRVR operands can specify the same resource name.
For example, a logical unit can be owned by a network node, in which case the
network node serves as both the control point and the network node server for
the logical unit.
v Deletes resources from the directory database.

This command has no effect on corresponding CDRSC major nodes or minor nodes
that have the same name as the resource specified by the ID operand. That is, the
directory representation of the resource is changed, but the subarea representation
of the resource is not changed.

This command is valid only when it is issued at a network node or an interchange

node.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CPNAME
specifies the new owning control point for the resource or resources named in
the ID operand and the old owner that it replaces. The CPNAME operand is
valid only when FUNCTION=UPDATE is specified. The owning CP can be
either a network node or an end node.

You can specify network-qualified names on the CPNAME operand. If you do

not, the host’s network ID will be used as the network qualifier.
CPNAME=new_cp_name
specifies the name of the new control point that owns the resources.
CPNAME=(new_cp_name,old_cp_name)
specifies the name of the control point that previously owned the resources,
as well as the new owning control point. If old_cp_name is specified, only
those resources whose owning control point matches old_cp_name are
changed. If old_cp_name is not specified, the owning control point name for
the specified resources is changed to new_cp_name, regardless of the
previous value.
FUNCTION
specifies the function to be performed by this command. The FUNCTION
operand is required.
FUNCTION=UPDATE
updates the database to reflect a new owning end node (CPNAME), or
network node (NETSRVR), or both for the resource named in the ID
operand.
FUNCTION=DELETE
deletes the resource named in the ID operand from the directory database.
If ID specifies the name of a CDRSC major node, this command deletes the
directory representation of each minor node that was predefined with a
CPNAME in the major node.

276 SNA Operation

 MODIFY DIRECTRY
ID=resource_name
specifies the name of the resource (either an individual APPN resource or a
CDRSC major node) that is to be updated or deleted.

If the resource is a CDRSC major node, this command affects the directory
representation of each minor node that was predefined with a CPNAME in the
major node. For example, you could enter:
F procname,DIRECTRY,UPDATE,ID=CDRSC2A,CPNAME=SSCP2A

where CDRSC2A is the name of a CDRSC major node which contains several
resources that are now owned by control point SSCP2A.

The name specified on CPNAME or NETSRVR cannot match the name

specified on ID, unless ID is a major node. If ID is a major node, then the name
specfied for ID can match the name specified for CPNAME or NETSRVR;
however, if there is a minor node with the same name as the major node, the
update will fail for that minor node.

If the resource specified on the ID operand is not found in the database, an

error message is issued.

You can specify a network-qualified name on the ID operand. If you do not, the
host’s network ID is used as the network qualifier.
NETSRVR=server_name
specifies the new network node server for the resource or resources named in
the ID operand. The NETSRVR operand is valid only when
FUNCTION=UPDATE is specified.

You can specify a network-qualified name on the NETSRVR operand. If you do

not, the host’s network ID is used as the network qualifier.

Chapter 2. VTAM Operator Commands 277

MODIFY DR

MODIFY DR Command
Delete a logical unit from a physical unit, or a physical unit from a line:

ÊÊ MODIFY procname,DR ,TYPE=DELETE ,ID=lu_name,FROM=pu_name ÊÍ

,ID=pu_name,FROM=line_name

Move a physical unit:

ÊÊ MODIFY procname,DR ,TYPE=MOVE ,ID=pu_name ,FROM=line_name Ê

,ACTIVATE=NO
Ê ,TO=line_name ÊÍ
,ACTIVATE= NO ,ADDR=link_station_address
YES

Abbreviations
Operand Abbreviation
MODIFY F
ACTIVATE=NO ACT=NO
ACTIVATE=YES ACT=YES

Purpose
The MODIFY DR (dynamic reconfiguration) command dynamically reconfigures an
NCP or a local peripheral node. You can use this command to delete or move type
1, 2, and 2.1 PUs along with their associated LUs, or to delete LUs.

See the OS/390 eNetwork Communications Server: SNA Network Implementation

Guide for information about dynamically reconfiguring VTAM peripheral nodes and
for information about dynamic NCP reconfiguration.

The MODIFY DR command cannot dynamically add a physical unit or logical unit.
To add a physical or logical unit, use the VARY DRDS command with a DR file or
use the VARY ACT command with the UPDATE operand. Note that you can also
use the VARY DRDS command or the VARY ACT command with the UPDATE
operand to perform the same functions as the MODIFY DR command.

Note: See the “MODIFY ALSLIST Command” on page 251 for information about
how to update the list of PUs (adjacent link stations) associated with an
independent LU.

Dynamic reconfiguration for an NCP:

For an NCP, this command performs the following functions without regenerating
the NCP:
v Moves a nonswitched PU and its subordinate LUs from one line to another
v Changes a nonswitched PU link station address
v Deletes a nonswitched PU and its subordinate LUs from a line

278 SNA Operation

 MODIFY DR
v Deletes an LU from a nonswitched PU
v Deletes a type 2.1 PU on an NCP ESCON* channel
v Deletes an independent LU on an NCP ESCON channel
v Deletes frame relay type 1 PUs.

An NCP must be active and must be capable of dynamic reconfiguration before it

can be dynamically reconfigured. The active and inactive requirements for the
reconfiguration operations are shown in Table 2 and Table 3 on page 280 .
Table 2. Active and Inactive Status Requirements for MODIFY DR for an NCP
Operation/ Resource Major Node LINE PU LU
Delete PU Active Either Inactive Inactive
Delete LU Active Either Either Inactive
Move PU Active Either Inactive Inactive

In order to modify a frame relay switching equipment set (FRSESET), you need to
know whether the FRSESET was statically or dynamically defined. If you are not
sure, you can issue a DISPLAY NET,ID=frseset_name command to find out.
Statically means that the FRSESET was included in the NCP generation.
Dynamically means that the FRSESET was not included in the NCP generation.
Statically and dynamically defined PUs cannot be specified in the same FRSESET;
the PUs must be all static or all dynamic.

If the FRSESET was dynamically defined, you can dynamically add and delete PUs
from the set. You can delete PUs with the MODIFY DR, VARY DRDS, or VARY
ACT,UPDATE=ALL commands. You can add PUs only with the VARY
ACT,UPDATE=ADD or VARY ACT,UPDATE=ALL command.

If the FRSESET was statically defined, you can delete PUs from the set, but you
cannot add PUs. In practical terms, this means you need to delete the entire
FRSESET and then add it back dynamically in order to make changes. For
example, if you have a statically defined FRSESET containing two primary PUs and
you want to add two backup PUs, follow these steps:
1. Delete the two primary PUs, thereby deleting the FRSESET itself (because it is
empty).
2. Edit the VTAMLST source file to add the PU definitions for the backup PUs and
add the backup PUs to the FRSESET.
3. Use the VARY ACT command with UPDATE=ADD or UPDATE=ALL. The VARY
ACT command causes the FRSESET to be dynamically defined.

If you delete one or more PUs (using MODIFY DR or VARY DRDS) from a statically
defined FRSESET without deleting the whole FRSESET, VARY ACT will cause the
deleted PUs to be added back, but they will not be part of the FRSESET.

The first PU under a frame relay line (the LMI) cannot be deleted and it cannot be
part of a FRSESET.

For more information on how to define frame relay lines, frame relay PUs, and
FRSESETs, see the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference.

Dynamic reconfiguration for local peripheral nodes:

Chapter 2. VTAM Operator Commands 279

MODIFY DR
For a VTAM local peripheral node, this command performs the following functions:
v Deletes a logical unit from a VTAM nonswitched peripheral node. This is possible
only for local SNA major nodes. The MODIFY DR command cannot move
resources in a VTAM peripheral node, and it cannot delete physical units or lines
in a VTAM peripheral node.
v Removes a PU from an independent LU’s adjacent link station list.

Note: You cannot use MODIFY DR to move an independent LU.

Table 3. Active and Inactive Status Requirements for MODIFY DR for Local Peripheral Nodes
Operation/ Resource Major Node LINE PU LU
Delete LU N/A Either Either Inactive

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ACTIVATE
applies only if TYPE=MOVE. It specifies whether the physical unit and its
associated logical units are activated automatically after a successful move.
ACTIVATE=YES
VTAM activates the physical unit and its associated logical units after the
move completes successfully. This is equivalent to entering VARY
ACT,ID=pu_name,SCOPE=ONLY after the MODIFY
DR,ID=pu_name,TYPE=MOVE command has successfully completed.
Notes:
1. If the line to which the PU is being moved is inactive before the move,
ACTIVATE=YES does not activate the line.
2. If the system programmer has defined the initial status of a logical unit
subordinate to the moved physical unit (ISTATUS) as inactive,
ACTIVATE=YES does not activate the logical unit. The logical unit must
be explicitly activated.
3. If the line to which the PU is being moved is active, and the PU’s
ISTATUS is active, the PU and associated LUs are activated even if
ACTIVATE=YES is not specified.
ACTIVATE=NO
VTAM does not activate the physical unit and its associated logical units
after the move completes.
ADDR=link_station_address
applies only if TYPE=MOVE. It specifies the physical unit’s link station address.
Using this operand, you can change the physical unit’s link station address.

To change the address, use both the TO and FROM operands. The address
value must be a 2-digit hexadecimal number that is unique for each physical
unit on the same line.

280 SNA Operation

 MODIFY DR
You can use the ADDR operand to change a physical unit’s SDLC link station
address regardless of whether the physical unit is being moved to a new line. (It
is acceptable to code the same line on the TO and FROM operands associated
with a TYPE=MOVE command.)

If you use the ADDR operand to assign link station addresses, be careful when
using an address that a resource previously used. NCP is not informed of
dynamic moves or additions until the resource is activated; therefore, activate
resources in the order in which the dynamic reconfiguration requests were
made.
FROM
specifies the line name or physical unit in the dynamic reconfiguration.
FROM=line_name
If TYPE=MOVE, identifies the line from which the physical unit and its
subordinate LUs are to be moved.

If TYPE=DELETE, identifies the name of the line from which the physical
unit and all associated logical units are to be deleted.

The line must be nonswitched. The line can be active or inactive.

FROM=pu_name
identifies the physical unit from which the logical units identified in the ID
operand are to be deleted. The physical unit must be nonswitched.

If ID specifies an independent logical unit, the logical unit must not have
any session over the physical unit (adjacent link station) named in the
FROM operand.
ID specifies the physical unit or logical unit in the dynamic reconfiguration. When
TYPE=DELETE is specified, the name can be a network-qualified name.
ID=pu_name
identifies the physical unit to be deleted or moved (as specified in the TYPE
operand) and its associated logical units. The physical unit must be inactive
and nonswitched.
ID=lu_name
applies only if TYPE=DELETE. It identifies the logical unit to be deleted.
The logical unit must be inactive and under a nonswitched physical unit. If
the specified logical unit is an independent LU, it must not have any
session over the physical unit (adjacent link station) specified in the FROM
operand.
TO=line_name
applies only if TYPE=MOVE. It identifies the line to which the physical unit and
its associated logical units are to be moved. The line must be attached to the
same NCP as the physical unit and be nonswitched. The line can be active or
inactive.

This operand is required with TYPE=MOVE.

TYPE
specifies the type of dynamic reconfiguration to be performed.

The MODIFY DR command is valid only for nonswitched PUs and LUs and type
2.1 PUs on ESCON channels. MODIFY DR is not supported for cross-domain

Chapter 2. VTAM Operator Commands 281

MODIFY DR
resources. You cannot move or delete a PU that has PUDR=NO coded in its
NCP definition, and you cannot delete a dependent LU that has LUDR=NO
coded in its NCP definition.

The MODIFY DR command can be used to delete PUs from an independent

LU’s adjacent link station list if the independent LU has no active sessions over
the PU; however, the MODIFY ALSLIST command is recommended for adding
and deleting PUs from an adjacent link station list.
TYPE=MOVE
moves the physical unit identified in the ID operand, and all logical units
associated with the physical unit, from the line identified in the FROM
operand to the line identified in the TO operand. You can move a physical
unit from one line to another only if both lines are attached to the same
NCP.
TYPE=DELETE
deletes the physical unit identified in the ID operand and all logical units
associated with the physical unit from the line identified in the FROM
operand, or deletes the logical unit identified in the ID operand from its
physical unit identified in the FROM operand.

282 SNA Operation

 MODIFY DUMP

MODIFY DUMP Command

Static dump of remote NCP (via link station) to host:

ÊÊ MODIFY procname,DUMP ,ID=link_station_name ,DUMPDS=name Ê

,ACTION=COMP ,OPTION=STATIC ,RMPO=NO ,TYPE=NCP

Ê ÊÍ
,RMPO= NO
YES

Static dump of NCP to host:

,ACTION=COMP
ÊÊ MODIFY procname,DUMP ,ID=ncp_name Ê
,DUMPDS=name

,OPTION=STATIC ,RMPO=NO
Ê Ê
,DUMPSTA= ,RMPO= NO
link_station_name YES

,TYPE=NCP
Ê ÊÍ

Static dump of NCP to hard disk:

,OPTION=STATIC
ÊÊ MODIFY procname,DUMP ,ID=ncp_name ,ACTION=STORE ÊÍ

Dynamic dump of NCP to host:

,ACTION=COMP
ÊÊ MODIFY procname,DUMP ,ID=ncp_name ,OPTION=DYNA Ê

,TYPE=NCP
Ê ÊÍ
(1)
,DUMPDS=name

Notes:
1. If the NCP has been acquired before activation, DUMPDS is required.

Transfer CSP or MOSS dump from hard disk to host:

,ACTION=COMP
ÊÊ MODIFY procname,DUMP ,ID=ncp_name ,TYPE= CSP Ê
MOSS

Chapter 2. VTAM Operator Commands 283

MODIFY DUMP

Ê ÊÍ
(1)
,DUMPDS=name

Notes:
1. If the NCP has been acquired before activation, DUMPDS is required.

Transfer NCP, CSP, or MOSS dump from hard disk to host:

,TYPE=NCP
ÊÊ MODIFY procname,DUMP ,ID=ncp_name ,ACTION=TRANSFER Ê
,TYPE= CSP
MOSS
NCP

Ê ÊÍ
(1)
,DUMPDS=name

Notes:
1. If the NCP has been acquired before activation, DUMPDS is required.

Purge dump from hard disk:

,TYPE=NCP
ÊÊ MODIFY procname,DUMP ,ID=ncp_name ,ACTION=PURGE ÊÍ
,TYPE= CSP
MOSS
NCP

Abbreviations
Operand Abbreviation
MODIFY F
ACTION=TRANSFER ACTION=TRANS
DUMPDS DS
DUMPSTA DST
OPTION=DYNA OPT=DYNA or DYNA
OPTION=STATIC OPT=STATIC
RMPO=YES RMPO or RMPO=Y
RMPO=NO RMPO=N

The MODIFY DUMP (dump of an NCP) command is used to control NCP,

communication scanner processor (CSP), and maintenance and operator
subsystem (MOSS) dumps. Some functions use the IBM 3720 or 3745
Communication Controller’s hard disk. The functions that can be performed are:
v Dump the NCP from the communications control unit (CCU) to the host
v Dump the NCP from the CCU and store the dump on the hard disk
v Transfer an NCP, CSP, or MOSS dump from the hard disk to the host

284 SNA Operation

 MODIFY DUMP
v Purge an NCP, CSP, or MOSS dump from the hard disk.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ACTION
specifies what is to be done to the dump. ACTION=STORE requires NCP
Version 5 Release 3 or later.
ACTION=TRANSFER
VTAM stores the dump in a host data set, using SSP as the interface to the
dump data set.

If TYPE=CSP or TYPE=MOSS, VTAM transfers the CSP or MOSS dump

(taken automatically when the CSP or MOSS fails) from the controller’s
hard disk or diskette to the host. When the transfer is complete, MOSS
purges the dump from the controller’s hard disk.

If TYPE=NCP, VTAM transfers the dump from the IBM 3720 or the 3745
Communication Controller hard disk to the host. The dump is not purged.

ACTION=TRANSFER and TYPE=NCP are valid only if an NCP dump is on

the controller’s hard disk from a previous VARY ACT DUMPLOAD=YES
command or because DUMPLD=YES is coded on the PCCU definition
statement.
ACTION=PURGE
VTAM purges the dump from the disk.

If TYPE=CSP or TYPE=MOSS, VTAM purges the CSP or MOSS dump

(taken automatically when the CSP or MOSS fails) from the controller’s
hard disk.

If TYPE=NCP, VTAM purges an NCP dump previously stored on the IBM

3720 or 3745 Communication Controller hard disk. VTAM does not transfer
the dump to the host.

ACTION=PURGE and TYPE=NCP are valid only if an NCP dump is on the

controller’s hard disk from a previous VARY ACT DUMPLOAD=YES
command or because DUMPLD=YES is coded on the PCCU definition
statement.
ACTION=COMP
specifies the compatibility mode of operations for this command with
previous releases of VTAM.

If TYPE=CSP or TYPE=MOSS, VTAM transfers the CSP or MOSS dump

(taken automatically when the CSP or MOSS fails) from the controller’s
hard disk to the host.

Chapter 2. VTAM Operator Commands 285

MODIFY DUMP
If TYPE=NCP, VTAM dumps the NCP and stores the results at the host.
The type of NCP dump (static or dynamic) to be taken is specified on the
OPTION operand.
ACTION=STORE
VTAM causes the NCP to be dumped to the controller’s hard disk only if
DUMPLOAD=YES is specified on the VARY ACT command or
DUMPLD=YES is specified on the PCCU definition statement and the dump
slot for this CCU on the controller’s hard disk is empty. Use the DISPLAY
DISK command to see that these conditions are met. If either one of these
conditions is not met, a dump to disk will not take place and the NCP will
be deactivated.

Only OPTION=STATIC and ID=ncp_name are allowed if ACTION=STORE

is specified. No other operands are allowed.

ACTION=STORE requires NCP Version 5 Release 3 or later.

DUMPDS=name
identifies the file that is to contain this dump. The specified file should be large
enough to contain the dump. The contents of the file are overwritten by the
dump. name must be the data definition name on the DD statement that defines
the file to receive the dump.

If ID=link_station_name, this operand must be specified.

If ID=ncp_name, the DUMPDS operand (if specified) overrides any file

specification in the PCCU definition statement. If this operand is omitted, VTAM
uses the file specified in the PCCU definition statement. If the dump file is not
specified on either the MODIFY DUMP command or the PCCU definition
statement, the command fails.

If the NCP has been acquired before activation, the DUMPDS operand is
required for all non-static dump types including CSP, MOSS, and NCP dump
transfers and an NCP dynamic dump. VTAM does not allow static dumps of
NCPs that have been acquired before activation.
DUMPSTA=link_station_name
specifies the name of a link station (channel or SDLC link station within another
NCP) in a node adjacent to the NCP to be dumped, through which a static
dump operation is to be performed. The link station must be active at the time
of the dump. The VTAM-generated link station name (a 3-digit or 4-digit
hexadecimal channel unit address followed by -S) can be specified.

DUMPSTA applies only when all of the following conditions are met:
v ID=ncp_name is specified.
v OPTION=STATIC is specified (or assumed by default).
v TYPE=NCP is specified (or assumed by default).

If the DUMPSTA operand is specified, any previous DUMPSTA specifications

(from the VARY ACT command or from the NCP definition) are overridden for
this one dump operation. If a null value is specified (that is, if DUMPSTA= is
specified), VTAM selects an available link station, giving preference to a
channel link station over any SDLC link stations.

286 SNA Operation

 MODIFY DUMP
If the DUMPSTA operand is omitted, the current dump station name from the
VARY ACT command or from the NCP definition (in that order) is used. If the
current dump station name is null, VTAM selects an available link station as
described above.
ID specifies the NCP to be dumped or the link station through which a remote
NCP is to be dumped.
ID=ncp_name
specifies an active NCP
ID=link_station_name
specifies an SDLC link station within an NCP that is adjacent to the
communication controller containing the NCP to be dumped. The associated
SDLC link must be active. If ID=link_station_name is specified, the
DUMPDS operand is required, and the DUMPSTA and OPTION=DYNA
operands are not allowed.

Note: CSP and MOSS dumps cannot be taken by specifying a link station
name. Specify the NCP name to take CSP and MOSS dumps.
OPTION
provides additional specifications for an NCP dump. The OPTION operand
applies if TYPE=NCP is specified or assumed by default, and if ACTION=COMP
or ACTION=STORE.
OPTION=DYNA
applies only when the ID operand specifies the name of an active NCP.
OPTION=DYNA specifies that the NCP is to be dumped dynamically. That
is, NCP processing continues while the NCP’s contents are dumped. The
NCP is not deactivated. VTAM requests multiple storage images from the
NCP, and the resulting output reflects the storage contents of the
communication controller over the period required to complete the dump.

Note that the following two commands produce identical results:

F NET,DUMP,ID=ncp_name,DYNA

F NET,DUMP,ID=ncp_name,OPTION=DYNA
OPTION=STATIC
specifies that the NCP is to be dumped statically. That is, NCP processing
stops and the NCP is deactivated. The resulting output reflects the storage
contents of the communication controller at the time the dump was started.

When TYPE=NCP and OPTION=STATIC, VTAM checks for the availability

of the NCP dump data set. If this data set is not available, the command
fails and the NCP remains active.

When ACTION=STORE, issue the DISPLAY DISK command to determine

that the automatic dump switch in the controller is set on
(DUMPLOAD=YES on VARY ACT command or DUMPLD=YES on the
PCCU definition) and that the dump slot for this CCU on the controller’s
hard disk is empty. If either one of these conditions is not met, no dump to
disk will take place, and the NCP will be deactivated.
RMPO
specifies whether the communication controller containing the NCP is to be
powered off after a static dump and deactivation of the NCP.

Chapter 2. VTAM Operator Commands 287

MODIFY DUMP
RMPO=YES
specifies that the communication controller is to be powered off.
RMPO=YES is valid only for a static NCP dump (OPTION=STATIC is
specified or assumed by default). Also, RMPO=YES should be entered only
for an NCP that is in a communication controller with the remote power-off
facility.

Note that RMPO can be entered instead of RMPO=YES.

RMPO=NO
specifies that the communication controller is not to be powered off.
TYPE
specifies the type of dump.

If ACTION=TRANSFER and either TYPE=CSP or TYPE=MOSS, the box event

record (BER) log, configuration data file (CDF), token-ring interface coupler
(TIC) dump, and channel adapter (CA) dump are transferred automatically from
the hard disk with the CSP or MOSS dump. If the CSP or MOSS dump is not
present, the BER log, CDF, TIC dump, and CA dump are transferred; however,
after they are transferred, the MODIFY DUMP command will fail because the
specified dump is not present.
TYPE=CSP
if ACTION=TRANSFER or COMP, transfers a dump of the NCP’s
communication scanner processor (taken automatically when the CSP fails)
from the controller’s hard disk to the host data set using SSP as the
interface to the dump data set. From the host data set, it can be formatted
and printed.

The file to contain this dump can be specified by the operator with the
DUMPDS operand of the MODIFY DUMP command, or it can be specified
by the system programmer on the CDUMPDS operand of the PCCU
definition statement. If neither the DUMPDS operand nor the CDUMPDS
operand are specified, VTAM uses the dump file specified by the DUMPDS
operand of the PCCU definition statement.

If ACTION=PURGE, purges the CSP dump from the hard disk or diskette in
the controller.
TYPE=MOSS
if ACTION=TRANSFER or COMP, transfers a dump of the maintenance
operator subsystem (taken automatically when the MOSS fails) from hard
disk or diskette in the controller to the host data set using SSP as the
interface to the dump data set.

The file to contain this dump can be specified by the operator with the
DUMPDS operand of the MODIFY DUMP command, or it can be specified
by the system programmer on the MDUMPDS operand of the PCCU
definition statement. If neither the DUMPDS operand nor the MDUMPDS
operand are specified, VTAM uses the dump file specified by the DUMPDS
operand of the PCCU definition statement.

If ACTION=PURGE, purges the MOSS dump from the hard disk or diskette
in the controller.
TYPE=NCP
if ACTION=COMP, TYPE=NCP specifies a normal dump of the NCP. If

288 SNA Operation

 MODIFY DUMP
ACTION=TRANSFER, the resulting dump is sent to the host from the IBM
3720 or 3745 Communication Controller hard disk. If ACTION=PURGE, the
dump is purged from the IBM 3720 or 3745 Communication Controller hard
disk.

If ACTION=TRANSFER or PURGE, the OPTION operand does not apply. If

ACTION=TRANSFER, the host file to contain the transferred dump can be
specified by the operator with the DUMPDS operand of the MODIFY DUMP
command, or it can be specified by the system programmer on the
DUMPDS operand of the PCCU definition statement.

If TYPE=NCP and ACTION=COMP, the OPTION operand can be used to

specify whether this is to be a dynamic or static dump.

Chapter 2. VTAM Operator Commands 289

MODIFY ENCR

MODIFY ENCR Command

ÊÊ MODIFY procname,ENCR= COND ,ID=lu_name ÊÍ
OPT
REQD

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY ENCR (encryption) command allows you to change the cryptography
specifications for logical units. Logical units (application programs, independent
LUs, and device type logical units) can be defined as having one of several
cryptography specifications. These specifications define the cryptographic
capabilities or user session requirements involving the logical units and are
described in the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ENCR
specifies the new cryptography specifications of the logical unit. The level of the
cryptography specification can only be raised. Any attempt to lower the level is
rejected. The new level is effective for all future sessions involving the logical
unit; existing active or pending sessions are not affected.
ENCR=OPT
raises the level of the logical unit’s cryptography specification from no
cryptography to optional (capable of cryptography).
ENCR=COND
raises the level of the logical unit’s cryptography specification from no
cryptography or optional to required (that is, all user sessions must be
encrypted) if both sides support encryption. If the session partner does not
support encryption, the session does not fail; instead, a session is
established with no encryption of data.
ENCR=REQD
raises the level of the logical unit’s cryptography specification from no
cryptography or optional (or selective or conditional for application
programs) to required (that is, all user sessions must be encrypted).

290 SNA Operation

 MODIFY ENCR
ID=lu_name
specifies the name of the logical unit whose cryptography specification is to be
changed. The logical unit can be either an application program, a device-type
logical unit, or an independent LU.

The name can be a network-qualified name. It cannot be a USERVAR or

LUALIAS name. If the name specified on the ID operand is network-qualified,
this name is considered to be the real name of the resource. The name can be
an ACB name or an alias name, so long as it is not network-qualified.

Following is an example of an APPL major node definition to show how

application names can be network-qualified:
x APPL ACBNAME=y,...

In the above example, x (the application name) can always be

network-qualified. The value y (the ACB name) can be network-qualified only if
y is the same as x.

Note: If ID specifies the name of an LU 6.2 application program, you should

use the MODIFY ENCR command only when no sessions exist for logon
modes other than SNASVCMG. If sessions are active on logon modes
other than SNASVCMG, and you use the MODIFY ENCR command to
change the encryption level, any attempt to establish a new session with
these logon modes is rejected until all existing sessions on that mode
that use the previous encryption level have ended.

Chapter 2. VTAM Operator Commands 291

MODIFY EXIT

MODIFY EXIT Command

Activate or replace an exit routine:

ÊÊ MODIFY procname,EXIT ,OPTION= ACT Ê

REPL

Ê ,ID= ISTEXCDM ÊÍ
ISTEXCVR ,MODULE=module_name
ISTCMMND
,PARMS=character_string
ISTEXCAA
,PARMS=character_string
ISTEXCCS
,PARMS=character_string
ISTEXCGR
,PARMS=character_string
ISTEXCPM
,PARMS=character_string
ISTEXCSD
,PARMS=character_string
ISTEXCUV
,PARMS=character_string

Activate a multiple instance of ISTEXCPM:

ÊÊ MODIFY procname,EXIT ,OPTION=ACT ,ID=ISTEXCPM.instance_name Ê

Ê ÊÍ
,PARMS=character_string

Replace a multiple instance of ISTEXCPM:

ÊÊ MODIFY procname,EXIT ,OPTION=REPL ,ID=ISTEXCPM.instance_name Ê

Ê ÊÍ
,MODULE=module_name ,PARMS=character_string

Deactivate an exit routine:

ÊÊ MODIFY procname,EXIT ,OPTION= INACT Ê

FORCE

292 SNA Operation

 MODIFY EXIT
Ê ,ID= ISTEXCDM ÊÍ
ISTEXCVR
ISTCMMND
,PARMS=character_string
ISTEXCAA
,PARMS=character_string
ISTEXCCS
,PARMS=character_string
ISTEXCGR
,PARMS=character_string
ISTEXCPM
,PARMS=character_string
ISTEXCSD
,PARMS=character_string
ISTEXCUV
,PARMS=character_string

Deactivate a multiple instance of ISTEXCPM:

ÊÊ MODIFY procname,EXIT ,OPTION= INACT ,ID=ISTEXCPM.instance_name Ê

FORCE

Ê ÊÍ
,PARMS=character_string

Abbreviations
Operand Abbreviation
MODIFY F
MODULE MOD
OPTION OPT

Purpose
The MODIFY EXIT command enables you to activate, deactivate, or replace a
specified installation-wide exit. Using this command, you can modify the state of an
installation-wide exit that was loaded during initialization or activated, replaced, or
deactivated with an earlier MODIFY EXIT command.

Note: To modify an ISTEXCPM exit, the MODIFY EXIT command must be issued
from a program operator application (POA) program, unless
OPTION=FORCE is specified.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID specifies the installation-wide exit to be activated, deactivated, or replaced.

Chapter 2. VTAM Operator Commands 293

MODIFY EXIT
ID=exit_name
specifies the name of the installation-wide exit routine to be activated,
deactivated, or replaced.

For further information about valid installation-wide exit routines, see

OS/390 eNetwork Communications Server: SNA Customization.

Exit_name can be one of the following:

ISTEXCAA
Session management exit routine
ISTEXCCS
Configuration services XID exit routine
ISTEXCDM
Directory management exit routine
ISTEXCPM
Performance monitor exit routine

Note: Only a program operation application (POA) program can

issue the MODIFY EXIT command for ISTEXCPM, unless
OPTION=FORCE is specified.
ISTEXCSD
Selection of definitions for dependent logical units (SDDLU) exit
routine
ISTEXCVR
Virtual route selection exit routine
ISTCMMND
Command verification exit routine
ISTEXCGR
Generic resource resolution exit routine
ISTEXCUV
USERVAR exit routine
ID=ISTEXCPM.instance_name
specifies the instance of ISTEXCPM to be activated, deactivated, or
replaced. The instance_name is the name of the load module containing
the exit.

Note: Only a program operation application (POA) program can issue the
MODIFY EXIT command for ISTEXCPM.instance_name, unless
OPTION=FORCE is specified.

An instance_name being activated cannot have the same load module

name as one that is already active.
MODULE=module_name
specifies the load module name containing the exit to be activated, or the load
module name containing an alternate exit to replace an active exit.

module_name cannot have the same load module name as any other currently
active exit.

The MODULE operand is valid only with OPTION=ACT and OPTION=REPL.

294 SNA Operation

 MODIFY EXIT
Note: The MODULE operand is not valid when ID=ISTEXCPM.instance_name
and OPTION=ACT are both specified.
OPTION
specifies whether the installation-wide exit is to be activated, deactivated, or
replaced.
OPTION=ACT
specifies that the installation-wide exit is to be invoked where the
installation-wide exit routine is indicated within VTAM. The invocation points
cannot be modified.
OPTION=INACT
specifies that the installation-wide exit should not be invoked during VTAM
processing.
OPTION=REPL
specifies that the installation-wide exit should be replaced by the
installation-wide exit routine contained in the module named on the
MODULE operand during VTAM processing.
OPTION=FORCE
specifies that the installation-wide exit should be deactivated immediately.
The exit will not be driven for inactivation in this case.
Notes:
1. OPTION=FORCE should not be used in place of OPTION=INACT. Use
OPTION=FORCE only if a previous MODIFY EXIT,OPTION=INACT
command failed to deactivate the exit.
2. OPTION=FORCE is valid for use by a network operator and not by a
program operator application (POA) program.
PARMS=character_string
specifies a character string, 1–70 characters in length, that can be passed to an
installation-wide exit routine. You can use the PARMS operand to pass
user-specified data or control information to the following exit routines:
v ISTCMMND
v ISTEXCAA
v ISTEXCSS
v ISTEXCGR
v ISTEXCPM
v ISTEXCSD
v ISTEXCUV.

The PARMS operand is ignored for other exit routines or if OPT=FORCE is

specified.

See OS/390 eNetwork Communications Server: SNA Customization for more

information on how this data is passed to the exit routine.

Chapter 2. VTAM Operator Commands 295

MODIFY IMR

MODIFY IMR Command

Start intensive mode recording:

,OPTION=ACT
ÊÊ MODIFY procname,IMR ,ID= link_station_name Ê
pu_name

,RECLIM=10
Ê ÊÍ
,RECLIM=number_of_errors

Stop intensive mode recording:

ÊÊ MODIFY procname,IMR ,ID= link_station_name ,OPTION=INACT ÊÍ

pu_name

Abbreviations
Operand Abbreviation
MODIFY F
OPTION=ACT OPT=ACT
OPTION=INACT OPT=INACT

Purpose
The MODIFY IMR (intensive mode recording) command enables you to request that
an NCP provide detailed information concerning temporary line errors or other
hardware error conditions for a station on an SDLC link. IMR can be specified for a
peripheral physical unit of an NCP or for a cross-subarea link station within an NCP.
For more information on intensive mode recording, such as the reason for using it
and information on where the output is recorded, see OS/390 eNetwork
Communications Server: SNA Diagnosis.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID specifies the name of the resource for which IMR data is to be recorded.
ID=link_station_name
records IMR data for a link station.
ID=pu_name
records IMR data for a physical unit.

296 SNA Operation

 MODIFY IMR
OPTION
specifies whether IMR should be started or stopped for the named link station
or physical unit.
OPTION=ACT
specifies that IMR should be started for the named link station or physical
unit.
OPTION=INACT
specifies that ongoing intensive mode recording should be stopped, and
that the NCP is not to generate any more IMR records for the named link
station or physical unit.
RECLIM=number_of_errors
specifies the maximum number of temporary errors that are recorded for the
named link station or physical unit. When this limit is reached (or IMR is
canceled with OPTION=INACT), the NCP reverts to sending only permanent
error records to VTAM. Any decimal integer 1–65535 can be specified. The
default is 10. RECLIM is not applicable if OPT=INACT is specified.

Chapter 2. VTAM Operator Commands 297

MODIFY IOPD

MODIFY IOPD Command

ÊÊ MODIFY procname,IOPD ,IOINT=number_of_seconds ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
This command allows you to change the I/O problem determination (IOPD) time-out
interval. This interval determines how long certain VTAM I/O operations or internal
procedures can remain pending before VTAM reports them to the operator. You can
then decide whether a problem exists and what action, if any, is warranted.

See OS/390 eNetwork Communications Server: SNA Diagnosis for guidance on

setting the I/O problem determination time-out interval.

Note: You can use the “MODIFY VTAMOPTS Command” on page 385 (IOINT
operand) to perform the same function as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
IOINT=number_of_seconds
specifies the time-out interval (in seconds) for the I/O problem determination
function. The value must be a decimal integer 0–5366000. IOINT=0 specifies
that the I/O problem determination function is to be deactivated, meaning that
VTAM will not notify the operator of pending I/O operations or internal
procedures. IOINT is rounded up to the nearest 60-second multiple.

298 SNA Operation

 MODIFY IOPURGE

MODIFY IOPURGE Command

ÊÊ MODIFY procname,IOPURGE=timeout_value ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY IOPURGE (input/output purge) command allows you to set a time
interval after which outstanding I/O is assumed to be lost and recovery steps are
taken. The types of outstanding I/O that are examined are CDINIT requests, direct
search list requests, APPN search requests, and HPR route setup requests.

Prior to the availability of this function (or when IOPURGE is set to zero),
outstanding session requests could remain indefinitely. For example, when an
intermediate host that is used in session routing goes down, no response is
received to a session establishment request and the LU remains hung indefinitely.
By setting an IOPURGE value, you can, in effect, cancel session requests that fail
to complete in a certain amount of time. This frees the LU so you can request a
session using an alternate path.

It is recommended that you set an IOPURGE value of 3 minutes or more. In some

circumstances, for example logging on a remote LU via a slow modem, session
setup might take longer and the IOPURGE should be adjusted upward accordingly.
A good rule of thumb is to set the IOPURGE value for twice as long as session
setup usually takes. If you set IOPURGE too low, the session request is canceled
before a response can be received, and you will have to repeat the session
request.

Note: You can use the “MODIFY VTAMOPTS Command” on page 385 to perform
the same function as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
IOPURGE=timeout_value
specifies the time interval allowed to elapse before outstanding I/O is assumed
to be lost. When this time interval expires, recovery steps are taken. VTAM
supports this feature for CDINIT requests, direct search list requests, APPN
search requests, and HPR route setup requests.

The time interval can be specified in seconds, minutes, hours, or days. The
minimum value is 30 seconds. The maximum value is 7 days, or the equivalent

Chapter 2. VTAM Operator Commands 299

MODIFY IOPURGE
value in seconds, minutes, or hours. A value of 0 deactivates the IOPURGE
function. If you code a value from 1 to 30, VTAM sets IOPURGE to 30 seconds.

Note: To reduce potential performance strain, set IOPURGE greater than 2

minutes.
IOPURGE=n or IOPURGE=nS
specifies the number of seconds that can pass before a response is
assumed to be lost. By default, the time is assumed to be seconds, unless
M, H, or D is specified.
IOPURGE=nM
specifies the number of minutes that can pass before a response is
assumed to be lost.
IOPURGE=nH
specifies the number of hours that can pass before a response is assumed
to be lost.
IOPURGE=nD
specifies the number of days that can pass before a response is assumed
to be lost.

300 SNA Operation

 MODIFY LINEDEF

MODIFY LINEDEF Command

ÊÊ MODIFY procname,LINEDEF ,ID=line_name ,USE= DEFINED ÊÍ
SPARE

Abbreviations
Operand Abbreviation
MODIFY F
USE=DEFINED DEFINED
USE=SPARE SPARE

Purpose
The MODIFY LINEDEF command allows you to dynamically change the definition
of a redefinable line. A redefinable line is an SDLC line that has been defined in an
NCP major node with USE=REDEF or USE=SPARE. A redefinable line must be the
only line defined in the line group.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=name
specifies the name of an SDLC line defined in an NCP major node with the
USE=REDEF or USE=SPARE.
USE
specifies that the line identified on the ID operand is to be dynamically
redefined.
USE=DEFINED
specifies that the line identified on the ID operand is to become usable.
USE=SPARE
specifies that the line identified on the ID operand is to become a spare
line.

Chapter 2. VTAM Operator Commands 301

MODIFY LL2

MODIFY LL2 Command

Start a continuous link level 2 test:

ÊÊ MODIFY procname,LL2 ,ID=name ,OPTION=CONT Ê

,DATA=data

,NFRAMES=1
Ê ÊÍ
,NFRAMES=number_of_test_messages

Start a brief link level 2 test:

ÊÊ MODIFY procname,LL2 ,ID=name Ê

,DATA=data

,NFRAMES=1 ,NTRANS=10
Ê ÊÍ
,NFRAMES=number_of_test_messages ,NTRANS=number_of_test_messages

Stop a link level 2 test:

ÊÊ MODIFY procname,LL2 ,ID=name ,OPTION=CANCEL ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F
OPTION=CANCEL OPT=CANCEL or CANCEL
OPTION=CONT OPT=CONT or CONT

Purpose
The MODIFY LL2 command is used to request a link level 2 test for a nonswitched
SDLC link. This tests communication lines between the following:
v An NCP and a peripheral PU attached to it.
v Two NCPs (PU type 4).
v VTAM and a peripheral PU attached to it.
v An NCP and another VTAM (PU type 5). The command must be initiated from
the NCP’s domain, and the link station identified by the ID operand must be
inactive or inoperative.
v VTAM and another VTAM (PU type 5). The command must be initiated from the
VTAM with the highest subarea, and the link station identified by the ID operand
must be inactive or inoperative.

The test is performed by sending test data over the link from the primary end of the
line to the remote station; the data is then echoed back to the sender. The data
received is compared with the data sent. VTAM collects the results and displays

302 SNA Operation

 MODIFY LL2
these results in a message. For more information on when and how to run an LL2
test, see OS/390 eNetwork Communications Server: SNA Diagnosis.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
DATA=data
specifies optional user data to be used as part of the test message. Any
EBCDIC alphabetic, numeric, or special characters (such as @ # $) can be
specified. The maximum number of characters permitted depends on the
characteristics of the device at the receiving end of the test. If the DATA
operand is omitted, VTAM sends test messages without user data.

If DATA is specified and the physical unit returns the correct number of echoes
but does not return any data, the physical unit probably does not support echo
check with data. To determine whether a physical unit supports data, see the
component description for that physical unit.
ID=name
specifies:
v For a test of an SDLC link:
– Between two NCPs or
– Between an NCP and a host processor or
– Between two host processors

the name of a link station on the link that is to be tested. The specified link
station must be in the NCP or the host that is to initiate the test. The link
station at the originating end must be inactive.
v For a link to an SDLC peripheral node:
the name of a physical unit on the link that is to be tested. The SDLC link
must be active and the specified physical unit must be inactive, but, for a
multipoint link, the other physical units on the link can be active during the
test.

If there is a conflict between VTAM and the NCP about whether a resource has
been dynamically reconfigured, an informational message is displayed. This
could happen when an NCP is shared among VTAMs.

See OS/390 eNetwork Communications Server: SNA Diagnosis for additional

information on testing a nonswitched SDLC communication line.
NFRAMES=number_of_test_messages
specifies (for a multipoint line) the number of test messages to send to the
physical unit each time its station is selected. This option allows the test
messages to be interleaved with other data going to other stations on the line.
Specify any decimal integer 1–65535. The default is 1.

Chapter 2. VTAM Operator Commands 303

MODIFY LL2
NTRANS=number_of_test_messages
specifies the number of test messages to send. This number can be any
decimal integer 1–65535. (Specifying NTRANS=65535 gives the same result as
specifying OPTION=CONT.)

NTRANS must not be specified on the same command as the OPTION

operand. If neither NTRANS nor OPTION is specified, the default, NTRANS=10,
is used.
OPTION
specifies a test option to use instead of the NTRANS value. If OPTION is not
specified, the value in effect for NTRANS is used. OPTION must not be
specified on the same command with the NTRANS operand.
OPTION=CANCEL
specifies that the test running currently should be stopped.
OPTION=CONT
specifies that the test being started should run continuously until canceled
by the VTAM operator.

304 SNA Operation

 MODIFY LOAD

MODIFY LOAD Command

Store a load module on the hard disk, and optionally for a 3745, schedule an
IPL:

,ACTION=ADD
ÊÊ MODIFY procname,LOAD ,ID=ncp_name Ê

Ê Ê
,NOTIFY=60
,IPLTIME= (date,time)
,NOTIFY=
NO
time_period

Ê ÊÍ
,LOADMOD=load_module_name

Replace a load module on the hard disk, and optionally for a 3745, schedule
an IPL:

ÊÊ MODIFY procname,LOAD ,ID=ncp_name ,ACTION=REPLACE Ê

Ê Ê
,NOTIFY=60
,IPLTIME= (date,time)
,NOTIFY=
NO
time_period

Ê ÊÍ
,LOADMOD=load_module_name

Purge a load module from the hard disk:

ÊÊ MODIFY procname,LOAD ,ID=ncp_name ,ACTION=PURGE Ê

Ê ÊÍ
,LOADMOD=load_module_name

Cancel an ADD or REPLACE operation in progress:

ÊÊ MODIFY procname,LOAD ,ID=ncp_name ,ACTION=CANCEL Ê

Ê ÊÍ
,LOADMOD=load_module_name

Schedule or cancel an automatic IPL for an NCP load module in a 3745:

ÊÊ MODIFY procname,LOAD ,ID=ncp_name ,ACTION=SETTIME Ê

Chapter 2. VTAM Operator Commands 305

MODIFY LOAD
,NOTIFY=60
Ê ,IPLTIME= (date,time) Ê
,NOTIFY=
NO
time_period
CANCEL

Ê ÊÍ
,LOADMOD=load_module_name

Rename a load module on the 3745 hard disk for MOSS:

ÊÊ MODIFY procname,LOAD ,ID=ncp_name ,ACTION=RENAME Ê

Ê ,LOADMOD=load_module_name ,NEWNAME=new_load_module_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F
ACTION=ADD ACTION=A
ACTION=CANCEL ACTION=C
ACTION=PURGE ACTION=P
ACTION=RENAME ACTION=N
ACTION=REPLACE ACTION=R
ACTION=SETTIME ACTION=S
IPLTIME=CANCEL IPLT=C
IPLTIME=time IPLT=time
LOADMOD :c .LM
NEWNAME NEWN
NOTIFY=NO NT=NO
NOTIFY=time NT=time

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
IPLTIME=CANCEL, code only IPLT=C. Do not code IPLTIME=C.

Purpose
The MODIFY LOAD command is used to control NCP load module contents on IBM
3720 or 3745 Communication Controller hard disks. The actions that can be
performed are:
v Move a load module from the NCP library to the communication controller hard
disk.
v Replace a load module already on the communication controller hard disk.
v Purge a load module on the communication controller hard disk.
v Schedule a load module already on the IBM 3745 Communication Controller hard
disk for an automatic IPL, or cancel a scheduled IPL.

306 SNA Operation

 MODIFY LOAD
v Rename a load module already on the IBM 3745 Communication Controller hard
disk.

For additional information about using the timed IPL and automatic reloading
functions, see the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide.

Use the “DISPLAY DISK Command” on page 79 to examine the contents of the
communication controller hard disk.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ACTION
specifies the action to take on the load module specified by LOADMOD. See
Table 4 on page 308 for additional information about scheduling or cancelling
IPL, or adding, purging, moving or replacing a load module.
ACTION=ADD
requests that the load module specified by LOADMOD be stored on the
communication controller’s hard disk. The name specified by LOADMOD
cannot be the same name as a load module already on the disk. If the load
module to be added is already on the controller hard disk, the command is
rejected. (If you do not specify LOADMOD, it defaults to the NCP name
specified on the ID operand.)

The 3720 disk holds a maximum of two load modules. The IBM 3745
Communication Controller’s hard disk holds a maximum of two load
modules per CCU. If you request an ADD of a load module and the
maximum number of load modules are on the disk, the request will be
rejected. You then have two options:
v Replace one or both of the load modules already on the disk using the
ACTION=REPLACE option.
v Purge one or all of the load modules already on the disk using the
ACTION=PURGE option, and then add the module or modules desired
with the ACTION=ADD option.

Chapter 2. VTAM Operator Commands 307

MODIFY LOAD
Table 4. Relationship between ACTION and IPLTIME Operands
IPLTIME=time IPLTIME=CANCEL IPLTIME not
specified
ACTION=ADD Requests that the This is an incorrect V NET,ACT,
load module be specification. LOADFROM=EXT
Requests that the load scheduled for IPL can be used to
module specified by at the specified load the load
LOADMOD be placed on the time on the module into the
hard disk. If the load module IPLTIME operand. CCU.
to be added is already on the
hard disk or if the load
module slots are already full,
the request is rejected.
ACTION=REPLACE Requests that the This is an incorrect V NET,ACT,
load module be specification. LOADFROM=EXT
Requests that the load scheduled for IPL can be used to
module specified by at the specified load the load
LOADMOD replace a load time on the module into the
module of the same name IPLTIME operand. CCU.
already on the hard disk. If a
load module with the name If a scheduled IPL
specified is not on the hard is outstanding for
disk, VTAM attempts an ADD the load module to
of the load module. The rules be replaced, the
for a successful ADD then scheduled IPL is
apply to the REPLACE canceled.
option.
ACTION=SETTIME Requests that the Requests the This is an incorrect
load module be scheduled IPL for specification.
Requests that the load scheduled for IPL the load module be
module specified by (or changes a canceled. The load
LOADMOD, already existing scheduled IPL) at module is not
on the hard disk, be the specified time purged from the
scheduled for an automatic on the IPLTIME hard disk.
IPL or have a scheduled IPL operand.
canceled. The IPLTIME
operand is required.
ACTION=PURGE This is an incorrect This is an incorrect If a scheduled IPL
specification. specification. is outstanding for
Requests that the load the load module to
module specified by be purged, the
LOADMOD be purged from scheduled IPL is
the hard disk. If no load canceled.
module with the name
specified by LOADMOD is on
the hard disk, no action is
taken and the request is
rejected.

ACTION=REPLACE
requests that the load module specified by LOADMOD be replaced on the
communication controller’s hard disk. The name specified by LOADMOD
should have the same name as a load module already on the disk, but this
is not required. If a load module with the name specified is not on the disk,
VTAM attempts an ADD of the load module. The rules for a successful ADD
then apply to the REPLACE option.

You should be aware that the REPLACE option affects the automatic reload
of a load module if an NCP abends. If the load module being replaced is

308 SNA Operation

 MODIFY LOAD
the one tagged for automatic IPL by use of the DUMPLOAD operand on the
VARY ACT command or the DUMPLD operand on the PCCU definition
statement (that is, the load module to be reloaded if an NCP abend occurs),
it is no longer tagged for automatic IPL after the replace operation begins,
nor is the load module re-tagged for automatic IPL after the replace
operation completes.

If the load module being replaced is not the load module tagged for
automatic IPL, the automatic IPL tag is not affected during or after the
replace of the other load module.
ACTION=PURGE
requests that the load module and scheduled IPL (if applicable) specified by
LOADMOD be purged from the hard disk. Only one load module is purged
by this command. Issue a separate PURGE command for each load
module to be purged. If no load module with the name specified by
LOADMOD is on the disk, no action is taken and an error message is
issued.

Prior to issuing a subsequent MODIFY LOAD command of any type, wait

for the completion message of the purge request.

Note: ACTION=PURGE is not valid with the IPLTIME or NOTIFY operands.

ACTION=CANCEL
requests that a nondisruptive MODIFY LOAD ACTION=ADD or REPLACE
option be canceled. The command cannot be disruptive, and must still be
executing in order to be canceled. This command does not reverse the
process if the process is finished executing. The load module name
specified for the CANCEL option must match the load module name
specified in the ADD or REPLACE option that is to be canceled.

Regardless of whether the specified load module was originally tagged for
automatic IPL, canceling an ADD or REPLACE option results in a PURGE
of the partial load module on the disk.

Note: ACTION=CANCEL is not valid with the IPLTIME or NOTIFY

operands.

A nondisruptive PURGE cannot be canceled with this command.

ACTION=SETTIME
requests that the load module specified by LOADMOD, which already exists
on the IBM 3745 Communication Controller hard disk, either be scheduled
for automatic IPL or have its scheduled IPL canceled. If you use SETTIME,
the IPLTIME operand is required.

See Table 4 on page 308 for additional information about scheduling IPL.

You can use the “DISPLAY DISK Command” on page 79 to display the
scheduled IPL time.
ACTION=RENAME
requests that the load module on the IBM 3745 Communication Controller
hard disk be renamed. This command changes the name MOSS associates
with a specified load module on the disk. The internal NCP names

Chapter 2. VTAM Operator Commands 309

MODIFY LOAD
(specified in the NCP generation definition) are not affected by this
command. If you use RENAME, both the LOADMOD and NEWNAME
operands are required.

Renaming a load module that already has a timed IPL set does not cancel
the scheduled IPL.
ID=ncp_name
specifies the name of an active NCP (as specified in the PUNAME operand of
the BUILD statement during NCP generation) that resides in the communication
controller whose associated hard disk is to be modified.
IPLTIME
specifies the scheduled IPL time or cancels an already existing scheduled IPL
from the hard disk into the CCU. This operand is valid with ACTION=SETTIME,
ADD, or REPLACE.

IPLTIME can be specified only when an IBM 3745 Communication Controller is

being used.

Each load module can have only one IPL time selected for it. Two load modules
on the same CCU cannot have estimated IPL times within 5 minutes of each
other.

If the time you specify as the IPL time is the same as the current system time,
MOSS does not IPL. See the “VARY ACT Command” on page 410 for
information about how to cause an immediate IPL.
IPLTIME=(date,time)
specifies the time of the scheduled IPL. The format of the date entered is
determined by the value specified on the DATEFORM start option. The valid
possible values for this operand are:
v DATEFORM=MDY (default); date format is mm/dd/yy. The delimiters can
be either slash (/) or dash (–).
v DATEFORM=DMY; date format is dd/mm/yy. The delimiters can be either
slash (/) or period (.).
v DATEFORM=YMD; date format is yy/mm/dd. The delimiters can be slash
(/), period (.), or dash (–).

For example, if DATEFORM=MDY is in effect, specify the IPL time in the

form IPLTIME=(mm/dd/yy,hh:mm).

If the year is omitted, the current year is used. The command is rejected if
the value entered for the date or time conflicts with any of the following
restrictions:
v Date or time is not valid
v Date or time is greater than 90 days from the current date or time. (If you
specify a time interval greater than 15 days, minor MOSS clock deviation
might occur.)
v Date or time is prior to current date or time.

The time hh:mm must be specified in military format (24-hour day) and is
time zone independent. See Table 5 on page 311 for examples of time
specifications.

310 SNA Operation

 MODIFY LOAD
Table 5. Examples of Time Specifications for IPLTIME
Difference in
time zones
Location of between the Time of
Location of 3745 for the operator and Time specified scheduled IPL
operator scheduled IPL 3745 in IPLTIME at 3745
Los Angeles New York + 3 hours 14:00 17:00
Paris London − 1 hour 13:00 12:00
Tokyo Tokyo 0 hours 23:00 23:00

IPLTIME=CANCEL
indicates that a scheduled IPL for the specified load module be canceled.
ACTION=SETTIME is required.
LOADMOD=load_module_name
specifies the name of the NCP load module. For ACTION=REPLACE or
PURGE, the load module on the disk does not have to be the load module
currently active in the communication controller.

For ACTION=ADD, ACTION=REPLACE, ACTION=PURGE, or

ACTION=SETTIME, the LOADMOD operand, when not coded, defaults to the
name specified for the ID operand. For ACTION=CANCEL, LOADMOD defaults
to the name of the load module currently being loaded, if a load is in progress.

For ACTION=RENAME, the LOADMOD operand is required.

For ACTION=ADD or ACTION=REPLACE, the load module specified must be

one of the load modules in the load library specified by the LOADLIB operand
of the BUILD definition statement for the active NCP.
NEWNAME=new_load_module_name
specifies the new name to be given to the load module specified by the
LOADMOD operand. If the new name is the same as the value already
specified in LOADMOD, the command is rejected.

NEWNAME can only be specified when an IBM 3745 Communication Controller

is being used. NEWNAME is valid and is required when ACTION=RENAME is
specified.
NOTIFY
specifies if and when an alert is to be sent prior to the expiration of the
scheduled IPL. NOTIFY is valid only when a time is specified in the IPLTIME
operand. NOTIFY can only be specified when an IBM 3745 Communication
Controller is being used.

An IPLTIME cannot be sooner than the NOTIFY time or the command fails. For
example, if NOTIFY is allowed to take the default time (60 minutes) an IPLTIME
of less than one hour away is not accepted.

Note: The alert is not displayed by VTAM; it is forwarded to the NetView*

program, where it can be displayed using the hardware monitor.
NOTIFY=mmm
indicates that an alert will be sent mmm minutes prior to expiration of the
scheduled IPL. The default time is 60 minutes. The maximum value is 999
minutes.

Chapter 2. VTAM Operator Commands 311

MODIFY LOAD
NOTIFY=(hh,mm)
indicates that an alert will be sent at time hh,mm prior to expiration of the
scheduled IPL. The maximum value is 99,99 (99 hours and 99 minutes).
NOTIFY=NO
indicates that no alert will be sent prior to the scheduled IPL.

312 SNA Operation

 MODIFY MSGMOD

MODIFY MSGMOD Command

ÊÊ MODIFY procname,MSGMOD= NO ÊÍ
YES

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY MSGMOD (message module) command enables you to specify
whether VTAM messages contain an identifier that indicates the VTAM module that
originated the message. MSGMOD=YES puts the last five characters of the name
of the issuing module immediately after the message identifier. This command
overrides the value that was used on the MSGMOD start option.

If the addition of this identifier causes the message text to exceed the maximum
allowable message length, the message is truncated on the right, with the possible
loss of information. The truncation of messages can be significant (for example,
when a display of buffer usage is requested). In this case, the truncated information
contains the expansion increment for each buffer pool.

Note: You can use the “MODIFY VTAMOPTS Command” on page 385 to perform
the same function as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
MSGMOD
specifies whether VTAM messages are to contain an issuing-module identifier.
MSGMOD=YES
causes VTAM messages to contain an issuing-module identifier.
MSGMOD=NO
causes VTAM messages to not contain an issuing-module identifier.

Chapter 2. VTAM Operator Commands 313

MODIFY NEGPOLL

MODIFY NEGPOLL Command

ÊÊ MODIFY procname,NEGPOLL=number_of_responses ,ID=line_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
Use this command to request that an NCP change the negative polling limit (the
maximum number of consecutive negative polling responses accepted before
polling another terminal on the line) for a nonswitched, multipoint line to one or
more attached start/stop or BSC terminals.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=line_name
specifies the name of a nonswitched multipoint line to one or more attached
start/stop or BSC terminals.
NEGPOLL=number_of_responses
specifies the negative polling limit as a decimal integer 1–255. This is the
maximum number of consecutive negative polling responses accepted before
polling another terminal on the line specified by the ID operand.

314 SNA Operation

 MODIFY NOTNSTAT

MODIFY NOTNSTAT Command

ÊÊ MODIFY procname,NOTNSTAT ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY NOTNSTAT (no tuning statistics) command enables you to stop the
recording of tuning statistics. Also see the “MODIFY TNSTAT Command” on
page 355 for more ways to control the recording of tuning statistics.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.

Chapter 2. VTAM Operator Commands 315

MODIFY NOTRACE

MODIFY NOTRACE Command

Stop a buffer contents trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=BUF ,ID=node_name Ê

,IDTYPE=RESOURCE ,SCOPE=ONLY
Ê ÊÍ
,IDTYPE= CP ,SCOPE= ONLY
SSCP ALL
RESOURCE

Stop a communication network management trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=CNM ,ID= PDPIUBUF ÊÍ

SAWBUF

Stop a user Exit buffer trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=EXIT ,ID=ISTEXCAA Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » ACCTING )
ADJSSCP
ALIAS
ALS
BEGIN
END
GWPATH
INITAUTH
REPL
SECAUTH
VRSEL
XRF

ÊÊ MODIFY procname,NOTRACE ,TYPE=EXIT ,ID=ISTEXCCS Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » BEGIN )
CONNSTAT
DYNABLD
XID
END

316 SNA Operation

 MODIFY NOTRACE
ÊÊ MODIFY procname,NOTRACE ,TYPE=EXIT ,ID=ISTEXCDM Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » BEGIN )
INITAUTH
BN_SEL
ADS_SEL
CDS_SEL
CRR_SEL
REPL
END

Stop a generalized PIU trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=GPT ,ID=node_name Ê

,IDTYPE=RESOURCE
Ê Ê
,IDTYPE= CP ,ALSNAME=adjacent_link_station_name
SSCP
RESOURCE

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
ALL

Stop an input/output trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=IO ,ID=node_name Ê

,IDTYPE=RESOURCE ,SCOPE=ONLY
Ê ÊÍ
,IDTYPE= CP ,SCOPE= ONLY
SSCP ALL
RESOURCE

Stop a module trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=MODULE Ê

Chapter 2. VTAM Operator Commands 317

MODIFY NOTRACE
Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » COMMAND )
CONNECTION
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
SESSION

Stop an NCP line trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=LINE ,ID=line_name ÊÍ

Stop a 3710 Network Controller line trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=NETCTLR ,ID=pu_name ,LINE=line_name Ê

Ê ,PU=3710_pu_name ÊÍ

Stop a scanner interface trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=SIT ,ID=line_name ÊÍ

Stop an SMS (buffer use) trace:

,ID=VTAMBUF
ÊÊ MODIFY procname,NOTRACE ,TYPE=SMS ÊÍ

Stop a resource state trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=STATE Ê

Ê ,ID=node_name Operands used with ID ÊÍ

,OPTION= ALL Operands used with OPTION
option
(option)
,

( » ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU

318 SNA Operation

 MODIFY NOTRACE
Operands used with ID

,IDTYPE=RESOURCE

,IDTYPE= CP ,OPTION= ALL

SSCP option
RESOURCE (option)
,

( » ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU

Operands used with OPTION

,IDTYPE=RESOURCE

,ID=node_name ,IDTYPE= CP
SSCP
RESOURCE

Stop a transmission group trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=TG ,ID=line_name ÊÍ

Stop a TSO user ID trace:

ÊÊ MODIFY procname,NOTRACE ,TYPE=TSO ,ID=tso_user_id ÊÍ

Stop a VTAM internal trace:

,MODE=INT
(1)
,MODE=EXT
ÊÊ MODIFY procname,NOTRACE ,TYPE=VTAM Ê
,MODE= INT
EXT

Chapter 2. VTAM Operator Commands 319

MODIFY NOTRACE

Ê ÊÍ
,OPTION= ALL
(2)
END
(3)
FORCE
option
(option)
,

( » API )
APPC
CFS
CIO
CMIP
CSM
ESC
HPR
LCS
LOCK
MSG
NRM
PIU
PSS
SMS
SSCP
TCP
VCNS
XBUF
XCF

Notes:
1. If you do not specify the mode, both internal and external recording are
stopped. However, any default options that you have stopped are immediately
restarted by VTAM and recorded on the internal trace table.
2. To stop external recording with OPTION=END, MODE=EXT must be explicitly
specified.
3. OPTION=FORCE is not valid when MODE=EXT is specified.

Abbreviations
Operand Abbreviation
MODIFY F
ALSNAME ALS
OPTION OPT
OPTION=COMMAND OPT=CMD
OPTION=CONNECTION OPT=CON
OPTION=DEFINITION OPT=DEF
OPTION=INTERFACES OPT=INT
OPTION=MANAGEMENT OPT=MGMT
OPTION=SESSION OPT=SES

320 SNA Operation

 MODIFY NOTRACE
Operand Abbreviation
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The MODIFY NOTRACE command stops a specified trace or deletes a trace
command that was saved previously with MODIFY TRACE,SAVE=YES. See
OS/390 eNetwork Communications Server: SNA Diagnosis for a more detailed
description of the VTAM trace facilities. See also the OS/390 eNetwork
Communications Server: SNA Resource Definition Reference and the “MODIFY
TRACE Command” on page 361.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ALSNAME=adjacent_link_station_name
applies only when TYPE=GPT. It specifies the name of the adjacent link station
through which you want to turn off traces. The adjacent link station name must
be a PU in an NCP major node or a switched PU connected by an NCP link.

The LU can be traced over multiple connections. To turn off tracing for multiple
connections, enter a separate command for each connection.

You do not need to specify the ALSNAME operand if either of the following is
true:
v The ALS list has only one entry (and it is not ISTAPNPU). That entry is
selected.
v The ALS list has two entries, one of which is ISTAPNPU. The entry other
than ISTAPNPU is selected.

The command fails if ISTAPNPU is specified, or if ISTAPNPU is used by default

because it is the only entry in the ALS list.

If no ALS list exists for the resource, specify the adjacent link station on the
ALSNAME operand.

Use the DISPLAY ID=lu_name,SCOPE=ALL command to display all sessions

for an independent LU and which adjacent link station list is used for each
session.
ID=name
specifies one of the following:

Chapter 2. VTAM Operator Commands 321

MODIFY NOTRACE
v When TYPE is BUF, IO, GPT, LINE, SIT, STATE, or TG, the ID operand
specifies the name of a node for which there is an active trace of the type
specified by the TYPE operand.
For TYPE=BUF, TYPE=IO, TYPE=GPT, or TYPE=STATE, the name can be a
network-qualified name. If name is an ACB name, and the ACB name
matches the name on the APPL definition statement, then you can use a
network-qualified ACB name.
For TYPE=BUF, TYPE=IO, or TYPE=STATE for a CDRM, you can specify a
network-qualified name, but this does not remove the restriction that the
non-network-qualified CDRM name must be unique across networks.
For TYPE=BUF, you can specify the name of the internal or external CMIP
application program. For the VTAM topology agent, node_name is
ISTTOPAG. For notification services, node_name is ISTNOTIF
v When TYPE is CNM, the ID operand specifies one of the following:
– PDPIUBUF, to stop the problem determination PIU buffer trace
– SAWBUF, to stop the session awareness buffer trace.
v When TYPE is EXIT, the ID operand is required and must be specified as
ISTEXCAA, ISTEXCCS or ISTEXCDM.
v When TYPE is MODULE, the ID operand does not apply.
v When TYPE is NETCTLR, the ID operand specifies the physical unit for
which the trace is to be stopped. (VTAM is not required to own or know
about the IBM 3710 Network Controller). VTAM sends the name of the
resource specified on the ID operand to the IBM 3710 Network Controller
specified on the PU operand.
v When TYPE is SMS, the ID operand is optional and, if specified, is always
VTAMBUF.
v When TYPE is TSO, the ID operand specifies the name of a TSO user ID for
which there is an active trace.
v When TYPE is VTAM, the ID operand does not apply.
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE identifies which resource the
command should act on. IDTYPE applies when TYPE=BUF, TYPE=IO,
TYPE=GPT, or TYPE=STATE.
IDTYPE=CP
stops tracing for the CP with the name specified on the ID operand. The
control point can be the host CP or a CDRSC representing an adjacent CP.
IDTYPE=SSCP
stops tracing for the SSCP with the name specified on the ID operand.
IDTYPE=RESOURCE
stops tracing for a CP, an SSCP, or another resource with the name
specified on the ID operand. If both an SSCP and a CP are found, VTAM
stops tracing for both of them.
LINE=line_name
applies only when TYPE=NETCTLR. It specifies the name of a link whose trace
is to be stopped. This link is attached to the IBM 3710 Network Controller
specified on the PU operand. VTAM has no knowledge of this link. VTAM sends
the name of the link specified on the LINE operand to the IBM 3710 Network
Controller specified on the PU operand.

322 SNA Operation

 MODIFY NOTRACE
MODE
applies only when TYPE=VTAM. It specifies whether to stop internal or external
trace recording.

If you do not specify MODE, the requested options are stopped both internally
and externally. However, if external tracing is active when the command is
issued, external tracing is restarted with the same number of external buffers.

If you turn off tracing for the default trace options, they will be immediately
restarted and recorded internally.

The default options are for internal tracing only. In effect, you cannot stop the
default options from running internally.
MODE=INT
stops internal trace recording for the specified options.
MODE=EXT
stops external trace recording for the specified options.

MODE=EXT is not valid when OPTION=FORCE is specified.

OPTION
applies to TYPE=EXIT, TYPE=MODULE, TYPE=STATE, and TYPE=VTAM.

For TYPE=EXIT, OPTION specifies the functions of the session management

exit (SME) for which tracing is to be stopped.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(BEGIN,INITAUTH,ACCTING).

For TYPE=MODULE, OPTION specifies the modules for which tracing is to be

stopped.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(COMMAND,SESSION).

For TYPE=STATE, OPTION specifies the types of resources for which resource
state tracing is to be stopped.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(APPL,GROUP,NCP).

For TYPE=VTAM, OPTION indicates the types of VTAM internal traces to be

stopped. For additional information on the OPTION operand, see the “MODIFY
TRACE Command” on page 361 and the OS/390 eNetwork Communications
Server: SNA Resource Definition Reference. For more information about VTAM
internal trace options, see the OS/390 eNetwork Communications Server: SNA
Diagnosis.

If TYPE=VTAM is specified and OPTION is omitted, VTAM issues messages

identifying the components for which the internal trace is active, without
stopping any active traces.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example, OPTION=(API,LOCK,SSCP).

Chapter 2. VTAM Operator Commands 323

MODIFY NOTRACE
The default VIT options are API, MSG, NRM, PIU, and SSCP. If you turn them
off, VTAM will restart them immediately.

The VTAM internal trace always runs with these options recorded internally. For
external recording, there are no default options.

Note: Although the default options are always active, these options do not
appear in DISPLAY TRACES output unless you have specified them on
the MODIFY TRACE command or the TRACE,TYPE=VTAM start option.
OPTION=ALL
applies to TYPE=EXIT, TYPE=MODULE, TYPE=STATE, and TYPE=VTAM.

For TYPE=EXIT, it stops the tracing of all functions of the session

management exit (SME).

For TYPE=MODULE, it stops the tracing of all modules.

For TYPE=STATE, it stops the tracing of all resource types except for those
started for a specific resource.

For TYPE=VTAM, it stops all of the internal trace options. Exception trace
entries continue to be recorded in the internal trace table. For MODE=INT,
OPTION=ALL stops internal recording for all options; however, the default
options are restarted immediately. For MODE=EXT, OPTION=ALL stops
external trace recording for all options. If you do not specify the MODE,
tracing is stopped both internally and externally, but the default options are
restarted immediately for MODE=INT.
OPTION=END
applies to TYPE=EXIT and TYPE=VTAM.

For TYPE=EXIT, it stops the tracing of the END function of the session
management exit (SME).

For TYPE=VTAM:
v If MODE is not specified, OPTION=END stops both internal and external
trace recording and frees the internal trace table (with consequent loss of
existing trace data if external recording is not being used). VTAM
immediately restarts the default trace options with MODE=INT and the
default trace table size.
v If MODE=INT is specified, OPTION=END stops internal trace recording
only and frees the internal trace table (with consequent loss of existing
trace data if external recording is not being used). VTAM immediately
restarts the default trace options with MODE=INT and the default trace
table size.
v If MODE=EXT is specified, OPTION=END stops external trace recording
only. To stop external recording with OPTION=END, MODE=EXT must
be explicitly specified.

For TYPE=EXIT, you can also specify the following options:

OPTION=ACCTING
stops tracing the initial and final accounting function of the session
management exit (SME).

324 SNA Operation

 MODIFY NOTRACE
OPTION=ADJSSCP
stops tracing the adjacent SSCP selection function of the session
management exit (SME).
OPTION=ALIAS
stops tracing the alias translation function of the session management exit
(SME).
OPTION=ALS
stops tracing the adjacent link station function of the session management
exit (SME).
OPTION=BEGIN
stops tracing the begin function of the session management exit (SME).
OPTION=GWPATH
stops tracing the gateway path list function of the session management exit
(SME).
OPTION=INITAUTH
stops tracing the initial authorization function of the session management
exit (SME).
OPTION=REPL
stops tracing the exit replacement function of the session management exit
(SME).
OPTION=SECAUTH
stops tracing the secondary authorization function of the session
management exit (SME).
OPTION=VRSEL
stops tracing the virtual route selection function of the session management
exit (SME).
OPTION=XRF
stops tracing the XRF session switch function of the session management
exit (SME).

For TYPE=MODULE, you can also specify the following options:

OPTION=COMMAND
stops tracing modules involved in command processing.
OPTION=CONNECTION
stops tracing modules involved in setting up connections between nodes.
OPTION=DEFINITION
stops tracing modules involved in resource definition processing.
OPTION=INTERFACES
stops tracing modules involved in the interface with the host SSCP or the
host CP.
OPTION=MANAGEMENT
stops tracing modules involved in network management.
OPTION=NOEXIT
specifies that module exits are to be traced for the modules associated with
all active OPTION values for TYPE=MODULE. Module exits are traced for
all modules until a subsequent MODIFY
TRACE,TYPE=MODULE,OPTION=NOEXIT command is issued.

Chapter 2. VTAM Operator Commands 325

MODIFY NOTRACE
Note: When a MODULE trace is started with OPTION=NOEXIT (either with
the TRACE start option or a MODIFY TRACE command), module
exits are not traced. Specifying OPTION=NOEXIT on the MODIFY
NOTRACE command resumes the tracing of the module exits.
OPTION=SESSION
stops tracing modules involved in session establishment.

For TYPE=STATE, you can also specify the following options:

OPTION=ADJCP
stops tracing the states of all adjacent control points.
OPTION=APPL
stops tracing the states of all application programs.
OPTION=CDRM
stops tracing the states of all CDRMs.
OPTION=CDRSC
stops tracing the states of all CDRSCs.
OPTION=GROUP
stops tracing the states of all line groups.
OPTION=LINE
stops tracing the states of all lines.
OPTION=LNKST
stops tracing of link stations.
OPTION=LU
stops tracing the states of all logical units.
OPTION=NCP
stops tracing the states of all NCPs.
OPTION=PU
stops tracing the states of all physical units.

For TYPE=VTAM, you can also specify the following options:

OPTION=API
stops tracing the application program interface.
OPTION=APPC
stops tracing LU 6.2 communication.
OPTION=CFS
stops tracing coupling facility services.
OPTION=CIO
stops tracing channel I/O for channel-attached devices and for lines
attached to a communication adapter.
OPTION=CMIP
stops tracing internal events in CMIP services and the VTAM topology
agent.
OPTION=CSM
stops tracing the communications storage manager.
OPTION=ESC
stops tracing the execution sequence control.

326 SNA Operation

 MODIFY NOTRACE
OPTION=HPR
stops tracing for HPR.
OPTION=LCS
stops tracing LAN channel stations.
OPTION=LOCK
stops tracing locks
OPTION=MSG
stops tracing messages.
OPTION=NRM
stops tracing network resource management.
OPTION=PIU
stops tracing path information units.
OPTION=PSS
stops tracing process scheduling services.
OPTION=SMS
stops tracing storage management services.
OPTION=SSCP
stops tracing the system services control point.
OPTION=TCP
stops tracing the VTAM to TCP/IP interface events. This option is used only
with the AnyNet function.
OPTION=VCNS
stops tracing VTAM common network services.
OPTION=XBUF
stops tracing of extended buffer list information.
OPTION=XCF
stops tracing XCF communication.
OPTION=FORCE
stops trace recording if it apppears that a previous MODIFY
NOTRACE,OPT=ALL or END command did not complete. Use
OPTION=FORCE only if your attempt to use OPTION=END appears to
have failed. VTAM immediately restarts the default trace options with
MODE=INT and the default trace table size.

Note: OPTION=FORCE may cause ABENDs for applications that are in a

hung condition.

OPTION=FORCE is not valid when MODE=EXT is specified. If

OPTION=FORCE is specified without the MODE operand, external tracing
is stopped and all external buffers are freed.
PU=3710_pu_name
applies only when TYPE=NETCTLR. It specifies the 3710 physical unit
performing the trace to be stopped. VTAM rejects the command if the physical
unit is not active to this VTAM (SSCP).
SCOPE
specifies the scope of the trace. It applies when TYPE=BUF or TYPE=IO. You

Chapter 2. VTAM Operator Commands 327

MODIFY NOTRACE
can also specify the SCOPE operand for TYPE=GPT, but it is meaningful only
for the NCP node. SCOPE=ALL is assumed for a GPT trace of all other node
types.
SCOPE=ALL
stops traces for any nodes subordinate to the node specified. SCOPE=ALL
is not valid for the host PU trace or for the host intermediate routing node
trace (ID=ISTIRN). If SCOPE=ALL is specified, VTAM issues a message
and uses SCOPE=ONLY instead.
SCOPE=ONLY
stops a trace only for the specified node.
TYPE
specifies the kind of trace that is to be stopped. Each trace must be stopped
with a separate MODIFY NOTRACE command.
TYPE=BUF
stops the tracing of text that passes through VTAM buffers on the way to or
from the node indicated by the ID operand. The SCOPE=ALL operand can
be used to extend the scope of the trace to all nodes subordinate to the
specified node.
TYPE=CNM
stops a communication network management trace.
TYPE=EXIT
stops the tracing of functions of the session management exit (SME).
TYPE=GPT
stops an NCP generalized PIU trace for the resources specified by the ID
operand.

Note: The ID operand of MODIFY NOTRACE cannot specify:

v An NCP switched line that is a switched subarea connection
v A dynamic CDRSC.
TYPE=IO
stops a trace of I/O activity associated with the node specified on the ID
operand. The SCOPE=ALL operand can be used to extend the scope of the
trace to all nodes subordinate to the specified node. Also, for an NCP major
node with an active channel attachment, the SCOPE=ALL operand
terminates any active channel I/O trace.

Note: The external VIT is now used to record the IO trace entries. The
previously used IO trace is no longer available. PIU, NLPI, NLPO,
LSNA, and MPTNFMT entries may be written for a specific IO trace
invocation. When the last IO trace is terminated, the external VIT
remains active. You must explicitly turn the VIT off.
TYPE=LINE
stops an NCP line trace for the line specified by the ID operand. Note that
specifying TYPE=LINE stops any transmission group trace that was started
using the same line name.
TYPE=MODULE
stops module tracing for the options specified on the OPTION operand.
TYPE=NETCTLR
stops the IBM 3710 Network Controller line trace for the physical unit
named on the PU operand.

328 SNA Operation

 MODIFY NOTRACE
TYPE=SIT
stops a scanner interface trace (SIT) of the communication scanner
processor in the IBM 3720 or 3745 Communication Controller.
TYPE=SMS
stops a storage management services (SMS) trace that is recording VTAM
buffer pool usage data.
TYPE=STATE
stops resource state tracing. If the ID operand is specified, state tracing is
stopped for that resource only. If the OPTION operand is specified, state
tracing is stopped for those resource types specified.
TYPE=TG
stops an NCP transmission group trace for the transmission group
containing the line specified by the ID operand.
TYPE=TSO
stops a TSO component trace for the user ID specified by the ID operand.
TYPE=VTAM
stops the VTAM internal trace (VIT) for the components specified by the
OPTION operand. If OPTION is omitted, no internal traces are stopped;
rather, VTAM issues messages identifying the components for which the
internal trace is currently active.

Chapter 2. VTAM Operator Commands 329

MODIFY POLL

MODIFY POLL Command

ÊÊ MODIFY procname,POLL=number_of_seconds ,ID=line_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
You can use this command to request that an NCP change the polling delay (the
time delay between polling sequences) for a nonswitched, polled line to one or
more attached BSC IBM 3270 terminals.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=line_name
specifies the name of a nonswitched, polled line to one or more attached BSC
IBM 3270 terminals.
POLL=number_of_seconds
specifies the polling delay in seconds. This is the time delay between polling
sequences on the line specified by the ID operand. Specify the number of
seconds as an integer in the range 0–255.

330 SNA Operation

 MODIFY PPOLOG

MODIFY PPOLOG Command

ÊÊ MODIFY procname,PPOLOG= YES ÊÍ
NO

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
Use the MODIFY PPOLOG command to request that VTAM start or stop sending
copies of VTAM operator commands and VTAM messages to the primary program
operator (PPO).

If the PPOLOG option is in effect, messages that were suppressed by the MODIFY
SUPP command or the SUPP start option are still sent to the primary program
operator, even though those messages do not appear on the system console.

PPOLOG is supported by the NetView program. Use of this command requires the
system to have a primary program operator such as the NetView program, and
requires that the primary program operator can support the option.

Note: You can use the “MODIFY VTAMOPTS Command” on page 385 to perform
the same function as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
PPOLOG
specifies whether to send copies of VTAM operator commands and messages
to the PPO for logging.
PPOLOG=YES
sends copies of all VTAM operator commands received from the system
console, and copies of all VTAM messages that have been written to the
system console.
PPOLOG=NO
stops sending copies of all VTAM operator commands received from the
system console, and copies of all VTAM messages that have been written
to the system console.

Chapter 2. VTAM Operator Commands 331

MODIFY PROFILES

MODIFY PROFILES Command

ÊÊ MODIFY procname,PROFILES ,ID=appl_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY PROFILES command refreshes an active application’s set of RACF*
profiles. This command updates the profiles in storage to reflect changes made by
the security administrator to the RACF profiles.

Note: The profile changes affect only those sessions that are started after the
command is executed. Active sessions are not affected. Pending sessions
might be terminated if the profile or the LU-LU password is deleted or
changed for a partner LU. To prevent such an error, it is recommended that
this command not be invoked if any active or pending sessions between the
application program and its partner LUs would be affected by a profile
change. See the OS/390 eNetwork Communications Server: SNA
Programmers LU 6.2 Guide for more information on LU 6.2 application
program security.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=appl_name
specifies the name of an active application that has VERIFY=OPTIONAL or
VERIFY=REQUIRED specified on its APPL statement. This operand is required.

332 SNA Operation

 MODIFY QUERY

MODIFY QUERY Command

Abbreviations
The MODIFY QUERY command can be issued only from a program operator
application.

The MODIFY QUERY command allows a program operator application to

communicate with a tuning facility such as the NTune* program. For more
information about this command, refer to OS/390 eNetwork Communications
Server: SNA Programming.

Chapter 2. VTAM Operator Commands 333

MODIFY RESOURCE

MODIFY RESOURCE Command

Modify the DLOGMOD value for a resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,DLOGMOD= ÊÍ

logon_mode_name

Add or change the ADJLIST value for a cross-domain resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,ADJLIST=list_name Ê

Ê ,ACTION=UPDATE ÊÍ

Delete the ADJLIST value for a cross-domain resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,ADJLIST=list_name Ê

Ê ,ACTION=DELETE ÊÍ

Change the delay timer for disconnection of a switched PU:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,DISCNTIM=time_period ÊÍ

Change the number of search requests for a resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name Ê

Ê ,SRCOUNT=number_of_search_requests ÊÍ

Change the value of the search reduction timer for a resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,SRTIMER=number_of_seconds ÊÍ

Reset the search reduction entry for a resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,SRCLEAR=YES ÊÍ

Modify the registration value for a resource:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,REGISTER= CDSERVR ÊÍ

NETSRVR
NO

Modify the ASRCVLM value for an application program:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,ASRCVLM=amount_of_storage ÊÍ

334 SNA Operation

 MODIFY RESOURCE
Modify the MODSRCH value for a model application program:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,MODSRCH= FIRST ÊÍ

LAST
NEVER

Modify the VTAMTOPO value for a reporting status:

ÊÊ MODIFY procname,RESOURCE ,ID=resource_name ,VTAMTOPO= REPORT ÊÍ

NOREPORT
NOLLINES
NOSWPUS
INCLUDE
IGNORE

Abbreviations
Operand Abbreviation
MODIFY F
DLOGMOD DLOG

Purpose
The MODIFY RESOURCE command allows you to perform the following changes
for an individual resource:
v Change the current value of the DLOGMOD operand of a definition statement for
an LU, application program, or cross-domain resource without deactivating the
entire major node
v Modify the reporting status for a resource.
v Add, replace, or delete the current value of the ADJLIST operand of a definition
statement for a cross-domain resource
v Change the delay timer for disconnection of a switched PU
v Modify search reduction information for existing CDRSCs and APPN directory
entries
v Modify the registration value for a resource
v Change the current value of the ASRCVLM operand coded on the APPL
definition statement.
v Change the current value of the MODSRCH operand coded on the APPL
definition statement.

When VTAM receives the MODIFY RESOURCE command, it overlays the existing
value for the specified operand with the new value.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

Chapter 2. VTAM Operator Commands 335

MODIFY RESOURCE
If procname in the START command was startname, startname must be
specified for procname.
ACTION
specifies whether VTAM is to add, update, or delete the name of the adjacent
SSCP list for a cross-domain resource.

ACTION is only valid with the ADJLIST and ID operands.

ACTION=DELETE
deletes the name of the current adjacent CDRM list for the cross-domain
resource specified on the ID operand. Routing after the successful
completion of this command will not use ADJLISTs. Existing sessions are
not affected by this command.
ACTION=UPDATE
adds a name of an adjacent CDRM list or replaces the name of the current
adjacent CDRM list for the cross-domain resource specified on the ID
operand. Routing after the successful completion of this command will use
the specified list.
ADJLIST=list_name
specifies the value of the adjacent CDRM list for the cross-domain resource
specified on the ID operand. If ACTION=UPDATE, the list_name must match
the name on an ADJLIST definition statement for subsequent routing to be
successful.

ADJLIST is only valid with the ACTION and ID operands.

ASRCVLM
specifies an amount of the data space storage associated with this application
that is used by VTAM to calculate constrained and critical threshhold values for
the data space. These constrained and critical threshhold values affect the way
adaptive session pacing operates with session partners. High usage periods of
data space storage should be considered when setting this value.

The range is 0–99,999,999. If you specify 0, the amount of data space storage
used is 1,000,000 bytes.
DISCNTIM=time_period
specifies the amount of time that VTAM delays deactivation of the SSCP-PU
session when there are no outstanding LU-LU session requests.

You can specify the time in seconds (S). Specify the number of seconds as an
integer in the range 5–65535.

DISCNTIM is valid only for PU types 2 and 2.1 that have DISCNT=DELAY
specified on the PU definition statement.

DISCNTIM is only valid with the ID operand.

DLOGMOD=logon_mode_name
specifies the new value for the logon mode. If DLOGMOD is specified with a
null value (left blank), the predefined DLOGMOD value is deleted.

DLOGMOD is only valid with the ID operand

336 SNA Operation

 MODIFY RESOURCE
Note: If DLOGMOD is specified with an unknown logon mode, a warning
message is issued indicating that it is unknown and the change is
accepted.
ID=resource_name
specifies the name of the resource to which the command applies. If you
specify ADJLIST, the resource name must specify a cross-domain resource.

The name can be a network-qualified name. If the name specified on the ID

operand is network-qualified, this name is considered to be the real name of the
resource.

Note: If the resource name is a cross-network CDRSC which is defined with

NQNMODE=NQNAME (either by definition statement or start option), be
sure to use its network-qualified name on this command.
MODSRCH
specifies when the INQUIRE APPSTAT and INQUIRE STATUS
macroinstructions will search for a model application definition. The VTAM
containing the application that issued the INQUIRE first searches its tables for a
previously defined application. If one is not found, it searches for a model that
can satisfy the request.

Note: If you plan to use the TSO/VTAM BASENAME parameter, then you must
code MODSRCH=FIRST on the TSO application definition statement
which represents the subordinate TSO APPLs. For more information on
MODSRCH, refer to the “TSO/VTAM” section in the OS/390 eNetwork
Communications Server: SNA Network Implementation Guide.
MODSRCH=FIRST
specifies that VTAM search for a model definition before searching the
network for the specified name. For example, because the OPEN ACB
macroinstruction can use a model definition, you could specify
MODSRCH=FIRST for an application issuing INQUIRE APPSTAT to
determine if an OPEN ACB will follow.
MODSRCH=LAST
specifies that VTAM search for a model definition only if all other hosts in
the network report that the application was not found.
MODSRCH=NEVER
specifies that VTAM search only for the name specified on the INQUIRE
macroinstruction.
REGISTER
indicates that the registration value of the resource should be changed and a
registration request might be initiated. This command can only be issued from
the resource’s real or surrogate owner.
REGISTER=CDSERVR
specifies that the resource is to be registered to the network node server
and the central directory server (CDS).
REGISTER=NETSRVR
specifies that the resource is to be registered to its network node server
only. If the resource is currently registered to the central directory server,
the registration is not deleted.
REGISTER=NO
specifies that the resource should not be registered. If the resource is

Chapter 2. VTAM Operator Commands 337

MODIFY RESOURCE
currently registered to a network node server, a request to delete the
registration is sent to the network node server. If the resource is currently
registered to the central directory server, the registration is not deleted.
SRCLEAR=YES
specifies that the search reduction entry should be reset for this resource. This
operand does not affect the SRTIMER or SRCOUNT values for subsequent
entries. The resource is verified when the next request is received. If the
resource cannot be reached, a new search reduction entry is created.

SRCLEAR is only valid with the ID, SRCOUNT, and SRTIMER operands.
SRCOUNT=number_of_search_requests
specifies the new number of search requests that are limited due to a search
reduction entry before another search is attempted. The value for this operand
is 0–65535.

Note: This operand only applies to existing CDRSCs and APPN directory
entries.

SRCOUNT is only valid with the ID, SRCLEAR, and SRTIMER operands.
SRTIMER=number_of_seconds
specifies the new number of seconds that a search reduction entry limits
incoming search requests or session requests. The value for this operand is
0–65535.

Note: This operand only applies to existing CDRSCs and APPN directory
entries.

SRTIMER is only valid with the ID, SRCLEAR, and SRCOUNT operands.
VTAMTOPO
specifies the new reporting status for a resource. The following are the values
allowed for this operand.
VTAMTOPO=REPORT
specifies that the VTAM topology agent reports resources.
VTAMTOPO=NOREPORT
specifies that the VTAM topology agent does not report resources.
VTAMTOPO=NOLLINES
specifies that the VTAM topology agent does not report switched logical
lines.
VTAMTOPO=NOSWPUS
specifies that the VTAM topology agent does not report connected switched
PUs, except for those switched PUs which have VTAMTOPO=REPORT
explicitly coded or specified under the switched major node.
VTAMTOPO=INCLUDE
specifies that the VTAM topology agent reports all resources, regardless of
the reporting status of the subordinate resources.
VTAMTOPO=IGNORE
specifies that the VTAM topology agent does not report resources,
regardless of the reporting status of the subordinate resources.

338 SNA Operation

 MODIFY RTP

MODIFY RTP Command

ÊÊ MODIFY procname,RTP ,ID=rtp_pu_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY RTP command causes VTAM to search for a better high performance
routing (HPR) route, based on transmission group weight, between the two
endpoints of a rapid transport protocol (RTP) connection. If a better route is found,
the connection is switched to the better route.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=rtp_pu_name
specifies the name of a PU that represents a rapid transport protocol (RTP)
route. The PU name must begin with “CNR”. This operand is required.

Chapter 2. VTAM Operator Commands 339

MODIFY SECURITY

MODIFY SECURITY Command

Increase the cryptography specification for an LU:

ÊÊ MODIFY procname,SECURITY ,ID=lu_name ,ENCR= COND ÊÍ

OPT
REQD

Modify which cryptographic key name is used for an LU:

ÊÊ MODIFY procname,SECURITY ,ID=lu_name ,CKEY= ALTERNATE ÊÍ

PRIMARY

Initiate SLU authentication for an LU:

ÊÊ MODIFY procname,SECURITY ,ID=lu_name ,CERTIFY=YES ÊÍ

Increase the message authentication specification for an LU:

ÊÊ MODIFY procname,SECURITY ,ID=lu_name ,MAC= COND Ê

REQD

Ê ÊÍ
,MACTYPE= CRC
,MACLNTH= 2
4
DES
,MACLNTH= 4
6
8

Abbreviations
Operand Abbreviation
MODIFY F
ALTERNATE ALT
PRIMARY PRIM

Purpose
The MODIFY SECURITY command is a superset of the MODIFY ENCR command.
This command allows you to change the cryptographic and the message
authentication requirements for application program logical units and device-type
logical units.

Operands
procname
is the procedure name for the command. If procname in the START command

340 SNA Operation

 MODIFY SECURITY
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CERTIFY=YES
indicates that SLU authentication (verifying that the SLU is using the same
cryptographic key as the PLU) is to be performed by the PLU, if encryption is
being used.
CKEY
indicates whether VTAM is to use the primary or alternate cryptographic key
name to generate cryptographic session keys for this logical unit.

This indicator is initialized to PRIMARY, and cannot be explicitly set with the LU
definition statement. If you do not specify CKEY, the current CKEY value is
unchanged.

CKEY only affects the secondary logical unit (SLU) key; it does not affect the
cross domain (CP/SSCP) keys.
CKEY=ALTERNATE
specifies that VTAM use the alternate cryptographic key name to generate
cryptographic session keys. The alternate name is either the name on the
LU definition statement or the value of the CKEYNAME operand with the
suffix .ALT. For example, name.ALT.
CKEY=PRIMARY
specifies that VTAM use the primary cryptographic key name to generate
cryptographic session keys. The primary name is either the name on the LU
definition statement or the value of the CKEYNAME operand.
ENCR
specifies the new cryptography specifications of the logical unit. The level of the
cryptography specification can only be raised. Any attempt to lower the level is
rejected. The new level is effective for all future sessions involving the logical
unit; existing active or pending sessions are not affected.
ENCR=OPT
raises the level of the logical unit’s cryptography specification from no
cryptography to optional (capable of cryptography).
ENCR=COND
raises the level of the logical unit’s cryptography specification from no
cryptography or optional to required (that is, all user sessions must be
encrypted) if both sides support encryption. If the session partner does not
support encryption, the session does not fail; instead, a session is
established with no encryption of data.
ENCR=REQD
raises the level of the logical unit’s cryptography specification from no
cryptography or optional (or selective or conditional for application
programs) to required (that is, all user sessions must be encrypted).
ID=lu_name
specifies the name of the LU whose security specification you want to change.

Chapter 2. VTAM Operator Commands 341

MODIFY SECURITY
The ID must represent the type of LU that can be modified by the remaining
operands:

CKEY Device-type LU
ENCR Application program or device-type LU
MAC Application program LU
MACTYPE
Application program LU
MACLNTH
Application program LU
MAC
specifies the new message authentication specifications for the logical unit
(application program or device). The value you specify must be higher than the
current value. Any attempt to lower the level is rejected.

MAC values, in ascending order, are:

v NONE
v COND (conditional)
v REQD (required)

The new MAC level is effective for all subsequent sessions involving the logical
unit; currently active or pending sessions are not affected. If you do not specify
the MAC operand, the current MAC value is unchanged.
MAC=COND
raises the level of the application program message authentication
specifications from NONE to COND (conditional); that is, if the session
partners are MAC capable, each side uses message authentication codes.
If one session partner does not support the function, the session does not
fail; instead, a session is established but without any message
authentication of data.
MAC=REQD
raises the level of the message authentication specification of an application
program or logical unit from NONE or conditional (COND), to required; that
is, all user sessions must use message authentication codes.
MACLNTH
specifies the minimum length, in bytes, of the message authentication code that
is to be generated. For MACTYPE=DES, valid values are 4, 6, or 8. For
MACTYPE=CRC, valid values are 2 or 4.
MACTYPE
specifies the method to use when message authentication codes are created
and checked.
MACTYPE=CRC
specifies that an internal VTAM service is used to create a cyclic
redundancy check (CRC) for data on the specified conversation.
MACTYPE=DES
specifies that VTAM uses message authentication code services as
provided in the Common Cryptographic Architecture (CCA) specification.
The message authentication code calculation support is described in the
ANSI X 9.9 standard.

342 SNA Operation

 MODIFY SESSION

MODIFY SESSION Command

ÊÊ MODIFY procname,SESSION=number_of_sessions ,ID=line_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
You can use the MODIFY SESSION command to request that an NCP change the
session limit (the maximum number of concurrent line scheduling sessions allowed)
for a nonswitched multipoint line to one or more attached start/stop or BSC
terminals. This limit does not become effective until the number of sessions now in
operation falls below the new limit.
Notes:
1. The session limit should not exceed the number of devices on the line. If the
line has IBM 3270 terminals attached, the session limit should be the total
number of cluster controllers and terminals on the line.
2. This command does not activate resources. To do this, the appropriate resource
must be activated (for example, by using the VARY ACT command).

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=line_name
specifies the name of a nonswitched multipoint line to one or more attached
start/stop or BSC terminals.
SESSION=number_of_sessions
specifies the session limit as a decimal integer 1–255. This is the maximum
number of concurrent line scheduling sessions allowed on the line specified by
the ID operand.

Chapter 2. VTAM Operator Commands 343

MODIFY SUPP

MODIFY SUPP Command

ÊÊ MODIFY procname,SUPP= NOSUP ÊÍ
INFO
WARN
NORM
SER

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY SUPP (suppression) command allows you to change the message
suppression level after VTAM has been started.

Note that some error messages, such as those indicating abnormal termination of a
task, are classified as “insuppressible” and cannot be suppressed. Other messages
that cannot be suppressed include those requiring a response from the VTAM
operator (messages that end in “A”) and those resulting from the operator’s status
inquiries (messages resulting from a DISPLAY command). See OS/390 eNetwork
Communications Server: SNA Messages for a definition of these message
categories and the classifications of specific VTAM messages.

If the PPOLOG option is in effect, messages that are suppressed by the MODIFY
SUPP command or the SUPP start option are still sent to the primary program
operator, even though those messages do not appear on the system console.

Also see OS/390 eNetwork Communications Server: SNA Messages for information
on message flooding.
Notes:
1. Issuing a MODIFY SUPP command prevents specific messages from being
issued by VTAM. Prior to issuing the command, make sure you understand the
potential effects on NetView command lists and any automated operation
facilities in your network.
2. Message suppression might prevent message IST223I (indicating the
completion of the MODIFY SUPP command) from being issued by VTAM.
3. You can use the “MODIFY VTAMOPTS Command” on page 385 (SUPP
operand) to perform the same function as this command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.

344 SNA Operation

 MODIFY SUPP
SUPP
specifies the suppression level for VTAM messages. The following list shows
suppression level in the order of severity from least to most.
SUPP=NOSUP
specifies that no VTAM messages are to be suppressed.
SUPP=INFO
specifies that only those VTAM messages classified as informational
messages are to be suppressed.
SUPP=WARN
specifies that those VTAM messages classified as warning messages, as
well as informational messages, are to be suppressed.
SUPP=NORM
specifies that those VTAM messages classified as normal messages, as
well as warning and informational messages, are to be suppressed.
SUPP=SER
specifies that those VTAM messages classified as serious error messages,
as well as normal, warning, and informational messages, are to be
suppressed.

Chapter 2. VTAM Operator Commands 345

MODIFY TABLE

MODIFY TABLE Command

Change resource associations:

ÊÊ MODIFY procname,TABLE ,OPTION=ASSOCIATE Ê

Ê ,TYPE= ASLTAB ,ID=name,OLDTAB= * Ê

FLDTAB old_table_name
LOGTAB
MDLTAB
MODETAB
USSTAB
COSTAB,NETID=netid,ORIGIN=ncp_name

Ê ,NEWTAB=new_table_name ÊÍ

Delete resource associations:

ÊÊ MODIFY procname,TABLE ,OPTION=DELETE Ê

Ê ,TYPE= ASLTAB ,ID=name,OLDTAB= * ÊÍ

FLDTAB old_table_name
LOGTAB
MDLTAB
MODETAB
USSTAB
COSTAB,NETID=netid,ORIGIN=ncp_name
FILTER

Load a replacement table (other than a filter table):

ÊÊ MODIFY procname,TABLE ,OPTION=LOAD ,NEWTAB=new_table_name Ê

Ê ÊÍ
,OLDTAB=old_table_name

Load a replacement filter table:

ÊÊ MODIFY procname,TABLE ,OPTION=LOAD ,TYPE=FILTER ,NEWTAB=new_table_name ÊÍ

Load an updated directory definition file:

ÊÊ MODIFY procname,TABLE ,OPTION=LOAD ,TYPE=CMIPDDF ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F
NETID=name NET=name
NEWTAB=name NEW=name

346 SNA Operation

 MODIFY TABLE
Operand Abbreviation
OLDTAB=name OLD=name
OPTION OPT
OPTION=ASSOCIATE OPT=ASSOC
OPTION=DELETE OPT=DEL
TYPE=ASLTAB TYPE=ASL
TYPE=COSTAB TYPE=COS
TYPE=FLDTAB TYPE=FLD
TYPE=LOGTAB TYPE=LOG
TYPE=MDLTAB TYPE=MDL
TYPE=MODETAB TYPE=MODE
TYPE=USSTAB TYPE=USS

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
OPTION=DELETE, code only OPT=DEL. Do not code OPTION=DEL.

Purpose
The MODIFY TABLE command dynamically loads VTAM tables, changes VTAM
table associations, or both. This command also disassociates resources from
tables. MODIFY TABLE does not affect existing sessions with the resource named
on the ID operand or its subordinate nodes. Only new sessions established after
this command is issued are affected. The MODIFY TABLE command supports the
following types of tables:
v Associated LU
v Class-of-service
v CMIP services directory definition file
v Interpret
v Logon mode
v Message-flooding prevention
v Model name
v Session awareness data filter
v USS.

Note: Do not use the MODIFY TABLE command for the APPN class-of-service
definitions. Use the VARY ACT command to activate the file containing the
updated definitions.

The MODIFY TABLE command does not change the value of the DLOGMOD
operand. To change the value of the DLOGMOD operand, see the “MODIFY
DEFAULTS Command” on page 269 or the “MODIFY RESOURCE Command” on
page 334 .

The MODIFY TABLE command can end unsuccessfully if the table being loaded is
partially or entirely contained in new extents (data spaces where information is
stored) within VTAMLIB. Because VTAMLIB is opened once during VTAM
initialization, the table is not accessible until VTAM is halted, restarted, and
VTAMLIB is opened again.

Chapter 2. VTAM Operator Commands 347

MODIFY TABLE
The MODIFY TABLE command performs several functions, depending on the
values you specify on the OPTION and TYPE operands.
v F TABLE,OPT=ASSOC
Allows you to change all references to old_table_name to refer to
new_table_name for resource name and its subordinate nodes. If necessary,
new_table_name is loaded. Values for old_table_name include:
– Logmode table (TYPE=MODETAB)
– USS table (TYPE=USSTAB)
– Interpret table (TYPE=LOGTAB)
– Associated LU table (TYPE=ASLTAB)
– Message-flooding prevention table (TYPE=FLDTAB)
– Model name table (TYPE=MDLTAB).
v F TABLE,OPT=ASSOC,TYPE=COS
Allows you to associate a new class-of-service table with the network netid for
the gateway NCP or PU type 5 identified by name.
v F TABLE,OPT=DEL
Allows you to delete the association between name, its subordinate nodes, and
old_table_name. If applicable, default tables are used with subsequent session
initiation requests.
v F TABLE,OPT=DEL,TYPE=COS
Allows you to terminate the association between a COS table and network netid
for gateway NCP name. A COS table is no longer defined for the specified
network.
v F TABLE,OPT=DEL,TYPE=FILTER
Allows you to delete the current session awareness (SAW) data filter. When you
delete the filter, SAW data and trace data for all sessions are sent over the CNM
interface.
v F TABLE,OPT=LOAD
Allows you to replace old_table_name, which is in use, with new_table_name,
which is currently not in use, or to reload a table that is in use. All resources
currently associated with the old table are re-associated with the new table.

Note: If old_table_name is the current value of the DYNMODTB start option, the
value of the DYNMODTB start option is changed to new_table_name.

If OLDTAB is omitted, it is assumed to be the same as NEWTAB.

v F TABLE,OPT=LOAD,TYPE=FILTER
Allows you to replace the current session awareness data filter, which is in use,
with a new filter, which is currently not in use, or to reload a filter that is in use.
v F TABLE,OPT=LOAD,TYPE=CMIPDDF
Loads the current version of the CMIP services directory definition file, which lists
the systems that are and are not allowed access to CMIP services.
When CMIP services is started, CMIP services reads in the directory definition
file. You can update the directory definition file while VTAM is running, but CMIP
services is aware of these changes only when the MODIFY TABLE command is
issued.

Note: If you use the MODIFY TABLE command to change or delete a table
association, be aware that later use of a VARY ACT,UPDATE=ALL command
for dynamic reconfiguration can undo the effects of the MODIFY TABLE

348 SNA Operation

 MODIFY TABLE
command. This is because the table name in the definition file overrides the
value that was changed or deleted with the MODIFY TABLE command. Even
if no table name is coded in the definition file, VTAM assumes a null value
for the table name and the null value overrides the MODIFY TABLE value.
To prevent the new table name specification from being overridden
unintentionally, code the definition statement with the desired value.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=name
identifies the resource. All resources at or below this resource in the hierarchy
are considered eligible resources.

The name can be a network-qualified name. If the name specified on the ID

operand is network-qualified, this name is considered to be the real name of the
resource. If a cross-network CDRSC is to be specified on the ID operand, it
must be specified as a network-qualifed name if the CDRSC is defined using
NQNMODE=NQNAME (either by definition or start option). For a
message-flooding prevention table (TYPE=FLDTAB), this value must always be
specified as ISTNOP.
NETID=netid
identifies the network attached to a gateway NCP with which the
class-of-service table association is to be changed.

Note: If a model network is defined by using COPIES as part of the network

definition, then *NETWORK is used to change the class-of-service table
for the model network.
NEWTAB=new_table_name
identifies the table to be used. When the new table is of TYPE=USSTAB, then
FORMAT=DYNAMIC must have been coded on the USSTAB macro for the
referenced table.

For TYPE=USSTAB and TYPE=LOGTAB, new_table_name must be assembled

using the VTAM V3R2 or later macro libraries.

VTAM validates the table type.

OLDTAB
specifies a specific old table or all old tables. If old_table_name refers to a table
that was not assembled using the VTAM V3R2 or later macro library, MODIFY
TABLE,OPTION=LOAD can still be used to replace the old table, as long as the
new table has been reassembled and new_table_name is the same as
old_table_name. If both tables are assembled using the VTAM V3R2 or later
macro libraries, the names can be different because table type verification will
take place. There is no type verification between the old table and the new
table if the old table was not assembled against the VTAM V3R2 or later macro
libraries.

Chapter 2. VTAM Operator Commands 349

MODIFY TABLE
OLDTAB=old_table_name
For OPTION=ASSOCIATE, changes associations for the resource specified
by the ID operand (and its subordinate resources) and currently associated
with the named table.

For OPTION=DELETE, terminates associations for the resource specified

by the ID operand (and its subordinate resources) and currently associated
with the named table.

For OPTION=LOAD, replaces the old table with the table identified by the
NEWTAB operand. Resources associated with the old table are
re-associated with the new table.

Note: If old_table_name is the current value of the DYNMODTB start

option, the value of the DYNMODTB start option is changed to
new_table_name.
OLDTAB=*
For OPTION=ASSOCIATE, indicates that the specified table associations
should be changed to new_table_name, regardless of the current table
associations.

For OPTION=DELETE, changes the associations of all eligible resources

specified by the ID operand regardless of any current table associations.
OPTION
specifies whether a table is to have its resource associations changed or
deleted, or whether the table is to be loaded.
OPTION=ASSOCIATE
specifies the table is to have its resource associations changed. It changes
the associations of the specified resources. If the table to be associated is
not in use, VTAM loads it. Current table associations for a specific resource
can be determined by issuing one of the following commands:
v The DISPLAY COS command for the resource named on the ID operand
v The DISPLAY ID command for the resource named on the ID operand or
its subordinate nodes.

If the MODETAB, LOGTAB, or USSTAB value is omitted from the original

resource definition, the default table can be used. However, the name of the
default table is not stored with the resource definition. Therefore, MODIFY
TABLE,OLDTAB=default_name, NEWTAB=new_table_name does not
change the table association; however,
OLDTAB=*,NEWTAB=new_table_name does provide that function.

If COSTAB was not specified on either the BUILD or NETWORK definition

statement, OPTION=ASSOCIATE adds the appropriate class-of-service
specification.

A non-gateway SSCP (GWSSCP=NO) can associate a class-of-service

table only for the native network of a gateway NCP.

Specifying MODIFY TABLE,OPTION=ASSOC,TYPE=COS, ORIGIN=

host_pu_name, NEWTAB=ISTSDCOS,NETID=host_netid requests that
VTAM attempt to load ISTSDCOS if it is not currently loaded. This enables
the user to create and load a copy of ISTSDCOS, even though one might

350 SNA Operation

 MODIFY TABLE
not have been available during VTAM initialization. host_pu_name can be
either ISTPUS or the name specified in the HOSTPU start option.

Use MODIFY TABLE,OPTION=LOAD,NEWTAB=ISTSDCOS to request

VTAM to reload ISTSDCOS if it is currently loaded.
OPTION=DELETE
specifies the table is to have its resource associations deleted. It terminates
the association between the specific resources and the table.

If USSTAB, MODETAB, LOGTAB, ASLTAB, or MDLTAB is not specified

when the resource is defined, there is no association to terminate. Where
applicable, the default table is still used.

If old_table_name is an IBM-supplied default table (for example

OLDTAB=ISTINCDT or OLDTAB=ISTSDCOS), all explicit table associations
are terminated, but the table is not deleted from memory. If old_table_name
is not an IBM-supplied default table, it is deleted from memory as a result of
this command.
OPTION=LOAD
specifies the table is to be loaded.

When OPTION=LOAD,NEWTAB=new_table_name is specified:

The MODIFY TABLE command loads the table named in the NEWTAB
operand. All resources associated with the old table are re-associated with
the new table. If the OLDTAB and NEWTAB operand values are identical or
OLDTAB is omitted, the indicated table is reloaded into memory.

Note: All tables must be associated with resources. OPTION=LOAD

replaces a table only if it is already being used by a resource.
OPTION=ASSOCIATE can be used to load a new table (which is not
in use) and associate it with a resource.

The IBM-supplied tables can be reloaded (old_table_name is equal to

new_table_name), but cannot be deleted (old_table_name is not equal to
new_table_name).

When OPTION=LOAD,TYPE=CMIPDDF is specified:

CMIP services reads in the current version of the directory definition file
without disrupting the CMIP application program interface or any topology
manager or topology agent application programs. If the MODIFY command
fails, the existing directory definition file remains in use.

If CMIP services is not active when the command is issued, a message

indicates it is not active. When CMIP services becomes active, it reads in
the current version of the directory definition file.

If CMIP services is active when the command is issued, it reads in the

current version of the directory definition file from SYS1.SISTCMIP. The
directory definition file indicates the instances of CMIP services that can
have associations with one another. For a description of associations, refer
to the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide. Existing associations are not affected by this
command. For example, if the directory definition file denies access to an

Chapter 2. VTAM Operator Commands 351

MODIFY TABLE
application program that already has an association with CMIP services, the
association remains established. However, if this association ends, it cannot
be reestablished, because the directory definition file denies access to that
application program.
ORIGIN=ncp_name
identifies the NCP major node of a gateway NCP for which the class-of-service
table association is to be changed.
TYPE
specifies the type of table the command will process. This value must be one of
the following:
TYPE=ASLTAB
specifies the associated LU table.
TYPE=CMIPDDF
specifies the updated CMIP services directory definition file.
TYPE=COSTAB
specifies the class-of-service table.
TYPE=FILTER
specifies the session awareness data filter.
TYPE=FLDTAB
specifies the message-flooding prevention table. For TYPE=FLDTAB, ID
must be specified as ISTNOP.
TYPE=LOGTAB
specifies the interpret table.
TYPE=MDLTAB
specifies the model name table.
TYPE=MODETAB
specifies the logon mode table.

Note: The MODIFY TABLE command does not change the value of the
DLOGMOD operand. To change the value of the DLOGMOD
operand, see the “MODIFY DEFAULTS Command” on page 269 or
the “MODIFY RESOURCE Command” on page 334.
TYPE=USSTAB
specifies the USS table. If message IST116I is received because the
USSTAB start option is incorrect, MODIFY
TABLE,OPTION=ASSOCIATE,ID=ISTNOP,OLDTAB=*,
NEWTAB=new_table_name can be issued to supply a new USS table,
represented by ISTNOP, for the network operator.

When OPTION=ASSOCIATE or OPTION=DELETE is specified, VTAM does

not change the value of USS LANGTAB tables. When OPTION=LOAD is
specified, VTAM changes the USS LANGTAB table if old_table_name or
new_table_name is currently being used as a LANGTAB table. For more
information about LANGTAB processing using USS commands, see the
OS/390 eNetwork Communications Server: SNA Resource Definition
Reference.

352 SNA Operation

 MODIFY TGP

MODIFY TGP Command

ÊÊ MODIFY procname,TGP ,TGPNAME=tg_profile_name Ê

Ê ,ID=adjacent_link_station_name ÊÍ
,ID=cp_name ,TGN=tg_number

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY TGP (transmission group profile) command allows you to change the
TG profile associated with a type 2.1 connection. A specific connection is identified
by the combination of a control point (CP) name and TG number, or by the adjacent
link station (PU) name.

If this command is issued while the connection is active and the new TG profile can
be located, the topology database is updated and the new characteristics are used
immediately. If the connection is not active, the new TG profile name is saved and
is reported the next time the connection is activated.

This command is valid only when it is issued at an APPN node (network node, end
node, interchange node, or migration data host).

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ID=name
specifies an adjacent control point (CP) name or an adjacent link station (PU)
name. If a CP name is specified, then the TGN operand must also be specified.

A CP name can be network-qualified. If the network ID is not specified, VTAM

uses the network ID of the host from which the command is issued. You can
specify * (or *NETWORK) as the network ID portion of a network-qualified
adjacent CP name in order to modify the TG profile for adjacent CPs that do
not currently have a network identifier assigned to them. For example, the
following command is valid if A01N currently does not have a network ID
associated with it:
F procname,TGP,TGPNAME=BATCH,ID=*.a01n,TGN=3
TGN=tg_number
specifies the transmission group number associated with the CP. For
virtual-route-based TG connections, TGN must be specified as 255.

Chapter 2. VTAM Operator Commands 353

MODIFY TGP
TGPNAME=tg_profile_name
specifies the name of a transmission group profile definition.

354 SNA Operation

 MODIFY TNSTAT

MODIFY TNSTAT Command

,CNSL=NO
ÊÊ MODIFY procname,TNSTAT ÊÍ
,CNSL= NO ,TIME=number_of_minutes
YES

Abbreviations
Operand Abbreviation
MODIFY F
CNSL=NO NOCNSL
CNSL=YES CNSL

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for CNSL=YES,
code only CNSL.

Purpose
VTAM can record tuning statistics about some of its activities. You can use these
statistics to adjust VTAM and NCP variables to improve performance. You can use
tuning statistics to gather information on communications between VTAM and any of
the following channel-attached nodes:
v Communication controller
v Adjacent host processor
v SNA cluster controller.

For more information on using tuning statistics, see the OS/390 eNetwork
Communications Server: SNA Network Implementation Guide.

If you choose to record tuning statistics, you must specify the TNSTAT start option
when you start VTAM.

You can record external trace data using the system management facility (SMF) in
the system during system generation.

MODIFY TNSTAT reopens the tuning statistics file if it was closed by a previous
MODIFY NOTNSTAT command.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
CNSL
specifies whether tuning statistics are to be sent to the system console.

Chapter 2. VTAM Operator Commands 355

MODIFY TNSTAT
CNSL=YES
specifies that tuning statistics records are to be sent to the system console
and to the SMF data set.
CNSL=NO
specifies that tuning statistics records are to be sent only to the SMF data
set.
TIME=number_of_minutes
specifies the number of minutes between tuning statistic recording events.
Specify this number as a decimal integer in the range 1–1440. If the TIME
operand is not specified, the time value in effect before MODIFY NOTNSTAT
was issued remains in effect.

356 SNA Operation

 MODIFY TOPO

MODIFY TOPO Command

Delete a node:

,FUNCTION=DELETE
ÊÊ MODIFY procname,TOPO ,ID=cp_name Ê

,SCOPE=LOCAL
Ê ÊÍ
,SCOPE= LOCAL ,TYPE=FORCE
NETWORK

Delete a transmission group:

,FUNCTION=DELETE
ÊÊ MODIFY procname,TOPO ,ORIG=cp_name ,DEST=cp_name Ê

,SCOPE=LOCAL
Ê ,TGN=tg_number ÊÍ
,SCOPE= LOCAL ,TYPE=FORCE
NETWORK

Modify the status of a node for route calculation:

ÊÊ MODIFY procname,TOPO ,ID=cp_name ,FUNCTION= NORMAL Ê

QUIESCE

,SCOPE=LOCAL
Ê ÊÍ
,SCOPE= LOCAL
NETWORK

Modify the status a transmission group for route calculation:

ÊÊ MODIFY procname,TOPO ,FUNCTION= NORMAL ,ORIG=cp_name ,DEST=cp_name Ê

QUIESCE

,SCOPE=LOCAL
Ê ,TGN=tg_number ÊÍ
,SCOPE= LOCAL
NETWORK

Abbreviations
Operand Abbreviation
FUNCTION=DELETE DELETE
MODIFY F
TYPE=FORCE FORCE or F

Chapter 2. VTAM Operator Commands 357

MODIFY TOPO
When using an abbreviation in place of an operand, code the abbreviation exactly
as shown in the table. For example, when coding the abbreviation for
TYPE=FORCE, code only F or FORCE. Do not code TYPE=F.

Purpose
The MODIFY TOPO (topology) command deletes entries from the topology
database or changes the status of an entry in the topology database. The entries
can be for either nodes or transmission groups (TGs).

Normally you should not need to delete entries from the database; however, if for
some reason you need to do so, you can use this command. For example, if
another node (over which you have no control) has broadcast erroneous or
unnecessary topology data into the network, the topology database at this node
could choose incorrect or inefficient routes.

Existing sessions are not affected when you delete an entry from the topology
database or change the status of an entry in the topology database for a node or
TG that is currently in use. However, new session requests might fail if no other
route is available.

This command is valid only when it is issued at a network node or an interchange

node.
Notes:
1. You cannot delete the entry for your own host node.
2. You cannot delete an active local transmission group.
3. You cannot delete an adjacent node unless the link to the adjacent node is
inactive.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
DEST=cp_name
specifies the destination node (a control point) for a transmission group. The
name can be network-qualified.
FUNCTION
specifies the function to be performed on the entry in the topology database.
FUNCTION=DELETE
specifies that an entry is to be deleted from the topology database.
FUNCTION=NORMAL
specifies that an entry for a resource is to be returned to a normal state
(after being quiesced) in the topology database and available for route
calculation.

358 SNA Operation

 MODIFY TOPO
FUNCTION=QUIESCE
specifies that an entry for a resource is to be marked as quiesced in the
topology database and not used for route calculation.
ID=cp_name
specifies the name of a node (control point). The name can be
network-qualified.

Note: You cannot delete the entry for your own host node.
ORIG=cp_name
specifies the origin node (a control point) for a transmission group. The name
can be network-qualified.
TGN=tg_number
specifies the transmission group number. The valid range for TG numbers is
1–255.

For FUNCTION=DELETE, the transmission group is deleted in both directions

between the origin and destination nodes.
SCOPE
specifies whether the request affects the local topology database only or is
propagated to all topology databases in the network.
SCOPE=LOCAL
specifies that the request affects the local topology database only.

For FUNCTION=DELETE, the resource is deleted immediately from the

local topology database.
SCOPE=NETWORK
specifies that the request is propagated to all topology databases in the
network.

For FUNCTION=DELETE, the resource is marked as unusable for route

calculation in all topology databases in the network. Each network node
supporting enhanced topology database garbage collection deletes the
resource during its next garbage collection cycle. Garbage collection occurs
once every 24 hours. Network nodes that do not support enhanced
topology database garbage collection reset the time left value to 15 days.
Notes:
1. If SCOPE=NETWORK is specified for an end node resource, the
request is not propagated to other network nodes. Topology information
for end node resources is only kept in the topology database of the
owning network node.
2. If SCOPE=NETWORK is specified with FUNCTION=QUIESCE for
another node or for a TG owned by another node, a correction to the
status of the resource might be broadcast by the owning node.
TYPE=FORCE
is required to delete an adjacent node. The link to the adjacent node must be
inactive. If you are deleting a node that is not adjacent, this operand is not
required.

Chapter 2. VTAM Operator Commands 359

MODIFY TOPO
TYPE=FORCE is also required to delete a local transmission group. A TG is
considered to be local if the origin or destination is the host from which you are
entering this command. The TG must be inactive. If the TG is not local, this
operand is not required.

360 SNA Operation

 MODIFY TRACE

MODIFY TRACE Command

Start or modify a buffer contents trace:

,AMOUNT=PARTIAL
ÊÊ MODIFY procname,TRACE ,TYPE=BUF ,ID=node_name Ê
,AMOUNT= FULL
PARTIAL

,IDTYPE=RESOURCE ,SAVE=YES ,SCOPE=ONLY

Ê ÊÍ
,IDTYPE= CP ,SAVE= NO ,SCOPE= ONLY
SSCP YES ALL
RESOURCE

Start or modify a communication network management trace:

ÊÊ MODIFY procname,TRACE ,TYPE=CNM ,ID= PDPIUBUF ÊÍ

SAWBUF

Start or modify a user Exit buffer trace:

ÊÊ MODIFY procname,TRACE ,TYPE=EXIT ,ID=ISTEXCAA Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » ACCTING )
ADJSSCP
ALIAS
ALS
BEGIN
END
GWPATH
INITAUTH
REPL
SECAUTH
VRSEL
XRF

ÊÊ MODIFY procname,TRACE ,TYPE=EXIT ,ID=ISTEXCCS Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » BEGIN )
CONNSTAT
DYNABLD
XID
END

Chapter 2. VTAM Operator Commands 361

MODIFY TRACE
ÊÊ MODIFY procname,TRACE ,TYPE=EXIT ,ID=ISTEXCDM Ê

Ê ,OPTION= ALL ÊÍ
option
(option)
,

( » BEGIN )
INITAUTH
BN_SEL
ADS_SEL
CDS_SEL
CRR_SEL
REPL
END

Start or modify a generalized PIU trace:

ÊÊ MODIFY procname,TRACE ,TYPE=GPT ,ID=node_name Ê

,IDTYPE=RESOURCE
Ê Ê
,ALSNAME=adjacent_link_station_name ,IDTYPE= CP
SSCP
RESOURCE

,SCOPE=ONLY
Ê ÊÍ
,SCOPE= ONLY
ALL

Start or modify an input/output trace:

,IDTYPE=RESOURCE
ÊÊ MODIFY procname,TRACE ,TYPE=IO ,ID=node_name Ê
,IDTYPE= CP
SSCP
RESOURCE

,SAVE=YES ,SCOPE=ONLY
Ê ÊÍ
,SAVE= NO ,SCOPE= ONLY
YES ALL

Start or modify a module trace:

362 SNA Operation

 MODIFY TRACE
ÊÊ MODIFY procname,TRACE ,TYPE=MODULE ,OPTION= ALL ÊÍ
option
(option)
,

( » COMMAND )
CONNECTION
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
PURGE
SESSION

Start or modify an NCP line trace:

ÊÊ MODIFY procname,TRACE ,TYPE=LINE ,ID=line_name Ê

,COUNT=ALL
Ê ÊÍ
,COUNT= ALL
number_of_bytes

Start or modify a 3710 Network Controller line trace:

ÊÊ MODIFY procname,TRACE ,TYPE=NETCTLR ,ID=pu_name ,LINE=line_name Ê

Ê ,PU=3710_pu_name ÊÍ
,FRAMES= ALL
DATA

Start or modify a scanner interface trace:

ÊÊ MODIFY procname,TRACE ,TYPE=SIT ,ID=line_name Ê

,COUNT=ALL
Ê ÊÍ
,COUNT= ALL ,TRACEPT=trace_point_id
number_of_bytes

Start or modify an SMS (buffer use) trace:

,ID=VTAMBUF
ÊÊ MODIFY procname,TRACE ,TYPE=SMS ÊÍ

Start or modify a resource state trace:

ÊÊ MODIFY procname,TRACE ,TYPE=STATE Ê

Chapter 2. VTAM Operator Commands 363

MODIFY TRACE
Ê ,ID=node_name Operands used with ID ÊÍ
,OPTION= ALL Operands used with OPTION
option
(option)
,

( » ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU

Operands used with ID

,IDTYPE=RESOURCE ,SAVE=YES
Ê
,IDTYPE= CP ,SAVE= NO
SSCP YES
RESOURCE

Ê
,OPTION= ALL
option
(option)
,

( » ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU

Operands used with OPTION

,IDTYPE=RESOURCE ,SAVE=YES

,ID=node_name ,IDTYPE= CP ,SAVE= NO

SSCP YES
RESOURCE

Start or modify a transmission group trace:

ÊÊ MODIFY procname,TRACE ,TYPE=TG ,ID=line_name ÊÍ

Start or modify a TSO user ID trace:

364 SNA Operation

 MODIFY TRACE
ÊÊ MODIFY procname,TRACE ,TYPE=TSO ,ID=tso_user_id ÊÍ

Start or modify the VTAM internal trace:

ÊÊ MODIFY procname,TRACE ,TYPE=VTAM Ê

Ê Ê
,BFRNUM=2
,MODE= EXT
,BFRNUM=number
INT
,SIZE=size ,DSPSIZE=dspsize

(1) (2)
,OPTION=(API,MSG,NRM,PIU,PSS,SMS,SSCP)
Ê ÊÍ
,OPTION= ALL
option
(option)
,

( » API )
APPC
CFS
CIO
CMIP
CSM
ESC
HPR
LCS
LOCK
MSG
NRM
PIU
PSS
SMS
SSCP
TCP
VCNS
XBUF
XCF

Notes:
1. These seven options are defaults for MODE=INT. There are no default options
for MODE=EXT.
2. PSS and SMS can be turned off.

Abbreviations
Operand Abbreviation
MODIFY F
ALSNAME ALS

Chapter 2. VTAM Operator Commands 365

MODIFY TRACE
Operand Abbreviation
AMOUNT=FULL AMT=F
AMOUNT=PARTIAL AMT=P
OPTION OPT
OPTION=COMMAND OPT=CMD
OPTION=CONNECTION OPT=CON
OPTION=DEFINITION OPT=DEF
OPTION=INTERFACES OPT=INT
OPTION=MANAGEMENT OPT=MGMT
OPTION=SESSION OPT=SES
SAVE=YES SAVE
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE
TRACES TRACE

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for SCOPE=ALL,
code only EVERY or E. Do not code SCOPE=E.

Purpose
The MODIFY TRACE command starts traces or modifies the parameters for
currently running traces. VTAM traces are also started with the TRACE start option,
as described in the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference.

Activation and use of VTAM traces have dependencies on the options used to start
the system trace facility in each operating system environment. See the OS/390
eNetwork Communications Server: SNA Diagnosis for a complete description of the
system trace facility requirements, when to use these traces, and how to interpret
the results.

General PIU trace (GPT) records are printed by the trace analysis program (TAP)
utility of SSP. For more information about TAP, see the NCP, SSP, and EP
Diagnosis Guide .

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
ALSNAME=adjacent link station name
applies only when TYPE=GPT and specifies the name of the adjacent link
station through which you want tracing to occur. The adjacent link station name
must be a PU in an NCP major node or a switched PU connected by an NCP
link.

366 SNA Operation

 MODIFY TRACE
The LU can be traced over multiple connections; however, to do so, you must
enter a separate command for each connection.

You do not need to specify the ALSNAME operand if either of the following is
true:
v The ALS list has only one entry (and it is not ISTAPNPU). That entry is
selected.
v The ALS list has two entries, one of which is ISTAPNPU. The entry other
than ISTAPNPU is selected.

The command fails if ISTAPNPU is specified, or if ISTAPNPU is used by default

because it is the only entry in the ALS list.

If no ALS list exists for the resource, specify the adjacent link station on the
ALSNAME operand.

Use the DISPLAY ID=lu_name,SCOPE=ALL command to display all sessions

for an independent LU and which adjacent link station list is used for each
session.
AMOUNT
applies only when TYPE=BUF. It determines whether VTAM starts a partial
buffer contents trace or a full buffer contents trace for the specified node name.

You can run a partial buffer contents trace and a full buffer contents trace at the
same time for different resources. (Issue a separate MODIFY TRACE command
for each resource.) For example, you can start a partial buffer contents trace for
an application program, with partial buffer contents tracing for some resources
in session with the application program and full buffer contents tracing for other
resources in session with the application program. When the level of tracing
differs between two resources on opposite ends of a session (one is partial and
the other is full), full buffer tracing is used.

You can switch between partial and full buffer tracing for the same resource by
issuing additional MODIFY TRACE commands, without having to deactivate the
trace.
AMOUNT=PARTIAL
tells VTAM to record the data in trace records with a maximum size of 256
bytes. Each trace record contains a trace record header and data. Data that
does not fit in a 256-byte trace record is lost.
AMOUNT=FULL
tells VTAM to record all of the data transmitted in message buffers. Multiple
trace records might be needed to record all of the data.
BFRNUM=number
applies only to TYPE=VTAM,MODE=EXT. It specifies the number of 8K external
trace buffers the VTAM internal trace is to allocate and use for generalized
trace facility (GTF) processing. Integers 0 or 2–50 can be specified. If you omit
this option, the default is 2. Two times the number of processors in the central
processing unit (CPU) should ensure that enough buffers are available.

When an integer of 2–50 is specified, VTAM accumulates approximately 8K of

external trace data prior to sending the data to GTF.

Chapter 2. VTAM Operator Commands 367

MODIFY TRACE
If zero is specified or there is no buffer available for the trace record, VTAM
sends each trace record to GTF as it is recorded. This incurs a significant
system overhead, and should be avoided.

If external trace recording is already active, and the new value specified for
BFRNUM:
v Is less than the existing value, the number of buffers is not changed
v Is greater than the existing value, the number of the buffers is increased.
COUNT
applies only when TYPE=LINE or TYPE=SIT. It specifies the number of bytes
that are traced by either the NCP for a line trace (without the TG operand), or
the communication scanner processor for the scanner interface trace. The
COUNT operand has no effect on NTRI lines prior to NCP V5R2.1. NTRI
always traces the same amount of data.
COUNT=number_of_bytes
specifies the number of bytes of data to be traced. The value must be a
decimal integer 0–254. COUNT=0 specifies that only the NCP control
characters and none of the data is to be traced.
COUNT=ALL
specifies that all of the data is to be traced.
DSPSIZE
controls the use of the VIT data space. The VIT data space can store much
more of the internal VIT than is possible using only the fixed CSA internal VIT.
The default DSPSIZE is 0, meaning the data space will not be used. Valid
values are 0 through 5, where a value of 1 is equal to 10 megabytes, a value of
2 is equal to 20 megabytes, and so on.
FRAMES
applies only when TYPE=NETCTLR. For a start/stop line, ALL is the only
option. If DATA is specified on a start/stop line, it is ignored and the command
proceeds as if ALL were specified. For SDLC and BSC lines, either DATA or
ALL can be specified, with DATA being the default.
FRAMES=ALL
specifies that all frames (meaning control and data frames) are to be traced
by the cluster control unit.
FRAMES=DATA
specifies that only data frames are to be traced by the cluster control unit.
ID=name
specifies the name of the resource for which tracing is to be done. Only active
resources can be traced. This operand does not apply when TYPE=MODULE
or TYPE=VTAM.

Names of various types of resources can be specified, depending on the value

of the TYPE operand. The different resources and the traces that can be
specified for them (with the TYPE operand) are shown in Figure 5 on page 370
and are described in the following section.

For TYPE=BUF, TYPE=IO, TYPE=GPT, or TYPE=STATE, the name can be a

network-qualified name. If name is an ACB name, and the ACB name matches
the name on the APPL definition statement, then you can use a
network-qualified ACB name.

368 SNA Operation

 MODIFY TRACE
For TYPE=BUF, TYPE=IO, or TYPE=STATE for a CDRM, you can specify a
network-qualified name, but this does not remove the restriction that the
non-network-qualified CDRM name must be unique across networks.

Chapter 2. VTAM Operator Commands 369

MODIFY TRACE

MODIFY TRACE

LL
LL

LL
=A
=A

=A
PE
PE

PE
GP CO

SI TLR
BU CO

NE LE
CO
S

E
S

DU

AM
TC

AT
M

,S

E
T,
IT

S
F,

O
F

MO
LIN

T
SM
CN

GP

TG
BU

EX

VT
ST

TS
IO
IO
ID=
Adjacent CP major node
Application program major node
Application program minor node
Channel-attachment major node
Channel link
Channel link station
CDRSC major node
CRDSC minor node
Dynamic CDRSC major node
Dynamic CDRSC minor node
CDRM major node
CDRM minor node
XCA major node
Nonswitched line
Link station
Switched line
Local non-SNA major node
Local non-SNA logical unit
Local SNA major node
Local SNA physical unit
Local SNA logical unit
NCP major node
Nonswitched line
Switched line
Link station
Physical unit
Logical unit
Switched major node
Switched physical unit
Switched link station
Switched logical unit
Dynamic switched major node
Dynamic switched physical unit
Dynamic switched logical unit
TCP/IP major node
Nonswitched line
Physical unit
IBM 3710-attached resource
Host physical unit
ISTEXCAA
ISTIRN
ISTNOTIF
ISTTOPAG
PDPIUBUF
SAWBUF
VTAM
VTAMBUF
RTP major node
TRL major node

Figure 5. Resource and Trace Reference

v For TYPE=BUF or TYPE=IO, any of the following names can be specified

along with the SCOPE=ALL operand to trace message activity with the
named resource and, if applicable, all of the resource’s subordinate nodes:

370 SNA Operation

 MODIFY TRACE
– The name of an NCP major node
– The name of the following major nodes (only TYPE=IO,SCOPE=ALL can
be specified):
- Channel-attachment major node
- TCP/IP major node
- XCA major node.
– The name of a line attached to a communication adapter (only
TYPE=IO,SCOPE=ONLY can be specified)
– The name of a line attached to a TCP/IP major node
– The name of a switched line that has a physical unit attached to it
– The name of one of following types of physical units:
- Channel-attached SNA physical unit
- An active physical unit defined in a TCP/IP major node
- Switched physical unit
– The name of a logical unit
– The name of the host CDRM.

Note: If you do a trace for a host CDRM, any subordinate minor nodes
also have trace turned on.

Any of the following names can be specified to trace message activity with
the named resource:
– Host physical unit (for a trace of all PIUs between this host and another
PU type 4 or PU type 5)
– ISTIRN (with TYPE=IO only, for an IO trace of all PIUs passing through
this host that are received from a channel-attached PU type 4 or type 5
and are being sent to another channel-attached PU type 4 or type 5)
– VTAM (for a trace of all SSCP sessions)
– The name of an NCP
– The name of a logical unit (including application programs)
– The name of a local non-SNA minor node
– The name of a CDRM (only in a multiple-domain or multiple-network
environment)
– The name of a CDRSC
– The name of the internal or external CMIP application program (for
TYPE=BUF only). For the VTAM topology agent, node_name is
ISTTOPAG. For notification services, node_name is ISTNOTIF. For
external CMIP application programs, node_name is the application name
defined as the ACB name of the application program major node. In the
following example, APPL1 is the name of the CMIP application program,
as defined in the name field of the APPL definition statement.
APPL1 APPL PRTCT=ADRAPL01

The host CP can be traced as an application program minor node, and

adjacent CPs can be traced as CDRSC minor nodes.
v For TYPE=CNM, the ID operand specifies one of the following:
– PDPIUBUF, to start the problem determination PIU buffer trace
– SAWBUF, to start the session awareness buffer trace

Chapter 2. VTAM Operator Commands 371

MODIFY TRACE
v For TYPE=EXIT, the ID operand is required and must be specified as
ISTEXCAA, ISTEXCCS or ISTEXCDM.
v For TYPE=GPT, the ID operand specifies the name of the NCP resource for
which tracing is to be done:
– An NCP major node (and all of its resources) that is active or pending
active
– An NCP switched or nonswitched line

Note: The ID operand of MODIFY TRACE cannot specify an NCP

switched line that is a switched subarea connection.
– An active LU that has been dynamically reconfigured within the NCP
– An active PU on an NCP switched line
– An active or inactive PU on an NCP nonswitched line
– An active PU that is dynamically reconfigured within the NCP
– An active or inactive LU associated with an active PU on a switched line
– An active or inactive LU associated with a PU (active or inactive) on a
nonswitched line
– An active or inactive independent LU associated with a PU (ALS) in an
NCP major node or a switched PU connected by an NCP link. The state
(active or inactive) of the PU with which the independent LU is associated
must be as follows:
- If it has been dynamically reconfigured within the NCP, the PU must be
active
- If it is on an NCP switched line, the PU must be active.
- If it is on an NCP nonswitched line, the PU can be either active or
inactive.

The SSCP and host CP are not valid resources for a GPT trace, but the
adjacent CP can be traced as a CDRSC minor node.
v For TYPE=NETCTLR, the ID operand specifies the name of the physical unit
representing the device for which the trace is to be started. (VTAM is not
required to own or have knowledge of the 3710.) VTAM sends the name of
the PU specified on the ID operand to the 3710 specified on the PU operand.
If a 3710 is to be simultaneously traced over more than one line, use a
separate MODIFY TRACE command to start each trace.

Note: It is not necessary that the resource specified by the ID operand be

another 3710.
v For TYPE=LINE or TYPE=SIT, the ID operand specifies the name of the line
for which tracing is to be done.
ID cannot specify a line attached to a communication adapter or the name of
a transmission group through a communication adapter.
v For TYPE=SMS the ID operand is optional. If it is omitted, ID=VTAMBUF will
be used for an SMS trace.
v For TYPE=STATE, the ID operand specifies the name of the resource for
which state tracing is to be done.
v For TYPE=TG, the ID operand specifies the name of a nonswitched line
currently within the transmission group to be traced. All the lines in the
transmission group are traced as if they were a single logical line.
v For TYPE=TSO, the ID operand specifies the TSO user ID for which tracing
is to be done.

372 SNA Operation

 MODIFY TRACE
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE identifies which resources the
command should act on. IDTYPE applies to TYPE=BUF, TYPE=IO, TYPE=GPT,
and TYPE=STATE.
IDTYPE=CP
starts tracing for the control point (CP) with the name specified on the ID
operand. The CP that is traced can be the host CP or a CDRSC
representing an adjacent CP.
IDTYPE=SSCP
starts tracing for the system services control point (SSCP) with the name
specified on the ID operand.
IDTYPE=RESOURCE
starts tracing for a CP, an SSCP, or another resource with the name
specified on the ID operand. If both an SSCP and a CP are found, VTAM
starts tracing for both of them.
LINE=line_name
applies only to TYPE=NETCTLR. It specifies the name of a link that is attached
to the 3710 that is to be traced. The 3710 performing the trace (named on the
PU operand) copies the SDLC, BSC, and S/S data link control frames that are
transmitted or received on that link for the physical unit named by the ID
operand. VTAM has no knowledge of this link. VTAM sends the name of the link
specified on the LINE operand to the 3710 specified on the PU operand.
MODE
applies only to TYPE=VTAM. It specifies that the VTAM internal trace is to
record its data on an internal, wraparound table (MODE=INT) or an external
trace file (MODE=EXT).

You can record trace data internally and externally at the same time. If desired,
you can have different sets of trace options active for internal and external
recording. VTAM always runs with MODE=INT and the default trace options,
regardless of whether you request tracing.

You must run specific operating system utilities to trap, format, and view
external trace output. See OS/390 eNetwork Communications Server: SNA
Diagnosis for more information about use of these operating system utilities.

Do not specify MODE=EXT and SIZE on the same command.

MODE=INT
specifies that the VTAM internal trace is to record its data on an internal,
wraparound table.
MODE=EXT
specifies that the VTAM internal trace is to record its data on an external
trace file as well as on an internal, wraparound table.
OPTION
applies to TYPE=EXIT, TYPE=MODULE, TYPE=STATE and TYPE=VTAM.

For TYPE=EXIT, OPTION specifies the functions of the session management

exit (SME) for which tracing is to be started.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(BEGIN,INITAUTH,ACCTING).

Chapter 2. VTAM Operator Commands 373

MODIFY TRACE
For TYPE=MODULE, OPTION specifies the types of processing modules for
which tracing is to be started.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(COMMAND,SESSION).

For TYPE=STATE, OPTION specifies the types of resources for which resource
states are to be recorded. The data is recorded using the mode (internal or
external) specified for the SSCP VIT option.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(APPL,GROUP,NCP).

For TYPE=VTAM, OPTION specifies the VTAM internal functions for which
trace data is to be recorded.

You can specify different options for internal and external recording. The default
options for internal recording (MODE=INT) are API, MSG, NRM, PIU, PSS,
SMS, and SSCP. Except for PSS and SMS which can be turned off, these
options are always active for internal recording. If you stop them, VTAM
immediately restarts them. For external recording (MODE=EXT), there are no
default options. You can start or stop any options.

Note: Although the default options are always active, these options do not
appear in DISPLAY TRACES output unless you have specified them on
the MODIFY TRACE command or the TRACE,TYPE=VTAM start option.

If more than one option is selected, separate them with commas and enclose
the list in parentheses; for example OPTION=(API,NRM,SSCP). For information
on what is traced for each internal function, see the OS/390 eNetwork
Communications Server: SNA Diagnosis.
OPTION=ALL
applies to TYPE=EXIT, TYPE=MODULE, TYPE=STATE, and TYPE=VTAM.

Note: Turning on all traces slows performance.

For TYPE=EXIT, it starts the tracing of all functions of the session

management exit (SME).

For TYPE=MODULE, it starts the tracing of all the modules shown on the
OPTION operand for which TYPE=MODULE apply.

For TYPE=STATE, it starts the tracing of resource states for all of the
resource types shown on the OPTION operand for which TYPE=STATE
apply.

For TYPE=VTAM, it starts the VTAM internal trace for all of the VTAM
internal functions for which the VTAM internal trace is available. Exception
trace entries continue to be recorded.

For TYPE=EXIT, you can also specify the following options:

OPTION=ACCTING
starts tracing the initial and final accounting function of the session
management exit (SME).

374 SNA Operation

 MODIFY TRACE
OPTION=ADJSSCP
starts tracing the adjacent SSCP selection function of the session
management exit (SME).
OPTION=ALIAS
starts tracing the alias translation function of the session management exit
(SME).
OPTION=ALS
starts tracing the adjacent link station function of the session management
exit (SME).
OPTION=BEGIN
starts tracing the begin function of the session management exit (SME).
OPTION=END
starts tracing the end function of the session management exit (SME).
OPTION=GWPATH
starts tracing the gateway path list function of the session management exit
(SME).
OPTION=INITAUTH
starts tracing the initial authorization function of the session management
exit (SME).
OPTION=REPL
starts tracing the exit replacement function of the session management exit
(SME).
OPTION=SECAUTH
starts tracing the secondary authorization function of the session
management exit (SME).
OPTION=VRSEL
starts tracing the virtual route selection function of the session management
exit (SME).
OPTION=XRF
starts tracing the XRF session switch function of the session management
exit (SME).

For TYPE=MODULE, you can also specify the following options:

OPTION=COMMAND
starts tracing modules involved in command processing.
OPTION=CONNECTION
starts tracing modules involved in setting up connections between nodes.
OPTION=DEFINITION
starts tracing modules involved in resource definition processing.
OPTION=INTERFACES
starts tracing modules involved in the interface with the host SSCP or the
host CP.
OPTION=MANAGEMENT
starts tracing modules involved in network management.
OPTION=NOEXIT
specifies that module exits are not traced for modules associated with other
OPTION values for TYPE=MODULE. Module exits are not traced for any

Chapter 2. VTAM Operator Commands 375

MODIFY TRACE
modules until a subsequent MODIFY
NOTRACE,TYPE=MODULE,OPTION=NOEXIT command is issued.

Starting a module trace for any OPTION with TYPE=MODULE starts the
tracing of the module exits also, unless you specify OPTION=NOEXIT.
OPTION=PURGE
causes all information currently held in module tracing buffers to be written
to VTAM internal trace (VIT) entries. Upon completion of the command, new
information is written to the module tracing buffers.
OPTION=SESSION
starts tracing modules involved in session establishment.

For TYPE=STATE, you can also specify the following options:

OPTION=ADJCP
starts tracing the states of all adjacent control points.
OPTION=APPL
starts tracing the states of all application programs.
OPTION=CDRM
starts tracing the states of all CDRMs.
OPTION=CDRSC
starts tracing the states of all CDRSCs.
OPTION=GROUP
starts tracing the states of all line groups.
OPTION=LINE
starts tracing the states of all lines.
OPTION=LNKST
starts tracing of link stations.
OPTION=LU
starts tracing the states of all logical units.
OPTION=NCP
starts tracing the states of all NCPs.
OPTION=PU
starts tracing the states of all physical units.

For TYPE=VTAM, you can also specify the following options:

OPTION=API
starts tracing the application program interface.
OPTION=APPC
starts tracing LU 6.2 communication.
OPTION=CFS
starts tracing coupling facility services.
OPTION=CIO
starts tracing channel I/O for channel-attached devices and for lines
attached to a communication adapter.
OPTION=CMIP
starts tracing internal events in CMIP services and the VTAM topology
agent.

376 SNA Operation

 MODIFY TRACE
OPTION=CSM
starts tracing of the communications storage manager.
OPTION=ESC
starts tracing execution sequence control.
OPTION=HPR
starts tracing for HPR.
OPTION=LCS
starts tracing LAN channel stations.
OPTION=LOCK
starts tracing locking.
OPTION=MSG
starts tracing messages.
OPTION=NRM
starts tracing network resource management
OPTION=PIU
starts tracing path information units.
OPTION=PSS
starts tracing process scheduling services.
OPTION=SMS
starts tracing storage management services.
OPTION=SSCP
starts tracing the system services control point.
OPTION=TCP
starts tracing the VTAM to TCP/IP interface events. This option is used only
with the AnyNet function.
OPTION=VCNS
starts tracing VTAM common network services.
OPTION=XBUF
starts tracing of extended buffer list information.
OPTION=XCF
starts tracing XCF communication.
PU=3710_pu_name
applies only when TYPE=NETCTLR. It specifies the name of the IBM 3710
Network Controller that is to perform the trace. VTAM rejects the command if
the physical unit is not known to VTAM.
SAVE
applies to TYPE=BUF, TYPE=IO, and TYPE=STATE. It specifies whether the
trace command should be saved for the resource named on the ID operand.
SAVE=YES
VTAM saves the trace command for the resource named on the ID
operand. If the resource exists when this command is issued, the trace
starts immediately. If the resource does not exist when this command is
issued, VTAM saves the trace command and starts the trace when the
resource is defined.

Note: For TYPE=BUF, TYPE=IO, and TYPE=STATE, if you start a trace

with IDTYPE=RESOURCE and a CP or an SSCP (but not both)

Chapter 2. VTAM Operator Commands 377

MODIFY TRACE
exists when the command is issued, VTAM starts the trace for the
existing resource and saves the trace commands for both resources.
If both a CP and an SSCP exist when the command is issued, VTAM
starts tracing for them immediately.

You can also issue this command to update a previously saved trace
command.

Use the MODIFY NOTRACE command to delete a saved trace command.

VTAM will not delete a saved trace command until you issue a MODIFY
NOTRACE command for it, even though the resource might be created and
freed or activated and deactivated several times. Saved trace commands
are lost when VTAM is halted and restarted.
SAVE=NO
does not save the MODIFY TRACE command. If the resource does not
exist when you issue MODIFY TRACE, the command fails.
SCOPE
applies when TYPE=BUF, TYPE=IO, or TYPE=GPT. It specifies the scope of
the trace.

You can specify the SCOPE operand for TYPE=GPT, but it is meaningful only
for the NCP node. SCOPE=ALL is assumed for a GPT trace of all other node
types.
SCOPE=ALL
starts traces for all nodes subordinate to the specified node. If an LU that is
subordinate to a node is an independent LU, it is not considered to be
subordinate to the node for the purpose of tracing.

SCOPE=ALL is not valid for the host PU trace or for the host intermediate
routing node trace (ID=ISTIRN). If SCOPE=ALL is specified, VTAM issues a
message and uses SCOPE=ONLY.

For an I/O trace of a channel-attached NCP, SCOPE=ALL provides a trace

of all channel I/O, including network message traffic routed through the
channel-attached NCP.
SCOPE=ONLY
starts a trace only for the specified node.

SCOPE=ONLY on a GPT trace command for the NCP PU limits the trace to
RUs that flow on the SSCP-PU session for the NCP.
SIZE=size
applies only to TYPE=VTAM,MODE=INT. It specifies the number of pages to be
allocated for the internal trace table. Page size is 4K. Integers 1–999 can be
specified.

If you omit this option, the default size is 100.

If you specify a value less than 100, 100 will be used instead.

After the VTAM internal trace is started, the SIZE operand does not have a
default. If successive MODIFY commands change other options, the SIZE
specification remains the same until re-specified on a MODIFY command.

378 SNA Operation

 MODIFY TRACE
If the SIZE value is too small, trace information might be lost because of
wraparound in the internal trace table. Also, if the SIZE operand specifies a size
different from the current table size, information is lost because the trace table
is freed when another table with a new size is obtained. When an attempt to
increase the SIZE value fails because of insufficient storage, the internal trace
table size is set to the default size, not the size you requested.
TRACEPT=trace_point_id
applies to TYPE=SIT and is valid only if you are tracing connectivity subsystem
(CSS) resources on an IBM 3745 Communication Controller. This operand
specifies the point in the microcode at which tracing should be activated. If you
omit this operand, tracing is done for all valid trace points. The TRACEPT
operand allows you to limit the tracing to a single trace point if too much output
is being produced.

VTAM accepts any integer in the range 1–255; however, only a few values are
defined by the NCP. For information on which values are defined and what they
mean, see the NCP, SSP, and EP Diagnosis Guide.
TYPE
specifies the kind of trace that is to be affected. More than one kind of trace
can be active at the same time, but you must start or change each trace with a
separate MODIFY TRACE command.
TYPE=BUF
starts the tracing of text that passes through VTAM buffers on the way to or
from the node identified by the ID operand. The SCOPE operand can be
used to extend the scope of the trace to all nodes subordinate to the
specified node. This trace is useful when one of the logical units in the
session is an application program in this domain.
TYPE=CNM
starts a communication network management trace.

Note: When this option is specified, the generalized trace facility (GTF)
must be active with the TRACE=USR option specified.
TYPE=EXIT
starts the tracing of functions of the session management exit (SME).
TYPE=GPT
starts an NCP generalized PIU trace (GPT) for the resources identified by
the ID operand.

Note: The ID operand of MODIFY TRACE cannot specify:

v An NCP switched line that is a switched subarea connection
v A dynamic CDRSC.
TYPE=IO
starts a trace of I/O activity associated with the node identified by the ID
operand. The SCOPE operand can be used to extend the scope of the
trace to all nodes subordinate to the specified node. In addition, for an NCP
major node with an active channel attachment, the SCOPE=ALL operand
provides a trace of all I/O going across the channel, including cross-domain
session I/O.

Note: The external VIT is now used to record the IO trace entries. PIU,
NLPI, NLPO, LSNA, and MPTNFMT entries may be written for a
specific IO trace invocation.

Chapter 2. VTAM Operator Commands 379

MODIFY TRACE
TYPE=LINE
starts an NCP line trace for the line identified by the ID operand.
TYPE=MODULE
starts module tracing for the options specified on the OPTION operand.
TYPE=NETCTLR
sends a trace request to the 3710 named on the PU operand.
TYPE=SIT
starts a scanner interface trace (SIT) through the communication scanner
processor located in the IBM 3720 or 3745 Communication Controller
containing the NCP identified by the line specified by the ID operand.

The scanner interface trace and the NCP line trace can be started
separately, and can be active at the same time.
TYPE=SMS
starts a storage management services (SMS) trace to record VTAM buffer
pool usage data.
TYPE=STATE
starts a resource state trace to record the changing states of resources.
TYPE=TG
starts an NCP transmission group trace for the transmission group (TG)
containing the NCP line identified by the ID operand. A line is part of a
transmission group only when both the line and its subordinate link station
are active. A transmission group trace can be started by naming any line
within the transmission group. Once a transmission group trace is started,
another trace of the same transmission group cannot be requested by
naming the same or another line within the transmission group in another
MODIFY TRACE command.

If the line or its link station subsequently fails or is deactivated (that is, if the
line is removed from the transmission group), the transmission group trace
is ended, even though the transmission group continues to operate if there
are any remaining lines in the transmission group. The trace can be
restarted, naming another line in the transmission group.

The NCP line trace and the transmission group trace are mutually exclusive
for a particular line. Therefore, when starting a transmission group trace,
select a line that is not being used, and is not likely to be used, for a line
trace.
TYPE=TSO
starts a TSO component trace for the user ID identified by the ID operand.
GTF must be active when this trace option is specified.
TYPE=VTAM
starts the VTAM internal trace (VIT) for the components specified by the
OPTION operand. If OPTION is omitted, no new component internal traces
are initiated; rather, VTAM issues messages identifying the components for
which the internal trace is currently active.

380 SNA Operation

 MODIFY USERVAR

MODIFY USERVAR Command

Create a new USERVAR:

,OPTION=UPDATE
ÊÊ MODIFY procname,USERVAR ,ID=uservar_name Ê

,TYPE=DYNAMIC ,APPC=NO,UVEXIT=NO
Ê ,VALUE=appl_name ÊÍ
,TYPE= DYNAMIC ,APPC= YES,UVEXIT=NO
STATIC NO,UVEXIT= YES
VOLATILE NO

Update an existing USERVAR and change the TYPE:

,OPTION=UPDATE
ÊÊ MODIFY procname,USERVAR ,ID=uservar_name Ê

,APPC=NO,UVEXIT=NO
Ê ,TYPE= DYNAMIC ÊÍ
,VALUE=appl_name STATIC ,APPC= YES,UVEXIT=NO
VOLATILE NO,UVEXIT= YES
NO

Update an existing USERVAR, leaving the TYPE unchanged:

,OPTION=UPDATE
ÊÊ MODIFY procname,USERVAR ,ID=uservar_name Ê

,APPC=NO,UVEXIT=NO
Ê ,VALUE=appl_name ÊÍ
,APPC= YES,UVEXIT=NO
NO,UVEXIT= YES
NO

Delete a USERVAR:

ÊÊ MODIFY procname,USERVAR ,ID=uservar_name ,OPTION=DELETE Ê

Ê ÊÍ
,VALUE=appl_name

Abbreviations
Operand Abbreviation
MODIFY F
NO N
OPTION OPT
OPTION=DELETE OPT=DEL
OPTION=UPDATE OPT=UP

Chapter 2. VTAM Operator Commands 381

MODIFY USERVAR
Operand Abbreviation
TYPE=DYNAMIC TYPE=DYN
TYPE=STATIC TYPE=STA
TYPE=VOLATILE TYPE=VOL
VALUE=value VAL=value
YES Y

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
OPTION=DELETE, code only OPT=DEL. Do not code OPTION=DEL.

Purpose
The MODIFY USERVAR command is issued by a network operator or application
subsystem to define, change, or delete the name of an application associated with
a USERVAR.

You cannot create or modify automatic (VTAM-managed) USERVARs using the

MODIFY command; they are created and maintained by VTAM. If you issue a
MODIFY command that specifies the name of an automatic USERVAR as its target,
VTAM assumes that you are taking over control of the USERVAR (by changing its
class from automatic to user) and that you are responsible for any future updates to
that USERVAR. Whenever an automatic USERVAR is changed to a user-managed
USERVAR, the operator should delete the USERVAR for VTAM to take control of it
once again.

Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.
APPC
specifies how the USERVAR ID affects LU 6.2 sessions that were established
with APPC/VTAM application programs.

This operand is valid only when the application program specified on the
VALUE operand executes on the same host that is processing this operator
command. This operand is valid only when OPTION=UPDATE and UVEXIT=NO
are specified or assumed by default.

If you specify OPTION=DELETE, APPC=NO is assumed by default. If you

specify APPC=YES and UVEXIT=YES, both APPC=NO and UVEXIT=NO are
assumed by default.

If you are updating an existing USERVAR and you do not specify a value for
APPC, the previously defined value will be replaced with the default value found
in the operation-level USS table (ISTINCNO). The IBM-supplied default value is
APPC=NO.

382 SNA Operation

 MODIFY USERVAR
APPC=NO
specifies that the USERVAR ID is not used to replace the application
program’s name when establishing LU 6.2 sessions for any application
programs identified in the VALUE operand.
APPC=YES
specifies that the USERVAR ID is used to replace the application program’s
name when establishing LU 6.2 sessions only for APPC/VTAM application
programs identified in the VALUE operand.

If an LU 6.2 application uses a USERVAR ID with the operand APPC=YES,

you cannot define another USERVAR ID with APPC=YES for that
application.
ID=uservar_name
specifies the USERVAR. It can be used to specify any valid USERVAR (1–8
alphanumeric characters, the first of which must be alphabetic). VTAM uses this
USERVAR during the logon process to send the session request to the
currently active application subsystem. The USERVAR is also specified in the
LOGCHAR operand used to add an entry to the interpret table.

Note: If ID is specified using a reserved name (for example, ID=VTAM),

inconsistent results will occur.
OPTION
specifies whether the USERVAR identified by the ID operand is to be assigned
a value, have its current value changed, or be deleted.
OPTION=UPDATE
specifies that the USERVAR identified by the ID operand is to be assigned
a value, or that the current value of an existing USERVAR is to be changed.
OPTION=DELETE
specifies that the USERVAR identified by the ID operand is to be deleted. If
used with the VALUE operand, the USERVAR is deleted only if the
specified value matches that of the USERVAR.
TYPE
specifies the type (or attributes) of a USERVAR.
TYPE=DYNAMIC
specifies that, in event of failure, the value of the USERVAR identified by
the ID operand is to be queried again by those SSCPs having automatic
USERVARs with the same name. The default value for the TYPE operand
is used only when a USERVAR table entry is being created. It is not used
on each execution of the MODIFY USERVAR command.
TYPE=STATIC
specifies that the value of the USERVAR will not change. Those SSCPs
having automatic USERVARs with the same name only need to query the
USERVAR if the value is unknown.
TYPE=VOLATILE
specifies that the value of the USERVAR identified by the ID operand is to
be queried again before any session setup is attempted because the value
is likely to change.
UVEXIT
specifies whether an installation-wide exit routine is to be used for the
USERVAR. For more information about installation-wide exit routines identified
by the UVEXIT operand, see OS/390 eNetwork Communications Server: SNA

Chapter 2. VTAM Operator Commands 383

MODIFY USERVAR
Customization. This operand is valid only when APPC=NO and
OPTION=UPDATE are specified or assumed by default.

If you specify OPTION=DELETE, UVEXIT=NO is assumed by default. If you

specify APPC=YES and UVEXIT=YES, both APPC=NO and UVEXIT=NO are
assumed by default.

If you are updating an existing USERVAR and you do not specify a value for
UVEXIT, the previously defined value will be replaced with the default value
found in the operation-level USS table (ISTINCNO). The IBM-supplied default
value is UVEXIT=NO.
UVEXIT=NO
specifies that the USERVAR installation exit is not used for this USERVAR.
UVEXIT=YES
specifies that the USERVAR installation exit is used for this USERVAR.
VALUE=appl_name
specifies the name of an application program. Any session initiated with the
USERVAR name specified in the ID operand is initiated with the application
program named by appl_name.

Note: If VALUE is specified using a reserved name (for example

VALUE=VTAM), inconsistent results will occur. The name can be a
network-qualified name. If appl_name is a network-qualified name, the
name (both the network identifier and the resource name) is considered
to be a real name and cannot change.

If appl_name is not a network-qualified name, the name uses the network

identifier that was specified on the session request if one is specified. If a
network identifier is not specified on the session request, and if the USERVAR
is in the OLU domain, the name can represent any resource with that name in
any network and the network identifier is filled in when a resource is found with
that name. If the USERVAR is not in the OLU domain, the value must be
predefined in the VTAM that contains the USERVAR. In addition, if the
USERVAR is represented by a CDRSC, the CDRSC must be predefined with a
network identifier.
Notes:
1. When a VTAM in an APPN network receives a request containing a
USERVAR name, the user-managed USERVAR must be defined on the
same node as the real resource. Therefore, when the real resource is on an
end node, define the USERVAR at the end node and not at its network
node server.
2. When an interchange node receives a request containing a USERVAR
name from the APPN network, the real resource must be located on the
interchange node or through an adjacent SSCP attached to the interchange
node (that is, not in the APPN network attached to the interchange node).

The output from the DISPLAY USERVAR command for this USERVAR includes
network-qualified names only if appl_name is a network-qualified name on the
MODIFY USERVAR command.

If appl_name is an ACB name, and the ACB name matches the name on the
APPL definition statement, then you can use a network-qualified ACB name.

384 SNA Operation

 MODIFY VTAMOPTS

MODIFY VTAMOPTS Command

(1)
ÊÊ MODIFY procname,VTAMOPTS Ê
,APPNCOS=class-of-service_name

Ê Ê
,ASIRFMSG= ALLSSCP ,AUTHLEN= NO
OLUSSCP YES
NONE

Ê Ê
,AUTORTRY= AUTOCAP ,AUTOTI=time_period
CDRM
ALL
NONE

(2) (3)
Ê Ê
,BNDYN= NONE ,BNORD= DEFINED
LIMITED PRIORITY
FULL

Ê Ê
,BSCMDRS= STATS ,CDRDYN= YES
NOSTATS NO
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS

(5)
Ê Ê
(4) ,CMPMIPS=compression_ratio
,CDSREFER=number_of_CDSs

(6)
Ê Ê
,CMPVTAM=compression_level ,CONNTYPE= APPN
LEN

(7)
Ê Ê
,CPCP= YES ,CSALIMIT= value
NO (value )
LEASED ,F
SWITCHED

Ê Ê
,CSA24= value ,DIALRTRY= YES
(value ) NO
,F

Chapter 2. VTAM Operator Commands 385

MODIFY VTAMOPTS
(8) (9)
Ê Ê
,DIRSIZE=number_of_resources ,DIRTIME=time_period

Ê Ê
,DISCNTIM=(time_period1,time_period2) ,DLRORDER= STATNID
CPNAME

Ê Ê
,DSPLYDEF=number_of_messages ,DSPLYWLD= FULLWILD
NOWILD
OPERONLY
POAONLY

Ê Ê
DUPDEFS= ALL ,DYNDLGMD= logmode_name
NONE NONE
APPL
DEPLU

Ê Ê
,DYNMODTB= table_name ,ENCRPREF= NONE
NONE value

(10)
Ê Ê
,ENCRYPTN= YES ,ESIRFMSG= ALLSSCP
NO OLUSSCP
CCA NONE
CUSP
24
31

Ê Ê
,FSIRFMSG= ALLSSCP HOTIOTRM=percentage_of_buffer_pool
OLUSSCP
NONE

Ê Ê
,HPRNCPBF= YES
NO

Ê Ê
HPRPST=(low_limit,med_limit,high_limit,network_limit)

Ê Ê
,INOPDUMP= ON ,IOINT=number_of_seconds
OFF

Ê Ê
,IOMSGLIM=number_of_message_pairs (11)
IPADDR=ip_address

386 SNA Operation

 MODIFY VTAMOPTS
Ê Ê
,ISTCOSDF= ALL LIMINTCP=number_of_seconds
APPL
DEPLU
INDLU
NONE
,

( » APPL )
DEPLU
INDLU

(12)
Ê Ê
,MAXLOCAT=max_locate_congestion_threshhold

Ê Ê
,MAXSSCPS=number_of_sscps ,MIHTMOUT=units_of_time

Ê Ê
,MSGLEVEL= BASE ,MSGMOD= YES
V4R1 NO
V4R2
V4R3
V4R4
CS390

Ê Ê
(13) ,NQNMODE= NAME
,NNSPREF= NONE NQNAME
network_node_server

(14)
Ê Ê
,NUMTREES=number_of_routing_trees

Ê Ê
OSIEVENT= ALL OSIMGMT= YES
NONE NO
(15)
PATTERNS

Ê Ê
(16) ,PDTRCBUF=number_of_buffers
OSITOPO= ALLCDRSC
ILUCDRSC

Ê Ê
,PIUMAXDS=calculation_factor ,PLUALMSG= SUPPRESS
NOSUPP

Ê Ê
,PPOLOG= YES
NO

Chapter 2. VTAM Operator Commands 387

MODIFY VTAMOPTS
Ê Ê
PSRETRY=(low_tp_int,med_tp_int,high_tp_int,network_tp_int)

(17) (18)
Ê Ê
,RESUSAGE=usage_limit ,ROUTERES=resistance_value

Ê Ê
,SAWMXQPK=calculation_factor

Ê Ê
,SDLCMDRS= YES
NO
STATS
NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS

Ê Ê
,SIRFMSG= ALLSSCP ,SLUALMSG= SUPPRESS
OLUSSCP NOSUPP
NONE

(19) (20)
Ê Ê
,SNVC=subnet_visit_count ,SORDER= ADJSSCP
APPN
APPNFRST
SUBAREA

(21)
Ê Ê
,SRCHRED= OFF ,SRCOUNT=number_of_search_requests
ON

(22)
Ê Ê
,SRTIMER=number_of_seconds ,SSDTMOUT=number_of_seconds

(23)
Ê Ê
,SSEARCH= YES ,SUPP= NOSUP
NO INFO
CACHE WARN
NORM
SER

Ê Ê
,SWNORDER= CPNAME (24)
STATNID TCPNAME=tcp_job-name

388 SNA Operation

 MODIFY VTAMOPTS

Ê Ê
UPDDELAY=maximum_time VFYRED= YES
NO

(25) (26)
Ê Ê
VFYREDTI= OFF ,VRTG= YES
0 NO
reduction_timer

(27)
Ê ÊÍ
,VRTGCPCP= YES
NO

Notes:
1. APPNCOS can be modified only if NODETYPE was specified during VTAM
START processing.
2. BNDYN can be modified only if BN=YES was specified during VTAM START
processing.
3. BNORD can be modified only if BN=YES was specified during VTAM START
processing.
4. CDSREFER can be modified only if NODETYPE=NN and CDSERVR=NO
were specified during VTAM START processing.
5. CMPMIPS is meaningful only if the value for CMPVTAM is greater than 1.
6. CONNTYPE can be modified only if NODETYPE was specified during VTAM
START processing.
7. CPCP can be modified only if NODETYPE was specified during VTAM START
processing.
8. DIRSIZE can be modified only if NODETYPE=NN was specified during VTAM
START processing.
9. DIRTIME can be modified only if NODETYPE=NN was specified during VTAM
START processing.
10. The ENCRYPTN start option cannot be modified if ENCRYPTN=NO was
specified during VTAM START processing.
11. IPADDR can be modified but the new value will not be used until all lines in the
XCA major node used for Enterprise Extender are inactive. However, displays
of VTAM start options will show the new value immediately. Any susequent line
activation from the Enterprise Extender XCA major node will make use of the
new IPADDR value.
12. MAXLOCAT can be modified only if NODETYPE was specified during VTAM
START processing.
13. NNSPREF can be modified only if NODETYPE=EN was specified during
VTAM START processing.
14. NUMTREES can be modified only if NODETYPE=NN was specified during
VTAM START processing.
15. OSIEVENT=PATTERNS is not valid when OSIMGMT=YES.
16. OSITOPO=ALLCDRSC is not valid when OSIMGMT=YES.
17. RESUSAGE can be modified only if NODETYPE=NN was specified during
VTAM START processing.

Chapter 2. VTAM Operator Commands 389

MODIFY VTAMOPTS
18. ROUTERES can be modified only if NODETYPE=NN was specified during
VTAM START processing.
19. SNVC can be modified only if BN=YES was specified during VTAM START
processing.
20. SORDER can be modified only if VTAM has been started as a network node,
interchange node, or migration data host.
21. SRCOUNT is meaningful only when SRCHRED=ON.
22. SRTIMER is meaningful only when SRCHRED=ON.
23. SSEARCH can be modified only if NODETYPE=NN was specified during
VTAM START processing.
24. TCPNAME can be modified but the new value will not be used until all lines in
the XCA major node used for Enterprise Extender are inactive. However,
displays of VTAM start options will show the new value immediately. Any
subsequent line activation from the Enterprise Extender XCA major node will
make use of the new TCPNAME value.
25. VFYREDTI can be modified only if NODETYPE=NN was specified during
VTAM START processing.
26. VRTG can be modified only if NODETYPE and HOSTSA are specified.
27. VRTGCPCP can be modified only if NODETYPE and HOSTSA are specified.

Abbreviations
Operand Abbreviation
MODIFY F
MSGLEVEL MSGLVL
PLUALMSG=NOSUPP PLUALMSG=NOSUP
PLUALMSG=SUPPRESS PLUALMSG=SUPP
SLUALMSG=NOSUPP SLUALMSG=NOSUP
SLUALMSG=SUPPRESS SLUALMSG=SUPP

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
PLUALMSG=SUPPRESS, code only PLUALMSG=SUPP.

Purpose
The MODIFY VTAMOPTS (VTAM start options) command enables you to change
certain values that might have been specified on VTAM start options. See the
OS/390 eNetwork Communications Server: SNA Resource Definition Reference for
descriptions of each of the start options that you can change with this command.

There are no default values on the MODIFY VTAMOPTS command. Only the
values that you specify are affected. Operands that are not specified on the
command are not affected in any way.

Note: If a start option affects individual resources, and you change the value of the
start option with this command, the change does not go into effect until the
major nodes for those resources are deactivated and reactivated. The
command takes effect for major nodes that are activated after you issue this
command and for dynamic cross-network resources that are dynamically
defined after the command is issued.

390 SNA Operation

 MODIFY VTAMOPTS
Operands
procname
is the procedure name for the command. If procname in the START command
was specified as startname.ident, where startname is the VTAM start procedure
and ident is the optional identifier, either startname.ident or ident can be
specified for procname.

If procname in the START command was startname, startname must be

specified for procname.

Chapter 2. VTAM Operator Commands 391

START

START Command
Starting VTAM in an MVS environment:

ÊÊ START procname,,,( Options ) ÊÍ

Notes:
1. The start options are listed in this section alphabetically; however, you can code
them in any order.
2. Precede the option list with three commas and enclose the group of options in
parentheses.
3. Start options that are entered on the START command must be separated by
commas. Do not leave any blanks between options.

Options

ALSREQ=NO
NETID=network_id SSCPID=sscp_id SSCPNAME=name Ê
ALSREQ= YES
NO

(1)
APPNCOS=NONE ASIRFMSG=OLUSSCP
Ê Ê
APPNCOS=class-of-service_name ASIRFMSG= ALLSSCP
OLUSSCP
NONE

ASYDE=TERM AUTHLEN=YES AUTORTRY=AUTOCAP

Ê Ê
ASYDE= KEEP AUTHLEN= NO AUTORTRY= AUTOCAP
TERM YES CDRM
ALL
NONE

(2) (3)
AUTOTI=0 BN=NO BNDYN=LIMITED
Ê Ê
AUTOTI=time_period BN= NO BNDYN= LIMITED
YES NONE
FULL

(4)
BNORD=PRIORITY BSCMDRS=(STATS,INOPS)
Ê Ê
BNORD= PRIORITY BSCMDRS= STATS
DEFINED NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS

392 SNA Operation

 START

BSCTMOUT=286
Ê Ê
BSCTMOUT=units_of_time poolname= ()
Buffer Pool Values

CACHETI=8 CDRDYN=YES
Ê Ê
CACHETI=number_of_minutes CDRDYN= NO
YES
(5)
CDRSCTI=8M CDSERVR=NO
Ê Ê
CDRSCTI=timeout_value CDSERVR= YES
NO

(6)
CDSREFER=1 CINDXSIZ=8176
Ê Ê
CDSREFER=number_of_CDSs CINDXSIZ=table_size

(7)
CMPMIPS=100 CMPVTAM=0
Ê Ê
CMPMIPS=compression_ratio CMPVTAM=compression_level

CNMTAB=ISTMGC00 COLD CONFIG=00

Ê Ê
CNMTAB=cnm_table_name WARM CONFIG= file_id
file_name

(8) (9)
CONNTYPE=APPN CPCDRSC=NO CPCP=LEASED
Ê Ê
CONNTYPE= APPN CPCDRSC= YES CPCP= YES
LEN NO NO
LEASED
SWITCHED

CSALIMIT=0 CSA24=0 DATEFORM=MDY

Ê Ê
CSALIMIT=value CSA24=value DATEFORM= MDY
DMY
YMD

(10)
DIALRTRY=YES DIRSIZE=0
Ê Ê
DIALRTRY= YES DIRSIZE=number_of_resources
NO

(11)
DIRTIME=8D
Ê Ê
DIRTIME=time_period

Chapter 2. VTAM Operator Commands 393

START

DISCNTIM=(15,0) DLRORDER=STATNID
Ê Ê
DISCNTIM=(time_period1,time_period2) DLRORDER= STATNID
CPNAME

(12)
DLRTCB=32 DSPLYDEF=100
Ê Ê
DLRTCB=number_of_task_control_blocks DSPLYDEF=number_of_messages

DSPLYMAX=65535 DSPLYWLD=FULLWILD
Ê Ê
DSPLYMAX=number_of_messages DSPLYWLD= FULLWILD
NOWILD
OPERONLY
POAONLY

(13)
DUPDEFS=ALL DYNADJCP=YES DYNASSCP=YES
Ê Ê
DUPDEFS= ALL DYNADJCP= YES DYNASSCP= YES
NONE NO NO
APPL
LU

DYNDLGMD=NONE DYNHPPFX=*BLANKS*
Ê Ê
DYNDLGMD= logmode_name (14)
NONE DYNHPPFX= prefix

DYNLU=NO DYNMODTB=NONE DYNPUPFX=*BLANKS*

Ê Ê
DYNLU= YES DYNMODTB= table_name DYNPUPFX= prefix¹⁴
NO NONE

DYNVNPFX=*BLANKS* ENCRPREF=NONE ENCRYPTN=YES

Ê Ê
DYNVNPFX= prefix¹⁴ ENCRPREF= NONE ENCRYPTN= YES
value NO
CCA
CUSP
24
31

ENHADDR=NO
Ê Ê
ENHADDR= NO
YES

ESIRFMSG=ALLSSCP FLDTAB=ISTMSFLD
Ê Ê
ESIRFMSG= ALLSSCP FLDTAB= table_name
OLUSSCP NONE
NONE

394 SNA Operation

 START
FSIRFMSG=OLUSSCP GWSSCP=YES HNTSIZE=4080
Ê Ê
FSIRFMSG= ALLSSCP GWSSCP= YES HNTSIZE=table_size
OLUSSCP NO
NONE

HOSTPU=ISTPUS HOSTSA=1
Ê Ê
HOSTPU=host_subarea_pu_name (15)
HOSTSA=subarea_number

(16)
HOTIOTRM=0 HPR=RTP
Ê Ê
HOTIOTRM=percentage_of_buffer_pool HPR= ANR
RTP
NONE
(RTP,ANR)
(RTP,NONE)
(ANR,NONE)

HPRNCPBF=NO
Ê Ê
HPRNCPBF= YES
NO

HPRPST=(8M,4M,2M,1M)
Ê Ê
HPRPST=(low_limit,med_limit,high_limit,network_limit)

(17)
HSRTSIZE=9973 INITDB=ALL
Ê Ê
HSRTSIZE=number_of_queue_pointers INITDB= ALL
DIR
TOPO
NONE

INOPDUMP=OFF IOINT=180
Ê Ê
INOPDUMP= ON IOINT=number_of_seconds
OFF

IOMSGLIM=2147483647 IOPURGE=0
Ê Ê
IOMSGLIM=number_of_message_pairs IOPURGE=timeout_value

Ê
IPADDR=ip_address

Notes:
1. APPNCOS is meaningful only if the NODETYPE start option is also used.
2. BN is meaningful only if the NODETYPE=NN start option is also used.

Chapter 2. VTAM Operator Commands 395

START
3. BNDYN is meaningful only if the BN=YES start option is also used.
4. BNORD is meaningful only if the BN=YES start option is also used.
5. CDSERVR is meaningful only if the NODETYPE=NN start option is also used.
6. CDSREFER is meaningful only if the NODETYPE=NN and CDSERVR=NO
start options are also used.
7. The CMPMIPS start option is meaningful only if the value for CMPVTAM is
greater than 1.
8. CONNTYPE is meaningful only if the NODETYPE start option is also used.
9. CPCP is meaningful only if the NODETYPE start option is also used.
10. DIRSIZE is meaningful only if the NODETYPE=NN start option is also used.
11. DIRTIME is meaningful only if the NODETYPE=NN start option is also used.
12. If the DSPLYMAX start option value is less than 100, that value is the default
for DSPLYDEF.
13. DYNADJCP is meaningful only if the NODETYPE start option is also used.
14. Two character prefix.
15. HOSTSA provides subarea function. If you do not specify HOSTSA, but you
specify NODETYPE, there is no default for HOSTSA and subarea function is
not provided. If you do not specify HOSTSA and NODETYPE, a default of
HOSTSA=1 is assumed and APPN function is not provided.
16. HPR is meaningful only if NODETYPE is also used.
17. INITDB is meaningful only if the NODETYPE=NN start option is also used.

IRNSTRGE=0 ISTCOSDF=INDLU
Ê
IRNSTRGE=size ISTCOSDF= ALL
APPL
DEPLU
INDLU
NONE
( APPL )
DEPLU
INDLU

(1)
LIST=00
Ê Ê
LIMINTCP=number_of_seconds LIST=start_option_list_id

Ê Ê
(2) MAINTLVL=maintenance_level
LISTBKUP= start_option_list_id
DEFAULTS
PROMPT

396 SNA Operation

 START
(3)
MAXLOCAT=5000 MAXLURU=6144
Ê Ê
MAXLOCAT=max_locate_congestion_threshhold MAXLURU=ru_length

MAXSSCPS=10 MAXSUBA=15
Ê Ê
MAXSSCPS=number_of_SSCPs MAXSUBA=maximum_subarea_number

MIHTMOUT=1800 MSGLEVEL=BASE MSGMOD=NO

Ê Ê
MIHTMOUT=units_of_time MSGLEVEL= BASE MSGMOD= NO
V4R1 YES
V4R2
V4R3
V4R4
CS390

MXSAWBUF=10000 MXSSCPRU=4096
Ê Ê
MXSAWBUF=number_of_buffers MXSSCPRU=ru_length

MXSUBNUM=511 NCPBUFSZ=512 NMVTLOG=NPDA

Ê Ê
MXSUBNUM= 255 NCPBUFSZ= 512 NMVTLOG= ALWAYS
511 1024 NEVER
1023 2048 NPDA
2047
4095
8191
16383
32767
65535
(4)
NNSPREF=NONE
Ê Ê
NNSPREF=network_node_server NODELST=name

NQNMODE=NAME
Ê Ê
(5) NQNMODE= NAME
NODETYPE= EN NQNAME
NN

NUMTREES=100
Ê Ê
NSRTSIZE=( netid,size ) (6)
NUMTREES=number_of_routing_trees

OSIEVENT=PATTERNS OSIMGMT=NO OSITOPO=(ILUCDRSC)

Ê Ê
OSIEVENT= ALL OSIMGMT= YES ALLCDRSC
NONE NO OSITOPO=
PATTERNS ILUCDRSC

Chapter 2. VTAM Operator Commands 397

START
OSRTSIZE=43 PDTRCBUF=2
Ê Ê
OSRTSIZE=number_of_queue_pointers PDTRCBUF=number_of_buffers

PIUMAXDS=200 PLUALMSG=NOSUPP
Ê Ê
PIUMAXDS=calculation_factor PLUALMSG= SUPPRESS
NOSUPP

(7)
PPOLOG=NO PROMPT
Ê Ê
PPOLOG= NO NOPROMPT
YES

PSRETRY=(0,0,0,0)
Ê Ê
PSRETRY=(low_tp_int,med_tp_int,high_tp_int,network_tp_int)

(8)
PSSTRACE=NORB RESUSAGE=100
Ê Ê
PSSTRACE= NORB RESUSAGE=usage_limit
IRB
SRB
BOTH
(9)
ROUTERES=128 SAWMAXDS=100
Ê Ê
ROUTERES=resistance_value SAWMAXDS=calculation_factor

SAWMXQPK=0
Ê Ê
SAWMXQPK=calculation_factor

SDLCMDRS=(STATS,INOPS) (10)
SDLCMDRS=YES SECLVLCP=ADAPT
Ê Ê
SDLCMDRS= YES SECLVLCP= LEVEL1
NO LEVEL2
STATS ADAPT
NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS

SIRFMSG=ALLSSCP SLUALMSG=NOSUPP
Ê Ê
SIRFMSG= ALLSSCP SLUALMSG= SUPPRESS
OLUSSCP NOSUPP
NONE

398 SNA Operation

 START

SMEAUTH=DISCARD SNAPREQ=1000
Ê Ê
SMEAUTH= DISCARD SNAPREQ=number_of_requests
EXIT
KEEP

(11)
SNVC=3 SONLIM=(60,30)
Ê Ê
SNVC=subnet_visit_count SONLIM= (percent_1,percent_2)
(percent_1)
(,percent_2)

(12)
SORDER=APPN SRCHRED=OFF
Ê Ê
SORDER= ADJSSCP SRCHRED= OFF
APPN ON
APPNFRST
SUBAREA

(13) (14)
SRCOUNT=10 SRTIMER=30
Ê Ê
SRCOUNT=number_of_search_requests SRTIMER=number_of_seconds

(15)
SSCPDYN=YES SSCPORD=PRIORITY
Ê Ê
SSCPDYN= NO SSCPORD= DEFINED
YES PRIORITY

SSDTMOUT=30
Ê Ê
SSDTMOUT=number_of_seconds
(16)
SSEARCH=YES STRGR=ISTGENERIC
Ê Ê
SSEARCH= YES STRGR= ISTGENERIC
NO NONE
CACHE structure_name
APPNFRST

STRMNPS=ISTMNPS SUPP=NOSUP
Ê Ê
STRMNPS= ISTMNPS SUPP= NOSUP
NONE INFO
structure_name WARN
NORM
SER

SWNORDER=CPNAME
Ê Ê
SWNORDER= CPNAME TCPNAME=tcp_job-name
STATNID

Chapter 2. VTAM Operator Commands 399

START
NOTNSTAT
Ê Ê
,NOCNSL ,TIME=60
TNSTAT
,CNSL ,TIME=minutes

(17)
NOTRACE,TYPE=BUF
Ê Ê
(18)
TRACE,TYPE=BUF BUF Trace Operands

(17)
NOTRACE,TYPE=IO
Ê Ê
(18)
TRACE,TYPE=IO IO Trace Operands

(17)
NOTRACE,TYPE=LINE
Ê Ê
(18)
TRACE,TYPE=LINE LINE Trace Operands

(17)
NOTRACE,TYPE=MODULE
Ê Ê
(18)
TRACE,TYPE=MODULE, MODULE Trace Operands

(17)
NOTRACE,TYPE=SIT
Ê Ê
(18)
TRACE,TYPE=SIT SIT Trace Operands

(17)
NOTRACE,TYPE=SMS
Ê Ê
(18)
TRACE,TYPE=SMS ,ID=VTAMBUF

(17)
NOTRACE,TYPE=STATE
Ê Ê
(18)
TRACE,TYPE=STATE STATE Trace Operands

(18)
TRACE,TYPE=VTAM, VIT Operands
Ê
(19)
NOTRACE,TYPE=VTAM

Notes:
1. LIST can be entered by a VTAM operator only. If LIST is coded in an
ATCSTRxx file, it is considered to be an error and is ignored.
2. LISTBKUP can only be coded in a start option file. If you enter it on the
START command or at an operator prompt, VTAM will ignore it.

400 SNA Operation

 START
3. MAXLOCAT is meaningful only if NODETYPE is specified.
4. NNSPREF can be specified only if NODETYPE=EN is specified during VTAM
START processing.
5. NODETYPE provides APPN function. The combination of NODETYPE and
HOSTSA determines the configuration (subarea node, interchange node,
migration data host, network node, or end node).
6. NUMTREES is meaningful only if the NODETYPE=NN start option is also
used.
7. A VTAM operator cannot enter the PROMPT or NOPROMPT start option; it
can be coded only in ATCSTR00. The value coded in ATCSTR00 is ignored if
start options are entered on the START command or if VTAM finds an error in
a start list. Upon finding an error in a start list, VTAM prompts the operator so
that the operator can specify the option correctly.
8. RESUSAGE is meaningful only if the NODETYPE=NN start option is also
used.
9. ROUTERES is meaningful only if the NODETYPE=NN start option is also
used.
10. The SECLVLCP start option is meaningful only if the NODETYPE and
VERIFYCP start options are also used.
11. SNVC is meaningful only if the BN=YES start option is also used.
12. SORDER is meaningful only in a network node, interchange node, or migration
data host.
13. SRCOUNT is meaningful only if the SRCHRED=ON start option is also used.
14. SRTIMER is meaningful only if the SRCHRED=ON start option is also used.
15. The SSCPDYN start option applies only for interconnected networks (that is,
GWSSCP=YES is used).
16. SSEARCH is meaningful only if the NODETYPE=NN start option is also used.
17. Do not use NOTRACE when starting VTAM, except to override a TRACE start
option coded in a predefined list.
18. Code TRACE and its qualifiers on one line. Code the TYPE qualifier
immediately following TRACE.
19. NOTRACE,TYPE=VTAM is accepted but ignored. Tracing is started with the
default trace table size and the default options.

(1)
TRANSLAT=(0,1,2,3,4,5,6,7) UPDDELAY=60
Ê
TRANSLAT= value UPDDELAY=max_time
()
( )
OLUALIAS
0
DLUREAL
1
DLUSSCP
2
COSNAME
3
LOGMODES
4
LUANAME
5
USERVAR
6
DLUALIAS
7 Chapter 2. VTAM Operator Commands 401
START
(2)
VERIFYCP=NONE VFYRED=YES
Ê Ê
USSTAB=table_name VERIFYCP= NONE VFYRED= YES
OPTIONAL NO
REQUIRED

(3) (4) (5)

VFYREDTI=OFF VRTG=NO VRTGCPCP=YES
Ê Ê
VFYREDTI= OFF VRTG= YES VRTGCPCP= YES
0 NO NO
reduction_timer

VTAMEAS=32001 XCFINIT=YES
Ê Ê
VTAMEAS=number_of_concurrent_sessions XCFINIT= NO
YES

XNETALS=NO
Ê
XNETALS= NO
YES

Buffer Pool Values

( , , , , , Ê
baseno bufsize slowpt F xpanno

Ê , )
xpanpt xpanlim

BUF Trace Operands

,AMOUNT=PARTIAL
,ID=node_name Ê
,EVERY ,AMOUNT= FULL
PARTIAL

,IDTYPE=RESOURCE ,SAVE=NO
Ê
,IDTYPE= CP ,SAVE= NO
SSCP YES
RESOURCE

IO Trace Operands

,IDTYPE=RESOURCE ,SAVE=NO
,ID=node_name
,EVERY ,IDTYPE= CP ,SAVE= NO
SSCP YES
RESOURCE

402 SNA Operation

 START
LINE Trace Operands

,COUNT=ALL (6)
,ID=line_name
,COUNT= ALL
number_of_bytes

MODULE TRACE Operands

,OPTION= ALL
option
(option)
( COMMAND )
CONNECTIONS
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
SESSION

SIT Trace Operands

,COUNT=ALL (6)
,ID=line_name Ê
,COUNT= ALL
number_of_bytes

Ê
,TRACEPT=trace_point_id

STATE Trace Operands

,IDTYPE=RESOURCE
,ID=node_name
,IDTYPE= CP
SSCP
RESOURCE
,OPTION= ALL
option
(option)
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LU
NCP
PU

Notes:
1. UPDDELAY is meaningful only if the OSIMGMT=YES start option is also used.
2. The VERIFYCP start option is meaningful only if the NODETYPE start option is
also used.

Chapter 2. VTAM Operator Commands 403

START
3. VFYREDTI is meaningful only if the NODETYPE=NN start option is also used.
4. VRTG is meaningful only if the NODETYPE and HOSTSA start options are also
used.
5. VRTGCPCP is meaningful only if the NODETYPE and HOSTSA start options
are also used.
6. COUNT applies only to the IBM 3720 and 3745 Communication Controllers.

VIT Operands

,MODE=INT,SIZE=100,DSPSIZE=0
Ê
,BFRNUM=2
,MODE= EXT
,BFRNUM=number
INT
,SIZE=size ,DSPSIZE=dspsize

(1) (2)
,OPTION=(API,MSG,NRM,PIU,PSS,SMS,SSCP)
Ê
,OPTION= ALL
NONE
option
(option)
( API )
APPC
CFS
CIO
CMIP
CSM
ESC
HPR
LCS
LOCK
MSG
NRM
PIU
PSS
SMS
SSCP
TCP
VCNS
XBUF
XCF

Notes:
1. The default options apply only to MODE=INT.
2. PSS and SMS can be turned off.

Abbreviations
Operand Abbreviation
START S
AMOUNT=FULL AMT=F
AMOUNT=PARTIAL AMT=P

404 SNA Operation

 START
Operand Abbreviation
DATEFORM DATEFRM
EVERY E
MSGLEVEL MSGLVL
OPTION OPT
OPTION=COMMAND OPT=CMD
OPTION=CONNECTION OPT=CON
OPTION=DEFINITION OPT=DEF
OPTION=INTERFACES OPT=INT
OPTION=MANAGEMENT OPT=MGMT
OPTION=SESSION OPT=SES
PLUALMSG=NOSUPP PLUALMSG=NOSUP
PLUALMSG=SUPPRESS PLUALMSG=SUPP
SECLVLCP=LEVEL1 SECLVLCP=LVL1
SECLVLCP=LEVEL2 SECLVLCP=LVL2
SLUALMSG=NOSUPP SLUALMSG=NOSUP
SLUALMSG=SUPPRESS SLUALMSG=SUPP
TRANSLAT=COSNAME TRANSLAT=3
TRANSLAT=DLUALIAS TRANSLAT=7
TRANSLAT=DLUREAL TRANSLAT=1
TRANSLAT=DLUSSCP TRANSLAT=2
TRANSLAT=LOGMODES TRANSLAT=4
TRANSLAT=LUANAME TRANSLAT=5
TRANSLAT=OLUALIAS TRANSLAT=0
TRANSLAT=USERVAR TRANSLAT=6

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
PLUALMSG=SUPPRESS, code only PLUALMSG=SUPP.

Purpose
VTAM is started with the START command.

You can enter the START command only at the master or a secondary system
console.

Operands
procname
is the procedure name for the command.

procname can be specified as either startname.ident or startname, where

startname is the name of the JCL procedure used to start VTAM and ident is an
optional identifier.

procname used for this command determines the procname used for all
MODIFY commands as follows:

Chapter 2. VTAM Operator Commands 405

START
v If procname in the START command was specified as startname.ident, where
startname is the VTAM start procedure and ident is the optional identifier,
then either startname.ident or ident can be specified for procname.
v If procname in the START command was startname, then startname must be
specified for procname.

Therefore, if you use NET as the optional identifier on this command, you can
consistently use NET as procname for all VTAM commands.
options
are VTAM start options supplied by the system programmer. The VTAM
operator can enter one or more options. For a description of the start options,
see the OS/390 eNetwork Communications Server: SNA Resource Definition
Reference.

If more than one line is necessary for the start options, enter a comma and a
closing parenthesis after the last option.

The values established by the start options go into effect when VTAM is started and
remain in effect until VTAM is halted. Many of the options, however, can be
modified with the MODIFY VTAMOPTS command while VTAM is running. You can
use the DISPLAY VTAMOPTS command to display the values of the start options.

406 SNA Operation

 VARY ACQ

VARY ACQ Command

Acquire an NCP, and optionally its subordinate resources, from another host:

ÊÊ VARY NET,ACQ ,ID=ncp_name Ê

,OWNER=host_name ,PUSUB

Ê ÊÍ
,ACT Operands used with ACT

Acquire “inactive” NCP, and optionally its subordinate resources, without

activating them:

ÊÊ VARY NET,ACQ ,ID=ncp_name ÊÍ

,PUSUB

Acquire “inactive” NCP, and optionally its subordinate resources, and activate
them:

ÊÊ VARY NET,ACQ ,ID=ncp_name ,ACT Operands used with ACT Ê

,PUSUB

Ê ÊÍ
,LOADMOD=load_module_name

Acquire nonswitched PU and its LUs:

ÊÊ VARY NET,ACQ ,ID=pu_name ÊÍ

,ACT Operands used with ACT

Operands used with ACT

,SCOPE=COMP

,LOGON=appl_name ,SCOPE= ALL

,LOGMODE=logon_mode_name COMP
ONLY
U

Abbreviations
Operand Abbreviation
VARY V
LOADMOD LM
PUSUB P

Purpose
The VARY ACQ (acquire) command is used to acquire an NCP, or to acquire a
peripheral PU (except for switched and local SNA PUs) attached by a nonswitched

Chapter 2. VTAM Operator Commands 407

VARY ACQ
line. An NCP or a peripheral physical unit attached to an NCP can be acquired as
part of a backup and recovery procedure in a multiple-domain network. A physical
unit attached to an NCP can also be acquired as part of a switched network backup
procedure in either a single-domain or multiple-domain network.

The purpose of the VARY ACQ command is to acquire ownership of:

v NCP resources that are normally owned by another host. In that case, the NCP
must have been previously activated.
See the OS/390 eNetwork Communications Server: SNA Resource Definition
Reference for additional information regarding the association of a resource with
a particular host.
v All resources within an NCP, including the NCP itself. In that case, the NCP
major node must be inactive and contacted through an active link station.
v An individual peripheral physical unit and its logical units.

Acquiring an NCP makes that NCP’s resources known to VTAM until the NCP is
released or deactivated. Likewise, acquiring a physical unit makes its logical units
known until the physical unit is released.

Acquiring a physical PU in a logical hierarchy results in the acquisition of the logical

lines in addition to any LUs. Also, the logical lines can be acquired only if the
physical PU is acquired. This means that acquiring an NCP acquires the logical
lines only if PUSUB is specified. Otherwise, a VARY ACQ command must be
entered for the physical PU.

If a subarea VTAM takes over an NCP owned by an APPN VTAM, it is possible that
some resources will no longer be known. To avoid this situation, it is recommended
that only APPN VTAMs take over resources from other APPN VTAMs.

The VARY ACQ command can also be entered for a physical unit when terminating
a switched network backup procedure. The purpose of the VARY ACQ command is
to make a nonswitched physical unit’s logical units known to VTAM after a switched
physical unit definition (representing the same physical device with a different
physical unit name but with the same logical unit names) is deactivated.

Operands
ACT
If you use the ACT operand on the VARY ACQ command, other operands of the
VARY ACT command are available. The operands you can use are:
v For resources subordinate to the NCP:
– LOGON
– LOGMODE
– SCOPE
v For the NCP and resources subordinate to the NCP:
– LOGON
– LOGMODE
– SCOPE
– LOADMOD
v For PUs and LUs:
– LOGON
– LOGMODE

408 SNA Operation

 VARY ACQ
– SCOPE.

See the “VARY ACT Command” on page 410 for a complete description of the
operands from the VARY ACT command that apply.
ID=name
specifies the name of the resource that is to be acquired. The resource must be
either an NCP major node or a physical unit within an NCP major node.

If the resource being acquired is an inactive NCP, it is possible to specify any

name for the ID operand, and then use the LOADMOD operand to identify the
actual NCP major node. If PUNAME is specified in the BUILD definition
statement, the NCP’s name must match that PUNAME value.
LOADMOD=load_module_name
specifies the member name in VTAMLST of the NCP major node to be
acquired. This operand applies to the acquisition of inactive NCPs only. If
LOADMOD is not specified, the name specified for the ID operand is used as
the member name.

See the LOADMOD operand on the VARY ACT command on page 427 for a
complete description.
OWNER=host_name
applies only when ID specifies an NCP that has previously been activated.
VTAM acquires only the resources that have an owner name matching the one
on this operand. You can specify only one owner name on this command.
However, you can enter multiple acquire commands, each specifying a different
owner name. If you do not specify OWNER on this command, all resources that
have OWNER coded in their resource definition are acquired, regardless of
which host is defined as the owner. However, resources that do not have
OWNER coded are not acquired.

The host_name operand is defined in the NCP PCCU macro or coded on

specific resources within an NCP, such as LINE or PU. This name specified on
the OWNER operand cannot match the name of the VTAM host from which you
are issuing the command (that is, VTAM cannot acquire resources that it
already owns).
PUSUB
applies only when ID specifies an NCP. PUSUB specifies that physical units
and their logical units, subordinate to the acquired NCP are to be acquired in
addition to the higher-level resources. If an NCP has previously been acquired
without PUSUB, specifying PUSUB in a subsequent VARY ACQ command for
the NCP can be used to acquire subordinate PUs and LUs.

If PUSUB is not specified, no PUs and associated LUs are acquired.

Chapter 2. VTAM Operator Commands 409

VARY ACT

VARY ACT Command

Activate an NCP major node:

ÊÊ VARY NET,ACT ,ID=ncp_name Ê

,DUMPSTA=
link_station_name

Ê Ê
,LOGON=appl_name
,LOGMODE=logon_mode_name

,LOAD=U,LOADFROM=HOST,DUMPLOAD=NO,SAVEMOD=NO
Ê Ê
,LOAD= NO
U NCP Load Operands
YES

Ê Ê
,NEWPATH=
dpu_name
,
(1)
( » dpu_name )

,SCOPE=COMP
Ê Ê
,RNAME= ,SCOPE= ALL
link_station_name COMP
(2) ONLY
( link_station_name ) U

,UPDATE=IMPLICIT
Ê ÊÍ
,U=channel_unit_address ,UPDATE= IMPLICIT
ADD
ALL

Notes:
1. You can specify up to 3 dynamic path update member names on the NEWPATH
operand.
2. You can specify up to 13 link station names on the RNAME operand.

NCP Load Operands

,LOADFROM=HOST,DUMPLOAD=NO,SAVEMOD=NO

,LOADSTA= ,LOADMOD=load_module_name ,DUMPLOAD=NO ,SAVEMOD=NO

link_station_name ,LOADFROM= EXTERNAL
,DUMPLOAD= NO
YES
,DUMPLOAD=NO,SAVEMOD=NO
HOST
,SAVEMOD=NO
,DUMPLOAD= NO
,SAVEMOD= NO
YES
YES,SAVEMOD=YES

Activate a switched major node:

410 SNA Operation

 VARY ACT
,DWACT=NO
ÊÊ VARY NET,ACT ,ID=major_node_name Ê
,DWACT= NO
YES

,SCOPE=COMP
Ê Ê
,LOGON=appl_name ,SCOPE= ALL
,LOGMODE=logon_mode_name COMP
ONLY
U

,UPDATE=IMPLICIT
Ê ÊÍ
,UPDATE= IMPLICIT
ADD
ALL

Activate the dynamic XCF local SNA major node:

ÊÊ VARY NET,ACT ,ID=ISTLSXCF ÊÍ

Activate a switched line:

ÊÊ VARY NET,ACT ,ID=line_name ÊÍ

,ANS= OFF
ON

Activate a type 2.1 PU (adjacent link station) or a nonswitched line under an

NCP:

ÊÊ VARY NET,ACT ,ID= pu_name Ê

line_name ,CPCP= YES
NO

(1)
Ê Ê
,HPR= NO ,LOGON=appl_name
YES ,LOGMODE=logon_mode_name

,SCOPE=COMP (2)
Ê ÊÍ
,SCOPE= ALL ,U=channel_unit_address
COMP
ONLY
U

Notes:
1. The HPR operand is valid for HPR-capable resources only.
2. The U operand is valid for a local SNA PU only.

Activate a dynamic XCF local SNA PU:

Chapter 2. VTAM Operator Commands 411

VARY ACT
ÊÊ VARY NET,ACT ,ID=name ÊÍ
,IDTYPE=XCFCP

Activate a control point (CDRSC minor node or application program minor

node):

,IDTYPE=RESOURCE ,SCOPE=COMP
ÊÊ VARY NET,ACT ,ID=name ÊÍ
,IDTYPE= CP ,SCOPE= ALL
RESOURCE COMP
ONLY
U

Activate an SSCP (CDRM minor node):

(1) ,IDTYPE=RESOURCE
ÊÊ VARY NET,ACT ,ID=name Ê
,HPR= NO ,IDTYPE= SSCP
YES RESOURCE

,SCOPE=COMP (2)
Ê ÊÍ
,SCOPE= ALL ,VRTGCPCP= YES
COMP NO
ONLY
U

Notes:
1. HPR and VRTGCPCP are only valid if VRTG=YES is coded for the CDRM, and
the CDRM is in an inactive state.
2. HPR and VRTGCPCP are only valid if VRTG=YES is coded for the CDRM, and
the CDRM is in an inactive state.

Warm start a major node:

ÊÊ VARY NET,ACT ,ID=major_node_name ,WARM ÊÍ

Activate a definition file (a major node with no subordinate resources):

ÊÊ VARY NET,ACT ,ID=major_node_name ÊÍ

Check the syntax of a definition file (major node):

ÊÊ VARY NET,ACT ,ID=major_node_name ,SCOPE=SYNTAX Ê

Ê ÊÍ
,LOADMOD=load_module_name

Dynamically reconfigure resources in a major node:

412 SNA Operation

 VARY ACT
Note: For an NCP major node, follow the syntax diagram for “Activating an NCP
major node” and specify the UPDATE operand.

,SCOPE=COMP
ÊÊ VARY NET,ACT ,ID=major_node_name Ê
,SCOPE= ALL
COMP
ONLY
U

,UPDATE=IMPLICIT
Ê ÊÍ
,UPDATE= IMPLICIT
ADD
ALL

Dynamically reconfigure TRLEs in a TRL major node:

,UPDATE=ADD
ÊÊ VARY NET,ACT ,ID=trl_major_node_name ÊÍ
(1)
,UPDATE= IMPLICIT
ADD
ALL

Notes:
1. Specifying UPDATE=IMPLICIT is the same as UPDATE=ADD.

Activate other resources:

,DWACT=NO
ÊÊ VARY NET,ACT ,ID=name Ê
,DWACT= NO
YES

,SCOPE=COMP
Ê Ê
,LOGON=appl_name ,SCOPE= ALL
,LOGMODE=logon_mode_name COMP
ONLY
U

(1)
Ê ÊÍ
,U=channel_unit_address

Notes:
1. The U operand is valid for a local SNA PU or a channel link.

Abbreviations
Operand Abbreviation
VARY V
CPCP=NO CPCP=N

Chapter 2. VTAM Operator Commands 413

VARY ACT
Operand Abbreviation
CPCP=YES CPCP=Y
DUMPLOAD=NO DL=NO or DL=N
DUMPLOAD=YES DL=YES or DL=Y
DUMPSTA DST
DWACT=NO DWACT=N
DWACT=YES DWACT=Y
EXTERNAL EXT
LOADFROM LF
LOADFROM=EXTERNAL EXT
LOADFROM=HOST HOST
LOADMOD LM
LOADSTA LST
LOGMODE LOG
SAVEMOD=NO SM=NO or SM=N
SAVEMOD=YES SM=YES or SM=Y
SCOPE=ALL ALL
SCOPE=COMP COMP
SCOPE=ONLY ONLY
SCOPE=SYNTAX SYNTAX
VRTGCPCP=NO VRTGCPPC=N
VRTGCPCP=YES VRTGCPPC=Y

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
LOADFROM=EXTERNAL, code only EXT.

Purpose
The VARY ACT (activate) command activates VTAM resources. Figure 6 on
page 416 shows each resource type for which the command is valid, and which
operands can be used for that resource type. A large dot means the operand can
be specified for the resource, and an S means the operand can be specified to sift
down to subordinate resources.

If any of the DUMPLOAD, SAVEMOD, or LOADFROM operands are coded on a

VARY ACT command, the target of the command is assumed to be an IBM 3720 or
3745 Communication Controller with the hard disk option, and the following default
values apply:
v LOADFROM=HOST
v SAVEMOD=NO
v DUMPLOAD=NO.

If all three are omitted, the target of the command is assumed not to be an IBM
3720 or 3745 Communication Controller and these operands do not apply.

Note: The combination LOADFROM=HOST,DUMPLOAD=YES,SAVEMOD=NO is not valid.

414 SNA Operation

 VARY ACT
Figure 7 on page 417 shows operands that are mutually exclusive for this
command. To read the table, you:
v Look at the operand name on the right of the table.
v Read across the table to the left to find an X (to see the operands that cannot be
coded with the operand named in the right-hand list). If the X appears in another
operand’s vertical column, the two operands are mutually exclusive.
v Match any number found at a row and column junction with the list of numbered
notes that accompany the table to get information about unique restrictions or
interactions.

The numbered fields in Figure 7 on page 417 identify unique requirements and
restrictions as follows:
1. LOAD=YES or LOAD=U is required if DUMPLOAD=YES, SAVEMOD=YES, or
LOADFROM is coded. The converse is not true.
2. This combination is not valid if SAVEMOD=NO is coded or assumed by default.
3. SAVEMOD=YES is required if DUMPLOAD=YES is coded, but only when
LOADFROM=HOST is also specified. The converse is not true.
4. LOADMOD is required if it differs from the ID (that is, if NEWNAME on the
BUILD statement differs from the PUNAME).
5. LOADFROM=HOST is required if SAVEMOD=YES is coded. The converse is
not true.
6. This combination is not valid if LOADFROM=HOST is coded.

Note: Specification of WARM and SCOPE together causes the command to fail.

NO is the default for both SAVEMOD and DUMPLOAD (DUMPLD on the PCCU
definition statement). If a value is specified on the PCCU definition statement, it
overrides the default. If a value is specified on the VARY ACT command, it
overrides both the PCCU definition statement value and the default value. This is
shown in Table 6 on page 418.

Chapter 2. VTAM Operator Commands 415

VARY ACT

/U
LY
ON
CP CE

P/
OM
TY =SS UR

X
CP

TA
L/C
SO

A D XCF

YN
M
D

TY =RE
TY =CP

AR PCP
AL
AD D

E
RO
DU LOA

OP D
AM H
DW STA

SC E=S
GM A
L O OD
LO DMO
=

SC MO
RN PAT

E=
LO ST

VR TE
NE O N
E
PE
PE
HP T

SA E
PE

C
M
AC

P
MP

MP

AD

OP

DA
CP

TG
VE
W
TY

G
A
S

R
DU
AN

LO
LO
LO
CP

UP
ID
ID=

ID
ID
ID

W
U
Adjacent CP major node
Adjacent SSCP tables
Application program major node
Application program minor node
APPN COS definition set
CDRM major node
CDRM minor node
CDRSC major node
CDRSC minor node
S S Channel-attachment major node
Channel link
Channel link station
S S Local non-SNA major node
Local non-SNA logical unit
S S Local SNA major node
S S Local SNA physical unit
Local SNA logical unit
LUGROUP major node
Model major node
S S NCP major node
S S S S Nonswitched line
Switched line
Link station
S S Physical unit
Logical unit
Network node server list
Path definition set
S S Switched major node
S S Switched physical unit
Switched link station
Switched logical unit
TGP definition set
TRL major node
XCA major node
Nonswitched line
Link station
Switched line
XCF local SNA major node
XCF local SNA physical unit
CP name of XCF local SNA physical unit

Figure 6. Valid Resource Types for VARY ACT

416 SNA Operation

 VARY ACT

ANS = ON
X ANS = OFF
CPCP = YES
X CPCP = NO
DUMPLOAD = YES
X DUMPLOAD = NO
DWACT = YES
X DWACT = NO
HPR = YES
X HPR = NO
IDTYPE = CP
X IDTYPE = SSCP
X X IDTYPE = RESOURCE
X X X X IDTYPE = XCFCP
1 X X X LOAD = YES
X X LOAD = NO
1 X X LOAD = U
2 1 X 1 LOADFROM = HOST
1 X 1 X LOADFROM = EXTERNAL
LOADMOD
X LOGMODE
LOGON
3 1 X 1 5 X 4 SAVEMOD = YES
6 X X SAVEMOD = NO
SCOPE = ALL
X SCOPE = COMP
X X SCOPE = ONLY
X X X SCOPE = SYNTAX
X X X X SCOPE = U
X X X X UPDATE = ADD
X X X X X UPDATE = ALL
X X X X X X UPDATE = IMPLICIT

X VRTGCPCP = YES
X X VRTGCPCP = NO
X X X X X X X X WARM

Figure 7. Mutually Exclusive (X) Operands for VARY ACT

Table 7 on page 419 and Table 8 on page 420 show the relationships between the
SAVEMOD and DUMPLOAD operands as they relate to the LOADFROM=HOST (
Table 7 on page 419) and LOADFROM=EXT ( Table 8 on page 420) operands.
SAVEMOD and DUMPLOAD (DUMPLD on PCCU) can be specified on either the
PCCU definition statement or the VARY ACT command. See the OS/390 eNetwork
Communications Server: SNA Resource Definition Reference for information about
the PCCU definition statement.

In Table 7 on page 419, Table 8 on page 420, and Table 9 on page 420, the
following is assumed:
v DUMPLOAD refers to both DUMPLOAD on the VARY ACT command and
DUMPLD on the PCCU. The value to be used is determined by Table 6 on
page 418 .

Chapter 2. VTAM Operator Commands 417

VARY ACT
v SAVEMOD refers to both SAVEMOD on the VARY ACT command and
SAVEMOD on the PCCU. The value to be used is determined by Table 6.
v Hard disk refers to the hard disk on the IBM 3720 or 3745 Communication
Controller.

Table 9 on page 420 shows how AUTODMP and AUTOIPL relate to the IBM 3720 or
3745 hard disk.
v AUTODMP: If the NCP abends, an attempt to put the NCP dump on the hard
disk is made if the dump/load switch is set. If there is an NCP dump on the hard
disk for this CCU, a request is made to dump the NCP to the host. The value of
the AUTODMP operand on the PCCU definition statement determines whether
this request is automatically implemented.
v AUTOIPL: If the NCP abends, and there is an NCP dump on the hard disk for
this CCU, or if the automatic dump/load switch is set to NO, the value of the
AUTOIPL operand on the PCCU definition statement determines how the NCP is
reloaded.

If DUMPLOAD=YES (as determined in Table 6), the communication controller

attempts to dump and load the NCP. If the dump and load are not successful, the
action to be taken depends on the values of AUTODMP and AUTOIPL as shown in
Table 9 on page 420.

Note: For the DUMPSTA and LOADSTA operands, the operator must determine
from the person who defined the VTAM system, usually the system
programmer, whether a name has been given in the system definition
statements for the link station. If a name has been defined already, then that
name should be used for the DUMPSTA and LOADSTA operands.
Otherwise, the operator can use the name automatically defined by VTAM.
Table 6. Precedence of Values When SAVEMOD and DUMPLOAD Are Specified. These rules of precedence apply in
both the VARY ACT command and PCCU definition statement.
PCCU
VARY ACT YES NO Not Specified1
YES YES YES Yes
NO NO NO NO
Not Specified YES NO NO
Note:
1. NO is the default for both SAVEMOD and DUMPLOAD (DUMPLD on PCCU).

418 SNA Operation

 VARY ACT
Table 7. Results When LOADFROM=HOST or LOADFROM Is Not Specified
SAVEMOD
DUMP- LOAD YES NO or Not Specified
YES The NCP is loaded from the host into the CCU and saved on This is an incorrect specification
the hard disk. If the NCP abends: or ignored if on the PCCU
definition statement. The
v If there is no NCP dump on the hard disk for this CCU,
dump/load switches cannot be
the NCP dumps automatically to the hard disk and the
manipulated without saving the
CCU is reloaded automatically from the hard disk.
load module onto the hard disk
v If there is an NCP dump on the hard disk for this CCU, a unless the load module already
request is made to dump the NCP to the host. exists on the hard disk and is
– If AUTOIPL=YES is coded on the PCCU definition being reloaded with
statement, VTAM automatically reloads the NCP into LOADFROM=EXT.
the CCU by transferring the load module from the host.
– If AUTOIPL=NO is coded on the PCCU definition
statement, the operator must request to reload the
NCP into the CCU. This is done in one of the following
ways:
- To transfer the load module from the host, enter the
VARY ACT, LOADFROM=HOST command (see
Table 9 on page 420).
- To transfer the load module from the hard disk, enter
the VARY ACT, LOADFROM=EXT command (see
Table 9 on page 420).

NO or Not Specified The NCP is loaded from the host into the CCU and saved on The NCP is loaded only from the
the hard disk. The dump and reload of NCP into the CCU host into the CCU. The dump
must be transferred to or from the host. and reload of NCP into the CCU
must be transferred to or from
v If AUTOIPL=YES is coded on the PCCU definition
the host.
statement, VTAM automatically reloads the NCP into the
CCU by transferring the load module from the host. v If AUTOIPL=YES is coded on
v If AUTOIPL=NO is coded on the PCCU definition the PCCU definition statement,
statement, the operator must request to reload the NCP VTAM automatically reloads
into the CCU. the NCP into the CCU by
transferring the load module
– To transfer the load module from the host, enter the
from the host.
VARY ACT, LOADFROM=HOST command (see Table 9
on page 420). v If AUTOIPL=NO is coded on
the PCCU definition statement,
– To transfer the load module from the hard disk, enter the operator must request to
the VARY ACT, LOADFROM=EXT command (see reload the NCP into the CCU.
Table 9 on page 420).
– To transfer the load module
from the host, enter the
VARY ACT,
LOADFROM=HOST
command (see Table 9 on
page 420 ).

Chapter 2. VTAM Operator Commands 419

VARY ACT
Table 8. Results When LOADFROM=EXT Is Specified
SAVEMOD
DUMP- LOAD YES NO or Not Specified
YES This is an incorrect specification The NCP is loaded into the CCU from the hard disk. If the NCP
or ignored if on the PCCU abends:
definition statement. It cannot
v If there is no NCP dump on the hard disk for this CCU, the
be specified to load the CCU
NCP is automatically dumped to the hard disk and the CCU
from the hard disk
is automatically reloaded from the hard disk.
(LOADFROM=EXT) and to save
the load module on the hard v If there is an NCP dump on the hard disk for this CCU, a
disk at the same time request is made to dump the NCP to the host.
(SAVEMOD=YES). – If AUTOIPL=YES is coded on the PCCU definition
statement, VTAM automatically reloads the NCP into the
CCU by transferring the load module from the host.
– If AUTOIPL=NO is coded on the PCCU definition
statement, the operator must request to reload the NCP
into the CCU. This is done in one of the following ways:
- To transfer the load module from the host, enter the
VARY ACT, LOADFROM=HOST command (see
Table 9).
- To transfer the load module from the hard disk, enter
the VARY ACT, LOADFROM=EXT command (see
Table 9).

NO or Not This is an incorrect specification The NCP is loaded into the CCU from the hard disk. The dump
Specified or ignored if on the PCCU and reload of NCP into the CCU must be transferred to or from
definition statement. It cannot the host.
be specified to load the CCU
v If AUTOIPL=YES is coded on the PCCU definition
from the hard disk
statement, VTAM automatically reloads the NCP into the
(LOADFROM=EXT) and to save
CCU by transferring the load module from the host.
the load module on the hard
disk at the same time v If AUTOIPL=NO is coded on the PCCU definition statement,
(SAVEMOD=YES). the operator must request to reload the NCP into the CCU.
– To transfer the load module from the host, enter the
VARY ACT, LOADFROM=HOST command (see Table 9).

Table 9. Actions to Be Taken for Unsuccessful DUMP and LOAD

AUTODMP on PCCU AUTOIPL on PCCU
DUMP-
LOAD YES NO YES NO
YES NCP dump is The operator must The NCP is The operator must reload the NCP
automatically decide whether to automatically by issuing either the VARY ACT,
transferred to the dump the NCP. The loaded into the LOADFROM=EXT command to
host. operator indicates CCU from the host reload the NCP from the hard disk
whether to dump even though the or the VARY ACT,
the NCP in NCP load module LOADFROM=HOST command to
response to the resides on the hard reload the NCP from the host.
prompt shown. disk.

420 SNA Operation

 VARY ACT
Table 9. Actions to Be Taken for Unsuccessful DUMP and LOAD (continued)
AUTODMP on PCCU AUTOIPL on PCCU
DUMP-
LOAD YES NO YES NO
NO or Not NCP dump is The operator must The NCP is The operator must reload the NCP
Specified automatically decide whether to automatically by issuing the VARY ACT,
transferred to the dump the NCP. The loaded into the LOADFROM=HOST command to
host. operator indicates CCU from the host. reload the NCP from the host.
whether to dump
the NCP in
response to the
prompt shown.

Operands
ANS
specifies whether VTAM should put a switched SDLC line in answer mode. The
VARY ACT command with the ANS operand has the same effect as the VARY
ANS command with the ACT operand. See the “VARY ANS Command” on
page 439 for more information on the VARY ANS command.
ANS=ON
specifies that VTAM should put the switched SDLC line in answer mode.
When the line is in answer mode (and active), the NCP answers incoming
calls from dial-in devices and notifies VTAM of the calls so that sessions
can be established.
ANS=OFF
specifies that VTAM should not put a switched SDLC line in answer mode.
If there is an existing session for the line, ANS=OFF does not break the
session, but no further calls are accepted after the session ends.
CPCP
applies for adjacent link stations and indicates whether the connection is to
support CP-CP sessions. This operand allows the value of the CPCP operand
on the PU definition statement to be overridden. You can also specify CPCP for
an NCP nonswitched line to indicate whether PUs under the line are to support
CP-CP sessions. If CPCP is not specified on the VARY ACT command, CP-CP
session capability on the connection is determined from the PU definition
statement or from the CPCP start option. If CPCP is specified on the VARY
ACT command, the value affects only a single activation instance. Subsequent
activations use the predefined values for that PU.

The resource must be in an inactive or connectable state; otherwise the

command fails and an error message is issued. CP-CP session capability is
determined during XID exchange and cannot be changed after a connection is
established.
CPCP=YES
indicates that the connection is to support CP-CP sessions.
CPCP=NO
indicates that the connection is not to support CP-CP sessions.
DUMPLOAD
applies only if LOAD=YES is specified or if LOAD=U is specified or assumed by
default. Specifies whether the automatic dump/load switch in the IBM 3720 or

Chapter 2. VTAM Operator Commands 421

VARY ACT
3745 Communication Controller should be set to on or off. The switch controls
automatic dumping and reloading of an NCP to or from the hard disk in the
event of an NCP abend.

See Table 7 on page 419 and Table 8 on page 420 for additional information
about DUMPLOAD specifications.

Existing automatic IPL settings for a load module are retained by the IBM 3720
or 3745 Communication Controller (that is, DUMPLOAD does not default) if the
following are true:
v DUMPLD is not specified in the PCCU definition statement
v DUMPLOAD, SAVEMOD, and LOADFROM are not specified in the VARY
ACT command
v A copy of the load module is already stored on the IBM 3720 or 3745
Communication Controller hard disk.
DUMPLOAD=YES
turns the automatic dump/load switch on. When the NCP abends, the
switch is tested. If the switch is on, and if there is no NCP dump on the
hard disk for this CCU, a dump of the NCP is stored on the IBM 3720 or
3745 Communication Controller hard disk. If the dump slot is full and
AUTODMP=YES on the PCCU definition statement, the dump is transferred
to the host. Otherwise, the network operator is prompted as specified in
Table 9 on page 420.

After a dump has been stored, the controller is reloaded with the active
NCP load module from the IBM 3720 or 3745 Communication Controller.
The automatic load takes place only if the automatic dump has successfully
occurred.
DUMPLOAD=NO
turns the automatic dump/load switch off in the communication controller.
The controller is not automatically dumped and reloaded from the hard disk.
DUMPSTA=link_station_name
applies only to the first activation of an NCP. (That is, DUMPSTA does not apply
if the NCP is already active or is in the process of being activated.)

DUMPSTA specifies the name of a link station in an adjacent subarea node

through which any later static dump operations for this NCP are to be carried
out. The VTAM-generated link station name (a 3-digit or 4-digit hexadecimal
channel unit address followed by -S) can be specified. The link station can be
either a channel link station or an SDLC link station in an NCP major node. The
link station cannot be an SDLC link station in a channel-attachment major node.
The link station identified for DUMPSTA should also be identified in the channel
unit address (U) or RNAME specifications for this NCP, either in the NCP
definition or in this VARY ACT command.

Note: DUMPSTA does not support switched, X.25, or token-ring link stations.

The DUMPSTA operand, if specified, overrides any NCP definition value of

DUMPSTA. If DUMPSTA is not specified in either the NCP definition or this
command, VTAM selects (at the time of each dump operation) an available
adjacent link station, giving preference to a channel link station. Similarly, if

422 SNA Operation

 VARY ACT
DUMPSTA is specified without a value (that is, if DUMPSTA= is specified),
DUMPSTA assumes a null value and VTAM selects an available adjacent link
station as previously described.

Note: All references to NCP definition should be “NCP PCCU definition”.

DWACT
specifies whether to dial the PUs that are activated as a result of the activation
of the switched major node or switched PU named on the ID operand.

Activation of PUs subordinate to the switched major node is determined by the

ISTATUS value coded on the PU definition statement and the SCOPE value on
the VARY ACT command. Specifying DWACT=YES on the major node
activation prevents you from having to issue a VARY DIAL command for each
PU individually after the PU is activated.
DWACT=YES
dials the PUs that are activated as a result of the switched major node or
| switched PU activation.

| Note: For switched PU activation, the PU is dialed on initial activation only;

| DWACT=YES has no affect on VARY INACT,R command
| processing. This command causes the PU to be inactivated and then
| activated, but no dial operation is performed.
DWACT=NO
does not dial the PUs that are activated as a result of the switched major
node or switched PU activation. Specifying DWACT=NO on the VARY ACT
command does not override DWACT=YES specified on the PU definition
statement.
HPR
specifies HPR capability at the link level. The use of the HPR operand on this
command overrides what is coded for HPR on the CDRM, GROUP, LINE, or
PU definition statements. HPR is valid on activation of a CDRM, GROUP, LINE,
or PU in an HPR-capable node. For information on HPR capability for various
node and connection types, see the OS/390 eNetwork Communications Server:
SNA Network Implementation Guide.

Note: For a CDRM, this operand is valid only if VRTG=YES is specified for the
CDRM, and the CDRM is in an inactive state; otherwise, the command
fails and an error message is issued.
HPR=YES
specifies that the GROUP, LINE, PU, or VR-based TG to the CDRM being
activated is HPR-capable.
HPR=NO
specifies that the GROUP, LINE, PU, or VR-based TG to the CDRM being
activated is not HPR-capable.
ID=name
specifies the name of the resource to be activated. The name can be a
network-qualified name. It cannot be a USERVAR or LUALIAS name. If the
name specified on the ID operand is network-qualified, this name is considered
to be the real name of the resource. The name can be an ACB name or an
alias name, as long as it is not network-qualified.

Chapter 2. VTAM Operator Commands 423

VARY ACT
Following is an example of an APPL major node definition to show how
application names can be network-qualified:
x APPL ACBNAME=y,...

In the above example, x (the application name) can always be

network-qualified. y (the ACB name) can be network-qualified only if y is the
same as x.

To activate the dynamic local SNA major node for XCF connections, specify
ID=ISTLSXCF.

To reactivate a dynamic XCF local SNA PU representing the connection to

another VTAM, you can specify one of the following:
v The name of the PU
v The CP name of the other VTAM with IDTYPE=XCFCP.

For a CDRM, you can specify a network-qualified name, but this does not
remove the restriction that the non-network-qualified CDRM name must be
unique across networks.

If the resource is a TRL major node, specify the VTAMLST member name as
the ID value. The command builds the TRL major node using the set of TRLE
definition statements that are defined in the TRL major node. Subsequent
messages about the TRL major node display ISTTRL as the name of the table.
ISTTRL is the name of the VTAM internal table.

If the resource is an NCP:

v If PUNAME is specified in the BUILD definition statement, the ID operand
must specify that PUNAME value.
v If PUNAME is not specified in the BUILD definition statement, the ID operand
can specify any name desired (that is not not already known to this VTAM),
and use the LOADMOD operand to identify the actual NCP major node. After
the NCP is active, the name specified on the ID operand is the name used to
identify the NCP (not the load module name specified on LOADMOD).

If the resource is a switched major node containing PUs supported by a

dependent LU requester (DLUR), the CPSVRMGR session is not activated until
a VARY DIAL command is issued for the physical unit. See the “VARY DIAL
Command” on page 442 for more information.

If the resource is a model application program, the state of the model

application program becomes connectable (CONCT). This means that the
model application program definition is available to build dynamic application
programs.

You cannot activate dynamic application programs with the VARY ACT
command. Dynamic application programs are activated only by opening their
ACBs. For a dynamic application program to successfully open its ACB, a
model definition must exist to build the dynamic application program, and that
model definition must be connectable.

The following restrictions apply to VARY ACT depending on whether VTAM has
been defined to support APPN function:

424 SNA Operation

 VARY ACT
v If VTAM has been defined as an APPN-only node, you cannot activate the
following resources:
– NCP
– CDRM
– Path definition set
– Adjacent SSCP.
v If VTAM has been defined as a subarea-only node, you cannot activate the
following resources:
– Adjacent CP
– Transmission group profile
– APPN class-of-service table.
v If VTAM has been defined as a migration data host, you cannot activate an
NCP.
v If VTAM has been defined as a network node, you cannot activate a network
node server list. (The list can only be activated at an end node.)

If the named resource has subordinate resources (for example, logical units
subordinate to a physical unit), those subordinate resources can also be
activated using the SCOPE or WARM operands.

Independent LUs are not subordinate to any PU. Therefore, the sift-down to
subordinate LUs does not affect independent LUs unless the ID value is a
CDRSC major node.

You can individually activate multiple adjacent SSCP table definitions. Each new
set of definitions is added to the internal table used by VTAM. New definitions
for destinations already in the internal table replace the current adjacent SSCP
list for those destinations, but you cannot deactivate existing adjacent SSCP
lists. If a new table replaces an existing one, VTAM issues a message informing
the operator.

To activate an APPN-to-subarea or subarea-to-APPN class-of-service mapping

table, issue the VARY ACT command at the APPN-capable host that will use
the table.

| To activate a subarea mapping table, issue the VARY ACT command at the ICN
| host that will use the table.

To activate a network node server list, issue the VARY ACT command at the
end node which will use the list. Note that this command activates the list, but
the list is not used until a new CP-CP session is established. If the end node
has no CP-CP session when you issue this command, and an active link is
available to one of the servers in the list, this command will activate a CP-CP
session as well as activating the server list.

You can dynamically replace a network node server list by creating a new list,
issuing VARY ACT to activate the new list, and issuing VARY TERM to
terminate the existing CP-CP session. VTAM will automatically drive a new
CP-CP session using the new list. A network node server list cannot be
deactivated.

To activate a SAW sense filter, issue the VARY ACT command at the host node
that will use the table.

Chapter 2. VTAM Operator Commands 425

VARY ACT
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE can be used to identify which
resource the command should act on.
IDTYPE=CP
specifies that the name on the ID operand is a CP. If an APPN connection
exists, VTAM attempts to activate a CP-CP session between the host CP
and the resource named on the ID operand.

Note: You cannot activate a CP-CP session between an adjacent CP

running VTAM V4R1 and a host CP running a version of VTAM later
than V4R1, if the link is already active.
IDTYPE=RESOURCE
activates the resource specified on the ID operand.

If the resource VTAM finds is a CP and if an APPN connection exists,

VTAM attempts to activate a CP-CP session between the host CP and the
resource named on the ID operand.

If the resource VTAM finds is a host CP or an adjacent CP, VTAM searches

for a CDRM with the name specified on the ID operand and activates the
CDRM, as well.

If a CP and an SSCP are found with the specified name, VTAM activates
both the CP and the SSCP simultaneously.
IDTYPE=SSCP
specifies that the name on the ID operand is an SSCP. VTAM activates the
CDRM by the name specified.
IDTYPE=XCFCP
activates the dynamic XCF local SNA PU representing the connection to
another VTAM, when the ID operand specifies the CP name of the other
VTAM.
LOAD
applies only to the first activation of an NCP. (That is, LOAD does not apply if
the NCP is already active or is in the process of being activated.)

LOAD specifies whether the communication controller associated with the

specified NCP is to be reloaded with the appropriate NCP load module.

A communication controller is associated with an NCP for the purposes of this

command if any of the following conditions are met:
v It is already known to contain the named NCP.
v It is attached through one or more of the adjacent link stations identified by
the NCP’s channel unit address (U) or RNAME specifications, or both.
v It is attached through the adjacent link station identified by the LOADSTA
specification for the NCP.
LOAD=YES
unconditionally loads the communication controller associated with the
specified NCP, regardless of the current state or contents of the
communication controller.

426 SNA Operation

 VARY ACT
Note: If the NCP is being loaded by another host when this command is
issued, the command fails.
LOAD=NO
prevents the communication controller associated with the specified NCP
from being loaded during the processing of this VARY ACT command,
regardless of the current state or contents of the communication controller.
(The communication controller is still subject to possible reload operations
during error recovery procedures subsequent to the activation of the NCP.)
If the communication controller does not contain the expected NCP load
module, the VARY ACT command fails.
LOAD=U
lets VTAM determine whether the communication controller associated with
the specified NCP should be loaded during the processing of this VARY
ACT command (based on the current contents of the communication
controller and on the NCP definition statements), as it was before the
availability of the LOAD operand.

For additional information about what VTAM does when LOAD=U is

specified, see the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide.

Note: If this command is issued while another host is loading the NCP, you
are notified, and VTAM waits until the load is complete from the
other host. VTAM then loads the NCP as appropriate.
LOADFROM
applies only if LOAD=YES or LOAD=U. It specifies whether VTAM loads the
NCP module from the host or from the communication controller hard disk. See
the OS/390 eNetwork Communications Server: SNA Resource Definition
Reference for a complete description of the LOADFROM operand on the PCCU
definition statement.

LOADFROM=HOST is not supported for loading an NCP attached by a

token-ring, X.25 PVC or SVC, or X.21 switched connection. Specify
LOADFROM=EXTERNAL for those line types.

See Table 7 on page 419 and Table 8 on page 420 for additional information
about LOADFROM specifications.
LOADFROM=HOST
loads the NCP from the host, using the SSP as the interface to the NCP
load library.

Note: The combination LOADFROM=HOST,DUMPLOAD=YES,SAVEMOD=NO is not

valid.
LOADFROM=EXTERNAL
loads the NCP from the IBM 3720 or 3745 Communication Controller hard
disk.
LOADMOD=load_module_name
specifies the name of the load module to load. The load module name is the
member name specified in the NCP LOADLIB. This name must match the
major node name (the member name in VTAMLST).

The LOADMOD operand must be specified if the name of the PU specified in

the BUILD definition statement is not the same as the load module name.

Chapter 2. VTAM Operator Commands 427

VARY ACT
Failure to code LOADMOD when the PU name and load module name differ
prevents VTAM from locating the specific definition program you now want to
activate. If NEWNAME is specified, the LOADMOD value must match the
NEWNAME value specified in the BUILD definition statement.
LOADSTA=link_station_name
applies only to the first activation of an NCP. (That is, LOADSTA does not apply
if the NCP is already active or is in the process of being activated.)

LOADSTA specifies the name of a link station in an adjacent subarea node

through which any load operations for this NCP are to be carried out. The
VTAM-generated link station name (a 3-digit or 4-digit hexadecimal channel unit
address followed by -S) can be specified. The link station can be either a
channel link station or an SDLC link station in an NCP major node. The link
station identified for LOADSTA should also be identified in the channel unit
address (U) or RNAME specifications for this NCP, either in the NCP definition
or in this VARY ACT command.

The link station cannot be an SDLC link station in a channel-attachment major

node.

The LOADSTA operand, if specified, overrides any NCP definition value of

LOADSTA. If LOADSTA is not specified in either the NCP definition or on this
command, VTAM selects (at the time of each reload operation) an available
adjacent link station, giving preference to a channel link station. Similarly, if
LOADSTA is specified without a value (that is, if LOADSTA= is specified),
LOADSTA assumes a null value and VTAM selects an available adjacent link
station from the NCP link station queue in the following order:
1. Channel
2. Active leased
3. Active dial-out switched
4. Active dial-in switched
5. Pending active leased
6. Pending active dial-out switched
7. Pending active dial-in switched
8. Dummy (undefined).

If the NCP resides in a communication controller that is attached to VTAM by a

serial optical channel (SOC), and you are reloading the NCP with a new load
module, the LOADSTA operand is required and the link station name that you
specify must be defined as an IPL port in the Telecommunication Service
Processor (TSP). This is because ESCON support allows up to sixteen SOC
link stations to be defined as parallel TGs, and usually only one or two of these
link stations are defined as IPL ports. The NCP load will fail if the link station is
not defined as an IPL port in the TSP. (Because a maximum of eight VRs can
be active at a time, only eight of the sixteen parallel TGs can be attached
between the host and the NCP at a time.)
LOGMODE=logon_mode_name
specifies the logon mode name to be used for any logon initiated for a logical
unit as a result of this command (see the description of the LOGON operand).
This logon mode name also becomes the logon mode name for all future
automatic logons performed by VTAM for logical units within the scope of this
command and for their controlling primary LUs (if any).

428 SNA Operation

 VARY ACT
LOGMODE is valid only if LOGON is specified. If LOGMODE is specified
without LOGON, the command fails and an error message is issued.

If LOGMODE is not specified, the LOGMODE value specified in any previous

command applicable to a logical unit also within the scope of this VARY ACT
command is used. If no LOGMODE value was ever specified for a given logical
unit within the scope of this command, the logical unit’s default value is used.
LOGON=appl_name
specifies the name of an application program (primary LU) to which any
secondary LUs within the scope of this command are to be logged on. The
application name can be network-qualified. If it is, the network identifier is
considered to be real, but the resource name is considered to be generic (that
is, the resource name can be either the real application name or a USERVAR
name).

If the application name is an ACB name, and the ACB name matches the name
on the APPL definition statement, then you can use a network-qualified ACB
name.

If a USERVAR is found, VTAM resolves its name to the name of the VTAM
application with which it is currently associated. If a USERVAR with this name is
not found, VTAM searches for an application program with this name.

If the primary LU is an application program in this domain, the name must be

that of an application program minor node within an active application program
major node.

If the primary LU is a predefined CDRSC, the CDRSC must be active.

If the primary LU is a device-type LU, it must be attached to the same NCP as

the secondary LU.

See also the “VARY LOGON Command” on page 459 for more information on
the operator-initiated logon function.
NEWPATH=name
specifies the dynamic path update member names in the VTAM definition
library. When the NCP is successfully activated, VTAM processes and sends
path table update specifications to the NCP. The NEWPATH operand is valid
only when an NCP major node is being activated.

Up to three member names can be specified; if more than three member names
are specified, the VARY command is rejected, and you must issue a new path
command to activate the NCP. If more than one member name is specified, the
names must be enclosed in parentheses and separated by commas.

VTAM sends the path table update specifications by means of the SSCP-PU
session before any links, other than the link for the SSCP-PU session, are
activated. If you attempt to change or delete the explicit route being used for
the SSCP-PU session, the NCP rejects the request (because the explicit route
is currently operative), and VTAM displays a warning message.

This operand overrides NEWPATH specifications on the PCCU definition

statement in the NCP’s generation file (see the OS/390 eNetwork
Communications Server: SNA Resource Definition Reference ). For example, if
the PCCU NEWPATH operand specifies three member names and the VARY

Chapter 2. VTAM Operator Commands 429

VARY ACT
ACT NEWPATH operand specifies one member name, only the one member
specified in the VARY ACT command is processed. If you specify “NEWPATH=,”
or “NEWPATH= ” in the VARY ACT command, the NEWPATH operand coded in
the PCCU definition statement is nullified.

NEWPATH processing does not affect NCP activation in any way. For example,
if the member specified with the NEWPATH operand cannot be processed
because of a shortage of VTAM storage, an appropriate message is displayed
and no further recovery processing is attempted.

When a dynamic path update member is processed as a result of a NEWPATH

operand, any path table update specifications for VTAM subareas and other
NCP subareas are discarded. However, VTAM checks the validity of PATH
statements and issues warning messages if errors are detected.
RNAME=name
applies to the activation of an NCP or, in certain migration cases, to the
activation of a link station.

For an NCP, the RNAME operand is described in the following paragraphs and
applies only to the first activation of the NCP. (That is, RNAME does not apply if
the NCP is already active or is in the process of being activated.)

Note: When activating NCPs, if the RNAME is referring to a switched link

station, activate the switched major node before issuing the VARY ACT
command for the NCP. Otherwise, the NCP activation might fail.

RNAME specifies the names of up to 13 SDLC or channel link stations in

adjacent subarea nodes through which the specified NCP is attached to the
network. It also specifies which link stations (and associated links) in adjacent
subarea nodes are to be automatically activated as part of the activation of the
specified NCP. Therefore, these RNAME values identify the location of the
communication controller in the network and enable VTAM to establish the
necessary connectivity to the specified NCP (if such connectivity does not
already exist).

If more than one link station name is specified, the names must be enclosed in
parentheses and separated by commas.

The RNAME operand, if specified, overrides any NCP definition RNAME values
or the checkpointed RNAME values for the specified NCP. For a list of the
checkpointed parameters for each major node and for a general description of
the configuration restart facility, see the OS/390 eNetwork Communications
Server: SNA Network Implementation Guide.

If RNAME values are specified on this command, VTAM uses those values to
determine the link stations to be used. If the RNAME operand is not specified
on this command, VTAM uses the checkpointed RNAME values for the
specified NCP (if the WARM operand is specified). If neither the RNAME nor
the WARM operand is specified, VTAM uses the NCP definition values for
RNAME, if any. If RNAME is not specified in the NCP definition, RNAME
assumes a null value, and no SDLC link stations are automatically activated. If
the RNAME operand is specified without a value (that is, RNAME= is specified),
RNAME assumes a null value.

430 SNA Operation

 VARY ACT
If both the RNAME and the channel unit address specifications have null
values, no automatic link station activations are performed, and there must be
link stations already active in adjacent subarea nodes to provide the required
connectivity. If this is not so, the VARY ACT command fails.
SAVEMOD
applies only if LOAD=YES or LOAD=U. It specifies whether the NCP load
module is saved on the communication controller hard disk after the NCP is
loaded from the host.

See Table 7 on page 419 and Table 8 on page 420 for additional information
about SAVEMOD specifications.
SAVEMOD=YES
saves the NCP on the communication controller hard disk after the NCP is
loaded from the host.

If both load module data sets are full for this CCU, and:
v The name specified matches the name of a load module already stored,
the load module with that name is replaced.
v The name specified does not match the name of a load module already
stored, the oldest load module is replaced.
SAVEMOD=NO
does not save the NCP load module on the IBM 3720 or 3745
Communication Controller hard disk after the NCP is loaded from the host.
SCOPE
specifies the scope of the command.

WARM and SCOPE cannot be specified on the same command. If both are
specified, the command fails.

The only SCOPE value applicable to model major node, LUGROUP major
node, path definition set, or adjacent SSCP tables is SCOPE=SYNTAX.

SCOPE has no effect for a TRL major node. If the SCOPE value is specified for
this resource, VTAM issues message IST1275I to indicate that the operand was
ignored and continues processing.

For configuration restart, the checkpoint data set is updated with information on
these resources, unless SCOPE=SYNTAX is specified. No information is stored
in the checkpoint data set if the SYNTAX option is used.
SCOPE=ALL
specifies that the resource named in the ID operand and all of the
appropriate subordinate resources are to be activated (regardless of their
defined ISTATUS values).
SCOPE=COMP
specifies one of the following actions:
v For the initial activation of a major node, activates all subordinate minor
nodes according to the ISTATUS specification. (This is the same as
SCOPE=U.)
v For a major node that is already active:

Chapter 2. VTAM Operator Commands 431

VARY ACT
– If UPDATE=ADD|ALL is specified on the same command, VTAM
updates the current configuration to match the VTAMLST definition
and activates minor nodes based on the ISTATUS value.
– If UPDATE=IMPLICIT is specified or assumed by default, VTAM
activates all subordinate minor nodes that were not previously active.
(Logical units are activated according to their ISTATUS specification if
the PU was not previously active. Otherwise, they are not activated.)
v For a minor node, the action depends on the node type, as follows:

Node Action
Group, PU Same as SCOPE=U
Line, LU, APPL, CDRSC, link station Same as SCOPE=ONLY

LU activation varies according to the owning PU status when processing

a SCOPE=COMP on an active major node. A previously inactive PU is
activated and its subordinate LUs are activated according to their
ISTATUS specification. The LUs of a previously active PU are ignored.
SCOPE=ONLY
specifies that only the resource named in the ID operand is to be activated;
none of its subordinate resources are to be activated (regardless of their
defined ISTATUS values).
SCOPE=SYNTAX
specifies that the major node named on the ID operand is to have its
VTAMLST definition file checked for syntax errors. This validation does not
include user-replaceable tables such as USS tables, ALS tables, and the
like. The error checking consists of validation of syntax, definition
statements, operands, and the type of the operands. This checking is the
same as is done when the VARY ACT command is used to activate a
resource. When SCOPE=SYNTAX is specified, no resource activation takes
place.

The ID operand is required. The LOADMOD operand must be used if the

name specified on the PUNAME operand in the NCP BUILD definition
statement is not the same as the load module name. See the description of
the ID operand for more information. All other operands are ignored if
SCOPE=SYNTAX is specified.

All major node types (including path definition set and adjacent SSCP
tables) shown in Figure 6 on page 416 can be specified using
SCOPE=SYNTAX.

Note: SCOPE=SYNTAX builds an internal representation of the resources

in the file being checked, and might have an impact on storage until
the command completes. VTAM uses approximately 600 bytes of
storage for each definition statement included in the definition file.
See the OS/390 eNetwork Communications Server: SNA Resource
Definition Referencefor more information about definition statements.
SCOPE=U
specifies that the resource named in the ID operand, and all the appropriate
subordinate resources defined with ISTATUS=ACTIVE, are to be activated.
U=channel_unit_address
specifies the hexadecimal channel unit address by which a channel attachment
to a communication controller, to an adjacent host, or to an SNA physical unit is

432 SNA Operation

 VARY ACT
known to the operating system and through which VTAM is to establish
connectivity to the specified NCP, VTAM, or physical unit. A channel unit
address must be supplied for a channel-attached physical unit because the
physical unit can communicate only through the channel. Likewise, a channel
unit address must be supplied for a channel-attached host because the
adjacent host can communicate directly only through the channel attachment. A
channel unit address is optional for an NCP because an NCP can also
communicate across SDLC links. This operand has no effect if the node is
being activated or is currently active.
v For a channel-attachment major node, the U operand overrides any
previous channel unit address specifications, including the ADDRESS
operand on the LINE definition statement of the channel-attachment major
node definition.
Omit the U operand if you are activating a channel-attachment major node
that has LNCTL=MPC in its definition. Otherwise, the activation of resources
in the multipath channel (MPC) group will fail.
If the U operand is omitted and there is no current channel unit address
specification for VTAM, the VARY ACT command fails. The VARY ACT
command also fails if the U operand is specified without a value (that is, if
U= is specified).
v For an SNA physical unit, the U operand, if specified, overrides any
previous channel unit address specifications for the physical unit, including
the CUADDR operand on the PU definition statement.
The U operand, if specified, overrides any specification maintained by
configuration restart.
If the U operand is omitted and there is no current channel unit address
specification for the physical unit, the VARY ACT command fails. The VARY
ACT command also fails if the U operand is specified without a value (that is,
if U= is specified).
v For an NCP, the U operand, if specified, overrides any NCP definition
CUADDR values or the checkpointed channel unit address values for the
specified NCP. If a U value is specified on this command, VTAM uses the
value to determine the link station to be used. If the U operand is not
specified on this command, VTAM uses the checkpointed channel unit
address values for the specified NCP (if the WARM operand is specified). If
neither the U nor the WARM operand is specified, VTAM uses the NCP
definition value for CUADDR, if any. If CUADDR is not specified in the NCP
definition, the channel unit address specification assumes a null value, and
no channel link station is automatically activated. If the U operand is
specified without a value (that is, if U= is specified), the channel unit address
specification assumes a null value.
If both the RNAME and the channel unit address specifications have null
values, no automatic link station activations are performed, and there must
be link stations already active in adjacent subarea nodes to provide the
required connectivity. If this is not so, the VARY ACT command fails.
UPDATE
allows you to dynamically implement changes that you have made in a
VTAMLST definition file. You can use the UPDATE operand to make the
following kinds of dynamic reconfiguration changes:
v Local SNA major node: add and delete LUs; dynamically change certain
operand values on LU definition statements.
v NCP major node: add, delete, and move PUs and LUs; dynamically change
certain VTAM-only operand values on PU and LU definition statements.

Chapter 2. VTAM Operator Commands 433

VARY ACT
v Switched major node: add and delete PUs and LUs; dynamically change
certain operand values on PU, LU, and PATH definition statements.
v Transport resource list (TRL) major node: add, delete, or replace TRLEs;
dynamically change operand values on TRLE definition statements.

VTAM reads the VTAMLST definition file for the major node and updates the
current configuration to match the definition. The affected minor nodes must be
inactive (except for PATH definition statements in the switched major node), but
the major node can remain active. For more information on dynamic
reconfiguration, see the OS/390 eNetwork Communications Server: SNA
Network Implementation Guide. For information on which operands in PU and
LU definition statements can be dynamically changed, see the OS/390
eNetwork Communications Server: SNA Resource Definition Reference.

If you have used the VARY LOGON command to establish an automatic logon
relationship that was not coded on the LOGAPPL operand of a definition
statement, or if you have used the VARY NOLOGON command to terminate an
automatic logon relationship that was coded on the LOGAPPL operand of a
definition statement, the VARY ACT,UPDATE=ALL command might undo the
effects of these commands. This is because the LOGAPPL operand in the
definition file overrides these commands. Even if no LOGAPPL is coded in the
definition file, VTAM assumes a null value for LOGAPPL and the null value
overrides the VARY LOGON value. To avoid undoing the effects of the VARY
LOGON command, code the LOGAPPL definition statement with the desired
value. To avoid undoing the effects of the VARY NOLOGON command, delete
the LOGAPPL operand from the definition statement. VARY ACT,UPDATE=ALL
can undo the effects of the MODIFY DEFAULTS command in the same way.

VTAM issues an error message if a VARY ACT,UPDATE=ALL command is

attempted for an active resource. For example, you might have activated an
NCP, then issued a VARY LOGON command for some of the LUs under the
NCP. (The VARY LOGON command overrides the LOGAPPL value that was
used during NCP activation.) If you later issue a VARY ACT,UPDATE=ALL
command to make some other kind of change, such as moving a PU from one
line to another, and meanwhile the LUs are active that have the new LOGAPPL
value, VTAM will issue an error message. This is because the VARY
ACT,UPDATE=ALL command overrides the VARY LOGON command; that is,
VTAM encounters a defined LOGAPPL value that is different from the current
value, so it attempts an operand change, but the operand change fails because
the LUs are active.

Dynamic reconfiguration for an NCP:

For an NCP, this command performs the following functions without

regenerating the NCP:
v Adds a nonswitched physical unit and its subordinate LUs to a line
v Adds a logical unit to a nonswitched physical unit
v Passes the GP3174 and RETRIES operands to NCP when dynamically
adding a PU
v Moves a nonswitched physical unit and its subordinate LUs from one line to
another
v Moves a logical unit to another physical unit
v Changes a nonswitched physical unit link station address (except on the
initial activation of the NCP)

434 SNA Operation

 VARY ACT
v Changes the LOCADDR for an LU (except on the initial activation of the
NCP)
v Deletes a nonswitched physical unit and its subordinate LUs from a line
v Deletes a dependent logical unit from a nonswitched physical unit
v Changes certain operand values in PU and LU definition statements
v Adds or deletes frame relay PUs and their associated FRSESET definition
statements.

The active and inactive requirements for the reconfiguration operations are
shown in Table 10.
Table 10. Active and Inactive Status Requirements for Dynamic Reconfiguration of an NCP
Operation/ Resource Major Node LINE PU LU
Add LU Active Either Either N/A
Add PU Active Either N/A N/A
1
Delete PU Active Either Inactive Inactive
1
Delete LU Active Either Either Inactive
Move PU Active Either Inactive Inactive
Move LU Active Either Either Inactive
Note:
1. The current state and desired state of the resource must be inactive.

To prepare another host for backup and takeover, you can issue a VARY ACT
command with the UPDATE operand at a VTAM that does not own selected
NCP resources to prepare that VTAM for a future takeover of those resources.
The command fails if UPDATE is specified on the same command with the
LOGON, LOGMODE, WARM, or ACQ (as in VARY ACQ) operands. UPDATE
has no meaning on the initial activation of major nodes other than an NCP
major node.

Conflicts can arise between the NCP source file and the generated NCP load
module. If you modify the NCP source, moving PUs and LUs, use
UPDATE=ALL when activating an inactive NCP. Otherwise VTAM and NCP will
not agree on the location of the PUs and LUs. It is recommended that you
always use UPDATE=ALL for the initial activation of an NCP if you are using (or
plan to use) dynamic reconfiguration with that NCP. If the source file has
changed, VTAM will make the changes and bring up the NCP correctly. If the
source file has not changed, VTAM will bring up the NCP as usual.

You can use VARY ACT with the UPDATE operand to dynamically reconfigure a
frame relay switching equipment set (FRSESET). In order to modify a
FRSESET, you need to know whether the FRSESET was statically or
dynamically defined. If you are not sure, you can issue a DISPLAY
NET,ID=frseset_name command to find out. Statically means that the FRSESET
was included in the NCP generation. Dynamically means that the FRSESET
was not included in the NCP generation. Statically and dynamically defined PUs
cannot be specified in the same FRSESET; the PUs must be all static or all
dynamic.

If the FRSESET was dynamically defined, you can dynamically add and delete
PUs from the set. You can delete PUs with the MODIFY DR, VARY DRDS, or

Chapter 2. VTAM Operator Commands 435

VARY ACT
VARY ACT,UPDATE=ALL commands. You can add PUs only with the VARY
ACT,UPDATE=ADD or VARY ACT,UPDATE=ALL command.

If the FRSESET was statically defined, you can delete PUs from the set, but
you cannot add PUs. In practical terms, this means you need to delete the
entire FRSESET and then add it back dynamically in order to make changes.
For example, if you have a statically defined FRSESET containing two primary
PUs and you want to add two backup PUs, follow these steps:
1. Delete the two primary PUs, thereby deleting the FRSESET itself (because
it is empty).
2. Edit the VTAMLST source file to add the PU definitions for the backup PUs
and add the backup PUs to the FRSESET.
3. Use the VARY ACT command with UPDATE=ADD or UPDATE=ALL. The
VARY ACT command causes the FRSESET to be dynamically defined.

If you delete one or more PUs (using MODIFY DR or VARY DRDS) from a
statically defined FRSESET without deleting the whole FRSESET, VARY ACT
will cause the deleted PUs to be added back, but they will not be part of the
FRSESET.

The first PU under a frame relay line (the LMI) cannot be deleted and it cannot
be part of a FRSESET.

For more information on how to define frame relay lines, frame relay PUs, and
FRSESETs, see the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference.

Dynamic reconfiguration for local SNA major nodes:

This command adds and deletes LUs for local SNA major nodes.

The active and inactive requirements for the reconfiguration operations are
shown in Table 11.
Table 11. Active and Inactive Status Requirements for Dynamic Reconfiguration for a Local
SNA Major Node
Operation/ Resource Major Node LINE PU LU
Add LU Active Either Either N/A
Delete LU Active Either Either Inactive

UPDATE=IMPLICIT
only has meaning on the initial activation of an NCP. Otherwise
UPDATE=IMPLICIT has no effect. For the initial activation of an NCP,
UPDATE=IMPLICIT dynamically adds resources. If you specify
UPDATE=IMPLICIT for a TRL major node, it is changed to UPDATE=ADD.
UPDATE=ADD
allows you to add resources. The major node must be active, unless it is an
NCP major node, which can be either active or inactive. VTAM reads the
VTAMLST definition file for the major node and adds any new resources to
the current configuration. For a TRL major node, this is the default.
UPDATE=ALL
allows you to add, move, and delete resources in certain major nodes, and
to add, delete, and replace existing TRLEs in an active TRL major node.

436 SNA Operation

 VARY ACT
TRLEs that are in use, however, are not deleted and remain in the TRL
major node along with the new TRLEs.

Note: Moving resources requires that you issue the VARY ACT,UPDATE
command twice. Resource deletions occur during the first processing
of the command, and resource additions occur during the second
processing of the command. See the OS/390 eNetwork
Communications Server: SNA Network Implementation Guide for
more information on dynamic reconfiguration changes.

UPDATE=ALL also allows you to change certain VTAM-only operands in PU

and LU definition statements in the following active nodes:
v Local SNA
v NCP major node (VTAM-only operands)
v Switched major node.

See the major node descriptions in the OS/390 eNetwork Communications

Server: SNA Resource Definition Reference for more information on the
operands that you can change for each major node.
VRTGCPCP
applies for cross-domain resource managers (CDRM) and indicates whether the
virtual-route-based transmission group is to support CP-CP sessions. This
operand allows the value of the VRTGCPCP operand on the CDRM definition
statement to be overridden. If VRTGCPCP is not specified on the VARY ACT
command, CP-CP session capability over the virtual-route-based transmission
group connection is determined from the CDRM definition statement or from the
VRTGCPCP start option. If VRTGCPCP is specified on the VARY ACT
command, the value affects only a single activation instance. Subsequent
activations use the predefined values for that CDRM.

This operand is only valid if VRTG=YES is specified for the CDRM, and the
CDRM is in an inactive or connectable state; otherwise the command fails and
an error message is issued.
VRTGCPCP=YES
specifies that the virtual-route-based transmission group is to support
CP-CP sessions.
VRTGCPCP=NO
specifies that the virtual-route-based transmission group is not to support
CP-CP sessions.
WARM
applies only to certain major nodes (as shown in Figure 6 on page 416) and
specifies that the major node named in the ID operand is to be activated to the
status it had when it was last active. That is, those minor nodes that were
active the last time the major node was active are reactivated, and other
operator-modified values applicable to the major node or its minor nodes (such
as controller application name and logmode name for a logical unit) are
restored. By recording changes in a configuration restart file, VTAM tracks the
status of the minor nodes as well as operator changes to other checkpointed
parameters. For a list of the checkpointed parameters for each major node and
for a general description of the configuration restart facility, see the OS/390
eNetwork Communications Server: SNA Network Implementation Guide.

Chapter 2. VTAM Operator Commands 437

VARY ACT
The WARM operand is not allowed and the VARY ACT command fails in the
following circumstances:
v WARM and SCOPE are specified on the same command.
v WARM is specified for a major node that is already active.
v WARM is specified when activating a major node that has no associated
VSAM configuration restart file or whose configuration restart file has not
been used (that is, contains no checkpointed information).

If you used a VARY ACT,UPDATE=ALL command for dynamic reconfiguration of

the major node at some time prior to the warm start, the dynamic
reconfiguration changes stay in effect after the warm start. This is because
VTAM takes a checkpoint during the VARY ACT,UPDATE=ALL processing.

438 SNA Operation

 VARY ANS

VARY ANS Command

ÊÊ VARY NET ,ANS= OFF ,ID=line_name ÊÍ
ON ,ACT

Abbreviations
Operand Abbreviation
VARY V

Purpose
The VARY ANS (answer mode) command enables active switched SDLC lines with
dial-in capability to allow or disallow an incoming call from a physical unit defined in
a switched major node. For an incoming call to be allowed, an active line must be
in answer mode.

The mode setting can be specified in the definition statement for the line and can
be changed whenever the line is active by using this command. The mode setting
of a line can also be specified when the line is activated (see the description of the
ANS operand on the VARY ACT command).

The VARY ANS command is most often used for lines with both dial-in and dial-out
capability. To ensure that a line is available for dial-out requests, it can be taken out
of answer mode while it is still active. Incoming calls are blocked, but outgoing calls
proceed normally.

Operands
ACT
activates the line, if it is not active already.
ANS
specifies whether the line is to be put in answer mode.
ANS=ON
specifies that the line is to be put in answer mode. When a line is in answer
mode (and active), the answering subarea node accepts an incoming call
from a dial-in device and notifies VTAM of the call so that sessions can be
established.
ANS=OFF
specifies that the line is to be taken out of answer mode. If there is an
existing session using the line, ANS=OFF does not break the session, but
no further incoming calls are accepted after the session ends.
ID=line_name
specifies the name of an SDLC line. The line must be a switched line with
dial-in capability. The line must be active, unless the ACT operand is also
specified on this command.

Chapter 2. VTAM Operator Commands 439

VARY CFS

VARY CFS Command

ÊÊ VARY NET ,CFS ,ACTION= CONNECT ,STRNAME= ALL ÊÍ
DISCONNECT structure_name

Abbreviations
Operand Abbreviation
VARY V
ACTION=CONNECT CONNECT
ACTION=CONNECT CONN
ACTION=DISCONNECT DISCONN
ACTION=DISCONNECT DISC

Purpose
The VARY CFS command is used to connect to a VTAM coupling facility structure
or disconnect from a VTAM coupling facility structure. Normally, connecting or
disconnecting to a coupling facility structure is handled automatically by VTAM. The
VARY CFS command allows an operator to perform these functions outside normal
VTAM processing.

If VTAM is unable to connect to a coupling facility structure or loses its connection

to a coupling facility structure, it will use the event notification facility to know when
to attempt a reconnection to the coupling structure. The event notification facility will
notify VTAM when changes occur in coupling facility resources. This reconnection
process is automatic and requires no operator intervention. However, if VTAM
disconnects due to the VARY CFS,ACTION=DISCONNECT command, VTAM will
ignore event notifications for the particular structure. The VARY
CFS,ACTION=CONNECT command must be issued to cause VTAM to reconnect to
the structure and also enable event notification for the structure.

To determine if VTAM is using the event notification for a disconnected structure,

issue the D NET,STATS,TYPE=CFS command. Message IST1368I will be issued if
VTAM is receiving event notifications for the structure.

Operands
ACTION
specifies that VTAM is to attempt to connect to or disconnect from the coupling
facility structure specified by the STRNAME parameter.
ACTION=CONNECT
specifies that VTAM is to attempt to connect to the coupling facility structure
specified by the STRNAME parameter.
ACTION=DISCONNECT
specifies that VTAM is to disconnect from the coupling facility structure
specified by the STRNAME parameter.
STRNAME
specifies the name of the structure to connect to or disconnect from.

440 SNA Operation

 VARY CFS
STRNAME=ALL
specifies that VTAM will disconnect from all coupling facility structures.
STRNAME=ALL can be specified for ACTION=DISCONNECT only.
STRNAME=structure_name
specifies the name of the structure to connect to or disconnect from.

Chapter 2. VTAM Operator Commands 441

VARY DIAL

VARY DIAL Command

ÊÊ VARY NET,DIAL ,ID=resource_name ÊÍ
,CPCP= YES
NO

Abbreviations
Operand Abbreviation
VARY V

Purpose
The VARY DIAL command can be used to establish the following:
v A switched subarea connection so that LU-LU sessions can be started
v A switched connection to a type 1,2, or 2.1 device (adjacent link station)
v A CPSVRMGR session between a dependent LU requester (DLUR) and a
dependent LU server (DLUS).

Operands
CPCP
applies for adjacent link stations and allows the value of the CPCP operand on
the PU definition statement to be overridden. If CPCP is not specified on the
VARY DIAL command, the value for CP-CP session support on the connection
is determined from the PU definition statement or from the CPCP start option. If
CPCP is specified on the VARY DIAL command, the CP-CP session support on
the connection is taken from the command value for a single activation
instance. Subsequent activations use the predefined values for that PU.

If the resource does not support APPN, then an error message is issued and
the command fails.

The resource must be in a connectable state; otherwise the command fails and
an error message is issued. CP-CP session capability is determined during XID
exchange and cannot be changed after a session is established.
CPCP=YES
indicates that the connection is to support CP-CP sessions.
CPCP=NO
indicates that the connection is not to support CP-CP sessions.
ID=resource_name
specifies the name of a resource. This value can be one of the following:
v The name of the link station specified in the switched major node that
specifies the NCP or VTAM to be connected.
v A PU name that specifies a link station with a PUTYPE of 1,2, 2.1, 4, or 5
v The name of a PU supported by a DLUR.

442 SNA Operation

 VARY DRDS

VARY DRDS Command

ÊÊ VARY NET,DRDS ,ID=dr_file_name ÊÍ

Abbreviations
Operand Abbreviation
VARY V

Purpose
The VARY DRDS command dynamically reconfigures an NCP or a nonswitched
peripheral node. If the physical configuration of a communication controller is
changed (for example, a physical unit is moved from one line to another), the NCP
residing in the communication controller can be reconfigured without having to
generate a new NCP. To use this command, a previously filed set of statements
called a dynamic reconfiguration (DR) file must be available before the major
node can be reconfigured. For information on dynamic reconfiguration, see the
OS/390 eNetwork Communications Server: SNA Network Implementation Guide.
For information on creating a DR file, see the OS/390 eNetwork Communications
Server: SNA Resource Definition Reference.

Minor nodes that are dynamically added as a result of this command are
automatically activated if the DR definition file defines their initial status as active.

Dynamic reconfiguration for an NCP:

For an NCP, this command performs the following functions without regenerating
the NCP:
v Adds a nonswitched physical unit and its subordinate LUs to a line
v Adds a logical unit to a nonswitched physical unit
v Adds a type 2.1 PU to an NCP ESCON channel.
v Adds an independent LU to an NCP ESCON channel.
v Passes the GP3174 and RETRIES operands to NCP when dynamically adding a
PU.
v Moves a nonswitched physical unit and its subordinate LUs from one line to
another.
v Changes a nonswitched physical unit link station address.
v Deletes a nonswitched physical unit and its subordinate LUs from a line.
v Deletes a logical unit from a nonswitched physical unit.
v Deletes a type 2.1 PU from an NCP ESCON channel.
v Deletes an independent LU from an NCP ESCON channel.
v Deletes frame relay type 1 PUs. The first PU (the LMI) under a frame relay line
cannot be deleted.

The active and inactive requirements for VARY DRDS for an NCP are shown in
Table 12 on page 444.

Chapter 2. VTAM Operator Commands 443

VARY DRDS
Table 12. Active and Inactive Status Requirements for VARY DRDS for an NCP
Operation/ Resource Major Node LINE PU LU
Add LU Active Either Either N/A
Add PU Active Either N/A N/A
1
Delete PU Active Either Inactive Inactive
1
Delete LU Active Either Either Inactive
Move PU Active Either Inactive Inactive
Note:
1. The current state and desired state of the resource must be inactive.

In order to modify a frame relay switching equipment set (FRSESET), you need to
know whether the FRSESET was statically or dynamically defined. If you are not
sure, you can issue a DISPLAY NET,ID=frseset_name command to find out.
Statically means that the FRSESET was included in the NCP generation.
Dynamically means that the FRSESET was not included in the NCP generation.
Statically and dynamically defined PUs cannot be specified in the same FRSESET;
the PUs must be all static or all dynamic.

If the FRSESET was dynamically defined, you can dynamically add and delete PUs
from the set. You can delete PUs with the MODIFY DR, VARY DRDS, or VARY
ACT,UPDATE=ALL commands. You can add PUs only with the VARY
ACT,UPDATE=ADD or VARY ACT,UPDATE=ALL command.

If the FRSESET was statically defined, you can delete PUs from the set, but you
cannot add PUs. In practical terms, this means you need to delete the entire
FRSESET and then add it back dynamically in order to make changes. For
example, if you have a statically defined FRSESET containing two primary PUs and
you want to add two backup PUs, first delete the two primary PUs, thereby deleting
the FRSESET itself (because it is empty). Then edit the VTAMLST source file to
add the PU definitions for the backup PUs (if necessary) and add the backup PUs
to the FRSESET. Then use the VARY ACT command with UPDATE=ADD or
UPDATE=ALL. The VARY ACT command causes the FRSESET to be dynamically
defined.

If you delete one or more PUs (using MODIFY DR or VARY DRDS) from a statically
defined FRSESET without deleting the whole FRSESET, VARY ACT will cause the
deleted PUs to be added back, but they will not be part of the FRSESET.

The first PU under a frame relay line (the LMI) cannot be deleted and it cannot be
part of a FRSESET.

For more information on how to define frame relay lines, frame relay PUs, and
FRSESETs, see the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference.

Dynamic reconfiguration for local SNA major nodes:

This command adds and deletes LUs for local SNA major nodes.

The active and inactive requirements for the reconfiguration operations are shown
in Table 13 on page 445.

444 SNA Operation

 VARY DRDS
Table 13. Active and Inactive Status Requirements for VARY DRDS for Local SNA Major
Nodes
Operation/ Resource Major Node LINE PU LU
Add LU Active Either Either N/A
Delete LU Active Either Either Inactive

Operands
ID=dr_file_name
specifies the name of a dynamic reconfiguration file.

Chapter 2. VTAM Operator Commands 445

VARY HANGUP

VARY HANGUP Command

ÊÊ VARY NET,HANGUP ,ID=link_station_name ÊÍ

Abbreviations
Operand Abbreviation
VARY V

Purpose
VARY HANGUP is used to take down a switched subarea connection or a switched
connection to a type 1,2, or 2.1 device. This allows the connection to be terminated
when it is no longer necessary.

Note: VARY HANGUP only terminates the switched connection; it does not
deactivate the line or the physical unit.

Operands
ID=link_station_name
specifies the name of the link station. link_station_name can be the link station
in the switched major node that specifies the NCP or VTAM to be disconnected,
or link_station_name can be a link station (PU) with a PU type of 1,2, 2.1, 4 or
5.

446 SNA Operation

 VARY INACT

VARY INACT Command

Deactivate an NCP major node:

,CDLINK=ACT ,RMPO=NO
ÊÊ VARY NET,INACT ,ID=ncp_name Ê
,CDLINK= ACT ,RMPO= NO
INACT YES

Ê ÊÍ
,TYPE= FORCE
IMMED
REACT
UNCOND

Deactivate an NCP line:

ÊÊ VARY NET,INACT ,ID=line_name ÊÍ

,TYPE= FORCE
GIVEBACK
IMMED
UNCOND

Deactivate a CDRM major node:

ÊÊ VARY NET,INACT ,ID=node_name ÊÍ

,SAVESESS ,TYPE= FORCE
IMMED
UNCOND

Deactivate a CDRM minor node:

ÊÊ VARY NET,INACT ,ID=node_name Ê

,IDTYPE=SSCP ,SAVESESS

Ê ÊÍ
,TYPE= FORCE
IMMED
UNCOND

Deactivate a CDRSC minor node:

,DELETE=NO
ÊÊ VARY NET,INACT ,ID=node_name Ê
,DELETE= NO ,IDTYPE=CP
YES

Ê ÊÍ
,TYPE= FORCE
IMMED
UNCOND

Chapter 2. VTAM Operator Commands 447

VARY INACT
Deactivate the dynamic XCF local SNA major node:

ÊÊ VARY NET,INACT ,ID=ISTLSXCF ÊÍ

,TYPE= FORCE
IMMED
UNCOND

Deactivate a dynamic XCF local SNA PU:

ÊÊ VARY NET,INACT ,ID=name ÊÍ

,IDTYPE=XCFCP

Deactivate a dynamic switched PU:

ÊÊ VARY NET,INACT ,ID=pu_name ÊÍ

,TYPE= FORCE
IMMED
UNCOND

Deactivate a dependent LU requester (DLUR):

ÊÊ VARY NET,INACT ,ID=dlur_name ÊÍ

,TYPE= FORCE
IMMED
UNCOND

Deactivate a PU supported by a DLUR:

ÊÊ VARY NET,INACT ,ID=pu_name ÊÍ

,TYPE= FORCE
GIVEBACK
IMMED
REACT
UNCOND

Deactivate other PUs:

,FINAL=NO
ÊÊ VARY NET,INACT ,ID=pu_name Ê
,FINAL= NO
,TYPE= FORCE
IMMED
REACT
UNCOND
YES
,TYPE= FORCE
IMMED
UNCOND

448 SNA Operation

 VARY INACT

Ê ,ID=rtp_pu_name ,TYPE=FORCE ÊÍ

Deactivate other resources:

ÊÊ VARY NET,INACT ,ID=name ÊÍ

,TYPE= FORCE
IMMED
REACT
UNCOND

Abbreviations
Operand Abbreviation
VARY V
DELETE=YES DELETE or DELETE=Y
FINAL=YES FINAL or FINAL=Y
NO N
RMPO=YES RMPO or RMPO=Y
SAVESESS S
TYPE=FORCE F or FORCE
TYPE=GIVEBACK G or GIVEBACK
TYPE=IMMED I or IMMED
TYPE=REACT R or REACT
TYPE=UNCOND U or UNCOND
YES Y

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
TYPE=IMMED, code only I or IMMED. Do not code TYPE=I.

Purpose
The VARY INACT command deactivates VTAM resources. For SDLC switched and
nonswitched links in a multiple-domain network, it can also return ownership of the
line and its associated resources to the original SSCP without disrupting LU-LU
sessions. This is usually done as part of error recovery procedures after one SSCP
has taken over a failed SSCP’s resources. For information on the deactivation of
links and link stations, see the OS/390 eNetwork Communications Server: SNA
Network Implementation Guide.

Figure 8 on page 450 shows each resource type for which the command is valid
and which operands can be used on the command. A large dot means the operand
applies to that resource. An I or F in the table shows what value is substituted if an
IMMED, UNCOND, FORCE, or REACT operand is specified for a resource to which
it does not apply.

Chapter 2. VTAM Operator Commands 449

VARY INACT

VARY INACT

N D
C T CO
CT

EA /UN
PE ME K
YE /NO

SA =YE FCP
FI TE= /INA

AC
TY SES NO
P
NO

SC

D
E
S

EB
P

PO XC
CT

RC
S/
YE

S/
TY = C
TY = S

TY GIV
DE K=A

TY =FO

IM
RM E =

=R
PE
PE
L=

=
=
P
L IN

PE
PE
LE

VE
PE
NA

TY

TY
CD

ID=
ID
ID
ID

Adjacent CP major node

F Application program major node
F Application program minor node
I Channel-attachment major node
F Channel link
Channel link station
F CDRSC major node
F CDRSC minor node
F F CDRSC minor node - adjacent CP
F CDRM major node
F CDRM minor node
I XCA major node
F Nonswitched line
Link station
F Switched line
I I Local non-SNA major node
F Local non-SNA logical unit
I Local SNA major node
Local SNA physical unit
F Local SNA logical unit
F LUGROUP major node
F Model major node
NCP major node
F Nonswitched line
F Switched line
Link station
Physical unit
F Logical unit
I Switched major node
Switched physical unit
Switched link station
F Switched logical unit
I Dynamic switched major node
I Dynamic switched physical unit
F Dynamic switched logical unit
XCF local SNA major node
XCF local SNA physical unit
CP name of XCF local SNA physical unit

Figure 8. Valid Resource Types for VARY INACT

450 SNA Operation

 VARY INACT
Operands
CDLINK
applies only to the deactivation of an NCP. It specifies whether active, leased,
cross-domain links and link stations are to remain active after the NCP major
node is deactivated.

This option is effective only on the VARY INACT or VARY REL command that
begins the deactivation of an NCP. For example, if a second VARY INACT
(perhaps with the IMMED operand specified) is entered before the first VARY
INACT command completes, CDLINK does not apply to the second command
and is ignored if specified.

For information on the deactivation of links and link stations, see the OS/390
eNetwork Communications Server: SNA Network Implementation Guide.
CDLINK=ACT
specifies that active cross-domain links and link stations are to remain
active after the NCP major node is deactivated, so that sessions routing
information through the NCP over such links can continue without
disruption.
CDLINK=INACT
specifies that cross-domain links and link stations are to be deactivated as
part of the NCP deactivation. Any session traffic over such links might be
disrupted, depending on whether such links and link stations are also
owned by some other host. See the OS/390 eNetwork Communications
Server: SNA Network Implementation Guide for a discussion of how shared
ownership affects the results of deactivating a link or link station.
DELETE
applies only to deactivation of cross-domain resources (CDRSCs). It specifies
whether they can be deactivated and, at the same time, the RDTE storage
associated with the resource released.

If you specify DELETE without including a qualifier (YES or NO), the RDTE
storage associated with the resource is released when the CDRSC is
deactivated. This is the same result as if you specified DELETE=YES.
DELETE=YES
specifies that the RDTE storage associated with the resource is released
when the CDRSC is deactivated. If the CDRSC exists in ISTCDRDY,
DELETE=YES is not necessary.
DELETE=NO
specifies that the RDTE storage associated with the resource is not
released when the CDRSC is deactivated.

If the CDRSC exists in ISTCDRDY, DELETE=NO is not applicable. If

DELETE=NO is specified, it is ignored.
FINAL
specifies whether the physical unit specified in the ID operand will be
reactivated.
FINAL=YES
specifies that there are no immediate plans to reactivate the physical unit.
The actual effects of this operand are device-dependent, and could include
such functions as automatic power-off. See the appropriate component’s
manual for the specific effects of a DACTPU type hex 01 command on a

Chapter 2. VTAM Operator Commands 451

VARY INACT
particular device. For physical units in a local SNA or switched major node,
FINAL is meaningful only if the physical unit is fully active before
deactivation begins.

FINAL=YES is ignored for type 2.1 physical units if ACTPU is not sent.

If you enter FINAL=YES, you cannot enter TYPE=REACT.

FINAL=NO
specifies that there are plans to reactivate the physical unit.
ID=name
specifies the name of any active major or minor node that is to be deactivated.
The name can be a network-qualified name. It cannot be a USERVAR or
LUALIAS name. If the name specified on the ID operand is network-qualified,
this name is considered to be the real name of the resource. The name can be
an ACB name or an alias name, as long as it is not network-qualified. (See the
description of the ID operand on the VARY ACT command for an example of
how you can specify a network-qualified application name.)

To deactivate the dynamic local SNA major node for XCF connections, specify
ID=ISTLSXCF.

Attention: Deactivating ISTLSXCF removes all dynamic PUs and TRLEs and
causes VTAM to leave the XCF group.If TCP/IP is using XCF connections,
those connections are also terminated.

To deactivate a dynamic XCF local SNA PU representing the connection to

another VTAM, you can specify one of the following:
v The name of the PU
v The CP name of the other VTAM with IDTYPE=XCFCP.
Notes:
1. For a gateway NCP, resources in the nonnative network are not affected
by the VARY INACT command.
2. The PUs and LUs within a model major node cannot be individually
deactivated with the VARY INACT command. After either a dynamic
switched major node or a dynamic switched PU has been deactivated, it
cannot be reactivated without being redefined to VTAM. The major
difference between dynamically defined devices and statically defined
devices is that after a dynamically defined PU is deactivated, its elements
will be deleted from VTAM.
3. For ID=pu_name, there is no relationship between the PU and the
independent LU. Deactivation of the PU ends any LU-LU sessions that are
using the connection. However, the actual independent LU resource
remains active because it might be in session over another adjacent link
station connection.
Network addresses for the boundary function CDRSC are reclaimed from
the terminated sessions if appropriate (for example, if the cross-domain
resource is a switched LU), but the RDTE remains intact.
4. For ID=rtp_pu_name, TYPE=FORCE is required.
5. For ID=appl_name, TYPE=FORCE is required to override persistence and
terminate the application and sessions.
6. For a model application program, the state of the model is changed from
connectable (CONCT) to inactive (INACT). This means that it can no

452 SNA Operation

 VARY INACT
longer be used to build dynamic application programs. Active dynamic
application programs built from the model are not affected by the
deactivation of the model.
For any dynamic application program built from the model, when CLOSE
macro processing for the dynamic application program is complete, the
definition of the dynamic application program is deleted. The dynamic
application program will no longer be known to VTAM and will not appear
in the output of any DISPLAY commands.
7. For ID=ISTCDRDY, VTAM deletes all dynamically created CDRSC RDTEs
and terminates their associated sessions. CP-CP and CPSVRMGR
sessions involving this host are terminated if the partner’s CDRSC RDTE
was dynamically defined. To avoid losing the CP-CP and CPSVRMGR
sessions, you can predefine a CDRSC for the partner LU. The name on
the CDRSC statement or the LU statement should be the CPNAME of the
session partner. Predefining the CDRSC is suggested only if you expect to
deactivate ISTCDRDY while CP-CP sessions are active. (This should be
rare.) See the OS/390 eNetwork Communications Server: SNA Resource
Definition Reference for more information on defining cross-domain
resources and independent LUs.
8. For a CDRM, you can specify a network-qualified name, but this does not
remove the restriction that the non-network-qualified CDRM name must be
unique across networks.
9. Issuing a VARY INACT command to terminate the CP-CP session with an
adjacent node might cause later session establishment requests to fail. To
resolve the problem, reactivate the CP-CP session or else reactivate the
link with CPCP=NO so that it will no longer be used in directed search
routing.
10. For a dependent LU requester, VTAM deactivates the CDRSC node that
represents the CPSVRMGR session between the DLUR and the DLUS. If
a dependent LU requester is adjacent to a dependent LU server, the
CDRSC also represents the CP-CP session. For a normal deactivation, all
pending and queued sessions for supported PUs and LUs fail, but
inactivation does not complete until all active LU-LU sessions are
terminated. A forced deactivation ends all current sessions for LUs and
PUs supported by this DLUR. See the OS/390 eNetwork Communications
Server: SNA Network Implementation Guide for further information about
the CPSVRMGR session.
11. For a PU supported by a DLUR, VTAM deactivates the PU. If there are no
active or pending SSCP-PU sessions using the CPSVRMGR session, the
CPSVRMGR session is deactivated.
IDTYPE
specifies the type of resource that the ID operand names. If several types of
resources share the same name, IDTYPE identifies which resource the
command should act on.

IDTYPE is required and has no default if the resource named on the ID

operand is the host CDRM. IDTYPE is optional if the resource is an adjacent
CP or an external CDRM; if both an adjacent CP and an external CDRM are
found, the default is IDTYPE=SSCP. If you attempt to deactivate the host CP,
the command will fail.
IDTYPE=CP
deactivates the CP with the name specified on the ID operand.

Chapter 2. VTAM Operator Commands 453

VARY INACT
IDTYPE=SSCP
deactivates the SSCP with the name specified on the ID operand.
IDTYPE=XCFCP
deactivates the dynamic XCF local SNA PU representing the connection to
another VTAM, when the ID operand specifies the CP name of the other
VTAM.
RMPO
applies only to NCP major nodes. RMPO specifies whether the communication
controller in which the NCP is running is to be powered off automatically at the
completion of the deactivation.

RMPO can be done only by an implicitly activated link station.

RMPO=YES
powers off the communication controller automatically. The communication
controller must be link-attached, and must support the remote power-off
facility for this operand to be effective. Use the same link for the RMPO
operation as you used earlier to load and activate the remote NCP.
RMPO=NO
does not power off the communication controller automatically.
SAVESESS
applies to CDRM major and minor nodes. SAVESESS specifies that active
LU-LU sessions set up using the SSCP-SSCP session, which is being
terminated by the VARY INACT command, remain active. Queued or pending
sessions using the specified CDRM are terminated.

After you deactivate a CDRM with SAVESESS, the active sessions that remain
are no longer associated with the CDRM. Therefore, subsequent activations
and deactivations of the CDRM have no effect on these sessions.

The SAVESESS operand is not required during normal deactivation, and if

specified, does not change the normal deactivation.
TYPE
specifies the type of deactivation (other than normal deactivation). Unless
IMMED, UNCOND, FORCE, REACT, or GIVEBACK is specified, normal
deactivation occurs. The TYPE operand is not valid for an ADJCP major node.

During normal deactivation, queued and pending sessions fail; the VARY INACT
command is queued until all active sessions are terminated.

Note: During normal deactivation of an NCP, some active sessions might be

disrupted. For more information on the effects of deactivating an NCP,
see the OS/390 eNetwork Communications Server: SNA Network
Implementation Guide.
TYPE=IMMED or TYPE=UNCOND
means that the specified resource and applicable subordinate resources are
to be deactivated immediately.

If TYPE=IMMED or TYPE=UNCOND, sessions involving the affected

resources are disrupted. However, before completing the deactivation,
VTAM waits for application programs being deactivated, or for application
programs in session with resources being deactivated, to formally end their
sessions (that is, issue CLSDST).

454 SNA Operation

 VARY INACT
A TYPE=IMMED or TYPE=UNCOND operand can be specified on a VARY
INACT command entered while a normal deactivation is in progress.
Notes:
1. TYPE=IMMED and TYPE=UNCOND have the same function.
TYPE=UNCOND is consistent with the “VARY TERM Command” on
page 469 .
2. If you specify IMMED or UNCOND on this command for a dependent
LU requester, the value is automatically promoted to FORCE.
TYPE=FORCE
means that the specified resource and applicable subordinate resources are
to undergo forced deactivation. This type of deactivation might be advisable
for resources that do not respond to normal or immediate (I) deactivation
requests, or that are preventing completion of a VTAM HALT command. A
forced deactivation instructs VTAM to deactivate its internal representations
of the applicable resources and to send appropriate deactivation requests to
the resources or their superior nodes, without waiting for responses to
these requests. Therefore, a forced deactivation of a resource could result
in a mismatch between VTAM’s record of the status of a resource and the
actual status of the resource in the network.

If TYPE=FORCE, sessions involving the resources are disrupted, and

VTAM might have to wait (depending on how a given application program is
coded) for application programs being deactivated, or for application
programs in session with resources being deactivated, to formally end their
sessions (that is, issue CLSDST) before completing the deactivation. A
forced deactivation might cause VTAM to enter the wait state. It could then
be necessary to deactivate an associated resource in order to free the
system.

Forced deactivation of a local device might result in a slight wait because

VTAM might have I/O outstanding for the device. VTAM cannot complete
deactivation until the outstanding I/O is completed.
Notes:
1. Normally, all sessions involving a resource that undergoes forced
deactivation terminate as a result of this command, but there are
exceptions. For example, if there is no CDRM-CDRM session with the
owning SSCP of the session partner, or if the CDRM of a session
partner is unknown because of takeover, those sessions are not
terminated.
2. Forced deactivation of an NCP link unconditionally takes down the link,
regardless of the shared ownership of the link. However, any lines
under the NCP that would remain active during an automatic network
shutdown (ANS) remain active after a forced deactivation of an NCP link
or link station.
3. V INACT FORCE deletes a dynamic CDRSC independent of the
CDRSCTI start option. This will cause a buffer trace to be turned off.
4. For ID=rtp_pu_name, TYPE=FORCE is required.
5. For ID=appl_name, TYPE=FORCE is required to override persistence
and terminate the application and sessions.

Chapter 2. VTAM Operator Commands 455

VARY INACT
The TYPE=FORCE operand can be specified on a VARY INACT command
entered while a normal or immediate deactivation or a VTAM HALT is in
progress.
TYPE=REACT
means that the specified resource and applicable subordinate resources are
to undergo deactivation and subsequent reactivation. This type of
deactivation and reactivation might be advisable for resources that are not
responding to VTAM commands, but that the operator wants to remain
active. A forced reactivation instructs VTAM to deactivate its internal
representations of the applicable resources and to send appropriate
deactivation requests to the resources or their superior nodes, waiting for
responses before beginning reactivation. If any of the resources still do not
respond, a VARY INACT command with the TYPE=FORCE operand should
be entered to force deactivation of those resources.

A device contained in a dynamic switched major node cannot be

deactivated with TYPE=REACT. After such a PU is deactivated, it is no
longer known to VTAM and cannot be reactivated with an operator
command. Dynamic LUs under a dynamic PU can be deactivated and
subsequently reactivated as long as their PU is not deactivated.
Notes:
1. Normally, sessions involving a REACT deactivated resource terminate
as a result of this command, but there are exceptions. For example, if
there is no CDRM-CDRM session with the owning SSCP of the session
partner, or if the CDRM of a session partner is unknown because of
takeover, those sessions are not terminated. These sessions also do
not respond to reactivation, and are not displayed as activated in
response to this command.
If this command is issued for an NCP, the SSCP-PU session between
VTAM and the NCP is disrupted. VTAM does not terminate any LU-LU
sessions; they might or might not be disrupted, depending on what the
NCP does for automatic network shutdown (ANS). LU-LU sessions
involving type 2.1 PUs generally stay up.
A second VARY INACT command with TYPE=REACT issued before the
first one has time to complete has the same effect as specifying the
TYPE=FORCE option.
Any type of deactivation request (normal, immediate, or forced) can be
entered while a forced reactivation is in progress if you want termination
of the reactivation. As previously stated, forced deactivation might be
the only effective deactivation method if a resource fails to respond to
the forced reactivation.
2. If you specify REACT on this command for a dependent LU requester,
the value is automatically promoted to FORCE.
TYPE=GIVEBACK
applies to SDLC switched and nonswitched links, leased lines, and
switched PUs that are supported by dependent LU requesters (DLURs) that
allow ANS=CONTINUE. (Token ring is considered to be a switched
connection.) The specified resource and applicable subordinate resources
are released from this SSCP. VTAM terminates queued and pending
sessions before deactivating the resource. If the specified resource was
defined with ANS=CONTINUE, active LU-LU sessions remain active.

456 SNA Operation

 VARY INACT
If the link does not support giveback, VTAM waits for the session to
terminate before giveback is completed.

Under certain conditions, sessions returned with giveback remain

displayable in the SSCP that issued the giveback. Either of the following
conditions produce such results:
v If the session partner is in the domain of the SSCP owning the resource
before giveback
v If the session is cross-network and the old owner of the resource was a
gateway SSCP and was in session with the gateway NCP.
Notes:
1. Issuing this command overrides any outstanding command for the node.
2. If you specify GIVEBACK on this command for a dependent LU
requester that does not support ANS=CONTINUE, the value is
automatically promoted to FORCE.

Chapter 2. VTAM Operator Commands 457

VARY INOP

VARY INOP Command

,END=NO
ÊÊ VARY NET,INOP ,ID=line_name ÊÍ
,END= NO
YES

Abbreviations
Operand Abbreviation
VARY V
END=YES END

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for END=YES,
code only END.

Purpose
You can use the VARY INOP command to terminate a manual dial operation if the
VTAM operator is unable to complete the call.

A physical unit in a switched major node can be dialed either automatically or

manually to establish a session with a logical unit. For manual dialing, VTAM issues
a message containing the following information:
v The name of the line that VTAM will try to use to make the connection. The line
must be a switched line with dial-out capability.
v The telephone number that the VTAM operator is to dial. This number is the
number specified in the DIALNO operand of the appropriate PATH statement
associated with the physical unit that the operator is dialing.

After receiving this information, the VTAM operator must try to make the connection
by dialing the specified telephone number. If the operator is unable to complete the
connection, the operator should enter the VARY INOP command either to ask
VTAM to search for an alternate path or to ask VTAM to terminate the session
request without a search for an alternate path.

Operands
END
specifies whether VTAM is to search for an alternate line on which to send the
session request.
END=NO
searches for another appropriate line to the physical unit.
END=YES
does not search for another appropriate line to the physical unit.
ID=line_name
specifies the name of the line used to attempt the manual dial connection. This
name is included in the VTAM message requesting manual dialing.

458 SNA Operation

 VARY LOGON

VARY LOGON Command

ÊÊ VARY NET ,LOGON=appl_name ,ID=slu_name Ê
,LOGMODE=logon_mode_name

Ê ÊÍ
,ACT

Abbreviations
Operand Abbreviation
VARY V

Purpose
You can use the VARY LOGON command to change an existing automatic logon
specification or to create an automatic logon specification. This command applies to
any device-type logical unit, whether channel-attached or link-attached. Neither the
device-type logical unit, which is the secondary LU, nor the primary LU receiving
the automatic logon has to be active when the VARY LOGON command is issued.

Note: This command is restricted to the VTAM owning the SLU specified in the ID
operand.

An automatic logon specification remains in effect until one of the following occurs:
v The primary logical unit controlling the secondary logical unit is changed with
VARY LOGON or VARY ACT,LOGON command.
v A VARY NOLOGON command is entered for the secondary logical unit.

Note: If you use the VARY LOGON command to create or change an automatic
logon specification, be aware that later use of a VARY ACT,UPDATE=ALL
command for dynamic reconfiguration can undo the effects of the VARY
LOGON command. This is because the LOGAPPL value in the definition file
overrides the value that was established with the VARY LOGON command.
Even if no LOGAPPL is coded in the definition file, VTAM assumes a null
value for LOGAPPL and the null value overrides the VARY LOGON value. To
prevent the automatic logon specification from being deleted unintentionally,
code the LOGAPPL definition statement with the desired value.

Any automatic logon request made as a result of this specification might be

accepted or rejected by the primary LU.

The VARY LOGON command specifies only a primary LU session partner for
automatic logon (when the specified secondary LU becomes available for a
session); it does not activate the secondary LU. To activate the secondary LU (or a
resource to which the secondary LU is subordinate) and change the automatic
logon specification at the same time, use the VARY ACT command with the
LOGON operand (see the LOGON operand on the VARY ACT command on page
429 for more information).

For independent SLUs, the VARY LOGON command initiates a session with the
controlling PLU only if there are no sessions already established with the specified
PLU. Repeated use of the VARY LOGON command for the same LU and

Chapter 2. VTAM Operator Commands 459

VARY LOGON
controlling PLU establishes only a single session. A series of VARY LOGON
commands for the same LU specifying different controlling PLUs establishes
sessions between the LU and each of the controlling PLUs specified. The
controlling PLU is the one specified in the last command. The other sessions are
not automatically re-established after they terminate.

Note: When you enable automatic logons to TSO (either by using the VARY
LOGON command or by specifying LOGAPPL=TSO in a definition
statement), a new logon attempt is made when the user session ends, even
if it ends in error. This is because it is not the session with TSO that is
failing. If a loop occurs, for example message IKT029I being issued
repeatedly, you can break the automatic logon relationship by issuing a
VARY NOLOGON command. If you have a user-written application in your
network called TSO, then enabling automatic logons to TSO could have
unpredictable results.

Operands
ACT
activates any subordinate resources within the scope of this command. If ACT
is specified on the VARY LOGON command, other operands of the VARY ACT
command are available. See Figure 6 on page 416 for the operands you can
use. Use the LOGON column of that table to identify which resources are
applicable.
ID=slu_name
specifies the name of the secondary LU. This name can be one of the following:
v A device-type logical unit
v A resource with subordinate device-type logical units
v A boundary function CDRSC.

If the value is a boundary function CDRSC, the boundary function CDRSC

named must be known to VTAM at the time the command is issued. That is, it
must have been predefined or dynamically defined because of another session.
In addition, it must have a default ALS list.

Boundary function CDRSCs are only subordinate to the CDRSC major node
where they were defined (ISTPDILU or ISTCDRDY). Boundary function
CDRSCS are not subordinate to any device type major node (NCP, local SNA,
etc.), nor to a line or PU, even if the independent LU was defined within or
under these resources.

Because of this, independent LUs are not subordinate to any PU. Therefore, the
sift-down to subordinate LUs does not affect independent LUs unless the ID
value is a CDRSC major node.

The VARY LOGON command affects only LUs. If another resource type is
specified, the logical units affected are those subordinate to the resource that is
specified on this command.

The name can be a network-qualified name. If the name specified on the ID

operand is network-qualified, this name is considered to be the real name of the
resource.
LOGMODE=logon_mode_name
specifies the name of the logon mode entry to be used for any logon initiated

460 SNA Operation

 VARY LOGON
for a logical unit as a result of this command. This logon mode name also
becomes the logon mode name for all future automatic logons performed by
VTAM for logical units within the scope of this command, and for their
controlling primary LUs (if any).

LOGON can be specified without LOGMODE, but LOGMODE cannot be

specified without LOGON. If LOGMODE is specified without the LOGON
operand, LOGMODE is ignored and no error message is sent.

If LOGMODE is not specified, the LOGMODE value specified in any previous

command applicable to a logical unit within the scope of this current VARY
LOGON command is used. If no LOGMODE value was ever specified for a
given logical unit within the scope of this command, the logical unit’s default
value is used.
LOGON=appl_name
specifies the name of an application program (primary LU) to which any
secondary LUs within the scope of this command are to be logged on. The
application name can be network-qualified. If it is, the network identifier is
considered to be real, but the resource name is considered to be generic (that
is, the resource name can be either the real application name or a USERVAR
name).

If the application name is an ACB name, and the ACB name matches the name
on the APPL definition statement, then you can use a network-qualified ACB
name.

If a USERVAR is found, VTAM resolves its name to the name of the VTAM
application with which it is currently associated. If a USERVAR with this name is
not found, VTAM searches for an application program with this name.

If the primary LU is an application program in this domain, the name must be

that of an application program minor node within an active application program
major node.

If the primary LU is a predefined CDRSC, the CDRSC must be active.

If the primary LU is a device-type LU, it must be attached to the same NCP as

the secondary LU.

Chapter 2. VTAM Operator Commands 461

VARY NOLOGON

VARY NOLOGON Command

ÊÊ VARY NET ,NOLOGON= * ,ID=slu_name ÊÍ
cdrsc_name
plu_name
uservar_name

Abbreviations
Operand Abbreviation
VARY V

Purpose
Use the VARY NOLOGON command to delete an existing automatic logon
specification that was established by the VARY LOGON command or the LOGAPPL
operand on a definition statement. This command applies to any device-type logical
unit, whether channel-attached or link-attached. The device-type logical unit does
not have to be active when the VARY NOLOGON command is issued; however, the
major node must be active.

The VARY NOLOGON command deletes any existing automatic logon specification
for the named logical unit. When the command is issued, any active or pending
sessions that resulted from an automatic logon specification will continue. When
these sessions end, however, the logical unit will no longer have an automatic logon
specification until a VARY LOGON is entered for it.

Note: If you use the VARY NOLOGON command to delete an automatic logon
specification that was coded on the LOGAPPL operand of a definition
statement, be aware that later use of a VARY ACT,UPDATE=ALL command
for dynamic reconfiguration can undo the effects of the VARY NOLOGON
command. This is because the LOGAPPL value in the definition file overrides
the operator command. To prevent the automatic logon specification from
being added back unintentionally, delete the LOGAPPL operand from the
definition statement.

Operands
ID=slu_name
specifies the name of the secondary LU. This name can be one of the following:
v A device-type logical unit
v A resource with subordinate device-type logical units
v A boundary function CDRSC.

Boundary function CDRSCs are subordinate only to the CDRSC major node
where they were defined (ISTPDILU or ISTCDRDY). Boundary function
CDRSCS are not subordinate to any device type major node (NCP, local SNA,
etc.), nor to a line or PU, even if the independent LU was defined within or
under these resources.

Because of this, independent LUs are not subordinate to any PU. Therefore, the
sift-down to subordinate LUs does not affect independent LUs unless the ID
value is a CDRSC major node.

462 SNA Operation

 VARY NOLOGON
The VARY NOLOGON command affects only LUs. If another resource type is
specified, the logical units affected are those subordinate to the resource
specified on the command.

The name can be a network-qualified name. If name is an ACB name, and the
ACB name matches the name on the APPL definition statement, then you can
use a network-qualified ACB name. (See the description of the ID operand on
the VARY ACT command for an example of how you can specify a
network-qualified application name.)
NOLOGON
specifies the scope of the VARY NOLOGON command. It can be a
network-qualified name. The NOLOGON operand must specify the same name
that was used on the LOGON operand or the LOGAPPL definition, with the
following exception (because the host’s network ID is assumed):
v In NETA, LOGON=NETA.CICS can be cancelled by NOLOGON=NETA.CICS
or NOLOGON=CICS
v In NETA, LOGON=CICS can be cancelled by NOLOGON=NETA.CICS or
NOLOGON=CICS.

If the application name is an ACB name, and the ACB name matches the name
on the APPL definition statement, then you can use a network-qualified ACB
name. (See the description of the ID operand on the VARY ACT command for
an example of how you can specify a network-qualified application name.)
NOLOGON=plu_name
specifies that only logical units that are either:
v Identified by slu_name or
v Subordinate to slu_name

and have plu_name as their controlling PLU are to have their automatic
logon specification deleted.
NOLOGON=cdrsc_name
specifies the name of a CDRSC minor node within an active CDRSC major
node. NOLOGON=cdrsc_name must be specified when the primary LU is
an application program in another domain or another network.
NOLOGON=uservar_name
specifies the name of a USERVAR that VTAM resolves to be the application
with which it is currently associated. If a USERVAR with the specified name
is not found, VTAM searches for an application program with that name.
NOLOGON=*
specifies that all secondary logical units that are either:
v Identified by slu_name or
v Subordinate to slu_name

are to have their automatic logon specification deleted, regardless of which

PLU is currently in control.

Chapter 2. VTAM Operator Commands 463

VARY PATH

VARY PATH Command

ÊÊ VARY NET,PATH= NOUSE ,GID=group_id ,ID=switched_major_node_name ÊÍ
USE ,PID=path_id ,ID=switched_pu_name

Abbreviations
Operand Abbreviation
VARY V

Purpose
Use this command to modify the availability of a dial-out path to a specific switched
physical unit or a group of dial-out paths within a switched major node.

A physical unit in a switched major node can be dialed through one or more dial-out
paths associated with the physical unit. Switched path control is initially established
in a switched major node definition by the USE operand of the PATH statement
associated with a physical unit. Unless USE=NO has been specified, the path is
automatically enabled for use by VTAM when the physical unit is activated.

Note: The PATH statement referred to on this command description is in the

switched major node definition; do not confuse it with the PATH statements
used to define a path definition set.

Dial-out path usage can be altered by enabling or disabling:

v A single dial-out path to the physical unit (represented by a PID)
v A logical group of dial-out paths in the same switched major node (represented
by a GID).

Operands
GID=group_id
specifies the group identifier of the dial-out paths to be made usable or
unusable. The group identifier is defined by the GID operand of the PATH
statements in a switched major node definition. This value must be a decimal
integer 1–255.
ID=name
specifies the name of the switched major node (if the GID operand is specified)
or the name of the physical unit in a switched major node (if the PID operand is
specified) for which dial-out path status is to be changed.
PATH
specifies the paths identified by the PID or GID operand to enable or disable.
PATH=USE
specifies that one or more paths identified by the PID or GID operand are
to be enabled (changed from unusable to usable), if they are not already
enabled.
PATH=NOUSE
specifies that one or more paths identified by the PID or GID operand are
to be disabled (changed from usable to unusable), if they are not already

464 SNA Operation

 VARY PATH
disabled. If the path is currently in use, PATH=NOUSE does not take effect
until after the existing dial connection is broken.
PID=path_id
specifies the path identifier of the dial-out path to be made usable or unusable.
This value must be a decimal integer 1–255.

The path identifier is defined by the PID operand of a PATH statement. This
PATH statement must be associated with the physical unit specified in the ID
operand of this command. (This PATH statement is in the switched major node
definition; do not confuse it with the PATH statements used to define a path
definition set.)

Chapter 2. VTAM Operator Commands 465

VARY REL

VARY REL Command

Release a previously acquired NCP:

,CDLINK=ACT
ÊÊ VARY NET,REL ,ID=ncp_name Ê
,OWNER=host_name ,CDLINK= ACT
INACT

Ê ÊÍ
,TYPE= GIVEBACK
IMMED

Release a PU:

,FINAL=NO
ÊÊ VARY NET,REL ,ID=pu_name Ê
,OWNER=host_name ,FINAL= NO
YES

Ê ÊÍ
,TYPE=IMMED

Abbreviations
Operand Abbreviation
VARY V
FINAL=YES FINAL
TYPE=GIVEBACK G or GIVEBACK
TYPE=IMMED I or IMMED

When using an abbreviation in place of an operand, code the abbreviation exactly

as shown in the table. For example, when coding the abbreviation for
TYPE=IMMED, code only I or IMMED. Do not code TYPE=I.

Purpose
Use the VARY REL (release) command to release a previously acquired NCP or to
release a physical unit attached by a nonswitched line to an NCP (regardless of
whether the physical unit was previously acquired).

The VARY REL command is usually applied to a previously acquired NCP or

physical unit attached to an NCP as part of a backup and recovery procedure in a
multiple-domain network. A physical unit attached to an NCP can also be released
as part of a switched network backup procedure in either a single- or
multiple-domain network. The purpose of the VARY REL command is to relinquish
ownership of the following resources:
v NCP resources that are normally owned by another host (if the NCP was
activated before being acquired)

466 SNA Operation

 VARY REL
v All resources within an NCP, including the NCP itself (if the NCP was acquired
without having been previously activated)
v An individual physical unit and its logical units.

Releasing resources within an NCP makes them unknown to VTAM until the NCP is
reacquired, and any active traces for subordinate lines are deactivated; releasing a
physical unit makes it unusable by the releasing host and makes its logical units
unknown until the physical unit is reacquired. Releasing an NCP that had not been
previously active also results in deactivation of the NCP. (Here there is no functional
difference between the VARY REL and VARY INACT commands.)

As part of a switched network backup procedure for NCP resources, the VARY REL
command can be entered for a physical unit that was not previously acquired. The
purpose of the VARY REL command is to make the physical unit’s logical units
unknown to VTAM so that a corresponding switched physical unit definition
(representing the same physical device with a different physical unit name but with
the same logical unit names) can be activated.

Operands
CDLINK
applies only to an NCP being released. It specifies whether any active
cross-domain links and link stations are to remain active (in the NCP, not with
respect to VTAM) after they are released. That is, the CDLINK operand
specifies whether VTAM is to send deactivation requests to cross-domain links
and link stations when the internal representations of these resources are
deactivated as part of the VARY REL command processing.

For an NCP that was activated before being acquired, the CDLINK operand is
ignored. The NCP remains active after the VARY REL command completes.
Even though VTAM considers such links and link stations to be inactive, the
NCP still considers them to be owned by VTAM. Therefore, specifying
CDLINK=ACT in an environment of shared link and link station ownership might
provide no benefits (because the shared ownership prevents traffic disruption
on the link), but could cost the ability of an other host to become a shared
owner (because the share count is one closer to its limit than it needs to be). It
could also prevent the original host from acquiring and activating the link. See
the OS/390 eNetwork Communications Server: SNA Network Implementation
Guide for details of special considerations and cautions that might be applicable
to deactivation of cross-domain links and link stations.

For an NCP acquired without having been previously activated, this option is
effective only on the first command (whether VARY INACT or VARY REL)
applied to the NCP. Any subsequent CDLINK specifications are ignored.
CDLINK=ACT
specifies that active cross-domain links and link stations are to remain
active after they are released, so that sessions routing information through
the NCP over such links can continue without disruption.
CDLINK=INACT
specifies that cross-domain links and link stations within the scope of the
release are to be deactivated as part of the NCP release processing. Any
session traffic over such links might be disrupted (depending on whether
such links and link stations are also owned by some other host). See the

Chapter 2. VTAM Operator Commands 467

VARY REL
OS/390 eNetwork Communications Server: SNA Network Implementation
Guide for a discussion of how shared ownership affects the results of
deactivating a link or link station.
FINAL
specifies whether the physical unit specified on the ID operand will be
reactivated.
FINAL=YES
specifies that there are no immediate plans to reactivate the physical unit.
The actual effects of this operand are device-dependent, and could include
such functions as automatic power-off. See the appropriate component’s
manual for the specific effects of a DACTPU type hex 01 command on a
particular device. For physical units in a local SNA or switched major node,
FINAL is meaningful only if the physical unit is fully active before
deactivation begins.

FINAL=YES is ignored for type 2.1 physical units if ACTPU is not sent.
FINAL=NO
specifies that there are plans to reactivate the physical unit.
ID=name
specifies the name of the NCP or physical unit to be released.
OWNER=host_name
specifies that the command is to apply only to resources defined with the
OWNER operand, and whose owning SSCP matches the host_name specified
in the command. host_name cannot be the name of the VTAM host from which
you are issuing this command.
TYPE
specifies the type of release. If neither GIVEBACK nor IMMED is specified,
normal release occurs. Normal release does not break existing sessions, but
does prevent the establishment of new sessions with nodes within the scope of
this command.
TYPE=GIVEBACK
applies only to an NCP and specifies that all subordinate resources that are
capable of nondisruptive deactivation are to be released without disruption
to existing LU-LU sessions.

Note: Because GIVEBACK is only supported at the line level, a normal

release is performed for the following resources:
v Lines attached to this NCP that are not capable of nondisruptive
deactivation
v PUs that are attached to a line that is not being released.
TYPE=IMMED
specifies immediate release. If you specify TYPE=IMMED, sessions
involving the resources being released are disrupted.

You can specify TYPE=IMMED on a VARY REL command entered while a

normal or giveback release is in progress.

468 SNA Operation

 VARY TERM

VARY TERM Command

ÊÊ VARY NET,TERM ,LU1=lu_name Ê

,LU2=lu_name
,LU2=lu_name
,LU1=lu_name
,PLU=plu_name
,SLU=slu_name
,SLU=slu_name
,PLU=plu_name
,SID=session_id

,TYPE=UNCOND ,SCOPE=ACT ,NOTIFY=YES

Ê ÊÍ
,TYPE= COND ,SCOPE= ACT ,NOTIFY= NO
FORCE ALL YES
UNCOND Q

Abbreviations
Operand Abbreviation
VARY V

Purpose
The VARY TERM command terminates a session or group of sessions. The
command can identify one or several of the following sessions for termination:
v A single session by its session identifier (SID)
v All of the sessions for which a specified logical unit is the primary session partner
(PLU)
v All of the sessions for which a specified logical unit is the secondary session
partner (SLU)
v All of the sessions between a specified pair of logical units having a specified
primary/secondary relationship as session partners (PLU and SLU)
v All of the sessions for which a specified logical unit is a session partner, without
regard to its primary or secondary status (LU1)
v All of the sessions between a specified pair of logical units, without regard to
their primary/secondary relationship as session partners (LU1 and LU2).

You can use the “DISPLAY SESSIONS Command” on page 170 to display the
sessions that are to be terminated with this command. If a session is displayed with
an “A-” session state, you cannot issue a VARY TERM command for it at this host.
Instead, issue VARY TERM from one of the session end points.

VTAM overrides persistence and terminates the application and sessions normally.

Issuing a VARY TERM command to terminate the CP-CP session with an adjacent
node might cause later session establishment requests to fail. To resolve the
problem, reactivate the CP-CP session or else reactivate the link with CPCP=NO so
that it will no longer be used in directed search routing.

Chapter 2. VTAM Operator Commands 469

VARY TERM
Operands
LU1=lu_name
identifies the logical unit whose sessions are to be terminated. If you also
specify the LU2 operand, only sessions involving both specified logical units are
terminated. LU1 can be either the primary LU or the secondary LU.

lu_name can be a network-qualified name. If the name is network-qualified, it is

considered to be the real name of the resource. If a non-network-qualified name
is specified, the name can be an ACB name, an alias name, or the real name of
a local resource.

If a cross-network CDRSC is to be specified on the LU1 operand and the

CDRSC is defined using NQNMODE=NQNAME (either by definition or start
option), it must be specified as a network-qualifed name.
LU2=lu_name
identifies the logical unit whose sessions are to be terminated. If you also
specify the LU1 operand, only sessions involving both specified logical units are
terminated. LU2 can be either the primary LU or the secondary LU.

lu_name can be a network-qualified name. If the name is network-qualified, it is

considered to be the real name of the resource.

If a cross-network CDRSC is to be specified on the LU2 operand and the

CDRSC is defined using NQNMODE=NQNAME (either by definition or start
option), it must be specified as a network-qualifed name.
NOTIFY
specifies whether VTAM is to send a notification message to the operator when
all affected sessions have ended.
NOTIFY=YES
sends a notification message to the operator when all affected sessions
have ended.
NOTIFY=NO
does not send a message when all affected sessions have ended.
PLU=plu_name
identifies a primary logical unit. All sessions in which this logical unit functions
as the primary session partner are terminated. If you also specify the SLU
operand, only sessions involving both specified logical units in the specified
primary/secondary relationship are terminated.

The value for plu_name can be a network-qualified name. If the name is

network-qualified, it is considered to be the real name of the resource. If a
network-qualified name is not specified, the default network identifier will be
from the network where the command was issued.

If a cross-network CDRSC is to be specified on the PLU operand and the

CDRSC is defined using NQNMODE=NQNAME (either by definition or start
option), it must be specified as a network-qualifed name.
SCOPE
specifies the scope of the command.
SCOPE=ACT
terminates only active sessions.

470 SNA Operation

 VARY TERM
Note that the termination of an active session between a device-type logical
unit and its controlling primary LU terminates the session (unless the
session is terminated using TYPE=FORCE) but does not alter the basic
controller relationship between them.

Deactivation and reactivation of the logical unit (including error recovery

procedures), or use of the logical unit by another primary LU, results in the
re-establishment of the logical unit’s session with its controlling application
program. If this is not the case, the controller session can be re-established
with a VARY LOGON command or by a specific session request from the
primary LU.
SCOPE=ALL
terminates all sessions, whether active or queued.
SCOPE=Q
terminates only queued sessions.

Note that the termination of a queued session between a device-type logical

unit and its controlling primary LU does not alter the basic controller
relationship between them.
SID=sessionid
identifies the VTAM session to terminate. You can display the session ID by
issuing the DISPLAY ID,SCOPE=ALL command. The application program can
be in either this domain (application program minor node) or another domain
(CDRSC minor node). The session ID must be a valid hex number.
SLU=slu_name
identifies a secondary logical unit. All sessions in which this logical unit
functions as the secondary session partner are terminated. If you specify the
PLU operand, only sessions involving both specified logical units in the
specified primary/secondary relationship are terminated.

slu_name can be a network-qualified name. If the name is network-qualified, it

is considered to be the real name of the resource.

If a cross-network CDRSC is to be specified on the SLU operand and the

CDRSC is defined using NQNMODE=NQNAME (either by definition or start
option), it must be specified as a network-qualifed name.
TYPE
specifies the type of session termination to be performed. If this command
applies to queued sessions, they are terminated. This command will terminate
only the primary session between the PLU and SLU; the backup session will
not terminate.
Notes:
1. To avoid re-driving the session for an automatic logon relationship, issue
VARY TERM,TYPE=COND.
2. For a phantom session (an active session for which no SIB exists in this
host), issue V NET,TERM,TYPE=UNCOND or V NET,TERM,TYPE=FORCE
to terminate the session.
3. If the VARY TERM command is issued in the SLU’s host after takeover has
occurred and the PLU for the session resides in another host, the session
might terminate properly. In that case, the VARY TERM command should be
issued from the host where the PLU resides.

Chapter 2. VTAM Operator Commands 471

VARY TERM
4. For a CP-CP session, TYPE=COND or UNCOND is converted by VTAM to
TYPE=FORCE. The session will not be automatically re-established even if
other CP-CP session-capable connections are subsequently activated. If
you want to reactivate the session, issue a VARY
ACT,ID=adjacent_cp,IDTYPE=CP command.
5. For a CPSVRMGR session between a DLUR and a DLUS, TYPE=COND or
UNCOND is converted to FORCE. If the DLUR allows ANS=CONTINUE,
VTAM performs GIVEBACK for PUs supported by the DLUR, and current
LU-LU sessions are not disrupted because the LUs become shadow
resources.
TYPE=COND
specifies conditional termination.

Note: This command is rejected if the termination request is for a session

with an unknown partner.

If this command applies to active sessions, they might be disrupted. PLUs

involved in such sessions are notified of the operator’s request for
termination and have the option to terminate the session.

If the PLU is an independent LU, the session remains active because

independent LUs cannot perform orderly termination. If the session remains
active, it is marked “session end pending” in each SSCP that knows of the
termination request.
TYPE=FORCE
specifies forced termination. If this command applies to active sessions,
they are disrupted, and application programs involved in such sessions are
notified of the disruption.

If a controlling relationship is set up for the logical unit, the session

re-drives because the termination was of an abnormal type.
TYPE=UNCOND
specifies unconditional termination.

If this command applies to active sessions, they are disrupted. PLUs

involved in such sessions are notified of the disruption.

If a controlling relationship is set up for the logical unit, the session

re-drives because the termination was of an abnormal type.

472 SNA Operation

Chapter 3. Logon Manager Operator Commands
Logon Manager Operator Commands
The logon manager permits a terminal user to pass through VTAM and log on to an
independent application running on a transaction processing facility (TPF). More
specifically, it allows a dependent secondary logical unit (SLU) to initiate a session
with an independent primary logical unit (PLU).

The logon manager is a VTAM application. Any similarity between VTAM

commands and logon manager commands is coincidental.

This chapter is a reference to the logon manager operator commands. It includes a

description of each command’s format and applicable operands. The descriptions
are arranged alphabetically by command name.

Command Fundamentals
A logon manager operator command consists of:
v The command name or its abbreviation
v A procedure name, referred to as a procname in the command syntax, that tells
the operating system to send the command to the logon manager for processing.
The procname must be the same as the procname specified in the logon
manager START command.

Note: The logon manager procedure name is not VTAM.

v Operands that describe the operation to be performed.

Syntax Notation
See “How to Read the Syntax Diagrams” on page 9 for details on the operator
command syntax notation.

Entering Operator Commands

Logon manager operator commands are entered and logon manager messages are
received at the system console or remote network console. Logon manager
commands cannot exceed 80 characters and must be entered on a single input line
from whatever input device is being used.

Using MVS System Symbols

You can use the following MVS system symbols in the values you specify on TPF
logon manager operator commands:
&SYSCLONE
Represents a 1–2-character shorthand notation for the name of the system
&SYSNAME
Represents a 1–8-character system name
&SYSPLEX
Represents a 1–8-character sysplex name
&SYSR1
Represents a 1–6-character sysres volume
© Copyright IBM Corp. 1984, 1998 473
Logon Manager Commands
&installation-defined system symbol
Represents a 1–8-character identifier. You can define this symbol to be any
identifier you want.

The substitution text for these system symbols is defined in MVS and is substituted
by MVS in place of the symbols when commands are processed. Refer to OS/390
MVS Initialization and Tuning Reference for information about how to define the
symbols in MVS.

MVS system symbols can be used to eliminate the need to know the exact name of
a resource on the system from which a command is issued.

Correct and Incorrect Commands

The logon manager issues messages indicating whether commands are accepted
or rejected.

When a command is entered with correct syntax and valid operands, the logon
manager issues a message of acknowledgement. Note, however, that the
acknowledgement of a command does not imply that the command will complete.

If the command contains a syntax error or incorrect operands, the logon manager
issues one or more error messages and rejects the command.

474 SNA Operation

 Logon Manager MODIFY HELP

MODIFY HELP Command

ÊÊ MODIFY procname,HELP ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY HELP command displays the syntax and a brief description of each
logon manager command.

Operands
procname
must be the same as the procname specified in the logon manager START
command.
HELP
displays logon manager help information.

Examples
Displaying logon manager help:
modify elmngr,help
ELM022I HELP REQUEST ACCEPTED
ELM023I VALID COMMAND PARAMETERS ARE:
ELM024I HELP ...GET VALID COMMAND FORMATS
ELM025I INFO,ID=NNNNNNNN ...GET STATUS FOR RESOURCE NAMED NNNNNNNN
ELM0261 INFO,ID=CLU ...GET STATUS FOR EACH CONTROL LOGICAL UNIT
ELM027I INFO,ID=CLU,PEND ...GET STATUS FOR EACH PENDING CLU
ELM028I INFO,ID=APPL ...GET STATUS FOR EACH SUPPORTED APPLICATION
ELM029I INFO,ID=APPL,PEND ...GET STATUS FOR EACH PENDING APPL
ELM030I INFO,ID=ALL ...GET STATUS FOR EACH CLU AND APPL
ELM031I INFO,ID=ALL,PEND ...GET STATUS FOR EACH PENDING CLU AND APPL
ELM032I MEMBER=MMMMMMM ...PROCESS DEFINITION MEMBER MMMMMMMM
ELM033I MINLINK=VVV,ID=ALL...SET MINLINK VALUE TO VVV (1 - 255)
ELM034I FOR EACH SUPPORTED APPLICATION
ELM035I MINLINK=VVV,ID=NNNNNNNN... SET MINLINK VALUE FOR APPL NNNNNNNN
ELM036I STOP ...REQUESTS CLOSEDOWN

Chapter 3. Logon Manager Operator Commands 475

Logon Manager MODIFY INFO

MODIFY INFO Command

ÊÊ MODIFY procname,INFO ,ID= name ÊÍ
APPL ,PEND
CLU
ALL

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY INFO command displays information about logon manager resources.

Operands
procname
must be the same as the procname specified in the logon manager START
command.
ID identifies the resource or resources to include in the display.
ID=name
displays only the named resource.
ID=APPL
displays only logon manager TPF applications.
ID=CLU
displays only channel-attached control point LUs.
ID=ALL
displays both logon manager TPF applications and channel-attached control
point LUs.
PEND
displays only resources with a status of pending (that is, resources in the
process of being activated or deactivated).

If ID=name, displays the named resource only if the resource is in a pending

state.

If ID=APPL, displays each logon manager application in a pending state.

If ID=CLU, displays each channel-attached control point LU in a pending state.

If ID=ALL, displays each logon manager application and each channel-attached

control point LU in a pending state.

Resulting Display
The resulting display shows:
v The resource name
v The resource session status (active, inactive, or pending)

476 SNA Operation

 Logon Manager MODIFY INFO
v The reason code for the resource, if appropriate
v The number of session initiation requests sent to the resource.

Examples
Displaying a specific logon manager resource:
modify elmngr,info,id=trapl
ELM014I NAME: TYP: STATUS: CURRENT: CONTROL: REASON: INITS:
ELM040I TRAPL CLU ACTIVE SESCNT=19 SESLMT=32 0

Displaying pending logon manager TPF applications:

modify elmngr,info,id=appl,pend
ELM014I NAME: TYP: STATUS: CURRENT: CONTROL: REASON: INITS:
ELM040I RES APPL PENDACTV LNKCNT=5 MINLINK=1 OPNOST 0
ELM040I FIN APPL PENDINAC LNKCNT=4 MINLINK=2 LOSTERM 22

Displaying logon manager channel-attached control point LUs:

modify elmngr,info,id=clu
ELM014I NAME: TYP: STATUS: CURRENT: CONTROL: REASON: INITS:
ELM040I TRAPL CLU ACTIVE SESCNT=0 SESLMT=0 0

Displaying all logon manager resources:

modify elmngr,info,id=all
ELM014I NAME: TYP: STATUS: CURRENT: CONTROL: REASON: INITS:
ELM040I RES APPL INACTIVE LNKCNT=0 MINLINK=1 0
ELM040I FIN APPL INACTIVE LNKCNT=0 MINLINK=2 0
ELM040I TEST1 APPL INACTIVE LNKCNT=0 MINLINK=1 0
ELM040I TEST2 APPL INACTIVE LNKCNT=0 MINLINK=1 0

Chapter 3. Logon Manager Operator Commands 477

Logon Manager MODIFY MEMBER

MODIFY MEMBER Command

ÊÊ MODIFY procname,MEMBER=member_name ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY MEMBER command redefines the network configuration known to the
logon manager. If the system programmer has modified the specified member, this
command implements the changes by rebuilding the logon manager control blocks
using the new definitions.

Operands
procname
must be the same as the procname specified in the logon manager START
command.
MEMBER=member_name
identifies the member of the ELMDEFDS file to read.

478 SNA Operation

 Logon Manager MODIFY MINLINK

MODIFY MINLINK Command

ÊÊ MODIFY procname,MINLINK=number_of_lus ,ID= appl_name ÊÍ
ALL

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY MINLINK command changes the minimum number of supporting
channel-attached, control-point logical units that the logon manager requires before
allowing the TPF application to enter into a session.

Operands
procname
must be the same as the procname specified in the logon manager START
command.
ID specifies whether to change the number of required links for one TPF
application or for all applications.
ID=appl_name
identifies the application for which the number of required links is to
change.
ID=ALL
specifies that the minimum number of required links should change for all
applications.
MINLINK=number_of_lus
specifies the minimum number of supporting channel-attached, control-point
logical units that the logon manager requires before allowing the TPF
application to enter into a session. Specify a decimal integer 1–255.

Chapter 3. Logon Manager Operator Commands 479

Logon Manager MODIFY STOP

MODIFY STOP Command

ÊÊ MODIFY procname,STOP ÊÍ

Abbreviations
Operand Abbreviation
MODIFY F

Purpose
The MODIFY STOP command terminates a logon manager session. When this
command is issued, the logon manager shuts down its ACBs, and returns control to
MVS.

Operands
procname
must be the same as the procname specified in the logon manager START
command.
STOP
terminates the logon manager. Although all active sessions continue until
completion, the logon manager denies any requests to initiate new sessions.
When all active sessions end, the logon manager terminates.

The VTAM operator commands HALT, HALT QUICK, and HALT CANCEL also
can be used to terminate a logon manager session. The effect of these
commands on the logon manager is the same as their effect on any VTAM
application.

480 SNA Operation

 Logon Manager START

START Command
ÊÊ START procname ÊÍ

Abbreviations
Operand Abbreviation
START S

Purpose
The START command starts the logon manager. Enter this command from either
the master console or a secondary system console.

The system programmer supplies logon manager start options in the JCL used to
start the logon manager. If the options are not supplied, VTAM prompts the operator
for the required options.

Operands
procname
is the name of the MVS procedure containing the JCL necessary to start the
logon manager.

This procname must be used for all logon manager commands.

Chapter 3. Logon Manager Operator Commands 481

Logon Manager START

482 SNA Operation

Appendix A. Cross-Reference for VTAM DISPLAY Commands
This appendix is supplied to help you determine which DISPLAY command to use
to locate a specific piece of information. The list of DISPLAY command output is not
exhaustive, but it does contain the most widely used output.

The DISPLAY commands are listed across the top of the table with the information
in the output examples located down the left side of the table. To determine which
DISPLAY command displays a given piece of information, locate the information on
the left side and read across to find a large dot. A dot indicates that the command
provides the requested piece of information. More than one dot indicates that more
than one DISPLAY command displays the requested piece of information.

An example of the usage for this table would be if you want to display an access
method control block name (ACB name). First you would locate “ACB name” on the
left side of the table. Next, read across the table and identify the columns where
there are dots. In this case, this information can be displayed by three different
DISPLAY commands: APPLS, ID, and PENDING. Refer to the specific DISPLAY
command in “Chapter 2. VTAM Operator Commands” on page 9, for details on how
to display a particular piece of information using a command.

© Copyright IBM Corp. 1984, 1998 483

Cross-Reference for DISPLAY Commands

DISPLAY Command

BNCOSMAP

LUGROUPS
APPNTOSA
ADJSSCPS
ADJCLUST

APINGDTP

DIRECTRY

GROUPS
CDRSCS
BFRUSE

CLSTRS

CONVID
CDRMS

DLURS
ADJCP

APPLS

LMTBL
APING

LINES
CNOS

DISK
CSM

EXIT
COS

ID
DISPLAY Command Output
Access method control block (ACB name)
Active sessions
Adjacent cluster table definitions
Adjacent CP
Adjacent SSCP tables
Adjacent subarea address
Adjacent subarea node
APINGD instance limit
Application program
Application program name
APPN directory database
APPN route information
Buffer pool data
Buffer trace
Buffer usage
CDRM
CDRM for a CDRSC
Channel-attached links
Channel unit address (CUA)
Checkpoint date and time
Class-of-service mapping
Class-of-service name
Class-of-service (COS) table
Clusters
Common service area (CSA) buffers
Communication scanner processor (CSP)
Conversation ID (CONVID)
CP - CP session information
Cross-domain resource (CDRSCS)
Current transmission group (CTG)
Data compression
Data space usage
Dependent LU requester
Destination node
Destination subarea address
Dump name
Dump procedure address
Dynamic CDRSC suppport
Elapse time (ETIME)
Element address
Exit routines
Expansion limit
Explicit route length
Explicit route (ER) number

Figure 9. DISPLAY Output Cross Reference (A-E) (Part 1 of 2)

484 SNA Operation

 Cross-Reference for DISPLAY Commands

DISPLAY Command

MAJNODES

VTAMSTOR
VTAMOPTS
SATOAPPN

SRCHINFO
SESSIONS

STATIONS
NCPSTOR

TSOUSER
STORUSE
SNSFILTR

USERVAR
NETSRVR

PENDING
PATHTAB

RSCLIST
MODELS

TRACES
SAMAP
ROUTE

TERMS
TABLE
PATHS

STATS

TOPO
TGPS

TRL
DISPLAY Command Output
Access method control block (ACB name)
Active sessions
Adjacent cluster table definitions
Adjacent CP
Adjacent SSCP tables
Adjacent subarea address
Adjacent subarea node
APINGD instance limt
Application program
Application program name
APPN directory database
APPN route information
Buffer pool data
Buffer trace
Buffer usage
CDRM
CDRM for a CDRSC
Channel-attached links
Channel unit address (CUA)
Checkpoint date and time
Class-of-service mapping
Class-of-service name
Class-of-service (COS) table
Clusters
Common service area (CSA) buffers
Communication scanner processor (CSP)
Conversation ID (CONVID)
CP - CP session information
Cross-domain resource (CDRSCS)
Current transmission group (CTG)
Data compression
Data space usage
Dependent LU requester
Destination node
Destination subarea address
Dump name
Dump procedure address
Dynamic CDRSC suppport
Elapse time (ETIME)
Element address
Exit routines
Expansion limit
Explicit route length
Explicit route (ER) number

Figure 9. DISPLAY Output Cross Reference (A-E) (Part 2 of 2)

Appendix A. Cross-Reference for VTAM DISPLAY Commands 485

Cross-Reference for DISPLAY Commands

DISPLAY Command

BNCOSMAP

LUGROUPS
APPNTOSA
ADJSSCPS
ADJCLUST

APINGDTP

DIRESTRY

GROUPS
CDRSCS
BFRUSE

CLSTRS

CONVID
CDRMS

DLURS
ADJCP

LMTBL
APPLS
APING

LINES
CNOS

DISK
CSM

EXIT
COS

ID
DISPLAY Command Output
Generalized PIU trace (GPT)
Generalized TG (GTG)
Group identifier (GID)
I/O traces
IP address
Independent LUs
Intermediate routing node buffers
Intermediate routing node trace
Job name
Line Group
Line name
Line trace
Line type
Lines/links
Link station
Load module name
Load procedure status
Logical unit (LU)
Logical unit name (LUNAME)
Logon mode name
Major node name
Major node data
Major node subordinate resources
Minor node data
Minor node subordinate resources
Model LUs
Model PUs
Negpoll (negative response polling)
Network control program (NCP)
Network ID
Network node servers
Node characteristics
Node type
Origin node
Owned TGs
Paths, switched

Figure 10. DISPLAY Output Cross Reference (G-P) (Part 1 of 2)

486 SNA Operation

 Cross-Reference for DISPLAY Commands

DISPLAY Command

MAJNODES

VTAMSTOR
VTAMOPTS
SATOAPPN

SRCHINFO
SESSIONS

STATIONS
NCPSTOR

TSOUSER
SNSFILTR

STORUSE

USERVAR
NETSRVR

PATHTAB
PENDING

RSCLIST
MODELS

TRACES
SAMAP
ROUTE

TERMS
TABLE
PATHS

STATS

TOPO
TGPS

TRL
DISPLAY Command Output
Generalized PIU trace (GPT)
Generated TG (GTG)
Group identifier (GID)
I/O traces
IP address
Independent LUs
Intermediate routing node buffers
Intermediate routing node trace
Job name
Line group
Line name
Line trace
Line type
Lines/links
Link station
Load module name
Load procedure status
Logical unit (LU)
Logical unit name (LUNAME)
Logon mode name
Major node name
Major node data
Major node subordinate resources
Minor node data
Minor node subordinate resources
Model LUs
Model PUs
Negpoll (negative response polling)
Network control program (NCP)
Network ID
Network node servers
Node characteristics
Node type
Origin node
Owned TGs
Paths, switched

Figure 10. DISPLAY Output Cross Reference (G-P) (Part 2 of 2)

Appendix A. Cross-Reference for VTAM DISPLAY Commands 487

Cross-Reference for DISPLAY Commands

DISPLAY Command

BNCOSMAP

LUGROUPS
APPNTOSA
ADJSSCPS
ADJCLUST

APINGDTP

DIRECTRY

GROUPS
CDRSCS
BFRUSE

CLSTRS

CONVID
CDRMS

DLURS
ADJCP

LMTBL
APPLS
APING

LINES
CNOS

DISK
CSM

EXIT
COS

ID
DISPLAY Command Output
Path identifier (PID)
Physical unit (PU)
Physical unit name
Primary LU
Resource use count
SAW sense filter
Scanner interface trace (SIT)
Search requests
Secondary LU
Session ID
Session limit
Sessions
SIO count
Start options
Stepname
Storage
Subarea address
Subarea mapping table
Table name

Table type
TCP job name
Telephone number
Transmission data rate
Transmission group data
Transmission priority (TP)
Transport resource list entry
TSO trace
TSO user ID
USERVAR class
USERVAR name
USERVAR type

VCNS user
Virtual route number
VTAM internal trace
VTAM segment type
Weight of node or TG

Figure 11. DISPLAY Output Cross Reference (P-W) (Part 1 of 2)

488 SNA Operation

 DISPLAY Command

MAJNODES

VTAMSTOR
VTAMOPTS
SATOAPPN

SRCHINFO
SESSIONS

STATIONS
NCPSTOR

TSOUSER
SNSFILTR

STORUSE

USERVAR
NETSRVR

PATHTAB
PENDING

RSCLIST
MODELS

TRACES
SAMAP
ROUTE

TERMS
TABLE
PATHS

STATS

TOPO
TGPS

TRL
DISPLAY Command Output
Path identifier (PID)
Physical unit (PU)
Physical unit name
Primary LU
Resource use count
SAW sense filter
Scanner interface trace (SIT)
Search requests
Secondary LU
Session ID
Session limit
Sessions
SIO count
Start options
Stepname
Storage
Subarea address
Subarea mapping table
Table name
Table type
TCP job name
Telephone number
Transmission data rate
Transmission group data
Transmission priority (TP)
Transport resource list entry
TSO trace
TSO user ID
USERVAR class
USERVAR name
USERVAR type
VCNS user
Virtual route number
VTAM internal trace
VTAM segment type
Weight of node or TG

Figure 11. DISPLAY Output Cross Reference (P-W) (Part 2 of 2)

Appendix A. Cross-Reference for VTAM DISPLAY Commands 489

490 SNA Operation
Appendix B. Notices
This information was developed for products and services offered in the U.S.A. IBM
may not offer the products, services, or features discussed in this document in other
countries. Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product, program,
or service is not intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However,
it is the user’s responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
500 Columbus Avenue
Thornwood, NY 10594
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply to
you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this publication at any
time without notice.

Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Corporation
P.O. Box 12195
3039 Cornwallis Road
Research Triangle Park, NC 27709-2195
U.S.A.

© Copyright IBM Corp. 1984, 1998 491

 Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.

All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.

492 SNA Operation

Trademarks
The following terms are trademarks of the IBM Corporation in the United States or
other countries or both:

ACF/VTAM IMS/ESA
Advanced Peer-to-Peer Networking LANStreamer
AD/Cycle Library Reader
AIX LPDA
AIX/ESA MVS/DFP
AnyNet MVS/ESA
APPN MVS/SP
AS/400 MVS/XA
AT NetView
BookManager Nways
C/370 OfficeVision/MVS
CICS OS/2
C/MVS OS/390
Common User Access PR/SM
CT PROFS
CUA PS/2
DATABASE 2 RACF
DB2 RETAIN
DFSMS RISC System/6000
DFSMShsm RS/6000
DFSMS/MVS S/370
DRDA SAA
ESA/390 SP
ESCON SQL/DS
ES/9000 System/360
ES/9370 System/370
EtherStreamer System/390
Extended Services SystemView
FFST TURBOWAYS
First Failure Support Technology UNIX System Services
GDDM VM/ESA
Hardware Configuration Definition VTAM
IBM 3090
IBMLink
IMS

The following terms are trademarks of other companies:

ATM is a trademark of Adobe Systems, Incorporated.

BSC is a trademark of BusiSoft Corporation.

CSA is a trademark of Canadian Standards Association.

Appendix B. Notices 493

 DCE is a trademark of The Open Software Foundation.

HYPERchannel is a trademark of Network Systems Corporation.

UNIX is a registered trademark in the United States and other countries licensed
exclusively through X/Open Company Limited.

Microsoft, Windows, and the Windows 95 logo are trademarks or registered

trademarks of Microsoft Corporation.

Other company, product, and service names, which may be denoted by a double
asterisk (**), may be trademarks or service marks of others.

494 SNA Operation

Bibliography
v VTAM
eNetwork Communications
v TCP/IP
Server for OS/390 V2R6
Publications Ask your IBM marketing representative for more
information.
Following are descriptions of the books in the
eNetwork Communications Server for OS/390 Planning
V2R6 library. The books are arranged in the
following categories: OS/390 eNetwork Communications Server: SNA
v Softcopy Information Planning and Migration Guide (SC31-8622). This
guide helps you upgrade to eNetwork
v Marketing Information
Communications Server for OS/390 V2R6. It
v Planning includes:
v Installation, Resource Definition, and Tuning v Installation procedures
v Operation v Planning to upgrade
v Customization – Upward and downward compatibility
v Writing Application Programs – Software and hardware requirements
v Diagnosis – Storage requirements
v Messages and Codes – Impacts of new functions and enhancements
v APPC Application Suite. performed without changes to user
v Multiprotocol Transport Networking (MPTN) interfaces
Architecture publications – Changes to installation process
v Upgrading user interfaces
The complete set of unlicensed books in this
– Changes to start options
section can be ordered using a single order
number, SBOF-7011. – Changes to buffer pools
– Changes to definition statements
Softcopy Information – Changes to IBM-supplied default
user-definable tables and modules
IBM Networking Softcopy Collection Kit – Changes to user-definable table
CD-ROM(SK2T-6012). macroinstructions
– Changes to commands
The softcopy library contains softcopy versions of
the licensed and unlicensed books for eNetwork – Changes to messages
Communications Server for OS/390 V2R6. – Changes to SNA application programming
interface
All of the unlicensed and licensed books described – Changes to installation-wide exit routines
in this section are available in softcopy on this
– Changes to control blocks
CD-ROM. These softcopy files can be read using
any of the IBM BookManager READ programs. v Implementing optional functions and
They can also be read with the IBM Library enhancements introduced in eNetwork
Reader program shipped on this CD. Communications Server for OS/390 V2R6.
– Overview of each new function and
The CD also contains softcopy of the unlicensed enhancement introduced since VTAM V4R4
books of many other products. – Pointers to other books in the library where
implementation details can be found.
Marketing Information
OS/390 eNetwork Communications Server: IP
A Networking Overview and the following IBM Planning and Migration Guide (SC31-8512). This
Networking Previews are available: book is intended to help you plan for TCP/IP

© Copyright IBM Corp. 1984, 1998 495

Bibliography
whether you are migrating from a previous version book in conjunction with the OS/390 eNetwork
or installing TCP/IP for the first time. This book Communications Server: SNA Network
also identifies the suggested and required Implementation Guide.
modifications needed to enable you to use the
enhanced functions provided with TCP/IP. OS/390 eNetwork Communications Server: SNA
Resource Definition Samples (SC31-8566). This
Installation, Resource Definition, book contains sample definitions to help you
implement VTAM functions in your networks, and
Configuration, and Tuning includes sample major node definitions. Use this
book in conjunction with the OS/390 eNetwork
Program Directory. This document is shipped with Communications Server: SNA Network
the product tape and explains the steps for Implementation Guide and OS/390 eNetwork
installing VTAM and TCP/IP. Communications Server: SNA Resource Definition
Reference.
OS/390 eNetwork Communications Server: IP
Configuration Guide (SC31-8513). This book is for OS/390 eNetwork Communications Server:
people who want to configure, customize, AnyNet SNA over TCP/IP (SC31-8578). This guide
administer, and maintain TCP/IP. Familiarity with provides information to help you install, configure,
MVS operating system, TCP/IP protocols, and IBM use, and diagnose SNA over TCP/IP.
Time Sharing Option (TSO) is recommended.
OS/390 eNetwork Communications Server:
OS/390 eNetwork Communications Server: SNA AnyNet Sockets over SNA (SC31-8577). This
Network Implementation Guide (SC31-8563). This guide provides information to help you install,
book presents the major concepts involved in configure, use, and diagnose Sockets over SNA. It
implementing a SNA network, and includes: also provides information to help you prepare
v Buffer pools, slowdown, pacing, storage application programs to use sockets over SNA.
considerations
v Implementation considerations Operation
v Sample major node definitions
v Migration considerations OS/390 eNetwork Communications Server: IP
User’s Guide (GC31-8514). This book is for
v Tables and filters people who want to use TCP/IP for data
v TSO, VCNS, and other programs that run with communication activities such as FTP and Telnet.
VTAM Familiarity with MVS operating system and IBM
v Tuning procedures Time Sharing Option (TSO) is recommended.
v VTAM start options.
OS/390 eNetwork Communications Server: SNA
Use this book in conjunction with the OS/390 Operation (SC31-8567). This book serves as a
eNetwork Communications Server: SNA Resource reference for programmers and operators requiring
Definition Reference. detailed information about specific operator
commands. The information includes:
OS/390 eNetwork Communications Server: SNA v VTAM commands and start options
Resource Definition Reference (SC31-8565). This
book describes each VTAM definition statement, v Logon manager commands
start option, and macroinstruction for user tables. v DISPLAY output examples (messages received)
It also describes NCP definition statements that v VSCS commands.
affect VTAM. The information includes:
v IBM-supplied default tables (logon mode and OS/390 eNetwork Communications Server: SNA
USS) Operation Quick Reference (SX75-0121). This
v Major node definitions book contains essential information about VTAM
operator commands.
v User-defined tables and filters
v VTAM start options. OS/390 eNetwork Communications Server: High
If you are unfamiliar with the major concepts Speed Access Services User’s Guide
involved in implementing a SNA network, use this (GC31-8676). This book is for end users and
system administrators who want to use

496 SNA Operation

 Bibliography
applications using a High Speed Access Services writing your own client or server application. You
connection available in CS for OS/390. can also use this book to adapt your existing
applications to communicate with each other using
Customization sockets over TCP/IP.

OS/390 eNetwork Communications Server: SNA OS/390 eNetwork Communications Server: IP

Customization (LY43-0110). This book enables CICS Sockets Guide (SC31-8518). This book is
you to customize VTAM, and includes: for people who want to set up, write application
programs for, and diagnose problems with the
v Communication network management (CNM)
socket interface for CICS using TCP/IP for MVS.
routing table
v Logon-interpret routine requirements OS/390 eNetwork Communications Server: IP IMS
v Logon manager installation-wide exit routine for Sockets Guide (SC31-8519). This book is for
the CLU search exit programmers who want application programs that
v TSO/VTAM installation-wide exit routines use the IMS TCP/IP application development
services provided by IBM TCP/IP for MVS.
v VTAM installation-wide exit routines:
– Command verification exit (ISTCMMND) OS/390 eNetwork Communications Server: IP
– Configuration services XID exit (ISTEXCCS) Programmer’s Reference (SC31-8515). This book
with description of IBM-supplied default exit describes the syntax and semantics of a set of
– Directory services management exit high-level application functions that you can use to
(ISTEXCDM) program your own applications in a TCP/IP
environment. These functions provide support for
– Generic resource resolution exit application facilities, such as user authentication,
(ISTEXCGR) distributed databases, distributed processing,
– Performance monitor exit (ISTEXCPM) network management, and device sharing.
– SDDLU exit (ISTEXCSD) with description of Familiarity with the MVS operating system, TCP/IP
IBM-supplied default exit protocols, and IBM Time Sharing Option (TSO) is
– Session accounting exit (ISTAUCAG) recommended.
– Session authorization exit (ISTAUCAT) OS/390 eNetwork Communications Server: SNA
– Session management exit (ISTEXCAA) with Programming (SC31-8573). This book describes
example how to use VTAM macroinstructions to send data
– TPRINT processing exit (ISTRAEUE) to and receive data from (1) a terminal in either
– USERVAR exit (ISTEXCUV) with description the same or a different domain, or (2) another
of IBM-supplied default exit application program in either the same or a
different domain. The information includes:
– Virtual route pacing window size calculation
exit (ISTPUCWC) v API concepts
– Virtual route selection exit (ISTEXCVR). – Cryptography
– RUs and exchanges
OS/390 eNetwork Communications Server: IP – Session establishment and termination
Network Print Facility (SC31-8522). This book is v BIND area format
for system programmers and network
administrators who need to prepare their network v Communication Network Management Interface
to route VTAM, JES2, or JES3 printer output to v Dictionary of VTAM macroinstructions
remote printers using TCP/IP. v OPEN or CLOSE errors
v Operating system differences
Writing Application Programs v Program Operator Coding requirements
OS/390 eNetwork Communications Server: IP API v RAPI DSECTs and control block mappings
Guide (SC31-8516). This book describes the (ACB, ADSP, BLENT, CV29, EXLST, MTS, NIB,
syntax and semantics of program source code NIB DEVCHAR, NIB PROC, RH, RPL,
necessary to write your own application RPL RTNCD=FDB2=FDBK=DSECT)
programming interface (API) into TCP/IP. You can v RAPI global variables
use this interface as the communication base for v Vector lists

Bibliography 497
Bibliography
v RPL-based macroinstructions v Creating and deleting buffer pools
v RPL RTNCD,FDB2 codes v Obtaining and freeing buffers
v User exit routines. v Return codes and reason codes
v DSECTs
OS/390 eNetwork Communications Server: SNA
Programmers LU 6.2 Guide (SC31-8581). This OS/390 eNetwork Communications Server: CMIP
book describes how to use the VTAM LU 6.2 Services and Topology Agent Guide (SC31-8576).
application programming interface for host This book describes the Common Management
application programs. This book applies to Information Protocol (CMIP) programming
programs that use only LU 6.2 sessions or that interface for application programmers to use in
use LU 6.2 sessions along with other session coding CMIP application programs. The book
types. (Only LU 6.2 sessions are covered in this provides guide and reference information about
book.) The information includes: CMIP services and the VTAM topology agent and
v VTAM’s implementation of the LU 6.2 includes the following topics:
architecture v Management information base (MIB) API
v Design considerations for LU 6.2 application functions
programs v CMIP message strings
v Negotiating session limits with partner LUs v Special CMIP message strings
v BIND image and response v Read queue exit routine
v Allocating and deallocating conversations v Sample CMIP application program
v FMH-5 and PIP data v VTAM resources as CMIP objects
v Conversation states v Naming conventions for objects
v Sending and receiving data v VTAM resources and OSI states
v Using high performance data transfer (HPDT) v Attributes to object cross-reference
v Session- and conversation-level security and v ASN.1 syntax for CMIP messages
data encryption
v GDMO table format
v Register usage
v ACYAPHDH header file.
v Sync point services
v LU 6.2 global variables Diagnosis
v Vector lists
v Sense codes for FMH-7 and UNBIND OS/390 eNetwork Communications Server: IP
v RCPRI,RCSEC codes
Diagnosis (SC31-8521). This book explains how to
diagnose TCP/IP problems and how to determine
v User exit routines. whether a specific problem is in the TCP/IP
product code. It explains how to gather information
OS/390 eNetwork Communications Server: SNA for and describe problems to the IBM Software
Programmers LU 6.2 Reference (SC31-8568). Support Center.
This book provides reference material for the
VTAM LU 6.2 programming interface for host OS/390 eNetwork Communications Server: SNA
application programs. The information includes: Diagnosis (LY43-0079). This book helps you
v APPCCMD macroinstructions identify a VTAM problem, classify it, and collect
v Primary and secondary return codes (RCPRI, information about it before you call the IBM
RCSEC) Support Center. The information collected includes
traces, dumps, and other problem documentation.
v DSECTs
Volume 1 includes information on the following:
v Examples of using VTAM’s LU 6.2 API
v Command syntax for running traces and
v Register usage collecting and analyzing dumps
OS/390 eNetwork Communications Server: CSM v Procedures for collecting documentation
Guide (SC31-8575). This book describes how (VTAM, TSO)
applications use the communications storage v VIT analysis tool
manager. The information includes: v Channel programs

498 SNA Operation

 Bibliography
v Flow diagrams – Message routing and suppression including
v Procedures for locating buffer pools descriptor codes, routing codes, and
suppression levels for ELM, IKT, IST, and
v CPCB operation codes
ISU messages
v Storage and control block ID codes
– Message text and description formats
v Offset names and locations for VTAM buffer
– Message text of MSGLVL option messages
pools.
including general information on the
MSGLVL option
Volume 2 includes information on the following:
– Message text of all VTAM network operator
v VIT entries
messages including variable field lengths
v VTAM internal trace
v FFST dumps and probes OS/390 eNetwork Communications Server: IP
Messages Volume 1 (SC31-8517). This volume
OS/390 eNetwork Communications Server: Data contains TCP/IP messages beginning with EZA.
Areas Volume 1 (LY43-0111). This book describes
VTAM data areas and can be used to read a OS/390 eNetwork Communications Server: IP
VTAM dump. It is intended for IBM programming Messages Volume 2 (SC31-8570). This volume
service representatives and customer personnel contains TCP/IP messages beginning with EZB.
who are diagnosing problems with VTAM.
OS/390 eNetwork Communications Server: IP
OS/390 eNetwork Communications Server: Data Messages Volume 3 (SC31-8674). This volume
Areas Volume 2 (LY43-0112). This book describes contains TCP/IP messages beginning with EZY,
VTAM data areas and can be used to read a EZZ, and SNM.
VTAM dump. It is intended for IBM programming
service representatives and customer personnel OS/390 eNetwork Communications Server: IP and
who are diagnosing problems with VTAM. SNA Codes (SC31-8571). This book describes
codes and other information that display in CS/390
Messages and Codes messages:
v Sense codes including VTAM sense code hints,
OS/390 eNetwork Communications Server: SNA SNA sense field values for RPL-based
Messages (SC31-8569). This book describes the macroinstructions, and 3270 SNA and non-SNA
following types of messages and other associated device sense fields
information: v Return codes for macroinstructions including
v Messages: ACB OPEN and CLOSE macroinstruction error
– ELM messages for logon manager fields, RTNCD-FDB2 return code combinations,
and LU 6.2 RCPRI-RCSEC return codes
– IKT messages for TSO/VTAM
v Data link control (DLC) status codes
– IST messages for VTAM network operators
v Status codes including resource status and
– ISU messages for sockets-over-SNA
session state codes
– IVT messages for the communications
v Wait state event codes and IDs
storage manager
v Abend codes
– IUT messages
v ATM network-generated cause and diagnostic
– USS messages
codes
v Other information that displays in VTAM
messages: APPC Application Suite
– Command and RU types in VTAM messages
– Node and ID types in VTAM messages OS/390 eNetwork Communications Server: APPC
v Supplemental message-related information: Application Suite User’s Guide (GC31-8619). This
book documents the end-user interface (concepts,
– Message additions, deletions, and changes
commands, and messages) for the AFTP, ANAME,
– Message flooding prevention and APING facilities of the APPC application suite.
– Message groups and subgroups

Bibliography 499
Bibliography
Although its primary audience is the end user, Networking Blueprint Executive Overview
administrators and application programmers may (GC31-7057)
also find it useful.
Multiprotocol Transport Networking: Technical
OS/390 eNetwork Communications Server: APPC Overview (GC31-7073)
Application Suite Administration (SC31-8620). This
book contains the information that administrators Multiprotocol Transport Networking: Formats
need to configure the APPC application suite and (GC31-7074)
to manage the APING, ANAME, AFTP, and A3270
servers.
OS/390 Publications
OS/390 eNetwork Communications Server: APPC
Application Suite Programming (SC31-8621). This For information on OS/390 and other products,
book provides the information application refer to OS/390 Information Roadmap
programmers need to add the functions of the (GC28-1727-03).
AFTP and ANAME APIs to their application
programs.

Multiprotocol Transport
Networking (MPTN) Architecture
Publications
Following are selected publications for MPTN:

500 SNA Operation

Index
A ASIRFMSG start option (continued)
modifying 385
ACT operand
setting 392
VARY ACQ command 408
ASLTAB (associated LU table)
VARY ANS command 439
displaying 201
VARY LOGON command 460
modifying resource associations 352
ACTION operand
ASRCVLM operand
MODIFY ALSLIST command 252
MODIFY RESOURCE command 336
MODIFY DUMP command 285
associated LU table (ASLTAB)
MODIFY LOAD command 307
displaying 201
MODIFY RESOURCE command 336
modifying resource associations 352
ACTIVATE operand
ASYDE start option
MODIFY DR command 280
displaying 235
activating resources 414
setting 392
adaptive data compression 264
AUTHLEN start option
ADDR operand
displaying 235
DISPLAY NCPSTOR command 143
modifying 385
MODIFY DR command 280
setting 392
ADDRESS operand
automatic activation of link stations 430, 433
DISPLAY VTAMSTOR command 244
automatic logon relationship
adjacent control point, displaying 20, 98
deleting 462
adjacent link station list, modifying 251
effect on session termination 471
adjacent nodes, displaying 215
establishing or changing 459
adjacent SSCP tables, displaying 24
AUTORTRY start option
ADJLIST operand
displaying 235
DISPLAY ADJSSCPS command 24
modifying 385
MODIFY RESOURCE command 336
setting 392
ADJSUB operand
AUTOSES operand
DISPLAY PATHTAB command 151
MODIFY DEFINE command 272
ALSNAME operand
AUTOTI start option
MODIFY NOTRACE command 321
displaying 235
MODIFY TRACE command 366
modifying 385
ALSREQ start option
setting 392
displaying 235
setting 392
AMOUNT operand
MODIFY TRACE command 367
B
ANS operand BFRNUM operand
VARY ACT command 421 MODIFY TRACE command 367
VARY ANS command 439 BN start option
APPC operand displaying 235
MODIFY USERVAR command 382 modifying 385
APPL operand setting 392
DISPLAY STORUSE command 196 BNDYN start option
application jobs displaying 235
displaying storage usage for 196 modifying 385
application programs setting 392
displaying 35 BNORD start option
displaying APPL major node 99 displaying 235
displaying storage usage for 196 modifying 385
APPNCOS operand setting 392
DISPLAY TOPO command 215 BSCMDRS start option
APPNCOS start option displaying 235
displaying 235 modifying 385
modifying 385 setting 392
setting 392 BSCTMOUT start option
ASIRFMSG start option displaying 235
displaying 235 setting 392

© Copyright IBM Corp. 1984, 1998 501

buffer contents trace checkpoint
displaying status of 224 date and time, displaying 216
starting 379 taking 257
stopping 328 CINDXSIZ start option
BUFFER operand displaying 235
DISPLAY BFRUSE command 41 setting 392
buffer pool start options CKEY operand
displaying 41 MODIFY SECURITY command 341
setting 392 class of service (COS) table
buffer pools, displaying 41 displaying contents of 201
buffer use (SMS) trace displaying name of 70
displaying status of 225 modifying resource associations 352
starting 380 clusters, displaying 60
stopping 329 CMIP services directory definition file
modifying 352
CMIPDDF
C modifying 352
CACHETI start option CMPAPPLI operand
displaying 235 MODIFY COMPRESS command 264
setting 392 CMPAPPLO operand
CDINIT requests, pending, recovery from 299 MODIFY COMPRESS command 265
CDLINK operand CMPMIPS start option
HALT command 248 displaying 235
HALT QUICK command 250 modifying 385
VARY INACT command 451 setting 392
VARY REL command 467 CMPVTAM operand
CDRDYN start option MODIFY COMPRESS command 265
displaying 235 CMPVTAM start option
modifying 385 displaying 235
setting 392 modifying 264, 385
CDRM (cross-domain resource manager) setting 392
displaying 49, 99 CNM (communication network management) trace
modifying ownership of resources 255 displaying status of 224
CDRM operand starting 379
DISPLAY ADJSSCPS command 24 stopping 328
DISPLAY CDRM command 255 CNMTAB start option
CDRSC (cross-domain resource) displaying 235
displaying setting 392
DISPLAY CDRSCS command 54 CNOS (change number of sessions) information
DISPLAY ID command for CDRSC major node displaying 64
99 modifying 260
DISPLAY ID command for individual CDRSCs CNSL operand
110 MODIFY TNSTAT command 355
CDRSC operand COLD start option
DISPLAY ADJSSCPS command 24 displaying 235
CDRSCTI start option setting 392
displaying 235 commands
setting 392 correct and incorrect
CDSERVR start option logon manager 474
displaying 235 VTAM 12
setting 392 fundamentals
CDSREFER start option logon manager 473
displaying 235 VTAM 9
modifying 385 length limitation
setting 392 logon manager 473
CERTIFY operand VTAM 12
MODIFY SECURITY command 341 procedure name
channel-attachment major node, displaying 102 logon manager 473
channel link, displaying 118, 127 VTAM 9
channel link station, displaying 118 syntax diagrams, how to read 12

502 SNA Operation

common service area (CSA) limit CSA24 start option (continued)
modifying 266 modifying 266, 385
communication controller disk contents, displaying 79 setting 392
communication network management (CNM) trace CSALIMIT operand
displaying status of 224 MODIFY CSALIMIT command 266
starting 379 CSALIMIT start option
stopping 328 displaying 235
component ID, VTAM, displaying 235 modifying 266, 385
compression level, data, modifying 264 setting 392
CONFIG start option CSP (communication scanner processor) dumps 285
displaying 235
setting 392
configuration lists 5
D
data compression level, modifying 264
congestion level of node, displaying 216
DATA operand
CONNTYPE start option
MODIFY LL2 command 303
displaying 235
data spaces
modifying 385
displaying storage usage for 196
setting 392
DATEFORM start option
CONSEC operand
displaying 235
DISPLAY APING command 29
setting 392
controlling a VTAM domain
DDRAINL operand
commands involved in 5
MODIFY DEFINE command 272
conversations, displaying 67
deactivating resources 449
CONVSECL operand
DELETE operand
MODIFY CNOS command 261
MODIFY DEFINE command 273
COS (class of service) table
VARY INACT command 451
displaying contents of 201
dependent LU requesters, displaying 81
displaying name of 70
DEST operand
modifying resource associations 352
DISPLAY TOPO command 215
COSNAME operand
MODIFY TOPO command 358
DISPLAY ROUTE command 155
DESTSUB operand
COUNT operand
DISPLAY PATHTAB command 151
MODIFY TRACE command 368
DISPLAY ROUTE command 155
CPCDRSC start option
dial connections
displaying 235
establishing 442
setting 392
setting answer mode 439
CPCP operand
terminating 446
VARY ACT command 421
terminating a manual operation 458
VARY DIAL command 442
dial-out paths
CPCP start option
displaying 149
displaying 235
making available or unavailable 464
modifying 385
directory information
setting 392
displaying 75
CPNAME operand
modifying 275
MODIFY DIRECTRY command 276
saving 257
cross-domain resource (CDRSC)
DIRSIZE start option
displaying
displaying 235
DISPLAY CDRSCS command 54
modifying 385
DISPLAY ID command for CDRSC major node
setting 392
99
DIRTIME start option
DISPLAY ID command for individual CDRSCs
displaying 235
110
modifying 385
cross-domain resource manager (CDRM)
setting 392
displaying 49, 99
DISCNTIM operand
modifying ownership of resources 255
MODIFY DEFAULTS command 270
cross-reference for DISPLAY commands 483
MODIFY RESOURCE command 336
cryptography level, modifying 290
DISCNTIM start option
CSA (common service area) limit
displaying 235
modifying 266
modifying 385
CSA24 start option
setting 392
displaying 235
DISPLAY ADJCLUST command 18

Index 503
DISPLAY ADJCP command 20 DLRTCB start option
DISPLAY ADJSSCPS command 23 displaying 235
DISPLAY APING command 29 setting 392
DISPLAY APINGDTP command 34 DLU operand
DISPLAY APPLS command 35 DISPLAY SRCHINFO command 181
DISPLAY APPNTOSA command 40 DR (dynamic reconfiguration)
DISPLAY BFRUSE command 41 MODIFY DR command 278
DISPLAY BNCOSMAP command 47 VARY ACT command 433
DISPLAY CDRMS command 49 VARY DRDS command 443
DISPLAY CDRSCS command 53 DRAINL operand
DISPLAY CLSTRS command 59 MODIFY CNOS command 262
DISPLAY CNOS command 64 DRAINR operand
DISPLAY command cross-reference 483 MODIFY CNOS command 262
DISPLAY CONVID command 67 DRESPL operand
DISPLAY COS command 70 MODIFY DEFINE command 273
DISPLAY CSM command 72 DSPLYDEF start option
DISPLAY DIRECTRY command 75 displaying 235
DISPLAY DISK command 79 modifying 385
DISPLAY DLURS command 81 setting 392
DISPLAY EXIT command 82 DSPLYMAX start option
DISPLAY GROUPS command 85 displaying 235
DISPLAY ID command 89 setting 392
DISPLAY LINES command 126 DSPLYWLD start option
DISPLAY LMTBL command 131 displaying 235
DISPLAY LUGROUPS command 134 modifying 385
DISPLAY MAJNODES command 138 setting 392
DISPLAY MODELS command 140 DSPNAME operand
DISPLAY NCPSTOR command 143 DISPLAY STORUSE command 196
DISPLAY NETSRVR command 145 DUMP operand
DISPLAY PATHS command 149 HALT CANCEL command 249
DISPLAY PATHTAB command DUMPDS operand
description 151 MODIFY DUMP command 286
versus DISPLAY ROUTE command 151 DUMPLOAD operand
DISPLAY PENDING command 153 VARY ACT command 421
DISPLAY ROUTE command dumps
description 155 displaying 79
versus DISPLAY PATHTAB command 151 taking
DISPLAY RSCLIST command 160 CSP 288
DISPLAY SATOAPPN command 169 MOSS 288
DISPLAY SESSIONS command 170 NCP 288
DISPLAY SNSFILTR command 178 DUMPSTA operand
DISPLAY SRCHINFO command 179 MODIFY DUMP command 286
DISPLAY STATIONS command 186 VARY ACT command 422
DISPLAY STATS command 190 DWACT operand
DISPLAY STORUSE command 195 VARY ACT command 423
DISPLAY TABLE command 201 DYNADJCP start option
DISPLAY TERMS command 205 displaying 235
DISPLAY TGPS command 210 setting 392
DISPLAY TOPO command 213 dynamic reconfiguration (DR)
DISPLAY TRACES command 221 MODIFY DR command 278
DISPLAY TRL command 229 VARY ACT command 433
DISPLAY TSOUSER command 232 VARY DRDS command 443
DISPLAY USERVAR command 233 dynamic resources, warning about deactivating 453
DISPLAY VTAMOPTS command 235 dynamic switched PUs and LUs, displaying model
DISPLAY VTAMSTOR command 243 definitions for 140
DLIMITS operand DYNASSCP start option
MODIFY DEFINE command 273 displaying 235
DLOGMOD operand setting 392
MODIFY DEFAULTS command 270 DYNDLGMD start option
MODIFY RESOURCE command 336 displaying 235
DLOGMOD value, predefined, modifying 269, 335 modifying 385

504 SNA Operation

DYNDLGMD start option (continued) external communication adapter (XCA) major node
setting 392 displaying 102
DYNLU start option
displaying 235
setting 392 F
DYNMODTB start option FINAL operand
displaying 235 VARY INACT command 451
modifying 385 VARY REL command 468
setting 392 FIXED operand
MODIFY CSM command 268
FLDTAB (message-flooding prevention table)
E displaying 201
ECHO operand modifying resource associations 352
DISPLAY APING command 29 FLDTAB start option
ECSA operand displaying 235
MODIFY CSM command 268 setting 392
ENCR operand FORMAT operand
MODIFY ENCR command 290 DISPLAY VTAMOPTS command 236
MODIFY SECURITY command 341 frame relay switching equipment set (FRSESET)
ENCRPREF start option adding PUs
displaying 235 VARY ACT command 436
modifying 385 deleting PUs
setting 392 MODIFY DR command 279
encryption facility 290 VARY ACT command 436
ENCRYPTN start option VARY DRDS command 443
displaying 235 displaying 91
modifying 385 FRAMES operand
setting 392 MODIFY TRACE command 368
end nodes, displaying 216 FROM operand
END operand MODIFY DR command 281
VARY INOP command 458 FROMCP operand
ENHADDR start option DISPLAY SRCHINFO command 181
displaying 235 FROMSSCP operand
setting 392 DISPLAY SRCHINFO command 182
ENTERPRISE EXTENDER FRSESET (frame relay switching equipment set)
DISPLAY ID command 103, 123 adding PUs
ER (explicit route) VARY ACT command 436
displaying status of 151, 155 deleting PUs
ER operand MODIFY DR command 279
DISPLAY ROUTE command 155 VARY ACT command 436
ESIRFMSG start option VARY DRDS command 443
displaying 235 displaying 91
modifying 385 FSIRFMSG start option
setting 392 displaying 235
ETIME operand modifying 385
DISPLAY CONVID command 67 setting 392
EXCLUDE operand FUNCTION operand
DISPLAY RSCLIST command 161 DISPLAY VTAMOPTS command 236
EXIT (SME buffer) trace MODIFY DIRECTRY command 276
displaying status of 224 MODIFY TOPO command 358
starting 379
stopping 328
exit routine information, displaying 82 G
exit routines generalized PIU trace (GPT)
activating 293 displaying status of 224
deactivating 293 starting 379
displaying 82 stopping 328
replacing 293 GID operand
explicit route (ER) VARY PATH command 464
displaying status of 151, 155 GPT (generalized PIU trace)
external CDRM, displaying 51, 112 displaying status of 224

Index 505
GPT (generalized PIU trace) (continued) ID operand (continued)
starting 379 DISPLAY CDRMS command 50
stopping 328 DISPLAY CDRSCS command 54
GROUP operand DISPLAY CLSTRS command 60
DISPLAY LUGROUPS command 135 DISPLAY CNOS command 64
GWSSCP start option DISPLAY CONVID command 67
displaying 235 DISPLAY COS command 70
setting 392 DISPLAY DIRECTRY command 75
DISPLAY DISK command 79
DISPLAY EXIT command 82
H DISPLAY GROUPS command 86
HALT CANCEL command 249 DISPLAY ID command 91
HALT command 248 DISPLAY LINES command 127
HALT QUICK command 250 DISPLAY LMTBL command 131
halting VTAM DISPLAY LUGROUPS command 135
HALT CANCEL command 249 DISPLAY MODELS command 140
HALT command 248 DISPLAY NCPSTOR command 143
HALT QUICK command 250 DISPLAY PATHS command 149
hardware errors, detecting DISPLAY PENDING command 153
MODIFY IMR command 296 DISPLAY RSCLIST command 161
MODIFY LL2 command 302 DISPLAY STATIONS command 187
HNTSIZE start option DISPLAY TABLE command 201
displaying 235 DISPLAY TERMS command 206
setting 392 DISPLAY TGPS command 210
host CDRM, displaying 112 DISPLAY TOPO command 215
host physical unit DISPLAY TRACES command 222
displaying 101 DISPLAY TSOUSER command 232
tracing 371 DISPLAY USERVAR command 233
HOSTPU start option MODIFY ALSLIST command 253
displaying 235 MODIFY CDRM command 256
setting 392 MODIFY CNOS command 262
HOSTSA start option MODIFY COMPRESS command 265
displaying 235 MODIFY DEFAULTS command 270
setting 392 MODIFY DEFINE command 274
HOTIOTRM start option MODIFY DIRECTRY command 277
displaying 235 MODIFY DR command 281
modifying 385 MODIFY DUMP command 287
setting 392 MODIFY ENCR command 291
HPR operand MODIFY EXIT command 293
VARY ACT command 423 MODIFY IMR command 296
HPR start option MODIFY INFO command 476
displaying 235 MODIFY LINEDEF command 301
setting 392 MODIFY LL2 command 303
HPRNCPBF start option MODIFY LOAD command 310
displaying 235 MODIFY MINLINK command 479
modifying 385 MODIFY NEGPOLL command 314
setting 392 MODIFY NOTRACE command 321
HPRPST start option MODIFY POLL command 330
displaying 235 MODIFY PROFILES command 332
modifying 385 MODIFY RESOURCE command 337
setting 392 MODIFY RTP command 339
HSRTSIZE start option MODIFY SECURITY command 341
displaying 235 MODIFY SESSION command 343
setting 392 MODIFY TABLE command 349
MODIFY TGP command 353
MODIFY TOPO command 359
I MODIFY TRACE command 368
ID operand MODIFY USERVAR command 383
DISPLAY ADJCP command 20 VARY ACQ command 409
DISPLAY APING command 30 VARY ACT command 423
DISPLAY APPLS command 36 VARY ANS command 439

506 SNA Operation

ID operand (continued) IOPURGE start option
VARY DIAL command 442 displaying 235
VARY DRDS command 445 modifying 299, 385
VARY HANGUP command 446 setting 392
VARY INACT command 452 IP ADDRESS 90
VARY INOP command 458 IPADDR start option 392
VARY LOGON command 460 IPL (initial program load)
VARY NOLOGON command 462 scheduling for communication controller 306
VARY PATH command 464 IPLTIME operand
VARY REL command 468 MODIFY LOAD command 310
IDTYPE operand IRNSTRGE start option
DISPLAY CLSTRS command 60 displaying 235
DISPLAY ID command 92 setting 392
DISPLAY RSCLIST command 162 ISTCOSDF start option
DISPLAY TRACES command 224 displaying 235
MODIFY NOTRACE command 322 modifying 385
MODIFY TRACE command 373 setting 392
VARY ACT command 426 ITER operand
VARY INACT command 453 DISPLAY APING command 30
independent logical unit
deactivating 451
displaying J
as CDRSC 54, 111 JOBNAME operand
under PU that provides boundary function 96 DISPLAY STORUSE command 196
dynamic reconfiguration 282
modifying
entry in adjacent link station list 251 L
tracing 372 LENGTH operand
INITDB start option DISPLAY NCPSTOR command 143
displaying 235 DISPLAY VTAMSTOR command 244
setting 392 LIMINTCP start option
initial program load (IPL) displaying 235
scheduling for communication controller 306 modifying 385
INOPDUMP start option setting 392
displaying 235 LIMITS operand
modifying 385 MODIFY CNOS command 262
setting 392 line errors, recording 296
input/output problem determination (IOPD) facility line groups, displaying 85, 114
time-out interval, changing 298 LINE operand
input/output trace MODIFY NOTRACE command 322
displaying status of 224 MODIFY TRACE command 373
starting 379 line trace, NCP
stopping 328 displaying status of 224
INSTANCE operand starting 380
MODIFY APINGDTP command 254 stopping 328
intensive mode recording (IMR) 296 lines, displaying 127
interchange nodes, displaying 216 link level 2 test, starting and stopping 302
IOINT operand link stations
MODIFY IOPD command 298 cross-subarea
IOINT start option displaying 186
displaying 235 recording line errors for 296
modifying 298, 385 links
setting 392 logon manager, changing minimum number of 479
IOMSGLIM start option LIST operand
displaying 235 DISPLAY SESSIONS command 171
modifying 385 DISPLAY SRCHINFO command 182
setting 392 DISPLAY STORUSE command 196
IOPD (input/output problem determination) facility DISPLAY TOPO command 215
time-out interval, changing 298 LIST start option
IOPURGE operand displaying 235
MODIFY IOPURGE command 299 setting 392

Index 507
LISTBKUP start option LU2 operand (continued)
setting 392 DISPLAY SRCHINFO command 182
load module VARY TERM command 470
displaying 79 LUGROUP major nodes, displaying 135
storing, replacing, purging, or renaming 306 LUNAME operand
LOAD operand DISPLAY CNOS command 64
VARY ACT command 426 DISPLAY CONVID command 68
LOADFROM operand DISPLAY LMTBL command 131
VARY ACT command 427 MODIFY CNOS command 263
LOADMOD operand MODIFY DEFINE command 274
MODIFY LOAD command 311
VARY ACQ command 409
VARY ACT command 427 M
LOADSTA operand MAC operand
VARY ACT command 428 MODIFY SECURITY command 342
local non-SNA major node, displaying 101 MACLNTH operand
local SNA major node, displaying 100 MODIFY SECURITY command 342
logical unit (LU) MACTYPE operand
displaying 121 MODIFY SECURITY command 342
LOGMODE operand MAINTLVL start option
DISPLAY APING command 30 displaying 235
DISPLAY CNOS command 64 setting 392
DISPLAY CONVID command 67 MAJNODE operand
MODIFY CNOS command 263 DISPLAY RSCLIST command 164
MODIFY DEFINE command 274 major node, displaying 90, 138
VARY ACT command 428 MAX operand
VARY LOGON command 461 DISPLAY ADJSSCPS command 24
logon interpret table (LOGTAB) DISPLAY APPLS command 36
displaying 201 DISPLAY CDRMS command 50
modifying resource associations 352 DISPLAY CDRSCS command 54
logon manager DISPLAY CLSTRS command 60
commands DISPLAY DIRECTRY command 76
displaying help for 475 DISPLAY EXIT command 83
entering 473 DISPLAY GROUPS command 86
procedure name 473 DISPLAY ID command 94
where to enter 473 DISPLAY LINES command 127
displaying resources 476 DISPLAY LUGROUPS command 135
links, modifying minimum number of 479 DISPLAY MAJNODES command 138
purpose 473 DISPLAY PATHTAB command 151
starting 481 DISPLAY PENDING command 153
stopping 480 DISPLAY RSCLIST command 164
logon mode table (MODETAB) DISPLAY SESSIONS command 172
displaying 201 DISPLAY SRCHINFO command 182
modifying resource associations 352 DISPLAY STATIONS command 187
LOGON operand DISPLAY STATS command 190
VARY ACT command 429 DISPLAY STORUSE command 197
VARY LOGON command 461 DISPLAY TABLE command 201
LOGTAB (logon interpret table) DISPLAY TERMS command 206
displaying 201 DISPLAY TGPS command 210
modifying resource associations 352 DISPLAY TRL command 230
LU (logical unit) DISPLAY USERVAR command 233
displaying 121 MAXLOCAT start option
LU-mode table displaying 235
displaying 131 modifying 385
modifying entries in 272 setting 392
LU1 operand MAXLURU start option
DISPLAY SESSIONS command 171 displaying 235
DISPLAY SRCHINFO command 182 setting 392
VARY TERM command 470 MAXSSCPS start option
LU2 operand displaying 235
DISPLAY SESSIONS command 172 modifying 385

508 SNA Operation

MAXSSCPS start option (continued) MODIFY NOTNSTAT command 315
setting 392 MODIFY NOTRACE command 316
MAXSUBA start option MODIFY POLL command 330
displaying 235 MODIFY PPOLOG command 331
setting 392 MODIFY PROFILES command 332
MDLTAB (model name table) MODIFY QUERY command 333
displaying 201 MODIFY RESOURCE command 334
modifying resource associations 352 MODIFY RTP command 339
MEMBER operand MODIFY SECURITY command 340
MODIFY MEMBER command 478 MODIFY SESSION command 343
message flooding prevention table (FLDTAB) MODIFY STOP command 480
displaying 201 MODIFY SUPP command 344
modifying resource associations 352 MODIFY TABLE command 346
messages MODIFY TGP command 353
including module ID in 313 MODIFY TNSTAT command 355
modifying suppression level 344 MODIFY TOPO command 357
MIHTMOUT start option MODIFY TRACE command 361
displaying 235 MODIFY USERVAR command 381
modifying 385 MODIFY VTAMOPTS command 385
setting 392 MODSRCH operand
MINLINK operand MODIFY RESOURCE command 337
MODIFY MINLINK command 479 module name
minor node, displaying 90 including in messages 313
MODE operand MODULE operand
MODIFY NOTRACE command 323 DISPLAY VTAMSTOR command 244
MODIFY TRACE command 373 MODIFY EXIT command 294
model LU groups, displaying 135 module trace
model name table (MDLTAB) displaying status of 224
displaying 201 starting 380
modifying resource associations 352 stopping 328
model resources, displaying 140 MOSS (maintenance operator subsystem) dumps 285
MODETAB (logon mode table) MSGLEVEL start option
displaying 201 displaying 235
modifying resource associations 352 modifying 385
MODIFY ALSLIST command 251 setting 392
MODIFY APINGDTP command 254 MSGMOD operand
MODIFY CDRM command 255 MODIFY MSGMOD command 313
MODIFY CHKPT command 257 MSGMOD start option
MODIFY CNOS command 259 displaying 235
MODIFY COMPRESS command 264 modifying 313, 385
MODIFY CSALIMIT command 266 setting 392
MODIFY CSM command 268 mutually exclusive operand table 417
MODIFY DEFAULTS command 269 MXSAWBUF start option
MODIFY DEFINE command 271 displaying 235
MODIFY DIRECTRY command 275 setting 392
MODIFY DR command 278 MXSSCPRU start option
MODIFY DUMP command 283 displaying 235
MODIFY ENCR command 290 setting 392
MODIFY EXIT command 292 MXSUBNUM start option
MODIFY HELP command 475 displaying 235
MODIFY IMR command 296 setting 392
MODIFY INFO command 476
MODIFY IOPD command 298
MODIFY IOPURGE command 299 N
MODIFY LINEDEF command 301 NBRMODE operand
MODIFY LL2 command 302 MODIFY CNOS command 263
MODIFY LOAD command 305 NCP (Network Control Program)
MODIFY MEMBER command 478 acquiring 408
MODIFY MINLINK command 479 dumping 285
MODIFY MSGMOD command 313 dynamic reconfiguration 278, 443
MODIFY NEGPOLL command 314

Index 509
NCP (Network Control Program) (continued) NMVTLOG start option (continued)
line trace setting 392
displaying status of 224 NNSPREF option
loading 306 DISPLAY VTAMOPTS command 240
major node, displaying 101 MODIFY VTAMOPTS command 385
releasing 466 START command 392
storage, displaying 143 node, displaying 90
NCPBUFSZ start option node congestion, displaying 216
displaying 235 node type, displaying 216, 235
setting 392 NODELST start option
negative polling limit, modifying 314 displaying 235
NEGPOLL operand setting 392
MODIFY NEGPOLL command 314 NODETYPE start option
NETADDR operand displaying 235
DISPLAY VTAMSTOR command 244 setting 392
NETID operand NOLOGON operand
DISPLAY ADJCLUST command 18 VARY NOLOGON command 463
DISPLAY ADJSSCPS command 25 NOPROMPT start option
DISPLAY BNCOSMAP command 47 setting 392
DISPLAY CDRSCS command 54 Notices 491
DISPLAY COS command 70 NOTIFY operand
DISPLAY ID command 94 MODIFY LOAD command 311
DISPLAY ROUTE command 156 VARY TERM command 470
DISPLAY VTAMSTOR command 244 NOTNSTAT start option
MODIFY TABLE command 349 displaying 235
NETID start option setting 392
displaying 235 NOTRACE start option
setting 392 setting 392
NETSRVR operand NQNMODE start option
MODIFY DIRECTRY command 277 displaying 235
network configuration modifying 385
logon manager, modifying 478 setting 392
Network Control Program (NCP) NSRTSIZE start option
acquiring 408 displaying 235
dumping 285 setting 392
dynamic reconfiguration 278, 443 NTRANS operand
line trace MODIFY LL2 command 304
displaying status of 224 NUM operand
loading 306 DISPLAY STATS command 191
major node, displaying 101 DISPLAY STORUSE command 197
releasing 466 NUMTREES start option
storage, displaying 143 displaying 235
network controller (3710) line trace modifying 385
displaying status of 224 setting 392
starting 380
stopping 328
network node server list, displaying 145 O
network node servers, displaying 145, 216 OLDALS operand
network nodes, displaying 216 MODIFY ALSLIST command 253
NEWALS operand OLDTAB operand
MODIFY ALSLIST command 253 MODIFY TABLE command 349
NEWNAME operand OLU operand
MODIFY LOAD command 311 DISPLAY SRCHINFO command 183
NEWPATH operand OPTION operand
VARY ACT command 429 DISPLAY VTAMOPTS command 239
NEWTAB operand MODIFY CSALIMIT command 267
MODIFY TABLE command 349 MODIFY DUMP command 287
NFRAMES operand MODIFY EXIT command 295
MODIFY LL2 command 303 MODIFY IMR command 297
NMVTLOG start option MODIFY LL2 command 304
displaying 235 MODIFY NOTRACE command 323

510 SNA Operation

OPTION operand (continued) physical unit (PU) (continued)
MODIFY TABLE command 350 switched (continued)
MODIFY TRACE command 373 terminating switched connection for 446
MODIFY USERVAR command 383 PID operand
ORIG operand VARY PATH command 465
DISPLAY TOPO command 216 PIUMAXDS start option
MODIFY TOPO command 359 displaying 235
ORIGIN operand modifying 385
DISPLAY ROUTE command 156 setting 392
MODIFY TABLE command 352 PLU operand
OSIEVENT start option DISPLAY SESSIONS command 172
displaying 235 VARY TERM command 470
modifying 385 PLUALMSG start option
setting 392 displaying 235
OSIMGMT start option modifying 385
displaying 235 setting 392
modifying 385 POLL operand
setting 392 MODIFY POLL command 330
OSITOPO start option polling
displaying 235 modifying negative response limit 314
modifying 385 polling delay, modifying 330
setting 392 POOL operand
OSRTSIZE start option DISPLAY STORUSE command 197
displaying 235 POOLTYPE operand
setting 392 DISPLAY STORUSE command 197
OWNER operand PPO (primary program operator)
DISPLAY CLSTRS command 61 logging commands and messages 331
DISPLAY LINES command 127 PPOLOG operand
VARY ACQ command 409 MODIFY PPOLOG command 331
VARY REL command 468 PPOLOG start option
OWNERID operand displaying 235
DISPLAY CSM command 72 modifying 385
ownership of resources, modifying 275 setting 392
primary program operator (PPO)
P logging commands and messages 331
profiles
PARMS operand
RACF, updating 332
MODIFY EXIT command 295
transmission group
PASSWORD operand
displaying 210
DISPLAY APING command 30
modifying 353
PATH operand
PROMPT start option
VARY PATH command 464
setting 392
paths, dial-out
PSRETRY start option
displaying 149
displaying 235
making available or unavailable 464
modifying 385
PDTRCBUF start option
setting 392
displaying 235
PSSTRACE start option
modifying 385
displaying 235
setting 392
setting 392
PEND operand
PU (physical unit)
MODIFY INFO command 476
acquiring 408
pending operations, time-out interval for 298
displaying 118
pending requests, time-out interval for 299
releasing 466
pending state, displaying resources in 153
switched
physical unit (PU)
displaying dial-out path information for 149
acquiring 408
establishing switched connection for 442
displaying 118
making dial-out path available for 464
releasing 466
terminating switched connection for 446
switched
PU operand
displaying dial-out path information for 149
MODIFY NOTRACE command 327
establishing switched connection for 442
MODIFY TRACE command 377
making dial-out path available for 464

Index 511
PUSUB operand scanner interface trace (SIT)
VARY ACQ command 409 displaying status of 224
starting 380
stopping 329
R SCOPE operand
RACF (Resource Access Control Facility) DISPLAY ADJCLUST command 18
profiles, updating 332 DISPLAY ADJCP command 20
RECLIM operand DISPLAY ADJSSCPS command 25
MODIFY IMR command 297 DISPLAY APPLS command 36
REGISTER operand DISPLAY BNCOSMAP command 47
MODIFY RESOURCE command 337 DISPLAY CDRMS command 50
resource DISPLAY CDRSCS command 55
configuration list 5 DISPLAY CLSTRS command 61
Resource Access Control Facility (RACF) DISPLAY DIRECTRY command 76
profiles, updating 332 DISPLAY GROUPS command 86
RESOURCE operand DISPLAY ID command 94
DISPLAY VTAMSTOR command 244 DISPLAY LINES command 128
resource state (STATE) trace DISPLAY LMTBL command 132
displaying status of 225 DISPLAY LUGROUPS command 136
starting 380 DISPLAY MODELS command 140
stopping 329 DISPLAY NETSRVR command 145
RESP operand DISPLAY RSCLIST command 164
MODIFY CNOS command 263 DISPLAY SESSIONS command 172
RESUSAGE start option DISPLAY STATIONS command 187
displaying 235 DISPLAY TABLE command 202
modifying 385 DISPLAY TERMS command 206
setting 392 MODIFY NOTRACE command 327
RMPO operand MODIFY TOPO command 359
MODIFY DUMP command 287 MODIFY TRACE command 378
VARY ACT command 454 VARY ACT command 431
RNAME operand VARY TERM command 470
VARY ACT command 430 SDLCMDRS start option
route addition resistance, displaying 216 displaying 235
ROUTERES start option modifying 385
displaying 235 setting 392
modifying 385 SECLVLCP start option
setting 392 displaying 235
routes setting 392
displaying 151 security profiles, updating 332
testing 155 servers, network node, displaying 145
run-length encoding (data compression) 264 session awareness (SAW) data filter table
modifying resource associations 352
S session limits, modifying
MODIFY CNOS command 260
SAMAP option
MODIFY SESSION command 343
CROSS-REFERENCE table 485, 487, 489
SESSION operand
DISPLAY SAMAP command 168
MODIFY SESSION command 343
SAVE operand
session status, displaying 171
MODIFY TRACE command 377
sessions
SAVEMOD operand
terminating 469
VARY ACT command 431
SID operand
SAVESESS operand
DISPLAY SESSIONS command 173
VARY INACT command 454
DISPLAY SRCHINFO command 183
SAW (session awareness) data filter table
VARY TERM command 471
modifying resource associations 352
SIRFMSG start option
SAWMAXDS start option
displaying 235
displaying 235
modifying 385
setting 392
setting 392
SAWMXQPK start option
SIT (scanner interface trace)
displaying 235
displaying status of 224
modifying 385
starting 380
setting 392

512 SNA Operation

SIT (scanner interface trace) (continued) SSCPID start option
stopping 329 displaying 235
SIZE operand setting 392
DISPLAY APING command 30 SSCPNAME start option
MODIFY TRACE command 378 displaying 235
SLU operand setting 392
DISPLAY SESSIONS command 173 SSCPORD start option
VARY TERM command 471 displaying 235
SLUALMSG start option setting 392
displaying 235 SSDTMOUT start option
modifying 385 displaying 235
setting 392 modifying 385
SME buffer (EXIT) trace setting 392
displaying status of 224 SSEARCH start option
starting 379 displaying 235
stopping 328 modifying 385
SMEAUTH start option setting 392
displaying 235 START command
setting 392 for logon manager 481
SMS (buffer use) trace for VTAM 392
displaying status of 225 start list
starting 380 changing 6
stopping 329 use of 5
SNAPREQ start option start options
displaying 235 displaying 235
setting 392 modifying 390
SNGSESLU operand setting 405
MODIFY CNOS command 263 starting VTAM 405
SNVC start option STATE (resource state) trace
displaying 235 displaying status of 225
modifying 385 starting 380
setting 392 stopping 329
SONLIM start option statistical information, displaying 190
displaying 235 STOP operand
setting 392 MODIFY STOP command 480
SORDER start option stopping VTAM
displaying 235 HALT CANCEL command 249
modifying 385 HALT command 248
setting 392 HALT QUICK command 250
SRCHRED start option storage, NCP, displaying 143
displaying 235 STORAGE operand
modifying 385 DISPLAY NCPSTOR command 143
setting 392 storage pools
SRCLEAR operand displaying storage usage for 196
MODIFY RESOURCE command 338 storage usage information, displaying 196
SRCOUNT operand STRGR start option
MODIFY RESOURCE command 338 displaying 235
SRCOUNT start option setting 392
displaying 235 STRMNPS start option
modifying 385 displaying 235
setting 392 setting 392
SRTIMER operand STRNAME operand
MODIFY RESOURCE command 338 DISPLAY STATS command 191
SRTIMER start option SUPP operand
displaying 235 MODIFY SUPP command 345
modifying 385 SUPP start option
setting 392 displaying 235
SSCPDYN start option modifying 385
displaying 235 setting 392
setting 392 suppression level of messages, modifying 344
switched major node, displaying 102

Index 513
switched PU traces
displaying dial-out path information for 149 displaying status of 222
establishing switched connection for 442 starting and modifying 366
making dial-out path available or unavailable 464 stopping 321
terminating switched connection for 446 TRANSLAT start option
SWNORDER start option displaying 235
displaying 235 setting 392
modifying 385 transmission group (TG) information
setting 392 displaying 214
syntax notation transmission group (TG) profiles
description of 12 displaying 210
modifying 353
transmission group (TG) trace
T displaying status of 224
tables starting 380
changing associations of 347 stopping 329
deleting associations of 347 transport resource list (TRL)
displaying 201 displaying 229
loading 347 TRL (transport resource list)
TCPNAME start option 392 displaying 229
terminals, displaying 205 TRLE operand
TEST operand DISPLAY TRL command 230
DISPLAY ROUTE command 156 truncation of message text 313
TG (transmission group) information TSO user ID
displaying 214 displaying status of 232
TG (transmission group) profiles TSO user trace
displaying 210 displaying status of 225
modifying 353 starting 380
TG (transmission group) trace stopping 329
displaying status of 224 tuning statistics
starting 380 starting the recording of 355
stopping 329 stopping the recording of 315
TGN operand TYPE operand
DISPLAY TOPO command 216 DISPLAY LMTBL command 132
MODIFY TGP command 353 DISPLAY SRCHINFO command 183
MODIFY TOPO command 359 DISPLAY STATS command 191
TGPNAME operand DISPLAY TRACES command 224
MODIFY TGP command 354 DISPLAY VTAMSTOR command 244
TIME operand MODIFY CDRM command 256
MODIFY TNSTAT command 356 MODIFY CHKPT command 257
TNSTAT start option MODIFY DR command 281
displaying 235 MODIFY DUMP command 288
setting 392 MODIFY NOTRACE command 328
TO operand MODIFY TABLE command 352
MODIFY DR command 281 MODIFY TOPO command 359
TOCP operand MODIFY TRACE command 379
DISPLAY SRCHINFO command 183 MODIFY USERVAR command 383
topology database VARY INACT command 454
deleting entries from 358 VARY REL command 468
displaying 214 VARY TERM command 471
saving 257
TOSSCP operand
DISPLAY SRCHINFO command 183 U
TP operand U operand
DISPLAY APING command 30 VARY ACT command 433
TRACE start option ULPID operand
displaying 222 DISPLAY TRL command 230
modifying 366 unformatted system services (USS) table
setting 392 command syntax 16
TRACEPT operand displaying 201
MODIFY TRACE command 379 modifying resource associations 352

514 SNA Operation

UPDATE operand VR (virtual route)
VARY ACT command 433 displaying status of 151, 155
UPDDELAY start option VR operand
displaying 235 DISPLAY ROUTE command 156
modifying 385 VRTG start option
setting 392 displaying 235
USE operand modifying 385
DISPLAY LINES command 129 setting 392
MODIFY LINEDEF command 301 VRTGCPCP operand
USERID operand VARY ACT command 437
DISPLAY APING command 30 VRTGCPCP start option
USERVAR applications displaying 235
defining, changing, or deleting 382 modifying 385
displaying 233 setting 392
USS (unformatted system services) table VTAM
command syntax 16 changing with MODIFY 6
displaying 201 changing with VARY 5
modifying resource associations 352 halting 5
USSTAB start option VTAM internal trace (VIT)
displaying 235 displaying status of 225
setting 392 starting 380
UVEXIT operand stopping 329
MODIFY USERVAR command 383 VTAMEAS start option
displaying 235
setting 392
V
VALUE operand
MODIFY USERVAR command 384 W
VARY ACQ command 407 WARM operand
VARY ACT command 410 VARY ACT command 437
VARY ANS command 439 WARM start option
VARY DIAL command 442 displaying 235
VARY DRDS command 443 setting 392
VARY HANGUP command 446 weight of node, displaying 216
VARY INACT command 447 wildcard network IDs
VARY INOP command 458 DISPLAY ADJCP command 20
VARY LOGON command 459 DISPLAY ID command 92
VARY NOLOGON command 462 MODIFY TGP command 353
VARY PATH command 464 wildcard resource names
VARY REL command 466 DISPLAY APPLS command 36
VARY TERM command 469 DISPLAY CDRMS command 50
VERIFYCP start option DISPLAY CDRSCS command 54
displaying 235 DISPLAY CLSTRS command 60
setting 392 DISPLAY GROUPS command 86
version and release of VTAM, displaying 235 DISPLAY LINES command 127
VFYRED start option DISPLAY RSCLIST command 161
displaying 235 DISPLAY TERMS command 206
modifying 385 DISPLAY TGPS command 210
setting 392 DISPLAY TOPO command 215
VFYREDTI start option DISPLAY TRACES command 222
displaying 235
modifying 385
setting 392 X
virtual nodes, displaying 216 XCA (external communication adapter) major node
virtual route (VR) displaying 102
displaying status of 151, 155 XCFINIT start option
VIT (VTAM internal trace) displaying 235
displaying status of 225 setting 392
starting 380 XLENGTH operand
stopping 329 DISPLAY VTAMSTOR command 245

Index 515
XNETALS start option
displaying 235
setting 392

516 SNA Operation

Readers’ Comments — We’d Like to Hear from You

OS/390 eNetwork Communications Server

SNA Operation
Version 2 Release 6

Publication No. SC31-8567-01

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way
it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
 ___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SC31-8567-01 IBMR Along Line

_ _ _ _ _ _ _Fold
_ _ _ and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ do
_ _ not
_ _ _staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Corporation
Information Development
Department CGMD / Bldg 500
P.O. Box 12195
Research Triangle Park, NC
27709-9990

________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
SC31-8567-01 Along Line
IBMR

Program Number: 5647-A01 (OS/390)

Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.

SC31-8567-01