DSXchange

Hi All,

below error is displayed
please do the need ful

SEQUENCER NAME..JobControl (fatal error from UtilityAbortToLog): USER INFO: Job Aborted. Please refer log for details JOB=> SEQUENCER NAME STAGE=> JobControl LINK=> -8

please help...
Thanks in adavance.....

What caused your job sequence (note, it's not "sequencer") to execute a routine activity that invoked UtilityAbortToLog?

Only you can determine this, as none of us can see your job sequence design.

ray.wurlod wrote:What caused your job sequence (note, it's not "sequencer") to execute a routine activity that invoked UtilityAbortToLog?

Only you can determine this, as none of us can see your job sequence design. ...

thanks ray,
can u please give me the clear discripition

I don't know. You will have to wait until next time U logs in. And even then, U may not be able to give a clear description.

The problem is in how your job sequence is executing. You must determine what caused the Routine activity that invokes UtilityAbortToLog() to be executed - presumably a trigger upstream of the activity.

There is no clearer explanation that we can give, because we can not see your job sequence design.

Premium membership is not expensive, at less than 30c (Rs12) per day.

the sequencer is failed due to the above error and it can describe as
in the sequencer abort acitvity and job acitivty and routine acitvity
in the job activity it trigger as job that generates sequncer number and the job is amultiple instance.
belowis the some more discription
Exception Handler is triggered whenever a job fails. The Update Sakey job is called so the max sakey is updated just in case the load job aborts. The Routine Activity calls UtilityAbortToLog to abort the sequencer.

Hello Tej,

can you please write down a flow diagram of your sequecer activities in sequece,

Based on your previous post,

you are aborting your sequecer incase of failure of your job activity.

what actully you want if your ur job abort.

Regards,

The Exception Handler has its own activity variables which you could include in the logged message. But you should be able to identify the culprit - that it, the activity that failed and thereby caused the Exception Handler to be triggered - from the job sequence's job log.

Exception Handler activity variables are:

• $ErrSource - name (label) of the activity that raised the exception
  
  $ErrNumber - indicates whether the activity actually ran (1 = activity ran, aborted and had no specific handler set up, -1 = job failed to run for some reason)
  
  $ErrMessage = text of message that would be logged as a warning when the exception is raised