DSXchange

Yes, the actual 'Orchestrate' manuals and please don't ask me to 'search the dang forums'. All that turns up are numerous responses of 'search the dang forums', 'request them' or dead links from the ADN days.

So... working linky anyone?

Won't PX do this 'automagically' because (typically) the metadata for the header/trailer records are different and thus they... reject?

Been there.

Not that familiar with a true Grid implementation, so perhaps not everything I've said applies. Others, however, are - hopefully they'll pop in here with more grid-specific Words of Wisdom.

That's just standard UNIX / shell stuff. Pretty much all you need to worry about there is zero = good, not zero = not so good.

I'm guessing these aren't 400+ DataStage TX jobs. 1. No. 2. Yes. In other words, your *scheduler* needs to understand the limitations of your system and not overwhelm it. If that means you need to 'teach' it or lead it by the nose so it doesn't run 'too many' jobs at the same time, then that's what ...

Give that boy a cee-gar!

ReturnValue is the status of the command and zero indicates it ran without error. CommandOutput would capture whatever the command echo'd up on the screen / standard out - in this case your cat'd records.

That's... not how it works.

The only way this job can run 'many times at the same scheduled time' with different parameter values is if it is multi-instance.

Did you try searching for 'JobMonApp'?

I personally wouldn't worry about 'duplicate activities' on the canvas. If it works, is maintainable and doesn't look like it was designed by a spider on crack then it's all good.

You don't "call jobs" in triggers. By "call" do you mean they are linked in the Sequence job?

JobA -> JobB -> JobC

Are you looking for a way to conditionally skip JobB based on a parameter? If yes, I would use a Nested Condition with Sequencer stages for something like that.

Isn't this the same issue as your other post? Your other post at least showed you attempting to use the JobName, here you would send the job handle if it was working correctly. And it's not working because you buried the variable name in a string. You'd need to break the string around it and concate...

The answer is... depends. Without knowing exactly what needs doing, it's hard to give very specific advice. Properly leveraging hashed files is key. Don't try to build one huge mongo job that does everything, think modular and break the processing up into logical segments. Your last job would still ...

Check the DateGenericToTimeStamp routine in the sdk branch. You may be able to use it directly or copy it and make it your own.

I'll wager your quotes are being stripped...