MAX BATCH CONNECT field (IDBACK subsystem parameter)
The IDBACK subsystem parameter determines the maximum number of concurrent connections that can be identified to Db2 from batch.
| Acceptable values: | 1–20000 |
|---|---|
| Default: | 50 |
| Update: | option 19 on panel DSNTIPB |
| DSNZPxxx: | DSN6SYSP IDBACK |
Recommendation: Use
a minimum setting of 30.
Count each of the following items as a separate connection:
- Each Db2 utility.
- Each batch job that uses QMF.
- Each batch job that uses the DSN command processor.
- Each task that is connected to Db2 through
the call attachment facility, which runs in batch. Among others, this
can include:
- Batch jobs that use QMF.
- TCP⁄IP FTP connections.
- Each RRSAF connection that runs in batch.
- Each WebSphere application server or other application server that uses JDBC or ODBC has multiple connections to Db2. The number of connections is determined by the application server.
Batch job requests to access Db2 that exceed this limit are rejected.
REBUILD INDEX processing uses Db2 connections and might cause message DSNU397I to be issued. If you receive message DSNU397I indicating the REBUILD INDEX utility is constrained, increase the number of concurrent connections.