PI83453: TRANSACTION EXPIRATION FOR OTMA MESSAGES NEEDS AN OPTION TO DISCARD INPUT MESSAGE WITHOUT ABENDING MESSAGE REGION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer needs ability to discard expired OTMA source messages
  without abending the message region which GU's the message.
  Currently, a U0243 will be issued if the retrieved message
  is expired. Cycling a message region via an abend is an
  expensive process even if TODUMP=NO is defaulted to in DFSYDTxx
  descriptor for source OTMA member. The program controller TCB
  collapses and has to be reattached, preload list re-parsded,
  and language environment(s) rebuilt. This is probably far more
  expensive than allowing the application to process an expired
  message. For customer who want to use transaction expiration
  as a resilency function to quickly clear queued messages after
  a period of system degradation, abending the message region
  once per expired message is not useful.
  ( Note that for non-OTMA messages, there is no U0243 unless
  requested, and the message is simply discarded  - this APAR
  will implement similar function for OTMA source messages ).
  ABENDU0243
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IMS V15 QPP OTMA customers using transaction                 *
  * expiration or MAXTP functions                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IMS did not process I/O PCB output                           *
  * for non-expired OTMA transactions                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  When there are a mix of expired and non-expired OTMA
  transactions waiting to be processed, IMS processed
  the expired transaction and incorrectly set the
  TPCBSTAT field to X'AX' which prevented the subsequent
  non-expired OTMA transaction from sending I/O PCB
  output.
  

Problem conclusion

• DFSDLA30 was enhanced to turn on PSTTXPRD bit for OTMA expired
  transaction to avoid TPCBSTAT from getting an incorrect
  setting.
  
  In addition, TODUMP=(U243) is supported for OTMA client
  descriptor so that an OTMA customer can request a pseudo
  ABENDU0243 without a symptom dump.
  
  DFSYIDC0, DFSYTIB0, DFSYMOM0, DFSYLUS0, DFSAOA00, DFSAOAM1,
  DFSAOAM2, DFSYPRE, DFSYMTE, DFSYDES, and DFSTSCD were
  enhanced to support the TODUMP=(U243) option.
  
  RETAIN searchable keyword: ABENDU0243 ABENDU243
  
  Doc Changes are:
  
  ============================================================
  IMS System Definition
  ============================================================
  DFSYDTx
  OTMA client descriptor syntax and parameters
  
  Rewrite the definition of TODUMP= parameter as follows:
  
  TODUMP= specifies whether (YES), (NO), or (U243) the pseudo
  ABENDU0243 is needed at application GU time for an expired
  OTMA transaction or for a transaction reaching the OTMA
  MAXTP condition.
  
  If YES is specified, a pseudo ABENDU0243 with
  DFS554A and symptom dump will be generated for each
  expired OTMA transaction or for a transaction reaching
  the MAXTP condition at the GU time. Choosing this option
  could potentially flood the console and would take additional
  CPU cycles if there are lots of affected transactions.
  
  If U243 is specified, a pseudo ABENDU0243 without
  DFS554A and symptom dump will be used for each
  affected transaction at the GU time. Since each pseudo
  ABENDU0243 comes with the IMS TYPE X'56' log record, it
  could help customers to identify the affected transactions.
  
  If NO is specified, IMS will simply discard
  the affected transaction without the ABENDU0243 to save CPU
  cycles. This parameter is optional and defaults to
  TODUMP=NO. Since there is no pseudo ABENDU0243 for each
  affected transaction at GU time, no additional IMS type
  X'56' log records will be cut. However, IMS will prepare
  a type X'67D0' diagnostic information log record for
  each affected transaction at GU time.
  
  For IMS shared queues customers, if TODUMP= is specified,
  it needs to be set in the OTMA client descriptor in the
  front-end IMS.
  
  If the DFSOTMA is specified in the OTMA client descriptor,
  the DFSOTMA TODUMP value is used by OTMA clients that
  do not specify TODUMP themselves.
  
  ============================================================
  IMS Messages and Codes : IMS Abend Codes
  ============================================================
  0243
  
  add the following to the Explanation section
  
  IMS detects an OTMA input transaction reaching the MAXTP
  condition at the application GU time and decides to take
  a pseudo ABENDU0243 to cancel the input transaction. This
  action is based on the TODUMP=YES or TODUMP=U243 setting
  in the OTMA client descriptor.
  

Temporary fix

Comments

APAR Information

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

  PI63173

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

  UI48974

Modules/Macros

• DFSYIDC0 DFSTSCD  DFSYMTE  DFSYMOM0 DFSAOA00 DFSYPRE  DFSYTIB0
  DFSYDES  DFSAOAM1 DFSAOAM2 DFSDLA30 DFSYLUS0
  

Fix information

• Fixed component name

  IMS V15

• Fixed component ID

  5635A0600

Applicable component levels

• R500 PSY UI48974

     UP17/07/28 P F707

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.