DFS2574I AREA=aaaaaaaa CLOSED|STOPPED, (RECOVERY NEEDED, RSN=nn)
Explanation
RSN=
) for the
problem: - 00
- Reason code unavailable for message. This code is the default.
- 01
- VSO area aaaaaaaa had a severe error during emergency restart.
- 02
- VSO area aaaaaaaa had a severe error during emergency restart.
- 03
- Emergency restart could not process area aaaaaaaa because a severe error had occurred on the area before failure.
- 04
- Area aaaaaaaa must be recovered following an /ERE COLDBASE command.
- 05
- Area open failed during emergency restart.
- 06
- VSO area aaaaaaaa had a severe error during emergency restart.
- 07
- Area aaaaaaaa had a read error during emergency restart.
- 08
- Area aaaaaaaa had a write error during emergency restart.
- 09
- VSO Area aaaaaaaa could not be recovered across an XRF takeover because a storage request failed.
- 10
- Either Emergency Restart or XRF Takeover determined that DASD writes failed to complete for a unrecoverable DEDB area. The area must be restored from an Image Copy.
- 12
- Emergency restart could not process area aaaaaaaa due to insufficient storage required for the area private buffer pool.
- 13
- During an /ERE or XRF TAKEOVER process, an inconsistency was noted in the VSO options for an AREA. The AREA is stopped. Message DFS2574I is issued with reason code 13. Issue a /START AREA or UPDATE AREA START(ACCESS) command to correct the inconsistency.
- 14
- An area has been stopped and marked as recovery needed due to one of the SVSODR options. These options take effect at emergency restart processing for SVSO areas.
- 15
- Emergency restart could not process area aaaaaaaa due to an inconsistency in the SVSO private buffer pool. The preceding message, DFS2835I, identifies the inconsistency.
System action
Processing is terminated for the named area. The Prohibit Authorization flag is set for the database or area, unless the message is in response to a /DBR command that includes the NOPFA option.
Operator response
If message DFS3712A or message DFS3713A preceded this message, correct any VSAM errors before restarting the area; then run recovery, if necessary.
If the area is indicated as recovery-needed, recover the area using the Database Recovery utility before restarting the area.
If the area is in recovery-needed status because an extended error queue element (EEQE) still exists, issue a LIST.DBDS command to find the EQERBA. If a write error EEQE with a null EQERBA exists, it was created because IMS lost connectivity with the coupling facility, causing CASTOUT to fail. The area is marked as temporary recover-needed. When connectivity is re-established and CAST is successful, the status is reset. If you find anything other than null EQERBA, recover the area using the /UNLOCK SYSTEM command.