Troubleshooting data for Node.js problems in CICS Transaction Server for z/OS, Version 5 Release 5 or later

CICS® MustGather for Node.js problems

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your Node.js problems.

Required data:
  1. The CICS job log and any entries in the SYSOUT and SYSnnnn DD cards. Ensure this is sent in tersed binary format. The job log contains CICS messages that are relevant to the BUNDLE resource and Node.js application.
  2. The Node.js profile contents, and files that are included using the %INCLUDE profile option. Ensure that you identify the Node.js profile correctly. The NODEJSAPP resource defines the file name and the location of the Node.js profile. You can use INQUIRE NODEJSAPP API or the CEMT INQUIRE NODEJSAPP command to inquire on the NODEJSAPP resource.
  3. The LOG, STDERR, STDOUT, and TRACE files. Refer to the Node.js profile options to determine their location, as described in Node.js profile and command line options. You can also use the INQUIRE NODEJSAPP API or the CEMT INQUIRE NODEJSAPP command to determine the locations of these files. The STDERR file contains the Node.js stack trace when a JavaScript exception occurs. The STDOUT file contains information written by the application. The LOG file contains CICS messages related to managing the environment for Node.js. The TRACE file contains CICS trace information relating to the execution of the Node.js runtime and application.
  4. The CICS internal trace table that is included in a z/OS® system dump when tracing is active. 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. Set CICS JS component tracing to level 1-5, and all other components to at least level 1. For more information, see Using trace for CICS problem determination on z/OS.
    Note: Besides the trace that is written to the internal trace table, trace entries for each Node.js application are written to a unique file on zFS. For more information, see Activating and managing tracing for Node.js applications.
  5. The Language Environment® system dump. This is required if there is a failure in the Node.js application or in the Language Environment (LE) enclave that the Node.js application runs. The high-level qualifier for the dump dataset is controlled by the Language Environment runtime option DYNDUMP. For more information, see z/OS Language Environment Programming Reference. An IEA822I message is written to the CICS job log identifying the dump dataset. In addition, a CEEDUMP may be written to the CICS job log.
  6. The Node.js version used by the application. To determine the Node.js version, execute the z/OS UNIX command:
    <NODE_HOME>/bin/node --version

    where <NODE_HOME> is the value of the NODE_HOME option specified in the Node.js profile.