Options and Directives Screen

The Options and Directives screen is used to specify options for a dialog, such as:
idmscu
The Options and Directives screen is used to specify options for a dialog, such as:
  • Alternative message prefixes
  • Autostatus
  • Specifying the mainline dialog
  • Including a symbol table
  • Including a diagnostic table
  • Specifying the premap as the entry point
  • Using COBOL or CA ADS rules in handling data types and arithmetic and assignment commands
  • Activity logging
  • Selectively disabling retrieval locks
The current settings for the dialog options are displayed on the screen. Each option can be changed by overwriting the displayed setting or by placing a slash (/) or other nonblank character in the space to the left of the option.
Sample screen
                             Options and Directives                          Dialog  JPKTD10   Version     1  Message prefix  . . . . . . . . . . . DC  Autostatus record . . . . . . . . . . ADSO-STAT-DEF-REC  Version . . . . . . . . . . . . . . .    1  Description . . . . . . . . . . . . . ADS DIALOG  Options and directives  . . . . . . . _ Mainline dialog                                        _ Symbol table is enabled                                        / Diagnostic table is enabled                                        / Entry point is premap                                        _ COBOL moves are enabled                                        / Activity logging                                        / Retrieval locks are kept                                        / Autostatus is enabled  Enter  F1=Help  F3=Exit  F4=Prev  F5=Next
Field Descriptions
  • Dialog
    Displays the name of the current dialog, as specified on the Main Menu screen. This field is protected.
  • Version
    Displays the version number, in the range 1 through 9999, of the current dialog. This field is protected.
  • Message Prefix
    Specifies a 2-character prefix for a message at the dialog level. DC is the default prefix.
  • Autostatus Record
    Specifies the 1- to 32-character name of the status definition record used when the current dialog executes at runtime. The specified status definition record must be defined in the data dictionary. If no record name is specified,
    Autostatus record
    defaults to the name of the status definition record defined at DC/UCF system generation.
    An autostatus record is required if the
    Autostatus is enabled
    option is chosen.
  • Version
    Specifies a 1- to 4-digit version number, in the range of 1 through 9999, of the named status definition record. If a version number is not specified,
    Version
    defaults to the system default version number specified at system generation. If no system default version number is specified,
    Version
    defaults to 1.
  • Mainline Dialog
    Inserting a nonblank character in the accompanying data field specifies that the current dialog is a mainline dialog.
    At runtime, the dialog that executes first in a series of dialogs that make up an application must be a mainline dialog. If a dialog function is initiated by an application task code, the dialog associated with the function must be a mainline dialog.
  • Symbol Table is Enabled
    Inserting a nonblank character in the accompanying data field specifies that a symbol table is created for a dialog.
    A symbol table facilitates the use of element names and process line numbers by the online debugger.
  • Diagnostic Table is Enabled
    Inserting a nonblank character in the accompanying data field specifies that the dialog load module contains diagnostic tables (line number tables and offset tables).
    During the testing of a dialog, the
    Diagnostic table is enabled
    option should be selected.
    Diagnostic tables facilitate the testing and debugging of a dialog. If a dialog aborts, diagnostic tables are used to display the process command in error on the Dialog Abort Information screen. The ADSORPTS utility uses diagnostic tables to format the dialog report for easy reference.
    Once a dialog has been tested thoroughly, the
    Diagnostic table is enabled
    option should be deselected and the dialog recompiled if dialog load module size is a consideration. The size of a large dialog load module can be reduced significantly by compiling the dialog without diagnostic tables.
    The
    Diagnostic table is enabled
    option is deselected by spacing over the slash.
    The
    Diagnostic table is enabled
    option must be selected if the
    Symbol table is enabled
    option is selected.
  • Entry Point is Premap
    The entry point of a dialog specifies the point at which the dialog becomes operative in the application thread.
    Inserting a nonblank character in the accompanying data field specifies that the dialog begins with its premap process.
    Regardless of the specification, a dialog without an online map or a batch input file map begins with its premap process. A dialog without a premap process begins with its first mapping operation.
  • COBOL Moves are Enabled
    Inserting a nonblank character in the accompanying data field specifies that the rules of COBOL are used in the conversion between data types and in the rounding or truncation of the results of arithmetic and assignment commands.
    If COBOL moves are enabled, certain types of invalid expression may be allowed by the CA ADS compiler. When a MOVE, COMPUTE, ADD, SUBTRACT, MULTIPLY, or DIVIDE statement has a numeric source expression and an EBCDIC target expression, the source expression must be a literal or a simple dataname with an optional subscript.
    The default setting for COBOL MOVE is defined in the DC/UCF system generation ADSO statement. NO is the system generation default status.
    The
    COBOL moves are enabled
    option can be modified only if the DC/UCF system generation COBOL MOVE subclause has been defined as OPTIONAL. OPTIONAL is the system default.
    For more information about the COBOL MOVE subclause of the system generation ADSO statement, see the
    CA IDMS System Generation section
    .
  • Activity Logging
    Inserting a nonblank character in the accompanying data field specifies that the dialog uses the activity logging facility. This facility documents all potential database activity by a dialog, based on the database commands issued explicitly or implicitly by the dialog's processes.
    The default setting for the
    Activity logging
    option is defined at DC/UCF system generation.
    For more information about the system generation ADSO statement, see the
    CA IDMS System Generation section
    .
  • Retrieval Locks are Kept
    Inserting a nonblank character in the accompanying data field specifies that database record retrieval locks will be held on behalf of run units started by the dialog.
    Retrieval locks should be disabled only for retrieval dialogs that do not update the database or pass currencies to update dialogs. When retrieval locks are disabled for dialogs that
    do
    update the database or pass currencies, CA ADS displays the following message:
    DC173015  DIALOG ABORTED DUE TO VIOLATION OF NO RETRIEVAL LOCKING RULES
    In addition, the update dialog abends when a higher dialog in the application thread does not have retrieval locks kept and system-wide RETRIEVAL NOLOCKS are specified.
    The update dialog or program is allowed to update the retrieval dialog's database records when the dialog with retrieval locks turned off readies the area in UPDATE mode or when the update dialog or program does not receive currencies when control passes to it.
  • Autostatus is Enabled
    Inserting a nonblank character in the accompanying data field specifies that the autostatus facility is to be used when the current dialog executes at runtime.
    The initial setting corresponds to the autostatus specification defined at DC/UCF system generation. If autostatus is defined as optional, the application developer can override the initial setting. If autostatus is defined as mandatory, this field is protected and the initial setting cannot be changed.