RE: Longer backup after an IPL

["Evan Harris" <spanner@xxxxxxxxxx>]

Hi Mike

Agreed re the compress I wasn't really thinking about the details, just
things that could cause an issue.

You mention that you are not there to change tapes on weekends. How do you
manage the tapes for the weekend save, in particular the positioning. Do you
do two saves to one tape on weekends ? Could the longer save after the IPL
be the tape repositioning ? 

I still think as per my earlier email that you should compare the steps in
the job on a one to ne basis to see which bit of it is taking longer. At the
moment you are trying to see why the whole process takes longer - break it
down into its constituent parts as that will give you more insight into what
the issue might be.

Look at the trees not the forest :)

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Thursday, 10 April 2008 12:31 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: RE: Longer backup after an IPL

The script does the same backup process every night Mon-Fri. Weekends are
different since we are not open for business and not here to change tapes.
The script does a save of security data, configuration, all non-system
libraries except our test libraries, all of the IFS. We IPL every Sunday AM
and savsys once a month. The only time we do a GO SAVE 21 is just before an
upgrade or OS or hardware.

Wouldn't it be odd if a save of an object caused it to be decompressed? What
would be the purpose of doing compression if on every save
(which every object on the system should be saved at least once a month) the
object was decompressed.