Sequencer Controller problem: Unhandled failure

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
datastage
Participant
Posts: 229
Joined: Wed Oct 23, 2002 10:10 am
Location: Omaha

Sequencer Controller problem: Unhandled failure

Post by datastage »

I have a sequencer that is aborting at the end of it when it calls a routine activity (actually the routines runs, then the sequencer aborts). What I have a sequencer stage that has a link from every job activity the sequencer calls. After all have completed it moves on to a nested condition that tests if any job finished with warnings. If this nested condition is met a routine is called to write a warning message to the sequencer log.

I do get at the end of the sequence run the warning message I want from my routine. Then I get the following warning:
O2c_Jde_Load_49CarrierZone_SSeq..JobControl (@fWarningForce): Controller problem: Unhandled failure () encountered calling routine DSU.fWarningForce
followed by the information summary of the sequence run followed by:
O2c_Jde_Load_49CarrierZone_SSeq..JobControl (fatal error from @Coordinator): Sequence job (restartable) will abort due to previous unrecoverable errors
and then the sequencer aborts.

The function is a simple as:
Call DSLogWarn(JobName, "Sequencer called jobs with warnings")
Ans = ''

and DSJ.ME is passed from the sequencer as the job name


Since the sequencer does call the routine and the routine does correctly write my warning log entry I'm not sure why the other errors occur and the sequencer eventially aborts
Byron Paul
WARNING: DO NOT OPERATE DATASTAGE WITHOUT ADULT SUPERVISION.

"Strange things are afoot in the reject links" - from Bill & Ted's DataStage Adventure
sumitgulati
Participant
Posts: 197
Joined: Mon Feb 17, 2003 11:20 pm
Location: India

Post by sumitgulati »

I don't know why is this happening. Try using UtilityWarningToLog routine in the routine activity instead of your routine. This may help you find out if the problem is with the routine you wrote or there is some other problem.

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

Re: Sequencer Controller problem: Unhandled failure

Post by chulett »

datastage wrote:The function is a simple as:
Call DSLogWarn(JobName, "Sequencer called jobs with warnings")
Ans = ''
You've got the arguments backwards. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DSJ.ME is not a job name, it's a job handle.

Deep within DSLogWarn, therefore, an "invalid data type" error has been generated, but not handled. Hence "unhandled failure".

What you should have written was

Code: Select all

$IFNDEF JOBCONTROL.H
$INCLUDE DSINCLUDE JOBCONTROL.H
$ENDIF
JobName = DSGetJobInfo(Arg1, DSJ.JOBNAME)
Call DSLogWarn("Job name = " : JobName, "Sequencer called jobs with warnings") 
Ans = '' 
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Or what Ray said. :oops:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply