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



IIRC, a sure-fire way to hit the link/loader error was to install a test PTF and then forget to remove it when the final was released.

The easiest way to fix *most* PTF installation problems is to do a APYPTF LICPGM(*ALL) DELAYED(*YES) IPLAPY(*NO) to cancel the IPL Action, then install the most current cume from GO PTF Option 8. That will fix you 90% of the time. If you don't reset the IPL Action you will just have the same thing happen again, and you should note that if you don't specify DELAYED(*YES), the IPLAPY parameter is ignored.

During an OS upgrade you should install the cume from the A side and then install the groups after the INZSYS runs. Outside of an upgrade you can usually install everything together in one shot. As always, you should RTFM. Technology Refresh PTFs are a newer type that (I believe) *always* requires a separate IPL.

But IPLs don't usually take 8 hours anymore, so you really don't have much of an excuse for not staying reasonably current on PTFs.


Regards,
 
Scott Ingvaldson




-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Tuesday, December 13, 2011 7:11 AM
To: Midrange Systems Technical Discussion
Subject: RE: determine v5r4 ptf level

I too have see the link loader issue. However, when was the last time
you've seen that? CISC box?
I think the resolution was to slip the LIC and reinstall all the PTFs (the
right way).


Rob Berendt

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.