DSXchange

Post the error.

It's client software, so it goes on individual PCs not the main DataStage server. And installation doesn't require you to do anything other than launch it as it doesn't ask any questions or require any codes, it just installs to the same directory where the DataStage client is installed.

Please don't, Mr Moderator. In DataStage Server edition, it's very easy to process rows and retain only the first & last values of a column by grouped columns in an aggregator stage. I notice this isn't an option anymore in a parallel job aggregator stage. How, in a parallel job, would you most ...

Simply you can add a transformer before hashed file and you can pass null values to the columns ... That is wrong. What you do is set up a constraint expression (such as @FALSE) that allows no rows at all to pass. If you send NULL to a key column you end up with a warning in the job log. You ought ...

my output is this 14913 08:31:00 What happened to the date part? Build a small test routine in the Manager and tweak the code until what comes out is what you want. All you need is one line of code, then tweak / save / compile / test until it works: Ans = OCONV(ICONV(Field(Arg1," ",1,1),&...

Was wondering... just a pathname here, so remove the "ftp" and "server name" parts as the stage takes care of that for you. And you may have problems with the space in the pathname, perhaps try the "short name" for that portion.

:roll: More secrets. Ok, so a stored procedure is the target for this, not an OCI or ODBC stage? Your answer depends entirely on what the stored procedure is expecting... got any clue on that? Meaning, is it expecting a native DATE or a string that it reformats or ??? If it is looking for a DATE the...

Procedures?

Sorry, but min != first and max != last. Wish I knew the answer, but that's not it.

Yes, as a 'best practice' for dealing with Oracle DATE fields I always treat them as Timestamps in the format I noted. So your goal is to transform the original string to one that looks like this: "10/29/2008 8:31:00 AM" -> "2008-10-29 08:31:00" And then wrap that transformed fie...

Completely different problem, and one we could have avoided if you'd mentioned right away this was for Oracle. However, not all that surprising. For that you want YYYY-MM-DD HH24:MI:SS for the mask and a TO_DATE() function in the SQL using that mask. Set the datatype of the target field to Timestam...

I don't see anything wrong, what output do you get from the example input you posted?

Use ":" for concatenation, not "+". And you want the 2nd & 3rd "field" for the timestamp part, so Field(DSLink2.CreateDate," ",2,2) to mean "two contiguous fields starting with the 2nd field".

Post your "full path".

Works just fine for me with your posted data:

"10/29/2008 8:31:00 AM" -> "29-OCT-08"