Your best friend for file transfer.

Fetch application logoFetch

VMS Logical Name problem? (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 11 years ago by lcarl
  • Latest reply 11 years ago from Jim Matthews
  • lcarl Member

    A few days ago, I was trying to help someone at Dartmouth submit a FAS journal entry using Fetch 4.0.2 on OS X.

    The connect seemed to work, but sending a file gave "directory not found" after a long delay. Looking at the error, I could see if was not correctly expanding the logical name. When I plugged in the logical name equivalent, it worked fine. I don't know why this would be failing because FAS$INPUT is a "system" logical which *should* be expanded anywhere is is used. As I recall, the error made it look like it was trying to use FAS$INPUT as the name of a subdirectory in the user's home directory.

    I'm fairly sure this used to work when I was at Dartmouth, and a lot of people must be *trying* to do this.... ??? Any thoughts?

    Posted 11 years ago #

  • Jim Matthews Administrator

    I wonder if the FTP server isn't smart about expanding system logicals, but I'm not familiar enough with VMS to know if that would explain the problem. It might help to see the contents of the Fetch Transcript window after the error.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

Topic closed

This topic has been closed.