profile OR userprofile files.Įxample for setting environment variables (for ksh / bash):Įxport DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.optĮxport DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 Make sure the required environment variables are appropriately exported from the. Use one of the following methods to start ibmslapd appropriately and have the DB2 acquire the required environment variables from the. This causes issues with DB2 (in TDS system) being aware of TSM. In turn if DB2 also gets started during this step by ibmslapd, the required TSM related environment variables will not be set into DB2. If ibmslapd is started by the root user then neither the instance's profile nor the userprofile files are sourced into ibmslapd. If DB2 is already started, ibmslapd will just proceed. During the start of ibmslapd, ibmslapd also starts the associated DB2 instance. When using the default ldap ports (389 and 636), ibmslapd must be started as the root user. On a Tivoli Directory Server system, the ldap server (ibmslapd) stores all its data into its own backend DB2 database on the same system. When DB2 gets started as the instance owner, the database will have all the required environment variables properly set. profile or even in the DB2 instance's userprofile file.

The common practice is to set these TSM related environment variables in the DB2 instance's. Then DB2 can perform TSM related functions appropriately. In order to make DB2 aware of Tivoli Storage Manager (TSM), certain environment variables need to be set before starting DB2.

Tradeskillmaster profiles