Status dump
If a dump was requested for a CALL DML or SQL status using one of the administration statements below, message SES6016 is output to inform you of the event.
SET-DIAGNOSIS-DUMP-PARAMETER
DUMP=*ON(SELECT=*CALL-DML(STATE=<alphanum-name 2..2>))
SET-DIAGNOSIS-DUMP-PARAMETER
DUMP=*ON(SELECT=*SQL(SQLSTATE=<alphanum-name 5..5>))
The same applies to a request using the equivalent administration command
OPT,DIAG,STATUS=<xx> or OPT,DIAG,SQLSTATE=<yyyy>.
The dump is written as a result.
File bottleneck
If a bottleneck occurs in one of the logging files or a DBH cursor file or a space, a filespecific message is output before a restart is initiated. The following rules apply:
File bottleneck | Message number | Inserts supplied |
CAT-REC |
| Catalog name |
DALOG/CATLOG |
| Catalog name |
TALOG1/2 |
| - |
WALOG |
| - |
Cursor file |
| - |
Space |
| - |
The DBH session is continued after a follow-up transaction restart.
Explanations of the file bottleneck handling
CAT-REC bottleneck or inconsistency
Meaning
There is either an inconsistency between the catalog space and the CAT-REC file or a bottleneck has occurred while writing the CAT-REC file. The exact cause is output first, followed by message SES6017, which announces the restart. During the restart all open transactions are rolled back, all request sessions are closed and only the ACCESS = *PARAMETERS (READ=*YES) access function is permitted for the affected database. After that the DBH continues with the session.
Response
When there is enough space again or the correct CAT-REC file is available again, write access to the database can be authorized again using the MODIFY-CATALOG-ACCESS-RIGHTS administration statement.
DA-LOG/CAT-LOG bottleneck
Meaning
A bottleneck has occurred while writing the DA-LOG file or CAT-LOG file. An internal restart is announced with message SES6018. During the restart all open transactions are rolled back, all job sessions are closed and only the ACCESS = *PARAMETERS (READ=*YES) access function is permitted for the affected database. After that the DBH continues with the session.
Response
When there is enough space again, write access to the database can be authorized again using the MODIFY-CATALOG-ACCESS-RIGHTS administration statement.
TA-LOG bottleneck
Meaning
A bottleneck has occurred while writing to one of the TA-LOG files. An internal restart is announced with message SES6019. During the restart all open transactions are rolled back, all job sessions are closed. This lowers the utilization of the TA-LOG files and the DBH continues with the session.
Response
None
WA-LOG bottleneck
Meaning
A bottleneck has occurred while writing to the WA-LOG file. An internal restart is announced with message SES6020. During the restart all open transactions are rolled back, all job sessions are closed. This lowers the utilization of the WA-LOG file and the DBH continues with the session.
Response
None
Cursor file bottleneck
Meaning
A bottleneck has occurred while writing to a CURSOR file. An internal restart is announced with message SES6021. During the restart all open transactions are rolled back, all job sessions are closed. This lowers the utilization of the cursor files and the DBH continues with the session.
Response
None
Space file bottleneck
Meaning
The maximum space size has been reached. The internal restart is announced with the message SES6026. During the restart all open transactions are rolled back, all job sessions are closed.
The space is placed in the “reorg pending” state. In the “reorg pending” state only read accesses, deletion of records with DELETE, deletion of tables with DROP TABLE ... DEFERRED, deletion of indexes with DROP INDEX ... DEFERRED and reorganization with REORG SPACE are permitted.
Response
The space’s “reorg pending” state can be reset again using the utility statement REORG SPACE.