×
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 6:44 AM, Ketzes, Larry wrote:
Anyone have any experience with having damaged IBM cross reference
files that a reclaim storage did NOT correct?
The system database cross-reference feature implemented as system
jobs QDBSRVXR and QDBSRVXR2 must be functional for a RCLSTG [that
includes the *DBXREF] to be successful. Also pending database
operations that can not be completed without an IPL will not be
completed with RCLSTG SELECT(*DBXREF), but would be dismissed [if not
actually corrected] by RCLSTG SELECT(*ALL).
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.
Regards, Chuck
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.
midrange.com
