DSXchange

You create a generic routine to call DSGetLinkInfo for any completed job and then leverage that with a Routine Activity stage in a Sequence job. Pass it job,stage,link at runtime.

Any 'improperly designed' database object can cause 'issues'. I think triggers generally get a bum rap with campfire lore suggesting that they are some kind of evil boogeymen used to scare young DBAs. Triggers are just fine when designed and used properly. First you need to clarify exactly what it i...

Works fine for me on 7.5.2. Use the "..." External Parameter Helper to pick the right value from the Start Loop stage rather than typing it by hand. Should end up looking something like this:

#StartLoop_Activity_Stage_Name.$Counter#

What's your exact "7.x" version of DataStage?

Other than what I posted? Apparently not, and I'm not sure many businesses have deployed SP3. If what worked for me didn't for you, then it seems to me that you either need to see about rolling back SP3 or contact your official support provider for a patch / workaround, see if it's a known issue.

We know.

A little OT but you should be installing 8.1 not 8.0.1. IMHO.

My journey down that path documented here: viewtopic.php?t=127425

As noted earlier, the only way to know for certain would be to have support analyze the core dump.

Was wondering... don't think I've ever actually used the internal one but have shelled out and used the O/S sleep function without issue many (many) times and places.

You're probably not passing the parameters correctly. Hard to say without proper details. And in your script you either need to 'cd' to your source location or use a full path.

Hi Chulett The Updation of environment variables is for our surrogate key approach as outlined below http://it.toolbox.com/blogs/dw-soa/surrogate-key-generation-in-datastage-an-elegant-way-22482 Hope this clarifies... Hmmm... it does, thanks. Working routine code should really have been posted alon...

Right, BINDSIZE and READSIZE must be the same. How 'fat' are your rows, perhaps they need to be larger? Regardless, this is strictly a sqlldr issue so your DBA should be able to help you figure out what's going on and get it working 'properly' for you I would think. I really need to get my hands on ...

That is a PX variable, not one for Server. And the XML stages have a size limit on files they can process, looks like you've found yours. Any chance your file can be delivered in smaller chunks? That's a pretty unreasonable size and even the wunderkinds at Google put a limit of 100MB on the XML file...

ROWS does control commit points in a Conventional load but you may be overriding your setting by also including BINDSIZE and READSIZE. Try just using ROWS without the other two, it will then calculate the others appropriately for the bind array from what I recall.