Kevin just create a script and execute it. This is fairly simple and you
can capture the output from the _PH_ file. We have a public warehouse
application that uses EDI to talk with lots of different customers. This
process is their life blood and works like a champ from 6.0 to 7.2.7 of
Unidata.
ITEM = 'open ftp1.com'
ITEM<-1> = 'user dave...@u2logic.com'
ITEM<-1> = 'daverch7777'
ITEM<-1> = 'bin'
ITEM<-1> = 'cd inbox'
ITEM<-1> = 'lcd c:\IBM\ud72\WH.DATA\WH.EDI'
ITEM<-1> = 'put ':EDI.ID
ITEM<-1> = 'quit'
WRITE ITEM ON HOLD,'ftp_send.txt'
TEMP = 'c:\IBM\ud72\XLr8\_HOLD_\'
LINE = "!ftp -n -d -s:\:TEMP:\ftp_send.txt"\
EXECUTE 'PHANTOM ':LINE CAPTURING OUTPUT
Regards,
Doug
www.u2logic.com
"A plethora of SMB applications all 100% Web based"
-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Thursday, February 17, 2011 5:48 PM
To: U2 Users List
Subject: [U2] Frustrated with Rocket / Unidata 7.2
About a week ago I upgraded Unidata 7.1 on Windows XP/32 to Unidata 7.2 on
Windows 7/64. Everything I need in Unidata seems to work fine on this
release with one notable exception: Unidata 7.2 on Windows will no longer
properly execute the Windows ftp program. Rocket support has basically said
that in this version they changed the telnet server so that it can only run
fully stdin/stdout compliant programs in the shell. Because the Windows ftp
program isn't exactly stdin/stdout compliant, it is no longer a functional
PCPERFORM program. Even if the ftp program is scripted to connect,
transfer, and exit with no additional inputs or outputs, the ftp program
will still fail. Of course, in this case if there's a put in the commands
it'll fail after writing a zero byte file, potentially overwriting
something.
I could be frustrated with Microsoft because, after all, it's their program
that's failing, I'm more frustrated with Rocket. While it's frustrating to
have a past ability removed it's more frustrating to have received
absolutely zero warning from Rocket that this could happen. I've searched
the docs for 7.2... can't find a word about this change. (Hey, and I could
be missing something; that's certainly a possibility.)
It's fortunate that this install isn't a big production system, but what if
it was? There are several production systems running Unidata on Windows, so
if any of y'all are using ftp or any OS commands that may not meet Rocket's
muster, please be aware of this change in 7.2.
BTW, for me the fix was to use WinSCP (in command line mode) instead of
Microsoft's FTP program. So far it seems to work just fine though the
scripting is a bit different from Microsoft's ftp client.
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
