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.

Use symbolic variables in DBSIDPR DSN_XXX setting

book

Article ID: 33633

calendar_today

Updated On:

Products

Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware

Issue/Introduction

Question: 

Can the DSN_XXX entry in the DBSIDPR customization use a symbolic variable?

For example, we have LPAR-specific files defined for the CXX:

SYSA.DATACOM.CXX
SYSB.DATACOM.CXX

We would like to use only one DBSIDPR, and code the DSN_XXX entry like this:

DSN_XXX=&LPAR..DATACOM.???

Can we do this so that we only have one CUSLIB and one DBSIDPR module?

Answer: 

The DBSIDPR macro does not support the use of symbolic variables in these values, as the value is used during the operation of the Multi-User Facility (called MUF) to create the file names, and it is not available to be modified from the JCL or other commands.

Also, you cannot share the CUSLIB file - in fact, you really cannot share any file with CUS* as the final qualifier in the name, as the information in this loadlib is customized for each MUF. Therefore, you need a separate CUSLIB for each MUF, and each MUF needs to have a unique name.

Additional Information:

For more information about the DBSIDPR module and the MUF Customization settings, please refer to the CA Datacom/DB Database and System Administration Guide, in the section “Using the Multi-User FacilityModifying DBSIDPR Parameters.”

As always, please contact CA Technologies support for CA Datacom if you have further questions.

 

 

 

Environment

Release:
Component: DB