How to add volumes to an SMS-managed CA Datacom database file.

Document ID : KB000033629
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary: 

A CA Datacom database file (index or data) appears as any other standard sequential file to the operating system, and can be managed in the same way.

In the case of files under SMS control, it is possible to allocate these database areas to multiple volumes in a storage group. As the current allocation becomes full and all volumes in the storage group are used, it is sometimes necessary to add more volumes to the group to keep the area from becoming totally full and causing an application outage.

This document will explain how to add more volumes to the available list of candidates in the SMS storage group used by the CA Datacom database area. Due to the size of a given area, it may not be possible to perform a standard process to backup, allocate a new file, initialize and load it, so this procedure is a good alternative.

Instructions: 

This process can be done with minimal disruption or outage for the application, and for best effect, should be done during a period of light activity for the database area.

  1. Identify the filename for this area from a CXX report.
  2. Add the additional volumes to the appropriate SMS storage group used by this file.
  3. If using a particular SMS Data class for this file, be sure that the volume limit encompasses these new volumes.
  4. Determine how many volumes you want to add to the candidate list for this file.
  5. Run a LISTCAT report or your own utility before the change to identify the “before” attributes.
  6. Execute IDCAMS (or use a TSO command) to change the catalog definition for the file to add the new volumes. For example, if adding 4 volumes to the definition, you would use the command:
    ALTER dsn AVOL(* * * *)
    The number of asterisks in this command reflect the number of new volumes being added.
  7. Run a LISTCAT report or your own utility after the above command to ensure the file is now defined correctly.
  8. Close the database in CICS regions if needed, and then close the database in the MUF using COMM CLOSE. At the next request to the database, the file will be opened, and it will retrieve the attributes from the system catalog – including the updated volume candidate list. Then, if the database needs to be extended by a manual or dynamic extend process, the new volumes will be used as defined.

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