The various components of SESAM/SQL carry out consistency checks within the field of their relevant activities. Any inconsistencies the components find are output to the console or the data display terminal (central error messages) and to SYSLST.
Consistency checks are output in the form module-name: nn/gg/uu. where
modulename nn ww uu | is the name of the module or component that detects the error or event is the number of the consistency check is the error weight is the subnumber |
module-name, nn and gg allow the error to be localized in subsequent diagnostics.
The error weight ww indicates what effect the error or event has on the current session and, in particular, what state the affected databases are in. It also indicates whether any actions need to be taken and, if so, what needs to be done.
Some consistency checks are output after events that are not necessarily the result of errors and do not require any action to be taken. The administration statement CREATE-DUMP, for instance, is always followed by consistency check SESADXS: XX/05/99 or SESADXS XX/40/99.
Other consistency checks are caused by inconsistencies that the DBH can correct immediately when it is running with transaction management so that no action needs to be taken.
Another group of consistency checks are caused by problems which the system administrator can eliminate with a minimum of effort. These include, for instance, consistency checks that occur following a DMS error. The system administrator must first check whether the cause of the reported DMS error can be eliminated.
Many consistency checks, however, are caused by errors and require precise diagnostics to be carried out with the relevant diagnostics documentation.
If a consistency check occurs repeatedly, the diagnostic documents are only generated the first time the check occurs. One requirement for the suppression of a second dump is that the same consistency check occurs two times in a row. See also the section “Dump repetition for consistency checks”
The importance of the error weight depends on the SESAM component which reports the consistency check. The message number indicates which component issued the consistency check:
Component | Message number |
DBH |
|
Service task |
|
DBCON |
|
SESDCN |
|
Table 37: Components and the corresponding message numbers