MSGFILE considerations when using PL/I

If MSGFILE(SYSPRINT) is in effect, use SYSPRINT only to direct output to the PL/I SYSPRINT STREAM PRINT file.

Because performance is slower with the MSGFILE(SYSPRINT) option, it is recommended only for debugging purposes. For production applications, direct user-created output to the PL/I SYSPRINT STREAM PRINT file.

In a nested enclave environment, you can specify MSGFILE(SYSPRINT) for all enclaves in the application or only for those enclaves containing PUT statements. For batch, multiple enclaves in a Language Environment process can use the PL/I SYSPRINT STREAM PRINT. In this instance, you cannot open the file until it is referenced, and it is closed by Language Environment at process termination.

Under CICS®, the MSGFILE runtime option is ignored. Both runtime messages and the SYSPRINT STREAM PRINT file output are directed to the CESE transient data queue. The CESE transient data queue is a CICS thread-level resource. See Running applications under CICS for more information about the CESE transient data queue.

For more information about directing PL/I output, refer to IBM Enterprise PL/I for z/OS library .