Saving spool files!

["Graap, Ken" <keg@xxxxxxxxxxxxxxxxxx>]

Time to share my frustration...

I'm in the process of planning a major configuration change to our
production system which will involve backing up the entire system (twice)
scratching all system data, initializing the system, adding 22 new disk
drives, reconfiguring RAID sets and ASP's and then reloading the entire
system. 

This is all a pretty straight forward process (even though it will take 32
hours!) for everything on the system except spool files.

I wish IBM would treat a spool file as a real object.

I know I can copy the spool file to a DB file or to a folder, backup up the
DB file or folder and then restore it later, in fact I do archive spool
files regularly via BRMS but only after they have aged about 30 days. 

The restore process results in the loss of several very important
attributes. The most important being the Jobname the file was originally
created in and the original creation date. This really makes things
difficult when trying to locate a spool file after it has been restored...
and ... we have 1000's of spool files users access on a regular basis. 

Does anyone else share my frustration? 

Does anyone have a good reason why IBM couldn't create a "spool object"
which could be saved and restored just like any other object on the system,
without changing original attributes? 

Doing this would sure make my life easier....

Geesh!

Kenneth

--
********************************
       Kenneth  E.  Graap
    IBM Certified Specialist
          AS/400   Professional 
          System  Administrator
 NW Natural - Information Services
           System Services
        503 226 4211 X5537
          FAX  503 721 2521
      keg@nwnatural.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
+---