DSXchange

Time to involve your official Support provider, it seems.

Same way should work, just attach to the specific invocation id.

dsdev_123 wrote:>##E TOIX 000049 14:30:51(000) <CommonFormat_File_PLS_PhysicalStocks,0> Unable to open /bi/busdata/dwbi/mna1/_lgi/dsdata/EUR/MNA/1/data/output/PhysicalStocks/PHYSICALSTOCKS.YYYYMMDD.dat: No such file or directory.

<- (light)

Disagree, but that's the nature of opinions.

Yah, that's the answer - just delete all of the before and after job routines.

Make sure you don't actually need them rather then just don't understand what they do first!

Welcome. :D

You obviously have a custom (i.e. home grown) routine called CheckLogForErrors running as an 'After Job' process. It aborts the job when things don't "reconcile" it seems. Seek your answers there.

That or create a Sequence job and don't link the Job Activity stages together.

Modify the generated code, move all of the 'DSWaitForJob' calls to the end so that all get started and then it waits.

Fully path your .run file. That or 'cd' to where it lives first.

You don't. Job names are unique, so that's all you need to run them.

No one is laughing, but we are wondering if you've read the documentation? Searched the forums? There are tons of examples of dsjob syntax here and a plethora of conversations on the subject. Running 'dsjob' without any parameters will give you the expected 'usage error' and dump the proper syntax t...

You could simply update the definition manually. Or delete the old one and reimport but that would hork your metadata linkage, I would think.

And they are different, so having 2.0 installed doesn't mean you also have 1.1 installed. Don't skip that step.

Amit_111 wrote:If No, Is there any alternative to this Problem?

Dump the SP and build the logic directly into your job. Is there something magical it is doing that can't be done in your job?

Dearth. Cool word. The opposite of plethora.