BMC Software, Inc., Confidential and Proprietary Information
92 Application Enhancement Solutions Messages Manual
8 The job step was restarted after a previous execution where log recovery
had been attempted. The prior recovery was not successful and will not be
retried. The logs must be recovered manually, batch backout must be
executed if necessary, and the execution control record must be deleted
before job step restart.
9 The job step was restarted after a previous execution where IMS batch
backout had been attempted. The prior backout was not successful and will
not be retried. The databases must be backed out or recovered manually, and
the execution control record must be deleted before job step restart.
10 The application program has terminated abnormally, and the IMS Batch
Backout utility was invoked for batch backout. The utility did not execute
successfully. The databases must be backed out or recovered manually, and
the execution control record must be deleted before job step restart.
11 The application program has terminated abnormally, and the IMS Log
Recovery utility was invoked to recover a log data set that was marked in
error. The utility did not execute successfully. The log must be recovered,
the database must be backed out or recovered manually, and the execution
control record must be deleted before job step restart.
12 The application program has terminated abnormally, but the execution
control record indicates that a critical REGISET error occurred. Log
recovery or batch backout may be necessary before job step restart.
13 The execution control record cannot be deleted. Before the job step can be
resubmitted, the execution control record must be deleted by using the
Display Active Job Step option of the BATCH CONTROL FACILITY
(BCF) ISPF interface.
14 The application program has terminated abnormally, and the BCF Physical
Logger was not active. BCF cannot determine whether updates were made.
The job step may require log recovery or batch backout if updates were
made.
15 The application program has terminated abnormally with an abend U8xx.
This abend may be the result of database damage. Since DBRC is not active
or at least one database is unregistered, manual intervention is required
because BCF cannot invoke the IMS Batch Backout utility. This is
necessary to provide protection from inadvertent database damage. To
obtain maximum protection against individual database damage or
corruption, the job step should use DBRC and the databases must be
registered. If the error is the result of previous database damage, the
database(s) may need to be recovered and the IMS Batch Backout utility
executed before job step restart. The job log data set might contain
additional information to assist with problem determination.
16 Reserved
17 Reserved
