IBM Support

z/OS V1R13 Communications Server: IP System Administrator's Commands

Troubleshooting


Problem

Publication updates for the z/OS V1R13 Communications Server: IP System Administrator's Commands

Resolving The Problem


In Chapter 1, "Operator commands and system administration", under "VARY TCPIP command", under "VARY command: TCP/IP address space", under "VARY TCPIP,,OBEYFILE", the command format is changed to the following syntax:



===============================================================
In Chapter 1. "Operator commands and system administration", under "TSO commands", under "MODIFY command: Communications Server SMTP application (CSSMTP)", under "Example 5", in the value description of the STATE parameter, add the WAITS value and description:

STATE
This parameter can have one of the following values:

      WAITS
The task is waiting because virtual storage is constrained.

Under "Example 5", under the "TASK" parameter, under "state", add the "WAITS" value and description

TASK
The TASK parameter has the following fields:
state
Possible values are:
WAITS
The task is waiting because virtual storage is constrained.                                                          ===============================================================
In Chapter 1. "Operator commands and system administration", under "TSO commands", under "MAKESITE command", under "Examples", the following updates are made:

Original:
    The following example shows the output when the MAKESITE command is run as a batch job. When the MAKESITE command is run as a TSO command, the report format is the same except that the message numbers are not displayed.


Revised:
    The following example shows the output when the MAKESITE command is run as a batch job. When the MAKESITE command is run as a TSO command, the report format is the same except that the message numbers are not displayed.

    Tip: Messages with numbers that end with an "E" (for errors) or a "W" (for warning) are issued when an error occurs. Messages with numbers that end with an "I" are informational messages and do not represent a problem. Some of the messages in the following example reflect internal processing statistics.

===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "The Netstat command filter", under the description of the "IPAddr/-I' parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or
source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or
source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, in the "Guidelines" list, remove the last bullet as follows:
  • No wildcards are allowed

Under the same topic, after the "Guidelines" section, add a list of "Restrictions" as follows:

Restrictions:
  • No wildcards are allowed.
  • For a UDP endpoint socket, the filter value applies only to the local or

  • source IP address.
=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat ALL/-A report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat ALL/-A report", under "Report field descriptions", under "TcpPrf", the description of the "40 .1.. ...." is changed to the following wording:

40 .1.. ....
Indicates that Dynamic Right Sizing (DRS) is active for this connection so the stack is automatically tuning the advertised receive window. For more information about DRS, see TCP receive window in z/OS Communications Server: IP Configuration Guide. The RcvWnd field shows the current size of the receive window for this connection.

===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat ALL/-A report", under "Report field descriptions", under "TcpPrf", add the description of "02 .... ..1."after "40 .1.. ....":

40 .1.. ....
Indicates that Dynamic Right Sizing (DRS) is active for this connection so the stack is automatically tuning the advertised receive window. For more information about DRS, see TCP receive window in z/OS Communications Server: IP Configuration Guide. The RcvWnd field shows the current size of the receive window for this connection.
02 .... ..1.
Indicates that DRS was active for this connection, but has been disabled. This is caused by the associated application not reading the data as fast as the data arrives.

=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat ALLConn/-a report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat BYTEinfo/-b report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat COnn/-c report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat PORTList/-o report", under the description of the "POrt/-P portnum" parameter, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.



=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat SOCKets/-s report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat VCRT/-V report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat VDPT/-O report", under the description of the "IPAddr/-I" parameter, add the following information after the second bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address.

Under the same topic, under the description of the "IPPort/-B" parameter, add the following information after the third bullet of the "Restrictions" list:
  • For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

Under the same topic, under the description of the "POrt/-P portnum" parameter, after the "Guidelines" section, add a restriction as follows:

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "The TSO PING command: Send an echo request", under the description of the Intf interface parameter, add a bullet to the "Restriction" list as follows:
  • To specify an OSM interface for the parameter, the user ID must have RACF

  • authority to use the interface. For more information about OSM interface
    authorization, see OSM Access Control in z/OS Communications Server: IP
    Configuration Guide.
