Re: RUNSQLSTM drop/create alias error -- MIDRANGE-L

× 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.

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.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.