Renaming and moving CA Datacom/AD MUF files to a single pack

Products

• Datacom
• Datacom/DB
• Datacom/AD

Issue/Introduction

After a CA Datacom/AD MUF has been configured and been running to support a CA product, it is sometimes necessary to rename the files, or to move them to a different volume. Because information about the database files is maintained within an internal database catalog called the CXX, it is not as simple as renaming the files. Two different methods for handling this request are listed below.

Environment

Release : 14.0

Component : CA Datacom/AD

Resolution

Here is the first process:

This process would close all the databases in the MUF, rename the database files, move the files to the new pack, and then rename the files in the database catalog (CXX). You would then need to shut down the MUF, rename the rest of the operational and control files, add the new file names into APFlist, reload the PC modules, and then you could restart the MUF. Here are the detailed steps:

1. Shut down the CA 11 STC;

2. Run a DBUTLTY job to turn off access and close all databases in the MUF (not just CA 11)

   This will not be able to close the VIRTUAL databases that also have files defined in the CXX. That will come later.

3. Run DBUTLY CXXMAINT job to rename all the database files (except the VIRTUAL ones) in the CXX (database catalog).

4. Shut down the MUF STC normally (using EOJ)

5. Run IDCAMS job to rename the database, operational and control files to the correct names, and then move the files to the new pack, or

    Run DFDSS job to move and rename the files in one process.

6. Run DBSIDPR assembly, changing the value of the DSN_XXX setting to reflect the new file name mask.

7. Update CUSMAC(AXDATIN1) member, and change this option to a comment:

CBS 6,1024K,0,0,16,1006

8. Start the MUF again.

9. Run DBUTLTY CXXMAINT job to rename DB006 and DB1006 files as needed.

10. Shut down the MUF normally

11. Update CUSMAC(AXDATIN1) member, and remove the comment:

*CBS 6,1024K,0,0,16,1006

12. Restart the MUF

13. Restart the CA 11 STC

At this point, all files should now have the new names, and the CXX should be updated appropriately. As you can see, the process is not simple, and requires the MUF to be shutdown and restarted two different times in the process. This is why option #2 below would be easier, as you can create the second MUF and run all the basic jobs while the current MUF is still running, and then only take the system down for a short time to take a backup and recreate the CA 11 files as needed.

The second process would be simpler, I believe. In addition, this would allow you to upgrade to version 15.0 at the same time if you wish. 

In this process, you would run all the customization jobs as if it were a new installation (which it is, in reality) - AXCUS01, AXAPFADD, AXRIM01 and AXNEW01. You would define the files with the desired names and volume in these jobs, and when complete, you should be able to run the AD14STRT job to start the new MUF. Then, you can run the AXIVP01 job to give it a quick checkout and be sure it performs the basic functions.

Once that is done, the process is a little different from the normal migration. Here, you will run the AL7AD1 and AL7AD2 jobs from the CA 11 SAMPJCL to define and allocate the CA 11 database files on the new pack. Then you need to decide:

• If you use the CA 11 data for reporting (check with your CA 11 administrator), you will want to keep the data. In this case, you would take a backup of the CA 11 database from the "old" MUF followed by the AL7LD1 job to reload the data into the "new" MUF.
• If you do not need the CA 11 data, then you do not need to do anything else - the database is initialized and ready for use.

You will then need to update the STEPLIB in the CA 11 proc to the "new" loadlibs, and it should be ready to start.

Note that if you want to upgrade to version 15.0 during this process, you would run the customization jobs for 15.0 just as you would for 14.0 - the 15.0 jobs are AXCUSNEW, AXAPFADD, AXRIM01 and AXNEW01. The MUF job would be AD15STRT, and the IVP job is AXIVP01. We would recommend that you upgrade to 15.0 or 15.1 to take advantage of improved processing and new features.

Additional Information

Using one of these methods should allow you to rename and move all of the files associated with a MUF. 

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