DSD.UVOpen Unable to open file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am
DSD.UVOpen Unable to open file
DSD.UVOpen Unable to open file.
Hass file unable to open.
Sequencer have parametes as normal and same parameters will be use for every job in the sequencer. But a job got a extra slash (/).All jobs completed successfully except that job.
All Parameters are default from UNIX.(defined in Unix)
Schedule tool Unicenter call the scripts from UNIX
Job..xProcess: |job..Vehicle.InVeh: DSD.UVOpen Unable to open file '/DSIU_02/Dstage/dat/CV/hash//Vehi'.|
Hass file unable to open.
Sequencer have parametes as normal and same parameters will be use for every job in the sequencer. But a job got a extra slash (/).All jobs completed successfully except that job.
All Parameters are default from UNIX.(defined in Unix)
Schedule tool Unicenter call the scripts from UNIX
Job..xProcess: |job..Vehicle.InVeh: DSD.UVOpen Unable to open file '/DSIU_02/Dstage/dat/CV/hash//Vehi'.|
Siva
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Does the parameter value for the directory have a terminating slash and this particular job have a slash between the parameter reference and the hashed file name?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am
Ray,ray.wurlod wrote:Does the parameter value for the directory have a terminating slash and this particular job have a slash between the parameter reference and the hashed file name? ...
Thanks a lot for your quick response.
we have parameter value for each directory (/) and also we have a slash between parametrs reference and hash file name .
(At this point when job was runninh it took one extra slash(/) and job was aborted..)
I am trying for root cause.
Thank you,
Siva
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am
Chulett,chulett wrote:A "double slash" usually isn't a problem. Ignoring that, are you certain the hashed file at that path otherwise exists and is accessible? ...
Thank you for your help.
Ignored the slash(/) and ran the job finshed successfully.
I am doing root cause analyzing.
Please help to me on this.
Thanks
Siva
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
And *I* want... well, never mind what exactly it is that I want.
As I said, I've had no issues with this, from either sequential file pathnames to pathed hashed filename so perhaps it varies from UNIX to UNIX. As noted, this typically comes from combining two parameters with a hard-coded slash (or perhaps a parameter and a hard-coded "slash hashed file name" and then also including the slash at the end of the parameter value. I've not seen it cause a problem so it looks like you'll need to wait for more smarter peoples to help with this particular sticky wicket.
And hit Preview and there he is. That's what happens when you get distracted mid-post.
As I said, I've had no issues with this, from either sequential file pathnames to pathed hashed filename so perhaps it varies from UNIX to UNIX. As noted, this typically comes from combining two parameters with a hard-coded slash (or perhaps a parameter and a hard-coded "slash hashed file name" and then also including the slash at the end of the parameter value. I've not seen it cause a problem so it looks like you'll need to wait for more smarter peoples to help with this particular sticky wicket.
Code: Select all
#DirectoryPath#/#Filename#
#DirectoryPath#/HashedFileName
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am
Thank you very much....chulett wrote:And *I* want... well, never mind what exactly it is that I want.
As I said, I've had no issues with this, from either sequential file pathnames to pathed hashed filename so perhaps it varies from UNIX to UNIX. As noted, this typically comes from combining two parameters with a hard-coded slash (or perhaps a parameter and a hard-coded "slash hashed file name" and then also including the slash at the end of the parameter value. I've not seen it cause a problem so it looks like you'll need to wait for more smarter peoples to help with this particular sticky wicket.
And hit Preview and there he is. That's what happens when you get distracted mid-post.Code: Select all
#DirectoryPath#/#Filename# #DirectoryPath#/HashedFileName
Siva
-
- Participant
- Posts: 135
- Joined: Tue Dec 09, 2008 10:35 am