DATA PREPARATION CONTROL STATEMENTS

3.8.1. Direct Creation of Card Image Files (@FILE) Purpose:

The @FILE control statement creates SDF mass storage or magnetic tape files while the input symbiont is reading the runstream. Creating a file in this manner, rather than by means of the EL T or DATA processors, reduces overhead since it is accomplished at input time rather than at execution time. ThH data is handled only once in creating the file, rather than being read again from auxiliary storage with the runstream and then transferred to the file by the DATA or ELT processors at execution time. The file into which the images are placed may be either a sector-formatted or magnetic tape file. Sector-formatted files may not be temporary files except for removable disks. The @FILE statement is valid only within an @RUN, and cannot have been initiated via @START.

Format:

For each storage device, the format of the @FILE control statement is identical to the @ASG control statement for that device (except that the label field is not used).

If the device type specifies sector-formatted mass storage, the format is:

@FILE,options filename,type/reserve/granule/maximum,pack-id-1 I pack-id-2/ ... pack-id-n NOTE:

The pack-ids are only used if the type field specifies removable disk.

If the device type is magnetic tape, the format is:

@ FtLE,options

Parametl3rs:

options

Description:

fi len a me, typ e/u n its/l 0 gin 0 i se/p ro cesso rita pel format/dc,reel-1/reel-2/ .. ./reel-n, expiration-period

The options are interpreted exactly as they would be for the @ASG statement of the appropriate device type.

For a m()re complete explanation of these options and the remainder of the control statement, see the @ASG statement for sector-formatted mass storage or magnetic tape (see 3.7.1.1 and 3.7.1.2).

4144.23

UP-NUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC

I

U""ATE LEVEL

I

_PAGE ^3-64

The qualifier must either be explicitly given cr the qualifier 0$0$0$ is assumed. For private files, the project-id is picked up from the @RUN control statement.

@FILE control statement processing is terminated upon encountering an @ENDF control statement, an @FIN control statement, or another @FILE control statement. Data images and all control statements except @COL and its accompanying end sentinel are placed into the created file (the

@COL control statement and sentinel are processed immediately, and the file is marked when the mode switch is made).

@FILE control statements cannot be nested unless they use the same filename and are a tape file.

Nested mass storage files will cause @FILE mode to terminate with an error message. Nested tape files with the same name will cause an EOF to be written on the tape and a new file to follow the EOF.

No run is opened until an @FIN control statement is encountered. Thus, all @FILE files will have been created.

The @FILE statement is not available from demand runs.

The C or U option causes cataloging to occur upon successful completion of the @FILE (@ENDF or

@FIN encountered), rather than upon successful run termination.

3.8.2. Terminating the File Mode (@ENDF) Purpose:

Marks the end of the images for a file created by the @FILE control statement.

Format:

@ENDF Description:

@ENDF control statements cannot have labels and cannot be continued.

3.8.3. Direct Creation of Data Files from NTR Sites Purpose:

An SDF-formatted mass storage file can be created directly by initiating a data-transfer device or initiating a non-data-transfer device in alternate mode.

Description:

This data-transfer file consists of images which are not sensitive to content of images (e.g.,

@RUN,@COL), to control images (e.g., control directions for printers, punches), to type of symbiont device (e.g., card reader, printer, punch, paper tape, disk, magnetic tape), or to image length (up to 510 words). Upon initiation of the input data-transfer device, th,e Executive generates an @RUN and an @FILE control statement. The public, read-only mass storage file is named Q$Q$Q$*symbiont name. The 1100 user program may use the standard system library routines of SDFI/SDFO to access the mass storage file. After an output data-transfer file is created, the user does an @SYM,C of the filename to the desired output data-transfer device or device group. If another input data-transfer file is sent, the F-cycle number is updated for the O$O$Q$*symbiont name associated with the device.

~M~~ ________ V_o_l_u_m_e __ 2_E_X __ E_C ____________________________________ ~U_P-D_AT_E_LE_V_EL ____ ~._PA_G_E ____ __

3 .. 9. PROCESSOR CONTROL STATEMENTS

Two separate 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 (L1B$) contains the absolute elements of each standard processor included in the operating system. L1B$ may contain any other processor and executable program added by the installation. "

The relocatable library file (RLlB$) 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.

