FORCE COMMANDS


|********************************* TOP OF DATA ********************************|
|   *** Forcing Jobs, Users, Tasks, MOUNTs, XWTRs and Output Processing ***    |
|                                                                              |
|    Command: FORCE                       Supported MVS Levels: SP1|XA|ESA     |
|                                                                              |
|   Overview  Issue the FORCE command to cause the immediate termination       |
|             of either a time sharing (TSO) user, a job in execution,         |
|             a cataloged procedure started with a START command, an           |
|             external writer (XWTR) allocation or the output processing       |
|             for a job.  The FORCE command is used only as a last             |
|             resort.  If you have issued the CANCEL command several           |
|             times, and it does not perform the function you desire,          |
|             then you may wish to FORCE the task out of the system.           |
|             FORCE should never be used as a substitute for CANCEL,           |
|             always attempt to CANCEL first, several times.  If you           |
|             need to use FORCE use it with the ARM operand first, only        |
|             if that fails should you issue the FORCE without the ARM         |
|             operand.                                                         |
|                                                                              |
|             PLEASE NOTE:  After using the FORCE command you may have         |
|             to IPL.  When FORCE is used on a job or TSO user, that           |
|             address space is deleted from the system and recovery is         |
|             severely limited.  If a DUMP is required, you must issue         |
|             the DUMP command before issuing the FORCE command.  FORCE        |
|             processing may not complete immediately if your system was       |
|             part of a GRS ring and had been quiesced.  If a job is in        |
|             a loop, do not FORCE it, use the RESTART function instead.       |
|             The FORCE command is only valid from a MASTER console.           |
|                                                                              |
|     Syntax:                                                                  |
|             FORCE| jobname             |,ARM|,A=asid|                        |
|                  | STARTING            |    |       |                        |
|                  | U=userid            |    |       |                        |
|                  | U=*LOGON*           |    |       |                        |
|                  | devnum              |    |       |                        |
|                  | devicetype          |    |       |                        |
|                  | identifier          |    |       |                        |
|                  | {jobname.}identifier|    |       |                        |
|                  | unitaddr            |    |       |                        |
|                  | ARMRESTART                                                |
|                                                                              |
|******************************* BOTTOM OF DATA *******************************|

Examples :

     FORCE
     -----

     FORCE JOBNAME
     FORCE JOBNAME,ARM
     FORCE STARTING
     FORCE SERVICE,ARM,A=XXX
     F 5ØE

     TO FORCE A USERID OFF AN MVS SYSTEM:
     ------------------------------------
     D J,USRID CHECK "SMC=ØØØ" DO NOT FORCE IF THERE IS NOT THREE Ø'S
     FORCE U=XXXXXX,ARM  THEN ISSUE NEXT COMMAND IF NECESSARY
     FORCE U=XXXXXX  (XXXXX=USERID)

     * REF CANCEL COMMANDS