MAX REMOTE ACTIVE field (MAXDBAT subsystem parameter)
The value of the MAXDBAT subsystem parameter specifies the maximum number of database access threads (DBATs) that are allowed to be concurrently active.
| Acceptable values: | 0 - 19999 |
|---|---|
| Default: | 200 |
| Update: | option 19 on panel DSNTIPB |
| DSNZPxxx: | DSN6SYSP MAXDBAT |
The total number of threads accessing data concurrently is the sum of the value of the MAX USERS field and this field, MAX REMOTE ACTIVE. The maximum allowable value for this sum is 20000. If a request for a new connection to Db2 is received and MAX REMOTE ACTIVE has been reached, the resulting action depends on the setting of the DDF THREADS field on panel DSNTIPR.:
| If DDF THREADS is ... | Action taken is ... |
|---|---|
| ACTIVE | The allocation request is allowed but any further processing for the connection is queued waiting for an active database access thread to terminate. |
| INACTIVE | The allocation request is allowed and is processed when Db2 can assign an unused database access thread slot to the connection. |
Setting MAXDBAT to 0
You can use a 0 in this field to restrict DDF server activity on a member of a data sharing group, with the following results:
- DDF does not register the member with WLM for member-specific sysplex routing. This does not prevent the member from using WLM for enclave prioritization, but it prevents WLM from including this member in the Sysplex routing data that is sent to remote sites.
- In an SNA network, DDF does not register the member's LU name with the VTAM® generic LU name during DDF startup. This causes VTAM generic resource connections to be directed to Db2 members that specify a MAX REMOTE ACTIVE value of greater than 0.
- In a TCP/IP network, DDF does not listen on the DRDA SQL port. This means TCP/IP SQL connections can be accepted only by members that specify a MAXDBAT setting greater than 0.
- DDF rejects requests for the sysplex routing TPN with the following sense code: SNA TPN not available.
- MAX REMOTE CONNECTED (CONDBAT) is lowered to zero by default if it is not set explicitly.
- Db2 will still accept inbound Automatic Resynchronization requests.