PK33332: PROBLEM AFTER IOCTL WITH SIOCATMARK, WHEN THERE IS OOB DATA TO BE RECEIVED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • The following errors exist in the TCPIP OOB processing logic.
    1) Issuing a recv() with a length that exactly matches the
    number of
    normal data bytes preceding the OOB byte will fail to set the
    tcb_at_mark flag.  The tcb_at_mark flag is used to determine the
    outcome of the ioctl SIOCATMARK.
    2) Issuing a recv() with MSG_OOB when the tcb_at_mark flag
    is set fails to turn the flag off.  Consuming the OOB byte means
    the
    subsequent data byte on the receive queue is normal data.
    Item 1 means that if you always issue the recv() with a length
    of 1
    the tcb_at_mark will never be turned on
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS IP                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SIOCATMARK ioctl may return an      *
    *                      incorrect value. As a result out of     *
    *                      band TCP data may be incorrectly        *
    *                      handled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Two errors exist in the TCP out of band processing:
    
    1. issuing a receive with a length that exactly matches the size
       of data bytes immediately proceeding the out of band data
       fails to set the tcb_at_mark flag.
    
    2. issuing a receive with MSG_OOB when the tcb_at_mark is set
       may fail to turn the flag off.
    +-------------------------------------------------------------+
    + 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 24 months.
    
    This problem will be tracked as Defect D139547 by Communications
    Server for z/OS Development.
    

APAR Information

  • APAR number

    PK33332

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    180

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-10-20

  • Closed date

    2006-11-20

  • Last modified date

    2006-11-20

  • 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

  • R180 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

180

Operating system(s):

z/OS

Reference #:

PK33332

Modified date:

2006-11-20

Translate my page

Machine Translation

Content navigation