Richard, Jim is correct. SYBMON was going through "refresh" processing ... essentially a cleanup (reaccess of minidisks, etc.). I would think if you can delay for 30 seconds before the next command you'd be OK.
However, Jonathan has a point ... is there a reason you can't just schedule the jobs to run with an event in the scheduler on SYSMON? HiDRO will only run one backup job at a time, so if job 2 (and 3) are submitted prior to job 1 (or 2) finishing, they will wait in the queue ... when one job completes, the next will start. JR (Steven) Imler CA Senior Sustaining Engineer Tel: +1-703-708-3479 steven.im...@ca.com <mailto:steven.im...@ca.com> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, May 04, 2009 07:04 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: OT: Undocumented from Hidro That is what I was guessing; however, confirmation would be nice. I don't want to try varying the length of pause several times, only to find out that the answer lies elsewhere. Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of James Vincent Sent: Monday, May 04, 2009 3:44 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: OT: Undocumented from Hidro Hello! Marci, sending backup requests to SYBMON is correct for "batch runs" of multiple volume backup jobs. Richard, that message is from SYBRQST MODULE, part of the HiDRO code that SYBMON runs. Could it be you need to pause a bit before continuing your next step? I do not do multi-job runs via SYBMON, but I am wondering if it is cleaning up or something after the first job wrapped up. -- Jim Vincent
