VTAM Operations
VTAM Operations
SNA Operation
Version 1 Release 7
SC31-8779-05
z/OS Communications Server
SNA Operation
Version 1 Release 7
SC31-8779-05
Note:
Before using this information and the product it supports, be sure to read the general information under “Notices” on page
615.
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Contents v
Appendix A. Cross-reference for VTAM DISPLAY commands . . . . . . . . . . . . 599
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
z/OS Communications Server information . . . . . . . . . . . . . . . . . . . . . . . . 625
z/OS Communications Server library . . . . . . . . . . . . . . . . . . . . . . . . . 625
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
You can use this document as a reference for specific operator commands and as
background reading to help understand how to operate VTAM.
To make the best use of this document, both the operator and the system
programmer should be familiar with the local operating system.
Communication
Adapter Non-SNA
Device
SNA Device
Coupling Facility
running in a sysplex
Most problems can be resolved at this Web site, where you can submit questions
and problem reports electronically, as well as access a variety of diagnosis
information.
For telephone assistance in problem diagnosis and resolution (in the United States
or Puerto Rico), call the IBM Software Support Center anytime (1-800-IBM-SERV).
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.
Clarification of notes
Information traditionally qualified as Notes is further qualified as follows:
Note Supplemental detail
Tip Offers shortcuts or alternative ways of performing an action; a hint
Guideline
Customary way to perform a procedure; stronger request than
recommendation
Rule Something you must do; limitations on your actions
Restriction
Indicates certain conditions are not supported; limitations on a product or
facility
Requirement
Dependencies, prerequisites
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.
Second Line
REQUIRED_OPERAND
REQUIRED_OPERAND_OR_VALUE_1
REQUIRED_OPERAND_OR_VALUE_2
v Optional operands and values appear below the main path line.
OPERAND
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.
Note: VTAM and IP commands are not case sensitive. You can code them in
uppercase or lowercase. If the operand is shown in both uppercase and
lowercase, the uppercase portion is the abbreviation (for example,
OPERand).
OPERAND
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
(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
Syntax Fragment:
1ST_OPERAND,2ND_OPERAND,3RD_OPERAND
Required information
Before using this product, you should be familiar with TCP/IP, VTAM, MVS, and
UNIX® System Services.
Related information
This section contains subsections on:
v “Softcopy information”
v “Other documents” on page xviii
v “Redbooks” on page xviii
v “Where to find related information on the Internet” on page xix
v “Using LookAt to look up message explanations” on page xx
Softcopy information
Softcopy publications are available in the following collections:
Title Number
DNS and BIND, Fourth Edition, O’Reilly and Associates, 2001 ISBN 0-596-00158-4
Routing in the Internet , Christian Huitema (Prentice Hall PTR, 1995) ISBN 0-13-132192-7
sendmail, Bryan Costales and Eric Allman, O’Reilly and Associates, 2002 ISBN 1-56592-839-3
SNA Formats GA27-3136
TCP/IP Illustrated, Volume I: The Protocols, W. Richard Stevens, Addison-Wesley ISBN 0-201-63346-9
Publishing, 1994
TCP/IP Illustrated, Volume II: The Implementation, Gary R. Wright and W. Richard ISBN 0-201-63354-X
Stevens, Addison-Wesley Publishing, 1995
TCP/IP Illustrated, Volume III, W. Richard Stevens, Addison-Wesley Publishing, 1995 ISBN 0-201-63495-3
TCP/IP Tutorial and Technical Overview GG24-3376
Understanding LDAP SG24-4986
z/OS Cryptographic Service System Secure Sockets Layer Programming SC24-5901
z/OS Integrated Security Services Firewall Technologies SC24-5922
z/OS Integrated Security Services LDAP Client Programming SC24-5924
z/OS Integrated Security Services LDAP Server Administration and Use SC24-5923
z/OS JES2 Initialization and Tuning Guide SA22-7532
z/OS MVS Diagnosis: Procedures GA22-7587
z/OS MVS Diagnosis: Reference GA22-7588
z/OS MVS Diagnosis: Tools and Service Aids GA22-7589
z/OS MVS Using the Subsystem Interface SA22-7642
z/OS Program Directory GI10-0670
z/OS UNIX System Services Command Reference SA22-7802
z/OS UNIX System Services Planning GA22-7800
z/OS UNIX System Services Programming: Assembler Callable Services Reference SA22-7803
z/OS UNIX System Services User’s Guide SA22-7801
z/OS XL C/C++ Run-Time Library Reference SA22-7821
zSeries OSA-Express Customer’s Guide and Reference SA22-7935
Redbooks
The following Redbooks might help you as you implement z/OS Communications
Server.
Information about Web addresses can also be found in information APAR II11334.
DNS Web sites: For more information about DNS, see the following USENET
news groups and mailing addresses:
USENET news groups
comp.protocols.dns.bind
BIND mailing lists
http://www.isc.org/ml-archives/
BIND Users
v Subscribe by sending mail to [email protected].
v Submit questions or answers to this forum by sending mail to
[email protected].
BIND 9 Users (This list might not be maintained indefinitely.)
v Subscribe by sending mail to [email protected].
v Submit questions or answers to this forum by sending mail to
[email protected].
Note: Any pointers in this publication to Web sites are provided for convenience
only and do not in any manner serve as an endorsement of these Web sites.
You can use LookAt from the following locations to find IBM message
explanations for z/OS elements and features, z/VM®, VSE/ESA™, and Clusters for
AIX® and Linux™:
v The Internet. You can access IBM message explanations directly from the LookAt
Web site at http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/.
You can obtain code to install LookAt on your host system or Microsoft Windows
workstation from a disk on your z/OS Collection (SK3T-4269), or from the LookAt
Web site (click Download, and select the platform, release, collection, and location
that suit your needs). More information is available in the LOOKAT.ME files
available during the download process.
For additional information about checks and about IBM Health Checker for z/OS,
see IBM Health Checker for z/OS: User’s Guide. z/OS V1R4, V1R5, and V1R6 users
can obtain the IBM Health Checker for z/OS from the z/OS Downloads page at
http://www.ibm.com/servers/eserver/zseries/zos/downloads/.
SDSF also provides functions to simplify the management of checks. See z/OS
SDSF Operation and Customization for additional information.
The information in this document includes descriptions of support for both IPv4
and IPv6 networking protocols. Unless explicitly noted, descriptions of IP protocol
support concern IPv4. IPv6 support is qualified within the text.
New information
v VTAM and Enterprise Extender display enhancements
– DISPLAY EEDIAG
v LOGAPPL enhancements
– VARY AUTOLOG
v VTAM command to remove a generic resources from a sysplex
– MODIFY GR
v VTAM start option to display RSCVs
– DISPLAY VTAMOPTS
– MODIFY VTAMOPTS
– START
v EXPFLTRM operand in the DISPLAY VTAMOPTS, MODIFY VTAMOPTS, and
START section
Changed information
v VTAM and Enterprise Extender Display Enhancements
– DISPLAY RTPS
– DISPLAY ID
– DISPLAY SESSIONS
v LOGAPPL enhancements
– DISPLAY AUTOLOG
v Model definition of VTAM cross-domain resources
– DISPLAY ADJSSCPS
– DISPLAY CDRSCS
– DISPLAY ID
– DISPLAY MODELS
– DISPLAY RSCLIST
– DISPLAY TRACES
– DISPLAY VTAMSTOR
– MODIFY ALSLIST
– MODIFY CDRM
– MODIFY DEFAULTS
– MODIFY DIRECTRY
© Copyright IBM Corp. 1984, 2005 xxiii
– MODIFY ENCR
– MODIFY NOTRACE
– MODIFY RESOURCE
– MODIFY SECURITY
– MODIFY TABLE
– MODIFY TRACE
– MODIFY USERVAR
– VARY ACT
– VARY INACT
– VARY LOGON
– VARY NOLOGON
v Promotion of the use of IPv6 global unicast addresses- Site-local addresses
were designed to use private address prefixes that could be used within a site
without the need for a global prefix. Until recently, the full negative impacts of
site-local addresses in the Internet were not fully understood. The IETF has
deprecated the special treatment given to this site-local prefix. Because of this, it
is preferable to use global unicast addresses. This means we are replacing
addresses and prefixes that use the site-local prefix (fec0::/10) with ones that use
the global prefix for documentation (2001:0DB8::/32). Some samples and
examples in this document may display site-local prefixes instead of the now
preferred global unicast address.
Deleted information
v The support for the Cryptographic Unit Support Product (CUSP) has been
removed from the product.
This document has been enabled for the following types of advanced searches in
the online z/OS Library Center: commands.
You might notice changes in the style and structure of some content in this
document–for example, headings that use uppercase for the first letter of initial
words only, and procedures that have a different look and format. The changes are
ongoing improvements to the consistency and retrievability of information in our
documents.
Summary of changes
for SC31-8779-04
z/OS Version 1 Release 6
New information
v In the VTAM operator commands section:
– DISPLAY AUTOLOG
– DISPLAY CSMUSE
Changed information
v Promotion of the use of IPv6 global unicast addresses- Site-local addresses
were designed to use private address prefixes that could be used within a site
without the need for a global prefix. Until recently, the full negative impacts of
site-local addresses in the Internet were not fully understood. The IETF has
deprecated the special treatment given to this site-local prefix. Because of this, it
is preferable to use global unicast addresses. This means we are replacing
addresses and prefixes that use the site-local prefix (fec0::/10) with ones that use
the global prefix for documentation (2001:0DB8::/32). Some samples and
examples in this document may display site-local prefixes instead of the now
preferred global unicast address.
Starting with z/OS V1R4, you may notice changes in the style and structure of
some content in this document–for example, headings that use uppercase for the
first letter of initial words only, and procedures that have a different look and
format. The changes are ongoing improvements to the consistency and
retrievability of information in our documents.
Summary of changes
for SC31-8779-03
z/OS Version 1 Release 5
New information
v In the VTAM operator commands section:
– DISPLAY APINGTP
– DISPLAY CSDUMP
– DISPLAY INOPCODE
Changed information
v Sample displays in the DISPLAY ID, DISPLAY ADJSSCP, and NETSRVR sections
v SWNORDER and DLRORDER syntax diagrams in the MODIFY VTAMOPTS
section
v SWNORDER and DLRORDER syntax diagrams in the START command section
v DISPLAY RTPS section
v DISPLAY CSM command in the VTAM operator commands section
v MODIFY CSDUMP and MODIFY CSM in the VTAM operator commands section
v Storage usage summary sample display in DISPLAY BFRUSE
v SUBTRACE syntax and operand descriptions in MODIFY NOTRACE, MODIFY
TRACE, and START Commands section
v “Using wildcard names” on page 11
Starting with z/OS V1R4, you may notice changes in the style and structure of
some content in this document–for example, headings that use uppercase for the
first letter of initial words only, and procedures that have a different look and
format. The changes are ongoing improvements to the consistency and
retrievability of information in our documents.
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.
PU
CICS01 LU
VTAM SSCP
Channel 321
PU
NCP3AA1
LN3A1
PU PU
P3A3767A P3A3274A
Not Active
LU LU LU LU
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.
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.
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.
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.
The operator uses this command to display line LN3A1 and the resources that are
attached to the line.
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).
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, TYPE = DES
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.
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.
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.
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
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, TYPE = DES
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.
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
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.
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.
v 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.
VTAM operator commands and their formats are described later in this chapter.
See z/OS Communications Server: SNA Messages for an explanation of error messages
you might encounter.
See the “MODIFY EXIT command” on page 381 for information about modifying
an installation-wide exit routine. See z/OS Communications Server: SNA
Customization for information about the command verification exit routine.
Note: You can only specify one message-flooding prevention table per VTAM.
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.
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.
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, and in the values specified for the
LU and GNAME operands of the DISPLAY GRAFFIN command.
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
v Resources in any network whose name begins with T followed by
exactly two characters
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 z/OS 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.
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
supply the operator with an explanation of the new command syntax. For more
information on USS tables, see the z/OS 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.
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
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.
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
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
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.
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
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 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 NATIVE
IST1103I NETA.SSCPAA NN 0 0 *NA*
IST1104I CONNECTION SUMMARY FOR NETA.SSCPAA
IST172I NO CONNECTIONS FOUND
IST1493I RTP SUMMARY FOR NETA.SSCPAA COUNT = 1 RTPONLY = NA
IST1486I RTP NAME STATE DESTINATION CP MNPS TYPE
IST1487I CNR00001 CONNECTED NETA.SSCPAA NO CPCP
IST314I END
From a border node, 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 NATIVE
IST1103I NETA.SSCPAA NN 0 0 *NA*
IST1104I CONNECTION SUMMARY FOR NETA.SSCPAA
IST172I NO CONNECTIONS FOUND
IST1493I RTP SUMMARY FOR NETA.SSCPAA COUNT = 1 RTPONLY = NA
IST1486I RTP NAME STATE DESTINATION CP MNPS TYPE
IST1487I CNR00001 CONNECTED NETA.SSCPAA NO CPCP
IST314I END
DISPLAY NET,ADJSSCPS
,CDRM=sscp_name
,MAX=DSPLYDEF_start_option_value
,MAX= * ,NETID=netid
number_of_resources
,SCOPE=ONLY
ALL
,SCOPE=
ALL
ONLY
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
,MAX=DSPLYDEF_start_option_value
DISPLAY NET,ADJSSCPS ,ADJLIST=*
,MAX= *
number_of_resources
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
Operand Abbreviation
SCOPE=ONLY NONE or N
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 z/OS Communications Server: SNA Resource
Definition Reference for an explanation of NQNMODE.
| You can specify the name of a conventionally defined CDRSC, a model
| CDRSC, a clone CDRSC built from a model CDRSC, or a dynamic CDRSC. You
| can use wildcard characters in the name you specify. The use of the wildcard
| characters does not depend on the value of the DSPLYWLD start option.
| However, unlike wildcard characters in other commands, the wildcard
| characters you specify here do not represent unspecified characters. They are
| interpreted as actual characters, an asterisk (*) and a question mark (?).
| Therefore, if you specify D NET,ADJSSCPS,CDRSC=APPL*, VTAM will display
| information related to the model CDRSC named APPL* , but it will not display
| information about any other CDRSCs whose names begin with APPL.
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.
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.
Resulting display
The resulting display differs depending on the operands specified and the value of
VTAM start options. (For example, messages IST1704I and IST1705I are only issued
if VTAM is enabled for APPN.)
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.
See the z/OS 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. All of these
examples assume that the SORDER start option is currently set to
SORDER=ADJSSCP and that the SSCPORD start option is currently set to
SSCPORD=PRIORITY.
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 or ADJLIST)
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST623I DYNAMIC ADJACENT SSCP TABLE
IST1705I SORDER = ADJSSCP FROM START OPTION
IST1705I SSCPORD = PRIORITY FROM START OPTION
IST624I SSCP2A
IST1454I 1 RESOURCE(S) DISPLAYED
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
IST1705I SORDER = ADJSSCP FROM START OPTION
IST1705I SSCPORD = PRIORITY FROM START OPTION
IST1220I SSCPNAME NETID CURRENT STATE ROUTING STATUS
IST624I SSCP2A NETA ACTIV SUCCESS
IST1454I 1 RESOURCE(S) DISPLAYED
IST314I END
v Next you activate the following user-defined ADJSSCP table:
************************************************************
* *
* ADJSSCP Tables - Assumes SORDER=ADJSSCP Start Option *
* and SSCPORD=PRIORITY Start Option *
************************************************************
ADJSSCP VBUILD TYPE=ADJSSCP
* Default table for all networks
DEFAULT NETWORK SORDER=APPNFRST
SSCP1A ADJCDRM
SSCP2A ADJCDRM
SSCP7B ADJCDRM
SSCP9C ADJCDRM
* CDRM SSCP2A table for all networks
SSCP2A CDRM SSCPORD=PRIORITY
SSCP2A ADJCDRM
SSCP1A ADJCDRM
* Default table for network NETA
NETA NETWORK NETID=NETA,SORDER=APPNFRST,SSCPORD=DEFINED
SSCP1A ADJCDRM
SSCP2A ADJCDRM
* CDRM SSCP2A table for network NETA
SSCP2A CDRM SSCPORD=STARTOPT
SSCP2A ADJCDRM
SSCP1A ADJCDRM
* Default table for network NETB
NETB NETWORK NETID=NETB
SSCP7B ADJCDRM
* Default table for network NETC
NETC NETWORK NETID=NETC
SSCP9C ADJCDRM
* Define adjacent lists for NETA, NETB and NETC
LISTA ADJLIST
SSCP1A ADJCDRM
SSCP2A ADJCDRM
LISTB ADJLIST
SSCP7B ADJCDRM
LISTC ADJLIST
SSCP9C ADJCDRM
v To display the new, dynamically created, session-specific adjacent SSCP table for
the same resource as above, issue:
d net,adjsscps,cdrsc=appl2
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
IST611I ADJACENT SSCP TABLE FOR APPL2 IN NETA
IST1704I SORDER = APPNFRST FROM ADJACENT SSCP TABLE
IST1705I SSCPORD = PRIORITY FROM START OPTION
IST1220I SSCPNAME NETID CURRENT STATE ROUTING STATUS
IST624I ISTAPNCP NETA ACTIV ***NA**
IST624I SSCP2A NETA ACTIV SUCCESS
IST624I SSCP1A NETA ACTIV ***NA**
IST1454I 3 RESOURCE(S) DISPLAYED
IST314I END
v 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
IST1704I SORDER = APPNFRST FROM ADJACENT SSCP TABLE
IST1705I SSCPORD = PRIORITY FROM START OPTION
IST624I SSCP1A
IST624I SSCP2A
IST624I SSCP7B
IST624I SSCP9C
IST1454I 4 RESOURCE(S) DISPLAYED
IST314I END
| v To display the dynamic ADJSSCP table for a model CDRSC, issue:
| d net,adjsscps,cdrsc=applb*
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
| IST611I ADJACENT SSCP TABLE FOR APPLB* IN NETB
| IST1705I SORDER = APPN FROM START OPTION
| IST1705I SSCPORD = PRIORITY FROM START OPTION
| IST1220I SSCPNAME NETID CURRENT STATE ROUTING STATUS
| IST624I SSCP7B NETB NEVAC ***NA**
| IST624I ISTAPNCP NETA ACTIV ***NA**
| IST1454I 2 RESOURCE(S) DISPLAYED
| 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=sscp2a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = ADJACENT SSCP TABLE
,CONSEC=1 ,ECHO=YES
,CONSEC=number_of_consecutive_packets ,ECHO= NO
YES
,ITER=2 ,LIST=ALL
,ITER=number_of_send_and_receive_iterations ,LIST=SUMMARY
,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.
More than one D APING command can be executing at a time. The default limit
for APING command TP instances is 10. The limit may be adjusted using the
MODIFY APINGTP command. Information about the APING TP and its sessions
may be displayed using the DISPLAY APINGTP command.
Note: Issuing an APING command to the same partner and with the same
logmode may result in a failure with RCPRI=2C and RCSEC=11. This failure
occurs because the second command was issued prior to completion of
session setup for the first APING command. This condition is temporary
and a subsequent APING command should work. If desired, you can issue
the APING to the same partner and specify a different logmode.
Refer to z/OS 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.
28 z/OS V1R7.0 Comm Svr: SNA Operation
DISPLAY APING
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.
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.
LIST
Specifies whether detailed statistics for iteration data exchanged should be
displayed.
LIST=ALL
Specifies that all output messages should be displayed.
LIST=SUMMARY
Specifies that iteration statistics messages should be suppressed. All other
messages will be included.
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.
Resulting display
The resulting VTAM display shows performance information and routing
information in two separate message groups.
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
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
IST314I END
,LIST=ONLY
,MAX=DSPLYDEF_start_option_value
,LIST= ALL
,MAX= *
number_of_sessions
COUNT
ONLY
Purpose
The DISPLAY APINGDTP command displays the number of APINGD transaction
programs permitted to run concurrently for responding to APING requests from
other nodes, and optionally shows session information for active APINGD
instances.
Operands
LIST
Specifies the level of detail to display.
LIST=ALL
Specifies that the partner LU name and Session Identifier for active
sessions associated with all APINGD instances should be displayed.
LIST=COUNT
Specifies that only the instance limit and the number of active sessions
should be displayed.
LIST=ONLY
Specifies that only the instance limit should be displayed.
MAX
Specifies the maximum number of sessions 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_sessions
Specifies the number of sessions to display for this command. The valid
range is 1 through the 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.
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,
and optionally shows session information for active APINGD instances.
Examples
Displaying the number of transaction programs permitted to run concurrently:
d net,apingdtp
IST097I DISPLAY ACCEPTED
IST1474I APINGD TP CONCURRENT INSTANCE LIMIT = 10
,LIST=ONLY
,MAX=DSPLYDEF_start_option_value
,LIST= ALL
,MAX= *
number_of_sessions
COUNT
ONLY
Purpose
The DISPLAY APINGTP command displays the number of APING command
transaction programs permitted to run concurrently for sending APING requests to
other nodes, and optionally shows session information for active APING instances.
Operands
LIST
Specifies the level of detail to display.
LIST=ALL
Specifies that the partner LU name and Session Identifier for active
sessions associated with all APING instances should be displayed.
LIST=COUNT
Specifies that only the instance limit and the number of active sessions
should be displayed.
LIST=ONLY
Specifies that only the instance limit should be displayed.
MAX
Specifies the maximum number of sessions 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_sessions
Specifies the number of sessions to display for this command. The valid
range is 1 through the 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.
Resulting display
The resulting VTAM display shows the number of APING command transaction
programs permitted to run concurrently for sending APING requests to other
nodes, and optionally shows session information for active APING instances.
Examples
Displaying the number of transaction programs permitted to run concurrently:
d net,apingtp
IST097I DISPLAY ACCEPTED
IST1474I APING TP CONCURRENT INSTANCE LIMIT = 10
( 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
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.
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 11.
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.
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
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.
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
IST360I APPLICATIONS:
IST080I ECHO01A ACT/S ECHO01B ACTIV ECHO01C ACT/S
IST080I ECHO01D CONCT ECHO01E CONCT
IST1454I 93 RESOURCE(S) DISPLAYED
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
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
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
Purpose
The DISPLAY AUTOLOG command displays information about controlling
applications that have pending autologon requests. By default, this command
displays each controlling application for which there is at least one pending
autologon request and the condition (or conditions) that will cause the pending
autologon request or requests to be initiated again. Optionally, this command also
displays a list of secondary logical units that have pending autologon requests for
each controlling application displayed.
Refer to z/OS Communications Server: SNA Network Implementation Guide for more
information on AUTOLOGON.
The following operands can be used to control the output that is generated by this
command.
Operands
ID=controlling_appl
Specifies the real or alias name of a controlling application for which pending
autologon requests may exist. Controlling_appl can be network qualified. If
controlling_appl is not network qualified, then the network ID of the host from
which the command was issued is used.
SCOPE
Specifies whether the display output includes the names of secondary logical
units that have pending autologon requests for each controlling application.
SCOPE=ALL
A list of secondary logical units that have pending autologon requests is
displayed for each controlling application that is displayed.
SCOPE=ONLY
A list of secondary logical units that have pending autologon requests is
not displayed.
| MAX
| Specifies the maximum number of resources to be displayed by 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 maximum number of resources to be displayed by this
Resulting display
The resulting display shows:
v For ID= and SCOPE=ONLY, if pending autologon requests exist for the
controlling application specified on the ID= operand, the controlling application
name is displayed, along with the condition or conditions that will cause these
pending autologon requests to be initiated.
v For ID= and SCOPE=ALL, if pending autologon requests exist for the controlling
application specified on the ID= operand, the controlling application name is
displayed, along with the condition or conditions that will cause these pending
autologon requests to be initiated. A list of secondary logical units that have
autologon requests pending for this controlling application is also displayed.
v For SCOPE=ONLY, every controlling application that has at least one pending
autologon request is displayed, along with the condition or conditions that will
cause these pending autologon requests to be initiated.
v For SCOPE=ALL, every controlling application that has at least one pending
autologon request is displayed, along with the condition or conditions that will
cause these pending autologon requests to be initiated. A list of secondary
logical units that have autologon requests pending for each controlling
application is also displayed.
Examples
The following is displayed if there is an autologon request pending for APPL1. The
host on which the command was issued has the AUTOTI start option set to a
nonzero value, the AUTORTRY=CDRM start option is set, and the host network ID
is NETA:
d net,autolog,id=appl1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = AUTOLOG
IST1990I PENDING AUTOLOGON REQUESTS FOR:
IST1991I NETA.APPL1 - WAITING FOR CDRM ACTIVATION
IST1996I OR AUTOTI TIMER
IST314I END
The following is displayed if there is an autologon request pending for APPL1. The
host on which the command was issued has the AUTOTI start option set to a
nonzero value, the AUTORTRY=CDRM start option is set, and the host network ID
is NETA. In this case, the pending autologon request for APPL1 was created when
an autologon request found APPL1 to be in a connectable state (not enabled for
sessions). The host on which APPL1 resides sends a notification when APPL1
becomes session capable:
d net,autolog,id=appl1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = AUTOLOG
IST1990I PENDING AUTOLOGON REQUESTS FOR:
IST1993I NETA.APPL1 - WAITING FOR PLU NOTIFICATION
IST314I END
The following is displayed if there are autologon requests pending for APPL1,
APPL2 and APPLBA1. In this case, the real network ID is known for APPL1 and
APPLBA1, but not for APPL2. The host on which the command was issued has
AUTOTI defined with a nonzero value and AUTORTRY=ALL. The pending
autologon request for APPL1 was created when an autologon request found APPL1
to be in a connectable state (not enabled for sessions). The pending autologon
requests for APPL2 and APPLBA1 were created when these autologon requests
failed to find the controlling applications.
d net,autolog
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = AUTOLOGON
IST1990I PENDING AUTOLOGON REQUESTS FOR:
IST1991I NETA.APPL1 - WAITING FOR PLU NOTIFICATION
IST1994I APPL2 - WAITING FOR CDRM OR CPCP ACTIVATION
IST1996I OR AUTOTI TIMER
IST1994I NETB.APPLBA1 - WAITING FOR CDRM OR CPCP ACTIVATION
IST1996I OR AUTOTI TIMER
IST314I END
| The following is displayed when two LUs in this host have logged off their
| controlling application (APPL1), which resides in a different host and is
| session-capable:
| d net,autolog,id=appl1,scope=all
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = AUTOLOG
| IST1990I PENDING AUTOLOGON REQUESTS FOR:
| IST2100I NETA.APPL1 - NORMALLY LOGGED OFF LUS
| IST1997I NETB.L3B3278A NETB.L3B3279C
| IST314I END
Abbreviations
Operand Abbreviation
DISPLAY D
BUFFER=* BUF=*
BUFFER=buffid BUF=buffid
BUFFER=SHORT BUF=SH
BUFFER=SUMMARY BUF=SUMM
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 49 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:
v CSA usage for buffers
v IRNLIMIT buffer usage
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 of each buffer, in bytes. (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.
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:
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
– The system CSA limit (90% of the total 24-bit and 31-bit CSA defined to the
system)
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.
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 z/OS
Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures.
Table 1 shows the IDs, names and abbreviated names of the buffer pools. For
descriptions of VTAM buffer pools, see the z/OS Communications Server: SNA
Network Implementation Guide.
Table 1. Buffer pools
ID Name Abbrev
IO00 IOBUF IO
BS00 BSBUF BS
LP00 LPBUF LP
XD00 XDBUF XD
LF00 LFBUF LF
CRPL CRPLBUF CR
SF00 SFBUF SF
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 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
IST1667I SYSTEM CSA LIMIT=1887436K
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 -------------------------------------------------------------
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
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 T100 1004 16 16 16 0 0 15/----- 32
IST356I T200 2028 8 8 8 0 0 7/----- 32
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
IST1667I SYSTEM CSA LIMIT=1887436K
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 -------------------------------------------------------------
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
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
IST1321I TABLE FOR BNCOSMAP DEFAULT_NETID
IST1322I NON-NATIVE NATIVE
( 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
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.
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 11.
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.
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:
d net,cdrms
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CDRMS
IST089I CDRM1A TYPE = CDRM SEGMENT , ACTIV
Displaying CDRM major nodes and their minor nodes, limiting output to five
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
,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
Purpose
The DISPLAY CDRSCS (cross-domain resources) command displays information
about cross-domain resources, including independent LUs.
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 11.
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.
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.
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 the following:
v If ID is specified, the name and status of the specified CDRSC major node or
nodes are displayed. 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 are displayed. 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 including model
| CDRSCs and clone CDRSCs are displayed. The display output is 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 CDRSC1A TYPE = CDRSC SEGMENT , ACTIV
| IST483I A04I042* ACTIV , CDRM = ***NA***, NETID = NETA
| IST483I A04I0423 ACTIV , CDRM = ***NA***, NETID = NETA
| IST483I A04I0422 ACTIV , CDRM = ***NA***, NETID = NETA
| IST483I A04I0421 ACTIV , CDRM = ***NA***, NETID = NETA
| IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV
| IST483I L3A4956V ACTIV , CDRM = ***NA***, NETID = NETA
| IST483I L3A4956W ACTIV , CDRM = ***NA***, NETID = NETA
| IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV
| IST483I C25NVLUC ACTIV----Y, CDRM = ***NA***, NETID = NETA
| IST1454I 7 RESOURCE(S) DISPLAYED
| IST314I END
( name )
,IDTYPE=* ,LIST=ALL
,IDTYPE= LCLSNA ,LIST= ALL
PUT45 COUNT
SWSEG
*
,MAX=DSPLYDEF_start_option_value
,MAX= * ,OWNER= host_name
number_of_resources *NONE
,SCOPE=ALL
ALL
,SCOPE=
ACT
ACTONLY
ALL
CONCT
IACTIVE
IINACT
INACT
INACTONLY
PENDING
RELSD
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=ALL EVERY or E
SCOPE=CONCT CONCT
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
Operand Abbreviation
SCOPE=RELSD RELSD
SCOPE=RESET RESET
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 11.
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.
LIST
Specifies the level of detail to display.
LIST=COUNT
Displays only the number of resouces in each state, based on the filters
specified in the SCOPE, OWNER, and IDTYPE keywords.
LIST=ALL
Displays information about all resources, based on the filters specified in
the SCOPE, OWNER, and IDTYPE keywords.
MAX
Specifies the maximum number of resources that VTAM displays for this
command. This operand is ony 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 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
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.
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=IACTIVE
Specifies that information is to be displayed about all PUs within the
specified major nodes (or within all NCP, local SNA, and switched major
nodes if the ID operand is omitted) for which the minor node is
ISTATUS=INACTIVE.
SCOPE=IINACT
Specifies that information is to be displayed about all PUs within the
specified major nodes (or within all NCP, local SNA, and switched major
nodes if the ID operand is omitted) for which the minor node is
ISTATUS=ACTIVE.
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 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=RELSD
Specifies that the information is to be displayed about all PUs in a RELSD
state within the specified major nodes (or within all NCP, local SNA, and
switched major nodes if the ID operand is omitted).
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
IST1454I 9 RESOURCE(S) DISPLAYED FOR ID=C23SMNC
IST314I END
Displaying LIST=COUNT:
d net,clstrs,id=ncp3ab8,list=count
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CLUSTERS/PHYS UNITS
IST089I NCP3AB8 TYPE = PU T4/5 , ACTIV
IST1747I SUMMARY OF STATE INFORMATION:
IST1748I RESET = 4 RELSD = 2 NEVAC = 36
IST1748I ACTIV = 3
IST1454I 45 RESOURCE(S) DISPLAYED FOR ID=NCP3AB8
IST314I END
,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
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 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
IST1005I WINLCNT = 1 WINRCNT = 0 AUTOSES = 0
IST1005I DRESPL =NALLOW RESP =***NA*** DELETE =NALLOW
IST1005I SYNCLVL =SYNCPT CONVCAP =HDX
,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.
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
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 with no API activity for more than two 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
,TYPE=SUBAREA
DISPLAY NET,COS
,ID=pu_name ,NETID= *
netid
Display the APPN Class of service table entries and the APPNCOS table used to
create each entry:
DISPLAY NET,COS,TYPE=APPN
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
When TYPE=SUBAREA is coded (or defaulted):
v 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.
v 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.
Resulting display
The resulting display shows the requested networks paired with the applicable
COS tables.
Examples
Displaying a Class of Service table for a specific PU:
d net,cos,id=istpus
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = SUBAREA COS
IST354I PU T4/5 MAJOR NODE = ISTPUS
IST862I NETID = NETA COSTABLE = ISTSDCOS
IST314I END
,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
,MAX= * ,SCOPE= ACT
number_of_CPCP_sessions ALL
PENDING
INACT
Notes:
1 Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand.
2 Since an end node will never have CP-CP sessions with another end node,
LIST=EN is not valid if this command is issued from an end node. In this
case, the LIST operand is not necessary because the output for LIST=ALL and
LIST=NN will be identical.
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
Use the DISPLAY CPCP command from a network node or end node to display
the status of CP-CP sessions with adjacent APPN nodes. If the ID operand is not
specified, then the CP-CP session status for all adjacent APPN nodes capable of
having CP-CP sessions with the local node is displayed.
The ID operand can be used to filter this display so that fewer adjacent nodes are
shown. If a network qualified adjacent CP name is specified, then the CP-CP
session status for only that node is displayed. If the CP name specified is not
network qualified, then the CP-CP session status for all adjacent nodes with that
CP name (and any network ID) is displayed. If the adjacent CP name specified is a
wildcard name, then the CP-CP session status for all adjacent nodes with matching
CP names is displayed.
Operands
ID Specifies the name of the adjacent node to display.
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 11.
ID=cp_name
Specifies the name of an adjacent control point to display.
ID=*.*
Specifies that all adjacent nodes are to be displayed.
LIST
Specifies the type of adjacent nodes to be displayed.
LIST=ALL
Displays information about all adjacent nodes specified on the ID operand.
If you omit the ID operand, information about all adjacent nodes is
displayed.
LIST=NN
Displays information about the network nodes specified on the ID
operand. If you omit the ID operand, information about all network nodes
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.
SCOPE
Specifies the status of the CP-CP sessions to display.
SCOPE=ACT
Displays only active CP-CP sessions.
SCOPE=ALL
Displays all CP-CP sessions, whether active, pending, or inactive.
SCOPE=INACT
Displays only inactive CP-CP sessions. The output shows adjacent nodes
that have at least one active CP-CP session-capable connection but no
CP-CP sessions with the local node.
SCOPE=PENDING
Displays only pending CP-CP sessions.
MAX
Specifies the maximum number of CP-CP sessions 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_cpcp_sessions
Specifies the number of CP-CP 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.
Resulting display
The resulting display shows the status of CP-CP sessions between the local node
and adjacent nodes.
Examples
Displaying CP-CP session status for all adjacent nodes when no CP-CP sessions
exist:
d net,cpcp
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CP-CP SESSION STATUS
IST1763I NO ACTIVE CP-CP SESSION-CAPABLE TGS EXIST
IST1454I 0 ADJCP(S) DISPLAYED
IST314I END
Displaying pending CP-CP session status for all adjacent network nodes:
d net,cpcp,list=nn,scope=pending
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CP-CP SESSION STATUS
IST1765I ADJACENT CP WINNER LOSER STATE NODE ANDCB
IST1766I NETA.SSCP2A PACT INACT UP NN 004AA010
IST1454I 1 ADJCP(S) DISPLAYED
IST314I END
Displaying active CP-CP session status for all adjacent end nodes:
d net,cpcp,list=nn,scope=act
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CP-CP SESSION STATUS
IST1765I ADJACENT CP WINNER LOSER STATE NODE ANDCB
IST1766I NETA.SSCPAA ACT ACT UP EN 004AA128
IST1766I NETA.SSCPBA ACT ACT UP EN 004AA028
IST1454I 2 ADJCP(S) DISPLAYED
IST314I END
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
The DISPLAY CSDUMP command displays the current dump triggers set by the
MODIFY CSDUMP command.
Resulting display
The resulting display shows the current CSDUMP message and sense code triggers
to take the dump. If either the message or sense code trigger does not exist, then
NONE is indicated.
Examples
The following sample output is displayed when both a message and a sense code
trigger have been set using the MODIFY CSDUMP command:
d net,csdump
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CSDUMP TRIGGERS
IST1871I MESSAGE TRIGGER: MESSAGE = IST080I MATCHLIM = 1
IST1872I VALUE 1 = CSMAPPL1
IST1873I SENSE TRIGGER: SENSE = 08010000 RU = 810601 MATCHLIM = 1
IST314I END
The following sample output is displayed when neither a message nor a sense
code trigger has been set using the MODIFY CSDUMP command:
d net,csdump
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CSDUMP TRIGGERS
IST1874I MESSAGE TRIGGER: NONE
IST1875I SENSE TRIGGER: NONE
IST314I END
The following sample output is displayed when only a sense code trigger has been
set using the MODIFY CSDUMP command:
d net,csdump
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = CSDUMP TRIGGERS
IST1874I MESSAGE TRIGGER: NONE
IST1873I SENSE TRIGGER: SENSE = 08010000 RU = 810601 MATCHLIM = 1
IST314I END
DISPLAY NET,CSM
,OWNERID= ALL
ownerid
DISPLAY NET,CSM,MONITOR
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
To Monitor CSM Storage usage:
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.
The DISPLAY CSM command with MONITOR option allows the display of the
current status of CSM buffer monitor.
Operands
To Monitor CSM Storage usage:
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 hexidecimal
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 owner ID showing the amount of storage
owned in each storage pool and the cumulative total for each owner ID
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
Resulting display
The resulting display to Monitor CSM storage usage shows:
v The overall storage use for each of the different sizes in the ECSA pools
v If OWNERID is specified, the amount of storage allocated to the owner
v If OWNERID is not specified, information about storage usage for each buffer
pool
v The maximum current values for fixed and ECSA storage
| v The highest level of fixed and ECSA storage obtained (highwater mark) since the
| last D NET,CSM command without the ownerid operand.
v The names of the CSM data spaces
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
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 31 0M 256K 256K
IVT5533I 16K DATA SPACE 31 0M 0M 0M
IVT5533I 32K DATA SPACE 31 0M 0M 0M
IVT5533I 60K DATA SPACE 31 0M 0M 0M
IVT5533I 180K DATA SPACE 31 0M 0M 0M
IVT5535I TOTAL DATA SPACE 31 0M 256K 256K
IVT5532I ------------------------------------------------------
IVT5533I 4K DATA SPACE 64 0M 256K 256K
IVT5533I 16K DATA SPACE 64 0M 0M 0M
IVT5533I 32K DATA SPACE 64 0M 0M 0M
IVT5533I 60K DATA SPACE 64 0M 0M 0M
IVT5534I 180K DATA SPACE 64 POOL DOES NOT EXIST
IVT5535I TOTAL DATA SPACE 64 0M 256K 256K
IVT5532I ------------------------------------------------------
IVT5535I TOTAL DATA SPACE 0M 512K 512K
IVT5532I ------------------------------------------------------
IVT5536I TOTAL ALL SOURCES 0M 768K 768K
IVT5538I FIXED MAXIMUM = 100M FIXED CURRENT = 400K
IVT5541I FIXED MAXIMUM USED = 400K
IVT5539I ECSA MAXIMUM = 100M ECSA CURRENT = 414K
Display CSM Monitoring when CSM MONITOR option is dynamic and currently
not active:
d net,csm,monitor
IVT5508I DISPLAY ACCEPTED
IVT5570I CSM MONITOR IS DYNAMIC AND CURRENTLY NOT ACTIVE
Display CSM Monitoring when CSM MONITOR option is dynamic and currently
active:
d net,csm,monitor
IVT5508I DISPLAY ACCEPTED
IVT5569I CSM MONITOR IS DYNAMIC AND CURRENTLY ACTIVE
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
The DISPLAY CSMUSE command allows IBM service to evaluate the use of
storage managed by the communications storage manager (CSM). Although this
command is similar to the DISPLAY CSM command, it provides a lower level of
detail regarding storage usage, and therefore the output of this command is
different than that of DISPLAY CSM.
This command is primarily intended for IBM service. However, it can also be
beneficial to the user. The display output provides detailed information about each
CSM storage pool. The detailed information describes storage as it corresponds to
an identifier, which is referred to as a monitor ID. Monitor IDs describe specific
z/OS Communications Server components. When CSM storage is associated with
(or isolated to) a specific monitor ID, then IBM service can correlate the monitor ID
to a component (usage or function) of z/OS Communications Server. This
information can be useful when evaluating how z/OS Communications Server is
using system storage or to help diagnose storage growth. Refer to z/OS
Communications Server: IP and SNA Codes for the complete description of monitor
IDs.
The CSM monitor IDs are associated with the CSM monitor function. The display
output from this command will always provide monitor IDs even when the
monitor is inactive. However, the display output will be much more useful when
the CSM monitor is active (an active monitor will provide closer tracking). To
determine if the CSM monitor is active, refer to the “DISPLAY CSM command” on
page 83.
You can use this command to see up to four monitor ID/OWNERID pairs using
the most CSM storage for each pool.
This command is routed to CSM so that VTAM does not have to be operational
when you issue this command.
Operands
POOL
Specifies whether to display information about the amount of storage in use by
all pools or a specific pool. The POOL is the pool name of the CSM storage
pool. OWNERID can be specified with the pool. When POOL is specified on
the command, CSM displays up to four monitor IDs with the amount of
storage and the buffer’s user data field and monitor history field. The user data
field allows IBM service to correlate the current usage and history to a specific
resource, such as a device, connection, route, and so forth. The monitor IDs are
displayed in the order of highest to lowest storage usage in the messages.
The default value of POOL is ALL.
POOL=ALL
A summary is provided for all CSM pools.
POOL=poolname
Specifies the poolname of the CSM storage pool.
Following is a list of valid CSM pool names and their explanations:
4KECSA
4 KB buffer size ECSA storage pool.
16KECSA
16 KB buffer size ECSA storage pool.
32KECSA
32 KB buffer size ECSA storage pool.
60KECSA
60 KB buffer size ECSA storage pool.
180KECSA
180 KB buffer size ECSA storage pool.
4KDS
4 KB buffer size data space storage pool.
16KDS
16 KB buffer size data space storage pool.
32KDS
32 KB buffer size data space storage pool.
60KDS
60 KB buffer size data space storage pool.
180KDS
180 KB buffer size data space storage pool.
4KDS64
4 KB buffer size data space backed by 64–bit real storage pool.
16KDS64
16 KB buffer size data space backed by 64–bit real storage pool.
32KDS64
32 KB buffer size data space backed by 64–bit real storage pool.
60KDS64
60 KB buffer size data space backed by 64–bit real storage pool.
180KDS64
180 KB buffer size data space backed by 64–bit real storage pool.
OWNERID
Specifies whether to display information about the amount of storage owned
by all owners or a specific owner. The owner ID is the halfword 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 the storage pool source.
OWNERID=ALL
Produces the same display as if OWNERID was not specified.
OWNERID=ownerid
Specifies that the storage owned by the specified owner ID be displayed.
Resulting display
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,csmuse
IVT5508I DISPLAY ACCEPTED
IVT5572I PROCESSING DISPLAY CSMUSE COMMAND - OWNERID NOT SPECIFIED
IVT5532I ------------------------------------------------------
IVT5575I USAGE SUMMARY - 4KECSA POOL TOTAL (ALL USERS) = 60K
IVT5576I AMOUNT MONITOR ID OWNERID JOBNAME
IVT5577I 24K B1 0029 TCPCS
IVT5577I 24K 21 0028 VTAMCS
IVT5578I DISPLAY TOTAL FOR 4KECSA POOL (2 USERS) = 48K
IVT5532I ------------------------------------------------------
IVT5575I USAGE SUMMARY - 32KECSA POOL TOTAL (ALL USERS) = 32K
IVT5576I AMOUNT MONITOR ID OWNERID JOBNAME
IVT5577I 32K B1 0029 TCPCS
IVT5578I DISPLAY TOTAL FOR 32KECSA POOL (1 USERS) = 32K
IVT5532I ------------------------------------------------------
IVT5575I USAGE SUMMARY - 4KDS64 POOL TOTAL (ALL USERS) = 24K
IVT5576I AMOUNT MONITOR ID OWNERID JOBNAME
IVT5577I 20K 21 0028 VTAMCS
IVT5578I DISPLAY TOTAL FOR 4KDS64 POOL (1 USERS) = 20K
IVT5599I END
Tips:
v This is the summary information (when ALL pools specified or defaulted).
v An operator can also use OWNERID of the user with this command and
monitor one user.
v A pool will not be displayed if there is no storage in use or it does not match
the provided OWNERID.
v An operator can get more details about a specific pool if poolname is specified.
v Although CSM storage will always have an associated monitor ID even when
the CSM Monitor is not active, the monitor IDs are tracked (monitored and
updated) more closely when the CSM monitor is active.
v Refer to z/OS Communications Server: IP and SNA Codes for the description of
monitor IDs.
Guideline: Under each pool summary, monitor IDs are no longer listed when 75%
of the pool total usage or a maximum of four monitor ID and OWNERID pairs is
reached. They are listed in the order by highest to lowest storage usage. It will
display at least one pair of monitor ID and OWNERID usage.
The new display CSMUSE command with the ownerid operand and its output:
d net,csmuse,ownerid=0029
IVT5508I DISPLAY ACCEPTED
IVT5573I PROCESSING DISPLAY CSMUSE COMMAND - OWNERID SPECIFIED
IVT5557I OWNERID: ASID = 0029 JOBNAME = TCPCS
IVT5532I ------------------------------------------------------
IVT5575I USAGE SUMMARY - 4KECSA POOL TOTAL (ALL USERS) = 56K
IVT5576I AMOUNT MONITOR ID OWNERID JOBNAME
The new display CSMUSE command with the pool operand and its output:
d net,csmuse,pool=4kecsa
IVT5508I DISPLAY ACCEPTED
IVT5574I PROCESSING DISPLAY CSMUSE COMMAND - POOL SPECIFIED
IVT5584I USAGE DETAILS - 4KECSA POOL - POOL TOTAL = 56K
IVT5532I ------------------------------------------------------
IVT5576I AMOUNT MONITOR ID OWNERID JOBNAME
IVT5532I ------------------------------------------------------
IVT5577I 24K B1 0029 TCPCS
IVT5579I BUFFER USE FOR B1 : USECNT USERDATA MONITOR HISTORY
IVT5580I 3 15352C90 000000B1
IVT5580I 2 15352C88 000000B1
IVT5580I 1 15352C98 000000B1
IVT5580I 1 15352CA8 000000B1
IVT5532I ------------------------------------------------------
IVT5577I 20K 21 0028 VTAMCS
IVT5579I BUFFER USE FOR 21 : USECNT USERDATA MONITOR HISTORY
IVT5580I 5 F0C4F0F0 00000021
IVT5585I DETAIL TOTAL FOR 4KECSA POOL = 44K
IVT5599I END
Tips:
v This is an example of the detailed CSM usage information (when a specific pool
is specified).
v For each CSM monitor ID, the user data field and monitor history field from the
CSM buffer headers is provided. The user data field allows IBM service to
correlate the current usage and monitor history to a specific resource, such as a
device, connection, route, and so on.
v Note that the display is similar to poolname=all (summary) with the addition of
IVT5579I and IVT5580I. This display is most useful when CSM MONITOR is
active.
v This detailed output provides details of the same monitor IDs that were
provided in the summary display (for example, if the summary output only
provided one monitor ID, then the detailed display will provide information
about one monitor ID).
v Under each monitor ID, more detailed buffer usage information is provided. A
list of up to four usage pairs (user data and monitor ID history) are provided.
The usage pairs are listed in order of highest to lowest number of times a
matching usage pair was found. The use count is only counted once per CSM
buffer even when multiple matching usage pairs exist for the same buffer. A
usage pair match is counted for either a CSM primary buffer or image buffer
usage, but not both (or multiple images) for the same CSM buffer. A CSM buffer
may have multiple concurrent usages that have both matching and unmatching
usage pairs, and therefore some CSM buffers may be counted multiple times.
v An operator can also specify OWNERID of the user with the poolname and
monitor one user (specific TCP stack or VTAM).
90 z/OS V1R7.0 Comm Svr: SNA Operation
DISPLAY DIRECTRY
,SCOPE=ONLY
DISPLAY NET,DIRECTRY ,ID=name
,SCOPE= ALL
ONLY
NSEARCH
,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
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=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 an asterisk (*) 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.
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
asterisk (*) 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 to the 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:
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.
Note: When the entry type is registered or dynamic, and the resource type is an
LU, the display also includes the LU’s subarea number (if applicable), the
desired locate size, and the last locate size.
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.
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 LU:
d net,directry,id=appcaa01
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = DIRECTORY
IST1186I DIRECTORY ENTRY = REGISTERED LU
IST1184I CPNAME = NETA.SSCPAA - NETSRVR = NETA.SSCP1A
IST484I SUBAREA = 1
IST1703I DESIRED LOCATE SIZE = 1K, LAST LOCATE SIZE = 1K
IST314I END
IST924I -------------------------------------------------------------
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
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
533 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.
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 195.
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
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.
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
DISPLAY EE command
Display general Enterprise Extender information:
,LIST=SUMMARY
DISPLAY NET,EE
,LIST=SUMMARY
,LIST=DETAIL
,LIST=SUMMARY
DISPLAY NET,EE ,ID=name
,LIST=SUMMARY
,LIST=DETAIL
DISPLAY NET,EE
,IPADDR= local_ipaddr
,HOSTNAME=(,remote_hostname)
(local_ipaddr)
,HOSTNAME=(,remote_hostname)
(local_ipaddr,remote_ipaddr)
(,remote_ipaddr)
,LIST=SUMMARY ,MAX=DSPLYDEF_start_option_value
,LIST=SUMMARY ,MAX= *
,LIST=DETAIL number_of_EE_connections
DISPLAY NET,EE
,HOSTNAME= local_hostname
,IPADDR=(,remote_ipaddr)
(local_hostname)
,IPADDR=(,remote_ipaddr)
(local_hostname,remote_hostname)
(,remote_hostname)
,LIST=SUMMARY ,MAX=DSPLYDEF_start_option_value
,LIST=SUMMARY ,MAX= *
,LIST=DETAIL number_of_EE_connections
Abbreviations
Operand Abbreviation
DISPLAY D
HOSTNAME HN
IPADDR IP
LIST=DETAIL DETAIL or DET
LIST=SUMMARY SUMMARY or SUM
Purpose
The DISPLAY EE command provides information about Enterprise Extender. This
command has various formats providing general Enterprise Extender information,
as well as detailed connection throughput statistics.
Operands
HOSTNAME
Filter used to limit the scope of the diagnostic scan to Enterprise Extender
connections specified by either the local host name, the remote host name, or
both.
Rule: The remote_hostname value is not always available for use by this
command. The remote_hostname value is only available for use by a host when
it initiates the connection (dial-out) to the remote EE partner. For a predefined
EE connection (non-VRN), which is the dial-in side of the connection, the
remote_hostname value is not available for use by this command. For a VRN EE
connection, which is the dial-in side of the connection, the remote_hostname
value is available for use after a dial-out is attempted to the remote EE partner.
A new session request, initiated from that EE endpoint, must cause the dial to
occur to the partner EE endpoint. At that time, the remote_hostname value is
resolved, the existing EE connection is found and is used for the session, and
that remote host name becomes available for use by this display command.
HOSTNAME=local_hostname
Limits the scope of the diagnostic scan to Enterprise Extender connections
that have a local host name of local_hostname.
Result: When the DISPLAY EE command is issued with only a
local_hostname, the output will contain aggregate totals comprised of all
active EE connections associated with the local_hostname.
Tip: Code either a remote HOSTNAME or remote IPADDR to further
refine the scope of the DISPLAY EE command.
HOSTNAME=(,remote_hostname)
Limits the scope of the diagnostic scan to Enterprise Extender connections,
which have a remote host name of remote_hostname.
Tip: Code either a local HOSTNAME or local IPADDR to further refine the
scope of the D EE command.
HOSTNAME=(local_hostname,remote_hostname)
Limits the scope of the diagnostic scan to Enterprise Extender connections,
which have an endpoint in this host, that have a local host name of
local_hostname and a remote host name of remote_hostname.
ID=name
Specifies the name of either a LINE or switched PU name which has an active
Enterprise Extender connection.
IPADDR
Filter used to limit the scope of the diagnostic scan to Enterprise Extender
connections specified by either the local IP address, remote IP address, or both.
The IP address accepts a fully qualified dotted decimal for IPv4–type address,
or colon-hexadecimal format for IPv6–type addresses.
IPADDR=local_ipaddr
Limits the scope of the diagnostic scan to Enterprise Extender connections
that have a local IP address of local_ipaddr.
Result: When the DISPLAY EE command is issued with only a
local_hostname, the output will contain aggregate totals comprised of all
active EE connections associated with the local_hostname.
Tip: Code either a remote IPADDR or remote HOSTNAME to further
refine the scope of the DISPLAY EE command.
IPADDR=(,remote_ipaddr)
Limits the scope of the diagnostic scan to Enterprise Extender connections
which have a remote IP address of remote_ipaddr.
Tip: Code either a local IPADDR or local HOSTNAME to further refine the
scope of the DISPLAY EE command.
IPADDR=(local_ipaddr,remote_ipaddr)
Limits the scope of the diagnostic scan to Enterprise Extender connections,
which have an endpoint in this host, that have a local IP address of
local_ipaddr and a remote IP address of remote_ipaddr.
LIST
Specifies the amount of detail the output will contain.
Guideline: If you specify the LIST operand without specifying a value, the
default of LIST=SUMMARY is assumed.
LIST=DETAIL
When specified on the standalone D NET, EE command, general Enterprise
Extender information will be displayed at the local IP address level, along
with the information provided in the summary format.
When specified on the D NET,EE,ID=name command, the output will
contain Enterprise Extender transmission statistics displayed at the port
priority level.
When specified on the D NET,EE command using the
IPADDR/HOSTNAME operands, the output is varied depending on the
command inputs.
Specifying MAX limits the display output. VTAM searches only for the number
of instances that you have specified. If fewer Enterprise Extender connections
are found than you have specified on MAX, VTAM displays only the
Enterprise Extender connections that are found.
Rules:
v Do not specify both remote_hostname and remote_ipaddr.
v Do not specify both local_hostname and a local_ipaddr.
v You must specify at least one local or one remote input when issuing the D
NET,EE command with the IPADDR/HOSTNAME operands. A local input is
either local_ipaddr or local_hostname. A remote input is either remote_ipaddr or
remote_hostname.
Examples
Displaying general Enterprise Extender information in summary format:
| D NET,EE
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EE
| IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
| IST1685I TCP/IP JOB NAME = TCPCS
| IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = XCAEE2
| IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
| IST2005I IPRESOLV = 0
| IST924I -------------------------------------------------------------
| IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
| IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
| IST2008I IPTOS VALUE = C0 C0 80 40 20
| IST924I -------------------------------------------------------------
| IST2017I TOTAL RTP PIPES = 4 LU-LU SESSIONS = 3
| IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 2
| IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
| IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
| IST2021I TOTAL ACTIVE EE CONNECTIONS = 2
| IST314I END
D NET,EE,HOSTNAME=VIPA16.SSCP1A.TCP.RALEIGH.IBM.COM
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EE
IST2002I ENTERPRISE EXTENDER AGGREGATE CONNECTION INFORMATION
IST924I -------------------------------------------------------------
IST1680I LOCAL IP ADDRESS 2000::67:1:1
IST1910I LOCAL HOSTNAME VIPA16.SSCP1A.TCP.RALEIGH.IBM.COM
IST2009I RTP PIPES = 7 LU-LU SESSIONS = 6
IST2010I INOPS DUE TO SRQRETRY EXPIRATION = 0
IST2013I AVAILABLE LINES FOR PREDEFINED EE CONNECTIONS = 0
IST2014I ACTIVE PREDEFINED EE CONNECTIONS = 1
IST2015I ACTIVE LOCAL VRN EE CONNECTIONS = 0
IST2016I ACTIVE GLOBAL VRN EE CONNECTIONS = 0
IST2044I TOTAL ACTIVE EE CONNECTIONS FOR LOCAL IPADDR = 1
IST924I -------------------------------------------------------------
IST2035I TOTALS FOR ALL PORT PRIORITIES
IST2036I NLPS SENT = 78877 ( 078K )
IST2037I BYTES SENT = 8671229 ( 008M )
IST2038I NLPS RETRANSMITTED = 0 ( 000K )
IST2039I BYTES RETRANSMITTED = 0 ( 000K )
IST2040I NLPS RECEIVED = 78923 ( 078K )
IST2041I BYTES RECEIVED = 7951928 ( 007M )
IST314I END
|
| DISPLAY EEDIAG command
| Display Enterprise Extender (EE) connections that meet or exceed a specified
| retransmission threshold:
| ,LIST=SUMMARY
| ,CLEAR=ALL
,CLEAR=REXMIT ,LIST=SUMMARY
,CLEAR=SRQRETRY ,LIST=DETAIL
| ,MAX=lesser_of_20_or_DSPLYDEF_start_option_value
|
,MAX= *
number_of_EE_connections
|
| EEDIAG command filters
| Tip: Specify the CLEAR operand on this command to clear the diagnostic counters.
| The REXMIT information is displayed before the diagnostic counters are cleared.
| ,LIST=SUMMARY ,MAX=lesser_of_20_or_DSPLYDEF_start_option_value
|
,LIST=SUMMARY ,MAX= *
,LIST=DETAIL number_of_EE_connections
|
| EEDIAG command filters
| The SRQRETRY=retries value indicates that only EE connections with LDLC signal
| retries equal to or exceeding the specified value should be displayed.
| Tip: Specify the CLEAR operand on this command to clear the diagnostic counters.
| The SRQRETRY information is displayed before the diagnostic counters are
| cleared.
| ,ID=name
|
| ,IPADDR= local_ipaddr
,HOSTNAME=(,remote_hostname)
(local_ipaddr)
,HOSTNAME=(,remote_hostname)
(local_ipaddr,remote_ipaddr)
(,remote_ipaddr)
|
| ,HOSTNAME= local_hostname
,IPADDR=(,remote_ipaddr)
(local_hostname)
,IPADDR=(,remote_ipaddr)
(local_hostname,remote_hostname)
(,remote_hostname)
|
| Abbreviations
|| Operand Abbreviation
| DISPLAY D
| CLEAR=ALL CLEAR
| HOSTNAME HN
| IPADDR IP
| LIST=DETAIL DETAIL or DET
| LIST=SUMMARY SUMMARY or SUM
|
| Purpose
| The DISPLAY EEDIAG command is used to display diagnostic information about
| one or more EE connections.
| The DISPLAY EEDIAG command enables filters on the command to limit the EE
| diagnostic scan to a subset of the overall EE connections.
| Tip: Specify filters to reduce the scope of the command to EE connections that are
| of interest. This eliminates unnecessary overhead while processing the display
| command.
| Operands
| CLEAR
| Specifies which diagnostic counters are to be cleared.
| CLEAR=ALL
| Clears both REXMIT and SRQRETRY diagnostic counters.
| CLEAR=REXMIT
| Clears only the REXMIT diagnostic counters.
| CLEAR=SRQRETRY
| Clears only the SRQRETRY diagnostic counters.
| Rule: The REXMIT and SRQRETRY operands limit the scope of the display
| output, but only the command filters (for example, ID, IPADDR, HOSTNAME)
| limit the scope of the CLEAR operand. If the command filters are not included
| on the D EEDIAG command, all EE connections are affected by the scope of
| this command. Otherwise, the scope of the D EEDIAG command is limited to
| the EE connections that match the values of the filters. For example, a local IP
| address (IPADDR) that is used by 500 EE connections can be specified on the
| command. The CLEAR=ALL option clears both the REXMIT and SRQRETRY
| counters for all 500 EE connections. However, only one of these EE connections
| might be experiencing retransmission problems. In this case, message IST2042I
| lists only one connection.
| HOSTNAME
| Filter used to limit the scope of the diagnostic scan to Enterprise Extender
| connections that are specified by either the local host name, the remote host
| name, or both.
| Rule: The remote_hostname value is not always available for use by this
| command. The remote_hostname value is available for use only by a host when
| it initiates the connection (dial-out) to the remote EE partner. For a predefined
| EE connection (non-connection network), which is the dial-in side of the
| connection, the remote_hostname value is not available for use by this command.
| For a virtual routing node (VRN) EE connection which is the dial-in side of the
| LIST=DETAIL
| When specified on the D NET,EEDIAG,REXMIT command, for connections
| meeting or exceeding the specified retransmission rate, the output contains
| Enterprise Extender retransmission rates displayed at the port priority
| level.
| When specified on the D NET,EEDIAG,SRQRETRY command, for
| connections meeting or exceeding the specified threshold, the output lists
| each SRQRETRY attempt and the count of LDLC signals that received
| responses on each retry attempt. For example, if an LDLC signal requires
| three retries prior to receiving a response, the display indicates one
| occurrence for the third SRQRETRY attempt.
| LIST=SUMMARY
| When specified on the D NET,EEDIAG,REXMIT command, for connections
| meeting or exceeding the specified retransmission rate, the output contains
| an Enterprise Extender retransmission rate comprised of the average of all
| port priorities.
| When specified on the D NET,EEDIAG,SRQRETRY command, for
| connections meeting or exceeding the specified threshold, the output lists
| only SRQRETRY attempts (and the count of LDLC signals that received
| responses on this retry attempt) that meet or exceed the specified
| threshold. That is, LIST=SUMMARY lists only SRQRETRY attempts that
| meet or exceed the specified threshold, while LIST=DETAIL lists all
| SRQRETRY attempts.
| Rule: If you specify REXMIT=xx with the LIST=SUMMARY option, the
| display provides an overall retransmission rate for all port priorities. It is
| possible that the retransmission rate displayed in message IST2068I, which
| is associated with all port priorities, is smaller than the rate specified by
| REXMIT=xx. This means that at least one of the EE port priorities for this
| EE connection is experiencing a retransmission rate that meets or exceeds
| the specified rate. In this case, the LIST=SUMMARY option displays the
| message groups for the specific port priorities that meet or exceed the
| specified rate, along with the summary of all port priorities.
| MAX
| Specifies the maximum number of Enterprise Extender connections 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_EE_connections
| Specifies the number of Enterprise Extender connections that VTAM
| displays for this command. The valid range of this keyword is from 1 up
| to and including the value of the DSPLYMAX start option value. The
| default for the MAX operand 20, or the value of the DSPLYDEF start
| option, whichever is less.
| Specifying the MAX operand limits the display output. If fewer Enterprise
| Extender connections are found than you have specified on the MAX operand,
| VTAM displays only the Enterprise Extender connections that are found.
| Tip: If the default value of 20 is not optimal for your environment, this value
| can be modified by altering the IBM-supplied USS table, ISTINCNO. See
| “Unformatted system services (USS) command syntax” on page 14 for details.
| Rule: If you specify the CLEAR operand and the display output is truncated
| because of the MAX operand value, processing continues to clear the
| diagnostic counters for all EE connections associated with the command filters.
| REXMIT=retransmission_rate_percentage
| The retransmission_rate_percentage value specifies that only EE connections that
| have a retransmission rate equal to or exceeding the specified percentage
| should be displayed. The REXMIT counters are maintained from the time the
| EE connection was activated, or since the last DISPLAY EEDIAG command
| that cleared the REXMIT counters for this EE connection was issued.
| The valid range is 0-99
| Result: When a value of 0 is specified for the REXMIT operand, all EE
| connections associated with the command filters, up to a maximum limited by
| the MAX operand, are displayed.
| Rule: The REXMIT and SRQRETRY operands limit the scope of the display
| output, but only the command filters (for example ID, IPADDR, and
| HOSTNAME) limit the scope of the CLEAR operand. If the command filters
| are not included on the DISPLAY EEDIAG command, all EE connections are
| affected by the scope of this command. Otherwise, the scope of the DISPLAY
| EEDIAG command is limited to the EE connections that match the values of
| the filters. For example, a local IP address (IPADDR) that is used by 500 EE
| connections can be specified on the command. The CLEAR=REXMIT option
| clears the REXMIT counters for all 500 EE connections. However, only one of
| these EE connections might be experiencing retransmission problems. In this
| case, message IST2042I lists only one connection.
| Refer to z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and
| Procedures for more information related to the DISPLAY EEDIAG command.
| SRQRETRY
| Specifies that only EE connections that have had an LDLC signal retransmitted
| a specified number of times or more prior to receiving a response should be
| displayed.
| SRQRETRY=*
| Specifies that the value of the SRQRETRY operand associated with the
| PORT keyword of the Enterprise Extender XCA major node is to be used.
| Only EE connections that have had an LDLC signal retransmitted the
| maximum number of times prior to receiving a response should be
| displayed.
| SRQRETRY=retries
| The retries value specifies that only EE connections with LDLC signal
| retries equal to or exceeding retries prior to receiving a response should be
| displayed.
| The upper limit of the range is the value of the SRQRETRY keyword that is
| associated with the Enterprise Extender XCA major node PORT definition
| statement. The SRQRETRY operand has a maximum value of 9.
| Rule: The REXMIT and SRQRETRY operands limit the scope of the display
| output, but only the command filters (for example ID, IPADDR, and
| HOSTNAME) limit the scope of the CLEAR operand. If the command filters
| are not included on the DISPLAY EEDIAG command, all EE connections are
| affected by the scope of this command. Otherwise, the scope of the DISPLAY
| EEDIAG command is limited to the EE connections that match the values of
| the filters. For example, a local IP address (IPADDR) that is used by 500 EE
| connections can be specified on the command. The CLEAR=SRQRETRY option
| clears the SRQRETRY counters for all 500 EE connections. However, only one
| of these EE connections might be experiencing retransmission problems. In this
| case, message IST2042I lists only one connection.
| Rules:
| v Do not specify both REXMIT and SRQRETRY.
| v Do not specify values for both remote_hostname and remote_ipaddr.
| v Do not specify values for both local_hostname and local_ipaddr.
| v You must specify at least one local or one remote input when issuing the D
| NET,EEDIAG command with either the IPADDR operand, the HOSTNAME
| operand, or both. A local input is either local_ipaddr or local_hostname. A
| remote input is either remote_ipaddr or remote_hostname.
| Examples
| Find all Enterprise Extender connections whose retransmission rates meet or
| exceed 5%, display the output in summary format, and clear all diagnostic
| counters after command processing is complete:
| D NET,EEDIAG,REXMIT=5,CLEAR,LIST=SUMMARY
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2065I ENTERPRISE EXTENDER CONNECTION REXMIT INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/19/04 AT 10:30:19
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9::67:1:1
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9::67:1:6
| IST1909I REMOTE HOSTNAME IP.SSCP2AV8
| IST2024I CONNECTED TO SWITCHED PU SWIP2A1
| IST924I -------------------------------------------------------------
| IST2035I TOTALS FOR ALL PORT PRIORITIES
| IST2036I NLPS SENT = 13647 ( 013K )
| IST2038I NLPS RETRANSMITTED = 1279 ( 001K )
| IST2068I NLP RETRANSMIT RATE = 9%
| IST2069I REXMIT COUNTERS LAST CLEARED ON 08/19/04 AT 10:27:18
| IST2071I ALL DIAGNOSTIC COUNTERS CLEARED FOR 3 EE CONNECTIONS
| IST2042I 1 OF 1 EE CONNECTIONS DISPLAYED
| IST314I END
| Display the Enterprise Extender connection that is identified by the LINE name in
| summary format when its retransmission rate meets or exceeds 5%:
| D NET,EEDIAG,REXMIT=5,ID=LNEE1000,LIST=SUMMARY
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2065I ENTERPRISE EXTENDER CONNECTION REXMIT INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/19/04 AT 10:30:19
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9::67:1:1
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9::67:1:6
| IST1909I REMOTE HOSTNAME IP.SSCP2AV8
| IST2024I CONNECTED TO SWITCHED PU CNV00009
| IST924I -------------------------------------------------------------
| IST2035I TOTALS FOR ALL PORT PRIORITIES
| IST2036I NLPS SENT = 13647 ( 013K )
| IST2038I NLPS RETRANSMITTED = 1279 ( 001K )
| IST2068I NLP RETRANSMIT RATE = 9%
| IST2069I REXMIT COUNTERS LAST CLEARED ON 08/19/04 AT 10:27:18
| IST2042I 1 OF 1 EE CONNECTIONS DISPLAYED
| IST314I END
| Find all Enterprise Extender connections using local IP address 9.67.1.4 whose
| retransmission rates meet or exceed 20%. Present the display in summary format
| and clear all diagnostic counters for all EE connections that are affected by the
| scope of this command. This example demonstrates a case where the overall
| retransmission rate for all port priorities is less than the requested retransmission
| rate, but one of the port priorities exceeds the requested retransmission rate.
| D NET,EEDIAG,REXMIT=20,IP=9.67.1.4,CLEAR=ALL,LIST=SUMMARY
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2065I ENTERPRISE EXTENDER CONNECTION REXMIT INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/27/04 AT 13:30:42
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9.67.1.4
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9.67.1.3
| IST2024I CONNECTED TO SWITCHED PU CNV00003
| IST924I -------------------------------------------------------------
| IST2032I PORT PRIORITY = HIGH
| IST2036I NLPS SENT = 134 ( 000K )
| IST2038I NLPS RETRANSMITTED = 67 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 50%
| IST924I -------------------------------------------------------------
| IST2035I TOTALS FOR ALL PORT PRIORITIES
| IST2036I NLPS SENT = 590 ( 000K )
| Find all Enterprise Extender connections using local IP address 9.67.1.4 whose
| retransmission rates meet or exceed 20%. Present the display in detail and clear all
| diagnostic counters for all EE connections affected by the scope of this command.
| D NET,EEDIAG,REXMIT=20,IP=9.67.1.4,CLEAR,DET
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2065I ENTERPRISE EXTENDER CONNECTION REXMIT INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/27/04 AT 13:30:54
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9.67.1.4
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9.67.1.3
| IST2024I CONNECTED TO SWITCHED PU CNV00003
| IST924I -------------------------------------------------------------
| IST2030I PORT PRIORITY = SIGNAL
| IST2036I NLPS SENT = 22 ( 000K )
| IST2038I NLPS RETRANSMITTED = 0 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 0%
| IST924I -------------------------------------------------------------
| IST2031I PORT PRIORITY = NETWORK
| IST2036I NLPS SENT = 56 ( 000K )
| IST2038I NLPS RETRANSMITTED = 0 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 0%
| IST924I -------------------------------------------------------------
| IST2032I PORT PRIORITY = HIGH
| IST2036I NLPS SENT = 134 ( 000K )
| IST2038I NLPS RETRANSMITTED = 67 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 50%
| IST924I -------------------------------------------------------------
| IST2033I PORT PRIORITY = MEDIUM
| IST2036I NLPS SENT = 278 ( 000K )
| IST2038I NLPS RETRANSMITTED = 0 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 0%
| IST924I -------------------------------------------------------------
| IST2034I PORT PRIORITY = LOW
| IST2036I NLPS SENT = 100 ( 000K )
| IST2038I NLPS RETRANSMITTED = 1 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 1%
| IST924I -------------------------------------------------------------
| IST2035I TOTALS FOR ALL PORT PRIORITIES
| IST2036I NLPS SENT = 590 ( 000K )
| IST2038I NLPS RETRANSMITTED = 67 ( 000K )
| IST2068I NLP RETRANSMIT RATE = 11%
| IST2069I REXMIT COUNTERS LAST CLEARED ON 08/27/04 AT 13:30:42
| IST2071I ALL DIAGNOSTIC COUNTERS CLEARED FOR 3 EE CONNECTIONS
| IST2042I 1 OF 1 EE CONNECTIONS DISPLAYED
| IST314I END
| Find all Enterprise Extender connections to the host using remote host name
| IP.SSCP2AV7 that experienced LDLC retries of three or more attempts, and present
| the output in summary format.
| D NET,EEDIAG,SRQRETRY=3,HOSTNAME=(,IP.SSCP2AV7)
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2066I ENTERPRISE EXTENDER CONNECTION SRQRETRY INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/23/04 AT 21:00:01
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9.67.1.1
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9.67.1.4
| IST1909I REMOTE HOSTNAME IP.SSCP2AV7
| IST2024I CONNECTED TO SWITCHED PU CNV00006
| Find all Enterprise Extender connections that experienced LDLC retries of three or
| more attempts. Present the output in detailed format and clear the SRQRETRY
| diagnostic counters for all connections.
| D NET,EEDIAG,SRQRETRY=3,LIST=DETAIL,CLEAR=SRQRETRY
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = EEDIAG
| IST2066I ENTERPRISE EXTENDER CONNECTION SRQRETRY INFORMATION
| IST2067I EEDIAG DISPLAY ISSUED ON 08/23/04 AT 21:00:01
| IST924I -------------------------------------------------------------
| IST1680I LOCAL IP ADDRESS 9.67.1.1
| IST1910I LOCAL HOSTNAME IP.SSCP1AV6
| IST1680I REMOTE IP ADDRESS 9.67.1.4
| IST1909I REMOTE HOSTNAME IP.SSCP2AV7
| IST2024I CONNECTED TO SWITCHED PU CNV00006
| IST2074I SUCCESSFUL SRQRETRY ATTEMPT = 0 OCCURRENCES = 98
| IST2074I SUCCESSFUL SRQRETRY ATTEMPT = 1 OCCURRENCES = 5
| IST2074I SUCCESSFUL SRQRETRY ATTEMPT = 2 OCCURRENCES = 1
| IST2074I SUCCESSFUL SRQRETRY ATTEMPT = 3 OCCURRENCES = 1
| IST2070I SRQRETRY COUNTERS LAST CLEARED ON 08/23/04 AT 20:55:15
| IST2073I SRQRETRY COUNTERS CLEARED FOR 3 EE CONNECTIONS
| IST2042I 1 OF 1 EE CONNECTIONS DISPLAYED
| IST314I END
,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.
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 to the 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 z/OS 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
IST1454I 9 EXIT(S) DISPLAYED
IST314I END
,MAX=DSPLYDEF_start_option_value
,MAX= *
max_affinities
Purpose
The DISPLAY GRAFFIN command displays affinity information for generic
resources. Since affinities for TSO generic resources exist only temporarily during
TSO logon processing, DISPLAY GRAFFIN does not display affinities for sessions
with these types of resources.
Operands
LU
Specifies the name of the partner LU. The name can be a network-qualified
name.
Notes:
1. 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 11.
2. Specifying a wildcard name might degrade performance because VTAM
checks every application major node in the network.
GNAME
Specifies the generic resource name. The name can be a network-qualified
name.
Notes:
1. 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 11.
2. Specifying a wildcard name might degrade performance because VTAM
checks every application major node in the network.
MAX
Specifies the maximum number of affinities that VTAM displays for this
command.
MAX=*
Specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=max_affinities
Specifies the number of affinities 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 affinities are found than you have
specified on MAX, VTAM displays only the affinities that are found.
Resulting display
The resulting display shows the affinity values.
Examples
Displaying the affinity values:
d net,graffin,lu=netx.*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = GENERIC AFFINITY
IST1706I PARTNER NAME GENERIC RESOURCE MEMBER ATTRIBUTES
IST1707I NETX.LUA10027 NETA.GRCICS CICS1 -VG--V--
IST1707I NETX.LUAPPC55 NETA.MVSAPPC MVSAPPC1 -VG-MX--
IST1707I NETX.LUAPPC55 NETA.MVSAPPC MVSAPPC2 -VA-MX--
IST1707I NETX.LUA13039 NETA.GRIMS IMS01 PAG6-V--
IST1454I 4 AFFINITIES DISPLAYED FOR LU=netx.*
IST314I END
,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
,MAX= * ALL
number_of_resources ,SCOPE=
ACT
ACTONLY
ALL
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=ALL EVERY or E
SCOPE=INACT INACT or I
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET
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.
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 11.
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.
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
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
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
DISPLAY ID command
Display a resource:
,HPRDIAG=NO ,IDTYPE=RESOURCE
DISPLAY NET,ID=name
,HPRDIAG=YES ,IDTYPE= CDRM
CP
DIRECTRY
GENERIC
LUALIAS
RESOURCE
SHADOW
SSCP
USERVAR
XCFCP
,SCOPE=ONLY
,NETID=netid ALL
,SCOPE=
ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
ONLY
PENDING
RELSD
RESET
,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
RELSD
RESET
DISPLAY NET,ID=ipaddress,IDTYPE=IPADDR
Abbreviations
Operand Abbreviation
DISPLAY D
HPRDIAG=YES HPRDIAG=Y
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=RELSD RELSD
SCOPE=RESET RESET
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.
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.
128 z/OS V1R7.0 Comm Svr: SNA Operation
DISPLAY ID
Operands
HPRDIAG=YES
Specifies that additional HPR diagnostic information is to be displayed for the
Rapid Transport Protocol (RTP) physical unit.
The resource identified by the ID operand must be an RTP physical unit in this
host.
HPRDIAG=NO
Specifies that additional HPR diagnostic information is not to be displayed for
the Rapid Transport Protocol (RTP) physical unit. If specified, the resource
identified by the ID operand must be an RTP physical unit in this host.
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.
| For an APPN node, 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 (or SSCP name) of the other VTAM with IDTYPE=XCFCP
| For a pure subarea node, to display information about a dynamic XCF TRLE
| representing the connectivity to another VTAM node, you can specify one of
| the following:
| v The name of the TRLE
| v The SSCP name (or 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.
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 lists all the members
known by that generic resource name.
9. If the name is a TN3270 client IP address in dotted decimal format (for
example, ID=192.5.48.122) or in colon-hexadecimal format for IPv6
addresses and there is an associated z/OS Communications Server Telnet
server APPL, CDRSC, or LU minor node resource name, it is displayed.
The saving and displaying of the IP information for TN3270 clients is
controlled by the IPINFO start option. Refer to z/OS Communications Server:
SNA Resource Definition Reference for more information on the IPINFO start
option.
Note: The saving and displaying of the IP information for TN3270 clients
is controlled by the IPINFO start option. See z/OS Communications
Server: SNA Resource Definition Reference for more information.
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 z/OS
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:
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
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.
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=RELSD
Specifies that the information is to be displayed about all PUs in a RELSD
state within the specified major nodes.
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.
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.
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:
- Conventionally 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:
| - Conventionally defined CDRSCs
| - Model CDRSCs
| - Clone CDRSCs built from model CDRSC definitions
– 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
– 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
– For ID=transport resource list major node, its subordinate transport resource list
entries (TRLEs).
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 (conventionally defined and dynamic):
| - 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 section
| – For ID=model CDRSC minor node:
| - An indication that the CDRSC is a model
| - An indication of the current value of the DELETE parameter of the model
| CDRSC
| - For SCOPE=ONLY, an indication if no clone CDRSCs currently exist that
| were built from this model
| - For other values of SCOPE, a list of clone CDRSCs that have been built
| from this model that meet the SCOPE criteria, or an indication if no clone
| CDRSCs currently exist that were built from this model that meet the
| SCOPE criteria
| – For ID=clone CDRSC minor node:
| - An indication that the CDRSC is a clone
| - The name of the model CDRSC used to build the clone CDRSC
| - An indication of the current value of the DELETE parameter from the
| model CDRSC used to build this clone CDRSC
| - 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 previously
– 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
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
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 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
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 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
IST314I END
Displaying a GROUP associated with an XCA major node that defines Enterprise
Extender, where the GROUP definition uses only IPADDR to define the IPv4
connection:
d net,id=gpip,scope=all
IST097I DISPLAY ACCEPTED
IST075I NAME = GPIP, TYPE = LINE GROUP
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST231I XCA MAJOR NODE = XCAIP
IST1680I LOCAL IP ADDRESS 223.254.254.252
IST084I NETWORK RESOURCES:
IST089I LNIP1 TYPE = LINE , NEVAC
IST089I LNIP2 TYPE = LINE , NEVAC
IST314I END
Displaying a GROUP associated with an XCA major node that defines Enterprise
Extender, where the GROUP definition uses HOSTNAME to define the IPv6
connection:
d net,id=gpip6v,e
IST097I DISPLAY ACCEPTED
IST075I NAME = GPIP6V, TYPE = LINE GROUP
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST231I XCA MAJOR NODE = XCAIP1
IST1680I LOCAL IP ADDRESS 9::67.1.1
IST1910I LOCAL HOSTNAME VIPA26.SSCP1A.RALEIGH.IBM.COM
IST084I NETWORK RESOURCES:
IST089I LNGV6000 TYPE = LINE , NEVAC
IST089I LNGV6001 TYPE = LINE , NEVAC
IST314I END
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
IST1131 DEVICE = ILU/CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST228I ENCRYPTION = OPT, TYPE = TDES24
IST1563I CKEYNAME = NNCPA1 CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST171I ACTIVE SESSIONS = 0000000004, SESSION REQUESTS = 0000000004
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 EAABEEC3361D945B 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 an SSCP (CDRM) and adjacent CP (CDRSC) with the same name from
a network node:
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
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
IST228I ENCRYPTION = NONE, TYPE = DES
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:
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, TYPE = DES
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
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
IST1184I CPNAME = NETA.SSCP2A - NETSRVR = ***NA***
IST1044I ALSLIST = ISTAPNPU
IST082I DEVTYPE = INDEPENDENT LU / CDRSC
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST228I ENCRYPTION = NONE, TYPE = DES
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***
IST484I SUBAREA = ****NA****
IST1703I DESIRED LOCATE SIZE = 1K LAST LOCATE SIZE = 16K
IST314I END
IST206I SESSIONS:
IST634I NAME STATUS SID SEND RECV VR TP NETID
IST635I TSO20001 ACTIV-P F6ABEEC39DE3E239 0008 0010 0 0 NETA
IST314I END
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
Note: Independent LU L3A4956A is shown under two PUs because it has active
sessions through these PUs.
Tip: The REMOTE TCID shown on message IST1476I can be used to correlate a
local RTP PU name to the RTP PU name used by the remote (VTAM) partner RTP
node (shown on the IST1481I message) to represent the same RTP connection. To
determine the RTP PU name used by the remote (VTAM) partner RTP node, first
issue the above command on the local node and remember the REMOTE TCID
value from the IST1476I message. Then issue the DISPLAY RTPS,TCID=tcid
command on the remote (VTAM) partner RTP node using the REMOTE TCID
value from the prior display.
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 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 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.67.113.58
IST097I DISPLAY ACCEPTED
IST075I NAME = NETA.TCPM1001, TYPE = APPL 472
IST486I STATUS= ACT/S, DESIRED STATE= ACTIV
IST1447I REGISTRATION TYPE = CDSERVR
IST599I REAL NAME = NETA.TCPM1001
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=ISTINCLM USSTAB=***NA*** LOGTAB=***NA***
IST934I DLOGMOD=***NA*** USS LANGTAB=***NA***
IST1632I VPACING = 7
IST1938 APPC = YES
IST597I CAPABILITY-PLU ENABLED ,SLU ENABLED ,SESSION LIMIT 00000001
IST231I APPL MAJOR NODE = TCPAPPLS
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1500I STATE TRACE = OFF
IST271I JOBNAME = TCPCS, STEPNAME = TCPCS, DSPNAME = ISTD629B
IST228I ENCRYPTION = OPTIONAL, TYPE = DES
IST1563I CKEYNAME = TCPM1001 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 = 0 MAXIMUM = 0
IST1669I IPADDR..PORT 9.67.113.58..1029
IST171I ACTIVE SESSIONS = 0000000001, SESSION REQUESTS = 0000000000
IST314I END
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_modules
Abbreviations
Operand Abbreviation
DISPLAY D
MODULE MOD
Purpose
The DISPLAY INOPCODE command is used to determine the attributes for every
INOPCODE defined to VTAM or for every INOPCODE defined within a single
VTAM module.
Operands
MODULE=modulename
Specifies the name of the VTAM module for which the attributes are to be
displayed.
MAX
Specifies the maximum number of modules 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_modules
Specifies the number of modules 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 modules are found than you have
specified on MAX, VTAM displays only the modules that are found.
Resulting display
The resulting display lists the VTAM module name and two groups, those codes
for which the dump attribute is enabled, and those for which the dump attribute is
disabled.
Examples
Displaying INOPCODE for a single module:
d net,inopcode,module=isttsc8e,max=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = INOPCODE
IST1919I INOPCODE FOR MODULE ISTTSC8E:
IST1920I DUMP ENABLED:
IST1921I 002 003 004 005 006 007 008 009 010 011 012 013 100 101
IST1921I 102 103 200 201 202 205 206 207 208
IST1922I DUMP DISABLED:
IST1921I 001 203 204
IST314I END
Purpose
The DISPLAY INOPDUMP command is used to determine:
v The global status for INOPDUMP. The global status controls the INOPDUMP
function for resources that are not defined within a transport resource list entry
(TRLE). When a TRLE is activated, the global status is propagated to the newly
activated TRLE if the TRLE InOpDump status has not been explicitly set.
v Whether TRLE controlled resources are subject to INOPDUMP and, if so, the
TRLE names.
v Whether TRLEs subsequently activated, whose InOpDump status has not been
explicitly set, will be subject to INOPDUMP.
Resulting display
The resulting display shows:
v The global status for INOPDUMP
v The names of all TRL major nodes having at least one TRLE currently having
INOPDUMP set to ON.
v TRLEs that currently have INOPDUMP set to ON (TRLEs that currently have
INOPDUMP=OFF are not displayed)
Examples
Displaying INOPDUMP information:
d net,inopdump
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = INOPDUMP
IST1865I GLOBAL INOPDUMP = OFF
IST924I ------------------------------
IST1954I TRL MAJOR NODE = TRL1A
IST1866I TRLE = TRLE1A INOPDUMP = ON
IST1866I TRLE = TRLE1B INOPDUMP = ON
IST924I ------------------------------
IST1954I TRL MAJOR NODE = TRL1B
IST1866I TRLE = TRLE1F INOPDUMP = ON
IST314I END
( name )
,MAX=DSPLYDEF_start_option_value
,MAX= * ,OWNER= host_name
number_of_resources *NONE
,SCOPE=ALL
ALL ,USE= DEFINED
,SCOPE= SPARE
ACT
ACTONLY
ALL
IACTIVE
IINACT
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=ALL EVERY or E
SCOPE=INACT INACT or I
USE=DEFINED DEFINED
USE=SPARE SPARE
SCOPE=INACTONLY INACTONL
SCOPE=PENDING PEND
SCOPE=RESET RESET
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 11.
Attention: Specifying a wildcard name might degrade performance because
VTAM checks every NCP, channel-attachment, and XCA major node in the
network.
LIST
Specifies the level of detail to display.
LIST=COUNT
Displays only the number of resouces in each state, based on the filters
specified in the SCOPE, OWNER, and IDTYPE keywords.
LIST=ALL
Displays information about all resources, based on the filters specified in
the SCOPE, OWNER, and IDTYPE keywords.
MAX
Specifies the maximum number of resources that VTAM displays for this
command. This operand is ony 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 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.
SCOPE
Specifies the desired scope of the display.
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.
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
IST1454I 32 RESOURCE(S) DISPLAYED
IST314I END
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
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
IST1454I 55 RESOURCE(S) DISPLAYED FOR ID=A0362ZC
IST314I END
Displaying LIST=COUNT:
d net,lines,id=ncp3ab8,list=count
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = LINES
IST354I PU T4/5 MAJOR NODE = NCP3AB8
IST1747I SUMMARY OF STATE INFORMATION:
IST1748I RESET = 1 INACT = 67 ACTIV = 1
IST1454I 69 RESOURCE(S) DISPLAYED FOR ID=NCP3AB8
IST314I END
,SCOPE=ONLY
DISPLAY NET,LMTBL ,ID=appl_name ,TYPE=LUNAME
ALL
,SCOPE=
ONLY
ALL
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.
SCOPE
Specifies the desired scope of the display. SCOPE is valid only when
TYPE=LUNAME is 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 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
DISPLAY NET,LUGROUPS
,SCOPE=ONLY
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources
,SCOPE=ONLY
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources
,SCOPE=ONLY
,SCOPE= ONLY
,MAX=DSPLYDEF_start_option_value
ALL
,MAX= *
number_of_resources
,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
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 name
v Model LU group
v Model LU name
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.
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@ @
IST1454I 19 RESOURCE(S) DISPLAYED
IST314I END
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 Dynamic XCF local SNA major node (ISTLSXCF)
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
v Transport resource list
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.
190 z/OS V1R7.0 Comm Svr: SNA Operation
DISPLAY MAJNODES
MAX=number_of_resources
Specifies the number of active major nodes 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 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
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
Purpose
| The DISPLAY MODELS command provides information about model resources,
| excluding model applications and model CDRSCs.
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.
In addition, VTAM will use the Model XCF PU definition as the basis for defining
dynamic XCF PUs when establishing XCF connectivity.
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.
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
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 = REQD, TYPE = TDES24
IST1563I CKEYNAME = A03MMNLU CKEY = PRIMARY CERTIFY = NO
IST1552I MAC = NONE MACTYPE = NONE
IST314I END
,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
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
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
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. The name displayed here is the
name of an adjacent network node that this end node has most recently
determined to be a suitable network node server and with which this end node
has either established CP-CP sessions or is in the process of establishing CP-CP
sessions. At the time the DISPLAY NETSRVR command displays this name,
CP-CP sessions with this network node may or may not be fully active yet.
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 z/OS
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 ENBCAST = NO
IST924I ------------------------------------------------------------
IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
IST1253I NETA.SSCP1A SLUINIT = OPT ENBCAST = NO
IST924I ------------------------------------------------------------
IST1256I CURRENT NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = OPT ENBCAST = NO
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 ENBCAST = NO
IST924I ------------------------------------------------------------
IST1256I CURRENT NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = OPT ENBCAST = NO
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 ENBCAST = NO
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 ENBCAST = NO
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=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 ENBCAST = NO
IST924I ------------------------------------------------------------
IST1254I SERVER LIST PROCESSED ORDER = FIRST
IST924I ------------------------------------------------------------
IST1256I CURRENT NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = OPT ENBCAST = NO
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 ENBCAST = NO
IST924I ------------------------------------------------------------
IST1256I CURRENT NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
IST924I ------------------------------------------------------------
IST1677I PREFERRED NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
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 ENBCAST = NO
IST1253I NETA.SSCPCA SLUINIT = REQ ENBCAST = NO
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 ENBCAST = NO
IST1253I NETA.SSCPAA SLUINIT = REQ ENBCAST = NO
IST1253I NETC.SSCP9C SLUINIT = REQ ENBCAST = NO
IST1253I NETA.SSCPBA SLUINIT = OPT ENBCAST = NO
IST1253I NETA.SSCPCA SLUINIT = REQ ENBCAST = NO
IST1253I NETA.SSCPDA SLUINIT = OPT ENBCAST = NO
IST1253I NETA.SSCPEA SLUINIT = REQ ENBCAST = NO
IST924I ------------------------------------------------------------
IST1254I SERVER LIST PROCESSED ORDER = FIRST
IST924I ------------------------------------------------------------
IST1255I OTHER NETWORK NODES ALLOWED AS SERVERS
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
IST924I ------------------------------------------------------------
IST1256I CURRENT NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
IST924I ------------------------------------------------------------
IST1677I PREFERRED NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
IST314I END
Displaying a network node server list with two explicit entries and no nameless
entry using SCOPE=ALL. The primary network node server has been defined with
ENBCAST=NO; a backup-mode network node server (used to enable generic
resources with a network node server that is not attached to the same generic
resource structure) is defined with ENBCAST=YES. The primary network node
server is also defined as the preferred network node server.
d net,netsrvr,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = NETWORK NODE SERVER LIST
IST1252I DEFINED NETWORK NODE SEVER LIST, NAME = NNSL2B
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
IST1253I NETA.SSCPXX SLUINIT = REQ ENBCAST = YES
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 = REQ ENBCAST = NO
IST924I ------------------------------------------------------------
IST1677I PREFERRED NETWORK NODE SERVER
IST1253I NETA.SSCP1A SLUINIT = REQ ENBCAST = NO
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. For Enterprise Extender definitions, the remote partner’s IP address
and host name are also displayed.
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
IST1318I 1,C’SAMPLE’
IST1318I 20,C’1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890123456789
IST1319I 012345678901234567890’
IST314I END
,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 207, 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.
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
IST1454I 7 PATH(S) DISPLAYED
IST314I END
( 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.
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.
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
IST1454I 7 RESOURCE(S) DISPLAYED
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
IST1454I 24 RESOURCE(S) DISPLAYED FOR ID=A0362ZC
IST314I END
,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
,ORIGIN=ALL YES
,ORIGIN=subarea_pu_name
,ORIGIN=ALL
Notes:
1 When the BLOCKED operand is specified, the NETID of the host where the
command was entered is assumed, and specification of another NETID is not
permitted.
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.
BLOCKED
Displays the blocked Virtual Routes from the PU specified in ORIGIN for
all destination Subarea combinations known to VTAM through its current
PATH table.
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 BLOCKED, ER nor the VR operands
can be specified.
DESTSUB=subarea_number
Specifies the subarea address of the destination subarea of the routes to be
displayed.
The BLOCKED and DESTSUB operands are mutually exclusive.
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 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 BLOCKED, 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 BLOCKED, COSNAME nor the VR operands
can be specified.
If COSNAME, ER, or VR options are not specified, then 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 BLOCKED, COSNAME, nor the ER operands
may be specified.
HELD
Displays the held virtual routes for the virtual routes that originate in VTAM.
When this command is used, no other keywords are permitted. The NETID
and ORIGIN of the host where the command was entered is assumed.
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.
When the BLOCKED operand is specified, the NETID of the host where the
command was entered is assumed and specification of another NETID is not
permitted.
ORIGIN=ALL
Used with the BLOCKED operand. Specifies that all PU type 4 and 5 nodes
that serve as an origin of a route should be checked for blocked Virtual Routes.
As in the case where the subarea_pu_name is specified, VTAM must have an
SSCP-PU session with this node to forward a route display request to the node.
Warning: The use of this operand may have a significant performance impact
depending on the number of NCPs and destination subareas in the network.
Therefore, it is recommended that this operand only be used when the
diagnostic advantage is preferred over the performance impact.
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
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 blocked virtual routes from one origin with no blocked routes found:
d net,route,blocked,origin=ISTPUS
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = BLOCKED VIRTUAL ROUTES
IST172I NO BLOCKED VIRTUAL ROUTE
IST314I END
( name )
,MAX=DSPLYDEF_start_option_value
,MAJNODE=nodename ,MAX= *
number_of_resources
,SCOPE=ALL
ALL
,SCOPE=
ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RELSD
RESET
Notes:
1 Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand.
| ,IDTYPE=*
,IDTYPE= ADJCPS
ADJCPSEG
APPLCLN
APPLDYN
APPLMOD
APPLS
APPLSEG
CDRMS
CDRMSEG
CDRSCCLN
CDRSCMOD
CDRSCS
CDRSCSEG
CLSTRS
DLURS
GENERIC
GROUPS
LCLSNA
LCL3270
LINES
LINKSTA
LUGROUPS
MAJNODES
MODELSEG
PUT45
SWSEG
TCPIPSEG
TERMS
TRLSEG
XCASEG
*
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=RELSD RELSD
SCOPE=RESET RESET
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 11.
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 11.
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 an asterisk (*) or APPLS, those model application
program names appear in your display output. In addition, any
dynamic application programs built from those model application
program definitions also appear in your display output.
| If model CDRSC definition names match the pattern you specify on the
| ID operand when IDTYPE specifies an asterisk (*) or CDRSCS, those
| model CDRSCs appear in your display output. In addition, any clone
| CDRSCs built from those model CDRSCs also appear in your display
| output.
| and model resources (APPLs or CDRSCs) 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* ACTIV MODEL CDRSC CDRSC1A
| IST1418I NETA APPLQ? CONCT MODEL APPL APPL1A
| IST1418I NETA APPL1 ACT/S APPL APPL1A
| IST1418I NETA APPLA01 ACTIV CLONE CDRSC CDRSC1A
| IST1418I NETA APPLQ1 ACTIV DYNAMIC APPL APPL1A
| IST1454I 5 RESOURCE(S) DISPLAYED FOR ID=APPL*
| IST314I END
IDTYPE=CDRMS
Displays only cross-domain resource managers known to this host
processor.
IDTYPE=CDRMSEG
Displays only CDRM major nodes.
| IDTYPE=CDRSCCLN
| Displays only clone cross-domain resources known to this domain.
| IDTYPE=CDRSCMOD
| Displays only model cross-domain resources known to this domain.
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=DLURS
Displays only dependent LU requesters (DLURs).
IDTYPE=GENERIC
| Displays only generic resources.
| GENERIC USERVAR in the TYPE column of message IST1418I indicates
| that a USERVAR representation of the generic resource exists locally on the
| host where the display was issued. You can use this information to
| determine whether you should issue a MODIFY GR,OPTION=DELETE
| command on a given host when trying to delete a generic resource from
| the sysplex.
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.
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 11.
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.
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).
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=RELSD
Specifies that the information is to be displayed about all PUs in a RELSD
state within the specified major nodes.
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
Results:
v 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 If model CDRSCs are included in the display, any clone CDRSCs that were built
| from those models that have been deleted are not displayed. Clone CDRSCs can
| exist in the inactive state, but whether they do or not is governed by the value
| of the DELETE operand that was on the model CDRSC at the time of the
| inactivation of the clone CDRSC or the value of the DELETE parameter that was
| on the VARY INACT operator command.
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
| IST1418I NETA APPL1 ACT/S APPL APPL1A
| IST1418I NETA APPL8 ACTIV--S-- CDRSC CDRSC1A
| IST1418I NETA APPLAA1 ACTIV CDRSC CDRSC1A
| IST1418I NETA APPLA01 ACTIV DYNAMIC APPL APPL1A
| IST1418I NETA APPLQ1 ACTIV 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, model CDRSCs,
| and any clone resources that were 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 DYNAMIC APPL APPL1A
| IST1418I NETA APPLA01 ACTIV DYNAMIC APPL APPL1A
| IST1418I NETA APPLAA* ACTIV MODEL CDRSC CDRSC1A
| IST1418I NETA APPLAA1 ACTIV CLONE 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 DYNAMIC APPL APPL1A
| IST1418I NETA APPLA01 ACTIV 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
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
| Displaying all generic resources known locally (type GENERIC USERVAR) and in
| the sysplex (type GENERIC RESOURCE):
| d net,rsclist,id=*,idtype=generic
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = RSCLIST
| IST1417I NETID NAME STATUS TYPE MAJNODE
| IST1418I NETA GRAPPL INACT GENERIC RESOURCE **NA**
| IST1418I NETA GRAPPL *NA* GENERIC USERVAR **NA**
,CONGEST=ALL
,CONGEST= YES ,FIRSTCP=name ,FIRSTTG=number
NO
ALL
,LIST=DETAIL
,TEST=NO ,LIST=SUMMARY
,ID=name ,LIST=DETAIL
,TCID=tcid ,TEST= YES
NO
,MAX=DSPLYDEF_start_option_value ,STALL=ALL
,MAX= * ,STALL= YES
number_of_resources NO
ALL
,SWITCH=ALL
,SWITCH= YES
NO
ALL
Abbreviations
|| Operand Abbreviation
| DISPLAY D
| LIST=DETAIL DETAIL or DET
| LIST=SUMMARY SUMMARY or SUM
|
Purpose
The DISPLAY RTPS command displays information concerning HPR pipes
terminating or originating in the host. The following keywords can be used to limit
the display information.
Operands
ALSNAME=name
Specifies the name of an Adjacent Link Station in this node that the HPR pipe
goes over.
APPNCOS=name
Specifies the name of a Class of Service (CoS) used to establish the HPR pipe.
CONGEST
Specifies whether the display should be restricted.
CONGEST=YES
Displays only pipes that are congested.
CONGEST=NO
Displays only pipes that are not congested.
CONGEST=ALL
Displays all pipes. This is the default value.
CPNAME=name
Specifies the name of a CP that is at the other end of the HPR pipe. The name
may be network qualified. If a network identifier is omitted, the host network
identifier is assumed.
You can specify * as the name portion of a network-qualified name. The * is
useful for displaying only HPR pipes whose other end is in a particular
network. To use the * for the name, you must explicitly specify the netid in the
form netid.* (for example, NETA.*). The capability of specifying netid.* for this
value is not affected by the coding of the DSPLYWLD start option.
FIRSTCP=name
Specifies the name of a CP that is at the other end of the first hop of the HPR
pipe. The name may be network qualified. If a network identifier is omitted,
the host network identifier is assumed.
You can specify * as the name portion of a network-qualified name. The * is
useful for displaying HPR pipes that have a first hop into a particular network.
To use the * for the name, you must explicitly specify the netid, in the form
netid.* (for example, NETA.*). The capability of specifying netid.* for this value
is not affected by the coding of the DSPLYWLD start option.
FIRSTTG=number
Specifies the TG number of the first hop of the HPR pipe. When used in
conjunction with FIRSTCP, a unique hop can be identified. The valid range for
this keyword is 0-255.
ID=name
Specifies the name of an RTP PU in this node.
| LIST
| Specifies the amount of detail the output contains.
| LIST=DETAIL
| Provides detailed information for each RTP pipe that matches the scope of
| the display command.
| LIST=SUMMARY
| Provides a condensed format of the RTP pipe information that matches the
| scope of the display command.
MAX
Specifies the maximum number of HPR pipes 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 HPR pipes to display for this command. The valid
| range of this keyword is 1–value of the DSPLYMAX start option. The
| default is the value specified for the DSPLYDEF start option.
| Specifying the MAX operand 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 HPR pipes are found than you
| have specified on the MAX operand, VTAM displays only the HPR pipes
| that are found.
STALL
Specifies whether the display should be restricted.
STALL=YES
Displays only pipes whose data flow is stalled.
STALL=NO
Displays only pipes whose data flow is normal.
STALL=ALL
Displays all pipes. This is the default value.
SWITCH
Specifies whether the display should be restricted.
SWITCH=YES
Displays only pipes in the midst of a path switch.
SWITCH=NO
Displays only pipes not in the midst of a path switch.
SWITCH=ALL
Displays all pipes. This is the default value.
TCID=tcid
Specifies the local transport connection identifier (TCID) for an RTP PU.
Tip: The TCID operand can be used to correlate a local RTP PU name to the
RTP PU name used by the remote (VTAM) partner RTP node to represent the
same RTP connection. To determine the RTP PU name used by the remote
(VTAM) partner RTP node, use the DISPLAY ID=rtp_pu_name command on
the local node to display the local RTP PU, and remember the REMOTE TCID
value that is displayed at the end of the IST1476I message. Then, from the
remote (VTAM) partner RTP node (shown on the IST1481I message in the prior
display), issue the DISPLAY RTPS,TCID=tcid command using the REMOTE
TCID value obtained from the prior display.
TEST
Specifies whether an HPR route test is to be performed.
TEST is only valid if the ID operand or the TCID operand is also specified and
if the resource identified by the ID or TCID operand is an RTP PU in this
node.
TEST=YES
Specifies that VTAM is to perform an HPR route test for this RTP PU in
addition to displaying the RTP PU status.
The HPR route test is initiated if the RTP PU is connected and is not path
switching. When the test results are received, they are provided to the
operator console in a separate message group from the initial display
output.
TEST=NO
Specifies that the RTP PU status is to be displayed but no HPR route test is
to be performed.
Examples
Displaying RTP pipe information:
| d net,rtps
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = RTPS
| IST1695I PU NAME CP NAME COSNAME SWITCH CONGEST STALL SESS
| IST1960I CNR00004 NETA.SSCP2A #INTER NO NO NO 5
| IST1960I CNR00003 NETA.SSCP2A RSETUP NO NO NO 0
| IST1960I CNR00002 NETA.SSCP2A CPSVCMG NO NO NO 1
| IST1960I CNR00001 NETA.SSCP2A CPSVCMG NO NO NO 1
| IST2084I 4 OF 4 MATCHING RTP PIPES DISPLAYED
| IST314I END
Initiating an HPR Route Test and displaying the results using the TEST operand:
| d net,rtps,id=cnr00004,test=yes
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = RTPS
| IST1695I PU NAME CP NAME COSNAME SWITCH CONGEST STALL SESS
| IST1960I CNR00004 NETA.SSCP2A #INTER NO NO NO 1
| IST1786I HPR ROUTE TEST INITIATED FOR RTP PU
| IST2084I 1 OF 1 MATCHING RTP PIPES DISPLAYED
| IST314I END
| IST1787I HPR ROUTE TEST RESULTS FOR RTP PU CNR00004
| IST1788I NODE CP NAME TG NUMBER PARTNER CP NAME INTERNODAL TIME
| IST1789I (MILLISECONDS)
| IST1790I NETA.SSCP1A 21 NETA.SSCP2A 1
| IST1792I TOTAL RTP TRAVERSAL TIME 1 MILLISECONDS
| IST314I END
| Displaying the HPR pipes with a first hop to SSCP2A in summary format:
| d net,rtps,firstcp=neta.sscp2a,list=summary
| IST097I DISPLAY ACCEPTED
| IST350I DISPLAY TYPE = RTPS
| IST2075I DISPLAY RTPS SUMMARY INFORMATION
| IST2076I TOTAL MATCHING PIPES = 5
| IST2077I CPSVCMG PIPES = 2
| IST2078I RSETUP PIPES = 1
| IST2079I LU-LU PIPES = 2
| IST2080I PATH SWITCHING PIPES = 0
| IST2081I CONGESTED PIPES = 0
| IST2082I STALLED PIPES = 0
| IST2083I SESSIONS = 4
| IST314I END
|
Abbreviations
Operand Abbreviation
DISPLAY D
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
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
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:
MAX operand:
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
,PATHINFO=YES
DISPLAY NET,SESSIONS ,SID=session_id
,PATHINFO= NO
YES
Abbreviations
Operand Abbreviation
DISPLAY D
PATHINFO=YES PATH
SCOPE=ACT ACT or A
SCOPE=ALL EVERY or E
SCOPE=PENDING SCOPE=PEND or PEND
SESSIONS SESSION
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 z/OS 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.
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
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).
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’
| IST2064I PLU TO SLU RU SIZE = 65535 SLU TO PLU RU SIZE = 65535
| 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
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
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
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
Format
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.
(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.
(3)
,TYPE=SUBAREA
(2)
,TYPE=APPN
(1)
,TYPE=ALL
DISPLAY NET,SRCHINFO ,SID=session_identifier
,TYPE= ALL
APPN
SUBAREA
242 z/OS V1R7.0 Comm Svr: 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.
Operand Abbreviation
DISPLAY D
SID PCID
Purpose
The DISPLAY SRCHINFO command displays information about outstanding
APPN and subarea search requests.
Parameters
DLU=lu_name
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 11.
FROMCP=cp_name
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.
You can specify wildcard values for this operand. For more information about
using wildcards, see “Using wildcard names” on page 11.
FROMSSCP=sscp_name
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 11.
LIST
Specifies the level of detail to display.
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=lu_name
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 11.
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=lu_name
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 11.
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.
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=lu_name
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 11.
SID=session_identifier
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=cp_name
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 11.
TOSSCP=sscp_name
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 11.
TYPE
Identifies the type of information desired.
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.
Results
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
( name )
,MAX=DSPLYDEF_start_option_value ,SCOPE=ALL
,MAX= * ALL
number_of_resources ,SCOPE=
ACT
ACTONLY
ACTSESS
ALL
CONCT
INACT
INACTONLY
PENDING
RELSD
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=RELSD RELSD
SCOPE=RESET RESET
Purpose
The DISPLAY STATIONS command displays the status of all cross-subarea link
stations for active major nodes.
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 11.
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.
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.
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=RELSD
Specifies that the information is to be displayed about all PUs in a RELSD
state within the specified major nodes (or within all NCP, local SNA, and
switched major nodes if the ID operand is omitted).
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
Examples
Displaying a specific cross-subarea link station:
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
IST1454I 1 STATIONS(S) DISPLAYED FOR ID=A31P04A
IST314I END
,MAX=DSPLYDEF_start_option_value
DISPLAY NET,STATS ,TYPE=VTAM
, MAX = *
NUM number_of_resources
,STRNAME=STRGR_start_option_value
,STRNAME= structure_name
*
EZBDVIPA
Entry Options
EZBEPORT
Entry Options
Entry Options:
,DVIPA=dvipa_address
,LIST=list_number
,FROM=1
,LIST=ALL
,FROM=starting_list_number
Scope Options:
,SCOPE=ONLY
,SCOPE= ALL
ONLY
Max Options:
,MAX=DSPLYDEF_start_option_value
, MAX = *
NUM number_of_lines
Abbreviations
Operand Abbreviation
DISPLAY D
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE or N
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 z/OS Communications Server: New Function
Summary 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 z/OS
Communications Server: New Function Summary.
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.
More specifically, for each claimed list, the output will display:
v The list number
v The DVIPA address
v The stack name (job name) and system name of the owning TCP stack
v The number of entries in the list
v For a list that is not being used for sequence number tracking, the takeover or
giveback count
v For a list that is used for sequence number tracking, the next available sequence
number is displayed.
A claimed list is one which has been associated with a DVIPA address and assigned
an owning TCP stack.
Base your choice on the following conditions. If all claimed lists in the structure
are displayed, the sum of the number of entries of all the lists will be one less than
the current number of entries shown in message IST1377I. This is because list 0,
which is used for structure maintenance, is never displayed.
You can now perform the steps to display a specific claimed list.
More specifically, for each claimed list (that is, a list associated to a DVIPA), the
output will display:
v The list number
v The DVIPA address
v The number of assigned ephemeral ports
v For each TCPIP stack associated with the DVIPA, the stack name (job name),
system name of that TCP stack, and the number of ephemeral ports assigned to
that stack
You can now perform the steps to display a specific claimed list.
Operands
DVIPA
Specifies a DVIPA address in dotted decimal format. All list headers pertaining
to this DVIPA will be displayed.
FROM
Indicates the starting list number at which the search for claimed lists to be
displayed begins. Valid only when LIST=ALL is specified.
LIST
Specifies the list number to display. If LIST=ALL is specified, the FROM
keyword may be used to indicate where to begin searching for claimed lists.
MAX
Specifies the maximum number of output lines that VTAM displays for this
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.
v For TYPE=CFS with STRNAME=EZBDVIPA specified and either DVIPA or LIST
specified, information on the contents of the list headers within the EZBDVIPA
structure, and, if SCOPE=ALL is specified, the list entry keys for each list entry
on the list.
v For TYPE=CFS with STRNAME=EZBEPORT specified and either DVIPA or LIST
specified, information on the number of ephemeral ports assigned for each
DVIPA plus each TCPIP stack associated with the DVIPA and the number of
ephemeral ports assigned to that stack. If SCOPE=ALL is specified, the set of
ephemeral ports assigned to each stack.
Examples
Displaying statistical information:
d net,stats,type=vtam
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=VTAM
IST1349I COMPONENT ID IS 5695-11701-10A
IST1345I ID VALUE DESCRIPTION
IST1227I 151 0 = DEPENDENT LU TOTAL FOR ISTPUS
IST1227I 151 32 = DEPENDENT LU TOTAL FOR NCP3AB8
IST1227I 11 0 = CHANNEL-TO-CHANNEL ATTACHMENTS
IST1227I 61 0 = SNA DATA COMPRESSION SESSIONS
IST1227I 63 27 = RECOVERABLE SESSIONS
IST1227I 56 1 = TOTAL APPL SESSIONS
IST1227I 58 0 = LU6.2 SESSIONS
IST1227I 60 1 = ICSF ENCRYPTION SERVICES
IST1227I 67 33 = PU STATEMENTS UNDER SW LINES
IST1227I 15 0 = SNA PU TOTAL MAXBFRU
IST1227I 21 0 = ICA DEVICES
IST1227I 51 49 = ACTIVE LU TOTAL
IST1227I 10 0 = TOTAL LINE STATEMENTS FOR XCA MAJOR NODES
IST1227I 14 0 = CA CLUSTER CONTROLLER TOTAL
Displaying the contents of the EZBDVIPA structure for all lists associated with
DVIPA addresses.
d net,stats,type=cfs,strname=ezbdvipa,list=all,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE EZBDVIPA
IST1371I STRUCTURE TYPE = LIST
IST1517I LIST HEADERS = 1024 - LOCK HEADERS = 0
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 6144K 10240K 60
IST1376I STORAGE ELEMENTS 32 16821 0
IST1377I LIST ENTRIES 4 1682 0
IST924I -------------------------------------------------------------
IST1834I LIST DVIPA SYSNAME TCPNAME #ENTRIES TGCOUNT SEQNUMBER
IST1835I 1 203.3.1.165
IST1836I MVS165 TCPCS3 0 1
IST1835I 3 203.1.1.11
IST1836I VIC011 TCPCS 2 2
IST1838I LIST ENTRY KEYS:
IST1839I 01000000000000010000000100000000
IST1839I 0200000000000001077A83D000000000
IST1835I 4 203.1.1.11
Displaying the contents of the EZBEPORT structure for all lists associated with
DVIPA addresses:
d net,stats,type=cfs,strname=ezbeport,list=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.A01N IS CONNECTED TO STRUCTURE EZBEPORT
IST1371I STRUCTURE TYPE = LIST
IST1517I LIST HEADERS = 1024 - LOCK HEADERS = 1024
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 6144K 10240K 60
IST1376I STORAGE ELEMENTS 32 16821 0
IST1377I LIST ENTRIES 8 1682 0
IST924I -------------------------------------------------------------
IST1823I LIST DVIPA SYSNAME TCPNAME # Assigned Ports
IST1824I 1 203.3.1.165 3
IST1825I VIC011 TCPCS2 2
IST1825I VIC011 TCPCS 0
IST1825I MVS165 TCPCS 1
IST1824I 4 203.1.1.11 5
IST1825I MVS165 TCPCS3 2
IST1825I VIC011 TCPCS 3
IST314I END
Displaying the contents of the EZBEPORT structure including a set of all the
ephemeral ports associated with each TCP stack for all lists associated with DVIPA
addresses:
d net,stats,type=cfs,strname=ezbeport,list=all,scope=all
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS
IST1370I NETA.SSCP1A IS CONNECTED TO STRUCTURE EZBEPORT
IST1797I STRUCTURE TYPE = LIST
IST1517I LIST HEADERS = 1024 - LOCK HEADERS = 1024
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 6144K 10240K 60
IST1376I STORAGE ELEMENTS 32 16821 0
IST1377I LIST ENTRIES 8 1682 0
IST924I -------------------------------------------------------------
IST1823I LIST DVIPA SYSNAME TCPNAME # Assigned Ports
IST1824I 1 203.3.1.165 3
IST1825I VIC011 TCPCS2 2
IST1826I PORTS: 1025 60234
IST1825I VIC011 TCPCS 0
IST1825I MVS165 TCPCS 1
IST1826I PORTS: 24051
IST1824I 4 203.1.1.11 12
IST1825I MVS165 TCPCS3 2
IST1826I PORTS: 11576 23000
IST1825I VIC011 TCPCS 10
IST1826I PORTS: 1027 2145 9815 20471 47611 48001
IST1827I 51225 60223 61427 63000
IST314I END
Displaying the contents of the EZBEPORT structure including a set of all the
ephemeral ports associated with the specific IPv6 DVIPA address specified:
d net,stats,type=cfs,strname=ezbeport,scope=all,dvipa=2003::38:1:1
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = STATS,TYPE=CFS 364
IST1370I NETA.SSCP1A IS CONNECTED TO STRUCTURE EZBEPORT
IST1797I STRUCTURE TYPE = LIST
IST1517I LIST HEADERS = 1024 - LOCK HEADERS = 1024
IST1373I STORAGE ELEMENT SIZE = 256
IST924I -------------------------------------------------------------
IST1374I CURRENT MAXIMUM PERCENT
IST1375I STRUCTURE SIZE 8192K 15104K *NA*
IST1376I STORAGE ELEMENTS 64 25711 0
IST1377I LIST ENTRIES 3 804 0
IST924I -------------------------------------------------------------
IST1823I LIST DVIPA SYSNAME TCPNAME # ASSIGNED PORTS
IST1824I 1 2003::38:1:1 64
IST1825I VIC038 TCPCS 64
IST1826I PORTS: 1024 1025 1026 1027 1028 1029
IST1827I 1030 1031 1032 1033 1034 1035
IST1827I 1036 1037 1038 1039 1040 1041
IST1827I 1042 1043 1044 1045 1046 1047
IST1827I 1048 1049 1050 1051 1052 1053
IST1827I 1054 1055 1056 1057 1058 1059
IST1827I 1060 1061 1062 1063 1064 1065
IST1827I 1066 1067 1068 1069 1070 1071
IST1827I 1072 1073 1074 1075 1076 1077
IST1827I 1078 1079 1080 1081 1082 1083
IST1827I 1084 1085 1086 1087
IST314I END
( appl_name )
,MAX=DSPLYDEF_start_option_value
, MAX = *
NUM number_of_resources
( appl_job_name )
,MAX=DSPLYDEF_start_option_value
, MAX = *
NUM number_of_resources
( data_space_name )
,MAX=DSPLYDEF_start_option_value
, MAX = *
NUM number_of_resources
,POOL=*
DISPLAY NET,STORUSE
,POOL= *
SUMMARY
,
( storage_pool_name )
,SUMMARY
,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.
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.
264 z/OS V1R7.0 Comm Svr: 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
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 z/OS Communications Server: SNA Network Implementation
Guide.
POOLTYPE
Specifies the type of pools for which storage information is to be displayed.
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, in CSA storage that have been currently
allocated from that storage pool:
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
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
Displaying storage usage for all applications, limiting output to four 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
,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
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.
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
IST1454I 14 RESOURCE(S) DISPLAYED
IST314I END
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
IST1454I 1 RESOURCE(S) DISPLAYED
IST314I END
( 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
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.
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 11.
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.
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
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
IST1454I 7 RESOURCE(S) DISPLAYED FOR ID=A50LOCAL
IST314I END
( 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 z/OS 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 11.
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.
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 z/OS 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
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
IST1454I 1 TGP(S) DISPLAYED FOR ID=SECURE
IST314I END
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
The DISPLAY TNSTAT (tuning statistics) command is used to determine:
v Whether tuning statistics data is directed to the system console.
v The time interval between tuning statistics summaries.
v The global setting for collecting tuning statistics.
v Whether TRLEs (TRLE controlled devices) are collecting statistics and if so,
which TRLEs.
v Whether devices subsequently activated will collect tuning statistics.
v The names of all TRL major nodes having at least one TRLE currently collecting
tuning statistics (ACTIVE)
Resulting display
The resulting display shows a typical response for a DISPLAY TNSTAT command.
Examples
Displaying a TNSTAT:
d net,tnstat
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TNSTAT
IST1450I GLOBAL TNSTAT = INACTIVE CNSL = NO TIME = 60
IST924I ------------------------------
IST1954I TRL MAJOR NODE = TRL1A
IST1451I TRLE = TRLE1A TNSTAT = ACTIVE
IST924I ------------------------------
IST1954I TRL MAJOR NODE = ISTTRL
IST1451I TRLE = IUTL0D00 TNSTAT = ACTIVE
IST314I END
,LIST=SUMMARY
DISPLAY NET,TOPO
,ID=*.*
(1)
,ID= name
*
Notes:
1 Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand.
,SCOPE=ACTIVITY
DISPLAY NET,TOPO ,LIST=TDUINFO
,SCOPE= RECENT
ACTIVITY
,NUM=10 ,CLEAR=NO
,NUM= number_of_entries ,CLEAR= YES
NO
,TGN=tg_number
,APPNCOS=cos_name
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_unreachable_partner_paths
,ID=*.*
(1) (2)
,ID= name
*
Notes:
1 Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand.
2 Name represents either an Enterprise Extender virtual node name or the name
of an end node connected to an Enterprise Extender virtual node.
Abbreviations
Operand Abbreviation
CLEAR=YES CLEAR
DISPLAY D
SCOPE=ACTIVITY ACTIVITY
SCOPR=RECENT RECENT
Purpose
The DISPLAY TOPO (topology) command displays information about the topology
of an APPN network.
This command is valid in all APPN-capable hosts. However, since end nodes and
migration data hosts do not receive topology updates (TDU) from other nodes,
only local topology resources and brief information about adjacent nodes can be
displayed at end nodes. For example, you can display detailed information about
the local end node and the TGs originated at that end nodes. The end node’s
topology database does not have information about any TGs originated at an
adjacent node to the end node itself. End nodes know the following information
about an adjacent node:
v Network-qualified CP name
v Node type (network node, end node or virtual node)
v Status of the CP-CP sessions between the local end node and the adjacent node
This command displays only the information that is found in the topology
database. Some resources might not be displayed in a network node or an
interchange node 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 nonnative nodes 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.
NN1 NN2
ENA
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.
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:
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.
CLEAR
Specifies whether the TDU statistics counters in the topology database are to
be reset after the current display operation. This allows users to control the
time interval in which TDU statistics data is to be collected between two D
NET,TOPO,LIST=TDUINFO commands.
CLEAR=NO
TDU statistics counters will not be reset.
CLEAR=YES
All TDU statistics counters will be reset.
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=UNRCHTIM
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 11.
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. LIST=BN is not valid in end nodes or migration data hosts.
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=CDSERVR is not valid in end nodes or
migration data hosts.
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=ICN is not valid in end nodes or migration data
hosts.
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=SUMMARY
Displays a summary, including how many nodes of each type are in the
database. LIST=SUMMARY is the default.
LIST=TDUINFO
Display information about the Topology Updates (TDUs) received by this
node. Since end nodes or migration data hosts never receive TDUs from
other nodes, TDUINFO is not valid in end nodes or migration data hosts.
LIST=UNRCHTIM
Displays unreachable partner information for an Enterprise Extender
connection network path. Unreachable partner information identifies paths
from one node through an Enterprise Extender virtual node to a second
node that is considered unreachable due to a connection network dial
failure or connection network link INOP condition. When this occurs, the
problem path is remembered for the period of time specified as the
UNRCHTIM for that connection network. During this period, the problem
path will not be considered for new sessions or HPR path switches.
MAX
Specifies the maximum number of unreachable partner paths that VTAM
displays for this command. This operand is only valid with LIST=UNRCHTIM.
MAX=*
Specifies that the value of the DSPLYMAX start option is used to limit the
display output.
MAX=number_of_unreachable_partner_paths
Specifies the number of unreachable partner paths 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 unreachable partner paths are found than you have specified on MAX,
VTAM displays only the unreachable partner paths that are found.
NUM
Specifies the number of TDU information entries to be displayed. The default
value is 10 and the maximum value is 100.
When SCOPE=RECENT, it specifies the number of entries for the most recently
received TDU to be displayed.
When SCOPE=ACTIVITY, it specifies the number of resource records to be
displayed.
ORIG=cp_name
Specifies the origin node (a control point) for a transmission group (TG).
SCOPE
Specifies the type of TDU information to be displayed.
SCOPE=RECENT
Display the information about the most recently received TDUs.
SCOPE=ACTIVITY
Display information about topology resources that are received in TDUs
most frequently.
TGN=tg_number
Specifies the transmission group number of the route to be displayed. The
number must be an integer in the range 1–255.
Resulting display
The resulting display depends on the kind of information that was requested.
v For a summary of the topology, VTAM end node displays:
– The number of adjacent nodes
– The number of network nodes with a direct connection to this node
– The number of end nodes with a direct connection to this node
– The time and date of the last topology garbage collection
v For brief information for the local end node, VTAM end node displays:
– The network-qualified name of the control point
– The node type
– The current weight of the node, if the Class of Service was specified
v For detailed information for the local end node, VTAM end node displays the
short form plus the following:
– An indication of whether the node is a migration data host
– The resource sequence number
– The number of days remaining until the node entry is removed from the
topology database
– An indication of the level of HPR support provided by the node
– The LOCATE message size supported by the end node
– All TGs owned by the end node
v For brief information for other specific nodes, VTAM end node displays:
– The network-qualified name of the control point
– The node type
– The status of CP-CP sessions between the local end node and the node
displayed
v For a summary of the topology, VTAM network node displays:
– The time and date of the last database checkpoint
– The time and date of the last topology garbage collection
– The time and date of the checkpoint dataset recovered during VTAM
initialization
– 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 network node 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 brief information for a specific node, VTAM end node displays:
– The network-qualified name of the control point
– The node type
v For detailed information for a specific node, VTAM network node displays the
short form plus the following:
– 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
– The LOCATE message size supported by the node
– The time and date when the last TDU about this node is received, and the
name of the CP that sent the TDU
– The time and date when TDU statistics counts on this resource were reset the
last time
– The number of TDUs about this resource sent
– The number of TDUs about this resource received
– The number of TDUs about this resource accepted
– The number of TDUs about this resource rejected
– The number of TDUs about this resource ignored
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 z/OS
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)
– The name of the physical unit if the origin node of the TG is the local node
– The time and date when the TDU statistics counts for the TG were reset
– The time and date when the last TDU about this TG is received, and the
name of the CP that sent the TDU
– The number of TDUs about this resource sent
– The number of TDUs about this resource received
– The number of TDUs about this resource accepted
– The number of TDUs about this resource rejected
– The number of TDUs about this resource ignored
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).
v For a display of an unreachable partner path through an Enterprise Extender
connection network, VTAM displays the following:
– The network-qualified name of the Enterprise Extender virtual node or the
origin end node of a path through an Enterprise Extender virtual node.
– If the unreachable partner information is for an Enterprise Extender virtual
node, VTAM displays the following:
- The network-qualified name of the origin network node on the path
through the connection network
- The network-qualified name of the unreachable partner (destination) on a
path through the connection network
| - The UNRCHTIM unreachable time value specified for the Enterprise
| Extender connection network
| - The time the unreachable time expires for the unreachable path through the
| connection network
– If the unreachable partner information is for the origin end node of an
unreachable path through an Enterprise Extender connection network, VTAM
displays the following:
- The network-qualified name of the virtual node on the path through the
connection network
- The network-qualified name of the unreachable partner (destination) on the
path through the connection network
| - The UNRCHTIM unreachable time value specified for the Enterprise
| Extender connection network
| - The time the unreachable time expires for the unreachable path through the
| connection network
Examples
Displaying TDU information about the most recently received TDUs:
d net,topo,list=tduinfo,scope=activity
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1780I TOPOLOGY RESOURCE RECORDS REFERENCED MOST FREQUENTLY
IST1777I CP NAME RSN DESTINATION CP TGN ACC REJ
IST1778I NETA.SSCPAA 6 NETA.SSCPVN 21 3 0
IST1778I NETA.SSCPAA 12 NETA.SSCP1A 21 3 0
IST1778I NETA.SSCPAA 8 ***NA*** NA 2 0
IST1778I NETA.SSCPVN 2 NETA.SSCP2A 21 2 0
IST1778I NETA.SSCP2A 2 NETA.SSCPVN 21 2 0
IST1778I NETA.SSCPAA 8 NETA.SSCP2A 21 1 0
Displaying information about topology resources that are received in TDUs most
frequently:
d net,topo,list=tduinfo,scope=recent
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1776I TDUS RECEIVED MOST RECENTLY
IST1777I CP NAME RSN DESTINATION CP TGN ACC REJ
IST1778I NETA.SSCPAA 8 NETA.SSCP2A 21 1 0
IST1778I NETA.SSCPAA 6 NETA.SSCPVN 21 3 0
IST1778I NETA.SSCPAA 12 NETA.SSCP1A 21 3 0
IST1778I NETA.SSCPAA 8 ***NA*** NA 2 0
IST1778I NETA.SSCPVN 2 NETA.SSCP2A 21 2 0
IST1778I NETA.SSCP2A 2 NETA.SSCPVN 21 2 0
IST1778I NETA.SSCPVN 0 NETA.SSCP2A 21 1 0
IST1778I NETA.SSCP2A 0 NETA.SSCPVN 21 1 0
IST1778I NETA.SSCPAA 2 NETA.SSCPVN 21 2 0
IST1778I NETA.SSCPAA 0 NETA.SSCPVN 21 1 0
IST1454I 10 TDUINFO(S) DISPLAYED
IST1779I TDUS RECEIVED BETWEEN 01/09/04 15:06:07 - 01/09/04 17:14:51
IST1770I TDU COUNTS RESET - 01/09/04 13:00:42
IST314I END
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 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
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
IST1769I LAST TDU RECEIVED - 12/21/00 08:35:44 FROM NETA.SSCPCA
IST1770I TDU COUNTS RESET - 12/21/00 08:30:45
IST1771I SENT - 10 RECEIVED - 4 ACCEPTED - 0
IST1772I REJECTED - 2 IGNORED - 2
IST314I END
Displaying all network nodes or interchange nodes that support any LOCATE
message size:
d net topo,list=nn,locsize=*
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1701I CP NAME LOCATE SIZE
IST1702I NETA.SSCP1A 16K
IST1702I NETA.SSCPBA 1K
IST1702I NETA.SSCP2A 16K
IST314I END
Displaying a list of end nodes (known to this NN) or interchange nodes that
support a specified LOCATE size:
d net,topo,list=en,locsize=1k
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1701I CP NAME LOCATE SIZE
IST1702I NETA.SSCP1A 1K
IST314I END
Displaying brief information for a specific node adjacent to the local end node:
d net,topo,id=sscp1a
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST1295I CP NAME NODETYPE ROUTERES CONGESTION CP-CP WEIGHT
IST1296I NETA.SSCP1A NN *NA* ***NA*** YES *NA*
IST314I END
Displaying unreachable partner information for an end node that is the origin of a
path through an Enterprise Extender connection network:
d net,topo,id=neta.endnode1,list=unrchtim
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TOPOLOGY
IST2057I UNREACHABLE PARTNER INFORMATION:
IST924I -------------------------------------------------------------
IST2053I ORIGIN END NODE - NETA.ENDNODE1
IST2054I VIRTUAL NODE PARTNER NODE UNRCHTIM EXPIRES
IST2055I NETA.VIRTUAL1 NETA.SSCPAA 3000S 00:04:15
IST2055I NETA.VIRTUAL2 NETA.SSCPAA 65535S 02:54:02
IST2055I NETA.VIRTUAL3 NETWORK1.TEST4444 65535S 02:32:34
IST924I -------------------------------------------------------------
IST314I END
IST924I -------------------------------------------------------------
IST2053I ORIGIN END NODE - NETA.ENDNODE1
IST2054I VIRTUAL NODE PARTNER NODE UNRCHTIM EXPIRES
IST2055I NETA.VIRTUAL1 NETA.SSCPAA 3000S 00:04:15
IST2055I NETB.VIRTUAL2 NETA.SSCPAA 65535S 02:54:02
IST2055I NETA.VIRTUAL3 NETWORK1.TEST4444 65535S 02:32:34
IST924I -------------------------------------------------------------
IST2053I ORIGIN END NODE - NETA.ENDNODEA
IST2054I VIRTUAL NODE PARTNER NODE UNRCHTIM EXPIRES
IST2055I NETA.VIRTUAL1 NETA.SSCPAA 300S 00:24:46
IST2055I NETB.VIRTUAL2 NETA.SSCPAA 300S 00:11:55
IST924I -------------------------------------------------------------
IST2051I VIRTUAL NODE BETWEEN ORIGIN AND PARTNER - NETB.GVRN2
IST2052I ORIGIN NODE PARTNER NODE UNRCHTIM EXPIRES
IST2055I NETA.SSCP1A NETA.SSCPAA 1500S 00:40:47
IST2055I NETA.TEST1233 NETWORKB.TEST5555 300S 00:02:33
IST2055I NETA.TEST1234 NETA.SSCPAA 300S 00:16:59
IST2055I NETA.TEST1 NETWORK1.TEST4444 14500S 01:15:24
IST924I -------------------------------------------------------------
IST314I END
,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.
,ID=VTAMBUF
DISPLAY NET,TRACES ,TYPE=SMS
( user_id )
Notes:
1 Depending on the value of the DSPLYWLD start option, wildcard values can
be used for this operand.
,TYPE=VTAM
DISPLAY NET,TRACES
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 11.
Guideline: Specifying a wildcard name might degrade performance because
VTAM checks every major or minor node in the network.
| 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 appear in your
| display output. In addition, any dynamic application programs built from
| those model application program definitions also appear in your display
| output. Similarly, any model CDRSCs and clone CDRSCs that match the
| pattern you specify on the ID operand appear in your display output. On
| message IST1041I, a model application program is identified as MODEL
| APPL, a dynamic (clone) application program is identified as DYNAMIC
| APPL, a model CDRSC is identified as MODEL CDRSC, and a clone CDRSC
| is identified as CLONE CDRSC
| For example, if you issue the command DISPLAY
| NET,TRACES,ID=APPL*,TYPE=NODES, and model application programs and
| model CDRSCs have been defined using names that match the pattern
| specified on the ID operand (APPL*), you 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
| IST924I --------------------------------------------------------
| IST075I NAME = TESTCDRS, TYPE = CDRSC SEGMENT
| IST1041I NETA.APPL2* MODEL CDRSC
| IST1042I BUF = ON - AMOUNT = PARTIAL - SAVED = NO
| IST1041I NETA.APPL2Q CLONE CDRSC
| 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.
| The name fields of the network-qualified names NETA.APPL1* and
| NETA.APPL2*, even though they contain a wildcard character, begin with
| APPL, followed by zero to four valid characters [an asterisk (*) and a
| question mark (?) are valid characters in an application program minor node
| name and CDRSC minor node name]. Therefore, they are included in the
| display output, as are the dynamic application program (NETA.APPL1Q)
| built from APPL1* and the clone CDRSC (NETA.APPL2Q) built from
| APPL2*.
See the “MODIFY TRACE command” on page 462 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 301
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 11.
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.
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 312.
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.
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=SMS
– TYPE=STATE
– TYPE=TSO,ID=*
– 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 SECAUTH ACCTING GWPATH XRF ADJSSCP
IST199I OPTIONS = ALIAS ALS REPL VRSEL HPRVRSEL HPRP_OLU HPRP_ANR
IST199I OPTIONS = HPRP_DLU END
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
,CONTROL=ALL
DISPLAY NET,TRL
,CONTROL= ALL
MPC
TCP
,ULPID=name
XCF
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
DISPLAY NET,TRL
,TRLMN= name
,
( name )
,MAX=DSPLYDEF_start_option_value
,MAX= *
number_of_resources
Abbreviations
Operand Abbreviation
DISPLAY D
Purpose
The DISPLAY TRL (transport resource list) command provides information about
the active TRL major nodes 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.
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 TRLE to be displayed.
TRLMN=trl_major_node_name
Specifies the name of one or more active TRL major nodes to be displayed.
ULPID=name
Specifies the name of a CS z/OS 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. The value of cp_name is the CP
| name or SSCP name of the other VTAM.
Resulting display
The resulting display shows:
v The name and status of all TRLEs in the active TRL major nodes 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 the READ,
WRITE, and (OSA-Express only) DATA subchannels. In addition, the following
information may be displayed:
– MPC level and usage (MPC header size, maximum MPC data size, inbound
data storage medium)
– Name of the CS z/OS upper-layer protocols (ULPs) using this TRLE
– OSA portname, OSA adapter number, and OSA microcode level
– I/O trace status
– The capability of the connection to perform channel I/O directly to or from
communications storage manager (CSM) buffers.
v For a dynamic TCP TRLE, or an exclusively owned TRLE, only one message
with a ULP ID will be issued, since there can only be one ULP using each of
these TRLEs. For an OSA-Express Adapter, one message with a ULP ID will be
issued for each datapath channel address used by a ULP. For other TRLEs, more
than one ULP ID message may be issued, depending on how many ULPs are
using the TRLE.
v The ULP ID will be the jobname for TCP/IP ULPs, the SNA PU name for
ANNC ULPs, and the XCA Major Node name for ATM or EE ULPs.
Examples
Displaying all TRL entries:
d net,trl
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = TRL
IST1954I TRL MAJOR NODE = ISTTRL
IST1314I TRLE = ISTT0001 STATUS = ACTIVE----E CONTROL = XCF
IST1454I 1 TRLE(S) DISPLAYED
IST924I ----------------------------------------------------------
IST1954I TRL MAJOR NODE = TRL1
IST1314I TRLE = TRL1A STATUS = ACTIVE CONTROL = MPC
IST1314I TRLE = TRL1B STATUS = NEVAC CONTROL = MPC
IST1454I 2 TRLE(S) DISPLAYED
IST924I ----------------------------------------------------------
IST1954I TRL MAJOR NODE = TRL2
IST1314I TRLE = TRL2A STATUS = NEVAC CONTROL = XCF
IST1314I TRLE = TRL2B STATUS = ACTIVE CONTROL = XCF
IST1454I 2 TRLE(S) DISPLAYED
IST314I END
d net,trl,trle=trle1a
IST097I DISPLAY ACCEPTED
IST075I NAME = TOC01N, TYPE = TRLE 701
IST1954I TRL MAJOR NODE = TRL1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES
IST1715I MPCLEVEL = HPDT MPCUSAGE = SHARE
IST1717I ULPID = AHHCPU7
IST1577I HEADER SIZE = 4092 DATA SIZE = 60 STORAGE = ***NA***
IST1221I WRITE DEV = 0CE6 STATUS = ACTIVE STATE = ONLINE
IST1221I WRITE DEV = 0CE7 STATUS = ACTIVE STATE = ONLINE
IST1221I WRITE DEV = 0CE8 STATUS = ACTIVE STATE = ONLINE
IST1221I WRITE DEV = 0CE9 STATUS = ACTIVE STATE = ONLINE
IST1577I HEADER SIZE = 4092 DATA SIZE = 60 STORAGE = DATASPACE
IST1221I READ DEV = 0CC6 STATUS = ACTIVE STATE = ONLINE
IST1221I READ DEV = 0CC7 STATUS = ACTIVE STATE = ONLINE
IST1221I READ DEV = 0CC8 STATUS = ACTIVE STATE = ONLINE
IST314I END
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 secoundary logical unit (SLU) the TSO user is using
v If the SLU is a Telnet client, the IP address, the IP port number, and (if it exists)
the DNS name
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
,MAX=DSPLYDEF_start_option_value
DISPLAY NET,USERVAR
,MAX= *
number_of_resources
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.
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.
Specifying MAX limits the display output. VTAM searches only for the
number of instances that you have specified. When that number is found,
Chapter 2. VTAM operator commands 313
DISPLAY USERVAR
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
IST1454I 2 USERVARS(S) DISPLAYED
IST314I END
,FORMAT=CURRENT
DISPLAY NET,VTAMOPTS
,FORMAT= CURRENT
COMPLETE
MODIFIED
,OPTION=*
,OPTION= *
(*)
option
,
( option )
,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
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.
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 DLURSAW DUPDEFS
DYNADJCP HOSTNAME HPR
HPRARB HPRNCPBF HPRPST
INITDB IOPURGE IPADDR
MAXLOCAT NETID NNSPREF
NODETYPE NUMTREES PSRETRY
PSWEIGHT RESUSAGE ROUTERES
SACONNS SAVERSCV SECLVLCP
SNVC SORDER SRCHRED
SRCOUNT SRTIMER SSCPNAME
SSEARCH TCPNAME UNRCHTIM
VERIFYCP VFYRED VFYREDTI
VRTG VRTGCPCP XCFINIT
FUNCTION=CONNECT
Displays the start options that affect connectivity. The start options
displayed using FUNCTION=CONNECT are:
FUNCTION=MESSAGES
Displays the start options that affect messages. The start options displayed
using FUNCTION=MESSAGES are:
FUNCTION=PERFTUNE
Displays the start options that affect performance and tuning. The start
options displayed using FUNCTION=PERFTUNE are:
FUNCTION=RECSTATS
Displays the start options that affect recording and statistics. The start
options displayed using FUNCTION=RECSTATS are:
FUNCTION=SECURITY
Displays the start options that affect session security. The start options
displayed using FUNCTION=SECURITY are:
FUNCTION=SESSCONT
Displays the start options that affect session control. The start options
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:
FUNCTION=TRACDUMP
Displays the start options that affect traces and dumps. The start options
displayed using FUNCTION=TRACDUMP are:
FUNCTION=VTAMINIT
Displays the start options that affect VTAM initialization. The start options
displayed using FUNCTION=VTAMINIT are:
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:
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
INOPCODE, PROMPT, NOPROMPT, LISTBKUP, and the trace and buffer pool
start options. The DISPLAY INOPCODE command can be used to display the
current dump attributes. The DISPLAY TRACES command and the DISPLAY
BFRUSE command can be used to display trace and buffer pool information.
See the z/OS 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.
See the z/OS 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
Examples
Displaying start options that have been modified:
d net,vtamopts,opt=(sscpid,dsplydef,cmpvtam,cpcp,tnstat,hostname),format=modified
IST097I DISPLAY ACCEPTED
IST1188I ACF/VTAM CSV2R10 STARTED AT 11:54:32 ON 03/23/00
IST1349I COMPONENT ID IS 5695-11701-10A
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 TNSTAT OFF CNSL,TIME=1 OPERATOR
IST924I ------------------------------------------------------------
IST19051 START OPTION = HOSTNAME
IST1906I CURRENT VALUE = NODENAME.NETID.REALLYLONGDOMAIN.COM
IST1907I ORIGINAL VALUE = NODENAME.NETID.SHORTDOMAIN.COM
IST1908I ORIGIN = OPERATOR
IST314I END
,LENGTH=32
,LENGTH=decimal_number_of_bytes
,XLENGTH=hex_number_of_bytes
DISPLAY NET,VTAMSTOR
,X
,NETADDR=( ,element_address )
subarea_address ,D
,X
,NETID=network_id
,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
Operand Abbreviation
XLENGTH XLEN
Purpose
The DISPLAY VTAMSTOR command displays storage contents associated with
VTAM modules and resources.
Operands
ADDRESS=storage_address
Specifies the address (in hexadecimal). The storage address must be in the
range of 0–7FFFFFFF.
LENGTH=decimal_number_of_bytes
Specifies the number of bytes in decimal to display. The valid range is 1–value
of DSPLYMAX multiplied by 16.
MODULE=module_name
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. The following notes apply to
subrarea_address and element_address:
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. If the value is greater than the host’s MXSUBNUM
start option, the command will be rejected.
element_address
Specifies the element portion of the network address. Leading zeros are
acceptable but not required. Acceptable values range from 0–FFFF in
hexadecimal; 0–65535 in decimal.
D Indicates the subarea and element addresses are specified in decimal.
X Indicates the subarea and element addresses are specified in hexadecimal.
Notes:
1. To display an Enhanced network address, you must incorporate the index
into either the subarea_address or the element_address. Leading zeros are
acceptable but not required. If omitted, the index defaults to 0. Acceptable
values are 1-1FA in hexadecimal and 1-506 in decimal.
2. To incorporate the index into either the subarea_address or the
element_address do the following:
v In hexadecimal, concatenate the index in front of the 2–byte subarea or
element. For example, subarea 2, index 1, element 3 can be entered as
NETADDR=(10002,3) or NETADDR=(2,10003).
v In decimal, multiply the index by 65536 and add it to the subarea or
element. For example, subarea 2, index 1, element 3 can be entered as
NETADDR=(65538,3,d) or NETADDR=(2,65539,d).
NETID=network_id
Specifies the network identifier. If omitted, the network identifier of the host is
used.
RESOURCE=resource_name
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.
| Tip: If you are specifying a model resource (APPL or CDRSC), you can use
| wildcard characters in the name you specify. The use of wildcard characters on
| the RESOURCE operand does not depend on the value of the DSPLYWLD start
| option.
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).
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 z/OS
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 z/OS 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
| For an APPN node, this displays the resource definition table entry (RDTE)
| 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 or SSCP name of the other VTAM. For a pure subarea node, this
| displays the RDTE of the dynamic XCF TRLE representing the connectivity
| to another VTAM node in the XCF group, when the RESOURCE operand
| specifies the CP name or SSCP name of the other VTAM.
XLENGTH=hex_number_of_bytes
Specifies the number of bytes in hexadecimal to display. The valid range is
1–value of DSPLYMAX multiplied by 16, converted to hexadecimal.
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=8756000,length=128
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = VTAMSTOR
IST1573I STORAGE DISPLAY BEGINS AT LOCATION 08756000
IST1574I -010 0881E120 00000000 E3406000 000C8010 *.A......T -.....
IST1574I +000 00000000 00000000 B376630A 68184202 *................
IST1574I +010 B3765E66 C27F6007 0878C580 0881DFE0 *..;.B"-...E..A..
IST1574I +020 D9C5D3E2 1A240000 08926B90 0886F010 *RELS.....K,..F0.
IST1574I +030 88F11578 00000000 0886F010 00000000 *H1.......F0.....
IST1574I +040 E4D72342 1A000000 006F6318 006F6320 *UP.......?...?..
IST1574I +050 006F6450 000000D4 04000004 00000000 *.?.&...M........
IST1574I +060 D9C5D3E2 1A150000 08926B90 08D631F0 *RELS.....K,..O.0
IST1574I +070 88DE40D8 00000000 006F6318 00000000 *H. Q.....?......
IST314I END
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 z/OS upper layer protocol (ULP) service access points (SAPs) will also not be
disrupted.
When normal HALT is issued for a VTAM, none of the sessions on that VTAM will
be able to be recovered using the MNPS function.
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.
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 z/OS 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
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.
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 570 for more
information on forced deactivation.)
This commands causes sessions to terminate. Multinode persistent sessions are not
recoverable.
| Rule: You must reply to any VTAM operator messages that are outstanding before
| HALT QUICK can complete.
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.
,NEWALS=adjacent_link_station_name
,OLDALS=adjacent_link_station_name
,NEWALS=adjacent_link_station_name ,OLDALS=adjacent_link_station_name
| Create a clone CDRSC or a dynamic CDRSC and add entry in adjacent link
| station list:
,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.
Operands
procname
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 or clone 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.
| Tip: 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 clone cross-domain resource or 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 and a clone CDRSC cannot be created from an active model
| CDRSC. If the independent LU already exists or if it is dynamically created
| (from a model CDRSC or in ISTCDRDY), 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 is added to the ALS list but it is not 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. The CDRSCTI start option has no affect on newly created
| clone CDRSCs; they remain active until some other action on them occurs,
| such as a VARY INACT operator command.
| 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.
| Tip: 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 ISTAPNPU as if it were any
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 z/OS Communications Server: SNA Network Implementation Guide for more
information on APING.
Operands
procname
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.
Purpose
The MODIFY APINGTP command allows you to change the number of APING
command transaction programs permitted to run concurrently for sending APING
requests to other nodes. The initial limit provided at startup is 10.
Operands
procname
The procedure name for the command. If procname in the START command is
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 is startname, startname must be specified for
procname.
INSTANCE
Specifies the number of APING transaction programs permitted to run
concurrently for sending APING requests to other nodes.
INSTANCE=UNLIMITED
Specifies that there is no limit to the number of transaction programs
permitted to run concurrently for sending APING requests to other nodes.
INSTANCE=value
Specifies the number of transaction programs permitted to run
concurrently for sending APING requests to other nodes. Values of 0–32763
are accepted.
Specifying INSTANCE=0 prevents sending APING requests to other nodes,
and a DISPLAY APING command will be rejected.
Abbreviations
Operand Abbreviation
MODIFY F
BUFFER BUF
Purpose
The MODIFY BFRUSE command allows you to dynamically change the total
amount of common service area (CSA) storage that VTAM is allowed to use for the
IO buffer pool. Refer to the z/OS Communications Server: SNA Resource Definition
Reference for information on the xpanlim parameter of IOBUF buffer pool start
option.
Notes:
1. This command can be used to increase the IO buffer pool expansion limit by
selecting a value greater than the current total storage used for the IO buffer
pool. It can also be used to set the value to 0, which removes the expansion
limit. This means that the IO buffer pool has no expansion limit. It will be set
to the current CSALIMIT value.
2. This command fails if a value of 0 is coded for the xpanno parameter for the
IOBUF operand at VTAM startup (indicating static buffering specified).
3. If the XPANLIM value is less than the current allocated total IO buffer pool
storage, the expansion limit will be set to the current allocated IO buffer pool
storage.
4. If the XPANLIM value is greater than the current CSALIMIT value, the
expansion limit will be set to the current CSALIMIT value.
Operands
procname
The procedure name for the command. If procname in the START command is
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.
BFRUSE
Specifies that the command is to modify a VTAM buffer pool value.
BUFFER=IOBUF | IO00 | IO
This parameter is optional, as the XPANLIM parameter applies only to the
IOBUF pool.
XPANLIM=value
Specifies the new total size for the IO buffer pool including the base allocation
and expansions.
Value can be specified in any of the following forms:
n or nk
The number of 1024-byte increments to be used. The value of n is rounded
up to the next multiple of 4.
qM
The number of 1 MB increments that are to be used.
Though the range for value is between 0 and 2097152 Kb, the valid range is
between the current pool allocation and the VTAM CSALIMIT value. If a value
is specified less than that currently in use (except 0), the current in-use value
will become the expansion limit. If a value is specified greater than the current
VTAM CSA limit, the expansion limit will be set to the VTAM CSA limit.
A value of 0 is also valid and is used to remove the IO buffer pool expansion
limit.
The current total IO buffer pool allocation is obtained by multiplying the Max
Total value from message IST923I by the BUFSIZE value in message IST920I. Note
that this is an approximate value, as the IO buffer size selected may result in
unused space in a 4K page. This unused space is added to the total space
calculation for expansion limit.
You can also determine if dynamic buffering is in effect for the IOBUF pool by
checking to see if the EXP INCREMENT field in message IST920I contains a
numeric value. (A value of *NA* indicates that xpanno=0 was coded on the IOBUF
start option at VTAM startup, and that static buffering is to be used.)
Examples
Modify vtam,bfruse,buf=iobuf,xpanlim=2400K
IST097I MODIFY ACCEPTED
IST495I XPANLIM HAS BEEN SET TO 2400K
IST223I MODIFY BFRUSE COMMAND COMPLETED
IST314I END
,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.
Operands
procname
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.
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.
340 z/OS V1R7.0 Comm Svr: SNA Operation
MODIFY CDRM
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 must be specified as a network-qualified name, if the CDRSC
represents a real cross network resource.
| Tip: If you are specifying a model CDRSC, you can use wildcard
| characters in the name you specify. The use of wildcard characters on the
| ID operand does not depend on the value of the DSPLYWLD start option.
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.
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.
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 489. For more information about the DIRTIME start option, see
the z/OS Communications Server: SNA Resource Definition Reference.
| When you issue this command for the topology database (TYPE=TOPO or
| TYPE=ALL) VTAM saves all network topology except non-native nodes, end
| nodes, and endpoint TGs.
Operands
procname
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.
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.
,DRAINL=NO
,LOGMODE=logon_mode_name ,LUNAME=lu_name
,DRAINL= NO
YES
,SNGSESLU=NO
,SNGSESLU= NO
YES
,DRAINL=NO ,DRAINR=NO
,NBRMODE=ALL
,DRAINL= NO ,DRAINR= NO
YES YES
,RESP=LOCAL ,SNGSESLU=NO
,RESP= LOCAL ,SNGSESLU= NO
REMOTE YES
,LOGMODE=logon_mode_name ,LUNAME=lu_name
,CONVSECL= NONE
CONV
ALREADYV
PERSISTV
AVPV
,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.
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 z/OS Communications Server: SNA Programmer’s 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
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.
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 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
,CMPAPPLI=input_limit
,CMPAPPLO=output_limit
,CMPAPPLI=input_limit,CMPAPPLO=output_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.
See the z/OS Communications Server: SNA Network Implementation Guide for
additional information about compression.
Note: You can use the “MODIFY VTAMOPTS command” on page 489 (CMPVTAM
operand) to change the compression level set by the start option.
Operands
procname
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
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.
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 489 (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.
3. Unless CSA24 is specifically indicated, all references to CSA mean CSA plus
ECSA.
Operands
procname
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
The value operand specifies the maximum amount of common service area
(CSA) storage to be used by VTAM 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 47 to display the current CSALIMIT setting, VTAM CSA usage, system
CSA limit, and system CSA storage remaining.
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 When OPTION=BELOW, specifies that no limit is enforced on the
amount of CSA used by VTAM. When OPTION=TOTAL, specifies the
maximum amount of CSA used by VTAM is to be set to the system
CSA limit. To find out what the system CSA limit is for your system,
use the DISPLAY BFRUSE command.
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.
If the value specified for n is not a multiple of 4, it is rounded to the
next page-size multiple (4K bytes).
Notes:
1. If the number you code is greater than the system CSA limit (of all
CSA + ECSA defined in the system) CSALIMIT is set to 90% of the
system CSA limit (which is the default). If the value specified is less
than 25 MB and the,F modifier is used on the command, a message
will be issued. Refer to the DISPLAY BFRUSE command for
information on displaying the current CSALIMIT setting, VTAM
CSA usage, system CSA limit, and available system CSA.
2. If CSALIMIT is specified (but without the ,F modifier) and VTAM
CSA usage reaches this specified CSALIMIT value with 25% or
more of system CSA storage remaining available for use, a warning
message will be issued. VTAM will continue to execute until only
25% of CSA storage remains available for use. If you wish to
prevent VTAM from using additional CSA beyond the specified
CSALIMIT value, issue a MODIFY CSALIMIT or MODIFY
VTAMOPTS,CSALIMIT command with the desired CSALIMIT
value and the ,F operand specified.
3. 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.
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.
MODIFY procname,CSDUMP
,SENSE=sense_code
,RU=ru_code
,MESSAGE= message_id_number
,
( message_id_number, message_value_field )
,MATCHLIM=1
,MATCHLIM=matchlim_value
Abbreviations
Operand Abbreviation
MODIFY F
Purpose
Set the CSDUMP trigger:
The user can have only one sense code, and one message trigger set
simultaneously. Therefore, the user can not have two different message or sense
code triggers set at the same time. If the user enters a message trigger, and then
enters a different message trigger, the first message trigger will be overwritten.
The MODIFY CSDUMP,DELETE command allows the user to delete the triggers
set earlier.
Operands
procname
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.
Set the CSDUMP trigger:
MATCHLIM=matchlim_value
Specifies that the CSDUMP trigger is to be disabled after matchlim_value
matches. The matchlim_value is an integer in the range 1-255. The default is 1.
MESSAGE=message_id_number
Specifies the ID number of the message that will trigger a dump. Message
numbers must be of the format ISTxxxI, ISTxxxxI, or IVTxxxxI.
Rule: If start option MSGLEVEL=BASE has been specified, or if
MSGLVL=BASE has been specified in a USS operator message table, the
message displayed on the console is the pre-version 4 message. CSDUMP with
a message trigger checks the message_id_number before it has been swapped to
the base message_id_number. Therefore, the message_id_number used with the
CSDUMP command must be the version 4 message number for CSDUMP to
match on the message_id_number and take the dump. Refer to z/OS
Communications Server: SNA Messages for a list of the base messages and their
corresponding version 4 numbers.
MESSAGE=(message_id_number,message_value_field,...)
This parameter specifies the message variable text that can be used to trigger a
dump. Instead of just matching on a message number, this allows the trigger to
be more specific. If variable text is specified, then a dump will be taken only if
the message and variable text match. If a variable text field is left blank, then it
is considered a wild card. Refer to z/OS Communications Server: SNA Messages
for more information about message text for VTAM operator messages.
Note: Use an underscore as a substitute for a space in the variable text value
of the message operand.
Rules:
1. Each message has the fixed number of message_value_fields. Each
message_value_field has the maximum length.
2. The specified number of message_value_fields must be less than or equal to
the number of message_value_fields in the specified message.
3. The specified length of the message_value_field must be less than or equal
to the maximum length of the specified message_value_field.
4. The leading message_value_field can be skipped using a comma ( , ) for
each message_value_field. The trailing message_value_field is not required.
5. Refer to z/OS Communications Server: SNA Messages to determine the
number of message value fields and their maximum lengths.
RU=ru_code
Specifies the response unit code that will carry the sense code specified. The
RU operand can only be used in combination with the SENSE operand. If the
RU operand is used, then the dump will only be triggered if the RU and
SENSE codes occur together. The RU code must be 2, 4, or 6 characters in
length.
Refer to z/OS Communications Server: SNA Data Areas Volume 1 for valid RU
codes or SNA Formats.
SENSE=sense_code
Specifies the sense code that will trigger a dump. It must be 8 characters in
length.
Refer to z/OS Communications Server: IP and SNA Codes for the valid sense
codes.
Remove the CSDUMP trigger:
DELETE=ALL
Specifies to delete both the message and the sense triggers.
DELETE=MESSAGE
Specifies to delete the message trigger.
DELETE=SENSE
Specifies to delete the sense trigger.
Examples
Using the message to take the dump:
f vtam,csdump,message=ist1386i
IST097I MODIFY ACCEPTED
IST223I MODIFY CSDUMP COMMAND COMPLETED
Using the message and the first message_value_field to take the dump:
f vtam,csdump,message=(ist169i,react)
IST097I MODIFY ACCEPTED
IST223I MODIFY CSDUMP COMMAND COMPLETED
Using the message and the second message_value_field to take the dump:
f vtam,csdump,message=(ist169i,,pua)
IST097I MODIFY ACCEPTED
IST223I MODIFY CSDUMP COMMAND COMPLETE
Using the sense code, RU code, and matchlim to take the dump 12 times:
f vtam,csdump,sense=08090000,ru=818641,matchlim=12
IST097I MODIFY ACCEPTED
IST223I MODIFY CSDUMP COMMAND COMPLETED
MODIFY procname,CSM
,ECSA=maxecsa ,FIXED=maxfix
DYNAMIC
MODIFY procname,CSM,MONITOR= YES
NO
Abbreviations
Operand Abbreviation
MODIFY F
Purpose
MODIFY CSM command to update CSM storage value or to activate CSM
PARMLIB member values:
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 z/OS
Communications Server: New Function Summary.
The Modify CSM command allows the operator to start or stop dynamic CSM
buffer monitoring. For more information about CSM Monitoring, refer to z/OS
Communications Server: New Function Summary.
Operands
procname
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 30720M.
MONITOR=YES
Specifies that CSM Buffer Monitoring will be activated. It provides the
component IDs of the users of CSM buffers in CSM buffer headers.
MONITOR=NO
Specifies that CSM Buffer Monitoring will be deactivated.
MONITOR=DYNAMIC
Specifies that CSM Buffer Monitoring will be dynamically activated and
deactivated. CSM dynamically activates CSM buffer Monitoring when CSM
storage usage approaches the critical level. It will dynamically deactivate CSM
buffer monitoring when CSM storage returns to a level slightly lower than the
normal level. The default value is DYNAMIC.
Notes:
1. It is recommended that users review their CSM usage and IVTPRM00 parmlib
specifications for ECSA and fixed CSM storage. CSM uses these values to
determine the activation and inactivation points of Dynamic CSM buffer
Monitoring. Refer to z/OS MVS Initialization and Tuning Reference for details.
2. When the CSM comes up, CSM Monitor status is dynamic by default. The
operator can modify the status of CSM Monitor active, inactive, or dynamic.
This status does not change when VTAM or TCP/IP goes down or comes up. It
will stay the same until the system is re–IPL’d, or another MODIFY command
is issued.
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
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.
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.
,LOGMODE=logon_mode_name ,LUNAME=lu_name
,DELETE=NALLOW
,AUTOSES=number_of_winner_sessions ,DELETE= ALLOW
NALLOW
,DDRAINL= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW
,DLIMITS=(dseslim,dminwinl,dminwinr) ,LOGMODE=logon_mode_name
,LUNAME=lu_name
,AUTOSES=number_of_winner_sessions
,DELETE=NALLOW
,DELETE= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW
,LUNAME=lu_name
,AUTOSES=number_of_winner_sessions
,DELETE=NALLOW
,DELETE= ALLOW ,DRESPL= ALLOW
NALLOW NALLOW
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
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.
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.
DRESPL=NALLOW
Specifies that VTAM does not accept a CNOS request specifying that the
LU is responsible for deactivating sessions.
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.
,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)
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.
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.
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.
Operands
procname
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.
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.
| where CDRSC2A is the name of a CDRSC major node that contains several
| resources that are now owned by control point SSCP2A. Model CDRSCs do not
| have a directory representation, but any model CDRSC in a CDRSC major
| node will be updated so that future clone CDRSCs built from that model
| CDRSC will be affected by this command.
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.
MODIFY DR command
Delete a logical unit from a physical unit, or a physical unit from a line:
,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 z/OS 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 333 for information about
how to update the list of PUs (adjacent link stations) associated with an
independent LU.
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
v Deletes an LU from a nonswitched PU
v Deletes a type 2.1 PU on an NCP ESCON® channel
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 z/OS Communications Server: SNA Resource Definition Reference.
For a VTAM local peripheral node, this command performs the following
functions:
Operands
procname
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.
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 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.
,ACTION=COMP
MODIFY procname,DUMP ,ID=ncp_name
,DUMPDS=name
,OPTION=STATIC ,RMPO=NO
,DUMPSTA= ,RMPO= NO
link_station_name YES
,TYPE=NCP
,OPTION=STATIC
MODIFY procname,DUMP ,ID=ncp_name ,ACTION=STORE
,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.
,ACTION=COMP
MODIFY procname,DUMP ,ID=ncp_name ,TYPE= CSP
MOSS
(1)
,DUMPDS=name
Notes:
1 If the NCP has been acquired before activation, DUMPDS is required.
,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.
,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
Purpose
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
v Purge an NCP, CSP, or MOSS dump from the hard disk
Operands
procname
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.
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 device number 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 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.
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.
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 z/OS Communications Server: SNA Network Implementation Guide.
Note: The only way to modify ENCRTYPE is to use the MODIFY SECURITY
command.
Operands
procname
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).
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.
| Tip: If you are specifying a model resource (APPL or CDRSC), you can use
| wildcard characters in the name you specify. The use of wildcard characters on
| the ID operand does not depend on the value of the DSPLYWLD start option.
| For model resources, any current clone resources are unaffected by this
| command, but future clone resources and their sessions will be affected.
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,...
,ID= ISTEXCDM
,PARMS=character_string ,MODULE=module_name
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
,PARMS=character_string
,MODULE=module_name ,PARMS=character_string
,ID= ISTEXCDM
,PARMS=character_string
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
,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
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.
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.
|
| MODIFY GR command
| MODIFY procname,GR ,GNAME=netid.generic_resource ,OPTION=DELETE
|
| Abbreviations
|| Operand Abbreviation
| MODIFY F
| DELETE DEL
| OPTION OPT
|
| Purpose
| The MODIFY GR command causes VTAM to delete information about a generic
| resource locally at this host and from the generic resource’s coupling facility
| structure. If VTAM has lost access to the generic resource’s coupling facility
| structure, local generic resource information can still be deleted. This command has
| dependencies that must be met for the command to succeed. Every application
| instance of the generic resource must do the following:
| v Delete itself as an active instance of the generic resource
| v End all of its sessions
| v Delete all of its generic resource affinities
| v Close its ACB
| If these dependencies are met on the host where the MODIFY GR command is
| issued, but are not met for generic resource applications residing on other hosts,
| then local generic resource information can still be deleted. In order for a generic
| resource to be completely deleted from all hosts in a sysplex, this command must
| be issued at every host in a sysplex, and at least one host must have connectivity
| to the generic resources structure in the coupling facility. Refer to z/OS
| Communications Server: SNA Network Implementation Guide for a description of how
| and why a generic resource should be deleted from a sysplex.
| Tips:
| v You can display affinities using the D NET, GRAFFIN command. All generic
| resource instances can be displayed with the D
| NET,ID=grname,IDTYPE=GENERIC command.
| v Use the D NET,RSCLIST command to determine where the representation of the
| generic resource exists. A type of GENERIC RESOURCE indicates that it exists in
| the generic resource coupling facility structure. A type of GENERIC USERVAR
| indicates that it exists on the local VTAM where the display command is issued.
| Operands
| procname
| The procedure name for the command. If the procname value 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 the procname value in this command.
| If the procname value in the START command was startname, startname must be
| specified for the procname value in this command.
| GNAME=netid.generic_resource
| A required parameter that specifies the generic resource name to be deleted.
| The name can be a network-qualified name. If a netid value is not specified, the
| default network ID is that of the host where the command is issued.
| OPTION=DELETE
| A required parameter that specifies the operation to be performed. DELETE is
| the only valid value. It specifies that the generic resource should be deleted.
,OPTION=ACT
MODIFY procname,IMR ,ID= link_station_name
pu_name
,RECLIM=10
,RECLIM=number_of_errors
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 z/OS
Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures.
Operands
procname
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.
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.
Abbreviations
Operand Abbreviation
MODIFY F
DUMPENABLE DUMPE
DUMPDISABLE DUMPD
DUMPDEFAULT DUMPDEF
Purpose
INOPCODE is used to control the setting of the inoperative condition (InOp) code
attributes:
v A dump attribute of DUMPENABLE indicates that if the inoperative condition
specified by the module and code occurs, and INOPDUMP is enabled for the
resource, VTAM will not avoid taking a dump.
v A dump attribute of DUMPDISABLE indicates that if the inoperative condition
specified by the module and code occurs, VTAM will avoid taking a dump.
v A dump attribute of DUMPDEFAULT applies the original, IBM supplied
attributes.
Operands
procname
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.
Positional Parameters:
v Positional parameter 1 specifies the modules which contain the inopcodes to
be altered.
v Positional parameter 2 specifies the inopcode within the modules to be
altered.
v Positional parameter 3 specifies the dump attribute to be applied
Restrictions:
v When specifying an InOpCode for the second positional parameter, always
specify three digits by including any leading zeros.
v When positional parameter 1 is ALL, positional parameter 2 must also be ALL.
Tip: The value of using 'ALL' for either positional parameters 1 or 2, or both when
applying a dump attribute of DUMPENABLE is questionable, especially when a
resource is InOpDump active. Use caution with the ALL values when enabling.
Examples
Setting the dump attribute of ISTTSC8E inopcode 202 to DUMPDISABLE:
f vtam,inopcode=(isttsc8e,202,dumpd)
IST097I MODIFY ACCEPTED
IST1919I INOPCODES FOR MODULE ISTTSC8E:
IST1920I DUMP ENABLED:
IST1921I 002 003 004 005 006 007 008 009 010 011 012 013 014 100
IST1921I 101 102 103 200 201 205 206 207 208
IST1922I DUMP DISABLED:
IST1921I 001 033 034 035 037 038 039 040 041 042 132 133 202 203
IST1921I 204
IST314I END
IST223I MODIFY COMMAND COMPLETED
Restoring all IBM supplied defaults (does nothing unless at least one InOpCode
has been modified):
f vtam,inopcode=(all,all,dumpdef)
IST097I MODIFY ACCEPTED
IST1189I INOPCODE = DUMPDEFAULT
IST223I MODIFY COMMAND COMPLETED
The following example assumes the trlename, modulename, and inopcode have been
remembered from a previous InOp message.
The above two commands, by themselves, will not result in a dump when the
InOp occurs. This is because the resource is not yet enabled for InOpDump.
Now the dump will be taken if the condition leading to the use of the module
inopcode occurs. Once the problem is recreated and a dump has been acquired,
restore the environment.
Set InOpDump off for all resources and restore all InOpCode IBM supplied
defaults:
f procname,inopdump=off
IST097I MODIFY ACCEPTED
IST1865I GLOBAL INOPDUMP = OFF
IST1867I INOPDUMP = OFF FOR ALL TRLE-BASED RESOURCES
IST314I END
IST223I MODIFY INOPDUMP COMMAND COMPLETED
f procname,inopcode=(all,all,dumpdef)
IST097I MODIFY ACCEPTED
IST1189I INOPCODE = DUMPDEFAULT
IST223I MODIFY COMMAND COMPLETED
( trle_name )
Abbreviations
Operand Abbreviation
MODIFY F
Purpose
INOPDUMP controls the automatic dumping of VTAM when an inoperative
condition occurs in one of VTAMs data link control layers. There are three separate
but related controls:
v The global INOPDUMP status, which is also the VTAM INOPDUMP start
option. This controls automatic dumping when an inoperative condition is
declared on a resource that is not defined within a TRLE (transport resource list
entry). The global INOPDUMP status is copied to the TRLE when a TRLE is
activated if the TRLE InOpDump status has not been explicitly set.
v The TRLE INOPDUMP status which controls automatic dumping when an
inoperative condition is declared on a resource that is defined within the TRLE.
v The INOPCODE status, which controls whether a given code in the module
detecting the inoperative condition is enabled for automatic dumping. Refer to
“MODIFY INOPCODE command” on page 389 for more details on the
interaction between INOPDUMP and INOPCODE.
Use MODIFY INOPDUMP to alter either the global or TRLE INOPDUMP status.
Operands
procname
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.
INOPDUMP=ON
Specifies that either the global or TRLE inopdump status is to be set on.
INOPDUMP=OFF
Specifies that either the global or TRLE inopdump status is to be set off.
TRLE=trle_name
Specifies the TRLE name or names for which the INOPDUMP status is to be
altered.
Notes:
1. If the TRLE operand is not specified, both the global and TRLE statuses are
altered. If the TRLE operand is specified, only the status of the TRLE for the
name or names specified is altered and the global status remains unchanged.
2. The response to a successful global Modify INOPDUMP command will always
include the global INOPDUMP status. If the TRL major node was available at
the time of the command, you will receive a reminder message that the status
for all TRLEs has also been changed. The response to a successful Modify
INOPDUMP command that includes the TRLE option will always include the
global INOPDUMP status along with the TRLE name or names that were
processed.
Examples
Modifying INOPDUMP information:
f vtam,inopdump=off,trle=trle1a
IST097I MODIFY ACCEPTED
IST1865I GLOBAL INOPDUMP = OFF
IST1866I TRLE = TRLE1A INOPDUMP = OFF
IST314I END
IST223I MODIFY INOPDUMP COMMAND COMPLETED
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 z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for
guidance on setting the I/O problem determination time-out interval.
Note: You can use the “MODIFY VTAMOPTS command” on page 489 (IOINT
operand) to perform the same function as this command.
Operands
procname
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.
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.
Note: You can use the “MODIFY VTAMOPTS command” on page 489 to perform
the same function as this command.
Operands
procname
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
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
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 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.
,NFRAMES=1
,NFRAMES=number_of_test_messages
,NFRAMES=1 ,NTRANS=10
,NFRAMES=number_of_test_messages ,NTRANS=number_of_test_messages
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
these results in a message. For more information on when and how to run an LL2
test, see z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures.
Operands
procname
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 z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
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.
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.)
,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:
,NOTIFY=60
,IPLTIME= (date,time)
,NOTIFY=
NO
time_period
,LOADMOD=load_module_name
,LOADMOD=load_module_name
,LOADMOD=load_module_name
,NOTIFY=60
,IPLTIME= (date,time)
,NOTIFY=
NO
time_period
CANCEL
,LOADMOD=load_module_name
,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
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.
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 z/OS Communications Server: SNA Network Implementation Guide.
Use the “DISPLAY DISK command” on page 95 to examine the contents of the
communication controller hard disk.
Operands
procname
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 5 on page 404 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.
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
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.
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 521 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 6 for examples of time specifications.
Table 6. Examples of time specifications for IPLTIME
Difference in
time zones
Location of 3745 between the Time of
Location of for the operator and Time specified scheduled IPL at
operator scheduled IPL 3745 in IPLTIME 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.
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 489 to perform
the same function as this command.
Operands
procname
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.
Abbreviations
Operand Abbreviation
MODIFY F
COMMAND COM, CMD
RESNM RES, NAME, RESNAME
Purpose
The MODIFY NCP command is used to send a request to NCP to execute the
specified command for the specified resource.
Operands
procname
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=ncp_name
Specifies an active NCP.
COMMAND
Specifies the command for NCP to execute.
COMMAND=TRSWITCH
Specifies the Token-Ring Path switch request command.
The TRSWITCH command requests NCP to initiate non-disruptive route
switch (NDRS) processing for the resource. The resource indicated by the
RESNM parameter must be an active NCP Token Ring Interface (NTRI)
subarea (PU4) physical unit connected to a 3745 through a bridged
network. If no error messages are received at the system console, then
VTAM has sent the request to NCP via a SETCV RU. If NCP cannot initiate
NDRS processing for the resource, the SETCV command will be rejected
and the following message will be displayed at the system console:
IST242I SETCV COMMAND FAILED FOR ID = nodename SENSE = code
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
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.
( trle_name )
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
455 for more ways to control the recording of tuning statistics. MODIFY
NOTNSTAT without the TRLE operand terminates global tuning statistics
recording (all devices for which VTAM gathers tuning statistics). MODIFY
NOTNSTAT with the TRLE operand only affects those TRLEs specified.
Operands
procname
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.
TRLE=trle_name
Specifies the transport resource list entry name or names for which statistical
recording is to be terminated.
Note: Recording is terminated only for those devices within the specified
TRLE or TRLEs. If the TRLE operand is not specified, recording is
terminated for all devices that collect tuning statistics.
,IDTYPE=RESOURCE ,SCOPE=ONLY
,IDTYPE= CP ,SCOPE= ONLY
SSCP ALL
RESOURCE
,OPTION= ALL
option
(option)
,
( ACCTING )
ADJSSCP
ALIAS
ALS
BEGIN
END
GWPATH
INITAUTH
REPL
SECAUTH
VRSEL
XRF
,OPTION= ALL
option
(option)
,
( BEGIN )
CONNSTAT
DYNA_XID
PRED_XID
END
,OPTION= ALL
option
(option)
,
( BEGIN )
INITAUTH
ADS_SEL
BN_SEL
CDS_SEL
CRR_SEL
REPL
END
,IDTYPE=RESOURCE
,IDTYPE= CP ,ALSNAME=adjacent_link_station_name
SSCP
RESOURCE
,SCOPE=ONLY
,SCOPE= ONLY
ALL
,IDTYPE=RESOURCE ,SCOPE=ONLY
,IDTYPE= CP ,SCOPE= ONLY
SSCP ALL
RESOURCE
, DEVICE = ALL
hex_device_address
( COMMAND )
CONNECTION
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
SESSION
,PU=3710_pu_name
,ID=VTAMBUF
MODIFY procname,NOTRACE ,TYPE=SMS
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU
,IDTYPE=RESOURCE
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU
,MODE=INT
(1)
,MODE=EXT
MODIFY procname,NOTRACE ,TYPE=VTAM
,MODE= INT
EXT
(2)
,SUBTRACE=ARBP,OPTION= HPR
(3)
(..,HPR,..)
(4)
,SUBTRACE= TGVC ,OPTION= SSCP
TREE (5)
(..,SSCP,..)
,OPTION= ALL
(6)
END
(7)
FORCE
option
(option)
,
( API )
APPC
CFS
CIA
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 OPTION=HPR must be specified when SUBTRACE=ARBP is specified.
3 If multiple trace options are coded in parentheses, HPR must be one of the
options coded inside the parentheses when SUBTRACE=ARBP is coded.
4 OPTION=SSCP must be specified when SUBTRACE=TGVC or
SUBTRACE=TREE is coded
5 If multiple trace options are coded in parentheses, SSCP must be one of the
options coded inside the parentheses when SUBTRACE=TGVC or
SUBTRACE=TREE is coded.
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
SCOPE=ALL EVERY or E
SCOPE=ONLY NONE
Purpose
The MODIFY NOTRACE command stops a specified trace or deletes a trace
command that was saved previously with MODIFY TRACE,SAVE=YES. See z/OS
Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for a more
detailed description of the VTAM trace facilities. See also the z/OS Communications
Server: SNA Resource Definition Reference and the “MODIFY TRACE command” on
page 462.
Operands
procname
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.
If no ALS list exists for the resource, specify the adjacent link station on the
ALSNAME operand.
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=MODULE, TYPE=STATE, and TYPE=VTAM.
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=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
For TYPE=EXIT where ID=ISTEXCAA, you can also specify the following
options:
OPTION=ALL
Stops the tracing of all functions of the session management exit (SME).
OPTION=ACCTING
Stops tracing the initial and final accounting function of the session
management exit (SME).
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=END
Stops the tracing of the END 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=EXIT where ID=ISTEXCCS, you can also specify the following
options:
OPTION=ALL
Stops tracing of all functions.
OPTION=BEGIN
Stops tracing the begin function.
OPTION=CONNSTAT
Stops tracing the connection status.
OPTION=DYNA_XID
Stops tracing the XIDs for dynamic PUs function.
OPTION=END
Stops tracing the end function.
OPTION=PRED_XID
Stops tracing the XIDs for predefined PUs function.
For TYPE=EXIT where ID=ISTEXCDM, you can also specify the following
options:
OPTION=ALL
Stops tracing of all the functions.
OPTION=ADS_SEL
Stops tracing the alternate central directory server selection function.
OPTION=BEGIN
Stops tracing the begin function.
OPTION=BN_SEL
Stops tracing the border node selection function.
OPTION=CDS_SEL
Stops tracing the central directory server selection function.
OPTION=CRR_SEL
Stops tracing the central resource registration selection function.
OPTION=END
Stops tracing the end function.
OPTION=INITAUTH
Stops tracing the initial authorization function.
OPTION=REPL
Stops tracing the exit replacement function
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.
OPTION=CIA
This option helps isolate problems related to channel I/O. CIA entries are
the remaining trace records from the CIO option.
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.
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.
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 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.
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.
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
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.
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 Tivoli NetView for z/OS. Use of this command
requires the system to have a primary program operator such as the Tivoli
NetView for z/OS, and requires that the primary program operator can support
the option.
Note: You can use the “MODIFY VTAMOPTS command” on page 489 to perform
the same function as this command.
Operands
procname
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.
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 z/OS Communications Server: SNA Programmer’s LU 6.2 Guide
for more information on LU 6.2 application program security.
Operands
procname
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.
Purpose
The MODIFY QUERY command can be issued only from a program operator
application.
,ACTION=UPDATE
,ACTION=DELETE
,SRCOUNT=number_of_search_requests
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 setting of the error message display value for an APPL or CDRSC
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
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 add, update, or delete the name of the adjacent
SSCP list for a cross-domain resource.
ACTION is valid only 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.
Note: The ADJLIST operand is not valid in a pure APPN node. The MODIFY
RESOURCE command will fail with an indication that ADJLIST is
ignored. A pure APPN node is a VTAM that is started with start options
NODETYPE=NN or NODETYPE=EN, but without HOSTSA or with
HOSTSA and SACONNS=NO.
ADJLIST is only valid with the ACTION and ID operands.
ASRCVLM=amount_of_storage
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
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 z/OS 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
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.
SIRFMSG
Specifies SIRFMSG values for the resource.
| The SIRFMSG operand for a CDRSC definition will effectively control
| ASIRFMSG, DSIRFMSG, ESIRFMSG, FSIRFMSG, LSIRFMSG, RSIRFMSG, and
| SIRFMSG processing.
SIRFMSG=ALLSSCP
Specifies that messages are issued for all session initiation request failures
involving this resource.
SIRFMSG=OLUSSCP
Specifies that messages are issued only when the VTAM owning this
resource is the origin logical unit (OLU) SSCP.
SIRFMSG=START
Specifies that the value of the SIRFMSG start option is to be used for this
resource. This is the default setting.
SIRFMSG=NONE
Specifies that no messages are issued for any searches involving this
resource.
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 valid only 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 applies only to existing CDRSCs and APPN directory
entries.
SRCOUNT is valid only 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 applies only to existing CDRSCs and APPN directory
entries.
SRTIMER is valid only 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.
Abbreviations
Operand Abbreviation
MODIFY F
Purpose
The MODIFY RTP command causes VTAM to search for the best high performance
routing (HPR) route, based on transmission group weight, between the two
endpoints of a rapid transport protocol (RTP) connection. If an equal or better
route is found, the connection is switched to the better route. If the current route is
the best route, a path switch still occurs, but the switch is made to the same route.
Operands
procname
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. This operand is required.
(1)
ENCRTYPE=DES
ENCRTYPE=TDES24
Notes:
1 ENCRTYPE can not be downleveled. If the current value is TDES24, MODIFY
SECURITY ENCRTYPE=DES will not be allowed.
,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
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.
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.
Note: 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
CKEY Device-type LU
| ENCR Application program, device-type LU, or CDRSC
ENCRTYPE
| Application program, device-type LU, or CDRSC
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.
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.
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
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.
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 z/OS 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 z/OS 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 489 (SUPP
operand) to perform the same function as this command.
Operands
procname
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.
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.
Change resource association with a CoS table or load a new CoS table and
associate it with a resource:
,TYPE=COSTAB,NETID=netid,ORIGIN=ncp_name ,NEWTAB=new_table_name
,OLDTAB=old_table_name
Abbreviations
Operand Abbreviation
MODIFY F
NETID=name NET=name
NEWTAB=name NEW=name
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
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 359 or the “MODIFY RESOURCE command” on
page 432.
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
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
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
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.
| Tip: If you are specifying a model resource (APPL or CDRSC), you can use
| wildcard characters in the name you specify. The use of wildcard characters on
| the ID operand does not depend on the value of the DSPLYWLD start option.
NETID=netid
Identifies the network attached to a gateway NCP with which the Class of
Service table association is to be changed.
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 359 or
the “MODIFY RESOURCE command” on page 432.
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 z/OS Communications Server: SNA Resource Definition
Reference.
Examples
Load a new USS table and associate it with a resource:
F VTAM,TABLE,TYPE=USSTAB,OPTION=ASSOCIATE,NEWTAB=USSTAB1,ID=LU1,OLDTAB=*
Change another LU’s USS table definition to the table loaded by the previous
example:
F VTAM,TABLE,TYPE=USSTAB,OPTION=ASSOCIATE,NEWTAB=USSTAB1,ID=LU2,OLDTAB=*
Change all resources using an existing USS table to use a new USS table:
F VTAM,TABLE,OPTION=LOAD,NEWTAB=USSTAB2,OLDTAB=USSTAB1
Change all resources using an existing USS table to use an updated copy of the
USS table:
F VTAM,TABLE,OPTION=LOAD,NEWTAB=USSTAB2
,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
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.
TGPNAME=tg_profile_name
Specifies the name of a transmission group profile definition.
,TIME=number_of_minutes ,TRLE= trle_name
,
( trle_name )
Abbreviations
Operand Abbreviation
MODIFY F
ACTION=ACTIVATE ACTIVATE or A
ACTION=UPDATE UPDATE or U
CNSL=NO NOCNSL
CNSL=YES 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 z/OS Communications
Server: SNA Network Implementation Guide.
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
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.
Note: Recording is initiated only for those devices within the specified TRLE
or TRLEs. If the TRLE operand is not specified, recording is initiated for
all devices that collect tuning statistics.
The TRLE operand is mutually exclusive with the ACTION=UPDATE operand.
,FUNCTION=DELETE
MODIFY procname,TOPO ,ID=cp_name
,SCOPE=LOCAL
,SCOPE= LOCAL ,TYPE=FORCE
NETWORK
,FUNCTION=DELETE
MODIFY procname,TOPO ,ORIG=cp_name ,DEST=cp_name
,SCOPE=LOCAL
,TGN=tg_number
,SCOPE= LOCAL ,TYPE=FORCE
NETWORK
,SCOPE=LOCAL
,SCOPE= LOCAL
NETWORK
,SCOPE=LOCAL
,TGN=tg_number
,SCOPE= LOCAL
NETWORK
,SCOPE=LOCAL
,SCOPE= LOCAL
NETWORK
,SCOPE=NETWORK
,SCOPE= NETWORK
LOCAL
Abbreviations
Operand Abbreviation
FUNCTION=DELETE DELETE
MODIFY F
TYPE=FORCE FORCE or 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, transmission groups (TGs), or unreachable partner
information for a virtual node (VRN) or end node (EN).
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.
Rules:
v You cannot delete the node entry for your own host node.
v You cannot delete an active local transmission group.
v You cannot delete an adjacent node unless the link to the adjacent node is
inactive.
Operands
procname
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=CLRUNRCH
Specifies that the unreachable partner information for an Enterprise
Extender virtual node or an end node will be cleared, making all paths
through the virtual node or all paths that originate in the end node and
traverse an Enterprise Extender virtual node available for route calculation,
if they were previously unavailable for route calculation due to the
unreachable partner information.
Guidelines:
v To clear the unreachable partner information associated with an end
node, the command should be issued on the end node. When the
command is issued on the end node, the request will be propagated to
the end node’s network node server, which does all route calculation for
an end node. This will cause unreachable partner information to be
cleared in both the end node and its network node server so paths that
originate in the end node and traverse the Enterprise Extender virtual
nodes named in the unreachable partner information will be available
for route calculation for new sessions and HPR path switches.
v You can also issue the command on the end node’s network node server
to clear the unreachable partner information associated with the end
node. This will make all paths that originate in the end node available
for route calculation, if they were previously unavailable due to
unreachable partner information. However, if you choose to clear the
unreachable partner information on an end node’s network node server,
the command should also be issued on the end node. Otherwise, the
residual unreachable partner information on the end node will be
communicated to a new network node server if the end node changes
network node servers.
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.
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. When FUNCTION=CLRUNRCH, cp_name must be the name of an
Enterprise Extender virtual node or an end node.
Rule: 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.
Result: If SCOPE=LOCAL is specified on an end node to clear unreachable
partner information for the end node, the request is still propagated to the
end node’s network node server, which does all route calculation for an
end node. This will cause unreachable partner information to be cleared in
both the end node and its network node server so paths that originate in
the end node and traverse the Enterprise Extender virtual nodes named in
the unreachable partner information will be available for route calculation
for new sessions and HPR path switches.
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
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.
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.
,AMOUNT=PARTIAL
MODIFY procname,TRACE ,TYPE=BUF ,ID=node_name
,AMOUNT= FULL
PARTIAL
,OPTION= ALL
option
(option)
,
( ACCTING )
ADJSSCP
ALIAS
ALS
BEGIN
END
GWPATH
INITAUTH
REPL
SECAUTH
VRSEL
XRF
,OPTION= ALL
option
(option)
,
( BEGIN )
CONNSTAT
DYNA_XID
PRED_XID
END
,OPTION= ALL
option
(option)
,
( BEGIN )
INITAUTH
ADS_SEL
BN_SEL
CDS_SEL
CRR_SEL
REPL
END
,IDTYPE=RESOURCE
,ALSNAME=adjacent_link_station_name ,IDTYPE= CP
SSCP
RESOURCE
,SCOPE=ONLY
,SCOPE= ONLY
ALL
,IDTYPE=RESOURCE
MODIFY procname,TRACE ,TYPE=IO ,ID=node_name
,IDTYPE= CP
SSCP
RESOURCE
,SAVE=NO ,SCOPE=ONLY
,SAVE= NO ,SCOPE= ONLY
YES ALL
Start or modify an input/output trace for a TRLE with the DATAPATH operand
coded:
,IDTYPE=RESOURCE
MODIFY procname,TRACE ,TYPE=IO ,ID=trle_name
,IDTYPE=RESOURCE
,LENGTH=272
,DEVICE = ALL ,LENGTH=number_of_bytes
hex_device_address
,SAVE=NO ,SCOPE=ONLY
,SAVE= NO ,SCOPE= ONLY
YES ALL
( COMMAND )
CONNECTION
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
PURGE
SESSION
,COUNT=ALL
,COUNT= ALL
number_of_bytes
,PU=3710_pu_name
,FRAMES= ALL
DATA
,COUNT=ALL
,COUNT= ALL ,TRACEPT=trace_point_id
number_of_bytes
,ID=VTAMBUF
MODIFY procname,TRACE ,TYPE=SMS
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU
,IDTYPE=RESOURCE ,SAVE=NO
,IDTYPE= CP ,SAVE= NO
SSCP YES
RESOURCE
,OPTION= ALL
option
(option)
,
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU
,BFRNUM=2
,MODE= EXT
,BFRNUM=number
INT
,SIZE=size ,DSPSIZE=dspsize
,SUBTRACE=ARBP,OPTION= HPR
ALL
(1)
(..,HPR,..)
,SUBTRACE= TGVC ,OPTION= SSCP
TREE ALL
(2)
(..,SSCP,..)
,OPTION= ALL
option
(option)
,
( API )
APPC
CFS
CIA
CIO
CMIP
CSM
ESC
HPR
LCS
LOCK
MSG
NRM
PIU
PSS
SMS
SSCP
TCP
VCNS
XBUF
XCF
Notes:
1 If multiple trace options are coded in parentheses, HPR must be one of the
options coded inside the parentheses when SUBTRACE=ARBP is coded.
2 If multiple trace options are coded in parentheses, SSCP must be one of the
options coded inside the parentheses when SUBTRACE=TGVC or
SUBTRACE=TREE is coded.
Abbreviations
Operand Abbreviation
MODIFY F
ALSNAME ALS
AMOUNT=FULL AMT=F
AMOUNT=PARTIAL AMT=P
OPTION OPT
OPTION=COMMAND OPT=CMD
OPTION=CONNECTION OPT=CON
OPTION=DEFINITION OPT=DEF
Operand Abbreviation
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
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 z/OS 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 z/OS
Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures 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
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.
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.
If no ALS list exists for the resource, specify the adjacent link station on the
ALSNAME operand.
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.
DEVICE
Applies only when the ID operand is a TRLE that has the DATAPATH operand
coded. Use DEVICE to start input/output trace on OSA-Express devices
specified on the DATAPATH operand.
DEVICE=ALL
Specifies to turn on input/output trace on all devices in the DATAPATH
list.
DEVICE=hex_device_address
Specifies to turn on input/output trace for a specific DATAPATH device.
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 472
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.
MODIFY TRACE
LL
LL
LL
=A
=A
=A
PE
PE
PE
GP CO
S I TLR
B U 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
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
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
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.
LENGTH
Applies only when the DEVICE operand is specified and the ID operand is a
TRLE that has the DATAPATH operand coded. Use LENGTH to specify the
number of bytes from each packet to trace. Valid values are 56 to 9016. Values
are rounded up to 56 and values above 9016 are rounded down to 9016. All
values are rounded up, if necessary, to an even multiple of 28.
Note: The default value is 272 for a TRLE that has the DATAPATH operand
coded.
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 z/OS Communications Server: SNA Diagnosis Vol 1,
Techniques and Procedures 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
Spplies 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).
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.
The API, CIO, MSG, NRM, PIU, and SSCP VIT options are kept active by
VTAM for internal recording (MODE=INT). 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 z/OS
Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT.
OPTION=ALL
Applies to TYPE=MODULE, TYPE=STATE, and TYPE=VTAM.
For TYPE=EXIT where ID=ISTEXCAA, you can also specify the following
options:
OPTION=ALL
Starts the tracing of all functions.
OPTION=ACCTING
Starts tracing the initial and final accounting function of the session
management exit (SME).
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=EXIT where ID=ISTEXCCS, you can also specify the following
options:
OPTION=ALL
Starts the tracing of all functions.
OPTION=BEGIN
Starts tracing the begin function.
OPTION=CONNSTAT
Starts tracing the connection status.
OPTION=DYNA_XID
Starts tracing the XIDs for dynamic PUs function.
OPTION=END
Starts tracing the end function.
OPTION=PRED_XID
Starts tracing the XIDs for predefined PUs function.
For TYPE=EXIT where ID=ISTEXCDM, you can also specify the following
options:
OPTION=ALL
Starts the tracing of all the functions.
OPTION=ADS_SEL
Starts tracing the alternate central directory server selection function.
OPTION=BEGIN
Starts tracing the begin function.
OPTION=BN_SEL
Starts tracing the border node selection function.
OPTION=CDS_SEL
Starts tracing the central directory server selection function.
OPTION=CRR_SEL
Starts tracing the central resource registration selection function.
OPTION=END
Starts tracing the end function.
OPTION=INITAUTH
Starts tracing the initial authorization function.
OPTION=REPL
Starts tracing the exit replacement function
OPTION=SESSION
Starts tracing modules involved in session establishment.
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.
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.
If the specified node is a model application, SCOPE=ALL turns on the
trace option for the model application and starts traces for all existing
dynamic applications created using the model. Traces will be started for
future dynamic applications created using the model.
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.
If the specified node is a model application, SCOPE=ONLY turns on the
trace option for the model application. Traces for all existing dynamic
applications created using the model are unaffected. Traces will be started
for future dynamic applications created using the model.
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 specify a value less than 100, 100 will be used instead.
If the VTAM internal trace is not already started, and you omit this option, the
default size is 999.
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.
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 minimum size, not the size you requested.
SUBTRACE
Specifies that SUBTRACE can be used to turn on a subset of trace entries
under a trace option. Of the SUBTRACE types defined, subtrace TREE and
TGVC are defined under the SSCP trace option and subtrace ARBP is defined
under the HPR trace option.
Note: All of the SUBTRACE options are defaulted to off. They can generate a
large number of records in the VTAM trace and can incur a significant
overhead, but may be necessary in some cases for diagnostic purposes.
It is not recommended to activate them at VTAM start time. If used, the
SUBTRACE options should be turned off when the necessary trace
output has been obtained.
SUBTRACE=ARBP
Specifies that OPTION is a required keyword when SUBTRACE is
specified and HPR must be one of the trace options specified when
SUBTRACE=ARBP is coded. After subtrace ARBP is activated, the
following trace records will be generated for the ARB algorithm processing:
ARBR (Generated when ARB Responsive Mode algorithm is utilized) and
ARBB (Generated when ARB Base Mode algorithm is utilized).
SUBTRACE=TGVC
Specifies that OPTION is a required keyword when SUBTRACE is
specified and SSCP must be one of the trace options specified when
SUBTRACE=TGVC is coded. After subtrace TGVC is activated, the
following trace records will be generated for various TG Vector requests:
TGVC and TGV2. If large amounts of data are being traced, additional
TGVC records (plus subsequent TGV2 records) may occur.
SUBTRACE=TREE
Specifies that OPTION is a required keyword when SUBTRACE is
specified and SSCP must be one of the trace options specified when
SUBTRACE=TREE is coded. After subtrace TREE is activated, the
following trace records will be generated for routing trees used by APPN
route computation: TRRT, TRR2, TRR3, TRR4, TRR5, HLST, and HLS2.
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 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.
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)
,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
,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
,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:
,VALUE=appl_name
Abbreviations
Operand Abbreviation
MODIFY F
NO N
OPTION OPT
OPTION=DELETE OPT=DEL
OPTION=UPDATE OPT=UP
TYPE=DYNAMIC TYPE=DYN
Operand Abbreviation
TYPE=STATIC TYPE=STA
TYPE=VOLATILE TYPE=VOL
VALUE=value VAL=value
YES Y
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.
Operands
procname
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.
APPC=NO
Specifies that the USERVAR ID is not used to replace the application
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.
(2)
(1) ,APPNCOS=class-of-service_name
,API64R= NO
YES
,ASIRFMSG= ALLSSCP ,AUTHLEN= NO ,AUTORTRY= AUTOCAP
OLUSSCP YES CDRM
NONE ALL
NONE
(3) (4)
,AUTOTI=time_period ,BNDYN= NONE ,BNORD= DEFINED
LIMITED PRIORITY
FULL
,BSCMDRS= STATS ,CDRDYN= YES
NOSTATS NO
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS
(6)
(5) ,CMPMIPS=compression_ratio
,CDSREFER=number_of_CDSs
(7)
,CNNRTMSG= SUPPRESS ,CMPVTAM=compression_level ,CONNTYPE= APPN
NOSUPP LEN
(8)
,CPCP= YES ,CSALIMIT= value
NO (value )
LEASED ,F
SWITCHED
,CSA24= value ,DIALRTRY= YES
(value ) NO
,F
(9) (10)
,DIRSIZE=number_of_resources ,DIRTIME=time_period
,DISCNTIM=(time_period1,time_period2) ,DLRORDER= STATNID
CPNAME
(,FIRST)
(,ONLY)
(CPNAME ,FIRST)
,ONLY
(STATNID ,FIRST)
,ONLY
(11) ,DSPLYDEF=number_of_messages
DSIRFMSG= ALLSSCP
OLUSSCP
NONE
,DSPLYWLD= FULLWILD DUPDEFS= ALL ,DYNDLGMD= logmode_name
NOWILD NONE NONE
OPERONLY APPL
POAONLY DEPLU
(12)
,DYNMODTB= table_name ,ENCRPREF= NONE ,ENCRYPTN= YES
NONE value NO
CCA
CUSP
24
31
,ESIRFMSG= ALLSSCP EXPFLTRM=expedited_flow_count ,FSIRFMSG= ALLSSCP
OLUSSCP OLUSSCP
NONE NONE
(13) HOTIOTRM=percentage_of_buffer_pool
HOSTNAME= fully_qualified_hostname
NONE
,HPRNCPBF= YES HPRPST=(low_limit,med_limit,high_limit,network_limit)
NO
(14) (15) (16) ALL ALL
,INOPCODE=( , , DUMPENABLE )
ALL ALL DUMPDISABLE
modulename inopcode DUMPDEFAULT
,INOPDUMP= ON ,IOINT=number_of_seconds
(17)
OFF
,IOMSGLIM=number_of_message_pairs ,IOPURGE=timeout_value
(18) IPINFO= SENDALL (19)
IPADDR=ip_address SNDLOCAL IQDCHPID= ANY
DISPONLY NONE
NONE CHPID
IQDIOSTG= MAX ,ISTCOSDF= ALL
AVG APPL
MIN DEPLU
NNN INDLU
NONE
,
( APPL )
DEPLU
INDLU
LIMINTCP=number_of_seconds (20)
,LSIRFMSG= ALLNNS
OLUNNS
NONE
(21)
,MAXLOCAT=max_locate_congestion_threshhold ,MAXLURU=ru_length
,MAXSSCPS=number_of_sscps ,MIHTMOUT=units_of_time ,MSGLEVEL= BASE
V4R1
V4R2
V4R3
V4R4
CS390
,MSGMOD= YES (22) ,NQNMODE= NAME
NO ,NNSPREF= NONE NQNAME
network_node_server
(23)
,NUMTREES=number_of_routing_trees OSIEVENT= ALL
NONE
(24)
PATTERNS
OSIMGMT= YES (25) ,PDTRCBUF=number_of_buffers
NO OSITOPO= ALLCDRSC
ILUCDRSC
,PIUMAXDS=calculation_factor ,PLUALMSG= SUPPRESS ,PPOLOG= YES
NOSUPP NO
PSRETRY=(low_tp_int,med_tp_int,high_tp_int,network_tp_int) ,PSSTRACE= NORB
IRB
SRB
BOTH
(26)
PSWEIGHT= EQUAL QDIOSTG= MAX ,RESUSAGE=usage_limit
LESSTHAN AVG
SAMEROUT MIN
NNN
(27)
,ROUTERES=resistance_value RSIRFMSG= ALLSSCP
OLUSSCP
NONE
,SAVERSCV= (,FREE) ,SAWMXQPK=calculation_factor
(,KEEP)
NO
(NO,FREE)
(NO,KEEP)
YES
(YES,FREE)
(YES,KEEP)
SAWDATA
(SAWDATA,FREE)
(SAWDATA,KEEP)
,SDLCMDRS= YES ,SIRFMSG= ALLSSCP
NO OLUSSCP
STATS NONE
NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS
,SLOWVAL= warn_time ,SLUALMSG= SUPPRESS ,SNAMGMT= YES
(warn_time,end_time) NOSUPP NO
(28) (29)
,SNVC=subnet_visit_count ,SORDER= ADJSSCP ,SRCHRED= OFF
APPN ON
APPNFRST
SUBAREA
(30) (31)
,SRCOUNT=number_of_search_requests ,SRTIMER=number_of_seconds
,SSCPORD= DEFINED ,SSDTMOUT=number_of_seconds
PRIORITY
(32)
,SSEARCH= YES ,SUPP= NOSUP
NO INFO
CACHE WARN
APPNFRST NORM
SER
,SWNORDER= CPNAME (33)
STATNID TCPNAME=tcp_job-name
(,FIRST)
(,ONLY)
(CPNAME ,FIRST)
,ONLY
(STATNID ,FIRST)
,ONLY
(34)
UNRCHTIM= unreachable_time UPDDELAY=maximum_time
(,partner_limit)
(unreachable_time,partner_limit)
(35)
,VARYWLD= FULLWILD VFYRED= YES VFYREDTI= OFF
NOWILD NO 0
OPERONLY reduction_timer
POAONLY
(36) (37)
,VOSDEACT= YES ,VRTG= YES ,VRTGCPCP= YES
NO NO NO
Notes:
1 API64R can be modified only when running in z/Architecture™ mode.
2 APPNCOS can be modified only if NODETYPE was specified during VTAM
START processing.
3 BNDYN can be modified only if BN=YES was specified during VTAM START
processing.
4 BNORD can be modified only if BN=YES was specified during VTAM START
processing.
5 CDSREFER can be modified only if NODETYPE=NN and CDSERVR=NO
were specified during VTAM START processing.
6 CMPMIPS is meaningful only if the value for CMPVTAM is greater than 1.
7 CONNTYPE can be modified only if NODETYPE was specified during
VTAM START processing.
8 CPCP can be modified only if NODETYPE was specified during VTAM
START processing.
9 DIRSIZE can be modified only if NODETYPE=NN was specified during
VTAM START processing.
10 DIRTIME can be modified only if NODETYPE=NN was specified during
VTAM START processing.
11 Due to the volume of messages that can be generated, it is not recommended
that this option be enabled during normal operation. Instead, it is
recommended that this option be enabled (using the MODIFY VTAMOPTS
command) on all necessary hosts only when trying to diagnose specific
problems. Once the problem has been diagnosed or documentation has been
collected, this option should be disabled once again (using the MODIFY
VTAMOPTS command).
12 The ENCRYPTN start option cannot be modified if ENCRYPTN=NO was
specified during VTAM START processing.
13 HOSTNAME can be modified only if NODETYPE was specified during
VTAM START processing. Displays of VTAM start options will show the new
value immediately; however, the new value will not be used until all
Enterprise Extender lines, whose GROUP definition statements do not have
HOSTNAME explicitly coded, are inactive. Any subsequent line activation
from the Enterprise Extender XCA major node, whose GROUP definition
statements do not have HOSTNAME explicitly coded, will make use of the
new HOSTNAME start option value. The IPADDR start option, if it is in
Note: VTAM only uses the CHPID value when building the IUTIQDIO
MPC group. To change CHPIDs for an active MPC group, the
following must be done:
1. All TCP/IP iQDIO (HiperSocket) devices must be stopped.
2. Make any necessary HCD/IOCDS changes.
3. Verify that new subchannel devices are varied online.
Note: In order to use iQDIO communications, the processor must have the
necessary hardware support. If the processor does not support iQDIO
communications, then modifications to this start option will not be
accepted and the IQDCHPID option will not be displayed (displayed
as ***NA***).
20 Due to the volume of messages that can be generated, it is not recommended
that this option be enabled during normal operation. Instead, it is
recommended that this option be enabled (using the MODIFY VTAMOPTS
command) on all necessary hosts only when trying to diagnose specific
problems. Once the problem has been diagnosed or documentation has been
collected, this option should be disabled once again (using the MODIFY
VTAMOPTS command).
21 MAXLOCAT can be modified only if NODETYPE was specified during
VTAM START processing.
22 NNSPREF can be modified only if NODETYPE=EN was specified during
VTAM START processing.
23 NUMTREES can be modified only if NODETYPE=NN was specified during
VTAM START processing.
24 OSIEVENT=PATTERNS is not valid when OSIMGMT=YES.
25 OSITOPO=ALLCDRSC is not valid when OSIMGMT=YES.
26 RESUSAGE can be modified only if NODETYPE=NN was specified during
VTAM START processing.
27 ROUTERES can be modified only if NODETYPE=NN was specified during
VTAM START processing.
28 SNVC can be modified only if BN=YES was specified during VTAM START
processing.
29 SORDER can be modified only if VTAM has been started as an interchange
node or a migration data host.
30 SRCOUNT is meaningful only when SRCHRED=ON.
31 SRTIMER is meaningful only when SRCHRED=ON.
32 SSEARCH can be modified only if NODETYPE=NN was specified during
VTAM START processing.
33 TCPNAME can be modified only if NODETYPE was specified during VTAM
START processing. 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.
34 UNRCHTIM is meaningful only if the NODETYPE start option is also used.
35 VFYREDTI can be modified only if NODETYPE=NN was specified during
VTAM START processing.
36 VRTG 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
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 z/OS
Communications Server: SNA Resource Definition Reference for descriptions of each of
the start options that you can change with this command.
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.
Operands
procname
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.
START command
Starting VTAM in an MVS environment:
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:
AFFDELAY=600
NETID=network_id SSCPID=sscp_id SSCPNAME=name
AFFDELAY=number_of_seconds
(1)
ALSREQ=NO API64R=YES APPNCOS=NONE
ALSREQ= YES API64R=NO APPNCOS=class-of-service_name
NO
(2)
AUTORTRY=AUTOCAP AUTOTI=0 BN=NO
AUTORTRY= AUTOCAP AUTOTI=time_period BN= NO
CDRM YES
ALL
NONE
(3) (4)
BNDYN=LIMITED BNORD=PRIORITY
BNDYN= LIMITED BNORD= PRIORITY
NONE DEFINED
FULL
BSCMDRS=(STATS,INOPS) BSCTMOUT=286
BSCMDRS= STATS BSCTMOUT=units_of_time
NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS
CACHETI=8
poolname= () CACHETI=number_of_minutes
Buffer Pool Values
(5)
CDRDYN=YES CDRSCTI=8M CDSERVR=NO
CDRDYN= NO CDRSCTI=timeout_value CDSERVR= YES
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
(8)
CONFIG=00 CONNTYPE=APPN CPCDRSC=NO
CONFIG= file_id CONNTYPE= APPN CPCDRSC= YES
file_name LEN NO
(9)
CPCP=LEASED CSALIMIT=0 CSA24=0
CPCP= YES CSALIMIT= value CSA24=value
NO (value )
LEASED ,F
SWITCHED
(10)
DATEFORM=MDY DIALRTRY=YES DIRSIZE=0
DATEFORM= MDY DIALRTRY= YES DIRSIZE=number_of_resources
DMY NO
YMD
(11)
DIRTIME=8D DISCNTIM=(15,0)
DIRTIME=time_period DISCNTIM=(time_period1,time_period2)
DLRORDER=(STATNID,FIRST)
,DLRORDER= STATNID
CPNAME
(,FIRST)
(,ONLY)
(CPNAME ,FIRST)
,ONLY
(STATNID ,FIRST)
,ONLY
(12)
DLRTCB=32 DLURSAW=YES
DLRTCB=number_of_task_control_blocks DLURSAW= YES
NO
(14)
DSIRFMSG=NONE DSPLYDEF=100
(13) DSPLYDEF=number_of_messages
DSIRFMSG= ALLSSCP
OLUSSCP
NONE
DSPLYMAX=65535 DSPLYWLD=FULLWILD
DSPLYMAX=number_of_messages DSPLYWLD= FULLWILD
NOWILD
OPERONLY
POAONLY
(15)
DUPDEFS=ALL DYNADJCP=YES DYNASSCP=YES
DUPDEFS= ALL DYNADJCP= YES DYNASSCP= YES
NONE NO NO
APPL
DEPLU
DYNDLGMD=NONE
DYNDLGMD= logmode_name (16)
NONE DYNHPPFX= prefix
ENHADDR=NO ESIRFMSG=ALLSSCP
ENHADDR= NO ESIRFMSG= ALLSSCP
YES OLUSSCP
NONE
EXPFLTRM=0 FLDTAB=ISTMSFLD
EXPFLTRM=expedited_flow_count FLDTAB= table_name
NONE
HOSTPU=ISTPUS
(18) HOSTPU=host_subarea_pu_name
HOSTNAME=fully_qualified_hostname
HOSTSA=1 HOTIOTRM=0
(19) HOTIOTRM=percentage_of_buffer_pool
HOSTSA=subarea_number
(20)
HPR=RTP HPRNCPBF=NO
HPR= ANR HPRNCPBF= YES
RTP NO
NONE
(RTP,ANR)
(RTP,NONE)
(ANR,NONE)
HPRPST=(8M,4M,2M,1M)
HPRPST=(low_limit,med_limit,high_limit,network_limit)
(21)
HSRTSIZE=9973 INITDB=ALL
HSRTSIZE=number_of_queue_pointers INITDB= ALL
DIR
TOPO
NONE
ALL ALL
INOPCODE=( ALL , ALL , DUMPENABLE
modulename inopcode DUMPDISABLE
DUMPDEFAULT
INOPDUMP=OFF IOINT=180
INOPDUMP= ON IOINT=number_of_seconds
(26)
OFF
IOMSGLIM=2147483647 IOPURGE=0
IOMSGLIM=number_of_message_pairs IOPURGE=timeout_value
(27)
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.
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 DLURSAW is meaningful only if the NODETYPE=NN start option is also
used.
13 Due to the volume of messages that can be generated, it is not recommended
that this option be enabled during normal operation. Instead, it is
recommended that this option be enabled (using the MODIFY VTAMOPTS
command) on all necessary hosts only when trying to diagnose specific
problems. Once the problem has been diagnosed or documentation has been
collected, this option should be disabled once again (using the MODIFY
VTAMOPTS command).
14 If the DSPLYMAX start option value is less than 100, that value is the default
for DSPLYDEF.
15 DYNADJCP is meaningful only if the NODETYPE start option is also used.
16 Two character prefix.
17 ENCRYPTN=CCA needs to be coded when Triple Des Encryption is desired.
18 HOSTNAME is meaningful only if the NODETYPE start option is also used.
If neither HOSTNAME nor IPADDR is specified on any of the GROUP
definition statements within the Enterprise Extender XCA major node, then
either the HOSTNAME, TCPNAME, or IPADDR start options must be
specified in order to activate an Enterprise Extender link. The HOSTNAME
start option specifies the default hostname to be used for name-to-address
resolution as part of activating an Enterprise Extender connection, and must
resolve at this node to a static VIPA address associated with a TCP/IP stack
at this node. If IPADDR is specified along with HOSTNAME on the START
command, the IPADDR value is ignored.
19 HOSTSA specifies the subarea number of this VTAM. If HOSTSA is not
coded, then a default subarea number of 1 is used.
IPINFO=SENDALL IQDCHPID=ANY
IPINFO= SENDALL (1)
SNDLOCAL IQDCHPID= ANY
DISPONLY NONE
NONE CHPID
(2)
IQDIOSTG=MAX IRNSTRGE=0 ISTCOSDF=INDLU
IQDIOSTG= MAX IRNSTRGE=size ISTCOSDF= ALL
AVG APPL
MIN DEPLU
INDLU
NONE
( APPL )
DEPLU
INDLU
(3)
LIST=00
LIMINTCP=number_of_seconds LIST=start_option_list_id
LSIRFMSG=NONE
(4) (5)
,LSIRFMSG= ALLNNS LISTBKUP= start_option_list_id
OLUNNS DEFAULTS
NONE PROMPT
MAINTLVL=maintenance_level
(6)
MAXLOCAT=5000 MAXLURU=6144
MAXLOCAT=max_locate_congestion_threshhold MAXLURU=ru_length
MAXSSCPS=10 MAXSUBA=15
MAXSSCPS=number_of_SSCPs MAXSUBA=maximum_subarea_number
MXSAWBUF=10000 MXSSCPRU=4096
MXSAWBUF=number_of_buffers MXSSCPRU=ru_length
(7)
NNSPREF=NONE
NNSPREF=network_node_server NODELST=name (8)
NODETYPE= EN
NN
NQNMODE=NAME
NQNMODE= NAME NSRTSIZE=( netid,size )
NQNAME
NUMTREES=100 OSIEVENT=PATTERNS
(9) OSIEVENT= ALL
NUMTREES=number_of_routing_trees NONE
PATTERNS
OSIMGMT=NO OSITOPO=(ILUCDRSC)
OSIMGMT= YES ALLCDRSC
NO OSITOPO=
ILUCDRSC
OSRTSIZE=43 PDTRCBUF=2
OSRTSIZE=number_of_queue_pointers PDTRCBUF=number_of_buffers
PIUMAXDS=200 PLUALMSG=NOSUPP
PIUMAXDS=calculation_factor PLUALMSG= SUPPRESS
NOSUPP
(10)
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)
(11) (12)
PSSTRACE=NORB QDIOSTG=MAX RESUSAGE=100
PSSTRACE= NORB QDIOSTG= MAX RESUSAGE=usage_limit
IRB AVG
SRB MIN
BOTH NNN
(13)
ROUTERES=128 RSIRFMSG=ALLSSCP
ROUTERES=resistance_value RSIRFMSG= ALLSSCP
OLUSSCP
NONE
SACONNS=YES SAVERSCV=(NO,KEEP)
SACONNS= NO SAVERSCV= (,FREE)
YES (,KEEP)
NO
(NO,FREE)
(NO,KEEP)
YES
(YES,FREE)
(YES,KEEP)
SAWDATA
(SAWDATA,FREE)
(SAWDATA,KEEP)
SAWMAXDS=100 SAWMXQPK=0
SAWMAXDS=calculation_factor SAWMXQPK=calculation_factor
SDLCMDRS=(STATS,INOPS) (14)
SDLCMDRS=YES SECLVLCP=ADAPT
SDLCMDRS= YES SECLVLCP= LEVEL1
NO LEVEL2
STATS ADAPT
NOSTATS
(,INOPS)
(,NOINOPS)
( STATS ,INOPS )
,NOINOPS
NOSTATS ,INOPS
,NOINOPS
SIRFMSG=ALLSSCP SLOWVAL=(0,0)
SIRFMSG= ALLSSCP SLOWVAL= warn_time
OLUSSCP (warn_time,end_time)
NONE
(15)
SNAPREQ=1000 SNVC=3
SNAPREQ=number_of_requests SNVC=subnet_visit_count
(16)
SONLIM=(60,30) SORDER=APPN
SONLIM= (percent_1,percent_2) SORDER= ADJSSCP
(percent_1) APPN
(,percent_2) APPNFRST
SUBAREA
(17)
SRCHRED=OFF SRCOUNT=10
SRCHRED= OFF SRCOUNT=number_of_search_requests
ON
(18) (19)
SRTIMER=30 SSCPDYN=YES
SRTIMER=number_of_seconds SSCPDYN= NO
YES
SSCPORD=PRIORITY SSDTMOUT=30
SSCPORD= DEFINED SSDTMOUT=number_of_seconds
PRIORITY
(20)
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,FIRST)
,SWNORDER= CPNAME (21)
STATNID TCPNAME=tcp_job-name
(,FIRST)
(,ONLY)
(CPNAME ,FIRST)
,ONLY
(STATNID ,FIRST)
,ONLY
(25)
NOTRACE,TYPE=BUF
(26)
TRACE,TYPE=BUF BUF Trace Operands
(25)
NOTRACE,TYPE=IO
(26)
TRACE,TYPE=IO IO Trace Operands
(25)
NOTRACE,TYPE=LINE
(26)
TRACE,TYPE=LINE LINE Trace Operands
(25)
NOTRACE,TYPE=MODULE
(26)
TRACE,TYPE=MODULE, MODULE Trace Operands
(25)
NOTRACE,TYPE=SIT
(26)
TRACE,TYPE=SIT SIT Trace Operands
(25)
NOTRACE,TYPE=SMS
(26)
TRACE,TYPE=SMS ,ID=VTAMBUF
(25)
NOTRACE,TYPE=STATE
(26)
TRACE,TYPE=STATE STATE Trace Operands
Notes:
1 The IQDCHPID option controls which IQD CHPID (and related subchannel
devices) VTAM selects to dynamically build the iQDIO (IUTIQDIO) MPC
group. The IUTIQDIO MPC group is used for TCP/IP dynamic XCF
communications within this zSeries system. Although this option can be
modified (and the modification will immediately be displayed) while the
IUTIQDIO MPC group is currently active, any modifications will have the
following effects:
v modified from ANY (or CHPID) to NONE — no effect on current usage
but blocks subsequent activations
v modified from NONE to ANY (or CHPID) — no effect on current usage
but allows subsequent activations
v modified from CHPID_X to CHPID_Y — no effect on current usage
Note: VTAM only uses the CHPID value when building the IUTIQDIO
MPC group. To change CHPIDs for an active MPC group, the
following must be done:
1. All TCP/IP iQDIO (HiperSocket) devices must be stopped.
2. Make any necessary HCD/IOCDS changes.
3. Verify that new subchannel devices are varied online.
4. Verify that the MPC group has deactivated (with no usage, it
times out after approximately two minutes).
5. Modify IQDCHPID=CHPID (to new CHPID).
6. Restart the TCP/IP iQDIO device or devices.
Note: In order to use iQDIO communications, the processor must have the
necessary hardware support. If the processor does not support iQDIO
communications, then modifications to this start option will not be
accepted and the IQDCHPID option will not be displayed (displayed
as ***NA***).
2 This option only affects iQDIO devices that use a MFS of 64k. The smaller
frame sizes will always use 126 SBALs. You can override this option on a
per-device basis via the READSTORAGE parameter on the LINK or
INTERFACE statement in the TCP/IP profile. Refer to z/OS Communications
Server: IP Configuration Reference for more details.
3 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.
4 Due to the volume of messages that can be generated, it is not recommended
that this option be enabled during normal operation. Instead, it is
recommended that this option be enabled (using the MODIFY VTAMOPTS
23 Code TRACE and its qualifiers on one line. Code the TYPE qualifier
immediately following TRACE.
24 NOTRACE,TYPE=VTAM is accepted but ignored. Tracing is started with the
default trace table size and the default options.
25 Do not use NOTRACE when starting VTAM, except to override a TRACE
start option coded in a predefined list.
26 Code TRACE and its qualifiers on one line. Code the TYPE qualifier
immediately following TRACE.
(2)
TRACE,TYPE=VTAM, VIT Operands
(1)
NOTRACE,TYPE=VTAM
TRANSLAT=(0,1,2,3,4,5,6,7)
TRANSLAT= value
()
( )
OLUALIAS
0
DLUREAL
1
DLUSSCP
2
COSNAME
3
LOGMODES
4
LUANAME
5
USERVAR
6
DLUALIAS
7
| (3) (4)
UNRCHTIM=(0,10) UPDDELAY=60
UNRCHTIM= unreachable_time UPDDELAY=max_time
(,partner_limit)
(unreachable_time,partner_limit)
(5)
VARYWLD=FULLWILD VERIFYCP=NONE
USSTAB=table_name VARYWLD= FULLWILD VERIFYCP= NONE
NOWILD OPTIONAL
OPERONLY REQUIRED
POAONLY
(6)
VFYRED=YES VFYREDTI=OFF
VFYRED= YES VFYREDTI= OFF
NO 0
reduction_timer
(7) (8)
VOSDEACT=NO VRTG=NO VRTGCPCP=YES
VOSDEACT= YES VRTG= YES VRTGCPCP= YES
NO NO NO
| (9)
VTAMEAS=32001 XCFINIT=YES
VTAMEAS=number_of_concurrent_sessions XCFINIT= NO
YES
DEFINE
XNETALS=NO
XNETALS= NO
YES
( , , , , ,
baseno bufsize slowpt F xpanno
, )
xpanpt xpanlim
,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
,COUNT=ALL (10)
,ID=line_name
,COUNT= ALL
number_of_bytes
,OPTION= ALL
option
(option)
( COMMAND )
CONNECTIONS
DEFINITION
INTERFACES
MANAGEMENT
NOEXIT
SESSION
,IDTYPE=RESOURCE
,IDTYPE= CP
SSCP
RESOURCE
OPTION Operand:
,OPTION= ALL
option
(option)
( ADJCP )
APPL
CDRM
CDRSC
GROUP
LINE
LNKST
LU
NCP
PU
,COUNT=ALL (10)
,ID=line_name
,COUNT= ALL
number_of_bytes
,TRACEPT=trace_point_id
Notes:
1 NOTRACE,TYPE=VTAM is accepted but ignored. Tracing is started with the
default trace table size and the default options.
2 Code TRACE and its qualifiers on one line. Code the TYPE qualifier
immediately following TRACE.
3 UNRCHTIM is meaningful only if the NODETYPE start option is also used.
4 UPDDELAY is meaningful only if the OSIMGMT=YES start option is also
used.
5 The VERIFYCP start option is meaningful only if the NODETYPE start option
is also used.
6 VFYREDTI is meaningful only if the NODETYPE=NN start option is also
used.
7 VRTG is meaningful only if the NODETYPE and HOSTSA start options are
also used.
8 VRTGCPCP is meaningful only if the NODETYPE and HOSTSA start options
are also used.
| 9 XCFINIT=YES is the default if VTAM is started as an APPN node (that is, the
| NODETYPE start option has been specified). XCFINIT=YES is not valid for
| pure subarea nodes. XCFINIT=DEFINE is the default if VTAM is started as a
| pure subarea node (the NODETYPE start option has not been specified).
10 COUNT applies only to the IBM 3720 and 3745 Communication Controllers.
VIT Operands:
,MODE=INT,SIZE=999,DSPSIZE=0
,BFRNUM=2
,MODE= EXT
,BFRNUM=number
INT
,SIZE=size ,DSPSIZE=dspsize
(1) (2)
,OPTION=(API,CIO,MSG,NRM,PIU,PSS,SMS,SSCP)
,SUBTRACE=ARBP,OPTION= HPR
ALL
(3)
(..,HPR,..)
,SUBTRACE= TGVC ,OPTION= SSCP
TREE ALL
(4)
(..,SSCP,..)
,OPTION= ALL
NONE
option
(option)
,
( API )
APPC
CFS
CIA
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.
3 If multiple trace options are coded in parentheses, HPR must be one of the
options coded inside the parentheses when SUBTRACE=ARBP is coded.
4 If multiple trace options are coded in parentheses, SSCP must be one of the
options coded inside the parentheses when SUBTRACE=TGVC or
SUBTRACE=TREE is coded.
Abbreviations
Operand Abbreviation
START S
AMOUNT=FULL AMT=F
AMOUNT=PARTIAL AMT=P
DATEFORM DATEFRM
Operand Abbreviation
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
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
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:
Therefore, if you use NET as the optional identifier on this command, you can
consistently use NET as procname for all VTAM commands.
options
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
z/OS 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.
,ACT Operands used with ACT
Acquire inactive NCP, and optionally its subordinate resources, and activate
them:
,LOADMOD=load_module_name
,SCOPE=COMP
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
line. An NCP or a peripheral physical unit attached to an NCP can be acquired as
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.
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
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:
– 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
,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.
LOADFROM Operand:
,LOADFROM=HOST,DUMPLOAD=NO,SAVEMOD=NO
,DUMPLOAD=NO ,SAVEMOD=NO
,LOADFROM= EXTERNAL
,DUMPLOAD= NO
YES
,DUMPLOAD=NO,SAVEMOD=NO
HOST
,SAVEMOD=NO
,DUMPLOAD= NO
,SAVEMOD= NO
YES
YES,SAVEMOD=YES
LOADSTA Operand:
,LOADSTA=
link_station_name
,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
(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.
,IDTYPE=RESOURCE ,SCOPE=COMP
VARY NET,ACT ,ID=name
,IDTYPE= CP ,SCOPE= ALL
RESOURCE COMP
ONLY
U
(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.
,LOADMOD=load_module_name
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
,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.
,SCOPE=COMP
VARY NET,ACT ,ID=group_name
,SCOPE=ALL
,SCOPE=COMP
,SCOPE=ONLY
,SCOPE=U
,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.
| Activate a model CDRSC and, optionally, all the clone CDRSCs created from it:
| ,SCOPE=COMP
VARY NET,ACT ,ID=model_cdrsc_name
,SCOPE= ALL
COMP
ONLY
U
|
| Abbreviations
Operand Abbreviation
VARY V
Operand Abbreviation
CPCP=NO CPCP=N
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
Purpose
The VARY ACT (activate) command activates VTAM resources. Figure 6 on page
528 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 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.
Figure 7 on page 529 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 529 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 7 on page 530.
/U
LY
N
O
A =X P CE
P/
LO PE SC UR
M
LL X
P
O
=A A
TY =S O
FC
/C
U PE NT
ID PE ES
DW PS D
ID PE P
LO M M
M P
O =SY
G DE
AD OD
M A
TY =C
TY =R
A TH
O OD
A A
AD O
C
G A
U O
AR P
LO FR
LO ST
VR TE
LO MO
R PA
ID PE
N ON
H CT
SA ME
D PL
W C
SC EM
SC PE
D P
LO D
AD
TG
A
EW
M
TY
S
PC
PR
PD
V
ID=
AN
N
ID
C
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
Enterprise Extender XCA major node
XCA(EE) Group
Nonswitched line
Link station
Switched line
XCF local SNA major node
XCF local SNA physical unit
CP name of XCF local SNA physical unit
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
Table 8 on page 531 and Table 9 on page 532 show the relationships between the
SAVEMOD and DUMPLOAD operands as they relate to the LOADFROM=HOST (
Table 8 on page 531) and LOADFROM=EXT ( Table 9 on page 532) operands.
SAVEMOD and DUMPLOAD (DUMPLD on PCCU) can be specified on either the
PCCU definition statement or the VARY ACT command. See the z/OS
Communications Server: SNA Resource Definition Reference for information about the
PCCU definition statement.
In Table 8 on page 531, Table 9 on page 532, and Table 10 on page 532, 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 7 on page
530.
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 7 on page
530.
v Hard disk refers to the hard disk on the IBM 3720 or 3745 Communication
Controller.
Table 10 on page 532 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.
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 7. 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).
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 550 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 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 8 on page 531 and Table 9 on page 532 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 10 on page 532.
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
device number 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
device number (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
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: 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.
Following is an example of an APPL major node definition to show how
application names can be network-qualified:
x APPL ACBNAME=y,...
To activate the dynamic local SNA major node for XCF connections, specify
ID=ISTLSXCF.
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. ISTTRL is the
name of the VTAM internal table that is used for dynamic TRLEs.
| If the resource is a model CDRSC, the state of the model CDRSC becomes
| active. This means that the model CDRSC is available to build clone CDRSCs.
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.
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 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 the existing CP-CP session is terminated. 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. If you choose not to activate
your own network node server list at end node initialization, a network node
server list consisting of a single nameless NETSRVR definition statement is
automatically activated by default.
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.
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: 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.
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 z/OS 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 8 on page 531 and Table 9 on page 532 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.
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 z/OS 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.
If both the RNAME and the device number 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 8 on page 531 and Table 9 on page 532 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). When the ID operand specifies a model CDRSC
| for the VARY ACT command, any existing inactive clone CDRSCs created
| from the model CDRSC are activated again.
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:
– 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
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)
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 11.
Table 11. Active and inactive status requirements for dynamic reconfiguration of an NCP
Operation 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
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 z/OS Communications Server: SNA Resource Definition
Reference.
This command adds and deletes LUs for local SNA major nodes.
The active and inactive requirements for the reconfiguration operations are
shown in Table 12 on page 548.
Table 12. 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.
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 z/OS 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, LU, and CDRSC definition statements in the following active nodes:
v Cross-domain resource major node
v Local SNA major node
v NCP major node (VTAM-only operands)
v Switched major node
See the major node descriptions in the z/OS 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 528) 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 z/OS
Communications Server: SNA Network Implementation Guide.
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).
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.
|
| VARY AUTOLOG command
| VARY NET,AUTOLOG ,ID=*
,ID=controlling_appl
|
| Abbreviations
|| Operand Abbreviation
| VARY V
|
| Purpose
| The VARY AUTOLOG command can be used to initiate sessions for one specific
| controlling application or for all controlling applications that have pending
| autologon requests. If the specified controlling application or applications are
| found and are available for sessions, a session initiation request is generated for
| each SLU that has an automatic logon relationship to that application (if the SLU is
| available for sessions and does not already have an active session to the controlling
| application). If a controlling application is not found or is not available for
| sessions, no attempt is made to initiate automatic logon sessions at this time.
| The VARY AUTOLOG command displays the number of searches that were sent to
| locate the controlling applications. When each search for a controlling application
| completes, a message is displayed that shows the number of sessions that were
| initiated to that application (if it was found and available for sessions) or the status
| of that application (if it was not found or was not available for sessions).
| If the controlling application is not session capable at the time the command is
| issued, all SLUs that are session capable, not in session, and have pending
| autologon requests with that controlling application are subject to future automatic
| logon events (AUTOTI, AUTORTRY, or PLU notification) for that controlling
| application.
| Refer to z/OS Communications Server: SNA Network Implementation Guide for more
| information on AUTOLOGON.
| Operands
| ID Specifies the name of the controlling application to be acted upon.
| The ID operand is required for this command. Wildcard values cannot be used
| for this operand.
| ID=controlling_appl
| Specifies the real or alias name of a controlling application for which there
| are one or more resources with pending autologon requests. The
| controlling_appl value can be network qualified. If the controlling_appl value
| is not network qualified, then the network ID of the host from which the
| command was issued is used.
| ID=*
| Specifies that all controlling applications for which there are one or more
| resources with pending autologon requests are acted upon.
| Tip: You can use the DISPLAY AUTOLOG command to determine which
| controlling applications have resources with pending autologon requests.
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.
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.
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.
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
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 z/OS
Communications Server: SNA Network Implementation Guide. For information on
creating a DR file, see the z/OS 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.
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 13 on page 557.
Table 13. 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 z/OS Communications Server: SNA Resource Definition Reference.
This command adds and deletes LUs for local SNA major nodes.
The active and inactive requirements for the reconfiguration operations are shown
in Table 14 on page 558.
Table 14. 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.
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.
Notes:
1. VARY HANGUP only terminates the switched connection; it does not
deactivate the line or the physical unit.
2. If the existing connection is for Enterprise Extender and DWINOP=YES is
specified on the switched PU definition on the remote host, the remote host
will attempt to redial the partner on this host when the VARY HANGUP
command is issued on this host. If the VARY HANGUP command successfully
places the switched PU in connectable state, then the dial-in from the remote
host will be accepted and the connection will be reestablished.
Issuing VARY INACT for the switched PU will prevent this from occurring
unless VARY ACT is then issued for the switched PU before either all dial
retries by the remote host have completed or VARY INACT is issued for the
switched PU on the remote host to terminate the redial attempts. Refer to the
descriptions of the DWINOP, REDIAL, and REDDELAY operands in z/OS
Communications Server: SNA Resource Definition Reference for details.
In addition, coding CALL=OUT on the Enterprise Extender PATH statement
under the PU, or ANSWER=OFF on the GROUP statement in the XCA major
node to which the PATH statement applies, will prevent inbound dial attempts
from being successfully directed to this PU.
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.
,CDLINK=ACT ,RMPO=NO
VARY NET,INACT ,ID=ncp_name
,CDLINK= ACT ,RMPO= NO
INACT YES
,TYPE= FORCE
IMMED
REACT
UNCOND
,TYPE= FORCE
IMMED
UNCOND
,DELETE=NO
VARY NET,INACT ,ID=node_name
,DELETE= NO ,IDTYPE=CP
YES
,TYPE= FORCE
IMMED
UNCOND
(1) ,FINAL=NO
VARY NET,INACT ,ID=dlur_name
,FINAL= NO
YES
,TYPE= FORCE
GIVEBACK
IMMED
UNCOND
Notes:
1 Depending on the value of the VARYWLD start option, wildcard values can
be used for this operand.
,FINAL=NO
VARY NET,INACT ,ID=pu_name
,FINAL= NO
,TYPE= FORCE
IMMED
REACT
UNCOND
YES
,TYPE= FORCE
IMMED
UNCOND
,ID=rtp_pu_name ,TYPE=FORCE
Deactivate a model application and all the APPLs created from it:
| Deactivate a model CDRSC and, optionally, all the clone CDRSCs created from
| it:
| ,DELETE=NO
|
,SCOPE=ALL ,DELETE= NO
YES
|
| ,DELETE=value_of_DELETE_operand_on_model_CDRSC
|
,DELETE= NO
YES
|
| 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
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 z/OS Communications Server: SNA Network
Implementation Guide.
Figure 8 on page 565 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.
VARY INACT
ND
CT CO
CT
NO
TY IMM ACK
P
N
FI TE= /INA
P
FC
=R D/U
PE /NO
PE SC
S/
/N
=G CE
PE IVEB
P
PO XC
CT
YE
E
VE ES
TY = C
TY ES
TY = S
EA
S
R
DE K=A
TY SES
=
TY FO
SA =Y
Y
PE
L=
=
LIN
PE
LE
PE
PE
NA
RM
CD
TY
ID=
ID
ID
ID
Adjacent CP major node
F Application program major node
F Application program minor node
F Model Application
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
F XCA (EE) Group
XCF local SNA major node
XCF local SNA physical unit
CP name of XCF local SNA physical unit
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 z/OS
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 z/OS 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
document for the specific effects of a DACTPU type hex 01 command on a
Note: VTAM will save an internal indicator that will prevent the DLUR
from opening a CPSVMGR session with VTAM. Any attempt to
establish a DLUS/DLUR CPSVRMGR session will be rejected with
sense code 080A000D. The operator can enable the DLUR again by
issuing a VARY ACT on the DLUR CDRSC.
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.
Abbreviations
Operand Abbreviation
VARY V
END=YES 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.
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.
,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.
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.
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
540 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
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 528 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, cloned from a model CDRSC, 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.
| If the ID operand specifies a model CDRSC, then future clone CDRSCs built
| using the model are affected by this operation. To affect an existing clone
| CDRSC, issue the VARY LOGON command against that clone CDRSC.
| If the ID operand specifies a CDRSC major node, then all the CDRSCs in that
| major node are affected. That includes conventionally defined CDRSCs, model
| CDRSCs, and clone CDRSCs.
LOGMODE=logon_mode_name
Specifies the name of the logon mode entry to be used for any logon initiated
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.
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.
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.
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.)
| If the ID operand specifies a model CDRSC, then future clone CDRSCs built
| using the model are affected by this operation. To affect an existing clone
| CDRSC, issue the VARY NOLOGON command against that clone CDRSC.
| If the ID operand specifies a CDRSC major node, then all the CDRSCs in that
| major node are affected. That includes conventionally defined CDRSCs, model
| CDRSCs, and clone CDRSCs.
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 canceled by NOLOGON=NETA.CICS
or NOLOGON=CICS
v In NETA, LOGON=CICS can be canceled 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.
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.
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
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.)
,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
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).
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 z/OS 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
z/OS 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
document 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.
,TYPE=UNCOND
VARY NET,TERM ,LU1=lu_name
,LU2=lu_name ,TYPE= COND
,LU2=lu_name FORCE
,LU1=lu_name UNCOND
,PLU=plu_name
,SLU=slu_name
,SLU=slu_name
,PLU=plu_name
,SCOPE=ACT ,NOTIFY=YES
,SCOPE= ACT ,NOTIFY= NO
ALL YES
Q
,TYPE=UNCOND
VARY NET,TERM ,SID=session_id
,TYPE= COND
FORCE
UNCOND
,SCOPE=ACT ,NOTIFY=YES
,SCOPE= ACT ,NOTIFY= NO
ALL YES
Q
APPN
Abbreviations
Operand Abbreviation
VARY V
Purpose
The VARY TERM command may be used to terminate 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)
The VARY TERM command may be used to terminate an APPN search. The
command can identify one search for termination:
v A single search by its session identifier (SID)
You can use the “DISPLAY SESSIONS command” on page 231 to display the
sessions that are to be terminated with this command. If a session is displayed
with an A- session state, you may be able to terminate the session at this host by
issuing the VARY TERM command with the SCOPE=APPN operand coded. If this
is unsuccessful, issue VARY TERM from one of the session endpoints.
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.
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.
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, or VARY TERM,TYPE=UNCOND.
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.
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.
6. For SCOPE=APPN search request termination, the TYPE operand is
ignored.
TYPE=COND
Specifies conditional termination.
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.
Note: The logon manager is a VTAM application. Any similarity between VTAM
commands and logon manager commands is coincidental.
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.
Syntax notation
See “How to read a syntax diagram” on page xv for details on the operator
command syntax notation.
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 z/OS 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.
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.
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
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)
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
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.
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.
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.
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
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.
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.
| DISPLAY Command
BNCOSMAP
LUGROUPS
APPNTOSA
INOPDUMP
INOPCODE
ADJSSCPS
ADJCLUST
APINGDTP
DIRECTRY
AUTOLOG
APINGTP
GRAFFIN
CSDUMP
GROUPS
CSMUSE
CDRSCS
BFRUSE
CLSTRS
CONVID
EEDIAG
CDRMS
DLURS
ADJCP
APPLS
LMTBL
APING
CNOS
LINES
CPCP
DISK
CSM
EXIT
COS
EE
ID
DISPLAY Command Output
Access method control block (ACB name)
Actiove CSDUMP triggers
Active sessions
Adjacent cluster table definitions
Adjacent CP
Adjacent SSCP tables
Adjacent subarea address
Adjacent subarea node
APING session limit
APINGD instance limit
Application program
Application program name
APPN class-of-service
APPN class-of-service table
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
Enterprise Extender (Aggregate Information)
Enterprise Extender (Connection Information)
Enterprise Extender (General Information)
Exit routines
Expansion limit
Explicit route length
|
Figure 9. DISPLAY output cross reference (A-E) (Part 1 of 2)
DISPLAY Command
MAJNODES
SATOAPPN
VTAMSTOR
VTAMOPTS
SRCHINFO
SESSIONS
STATIONS
NCPSTOR
SNSFILTR
STORUSE
NETSRVR
TSOUSER
USERVAR
PENDING
PATHTAB
MODELS
RSCLIST
TRACES
TNSTAT
SAMAP
TERMS
ROUTE
TABLE
PATHS
STATS
TGPS
TOPO
RTPS
TRL
DISPLAY Command Output
Access method control block (ACB name)
Active sessions
Adjacent cluster table of definitions
Adjacent CP
Adjacent SSCP tables
Adjacent subarea address
Adjacent subarea node
APINGD instance limit
Application program
Application program name
APPN class-of-service
APPN class-of-service table
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 support
Elapse time (ETIME)
Element address
Exit routines
Expansion limit
Explicit route length)
Explicit route (ER) number
| DISPLAY Command
BNCOSMAP
APPNTOSA
LUGROUPS
INOPDUMP
ADJSSCPS
INOPCODE
ADJCLUST
APINGDTP
DIRESTRY
AUTOLOG
APINGTP
GRAFFIN
CSDUMP
GROUPS
CSMUSE
CDRSCS
BFRUSE
CLSTRS
CONVID
EEDIAG
CDRMS
DLURS
ADJCP
LMTBL
APPLS
APING
LINES
CNOS
CPCP
DISK
CSM
EXIT
COS
EE
DISPLAY Command Output
ID
Generalized PIU trace (GPT)
Generalized TG (GTG)
Generic Resource information
Group identifier (GID)
Hostname
HPR Route Test
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)
DISPLAY Command
MAJNODES
VTAMSTOR
VTAMOPTS
SATOAPPN
SRCHINFO
SESSIONS
STATIONS
TSOUSER
NCPSTOR
SNSFILTR
USERVAR
STORUSE
NETSRVR
PENDING
PATHTAB
RSCLIST
MODELS
TRACES
TNSTAT
SAMAP
TERMS
ROUTE
TABLE
PATHS
STATS
TOPO
TGPS
RTPS
TRL
DISPLAY Command Output
Generalized PIU trace (GPT)
Generated TG (GTG)
Generic Resource information
Group identifier (GID)
HPR route test
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
| DISPLAY Command
BNCOSMAP
LUGROUPS
APPNTOSA
ADJSSCPS
ADJCLUST
INOPDUMP
INOPCODE
APINGDTP
DIRECTRY
AUTOLOG
APINGTP
GRAFFIN
CSDUMP
GROUPS
CDRSCS
CSMUSE
BFRUSE
CLSTRS
CONVID
EEDIAG
CDRMS
ADJCP
DLURS
APPLS
LMTBL
APING
CNOS
LINES
CPCP
DISK
CSM
COS
EXIT
EE
ID
DISPLAY Command Output
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)
Transmission statistics
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)
DISPLAY Command
MAJNODES
VTAMSTOR
VTAMOPTS
SATOAPPN
SRCHINFO
SESSIONS
STATIONS
SNSFILTR
TSOUSER
NCPSTOR
NETSRVR
STORUSE
USERVAR
PENDING
PATHTAB
MODELS
RSCLIST
TRACES
TNSTAT
SAMAP
ROUTE
TERMS
PATHS
TABLE
STATS
TOPO
TGPS
RTPS
TRL
DISPLAY Command Output
Path identifier (PID)
Physical unit (PU)
Physical unit name
Primary LU
Resource use count
RTP information
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
Tuning statistics information
USERVAR class
USERVAR name
USERVAR type
VCNS user
Virtual route number
VTAM internal trace
Many RFCs are available online. Hardcopies of all RFCs are available from the
NIC, either individually or by subscription. Online copies are available using FTP
from the NIC at http://www.rfc-editor.org/rfc.html.
where:
v nnnn is the RFC number.
v TXT is the text format.
v PS is the postscript format.
You can also request RFCs through electronic mail, from the automated NIC mail
server, by sending a message to [email protected] with a subject line of
RFC nnnn for text versions or a subject line of RFC nnnn.PS for PostScript versions.
To request a copy of the RFC index, send a message with a subject line of
RFC INDEX.
z/OS information
| z/OS information is accessible using screen readers with the BookServer/Library
| Server versions of z/OS books in the Internet library at:
| www.ibm.com/servers/eserver/zseries/zos/bkserv/
Notices
IBM may not offer all of the products, services, or features discussed in this
document. 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:
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
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.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Site Counsel
IBM Corporation
P.O. Box 12195
3039 Cornwallis Road
Research Triangle Park, North Carolina 27709-2195
U.S.A
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,
IBM International Program License Agreement, or any equivalent agreement
between us.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM’s suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
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.
COPYRIGHT LICENSE:
Each copy or any portion of these sample programs or any derivative work must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights
reserved.
Permission to use, copy, modify, and distribute the M.I.T., Digital Equipment
Corporation, and Hewlett-Packard Corporation portions of this software and its
documentation for any purpose without fee is hereby granted, provided that the
above copyright notice appears in all copies and that both that copyright notice
and this permission notice appear in supporting documentation, and that the
names of M.I.T., Digital, and Hewlett-Packard not be used in advertising or
publicity pertaining to distribution of the software without specific, written prior
permission. M.I.T., Digital, and Hewlett-Packard make no representation about the
suitability of this software for any purpose. It is provided ″as is″ without express
or implied warranty.
Copyright © 1988, 1993 The Regents of the University of California. All rights
reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
Notices 617
2. Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement:
This product includes software developed by the University of
California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be
used to endorse or promote products derived from this software without
specific prior written permission.
Permission from the Regents of the University of California to use, copy, modify,
and distribute the ″Popper″ software contained herein for any purpose, without
fee, and without a written agreement is hereby granted, provided that the above
copyright notice and this paragraph and the following two paragraphs appear in
all copies. HOWEVER, ADDITIONAL PERMISSIONS MAY BE NECESSARY
FROM OTHER PERSONS OR ENTITIES, TO USE DERIVATIVES OR
MODIFICATIONS OF POPPER.
Copyright © 1983 The Regents of the University of California. All rights reserved.
Copyright © 1991, 1993 The Regents of the University of California. All rights
reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement:
This product includes software developed by the University of
California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be
used to endorse or promote products derived from this software without
specific prior written permission.
Export of this software from the United States of America may require a specific
license from the United States Government. It is the responsibility of any person or
organization contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this
software and its documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation,
and that the name of M.I.T. not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission. Furthermore
Notices 619
if you modify this software you must label your software as modified software and
not distribute it in such a fashion that it might be confused with the original M.I.T.
software. M.I.T. makes no representations about the suitability of this software for
any purpose. It is provided ″as is″ without express or implied warranty.
Export of this software from the United States of America may require a specific
license from the United States Government. It is the responsibility of any person or
organization contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this
software and its documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation,
and that the name of FundsXpress not be used in advertising or publicity
pertaining to distribution of the software without specific, written prior
permission. FundsXpress makes no representations about the suitability of this
software for any purpose. It is provided ″as is″ without express or implied
warranty.
Permission to use, copy, modify, and distribute this software for any purpose with
or without fee is hereby granted, provided that the above copyright notice and this
permission notice appear in all copies.
This library is free for commercial and non-commercial use as long as the
following conditions are adhered to. The following conditions apply to all code
found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the
SSL code. The SSL documentation included with this distribution is covered by the
same copyright terms except that the holder is Tim Hudson ([email protected]).
Copyright remains Eric Young’s, and as such any Copyright notices in the code are
not to be removed. If this package is used in a product, Eric Young should be
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement: ″This product includes cryptographic
software written by Eric Young ([email protected])″. The word ’cryptographic’
can be left out if the routines from the library being used are not cryptographic
related.
4. If you include any Windows specific code (or a derivative thereof) from the
apps directory (application code) you must include acknowledgement:
″This product includes software written by Tim Hudson ([email protected])″
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS’’ AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
The license and distribution terms for any publicly available version or derivative
of this code cannot be changed. i.e. this code cannot simply be copied and put
under another distribution license [including the GNU Public License.]
Permission to use, copy, modify, and distribute this software for any purpose with
or without fee is hereby granted, provided that the above copyright notice and this
permission notice appear in all copies.
Notices 621
Copyright © 2004 IBM Corporation and its licensors, including Sendmail, Inc., and
the Regents of the University of California. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this
software and associated documentation files (the ″Software″), to deal in the
Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, provided that the
above copyright notice(s) and this permission notice appear in all copies of the
Software and that both the above copyright notice(s) and this permission notice
appear in supporting documentation.
Except as contained in this notice, the name of a copyright holder shall not be used
in advertising or otherwise to promote the sale, use or other dealings in this
Software without prior written authorization of the copyright holder.
If you are viewing this information softcopy, photographs and color illustrations
may not appear.
You can obtain softcopy from the z/OS Collection (SK3T-4269), which contains
BookManager and PDF formats of unlicensed books and the z/OS Licensed
Product Library (LK3T-4307), which contains BookManager and PDF formats of
licensed books.
| Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
| United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks
of others.
Updates to documents are available on RETAIN® and in information APARs (info APARs). See
Appendix C, “Information APARs,” on page 609 for a list of the documents and the info APARs
associated with them.
Info APARs for z/OS documents are in the document called z/OS and z/OS.e DOC APAR and PTF
++HOLD Documentation which can be found at http://publibz.boulder.ibm.com:80/cgi-
bin/bookmgr_OS390/ BOOKS/ZIDOCMST/CCONTENTS.
Planning
Title Number Description
z/OS Communications Server: GC31-8771 This document is intended to help you plan for new IP for SNA
New Function Summary function, whether you are migrating from a previous version or
installing z/OS for the first time. It summarizes what is new in
the release and identifies the suggested and required
modifications needed to use the enhanced functions.
z/OS Communications Server: SC31-8885 This document is a high-level introduction to IPv6. It describes
IPv6 Network and Application concepts of z/OS Communications Server’s support of IPv6,
Design Guide coexistence with IPv4, and migration issues.
Operation
Title Number Description
z/OS Communications Server: IP SC31-8780 This document describes how to use TCP/IP applications. It
User’s Guide and Commands contains requests that allow a user to log on to a remote host
using Telnet, transfer data sets using FTP, send and receive
electronic mail, print on remote printers, and authenticate
network users.
z/OS Communications Server: IP SC31-8781 This document describes the functions and commands helpful in
System Administrator’s Commands configuring or monitoring your system. It contains system
administrator’s commands, such as TSO NETSTAT, PING,
TRACERTE and their UNIX counterparts. It also includes TSO
and MVS commands commonly used during the IP
configuration process.
z/OS Communications Server: SC31-8779 This document serves as a reference for programmers and
SNA Operation operators requiring detailed information about specific operator
commands.
z/OS Communications Server: SX75-0124 This document contains essential information about SNA and IP
Quick Reference commands.
Bibliography 627
Title Number Description
z/OS Communications Server: SC31-8828 This document describes the Common Management Information
CMIP Services and Topology Protocol (CMIP) programming interface for application
Agent Guide programmers to use in coding CMIP application programs. The
document provides guide and reference information about CMIP
services and the SNA topology agent.
Diagnosis
Title Number Description
z/OS Communications Server: IP GC31-8782 This document explains how to diagnose TCP/IP problems and
Diagnosis Guide how to determine whether a specific problem is in the TCP/IP
product code. It explains how to gather information for and
describe problems to the IBM Software Support Center.
z/OS Communications Server: GC31-6850 These documents help you identify an SNA problem, classify it,
SNA Diagnosis Vol 1, Techniques and collect information about it before you call the IBM Support
and Procedures and z/OS GC31-6851 Center. The information collected includes traces, dumps, and
Communications Server: SNA other problem documentation.
Diagnosis Vol 2, FFST Dumps and
the VIT
z/OS Communications Server: GC31-6852 These documents describe SNA data areas and can be used to
SNA Data Areas Volume 1 and read an SNA dump. They are intended for IBM programming
z/OS Communications Server: GC31-6853 service representatives and customer personnel who are
SNA Data Areas Volume 2 diagnosing problems with SNA.
Bibliography 629
630 z/OS V1R7.0 Comm Svr: SNA Operation
Index
A APPNCOS start option
displaying 315
accessibility 613 modifying 489
ACT operand setting 497
VARY ACQ command 518 ASIRFMSG start option
VARY ANS command 550 displaying 315
VARY LOGON command 575 modifying 489
ACTION operand setting 497
MODIFY ALSLIST command 334 ASLTAB (associated LU table)
MODIFY DUMP command 375 displaying 269
MODIFY LOAD command 403 modifying resource associations 451
MODIFY RESOURCE command 434 ASRCVLM operand
ACTIVATE operand MODIFY RESOURCE command 434
MODIFY DR command 370 associated LU table (ASLTAB)
activating resources 526 displaying 269
adaptive data compression 349 modifying resource associations 451
adding resources ASYDE start option
See dynamic reconfiguration (DR) displaying 315
ADDR operand setting 497
DISPLAY NCPSTOR command 195 AUTHLEN start option
MODIFY DR command 370 displaying 315
ADDRESS operand modifying 489
DISPLAY VTAMSTOR command 324 setting 497
adjacent control point, displaying 17, 138 automatic activation of link stations 542, 545
adjacent link station list, modifying 333 automatic logon relationship
adjacent nodes, displaying 286 deleting 577
adjacent SSCP tables, displaying 21 effect on session termination 587
ADJLIST operand establishing or changing 574
DISPLAY ADJSSCPS command 21 AUTORTRY start option
MODIFY RESOURCE command 434 displaying 315
ADJSUB operand modifying 489
DISPLAY PATHTAB command 203 setting 497
AFFDELAY start option 489 AUTOSES operand
ALSNAME operand MODIFY DEFINE command 362
MODIFY NOTRACE command 417 AUTOTI start option
MODIFY TRACE command 468 displaying 315
ALSREQ start option modifying 489
displaying 315 setting 497
modifying 489
setting 497
AMOUNT operand
MODIFY TRACE command 469 B
ANS operand BFRNUM operand
VARY ACT command 533 MODIFY TRACE command 469
VARY ANS command 550 BLOCKED operand 207
API64R start option BN start option
displaying 318 displaying 315
modifying 489 modifying 489
setting 497 setting 497
APPC operand BNDYN start option
MODIFY USERVAR command 486 displaying 315
APPL operand modifying 489
DISPLAY STORUSE command 264 setting 497
application jobs BNORD start option
displaying storage usage for 264 displaying 315
application programs modifying 489
displaying 38 setting 497
displaying APPL major node 138 BSCMDRS start option
displaying storage usage for 264 displaying 315
APPNCOS operand modifying 489
DISPLAY TOPO command 285 setting 497
Index 633
DISPLAY CSM command 83 DRAINL operand
DISPLAY DIRECTRY command 91 MODIFY CNOS command 347
DISPLAY DISK command 95 DRAINR operand
DISPLAY DLURS command 97 MODIFY CNOS command 347
DISPLAY EE command 98 DRESPL operand
DISPLAY EEDIAG command 108 MODIFY DEFINE command 363
DISPLAY EXIT command 118 DSPLYDEF start option
DISPLAY GRAFFIN 121 displaying 315
DISPLAY GROUPS command 123 modifying 489
DISPLAY ID command 127 setting 497
DISPLAY INOPCODE command 175 DSPLYMAX start option
DISPLAY INOPDUMP command 177 displaying 315
DISPLAY LINES command 178 setting 497
DISPLAY LMTBL command 183 DSPLYWLD start option
DISPLAY LUGROUPS command 186 displaying 315
DISPLAY MAJNODES command 190 modifying 489
DISPLAY MODELS command 192 setting 497
DISPLAY NCPSTOR command 195 DSPNAME operand
DISPLAY NETSRVR command 197 DISPLAY STORUSE command 264
DISPLAY PATHS command 201 DUMP operand
DISPLAY PATHTAB command HALT CANCEL command 330
description 203 DUMPDS operand
versus DISPLAY ROUTE command 203 MODIFY DUMP command 376
DISPLAY PENDING command 205 DUMPLOAD operand
DISPLAY ROUTE command VARY ACT command 533
description 207 dumps
versus DISPLAY PATHTAB command 203 displaying 95
DISPLAY RSCLIST command 214 taking
DISPLAY RTPS 224 CSP 378
DISPLAY SATOAPPN command 230 MOSS 378
DISPLAY SESSIONS command 231 NCP 378
DISPLAY SNSFILTR command 240 DUMPSTA operand
DISPLAY SRCHINFO command 241 MODIFY DUMP command 376
DISPLAY STATIONS command 248 VARY ACT command 534
DISPLAY STATS command 253 DWACT operand
DISPLAY STORUSE command 263 VARY ACT command 534
DISPLAY TABLE command 269 DYNADJCP start option
DISPLAY TERMS command 273 displaying 315
DISPLAY TGPS command 278 setting 497
DISPLAY TNSTATP command 281 dynamic reconfiguration (DR)
DISPLAY TOPO command 282 MODIFY DR command 368
DISPLAY TRACES command 299 VARY ACT command 545
DISPLAY TRL command 307 VARY DRDS command 556
DISPLAY TSOUSER command 312 dynamic resources, warning about deactivating 568
DISPLAY USERVAR command 313 dynamic switched PUs and LUs, displaying model definitions
DISPLAY VTAMOPTS command 315 for 192
DISPLAY VTAMSTOR command 323 DYNASSCP start option
DLIMITS operand displaying 315
MODIFY DEFINE command 363 setting 497
DLOGMOD operand DYNDLGMD start option
MODIFY DEFAULTS command 360 displaying 315
MODIFY RESOURCE command 435 modifying 489
DLOGMOD value, predefined, modifying 359, 433 setting 497
DLRTCB start option DYNLU start option
displaying 315 displaying 315
setting 497 setting 497
DLU operand DYNMODTB start option
DISPLAY SRCHINFO command 243 displaying 315
DLURSAW operand modifying 489
displaying 315 setting 497
setting 497 DYNVNPFX start option 497
DNS, online information xx
DR (dynamic reconfiguration)
MODIFY DR command 368
VARY ACT command 545
E
ECHO operand
VARY DRDS command 556
DISPLAY APING command 29
Index 635
host CDRM, displaying 155 ID operand (continued)
host physical unit MODIFY CDRM command 341
displaying 141 MODIFY CNOS command 347
tracing 473 MODIFY COMPRESS command 350
HOSTNAME start option 497 MODIFY DEFAULTS command 360
HOSTPU start option MODIFY DEFINE command 364
displaying 315 MODIFY DIRECTRY command 366
setting 497 MODIFY DR command 371
HOSTSA start option MODIFY DUMP command 376
displaying 315 MODIFY ENCR command 380
setting 497 MODIFY EXIT command 383
HOTIOTRM start option MODIFY IMR command 387
displaying 315 MODIFY INFO command 592
modifying 489 MODIFY LINEDEF command 397
setting 497 MODIFY LL2 command 399
HPR operand MODIFY LOAD command 405
VARY ACT command 535 MODIFY MINLINK command 595
HPR start option MODIFY NEGPOLL command 410
displaying 315 MODIFY NOTRACE command 418
setting 497 MODIFY POLL command 428
HPRNCPBF start option MODIFY PROFILES command 430
displaying 315 MODIFY RESOURCE command 435
modifying 489 MODIFY RTP command 438
setting 497 MODIFY SECURITY command 441
HPRPST start option MODIFY SESSION command 443
displaying 315 MODIFY TABLE command 449
modifying 489 MODIFY TGP command 453
setting 497 MODIFY TOPO command 460
HSRTSIZE start option MODIFY TRACE command 470
displaying 315 MODIFY USERVAR command 487
setting 497 VARY ACQ command 519
VARY ACT command 535
VARY ANS command 550
I VARY DIAL command 555
VARY DRDS command 558
IBM Software Support Center, contacting xiv
VARY HANGUP command 559
ID operand
VARY INACT command 567
DISPLAY ADJCP command 17
VARY INOP command 573
DISPLAY APING command 29
VARY LOGON command 575
DISPLAY APPLS command 39
VARY NOLOGON command 577
DISPLAY CDRMS command 56
VARY PATH command 579
DISPLAY CDRSCS command 60
VARY REL command 583
DISPLAY CLSTRS command 66
IDTYPE operand
DISPLAY CNOS command 71
DISPLAY CLSTRS command 66
DISPLAY CONVID command 74
DISPLAY ID command 131
DISPLAY COS command 77
DISPLAY RSCLIST command 217
DISPLAY DIRECTRY command 91
DISPLAY TRACES command 302
DISPLAY DISK command 95
MODIFY NOTRACE command 419
DISPLAY EXIT command 118
MODIFY TRACE command 474
DISPLAY GROUPS command 123
VARY ACT command 537
DISPLAY ID command 129
VARY INACT command 568
DISPLAY LINES command 179
IMR (intensive mode recording) 387
DISPLAY LMTBL command 183
independent logical unit
DISPLAY LUGROUPS command 187
deactivating 566
DISPLAY MODELS command 192
displaying
DISPLAY NCPSTOR command 195
as CDRSC 60, 155
DISPLAY PATHS command 201
under PU that provides boundary function 134
DISPLAY PENDING command 205
dynamic reconfiguration 372
DISPLAY RSCLIST command 216
modifying
DISPLAY STATIONS command 249
entry in adjacent link station list 333
DISPLAY TABLE command 269
tracing 474
DISPLAY TERMS command 274
information APARs for IP-related documents 609
DISPLAY TGPS command 278
information APARs for non- document information 610
DISPLAY TOPO command 285
information APARs for SNA-related documents 610
DISPLAY TRACES command 300
INITDB start option
DISPLAY TSOUSER command 312
displaying 315
DISPLAY USERVAR command 313
setting 497
MODIFY ALSLIST command 335
Index 637
logon interpret table (LOGTAB) MAX operand (continued)
displaying 269 DISPLAY CLSTRS command 67
modifying resource associations 452 DISPLAY DIRECTRY command 92
logon manager DISPLAY EXIT command 119
commands DISPLAY GROUPS command 124
displaying help for 591 DISPLAY ID command 132
entering 589 DISPLAY LINES command 179
procedure name 589 DISPLAY LUGROUPS command 187
where to enter 589 DISPLAY MAJNODES command 190
displaying resources 592 DISPLAY PATHTAB command 203
links, modifying minimum number of 595 DISPLAY PENDING command 205
purpose 589 DISPLAY RSCLIST command 219
starting 597 DISPLAY SESSIONS command 233
stopping 596 DISPLAY SRCHINFO command 244
logon mode table (MODETAB) DISPLAY STATIONS command 249
displaying 269 DISPLAY STATS command 256
modifying resource associations 452 DISPLAY STORUSE command 265
LOGON operand DISPLAY TABLE command 269
VARY ACT command 540 DISPLAY TERMS command 274
VARY LOGON command 576 DISPLAY TGPS command 278
logon, automatic DISPLAY TRL command 308
See automatic logon relationship DISPLAY USERVAR command 313
LOGTAB (logon interpret table) MAXLOCAT start option
displaying 269 displaying 315
modifying resource associations 452 modifying 489
LookAt message retrieval tool xx setting 497
LU (logical unit) MAXLURU start option
displaying 167 displaying 315
LU-mode table modifying 489
displaying 183 setting 497
modifying entries in 362 MAXSSCPS start option
LU1 operand displaying 315
DISPLAY SESSIONS command 232 modifying 489
DISPLAY SRCHINFO command 244 setting 497
VARY TERM command 585 MAXSUBA start option
LU2 operand displaying 315
DISPLAY SESSIONS command 233 setting 497
DISPLAY SRCHINFO command 244 MDLTAB (model name table)
VARY TERM command 585 displaying 269
LUGROUP major nodes, displaying 187 modifying resource associations 452
LUNAME operand MEMBER operand
DISPLAY CNOS command 71 MODIFY MEMBER command 594
DISPLAY CONVID command 75 message flooding prevention table (FLDTAB)
DISPLAY LMTBL command 183 displaying 269
MODIFY CNOS command 348 modifying resource associations 452
MODIFY DEFINE command 364 message retrieval tool, LookAt xx
messages
including module ID in 408
M modifying suppression level 444
MIHTMOUT start option
MAC operand
displaying 315
MODIFY SECURITY command 441
modifying 489
MACLNTH operand
setting 497
MODIFY SECURITY command 442
MINLINK operand
MACTYPE operand
MODIFY MINLINK command 595
MODIFY SECURITY command 442
minor node, displaying 128
maintenance operator subsystem (MOSS) dumps 375
MODE operand
MAINTLVL start option
MODIFY NOTRACE command 419
displaying 315
MODIFY TRACE command 475
setting 497
model LU groups, displaying 187
MAJNODE operand
model name table (MDLTAB)
DISPLAY RSCLIST command 219
displaying 269
major node, displaying 128, 190
modifying resource associations 452
MAX operand
model resources, displaying 192
DISPLAY ADJSSCPS command 22, 121
MODETAB (logon mode table)
DISPLAY APPLS command 39
displaying 269
DISPLAY CDRMS command 56
modifying resource associations 452
DISPLAY CDRSCS command 60
Index 639
Network Control Program (NCP) (continued)
major node, displaying 140
O
releasing 581 OLDALS operand
storage, displaying 195 MODIFY ALSLIST command 335
network controller (3710) line trace OLDTAB operand
See also line trace, NCP MODIFY TABLE command 449
displaying status of 302 OLU operand
starting 483 DISPLAY SRCHINFO command 245
stopping 426 OPTION operand
network node server list, displaying 197 DISPLAY VTAMOPTS command 319
network node servers, displaying 197, 286 MODIFY CSALIMIT command 353
network nodes, displaying 286 MODIFY DUMP command 377
NEWALS operand MODIFY EXIT command 384
MODIFY ALSLIST command 335 MODIFY IMR command 387
NEWNAME operand MODIFY LL2 command 400
MODIFY LOAD command 407 MODIFY NOTRACE command 419
NEWPATH operand MODIFY TABLE command 450
VARY ACT command 541 MODIFY TRACE command 476
NEWTAB operand MODIFY USERVAR command 487
MODIFY TABLE command 449 ORIG operand
NFRAMES operand DISPLAY TOPO command 288
MODIFY LL2 command 399 MODIFY TOPO command 460
NMVTLOG start option ORIGIN operand
displaying 315 DISPLAY ROUTE command 209
setting 497 MODIFY TABLE command 451
NNSPREF option OSA-Express
display vtamopts command 320 modify notrace command 418
modify vtamopts command 489 modify trace command 470
start command 497 OSIEVENT start option
node congestion, displaying 289 displaying 315
node type, displaying 289, 315 modifying 489
node, displaying 128 setting 497
NODELST start option OSIMGMT start option
displaying 315 displaying 315
setting 497 modifying 489
NODETYPE start option setting 497
displaying 315 OSITOPO start option
setting 497 displaying 315
NOLOGON operand modifying 489
VARY NOLOGON command 578 setting 497
NOPROMPT start option OSRTSIZE start option
setting 497 displaying 315
NOTIFY operand setting 497
MODIFY LOAD command 407 OWNER operand
VARY TERM command 585 DISPLAY CLSTRS command 67
NOTNSTAT start option DISPLAY LINES command 179
displaying 315 VARY ACQ command 519
setting 497 VARY REL command 583
NOTRACE start option OWNERID operand
setting 497 DISPLAY CSM command 83
NQNMODE start option ownership of resources, modifying 365
displaying 315
modifying 489
setting 497 P
NSRTSIZE start option PARMS operand
displaying 315 MODIFY EXIT command 384
setting 497 PASSWORD operand
NTRANS operand DISPLAY APING command 29
MODIFY LL2 command 399 PATH operand
NUM operand VARY PATH command 579
DISPLAY STATS command 256 PATHINFO operand 233
DISPLAY STORUSE command 265 paths, dial-out
NUMTREES start option displaying 201
displaying 315 making available or unavailable 579
modifying 489 PDTRCBUF start option
setting 497 displaying 315
modifying 489
Index 641
SAVESESS operand SIRFMSG start option
VARY INACT command 569 displaying 315
SAW (session awareness) data filter table modifying 489
modifying resource associations 452 setting 497
SAWMAXDS start option SIT (scanner interface trace)
displaying 315 displaying status of 302
setting 497 starting 483
SAWMXQPK start option stopping 426
displaying 315 SIZE operand
modifying 489 DISPLAY APING command 29
setting 497 MODIFY TRACE command 481
scanner interface trace (SIT) SLOWVAL start option
displaying status of 302 displaying 315
starting 483 modifying 489
stopping 426 setting 497
SCOPE operand SLU operand
DISPLAY ADJCLUST command 15 DISPLAY SESSIONS command 234
DISPLAY ADJCP command 17 VARY TERM command 587
DISPLAY ADJSSCPS command 22 SLUALMSG start option
DISPLAY APPLS command 39 displaying 315
DISPLAY BNCOSMAP command 53 modifying 489
DISPLAY CDRMS command 56 setting 497
DISPLAY CDRSCS command 61 SME buffer (EXIT) trace
DISPLAY CLSTRS command 67 displaying status of 302
DISPLAY DIRECTRY command 92 starting 483
DISPLAY GROUPS command 124 stopping 426
DISPLAY ID command 133 SMEAUTH start option
DISPLAY LINES command 180 displaying 315
DISPLAY LMTBL command 184 setting 497
DISPLAY LUGROUPS command 187 SMS (buffer use) trace
DISPLAY MODELS command 192 displaying status of 302
DISPLAY NETSRVR command 197 starting 483
DISPLAY RSCLIST command 219 stopping 426
DISPLAY SESSIONS command 234 SNA protocol specifications 607
DISPLAY STATIONS command 249 SNAPREQ start option
DISPLAY TABLE command 270 displaying 315
DISPLAY TERMS command 274 setting 497
MODIFY NOTRACE command 425 SNGSESLU operand
MODIFY TOPO command 460 MODIFY CNOS command 348
MODIFY TRACE command 481 SNVC start option
VARY ACT command 542 displaying 315
VARY TERM command 586 modifying 489
SDLCMDRS start option setting 497
displaying 315 SONLIM start option
modifying 489 displaying 315
setting 497 setting 497
SECLVLCP start option SORDER start option
displaying 315 displaying 315
setting 497 modifying 489
security profiles, updating 430 setting 497
servers, network node, displaying 197 SRCHRED start option
session awareness (SAW) data filter table displaying 315
modifying resource associations 452 modifying 489
session limits, modifying setting 497
MODIFY CNOS command 345 SRCLEAR operand
MODIFY SESSION command 443 MODIFY RESOURCE command 436
SESSION operand SRCOUNT operand
MODIFY SESSION command 443 MODIFY RESOURCE command 436
session status, displaying 232 SRCOUNT start option
sessions displaying 315
terminating 584 modifying 489
shortcut keys 613 setting 497
SID operand SRTIMER operand
DISPLAY SESSIONS command 234 MODIFY RESOURCE command 437
DISPLAY SRCHINFO command 245 SRTIMER start option
VARY TERM command 586 displaying 315
modifying 489
Index 643
traces UPDDELAY start option (continued)
displaying status of 300 setting 497
starting and modifying 468 USE operand
stopping 417 DISPLAY LINES command 181
trademark information 623 MODIFY LINEDEF command 397
TRANSLAT start option USERID operand
displaying 315 DISPLAY APING command 30
setting 497 USERVAR applications
transmission group (TG) information defining, changing, or deleting 486
displaying 283 displaying 313
transmission group (TG) profiles USS (unformatted system services) table
displaying 278 command syntax 14
modifying 453 displaying 269
transmission group (TG) trace modifying resource associations 452
displaying status of 302 USSTAB start option
starting 484 displaying 315
stopping 426 setting 497
transport resource list (TRL) UVEXIT operand
displaying 307 MODIFY USERVAR command 487
TRL (transport resource list)
displaying 307
TRLE operand
DISPLAY TRL command 308
V
VALUE operand
truncation of message text 408
MODIFY USERVAR command 488
TSO user ID
VARY ACQ command 517
displaying status of 312
VARY ACT command 521
TSO user trace
VARY ANS command 550
displaying status of 303
VARY AUTOLOG 551
starting 484
VARY DIAL command 555
stopping 427
VARY DRDS command 556
tuning statistics
VARY HANGUP command 559
starting the recording of 455
VARY INACT command 560
stopping the recording of 411
VARY INOP command 573
TYPE operand
VARY LOGON command 574
DISPLAY LMTBL command 184
VARY NOLOGON command 577
DISPLAY SRCHINFO command 245
VARY PATH command 579
DISPLAY STATS command 256
VARY REL command 581
DISPLAY TRACES command 302
VARY TERM command 584
DISPLAY VTAMSTOR command 325
VARYWLD start option
MODIFY CDRM command 341
displaying 315
MODIFY CHKPT command 342
modifying 489
MODIFY DR command 371
setting 497
MODIFY DUMP command 377
VERIFYCP start option
MODIFY NOTRACE command 425
displaying 315
MODIFY TABLE command 451
setting 497
MODIFY TOPO command 461
version and release of VTAM, displaying 315
MODIFY TRACE command 482
VFYRED start option
MODIFY USERVAR command 487
displaying 315
VARY INACT command 569
modifying 489
VARY REL command 583
setting 497
VARY TERM command 587
VFYREDTI start option
displaying 315
modifying 489
U setting 497
U operand virtual nodes, displaying 287
VARY ACT command 544 virtual route (VR)
ULPID operand displaying status of 203, 207
DISPLAY TRL command 308 VIT (VTAM internal trace)
unformatted system services (USS) table displaying status of 303
command syntax 14 starting 484
displaying 269 stopping 427
modifying resource associations 452 VOSDEACT start option
UPDATE operand displaying 317
VARY ACT command 545 modifying 489
UPDDELAY start option setting 497
displaying 315 VR (virtual route)
modifying 489 displaying status of 203, 207
W
WARM operand
VARY ACT command 549
WARM start option
displaying 315
setting 497
weight of node, displaying 289
wildcard network IDs
DISPLAY ADJCP command 17
DISPLAY ID command 130
MODIFY TGP command 453
wildcard resource names
DISPLAY APPLS command 39
DISPLAY CDRMS command 56
DISPLAY CDRSCS command 60
DISPLAY CLSTRS command 66
DISPLAY GROUPS command 124
DISPLAY LINES command 179
DISPLAY RSCLIST command 216
DISPLAY TERMS command 274
DISPLAY TGPS command 278
DISPLAY TOPO command 285
DISPLAY TRACES command 300
X
XCA (external communication adapter) major node
displaying 142
XCFINIT start option
displaying 315
setting 497
XLENGTH operand
DISPLAY VTAMSTOR command 326
XNETALS start option
displaying 315
setting 497
Index 645
646 z/OS V1R7.0 Comm Svr: SNA Operation
Communicating Your Comments to IBM
If you especially like or dislike anything about this document, please use one of
the methods listed below to send your comments to IBM. Whichever method you
choose, make sure you send your name, address, and telephone number if you
would like a reply.
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.
Printed in USA
SC31-8779-05
Spine information:
z/OS Communications Server z/OS V1R7.0 Comm Svr: SNA Operation Version 1 Release 7