PM91029: DATTRACE PORTNUM PARM DOES NOT WORK FOR REMOTE PORTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • The DATTRACE PORTNUM parm does not capture data when a remote
    port is used as a filter. This occurs for both UDP and TCP
    protocol port. For instance, a portnum filter is used to
    capture DNS traffic data using UDP port number 53 for a remote
    DNS. Another example is an FTP initiated from z/OS using FTP
    TCP port number 21 as the portnum. In both cases no dattrace
    records were collected when issuing a nestat config command.
    
    
    
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s): data trace dattrace
    portnum
    

Local fix

  • use ip keyword instead of portnum to filter on remote ip address
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 11, 12,        *
    *                 and 13 IP: Data trace                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the Vary DATTRACE command,   *
    *                      some trace data is missing.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The destination port number in the SCB was not set in
    session control block before determination was made that
    the TCP session was to be traced.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

Temporary fix

Comments

  • This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 36 months.
    
    This problem will be tracked as Feature F016110
    by Communications Server for z/OS Development.
    

APAR Information

  • APAR number

    PM91029

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1D0

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-13

  • Closed date

    2013-06-28

  • Last modified date

    2013-06-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R1D0 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

1D0

Operating system(s):

z/OS

Reference #:

PM91029

Modified date:

2013-06-28

Translate my page

Machine Translation

Content navigation