Troubleshooting the JSON assistant

If you are experiencing problems with the JSON assistant, use troubleshooting techniques to diagnose the problem.

The following errors might occur when you run the JSON assistant:

• You receive a return code of 0, 4, 8, or 12 when running the CICS® JSON assistant batch jobs.
  For more information about the return codes, see JSON assistant return codes.
  1. Check the job log for any warning or error messages.
     Look up the detailed explanations for the messages. The explanations often 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 are case sensitive.
  3. Ensure that you have specified the correct combination of parameters.
• You receive a return code of 1, 136, or 139 when running the CICS JSON assistant batch jobs.
  These return codes indicate that the JVM has failed, usually because there is insufficient storage available. The CICS assistant requires a JCL region size of at least 300 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.
• You receive a return code of 137 when running the CICS JSON assistant batch job. 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 message in the range DFHPI9700 - DFHPI9711 indicating an invalid or unsupported JSON schema when running DFHJS2LS.
  1. Check that your JSON schema is valid. You could do this by checking it against the JSON Schema Validation, or you could use a tool, for example json-schema-validator.
  2. Check that your JSON schema is supported by DFHJS2LS. For more information, see High-level language and JSON schema mapping.