Updating z/OS for the Resource Monitoring Plug-in

If you selected to configure the Resource Monitoring plug-in, you might have system customization to perform, as described in this topic.

This topic contains the following information:

System customization for the Resource Monitoring and System Status tasks

Table 1 describes the z/OS® system changes that are required or recommended. Some of this work might already be done on your system, or might not be applicable. If so, you can skip the particular setup action.

Table 1. z/OS setup actions for the Resource Monitoring and System Status tasks
	z/OS setup action	Check when task is completed
1	Enable the optional priced feature, Resource Measurement Facility (RMF), on one of the systems in your enterprise. For information about enabling features, see z/OS Planning for Installation, GA22-7504.
2	For data collection and monitoring of your systems, ensure that the RMF Distributed Data Server (DDS) is active on one of the systems in your sysplex. To monitor several sysplexes, ensure that a DDS is running on one system in each sysplex. You can use the following command to check for the existence of GPMSERVE address spaces in your sysplex: `ROUTE ALL,D A,GPMSERVE` If your installation uses RMF Cross Platform Monitoring (RMF XP), the RACF® profile name for the RMF XP DDS is GPM4CIM, rather than GPMSERVE. For information about setting up the DDS and RMF XP, see z/OS RMF User's Guide*, SC33-7990.
3	Determine whether the DDS on the target system is currently configured to require authentication. To check, use the following command to display the active DDS options: `MODIFY GPMSERVE,OPTIONS` If your installation uses RMF XP, the RACF profile name for the RMF XP DDS is GPM4CIM, rather than GPMSERVE. In the command output, check for the HTTP_NOAUTH setting, which indicates the scope of authentication for the DDS, as follows: HTTP_NOAUTH() All hosts must authenticate HTTP_NOAUTH() No authentication is required HTTP_NOAUTH(specific_host_or_mask*) All hosts except those matching the mask must authenticate. If DDS authentication is not required in your enterprise, you are done. Otherwise, proceed to Step 4.
4	Determine whether your installation security procedures require that the DDS should require authentication from the z/OSMF system and its users, and perform one of the following actions: If DDS authentication is required from the z/OSMF system, you must ensure that the PassTicket is set up properly, and that the z/OSMF started task user ID is authorized to generate the PassTicket. See Enabling PassTicket creation for Resource Monitoring task users. If DDS authentication is not required from the z/OSMF system, you can disable DDS authentication for the system on which z/OSMF is running. Doing so allows the Resource Monitoring and System Status tasks to access the DDS on behalf of z/OSMF users without potentially encountering authentication errors. To disable DDS authentication for the system on which z/OSMF is running (the server host name or IP address), modify the HTTP_NOAUTH statement in the GPMSRVxx parmlib member on the DDS system. In the following example, the HTTP_NOAUTH statement is updated to bypass DDS authentication for the host system represented by `host_system_IP_address`: `HTTP_NOAUTH(host_system_IP_address)` For more information about DDS authentication, see z/OS RMF User's Guide, SC33-7990.