After a failure of a file system type, the system issues message BPXF032D. In response, the operator or automation corrects the problem as indicated by previous messages and then enters R in reply to message BPXF032D.

If a file system type fails to initialize, the system normally issues message BPXF006I. If the failing file system type was specified with the option to prompt for restart (the default), the error that caused the problem can be corrected, and then the prompt responded to. If it was specified with the option to not prompt for restart, the system continues to run without that file system type, but requests to use the files in any file systems of that file system type will fail.

In rare cases, the initialization of a file system type might fail due to a programming or environmental error, such as a severe storage shortage in the kernel address space. The failure can occur before the file system type is initialized, and, on rare occasions, the BPXF006I message is not issued. In these cases, the severe programming or environmental error should be addressed first. After the severe condition that prevented the initialization of the file system type is resolved, the operator can manually initialize the file system type with the SETOMVS RESET=xx operator command.