PI56084: OTMA RETURNS MSGDFS2533 WITH AN INCORRECT SETTING FOR FLAG TMAMCPFG. THIS CAUSES STORAGE PROBLEMS FOR OTMA CLIENTS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a Fast Path message is entered and there is no IFP to
  process it the message is rejected.  Message DFS2533 is
  returned.  If this is an OTMA input message the DFS2533 message
  is returned with an incorrect setting in OTMA header field
  TMAMCPFG.  If the input messages were from MQ this causes IME
  control blocks to be orphaned which can fill storage.
  

Local fix

• There is no local fix.  The customer should ensure that IFP
  regions are available to process the Fast Path messages.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS 13 OTMA users using Fast Path        *
  *                 transactions.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DFS2533 message returned to the     *
  *                      OTMA client contains an incorrect       *
  *                      setting in the OTMA header field        *
  *                      TMAMCPFG with TMAMCASY flag bit off.    *
  *                                                              *
  *                      Forward-fit of PI49383.                 *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  When a Fast Path transaction is sent to OTMA and there is no
  IFP region to process it, the transaction is rejected and OTMA
  returns DFS2533 message to the client.  However, the DFS2533
  message is returned with an incorrect setting in the OTMA
  header field TMAMCPFG with TMAMCASY flag bit off.
  The TMAMCASY flag bit should have been turned on to indicate
  asynchronous output.
  
  If the input messages were from MQ, the incorrect bit setting
  causes IME control blocks to be orphaned which can fill storage.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  In part DFSYSLM0, when it checks for DFS message for a
  Fast Path transaction that have not responded to the IOPCB,
  it only checks the Fast Path bit YTIB_MSG_EMH.  If that
  Fast Path bit is on, then it turns off async output bit
  TMAMCASY.
  However, for a Fast Path transaction that fails during input
  processing before the transaction runs, such as the scenario
  of when there is no IFP region to process the transaction,
  the async output bit TMAMCASY should be on but the previously
  mentioned Fast Path checking results in turning the async
  output bit off.
  
  The logic is corrected to the following:
  Turn off async output bit TMAMCASY if
   - transaction is Fast Path (YTIB_MSG_EMH bit on)
   - AND the output DFS message is NOT for an input processing
     error (TMAMCER2 bit off).
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

  PI49383

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

  012AC3Ÿ UI35619

Modules/Macros

•    DFSYSLM0
  

Fix information

• Fixed component name

  IMS V13

• Fixed component ID

  5635A0400

Applicable component levels

• R300 PSY UI35619

     UP16/02/27 P F602 Ž

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.