IBM Support

PH17439: ABENDS0C4 IN MODULE DFSYQAB0 AFTER A RESUME TPIPE WITH NO MESSGES TO SEND. 19/11/21 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND0C4 after a Resume TPIPE is received in OTMA but there are
    no message to send.
    
    In this case there is not a valid message prefix.  But OMTA is
    looking where the prefix should have been if there was one to do
    additional processing (TMAMCPFL).  If that storage is non-zero
    OTMA will call the Setup_Prefix which will result in ABEND0C4
    because there is no message prefix.
    

Local fix

  • There is no local fix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IMS V14 OTMA RESUME TPIPE users with APAR                *
    * PI99729/UI62028 applied.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABENDS0C4 IN MODULE DFSYQAB0 AFTER A RESUME TPIPE WITH       *
    * NOMESSGES TO SEND.                                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    The call to Setup_Prefix should only occur for a good GU call.
    However, a call of Setup_Prefix with a bad prefix pointer was
    made. If a bad prefix point contains values in TMAMCPFL then we
    attempt to process and could 0C4.
    
    It looked like it had residual data, which caused Setup_Prefix
    to calculate the wrong address for OTMA control data
    (Cntrl_Data_Ptr), which resulted in the 0C4.
    
    DFSYQAB0 allocates storage for the message prefix during
    initialization. PI99729/UI62028 removed the code to clear the
    storage after it's allocated to reduce CPU consumption.
    Therefore, the storage had residual data. This should be OK in
    most cases where GU is successful and we copy the prefix from
    the message. However, in this case, GU returned "no more
    messages" so there was no prefix to copy. Setup_Prefix was
    called with residual data in the prefix causing the 0C4.
    
    As previously, Setup_Prefix should only be called for a good GU
    call. That code was in error since V10 but didn't cause a
    problem since Get_Storage used to clear the prefix.
    

Problem conclusion

  • DFSYQAB0 was enhanced to call Setup_Prefix if return code 0 is
    returned from calling Check_Spa.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH17439

  • Reported component name

    IMS V14

  • Reported component ID

    5635A0500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-27

  • Closed date

    2019-11-21

  • Last modified date

    2019-11-30

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

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

    PH17623 UI66570

Modules/Macros

  • DFSYQAB0
    

Fix information

  • Fixed component name

    IMS V14

  • Fixed component ID

    5635A0500

Applicable component levels

  • R400 PSY UI66570

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

Document Information

Modified date:
30 November 2023