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



On 2/14/11 10:21 AM, Ketzes, Larry wrote:

Is there a way for me to see the queue that you reference below?

On 2/14/11 8:31 AM, CRPence wrote:
On 2/14/11 6:44 AM, Ketzes, Larry wrote:
Anyone have any experience with having damaged IBM cross
reference files that a reclaim storage did NOT correct?

<<SNIP>>

Thus any *functional* errors with the database XREF need to
corrected prior to attempting to correct any data [often referred
to as "damage"] errors. Otherwise a RCLSTG request which includes
the *DBXREF will simply enqueue a bunch of work pending correction
of the functional issue; on some releases and\or systems, the queue
may fill and "hang" the request because the job filling the queue
must wait until the queue is no longer full... thus a "catch 22"
situation.


The queue for the first job had long been QDBXREFQ in QSYS, so presumably still available by:

DMPSYSOBJ QDBXREFQ QSYS 0A C4

I do not recall the name of the second queue, but likely QDBXREFQ2 of the same type\subtype. However DMPSYSOBJ QDBXREF* QSYS 0A C4 SPACE(0 100) will almost surely produce output showing the NAME- of the second queue, so the first dump request can be modified to give the explicit name.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.