Procedure

Copy the sample JCL from the HVEENV member to your local proclib.

In your copy of the JCL from the HVEENV member, modify the variables listed in Table 1 to configure the execution environment for the guest platform management provider. If a dash is shown in the “Suggested value” column, you can use any value.

Table 1. z/OS execution environment variables for the guest platform management provider
Variable Name	Description	Suggested value
DATA-ROOT	Directory on UNIX where the guest platform management provider stores the configuration and diagnostics data.	–
ENV_PROFILE	The UNIX profile for the guest platform management provider to use. This profile contains environmental information, such as TimeZone and Locale.	–
EXTRA_LIBPATH	Optional directory of environment library path.	–
JREBIN_ROOT	Directory on UNIX where the 32-bit Java™ executable is located. Use the latest service level of IBM® Runtime Environment for Java 2 (JRE) 1.6 or 1.7.	–
LOGFILE_ROOT	Directory where the guest platform management provider startup-related diagnostics messages are stored.	–
MCA_GROUP	The group created in STEP01 of this JCL.	Use HVEMCA as the group name.
MCA_USER	The user created in STEP01 of this JCL.	Use HVEMCA1 as the user name.

In your copy of the JCL from the HVEENV member, add or modify JCL statement parameters to configure the security environment for the guest platform management provider. The HVEENV member in SYS1.SAMPLIB contains sample z/OS® Security Server RACF® commands that you or your installation's security administrator can modify to control access to specific system resources.

(Required) Add a group profile and user profile for the HVEMCA started task.

ADDGROUP HVEMCA SUPGROUP(SYS1) OWNER(SYS1) OMVS(GID(88888))
ADDUSER  HVEMCA1 DFLTGRP(HVEMCA) NOPASSWORD -
         OMVS(UID(0) PROGRAM(/bin/sh) -
         HOME(/usr/lpp/bcp/mca))
RDEFINE STARTED HVEMCA.** -
         STDATA(USER(HVEMCA1) GROUP(HVEMCA))
SETROPTS RACLIST(STARTED) REFRESH

(Required) Authorize the HVEMCA started task to use the INMN.

SETROPTS CLASSACT(SERVAUTH) RACLIST(SERVAUTH) GENERIC(SERVAUTH)
RDEFINE SERVAUTH EZB.OSM.sysname.tcpname
PERMIT  EZB.OSM.sysname.tcpname CLASS(SERVAUTH) ID(HVEMCA1) ACCESS(READ)
SETROPTS RACLIST(SERVAUTH) REFRESH

If you are using security labels (SECLABELs) in your environment, assign the user of the HVEMCA started task to the security label of SYSMULTI.

PERMIT SYSMULTI CLASS(SECLABEL) ID(HVEMCA1) ACCESS(ALTER)
ALTUSER HVEMCA1 SECLABEL(SYSMULTI)
RDEFINE STARTED HVEMCA.** -
        STDATA(USER(HVEMCA1) GROUP(HVEMCA))
        SECLABEL(SYSMULTI)
SETROPTS RACLIST(STARTED) REFRESH
SETROPTS RACLIST(SECLABEL) REFRESH

Run your copy of the modified JCL from an authorized user with UID=0. The z/OS system issues a message indicating that the job was submitted, and issues another message when the job ends. Check the job log for message FEW2119I, which indicates successful processing of the environment variables.
The job log also contains messages to indicate whether the security commands were successfully processed. For any error messages in the job log, use z/OS MVS™ System Messages to find message descriptions and suggested responses, correct the errors, and rerun the job.
From the MVS™ console, issue the DISPLAY WLM command to determine the status of the Application Response Measurement (ARM) services.
```
D WLM,AM,ALL
```
The system responds with message IWM075I. If message IWM075I indicates that ARM services are enabled, proceed to step 6. If message IWM075I indicates that ARM services are disabled, complete the following steps:
1. Check message IWM075I for started application instances. To collect ARM data for these applications, you must restart them in step 8 after you have successfully configured and started the guest platform management provider.
  ARM-instrumented applications must be authorized to use ARM services.
2. Issue the MODIFY WLM,AM command to enable ARM services.
```
F WLM,AM=ENABLE
```
  The system responds with message IWM072I.
Edit the z/OS WLM service definition to enable WLM to automatically activate and manage a guest platform management provider on all systems in the sysplex. Using the WLM ISPF application to modify the service definition is the recommended method of managing guest platform management providers. If you do not use this method, you can manually start guest platform management providers by using the MODIFY WLM,GPMP command.
1. On the Choose Service Definition pop-up, select option 1 or 2 to edit an existing service definition.
2. On the Definition Menu, select option 11 to edit the guest platform management provider settings.
3. On the GPMP-Settings panel, enter 2 to enable WLM to automatically manage guest platform management providers. On this panel, you also can enter the names of the systems on which you do not want WLM to start a guest platform management provider.
4. Return to the Definition Menu.
5. Select File > Save or File > Save As to save your changes to this service definition.
6. Select Utilities > Install definitionto make your changes available for policy activation.
7. Select Utilities > Activate service policy to activate the policy.
The system responds with messages IWM001I and IWM070I to indicate that the policy has been activated. When the system issues message FEW0600I to indicate successful connection to the INMN, the guest platform management provider is ready to collect and report performance data to the Unified Resource Manager.
If you enabled ARM services in step 5 and any ARM-instrumented applications were active when you issued that MODIFY command, you must restart these applications so ARM calls can be processed.