To All:
The day is finally approaching. One of my Microdata clients is now wanting to
switch to a contemporary platform.
Because of being a Microdata, I have a fork in the road: 1) Do I pursue a
system that can run in Microdata Flavor, ie Unidata or 2) do I endeavour on the
path of either
It's been a long time since I did one of these, but UniData has a conversion
tool to switch DICTs. It's pretty good, but as always, you need to verify.
John Israel
Senior Programmer/Analyst
Dayton Superior Corporation
721 Richard St.
Miamisburg, OH 45342
937-866-0711 x44380
-Original
Hi, we did Reality to Universe years ago. The reality flavour supports
PQN and 10 item dicts, and most of the nice reality features.
Les Sherlock Hewkin
Project Manager
Group Financial Systems
I.T. Department
Ryehill House
Ryehill Close,
Lodge Way Industrial Estate,
Northampton.
NN5 7UA
T
Basically, the road ahead is wide open and the future is bright.
I've heard good things about Reality. They seem to be making a
comeback. That would be an easy move.
jbase has a reality emulation and was written by microdata people.
Both universe and unidata have reality/microdata flavors.
From: Ed Clark
With all those options, there's no reason to consider
D3 if you rely on PQN procs.
I'll agree with all of Ed's other comments - except that one.
You can get RPL for D3, which is essentially compiled PQN. All
of your F-OPEN, F-READ, and /!/%/# buffers are there, plus more.
So
Mark,
How tightly is spooler manipulation integrated into the application? I'm
wondering if compatibility will affect your decision. Aren't there some
significant differences amongst the various choices?
Russ Watson
Asynchron Systems Inc.
-Original Message-
From:
Jeff
Kicked, thanks!
(Why do these things NEVER happen when I'm IN the office...)
Brian
On 03 November 2009 at 21:22 Jeff Butera jbut...@hampshire.edu wrote:
Can anyone kick the tires on the u2ug website:
mvScript Error
The following error has been reported
1006þNo active connections
Unidata 7.1.x on Windows 2003. When trying to access AE, we get the
following:
can't get to msgq in U_tosbcs
I found one limited email thread from 2005 on this, but the solution
(correcting CTLGTB VOC pointer) was already addressed.
Any ideas?
Jeff Butera, Ph.D.
Administrative Systems
I don't think I've ever seen that reported on Windows.
Typically - the sbcs daemon (Shared Basic Code Server) is not running. On
Windows, literally sbcs.exe.
It could also indicate a problem with Windows memory mapped files - that we've
used to mimic UNIX shared memory as well as message queues.
