[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

1092.0. "Dependency job problem." by HTSC04::WILLIAMCHAN () Wed May 08 1996 07:33

Hello,

	My customer has a problem about running the dependency job
	of Scheduler on VMS:

	When job A completed running, job B start - job A and job B
	is dependency job but A and B have no data transfer. When 
	job B completed running it will re-schedule for next.
	Then means A-B-A-B-A-B.....But sometimes (not always); if user
	force to run job B; then it executes job B at once; when it
	completed, it won't re-schedule for next execution but start
	itself (Job B) again. i.e. B-B not B-A-B-A

	Is there any special setup for "force to run" mode?
	User is using VMS V5.5-2, Scheduler V2.0 and VAX6630

	Thanks for any input.

Best regards,
William

T.R	Title	User	Personal Name	Date	Lines
1092.1	more details please	CSC32::G_BURTT		`Wed May 08 1996 12:14`	3
	Could you post what you have the intervals set to on these jobs or better yet the complete job description. If the intervals and dependencies are set properly you should have no problem doing what you want to do.
1092.2	This may help	MRBASS::PUISHYS	Project Leader Scheduler V3.0 for Digital UNIX	`Mon May 13 1996 14:21`	16
	SCHEDULE RUN /RESCHEDULE /RESCHEDULE /NORESCHEDULE Specifies whether or not the to reschedule to job as a result of this RUN command. /RESCHEDULE tells the scheduler that when the job is run, the next scheduled run time is to be calculated, and a (potentially) new start time entered for the job. /NORESCHEDULE tells the scheduler to run this job but no to calculate the next start time. The default is /RESCHEDULE
1092.3	Thanks and one more question.	HTSC04::WILLIAMCHAN		`Wed May 22 1996 08:04`	17
	Hello, Thanks for the reply 1 and 2. Customer just found this happened once. But he want to know how to make sure the job run correctly. Information: the job should run in this order (dependency): A-B-A-B-A-B... then when at the end of job A, he hold job B for some reason, then later on he want B to run again so he release it, then he found job B run twice and then A-B-A-B again. But this just happened once. Any suggestion? Thanks and regards, William