Skip to Content
Information
Space announcement We are no longer updating this version of the documentation for the infrastructure components (DBC, LGC, and NGL).  You can no longer leave comments on it. For the latest version of the documentation, see Common Mainframe Infrastructure 2022 release.

Authorizing the DBC started task procedure

The DBC subsystem acquires security authorization from the USERID associated with the started task procedure that starts the DBC subsystem. Users must authorize the DBC started task.

To authorize the DBC started task

  1. Associate the DBC started task with a USERID that has the appropriate security access.The DBC address space requires access to z/OS UNIX System Services (USS). Consequently, you must associate an OMVS segment with the USERID for the DBC subsystem.

    Warning

    Example

    The following example uses a RACF command to define a GROUP of DBCGRP:

    ADDUSER DBCGRP OMVS(GID(groupIdentifier))

    The following example uses a RACF command to define a USERID of DBCUSR:

    ADDUSER DBCUSR DFLTGRP(SYSMGMT) OWNER(SYSPROG)

  2. Associate the USERID with the procedure name for the DBC started task. 

    Warning

    Example

    In the following example, the RACF command uses procedure name DBCSTC:

    RDEFINE STARTED DBCSTC.* STDATA(USER(DBCUSR) GROUP(DBCGRP))

  3. To ensure that RACF recognizes these security updates, issue the following command: 

    SETROPTS RACLIST(STARTED) REFRESH

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Common mainframe infrastructure 2016 release