Administration Guide

Attributes of Each Object Class

In the DCE environment, each object and object attribute is identified by an object ID (OID). Each OID is obtained from a hierarchy of allocation authorities, where the highest authority is the International Organization for Standardization (ISO).

Table 55 shows the attributes for each object class and Table 56 shows their attributes.

Table 55. Object Attribute Classes

Object Class Object ID (OID) Required Attributes Optional Attributes
(DB) Database_Object 1.3.18.0.2.6.12 DAU, DOT, DDP, DNN DCO, DPN, DRL, DLN, DCP, DPR
(DL) Database_Locator_Object 1.3.18.0.2.6.13 DOT, DCP DCO, DPN, DRL
(RI) Routing_Information_Object 1.3.18.0.2.6.14 DOT, DTI DCO, DPN, DRL

Object Class	Object ID (OID)	Required Attributes	Optional Attributes
(DB) Database_Object	1.3.18.0.2.6.12	DAU, DOT, DDP, DNN	DCO, DPN, DRL, DLN, DCP, DPR
(DL) Database_Locator_Object	1.3.18.0.2.6.13	DOT, DCP	DCO, DPN, DRL
(RI) Routing_Information_Object	1.3.18.0.2.6.14	DOT, DTI	DCO, DPN, DRL

Table 56. Object Class Attributes

Attribute Name OID Minimum Length Maximum Length Syntax
(DAU) DB_Authentication 1.3.18.0.2.4.39 1 1024 Char
(DCO) DB_Comment 1.3.18.0.2.4.30 1 1024 Char
(DCP) DB_Communication_Protocol 1.3.18.0.2.4.31 1 1024 Char
(DDP) DB_Database_Protocol 1.3.18.0.2.4.32 1 1024 Char
(DLN) DB_Database_Locator_Name 1.3.18.0.2.4.33 1 1024 Char
(DNN) DB_Native_Database_Name 1.3.18.0.2.4.34 1 1024 Char
(DOT) DB_Object_Type 1.3.18.0.2.4.35 1 1 Char
(DPN) DB_Product_Name 1.3.18.0.2.4.36 1 1024 Char
(DRL) DB_Product_Release 1.3.18.0.2.4.37 1 1024 Char
(DTI) DB_Target_Database_Info 1.3.18.0.2.4.38 1 1024 Char
(DPR) DB_Principal 1.3.18.0.2.4.63 1 1024 Char

Note: Multiple values are allowed for DCP, DDP, and DTI. Only one value is allowed for the other attributes.

Details About Each Attribute

The following section describes each attribute.
Note: DCE Directory Services does not check that the entries are valid for DB2. Ensure that you enter the attributes that are required and that you enter the correct values.

DB_Authentication (DAU)

Authentication method required by the object. This attribute is required for the database object of a DB2 server. The value must be CLIENT, SERVER, or DCE.

DB_Principal (DPR)

If authentication method is "DCE", enter the DCE principal in this attribute.

DB_Comment (DCO)

For documentation purposes only.

DB_Communication_Protocol (DCP)

A multi-value attribute where each value consists of tokens that describe the network protocol supported. Examples of the network protocols are TCP/IP, APPC, IPX/SPX, and NetBIOS. (These last two are appropriate for OS/2 only.) Each token is separated by a semicolon. Do not put spaces between the tokens.

The tokens for TCP/IP are:
1. tcpip
2. Host name of the target node
3. Port number used by the object to listen for incoming TCP/IP connect requests
4. (Optional) Security can be either NONE or SOCKS.
For example: tcpip;HOSTNAME;1234
The tokens for APPC are:
1. appc
2. Network ID of the target to which to object belongs.
3. LU name where the target can be found.
4. Transaction Program Name (TPN) representing the object in the LU (For DB2 for MVS/ESA, use DB2DRDA as the TPN.)
5. Mode name
6. Type of security used by the target. The values are:
  - NONE
  - PROGRAM
  - SAME
