Cataloging an IBM DB2 OS/390 Database

To catalog an IBM DB2 for OS/390 database from a remote IBM DB2 Connect machine, issue the following commands from the DB2 Command Line Processor (CLP). The table below describes the variables within the commands.

  • catalog tcpip node aaaaaa remote bbbbbb server 999

  • catalog db xxxxxx at node aaaaaa authentication dcs

  • catalog dcs db xxxxxx as zzzzzz

    Variable Represents
    aaaaaa The local alias (an arbitrary name) for the node to be cataloged. This is used to identify the node on the client platform.
    bbbbbb The host name of the node where the target database resides. On IBM DB2 for OS/390 databases, the host name is defined in TCP.HOSTS.LOCAL with the HOST parameter.
    999 The TCP/IP port address as defined within the TCPIP.PROFILE.TCPIP and in the IBM DB2 for OS/390 DSNZPARMS sub-parameter "PORT=999".
    xxxxxx The database name defined within the IBM DB2 for OS/390 Subsystem associated with the parameter zzzzzz.
    zzzzzz The IBM DB2 for OS/390 Subsystem DDF location name defined within the DSNZPARMS DDF sub-parameter "LOCATION=zzzzzz".

Examples of Cataloging the Database

The examples in this section help you understand how to catalog an IBM DB2 for OS/390 database. Examine the information in the following table to understand the command syntax in both examples.

DB2 Subsystem DDF Location Database Name TCP/IP Port Address
zzzzzz xxxxxx 999
DB2P DSNP390 PROD01 446
DB2T DSNT390 TEST01 449
DB2T DSNT390 TEST02 449
DB2T DSNT390 TEST03 449

  • Example 1 

    catalog tcpip node NTBOX1 remote MAINFRAME server 446
catalog db PROD01 at node NTBOX1 authentication dcs
catalog dcs db PROD01 as DSNP390

  • Example 2 

    catalog tcpip node NTBOX1 remote MAINFRAME server 449
catalog db TEST02 at node NTBOX1 authentication dcs
catalog dcs db TEST02 as DSNT390