What steps should I take to Version my CA View database?
Versioning the View database.
Special Note: When VERSIONING to 12.2, consider running SARINIT with JOBMODE turned off. This will save the time needed to create job mode records.
1. Run a SARDBASE STATUS FULL
//STEP1 EXEC PGM=SARDBASE
//STEPLIB DD DISP=SHR,DSN=........VIEWxx.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
NAME ........db_hlq..........
STATUS FULL
/*
2. Remove CA-Deliver and CA-View SARXTD (if used) from the system.
Note: If application processing in CA-Deliver must continue,
change the ARCH settings to put everything to the JES
Spool so be can be picked up by CA-View SARSTC later.
3. Shut down all other CA-View tasks, DRAS, SAREAS, SARXMS, SARSTC
4. Create a final and complete Backup Cycle of the View
Database before continuing. Since the only way to create
a backup tape is with the archival task (SARSTC) we need
to start the archival task without allowing it to archive
any new reports. In order to accomplish this we can change
one of the archival selection criteria's to some unknown value.
An easy value to use is the FORM= parameter, we can use the
View SARINIT to set the archival form (FORM=) to some-
thing like FORM=Z999, so starting the archival task to run
the backup cycle will not allow new reports to be archived.
start the View SARSTC, and force a backup cycle,
"F SARSTC,NEW". This will give us a good backup if
recovery is necessary. Stop the SARSTC.
We will need to change the FORM back to its original value.
5. Unload the database using your View SARDBASE:
//STEP4 EXEC PGM=SARDBASE
//STEPLIB DD DISP=SHR,DSN=........VIEWxx.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SARUNLD DD DSN=.........UNLOAD,DISP=(,CATLG),
// UNIT=tape
//SYSIN DD *
NAME ......hlq........
UNLOAD
/*
Note: If your database is very large and an UNLD is impractical
you can run the VERSION step against the production
database. A SARDBASE/RESTORE can be run using the
most current backup tape (that is, the backup tape
created in the previous step) if you must fallback
to View The SARRSP (Restore Sysout Process) part
of a Database Restore Procedure can be run as time
permits.
6. Run the SARDBASE/VERSION function:
//STEP4 EXEC PGM=SARDBASE
//STEPLIB DD DISP=SHR,DSN=........VIEW.CVDELOAD
//SYSPRINT DD SYSOUT
//SYSOUT DD SYSOUT=*
//SORTLIB DD DSN=SYS1.SORTLIB,DISP=SHR
//SORTWK01 DD UNIT=SYSDA,
// SPACE=(CYL,(10),,CONTIG)
//SORTWK02 DD UNIT=SYSDA,
// SPACE=(CYL,(10),,CONTIG)
//SORTWK03 DD UNIT=SYSDA,
// SPACE=(CYL,(10),,CONTIG)
//SYSIN DD *
NAME .......hlq........
VERSION
/*
7. Review and modify your SARJCL1 member
8. OLOAD and BLOAD the database with SARDBASE:
//STEP5 EXEC PGM=SARDBASE
//STEPLIB DD DISP=SHR,DSN=........VIEW.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SAROLIB DD DISP=SHR,DSN=........VIEW.CVDEPENU
//SYSIN DD *
NAME .......hlq........
OLOAD
/*
//STEP6 EXEC PGM=SARDBASE //STEP6 EXEC PGM=SARDBASE
//STEPLIB DD DISP=SHR,DSN=........VIEW.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SARBLIB DD DISP=SHR,DSN=........VIEW.CVDEDATA
//SYSIN DD *
NAME .......hlq........
BLOAD
/*
9. Run SARINIT to verify your initialization parameters:
//STEP6 EXEC PGM=SARINIT
//STEPLIB DD DISP=SHR,DSN=........VIEW.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
NAME=.......hlq........
/*
10. Restart all tasks