Write code generation messages, generated by the backend, to SYSPRINT DD dataset if messages are linked to source code.

In the compilation output, each compiler message, with the exception of the code generation messages in the range 5000-5999, produced by the frontend starts with IBMnnnnI X where:
- IBM indicates that the message is a PL/I message.
- nnnn is the number of the message.
- The closing letter I indicates that no system operator action is required.
- The X represents a severity code.
Compiler messages produced by the compiler frontend are written, in groups according to their severity level and to the component that produced them, to the SYSPRINT DD dataset.

Example:
DDNAME StepName
PRINT2 PRINT
5655-PL5 IBM(R) Enterprise PL/I for z/OS CO021 : PROC(PCOM) OPTIONS(MAIN,REENTRANT);
Compiler Messages
Message Line.File Message Description
IBM2600I W Compiler backend issued warning messages to STDOUT.
IBM2642I W 1.0 OPTIONS(REENTRANT) is ignored.
...

Under batch, the code generation messages generated by the backend component are written to the STDOUT DD dataset.
As flow analysis occurs in the backend component the stdout contains, besides abends in the backend, also messages linked to the source code.

Example:
DDNAME StepName
STDOUT PLIE
WARNING IBM5109: Infinite loop detected in function CO021. Program may not stop
...

The objective of this RFE is to have compiler messages generated by the backend and that are linked to the source code, also written to the SYSPRINT DD dataset.
This in the same format as the message produced by the frontend (starting with IBMnnnnI X).