DSXchange

You could check the umask setting in the ds.rc script. This is now set to a umask value of 002 but it was not set at version 5.x and on some unix platforms this stops one user from creating/importing a job and another user compiling/changing it. (when all datastage users should have full access to e...

A Job with a Px Transformer generates the "VOS2_test_Transformer_2.so" during the job compile. Thus when moving jobs between types of unix machines you have to re-compile the job before you can run it (and expect it to work). Question - Have you re-compiled the job since import? PS: Other ...

External Parallel Routines should be compiled on the DataStage Server machine.

(Ths is due to the fact that Compiled 'C' Object files will differ depending on the compiler (platform/version) used and the options given to the compiler).

How did you compile the object file?

Open the DSX file in NotePad (or any text editor) right at the top of the file you should see: BEGIN HEADER CharacterSet "CP1252" ExportingTool "Ascential DataStage Export" Set the value for CharacterSet to the appropriate value for your Italian environment. (I'm not sure off han...

Check the PATH settings. If $ORACLE_HOME/bin is not included in the PATH (Add via the Administrator) then sqlldr connot be found and the call will fail.

You can write PX Routines (using C/Cpp) which can be used in the PX Transformer. These are not the same as Server Routines (using Universe Basic).

The Sequental File Stage (Import/Export Operator) allows NULL values to be replaced with a VALUE. (using the Column Property -> Nullable -> Null Field Value).

You must Expand the Variable ORACLE_HOME and give it the actual value (ORACLE_HOME = /opt/orasw/app/oracle/product/9i) rather than the reference of $ORACLE_HOME.

If the pre-production and production environments are the same (Same version and patch level of OS) then you won't need to recompile in in the production environment.

I found the info from this web site IBM DB2 Technical Support

Hope this helps.

SQL1390C The environment variable DB2INSTANCE is not defined or is invalid. Explanation: The environment variable DB2INSTANCE is not defined or is not set to a valid instance owner. User Response: Set the DB2INSTANCE environment variable to the name of the instance to use. If you do not know the na...

I think you would need to Login to DataStage as the Same user who has access to the Drive.

Set your variable in your job to $ENV and re-compile

From a unix prompt ...

set your variable in your shell.
cd to the project directory
use /dsjob -run -local

[:)]