Abstract for SNA Network Implementation Guide

Purpose of this information: This document provides an understanding of the major concepts involved in implementing a VTAM® network and describes how to:
  • Install VTAM
  • Define network resources to VTAM
  • Replace user tables and exit routines
  • Tune VTAM for a specific environment

It also provides guidance for using VTAM resource definition statements and macroinstructions. Use this document when installing, upgrading, or otherwise changing a VTAM network. The information in this document supports both IPv6 and IPv4. Unless explicitly noted, information describes IPv4 networking protocol. IPv6 support is qualified within the text.

Who should read this information: System programmers who are familiar with the basic concepts of telecommunication, Systems Network Architecture (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 Start of changeIBM® 10 GbE RoCE Express, IBM 10 GbE RoCE Express2, and IBM 25 GbE RoCE Express2 feature capabilitiesEnd of change. 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.
  • Start of changeRoCE 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.End of change
  • Start of changeRDMA 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.End of change
  • 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 (►◄).
    Read syntax diagramSkip visual syntax diagramSyntax Diagram
  • 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.
    Read syntax diagramSkip visual syntax diagramFirst LineOPERAND1OPERAND2OPERAND3OPERAND4OPERAND5Second Line
  • Required operands and values appear on the main path line.
    Read syntax diagramSkip visual syntax diagramREQUIRED_OPERAND

    You must code required operands and values.

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

    Read syntax diagramSkip visual syntax diagramREQUIRED_OPERAND_OR_VALUE_1REQUIRED_OPERAND_OR_VALUE_2
  • Optional operands and values appear below the main path line.
    Read syntax diagramSkip visual syntax diagramOPERAND

    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.

    Read syntax diagramSkip visual syntax diagramOPERAND_OR_VALUE_1OPERAND_OR_VALUE_2
  • 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.
    Read syntax diagramSkip visual syntax diagram,REPEATABLE_OPERAND
  • 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.
    Read syntax diagramSkip visual syntax diagram,REPEATABLE_OPERAND_OR_VALUE_1REPEATABLE_OPERAND_OR_VALUE_2
  • 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).
    Read syntax diagramSkip visual syntax diagramOPERAND

    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).
    Read syntax diagramSkip visual syntax diagramOPERAND=( 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).
    Read syntax diagramSkip visual syntax diagramOPERAND=( 001 FIXED)
  • Default operands and values appear above the main path line. VTAM uses the default if you omit the operand entirely.
    Read syntax diagramSkip visual syntax diagramDEFAULTOPERAND
  • 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.
    Read syntax diagramSkip visual syntax diagramvariable
  • References to syntax notes appear as numbers enclosed in parentheses above the line. Do not code the parentheses or the number.
    Read syntax diagramSkip visual syntax diagramOPERAND1
    Notes:
    • 1 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.
    Read syntax diagramSkip visual syntax diagramReference to Syntax Fragment
    Syntax Fragment
    Read syntax diagramSkip visual syntax diagram1ST_OPERAND,2ND_OPERAND ,3RD_OPERAND