× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2007

Re: Order of PTFs at release upgrade

Maybe I need to clarify what I'm unclear about:
I'm not sure whether to apply HIPER and DB Group packages (the two that come with the CUME) right after the CUME before the first IPL after the release upgrade (eg. before INZSYS).
I'm however clear about not applying any other Groups/Individual PTFs until after the upgrade is complete. 

I appreciate your help.
Moe

as400@xxxxxxxxxxxxxxxx wrote:

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.

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.