IWM003I

no

Explanation
The command failed for one of the reasons described
in text.
In the message text: {VARY|DISPLAY}
The name of the command that failed.
policy-name
The name of the service policy specified on the command.
system-name
The name of the system where the service policy is being activated.
text
text is one of the following: NO INSTALLED SERVICE DEFINITION
There is no service definition installed on the WLM couple data
set.
WLM SERVICE DEFINITION LEVEL (xxxxxxxx)
MUST BE LESS THAN OR EQUAL TO WLM VERSION LEVEL (yyyyyyyy)
The service definition is at a higher level than what the system
is running.
WLM COUPLE DATA SET NOT AVAILABLE
The WLM couple data set is not available.
WLM COUPLE DATA SET TOO SMALL
The WLM couple data set is too small to hold the service policy.
POLICY NAME policy-name NOT DEFINED
The policy you have specified is not defined.
SERVICE POLICY ACTIVATION IN PROGRESS BY SYSTEM system-name
The service policy is in the process of being activated on the
named system.
SYSTEM system-name NOT DEFINED
The named system is not defined to the sysplex.

System action
The system does not process the command.

Operator response
Notify the system programmer.

System programmer response
  If NO INSTALLED SERVICE DEFINITION appears
in the message text, make sure you have installed a service definition
on the WLM couple data set.
If WLM SERVICE DEFINITION LEVEL
(xxxxxxxx) MUST BE LESS THAN OR EQUAL TO WLM VERSION
LEVEL (yyyyyyyy) appears in the message text,
and you have a mixed sysplex with another system at level xxxxxxxx
or higher, then you must issue the command on that system. If you
have a mixed sysplex and no system at level xxxxxxxx or higher,
then you must use a service definition that is at the same level or
lower than the WLM version level yyyyyyyy.
If WLM
COUPLE DATA SET NOT AVAILABLE appears in the message text, make
sure you have defined a WLM couple data set and installed a service
definition containing at least one policy.
If WLM COUPLE
DATA SET NOT AVAILABLE appears in the message text, and you have
defined a WLM couple data set, check whether you have connectivity
to the data set with the command DISPLAY XCF,COUPLE,TYPE=WLM. If you
do have connectivity, issue the command again. If the problem persists,
search problem reporting data bases for a fix for the problem.  If
no fix exists, contact the IBM® support
center.
If WLM COUPLE DATA SET TOO SMALL appears in the
message text, first, allocate a new WLM couple data set that is large
enough to hold the service policy.  Next, make it the new alternate
WLM couple data set using the SETXCF COUPLE,TYPE=WLM,ACOUPLE= command.
Third, switch from the primary to the secondary couple data set by
using the SETXCF COUPLE,TYPE=WLM,PSWITCH command. Issue the VARY command
again.  Repeat this process until the WLM couple data set is large
enough.  If the maximum size has been allocated, and the problem persists,
search problem reporting data bases for a fix for the problem.  If
no fix exists, contact the IBM support
center.
If POLICY NAME policy name NOT DEFINED appears
in the message text, check whether you have spelled the policy name
correctly.  If you did, then notify the system programmer and provide
the policy name. If you did not spell it correctly, then correct the
name and issue the command again.
If SYSTEM system-name NOT
DEFINED appears in the message text, check whether you have spelled
the system name correctly. To find out the names of all the defined
systems, issue the command DISPLAY WLM,SYSTEMS. If you did not spell
it correctly, then correct the name and issue the command again.
If SERVICE
POLICY ACTIVATION IN PROGRESS BY SYSTEM system-name appears
in the message text, wait until the activation in progress is complete
before reissuing the command.  If the message persists, search problem
reporting data bases for a fix for the problem. If no fix exists,
contact the IBM support center.

Source
Workload manager (WLM)

Module
IWMO2CMD

Routing code
2,10

Descriptor code
5