Overview

The dialog compiler is used to define dialogs that perform transaction input and output, database retrieval and update, and any required processing within an application.

Associated Map

The environment within which a dialog can be executed depends on the map with which it is associated, as follows:

A dialog associated with an online map can be executed only in the online environment.
A dialog associated with a file map can be executed only in the batch environment.
A mapless dialog can be executed in either environment.

At runtime, if the runtime system encounters a disallowed dialog, it abends the application.

Process Modules

Process modules associated with batch dialogs can also include online-only commands and command parameters, and vice versa. The dialog compiler, when compiling a process module, accepts both types of commands, regardless of the environment of the dialog. This allows a process module to be used in both the online and batch environments. If, however, the runtime system encounters a disallowed command or command parameter, the application abends. For more information about process commands in the batch and online environments, see CA ADS Batch Concepts.

A dialog can be defined using the dialog compiler in either online or batch mode.

Note: Do not confuse batch and online definition modes with batch and online execution modes. The terms "batch" dialog and "online" dialog refer to the environment in which the dialog can be executed. Batch dialogs and online dialogs can be defined using the dialog compiler in online or batch mode, whichever is most convenient.

Batch Considerations

You can associate a dialog with one input file map and one output file map.
You can specify:
- The z/OS ddnames (z/VSE filenames) of the dialog's input, output, and suspense files
You can specify:
- That the response process currently being defined is the dialog's default response process
- That batch input record response field values and batch control events to associated with the response process