It is currently 17 Aug 2017 3:42


Post new topic  Reply to topic  [ 3 posts ] 
Author Message
PostPosted: 18 Jun 2014 5:12 
Offline
Nouveau
Nouveau
User avatar

Joined: 08 Sep 2010 12:00
Posts: 73
We are deciding to use either CONDITIONS or FORCE for our standard way of starting a dependent job when a prececessor has completed ok.

Under what conditions would FORCE be preferred over CONDITION?

Why both methods?

We believe FORCE overrides CONDITIONS if both are used on same job?

Pro's and Con's of using each.

Thank you,

--Goo


Top
   
 Post subject:
PostPosted: 24 Jun 2014 5:19 
Offline
Nouveau
Nouveau
User avatar

Joined: 24 Jun 2014 12:00
Posts: 1
We have been using Control-M since the Old 4th Dimesion days, our thought process behind force vs conditional subsequent processing is built around the job design, if something executes on a set schedule, we used a schedule for the definition, if the process/job has conditional programatic design, we used a Force, so if Job (A) would get a CC=4, forcejob (B), but if Job (A) gets an CC=8 job (B) is not executed. The CON's of forcejob is that pre determining your daily workload schedule will not identify FORCEJOB's. In additional if the (MAYBE) condition is utilized as part of your scheduling, the job that resolves these typically are part of the daily refresh process. We have because of multiple forcejob conditions/situations built into our schedule where we needed the (MAYBE) resolve process to execute mid stream in some of our schedules, this has posed no problems and solved our specific need.


Top
   
 Post subject:
PostPosted: 02 Jul 2014 2:20 
Offline
Nouveau
Nouveau
User avatar

Joined: 14 Jan 2010 12:00
Posts: 58
Pros - If you have long jobstreams and some jobs that get ordered do not run on the same day. Can save on license cost by changing to force as license is calculated on the number of jobs ordered.

cons - Jobs defined with the force option will order if you force order the job containing the "force". They will order again when its dependent job finishes. Example. Job A will force job B when it completes successfully. Job A has a calendar to only order on Mondays. You need to re-run job A on Wednesday. It must be forced ordered due to the calendar. When you force order Job A, job B will also order. If you do not catch this and then allow job A to run, it will force order job B again. Now you have 2 Job B's in your schedule which can cause alot of problems. This is a very simlpe example. What would happen if you force order a job stream with hundreds of jobs containing many "forces". What if the person that force ordered a job stream is not familiar with the jobs that have "force". I prefer to use ctmorder in a separate job block over the force order option.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 3 posts ] 

All times are UTC+02:00


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited
The site created by Franck YOT. Images, logo, content and trademarks about Control-M products are property of BMC Software.
All the comments are property of their posters. Images, logo, content and design are © copyright by Scheduler-Usage.com. All Rights Reserved