Initialization Best Practices › Protect CA Datacom/DB Critical System and User Data Sets from Non-Datacom Access › Systems Databases

Systems Databases

Each system database is commonly referred to by its functional purpose and by its assigned database ID (DBID). There is one or more index areas and one or more data areas for each database. Each of these areas has one associated z/OS data set. To refer to the data sets making up the database, we typically use the z/OS DDNAME. The actual data set name is dependent on the options chosen during installation.

Critical system databases should be protected and have specific access rights, such as the following examples:

CA Datacom Datadictionary

• Database 0002
  • Index data set, IXX002
  • Data area data set, DD1002

  Contains the metadata definitions of all databases accessible in this CA Datacom environment.

  • Required to populate information into the CXX and the DDD database (see Database 0015)
  • Should be externally secured
    • Must be fully accessible to the user ID used to submit the MUF startup
    • Must be fully accessible to user IDs used to execute DBUTLTY functions against this database

Data Definition Directory - DDD

• Database 0015
  • Index data set, IXX015
  • Data area data set, DDD015, MSG015, and SIT015

  Contains the SQL metadata definitions of all databases that are SQL accessible in this CA Datacom environment.

  • Should be externally secured
    • Must be fully accessible to the user ID used to submit the MUF startup
    • Must be fully accessible to user IDs used to execute DBUTLTY functions against this database