DSXchange

With a zero for the instance? Yes, that will work but looks wrong. Did you read the help for the function?

If instance is less than 1, 1 is assumed.

So under the covers it changes your zero to a one. Best if you just pass a one in the first place.

Hmm.. I think DSX routines are cataloged in all upper case.

The '1' in your example? Or the last argument you haven't mentioned? A bit of advice. Build a simple routine in the Manager to test stuff like this. For Arg1, pass in a filename like 'first.TXT'. Set Ans to the result of your Field command on Arg1. Then Test the routine and see what it returns. Work...

... are just figments of our imaginations...

Read them in a job using the DB2 stage and then use the UtilityRunJob routine (conveniently located in the sdk\Utilities branch) in a transformer.

Discussed here a bajillion times, a search would have turned up the answer.

You need to get your hands on the 'SP2 Patch' for DataStage. Call support to see where in the heck it can be found nowadays...

Have you read the Help associated with the Filter option? You can't just simply 'unzip' anything there, you need to find a way to provide the contents of all files to 'standard out' so the Sequential stage can read the stream of data as if it were a file. If all you want to do is unzip something, do...

You mean you want to strip the extension off the file? Read the help for the FIELD command. Tell it you have a field delimited by a dot '.' and it can return the two fields. You can then slide your date between the two parts and build the new pathname out.

So you have a Folder stage linked to multiple XML Input stages? How many XML Input stages, exactly?

Of course it is being 'called'. The only way that wouldn't happen is if you had the option enabled to run it 'only on successful completion' and the job didn't. You assert that the job is completing successfully therefore it must be executing. So... my assumption here is it just isn't working. And t...

Obviously using the DRS stage set to Oracle... and it is not properly configured. First question would be - have you used the 'normal' OCI stages before at all? Are they configured correctly and working? Or is this the first time you've tried to do anything with Oracle natively?

Again, not possible from this particular bit of code. Seek your culprit elsewhere.

joyson wrote:Here in my env the filter command is disabled.

Rather than seaking another route, why not just enable it? It's just a check box on the stage to light it up and start using it.

Otherwise, you're back to writing Before Job routines or shell scripts and we all remember how much fun that is.

clarcombe wrote:Triggers are set correctly for the flow

This really doesn't tell us anything. It also doesn't seem to be correct or you wouldn't be here.

Please post your triggers, conditions and all. Also please cut-and-paste them, don't hand type them in.

ragunathan13 wrote:actually my req. is, using routines i have to extract the records from db2 table

Perhaps you could share with us why you 'need' to do this, why the requirement? Then we can tell you why you don't want to do it that way and give you an alternative or two.