DataStage Phantom Aborting with @ABORT.CODE = 1

venkat626 · Post by **venkat626** » Tue Mar 19, 2013 4:14 am

Hi Team,

In the sequence starting the split job was aborted and the below log as written,

From previous run
DataStage Job 47 Phantom 12766
Job Aborted after Fatal Error logged.
Program "DSD.WriteLog": Line 315, Abort.
Attempting to Cleanup after ABORT raised in job Job_name..JobControl

DataStage Phantom Aborting with @ABORT.CODE = 1

After i reset the job and rerun it,the job was ran successfully.

Could you please tell me why the job/sequence was aborted.

Regards,
Venkat626

chulett · Post by **chulett** » Tue Mar 19, 2013 7:10 am

Which job was this message from - the Sequence job itself or the "split job"? What kind of job is the split job?

ray.wurlod · Post by **ray.wurlod** » Tue Mar 19, 2013 1:10 pm

@ABORT.CODE is only set by server/sequence jobs. However, this is the final message. You need to show us earlier errors from the job log, which is where the cause is reported. These errors might even be reported in the log of a job called from a Job activity in your sequence.

rameshrr3 · Post by **rameshrr3** » Tue Mar 19, 2013 2:58 pm

Reset the sequence and see if you get any additional information during reset in the job log. Sometimes recompiling a sequence will simply solve your problem.