Topic "support for vms file versions"

Author Message
jiri.kaspar
[View user's profile]

Joined: 2015-03-05
Posts: 2
Downloading a file (sftp) from VMS(v8.4, TCPIPv5.7-ECO5), a version number is preserved in the windows filesystem. Everything else works fine, but this is ugly, you need to cut it before other use of the file on windows.

Support of VMS file versions would be easy, there is only a need to respect VMS principle of file versioning.

VMS filesystem stores multiple versions of files, they are numbered 1...32767.
Version number is delimited by a semicolon (i.e., "name.ext;3256").
You can specify version number to work with specific version of a file.
The version specification is required only for the file deletion, it can be omitted in all other cases.
If no version is specified, the behavior depends on file opening mode.
The last version of the file is open if the file is open for reading or reading and writing.
A new version of the file is created if the file is open for writing only or the file does not exist.

There are several "version wildcards", you can use them in any file specification:
;0 means the highest version number,
;-0 means the lowest version number,
;-1 (or generally ;-n) means previous version (or nth version before the highest),
;* means all versions.

To support file versions we need to be able to cut a version specification from the filename and to concatenate it when necessary.
There are several possible modes of operation:

1. Neutral OS mode - vms will be seen as all other systems - you will see the most recent file version only.
In communication to the server, ";0" is concatenated.
There is the only exception: ";*" needs to be concatenated in delete command(or ";0" - user can select).
Version is cut from all server responses, no version is displayed.
No change is required in download operation.

2. VMS mode - multiple versions on VMS, single version on windows.
Versions are preserved in server communication (both directions), versions are displayed.
Versions are cut in download operation.

3. VMS archive mode - multiple versions on both systems. It can be useful for archiving of VMS directory including all file versions.
Versions are preserved in server communication (both directions) and also in download operation (the current behavior).

For advanced use, we can specify four attributes independently on each other:

1. server attribute "version for directory operation" - string (max. 7 characters)
2. server attribute "version for delete operation" - string (max. 7 characters)
3. server attribute "cut versions from server response" - flag
4. download transfer attribute "cut versions in download" - flag

Neutral OS mode: ";0", ";*", yes, yes
VMS mode: "", "", no, yes
VMS archive mode: "", "", no, no

advanced mode settings:
";-1", "", no, yes or no: to work with previous versions
";-0", "", no, yes or no: to work with the oldest versions
";0", ";0", no, yes or no: to work with current versions, but not to affect older, see version
";0", ";0", yes, yes or no: to work with current versions, but not to affect older, don't see versions
etc.

If we add this small change, VMS community will be very happy.
I can help you to implement and test this functionality, I can provide a VMS system for testing, but I have no time to dig to sources and make my own build. If you are interested, please, let me known, we can arrange cooperation by email or phone.

Regards,
Jiri
Advertisements
Petr
[View user's profile]
Moderator
Joined: 2006-01-26
Posts: 50
jiri.kaspar wrote:
If we add this small change, VMS community will be very happy.


Jiri, as you can imagine, our resources are very limited. How many users need to copy files between Windows and OpenVMS?
jiri.kaspar
[View user's profile]

Joined: 2015-03-05
Posts: 2
Petr wrote:
jiri.kaspar wrote:
If we add this small change, VMS community will be very happy.


Jiri, as you can imagine, our resources are very limited. How many users need to copy files between Windows and OpenVMS?


We'll see when I post VMS support announcement :D

OK, I understand it well. I've downloaded sources and looked at them in the meantime. Adding full VMS support with file version filtering would be more complicated than I expected. It made me to rethink required functionality. Let's focus to the main issue.

The minimal vms file version support is to cut version number from the filename (starting semicolon) during file transfers (in both directions). It can be switched on by some global option (in a configuration file or on a command line). A checkbox "cut VMS versions" in "transfer settings" is not necessary, vms people will set it once and forever. A communication to Unix systems wont be affected, because the semicolon is not used in filenames.

Could you add "if (vmsversioncutmode) { find first ';' and replace it with 0 }" to download and upload code in some future version ?

Regards, Jiri
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
I have sent you an email to an address you have used to register on this forum.
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24995
Location: Prague, Czechia
This request has been added to the tracker:
https://winscp.net/tracker/show_bug.cgi?id=1307
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License