Assuming a recent version of the OS, it's (mostly) there.
Then option screen for GO SAVE option 21-Save Entire System includes a
parameter, "Start Time" which allows you to delay the start of the save
upto 24hr. So if your operator goes home at 5pm Friday, the save can start
between 5pm Friday and 5pm Saturday.
The IPL and the DUPTAP are another issue.
For the DUPTAP to accord after restart, you'd have to make chages to your
In order to IPL or to do the DUPTAP after the save, you'd want to use your
own save command. Save menu option 21 calls QMNSRBND. You can easily do a
RTVCLSRC on that and modify it to do whatever you want. I'd recommend
putting together a command front end for it.
I can send you an example you'd like.
On Fri, Aug 22, 2014 at 8:17 AM, Mike Cunningham <mike.cunningham@xxxxxxx>
Does anyone have a script or tool that would do a monthly SAVSYS process
without the need for an operator? End all subsystems to a restricted state,
do the SAVSYS, initiate an IPL to bring the system back up, kick off a
DUPTAP to make a second copy of the SAVSYS tape. I remember there were some
techniques for doing this years ago, like write CL and call that CL from
the operators console before going home on the weekend to do the SAVSYS. CL
waits until Sunday morning at 6:00 am and then starts running. Does a tool
like BRMS or Robot handle this type of process?
VP of Information Technology Services/CIO
Pennsylvania College of Technology
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives