@rsford31: Cannot you switch to *nix-style file system? Also SFTP is usually easier to use with mainframe systems.
See Can I connect to a mainframe server? (e.g. VMS, MVS, AS/400)

I'm trying to connect to a mainframe using a command file and winscp.com. User id is OPPR123. When I manually log in through the GUI, I get "no dataset found", but then end up in /'OPPR123.'/. I the command file I have as follows:

When winscp.com runs with the above command, I end up with the following:

I also tried the command file:

The file was uploaded successfully, but when it was checked on the host, the text was garbled.
When I use a different FTP client that came with our file transfer automation software, I see in the logs

The reason I'm wanting to use WinSCP is I can save the sites, and then depending on the file name, I can dynamically create the command file to use with the applicable site and upload the file. So files matching JXU.UTUC.TFUUHM.TEMP will be uploaded to saved site going to the mainframe and then others to a different site.
Any ideas?

@Nenad: WinSCP supports both:
https://winscp.net/eng/docs/protocols

Hello,
Isn't that WinSCP supports only SSH FTP - I.e. "SFTP" - not FTPS (FTP over SSL) ?
Regards,
Nenad

Thanks for sharing your findings.

I was going to report an issue but while writing it up, I noticed the solution, so this post it just to help the mainframe friends who are trying to use FTPS to an IBM Mainframe using WinSCP.

There seems to be an issue with WinSCP to handle mainframe dataset names that are more than 2 parts. FileZilla has the same issue. For example UserID.Test will display as output to the dir command but UserID.Test.JCL will not. But downloading these datasets is not a problem with the command-line. See example below.

Support: Is this mainframe dataset listing thing listed as future enhancement?

You need to do a change directory command up to the second last portion of your dataset and then do a get of the last part. Also, you need to use /ini=nls, so it doesn't cache your remote files otherwise it will give you an error
(Can't get attributes of file ''filename''. File or folder ''filename'' does not exist.) second time you try downloading the same file.

Example:

FTPSGet.txt

This will download UserID.T.ALLTXND.ASPIN35I from the mainframe.

Navigating Datasets in the GUI:
To navigate the mainframe datasets in the GUI, use the Location Profiles feature and add the mainframe dataset name in the Remote Directory without the slash in front. So, if you need to navigate to a PDS User.Test.Jcl(*), then add 'UserID.Test.Jcl' <- notice the single quotes. If it is a regular dataset, (e.g. UserID.Test.crap.myJunk), then you will add 'User.Test.crap'. This same approach works if you need to download a dataset that you have access to but does not start with your userid. Without these Location Profiles, you just sit in the OMVS root and there is no way to switch to any MVS datasets.