DSXchange

Where would you be trying to use this command?

input, output, transform etc ?

Hope this helps a little ... DB2 Error codes ... SQL0804N The application program parameters for the current request are not valid. Reason code "103". SQL0804N The application program input parameters for the current request are not valid. Reason code "<reason-code>". 103 The len...

I have given the exact library path (-/home_dir/somename where the routine is existing), while creating the routine. I set environment variable LD_LIBRARY_PATH to /home_dir/somename:/apps/Ascential/DataStage/PXEngine/lib:/opt/oracle/product/9.2.0.1/lib32:/apps/Ascential/DataStage/PXEngine/user_lib:...

You don't "need" any shell scripts for PX as shell scripts won't support the parallelism and thus performance that PX can offer. Although saying that, you might want to use shell scripts to start jobs using "dsjob" that you can schedule using "cron". Also start reading ...

If the job compiles (use force compile to be sure) then DataStage can find the library file and I expect the problem will be with the way the compile of the library was performed. You could Look at the compiler options in the DataStage Administrator and then use these options when compiling the Exte...

(1) I have checked the Env. variable value for $APT_CONFIG_FILE and it is :/detld1/etl/ascential/Ascential/DataStage/Configurations/default.apt Assuming that the Colon at the start of the file path is not in the APT variable. ;) Always try a force compile when you have transformer problems to ensur...

Then again this might have problems with the 'PM' part of the data.
How about reading the data as a Varchar and then using a Transformer to apply the function StringToTimestamp(InDate,"%yyyy-%dd-%mm %hh:%nn:%ss") as noted by ArndW.

You can set the input (Or Output) column format in the PX Sequential file stage.
If you define the required column as Type TimeStamp (rather than a Varchar) then on the format tab (SEQ file stage) set the property for [TimeStage->FormatString]

There MUST be a valid CONFIG.APT file for the transformer to compile. The APT file you use can be a simple 1 node setup and does not have to be the APT file used in the Runtime/production environment.

(I think later versions of DataStage may have lifted this restriction)

umask may or maynot be set in the ds.rc script depending on the Unix platform. Run <DSHOME>/bin/uv -admin -info to find the script location, and check the umask setting at the top of the script.

NB: If you change this script you must stop and restart DataStage

XML Pack 2 is part of the server side RTI install
(I guess your looking at the client install software?)

You can't without using a server shared container ot the Basic Transformer on the Parallel canvas. (except for before/after routines) Either way your mixing server and parallel which can reduce the performance. For best performance you would be best to write a builop/PXRoutine that does the same task.

I don't beleive a remote connection as such is suppported. You must configure your local DB client to talk to the remote DB2 server. (This is a DB2 setup issue rather than a DataStage issue). DataStage then connects to the local client in the same way as you have already configured.

Have the server resources changed?
Mabybe you only see the problem now due to machine resources being used by another process?

I think SubStrings is a Server Function and not a Parallel function.