A DataStage job can run successfully from the Designer but aborts with a SIGINT when run in the Director

Technote (troubleshooting)


Problem(Abstract)

A DataStage job can run successfully from the Designer but aborts with a SIGINT when run in the Director

Symptom

A DataStage job can run successfully from the Designer but aborts with a SIGINT when run in the Director.


Cause

A SIGINT is sent by controlling terminal to terminate a process or program. In this case, if the user didn't kill the job process from the DataStage engine, nor stop the job in the Director and the issue can be reproduce constantly in the Director. Then the SIGINT is possibly being generated by DataStage itself to terminate the job for some reason, in general, it may be due to a limit being reached that caused DataStage to send the SIGINT signal to abort the job. These limits can be set differently in the Director and the Designer

Diagnosing the problem

Check the job log to see if there are too many warning message. If this is the case, from Director -> Tools -> Options, in Options window under Limits tab, check if any limit set to Warnings.

Resolving the problem

1. In Director -> Tools -> Options -> Limit, set "no limit" to Warning;
2. use message handler (MSH) to suppress the warning;
3. modify the job to avoid the warning (how will vary from job to job and will depend on the design).

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere DataStage

Software version:

8.0, 8.0.1, 8.0.1.1, 8.0.1.2, 8.0.1.3, 8.1, 8.1.0.1, 8.1.0.2, 8.5, 8.5.0.1, 8.5.0.2, 8.5.0.3, 8.7, 8.7.0.1, 8.7.0.2, 9.1

Operating system(s):

AIX, HP-UX, Linux, Solaris

Reference #:

1632981

Modified date:

2013-04-02

Translate my page

Machine Translation

Content navigation