Generating Dialogs
The Dialog Options Screen in ADSC has several options whose settings are standardized. This is a description of those options and their required settings on test and production. The other dialog options
used should be consistent between test and production.
Symbol Table
Use 'symbol table yes' only on the test system. It is required only if you are using the DEBUG or TRACE options of ADS. Before moving the dialog to production, regenerate the dialog with 'symbol table no'. On production IDMS, also generate the dialog with 'symbol table no'.
Diagnostic Tables
This option allows IDMS to produce an error screen indicating the statement in error when a dialog aborts. Set 'diagnostic tables yes' on the test system if you are debugging a dialog. Set it to 'no' before migrating the dialog to production, and set it to 'no' in production.
By setting 'symbol table no' and 'diagnostic tables no', the size of the dialog load module is greatly decreased, sometimes by over 20 percent. This means the program takes up 20 percent less space
in memory and 20 percent less space in the disk load area.
Activity Logging
This option should be set to 'no' on test, but 'yes' on production. It allows the IDD to keep a record of how the dialog accesses records. It does not affect the execution code, but greatly increases the time it takes to generate a dialog. If all dialogs on production were generated with this option on, we could produce accurate reports indicating all programs that access a record in a certain way (OBTAIN, ERASE, etc. ), which is very handy when a record's elements are to be modified.
Option Summary
| OPTION |
PRODUCTION |
TEST |
| SYMBOL TABLE |
NO |
YES |
| DIAGNOSTIC TABLES |
NO |
YES |
| ACTIVITY LOGGING |
YES |
NO |
