Sample JCL to allocate a WLM couple data set

To allocate a WLM couple data set, use the sample JCL and fill in the following information:

   //FMTCDS   JOB MSGLEVEL=(1,1)
   //STEP1    EXEC PGM=IXCL1DSU
   //STEPLIB  DD   DSN=SYS1.MIGLIB,DISP=SHR
   //SYSPRINT DD   SYSOUT=A
   //SYSIN    DD   *
      DEFINEDS SYSPLEX(PLEX1)
               DSN(SYS1.WLMCDS01) VOLSER(TEMPAK)
               MAXSYSTEM(32)
               CATALOG
           DATA TYPE(WLM)
                ITEM NAME(POLICY) NUMBER(10)
                ITEM NAME(WORKLOAD) NUMBER(35)
                ITEM NAME(SRVCLASS) NUMBER(30)
                ITEM NAME(SVDEFEXT) NUMBER(5)
                ITEM NAME(SVDCREXT) NUMBER(5)
                ITEM NAME(APPLENV) NUMBER(50)
                ITEM NAME(SVAEAEXT) NUMBER(5)
                ITEM NAME(SCHENV) NUMBER(50)
                ITEM NAME(SVSEAEXT) NUMBER(5)

Where:

SYSPLEX(sysplex): The name of your sysplex as it appears in your COUPLExx parmlib member.
DSN: The name you are calling your WLM couple data set
VOLSER: A volume that you have access to. If you are using DFSMS, you do not need to specify a VOLSER.
TYPE: The type of function for which this data set is allocated. For a service definition, the type is WLM.
ITEM NAME(POLICY) NUMBER(nn): Specifies that an increment of space large enough to accommodate the specified number of policies be allocated in the WLM couple data set (Default=5, Minimum=1, Maximum=99).
ITEM NAME(WORKLOAD) NUMBER(nnn): Specifies that an increment of space large enough to accommodate the specified number of workloads be allocated in the WLM couple data set (Default=32, Minimum=1, Maximum=999).
ITEM NAME(SRVCLASS) NUMBER(nnn): Specifies that an increment of space large enough to accommodate the specified number of service classes be allocated in the WLM couple data set (Default=128, Minimum=1, Maximum=999).
Note: WLM allows no more than 100 service classes to be defined in a service definition. The default, however, is 128. This will set aside as much space as you will ever need for service classes, as well as a little extra for other WLM objects.
ITEM NAME(SVDEFEXT) NUMBER(nnnn): Specifies that an exact amount of space (in K bytes) for extension areas to the WLM Service Definition (IWMSVDEF) be allocated in the WLM couple data set (Default=0, Minimum=0, Maximum=8092).
ITEM NAME(SVDCREXT) NUMBER(nnnn): Specifies that an exact amount of space (in K bytes) for extension areas to the WLM Service Definition Classification Rules (IWMSVDCR) be allocated in the WLM couple data set (Default=0, Minimum=0, Maximum=8092).
ITEM NAME(APPLENV) NUMBER(nnnn): Specifies that an increment of space large enough to accommodate the specified number of application environments be allocated in the WLM couple data set (Default=100, Minimum=1, Maximum=3000).
ITEM NAME(SVAEAEXT) NUMBER(nnnn): Specifies that an exact amount of space (in K bytes) for extension areas to the WLM Service Definition Application Environment Area (IWMSVAEA) be allocated in the WLM couple data set (Default=0, Minimum=0, Maximum=8092).
ITEM NAME(SCHENV) NUMBER(nnn): Specifies that an increment of space large enough to accommodate the specified number of scheduling environments be allocated in the WLM couple data set (Default=100, Minimum=1, Maximum=999).
ITEM NAME(SVSEAEXT) NUMBER(nnnn): Specifies that an exact amount of space (in K bytes) for extension areas to the WLM Service Definition Scheduling Environment Area (IWMSVSEA) be allocated in the WLM couple data set (Default=0, Minimum=0, Maximum=8092).

If you encounter a problem during processing, make sure you take a dump by adding the following to your JCL and re-submit.

   //SYSABEND DD SYSOUT=*

Note: The intended users of SVDEFEXT, SVDCREXT, SVAEAEXT, and SVSEAEXT are system management product vendors who wish to include some of their own unique information about customer workload definitions along with the WLM definitions. The WLM interfaces allow these extensions to accompany the service class definitions, report class definitions, or even classification rules. The amount of extra information is specific to each product that exploits these interfaces. That product's documentation should tell the customer how to set SVDEFEXT, SVDCREXT, SVAEAEXT, and SVSEAEXT to ensure that there is sufficient space available in the WLM couple data set to hold the extra information. For more information, see the “Adding Program-Specific Extensions to a Service Definition” topic in the “Using the Administrative Application Services” Chapter in z/OS MVS Programming: Workload Management Services.