CA ADS Runtime System › Dialog Abort Information Screen

Dialog Abort Information Screen

When a dialog abends at runtime, the CA ADS runtime system can display a diagnostic screen. The display of the diagnostic screen is enabled and disabled by using the DIAGNOSTIC SCREEN clause of the DC/UCF system generation ADSO statement.

Note: For more information on the ADSO statement, see the CA IDMS System Generation Guide.

If the diagnostic screen is enabled when an abend occurs at runtime, error messages are sent to the system log and the Dialog Abort Information screen is displayed. If the diagnostic screen is not enabled when an abend occurs, error messages are sent to the system log and the DC/UCF prompt ENTER NEXT TASK CODE is displayed with the following message:

ERROR OCCURRED DURING PROCESSING. CA ADS DIALOG ABORTED.

The id of the above message is DC466019; the application developer can change the message text by using IDD.

Sample Dialog Abort Information screen

        CA-ADS RELEASE nn.n            *** DIALOG ABORT INFORMATION ***    ABRT
DC173008 APPLICATION ABORTED. BAD IDMS STATUS RETURNED; STATUS=0306

 DATE....: yy.ddm      TIME....: 15:12:29.08        TERMINAL....: LV81004

 ERROR OCCURRED IN DIALOG......: DIALOG1
                AT OFFSET......: 310
                IN PROCESS.....: DIALOG1-PREMAP                   VERSION:    1
                AT IDD SEQ NO. : 00000200

SEQUENCE
NUMBER:         SOURCE :
00000100 IF FIRST-TIME
00000200    FIND CURRENT EMPLOYEE.
00000300 DISPLAY.

 HIT ENTER TO RETURN TO DC OR ENTER NEXT TASK CODE:

Field Descriptions

DATE

Specifies the date on which the dialog abended.

TIME

Specifies the time at which the dialog abended.

The date and time aid in locating the snap dump, if any, for the abend in the print log file.

TERMINAL

Specifies the logical terminal at which the abend occurred.

DIALOG

Specifies the name of the aborted dialog.

OFFSET

Specifies the hexadecimal offset for the command that was executing when the abend occurred. The offset is taken from the dialog's fixed dialog block (FDB).

PROCESS

Specifies the name of the premap or response process containing the command that caused the abend.

VERSION

Specifies the version number of the process containing the command that caused the abend.

IDD SEQ NUMBER

Specifies the data dictionary sequence number of the source line containing the command that caused the abend. The IDD sequence number is not displayed if the dialog was compiled without diagnostic tables.

SEQUENCE NUMBER

Specifies the internal command numbers of the source line containing the command that caused the abend and of the source lines immediately preceding and following it.

Internal command numbers are not displayed if the dialog was compiled without diagnostic tables.

Internal Commands for CA ADS Process Statements

Internal command numbers are assigned to all CA ADS process statements in addition to the IDD sequence numbers. IDD numbers may overlap or repeat when code is included from another data dictionary module.

Internal command numbers are assigned sequentially, regardless of the source of the process code. When the abending process command is from an included module, IDD sequence numbers should be used in conjunction with internal command numbers to pinpoint the position of the command.

Internal Commands for SQL Statements

Internal commands are created by CA ADS to implement SQL statements. These commands always have the sequence number of the line on which END-EXEC was coded.

SOURCE

Displays the first 70 characters of text of the source line containing the command that caused the abend and of the source lines immediately preceding and following the command. Source lines are not displayed if the dialog was compiled without diagnostic tables.

The three command lines are displayed only if the date on which the dialog was compiled agrees with the date on which the process was last revised. This prevents the display of source code that has been revised since the dialog was last compiled. Note, however, that the display of process text other than that from which the dialog was compiled could occur under the following circumstances:

• During a single day, the following actions occur:
  1. The process is revised.
  2. The dialog is recompiled.
  3. The process is revised again, but the dialog is not recompiled again.

  In this case, the process source does not match the compiled process in the dialog load module.

• During a single run of the DC/UCF system, the following actions occur:
  1. The dialog is recompiled by using the batch dialog compiler.
  2. The dialog's program definition element (PDE) in the system program pool is not updated. (The PDE can be updated by using the NEW COPY option of the DCMT VARY PROGRAM command.)
  3. The dialog is executed.

  In this case, the process source matches the compiled process in the dialog load module, but an old version of the dialog that remains in the DC/UCF program pool is being executed.

SYSTEM MESSAGE AREA

Displays the informational and error messages returned by the CA ADS runtime system.

HIT ENTER TO RETURN TO DC OR ENTER NEXT TASK CODE

Prompts the user for a DC/UCF task code.

If a dialog aborts during an online debugging session, a special version of the diagnostic information screen is displayed.

More information:

CA ADS Dialog Compiler (ADSC)

CA ADS Dialog and Application Reporter