For example: appc;NETID;TARGETLU;TPNAME;MODE;PROGRAM
Note: For APPC, the client must use its local control point (CP) as its LU name.
(OS/2, Windows NT, or Windows 95 only) The tokens for IPX/SPX are:
1. ipxspx
2. Name of the file server
3. Name of the object
For example: ipxspx;SVR_NAME;OBJ_NAME
(OS/2, Windows NT, or Windows 95 only) The tokens for NetBIOS are:
1. netbios
2. Node name of the server
For example: netbios;SVR_NNME where the client adapter number is found in either the registry value db2clientadpt or the database manager configuration parameter dft_client_adpt.
(Windows NT or Windows 95 only) The tokens for NPIPE are:
1. NPIPE
2. Computer name of the server
3. Instance name of the server
For example: npipe;computername;instance

DB_Database_Protocol (DDP)

The database protocol or protocols supported by the target database. Examples of the values are DB2RA and DRDA. The following are the cdscp commands to add two protocols.

add object /.:/subsys/database/AIXDB1 DB_Database_Protocol db2ra
add object /.:/subsys/database/AIXDB1 DB_Database_Protocol drda

DB_Database_Locator_Name (DLN)

The DCE name of the database locator object. In the database object, the name is for the DBMS instance. In the routing information object, the name is for the DB2 Connect instance.

For example, /.../CELL_TORONTO/subsys/database/AIX_INST

DB_Native_Database_Name (DNN)

The database name or alias by which the database is known within the instance containing the database. This is the name that a local application on the instance uses to connect to that database.

The name is up to 8 characters for a DB2 for Universal Database database. For other databases, the length of the name may be different. For example it can be up to 18 characters for databases on DB2 for MVS/ESA.

DB_Object_Type (DOT)

The type of object. This attribute is required for all objects and can be one of the following:

D: Database object
L: Database locator object
R: Routing information object

DB_Product_Name (DPN)

The identification of the product. For documentation purposes only.

DB_Product_Release (DRL)

The product release level. For documentation purposes only.

DB_Target_Database_Info (DTI)

A multi-value attribute where each value consists of a fixed number of tokens, separated by a semicolon. Do not put spaces between the tokens. The tokens must be in the following order:

Database name. The DCE name of a target database for which the routing service is provided. The value *OTHERDBS specifies a default gateway for any target databases not explicitly defined in the routing information object.
Outbound protocol from router. The database protocol used by the target database, or the database protocol the routing DB2 Connect instance uses to communicate with that target database. For example, DRDA.
Inbound protocol to router. The database protocol accepted by the routing DB2 Connect instance object. For example, DB2RA.
Authenticate at gateway. The valid values are 0 or 1. See Table 57 for more details.
Parameter string which contains information specific to the DB2 Connect gateway. The string contains tokens that must be in the order described below. The tokens are separated by commas. For tokens that are not specified, the default is used.
- Map-file name. The fully-qualified name of the SQLCODE mapping file that overrides the default SQLCODE mapping. To turn off SQLCODE mapping, specify NOMAP.
- D. The application disconnects from the DRDA server database when specific SQLCODEs are returned. Refer to the DB2 Connect User's Guide for details about the SQLCODEs.
- INTERRUPT_ENABLED. DB2 Connect will drop the connection and roll back the unit of work when a client issues an interrupt while connected to the DRDA server.
The following are some examples:
```
   NOMAP
   /u/username/sqllib/map/dcs1new.map,D
   /u/username/sqllib/map/dcs1new.map,D,INTERRUPT_ENABLED
```
Where defaults are used, use a comma to preserve the order of the tokens, for example:
```
   ,D
```
or
```
   ,,INTERRUPT_ENABLED
```
Refer to the DB2 Connect User's Guide for details about the Parameter string.
The DCE name of the DB2 Connect instance that provides the routing service.

The following is an example of the DB_Target_Database_Info:

   /.../CELL_TORONTO/subsys/database/MVSDB;\
   drda;db2ra;0;;\
   /.../CELL_TORONTO/subsys/database/GW_INST

Note:

In the above example, the back slash (\) is a line continuation character.

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

[ DB2 List of Books | Search the DB2 Books ]