ICL 1900 Series George 3 Operating System Commands

ABANDON (AB)

Function

Allows the operator to abandon the execution of a job, or a user to abandon his own jobs.

Format

  1. ABANDON job name,user name,TEMP,MESSAGE(text)
  2. ABANDON job name,MESSAGE(text)

Format 1 is for use by the operator
Format 2 is for a MOP user, who may ABANDON jobs that he has issued.

(TEMP may be abbreviated to TE and MESSAGE to ME)

Forbidden contexts

  1. NOT OPERATOR
  2. NOT USER

Execution

The command causes the specified job, whether it is in the well or not, to be abandoned. If the job has started, it's files are closed, and any core image that may exist is deleted, and any peripherals being used by the job are released. In format 2, the specified job is taken to be that with the specified jobname and the same username as the proper user. If the TEMP parameter is specified, the job's well entry is retained, but marked so thatt he job is not a candidate for selection for running. The job may be made a candidate for selection again be means of the REGENERATE command, or alternatively may be abandoned permanently by an ABANDON command without a TEMP parameter. The TEMP parameter is only allowed in central operator context ABANDONs for background jobs. A command error is given in all user or remote context ABANDONs and in operator ABANDONs for MOP jobs.

If a background job in the well is abandoned permanently, the entry is removed and the following message output:-

    job name, user name HAS BEEN WITHDRAWN FROM THE WELL

If a background job in the well is abandoned temporarily, the entry is marked to make it a non-candidate for sekection and the following message output:-

    job name, user name HAS BEEN TEMPORARILY WITHDRAWN FROM THE WELL

When a MOP job in the well is abandoned, the entry is removed and the message:-

    job name, user name IS BEING ABANDONED

output on the operator's console. The message:-

    ABANDONED BY OPERATOR INTERVENTION:

is sent to the MOP console. If a MESSAGE parameter is present, which for a well job is only used if it is MOP, then it is appended to the above message.

When abandoning a job which is already running, it is possible that the job cannot be abandoned immediately, in which case the message below is output:-

    job name, user name WILL BE ABANDONED AS SOON AS POSSIBLE

This may happen if the job is in the middle of a command that cannot be interrupted such as LOGOUT or ENDJOB, or if the job is being broken in on. If the job is logging out, the error message:-

    z DOES NOT EXIST

may be output afterwards.

    job name, user name IS BEING ABANDONED

is output when the job is found to be in an abandonable state. One of the following messages as appropriate is sent to the job's monitoring file:-

    ABANDONED BY OPERATOR INTERVENTION
    ABANDONED BY USER INTERVENTION

TEMPORARILY is prefixed to the message if the TEMP parameter was given and the text of any MESSAGE parameter appended to it. The message:-

    END OF MACRO

is sent to the job's monitoring file as each of the job's files, for example the job description file, is closed down. To implement the commang, GEORGE simulates a LOGOUT (for a MOP job) or an ENDJOB (for a background job). The monitoring file will always be listed in full, but not RETAINed. In order that the charge for running an abandoned job may be modifiable, the ABANDONED message is stored in the logging category. A system issued job is not abandonable. If an attempt is made to abandon a job that does not exist the operator will be informed. Remote operators are only allowed to abandon jobs originating from their own cluster.

Examples

ABANDON JOBNO135,:FRED
ABANDON TESTJOB,:BERT,TEMP,MESSAGE(SORRY)
ABANDON MYJOB

Notes

  1. This command must be used with great care, particularly if the job concerned has been started sincethe work done by the job is likely to be wasted.
  2. If the ABANDON command is issued in USER context either directly or using the OPERATOR command, and the job specified cannot be abandoned immediately, the action of ABANDONing it will proceed autonomously with the issuing job.
  3. A command error will be generated if an attempt is made to ABANDON a job which is already being abandoned. (Note that this previous abandon action may not necessarily be being taken for an ABANDON command, but could be the result of, for example, MOP OFF.)

Error Messages

JOB NAME PARAMETER MISSING
JOB z NOT ABANDONABLE: SYSTEM ISSUED
USER NAME PARAMETER MISSING
z DOES NOT EXIST
z IS NOT A CORRECTLY FORMED NAME
JOB IS NOT ABANDONABLE: IT IS NOT IN YOUR CLUSTER
USERNAMES NOT ALLOWED IN USER CONTEXT
YOU CANNOT ABANDON YOURSELF
JOB ALREADY TEMPORARILY ABANDONED
YOU ARE NOT PERMITTED TO TEMPORARILY ABANDON JOBS
JOB z IS ALREADY BEING ABANDONED