DSXchange

Export the whole project into a .dsx file. Use your favorite editor to find occurrences of those strings. The usage analysis, while powerful, doesn't yet go into that level of detail.

The whole trick is to find out what your database NLS settings are and use exactly those setting for the Database stage in DataStage. The rest (almost) automatic. Also, the "View Data" designer functionality should not be used to determine if NLS works or not.

Yes, you can use a BASIC transform stage in a PX job to do this. It can cause performance issues and is generally not recommended, though.

ICONV() and OCONV() do not exist in parallel jobs and are thus, unfortunately, not an option here.

Page 31 of the DataStage Parallel Developer Guide tells you what date mask to use. For the day-of-week in text form you would use the mask of "%eee"

It does work, but there are 2 sections for environment variables in the DSParams and both need to be changed/edited in order for it to work.

I cannot find the eCase, either in the project docs or under my name at support.

I don't know what to add. With an Oracle insert and a array size of 1 I don't see how a row could fail to go down the reject link.

I would suggest looking for a paid-for service for "ASAP" support, this is a volunteer forum.

Could your problem be this IBM APAR?

Can you connect to the web console? If yes, did you configure the installation? Since messages of the type at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException(AuthenticationService.java:1000) pop up several times in the log excerpt, I would look at userids and authentic...

You have been (successfully) archiving the dataset descriptors; but the actual data resides in the location(s) pointed to by the disk resource in your active APT_CONFIG file.

Note that the change only gets triggered after a job runs; that means you could change a job to 2 days that has weeks worth of log information, but that log won't get purged until after the job runs again.

Hmm, then I am not sure what the cause might be. Could it be UNIX access for the DataStage user?

What does "ldd $DSHOME/uvdlls/libodbc.so" return?

If you replace the derivation with a simple constant value, does the job run without that warning? The expression itself does not look like it would cause that error message (I assume you didn't cut-and-paste as there is a sytactical error with parenthesis in the statement).