Deployment errors can occur when you try to run the Web services
assistant batch jobs or install a PIPELINE or WEBSERVICE resource in CICS®. In the
event of a deployment error, PIPELINE resources usually install in a DISABLED
state, and WEBSERVICE resources install in an UNUSABLE state. The most common
deployment errors are described here, including the symptom of the problem,
the cause and the solution.
Information and error messages associated with the Web services assistant
batch jobs are located in the job log. Error messages associated with installing
resources are located in the system log.
- You receive a return code of 4, 8, or 12 when running the Web services
assistant batch jobs DFHWS2LS or DFHLS2WS. The return codes mean
the following:
- 4 - Warning. The job completed successfully, but one or more warning messages
have been issued.
- 8 - Input error. The job did not complete successfully. One or more error
messages were issued while validating the input parameters.
- 12 - Error. The job did not complete successfully. One or more error messages
were issued during execution.
- Check the job log for any warning or error messages. Look
up the detailed explanations for the messages. The explanations normally describe
actions that you can take to fix the problem.
- Ensure that you have entered the correct values for each of
the parameters in the job. Parameter values such as file names
and elements in the Web service description must be treated as case sensitive.
- Ensure that you have specified the correct combination of parameters.
For example, if you include the PGMNAME parameter in
DFHWS2LS when generating a Web service binding file for a service requester,
you get an error and the job does not complete successfully.
- You receive a DFHPI0914 error message when attempting to install
a WEBSERVICE resource. The message includes some information about the cause
of the install failure.
- Check that you have authorized CICS to read the Web service binding file
in z/OS® UNIX.
- Check that the Web service binding file is not corrupt. This can occur, for example, if you use FTP to transfer the file to z/OS UNIX in
text mode rather than binary mode.
- Check that two Web service binding files with the same name
are not in different pick up directories.
- If you are attempting to install a resource for a Web service
requester application, check that the version of the SOAP binding matches
the level supported in the pipeline. You cannot install a SOAP
1.1 WEBSERVICE into a service requester pipeline that supports SOAP 1.2.
- Check that you are not installing a provider mode WEBSERVICE
resource into a requester mode pipeline. Provider mode Web service
binding files specify a PROGRAM value, whereas requester
mode binding files do not.
- If you are using DFHWS2LS or DFHLS2WS, check that you have specified
the correct parameters when generating the Web service binding file. Some parameters, such as PGMNAME, are only allowed
for Web service providers and have to be excluded if you are creating a Web
service requester.
- If you are using DFHWS2LS or DFHLS2WS, check the messages issued
by the job to see if there are any problems that you need to resolve before
creating the WEBSERVICE resource.
- The PIPELINE resource fails to install and you receive a DFHPI0700,
DFHPI0712, DFHPI0714 or similar error message.
- If you received a DFHPI0700 error message, you need to enable
PL/I language support in your CICS region. This is required
before you can install any PIPELINE resources. See Language Environment support for PL/I for
more information.
- Check that you have authorized CICS to access the z/OS UNIX directories to read the pipeline configuration
files.
- Check that the directory you are specifying in the WSDIR parameter
is valid. In particular, check the case as directory and file names
in z/OS UNIX are
case-sensitive.
- Ensure that you do not have a PIPELINE resource of the same
name in an ENABLED state in the CICS region.
- The PIPELINE resource installs in a DISABLED state. You get an
error message in the range of DFHPI0702 to DFHPI0711.
- Check that there are no errors in the pipeline configuration
file. The elements in the pipeline configuration file can only
appear in certain places. If you specify these incorrectly you get a DFHPI0702
error message. This message includes the name of the element that is causing
the problem. Check the element description to make sure you have coded it
in the correct place.
- Check that you do not have any unprintable characters, such
as tabs, in the pipeline configuration file.
- Check that the XML is valid. If the XML is not valid,
this can cause parsing errors when you attempt to install the PIPELINE resource.
- Ensure that the pipeline configuration file is encoded in US
EBCDIC. If you try to use a different EBCDIC encoding, CICS cannot process
the file.