I'm connecting from a Windows XP Pro machine to a z/OS mainframe via FTPS (not SFTP). I need to send SITE FILETYPE=JES prior to uploading a file containing JCL. This command will cause the file to be sent to the z/OS internal reader and submitted as a batch job rather than uploaded into a file.
I'm able to do this using the GUI without any problem at all and everything works exactly as expected. However, what I *really* need to do is make this work via the command line.
I've created a text file called FileTypeJES.scr and am invoking Core FTP Lite with the following command line:
[code]"C:\Program Files\CoreFTP\coreftp.exe" -scbt "C:\Program Files\CoreFTP\FileTypeJES.scr" -u "C:\Documents and Settings\My.Name\My Documents\skeleton.jcl" -A ftp://userid:password@machine.host.com -tls[/code]
I've tried rearranging the order of the options, I've tried adding "QUOTE" to the beginning of the SITE command, I've tried -scal instead of -scbt, I've tried a trial version of Core FTP Pro, but to no avail. As far as I can tell, the script simply never executes.
Am I missing something really obvious?
Can't get -scbt to work
-
- Posts: 6
- Joined: Thu Jul 31, 2008 4:18 pm
Re: Can't get -scbt to work
Fooling around with this some more, I'm beginning to suspect that the script options are simply ignored. If I use -scbt followed by the name of a nonexistent file, I don't get an error message...I just get the same behavior as when I specify a real file.
I'll be happy to buy the Pro version if I need to to get this to work, but I need to know that it *will* work.
I'll be happy to buy the Pro version if I need to to get this to work, but I need to know that it *will* work.
-
- Posts: 6
- Joined: Thu Jul 31, 2008 4:18 pm
[quote="CP"]Try putting the URL as the first parameter...
If that doesn't work then there might be a bug that needs fixing...[/quote]
Looks like a bug. My (obfuscated) command line is now:
[code]"C:\Program Files\CoreFTP\coreftp.exe" ftp://userid:password@subdomain.domain.com -u "C:\Documents and Settings\My.Name\My Documents\skeleton.jcl" -tls -A -scbt "C:\Program Files\CoreFTP\FTJ.txt" -log "C:\Program Files\CoreFTP\log.txt" -output "C:\Program Files\CoreFTP\output.txt"[/code]
All the parameters are being honored except -scbt. I've also tried -scal (which in my case would accomplish the same thing), but it's also being ignored.
The log shows a successful tls logon and file transfer:
[code]TLSv1, cipher TLSv1/SSLv3 (DES-CBC3-SHA) - 168 bit250 Transfer completed successfully.[/code]
But because the -scbt is being ignored, it's just uploading into a file and not into the internal reader.
FTJ.txt consists of a single line:
[code]SITE FILETYPE=JES[/code]
If I refer to the script as "FTJ.xtx" (i.e., a file that does not exist), I don't get an error message, which maybe hints that the entire parameter is being ignored.
If that doesn't work then there might be a bug that needs fixing...[/quote]
Looks like a bug. My (obfuscated) command line is now:
[code]"C:\Program Files\CoreFTP\coreftp.exe" ftp://userid:password@subdomain.domain.com -u "C:\Documents and Settings\My.Name\My Documents\skeleton.jcl" -tls -A -scbt "C:\Program Files\CoreFTP\FTJ.txt" -log "C:\Program Files\CoreFTP\log.txt" -output "C:\Program Files\CoreFTP\output.txt"[/code]
All the parameters are being honored except -scbt. I've also tried -scal (which in my case would accomplish the same thing), but it's also being ignored.
The log shows a successful tls logon and file transfer:
[code]TLSv1, cipher TLSv1/SSLv3 (DES-CBC3-SHA) - 168 bit250 Transfer completed successfully.[/code]
But because the -scbt is being ignored, it's just uploading into a file and not into the internal reader.
FTJ.txt consists of a single line:
[code]SITE FILETYPE=JES[/code]
If I refer to the script as "FTJ.xtx" (i.e., a file that does not exist), I don't get an error message, which maybe hints that the entire parameter is being ignored.
-
- Posts: 6
- Joined: Thu Jul 31, 2008 4:18 pm
[quote="CP"]Are you running the LE or Pro version?
I ran a quick test with Pro and it seems to be working, so it might just be the LE version doesn't support it.[/quote]
I've tried both. Just now I used the uninstall option to remove the LE version, then installed the Pro version (splash screen says version 2.1, build 1573). Same result.
If it's working for you, it's gotta be something I'm doing wrong, I just can't see what...the file gets uploaded, the options way out at the end of the command are honored, it's just that one that's getting ignored.
I ran a quick test with Pro and it seems to be working, so it might just be the LE version doesn't support it.[/quote]
I've tried both. Just now I used the uninstall option to remove the LE version, then installed the Pro version (splash screen says version 2.1, build 1573). Same result.
If it's working for you, it's gotta be something I'm doing wrong, I just can't see what...the file gets uploaded, the options way out at the end of the command are honored, it's just that one that's getting ignored.
-
- Posts: 6
- Joined: Thu Jul 31, 2008 4:18 pm
[quote="CP"]I added the -s parameter and put the URL at the beginning of the command line.[/quote]
Like this?
---
"C:\Program Files\CoreFTP\coreftp.exe" ftp://<userid>:<password>@machine.domain.com -u "C:\Documents and Settings\My.Name\My Documents\skeleton.jcl" -tls -A -scbt "C:\Program Files\CoreFTP\FTJ.txt" -log "C:\Program Files\CoreFTP\log.txt" -output "C:\Program Files\CoreFTP\output.txt" -s
---
I did that many, many times yesterday and it didn't work once. I did the exact same command today after reading your post (I actually have it in a batch file) and it worked. Repeatedly.
The -s parameter does seem to be essential, though I'm not sure why that should be the case. It's certainly not a *problem*!
Thank you!
Like this?
---
"C:\Program Files\CoreFTP\coreftp.exe" ftp://<userid>:<password>@machine.domain.com -u "C:\Documents and Settings\My.Name\My Documents\skeleton.jcl" -tls -A -scbt "C:\Program Files\CoreFTP\FTJ.txt" -log "C:\Program Files\CoreFTP\log.txt" -output "C:\Program Files\CoreFTP\output.txt" -s
---
I did that many, many times yesterday and it didn't work once. I did the exact same command today after reading your post (I actually have it in a batch file) and it worked. Repeatedly.
The -s parameter does seem to be essential, though I'm not sure why that should be the case. It's certainly not a *problem*!
Thank you!