Before you begin: You need to notify users that the system
is being shut down and ask them to log off. If you do not shut down
and quiesce the UNIX workload,
these critical system functions might be ended abnormally during the
shutdown, which might cause several failures on the system. As a result,
the system might not be shut down successfully.
- Use the operator SEND command to send a note to all TSO/E users
telling them that the system will be shut down. For example:
send 'The system is being shut down in five minutes. Please log off.',NOW
- Use the wall command to send a similar note
to all logged-on shell users. For example:
wall The system is being shut down in five minutes. Please log off.
Perform the following steps to shut down z/OS UNIX using F
OMVS,SHUTDOWN.
- Prevent new TSO/E logons.
_______________________________________________________________
- Quiesce your batch and TSO workloads. Having batch jobs and TSO
users running during the shutdown might cause these jobs to experience
unexpected signals or abends. Additionally, these jobs and users might
end up being hung, waiting for z/OS UNIX services
to be restarted, if they first access z/OS UNIX services
during a shutdown.
Quiesce those application and subsystem workloads
using z/OS UNIX services
in the manner that each application or subsystem recommends. Doing
so will allow subsystems such as DB2®, CICS® and IMS™, and applications like SAP, Lotus® Domino®, Tivoli® NetView® for z/OS®,
and WebSphere® to be quiesced
in a more controlled manner than this facility will provide.
Tip: You
can use the D OMVS,A=ALL operator command to determine
which applications, if any, require quiescing.
_______________________________________________________________
- Move or unmount all of the NFS file systems by issuing: F OMVS,STOPPFS=NFS.
Doing so prevents the NFS file system from losing data.
_______________________________________________________________
- Terminate all file system address spaces such as TCP/IP and DFSS,
using their recommended shutdown methods. If you do not shut them
down before issuing F OMVS,SHUTDOWN, these system functions might
terminate abnormally when the shutdown takes place. Do not shut down
existing PFS colony address spaces such as zFS because they are shut
down as part of F OMVS,SHUTDOWN.
_______________________________________________________________
Result: Now you can issue F OMVS,SHUTDOWN.
Note: - After an F OMVS,SHUTDOWN request is accepted, jobs that attempt
to use z/OS UNIX services
for the first time will be delayed until the system is restarted.
Terminating signals are sent to jobs that are already connected; these
jobs will be ended abruptly.
- After F OMVS,SHUTDOWN has completed, you can shut down the system
completely via an IPL or by powering off.
Tip: You can completely
restart and reinitialize the z/OS UNIX environment
by issuing F OMVS,RESTART. You can also use it to change the configuration
of z/OS UNIX services
by specifying a different set of BPXPRMxx members when z/OS UNIX is started.
For more information about F OMVS,RESTART, see z/OS MVS System Commands
- Using F OMVS,SHUTDOWN, the steps for shutting down z/OS UNIX are the
same whether or not the system is participating in a shared file system.
However, in a shared file system, 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 system actions that might occur in a shared file system, see Implications of shared file systems during system failures and recovery.