Identifies the type of entity to be displayed or punched.
Entity-typemust be a valid system generation entity type.
Specifies a single entity occurrence to be displayed or punched.
Entity-occurrence-namemust be the name of an existing occurrence of the specified entity type. The named occurrence does not have to be associated with the current system, line, or physical terminal.
- Version isversion-numberQualifies the named entity occurrence with a version number.Version-numbermust be an integer in the range 1 through 9,999. The default is 1.
Directs the system generation compiler to display or punch either all entities associated with a specific system or all occurrences of the named entity type associated with the current system.
Entity-type-namemust be a valid system generation entity type.
The DISPLAY ALL option does not include the results of non-generated or pending changes, which are included with DISPLAY CHANGES.
Displays system definitions that are either changed or pending, but not finalized with the GENERATE command.
This option minimizes the risk of unexpected changes to be generated into the SYSGEN load module. Displaying entities that are changed allows the DBA to review the status of the entities and content, and allows the DBA to restore undesirable deletions or specifications.
DISPLAY CHANGES may also be useful for taking inventory of changes made for completeness, before generating. If there are no changed definitions since the last system generation compiler session, the DISPLAY CHANGES output displays the message DC601273: NO CHANGES SINCE LAST GENERATE.
When the command is issued in batch, a return code of 4 indicates that pending changes exist. A return code of 0 indicates that no pending (ungenerated) changes exist. When issuing the DISPLAY CHANGES command in batch, the return code may be useful to conditionally end batch processing.
Directs the system generation compiler to override the options specified by the DISPLAY WITH and DISPLAY ALSO WITH parameters of the SET OPTIONS statement and to include only the indicated information in the displayed or punched definition. The override applies to the current DISPLAY/PUNCH request only.
Directs the system generation compiler to include the indicated information in the displayed or punched definition in addition to the information included because of the options specified by the DISPLAY WITH and DISPLAY ALSO WITH parameters of the SET OPTIONS statement. The additional information is included for the current DISPLAY/PUNCH request only.
Directs the system generation compiler to exclude the indicated information from the information included in the displayed or punched definition because of the options specified by the DISPLAY WITH and DISPLAY ALSO WITH parameters of the SET OPTIONS statement. The information is excluded for the current DISPLAY/PUNCH request only.
Includes or excludes the entity-specific characteristics that make up the entity definition.
Includes or excludes the dates when the entity definition was created and last updated and the identification of the users who created and last updated the definition (given by the PREPARED BY and REVISED BY parameters). History is maintained only for the following entity types: DEFAULT PROGRAM, DESTINATION, LINE, LOGICAL TERMINAL, PHYSICAL TERMINAL, PROGRAM, QUEUE, SYSTEM, and TASK.
Includes or excludes both the entity history and the details of the entity definition.
Includes only the name and version number (if applicable) of the entity occurrence in the displayed or punched definition.
NONE is meaningful only with WITH.
Specifies whether the displayed or punched definition appears as comments or syntax.
- COMmentsSpecifies that each line of the entity definition is displayed or punched as a comment.Comment lines generated by the compiler are indicated by an asterisk and a plus sign (*+) in the first two columns and are ignored when resubmitted to the compiler.
- SYNtaxSpecifies that the displayed or punched definition appears in syntax format. Definitions that are displayed (online only) or punched (online and batch) as syntax can be edited and resubmitted to the compiler as input.
For PUNCH statements only, specifies the destination of the punched output.
- module-specificationCauses the compiler to write punched output to the specified module.Expanded syntax formodule-specificationis presented next.
- SYSpchCauses the compiler to write punched output to the SYSPCH file.