DSXchange

Yes, it does use a few custom routines. And yes this job is run from a sequencer and its set as "reset if required and run".

The same phantoms are logged in development too. All the rest of the jobs which are very similar to this job run fine. So I am thinking something very specific to this job is causing the issue. I am going to try to activate the server side tracing and re-run the jobs in production to gather more inf...

It runs twice successfully after every compile. I havent quite seen a pattern to confirm that. The log just says Abnormal termination . I looked in the &ph& folder, and didnt find anything unusual except these messages at the time of failure. DataStage Job 447 Phantom 256 Program "DSD.R...

This is defenetely one of the strangest things i have seen with DataStage so far. We have a code that runs successfully in development and fails in production, which is not unusual. But upon re-compiling the code in production and re run, it completes successfully. We have opened a ticket with Ascen...

I know there is a similar post, but I still seem to have some nagging doubts about hashed files. I have been under certain assumptions for so long , doesnt make me feel good to know that I was wrong:( 1. No options checked still creates the file if it does not exist, with the dictionary file contain...

I am giving up hope. Doesnt seem like there is a clean and elegant way to abort a job from the comand line. I will have to go with my workaround plan of masking my master sequence in a job activity and use my wait for done file approach. That works, but I will have to create these timer super sequen...

Even invoking the master sequence with dsjob warning limit of 1 and then logging a warning after timeout didnt work. The master sequence job should abort but it didnt??!![/code]

Nope. That doesnt work. The sequencer continues to run inspite of the exception handler. I think I will have to go with the zero warning approach

Coming to think of it, we use exceptional handlers connected to an abort stage to abort the master sequencers. So to abort jobs, using your dsjob -log -warn might actually invoke the exception handler and abort the job. I will have to try that.

It has to be from the command line because I am having a timer run in the back ground everytime a job is invoked through unix. This timer will check after certain time to see if the job is still running. If it is , then ideally I would like the timer process to abort the job. This is will get produc...

How to abort a job instead of stopping a job from command line. Doesnt look like dsjob has an abort feature. Since the jobs were built to be restartable , a stop will force them to be reset before they can be invoked again.

That is a good idea too. I think my idea kind of acheives the same purpose. I would prefer to have only master sequencer to deal with. Lot of our master sequencers are also built to be restartable. So having two jobs scheduled to run simultaneously in production seems a little more cumbersome than h...

The jobs in the master sequence should run in sequence one after the other. So running independently wont work. The only solution that I could come up with so far is the last solution suggested. To run the master sequence as a single job activity in another super master sequence :) with the file wai...

Hi, I am trying to implement some kind of a timeout feature on ETL jobs. We have a few master sequencers (as in they run other jobs), and each of these master sequence has its own expected average execution time. At times due to numerous factors out of our control, they end up running too long. I wo...

You guys have seen it all. I guess I am a little new to these tasks. Thanks everyone. No, it does take a long time. Critical is that you manage their expectations; they are NOT going to get this at the end of a single sleepless weekend from you. Multiple sleepless weekends fall into the occupational...