Error with $PROJDEF expansion/subsitution

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
dancomfort
Participant
Posts: 3
Joined: Mon Mar 22, 2010 12:59 pm

Error with $PROJDEF expansion/subsitution

Post by dancomfort »

The DS jobs run fine in Prod, but when I try to run them in QA they abort.
All runtime params are set to $PROJDEF in both prod and QA.
When I check the params in the run logs, Prod has expanded correctly.

$FSCM_AS = 2000
$FSCM_IPC_BUF_SIZE = 512
$FSCM_IPC_TIMEOUT = 600
....
$FSCM_SRC_DBCONNECTION = FSPRD90

But when I check the QA log, I see this:

$FSCM_AS = 2000 [$PROJDEF]
$FSCM_IPC_BUF_SIZE = 512 [$PROJDEF]
$FSCM_IPC_TIMEOUT = 600 [$PROJDEF]
...
$FSCM_SRC_DBCONNECTION = FSPRD [$PROJDEF]

The job aborts with an oracle error since there is no database named "FSPRD $PROJDEF".

I searched the archives, but didn't find this error. I'm guessing I've missed a project setting somewhere.

I'm running 7.5.1A on Windows, PeopleSoft EPM..
Three quarks for Muster Mark!
girija
Participant
Posts: 89
Joined: Fri Mar 24, 2006 1:51 pm
Location: Hartford

Post by girija »

Check environment variable in QA. You will see the difference.
girija
Participant
Posts: 89
Joined: Fri Mar 24, 2006 1:51 pm
Location: Hartford

Post by girija »

2. Check this variable in your oracle stage. It is appended the value
anbu
Premium Member
Premium Member
Posts: 596
Joined: Sat Feb 18, 2006 2:25 am
Location: india

Post by anbu »

Do you have connection to Database FSPRD in QA?
You are the creator of your destiny - Swami Vivekananda
dancomfort
Participant
Posts: 3
Joined: Mon Mar 22, 2010 12:59 pm

Post by dancomfort »

girija:
1. I checked the /properties/environment/user defined in administrator for both systems, and they seem to be the same; allowing for prod/QA different names.

2. I'm a relative newbie; where can I check this (append vs. replace)?

anbu:
Yes, FSPRD in the internal name of the FS QA database.
Three quarks for Muster Mark!
dancomfort
Participant
Posts: 3
Joined: Mon Mar 22, 2010 12:59 pm

Post by dancomfort »

The $PROJDEF strings seem to have been a false symptom; it may be a benign results of bundle 11, which we have in QA but not Prod.

The issue turned out to be the database Source DB Connector in DSParams. Prod had FSPRD90, QA has FSPRD, an older version of the Prod DB. When the old db went away, Datastage broke! I changed the Source DB connector to "FSQA" and the job ran.

Both prod and QA databases have the internal name of "FSPRD", which helped add to my confusion.

Thanks to all for their help.
Three quarks for Muster Mark!
Post Reply