Re: Migrating app from 3.2v4.2 to OpenServer 5.0.7?
From: Abid Khan (akhan_at_att.net)
Date: 05/09/03
- Next message: Enrique Arredondo: "SCO 5.0.5 , can't ping to router!!"
- Previous message: Brian K. White: "Re: 5.0.6a streams leak - HELP"
- In reply to: Brian Lavender: "Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Next in thread: Brian Lavender: "Re: Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 9 May 2003 07:58:15 -0700
Brian Lavender <brian@brie.com> wrote in message news:<j6mmbvodp2ma9hlba7pvetrbols7e5d6cn@4ax.com>...
> I have an orthodontics application running on 3.2v4.2 This is somewhat
> similar to another post, but a different approach.
>
> Should I:
>
> 1. Try to build another 3.2v4.2 box
> 2 Convert the app to 5.0.7
> 3. Run it under Linux-ABI
>
> I am thinking that there might be issues that could cause this to be
> somewhat difficult. Here's what I have. This is an old (still useful)
> terminal based application along with some dumb terminals and some
> logins through the TCP/IP network.
>
> The OrthoTrac system uses user ID's 200 through 240. It also has these
> users in the group called group which has a gid of 50. Are these
> uid/gid's reserved on the new version of Openserver?
>
> The app talks directly to the printer through the parallel port, and
> it looks like the app has /dev/slp1 hard coded into it in various
> areas. It also communicates with two serial based printers. The
> application talks directly to the device with its own drivers. Is
> /dev/slp1 still the device name of the printer on parallel port one?
> Am I going to have to tweak 5.0.7 to allow this direct device access?
> In fact, it seems wierd that this is the device name on 3.2v4.2,
> unless I got misinterpreted something somewhere.
>
> The app looks as if it forks, or calls another process that wants to
> write to the /dev/tty. In fact, the .profile for the ortho user
> executes a command that adds write privilege to all the /dev/tty*. Is
> /dev/tty* still the name of the pseudo terms in 5.0.7. I have had some
> problems with Linux's /dev/pts/* pseudo terminals.
>
> I am almost thinking that maybe I ought to build/obtain a box that is
> running 3.2v4.2 and use it as a failover. The app is working fine.
> It's just that there is no other server available if this one fails.
>
> I am most familiar with Linux, so I have been working with the
> application on Redhat 8 using ABI. THe cobol runtime seems to run
> well, but there seems to be problems with the way the software is
> accessing the hardware. I haven't seen any segfaults, but I can't seem
> to get strace to follow child processes, so it's hard to see where
> the app fails under Linux.
>
> brian
> --
> Brian E. Lavender
> http://www.brie.com/brian/
>
>
>
> brian
Hello Brian,
I have supported quite a few Healthcare applications, upgrade is never
been a straight forward deal even if you upgrade to the same OS
version level, because most of the installations are cutomized and
have programs, data, scripts, shells all over the places as well as
customized device nodes, etc, I would build a 5.0.7 test server, take
a good notes of printers and terminals device names, interface and
model and make a master backup of 3.2.4 machine and restore on a
temporary location in 5.0.7, create appropiate directories, copy over
the apps/data create user account with the appropiate rights and test,
test and test, create device nodes as needed or try to use existing
ones if possible, just remember you have to do lots of tweaking to get
it right.
Good luck..
Abid
- Next message: Enrique Arredondo: "SCO 5.0.5 , can't ping to router!!"
- Previous message: Brian K. White: "Re: 5.0.6a streams leak - HELP"
- In reply to: Brian Lavender: "Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Next in thread: Brian Lavender: "Re: Migrating app from 3.2v4.2 to OpenServer 5.0.7?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
