Use symbolic variables in DBSIDPR DSN_XXX setting
search cancel

Use symbolic variables in DBSIDPR DSN_XXX setting

book

Article ID: 33633

calendar_today

Updated On: 11-21-2024

Products

Datacom DATACOM - AD Datacom/AD Datacom/DB

Issue/Introduction

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

For example, if LPAR-specific files are defined for the CXX:

SYSA.DATACOM.CXX
SYSB.DATACOM.CXX

It would be preferable to use only one DBSIDPR, and code the DSN_XXX entry like this:

DSN_XXX=&LPAR..DATACOM.???

Can this be done so that there would be only one CUSLIB and one DBSIDPR module?

Environment

Release: All supported releases

Resolution

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