IBM Support

PM98982: IPIC IPV6 ADDRESS IS NOT SENT PROPERLY IN CAPEX FROM CICS-TS TO TXSERIES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There is a problem caused by IPIC Capability Exchange Message
    constructed by CICS Transaction Server. The calculation of the
    length of the LOGNAME subfield does not follow the design of
    IPIC protocol principles.
    When IPv6 is used, TXSeries properly follows IPIC protocol but
    can not parse Capability Exchange Message sent to it by CICS
    Transaction Server. CICS Transaction Server has incorrectly
    formatted this message.
    
    
    Additional Symptom(s) Search Keyword(s): KIXREVWRW
    

Local fix

  • USERMOD available from the Change Team
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS TS failed to acquire IPCONN        *
    *                      to TXseries when IPv6 address is        *
    *                      used in tcpipservice.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In case IPv6 address is used in tcpipservice. When CICS TS
    send request to TXseries to acquire IPCONN, subfields logname
    and IPv6 address are built up in request message. The IPV6
    subfield is not placed immediately after the logname subfield.
    This caused the TXseries side to fail to locate the IPv6
    address.
    

Problem conclusion

  • DFHISCO has been changed to generate the correct IPIC
    capability exchange CAPEX type 1 message.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM98982

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-14

  • Closed date

    2014-01-07

  • Last modified date

    2015-03-05

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

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

    PI04772 UI14309

Modules/Macros

  • DFHCIS4  DFHISCOP DFHISCOT DFHISCO  DFHISCU  DFHISJU  DFHISREU
    DFHISREX
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UI14309

       UP14/01/24 P F401

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":"5.1","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":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 March 2015