Re: chkprdopt fails

[CRPence <CRPbottle@xxxxxxxxx>]

  Check the creation date of the objects.  Also the history log and the 
QDBSRVXR joblog.  The *DBXREF might have had to recreate those files. 
Regardless, those files should not be missing at any time unless the 
QDBSRVXR job reported the loss; most likely to be seen at startup of the 
job [during file validation and open], but could also transpire at 
normal ops in response to an error for the job accessing the tables at 
run-time.  Since the files should never be missing, that they were 
either gone or their /owned by OS/ information had been missing [dspobjd 
qsys/qadb* *file *service], then /when/ the CHKPRDOPT is run should be moot.

  However to clear the /error/ with the product, a successful CHKPRDOPT 
must be completed... which was done.  This implies that the work to 
recreate the files [from a backup definitions stored on the system 
rather than having to restore from media; i.e. OS language install] had 
since completed.  This activity should be reflected in the history and 
in the QDBSRVXR joblog, as noted earlier.

  Since this was a new IPL, the SCPF joblog might need to be checked 
for activity related to those files, and the QDBSRVXR joblog [and 
history] from prior to that IPL, to determine when\where the problem 
originated.

Regards, Chuck

On 07 Mar 2013 03:11, rob@xxxxxxxxx wrote:
> The files are all there. Apparently running the CHKPRDOPT so soon
> (under 5 minutes) after QCTL comes active can run into conflicts from
> processes still going on from the IPL.
> CHKPRDOPT is better now.
>
> On 07 Mar 2013 01:15, rob@xxxxxxxxx wrote:
> > CHKPRDOPT PRDID(*OPSYS)
> > ...
> > CPD3DC8
> > *FILE QADBXTBCLA in QSYS not found for product 5770SS1 option *BASE
> >    release V7R1M0.
> > <ed:> and for each of *FILE QADBXTBFIL, QADBXTBFSN and QADBXTRIGB
> > Exit program processing found error in product.
> > Exit program processing failed.
> > Product 5770SS1 release V7R1M0 option *BASE load 5050 not correctly
> >    installed.
> > ...
> > Errors found by CHKPRDOPT.
> >
> > I have the pmr open <<SNIP>>
> > and, CHKPRDOPT took 39 minutes to run.