ABORTJOB/ =ABORTJOB

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

The standard error message that appears when a request is manually terminated by entering Y in response to =REPLY (or REPLY) is displayed on the user's terminal:

  SESSION ABORTED BY SYSTEM MANAGEMENT

The =ABORTJOB command may be used at the physical console if ABORTJOB is ineffective. Refer to the "Use" section of this command.

Use

You may issue this command from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It is executable only from the console unless it is distributed to users with the ALLOW command, or the JOBSECURITY command is set to LOW with AM or SM capability.

=ABORTJOB may be issued only from the console.

	NOTE: Users with AM capability may only abort jobs and sessions within their own account. Users with SM capability may abort jobs and sessions across accounts.

Examples

To terminate session number 139, enter:

  ABORTJOB #S139
  17:10/#S139/34/LOGOFF ON LDEV #62

To terminate job number 9, enter:

  ABORTJOB #J9
  20:18/#J9/26/LOGOFF ON LDEV #10

In both of the preceding examples, the LOGOFF ON LDEV # messages indicates that ABORTJOB command was successfully executed.

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

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