Bill, Why didn't you stop at Universe?
Why go to Unidata? Universe has a "Pick" flavor that runs D3 almost just like D3 runs D3. Out TAPE.DUMP and TAPE.LOAD programs move all the files in an account directly from D3 to Universe in two simple steps. Our UvSpoolerPlus provides a generic Pick spooler for generic Pick software like D3 software running on Universe. The only conversion issues we faced recently in converting software from R91 to Universe were related to the syntax of the CONVERT statement and the fact that Universe is not comfortable comparing the numeric value of an alpha string with that of another alpha string - eg. IF "ABC" > "XYZ" THEN etc. ( I can't understand why :)!). We're in the process of porting UvSpooler Plus to Unidata, as UdSpoolerPlus. Would UdSpoolerPlus help your D3 software feel more at home with a D3-like spooler and D3-like spooler commands? Would UdSpoolerPlus eliminate your need to re-program all of the print programs and procs in the D3 software? Please call me if we can be of assistance. Rgds, Dave Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (C) 310-561-5200 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated EDI Translation and DataSync Integration www.sysmarkinfo.com ----- Original Message ----- From: "Bill Haskett" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, March 16, 2006 7:39 PM Subject: RE: [U2] [UD] Triggers > David: > > Answers below. > > > -----Original Message----- > > From: David Wolverton > > Sent: Thursday, March 16, 2006 11:36 AM > > To: 'Bill Haskett'; [email protected] > > Subject: RE: [U2] [UD] Triggers > > > > What was the driving force to move from D3 to UniData? > > According to our client: > > 1) They want the IBM name, > 2) D3 costs too much, > 3) Support isn't what it should be, > 4) D3 is less than stable, > 5) Raining Data is treading water. > > > How difficult was the move - was it all green screen with > > source code or more difficult? > > It wasn't that difficult. The biggest problems were UniData is like > interfacing with Microdata in 1982...it's a time warp! The UniData > environment is excruciatingly tedious and the lack of MV enhancements is > what I'd expect from mvBASE (an end-of-line product). These issues cause > our conversion to extend from about 30 man-days to close to 150 man-days. > > Those who use UniData have no clue about the issues with conversion. Why > anyone involved with UniData wouldn't want it to be used by others is beyond > my comprehension. > > > How did you actually DO the move - it's not like D3 files > > will copy at any high level to UniData! > > They actually do. Colin has had success with "ACCOUNT.RESTORE" while I > copied to UniVerse then to UniData (of course this digression did take about > 10 man-days). > > > How long did it take to make the move (physically, once you > > worked out the kinks)? > > We have about 4 man-months into this. We estimate if UniData had taken > steps to update itself and provided a few utilities to assist in conversions > we would have only taken about one man-month (30 days isn't bad for an > enterprise application conversion). > > > Thanks -- I'm sure there are others here who would be > > interested in knowing more about your migration... > > > > David W. > > > > -----Original Message----- > > From: Bill Haskett > > Sent: Tuesday, March 14, 2006 7:44 PM > > To: [email protected] > > Subject: [U2] [UD] Triggers > > > > I've converted a client's system from D3 to UniData and > > everything mostly works fine. One of the last items I > > have to deal with are triggers. > > [snipped] > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
