×
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 to Jim's suggesions. I want to add that sometimes a CHKPRDOPT may
point out some stuff. I actually have that documented in our instructions
to be performed after PTF application as it sometimes now reports the
product in error and that certain PTFs need to be applied. Pasting these
instructions loses the formatting in this list but here goes:
CHKPRDOPT PRDID(*OPSYS)
Could take 2-13 minutes to run. Seen it run 39 minutes on GDISYS2 3/7/13,
but that one did kind of freak me out and I opened a pmr (69150,082).
If you get “Errors found by CHKPRDOPT.” then hit F1 on that message to do
a DSPJOBLOG and see what is the matter.
Sample error that once affected all lpars:
Required PTF 5770SS1-SI37877 V7R1M0 not in correct status for PTF
5770SS1-SI37171 V7R1M0.
Program temporary fix (PTF) 5770SS1-SI37171 V7R1M0 requires PTF
5770SS1-SI37877 V7R1M0 to be temporarily or permanently applied.
I ended up doing:
APYPTF LICPGM(5770SS1) SELECT(SI38389 SI37877) APY(*PERM)
Repeat CHKPRDOPT until clean. Sometimes applying one ptf frees up another
error, as you can see by the later addition of SI38389 above.
Rob Berendt
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.
midrange.com
