Hi

It seems that the supplied workload manager configuration is back level.

I activated CICSPlex SM on a ZD&T system, and the CMAS address space complained:

EYUCL0023W CMAS02 The MVS image is running in workload management goal mode but the CMAS is not defined to the service class, SYSSTC.

I went into the WLM ISPF panels to try to change the classification rules.

When saving I get these mesages:

IWMAM913I 0 errors and 3 warnings were found when validating the service definition. All errors must be corrected before the service definition may be installed.  

IWMAM911W The CICS/IMS service class SRVMDM is referenced by a rule in subsystem STC.

IWMAM911W The CICS/IMS service class SRVHIM is referenced by a rule in subsystem STC.  

IWMAM912W The CICS/IMS service class SRVHIM is used as the default for subsystem OMVS.

The manual states the following:

Note: As soon as you increase your service definition level to LEVEL011 or above, your service definition will be subject to a more rigorous verification. The following errors will now be flagged if you attempt to either save or install your service definition:

Classifying both CICS/IMS transactions and any other (non-CICS/IMS) work into the same service class. The application will return either message IWMAM911E (if you create a rule for a non-CICS/IMS subsystem type which references a CICS/IMS service class), or IWMAM912E (if you specify a CICS/IMS service class as the default service class for a non-CICS/IMS subsystem).

In a multiperiod service class, going from one period to the next with an increase in the importance level. For example, a period 1 goal with an importance level of 4 and a period 2 goal with an importance level of 3 would be flagged. (The application returns message IWMAM910E to identify the out-of-order importance.) The importance level must always either decrease or remain the same.

The application will allow you to save the service definition, but will prevent you from installing it until the errors are corrected.

Could we please ask the ADCD team to fix this in future versions?

Br Michael Erichsen,

Xact Consulting

I would need to bring up my Sysplex as I built it from scratch to check but wouldn't it be possible to fix this by creating a new WLM policy. I see that the one provided by IBM is at level 6 (OS/390 2.6) and the current level is 35 (z/OS 2.3) so presumably by building a new one under the WLM application and then installing it would put it at the correct level with all new functionality.

Sebastian

Hi

Thank you, Sebastian. I have fixed it on my own system, but I thought that the turnkey system should be updated.

My solution:

Start the WLM panels and extract the running system. Save it in a PDS.

Copy service classes SRV* as CICS*

Update rule STC by adding CMAS02 (my name) as SYSSTC

Alter rules CICS and IMS by changing the default to CICSLOM and others to CICSMDM.

Save, install, and activate

Br Michael Erichsen,

Xact Consulting

Hello,

I'll be correcting the WLM validation errors in the ADCD package as distributed by zD&T and have informed the team in Dallas about these warnings as well.

It is important to note that the WLM Functionality level might "appear" to be backlevel, however, the functionality level is only reflective of what features are currently being used in the WLM configuration.  If new features are not used then the functionality level remains unchanged (at a lower level than what is supported). As new features are used and activated, then WLM will update the Functionality level appropriately and dynamically.