Reset the Job

shilpa79 · Post by **shilpa79** » Thu May 31, 2007 1:09 pm

Hi,

I am trying to reset my Job if the Input XML file is in incorrect format and not processed properly and nothing is loaded into the target DB then i am moving those files to unprocess folder where I am using a shell script to move the files from inbox to unprocess directories.

I am using a routine for counting the linkcount = 0 then those files are
moved to unprocess and reset the job I am doing everything in the sequencer.

Everthing is working fine except the when the Job is getting reset then the seqeuncer job which is calling that Job is getting Aborted .

can anyone help me out.

Thanks,

ArndW · Post by **ArndW** » Thu May 31, 2007 3:42 pm

What is causing the abort in the sequence that tries to reset your failed job? Could you post the error message that is generated?

shilpa79 · Post by **shilpa79** » Thu May 31, 2007 4:12 pm

ArndW wrote:What is causing the abort in the sequence that tries to reset your failed job? Could you post the error message that is generated?

sequencer log:

JobControl (fatal error from @Coordinator): Sequence job will abort due to previous unrecoverable errors

dsjob log:

Attempting to Cleanup after ABORT raised in stage BCRecgToSTGMarsRecDocLoad..X_ReceiveBC

From previous run
DataStage Job 95 Phantom 29491
Aborting after 1 Rows written to BCRecgToSTGMarsRecDocLoad.X_ReceiveBC.ff_receive_error
Program "JOB.271999132.DT.1438043834.TRANS1": Line 203, Abort.
Attempting to Cleanup after ABORT raised in stage BCRecgToSTGMarsRecDocLoad..X_ReceiveBC

DataStage Phantom Aborting with @ABORT.CODE = 1
Abnormal termination of DataStage.
Fault type is 11. Layer type is Command Language.
CRITICAL ERROR! Notify the system administrator.

ArndW · Post by **ArndW** » Thu May 31, 2007 5:18 pm

The error messages look odd.

What options are you using when calling the job from the sequence? Have you thought about using the "reset then run@ option so you don't need to explicitly reset the job?

chulett · Post by **chulett** » Thu May 31, 2007 5:45 pm

Here are the various fault types that I am aware of:

Administering Universe wrote:signal Value Description
1 (SIGHUP) hangup
2 (SIGINT) interrupt
3* (SIGQUIT) quit
4* (SIGILL) illegal instruction
5* (SIGTRAP) trace trap
6* (SIGIOT) IOT instruction
7* (SIGEMT) EMT instruction
8* (SIGFPE) floating-point exception
9 (SIGKILL) kill (cannot be caught or ignored)
10* (SIGBUS) bus error
11* (SIGSEGV) segmentation violation
12* (SIGSYS) bad argument to system call
13 (SIGPIPE) write on a pipe with no one to read it
14 (SIGALRM) alarm clock
15 (SIGTERM) software termination signal
16 (SIGURG) urgent condition present on socket
17 (SIGSTOP) stop (cannot be caught or ignored)
18 (SIGTSTP) stop signal generated from keyboard
19 (SIGCONT) continue after stop
20 (SIGCHLD) child status has changed
21 (SIGTTIN) background read attempted from control terminal
22 (SIGTTOU) background write attempted to control terminal
23 (SIGIO) I/O is possible on a descriptor
24 (SIGXCPU) CPU time limit exceeded
25 (SIGXFSZ) file size limit exceeded
26 (SIGVTALRM) virtual time alarm
27 (SIGPROF) profiling timer alarm

The starred signals cause a core image to be saved.

So you've got a SIGSEGV Segmentation Violation.

shilpa79 · Post by **shilpa79** » Fri Jun 01, 2007 11:19 am

ArndW wrote:The error messages look odd.

What options are you using when calling the job from the sequence? Have you thought about using the "reset then run@ option so you don't need to explicitly reset the jo ...

My Job design is from the execute command stage using the dsjob command I am calling the dsjob there are two links out from this stage one for sending an email if the Job is getting aborted and another link if the file is bad and nothing is loaded into the target then reset the Job using reset only option the Job activity satge calling the same Job.

ray.wurlod · Post by **ray.wurlod** » Fri Jun 01, 2007 2:37 pm

WHY use Execute Command activity to invoke dsjob command ?!!!!!

Use a Job activity. You can then use "reset if required, then run" as its mode of operation, and everything is automatic. No coding, almost no thought, needed.

shilpa79 · Post by **shilpa79** » Mon Jun 04, 2007 12:18 pm

ray.wurlod wrote:WHY use Execute Command activity to invoke dsjob command ?!!!!!

Use a Job activity. You can then use "reset if required, then run" as its mode of operation, and everything is automatic. No ...

I was using Execute command instead of Job activity because I need to process mutiple files and capture each input file and update in the log table for auditing. Thats the reason we were using that.

Thanks,