Chapter 2 41
Command Definitions A-B
ABORTJOB/ =ABORTJOB
ABORTJOB/ =ABORTJOB
Aborts a job or session.
Syntax
ABORTJOB{#Jnnn #Snnn [ jobname,] user.acct }
=ABORTJOB{#Jnnn #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 Notes
The ABORTJOB 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 selects which job/session to abort.
Therefore, to exercise 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-times and connect-times are updated. Any I/O
activity, such as printing or file storage, is 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 is deleted. If the
ABORTJOB command is issued before the output spoolfile is complete, only that portion of
the file already spooled is printed, along with an error message indicating that the job was
aborted. If a request is pending at the system console, it is automatically terminated by the
ABORTJOB/=ABORTJOB command and the following message appears 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 has been aborted, as shown in the example below:
ABORTJOB #S9
11:20/#S9/34/LOGOFF ON LDEV #77
