| Previous | TContents | YIndex |
, This output will continue until interrupted. : 5.3.4 Abort an executing job
E A job which is currently in the K queue (Submitted for execution) or @ the L queue (Execution started) can be aborted either through a A SCHEDULE DCL command or directly through the DELETE DCL D command. First get the queue entry number by using the DCL command: F command or directly through the rm command. First get the queue entry number by using the command:
|
" $ SCHEDULE TYPE/QUEUE K,L , Scheduling queue K: Submitted for execution & Scheduling queue L: Execution started 1 119. [DEMO.D]A1 (1559) Execution queue entry 695 |
0 Then enter either of the following DCL commands:
|
" ( $ SCHEDULE MODIFY/QUEUE/ENTRY=119/ABORT $ DELETE/ENTRY=695 |
C This will cause the job to terminate with a FAILURE result status. E Since job A1 was configured for both BROADCAST and MAIL notification C upon a FAILURE result, within a few seconds the following messages appear on the screen:
|
" $ = Reply received on DWS from user SYSTEM at DWS Batch 09:59:48 [DEMO.D]A1 - Job failed $ 9 New mail on node DWS from CLUSTR::SYSTEM "Job scheduler" |
$ The mail message appears as follows:
|
" # #1 13-DEC-1996 09:59:57.22 NEWMAIL % From: CLUSTR::SYSTEM "Job scheduler" To: JDOE CC: Subj: [DEMO.D]A1 - Job failed C ------------------------------------------------------------------ # S C H E D U L E Event Notification [DEMO.D]A1 - Job failed Desription: Job /demo/d/a1 % Startup check before database update % Current time 13-DEC-1996 09:59:49.90 Set id 1560 Set tag Set parameter Scheduling entry 0 Started 13-DEC-1996 09:59:10.43 ! Finished 13-DEC-1996 09:59:34.31 Status %X00048084 . %JBC-F-JOBABORT, job aborted during execution C ------------------------------------------------------------------ A Job A1 has failed. Correct the cause of the failure and manually resubmit job A1. |
a 5.4 Review events of job execution
G The events that occurred during the execution of the jobs are saved in H a history database. These events can be reviewed by displaying a simple 9 listing on the screen or by generating a formated report. 4 5.4.1 Simple listing
G To output a simple listing on the screen of job completion events from 2 the last 24 hours, use the following DCL commands:
|
" > $ SCHEDULE TYPE/HISTORY [DEMO.D]* /QUEUE=R/FROM=NOW-24/TO=NOW [DEMO.D]A1 # December 5, 1996, 12:39 R Msg comp [DEMO.D]A2 # December 5, 1996, 12:41 R Msg comp [DEMO.D]A3 # December 5, 1996, 12:41 R Msg comp [DEMO.D]B1 # December 5, 1996, 12:43 R Msg comp [DEMO.D]B21 # December 5, 1996, 12:44 R Msg comp [DEMO.D]B22 # December 5, 1996, 12:45 R Msg comp [DEMO.D]B23 # December 5, 1996, 12:45 R Msg comp [DEMO.D]B24 # December 5, 1996, 12:46 R Msg comp [DEMO.D]F # December 5, 1996, 12:48 R Msg comp [DEMO.D]G # December 5, 1996, 12:47 R Msg comp [DEMO.D]H # December 5, 1996, 12:49 R Msg comp [DEMO.D]I # December 5, 1996, 12:50 R Msg comp E $ SCHEDULE TYPE/HISTORY [DEMO.D]B21 /QUEUE=R/FROM=NOW-24/TO=NOW/FULL [DEMO.D]B21 ; December 5, 1996, 12:44 R Msg comp 655. [DEMO.D]B21 (1484) step:0 tag:"" param:"" # node:DWS queue:DWS$BATCH entry:322 I strt:December 5, 1996, 12:42 Sts:00030001 CPU:5 Elps:99 IO:252 Flts:1821 Ppg:4675 |
| Previous | VNext | TContents | YIndex |