IDOC load error

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
Amos.Rosmarin
Premium Member
Premium Member
Posts: 385
Joined: Tue Oct 07, 2003 4:55 am

IDOC load error

Post by Amos.Rosmarin »

Hi,


I have 2 DS servers (development and production) . I have a job that uses the IDOC Load stage. Both uses the same DS version and the same SAP pack version.
When I run it from the development machine - it is ok.
When I run the same job (using the same input data) from the other machine it fails with :
DataStage Job 647 Phantom 5244
Program "DSP.Open": Line 122, Exception raised in GCI subroutine:
Unknown exception code.
Attempting to Cleanup after ABORT raised in stage MAT_Load..IDoc_Load
DataStage Phantom Aborting with @ABORT.CODE = 3
I tried to use trace and look at the PH .... nothing
Any idea what can make the diff ?



Thanks,
Amos
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

No, so you need to be a detective. What's different between the two machines? Look not just at DataStage but also at operating system and SAP connectivity configurations.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Amos.Rosmarin
Premium Member
Premium Member
Posts: 385
Joined: Tue Oct 07, 2003 4:55 am

Post by Amos.Rosmarin »

Hi,

I've been doing detective work but I was hoping to get some ideas about how the ds-idoc mechanism works.

There are 3 SAP dll's that has to be installed on the ds machine (libref32, librfc32u ...) . How do I know that the problem does not come from there ?



Thanks,
Amos
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

... because they work at other sites.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply