You can quickly find out how a process terminated by examining the C (Completed Mix Entries) system command display. The following is an example of this display:

---Job-Task-Time-Hist---- COMPLETED ENTRIES -----------------
* 1962\3430 11:43 EOT  (LANJ) *LIBRARY/MAINTENANCE
* 2619\3368 11:43 EOT  (ELMER) *OBJECT/MAIL ON PACK
* 3353\3354 11:43 SNTX (ORDS) *BINDER ON SYS37 MCP/FIXSBP ON DPMAST
  3384\3422 11:42 O-DS (JAS) (JAS)MARC WFL
  3384\3423 11:42 P-DS (JAS) (JAS)WFLCODE
  3327\3327 11:42 EOJ  (RALPH) JOB (RALPH)OBJECT/BNATEST ON DPMAST

For each entry, the following information is displayed: the job number, the mix number, the time the process terminated, the type of termination, the usercode of the process, and the name of the process (which is usually the object code file title).

If you know the mix number of the completed process, you can use the <mix number> Y form of the Y (Status Interrogate) system command to display the completion status of that process only. The following is an example of such a command and the response to the command:

7800 Y

   Task 7800 is completed
     7784\7800 15:08 F-DS (JASMITH) (JASMITH)OBJECT/JUNK ON PACK

If the process was initiated from a Menu-Assisted Resource Control (MARC) session, then a similar termination message is automatically displayed on the TASKSTATUS screen. The following is an example:

12:10 3384\3718 EOT  (ROLLINS)MARC  WFL

For a process initiated from a Command and Edit (CANDE) session, abnormal terminations result in a display of the termination type and other process history information. The following is an example:

#2316 OPERATOR DSED @ (00000120)
#O-DS @ 00000120.
#ET=3.2 PT=0.1 IO=0.1

The first two lines shown in the preceding example would be displayed only for an abnormal termination. These lines give the mix number, the cause of the termination, and the sequence number of the statement the process was executing when it terminated. (The sequence number is replaced by a code address if the program was compiled without the LINEINFO compiler option being set. For information about how to interpret the code address, refer to Determining Where a Fault Occurred later in this section.)

The third line in the preceding example is displayed for all terminations (normal or abnormal) of tasks initiated from CANDE. This line gives statistics on the elapsed time, accumulated processor time, and accumulated I/O time for the process.

The CANDE, MARC, and ODT termination messages make use of the same termination type abbreviations. Of these, the following indicate normal terminations:

For processes that terminated abnormally, you can get a general idea of the cause of the termination by examining the DS message (P–DS, O–DS, and so on). Abnormal Termination Messages lists the abnormal termination messages and their meanings.

For a more specific indication of why a process terminated abnormally, you need to examine the values of the history-related task attributes (HISTORYTYPE, HISTORYCAUSE, and HISTORYREASON). Abnormal Termination Messages lists the HISTORYTYPE and HISTORYCAUSE values corresponding to each DS message. For an introduction to history-related task attributes, refer to Determining the Type of Termination later in this section. For a list of the possible values for history-related task attributes, refer to the information later in this guide.