Viewing the Event Replay Log

Use the following procedure to review and select events to test new or changed Rules.

When you select an event to replay, the event is sent back to the Rule Processor where it can be evaluated for any matching Rules. You can view any automation that occurs manually or by using the Automation Log application to ensure that the new Rule (or a revised Rule) performs the automation that you expect.

Related topic

List-of-additional-EZAO-views

Problems can be identified earlier and corrected before they impact the production environment. In addition, because the event does not need to be re-created at the source (CICS, DB2, z/OS, and so on), the testing can be done quickly and easily and can be repeated as many times as necessary by using a single occurrence of the event.

To select an event for replay

Place the cursor on the Event Replay Log menu item and press Enter. The REPLAY view is displayed. 


DDMMMYYYY  13:12:26 -------------------------------- BMC AMI Ops WINDOW INTERFACE (Vv.r.mm)
COMMAND  ===>
CURR WIN ===> 1        ALT WIN ===>
>H1 =REPLAY============JO81=====*========DDMMMYYYY==13:12:22====MVAO=====D==103==========     
-  Event Replay Log                                                    - Hide Fixed Secti
   Related Hyperlinks:            Max Files.. 5          Max Search... 50000
   .Events-Only List              Start Date. CURRENT    Start Time... CURRENT
   .All Events and Actions        End Date...            End Time.....
   .Only Events w/ Actions        Direction.. REV        # of Records. 1000
   .Events without Actions        First Date: 2019/11/01 First Time:.. 13:12:22.226
                                  Last  Date: 2019/11/01 Last  Time:.. 13:11:09.403

C Event    Event      Origin   Event        Evnt Jobname  Partial Message
- Time---- Date------ -------- Msg ID------ Type -------- Text----
  13:11:09 2019/11/01 AAOJO81  AU1033I      MSG  JO81     AU1033I  Automation Log Connect
  13:11:09 2019/11/01 JO81     AU1033I      JRNL JO81     AU1033I  Automation Log Connect
  13:11:09 2019/11/01 AAOJO81  AU1041I      MSG  JO81     AU1041I  Event Replay option ac
  13:11:09 2019/11/01 JO81     AU1041I      JRNL JO81     AU1041I  Event Replay option ac
  13:11:09 2019/11/01 JO81     AU9999I      JRNL JO81     AU9999I  REQ=CALLR STOPIMS   I=
  13:11:13 2019/11/01 MAMHSTM  TX2002W      MSG  JO81     TX2002W Connection to HSAC lost
  13:11:14 2019/11/01 MVSMXH1  -Jobname     MSG  JO81     -Jobname  Stepname Procstep
  13:11:14 2019/11/01 MVSMXH1  -MVSMXH1     MSG  JO81     -MVSMXH1  $BCVM    $BCVM      0
  13:11:14 2019/11/01 MVSMXH1  IEF126I      MSG  JO81     IEF126I MVSMXH1 - LOGGED OFF -
  13:11:14 2019/11/01 MVSMXH1  -MVSMXH1     MSG  JO81     -MVSMXH1  Ended.
  13:11:14 2019/11/01 MVSMXH1  $HASP395     MSG  JO81     $HASP395 MVSMXH1  ENDED - RC=00
  13:11:15 2019/11/01 CNMNETC  IST663I      MSG  JO81     IST663I INIT OTHER REQUEST FAIL
  13:11:17 2019/11/01 DYCQAC21 OSZ0600I     MSG  JO81     OSZ0600I Task initiation TTOKEN
  13:11:18 2019/11/01 MD01CAS  OSZ0600I     MSG  JO81     OSZ0600I Task initiation TTOKEN
  13:11:20 2019/11/01 RQP2CAS  OSZ0600I     MSG  JO81     OSZ0600I Task initiation TTOKEN
  13:11:21 2019/11/01 CONSOLE  PWSACP94     MSG  JO81     PWSACP94 *WARNING* CPU usage is

For more information about any field in this view, place the cursor in the heading and press the Help (F1) key.

To use event replay

  1. Locate an original event by using the REPLAY view. 

    Tip

    You can also use the REPPROF (replay profile) and TIME MPDs to locate an original event.

  2. Use the S line command to select one (or more) events and press Enter to replay the event.
  3. Review the Rule or Rules that were intended to fire during the event replay to verify the expected outcome.
  4. Use the REPLAY view to repeat the event replay as needed.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*