Error Conditions

The following is a list of error conditions you might see in SERPRINT:

Unable to find Global Record.

This means that either there was a package master read error or you have an invalid package master. Check your package master to see if you have the correct one define to the started task.

Soap member is undefined.

This means the Soap file member is not defined in administration. Go to global administration A.G.O.3 and define your Soap File Member.

Unable to open SOAP DSN cmninfo.dd.info.soap.file.

This means that the soap file defined to the started task DD CMNINFO could not be opened. Check your start task procedure to see if you the CMNINFO DD defined and it has the proper Soap File DSN defined.

Unable to find SOAP member soapfile.

This means that the Soap file member defined in administration could not be found. Check your Soap File definition in global administration (A.G.O.3) and verify that you have the member defined in the Soap File.

Unable to read SOAP member soapfile.

This means that the Soap file member defined in administration could not be opened for reading. Verify that you can browse the Soap File member defined in global administration.

Unable to find start XMLTAGS in soapfile.

This means you have not defined the beginning of the ZMF variables table defined in the Soap file. Verify that you have XMLTAGS defined in your soap file member.

Unable to find start ENDXMLTAGS in soapfile.

This means you have not defined the ending of the ZMF variables table defined in the Soap file. Verify that you have ENDXMLTAGS defined in your soap file member.

Unable to find start READREQ in soapfile.

This means you have not defined the beginning of the read request defined in the Soap file. Verify that you have READREQ defined in your soap file member.

Unable to find start ENDREAD in soapfile.

This means you have not defined the ending of the read request defined in the Soap file. Verify that you have ENDREAD defined in your soap file member.

Unable to find start UPDATEREQ in soapfile.

This means you have not defined the beginning of the update request defined in the Soap file. Verify that you have UPDATEREQ defined in your soap file member.

Unable to find start ENDUPDATE in soapfile.

This means you have not defined the ending of the update request defined in the Soap file. Verify that you have ENDUPDATE defined in your soap file member.

Unable to find start CREATEREQ in soapfile.

This means you have not defined the beginning of the create request defined in the Soap file. Verify that you have CREATEREQ defined in your soap file member.

Unable to find start ENDCREATE in soapfile.

This means you have not defined the ending of the create request defined in the Soap file. Verify that you have ENDCREATE defined in your soap file member.

Unable to find start PARENTREQ in soapfile.

This means you have not defined the beginning of the parent read request defined in the Soap file. Verify that you have PARENTREQ defined in your soap file member.

Unable to find start ENDPARENT in soapfile.

This means you have not defined the ending of the parent read request defined in the Soap file. Verify that you have ENDPARENT defined in your soap file member.

Unable to find ENDPOINT for request type in soapfile.

This means there is no ENDPOINT defined for the request type in the Soap File. Verify that you have ENDPOINT defined in your soap file member.

Invalid EndPoint or not defined for request type in soapfile.

This means the ENDPOINT statement was found, but the data was invalid or did not start with http://. Verify that your ENDPOINT statement defined in your soap file member. Verify that it starts with http://hostname:port/url

The following errors are HTTP caller related errors. They start with one of the 3 following statements. If one of these 3 messages is all you get, this is all we know about the error. If an HTTP error is available it will also follow the message.

SOAP initialization failed

SOAP initialization No Buffer

SOAP Send did not complete

HTTP errors that follow one of the 3 above messages:

invalid CMNHTTP function.

This should not happen, but if it does, cycle the started task and try again.

URL Address is invalid.

Check your soap file and verify that the URL defined in the ENDPOINT definition is correct.

URL length is invalid.

Check your soap file and verify that the URL defined in the ENDPOINT definition is correct.

connect to TCP/IP interface failed.

The connection to TCP/IP on the mainframe failed, check to make sure the TCP/IP task is available and functioning correctly on your LPAR.

GETHOSTBYNAME failure.

The host name defined in the soap file could not be found. Check your soap file to verify that the host name specified in the ENDPOINT definition is correct. TCP/IP on the mainframe was unable to find the host name. Try to ping the host name on the mainframe. The host name is unavailable or does not exist if you cannot ping it from the mainframe.

CONNECT failed.

Check your soap file to verify you have the correct ENDPOINT definition. The host you are trying to connect to failed and maybe unavailable, contact the host administrator.

SEND failed.

The soap send function failed. This has many reasons for a failure and there may be an HTTP error after this message such as an HTTP 500 error. See an HTTP manual for the HTTP errors.

Servlet returned 202 Response.

There was a failure executing the soap file sent to the host. See an HTTP manual for this error.

No response from servlet.

There was no response sent back from the host. There may also be an HTTP error after this message. See an HTTP manual for the HTTP errors.

Servlet returned other than 200/202.

An error occurred trying to execute the soap on the host. There should be an HTTP error following this message. See an HTTP manual for the HTTP errors.