DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
poorknight
Participant



Joined: 15 May 2018
Posts: 1

Points: 12

Post Posted: Tue May 15, 2018 3:58 am Reply with quote    Back to top    

DataStage® Release: 11x
Job Type: Parallel
OS: Unix
Hi,

I'm looking for a recommendation on how be to inhibit the execution of a sequence or schedule. On-site we have a maintenance group that have a habit of just stopping processes.

The current thinking is to have a 'stop file' resident in a folder and stop the start of sequences if its there. I can see the reverse (wait for file), might work but I'm just after ideas on any better options.

All help gratefully received.

Thanks

_________________
poorknight
qt_ky



Group memberships:
Premium Members

Joined: 03 Aug 2011
Posts: 2827
Location: USA
Points: 21429

Post Posted: Tue May 15, 2018 5:07 am Reply with quote    Back to top    

The Wait For File Activity stage supports either way--waiting for a file to appear or disappear. So you could have it check for a 'maintenance file' and wait for it to disappear. Just be sure the team understands having the file present won't stop any jobs that are already running. Sounds like they need to be severely disciplined...!

_________________
Choose a job you love, and you will never have to work a day in your life. - Confucius
Rate this response:  
Not yet rated
FranklinE



Group memberships:
Premium Members

Joined: 25 Nov 2008
Posts: 727
Location: Malvern, PA
Points: 6904

Post Posted: Tue May 15, 2018 7:43 am Reply with quote    Back to top    

Disciplined, or punished? Razz

I tell my infrastructure support people that they have two choices: do some planning and announce any "outage" in advance, or watch me do a verbal scorched earth routine.

It should be very simple. The system is in use, or it is the private playground of the maintenance guys. One cannot have it both ways. We had a similar situation in our non-production regions at one point, prompting one developer to label it The Wild West, and it didn't get resolved until someone got a word in edgewise at a budget meeting for how much it was costing us in both resources and missed deadlines.

The file thing is a cheap and dangerous substitute for automated scheduling. If the jobs are dependent on hardware being available, any scheduler worth buying will have an on-off "switch" which will automatically hold jobs in any scenario where maintenance must be done. Making the developer code for that contingency is like making the IT team hire someone to guard the electrical outlet in case someone might blunder by and pull the plug.

_________________
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson

Using mainframe data FAQ: http://www.dsxchange.com/viewtopic.php?t=143596 Using CFF FAQ: http://www.dsxchange.com/viewtopic.php?t=157872
Rate this response:  
Not yet rated
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54431
Location: Sydney, Australia
Points: 295208

Post Posted: Sat May 19, 2018 7:48 pm Reply with quote    Back to top    

What Franklin said, redoubled.

_________________
RXP Services Ltd
Melbourne | Canberra | Sydney | Hong Kong | Hobart | Brisbane
currently hiring: Canberra, Sydney and Melbourne (especially seeking good business analysts)
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
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 vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours