DSXchange

Hi Rob,

We access DataStage 7.1 client components using Citrix Metaframe XP.

The performance is very good.

HTH
--Rich

Hi Somu,

What is the data type of the 2 columns. If it is varchar then you have to specify the null field value as ' '.

HTH
--Rich

Hi Seanc,

You cannot have 2 orchestrate functions in a single specification. You probably have to use the Transformer in this case.

HTH
--Rich

Hi,

Did you do a search. We had a discussion few days back.

Check if this helps.

HTH
--Rich

Hi Hadi,

A Job Sequence is a server kind of job and is capable of running both server and parallel jobs as job activities.

Yes you can execute the server routine using the routine activity.

Activities are nothing but stages in the Sequence Job

HTH
--Rich

Hi,

Have you registered with Ascential Developernet.

There are some downloads such as this one.

Maximize_Ascential_for_SAP_09_08_2004.zip

There are also some white papers here.

http://www.ascential.com/litlib/index.html

HTH
--Rich

Hi Raj,

Did a web search and this is what I found.

http://www-128.ibm.com/developerworks/f ... 298&cat=19

HTH
--Rich

Hi Sam, By default the previous stages would have a setting of propogating the existing partition to the following stages. But you would have defined a new partitioning for the following stage. So DataStage gives a warning stating that the existing partiton cannot be preserved and rather the new par...

Hi,

Are you doing some kind of partitioning in the input?

Are you using the configuration file with multiple nodes for running this job?

--Rich

Hi,

Check this link

http://www-03.ibm.com/certify/certs/iisdwsdev75.shtml

HTH
--Rich

Hi Kumar, One fine day the environment had some changes and we had the same kind of library problems that legendkiller has. We compiled the job 'n' number of times but in vain. Nothing happened. Then we were advised to do a force compile. After we did the force compile the job ran normally as it sho...

Hi legendkiller,

Do a Force Compile and then run the job. If the problem still persists do as advised by Arnd.

HTH
--Rich

Hi Yogesh,

Most of the time this problem occurs because of invalid derivation for stage variables or because of improper use of Environmental variables.

HTH
--Rich

Hi csimms,

Are you using the $APT_CONFIG_FILE environment variable as a job parameter? In the job parameter list move $APT_CONFIG_FILE parameter to the top of the list.

HTH
--Rich

Hi,

You can view the configuration files from Datastage Manager-->Tools-->Configurations. Also you can check the job log in the Director. It gives the configuration file used, the number of datasets, the number of operators and the number of processes.

HTH
--Rich