Preparing for Installation › Security Requirements

Security Requirements

Before you install CA Cross-Enterprise APM, verify that you meet these security requirements:

• You can run batch JCL streams.
• You have READ, WRITE, and ALLOCATE access to the data set prefix or high-level qualifier that is used for the installation.
• You have a user ID with an OMVS segment and UID defined for access to UNIX System Services (USS).
• If superuser rights are not assigned, you require the following permissions:
  • You have permission to mount a USS file system.
  • You have READ access to the SAF resource SUPERUSER.FILESYS.MOUNT in the UNIXPRIV class.
• You have the permission to update and create directories and files in the mount point for the installation.
• If the user ID of the WILYZOS procedure cannot be in the same group ID (GID) as you (the installer), you require CONTROL access to the SAF resource SUPERUSER.FILESYS in the UNIXPRIV class.

Before you run CA Cross-Enterprise APM, verify that the user ID that is assigned to the WILYZOS procedure (WILYZOS user ID) meets these security requirements:

• The WILYZOS user ID can run batch JCL streams.
• The WILYZOS user ID has READ access to the data set prefix or high-level qualifier that is used for the installation.
• The WILYZOS user ID has an OMVS segment and UID assigned.
• The WILYZOS user ID has READ access to the SAF resource BPX.CONSOLE in the FACILITY class. Otherwise, the agent issues WTO messages that are prefixed with message ID BPXM023I.
• If your environment requires PassTicket authentication to retrieve metric data from local DB2 subsystems, the WILYZOS user ID must be authorized to generate PassTickets.

  Note: For more information, see the documentation from your security vendor or see the IBM z/OS Security Server RACF Security Administrator's Guide.

  Also, configure the Xnet component of CA Database Management Solutions for DB2 for z/OS to accept PassTicket authentication information.

  Note: If PassTicket support is not configured, specify a valid user ID and password in the agent configuration file. This specification can potentially be a security risk.