Re: JCK tool not working after z/OS upgradation
Posted: Fri Jul 31, 2015 8:59 pm
To know for sure, you need to start on a console. Issue command and look for the line with IEASYS -- that will tell you which IEASYSxx member of SYS1.PARMLIB was used for the IPL. Go to that member of SYS1.PARMLIB and look for PROG=(xx,yy) -- there may be other values on this line -- which will give you the PROGxx and PROGyy members used for the LINKLIST and APF authorization. Those members are what the system is using -- if PROG=(L9,A0) is specified in IEASYSxx then you've got the right members. Otherwise, you'll need to look for different members of SYS1.PARMLIB.
One question that is unasked so far -- why was the JCK failure not discovered when testing the z/OS upgrade? There was a failure in the process if JCK wasn't tested, or if it was tested and worked then why did the upgrade subsequently break it? In other words, your site has a serious process flaw in your z/OS upgrade procedure that needs fixing before the next upgrade is done! Especially since z/OS 2.2 was announced this week for September delivery!
D IPLINFO
One question that is unasked so far -- why was the JCK failure not discovered when testing the z/OS upgrade? There was a failure in the process if JCK wasn't tested, or if it was tested and worked then why did the upgrade subsequently break it? In other words, your site has a serious process flaw in your z/OS upgrade procedure that needs fixing before the next upgrade is done! Especially since z/OS 2.2 was announced this week for September delivery!