Differences Between Windows And UNIX

Figure 14: Differences Between Windows and UNIX

The DB2 implementation on Windows is multi-threaded. AswithUNIX, there

are three distinct functional groups, but they are implemented as threads. All

threads run within the Windows program db2syscs.exe.

Use the Windows resource tool kit program qslice to view the threads in a

program. With this program, you can monitor the growing number of threads in

program db2syscs during SAP startup.

More information can be accessed using the Windows Performance Monitor

perfmon.exe, which is located in the administrative program group.

Except for the above mentioned differences, the implementations of DB2 on

UNIX and Windows are very similar.

DB2 environment controls many factors through the use of operating system

environment variables, DB2 registry variables, and configurable parameters at

instance and database levels.

This slide shows four different levels of configuration:

• Operating Systems:

– User Environment, User Profiles

• DB2 Profile Registry

• DB Manager Configuration

• DB Configuration

DB2 Profile Registry: db2set

• Centralized control of the DB2 environment settings

• Restart of system after changes of DB2 registry

• Various levels:

– Platform-specific environment variables

– DB2 instance-level profile registry

Variables set at this level apply only to a specific instance.

– DB2 global-level profile registry

Variables set at this level apply globally to all instances.

– DB2 instance-node-level profile registry

Variables at this level apply to a specific partition in a multi-partition

environment.

– DB2 instance profile registry

Contains a list of all instances in the system. The command db2ilist,

which lists all instances in a system, uses this registry as input.

DB2 profile registry is a centralized repository that stores most DB2 specific

environment information.

Depending on the operating system platform where DB2 is installed, variables

stored in the DB2 profile registries may be different.

List all DB2 registry variables currently set: db2set -all

Display global registry variables: db2set -g

Display instance registry variables: db2set -i <instname>

...