If you're already doing any sort of automated system monitoring, I'd just include this routine, How depends on what you're using. For Operations Manager, you'd define a scheduled action to execute it; for one of the WAKEUP-based utilities available on the VM download page you'd include it in the WAKEUP TIMES file. Any other similar product, you include a call to it in whatever routine you run at the desired interval.
Note that if you're going to run this iteratively, you'll also want something else periodically to clean up your disk log or it'll grow until it fills your A-disk. Also, before exiting you should do a "WAKEUP (RESET" as part of restoring the environment. -- Mike Harding z/VM System Support [email protected] [email protected] [email protected] (925) 926-3179 (w) (925) 323-2070 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) The IBM z/VM Operating System <[email protected]> wrote on 04/22/2010 12:23:16 PM: > From: Sergio Lima <[email protected]> > To: [email protected] > Date: 04/22/2010 12:35 PM > Subject: Re: Question About Read console output under REXX > Sent by: The IBM z/VM Operating System <[email protected]> > > Hello Mike, > > Of course We are very happy, but only more one thing : > We think run this exec in a Virtual machine running disconnected , > and also START this exec from time to time (5 minutes) for example. > This sample also run ? > My question is where I put the loop of control, and, what is better ? > > 1 - Send a SMSG to this machine STOP the process, or ? (If yes, can > i put WEKUP SMSG also in the exec ?) > 2 - Give a LOGOFF / FORCE in this machine ? > > Sergio >
