Because of the many environments in which BBI code executes, the BBI diagnostic facilities perform differently depending on the type of error and where it is encountered.
When an abend occurs in BBI or in a module of a product that uses a BBI module, recovery procedures gain control, collect the required information for problem analysis, write messages and diagnostics, and attempt recovery. Only if recovery fails or a specified recovery limit count is reached will the address space terminate and activate standard system or subsystem dumping facilities (SYSUDUMP, SYSABEND, SYSMDUMP).
The level of diagnostic information produced by default is that necessary to solve the majority of problems. Additional dump, trace, and display facilities are available if this information is not sufficient. In such a case, you might be asked by Customer Support personnel to collect more information.
Recovery procedures often limit the effect of errors occurring in BBI code. Because the temporary loss of data or function can be unnoticed or unimportant at the time, these errors are not always reported to the BBI system administrator. To prevent future errors, perhaps at a more critical point, operational procedures should be set up to check for such occurrences. Because a software log record (LOGREC) is usually produced for each BBI abend, a regularly scheduled job to print off BBI LOGRECs is the easiest method to use; see LOGREC.
This section contains the following topics:
- Overview of messages
- Summary of BBI abend diagnostics
- Troubleshooting security problems
- Troubleshooting UIM server problems