Re: Option 21 Save - QSTRUPPGM -- MIDRANGE-L

Just remember that if you create a custom SAV21 alternative that you should
compare you're custom program - both what you're saving and the other steps
involved - with IBM's after every OS upgrade to make sure that you're in
sync with any changes that IBM might make to the process. Changes are rare
so it's not something most would think about and that's all the more reason
to make such a check a documented step in your upgrade process.

On Thu, Oct 29, 2009 at 8:38 AM, Dave Snyder <DSnyder@xxxxxxxx> wrote:

Create your own SAVSYS job to do and not do what you want:

/* End all subsystems immediately */
ENDSBS SBS(*ALL) OPTION(*IMMED)

/* Delay for 2 minutes to allow subsystems to end */
DLYJOB DLY(120)

/* Change message queue delivery to break */
CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK)

/* Initialize tape - can do this here since we use just one tape */
INZTAP DEV(TAP01) NEWVOL(SAVSYS) CHECK(*NO) +
DENSITY(*CTGTYPE)

/* Perform SAVSYS function - save IBM code */
SAVSYS DEV(TAP01) ENDOPT(*LEAVE)

/* Perform SAVLIB function - ignore specific libraries */
SAVLIB LIB(*NONSYS) DEV(TAP01) ENDOPT(*LEAVE) +
ACCPTH(*YES)

/* Save document and folders and distribution objects */
SAVDLO DLO(*ALL) FLR(*ANY) DEV(TAP01) ENDOPT(*LEAVE)

/* Save user objects in directories */
SAV DEV('QSYS.LIB/TAP01.DEVD') OBJ(('/*') +
('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) +
ENDOPT(*REWIND) UPDHST(*YES)

/* unload tape // pwrdwnsys automatically // repeat any steps desired */

All this can be placed in a CL to be called by the operator.

Dave

From:
Noah Sandestin <nsandestin@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
10/29/2009 09:11 AM
Subject:
Option 21 Save - QSTRUPPGM
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

HI All,

On a monthly basis we run a full system (option 21) save and IPL our
system. To do this, we have an operator who manually brings the system
into a restricted state, goes to the save menu and executes option 21. As
part of the option 21, when the save completes, it starts the controlling
subsystem which then executes the qstruppgm. As I mentioned earlier, we
IPL the system after the save finishes but our operator is having to wait
for the system to start, then end back to a restricted state before he can
IPL the system. It's been awhile since I have been through the option 21
save options, and I've done some reading online, but there doesn't appear
to be an option to bypass the startup. Can anyone suggest a way around
this?

Also, we are preparing for our DR test this December and want to execute 3
consecutive option 21 saves (2 to send to out DR partner, 1 to keep). As
you can image, if the system starts after each one it would add a lot of
time to this procedure. Any suggestions would be appreciated!

Thanks,

David Charmatz

NOTICE - This e-mail message is intended only for use by the addressee(s)
named herein and may contain legally privileged and/or confidential
information. If you are not the intended recipient of this message, you are
hereby notified that any dissemination, distribution or copying of this
message is strictly prohibited. If you have received this message in error,
please notify the sender by e-mail or telephone and delete the original and
all copies of this message immediately.

www.ephratanationalbank.com
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.