Using External Security for CA Datacom › Security Interfaces, CA-ACF2 (z/OS and z/VSE) › Securing the MUF (DTSYSTEM)

Securing the MUF (DTSYSTEM)

At the startup of the MUF, when the LEVEL PASS and FAIL resource names are properly set up, the external security product is called with a series of resource names in the DTSYSTEM resource class.

These resource names have a high-level node of the cxxname followed by a low-level node or nodes representing a product or feature, for example, cxxname.DQ for CA Dataquery. If any level is selected at the startup of the MUF, cxxname.DD and cxxname.DQ are also checked. If access is denied for cxxname.DD, CA Datacom Datadictionary is externally secured. If access is denied for cxxname.DQ, CA Dataquery is externally secured. For more information about DTSYSTEM resources, see Using the DTSYSTEM. The following is an example of a rule to secure CA Datacom products and features:

SET RESOURCE(DTS)
COMPILE
$KEY(cxxname) TYPE(DTS)
$USERDATA(Rule to secure CA Dataquery and Datadictionary with CA ACF2 allow XCF)
DD-  UID(logonid)  PREVENT
DQ-  UID(logonid)  PREVENT
XCF-  UID(logonid)  ALLOW
STORE

This rule secures CA Datacom Datadictionary and CA Dataquery with CA ACF2 external security and allows access to the XCF facility (no external security). For a complete list of resource features and products and their corresponding resource names, see Setting Up Resource Classes.

Note: The UID string should represent the user logon ID that starts the MUF. The cxxname is the system identifier of the CA Datacom/DB Directory (CXX) name unique to each MUF.