DSXchange

I don't know... multi-instance jobs typically have to be designed with that capability in mind. Checking that by default allows you to run the job as a multi-instance job when that may not be appropriate. To me it kind of falls into the same category as including job parameters that nothing in the j...

I know... only mentioned it because you said the 'U' word.

Windows server, DOS commands.

EXECUTE "CREATE.FILE SDKSequences 2 1 1" FYI - This is from a Version 6 server.>> I tried to find this hashed file and found the name at "E:\Ascential\DataStage\Projects\PROD\SDKSequences", but it doesn't look like a normal hashed file to me. Am I missing something. A little extra hint would be app...

And include the real Trigger values, not something you've typed in by hand that is close. "$JobStaus>=0 and $JobStatus <=2" is invalid syntax for a Custom trigger and would not even compile.

Any information? One such source would be all of the postings in these forums from other people facing the same issue. A search on your error message should turn up quite a bit of information to get you started.

A couple of problems: There's no such thing as a null in a Sequential file, those are empty strings... and not the same thing. A null can never equal anything, not even another null, so your lookup will never succeed with those values. I'd suggest substituting another value when you see NULL, someth...

A better question would be - why is it generating any warnings? Unlimited warnings is not something I would allow. For whatever that is worth.

Where/how did you set the warning limit for this scheduled job? And by 'scheduled' I assume you mean cron via the Director interface, yes?

Define 'screwed up'. Usually that means it is way too late to be taking backups...

Most of the time, yes - but there are more ways then one for a job to fail. Never mind the fact that there is no advantage to that approach over the Unconditional trigger, only negatives.

I referred to all of your posts before replying, always do. My Guru friend, please don't try to code in something 'Unconditional'... that isn't. It only covers three of the many possible outcomes a job could have. Here the issue is that the Unconditional trigger is getting triggered only when the Jo...

That suggests your project is corrupt. Have you every 'reindexed' a project? Worked with the DS.TOOLS menu? That would be the suggestion for a next step. Search the fourm for 'reindex' or DS.REINDEX as there have been many posts on the subject explaining the process. Basically, you kick everybody ( ...

I want to write it as a Subroutine.. any help!! Ah... you need to mention little details like this, as the 'rules' are different between the two types. And I should have noted you parsing the InputArg - that's a big clue. A 'Before/After' routine takes only one input argument and can only return a ...

Make sure your dates are in an ISO format, then a simple compare will work: YYYY-MM-DD or YYYYMMDD, for example.

On job1 success or failure I want to trigger the routine and onsuess of job1 I want to trigger job2. Why make it more complicated than it needs to be? Dump the custom trigger. Two simple triggers will work: For the link from Job1 to the Routine - 'Unconditional'. For the link from Job1 to Job2 - 'O...