RT_SC213/jpfile: No such file or directory

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

RT_SC213/jpfile: No such file or directory

Post by roy »

Hi All,
I noticed the below in some of my EE jobs
Does anyone know what it means?
The job in question has nothing but a Dataset to Dataset nothing more.
Director log shows all is well
The job is using a Message Handler.
All seems to be ok but this enty is disturbing
(Almost as disturbing as the fact I even looked in the &PH& files :wink: )
DSD.RUN_10309_13919
::::::::::::::
DataStage Job 213 Phantom 26330
RT_SC213/jpfile: No such file or directory

3 record(s) selected to SELECT list #1.
DataStage Phantom Finished.
Thanks in advance for your time :),
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The RT_SC file is filled at compile with the scripts that PX uses - does the error go away if you recompile the job?
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Post by roy »

Thanks for the reply Arnd,
In this particular case I can compile the job, but since this is in the production server any job containing a transformer is not compile-able since there is no compiler there :(.
I used the export/import with executables to get the jobs to the prod server.
Any ideas on how I might prevent such issues to begin with?
Thanks in advance,
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

One way might be to count the number of pieces that should exist for job number xxx before promoting and verifying that number after promotion. RT_BPxxx, RT_SCxxx and RT_BPxxx.O. If you want to be thorough, do the same for RT_CONFIGxxx and RT_STATUSxxx using SQL queries (SELECT COUNT(*) FROM tablename).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
elavenil
Premium Member
Premium Member
Posts: 467
Joined: Thu Jan 31, 2002 10:20 pm
Location: Singapore

Post by elavenil »

Hi Roy,

Check this RT_SCnn file in the folder for that job and if this file exists in the folder then this could be a bug in DS and we had the same issue in my earlier project and we had to apply the patch and it worked.

HTWH.

Regards
Saravanan
Post Reply