The Database Services Utility takes different actions depending on the cause of the error. The various kinds of errors are:
If the database manager (or the operating system) is terminated abnormally while the Database Services Utility is running, any database updates that occurred during the in-process Database Services Utility logical unit of work are rolled back by recovery processing when the database manager is restarted. No rollback occurs if the tables reside in nonrecoverable storage pools.
If the Database Services Utility is terminated abnormally, database manager processing restores any database updates that occurred during the in-process logical unit of work unless updates are made to tables residing in nonrecoverable storage pools.
Database Services Utility processing errors are those errors that do not cause abnormal terminations. If a processing error occurs, and SET ERRORMODE is not reset to OFF, or SET ERRORMODE CONTINUE is not in effect, the Database Services Utility performs these actions:
In DB2 Server for VSE, if the Database Services Utility encounters problems when it tries to open the report, it generates a message to the operator console and terminates processing after performing steps 5 and 6 above. If the utility encounters problems when it tries to write to the report, it generates a message and terminates processing after performing steps 2, 5, and 6 above.
If the Database Services Utility encounters problems when it tries to open the input control card file, it terminates processing after performing steps 4, 5, and 6 described above. If the utility encounters problems when it tries to read from the input control card file, it terminates processing after performing steps 2, 4, 5, and 6 as described above.
In DB2 Server for VM, if the Database Services Utility encounters problems when it tries to open the message file, it generates a WTO (write-to-operator) message and terminates processing after performing steps 5 and 6 above. If the utility encounters problems when it tries to write to the message file, it generates a WTO message and terminates processing after performing steps 2, 5, and 6 above.
If the Database Services Utility encounters problems when it tries to open the command file, it terminates processing after performing steps 4, 5, and 6 described above. If the utility encounters problems when it tries to read from the command file, it terminates processing after performing steps 2, 4, 5, and 6 as described above.
If an incorrect ddname is specified in a Database Services Utility command, or incorrect data file job control or CMS FILEDEF statements are supplied, Database Services Utility processing is terminated. Database manager processing restores any database changes when the Database Services Utility job abnormally terminates because of a data-file-open error.