Compiler Options

Interaction between the term, print, disk, and type Options

The term , print , disk , and type options interact as shown in the following tables.

***Interaction between term and print under OS/390 Batch and in TSO***
Option or Options Requested	Result
`term` , `print`	A listing file (including any error messages) is generated. (table note 1) Error messages also go to `stderr` . (table note 2)
`noterm` , `print`	A listing file is not generated. Because `noterm` is explicitly requested, error messages are not sent to the terminal.
`print` (default is `noterm` )	A listing file (including any error messages) is generated. Error messages are not sent to the terminal.
`noprint` (default is `term` )	No listing file is generated. All error messages go to `stderr` .

TABLE NOTE 1: See the discussion of print for the destination of the listing file for your environment.

TABLE NOTE 2: Note that even when term is in effect, compiler information banners are not written to stderr .

***Interaction between term, print, disk, and type under CMS***
Option or Options Requested	Result
`term` (default is `disk` )	A listing file (including error messages is generated and sent to the A-disk. Messages also go to the terminal.
`noterm` (default is `disk` )	A listing file is generated. Messages are not sent to the terminal.
`disk` , `print` (default is `term` )	A listing file (including error messages) is generated. Messages also go to the terminal.
`type` (default is `term` )	A listing file (including any error messages) is produced and sent to the terminal. Only one copy of messages is sent to the terminal.
`noprint` (default is `term` )	No listing file is produced. By default, all messages go to the terminal.
`noprint` , `noterm`	A listing file is not produced. Because `noterm` is explicitly requested, messages are not sent to the terminal.