Planning for Your DB2 Database

Cataloging your DB2 database is done differently depending on your system setup. If your Lawson applications and your DB2 database are on the same system, the CREATE DATABASE command does the following:

  • Creates a system or local database directory if neither exists

  • Catalogs an entry in the server's system database directory. The resulting entry will contain the database name, alias, and path.

  • Catalogs the database in the server's local or volume database directory on the path indicated by the PATH parameter or in the default database path defined in the dbm configuration file.

  • Updates the client's system database directory with the database name and alias if a remote client issued the command.

The node directory is not needed on the server in this case, as everything is on the same machine.

If your Lawson applications and your DB2 database are on different systems, the applications server becomes a client to the database server. The CREATE DATABASE command on the server creates the necessary System and Volume Database Directory entries in the database server. In order for the client to communicate with the server, the following entries must be made on the client:

  • System Database Directory (via the catalog database command)

  • Node Directory (via the catalog tcpip node command)

  • Optional entries in the /etc/services file

Cataloging the DB2 Database.

User Naming Conventions

The following table explains the user or group naming conventions required by IBM DB2. Apply the correct user naming conventions appropriate for your platform.

Platform Description
UNIX IBM DB2 requires a maximum of 8 characters in a database, user, or group name. The first character of user IDs must be A-Z, #(X'7B'), $ (X'5B'), or @ (X'7C').

For more information on user naming conventions, see the IBMDB2 Security Administrator's Guide.

Limits

A complete listing of IBMDB2 limits for is available in the DB2 SQL Reference.

The complete listing of IBMDB2 limits for OS/390 is available in the DB2 for OS/390 SQL Reference.