SAMP,ALPHA
2.2.2.12. Absolute Element Optimization (MINGAP, MINSIZ) Purpose:
Specifies the end of the source language input for the Collector. The END statement is optional. If not given, the end of Collector source language is indicated by the next control statement.
Format:
END Example:
@MAP, I L SERIES OF
COLLECTOR DIRECTIVES END
2.2.2.12. Absolute Element Optimization (MINGAP, MINSIZ)
Purpose:Enables the user to modify the resultant absolute element so as to minimize the liD transfer time when the program is loaded for execution.
Format:
MINGAP value MINSIZ value
144.31
L
SPERRY UNIVAC 1100 Serios Executive_ _ UP_-~U_M_B_ER____ _ _ _ _ V_o_1 u_m_e_3_S_y_s_t_em __ P_ro_cessors
I UPD.:' LEVEL
I PAGE 2-19Param~~ter:
value Specifies any positive integer.
Description:
The program ar,eas created by an assembier R:ES directive or compiler array declarations are unique in- that at collection these areas do not contain meaningful data or instructions. The Collector then has two alternatives when defining these RES areas within the generated absolute element:
'I. The area could be zero filled. This has the effect of increasing the size of the absolute element which affects the mass storage space rE~quirements of the element as well as the number of words which must be transferred when tlhe element is brought into main storage for execution.
2. The area could be left void. This alternative decreases the size of the absolute element at the e>:pense of increasing the number of access control words (ACWs) and hence the number of 1/10 operations needed to transfer the element to main storage for execution.
The Collector uses a combination of these two alternatives depending upon the size of the area. Any area within the absolute element greater than or equal to MINGAP words is left void while those less than MINGAP words are zero filled. Each individual ACW required to transfer the element to main storagE~ also controls a minimum of MINSIZ words. Both MINGAP and MINSIZ are initially set equal to 10.
While the value 10 is felt to be optimum in most cases and it generally does not need to be changed, there may be instances, depending upon type of mass storage and program application, where it is desirable to modify the parameters, For instance, increasing the number of words controlled by each ACW, and decrHasing (he number of I/O operations needed to transfer the program to main storage may reduce the time required to load the program.
2.2.2. '13. Program Parameter Specification (TYPE)
Enables the user to specify certain program applicable conditions.
Format:
TYPE parameter-1,parameter-2, ...
ParamElter:
paramElter-n may be any of the following:
SETAFCM
CLRAFCM
INSAFCM
EXTDIAG
Set Arithmetic Fault Compatibility mode for the absolute or relocatable element.
Set Arithmetic Fault Non--interrupt mode for the absolute or relocatable element.
Set the absolute or relocatable element insensitive to the above Arithmetic Fault modes.
Produce extended diannostic tables for the absolute element.
4144.31
UP-NUMBER
REALTIME
BLOCKSIZE64 COMSEG
SPERRY UNIVAC 1100 Series Executive Volume 3 System Processors
A
UPDATE LEVEL
I 2-20
PAGE
All initial loads and reloads of absolute elements of type REALTIME are done at real-time request priority with real-time positioning. This does not affect processor switching priority.
Set bank sizes into the absolute element in 64 word blocks.
Include all text for a common block in the segment the common block is attached to.
IBJLNK <eltname>,<address>
<eltname> is the name of an element included in the collection, explicitly or implicitly.
NOTE:
Filename may not be used.
<address> is a symbol or numeric value representing an address in the absolute element.
Extend use of BDICALL$/IBJ$ feature to allow collection time definition of parameters to be passed to a routine (see 2.2.9.1).
These parameters may appear in any order on the TYPE directive.
Description:
Within the absolute element's diagnostic tables, the normal entry point name table contains only referenced entry points. The absolute value table contains only referenced absolute entry points and does not include any absolute entry points defined in an element named ERU$ or CERU$. The specification of EXTDIAG prevents any of these exclusions so that all entry points in the element are included in these diagnostic tables.
Parameters SETAFCM, CLRAFCM, and INSAFCM override any related indicators present in the individual relocatable elements included in the collection.
SETAFCM, CLRAFCM, and INSAFCM are only meaningful in collections which produce elements to be executed on an 1110 or 1100/40 System.
The parameter, REALTIME, is used to designate an absolute element as real-time for storage request purposes. All storage requests for programs so designated will be processed at real-time storage priority. The switching level and real-time activity count of the program are not affected until the program does an ER RT$. The storage priority of in-core banks of the program will always be real-time unless all of the program's activities are non-real-time and in a long-wait state, in which case the in-storage banks will be marked long-wait and will be swapable.
Location counters from many elements may define text IO be included in a common block. These location counters may be placed, due to rules of element inclusion, in different segments. The segment at the common point of the others contains the actual area to be occupied by the common block. The loading of one of the segments containing text for the common block will cause reinitialization of part of the common block. The presence of the COMSEG parameter will cause all location counters defining text for a common block to be included in the same segment as the common block area, thus avoiding any reinitinlization of the common block unless that segment is reloaded.
• 4144.31
L
SPERRY UNIVAC 11 00Serjl~s
Executive~NUM8ER _ _ _ _ _ _ _ V_o_' u_m_e_3_S_y_st_e __ m_P_r_o_c,essors I UPO.: LEVEl I 2-21
PAGE
.2.2.2.13.1. Absolute Element Arithmetic Fault Mode Determination
The Collector ·willmark the Arithmetic Fault mode of an absolute element or Collector produced relocatable element in the following order of precedence:
1. If explicit sensitivity is given on the TYPE statement, the output element is marked accordingly, regardless of the sensitivities of the input relocatable elements.
2. If all input relocatable elements have the same sensitivity, the output element is marked with the sensitivity.
3. If both SETAFCM and CLRAFCM relocatable elements are present, the output element is marked with the sensitivity of the relocatable e~ement containing the program start address; if that element is marked INSAFCM or if no starting address exists, then the output element is marked UNKNOWN. In this case (both SETAFCM and CLRAFCM relocatable elements present), the presence or absence of INSAFCM or sensitivity UNKNOWN relocatable elements is irrelevant.
4. If only SETAFCM relocatable elements are present in addition to INSAFCM and/or sensitivity UNKNOWN relocatable elements, the output element is marked SETAFCM.
5. If only CLRAFCM relocatable elements are present in addition to INSAFCM and/or sensitivity UNKNOWN relocatable elements, the output element is marked CLRAFCM.
6. If INSAFCM and sensitivity UNKNO'NN relocatable elements only are present, the output element is marked UNKNOWN.
2.2.2.13.2. EXEC Action Produced by Absolute Element Arithmetic Fault Mode
The Arithmetic Fault mode sensitivity of the absolute element is used by the Executive in determining the initial setting of PSR bit 020. See SPEFtRY UNIVAC 1110, 1100/40 System Processor and Storage Programmer Reference, UP-7970 (curl~ent version). The following describes the action taken by the Executive:
1. If 1the absolute element's sensitivity is UNKNOWN, the system standard set at system generation is used.
2. If the absolute element's sensitivity is SETAFCM, 020 is initially set.
3. If the absolute element's sensitivity is CLRAFCM, 020 is initially cleared.
4. If the absolute element's sensitivity is INSAFCM ,020 is initially cleared.
For standard contingency action related to Arithmetic Faults, see Volume 2-Table 4-2.
2.2.2.13.3. Blocksize
When BLOCKSIZE64 is specified on the TYPE statement, all banks of the program will have their sizes stored in the Bank Load Table of the absolute element in 64-word blocks. In the absence of the BLOCKSIZE64 specification, sizes will be stored in 512-word blocks. The operating system will correctly handle either case for any 1100 Seriies machine, but in the case of the 1100/80 System the presence of BLOCKSIZE64 will improve main storage usage.
4144.31
UP-NUMBER
SPERRY UNIVAC 1100 Series Executive
Volume 3 System Processors
I
UPD.:' LEVELI
PAGE 2-222.2.2.14. Program Segmentation (SEG) Purpose:
Informs the Collector of the beginning of a program segment. All parameters on the SEG directive are optional, except name-1.
Format:
SEG name-1,seg-list Parameters:
name-1 seg-list
Description:
Specifies the name of the segment, name-1.
Specifies the address relationship between the segment named in name-1 and the other program segments named in seg-list.
When name-1 is followed by an asterisk (*), the named segment is automatically loaded when referenced. The asterisk is allowed on all SEG directives, but is ignored if the directive defines the main segment.
The seg-list parameter has several formats which determine the addresses of the segment named in name-1 as follows:
When seg-list is void, the starting address of the name-1 segment immediately follows the last address of the segment named on last preceding SEG directive.
name-2 Specifies that the starting address of the name-1 segment is the same as the starting address of the name-2 segment. These two segments can never exist in main storage at the same time.
(name-2) Specifies that the starting address of the name-1 segment immediately follows the last address of the name-2 segment specified.
(name-2,name-3, ... , name-n) Specifies that the starting address of the name-1 segment immediately follows the highest last I-bank and D-bank address of the seyments specified in name-2, name-3, name-4, etc. Note that the highest last I-bank address may be contained in a segment different than the one containing the highest last D-bank address.
( ) Specifies that the starting address of name-1 segment immediately follows the highest last address of all segments previously named.
For additional information of the SEG directive, see 2.2.4.2.
4144.31
L
SPE;RRY UNIVAC 1100 Series EXlBcutiveI
A 2-22a____ up_-~J_M_BE_R______ __ _____ V_o_'_u_m_e __ 3 __ S_y_s_t_e_m __ P_r_o_c_e_s_so ___ rs ______________________ ~_U_PD._A_TE_L_E_VE_L ____ ~PA_G_E ________ ___