Re: Very Bizarre "Feature" with new V5R1 CUMET tape and Spaces inDocument Name

On Mon, 4 Aug 2003, Shannon O'Donnell wrote:
>
> Right after that we started noticing that when we attempted to open HTML
> documents in a browser (stored on our IFS) and those HTML documents contains
> spaces in the names (i.e.,   TEST DOCUMENT.HTM),  that we were unable to
> open it.

What is opening it?  The web server?   Try using TEST%20DOCUMENT.HTM,
since TEST DOCUMENT.HTM violates HTTP protocol standards, it shouldn't
work.

> Further investigation reveals that even from a DOS window, with a mapped
> network drive, attempting to do a DOS copy or rename ALSO fails...unless you
> first enclose the document name in double quotes.

Hmmm, this has always been the case on my PC.  Not only for IFS, but for
local hard drives as well.

>
> If we rename the document so that it contains no spaces, then everything
> works fine.
>

Yes, that's because DOS commands use space as a parameter delimeter.
If you specify a file as Long Name.doc it will think appear in the program
as two different parameters.  But, "Long Name.doc" is only one parameter.

In iSeries terms...   doing this:

        CALL PGM(MYPGM) PARM('abcde' 'fghij')

is very different from doing this:

        CALL PGM(MYPGM) PARM('abcde fghij')

The difference is that MYPGM is getting two parameters in the first case,
and just one long parm in the second case.   The same thing is true in
DOS programs when you do this:

        mypgm abcde fghij

instead of this:

       mypgm "abcde fghij"

>
> Has anyone seen this problem?  Anyone have any suggestions?
>

Yeah, use the quotes :)