× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Moe -

It's been a long time since I did a V5R3 upgrade, but in at least one
case I did do an upgrade from V5R1 straight to V5R3.  I don't remember
any special instructions for that release, but in MOST cases it is
safest after an upgrade to load the Cume (including DB and HIPERS)
immediately after the upgrade, while still IPLed to the A side.  Then
IPL to the B side to apply those, allow INZSYS to complete, load the
rest of your group PTFs and IPL to the B side again.  You can put the
Cume, DB and HIPERS in one image catalog, and the rest of your groups in
another.

This may take you an extra hour to do, but (IMHO) it's the safest way,
and if you do the upgrade from an image catalog you'll more than make up
the time there.  You PROBABLY could load and apply all the other groups
with the Cume, but why take the chance?

I remember one special case, but I don't remember the release, where
there where two MF PTFs that needed to be applied before the Cume.  This
was clearly spelled out in the Software Installation manual and the Memo
to users.

Regards,
 
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company


-----Original Message-----
From: as400@xxxxxxxxxxxxxxxx [mailto:as400@xxxxxxxxxxxxxxxx] 
Sent: Thursday, March 01, 2007 4:30 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Order of PTFs at release upgrade

Hi Scott,

Thanks for your reply.

But therein lies the problem: after rtfm I'm unsure.
Just as you say in your linked article I always applied Groups then CUME
then IPL - Except at release upgrade where the PTF installation
instructions instruct to skip the step where you would apply Groups and
other additional PTFs.

The PTF installation for the latest v5r3 CUME instructs to do it the
other way round, eg. CUME, Groups then IPL.

And here is what makes me unsure: there are no special instruction for
the release upgrade case.
Now does that mean there aren't any? As per the instructions do I just
put CUME and HIPER/DB Group into the same image catalog, specify Option
1 in the 'Prompt for media' parameter and that's it?
Even though this is a release upgrade?

I did rtfm, trust me. But I'd like to see this spelled out.

Regards,
Moe

Btw, the v5r3 software installation manual is of no help, it just refers
to the instructions that come with the CUME.


You are correct, Image catalog support was PTFed to V5R1 for upgrades
only.  However, if you have the space you CAN load the CDs for your
PTF
apply into an IFS directory and then create the *IMGCLG object after
the
upgrade.  Then it only takes seconds to do the ADDIMGCLGE from the
IFS.

As far as the order for applying PTFs after the upgrade the only
correct
anwser is RTFM.

See:

http://search400.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid3
_gci1102658,00.html

Regards,

Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company


-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@xxxxxxxxxxxxxxx]
Sent: Tuesday, February 27, 2007 9:35 AM
To: Midrange Systems Technical Discussion
Subject: RE: Order of PTFs at release upgrade

Evan,

My lack of experience is clear, but as I recall, image catalog support
was PTFd to V5R1, but was done only to support upgrade to V5R2.  I
seem
to remember that image catalog on V5R1 was barely usable...  I wonder
if
5.1 to 5.3 is supported...

Just curious,
Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Evan Harris
Sent: Tuesday, February 27, 2007 3:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: Order of PTFs at release upgrade

Hi Mo

other may have a different approach (I'll be watching this with
interest) but what I have settled on doing is:

- Load the cume first after the upgrade & IPL
- Apply the groups and hipers & IPL

As to the image catalogs, you need a catalog per set of CD's, so a
catalog for the cume, one for the DB group, one for the hipers, and so
forth. However, you can write a simple CL program to load all the
PTF's
- excluding the cume- from the various image catalogs and then IPl -
this is what I did on my last couple of upgrades (they were 5.2-to 5.4
upgrades so YMMV at 5.1)

Since the catalog is eseentially the same as loading from CD the
process
should be done the same way, but without having to load the pesky CD's
one at a time.

Hope this helps
Regards
Evan Harris

58 p.m. 27/02/2007, you wrote:

I'm still working on upgrading from 5.1 to 5.3.

I'm a little bit unclear on the PTF install process immediately after

the upgrade (before the IPL). I've received the latest 5.3 CUME along

with Hipers and DB Group. I'd like to install from image catalog.

Should I install the CUME then IPL, then install HIPERS and DB Group
or

install all three at the same time before the IPL?

There is a new option in GO PTF 8, 'Prompt for Media' that I'm not
sure

how to use.

Assuming CUME and groups are installed at the same time, do I load
them

all into the same image catalog or should I have a separate catalog
for

CUME and for HIPER/DB Group?

If the catalog is the same, which order should it be loaded in? CUME 
first or groups first?

Still assuming CUME and groups go on at the same time, depending on 
whether they are in different catalogs or not, how do I correctly use

the 'Prompt for media' option?

If somebody could give me a 'strategy' to follow on how and in what 
order to apply CUME, HIPERS and DB Group as part of the release
upgrade

I'd be most grateful.

Thanks in advance
Moe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.