Troubleshooting data for web services, XML, and JSON transformation problems

CICS® MustGather for web services, XML, and JSON transformation problems

If you are a new user to web services, run the web services sample application that is distributed with CICS. For more information on sample applications, see The CICS catalog manager example application. The CICS sample requires that you use WebSphere® Application Server or something similar as the client platform. If you do not have those, you can test CICS web services by using free Eclipse software to ensure that web services are set up correctly in your CICS region. For more information, see Testing CICS Web services.

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your web services problems.

Note: In CICS TS 5.1 or earlier, support for JSON web services is provided by CICS TS Feature Pack for Mobile Extensions. For problems with JSON web services in CICS TS 4.2 or CICS TS 5.1, see Troubleshooting data for CICS TS Feature Pack for Mobile Extensions V1.0 in CICS TS 4.2 or CICS TS 5.1.
Required data:
  1. For the CICS web services assistant, the CICS XML assistant, or the CICS JSON assistant that has problems with DFHWS2LS, DFHLS2WS, DFHSC2LS, DFHLS2SC, DFHJS2LS, or DFHLS2JS, collect the following documentation. For more information, see The CICS web services assistant, The CICS XML assistant, and The CICS JSON assistant.
    1. A description of the problem.
    2. The source document. For DFHLS2WS, DFHLS2SC, and DFHLS2JS, the source document includes the language structure (copybook). For DFHWS2LS, DFHSC2LS, or DFHJS2LS, the document includes the Web Services Description Language (WSDL) file, XML schema, or JSON schema that is used as input to the assistant, and all external WSDL and schema documents that are included in it.
    3. A list of the parameters that you specified.
    4. The log file that is generated by DFHWS2LS, DFHLS2WS, DFHSC2LS, DFHLS2SC, DFHJS2LS, or DFHLS2JS.
  2. For problems with the configuration of a pipeline that is used to handle web service requests, collect the pipeline configuration file that is used. This file includes problems such as handler programs not being called or problems with installing and manipulating pipelines by using CEMT. For more information, see Pipeline configuration files.
  3. For web services runtime problems, collect the following documentation:
    1. An MVS™ system dump if one is taken. For more information, see Using dumps for CICS problem determination on z/OS®. If you receive message DFHPI1007 or DFHPI1008 and a dump is not taken, enter the following command when you receive the message to request a dump:
      CEMT SET SYD(xxxxx) SYS MAX(1) ADD
      where xxxxx specifies the CICS message without the DFH. And then re-create the problem or wait for it to occur.
    2. The CICS internal trace that is included in the MVS system dump when tracing is active. For more information, see Using trace for CICS problem determination on z/OS. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. When possible, turn on the following trace levels:
      1. Level 1-2 for the PI, SO, and WB components.
      2. Level 1-2 for the AP component if you have a code page conversion problem.
      3. Level 1-2 for the ML component. ML level 2 trace might affect performance.
      4. Level 1-2 for the PG component.
      5. Level 1 for all other CICS components.
    3. An unformatted CICS auxiliary trace if no dump is available. For more information on the CICS internal trace and the trace levels you need to turn on, see the CICS internal trace section in Using trace for CICS problem determination on z/OS.