Kevin:
I had a problem with SETPTR on UD v7.2.5 when I converted to Windows
2008 R2 (Windows 7 Server). I contacted Rocket, we identified the
problem as having to do with the user setptr was running under, and they
fixed the problem in v7.2.7. This all took about a month or so. I'd
say that was pretty good response.
Bill
------------------------------------------------------------------------
On 2/17/2011 5:54 PM, Kevin King wrote:
Doug... If that's working on 7.2.7/Win I'd love to know how. Things here
aren't the same as they were on 7.1. Non-Windows versions appear to be
fine. Windows versions... not so much.
Wally, my case # is 153722. It was posted through my support contacts @ S7.
Feel free to contact me off list if you need more info.
On Thu, Feb 17, 2011 at 6:42 PM, Wally Terhune
<[email protected]>wrote:
Hi, Kevin.
I don't find any support cases opened by you recently.
Can you provide a support case number so I can review your interaction with
our team and the technical bits, as well.
thanks
Wally Terhune
U2 Support Architect
Rocket Software
4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA
Tel: +1.720.475.8055
Email: [email protected]
Web: www.rocketsoftware.com/u2
-----Original Message-----
From: [email protected] [mailto:
[email protected]] 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
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
