IBM Support

PI80970: ISSUES WITH SPECIFICATION OF A LOCAL PORT AT IMS V15

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1.  At IMS V15 use of TCPIP PORTID=LOCAL is no longer supported
    by IMS Connect but specification of a LOCAL port is still
    tolerated. However, specification of a LOCAL port at IMS V15
    will cause IMS Connect Extensions Publisher API initialization
    to enter a CPU-intensive loop and the subsequent IMS Connect
    server shut down will hang. The Publisher API has been modified
    to circumvent this issue.
    2.  Added defensive code to handle unexpected Journal event
    content.
    

Local fix

  • Remove the LOCAL PORTID from their ICON configuration and
    restart ICON.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Connections Extensions V2.4     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Issues with use of a LOCAL port         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. At IMS V15 use of TCPIP PORTID=LOCAL is no longer supported
       by IMS Connect but specification of a LOCAL port is still
       tolerated. However, specification of a LOCAL port at
       IMS V15 will cause IMS Connect Extensions Publisher API
       initialization to enter a CPU-intensive loop and the
       subsequent IMS Connect server shut down will hang.
    
    2. At IMS V14 and earlier, use of TCPIP PORTID=LOCAL can result
       in an abend S0C4 in module CEXCONSS.
    

Problem conclusion

  • 1. The Publisher API has been modified to circumvent the issues
       related to the specification of a LOCAL port at IMS V15
       or above.
    
    2. Corrected logic error in CEXCONSS to prevent the possibility
       of the loop which resulted in an abend S0C4.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI80970

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    240

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-03

  • Closed date

    2017-05-30

  • Last modified date

    2017-07-05

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

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

    UI47649

Modules/Macros

  • CEXCONS  CEXCONSS CEXCRPF  CEXEVT01 CEXEXRTR
    CEXPUBMN CEXSVC01 CEXTECL
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R240 PSY UI47649

       UP17/06/02 P F706

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88S","label":"IMS Connect Extensions"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.4.0"}]

Document Information

Modified date:
22 October 2020