Project:INFOCENTRE (t3fAC)
Job name:AlimIFCAICOM
Event #:11
Timestamp:20/12/2006 23:02:38
Event type:Warning
User:BDPME\USRTTT
Message:
DataStage Job 1 Phantom 3548
Program "JOB.1118171632.DT.1414830161.TRANS1": Line 152, Unable to open the operating system file "RT_BP1.O/DSU.DataTypePicS9".
[ENOENT] No such file or directory
Program "JOB.1118171632.DT.1414830161.TRANS1": Line 152, Unable to load file "DSU.DataTypePicS9".
Program "JOB.1118171632.DT.1414830161.TRANS1": Line 152, Unable to load subroutine.
Attempting to Cleanup after ABORT raised in stage AlimIFCAICOM..T010_ALIM_AICOM
DataStage Phantom Aborting with @ABORT.CODE = 3
Like you see i using the sdk/DataTypePicS9 transform and i and understand that the job can find it.
Before import a dsx in production we test the jobs in a pre-prod server and they don't abort.
After a simple compilation it's okay.
Can you tell me what is wrong?
Do an exact search on 'Unable to open the operating system file'. One thing is strange, the routine 'DataTypePicS9' is a datastage routine. It should be catalogued by DSX prefix rather than DSU.
thurmy34 wrote:
Program "JOB.1118171632.DT.1414830161.TRANS1": Line 152, Unable to load file "DSU.DataTypePicS9".
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Has this job been running in the past. A quick read of the query results indicates that such problems arise if something goes wrong with the executables, which can be fixed after a re-compile. The production support is right, they will not compile it, you need to recompile the job and export it again.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
I think we need more expert advice. Lets wait for the true Gurus to give us their expert advice.
If nothing else works, make a copy of the sdk routine, name it myDataTypePicS9(). This way you will be able to compile it and run it. Make sure it works in the test box. Export the new job and your user defined routine myDataTypePicS9(). Keep this as a second option/work around.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
You need to double-check that you actually have the sdk routines in this 'production' environment. The transform you used is just a gateway to the routine itself and it will happily compile without the routine there, but will blow at runtime.
I'm not sure why in the heck you wouldn't have them all as they install automatically with the product, but not knowing anything about how this environment was setup that's the first question that needs to be asked.
-craig
"You can never have too many knives" -- Logan Nine Fingers
That message says that DataTypePicS9 is being sought as a user-written routine, with a DSU prefix. But SDK routines are not cataloged with a DSU prefix. Thus, if you want to invoke the SDK routine your routine will require an appropriate DEFFUN declaration.
Note also that Transforms can not be invoked from routines.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.