I was basing the statement that CA's ftp2 works to other systems with
blanks on - 
>In desperation, do you really needs the damn blanks?

It's a political thing.   I can argue with users to who are already
using directories with blanks, or find a way to accommodate them. They
have several directories so defined.

Howard - can you set the record straight? I may be misreading the above.

Dennis Roach
GHG Corporation
Lockheed Martin Mission Services
Facilities Design and Operations Contract
NASA/JSC
Address:
   2100 Space Park Drive 
   LM-15-4BH
   Houston, Texas 77058
Mail:
   P.O. Box 58487
   Mail Code H4C
   Houston, Texas 77258
Phone:
   Voice:  (281)336-5027
   Cell:   (713)591-1059
   Fax:    (281)336-5410
E-Mail:  [email protected]

All opinions expressed by me are mine and may not agree with my employer
or any person, company, or thing, living or dead, on or near this or any
other planet, moon, asteroid, or other spatial object, natural or
manufactured, since the beginning of time.


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Paul Gilmartin
> Sent: Wednesday, July 29, 2009 8:53 AM
> To: [email protected]
> Subject: Re: FTP to Unix directory with spaces
> 
> On Wed, 29 Jul 2009 07:31:18 -0600, Roach, Dennis (N-GHG) wrote:
> 
> >What do we know?
> >     CA's FTP2 fails with blanks in the directory name to this
system.
> >     CA's FTP2 works with blanks in the directory name to other
> systems.
> 
> I have reviewed all the OP's updates in this thread, and I do not
> see that.  Can you cite timestamp and/or URL?
> 
> >     Another FTP client works with blanks in the directory name to
> this system.
> >             This says that the directory and access structure is
valid
> for this transfer.
> >
> >Suspect:
> >     One end or the other is issuing a command, such as SYST, that is
> >responding with something that is not liked or not valid, causing
> >invalid options to be assumed on one end.
> >
> >Validation:
> >     IP trace of success and failure
> 
> >> -----Original Message-----
> >> From: IBM Mainframe Discussion List [mailto:[email protected]]
On
> >> Behalf Of Howard Brazee
> >> Sent: Tuesday, July 28, 2009 2:46 PM
> >>
> >> On 28 Jul 2009 11:34:10 -0700, (Dennis Roach)
> >> wrote:
> >>
> >> >Not actually. What we are wanting to see is the directory up
level.
> >> Try
> >> >
> >> >cd /ps
> >> >cd /ps/cs90ftp
> >> >cd /ps/cs90ftp/conversion_files
> >> >cd /ps/cs90ftp/conversion_files/CC
> >> >cd /ps/cs90ftp/conversion_files/CC/extract
> >> >dir
> >> >
> >> >What I would suspect is that somewhere along the way something
does
> not
> >> >exist or you do not have the required access. This will list the
> last
> >> >valid directory in the path.
>       ...
> >> 12:45:45 FTP2: cd /ps/cs90ftp/conversion_files/CC/extract/Test
> Folder
> >> 12:45:45 550 Failed to change directory. 12:45:45 FTP2: END
12:45:45
> 
> -- gil
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to