Automation Point

Expand all | Collapse all

AP - generic monitoring during IPL start

  • 1.  AP - generic monitoring during IPL start

    Posted 11-03-2014 11:20 AM

    During IPL, before OPS/MVS is initialized…

     

    Does anyone have a method for AP to detect WTORs that are outstanding for X amt of seconds, so that we can ALERT someone?  We don’t always have someone watching a system as it is being IPL’d, and there are rare occasions that WTORs  (that we have not identified with automation) go unanswered, delaying the system startup.

     

    Any ideas for using AP to detect this scenario?

    Maybe a solution is to set at timer once AP sees the first system messages at IPL time and if we don’t get to a certain point (ie, seeing OPS/MVS initialize) in a certain amount of time, notify someone to take a look at the system console.

     

    Anybody doing this type of monitoring?

     

    Thanks

    Sal



  • 2.  Re: AP - generic monitoring during IPL start

    Posted 11-06-2014 11:03 AM

    Anybody able to help out Sal?

    SAL COSTANZO wrote:

     

    During IPL, before OPS/MVS is initialized…

     

    Does anyone have a method for AP to detect WTORs that are outstanding for X amt of seconds, so that we can ALERT someone?  We don’t always have someone watching a system as it is being IPL’d, and there are rare occasions that WTORs  (that we have not identified with automation) go unanswered, delaying the system startup.

     

    Any ideas for using AP to detect this scenario?

    Maybe a solution is to set at timer once AP sees the first system messages at IPL time and if we don’t get to a certain point (ie, seeing OPS/MVS initialize) in a certain amount of time, notify someone to take a look at the system console.

     

    Anybody doing this type of monitoring?

     

    Thanks

    Sal



  • 3.  Re: AP - generic monitoring during IPL start

    Posted 11-07-2014 11:05 AM

    I think that you have already identified the right approach by waiting until a known message indicates that the IPL has completed.

    Some specific steps could be:

    1. When AP rules detect the first IPL message in the session of interest,
      • Set a global variable from the AP rule to indicate that an IPL is in progress
      • Launch a REXX program from the AP rule to loop until the IPL is done
    2. The REXX program should check the global variable within a loop
      • If the global variable indicates that the IPL is done, you exist the REXX program
      • If the global variable indicates that the IP is still in progress, sleep for a minute and loop again
      • After the REXX program has looped for what you feel is an excessive delay,
        • It sends a notification
        • It exits
    3. A second AP rule would detect any message known to occur after the IPL process is complete.
      • Set the global variable to the value that indicates that the IPL is done.