Problems with file paths in production environment.
Posted: Mon Dec 08, 2003 11:20 pm
We have a DataStage 7 job running a QualityStage 7 matching job. DS passes in records read from a sequential file, QS finds possible matches in that file, the results are written out by DataStage to another sequential file.
When we deliver this job to our production environment the job aborts, the QS logs indicate the job is looking for files in the development directory path instead of our production path. In development we store our QualityStage jobs in the directory /u01/dsdev/... on production we store them in /u01/dsprod/.... After deploying everything to production the DataStage job aborts and the QS real time log shows the following messages:
When we deliver this job to our production environment the job aborts, the QS logs indicate the job is looking for files in the development directory path instead of our production path. In development we store our QualityStage jobs in the directory /u01/dsdev/... on production we store them in /u01/dsprod/.... After deploying everything to production the DataStage job aborts and the QS real time log shows the following messages:
Why would this job still be looking for files in the /u01/dsdev directory? We have set every QS and DS settings we could find to point to /u01/dsprod such as the QS profile, the QS stage Controls, log and ARD directory parameters. Are there some configuration settings somewhere that we have missed?ipe_exec.sh(16808): WARNING: unable to find env file /u01/dev/dqwork/QualityStage/Projects/SENSCP1/Scripts/CP1SPLIT.env
qsrtserv -f /var/run/qstage/QSRTManager/IAS43/IAS43.cfg -m 3 -s 4
...
ioOpenFile, open: No such file or directory