×
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.
Bingo! Always good to the read the cume cover letter. Granted, I often
ignore additional hiper ptf's mentioned on the cume letter (but I always
put on the latest hiper group at that time also). But one should watch
out for double IPL ptf's. Ain't like the V2R1 days when PTFs were almost
always multiple IPL's but does still happen on occasion.
After the IPL to apply ptf's I check:
DSPSYSVAL QABNORMSW
DSPIPLA OUTPUT(*), the Keylock position
If either of those aren't right, then I resolve it.
WRKPTFGRP, if any of those say "Not Installed" I resolve it. I don't
worry about "Not Applicable" and that rot. You may want to look at the
groups you have and match it against those for your release at IBM. Those
which are for previous releases you may want to delete.
http://www-912.ibm.com/s_dir/sline003.NSF/GroupPTFs?OpenView&view=GroupPTFs
DSPPTF. I make sure that the cume level I just put on for both the
####-999 and the ####-SS1 say Temporarily Applied.
GO LICPGM
50. Display log for messages
CHKPRDOPT PRDID(*OPSYS)
That showed some messages once like "Required PTF 5770SS1-SI37877 V7R1M0
not in correct state for PTF 5770SS1-SI37171 V7R1M0", and I had to resolve
that.
Another thing you could do is
DSPPTF SELECT(*NOTAPY)
You may also want to look at
DSPPTF SELECT(*ACTRQD)
Rob Berendt
midrange.com
