Change the CALL QGPL/QSTRUP to STRSBS controlling-sbs-name

It will accomplish the call to the QSTRUP program, and start the controlling
subsystem, which wouldn't be started in your example.

Also, you need to put some MONMSG after these to monitor for various
conditions like CPF3773

You can put some DLYJOB number-of-seconds to make the job wait between
commands.

I would change the ENDSYS to ENDSBS *ALL Controlled for 60 seconds, and
then put a DLYJOB of 120 afterwards.

You can also do a delay as soon as it starts and wait until 23:00 and then
let this start.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vinay Gavankar
Sent: Tuesday, August 25, 2009 5:11 PM
To: Midrange Systems Technical Discussion
Subject: Saving User and IBM libraries via CL program

I want to write a simple CL program to unable the user to back up all the
User and IBM libraries.

The user will sign on as QSECOFR in QCTL (which is the controlling
subsystem) and call the program interactively and go home.

Will the following work?

PGM
ENDSYS OPTION(*IMMED)
SAVLIB LIB(*NONSYS) DEV(TAP01)
CALL QGPL/QSTRUP
RETURN
ENDPGM

QSTRUP in QGPL is the startup program used after IPL.

The thing I am worried about is SAVLIB will start before ENDSYS completes
and terminate with an error message.

Ofcourse, I am not sure it will all fit on one tape. So, if next morning, it
is stuck asking for a new tape, he will just take C to cancel the SAVLIB
command and then I to continue on to the QSTRUP.

Any suggestions please.
Thanks

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].