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

Rob,

You are rightm of course. An additional bonus for your suggestion is
if you consider the GO SAVE options as a standard. If I say "GO SAVE
Option 21", everybody knows what I'm talking about, opposed as saying
"My CLP, Version 99".

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries

On Thu, Oct 29, 2009 at 12:41 PM, <rob@xxxxxxxxx> wrote:

Luis,

Some offsite services, and IBM itself, gets a little concerned when you
roll your own versus saying you took the option 21. It's that comfort
level that I'm trying to achieve.

That, and it helps to alleviate upgrade concerns.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/29/2009 11:50 AM
Subject: Re: Option 21 Save - QSTRUPPGM
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Rob,

If you think it through, the GO SAVE 21 is not a real CMD, but only a
shortcut for those of us who don't want to roll up our own sequence of
save procedures. In fact, the help for the menu indicates, under the
option 21:

ENDSBS SBS(*ALL) OPTION(*IMMED)
SAVSYS
SAVLIB LIB(*NONSYS) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT)
('/QDLS' *OMIT) UPDHST(*YES)
STRSBS SBSD(Control subsystem)

It is almost as easy as insert all these statements in an user CLP and
call it from the command line, omitting the last line. I think that a
DCR would be unnecessary (although, as I read on this boards, you are
famous for them!! :-) )

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries

On Thu, Oct 29, 2009 at 10:30 AM, <rob@xxxxxxxxx> wrote:

Now why didn't I think of that? Great idea!

Seriously though I think a DCR is in order to have whether or not to run
that at the end of GO SAVE 21.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/29/2009 09:47 AM
Subject: Re: Option 21 Save - QSTRUPPGM
Sent by: midrange-l-bounces@xxxxxxxxxxxx

David,

You could create a data area, write a value indicating if the start up
program must run or not and, inside your startup pgm, read the data
area and act accordingly. It could be something like "read data area",
"if value = 0 goto eoj", etc.

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries

On Thu, Oct 29, 2009 at 8:32 AM, Noah Sandestin <nsandestin@xxxxxxxxx>
wrote:

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

--
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.

--
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.

--
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.

--
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.

--
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.