Troubleshooting data for CICS TS Feature Pack for Mobile Extensions V1.0 in CICS TS 4.2 or CICS TS 5.1
CICS® MustGather for CICS TS Feature Pack for Mobile Extensions problems
Before you gather the following documentation and contact IBM® Support, run the sample application that is distributed with the feature pack to verify your installation. For instructions, see Verifying the operations of the CICS TS Feature Pack for Mobile Extensions.
Gather the following diagnostic information before contacting the CICS support team to troubleshoot your CICS TS Feature Pack for Mobile Extensions problems.
- Required data:
-
For problems with the CICS JSON assistants, including problems with DFHJS2LS or DFHLS2JS, provide the following documentation:
- A description of the problem.
- The source document. For DFHLS2JS, the document includes the language structure (copybook). For DFHJS2LS, the document includes the JSON schema that is used as input.
- A list of the parameters that you specified.
- The log file that is generated by DFHJS2LS or DFHLS2JS.
For problems with the configuration of a pipeline that is used to handle JSON web service requests, provide the pipeline configuration file that is used. This file includes problems with installing and manipulating pipelines. For more information about the pipeline configuration file, see Creating the CICS infrastructure for a JSON service provider.
For JSON web services runtime problems or problems in using the linkable interface to transform JSON, provide the following documentation:- 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, request a dump
when you receive the message by enter the following
command:
where xxxxx is the CICS message without the DFH prefix.CEMT SET SYD(xxxxx) SYS MAX(1) ADD
And then re-create the problem or wait for it to occur.
- 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:
- Level 1-2 for the ML, PG, PI, SO, and WB components. ML level 2 trace might affect performance.
- Level 1-2 for the AP component if you have a code page conversion problem.
- Level 1 for all other CICS components.
- An unformatted CICS auxiliary trace if no dump is
available. For more information on CICS auxiliary 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.