sysLib.writeStdErr() is typically used for debugging.
sysLib.writeStdErr(text STRING in)
The following example sends a comment to the console to help debug a program.
sysLib.writeStdErr("Opened file");
Platform | Issue |
---|---|
Java™ generation | The output of the function goes to the System.err output stream of the JVM. The default is to route the output to the console. However, when you start the JVM, you can route the output to a different location. |
COBOL generation | sysLib.writeStdErr() uses the COBOL DISPLAY statement to write output, which goes to the destination that is also used for sysLib.writeStdOut(). |
CICS® | All output is displayed on a JES output stream, and output from different transactions is intermingled. |
IMS/VS | The output destination is the DDNAME that you specify in the COBOL compiler option OUTDD. By default, the output is written to the DDNAME SYSOUT in the job that starts the message region. |
iSeries® COBOL | DISPLAY output goes to the QPRINT queue. |
z/OS batch |
The output destination is the DDNAME that you specify in the COBOL compiler option OUTDD. By default, the output is written to the DDNAME SYSOUT in the JCL that starts the run unit. |
zSeries® COBOL | Ensure that you have specified the correct CODEPAGE
compiler option for your language so that the text displays properly.
Set the code page compiler option in one of the following ways:
|