4GL Programs fail on other UNIX Machines UNless

I wonder if anyone has experienced this before; this is a situation where 4GL programs crash unless run under the username of the author of the 4GL program. This is SCO Platform where INFORMIX is concerned; host1 running informix on SCO; then directories are tar'd and xvf'd on host2; host1 is then de-commissioned/cannibalized/gone. On host2 programs crash; INFORMIX is looking for GIDs and UIDs or Usernames or Both?? Now what we have to do is run the programs only as the original user who wrote the 4GL program. If we don't login as that user, the db and 4GL crash. How can we change the informix 4GL progrs so that all programmers from group 'programmers' can ALL run the 4GLs under their own login? -- Please cc: response posts to joeh@adm.com if possible as I do not always have access to server; thanks! Disclaimer: opinions not representative of my employers

Any errors associated with this? What are the permissions on the executables / forms? John Carlson Informix DBA WHSmith USA joeh wrote: > > I wonder if anyone has experienced this before; this is a situation where > 4GL programs crash unless run under the username of the author of the 4GL > program. > This is SCO Platform where INFORMIX is concerned; host1 running informix on > SCO; then directories are tar'd and xvf'd on host2; host1 is then > de-commissioned/cannibalized/gone. On host2 programs crash; > INFORMIX is looking for GIDs and UIDs or Usernames or Both?? Now what we > have to do is run the programs only as the original user who wrote the 4GL > program. If we don't login as that user, the db and 4GL crash. How can we > change the informix 4GL progrs so that all programmers from group > 'programmers' can ALL run the 4GLs under their own login? > > -- > Please cc: response posts to joeh@adm.com if possible as I do not always > have access to server; thanks! > Disclaimer: opinions not representative of my employers

joeh wrote: > I wonder if anyone has experienced this before; No. > this is a situation where 4GL programs crash unless run under the > username of the author of the 4GL program. When you say 'crash', in what way do they crash? What is the error message? Is there a core file? > This is SCO Platform where INFORMIX is concerned; host1 running > informix on SCO; then directories are tar'd and xvf'd on host2; Presumably host2 is also running SCO? And has at least an I4GL RunTime software licence installed on it. You must have the relevant software (including licence) on the machine for the I4GL programs to run at all. > host1 is then de-commissioned/cannibalized/gone. I hope someone looked after the source code! > On host2 programs crash; > INFORMIX is looking for GIDs and UIDs or Usernames or Both?? Unless the program is written to do something else, Informix programs run as the real UID of the person who runs them. The effective UID of SUID programs is ignored (for hysterical raisins, of course*). So, we're going to need to know the nature of the crash and the error messages. > Now what we have to do is run the programs only as the original > user who wrote the 4GL program. If we don't login as that user, > the db and 4GL crash. The database crashes? That's fancy. You are going to need to look rather carefully at the installation. It begins to sound as if the Informix database software is mis-installed, possibly with the miscreant original programmer as the owner of the Informix software. > How can we change the informix 4GL progrs so that all programmers > from group 'programmers' can ALL run the 4GLs under their own login? Hmm; that's a long group name. I wonder what happens if you stick with 8-character IDs - the traditional limits. Anyway, you can ensure that the programs belong to group 'programmers' and the permissions on the programs are 755 or 750 or 555 or whatever; the permissions need to let the group execute but not modify the programs. Long user names and group names could be a genuine source of the problems if your problems are core dumps. Please provide the missing information - the details of how the programs crash, and also the software version number information. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h> * For 'hysterical raisins', read 'historical reasons'.

Jonathan Leffler <jleffler@earthlink.net> wrote: [snip] > >* For 'hysterical raisins', read 'historical reasons'. > Wow, now that's what I call non-destructive spell checker ! Yours, Andrej Falout, Product Manager, CSI Ltd New Zealand www.maximise.co.nz afalout@csi.co.nz ICQ 7628616 ++64 21 607517 #----------------------------------------------------------------- globals "std_disclaimer.4gl" "Generally, I upset people the first time they hear me, but usually I am able to convince them of what I am doing." - Maria Callas