ABORTJOB



ABORTJOB/=ABORTJOB

     Aborts a job or session (CM).

SYNTAX

              {#Jnnn              }
     ABORTJOB {#Snnn              }
              {[jobname,]user.acct}

               {#Jnnn              }
     =ABORTJOB {#Snnn              }
               {[jobname,]user.acct}


PARAMETERS

#Jnnn               A job number.

#Snnn               A session number.

jobname             The name of the job, as identified by the SHOWJOB
                    command.

user                A user name.

acct                An account name.


OPERATION

     This command terminates the designated job or session, and
     displays the following message on the job/session list
     device:

     SESSION ABORTED BY SYSTEM MANAGEMENT

     If you use the [jobname,]user.acct form of the command when
     there is more than one job or session executing under that
     name, MPE/iX will randomly select which job/session to abort.
     Therefore, to exercise the more precise control when aborting
     jobs or sessions, use the #Jnnn or #Snnn form of the ABORTJOB
     command. Although the job/session is abnormally terminated, log
     records are issued, and CPU and connect times are updated.  Any
     I/O activity (that is printing, STORE, etc.) will also be
     terminated.

     The ABORTJOB command can be applied to waiting and scheduled
     jobs, as well as to executing jobs.  If the spooler input file
     ($STDIN) for a batch job has been created and not yet opened (in
     other words, the job is in the WAIT state), the entire file will
     be deleted.  If the ABORTJOB command is issued before the output
     spoolfile is complete, only that portion of the file already
     spooled will be printed, along with an error message indicating
     that the job was aborted. If a request is pending at the system
     console, it will be terminated automatically and the following
     message will appear on the system console:

      time/#Snnn/pin/REQUEST REQUIRING OPERATOR REPLY FOR
      PIN #nn HAS BEEN ABORTED

     When the ABORTJOB command is successful, a logoff message is
     displayed on the console, indicating that the job being executed
     has been aborted, as shown in the example below:

     ABORTJOB #S9
     1120/#S9/34/LOGOFF ON LDEV #77

     Two messages will also be displayed on the user's terminal
     the standard error message that appears when a request is
     manually terminated by entering 0 or N in response to =REPLY
     (or REPLY):

     SESSION ABORTED BY SYSTEM MANAGEMENT

     If the :ABORTJOB command is ineffective, you must issue the
=ABORTJOB command from the physical console.

This command may be issued from a session, job, program or in
BREAK. Pressing [Break] has no effect on this command.

The :ABORTJOB command is executable only from the console unless
it has been distributed to users with the ALLOW command, or if
JOBSECURITY is LOW. Users with account manager (AM) or system
manager (SM) capability can execute this command. The =ABORTJOB
command may be issued only from the physical console.

EXAMPLE(S)

     To terminate session number 139, enter:

     ABORTJOB #S139
     1710/#S139/34/LOGOFF ON LDEV #62

     To terminate job number 9, enter:

     ABORTJOB #J9
     2018/#J9/26/LOGOFF ON LDEV #10

     Note that in both cases the execution was successful, and a
     logoff message was printed.

     To terminate session 6, which has a pending device allocation
     message, enter:

     ?1700/#S6/23/LDEV# FOR "SCRTAPE" ON TAPE (NUM)?
     ABORTJOB #S6
     1710/#S6/120/REQUEST REQUIRING OPERATOR REPLY FOR PIN 23
     HAS BEEN ABORTED
     1710/#S6/120/LOGOFF ON LDEV #58

ADDITIONAL INFORMATION

Commands:   ALTJOB, BREAKJOB, JOBFENCE, JOBSECURITY, RESUMEJOB,
SHOWJOB, STREAM