I have converted a number of Universe applications from various flavors
of Unix/Linux to Windows (and vice versa) and each one presented its own
challenges, but in general:
Use uvbackup/uvrestore to do the actual transfer of the application.
This takes care of all the big vs little endian insanity and other file
system level things that you don't want to deal with anyway. You will
still have to reset all of your indexes using SET.INDEX.
Recompiling everything is easy. BASIC BP * (or whatever your basic
source file(s) may be). Deciding what and how to to re-catalog things
may be a bit more complex. Look at the VOC pointers for cataloged
programs and create select lists of globally and locally cataloged
programs then create a paragraph to re-catalog everything.
Any Unix level commands/scripts/programs will have to be recreated as
windows commands/batch files/programs. Try running the SEARCH command on
all of your UvBasic program source files and look for "SH -c" to find
things executing shell commands. Speaking of which., save this list
because you will need to change all instances "SH -c" to "DOS /C". You
may want to look into Microsoft Windows Services For Unix which among
other things implements a very nice Korn & C shell on your Windows
machine. More info here:
http://technet.microsoft.com/en-us/library/bb463212.aspx
Printers. Universe automatically creates a spooler for each printer set
up in windows however the SETPTR command does not like printer names
with spaces in them. You will also want to look through your Unibasic
source code for the SETPTR command and change printer names accordingly.
Again SEARCH is your friend.
Check your VOC for file pointers which have pathnames to other
directories. These will have to be changed to windows paths. SEARCH (I'm
noticing a trend here) for things with an "F" as the first character in
attribute 1 and a '/' as the first character on line 2.
Those are the biggest things that come to mind right now. You will
undoubtedly encounter more. Feel free to send me a question if you get stuck
Richard Conway wrote:
Thanks for that, I hadn't actually downloaded it at that point and I didn't see
it elsewhere on their web site.
My main concern is how the existing data and programs written in Unibasic
actually handle the move from a Unix environment to a Windows one. I know there
is at least one call to a Unix function that will fail, but I'm not sure about
generally how interoperable the two environments are.
Has anyone tried anything like this? If so, what are the most likely/obvious
pitfalls?
Richard
----- Original Message -----
From: Glorfield, Gordon <[email protected]>
To: "'U2 Users List'" <[email protected]>
Sent: Monday Monday 08 November 2010 19:23:21
Subject: [U2] Upgrading and Migrating from Unix to Windows
"Along with being limited to two users, the UniData and UniVerse Personal Editions
also have an eight-process limit and a limitation of modulo 10007 assigned to a file.
Also, the following add-ons do not function: Connection Pooling, EDA, NFA, RFS,
UV/Net."
Right off of Rocket's U2 downloads page.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Bob Woodward
Sent: Monday, November 08, 2010 2:08 PM
To: Richard Conway; U2 Users List
Subject: Re: [U2] Upgrading and Migrating from Unix to Windows
I think the size limit is something like a modulo of 10009 or there
abouts, if memory serves me right. It's been a long time. You should
be able to get the limitations from Rocket.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Richard
Conway
Sent: Monday, November 08, 2010 10:30 AM
To: U2 Users List
Subject: Re: [U2] Upgrading and Migrating from Unix to Windows
What are the file size restrictions with PE? Is there a comprehensive
list of the restrictions present in PE anywhere that I can
read/download?
Richard
----- Original Message -----
From: Bob Woodward <[email protected]>
To: "Richard Conway" <[email protected]>, "U2 Users List"
<[email protected]>
Sent: Monday Monday 08 November 2010 18:20:24
Subject: [U2] Upgrading and Migrating from Unix to Windows
I think, at the very least, you're probably going to have an issue with
the PE version limiting your file sizes.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Richard
Conway
Sent: Monday, November 08, 2010 5:00 AM
To: [email protected]
Subject: [U2] Upgrading and Migrating from Unix to Windows
I am about to try to upgrade an old Unidata server running Unidata 3.x
on SGI Irix, to another machine running Windows Server 2003. I am going
to set up the Windows box with Unidata 7.2.7 PE initially.
Has anyone tried such a drastic move? What is the best upgrade path to
try? Unidata 3.x on Irix to Unidata 7 on Linux, then on to Unidata 7 on
Windows? Or would a single jump upgrade actually work, with the help of
vocupgrade and PATHSUB?
Richard
_______________________________________________
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
_______________________________________________
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
--
------------------------------------------------------------------------
Jeff Schasny - Denver, Co, USA
jschasny at gmail dot com
------------------------------------------------------------------------
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
