DSXchange

Can you do a "View Data" on the Header file?
You cant you use a sequential file for the same?

You can call below script in your after job subroutine for capturing Warnings from Director Log in a text file . $DSHOME/dsenv PROJDIR=<YOUR PROJECT DIRECTORY> cd $PROJDIR JOBNO=`$DSBIN/uv "select * from DS_JOBS where NAME='<JOB NAME>';" |grep No.......... | awk '{print $2}'` $DSHOME/bin/u...

Try this SQL in your routine

You need to be logged in as Administrator to do this...
One mere thing..you can upgrade this license even if the license has expired.

Saravanan,

We have done this.
After upgrading Server license (thru Administrator) you need to restart DS Service from server end...thats it.

If your license has expired...DS will automatically not allow you to login...So actually there is no need to remove the key.

If you have got an extension to the license from Ascential you can upgrade your key (of course before the previous license has expired )

I have this condition in DataStage 7.5 and it works fine (Its only for the master file though..not for the lookup file)

Christina Lim, You seem to confusing parameters set in Administrator and dsenv dsenv is for This script is sourced by the DataStage dsrpcd daemon to establish proper environment settings for DataStage client connections. This script may also be sourced by bourne shells to establish proper environmen...

Thanks, Vmcburney for the statistics, I was looking for something like that. So when you have to use a transformer (not replaceable with a single stage); you have no choice but to use a transformer. Hope in the next DS version, we dont have to hear this: In the Ascential World 2004 tech sessions on ...

I know its best to avoid a transformer; but how bad is a transformer?

Does a transformer simply by being in the job affect performance or does records passing through it hit the performance?

What exactly are you aggregating on...if its on a same key value...then you can do it in 1 aggregator itself....then you can directly use a transformer stage for adding the 2 cols.

or if you are having both o/ps from aggregators of same format then use:

Its only when you view data in DS will you see the dot.
If you write it to a file, it wont be a dot.

(But be carefull when converting decimal to char the dot might persist...hint: do a proper substring)

Just wanted to know....what can be input (looked up) by a lookup stage. It can obviously be a file/table; but when I added a lookup to a file and then looked up to another (see below code) no records matched in Lkp2. It is obvious that by the time Lkp2 tried the lookup no records were ready from Lkp...

I get this problem with every job that contains a BASIC Transformer stage....I havent tried the node configuration though...I tried to change sequential/parallel option in BASIC tx but still got the same error. Anyway we will be moving to a different env from now.....will check out this situation th...

I am not doing anything in the transformer. I am just mapping i/p cols and o/p cols...I think the real problem (I dont know what it is...hence this query) is not evident in the log.