IBM Support

PI24404: OTMA TRACE RECORD X'A6' CAN HAVE BAD LENGTH IF THE EXIT IS USING HWSSMPL0 OUTPUT FORMAT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR addresses the following problems:
    1. The OTMA trace record x'A6' can have bad length if the
    exit is using HWSSMPL0 output format, a message segment has an
    odd length, and the length is within 3 bytes of the maximum
    trace buffer length. The event LL is 1 - 3 bytes longer than the
    actual message data and this can result in an invalid event
    record time.
    2. IMS Connect APAR PI19723 changed the event 16 for dynamic add
    of a datastore to include the XCF Group name. CEX needs to
    support the changes to event 16 for dynamic add of a datastore
    in IMS Connect.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Connect Extensions V2.3         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The OTMA trace record x'A6' can have    *
    *                      bad length if the exit is using         *
    *                      HWSSMPL0 output format                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following problems are being addressed in this APAR:
    1.The OTMA trace record x'A6' can have bad length if the exit
    is using HWSSMPL0 output format, a message segment has an
    odd length, and the length is within 3 bytes of the maximum
    trace buffer length. The event LL is 1 - 3 bytes longer than
    the actual message data and this can result in an invalid
    event record time. The bad time stamp can cause an 0C9 in
    IMSPA if thejournal is used to run reports.
    2.IMS Connect APAR PI19723 changed the event 16 for dynamic
    add of a datastore to include the XCF Group name.
    CEX needs to support the changes to event 16 for dynamic
    add of a datastore in IMS Connect
    

Problem conclusion

  • 1. Module CEXTECL has been changed to correctly calculate the
    length of the x'A6' event when the message is in the
    HWSSMPL0 format
    2. Code has been added to support IMS Connect APAR PI19723
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI24404

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-21

  • Closed date

    2014-08-27

  • Last modified date

    2014-09-03

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

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

    UI20938

Modules/Macros

  • CEXACLR1 CEXACL10 CEXAPMT1 CEXCDSB  CEXCR16
    CEXEVTPR CEXEVTSR CEXEVWTR CEXJRNEX CEXPRED1 CEXPUBMN CEXRCDPR
    CEXRCDUT CEXSALUT CEXTECL
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R230 PSY UI20938

       UP14/08/30 P F408

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

Document Information

Modified date:
22 October 2020