You might have a situation where your database area is becoming full, but there is no room left on the current volume to extend the area. In this case, you need to move the area to a new volume with a larger allocation, but you do not yet have the solutions applied to support the Online Area Move scenario provided as part of CA Datacom/DB v14.01.
What are the steps needed to successfully move and recreate the database area?
To move a data or index area to another volume and make it bigger, here is the process to follow:
- Close the database in any CICS regions (if needed)
- Turn off access to the database from batch
- Close the database in the MUF
- Backup the existing data in the area
- Rename the current filename to .OLD (as a precaution)
- Allocate the new file for the area and Initialize it
- Load the backup data into the new file
- Turn on access to the file again
- Open the file in CICS regions (if needed)
Attached is a sample JCL file you can use that will do all of this except the first and the last steps. This JCL has two jobs - one to close the file (steps 2 and 3, above), and the other job to do the rest. If the first job fails, this means that something is accessing the file. You will need to research and see what might be using the file, and then either wait, or stop that job. Then you need to rerun this job again, and be sure this job finishes with a CC zero before continuing.
As always, please contact CA Technologies support for CA Datacom if you have further questions.