Problem(Abstract)

Publication updates for the z/OS V1R8 Communications Server SNA Resource Definition Reference.

Resolving the problem

In Chapter 2. Major nodes, Application program major node, section Full syntax, APPL, replace the syntax for ENCR with the following:


In Chapter 2. Major nodes, Application program major node, Operand descriptions, ENCR, replace the syntax with the following:


================================================
In Chapter 2. Major nodes, section Cross Domain resource (CDRSC) Major node, LUALIAS, add a restriction following the second to last paragraph:

LUALIAS is optional for cross-network or cross-domain resources predefined with the NETWORK definition statement. If it is not defined and there are duplicate names in the SNA network interconnection, application programs can use the network-qualified name [if PARMS=(NQNAMES=YES) is specified on the ACB macroinstruction] or any of the other types of alias name translation, such as:

• Alias name translation with NetView
• Session management exit routine
• USERVAR

Restriction: LUALIAS does not work in combination with ALIAS name translation (regardless of whether translation is performed by NetView or the Session Management Exit). If an ALIAS name is received on a session setup request from a resource that is predefined as a CDRSC with an LUALIAS, then the received ALIAS name is presented to local applications, rather than the predefined LUALIAS name.

================================================
In Chapter 2. Major nodes, Network control program (NCP) major node, DYNPU, remove the following bullet from the bulleted list:

• CPCP=YES

In Chapter 2. Major nodes, External communication adapter (XCA) major node, DYNPU, remove the following bullet from the bulleted list:

• CPCP=YES

=================================================
In Chapter 4. Start options, MIHTMOUT, in the row for "dependencies:", replace "does not apply to MPC" with "See Note". Also, replace the fist sentence of the Note with the following:

Note: Except for subarea sweep processing, this start option does not apply to attachments between two hosts that use the multipath channel (MPC) feature.
=================================================
In Chapter 4. Start options, Coding VTAM start options, Start options syntax diagrams, add the following start option alphabetically:

In Chapter 4. Start options, Table 61. Start options that define APPN characteristics, insert the following row in alphabetical order:

HPRCLKRT

Specifies whether the HPR clock rate runs in standard or adaptive mode. These modes control how reactive VTAM is to the packet loss that occurs on RTP pipes that run over Enterprise Extender.

In Chapter 4. Start options, Table 60. Start options that affect performance and tuning, insert the following row in alphabetical order:

HPRCLKRT

Specifies whether the HPR clock rate runs in standard or adaptive mode. These modes control how reactive VTAM is to the packet loss that occurs on RTP pipes that run over Enterprise Extender.

In Chapter 4. Start options, Descriptions of start options, add the following start option in alphabetical order:

HPRCLKRT

The HPR clock is the mechanism that processes the timer requests for all RTP pipes. The HPRCLKRT start option specifies whether the HPR clock runs in standard or adaptive mode. These modes control how reactive VTAM is to the packet loss that occurs on RTP pipes that run over Enterprise Extender.
Guideline: Use the default value HPRCLKRT=STANDARD when you are not running Enterprise Extender.

HPRCLKRT=ADAPTIVE
Specifies that the HPR clock operates in adaptive mode. Running the HPR clock in adaptive mode enables the clock to toggle between standard and high modes of operation when the clock is servicing RTP pipes that are experiencing packet loss. When packet loss occurs, the clock speed adapts and runs in high mode. The RTP pipes that are experiencing packet loss are scheduled more frequently, which enables the RTP pipes to recover more quickly. When packet loss is no longer occurring, the clock returns to the standard mode.

The adaptive mode increases the overall performance of RTP pipes when packet loss is occurring. However, RTP performance and CPU overhead are system dependent and might vary. There might be some CPU overhead when the HPR clock runs in high mode.

Restriction: If you code HPRCLKRT=ADAPTIVE, the following restrictions apply:

• This mode is meaningful only in Enterprise Extender configurations that have an access speed with a defined capacity of 1Gb or higher.
• Do not use this mode for uniprocessor configurations or in configurations that are CPU bound.

HPRCLKRT=STANDARD
Specifies that the HPR clock is to operate in standard mode. The HPR clock will run at the standard interval to service RTP pipes. Standard mode is the default mode for the HPR clock rate.
===========================
In Chapter 2. Major nodes, Switched major node, Operand descriptions, HOSTNAME, add a Note to the list as follows:

