Re: 4GL 4.0.UH1 Compiler on Sun SPARC (I'm not impressed)...

Path: emory!swrinde!cs.utexas.edu!usc!orion.oac.uci.edu!unogate!genisco!lawnet!dpdvax!pride386!odetics!uunet!uunet!europa.asd.contel.com!darwin.sura.net!wupost!unlinfo.unl.edu!price From: price@helios.unl.edu (Chad Price) Newsgroups: comp.databases.informix Message-ID: <387.2985a594@dpd.com> Date: 31 Jan 92 15:34:05 GMT You write: >Subject: 4GL 4.0.UH1 Compiler on Sun SPARC (I'm not impressed)... >X-Informix-List-Id: <newsgate.662> >Originator: dvadura@plg.waterloo.edu >[Actually I am uncertain if I have the number uptop correct the compiler > it was purchased new on Jan 4th.] >I have several gripes about the compiler that I feel important enough raise. >I find these inexcusable considering the amount of money that is dished >out for this product (I may be willing to accept them if it had cost a $100). >1. 4GL variable names may conflict with C reserved words. The following > program fails during the cc pass. . . This problem is not confined to 4GL. It also exists with the data-dictionary / report (ACE) writer interface. Data elements can be created with the ISQL interface which cannot be used in reports because of similar naming convention problems. >2. The documented and supported method of calling report routines is to use > the construct: > output to report report_fun_name(args...) > but if instead you write: > call report_fun_name(args...) > the compiler compiles the source without any warning or errors but dumps > core when run. Whats more the 4GL RDS system will happily execute the > above incorrect invocation and appears to produce correct results although > I am now not convinced that results were a 100 percent accurate. >3. I see no reason for the requirement that the parent directories of the > directory containing the database have permitions 755 or higher. This > is inexcusable. I want to put the database into a directory, say > /u/database/live > where the permisions and ownership are as follows: > /u root 755 > /u/database informix 755 > /u/database/live informix 755 > as it stands now I have to make /u owned by informix or I can't seem to get > grant or revoke to work for other users. I am confident of points 1 and 2, point 3 I am not so sure about. If anyone ... For this one, the not so obvious answer is to use (for example) 700, and then carefully grant individuals the appropriate permissions using the SQL "grant" statement. My experience on AT&T 386's running Sys V, rel 3.2 2.1, indicates that this works. The key is to use the Informix grant, ensure that the database is created by and owned by user "informix", and allow Informix to do it. Thus, you must login as user "informix" to make it all work. chad price price@helios.unl.edu Message-ID: <price.696104648@helios> Sender: news@unlinfo.unl.edu Nntp-Posting-Host: helios.unl.edu Organization: University of Nebraska - Lincoln Date: 22 Jan 92 18:24:08 GMT