DSXchange

This has happened several times to different people in this forum. The most common cause is that insufficient access rights are allocated to the user that actually performs the AT function. If you look at your entry, what userid and password have you specified?

Are you certain that this is a Server job, as the subject line and forum indicate Server yet the functionality you have described doesn't exist in server jobs.

In addition to checking your derivations, remember that stage variables don't allow nulls and you might be getting your error there.

There is no case statement in a Transform stage, you need to use an IF-THEN-ELSE construct. There is a Switch stage that you can look into.

And if it isn't XMETA, then can you try doing this same operation from a colleague's workstation - perhaps there is something different on your PC.

The INDEX() Function is correct; but use "INDEX(FKPOSSTR_IN.SEC_CODE,'.AX',1)" instead. The "2" that you used tells INDEX to use the 2nd occurrence position, and if it doesn't occur twice then the returned value will always be "0", which equates to "False".

The output reject link of your Oracle stage should have "sqlcode" as an integer column, is that correct? Are you writing straight to a sequential file or going through another stage?

that makes sense, the "sqlcode" is added in the reject link so that you can analyze the error cause. Which stage is giving this error?

What are your column definitions and it would seem you are using user-defined SQL, so what do you have there?

In this case it might be easier, since the conversion is only happening in one place. What character set is your DB2 set to?

do you have DataStage with NLS installed?

It might be easiest to take this step-by-step with an example. What is a value and datatype of the input value?

The lesson learned is that you should only use the approved methods in the client tools. Revert and try again.

This means it couldn't find your local "dsjob.exe" on your PC. You will need to add your dsjob.exe to your PC environment's path or explicitly code the location into your .bat program.

I can't check this now,but would be surprised if that failed conversion didn't go down the reject link. Perhaps the easiest solution is to use a date type in the DataStage and capture the invalid date in the job.