Two separate system library files are available during the processing of a user run; the absolute library file (SYS$*LlB$) and the relocatable library file (SYS$*RLlB$).
The absolute library file (LlB$) contains the absolute elements of each standard processor included with the operating system. LlB$ may contain any other processor and executable program added by the installation.
The relocatable library file (RUBS) contains the system-supplied relocatable elements and procedure elements which may be needed to assemble, compile, or collect the user program.
A temporary program file (TPF$) is created by the Executive for each run that is initiated. The qualifier for the filename is taken from the project-id field of the @RUN control statement. The file may be used as a scratch file for the user program's symbolic, relocatable, and absolute elements. Note, however, that since this is a temporary file it is discarded at run termination. Demand mode u:sers will find that it is safer to keep 'work in progress' in a catalogued file so that this work will not be lost in case of unplanned run termination.
The general format of the processor control statement is:
@Iabel:processor,options param-1,param-2,param-3, ... ,param-n
The label field is as described in Volume 2-3.2.1. The processor field is the name and file location (see Volume 2-3.2.2) of the absolute element desired. The following is an example of a generalized processor control statement where the processor is located in a user-specified file rather than in the system library file LlB$:
@USER*FILE.PROG/ABS,P FILE. IN, ELTOUT, FILE.OUT
All of the standard processors must be called using the above call form (rather than @XOT) since they expect to retrieve the parameters on the call line. Such parameters cannot be retrieved on an
@XOT call (see 2.3).
SPERRY UNIVAC 1100 Seriela Executive
I I
1 11V~ume3Sy~emProoouor_s~~~~~~~~~~~_U_~_A_n_~~_L~~~'_~_E_-~~~_
The rulE~s for loc,ating the element in the proces.sor field are slightly different from the standard rules for locating an EJlement specified on an @xar control statement. The processor call rules are:
1. If ia filename is specified, then that file is searched for the absolute element.
2. If
cl
filename is not specified but there is a Ileading period, then TPF$ is searched for the element;if 1there is no find, LIB $ is searched.
3. If a filename is not specified and there! is no leading period, then the system library file SYS$*LlB~1 is searched for the element if there is no find, then TPF$ is searched. The abbreviations for the standard processors (ACOB for COBOL, FTN for FORTRAN, and so forth) arE~ the names of the respective absolute elements.
In general the option field has meaning only for the particular processor, though there are some options that have the same meaning for all processors. The format of the options parameter is describled in Volume 2-3.2.2.
The param-l, param-2, ... param-n parameters contain information supplied to the processor. With the exc~~ption of the DATA processor (see Section 6), which works only with SDF files and, therefore assumes filenames, the parameter fields are assumed to be in element name form although they need not represent element names. The meaning of the parameter fields is determined by the processor.
The following rules are followed by the processors supplied by Sperry Univac:
1. If a field in'tended to contain the name of a program file is not specified, TPF$ is assumed.
2. If CI field is to contain an element name and the element name is specified but not the filename and there is. no leading period, TPF$ is assumed. If there is a leading period, then the filename is taken from previous field provided that 1the field exists and was intended to name an element or a program file.
The source lan!~uage processors (MASM, ACOB, FTN, NUALG, and so forth) have a common interpretation of several options as well as the lrirst three parameters. The typical standard language processor control statement take's the form:
@A.COB
5 I, RO, SOwhere SI, RO, and SO represent eltname-1, elitname-2, and eltname-3.
The meanings of these parameters are:
SI (Source Input) If no new ~~Iement is being introduced this paramete:' specifies the source of input for the processor.
If a new :symbolic element is being introduced from the runstream (I-option set), this parameter specifies the file into which the new element is placed and the name which it is given.
If an update is being performed (U-option set), then this parameter specifies the element and the cycle of the element being updated.
It is possible to specify a symbolic element from a tape file for this paraml~ter. The tape file must be in element file format (see 11.2.2) and the file must be positioned (@FIND) so that the element label is read in. Corrections to a symbolic element from a tape are permitted provided that the output is a symbolic element in a program file.
4144.31 UP-NUMBER
SPERRY UNIVAC 1100 S.ri . . Executive
Volume 3 System Processors UPOA T£ LEVEL
1-12 PAGE
AO (Aelocatable Output)
SO (Source Output)
This parameter specifies the name and the program file into which the element produced by the processor is placed. There is no restriction on the type of element being produced. For example, most of the processors produce relocatable binary elements: the collector produces either absolute or relocatable binary elements.
This parameter specifies the name and the file for the updated symbolic element if no U-option.
The System Aelocatable Library routine PAEPRO examines the facility description of each file specified in the 51, RO, and SO fields and assigns those files which do not meet the minimum assignment requirements.
51 - assigned
AD - exclusively assigned SO - exclusively assigned
The AD and SO fields are assigned exclusively because the language processor will modify the table of contents of the file(s) and write in the text portion of the file(s). If another run has any of the files assigned in such a way as to prevent PRE PRO from obtaining the minimum assignment the processing will be aborted if the run is in demand mode or held until the file is available if the run is in batch mode. Availability of required files may be checked by assigning the files, with the minimum assignment required, before calling the processor.
The source language processors do not interpret the 51, RO and SO fields to determine uniqueness or duplication of names. If an element name in the 51, AO or SO field matches an already existing element in name/version and type, and the field is an output field the old element will be replaced with the new element.
If no element name is specified for RO and SO or the parameter is left blank the following rules apply:
1. If there is no file information and the parameter does not have a preceding period or if the parameter is void. then the file specified in the 51 parameter is assumed.
2. The element name from the 51 parameter is assumed.
3. If there is no version specified, then the version from the 51 parameter is used.
Tables 1-3 and 1-4 describe the valid possibilities. The I and U options along with the 51 parameters determine the interpretation of the processor control statement. An error message is printed if there is any deviation from these rules. Table 1-3 is valid for the MA5M, ACOB, FTN, NUALG, MAP, and CFOA language processors (require 51, AO, and SO): Table 1-4 is valid for the PDP and EL T processors (require only 51 and SO).
41'4l4.31
UP· .... UM8EA
L
SPERRY UNIVAC 1100 Seri" ExecutiveI I
1 13_______ V_o_'_u_m_8 __
3 __
S_V_s_t_8_m __ P_r_o_c.:_8_s_s0 ___ rs ______________________ ~_u_~_A_n_UN! ___ L ____ ._PA_G_E_-_· ___lor U completely specilf ied. then
rom the 51 produced. If this parameter element. Also is not completely specified new symbolic then information from the element if 50 was