HI,
In release v7.5.3 I have a problem with the server container.
In my job I call a container and pass on two parameters: a path and a file name, the output of the container is a new seqfile.
until this release this would create a new file at the dir it got from the parameters .
par1 = d:\dw_ut\pd_fexp
par2= filename
with the new release it creates a new file at d:\dw_ut
with filename pd_fexpfilename
putting a \ at the end of par1 solves the problem
but this will make all my other jobs not run well because it is a global parameter
does anyone have a similar problem \ knows how to fix ?
So, they fixed something that never should have been working. What makes you think your change will 'make all other jobs not run well'? Have your tried it? What happened?
-craig
"You can never have too many knives" -- Logan Nine Fingers
when i added a \ after at the end of the parameter in other jobs i read a file by using #par1#\#filename# then the job look for a file in
d:\dw_ut\pd_fexp\\filename and i got an error cannt open fie
Ah... Windows. UNIX wouldn't care. You'll need to add the path separator in the container it seems - I assume you are doing "#par1##filename#" there, yes?
-craig
"You can never have too many knives" -- Logan Nine Fingers
in the container i do ""#par1#\#filename#" and also in the other jobs that not a container
it happend when i concatenate two parameter at the path of a file but if i send i change that at the container at this way ""#par1#\filename.txt it will work