DFS3702I AREA/ADS OPEN FAILED
REASON
CODE=nn message subtext
Explanation
IMS is shutting down or IRLM is being disconnected from this IMS.The DEDB area or ADS failed to open. The
reason code indicates the cause of the failure. The second message
contains one of the following reason codes and message subtext (nn)
which briefly explains the cause for the error.
- Code (Dec)
- message subtext
- 01
- AREA=areaname DD=ddname DEVICE TYPE NOT SUPPORTED
- 02
- AREA=areaname DD=ddname EQE EXISTS
- 03
- LOCK FOR UPDATE TO AREA=areaname FAILED
- 04
- AREA=areaname CI SIZE > USER DEFINED BUFFER SIZE
- 05
- AREA=areaname BUFFER PAGE-FIXING FAILED
- 06
- AREA=areaname AUTHORIZATION FAILED
- 07
- UNLOCK FOR UPDATE TO AREA=areaname FAILED
- 08
- LOCK FOR READ TO AREA=areaname FAILED
- 09
- AREA=areaname HAS NO AVAILABLE ADS
- 10
- AREA=areaname DD=ddname DUPLICATE ddname FOUND
- 11
- AREA=areaname SPACE FOR ADSC(S) UNAVAILABLE
- 12
- AREA=areaname RECEIVED A BAD RETURN CODE FROM DBRC
- 13
- AREA=areaname DD=ddname MEDIA MANAGER CONNECT FAILED
- 14
- AREA=areaname DD=ddname INCONSISTENT DSN SPECIFIED BETWEEN IN RECON AND IN ALLOCATED DATA SET
- 16
- AREA=areaname VSO I/O TOLERATED DATA LOST
- 17
- AREA=areaname DD=ddname ALLOCATION FAILED
- 18
- AREA=areaname UPDATE LEVEL INCONSISTENCY EXISTS
- 19
- AREA=areaname DD=ddname 2ND CI I/O ERROR OCCURRED
- 20
- AREA=areaname DD=ddname RDJFCB/MODCB ERROR
- 21
- AREA=areaname ACCESS INTENT IS NOT UP/EX FOR REORGANIZATION RECOVERY
- 22
- AREA=areaname REORGANIZATION IDENTIFICATION FAILED
- 23
- AREA=areaname ALL THE ADS'S ENCOUNTERED 2ND CI ERROR
- 24
- AREA=areaname NOTIFY TO OTHER SUBSYSTEM(S) FAILED
- 25
- AREA=areaname SOME ADS ENCOUNTERED 2ND CI ERROR
- 26
- AREA=areaname ACBLIB AREA NUMBER NOT EQUAL DMAC
- 27
- AREA=areaname DD=ddname GETMAIN FOR MEDIA MANAGER CONTROL BLOCKS FAILED
- 28
- AREA=areaname DBD AND DATA SET DEFINITIONS INCONSISTENT
- 29
- AREA=areaname IMS LEVEL OF AREA NOT SUPPORTED
- 30
- AREA=areaname CALC. NEXT SDEP NOT WITHIN SDEP RANGE.
- 31
- AREA=areaname DD=ddname THE HIGH RBA IS LESS THAN THE END OF THE AREA
- 34
- AREA=areaname 2ND CI EEQE OWNED BY SHARING SYSTEM
- 35
- AREA=areaname UNABLE TO OBTAIN VSO CONTROL BLOCK
- 36
- AREA=areaname UNABLE TO OBTAIN VSO CONTROL BLOCK
- 37
- AREA=areaname REQUEST FOR DATA SPACE FAILED
- 38
- AREA=areaname DATA SPACE AUTHORIZATION FAILED
- 39
- AREA=areaname UNABLE TO OBTAIN VSO CONTROL BLOCK
- 40
- AREA=areaname IMODULE GETMAIN FAILURE OCCURRED
- 41
- AREA=areaname COUPLING FACILITY CONNECT FAILED
- 42
- AREA=areaname VSO AREA HAS IOT EEQES
- 44
- AREA=areaname DD=ddname MADS I/O timing is detected
- 45
- AREA=areaname REQUEST FOR VLOCK FAILED.
- 46
- DEDBGT2K FUNCTION NOT ENABLED.
System action
When an open ADS failure occurs during the processing of the DEDB area data set Create utility, the named area continues processing. An invalid return code is returned to the utility. Otherwise, the area is stopped.
Programmer response
- Code (dec)
- Meaning
- 01
- Check the appropriate VSAM catalog or JCL DD statements if a disk device is specified for the named ADS. If dynamic allocation occurs, check the dynamic allocation parameter list to find a device type specified for the named ADS. If a different device type was specified, correct the device type to the disk device and rerun the job.
- 02
- This condition should not occur. Check why the named ADS was changed to an available status. After changing the named ADS status to an unavailable status, rerun the job.
- 03
- The application program terminates when the dependent region abends.
After preparing the tracing facilities for lock, rerun the job.
This reason code can be issued if a Fast Path area open failed because the PI limit of 63 active waiters was reached.
- 04
- Check the database definition (DBD) and the VSAM definition for the named area. Also, check the BSIZ in the startup procedure. Correct the control interval (CI) size or buffer size (BSIZ), and rerun the job.
- 05
- The number of allocated buffers is not sufficient to fill the
buffer allocation request. The number of allocated buffers is defined
by the DBBF parameter in the IMS EXEC
parameters.
For a description of the
dbbfvalue, see the IMS system definition information. - 06
- Follow the Programmer response of message DFS3709A or DFS3711A either of which might precede this message.
- 07
- See the description for reason code 03 in this message.
- 08
- See the description for reason code 03 in this message.
- 09
- Check an ADS list of the DBRC RECON data set and change at least one ADS to an available status by using the CHANGE.ADS command.
- 10
- The named ddname exists in the IMS subsystem, which means the ADS has been opened. If the ADS to be opened is already open, delete the DD statement for the named ddname. If the named ddname was incorrect, and thus coincidentally matched another ddname in the IMS subsystem, correct the input ddname and then rerun the job.
- 11
- Rerun the job later when the common service area (CSA) usage is low.
- 12
- Check the information given for the DBRC RECON data set for the named area. If the information is incorrect, correct the error and rerun the job.
- 13
- Follow the programmer response in message DFS2569I, which precedes this message.
- 14
- Either the dsname specified in the ADS list of the DBRC RECON data set, the JCL DD statement, or the dynamic allocation parameter list is incorrectly specified. Correct the specified dsname and rerun the job.
- 16
- Case 1
- The area had the virtual storage option active when an XRF takeover
occurred, and an EEQE was created to show that the area had I/O tolerated
data in its data space. Before the I/O toleration purge, one of the
following events occurred:
- The area was shut down internally due to a severe error and has not yet been recovered.
- IMS failed and was restarted with a cold start; the area has not yet been recovered
- Case 2
- The VSO area lost connection to its structure, and an EEQE for RBA 0 was created to indicate area has I/O tolerated data in the old structure. If an area is able to reconnect to the old structure, IMS resolves the I/O toleration data and deletes the EEQE. If the area was connected to a new structure, the I/O tolerated data in the old structure is lost.
In either case, the I/O tolerated data has been lost and the area must be recovered. Ensure the ADS marks unavailable. Run the database recovery utility to recover the lost data and delete the EEQE.
- 17
- If a DD statement is specified, specify the correct ddname. If the DD statement is missing, specify a DD statement. (The DD statement is located in the control region JCL.) If a dynamic allocation failed, follow the programmer response for DFS2502W or DFS2503W. Then, rerun the job.
- 18
- Run your database print program or a VSAM access method service program to print all the area data sets. Find at least one correct ADS, issue a CHANGE.ADS command for those ADSs that are incorrect, change the available status to an unavailable status, and rerun the job. Or follow your recovery procedure.
- 19, 20
- Check the DBRC RECON data set if the named ADS is set to an unavailable status. If the named ADS was set to an available status, change the status by the CHANGE.ADS command and rerun the job.
- 21
- Reorganization recovery is requested, but ACCESS INTENT is neither UP nor EX. Set ACCESS INTENT to UP or EX with /START DB ACCESS or UPDATE DB START(ACCESS) SET(ACCTYPE()) command and rerun the job.
- 22
- The system tried to check whether the reorganization utility was running or had been running among subsystems, but failed. Either IMS or IRLM might not be working correctly, thus causing a notify error. Rerun the job, and if the same error persists, restart IMS, IRLM, or both.
- 23
- In a block level sharing environment, reorganization recovery ended successfully, and the system then tried to update the second CI or the area, but failed. Run the database recovery utility to recover the area, and then rerun the job.
- 24
- In a block level sharing environment, reorganization recovery ended successfully. The system then tried to update the second CI of the area for the other subsystems, but failed. Either IMS or IRLM might not be working correctly, thus causing a notify error. Rerun the job, and if the same error persists, restart IMS or IRLM, or both, then rerun the job.
- 25
- Check which area data sets are not available in the DBRC RECON data set. If you want to recover the area data set, run the DEDB Area Data Set Create utility, or rerun the job.
- 27
- Start the area when the common service area (CSA) usage is low.
- 28
- DBD information in the DMAC is inconsistent with the area definition
as found in the second CI of the area or area data set. Note: This message could be seen if the DEDB Alter utility was run, and PREOPEN opened the area before restart or the XRF tracker processed the log records to complete the DEDB Alter based on the log record stream. Verify that the DMAC from the IMS memory matches the DMAC on the ADS before attempting to recover the DEDB area. This verification can be accomplished by manually inspecting the DMACs, or by forcing the area to open by issuing /STO AREA , /STA AREA, and running a job to access the DEDB area. If the DMACs match or the area can be accessed, no further action is required.One of the following events occurred:
- An area definition was changed by a DBDGEN (for example, CISIZE, number of UOW elements, number of RAPS). If the DBDGEN is to be changed, redefine it and rerun the job.
- An area was redefined with different characteristics, such as CISIZE or CYLINDERS. If an area definition is to be changed, the area must be reorganized by an UNLOAD/LOAD operation. Check the last DBDGEN and VSAM DEFINE for consistency with the current characteristics or the area data set.
- 29
- During area open, the second CI of the area was found to have
a structure for an IMS Release
level earlier than Version 1 Release 3. Determine why the identifier
is incorrect. Rerun the job with the correct data set.
The area must be reinitialized. Unload the area, run the Initialization utility, and then reload the area.
- 30
- The RBA calculated as the next position to insert sequential dependents (DMACNXTS) is not within the range of valid RBAs for sequential dependents for the area. Print the second CI for the area. If the error is not apparent from the second CI (DMAC), contact IBM® Software Support for assistance.
- 31
- The high used RBA of the AREA/ADS was not equal to the high allocated
RBA. The Fast Path AREA might have been defined to VSAM, but the Fast
Path format/initialization program might not have been run, or the
Database Image Copy utility or the DEDB Area Data Set Create utility
might not have completed successfully.
Use the list catalog (LISTCAT) command to find the high used and high allocated values. Delete and redefine the AREA/ADS. Then, recover the AREA/ADS by either using the DEDB Initialization utility and an application to restore the data, or the Database Image Copy utility and a forward recovery method.
- 34
- During Open processing of the specified Area, it was determined that an EEQE exists for the second CI of the Area and that the EEQE is owned by a sharing IMS subsystem. On the sharing subsystem, use the /UNLOCK SYSTEM command to eliminate the EEQE.
- 35
- During Area open, a request for a VSO control block failed. Rerun job when CSA use is lower.
- 36
- During Area open, a request for a new VSO control block failed. Rerun job when CSA use is lower.
- 37
- A request for a new data space was issued during open processing of the Area, but the request failed. See DFS2444I, which precedes this message.
- 38
- A new data space was obtained during open processing of the Area, but the request for authorization of the data space failed. See DFS2445I, which is precedes this message.
- 39
- During Area open, a request for a new VSO control block failed. Rerun job when CSA use is lower.
- 40
- Determine if insufficient CSA/ECSA storage has been allocated to IMS, or if excessive storage is being used.
- 41
- The area is not loaded into the Coupling Facility. This situation does not prevent access to the area unless preceded by message DFS2819A.
- 42
- A /START AREA or UPDATE AREA START(ACCESS) command was issued but the area was not started because it has IOT EEQEs. Message DFS2492I is generated before message DFS3702I RSN=42. See message DFS2492I for additional information.
- 45
- ADS is still in long busy mode at open time. During open processing for an SVSO area, a request to get the VLOCK failed. This lock serializes the SVSO processing across a data sharing environment.
- 46
- Stop IMS and specify DEDBGT2K=Y in the FASTPATH section. Then, restart IMS.