CA View - Transfer a Database to Another z/OS Logical Partition (LPAR)
book
Article ID: 128833
calendar_today
Updated On:
Products
OM DeliverOM View
Issue/Introduction
The client provided their plan for transferring a View database from one LPAR to another. Note: The plan is specific to their source databases, their interim resources, and their goals.
Environment
CA View - All Releases
Resolution
The client wants to follow this plan:
1. At the original site:
- Stop any CA Deliver RMOSTC tasks that write to the database
- In the SARSTC task, issue “/f sartsc,NEW”, to run a View backup
- Define the “volser”s listed in the VTS (of the original site) to the target site - Define entries “sartape dsn/volser” in the catalog of the target site
2. At the target site:
- Define the “volser”s listed in the VTS (actions specific to the robotic VTS) - Define entries “sartape dsn/volser” (AMS/DEFINE)
3. At the target site, allocate a new VIEW database (with same name as the old one)
4. At the target site, RESTORE the index of the old view DB to the DB newly allocated, and run SARDBASE OLOAD and BLOAD to load the panels and banners, respectively:
//RESTORE EXEC PGM=SARDBASE //STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD //SYSPRINT DD SYSOUT=* //SARRECV DD DISP=SHR,DSN=view_hlq.RECV (view_hlq DB name) //SARTAPE DD DISP=SHR,… archival tape containing the backup of the master index. //SYSIN DD * NAME view_hlq RESTORE //