Security Considerations › Security Considerations for CA View › CA ACF2 Security Considerations

CA ACF2 Security Considerations

If you use CA ACF2 Security as your primary security package, take the following steps to establish the authorization required by the CA DRAS task to access the CA View database.

1. Create a LOGONID for the started tasks as follows:

   INSERT dras STC NAME(dras)

2. Compile a data set rule to give the CA DRAS task access to CA View data sets as follows:

   $KEY(drashighlvl)
   caview.hlq UID(view uid) R(A) W(A) A(L) E(A)

3. As an alternative to compiling data set rules, the CA DRAS task logon ID can be given NON-CNCL privileges. This logon ID can then access any dataset or resource without having to compile rules. Using this method, CA DRAS has full access to CA View. The internal security rules defined in CA View then control password and user ID validation and SYSOUT id access authorization.
4. Create the logon ID as follows:

   INSERT dras STC NAME(dras) NON-CNCL

5. If users log on to CA View or CA DRAS, that logon ID also needs the MUSASS (Multi-User Single Address Space System) logon ID attribute as follows:

   INSERT dras STC NAME(dras) NON-CNCL MUSASS

Important! To verify the proper CA View user definition and security setup, we suggest that you first attempt to view the reports from a 3270 emulator. If you are unable to view reports through your mainframe emulation, you cannot generate a report list through cooperative processing. To correct this, review the instructions above or contact CA Support for assistance.