PK55184: IMRI TRANSACTION DOES NOT START SOMETIMES

APAR status

• Closed as program error.

Error description

• IMRI transaction can fail to start sometimes.  If this is
  not noticed the flop-flop files can become full and MERVA
  then stops.
  

Local fix

• Ensure the flip-flop is large enough for a day's work, and then
  run the batch insertion program at day's end to ensure all
  events are added to the Reconciliation DB2 tables.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Traffic Reconciliation.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The IMRI transaction is periodically    *
  *                      started by the IMRICON nucleus program, *
  *                      but occasionally this mechanism seems   *
  *                      to fail, so that IMRI is no longer      *
  *                      started.  Consequently the flip-flop    *
  *                      event files can become full and, if     *
  *                      RECON=(YES,STOP) is specified in        *
  *                      DSLPRM, MERVA is terminated.            *
  *                                                              *
  *                      By design IMRICON does not start IMRI   *
  *                      if the previous initiation resulted in  *
  *                      an IMRI failure.  But in this case      *
  *                      there is no indication of a failure so  *
  *                      it is not clear whether IMRI is not     *
  *                      started, fails to finish, or finishes   *
  *                      without reporting an error.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Errors have been found in the use of ENQ/DEQ which could have
  resulted in IMRINSP (transaction IMRI) waiting indefinitely for
  the flip-flop resource.
  
  If there is more than one MERVA in use it is important that each
  MERVA has a unique NAME value in DSLPRM.  The NAME value and the
  IMRPRM RNAME value together form the resource name for the
  Reconciliation flip-flop.  In each MERVA this resource name must
  be different.
  

Problem conclusion

• For the CICS environment the ENQ/DEQ mechanism used to
  coordinate flip-flop access between IMREXTP and IMRINSP has been
  changed to use CICS ENQ and DEQ.  Previously MVS ENQ and DEQ was
  used and this could have resulted in incorrect functioning.
  
  Additionally, at termination of IMREXTP an incorrect resource
  name was de-queued.  Since the correct resource was not
  de-queued IMRINSP could then wait indefinitely to enqueue it.
  
  
  Documentation updates
  ---------------------
  
  MERVA ESA Components Traffic Reconciliation, SH12-6392-04
  
    In Chapter 7, Customizing, IMRPRM Parameters Module, a third
    sub-parameter has been added to the TIV parameter:
  
          TIV=(n,n,QUIET|NOTQUIET)
               5,0,QUIET
               ---------
  
    In section IMRPARM TYPE=CONTROL, add a second paragraph to the
    explanation of the TIV parameter:
  
      For diagnostic purposes a third sub-parameter, NOTQUIET, can
      be specified to make visible the start and end times of
      transaction IMRI.  NOTQUIET causes transaction IMRI to issue
      operator message IMR063 when it starts, and IMR064 when it
      terminates.  Note that if the TIV time interval is short
      this can result large number of operator messages being
      issued.  The default, QUIET, inhibits these messages and
      should normally be chosen.
  
    In Appendix C, add the following messages:
  
      IMR063I Transaction IMRI starting
        Explanation: If TIV=(..,..,NOTQUIET) is specified in
          IMRPRM this message is issued when transaction IMRI
          starts.  It serves simply as a confirmation that IMR has
          started.
        System action: None.
        User response: None.
  
      IMR064I Transaction IMRI terminating 'rc' 'diag'
        Explanation: If TIV=(..,..,NOTQUIET) is specified in
          IMRPRM this message is issued when transaction IMRI
          stops.  'rc' is the 4-digit hexadecimal return-code, and
          will be 0000 if the transaction is terminating normally.
          The message serves simply as a confirmation that IMRI
          has stopped.
  
          If 'rc' is not 0000 another 4-digit hexadecimal value,
          'diag', is displayed as a diagnostic aid for IBM.
        System action: None.
        User response: If 'rc' is not 0000, and you cannot
          determine why transaction IMRI has terminated, contact
          IBM and supply the 'rc' and 'diag' values.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

•    IMRCSD41 IMREXTF  IMRINSF  IMRINSP  IMRMSGTC
  IMRPARM  IMRYCNSP IMRYINSP IMR063I  IMR064I  J0B1410J
  

Fix information

• Fixed component name

  MERVA COMPONENT

• Fixed component ID

  5648B3000

Applicable component levels

• R410 PSY UK30457

     UP07/10/25 P F710