The following factors may cause “abnormal” session termination:
hardware errors in peripheral devices or in the server
software errors caused by saturation or deadlock situations
conditions in which the system recognizes that continuation of processing is not possible.
In these cases the system cannot be terminated normally, i.e. all jobs active at this time usually have to be repeated after system recovery.
In most cases it is necessary to store the system status at the time of error by means of the SLED utility routine, so as to enable subsequent diagnosis.
The output files for SLED (see the “Diagnostics Handbook” [14]) may also be located outside the home pubset, but only on disks or pubsets that would be suitable as an IPL disk or home pubset - so not, for example, on SM pubsets or DRV private disks.
An error may have occurred which cannot be eliminated by immediately reloading the system, e.g. if the catalog or other important disk contents have been destroyed. In this case the disks have to be restored (from their last save status, see chapter "Data saving").
Private disk allocations cannot be returned, i.e. the system remains in the SVL of the disk and must, if necessary, be removed by means of the UNLOCK DISK command.
Similarly, it is no longer possible to cancel pubset allocations. The next time the system is initialized, message NSI424A is displayed to remind the user of this. Pubsets can be released by entering ACCEPT in response to this message.
During the BS2000 session the operator can reset any file locks still present for individual disks or entire pubsets using the UNLOCK-DISK command.