Option specification is different for applications written for mainframe- or workation-attached systems.
| Symbol | Definition |
|---|---|
| | (for mainframe-attached systems) |
OR For example, APOST|QUOTE means either APOST or QUOTE (but not both) can be specified. |
| [] (for workstation-attached systems) |
the enclosed variable is optional. |
Supported PP2 options follow:
| Syntax for Mainframe-Attached Systems | Syntax for Workstation-Attached Systems |
|---|---|
| APOST|QUOTE | -a | -q |
| APOSTSQL|QUOTESQL | -as | -qs |
| CHARSET (charset) | -cs charset |
| CURPREFIX (prefix) | -c prefix |
| DATABASE (dbname) | -db dbname |
| DATE (D|E|I|J|U) | -d D|E|I|J|U |
| DYNPREFIX (prefix) | -dp prefix |
| FLAG (I|W|E|S) | -f I|W|E|S |
| INPUT (file spec) | -i filespec |
| LINECOUNT (integer) | -lc integer |
| – | -ld logdata |
| – | -lm logmech |
| MARGINS (m,n [,c ] ) | -m m,n[,c] |
| NULLSCAN|NONULLSCAN | -ns | -nns |
| OPTIONS|NOOPTIONS | -lo | -nlo |
| PRINT [ (file spec) ] |NOPRINT | -l [filespec] | -nl |
| PUNCH [ (file spec) ] |NOPUNCH | -o [filespec] | -no |
| SOURCE|NOSOURCE | -ls | -nls |
| SQLCHECK (FULL|NOSYNTAX) | -sc FULL|NOSYNTAX |
| SQLFLAGGER (NONE|ENTRY|INTERMEDIATE) | -sf NONE|ENTRY|INTERMEDIATE |
| TDPID (tdpid|network group name) | -t tdpid|network group name |
| TERM [ (file spec) ] |NOTERM | -e [filespec] | -ne |
| TRANSACT (ANSI|COMMIT|BTET|2PC) | -tr ANSI|BTET|COMMIT |
| USERID (userid [,password [,accountid ] ] ) | -u userid[,password[,accountid]] |
| VERSION (COBOL|COBOLII|MF1|MF2|LPI) | -v COBOL|COBOLII|MF1|MF2|LPI |
| XREF|NOXREF | -lx | -nlx |
(1) An en dash (–) means unavailable or not applicable.
Whenever the DATABASE or USERID option values contain any Kanji or other multibyte character set characters, the CHARSET option must precede them in the preprocessor invocation line.
The file-spec variable used with some options takes the following forms:
| Client Type | File Spec |
|---|---|
| z/OS mainframe | ddname |
| Workstation-attached | name[.xtn] |
If associated PP2 options are specified more than once (for example, both TERM and NOTERM), the rightmost specification prevails.