Multipule instance Server Job execution

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
actiview
Participant
Posts: 20
Joined: Fri Sep 12, 2008 1:19 pm

Multipule instance Server Job execution

Post by actiview »

Hi,
I have a server sequencer job that is running in a loop, creating invocation name by the $counter.
The sequencer builds of 3 jobs:
1. write to an hash file one record.
2. Simple transformation job reading from DB and writing to another.
this job get a parameter from the function "UtilityHashLookup" to read the record written in the first job.
3. Update status/

most of the times, the process works well. Some times I see that the job starts and finished without doing anything, and the job executed without invocation name.

I think that the problem is in the routine.

Thanks.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What routine? Why not leverage USERSTATUS to pass the value, if you think that's the issue?

ps. UtilityHashLookup() will fail silently if not used properly, test your logic elsewhere to ensure it's doing what you think it is doing.
Last edited by chulett on Thu Mar 19, 2009 8:05 am, edited 1 time in total.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Pagadrai
Participant
Posts: 111
Joined: Fri Dec 31, 2004 1:16 am
Location: Chennai

Re: Multipule instance Server Job execution

Post by Pagadrai »

actiview wrote:Hi,
I have a server sequencer job that is running in a loop, creating invocation name by the $counter.
The sequencer builds of 3 jobs:
1. write to an hash file one record.
2. Simple transformation job reading from DB and writing to another.
this job get a parameter from the function "UtilityHashLookup" to read the record written in the first job.
3. Update status/

most of the times, the process works well. Some times I see that the job starts and finished without doing anything, and the job executed without invocation name.

I think that the problem is in the routine.

Thanks.
Hi,
You dint mention details about the job that is writing to hash file.
But you can think of embedding that logic in the second job itself.
If you provide more details, we can help you.
Post Reply