From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_05,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Xref: utzoo comp.sys.hp:6054 comp.lang.ada:4232
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!mucs!liv-cs!rkl
From: rkl@anduin.cs.liverpool.ac.uk
Newsgroups: comp.sys.hp,comp.lang.ada
Subject: Problems with Alsys Ada + HP 9000/800 + HP-UX 7.0
Message-ID: <1990Aug29.165204.16042@anduin.cs.liverpool.ac.uk>
Date: 29 Aug 90 15:52:04 GMT
Organization: Computer Science, Liverpool University
List-Id: <comp.lang.ada>

We are trying to run Alsys Ada on an HP UNIX box as follows:

Machine:          HP9000/850
OS:               HP-UX 7.0
Compiler Version: A.04.35

The installation of the compiler seemed to go smoothly, but when more
than one person attempts to create a user library (using the "ada.mklib"
command), then it appears that the first person to successfully create a user
library "locks out" the others and actually becomes the temporary 'owner'
of the system libraries (in particular predeflib and alternate in the
'installation' family). Any further attempts to create a user library by
any other user (except the new 'owner') fail until the new 'owner' removes
his user library (with "ada.rmlib"). Unfortunately, the behaviour of this
locking is erratic and it can take 4 users creating 3 user libraries each
to show up the problem on one day or just 2 users with 1 user library
each on another day.

Fixes that I've tried and failed with:
1) Re-installing the compiler (either by just running HP's "customize"
   script supplied with their release of Alsys Ada or redoing the stuff
   from scratch).
2) Using the "ada.protect -r" command to set the predeflib and alternate
   libraries to Read_Only (they're strangely shipped with Update_Allowed)
   ...this makes no difference either way.
3) Running on a different 800 series model (a 635) or trying the 300 series
   copy of Alsys Ada A.04.35. Doesn't seem to make any difference again.

My question is this: has anyone else with a similar setup had problems like
this with Alsys Ada ? And if you have, can you please supply any workarounds
that you have (preferably to me directly) ?

Richard K. Lloyd,       *** This is a MicroVAX II running VAX/VMS V5.3-1 ***
Computer Science Dept., * JANET     : RKL@UK.AC.LIV.CS.AND or              *
Liverpool University,   *             RKL@000010500211.FTP.MAIL            *
Merseyside, England,    * Internet  : RKL%and.cs.liv.ac.uk@cunyvm.cuny.edu *
Great Britain.          ***       Please note: New e-mail address !      ***