ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Required steps for the SYSVIEW for DB2 if a Db2 subsystem is moved

book

Article ID: 212707

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Are there any required procedures for the SYSVIEW for DB2 if the existing Db2 subsystem in a LPAR is moved to another LPAR?

Though one existing LPAR will be removed, the Db2 subsystem in the LPAR will be moved to another existing LPAR before the LPAR will be removed. In the existing another LPAR that the Db2 subsystem will be moved, two Db2 subsystems have been already exist and those two Db2 subsystems have been already monitored by the SYSVIEW for DB2. Since the entire Db2 subsystem will be moved to the other existing LPAR as it is, the Db2 catalog and Db2 datasets and so on can be used in the other existing LPAR as it is. 

 

Environment

Release : 20.0

Component : CA SYSVIEW Performance Management Option for DB2 for z/OS

Resolution

Since the entire Db2 subsystem will be moved to the other existing LPAR as it is, the Db2 catalog and Db2 datasets and so on can be used in the other existing LPAR as it is. In this case, it means the Db2 subsystem is started with the same Db2 Catalog. On this way, any Db2 Objects for the PTDB database do not need to be updated so it is not necessary to run the Post-Install Tasks. 

For the the SYSVIEW for DB2 started task, please check if the SYSVIEW for DB2 works with the VTAM UI or with RAF=YES parameter in the SYSVIEW for DB2 started task.
If the SYSVIEW for DB2 works with these features then all the VTAM definitions must be moved from the LPAR that will be removed to targeted existing LPAR otherwise the SYSVIEW for DB2 started task will fail.