Phantom Aborting with @ABORT.CODE = 1

attu · Post by **attu** » Fri Oct 21, 2005 9:21 am

DataStage Job 378 Phantom 8288
DataStage Phantom Aborting with @ABORT.CODE = 1

ArndW · Post by **ArndW** » Fri Oct 21, 2005 11:32 am

You not are going to get a lot of answers to this one.

Please provide enough information to assist in localizing the issue. So far we know the DataStage job is aborting. That's about it.

chulett · Post by **chulett** » Fri Oct 21, 2005 11:55 am

Also try Resetting the aborted job via the Director. Look for a log entry that says "From previous run...". Double-click on it and let us know what's in there - assuming it shows up in the log.

ray.wurlod · Post by **ray.wurlod** » Fri Oct 21, 2005 5:36 pm

Welcome aboard! :D

Every job in your project has a unique number; the job where this problem occurred is job number 378. (You can map names to job numbers in the DS_JOBS table, but I'm sure you know which job it is - its status is Aborted.)

"Phantom" is simply DataStage's name for a background process; the user number (process ID) that executed your job was 8288.

@ABORT.CODE is an internal system variable that identifies what kind of abort condition occurred; you can read about this in the DataStage BASIC manual.

And that's where we run out of information. Take Craig's and Arnd's advice - reset the job using Director then look in the job log for a message "from previous run...". It will contain additional diagnostic information.