Configuring the z/OS RMF Distributed Data Server to collect RMF Monitor III reports

If you configure RMF III Report data streams for gathering RMF Monitor III reports, you must also configure the RMF Distributed Data Server (DDS). The Log Forwarder sends HTTP requests to the RMF DDS and retrieves the report data from the HTTP responses. The gatherer interval is the same as the interval that RMF DDS gathers data from RMF.

Depending on whether or not the Log Forwarder user has a password, use one of the following methods to prepare the RMF Distributed Data server.

• If the user ID that is associated with the Log Forwarder has a password, complete the following actions:
  1. Run the follow command to grant the user ID access to generate PassTicket when accessing the RMF DDS.

     PERMIT IRRPTAUTH.GPMSERVE.* CLASS(PTKTDATA) ID(user)ACCESS(UPDATE)  
     SETROPTS RACLIST(PTKTDATA) REFRESH 

     where user is the user ID of the Log Forwarder started task procedure.

     For more information about configuring PassTicket support for the Distributed Data Server, see Configuring PassTicket support for the Distributed Data Server in the RMF documentation.

• If the user ID that is associated with the Log Forwarder is a protected user that does not have a password, complete the following actions:
  1. Specify the host name or TCP/IP address of the Log Forwarder in the RMF Distributed Data Servers HTTP_NOAUTH option to use the HTTP interface without authentication.
  2. Optional: If you need secured communication, you can set up Application Transparent-Transport Layer Security (AT-TLS) so that the Log Forwarder is authenticated through a client certificate. For more information about how to set up AT-TLS, see the technote for OMEGAMON® z/OS® agent http://www-01.ibm.com/support/docview.wss?uid=swg21697224&aid=1. Though this technote is for OMEGAMON z/OS agent, replace the OMEGAMON z/OS agent information with the Log Forwarder information when you read through this technote.
• If AT-TLS is set up to enable secure communication with RMF DDS, all RMF DDS clients including the Log Forwarder must use secure communication with RMF DDS. An AT-TLS TTLS rule is required to convert the outbound connection from the Log Forwarder to RMF DDS to secure communication. For more information, see the previously mentioned technote for OMEGAMON z/OS agent.