Aborted Sequencer: Attempting to Cleanup after ABORT raised

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
kiran_418
Participant
Posts: 40
Joined: Tue Feb 22, 2005 11:12 am

Aborted Sequencer: Attempting to Cleanup after ABORT raised

Post by kiran_418 »

I get the following error.
Iam not sure whats happening.
If I run all the indivudual jobs they are running perfectly fine.
I have declared in sequencer all the parameters as environment variables.
I checked all the parameters and they are fine.
so Y do i get that error

Attempting to Cleanup after ABORT raised in stage

Product_sequencer..JobControl

thanks
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You get that error because a stage aborted.
Reset the job in Director. There should then be an entry in the job log "From previous run..." which contains additional diagnostic information.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
bryan
Participant
Posts: 91
Joined: Sat Feb 21, 2004 1:17 pm

Post by bryan »

hi

I have the same situation.

I see status finished ok for each individual job. In the final event of type Info, I also get sequence finished ok.

The next event it records tells
"Attempting to Cleanup after ABORT raised in stage
sequencername"

wonder why it tells the sequencername as stage?

Ray- I have to tell you, I saw many posts where you say,
additional info would be put to along with "From Previous Run" .

But I never saw any additional info to debug..its just blank with just the message "From Previous Run". Jobs design varies.

Should I set something by which I can additional info in that particular event?

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

Post by chulett »

bryan wrote:But I never saw any additional info to debug..its just blank with just the message "From Previous Run". Jobs design varies.
Did you try double-clicking on the log entry? They usually aren't blank, it's just that you need to double-click on them to see all of the gory details.
-craig

"You can never have too many knives" -- Logan Nine Fingers
bryan
Participant
Posts: 91
Joined: Sat Feb 21, 2004 1:17 pm

Post by bryan »

Yes, Chulett.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I never guarantee that it will be there - always use words like "may" or "should", because sometimes it's not there. Are there any preceding warnings? Is there anything to be found for this run in the &PH& directory (a subdirectory in your project) pertinent to the failure?
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 »

Ray, I got the impression that Bryan was saying the message was there but there was nothing other than that particular message itself. No gory details. I don't recall it working that way. :?

It only shows up when it has something from the Phantom directory to pull into the log. No information there, no 'From previous run' message.

Right?
-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 »

I also was surprised at the report of an empty "from previous run..." event, but let it go through to the catcher. But it is why I suggested explicitly looking in &PH&.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply