Diagnosing deployment errors

Deployment errors can occur when you try to run the CICS® web services assistant batch jobs or the CICS XML assistant batch jobs, install a PIPELINE resource in CICS, or install a WEBSERVICE resource in CICS. The most common deployment errors are described here, including the symptom of the problem, the cause and the solution.

• You receive a return code of 0, 4, 8, or 12 when running the CICS web services assistant batch jobs or the CICS XML assistant batch jobs.
  The return codes mean the following:

  • 0 - The job completed successfully.
  • 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.
  1. 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.
  2. 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 should be treated as case sensitive.
  3. 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 return code of 1, 136 or 139 when running the CICS web services assistant batch jobs or the CICS XML assistant batch jobs.
  These return codes indicate that the JVM has failed, usually because there is insufficient storage available. The CICS assistants require a JCL region size of at least 300 MB, although some documents might require 400 MB.
  1. Increase the region size, or consider setting the region size to 0M.
  2. Check for any active IEFUSI exits, which can limit the region size.
  

  Note: If you use a 64bit JVM, ensure you specify a suitable MEMLIMIT value.

  
• You receive a return code of 137 when running the CICS web services assistant batch job DFHLS2WS, or the CICS XML assistant batch job DFHLS2SC. This return code means that the job timed out.
  1. Increase the time by coding the TIME parameter on the EXEC statement of your job to TIME=1440, or increase the MAXCPUTIME value in the SYS1.PARMLIB(BPXPRMxx) member.
• 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.
  1. Check that you have authorized CICS to read the web service binding file in z/OS UNIX.
  2. 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.
  3. Check that two web service binding files with the same name are not in different pick up directories.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  1. 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.
  2. Check that you have authorized CICS to access the z/OS UNIX directories to read the pipeline configuration files.
  3. 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.
  4. 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.
  1. 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.
  2. Check that you do not have any unprintable characters, such as tabs, in the pipeline configuration file.
  3. 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.
  4. 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.
• The WEBSERVICE resource is in a DISABLED state.
  The states DISABLED and DISABLING are only available for WEBSERVICE resources that are defined and installed in CICS bundles.
  1. If the PIPELINE resource associated with the WEBSERVICE resource has been discarded, the WEBSERVICE resource enters DISABLED state. Investigate why the PIPELINE resource is missing, and replace it if appropriate.
  2. If a disable action has been carried out for the CICS bundle where the WEBSERVICE resource is defined, the WEBSERVICE resource enters DISABLED state when the web service is no longer in use. Investigate the state of the CICS bundle, and enable it if appropriate.