Moving CA View Database and Isolating to New Sysplex

Document ID : KB000126322
Last Modified Date : 06/02/2019
Show Technical Document Details
Issue:
The client wants to :

 . Move a CA View database index extents to new DASD, to isolate it in a new sysplex.
 . Create a CA-View SYSOUT database
 . Have a CA Deliver database on the new sysplex.
 
Environment:
CA View - All Releases
CA Deliver - All Releases
Resolution:
The View database index extents can be moved, from one volume to another, using FDR or DFDSS.
The general suggestion is to use the View utilities, however the ability to use a third-party product would be feasible in this instance.

To create a new View database:
 . Run SARDBASE ADDDS (DATA and INDEX) to allocate the new database. 
 . Run SARDBASE OLOAD, to load the panels. 
 . Run SARDBASE BLOAD, to load the banners. 
 . Run SARINIT, to see the list of parameters. 

To have a Deliver database on the isolated sysplex:
 . Use RMODBASE ADDDS and MAKECKPT to create the target database.
 . Note: Ensure that the BLKSIZE used to create the target database is the same BLKSIZE which was used for the source database.
 . Use RMODBASE COPY to copy the source database to the target database:

//XXXXXXXX JOB ...
//RMODBASE EXEC PGM=RMODBASE
//STEPLIB DD DISP=SHR,DSN=DLVR.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
NAME dlvr_target
COPY dlvr_source HIST_OPT
/*
//

. Where HIST_OPT (history options) can be:
. . HISTDEL to delete the detail history subfile only
. . HISTDELALL (Recommended) to delete the history subfile and all basic history records.

 . Use RMODBASE MAKECKPT EMPTY, to clear out the target Checkpoint file.