DSXchange

Hi all Just wanted to update you guys on the development here...... I tried changing the cammand with warn option more than 50 i.e., i increase the number into warn 200000 and it worked the Mode was changed (row/warn limits) = 0/200000 but if i try to make the changes with the script with warn 0 it ...

Ok ..Thank ray and hulett for helping me out consistently... i will report the same to the support provider..Thanks once again

Hi Ray, So i see that it has nothing to do with dsjob.But i could not see the complete message, so can you tell me what is wrong with the command i have passed.... The Mode (row/warn limits) = 0/50 when i run the job through the script and it is Mode (row/warn limits) = 0/0 when i run the sequencer ...

Can anyone please tell me how to make use of DSJ_LIMITWARN in DSSetJobLimit. I have some series of server jobs which is called by a sequencer job.The sequencer job is simply called by a unix shell script. The portion of command that i used to call the sequencer job is "$DSHOME/bin/dsjob -run ${...

ray.wurlod wrote:Try changing the project default. Open Director, choose Options from the Tools menu. ...

The director warning limit is already set to 'no limit'

chulett wrote:Look in the Sequence job's log for a 'Job Run requested (...)' entry and double-click on it. What is the Mode (row/warn limits) ? ...

The MODE(row/warn limit) is 0/50...... I think its not suppose to be like this ... what other changes do i have to made guys???????????

errr.......guys....it seems like i m still finding the 50 warning hard to get rid of.... The code that i used is : "dsjob -run -warn 0 -wait ${ParmList} -jobstatus $ProjName $JobName" but still the sequence gets aborted due to 50 warning....What is the problem ....guys please help me out :x

Thank you all for the prompt reply...I'll implement the changes and let you know

Hi all I tried search option for this topic and found a lot of help which was almost having the same problem as mine but i just wanted to make things clear as i tried all the changes in my unix code but it is still not working. Here is my job details...... I have a sequencer which is calling about 1...

We are connecting the server which is in another place. The other job is the jobs which are created in the same project. After the changed made from the clients side it seems like they are able to run the job in 3000 row/sec now. The changes he made with the array size is 10000 and transaction size ...

The job design is quite simple in nature.The source is an oracle9i and the same is with the target.As far as the the constrain is concern there are only the primary and foreign key constrains. The loading is like "insert without clearing the table" and in other job its like"clear the ...

Hi all, I am working on a project which loads millions of records.Previously i did not touch any part of the array size or the transaction size and though the row/sec was less it was gaining the rate.Now when we showed this to client he made some changes with the array and the transaction sizes..The...

Sorry for that....It was a mistake ...... So finally i think i should use the jobname as jobname.InvocationId for those with multi instance option enabled and leave the rest of the jobs as it is????? Please verify
Thank you all for being so patience

No nothing has changed ..I mean the sequence is not multi insatnce job...What i meant was for the other two jobs which have multiple instance enabled ..Shall i just leave it like that and use the jobname as jobname.InvocationId for those two jobs and the other jobs by their actual name for calling t...

So do you think that i should leave the settings as it is????? The code that i am using in the unix script is something like this: "dsjob -run -wait ${ParmList} -jobstatus $ProjName $JobName.InvocationId" Will the dot seperator (InvocationId) actually recognise the invocation id mentioned ...