UNIVERSITY MATHEMATICAL LABORATORY, CAMBRIDGE

CAMBRIDGE SUPERVISOR : PLANNING DOCUMENT No. 26
User Identifications and Project Numbers

The following scheme is suggested since it satisfies all requirements, and would cause the least upheaval to existing users.

1. USER IDENTIFIER

Each individual (including certain pseudo individuals such as libraries and administration features) is associated with a unique USER IDENTIFIER, which consists of a sequence of up to 4 letters (commonly initials ) followed by up to 4 digits (the user number, if we like).

2. PROJECT NUMBERS

All jobs are run under a project number, whose main purpose is to form the basis of the log analysis system. A project number is an integer of up to 4 digits.

3. JOB TITLES

With every job running in the machine, the supervisor maintains a job title; if the job is off-line, then this is the job title from the job description; if on-line, it is supplied by CONTROL. The User Identifier and the Project Number will be found in the job title according to the following rules:

  1. the 1st integer before the / is the project number;
  2. ignoring any initial digits, the user identifier is up to 4 letters followed by up to 4 digits, before the /.

Examples

job titleproject numberuser identifier
DFH200/...200DFH200
1023DFH200/...1023DFH200

4. FILE TITLES

The first component of a file title is a user identifier; if the first component is not quoted, then the user identifier is taken from the job title (see 3 above).

5. JOB DESCRIPTIONS

The project number is only quoted at the start of the job title; if it is not quoted explicitly then the integer in the user identifier is taken (see 3 above). If any other (document) title is quoted in a job description, and the first component is missing, then only the user identifier is substituted automatically.

Example

IIT  (1033 DFH200/SAMPLE JOB)

INPUT P0 FROM FILE  (/TEST/1)

      D1 (/DATA)

The 2 input documents are respectively (DFH200/TEST/1) which is a file, and (DFH200/DATA) which is an input document.

6. CONTROL

Either(a)the project number and user identifier can be quoted after USER as for job description;
or(b)some more convenient notation can be used.

7. COMPATIBILITY

The only immediate changes for users would be those cases where a file owner does not have the required format; viz:
1001CWS(Whitby-Strevens)
291SYS   )   
   )
292SYS   )pseudo users
   )
etc.   )

It is suggested that all users are, as soon as convenient, given definitive user numbers, and urged to adopt the new formats; although this does not have to occur "overnight".

I would further propose:

  1. All output tank slots are also labelled with the user identifier.
  2. We work towards the situation where a pseudo-user identifier is used in the job title only when absolutely necessary; e.g. for setting partners. Administrators and supervisor maintainers should use their personal identifications normally. This cannot be fully achieved until we have better CONTROL facilities.

D.F. Hartley
B. Landy
26.5.67


Copyright © 1967 University of Cambridge Computer Laboratory. Distributed by permission. Thanks to Barry Landy, Roger Needham and David Hartley for giving permission to distribute these documents. Thanks to Barry Landy for lending me the paper document from which this was scanned. Any typographical errors probably arose in the course of OCR.


Previous Planning Document: 25. User Groups, A.G. Fraser and lmw, 8.5.67
Return to Cambridge Supervisor Planning Documents
Return to CUCPS TITAN page
Return to CUCPS home page
Return to University of Cambridge home page


Contact: CUCPS Committee (soc-cucps-committee@lists.cam.ac.uk)
This HTML version last updated: $Date: 1999/06/20 19:05:56 $