Re: Getting Command Center to connect

Michael L. Gallagher wrote: > > Bryan Tonnet wrote: > > > > In <5sar58$b9v@cssun.mathcs.emory.edu> mgallagh@motown.lmco.com > > ("Michael L. Gallagher") writes: > > > > >Hi, I'm trying to get Command Center on Win 95 to connect to OnLine > > >Workgroup Server running on Solaris 2.5.1. I've got these two > > Did you run osaedit from the informix/bin directory on the Win95 > > client? > > This will probably do the trick, if you've skipped this (obscure) > > step. > You can also modify the startup parameters for > sagent > in the startsa script on the server (informix/bin, I think). > > > This sounds great, but I don't have either of the binaries that you > describe. Did I lose something by accident? > -- :) Always the way, isn't it? From memory, osaedit (I think this is the correct beastie) lives in $INFORMIXDIR/bin on the client (Win95 or whatever). If you don't have that, then you don't have a complete installation of the Command Centre (at least, in the version I have which is either 1.0 or 1.1.) I'm going from memory, so please take everything I say with suitable scepticism) On the server side, startsa is a shell script which calls sagent. These two are either in $INFORMIXDIR/bin or $INFORMIXDIR/etc. My version of OWS was also bad mannered enough to try and insert lines into inittab to call up sagent on boot, so you might also look there. The inittab line (and associated rc.IFXsomething) don't even use startsa, and just call sagent directly. I noticed that Joe (Lumbley) also pointed out that sagent doesn't ship with ODS. This is certainly true, but OWS should have it, seeing as how it also doesn't ship with onmonitor and the Command Centre is the non-command line admin tool. Once again, good luck. Bryan Tonnet batonnet@phase4.com.au