ICL 1900 Series George 3 Operating System Commands

CONNECT (CN)

Function

Connects a background job to the MOP terminal from which it is issued.

Format

  1. If issued in USER context:

    CONNECT job name,action on monitoring file,RETAIN(local name)

    The first parameter gives the name of the background job to be connected. The other parameters are optional. They specify what action is to be taken on the monitoring file of the current MOP job. If RETAIN(local name) is given, the whole monitoring file will be copied to a file with the specified name, as by a COPY command. RETAIN may be abbreviated to RT.

    Monitoring Categories
    ALL Everything is to be printed
    ALLBUT (AB) The whole file is to be printed apart from the categories that follow ALLBUT
    NONE No printing is required
     
    BROADCAS (BC) Output as a result of a BROADCAST command given by the operator or internally by GEORGE. This can never be suppressed by a REPORT command and is therefore not relevant to that command, but is relevant to commands operating on the monitoring file
    COMERR (CE) Command error reporting
    COMMANDS (CM) A copy of each command
    COMMENT (CT) Command responses giving a track of the job's progress
    DISPLAY (DP) Output from the DISPLAY, QUESTION and ANSWER commands
    FILES (FL) Output converning file movements and changes in the filestore
    LISTING (LS) Output from the LISTFILE and LISTDIR commands
    LOGGING (LG) Log analysis information
    OBJECT (OJ) Output concerned with or sent by object programs
    ONLINE (OL) Output from object programs (see the ONLINE command
    POSTMORT (PM) Output from the POSTMORTEM and PRINT commands

  2. If issued in NO USER context:

    CONNECT job name,user name

Forbidden contexts

  1. If issued in USER context: NO USER, OFFLINE, CORE IMAGE, BREAK-IN

  2. If issued in NO USER context: USER, OFFLINE, CORE IMAGE, BREAK-IN

As a result of the command, the context of the connected job changes to MOP and BREAK-IN. A CONNECT command may only be issued direct from a MOP terminal.

Note: Jobs run by anticipated command issuers are classed as MOP jobs and may therefore issue CONNECT commands. An anticipated command issuer job must not, however, attempt to CONNECT to the job which is controlling the command issuer channel.

Execution

The job to be connected may be any background job belonging to the user, and whether it was initiated by JOB, RUNJOB or DISCONNECT is immaterial.

It is first checked that the parameters of the CONNECT command are valid, and that the job to be connected exists; if this is not so, the command is abandoned.

  1. If issued in USER context:

    The current on-line job's monitoring file is then terminated and processed according to the action on monitoring file parameters specified in the command. As with LOGOUT of no action on monitoring file is specified, nothing will be listed. The catergories of MOP output to the MOP terminal will be preset to ALLBUT,COMMANDS in the job connected.

  2. If issued in NO USER context:

    If the user specified is HIGH or NORMAL security, then the password will be called for and checked. Since the MOP console is at NO USER level no logging out occurs.

The connection of the background job to the user's MOP terminal is made immediately, irrespective of what is in progress in the job, and is effected by an automatic break-in.

A break-in message is sent to the user's MOP terminal and this both signals the successful connection of the job and informs the user of the stage to which it has progressed, for example

    BROKEN IN DURING ENTER IN FRED

The user may then issue any command that is permitted in BREAK-IN context. For example, to develop the above example, if CONTINUE is typed, the break-in will be terminated and the job FRED (now a MOP job) will be resumed in the object program at the point where it was suspended to effect the connection.

A background job that finishes by running out of commands will be suspended for a length of time determined by the value of the WAITTIME installation parameter. If it is connected during this period, the suspension will be terminated and the user will receive a break-in message at the MOP terminal to inform him that the job has been connected, for example

    BROKEN IN AFTER FRED

All commands in the connected job that are obeyed after the connection will be monitored on the user's MOP terminal, but any monitoring output from earlier commands will have missed being sent to the MOP terminal.

Examples

CONNECT OFFLINEJB
Reply BROKEN IN DURING ENTER

CONNECT J3,ALLBUT,COMMANDS
Reply BROKEN IN AFTER LISTFILE

Note

CONNECT and the commands RUNJOB and DISCONNECT may be used in conjunction. For example, a user may, if the state of a particular MOP job allows, hand it over as a set of predefined commands (or one time-comsuming one) to run autonomously (RUNJOB or DISCONNECT), use his MOP terminal for another problem and resume his interaction with the first (CONNECT).

Error Messages

COMMAND ALLOWED ONLY FROM CONSOLE
JOB NAME PARAMETER MISSING
z DOES NOT EXIST
z IS NOT AN OFF-LINE JOB
z IS NOT A CORRECTLY FORMED NAME (job name or local name)
z IS AN UNKNOWN MONITORING CATEGORY
USER NAME/PASSWORD INVALID
USER NAME PARAMETER MISSING