Control‑M/Analyzer can be installed without setting up special security requirements, except as noted below for RACF, ACF2 and TOP SECRET. After Control‑M/Analyzer is installed, it is possible to set up basic security parameters to allow a basic testing environment during the first stages of product testing.

• For RACF users:

  If you are using RACF and intend to run the Control‑M/Analyzer New Day procedure (CTBNDAY) as a started task (not a job), you must define the CTBNDAY started task as a valid started task under RACF.

  Perform an IPL, (CLPA or MLPA, depending on the way RACF is implemented at your site. Verify that any job containing the Control‑M/Analyzer Runtime environment belongs to a RACF Group, or user ID, that is authorized to read CDAM data set prefixes.

• For CA‑ACF2 users:

  Verify that any job that contains the Control‑M/Analyzer Runtime environment is associated with a UID that is authorized to read CDAM data set prefixes.

• For CA‑TOP SECRET users:

  If you are using TOP SECRET and intend to run the Control‑M/Analyzer New Day procedure (CTBNDAY) as a started task (not a job), then you must define the CTBNDAY started task as a valid started task under TOP SECRET.

  Verify that any job containing the Control‑M/Analyzer Runtime environment is associated with an ACID that is authorized to read CDAM data set prefixes.