ICL 1900 Series George 3 Operating System Commands

DISCONNECT (DC)

Function

Causes the curent MOP job to be disconnected from the MOP terminal and to continue as a background job.

Format

DISCONNECT job name

The parameter is optional. If it is given it must not coincide with the name of any of the user's files.
If the parameter is present, and does not coincide with the name of any other job which the user currently has in the system, the user remains logged in with the new job name specified.
If the parameter is present, and does coincide with the name of a background job which the user currently has in the system, then, after DISCONNECTing the current job, the job named is CONNECTed to the MOP terminal.
If the parameter is not present the MOP terminal returns to NO USER context.

Forbidden contexts

NO USER, OFF-LINE, NOT BREAK-IN

As a result of the command, the context of the disconnected job becomes USER and OFFLINE. If the job name parameter is not given, the MOP terminal returns to NO USER and NOT BREAK-IN context; if the parameter is given, and is a new name, the context of the new MOP job is USER, MOP and NOT BREAK-IN. If the parameter is given and is the name of a current background job then the context of this job changes to USER, MOP and BREAK-IN.

Execution

If a job name is present, its validity is checked. If it coincides with the name of a file belonging to the user, the command is abandoned. If the job name is new, a monitoring file is opened with this name and the MOP user remains logged in, but not in the same context (see above).

If the job name coincides with a background job belonging to the user, the MOP terminal is CONNECTed to this background job.

If the job name is not present, the user will effectively be logged out and the categories of MOP output to the MOP terminal will be reset to ALLBUT, COMMANDS.

The current broken-in MOP job is removed from the control of the MOP terminal. It is restarted automatically at the point where the break-in occurred (a CONTINUE command is issued internally by DISCONNECT to terminate the break-in).

If the disconnected job runs out of commands, it is suspended for a period of time determined by the value of the installation parameter WAITTIME and then terminated. At any time before termination it may be reconnected to the MOP terminal by a CONNECT command, or another DISCONNECT command.

Examples

DISCONNECT MOPJOB2
DISCONNECT

Error Messages

JOB NAME z NOT UNIQUE
z IS OVERDRAWN ON HIS MONEY BUDGET
z IS NOT A CORRECTLY FORMED NAME (job name)
THE LIMIT ON THE NUMBER OF JOBS HAS BEEN REACHED
USER OWNS/OWNED FILE WITH THE SAME LOCAL NAME AS JOBNAME SPECIFIED z IS NOT AN OFFLINE JOB