Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
Checking a Service Definition Using IWMDINST z/OS MVS Programming: Workload Management Services SC34-2663-00 |
|||||||||
Checking a Service Definition Using IWMDINSTBefore installing a service definition on the WLM couple data set, the IWMDINST macro checks to make sure the service definition is valid. For a service definition in XML format, the macro parses the input to make sure it conforms to the DTD. Otherwise, the macro checks the service definition to verify the service definition data structure and to detect any storage overlay problems. All data in a service definition must be valid to allow for the system to complete the installation. If the IWMDINST macro finds an error during parsing or validity checking, it issues a reason code in the VALCHECK_RSN parameter. IWMDINST also returns the offset to indicate where an error was found in the IWMSVDEF mapping macro or the XML string, respectively. Note that no valid offset is returned in case the service definition type is XML and the primary reason code returned is xxxx083d. IWMDINST identifies no more than one error per call. Appendix B. Application Validation Reason Codes contains a list of the reason codes, and their explanations. Table 21 shows an example of the information provided for reason code 1B01.
In this example, IWMDINST returned a reason code of 1B01 in the VALCHECK_RSN parameter. The error is in the SVDCRSST section of IWMSVDCR, and is in a subsystem type entry. IWMDINST found a service class in the classification rules for the subsystem type that was not defined in the service definition. Your program could check the service definition for the undefined service class name, and could issue a message to the service administrator. |
Copyright IBM Corporation 1990, 2014
|