DSXchange

The Parallel Job Developer Guide lists the functions.

Dates and times are NEVER stored with a format in databases. They are stored in binary form and only converted to a display format when extracted. Your problem is not in the database, but the settings when viewing the data. If you are using SQL to view the data, just use TO_CHAR() function with what...

No, stored procedures are in the database and Server code is in the DataStage server engine. You can call stored procedures (or pretty much anything on the command line) from Server routines.

Remove DataStage from the equation by manually doing a sendmail from the command line - does it still create an error or does it work?

IBM 01142 is an EBCDIC code page. I was not aware of SQL Server running on an EBCDIC machine. This is perhaps the source of your problems.

SORRY! I looked at the time and ignored the date portion.

So what is IBM 00142?

VarChar(32) is a bounded field, Varchar() is an unbounded one.

Rumu - you waited a whole hour before bumping your thread, what paid-for organization has response times like that? DataStage is volunteer and most members are in the USA, where it is still 2AM on Monday morning.

What page is IBM 00142, all I found in Google was a reference to EBCDIC

I suspect permission issues.

What user are you using for DataStage on the AIX server? login as that user to a command line and see what the permissions are in the $DSHOME directory.

Of course there is a possibility. I would not use stage in that server job, but put all the BASIC code in the Job Control section

The DS routines required are DSGetProjectInfo(), DSAttachJob(), DSDetachJob(), DSGetJobInfo().

I don't think you have understood the issue. Date and Time field have no format. None. When you wish to view a Date or Time the displaying program sets the format. So, once again, what program are you using to display the value? sqlplus? DataStage? Oracle SQLDeveloper? TOAD?

change the import for C to have only 1 column, does it compile?

What program are you using to display the date? The date setting for that program need to be changed to use the correct format.

In that case, post more details please. Remove the Column import stage from the job flow - does it compile? If yes, add a column import and slowly start adding fields, compiling each time until the error occurs.

Write an SQL script that does a bulk load and execute outside of DataStage and compare runtimes. I am pretty confident that they won't run in similar times - again, look for a cause outside of DS first.