[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference humane::scheduler

Title:	SCHEDULER
Notice:	Welcome to the Scheduler Conference on node HUMANEril
Moderator:	RUMOR::FALEK

Created:	Sat Mar 20 1993
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1240
Total number of notes:	5017

1165.0. "Wrong Completion Status" by NQOS01::rdodial_port14.32.81.16.in-addr.arpa::MCCARTY (Systems Integration) Thu Oct 10 1996 15:08

I have a job that runs on a daily basis. In the command stream that is 
executed, the last statement is $ EXIT 1  . I once had to abort the job by 
doing an SCHED ABORT. Now SCHEDULER is telling me for subsequent runs that 
when the job finishes, it was aborted which if you look at the log file, it 
did not. It looks like SCHEDULER is reporting the abort status from a previous 
run instead of the current status. Is there any way this error status can be 
cleaned up without having to delete and recreate the job?

T.R Title User Personal
Name Date Lines

1165.1 shouldn't be... RUMOR::FALEK ex-TU58 King Tue Oct 15 1996 15:57 8

T.R	Title	User	Personal Name	Date	Lines
1165.1	shouldn't be...	RUMOR::FALEK	ex-TU58 King	`Tue Oct 15 1996 15:57`	8
	Check the job's output file. Is the $ EXIT 1 statement REALLY executing ? Does the job have a "pre" or "post" function that might be messing things up? Is the completion time of the job (as shown by the scheduler in $ sched show job ) accurate?

    Check the job's output file.  Is the $ EXIT 1 statement REALLY
    executing ?
    
    Does the job have a "pre" or "post" function that might be messing
    things up?
    
    Is the completion time of the job (as shown by the scheduler in
    $ sched show job ) accurate?