|
Once you get current, keeping current isn't bad. Once a month I use Fix Central to download updates. Select "Groups, HIPERS, Cumes". When presented with the list of groups, click the first one after the Cume (should be HIPERs) and shift-click the last one in the list. For V5R3 that's 25 groups. Do the option to only download the PTFs that aren't already on the machine. I'm too lazy to mess with the CD image catalogs so I just do the above on each of our LPARs. Some things are downloaded multiple times (once for each LPAR) but in the end bandwidth is cheaper than my time. It also means I don't have to even think about the variances in LPPs on each LPAR; all LPARs get anything they could possibly need. Average d/l per LPAR varies but I'd say it'll run around 500-800MB/month/LPAR. If you've any kind of decent internet pipe it won't take that long. Average time/month/LPAR is 3-5 minutes; just long enough to sign on the Fix Central and do the selection. The d/l runs in the background and I ignore it. Unfortunately I can't do the above for Cumes. So once or twice a year I'll pull the CD images down once and FTP to all of the machines, create the image catalog, etc. It's a lot more hassle than the Groups but is still easier than handling physical media (one of our machines is 8 miles from me; the other is about 30 miles away). I don't worry much about the Cumes as most things that are likely to impact us will be included in the Groups. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Monday, November 13, 2006 12:01 PM To: Midrange Systems Technical Discussion Subject: Re: Cume & Image Catalogs Actually, I think when you order the cume via FTP it also comes with the hiper and database group. Ordering that way also gets rid of the chicken and egg argument.
From the file ilstCUME.txt in my download:
Version
Release
PTF# Reason PTF Listed Status Product Mod Lvl
-------- ----------------- --------------- ------- --------
MH00651 CO-REQ OF MH00681 Sup'd by MH00677
MH00666 CO-REQ OF MH00683 Sup'd by MH00677
MH00637 CO-REQ OF MH00674 Sup'd by MH00677
MF37730 ORDERED Sup'd by MF39573
...
SF99504 ORDERED <<< Shipped >>> SEL Lst V5R4M0
SF99539 ORDERED <<< Shipped >>> SEL Lst V5R4M0
...
Then I just load this image catalog all at once.
I order all groups and put them into a different image catalog. I used
to pick and choose applicable groups but now I just order them all for
my version of OS. With multiple lpar's running different products and
God knows how many times we add a product after we put on the cume and
groups and now have to reinstall them. Having the latest already
downloaded makes it really easy to reapply.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Buzz Fenner" <bfenner@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/13/2006 12:29 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Discussion" <Midrange-L@xxxxxxxxxxxx>
cc
Subject
Cume & Image Catalogs
Because of habit, when loading cume & hiper volumes to image catalogs,
I've
always placed them into two separate image catalogs. That sort of
dictated
at install time, to process the hipers first, then process the cume and
bounce the box. I've never tried the 'prompt for media' option when
installing a PTF package, since I used two different image catalogs.
Can
the hiper volumes be added after the cume volumes on the same image
catalog
to smooth things along?
Buzz Fenner
Systems Analyst/Network Administrator
City Water & Light
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.