Collect troubleshooting data for Dynamic Scripting problems in CICS TS for z/OS 4.1

Resolving The Problem

For the most up-to-date documentation, refer to Collecting CICS troubleshooting data (MustGather) for IBM Support in the CICS TS documentation. You will find the General information you should gather for every type of problem followed by the Component-specific information which includes Troubleshooting data for Dynamic Scripting problems in CICS TS 4.2 or CICS TS 4.1.

The following is the original MustGather information:

Collect this MustGather data before contacting IBM Support:

• Collecting general information for all problems
• Collecting data for Dynamic Scripting problems
• Troubleshooting hints and tips
• Exchanging data with IBM Support


• Collect troubleshooting data for CICS products - Read first

Back to top

• If available, the JVM server standard out and standard error files. These files are created in the JVM server working directory. For command-line interface (CLI) JVMs, this is the directory from which you enter the command. For application JVMs, this is the root directory of the application.
  
  The files are named applid.JVMServerID.dfhjvmerr and applid.JVMServerID.dfhjvmout, where applid is the APPLID of the CICS region and JVMServerID is the name of the JVMSERVER resource.

• Enter export CICS_DEBUG=ON to set the environment variable CICS_DEBUG to "on" in the z/OS UNIX shell before starting the application or running the problematic CLI command. This will result in extra logging being sent to the console and the log files.
  
  
• Provide the contents of your JVM profile directory. This directory is defined by the JVMPROFILEDIR system initialization parameter in your CICS region.

Back to top

• Review the logs and dumps generated at the point of failure.
• Search the CICS support site for known problems using symptoms like the message number and error codes.
• If you find a fixing PTF, see Ordering CICS products and maintenance for the options that are available to order CICS maintenance.
• Gather the documentation and work with the CICS support team to resolve your problem.
  
  

• Troubleshooting and Support for Dynamic Scripting

1. See Exchanging information with IBM Technical Support for FTP and email instructions using the IBM Enhanced Customer Data Repository (ECuRep).
   
2. Go to the Service Request page to open or update a problem. If you have a SoftwareXcel enterprise edition for zSeries contract, you can also ask a non-defect installation and usage questions.
   
   Note: Always update your Service Request (problem record) to indicate that data has been sent.

Back to top