4. See z/OS Communications Server: IP Configuration Guide for required security definitions.

In Chapter 2. Major nodes, External communication adapter (XCA) major node, Operand descriptions, HOSTNAME, add a Note to the list as follows:

5. See z/OS Communications Server: IP Configuration Guide for required security definitions.

In Chapter 4. Start options, Descriptions of start options, HOSTNAME, add a Note to the list as follows:

10. See z/OS Communications Server: IP Configuration Guide for required security definitions.
=========================
In Chapter 4. Start options, TRACE for MODULE, STATE (with OPTION), or VTAM internal trace, replace the second Note with the following:

You can code TRACE and its qualifiers through position 71, even if you are in the middle of the start option. The remainder of the item can be continued in the next record. Code the TYPE qualifier immediately following TRACE.

=========================
In Chapter 4. Start options, Coding VTAM start options, Start options syntax diagrams, add the following syntax in alphabetical order:

Notes:
(x) TOPOTIME is meaningful only if the NODETYPE start option is also used.

In Chapter 4. Start options, Summary of start options, APPN start options, Table 61. Start options that define APPN characteristics, add the following row alphabetically:



In Chapter 4. Start options, Descriptions of start options, add TOPOTIME in alphabetical order:



====================
In Chapter 4. VTAM start options, Summary of start options, add MPCACT to the Connectivity start options table as follows:



In Chapter 4. VTAM start options, Descriptions of start options, add MPCACT alphabetically:



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. At least one read device and one
write device are needed to activate an MPC group.

MPCACT=WAIT
Specifies that VTAM is to suspend activations of MPC
subchannel groups 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.

MPCACT=NOWAIT
Specifies that VTAM is to fail activations of MPC subchannel
groups if the minimum number of read and write subchannels is
not available. The system operator must manually retry these
activations after the minimum number of subchannels becomes
available.
====================                                             
In Chapter 2. Major nodes, Transport Resource List, modify the Transport Resource List major node full syntax
as follows:
a. Update the existing PORTNAME operand
b. Add the new PORTNUM operand



====================
Under Operand Descriptions, modify the existing PORTNAME
operand description as follows:

PORTNAME


statements: TRLE
dependency: OSA port operating in either ATM native mode or in
QDIO mode.

Specify a link_num value only for an OSA-Express
port that is operating in QDIO mode and customized
for LAN emulation. The link_num value is mutually
exclusive with the PORTNUM operand of the TRLE
definition statement.
port_name

Specifies the Open Systems Adapter (OSA) port name. The name
must be unique in one logical partition and it must be unique
for an OSA port shared by multiple logical partitions. Some
OSA-Express3 features provide support for multiple ports per
network interface card (NIC). The port name assigned to each
port on a specific NIC must also be unique. In general, each
defined port name should be unique within your network. The
maximum length for the port_name value is 8 characters.

For an OSA port customized for HPDT ATM native mode, the
port_name value must match the port name specified when OSA is
customized through OSA/SF. If this name is used by TCP/IP, it
must also be defined as the port name in the TCP/IP profile
DEVICE statement. If this name is used for SNA HPR over native
ATM connections, it must also be defined as the port name in the
PORT statement in a VTAM XCA major node.

For an Open Systems Adapter-Express (OSA-Express) port operating
in QDIO mode, the name specified for the port_name value is
downloaded into the OSA-Express when the first TCP/IP device for
this OSA-Express port is activated. For OSA-Express QDIO
connections, this name must be defined as the device name in the
TCP/IP profile DEVICE statement or as the port name in the
TCP/IP profile INTERFACE statement for any TCP/IP stack that
will use this OSA-Express feature. This name must also be
defined as the port name on a VARY TCPIP,,OSAENTA command or the
port name on an OSAENTA profile statement if a TCP/IP stack will
start an OSA-Express network traffic analyzer trace on this OSA
feature.
====================
Under Operand Descriptions, add the new description for
the PORTNUM operand as follows:

PORTNUM


       
statements: TRLE
dependency: Specify a port_num value only for an OSA-Express3
port operating in QDIO mode. The PORTNUM operand is
mutually exclusive with the link_num value
specified on the TRLE PORTNAME definition
statement.
range : 0-15

