IBM Support

PH10267: 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 V14 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
    traced 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.
    
    The following modules and macros are enhanced to support this
    new OTMA internal trace:
    DFSACK00, DFSYCKP0, DFSYFD00, DFSYFND0, DFSYLUS0, DFSYMEM0,
    DFSYPSI0, DFSYQAB0, DFSYSCP0, DFSYSLM0, DFSYSND0, DFSYTIB0,
    DFSYRR00, DFSAOSW0, DFSYMOM0. DFSAOA00
    DFSAOAM2, DFS6ECT0, DFSYCLH0, DFSYPIP, DFSYQAB, DFSYTIB, DFSYDST
    and DFSYDSTC
    

Temporary fix

Comments

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

APAR Information

  • APAR number

    PH10267

  • Reported component name

    IMS V14

  • Reported component ID

    5635A0500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-27

  • Closed date

    2019-07-16

  • Last modified date

    2020-03-25

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

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

    PH10272 UI64252

Modules/Macros

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

Fix information

  • Fixed component name

    IMS V14

  • Fixed component ID

    5635A0500

Applicable component levels

  • R400 PSY UI64252

       UP19/07/24 P F907

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":"14.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
30 November 2023