Re: Applying PTFs *PERM prior to new Cumulative/Groups -- MIDRANGE-L

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

That's 'kinda' what I was looking for. When I prompt the command, it requires all of this:

APYPTF LICPGM(*ALL)
APY(*PERM)
DELAYED(*YES)
IPLAPY(*YES *APYPERM)

That seems reasonable, so I'm going ahead with it.

Then, I'll load do the regular GO PTF option 8 to load PTFs and have them ALL apply at the next IPL.

As to the CHGIPLA, it's an unattended backup/IPL so it's "go" or "no go".

Thanks for the help!

"Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."--Tweedledee

On 04/19/2013 1:18 PM, Pete Massiello - ML wrote:

No problem, just do a APYPTF *PERM DELAY(*YES) and that should mark those PTFs to be perm applied, and you will be good to go.

Do your regular GO PTF option 8 to load PTFs and have them ALL apply at the next IPL

You can always do a CHGIPLA before the IPL and set the machine to come back up in restricted state, check everything, and if good start the controlling subsystem, or IPL again.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com

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.