Abstract for SNA Resource Definition Reference

Purpose of this information

This information presents the meaning and coding syntax of Virtual Telecommunications Access Method (VTAM®) resource definition statements and operands, NCP resource definition statements and operands that affect VTAM, start options, and macroinstructions and operands for user-defined tables. The information 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.

To plan for the tasks of installing VTAM and defining resources to it, see z/OS Communications Server: New Function Summary.

When you are ready to install VTAM and define resources to it, you can find the broader, more conceptual information about installation and definition in the z/OS Communications Server: SNA Network Implementation Guide.

This information contains the specifics of resource definition.

Who should read this information:

This document is intended to help system programmers define resources to VTAM.

How this information is organized:

This information consists of the following topics and appendixes:

Chapter 1, Introduction
This topic describes the symbols and coding conventions used for the definition statements and macroinstructions described in this information. Descriptions of the sift-down effect and each type of major node are also included.
Chapter 2, Major Nodes
This topic describes the VTAM definition statements used to define major nodes. Descriptions of NCP definition statements and their operands are given only when they affect VTAM.
Chapter 3, Routing and Dynamic Reconfiguration
This topic describes the VTAM definition statements used, in general, to define routes and to dynamically reconfigure and dynamically change resources.
Chapter 4, VTAM Start Options
This topic describes VTAM start options and how you can code them to set various conditions that are to exist while VTAM is running.
Chapter 5, User-Defined Tables and Data Filter
This topic describes how to create or modify the associated LU table, Class-of-Service table, CMIP services directory definition file, interpret table, logon mode table, message-flooding prevention table, model name table, and unformatted system services (USS) table. It also describes how to code the session awareness (SAW) data filter.
Appendix A, IBM®-Supplied Tables
This appendix contains listings of the IBM-supplied default tables.
Appendix B, Examples of USS Command Conversion
This appendix contains examples of how to code USS tables to convert commands.
Appendix C, VTAMTOPO Filter Option Reporting
This appendix summarizes the results of using the VTAMTOPO filtering option for reporting a switched PU under an NCP.
Architectural specifications
This appendix lists documents that provide architectural specifications for the SNA Protocol.
Information APARs and technotes
This appendix lists information APARs for IP and SNA documents.
Accessibility
This appendix describes accessibility features to help users with physical disabilities.
Notices
Contains notices and trademarks used in this document.
Bibliography
Contains descriptions of the documents in the z/OS® Communications Server library.

How to use this information:

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

To use this document, you should be familiar with the basic concepts of telecommunication, SNA, and VTAM.

Conventions and terminology that are used in this information

Commands in this information that can be used in both TSO and z/OS UNIX environments use the following conventions:

When describing how to use the command in a TSO environment, the command is presented in uppercase (for example, NETSTAT).
When describing how to use the command in a z/OS UNIX environment, the command is presented in bold lowercase (for example, netstat).
When referring to the command in a general way in text, the command is presented with an initial capital letter (for example, Netstat).

All the exit routines described in this information are installation-wide exit routines. The installation-wide exit routines also called installation-wide exits, exit routines, and exits throughout this information.

The TPF logon manager, although included with VTAM, is an application program; therefore, the logon manager is documented separately from VTAM.

Samples used in this information might not be updated for each release. Evaluate a sample carefully before applying it to your system.

Note: In this information, you might see the following Shared Memory Communications over Remote Direct Memory Access (SMC-R) terminology:

RoCE Express®, which is a generic term representing IBM 10 GbE RoCE Express, IBM 10 GbE RoCE Express2, and IBM 25 GbE RoCE Express2 feature capabilities. When this term is used in this information, the processing being described applies to both features. If processing is applicable to only one feature, the full terminology, for instance, IBM 10 GbE RoCE Express will be used.
RoCE Express2, which is a generic term representing an IBM RoCE Express2® feature that might operate in either 10 GbE or 25 GbE link speed. When this term is used in this information, the processing being described applies to either link speed. If processing is applicable to only one link speed, the full terminology, for instance, IBM 25 GbE RoCE Express2 will be used.
RDMA network interface card (RNIC), which is used to refer to the IBM® 10 GbE RoCE Express, IBM® 10 GbE RoCE Express2, or IBM 25 GbE RoCE Express2 feature.
Shared RoCE environment, which means that the "RoCE Express" feature can be used concurrently, or shared, by multiple operating system instances. The feature is considered to operate in a shared RoCE environment even if you use it with a single operating system instance.

Clarification of notes

Information traditionally qualified as Notes is further qualified as follows:

Attention: Indicate the possibility of damage
Guideline: Customary way to perform a procedure
Note: Supplemental detail
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
Result: Indicates the outcome
Tip: Offers shortcuts or alternative ways of performing an action; a hint

How to read a syntax diagram

This section describes how to read the syntax diagrams used in this book.

Read the diagrams from left-to-right, top-to-bottom, following the main path line. Each diagram begins on the left with double arrowheads (►►) and ends on the right with two arrowheads facing each other (►◄).
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.
Required operands and values appear on the main path line.

You must code required operands and values.

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

You can choose not to code optional operands and values.

If there is more than one mutually exclusive optional operand or value to choose from, they are stacked vertically in alphanumeric order below the main path line.
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.
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.
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).

If an operand or value can be abbreviated, the abbreviation is described in the text associated with the syntax diagram.
If a diagram shows a character that is not alphanumeric (such as parentheses, periods, commas, and equal signs), you must code the character as part of the syntax. In this example, you must code OPERAND=(001,0.001).
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).
Default operands and values appear above the main path line. VTAM uses the default if you omit the operand entirely.
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.
References to syntax notes appear as numbers enclosed in parentheses above the line. Do not code the parentheses or the number.
Notes:
- ¹ An example of a syntax note.
Some diagrams contain syntax fragments, which serve to break up diagrams that are too long, too complex, or too repetitious. Syntax fragment names are in mixed case and are shown in the diagram and in the heading of the fragment. The fragment is placed below the main diagram.

Syntax Fragment