Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!genat!clunk!bvax!rich From: rich@bvax.UUCP (Rich Chahley) Newsgroups: comp.unix.xenix Subject: GKS, INFORMIX on SCO XENIX Message-ID: <241@bvax.UUCP> Date: Mon, 22-Jun-87 00:11:07 EDT Article-I.D.: bvax.241 Posted: Mon Jun 22 00:11:07 1987 Date-Received: Tue, 23-Jun-87 06:45:11 EDT Organization: Bell Canada, Toronto, CANADA Lines: 37 Keywords: GKS, INFORMIX, C-ISAM Further to my posting on June 4, I have received numerous requests for info on GKS. For the benefit of all, the packages we are using are listed below: GKS/C Ver 2.3 (for SCO XENIX) Prior Data Sciences 240 Michael Cowpland Drive KANATA, Ontario Canada K2M 1P6 +1 613-591-7235 INFORMIX C-ISAM Ver 3.1 (for SCO XENIX) Informix Software 4100 Bohannon Drive MENLO PARK, CA USA 94025 +1 415-322-4100 As posted before, we are currently experiencing problems when using the multiscreen feature with XENIX (where - brings up a new screen). This is somehow related to GKS. We also ran into a mitful of problems when GKS, INFORMIX C-ISAM is linked together with our application software developed in-house. The problem is with the stack space for the "near data segment" in XENIX. Apparantly the near data segment includes the uninitialized data and string constants and cannot exceed 64k. The quick work-around is to move the string constants from the application software out of the d-segment. I'm not sure what the long term fix will be (according to SCO, a long term fix is somewhat messy and $$$). I will post any other findings as they become known. In the meantime, I would appreciate any feedback or comments (if any) on the above. Richard Chahley Corporate Engineering (Planning & Standards) Bell Canada {ihnp4, allegra, watmath, decvax} !utzoo!bnr-vpa!bnrnuns!ngpt!rich