DB20001 | DB20002 | DB20003 | DB20004 | DB20005 | DB20006| DB20001 | Connected to DB2: SSID=$1 REL=$2 Default_Plan=$3 |
| Explanation: |
Com-plete has sucessfully connected to DB2 with the subsystem id $1. DB2 returned the release identifier indicated by $2. |
| DB20002 | DB2 OPEN rejected. All tasks in group $1 got DB2 sessions already. |
| Explanation: |
An application running in task group $1 has requested to open a DB2 session, however, all subtasks in this task group are having DB2 sessions already. DB2 allows only one session per subtask. |
| System action: |
The request is rejected, the application is informed by means of a return code. |
| Terminal operator info: |
Inform your system programmer. |
| System programmer info: |
Consider to increase the number of subtasks in this task group. |
| Computer operator info: |
The number of subtasks in a task group can be increased "on the fly" using the operator command TASKS. |
| DB20003 | DB2 $1 RC=$2 RSN=$3 user $4 |
| Explanation: |
An explicit or implicit DB2 call as indicated produced the return code $2 and reason code $3. The userID in effect is shown in $4. |
| System action: |
Depending on the command and the meaning of the codes (warning/error). Refer to the DB2 Messages and Codes manual for an explanation of the codes. |
| DB20004 | Waiting for $1 DB2 user sessions to close |
| Explanation: |
Before issuing a DB2 DISCONNECT, Com-plete schedules all subtasks with open DB2 sessions to close these sessions, and waits for them to report completion. |
| DB20005 | DB2 Interface Disconnected |
| Explanation: |
Self-explanatory message. |
| System programmer info: |
Com-plete has disconnected itself from DB2. |
| DB20006 | DB2 interface requires sysparm RESOURCE-MANAGER=YES |
| Explanation: |
This version of Com-plete uses RRSAF for talking to DB2, therefore it requires Com-plete to be set up as a Resource Manager. |
| System action: |
Initialization of the DB2 interface fails. |
| System programmer info: |
Add Com-plete sysparm RESOURCE-MANAGER=YES. |