The next step in defining the application is to define its dialogs. A dialog is a collection of application components created in earlier steps, including file maps and process modules. You can define a dialog by using the online dialog compiler.
The dialogs in the archive application are described below.
|
Dialog |
Description |
|---|---|
|
ARCD1 |
Reads input records and acts as a mainline routine, passing control to ARCD2, ARCD3, and ARCD4, as required by the application; writes erroneous input records to the suspense file |
|
ARCD2 |
Writes the specified employee record to the archive file, then returns control to ARCD1 |
|
ARCD3 |
Writes the coverage records associated with the specified employee record to the archive file, then returns control to ARCD1 |
|
ARCD4 |
Determines the transaction report lines to be written to the report output file; for each line to be written, passes control to ARCD5; returns control to ARCD1 once all lines have been written for the transaction |
|
ARCD5 |
Writes a report line to the report output file, then returns control to ARCD4 |
The definitions for these dialogs are provided separately below, along with the process modules associated with the dialogs and the mapin or mapout operations that the dialogs perform at runtime. For an illustration of how these dialogs fit together, see the diagram earlier in this section.
|
Copyright © 2013 CA.
All rights reserved.
|
|