Thanks why we do a weekly IPL. Just to get any PFTs applied that need it. We just left it weekly because our script is not really setup to do something once a month and we also want to be sure the IPL happens after some other weekend only automated tasks are done (reorgs, dsppgmref to a file, etc)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US)
Sent: Wednesday, April 09, 2008 8:39 AM
To: Midrange Systems Technical Discussion
Subject: RE: Longer backup after an IPL
I'd suggest that you drop to a monthly IPL. There's no longer any good
reason to IPL weekly. Even monthly isn't really needed; we mostly do it
to have a scheduled window for applying PTFs and other system
maintenance.
Our non-production LPARs are IPLed as needed, which means rarely.
--
John A. Jones, CISSP
Sr. Analyst, Global Information Security
Jones Lang LaSalle, Inc.
Voice: +1.630-455.2787
FAX: +1.312.601.1782
Email: john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Wednesday, April 09, 2008 7:31 AM
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.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Tuesday, April 08, 2008 3:28 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Longer backup after an IPL
Hi Mike
What does the backup script do ?
Seems to me that a good place to start would be a compare of the joblogs
on
the IPL backup and another one to account for the differences.
If the differences is just in the save operations could you do the
DSPOBJD
before each of them and compare the objects and sizes being saved? This
will
tell you if for instance something is getting compressed and then the
first
save caused it to be uncompressed (this is a complete shot in the dark).
If I really had to just guess I'd look for a weekly housekeeping job
that
runs weekly the day after the IPL runs. Don't forget to check the GO
ASSIST/CLEANUP settings.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Wednesday, 9 April 2008 3:01 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: RE: Longer backup after an IPL
Just a followup for the archives....
Last night was the first backup since our IPL followed by the DSPOBJD of
the
entire system. No change in the length of the backup.
First backup after an IPL takes from 3:30 until about 7:20. Rest of the
week
is 3:30 until about 6:45.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This email is for the use of the intended recipient(s) only. If you have
received this email in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message. We cannot accept liability for any loss
or damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the attorney-client
privilege. If you are the intended recipient and you do not wish to receive
similar electronic messages from us in the future then please respond to the
sender to this effect.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
