Configuring the DB2 Network Information Center › How You Configure the Center in a New Region

How You Configure the Center in a New Region

The first time a new region starts, a program named Express Setup runs. Express Setup discovers all active DB2 for z/OS DDF address spaces on the system. (The discovery considers a DDF address space to be one that has a program name of DSNYASCP and an address space name ending in DIST.)

When Express Setup finds a DDF address space, it does these things:

• Define the DDF address space as a resource to the IP Resource Monitor. This resource definition ensures that the region collects throughput and performance data for the address space, and that you can run IP packet traces on the address space.
• Add the DDF TCP port numbers to the SMARTTRACE parameter group as DRDA ports. The identification of these ports ensures that when you view a DDF TCP/IP packet trace, SmartTrace does DRDA-specific decoding and formatting to make the trace a lot easier for you to understand.
• Add the traffic from the DDF address space to a DB2 business application name. The name enables the region to add all DDF traffic together to make it easier to compare the total DB2 TCP/IP traffic with other TCP/IP traffic.

Express Setup only discovers DDF address spaces that were active when it ran. If a DB2 subsystem or its DDF address spaces was not active or had not yet opened a socket when Express Setup ran, you can define them to the region manually.

After Express Setup has run, you check what is discovered and customize the configuration to suit your requirements:

• You can use the IP Resource Monitor to see the defined DDF address spaces (ASMON resources). Enter the FILTER DB2 command to list the address spaces. (DB2 is a distributed monitor filter.) Add any missing DDF address spaces that you want to monitor as ASMON resources of Type DB2.
• Review the DRDA ports specified in the SMARTTRACE parameter group. Add any missing ports.
• Review that the defined DB2 business application name meets your requirements. After you become familiar with all the DB2 diagnostics and traffic displays, you can replace the DB2 application name with more granular custom names of your choice. For example, you can group your traffic by DB2 subsystem version, function, geography, user, and so on).