IBM Support

PM27983: ALLOW TRANSACTION EXPIRATION TO BE TURNED OFF BY TRANSACTION CODE IF THE REMOTE CLIENT HAS SET TE IN IRM HEADER.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • -  The CEX GUI does not provide a confirmation pop-up before
    making a change to a message exit such as disabling the message
    exit.
    -  MSGCEX5050I should be issued to the Joblog and Console for
    message exit processing so that automated operations tools can
    detect the message being disabled and perform alert
    notifications.
    -  MSGCEX5063I is incorrect in the status of the Transaction
    Time-out and is missing the status of Cancel Client ID status
    -  An ABEND0C1 can occur in module CEXTECL1 after a CLOSEHWS
    FORCE command is issued
    -  New feature to allow Transaction Expiration to be turned off
    by transaction code if the remote client has indicated that
    Transaction Expiration is to be set in the IRM header.
    -  For a transaction definition, at runtime and during a
    transaction REFRESH command, Transaction Expiration and Client
    ID Cancellation settings are set to "inactive" if Activate
    Transaction Routing is active and Override Application options
    is not active.
    -  The IVP program sends IRM_F4 as x'00' when it should be a
    blank. This prevents HWSSMPL0/1 from setting transaction
    expiration if requested in IRM_F1.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Connect Extentions V2.2         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The CEX GUI does not provide a          *
    *                      confirmation pop-up before making a     *
    *                      change to a message exit such as        *
    *                      disabling the message exit.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR is addressing the following issues:
    1.The CEX GUI does not provide a confirmation pop-up before
    making a change to a message exit such as disabling
    the message exit.
    2.Message CEX5050I should be issued to the Joblog and
    Console for message exit processing so that automated
    operations tools can detect the message being disabled
    and perform alert notifications.
    3.Message CEX5063I is incorrect in the status of the
    Transaction Time-out and is missing the status of Cancel
    Client ID status.
    4.An 0C1 can occur in module CEXTECL1 after a CLOSEHWS
    FORCE command is issued.
    5.New feature to allow Transaction Expiration to be turned
    off by transaction code if the remote client has
    indicated that Transaction Expiration is to be set in
    the IRM header.
    6.For a transaction definition, at runtime and during a
    transaction REFRESH command, Transaction Expiration
    and Client ID Cancellation settings are set to "inactive"
    if Activate Transaction Routing is active and Override
    Application options is not active.
    7.The IVP program sends IRM_F4 as x'00' when it should
    be a blank. This prevents HWSSMPL0/1 from setting
    transaction expiration if requested in IRM_F1.
    

Problem conclusion

Temporary fix

Comments

  • The following changes have been made in this APAR:
    1.The CEX GUI has been changed to require user confirmation
    before issuing message exit command that result in changes
    to the status of the message exits.
    2.Message CEX5050I for exit maintenance actions is not issued
    on the Joblog and Console for use by automated operations.
    3.Corrected message CEX5063I to reflect the proper status of
    the transaction definition.
    4.It is possible for an event to be posted for a port task
    that is in the process of being terminated. If this
    happens, CEXTECL1 may attempt to use a service that has
    been disconnected from the port task during termination.
    A check is made to determine if the port task has been
    disconnected from the service to prevent an 0C1 abend
    trying to call the disconnected service.
    5.Changes made to not incorrectly set Transaction Expiration
    and Client ID Cancellation options.
    6.Changed the IVP program to correctly set IRM_F4 to a blank
    when necessary.
    

APAR Information

  • APAR number

    PM27983

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    220

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2010-12-01

  • Closed date

    2011-01-07

  • Last modified date

    2011-02-02

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

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

    UK63757

Modules/Macros

  •    CEX#TXCC CEX#TXTE CEX#TXTT CEXACL10 CEXBDDSG
    CEXBDSI1 CEXBDSO0 CEXCONS  CEXDFDRV CEXEXRTR CEXGUIW  CEXMAIN
    CEXMSGCM CEXMSGL  CEXMSGT  CEXREAD  CEXTECL1 CEXTRDEP
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R220 PSY UK63757

       UP11/01/12 P F101

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.2.0"}]

Document Information

Modified date:
14 December 2020