Pragma Systems Technical Forum

sftp client - need detailed documentation/reference for the sftp.exe commands

https://forums.pragmasys.com/Topic447.aspx

By emalinis - 8/20/2018 7:55:37 PM

Hi,
I cannot seem to find any details, either at https://www.pragmasys.com/ssh-client/topics or within the Pragma installation about how one uses each of the sftp commands.  For example, 'help' within an sftp client session only has high-level descriptions for each the commands.  I am specifically looking for what the put/mput command options are:
sftp> help
:
put/mput [-p] local-path [remote-path]  Upload files. Pattern can be given
:
- What does the [-p] parameter mean??
- Can multiple (space-separated) files be supplied for mput, like in most other ftp clients? Or is the 'local-path' actually meant to be a folder containing the set of multiple files to be sent?
- Etc.

Basically, what I'm saying is the help provided within the sftp session is *not* sufficient.  And there does not seem to be any additional details provided when running 'sftp> help mget'.

For Pragma sftp version details, this is what we get:
sftp> version
Pragma SFTP client. SFTP protocol version 0
The "Pragma FortressSSH ClientSuite" item in the Windows "Programs and Features" control panel applet says "5.0.9.2904".
By Technical Support Group (TSG) - 8/21/2018 10:27:03 AM

Hello,

I'm sorry that the documentation is not clear. We will look into clarifying it for a future release.

The -p option is to persist the date/time stamp on the new file. The -p added to the get/mget command will do the opposite of what the current setting is. For example, if you start the session with the -p parameter, so that all files will use the transfer timestamp, then adding the -p option to the mget command will retain the timestamp.

We do not allow multiple files with a list of files. We do allow multiple files separated by a space, but we do allow wildcards to transfer based on a pattern.
By emalinis - 8/21/2018 11:06:17 AM

Technical Support Group (TSG) - 8/21/2018 4:27:03 PM
Hello,

I'm sorry that the documentation is not clear. We will look into clarifying it for a future release.

The -p option is to persist the date/time stamp on the new file. The -p added to the get/mget command will do the opposite of what the current setting is. For example, if you start the session with the -p parameter, so that all files will use the transfer timestamp, then adding the -p option to the mget command will retain the timestamp.

We do not allow multiple files with a list of files. We do allow multiple files separated by a space, but we do allow wildcards to transfer based on a pattern.

Thank you for the reply.  Can you pls clarify the following:
- With mput -p .. (ie. using -p parameter in *mput") what will be the files' date/timestamp on the *remote* host?  Will the -p for mput modify the *source* files' date/timestamp at all?
- Kinda confused about your reply on the list of files.  If you "..do allow multiple files separated by a space.." what do you mean about *not* allowing with a *list* of files?  Do you mean something like a list of files in an input text file?  Pls clarify.
Thanx.
By Technical Support Group (TSG) - 8/21/2018 2:44:08 PM

Hello,
The client will not modify the source file in any way. Only the destination file. The options are keep the source file timestamp or use the timestamp at time of copy. The -p parameter of the mput/put command will alter what is assigned at time of connection.

By 'list of files' I am referring to a series of files passed to the mput command with a space separator, such as mput file1.txt file2.txt. We do allow a wildcard, such as mput file*.txt.

I hope that clears things up.
By emalinis - 8/21/2018 3:49:06 PM

Technical Support Group (TSG) - 8/21/2018 8:44:08 PM
Hello,
The client will not modify the source file in any way. Only the destination file. The options are keep the source file timestamp or use the timestamp at time of copy. The -p parameter of the mput/put command will alter what is assigned at time of connection.

By 'list of files' I am referring to a series of files passed to the mput command with a space separator, such as mput file1.txt file2.txt. We do allow a wildcard, such as mput file*.txt.

I hope that clears things up.

Ok, thank you again.
This is what you originally said:
[We do **not** allow multiple files with a **list of files**. We **do allow** multiple files separated by a space"]
So I hope you can see the discrepancy/confusion there.

I am presuming at this point that a command such as: mput file1.txt file2.txt file3.txt **is** allowed. and supported.  If this is not the case, pls do advise.
By Technical Support Group (TSG) - 8/21/2018 4:54:51 PM

I re-read my original reply and I do see where the confusion is. I dropped the word "not" in a very important place.

We do NOT support multiple files as part of the mget/mput command separated by spaces.