DSXchange

You should also have the permission to the directory whereever your log file exists.
This needs to be set in the APT file for that project.

Usually MSQL and any other database have quite similar syntax for case statments. You can do that in you SQL as well. The error you posted seems to be that either you are not allowed to use the functions or your SQL is no right. First test your SQL in the enterprise manager of MSSQL or the DB2connec...

If JD EDWARDS has a database, you should be able to connect to their database via the ODBC stage which uses the generic ODBC drivers.

O yea, sorry September. My brains are frozen, i am due to fly out for a vacation tomorrow, so much on my mind.

Yes Ray, ever since dsxchangers have pronounced me dead(remember Jules Renard), i keep coming back to planet earth pretty frequently. Cant leave my dsx buddies alone

What happens when you change the sql type back to decimal and specify the correct length and scale of 2?

That baby blue color text was a real challenge to read
09312006 gave you ******* because its invalid. October here on planet earth has just 30 days.
******* means '*** ** **** **'. Got it

And why are you doing that. Any specific reason of changing it to varchar. Change it back to decimal, with length 17 and scale 2. See what the results are.

opdas wrote:Its like picking a substring in a DB2 table using function substr(column,3,5) , which would give be a substring from character 3 to character 5 of the string.

Actually the OP contradicts his statement. We all just looked at his substr() example

Have you tried working with Craig's suggestion? Try it out.

Seq. file retains the input as its coming in. Thats why you see it the way its fed into the seq. file. Are you sure the .67 is changed to .00 That should not happen, you sure your looking at the right row both in input and output. I dont have access to DataStage so cant test that right now. Someone ...

a big
Sorry, my earlier solution wont work. I overlooked the fact that your on PX.
Sorry.

OR store that value in a hashed file keyed to a hardcoded value and then read that hashed file by UtilityHashLookup() routine in a Routine Activity Stage and branch the execution accordingly.

Sounds really silly, but there is something else thats going on at the back end. Maybe you can get your dba involved and try to find out whats going on. You can also explicity give the select permissiong to the production id by the GRANT command. GRANT SELECT ON <tablename> TO <productionid>

First of all you need to confirm weather its a server or px job. Answers to both types have been posted, so let us know if it worked. My code is only half the answer, then you need to convert it into output format depending upon what your database is, using the OCONV() function. I did not provide th...

use

to convert it into internal format
then use the oconv function to convert it to any format you like.