Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: OpenVMS now failing as a connected platform

So when did it used to work? Were you using different version of WinSCP or OpenVMS?

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

OpenVMS now failing as a connected platform

Using WinSCP with OpenVMS now fails (all versions of OpenVMS, V7.n, V8.n)
It has issues retrieving the directory, and copying files fails with invalid file specificaion (on OpenVMS)
Copying files to remote side failed.
Failed to set default directory to /SYS$SYSDEVICE:[NIC].
file specification syntax error

The extra / at the beginning is causing the problem for VMS. The SYS$SYSDEVICE: IS the disk, there are no / on OpenVMS.

Directory listings fail:
Unexpected directory listing line 'dspppaksipf-com2012-08-31.txt/dspppaksipf-com2012-08-31.txt;1////dspppaksipf-com2012-08-31.txt;1/29696/1/0/2014/3/57/11/30/1/0/1'.
Invalid argument to date encode [2014-3-57]

OpenVMS used to work... FileZilla works and is being used as a workaround for now.