For availability purposes, you should allocate both a primary and an alternate WLM couple data set.
You can allocate a new primary and alternate WLM couple data set from the application using the Allocate couple data set using CDS values function on the Utilities menu bar option of the Definition Menu. Figure 1 shows the allocate panel that uses CDS values.
Allocate couple data set for WLM using CDS values
Command ===> ___________________________________________________________
Sysplex name SYSPLEX1 (Required)
Data set name 'GAILW.PCOUPLE.P1' (Required)
-----------------------------------------------------------------------
|
Size parameters |
(optional): | Storage parameters:
|
Service policies . . 10 (1-99) | Storage class . . . A
Workloads . . . . . 35_ (1-999) | Management class . . ________
Service classes . . 30_ (1-100) |
Application |
environments . . . . 50_ (1-3000) | or
Scheduling |
environments . . . . 50_ (1-999) |
SVDEF extensions . . 0___ (0-8092) | Volume . . . . . . . ______
SVDCR extensions . . 0___ (0-8092) | Catalog data set? _ (Y or N)
SVAEA extensions . . 0___ (0-8092) |
SVSEA extensions . . 0___ (0-8092) |
This function primes the size parameters with values from the current couple data set. This way, you can ensure that the new couple data set is at least as large as the current one. If the new one is smaller than the current one, you will not be able to use SETXCF to make this data set available to the sysplex. (You will receive a series of messages starting with IXC255I UNABLE TO USE DATA SET.) You may need to increase one or more of these primed values if you have added new objects to your service definition since the last time you installed it.
If there is no current WLM couple data set, use the Allocate couple data set function on the Utilities menu. This function fills in the size parameters based on the service definition you are about to install. It gets the values from the ISPF PDS containing the service definition. Figure 2 shows the allocate panel that uses service definition values.
Allocate couple data set for WLM
Sysplex name SYSPLEX2 (Required)
Data set name 'KIRSTEN.PCOUPLE.P1' (Required)
-------------------------------------------------------------------------
|
Size parameters |
(optional): | Storage parameters:
|
Service policies . . 10 (1-99) | Storage class . . . A
Workloads . . . . . 35_ (1-999) | Management class . . ________
Service classes . . 30_ (1-100) |
Application | or
environments . . . . 50_ (1-3000) |
Scheduling | Volume . . . . . . . ______
environments . . . . 50_ (1-999) | Catalog data set? _ (Y or N)
If you have defined your service definition, the application fills in the number of policies, workloads, service classes, application environments, and scheduling environments in that definition. These actual values are the best estimate of what this service definition requires when installed on the couple data set. If you define too large a number, it can use up a lot of space.
If you are replacing couple data sets already in use, the new data sets must be at least as large as the existing ones. You need to run a special sizing utility to determine their size. Use this method to ensure that the new couple data set is at least as large as the current one, and, in most cases, can accommodate any new objects you might have added to the service definition:
Once you have allocated the WLM couple data sets, you need to make them available for use in the sysplex. If you are making couple data sets available for the first time, see Make a WLM couple data set available to the sysplex for the first time. If you are replacing couple data sets already in use, see Make a newly formatted couple data set available to the sysplex.