Creating a service definition for the first time

Use the following checklist to create a service definition for the first time, allocate the WLM couple data set, and then activate a service policy.

Set up performance objectives. If your installation already has performance objectives, Setting up a service definition is still helpful in setting up a service policy with realistic performance goals.
Set up a service definition from the performance objectives.
Refer to Setting up a service definition through Defining scheduling environments for further information.
Restrict access to the ISPF administrative application.
Refer to Restricting access to the WLM service definition for further information.
Start the application and enter the service definition.
Refer to Start the application and enter/edit the service definition for further information.
Upgrade the sysplex couple data set
Make sure that you have installed the z/OS release and allocated your sysplex couple data set with the IXCL1DSU utility.

For information about how to format the sysplex couple data set, refer to z/OS MVS Setting Up a Sysplex.
Allocate a WLM couple data set.
For more information, refer to Allocate a WLM couple data set.
Make the WLM couple data set available for use in the sysplex for the first time by either:
- Issuing the SETXCF command
- Updating the COUPLExx parmlib member and re-IPLing
For more information, see Make a WLM couple data set available to the sysplex for the first time.
Install a service definition on the WLM couple data set.
Before you can activate a service policy, you need to install the service definition on the WLM couple data set. To do this, use either the WLM ISPF application, or the Install Definition Utility (new with z/OS® R3).

To use the ISPF application, go into it specifying the name of the data set containing your service definition. From the Definition Menu, go to UTILITIES on the action bar, then select the pull-down option Install Service Definition.

To use the Install Definition Utility, configure the sample JCL (member IWMINSTL, shipped in SYS1.SAMPLIB) as directed in the prolog. Once the JCL has been prepared, it can be started from the command console or submitted as a batch job. A simple service definition has been provided (member IWMSSDEF, also shipped in SYS1.SAMPLIB) that is available for those customers without any other definition.
Adjust SMF recording
Before you run your systems in goal mode with z/OS V1R3, you should be aware of the changes in your SMF recording. There are several changes to SMF records for goal mode.

In particular, you should turn off SMF type 99 records. They trace the actions SRM takes while in goal mode, and are written frequently. SMF type 99 records are for detailed audit information only. Before you switch your systems into goal mode, make sure you do not write SMF type 99 records unless you want them.

If you do chargeback based on SMF record type 30 or record type 72 records, you may need to update your accounting package.

For more information about SMF record changes for goal mode, see z/OS MVS System Management Facilities (SMF).
Activate a service policy
Once you have installed a service definition, you can activate a service policy. You can activate a policy either from the administrative application, with the VARY operator command, or the WLM Install Definition Utility.

To activate a service policy from the application, choose the Utilities option from the action bar on the definition menu.
To activate a service policy with the VARY command, specify
```
VARY WLM,POLICY=xxxx
```
where xxxx is the name of a policy defined in the installed service definition.
To activate a service policy with the Install Definition Utility, start or submit the sample JCL (member IWMINSTL in SYS1.SAMPLIB).

Once you issue the command, there is an active policy for the sysplex. Systems will start managing system resources to meet the goals defined in the service policy.

For more information about the VARY command, see z/OS MVS System Commands.