The following table lists the function, device requirements, and allowable device classes for each data set that the compiler uses.
| Type | ddname | Function | Required? | Device requirements | Allowable device classes | Can reside in HFS? |
|---|---|---|---|---|---|---|
| Input | SYSIN1 | Reading source program | Yes | Card reader; intermediate storage | Any | Yes |
| SYSOPTF | Reading compiler options | If OPTFILE is in effect | Card reader; intermediate storage; direct access | Any | Yes | |
| SYSLIB or other copy libraries1 | Reading user source libraries (PDSs or PDSEs) | If program has COPY or BASIS statements (LIB is required) | Direct access | SYSDA | No | |
| Utility | SYSUT1, SYSUT2, SYSUT3, SYSUT4, SYSUT62 | Work data set used by compiler during compilation | Yes | Direct access | SYSDA | No |
| SYSUT52 | Work data set used by compiler during compilation | If program has COPY, REPLACE, or BASIS statements (LIB is required) | Direct access | SYSDA | No | |
| SYSUT72 | Work data set used by compiler to create listing | Yes | Direct access | SYSDA | No | |
| Output | SYSPRINT1 | Writing storage map, listings, and messages | Yes | Printer; intermediate storage | SYSSQ, SYSDA, standard output class A | Yes |
| SYSTERM | Writing progress and diagnostic messages | If TERM is in effect | Output device; TSO terminal | Yes | ||
| SYSPUNCH | Creating object code | If DECK is in effect | Card punch; direct access | SYSSQ, SYSDA | Yes | |
| SYSLIN | Creating object module data set as output from compiler and input to linkage editor or binder | If OBJECT is in effect | Direct access | SYSSQ, SYSDA | Yes | |
| SYSADATA | Writing associated data file records | If ADATA is in effect | Output device | Yes | ||
| SYSJAVA | Creating generated Java source file for a class definition | If compiling a class definition | (Must be an HFS file) | Yes | ||
| SYSUDUMP, SYSABEND, or SYSMDUMP | Writing dump | If DUMP is in effect (should be rarely used) | Direct access | SYSDA | Yes | |
| SYSDEBUG | Writing symbolic debug information tables to a data set separate from the object module | If TEST(. . .,SEP,. . .) is in effect | Direct access | SYSDA | Yes | |
| SYSMDECK | Writing expansion of COPY, BASIS, REPLACE, and EXEC SQL INCLUDE statements | If MDECK is in effect | Direct access | SYSDA | Yes | |
|
||||||
related references
Logical record length and block size
EXIT