Summary of Methods of Stopping APPC/MVS Work

Table 1. Stopping APPC/MVS Work
When you want to: Use one of the following: Which affects: By:
Prevent a transaction program (TP) from running APPC/MVS utility or dialog to deactivate a TP through its profile All new conversations for one specific TP Rejecting inbound Allocate requests for the TP
Stop a currently running TP CANCEL command The currently running instance of a TP, and its partner TPs Abnormally ending the TP
STOP command Same as for CANCEL Abnormally ending the initiator address space in which the TP is running
Stop a class of TPs SET ASCH command, with ASCHPMxx that contains CLASSDEL with WORKQ=DRAIN All TPs defined to a specific class Quiescing running or queued TPs, and deleting the class after the running and queued TPs have ended
SET ASCH command, with ASCHPMxx that contains CLASSDEL with WORKQ=PURGE Same as for CLASSDEL with WORKQ=DRAIN Rejecting all queued TPs, allowing only the currently running TP to finish its processing, and deleting the class after the one TP has ended
Stop a logical unit (LU) SET APPC command, with APPCPMxx that contains LUDEL All inbound or outbound conversations for the LU Rejecting new conversations, but allowing active or queued (that is, existing) conversations to continue processing without interruption
VARY TERM command, followed by VARY INACT command All inbound or outbound conversations for the LU Rejecting new conversations and interrupting all TPs involved in existing conversations that are processed through VTAM®
VARY INACT command, with the TYPE operand Same as for VARY TERM with VARY INACT Rejecting new conversations, and failing existing conversations on the next APPC/MVS or CPI-C service that requires APPC/MVS and VTAM interaction. Not recommended, because TPs waiting for an outstanding call to complete might hang indefinitely. IBM® recommends that you issue the VARY TERM command before issuing VARY INACT to avoid hanging TPs.
Stop the ASCH address space CANCEL ASCH command All conversations for TPs scheduled through the APPC/MVS scheduler Immediately ending all running or queued TPs scheduled through the APPC/MVS transaction scheduler. Outbound Allocate requests from address spaces not associated with ASCH can be processed only if a NOSCHED system base LU exists.
Stop the APPC address space CANCEL APPC command All APPC/MVS work on this MVS system Immediately ending all APPC/MVS TPs, schedulers, servers, and LUs
Stop VTAM HALT command All TPs, regardless of the operating system on which they reside, that require VTAM services to communicate Rejecting new conversations and interrupting all TPs involved in existing conversations that are processed through VTAM
HALT QUICK command Same as for HALT Rejecting new conversations and failing existing conversations that are processed through VTAM on the next APPC/MVS or CPI-C service that requires APPC/MVS and VTAM interaction. If any TPs are waiting for an outstanding APPC/MVS or CPI-C call, they might hang.
HALT CANCEL command Same as for HALT Same as for HALT QUICK, except that TPs waiting for outstanding calls do not receive control again.