Abstract for SNA Programmer's LU 6.2 Reference

Purpose of this information

This manual is designed to help customers write VTAM® application programs to use the VTAM logical unit (LU) 6.2 application programming interface (API). This manual describes the format of the macroinstructions and presents each macroinstruction in alphabetical order.

This manual explains macro instruction syntax and parameters, return codes and responses, and identifies fields set by DSECTs.

Who should read this information

This book is for programmers (such as application or system programmers) who code VTAM application programs. This audience can include programmers who are modifying existing programs or writing new ones.

You should be familiar with LU 6.2 architecture before you write LU 6.2 programs.

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.

z/OS no longer supports mounting HFS data sets (The POSIX style file system). Instead, a z/OS File System (ZFS) can be implemented. The term hierarchical file system, abbreviated as HFS, is defined as a data structure that has a hierarchical nature with directories and files. References to hierarchical file systems or HFS might still be in use in z/OS Communications Server publications.

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, IBM 25 GbE RoCE Express2, IBM 10 GbE RoCE Express3, and IBM 25 GbE RoCE Express3 feature capabilities. When this term is used in this information, the processing being described applies to all of these 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.
  • RoCE Express3, which is a generic term representing an IBM RoCE Express3 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 Express3 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, IBM 25 GbE RoCE Express2, IBM 10 GbE RoCE Express3, or IBM 25 GbE RoCE Express3 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