IBM Support

PI64856: POTENTIAL UNPREDICATABLE RESULTS WITH SOCKAPI CTRACE OPTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • .
    When there is an application active on the system that is using
    the EZASMI sockets interface (includes EZASOKET calls, CICS
    Sockets API (not TCPSERVICE listeners), and IMS Socket API), if
    the SYSTCPIP CTRACE option SOCKAPI is enabled the potential
    exists for unrelated key 6 storage areas to be altered.
    Results if this occurs are unpredictable.
    
    
    Other symptoms:
    
    SYSTRACE and SYSOMVS CTRACE will show program interrupts
    occurring during socket processing but no errors reflected back
    to the application (or logged in the SYSTCPIP CTRACE).
    
    Some asynchronous calls do not log call completions in the
    SOCKAPI trace.
    

Local fix

  • .
    Do not enable the SOCKAPI option.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the Communications Server for                   *
    * z/OS Version 2 Releases 2  IP : SOCKAPI                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the CTRACE SOCKAPI trace option is turned on,           *
    * unpredictable results can occur during  application          *
    * processing. Storage areas belonging to KEY 6 are overwritten *
    * causing erroneous outputs.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During read/and write  asynchronous socket calls,  sockapi trace
    entries are cut if the sockapi option is on. To collect
    information for the trace, an IOCTL socket call  is invoked but
    the call is made in 64-bit addressing mode. The IOCTL socket
    call cannot be issued in 64-bit mode  during asynchronous
    processing.
    

Problem conclusion

  • Code has been added to issue the IOCTL socket call in 31-bit
    addressing mode.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI64856

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-27

  • Closed date

    2016-08-15

  • Last modified date

    2016-10-03

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

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

    UI40092

Modules/Macros

  • EZBSOMT1
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R220 PSY UI40092

       UP16/09/17 P F609

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 October 2016