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.

CA RC/Query for DB2 for z/OS: PK on a plan list (P - L report) is accessing all locations why?

book

Article ID: 200851

calendar_today

Updated On:

Products

Database Management for DB2 for z/OS - Administration Suite RC/Migrator for DB2 for z/OS RC/Query for DB2 for z/OS

Issue/Introduction

 In RC/Query doing a Plan List report ( P L), then placing PK next to a plan returns a list of packages from various locations.  The SQL seen through Detector is 

doing a 3 part name query against sysibm.syspackage: FROM location.SYSIBM.SYSPACKAGE.

If a Plan Collection report (P CL) is done, then PK next to a collection, a 3 part name query with the location is not used.

Why is there a difference in the SQL used in the reports?

Environment

Release : 20.0

Component : CA RC/Query for DB2 for z/OS

Resolution

In the RC/Query Profile, if ALL Locations is 'Y', the P PK report will use a 3 part name to access the remote location.  Set this to 'N' for remote locations to not be included.

The Plan Collection report is a different report and does not use the location. 

The Profile Variables screen can be found by typing 'PROF' from any RCQ screen, then option 2: RC/Query Profile Variables.

See the 'ALL LOCATIONS' setting and it relates specifically to the Plan Package report.

Attachments