DAMP can also be started from within a BS2000 procedure or executed as a batch job.
A procedure file can, for example, contain the necessary ADD-FILE-LINK commands for assigning the dump and logging files, together with the appropriate DAMP statements for assigning user-defined symbol files, for switching on the logging function or for calling dump analysis and print editing routines. Before the DAMP program is called, task switch 5 must be set in the procedure.
If, in procedure mode, a DAMP statement is followed by a system command that is not permitted at the DAMP program level (see "System level"), DAMP switches from procedure mode to interactive mode and resets task switch 5. The last DAMP output screen is then displayed on the screen. In batch mode, a system command which is not permitted causes the job to be aborted.
Statement sequences which are required frequently during diagnosis with DAMP can also be stored in files. Such a file can then be activated in interactive, batch or procedure mode by means of the START-STATEMENT-SEQUENCE statement. In interactive mode, the last output which was initiated is displayed on the screen after the statement sequence has been executed. In procedure or batch mode, processing of the procedure or batch file is continued when all statements in the sequence have been executed.
When the START-STATEMENT-SEQUENCE statement is used, SYSDTA is temporarily redirected to the specified file. Changing the assignment for SYSDTA in this procedure (or, for example, in a procedure called via START-MODULE) may have unexpected consequences. In particular, the statement START-MODULE DCM should never be used in a statement file, since this can result in an endless loop.
Examples of statement sequences:
Contents of the file DAMP.STATEMENT.DCM
|