DD Statements

The CA Chorus Application Server writes the output to the following DD statements:

JESMSGLG

Displays the confirmation that the CA Chorus UI is available, the STOP command has been received, and other important messages.

Note: This data set is the first place to refer when investigating a problem.

SYSPRINT

Displays the startup information for the spawning of the internal CA DSI server, as well as messages whenever a login is made (no user ID or timestamp). Additionally, you see messages from the Data Source API code when it initiates the DATACOM connection and executes queries. You can also see messages from the QUIKREF data handler as it performs keyword searches. This is the output from the C code that is invoked through JNI.

SYSOUT

Displays the output from the JZOS launcher. If the confirmation does not appear, consider it as a sign of the task not responding. The values of all the environment variables and the JVM options are displayed here. So, look here verify the JVM options. If the server goes down with a program check abend, from here you get the PSW and registers at the time of the program check. It displays a stack trace from the abend here. However, you will probably not be able to resolve the symbols for functions that are located in JNI modules. This information should go with the system dump that is produced if a program check ("gpf signal") occurs.

STDOUT

Displays the debug messages and stacktraces coming from the CA Chorus Application Server. This location should be the second place to look when troubleshooting a problem. Any relevant stacktraces or problems reported by the CA Chorus Application Server usually appear here. Most of this information is also included in the server.log file, which is located in the $CHORUS_HOME/logs location as an ASCII file.

Note: An EBCDIC version of the same log file also resides in the $CHORUS_HOME/logs location.

STDERR

Displays the ERROR level output from log4j, typically stacktraces.

QWSFTRCE

Displays the diagnostic file for calls to QuickRef. If there are error messages that are produced while trying to access QuickRef, set CHORUS_QWS_DEBUG=YES in the CETJOPTN(ENVETJ) dataset. The QWSFTRCE output contains the trace information each time a call to QuickRef is done. QuickRef is usually searched each time a Knowledge Center search is executed. Because the number of QuickRef accesses can be high, we recommended not to use this debug option unless you are experiencing a problem.

QWSFDUMP

Displays the snap entries that are related to the calls to QuickRef. This is used with the above trace file.