Page 1 of 1

debugging

Posted: Thu Jun 16, 2005 2:17 pm
by pandu80
Hi,

How can i debug a sequencer job?.

any help would be appreciated.

TIA

Posted: Thu Jun 16, 2005 5:54 pm
by kduke
What is the problem? Is there too many jobs and it is hard to figure out the order? Is something not running? What is the issue otherwise kick it off ansd see what breaks.

Posted: Mon Jun 20, 2005 2:01 am
by roy
Hi,
you first go thru the director's log and find where things 'went a stray'.
I agree it's a bit of work for big sequences.
when you manage to narrow the suspicious section you can create a copy of it and remove unrelated activities.
then use the director to get what values where used in the entire run that didn't work to your sutisfaction and supply then to any activities left that needs them manually.
then run the partial sequence and go over it.
you might also want to use DSLogInfo() to log any values you want to examine.

IHTH,

Posted: Mon Jun 20, 2005 2:40 am
by ray.wurlod
There is NO interactive debugger for job sequences.

There is no interactive debugger for parallel or mainframe jobs, either.

Posted: Mon Jun 20, 2005 2:52 am
by elavenil
Create a sequence with couple of jobs and test the sequencer. Figure out the problem and apply the same rule to add all other jobs in the sequencer. It is bit difficult to debug the sequencer when you have more number of jobs in the sequencer.

HTWH.

Regards
Saravanan