Resources › DBD Resource Class—Secure IMS Database Name

DBD Resource Class—Secure IMS Database Name

Valid on z/OS.

Use DBD to secure an IMS database descriptor name.

When used with TSS ADDTO/REMOVE, this resource class has the following format:

TSS ADDTO(acid) DBD(prefix(es))

Prefix length

One to eight characters

Capacity of list

One to five prefixes per TSS command

When used with TSS PERMIT/REVOKE, this resource class has the following format:

TSS PERMIT(acid) DBD(prefix(es)) ACCESS(access levels)

Prefix length

One to eight characters per prefix

Capacity of list

One to five prefixes per command

DBD is used with:

• The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOOWNS, and WHOHAS
• The DBD ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
• The DBD ACID types User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
• DBD(OWN) authority to ADD or REMOVE ownership of DBD resources from ACIDs
• DBD(XAUTH) authority to PERMIT or REVOKE access to DBD

The administrator can:

• Use following methods to control access to DBDs: Expiration, Facility, PRIVPGM, PSB Pathing, Time/Day, and Actions
• Specify the access levels: INQUIRE, SET, DELETE, REPLACE, NONE, READ, UPDATE, and WRITE. If ACCESS is not specified, CA Top Secret defaults to READ access.

Examples: DBD resource class

This example gives the Personnel Department ownership of the DBD resource for the corporate personnel database (PERSFILE):

TSS ADDTO(PERSDPT) DBD(PERSFILE)

The administrator may now PERMIT access to users or profiles that require access:

This example removes ownership:

TSS REMOVE(PERSDPT) DBD(PERSFILE)

This example permits user PERSF1 to update DBDs used by the Personnel Department:

TSS PERMIT(PERSF1) DBD(PERS44,PERS51,PERS07) ACCESS(U)

This example revokes access:

TSS REVOKE(PERSF1) DBD(PERS44,PERS51)

Now, user PERSF1 may only update PERS07.