Unable to open file 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
Poornagirija
Participant
Posts: 65
Joined: Fri Nov 19, 2004 12:00 am

Unable to open file error

Post by Poornagirija »

Hi Folks, :D

We have a job which is taking xml input and giving .txt output.

The job desing is like

folder--->xmlinput--->xfm--->fileoutput


we have defined parameters for file path for that job.When we tried to run the job its giving following error
unable to open the path :(

We have checked the path its correct!
We tried to change from parameters to default values still no luck.
We have permission as we tried running through dsadmin.

we have only executable available in test environment but not the design.but its running fine in test environment.

we tried to import and export the executable and tried to run the job but the same error is coming.

Im scared whether the job has corrupted in anyway as it was last run on jun2006 and now we are trying to run it again. :shock:
We need to recover the original code with the design.

Can anyone please help me in getting that!
Thanks in advance
:D
With Regards,
Poornagirija.

"Don't limit your challenges - challenge your limits"
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Please post the complete error(s) from the job's log regarding the file error.

We need to recover the original code with the design.

Recover? Either you have it or you don't. What about in your development environment or in Version Control? Exports of the project you've archived somewhere?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Poornagirija
Participant
Posts: 65
Joined: Fri Nov 19, 2004 12:00 am

Post by Poornagirija »

Erro is:
"DSD.UVOpen Unable to open folder /xxx/...../xxx"

FYI
The same job is running fine when i tried to mv the input file to some other folder..
is that a permission issue?? :?:
With Regards,
Poornagirija.

"Don't limit your challenges - challenge your limits"
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

If you are certain that it exists, then yes I would assume a permissions issue.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Check the permissions for every directory on the path. Make sure that every directory and the basename are both spelled and cased correctly.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

The 'other folder' that you are referring to, is it on the Test enviroment that you specified where the job (executable) that runs fine?
If the job work from root and not from any particular direcory, hust to check the permission releated issues a specified, move your file to immediate parent directory and check, if it doest work out, move to another level up. Till you find out the folder where th actual permission is lacking.
And BTW, you cannot create a desing from an executable.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Poornagirija
Participant
Posts: 65
Joined: Fri Nov 19, 2004 12:00 am

Post by Poornagirija »

Hi Friends,
Thanks for all your suggestions.

Actually the problem is with the directory(folder).It got corrupted due to some reason on unix dev box(dont know why:roll: ).

so we created a newfolder previous one renamed and its working fine now.

Thanks!! :D
With Regards,
Poornagirija.

"Don't limit your challenges - challenge your limits"
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Check what is the difference for the new and existing folders interms of permissions.
Renaming the existing folder to a new one will always retain the existing previlages unless altered specifically.
Or could be even due to some character that persent in Unix min interpreted by Datastage.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply