Return codes for the IWMINSTL sample job

This information describes the return codes issued by the IWMINSTL sample job. The Install Definition Utility is shipped as member IWMINSTL in SYS1.SAMPLIB. You can use the IWMINSTL job to install a WLM service definition or to activate a WLM policy without having to use the ISPF WLM application.

Table 1 describes the return codes that are issued by IWMINSTL. An accompanying message text is written to the job output listing.

Table 1. Return codes from IWMINSTL
Return code Message text and explanation
0 
Successful execution.
104 
The service definition was not processed due
to a mismatch between the WLM address space
level (current.wlm.level) and the level of this
utility (IWMARIDU.level).
Use the correct level of the IWMARIDU utility.
204 
GetServiceDefinition
Unable to use (your.definition.dataset) for service
definition data. A table has an unrecognized format.
208 
GetServiceDefinition
Unable to use (your.definition.dataset),
data set is in use.
212 
GetServiceDefinition
The service definition was not read due to a
mismatch between the service definition PDS
and the WLM Install Definition Utility.

The service definition PDS has a higher functionality level than the current version of the WLM Install Definition Utility. Once a service definition was updated by a WLM instance with a higher functionality level it can no longer be updated by a WLM instance with lower functionality level.
216 
GetServiceDefinition
The service definition was not opened due to an ISPF dialog
error.
304 
InstallServiceDefinition
Install failed, service definition has no name.
No service definition name was specified. To fix the error, do the following:
  • Specify a valid service definition name for IWMINSTL parameter SVDEFPDS.
  • Verify in the IWMINSTL JCL, whether the SVDEF DD statement exists.
308 
InstallServiceDefinition
Install failed, no workloads are defined.
312 
InstallServiceDefinition
Install failed, no service classes are defined.
316 
InstallServiceDefinition
Install failed, no service policies are defined.
320 
InstallServiceDefinition
Install failed, access was denied to the WLM couple data set.
The UserID does not have proper access to MVSADMIN.WLM.POLICY
in the FACILITY class. See
for more information.
324 
InstallServiceDefinition
InstallServiceDefinition Install failed, service definition
was modified
Every WLM service definition contains a service definition ID. An attempt was made to install a service definition with a different ID than the service definition ID that is installed. A WLM service definition ID consists of the following:
  • The name of the service definition
  • A timestamp when the service definition was installed
  • A user ID that installed the service definition
  • The system name from which the installation was done
Use the FORCE=Y parameter for the WLM install definition utility to install a service definition with a different ID. The default is FORCE=N.
336 
InstallServiceDefinition
Install failed, failure in WLM bridge layer.
Additional messages regarding this error might
be written to the job output listing.
404 
ActivateServicePolicy
The service policy was not activated due to an ISPF dialog
error.
408 
ActivateServicePolicy
Activate failed, activation in progress on another system.
412 
ActivateServicePolicy Activate failed, one or more
systems were unable to activate the policy.
416 
ActivateServicePolicy
Activate failed, (POLNAME) was not found on the
WLM couple data set.
420 
ActivateServicePolicy
Activate failed, failure in WLM bridge layer.
Additional messages regarding this error might
be written to the job output listing.
516 
SaveServiceDefinition
The service definition was not opened due to an ISPF dialog
error.