Capturing detail information of job in other category
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 60
- Joined: Tue Aug 29, 2006 11:14 pm
Capturing detail information of job in other category
In many cases jobs are called by Batch, sometimes jobs(in other category) get aborted due to many reasons like locks on some table, some ORA error.. etc
Is there some way to get exact reason of job failure how that can be implement in the Batch.
Is there some way to get exact reason of job failure how that can be implement in the Batch.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 60
- Joined: Tue Aug 29, 2006 11:14 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You know the job name. You can attach that job and use the requisite functions to interrogate its log. Don't forget to detach the job before exiting from your routine.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: Capturing detail information of job in other category
hello i am new to datastage, but below process is followed by department.
for batch file you may be using DSExecute.exe with parameter as job name.
in this job, go to job-properties-->job-control. in job-control write your code which will use following routines like
DSAttachJob
DSRunJob
DSGetLogSummary
DSDetachJob
you can find help and code for above routines in built-in help of datastage.
then you can execute this job and catch a log. you can get all types of error logged.
for batch file you may be using DSExecute.exe with parameter as job name.
in this job, go to job-properties-->job-control. in job-control write your code which will use following routines like
DSAttachJob
DSRunJob
DSGetLogSummary
DSDetachJob
you can find help and code for above routines in built-in help of datastage.
then you can execute this job and catch a log. you can get all types of error logged.
-
- Participant
- Posts: 60
- Joined: Tue Aug 29, 2006 11:14 pm
Thankx Ray, Your suggestion sovled my problem , but know there is new problem, whatever error reason is stored in a variable and passed to the a job that insert it (error) in a table.
Obstacle comes when job pass the parameter(which have stored error message) throgh the transformer job get aborted as the "identifier becomes too long" becuase the error message is in detail(paragraph),
Do you have any suggestion to resolve this problem.
Obstacle comes when job pass the parameter(which have stored error message) throgh the transformer job get aborted as the "identifier becomes too long" becuase the error message is in detail(paragraph),
Do you have any suggestion to resolve this problem.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 60
- Joined: Tue Aug 29, 2006 11:14 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
"Identifier" is usually the column or table name, not the text value itself. In DataStage you can set VarChar up to 65535. The restriction, however, may be in the data browser itself rather than in the database connection - post the full error message, which should indicate its source.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.