IBM Books

Quick Beginnings


Planning to Configure Your DB2 Connect System

For an OS/390, MVS, VSE, or VM connection, do the following:

  1. For XID node ID, determine the IDBLK and IDNUM of the DB2 Connect workstation ((13) plus (14)).
  2. For Network name, determine the network name of both the host and the DB2 Connect workstations ((1) and (9)). Usually these values will be the same.
  3. Determine the control point name of the DB2 Connect for HP-UX workstation ((10)). This is usually the same as the PU name for the system.
  4. Leave the token ring profile name blank for now.
  5. For mode name, usually the default is sufficient ((6) and (15)).
  6. Determine the local LU name to be used by DB2 Connect ((11)).
  7. For Local LU alias ((12)), you usually use the same value as for the local LU name ((11)). This helps to avoid confusion.
  8. Repeat steps 6 and 7 above for any additional LUs that you may need to define.

For an OS/400 connection, complete Table 46 as follows:

  1. For XID node ID, write an asterisk (*). This means that you will use the default.
  2. For Network name, use the Network ID ((1)).
  3. For Mode name, use your value for ((6)).
  4. Leave the other items blank for now.

Planning for Each Server Connection

For each server that you are connecting to, fill in a copy of the example worksheet Table 18 as follows:

  1. For Link station profile name ((7)), choose a suitable value.
  2. For Remote link address ((8)), determine the controller address or local adapter address of the target host.
  3. For Symbolic Destination name ((16)), choose a suitable value.
  4. For Partner CP name, use (4). For OS/390, MVS, VM, or VSE it is the System Services Control Point (SSCP) name. For an AS/400 it is the local control point name at the AS/400. See Table 46.
  5. The remote (partner) LU name for OS/390, MVS, VSE, or VM ((2)), is the VTAM application (APPL) name. You will also need to provide the network name for the remote node ((1)). (For example, SPIFNET.NYM2DB2). Usually the host network name is the same as the network name of the DB2 Connect workstation ((9)). For OS/400, use the local CP name.
  6. For Application transaction program ((17)), the default is X'07F6C4C2' for OS/390, MVS and OS/400, and the RDB_NAME for VSE and VM. We recommend you use DB2DRDA for OS/390 and MVS.
  7. For database name ((5)), provide the name of the host database. This is the LOCATION NAME for OS/390 or MVS, the RDB_NAME for VM or VSE, or a relational database name for OS/400.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]