=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "The z/OS UNIX ping command: Send an echo request", under the description of the -i interface parameter, add a bullet to the "Restriction" list as follows:
  • To specify an OSM interface for the parameter, the user ID must have RACF

  • authority to use the interface. For more information about OSM interface
    authorization, see OSM Access Control in z/OS Communications Server: IP
    Configuration Guide.
===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "The TSO TRACERTE command: Debug network problems", under the description of the Intf interface parameter, add a bullet to the "Restriction" list as follows:
  • To specify an OSM interface for the parameter, the user ID must have RACF

  • authority to use the interface. For more information about OSM interface
    authorization, see OSM Access Control in z/OS Communications Server: IP
    Configuration Guide.
=======================================================================
In Chapter 3, "Monitoring the TCP/IP network", under "The z/OS UNIX traceroute command: Debug network problems", under the description of the -i interface parameter, add a bullet to the "Restriction" list as follows:
  • To specify an OSM interface for the parameter, the user ID must have RACF

  • authority to use the interface. For more information about OSM interface
    authorization, see OSM Access Control in z/OS Communications Server: IP
    Configuration Guide.
===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat report details and examples", under "Netstat VIPADyn/-v report", under "Report field descriptions", under "Dynamic VIPA", the description of the "Moving" status is changed to the following wording:

Moving
    The DVIPA was active on this stack and has been moved to another stack. The DVIPA will remain in the Moving status until no established connections exist. Connections on this stack for this DVIPA that were established before the move are still serviced. If new connections on this stack use the DVIPA, the new connections will also be serviced.
===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Rpcinfo", under "The TSO RPCINFO command: Display server information", under "Examples", the example is replaced by the following example:

    READY
   rpcinfo -p mvsx

    program        vers proto   port    
     100000           2   udp    111    
     100000           2   tcp    111    
     150001           1   udp   1030    
     150001           2   udp   1030    
     100003           2   tcp   2049    
     100003           2   udp   2049    
     100003           3   tcp   2049    
     100003           3   udp   2049    
     100003           4   tcp   2049    
     100059           2   udp   1029    
     100059           2   tcp   1033    
     100044           1   udp   1028    
     100044           1   tcp   1032    
     100005           1   udp   1027    
     100005           1   tcp   1031    
     100005           3   tcp   1031    
     100005           3   udp   1027  


===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat", under "Netstat report and examples", under "Netstat CACHinfo/-C report", under "Report field descriptions", the RequestsProcessed entry is changed to the following wording:
    RequestsProcessed
    The number of requests that were at least partially processed by the Cache Accelerator. This counter can be incremented multiple times for a single connection.

    Tip: It is possible for a single connection to be processed by the Cache Accelerator for some cache objects and then deferred to the application for additional processing. If this occurs, the connection is included in both the RequestsProcessed and RequestsDeferred counts.


===============================================================
In Chapter 3, "Monitoring the TCP/IP network", under "Netstat", under "Netstat report and examples", under "Netstat DEvlinks/-d report", the following changes are made:

In the "Report examples" section,
  • For the example about "IntfName: EZAIQXC9", change "IntfType: IPAQIQX" to "IntfType: IPAQIQDX".
  • For the example about "IntfName: EZ6IQXC9":
    • Change "IntfType: IPAQIQX6" to "IntfType: IPAQIQDX6".
    • Change "Multicast Capability: Yes" to "Multicast Capability: ND only".

In the "Report field descriptions section", the Multicast Capability entry is changed to the following wording:

    Multicast Capability
    Indicates whether the link or interface is multicast capable.
    • For point-to-point interfaces, the value of this field is always Yes.
    • For LCS and MPCIPA links and IPAQENET, IPAQENET6, and IPAQIDIO6 interfaces, the multicast capability is known only after the link or interface is active. If the link or interface is not active, the multicast capability value is Unknown.
    • For IPAQIQDX6 interfaces, the value of this field is always ND only, the interface is multicast capable but multicast processing is only used for neighbor discovery.

    If the link or interface is multicast capable then the following additional fields are displayed for each multicast group for which the link or interface is receiving data. There is no limit to the number of multicast groups for which a link or interface can receive data. For IPAQIQDX6 interfaces, the multicast groups only indicate neighbor discovery processing.

[{"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"All","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.13","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
15 June 2018

UID

swg21514876