RE: backups on AS/400; part2

[Jim Damato <jdamato@xxxxxxxxxxxxxxxxx>]

As I said, I thought the batch subsystem would be a problem, so I'd have to
bring up just enough of the system to allow batch jobs to run by modifying
the startup script.  I'm digging through our startup CL to see if there are
show-stoppers, but I haven't found any yet.

Our SAVSYS portion of the SAVE option 21 is fairly quick compared to the
SAVLIB *NONSYS.  That portion of the backup could run attended with the
console logged on.  SAVSYS could be performed interactively before the batch
job is submitted for the rest of the saves.  The CL could be called to
switch the startup mode, start QCTL to start the batch subsystem, perform
the SAVSYS, submit the batch job for the rest of the saves, and sign off.

-Jim

James Damato 
Manager - Technical Administration 
Dollar General Corporation 
<mailto:jdamato@dollargeneral.com> 

-----Original Message-----
From: Neil Palmer
To: MIDRANGE-L@midrange.com
Sent: 5/28/01 5:12 PM
Subject: Re: backups on AS/400; part2

Not the only problem.  When you start any subsystem you are no longer in
a 
restricted state, so you're caught there too.
(Starting any subsystem will also start subsystem QSYSWRK).

...Neil





"Eric Graeb" <egraeb@home.com>
Sent by: owner-midrange-l@midrange.com
2001/05/28 19:11
Please respond to MIDRANGE-L

 
        To:     <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        Re: backups on AS/400; part2


The only problem with this is the SAVSYS command must be run from an
interactive job.

Eric Graeb
System Operations

----- Original Message -----
From: "Jim Damato" <jdamato@dollargeneral.com>
To: <MIDRANGE-L@midrange.com>
Sent: Monday, May 28, 2001 1:19 PM
Subject: RE: backups on AS/400; part2


>
> I'm treading on thin ice here since I've always worked in shops with
> 24x7 operations...
>
> The last time I retrieved the source for the GO SAVE option 21 it
> consisted of:
>
> SAVSYS
> SAVLIB *NONSYS
> SAVDLO
> SAV
>
> Couldn't you create a batch subsystem "SPARKy" with it's own jobd,
jobq,
> etc. and create a backup script to be run from the console?  You'd
bring
> the system to it's restricted state then bring up only subsystem
SPARKY
> and submit a CL to SPARKY's queue that would run the equivalent of the
> save option 21.  The last steps in the CL would be to bring bring down
> SPARKY and bring up the whole system.  Once submitted you could sign
off
> and go home.
>
> I'm sure I'm oversimplifying.  The one weak link has got to be "bring
> the system to it's restricted state then bring up only subsystem
> SPARKY", since I'm unsure if you could start that subsystem from the
> restricted state.  If I still had a spare AS/400 to play with I'd try
to
> work out how to bring the system from a restricted state to a
"minimally
> unrestricted state" with no TCP/IP, network services, interactive
> subsystem, QSPL, etc -- just SPARKY.  Perhaps you could code your
system
> startup script to conditionally bypass bringing up most of the good
> stuff based on a mode bit or flag in a data area.  Then you would
either
> start QCTL in backup mode or normal mode.
>
> We're at the point where we need to gut the Save option 21 anyway.  It
> takes too long with all our data.  I'm gonna have to figure out if I
> really know what I'm talking about so that I can split the SAVLIB
> *NONSYS into two batch streams to two 3590 tape drives.
>
> I'll let you know if it's easy, or if it's Advanced AS/400 System
> Administration.
>
> -Jim
>
> Manager - Technical Administration
> Dollar General Corporation
> <mailto:jdamato@dollargeneral.com>
>




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---