How to move a CA Datacom/DB area to a new volume.

book

Article ID: 33303

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Summary: 

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?

Instructions: 

To move a data or index area to another volume and make it bigger, here is the process to follow:

  1. Close the database in any CICS regions (if needed)
  2. Turn off access to the database from batch
  3. Close the database in the MUF
  4. Backup the existing data in the area
  5. Rename the current filename to .OLD (as a precaution)
  6. Allocate the new file for the area and Initialize it
  7. Load the backup data into the new file
  8. Turn on access to the file again
  9. Open the file in CICS regions (if needed)

Additional Information:

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.

DBMOVE.txt

As always, please contact CA Technologies support for CA Datacom if you have further questions.

 

 

 

Environment

Release:
Component: DB

Attachments

1558535560946TEC1339216.zip get_app