How to rename CA Datacom database files

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

With many of the files used by CA Datacom products, it is simple enough to rename them using ISPF functions or IBM Batch utilities. This process, though, only works to rename the files in the catalog used by the operating system. CA Datacom database files have this physical file defined in the catalog, but they also have an additional directory for the Multi-User Facility (called MUF), where the filename and other statistical information is maintained.

This is a high-level overview of the process to rename the database files. Note that any applications using the database file(s) must be shutdown or suspended before starting this process. This would include any CICS- or ISPF-based applications.

1. The databases need to be closed in the MUF and access turned off;
2. The physical files need to be renamed in the OS catalog (this can be done manually or though a utility like IDCAMS);
3. The database directory (called the CXX) needs to be changed to reflect the new filenames;
4. The databases need to have the access restored.

Once this is complete, the applications that were shutdown or suspended can now be restarted or processing resumed.

Note: If you are using Simplify mode (SIMPLIFY_MODE=YES), and have used "FORCE_DSN_CXXNAME=YES" in your DBSYSID/DBSIDPR assembly, the value of the CXXname must be included in the name of the index or data file that you are renaming. If you use "NO" for either of these parameters, you can use any filename you wish. For more information about the SIMPLIFY_MODE or FORCE_DSN_CXXNAME parameters in the DBSIDPR module, please refer to the CA Datacom/DB Database and System Administration Guide, in the section "Using the Multi-User Facility > Modifying DBSIDPR Parameters."

Here is an example of the process using the CA Datacom database supporting the CA Jobtrac application. This application uses a single database - DB 161 - with one index file and 4 data files.

Step 1 - The databases need to be closed in the MUF and access turned off

This job will:

• Turn off access to the database, so nothing more can use it;
• Close the database in the MUF so we can work with it;
• Report on the database catalog, so we can see the names of the database files.

//*
//JCL JCLLIB ORDER=(CAI.NEWCHLQ.CUSPROC)
//*
//CXXRPT   EXEC PGM=DBUTLTY,REGION=6M,PARM='/PGMMONTH=1'
//         INCLUDE MEMBER=B14STLIB                          
//         INCLUDE MEMBER=B14DDOUT                          
//*                                                      
//SYSIN    DD  *                                            
  ACCESS  DBID=161,STATUS=OFF,USERS=FAIL
  COMM    DBID=161,OPTION=CLOSE                              
  REPORT  DBID=161,AREA=CXX
/*                                                     

Step 2 - The physical files need to be renamed in the OS catalog

Here is a sample IDCAMS step that will rename the files:

//RENAME   EXEC PGM=IDCAMS         
//SYSOUT   DD  SYSOUT=*             
//SYSPRINT DD  SYSOUT=*             
//SYSMDUMP DD  SYSOUT-*             
//SYSIN    DD  *                
   ALTER   DATACOM.HLQ.IXX0161  -   
   NEWNAME(SYS1.MYMUF.NEWNAME.IXX0161)  
   ALTER   DATACOM.HLQ.EVT0161  -   
   NEWNAME(SYS1.MYMUF.NEWNAME.EVT0161)  
   ALTER   DATACOM.HLQ.OPT0161  -   
   NEWNAME(SYS1.MYMUF.NEWNAME.OPT0161)  
   ALTER   DATACOM.HLQ.HIS0161  -   
   NEWNAME(SYS1.MYMUF.NEWNAME.HIS0161)  
   ALTER   DATACOM.HLQ.STG0161  -   
   NEWNAME(SYS1.MYMUF.NEWNAME.STG0161)
/*

Step 3 - The database directory (called the CXX) needs to be changed to reflect the new filenames

This job uses the DBUTLTY program to rename the files in the CXX.

//*
//JCL      JCLLIB ORDER=(CAI.NEWCHLQ.CUSPROC)
//*
//CXXMAINT EXEC PGM=DBUTLTY,REGION=6M,PARM='/PGMMONTH=1' 
//         INCLUDE MEMBER=B14STLIB                           
//         INCLUDE MEMBER=B14DDOUT                           
//*                                                      
//SYSIN    DD  *   
  CXXMAINT DBID=161,AREA=IXX,OPTION=ALTER,
           DSN=SYS1.MYMUF.NEWNAME.IXX0161
  CXXMAINT DBID=161,AREA=EVT,OPTION=ALTER,
           DSN=SYS1.MYMUF.NEWNAME.EVT0161
  CXXMAINT DBID=161,AREA=HIS,OPTION=ALTER,
           DSN=SYS1.MYMUF.NEWNAME.HIS0161
  CXXMAINT DBID=161,AREA=OPT,OPTION=ALTER,
           DSN=SYS1.MYMUF.NEWNAME.OPT0161
  CXXMAINT DBID=161,AREA=STG,OPTION=ALTER,
           DSN=SYS1.MYMUF.NEWNAME.STG0161
/*

Step 4 - The databases need to have the access restored

This job uses the DBUTLTY program to report on the database from the CXX and restore access to the database.

//*
//JCL      JCLLIB ORDER=(CAI.NEWCHLQ.CUSPROC)
//*
//CXXACCES EXEC PGM=DBUTLTY,REGION=6M,PARM='/PGMMONTH=1'
//         INCLUDE MEMBER=B14STLIB                          
//         INCLUDE MEMBER=B14DDOUT                          
//*                                                      
//SYSIN    DD  *  
* REPORT THE CXX FOR DATABASE AFTER THE CHANGE
  REPORT   DBID=161,AREA=CXX
*
* TURN ON ACCESS AGAIN TO THE DATABASE. IT OPENS AUTOMATICALLY.
  ACCESS   DBID=161,STATUS=WRITE
/*

Once the renames are complete, you can then start your applications, and the databases will open automatically.

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

Environment

Release:
Component: DB