Some OSA-Express3 features provide support for multiple ports
per network interface card (NIC). To access these ports, you
must supply a physical port number on the QDIO TRLE definition
to distinguish between the physical ports on an OSA-Express3
NIC.

port_num

Specifies the physical port number of an OSA-Express3 NIC that
is to be associated with this QDIO MPC group. The PORTNAME and
PORTNUM values together uniquely define the OSA-Express3
physical port. The value of the PORTNUM operand is zero-based;
the value port_num 0 represents the first physical port,
port_num 1 represents the second port, up to port_num 15, which
represents the sixteenth physical port. The default is 0.

Rule: Although the PORTNUM operand supports up to the value 15
(that is, 16 physical ports), do not code a value higher than
what each OSA-Express3 NIC supports. If the port_num value is
higher than the physical capabilities of the OSA-Express3 NIC,
failures will occur when QDIO is activated.
====================
In Chapter 2. Major nodes, Adjacent control point major node, Adjacent control point major node operand descriptions, NETID, add the following Tip:

Tip: For ADJCP minor nodes that specify the NETID operand, you can dynamically change the ALIASRCH and RTPONLY operands without stopping and restarting CP-CP sessions to these adjacent CPs. If you do not specify the NETID operand on the ADJCP minor node, then you must stop all of the links (at the same time) to this adjacent node and restart them for the updated definitions to be used.

In Chapter 2. Major nodes, Adjacent control point major node, Adjacent control point major node operand descriptions, ALIASRCH, modify the Tip as follows:

Tip: You can dynamically change the ALIASRCH value for one or more adjacent CP definitions without restarting VTAM. If a definition for the adjacent CP to be changed has already been activated, then you must first inactivate the entire ADJCP major node containing that definition. (Inactivating a predefined ADJCP major node does not cause links or CP-CP sessions to stop. Rather, the adjacent CP definitions for nodes that currently have active connections to this node are moved to the dynamic ADJCP major node, ISTADJCP. During this process, the current ALIASRCH value in effect is preserved.) After you modify or create the necessary ADJCP minor node definitions, and you activate the ADJCP major node, VTAM updates these definitions immediately if the NETID operand is specified on the ADJCP minor node. If you do not specify the NETID operand on the ADJCP minor node, then you must stop (at the same time) all of the links to this adjacent node and restart them for the updated definitions to be used.

In Chapter 2. Major nodes, Adjacent control point major node, Adjacent control point major node operand descriptions, RTPONLY, modify the Tip as follows:

You can dynamically change the RTPONLY value for one or more adjacent CP definitions without restarting VTAM. If a definition for the adjacent CP to be changed has already been activated, then you must first inactivate the entire ADJCP major node containing that definition. (Inactivating a predefined ADJCP major node does not cause links or CP-CP sessions to stop. Rather, the adjacent CP definitions for nodes that currently have active connections to this node are moved to the dynamic ADJCP major node, ISTADJCP. During this process, the current RTPONLY value in effect is preserved.) After you modify or create the necessary ADJCP minor node definitions, and you activate the ADJCP major node, VTAM updates these definitions immediately if the NETID operand is specified on the ADJCP minor node. If you do not specify the NETID operand on the ADJCP minor node, then you must stop all of the links (at the same time) to this adjacent node and restart them for the updated definitions to be used.

====================
In Chapter 4. VTAM start options, Descriptions of start options, Buffer pool start option, Table 64. IBM-supplied VTAM buffer pool values, replace the baseno values in the second column with the following:




====================
In Chapter 4. Start options, Descriptions of start options, IQDCHPID, replace the sentence in the second paragraph that reads "To understand the effects of modifications to IQDCHPID on an active system, refer to the MODIFY command in z/OS Communications Server: SNA Operation." with "For information about the effects of modifications to IQDCHPID on an active system, refer to the IQDCHPID option of the MODIFY VTAMOPTS command in z/OS Communications Server: SNA Operation."

Also, remove the second note in the list that reads "To understand how the MODIFY command affects the current usage of HiperSockets, refer to the MODIFY VTAMOPTS (IQDCHPID) command.
====================
In Chapter 2. Major nodes, Switched major node, Switched major node operand descriptions, IPRESOLV, change

statements: PU

to

statements: PATH