7 Replies Latest reply: May 4, 2012 3:05 AM by Justin Dettmann RSS

Mainframe time 7 hours behind in BEM

Justin Dettmann

Hi,

 

We have a situation where the mainframe runs on a different timezone setting. This is due to some batch jobs that need certain times to complete and cant change at this stage.

The problem with this is that the events coming from the mainframe are 7 hours behind.

Is it possible to set something im BEM to adjust these time to the correct time when a event arrives?

 

Thanks

Justin

  • 1. Mainframe time 7 hours behind in BEM
    Cesar Salazar

    Events are propagated from the mainframe to a cell via IIDK. There are rules in mv_rules.mrl that execute when events are first OPEN.

    maybe a refine rule like this could do the desired correction:

    refine mv_change_time :

          MV_ALERT ($ALERT)

          when $ALERT.status == OPEN

          {

                    $ALERT.date_reception=$ALERT.date_reception + (7*3600);

          }

    END

     

    the following slots could also be modified as needed:

    mc_incident_time

    mc_arrival_time

    mc_local_reception_time

    mc_date_modification

     

    regards

    Cesar

  • 2. Mainframe time 7 hours behind in BEM
    Justin Dettmann

    Hi Cesar,

     

    I tried your first option with date_reception, but get the following error when compiling:

     

    BMC-IMC120090E: Error in file mv_rules.mrl, line 52 column 12

    BMC-IMC120102E: Slot date_reception is read-only

    BMC-IMC120017E: Number of error(s): 1

    BMC-IMC120015E: Total number of error(s): 1

    BMC-IMC120012F: Compilation failed

     

    Regards

    Justin

  • 3. Re: Mainframe time 7 hours behind in BEM
    Jonathan Coop

    I think the time received, is the time at the cell when the event

    arives, so it shouldn't need altering, I'd suggest generating an

    event, and checking exectly which slots need to be altered.

     

     

     

     

    Jon.

  • 4. Re: Mainframe time 7 hours behind in BEM
    Cesar Salazar

    Justin,

     

    Please try with mc_incident_time. This the slot I had used before for a similar purpose.

     

    refine mv_change_time :

          MV_ALERT ($ALERT)

          when $ALERT.status == OPEN

          {

                    $ALERT.mc_incident_time=$ALERT.mc_incident_time + (7*3600);

          }

    END

  • 5. Mainframe time 7 hours behind in BEM
    Justin Dettmann

    Hi Cesar,

     

    I compiled using mc_incident_time and that compiled successfully. Just waiting for the next mainframe event to see if it worked

     

    Justin

  • 6. Mainframe time 7 hours behind in BEM
    Cesar Salazar

    Hi Justin,

     

    I'm afraid that you will probably not find a satisfactory solution.

     

    I assume that you are using BIIZ (BMC Integration for z/OS) with MV AutoOperator.

    BIIZ implement a gateway to connect with a cell, based on IIDK (Impact Integration Developer Kit).

    So, unlike other integrations, the event is not MSENDed to the cell in which case date_reception would have taken the value from mc_arrival_time or mc_incident_time at the time the event arrives, as pointed out by Jon.

     

    BIIZ propagates events to the target cell, in the same way that events are propagated from cell to cell. The target cell "sees" BIIZ as another cell by means of the gateway implemented using IIDK. You can verify this in the following way: select any event from mainframe, go to the event details and clic the internals tab.

    There you can see the following fields:

    ID=BBO_ALRT_BNZA_4C184AE6

    Internal ID=15105561

    Collectors=[1.1, 2.2.1.1.1, 6.1.1, 12.2, 13.1.1.1.1.4]

    Propagations=[bn00:16686833]

    History=[BNZA:0]

     

    History shows de cell from where the event was propagated. In this case BNZA is the cell name assigned to BIIZ, usually the SSID of the BBISS started task:

    -------------------------------------------------------------------------------------------------------------------------

    BROWSE    PBMC.MV2250.IIM.DIR                        Line 00000000 Col 001 080

     

     

      cell BNZA     mc 10.1.0.2:1828

      cell BN04     mc 10.7.16.38:1832

    -------------------------------------------------------------------------------------------------------------------------

     

    Propagations shows de cells to which the event has been propagated, in this case BN00 is my presentation cell

     

    So, the event is created by BIIZ and the slots values are assigned by BIIZ, and then the event is propagated to the target cell. If date_reception is read only then you will not have the chance to modify it via a rule.

     

    Also, because events are propagated I am not sure if they pass through refine rules. In mv_rules.mrl they use new or execute rules for MV_ALERTS events.

     

    Regards

    Cesar

  • 7. Mainframe time 7 hours behind in BEM
    Justin Dettmann

    Thanks Cesar,

     

    I will scratch around and see what else to try

     

    Regards

    Justin