DSXchange

The help simply says "Note that the meta data on all input links must be identical, and this in turn must be identical to the meta data on the output link". Interpret that as you will, but I don't see the problem with ensuring everything is identical including the column order. Drag the link, Luke.

Promote it from Version Control to Production, either at the same time as the job(s) that use it or before in a separate step.

In my stored procedure. iam just passing the Input parameter and it wont return any OUT parameter.So if the procedure fails due to any exceptions,then will my Datastage Job will also get aborted at the same with the same exception been trapped in datastage log.Or to have this functionality we need ...

It should work fine if you 'just move the variables', I've done this many times. Note that there are two sections (and entries) in the file for each variable.

XE is no longer used as a product bundle name, even in the pre-8.x world. It was simply the Server product bundled with MetaStage.

There are a couple of recent threads on this very topic, perhaps some of the principles from them could summarize the options here?

http://www.dsxchange.com/viewtopic.php?t=117173

http://www.dsxchange.com/viewtopic.php?t=117096

In other words, at the very least post your 'dsjob' syntax. Or the entire script if you like.

How many parameter markers are in your SQL? You'll need the same number of columns defined in the DB2 stagte as well.

There are several solutions for this, depending on if DataStage or Oracle should manage the numbers. You could leverage an Oracle Sequence object, for example, in addition to what Arnd posted.

BizIntel_LH wrote:blocking out information this way makes me angry - it's not the way I would try to get more money from the users

Umm... more money? This isn't being run by IBM, you know.

Right, setting in the dsenv file makes it a part of every projects environment and removes the need to set it up in the Administrator. Unless you need to override it in your jobs, in which case I would suggest creating it there with a value of $ENV. For Oracle, the two values I've found need to be s...

Nice. Had pondered this briefly today and hadn't come up with anything.

I got 8 hits when I searched for C Stage PlugIn function "Run" required, did none of them help?

eostic wrote:Make the datatype varchar.

I would think that this is the key piece of advice here.

Sorry, can't provide any specific help as I really haven't had to deal with the CFF stage or mainframe files in DataStage. Did in a past life, however, pre-DataStage. I really should stay out of threads like this.