If an XML Service call fails for any reason the calling routine will generally receive both a return code and a reason code to indicate the cause of the failure. The common ones are documented in the ChangeMan ZMF XML Services User’s Guide, the 8.3 version of which can be found here.

However, sometimes an unexpected reason code may be returned. For example, a PARMS.APL.LIST service call may receive return code 4 with a <statusReasonCode/> value of 6504. Or the same call could also receive a return code 8 with a 6105 <statusReasonCode/>. In this type of situation it is worth checking the ChangeMan ZMF Messages Guide to see if a matching CMNnnnnl or SERnnnnl (where nnnn = reason code and l = severity level (I -Information, E – Error, etc.)) message can be found. Although the full message will often be returned in the <statusMessage/> field, it can sometimes be overwritten or custom-written routines may not always display this field. Hence the frequent confusion around these types of reason code.

Whilst this will not always explain the cause of the problem, it often will. If it does not, or if further assistance is required in understanding the underlying cause of the problem even when the full error message is displayed, customers with an active support contract can, of course, open a case with the Support team who will be happy to help.