Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Handling an Incompletely Processed MONITOR_SUBLISTS Request z/OS MVS Programming: Sysplex Services Guide SA23-1400-00 |
|
An IXLLIST REQUEST=MONITOR_SUBLISTS can complete prematurely for
one of the following reasons:
When a MONITOR_SUBLISTS request ends before processing all the
IXLYMSRI entries, list services sets the IXLLIST return and reason
codes as follows:
List services also returns in the LAAMNSLS_FAILINDEX field of the answer area, the index of the first unprocessed IXLYMSRI entry when the request completed prematurely. The MOSVECTOR bits that correspond to the IXLYMSRI entries between STARTINDEX and LAAMNSLS_FAILINDEX minus one contain valid monitored object state information. To continue processing the IXLYMSRI entries after processing the entries that were successfully completed, reissue the MONITOR_SUBLISTS request with the STARTINDEX keyword specifying the index of the first unprocessed IXLYMSRI entry to be processed. If the premature completion was caused by a lack of EMCs in the structure, you must first either release some EMCs or rebuild the structure allowing for more EMCs. You can reissue the request to continue processing the IXLYMSRI entries when either of the corrective actions is complete. Note that if the corrective action was to rebuild the structure, you must first start monitoring for all the sublists you were monitoring prior to the rebuild before reissuing the request to process the IXLYMSRI entries. If the premature completion was caused by a list number that was not valid in an IXLYMSRI entry, either correct the list number value and reissue the request with STARTINDEX updated to the value in LAAMNSLS_FAILINDEX or update STARTINDEX to skip over the IXLYMSRI entry containing the list number that was not valid. |
Copyright IBM Corporation 1990, 2014
|