The following indicate that the CRQ may be corrupted:
- Message ARC1506E was issued.
- Message ARC1187E was issued.
- Recall requests are unexpectedly not being selected for processing.
Note: If recall requests are unexpectedly not being selected for
processing, issue the QUERY ACTIVE command and examine message ARC1541I.
This message displays the factors that affect the selection of requests
from the CRQ. A status of anything other than CONNECTED or a hold
level of anything other than NONE are probable reasons why certain
recall requests are not being selected.
Note: An unexpected loss of connectivity to the CRQ
may also introduce errors, but in most cases DFSMShsm automatically
corrects those errors. When this occurs, you may see the multiple
issuance of message ARC1102I. Message ARC1102I is issued when DFSMShsm
attempts to recall a data set that has already been recalled. It is
normal for this message to occur at the time of a loss of connectivity
and it does not indicate a problem with the CRQ list structure.
If you believe that the CRQ has been corrupted, issue the AUDIT
COMMONQUEUE(RECALL) FIX command. When this command is issued, DFSMShsm
scans the entries in the CRQ and attempts to correct logical inconsistencies
within the structure. AUDIT cannot correct all types of errors and
may report that zero errors were detected even though there are errors
in the CRQ structure.
Note: The following parameters are not used with AUDIT COMMONQUEUE:
- ALL
- OUTDATASE | SYSOUT | TERMINAL
- REPORT(ALL | ERRORS)
- SERIALIZATION(DYNAMIC | CONTINUOUS)
If after issuing the AUDIT command, message ARC1506E or message
ARC1187E occurs repeatedly, or certain data sets are unexpectedly
not being selected for recall processing, refer toOther space management considerations for
more information about correcting errors within the CRQ.