Use symbolic variables in DBSIDPR DSN_XXX setting


Article ID: 33633


Updated On:


CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware



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

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


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


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


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.





Component: DB