RE: Save-while-active questions / concerns

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

QSYSWRK does not follow the normal rules in that you don't have to start
QCTL or call QSTRUP for it to start, if it is not running it will start
automatically when you start any other subsystem. (As of V5R1 if Start
TCP/IP is *YES in the IPL attributes TCP/IP will start when QSYSWRK starts.)


Restricted state means all subsystems are ended and the only job is the
console job in QCTL.  Message CPF0968 will be issued to the QSYSOPR message
queue and the history log.  You need to run the ENDSBS *ALL manually from
the console to do this.

I do not use the SAVALLACT and SAVCHGACT commands, but it looks like they
need to be issued manually from the console.  They will take the system to a
restricted state then restart the system after the libraries sync.  There is
also a TAATOOL that will allow you to issue these commands with a delay to
run at a later time.  Documentation for TAATOOLs is at:
http://www.taatool.com/toolinfo.htm  It also appears that these commands
only affect your library save, not your SAVDLO or your SAV.  If your system
completely restarts after the libraries sync you may still have issues with
DLO's or IFS objects.

You do not need to have a restricted system to run SWA backups, it only
needs to be idle.  Only user jobs that update files need to be ended.  A
quick check of the joblog will tell you if you missed anything that needs to
be ended.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Tue, 16 Dec 2003 16:26:21 -0500
from: "David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx>
subject: Re: Save-while-active questions / concerns


Al,

Thanks for the info.  One question spawns many more...  We do have TAATOOL.
I took a quick look the SAVALLACT and SAVCHGACT commands.  Normally we do a
SAVLIB *ALLUSR with a list of libraries that don't change and are omitted
from the daily save.  That doesn't appear to be an option with these
commands.

How does QSYSWRK not follow the normal rules?  Also, how do you define
"restricted state"?  Manually doing a ENDSBS *ALL *IMMED was how I
typically got to a restricted state.  The only thing running was the system
console in QCTL.  Do you get to the restricted state by submitting a job to
QCTL that does the ENDSBS *ALL *IMMED?  If so, it sounds kind of scary to
me.  I suppose that the system console would still be active (I hope).  How
does QSYSWRK fit in?

Thanks

Dave

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx
   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.