Re: Save System question

Henrik,

A good idea to reduce exposure to interruption of the job at the system
console.
The downside is it will take a bit longer for your SAVLIB *NONSYS as once
you start your limited batch subsystem the system is no longer in
restricted state, and therefore you lose the benefit of having the system
bypass checking for object locks (as in restricted state there can not be
any, so that is bypassed).

Neil Palmer      DPS Data Processing Services Canada Ltd.
50 Acadia Avenue, Ste.102                   OS/400~~~~~
Markham, Ontario, Canada.   ____________          ___  ~
Phone:(905) 474-4890 x303   |OOOOOOOOOO| ________  o|__||=
Cell.:(416) 565-1682 x303   |__________|_|______|_|______)
Fax:  (905) 474-4898         oo      oo   oo  oo   OOOo=o\
mailto:NeilP@DPSlink.com  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://www.DPSlink.com     IBM iSeries  The Ultimate Business Server







"Henrik Krebs" <hkrebs@hkrebs.dk>
Sent by: midrange-l-admin@midrange.com
2001/09/10 17:19
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Subject:        Re: Save System question


The less lazy approch:

You should do a RTVCLSRC of save menu option 21 (in this case the
interesting objects are QMNSRBND and QMNSAVE), and create an
alternative program. Include all unchanged until after the the online
stuff is completed, then you can start a limited batch-sbs
(limited so that user application update programs will not run), submit
the rest of option 21, submit a full start up of the
system (or pwrdwn restart(*YES) or whatever and finally sign off the
online session while most part of the save runs in normal
batch-mode.

See: Now the time slot in which I can go to your console, do a cancel
request and more bad things without any pwd is minimized.

Yes - the programs behind option 21 are all OPM CLP's with Allow RTVCLSRC
= *YES

Henrik
http://hkrebs.dk


> Date: Mon, 10 Sep 2001 08:27:34 -0400
> From: "Denis Robitaille" <DRobitaille@cascades.com>
> To: <midrange-l@midrange.com>
> Subject: Re: Save System question
> Reply-To: midrange-l@midrange.com
>
> Here is the lazy approch. Make sure that the terminal where option 21 is
taken support type ahead. Then after taking the 21
option an after answering the different screen, just type SIGNOFF <enter>.
>
> Denis Robitaille
> Directeur services techniques
> Cascades Inc
> 819 363 5187
> fax 819 363 5177
>
>
> >>> gcrane@johansonmfg.com 09/08/01 08:47am >>>
>
>
> Is there a way to have the System Console signed off upon completion of
the Save
> System?  The user is logged on to the system console Save Menu and using
option
> 21 save entire system and scheduled for a later time in the middle of
the night.
> Just do not want the terminal signed on when the save finishes.
>
> Also, what authority rights does the operator really need to do a
complete
> System Save - must be able to back up all files/libraries and the IFS
> directories that are secured.