Processors form a special class of absolute elements which provide standard services for the user.

The principal distinction is in regard to the manner in which the absolute element is invoked and the means by which information is made available to the processor.

The general format of the processor control statement is:

@Iabel:processor,options param-1,param-2,param-3, ... ,param-n

The labEd field is as described in 3.2.1. The' processor field is the name and file location (see 3.2.2) of the absolute E~lement 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$:

1. @USER*FILE.PROG/ABS,P FILE IN,ELTOUT,FILE OUT

The rules for locating the element in the processor field are slightly different from the standard rules for loca1ting an element specified on an @XOT control statement (see 3.4.4):

1. If 01 filename is specified, then that file is searched for the absolute element.

2. If a filename is not specified but there is a leading period, then TPF$ is searched for the element.

3. If a filename is not specified and there is no leading period, then the system library file SYS$*LlB$ is searched for the element; if there is no find, then TPF$ is searched. The abbreviations for the standard processors (COB for COBOL, FOR for FORTRAN, etc.) 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 described in 3.2.2.

4144.23

UP-NUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC

I

UPD. TE LEVEl

I

_PAGE ^3-66

The param-1, param-2, ... param-n parameters contain information supplied to the processor. With the exception of the DATA processor (see Volume 3-Section 6), which works only with 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 although the following rules are followed by the processors supplied by Sperry Univac:

1. If a field intended to contain the name of a program file is not specified, TPF$ is assumed.

2. If a 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 the previous field, provided that the field exists and was intended to name an element or a program file; otherwise TPF$ is assumed.

The source language processors (ASM, COB, FOR, ALG, etc.) have a common interpretation of several options as well as the first three parameters. The typical standard language processor control statement takes the form:

@COB S I, RO, SO

where SI, RO, and SO represent eltname-1, eltname-2, and eltname-3.

The meanings of these parameters are:

SI (Source Input)

RO (Relocatable Output)

SO (Source Output)

If a new symbolic element is being introduced from the runstream, 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, then this parameter specifies the element and the cycle of the element being updated.

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 produced.

For each file specified in the 51, RO, and SO fields the processor dynamically performs an @ASG,AX.

The file(s) are assigned to the run with exclusive use. This is necessary because the language processor is modifying the table of contents of the file(s) and/or writing in the text portion of the file(s).

If another run has any of the files already assigned with exclusive use, a facility reject occurs and the compilation terminates. This problem would occur when cataloged files are referenced, and the termination of a compilation may be avoided by placing an @ASG,AX control statement for the cataloged file(s) specified in the runstream prior to the language processor control statement.

The source input routine options assist in specifying the type of processing to be performed. (See Volume 4-Table 2-13.)

UP-NUMBER

~

^_Volume 2 EXEC ^{_ _ _ _ _}- - - - L - - - l - - - _ UPDATE LEVEL PAGE

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 SI parameter is assumed.

2. Thel element name from the SI parameter is assumed.

3. If there is no version specified, then the version from the SI parameter is used.

Tables 3-8 and 3·-9 describe the valid possibilities. The I and U options along with the SI parameters determine the interpretation of the processor control statement. An error message is printed if there is any dEwlation from these rules. Table 3-8 is valid for example, for the ASM, COB, FOR, ALG, and

If not completely specified, the information from SI produced. If this symbolic element parameter is not if SO was

If this parameter New relocatable is not completely element and specified, then the· updated symbolic information from

4144.23 UP-NUMBER

I or U Option

Neither

Neither

I Only

I Only

U Only

SPERRY UNIVAC SERIES 1100 Executive System Volume 2 EXEC

Table 3-9. Processors that Require the 51 and SO Parameters

51 Notes SO Notes

Not specified. Illegal to use this parameter.

Parameter is completely If this parameter is void, no source speCified. If SO is void, the output is produced. If it is not L option is assumed. completely specified, then the

information from the SI parameter is used. Invalid to specify a cycle.

Not specified. Illegal to use this parameter.

Parameter is completely Illegal to use this parameter.

specified but without the

cycle.

I

This parameter must be If this parameter is not completely completely specified. specified, then the information from

the SI parameter is used. It is invalid to specify a cyc~e.

Dans le document SPERRY UNIVAC Series 11 00 (Page 122-127)