Re: IECC - Problems viewing Unix DB

David, Thanks for your reply. I have tried all of your suggestions and now have some success. I can now select the dbserver on the LHS under Informix Neighbourhood and can select the Databases. This lets me get at the stored procedures and table/trigger information. However - I still can not get at any of the options under the Spaces tab (Events, Reports, Bar Activity and Sessions). Any further suggestions would be a great help. Regards, Stephen C Manga Email: Stephen.Manga@dbgroup.co.nz Stephen@quanta.co.nz BTW - Here are my findings based on your suggestions. > 1. Double-check the port the OSAGENT is using on the Unix side (osagent is one REPLY: This does not seem to have any effect on the outcome. > 2. Whenever I do a clean install of IECC on a windows box and start IECC up for REPLY: Deleting the Servers in the Network panel and re adding them has made them visable on the LHS under Informix Neighbourhood. > 3. Don't know if this is still true with the latest revs of IECC, but it used REPLY: Don't know about this one??? On Fri, 8 Oct 1999, David Kosenko wrote: > Also sprach Stephen Manga <Stephen.Manga@dbgroup.co.nz> : > > : > :Hi all, > : > :Has any one managed to successfully set up IECC on an NT box to view their > :Informix Databases on Unix boxes? > : > :What we have done this far: > : > :1. Installed IECC on the NT box (Informix = 7.30.TC7) > :2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) > :3. Started the server agent using startsa on the Sun box > :4. Sqlhosts has been set up on the Unix box > :5. Hosts.equiv has been set up on the Unix box > :6. Setnet32 has been set up on the NT box (such that I can see the > :databases under Informix Neighborhood in the sqleditor > :7. > : > :I can see informix databases on other NT Servers, but can not see (or > :discover) any of our Unix database servers or databases. > : > :Any suggestions on what we can do / try ? > > > Couple of thoughts based on a lot of experience setting up IECC for classes I > teach: > > 1. Double-check the port the OSAGENT is using on the Unix side (osagent is one > of the daemons startsa kicks off) and on the NT side. If you run set in a dos > window and look for OSAGENT_PORT, you'll see what NT expects. You can set the > environment variable OSAGENT_PORT on your Unix box to this same value before > kicking off startsa. I haven't had the time to verify that this is absolutely > necessary or not, so it may not really matter. > > 2. Whenever I do a clean install of IECC on a windows box and start IECC up for > the first time, no matter what I've done in setnet32, it fails to find the > server running on the Unix box, even when I've confirmed that the two daemons > startsa kicks off (admagent and osagent) are running. I have found the > following process always corrects this problem: Start IECC and then dobleclick > the Control Panel (in the right pane) then Network. That brings up an applet > with 4 tabs. Choose the server tab. It may list your server already (from > setnet32 settings). Remove that entry if present. Now choose Add. When > prompted for the machine name (it will default to //NTHOSTNAME) type in the name > of your Unix host, then choose next. It will complain that no server can be > found on that box. Choose to continue anyway and click the check box indicating > that a server will be found on this box later. It will then ask for the service > name and protocol. Enter those in as appropriate (note: you can type the port > number in for the service name if you want to avoid editing the services file). > Click finish and the server should appear in the list on the Server tab. It may > be exactly the same as before - that's fine. Click OK and it will warn you that > you are about to overwrite the SQLHOSTS info in the registry; click OK to this > as well, and you will leave the applet. If you either wait a minute or exit > IECC and restart it, the server on the Unix box should now show up and be > accessible. > > I have no idea why this works. > > 3. Don't know if this is still true with the latest revs of IECC, but it used > to be that it would only work against a Unix-based server if the DBSERVERNAME > was the network protocol; using DBSERVERALIASES to list the tcp connection would > not work. > > Dave > > > >

For these options to be active, you need to be connected to the database server as user informix. In the left hand pane, right click on the server icon (should be a blue ball) and pick Connect or Connect As. Enter informix userid and password to connect to the server in admin mode. The blue ball should now have "OL" in it, indicating that the server is on-line (a gray ball indicates off-line, and a yellow "wrench" over the blue ball indicates quiescent). Dave Also sprach Stephen Manga <steve@quack16.quanta.co.nz> : : :David, : :Thanks for your reply. I have tried all of your suggestions and now have some :success. I can now select the dbserver on the LHS under Informix Neighbourhood :and can select the Databases. This lets me get at the stored procedures and :table/trigger information. However - I still can not get at any of the options :under the Spaces tab (Events, Reports, Bar Activity and Sessions). : :Any further suggestions would be a great help. : :Regards, : :Stephen C Manga :Email: Stephen.Manga@dbgroup.co.nz : Stephen@quanta.co.nz : : : :BTW - Here are my findings based on your suggestions. : :> 1. Double-check the port the OSAGENT is using on the Unix side (osagent is one :REPLY: This does not seem to have any effect on the outcome. : :> 2. Whenever I do a clean install of IECC on a windows box and start IECC up for :REPLY: Deleting the Servers in the Network panel and re adding them has made :them visable on the LHS under Informix Neighbourhood. : : :> 3. Don't know if this is still true with the latest revs of IECC, but it used :REPLY: Don't know about this one??? : : : :On Fri, 8 Oct 1999, David Kosenko wrote: : :> Also sprach Stephen Manga <Stephen.Manga@dbgroup.co.nz> : :> :> : :> :Hi all, :> : :> :Has any one managed to successfully set up IECC on an NT box to view their :> :Informix Databases on Unix boxes? :> : :> :What we have done this far: :> : :> :1. Installed IECC on the NT box (Informix = 7.30.TC7) :> :2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) :> :3. Started the server agent using startsa on the Sun box :> :4. Sqlhosts has been set up on the Unix box :> :5. Hosts.equiv has been set up on the Unix box :> :6. Setnet32 has been set up on the NT box (such that I can see the :> :databases under Informix Neighborhood in the sqleditor :> :7. :> : :> :I can see informix databases on other NT Servers, but can not see (or :> :discover) any of our Unix database servers or databases. :> : :> :Any suggestions on what we can do / try ? :> :> :> Couple of thoughts based on a lot of experience setting up IECC for classes I :> teach: :> :> 1. Double-check the port the OSAGENT is using on the Unix side (osagent is one :> of the daemons startsa kicks off) and on the NT side. If you run set in a dos :> window and look for OSAGENT_PORT, you'll see what NT expects. You can set the :> environment variable OSAGENT_PORT on your Unix box to this same value before :> kicking off startsa. I haven't had the time to verify that this is absolutely :> necessary or not, so it may not really matter. :> :> 2. Whenever I do a clean install of IECC on a windows box and start IECC up for :> the first time, no matter what I've done in setnet32, it fails to find the :> server running on the Unix box, even when I've confirmed that the two daemons :> startsa kicks off (admagent and osagent) are running. I have found the :> following process always corrects this problem: Start IECC and then dobleclick :> the Control Panel (in the right pane) then Network. That brings up an applet :> with 4 tabs. Choose the server tab. It may list your server already (from :> setnet32 settings). Remove that entry if present. Now choose Add. When :> prompted for the machine name (it will default to //NTHOSTNAME) type in the name :> of your Unix host, then choose next. It will complain that no server can be :> found on that box. Choose to continue anyway and click the check box indicating :> that a server will be found on this box later. It will then ask for the service :> name and protocol. Enter those in as appropriate (note: you can type the port :> number in for the service name if you want to avoid editing the services file). :> Click finish and the server should appear in the list on the Server tab. It may :> be exactly the same as before - that's fine. Click OK and it will warn you that :> you are about to overwrite the SQLHOSTS info in the registry; click OK to this :> as well, and you will leave the applet. If you either wait a minute or exit :> IECC and restart it, the server on the Unix box should now show up and be :> accessible. :> :> I have no idea why this works. :> :> 3. Don't know if this is still true with the latest revs of IECC, but it used :> to be that it would only work against a Unix-based server if the DBSERVERNAME :> was the network protocol; using DBSERVERALIASES to list the tcp connection would :> not work. :> :> Dave :> :> :> :> :