Shutting down ADCD z/OS

If possible, always shut down z/OS® cleanly. Typically, shutting down cleanly begins by logging off all TSO users, and starting a procedure that shuts down all active subsystems.

This z/OS 2.3 ADCD contains shutdown scripts for most systems available and active in the distribution. They are named SHUTxx, where xx corresponds to the VTAM®xx parmlib member that was used to start the subsystems for a particular IPL.

Note: Use SHUT00 when the z/OS 2.3 ADCD was started with loadparm CS or WS, and SHUTALL when the z/OS 2.3 ADCD was started with loadparm AL.

When an S SHUTxx command is issued from the MVS™ master console, these scripts shut down all systems that were automatically started by the corresponding VTAMxx parmlib member. These shutdown scripts are contained in ADCD.*.PROCLIB, where * varies according to the release started.

While the shutdown scripts attempt to stop all active subsystems started by that loadparm, some subsystems might require further input to be stopped. You might have to respond to z/OS console messages, such as when IMS™, TSO, or z/OS UNIX are stopped. You can see what programs are still running by entering the D J,L console command. Ensure VTAM and all subsystems are stopped.

After you run the appropriate SHUTxx script and all systems are stopped, stop your JES system. The loadparms in your z/OS 2.3 ADCD distribution always start JES2. A $pjes2 command that is entered from the MVS console stops JES2.

After JES ends, Z operation can be stopped by entering the QUIESCE command. After this command completes, stop the zPDT® system by entering this command in the Linux window:

$ awsstop

This command produces several messages. It might be necessary to press Enter to obtain the Linux prompt. Any 3270 windows can be closed.