🚀 go-pugleaf

127.0.0.1 is the IP loopback address. So yes, it's using the address
because DB2 is installed on the same machine as your browser (the host
name entry that matches this is probably "localhost"). That name may
appear in HOSTNAME or (more likely) the hosts file in the etc directory.

As to the Netscape problem, the following might help (but I'd have to
check my reference materials to be sure -- so someone else jump in if
I'm wrong). You're jdbc classes are listing the net drivers, e.g.
COM.ibm.db2.jdbc.net.DB2Driver.connect

If I remember correctly, those drivers work through the database client
programs installed on your system. Netscape may not be able to access
those because of security limitations. One approach that should work (I
haven't actually used this approach yet because we don't [yet] need
browser access for our apps) would be changing to the applet drivers
(which, again from memory so it may be wrong) would look like:
COM.ibm.db2.jdbc.app.DB2Driver.connect

Note that you're DB2 server would need to be configured to serve JDBC
applets. I'm not sure whether that is the default or not.