DSXchange

Hi,

Let me explain the design of the job, which is

Merge ----> Transformer ----> Few Sequential files (Output)

This job processes nearly 5mn records and this job was running fine in the development server (Development server is in Windows) and the same job is giving the weird problem, which is "XFMGetMMDaysForHCCostCtrHor..XFMAlloMMDaysByCostCtr detected" and when the job was reset, the error message is "DataStage Job 521 Phantom 226
Abnormal termination of DataStage.
Fault type is 4. Layer type is BASIC run machine.
Fault occurred in BASIC program JOB.614944104.DT.1387966028.TRANS1 at addre". I think the error message is incomplete and so i could not trace the problem.

Has anyone encountered the problem, if yes can you share the solution to resolve the problem?

All your valuable inputs are very much appreciated.

Thanks in advance for your inputs.

Regards
Saravanan

Searching for that error only finds one other post that mentions it. No solution there, but there is a complete error message and it probably shows what was cut off from yours. Best to contact Support for this one, I would think.

Hi Craig,

Thanks for your response.

Am still trying something to figure out what is causing this problem. I would contact support if nothing can be found.

Regards
Saravanan

Changed the existing job design as mentioned below.

Merge ---> Seq File.

This temp job got aborted with warning message as 'Fault type is 4. Layer type is BASIC run machine.
Fault occurred in BASIC program DSD.StageRun at address 150'.

Is there anyway to look at the source code of DSD.StageRun to find out the cause of the problem.

Any other suggesstions are very much appreciated.

Thanks in advance for your inputs.

Regards
Saravanan

No. Source code for DSD.StageRun is an IBM proprietary secret. It is the subroutine that invokes a server job Transformer stage.

Your support provider will be able to ask the question, and someone in IBM can look at the source code, but you'll not be permitted to do so.

In Appendix E of Administering UniVerse you will find how to decode fault types. Here you will learn, for example, that fault type 4 is a SIGILL (illegal instruction signalled), so you might search the forum for this.

Thanks Ray for your repsonse. In this case, i would seek IBM support to investigate and resolve the problem.

Regards
Saravanan

I am very curious to know uvconfig file parameters are related to this problem.

Your inputs are much appreciated.

Thanks & Regards
Saravanan

None at all.