| ALSREQ |
Whether adjacent link station names
are required to be in the default ALS list of independent LUs |
| AUTHLEN |
Whether VTAM® is enabled to pass transmission priority
from one LEN node to another |
| CONNTYPE |
Whether a LEN connection or an APPN
connection is established with type 2.1 PUs |
| CPCP |
The types of connections on which
CP-CP sessions are allowed with adjacent nodes |
| DISCNTIM |
Amount of time VTAM delays deactivation of SSCP-PU session
when there are no outstanding LU-LU session requests |
| DYNHPPFX |
Indicates if DYNHPPFX is not specified,
then dynamic PUs created for HPR will be prefixed with the three characters,
CNR. If DYNHPPFX=cc where cc is the two character prefix that you
want, then dynamic PUs created for HPR will be prefixed with the two
characters, cc. In these two cases, respectively, the dynamic PU names
will have the format of CNRxxxxx or ccxxxxxx. |
| DYNPUPFX |
Specifies a two character prefix
that is used in creating the dynamic PUs. This prefix will be used
when generating names for these dynamically built PUs. The prefix
defined by the start option will be used if DYNPUPFX is not coded
on the group statement for the line under which the PU is built. A
unique value will then be generated and concatenated to the defined
prefix to create an eight character PU name. |
| DYNVNPFX |
Specifies the prefix to be used when
generating the name for dynamic connection network PUs |
| ENSEMBLE |
Specifies whether this z/OS® Communications Server will permit connectivity
to the intraensemble data network (IEDN) and to the intranode management
network (INMN). Access to these networks is through OSA-Express3 or
later features that are configured in OSX and OSM modes. |
| HPR |
Specifies the level of High-Performance
Routing (HPR) support provided by VTAM |
| HPRNCPBF |
Specifies whether HPR can be used
although it may cause session data to travel through an NCP twice |
| IQDCHPID |
Specifies superfast connectivity replacing XCF
links |
| MPCACT |
Specifies whether activations of MPC subchannel
groups are to be suspended if the minimum number of read and write
subchannels is not available, either because they are offline or because
no valid path exists to the connecting host. VTAM automatically resumes activation when the
minimum number of subchannels becomes available. This option applies
only to MPC groups consisting of CTC connections. |
| NNSPREF |
Specifies the name of the preferred
network node server for this end node |
| SACONNS |
Specifies if subarea connections
will be used |
| SLOWVAL |
Specifies that a network node which
has been placed in a SLOWDOWN mode can now allow a maximum SLOWDOWN
time to be set |
| SNVC |
Maximum number of networks searched
for a resource by this border node |
| SSDTMOUT |
The amount of time that a switched
PU can go without a session before the connection is dropped |
| VRTG |
Whether virtual-route-based transmission
groups connections are requested when SSCP-SSCP session is established |
| VRTGCPCP |
Whether CP-CP sessions are supported
over the virtual-route-based transmission group |
| XCFGRPID |
Specifies the group ID suffix that VTAM will use when joining groups in the sysplex. VTAM will join groups ISTXCFvv and
ISTCFSvv, where vv is
the value provided with XCFGRPID |
| XCFINIT |
Specifies whether VTAM will join a sysplex group at VTAM initialization and establish the capability
for XCF connectivity to other VTAM nodes
in the sysplex |
| XNETALS |
Whether VTAM can establish sessions with LUs in adjacent
networks |