DSXchange

Everything here is a question, so please come up with a better subject in the future, something germane to the question being asked. And 'Hi' isn't really all that helpful as Additional Info.

The Filter command is meant to be used to replace how the stage gets its input. Rather than reading a file directly, you supply a filter command that outputs something to 'standard out' and the stage will read that stream as input instead of opening a file. So while you would still put the file to w...

What was used to 'zip' them? Was it zip or gzip or something else? Regardless, they should all have help built in and usually you launch them with -h for help. For example: $ unzip -h UnZip 5.52 of 28 February 2005, by Info-ZIP. Maintained by C. Spieler. Send bug reports using http://www.info-zip.or...

Under UNIX I'd be looking for the job process / PID and killing that, for Windows I've no clue how that would be done but it's all from outside of DataStage at the O/S level.

Find the process and kill it.

Again, comes with it - tutorial, pdf manuals, the whole nine yards.

IBM can. And luckily, they actually do - there's an Installation & Upgrade Guide pdf on the media for that express purpose.

There's no setting for this. Does this happen to just certain people or to anyone who connects to the project? Usually that's a client side problem, corruption or lack of memory related from what I recall, but it sounds like it's an "everyone but only in a specific project" problem. Odd.

OK. There is an Idle Timeout value per server, perhaps yours is set to 15 minutes? Other than that, we'd need a lot more information to be able to help you.

Well, there's certainly nothing wrong with the look of the crontab entry. Take your problem to an SA, see if they can help troubleshoot it. You could also add some 'breadcrumbs' to the script to check if it is indeed not even starting or failing somewhere inside the script after it starts. Unless yo...

Welcome Mr Todd. :D I thought there was a TAG for this, but... create a custom routine that takes a date and passes back the day of the week by name. Use OConv for this with a 'D' or Date conversion code - specifically 'DWA' to return the full day name or 'DWB' to return the 'abbreviated' day name. ...

Out of curiousity, what is causing the log growth? If there are a plethora of warnings being generated, could not the job be modified to tone them down or perhaps eliminate them?

Perish the thought. Besides, I'm sure that was the first prong of the attack on the problem, people only come here as a last resort when all other avenues have been exhausted... right?

It's not triggering the script when? The second entry means run every day at 1:30 in the afternoon, is that when its 'not triggering'?