DSXchange

Go to the job control tab in the Sequencer job and look for your job name in the source code. You should see a line that uses the DSSetJobLimit API to limited the number of warning messages. The token DSJ.LIMITWARN is used to control the maximum number of warning messages prior to starting the job. ...

Fixing your weekly load process and fixing your already loaded data are two different problems. Fixing the weekly process is easy and you probably already know how to do that. Fixing the existing data is probably going to be fun. In this case you're going to want to build a throw away process. You s...

Maybe I'm being too harsh, but you really must focus and realize that your last two queries have been incredibly broad and we can't even begin to answer them. Can you please post some example at your current implementation where you need "recovery concepts" applied?

I have looked at your previous posts and see a trend where you seem to be attempting to gather "talking points" about DataStage. I read every one of your posts again and believe you can't possibly have much experience with this tool. You have requested answers that can't possibly be given to a novic...

Try using "eval dsjob ...". We found that the quotes weren't being honored. Check out this script which shows a method for launching and monitoring a controlling job:
http://www.dsxchange.com/viewtopic.php?t=85578

Export the job to a dsx file. Then, delete the job. Then, import the job. See if that fixes it. Make sure you're not even close to running out of disk space on the project file system. Baaaad things happen. If this still doesn't fix your problem, I know it sounds cheezy, reboot your PC. You could be...

Start with learning the Sequencer. There's a tutorial on the CD, as well as ample documentation. Start but creating a Sequencer job and adding a job activity stage. You'll quickly grasp how the Sequencer can run a job, as well as reset it if necessary. You'll be able to link jobs into a series so th...

chulett wrote:

kcbland wrote:Obviously the error is in the shell script.

Possibly, but not necessarily.

Okay, pick that nit. But, the solution is going to be in the script, as well as all troubleshooting. So, my statement in spirit, is correct.

No it is not after job routine that calls the reset job but after completion of the job once again we are checking the status and reseting the job through the Routine and running the job once again. Hope this is fine. No, it is not fine. A job cannot use job control APIs on itself, you need to eith...

Your doubt is not correct. The Sequencer uses the same API set to run Server as well as Parallel jobs.

You have retrieved data in a column that exceeded the specified metadata.

DataStage on Unix simply uses cron, on Windows it uses AT. If you need more flexibility, you need to write your own scheduling system. You can write a script that runs your job, then adds the next entry to cron for execution 2 minutes later. You can do anything you want.

Obviously the error is in the shell script. The problem you are encountering is that DataStage jobs run as your userid, but using the environment of the server engine. You need to verify the contents of the environment are what you shell script requires. As easy way is to put 'env' in to the shell s...

You have to make sure you have the version of 7.1 that has the 64bit capabilities for Sequential and CFF stages. I have a customer who uses RedHat and required patches to get it to work after logging GTARS with tech support. I imagine that's in the 7.5 product by now.