Problem(Abstract)

Migrated Parallel job that has been imported and compiled on the new Information Server will recompile without error even when the env var APT_CONFIG_FILE is set to an incorrect/bogus location.

Symptom

After initial Save and Compile of the imported job, subsequent change to APT_CONFIG_FILE to incorrect locations will still allow the job to compile successfully. Running the job will cause the job to fail as the APT_CONFIG_FILE is incorrect.

Cause

DataStage uses the Config file to compile the Transformer based stages within the job and create the objects from these stages.
When you then change the config file to an invalid location, and compile again, DataStage notes that these stages have not changed. Therefore it does not recompile these stages to create new objects (as nothing has changed). DataStage generates new osh code and says that the job has 'compiled successfully".
.
The Config File is only used when a Transformer based object needs to be compiled and generated. If there is no new Transformer based object file to create, the APT_CONFIG_FILE is not used in job compilation. Then when the job runs, since the APT_CONFIG_FILE is incorrect, the job will still fail.

Diagnosing the problem

Import in a Parallel Job, Set the APT_CONFIG_FILE to a valid configuration file. Save and compile the job. Then reset the APT_CONFIG_FILE to an incorrect location. The Parallel job will still compile without any error messages but the job run will still fail.

Resolving the problem

Doing a Force Compile on Parallel job will cause everything within the job to be recompile, including the Transformer which will flush out all issue which can be corrected. 
Site assistance
Translate this page: