Re: RUNSQLSTM drop/create alias error

Chuck,
I had sent your entire message to our ops person who still wanted IBM involved rather than try your suggestions. I wasn't sure if I was 'allowed' to run anything like that. I believe we are not at the release required for RCLDBXREF, though. We are at V5R2.

Our people are thrilled with IBM support and as one programmer put it, "We're paying for the highest level of support they provide... might as well take advantage of it!"

Thanks again,


Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email

CRPence <CRPbottle@xxxxxxxxx> 05/19/2008 9:51 AM >>>

Note: The Option-5 from GO LICPGM is intended to diagnose an issue in
preparation for an upgrade, *not* to determine the need to perform the
RCLSTG SELECT(*DBXREF) for normal run-time concerns. So although it may
be 'much quicker' to diagnose that _an issue_ may have previously been
diagnosed with the *DBXREF data, it is in fact diagnosing the wrong
concern. The two means I noted prior, the program QDBXRCTX and the
command RCLDBXREF, are the proper ways [the latter, on releases where it
exists] to interrogate the status of the *DBXREF.

Regards, Chuck

Frances Denoncourt wrote:

I called IBM Friday. Tracy had me GO LICPGM/option #5 [prepare for
install]. Didn't know where this was taking me, but sure enough, got
this message:
*Database cross-reference files are in error*

Tracy said that this is much quicker when diagnosing that particular
error. She said the RCLSTG dbxref should only take 20 minutes to one
hour.

Operations ran the RCLSTG over the weekend along with the latest PTFs.

I tested the RUNSQLSTM this morning and we are back in business.
Thanks for all of your help.