gnb@bby.oz.au (Gregory N. Bond) (02/05/90)
This may be my nomination for brain-damage-of-the-month award:
Ingres/Net, vers 5.0/04, on Sun 3 and Sun 4 machines. The database is
on a Sun 4 compute server.
Forms created with vifred (and hence all abf applications) are NOT
portable across architectures!!!
So if I create a form using Vifred on a Sun4, and access it using qbf
on a sun3. then qbf coredumps. Same thing if I use vifred on a sun3
and qbf on a sun4.
So you have to have duplicates of all your forms, one for each
architecture. And remember which one to ask for, depending which
machine you are logged in to. And edit each form twice, once for each
architecture. And you have to duplicate entire applications to build
binaries for both architectures.
Can someone tell me they fixed this brain-death in 6.0?? PLEASE?
And why did it take RTI support 3 weeks to not find this out???
Greg.
--
Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia
Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net
Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnbgnb@bby.oz.au (Gregory N. Bond) (02/05/90)
In article <GNB.90Feb5164436@baby.bby.oz.au> I wrote:
Forms created with vifred (and hence all abf applications) are NOT
portable across architectures!!!
So if I create a form using Vifred on a Sun4, and access it using qbf
on a sun3. then qbf coredumps. Same thing if I use vifred on a sun3
and qbf on a sun4.
Well, I just got a call from tech support. They told me that I had to
declare the architecture type (in the Ingres/Net files/ncf file)
"different" for Sun3/Sun4 machines. That has fixed the problem.
A pity they told me it had to be "same" when I installed the Sun4.....
Greg.
--
Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia
Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net
Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnbrobinson@boone.med.unc.edu (Gerard A. Robinson) (02/06/90)
A work-around for this (which will lower performance slightly) is to clear the iicompforms (I think that spelling is correct) table of the 'semi-compiled' version of the form. This code incompatibility is what's hitting you, depending upon the machine developed/used upon. You'll have to have different abf executable images anyhow, and the forms (at least for OSL frames) are embedded in the application. QBF frames in ABF may be another story. Gerard Robinson, UNC School of Medicine Office of Information Systems