IBM Support

PK55495: INCORRECT RECORDING OF PARTNER IN SAME SYSPLEX

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a CICS system receives a request to establish communication
    using TCP/IP it can fail to correctly detect whether or not the
    partner system is within the same sysplex.  The CICS system can
    incorrectly record that partner system is in the same sysplex
    when it is not, or it can incorrectly record that it is not in
    the same sysplex when it is. When TCP/IP communication is in use
    for IPIC connectivity, during the process to acquire an IPCONN a
    CICS system can incorrectly record whether or not the partner is
    in the same sysplex so that there is a failure to correctly
    correlate CICS tasks for the purposes of z/OS Workload Manager.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect recording of CICS information *
    *                      in WLM when using an IPIC connection to *
    *                      a partner in the same sysplex.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The CICS SO domain incorrectly interprets the result of a z/OS
    communications server GETSOCKOPT request for SO_CLUSTERCONNTYPE
    which reports whether a partner system is in the same sysplex.
    The incorrect interpretation means the actual result of this
    request produces unpredictable results so that a CICS system can
    wrongly decide the partner system is in the same sysplex or not.
    This in turn results in incorrect correlation of CICS tasks
    for the z/OS Workload Manager when using an IPIC connection.
    
    Additional Keywords: IPCONN IPIC WLM SECURITY iwmmswch
    

Problem conclusion

  • Logic in CICS SO domain that interprets the result of this
    request to z/OS communications server has been corrected.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK55495

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-10-29

  • Closed date

    2008-01-16

  • Last modified date

    2008-02-02

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

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

    UK32949

Modules/Macros

  •    DESSOUS  DFHSOCK  DFHSOUSC
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK32949

       UP08/01/19 P F801

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 February 2008