Scott, We don't use VMUTIL (or the WAKEUP command and parms) to run long running execs. We do have separate userids that are autologged on by VMUTIL and they run long execs, but they log off at the end, and we just let VMUTIL control when they start again, with another autolog.
If you are in a wakeup loop, running a long exec, you should not have to do anything different from any other exec, I would think, just end the long running exec. There is, or at least was, a long-standing issue with wakeup - it has a problem with running through midnight, or at least it used to (my VMUTIL parms go back to 1985 and the comment I put there says "don't be in wakeup through midnight". So we wakeup, do a CP SLEEP until midnight is passed, then start the wakeup loop again. So if your long-running exec is leaving your service machine in wakeup through midnight, maybe that is the problem? Ron On Sat, Feb 27, 2010 at 11:37 AM, Wandschneider, Scott <scott.wandschnei...@infocrossing.com> wrote: > I have a follow up question: > > I created a VMUTIL like CMS UserID to run the long-running backup execs. > My question is, do I need to do anything special at the end of the EXEC? > It seems to run just fine but the WAKEUP logic does not seem to continue > as I would expect. > > Thank you, > > Scott > > -----Original Message----- > From: Wandschneider, Scott > Sent: Wednesday, February 24, 2010 2:42 PM > To: 'The IBM z/VM Operating System' > Subject: VMUTIL Executing a long running EXEC > > > I have a REXX EXEC that is triggered by VMUTIL and it runs 90 minutes. > While this EXEC is running VMUTIL is not acting on any other items in > the WAKEUP file. Which makes sense. My question is how can I have > VMUTIL trigger a long running EXEC? > > Thank you, > Scott R Wandschneider > Senior Systems Programmer > > Confidentiality Note: This e-mail, including any attachment to it, may > contain material that is confidential, proprietary, privileged and/or > "Protected Health Information," within the meaning of the regulations under > the Health Insurance Portability & Accountability Act as amended. If it is > not clear that you are the intended recipient, you are hereby notified that > you have received this transmittal in error, and any review, dissemination, > distribution or copying of this e-mail, including any attachment to it, is > strictly prohibited. If you have received this e-mail in error, please > immediately return it to the sender and delete it from your system. Thank you. >
