How to remotely connect to the db2 database

How to remotely connect to the db2 database in the DB2 database, the word catalog is hard to understand. I was often confused by this cataloguing when I was learning DB2, until now, I personally feel that the term catalog (catalog) in DB2 is not very good. Specifically, catalog nodes and database. If you want to understand the cataloguing, let me briefly introduce the architecture of the DB2 database. The biggest concept in the DB2 database is the system (node), that is, the host. Below is an instance, below the instance is the database, then the tablespace, and then the database object. Now suppose you have a database server on p570, and you have a client on windows, linux, or any platform. Now you want to establish a client-to-server connection, what are the specific steps? Step 1: www.2cto.com. You must identify the remote server on the client machine. How can this problem be solved? The catalog Method Used in DB2 is to write a remote server in a local client file by cataloguing: db2 catalog tcpip node p570 remote 172.10.10.10 server 50000 in the preceding command, p570 is a node name (which must be unique on a machine), and remote is followed by the server IP address, server is the port number corresponding to the instance on the remote server. DB2 records the remote server information in the local SQLNODIR file in this way. Therefore, the cataloguing node maps the remote server to the local server, the records in SQLNODIR can be used to locate the remote server and instance, similar to the address pointer pointing to the remote server and instance. Step 2: www.2cto.com when the remote server IP address and instance are catalogued, the database under the instance should be catalogued to the local db2 catalog db REMOTEDB at node p570 in this command, REMOTEDB is the database under the remote instance, and p570 is the name of the target node. After the command is executed, the remote database information is recorded in the local SQLDBDIR file, this allows you to map the database under a remote server instance to a local alias. The preceding example shows that the client and server are not on the same machine, and the database is catalogued through the cataloguing node to connect the client to the database on the server. If the client is connected to the same machine, at this time, do not display the cataloguing nodes. However, when we create an instance on the server, there is an implicit process of cataloging the instance locally, assume that an instance named db2inst1 is created on p570. In fact, there is an implicit step of www.2cto.com db2 catalog local node db2inst1 instance db2inst1 system p570 ostype aix, similarly, when you create a database MYDB under db2inst1, there is an implicit catalog Database step: db2 catalog db mydb at node db2inst1. Now you can understand the catalog, which is the purpose of establishing a database connection from the client to the server locally or remotely.