Abnormal Termination

[ray.wurlod]

There's no parameter.

There IS, however, good design and good operational practice.

One of these is determining the cause for the aborts (reset the job and read the log entry called "from previous run") then fixing the design so that they don't recur.

Another is to limit the total number of simultaneously open dynamic hashed file to a number smaller than T30FILE.

[elavenil]

Hi,

This abnormal termination happens due to insufficient resources in the server or No of files opened is greater than T30File parameter value mentioned.

Hope this would help to identify the issue.

Regards
Saravanan

[ariear]

insufficient resources absolutly !
Ask Ascential to send you the registry (SessionManager) values - It really can help

[bonthalaprasad]

We are encountering the same kind of abnormal termination in job, when reset was issued it came back with this message

From previous run
DataStage Job 2260 Phantom 4343
Abnormal termination of DataStage.
Fault type is 11. Layer type is BASIC run machine.
Fault occurred in BASIC program DSP.Open at address 4d4.

Any ideas of why this might be happening

There's no parameter.

There IS, however, good design and good operational practice.

One of these is determining the cause for the aborts (reset the job and read the log entry called "from previous run") then fixing the design so that they don't recur.

Another is to limit the total number of simultaneously open dynamic hashed file to a number smaller than T30FILE.

[ray.wurlod]

DSP.Open is one of theirs (Ascential's). It's the "open" function exposed by plug-in stage types. With sufficient knowledge you could use a utility like VLIST to see what's being executed at address 0x4d4 in the object code but, without source, that won't help greatly.

Fault type codes are listed in Appendix E in the Administering UniVerse manual, which can be downloaded from IBM web site. They correspond to UNIX signal numbers; fault type 11 is "segmentation violation" (SIGSEGV), which means that something has tried to access a piece of memory that it doesn't own. It can sometimes occur if a "null pointer" is generated, for example by trying to open a file without providing a file name.