DSXchange

StringToDate is a parallel function. You need to stick with Server functions in the transform, for example IConv/OConv... but then you could only leverage it in a Server Shared Container or a Server job proper.

Unless I'm not understanding what you mean by 'transform'.

But is it really that simple? The short answer is "yes". Specifically what you are seeing are two hashed files of different types. The single file is static and probably a type 2 while the directory is a dynamic type 30 hashed file and there are actually three files in the directory (one ...

Of course, that's a completely different issue and not what you posted. Did you search here? It's been discussed quite a number of times. One example:

viewtopic.php?t=121008

Did you use a significant volume for your test? Compare the scores?

My understanding:

1. The latter.
2. No.

Out of curiosity, have you actually tried to load the data and had an issue or are you just assuming there will be a problem? I would think the quotes around the strings would 'protect' the delimiters in the data. If that's not the case with the PX Sequential File stage then perhaps try the Server o...

Un-marked.

That just means you ran the executable from the 9.1 directory and I doubt there's anything different between it and the one under the 8.1 directory. I would be curious what environment you have loaded. Did you source the 9.1 dsenv before you executed that command?

metaman wrote:Not sure if Datastage has a similar inbuilt capability

It doesn't but an exact search here will turn up people that have rolled their own, for example here. There are others.

So in other words, yes. Get rid of the DSTranslateCode() function, just pass back the code itself.

How similar? What are you passing back on success, "No error"? If you have the "automatically handle" option checked and a routine does not return a zero then it is considered to have failed.

Sorry, I meant that I had already moved it... this is the proper forum.

Just wanted to get anal and point out that with dsjob you use the "-jobstatus" OR the "-wait" option, not both. Pick one based on the type of status information you want returned.

You probably need to look at pulling it from the job's log using the API (the various DSGetLog* functions) depending on exactly what 'fatal error message' you are looking for.

Have you acquired a UNIX based ODBC driver for MS Access? I don't believe any such thing ships with the product.