IBM Support

PH10272: EVERY SIGNIFICANT OTMA EVENT WOULD HAVE A TRACE BYTE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Every significant OTMA event would have a trace byte in DFSYTIB
    or DFSYQAB blocks, and we will dedicate 32 bytes in each DFSYTIB
    and DFSYQAB to trace last 32 events.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IMS V15 customers using OTMA                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Every significant OTMA event would need a trace byte in the  *
    * related OTMA control block.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • We dedicated the trace bytes in the OTMA control block (DFSYTIB,
    DFSYQAB, and DFSYPIP) to store the last 32 OTMA events. For each
    trace event, an one byte event ID is assigned. The definition of
    each event ID is defined in DFSYTIB, DFSYQAB, and DFSYPIP
    control blocks. Also, the dump formatter was enhanced to display
    each event with module name and event description. This
    enhancement is mainly to help IMS L2 and L3 trace the flow of
    OTMA message processing.
    

Temporary fix

Comments

  • REPINNED RP03/02/20 (ATXT) TO ADD POSTREQ PH22024 INFO.
     **** PE03/02/20 PTF IN ERROR. SEE APAR PH22024 FOR DESCRIPTION
    ×**** PE20/02/12 FIX IN ERROR. SEE APAR PH22024  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PH10272

  • Reported component name

    IMS V15

  • Reported component ID

    5635A0600

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-27

  • Closed date

    2019-11-04

  • Last modified date

    2020-03-18

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

    PH10267

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

    UI66241

Modules/Macros

  • DFSYPSI0 DFS6ECT0 DFSYDSTC DFSYFD00 DFSYTIB  DFSYQAB0 DFSYCLH0
    DFSYPIP  DFSYRR00 DFSYQAB  DFSYCKP0 DFSYSND0 DFSYLUS0 DFSYACK0
    DFSYDST  DFSYSCP0 DFSYFND0 DFSAOSW0 DFSYMEM0 DFSYSLM0 DFSAOAM2
    DFSYTIB0 DFSAOA00 DFSYDAD0 DFSYMOM0
    

Fix information

  • Fixed component name

    IMS V15

  • Fixed component ID

    5635A0600

Applicable component levels

  • R500 PSY UI66241

       UP19/11/05 P F911

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":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 December 2023