Do DB2 "members" count as "partitions" for Agent Manager capacity? (4383065)

Do DB2 "members" count as "partitions" for Agent Manager capacity?

DB2 terminology differs by architecture (pureScale uses "member", DPF uses "partition"). The agent uses a single monPartitions table and an is_pureScale flag to adapt labels, so counting uses the table rows rather than the label.

For capacity calculations the DB2 cartridge treats members and partitions as the same monitored entity: each monitored partition/member (a monPartitions row) counts as one agent.

• Count agents as: 1 (instance) + number of monitored databases (monDatabases with monDbMonitor=true) + number of monPartitions rows.
  • Example: 1 instance + 2 DBs + 2 members = 5 agents.
• For WSFC single-partition DB2, add one monPartitions row (partition 0); do NOT add one row per physical cluster node.
• Physical nodes placed in winHostCredentials for OS monitoring are not counted as agents.
• To reduce load: disable unmonitored DBs, remove unused monPartitions rows, or add more Agent Managers.