 |
» |
|
|
|
The ABORTJOB/CtrlA ABORTJOB command terminates either a designated job or session. Typically, you use this command to cancel a job that you decided not to run but had already streamed. You can also use this command to terminate one or more sessions, if necessary, for system emergencies or scheduled shutdowns. Syntax | |
From a terminal:
ABORTJOB {#Jnnn
#Snnn
[jobname,]user.acct}
|
From the console:
CtrlA ABORTJOB {#Jnnn
#Snnn
[jobname,]user.acct}
|
Parameters | |
- #Jnnn
Specifies a job number. - #Snnn
Specifies a session number. - jobname
Specifies the name of the job, as identified by the SHOWJOB command. - user
Specifies a user name. - acct
Specifies an account name.
Operation Notes | |
| | | |  | NOTE: You need to use the SHOWJOB command to determine the job or session number of the operation you want to cancel. If you need more information on SHOWJOB, refer to the section on that command later in this chapter. | | | | |
Usage You can enter this command from a session, a job, a program, or in break mode. Pressing Break does not affect this command. You must enter the CtrlA ABORTJOB command from the console. You can enter the ABORTJOB command from a terminal other than the console if the JOBSECURITY command is set to LOW, or if your system administrator has used the ALLOW command, which permits you to enter this command. Differences between ABORTJOB and CtrlA ABORTJOB Both of these commands function identically except that you can enter CtrlA ABORTJOB only from the console. The = sign appears when you press CtrlA. Pressing these keys enables you to enter certain commands on a console from which another process (such as STORE) is currently running. Recommended usage If you use the [jobname,]user.acct form of the command when more than one job or session is executing with the same name, the system selects the job or session that it aborts. Consequently, you should use the #Jnnn or #Snnn form of the command for more precise control of jobs or sessions to be terminated. Although the job or session abnormally terminates, log records are issued, and CPU times and connect times are updated. All I/O activity terminates, such as printing, and reading or writing files. Waiting and scheduled jobs You can also use the ABORTJOB command for waiting and scheduled jobs, as well as for executing jobs. If a request is pending at the console, the command automatically terminates the request, and the following message appears on the console:
time/#Snnn/pin/REQUEST REQUIRING OPERATOR REPLY FOR
PIN #nn HAS BEEN ABORTED
|
Refer to the Glossary for a definition of the process identification number (PIN).
Examples | |
To terminate session number 139, enter: The system responds by displaying the following logoff message on the console if the session ends successfully:
17:10/#S139/34/LOGOFF ON LDEV #12
|
To terminate job number 9, enter: The system responds by displaying the following logoff message if the executing job successfully terminates:
20:18/#J9/26/LOGOFF ON LDEV #10
|
This message does not appear when you terminate waiting or scheduled jobs. To terminate session 6, which has the following pending device allocation message, enter:
?17:00/#S6/23/LDEV# FOR "SCRTAPE" ON TAPE (NUM)?
:ABORTJOB #S6
|
The system responds by displaying the following message:
17:10/#S6/120/REQUEST REQUIRING OPERATOR REPLY FOR
PIN 23 HAS BEEN ABORTED
17:10/#S6/120/LOGOFF ON LDEV #58
|
Related Commands | |
ALLOW
BREAKJOB
CONSOLE
JOBSECURITY
SHOWJOB
STREAM
|
|
