With the CA Datacom version 14.0 SIMPLIFY feature, how do I use the DSN_XXX setting in DBSIDPR?

Document ID : KB000018826
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

I am implementing CA Datacom version 14.0, and want to use the SIMPLIFY feature. What is the DSN_XXX setting, and how do I enter the value for it?

Solution:

CA Datacom version 14.0 provides improved data integrity through the use of the SIMPLIFY feature. One of the requirements when using the DBSIDPR parameter SIMPLIFY_MODE=YES is that your CXX, LXX and FXX must conform to certain naming conventions as specified in your DBSIDPR module as it is assembled in the AXCUS01 (for CA Datacom/AD) or BDCUSNEW/BDCUSUPG (for CA Datacom/DB).

For example, the default filename for the CXX is CAI.NEWHLQ.CXX^NAME.CXX, and this matches with the following entries in the DBSIDPR assembly in the customization job:


   CXXNAME=CXX^NAME, NAME OF THE CXX 	  
   DSN_XXX=CAI.NEWHLQ.CXX^NAME.???, 

According to the instructions, you will first change the CXX^NAME value to a unique name in your environment. If the high-level qualifier of your version 14.0 files is SYS3.DB1400, and the CXX^NAME is MYMUF01, this will result in the DBSIDPR containing:


   CXXNAME=MYMUF01, NAME OF THE CXX     
   DSN_XXX=SYS3.DB1400.MYMUF01.???,      

According to the CA Datacom/DB Database and System Administration Guide for version 14.0, in the section, "Using the Multi-User Facility › Modifying DBSIDPR Parameters › DSN_XXX="

(Optional) (z/OS only.) This keyword exists to provide the model data set name to be used for dynamic allocation of the CA Datacom system areas CXX, LXX, and FXX. It is required to be specified when using the SIMPLIFY option. It is optional when not using the Simplify option. A significant part of the Simplify option protection is to protect the system areas from corruption. This protection needs the name of the data sets to protect. The parameter-provided model must include 3 question marks. The question marks are replaced by CXX, LXX, or FXX to use to dynamically allocate the data sets when needed (and the DD statement for the area is not provided), and also to ensure that the DD statement was provided that it specifies the correct data set name. These data sets should not have provided-DD statements present and should allow dynamic allocation only when needed as part of the protection.

Since the value of the DSN_XXX parameter is to be treated as a mask for the filename, you must keep "???" in the position you desire, and the MUF will automatically substitute "CXX," "LXX" or "FXX" as appropriate when allocating the files. As a result, when you are ready to create the files, these are the names that the MUF will expect, based on the DSN_XXX value above:


   SYS3.DB1400.MYMUF01.CXX
   SYS3.DB1400.MYMUF01.FXX 	  
   SYS3.DB1400.MYMUF01.LXX

Other than the job that defines and initializes these files, the CXX, FXX and LXX DD statements should not be defined in any utility or application job, and they should not be defined to the MUF job or started task. All subsequent references to this file will be handled through dynamic allocation within the MUF.

  • For further information about the DBSIDPR values, please refer to the CA Datacom/DB Database and System Administration Guide for version 14.0, in the section, "Using the Multi-User Facility › Modifying DBSIDPR Parameters."
  • For further information about using the SIMPLIFY feature, please refer to CA Datacom/DB Database and System Administration Guide for version 14.0, in the section, "Introduction › Simplify Feature."

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