Planned shutdowns using F BPXOINIT,SHUTDOWN=...

When you are doing a planned shutdown of z/OS UNIX, follow the instructions in Steps for shutting down z/OS UNIX using F BPXOINIT,SHUTDOWN=.... As part of a planned shutdown, you need to prepare the file systems before shutting down z/OS UNIX by issuing one of these commands:

F BPXOINIT,SHUTDOWN=FILEOWNER
F BPXOINIT,SHUTDOWN=FILESYS

Issuing one of these commands synchronizes data to the file systems and possibly unmounts or moves ownership of the file systems. If you use SHUTDOWN=FILEOWNER, the system is disabled as a future file system owner via move or recovery operations until z/OS UNIX has been restarted.

Restriction: SHUTDOWN=FILEOWNER is valid only in a shared file system configuration.

If you get message BPXM048I saying that the file system shutdown was incomplete, a local mount might have been performed while the shutdown was in progress. To identify the file systems that were not moved or unmounted, issue D OMVS,F,O on the source system to see which file systems are still owned by this system. You can try to move individual file systems by issuing the following operator command for each file system in question:

 SETOMVS FILESYS,FILESYSTEM=xxxxxxxx,SYSNAME=yyyyyyyy

If a move fails, you will see message BPXO037E.

Automounted file systems are not mounted during the processing of F BPXOINIT,SHUTDOWN=FILEOWNER, or after it completes in order to provide the ability to handle unexpected mounts that occur when a file system is shut down.

In a shared file system configuration, the resulting system actions are more complex, because they might involve the movement of file system ownership between systems in the shared file system. For more information about the system actions that might occur in a shared file system, see Implications of shared file systems during system failures and recovery.

To shut down the system as part of JES maintenance without reIPLing the system, see Partial shutdowns for JES2 maintenance.