DSXchange

Can I know how to replace the database output stages.

I am sorry I was not clear on my previous email.

I am having this issue basically for loading files from input files with large number of data into the database.

The issue is even with loading data from the hash files

WHen I run the Datastage jobs, they are either hanging or aborting.

When I look into the monitor of the jobs which are running for a long time, I see that the time count increasing, but the num rows is still the same. Can I know how to trouble shoot this issue.

[quote="ray.wurlod"]You are also missing a command. The [i]bin [/i]folder contains the executables; it isn't one itself.[/quote]

Can I know what might be the command I am missing

[quote="ArndW"][quote="shyamrai]...it gave a return as "''D:Ascential\DataStage\Engine\bin'...[/quote]
You are missing a "" in the 3rd position[/quote]

I am sorry, it was actually set as 'D:\Ascential\DataStage\Engine\bin

[quote="ray.wurlod"]Control Panel, System applet, Environment command button PATH (maybe Path) is a System variable. Select it and edit it to include the pathname of the DataStage Engine [b]bin [/b]directory (and of the PXEngine [i]bin [/i]directory if you have Enterprise edition). Tip: co...

But still I am getting the same error when I am scheduling it through TWS. But when I am directly executing the batch file, it is running the datastage job.
May I know how is it possible to make it permanent through Control Panel or login script.

I was able to define the path which was not present Check for the Path in command prompt. If you donot find the path where dsjob.exe is present, goto My Computer ->Properties, Advanced Tab -> Environment Variables, look for PATH under Variable and add the path=D:\Program Files\Ascential\DataStage7.5...

chulett wrote:PATH issue, as in the directory where dsjob lives is not in your production PATH environment variable.

I have found dsjob.exe in the path D:\Program Files\Ascential\DataStage7.5 in Production.

I also found it present in the test.

Can I know what should I be checking other than this.

Thanks

[quote="DSguru2B"]You need to design your sequence that way then. Stick in an exception handler connected to a terminator activity. Do not handle the scenario in which the job finishes with warnings, in the conditional trigger. This way if a job finishes with warnings, the control will go ...

You can set the warnining limit in the UtilityRunJob() to 1. So that your sequence job inherits this property and passes it down to the children jobs. This way, even if there is a single warning, your jobs will abort. But I am not sure about the entire design, but then again, thats not the topic of...

The UtilityRunJob in the Transformer is given as the following. UtilityRunJob('SubMasterLoadBWFiles','MeridiumApplicationServer=' : ToSubMasterLoadBWFiles.Meridium_Application_Server : '|MeridiumDatasource=' : ToSubMasterLoadBWFiles.Meridium_Datasource : '|MeridiumUserId=' : ToSubMasterLoadBWFiles.M...

The jobs are designed such that there is a Datastage job(level 3) that is called by the sub master job(level 2). The sub master job is called by the master job.These master jobs(Level 1) are not in Job Sequence but they are run in Server Job. In the master job and the sub master jobs we are passing ...

I have given the following code and this seems to work fine while scheduling through TWS

@echo OFF

dsjob -run -jobstatus -Project -Job

echo ERRORLEVEL %ERRORLEVEL%

IF ERRORLEVEL 1 SET ERRORLEVEL=0

IF ERRORLEVEL 2 SET ERRORLEVEL=0

We are using the batch files and not the shell scripts to call the DataStage Jobs.

I have contacted the tivoli scheduling team and they have said that it will not be possible for them to set up the status on a case-by-case basis. Do you think I should be adding any error handling syntax in the code which I have written earlier so that it would change the status at the end of the j...