Re: Apparently Hosed V5R3 Install

The error being received indicates a failure of the LIC. There will be a VLog VL02000306 which is a /function check/ error; effectively the same as CPF9999. The PRTINTDTA ERRID(010036DE), or some such, would spool that vlog. There may be other relevant vlogs however, typically prior to the 0200 0306. The file name seems to suggest that group PTF processing was unable to be tracked; possibly limited only to the access path for that file. The error during query processing may be a side effect of the query engine inquiring of the PTF database to determine [re]optimization rules to follow; I am not sure if\why the code would access the group information versus a specific PTF.

The errors definitely indicate to call for support, and that is what I would both recommend and do. Possibly the recovery will require deleting the PTF database [or the one file and logicals] and then reinstall of the cumulative, or perhaps delete of the PTF database and then reinstall both the LIC and OS. Review of the SCPF joblog, the vlogs, and history, may indicate that many PTF status are suspect due to failures to update the PTF database.

Regards, Chuck

Bill wrote:

I'm looking for WWYD (What would you do) for the following situation. V5R3 on a 720 over the weekend. Everything was fine. Cum PTF apply after an intervening IPL. A couple of PTF option 8's with *NONE as the device. Some ptfs still remain in IPL action status. After another PTF 8, a review of job log shows 5722XE1 has a damaged PTF (SI26600). Re-loaded and re-applied, went damaged again. So re-loaded and then removed *Perm with requisites. Another in 5722XE1 goes damaged, same process for it. 5722XE1 is now "clean".

So, now the PTF 8 *none (no ipl) is tried again and I get the following:

Function error X'0306' in machine instruction. Internal dump identifier (ID) 010036EB.
Failure for device or member QAPZGRP2 file QAPZGRP2 in library QUSRSYS.
Error while processing file *N in library *N.
Function check. CPF9846 unmonitored by QPZAPC at statement *N, instruction X'0FBA'.
Pointer not set for location referenced.
Function check. MCH3601 unmonitored by QPZAPC at statement *N, instruction X'1572'.
PTF install processing failed.

I'm also getting things like this in random jobs:

00 02/17/09 03:05:03.910880
QQQOPNQF QSYS 0366 CST600C BPCDREL02
Message . . . . : Member FRTL02 file FRTL02 in BPCSCDELCF opened.
Cause . . . . . : The file was opened with either the Open Data Base File (OPNDBF) command or the Open Query File (OPNQRYF) command, and the value FRTL02 was specified for the OPNID parameter.
60 02/17/09 03:05:22.550488
< odeHighUse 000E8C QDBGETKY QSYS
From Program . . . . . . . : QuGateCodeHighUse
Message . . . . : Function error X'0306' in machine instruction. Internal dump identifier (ID) 010036DE.

My current plan is to try a re-application of the CUM, but I'm concerned that the whole PTF process is hosed - but don't know for sure at this point. The download of the images is going to take the rest of the day, so I've got some time before I go down that road. I do have SW support for this machine, but I figure that it might be a wasted effort if the CUM isn't fully applied yet. So, WWYD?