The first step in troubleshooting is to determine in which Application Workflow Manager component the problem occurred.
The type of an Application Workflow Manager component, and where the error occurred, determine the analysis methods required.
Some error situations are caused by a temporary failure; for example, the IP communication socket between the client and the z/Server might not be ready for communication.
In such cases, you will typically receive an org.xml.sax.SAXParseException message, sometimes with the reason “Content not allowed in prolog.”. Communication between the client and z/Server scheduler address space is in XML format. When the client does not receive an expected XML response (for instance because the scheduler address space is temporarily unavailable), a SAX exception occurs. In this case, first try to repeat the action, and it might work.
For more information, General problem determination describes general troubleshooting methods which apply to all components, z/Explorer problem determination describes special methods for z/Explorer, and Application Workflow Manager problem determination describes methods for modeled Application Workflow Manager applications.