DSXchange

First question would be - have you searched this forum for 'vertical pivot'? The technique has been explained quite a number of times.

I have thought about doing what Craig had mentioned... But, its a requirement that enforces us not to have a cross application dependancy at the scheduler level directly... Sorry, but this kind of stuff bothers me. Who came up with this 'requirement'? Push back - this is exactly why your company bo...

Good to know. Wasn't sure if 8 changed things enough such that the MCM no longer worked.

Not quite. The Run dialog window will always pop up when running manually from the Director. However, you can turn off the prompting of individual parameters through the option Ray mentioned.

Guys, problem solved.

mc_harsha - please mark the post as Resolved.

In other words you'd need both clients installed into separate locations. Before 8.x you would also need the 'MCM' or Multiple Client Manager as well as only one client can be used at a time. Anyone know if this is still possible with 8?

Arnd - the eCase seems to be specific to passing a single quote, as in one quote not two or more. And it says it breaks the next parameter so I don't think it's applicable here. This is just your classic case where DataStage strips quotes from parameter values. OddJob - read the examples more closel...

chulett wrote:That one is specific to XP's Service Pack 2 and not being able to open stages. There is yet another patch to address Designer crashing in Sequence jobs.

Ask your official Support provider about it. If I can find the eCase number for it I'll post it later.

I'm creating line numbers for each new batch. I find KeyMgtGetNextValue as appropiate function. Details always help. Actually, that's a totally inappropriate use of the function, no wonder it's so slow. All you need is a couple of stage variables, one to detect the 'group change' when the batch num...

ArndW wrote:Use "#VAR#". Better yet...

Even more better yet, use a more meaningful variable / parameter name.

Why go through all those gyrations? When Autosys completes running the 'external job' successfully, have it trigger the DataStage job next. Done.

Said technique is only valid if your process is guaranteed to be the only process creating new records in the target while it runs. We use a slightly modifed version of the Concurrent flavor of that routine and have no problems getting it it process multiple 1000 rows per second, so not really sure ...

One option that comes to mind involves having to build a dependancy within autosys scheduler so that when the autosys job for the external job completes, we can trigger the master sequence datastage job from the autosys. But, doing this would mean that we would have a very tight dependancy with the...

Make sure you understand - not double quotes but two single quotes.

Only whatever limits your underlying email system enforces. Check with your System Admins.