UP 4144_Rev1_1108_Exec_8_Programmers_Reference_1968 4144 Rev1 1108 Exec 8 Programmers Reference 1968

UP-4144_Rev1_1108_Exec_8_Programmers_Reference_1968 UP-4144_Rev1_1108_Exec_8_Programmers_Reference_1968

User Manual: Pdf UP-4144_Rev1_1108_Exec_8_Programmers_Reference_1968

Open the PDF directly: View PDF .
Page Count: 464

Download
Open PDF In Browser	View PDF

E

A

E

UP.4144 Rev. 1

This manual is published by the Univac Division of Sperry Rand Corporation
in loose leaf format. This format provides a rapid and complete means of
keeping recipients apprised of UN IV AC ® Systems developments. The information presented herein may not reflect the current status of the product.
For the current status of the product, contact your local Univac Representative.
The Univac Division will issue updating packages, utilizing primarily a
page-for-page or unit replacement technique. Such issuance will provide
notification of hardware changes and refinements. The Univac Division reserves the right to make such additions, corrections, and/or deletions as,
in the judgment of the Univac Division, are required by the development of
its Systems.
UNIV AC is a registered trademark of Sperry Rand Corporation.
Other trademarks of Sperry Rand Corporation appearing in the text of this
publication are:
UNISERVO
FASTRAND
FASTBAND
PAGEWRITER

© 1968

- SPERRY RAND CORPORATION

PRINTED IN U.S.A.

- -- - - -

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

,--------

SYSTEM

PROGRAMMERS REFERENCE

1

Contents 1
SECTION:

PAGE:

TABLE OF CONTENTS

1.

2.

3.

CONTENTS
INTRODUCTION
EXECUTIVE SYSTEM DESIGN CRITERIA
1.1. OPERATIONAL CAPABILITIES
1.2. EXEC HELATION TO OTHER SYSTEM COMPONENTS
1.3. FUNCTIONAL OBJECTIVES
1.4. RANGE Of EXECUTIVE SYSTEM CAPABILITIES
1.4.1. BATCH PROCESSING
1.4.2. DEMAND PROCESSING
1.4.3. REAL-TIME PROCESSING
1.5. PROGRAM PROTECTION
1.6. MASS STORAGE UTILIZATION TECHNIQUES
1.7. PROGRAM FILES
1.7.1. BASIC CONCEPT
1.7.2. PROGRAM FILE ELEMENTS
1.7.3. ELEMENT NAME AND VERSION
1.7.4. ELEMENT VERSIONS
1.7.5.
'CyCLE' PARAMETER
HARDWARE CONFIGURATIONS
2.1. MINIMUM CONFIGURATION
2.2. STORAGE REQUIREMENTS
2.3.
EXECUTIVE MAIN STORAGE REQUIREMENTS
2.4. TAPE USAGE IMPLIED BY EXECUTIVE OPERATION
2.5. UTILIZATION OF ADDITIONAL HARDWARE
2.6. 1/0 DEVICE-SUPPORT CAPABILITIES
BASIC CONCEPTS OF THE UNIVAC 1108 EXECUTIVE SYSTEM
3.1. DEFINITIONS
3.1.1.

3.1.2.

4.

C:

ACT1V~TY

ACTIV1TY REGISTRATION
3.1.3. 6ATCH PROCESSING
3.1.4. BREAKPOINT
3.1.5. CENTRAL SITE
3.1.6. COLLECTION
3.1.7. COMMUNICATION DEVICE
3.1.8. DEMAND PROCESSING
3.1.9. ELEMENT
3.1.10. EXECUTIVE CONTROL LANGUAGE
3.1.11. FACILITIES
3.1.12. FILE
3.1.13. GRANULE
3.1.14. MULTI-PROGRAMMING
3.1.i5. PACKET
3.1.16. PROCESSOR CALL STATEMENTS
3.1.17. PROGRAM
3.1.18. PR'OGRAM FILE
3.1.19. REAL-TIME PROCESSING
3.1.20. RE-ENTRANT CODING
3.1.21. REMOTE SITE
3.1.22. RUN
~.1.23.
SIMULATED FASTRAND
3.1.2~.
SWAPPING
3.1.2S. SySTEMS PROCESSOR
3.1.26. TASK
3.2. SYSTEM CONVENTIONS
3.2.1. PRIVILEGED INSTRUCTIONS
3.2.2. SYMBOLISM
COMPONENTS OF THE EXECUTIVE SYSTEM
4.1. SUPERVISOR
4.2. EXECUTIVE REQUESTS
4.3. SYMlHONTS
4.4. INPUT-OUTPUT DEVICE HANDLERS
4.5. OPERATOR COMMUNICATIONS
4,6. FILE CONTROL SYSTEM
4.7. DATA HANDLING

1 to 12
1
1-1 to 1-5

1-1
1.. 1
1 .. 1

1-2
1-2
1-2
1-2
1-3
1-3

1 .. 3

1-"
1-"
1-"
1.. 5
1-5

2-1 to 2-10

2-1

2 .. 1
2-2
2 .. 2
2 .. 3
2....
3-1 to 3-4
3 .. 1

3-1
3-1
3-1
3-1
3-1
3-1

3 .. 1

3-1
3 .. 1
3-1
3-2
3-2
3-2
3-2

3.. 2
3-2
3-2
3-2
3-2
3-2
3-2
3-2
3-3
3 .. 3
3-3

3.. 3
3-3

3-3
3-3
4-1 to 4-2

"-1
4-1

.. -1

4-1
4-1
4-1

4.. 1

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

4.8. FILE UTILITY ROUTINES
4.9. AUXILIARY PROCESSORS
4.10. PROCESSOR INTERFACE ROUTINES
4.11. THE DIAGNOSTIC SYSTEM
4.12. SYSTEM SETUP
4.13. UTILITY ROUTINES

5.

EXECUTIVE CONTROL LANGUAGE
5.1. PURPOSE
5.2. STATEMENTS
5.2.1. GENERAL CONTENT
5.2.2. STATEMENT FORMAT
5.2.2.1. LABEL FIELD
5.2.2.2. cOMMAND FIELD
5.2.2.3. OPTIONS FIELD
5.2.2,4. SPECIFICATIONS FIELDS
5,2.2.5. LEADING BLANKS
5.2.2.6. COMMENTS FIELD
5,2.3. CONTINUATION RULES
5.:3. STATEMENT TYPES
5,3.1. GENERAL
5,4. ORGANIZATIONAL STATEMENTS
5.4.1. THE QRUN STATEMENT
5.4.1.1, PRIORITY SUB-FIELD
5.4.1.2. RUN-OPTIONS SUB-FIELD
5.4.1.3. RUN-ID FlELD
5.4.1,4. ACCOUNTING FIELD
5.4.1.5. PRO,JECT FIELD
5.4.1.6. RUNNING TIME/DEADLINE FIELD
5.4.1.7. PAGES SUB-FIELD
5.4.1.8. CARDS SUB-FIELD
5.4.1.9. START-TIME FIELD
5.4.1.10. RUN RESfRICTIONS
5.4.1.11. QRUN STATEMENT EXAMPLES
5.4.2. THE WFIN STATEMENT
5,4.3. THE QLOG STATEMENT
5.4.4. THE WMSG STATEMENT
5.4.5. THE QHDG STATEMENT
5,4.6. THE WADD STATEMENT
5.4.7, THE WSTART STATEMENT
THE WBRKPT STATEMENT
5.4.8.
5.4.9. THE ~SYM STATEMENT
5,4.9.1. USE OF wSYM WITH PRINT$ AND PU~JCH$
5.4.10. THE WCOL STATEMENT
5.4.11. THE WCKPT STATEMENT
5.4.12. THE WRSTRT STATEMENT
5.5. INPUT/OUTPUT SPECIFICATION STATEMErnS
5.5.1. THE QASG STATEMENT
5,5.1.1. NOTATION FOR FILE NAMES
EXCLUSIVE USE FILE AND FACILITY HANDLING
5.5.1.2.
5.5.1.3. THE FASTRANO ~ASG STATEMENT
5.5.1.4. THE MAGNETIC TAPE QASG STATEMENT
5.5.1.5. THE DRUM ~ASG STATEMENT
5.5.1.6. THt:: ARBITRARY DEVICE IiilASG STATElvlENT
5.5.2. THE IiilMODE STATEMENT
5.5.3. THE ~CAT STATEMENT
5.5.4, THE ~FREE STATEMENT
5.5.5. THE WUSE SfATEMENT
5.5.6. THE WELT STATEMENT
5.5.7. THE WUATA STATEMENT
5.5.8. THE IiilEND STATEMENT
THE IiilFILE STATEMENT
5.5.9.
THE IiilENDF STATEMENT
5.5.10,
5.5.11. THE WQUAL CONTROL STATEMENT
5.6. PROCESSOR CALL STATEMENTS

Contents 1
SECTION:

2
PAGE:

4-2
4-2
4-2
4-2
4-2
4-2
5-1 to 5-64
5-1
5-1
5-1
5-1
5-1
5-1
5-2
5-2
5-2
5-2
5-2
5-2
5-2
5-6
5-6
5-6
5-7
5-8
5-8
5-8
5-8
5-9
5-9
5-9
5-10
5-10
5-11
5-11
5-11
5 .. 12
5 .. 13
5-13
5-14
5-15
5-16
5 .. 16
5-18
5-18
5-19
5-19
5 ... 20
5-22
5-23
5-30
5 .. 34
5-35
5-35
5-37
5-39
5-42
5-43
5-45
5-47
5-47
5-48
5-49
5-49

~\

.'-./

~-

."

\\,.....,,/

UP-4144
Rev. 1

(

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

Contents 1
SECTION:

3
PAGE:

""."
.~

5.6.1.
5.6.2.
5.6.3.
5.6.4.

6.

c
7.

NOTATION FOR PROGRAM FILE ELEMENTS
SlATEMENT FORMAT
FORMAT OF CORRECTION LINES
SYSTEM LI~RARIES (PROGRAM FILES)
5.6.~.
A GENERALIZATION
5.7. PROGRAM EXECUTION STATEMENTS
5.7.1. THE folMAP STATEMENT
5.7.2. THE ~XQTSTATEMENT
5.7.3. THE WEOF STATEMENT
5.7.4. THE ~PMD STATEMENT
5.B. CONDITIONAL STATEMENTS
~.8.1.
PUHPOSE OF CONDITIONAL STATEMENTS
5.8.2. STATEMENT LABELS
5.8.3. TIlE LAUEL STATEMENT
5.8.4. THE 'CONDITION' WORD
5.8.5. THE lalSETC STATEMENT
5.8.6. THE WJUMP STATEMENT
5.8.7. THE ~TEST STATEMENT
5.9. STATEMENT SYNTAX ERROR DIAGNOSTICS
5.10. STATEMENT FORMAT SUMMARY
BASIC OPERATIONAL DESCRIPTIONS
6.1. BATCH PROCESSING
6.1.1. RUN PREPARATION
6.1.1.1. TYPICAL RUN INPUT ARRANGEMENT
6.1.2. HUN SUBMISSION
6.1.3. RUN SCHEDULING
6.1.4. RUN EXECUTION
6.1.5. POST-RUN PROCESSING
6.2. DEMANU PROCESSING
6.2.1. CONTROL STATEMENTS
6.2.2~
CONVERSATIONAL COMPONENTS
6.2.2.1.
SYMBIONT COMPLEX
6.2.~.2.
HE-ENTRANT CONTROL
6.2.2.3.
PROGRAM LIBRARY SERVICES
6.3. REAL TIME PROCESSING
6.3.1. PRIORITY
6.3.2. TIMING
6.3.2.1. E~I INTERRUPTS
6.3.2.2. REAL-TIME WORKERS
SUPERVISOR
7.1. GENERAL
7.2. MULTI-PROCESSING
7.3. SCHEDULING
7 • .3. 1. GOJERAL
7.~.2.
FACILITIES INVENTORY
7.3.3. CONTHOL STATEMENT INTERPRETER(CSI)
7.3.4. COARSE SCHEDULER
7.3.4.1. BATCH SCHEDULING
7.3.4.2. DEMAND SCHEDULING
7.3.4.3. SUMMARY
7 • .3.5. THE DYNAMIC ALLOCATOR
7.3.5.1.
7.3.5,2.

C...

O,.

G~NERAL

CORE ALLOCATION
7.3.5.3. PROGRAM TYPES
7.3.5.4. SHARING BETWEEN PROGRAM TYPES
7.3.5.5. PROGRAM STATES
7.3.5.6. TAdLES AND QUEUES
7.3.5.7. CPU ALLOCATION
7.3.6. CORE CONTENTS CONTROL(CCC)
7.4. DISPATCHER
7.4.1. SwITCHING
7.4.1.1. REAL TIME SWITCHING
7.4.2. S~ITCH LISTS
7.4.3. COMMON DATA PROTECTION

5 .. 49
5 .. 50

5.. 53
5-54
5-55
5-55
5 .. 55
5 ... 55
5 ..56

5-56
5-57
5 ...57
5-58
5 ..59
5-59
5-61
5 ..61
5 .. 61

5 .. 63
5 .. 63
6-1 to 6-7
6-1
6-1

6 ... 1
6 .. 2
6-2
6-3

6 .. 3
6 .. 3
6 ... 4
6-5
6 ... 5
6-5

6-5
6-6
6-6
6-6
6 ..6
6-7
7-1 to 7-44

7.. 1

7 .. 2
7 ... 3
7-3
7-3

7-4
7-5
7-5
7-8
7-10
7 .. 10
7 .. 10
7-11
7 ... 12
7-12

7 .. 13
7-14
7-15
7-16
7 .. 17
7-18
7 ... 18
7.. 18
7-18

UP-4144

Rev. 1

8.

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS· REFERENCE.

7.5. INTERRUPT PROCESSING
7.5.1. INPUT/OUTPUT INTERRUPTS
7.5.2. COMPUTER/CORE MALFUNCTIONS
7.5.2.1. CONTROL MEMORY PARITY ERROR
7.5.2.2. INPUT/OUTPUT DATA PARITY
7.5.2.3. CORE STORAGE PARITY ERROR
7.5.2.4. POWER FAILURE
7.5.2.5. MESSAGE FORMAT
7.5.3. PROGHAM CONTINGENCY
7.5.4.
ESI CONTINGENCY
7.6. TIMING ROUTINES
7.6.1. GENERAL
7.6.2. REAL-TIME CLOCK
7.6.3. DAY CLOCK
7.7.
LOGGING AND ACCOUNTING
7.7.1. LOG CONTROL
7.7.2. RUN TERMINATION ACCOUNTING
7.7.3. BILLING
7.7.4. MASTER RUN LOG
7.7.4.1. LOG CONTROL CARD OR EXECUTIVE REQUEST LOG ENTRy
7.7.4.2. FACILITY USAGE LOG ENTRY
7.7.4.3. CATALOGUED MASS STORAGE FILE USAGE ENTRY
7.7.4.4. PROGRAM TERMINATION LOG ENTRY
7.7.4.5. RUN TERMINATION LOG ENTRY
7.7.4.6. I/O ERROR LOG ENTRY
7.7.4.7.
CONSOLE LOG ENTRIES
7.7.4.8.
RUN INITIATION
7.7.4.9.
CONSOLE REPLIES
7.7.5. SUMMARY ACCOUNTING FILE
7.8. CHECKPOINT/RESTART
7.8.1. GENERAL
7.8.2. USER-CHECKPOINT INTERFACE
7.8.c.l. PROGRAM REQUEST
7.8.2.2. CONTROL STATEMENT REQUEST
7.8.2.3.
UNSOLICITED REQUEST
7.8.3. DUMPING TEC~NIQUES
7.8.3.1, TAPE
7.8.3.2. FASTRAND
7.8.3.3. CONTROL MESSAGES
7.8.3.4. STATUS CODES
7.8.4. USER-RESTART INTERFACE
7.8.4.1. PROGRAM REQ~EST
7.8.4.2. CONTROL STATEMENT REQUEST
7.8.4.3. UNSOLICITED REQUEST
EXECUTIVE REQUEST FUNCTIONS
8.1. GENERAL
8.2. ACTIVITY REGISTRATION
8.2.1. FORK$
8.2.2. TIMEU ACTIVITy REGISTRATION
8.2.3.
TIMED WAIT
8.2.4. WAIT CONDITIONS
8.3. ACTIVITY NAMING AND INTERACTION.
&.3.1.
NAMING TECHNIQUE.
8.3.2.
ACTIVITY ACTIVATION (ACT$)
8.3.3.
ACTIVITY DEACTIVATION (DACT$
8.3.4. ACTIVITY DELETION (ADLT$)
tl.4. TERMINATION
8.4.1. THE EXIT FUNCTION
8.4.2. THE ABORT FUNCTION
8.4.3. THE ERR EXIT
8.5. FILE SUPERVISION
8.5.1. BUFFER POOL EXPANSION
8.5.2. BUFFER POOL SETUP
8.5.3. COMMUNICATIONS BUFFER POOL ADDITION

Contents 1
SECTION: .

4
PAGE:

7-19
7-19
7-19
7-19
7-20
7-20

7-20
7 .. 20

7-21
7-25
7-26

7-26
7 ... 26

7-26
7-27

7-28
7-28
7-28
7-29

7-29
7-30

7-31
7-32

7-33
7-34

7-35
7-36
7-37

7-38
7-40

7-40
7-40

7-40
7-41
7-41

7-41
7-42
7-42

7-42
7-43

7-43

7-44
7 .. 44
7-44
8-1 to 8-20
8-1
8-1
8-2
8-3
8-3
8-3
8-3
8-4
8-4
8-4
8-4
8-5
8-5
8-5
8-5
8-5
8-6
8-6
8-6

r-~

'-....)

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

8.5.4.

,9.

SYSTEM
REFERENCE

COMMUNICATIONS BUFFER POOL REMOVAL
COMMUNICATIONS BUFFER POOL SETUP
d.5.6. DiRECTORY ITEM RETRIEVAL
8.~.7.
FACILITY DETERMINATION
8.5.8. TAPE REEL NUMBER SET INITIALIZATION
8.5.9. TAPE SWAPPING
8.6. REAL-TIME
8.7. REENTRANT ROUTINES
d.7.1. REENTRANT ENTRY
8.7.2. REENTRANT RETURN
8.8.
DYNAMIC FACILITIES
8.8.1. REQUEST ADDITIONAL CORE
8.8.2. RELEASE OF UNNEEDED CORE
B.8.3. CONTROL STATEMENT FORMAT REQUESTS-CSF$
8.9.
INPUT/OUTPUT
8.10. CONSOLE COMMUNICATIONS
8.11. SY~BIONT CONTROL
A.12. CHECKPOINT/RESTART
8.12.1. CHECKPOINT
8.12.2. RESTART
8.13. MISCELLANEOUS
8.1.5.1.
UNLOCK
8.13.2. OPTION LETTER RECOVERY
8.13.3.
11M!:. AND DATE
8.13.4. READ PROGRAM CONTROL TABLE
5.13.5. SNAP~HOT DUMPS
8.13.6. THE CONDiTION WORO
8. 13.6. 1 •
SE T
8.1..3.6.2.
RETrU'EVE
8.13.1. SEGMENT LOADING
8.1Lt. SUMMARY
SYMBIONTS
9.1. GENERAL DESCRIPTION
9.2. HEAD'!;
9.2.1. CLIST'!>
9.2.2. TREAD1>
9.2.3.
ALTERNATE INPUT FILES (READA$)
9.3.
PRINH
9.3.1.
ALIERNATE PRINT FILES (PRNTA$)
9.'+.
PUNCH$
9.4.1.
ALT~RNATE PUNCH FILES (PNCHA~)
9.5.
SYMBIONT CONTHOL
9.5.1.
OUTPUT CONTkOL
9.5.1.1.
PRTCN~ CONTROL FUNCTIONS
9.5.1.2.
PCHCN'f, CO),JTROL FUNCTIONS
9.5.1.3.
INTERNAL BREAKPOINT FUNCTIO
9.5.1.Lt.
INTERNAL FILE QUEUEING
9.5.2.
INPUT CONTROL
9.5.3.
SYMIllONT ERROR CODE DEFINITIONS (E,.jODE TYPE 02)
9.6. ON-SITE DEVICE HANDLERS
9.6.1.
INPUT OPE!ll\TION
9.6.2.
OUTPUT QUEUEING.
9.6.J. UEVIC£ TYPES AND RECOVERY PROCEDURES
9.6.3.1.
900/300 CARD SUBSYSTEM
9.b.3.2.
0755 HIGH SPEED PRINTER SURSYSTEM
9.6.3.3.
1004 SUBSYSTEM
9.7.
REMOTE 1004-BATCH OPERATION
9.8. REMOTE DEMAND OPERATION
9.8.1. GENERAL DEMAND TERMINAL HANDLER FEATURES
9.8.2.
INITIAtION PROCEDURES
9.8.3. TERMiNATION OF DEMAND RUNS
9.8.3.1.
TELETYPE* MODEL 35 ASR-KSR MACHINES
9.9. SYSTEM GENERATION PARAMETERS
9.9.1.
DEVICE A~SOCtATION
8.5.~.

c

OPERATING

PROGRAMMERS

Contents 1
SECTION:

5
PAGE:

8-7
8-7
8-7
8-7
8-7
8-8
8-8
8-9
8-9
B-9
8-9
8-9
8-10
8-10
8-13
8-13
8-14
8-14
8-14
8-15
8-15
8-15
8-15
8-15
8-16
8-16
8-17
8-17
8-17
8-17
8-17
9-1 to 9-34
9-1
9-3
9-4
9-5
9-5
9-6
9-7
9-7
9-8
9-8
9-9
9-9
9-10
9-11
9-11
9-11
9-11

9-12
9-12
9-13
9-13
9-15
9-17
9-18
9-21
9-25
9-26
9-26
9-26
9-27
9-29
9-29

UP-4144
Rev. 1

10.

UNIVAC 1.108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

9.9.2. PROBE
9.9.3.
MASS STORAGE REQUIREMENTS
9.10. REMOTE DCT-2000 BATCH OPERATIONS.
9.10.1. STANDARD SWITCH SETTINGS
9.10.2. OCT-2000 SPECIAL CONTROL CARDS
9.10.3. REMOTE OCT-2000 INITIALIZATION
9.10.4. REMOTE OCT-2000 INPUT
9.10.5. REMOTEOCT-2000 OUTPUT
9.10.5.1. REMOTE DCT-2000 PRINT
9.10.5.2. R~MOTE OCT-2000 PUNCH
9.10.6. OCT-2000 ~EL SEQUENCE
INPUT/OUTPUT DEVICE HANDLERS
10.1. I/O CONTROL
10.1.1. GENERAL
10.1.2. QUEUEING AND UNIT CONTROL
10.1.3. INPUT/OUTPUT PACKET
10.1.4. PROGRAM-I/O SYNCHRONIZATION
10.1.4.1. STATUS CODES
10.1.5. ERROR MESSAGES
10.2. MAGNETIC TAPE HANDLER
10.2.1. EQUIPMENT
10.2.2. OPERATION
10.2.3. THE SET MODE REQUEST
10.2.4. STANDARD RECOVERY
10.2.5. CONSIDERATIONS FOR IV/VI/VIIIC TAPE TYPES
10.2.6. r-1UL Tl PLE-CHANNEL OPERATION
10.3. MAGNETIC DRUM HANDLER
10.3.1. EQUIPMENT
10.3.2. OPERATION
10.3.3. RECOVERY
10.3.4. MULTIPLE-CHANNEL OPERATION
10.4. FAST HAND HANDLER
10.4.1. GENERAL
10.4.2. EQUIPMENT
10.4.3. OPERATION
10.4.4. RECOVERY
10.5. ARBITRARY DEVICE HANDLER
10.5.1. GENERAL
10.5.2, OPERATION
10.6. COMMUNICATIONS MULTIPLEXOR HANDLER
10.6.1. GENERAL
10.6.2. EQUIPMENT
10.6.3. ASSIGNING LT DEVICES
10.6.4. THE LT CONTROL TABLE
10.7.
COMMUNICATION OPERATIONS
10.7.1.1. FIRST LEVEL SUPPORT
10.7.2. FIRST LEVEL SUPPORT
10.8. COMMUNICATION INITIALIZATION
10.6,1. OUTPUT INITIALIZATION
10.6.2.
INPUT INITIALIZATION
10.6.3.
INITIALIZATION ERRORS
10.8.3,1. OUTPUT ERRORS
10.8,3.2, INPUT ERRORS
10.9. DIALING
10.9.1.1.
DIAL ERRORS
10.10, INPUT
10.10.1. SINGLE MODE
10.10.2. POOL MODE
10.10.3. INPUT ERRORS
10.11. OUTPUT
10.11.1.
SINGLE MODE
10.11.2.
POOL MODE
10.11.3. OUTPUT ERRORS
10,11.3.1. SECOND LEVEL SUPPORT

Contents 1
SECTION:

6
PAGE:

9-30
9-30
9-30
9-31
9-31
9-32
9-32
9-33
9-33
9-33
9-33
10-1 to 10-70
10-1
10-1
10-2
10-3
10-5
10-6
10-8
10-10
10-10
10-10
10-12
10-14
10-15
10-16
10-19
10-19
10-19
10-21
10-22
10-22
10-22
10-23
10-23
10-26
10-26
10-26
10-27
10-32
10-32
10-32
10-33
10-33
10-38
10-38
10-38
10-38
10-39
10-40
10-40
10-41
10-41
10-42
10-43
10-43
10 ... 43
10-44
10-45
10-45
10-45
10-46
10-47
10-47

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

Contents 1
SECTION:

7
PAGE:

o
BUFFER FORMATS
ERROR CODES
10.12. HANG-UP
10.13.
COMMUNICATION TERMINATION
10.13.1.
TERMINATION ERRORS
10.14.
f(OUTES
10.14.1.
ROUTE$ CALLING SEQUENCE
10.14.2.
ROUTING PROCEDURES
10.14.3.
ROUTE$ ERROR CODES
10.15. COMPLETION ACTIVITIES
10.15.1. ESI ER REQUESTS
10.15.1.1. ESI EXITs
10.15.1.2. ESI ACT$
10.15.1.3. ESI CADDs
10.15.1.4. ESI ADACTS
10.16. IDLE LINE MONITOR
10.17. TIMING CONSIDERATIONS
10.17.1. INTERRUPT LEVEL
10.17.2. BUFFER LEVEL
10.17.3. ANALYSIS LEVEL
10.17.4. ERROR CODES FOR LT CONTINGENCIES
10.18. REAL-TIME SYSTEM CONSIDERATION
10.18.1. PROGRAM LOCATION
10.18.2. EXECUTION
10.18.3. BUFFER OPERATIONS
10.18.3.1. TRANSMISSION TYPES
10.18.3.2. CORE AVAILABITY
10.18.3.3. POOL SIZE
10.18.3.4. BUFFER SIZE
10.18.4. PRIORITY CATEGORIES
10.18.4.1. CATEGORY A
10.18.4.2. CATEGORY B
10.18.4.3. CATEGORY C, 0, ANO E
10.18.4.4. CATEGORY G AND H
10.18.4.5. PRIORITY CONTROL
10.18.4.6. RT$ AND NRT$ ER REQUEST
1U.18.4.7. FORKS
10.18.4.8. UNLCK$
10.18.5. TEST AND SET USAGE.
OPERATOR COMMUNICATIONS
11.1. GENERAL
11.2. SYSTEM MESSAGES
11.2.1. MESSAGE CLASSIFICATION
11.2.2. M~SSAGE TYPES
11.2.2.1. UNSOLICITED
11.2.2.2. TYPE
11.2.2.3. TYPE AND READ
11.2.3.
KEYBOARD OPERATIONS-TELETYPE* MODEL 35 MACHINE
11.2.4. KEYBOARD OPERATIONS - CRT DISPLAY CONSOLE
11.3. SYNOPSIS OF SYSTEM MESSAGES
11.3.1. SYSTEM CONTROL MESSAGES
11.3.1.1. FACILITY CONTROL
11.3.1.2. COARSE SCHEDULER
11.3.1.3. DYNAMIC ALLOCATOR
11.3.2. TERMINATIONS
11.3.2.1. ABORT$
11.3.2.2. EHR$
11.3.2.3. INTERRUPT
11.3.2.Q. CHECKPOINT/RESTART MESS~GES
11.3.3. INPUT/OUTPUT ACTIVITY MESSAGES
11.3.3.1. ON-SITE PERIPHERAL DEVI~E HANDLER
11.3.3.2. ON-SITE SYMBIONT MESSAGES
11.3.4. COMMUNICATIONS ACTIVITY MESSAGES
11.3.4.1. COMMUNICATIONS DEVICE HANDLER
10.11.3.2.
10.11.~.

11.

10-47
10-50
10-51
10-51
10-51
10 ... 51
10-52
10-52
10 ..52
10 ..53
10 ..53
10-53
10-53
10-54
10-54
10-54
10-54
10 .. 55
10 .. 55
10-57
10 ..57
10-63
10-63
10-63
10-63
10 ..61J
10-64
10 ...64
10 ..65
10 ..66
10-67
10 ...67
10 ...67
10-67
10 ..68
10-68
10 ...68
10-69
1.0-69
11-1 to 11-14
11-1
11-1
11-1
11-1
11 .. 2
11 ..2
11-2
11"2
11 .. 3
11-3
11-3
11-3
11-4
11-5
11-6
11-6
11-6
11-6
11-6
11-8
11-8
11-8
11 ... 10
U ... lO

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

11.3.'+.2. REMOTE SYMBIONT MESSAGES
11.3,5. HARDWARE CONFIDENCE MESSAGES
INITIAL LOAD MESSAGES
11.3,6.
11.'+. USER CONSOLE REQUESTS
11.'+.1. SYSTEM ENTRANCE-COM$
11.'+.2. PROCEDURE DEFINITIONS-C$OM AND C$OMPK
11.4.3. STATUS COOES

12.

13.

FILE CONTROL SYSTEM
12.1. FILE SUPERVISION
12.2. FILE ORGANIZATION
12.2.1. MASTER DIRECTORY
12.2.2, MASS STORAGE ALLOCATION
12.2.2.1. GENERAL
12.2.2.2. SPACE AVAILABILITY CONTROL
12.2.2.3. MASS STORAGE UNIT AVAILABILITY CONTROL
12.2.2.4. ROLLOUT OF FILES TO MAGNETIC TAPE
12.3. fILE REFERENCING
12.3.1. FILE CONTROL TABLE GENERAL FORMAT
12.3.2. DIRECTORY ITEM RETRIEVAL
12.3.3. FILE ASSIGNMENT DETERMINATION
12.3.4. MAGNETIC TAPE LOADING
12.3.5. FILE SECURITY
12.3.6. BUFFEH SETUP
12.3.7. COMMUNICATIONS BUFFER POOLS
12.3.8. EXCLUSIVE USE OF FILES
DATA HANDLING
13.1. GENERAL
13.2. fORMAT DEFINITION
13.2.1. THE FORMAT PROCEDURE
13.2.2. TrlE RECORD-TyPE PROCEDURE
13.2 • .5. THE SECTION-NAME PROCEDURE
13.2.'+. THE SUBROUTINE-NAME PROCEDURE
THE END-FORMAT PROCEDURE
13.2~5.
13.2.6. EXAMPLE-COMPLETE FORMAT DEFINITION
13.2.7. RULES FOR CODING FORMAT SUBROUTINES
13.2.7.1. LABEL RECORD SUBROUTINES
13.2.7.2. BLOCK RECORD SUBROUTINES
13.2. -, .3.
ITEM RECORD SUBROUTINES
13.2.7.4. END OF REEL SUBROUTINES
13.2.7.5. ENU-OF-FILE SUBROUTINES
ITE~1 CONTROL
13.3.
13.3.1. OUTPUT
13.3.1.1. OPEN OUTPUT
13 • .5.1.2. WRITE
13.3.1.3. WRITE RANDOM
13.3.1.4. DRAIN
13.3.1.5. CLOSE REEL
13.3.1.6. CLOSE FILE
13.3.1."'. RELEASE
INPUT
13.3.2.
13.3.2.1. OPEN INPUT
READ
~3.3.2.2.
13.3.2.3. READ RANDOM
13.3.2.4. DRAIN
13.3.2.5. CLOSE REEL
13.3.2.6. CLOSE FILE
13.3.2.7. RELEASE
IN/OUT
13.3.3.
13.3 • .3.1. OPEN IN/OUT
13.3.3.2. READ-WRITE
13.3. • .3.3. READ-WRITE RANDOM
13.3.3.'+. EXCLUSIVE READ RANDOM
13.3.3.5. CLOSE FILE
13.3 • .5.6. RELEASE

Contents 1
SECTION:

8
PAGE:

11-10
11-11
11-11
11-12
11-'12
11-13
11-1'+

·12-1 to 12-18
12-1
12-1
12-1
12-2
12-2
12-3
12-3
12-4
12-5
12-5
12-5
12-7
12-10
12-12
12-12
12-14
12-18
13-1 to 13-55
13-1
13-2 ~.
1:5-3 \,,--J
13-3
13-'+
13-5
13-6
13-7
13-8
13-9
13-9
13-9
13-10
13-10
13-11
13-11
13-11
13-12
13-13
13-13
13-13
13-14
13-14
13-15
13-16
13-16
13-17
13-17
13-18
13-18
13-18
13-19
13-19
13-19
13-20 I~
13-20
13-20
13-21

Go

UP-4144
Rev. 1

C'
/'

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

13.3.4. ITEM LAYOUT
13.3.4.1. SINGLE ITEM LAYOUT
13.3.4.2. BLOCKED ITEM LAYOUT
13.4. LABEL AND SENTINEL CONVENTIONS
13.4.1. OUTPUT
13.4.2. INPUT
13.5. BLOCK BUFFERING PACKAGE
13.5.1. OUTPUT
13.5.1.1. OPEN OUTPUT
13.5.1.2. WR I TE
13.5.1~3.
WRITE RANDOM
13.5.1.4. CLOSE REEL
13.5.1.5. MARK
13.5.1.6. CLOSE FILE
13.5.1.7~
RELEASE
13.5.2. INPUT
13.5.2.1. OPEN INPUT
13.5.2.2. READ
13.5.2.3. READ RANDOM
13.5.2.4. CLOSE REEL
13.5.2.5. CLOSE FILE
13.5.2.6. RELEASE
13.5.3. IN/OUT
13.5.3.1. OPEN IN/OUT
13.5.3.2. READ-WRITE
13.5.3.3. REAO";WRITE RANDOM
13.5.3.4. EXCLUSIVE READ RANDOM
13.5.3.5. CLOSE FILE
13.5.3.6. RELEASE
13.5.4. ~LOCK LAYOUT
13.6. FILE CONTROL TABLE
13.6.1. THE FILE PROCEDURE
13.6.1.1. 'FILENAME' LIST
13.6.1.2. 'SIZE' LIST
13.6.1.3. 'POOL~ LIST
13.6.1.4. 'ERROR' LIST
13.6.1.5. 'SENT' LIST
13.6.1.6. '~ABEL' LIST
13.6.1.7. 'FREEWD' LIST
13.6.1.8. 'EOR' LIST
13.6.2. FIL~ PROCEDURE LAYOUT
13.7.
BUFFER POOL
13.8.
ERROR PROCESSING
13.8.1.
DEVICE ERRORS
13.8.2.
FILE ERRORS
13.8.3.
A~NORMAL CONDITIONS
13.9. BLOCK BUFFERING ER REQUEST CALLING SEQUENCES
13.9.1. OPEN FUNCTION
13.9.2. WRITE FUNCTIONS
13.9.2.1.
FORM 1
13.9.2.2.
FORMS 2-4
13.9.3. READ FUNCTIONS
13.9.3.1.
FORM 1
13.9.3.2.
FORMS 2-3
13.9.4. RANDOM WRITE FUNCTIONS
13.9.4.1.
FORM 1
13.9.~.2.
FORMS 2-4
13.9.5. RANDOM READ FUNCTIONS
13.9.5.1.
FORM 1
13.9.~.2.
FOR~S 2-3
13.9.6. CLOSE REE~/FILE FUNCTIONS
13.9.7. ;';RITE. EOF fUNCTION
13.10. ITEM HANDLER CALLING SEQUENCES
13.11. FILE ORGANIZATION

Contents 1
SECTION:

9
PAGE:

13 ... 21
13-21
13... 23
13... 24
13-24
13-24
13-25
13-25
13.. 25
13-25
13-26
13-26
13-27
13-27
13-27
13-27
13-28
13-28
13-28
13-29
13-29
13-29
13.. 29
13-30
13-30
13-30
13-30
13-31
13-31
13-32
13-33
13-33
13-33
13-34
13 .. 35
13-35
13-35
13-36
13-36
13-37
13-37
13-39
13-40
13-40
13-40
13-41
13-42
13-42
13-43
13-43
13-43
13-43
13-43
13-44
13-44
13-44
13-44
13-45
13-45
13-45
13-45
13-45
13-45
13-48

UP-4144

Rev. 1

15.

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

13.11.1. ITEM LEVEL TAPE FILES
13.11.2. ITEM LEVEL FASTRAND FILES
13.11.3. BLOCK BUFFERING LEVEL TAPE AND FASTRAND FILES
13.12.
SYSTEM DATA FILE FORMAT (SDF)
13.12.1.
FORMAT DEFINITION
13.12.2. FILE CONVENTIONS
13.12.3.
LABEL IMAGES
FILE UTILITY ~OUTINES (FURPUR)
14.1. GENERAL
14.2. STATEMENT FORMAT
14.2.1. CONTENTS OF SPECIFICATION FIELDS.
14.2.2. FILE ASSIGNMENTS
14.2.3. OPTIONS FIELD
14.3.
SHOKTHAND NOTATION.
14.4. FURPU~ STATEMENTS
14.4.1. r.lCOPY
14.4.1.1. FORMATTING THE QCOPY STATEMENT
14.4.1.2. EXAMPLES OF THE QCOpy STATEMENT.
14.4.2. r.JCOPOUT
14.4.2.1. FORMATTING THE QCOPOUT STATEMENT.
14.4.2.2. EXAMPLE OF THE USE· OF QCOPOUT
1 '+.4.3. fOlCOPIN
14.4.3.1. FORMATTING THE QCOPIN STATEMENT.
14.4.3.2. EXAMPLES OF THE r.JCOPIN STATMENT
14.4.4. ~DELETE
14.4.4.1. FORMATTING THE QDELETE STATEMENT
14.4.4.2. EXAMPLES OF THE QDELETE STATEMENT.
14.4.5. raJPRT
14.4.5.1. FORMATTING THE QPRT STATEMENT
14.4.5.2. EXAMPLES OF THE QPRT STATEMENT.
14.4.6. gPCH
14.4.6.1. FORMATTING THE QPCH STATEMENT.
14.4.6.2. EXAMPLES OF THE QPCH STATEMENT:
14.4.7. foiCHG
14.4.7.1. CATALOGUED FILES
14.4.7.2. PROGRAM FILE ELEMENTS
14.4.7.3. EXAMPLES OF THE QCHG STATEMENT:
14.4.8. IGlPACK
14.4.9. ialPREP
14.4.10. iOlERS
14.4.11. QREWIND.
14.4.12. r.JMARK
14.4.13. QCLOSE.
14.4.14. fcilMOVE.
14.4.15. (.lFIND
14.4.16. iOlCYCLE.
14.4.16.1. FORMATTING THE QCYCLE STATEMENT.
14.4.16.2. EXAMPLES OF THE ~CYCLE STATEMENT
14.4.17. ~ENABLE
14.5. MULTIREEL FILES
AUXILIARY PROCESSORS
15.1. THt COLLECTO~
15.1.1. GENERAL
15.1.2. EXECUTIVE CONTROL STATEMENTS
15.1.2.1. THE ~MAP CONTROL STATEMENT
15.1.2.2. THE ~XQT CONTKOL STATE~ENT
15.1.3. COLLECTOR CONTROL STATEMENTS
15.1.3.1. GENERAL
15.1.3.2. THE IN STATEMENT
15.1.3.3. TilE NOT STATEMENT
15.1.3.4. THE LIB STATEMENT

i~:~:~:~: ~~~ ~~~GS~t!i~~~~T
15~1.j.7.

THE RSEG STATEMENT

Contents 1
SECTION:

10
PAGE:.

13-48
13-53
13-53
13-54
13-54
13-55
13-55
14-1 to 14-16
14-1
14-1
14-1
14-2
14-2
14-2
14-2
14-3
14-3
14-5
14-6
14-6
14-6
14-7
14-7
14-8
14-8
14-8
14-9
14-9
14-9
14-10
14 .. 10
14-10
14-11
14-11
14-11
14-12
14-12
14-13
14-13
14 ... 13
14-13
14... 14
14-14
14-14
14-14
14-15
14-15
14-15
14-15
14-16
15-1 to 15-23
15... 1
15... 1
15-2
15... 2
15-5
15-5
15-5
1"5-6
15-7
15-7
15;'7
15-8
15-9

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

Contents 1
SECTION:

11
PAGE:

o
15.1.3.8. THE DEF STATEMENT
15.1 • .3.9. THE REF STATEMENT
15.1.3.10. THE ENT STATEMENT
15.1.3.11. THE EQU STATEMENT
15.1.3.12. THE CLASS STATEMENT
15.1.3.13. THE COR STATEMENT
15.1.3.14. THE SNAP STATEMENT
15.1.3.15. THE END STATEMENT
15.1.'+. FUNCTIONAL ASPECTS
15.1.5. COLLECTOR DEFINED SYMBOLS
15.1.6. PROGRAM SEGMENTATION AND LOADING
15.2. THE PROCEDURE DEFINITION PROCESSOR
15.2.1. GENERAL
15.2.2. ASSEMBLER PROCEDURES
15.2.3. FORTRAN PROCEDURE
15.2.'+. COBOL PROCEDURE
15.3. THE ~EO STATEMENT

16.

17.

( ;.
.

./

PROCESSOR INTERFACE ROUTINES
16.1. GENERAL
16.2. SOURCE INPUT ROUTINE (SIR)
16.3.
PREPROCESSOR ROUTINE (PREPRO)
16.4, SOURCE OUTPUT ROUTINE (SOR)
16.5. RELOCATABLE OUTPUT ROUTINE (ROR)
16.6.
PREAMBLE OUTPUT ROUTINE (TBLWR)
THE DIAGNOSTIC SYSTEM
17. I, GEI'>IERAL
17.2, SNAPSHOT DUMPS VIA A PROCESSOR
17.2.1, BASIC OPERATION
17.2,2. AVAILABLE SNAPSHOT DUMP TYPES
17.2.3. THE CONDITIONAL PROCEDURES
17.2,3.1. THE X$IF PROCEDURE
17.2 • .3.2. 'THE X$AND PROCEDURE
17.2,3~3.
THE X$OR PROCEDURE
17.2,3.4. THE X$TALY PROCEDURE
17,2.3.5.
EXAMPLE.
17.2.4. THE DUMP PROCEDURES
17.2.4.1. THE X$MESG PROCEDURE
17.2.4.2. THE X$CORE PROCEDURE
17.2.4.3. THE X$DUMP PROCEDURE
17.2,4.4.

THE X$TAPE PROCEDURE
THE X$DRUM PROCEDURE
THE X$FILE PROCEDURE
17.2.~.8.
EXAMPLES.
17.2.5. THE SPECIFICATION PROCEDURES
17.2.5.1. THE X$FHMT PROCEDURE
17.2.S.2. THE X$BUFR PROCEDURE
17.2.5.3. THE X$MARK ANO X$BACK PROCEDURES
17.2.5.4. THE X$ON AND X$OFF PROCEDURES
17.2.5.5.
EXAMPLES.
17.2.b. ASYNCRONOUS ACTIVITY DIAGNOSTIC CALLS
17.3. THE PMD STATEMENT
17.3.1. GENERAL
17.3.2. OPTIONS
17.3.2.1. GENERAL OPTIONS
17.3.2.2. SPECIAL OPTIONS
17.3.2.3. OPTIONS USED WITH SPECIAL OPTIONS
17.3.2.4. THE 'BLANK, OPTION
17.4.
PMD AND DYNAMIC DUMP CORRELATION
SYSTEM SETUP
18.1. 1108 EXECUTIVE SYSTEM GENERATION
18.1.1. GENERAL
18.1.2. PROCEDURES
18.1.j. SYSTEM GENERATION STATEMENTS
17.2.~,5.

17.2,4.6.
17.2.4.7,

18.

15-9
15-9
15-9

15-9
15-10
15-11
15-11
15-12
15-12
15-13
15-13
15-16
15-16
15-18
15.. 18
15-19
15-19
16-1 to 16-6
16-1
16-1
16-4
16-4
16-5
16-6
17-1 to 17-12
17-1
17-1
17-1
17-1

17-1
17-2
17-2
17-2
17-2
17-2
17-3
17-3
17-3
17.. 4

17-4
17-4
17-5

17-5

17-5
17-7

17-7
17-7
17-8
17-8
17-8
17-9

17-9
17-9
17-10
17-10
17-10
17-11
17-11
17-12
18-1 to 18-24
18-1
18-1
18-1
18-2

UP-4144

UNIVAC 110B OPERATING

Rev. 1

EXEC B

19.

SYSTEM

PROGRAMMERS REFERENCE

18.1.4. INITIA~ SYSTEM
18.2. SYSTEM LOADING
18.2.1. INITIAL LOAD CONSOLE COMMUNICATIONS
18.3. SYSTEM GENERATION
18.3.1. INTRODUCTION
18.3.2. CALLING SEQUENCE FOR THE SGR
18.3,3. SYSTEM GENERATION STATEMENTS
18.3.4. CORR~CTIONS
18.3.5. SKELETON
18.3,5.1. SYSTEM GENERATION STATEMENT REFERENCES
18.3.5.2. CORRECT DIRECTIVE CARD
18.3.5.3. IF DIRECTIVE CARD
18.3.5.4. INCREMENT DIRECTIVE CARD
18.3.5.5. DEFINE PROCESS DIRECTIVE CARD
18.3.5.6. PROCESS DIRECTIVE CARD
18.3,5.7. SYNTACTICAL DESCRIPTION
18.3.6. SKELETON CORRECTIONS
18.3.7. OPTIONS
UTILITY ROUTINES
19.1. CONVERSION AIDS
19.1,1. UNIVAC 1107 TO UNIVAC 1108
19.2. OUTPUT EDITING ROUTINE
19.2.1. ORGANIZATION
19.2.2. THE EDITING FUNCTIONS
19.2.2.1.
EXAMPLE OF EDITING FUNCTIONS
19.2.3. THE OUTPUT FUNCTIONS
19.2.4. THE MODAL FUNCTIONS
19.2.5. THE CONTROL FUNCTIONS
19.2.6. EXAMPLES
APPENDIX A--DIAGNOSTIC MESSAGES
APPENDIX B--ERROR CODES

12

Contents 1
pAGE:

SECTION:

18... 15
18-16
18-16
18-18
18-18
18-19
18-19
18-19
18 ... 20
18-20
18-20
18-21
18-22
18-22
18-22
18-22
18-23
18"",23
19-1 to 19-6

19-1
19-1
19-1
19-1
19-3
19-3
19-4
19-4
19-5
19-6
A-1 to A-1
. B-1

to

B-7

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

1

Introduction
SECTION:

INmOUUCTION
THIS DOCUMENT CONTAINS A DESCRIPTION OF THE EXECUTIVE COMPONENT OF THE OPERATING
SYSTEM FOR THE UNIVAC 1108 COMPUTER AND TAKES THE FORM OF A PROGRAMMERS REFERENCE
MANUAL (PRM). THE EXECUTIVE IS DESIGNED TO OPERATE AS A MASTER CONTROL PROGRAM WHICH
ESTA~LISHES THE EFFICIENT MULTI-PROGRAMMING ENVIRONMENT NEEDED'FOR UTILIZING THE FULL
CAPA~ILITIES OF THE UNIVAC 1108 MULTI.PROCESSOR SYSTEM.
THIS MANUAL INCLUDES DETAILS
OF UTILIZATION PKOCEDURES AND FUNCTIONAL CAPABILITIES BUT DOES NOT IN ALL CASES
PKES~NT THE DETAILED PROGRAMMING LOGIC WHICH MAKES POSSIBLE THOSE PROCEDURES AND
CAPABILITIES.
TH~
VEKSION OF THE EXECUTIVE SYSTEM DESCRIBED IS FOR THE UNIT PROCESSOR
CONFIGUKATION. THE INT~RFACE OF THE USER TO THE EXEC IS THAT SHOWN, THE SAME
INTEKFACE WILL BE USED IN THE MULTI-PROCESSING VERSION WITH ADDITIONS MADE FOR
CONTKOL AND ,USE OF NEW FEATURES AVAILABLE ONLy IN THE MULTI-PROCESSOR CONFIGURATION,
ALL SYSTEM SHIPMENTS WILL INCLUDE A 'SYSTEM MEMORANDUM' WHICH DETAILS THE
CdAKACTERISTICS OF THE CURRENT SYSTEM. THE MEMOS WILL POINT OUT THE VARIOUS
AUUI1IONS OR ENHANCEMENTS MADE AS THE SYSTEM IS UPDATED,

INCLUDED IN THIS MANUAL ARE SECTIONS ESTABLISHING THE OPERATIONAL REQUIREMENT FOR
THE EXECUTIVE SYSTEM, EXPLAINING CERTAIN BASIC CONCEPTS NECESSARY FOR EXECUTIVE
S~STEM OPERATIONS--IN THE REAL-TIME, BATCH AND DEMAND (OR 'CONVERSATIONAL') MODES,
AND OUTLINING THE ORGANIZATION OF THE SYSTEM. THESE GENERALIZED INTRODUCTORY
SECTIONS ARE FOLLOWED BY MOKE DETAILED EXPLANATIONS OF THE EXECUTIVE CONTROL
LANGUAGE, BATCH-PKOCESSING OPERATIONS, DEMAND-PROCESSING OPERATIONS, REAL-TIME
PKOC~SSING OPERATI,ONS, AND THE PROCESSING SUPERVISOR.
AFTER THIS CLARIFICATION OF
THE MAJOK SYSTEM COMPONENTS AND OPERATIONS, SECTIONS ARE PRESENTED ON OTHER
COMPONENTS OF THE 1108 EXECUTIVE SYSTEM,

PAGE:

~,

u

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

c
1.

EXEtUTIVE SYSTEM DESIGN CRITERIA

1.1.

OPERATIONAL CAPABILITIES
TO TAKE MAXIMUM ADVANTAGE OF THE SPEED AND HARDWARE CAPABILITIES OF THE UNIVAC

1108 COMPUTER AND TO MAKE EFFECTIVE USE OF A GIVEN HARDWARE CONFIGURATION, A COMPLEX

INTERNAL OPERATING ENVIRONMENT HAS BEEN CREATED.

THIS ENVIRONMENT ALLOWS FOR THE CONCURRENT OPERATION OF MANY PROGRAMS' IT ALLOWS
THE SYSTEM TO REACT IMMEDIATELY TO THE INQUIRIES, REQUESTS, AND DEMANDS OF MANY
DIFFERENT USERS AT LOCAL AND REMOTE STATIONS; IT ALLOWS FOR THE STRINGENT DEMANDS OF
REAL-TIME APPLICATIONS; IT IS ABLE TO STORE, FILE, RETRIEVE AND PROTECT LARGE BLOCKS
OF DATA; AND IT MAKES OPTIMUM USE OF ALL AVAILABLE HARDWARE FACILITIES, WHILE
MINIMIZING ~OB TURNAROUND TIME.
ONLY THROUGH CENTRAL CONTROL OF-ALL ACTIVITIES OF THE UNIVAC 1108 CAN THIS
ENVIRONMENT OF THE COMBINED HARDWARE AND SOFTwARE SYSTEMS BE FULLY ESTABLISHED AND
MAINTAINED TO SATISFY THE REQUIREMENTS OF ALL APPLICATIONS. THIS RESPONSIBILITY FOR
EFFICIENT, FLEXIBLE, CENTRALIZED CONTROL IS BORNE BY THE EXEC. THE EXEC CONTROLS AND
COORDINATES THE FUNCTIONS OF THIS COMPLEX INTERNAL ENVIRONMENT AND, BY PRESENTING A
RELATIVELY SIMPLE INTERFACE TO THE PROGRAMMER, ALLOWS HIM TO USE THE SYSTEM EASILY
WHILE RELIEVING HIM OF CONCERN FOR THE INTERNAL INTERACTION BETWEEN HIS PROGRAM AND
OTHER CO-EXISTENT PROGRAMS.
1.2.

EXEC RELATION TO OTHER SYSTEM COMPONENTS

THE UNIvAC 1108 EXECUTIVE SYSTEM INCLUDES A COMPLETE SET OF SOURCE-LANGUAGE
PROCESSORS INCLUUING FORTRAN V, COBOL, ALGOL AND THE ASSEMBLER. THE OPERATION OF ALL
OF THESE PROCESSORS IS CONTROLLED BY THE EXEC FOR THE USER OF THE SYSTEM. BY THE
EXECUTIVE'S ASSUMPTION OF THE RESPONSIBILITY FOR: 1) CALLING IN PROCESSORS AS
REQUIRED, 2) PROVIDING INPUTS TO THE PROCESSORS. 3) STORAGE AND MAINTENANCE OF THE
OUTPUTS OF THE PROCESSO~S, AND 4) THE INTEGRATION OF ACTIVITIES INVOLVING SEQUENCES
OF P~OCESSOR CALLS, A PROCESSOR'S OPERATION CAN BE CONFINED TO THE ACTUAL PROCESSING
INVOLVED IN A SINGLE ACTIVITY. THE EXECUTIVE SYSTEM WILL TAKE CARE OF ALL OTHER
FUNCTIONS.
OTHER COMPONENTS O~ THE 1108 SOFTWARE SYSTEM SUCH AS SORT/MERGE, APT, PERT/COST,
AND LP (LINEAR PROGRAMMING) INTERFACE WITH THE EXECUTIVE SYSTEM IN A SIMILAR MANNER.
1.3.

FUNCTIONAL

1

1
SECTION:

O~~ECTIVES

THE PRIMARY OB~ECTIVES IN THE DESIGN OF THE 1108 EXECUTIVE SYSTEM ARE AS FOLLOWS:
1.TO OPTIMIZE MACHINE EACILITIES USAGE, AND AT THE SAME TIME
OPTIMIZE INTERACTION FOR ALL USERS BY THE USE OF
MUL TI-PROGRAfMJIING/MUL Tl-PROCESSING TECHNIQUES.
2.TO MAKE AVAILABLE TO REMOTE USERS THE COMPLETE FACILITIES OF
THE 1108 SYSTEM.
_
3.TO PROVIDE AN EXECUTIVE CONTROL LANGUAGE WHOSE STRUCTURE WILL
ALLOW SIMPLE PROGRAMS TO HAVE A SIMPLE MEANS OF EXPRESSING THEIR REQUIREMENTS.
4.TO PROVIDE THE FLEXIBILITY TO EXPRESS A COMPLEX ENVIRONMENT
FOR COMPLEX PROGRAMS.
5.TO PROVIDE A BROAD AND EASILY-USED SPECTRUM OF PROGRAM CONSTRUCTION, rJlANIPULATION,AND CHECKOUT AIDS, INCLUpING THE PERMAI'-IENT STORAGE OF PROGRAM ELEMENTS ON RANDOM-ACCESS DEVICES.
6.TO ~ROVIDE FOR TASKS TO BE EXECUTED IN EITHER BATCH, DEMAND,

PAGE:

UNIVAC 1108 OPERATING

EXEC. B

SYSTEM

PROGRAMMERS REFERENCE

1
SECTION:

2
PAGE:

OR REAL-TIME MODE.
7.TO PROVIDE A SIMPLE AND FLEXIBLE MEANS OF COMPLETE SOFTWARE
SYSTEM GENERATION AND MAINTENANCE AT THE INDIVIDUAL
INSTALLATION.
S.TO PROVIDE SYSTEM INVULNERABILITy TO PROGRAMMING ERROR AND,
AS FAR AS 1& REASONABLE, HARDWARE ERRORS.
9.TO PROVIDE THE SIMPLEST POSSIBLE OPERATIONAL CHARACTERISTICS CONSISTENT WITH FULL UTILIZATION OF THE CAPABILITES
OF THE SYSTEM.
1.4,

RANGE OF EXECUTIVE SYSTEM CAPABILITIES

THE TECHNICAL CAPABILITIES OF THE UNIVAC 11ns EXECUTIVE SYSTEM SPAN A BROAD
SPEC1RUM OF DATA PROCESSING ACTIVITIES, ITS DESIGN IS SUCH THAT NO PENALTIES OF
II~E!-=r ICIENCY AHE IMPOSED UPON ONE OF THESE ACTIVITIES BY THE SUPPORT PROVIDED FOR THE
OTHEK ACTIVITIES, AN INSTALLATION NOT INTERESTED IN UTILIZATION OF THE FULL SPECTRUM
MAY SPECIFY CAPABILITIES TO BE ELIMINATED AT SYSTEM GENERATION TIME.
1.4.1.

BATCH PROCESSING

FOKEMOST AMONG SYSTEM CAPABILITIES IS THE SUPPORT PROVIDED FOR BATCH PROCESSING.
DESIGN EMPHASIS HAS BEEN PLACED UPON THE ACHIEVEMENT OF EASE OF RUN PREPARATION AND
SUBMISSION, MINIMIZATION OF .JOB TURN-AROUND TIfvlE.AND MINIMIZATION OF OPERATOR
INTERVENTION AND DECISION REQUIREMENTS. RUN·SUBMISSIONMAY COME FROM MANY SOURCES,
R~MOTE AND CENTRAL.
THESE VARIOUS INPUTS THROUGH THE EXEC'S USE AND CONTROL OF
~FFICIENT MULTI-PROGRAMMING TECHNIQUES. MAY UNDERGO WHAT IS ESSENTIALLY SIMULTANEOUS
INPUT, PROCESSHIG, AND OUTPUT. THUS. IN A DEr"lANDING ENVIRONMENT, THE FULL
CAPABILITIES OF THE 110S CAN BE UTILIZED EFFICIENTLY.
..
1.4.2.

DEMAND PROCESSING

THE EXEC PROVIDES SIMULTANEOUS USE OF THEUOS BY MANY USERS AT REMOTE CONSOLES TO
OPTIMIZE THE USER/SYSTEM INTERACTION RATE. EACH USER SHARES CONTROL OF THE
COMPUTATIONAL FACILITIES AND HAS THE FULL CAPABILITY OF THE 1108 CONFIGURATION AT HIS
DISPOSAL..
THE LJEMAND MODE OF PROCESSING IS .INITIATED AND CONTROLLED BY THE EXECUTIVE CONTROL
LANGUAGE. COMf-1ANDS ARE INPUT VIA THE USER'S REMOTE CONSOLE ON A CONVERSATIONAL
BASIS. THAT IS. AN IMMEDIATE SYSTEM RESPONSE WILL BE APPARENT.
PROVISIONS ARE MADE FOR: 1) DIALED COMMUNICATION CONNECTION IN ADDITION TO
L.EASED LINES AND REMOTE CONSOLES ON SITE:; 2) PAPER TAPE INPUT ALLOWING PRE-TYPED
COMMAND PROGRAMS WITH DATA FOR HIGH EFFICIENCy COMMUNICATION TRANSMISSION' 3) USER
COl'vlMUNICATlON wITH THE COMPUTER CENTER. OTHER CONSOLES AND THE EXEC ITSELF.
1.4.3.

REAL-TIME PROCESSING

A BASIC RESPONSIBILITY OF THE EXEC IS TO ASSIST REAL-TIME COMMUNICATIONS(RT/C)
PROGRAMS WITH EXEC FUNCTIONS PROVIDED TO ALLOW RT/C PROGRAMS TO APPROPRIATELY
INFLUENCE THE EXEC AND THE MULTI-PROGRAM BACKGROUND, NO ATTEMPT IS MADE TO
GENERALIZE THE CONTROL REQUIRED IN EACH RTIC PROGRAM IN RECOGNITION OF THE SPECIFIC
TAILORING OF A RT/C PROGRAM TO 80TH THE HARDWARE CONFIGURATION AND THE PROCESS·
CONTROLLED.
EXEC IS
MECHANISMS
EXECUTIONI
BECAUSE OF

SENSITIVE TO THE NATURE OF ~T/C PROCESSING AND PROVIDES APPROPRIATE
FOR: LOCKOUT PROTECTION FROM SIMULTANEOUS RECORD ACCESS DURING PROGRAM
PKIORITY SENSITIVITYI PROTECTION TO RT/C PROGRAMS FROM INTERFERENCE
PERIPHERAL ACCESS OF BACKGROUND PROGRAMS (SEARCH FUNCTIONS,ETC.).

INTERFACE WITH NON-STANDARD PERIPHERALS CAN BE AT THE HARDWARE LEVEL (I/O COMMANDS
AND INTERRUPTS). EXEC AWARENESS OF INDIVIDUAL TRANSMISSION LINES PROVIDES FOR

------_._----- - - - - - - - - - - - - - - - - - -

-------,-----------._--

UNIVAC 1108 OPERATING

UP-4144

Rev.1

EXEC B

SYSTEM

PROGRAMMERS

REFERENCE

ADEQUATE RESPONSE AND FLEXIBILITY.
1.5.

PROGRAM PROTECTION

THE MULTIPROGRAMMING CAPABILITIES OF THE EXECUTIVE SYSTEM IMPLIES THAT MANy
PROGRAMS MAY BE RESIDING IN MAIN STORAGE AT THE SAME TIME. SUCH PROGRAMS
MAY BE REAL-TIME RUNS, PRODUCTION RUNS, CLASSIFIED RUNS, OR SIMPLE DEBUGGING RUNS.
INFRINGEMENT OF PRIVACY IN SUCH A MIXTURE IS HIGHLY PROBABLE ESPECIALLY IN CASES
WHERE DEBUGGING RUNS ARE EXECUTING. THE KNOWLEDGE OR IGNORANCE OF AN INVASION MAY
RANGE FROM LITTLE OR NO CONCERN FOR SOME RUNS TO GREAT CONCERN FOR CLASSIFIED OR
REALTIME RUNS.

~~RELATED

TO COMBAT THIS INVASION, INTENTIONAL OR UNINTENTIONAL, THE EXECUTIVE SYSTEM HAS
UNIQUE FEATURES THAT AUTOMATICALLY GUARANTEE ABSOLUTE PROTECTION FOR EACH PROGRAM,
THE PROTECTION GUARDS AGAINST TWO FORMS OF INVASION, DIRECT AND INDIRECT.
DIRECT PROTECTION SAFEGUARDS ALL PROGRAMS IN MAIN STORAGE FROM AN ACTIVE PROGRAM
ThAT MAY ATTEMPT TO READ, WRITE, OR ~UMP INTO ANOTHER PROGRAM AREA. THIS SAFEGUARD
IS EFFECTED BY 'LOCKING OUT' ANY AREA OF MAIN STORAGE THAT IS NOT ASSIGNED TO THE
PRESENTLY ACTIVE PROGRAM OR, IN EFFECT, 'LOCKING IN' THE ACTIVE PROGRAM. ANY ATTEMPT
TO PERFORM ANY OF THE ABOVE FUNCTIONS IS IMMEDIATELY REPORTED TO THE EXECUTIVE
SYSTEM.
INDIRECT PROTECTION IS REALIZED BY RESERVING CERTAIN CONTROL FUNCTIONS FOR THE
EXCLUSIVE USE OF THE EXECUTIVE SYSTEM. THESE FUNCTIONS ARE OF THE TYPE THAT CoULD
CAUSE A SYSTEM MALFUNCTION AND, IN TURN, A PROGRAM MALFUNCTION IF ERRONEOUSLY USED.
TH~ EXECUTIVE SY5TEM WILL PROHIBIT THE USE OF THESE FUNCTIONS.
IN BOTH FORMS OF PROTECTION, THE EXECUTIVE SYSTEM IS, IN REALITY, GUARANTEEING
ITS OWN SAFETY FROM ABUSES THAT MAY PROVE CATASTROPHIC TO THE SYSTEM.
1.6.

MASS STORAGE UTlLIZA"TION TECHNIQUES

THE UNIVAC 1108 EXECUTIVE SYSTEM IS DESIGNED TO PRoVIDE INSTALLATIONS WITH AN
EFFECTIVE AND EFFICIENT UTILIZATION OF THE MASS STORAGE DEVICES AVAILABLE WITH THE
1108. THE RESULT IS AN UNPRECEDENTED ABILITY TO RELIEVE OPERATORS AND PROGRAMMERS OF
RESPONSIBILITIES IN MAINTAINING AND PHYSICALLy HANDLING CARDS, MAGNETIC TAPES, ETC.,
THUS ELIMINATING MANY OF T~E ERRORS WHICH PREVIOUSLY ACCOMPANIED THE USE OF
LARGE-SCALE SOFTWARE SYSTEMS. AT THE SAME TIME, THE OVERALL EFFICIENCY OF OPERATION
IS CONSIDERABLY IMPROVED.
PROVISIONS ARE MADE FOR THE MAINTENANCE OF PERMANENT DATA FILES AND PROGRAM FILES
ON THE MASS STORAGE DEVICES, WITH FULL FACILITIES FOR MODIFICATION AND MANIPULATION
OF THESE FILES. SECURITY MEASURES ARE INVOKED BY THE EXECUTIVE SYSTEM TO INSURE THAT
FILES ARE NOT SUB~ECTED TO UNAUTHORIZED USE. AS UNUSED MASS STORAGE SPACE APPROACHES
EXHAUSTION, PROVISIONS ARE ALSO MADE WITHIN THE EXECUTIVE SYSTEM FOR AUTOMATIC
"
RELOCATION OF FILES OF LOw USAGE-FREQUENCY TO MAGNETIC TAPE. WHEN THE USE OF FILES
RELOCATED IN SUCH A MANNER IS REQUESTED, THEY ARE RETRIEVED AND RESTORED, UNDER
CUNTROL OF THE EXECUTIVE SYSTEM, WITH NO INCOINENIENCE TO THE USER. FOR THE MOST
PART, DYNM'iIC ASSIGNMENT OF MASS STORAGE SPACE IS AVAILABLE TO THE USER VIA THE
EXECUTIVE SYSTEM. TO FACILITATE EFFICIENT UTILIZATION OF AVAILABLE FACILITIES, THE
USER IS ALSO ABLE TO RETURN PORTIONS OF MASS STORAGE TO GENERAL USE AS HE FINISHES
WITH THEM.
1.7.

PROGRAM FILES

3

1
SECTION:

PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

1
SECTION:

PAGE:

o
1.7.1.

~ASIC

CONCEPT

THE CONCEPT OF A PROGRAM FILE IS FUNDAMENTAL TO AN UNDERSTANDING OF THE 1108
SOFTWARE SYSTEM. A PROGRAM FILE IS ESSENTIALLY A NAMED SET OF ELEMENTS. THE FILE
NAME IS THE PRIME IDENTIFIER FOR THE SET OF ELEMENTS. TO IDENTIFY AND LOCATE THE
ELEMENTS WITHIN A PROGRAM FILE. A TABLE OF CONTENTS IS CREATED, AND MAINTAINED WITHIN
THE PROGRAM FILE BY THE SYSTEM,
1.7.2.

PROGRAM FILE ELEMENTS

WlTHIN THE TABLE OF CONTENTS. EACH ELEMENT WITHIN THE PROGRAM FILE IS UNIQUELY
IUENTIFIED BY THE FOLLOWING FOUR PARAMETERS:
1. ELEMENT TYPE
2. ELEMENT r~AME
3. ELEMENT VERSION
4. ELEMENT CYCLE

ALSO INCLU0ED ARE VARIOUS OTHER PARAMETERS SUCH AS THE DA.TE OF ELEMENT CREATION
AND THE CURRENT RELATIVE LOCATION OF THE ELEMENT ON MASS STORAGE.
THE ELEMENTS CONTAINED WITHIN A PROGRAM FILE ARE OF THE FOLLOWING THREE TYPES:
1. SOURCE LANGUAGE. OR MORE GENERALLY, VARIABLE LENGTH

DATA IMAGES'
2. RELOCATAULE BINARY
3. ABSOLUTE BINARY

TYPICAL SOURCE-LANGUAGE ELEMENTS ARE THE FOLLOWING:
1~ FORTRAN SOURCE PROGRAM
2. COBOL SOURCE PROGRAM
3. ASSEMBLER SOURCE PROGRAM
4. COLLECTOR SOURCE ELEMENT

ANY OF THESE ELEMENTS MAY BE INTRODUCED INTO A PROGRAM FILE OR MANIPULATED WITH A
FILE BY THE USE OF THE APPROPRIATE PROCESSOR (FORTRAN, COBOL, ETC.1 OR BY CERTAIN
UTILITY ROUTWE:..S.
THE FOLLOWING ELEMENTS MAY BE THOUGHT OF AS BEING SPECIAL-CASE SOURCE-LANGUAGE
ELEMENTS:
1. ASSEMBLER PROCEDURE ELEMENTS
2. COBOL PROCEUURE ELEMENTS
3. FORTRAN PROCEUURE ELEMENTS

THESE ELEMENTS ARE AVAILABCE TO THE LANGUAGE PROCESSORS ESSENTIALLY AS
SOURCE-LANGUAGE LIl:lRARY ELEMENTS. SPECIAL ELEMENTS ARE REQUIRED BY THE SYSTEM TO
fACILITATE THE RETRIEVAL OF SOURCE LANGUAGE LIBRARY ELEMENTS AT COMPILATION OR
ASSEMBLY TIME. HO~EVER, THESE ELEMENTS ARE CREATED AND MAINTAINED BY THE SYSTEM AND
REQUIRE NO CONCERN ON THE PART OF THE USER.
IN AuOITIOI~ TO THE ABOVE SOURCE ELEMENTS, SETS OF EXECUTIVE CONTROL STATEMENTS MAY
BE ENTEREU AS SOURCE ELEMENTS. THESE ELEMENTS MAY BE CALLED BY THE QSTART OR QADD
S1 ATEfl.1ENTS.
RELOCATABLE ELEMENTS ARE TrlE BINARy OUTPUT Of THE pROCESSORS SUCH AS FORTRAN,
CUBOL, THE ASSE~HLER, AND ONE SPECIAL USE OF THE COLLECTOR. ABSOLUTE ELEMENTS ARE
PLACED IN A PROGRAM FILE BY THE COLLECTOR.
1.7.3.

ELEMENT NAME

AN~

VERSION

EACH ELEMENT WITHIN A PROGRAM FILE IS GIVEN A NAME SPECIFIED BY THE USER. THIS
IS REFERRll) TO SIMPLY AS THE ELEMENT NAME. TO DISTINGUISH BETWEEN ELEMENTS OF

~AME

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

1
SECTION:

THE SAME NAME AND TYPE, A USER MAY SPECIFY A SUBNAME FOR AN ELEMENT, AND THIS SUBNAME
IS CALLED THE ELEMENT VERSION.
HOTH AN ELEMENT NAME AND AN ELEMENT VERSIOi~ MAY BE FROM ONE TO TWELVE CHARACTERS
IN LENGTH, AND THESE TWO P~RAMETERS TOGETHER MUST UNIQUELY IDENTIFY ONE ELEMENT AMONG
ALL ELEMENTS OF ANY PARTICULAR TYPE. ELEMENTS OF DIFFERENT TYPES (E.G., SOURCE
LANGUAGE VS. RELOCATABLE 8INARY)MAY, HOWEVER, HAVE THE SAME NAME AND VERSION. AN
ELEMENT NAME IS REQUIRED FOR ALL ELEMENTS wITHIN A PROGRAM FILE(A NAME IS SUPPLIED
AUTOMATICALLY ~Y T~iE EXEC IN MANY CASES); HOWEVER, THE SPECIFICATION OF AN ELEMENT
VERSION IS NOT REQUIRED.
1.7.4.

ELEMENT VERSIONS

RELOCATABLE ELEMENTS MAY BE FURTHER CLASSIFIED BY SPECIFYING A CLASS DESIGNATION
WHICH IS APPLIED TO THE VERSION NAME. THE PURPOSE OF THIS CLASSIFICATION IS THE
SELECTION OF ELEMENTS BASED ON PARAMETERS SUITED FOR THE PARTICULAR ALLOCATION TO BE
MADE. LETTERS WITHIN THE VERSION NAMES OF ELEMENTS ARE GIVEN MEANING 8Y THE
PROGRAMMER WHICH CAN THEN BE USED TO SELECT A PROPER CLASS OR CLASSES ACCORDING TO
THE NEED. EACH REQUIRED ELEMENT NEED NOT BE NAMED, BUT THE PROPER ELEMENT WILL BE
SELECTED BY ELIMINATION.
1.7.5.

'CYCLE' PARAMETEH

FOH DIFFERENTIATION AMONG SYMBOLIC ELEMENTS, AN INTEGER PARAMETER CALLED 'CYCLE'
IS ASSOCIATEU wITH EACH ELEMENT. THIS ALLOWS SEVERAL 'COPIES' OF THE SAME VERSION OF
AN ELEMENT TO BE RETAINED WITHIN A PROGRAM-FILE. EACH ITEM(IMAGE) OF A SYMBOLIC
~LEMENT HAS A CYCLE NUM~ER INDICATING TO WHICH CYCLE IT BELONGS, AND, IF DELETED, A
U~LETE-CYCLE NUMBER TO INDICATE IN WHICH CYCLE THIS ITEM WAS DELETED.
WHEN A
SYMBOLIC ELEMEiJT IS UPDATED, THE UPDATE ITEMS ARE INSERTED WHERE THEY BELONG IN THE
ELEMENT AND GIVEN A CYCLE NUMBER ONE GREATER THAN THE LAST CYCLE OF THE ELEMENT. ANY
PHEVIOUS CYCLE ITE~S THAT HAVE BEEN DELETED BY THIS UPDATE ARE MARKED SO. THE USER
MAY MAKE REFERENCES BY CYCLE NUMBER. THIS GIVES THE SAME EFFECT AS THOUGH SEVERAL
DIFFERENT COPIES OF THE ELEMENT WERE MAINTAINED. THE USER MAY SET THE NUMBER OF
UPDATE-CYCLES TO BE RETAINED AT ANY LEVEL HE DESIRES; HOWEVER, HE NEED SET THAT
NUMBER ONLY IF HE DESIRES TO CHANGE IT FROM THE STANDARD SYSTEM ASSUMPTION. THIS
STANDARU VALUE MAY BE ALTERED AT SYSTEM GENERATION TIME.
IN SPECIFYING A SYMBOLIC ELEMENT FOR COMPILATION OR ASSEMBLY, THE USER MAY
REFERENCE A SPECIFIC UPDATE FROM A SEQUENCE OF RETAINED UPDATES BY SPECIFYING THE
PKOPEH UPDATE CYCLE NUMBER AS PART OF THE EXECUTIVE CONTR6L STATEMENT CALLING FOR THE
CUMPILER OR ASSEM~LER. IN COMPILATIO~, THE UPDATE ENTRY WILL BE COMBINED WITH THE
ELEMENr I~ ITS COMPLETE STATE THEREBY CREATING A COMPLETt ELEMENT AS OF THAT CYCLE.
AS SO(JIJ AS THE NUMBER OF UPfJATES RETAINED FOR AN ELEMENT EXCEEDS THE SPECIFIED
MAXIMUM, TliE UPDATE OF THE LOWEST CYCLE NUMBEH (THE ORIGINAL, COMPLETE ELEMENT) IS
COMBINED ~ITH THE UPDATE NEXT LOWEST IN CYCLE NUMBERIIN EFFECT, THE OLDEST ENTRY IS
DISCARDED, AND rHE fJEXT-OLDEST, IN ITS COMPLETED FORM, BECOMES THE OLDEST TO MAKE
ROOM FUR TliE LATE~T CYCLE ENTHY. THESE CORRECTIONS THUS BECOME INCORPORATED
PERMANENTLY IN10 THE BASIC ELEMENTS AND CAN ONLY BE REMOVED BY ENTERING NEW
CORRECTION STATEMENTS.
THIS TECHNIGUE OF HANDLING

SYM~OLIC

ELEMENTS OFFERS TWO DISTINCT ADVANTAGES;

(l)THE USEH I~ ALLOWEU TO KEEP MANY DIFFERING COPIES OF THE SAME ELEMENT IN A
PROGRAM FILE ~HILE REQUIRING LITTLE ADDITIONAL STORAGE OVER THAT NEEDED FOR A SINGLE
COPY.
(2)THE USER IS A~LE TO REFER EASILy TO EARUER COPIES OF A SPECIFIC- ELEMENT
WITtiUUT HAVING TO PREPARE CORRECTIONS DELETING PREVIOUSLY INPUT CORRECTIONS.
H0i'1EVEH, If-' A SET OF COHRECTIONS ARE APPLIED TO ANY CYCLE EXCEPT THE LATEST AND THE
UPUATEO CYCLE IS TO BE RETAINED, ALL CYCLES THAT PREVIOUSLY FOLLOWED THE CYCLE TO BE
UPUATEU WILL 8E DELETED. THE NEW CYCLE NUMBER WILL BE THE UPDATED CYCLE NUMBER PLUS
OI'
Tl::RMINAL
MOOULE
CONTROLLER

ANY SWITCHED
NETWORK OR LEASED
LINE EXCEPT
BROADBAND CONFORM_
ING TO EIA STANDARDS FOR USE WITH
RELAY INTERFACE
OR APPROPRIATE
DATA SET (MODEM)

USER CONTROLLED
DEVIcES SUCH AS
TELETYPES, KEYBOARDS AND
PRINTERS, CRT
DISPLAYS, PAPER
TAPE READERS AND
REPERFORATORS VIA
SIMPLEX, HALF
DuPLEX OR FULL
DUPLEX CIRCUITS

WORD TERMINAL
SYNCHRONOUS(WTS).

SAME AS CTS.

REMOTE 1004 II
AND 1004 I II

FOLLOWING ARE THREE CONFIGURATORS WHICH ILLUSTRATE THE HARDWARE SUPPORTED BY THE
1004 SYSTEMS. FIGURE 2.1 SHOWS SHOWS THE CONFIGURATION FOR THE ON-SITE 1004
(bOARD U1); FIGURE 2.2 SHOWS THE COMPRESSED REMOTE 1004 (BOARD #2); FIGURE 2.3 SHOWS
THE NON-COMPRESSED REMOTE 1004 (BOARD #3).
THR~E

5

2
SECTION:

PAGE:

i UP-4144

UNIVAC 1108 OPERATING

I Rev. 1

EXEC B

.

SYSTEM

PROGRAMMERS REFERENCE

2
SECTION:

6
PAGE:

o
100~ CONFIGURATION
BOARD #1 (ON-SITE)

ON-LINE, ON-SITE, 80 COLUMN ONLY

1108 CHANNEL

IOC CHANNEL (MP ONLY)

:---------------:-------------------:
---------------:-------------------:
:
:- REQUIRED -:
1-02
-:
EXTERNAL
:-100~ 1-04,-06,-07
11-02
:---: INTERRUPT
:---: 1004 11-04,-06,-07
1004 111-02 -:
FEATURE, AND
:-100~ 111-04,-06,-07
ILLEGAL CARD
CODE DETECT
FEATURE
-OPTIONS.OPTIONS80COl..UMN PUNCH
-:
80 COLUMN PUNCH
PAPER TAPE READ
PAPER TAPE PUNCH
CODE IMAGE READ
CODE IMAGE PUNCH
100~
100~

..-

ON-SITE FUNCTIONS
READ 80 COLUMN CARDS • • • • • • • • •
PUNCH 80 COI..UMN CARDS • • • • • • • •
PRINT • • • • • • • • • • • • • • • •
READ COUE IMAGE CARDS • • • • • • • •
PUNCH CODE IMAGE CARDS • • • • • • • •
READ PAPE~ TAPE (4 LEVELS) • • • • • •
PUNCH PAPER TAPE (4 LEVELS) • • • • •

FIGURE 2.1

ALL MODELS SHOWN
AI..L MODELS SHOWN
ALL MODELS SHOWN
-04,-06,-07 ONLY
-04,-06,-07 ONLY
-04,-06,-07 ONLY
-04,-06,-07 ONLY

~--~---

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

1004

BOARD

SYSTEM
SECTION:

CONFIGURATION
~2 (REMOTE COMPRESSED)

REMOTE, VOICE-GRADE LINES. DlT-l,

80

COLUMN ONLY

cTr.,c

··

HIGH SPEED CTM
201 /·100Er.,

·

2400 BPS

Llf~E

..

201

2400 BPS LINE

2400 BPS lINE

201

MOOEr~

OLT-1

1004 1-06,-07
1004 11-06,-07
1004 I Il-06,-07

-OPTlONS80 COLUMN PUNCH

(,

,-,

,.//

MODEM

201 r-l00EM

:-----------------:-------------------:

7

2

PROGRAMMERS REFERENCE

PAGE:

....

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC· B

PROGRAMMERS

REFERENCE

2
SECTION:

8
PAGE:

o
ROEMOTE FUNCTIONS (BOARD #2)
READ BO COLUMN CARDS. • • • • • • • • ALL MODELS SHOWN
PUNCH 80 COLUMN CARDS • • • • • • • • ALL MODELS SHOWN
PRINT • • • • • • • • • • • • • • • • ALL MODELS SHOWN
*NOTE* THIS BOARD READS 80 COLUMN CARDS, REMOVES BLANKS FROM
THE IMAGE THROUGH COMPRESSION, BUILDS A 330 CHARACTER
BUFFER AND TRANSMITS IT. THE BOARD ALSO ACCEPTS 330
CHARACTER COMPRESSED OUTPUT BUFFERS, DECOMPRESSES AND
PRINTS OR PUNCHES THE DATA.
*NOTE* WLIH MODIFICATION BOARD #2 COULD BE USED WITH TELPAK-A
LINES AND A DLT-IB. HOWEVER, THIS SET-UP WOULD NOT
PROVIDE FULL 1004 SPEEDS.

FIGURE 2.2 CONTINUED

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
REFERENCE

1004 CONFIGURATION

bOAKD

~3

(REMOTE NON-COMPRESSED)

CTS

WTS

301 MODEM

301 MODEM

TELPAK-A
LINE

TELPAK-A
LINE

---------:---------:
301 MODEM

DLT-1B

1004 1-06,-07
1004 II-06,-07
1004 111-06,-07

-OPTIONS-

80 COLUMN PUNCH

CODE IMAGE
CODE IMAGE
PAPER TAPE
PAPER TAPE

FIGURE 2.3

READ
PUNCH
READ
PUNCH

9

2
SECTION:

PAGE:

UP-4144

Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS

REMOTE FUNCTIONS (BOARD n3)
READ 80 COLUMN CARDS. • • • • • • • •
PUNCH 8U COLUMN CARDS • • • • • • • •
PRINT • • • • • • • • • • • • • • • •
READ CODE IMAGE CARDS • • • • • • • •
PUNCH CODE IMAGE CARDS • • • • • • • •
READ PAPER TAPE (4 LEVELS) • • • • • •
PUNCH PAPER TAPE (4 LEVELS) • • • • •

10

2

REFERENCE

SECTION: '

PAGE:

ALL MODELS SHOWN
ALL MODELS SHOWN
ALL MODELS SHOWN
-06,-07 ONLY
-06,-07 ONLY
-06,-07 ONLY
-06,-07 ONLY

*NOTE* WITH SLIGHT MODIFICATION BOARD #3 COULD BE USED WITH
THE SLOW-SPEED OPTION ON DLT-1S AND VOICE-GRADE LINES.
THE SPEED OF THE 1004 WOULD BE GREATLY REDUCED.

FIGURE 2.3 CONTINUED

o

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

3.

SYSTEM

PROGRAMMERS REFERENCE

1

3
PAGE:

SECTION:

BASIC CONCEPTS OF THE UNIVAC 1108 EXECUTIVE SYSTEM

DEFINITIONS

3.1.

CERTAIN TERMS ARE RE~ERRED TO IN THIS MANUAL WITH THE ASSUMPTION THAT THE READER
IS ACQUAINTED WITH THEIH MEANING. THE FOLLOWING DEFINITIONS ARE FOR THE CONVENIENCE
Of- n1E HEADEH.
3.1.1.

ACTIVITY

A DIVISION OF A PROGRAM WHICH MAY BE EXECUTED INDEPENDENT OF OTHER PORTIONS OF THE
PROGRAM. IT IS USUALLY CONSIDERED PART OF A TASK.
3.1.2.

ACTIVITY REGISTRATION

THE ACT OF REGISTERING WITH THE EXECUTIVE SYSTEM AN ACTIVITY WHICH CAN BE EXECUTED
ASYNCHRUNOUSLY WITH OTHER PARTS OF A PROGRAM. FORKING.
3.1.3.

BATCH PROCESSING

A MODE OF OPEHATION WHERE SEVERAL RUNS ARE GROUPED PRIOR TO PROCESSING.
TRANSITION FRON RUN TO RUN IS EFFECTED BY THE EXECUTIVE SYSTEM.

THE DIVISION OF SYMBIONT DEFINED FILES. ALLOWS THOSE PORTIONS OF THE FILE TO BE
INDEPENDENTLY OF RUN COMPLETION. MAXIMUM USE OF AVAILABLE PRINTERS AND
PUNCHES IS ACHIEVEU IN THIS MANNER.
QUEU~D

3.1.5.

CENTRAL SITE

THE 110B COMPUTER AND ITS ATTACHED PERIPHERAL EQUIPMENT.
3.1.6.

COLLECTION

THE PROCESS 6Y WHICH ELEMENTS OF A PROGRAM ARE COLLECTED ~Y SATISFYING THE
EXTERNAL SYMBOLS OF THE INITIAL ELEMENT AND ALL REFERENCED ELEMENTS. THE RES~LTING
SIRUCTUHE JEFI~ES A PROGRAM TO BE ALLOCATED AND EXECUTED.
3.1.7.

COM~UNICAIION

DEVICE

AN INPUT OR OUTPUT D~VtCE WHICH OPERATES IN A REAL-TIME MODE. THE CENTRAL
UNIT MUST BE PREPARED TO RECEIVE IIJPUT AT ANY TIME OR THE INFORMATION
MAYBE LOST.
PROC~SSlNG

3.1.8.

UEMAND PROCESSING

THE 1'-1Ai'Ji'JER OF PROCESSING IN WHICH THE EXECUTIVE SYSTEM OR A PROCESSOR
SPONTANEOUSLY REACTS TO THE INPUTS FROM A REMOTE INQUIRY TERMINAL WHICH IS SENDING
MESSAGES AS REQUIRED. THIS IS ESSENTIALLY A DEMAND AND RESPONSE TYPE OF ACTIVITY.

fHE

THE BASIC COMPONENT OF A PROGRAM FILE USUALLY DEFINED AND MANIPULATED AS A
~ORM OF AN ELEMENT IS DEPENDENT UPON THE PROGRAM USING IT.

3.1.10.

UNIT~

EXECUTIVE CONTROL LANGUAGE

SPECIFICALLY FORMATTEU INPUT INFORMATION WliICHIS USED TO DIRECT THE ACTIVITY OF

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

3
SECTION:

2
PAGE:

THE EXECUTIVE SYSTEM.
3.1.11.

THE

FACI~ITIES

PERIPHERA~

UNITS, MAIN STORAGE, TAPE DRIVES, DRUM STORAGE, ETC.

AN ORGANIZED CO~LECTION OF DATA STORED IN SUCH A MANNER SO AS TO FACILITATE THE
RETRIEVAL OF EACH INDIVIDUAL DATUM.
3.1.13.

GRANULE

THE INCREMENTAL SIZE IN WHICH A STORAGE UNIT IS ASSIGNABLE.
3.1.14.

MULTI-PROGRAMMING

THE CON~URRENT EXECUTION OF SEVERAL PROGRAMS WHICH OCCUpy MAIN STORAGE.
ACCOMPLISHED BY SHARING THE ATTENTIONS OF THE CENTRAL PROCESSOR.
3.1.15.

THIS IS

PACKET

A CONTIGUOUS SET OF WORDS WHICH CONTAIN INFORMATION DESCRIBING AN INPUT/OUTPUT
OPERATION TO BE PERFORMED
3.1.16.

PROCESSOR CALL STATEMENTS

SPECIFICALLY FORMATTED INPUT INFORMATION WHICH IS USED TO DIRECT THE ACTIVITY OF A
SYSTEM PROCESSOR. A SU~SET OF THE EXECUTIVE CONTROL LANGUAGE.
3.1.17.

PROGRAM

A COL~ECTION OF INSTRUCTIONS, EXECUTION OF WHICH RESULTS IN PERFORMANCE' OF ONE OR
MORE LOGICAL FUN~TIONS. A PROGRAM IS THE SUB-DIVISION OF THE EXECUTABLE ASPECTS OF A

KUN.

3.1.18.

PROGRAM

~ILE

A FILE IfJ WHICH THE DATA ARE THE CONSTITUENTS OF A PROGRAM OR OF SEVERAL PROGRAMS.
TttIS DATA ~AY CONSIST OF PROGRAM ELEMENTS IN SYMBOLIC, RELOCATABLE BINARY, OR
AbSOLUTE BINARY FOR~. SPECIAL INFORMATION IN THE PROGRAM FILE IS USED TO AID THE
~YSTGl IN THt::: rv1ANIPULATlON OF THE PROGRAM CONSTITUENTS.
3.1.19.

REAL-TlME PROCESSING

AN OPERATING ENVIRONMENT IN WHICH THE RlSPONSE TO AN EXTERNAL STIMULI IS
SuFFICIENTLY FAST TO ACHIEVE A DESIRED OBJECTIVE. DEPENDING UPON, THE APPLICATION
TI1t::: RESPONSE TIME MAY VARY FROM SECONDS TO MICROSECONDS. GENERALLY, REAL-TIME
PkOCt:::SSlNG IS UNDER TilE INFLUENCE OF ASYNCHRONOUS INPUTS FROM ONE OR MORE DEVICES.
3.1.20.

RE-ENTRANT COOING

A SET O~ INSTRUCTIONS CODED IN SUCH A MANNER THAT THEY. MAY LOGICALLY PERFORM THE
SAME TASK ON DIFFERENT UATA SETS SIMULTANEOUSLY.
3.1.21.

REMOTE SITE

A COMMUt.JICATION~ TEHMINAL
IijFOH,'·'ATlOi~ FROl4 THE CENTRAL

wHICH IS CAPAllLE OF SENDING INFORMATION TO AND RECEIVING
PHOCE;SSOR VIA 50;"'E COMMON CARRIER OR TRANSMISSION

~CHEME.

A RUN r::; THE

SrAr~OARIJ Ur~IT

IN 'IIHICH WOkK IS ENTERED INTO THE OPERATING SYSTEM.

C,.)'·
,<

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
SECTION:

(
THIS CONSISTS OF A RUN COMMAND FOLLOWED BY ONE OR MORE CONTROL COMMANDS WHICH CAUSES
THE ORDERED EXECUTION OF PROCESSORS AND/OR WOKKER PROGRAMS.
3.1.23.

SIMULATED FASTRAND

DRUM SIMULATION OF FASTRAND WHICH ALLOWS EXECUTION OF A PROGRAM WITH FILES DESIGNED
FOR FAST RAND ALLOCATION ALLOCATED TO THE SECTION OF THE 'FLYING HEAD' DRUM STORAGE
DESIGNATED AS SIMULATED FASTRAND.
3.1.24.

SWAPPING

THE PROCESS OF STORING LOW PRIORITY OR SUSPENDED PROGRAMS ON SECONDARY STORAGE IN
ORDER TO ALLOW SPACE TO RETRIEVE ANOTHER PROGRAM INTO PRIMARY STORAGE FOR EXECUTION.~
3.1.25.

SYSTEMS PROCESSOR

A PROGRAM WHICH PERFORMS SPECIALIZED FUNCTIONS UNDER THE CONTROL OF THE EXECUTIVE
SYSn::rvl.

A LOGICAL STEP IN THE PROCESSING OF A RUN.
PkOCESSOR OR A USER PROGRAM.

3.2.1.

FOR EXAMPLE, EXECUTION OF A SYSTEM

PRIVILEGEU INSTRUCTIONS

SEVEKAL INSTRUCTIONS ARE RESERVED FOR THE EXECUTIVE SYSTEM USAGE·ONLY. IF ANy OF
fHE PRIVILEGED INSTRUCTIONS ARE EXECUTED BY A USER PROGRAM A GUARD MODE INTERRuPT
WILL OCCUR. THE ~ANDLING OF THE GUARD MODE INTERRUPT IS DESCRIBED IN DETAIL IN THE
SUPERVISOR SECTION (SECTION 7). THE PRIVILEGED INSTRUCTIONS ARE:
72 - 15
72 - 16
73 - 11+
73 - 15
73 - 16
75 (0-15)

LOAU PROCESSOR STATE REGISTER
LOAD STORAGE LIMITS REGISTER
INITIATE INTER-PROCESSOR INTERRUPT
SELECT INTERRUPT LOCATION
LOAu CHANNEL SELECT REGISTER
ALL I/O INSTRUCTIONS

THE INSTRUCTION, 'PREVENT ALL 1-0 INTERRUPTS AND JUMP, (72 13), IS NOT A PRIVILEGED
INSTRUCTION FOR THE UNIf PROCESSOR, BUT CAUTION SHOULD BE EXERCISED WHEN USING IT.
TH[ HARUWAKE ALLOWS INTERRUPTS TO BE LOCKED OUT FOR ONLY 100 MICROSECONDS WHILE IN
GUARU MODE. DATA TRANSFERS ASSUME TIME PRIORITY OVER INSTRUCTION EXECUTION,
TrlEREFORE, A GUARANTEE CAN NOT BE MADE ON THE NUMBER OF INSTRUCTIONS EXECUTED BEFORE
INTERRUPTS ARE ENABLED.
.
.3.2.2.
~.

SYM30LISM
WHEN IT IS NECESSARY TO INDICATE PARTICULAR BITS IN A WORD,
THEY ARE NUMBERED FROM RIGHT TO LEFT.

35

C:

o

------------------------------------------------------------------------------------------------------------------------2. WHEN PARTS OF WORDS ARE REFERENCED THE FOLLOWING SYMBOLS
AHE USED:

3

3

REFERENCE

PAGE:

UP-4144

Rev. I

35

UNIVAC 1108

OPERATING

EXEC· B

PROGRAMMERS REFERENCE

30 29

24 23

SYSTEM

18 17

12 11

3
SECTION:

6 5

4
PAGE:

o

-------------------------------~------------~---------.-----S1
S2
S3
55
S4
56

------------.-----------------------.----------.------------35

24 23

12 11

o

--.---------------------------------.-----.----.-------.----T1
T2
T3
------------------------------------------.----.------.-----35

18 17

o

--------.--------------.------------------.----.------------H1
H2
------------------------------------------.----.--.---------3. CONTROL REGISTERS ARE INDICATED BY THE FOLLOWING:
AO, Al, ETC. - ACCUMULATORS
XO, Xl, ETC. - INDEX REGISTERS
RO, kl, ETC. - R REGISTERS
4. WHEN REFERENCING AN EXTERNALLY DEFINED EXECUTIVE SYSTEM
SYMBOL THE LAST CHARACTER IS ALWAYS THE $. PROCEDURE NAMES USE THE $AS THEIR
SECOND CHARACTER. THEREFORE, IT IS RECOMMENDED THAT THE USER NOT USE THE $ IN
HIS SYMBOLS.
5. 1108 ASSEMBLER MNEMONICS ARE USED WHENEVER REFERENCES ARE
f<'lADE TO f't.ACHINE INSTRUCTIONS.

~
I

6. USER PROGRAMS ARE NORMALLY PROVIDED THE OPTION OF USING ONE
OF TwO SETS OF CONTROL REGISTERS. THE MINOR SET CONSISTS OF Xli, AO THRU A5,
AND R1 THRU R3, AND THE MAJOR SET CONSISTS OF ALL A, X AND R REGISTERS WITH THE
EXCEpTION OF RO~ INTERRUPT ACTIVITIES ARE ALWAyS ASSIGNED THE MINOR SET.
7. il08 ASSEMBLER SyNTACTIC RULES ARE USED FOR NUMBER REPRESENTATION (AN OCTAL VALUE HAS A PRECEDING ZERO).

I

~j;

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

4.

COMPONEI~T~

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

4
SECTION:

OF THE EXECUTIVE SYSTEM

THE UNIVAC 1108 EXECUTIVE SYSTEM IS COMPOSED OF MANY DIFFERENT ROUTINES, EACH OF
WIIICH P~KFORM SPECIFIC FUNCTIONS. THESE ROUTINES ARE ORGANIZED INTO SEVERAL SEPARATE
GkOUPS wHICH ARE THE BASIS OF DISCUSSION IN SUBSEQUENT SECTIONS OF THIS MANUAL. FOR
II~THOOUCTOKY PURPOSES, A BRIEF DESCRIPTION OF EACH COMPONENT GROUP FOLLOWS.
4.1.

SUPERVISOR

THE SUPERVISOR CONTROLS THE SEQUENCING, SETUP, AND EXECUTION OF ALL RUNS. AMONG
THOSE ROUTINES INCLUDED WITHIN THE SUPERVISOR ARE THE SCHEDULING ROUTINES, INTERRUPT
PROCESSING ROUTINES, TIMING ROUTINES, AND ACCOUNTING ROUTINES.
4.2.

EXECUTIVE REQUESTS

EXECUTIVE REQUESTS ARE'ENTRANCES INTO THE EXECUTIVE SYSTEM WHICH PROVIDE FUNCTIONS
FOR A USER PROGRAM. DEPENDING ON THE FUNCTIOi~, IT MAY BE PERFORMED ASYNCHRONOUSLY,
SYNCHRONOUSLY, OR IMMEDIATELY. IF IT IS NOT AN IMMEDIATE REQUEST, A QUEUE IS
r~AlN I AINED.

(

4.3.

SYI'4bIONTS

SYMBIONTS PROVIDE TH~ INTERFACE BETWEEN THE PRIMARY UNIT RECORD EQUIPMENT AND THE
USER PROGRAM. THESE ROUTINES ARE REFERENCED BY USING EXECUTIVE REQUESTS FOR INPUT
Ai-iD OUTPUT. It~PUT AND OUTPUT DATA ARE BUFFERED ON THE MASS STORAGE DEVICES.
4.~.

INPUT-OUTPUT DEVICE HANDLERS

THE iNPUT/OUTPUT HANDLERS ARE RESPONSIBLE FOR CONTROLLING THE ACTIVITIES OF ALL
I/O CHANNELS AND PERIPHERAL EQUIPMENT ATTACHEO TO THE UNIVAC 1108. THESE DEVICE
HAND~ERS PROVID~-THE USER WITrl A FULL CAPABILITY .OF PERIPHERAL DEVICE OPERATIONS.
4.~.

OPtRATOR COMMUNICATIONS

THE COMMUNIC~TIONS
ilET~EEN TIlE OPERATOR

SECTION OF THE EXECUTIVE SYSTEM HANDLES ALL COMMUNICATIONS
AND THE OPERATING. PROGRAMS. THIS COMMUNICATION TAKES PLACE VIA
THE Cor.WUTER KEYBOARD AND ON-LINE Pf{INTER ON THE CONSOLE CHANNEL. ' NEITHER THE
KEYBOARLJ NOR THE CONSOLE PRINTER CAN BE ASSIGiJED TO OPERATING PROGRAMS.

~.b.

FILE CONTROL SYSTEM

THE FILE SUPERVISOR CONTROLS THE CREATION AND MAINTENANCE OF ALL PROGRAM AND DATA
FILES. IT ALSO MAINTAINS AN UP-TO-DATE MASTER DIRECTORY OF ALL FILES CATALOGUED IN
THE SYSTEM AND THE AVAILABILITY OF ALL MASS STORAGE.

THE DATA

HAi~OLWG

ROUTlr~ES

ARE DESIGNED TO PROCESS A WIDE VARIETY OF FILE FORMATS

1
PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

2

4
SECTION:

PAGE:::

C)
USING A GENERAL TECHNIQUE.
THE SYSTEM.

FEW RESTRICTIONS ARE PLACED ON THE FORMATS ACCEPTABLE TO

FILES MAY BE PROCESSED AT THE ITEM OR BLOCK LEVELS WITH GENERAL DISREGARD FOR THE
PHYSICAL CHARACTERISTICS OF THE 1/0 DEVICE ASSIGNED. DATA IS PRESENTED OR ACCEPTED,
RANDOMLY OR SEQUENTIALLY, ON REQUEST OF THE USER THEREBY PROVIDING COMPLETE
OPERATIONAL FLE:XIBILITY FOR EFFICIENT FILE MANIPULATION.
4.8.

FILE UTILITY ROUTINES

TO AID THE USER IN THE MANIPULATION OF PROGRAM AND DATA FILES, A SET OF FILE
UTILITY ROUTINES IS PROVIDED BY THE EXECUTIVE SYSTEM. THESE ROUTINES PERFORM A
VARIETY OF FUNCTIONS FOR SYSTEM AND USER DATA FILE MAINTENANCE.
4.9.

AUXILIARY PROCESSORS

A SET OF AUXILIARY PROCESSORS IS INCLUDED IN THE EXECUTIVE SYSTEM. THESE
PROCESSORS COMPLEMENT TtiE SOURCE LANGUAGE PROCESSORS SUCH AS FORTRAN. THIS SET OF
PROCESSORS INCLUDES THE COLLECTOR FOR LINKING RELOCATABLE SUBPROGRAMS, AND THE
PROCEDURE DEFINITION PROCESSOR FOR INSERTING AND MODIFYING ASSEMBLER, COBOL, OR
FURTRAN PROCEDURE DEFINITIONS IN A PROGRAM-FILE.
4.10.

PROCESSOR INTERFACE ROUTINES

THE PROCESSOR INTERFACE ROUTINES PROVIDE A SIMPLE, STANDARD INTERFACE FOR ALL
pROCESSORS WITHIN THE SYSTEM. COMPLETE FACILITIES ARE PROVIDED FOR THE INPUT OF
SOURCE-LANGUAGE STATEMENTS AND THE OUTPUT OF THE RESULTING RELOCATABLE BINARY CODE.
4.11.

THE DIAGNOSTIC SYSTEM

A COMPREH~NSIV[ DIAGNOSTIC SYSTEM IS AVAILABLE WITHIN THE 1108 EXECUTIVE SYSTEM TO
AID THE CHECKOUT OF USER PROGRAMS. COMMANDS ARE AVAILABLE WHICH CAN TRIGGER SNAPSHOT
DUMPS AT THE TIME OF COMPILATION OR COLLECTION OF A USER ROUTINE. POST-MORTEM DUMPS
ARE ALSO AVAILABLE THROUGH AN EXECUTIVE CONTROL STATEMENT.
4.12.

SYSTEM SETUP

THl srSTEM GENERATION ROUTINE PROVIDES THE MEANS OF GENERATING AND MAINTAINING A
SYSTEM TAILOREJ TO THE PARTICULAR NEEDS OF EACH INSTALLATION.
4.13,

UTILITY ROUTINES

Ir~CLUD[U WlTHW THE UTILITIES SECTION OF THE EXECUTIVE SYSTEM ARE DIAGNOSTIC
ROUTlNES, FILE CONVERSION ROUTINES, AND OTHER PROGRAMMING AIDS,

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

5.

SYSTEM

PROGRAMMERS

SECTION:

EXECUTIVE CONTROL LANGUAGE

5. 1 •

PURPOSE

CONTROL OF THE OPERATING ENVIRONMENT ON THE UNIVAC 1108 IS ACCOMPLISHED THROUGH A
SlT OF CONTROL STATEMENTS. THESE STATEMENTS JIRECT THE EXECUTIVE IN SCHEDULING,
ASSIGNMENT OF FACILITIES, AND IN THE DISPOSITION OF PROGRAM AND DATA FILES. THE
LANGUAGE IS DESIGNED IN A COMPACT AND DESCRIPTIVE MANNER TO FACILITATE USE AND YET
PROVIDE ALL OF THE FEATURES AND FUNCTIONS OF A MODERN EXECUTIVE SYSTEM. STATEMENTS
MAY BE EASILY ADDED, MODIFIED, OR DELETED IN THE SYSTEM DEFINED SET.
5.2.

STATEMENTS

5.2.1.

GENERAL CONTENT

THE HASIC FORMAT OF THE EXECUTIVE CONTROL STATEMENTS IS QUITE SIMPLE AND IS
AMENABLE TO A LARGE NUM~ER OF INPUT DEVICES. STATEMENTS ARE NOT RESTRICTED TO A
CAHD-IMAGE FORMAT; HENCE, THEY MAY BE OF VARIABLE LENGTHS. EACH STATEMENT CONSISTS
OF A RECOGNITION CHARACTER IN COLUMN ONE, FOLLOWED BY A COMMAND WHICH CATEGORIzES THE
STATEMENT, FOLLOWED BY A VARIABLE NUMBER OF SPECIFICATIONS FIELDS, AND CONCLUDED BY A
COMMENTS FIELD. THE RECOGNITION CHARACTER IS A MASTER SPACE(Q), WHICH IS A MULTIPLE
(7-8) CARD PUNCH OR ITS EQUIVALENT FOR OTHER TYPES OF INPUT DEVICES (SUCH AS THE
TTY35 WIIERE TrlE POUND-SIGN (tI) IS USED). THE END OF A STATEMENT IS SIGNIFIED BY THE
END OF A CARD FOK CARD-IMAGE INPUT, OR BY A CARRIAGE RETURN OR ITS EQUIVALENT FOR
OTHER TYPES OF INPUT DEVICES. .
EXECUTIVE CONTROL STATEMENTS ARE ALWAYS LOGGED IN A BATCH RUN.S PRINT FILE. IF A
CONTROL STATEMENT IS IN ERROR, THE DIAGNOSTIC IS PRINTED IMMEDIATELY FOLLOWING THE
STATEMENT.
5.2.2.

STATEMENT FORMAT

THE GENERAL FORMAT OF AN EXECUTIVE CONTROL STATEMENT IS:
QLABEL:COMMAND,OPTIONS

SPEC1,SPEC2, ••• ,SPECN

COMMENT

THE FOLLOWING GIVES A DESCRIPTION OF EACH OF THE 'FIELDS' OF THE EXECUTIVE CONTROL
STA rEME~JT AS WELL AS FORMAT AND CONTINUATION RULES.
5.2.2.1.

LABEL FIELD

THE LABEL FIELD NEED NOT APPEAR BUT MAY BE USED TO NAME A CONTROL STATEMENT. THE
LA8EL IS LIMITEO TO SIX CHARACTERS FROM THE ALPHANUMERIC SET(A ••• Z,O ••• 9), THE FIRST
OF WHICH MUST BE AN ALPHABETIC. IF A LABEL IS SPECIFIED, IT MUST 8E IMMEDIATELY
FOLLOwED BY THE COLON(:). A LABEL IS USED ONLY WHEN DYNAMIC ADJUSTMENT OF THE
CONTROL STREAM IS REQUIRED. THE DISCUSSION OF THEIR USE IS DEFERRED TO THE SECTION
ENTITLED 'CONDITIO~AL STATEMENTS'.
5.~.2.2.

c

1

5

REFERENCE

COMMAND FIELD

THE COMMAND FIELD MUST ALW~YS BE SPECIFIED AS IT DETERMINES THE STATEMENT'S BASIC
OPERATION. THE COMMAND IS LIMITED TO SIX CHARACTERS FROM THE ALPHANUMERIC SET
(A ••• Z,O ••• 9), THE FIRST OF WHICH MUST BE ALPHABETIC. FOR CERTAIN CONTROL
STATE~ENTS, THE OPTIONS FIELD, WHICH IS AN APPENDAGE lOTHE COMMAND FIELD, IS
RI:.COGraZED. i/HEN THE OPTIONS FIELD IS SPECIFIED, THE COMMAND FIELD TERMINATOR IS THE
COMMA(,). HOWLVEH, ·IF AN OPTIONS FIELD IS NOT SPECIFIED BLANK( ) IS THE COMMAND

PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

5
SECTION:

2
PAGE:

FIELD TERMINATOR.
5.2.2.3.

OPTIONS FIELD

THE OPTIONS FIELD PROVIDES THE USER WITH THE ABILITY TO SPECIFY CERTAIN OPTIONS,
IN THE FORM OF UNSEQUENCED ALPHABETIC CHARACTERS, TO THE PARTICULAR PROCESSOR
ADDRESSED IN THE COMMAND FIELD OR TO A SPECIFIC PROGRAM AS IT IS EXECUTED. ON SOME
CONTROL STATEMENTS THE OPTIONS FIELD CAN BE BROKEN INTO SUB-FIELDS, EACH OF WHICH IS
SEPARATED BY A SLASH(/). A BLANK CHARACTER OR A SERIES OF BLANK CHARACTERS SEPARATES
THE COMMAND OR OPTIONS FIELD FROM THE SPECIFICATIONS FIELD~.
5.2.2.4.

SPECIFICATIONS FIELDS

THE SPECIFICATIONS FIELDS OF AN EXECUTIVE CONTROL.STATEMENT ARE SEPARATED BY
COMMAS AND ARE SPECIFIED BY THE USER AS DICTATED BY HIS REQUIREMENTS. THE CONTENT OF
EACH SPECIFICATION FIELD, THE NUMBER OF SPECIFICATION FIELDS, AND WHETHER EACH IS
R~QUIRED OR OPTIONAL, VARIES WITH THE COMMAND SELECTED.
SPECIFICATION FIELDS, IN
TURN, MAY CONTAIN SUBFIELDS THAT ARE SEPARATE0 BY A SLASH (I). FOR THE MOST PART,
THESE SUB-FIELDS ARE OPTIONAL WITHIN A FIELD. THUS, IT IS POSSIBLE TO SPECIFY PARTS
OF A FIELD WITHOUT SPECIFYING THE ENTIRE FIELD.
5.2.2.5.

LEADING 8LANKS

LEADING BLANKS ARE ALLOWABLE FOLLOWING THE RECOGNITION CHARACTER (Q), THE COLON
(:) IF A LABEL IS SPECIFIED, THE FIELD SEPARATOR (,), AND THE SUB-FIELD SEPARATOR
(I),
A BLANK IN ANY OTHER POSITION ACTS AS THE SEPARATOR SIGNIFYING THE START OF THE
SPECIFICATIONS FIELDS OR ~OMMENTS FIELD. AN EMPTY FIELD OR SUB-FIELD IS ONE THAT
CONTAINS NO CHARACTERS OR ONE OR MORE BLANK CHARACTERS. WHEN ALL REMAINING FIELDS OR
SUB-FIELDS ARE EMPTY, THEY MAy BE OMITTED.
5.2.2.6.

COMMENTS FIELD

AT LEAST O'~E ~LANK CHARACTER MUST PRECEDE THE COMMENT FIELD. THE COMMENT ITSELF
MAY CONTAIN ANY CHARACTER EXCEPT THE SEMICOLON (I), THE CONTINUATION CHARACTER. THE
COMMENT FI~LD IS ENDED BY END-OF-CARD OR ITS EQUIVALENT FOR OTHER INPUT DEVICES. THE
COMMENT FIELD IS NEVER REQUIRED. IF SPECIFICATIONS FIELDS ARE OMITTED, THE COMMENT
FlELD MUST BEGIN WITH A PERIOD (.) FOLLOWED bY A BLANK. THIS IS ALSO TRUE WHEN THE
CONTENT OF A SPECIFICATIONS FIELD IS UNRESTRICTED AND VARIABLE IN LENGTH (AS WITH THE
WLOG STATEMENT AND QMSG STATEMENT). THE WXQT STATEMENT IS AN EXAMPLE OF A STATEMENT
WHERE SPECIFICATIONS ARE POSSIBLE BUT MAY BE uMITTED.
5.2.3.

CONTINUATION RULES

IN CERTAIN SITUATIONS, A STATEMENT MAY REQUIRE MORE THAN ONE LINE OR CARD. IN
SUCti CASES, CODING OF A SEMICOLON (;) INDICATES CONTINUATION ON THE NEXT CARD OR
L.INE. A STATE~1ErH MAY tiE SPLIT AT .~NY POINT, AFTER THE OPTIONS FIELD, WHERE A
LEADING SPACE IS ALLOWAHL.E OR wITHIN THE COMMENT FIELD. IT IS TREATED LOGICALLY AS A
SPACE. CONTINUATION ON THE NEXT LINE CAN BEGIN IN ANY COLUMN, WITH ONE EXCEPTION: A
MASTER SPACE CHARACTER (W) SHOULD NOT BE PLACED IN COLUMN ONE ON A CONTINUATION LINE.
5.3.

STATEMENT TYPES

THE 1108 EXECUTIVE SYSTEM RECOGNIZES FIVE TYPES OF CONTRoL STATEMENTS:
1.
2.
3.
It.
5.

ORGANIZATIONAL STATEMENTS I
l,iPUT/OUTPUT SPECIFICATION STATEMENTS;
PKOC£SSOH CALL STATEMENTS I
Pf. THE 'E' OPTION
IS ASSUMED ONLY IF SOFTWARE IS USED.
B BINARY (NO TRANSLATE)
S

INDICATES THAT A SPECIFIC SYMBIONT MUST BE USED TO'PRINT
UR PUNCH THE FILE. CAN BE USED ~ITH EITHER TAPE OR DRUM
FILES. THE SPECIFIC SYMBIONT IS NAMED IN THE SYMBIONT
FIELD.
EXAMPLE

IN THIS EXAMPLE THE PRINT OUTPUT PRODUCED WILL BE
QUEUED TO AND PRINTED BY THE PRINT SYMBIONT 'PRl'.
C USEU ~ITH A PUNCH FILE WHEN THE SYMBIONT FIELD INDICATES
A RI::MUTE SITE.
THE 'FILENAME' FIELD IS USED TO SPECIFY THE FILE TO BE PROCESSED AND TO DIRECT
TAPE MOUNTING IF REQUIRED.
FOR

THE 'TYPE' FIELD SPECIFIES THE TAPE TYPE OF THE INPUT
A~Y SYSTEM CATALOGUED FILES.
THE FIELD VALUES ARE:

FILE~

THIS FIELD IS OMITTED

8e UiHSERVO VII IC
6C UiHSt::HVO VIC
4C Ui'HSEI\VO IVC
3/\ UiHSERVO llIA
2A Ur~ISERVO IIA

THE

'Sy~al0NT'

FIELD IS THE NAME OF A

SYM~IONT,

OR SYMBIONT CLASS, WHICH IS TO

PAGE: 15

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

16

5
SECTION:

PAGE:.

o
OUTPUT THE FILE. IF OMITTED, THE PRINT SYMBIONT ASSOCIATED WITH THE RUN INITIATION
DEVICE IS ASSUMED. TO TRANSMIT A PRINT FILE TO A REMOTE SITE, THE SITE 10 MUST
REPLACE THE SYMBIONT NAME AND THE '5' OPTION IS USED.
EXAMPLE
~SYM,S

FILEA,T,SPOl

IN THE EXAMP~E, THE TAPE FILE 'FILEA' WILL BE PRINTED AT REMOTE SITE 'SP01'. TO
TRANSMIT A PUNCH FILE TO A REMOTE SITE, BOTH THE '5' AND 'C, OPTIONS ARE USED AND THE
SITE 10 MUST REPLACE THE SyMBIONT NAME.
EXAMPLE
~SYM,SC

FILEB"SP02

IN THE EXAMPLE, THE FILE 'FILEB' WILL BE PUNCHED AT REMOTE SITE ,SP02'.
THE 'FILE-LABELS' FIELD IS USED FOR SELECTIVE PRINTING OR PUNCHING OF FILES RESIDING
ON 'FILENAME', WHERE THE DEVICE DEFJNED BY 'NAME' IS MAGNETIC TAPE. ·FILE LABELS ARE
SEPARATED WITH A SLASH (I).
MULTIPLE FILE PRINTINGS FROM MASS-STORAGE WILL BE EXECUTED CONCURRENTLY FOR EACH
STATEMENT ENCOUNTERED. TAPE FILES HOWEVER, ARE SERIAL. THE FILE-LABELS CAN BE
REPEATED ~OR MULTIPLE OUTPUT OPERATIONS. EACH ENTRY IN THE FILE-LABELS FIELD WILL
PRODUCE ONE OUTPUT OPERATION.
~SYM

THE SYSTEM PROVIDES A LINKAGE WHICH ALLOWS THE QSYM FUNCTION TO BE REQUESTED FROM
WITHIN A USER PROGRAM VIA CSF$. THE LINKAGE OESCRIPTION IS FOUND IN THE CHAPTER
ENTITLED 'SyMBIONTS'.
USE OF

5.~.9.1.

~SYM

WITH PRINT$ AND PUNCH$

EACH RUI~ ENTERED INTO THE SYSTEM HASSYMBIONTS DEFINED FOR PROCESSING THE SySTEM
INITIATED PRINT (PRINT$) FILE AND PUNCH (PUNCH$) FILE. THESE OUTPUT SYMBIONTS ARE
CLASSIFIED FOR EACH RUN AT SYSTEM GENERATION TIME (SEE SYSTEM GENERATION STATEMENTS ASSOCIATEU SYMBIONTS). HOWEVER IT MAY BECOME NECEsSARY TO REDEFINE EITHER, OR BOTH,
OUTPUT SYMBIONTS FOR A PARTICULAR RUN TO PROCES~ ALL, OR PORTIONS, OF THE OUTPUT
FILE. THE 'FILENAME' FIELD IS USED TO DENOTE THE PRINT OR PUNCH FILE WITH EITHER
PKINT$ OH PUNCH$ RESPECTIVELY. THE SYMBIONT FIELD IS USED AS DEFINED ABOVE. THE
REMAINING TWO FIELDS, .TYPE' AND 'FILELABELS', DO NOT APPLY TO PRINT$/PUNCH$ USAGE.
EXAMPLE
RUN

QSYM

PRINT$"RPN~/STP

~SYM,S

PRINT$"srp
PROGl

,QlXGT

IN THIS EXAMPLE, THE PRINT OUTPUT PRODUCED BY PRINT$ IS TO BE SENT TO THE REMOTE SITE
'STP, VIA THE REMOTE 100~ pRINT SYMBIONT
5.4.10.

THE

~COL

STATEMENT

EACH 1004 OF A SYSTEM HAS A DEFINED STANDARD CARD cOLUMN MODE FOR READING AND FOR
PUNCHInG WHICH IS ESTABLISHED AT SYSTEM GENERATION TIME (SEE SYSTEM GENERATION
STATEMENTS - CONNECT AND DISCONNECT CHANNEL). THE 80 COLUMN MODE IS ASSUMED STANDARD
UNLESS OTHERWISE SPECIFIED. WHEN OPERATING 14 THE STANDARD MODE IT MAY BECOME

~,

:'

V

\

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

(-':
NECESSARY TO READ CARDS IN A DIFFERENT COLUMN LENGTH. E.G. 80 COLUMN STANDARD MODE
IS DEFINED AND COLUMN BINARY CARDS ARE TO BE READ AS PART OF THE INPUT STREAM. THE
A~ILITY TO SWITCH CARD COLUMN MODE IS ACHIEVED WITH THE CONTROL STATEMENT
fii)COL,OPTIONS

xx

COMMENT

rJOTE: THE (.lCQL STATEt"'ENT IS FIXED IN FORMAT THRU THE FIRST
FOUR CHARACTERS. E.G. A QCOL CARD IS WRITTEN:
CQLUMN •••••• 123456789
CHARACTER ••• QCOL
WHERE 'XX' SPECIFIES THE INPUT MODE TO BE USED TO READ THE FOLLOWING DATA OF THE
CONTROL STREAM. THE INPUT MODE IS SWITCHED TO FACILITATE THE READING OF THE
FOLLOWING CARDS AND IS MAINTAINED UNTIL THE TERMINATION SENTINEL CARD IS ENCOUNTERED
Ok UNTIL THE END OF THE INPUT STREAM IS DETECTED. THE LATTER TWO CASES RESTORE THE
STANDARD MODE.
xx
CB
PT5
PT6
PT7
PTa

()

UEFINITION

----------

SWITCH TO COLUMN BINARY INPUT
OR 1004
SWITCH TO 5 LEVEL PAPER TAPE
SWITCH TO 6 LEVEL PAPER TAPE
SWITCH TO 7 LEVEL PAPER TAPE
SWITCH TO 8 LEVEL PAPER TAPE

MODE-900 CPM READER
INPUT
INPUT
INPUT
INPUT

MODE-1OO4
MODE-1004
MODE-1004
MODE-1OO4

THE OPTIONS FIELD MAY HAVE THE VALUE:
T- TRANSLATE PAPER TAPE INPUT TO FIELD DATA
PAPER TAPE INPUT IS TRANSLATED TO FIELD DATA FROM A STANDARD
CODE WHEN REQUESTED ON THE QCOL CONTROL CARD.
EACH Blr~ARY MoDE IS TERMINATED WITH A PARTICULAR SENTINEL IMAGE WHICH IS USED TO
NOTIFy THE INPUT SYMBIONT OF END OF BINARY DATA. THIS IMAGE HAS THE FIELDATA
II~TERPRETATION 'QENDCL'.
THIS SENTINEL MUST APPEAR IN COLUMNS,1-6 OF THE TERMINATION
IMAGE.
A BLANK CARD IS REQUIRED FOLLOWING THE ~COL STATEMENT AND THE END SENTINEL IMAGE.
THIS IS NECESSARY TO PROPERLY CONDITION THE INPUT MEDIA TO HANDLE THE CHANGE IN THE
INPUT OPERATION. THE DATA CARDS READ IN THE NEW MODE MUST IMMEDIATELY FOLLOW THE
BLANK CARD.
EXAMPLE

[.lCOL CB
IGNOREU CARD
DATA CARDS
iOlENDCL
IGNORED CARD
CONTINUATION OF RUN STREAM

THE BINARY MODE TERMINATION SENTINEL CAN BE REDEFINED WHEN SPECIFYING A BINARY
MODE OF INPUT WITH THE ~COL CARD.

C:

~COL,OPTIONS

17

5
SECTION:

XX,SENT

'SENT' IS A FIVE CHARAC1ER FIELD REDEFINING THE BINARY TERMINATION SENTINEL. THE
FlRST FIVE CHARACTERS HtMEoIATELY FOLLOWING THE COMMA ARE CONVERTED TO THE BINARY

PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

18

5
SECTION:

PAGE:

o
IMAGE IN WHICH THE TERMINATION IMAGE WILL BE READ. THE 'SENT' FIELD HAS AN IMPLIED
,~, PRECEEPING THE FIVE CHARACTER STRING, AND MUST APPEAR ON TERMINATION STATEMENT AS
'r~SENT'.
E.G.
folCOL CB,NEWSN
BLANK CARD (DISREGARDED BY SYSTEM)
BINARY DATA
folNEWSN
BLANK CARD
THE INTERPRETATION OF THE folCOL AND BINARY MODE TERMINATION CARDS IS DONE DURING
THE READING OF THE INPUT STREAM, AND THEY ARE NOT PLACED IN THE RUN FILE. NEITHER
CARD CAN HAVE A MEANINGFUL LABEL. THE IGNORED CARDS ARE ALSO ELIMIMATED FROM THE RUN
FILE.
THE 'SENT' FIELD IS ALSO USED FOR TERMINATION OF PAPER TAPE INPUT STREAMS. SENT
IS THEN AN OCTAL VALUE, EACH COLUMN REPRESENTING THREE BITS, WHICH IS THE END OF
INPUT SENTINEL. IF NO SENTINEL IS SPECIFIED ON THE folCOL CONTROL CARD, STANDARD
SySTEM SENTINELS ARE ASSUMED AS FOLLOWS.
PR5- 03321j.
PH6Olj.3
PR1Qlj.1
PT8Qlj.1

5.Ij..ll.

THE WCKPT STATEMENT

THE folCKPT STATEMENT IS USED TO ESTABLISH A CHECKPOINT DUMP AT SOME POINT IN THE
CONTROL STREAM TO BE USED AS A RESTART POINT IN THE EVENT SOME CONTINGENCY FORCED THE
RUN TO ABORT. CHECKPOINTS ARE RECORDED ON OUTPUT FILES ONLY AND THERE MAY BE AS MANY
STATEMENTS AS THE USER DEEMS NECESSARy FOR THE RUN. THE FORMAT OF THE folCKPT CONTROL
STATEMENT.IS:
QCKPT,OPTIONS

FILENAME

THE OPTIONS FIELU CAN INCLUDE TWO'CHARACTERS.

THESE ARE:

P

THIS SPECIFIES THAT THE DUMP COMPLETION MESSAGE AND
ALL ERROR MESSAGES ARE TO BE WRITTEN ON THE CONSOLE.
IF NOT PRESENT NONE OF THESE MESSAGES WILL BE WRITTEN.

T

THIS SPECIFIES THAT THE RUN IS TO BE TERMINATED AFTER
THE CHECKPOINT IS TAKEN.

THE FIELD 'FILENAME' CONTAINS rHE NAME OF A FILE PRESENTLY ASSIGNED TO THE RUN
INTO WHICH THE CHECKPOINT INFORMATION WILL BE RECORDED. IT MAY BE AN OUTPUT DATA
FILE OR AN INDEPENUENT FILE DEFINED BY THE USER TO CONTAIN CHECKPOINT INFORMATION
ONLY. IF THE PUMP IS TO RESIDE ON FASTRANP, IT MUST BE ON A SEQUENTIAL FILEI THE
CrlECKPOINT CAN NOT BE TAKEN ON A RANDOM FILE. THE FILENAME MAY ALSO BE THE NAME OF A
FlLE ASSIGNED TO THE SYSTEM BY THE OPERATOR TO CONTAIN CHECKPOINT INFORMATION FROM
S~VERAL RUNS.
SEE A LATER SECTION OF THIS MANUAL FOR A DETAILED DESCRIPTION OF THE
CHECKPOINT FACILITIES.
5.4.12.

THE QRSTRT STATEMENT

THE QRSTRT STATEMENT IS USED TO RE-ESTABLISH (RESTART) A RUN AT SOME DESIGNATED
CHECKPOINT PREVIOUSLY TAKEN. THE FILE ON WHICH THE DUMP IS LOCATED MUST BE
CATALOGUED AT THE TIME OF QRSTRT. ITS EFFECT WITHIN THE CONTROL STREAM MAY BE
SIMILAR IN FUNCTION TO THAT OF THE QSTART CONTROL STATEMENT IN THAT SETUP AND
EXECUTION OF THE RUN TO BE RESTARTED IS AN INDEPENDENT OPERATION, OR IT MAY BE A
R~START OF THE RUN REQUESTING RESTART.
IN THE LATTER CASE THE RUN IS TERMINATED AND
R~STARTEU AT THE NA~1ED CHECKPOINT.
THE FORMAT OF THE QRSTRT STATEMENT IS:
GRSTRT,PRIORITY/OPTION

RUNID,ACCOUNTING,FILENAME,CKPT~,REEL~

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

19

5

PAGE:

THE PklORITY FIELD SPECIFIES THE NEW PRIORITY UNDER WHICH TO REESTABLISH AND RERUN
TtiE RUN. IF rWT SPECIFIED THE STANDARD SYSTEM PRIORITY IS USED.
TO

THE OPTIONS FIELD MAY CONTAIN A 'PI TO SPECIFY THAT THE RESTART ERROR MESSAGES ARE
PRINTEO ON THE CONSOLE PRINTER AS WELL AS THE 'PROGRAM LOG.

~E

THE KUN-ID FIELD IS TliE 10 OF THE RUN TO BE RESTARTED.
THE CORRECT CHECKPOINT DUMP.

IT WILL BE USED TO LOCATE

THE ACCOUNTING FIELD SPECIFIES THE ACCOUNT TO WHICH THE CHARGE FOR RELOADING THE
RUN IS TO ~E ATTRIBUTED. THE ORIGINAL ACCOUNT WILL BE CHARGED WHEN THE
R~-ESTA~LISHED RUN RECEIVES CONTROL.
BOTH THE PRIORITY AND ACCOUNTING SPECIFICATIONS
MAY ~E OMITTED. IF OMITTED THOSE OF THE INITIATING RUN ARE USED.
THE CKPT# FIELD SPECIFIES THE PARTICULAR CHECKPOINT DUMP OF THIS RUN-ID THAT IS TO
13E Rt::.STARTED.
THE FIL~NAME FIELD SPECIFIES THE NAME OF THE CATALOGUED FILE THAT CONTAINS THE
CHECKPOINT O'Ufl.1P. THE. Rt:EL FIELD CONTAINS THE NUMBER OF THE REEL OF THE FILE THAT
ACTUALLY CONTAINS THE DUMP TO RESTART. IF A REEL NUMBER IS NOT GIVEN, THE SEARCH
~ILL BEGIN WITH THE FIRST REEL OF THE FILE.
ALL OF THE INFORMATION NECESSARy TO READ
THE CHECKPOINT FILE WILL BE TAKEN FROM THE DIRECTORY~
5.5.

(-'

INPUT/OUTPUT SpECIFICATION STATEMENTS

5'5'1'

THE QASG STATEMENT

THE gASG (ASSIGN) CONTROL STATEMENT, IS USED TO NAME AN EXTERNAL FILE, STATE ITS
I/O FACILITY REQUIREMENTS, AND CAUSE THEIR ASSIGNMENT TO THE REQUESTING RUN, UNDER
HiE GIVEN EXTERNAL FILE I~Afv'!E.
IF THE FILE IS CATALOGUED THE FACILITY REQUIREMENTS
AKE KNOWN AND NEED NOT BE SPECIFIED IN ASSIGNING THE FILE AS INPUT. THE VARIETY OF
INPUT/OUTPUT DEVICES AVAILABLE MAKES SEVERAL FORMATS NECESSARY FOR THIS STATEMENT.
THERE ARE FOUR ~ASIC FORMATS, AS FOLLOWS:
1. TilE FASTRAND r.JASG STATEMENT
2. THE MAGNETIC TAPE gASG STATEMENT
3. THE DRUM rolASG STATEMENT
4. THE ARdlTRARY DEVICE r.JASG STATEMENT
£ACH SPECIFIC FORMAT IS DISCUSSED INDIVIDUALLy IN SUCCEEDING PARAGRAPHS,
THE SYSTEM PROVIDES A LINKAGE WHICH ALLOWS THE r.JASG FUNCTION TO BE REQUESTED FROM
WITHIN A USER PROGRAM. THE LINKAGE DESCRIPTION IS FOUND IN 'EXECUTIVE REQUEST
FUNCTIONS', SECTION 8.
ALL USER FILES '''UST BE ASSIGNED PRIOR TO BEING REFERENCED FOR 1/0 OPERATIONS.
MAY OCCUR IN ONE OF THREE WAYS:

A~SIGNMENTS

THE

1. VIA AN ~ASG CONTROL STATEMENT.
2. VIA AN EXECUTIVE REQUEST FROM WITHIN A USER PROGRAM.
3. VIA AN EXECUTIVE REQUEST FROM WITHIN A PART OF THE
SYSTEM ITSELF, SUCH AS A SYStEM PROCESSOR OR THE FILE
UTILITY ROUTINE (FUR)
THE ONLY CASE WHERE A fILE CAN BE REFERENCED WITHOUT AN ASSIGNMENT SPECIFICATION
l~ASG STATEMENT) ON-TilE PART OF THE USER IS WHEN A CATALOGUEDFASTRAND FILE IS BEING
NAt4ED ON A CONTROL STATEMENT OR BEING NAME;.D IN THE SOURCE LANGUAGE TO A SYSTEM
PROCE;.SSOR, SUCH AS THE COLLECTOR. AS IMPLIED IN CASE 3 ABOVE, THE ACTUAL ASSIGNMENT
IS MADE ~Y THE PARTICULA~ PART OF THE SYSTEM HANDLING THE CONTROL STATEMENT AND ALL
iNFORMATION COfJCEHNING THE ASSIGNMENT IS TAKEN FROM THE DIRECTORY. IF ANY
l~FORMATIUN IS NEEDED AUOUT THE FILE OTHER THAN ITS NAME, SUCH AS AN OPTION LETTER,

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

5

PAGE:

20

AN QASG STATEMENT MUST BE USED TO ASSIGN THE FILE. THE USER IS ALWAYS FREE TO ASSIGN
A FILE PRIOR TO REFERENCING IT ON A CONTROL STATEMENT. IN THIS CASE THE PART OF THE
SYSTEM HANDLING THE CONTROL STATEMENT WILL DETECT THAl THE ASSIGNMENT HAS ALREADY
BEEN MADE. THIS ASSIGNMENT MUST BE PERFORMED IF THE FILE IS NOT A CATALOGUED
FASTRAND FILE.
5.5.1.1.

NOTATION FOR FILE NAMES

THE ~ASG STATEMENTS, AS WELL AS OTHER CONTROL,STATEMENTS, REQUIRE THAT AN
'EXTERNAL' FILE NAME BE SPECIFIED. PRIOR TO DEALING WITH THE INDIVIDUAL QASG
STATEMENTS, AN EXPLANATION OF THE NOTATION USED FOR FILE NAMES IS IN ORDER.
IN THE FORMAT DESCRIPTION OF THE VARIOUS CONTROL STATEMENTS, THE 'EXTERNAL' FILE
NAME IS INDICATED BY 'FILENAME, OR SIMPLY BY 'NAME'. IT SHOULD BE NOTED THAT
ALTHOUGH SOME OF THE CONTROL STATEMENTS JUST SPECIFY THE 'EXTERNAL' FILE NAME
SPECIFICATION FIELD, THE 'READ' AND 'WRITE' KEYS SUB-FIELDS ARE ALWAYS IMPLIED. (THE
KEYS ARt NOT PART OF THE FILE NAME BUT ARE ALWAYS ASSOCIATED WITH IT.) NORMALLY,
WHEN A FILE IS REFERENCED IN THE CONTROL STREAM, IT IS THE 'EXTERNAL' NAME THAT IS
INTENDED, ALTHOUGH IT CAN ALWAYS BE AN INTERNAL NAME.
AN 'EXTERNAL' FILE NAME HAS THE FORMAT
QUALIFIER*FILE(F-CYCLE)
WHERE THE 'QUALIFIER', THE '*', AND THE '(F-CYCLE)' ARE ALL OPTIONAL AND BOTH THE
AND THE 'FILE' ARE LIMITED TO 12 CHARACTERS EACH FROM THE SET A••• Z,
0 ••• 9, -, AND $. THE OMISSION OF THE ,QUALIFIER' WITH THE '*' PRESENT CAUSES THE
folGlUAL STATEMENT TO SUPPLY THE QUALIFIER USED. IF THE fiilQUAL STATEMENT HAS NOT
OC'URREU, THE 'PROJECT' FIELD FROM THE QRUN STATEMENT IS USED AS THE QUALIFIER. THE
OMISSION OF BOTH THE 'QUALIFIER' AND THE '*' ALSO CAUSES THE 'PROJECT' FIELD FROM THE
fiilRUN STATEMENT TO BE USED AS THE QUALIFIER (PROVIDED THE 'FILE' IS NOT AN 'ATTACHED'
NAME WHICH POINTS TO A PARTICULAR EXTERNAL NA;';E). THE PURPOSE OF THE QUALIFIER
(PROJECT) IS TO ALLOW 24 CHARACTER UNIQUENESS IN THE CATALOGUE DIRECTORY - BUT MORE
IMPORTANT - IF A PARTICULAR USER IS GIVEN A PHIVATE PROJECT NUMBER(S), IT INSURES THE
AbILITY-TO CATALOGUE THE FILE WITHOUT NAME CONFLICTION, AS LONG AS THE USER INSURES
THAT THE 'FILE' DESIGNATORS ARE UNIQUE WITHIN THE PROJECT. THE ,F-CYCLE' NUMBER
SERVES TO MAINTAIN SUCCESSIVE VERSIONS OF THE SAME FILE (SAME 'QUALIFIER' AND
'FILE'). OMISSION OF THE F-CYCLE IMPLIES THAT THE MOST RECENTLY CONSTRUCTED FILE IS
INTENDED.
'~UALIFIER,

THE USE OF THE F-CYCLE FOR FILE CATALOGUING IS SIMILAR TO THE USE OF THE 'CYCLE'
FIELD IN PRODUCING UPDATED PROGRAM ELEMENTS.
THE DISCUSSION TO FOLLOW ASSUMES THAT THE REAOER HAS SEEN THE SECTION ON 'PROCESSOR
CALL STATEMENTS' AND IS FAMILIAR WITH HOW THE 'CYCLE' IS USED FOR ELEMENTS WITHIN A
FILE.
A FILE ~ITH A PARTICULAR F-CYCLE NUMBER CAN BE REFERENCED BY THE ABSOLUTE F-CYCLE
NUMBER (IDENTICAL TO THAT DESCRIBED BY CYCLE) OR BY A RELATIVE F-CYCLE NUMBER. WiTH
TrlE RELATIVE t~UMBER, THE LAST FILE TO BE PRODUCED AND CATALOGUED IS REFERENCED BY
'+0' OR A VOIDJ THE ONE BEING PRODUCED AND TO BE CATALOGUED BY A '+1" AND THE BACKUP
FILES ur '-1', '-2', ETC. "AS AN EXAMPLE, IF THE LAST FILE TO BE CATALOGUED HAD AN
ABSOLUTE F-CrCLE I\lUMBER OF 28, IT COULD ae;: REFERENCED BY 28, +0, OR AVOID WITH THE
N~W FILE TO BE CATALOGUED CALLED +1.
PRIOR TO THE CATALOGUING OF 29, IF A BACKUP
EXISTS FOR 28, IT IS NECESSARILY CALLED -1. WHEN THE NEW FILE(29) IS CATALOGUED, IT
BECOMES '+0' ~ITH 28 MOVED TO -1 AND 27 MOVED TO -2. A PLUS SIGN IS ILLEGAL WHEN THE
11~TENTION IS FOR ABSOLUTE NOTATION.
ABSOLUTE F-CYCLE NUMBERS BEGIN WITH 1 AND
CONTINUE TO 999 AT WHICH POINT NUMBERING BEGINS WITH 1 AGAIN. THE RELATIVE F-CYCLE
NUM~ER ALLO~S THE USER TO ACCESS A PARTICULAR RELATIVE BACKUP, FOR EXAMPLE NUMBER 2,
WITH A '-2' AT ALL TIMES, WHEREAS WITH THE ABSOLUTE F-CYCLE THE NUMBER CHANGES WITH
SUCCESSIVE RUiJS.
(PROGRAM-FILENAME.ELEMENTNAME/VERSIOtHCYCLE». WHEN UPDATING IS CALLED FoR,
THE F-CYCLt:: NlJMdEH FOR THE NEW FIELD MUST 5ESPECIFIED AS +1. IF AN EXISTWG F-CYCLE

(~\

~/

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
REFERENCE

IS BEING RENAMED TO SOMETHING OUTSIDE THE SET ALL OLDER RELATIVE F-CYCLES OF THE FILE
ARE INCREASED BY ONE • THE ABSOLUTE F-CYCLE DESIGNATOR WILL NOT CHANGE. IF IT IS
RENAMED TO RESIDE WITHIN THE SET IT MUST 8E GIVEN AN F-CYCLE NUMBER OF +1 TO CONFORM
TO THE F-CYCLE RULES. THE 'OLD NAME' FILE IS TREATED AS THOUGH IT WERE BEING MOVED
OUTSIDE THE SET, BUT IS PLACED IN THE SAME SET WITH THE ,NEW NAME'. ACTUALLY A
DIFFERENT F-CYCLE , IT IS TREATED AS A CATALOGUE ACTION. NUMBER. IF FILE IS BEING
RENAMED TO SOMETHING OUTSIDE THE SET ALL OLDER RELATIVE F-CYCLES OF THE FILE ARE
lNCREASED bY ONE. IF IT IS RENAMED TO RESIDE WITHIN THE SET, IT MUST BE GIVEN AN
F-CYCLE NUMBER OF +1 TO CONFORM TO THE F-CYCLE RULES. THE 'OLD NAME' FILE IS TREATED
AS THOUGH IT WERE BEING MOVED OUTSIDE THE SET, BUT WHEN PLACED BACK IN THE SAME SET
WITH THE 'NEW NAME', ACTUALLY A DIFFERENT F-CyCLE, IT IS TREATED AS A CATALOGUE
ACTION.
THE MAXIMUM RANGE OF ABSOLUTE F-CYCLES MAINTAINED FOR A PARTICULAR FILE IS
DETERMINED EITHER AS THE SYSTEM STANDARD FOR ALL FILES SUPPLIED AT SYSTEM GENERATION
TIME (SEE SYSTEM GENERATION STATEMENTS - RETAIN CYCLES AND F-CYCLES, AND INITIAL
$YSTEMI OR AS THE NUMBER SPECIFIED BY THE USER VIA THE FILE UTILITY ROUTINE FOR THIS
F1LE. AUTOMATIC DELETION OF THE DIRECTORY ENTRY FOR THE OLDEST FILE FILE ITSELF IS
ON FASTRANO, IT TOO IS DELETED. IF THE FILE IS ON MAGNETIC TAPE, THE OPERATOR IS
NOTIFIED OF THE DIRECTOKY DELETION.
WITHIN EACH RUN, THE 'EXTERNAL' NAMES OF THE CURRENT FILE ASSIGNMENTS MUST BE
UNIQUE. CURRENT ASSIGNMENTS ARE THOSE ASSIGNED VIA THE ~ASG REQUEST BUT NOT YET
RELEASED VIA THE wFREE STATEMENT. IN MAINTAINING UNIQUENESS, ANY TWO OF THE FILES
ARE UNIQUE IN Of,JE OF THREE WAYS:
1. UNIQUE BY BOTH 'QUALIFIER' AND 'FILE'
2. UNIQUE BY THE F-CYCLE NUMBER ONLY
IF NONE OF THESE CONDITIONS IS MET, THE ASSIGNMENT IS RE~ECTED BY THE SYSTEM AND
THE RUN IS TERMINATED AND PLACED IN THE ERROR MODE. CATALOGUED FILES ARE NECESSARILY
UNIQUE WITHIN THEMSELVES; HOWEVER, THE USER MAY DEFINE ADDITIONAL FILES THAT CAUSE A
CONFLICT. IN THE NORMAL CASE, THE USER MUST GUARD ONLY AGAINST A CONFLICT AMONG THE
'FILE' SPECIFICATIONS WITHIN HIS GIVEN QUALIFIER (PRO~ECT). TWO CASES ARISE HoWEVER
WHERE THERE IS A CONFLICT AMONG THE 'FILE' PORTIONS OF EXTERNAL NAMES. THIS OCCURS
WHEN THE CYCLING FEATURE IS BEING USED AND WHEN THE NAMES ARE UNIQUE ONLY BY
QUALIFIER BECAUSE THE USER MUST USE A FILE OUTSIDE OF HIS PRO~ECT BUT WITH THE SAME
'FILE' PORTION AS ONE OF HIS OWN FILES. (THE SIGNIFICANCE OF THESE TWO POINTS WILL BE
BROUGHT OUT SUBSEQUENTLY.)
THE • INTERNAL' FILE NAME IS USED BY THE WORKER PROGRAM ON AN I/O REFERENCE TO THE
EXECUTIVE AND SPECIFIES THE FILE TO BE USED FOR THE I/O OPERATION. IT IS LIMITED TO
A MAXIMUM OF 12 CHARACTERS FROM THE SET A, •• Z, 0 ••• 9, -, AND $. THE 'INTERNAL, NAME
MUST POINT TO SOME 'EXTERNAL' NAME BEFORE THE I/O REFERENCE CAN BE HONORED. THIS
CONNECTION IS AUTOMATIC BY HAVING THE 'INTERNAL' NAME THE SAME AS THE 'FILE' PORTION
OF THE 'EXTERNAL' NAME (ALSO 12 CHARACTERS). AS AN EXAMPLE, IF THE 'EXTERNAL' NAME
ON THE ~ASG STATEMENT IS 'SLACK*CAT', THEN AN ,INTERNAL' NAME OF 'CAT' WILL POINT TO
THE FILE.
THE • INTERNAL' NAME NEED NOT BE THE SAME AS THE 'FILE, PORTION OF THE 'EXTERNAL'
NAME. FOR EXAMPLE, AN 'INTERNAL' NAME OF 'CAT' CAN BE MADE TO POINT TO THE FILE
'tl~ACK*OOG' By THE FOLLOWING CONTROL STATEMENT:
QUSE

CAT,BLACK*DOG

THIS STATEMENT CAUSES THE NAME 'CAT' TO BE 'ATTACHED' TO THE 'EXTERNAL' NAME. THIS
FE.ATURE ALLOWS 'INTERNAL' NAMES TO BE FIXED AND SUBSEQUENTLY CONNECTED TO ANy
'tXTERNAL' FILE, DEPENDING ON THE PARTICULAR RUN. FOR A COMPLETE EXPLANATION OF THIS
STATEMENT, THE READER SHOULD SEE SECTION 5. ON THE '~USE STATEMENT'.

c

21

5
SECTION:

IN THE TWO CASES MENTIONED ABOVE WHERE lHE ,FILE' PORTIONS OF 'EXTERNAL' NAMES ARE
NOT UNIQUE, A QUSE STATEMENT IS REQUIRED IN ORDER TO CONNECT AN 'INTERNAL' NAME TO A
PARTICULAR FILE INVOLVED IN THE CONFLICT. WHEN AN ASSIGNMENT IS MADE, IF THE ,FILE'
PORTION OF THE 'EXTERNAL' NAME IS THE SAM~ AS THAT OF A PREVIOUS ASSIGNMENT, THE FILE

PAGE:

iUP-4144

UNIVAC 1108

OPERATING

I Rev. 1

EXEC

PROGRAMMERS REFERENCE

a

SYSTEM

BEING ASSIGNED IS MARKED AS NOT-AVAILABLE FOR I/O REFERENCE EXCEPT VIA AN 'ATTACHED'
NAME SUPPLIED BY A ~USE STATEMENT TO RESOLVE THE CONFLICT. IN OTHER WORDS, OF ALL
FILES THAT HAVE THE SAME 'FILE' PORTION IN THEIR 'EXTERNAL' NAMES, ONLY THE FIRST CAN
BE REFERENCED BY THE 'FILE' PORTION ON AN I/O REFERENCE. ALL OTHERS MUST HAVE
'ATTACHED' NAMES. AS STATED EARLIER. THIS SITUATION ARISES ONLY WHEN THE F-CVCLE
FEATURE IS BEING USED AND WHEN THE 'FILE' PORTIONS ARE NOT UNIQUE BECAUSE OF THE
NECESSITY TO USE FILES FROM DIFFERENT PRO~ECTS BUT WITH THE SAME 'FILE' IDENTIFIERS.
AN 'ATTACHED' NAME MAY BE USED FROM WITHIN THE CONTROL STREAM IF SPECIFIED BY A
QUSE STATEMENT. THE EXTERNAL NAME (WHERE THE PRO~ECT OR QUALIFIER IS USED) WILL
ALWAYS SUFFICE. HOWEVER IT MAy BE DESIRABLE To USE A SHORTER NAME OR TO USE AN
'ATTACHED' NAME THAT HAD TO BE SPECIFIED FOR SOME OTHER REASON. THE SYSTEM TREATS
FILE SPECIFICATIONS IN THE CONTROL STREAM AS FOLLOWS. IF ANY PART OF THE 'EXTERNAL'
NAME OTHER THAN THE 'FILE' PORTION IS GIVEN, THE NAME IS ALWAYS TREATED AS
'EXTERNAL'. IF ONLy THE 'FILE' PORTION IS SPECIFIED ~ND THE 'FILE' CANNOT BE FOUND
IN THE 'ATTACHED' LIST •. THE 'EXTERNAL' LIST IS SEARCHED FOR THE 'PRO~ECT*FILE'. IF A
MATCH IS NOT FOUND, IT IS THEN ASSUMED THAT THE FILE IS A CATALOGUED FILE YET TO BE
ASSIGNED. IF AN 'ATTACHED, NAME IS NOT INTENDED. BUT SUCH AN 'ATTACHED' NAME EXISTS,
THE '*' MUST BE SPECIFIED EVEN IF THE 'QUALIFIER'. IS ACTU4LLY THE PRO~ECT NUMBER.
THIS IS THE ABNORMAL CASE AND OCCURS ONLY WHEN THERE IS A ~ONFLICT BETWEEN 'ATTACHED'
NAMES AND THE 'FILE' PORTION OF AN 'EXTERNAL' NAME.
EXCLUSIVE USE FILE AND FACILITY HANDLING
THE EXEC PROVIDES FOH THE PLACEMENT OF QASG AND ~FREE STATEMENTS ANYWHERE WITHIN
THE CONTROL STREAM. DYNAMIC ASSIGN AND FREE REQUEsTS MAY APPEAR WITHIN THE PROGRAMS,
THESE FEATURES ALLOW THE USER TO ASSIGN AND FREE FILES AS REGUIRED, WITHOUT
'TYING-UP' THE FILES AND/OR FACILITIES FROM THE BEGINNING OF THE RUN UNTIL ITS
COMPLETION. HOWEVER. THE USER MIGHT BE FORCED TO WAIT UNTIL THE FACILITY OR FILE IS
MADE AVAILABLE WHEN THE REQUEST IS FOR ONE OF THE FOLLOWING:
1.

2.
.3.
4.

A MAGNETIC TAPE UNIT THAT IS BEING USED BY ANOTHER RUN.
AN ARBITRARy DEVICE THAT IS BEING USED BY ANOTHER RUN •
'A MAGNETIC TAPE FILE. THAT IS BEING USED BY ANOTHER RUN.
EXCLUSIVE USE OF A FASTRAND FILE BY ANOTHER RUN
OR THIS RUN.

TO PREVENT THE POSSIBLE PROLONGED WAIT OF A RUN. WHEN REQUESTING AN EXC.LUSIVE USE
FACILITY AND YET NOT FORCE A RUN TO SPECIFY ALL REQUIREMENTS BEFORE THE FIRST PROGRAM
(TASK) OF THE CONTROL STREAM, THE EXECUTIVE:
. 1.
2.
3.

WILL NOT OPEN.A RUN FOR EXECUTION UNTIL ALL THE
QASG STATEMENTS LOCATED BEFORE THE FIRST TASK
IN THE CONTROL STREAM HAVE BEEN SATISFIED.
WILL NOT START THE EXECUTION OF A PROGRAM UNTIL
ALL THE r.lASG STATEMENTS LOCATED BEFORE THE PROGRAM
IN THE CONTROL STREAM HAVE BEEN SATISFIED.
WILL MAINTAIN FOR EACH RUN (ONCE IT HAS BEEN OPENED)
A PRIVATE FACILITY POOL.

oN THE MAGNETIC TAPE folASG STATEMENTS, THERE IS AN OPTION WHICH RELEASES ~UST THE
FILE AND NOT THE PHYSICAL FACILITY AT THE OCCURR~NCE OF A ~FREE STATEMENT. THE
'SAVED' PHYSICAL FACILITY IS PLACED IN THE FACILITY POOL OF THE RUN AND IS AVAILABLE
FOR RE'-ASSIGNMENT AT ANY POINT WITHIN THIS RUN. THE FACILITY WILl. NOT BE RETURNED TO
THE EXECUTIVE'S FACILITY POOL, AVAILABLE TO ALL RUNS, UNTIL IT IS RE-ASSIGNED AND
COMPLETELY RELEASED OR UNTIL RUN TERMINATION. THE USER RE .. ASSIGNS F:ACILITIES THROUGH
NORMAL MEAI~S,· CONFloENT iTHAT THE REQUEST CAN 8E IMMEDIATELY HONORED, SINcE: THE RUN'S
FACII..ITY POOL IS ALWAYS REFERENCED BEFORE HiE EXEClJTIVE'S FACILITY POOL. BY USING
THE ABOVE MENTIONED OPTION. (SEE DISCUSSIONS OF~ASG STATEMENTS) AND SPECIFYING. BEFORE
THE FIRST PROGRAM OF THE RUN, THE MAXIMUM AMOUNT OF EACH TYPE OF MAGNETIC TAPE OR
AHsITRARYDEVICE THE RUN WILL REQUIRE AT ANY ONE GIVEN TIME, THE USER HAS THE ABILITY

W : ·
,.

,

,.

22

5
SECTION:

.

,

'

:

PLACE QASGSTATEMENTS AND/OR DYNAMIC ASSIGN REQUESTS

----_._--------- - - - - - - - - -

-

..

_-------

PAGE:

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

PROGRAMMERS REFERENCE

SECTION:

ANYWHERE IN THE CONTROL STREAM A~D/OR PROGRAMS
AI.JD STILL BE ASSURED THAT THE RUN AND/OR PROGRAMS
WILL ALWAYS IMMEDIATELY ~ECEIVE THE FACILITY
REQUESTED.
5.5.1.3.

THE FAST RAND

~ASG

STATEMENT

THE FASTRANO IOlASG CONTROL STATEMENT IS USED TO ASSIGN:

FASTRANL)

(MODEL II)

FA5TdANLl
SIMULATED FASTRANLl

(DRUM IS USED AS THE RECORDING DEVICE
BUT THE FILES ARE CALLED AS IF THEY WERE FOR FASTRAND
ALLOCA TI ON)

THE GENERAL FORM OF THE FASTRAND QASG STATEMENT IS:
NAME/KEYI/KEY2,TYPE/RESERVE/GRANULE/MAXIMUM

~ASG,OPTIONS

THE FIELDS OF
OF APPEARANCE

T~IE

ON

STATEMENT ARE EXPLAINED IN SUCCEEDING PARAGRAPHS AND IN THE ORDER
THE STATEMENT.

THE OPTIONS SUd-FIELD IS USED TO CAUSE A FILE TO BE CATALOGUED (OR DECATALOGUED)
AND TO PLACE OR REMOVE CONSTRAINTS ON THE USE OF THE FILE. IT SHOULD BE NOTED THAT
WHEN AN ERROR CONDITION OCCURS WHICH WOULD CAUSE A BATCH RUN TO BE TERMINATED, THE
DEMAND USER RECEIVES AN ERROR MESSAGE AND IS ALLOWED TO SUBMIT A NEW STATEMENT.
CA-TALOGUING OPTIONS ARE AS FOLLOI'IS ':
C

THAT THE FILE IS TO BE CATALOGUED IF THE RUN
TERMINATES NORMALLY. IF A QFREE COMMAND (CONTROL STATEMENT OR EXECUTIVE
kEQUEST) IS ENCOUNTERED FOR THE FILE PRIOR TO TERMINATION, THE FILE IS
CATALOGUED AT THAT TIME (SEE 'THE r.JFREE STATEMENT'). IF A FILE BY THIS
'NAME' ALREADY EXISTS IN THE MASTER DIRECTORY, THE RUN IS PLACED IN THE
ERROR r",OOE.

U

SAME AS 'C' OPTION EXCEPT THAT THE FILE IS TO BE
CATALOGUEU AT RUN TERMINATION REGARULESS OF THE
MANNER OF TERMINATION (BEYOND THIS STATEMENT>. THE
GFRE~ COMMAND MAY CAUSE CATALOGUING PRIOR TO THE
TERto.1I!~A TION.

R

SPECIFIES THAT THE FILE IS TO BE PLACED IN THE
• READ-uNLY' STATE wtlEN IT IS CATALOGUED. THIS OPTION IS MEANINGFUL ONLY
WHEN THE 'C, OH .U' OPTION IS ALSO PRESENT. A FILE CATALOGUED WITH THE tRt
OPTION PRESENT CANNOT BE OVER-WRITTEN. THE FILE CAN ONLY BE READ OR
OECATALOGUED. ANY ACTIVITY REQUESTING TO WRITE IN THE FILE WILL BE pLACED
IN THE ERROR MODE.

P

SPECIFIES THAT THE FILE IS TO BE CATALOGUED AS A
'PUBLIC' FILE RATHEK THAN A, .PRIVATE' FILE. THE
UISTINCTION BETWEEN THEM IS THAT ONLY THE RUNS
<'IHICH HAVE THE SAME PROJECT 10' AS THE RUN WHICH
CREATEU THE FILE CAN ACCESS A tPkIVATE' FILE
WHILE ANY RUN CAN ACCESS A 'PUBLIC' FILE. (FOR
PRIVACY lr-j 'PRIVATE' FILES SEETHE DISCUSSION
CONCERNING TH~ TWO 'KEY' SUU-FIELD51.

w

SPECIFIES THAT THE FILE IS TO BE CATALOGUED
AS A WRITE ONLY FILE. THE FILE CAN ONLY BE WRITTEN INTO, AND IN THE

SPECIFIE~

PROCES~

EXTENO~D.

23

5

SYSTEM

PAGE:

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

5
SECTION:

24
PAGE:

o
THE ABOVE OPTIONS ARE FOR USE ONLY WITH FILES THAT ARE NOT
PRESENTLY CATALOGUED. IF NEITHER OF THE CATALOGUING OPTIONS ('C' AND lUI)
APPEAR, THE FILE, UNLESS CURRENTLY CATALOGUED, IS TREATED AS TEMPORARY AND
RELEASED AT RUN TERMINATION. IT WILL BE RELEASED PRIOR TO RUN TERMINATIoN IF A
~FREE STATEMENT IS ENCOUNTERED.
IN THE ABSENCE OF THE 'PI OPTION, A FILE IS
ALWAYS CATALOGUED AS 'PRIVATE'.
OPTIONS TO BE USED WHEN THE QASG
CATALOGUED ARE AS FOLLOWS:

STATE~ENT

NAMES A FILE THAT IS PRESENTLY

o

SPECIFIES THAT THE CATALOGUED FILE IS TO BE DELETED
FROM THE DIRECTORY(DE-CATALOGUEO) IF THE RUN TERMINATES
NORMALLY OR WHEN A QFREE COMMAND IS ENCOUNTERED PRIOR
TO TERMINATION. THE EXECUTIVE WILL INSURE THE FILE
IS ASSIGNED ONLY TO THIS RUN AT THE TIME OF RELEASE.

K

SAME AS '0' OPTION EXCEPT 7HAT THE FILE IS TO BE
DELETED AT RUN TERMINATION REGARDLESS OF THE MANNER
OF TERMINATION. THE r.lFREE COMMAND l"1AY CAUSE
THE FILE TO BE DE-CATALOGUED PRIOR TO TERMINATION.

x

SPECIFIES THAT THIS RUN IS TO HAVE 'EXCLUSIVE USE' OF
THE FILE UNTIL THE RUN HAS TERMINATED OR THE FILE IS
RELEASED VIA THE QFREE COMMAND. NO OTHER RUN CAN BE
USING THE FILE. (IF THE FILE IS NOT CURRENTLY
CATALOGUED, THE 'X, OPTION IS NOT NEEDED BECAUSE
THE RUN NECESSARILY HAS 'EXCLUSIVE USE').

A

SPECIFIES THAT THE FILE IS CURRENTLy CATALOGUED AND
INSURES THAT THE EXECUTIVE WILL NOT TREAT THE FILE
AS TEMPORARY IF THE NAME CANNOT BE FOUND.
THE RUN WILL ~E TERMINATED IF THE NAME CANNOT BE
FOUND IN THE UIRECTORY.

THE ABOVE OPTIONS ARE TO BE USED ONLY WITH FILES THAT ARE
CURRENTLY CATALOGUED. IF NEITHE~ OF THE DE-CATALOGUING
OPTIONS ('0' OR 'K') APPEAR, THE CATALOGUED FILE IS LEFT
INTACT AT RUN TERMINATION. IF EITHER THE '0' OR 'K'
OPTIONS APPEAR ANU THE FILE HAS EITHER OR BOTH KEYS, THE
KEY(S) MUST BE SPECIFIED, FAILURE TO DO SO CAUSES THE
RUN TO BE PLACED LN THE ERROR MODE.
AN OPTION TO BE USED FOR A TEMPORARY FILE (NOT CATALOGUED AND NOT TO BE
CATALOGUED) IS:
T

SPECIFIES THAT THE FILE IS TEMPORARy AND ALLOWS IT TO
HAVE A NAME THE SAME AS THAT OF A CATALOGUED FILE. NO
THOUGHT NEED ~E GIVEN AS TO WHETHER A FILE BY THIS
NAME IS CURRENTLY CATALOGUED, IF THIS OPTION IS
--NOT-- PRESENT.FOR TEMPORARY FILES, THE
SYSTLM WILL ATTEMPT TO FIND THE FILE IN THE DIRECTORY.
IF A FINU IS MADE, THE ASSIGNMENT WILL BE MADE FROM
THE lIRECTORY.

THE FOLLOWIr;G OPTIONS CONTROL THE DUMPING OF CATALoGUED FASTRAND FILES AT A
CHECKPOINT, AND SUdSEQUENT SYSTEM ACTION ON RESTARTING:
F

JUMP THE FILE AS A PART OF ANY CHECKPOINT.

G

RELOAD THIS ~ILE IF ANY OTHER RUN HAS REFERENCED
THE FILE SINCE THE CHECKPOINT.

H

RELOAD TH I S FILE ONL Y I F NO OTHER RUN liAS

o

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

REFERENCED THE FILE SINCE CHECKPOINT.
M

IF A CATALOGUED FILE BY THIS NAME EXISTS WHEN
RELOADING, MAKE THE RELOADED FILE AVAILABLE
TO nILs RUN AS A TEMPORARY FILE.

N

RENAME THIS FILE UPON RELOADING IF A CATALOGUED
FILE WITH THIS NAME EXISTS.

OPTION F FORCES THE FILE TO BE DUMPED ON A CHECK POINT. WITHOUT ONE OF THE
OPTIONS, G OR H, THE FILE IS ALWAYS RELOADED ON RESTART, OPTIONS M AND N CONTROL THE
MANNER OF RELOAD.
THE FIELD 'NAME' ON THE QASG STATEMENT IS USED TO SPECIFY THE 'EXTERNAL' NAME OF
THE FILE. THE I~AjvlE MUST BE PRESENT AND IS SPECIFIED IN THE NORMAL MANNER:
QUALlFIER*FILE
WHERE THE 'QUALIFIER' AND '*' ARE OPTIONAL AND NEITHER THE 'QUALIFIER' NOR THE 'FILE'
MAY EXCEED 12 CHARACTERS. ALTHOUGH NOT SHOWN ABOVE AN 'F-CYCLE' NUMBER MAY ALSO NEED
TO BE SPECIFIED FOR CATALOGED FILES (SEE SECTION 5.6.1. FOR A MORE DETAILED
U~SCRIPTION OF THE 'EXTERNAL' NAME).

('

25

5
SECTION:

WHEN CATALOGUING, THE SUB-FIELDS 'KEYl' ANa 'KEY2' LOCK A FILE AGAINST
INDISCRIMINATE READING AND WRITING, RESPECTIVELY, BY oTHER USERS. THEY MAY CONTAIN
UP TO SIX CHARACTERS AND ALL CHARACTERS ARE LEGAL EXCEPT THE BLANK, THE SLASH (I),
THE COMMA (,), ANU THE SEMICOLON(I). A FILE IS CATALoGUED WITH ,READ' ANDIOR .WRITE'
LOCK 8Y SPECIFYING THE KEY! ANDIOR KEY2 SUB-FIELDS ALONG WITH THE .C' OR 'U' OPTION.
TO GAIN READ AND/OR WRITE ACCESS TO SUCH A FILE, THE APPROPRIATE KEY(S) MUST BE
SPECIFIED AT ASSIGN TIME OR THE REQUEST(S) WILL NOT BE HONORED. (ONCE THE ASSIGNMENT
HAS BEEN MADE, WITH THE APPROPRIATE KEY(S) MADE AVAILABLE THROUGH THE QASG OR QUSE
STATEMENT, THE KEY(S) NEED NOT BE SPECIFIED IN FURTHER REFERENCES.) IF THE KEY(S)
AKE.KNOWN, A 'LOCKED' FILE CAN BE PARTIALLY OR COMPLETELY 'UNLOCKEO' OR HAVE ITS
K~Y(S) CHANGED BY USING THE FILE UTILITY ROUTINE STATEMENT CREATED FOR THIS PURPOSE
(SECTION 14, 'FILE UTILITY ROUTINES').
A COMBINATION OF THE TWO KEYS IS USED FOR CATALOGUING. THE FOLLOWING TABLE SHOWS
THE ACTION ALLOWED ACCORDING TO THE KEY(S) GIVEN AT CATALOGUING TIME AND THE KEY(S)
GIVEN AT ASSIGN TIME. WHERE 'MESSAGE' APPEARs AS AN ACTION. A 'FAC WARNING
DUOUDODDDDDD' MESSAGE WILL BE PRINTED.
IF A KEY IS FURNISHED ANO IT DOES
NOT MATCH THE CATALOGUED KEY, THE RUN IS ABORTED, AND THE MESSAGE WILL BE .FAC
REJECTED DODODODDDDDDD'.

PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

26

5
SECTION:

PAGE:

KEY(S)
KEY(S) SPECIFIED AT ASSIGN
SPECIFIED
TIME.
AT CATALO-:
GUING TIME: READ : WRITE : BOTH ;NEITHER:

----------:-------:-------:-------:-------:
: READ ;
:

.

READ : WRITE : ABORT : ABORT : WRITE :
___ : _______ : _______ : _______ e _______ :

; READ
WRITE : ABORT : WRITE : ABORT

·

READ :

___ :______ .e---____ :______ _ -------:

80TH ; READ
WRITE: READ
:MESSAGE MESSAGE: WRITE .MESSAGE:

·
-------:-------:-~~----:
.
·
·
NEITHER : ABORT
ABORT : ABORT : READ :
·
---:-------.-------:-------:-------:

·
---:-------

WRITE :

TABLE 5.1

ALLO~ABLE

ACTION ACCORDING TO KEYS

ON ALL QASG STATEMENTS (FASTRAND, MAGNETIC TAPE, ETC.), THE FIELD THAT FOLLOWS THE
NAME FIELO IS CALLED THE 'FACILITIES' FIELD. AS SHOWN PREVIOUSLY, THE FACILITIES
FIELD FOR THE ~ASTRANDgASG STATEMENT IS 'TYPE/RESERVE/GRANULE/MAXIMUM,. IN GENERAL,
IF THE FILE IS CATALOGUED AND TO BE READ, THE ENTIRE FACILITIES FIELD NEED NOT BE
SPECIFIED.

~

THE SUB-FIELD 'TYPE' SPECIFIES THAT THE STATEMENT APPLIES TO FASTRAND FORMAT AND,
IN ADDITION; PQ~NTS OUT THE TyPE OF EQUIPMENT TO BE USED. IF EQUIPMENT TYPE IS
SPECIFIED FOR CATALOGUED FILES, IT IS CHECKED FOR COI>1PATIBILITY. IF NOT COMPATIBLE,
THE STATEMENT IS REJECTED. FOR CATALOGUED FASTRAND FORMAT FILES THE FURNISHED TYPE
MUST AeREE WITH CATALOGUED TYPE. THE-ALLOWABLE TYPES FOR THE FASTRAND QASG STATEMENT
AND ASSOCIATED EQUIPMENT FOR EACH TYPE ARE:
F4
F17
F8
F2
FB
F

FA~TRAND SIMULATED ON FH 432
FASTRAND SIMULATED ON FH 17&2 (OELAYED IMPLEMENTATION)
FASTRAND SIMULATED ON FH 880 IMPLEMENTATION)
FASTRAND .MODEL II
FASTBAND
FASTHAND, TYPE INDEPENDENT

A FILE PLACED ON DRUM SIMULATED FASTRAND HAS ALL THE CHARACTERISTICS OF A FASTRAND
FILE EXCEPT FOR SECTOR PADDING ON WRITE FUNCTIONS. WHEN TYPE F4 OR F8 IS SPECIFIED
AI~O DRUM SPACE IS NOT CURRENTLY AVAILABLE, THE SYSTEM WILL SUBSTITUTE Fe OR F2 FOR
F4, OR F2 FOR Fa. NO SUBSTITUTION IS MADE FOR FASTBAND REQUESTS. CATALOGUING IS
PERMISSIBLE ON ANY HARDWARE TYPE.
RULES FOR FAST RAND FORMAT ALLOCATION REQUESTS

--------------------------------------------:REQUEST : ORDER OF SATISFYING REQUEST
--------------------------------------------F4, F17, F8, F2
F4
F17
F8
F2
F8

F

F17, Fa, F2
Fa,F2
F2
FB
F4, F17, Fa, F2

---------------------------------------------

Q

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

PROGRAMMERS REFERENCE

SECTION:

PAGE:

THE SUb-FIELD 'RESERVE' IS USED TO SPECIFY THE APPROXIMATE NUMBER OF GRANULES TO
BE USED BY THE FILE. THE SUB-FIELD 'GRANULE' IS USED TO SPECIFY THE GRANULE SIZE.
IN CERTAIN CASES, EITHER OR BOTH SUB-FIELDS MAY BE OMITTED. IF THE GRANULE SUB-FIELD
IS SPECIFIED IT MUST CONTAIN EITHER 'TRK' OR 'POS'.
TRK -- SPECIFIES A GRANULE OF ONE TRACK (64 SECTORS)
POS -- SPECIFIES A GRANULE OF ONE POSITION (64 TRACKS)
IF THE GRANULE SPECIFICATION IS OMITTED, THE GRANULE IS ASSUMED TO BE 'TRK'.
GRANULE SUB-FIELD IS IGNORED IF THE FILE IS CURRENTLY CATALOGUED.

THE

THE RESERVE SUB-FIELD IS IGNORED AND NEED NOT 8E SPECIFIED WHEN THE FILE IS
CATALOGUED AND IS 1'0 BE READ ONLY. IF THE FILE IS TO BE CREATED OR UPDATED, THE
R~SERVE MAY CONTAIN AN INTEGER SPECIFYING THE NUMBER OF GRANULES TO RESERVE FOR THE
FILE (ON AN UPDATE THE RESERVE SPECIFICATION INCLUDES THAT PORTION OF THE FILE THAT
ALREADY EXISTS). IF THE RESERVE SPECIFICATION IS OMITTED, NO GRANULES (OR ADDITIONAL
GRANULES) ARE INITIALLY ASSIGNED, THEy ARE ASSIGNED DyNAMICALLY AS NEEDED. WHEN THE
RESERVE IS SUPPLIED BUT EXCEEDED, ADDITIONAL GRANULES ARE ALSO ASSIGNED DYNAMICALLY
AS NEEDED.
NOTE:

WHEN CREATING A FILE, THE RESERVE SUB_FIELD SHOULD
CONTAIN A REASONABLE ESTIMATE OF THE NUMBER OF GRANULES
NEEDED. IF A FILE CAN BE CONTAINED WITHIN THE LIMITS OF
THE KESERVE THE RUN IS ASSURED OF BEING ABLE TO CREATE
THE FILE· WITHOUT DELAY (WITH DYNAMIC EXPANSION, THE
REQUESTING PROGRAM MAY BE REMOVED FROM CORE WHILE
FASTRAND IS BEING MADE AVAILABLE). IN ADDITION, THE
SPECIFICATION OF A RESERVE AIDS THE EXECUTIVE IN
ALLOCATING FASTRAND AREA EFFICIENTLy (IF A RESERVE IS
USED THE TRACK OR POSITIONS WILL BE ADJACENT, IF
POSSIBLE).
fOK MOST EFFICIENT USE OF MASS STORAGE ALL FILES THAT
ARE TO (jE PROGRAM FILES SHOULD BE ALLOCATED UNDER TRACK
GRANULES ('TRK') • A SPECIFICATION OF 'POS' CREATES
UNUSED SPACE IN THE PROGRAM FILE IN THAT 64 CONTIGUOUS
TRACKS WILL BE ASSIGNED •

IF THE FILE TAKES FEWER GRANULES THAN RESERVED, THE EMPTY GRANULES ARE RETURNED TO
THE AVAILABLE STATUS WHEN THE FILE IS CATALOGUED. FURTHERMORE, IF 'POS' IS SPECIFIED
IN THE GRANULE SUB-FIELD AND CONSIDERABLE SPACE IN THE HIGHEST REFERENCED GRANULE HAS
NOT BEEN REFERENCEO, THIS NONREFERENCED SPACE IS PUT BACK INTO THE AVAILABLE POOL AT
'FREE' TIME. THE RESERVE VALUE IS PLACED IN THE DIRECTORY AND WILL BE USED ON FUTURE
UPUATES UNLESS A RESERVE IS SUPPLIED ON THE UPDATE QASG STATEMENT. IN THAr CASE IT
IS USED ANO REPLACES THE PREVIOUS VALUE IN THE DIRECTORY.
THE SUB-FIELD tMAXIMUM' IS USED TO INDICATE THAT THE RUN IS TO BE TERMINATED IF
LENGTH OF THE FILE ~EING C~EATED OR UPDATED EXCEEDS THE NUMBER OF GRANULES
SPECIFIED. THIS FIELD IS USED PRIMARILY TO INSURE THAT A RUN-AWAY-FILE SITUATION
DOES NOT OCCUR DURING DEBUGGING. HOWEVER, IT MAY ALSO BE USED TO OVER-RIDE THE
'SYSTEM-MAXIMUM' FOR ALL FILES, AS SPECIFIED BY THE PARTICULAR INSTALLATION AT SYSTEM
GENERATlON TIME (SEE SYSTEM GENERATION STATEMENTS - MAXIMUM FILE SIZE, AND INITIAL
SYSTEM). THE MAXIMUM SUB-FIELD IS NEVER A REQUIRED SPECIFICATION. IF THE FILE IS
B£ING CREATED OR UPDATED AND A MAXIMUM IS GIVEN, ITS VALUE IS PLACED IN THE DIRECTORY
ALONG WITH THE NAME, TYPE, RESERVE, AND GRANULE SIZE.
Tt~

IF A MAXIMUM WAS SUPPLIED WHEN THE FILE WAS CATALOGUED, ITS VALUE IS RETAINED "AND
USE[) WHEN i\N UPiJATE OCCURS. IF A MAXIMUM IS SUPPLIED ON THE UPDATINGr.JASG STATEMENT,
II IS USEU.
IT IS ALSO PLACED IN THE DIRECTORY, THEREBY REPLACING THE PREVIOUS
tJlAXIMUiJl.
CONSIDER THE FOLLOWING EXAMPLES OF QASG STATEMENTS FOR FASTRAND!

27

5

SYSTEM

UP-4144

Rev. 1

28

5

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

SECTION:

PAGE:

IF THE RUN TERMINATES NORMALLY OR A QFREE STATEMENT
FOH FILEX IS PROCESSED, FILEX wILL BE CATALOGUED
IN THE 'READ-ONLY. MODE. FIVE TRACKS ARE ASSIGNED
INITIAL~Y AND THE 'SYSTEM-MAXIMUM' SIZE IS
ASSUMED AS NO MAXIMUM WAS SPECIFIED.
QASG,O

FILEX/A229~B

FILEX IS CURRENTLY CATALOGUED AND IS TO BE
DE-CATALOGUED IF THE RUN TERMINATES NORMALLY,
THE KEY A2294B IS REQUIRED TO READ THE FILE,
QASG,T

FILEX,F/~/POS/5

FILEX IS A TEMPORARY FILE REQUIRING 4 FASTRAND
POSITIONS TO BE RESERVED INITIALLY. TERMINATION IS
TO OCCUR IF MORE THAN 5 POSITIONS ARE REQUIRED.
fGlASG,X

FILEX,/6118

FILEX IS CURRENTLY CATALOGUED AND THIS RUN IS TO
HAVE 'EXCLUSIVE USE' OF THE FILE FOR UPDATING. A
RESERVE OF 6 THACKS IS SPECIFIED AND THE RUN IS
TO BE TEHMINATED IF MORE THAN 8 TRACKS ARE USED.
DIAGNOSTIC MESSAGES
A GENERALIZED FORMAT IS CURRENTLY USED IN THE PRINT FILE ASSIGNED TO EACH RUN FOR
THE ASG, MODE, CAT, FREE, AND USE STATEMErHS. THE FORMAT IS AS FOLLOWS:
(STATEMENT IMAGE)

1.

FAC REJECTED

DDDDDDDODDDD

(STATEMENT IMAGE)

2.

FAC WARNING

DODDDDDDDDDD

THE FIRST MESSAGE WILL APPEAR FOR A RUN THAT ABORTED DUE TO A STATEMENT. THAT
CANNOT BE HONORED BY THE SYSTEM. THE SECOND MESSAGE IS A WARNING THAT THE STATEMENT
COULD CAUSE A PROBLEM, IN EITHER CASE THE REASON FOR RE.JECTION OR WARNING IS
DETERMINED BY EXAMINING THE BITS SET IN THE OCTAL WORD .bODDDDODDDDD'. (THIS STATUS
WORD IS SET IN AD IF THE STATEMENT WAS PROCESSED BY CSF$.l THE FOLLOWING TABLE
DEFINES THE MEANING OF THE BITS IF SET (l=SETl, BITS ARE NUMBERED 35-0 READING LEFT
TO HIGHT.

-----------.---------------------------------.----.------------:SOURCE :
BIT:-------:
:RUN:CSF:

DESCRIPTION OF MEANING IF SIT SET

-----------.---.---.-.----.------------.-----.----.------.-----35 : K :
: REQUEST NOT ACCEPTED - EXAMINE REST OF BITS AS
: TO WHY.

----:---:---:--------------------------------------------.-----34 : K :
: FIELD ERROR IN STATEMENT OTHER THAN SYNTAX.
: ALSO OPTION

~ONFLICT

'MLH"'OE"

'IB,

----:---:---:--------------------------------------------.------33 : K :
: FILE NAME HAS ALREADY BEEN ASSIGNED TO THIS RUN.
----:---:---:--------------------------------------------.-----32 :
: (RESERVED INTERNAL USE BY F.I.) SET ON FIND IN
----:---

..--:--.-----------------------------------------.------

31 : K :

: DIRECTORY.

: EwUIP TYPE ON ASG STATEMENT IS NOT COMPATABLE

C\
-j

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

: WITH CATALOGUED EQUIP TYPE.

----:---:---:-------------------------------------.------------30 :
: (RESERVED INTERNAL USE BY F.I.), NAME FOUND
: IN ATTACHED NAMES LIST IN PCT

----:---:---:--------------------------------------------.-----.
: 12 CHARACTER NAME IS NOT UNIQUE (THAT PORTION OF
29 : W :
: NAME USED AS INTERNAL NAME FOR I/O PACKETS).

----:---:---:-------------.------------------------------------28 :
: (RESERVED INTERNAL USE BY F.I.). X OPTION
: SPECIFIED ON FILE ALREADY ASG THIS RUN

----:---:---:------------------------------------------------.-.
27 : K : K : READ KEY INCORRECT FOR CATALOGUED FILE

·
----:---:---:--------------------------------------------------26 : K : K : WRITE KEY INCORRECT FOR CATALOGUED FILE.
----:---:---:--------------------------------------------------25 : W :
: WHITE KEY EXISTS IN DIRECTORY, NOT SPECIFIED ON
: ASG STATEMENT (ASSIGNED READ MODE ONLY).

----:---:---:--------------------------------------------------24 : Yi :
: READ KEY EXISTS IN DIRECTORY, NOT SPECIFIED ON
:

ASS

STATEMENT (ASSIGNED WRITE MODE ONLY).

----:---:---:--------------------------------------------------~

READ KEY FUHNISHED ON ASG STATEMENT NONE
: EXISTS IN DIRECTORY.

23 : K : K :

----:---:---:--------------------------------------------------22 : K : K : WRITE KEY FURNISHED ON ASG STATEMENT NONE
: EXISTS IN DIRECTORY.

----:---:---:--------------------------------------------------21 : K :
: 'A' OPTION SPECIFIED ON ASG STATEMENT AND FILE
: NAME WAS NOT FOUND IN DIRECTORY.

----:---:---:--------------------------------------------------: INVALID REEL NUM8ER ON ASG STATEMENT FOR
20 : K :
: CATALOGUED TAPE FILE.

----:---:---:-----------------------------------~--------------19 :
: (~ESERVED INTERNAL USE BY F,I.) MASS STORAGE
: FILE HAS BEEN ROLLED OUT.

----:---:---:--------------------------------------------.-----: (RESERVED INTERNAL USE BY F.l.) REQUEST ON
18 :

· . : wAIT STATUS FOR FACILITIES.
----:---:---:----------------------~---------------------.-._--.
17 :

: K :

: OPTION CONFLICT FOR CATALOGUED FILE, BOTH tDt&tKt
: OR 'CUPRW' WHICH ARE OPTIONS FOR NEW FILES

----:---:---:--------------------------------------------------16 :
: (RESERVED INTERNAL USE BY F,I.) -FILE WAS BEEN
: ASSIGNED EXCLUSIVELY SOME OTHER RUN

----.---:---:-----------------------------------------~--------: (RESERVED INTERNAL USE BY F.l.) FIND MADE IN
15

: DIRECTORY AND ALREADY ASSIGNED

1~

---:---:--------------------------------------------------:
INTERNAL USE BY F.I,) FIND MADE IN
(~ESERVED

: DIHECTORY AND NOT ASSIGNED

13

---:---:--------------------------------------------------K:
: PROJECT 1.0. INCORRECT FOR CATALOGUED ~RIVATE

12

---:---:--------------------------------------------------: (RESERVED INTERNAL USE BY F.l.) EQUIP TyPE

: FILE

: IS TAPEJ IS SET ON FIND OF NAME IN DIRECTORY

----.
--- :.--- :: ---------------------.-------------~---------------(RESERVED INTERNAL USE BY F.I,) READ ONLY
11:

.

: FILE CATALOGUED WITH R OPTION

----:---:---:--------------------------------------------------~
(RESERVED INTERNAL USE BY F.l,) WRITE ONLY
10

: FILE CATALOGUED WITH W OPTION

29

5
SECTION:

PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

5
SECTION:

30
PAGE:

----:---:---:--------------------------------------------.---.-.
9 :
: EQUIPMENT IS DOWN
----:---:---:--------------------------------------------------.
8 :
UNUSED

.

o• :•

----:---:---:--.-----------------------------------------------.
NOTE: K IN RUN OR CSF$ SOURCE
MEANS THAT THE RUN WILL BE TERMINATED
W IN RUN STREAM MEANS THAT A WARNING MESSAGE WILL
BE PRINTED.
5.5.1.4.

THE MAGNETIC TAPE QASG STATEMENT

FOR MAGNETIC TAPE THE FORMAT OF THE QASG STATEMENT IS:
QASG,OPTIONS NAME/KEYI/KEY2,TYPE/UNITS/LOG/NOISE,J
REELI/REEL2/ ••• /REELN
THE 'NAME' FIELD AND THE 'KEY1' AND 'KEY2' SUB-FIELDS ARE THE SAME AS FOR THE
FASTRANO GASG STATEMENT. THE NAME MUST ALWAYS APPEAR.
OPTIONS TO BE USED FOR CATALOGUING ARE:
C
U

P
R

SAME
SAME
SAME
SAME

AS
AS
AS
AS

FOR
FOR
FOR
FOR

FASTRANO
FASTRANO
FASTRAND
FASTRAND

OPTIONS TO BE USED WHEN THE FILE IS PRESENTLY CATALOGUED ARE:

D
K
A

'SAME
SAME
SAME

A~

AS
AS

FOR FASTRAND
FOR FASTRANO
FOR FA~TRANO

THE OPTION TO SPECIFY A FILE AS TEMPORARY IS:
T

SAME AS FOR FASTRAND

THE FOLLOWING OPTIONS 'POOL' FACILITIES WITHIN A RUN WHEN A DYNAMIC FREE OR A
STATEMENT IS ENCOUNTERED:

~FREE

S

HOLD THE PHYSICAL ASSIGNMENT FOR THIS FILE NAME,
I.E., FREE ONLY THE FILE AND SAVE THE UNIT.

THE FOLLOWING OPTIONS, CALLED THE 'MODE OPTIONS" CORRESPOND
TO THE 'MODES' AVAILABLE WITH THE 'SET MODE' FUNCTION OF THE MAGNETIC TAPE HANOLER:
L
M

H
'E

o

B
I

LOW DENSITY
MEDIUM DENSITY
HIGH DENSITy
EVEN PARITY
ODD PARITy
BINARY (NO TRANSLATE)
DECIMAL (TRANSLATE)
HARDWARE IS USED IF AVAILABLE, OTHERWISE THE STANDARD
SOFTWARE CONVERSION ROUTINE IS USEO(BCO TO FIELOATA
ON INPUT AND THE OP,POSITE ON OUTPUT). THE 'E' OPTION
IS ASSUMED ONLY IF SOFTWARE IS USED.

IF THE EQUIPr4ENT 'TYPE'IS NINE-CHANNEL PER FRAME(SEE BELOW), THE DENSITY IS FIXED
AT HIGH, THE PARITY IS FIXED AT ODD, AND ANY ATTEMPT TO CHANGE THESE SETTINGS IS
ILLEGAL. HARDWARE TRANSLATION IS NOT AVAILABLE ON NINE-CHANNEL PER FRAME UNITS.

, . ,,/

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS

REFERENCE

WHEN A FILE IS TO BE CATALOGUED, THE OPTIO~S PLACED IN THE DIRECTORY ARE THOSE
WrlICH WERE IN EFFECT AT THE TIME OF FIRST I/O REFERENCE BY A PROGRAM WITHIN THE RUN
(OTHEI{ THAi~ THE 'SET MODE' REFERENCE).
THE FIELD 'TyPE/UNITS/LOG/NOISE' IS CALLED THE 'F~CILITIES' FIELD AND NORMALLY
DOES NOT HAVE TO BE SPECIFIED IF THE FILE IS CURRENTLy CATALOGUED.
THE SUB-FIELD 'TYPE' IS USED TO SHOW THAT THE gASG STATEMENT IS FOR MAGNETIC TAPE
A SYMBOL DENOTING THE EXACT TYPE OF TAPE UNITS REQUIRED. THIS
SPECIFICATION IS REQUIRED IF THE FILE IS NOT PRESENTLy CATALOGED. IT MAY BE
SPECIFIED, BUT IS IGNORED IF CURRENTLY CATALOGUED. ALLOWABLE TYPES AND THEIR
MtANINGS ARE AS FOLLOWS:
AND C6NTAII~S

T
C
U

8C
6C
4C
3A
2A

TAPE, TYPE INDEPENDENT
UNISERVOS VIIIC, VIC, AND IVC
UNISERV05 VIIIC AND VIC
UNISERVO VIIIC
UNI5ERVO VIC
UNISERVO IVC
UNISERVO IlIA
UNISERVO IIA

THE USE OF TyPE 'T' OR 'C' IS ENCOURAGED AS IT GIVES THE SySTEM MORE FREEDOM IN
ASSIGNING UNITS. WHEN USING TYPE 'T', ONLY THoSE FUNCTIONS AND OPTIONS COMPATIBLE
WITH ALL TYPES OF UNITS MAY BE SPECIFIED.
SOME INSTALLATIONS MAY NOT HAVE '9-CHANNEL/FRAME' CAPABILITIES ON ALL UNITS WHERE
IN ADDITION THERE MAY NOT BE 'TRANSLATION' HARDWARE ON ALL TAPE CHANNELS
WnEHE POSSIBLE. IN ORDER TO SELECT THIS EQUIPMENT, THE CHARACTER '9' OR THE
CHARACTER 'B' MAY BE ADDED TO THE 'TYPE' SYMBOLS TO INDICATE '9-CHANNEL/FRAME' UNIT
OK 'TRANSLATE' CHANNEL, RESPECTIVELY. AS AN EXAMPLE, IF AN VIIIC UNIT WITH
'9-CHANNEL' CAPABILITIES IS NEEDED (BUT NOT AVAILABLE ON ALL 8C UNITS), THE 'TYPE'
SUBFIELD WOULD CONTAIN '8C9'. THE SYMBOL '6Ccl' WOULD CALL FOR A UNISERVO 6C CHANNEL
WITH THE HARDWARE TRANSLATION FEATURE. THE COMBINATION OF TB AND T9 IS NOT
ACCEPTAt'SLE.
POSSl~LE.

THE SYSTEM DOES NOT ASSUME THE TRANSLATE OPTION (I) IF A CHANNEL WITH TRANSLATION
EQUIPMENT WAS REQUESTED. THIS ACTION MUST BE CALLED FOR EITHER ON THE QASG STATEMENT
OR BY USE OF THE 'SET MODE, FUNCTION OF THE MAGNETIC TAPE HANDLER.
THE SUB-FIELD 'UNITS' IS AN INTEGER (1 OR 2) SPECIFYING THE NUMBER OF UNITS
HEQUIRED. IF OMITTED OH AN INTEGER OTHER THAN 1 OR 2 THE NUMBER· OF UNITS IS ASSUMED
T.O 13[ ONE. A fV1AXIMUM OF 2 UNITS PER FILE IS ALLOWED. THE VALUE SUPPLIED IN THE QASG
SfArEMENT IS ALWAYS USED FOR BOTH CATALOGUED AND TEMPORARY TAPE FILES. WHEN 2 UNITS
ARE REQUESTED THEY WILL BE ON A COMMON CHANNEL. THESE UNITS WILL BE THE SAME TYPE.
THE SUu-FIELO 'LOG', IF SPEciFIED, MUST BE A SINGLE LETTER TO INDICATE A 'LOGICAL
CHANNEL'. THE SYSTEM WILL ATTEMPT TO ASSIGN ALL FILES WITH THE SAME LETTER TO THE
SAME PtiYSICAL CHANNEL, THE LETTER IS NOT PLACED IN THE DIRECTORY ON CATALOGUING. ON
RtFERENCING A CATALOGUED FILE, THE LETTER CAN BE SPECIFIED AND WILL BE HONORED IF
PuSSIbLE. SPECIFICATION OF THE 'LOG' SUB-FIELD IS NEVER REQUIRED.
fHE 'NOISE' SUUFIELD IS AN INTEGER IN THE RANGE 1-99 THAT WILL OVERRIDE THE SYSTEM
STANDARD IF PRESPH. THE SYSTEM STANDARD NOISE CONSTANT IS ASSUMED IF THE 'NOISE'
SUBFIELD IS NOT SPECFIEO.
THL FIELO 'HEEL1/REEL2/ ••• /REELN' MAY BE USED TO LIST THE SPECIFIC REELS TO BE
USED AND IS CALLED THE 'REEL' FIELD. THE SUB-FIELDS (REEL1/REEL2/ETC.) CONTAIN REEL
IDENTIFIERS, HEREAFTER CALLED NUMBERS. EACH SUB-FIELD IS LIMITED TO A MAXIMUM OF SIX
ALPHANUMERIC CI1ARACTERS. THE REEL SPECIFICATIONS TAKE ON A PARTICULAR MEANING
UtPENUING ON THE STATUS OF THE FILE:
FILES 8EING CArALOGUED (C OR U OPTION):

31

5
SECTION:

PAGE:

UP-4144

Rev. 1

UNIVAC 110a

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

THE FIELD MAY BE EMPTY THEREBY SPECIFYlNG
THAT THE EXECUTIVE REQUESTS THE OPERATOR TO MOUNT A BLANK
REEL(S) AND SUPPLY THE REEL NUMBER(S) FOR CATALOGUING
THE FIELD MAY CONTAIN THE SPECIFIC REEL NUMBERS IN WHICH
CASE THEY ARE USED AND CATALOGUED IN THE ORDER GIVEN. ALL
GIVEN REEL NUMBERS ARE PLACED lN THE DI~ECTORY, EVEN IF SOME
OR ALL REELS WERE NOT USED. IF ADDITIONAL REELS ARE
REQUESTED (VIA A KEEL SWAP AFTER LAST GIVEN REEL IS USED),
THE SYSTEM WILL THEN ASK FOR BLANK REELS AND INCLUDE THEIR
NUMBERS IN THE DIRECTORY ENTRY.
FILES CURRENTLY CATALOGUED:
NORMALLY THE FIELD WILL BE VOID THUS lNDICATING THAT THE
REELS LISTEO IN THE DIRECTORY ARE TO BE USED IN THE
ORDER IN WHICH THEY WERE CREATED.
IF REEL NUMBERS ARE SUPP(IEU, THEY MUST ~E OF THE SET
LISTED IN THE DIRECTORY, BUT MAY BE A SUBSET AND/OR IN
ANY ORDER, THIS FEATURE ALL'OWS THE USER TO OMIT AND/OR
ACCESS THEM IN ANY ORDER, IF AN INVALID REEL NUMBER
IS SUPPLIED, THE QASG STATEMENT IS NOT HONORED.
IN EITHER OF THE ABOVE CASES (REEL NUMBERS TAKEN IN
ORDER FROM THE DIRECTORY OR TAKEN FROM A SUBSET)
WHEN THE KNOWN REELS ARE EXHAUSTED AND ADDITIONAL REELS
ARE REQUESTED, BLANK REELS WILL BE USED AND THEIR NUMBERS
ADDEO TO THE DIRECTORY. (THIS FEATURE IS NOT ALLOWED IF
THE FILE IS CATALOGUED IN THE 'READ-ONLy, STATE).
FILES NOT CATALOGUED AND NOT TO BE CATALOGUED (TEMPORARY):
IF THE REEL FIELD IS NOT SPECIFIED, THE OPERATOR WILL
BE REQUESTED TO MOUNT BLANK REELS BUT THE REEL NUMBERS
WILL NOT BE REGUIRED FROM THE OPERATOR.
IF REEL NUMBERS ARE GIVEN ON THE QASG STATEMENT, THEY
WILL BE USED IN THAT ORDER, WHEN THE GIVEN REELS ARE
EXHAUSTED AND ADDITIONAL REELS ARE REQUESTED, BLANKS WILL
B~ USED BUT REEL NUMBERS ARE NOT REQUESTED.
WHEN A TAPE ASSIGNMENT IS MADE, THE FOLLOWING INFORMATION IS
MADE AVAILABLE TO THE. ON-SITE OPERATOR:
1,

THE RUN-IO,

2. THE 'FILE' PORTION OF THE 'EXTERNAL' NAME,
3. THE UNIT(S) ASSIGNED.
4. THE INITIAL REEL(S) TO BE MOUNTED.

AS AUDITIOIJAL kEELS ARE NEEDED, ONLY THE UNIT AND REEL NUMBER ARE GIVEN. THE FORMAT
AND INTERPRETATION OF THE· MESSAGES INVOLVED WITH TAPE MOUNTING IS DEFINED IN THE FILE
CONTROL SYSTEM (SECTION 12).
THE FOLLOWING ARE EXAMPLES OF THE USE OF THE QASG CONTROL STATEMENT FOR TAPE
FrLES.
folASG

FILEY
FILEr IS CATALOGUED AND ALL NECESSARY OPTIONS,
FACILITY REQUIREMENTS, AND REEL NUMBERS ARE
TAKEN FROM THE DIRECTORY IF A FIND IS MADE
IN THE DIRECTORY. NOTE: THE PROJECT ID OF THE

32

5
SECTION:

PAGE:

UP-4144
Rev.l

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

5
SECTION:

CUKRENT RUN IS USED AS A QUALIFIER. IF THE NAME
DOES NOT EXIST IN THE DIRECTORy A TEMPORARY
FASTRAND FORMAT FILE IS ASSUMED. (QASG,T FILEY,F)
~ASG,T

FILEY,TII136
FILEY IS A TEMPORARY FILE REQUIRING ONE UNIT
OF THE SYSTEMS CHOOSING, AND ONE OR MORE SCRATCH
REELS WILL BE USED. THE NOISE CONSTANT IS TO
BE SET TO 36 CHARACTERS.

QASG,TEL FILEY,6C/2,N432
FILEY IS A TEMPORARY FILE THAT REQUESTS 2 VIC
UNITS, IT IS TO BE RECORDED IN EVEN PARITY AND
LOW DENSITY. REEL NUMBER N432 IS TO BE USED.
QASG,CR FILEY,8C9
FILEY IS TO BE CATALOGUED IF THE RUN TERMINATES
NORMALLY. ONE VIIIC UNIT WITH ~-CHANNEL/FRAME
CAPABILITIES IS REQUIRED. THE FILE WILL BE
CATALOGUED IN THE 'READ-ONLY' STATE.
QASG,D

(_.
.

FILEY/4AB96,8CIIA,N212
FILEy IS CURRENTLY CATALOGUED BUT IS TO BE
RELEASED WHEN THE RUN TERMINATES NORMALLY. A
KEY OF 4AB96 IS REQUIRED TO READ THIS FILE.
THE ac UNIT IS TO BE ON LOGICAL 'A' AND REEL
N212 IS TO 8E USED.

~\

/

QASG,U

FILEY/492671/RA1234,BC/2,707/70BI709/710

FILEY IS TO ~E CATALOGUED, REQUIRES TWO VIIIC UNITS
ON ANY CHANNEL. REELSS 707, THRU 710
ARE TO BE USED, THE FILE wILL BE LOCKED WITH
THE GIVEN 'READ' AND 'WRITE' KEYS.
QASG,T

FILEY,T,SCRTCH
FILEy IS A TEMPORARY FILE AND THE SYMBOL
'SCRTCH' IS USED AS A REEL NUMBER, WHICH MAY
INDICATE THAT THE OPERATOR SHOULD MOUNT A
SCRATCH HEEL (DEPENDING ON THE INSTALLATION'S
OPERATING CONVENTIONS).

MAGNETIC TAPE UNITS MAY BE ASSIGNED FOR A PARTICULAR CHANNEL
(WITH THE EXECUrIVE CHOOSING THE UNIT) OR A SPECIFIC UNIT CAN BE ASSIGNED. (SPECIFIC
ASSIGNMENT IS NOT RECOMMENDED EXCEPT IN THESE CASES SUCH AS MAINTENANCE ROUTINES,
REAL-TIME PROGRAMS, OR SPECIAL HARDWARE WHICH DICTATES ABSOLUTE ASSIGNMENTS),
A UNIT THAT IS IN A KESERVE STATUS VIA AN UNSOLICITED KEY-IN 'RV' (SEE SECTION
11,3,1.1) IS ONLY ASSIGNABLE BY SPECIFYING THE ABSOLUTE CHANNEL AND UNIT ON THE ASG
STATEi>lENT.
FOR THE. CASE WHERE A PARTICULAR CHANNEL IS SPECIFIED AND THE EXECUTIVE CHOOSES THE
UNIT(S), THE FORMAT OF THE FACILITIES FIELD OF THE TAPE QASG STATEMENT IS:
TY'PE/UNITS

(~.

WhERE .TYPE' SPECIFIES THE CHANNEL BY THE SYMBOL
CXX

33
PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

5

34

SECTION:

PAGE:

')

'.'
C·

WHERE 'XX' IS THE CHANNEL NUMBER (0 TO 15) ANQ 'UNITS' IS THE SAME AS DESCRIBED
EARLIER. CATALOGUING IS THE SAME AS INDICATED EARLIER.
FOR THE CASE WHERE A PARTICULAR UNIT (OR 2 UNITS) IS REQUIRED THE FORMAT IS:
CXX/UYV/UZZ
WHERE .yy. AND 'ZZ' ARE THE UNIT NUMBERS.
CONSIDER THE FOLLOWING EXAMPLES:
~ASG

FILEY,C12/2
FILEY IS ASSIGNED TWO UNITS OF THE SYSTEMS
CHOOSING FROM CHANNEL TWELVE.

QASG

FILEY,CI2/U6,29416
FILEY IS ASSIGNED UNIT 6 ON CHANNEL 12, REEL
29416 IS TO BE USED.

~ASG

FILEY,C12/U6/U4
UNITS 6 AND 4 FROM CHANNEL 12 ARE ASSIGNED TO THE
FILE.

5.5.1.5.

THE DRUM QASG STATEMENT

THE DRUM ~ASG STATEMENT IS USED ONLY WHEN A FILE 'MUST' RESIDE ON A RANDOM ACCESS
DEVICE AND WILL BE BUILT AND READ BY THE USERS DIRECT REFERENCE TO THE MAGNETIC DRUM
HANDLER (SEE SECTION 10.3 ON THE 'MAGNETIC DRUM HANDLER' FOR FUNCTIONS AVAILABLE).
NORMALLY, AS WHEN THE BLOCK BUFFERING PACKAGE OR ITEM HANDLER IS USED, FILES ARE
P~ACED ON QRUM BY USING A FASTRAND gASG STATE~ENT WITH SIMULATED FASTRAND AS THE
tTYPE. ,
FILES SPECIFED BY THE DRUM QASG STATEMENT CANNOT BE CATALOGUED AND ARE TREATED AS
TEMPORARY SCRATCH FILES. THEY ARE RELEASED AT RUN TERMINATION OR WHEN A QFREE
COMMAND IS ENCOUNTERED FOR A PARTICULAR FILE.
THE FORMAT OF THE DRUM gASG STATEMENT IS:
f;;JASG

NAf<1E, TYPE/LOCAT.I ONS

WHERE THE ,NAME' FIELD IS ALWAYS THE SAME AS FOR THE FASTRAND gASG STATEMENT,
SUH-FIELDS ARE NOT AVAI~ABLE SINCE DRUM FILES CAN NOT BE CATALOGUED.

'KEY'

THE 'TYPE' FIELD CONTAINS ONE OF THE FOLLOWING SYMBOLS:
D
04
08
017

DRUM, TYPE INDEPENDENT
FH 432
FH 880
FH 1782
(DELAYED IMPLEMTATION)

TYPE 'D' IS RECOMMENDED AND SHOULD BE USED WHENEVER POSSIBLE SO THAT THE SYSTEM
HAS MORE FREEDOM IN ALLOCATING FILE SPACE.
THE SUB-FIELD 'LOCATIONS' SPECIFIES THE NUf'.1BER OF WORDS NEEDED FOR THE FILE. THE
BE TREATED AS OCTAL IF THE FIRST DIGIT IS A ZERO. AN ERROR STATUS IS
RETURNED TO THE PROGRAM IF IT ATTEMPTS TO REFERENCE OUTSIDE OF THE REQUESTED AREA.

NUM~ER ~ILL

AN EXAMPLE OF A DRUM
gASG

~ASG

STATEMENT WOULD dE:

FILEX,D/2000

- - - - - - - - _ . -----

-----

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

(.
FILEX REQUIRES TWO THOUSAND LOCATIONS ON A
MAGNETIC DRUM OF THE SYSTEMS CHOOSING.
5.5.1.6.

THE ARBITRARY DEVICE QASG STATEMENT

THE ARBITRARY DEVICE ~ASG STATEMENT IS USED TO ASSIGN ALL EQUIPMENT EXCEPT
FASTRAND, DRUM AND MAGNETIC TAPE(SEE RESPECTIVE QASG STATEMENT FORMATS). ITS MAIN
USE IS IN ASSIGNING SPECIAL I/O DEVICES AND COMMUNICATIONS EQUIPMENT IN THAT MOST
STANDARU PERIPHERALS (READERS,PUNCHES,ETC.) NEED NOT BE ASSIGNED SINCE THEY ARE USED
VIA THE SYMBIONT MECHANISM.
THE FORMAT OF THE ARBITRARy DEVICE QASG STATEMENT IS:
QASG,OPTIQNS

NAME,TYPE

THE FIELD 'NAME' GIVES THE 'EXTERNAL' IDENTIFICATION OF THE SELECTED UNIT.
THE 'TYPE' FIELD CONTAINS EITHER:
1.

2.

THE SYM~OLIC NAME OF A CLASS OF DEVICES, WHERE THE
SYSTEM CHOOSES THE UNIT, IF MORE THAN ONE'
AN ABSOLUTE CHANNEL, WHERE THE SYSTEM CHOOSES THE
UNITI OR,

3.

(\

AN ABSOLUTE CHANNEL/UNIT,

SYMBOLIC NAMES OF STANDARD DEVICES OTHER THAN MAGNETIC TAPE AND MASS STORAGE ARE
LISTED 8ELOW. THE USER MUST SELECT THE SYMBOLIC NAMES TO BE GIVEN TO NONSTANDARD
DEVICES AT SYSTEM GENERATION TIME (SEE SYSTEM GENERATION STATEMENTS - CONNECT CHANNEL
AND NAME ASSOCIATION).
CRD
PTP
P
HSP

CARD SUBSYSTEM
PAPER TAPE SUBSYSTEM
PRINTING DEVICE
HIGH SPEEU PRINTER
1004 PRINTING UNIT

1004

AT SYSTEM GEI~ER~TION TIME, GROUPS OF DEVICES, CHANNELS, OR SPECIFIC UNITS MAY BE
GIVEN SYM~OLIC NAMES (SEE SYSTEM GENERATION STATEMENTS - NAME AND C/U ASSOCIATION),
THESE NAMES AkE U~ED IN THE 'TYPE' FIELD TO OBTAIN AN ASSIGNMENT. FOR EXAMPLE,
COMMUNICATIONS DEVICES ARE DEFINEO AT GENERATION TIME AS UNITS UNDER A GROUP (CLASS)
IDENTITY, CALLED ·'THE LT GROUP IDENTITY' (SEE THE SECTION ON 'COMMUNICATIONS
MULTIPLEXOR HANDLER,). THE LT GROUP IDENTITY IS USED IN THE 'TYPE' FIELD AND ~HE
EXECUTIVE CHOOSES THE UNIT.
FOR ABSOLUTE CHANNEL ASSIGNMENT, THE 'TYPE' FIELD CONTAINS THE SYMBOL:
CXX
WHERE 'XX' IS THE CHANNEL NUMBER (0 TO 15).
FOR ABSOLUTE UNIT ASSIGNMENT, THE 'TYPE' FIELD CONTAINS:
CXX/UyY
WHERE 'YY' IS THE UNIT NUMOER.
~ASG

THE STATEMENT:

NAME,C6/U2

CAUSES THE ASSIGNMENT OF UNIT 2 ON CHANNEL 6.
5.5.2.

35

5
SECTION:

THE QMOUE STATEMENT

THE ~MOOE STATEMENT IS USED TO CHANGE THE 'MODE, SETTINGS OF A TAPE FILE. THESE
MOUES ARE SET INITIALLY WHEN THE QASG STATEMENT IS PROCESSED AND MAY ALSO BE CHANGED

PAGE:

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

5
SECTION:

36
PAGE:

")
G
INTERNALLY BY USE OF THE 'SET MODE' FUNCTION OF THE MAGNETIC TAPE HANDLER.
FORMAT OF THE fa1MODE STATEMENT IS:
QMODE,OPTIONS

THE

NAME, NOISE

THE FIELD 'NAME' IS THE SAME AS FOR THE QASG STATEMENT. THE FILE MUST BE
CURRENTLY ASSIGr~EO TO THE RUN (AN QASG STATEMENT WITH THIS NAME MUST PRECEDE THE
QMODE STATEMENT). IF THE FILE IS NOT ASSIGNED (NEVER ASSIGNED OR RELEASED VIA A
~FREE STATEMENT), THE RUN IS PLACED IN THE ERROR MODE.
THE NOISE SUB·FIELD IS ALSO
THE SAME AS FOR THE folASG STATEMENT.
THE 'OPTIONS' FIELD MAY CONTAIN THE FOLLOWING OPTIONS:
L
M
H
E
o
I
B

LOW DENSITY
MEDIUM DENSITy
HIGH DENSITY
EVEN PARITY
000 PARITY
DECIMAL (TRANSLATE)
BINARY (NO TRANSLATE)

WITH THE folMOQE STATEMENT, OPTIONS (MODES) ARE NEVER ASSUMED IN THE ABSENCE OF
OTHERS. THE SPECIFIED OPTIONS ARE NOT PLACED IN THE CATALOGUE SINCE THEY APPLY ONLY
TO THE CURRENT ASSIGNMENT.

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

5

i

SECTION:

PAGE,

('
DIAGNOSTIC MESSAGES
THE GENERALIZED FORMAT AS DESCRIBED IN SECTION 5.5.1.4 FOR THE ASG STATEMENT IS
USED. THE FOLLOWING TA8LE DEFINES THE MEANING OF THE BITS (l=SET) WHEN SET. BITS
ARE NUM~ERED 35-0 READING LEFT TO RIGHT:

--------------------------.-----------------------.------------:SOURCE :
81T:-------:

:RUN:CSF:

DESCRIPTION OF MEANING IF BIT SET

-------------.-.---.---------.--------------------.------------35 : K :
: REQUEST NOT ACCEPTED - EXAMINE REST OF BITS AS
: TO WHY.

----:---:---:--------------------------------------------------.
34 : K:
: FIELD ERROR - NOISE CONSTANT
----:-----:------.-------------------------------------------33 : K:
: NAME NOT IN PCT FOR THIS RUN (FILE HAS NOT BEEN
: ASSIGNED TO THIS RUN)

----: -.--: -.- : --.---------------------.-------------------------.
32 :

: UNUSED

----:---:---:--------------------------------------------------31 : K:
: EQUIPMENT TYPE NOT TAPE FOR FOUND FILE IN PCT
----:-----:-----------------------------------------~--------30
UNUSED

,
,

.
:

18 :

----:-----:--------------------------------------------------17 : K:
: OPTION CONFLICT, ONLY ONE OPTION IN THE FOLLOWING
: 3 GROUPS ALLOWED· (1) 'MLH' (2) 'EO' (3) tBlt

----:--16

,

:

---:--------------------------------------------------UNUSED

o
-----------------------------------------~----------------------

NOTE: K IN SOURCE FIELD MEANS THAT RUN WILL BE TERMINATED
5.5.3.

THE QCAT STATEMENT

CATALOGUING IS NORMALLY DONE IN THE COURSE OF CREATING THE FILE WHERE THE QASG
STATEMENT SPECIFIES THAT THe FILE IS TO BE CATALOGUED. THE CATALOGUING IS DONE WHEN
TrlE RUN TEI1ED TO COMPLETE THE 1-'0 OPERATION.

r~

~i

IN THE MULTI-PROCESSING CONFIGURATION ONE ExEC IN THE SHARED CORE MEMORY OF THE
THE MULTI-PROCESSING EXTENSIONS TO THE 1108 PROVIDE
THE ABILITY TO ISOLATE EACH OF THE AVAILABLE PROCESSORS. EACH IN TURN ACTING AS THE
EXEC PROCESSOR INSPECTS THE LIST OF CURREtJT ACTIVITIES AND SELECTS A TASK TO BE DONE.
ONE PROCESSOR MAY INTERLOCK THE OTHERS WHILE REFERENCING THE CRITICAL AREAS OF COMMON
DATA.

1108 CONTROLS ALL PROCESSING.

THE MANY RUNS oEING INPUT TO THE 1108 EXECUTIVE SYSTEM PROVIDE A NUMBER OF TASKS
TO oE MULTI-PROCESSED. WITHIN ANY RUN, THE INDIVIDUAL TASKS ARE EXECUTED IN A SERIAL
MANNER AS UIRECTED BY THE USER. AMONG THE MANY RUNS, THE EXEC USES THE PROCESSORS OF
THE SYSTEM TO WORK ON TASKS OF MORE THAN ONE RUN.
WITHIN ANY PROORAM, THE EXEC PROVIDES THE ABILITY TO CODE PROCEDURES WlUCH SPLIT A
PROGRAM INTO AN ARBITRARY NUMBER OF INDEPENDENT PATHS, AVAILABLE FOR PROCESSING ON
ANY OF THE PROCESSORS OF THE SYSTEM. SYSTEM JESIGN PROVIDES THE ABILITY TO USE ALL
AVAILABLE PROCESSORS ON THE EXECUTION OF A PARTICULAR PROGRAM. THE EXECUTIVE IS OF
COURSE FREE TO USE THE AVAILABLE PROCESSORS FOR PROGRAM-RELATED BUT INDEPENDENT TASKS
N~CESSARY WITHIN THE EXEC.
THE EXEC ROUTINES INTERFACING WITH THE RESIDENT WOR'KER PROGRAMS ARE RE-ENTRANT IN
FOR MINOR TASKS REQUESTED OF THE EXEC MANy OF THE ROUTINES ARE TOTALLY
HE-ENTRANT. OTHERS, WHEN IN THE MULTI-PROCESSING ENVIRONMENT, WILL QUEUE THE WORKER
PHOGRAM REQUEST WHERE SERIAL PROCESSING IN A PARTICULAR AREA OF THE EXEC IS REQUIRED.
AT THE LOWEST LEVEL, THE EXEC MUST QUEUE INTERRUPTS USING THE DESIGNATED PROCESSOR.
IT MUST ALSO ISSUE 1-0 REQUESTS ON PARTICULAR PROCESSORS ACCORDING TO THE AVAILABLE
H~RDWARE LINKAGES.
ABOVE THIS BASIC LEVEL, ANY OF THE AVAILABLE PROCESSORS CAN
Pt:RFORM A GIVEN TASK, WITH SELECTION BASED ON THE PRIORITY OF THE TASKS CURRENTLY
BEING EXECUTED BY THE PROCESSORS. THE AREAS OF EXEC cODING WHICH REFERENCE COMMON
DATA AND OTHERS WITH SPECIALIZED CODING METHOOS MUST BE PROTECTED FROM SIMULTANEOUS
DESIGI~.

r"i
~

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

7
SECTION:

EXECUTION, BUT MANy'AREAS WILL BE OPEN AND MULTI-PROCESSED AS NECESSARY.
7.~.

SCHEDULING

7.~.1.

GENERAL

TIlE GENERAL SCHEDULING TECHNIQUE USED BY THE EXECUTIVE REMOVES ANY DIFFICULTY IN
THE AOVANCEMENT OF AN INSTALLATION INTO THE USE OF MULTI-PROGRAMMING. THE TECHNIQUE
IS EASILY UNDERSTOOD, AND ANY INSTALLATION CAI~ READILY MODIFY OR EXTEND ITS
CAPABILITI~S IF NECESSARY.
THE SCHEDULING ROUTINES OF THE SUPERVISOR ARE RESPONSIBLE FOR THE CONTROL OF
FACILITIES AS WELL AS TIE ACTUAL SCHEDULING OF RUNS AND TASKS. THIS INCLUDES BOTH
THE ASSIGNMENT ANU RELEASE OF FACILITIES. THERE ARE FIVE ROUTINES WITHIN THE SYSTEM
FOR HANDLIIJG THE SCHEDULING OF RUNS AND THE TASKS WITHIN RUNS. THE IDENTITIES ARE:
F4CILITIES WVENTORY
CONTROL STATEMENT INTERPRETER(CSI)
COARSE SCHEUULER
DYNAMIC ALLOCATOR
CORE CONTENTS CONTROL
EACH ROUTINE IS OISCUSSED INDIVIDUALLy IN THE SECTIONS WHICH FOLLOW.

(-

7.3.2.

FACILITIES INVENTORY

TIlE FACILITIES AT THE DISPOSAL OF THE EXECUTIVE SYSTEM INCLUDE THE INPUT/OUTPUT
CHANNELS, ALL PERIPHERAL EQUIPMENT ATTACHED TO THESE CHANNELS, INCLUDING AVAILABLE
COMMUNICATION LINt TERMINALS AND ALL CORE STORAGE SPACE. AVAILABLE FACILITIES AND
THEIR DISPOSITION ARE INDICATED TO THE SYSTEM AT SYSTEM GENERATION TIME (SEE SySTEM
GENERATIQN STATEMENTS - CONNECT AND DISCONNECT CHANNELS - CORE SIZE, AND INITIAL
SYSTEM); THEREAFT[II, THE EXECUTIVE SYSTEM ASSIGNS THESE FACILITIES, AS NEEDED AND AS
AVAILA~LE, TO FULFILL THE FACILITY REQUIREMENTS OF ALL RUNS ENTERING THE 1108.
THE
EXECUTIVE SYSTE~ MAINTAINS AND CONTINUALLY UPDATES INVENTORY TABLES THAT REFLECT WHAT
FACILITIES ARE AVAILABLE FOR ASSIGNMENT, AND WHICH RUNS ARE USING THE CURRENTLY
UI~AVAILABLE FACILITIES.
AS DEMONSTRATED IN THE FOLLOWING TEXT, THE FACILITIES INVENTORY ROUTINE IS A BASIC
CONSTITUENT OF TilE SCHEDULING SECTION OF THE SUPERVISOR. ONLY BY ESTABLISHING AN
EFFICIENT ANU CONVENIENT .(FOR THE USER) MEANS OF FACILITIES CONTROL IS THE
MULTI-PKOG~AMMING ENVIRONMENT PRACTICAL.
THE ROUTINES CONTROLLING THE FACILITIES
AVAILABLE TO THE 1108 ARE DESIGNED TO OPTIMIZE UTILIZATION OF THOSE FACILITIES WHILE
RE~UIRING A MINIMUM OF USER-GENERATED STATEMENTS CONCERNING OPERATIONAL REQUIREMENTS.
DEVICES SUCH AS MAGNETIC TAPES ARE NORMALLy ASSIGNED BEFORE RUN-EXECUTION TIME,
THEY CANiWT t:)E SHARED BY TWO OR MORE RUNS, AND, SINCE THEY NORMALLY REQUIRE
OPERATOH SET UPS. SUCH DEVICES ARE ALWAYS RELEASED AUTOMATICALLY BY THE TERMINATION
OF THE RUN; HOWEVER THEt MAY ALSO BE RELEASED DURING THE COURSE OF THE RUN BY THE
U5EH.
SIi~CE

MAGNETIC TAPES ARE ALWAYS ASSIGNED WITH THE FOLLOWING RULES OF ALLOCATION.
TYPE DESIGNATIOrJ
ORDER OF SATISFYING REQUEST
T
C
U

8C
6C

'+<:

CB

--------------------------8C,8C8,6C,6C8,8C9,6C9,4C,
4CB,3A,2A.
8C,8CB,6C,6CB,4C,4CB
8C,tlCl::i,6C,6CB
8C,8C8
6C,bCB
4C,4CI:3
8CB,6CB,4CB

3
PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

4

7
SECTION:

PAGE:

UB
8CB,6C8
U9
8C9,6C9
OTHER ,TYPE' MAGNETIC TAPE ASSIGNMENTS DO NOT HAVE A SECOND CHOICE.
(8CB,6CB,4CB,8C9,6C9,3A AND 2A)
BOTH CORE STORAGE SPACE AND MASS STORAGE SPACE (FASTRAND, FH-432, FH-880, ETC) ARE
DYNAMICALLY ASSIGNABLE BY THE EXECUTIVE SYSTEM AND DYNAMICALLy RELEASABLE BY THE
USER. THE ALLOCATION OF CORE SPACE IS DISCUSSED IN A SUBSEQUENT SECTION CALLED 'CORE
CONTENTS CONTROL'. MASS STORAGE SPACE IS TR6ATED MUCH THE SAME AS CORE STORAGE SPACE
BECAU5.E SPACE CAN BE DYNAMICALLY REQUESTED AND RELEASED.
THE USER IS ENCOURAGED TO
00 SO WHENEVER POSSIBLE, SINCE NO RELOCATION OF' INFORMATION IS NECESSARY IN
ALLOCATING MASS STORAGE FACILITIES(AS MAY BE THE CASE FOR CORE STORAGE).
DRUM SPACE IS AVAILABLE IN CONTINUOUS BLOCKS IN ORDER TO ALLOW USERS TO TAKE
ADVANTAGE OF THE HARDWARE CHARACTERISTICS OFFERED BY A WORD-ADDRESSABLE DRUM UNIT
LIKE THE FH.,.432 AND FH-880. THE PORTION OF DRUM SPACE NOT USED IN CONTINUOUS BLOCKS
AND NOT USED FOR SYSTEM RESIDENCE IS THE SIMULATED FASTRAND AREA USED FOR FILE
STORAGE. THIS PERMITS FILES TO BE INDEPENDENT OF DEVICE, THUS RESULTING IN INcREASED
OVERALL EFFICIENCY, BECAUSE FASTER DEVICES CAN BE USED WHENEVER SPACE IS AVAILABLE.
A PORTION OF DRUM IS SET ASIDE AT SYSTEM GENERATION TIME FOR THE RESIDENCE OF THE
SYSTEM AND T~EPROCESSORS (SEE SYSTEM GENERATION STATEMENTS - SYSTEM RESIDENCE -MOVE
PROCESSORS - DIVIDE DRUM). NORMALLY, ALL FILES CREATED BY A'USER ON A DRUM DURING
THE COURSE OF A RUN, ARE PURGED AT THE COMPLETION OF THE RUN, AND THE SPACE USED FOR
SUCH FILES IS RETURNED TO THE POOL OF AVAILABL.E FACILITIES. IF SO SPECIFIED,
HOWEVER, THE FILE MAY BE RETAINED FOR FUTURE REFERENCE.
FASTRAND SPACE IS· NORMALLY ALLOCATED IN GRANULES OF A SINGLE TRACK. THE SINGLE
SECTOR ALLOCATION IS RESERVED FOR SYSTEM USAGE ONLY, BY USE OF THE r.1ASG EXECUTIVE
CONTROL STATEMENT, A USER SPECIFIES THE NUMBER OF GRANULES TO BE INITIALLY RESERVED
FOR THE FILE. EACH DYNAMIC REQUEST FOR ADDITIONAL SPACE WILL THEN RESULT IN THE
ASSIGNMENT OF AN ADDITIUNAL GRANULE. WHEN USING THE SYSTEM FILE .CONTROL ROUTINES,
THE USER WILL NOT HAVE TO REQUEST ADDITIONAL MASS STORAGE SPACE BECAUSE THIS
PROCEDURE IS TAKEN CARE OF AUTOMATICALLY BY THE SYSTEM. FASTRAND SPACE IS TREATED
DIFFERENTLY FROM DRUM SPACE, IN THAT IT MAY BE ASSIGNED ~QR UNLIMITED DURAT.IONS. A
USER'S PROGRAM FILE, FOR INSTANCE, MAY BE FORMED ON A FA~RAND UNIT AND LEFT THERE
INDEFINITELY, WHEREAS USER FILES ON THE DRUM ARE NORMALLY EITHER PURGED AT THE
COMPLETION OF A RUN OR ARE TRANSCRIBED TO FASTRAND.
IN ADDITION TO MAINTAINING COGNIZANCE OF SYSTEM INFORMATION CONCERNING DEVICE
ERRORS, ETC" THE FACILITIES INVENTORY ROUTINE IS ABLE TO ACCEPT DIRECTION FROM AN
OPERATOR CONCERNING DEVICE RELIABILITY, ETC. THE OPERATOR MAY INDICATE WEAK DEVICES,
AND HE MAY REQUEST THAT DEVICES OR CHANNELS BE REMOVED FROM THE POOL OF AVAILA~LE
FACILITIES. THESE CAPABILITIES ARE FURTHER DISCUSSED IN A LATER SECTION.
7~3.3.

CONTROL STATEMENT INTERPRETER(CSI)

THE CONTROL STATEMENT INTERPRETER IS USED BY THE SyMBIONT COMPLEX FOR THE PURPOSE
OF INTERPRETING THE INPUT CONTROL STREAM. IT IS ALSO USED BY THE FUNCTION CSF TO
INTERPRET CONTROL STATEMENT IM~GES PASSED TO THAT FUNCTION INTERNALLY VIA ER CSFS
R£QUESTS. FOR EACH CONTROL STATEMENT IMAGE PASSED TO THE CONTROL STATEMENT
INTERPRETER, CSI PERFORMS THE FOLLOWING MAIN TASKS;
1. FORMAT CHECKS THE STATEMENT
2. REQUESTS CONTINUATION STATEMENTS (CONTINUATION
CHAKACTEK IS TREATED AS AN ILLEGAL CHARACTER
IF REQUEST WAS TO CSF)
3. CHANGES THE EXTERNAL FORMAT OF THE CONTROL
STATEMENT TO AN INTERNALLY FORM~TTED TABLE
ACCEPTABLE TO THE SYSTEM
THE CONTROL STATEMENT INTERPRETER IS THE SINGLE CO",PONENT OF THE SUPERVISOR THAT
r~.
DICTATES THE FORMAT OF THE EXECUTIVE CONTROL LANGUAGE. IF IT BECAME NECESSARY T O " . )
INPUT A CONTROL STREAM UIFFERENT FROM THAT SPECIFIED BY THE EXECUTIVE CONTROL
LANGUAGE, THE CONTROL STATEMENT INTERPRETER COULD BE MODIFIED TO ACCEPT THIS INPUT AS

----

_.

__.. _ - - - - - - - - - - - -

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS

REFERENCE

7
SECTION:

(~::

LONG AS THE INTERPRETATION PRESENTED FUNCTIONS KNOWN TO THE COARSE SCHEDULER AND IN
THE PROPER ORDER ANO GROUPING. THE COARSE SCHEDULER IS THE LEVEL AT WHICH THE
CAPABILITIES AND FUNCTIONS OF THE SYSTEM ARE DEFINED. THE COARSE SCHEDULER SCANS THE
INPUT STREAM VIA ER READ$ REQUESTS IN SEARCH OF THE NEXT LOGICAL TASK OR PARAMETER ON
WHICH IT MUST ACT. IF THE NEXT STATEMENT IS A CONTROL STATEMENT, READ$ ACTIVATES CSI
AND THE INTERNAL TABLE IT BUILDS IS PASSED BACK TO THE COARSE SCHEDULER. FOR DATA
STATEMENTS. THE STATEMENT IMAGE IS PASSED BACK TO THE COARSE SCHEDULER. THE
INTERFACE BETWEEN CSI AND THE SYSTEM IS FIXED. BUT INPUT TO CSI IS FIXED ONLY IN THE
SENSE THAT THE EXECUTIVE CONTROL LANGUAGE IS DEFINED TO BE OF A PARTICULAR FORMAT.
7.3.4.

COARSE SCHEDULER

COARSE SCHEDULING OCCURS AT THE CONTROL STATEMENT LEVEL AND CONCERNS THE
INTRODUCTION OF NEW RUNS INTO THE OPERATING ENVIRONMENT, AS WELL AS CONTINUED
PROCESSING OF PARTIALLY COMPLETED RUNS. THE RESULT OF SCHEDULING IS A QUEUE OF TASKS
MADE AVAILABLE TO THE DYNAMIC ALLOCATOR AS THOSE READY TO BE INTRODUCED INTO THE
OPERATING MIX. THE SYSTEM EXERCISES THE COARSE SCHEDULER WHEN A NEW RUN IS SUBMITTED
OR WHEN A CHANGE IN THE PRIORITY, DEADLINE. OR START-TIME OF EXISTING RUNS IS GIVEN
BY THE OPERATOR. MORE FREQUENT ARE THE INITIATIONS OF SCHEDULING BECAUSE OF PROGRAM
OR TASK TERMINATIONS AND CHANGE IN' PERIPHERAL FACILITY STATUS. ANY.REDUCTION IN THE
TOTAL STORAGE OR FACILITY REQUIREMENTS MIGHT ALLOW A wAITING TASK TO PROCEED.
THE FOLLOWING DISCUSSION CONCERNING COARSE SCHEDULING ASSUMES THAT THE READER IS
FAMILIAR WITH THE EXECUTIVE CONTROL LANGUAGE AND WITH THE SCHEDULING PARAMETERS OF
THE QRUN STATEMENT IN PARTICULAR.
7.3.4.1.

BATCH SCHEDULING

THERE ARE THREE BASIC QUEUES USED BY THE COARSE SCHEDULER IN PROCESSING BATCH
RUNS. THESE ARE:
RUN QUEUE

- QUEUE OF RUNS NOT YET INITIATED.

STATEMENT QUEUE - CONTAINS AN ENTRY AT THE CONTROL
STATEMENT LEVEL FOR EACH INITIATED RUN.
EACH RUN IS NECESSARILY REPRESENTED IN
THIS QUEUE AND THE PARTICULAR STATEMENT
BEING PROCESSED MARKS THE DEPTH TO WHICH
PROCESSING HAS PROCEEDED FOR THE RUN.
THE TASKS WITHIN THIS QUEUE CAN BE IN
VARIOUS STATES. THEY MAY BE IN A WAIT
STATE BECAUSE OF FACILITY REQUIREMENTS.
AS IN THE CASE OF THE QASG STATEMENT. OR
THEY MAY BE REPRESENTED IN THE CORE QUEUE
WHERE THEY ARE CANDIDATES FOR CORE
ALLOCATION AND EXECUTION. MANY TASKS
CAN BE HANDLED ENTIRELY BY THE COARSE
SCHEDULER AND NEVER REACH THE CORE QUEUE.
CORE QUEUE

c

- QUEUE OF TASKS(WORKER PROGRAMS; ETC.>
THAT ARE EITHER READY FOR CORE ALLOCATION
AND EXECUTION OR ARE bEING EXECUTED. THE
~ONTROL STATEMENTS REPRESENTED HERE ARE
A SUBSET OF THOSE IN THE STATEMENT
QUEUE.

THE RUN QUEUE IS INITIALLY BUILT BY THE INPUT SYMBIONTS IN THE COURSE OF
PROCESSING INCOMING RUNS. THE NUMBER OF RUNS CURRENTLY BEING PROCESSED BY THE SYSTEM
IS LIMITED ONLY BY THE MASS STORAGE SPACE AVAILABLE TO HOLD THE INPUT STREAMS.
FOR
EACH RUN IN THE RUN QUELJE. THE COARSE SCHEDULER IS AWARE OF THE FOLLO\'iING SCHEDULING
1 NFORI-1A TION:
PIHOiHTY
DEADLINE

5
PAGE:

I UP-4144

UNIVAC 1108 OPERATING

, Rev.1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

6

7
SECTION:

PAGE:

C;

""I

ESTIMATED RUNNING TIME
START-TIME
ORDER OF RUN SUBMISSION
WITHIN THE STATEMENT QUEUE, EACH ENTRY REPRESENTS THE TASK(ONE OR MORE FUNCTIONS)
TO BE PERFORMED AS A RESULT OF ONE CONTROL STATEMENT INTERPRETATION. THE
TASKS(STATEMENTS) IN THE STATEMENT QUEUE ARE IN ONE OF FOUR STATES:
1, WAITING FOR FACILITIES OTHER THAN CORE.
2. BEING PROCESSED BY THE COARSE SCHEDULER ITSELF--A CASE

WHERE CORE STORAGE IS NOT REQUIRED.

3. REPRESENTED IN THE CORE QUEUE WHERE THEY ARE CANDIDATES

FOR CORE ALLOCATION AND EXECUTION. ALL OTHER FACILITY
REQUIREMENTS HAVE BEEN MET.
4. IN A WAIT STATE FOR SOME OTHER REASON, SUCH AS OPERATOR
ACTION.

AS FACILITIES BECOME AVAILABLE, THE STATEMENT QUEUE IS SCANNED IN PRIORITY ORDER IN
AN ATTEMPT TO SATISFY A STATEMENT THAT IS IN A FACILITY-WAIT STATE. THE FAClLITIES
INVENTORY ROUTINE IS RESPONSIBLE FOR MAINTAINING A LIST OF AVAILABLE FACILITIES, AND
KEYS THE COARSE SCHEDULER WHEN ADDITIONAL FACILITIES BECOME AVAILABLE. IN SOME
CASES, THE COARSE SCHEDULER WILL LOG A REQUEST WITH THE FACILITIES INVENTORY ROUTINE
WHICH WILL AUTOMATICALLY BE HONORED WHEN THE PARTICULAR FACILITY BECOMES AVAILABLE.
IF A DEADLINE RUN IS PRESENT, THE COARSE SCHEDULER WILL IMPOSE A HOLD ON FURTHER
FACILITY ASSIGNMENTS UNTIL SUCH TIME AS THE REQUIREMENTS OF THE DEADLINE RUN HAVE
BEEN MET. IF A PARTICULAR STATEMENT REQUIRES CORE AREA AND ALL OTHER FACILITY
~EQUIREMENTS HAVE BEEN MET, IT IS ALSO PLACED IN THE CORE QUEUE SO THAT IT MAY BE
INT~ODUCED INTO THE OPERATING MIX BY THE DYNAMIC ALLOCATOR.
WHEN THE TASK HAS
TERMINATED, IT IS TURNED BACK TO THE COARSE SCHEDULER FOR POST-PROCESSING.
WHEN ALL OF THE WORK FOR A TASK(STATEMENT) HAS BEEN COMPLETED, THE COARSE
SCHEDULER CALLS Of~ THE CONTROL STATEMENT INTERPRETER FOR FURTHER INTERPRETATION OF
THE CONTROL STREAM, WHICH CAUSES. THE NEXT STATEMENT OF THAT RUN TO BE ADDED TO THE
STATEMENT QUEUE OR THE END-RUN TO BE DETECTED. IN THE LATTER CASE, CLOSEOUT OCCURS.
FURTHER CONTROL STATEMENT INTERPRETATION IS ASSUMED TO BE INSTANTANEOUS. SO, IN THAT
SENSE, ONE STATEMENT FOR EACH RUN IS ALWAYS REPRESENTED IN THE STATEMENT QUEUE.
THE TASKS IN THE CORE QUEUE ARE IN ONE OF THREE STATES AS FAR AS THE COARSE
SCHEDULER IS CONCERNED. THESE ARE:
1. ACTIVE

- IN CORE AND BEING EXECUTED BY THE DYNAMIC
ALLOCATOR.
2. SUSPENDED - PREVIOUSLY ACTIVATED BUT THEN SUSPENDED
FROM CORE BY THE DYNAMIC ALLOCATOR TO CREATE
CORE AREA FOR MORE IMPORTANT TASKS. CAN BE
EXECUTED AGAIN AS SOON AS CORE IS AVAILABLE.
3. READY
- NOT YET INITIATED BUT READY FOR CORE
ALLOCATION AND EXECUTION.
EXCLUDING DEADLINE RUNS FOR A MOMENT, IN CONSIDERING THE RUN QUEUE THE COARSE
SCHEDULER ATTEMPTS TO SELECT A RUN FOR INITIATION ONLY FROM THE GROUP WITH THE
HIGHEST PRIORITY LETTER. WITHIN THIS GROUP, THE RUNS ARE CONSIDERED IN THE ORDER OF
RUN SUBMISSION, WITH SELECTION TAKING PLACE ON THE FIRST RUN WHOSE INITIAL FACILITY
R£QUIHEMENTS CAN BE MET. THE COARSE SCHEDULER wILL ATTEMPT TO OPEN A NEW RUN ONLY
WHEN ALL STATEMENTS OF CU~RENT RUNS ARE REPRESENTED IN THE ACTIVE PORTION OF THE CORE
QUEUE. IN OTHER WORDS, A NEW RUN IS OPENED ONLY WHEN EXECUTION IS PROCEEDING FOR ALL
CURRENTLY OPENED KUNS. THE MORE TASKS THAT CAN BE EXECUTED AT ONCE, THE MORE RUNS
THAT WILL BE OPENED. SINCE THE CORE REQUIREMENTS FOR CONSECUTIVE TASKS WITHIN A RUN
MAY VARY GREATLY, IT IS POSSIBLE THAT FOR A GIVEN SET OF RUNS, ALL CURRENT TASKS
MIGHT 8E ACTIVE AT ONE INSTANCE AND A SHORT TIME LATER MOST OF THE NOW CURRENT TASKS
ARE INACTIVE BECAUSE OF LARGER CORE REQUIREMENTS. IT IS ALSO POSSIBLE THAT BEcAUSE
OF FACILITY REQUI~EMENTS, ONLY A FEW OF THE OPENED RUNS CAN HAVE TASKS pLACED IN THE
READY OR ACTIVE STATE. THE NUMBER OF OPENED RUNS THEN VARIES WITH THE PARTICULAR MIX
OF TASKS AS WELL AS THE FACILITY MESH. WHEN ALL OPENED RUNS ARE PROGRESSING, AN

rf"\
~

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

7
SECTION:

ADDITIONAL RUN IS INITIATED IF POSSIBLE. IF THE INITIAL FACILITY REQUIREMENTS OF
THOSE RUNS OF THE HIGHEST PRIORITY CANNOT ~E MET, RUN SELECTION IS HELD UNTIL A
FACILITY CHANGE OCCURS.
IF IT BECOMES EVIDENT THAT A DEADLINE RUN WILL NOT BE COMPLETED ON TIME VIA THE
NORMAL SCHEDULWG ALGORITHMeVIA THE POWER OF ITS PRIORITY LETTER ONLY), THE RUN IS
INITIAT~D IMMEUIATELY, REGARDLESS OF ITS PRIORITY, AND IF NECESSARY ITS TASKS ARE
GIVEN HIGH PRIORlTY IN THE STATEMENT AND CORE QUEUES. THE ESTIMATED RUNNING TIME OF
THE ACTIVE RUNS IS USED AS A GAUGE AS TO WHEN A DEADLINE RUN SHOULD BE INITIATED.
THE AMOUNT OF CPU TIME AVAILABLE TO BATCH RUNS, AS OPPOSED TO DEMAND AND REAL TIME,
ALSO COMES INTO PLAY.
IN ORDER TO ACCOMMODATE DEADLINE RUNS, THE ,READY' TASKS OF THE CORE QUEUEeTHOSE
ENTERED BY THE COARSE SCHEDULER) FALL INTO ONE OF FOUR CLASSES AS SHOWN BELOW. THE
DYNAMIC ALLOCATOR CONSIDERS THE CLASSES IN THE ORDER SHOWN AND IS RESTRICTED TO
SELECTING FROM THE FIRST CLASS THAT IS NOT VOID.
1. CRITICAL DEADLINE

(-

- THOSE FOR WHICH CORE MUST BE MADE
AVAILABLE lMMEDIATELY, AT THE
EXPENSE OF TEMPORARILY SUSPENDING
OTHER PROGRAMS FROM CORE IF
NECESSARyeEXCLuDING REAL-TIME).
SELECTION IS RESTRICTED TO A
PARTICULAR TASK.

2. SEMI-CRITICAL DEADLINE - THOSE FOR WHICH CORE IS TO BE MADE
AVAILABLE AT THE EXPENSE OF
IMPOSING A WAIT ON FURTHER CORE
ASSIGNMENT UNTIL SUCH TIME AS CORE
IS RELEASED VIA TASK TERMINATIONS.
SELECTION IS RESTRICTED TO A
PARTICULAR TASK.
3. DEA'DLINE

4.

NORfv1AL

THOSE THAT HAVE BEEN DECLARED
'DEADLINE' BUT FROM WHICH THE
DYNAMIC ALLOCATOR IS STILL FREE
TO CHOOSE THE PARTICULAR TASK, FOR
BESt 'CORE-FIT. AND MINIMUM OVERHEAD. SAME AS ABOVE CLASS EXCEPT
SELECTION IS NOT RESTRICTED TO
A PARTICULAR TASK.
- THOSE FROM WHICH THE DYNAMIC
ALLOCATOR IS FREE TO CHOOSE ON A
'BEST-FIT' BASIS, GIVING PREFERENCE TO THOSE ~ITH THE HIGHEST
PRIORITY LETTER IF CORE REQUIREMENTS ARE THE SAME.

A DEADLINE TASK MAY BE FOUND IN ANY ONE OF THE FOUR CLASSES, DEpENDING ON HOW
CRITICAL IT IS. CLASS 4 IS CONSIDERED THE NORMAL WAY IN WHICH TASKS ARE SELECTED FOR
EXECUTION. TASKS MARKED AS REAL-TIME ARE AUTOMATICALLY PLACED IN CLASS 2 UNLESS A
DEADLINE IS ALSO SPECIFIED IN WHICH CASE THEY MAY BE MOVED TO CLASS 1 WHERE CORE AREA
IS I~MEDIATELY ~AOE AVAILASLEeBARRING THE PRESENCE OF OTHER CLASS 1 TASKS). AS AN
EXAMPLE, REAL TIME RUNS MAY HAVE A HIGH PRIORITY, ,A' FOR INSTANCE, IN WHICH CASE
THEY ARE IN A HIGH PRIORITY GROUP FOR RUN INITIATION AND CORE IS ACQUIRED AS SOON AS
If ~ECOMES AVAILABLE VIA OTHER TASK TERMINATIONS. A DEADLINE MAY ALSO BE SPECIFIED
WHICH CAN CAUSE IMMEDIATE RUN INITIATION, ACQUISITION OF FACILITIES FOR THE HIGHEST
PRIORITY IiJ THE STATEMENT QUEUE, AND THE SUSPENSION OF EXECUTING TASKS IN ORDER TO
CREATE CORE SPACE. THE DEADLINE CAN OF COURSE BE APPLIED TO ANY TYPE OF BATCH RUN,
HO~EVER IT SHOULD BE USED WITH SOME FORETHOUGrlT SINCE IT CAUSES INTERRUPTION OF THE
NORMAL SCHEDULING METHODS.
AS

~4ENTIONE;.U

PKEVIOUSLY, THE DYNAMIC ALLOCATOR RETURNS SUSPENDED TASKS TO THE CORE

7
PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

E)(EC B

SYSTEM

PROGRAMMERS REFERENCE

QUEUE FOR L.ATER SEL.ECTION.

7

8
PAGE:

THE SUSPENDED TASKSF.ALL INTO T\'IO CLASSES:

1. SUSPENDED CRITICAL DEADL.INE - SUSPENDED BECAUSE OF REALTIME OR DEADL.INE CORE
EXPANSIONS.
2. NORMAL SUSPENDED
- SUSPENDED FOR ANY NUMBER OF
REASONS (REAL.-TIME, DEADLINE,
DEMAND, AS WELL AS 'NORMAL..
TASK EXPANSIONS).
THE CORE QUEUE THEN IS A SEVEN L.EVEL. QUEUE WITH ONE L.EVEL. TO INDICATE THE ACTIVE
TASKS(NO SELECTION FROM THIS L.EVEL.) AND SIX LEVEL.S FOR THE SIX CLASSES OF TASKS THAT
ARE WAITING FOR ~ORE AL.LOCATION. WHEN THE DYNAMIC ALLOCATOR SELECTS A TASK, IT MUST
BE TAKEN FROM THE L.0WEST NUMBERED LEVEL THAT CONTAINS AN ENTRY.
LEVEL A - ACTIVE
LEVEL 1 - SUSPENDED CRITICAL. DEADLINE
LEVEL 2 - CRITICAL DEADLINE
LEVEL 3 - NORMAL SUSPENDED (INCLUDES THOSE STIL.LCL.ASSED AS
L.EVEL q OR 5)
LEVEL q - SEMI-CRITICAL DEADL.INE
LEVEL 5 - DEADLINE
LEVEL 6 • NORMAL.
WITHIN LEVELS 1~2,4 A~D 5 EACH TASK HAS A SELECTIO~ 'WEIGHT' BAsED ON HOW CRITICAL.
THE RUN'S DEADLINE TIME APpEARS TO THE SYSTEM. THE SELECTION WEIGHT IS SUBJECT TO
CHANGE AS THE DYNAMIC ALLOCATOR (OR COARSE SCHEDULER) PERIODICAL.LY EXAMINES THE
SYSTEM LOAD. AT LEVELS 1,2,AND q, THE DYNAMICAL.LOCATOR IS RESTRICTED TO SELECTING
THE TASK THAT HAS THE HIGHEST 'WEIGHT'. AT L.EVEL. -5 ANY TASHAY-BE SELECTED, WITH
DEADL.INE 'WEIGHT' GIVEN CONSIDERATION IF CORE REQUIREMENTS A THE SAME. A TASK AT
LEVEL.3 OR 6 EITHER HAS NO DEADLINE SPECIFICATION ON ITS RU STATEMENT, OR THE TIME
ALL.OWED TO COMPLETE THE RUN IS SUCH THAT THE DEADLINE SPECIFICATION IS AS YET BEING
IGNORED IN FAVOR OF NORMAL SCHEDULING BASED ON THE PRIORITY LETTER. AS INDICATED
EARLIER, AT THESE L.EVELS THE DYNAMIC ALLOCATOR IS FREE TO CHOOSE, IN PRIORITY-LETTER
ORDER, ANY TASK THAT WILL. ~BEST-FIT' OR CAUSE THE LEAST TASK-SHIFT TO MAKE CORE
AVAILABL.E.
ONCE A TASK HAS BEEN ACTIVATED BY THE DYNAMIC ALL.OCATOR AND SUBSEQUENTLY
TERMINATES, THE TASK'S CORE AREA IS DUMPED TO MASS STORAGE FOR A POSSIBL.E POST_MORTEM
DUMP. IF SNAPSHOT DUMPS WERE TAKEN DURING THE EXECUTION, THE DIAGNOSTIC EDITOR IS
CAL.LED TO PROCESS THEM. IF, DURING THE INSPECTION OF THE CONTROL. STREAM, IOlPMD
STATEMENTS ARE FOUND, THE PMD PROCESSOR IS CALL.ED TO PROVIDE POST-MORTEM DUMPS OF THE
LAST PROGRAM OR PROCESSOR EXECUTED. SEVERAL GPMD STATEMENTS MAY APPL.Y TO A GIVEN
PROGRAM I HOWEVER, THEY MUST BE GROUPED TOGETHER AS THE PMD PROCESSOR GIVES UP CONTROL
WHEN IT READS A NON.PMD STATEMENT (CONDITIONAL STATEMENTS MAY BE INTERL.EAVED WITH
gPMD STATEMENTS AS THEY ARE PROCESSED BY CSI AND NEVER PASSED TO THE PMD PROCESSOR).
7.3.4.2.

DEMAND SCHEDULING

THE COARSE SCHEDULING OF DEMAND RUNS IS SOMEWHAT DIFFERENT FROM THAT OF BATCH
RUNS. IT IS ASSUMED THAT THE READER IS FAMIL.IAR WITH THE PRECEDING SECTION.
AS DEMAND RUNS APPEAR IN THE RUN QUEUE~ THEY ARE INITIATED· IMMEDIATELY. IN THE
COARSE SCH~DULING OF DEMAND RUNS, THE DEADLINE, START-TIME, AND RUNNING TIME ARE OF
NO SIGNIFICANCE AND NEED NOT BE SUBMITlED ON THE IOlRUN STATEMENT. ONLY THE PRIORITY
LETTER, ONE OF THE LETTERS A THRU Z, IS USED. IT IS USED. TO RESOLVE CONFLICTS ON
GAINING EXTERNAL. FACIL.ITY ASSIGNMENTS AND TO GIVE CERTAIN PRIVILEGES IN CPU SWITCHING
IF AN OVERLOAD 51TUATION EXISTS SUCH THAT NOT ALL REMOTE TERMINALS CAN BE GIVEN THE
DESIRED RESPONSE TIME (DISCUSSED IN SEC'ION ON DYNAMIC AL.LOCATOR).
AT A GIVEN TIME, THE DEMAND USER IS IDLE, IN CONVERSATION WITH THE EXECUTIVE ON A

r",

~)

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

CONTROL STATEMENT LEVEL, OR IN CONVERSATION WITH A PARTICULAR CONVERSATIONAL
PROCESSOR OR WORKER PROGRAM ON A SOURCE LINE LEVEL, THIS DISCUSSION IS CONCERNED
MAINLY WITH THE CASE OF THE DEMAND USER BEING CONVERSATIONAL WITH THE SYSTEM ON A
CONTROL STATEMENT LEVEL,
THE PROCEDURES FOLLOWED DURING THE INITIATION AND EXECUTION OF A DEMAND RUN ARE
STRAIGHT FORWARD, THE USER MAKES CONTACT WITH THE INPUT SYMBIONT AND SUBMITS A QRUN
STATEMENT, THE QRUN REQUEST IS PROCESSED BY THE COARSE SCHEDULER AND THE USER IS
FREE TO SUBMIT ANOTHER CONTROL STATEMENT, THE COARSE SCHEDULER IS AGAIN KEYED WHEN
THE NEXT CONTROL STATEMENT HAS BEEN RECEIVED BY THE INPUT SYMBIONT AND THE PREVIOUS
TASK HAS BEEN COMPLETED, IN MOST CASES, AT LEAST FOR THE CONTROL STATEMENT ITSELF,
THE INPUT WILL NOT GO TO MASS STORAGE BUT WILL BE LEFT IN CORE BY THE SYMBIONT FOR
IMMEDIATE ACCESS BY THE COARSE SCHEDULER, SINCE MANY USERS MAY BE SUBMITTING
STATEMENTS AT ONCE, A QUEUE OF CONTROL STATEMENTS(ONE PER DEMAND USER) MAY BUILD UP
AT THE COARSE SCHEDULER LEVEL. THE COARSE SCHEDULER IS EITHER IN THE PROCESS OF
ACTING ON A REQUEST OR STANDING BY FOR THE NEXT STATEMENT TO BE SUBMITTED,
EACH CONTROL STATEMENT SUBMITTED BY THE DEMAND USER IS IMMEDIATELY PLACED IN THE
STATEMENT QUEUE ,(DESCRIBED EARLIER), (ONCE A RUN IS OPENED, DEMAND OR BATCH, IT HAS
AN ACKNOWLEDGED ENTRY IN THE STATEMENT QUEUE, EVEN THOUGH THIS ENTRY SIMPLY MARKS
THAT THE RUN IS IN A WAIT-STATE UNTIL SUCH TIME AS THE NEXT STATEMENT IS
INTERPRETED,) NORMALLY A CONTROL STATEMENT CAN BE SATISFIED IMMEDIATELY (WITHIN A
REASONABLE RESPONSE TIME), AN EXCEPTION TO THIS IS WHEN FACILITIES, SUCH AS MAGNETIC
TAPES, ARE CALLED FOR BUT NOT AVAILABLE, IN THIS CASE THE USER IS NOTIFIED AND CAN
ELECT TO TAKE AN ALTERNATE ACTION OR WAIT UNTIL THE ASSIGNMENT CAN BE MADE, IF MORE
THAN ONE DEMAND RUN IS WAITING FOR THE SAME FACILITY AND THAT FACILITY BECOMES
AVAILABLE, THE ASSIGNMENT IS MADE ACCORDING TO THE PRIORITY LETTERS OF THE DEMAND
RUNS, THE MORE LIKELY CASE, FOR DEMAND MODE RUNS, IS THAT ONLY CORE AND MASS STORAGE
ARE NEEDED IN ORDER TO SATISFY THE ACTION CAL~ED FOR ON THE USERS COMMAND. MASS
STORAGE IS NORMA~~Y AVAILABLE, AND CORE IS ALWAYS AVAILABLE FOR FREQUENT BUT SHORT
PERIODS OF TIME,
FOR BATCH RUNS~ ONCE A TASK IS READY FOR EXECUTION IT IS PLACED IN THE CORE QUEUE
(DESCRIBED EARLIER) WHERE IT IS EXECUTED IN THE GENERA~ MIX OF BATCH TASKS BUT NOT
NECESSARILy IMMEDIATELY OR WITHIN A CERTAIN RESPONSE TIME (EXCEPT FOR DEADLINE JOBS),
FOR DEMAND MODE RUNS, WHEN A TASK IS READY FOR CORE SPACE, IT IS INTRODUCED INTO A
SPECiAL QUEUE CALLED THE CORE-SWAP QUEUE, WHERE IT IS GIVEN CORE SPACE AND CPU TIME
AS SOON AS ITS TURN COMES Up. THIS WILL BE ALMOST IMMEDIATE SINCE EACH TASK IN THE
CORE-SWAP QUEUE IS GIVEN A CONTROLLED AMOUNT OF CPU TIME PRIOR TO BEING INTERRUPTED
AND POSSIBLY SWAPPED OUT TO MASS STORAGE, THERE MAY BE CORE AVAILABLE, OF COURSE,
WITHOUT HAVING TO SWAP OUT OTHER DEMAND TASKS, DEPENDING ON THE CURRENT SYSTEM LOAD.
IT IS ALSO POsSIBLE THAT BATCH JOBS WILL GET SUSPENDED FROM CORE (SUSPENSION BEING
FOR A LONGER PERIOD OF TIME THAN A SWAP) IN ORDER TO MEET THE RESPONSE TIME FOR
DEr"'AND· REQUESTS. NORMALLY HOWEVER, A.SSUMItJG A HEAVY BArCH LOAD, THE TOTAL CORE SPACE
BEING USED BY DEMAND TASKS IS SUPPRESSED AS MUCH AS POSSIBLE AS LONG AS REASONABLE
RESPONSE TIMES ARE BEING MET. IF THE CORE-SWAP QUEUE WERE TO BE EXAMINED, AT ONE
TIME IT MIGHT SHOW ALL TASKS RESIDING IN CORE, AND AT ANOTHER THAT ALL TASKS BuT ONE
HAVE BEEN SWAPPED OUT TO MASS STORAGE, DEPENDING ON THE CURRENT SYSTEM LOAD. THE .
CORE-SWAP QUEUE THEN, SHOWS DEMAND TASKS TO BE IN ONE OF THE FOLLOWING STATES:

c

9

7
SECTION:

1. ACTIVE
- IN CORE AND AVAILABLE FoR EXECUTION,
2, SWAPPED-OUT - PREVIOUSLY ACTIVATED BUT MOMENTARILY
SWAPPED TO MASS STORAGE IN FAVOR OF
ANOTHER DEMAND TASK - BUT CAN BE EXECUTED
AGAIN A.S SOON AS CORE IS MADE AVAILABLE.,
3. READY
- NOT YET INITIATED BUT READY FOR CORE
ALLOCATION. THIS S.TATE IS THE SAME
IN ALL RESPECTS TO THE ,SWAPPED-OUT'
STATE, EXCEPT FOR AN INITIAL~LOAD ..
RATHER THAN ARE-LOAD,
OF THE SWAPPED-OUT TASKS~ ONLY THOSE THAT ARE STILL IN NEED OF EXECUTION ARE
Rt:.PRESENTED IN THE CORE-SWAP QUEUE. AN ADDITIONAL STATE IS THE

PAGE:

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

10

7

PROGRAMMERS REFERENCE

SECTION:

PAGE:

INPUT-WAIT STATE
WHERE THE TASK MAY ALSO BE SWAPPED OUT, BUT
HAVING NOT YET RECEIVED THE NEXT STATEMENT,
INPUT IS RECEIVED, THE TASK IS MOVED TO THE
QUEUE. THE DYNAMIC ALLOCATOR SELECTS TASKS
AS TO BEST MEET USER RESPONSE TIMES,

HAVING REACTED TO THE LAST INPUT AND
IT IS NOT IN NEED OF CPU TIME. WHEN THE
• SWAPPED-oUT. STATE IN THE CORE-SWAP
FROM THE CORE-SWAP QUEUE IN A MANNER SUCH

WHEN THE USER IS IN CONVERSATION WITH A PROCESSOR OR USER PROGRAM, ON A SOURCE
LINE LEVEL, IT IS THE .JOB OF THE DYNAMIC ALLOCATOR AND REMOTE SYMBIONTS TO HANDLE
THESE COMMUNICATIONS (AS OPPOSED TO THE C~RSE SCHEDULER WHEN THE CONVERSATION IS ON
A CONTROL STATEMENT LEVEL). THE DYNAMIC AL~OCATOR CONTROLS THE CPU TIME GIVEN TO A
DEMAND TASK WITH THE IDEA THAT THE TASK WILL REACT (OUTPUT) AND GO INTO A VOLUNTARY
WAIT-STATE UNTIL SUCH TIME AS AN INPUT SOURCE LINE IS RECEIVED. WHEN THE TASK
REACTS, THE DYNAMIC ALLOCATOR NOTIFIES THE OUTPUT SYMBIONT OF THE PRESENCE OF AN
OUTPUT MESSAGE AND HOLDS THE TASK FOR FURTHE:R EXECUTION UNTIL SUCH TIME AS KEYED BY
THE INPUT SYMBIONT THAT AN INPUT MESSAGE IS PRESENT. AT THIS TIME THE TASK IS PUT
BACK INTO THE ACTIVE CYCLE AND GIVEN ITS SHARE OF CPU TIME. THE TIME-SHARED TASK MAY
OH MAY NOT HAVE BEEN SWAPPED OUT PRIOR TO REACTING ANDIOR BETWEEN INTERACTION WITH
THE USER. THE POINT BEING THAT THE COARSE SCHEDULER IS BY-PASSED WHEN THE
CONVERSATION IS NOT ON THE EXECUTIVE CONTROL STATEMENT LEVEL. WHEN THE TASK
EVENTUALLY TERMINATES, THE COARSE SCHEDULER IS PUT BACK INTO PLAY FOR POST-PROCESSING
AND IN ANTICIPATION THAT THE NEXT CONTROL STATEMENT WILL BE FORTHCOMING FROM THE
REMOTE USER, THE NEXT CONTROL STATEMENT COULD CALL FOR THE EXECUTION OF ANOTHER TASK
OR FOR RUN CLOSEOUT.
IT IS IMPORTANT TO NOTE THAT THE DEMAND USER HAS THE ENTIRE SYSTEM AT HIS DISPOSAL
HAS THE SAME CAPABILITIES AS DOES THE BATCH USER, BUT MORE IMPORTANT, THE USE OF
THE SYSTEM IS AVAILABLE .ON DEMAND'.

Ar~D

7.3.4.3.

(._"\!
.~

SUMMARY

IN SUMMARY, THE TASKS (PROGRAMS) OF DEMAND RUNS GET ENTERED INTO THE CORE-SWAP
QUEUE, AS OPPOSED TO THE CORE QU~UE FOR BATCH RUNS. BOTH QUEUES, THE
CORE QUEUE
- FOR BATCH TASKS, AND THE
CORE-SWAP QUEUE - FOR DEMAND TASKS,
ARE BASIC QUEUES USED BY THE DYNAMIC ALLOCATOR IN CONTROLLING CORE SPACE AND CPU TIME
ALLOCATION.
FOR EACH RUN INITIATED (OPENED), THE COARSE SCHEDULER PREPARES A PROGRAM·CONTROL
TABLE (PCT) WHICH IS MAINTAINED DURING THE PROCESSING OF THE RUN. THIS TABLE
CONTAINS CERTAIN FIXED INFORMATION, SUCH AS RUN-ID, ESTIMATED RUNNING TIME, ETC., AS
WELL AS VARIABLE INFORMATION SUCH AS THE CURRENT FACILITIES ASSIGNED, THE CORE
R£QUIREMENTS OF THE PARTICULAR TASK BEING EXECUTED, ETC. THE CONTROL TABLE IS
MAINTAINED BY THE DyNAMIC ALLOCATOR DURING THE EXECUTION OF A TASK, AND RETURNED TO
TI1E COARSE SCHEDULER WHEN THE TASK TERMINATES.
7.3.5.
7.3.5.1.

THE DYNAMIC ALLOCATOR
GENERAL

THE FUNCTION OF THE DYNAMIC ALLOCATOR (DA) IS THE 'DYNAMIC' ALLOCATION OF CPU TIME
AND CORE SPACE TO THE CURRENT MIX OF TASKS (PROGRAMS), . WHERE 'THE CURRENT MIX' IS
DETERMINED BY tHE PARTICULAR GROUP OF RUNS PRESENTLY BEING PROCESSED. IN THE COURSE
OF ALLOCATING CPU TIME FOR COMPUTATION, BASED ON PRIORITY LETTERS, DEADLINE TIMES,
ETC., THE UYNAMIt ALLOCATOR NECESSARILY CONTROLS THE ALLOCATION OF CORE SPACE FOR
EXECUTION, AS WELL AS THE MOVEMENT OF PROGRAMS TO AND FROM MASS STORAGE AS DEMAND
PROGRAMS ARE SWAPPED OR BATCH PROGRAMS ARE SUSPENDED AND SUBSEQUENTLY REINITIATED.
ASSUMING THAT MORE THAN ENOUGH REQUESTS EXIST FOR THE FACILITIES OF THE COMPUTER
(FACILITIES ~EING MAINLY SPACE AND TIME), IT IS THE JOB OF THE DYNAMIC ALLOCATOR TO
MAKE AN EQUITA~LE ALLOCATION OF THESE FACILITIES IN ORDER TO BEST SERVE THE VARIED
IhlTERESTS OF ALL USERS. THE ALLOCATION IS BASED ON THE TYPE OF TASKS (REAL-TIME,

.~~
\~

UP-4144

UNIVAC

Rev" 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS

REFERENCE

7

11

SECTION:

PAGE:

(
DEMAND, AND BATCH), ~S WELL AS ON THE PRIORITIES AND RESPONSE TIMES WITHIN A
PARTICULAR TYPE. THE BASIC IDEA UNDER WHICH THE DYNAMIC ALLOCAToR OPERATES IS THAT
THE PRIMARY CONCERN OF ANY COMPUTING INSTALLATION IS THE COMPLETION OF BATCH RUNS AT
THE REQUIRED DEADLINE (WITHIN THE LIMITATIONS OF THE oPERATING ENVIRONMENT) WHILE AT
THE SAME TIME ATTEMPTING TO MAINTAIN THE REQUIRED RESPONSE TIMES FOR DEMAND USERS.
WITHIN THIS UYNAMIC OPEKATING ENVIRONMENT, THE DIVIDING LINE BETWEEN DEMAND AND BATCH
PROGRAMS IS SUBJECT TO CONSTANT CHANGE AS EMPHASIS IS PLACED UPON ALLOCATING TIME TO
BATCH RUNS APPROACHING THE REQUIRED COMPLETION TIME.
THE DYNAMIC ALLOCATOR PREPARES THE SWITCH LIST USED BY THE DISPATCHER IN GIVING
CONTROL TO PROGRAMS RESIDENT IN CORE AND SWITCHING AMONG THEM AS VARIOUS EVENTS AND
CONTINGENCIES ARISE. THE DA (DYNAMIC ALLOCATOR) PERIODICALLY ADJUSTS THE SWITCHING
LEVEL OF PROGRAMS OR CLASSES OF PROGRAMS SO AS TO FORcE THE CPU TIME TO BE USED IN A
PARTICULAR MANNER BASED ON DEADLINES, PRIORITIES, AND INTERACTION RATES AS WELL AS
CERTAIN OVERALL CONSTRAINTS AS TO HOW CPU TIME SHOULD BE SHARED AMONG THE DIFFERENT
TYPES OF PROGRAMS (DEMAND VERSUS BATCH, FOR EXAMPLE).
THE DA IS STIMULATED BY CHANGES IN THE SYSTEM ENVIRONMENT, AND BY A TIMED INTERVAL
THAT ALLOWS A PERIODIC APPRAISAL OF THE SYSTEM STATUS. EXAMPLES OF ENVIRONMENTAL
CHANGES WHICH CAUSE THE DA TO BE KEYED ARE ACTIONS SUCH AS LISTED BELOW:

(

1. THE COARSE SCHEDULER MADE A NEW TASK AVAILABLE FOR
EXECUTION.
2. AN EXECUTING PROGRAM IS REQUESTING ADDITIONAL CORE
SPACE OR DESIRES TO RELEASE CORE SPACE.
3. THE SYSTEM HAS RECEIVED THE NEXT COMMAND FOR A DEMAND
PROGRAM AND THE PROGRAM IS TO BE CONSIDERED FOR
EXECUTION.
ON A TIMED INTERVAL (OR WHEN KEYED AS ABOVE), THE DA MAY DISCOVER THAT CERTAIN
ADJUSTMENTS MUST BE MADE IN THE WAY CPU TIME (AND/OR CORE SPACE) IS BEING USED.
OF THE CONDITIONS WHICH THE DA DETECTS ARE AS FOLLOWS:

SOME

1. AN ADJUSTMENT MUST BE MADE SO THAT A PARTICULAR BATCH
PROGRAM WILL BE COMPLETED AT THE REQUIRED DEADLINE.
2. THE TOTAL CPU TIME WILL NOT BE SHARED PROPERLY AMONG
THE DIFFERENT TYPES OF PROGRAMS (DEAOLINE BATCH VERSUS
DEMAND, FOR EXAMPLE) UNLESS AN ADJUSTMENT IS MADE.
3. THE RESPONSE TIMES FOR DEMAND USERS wILL DEGENERATE
UI.jLESS AN ADJUSTMENT IS MADE (BECAUSE Of A RECENT CHANGE
IN THE REQUIREMENTS OF OTHER PROGRAMS).
THE DYNAMIC ALLOCATOR STIMULATES OTHER PORTIONS OF THE EXECUTIVE AS CHANGES IN
SYSTEM STATUS OCCUR. FOR" EXAMPLE, THE COARSE SCHEDULER IS KEYED WHEN ALL BATCH TASKS
IN THE CORE QUEUE HAVE ~EEN INITIATED. THIS ALLOWS THE COARSE SCHEDULER THE
OPPORTUNITY TO OPEN A NEW RUN.
7.3.5.2.

c

CORE ALLOCATION

WHEN THE TIME-SHARING OF CORE IS APPROPRIATE, THE DA IS RESPONSIBLE FOR INITIATING
THE CORE SWAP; I.E •• THE WRITING OF ONE PROGRAM TO MASS STORAGE AND REPLACING IT IN
CORE WITH ANOTHER, SO THAT REASONABLE RESPONSE TIMES CAN BE ASSURED. THE DA CALLS ON
THE CORE CONTENTS CONTROL ROUTINE FOR THE MOVEMENT OF PROGRAMS TO AND FROM MASS
STORAGE AS WELL AS FOR THE MAINTENANCE OF THE TABLE REFLECTING THE CURRENT USE OF
CORE "(THE CORE MAP). IN BRIEF. CORE CONTENTS CONTROL (CCC) CONSISTS OF A SET OF
SUBFUNCTIONS FOR CARRYING OUT SPECIFIC OPERATIONS, SUCH AS INITIAL LOADING OF A TASK
OR THE MOVEMENT OF A PROGRAM FROM CORE TO MASS STORAGE. THE OA ASSESSES CORE STORAGE
AND THE SWITCH LIST AND CONSTRUCTS A LIST OF OPERATIONS TO BE EXECUTED BY CCC. THE
OPERATIONS PERFORMED BY CCC FOR THE DA ARE AS FOLLOWS.
1. INITIAL LOAD PROGRAM
2. RELOAD PROGRAM
3. SWAP-OUT PROGRAM
4. RELOCATE PROGRAM
5. EXPAND PROGRAM

iUP-4144
I

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

7
SECTION:

12
PAGE:

o
CORE STORAGE IS ALLOCATED IN A MANNER SIMILAR TO THE ALLOCATION OF CPU TIME BY THE
DISPATCHER. THIS METHOD IS USED TO HELP INSURE THE PROPER USE OF CPU TIME (SEE
SHARING BETWEEN PROGRAM TYPES AND CPU ALLOCATION). EXECUTIVE, ESI. AND REAL~TIME
REQUESTS ARE HONORED BEFORE ALL OTHERS. AND HONORED IN ORDER OF SW!TC·H LIST LEVELS,
DEADLINE REQUESTS ARE THEN HONORED IN ORDER OF DEADLINE WEIGHTS. DEMAND AND BATCH
REQUESTS ARE THEN ATTEMPTED IN ORDER OF S·WITCH LIST \.EVELS.
7.3.5.3.

PROGRAM TYPES

AMONG THE FOUR TYPES OF PROGRAMS, THE PRIORITY ON GAINING PROCESSOR TIME IS AS
SHOWN BELOW.
REAL-TIME TASKS
CRITICAL-DEAQLINE TASKS
DEMAND TASKS
BATCI-l TASKS
THE ABOVE ORDER DOES NOT NECESSARILY REPRESENT THE ORDER IN WHICH THE TYPES OF
PROGRAMS APPEAR ON THE SWITCH LIST. IN PRACTICE, THE TYPES OVERLAP EACH OTHER
DEPENDING ON·SUCH FACTORS AS:
1. AMOUNT OF CPU TIME TO BE GIVEN TO A PARTICULAR CLASS.
2. PRIORITY OF A PROGRAM (OR ACTIVITY) WITHIN A CLASS (TYPE).
3. THE CPU TIME NEEDED BY A PARTICULAR PROGRAM (OR ACTIVITY)
PRIOR TO ITS RELEASING CONTROL FOR I/O ACTION.
THE SWITCH LIST ·IS ORDERED SUCH THAT THOSE PROGRAMS THAT ARE HIGHLY REACTIVElNEED
ONLY SHORT BURSTS BETWEEN I/O REFERENCES) TEND TO HAVE A HIGH PRIORITY REGARDLESS OF
THEIR TYPE, HOWEVER THE DA IS FREE TO REORDER THE LIST SUCH THAT THE AMOUNT OF CPU
TIME GIVEN TO EACH CLASS OF PROGRAMS IS AS SPECIFIED BY THE USER
INSTALLATION(DISCUSSED ~ELOW). A SUCCEEDING SECTION CALLED 'CPU -ALLOCATION'
DESCRIBES THE PLACEMENT OF PROGRAMS AT SWITCHING LEVELS AND POSSIBLE MOVEMENT TO NEW
LEVELS. THE FUNCTIONS OF THE EXECUTIVE ITSELF ALSO APPEAR ON THE SWITCH LIST AND
TtiESE 'EXECUTIVE FUNCTIONS, ARE INTERSPERSED wITH THE FOUR TYPES OF PROGRAMS, THE
SWITCHING PRIORITY OF EXECUTIVE FUNCTIONS RANGE FROM OPERATIONS WHICH ARE AT A HIGHER
PRIORITY THAN REAL-TIME PROGRAMS(MONITORING 1/0 CHANNELS IN E51 MODE, I/O INTERRUPT
QUEUING, ETC.), TO THOSE OPERATIONS WHICH HAVE A PRIORITY JUST ABOVE BATCH
PROGRAMS(SCHEDULING OPERATIONS. SYMBIONT OPERATIONS, ETC.), CONTROL OVER THE SWITCH
LIST BY THE EXECUTIVE(DISPATCHER) IS EXERTED ASA FUNCTION OF TIME (REAL-TIME CLOCK
INTERRUPTS) AND AS A FUNCTION OF PERIP8ERAL DEVICE ACTIVITY(I/O INTERRUPTS),
7.3.5.4,

SHARING BETWEEN PROGRAM TYPES

AS MENTIONED EARLIER THE DYNAMIC ALLOCATOR INSURES THAT CERT~IN OVERALL RULES ARE
ENFORCED AS TO HOW CPU TIME IS SHARED AMONG THE FOUR TYPES OF PROGRAMS. REAL-TIME
PKOGRAMS ARE GIVEN CPU TIME AS NEEDED WITH DEADLINE BATCH, DEMAND, AND BATCH SHARING
THE REMAINDER. ONCE THE DEADLINE TIME OF A BATCH RUN BECOMES CRITICAL, THE TASKS OF
TI1E RUN ARE ASSURED A PERCENTAGE OF THE REMAINING CPU TIME IN ORDER TO SATISFY THE
COMPL.ETION TIME.
NORMALLY, DEMAND PROGRAMS ARE ALLOWED TO OPERATE IN THE tIME REMAINING AFTER
THE REAL-TIME AND EXECUTIVE REQUIREMENTS AND THE TIME NECESSARY TO INSURE
COMPL.ETIONQF CRITICAL DEADLINE RUNS. THIS COULD MEAN THE COMPLETE SUPPRESSION OF
DEMAND RUtJS BY DEADLINE BATCH RUNS UNLESS SOME MINIMUM IS GUARANTEED. THE EXECUTIVE
PROVIDES FUR THE 'SHARING PERCENTAGES, SHOWN BELOW TO BE SPECIFIED At SYSTEM
Gf:.NERATlON TIME (SEE SYSTEM GENERATION STATEMENTS - SHARING PERCENTAGES, AND INITIAL
SYSTEM) AND VIA OPERATOK DIRECTION.
~ATISFYING

DMIN - DEMAND MINIMUM PERCENTAGE
OMAX - DEMAND MAXIMUM PERCENTAGE
THESE VALUES ARE USED BY THE DYNAMIC ALLOCATOR ACCORDING TO THE FOLLOWING RULES:
1. REAL-TIME PROGRAMS - GIVEN CPU TIME AS NEEDED.

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

(
2. CRITICAL DEADLINE - GIVEN THAT PART OF THE REMAINING
TIME NOT GUARANTEED TO DEMAND BY DMIN (SEE BELOW).
3. OEMAND(OMIN) - DEMAND PROGRAMS ARE GUARANTEED A MINIMUM
PERCE~TAGE(DMIN) OF THE TIME REMAINING AFTER REAL-TIME.
THIS INSURES THAT DEADLINE OR NORMAL BATCH "RUNS WILL NOT
COMPLETELY SUPPRESS DEMAND RUNS.
4. DEMAND(DMAX) - DEMAND PROGRAMS ARE GIVEN A MAXIMUM
PERCENTAGE(DMAX) OF THE TIME REMAINING AFTER REAL-TIME,
WHICH WILL BE EXCEEDED ONLY IN THE EVENT"OF OTHERWISE
IDLE TIME. THIS IS ACTUALLY THE DIVIDING LINE BETWEEN
~ATCH AND DEMAND RUNS.
IF SOME MINIMUM AMOUNT OF CPU
TIME IS GIVEN TO EACH CLASS OF PROGRAMS IN THE SWITCH LIST, THIS
GUARANTEES THAT AT LEAST THE HIGHLY REACTIVE PROGRAMS (ACTIVITIES) ARE
GIVEi~ A CHANCE TO FUNCTIONI KEEPING I/O GEAR IN USE, AND IN THE CASE
OF DEMAND RUNS, KEEPING THE HIGHLY CONVERSATIONAL RUNS IN PROGRESS.
THE SPECIFICATIONS DMIN AND DMAX SHOULD BE SET TO BEST MEET THE NEEDS
OF THE PARTICULAR INSTALLATION. AN EXAMPLE FOR A PARTICULAR
INSTALLATION MIGHT BE AS FOLLOWS:
REAL-TIME PROGRAMS WHEN PRESENT USE APPROXIMATELY 20 PERCENT OF THE TOTAL CPU
TIME. DMIN IS SET TO 15 PERCENT OF THE TIME REMAINING, WITH DMAX SET TO 60
PERCENT. WITH THESE SPECIPICATIONS WE SEE THAT IF A CRITICAL-DEADLINE TASK
THAT IS COMPUTE LIMITED WERE TO ENTER THE SYSTEfJi, IT WOULD GAIN A MAXIMUM OF 85
PERCENT OF THE CPU TIME LEFT AFTER REAL_TIME OPERATIONS _ ASSUMING THAT THERE
~ERE ENOUGH DEMAND PROGRAMS TO USE 15 PERCENT.
ON THE OTHER HAND, IN THE
A~SEI~CE OF CRITICAL-DEADLINE RUNS, A HEAVY LOAD OF DEMAND RUNS CAN GAIN NO MORE
THAN 60 PERCENT OF THE CPU TIME AFTER REAL-TIME, ASSUMING THERE ARE ENOUGH
bATCH PROGRAr-'1S TO USE 40 PERCENT.
7.j.5.5.

PROGRAM STATES

THE VARIOUS PROGRAMS CURRENTLY BEING EXECUTED FALL INTO SEVERAL STATES DEPENDING
ON THEIR ABILITY TO ACCEPT CONTROL, OR ON SOME ACTION TAKEN BY THE DYNAMIC ALLOCATOR
IN SUPERVISING THE USE OF CPU TIME. THESE STATES ARE AS FOLLOWS:
1) TERMINATED - PROCESSING BY THE PROGRAM IS COMPLETED, THE ONLY FURTHER ACTION TO
BE UNDERTAKEN IS HOUSEKEEPING BY THE EXECUTIVE AND RECORDING SPECIFIED POST MORTEM
DUMPS FOR FUTURE EDITING AND LISTING.
2) SUSPENDED - PROCESSING BY THE PROGRAM IS CURRENTLY INTERRUPTED TO ACCOMMODATE A
HIGHER PRIORITY JOB, THIS MAY RESULT FROM EXPANSION OF A REAL-TIME PROGRAM,
EXCESSIVELY LONG WAIT USER SPECIFICATION, PRECEDENCE GIVEN TO A MORE URGENT CATEGORY,
ETC. USER SPECIFIED SUSPENSION MUST BE RESUMED BY THE USERI OTHER SUSPENDED PROGRAMS
ARE RESUMED AUTOMATICALLY BY THE EXECUTIVE. TASKS IN THIS STATE MAY STILL BE
RESIDENT IN CORE, HOWEVER THEY ARE NORMALLY THOUGHT OF As BATCH TASKS THAT HAVE BEEN
SUSPENDED FROM CORE OR DEMAND TASKS THAT HAVE BEEN SWAPPED OUT INVOLUNTARILY.
3) WAITING - PROCESSING BY THE PROGRAM IS CURRENTLy INTERRUPTED PENDING COMPLETION
OF AN EXTERNAL EVENT. THIS DIFFERS FROM THE SUSPENDED STATE IN THAT THE INTERRUPTION
IS EXPECTED TO ~E OF A RELATIVELY SHORT DURATION. THE WAIT STATE MAY BE IMPOSED BY
UNSATISFIED I/O REQUESTS, UNSATISFIED INTERNAL REQUESTS FOR ACQUISITION OF FACILITIES
OR OTHER REQUIREMENTS WHICH CANNOT BE IMMEDIATELY RESOLVED.
4) INPUT-WAIT - PROCESSING BY THE PROGRAM IS CURRENTLY INTERRUPTED PENDING
ANALYSIS AND RESULTING ACTION TO BE TAKEN WHEN INPUT IS INTRODUCED ON THE DEMAND
INPUT DEVICE. THE PROGRAM IS NOT A CANDIDATE FOR CPU TIME UNTIL THE INPUT COMMAND IS
RECEIVED. TASKS IN THIS STATE MAY OCCUpy CORE WHILE WAITING FOR THE INPUT COMMAND,
HOWEVER THEY ARE NORMALLY THOUGHT OF AS HAVING BEEN SWAPPED OUT IN ORDER TO
TIr-1E-SHARE CORE wITH OTHER USERS. \

c

13

7
SECTION:

5) ACTIVE - PROCESSING BY THE PROGRAM IS CURRENTLY IN PROGRESS OR CAN BE PLACED IN
PH OGRESS UPON EXAMINATION OF THE QUEUE BY THE SWITCHING FUNCTION.
THE EXECUTIVE MAINTAINS A LIST OF OPERATIONAL PROGRAMS (THE FIVE STATES DESCRIBED

PAGE:

IUP-4144

UNIVAC 1108 OPERATING

I Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

7
SECTION:

14
PAGE:

o
AHOVE) AND SWITCHES CONTROL OF THE COMPUTER BETWEEN THE CURRENTLY ACTIVE PROGRAMS TO
ACHIEVE THE BEST FACILITY UTILIZATION WITHIN THE REALM OF NECESSARY REAL-TIME
RESPONSE AND DESIRED INTERACTION RATES OF THE MIX OF PROGRAMS.
.
7.3.5.6.

TABLES AND QUEUES

IN THE COURSE OF ALLOCATING TIME AND SPACE, THE DYNAMIC ALLOCATOR MAINTAINS NOT
ONLY THE SWITCH LIST BUT ALSO A SET OF TABLES AND QUEUES REFLECTING THE STATE OF ALL
AVAILABLE TASKS, INCLUDING THOSE NOT YET LOADED AND THOSE TEMPORARILY SUSPENDED ON
MASS STORAGE. THE MAIN TABLES AND QUEUES, AND THEIR USES, ARE AS FOLLOWS:
1. SWITCH LIST - USED BY THE DISPATCHER TO SWITCH CONTROL
AMONG TH~ VARIOUS TASKS. MAINTAINED BY BOTH THE DA AND THE
DISPATCHER.
2. CORE QUEUE - USED BY THE DA IN THE COURSE OF SELECTING NEW
OR SUSPENDED BATCH TASKS. MAINTAINED BY BOTH THE DA AND
COARSE SCHEDULER. (DISCUSSED IN COARSE SCHEDULER SECTION).
3. CORE-SWAP QUEUE - USED BY THE DA IN THE COURSE OF SELECTING
NEW OR SWAPPED-OUT DEMAND TASKS.
4. PROGRAM CONTROL TABLE(PCT) - SUPPLIED By THE COARSE
SCHEDULER AND USED BY THE DA TO MAINTAIN THE CURRENT STATUS
OF A TASK AS IT PROCEEDS THROUGH EXECUTION.
5. CORE MAP - USED AND MAINTAINED BY THE DA(VIA THE CORE
CONTENTS CONTROL ROUTINE) IN ALLOCATING CORE SPACE. IT
REFLECTS THE CURRENT USE OF CORE.
6. TIME MAp - CONTAINS ALL HISTORICAL INFORMATION AS TO HOW
THE CPU TIME IS BEING USED. VALUES ARE UPDATED BY BOTH THE
DISPATCHER AND THE DYNAMIC ALLOCATOR. USED MAINLY BY THE
DA IN bECIDING HOW CPU TIME SHOULD bE ALLOCATED IN THE
FUTURE.
7. MASS STORAGE MAP - REFLECTS THE LOCATION OF ALL PROGRAMS
CURRENTLY RESIDING ON MASS STORAGE AS WELL AS THE AREAS
AVAILABLE FOR PLACING ADDITIONAL TASKS. USED BY THE COURSE
SCHEDULER, DYNAMIC ALLOCATOR, AND THE SWAP ROUTINE.
THE DYNAMIC ALLOCATOR SUPERVISES THE USE OF CPU TIME BASED ON HISTORICAL
FOUND IN THE TIME MAP. THE INFORMATION AVAILABLE IN THE TIME MAP IS AS
FOLLOwS:
li~FORMATION

1. THE AMOUNT OF CENTRAL PROCESSOR TIME BEING USED BY EACH
CLASS OF PROGRAMS(REAL-TIME, CRITICAL-DEADLINE, DEMAND, AND BATCH).
AVAILABLE FOR THE LAST 6 SECOND PERIOD AS WELL AS AN AVERAGE OVER SEVERAL
PERIODS.
2. THE CPU TIME USED FOR EXECUTIVE FUNCTIONS, OTHER THAN
THE SWAPPING OF DEMAND TASKS,
:3. IDLE TIME.
4. TOTAL CPU TIME USED THUS FAR BY EACH RUN.
IN ADDITION TO THE ABOVE INFORMATION, THE TIME MAP CONlAINS THE FOLLOWING FIXED
INFORMATION:
1. ESTIMATED RUNNING TIM[(CPU TIME) FOR EACH BATCH TYPE
RUN.
2. D~ADLINE TIME, IF SUPPLIED WITH BATCH RUN.
THE TIME MAP, ALONG WITH ALL OTHER INFORMATION MAINTAINED, ALLOWS THE DA TO MAKE
..JUDGEMENTS AS TO WHETHER ADJUSTMENTS SHOULD BE MADE IN THE SWITCHING PRIORITIES, IN
THE BURSTS OF CPU TIME ALLOWED AT A PARTICULAR PRIORITY, AND IN THE USE OF CORE

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS

REFERENCE

(
STORAGE. FOR EXAMPLE, THE DA MONITORS THE PROGRESS OF A DEADLINE RUN AND, AFTER
MAKING PROJECTIONS B'ASED ON CURRENT INFORMATION, DECIDES WHETHER THE RUN WILL BE
COMPLETlD ON TIME UNDER THE PRESENT CONDITIONS. IF NOT, THE DA MAKES WHAT APPEARS TO
Bl THE NECESSARY ADJUSTMENTS IN THE USE OF TIME AND SPACE, THE RESULTS OF WHICH WILL
BE EVALUATED AT A LATER TIME.
OTHER FUNCTIONS PERFORMED BY THE DYNAMIC ALLOCATOR, BUT NOT SPECIFICALLY MENTIONED
BlFORE ARE:
1. MAINTAINS COMPLETE SUPERVISION OVER THE DEMAND ENVIRONMENT. THIS INCLUDES
COMMUNICATING WITtl THE INPUT/OUTPUT SYMBIONTS, DRIVING THE SWAPPING MECHANISM, AND
MAINTAINING THE STATUS OF RE-ENTRANT PROCESSORS.
2. ACCEPTS UNSOLICITED KEYINS AS TO HOW THE COMPUTER SHOULD BE SHARED AMONG THE
DIFFERENT TyPES OF PROGRAMS AS WELL AS CHANGES IN THE PRIORITY AND/OR DEADLINE OF
PARTICULAR RUNS.
3. RESPONDS TO EXTERNAL INQUIRIES CONCERNING THE PREDICTED OR CURRENT STATUS OF
CURHErn RUiJS.
7.3.5.7.

(

CPU ALLOCATION

AS Ir~DICATEU EARLIER, THE DYNAMIC ALLOCATOR IS RESPONSIBLE FOR BUILDING AND
MAINTAINING THE SWITCH LIST USED BY THE DISPATCHER IN GIVING CONTROL TO
PROGRAMSIACTIVITIESI THAT ARE RESIDENT IN CORE AND ABLE TO ACCEPT CONTROL. THE JOB
OF THE DYNAMIC ALLOCATOR INCLUDES THE PERIODIC RESTRUCTURING OF THE LIST SUCH THAT
DURING TflE NEXT PERIOD, THE DISPATCHER WILL DISTRIBUTE CPU TIME IN THE MOST SUITABLE
MANNER. DURING A GIVEN PERIOD, THE DISPATCHER SWITCHES CONTROL ACCORDING TO THE
'CURRENT' STRUCTUKE OF fHE LIST, ALWAyS GIVING CONTROL TO THE HIGHEST PRIORITY
PROGRAM READY TO RUN. THE SWITCH LIST IS CONSTRUCTED SUCH THAT IN THE COURSE OF
MAKING ADJUSTMENT~, VERY LITTLE WORK MUST BE OO~E BY THE DYNAMIC ALLOCATOR. SWITCH
LIST ENTRIES TflEMSELVES ARE NEVER MOVED, BUT RATHER THE 'POINTERS' TO THE ENTRIES ARE
SIMPLY REORDEREO. IN THE NORMAL CASE, ONLY MINOR ADJUSTMENTS ARE MADE TO THE SWITCH
LIST AT MH OfJE TIi'IE.
Hl OlSCUSSIf'JG THE ALGORITHIIiJS OF THE DYNMHC ALLOCATOR, IT IS ESSENTIAL THAT THE
NATURE OF THE S~ITCH LIST AND THE MECHANICS OF SWITCHING BE UNDERSTOOD. THE READER
IS REFERRED TO SECTION 7~ij, PRIOR TO CONTINUING WITH THIS DISCUSSION. IN BRIEF, THE
S~ITCH LIST IS A N LEVEL LIST WHICH' ALLOwS ANy NUMBER OF ENTRIES AT ANY LEVEL.
LEVEL
1 IS THE HIGHEST PRIORITY LEVEL WITH LEVEL N THE LOWEST, WHERE N 15 A REASONABLE
VALUE. THE DISPATCHER S~ITCHES ACCORDING TO THE FOLLOWING RULES:
1. PHOGI

'-.v'

UP-4144

UNIVAC 110a OPERATING

Rev. 1

EXEC B

SYSTEM
SECTION:

(
CONTINGENCY, THEREBY CAUSING IT TO BE QUEUED WAITING FOR CONTINGENCY ENTRANCE, IN
WHICH CASE A LOCK UP SITUATION OCCURS.
A PROGRAM IS TERMINATED 'IN ERROR' ONLY IF THE LAST EXISTING ACTIVITY TERMINATES VIA
STANDARD CONTINGENCY ACTION,
ESI CONTINGENCY
THE 1108 COMMUNICATION HANDLER PROVIDES THE USER THE CAPABILITY OF PROCESSING
VARIOUS CONTINGENCY CONDITIONS THAT MIGHT OCCUR WHILE EXECUTING UNDER AN ESI
ACTIVITY. TO ESTABLISH AN ESl CONTINGENCY, THE USER REAL-TIME PROGRAM WILL REGISTER
THE CONTINGENCY VIA THE EXECUTIVE REQUEST IALL$. THE CALLING SEQUENCE IS AS FOLLOWS:
L
ER

AO,ADDR
IALL$

WHERE ADDR IS DEFINED

AS FOLLOWS:

-------------------------------------------:APPL : CONTINGENCY ADDR :
---~---------------------------------------HI-APPLICATION SET TO 2 FOR ESI CONTINGENCY.
H2-CONTINGENCY ROUTINE BEGINNING ADDRESS.

(

.~ ...

IT IS NOT NECESSARY FOR THE REAL-TIME PROGRAM TO PROVIDE A SELECTIVE MASK IN THE
ABOVE REFERENCE, AS REQUIRED FOR NON-ESI CONTINGENCY, AS ALL CONTINGENCY TYPES WITHIN
AN E51 ACTIVITY WILL BE PROCESSED BY THE SPECIFIED ESI CONTINGENCY.
THE ESI CONTINGENCY ROUTINE ADDRESS POINTS TO THE BEGINNING OF A TWO WORD PACKET
WHICH WILL CONTAIN PERTINENT INFORMATION CONCERNING THE ESI CONTINGENCY. SAME AS FOR
BATCH AND REAL TIME.
ON THE OCCURRENCE OF AN ESI CONTINGENCY, CONTROL WILL BE GIVEN TO THE LOCATION
PLUS 2. IF THE REAL-TIME PROGRAM DESIRES AN ESI CONTINGENCY, THE ABOVE EXECUTIVE
REQUEST MUST BE EXECUTED PRIOR TO ANY REFERENCE TO THE COMMUNICATION HANDLER.
THERE MAY BE AS MANy ESI ACTIVITIES AS THERE ARE CPU'S IN A SYSTEM. ESI CONTINGENCY
ACTIVITIES FOR A PROGRAM EXECUTE SERIALLY. ONCE AN ESI CONTINGENCY ACTIVITY IS GIVEN
CONTROL, ANY OTHER CONTINGENCY THAT MAY OCCUR ON ANOTHER CPU WILL BE INHIBITED VIA A
LOGICAL TEST AND SET ON Sl OF THE SECOND WORD OF THE CONTINGENCY PACKET. THESE
CONDITIONS EXIST UNTIL THE ESI (CURRENT) CONTINGENCY IS TERMINATED BY EXECUTING AN
EXECUTIVE REQUEST, BY CLEARING THE TEST AND SET INDICATOR, OR BY ALLOWING A TIME OUT.
SHOULD A CONTINGENCY OR TIME-OUT OCCUR WHILE EXECUTING IN THE ESI CONTINGENCY, THE
ESl CONTINGENCY ACTIVITY WILL BE TERMINATED AND THE COMMUNICATION LINE ASSOCIATED
WITH THE CONTINGENCY WILL BE DEACTIVATED FOR INPUT ANDIOR OUTPUT OPERATIONS. TO
ADVISE THE REAL-TIME ACTIVITY OF TERMINAL DEACTIVATION,'THE FIRST REFERENCE TO THE
DEACTIVATE TERMINAL BY THE REAL-TIME PROGRAM WILL CAUSE THE ACTIVITY TO ENTER NON-ESI
CONTINGENCY MODE WITH AN ERROR CODE OF 0710.
TO EXIT FROM AN ES1'CONTINGENCY ACTIVITY, ONLY THOSE EXECUTIVE REQUEST SPECIFIED
FOR NORMAL ESI ACTIVITIES MAY BE USED: EXIT$, ACT$, CADD$, AND ADACT$. ANY REFERENCE
OTHER THAN THOSE INDICATED ABOVE WILL CAUSE A CONTINGENCY WITHIN A CONTINGENCY,
CAUSING TERMINAL DEACTIVATION
THE FORMAT OF THE E5I CONTINGENCY PACKET AND FIELD DEFINITIONS ARE AS FOLLOWS:
35

o
1

2

29

23

17

o

-------------------------------------------------07
ERROR LOCATION
: CODE :CT6 TYPE:
--.---.------------------------------------------TS
: PACKET ADDRESS

--.----------------."------------------------.----CONTROL POINT
WORU-O

25

7

PROGRAMMERS REFERENCE

PAGE:

UP-4144

UNIVAC

Rev. 1

1108 OPERATING

EXEC B

SYST.EM

PROGRAMMERS REFERENCE

26

7
SECTION:

PAGE:

o
S1-ERROR TyPE EQUAL 07.
S2-ERROR CODE
060-INDICATES CONTINGENCY TyPES 1-5.
061-ESI ACT$ OR ADACT$ REQUEST ERROR.
062-ESI CADD$ OR ADACT$ REQUEST ERROR.
063-ILLEGAL ER REQUEST.
064-ESI TIME-OUT.
S3-CONTINGENCY TYPE
1-ILLEGAL OPERATION
2-GUARD MODE
3-FLOATING POINT OVERFLOW
4-FLOATING POINT UNDERFLOW
5-DIVIDE OVERFLOW
012-'ERR MODE', CODES 061-063.
H2-LOCATION OF ERROR OR RE-ENTRY POINT FOR
CONTINGENCY TYPE 012
WORD-l

7.0.

7.6.1.

51-TEST AND SET (TS) INDICATOR.
H2-PACKET ADDRESS FOR A CONTINGENCY TYPE 012

TIMING ROUTINES

GENERAL

WITHIN THE SUPERVISOR, THE TIMING ROUTINES MAKE PROVISIONS FOR THEIR USE BY AN
THESE ROUTINES ARE AVAILABLE TO THE USER BY
MEANS OF EXECUTIVE REQUESTS. THE TIMING ROUTINES SERVE AS THE BASIS FOR ALL
ACCOUNTING AND LOGGING FUNCTIONS, AS WELL AS A SOURCE OF CONTROL FOR MANY REAL_TIME
APPL.lCA HONS.

Ob~ECT PROGRAM AS WELL AS BY THE SYSTEM.

7.6.2.

REAL-TIME CLOCK

THE REAL-TIME CLOCK ROUTINE IS USED BY THE SySTEM FOR TIMING VARIOUS ACTIVITIES
SUCH AS INPUT/OUTPUT FUNCTIONS. OPERATOR RESPONSES. CPU USAGE TIME FOR EACH RUN.
THIS ROUTINE IS ALSO USED BY THE SYSTEM TO FORCE INTERRUPTS AFTER VARIABLE AMOUNTS OF
TIME SO THAT SUCH EVENTS AS NON-RESPONSIVE I/O DEVICES, UNBALANCED USAGE OF CPU TIME,
ETC. ARE UETECTED. THE FREQUENCY OF INTERRUPT DtPENDS ON THE NEEDS OF THE SYSTEM.
THE ROUTINE IS SO DESIGNED THAT MANY EVENTS MAY BE SIMULTANEOUSLY TIMED, AND MANY
INTERRUPTS MAy BE SIMULTANEOUSLY REQUESTED. SINCE ONLY ONE REAL-TIME CLOCK AND ONE
CLOCK INTERRUPT ARE AVAILABLE ON THE 1108, THE REAL TIME CLOCK ROUTINE ESSENTIALLY
ACTS AS A MULTIPLEXOR AND CREATES AN ENVIRONMENT SUCH THAT ANY ROUTINE MAY OPERATE AS
THOUGH IT HAD EXCLUSIVE ACCESS TO THE REAL-TIME CLOCK AND TO THE ASSOCIATED
INTERRUPT.
7.6.3.

DAY CLOCK

TliE DAY CLOCK ROUTINE IS USED BY THE SYSTEM TO MAINTAIN AN ACCURATE, STANDARD
TIME. THIS TIME IS USED BY ALL PROCESSORS FOR ANNOTATING LISTINGS, BY THE FILE
CONTROL SUPERVISOR FOR MAINTAINING HISTORICAL INFORMATION ABOUT ALL FILES, BY THE
ACCOUNTING AND LOGGING ROUTINES FOR TIME-TAGGING EVENTS, AS WELL AS, tlY OTHER
ROUTINES FOR OTHER FUNCTIONS.

/-~

l_~

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

(
LOGGING

A~O

ACCOUNTING

AN EXTENSIVE LOGGING SYSTEM IS MAINTAINED FOR COLLECTING INFORMATION PERTAINING
TO EACH RUN AND PHOGRAM. THE INFORMATION LOGGED IS LATER USED FOR ACCOUNTING AND
POST-EXECUTION pUHPOSES. A SUMMARY ACCOUNTING LOG IS UPDATED THROUGHOUT ALL RUNS.

• ••••••••••••••••
CONSOLE MESSAGES:

·
• ••••••••••••••••·
I/O ERROR LOG
• ••••••••••••••••
COARSE SCHEDULER:·
• ••••••••••••••••

SYMBIONTS

, ............... .
· ·....... ,
·............... .· ·••••••••.

·

CONTINGENCY
• ••••••••••••••••
FACILITY USAGE
• ••••••••••••••••

·........... .
·.. , ........ .

• ••••••••••••
: TEMPORARy
ER FUNCTIONS
: •• >:LOG
:.>:MASTER
: (FASTRANO)
•••••••••••••••• :
:cONTROL: :RUN LOG
USER(BY ER CSF$):
•
• ••••••••••••
TEKMINATlON

·., ............. .·
·

.

:ACcOUNTING :
:ROUTlNE

·
•:RUN
•••••••••••

•:MASTER
••••••••:

:PRINT
:FILE

:RUN LOG:

27

7
SECTION:

·., ........ .
:SUMMARY
: ACCOUNTING:
:FILE

....... . ·•••••••••••.
·., ........ . ·(FASTRAND
(FASTRAND)
OR TAPE)
•

PAGE:

UNIVAC 1108 OPERATING

UP-4144

EXEC B

Rev. 1

7.7.1.

SYSTEM

PROGRAMMERS REFERENCE

" 7

28

SECTION:

LOG CONTROL

TUIS FUNCTION OF THE 1108 EXEC CONTROLS THE FLOW OF ALL LOGGING INFORMATION
GENERATED BY THE VARIOUS EXEC FUNCTIONS AND BY THE USER PROGRAM. uSER REQUESTS ARE
GRANTED THROUGH THE CONTROL STREAM QLOG STATEMENT AND THE EXECUTIVE ENTRANCE CSF$ •
EACH EXECUTING RUN IS ASSIGNED A CORE LOG BUFFER. AS EACH BUFFER IS FILLED, THE LOG
CONTROL ROUTINE CHAINS THE NEW BLOCK OF INFORiJiATION BY RUN IN THE TEMPORARY MASTER
RUN 1..0G.
7.7.2.

RUN TERMINATION ACCOUNTING

AT EACH RUN TERMINATION, THE SUMMARY ACCOUNTING ROUTINE IS ACTIVATED. APPLICABLE
IN THE PROGRAM CONTROL TABLE AND THIS RUN'S ENTRIES IN THE TEMPORARY RUN
1..0G ARE COL.LECTED.
INFORMATION wHICH PERTAINS TO A RUN IS PLACED AT THE END OF THE PRINT FILE. THE
FOLLOWING INFORMATION IS AVAILABLE FOR THE REQUESTOR OF THE RUN:
INFORMATIOr~

RUN IDENTITY
CONTROL LANGUAGE LOG STATEMENTS
CONSOLE MESSAGES PERTAINING TO THE RUN
EXECUTIVE REQUEST L.OG MESSAGES
PROJEC'T IOENT ITY
ACCOUNT NUMBER
TOTAL RUN TIME
PAGES OF PRINTING ApPLICABLE TO THE RUN
NUMBER OF CARDS READ IN AND PUNCHED OUT
TIME ANU DATE OF RUN INITIATION
A CONSECUTIVE GROUP OF BLOCKS ARE WRITTEN TO THE MASTER LOG. ALL INFORMATIoN
COLLECTED IS SAVED IN SEQUENCE WITH THE ORDER OF EVENTS DURING THE RUN.
THE ACCOUNTING ROUTINE THEN READS ANe UPDATES AL~ TOTALS MAINTAINED. THE NUMBER
OF RUNS IS INCREMENTED. CURRENT TIME AND DATE ARE RECORDED. THIS SUMMARY GIVES FOR
EACH ACCOUNT A TOTAL FACILITY USAGE UPON WHICH A BILLING MAY BE MADE.
7.7.3.

("\
\~~~/

BILLING

HiE ACCOUNTING FILE IS PERMANENTLY ASSIGNED AS A FASTRAND FILE. CONTINUING TOTALS
ARE KEPT UNTIL CLEARED ~Y THE BILLING ROUTINE oR THE FILE IS REPLACED DURING SySTEM
LOADING. A PROCEDURE FOR EXECUTING THE BILLING ROUTINE MUST BE ESTABLISHED BY THE
USER.
THE BILLING ROUTINE SUPPLIED IS INTENDED FOR USE AS A BASE FOR AN INSTALLATION,S
OWN UNIQUE BILLING PROGRAM. THE FORMAT FOR OUTPUT IS VERY SIMPLE IN THE ROUTINE
SuPPLIED. THE PRIMARY PURPOSE IS TO PERFORM THE EXECUTIVE RELATED FUNCTIONS
l~cCESSARY FOR PROPlR ACCOUNTING FILE MAINTENANCE.
THE ROUTINE PERFORMS THE FOLLOWING
FUNCTIONS:
EACH ENTRY IN THE ACCOUNT FILE.
WHILE THE FILE IS LOCKED OUT FROM SUMMARY ACCOUNTING, RESET EACH ITEM TO THE
C~EARED STATE.
PRINT EACH TOTAl.. FOR THE VARIOUS FACILITIES USED BY THE ACCOUNT.
FI..AG EACH ENTRY WHICH HAD BEEN ADDEO THROUGH OPERATOR ACTION. GIVE THE DATE ON
WHICH THE ITEM WAS ADDED.
TOTAL EACH ENTRY TYPE FOR AL~ ACCOUNTS.
PRINT A SUMMARY FOR THE ENTIRE SYSTEM USAGE SINCE THE PREVIOUS BILLING RUN. THIS
INCLUDES TOTAL RUNS PROCESSED, TIME CHARGED, AND PERIPHERAL USAGE.
R~AD

EXECUTIVE TIME AND FACILITY USAGE IS LOGGED UNDER THE ACCOUNT MAINTAINED FOR EXEC.
THE TOTALS APPEAR ~UST AS IF THE EXEC ~AS A USER PROGRAM.

o

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM
SECTION:

MASTER RUN LOG

7.7.~.

THE MASTER RUN LOG MAINTAINS ALL INFORMATION IN 22~ WORD BLOCKS. EACH BLOCK
CONTAINS EIGHT 28-WORD LOG ENTRIES. THE STANDARD LOG MEDIUM IS FASTRANDa, HOWEVER,
THE USER MAY REQUEST TAPE AS THE SPECIFIC LOG MEDIUM AT SYSTEMS GENERATION TIME. THE
BASIC TYPES OF INFORMATION ENTERED IN THE RUN LOG ARE FACILITY USAGE, RUN TERMINATION
DATA AND LOGGING ENTRIES MADE BY LOG CONTROL CARDS OR THE EXECUTIVE REQUEST CSF$.
THE RUN IDENTITY IS SPECIFIED IN EACH BLOCK. THE FIRST WORD OF EACH NEW ITEM IN
THE BLOCK DEFINES THE TYPE OF DATA IN THE ITEM AND THE NUMBER OF WORDS PERTAINING TO
THIS ITEM,
7.7.~,1,

LOG CONTROL CARD OR EXECUTIVE REQUEST LOG ENTRY

LOGGING ENTRIES SPECIFIED BY THE LOG CONTROL CARD STATEMENT (QLOG) AND THE
EXECUTIVE REQUEST(CSF$) WILL BE PLACED IN THE RUN LOG IN THE ORDER IN WHICH THEY
OCCUR. THE FORMAT OF THESE ENTRIES IS:
24 23
35
o
30 29
-------------------------------~----------------.---.-------A
1
2
28

--.---------.---.---------.---------------.----.--.---------C
--.-----.---.-----.----------.------.-----.----.------------:
I
I
I

I
I
I

31

-----------------~------------------------------------.-----.

WHERE,
A
B
C

= ENTRY TyPE (LOGGING ENTRIES =01)
= NUMBER OF WORDS IN ENTRY ITEM BEGINNING

= MESSAGE

TEXT

WITH NEXT WORD.

29

7

PROGRAMMERS REFERENCE

PAGE:

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

30

7

PROGRAMMERS REFERENCE

SECTION:

PAGE:

o
7.7.~.2.

FACILITY USAGE LOG ENTRY

WHENEVER THE CONFIGURATION OF A RUN IS CHANGED, EXCEPT FOR MASS STORAGE, AN ENTRY
IS MADE INTO THE ACcOUNTING LOG. THE FORMAT OF THE USAGE LOG IS
35

1
2

3

29

23

17

o

------------.---.-------------------------.-.--.----..-----A
B
--------.---.---.-.-----------------------.----.------------o
C
E
----------------.-------------------------.----.-----.------OF
DAY
TIME
--------.---.---.-.----.------------.-----.----.------.----..

WHEHE,
A= ENTRY TYPE (FACILITY USAGE = 02)
B= NUMBER OF WORDS FOR THIS ENTRY (IF 1 FACILITY, B=2; IF TWO
FACILITIES, 8=~1 ETC.)
C= CHANNEL NUM~ER OF FACILITY
D= UNIT NUMBEH
E= EQUIPMENT TYPE (01=8C, 02=6C, 05=8C 9 TRACK, 06=6C 9 TRACK
07=4C, 16:3A, 17=2A,
40=CARD SUBSYSTEM,
~2:PAPER TAPE SUBSYSTEM, ~4=PRINTER,
50:1004, 70:CTS, 71=WTS, 72:CTMC).
THE FIRST ENTRY FOR A PARTICULAR CHANNEL AND UNIT INDICATES AN ASSIGNMENT AND THE
SECOND ENTRY A RELEASE, IF NO SECOND ENTRY EXISTS, RELEASE IS AT RUN TERMINATION.
THIRD, FIFTH, ETC ENTRIES ARE SUBSEQUENT ASSIGNMENTS OF THE SAME DEVICE.

o

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM
SECTION:

(
7.7.4.3.

CATALOGUED MASS STORAGE FILE USAGE ENTRY

WHENEVER A CATALOGUEU MASS STORAGE FILE IS DROPPED FROM THE CATALOGUING
ENVIRONMENT (FREE STATEMENT PROCESSED AFTER ASG WITH AN R OR K OPTION), OR CHANGE IN
SPACE ASSIGNED IS MADE, AN ENTRY IS MADE IN THE MASTER RUN LOG IN THE FOLLOWING
FORMAT:
35

1

29

23

o

------------------------.-.--------------------.------------A
8

2 ----------------------------------------~-------------------FILE NAME

4

5
6

7
8

9

10

(

11
12

------------.---.-------------------------.----.--.---------FILE NAME
(CONT. )
--.---------.---.-------------------------------------------QUALIFIER
----------.-.-----------------------------.----.--.---------QUALIFIER (CONT.)
--.---------.---.-------------------------.----.--.---------ACCOUNT NUMBER
------------.-----------------------------------------------ACCOUNT NUMBER (CONT.)
------------------------------------------------------------TIME OF CATALOGUING
------------------------------------------------------------TRACK-MINUTES OF FH432 USAGE
--------------------------------------------------.---------TRACK-MINUTES OF FH880 USAGE
------------------------------------------------------------TRACK-MINUTES OF F-II USAGE
------------------------------------------------------------TRACK-MINUTES OF FASTBAND USAGE

---------------------------------------------------~--------WHERE,

A=ENTR'y TYPE (MASS STORAGE DROP=03)
B=NUMBEH OF WORDS FOR THIS ENTRY

c

31

7

PROGRAMMERS REFERENCE

PAGE:

UP-4144
Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS

32

7

REFERENCE

·SECTION:

PAGE:

o
7.7.4.4.

PROGRAM TERMINATION LOG ENTRY

FOR EACH PROGRAM IN THE RUN, TERMINATION INFORMATION IS ENTERED IN THE RUN LOG.
THE FORMAT OF THIS ENTRY IS:
35
1

2
3

5
6

30 29

24 23

o

18 17

--------------~------------------------------------~--------.
B
A
------------------------------~----

PROGRAM

IDENTITY

PROGRAM

IDENTITY

..----------,--...,------...-----

----------------.---------------,-- ....-------------------~--~--(CONT.)

----------------.---------------------------------.---.-----PROGRAM IDENTITY (CONT.)

..--.------

----------------------------------~----------------,

PROGRAM

IDENTITY

PROGRAM

INITIATION

(CONT.)

------"------.---.------------- .. ----------------.----,--------TIME (TDATE$ FORMAT)

.
.

PROGRAM TERMINATION TIME = UNIT NUMBER
E= EQUIPMENT TYPE:
01= VIlle
02= VIC
03= IVC
20= FH'+32
21= FH880
30= FASTRANO
F= NUMBER OF INPUT FUNCTIONS
G= NUMbER OF OUTPUT FUNCTIONS
H= NUMBER OF INPUT AND OUTPUT WORD TRANSFERS DIVIDED BY 1000
1= THE EXTERNAL INTERRUPT CODE FROM THE STATUS WORD FOR DRUM
OR FASTRAND OR A PSEUDO CODE FOR MAGNETIC TAPES (SEE
CHAPTER 10 FOR PARTICULAR CODES)
J= COUNT OF OCCURRENCES OF THIS ERROR.
K= ADDRESS OF ERROR FOR MASS STORAGE ERRORS IF APPLICABLE
OTHERWISE ZERO.

o

UP-4144
Rev~

1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

CONSOLE LOG ENTRIES
EACH CONSOLE MESSAGE IS PLACED IN THE MASTER LOG, AT
RUN TERMINATION, EVERY MESSAGE PERTAINING TO THE RUN
IS PRINTED AT THE END OF THE PROGRAM LISTING, THE FORMAT
IF THE LOG ENTRY IS:
29

35

1
2
3

23

17

A
B
C
D

(

-.'"
./

o

-------------.---.-.-----.----------------------.-------A
8
-------------------.-----------------.----------.-------C
-------------.---------------------.------------.-------D
-------------.-----------------------.----------.----.---

WHERE,

= ENTRY TyPE (CONSOLE ENTRIES = 07)
= NUMBER OF WORDS IN TEST
= MESSAGE NUMBER
= TEXT

35

7
SECTION:

PAGE:

UNIVAC 110B

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

36

7
SECTION:

PAGE:

RUN INITIATiON
WHEN A RUN IN OPENED, AN ENTRY IS MADE IN THE LOG WITH PERTINENT INFORMATION
CONCERNING THE RUN.
29

35

1

17

23

11

5

o

-------------------------------.----------------.--.----A
B

----------.---------------.
.
: START TIME

"I!II------.,.,---""!'--~-

C

...-------"'!----

: OEAD,LINE TIME

EST p.O.
EST C.O.
3 ---------------------.-----------------------------~-~--: EST RUN TIME
---------~------~-------------------~-------------------RUNIO (GENERATED)
RUNID (SUBMITTED)
5 ---------~------------------------~-----~---------------~
6
7

8

----------------------------------------------------~---PRO..JECT

-------------------.----------------------------.-------PRO..JECT

------------------------_."--_
.._-----------------.--.----.
ACCOUNT

-----------------------------------------------~----.---.
NUMBER
SEQUENCE RUNID
10:-----------------------------------------~----------~~---

9

--------------------.---------~-------------------------WHERE,
A
B
C

= ENTRY TYPE (RUN INITIATION = 9)
= NUMBER OF WORD IN
ENTRY
=
RUN LIMITING OPTIONS ( S,C,P, OR
~OG

T)

( lJ

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OF:'ERATING

SYSTEM

7

PROGRAMMERS REFERENCE

SECTION:

CONSOLE REPLIES
REPLIES TO CONSOLE TYPE AND READ MESSAGES ARE PLACED
IN THE MASTER LOG. THE REPLIES AS WELL AS THE TYPE AND
READ MESSAGES ARE PRINTED AT THE END OF THE PROGRAM
LISTING. THE FORMAT OF THE CONSOLE REPLY IS:
35
1

2

29

23

17

11

5

o

---------------------------------------~---------------.A
B

--------------------------------------------------------.
REPLY
-----------------------------------"---------------------

-----------------.-------------------------------------.: MSG 10 :

27:

-----------------~-------------~-.------~-----------~-.-.
WHERE,
A
S

= ENTRY TYPE (CONSOLE REPLIES = 012)
=
NVMBER OF WORDS IN TEXT

37
PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM

38

7

PROGRAMMERS REFERENCE

SECTION:

PAGE:

(j
'--'"

7.7.5.

SUMMARY ACCOUNTING FILE

A SPECIAL ACCOUNTING FILE IS MAINTAINED BY THE EXECUTIVE SYSTEM FOR THE PURPOSE OF
PROVIDING LIMITED SUMMARY ACCOUNTING INFORMATION. THE INFORMATION IS ACCUMULATED BY
~CCOUNT NUMBER AT THE TIME OF RUN COMPLETION.
THE TYPE OF TERMINATIONS WITHIN THE
RUN ARE DISREGARDED,
THE SUMMARY WILL ACCUMULATE INFORMATION ON THE FOLLOWING ITEMS:
RUN TIME APPLICABLE TO THE ACCOUNT NUMBER
TIME AND DATE OF THE FIRST ENTRy IN THE ACCOUNT NUMBER
TIME AND DATE OF THE LAST ENTRY IN THE ACCOUNT NUMBER
NUMBER OF PAGES OF PRINTING
NUMBER OF CARDS READ IN AND NUMBER PUNCHED OUT
ELAPSED TIME AN I/O FACILITY WAS ASSIGNED TO THE
ACCOUNT. THE I/O FACILITIES APPLY TO THE
DRUM SCRATCH AREA AND TO THE EQUIPMENT DESCRIBED
IN THE FACILITY USAGE LOG ENTRY.
THE SUMMARY ACCOUNTING FILE IS FIRST CONSTRUCTED DURING SYSTEM GENERATION. AN
ENTRY FOR EACH ACCOUNT NUMBER IS CONSTRUCTED WHICH INCLUDES THE SCHEDULING .
LIMITATIONS FOR THIS ACCOUNT. THE ENTRY IS 51+ WORDS LONG AND CURRENTLY HAS MANY·
UNUSED WORDS ALLOWING EXPANSION FOR NEW PERIPHERAL SUMMARY ITEMS, ETC.
ADDITIONAL ENTRIES ARE MADE IF OPERATOR APPROVAL IS GIVEN TO ACCEPT THE UNKNOWN
ACCOUNT NUMBER OF A RUN. THE PRIORITY SUPPLIED IS PLACED IN THE 'P' AND 'Q' ENTRIES,
DEADLINE AND REAL TIME ARE MADE ILLEGAL.
05
17
00
11
00 ---~------------------------------------------~------~-ACCOUNT
35

29

_____________ -

01

23

_____________ -

..-.

_ _ _ _ _ _ _ ~------------------ _ _ _ MM.

NUMBER

P
DL
02 ---------------------------------------------------~-------NEW
RT

_____________ --________.--_-____________________ --_w_______ _

03

06

--------.---.--------------------------------------------.---.---------.-----------------------------.----.-_.--------------------.-----------------------.-----.----.------------

07

---------~-----------------------------------------.---~----

08

-------------~----------------------------------------------

04
05

09 ----------------.-------------------.---~-------------------

10

~--------------------.-----~-----------------------~--.----DATE OF FIRST ENTRy

TIME OF FIRST ENTRY
11 ----------------.----------------------~-----------".------DATE OF LAST ENTRY
12 -----------.----~----------------------------------.-------13
14

15
16

--------.---.-----------------------------------------.----TIME OF LAST ENTRY
--.---------.---.------------------------------.-----------DATE ENTRY LAST CLEARED
--_.------------------------------.-------.----------------TIME ENTRY LAST CLEARED
----------.-.-----------------------------.----------------TOTAL NUMBER OF RUNS

TOTAL ELAPSED TIME OF RUNS
17 -----.--------------------------------------------~~-------18

-._---------------------------------.------------_.--------TOTAL COMPUTE TIME USED
------------------------------------------.----.-----------

UP-4144

UNIVAC 1108

OPERATING

Rev. 1

EXEC S'

PROGRAMMERS REFERENCE

SYSTEM

(
19

TOTAL CARDS/IMAGES IN
20 -------~----------------------------------------------.---TOTAL CARDS OUT
TOTAL LINES OUT
21 -------------------------------~--------------------------22 -------------------------------------------------~--------23
24

--------.-.-.---.-------------------------._------.-------.-------.--------------------------------------------------

25 -------------------------------------------------~----.---TRACK-MINUTES OF FH432 USAGE

26

--------.---.-------------------.---------.----.--.-.-.---TRACK-MINUTES OF FH880 USAGe

27 --------------------~---------------------------~-----.---TRACK-MINUTES OF FASTRAND USAGE
_ _ _ _ _ ~ _ _ _ - _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ M _ _ _ _ _. _
28 -----------------------~---~---~-------------------------.TRACK-MINUTES OF FASTBAND USAGE

29 :

30
31

----.-----------.------------------------------.----------.-.---------------.---.-----------.------------.
__ .-------TOTAL TIME 8C ASSIGNED

TOTAL TIME 6C ASSIGNED
32 -------------------------------------------------~--------33

(

34
35

36
37

38
39

41
42

--.---------.---.-----------------------------------------TOTAL TIME 4C ASSIGNED
--------.---.----------.------------.---------------------TOTAL TIME lIlA ASSIGNED
--------.---.-----------------------------.----.------.---TOTAL TIME IIA ASSIGNED
------------.-----------------------------.-----------.---TOTAL TIME FH432 ASSIGNED
--------.------ ..------.------------.-----.------_.-------TIME FH880 ASSIGNED
--------------------------.---------.-----.-.-----------.---------.---.---.------------------------------.--.-----------------------.---------------------------------.-------TOTAL TIME CARD SUBSYSTEM ASSIGNED
----------------.-----------------------------------.-----TOTAL TIME PAPER TAPE SUBSYSTEM ASSIGNED
----------------------------------------------------------TOTAL TIME PRINTER ASSIGNED
--------.---.---------------------------------------------TOTAL TIME 1004 ASSIGNED
TOTA~

-------------------------------------------.-----~----.---TOTAL TIME CTS ASSIGNED

45

47

c

50

------------.---------------------------------------------TOTAL TIME WTS ASSIGNED
--.-----.-------------------------------------------------TOTAL TIME CTMC TERMINAL ASSIGNED
--.-----------------------.---------------------------------.---------.---.-.-------.---------.-----.-.---------------------.---.-----------------------------------------.-----.---------.----------.----------.-------------------------------------------------------------------.-------~------

7
SECTION:

39
PAGE:

UP-4144
Rev.1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

7
SECTION:

40
PAGE:

51

52
53

---------------------------------------------------------~-

---------~--------------------------------------------..-.-

54 ---------------.-----~-------------------------------------

--.---.-----.----------.------------------.----------------WHERE:
P : HIGEST ALLOWABLE PRIORITY.
Q : PRIORITY USED WHEN NONE SPECIFIED.
DL: NON-ZERO IF DEADLINE SPECIFICATION ALLOWED.
RT: NON-ZERO IF REAL TIME SPECIFICATION ALLOWED.
NEW: NON-ZERO IF ENTRY ADDED BY OPERATOR ACTION,

7.8.

CHECKPOINT/RESTART

7.8. 1 •

GENERA'L

THE 1108 EXECUTIVE SYSTEM INCORPORATES A CHECKPOINT/RESTART FACILITY THAT WILL
FUNCTION WITH ANY FILE FORMAT AT ANY LEVEL OF ACCESS. IT MAY BE INITIATED BY A USER
PROGRAM, A CONTROL STATEMENT, OR AN UNSOLICITED KEyIN. ALL RUNS EXCEPT REAL-TIME MAY
BE CHECKPOINTED.
THE CHECKPOINT ROUTINE WILL AUTOMATICALLY INCLUDE ALL PERTINENT INFORMATION
NECESSARY FOR RESTART EXCEPT CATALOGUED OR 'TO BE CATALOGUED' FASTRANDFILES THAT ARE
BEING UPDATED. THE USER MUST SPECIFY, BY AN OPTION ON THE ASG CONTROL CARD FOR EACH
OF THESE CATALOGUED FILES, WHETHER THE CHECKPOINT ROUTINE SHOULD OR SHOULD NOT DUMP
SUCH FILES. IF THEY ARE DUMPED, THE STATUS OF THE ORIGINAL FILE REMAINS UNCHANGED.
(SEE C!-,APTER ON THE ASG CONTROL CARD), . ALL TEMPORARY FILES WILL BE AUTOMATICALLY
DUMPED AND RELOADED ON RSTRT. IF THE TEMPORARY FILE DOES NOT NEED TO BE SAVED, IT
SHOULD BE RELEASED BEFORE THE CHECKPOINT WITH A CALL TO CSFS.
CHECKPOINT INFORMATION MAY BE RECORDED ON TAPE OR FASTRAND. IF TAPE IS CHOSEN,
THE INFORMATION CAN BE INTERSPERSED WITH DATA (CHECKPOINT ON OUTPUT OATA TAPE ONLY)
OR RECORDED ON A NON~DATA TAPE 

THE RESTART INTERRUPT LOCATION WILL. BE CHECKED UPON COMPLETION OF THE LOAD ·TO
ASCERTAIN IF THE USER WANTS CONTROL AT THIS INTERRuPT LOCATION BEFORE THE RUN IS

PAGE:

43

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

I

EXEC B

I

SYSTEM

PROGRAMMERS REFERENCE

7
SECTION:

44
PAGE:

o
INITIATED. IF THE USER DOES ACCEPT CONTROL, IT IS HIS RESPONSIBILITY TO TRANSFER
CONTROL TO REINITIATE HIS RUN AT THE COMPLETION OF THE INTERRUPT SEQUENCE.
7.8.4.1.

PROGRAM REQUEST

THE PROGRAM REQUEST IS A PROCEDURE CODED IN THE USER'S SOURCE PROGRAM TO AFFORD AN
IMMEDIATE RESTART CAPABILITY WITHOUT LEAVING THE OPERATIONAL ENVIRONMENT, AND/OR
WITHOUT OPERATOR INTERVENTION. THE REQUEST f"ORM IS:'
R$STRT
WHERE:
R$STRT IS THE NAME OF THE REQUEST AND MUST BE USED AS SHOWN. P SPECIFIES THAT
ERROR ~ESSAGES ARE ,.TO BE TyPED ON THE CONSOLE. FILENAME IS THE ,NAME OF A TAPE OR
FASTRAND FILE ASSIGNED TO THE SYSTEM OR RUN THAT CONTAINS THE CHECKPOINT DUMP TO BE
RESTARTED. CKPT~ IS THE NUMBER OF THE PARTICULAR CHECKPOINT TO USE. WITH FILENAME
AND Ct. THIS
RUN CAN BE REINITIATED FROM THIS POINT AT A LATER TIME, IF A 'PI OPTION IS
SPECIFIED. INFORMATION REGARDING THIS CHECKPOINT WILL B~ TYPED ON THE CONSOLE. IF A
'T' OPTION IS SPECIFIED, THE RUN WILL BE TERMINATED' IF NOT SPECIFIED, CONTROL WILL
BE RETURNED TO THE WORKER AFTER CHECKPOINT.
EXEC REFERENCE IS MADE BY THE PROCEDURE CALL:
C$KPT

'FILENAME'.'OPTIONS'

WHICH WILL GENERATE THE ER REQUEST. THE PROCEDURE WILL LOAD AO WITH AN ENTRY CODE.
L,U AO,PKT
ER CKPT$
WHERE PKT IS A THREE WORD PACKET GENERATED UNDER LOCATION COUNTER $(30),
WORD 1

------------------------------------o
o
o
o : ' P' : "Tt : *

WORD 2

-~----------------~-----------------FILE NAME

---------------------.--------------=

UPON RETURN FROM CKPT, WORD 1 WILL BE SET AS FOLLOWS:
Sl - =0 iF CHECKPOINT WAS TAKEN,
,
ERROR CODE IF CHECKPOINT ENDED, IN ERROR AND COULD NOT BE TAKEN.

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

8.12.2.

OPERATING

SYSTEM

PROGRAMMERS

15

8

REFERENCE

SECTION:

PAGE:

RESTART

A WORKER MAY CALL FOR A RESTART OF A RUN IF HE HAS TAKEN A RESTART PREVIOUSLY,
A RUN RESTARTS ITSELF, IT WILL BE TERMINATED AND REINITIATED AT THE CHECKPOINT
SPECIFIED. IF IT RESTARTS ANOTHER RUN, A START SITUATION WILL OCCUR.

,

IF

EXEC REFERENCE IS MADE BY THE PROCEDURE CALL:
R$STRT

'FILENAME',CKPT#,'P'

WHICH WILL GENERATE THE ER REQUEST.
L,U
AQ,PKT
EH
RSTRT$
WHERE PKT IS A FOUR WORD PACKET GENERATED UNDER LOCATION COUNTER $(30).
WORD

1

WORD 2
WORD ::3

-------------.-------------------.--P
:
-----------------------------.------FILE NAME

*

-----------.------------------------CKPT #
----------------------.-------------WHERE P IS ZERO FILLED IF NOT SPECIFIED.

WORD 4

*

RETURN FROM A RSTRTCALL WILL BE MADE TO THE LOCATION
FOLLOWING THE CHECKPOINT CALL.
8.13.

MISCELLANEOUS

(
8013.1.

UNLOCK

IN ORDER TO ALLOw AN INTERRUPT ACTIVITY TO REDUCE ITS PRIORITY IN THE ABSENCE OF
ANY OTHER ER TO BE DONE THE ER UNLCK$ CAN BE USED. THE PRIMARY INTENT OF THE
INTERRUPT ACTIVITY IS TO PLACE THIS ACTIVITY AT ITS PROPER LEVEL. PROLONGED
EXECUTION AT THIS HIGH LEVEL NEGATES ANY BENEFIT HENCE THE USER SHOULD USE THE UNLCK$
FUNCTION BEFORE GOING INTO A LENGTHY COMPUTE LOOP.
8.13.2.

OPTION LETTER RECOVERY

THE OPTION LETTERS ON THE QXQT CONTROL STATEMENT INITIATING A PROGRAM ARE MADE
AVAILABLE BY CALLING EXECUTIVE REQUEST FUNCTION 'OPT$'. WHEN CONTROL IS RETURNED,
THE OPTION LETTERS WILL BE ENCODED INTO REGISTER AQ' I.E., IF THE LETTER Z IS
PRESENT, BIT Q wOULD BE SET' IF THE LETTERS A AND B ARE PRESENT, BITS 24 AND 25 WOULD
BE SET.
THE EXEC REFERENCE IS:
ER
8.13.3.

OPU

TIME AND DATE

THE EXECUTIVE FUNCTION 'DATE$' SUPPLIES THE USER WITH THE CURRENT DATE IN FIELOATA
DECIMAL CODE IN REGISTER AO. THE CURRENT TIME IN FIE~DATA DECIMAL CODE IS SUPP~IED
IN REGISTER AI. THE FORMAT OF REGISTER AD IS:
35

24 23

12 11

00

------------------------------------------------------------A
B
C
-----------------~------------------------------------------WHERE,

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

16

8
SECTION:

PAGE:

A - MONTH (l=JAN, 2=FEB, ETC.)
B - DAY OF THE MONTH
C - YEAR (LAST TWO DIGITS OF THE YEAR)
THE FORMAT OF REGISTER A1 IS:
00

12 11

.24 23

35

--------------.----------.----------------------------------F
E
D
------------------------------------------------------------WHERt.,
D - HOURS (00 - 24)
E - MINUTES (00 - 60)
F - SECONDS (00 - 60)
TliE EXECUTIVE FUNCTION 'TDATE$' SUPPLIES THE USER WITH THE DATE AND TIME IN AO IN
THE FOLLOWING FORMAT:
35

23

17

o

-------------.------------------------------------------o
B
C
A
-----------------.--------------------------------------wHERE,

=

A
t"10NTH
B
DAY
C
YEAR (MODULO 1964)
D = TIME IN SECONDS FROM MIDNIGHT

=
=

TH~ EXECUTIVE FUNCTION .TIME$' SUppLIES THE USER WITH THE TIME OF DAY IN
MILLISECONDS IN REGISTER AO.

8.13.4,

READ PROGRAM CONTROL TABLE

INFORMATION STORED IN THE PROGRAM CONTROL TABLE COLLECTED BY THE EXECUTIVE FOR RUN
IS AVAILBLE WITHIN A PROGRAM USING THE REQUEST, PCT$. THE FORM IS:

COI~TROL

LAG, (N,A)
ER
pca
WHERE 'N' WORDS ARE MOVED BY THE EXECUTIVE TO THE LOCATION 'A' IN THE PROGRAM.
THE FIRST ~ORD CONTAINS THE RUNID IN FIELDATA CODE, CONSULT SYSTEMS MANUAL FOR OTHER
AVAILABLE DATA.
NOTE: THE MAXIMUM 'N' PERMITTED IS LIMITED TO ALL DATA BEFORE
THE FILE NAME LIST. FILE NAMES,USE NAMES AND OTHER INFORMATION
WILL NOT BE AVAILABLE TO THE PROGRAMMER.
8.13.5.
B~

SNAPSHOT DUMPS

A SNAPSHOT DUMP OF THE CONTENTS OF SELECTED CONTROL REGISTERS AND MAIN STORAGE CAN

OBTAINED USING THE REQUEST 'SNAP$'. THE EXECUTIVE REQUEST IS CODED:

L,u

EH

AO,PKT ADDR
SNAP$

o

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM
SECTION:

WHERE THE PACKET HAS THE FORM:
:35

17

32

00

-----------------------------------------------------------SNAPSHOT IDENTIFIER
---------------------------------------------..-----------LENGTH
:X:A:R:
AUlJRESS
------------.----------------------------------.-----------FORMER CONTENTS OF AD
-----------------------------------------------.-----------THE SNAPSHOT IUENTIFIER IS A SIX CHARACTER FIELDATA WORD USE" TO IDENTIFY THE
SNAPSHOT. THE TIME AND DATE WILL ALSO BE PRItJTED ON THE IDENTIFICATION LINE.
'X','A', AND ,R' ARE ONE BIT FIELDS WHICH WHEN SET TO ONE CAUSE THE DESIGNATED
CONTROL HEGISTERS TO BE PRINTED. 'LENGTH' ANO 'ADDRESS' DEFINE A MAIN STORAGE AREA
TO I:3E DUMPED.
UPON RETURN FROM THE REQUEST, THE CONTENTS OF AO WILL BE EQUAL
TO PKT ADDR+2. THE cONTENTS OF THIS CELL WILL ALSO BE USED FOR AO IF THE SNAP REQUEST
SPECIFIES AN A-REGISTER DUMP OR AN X-REGISTER DUMP.
8.13.6.

THE CONDITION WORD

THE EXEC FUNCTION, SETC$, PLACES(SETS) THE CONTENTS OF THE LOWER THIRD(BITS 11-00)
OF CONTROL REGISTER AO IN THE CORRESPONDING THIRD OF THE RUN 'CONDITION' WORD. THIS
FUNCTION IS SIMILAR TO THAT OF THE ~SETC CONTROL STATEMENT, EXCEPT THAT THERE IS NO
CHOICE OF ~-UESIGNATORS.
8.13.6.2.

RETRIEVE

THE EXECUTIVE FUNCTION 'CONDS' RETRIEVES THE CONDITION WORD AND MAKES IT AVAILABLE
TO THE USER IN REGISTER AO. THIS FUNCTION IS SOMEWHAT SIMILAR TO THE QTEST CONTROL
STATEMENT IN THAT A DECISION CAN BE MADE ON THE BASIS OF WHAT IS FOUND IN THE
CONUITION WORD. TliIS DOES NOT IMPLY, HOWEVER, THAT THE 'CONDS' FUNCTION ITSELF
PROVIDES ANY TEsTING CAPABILITIES.
8.13.7.

SEGMENT LOADING

THE LOAD$ FUNCTION PROVIDES THE WORKER PROGRAM A MEANS OF LOADING SEGMENTS OF
ITSELF. THE SEGMENT NAME IS LOADED IN CR AO AND THE RETURN ADDRESS IS LOADED IN CR
Al BEFORE THE REQUEST IS MODE. IN ADDITION, IF AO IS POSITIVE, THE CORE WITH WHICH
THE SEGMENT WILL BE LOAuEO IS ZERO FILLED PRIOR TO LOADING. IF Al IS ZERO, CONTROL IS
RETURNED TO THE NEXT INSTRUCTION OF THE PROGRAM. IF A RELOCATABLE SEGMENT IS TO BE
LOADED, CR A2 MUST BE LOADED WITH THE ADDRESS wHERE THE SEGMENT IS TO BE LOADED
THE EXECUTIVE REQUEST IS CODED:
L,U
L,U
ER
8.14.

AO,SEGMENT NAME
Al,RETURN ADDRESS
LOAD$

SUMMARY

TA~LE 8. 1 SUMMARIZES THE EXECUTIVE REQUESTS RECOGNIZED BY THE EXECUTIVE SYSTEM.
THE TA8LE CLASSIFIES ER FUNCTIONS AS TO WHETHER THEY ARE IMMEDIATE, ASYNCHRONOUS, OR
SrNCHRONOUS.

t"UNCTION TYPE DESCRIPTION

CROSS REFERENCE

AUOHT$

E..XECUT IVE Rt:.QUEST

--------

(~;
. .-/

-----------

I

AtWRT EXIT

---------

FUNCTIOI~S

17

8

PROGRAMMERS REFERENCE

PAGE:

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS

REFERENCE

18

8
SECTION:

PAGE:

r"'!
,~,,/
ACTIVITY ACTIVATION

ACT$
ALTCL$
ADLT$

S
I

CLOSE ALTERNATE FILES
ACTIVITY DELETION

ADACT$
AWAIT$

I

COMPLETION ACTIVITIES
ACTIVITY WAIT

~JOIN$

BPOOL$
CADD$

I
I
I

CEND$
BREAf.)$
tlRRED$
BWRITE$
BRWRT$
BOPEN$
tlCLOR$
BCLOF$
UMARK$
CGET$

I

CKPT$
COND$

S
I

CMD$

A

CMH$

A

CMU

A

CMO$

A

CMS$

I

CMSA$

A

CMT$

I

CPOOL$

I

CSF$

S

COM$

S

OACT$

BUFFER POOL EXPANSION
BUFFER POOL SETUP
COMMUNICATIONS BUFFER
POOL ADDITION
PROGRAM CONTINGENCY
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
BLOCK BUFFERING
COMMUNICATIONS BUFFER
POOL REMOVAL.
CALL FOR CHECKPOINT
RETRIEVE THE
'CONDITION WORD
COMMUNICATION HANDLER.
DIAL
COMMUNICATION HANDLER,
HANGUP
COMfvlUNICATlON HANDLER.
INPUT
COMMUN I CATI ON HANDLER.
OUTPUT
COMMUNICATION HANDLER.
INITIALIZE
COMMUNICATION HANDLER.
SEND AND ACKNOWLEDGE
COMMUNICATION HANDLER,
TERf"lINATE
COMMUNICATIONS BUFFER
POOL SETUP
CONTROL STATEMENT
FORMAT ENTRY
CONSOLE COMMUNICATION
ENTRANCE
ACTIVITY DEACTIVATION

()ATE$

I

REGlUEST DATE

lJITEM$
LlREL$

S
I

DIRECTORY ITEM RETRIEVED
DYNAMIC SEGMENT RELEASE

ERR$

I

ERROR EXIT

EXIT$

I

NORfltlAL EXIT

FACIL$
FORK$

5

I

FACILITY DETERMINATION
REGISTER ACTIVITY

lALL$
10$

I
A

INTERRUpr ADDRESS CHANGE
INPUT/OUTPUT FUNCTION

IOARB$

A

INPUT/OUTPUT FUNCTION

EXECUTIVE REQUEsT
FUNCTION.
SYMBIONTS
EXECUTIVE REQUEST
FUNCTIONS
I/O DEVICE HANDLERS
EXECUTIVE REQUEST
FUNCTIONS
FILE CONTROL SYSTEM
FILE CONTROL SYSTEM
FILE CONTROL. SYSTEM
SUPERVISOR
DATA HANDLING
DATA HANDLING
DATA HANDLING
DATA HANDLING
DATA HANDLING
DATA HANDLING
DATA HANDLING
DATA HANDLING
FILE CONTROL. SYSTEM
SUPERVISOR
EXECUTIVE REQUEST
FUNCTIONS
INPUT/OUTPUT DEVICE
HANOLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
FILE cONTROL SYSTEM
EXECUTIVE REQUEST
FUNCTIONS
OPERATOR
COMMUNICATIONS
EXECUTIVE REQUEST
FUNCTION.
EXECUTIVE REQUEST
FUNCTIONS
FILE CONTROL SYSTEM
AUXILARY PROCESSORS
EXECuTIVE REQUEST
FUNCTIONS
EXEcuTIVE REQUEST
FUNCTIONS
FILE CONTROL SYSTEM
EXECUTIVE REQUEST
FUNCTIONS
SUPERVISOR
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE

(~
.j

UP-4144

Rev. 1

UNIVAC 110e

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

(

f--

C~

ON ARBITARY DEVICE
INPUT/OUTPUT FUNCTION ON
ARBITARY DEVICE EXIT AND
INTERRUPT ACTIVITY
INPUT/OUTPUT FUNCTION,
ACTIVITY NAMING

HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS

10AXI$

A

101$
NAME$

A

IOWI$

S

101'1$

S

IOXI$

A

IRST$
LCORE$

I
S

LINK$

S

LOAD$

S

MCORE$

S

REQUESTS TO LINK TO
REENTRANT ROUTINE
REQUEST FOR SEGMENT
TO BE LOAUED
REQUEST ADDITIONAL CORE

NRT$

I

RELEASE REAL-TIME STATUS

OPT$

I

PCHCN$
PCT$

S
I

PRINT$

S

PRTCN$
PRNTA$

S
S

PUNCH$

5

PNCHA$

S

READ$

S

REAOA$

S

HSTRT$
RT$

S
I

SETC$

I

SNAP$

5

TDATE$

I

TFORK$

I

TIME$

I

TINTL$

S

TSWAP$

S

ULINK$

S

UNLCK$

I

REQUEST OPTION LETTERS
FROM XQT CARD
PUNCH SYMBIONT CONTROL
PROGRAM CONTROL TABLE
REFERENCE
SYSTEM INITIATED PRINT
FILE ENTRY
PRINT SyMBIONT CONTROL
SYMBIONTS
ALTERNATE PRINT FILE
SYMBIONTS
ENTRY
SYSTEM INITIATED PUNCH
SYMBIONTS
FILE ENTRY
ALTERNATE PUNCH FILE'
SYMtHONTS
ENTRY
ENTRY FOR READING CONTROL SYMSIONTS
STKEAM
ALTERNATE READ ENTRY FOR
SYMBIONTS
SYMBIONT CONTROLLED DEVICES
CALL FOR RESTART DUMP
SUPERVISOR
REQUEST REAL-TIME STATUS
EXECUTIVE REQUEST
FUNCTIONS
SET A VALUE IN THE
EXEcuTIVE REQUEST
'CONDITION' WORD
FUNCTIONS
SNAPSHOT DUMP
EXEcuTIVE REQUEST
FUNCTIONS
REGUEST DATE/TIME
EXEcuTIVE REQUEST
FUNCTIONS
TIf..1ED ACTIVITY
EXECUTIVE REQUEST
HEGISTRA nON
FUNCTIONS
REGUEST TIME OF DAY
EXEcuTIVE REQUEST
IN MILLISECONDS
FUNCTIONS
TAPE REEL NUMBER SET
EXECUTIVE REQUESTS
INITIALIZATION
TAPE SWAPPING
EXEcuTIVE REQUEST
FUNCTIONS
~ETURN TO WORKER PROGRAM
EXEcuTIVE REQUEST
FROM REENTRANT ROUTINE
FUNCTIONS
HEVERT TO NORMAL MODE
SUPERVISOR

INTERRUPT ACTIVITY
INPUT/OUTPUT FUNCTION,
INTERRUPT ACTIVITY, wAIT
INPUT/OUTPUT FUNCTION AND
WAIT FOR COMPLETION
INPUT/OUTPUT FUNCTION,
INTERRUPT ACTIVITY, EXIT
RESTART
RELEASE CORE

INPUT/OUTPUT DEVICE
EXECUTIVE REQUEST
FUNCTION.
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
SUPERVISOR.
EXECUTIVE REQUEST
FUNCTIONS
EXECUTIVE REQUEST
FUNCTIONS
AUXILIARY
PROCESSORS
EXECUTIVE REQUEST
FUNCTIONS
EXECUTIVE REQUEST
FUNCTIONS
EXECUTIVE REQUEST
FUNCTIONS
SYMBIONTS
E.XECUTIVE REQUEST
FUNCTIONS
SYMBIONTS

19

8
SECTION:

PAGE:

;UP-4144

I Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

wAlT$

S

WANY$

S

SYSTEM

WAIT FOR COMPLETION OF
SPECIFIC I/O
WAIT FOR CO~PLETION OF
ANY I/O

20

8
SECTION:

PAGE:

HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS
INPUT/OUTPUT DEVICE
HANDLERS

TABLE 8. 2

o

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

-=~,

EXEC B

9.

9. 1 •

SYSTEM

PROGRAMMERS REFERENCE

SYMBIONTS

GENERAL DESCRIPTION

THE EXECUTIVE SYSTEM PROVIDES A COMPLEX OF ROUTINES CALLED SYMBIONTS WHICH
INTERFACE THE PRIMARY UNIT RECORD EQUIPMENT OF THE i108 WITH THE USER. THESE DEVICE
ROUTINES ARE AVAILABLE FOR ALL STANDARD TERMINALS. ON-SITE DEVICES INCLUDE CARD
READERS/PUNCHES, PRINTERS, PAPER TAPE READER/PUNCH AND 1004'S. REMOTE SITE TERMINALS
AHE ACCOMODATED USING NORMAL COMMUNICATIONS SYSTEMS. DATA, TO AND FROM THESE
DtVICES, IS BUFFEHED USING MASS STORAGE TO PROVIDE AN EFFECTIVE LINKAGE TO THE
ASYNCHRONOUS AND RELATIVELY SLOW DEVICES. THE ROUTINES WHICH INTERFACE DIRECTLY WITH
THE USER ARE AVAILABLE THROUGH THE EXEC REQUESTS READ$, PRINT$ AND PUNCH$, FOR EACH
THE USER SPECIFIES THE CORE AREA WHERE THE IMAGE IS, OR IS TO BE PLACED, A FILE IS
AVAILABLE FOR ALL THREE PATHS, AND THE PROVISION IS MADE THROUGH DEFINITION BY THE
USER OF OTHER FILES FOR THE CONSTRUCTION OF OTHER OUTPUTS AND INPUTS AS REQUIRED. AN
OUTPUT CONTROL REQUEST IS .LSO AVAILABLE WHICH CAN BE USED TO PROVIDE CONTROL
INFORMATIOiJ TO THE ROUTINES RELATED TO SPECIFIC OUTPUT DEVICES. THE OUTPUT CONTROL
REQUEST ALSO PROVIDES THE ADDITIONAL FACILITY OF ADVISING THE OPERATOR OF THE OUTPUT
DEVICE SYNCHRONIZED WITH THE ACTIVITY OF THE DEVICE. PROVISION ALSO EXISTS TO SKIP
OR BACKSPACE OVER PORTIONS OF THE OUTPUT FILES,
THE READ$, PRItJT$ AND PUNCH$ INTERFACE ROUTINES ARE CAPABLE OF MULTIPLE FILE
OPERATIONS WITHIN ANY RUN. THE SYSTEM IS RESPONSIBLE FOR INITIATING ONE FILE FOR
EACH INTERFACE ROUTINE, THE RUN INITIATING FILE(READ$), THE SYSTEM PRINT(PRINT$) AND
PUNCH(PUNCli$) FILES. THESE ARE NECESSARILY DEFINED TO ALLOW THE VARIOUS EXEC 8
COMPONENTS TO RECEIVE INPUT AND TO DISPLAY OUTPUT. THESE INTERFACE ROUTINES ARE
SUPPLEMENTED NITH ADDITIONAL ENTRANCES TO FACILITATE MULTIPLE FILE SYMBIONT
INPUT/OUTPUT OPERATIONS.
DURING SYSTEM GENERATION, AN OUTPUT DEVICE OR CLASS OF DEVICES IS ASSOCIATED WITH
EACH OF THE INPUT DEVICES (SEE SYSTEM GENERATION STATEMENTS - ASSOCIATED SYMBIONTS).
THE LOCATION OF THE CONTROL STREAM INPUT FOR EACH RUN THEN DICTATES THE LOCATION OF
THE PRIMARy PRINT OUTPUT DEVICE. THE QSYM STATEMENT PROVIDES A METHOD OF SELECTING
AN ALTERNATE OUTPUT DEVICE FOR THE PRINT OR PUNCH FILES. IN GENERAL, ALL OF THE
REMOTE TERMINALS WILL RECEIVE THEIR OUTPUT DIRECTLY, BUT WHERE VOLUME QICTATES OR A
SUITABLE PRINTER IS NOT AVAILABLE, SOME OTHER REMOTE OUTPUT OR AN ON-SITE PRINTER
COULD BE SELECTED.
INPUT TO THE SYSTEM IS SEPARATED ACCORDING TO QRUN AND QFILE STATEMENTS. EACH
WRUN ENCOUNTERED AND ITS SUCCEEDING STATE~ENTS ARE USED TO GENERATE A 'RUN FILE' TO
BE SUBMITTED TO THE SCHEDULING RO~TINE. INFO~MATION OF CONCERN TO THE COARSE
SCHEDULER IS EXTRACTED FOR PRELIMINARY RU~ SCHEDULING. THE INPUT SYMBIONTS MUST ALSO
INTERPRET THE QELT,D, QDATA, QEND, QFILE AND ~ENDF STATEMENTS TO PROVIDE UNRESTRICTED
If~PUT OF DATA FILES BETWEEN THESE TWO STATEMENTS.
.
ALL FILES CREATED OR PROCESSED BY THE SYMBIONT COMPLEX ARE IN THE SYSTEM DATA FILE
(SDF) FORMAT, ANY FILE EXISTING IN THIS FORMAT CAN BE DIRECTLY PROCESSED WITH THE
INPUT INTERFACE ROUTINES AND/OR WITH THE OUTPUT SYMBIONTS.
FILES OR ELEMENTS ARE INSERTED INTO THE RUI~ FILE WHEN AN QADD CONTROL STATEMENT IS
ENCOUNfERED BY THE READ$ ROUTINE. WHEN READ$ IS ENTERED AND AN QADD CONTROL
STATEMENT IS FOUND, THE FIRST IMAGE OF THE FILE NAMED WILL BE TRANSFERRED TO THE
~EQUESTOR IN LIEU OF THE QADD,
AN INTERNAL EXEC CALLING SEQUENCE TO PERFORM THE QADO
FUNCTION IS PROVIDED FOR DYNAMIC FILE INSERTION.
SYMHIONT OUTPUT FILES ARE SUBJECT TO VARIOUS CONTROL FUNCT[ONS SUBMITTED BY AN
INTERNAL CALLING SEQUENCE. THESE FUNCTIONS VARY ACCORDING TO THE OUTPUT DEVICE TYPE
TO WHICH THE FILE IS BEING DIRECTED. AS T~IE CONTROL PARAMETERS ARE SUBMITTED THEY
ARE PLACED INTO THE APPROPRIATE OUTPUT FILE. AND INTERPRETED WHEN THE FILE IS BEING

c/

1

9
SECTION:

PAGE:

• UP-4144
Rev. 1

!

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

9
SECTION:

PROCESSED.
THE SYMBIONTS DESIGNED FOR USE WITH REMOTE DEVICES IN PARTICULAR ARE
SELF-ADJUSTING. WHEN A NUMBER OF IMAGES ARE STACKED AWAITING TRANSMISSION, THE
SYMBIONT AUTOMATICALLY MAKES USE OF A MASS STORAGE FILE FOR TEMPORARY STORAGE. ON
THE OTHER HAND, WHEN ONLY A FEW ARE CURRENTLY IN TRANSIT, THE SYMBIONT SAVES THESE
WITHIN THE CORE AREA AVAILABLE, DISPENSING THEM AS REQUIRED. OUTPUT FOR DEMAND RUNS
USE CORE BUFFERING ONLY. WHEN A LIMITED NUMBER OF IMAGES ARE STACKED IN THE OUTPUT
QUEUE, THE SUBMITTING RUN IS SWAPPED OUT.
COMMUNICATION BETWEEN THE 1108 SYMBIONTS AND THE 1004 OPERATES IN TWO MODES OF
It-IAGE HANDLING. Tt-iE ONE MODE TRANSFERS IMAGES IN THE FORMAT IN WHICH THEY ARE
PRESENTED FROM THE USER. THIS IS DONE FOR ON-SITE 1004 OPERATIONS AND FOR THE REMOTE
1004 OPERATING AT HIGH SPEED TRANSMISSION RATES FASTER THAN 2400 BITS PER SECOND.
THE OTHER MODE OF OPERATION COMPRESSES THE IMAGES BY ELIMINATING REDUNDANT SPACE
CHARACTERS PRIOR TO TRANSMISSION ACROSS SLOWER SPEED REMOTE LINES. THE FOLLOWING
TABLE IS A LIST OF THE FUNCTIONS ACCOMPANYING EACH TYPE OF 1108-1004 COMMUNICATION:

2
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
SECTION:

(
ON-SITE REMOTE NON-COMP

REMOTE COMP

------ ------.---.---. -----.----CARD READ (80)
CARD PUNCH (80)
PRINT
CODE IMAGE READ (80)
CODE IMAGE PUNCH (80)
PAPER TAPE READ
PAPER TAPE PUNCH

X

X

X
X
X
X

X

X
X

X

X

X

X
X
X

X

X

THE SYMBIONT COMPLEX CONSISTS OF THE FOLLOWING ITEMS:
1. A MASTER CONTROL FOR ALL SYMBIONT OPERATIONS.
INCLUDED ARE COMMON FUNCTIONS REQUIRED BY ALL VARIATIONS
OF THE COMPLEX.
2. CONTROL TABLES ARE CONSTRUCTED DYNAMICALLY WITH ITEMS
FOR ALL ACTIVE DEVICES AND FILES.
3. DEVICE ROUTINES, ONE FOR EACH OF THE HARDWARE DEVICES
ATTACHED TO THE 1108. A SINGLE COpy IS BROUGHT IN WHICH
HANDLES ALL DEVICES OF THE SAME CLASS.
~. IMAGE/~LOCK BUFFER CONTROL WHICH HANDLES ALL THE
BUFFERED FILES ON MASS STORAGE.
5. INTERFACE ROUTINES WRITTEN IN A RE-ENTRANT MANNER TO
DISPENSE INPUT IMAGES AND ACCEPT OUTPUT IMAGES FROM THE
VARIOUS PROGRAMS AND THE EXEC.

(

MANY OF THE CONTROLLED DEVICES ARE INITIATED AUTOMATICALLY BY THE EXEC AS
REQUIRED. OTHERS REQUIRE OPERATOR INITIATION SINCE INFORMATION IS NOT AVAILABLE TO
EXEC FOR EXAMINATION. ACTIVITY MAY ALSO BE INITIATED WITH THE QSYM CONTROL
STATE'''ENT.
9.2.

READ$

RUN FILES GENERATED BY THE INPUT SYMBIONTS ARE AVAILABLE TO THE USER VIA THE REAO$
ROUTINE. EACH REFERENCE TO READ$ RESULTS IN AN IMAGE TRANSMISSION TO THE REQUESTOR.
THE IMAGES ARE EITHER TAKEN FROM THE SYMBIONT STORED RUN FILE OR ARE OBTAINED
DIRECTLY FROM THE SYMBIONT. THE REQUIREMENT FOR ACCESSING DATA IN THIS MANNER IS
THAT IT MUST FOLLOW THE EXECUTION CONTROL STATEMENT OF THE PROGRAM WHICH IS TO
PROCESS THt: DATA. IMAGE TRANSFERS ARE RESTRICTED TO NON-CONTROL CARDS ONLY, WITH .THE
EXCEPTION OF CLIST STATEMENTS AND THE PROCESSOR CALL CARD FOR PROCESSORS.
THE FOLLOWING LINKAGE IS USED TO OBTAIN AN IMAGE:
LA AO,PACKET
£R
READ$
NORMAL RETURN
REGISTER AO CONTAINS:
+

3

9

REFERENCE

EOF,ADDRESS

THE FIELD 'ADDR~SS' IS THE LOCATION TO WHICH THE INPUT IMAGE IS TRANSFERRED. THE
IS TAKEN FROM THE IMAGE POOL, AND TRANSFERRED TO 'ADDRESS'. CONTROL IS
RETURNED TO THE ADDRESS FOLLOWING THE READ$ ENTRY WITH THE IMAGE WORD COUNT IN THE
LOWER HALF OF AO. THE UPPER HALF OF AO DEFINES THE TYPE AND SOURCE OF THE DATA
IMAGE..
THE CONDITIONS POSSIBLE IN AO ON RETURN FROM A READ$ OR TREAD$ REFERENCE ARE:
IMAG~

cIT 35 SET - ABNORMAL RETURN TAKEN BECAUSE A CONTROL STATEMENT
CANNOT BE PASSED TO THE REQUESTOR. ANY FURTHER ATTEMPT TO DO A READ$
OR TREAD$ REQUEST WITHIN THIS PROGRAM WILL CAUSE AN ERROR
TERMINATION. (WITHIN THE CLlST$ MODE THIS APPLIES ONLY TO THE QFIN

PAGE:

UP-4144

UNIVAC 1108

OPERATING

I Rev. 1

EXEC B

PROGRAMMERS

SYSTEM

9

REFERENCE

SECTION:

4.
PAGE:

o
STATEMENT.)
BIT 34 SET - CURRENTLY READING AN ADD FILE. THIS IS NOT
INFLUENCED BY OTHER BITS OR RETURNS.
BITS 33-32 - NOT USED, ALWAYS SET TO ZERO.
BIT 31 SET - IMAGE IN INFOR FORMAT. (SEE TECHNICAL DOCUMENTATION FOR DESCRIPTION OF INFOR.)
BIT 30 SET - PART OF AN INFOR TABLE, THE NEXT REFERENCE WILL
RETRIEVE NEXT PART. IN OTHER WORDS, BIT 30 SET TO ZERO INDICATES

THAT THIS IS THE LAST PART.
OF BIT 30.

BIT 31 IS SET REGARDLESS OF THE SETTING

BITS 29-18.- SET TO ZERO EXCEPT IN CLIST$ MODE WHEN IT IS SET
TO ZERO FOR DATA STATEMENTS OR TO THE INDEX OF A COMMAND IN THE
REL.EVANT CLIST$.
BITS 17-0

- WORD COUNT IF IMAGE PASSED.

SENTINEL. IF AN QEOF STATEMENT IS PASSED.
ZERO IF NO IMAGE PASSED.

QEOF STATEMENT RETURN
AO IS SET TO THE SENTINEL CHARACTER (RIGHT-~USTIFIED, ZEROFILLED) FROM COLUMN SIX
Or THE STATEMENT. CONTROL IS RETURNED TO THE USER AT HIS ABNORMAL RETURN POINT.
BIT 34 IS THE ONLY BIT THAT MAY BE SET ON THIS RETuRN.

CL.IST$ IS A MECHANISM TO ALLOW A PROGRAM To READ A GIVEN SET OF CONTROL
STATEMENTS. IF A USER CHOOSES TO USE CLIST$, THOSE CONTROL STATEMENTS IN
HIS L.I5T WILL. BE PASSED TO HIM, TRANSPARENT STATEMENTS WILL BE HANDLED BY
TtiE EXECUTIVE, AND THE QEOF AND QFIN STATEMENTS WILL CAUSE AN ENo-OF-FILE
RETURN; ALL. OTHER CONTROL STATEMENTS WILL BE REJECTED BY THE EXECUTIVE
UNTIL. AN ACCEPTA~L.E STATEMENT IS ENCOUNTERED.
CLIST$ CAN BE USED IN ONE OF TWO WAYS; IT CAN CALL FOR A LIST OF COMMANDS
THAT IS STORED IN THE EXEC, OR IT CAN REQUEST A LIST IN THE USER PROGRAM
WHICH IS MOVED INTO THE EXEC FOR THE DURATION OF THE PROGRAM. THE CALLING
SEQUENCE FOR CLIST$ IS
L
ER

AO,PKT
CLIST$

WliERE PKT CONTAINS THE ALPHANUMERIC NAME OF A CANNED LIST, LEFT-JUSTIFIED,
SPACE-FILLED, OR THE ADDRESS OF A LIST WITHIN THE PROGRAM. IN EITHER CASE,
THE LIST MAY CONTAIN UP TO 62 A~PHANUMERIC NAMES, LEFT-~USTIFIEo,
SPACE-FILLED. THE LIST IS TERMINATED BY A MINUS ZERO. THE INDEX OF A NAME
CORRESPONDS TO ITS POSITION IN THE LIST; THE FIRST NAME HAS INDEX 11 THE
SECOND 2; AND SO ON. Ir A LIST NAME IS GIVEN THAT IS NOT IN THE SYSTEM, IT IS
NuT CONSIDEREO TO BE IN ERROR, BUT THE LIST IS REGARDED AS AN EMPTY LIST. IF
A MINUS ZERO IS NOT SUPPLIED AS A TERMINAL ITEM IN THE LIST, IT IS
AUTOMATICAL.LY SUPPLIED IN PLACE OF THE SIXTY-THIRD NAME.
WHENEVER A PROGRAM HAS ENTERED THE tLIST$ MODE, THE CONTROL STATEMENT QENDX
IS AUTOMATICALL.Y ASSUMED TO BE PART OF THE LIST; ITS INDEX IS 77 OCTAL. THE
PURPOSE OF THIS STATEMENT IS TO HAVE A COMMON TERMINATION COMMAND FOR PROGRAMS
USING CL.lST$.
THE INDEX SPECIFYING A GIVEN COMMAND FROM THE LIST IS RETURNED IN BITS
23 TO 18 OF AO ON RETURN FROM THE READ$ REQUEST. THE IMAGE GIVEN FOR A
STATEMENT CONTAINING A COMMAND IN THE LIST WILL BE THE COMPLETE STATEMENT

c

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

IMAGE.
IF A CONTROL STATEMENT IS REJECTED AND THE PROGRAM IS ATTEMPTING TO READ
THE IMAGE VIA TREAD$, THE OUTPUT IMAGE ASSOCIATED WITH THE TREAD$ CALL WILL
BE REPRINTED.

R$EAD

PKT

GENERATES A TwO wORD CALLING SEQUENCE. THE FIRST WORD LOADS
REGISTER AO FROM THE LOCATION ,PKT' AND THE SECOND WORD IS AN 'ER
READ$'.
9.2.2.

TREAD$

THE LINKAGE TREAD$ CAN BE USED AS AN ALTERNATE TO THE READ$
REQUEST. ·TREAD$ IS DESIGNED FOR CONVERSATIONAL REMOTE TERMINAL INPUT AND
PROVIDES THE ABILITY TO PRINT AT THE TERMINAL A REQUEST FOR AN INPUT IMAGE,
THE REQUEST FORM IS:
LA
ER

AD,PACKET ADDRESS
TREAU$

WHERE PACKET ADDRESS REFERS TO A TWO WORD PACKET CONTAINING THE
PRINT$ AND READ$ PARAMETERS:

(

p

+

L,S,N,OUT
EOF,AUORESS

THE ACTION THAT TAKES PLACE IS:
1 'S' SPACING IS PERFORMED.
2 THE IMAGE AT 'OUT' OF LENGTH,N' IS PRINTED.
3 AN IMAGE IS ACCEPTED FROM THE INPUT JEVICE.
4 IF THE IMAGE IS DIRECTED TO THE EXECUTIVE, IT IS ACTED
UPON WHILE THE PROGRAM WAITS. SPACING AND THE
PRINTOUT IS THEN RE-ISSUED AS A REQUEST FOR ANOTHER
IMAGE FOR THE PROGRAM.
S AN IMAGE FOR THE PROGRAM IS THEN TRANSMITTED WITH THE SAME INFORMATION
IN AD AS A READY CALL.

ALTERNATE INPUT FILES (READA$)
ASSIGNMENT OF SYMBIONT CONTROLLED INPUT DEVICES IS MADE AVAILABLE TO A RUN WITH
THE ARBITRARY DEVICE FORMAT ~ASG STATEMENT. THE OPERATING PROGRAM MAY EITHER USE THE
DEFINED DEVICE SYMBIONT OR PROVIDE ITS OWN DEvICE HANDLER TO PERFORM THE INPUT
OPERATION. WHEN USING THE SYMBIONT COMPLEX, INPUT IMAGES ARE OBTAINED FROM THE
UEVICE THROUGH THE LINK~GE:
L
ER

AD, PACKET ADDRESS
READA$

R~GISTER

+

5

9
SECTION:

AD CONTAINS THE ADDRESS OF THE PACKET:

E.OF,ADDRESS
'FILE NAME'

!HE Illl1!RNAL 'FILE NAME' MUST HAVE BEEN PREVIOUSLY ASSOCIATED WITH AN INPUT DEVICE PRIOR
TO !HE PIRST READA$ REFERENCE. IF !HE INPU! DEVICE IS MASS STORAGE OR TAPE, IT IS ASSUMED

PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

9
SECTION:

6

i

PAGE:

·
C
-J
~\

TO BE IN SOF FORMAT AND WILL SIMPLY BE READ. IF THE FILENAME HAS NOT BEEN DEFINED,
THE PROGRAM IS PLACED IN THE 'ERR MODE'. THE FIRST REFERENCE TO READA$ INITIATES THE
INPUT OPERATION AND CONTROL IS RETURNED UPON RECEIPT OF THE IMAGE. THE INPUT
OPERATION IS CONTINUOUS WITH INTERMEDIATE MASS STORAGE BUFFERING IN SDF FORMAT.
EACH DEVICE TYPE HAS AN END OF INPUT SENTINEL WHICH IS DEFINED AS THE QFIN
STATEMENT FOR UNIT RECORD EQUIPMENT, OR THE SDF END-OF-FILE SENTINEL FOR TAPE OR
MASS-STORAGE. WHEN REAOA$ DETECTS THE END-OF-FILE SENTINEL. THE FILE IS CLOSED (BUT
NOT FREED) AND CONTROL IS RETURNED TO THE USER AT HIS EOF RETURN.
IN ADDITION TO THE END OF INPUT SENTINEL, THE QCOL CONTROL STATEMENT AND ITS
CORRESPONDING END SENTINEL ARE INTERPRETED IN THE ALTERNATE MODE. ALL OTHER CONTROL
STATEMENTS ARE NOT INTERPRETED.
R£ADA$ FILE WILL BE CLOSED ON AN END-OF-FILE, A QFREE OF THE FILE, OR ON A
FILENAME (SEE ~BKKPT IN THE CHAPTER ON EXECUTIVE CONTROL LANGUAGE.
THE PROCEDURE:

~BRKPT

R$EADA PKT ADDRESS
GENERATES A TWO-WORD CALLING SEQUENCE. THE FIRST wORD LOADS AO WITH THE LOCATION
'PKT ADDRESS' AND THE SECOND WORD IS AN ,ER READA$'.
9.3.

PRINTs

ASSOCIATED WITH EACH RUN IS A PRINT FILE WHICH IS ESTABLISHED BY THE COARSE
SCHEDULER. THIS FILE CONTAINS THE PRINT OUTPUT GENERATED BY THE VARIOUS SYSTEM
COMPONENTS AND THE USER PROGRAMS OF THE RUN. PRINTS TRANSFERS EACH IMAGE FROM THE
USER'S AREA TO THE SYSTEM CONTROLLED IMAGE POOL. FROM THERE THE IMAGES ARE BUFFERED
TO AN INTERMEDIARY STORAGE DEVICE, OR ARE PROCESSED DIRECTLY BY THE PRINT SYMBIONT,
THE BATCH PROCEDURE IS FOR PRINT$ TO BUFFER THE FILE TO MASS STORAGE, AND FOR THE
SYMBIONT TO PROCESS THE FILE WHEN IT REACHES THE TOP OF THE QUEUE, WHEN MAGNETIC
TAPE IS DEFINED AS THE REPOSITORY MEDIUM, THE FILE IS BUFFERED DIRECTLY TO THE TAPE
UNIT. IN THE DEMAND MODE, THE FILE IS PROCESSED DIRECTLY BY THE SYMBIONT. THE
FOLLOWING LINKAGE IS USED TO TRANSMIT A PRINT IMAGE:
ER
PIUNT$
NORMAL RETURN
PHIOR TO ENTERING PRINTS, REGISTER AO MUST BE LOADED WITH THE FOLLOWING WORD:
P

L,S,N,A

WITH P DEFINED AS
P

FOHr.1

6,6,6,18

WHERE:
A- IS THE ADDRESS OF THE FIRST WORD OF THE
PRINT IMAGE.
N- IS THE NUMBEH OF WORDS TO BE TRANSFERRED TO THE PRINT FILE
BEGINNING AT LOCATION 'A,.
S- IS THE NUMBER OF LINES TO BE SPACED BEFORE PRINTING THE
IMAGE. FOR S:O, NO SPACING WILL OCCUR. WHEN 5 IS GREATER
THAN THE NUMBER OF LINES REMAINING ON THE PRINTABLE PAGE,
THE IMAGE WILL BE PRINTED ON LOGICAL LINE 1 OF THE
FOLLOWING PAGE. WHEN THE
COUNT OF AN IMAGE EXCEEDS THE NUMBER OF LINES REMAINING ON
THE CURRENT PAGE, THE IMAG.E SUBMITTED IS PRINTED ON LOGICAL
LINE 1 OF THE SUCCEEDING PAGE.
L- IS THE CARRIAGE CONTROL LOOP VALUE,

c

UNIVAC 1108 OPERATING

UP-4144

EXEC B

Rev.l

SYSTEM

PROGRAMMERS REFERENCE

9
SECTION:

THE QBRKPT STATEMENT PROVIDES THE MEANS TO ESTABLISH MASS-STORED PRINT FILE
BREAKPOINTS OR TO RE-ASSIGN THE FILE'S OUTPUT MEDIUM. WHEN RE.ASSIGNMENT OF THE
PRINT$ FILE IS SPECIFIED, ONLY THOSE PRINT IMAGES GENERATED AFTER THE QBRKPT
STATEMENT WILL RESIDE ON THE LATEST DEFINED DEVICE. THE QSYM CONTROL STATEMENT,
PREVIOUSLY DISCUSSED IN THE EXECUTIVE LANGUAGE CHAPTER OF THIS DOCUMENT , IS REQUIRED
TO QUEUE ALL PRINT FILES WHICH HAVE BEEN GENERATED IN ANY FILE OTHER THAN THE SYSTEM
DEFINED PRINT$ FILE (THIS INCLUDES BREAKPOINT TO MAGNETIC TAPE). IF THE PRINTS IS
INTENDED FOR OUTPUT .oTHEi THAN THE DEVICE ARRIVED AT BY DEVICE ASSOCIATION, IT MUST
BE QUEUED FOR THE INTENDED SYMBIONT WITH THE I01SYM CONTROL STATEMENT PRIOR TO THE END
OF THE RUN.
THE PROCEDURE:
P$RINT

PKT

WILL GENERATE A TWO WORD CALLING SEQUENCE REFERENCING PRINTS. THE FIRST WORD WILL
LOAD REGISTER AO FROM THE ADDRESS 'PKT', FOLLOWED BY AN 'ER PRINT$'.
ALTERNATE PRINT FILES (PRNTA$)
AN ADDITIONAL ENTRY INTO THE PRINT$ INTERFACE ROUTINE IS PROVIDED TO FACILITATE
THE HANDLING OF PRINT FILES OTHER THAN THE SYSTEM INITIATED PRINT FILE. THE
FOLLOWING LINKAGE IS USED TO TRANSMIT A PRINT IMAGE INTO AN ALTERNATE PRINT FILE
ER PRNTAS
NORMAL RETURN

(

PRIOR TO ENTERING PRNTA$, REGISTER AO MUST BE SET TO THE ADDRESS OF THE FOLLOWING
PACKET:
P

L,S,N,A
'FILE-NAME' (12 CHARACTERS SPACE FILLED)

THE FIELDS 'A', 'N'. '5. AND .L' AND THE FORM 'P' HAVE THE SAME DEFINITION AS
PRINT$. THE ADDITIONAL FIELD 'FILE-NAME' IS THE INTERNAL REFERENCE TO A PREVIOUSLY
FILE NAME, F2 IS
ASSIGNED DEVICE. IF 'FILENAME' IS UNDEFINED, AN QASG, CP
PERFORMED AND THE FILE IS OPENED. THE FIRST REFERENCE TO PRNTA$ INITIALIZES THE
PRINT OPERATION.
THE ALTERNATE FILES PRODUCED ARE IN SDF FORMAT. • IF THE ASSIGNED DEVICE IS A
PRINTER SUBSYSTEM, PRINTING IS INITIATED wITH THE FIRST REQUEST. INTERMEDIATE MASS
STORAGE BUFFERING IS UTILIZED WITH DIRECT PRINTING. WHEN THE SDF END-OF-FILE IS
DETECTED. THE PRINTER IS ·RELEASED.
FILE LABELS FOR ALTERNATE PRINT FILES ARE GENERATED WITH THE ,FILENAME' FIELD OF
THE PRNTA$ CALLING SEQUENCE. A QBRKPT CALL
CAUSES THE FIRST PRINT FILE TO BE CLOSED AND THE TAPE POSITIONED FOR THE NEXT FILE.
THE FIRST REFENCE TO PRNTA$ FOLLOWING THE ER QBRKPT INITIALIZES THE SUCCEEDING FILE.
PRINT FILES PROCESSED VIA THE PRNTA$ LINKAGE ARE NOT AUTOMATICALLY ENTERED INTO A
SYMBIONT PRINT QUEUE, UNLESS THE EXEC PERFORMED THE ASSIGNMENT OF THE FILE IN WHICH
CASE WHEN THE FILEIS CLOSED, IT IS QUEUED IN THE SAME MANNER AS THE PRINT$ FILE AND
THE FILE IS DECATALOGUED AFTER IT IS PRINTED. IN ALL OTHER CASES THE QSYM CONTROL
STATEMENT IS REQUIRED TO QUEUE THE GENERATED PRINT FILE.
THE PROCEDURE:
P$RNTA

PKT

GENERATES A TWO-WORDCALLING SEQUENCE REFERENCING PRNTA$. THE FIRST WORD LOADS
REGISTER AO WITH THE ADDRESS 'PKT', FOLLOWED BY AN 'ER PRNTA$'.
9.'+.

PUNCH$

7
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
REFERENCE

9
SECTION:

EACH RUN ENTERED INTO THE SYSTEM WILL HAVE A PUNCH FILE WHICH IS ESTABLISHED WITH
THE FIRST REFERENCE TO PUNCH$. THE DEFINITION OF THIS PUNCH FILE IS SPECIFIED AS
EITHER 80 COLUMN CARD IMAGES, OR AS 5,6,7 OR 8 LEVEL PAPER TAPE. THE DETERMINATION
OF THE PUNCH TYPE IS BY INPUT DEVICE ASSOCIATION. IF A DIFFERENT DEFINITION IS
REQUIRED, IT CAN BE ESTABLISHED BY A REFERENCE TO PCHCN$. REFERENCE TO THIS PUNCH
FILE IS VIA THE LINKAGE:

ER PUNCH$
NORlvlAL RETURN
PRIOR TO ENTERING PUNCH$, REGISTER AO MUST CONTAIN THE FOLLOWING WORD:
+

N,A

A- IS THE ADDRESS OF THE FIRST WORD OF THE PUNCH I~AGE
N- IS THE NUMBER OF WORDS TO BE TRANSFE~REO TO THE PUNCH
FILE BEGINNING AT LOCATION 'A'.
THE GBRKPT STATEMENT PROVIDES THE MEANS TO ESTABLISH
MASS STORED PUNCH FILE BREAKPOINTS OR TO RE-ASSIGN THE FILE'S OUTPUT MEDIUM. THE
~SYM CONTROL STATEMENT IS REQUIRED TO QUEUE ALL PUNCH FILES WHICH HAVE BEEN GENERATED
IN ANY FILE OTHER THAN THE SYSTEM DEFINED PUNCH$ FILE.
IF THE PUNCHS FILE IS INTENDED FOR OUTPUT OTHER THAN THAT DETERMINED BY DEVICE
ASSOCIATIO~, IT MUST BE QUEUED FOR THE PROPER SyMBIONT BY THE QSYM CONTROL STATEMENT
B~FORE THE END OF THE RUN.
THE PROCEDURE
P$UNCH PKT
WILL GENERATE A TWO-WORD CALLING SEQUENCE REFERENCE TO PUNCH$. THE FIRST WORD WILL
LOAD REGISTER AO FROM THE ADDRESS ,PKT', FOLLOWED BY AN .ER PUNCH$'.
ALTERNATE PUNCH FILES (PNCHA$)
AN ADDITIONAL ENTRY INTO THE PUNCH$ INTERFACE ROUTINE IS PROVIDED TO FACILITATE
THE PROCESSING Of PUNCH FILES OTHER THAN SYSTEM INITIATEQ PUNCH FILE. THE FOLLOWING
LiNKAGE IS USED TO TRANSMIT A PUNCH IMAGE
Et{ PNCHA$
NOkMAL Rt:TURN
PKIOR TO Ef~TERING PNCHA$, REGISTER AO MUST BE SET TO THE ADDRESS OF THE FOLLOWING
PACKE.T
+ N,A

'FILE NAME' (12 CHARAC?ERS SPACE FILLED)

'N'

AND 'A' HAVE THE SAME DEFINITION AS PUNCHI.
THE RULES FOR 'FILENAME' AND FILE QUEUEING ARE THE SAME AS FOR PRNTA$ FILES.
THE PROCEDURE
P$NCHA

PKT

GENERATES A TWO-WORD CALLING SEQUENCE REFERENCING PNCHA$. THE FIRST WORD LOADS
REGISTER AD WITH THE ADDRESS 'PKT', FOLLOWED BY AN 'ER PNCHA$'.
SYMBIONT CONTHOL

8
PAGE:

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

9
SECTION:

(~

THERE ARE SEVERAL CONTROL FUNCTIONS TO ALLOW THE USER A MEANS OF DIRECTING THE
SYMBIONTS TO PERFORM SPECIAL FUNCTIONS ON A FILE.
OUTPUT CONTROL
THE OUTPUT CONTRoL FUNCTIONS PROVIDE A GENERAL METHOD OF CONTROLLING SYMBIONT
OUTPUTS. EACH REQUEST INSERTS IN THE OUTPUT FILE AN IMAGE OF THE SAME FORMAT AS
STANDARD DATA, BUT WITH A FLAG INDICATING THIS IS CONTROL INFORMATION. THE SYMBIONT
OUTPUT DEVICE ROUTINES INTERPRET THIS CONTROL IMAGE AND TAKE THE APPROPRIATE ACTION,
NOTE THAT FOR MASS STORAGE OR TAPE BUFFERED FILES THIS ACTION OCCURS AT THE TIME OF
THE PHYSICAL OUTPUTTING, FOUR EXECUTIVE REQUEST FUNCTIONS CORRESPONDING TO THE
PHINT$, PUNCH$, PRNTA$, AND PNCHA$ REQUESTS ARE PROVIDED:

(

LA
EK

AQ, (N,A)
PRTCN$

LA
EK

PCHCN$

FOR PUNCH$ FILES

LA
ER

AQ, (N,A)
PRTCA$

FOR PRNTA$ FILES

LA
ER

PCHCA$

FOR PRINT$ FILES

AQ,(t~,A)

AQ,

(r~,A)

FOR PNCHA$ FILES

FOR ALL CALLING SEQUENCES, ,N, IS THE LENGTH OF THE PACKET IN WORDS WHICH BEGINS
AT ADDRESS ~A'. FOR PRINT$ AND PUNCH$ N IS
OF THE CHARACTER STRING OR IMAGE WHICH DEFINES THE CONTROL FUNCTION. IT MAY BE
CODED:
.IMAGE'
FOR ALTERNATE FILES THE PACKET CONTAINS TWO ADDITIONAL WORDS AT THE BEGINNING
NAMING THE FILE:
,FILENAME'
'IMAGE'

(12 CHARACTERS SPACE FILLED)

EACH IMAGE CONSISTS OF ONE OR MORE CONTROL FUNCTIO~S. SPACES ARE IGNORED PRIOR TO
THE FIRST, OR BETWEEN FUNCTIONS. EACH FUNCTION BEGINS WITH A SINGLE LETTER, FOLLOWED
BY A COMMA FOLLOWED BY ANY SPECIAL INFORMATION REQUIRED, AND ENDED BY A PERIOD THE
FORMAT OF THE IN~ORMATION CHARACTER STRING VARIES ACCORDING TO THE FUNCTION BUT MUST
NOT CONTAIN A PERIOD.
PRTCN$ CONTROL FUNCTIONS
THE FOLLOWING CONTROL FUNCTIONS ARE DEFINED FOR PRINT FILES:
L- SPACE PRINTER TO LOGICAL LINE ,NN', WHERE LOGICAL LINE IS
DEFINED AS THE LINE NUMtlER RELATIVE TO THE TOP MARGIN
SETTI~G.
.
3. DEPRESS THE 'SIGNAL REMOTE' SWITCH IN THE 'SYSTEM
CONTROL' SECTION.
4. PLACE THE SPECIAL CONTROL CARD(S) INTO THE INPUT HOPPER
5. PLACE THE ,RUN/STOP' SWITCH IN THE 'RUN' POSITION AND
DEPRESS THE 'GENERAL CLEAR' SWITCH.
6. SWITCH TO ,UNATTENDED' MODE OF OPERATION
7. DEPRESS THE .CARD FEED', 'CARD CLEAR', AND 'TRANSMIT'
SWITCHES ONCE AND IN ORDER.
THE SPECIAL CONTROL CARD WILL BE READ AND THE INDICATED ACTION TAKEN. (SEE 9.10.2 FOR
A DESCRIPTION OF THE SPECIAL CONTROL CARDS)

()

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

INPUT/OUTPUT DEVICE HANDLERS

10.

10. 1 •

I/O CONTROL

GENERAL

10.1.1.

INPUT/OUTPUT OPERATIONS ARE CONTROLLED BY MEANS OF A CENTRAL ROUTINE. IT MAY BE
THOUGHT OF AS THE MASTER DEVICE HANDLER ACCEPTING AND QUEUEING REQUESTS AND
INTERRUPTS AND GIVING CONTROL OF THEM TO THE I/O DEVICE HANDLER, WHEN APPROPRIATE.
PARTIAL DUAL CHANNELS, FULL DUAL CHANNELS, DUAL-COMPUTER CHANNELS, AND ESI CHANNELS
REQUIRE SPECIAL TREATMENT. PARTIAL-DUAL AND FULL-DUAL. A SPECIAL MECHANISM IS USED
TO SERVE AS A COMMON ROUTINE FOR TREATMENT OF WAIT-TYPE ER.S, AND
INTERRUPT-REQUEST-TyPE ER'S. OTHER SUBROUTINES COMMON TO ALL THE HANDLERS .ARE
CONTAINED ~ITHIN CENTRAL CONTROL, SUCH AS THE CONVERSION OF A USER'S ACCESS WORD FROM
RELATIVE TO ABSOLUTE AND CHECKING IT AGAINST HIS ASSIGNED AREA OF CORE.
REFERENCE TO I/O CONTROL IS DEPENDENT UPON THE CLASS OF EQUIPMENT BEING REFERRED:
COMMUNICATIONS DEVICES,
MAGNETIC DRUM OR TAPE, OR
LOW-SPEED ON-SITE DEVICES.
THE COMMUNICATIONS DEVICES ARE REFERENCED VIA A SPECIAL HANDLER DESCRIBED IN
SECTION 6 BELOW. THE SYMBI'ONTS CONTROL THE LOW-SPEED ON-SITE DEVICES VIA THE
ARBITRARY DEVICE HANDLER. THIS HANDLER IS ALSO AVAILABLE TO OTHER ROUTINES SUCH AS
MAINTENANCE ROUTINES AND SpECIAL HANDLING OF PERIPHERAL DEVICES. FOR REFERENCING TAPE
AND DRUM UNITS THE STANDARD BASIC LEVEL CONSISTS OF THE PACKET MODE USING AN
EXECUTIVE'RETURN INSTRUCTION AND AO LOADED WITH THE PACKET ADDRESS AS FOLLOWS:
LA
ER

AO,PKT AUUR
ENTRANCE TAG

THE ENTRANCE TAG CAN BE ONE OF THE FOLLOWING

('

10$

INITIATE THE REQUESTED OPERATION AND RETURN CONTROL
IN-LINE IMMEDIATELY. PROGRAM ACTIVITY CONTINUES WITH
THE ASSUMPTION'THAT A WAIT ON COMPLETION IS CODED AT A
SUBSEQUENT POINT FOR PROPER SYNCHRONIZATION.

lOWS

INITIATE THE REQUESTED OPERATION AND RETURN CONTROL
AFTER THE OPERATION IS COMPLETED. NO FURTHER
SYNCHRONIZATION IS NEEDED. THIS ENTRANCE SAVES THE
TIME REQUIRED TO STORE AND RESTORE ICR IF FURTHER
OPERATION IS DEPENDENT UPON THE I/O COMPLETION.

IOXIS

INITIATE THE REQUESTED OPERATION AND EXIT. UPON
COMPLETION OF THE OPERATION CONTROL IS GIVEN TO THE
INTERRUPT ROUTINE DEFINED BELOW. THIS ENTRANCE CAN
BE USEU ONLY IF AN INTERRUPT ROUTINE ADDRESS IS
SPECIFIED. THE EXIT AND RESTART AS AN INTERRUPT
ROUTINE INCREASES THE COMPLETION PRIORITY AND SAVES
THE TIME NEEDED TO STORE AND RESTORE THE CONTRoL
REGISTER SET.

lOIS

SAME AS 10$ WITH THE ADDITION OF AN INTERRUPT ROUTINE
INITIATED AT COMPLETION OF THE I/O REQUEST.

10WI$

SAME AS IOW$ WITH THE ADDITION OF THE COMPLETION

PAGE:

1

UNIVAC 1108' OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

2
PAGE:

o
INTERRUPT ROUTINE.
IN MANY RESPECTS THE INTERRUPT ACTIVITY IS THE SAME AS ALL. OTHER REGIStERED
ACTIVITIES USING THE FORK FUNCTION. IT DIFFERS IN THE FOL.LOWING AREAS:
THE PRIORITY OF THE ACTIVITY IS RAISED TO THE HIGHEST
POSSIBL.E LEVEL WITHIN THE PROGRAM CL.ASS OF THIS' WORKER, I.E.
FOR A BATCH WORKER PROGRAM THESE I/O COMPLETION ACTIVITIES
WILL RECEIVE CONTROL BEFORE ANY OTHER BATCH PROGRAM
ACTIVITY •
THE INTERRUPT ROUTINE IS NOT INTERRUPTABLE IN FAVOR OF ANY
OTHER SIMIL.AR ACTIVITY OF THE SAME PROGRAM, AL.L ARE QUEUED
IN A FIRST-IN-FIRST-OUT LIST OF ALL PROGRAMS WITHOUT REGARD
TO PRIORITY WITHIN THE CLASS.
.
ANY EXEC SERVICE REQUEST REMOVES THE INTERRUPT ACTIVITY FROM
THE HIGH PRIORITY LIST AND PUTS IT BACK ~ITHIN THE WORKER
PROGRAM.
THE CM ~UBSET IN THE INTERRUPT ROUTINE IS LIMITED TO Bll,
AO THROUGH AS, AND Rl THROUGH R3. THE AO REGISTER IS
PASSEP·ON TO THE INTERRUPT ROUTINE FROM THE CONTENTS AT THE
REFERENCE TO I/O CONTROL.. IF THE SUPPRESS RECOVERY MODE
IS SET, THE Al REGISTER IS LOADED WITH THE STATUS WORD FROM
THE SUBSYSTEM EXTERNAL INTERRUPT.
IN THE ABSENCE OF ANY OTHER EXEC SERVICE REQUEST THE NORMAL PROGRAM STATUS CAN
BE RESTORED BY USING THE UNLCK$ FUNCTION (SEE EXECUTIVE REQUEST SECTION).
EVERY ATTEMPT IS MADE IN THE MULTIPROGRAMMING ENVIRONMENT TO PROVIDE PROPER
SWITCHING ALLOWING IMMEUIAT~ACCESS TO THE AMOUNT OF cOMPUTATION REQUIRED TO INITIATE
ANOTH~R 1/0 OPERATION FOLLOWING ANY OTHER 1/0 COMPLETION.
THE DIFFICULTY LIES IN
EFFECTIVELY PREVENTING ABUSE OF THE HIGH PRIORITY PROVISIONS MADE FOR THE INTERRUPT
ACTIVITIES. THE INTENT IS TO LIMIT THE FACIL.ITY AVAILABLE TO NO MORE THAN THAT
NECESSARY TO REQUEST ANOTHER 1/0 OPERATION HAVING CHECKED THE STATUS OF THE LAST.
10.1.2.

QUEUEING AND UNIT CONTROL

THE REFERENCES TO 1/0 CONTROL RESULT IN ENTERING THE HANDL.ER CONTROLLING THE
DEVICE REFERENCED. THE HANDLER HJ TURN CONSIDERS THE REQUEST AND QUEUES IT FOR THE
PARTICULAR SUBSYSTEM. WHEN THESUBSYSr.EM bECOMES FREE AN ENTRY IS REMOVED FROM THE
SUBSYSTEM QUEUE AND THE HANDLER IS ENTERED AT THE APPROPRIATE POINT. QUEUING IS
BYPASSED IF THE SUBSYSTEM IS INITIALLy NOT BUSY.
THE CHANNEL REQUEST QUEUE AND INTERRUPT QUeUE CONTAIN INFORMATION TO DIRECT THE
ATTENTION OF ThE DEVICE HANDLERS TO TH~ UNIT (AND wHERE REQUIRED. TO THE FILE) WITH
WHICH THE REQUEST OR INTERRUPT IS ASSOCIATED.
AN AID TO THE USER FOR DETECTION OF A LOOP IN A NONDEBUGGED PROGRAM WHICH INCLUDES
A REFERENCE TO 1/0 IS A NEGATIVE TEST ON THE;jORD of THE PACKET CON"(AINING THE STATUS
CODE (THE PACKtT IS DEFINED IN THE NEXT SECTION). WHEN AN 1/0 REQUEST IS MADE BY THE
USER THE EXEC SETS THE STATUS WORD NEGATIVE TO INDICATE AN IN-PROGRESS STATE. BEFORE
SETTJNG THE WORD NEGATIVE A CHECK IS MADE TO SEE IF IT IS ALREADY NEGATIVE,
INPICATING A POSSIBLE LOOP, IN WHICH CASE A UNiQUE STATUS CODE IS PLACED IN THE
PACKET AND CONTROL IS GIVEN TO THE 'ERR MODE' ROUTINE OF THE USER IF ONE EXISTS. FOR
A~L COMPLETIONS OF PACKETS A POSITIVE VALUE IS ALWAYS PLACED IN ~HE STATUS WORD HENCE
NO HOUSEKEEPING IS NECESSARY BY THE USER AND AN INITIAL NEGATIVE VALUE cAN BE
CORRECTLY INTERPRETED AS A SOFTWARE LOGIC ERROR.
EFFICIENT UTILIZATION OF ALL DRUM TYPES INCLUDING FASTRANO DICTATES THAT SERVICING
REQUESTS FOR A GIVEN FILE WILL NOT BE RESTRICTED TO THE ORDER OF SuBMISSION. THIS
ALLOWS A SPEEDUP OF SEHVICING BY INCLUSION OF THE ,SEND ANGUL.AR ADDRESS. FUNCTION AND

C

UP-4144

UNIVAC 1108 OPERATING

Rev.!

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

3
PAGE:

(
THE FACT THAT FILES MAY BE ALLOCATED ACROSS UNITS AND HENCE ACROSS ACCESS PATHS.
TESTING EACH PACKET IS NECESSARY TO INSURE COMPLETION, AND DO NOT ASSUME COMPLETION
BY TESTING A SUBSEQUENT PACKET.
FOR ALL REFERENCES TO I/O CONTROL VIA NONSYNCHRONOUS"ER'S FOR ALL TYPES OF DEVICES,
IT IS NECESSARy TO TEST THE STATUS CODE FOR COMPLETION OF I/O BEFORE EXITING FROM AN
ACTIVITY. UPON ACTIVITY EXIT, EITHER NORMAL OR ABNORMAL, LISTED I/O REQUESTS MAY BE
DISREGARDED WITHOUT SERVICING THE REQUEST.
10.1.3.

INPUT/OUTPUT PACKET

PRIOR TO EXECUTING THE ER INSTRUCTION TO REFERENCE THE TAPE OR DRUM HANDLER, THE
AQ REGISTER MUST BE LOADED WITH THE ADDRESS OF AN INPUT/OUTPUT PACKET. THIS PACKET IS
THE FIRST PART OF THE FILE CONTROL TABLE IF THE BLOCK BUFFERING OR ITEM HANDLING
ROUTINES ARE USED. THE LENGTH OF THE REQUEST PACKET CAN VARY FROM FOUR TO EIGHT WORDS
DEPENDING UPON THE OPERATION DESIRED. THE FORMAT OF THE PACKET IS AS FOLLOWS:

(

-----.-------~----.---.----.-.---~- --~

]P-4144

UNIVAC 1108

OPERATING

Rev. 1

EXEC B

PROGRAMMERS REFERENCE

35

01

29

23

SYSTEM

17

11

10
SECTION:

05

4
PAGE:

00

-----------------------------------------------.-------------INTERNAL FILE NAME (WORD 1)

02 ---------------------------------------------------~---------INTERNAL FILE NAME (WORD 2)

-._--'------------------------------------------.-----

03 :USED BY EXEC,

..

------~-

:INT ACT 10: INTERRUPT ACTIVITY START

06

-----------------------------------------------.-------------: STATUS :FUNCTION: AFC
SUBSTATUS FIELD
------------------------------------------------------------.ACCESS WORD
-------------------------------------------------------------DRUM ADDRESS

07

---------------------------~---------------------------------SEARCH IDENTIFIER

O~

05

OB

--------------------------------------.----------------------SEARCH ~IND DRUM ADDRESS

------.--------------~---------------------------------------WORD 1 AND WORD 2- THE INTERNAL FILE NAME US£O IN ALL REFERENCES
TO THE FILE. THIS NAME IS EITHER THE SAME AS SOME EXTERNAL
FILE NAME OF THE ~ASG STATEMENT OR IS ATTACHED TO AN
EXTERNAL FILE NAME BY A QUSE STATEMENT.

WORD 3 TI-USED BY THE EXEC TO ASSOCIATE THE INTERNAL FILE NAME
TO AN EXEC TABLE LOCATION.
53-THE NUMERIC IDENTITY (1-35) USED TO IDENTIFY THE
INTERRUPT ACTIVITY IF SYNCHRONIZATION IS INTENDED WITH
SOME OTHER ACTIVITY.
H2-INTERRUPT ACTIVITY STARTING ADDRESS. THIS IS THE
LOCATION AT WHICH THE WORKER RECEIVES CONTROL UPON
OCCURRENCE OF AN INTERRUPT SIGNIFYING COMPLETION OF
THE I/O OPERATION,
WORD

~

Sl-THE STATUS OF THE LAST FUNCTION PERFORMED.
52-THE CODE DENOTING THE FUNCTION TO BE PERFORMED.
S3-AFC- FOR MAGNETIC TAPE FILES IF THE CHARACTER COUNT
IS NOT A MULTIPLE OF 6(FOR 7-CHANNELS PER FRAME
DRIVES)OR A MULTIPLE OF 9 (FOR 9-CHANNELS PER FRAME)
THIS SIXTH OF A WORD CONTAINS THE NUMBER OF CHARACTERS
IN THE LAST WORD READ (FIRST WORD OF THE BUFFER FOR A
READ BACKWARD), THIS USED FIELD IS IN CONJUNTION WITH
A STATUS CODE OF 04. IF THE ACCESS WORD DOES NOT HAVE
A WORD COUNT LARGE ENOUGH TO ALLOW TRANSFER OF THE
ENTIRE BLOCK AND A STATUS CODE OF O~ IS RETURNED, THIS
FIELD IS SET TO ZERO.(FOR IVC UNITS IF THE ACCESS WORD
GOES TO ZERO, IT IS INDETERMINATE WHETHER ALL WORDS
WERE READ. IF ALL WORDS OF THE BLOCK ARE READ, AS
DETERMINED BY THE USER, THEN THE COUNT OF FRAMES OF
DATA IN THE LAST WORD READ IS STORED IN THE LOWER
SIXTH OF THE LAST DATA WORD.) FOR 9-CHANNEL TAPES, THE
COUNT IS THE NUMBER OF 8-BITBYTES ASSEMBLED AND
TRANSFERRED TO THE COMPUTER IN THE LAST 2-WORD SEQUENCE
I.E. A VALUE OF 1 INDICATES AN ODD NUMBER OF WORDS
WITH ONE 8-BIT BYTE ASSEMBLED IN THE FINAL WORD AND THE
REMAINDER OF THE WORD PADDED WITH ZEROES • A VALUE OF
5 INDICATES AN EVEN NUMBER OF WORDS wITH 4 DATA BITS IN
THE LAST WORD WHICH ARE THE LEAST SIGNIFICANT HALF OF
THE 8-BIT BYTE WITH THE MOST SIGNIFICANT 4 BITS IN THE
PRECI:.DING WORD.
H2-AUXILIARY STATUS INFORMATION. FOR ANY FUNCTION
INVOLVING INPUT TRANSFER, THIS FIELD WILL CONTAIN THE
EXACT NUMBER OF WORDS READ. FOR MAGNETIC TAPE OR THE
END OF A DRUM FILE, THIS NUMBER MAY DIFFER FROM THE

()

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

10

PROGRAMMERS REFERENCE

SECTION:

(ACCESS WORD,
WORD 5 THE FIFTH WORD OF THE PACKET IS AN I/O ACCESS WORD
SPECIFIED IN THE FORMAT DEFINED IN THE UNIVAC 1108
MULTI-PROCESSOR SYSTEM DESCRIPTION, UP-4046 REV.l. THAT
IS, BITS 35-34 ARE THE INCREMENT-DECREMENT DESIGNATOR,
BITS 33-18 CONTAl~ THE NUMBER OF WORDS TO TRANSFER, AND
BITSl7-00 CONTAIN THE ADDRESS AT WHICH TRANSFER IS TO
BEGIN. FOR GW$,SCR$,AND SCRB$ FUNCTIONS, THIS WORD
CONTAINS THE NUMBER OF ACCESS WORDS AND THE ADDRESS AT
WHICH THE STRING OF ACCESS WORDS BEGIN.
WORD 6 FOR MAGNETIC DRUM FILES, THIS WORD CONTAINS THE MASS
STORAGE ADDRESS AT WHICH THE DESCRIBED I/O oPERATION IS TO
START. THIS ADDRESS IS RELATIVE TO THE START OF THE MASS
STORAGE FILEI THE HANDLER PROVIDES FOR DETERMiNING THE
ABSOLUTE POSITION. FOR FASTRAND FILES (OR SIMULATED
FASTRAND ON OTHER TyPE DRUM) THE ADDRESS IS THE START OF A
SECTOR AND CONSECUTIVE ADDRESSES ARE 28 WORDS APART,
WORD 7 THIS WORD IS THE IDENTIFIER WORD FOR SEARCH OPERATIONS.
WORD 8 THE FINO ADDRESS FOR A DRUM SEARCH IS RETURNED IN THIS
WORD. THE ADDRESS IS RELATIVE TO THE START OF THE FILE.
WHENEVER THE INPUT/OUTPUT FUNCTION IS REQUESTED WITH AN INTERRUPT COMPLETION
ACTIVITY, WORD 3 OF THE PACKET MUST BE CODED AS OUTLINED. THIS WORD DESCRIBES THE
~INKAGE TO THE WORKER PROGRAM FOR HIGH PRIORITY PACKET PROCESSING.
THE PRIORITY IS
SET TO ~EVEL 1 WITHIN THE PROGRAM TYPE (SEE SUPERVISOR CHAPTER), THE INTERRUPT
ACTIVITY IS LIMITED TO THE MINOR SET OF CONTROL REGISTERS. THE INTERRUPT ACTIVITY
STARTING ADDRESS MUST BE A NONZERO VALUE. IF NO SYNCHRONIZATION IS INTENDED THE
NUMERIC IDENTITY FOR THE INTERRUPT ACTIVITY IS NOT NEEDED,
THE SY?TEM PROCEDURES AVAILABLE TO GENERATE I/O REQUEST PACKETS FOR DRUM AND TAPE
ARE:
1$00
I$OT

U, F , I NT ADDR,-I NT ID
U,F,INT ADDR,INT 10

COUNT, ADDR, I I~C
COUNT,ADDR,INC

DRUM ADDR, SENT

WHERE:
U-IS THE SYMBOLIC FILE NAME ASSOCIATED WITH THE UNIT BEING
REFERENCED
F-IS THE SYMBOLIC OR OCTAL CODE IDENTIFYING THE FUNCTION (SEE
TABLE 10-1>
INT ADDR-IS THE INTERRUPT ROUTINE STARTING ADDRESS
INT IO-IS THE INTERRUPT ROUTINE IDENTITY (1-35). IF OMITTED THIS
FIELD IS SET TO ZERO.
COUNT,ADDR,INC-5PECIFIES THE CORE AREA TO TRANSFER TO OR FROM.
THE INC FIELD CAN BE OMITTED IF INCREMENTATION IS DESIRED,
GIVEN THE SyM~OL 0 FOR DECREMENTATION OR N FOR NO
lNCREMENTING OR DECREMENTING
DRUM ADDR, SENT-IDENTIFY THE STARTING POINT AND, IF A SEARCH
OPERATION, THE SEARCH SENTINEL.
.
THE TAG ON THE PROCEDURE LINE IS ALLOCATED TO THE FIRST WORD OF THE FILE NAME. THE
I$OD PROCEDURE GENERATES SIX OR EIGHT WORDS DEPENDING UPON THE PRESENCE OF THE SENT
FIELD. THE I$OT PROCEDURE
GENERATES FIVE WORDS REGARDLESS OF THE FIELDS CODED.
10.1.4.

PROGRAM-I/O SYNCHRONIZATION

THE ABILITY OF A WORKER PROGRAM TO SYNCHRONIZE WITH THE COMPLETION OF AN I/O
OPERATION IS AVAILABLE THROUGfi ENTRANCE TO THE EXECUTIVE VIA AN ER INSTRUCTION WITH

5
PAGE:

.UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

10
'

AN OPERAND OF WAIT$ OR WANY$.
THE ENTHY WAIT$ WAITS FOR COMPLETION OF A PARTICULAR 1/0 REQUEST. THE WANY$ ENTRY
SYNCHRONIZES WITH ANY 110 REQUEST COMPL£TION FOR THE ACTIVITY. THE TEST MADE WITHIN
THE EXEC ON A WANY$ REQUEST IS TO DE~ERMINE IF ANY 110 REQUEST HAS BEEN COMPLETED FOR
THE ACTIVITY SlNCE:: THE LAST TIME THE ACTIVITY WAS PLACED IN AWAIT CONDITION BY A
PREVIOUS WAIT$ Ok WANY$ REQUEST.
.
WHENEVER A PROGRAM SUBMITS. A REQUEST TO EXEC FOR AN 1/0 OPERATION, THE EXEC SETS
THE FOURTH WORD OF THE PACKET NEGATIVE. THIS WORD WILL REMAIN NEGATIVE UNTIL THE
HE QUEST IS COMPLETELY SERVICED AND CAN BE USED BY THE PROGRAM TO DETERMINE WHETHER OR
NOT A REFERENCE TO WAIT$ OR WANY$ IS REQUIRED.
THE LINKAGE TO WAIT$ MUST BE PRECEDED BY A TEST POSITIVE INSTRUCTION ON WORD 4 OF
THE PACKET:
TP
EK

PKT AD[JR+3
WAIT$

THE NECESSITY OF EXEC PERFORMING THE SAME TEST INSTRUCTION A SECOND TIME TO
DETERMINE COMPLETION OF THE REQUEST BETWEEN THE TP AND ER REQUIRES THAT THE H AND I
DESIGNATORS OF THE INSTRUCTION BE SET TO ZERO. THE PACKET ADDRESS IS THE SPECIFIC
REQUEST WAITED FOR AT WAIT$.
THE REFERENCE TO WANY$:
EN

"

WANY$

NEED NOrSE PRECEDED BY ANy TEST INSTRUCTION. THE ONLY REQUIREMENT IS THAT AT LEAST
ONE I/O REQUEST MUST HAVE AEEN SUBMITTED SINCE TH5 LAST REFERENCE TO WAIT$ OR WANY$.
THIS ASSISTS THE EXEC IN DETECTING LOOPS IN U~DEBUGGED PROGRAMS.
.
ACTIVITIES WHICH ATTEMPT TO RELEASE CONTROL TO WAITS OR WANY$ WITHOUT AN
OUTSTANOING REGUESTOR WITHOUT A LEGAL'TEST POSITIVE (WAIT$ ONLy) CALL WILL EITHER BE
TLRMINATED OR WILL REGAIN CONTROL AT THE ERROR MODE RETURN. THE ERROR TYPE FOR THIS
TERMINATION IS 04 AND THE ERROR CODE IS 01 (NO OUTSTANDING REGUESTS)OR 02(ILLEGAL
TEST). UPON COMPLETION OF AN I/O REQUEST ONLy THE SUBMITTING ACTIVITY IS CHECKED TO
8E IN A WAIT CONDITION, THEREFORE IT IS NOT AOVISABLE FOR ONE ACTIVITY TO GO TO WAIT$
Ok WANY$ TO WAIT ON A REQUEST SUBMITTED BY A DIFFERENT ACTIVITY.
.
10.l.4.l.

STATUS CODES

UPON COMPLETION OF AN I/O REQUEST, A STATUS CODE IS STORED INTO S1 OF THE FOURTH
ALL CODES FROM
20 TO 37 CAUSE THE PROGRAM TO BE TERMINATED AND ARE HENCE NOT OBSERVED BY THE
EXECUTING PROGRAM UNLESS AN ERROR TERMINATION ACTIVITY IS CALLED (PREVIOUS REFERENCE
TO IERR$). IF CONTROL IS GIVEN TO THE ERROR TERMINATION ACTIVITY, ANY INTERRUPT
ACTIVITIES SPECIFIED BY THE REQUEST ARE DELETED. THE EXCEPTION TO THIS RULE IS IOXI$
IN WHICfi CASE THE INTERRUPT ACTIVITY ITSELF Is GIVEN cONTROL AT THE ERROR TERMINATION
ACTIVITY ENTRANCE.
.
WORU OF THE REQUEST PACKET DENOTING THE CONDITIONS OF THE COMPLETION.

OCTAL
COD~

DEFINITION

ou

THE REQUEST HAS BEEN COMPLETED NORMALLy. IF DATA TRANSFER
IS INVQLVEU, THE COUNT IS GIVEN IN H2 OF WORD 4.

01

END-OF-FILE SLOCK DETECTED ON MAGNETIC TAPE, AN ANSWER
OF 'E' TO AN I/O ERROR MESSAGE, A BLOCK READ DRUM FUNCTION WAS TRUNCATED BY
ENCOUNTERING AN END-OF-SLOCK WORD, OR A FIND WAS MADE ON A MASS STORAGE DEVICE
SEAHCH ANI) THEN THE END OF THE ASSIGNEU AREA (OR END-OF-BLOCK SENTINEL FOR
tiLOCK SEARCH READ) WAS ENCOUNTERED 8EF0RE THE SPECIFIED WORD COUNT WAS
TRA;JSF£I<.RED. TH~ COUNT ACTUALLY TRANSFERRED IS SPECIFIED IN H2 OF WORD 4 OF
THE PACKET. STATUS 00 IS KETURNED IF TRANSFER IS COMPLETED AFTER THE SEARCH

6
I"AGE:

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

OR IF NO TRANSFER IS INVOLVED.
WHICH THE FIND WAS MADE.

10
SECTION:

WORD 8 GIVES THE RELATIVE DRUM ADDRESS AT

02

END-OF-TAPE MARK ENCOUNTERED ON MAGNETIC TAPE ON A
READ BACKWARD FROM LOAD POINT OR ON A WRITE. NO
TRANSFER TAKES PLACE FOR THE READ BACKwARD. THE WRITE
IS DONE IN THE NORMAL MANNER. SUBSEQUENT WRITES
ARE PERFORMED IN THE SAME FASHION AND, BARRING OTHER
PROBLEMS, WILL RESULT IN RETURNING THE SAME STATUS CODE.

03

NO 'FIND' WAS MADE ON A MASS STORAGE DEVICE SEARCH. THE
SEARCH WAS TERMINATED BY AN END-OF-BLOCK, END-OF-TRACK,
END-OF-PoSITION, OR EXPIRATION OF SUFFICIENT TIME TO PASS
OVER THE ENTIRE AREA OF CONCERN DEPENDING UPON THE
PHYSICAL DEVICE AND TYPE OF SEARCH.

04

A NON INTEGRAL BLOCK WAS READ FROM MAGNETIC TAPE. THE
NUMBER OF DATA CHARACTERS ACCEPTED FROM THE LAST WORD
IS INDICATED BY 53 OF WORD 4 OF THE PACKET AND IS
EXPLAINED IN DETAIL IN SECTION 10.1.3

05

AN ATTEMPT WAS MADE TO INITIATE A MASS STORAGE SEARCH OR
READ FROM AN AREA WHICH IS WHOLLY OR PARTIALLY UNASSIGNED.
IF THE STARTING ADDRESS IS LEGAL THE READ IS TRUNCATED AS
REFLECTED BY THE WORD COUNT IN THE SUBSTATUS FIELD.

10

THE AREA OF THE FASTRAND FILE BEING UNLOCKED BY THIS
WRITE OR UNLOCK REQUEST TIMED OUT IN THE LOCKING LIST
OR A SUeSEQUENT REQUEST BY THE SAME ACTIVITY HAD A
PACKET FORMAT ERROR DETECTED BETWEEN THE TIME OF
SUBMITTING THE REQUEST AND THE TIME OF SERVICING.
OTHER REQUESTS BY OTHER ACTIVITIES FOR THE AREA MAY HAVE
~EEN HONORED IN THE INTERIM.
IF THE FUNCTION IS WRITE,
THE TRANSFER IS NOT PERFORMED.

11

A NONRECOVERABLE ERROR HAS OCCURRED AND EITHER THE
SUPPRESS RECOVERY MODE IS SET FOR MAGNETIC TAPE
OR AN ANSWER OF 'G' WAS GIVEN TO AN ERROR MESSAGE.
IF THE SUPPRESS RECOVERY MODE IS SET, THE EI STATUS
CODE IS STORED IN Al OF THE INTERRUPT ACTIVITY CONTROL
REGISTER SET.

12

A READ, OR WRITE ERROR ON MAGNETIC TAPE HAS RESULTED IN
LOSS OF POSlTION ON THE UNIT. THIS CODE IS RETURNED FOR
ALL OUTSTANDING REQUESTS AT THE TIME THE ANSWER OF 'B'
WAS ENTERED IN RESPONSE TO THE I/O ERROR MESSAGE. ANY
SUBSEQUENT REQUESTS WILL BE HONORED BUT THE LOST POSITION
IS MAINTAINED ANU NO FURTHER PROGRAM CHECKPOINTS WILL BE
VALID.

U

THE PERIPHERAL UNIT WAS DECLARED DOWN EITHER BY AN
UNSOLICITED OPERATION KEYIN OR IN RESPONSE TO AN
~RROR MESSAGE TYPED AFTER THE NORMAL RECOVERY FAILED TO
RESOLVE A MALFUNCTION.
.

17

(EXEC REFERENCE ONLY) AN AT~EMPT WAS MADE TO REFERENCE A
FILE FOR WHICH NO ASSIGMENT HAS BEEN MADE. THE FILE
DESCRIPTION AREA EXAMINED FOR THE NAME IS EITHER THE
EXECUTIVE FILES DESCRIPTION OR A RUN ASSOCIATED AREA AS
DEFINED BY THE REQUESTING EXECUTIV~ ~OUTINE.

20

SOME FOR,." OF WRITE OR A FUNCTION CAUSIIlG AREA RELEASE WAS
ATTEMPTED ON A FILE ASSIGNED IN THE READ ONLY MODE, OR
A FORM OF HEAD WAS ATTEMPTED ON A FILE IN THE WRITE ONLY

7

PAGE:

UP-4144

UNIVAC 110BOPERATING' SYSTEM

Rev. 1

EXEC

a

PROGRAMMERS REFERENCE

10
SECTION:

8
PAGE:

MODE.
21

AN ATTEMPT WAS MADE TO REFERENCE A FILE NAME FOR WHICH
NO ASSIGNMENT HAS BEEN MADE.

22

AN ATTEMPT WAS MADE TO REFERENCE AN UNASSIGNED AREA OF A
DRUM FORMAT MASS STORAGE FILE OR PAST THE MAXIMUM ASSIGNMENT FOR A FASTRANO FORMAT FILE.

23

THE ADDRESS SPECIFIED IN THE AO REGISTER IS NOT WITHIN THE
PROGRAM LIMITS OR DEFINES A PACKET SPLIT BETWEEN THE
INSTRUCTION AND DATA BANKS OF THE PROGRAM.

24

THE FUNCTION CODE IS NOT DEFINED FOR THE ASSIGNED
EQUIPMENT TYPE, THIS CODE ALSO COVERS NONCOMPATIBLE FIELDS
ON A SET MODE REQUEST.

25

THE 1/0 ACCESS WORD REFERS TO A BUFFER WHICH IS WHOLLY OR
PARTIALLY OUTSIDE OF THE PROGRAM AREA OR SPLIT BETWEEN THE
INSTRUCTION AND DATA BANK OF THE PROGRAM. FOR GW$,
SCR$,AND SCRB$ FUNCTIONS THIS ERROR CODE IS GIVEN IF
THE NUMBER OF ACCESS WORDS ISO OR MORE THAN 50 OR
IF THE TOTAL WORD COUNT IS MORE THAN o5K.

26

ILLEGAL INTERRUPT ROUTINE STARTING ADDRESS.

27

AN 1/0 REQUEST WAS MADE WITH THE STATUS WORD OF
THE REQUEST PACKET SET NEGATlVE INDICATING A POSSIBLE
PROGRAM LOOP.

030

THE INTERRUPT ACTIVITY SPECIFIED IS GREATER THAN 35 OR IS
ALREAOy IN USE.

031

A MAGNETIC TAPE OPERATION WAS ISSUED WITH USER RECOVERY
SPECIFIED AND AN INTERRUPT ACTIVITY WAS NOT SPECIFIED,

40

THE REQUEST IS EITHER IN THE PROCESS OF BEING EXECUTED OR
IS LISTED ON THE REQUEST QUEUE FOR THE PARTICULAR CHANNEL.

10.1.5.

ERROR MESSAGES

FOt{ EACH 110 FUNCTION ON MAGNETIC TAPE OR DRUM, THE EXEC HAS A sTANDARD RECOVERY
PROCEDURE FOR EACH POSSIBLE MALFUNCTION WHICH MAY OCCUR. IF AN ABNORMAL STATUS IS
KETURNED FOR AN 1/0 FUNCTION AND THE USER HAS NOT SUPPRESSED RECOVERY FOR THE
FUNCTION (SEE SECTION 2 BELOW), THE EXEC WILL INITIATE THE STANDARD PROCEDURE FOR THE
PARTlCULAR FUNCTION TO ATTEMPT RECOVERY. IN THE EVENT THAT RECOVERY IS NOT
SUCCESSFUL AN ERROR MESSAGE IS DISPLAYED ON THE CONSOLE IN THE FOLLOWING FORMAT:
CIU

FUNC ERROR RESPONSE

WHE::RE
IS FILLED IN WITH THE CHANNEL AND UNIT OR PHYSICAL
ADDRESS AT WHICH THE ERROR OCCURRED.
FUI'lC
IS THE MNEMONIC OF THE FUNCTION BEING PERFORMED I.E.
READF, REAOU, WRITE, WREOF, ETC.
ERROR IS AN INDICATION OF THE TYPE OF ERROR I.E. PARITY, ABNFC
FOR ABNORMAL FRAME COUNT, INTLK FOR INTERLOCK, ETC.
RESPONSE IS ONE OR MORE LETTERS WHICH THE OPERATOR MAY
E~TER AS A RESPONSE TO THE MESSAGE AS FOLLOWS:

CIU

A-TRY ISSUING THE FUNCTION AGAIN WITH STANDARD RECOVERY
B-RETURN BAD POSITION CODE OF 12 TO THE PACKET
D-OECLARE DEVICE DOwN AND RETURN A CODE OF 13 TO THE

c

-----------

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

PACKET. THE DOWNED UNIT IS NOT CONSIDERED FOR REUSE
UNTIL BROUGHT ~ACK INTO THE AVAILABLE POOL BY AN 'UP'
UNSOLICITED MESSAGE.
E-TREAT AS AN END-OF-FILE AND RETURN A CODE OF 01 TO THE
PACKET.
G-UNRECOVERABLE ERROR, POSITION GOOD, RETURN A CODE OF 11
TO THE PACKET.

(

10
SECTION:

9
PAGE:

UP-4144

UNIVAC

Rev. 1

1108

EXEC, B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

TABLE 10-1 OCTA~ AND MNEMONIC 1/0 CODES
(DEFINED IN SVS$*RLIB$)

WRITE
10
11
WRITE END OF FILE
12
CONTINGENCY WRITE
13
SKIP WRITE
ABSOLUT£ WRITE (SYSTEM ONLY) 1'1,
GATHER WRITE
15
ACQUIRE FASTRAND
17
20
READ
21
READ BACKWARD
22
READ AND RELEASE
23
RELEASE
24
BLOCK READ DRUM
READ' AND LOCK
25
26
UNLOCK
27
ABSOLUTE READ
30
TRACK SEARCH ALL WORDS
TRACK 'SEARCH FIRST WORD
31
32
POSITION SEARCH ALL WORDS
POSITION SEARCH FIRST WORD 33
34
SEARCH DRUM
35
BLOCK-SEARCH DRUM
36
SEAHCH READ DRUM
37
BLOCK SEARCH READ DRUM
40
REWIND
'1,1
REWIND WITH INTERLOCK
'1,2
SET MODE
'1,3
SCATTER READ
4'1,
SCATTER REAb BACKWARD
MOVE FORWARD
50
51
MOVE BACKWARD

10.2.1.

EQUIPMENT

THE 1108 EXECUTIVE SYSTEM PROVIDES SUPPORT FOR THE FOLLOWING MAGNETIC TAPE
DEVICES:
VIC/VIIIC
IVC
IlIA
IIA

TABLE 10-2 LISTS THE FUNCTIoNS AVAILABLE ON THE VARIOUS KINDS OF TAPE DEVICES.
10.2.2.

~J

W$

WEF$
CI"$
SW$
ABW$
GW$
ACQ$
R$
RB$
RR$
REL$
BRO$
RDL$
UNL$
ABR$
TSA$
TSF$
PSA$
PSF$
SO$
SSD$
SRD$
6SRD$
REW$
REWI$
SM$
seR$
SeRBs
MF$
MB$

MAGNETIC TAPE HANDLER

UNISERVO
UNISERVO
UNISERVO
UNISERVO

~"'..,
[,

OCTAL SYMBOL

FUNCTION

10.2.

10
PAGE:

OPERATION

THE VARIOUS TAPE FUNCTIONS ARE CONTROLLED BY A ROUTINE ALWAYS PRESENT IN CORE.
RECOVERY SEQUENCES ARE STORED ON MAGNETIC DRUM AND ARE RETRIEVED ONLY AS NEEDED.
THE CURRENT POSITION OF EACH TAPE IS KEPT IN TERMS OF A BLOCK COUNT. THIS
INFORMATION IS MADE AVAILABLE TO THE ERROR LOGGING, CHECKPOINT, AND ENDING LABEL
ROUTINES.
NO PROVISION IS MADE WITHIN THE SYSTEM FOR AUTOMATIC TREATMENT OF MIXED PARITY AND
MIXED DENSITY TAPE FILES.

r",

',J

;

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

10

UTILIZATION OF THE CONTINGENCY WRITE AND SKIP WRITE FUNCTIONS ARE AUTOMATICALLY
PROVIDED FOR BY THE HANDLER AND UNLESS THE USER PROVIDES HIS OWN ERROR RECOVERY,
THESE FUNCTIONS SHOULD BE OF NO CONCERN TO THE USER.
THE DEFINITION OF THE VARIOUS TAPE FUNCTIONS IS AS FOLLOWS:
FUNCTION

DEFINITION

WRITE

STARTING AT THE ADDRESS IN H2
OF WORD 5 OF THE REQUEST PACKET,
TRANSFER THE NUMBER OF WORDS
SPECIFIED IN Hi OF WORDS TO FORM
A SINGLE BLOCK ON MAGNETIC TAPE.
TRANSFER IS ACCOMPLISHED
ACCORDING TO THE STANDARD MODES
OR THE REQUESTED MODES I.E.
PARITY, DENSITY, ETC, NORMAL
COMPLETION RESULTS WHEN ALL
WORDS HAVE BEEN TRANSFERRED
EXCEPT FOR 7-TRACK FORMAT EVEN
PARITY WHERE A C~ARACTER OF
ZERO, AFTER TRANSLATION IF
~EQUESTED, WILL CONCLUDE THE
REQUEST FOR MORE DATA BY THE
SUBSYSTEM,

WRITE END OF FILE

WRITE A SENTINEL ON MAGNETIC
TAPE WHICH, WHEN READ, WILL .
RESULT IN AN END OF FILE STATUS
BEING RETURNEOTO THE PROGRAM.

CONTINGENCY WRITE

wRITE ZEROES IN EVEN CHANNELS
ONLY FOR 2.5 INCHES OF TAPE TO
ALLOW WRITING AFTER READING
FORWARD(iIIA ONLY). THIS
FUNCTION IS AUTOMATICALLY
PROVIDED BY THE SYSTEM AND
SHOULD BE OF NO CONCERN TO
THE USER UNLtsS THE SUPPRESS
RECOVERY MODE IS EMPLOYED.

SKIP WRITE

ERASE THREE INCHES OF TAPE THEN
THE SAME AS A WRITE FUNCTION,
THIS FUNCTION IS AUTOMATICALLY
PROVIDED IN THE SYSTEM FOR WRITE
PARITY RECOVERY. THE ONLY USER
NEED WOULD BE IN THE SUPPRESS
RECOVERY MODE OR IF AN EXTENDED
INTER BLOCK GAP IS NEEDED ON
COMPATIBLE TAPE TYPES,

GATHER WRITE

WRITE A SINGLE BLOCK ON MAGNETIC
TAPE SPECIFIED BY A STRING OF
ACCESS WORDS. THE NUMBER OF
ACCESS WORDS IS SPECIFIED IN
Hi OF ~ORD 5 AND THE STARTING
ADDRESS OF THE STRING IS
SPECIFIED IN H2 OF WORD 5.

READ FOHWARD

INITIATE TAPE MOTION IN THE
FORWARD DIRECTION AND TRANSFER
THE WORDS READ INTO THE AREA
DEFINED BY WORD 5 OF THE PACKET.
TRANSFER IS NORMALLY CONCLUDED

PAGE:

11

UNIVAC 1108 OPERATING

UP-4144

Rev.1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

PAGE:

12

o
BY EITHER ENCOUNTERING THE END
OF B~OCK OR TRANSFERRING THE
NUMBER OF WORDS REQUESTED.
READ BACKWARD

SAME AS READ FORWARD EXCEPT
OPPOSITE DIRECTION,

MOVE FORWARD

SAME AS READ FORWARD EXCEPT NO
TRANSFER TAKES P~ACE HENCE NO
ACCESS WORD IS REQUIRED,

MOVE BACKWARD

BACKSPACE THE TAPE ONE BLOCK.

REWIND

REPOSITION THE TAPE AT THE
'LOAD POINt,. THIS IS THE POINT
AT WHICH A READ FORWARD READS
THE FIRST BLOCK ON TAPE AND A
READ BACKWARDS REPORTS AN END OF
TAPE STATUS.

REWIND WITH

INTER~OCK

REPOSITION THE TAPE TO 'UNLOAD
POINT' AND LOCK THE UNIT AGAINST
FURTHER FUNCTIONS.

SCATTER READ FORWARD

SAME AS READ FORWARD EXCEPT
THE WORDS READ ARE TRANSFERRED
INTO AREAS SPECIFIED BY A
STRING OF ACCESS WORDS DEFINED
BY WORD 5.

SCATTER READ BACKWARD

SAME AS SCATTER READ FORWARD
EXCEPT~OPPOSITE MOTION
DIRECTION.

10.2.3.

~HE

SET MODE REQUEST

FOR THE SET MODE FUNCTION, THE 1/0 ACCESS WORD SHOULD BE SET TO POINT TO A
ONE-WORD BUFFER WHICH DEFINES THE MODES TO BE SET. THE BUFFER WORD IS FORMATTED AS
FIVE 2-61T FIELDS STARTING IN THE MOST SIGNIFICANT BIT FO~LOWED BY AN 8-BIT AND
18-~IT FIELD (FORM 2,2,2,2,2,8,18).
THE 8-BIT FIE~D SHOU~D BE CODED AS ZERO. THE
VALUES IN THE 2-BIT FIELDS ARE INTERPRETED AS FOL~OWS:
FIELD 1-DENSITY
O=NO CHANGE
1=I.OW
2=MEOIUM
3=HIGH
FIELD 2-PARITY
O=NO CHANGE
1=000 (BINARY)
2=EVEN (BCD)
FIELD 3-TRANSLATE
O=NO CHANGE
1=SET CHARACTER TRANSLATE MODE
2=DISCONTINUE TRANSLATION
FIELD 4-ALLOW NOISE
D=NO -CHANGE
1=5ET THE NOISE CONSTANT TO THE NUMBER OF CHARACTERS
!N THE 18-SIT FIELD (H2)
FIELD

5-SU~PRESS

RECOVERY

o

UP-4144

Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

O=NO CHANGE
l=HETURN EXTERNAL INTERRUPT STATUS CODE TO THE WORKER
PROGRAM IN CASE OF MALFUNCTION WITHOUT ATTEMPTING
HECOVERY.
2=DISCONTINUE SUPPRESS RECOVERY MODE
IN LIEU OF SETTING MODES BY THE WORKER PROGRAM, THE STANDARD MODES ESTABLISHED BY THE
EXEC AT INITIALIZATION AND RE"ESTABLISHED WHENEVER A TAPE IS RELEASED ARE:
HIGH DENSITY
000 PARITY
NO CHARACTER TRANSLATION
l8-CHARACTER NOISE CONSTANT
STANDARD RECOVERY
IN ADDITION TO THE SERVICE ENTRANCE, THE PARITY AND DENSITY MODES CAN BE SET BY
THE OPTIONS ON THE ASG CARD.
THE MAGNETIC TAPE HANDLER IS SET WITH A STANDARD 'NOISE CONSTANT'. THIS VALUE IS
INTERPRETED BY THE HANDLER TO MEAN THAT ON READING ANY BLOCK SHORTER THAN THIS VALUE
IF A PARITY ERROR IS DETECTED THE BLOCK WILL BE CONSIDERED AS INTERBLOCK"GAP NOISE
AND WILL BE PASSED OVER. ANY RECORDING DETECTED WHILE WRITING WHICH IS LESS THAT THE
I~OIS~ CONSTANT WILL BE PASSED OVER IF IT IS DETERMINED THAT THE BLOCK CAN BE ByPASSED
AS 'NOISE' WHEN READING WITH THE SAME NOISE CONSTANT. BY USE OF THE SET MODE
FUNCTION, THE USER CAN SET THE NOISE CONSTANT TO WHATEVER VALUE IS DESIRED. IT IS
ASSUMED BY THE HANDLER THAT IF THE NOISE CONSTANT IS CHANGED FOR WRITING A TAPE, THE
SAME CONSTANT WILL BE USED FOR READING. THIS ASSUMPTION IS IMPORTANT IF AN INCREASE
IN THE CONSTANT IS MADE FOR WRITING, AS BLOCKS MAY BE LEFT ON THE TAPE WHICH ARE
UNREADABLE WITH THE STANDARD NOISE CONSTANT. IF 'NOISE BLOCKS, ARE READ FROM TAPE OR
LEFT ON TAPE WHEN WRITING, AT THE TIME THE TAPE IS REWOUND A MESSAGE OF THE FORM:
C/U NOISE W-XX R"YY
15 DISPLAYED ON THE CONSOLE WHERE XX IS THE NUMBER OF REMAINING BLOCKS WHEN WRITING
AND YY IS THE NUMBER OF BLOCKS BYPASSED WHEN READING, ALSO WHENEVER NOISE IS LEFT
THE COUNT ENTERED IN THE SYSTEM LOG IS INCREMENTED. THE COUNT OF NOISE BLOCKS
BYPASSEU UPON READING IS ALSO RECORDED IN THE LOG. IF A TAPE IS READ AT A DENSITY
OTHER THAN THE RECORDING DENSITY, IT MAY RESULT IN HAVING A LEGAL DATA BLOCK OF
GkEATER LENGTH THAN THE NOISE CONSTANT APPEAR TO BE A BLOCK OF NOISE. THE NOISE
CONSTANT CAN BE CHANGED BY THE SET MODE ENTRANCE ONLY WHEN THE TAPE IS IN THE REWOUND
POSITION. THIS IS NEEDED TO INSURE PROPER POSITIONING FOR RESTART.
TRANSLATION ON IVC, VIC, OR VIIIC CHANNELS IS ASSUMED ACCORDING TO THE WAY IN
WHICH THE PLUGBOARD IS WIRED IF THE OPTIONAL BOARD IS IN THE CONFIGURATION. (TABLE
10-3 SHOWS THE STANDARD MANNER IN WHICH THE PLUGBOARD IS WIRED.) FOR THIS CASE, THE
HANDLER DOES NO MORE THAN SET THE PROPER BIT IN THE FUNCTION WORD. IF THE
CONFIGURATION IS WITHOUT THE PLUGBOARD, THE STANDARD TRANSLATION BY THE SOFTWARE ON
THE ABOVE MENTIONED TAPE TYPES IS FROM BCD TO FIELDATA ON READING AND THE REVERSE ON
WRITING (THE SAME AS HARDWARE STANDARD IN TABLE 10-3). HENCE THE PARITY MODE SHOULD
BE SET TO EVEN IF THE TRANSLATE MODE IS TO BE SET USING THE SOFTWARE. TRANSLATION ON
THE VIC/VIIIC UNITS IS ALLOWABLE ON 7-CHANNEL OPERATION ONLY. CHARACTER TRANSLATION
BY THE SOFTWARE WILL ADD APPROXIMATELy 40 MICROSECONDS PER WORD TO THE EXECUTION OF
THE PROGRAM, SOFTWARE TRANSLATION IS REMOVED AT SYSTEM GENERATION TIME IF HARDWARE
TRANSLATION IS AVAILABLE ON ANY CHANNEL. THE USER MAY ALSO SPECIFY REMOVAL OF
SOFTWARE TRANSLATION AT GENERATION IF HARDWARE TRANSLATION IS NOT INSTALLED AND NO
TRANSLATION IS ANTICIPATED. IF HARDWARE TRANSLATION IS NOT AVAILABLE ON ALL CHANNELS
AND THE MODE IS TO BE SET, IT IS IMPORTANT THAT THE ASG CARD SHOW THIS REQUIREMENT.
IF THE SUPPRESS RECOVERy MODE IS SET, THE TAPE HANDLER WILL NOT ANALYZE THE
INTERRUPT BUT INSTEAD THE USER PROGRAM IS GIVEN CONTROL WITH A STATUS CODE OF 11
(SUPPRESS RECOVERY SET), AND THE STATUS WORD IN THE A1 REGISTER OF THE INTERRUPT
ACTIVITY CONTROL REGISTER SET. THE SUBSTATUS FIELD REFLECT THE FINAL STATE OF THE
INPUT OR OUTPUT ACCESS WORD,

13
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS .REFERENCE

SYSTEM

10
SECTION:

PAGE:

o
IF THE MODES SPECIFIED IN THE SERVICE REQUEST ARE NOT COMPATIBLE, A STATUS CODE OF
21 IS STOHED IN THE PACKET AND CONTROL IS GIVEN TO THE USER'S ERROR TERMINATION
ROUTINE IF SPECIFIED. NONCONFLIC~ING MODES STARTING WITHFIELD-l (DENSITY) WILL BE
SET AS SPECIFIED IN THE REQUEST.
10.2.4.

STANDARD RECOVERY

R~COVERY BY THE HANDLER CONSISTS OF AN OPTIMUM NUMBER OF REREADS AT VARIOUS GAINS
(OR WHATEVER IS APPROPRIATE FOR THE TYPE OF UNIT) OR A NUMBER OF BACKSPACE/SKIP-WRITE
CYCLES BASED ON TliE SIZE OF THE BLOCK AND THE TAPE DENSITY. AN ERROR COUNT IS KEPT
FOR EACH TAPE. SYSTEM LOG ENTRIES ARE MADE IF THE NUMBER OF RECOVERIES EXCEEDS AN
ACCEPTABLE THRESHOLD.

IN THE EVENT THAT THE RECOVERY PROVIDED BY THE SYSTEM FAILS TO RESOLVE THE ERROR
CONDITION, ONE OF THE FOLLOWING MESSAGES IS DISPLAYED ON THE CONSOLE:
ME.SSAGE

RESPONSES

COMMENTS

C/U INTRLK FUNC

A,B,D,E

THE REQUESTED UNIT IS IN AN
INOPERABLE CONDITION. THIS
CAN RESULT FROM FAILURE TO
INSERT A WKITE ENABLE RING,
POWER OFF, UNIT ON LOCAL,"£TC.

C/U riASH FUNC

FOR VI/VIIIC UNITS THIS ERROR
RESULTS FROM READING INFORMATION IN THE INTERBLOCK GAP
WHEN ATTEMPTING A W, SW, OR
WEF FUNCTION. LOST POSITION
IS FLAGGED FOR THE UNIT AND
NO FURTHER RECOVERY ATTEMPT
CAN BE RELIED UPON.

C/U PARITY-l FUNC

A,8,0,G,E

RECOVERY TO PARITY ON THE
FUNCTION WAS UNSUCCESSFUL.
AN ANSWER OF 'A, WILL CAUSE
THE HANDLER TO REPOSITION
AND ATTEMPT TO PERFORM THE
FUNCTION AGAIN, .THE TAPE IS
POSITIONED SUCH THAT IF THE
FUNCTION IS A READ ANOTHER
READ OPERATION IN THE SAME
DIRECTION WILL READ THE NEXT
~LOCK IN THAT DIRECTION,
THIS WOULD BE THE CASE FOR A
READ AFTER ANSWERING 'G' TO
THIS MESSAGE.

C/U PAKITY-2 FUNC

A,B,D

PARITY OCCURRED ON THE FIRST
WRITE ATTEMPT FROM LOAD POINT.
NO RECOVERY HAS BEEN ATTEMPTED
TO ALLOW THE OPERATOR TO MOUNT
A NEW REEL IF DESIRED,

C/U PAHITY-3 FUNC

PARITY RECOVERY BY THE HANDLER
HAS BEEN UNSUCCESSFUL, FOR
WRlTE FUNCTIONS THE RECOVERY
WHiCH EITHER RESULTED IN A"
,BAD BLOCK ~EING LEFT QN THE
TAPE OR LOSS OF POSITION.
FOR READ OPERATIONS THE
NUMBER OF WORDS SPEC lED IN
THE INPUT/uUTPUT PACKET WAS
LESS THAN THE NOISE CONSTANT.

C"
.:.. ~.

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

C/U UNDFNC FUNC

THE FUNC FIELD (NUMERIC FOR
THIS CODE) CorJTAINS A VALUE
NOT DEFINED FOR THE SUBSYSTEM.
IF THE FUNCTION IS IN THE
REPERTOIRE OF THE TAPE TYPE
AND IS NOT A FORM OF WRITE ON
A READ-ONLY CHANNEL, THE FAULT
IS IN THE SUBSYSTEM; OTHERWISE
THE ERROR IS EXTERNAL TO THE
TAPE SU8SYSTEM.

C/U UNEXP-XX FUNC

THE INTERRUPT STATUS CODE XX
IS NOT EXPECTED FOR THE GIVEN
FUNCTION.

10.2.5.

CONSIDERATIONS FOR IV/VI/VIIIC TAPE TYPES

THE FOLLOWING DETAILS MUST BE TAKEN INTO ACCOUNT WHEN uSING THE TAPE HANDLER FOR
THE COMPATIBLE TAPE TYP~S:
1. READ BACKWARD LIMITATIONS
THE READ BACKWARD FUNCTION eN THE VI/VIIIC UNITS SHOULD
NOT UE USED IF THE TAPE TO BE READ HAS BEEN RECORDED ON
OTHEK THAN A VIC OR VIIIC UNIT. IT IS NECESSARY THAT
THE RECORDING PROUUCE A 'STATICALLY DESKEWED LONGITUDINAL CHECK FRAME' TO PREVENT THE READ BACKWARD FUNCTION
FROM INTERPRETING THE CHECK FRAME AS DATA FRAMES.
IF A BLOCK IS RECORDED IN 7-TRACK FORMAT wITH A BLOCK
LENGTH GREATER THAN 5 FRAMES AND NOT A MuLTIPLE OF 6,
A READ BACKWARD PRODUCES A DIFFERENT FORMAT THAN A
READ FORWARD OF THE SAME BLOCK. FOR EXAMPLE,IF THE
BLOCK LENGTH IS 7 FRAMES A READ FORWARD" RESULTS IN
ASSEMBLING FRAMES 1-6 AS "THE FIRST WORD AND FRAME 7
AS THE SECOND AND A READ BACKWARD RESULTS IN ASSEMBLING
FRAMES 2-7 AS THE FIRST WORD ANO FRAME 1 AS THE SECOND.
THE SAME TYPE OF BUFFER VARIATION EXISTS FOR A READ
BACKWARD ON A 9-TRACK UNIT IF THE WRITE BUFFER LENGTH
IS NOT A MULTIPLE OF 2 WORDS (9-FRAMtS). A ONE WORD
WRITE Ol~ A 9-TRACK UNIT RESULTS IN FIVE FRAMES BEING
RECORDED wITH THE FIFTH FRAME CONTAINING 4-8ITS OF ZERO
PADDING. A READ BACKWARD RESULTS IN THE 4-8ITS OF PADDING
APPEARING AS THE LEAST SIGNIFICANT 4 BITS OF THE FIRST
WORD ASSEMBLED. FURTHERMORE, REGARDLESS OF THE DIRECTION
OF READING, IF A bLOCK IS WHITTEN ON A 9-TRACK FORMAT UNIT
wITH AN ODD WORD COUNT IN THE ACCESS WORD, ONE MORE WORD IS
MADE AVAILA~LE AS INPUT THAN WAS SENT OUT TO BE WRITTEN
2. WRITE CONSIDERATIONS
IF THE USER ATTEMPTS TO WRITE END OF FILE SENTINELS
ON 7-TRACK UNITS BY DOING AN EVEN PARITy WRITE wITH
TRUNCATION CAUSED BY A ZERO CHARACTER, AND IF THE TRANSLATE
MODE IS SET,IT IS ESSENTIAL THAT THE FIRST TWO CHARACTERS
O~ THE BUFFER TRANSLATE TO 1700 OCTAL To CAUSE AN END
OF FILE STATUS WHEN READ.
SINCE HARDWARE TRANSLATION MAY BE AVAILABLE AND THE USER
HAS THE ABILITY TO VARY THE TRANSLATION, CARE MUST BE
EXERCISED TO P~EVENT UNWANTED TRANSLATION OF A CHARACTER
TO ZERO WHICH CAUSES TRUNCATING A WRITE TRANSFER WHEN
wRITING IN THE EVEN PARITY MODE. IF SOFTWARE CONVERSION IS

15

10
SECTION:

PAGE:

...

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

10

PROGRAMMERS REFERENCE

SECTION:

16
PAGE:

· ""
C
.

)

.~y'

USED FOR WRITE OPERATIONS THE WORDS ARE CONVERTED IN THE
8UFFER BEFORE THE WRITE OPERATION IS PERFORMED. IF A B~OCK
IS WRITTEN
WITH LESS CHARACTERS THAN THE NOISE CONSTANT, THE RISK
EXISTS OF BYPASSING THE DATA BLOCK AS NOISE WHEN READING,
ALSO. A ZERO AS THE FIRST CHARACTER RESULTS IN AN ERRONEOUS
BLOCK COUNT. ON A ZERO CHARACTER COUNT, uP TO THREE
WORDS LEAVE THE COMPUTER AND ARE CONSIDERED TO HAVE BEEN
WRITTEN AS REFLECTED IN THE COUNT IN THE SUBSTATUS FIE~D
OF THE REQUEST PACKET.
THE RECOVERY PROCEDURE FOR A PARITY ERROR OR CERTAIN TAPE
HASH ERROR ONA WRITE OPERATION MAY UTILIZE TWO FEET OF
TAPE OR TWICE THE LENGTH OF THE BLOCK WHICHEVER IS ~ARGER,
HENCE, IF BLOCKS ARE TO BE RECORDED WHICH ARE ~ONGER THAN
TWO FEET (OR LESS DEPENDING UPON WHETHER AN ENDING
INTERRUPT ACTIVITY SUBMITS THE NEXT REQUEST OR IF REQUESTS
ARE QUEUED AHEAD BY I/O CONTROL), IT IS RECOMMENDED THAT
TAPES BE USEO WHICH HAVE THE END OF TAPE WARNING MARKER
PLACED FURTHER FROM THE END OF TAPE. THE NORMAL PLACEMENT
IS 14 FEET FROM THE END OF TAPE AND IT IS RECOMMENDED THAT
AT LEAST 10 FEET OF TAPE REMAIN ON THE SUPPLY SIDE OF THE
WRITE HEAD TO INSURE THAT THE TAPE IS NOT PU~LEO OFF THE
SUPPLY REEL.
3. MOVE CONSIOERATIONS
THE MOVE FORWARD AND MOVE BACKWARD FUNCTIONS ARE INCLUDED
TO COVER THE CONDITIoN WHERE THE ONLY CONCERN IS POSITION,
PARITY ERRORS ARE NOT REPORTED AND ARE ONLY EXAMINED TO
DETERMINE NOlSE BLOCKS. FOR THE IVC UNITS THE PARITY
STATUS IS NOT RETURNED FOR THE BACKSPACE BLOCK FUNCTION,
THEREFORE THE MOVE BACKWARD IS NOT RECOMMENDED ON THE IVC
IF NOISE IS A PROf:lLEM AS L.OST POSITION MAY RESU~T,
10.2,6.

MULTIPLE-CHANNEL OPERATION

THE MAGNETIC TAPE HANDLER IS CAPABLE OF A SIMULTANEOUS OPERATION ON ANY NUMBER OF
CHANNELS INVOLVING ANY MIXTURE OF TAPE DEVICE TyPES.
THE FULL DUAL CHANNEL ON UNISERVO VIC/VIIIC
COGNIZANCE.

WI~L

BE SUPPORTED WITHOUT USER

o

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM
SECTION:

(TABLE 10-2 TAPE FUNCTIONS

C

FUNCTION

COOt:: PKT VIC/VIlIC IIlC/IVC
OCT LEN

READ FO~WARD
READ BACKWARD
SCATTER READ
SCATTER READ BKWD
MovE-FORWARD
MOVE BACKWARD
WRITE
WRITE END OF FILE
CONTINGENCY WRITE
SKIP-WRITE
GATHER WRITE
REWIND
REWIND WITH INTLK
SET MODE
HIGH DENSITY
MEDIUM DENSITY
LOW DENSITY
ODD PARITY
EVEN PARITY
TRANSLATE
ALLOW NOISE
SUPPRESS RECOVERY

20
21
43
44
50
51
10
11
12
13
15
40
41
42

CODE

5
5
5
5

4
4
5
4
4
4
5

4
4
5

*

*
*
**
*
*
*I
*
*

*
*
*
*
*
*
**
**
*

*I
*I
*
*
*

*I
*
*
*
*
*
*
*
*

*

*
*
*
*

*-AVAILABLE
I-ILLEGAL FUNCTION, CAUSES TERMINATION

17

10

PROGRAMMERS REFERENCE

lIlA

IIA

*
*I

*
*I

*"
*
*

**
*
I

*I

I

I

I

I

I

I

*
*
**

*
*
*
*I

I
*
I
I
*
*

*

*
I
I

*
*

*

PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

10
SECTION:

18
PAGE:

(-~
:
I
j

TABLE 10 ... 3 STANDARD TAPE TRANSLATION

PROCESSOR TO TAPE

TAPE TO PROCESSOR
TAPE
CODE

CPU
CODE

TAPE
CODE

CPU
CODE

CPU
CODE

TAPE
CODE

CPU
CODE

TAPE
CODE

00
01
02
05
04
05
06
07
10

46
61
62
63
64
65
66
67
70

40
f.!.1
42
43
44
45
46
47
50
51
52
53
5f.!.
55
56
57
60
61
62
63
64
65
66
67
70
71
72
73
74
7.5
76
77

41
17
20
21
22
23
2;4
25
26
27
55
47
50
02
73
04
42
06
07
10
11
12
13
14
15
16
54
75
40
01
43
03

00
01
02
03
04
05
06
07
10
11
12
13
1f.!.
15
16
17
20
21
22
26
24
25
26
27
30
31
32
33
34
35
36
37

17
75
55
77
57
20
61
62
63
64
65
66
67
70
71
41
42
43
44
45
46
47
50
51
22
23
24
25
26
27
30
31

40
41
42
43
44
45
46
47
50
51
52
53
54
55
56
57
60
61
62
63
64
65
66
67
70

74
40
60
76
13
16
00
53
54
34
35
15
72
52
33
36
12
01
02
03
04
05
06
07
10
11
14
56
21
73
37
32

11

71

12
13
14
15
16
17
20
21
22
23
24
25
26
27
30
31
32
33
34
35
36
37

60
44
72
53
45
00
05
74
30
31
32
33
34
35
36
37
77
56
51
52
57
76

71
72
73
74
75
76
77

/'~

(

''-.-/

c

UP-4144
Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS

10

REFERENCE
SECTION:

(
10.3.

MAGNETIC DRUM HANDLER

THE MAGNETIC DRUM HANDLER PROVIDES FOR CONTROL OVER OPERATIONS ON THE FH432 AND
FH8BO DRUM UNITS. EXTENSIONS WILL BE MADE TO THE HANDLER AT A FUTURE DATE TO
INCORPORATE THE FHl7B2 AND A SUBSYSTEM CONSISTING OF FH432 AND FH1782 UNITS ON THE
SAME SINGLE OR DUAL CHANNEL.
10.3.2.

OPERATION

TWO GENERAL MODES OF DRUM OPERATION ARE PROVIDED WITHIN THE DRUM HANDLER. THE
FIRST IS DRUM SIMULATION OF FAST RAND WHICH ALLOWS EXECUTION OF A PROGRAM WITH FILES
DESIGNED FOR FASTRAND ALLOCATION ALLOCATED TO THE SECTION OF THE 'FLYING HEAD' DRUM
STORAGE SPECIFIED AS SIMULATED FASTRAND. THE SECOND MODE IS DRUM AS A RANDOM STORAGE
DEVICE ALLOCATED IN FIXED ASSIGNMENTS WITH ONE WORD GRANULARITY. THE INTERPRETATION
OF FUNCTION CODES FOR SIMULATED FASTRAND ARE DEFINED IN THE FASTRAND HANDLER SECTION.
FOR DRUM FORMAT THE FUNCTIONS ARE DEFINED AS FOLLOWS:
FUNCTION

DEFINITION

WRITE

STARTING AT THE CORE ADDRESS
SPECIFIED IN H2 OF WORD 5
TRANSFER THE NUMBER OF WORDS
SPECIFIED IN Hl OF WORD 5 TO THE
DRUM AREA STARTING AT THE
RELATIVE ADDRESS IN WORD 6 OF
THE PACKET.

GATHER WRITE

TRANSFER THE NUMBER OF WORDS
SPECIFIED BY A STRING OF ACCESS
WORDS SPECIFIED BY WORD 5 FROM
THE AREAS SPECIFIED BY THESE
ACCESS WORDS TO THE DRUM AREA
STARTING AT THE RELATIVE ADDRESS
IN WORD 6. THE NUMBER OF ACCESS
¥lORDS 15 SPECIfIED IN H1 OF WORQ
5 AND THE ADDRESS OF THE ACCESS
WORDS IS SPECIFIED IN H2 OF WORD

(

5.

READ

STARTING AT THE RELATIVE DRUM
ADDRESS IN WORD 6 OF THE
REQUEST PACKET TRANSFER THE
NUMBER OF WORDS IN HI OF WORD 5
INTO THE AREA STARTING AT THE
ADDRESS IN H2 OF WORD 5.
NORMAL COMPLETION(STATUS 00)
INDICATES THE SPECIFIED NUMBER
OF WORDS HAVE BEEN TRANSFERRED
TO CORE FROM DRUM.

SCATTER READ

STARTING AT THE RELATIVE DRUM
ADDRESS IN WORD 6 OF THE PACKET
TRANSFER THE NUMBER OF WORDS
SPECIFIED BY A STRING OF ACCESS
WORDS DEFINED BY WORD 5 TO THE
AREAS SPECIFIED BY THESE ACCESS
WORDS. THE NUMBER OF ACCESS
WORDS IS SPECIFIED IN Hl OF WORD
5 AND THE ADDRESS OF THE ACCESS
WORDS IS SPECIFIED IN H2 OF WORD 5.

19
PAGE:

UP-4144

Rev. 1

UNIVAC

EXEC

1108

a

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

20
P"GE:

o
SLOCK READ

STARTING AT THE RELATIVE DRUM
ADDRESS IN WORD 6 OF THE
REQUEST PACKET TRANSFER WORDS
FROM DRUM TO CORE AT THE ADDRESS
IN H2 OF WORD 5 UNTIL EITHER
THE NUMBER OF WORDS SPECIFIED IN
H1 OF WORD 5 HAS BEEN READ OR
UNTIL THE END.OF-BLOCK SENTINEL
(A WORD OF ALL ONES) IS READ.
ENCOUNTERING A SENTINEL IS NOTED
BY AN 01 STATUS CODE AND THE
SENTINEL WORD IS TRANSFERRED
AS THE FINAL WORD IN THE BUFFER.
THE SUBSTATUS FIELD INDICATES
THE NUMBER OF WORDS READ.
IF COMPLETION IS BY END OF BLOCK
AND THE BUFFER LENGTH IS SUCH
THAT ANOTHER WORD CAN BE
ACCEPTED, THE OVERFLOW WORD
(THE WORD ON DRUM FOLLOWING THE
SENTINEL) IS STORED IN THE
BUFFER FOLLOWING (PRECEDING IF
DECREMENTATION) THE SENTINEL
WORD WITH THE UPPER 6 BITS SET
TO 04.

SEARCH

STARTING AT THE RELATIVE DRUM
ADDRESS IN WORD 6 COMPARE ALL
WORDS ON DRUM UNTIL EITHER A
l\ MATCH EQUAL IS MADE WITH
WORD 7 OF IHE PACK~r OR UNTIL
THE REMAINDER OF THE FILE HAS
BEEN TESTED. IF A 'FIND' IS
MADE (STATUS 00) THE RELATIVE
ADDRESS OF THE FIND IS STORED
IN WORD 6 OF THE PACKET.

BLOCK SEARCH

SAME AS A SEARCH WITH THE
ADDED CONDITION THAT READING
AN END-OF-BLOCK SENTINEL WORD
TERMINATES THE SEARCH WITH A
NO FIND, 03, STATUS CODE.

SEARCH READ

STARTING AT THE RELATIVE DRUM
ADDRESS IN WORD 6 COMPARE ALL
WORDS ON DRUM UNTIL EITHER A
COMPARE EQUAL IS MADE WITH
WORD 7 OF THE PACKET OR UNTIL
ALL REMAINING WORDS OF THE FILE
ARE TESTED. IF A 'FIND' IS
MADE, STORE THE RELATIVE ADDRESS
OF THE FIND WORD IN WORD 8
OF THE PACKET AND TRANSFER THE
NUMBER OF WORDS SPECIPIED IN
Hl OF WORD 5 INTO THE CORE AREA
STARTING AT THE AbDRESS IN H2
OF WORD 5. TRUNCATE THE READ
CYCLE IF THE END OF ASSIGNMENT
PRECEDES THE COUNT IN H1 OF
WORD 5.

BLOCK SEARCH READ

STARTING AT THE RELATIVE DRUM

C)

c

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

10
SECTION:

ADDRESS IN WORD 0 OF THE PACKET
COMPARE EQUAL BETWEEN THE DRUM
WORDS AND WORD 7 OF THE PACKET.
NO FINO IS DENOTED BY
ENCOUNTERING AN END~OF~BLOCK
SENTINEL OR THE END OF THE
ASSIGNED AREA FOR THE FILE.
UPON A FIND, STORE THE RELATIVE
ADDRESS OF THE FIND WORD IN WORD
8 OF THE PACKET AND TRANSFER
WORDS AS FOR THE BLOCK READ
WITH TRUNCATING FOR END-OF-BLOCK
SENTINEL OR END OF ASSIGNED AREA
(END OF ASSIGNED AREA IF THE
FINAL WORD IS NOT THE EOB
SENTINEL). STORING OF THE OVERFLOW WORD FOLLOWS THE SAME
CRITERIA AS THE BLOCK READ
FUNCTION.
THESE FUNCTIONS ARE PERFORMED ON AREAS RESERVED THROUGH THE USE OF THE ASG CONTROL
CARD. THESE ASSIGNMENTS ARE FIXED IN LENGTH, HENCE AN ATTEMPT TO READ, WRITE, OR
INITIATE A SEARCH PAST THE END OF THE ASSIGNED AREA RESULTS IN AN ERROR CONDITION. IF
ANY PART OF A READ AFTER SEARCH FINO IS OUTSIDE OF THE ASSIGNMENT, THE REQUEST IS
ft. TWO SPECIFIES THAT AN OUTPUT COMPLETION

PAGE:

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE'

10
SECTION:

40
PAGE:

ACTIVITY IS TO BE ACTIVATED EACH TIME THE OUTPUT OF THE LAST BUFFER IN AN OUTPUT
QUEUE FORPOOL~MODE OUTPUT IS SUCCESSFULLY COMPLETED OR THE OUTPUT OF ANY BUFFER IN
THE QUEUE IS UNSUCCESSFULLY COMPLETEO.
'
OUTPUT COMPLETION ADDRESS (WORD 02-H2) SPECIFIES THE STARTING ADDRESS OF THE
OUTPUT COMPLETION ACTIVITY. IF THE OUTPUT USAGE CODE IS NONZERO, THE OUTPUT
COMPLETION ADDRESS MUST SPECIFY THE ADDRESS OF AN ACTIVITY WITHIN THE BOUNDS OF THE
USER'S PROGRAM.
'
OUTPUT MODE (WORD 03-Hl) SPECIFIES THE BUFFERING MODE FOR OUTPUT. ANY NONZERO
VALUE SPECIFIES SINGLE-MODE OUTPUT. ZERO SPECIFIES POOL-MODE OllTPUT (IF THE OUTPUT
POOL NAME IS NONZERO). IF THE OUTPUT MODE AND THE OUTPUT POOL NAME ARE BOTH ZERO,
THE SPECIFIED CLT GROUP WILL NOT BE INITIALIZED FOR OUTPUT.
'
OUTPUT POOL NAME (wqRD 03-H2) SPECIFIES THE POOL TO BE USED FOR' POOL-MODE OUTPUT.
IF THE OUTPUT MODE IS ZERO, THE OUTPUT POOL NAME MuST EITHER BE ZERO OR SPECIFY A
POOL OF OPEN-CHAINED BUFFERS CURRENTLy ASSIGNED TO THE USER.
10.8.2.

INPUT INITIALIZATION

IF THE SPECIFIED CLT GROUP IS TO BE INITIALIZED FOR INPUT, EITHER THE INPUT MODE
OR THE INPUT POOL NAME MUST BE NONZERO, AND THE FOLLOWING PARAMETERS MUST BE
PROVIDED:
INPUT ACTION (WORD 06-S2) SPECIFIES THE ACTION TO BE TAKEN BY THE COMMUNICATION
HANDLER WHEN THE INPUT TOA POOL-MODE BUFFER IS COMPLETED. IF POOL-MODE INPUT IS
SPECIFIED, THE INPUT ACTION CODE MUST BE EITHER ZERO OR ONE. ZERO SPECIFIES THAT
INPUT IS TO BE TERMINATED WHEN THE INPUT TO A BUFFER IS COMPLETED. ONE SPECIFIES
THAT INPUT IS TO CONTINUE, USING THE NEXT BUFFER (IF THERE IS ONE) IN THE INPUT POOL.

('~

U

INPUT USAGE (WORD 06-S3) SPECIFIES THE USAGE OF AN INPUT COMPLETION ACTIVITY AND
MUST BE EITHER ZERO OR ONE. ZERO sPECIFIES THAT NO INPUT COMPLETION ACTIVITY IS TO
BE ACTIVATED. OOE SPECIFIES THAT AN INPUT COMPLETION ACTIVITY IS TO BE ACTIVATED
EACH TIME THE INPUT TO A BUFFER IS COMPLETED (SUCCESSFULLY OR UNSUCCESSFULLY).
INPUT COMPLETION ADDRESS (WORD 06-H2) SPECIFIES THE STARTING ADDRESS OF THE INPUT
COMPLETION ACTIVITY. IF THE INPUT USAGE CODE IS ONE, THE INPUT COMPLETION ADDRESS
MUST SPECIFY THE ADDRESS OF AN ACTIVITY WITHIN THE BOUNDS OF THE USER'S PROGRAM.
INPUT MODE (WORD 07-Hl) SPECIFIES THE BUFFERING MODE FOR INPUT. ANY NONZERO VALUE
SPECIFIES SINGLE-MODE INPUT. ZERO SPECIFIES POOL-MODE INPUT (IF THE INP~UT POOL NAME
IS NONZERO). IF THE INPUT MODE AND THE INPUT POOL NAME ARE BOTH ZE~~THE SPECIFIED
CLT GROUP WILL NOT BE INITIALIZED FOR INPUT.
INPUT POOL NAME (WORD 07-H2) SPECIFIES THE POOL TO BE USED FOR POOL-MODE INPUT.
IF THE INPUT MODE IS ZERO, THE INPUT POOL NAME MUST E~ER BE ZERO OR SPECIFY A POOL
CURRENTLY ASSIGNED TO THE USER.
INPUT DUAL POOL NAME (WORD 09-Hl) SPECIFIES THE POOL TO BE USED FOR DUAL POOL-MODE
INPUT. IF POOL-MODE INPUT IS SPECIFIED, THE DUAL POOL NAME MUST EITHER BE ZERO OR
SPECIFY A POOL CURRENTLY ASSIGNED TO THE USER AND DIFFERENT FROM THE INPUT POOL. IF
THE DUAL POOL NAME IS ZERO, THE SPECIFIED eLT GROUP WILL NOT BE INITIALIZED FOR DUAL
POOL-MODE INPUT.

OCTAL ERROR CODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMS$ ARE AS FOLLOWS:

c

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

01

USER PHOGRAM MAKING THE EXECUTIVE REQUEST IS NOT IN THE
HEAL-TH·1E MODE.

02

LINE TERMINAL TABLE SPECIFIED TO BE INITIALIZED IS NOT
WITHIN THE BOUNDS OF THE USER'S DATA-BANk.

03

INTERNAL GHOUP NAME SPECIFIES A COMMUNICATION LINE TERMINAL
GROUP CURRENTLy INITIALIZED.

06

10
SECTION:

INTERNAL GHOUP NAME DOES NOT SPECIFY A COMMUNICATION LINE
GROUP CURRENTLY ASSIGNED TO THE USER.

TERf~INAL

27

OUTPUT '·,001:: AND INPUT MODE DO NOT BOTH SPECIFY SINGLE-MODE
HUFFERING FOR A CTS SUBSYSTEM OR A WTS SUBSYSTEM.

53

ADDRESS OF A LINE TERMINAL TABLE TO BE INITIALIZED IS IN
THE USER'S INSTRUCTION-BANK.

7~

THE OUTPUT MODE AND THE OUTPUT POOL NAME ARE BOTH ZERO, AND
THE INPUT MODE AND THE INPUT POOL NAME ARE BOTH ZERO.

10.8.3.1.

OUTPUT ERRORS

IF A COMMUNICATION LINE TERMINAL GROUP IS TO BE INITIALIZED FOR INPUT ONLY, THE
FOLLOWING OCTAL ERROR CODES AND ERROR CONDITIONS ARE NOT APPLICABLE.
14

15

OUTPUT USAGE CODE SPECIFIED IS EITHER A VALUE OTHER THAN
ZERO OR ONE FOR SINGLE-MODE OUTPUT OR A VALUE OTHER THAN
ZERO, ONE, OR TWO FOR POOL-MODE OUTPUT.
OUTPUT POOL NAME DOES NOT SPECIFY A POOL OF OPEN-CHAINED
CURRENTLY ASSIGNED TO THE USER.

B~FFERS

40

INTERNAL GROUP NAME DOES NOT SPECIFY A COMMUNICATION LINE
TERMINAL GROUP WITH OUTPUT CAPABILITY.

45

OUTPUT COMPLETION ADDRESS SPECIFIED IS NOT WITHIN THE
BOUNDS OF THE USER'S PROGRAM.

76

INTERNAL GROUP NAME SPECIFIES A ~OMMUNICATION LINE TERMINAL
GROUP FOR WHICH AN. OUTPUT PATH IS NOT AVAILABLE.

10.8.3.2.

INPUT EKRORS

IF A COMMUNICATION LINE TERMINAL GROUP IS TO BE INITIALIZED FOR OUTPUT ONLy, THE
FOLLOWING OCTAL ERROR CODES AND ERROR CONDITIONS ARE NOT APPLICABLE:
05

INPUT USAGE CODE SPECIFIED IS A VALUE OTHER THAN ZERO OR
ONE.

07

INPUT ACTION CODE SPECIFIED FOR POOL-MODE INPUT IS A VALUE
OTHER THAN ZERO OR ONE.

11

INPUT POOL NAME OR DUAL POOL NAME DOES NOT SPECIFY A POOL
CURRENTLY ASSIGI...JEO TO THE USER, OR THE INPUT POOL NAME AND
THE DUAL POOL NAME SPECIFY THE SAME POOL.

13

INPUT COMPLETION ADDRESS SPECIFIED IS NOT WITHIN THE BOUNDS

41
PAGE:

UNIVAC 110B OPERATING

UP-4144

EXEC B

Rev. 1

~1

77

SYSTEM

PROGRAMMERS REFERENCE ..

OF THE USER,S PROGRAM,
INTERNAL GROUP NAME DOES NOT SPECIFY A COMMuNICATION LINE
TERMINAL GROUP WITH INPUT CAPABILITY,
INTERNAL GROUP NAME SPECIFIES A COMMUNICATION LINE TERMINAL
GROUP FOR WHICH AN INPUT PATH IS NOT AVAILABLE.

WHEN AN EXECUT·IVE REQUEST IS MADE TO CMS$, THE lINE TERMINAL TABLES SPECIFIED BY
USER WILL BE INITIALIZED IN TURN BEGINNING WITH THE lINE TERMINAL TABLE SPECIFIED
IN THE LOWER HALF OF REGISTER AO. THUS, WHEN AN ERROR CONDITION IS DETECTED AND
CONTROL RETURNED TO THE USER'S ERROR CONTINGENCY ROUTINE, ALL OF THE LINE TERMINAL
TABLES, PRECEDING THE ONE WHICH WAS BEING INITIALIZED WHEN THE ERROR CONDITION WAS
DETECTED, WILL HAVE BEEN INITIALIZED. THE USER MAY ELECT TO USE THE INITIALIZED LINE
TERMINAL TABLES OR·TERMINATE THEM BY MAKING AN EXECUTIVE REQUEST TO CMT$.

7HE

10.9.

DIALING

THE DIAL OPERATION CAUSES INITIATION OF THE BUFFER SPECIFIED IN WORD 11 OF THE LT
TABLE ADDRESSED BY AO. THE TELEPHONE NUMBER TO BE DIALED MUST BE IN BCD FORMAT. UPON
DETERMINING THAT THE DIAL OPERATION HAS BEEN COMPLETED, THE USER WILL GET CONTROL AT
THE DIAL COMPLETION ACTIVITY STARTING POINT , IF SUCH A ROUTINE EXISTS, WITH THE DIAL
STATUS IN 51 OF WORD 11. INPUT AND OUTPUT CAN BE INITIATED BEFORE A DIAL OPERATION IS
COMPLETED IN WHICH CASE NO CHARACTER TIMING IS DONE BEFORE THE FIRST CHARACTER
TRANSFER OR THE DIAL TIMES OUT. FOR THE CASE OF INITIATING OUTPUT, THE OUTPUT lINE
TERMINAL REQUIRES AN ENABLE FROM THE DIAL UNIT AND HENCE TRANSFER STARTS IMMEDIATELY
UPON DIAL COMPLETION.
IF· AN AUTOMATIC CAllING UNIT DOES NOT EXIST FOR AN IT GROUP, THE DIAL OPERAT.ION
WILL RESULT IN A MESSAGE BEING DISPLAYED ON THE CONSOLE IN THE FORMAT:
DIAL NUMBER CC/ll
WHERE CC/lL IS THE CHANNEL AND lINE NUMBER TO BE CONNECTED. THE OPERATOR MUST
RESPOND WITH AN N OR Y TO INDICATE COMPLETION. A REQUEST FOR OUTPUT FOR THE MANUAL
CASE IS NOT HONORED UNTIL A Y RESPONSE IS RECEIVED.
A DIAL REQUEST ON A lEASED-lINE IT GROUP IS GIVEN A UNIQUE STATUS CODE AND ANY
SUBSEQUENT INPUT OR OUTPUT WILL BE HONORED.
THE DIAL COMPLETION ACTIVITY OPERATES AS A HIGH PRIORITY INTERRUPT ROUTINE AND IS
ALLOWED ONLY A lIMITED TIME PERIOD TO PERFORM ITS ANALYSIS OF THE INTERRUPT. WHEN
THIS ROUTINE IS ENTERED, AO WIll CONTAIN THE lOCATION OF THE APPROPRIATE IT TABLE.
MUST BE IN THE REAL-TIME MODE AND REGISTER AO MUST CONTAIN THE lOCATION OF THE LINE
TERMINAL TABLE. THE CALLING SEQUENCE IS AS FOllOWS:
l,U
AO,lTT
ER
CMD$
INTERNAL GROUP NAME (WORD OO-WW AND WORD Ol-WW) SPECIFIES THE COMMUNICATION lINE
TERMINAL (ClT) GROUP TO ORIGINATE THE CAll AND MUST SPECIFY THE ClT GROUP FOR WHICH
THE LINE TERMINAL TABLE WAS INITIALIZED, AND THE SPECIFIED ClT GROUP MUST HAVE DIAL
AND HANGUP CAPABILIT~.
DiAL USAGE (WORD 10-53) SPECIFIES THE USAGE OF A DIAL COMPLETION ACTIVITY AND MUST
BE EITHER ZERO OR ONE. ZERO SPECIFIES THAT NO DIAL COMPLETION ACTIVITY IS TO.BE
ACTIVATED. ONE SPECIFIES THAT A DIAL COMPLETION ACTIVITY IS TO BE ACTIVATED WHEN THE
CALL IS ANSWERED (OR ABANDONED).
.
DIAL COMPLETION ADDRESS (WORD 10-H2) SPECIFIES THE STARTING ADDRESS OF THE DIAL

(.. ~\,..;

UP-4144
Rev.!

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

COMPLE-TION ACTIVITY. IF THE DIAL USAGE CODE IS ONE, THE DIAL COMPLETION ADDRESS MUST
SPECIFY THE ADDRESS OF AN ACTIVITY WITHIN THE BOUNDS OF THE USER,S PROGRAM.
DIAL CHARACTER COUNT (WORD II-HI) SPECIFIES THE NUMBER OF BINARY COOED DECIMAL
(SCO) DIAL DIGITS IN THE DIAL BUFFER AND MUST BE A vALUE BETWEEN ONE AND SIXTEEN AND
MUST NOT BE A VALUE THAT WOULD CAUSE THE DIAL BUFFER TO EXTEND BEYOND THE UPPER BOUND
OF THE USER'S DATA-BANK.
DIAL BUFFER ADDRESS (WORD 11-H2) SPECIFIES THE STARTING ADDRESS OF THE DIAL BUFFER
AND MUST BE IN THE USER'S DATA-BANK AND MUST NOT BE IN THE SAME STORAGE MODULE AS THE
ESI ACCESS CONTROL WORDS.
DIAL ERRORS
OCTAL ERROR cODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMD$ ARE AS FOLlOWS:

(

54

USER PROGRAM MAKING THE EXECUTIVE REQUEST IS NOT IN THE
REAL-TIME MODE.
.

55

UIAl USAGE CODE SPECIFIED ts A VALUE OTHER THAN ZERO OR
ONE.

56

lINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED, OR THE INTERNAL GROUP NAME
DOES NOT SPECIFY THE ClT GROUP FOR WHICH THE LINE TERMINAL
TABLE WAS INITIALIZED.

57

DIAL COMPLETION ADDRESS SPECIFIED IS NOT WITHIN THE BOUNDS
OF THE USER'S PROGRAM.

71

DIAL .HARACTER COUNT SPECIFIED IS NOT A VALUE BETWEEN ONE
AND SIXTEEN.
DIAL BUFFER SPECIFIED IS NOT WITHIN BOUNDS OF THE
USER'S DATA-BANK.

64
62

CHARACTERS IN THE DIAL BUFFER SPECIFIED ARE NOT BINARY
CODED DECIMAL (BCD).

67

INTERNAL GROUP NAME DOES NOT SPECIFY A ClT GROUP WITH DIAL
AND HANG-UP CAPABILITY •.

10.10.

43

10
SECTION:

INPUT

WHEN AN EXECUTIVE REQUEST IS MADE TO CMI$, THE USER PROGRAM MUST BE IN THE REAL
TIME MODE AND REGISTER AO MUST CONTAIN THE LOCATION OF THE LINE TERMINAL TABLE. THE
CALLING SEQUENCE IS AS FOllOWS:
l,U
AO,LTT
ER
CMI$

IF AN EXECUTIVE REQUEST TO CMI$IS FOR SINGLE-MODE INPUT, THE LINE TERMINAL TABLE
MUST BE CUHRENTL Y INITIALIZED FOR SINGLE-MODE INPUT, AND CONVERSELY, -IF THE LINE
TERMINAL TABLE IS CURRENTLY INITIALIZED FOR SINGLE-MODE INPUT, AN EXECUTIVE REQUEST
TO CMI$ MUST BE FOR SINGLE-MODE INPUT, AND THE FOLLOWING TWO PARAMETERS MUST BE
PROVIDED.

PAGE:

UNIVAC 1108 OPERA'TING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

44

.10·
SECTION:

PAGE:

INPUT CliARACTER COUNT (WORD 07-H1) SPECIFIES THE NUMBER OF .INPUT CHARACTERS FOR
SINGLE-MODE INPUT AND MUST BE GREATER THAN ZERO, MUST NOT EXCEED THE SYSTEM MAXIMUM,
AND MUST NOT BEA VALUE THAT WOULD CAUSE THE INPUT BUFFER TO EXTEND BEYOND THE UPPER
BOUND OF THE USER'S DATA-BANK.
"
INPUT BUFFER ADDRESS (WORD .07-H2) SPECIFIES THE STARTING ADDRESS OF THE INPUT
BUFFER FOR SINGLE-MODE INPUT AND MUST BE IN THE USER.S DATA-BANK AND MUST NOT BE IN
THE SAME STORAGE MODULE AS THE ESI ACCESS CONTROL WORDS.
INPUT ON LINE TERMINALS IS IN ONE OF TWO MODES' SINGLE AND MULTIPLE BUFFER.
EITHER OF THESE MODES MAY BE SYNCHRONOUS OR ASYNCHRONOUS.
IN THE SINGLE BUFFER MODE, AN INPUT REQUEST CAUSES INITIATION OF INPUT WITH THE
ACCESS WORD FROM WORD 7 OF THE LT TABLE. COMPLETION OF INPUT IS EXPECTED TO BE
DENOTED BY AN EXTERNAL INTERRUPT RESULTING FROM DETECTION OF AN EOM SIGNAL FOR WTS OR
CTS DEVICES OR AS A RESULT OF A TIME OUT OR INPUT MONITOR INTERRUPT FOR THE CTMC.
AFTER THE END OF INPUT IS DETECTED THE INPUT LT IS TURNED OFF, THE COMPLETION STATUS
OF THE INPUT BUFFER IS STORED IN 51 OF WORD 6. THE NUMBER OF CHARACTERS ACCEPTED AS
INPUT IS STORED IN H1 OF WORD 9. FOR SYNCHRONOUS LT DEVICES OPERATING ON THE CTMC,
SINCE AN EXTERNAL INTERRUPT DOES NOT OCCUR ON A UNIQUE CHARACTER, IF A MESSAGE IS
RECEIVED WHICH IS SHORTER THAN THE BUFFER THERE MAY BE SYNC CHARACTERS IN THE BUFFER
FOLLOWING THE LAST DATA CHARACTER. THE SINGLE BUFFER MODE IS ANTICIPATED FOR USAGE
WHERE THE INPUT MESSAGES ARE EITHER FIXED LENGTH OR A MAXIMUM LENGTH CAN BE
SPECIFIED.
10.10.2.

POOL MODE

IF AN EXECUTIVE REQUEST TO CMI$ IS FOR POOL-MODE INPUT, THE LINE TERMINAL TABLE
MUST BE CURRENTLY INITIALIZED FOR POOL-MODE INPUT, AND CONVERSELY, IF THE LINE
TERMINAL TABLE IS CURRENTLY INITIALIZED FOR POOL-MoDE INPUT, AN EXECUTIVE REQUEST TO
CMI$ MUST BE FOR POOL-MODE INPUT, AND THERE MUST BE AT LEAST ONE BUFFER CURRENTLY
AVAILA8LE IN THE INPUT POOL.
IF AN EXECUTIVE REQUEST TO CMI$ IS FOR DUAL POOL-MODE INPUT, THE LINE TERMINAL
TABLE MUST Bt CURRENTLY INITIALIZED FOR DUAL POOL-MODE INPUT, AND CONVERSELY, IF THE
LINE TERMINAL TABLE IS CURRENTLY INITIALIZED FOR DUAL POOL-MODE INPUT, AN EXECUTIVE
REQUEST TO CMI$ MUST BE FOR DUAL POOL-MODE INPUT, AND THERE MUST BE AT LEAST ONE
BUFFER CURRENTLY AVAILABLE IN THE DUAL POOL.
IN THE MULTIPLE BUFFER INPUT MODE, TWO METHODS (NORMAL POOL MODE AND DUAL POOL
MODE) OF POOL USAGE ARE PROVIDED WITH H2 OF WORD 7 POINTING TO A BUFFER POOL CONTROL
WORD WHICH LOCATES A POOL OF CHAINED BUFFERS. THE SINGLE/MULTIPLE MODE IS DETERMINED
BY THE CONTENT OF Hl OF WORD 7 OF THE LT TABLE (ZERO FOR MULTIPLE). THE DUAL POOL
MODE OF INPUT DIFFERS ONLY FROM THE NORMAL POOL MODE OF INPUT IN THAT THE FIRST
BUFFER TO BE USED IS DESIGNATED BY H1 OF WORD 9 AND ALL SUCCEEDING BUFFERS TO BE USED
ARE DESIGNATED BY H2 OF WORD 7. INPUT IN THE MULTIPLE MODE IS INITIATED BY SETTING
UP AN I/O ACCESS WORD WITH A COUNT EQUAL TO THE NUMBER OF CHARACTERS IN A FULL BUFFER
AND AN ADDRESS OF THE SECOND WORD OF THE FIRST AVAILABLE BUFFER IN THE POOL (WORD 1
IS A LINKING WORD). INPUT IS WITH MONITOR. AS EACH BUFFER IS FILLED, IT IS ADD~D TO
THE BACKUP QUEUE (WORD 8 OF LT TABLE), THE FIRST WORD OF THE BUFFER IS LOADED WITH
THE COMPLETION STATUS (53 OF WORD 1) AND THE NUMBER OF CHARACTERS TRANSFERRED INTO
THE BUFFER (Tl OF WORD 1). DEPENDING UPON THE INPUT USAGE FIELD (53 OF WORD 6), THE
INPUT COMPLETION ROUTINE IS ACTIVATED. THE END OF A MESSAGE IS DETECTED BY AN
EXTERNAL INTERRUPT (CTMC, CTS, OR WTS) OR A TIME OUT (CTMC) FOR THE SINGLE BUFFER
MODE. A MONITOR INTERRUPT CAUSES BUFFER SWITCHING WITH INPUT INITIATED USING THE
NEXT BUFFER IN THE POOL SPECIFIED BY H2 OF WORD 7.
"
UPON OCCURRENCE OF AN END-OF-MESSAGE INDICATION, FOR THE MULTIPLE BUFFER MODE, S2
OF WORD 6 IS TESTED TO INDICATE WHETHER TO SET uP INPUT INTO. ANOTHER BUFFER (NONZERO
VALUE) OR DISCARD FURTHER INPUT UNTIL THE NEXT INPUT REQUEST.
THE COMMUNICATIONS BUFFER. POOL HANDLING ROUTlNES ARE DESCRIBED IN THE CHAPTER ON
FILE REFERENCING UNDER THE FILE CONTROL SYSTEM. THE CM HANDLER PROVIDES FOR USING A
COMMON POOL AMONG SEVERAL LT GROUPS IF THE APPLICATION WILL ALLOW. ON INPUT THE

C_\
,

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

(HANDLER REMOVES BUFFERS FROM THE POOL, AND THE WORKER PROGRAM MUST RETURN THEM AFTER
PROCESSING.
THE INPUT COMPLETION ROUTINE IS ACTIVATED WITH AD SET TO THE STARTING ADDRESS OF
THE LT TABLE. THIS ROUTINE IS GIVEN CONTROL AS.A HIGH PRIORITY INTERRUPT PROCESSING
ROUTINE AND HENCE IS ALLOWED MINIMUM TIME FOR ANALSYSIS OF THE INTERRUPT. COMPLETION
ROUTINE TIMING CONSIDERATION ARE OUTLINED IN THE NEXT SECTION.
10.10.3.

INPUT ERRORS

OCTAL ERROR CODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMIS ARE AS FOLLOWS:

r-

12

INPUT POOL DOES NOT HAVE ANY BUFFERS CURRENTLY AVAILABLE
FOR POOL-MODE INPUT, OR DUAL POOL DOES NOT HAVE ANY BUFFERS
CURRENTLY AVAILABLE FOR DUAL POOL-MODE INPUT.

21

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED FOR INPUT.

23

CHARACTER COUNT SPECIFIED FOR SINGLE-MODE INPUT IS EQUAL TO
ZERO OR IS GREATER THAN THE SYSTEM MAXIMUM.

26

INPUT BUFFER SPECIFIED FOR SINGLE-MODE INPUT IS NOT WITHIN
THE BOUNDS OF THE USER'S DATA-BANK.

42

USER PROGRAM MAKING THE EXECUTIVE REQUEST IS NOT IN THE
REAL-TI ME MODE.

46

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED, OR THE INTERNAL GROUP NAME
DOES NOT SPECIFY THE CLT GROUP FOR WHICH THE LINE TERMINAL
TABLE WAS INITIALIZED.

50

INrUT BUFFER SPECIFIED FOR SINGLE-MODE INPUT IS IN THE SAME
STORAGE MODULE AS THE ESI ACCESS CONTROL WORDS.

10.11.

45

10
SECTION:

OUTPUT

OUTPUT ON LINE TERMINALS IS IN ONE OF TWO MODESJ SINGLE AND MULTIPLE BUFFER.
EITHER OF THESE MODES MAY.BE SYNCHRONOUS OR ASYNCHRONOUS. THE FOLLOWING DISCUSSES
THE TWO TYPE OF MODES, OPERATING PROCEDURES, AND ERROR CONDITIONS THAT MAY RESULTS.
SINGLE MODE
THE SINGLE BUFFER MODE IS DENOTED BY A NONZERO VALUE IN H1 OF
WORD 3. SINGLE BUFFER MODE OUTPUT IS EXPECTED TO COMPLETE AS A RESULT OF AN
EXTERNAL INTERRUPT FOR WTS OR CTS SUBSYSTEMS OR AS A RESULT OF A MONITOR INTERRUPT
FOR THE CTMC. THE USER CAN AVOID THE INTERRUPT PROCESSING FOR OUTPUT BY SPECIFYING A
CHARACTER COUNT GREATER THAN THE CHARACTER POSITION CONTAINING THE EOT INDICATION FOR
THE CIMC IN WHICH CASE THE DEVICE WILL TIME OUT WITH A STATUS CODE OF 5 IN Sl OF WORD
2 OF THE LT TABLE. THE TIME OUT METHOD IS NOT ALLOWED ON THE WTS OR CTS BECAUSE OF
THE NECESSITY OF TRANSMITTING END OF MESSAGE AND MESSAGE PARITY CHARACTERS. THE
NUMBER OF CHARACTERS TRANSFERRED IN THE SINGLE BUFFER MODE IS STORED IN H1 OF WORD 5
BEFORE THE OUTPUT COMPLETION ROUTINE IS ACTIVATED, IF SUCH A ROUTINE IS SPECIFIED.
IF AN EXECUTIVE REQUEST TO CMO$ IS FOR SINGLE-MODE OUTPUT. THE LINE TERMINAL TABLE
MUST BE CURRENTLY INITIALIZED FOR SINGLE-MODE OUTPUT, AND CONVERSELY, IF THE LINE
TERMINAL TABLE IS CURRENTLY INITIALIZED'FOR SINGLE-MODE OUTPUT, AN EXECUTIVE REQUEST

PAGE:

--------

,---

- - _.. - .-------------- ----- r------

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM.

10 .

PROGR.AMMERS REFERENCE

SECTION: "

46

PAGE:

TO CMOS MUST BE FOR SINGl.E ... MODEOUTPUT, AND THE FOl.L.OWING TWO PARAMETERS MUST BE
PROVIDED.
OUTPUT CHARACTER~OUNT (WORQ 03-Hl) SPECIFIES THE NUMBER OF OUTPUT CHARACTERS FOR
SINGLE-MODE OUTPUT AND MUST .BE GREATER THAN ZERO, MUST NOT EXCEED THE SYSTEM MAXIMUM,
AND MUST NOT BE A VALUE THATWoUL:D CAUSE THE OUTPUT BUFFER TO EXTEND BEYOND THE UPPER
BOUND OF THE USER'S DATA-BANK.
OUTPUT SUFFER ADDRESS (wORD 03-H2) SPECIFIES THE STARTING ADDRESS OF THE OUTPUT
BUFFER FOR SINGL.E-MODE OUTPUT AND MUST BE IN THE USER'S DATA-BANK AND MUST NOT BE IN
THE SAME STORAGE MODULE AS THE ESI ACCESS CONTROL. WORDS.
10.11.2.
IF AN EXECUTIVE REQUEST TO CMOS IS FOR POOL.-MODE OUTPUT, THE L.INE TERMINAL. TABl.E
MUST BE CURRENTL. Y INITIALIZED FOR POOL-MODE OUTPUT, .AND CONVERSELY, IF THE L.INE
TERMINAL TABLE IS CURRENTLY INITIAL.IZED FOR POOL-MODE OUTPUT, AN EXECUTIVE REQUEST TO
CMOS MUST BE FOR POOL-MODE OUTPUT, AND THE FOLL.OWING TWO PARAMETERS MUST BE PROVIDED.
START OF BACKUP QUEUE (WORD 04-H2) SPECIFIES THE ADDRESS OF THE FIRST BUFFER IN
THE OUTPUT QUEUE FOR POOL-MODE OUTPUT AND MUST SPECIFY A BUFFER CURRENTLY REMOVED
FROM THE OUTPUT POOL. AND NOT CURRENTLy IN ANOTHER OUTPUT QUEUE.
END OF BACKUP QUEUE (WORD O,!--Hl) SPECIFIE.S THE ADDRESS OF THE LAST BUFFER IN THE
OUTPUT QUEUE FOR POOL ... MODE OUTPUT AND MUST SPECIFY A BUFFER CURRENTL.Y REMOVED,FROM
THE OUTPUT POOL AND NOT CURRENTL.Y IN ANOTHER OUTPUT QUEUE,
THE OUTPUT QUEUE MAY CONTAIN ANY NUMBER OF BUFFERS BETWEEN ONE AND THE TOTAL
NUMBER OF BUFFERS CURRENTLY REMOVED FROM THE OUTPUT POOL AND NOT CURRENTLY IN. ANOTHER
OUTPUT QUEUE AND WHOSE FORMAT IS AS FOLLOWS:

00

-------------------------------------------.----------: CHARACTER COUNT :
:
NEXT BUFFER ADDRESS :
:
I
\
I

-----------------------------------,------------------ :
(OUTPUT CHARACTERS)

I
\
I

.

-----------------------------------------------~~------

OUTPUT CHARACTER COUNT (WORD OO-Tl) SPECIFIES THE NUMBER OF CHARACTERS TO BE
OUTPUT FROM THE BUFFER AND MUST BE GREATER THAN ZERO AND MUST NOT EXCEED THE CAPACITY
OF THE BUFFER.
NEXT BUFFER ADDRESS (WORD 00-H2) SPECIFIES THE ADDRESS OF THE NEXT BUFFER IN THE
OUTPUT QUEUE AND, EXCEPT FOR THE LAST BUFFER IN THE OUTPUT QUEUE, MUST SPECIFY A
BUFFER CURRENTLY REMOVED FROM THE OUTPUT POOL AND NOTCURRENT~Y IN ANOTHER OUTPUT
QUEUE. WORD OO-H2 OF THE LAST BUFFER IN THE OUTPUT QUEUE MAY CONTAIN ANYTHING.
IN THE MULTIPLE BUFFER OUTPUT MODE, EACH BUFFER IS TRANSFERRED WITH MONITOR, AND
UPON OCCURRENCE OF AN INTERRUPT, THE NEXT BUFFER IN THE BACKUP QUEUE IS INITIATED,
AS EACH BUFFER IS REMOVED FROM THE QUEUE, .THE CM HAND~ER UPDATES THE START OF OUTPUT
BACKUP QUEUE FIELD (H2 OF WORD 4). THE; WORKER PROGRAM ADDS TO THE QUEUE BY UPDATING
Hl OF WORD 4. AS EACH BUFFER IS EMPTYED, THE HANDLER STORES THE COMPLETION STATUS IN
53 OF. WORD 1 OF THE BUFFER AND THE NUMBER OF CHARACTERS TRANSFERRED IN T1 OF WORD 1
AND, DEPENDING UPON THE CONTENTS OF THE OUTPUT USAGE FIEL.D, ACTIVATES THE OUTPUT
COMPLETIuN ROUTINE. THE CM HANDLER EXAMINES THE START OF BACKUP QUEUE FIELD (H2 OF
WORD 5) WHEN THE OUTPUT IS FlRST INITIATEO AND T.HEN WORKS FROM THE LINK FIELD (H2 OF
WORD 1 OF THE BUFFER) TO DETERMINE .THEEND OF THE CHAIN,THE WOR~ER PROGRAM MUST A P D '
THE COMPLETED BUFFERS BACK TO THE AVAILABLE POOL..

0"'".

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

10

WHEN THE END OF THE BACKUP QUEUE IS REACHED, THE HANDLER WILL TURN OFF OUTPUT AND
A STATUS CODE OF 20 TO DENOTE THE 'CAUGHT UP' CONDITION. IF THE WORKER
PROGRAM SUBMITS A NEW BUFFER AFTER THE HANDLER MAKES THE CHECK, THIS STATUS CAN BE
USED BY THE WORKER AS AN INDICATION TO MAKE ANOTHER REFERENCE TO CMOS. THE START OF
BACKUP QUEUE MUST BE RESET FOR THIS REFERENCE.
RETUR~

THE OUTPUT cOMPLETION ACTIVITY, IF ANY, IS ACTIVATED WITH AO CONTAINING THE
ASSOCIATE LT TABLE ADDRESS, AND A1 CONTAINING THE BUFFER OR USER'S AREA LOCATION FROM
WITH OUTPUT WAS INITIATED. THIS ROUTINE IS GIVEN CONTROL AS A HIGH PRIORITY INTERRUPT
ROUTINE AND HENCE IS ALLOWED MINIMUM TIME IN ANALYSIS OF THE INTERRUPT. COMPLETE
ROUTINE TIMING CONSIDERATION ARE OUTLINED IN THE NEXT SECTION,
10.11.3.

OUTPUT ERRORS

OCTAL ERROR CODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMOS ARE AS FOLLOWS:
03

ADDRESS OF" A BUFFER IN THE OUTPUT QUEUE FO~ POOL-MODE OUTPUT DOES NOT SPECIFY A BUFFER CURRENTLy REMOVED FROM THE
OUTPUT POOL OR SPECIFIES A.BUFFER CURRENTLY IN ANOTHER OUT~
PUT QUEUE.

04

CHAR~CTER COUNT OF A BUFFER IN THE OUTPUT QUEUE FOR POOLMODE OUTPUT IS EQUAL TO ZERO OR IS GREATER THAN THE CAPACITY OF THE BUFFER.

23

CHARACTER COUNT SPECIFIED FOR SINGLE-MODE OUTPUT IS EQUAL
TO ZERO OR IS GREATER THAN THE SYSTEM MAXIMUM.

31

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED FOR OUTPUT.

34

OUTPUT BUFFER SPECIFIED FOR SINGLE-MODE OUTPUT IS NOT WITHIN THE BOUNDS OF THE USER.S DATA-BANK.

42

USER PROGRAM MAKING THE EXECUTIVE REQUEST IS NOT IN THE
REAL-TIME MODE.

46

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED, OR THE INTERNAL GROUP NAME
DOES NOT SPECIFY THE CLT GROUP FOR WHICH THE LINE TERMINAL
TABLE WAS INITIALIZED.

51

OUTPUT BUFFER SPECIFIED FOR SINGLE.MODE OUTPUT IS IN THE
SAME STORAGE MODULE AS THE ESI ACCESS CONTROL WORDS.

10.11.3.1.

(

.•..

SECOND LEVEL SUPPORT

SECOND LEVEL SUPPORT IS AN EXTENSION OF THE INTERFACE USED FOR REMOTE CPU
TRANSMISSIONS WHICH INCLUDES THE UNIVAC 1004 CARD PROCESSOR. THIS LEVEL USES THE
SYSTEM REFERENCE ER CMSA$ MEANING SEND AND ACKNOWLEDGE, IN ADDITION TO THE INITIALIZE
CMSS, TERMINATE CMTS, DIAL CMD$, AND HA!'IGUP ClYIHS DESCRIBED IN FIRST LEVEL. THESE
REFERENCES MUST BE MADE VIA AN ER INSTRUCTION WITH THE AO REGISTER LOADED WITH THE LT
TABLE STARTING ADDRESS FOR THE GROUP CONCERNED.
FOR SECOND LEVEL OPERATIONS THE EXECUTIVE REQUEST CMSAS IS THE NORMAL SYSTEM
REFERENCE, BUT THE FIRST LEVEL REFERENCES, CMIS AND CMOS, MAY ALSO BE USED IF
APPLICABLE FOR A USERS APPLICATION. THE CALLING SEQUENCE FOR THE CMSAS REQUEST IS AS
FOLLOWS:
. '
L,U
AO,LTT
ER
CMSAS
10.11.3.2. BUFFER FORMATS

PAGE:

47

,,-------~------

UP-4144
Rev. 1

-

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION: .

48
PAGE:

OUTPUT CHARACTER COUNT (WORD 03-Hi) SPECIFIES THE NUMBER OF CHARACTERS TO BE
OUTPUT FROM THE OUTPUT BUFFER AND MUST BE GREATER THAN ZERO, MUST NOT EXCEED THE
SYSTEM MAXIMUM, AND MUST NOT BE A VALUE THAT WOULD CAUSE THE OUTPUT BUFFER TO EXTEND
BEYOND THE UPPER BOUND OF THE USER'S DATA-BANK.
OUTPUT BUFFER ADDRESS (WORD 03-H2) SPECIFIES THE STARTING ADDRESS OF THE OUTPUT
BUFFER AND MUST BE IN THE USER'S DATA-BANK AND MUST NOT BE IN THE SAME STORAGE MODULE
AS THE ESI ACCESS CONTROL WORDS.
INPUT CHARACTER COUNT (WORD 07-Hl) SPECIFIES THE NUMBER OF CHARACTERS TO BE INPUT
TO THE INPUT BUFFER AND MUST BE GREATER THAN ZERO, MUST. NOT EXCEED THE SYSTEM
MAXIMUM, AND MUST NOT BE A VALUE THAT WOULD CAUSE THE INPUT BUFFER TO EXTEND BEYOND
THE UPPER BOUND OF THE USER'S DATA-BANK.
INPUT BUFFER ADDRESS (WORD 07-H2) SPECIFIES THE STARTING ADDRESS OF THE INPUT
BUFFER AND MUST BE IN THE USER'S DATA-BANK AND MUST NOT BE IN THE SAME STORAGE MODULE
AS THE ESI ACCESS CONTROL WORDS.
INPUT BUFFER TIME INTERVALS (WORD 09-H2) SPECIFIES THE NUMBER OF 600-MILLISECOND
TIME INTERVALS TO BE ALLOWED FOR THE NORMAL COMPLETION OF INPUT TO THE INPUT BUFFER.
THIS SUPPORT ASSUMES SEVEN BIT CHARACTERS(SIX DATA PLUS ONE PARITY)WITH THE
FOLLOWING MESSAGE FORMAT:
SOM - START OF MESSAGE
CONTROL CHARACTER
DATA
EOM - END OF MESSAGE
MPC - MESSAGE PARITY CHARACTER
EOB - END OF BUFFER
THE VARIATIONS THAT MAY APPEAR IN THE WORKER PROGRAM BUFFER DEPENDS UPON THE TYPE
OF SUBSYSTEM. FOR THE CTS, ALL OF THESE CHARACTERS MUST BE PRESENT IN OUTPUT BUFFERS
AND ALL EXCEPT THE SOM AND EOB ARE TRANSMITTED TO THE INPUT BUFFER. 'THE" WTS COMPUTES
MESSAGE PARITY AND GENERATES THE SOM AND EOM HENCE ONLY THE CONTROL AND DATA
CHARACTERS ARE NEEDED FOR OUTPUT AND OBSERVED FOR INPUT. FOR CTMC DEVICES A~L OF THE
SPECIFIED CHARACTERS MUST BE PRESENT FOR OUTPUT AND ALL EXCEPT EOB WI~L APPEAR IN THE
INPUT BUFFER. IN ADDITION FOR CTMC DEVICES, A MINIMUM OF TWO SYNC CHARACTERS MUST
PRECEDE THE SOM CHARACTER FOR OUTPUT. THE SYNC CHARACTERS WI~L NOT APPEAR IN TH~
INPUT RUFFER. THE FOLLOWING ILLUSTRATES THE PREVIOUS EXPLANATIONS OF SECOND LEVEL
WORKER PROGRAM BUFFER VARIATIONS FOR THE DIFFERENT SUBSYSTEMS OF WTS, CTS, AND CTMC.

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

CTMC OUTPUT BUFFER

SEQUENCE & SOURCE

10
SECTION:

CTMC INPUT

-----------------

---------------------. .---.----

SYNC (MINIMUM IS 2 SYNC)
SYNC (MAX AS PROGRAMMED)
SaM
CONTRO~ CHARACTER
DATA
EOM
MPC
EOB

SYNC (BUFFER)
SYNC (BUFFER)
SOM (BUFFER)
CONTRO~ CHAR (BUFFER)
DATA (BUFFER)
EOM (BUFFER)
MPC (BUFFER)

CTS OUTPUT BuFFER
SaM

CONTRO~

DATA
EOM
MPC
EOB

CHARACTER

WTS OUTPUT BUFFER

(

~INE

SYSTEM

--.-------------CONTRO~

DATA

CHARACTER

~INE

SEQUENCE & SOURCE

SaM
CONTRO~

DATA
EOM
MPC

CHAR

cTS INPUT

--------.------------. .-------SYNC (CTS--MIN:2)
SYNC (MAX:CTS OPTION)
SOM (BUFFER)
CONTRO~ CHAR (BUFFER)
DATA (BUFFER)
EOM (BUFFER)
MPC (BUFFER)

~lNE

SEQUENCE & SOURCE

CONTRO~

DATA
EOM
MPC

CHAR

WTS INPUT

--------.------------- .-------SYNC (WTS--MIN:2)
SYNC (MAX=WTS OPTION)
SOM (WTS)
CONTRO~ CHAR (BUFFER)
DATA (BUFFER)
EOM (WTS)
MPC (WTS)

CONTROL CHAR
DATA

THE CONTRO~ CHARACTER INDICATES BOTH THE OPERATION TO BE PERFORMED AND THE SUCCESS
OF A PRECEEDING TRANSMISSION. THE TOGG~ING OF THE ~OW ORDER BIT POSITION IS UsED TO
INDICATE A SUCCESSFUL OPE~ATION WHI~E A RETRANSMISSION IS INDICATED BY THE RECEIPT OF
A CONTRO~ CHARACTER IDENTICAL TO THAT OF A PRECEEDING TRANSMISSION.
THE ACKNOWLEDGE MESSAGE IS IN THE FORMAT PREVIOUS~Y DEFINED WITH ZERO DATA
CHARACTERS. THIS DICTATES THAT A~~ MESSAGES EXCEPT ACKNOW~EDGE MUST BE TWO CHARACTERS
(ONE CONTROL CHARACTER PLUS ONE DATA CHARACTER) OR MORE IN LENGTH.
EACH MESSAGE TRANSFERRED BY SECOND ~EVEL MUST BE CONTAINED WITHIN A SINGLE BUFFER.
COMPLETE OUTPUT MESSAGES MAY BE CHAINED, IN WHICH CASE A REQUEST TO CMSAS IS
NECESSARY ONLY TO START THE CHAIN. SINCE FINAL CHECK ON INPUT MUST BE MADE BY THE
wORKER BEFORE ANOTHER MESSAGE CAN BE RECEIVED, CHAINED INPUT IS NOT POSSIBLE AND EACH
INPUT, MESSAGE ~IUST BE REQUESTED,
A REQUEST TO CMSAS CAUSES THE CM HAND~ER TO SET UP OUTPUT OF THE MESSAGE ON THE
LINE TERMINA~ AND AFTER TRANSMISSION, TO SET UP INPUT TO RECEIVE THE ACKNOWLEDGE. IF
THE ACKNOW~EDGE HAS IL~EGAL PARITY OR SPECIFICALLY REQUESTS RETRANSMISSION, THE SAME
BUFFER WIL~ BE SENT AGAIN. IF THE ACKNOWLEDGE IS FAVORABLE, A STATUS CODE IS .sTORED
IN Sl OF WORD 3 (SINGLE BUFFER MODE) OR IN S3 OF THE FIRST WORD OF THE BUFFER IF A
POO~ IS USED, AND THE NEXT MESSAGE IN THE CHAIN, IF ONE EXISTS, IS SENT,
TRANSMISSION COMP~ETION CAUSES INITIATION OF THE OUTPUT COMP~ETION ROUTINE UNDER THE
SAME CIRCUMSTANCES AS DESCRIBED FOR FIRST ~EVEL SUPPORT. IF NO ACKNOWLEDGE IS

49
PAGE:

UP-4144

UNIVAC

Rev.l

1108

EXEC B

OPERATING

SYSTEM

PROGRJ;\.MMERS REFERENCE

10

50

SECTioN:

PAGE:

RECEIVED IN RESPONSE TO A TRANSMISSION OR IF THE ACKNOWLEDGE IS UNSUCCESSFUL AFTER 5
RETRIES, THE ON-SITE OPERATOR IS NOTIFIED BY ONE OF THE MESSAGES:
C/U
C/U

SEND TIMEOUT
SEND PAR)TY

THE TIME OUT RESULTS FROM NO ACKNOWLEDGEMENT RETURNED W.ITHIN 5 MINUTES. THIS TIME
IS ALLOWED FOR REMOTE OPERATOR MANUAL INTERVENTION; CHANGING PAPER, ETC. IN ADDITION
TO THE TYPEOUT, ALL FAILURES ARE WRITTEN IN THE SYSTEM LOG. AT TERMINATION OF THE
COMMUNICATIONS LINKAGE(REFERENCE TO CMT$),THE NUMBER OF MESSAGES SENT AND RECEIVED
AND THE NUMBER OF RETRANSMISSIONS REQUIRED IS ALSO LOGGED. THE OPERATOR CAN RESPOND
TO THESE MESSAGES TO EITHER TRY TRANSMITTING AGAIN (LETTER A) OR DECLARE THE LINE
DOWN (LETTER D). A DOWN RESPONSE RESULTS IN A STATUS CODE OF 02 TO BE RETURNED. NO
FURTHER ACTION IS TAKEN ON QUEUED BUFFERS. IF A SUBSEQUENT REQUEST IS MADE WITH THE
LINE DOWN, THE 02 STATUS CODE IS RETURNED WITHOUT TAKING ANY OTHER ACTION ON THE
BUFFER.
THE CMSA$ REQUEST CAN ALSO BE USED TO SEND AN ACKNOWLEDGE MESSAGE AND SET UP TO
RECEIVE A MESSAGE ON THE INPUT LINE TERMINAL ASSIGNED TO THE ADDRESSED L1 TABLE.
EXCEPT FOR CTMC CHANNELS, THE HARDWARE PROVIDES FOR CHARACTER PARITY CHECKING FOR THE
INPUT MESSAG~" UPON DETECTION OF A PARITY ERROR, A REQUEST FOR RETRANSMISSION IS
SENT. THUS THE MESSAGE HAS PASSED PARITY (EXCEPT ON CTMC) WHEN THE WORKER PROGRAM
RECEIVES THE MESSAGE~ THE WORKER PROGRAM IS EXPECTED TO VERi-FY MESSAGE PARITY FOR AN
INPUT MESSAGE RECEIVt.D VIA THE CTMC SINCE THE WORKER PROGRAM WILL PROBABLY PERFORM
SOME TYPE OF DATA PACKING ON THE INPUT eTMC MESSAGE WHICH IS THE MOST CONVENIENT
POINT FROM A SYSTEM STANDPOINT TO PERFORM THE MESSAGE PARITY VERIFICATION, UPON
COMPLETION OF INPUT, THE INPUT COMPLETION ROUTINE IS ACTIVATED, DEPENDENT UPON THE
INPUT USAGE FIELD VALUE, AND THE JNPUT LINE TERMINAL IS TURNED OFF UNTIL THE NEXT
REQUEST. THE USER PROGRAM MAY SUBJECT THE INPUT MESSAGE TO WHATEVER CHECKS DESiRED
BEFORE ACKNOWLEDGING. REGARDLESS OF THE FACT THAT ONLY ONE MESSAGE IS RECEIVED AT A
TIME, THE BUFFER POOL TECHNIQUE CAN BE USED FOR INPUT AS WELL AS OUTPUT.
SECOND LEVEL OPERATION IS PROVIDED IN EITHER HALF OR FULL DUPLEX OPERATION,
FULL DUPLEX OPERATION IT IS NECESSARY THAT THE REMOTE SUBSYSTEM RETURNS THE
ACKNOWLEDGE MESSAGE AS A SEPARATE ENTITY.
10.11.4.

~

~.

",~J

FOR

ERROR CODES

OCTAL ERROR CODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMSA$ ARE AS FOLLOWS:
21

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED FOR INPUT,

23

OUTPUT CHARACTER COUNT SPECIFIED OR INPUT CHARACTER COUNT
SPECIFIED IS EQUAL. TO ZERO OR EXCEEDS THE SYSTEM MAXIMUM.

25

INPUT CHARACTER COUNT SPECIFIED FOR A WTS SUBSySTEM IS NOT
AN INTEGRAL MULTIPLE OF.SIX CHARACTERS.

26

INPUT BUFFER SPECIFIED IS NOT WITHIN THE BOUNDS OF THE USER'S DATA-BANK,

31

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMINAL TABLE CURRENTLY INITIALIZED FOR OUTPUT.

34

OUTPUT BUFFER SPECIFIED IS NOT WITHIN THE BOUNDS OF THE USER'S DATA ... BANK.

42

USER PROGRAM MAKING THE EXECUTIVE REQUEST IS·NOT IN THE
REAL-TIME MODE.

46

LINE TERMINAL TABLE ADDRESS DOES NOT SPECIFY A LINE TERMI-

c

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

NAl TABLE CURRENTLY INITIALIZED, OR THE INTERNAL GROUP NAME
DOES NOT SPECIFY THEClT GROUP FOR WHICH THE lINE TERMINAL
TABLE WAS INITIALIZED.
50

INPUT BUFFER SPECIFIED IS IN THE SAME STORAGE MODULE AS THE
ESI ACCESS CONTROL WORDS.

51

OUTPUT BUFFER SPECIFIED IS IN THE SAME STORAGE MODULE AS
THE ESI ACCESS CONTROL WORDS.

10.12.

HANG-UP

THE EXECUTIVE REQUEST CMH$ CAUSES RELEASE OF THE CURRENT REMOTE CONNECTION. AT
THE TIME THE HANG-UP REQUEST IS MADE, THE WORKER PROGRAM SHOULD INSURE THAT OUTPUT
HAS BEEN COMPLETED AND ANY INPUT WHICH MAY OCCUR IS OF NO CONCERN. THE HANGUP
REQUEST DISREGARDS THE CURRENT lINE ACTIVITY AND ISSUES A REMOTE RELEASE TO THE DIAL
AND INPUT ClTS, ANY FURTHER ACTIVITY AFTER THE HANGUP MUST BE PRECEDED BY A DIAL
REQUEST TO ACTIVATE THE TERMINAL. .
IF NO AUTOMATIC DIALING EXIST FOR A IT GROUP, A HANGUPREQUEST WIll CAUSE THE
FOllOWING MESSAGE TO BE DISPlAYED'ON THE CONSOLE:
HANGUP

CC/UU

NO RESPONSE IS REQUIRED BY THE OPERATOR FOR THIS MESSAGE. A HANGUP REQUEST FOR A
lEASED-lINE IT GROUP IS IGNORED EXCEPT CAUSING QUEUED OUTPUT OR SUBSEQUENT INPUT TO
BE IGNORED.
WHEN AN EXECUTIVE REQUEST IS MADE TO CMH$ THE USER MUST BE IN THE REAL-TIME MODE
AND REGISTER AO MUST CONTAIN THE ADDRESS OF THE lINE TERMINAL TABLE. THE CAllING
SEQUENCE IS AS FOllOWS:
l,U
AO,lTT
ER
CMH$
10.13.

COMMUNICATION TERMINATION

THE FUNCTION OF THE CMTS EXECUTIVE REQUEST IS TO DEACTIVATE THE INPUT AND/OR
OUTPUT TERMINALS AND PERFORM VARIOUS HOUSEKEEPiNG ASSOCIATED WITH A IT GROUP. THE
REQUEST WIll CAUSE A RELEASE FUNCTION TO BE SENT TO THE INPUT ClT ASSOCIATED WITH THE
LTT. THE ASSIGNMENT FOR THE DEVICE IS NOT RELEASED FROM THE USER.S PROGRAM AND CAN BE
REINITIAlIlED VIA A CMS$ REQUEST. A COMMUNICATION DEVICE IS NOT RElEASEcr UNTIL THE
DEVICE IS RELEASED VIA A QFR£E OR WHEN THE PROGRAM TERMINATES.
TERMI'NATION ERRORS
OCTAL ERROR ~ODES AND THE ERROR CONDITIONS WHICH WILL BE DETECTED WHEN AN
EXECUTIVE REQUEST IS MADE TO CMT$ ARE 'AS FOllOWS:
16

ADDRESS OF A LINE' TERMINAL TABLE DOES NOT SPECIFY A LINE
TERMINAL TABLE CURRENTLY INITIALIZED, OR THE INTERNAL GROUP
NAME DOES NOT SPECIFY THE ClT GROUP FOR WHICH THE lINE TERMINAL TABLE WAS INITIALIZED.

17

USER PROGRAM MAKING THE EXECUTIVE REQUEST IS NOT IN THE
REAL~TIME MODE.

(10.n..

ROUTE$

51

10
SECTION:

PAGE:

UNIVAC 1108 OPERATING

JP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

52

10
SECTION:

PAG.E:

#~'

('j

THE 1108 COMMUNICATION HANDLER PROVIDES THE USER THE OPPORTUNITY TO DYNAMICALLY
THE PRIMARY PATHS OF COMMUNICATION LINE TERMINAL GROUPS(LTG) BY INITIATING THE
EXECUTIVE REQUEST ROUTES.
A~TER

EACH PRIMARY LTG IS DEFINED AT SYSTEM GENERATION TIME AND PROVIDES THE NECESSARY
INFORMATION FOR THE COMMUNICATION HANDLER AND FACILITY INVENTORY TO MAKE ASSIGNMENTS
VIA THE ASG CONTROL CARD. THE PRIMARY LTG MAy DEFINE UP TO THREE TERMINALS-INPUT,
OUTPUT, AND/OR DIAL. THE PRIMARY LTG PARAMETERS ARE MAINTAINED IN THE ELEMENT TODRUM
FROM 21 PARAMETERS AS SPECIFIED IN CHAPTER 18 OF THE PROGRAMMERS REFERENCE MANUAL.
AS THE PRIMARY LTG WILL NORMALLY DEFINES THREE CLT'S AS A GROUP, INPUT, OUTPUT,
AND DIAL, AN AN ALTERNATE LTG CONFIGURATION MAY DEFINE ONE, TWO, OR THREECLT'S. AN
ALTERNATE LTG MAY BE ANOTHER ASSIGNABLE PRIMARY LTG OR UNASSIGNABLE EXCEPT BY THE
ROUTEs EXECUTIVE REQUEST. IF A PRIMARY LTG IS ROUTED TO ANOTHER PRIMARY LTG, BOTH
INPUT AND OUTPUT CLT'S MUST BE ROUTE9 OR THE FIRST PRIMARY WILL REMAIN IN AN ASSIGNED
STATE AND CAN NOT BE ASSIGNED AGAIN VIA EITHER AN ASG CONTROL CARD OR A ROUTES
REQUEST. ONCE A PRIMARY LTG HAS BEEN ROUTED, ALL DIAL AND/OR HANG UP OPERATIONS WILL
BE INITIATED USING THE NEW LTG. HOWEVER, IF THE PRIMARY LTG WAS ONLY PARTIALLY
ROUTED, INPUT OR OUTPUT, BUT NOT BOTH, THE COMMUNICATION HANDLER WILL PROVIDE DIALING
SPECIFIED BY THE OUTPUT CLT ALTERNATE ONLY. IT WILL BE THE RESPONSIBILITY OF THE
USER TO PERFORM MANUAL DIALING FOR THE LTG NOT DlALED BY THE HANDLER. IF BOTH INPUT
AND OUTPUT CLTS OF A PRIMARY LTG ARE ROUTED, THE PRIMARY LTG WILL BE HUNG UP BY THE
HANDLER.
10.14.1.

ROUTE$ CALLING SEQUENCE

THE FOLLOWING DEFINES THE FORMAT FOR THE EXECUTIVE REQUEST ROUTES:
L
L

AO,(MODE,LTADDR)
Al,POINTER

WHERE ,

MODE=l-REQUEST FOR INPUT ALTERNATE CLT
2-REQUEST FOR OUTPUT ALTERNATE CLT.
3-REQUEST FOR BOTH INPUT AND OUTPUT CLTS.
LTADDR=USER'S LINE TERMINAL (LT) TABLE ADDRESS.
POINTER=SPECIFY AN ALTERNATE OF THE
PRIMARY LTG AS DEFINED VIA
THE ACTMC CONFIGURATION
CARD, WHERE 1,2,3, ••• ,N, SPECIFY
THE LOGICAL ALTERNATE.

ROUTING PROCEDURES
BEFORE A ROUTE$ REQUEST CAN BE MADE TO THE COMMUNICATION HANDLER, THE USER,S LT
TABLE MUST BE INITIALIZED USING THE EXECUTIVE REQUESTCMSS. ONCE THE LT TABLE HAS
BEEN INITIALIZED, THE ROUTES REQUEST MAY BE REFERENCED AS FREQUENTLY AS DESIRED. ONCE
A PRIMARY LTG HAS BEEN ROUTED, THE PRIMARY LTG IS NOT AVAILABLE FOR THIS ASSIGNMENT.
EITHER A FREE REQUEST MUST BE INITIATED OR THE PRIMARY LTG MAY BE AN ALTERNATE OF
IT'S A~TERNATES AND THE ROUTES REQUEST MAY BE INITIATED TO REESTABLISH THE ORIGINAL
ASSIGNMENT. IF THE PRIMARY LTG BEING ROUTED HAS AN IOLE/LINE MONITOR STATE AND BOTH
INPUT AND OUTPUT ARE ROUTED THE PRIMARY LTG WILL BE REESTABLISHED IN THE IDLE/LINE
MONITOR STATE.
'

THE FO~LOWING ERROR CODES WIL~ BE RETURNED IN THE ROUTES WILL SUPERCEDE THOSE
SPECIFIED IN THE 1108 PROGRAMMERS REFERENCE MANUAL. THE ROUTES ERROR CODES WILL BE

UP-4144
Rev-.1

UNIVAC 1108 OPERATING

EXEC

a

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

RETURNED IN THE USER'S ERROR CONTINGENCY PACKET IN S2 WITH Sl SET EQUAL TO 06 WHEN AN
ERROR IS DETECTED BY THE COMMUNICATION HANDLER.
20

A ROUTEs REQUEST WITH AN INVALID PROGRAM ,TYPE, PROGRAM
TYPE MUST BE REAL TIME.
A ROUTEs REQUEST WITH AN INVALID LT LOCATION.
A ROUTEs REQUEST WITH NO FACILITIES ASSIGNED FOR
THE SPECIFIED LT.
A ROUTEs REQUEST AND uSERS LT HAS NOT BEEN INITIALIZED.
A CMSS REQUEST MUST BE INITIATE BEFORE A ROUTEs REQUEST
WILL BE HONORED,
A ROUTEs REQUEST WITH A MODE CODE GREATER THAN 3
OR EQUAL TO ZERO,
A ROUTEs REQUEST WITH AN INVALID POINTER WHEN
REQUESTING AN ALTERNATE PATH, THE POINTER SPECIFIED IN
Al IS GREATER THAN THE NUMBER OF ALTERNATES S~ECIFIED
AT SYSTEMS GERERATION TIME OR ZERO.
A ROUTE$ REQUEST REQUESTING AN OUTPUT ALTERNATE, BUT
OUTPUT NOT PERMITTED FOR THE ALTERNATE.
A ROUTEs REQUEST REQUESTING AN IN~UT ALTERNATE, BUT
INPUT NOT PERMITTED FOR THE ALTERNATE.
A ROUTE$ REQUEST FOR AN ALTERNATE PATH ALREADY
ASSIGNED.
A ROUTE$ REQUEST WITH ALTERNATE DRUM PACKET
ADDRESS SPECIFIED AT SYSTEMS GENERATION TIME EQUAL TO
ZERO. INDICATES AN ERROR IN SYSTEM GENERATION PARAMETER
ALTPKT.
A ROUTE$ REQUEST WITH ALTERNATE'S DRUM ADDRESS IN
DRUM PACKET EQUAL ZERO.

21
22
23
24
25

26
27
30
31

32

(
10'15'

COMPLETION ACTIVITIES

COMPLETION ACTIVITIES ARE INITIALIZED BY THE COMMUNICATION HANDLER WHEN THE
EXECUTIVE REQUEST CMSS IS REFERENCED. COMPLETION ACTIVITIES, NORMALLY REFERRED TO AS
ESI ACTIVITIES, ARE ACTiVITIES THAT ARE GIVEN CONTROL ON THE OCCURANCE OF AN ESI
INTERRUPT OR lSI INTERRUPT IF CTS OR WTS SUBSYSTEMS. THE USERS CAN SPECIFY AN ESI
ACTIVITY FOR EACH CLT, INPUT AND/OR OUTPUT, BY SPECIFyING IN THE LTT A USE AGE cODE
AND A COMPLETION LOCATION FOR EACH RESPECTIVE MODE OF OPERATION. AN ESI ACTIVITY IS
CONTROLLED BY THE CM VIA A 4 WORD PACKET, REFERRED TO AS ESI CONTROL PACKET, WHICH IS
CREATED IN THE USER'S PCT, WHEN AN ESI ACTIVITY IS GIVEN CONTROL THE USER'S AO WILL
CONTAIN THE RESPECTIVELY LTT ADDRESS AND A1 WILL CONTAIN THE USER'S BUFFER LOCATION
IF POOL MODE OPERATION OR DATA AREA IF SINGLE MODE OPERATION. THE COMPLETE SET OF
USER'S REGISTERS ARE AVAILABLE IN AN ESI ACTIVITY, BUT ARE NEITHER PASSED OR RESTORED
ONCE THE ACTIVITY HAS RELEASED CONTROL, NOR ARE THEY PASSED BETWEEN REAL-TIME AND ESI
ACTIVITIES,
10,15.1.

ESI ER REQUESTS

THE ESI ACTIVITY MAY RELEASE CONTROL VIA 4 EXECUTIVE REQUESTS: EXITs, ACTs,
CADDS, AND ADACTS, REFERENCE TO ANY OTHER REGUEST WILL RESULT IN AN ESI CONTINGENCY
CONDITION. THE FOLLOWING DISCUSSESS THE APPLICATION AND REQUIRED FORMATS OF THE
ABOVE REQUESTs.
10.15.1.1. ESI EXITs
THE EXECUTIVE REQUEST EXITs FROM AN ESI ACTIVITY PROVIDES THE NORMAL EXITs FOR
THAT COMPLETION ACTIVITY.
10,15.1,2.

ESI ACTS

THE EXECUTIVE REQUEST ACTs PROVIDES AN EXIT FROM AN ESI ACTIVITY AND ACTIVATES AN

53
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS. REF.EReNCe

10
SECTION:

i

S4
PAGE:

o
ACTIVITY PREVIOUSLY NAMED USING THE EXECUTIVE REQUEST NAMES IN THE REAL TIME PROGRAM,
THE CALLING SEQUENCE OF THE ACT$ REQUEST IS AS FOLLOWS:
L
AO,NAME
ER
ACTS
WHERE'
WHERE NAME IS THE CONTENTS OF AO RETURNED
FROM THE EXECUTIYE REQUEST NAMES.
10.15.1.3.

ESI CADD$

THE EXECUTIVE REQUEST CADD$ PROVIDES AN EXIT FROM THE ESI ACTIVITY AND RELEASE OF
THE BUFFERS IN THE 2 WORD PACKET SPECIFIED BY THE USER'S AO, THE CALLING SEQUENCE IS
AS FOLLOWS:
L
ER

AO,PKTADDR
CADD$

WHERE'
PKTADD IS THE LOCATION OF A TWO WORD
PACKET IN THE FORMAT SPECIFIED IN THE PROGRAMMERS
REFERENCE MANUAL.
10.15.1.4.

ESI ADACTS

THE EXECUTIVE REQUEST ADACTs ·PROVIDES AN EXIT FROM AN ESI ACTIVITY, RELEASES THE
BUFFERS PROVIDED IN THE TWO WORD PACKET SPECIFIED BY THE USER,S AO AND ACTIVATES THE
ACTIVITY SPECIFIED BY THE NAME IN THE USER.S A1 THE CALLING SEQUENCE OF THE 'ADACTt
REQUEST IS AS FOLLOWS:
,
L
A1,NAME
L
AO,PKTADDR
ER
ADACTS
WHERE,
NAME-DEFINES THE NAME PASSED IN AO FROM THE NAMES
EXECUTIVE REQUEST.
PKTADDR-DEFINES THE ADDRESS OF A TWO WORD CADDS
PACKET IN THE FORMAT SPECIFIED IN THE
PROGRAMMER'S REFERENCE.
10.16.

IDLE LINE MONITOR

AT SYSTEM GENERATION THE INPUT LINE TERMINAL DEVICES CAN BE GIVEN AN UNASSIGNED
STATUS OF EITHER OFF OR STANDBY. THE STANDBY STATUS CAUSES INPUT TO BE ENABLED ON THE
DEVICES WHEN NOT ASSIGNED TO A PROGRAM. UPON RECEIPT OF A PARTICULAR IDENTIFYING
CHARACTER STRING, EITHER AN APPROPRIATE SYMBIONT OR A NAMED RUN IS INITIATED. THE
RUN FILE MUST ALREADY HAVE BEEM READ INTO THE OPERATING ENVIRONMENT. IF UNATTENDED
ANSWERING IS PROVIDED ON THE INPUT DEVICE AND THE SUBSYSTEM IS CAPABLE OF CAUSING
EXTERNAL INTERRUPTS, THEN NO INPUT BUFFER IS SET UP UNTIL THE OCCURRENCE OF A DIAL
SUCCESSFUL INTERRUPT. CORE STORAGE REQUIREMENTS FOR THE IDLE LINE MONITOR FEATURE
ARE APPROXIMATELY 85 PERMANENT LOCATIONS. THESE LOCATIONS HOLD SUCH THINGS AS
INTERNAL TABLES, SWITCH LIST ENTRIES, AND ACTIVITY SAVE AREAS PLUS EIGHT LOCATIONS
FOR EACH INPUT L.INE ACTUALLY IN A STANDBY CONDITION.
10.17,

TIMING CONSIDERATIONS

WITHIN THE REALM 'OF COMMUNICATIONS EQUIPMENT HANDLING THERE ARE THREE LEVELS QF
ACTIVIty WHICH MUST BE TAKEN INTO ACCOUNT TO DETERMINE THE COMMUNICATION ACTIVITY
WHICH CAN BE ALLOWED IN 'CONJUNCTION WITH OTHER 1/0 ACTIVITY, REAI.-TIME CI.OCK ACTIVITY

C

'._ .

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

(AND CPU USAGE,

THESE LEVELS ARE:

1, INTERRUPT RESPONSE
2. BUFFER PROCESSING
3. INFORMATION ANALYSIS
10.17.1,

INTERRUPT LEVEL

THE FIRST LEVEL, INTERRUPT RESPONSE, OCCURS WITHIN THE CM HANDLER AND CONSISTS OF
SETTING UP THE NEXT BUFFER FOR THE INTERRUPTING LINE TERMINAL, QUEUING THE INTERRUPT,
AND REINITIATING THE INPUT OR OUTPUT MODE. THE NECESSARY CRITERIA TO BE MET BY THE
HANDLER IS, 1) INSURING THAT THE MODE BE RESET WITHIN THE CHARACTER AVAILABILITY OF
THE FASTEST LINE TERMINAL DEVICE ON THE CHANNEL(196 MICROSECONDS FOR 40,800 CPS AT 8
BrT CHARACTERS), AND 2) INSURING THAT EACH INTERRUPT IS PROCESSED IN A TIME INTERVAL
SUCH THAT ALL ACTIVE LINES COULD BE READY TO INTERRUPT AT THE SAME TIME AND NO
INFORMATION IS LOST ON ANY LINE. IF SINGLE BUFFER MODE IS EMPLOYED, THEN THE SECOND
CASE IS OF NO CONCERN FOR THE GIVEN LINE(THE INTERRUPT TERMINATES ACTIVITY ON THAT
LINE)BUT MUST BE CONSIDERED FOR LOWER PRIORITy MULTIPLE BUFFER LINES. THE
CONFIGURATION SHOULD BE ARRANGED WITH THE HIGHEST SPEED LINE TERMINALS WHICH MAY BE
USED IN THE MULTIPLE BUFFER MODE IN THE HIGHEST PRIORITY INTERRUPT POSITION (LOWEST
ESI CHANNEL NUMBER AND HIGHEST PRIORITY MULTIPLEXOR POSITION). THEN TO INSURE NO
LOSS OF INFORMATION FOR EACH LINE" TERMINAL, HIGHER PRIORITY INTERRUPTS PLUS THE
SINGLE INTERRUPT FOR THIS LINE TERMINAL MUST BE HANDLED WITHIN THE CHARACTER
AVAILABILITY TIME OF THAT LINE. THE COUNT OF HIGHER PRIORITY INTERRUPTS MUST
INCLUDE:
1. ONE FOR EACH ESI EXTERNAL INTERRUPT WHICH CAN OCCUR IN
THE CHARACTER AVAILABILITY TIME.
2, ONE FOR EACH HALF DUPLEX I/O LINE TERMINAL PAIR OF HIGHER
PRIORITY
3. ONE FOR EACH SIMPLEX LINE OF HIGHER PRIORITY.
4. TWO FOR EACH HIGHER PRIORITY FULL DUPLEX PAIR
5. ONE FOR THE LINE OF CONCERN
IF ANY BUFFER OF A HIGHER PRIORITY LINE CAN FILL ONCE OR MORE WITHIN THE CHARACTER
AVAILABILITY TIME, ONE MUST BE ADDEO FOR EACH OCCURRENCE. THE CHARACTER AVAILABILITY
DIVIDED BY 40 MICROSECONDS SHOULD BE GREATER THEN THE NUMBER COMPUTED. THIS VALUE
TAKES INTO ACCOUNT THE INTERRUPT PROCESSING INSTRUCTIONS PLUS DATA TRANSFERS. FOR
INSTANCE WITH THE CONFIGURATION OF:
10 FULL DUPLEX 1004'S AT 4800 BPS(CA:1.25MS)
250 HALF DUPLEX KSR 35 TELETYPE*MACHINES AT 100 WPM(CA=20MS)
THE INTERRUPT COUNT FOR THE LOWEST PRIORITY 1004 IS 19 (2 FOR EACH OF THE 9 HIGHER
PRIORITY FULL DUPLEX" PAIR PLUS 1 FOR THE LINE OF CONCERN) AND THE LOWEST PRIORITY
TELETYPE* MACHINE IS 270 WHICH ARE LESS THAN THE LIMITS OF 1250/40:31 AND
20000/_0=500 RESPECTIVELY, HENCE THERE WOULD BE NO LOSS OF INFORMATION IF THE ENTIRE
SYSTEM WAS OPERATED SIMULTANEOUSLY IN A MULTIPLE BUFFER MODE(REMOTE 1004 UNDER EXEC
CONTROL WILL NORMALLY BE A SINGLE BUFFER OPERATION). IT SHOULD BE NOTED THAT CTS AND
WTS EQUIPMENT IS OPERATED ON 151 MODE CHANNELS AND HENCE ARE LOWER INTERRUPT PRIORITY
THAN ALL ESI CHANNELS. ALSO THE WTS INCORPORATES CHARACTER ASSEMBLY INTO FULL WORDS
AND HENCE MULTIPLIES THE CHARACTER AVAILABILITY TIME.
10.17.2.

('-

BUFFER LEVEL

BUFFER PROCESSING IS A WORKER FUNCTION TO BE PERFORMED FROM THE INPUT AND OUTPUT
COMPLETION ACTIVITIES. THESE ACTIVITIES ARE GIVEN PRIORITY, WITHIN THE DISPATCHING
ALGORITHM IMMEDIATELY BELOW INTERRUPT HANDLING. THE MOST CRITICAL BUFFER PROCESSING
ROUTINES ARE EXPECTED TO BE THOSE THAT HANDLE MULTIPLE BUFFER MODE LINE TERMINALS,
THESE MUST OPERATE WITHIN THE CONSTRAINT THAT EACH BUFFER MUST BE PROCESSED WITHIN
THE TIME IT TAKES TO FILL THE NEXT BUFFER IN THE CHAIN(UNLESS THE POOL IS OF
SUFFICIENT LENGTH TO CONTAIN AN ENTIRE MESSAGE FOR EACH TERMINAL CONCERNED), AND EACH
BUFFER PROCESSING ROUTINE MUST SHARE THE CPU SUCH THAT ALL ROUTINES HAVE A CHANCE TO
.TRADEMARK OF TELETYPE CORPORATION

55
PAGE:

UNIVAC 1108 OPERATING

UP-4,144
Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

10
SECTION:

PAGE:

56

PROCESS THEIR CORRESPONDING BUFFERS. THE NEED TO SHARE THE CPU AMONG THE PROCESSING
ROUTINES DICTATES THAT A TIME INCREMENT MUST BE CHOSEN SUCH THAT SWITCHING FROM ONE
COMPLETION TO ANOTHER IS BASED ON THE REAL-TIME CLOCK. THIS TIME INCREMENT IS SET BY
A SYSTEM GENERATION PARAMETER(IF OMITTED NO MAXIMUM EXISTS). THE BASIS FOR
DETERMINING THIS INTERVAL IS:
EACH BUFFER MUST BE PROCESSED IN THE TIME INTERVAL, TO, TO
FILL THE LARGEST (IN TERMS OF TIME) BUFFER, TMAX, DIVIDED BY
THE NUMBER OF BUFFERS WHICH CAN FILL IN THE MAXIMUM INTERVAL.
A GIVEN BUFFER CAN FILL TMAX/TI TIMES WHERE TI IS THE TIME
REQUIRED TO FILL A BUFFER (NUMBER OF CHARACTERS TIMES THE
CHARACTER TRANSFER RATE). TMAX IS THE LARGEST VALUE OF TI
IN THE SYSTEM. HENCE THE TIME LIMIT, TO, IS GIVEN BY THE
FORMULA:
TMAX

TO=----------------------TMAX TMAX TMAX
TMAX
----+----+----+
..•
+.--T1 T2
T3
TN
1

:------------1
1 1

1

--+--+--+ ••• +-11 T2 T3
TN
T1T2T3T4 ••• TN

:----------------------------------T1T3 ••• TN+T1T2T4 ••• TN+ ••• +T2T3 ••• TN
THE UPPER AND LOWER LIMITS OF TO ARE DETERMINED BY Tl=T2=T3= ••• TN=TMIN AND
TI=TMIN WITH ALL OTHER T1 ••• TN CONSIDERABLY LARGER WHICH GIVES:
TMIN
---- (TO
N

=

< TMIN

THE APPROXIMATION IS REASONABLE THAT ALL DEVICES WILL BE BUFFERED SUCH THAT THE TIME
TO FILL EACH IS NEARLY EQUAL, HENCE TD=TMIN/N CAN BE USED. THE VALUE N INCLUDES:
1 FOR EACH SIMPLEX INPUT OR OUTPUT
1 FOR EACH HALF DUPLEX PAIR
2 FOR EACH FULL DUPLEX PAIR
WHERE ONLY MULTIPLE BUFFER MODE LINES ARE CONSIDERED. TO CAN NOW BE CHANGED AS
BUFFERS ARE LENGTHENED OR SHORTENED. IN THE INTERVAL TO DURING WHICH THE BUFFERS
MUST BE PROCESSED, THE ONLY TIME WHICH THE COMPLETION ACTIVITY WILL NOT HAVE CONTROL
IS DURING CYCLES TAKEN FOR DATA TRANSFERS AND TIME NEEDED TO QUEUE INTERRUPTS. IN
THE WORST CASE ALL ACTIVE COMMUNICATIONS LINES AND ALL STANDARD LINES MAY INTERRUPT.
HENCE WITH:
TD=10 MILLISECONDS
50 ACTIVE LINE LINES AT 2400 BPS AT 7 BITS/CHAR
1 FH432(2400QO WORDS/SEC)
1 FASTRAND CHANNEL(25,150 WPS)
1 VIII C TAPE CHANNEL(16,000 WPS)
IN THE TO INTERVAL FOR THE EXAMPLE GIVEN ABOVE, THERE COULD BE
(240+25.15+16)(1000)(0.01):2811 DATA TRANSFERS AT 0.75 MICROSECONDS PER TRANSFER=2.1
MILLISECONDS. FOR HIGH SPEED CHANNELS, 50(10 MS)(1.5 MICROSEC)/2.91 MS = 0.25 MS FOR
COMMUNICATIONS LINE TERMINAL DATA TRANSFERS AND (53 INTERRUPTS) (25 MICROSECONDS PER
INTERRUPl)=1.33 MILLISECONDS FOR INTERRUPTS WHICH LEAVES 10-(2.1+0.25+1.33)=6.32
MILLISECONDS AS THE MINIMUM TIME THE PROGRAM CAN COUNT ON FOR EXECUTING INSTRUCTIONS.
SINCE ONLY MULTIPLE BUFFER MODE IS CRITICAL, THE CM HANDLER W.ILL E~TER INTERRUpT

C""'."

UNIVAC 1108 OPERATING

UP-4144
Revo1

EXEC B

SYSTEM

10

PROGRAMMERS REFERENCE

COMPLETION ACTIVITIES INTO ONE OF TWO

SECTioN:

QUEUES CONTROLLED BY THE DISPATCHER:

MULTIPLE BUFFER COMPLETION ACTIVITIES
SINGLE BUFFER COMPLETION ACTIVITIES
THE NATURE OF MULTIPLE BUFFER MODE PROCESSING IS SUCH THAT IT IS MORE TIME CRITICAL
THAN SINGLE BUFFER MODE PROCESSING AND WILL BE HANDLED BY THE DISPATCHER IN A MANNER
SUCH THAT SINGLE BUFFER MODE ACTIVITIES WILL BE GIVEN CONTROL ONLY WHEN THE MULTIPLE
BUFFER MODE ACTIVITY QUEUE HAS BEEN EXHAUSTED.
.
10.17.3.

ANALYSIS LEVEL

THE THIRD LEVEL OF ACTIVITY TO BE CONSIDERED, INFORMATION ANALYSIS, IS ALSO A
WORKER FUNCTION. THIS ACTIVITY IS NORMALLY EXPECTED TO BE REAL~TIME WITH A USER
DETERMINED RESPONSE TIME. THIS IS HANDLED BY THE EXECUTIVE THROUGH THE STANDARD
DISPATCHING ALGORITHM,
10.17.4.

ERROR CODES FOR LT CONTINGENCIES

EACH WORKER PROGRAM TO WHICH COMMUNICATION DEVICES ARE ASSIGNED IS EXPECTED TO
HAVE AN ERROR HANDLING ROUTINE REGISTERED WITH THE EXECUTIVE SYSTEM. THIS ERROR
HANDLING ROUTINE WILL BE THE COMMUNICATIONS HANDLER'S MEANS OF NOTIFYING THE USER OF
SYSTEM AND LT GROUP ERROR CONDITIONS WHICH DO NOT APPLY TO THE TRANSMISSION OR
RECEPTION OF A PARTICULAR BUFFER. THE WORKER PROGRAM WILL BE NOTIFIED IN THE MANNER
AND FORMAT AS DEFINED UNDER PROGRAM CONTINGENCY 'ERR MODE' CONDITION.
FOLLOWING IS
A LIST OF THE POSSIBLE ERROR CODES AND THEIR MEANING WHEN THAT CODE IS STORED IN THE
S2 PORTION OF THE FIRST WORD OF THE ERROR ROUTINE,

(

CODE

----

MEANING

1

AN ER CMSS REFERENCE HAS BEEN MADE
FROM THE WRONG TYPE OF CODING. USE
OF THIS ER IS NOT PERMITTED FOR
DEMAND, DEAD-LINE BATCH, OR BATCH
ACTIVITIES.

2

AN ER CMSS REFERENCE HAS SPECIFIED
AN ADDRESS IN H2 OF AO WHICH IS
BEYOND THE LIMITS OF THE PROGRAM.

3

THE INITIALIZATION°REQUEST SPECIFIES
A LT TABLE WHICH IS CURRENTLY IN USE
OR HAS BEEN INITIALIZED BUT HAS
NEVER BEEN TERMINATED.

5

AN INVALID VALUE WAS SPECIFIED FOR
THE INPUT COMPLETION ACTIVITY USAGE
CODE WITHIN THE REQUESTING PACKET
FOR AN ER CMSS,

6

THE FILE NAME FOR AN INITIALIZATION
REQUEST DOES NOT APPEAR IN THE
FACILITY ASSIGNMENT SECTION OF THE
USER'S PROGRAM CONTROL TABLE (PCT).

7

THE END OF INPUT ACTIVITY CODE IN
THE PACKET FOR AN INITIALIZATION
REQUEST IS NOT VALID.

10

AN ER CMIS OR CMOS REFERENCE AND LTG

ACTION
---.....

THIS PROBABLY
INDICATES THE
FILE HAS NOT
BEEN ASSIGNED.

57
PAGE:

----.

UP-4144

Rev. 1

._ ....

",

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

10
SECTION:

58
PAGE:

HAS BEEN TERMINATED DUE TO ESICONTINGENCY
ERROR OR NO ESI CONTINGENCY SPECIFIED FOR
AN ESI CONTINGENCY.
11

THE CONTROL GROUP ADDRESS SPECIFIED
IN A PACKET TO BE USED FOR POOL MODE
OF OPERATlON IS INVALID.

12

POOL MODE OF OPERATION HAS BEEN
SPECIFIED, BUT NO BUFFERS PRESENTLY
EXIST IN THE POOL SPECIFIED AS THE
ONE TO BE USED.

13

THE ADDRESS WITHIN THE PACKET SPECIFIED AS THE INPUT COMPLETION ACTIVITY WAS NOT VALID.

14

THE OUTPUT USAGE CODE SPECIFIED
WITHIN THE PACKET FOR AN INITIALIZATION REQUEST IS NOT VALID.

15

AN ER CMS$ REFERENCE SPECIFYING OUTPUT POOL
MODE WITH INVALID POOL 10 OR CLOSED MODE.

16

AN ER CMT$ REFERENCE HAS SPECIFIED A LT
GROUP WHICH HAS BEEN TERMINATED PREVIOUSLY OR HAS NEVER BEEN INITIALIZED.

17

AN ER CMT$ REFERENCE HAS BEEN MADE FROM
THE WRONG TYPE OF COOING. USE OF THIS
ER IS NOT PERMITTED FOR DEMAND, DEADLINE BATCH, OR BATCH ACTIVITIES.

20

AN ER CMT$ REFERENCE HAS SPECIFIED AN
ADDRESS IN H2 OF AO BEYOND THE BOUNDS
OF THE PROGRAM,

21

A REQUEST FOR AN INPUT OPERATION HAS
SPECIFIED A FILE NAME FOR WHICH INPUT IS NOT PE~MISSABLE (NO INPUT
FACILITY FOR THE LT GROUP WAS DEFINED AT SYSTEMS GENERATION ~IMEJ.

22

AN INVALID VALUE WAS SPECIFIED FOR
THE INPUT COMPLETION USAGE CODE
WITHIN THE REQUESTING PACKET FOR
AN ER CMI$I

THE POOL MAY Be:TEMPORARILY
EXHAUSTED, TOO
SMALL OF A POOL
WAS ESTABLISHED,
OR THE REAL-TIME
PROGRAM MAY HAVE
FAILED TO RETURN
TO THE POOL THE
BUFFERS WHICH
HAD BEEN REMOVED
PREVIOUSLY BY
THE COMMUNICATIONS HANDLER.
IF THE ,SITUA, nON CAN BE
CORRECTED DYNAMICALLY, THE
PACKET MUST BE
RESUBMITTED.

o

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

(

(

23

THE NUMBER OF CHARACTERS SPECIFIED
FOR A SINGLE MODE INPUT OR OUTPUT OPER~
ATION EXCEEDS THE MAXIMUM PERMISS~
ABLE VALUE ESTABLISHED AT SYSTEMS
GENERATION TIME.

2~

AN ADDRESS BEYOND THE BOUNDS OF THE
PROGRAM WAS SPECIFIED IN H2 OF AD
FOR A CMIS, CMOS, OR CMSAS REQUEST.

25

A NON-MULTIPLE OF 6 WAS SPECIFIED
AS THE CHARACTER COUNT FOR AN INPUT
OPERATION ON THE WTS SUBSYSTEM.

26

AN INPUT OPERATION HAS SPECIFIED A
CHARACTER COUNT AND BUFFER STARTING
ADDRESS SUCH THAT A PORTION OF THE
INPUT BUFFER EXISTS BEYOND THE
LIMITS OF THE PROGRAM,

27

AN INPUT OR OUTPUT oPERATION HAS SPECIFIED
POOL MODE OF OPERATION FOR.A FILE
NAME ASSOCIATED WITH EQUIPMENT WHICH
USES THE lSI METHOD OF BUFFERING.
BUFFER SWAPPING FOR lSI DEVICES IS
NOT PERMITTED BECAUSE OF THE DESIGN OF
THE HARDwARE WHICH OPERATES ON DATA
BY BLOCKS RATHER THAN AS A CONTIN~
UOUS INPUT STREAM.

30

AN CMI$, CMOS' OR CMSAS REQUEST AND
SPECIFIED LTT HAS INVALID FILE NAME.

31

A REQUEST FOR AN OUTPUT OPERATION
HAS SPECIFIED A FILE NAME FOR WHICH
OUTPUT IS NOT PERMISSABLE (NO OUTPUT
FACILITY FOR THE LT GROUP WAS DEFINED AT SYSTEMS GENERATION TIME).

32

AN INVALID VALUE WAS SPECIFIED FOR
THE OUTPUT COMPLETION USAGE CODE
WITHIN THE REGUESTING PACKET FOR
AN ER CMOS.

3~

AN OUTPUT OPERATION HAS SPECIFIED
A CHARACTER COUNT AND A BUFFER
STARTING ADDRESS SUCH THAT A PORTION OF THE OUTPUT BUFFER EXISTS
BEYOND THE LIMITS OF THE PROGRAM.

36

37

POOL AREA
POOL SIZE
POOL AREA
PROGRAM'S
POOL AREA
PROGRAM'S

IS ILLEGAL BECAUSE: (1 )
EQUALS ZERO WORDS, (2)
IS SPLIT: BETWEEN USER
D-BANK AND I~BANK, OR (3)
IS BEYOND BOUNDS OF USER
AREA.

THE CORE AREA SPECIFIED BY AN
ER CPOOL$ IS LOCATED IN THE I-BANK.
POOL BUFFERING USING THE I-BANK IS
NOT PERMITTED SINCE A PROGRAM IS
SUPPOSED TO BE SO POSITIONED IN CORE
SUCH THAT THE HAROWARE MEMORY OVER-

THE REFERENCE
TO CPOOL$ MUST
SPECIFY A CORE
AREA ASSOCIATED
WITH ITS D-BANK.

10
SECTION·:

59
PAGE:

..

-

_.-

--

.. .. . . . _.

UP-4144

--_.... _.....

__._._._-_._. -- ...... _.- -_.__ .. _ -_._--_.__...._----_.-

UNIVAC

Rev.l

..

1108

EXEC B

OPERATING

._._ ....

__

.... _......... -

-- - -

--_._. _. __ .. -

._---_._ ...... _._ __

SYSTEM

..

.

.._--_._.. - ------- .. - -_..

__ . -

10

PROGRAMMERS REFERENCE

SECTION:

60
PA-GE:

LAP FEATURE FOR ESI DATA TRANSFERS
WILL BE UTILIZED IN ORDER TO REDUCE
THE NUMBER OF CORE MEMORY ACCESSES
FROM 3 TO 2 FOR EACH DATA TRANSFER.
40

BUFFER SIZE IS ILLEGAL BECAUSE: (1)
CHARACTER COUNT EGUALS ZERO OR (2)
CHARACTER COUNT EXCEEDS SYSTEM'S
SPECIFIED MAXIMUM.

41

POOL AREA IS NOT LARGE ENOUGH FOR:
(1) A MINIMUM OF ONE BUFFER FOR AN
OPEN CHAIN OR (2) USER PROGRAM'S
SPECIFIED NUMBER OF BUFFERS FOR A
CLOSED CHAIN.

42

AN ER TO THE COMMUNICATIONS HANDLER
HAS BEEN EXECUTED FROM THE WRONG
TYPE OF CODING, USE OF THE COMMUNICATIONS HANDLER IS NOT PERMITTED
FOR DEMAND, DEADLINE BATCH, OR BATCH
ACTIVITIES.

43

THE SINGLE MODE OF BUFFERING HAS
SPECIFIED A COMMUNICATIONS BUFFER
WHICH IS IN THE I-BANK. COMMUNICATIONS BUFFERS ARE NOT PERMITTED IN
THE I-BANK BECAUSE REAL-TIME PROGRAMS ARE PROPERLY POSITIONED IN
CORE SO THAT THE D-SANK CAN UTILIZE
THE MEMORY OVERLAP FEATURE FOR EACH
CHARACTER TRANSFER.

45

THE ADDRESS WITHIN THE PACKET SPECIFIED AS THE OUTPUT COMPLETION ACTIV ...
ITY WAS NOT VALID FOR AN ER CMSS.

46

AN ER HAS BEEN MADE REQUESTING USE
OF A LT GROUP BY THE COMMUNICATIONS
HANDLER BEFORE THAT LT GROUP HAS
BEEN INITIALIZED.

47

AN ER CMOS HAS DESIGNATED THAT POOL
MODE SHOULD BE USED FOR OUTPUT, BUT
THE BUFFER POOL CONTROL WORD SPECIFIED
IN THE LT TABLE IS INVALID.

50

AN ER CMIS FOR SINGLE BUFFER MODE
HAS SPECIFIED AN INPUT BUFFER AREA
WHICH CONFLIcTS WITH THE MAIN STORAGE MODULE LOCATIONS OF THE ESI
ACCESS CONTROL WORDS, COMMUNICATIONS BUFFERS ARE NOT PERMITTED IN
THE SAME MAIN STORAGE MODULE AS THE
ESI ACW'S BECAUSE OF THE EXTENDED
TIME REQUIRED FOR EACH CHARACTER
TRANSFER WHEN THE MEMORY OVERLAP
CAPABILITY IS NOT UTILIZED.

THE REAL-TIME
PROGRAM MUST BE
PROPERLY POSITIONED IN MAIN
STORAGE SO AS
TO TAI;0
051
052
13.e.3.

MOVE ADDRESS NOT GIVEN ON IN/OUT
READ OR WRITE REQUEST.
MOVE. ADDRESS NOT GIVEN ON READ OR
WRITE REQUEST OF SPANNED ITEM.
ITEM SIZE FIXED ON REQUEST TO
WRITE A SPANNED ITEM.
ADDRESS OF ITEM
MOVE ADDRESS
GIVEN ON IN/OUT READ OR WRITE
REQUEST.
ADDRESS OF ITEM
MOVE ADDRESS
GIVEN ON RANDOM READ OR WRITE
REQUEST.
RANDOM REQUEST MADE IN FILE
WITHOUT FIXED ITEMS AND BLOCKS.
OPERATION ATTEMPTED ON A CLOSED
FILE.
LABEL SPECIFIED BUT NOT FOUND ON
OPEN INPUT REQUEST.
UPDATE FLAG NOT SET ON IN/OUT FILE
READ REQUEST.
HIGHEST ADDRESS WRITTEN NOT SET ON
IN/OUT FILE WRITE EXTEND REQUEST.
DRAIN REQUESTED ON IN/OUT FILE.
A RE~UEST WAS MADE TO WRITE A
SPANNED ITEM AFTER READING IT.
A REQUEST WAS MADE TO WRITE MORE
THAN THE SIZE READ ON IN/OUT FILE.
READ BACKWARGS REQUESTED ON A
SPANNED ITEM.
FORMAT NOT SET IN FILE CONTROL
TABLE.
TAPE POS IT IOIILO I MPROPERL Y ON OPEN
REQUEST
FRAME COUNT ERROR DETECTED AND USER
DID NOT SPECIFY TO ACCEPT AS NORMAL.
AN EOF BLOCK WAS DETECETD ON A
RANDOM READ REQUEST.
FIXED ITEM LARGER THAN MAX BLOCK SIZE.

=
=

Al.!NOHil,AL CONDITIONS

WHE:.rJ At~ ABrJORMAL CONUITION OCCURS, COt.TROL IS RETURNED TO THE USER VIA THE FILE
c.;UIHROL TAflLE' S AiJNORMAL EXIT. FOR EACH OCCURf~ENCE OF AN ABNORMAL CONDITION, ~EGISTER
Al WlLL CO:JTAIIJ THE ABNOHMAL CODE IN ITS UPPEf{ HALF AND THE USER,S RE-ENTRY LOCATION
IIJ lTS LOWER HALF. HEGISTER AD WILL CONTAW THE SIZE AND DATA LOCATION OF THE BLOCK
REAU OR TO BE (IIU TTEN.
ABNORMAL COUES RETURNED TO USER ARE:

41
PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC. B

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

42
PAGE:

10

U

CODE(OCTAL)

DESCRIPTION
EOF-OF-FILE MARK OR LOAD POINT
HAS BEEN DETECTED FOR INPUT
TAPE FILE OR FASTRAND HIGHEST
ADDRESS (EOF) HAS BEEN DETECTED.
END-OF-TAPE MARK HAS BEEN DETECTED
FOR OUTPUT FILE
SENTINEL BLOCK HAS BEEN DETECTED
FOR FILE.
BLOCK PREVIOUSLY READ EXCLUSIVELy
HAS BEEN TIMED OUT BY THE SYSTEM
FORAN IN/OUT FILE.

01

02
06

010

THE FOLLOWING ERROR CODES ARE RETURNED TO THE USER VIA THE ABNORMAL ERROR EXIT
WHILE AN ERROR IS DETECTED IN A SENTINEL BLOCK WHEN USING THE SYSTEMS LION FORMAT:
CODE (OCTAL)
DESCRIPTION
004
LABEL WORD ERROR HAS BEEN
DETECTED IN LABEL BLOCK FOR
AN INPUT FILE..
012
LABEL BLOCK CANNOT BE LOCATED, BAD
TAPE POSITION.
013
BLOCK SIZE SPECIFIED IN FILE
CONTROL TABLE IS LESS THAN 14
WORDS FOR AN OUTPUT FILE. FOR
AN INPUT FILE BLOCK SIZE OF
SENTINEL IS GREATER THAN BLOCK
SIZE SPECIFIED IN FILE CONTROL
TABLE.
014
ITEM SIZE SPECIFIED IN FILE CONTROL
TABLE NOT EQUAL TO ITEM SIZE IN
SENTINEL BLOCK FOR AN INPUT FILE.
RECOVERY CAN BE MADE FOR ERROR CODES OQ4, 013, AND 014 BY CLOSING THE FILE,
M0UIFYING THE RESPECTIVE FIELDS IN THE FILE CONTROL TABLE, AND INITIATING THE OPEN
PROCEDURE AGAIN. FOR ERROR CODE 012, THE TAPE MUST BE REPOSITIONED.

THE FOLLOWING CALLING SEQUENCES MAY BE USED BY THE USER TO REFERENCE BLOCK
BUFFERING FUNCTIONS. THESE CALLING SEQUENCES DESCRIBE THE ACTUAL CODING GENERATED BY
USING THE PROCEDURE CALLS FOR THE BLOCK BUFFERING FUNCTIONS AND MAY BE USED DIRECT~Y
BY THE USER. FOR EACH CALL TO BLOCK BUFFERING, AO MUST CONTAIN THE ADDRESS OF A ONE
Ok TWO WORD PACKET THAT WILL CONTAIN THE REQUIRED PARAMETERS FOR THE REQUEST.

LA,U
AO,PKT AOUR
ER
E:lOPEr~$
NORMAL RHURN
PACKET:
35

1

30

23

17

o

.-.--------------.-----------------------.-------: 1\10DE : REWIND
FCTABLE ADDRESS
--------------------------------------------------

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

WORD 1 52-INDICATES THE REQUESTED MODE FOR FILE.
MODES: 02
INPUT(FORWARD)
03
INPUT(REVERSE)
040
OUTPUT
041
IN/OUT
53-INDICATES REWIND OPTION FOR TAPE FILE OR IN/OUT
EXTENDING/UPDATING OPTION.
OPTIONS: 0
REQUEST FOR REWIND ONLY.
UPDATING FOR IN/OUT MODE,
013
EXTENDING FOR IN/OUT MODE.
021
REQUEST FOR REWIND WITH LOCK.
023
REQUEST FOR NO REWIND.
H2-ADDRESS OF THE FILE CONTROL TABLE THAT MAINTAIN
THE FILE IN QUESTION.

13.9.2.

WRITE FUNCTIONS

LA,U AO,PKT ADDR
ER
BWRIT$
NORMAL RETURN
PACKET:
35
1

WORD 1

17

o

17

0

-------------------------------------------------FCTABLE ADDRESS
-------------------------------------------------H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS
THE FILE IN QUESTION.

13.9.2.2.
LA,U
LMJ
LA,U
ER
NORMAL
*PACKET:
1
2

WORD 1
NORD 2

13.9.3.

("

1 3 .9. 3 .1.
LA,U
ER

FORMS 2-4
Ao,PKT ADUR*
Xll,B$WMOV
AO,I-'KT AiJDR*
BWRIT$
RETURI-J
35

-------------------------------------------------FCTABLE ADDRESS
-------------------------------------------------NBR-WDS
DATA ADDRESS
-------------------------------------------------H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS
THE FILE IN QUESTION.
H1-SPECIFIES THE NUMBER OF WORDS TO MOVE OR O.
H2-SPECIFIES THE LOCATION IN USERS AREA DATA WILL
BE MOVED FROM OR O.
READ FUNCTIONS
FORM 1
AO,PKT AODR
BREAO$

43
PAGE:

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

13
SECTION:

..

NORMAL RETURN
FORMS 2-3
LA,U
ER
LA,U
LM..J
NORMAL

AQ,PKT ADDR**
BREAD$
AQ,PKT ADDR**
Xll,B$MOVE
RETURN

.. PACKET:
35

17

o

---------------------------------------------~---FCTABLE ADDRESS

1
2

WORD 1
WORD 2

--.-.-.-----.-------.---------------.----.-------NBR-WDS
DATA ADDRESS
.-.-.-.----------.------------------.----.------.H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS
THE FILE IN QUESTION.
H1-SPECIFIES THE NUMBER OF WORDS TO MOVE OR Q.
H2-SPtCIFIES THE LOCATION IN USERS AREA DATA WILL
BE MOVED TO.

RANDOM WRITE FUNCTIONS

13.9.'+.
13. 9 .'+.1.

FORM 1

LA,U
AQ,PKT ADDR***
BRWRT$
ER
NORMAL RETURN
13,9.'+.2.
LA,U
LM.J
LA,U
EK
NORMAL

FORMS 2-4
AQ,PKT ADUR***
Xll,B$WMOV
AQ,PKT ADDR***
BRWRT$
RETURN

17

o

2

--.---.-----------.-.--------------------.--.---.FCTABLE ADDRESS
------.-----------.-----------.-----.-.--.--.---.DATA ADDRESS
NBR-WDS

wORD 1

--.---.---.-------------------------.------------H1-NON-ZERO FOH AN EXCLUSIVE READ REQUEST.

1

------------------------~------------------------BLOCK NUMBER

~ORO

2

WORD 3

H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS
THE FILE IN QUESTION •.
HI-SPECIFIES THE NUMBER OF WORD TO MOVE FROM/OR TO
USERS AREA.
H2-SPECIFIES THE LOCATION IN USERS AREA WHERE
DATA WIL~ BE MOVED FROM OR TO.
NOTE: FOR FORM 1 READ OR WRITE FUNCTIONS WORD 2
IS ZERO.
POSITION IN FILE wHERE BLOCK WILL BE READ OR
WRITTEN.

c

UP-4144
Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

RANDOI\II REAL) FUNCTIONS

13.9.5.

FORM

13.9.5.1.

1

LA,U
AO,PKT ADDR***
ER
BRRED$
NORMAL RETURN
FORMS 2-3

13.9.5.2.

LA,U
ER
LA,U
LM.J
NOkMAL

CLOSE REEL/FILE FUNCTIONS

13.9.6.

(

AO,PKT ADDR***
BRRED$
AO,PKT ADDR***
Xl1,B$MOVE
RETURN

AO,PKT ADDR
BCLOR$
RETURN

LA,U
ER
NORMAL
OR
LA,U
ER
NORMAL

AO,PKT ADDR
BCLOF$
RETURN

PACKET:
35

1

WORD 1

13.9~7.

30

23

17

0

-------------------------------------------------FCTABLE ADDRESS
: REWIND :
-------------------------------------------------53-REWIND OPTION FOR TAPE FILES
OPTIONS:

0 REQUEST REWIND ONLY
021 REQUEST REWIND WITH LOCK
023 REQUEST NO REWIND
H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS THE
FILE IN QUESTION.

WRITE EOF FuNCTION

LA,U
AO,PKT AD DR
ER
BMARK$
NORMAL RETURN
PACKET:
35
1

WORD 1

30

23

-------------------------------------------------FCTABLE ADDRESS
-------------------------------------------------H2-ADDRESS OF FILE CONTROL TABLE THAT MAINTAINS THE
FILE IN QUESTION.

I~

THE USER WISHES TO USE THE ITEM HANULER WITHOUT CALLING THE ITEM HANDLER

45
PAGE:

l1P-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

13
SECTION:

46
PAGE:

PROCEDURES, THE FOLLOWING METHOD MUST BE USED, THE LOCATION OF A PACKET IS LOADED IN
AO' AN LM~ IS MAOE ON Xll TO THE APPROPRIATE ENTRY IN THE ITEM HANDLER, EG:
L,U

AO,PACKET LOCATION
Xl1,ITEM ENTRY

LM~

THE ITEM HANDLER ENTRIES FOR THE VARIOUS FUNCTIONS ARE:
OPEN FILE , , • • • IHOPN
WRITE SEQUENTIAL ,IHWRT
WRITE RANDOM ' "
IHWTRN
READ SEQUENTIAL • • IHRD
READ RANDOM • • • , IHRDRN
DRAIN • • • • • • • IHDRN
CLOSE REEL • • • • IHCLR
CLOSE FILE • • • • IHCLF
THE REQUEST PACKETS ARE 1, 2, OR 3 WORDS LONG, AND CONTAIN THE FOLLOWING
INFORMATION:
OPEN FILE

---.~-------.-----------------------o
*: ** : FCTABLE REQUEST :

---.--------------------.-----------WRITE SEQUENTIAL

---.---------------.----------------.
o
: FCTABLE ADDRESS :
------------------------------------MOVE ADDREsS
MOVE LENGTH
----~--------------------------------

READ SEQUE;NTIAL

-----.--~---------------------------o
: FCTABLE ADDRESS :

------------------------.-----------MOVE LENGTH
MOVE AODRESS
------.-----------------.-----------o
EOF EXIT
------------~------------------------

READ AND WRITE RANDOM

------------------------------------***
: FCTABLE ADDRESS :
-----------.------------.--.--------MOVE ADDRESS
---------------------------.--------o
EOF EXIT
---------~------------------------.--

DRAIN

.------------.-----------------.----o
: FCTABLE ADDRESS :
------.----.-------.----.------------

CLOSE FILE AND REEL

------------------------.-----------o
o
** : FCTABLE ADDRESS :
-.-------------------------.---------

THE FOLLOWING FIELDS NEED FURTHER DEFINING:

*

MODE

040
02

_
-,

OUTPUT FILE
INPUT FILE, FORWARD MODE

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

PROGRAMMERS REFERENCE

03
O~l

**

SYSTEM

REWIND OPTION

INPUT FILE, REVERSE MODE
IN/OUT FILE
0
FIELDATA L

EXTENSION

***

(

0
1

-

FIELDATA N
- FIELDATA E

NORMAL RANDOM REQUEST
EXCLUSIVE READ REQUESTED

REWIND WITHOUT
INTI::RLOCK
REWIND WITH
INTERLOCK
NO REWIND
OPEN IN/OUT FILE
FOR EXTENSION

13
SECTION:

47
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
REFERENCE

13
SECTION:

48
P'AGE:

o
13.11.

13.11.1.

FILE ORGANIZATION

ITEM LEVEL TAPE

F~LES

TAPE FILES PROCESSED BY ITEM CONTROL WILL HAVE END~OF-FILE MARKS RECORDED
AUTOMATICALLY BY THE ROUTINE. THE PLACEMENT OF THESE MARKS IS AS FOLLOWS:
(A) TWO MARKS ARE RECORDED AFTER AN END OF REEL OR END OF FILE
SENTINEL BLOCK.
(8) IF AN END OF REEL OR END OF FILE SENTINEL IS NOT WRITTEN,
TWO END-OF-FILE MARKS FOLLOW THE LAST VALID DATA BLOCK.
(C) WHEN A HEEL CONTAINS MORE THAN ONE FILE THE 2ND OF THE
rwo MARKS IS OVERWRITTEN THEREBY SEPARATING FILES WITH
ONE MAR"'.
(0) A SPECIAL SEPARATOR BLOCK IS RECORDED BY ITEM CONTROL WHEN
A FILE IS OPENED AND CLOSED ON TAPE WITHOUT RECORDING ANY
UATA AND ENO-OF-FILE SENTINELS HAVE NOT BEEN SPECIFIED.
THE BLOCK DENOTES AN EMPTY (VOID) FILE AND SERVES TO SEPARATE
THE E~D-OF-FILE MARKS.

c

UP-4144

Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

SINGLE FILE REELS
: LAIJ[L
: BLOCK

: LABEL
: BLOCK

----------

----------

FILE

FILE

FILE

FILE

AHEA

AREA

AREA

AREA

---------MARK

---------MARK

------------------: EOF

MARK

: EOF
BLOCK :
MAHK
r.llARK

~lARK

BLOCK :

---------MARK
MARK

49
PAGE:

UP-4144

Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

50
PAGE:

c
MULTI-FILE REELS
: LABEL
: BLOCK

--..------: LABEL
: BLOCK

----------

----------

---.-----.

FILE

FILE

FILE

FILE

AREA

AREA

AREA

AREA

MARK

---------MARK
----------

---.------

FILE

---------MARK

: EOF
BLOCK :

--.------MARK

: LABEL
: BLOCK

AREA

; LABEL
: BLOCK

FILE

:
FILE
AREA

AREA

--.------MARK
MARK

---------MARK
MARK

: EOF
BLOCK :

FILE
AREA

------------------: EOF
BLOCK :

---------MARK
MARK
: EOF
BLOCK :

MARK
MARK

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

MULTI-FILE REELS WITH AN EMPTY (VOID) FILE

---------LABEL

---------LABEL

---------

-------------------

----------

----------

FILE

FILE

FILE

FILE

AREA

AREA

AREA

AREA

----------

---------MARK
---------: LABEL

---------MARK
---------:SEPARA- :

------------------: EOF

·· BLOCK
·
---------....

: EOF
BLOCK :
MARK

: LABEL
: BLOCK

: EOF
BLOCK :
MARK
MARK

··· BLOCK

: SLOCK
MARK
MARK

: TOR BLK:
MARK
r"lARK

BLOCK :

---------MARK
---------: EOF
BLOCK :

MARK
MARK

51
PAGE:

UP-4144

Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

13

PROGRAMMERS REFERENCE

SEcnON:

MULTI-REEL FILES (REEL 1 SHOWN - SUBS QUE NT REEL LAYOUT IS SAME)

---------·· LABEL
·------.--· BLOCK
--.-------

---------··· LABEL
BLOCK
----------

FILE

--

----------

----------

FIL.E

FILE

FILE

AREA

AREA

AREA

AREA

----------

---------MARK

---------MARK

----------

... ~------

MARK
: EOR
BLOCK :
MARK
MARK

MARK

: EOR
BLOCK :

---------MARK
MARK

52
PAGE:

UP-4144

Rev. 1

13.11.2.

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM

13

REFERENCE

SECTION:

ITEM LEVEL FASTRAND FILES

: LABEL
: BLOCK

FILE
ARC::A

---------: LABEL
: BLOCK

----------

----------

----------

FILE

FILE

FILE

AREA

AREA

AREA

----------

---------: EOF

: EOF
BLOCK :

BLOCK :

VOID FASTRAND FILES

: LABEL
: BLOCK

(

: LABEL
: BLOCK

: EOF
BLOCK :

: EOF
BLOCK :

13.11.3.

BLoCK BUFFERING LEVEL TAPE AND FASTRAND FILES

TAPE AND FASTRAND FILES AT THE
DATA. END-OF-FILE MARKS WILL NOT
MARKS IS AT THE DISCRETION OF THE
TO ELIMINATE THE INPUT OF INVALID

(-

---------.
.

---------.

BLOCK BUFFERING LEVEL ARE ASSUMED TO CONTAIN PURE
BE AUTOMATICALLY RECORDED. THE PLACEMENT OF THESE
USER. IT IS SUGGESTED HOWEVER, THAT THEY BE USED
DATA WHEN READING.

53
PAGE:

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

13

PROGRAMMERS REFERENCE

SECTION:

54
PAGE:

c
13.12.

SYSTEM DATA FILE FORMAT (SDF)

SDF PROVIDES THE SYSTEM WITH A BASIC FORMAT FOR DATA HANDLING BETWEEN THE VARIOUS
SYSTEM COMPONENTS, AND BETWEEN THE SYSTEM AND THE USER. SDF FORMAT IS PRODUCED BY
THE ~DATA AND gFILE PROCESSORS, AND IS THE FINAL FORMAT OF THE SYSTEM ACCOUNTING
FILE. ALL SYMBIONT PROCESSED FILES ARE OF THIS FORMAT, INCLUDING THOSE FILES TO BE
INSERTED INTO THE CONTROL STREAM WITH THE ~ADO CONTROL STATEMENT. SOURCE ELEMENTS
ARE NECESSARILY OF THE SAME FORMAT.
SDF HAS INTEGRATED FASTRAND AND MAGNETIC TAPE COMPATIBILITY BY 1) ADHERING TO
BLOCK LENGTHS OF FASTRAND SECTOR MULTIPLES,2) IMBEDDING FILE LABELS IN THE DATA AS
THE INITIAL IMAGE OF THE FILE, 3) WRITING THE FILE AS A ,CONTINUOUS SET OF DATA
WlTHOUT BLOCK CONTROL WORDS AND 4) INCORPORATING THE BLOCK BUFFERING PACKAGE'S
FACILITY OF SEQUENTIAL FILE PROCESSING.
.
FORMAT DEFINITION
DATA OF THE FILE IS RECORDED IN VARIABLE LENGTH IMAGES, WITH EACH IMAGE BEING
PkECEDED WITH A LENGTH. FILE IMAGES FALL INTO TWO CATEGORIES:
1. CONTROL IMAGES

THESE IMAGES PROVIDE FILE CONTROL INFORMATION SUCH AS THE
FILE LABEL, END OF FILE SENTINEL, ETC. THE FORMAT IS
35

30

24

00

---------------------------.--: 1:S : CL :
---------------------------.--: CONTROL IMAGE. NUMBER
---------------------------.--: OF WORDS DEFINED BY
-.-------------------------.--: CONTROL IMAGE LENGTH (CL).
-.----------------------------BIT 35 IS SET EQUAL TO 1 FOR ALL CONTROL IMAGES AND THE 'S'
FIELD SPECIFIES THE TYPE. THE DEFINITION OF S VARIES WITH
THE FILE TyPE. E.G. FILES GENERATED FOR PRINT SYMBIONTS USE
UNIQUE S DEFINITIONS. HOWEVER, CERTAIN S DEFINITIONS APPLY
THROUGHOUT THE SYSTEM. THEY ARE
TYPE

S VALUE

LABEL IMAGE.............
END OF FILE SENTINEL....
BYPASS lMAGE SENTINEL...

10
37
00

2. DATA IMAGES

35

24

00

------------------------------:0: IL
------------------~-----------DATA IMAGE. NUMBER

------------------------------OF WORUS DEFINED
--------.-------.-------------IMAGE LENGTH (IL).
-.-------------------------.--~Y

DATA IMAGES HAVE

~IT

35 SET EQUAL TO O.

THE REMAINDER OF

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

13
SECTION:

THIS WORD IS DEFINED ACCORDING TO THE TYPE OF DATA FILE
PRODUCED. E.G. FILES GENERATED FOR PRINTING USE THIS FIELD
FOR SPACING INCRE~ENTS, AND SOURCE ELEMENTS USE THIS FIELD
FOR CYCLE NUMBERS.
13.12.2.

FILE CONVENTIONS

FILES RESIDING ON MAGNETIC TAPE ARE RECORDED IN 224 WORD BLOCKS. IMAGES ARE
ALLOWED TO SPAN TWO CONSECUTIVE BLOCKS. FASTRAND FILES ARE RECORDED AS A CONTINUOUS
DATA SET. THE END-OFFILE SENTINEL CONTROL IMAGE TERMINATES FILE PROCESSING.
A SINGLE TAPE MARK IS USED TO SEPARATE FILES RESIDING ON MAGNETIC TAPE, AND TWO
CONSECUTIVE TAPE MARKS SPECIFY END OF RECORDING. MASS STORAGE FILES USE A SOFTWARE
DEFINED END-OF-FILE MARK FOR FILE OPERATIONS AT THE BLOCK LEVEL. THIS IS DEFINED AS
A BLOCK WHICH HAS AS ITS FIRST WORD THE FIELDATA SENTINEL '$QEOF$'.
THE BLOCK
BUFFERING PACKAGE INTERPRETS THIS SENTINEL AS IT WOULD A TAPE MARK.
LABEL IMAGES
THE FILE LABEL IMAGE IS THE INITIAL IMAGE OF AN SDF FORMATTED FILE PRECEDED BY ITS
FILE IMAGE CONTROL WORD. THE CONTROL WORD'S S FIELD MUST BE SET
OCTAL 10, AND CL
SET TO THE LABEL IMAGE LENGTH THE MINIMUM IMAGE CONSISTS OF THE FOLLOWING

=

WORD 1
WORD 2-3

T
B
FILELABEL

WHERE T = THE TyPE OF FILE, AND IS LOCATED IN Sl (BITS 35-30) OF THE FIRST WORD. THE
T FIELD IS SET EQUAL TO THE FIELDATA CHARACTER .p, FOR THOSE FILES PRODUCED FOR
PRINTING, OR 'C' FOR CARD FILES OR 'T' FOR PAPER TAPE FILES. THE B FIELD IS USED TO
DENOTE BREAKPOINT NUMBERS OF A PRINT OR PUNCH FILE AND IS ~OCATED IN S6 (BITS 5-0) OF
WORD 1, AND SERVES AS AN EXTENSION TO THE FILE LABEL IMAGE. THE FILELABEL FIE~D IS
USED TO IDENTIFY THE FILE AND IS A 12 CHARACTER FIELD.

55
PAGE:

 ARE ARBITRARILY INCLUDED IN THE PRo.GRAM BEING
COLLECTED. USE OF THE SYSTEM RELDCATABLE LIBRARY TO. SATISFY EXTERNAL REFERENCES IS
AUTOMATICALLY IMPLIED; THE USE DF USER LIBRARIES IS UNDER CDNTROL OF A SOURCE
LANGUAGE COHTROL STATEMENT TO. THE COLLECTOR. ANY SPECIFIED USER LIBRARIES ARE ALWAYS
S~ARCHED BEFORE THE SYSTEM RELDCATABLE LIBRARy.
THE OUTPUTS DF THE COLLECTOR ARE AS FOLLDWS:
1.
2.
3.

AN ABSOLUTE o.R RELDCATABLE ELEMENT
A SOURCE LANGUAGE Co.NTRDL ELEMENT AS DISCUSSED ABo.VE.
LISTING INFORMATIDN

THE PRIMARY DUTPUT OF THE CDLLECTo.R IS THE RELOCATABLE OR ABSOLUTE ELEMENT WHICH
RESULTS FROM THE COLLECTING AND LINKING DF THE VARIOUS RELOCATABLE ELEMENTS. TH[S
ELEMENT IS GIVEN A NAME AND PLACED WITHIN A PRDGRAM FILE Fo.R SUBSEQUENT USE, Bo.TH
TilE ELEMENT NAME AND THE FILE IN WHICH THE ELEMENT IS PLACED MAY BE DICTATED BY THE

1
PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC·

a

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

2

PAGE:

c
USER.
NORMALLY, THE COLLECTOR INCLUDES WITHIN AN ABSOLUTE ELEMENT, A SET OF TABLES FOR
USE BY THE DIAGNOSTIC SYSTEM. AS DISCUSSED LATER, THIS OUTPUT CAN BE SUPPRESSED BY
THE USER.
FOR ANY ERROR CONDITION ENCOUNTERED, THE COLLECTOR PRODUCES AN ERROR MESSAGE WHICH
!S PLACED IN TIlE PRINr FILi ASSIGNIID TO mE. RUN (PRINT$).

THE ENSUING SECTIONS DESCRIBE IN DETAIL THE EXECUTIVE CONTROL STATEMENTS INvOLVING
THE COLLECTOR, THE SOURCE LANGUAGE CONTROL STATEMENTS PROCESSED BY THE COLLECTOR, THE
OPERATIONAL CHARACTERISTICS OF IT, AND PROCEDURES FOR SEGMENTING A PROGRAM.
15.1.2,

EXECUTIVE CONTROL STATEMENTS

15,1.2,1.

THE .QMAP CONTROL STATEMENT

THE r.JMAP EXECUTIVE CONTROL STATEMENT IS USED FOR SPECIFYING THAT THE COLLECTOR IS
TO BE USED TO COMBINE A SET OF RE~OCATABLE ELEMENTS INTO A SINGLE ABSOLUTE ELEMENT OR
INTO A SINGLE RELOCATABLE ELEMENT, THE IOlMAP STATEMENT HAS THE SAME FORMAT AS OTHER
PKOCESSOR STATEMENTS AND IS :
IOlMAP,(OPTIONS)

(SPEC1),(SPEC2),(SPEC3)

THE AVAILABLE OPTIONS ARE:
I

INITIAL INSERTION: INTRODUCE SOURCE LANGUAGE ELEMENT INTO
PROGRAM FILE FROM THE CONTROL STREAM~ (SPEC 1) IDENTIFIES
THIS ELEMENT. (SPEC3) IS NOT USED, IF NO SOURCE LANGUAGE
FOLLOWS, THE COLLECTOR ASSUMES: IN TPF$.
(SEE: COLLEcTOR CONTROL STATEMENTS>,

U

UPDATE: PRODUCE A NEW CYCLE OF THE SOURCE LANGUAGE
ELEMENT IDENTIFIED IN (SPEC1). IF CORRECTIONS FOLLOW,
THEY WILL BE INCLUDED IN THIS NEW CYCLE.
(SPEC3) IS NOT
USED.

L

PRODUCE A COMPLETE LISTING CONTAINING A SUMMARY OF THE
CORE SPACE USED BY THE PROGRAM, THE SPACE ALLOCATED TO
EACH ELEMENT, THE PROGRAM ADDRESS OF A(L
DEFINITIONS, AND THE EXTERNAL REFERENCES OF EACH ELEMENT,

N

PRODUCE NO LISTING, DIAGNOSTIC MESSAGES ARE ALWAYS
PRINTED~ IF NEITHER L NOR N ARE CODED, ONLY SUMMARY
INFORMATION WILL BE PRINTED.

X

IF ANY ERRORS ARE DETECTED, INHIBIT EXECUTION OF THE
REMAINDER OF THE PROGRAM (EXCEPT A gPMD STATEMENT, IF ONE
FOLLOWS). NORMAL ACTION, WITHOUT THE X
OPTION, IS TO ACCEPT THE RESULTS OF THE COLLECTION SO LONG
AS AN ABSOLUTE OUTPUT ELEMENT IS PRODUCED.

Z

INHIBIT GENERATION OF THE DIAGNOSTIC INFORMATION NORMALLY
PROVIDED TO THE DIAGNOSTIC SYSTEM.

R

PRODUCE A RELOCATABLE ELEMENT RATHER THAN AN ABSOLUTE
ELEMENT. (ENTRY POINTS IN THE RELOCATABLE ELEMENTS BEING
COMdINED IN AN R-OPTION COLLECTION, WHICH ARE STILL TO BE
DEFINED AS ENTRY POINTS IN THE SINGLE HELOCATABLE OUTPUT
ELE~ENT, MUST BE NAMED ON THE COLLECTOR DEF STATEMENT. THE
UEF STATEMENT IS EXPLAINED BELOW.>

E

ALLOW PROGRAM TO EXCEED ADDRESS 177777 (DECIMAL 65 K).

c

.-~----

1-"

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SYSTEM
REFERENCE

15
SECTION:

(~

D

GIVE A DIAGNOSTIC MESSAGE FOR ALL POSSIBLE ADDRESS FIELDS
OVER 65K.

 IS 'FILE1. ELT1/VERS1(CYC LE),. IT NORMALLy IDENTIFIES THE SyMBOLIC INPUT
ELEMENT. WHEN THE I OPTION IS USED, IT IDENTIFIES THE SYMBOLIC OUTPUT ELEMENT,
 IS .F1LE2.ELT2/VERS2', IT IDENTIFIES THE ABSOLUTE OUTPUT ELEMENT OF THE
COLLECTION. (IF THE R OPTION IS ON, THIS IS INSTEAD A RELOCATABLE ELEMENT,)
 IS 'FILE3.ELT3/VERS3', IT IDENTIFIES THE (OPTIONAL) SYMBOLIC OUTPUT
ELEMENT WHEN THE I OR U OPTION IS NOT USED. IF CORRECTIONS FOLLOW, THEY WILL BE
INCLUDED IN THE NEW ELEMENT, THE CYCLE NUMBEf~ OF THE NEW ELEMENT IS SET TO ZERO,
STANDARD SYSTEM DROPOUT RULES APPLy TO THESE 3 SPECIFICATION SUBFIELDS. A SINGLE
NAME (WITH NO PERIOD) IN ANY OF THESE SUBFIELDS IS ASSUMED T~ BE AN ELEMENT IN THE
RUI~'S TEMPORAkY PROGRAM FILE (TPF$).
A SINGLE NAME WITH A LEADING PERIOD IN (SPEC2>
OK  IS ASSUMED TO BE AN ELEMENT IN THE FILE GIVEN IN THE  PRECEDING, A
SINGLE NAME WITH A LEADING PERIOD IN (SPEC1> IS ASSUMED TO BE IN TPF$,
HERE ARE SOME EXAMPLES OF THE
fiilMAP

~MAP

STATEMENT:

SYMIN/C,BACKUP.ABSOUT
(ELEMENT SYMIN, VERSION C, LATEST CYCLE, FROM
TPF$, IS USED TO DIRECT THE COLLECTION OF
ELEMENT ABSOUT WRITTEN INTO FILE BACKUP,
IF ANY CORRECTIONS FOLLOW, THEY WILL BE USED
BUT NOT SAVED, BECAUSE NO OUTPUT SYMBOLIC
ELEMENT IS PRODUCED.)

QMAP,I

BACKUP.SYMOUT,.ABSOUT
(THE STATEMENTS FOLLOWING THE ~MAP STATEMENT
ARE USED TO DIRECT THE COLLECTION AND ARE
OUTPUT AS ELEMENT SYMOUT IN FILE BACKUP, THE
ABSOLUTE OUTPUT ELEMENT IS ALSO PUT INTO FILE
BACKUP. )

r.JMAP,U

SYMIN(3),ABSOUT/REVISED
(CYCLE 4 OF ELEMENT SYMIN IN TPF$ IS PRODUCED,
SAVING ANY CORRECTIONS THAT FOLLOW THE ~MAP
STATEMENT. ABSOLUTE OUTPUT ELEMENT ABSOUT,
VERSION REVISED, IS ALSO PUT INTO TPF$.)

fOlMAP, I
(THIS IS A SPECIAL CASE WHERE THE SYSTEM PICKS
OUT ITS OWN NAME FOR THE SYMBOLIC AND ABSOLUTE
OUTPUT ELEMENTS. BOTH INTERNAL TABLE ENTRIES,
AND THE PRINTEu OUTPUT PROQUCED BY A QPRT,T
STATEMENT FOLLOWING THE COLLECTION, WILL
LOOK AS IF THE QMAP STATEMENT HAD CONTAINED:
~MAP,I
TPF$.NAME$,.NAME$ .>
r.lMAP

fiilMAP,lRXLED

(THIS IS TREATED AS IF IT HAS AN I OPTION,
WHICH IS THE SAME AS THE SPECIAL CASE ABOVE.)
A,A
(THE STATEMENTS FOLLOWING THE r.JMAP STATEMENT

"

3
PAGE:

UNIVAC 110a OPERATING

UP-4144
Rev. 1

EXEC, B

SYSTEM

PROGRAMMERSR,E;,F:ERENCE

, ,15.
SECTION:

4
'

PAGE:

ARE USED TO DIRECT THE COLLECTION AND ARE, .
OUTPUT TO TPF$ AS SYMBOLIC ELEMENT A. THE
RESULT OF THE COLLECTION IS OUTPUT TO TPES
AS RELOCATABLE ELEMENT A. IF ERRORS OF ANY
KIND ARE ENCOUNTERED, INHIBIT CONTINUATION OF
PROGRAM. PRODUCE A FULL LISTING. ALLOW DBANK
TO EXCEED 65K. PRINT DIAGNOSTICS FOR ADDRESS
FIELDS OVER 65K.> .
r.lMAP

OLDFILENAME. OLDELEMENT , A, NEWF I LENAr>1E. NEW ELEMENT
(THE SYMBOLIC LIST OF COLLECTOR COMMANDS
CONTA1NED IN OLDELEMENT, AS AMENDED BY ANY
CORRECTIONS FOLLOWING THIS fOIMAP STATEMENT, IS
USED TO DIRECT THE COLLECTION, AND IS OUTPUT
INTO A NEW FILE WITH A NEW ELEMENT NAME.
THE ABSOLUTE OUTPUT ELEMENT, A, GOES TO TPF$.>

THESE 3 EXA~pLES FOLLOW ONE ANOTHER IN SEQUENCE, AND SHOW SOME ACTUAL COLLECTOR
CONTROL STATEMENTS (WHICH ARE EXPLAINED LATER ON):
r.lMAP,I
LIB
SEG
IN
SEG
IN

F8.MAPSYM,.MYPROGRAM
F8.
CONTROL
ELEMENT!
OVERLAY5,(CONTROL)

r.lMAP,U
LIB

F8.MAPSYM,.MYPROGRAM
FlO.

F9.

-3,3

IN
SEG
IN

ELEMENTO
OVERLAY4,(CONTROL)
F7.

-5

SEG
IN
CLASS
NOT

fOlP1AP; I

LIB
LIB
SEG
IN
SE:G
IN
SEG
IN
SEG
IN

CLASS
NOT

HIGHCORE, (OVERLAY4,OVE'RLAY5>
DATAELEMENT
REVISED
ELEMENTl
(AFTER THIS SECOND r.lMAP, ELEMENT MAPSYM WILL
SAVE THE CORRECTIONS, BECAUSE AN UPDATE OF
CYCLE WAS SPECIFIED. THE ABSOLUTE ELEMENT
MYPROGRAM PUT INTO FILE Fa BY THE FIRST QMAP
WILL BE DELETED AND REPLACED BY THE DIFFERENT
MYPROGRAM PRODUCED BY THIS SECOND ~MAP.)
F8.MAPSYM,.MYPROGRAM
FlO.

FB.
CONTROL
ELEMENTO
OVERLAy~,(CONTROL)

F7.

OVERLAY5,(CONTROL)
F9.
'
HIGHCORE,(OVERLAY4,OVEI\LAY5)
DATAELEMENT
REVISED
ELEMENTl
(ELEMENT MYPROGRAM COMES OUT EXACTLY THE SAME
HERE AS THE PRECEDING MYPROGRAM, WHICH IT
REPLACES IN FILE Fa. ELEMENT MAPSYM, SET HERE
TO INTITAL CYCLE 0, ALSO COMES OUT THE SAME

c

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

.15
SECTION:

AS THE UPDATE CYCLE 1 OF MAPSYM, WHICH IT
REPLACES IN FILE Fe.)
IF A PROGRAM FILE NAMED ON A QMAP STATEMENT (OR ON A ,LIB, OR 'IN, COLLECTOR
C0NTROL STATEMENT) HAS NOT BEEN ASSIGNED, BUT HAS BEEN PREVIOUSLY CATALOGED, IT WILL
Bl ASSIGNEO AUTOMATICALLY DURING THE COLLECTION. AT THE END OF THE COLLECTION, IT
WILL BE RETURNED TO ITS ORIGINAL STATE WITH A QFREE (PLUS X, R, AND/OR A OPTION).
THE METHOD USED TO QASG AND QFREE THESE FILES FROM WITHIN THE COLLECTOR IS THE SAME
AS THAT AVAILA~LE TO EVERY USER PROGRAM VIA THE ER CSF$ EXECUTIVE REQUEST (DOCUMENTED
EARLIER IN THE PRM).
15.1.2.2.

THE

~xQr

CONTROL STATEMENT

FOH EXECUTING AN ABSOLUTE PROGRAM CREATED BY THE COLLECTOR, THE FOLLOWING CONTROL
STATEMENT IS USED:
~XQT,OPTIONS

(

FILE1.ELTI/VERSI

AI~Y OPTIONS SPECIFIED ARE AVAILABLE TO THE USER'S PROGRAM BY THE OPT$ EXECUTIVE
REQUEST WHENEVER IT IS INITIATED. THE FIELD 'FILEl.ELTI/VERSl' SPECIFIES THE
AdSOLUTE PROGRAM TO EXECUTE. THE SUB-FIELD 'FILE1' IS THE NAME OF THE FILE,
'ELTI/VERSl' IDENTIFIES THE ELEMENT (AND VERSION, IF ANY). THIS FIELD IS THE
COUNTERPART OF FI(E2.ELT2/VERS2' IN THE QMAP CONTROL STATEMENT. IF NO ELEMENT IS
SPECIFIED, THE LAST ABSOLUTE ELEMENT PLACED IN THE FILE GIVEN (TEMPORARY IF NO FILE
SPECIFIED) WILL BE LOADED AND EXECUTED. IN THE ABSENCE OF AN ABSOLUTE ELEMENT, ALL
OF THE RELOCATABLE ELEMENTS IN THE FILE ARE BOTH COLLECTED AND ExECUTED (A
RELOCATABLE ELEMENT MAY NOT BE EXPLICITELY NAMED ON AN ~XGT STATEMENT, HOWEVER).

EXAMPLES OF THE QXQT STATEMENT IN TYPICAL RUN STREAMS:
COMPILATIONS OR ASSEMBLIES TO PRODUCE
RELOCATABLE ELEMENTS IN THE RUN,S TEMPORARY
PROGRAM FILE, TPF$.
GENERATE AN ABSOLUTE ELEMENT CONSISTING OF ALL
THE RELOCATABLE ELEMENTS IN THE TEMPORARY FILE.
EXECUTE THE ABSOLUTE ELEMENT GENERATED ABOVE.

1.
fiIJMAP

QX(,)J
2.
ralMAP

~XQT

15.1.3.
15.1.3.1.

COMPILATIONS OR ASSEMBLIES PRODUCING
RELOCATABLE ELEMENTS IN THE USER SPECIFIED
FILE, FILEA.
FILEA.SYMHOLIC,FILEA.XYZ
GENERATE THE ABSOLUTE ELEMENT XYZ IN FILEA
AS DIRECTED BY THE SOURCE ELEMENT
FILEA.SYMBOLIC. '
FILEA.XYZ
EXECUTE THE ABSOLUTE ELEMENT GENERATED ABOVE.

COLLECTOR CONTROL STATEMENTS
GENERAL

IN AUDITION TO THE INFORMATION SPECIFIED IN THE QMAP CONTROL STATEMENT, A SET OF
SOURCE LANGUAGE CONTROL STATEMENTS CAN BE PROCESSED BY THE CbLLECTOR TO PROVIDE THE
USER THE CAPAbILITY OF CONTROLLING THE CONSTRUCTION OF EVEN THE MOST COMPLEX
PROGRAMS. THE USER CAN ENTER THESE CONTROL STATEMENTS VIA HIS CONTROL INPUT STREAM
FOR EACH COLLECTION, OR HE CAN CREATE WITHIN A PROGRAM FILE A SOURCE LANGUAGE CONTROL
ELEMENT CONTAINING THE STATEMENTS. THIS ELEMENT CAN BE UPDATED BY ENTERING THE
CORRECTIONS VIA THE CONTROL INPUT STREAM.

(~.

THE COhTROL STATEMENTS RECOGNIZED BY THE COLLECTOR INCLUDE THE FOLLOWING:
IN

INCLUDE SPECIFIC ELEMENTS IN THE COLLECTION.

5
PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

6
PAGE:

'" ,
C
,

NOT

EXCLUDE SPECIFIC ELEMENTS FROM THE COLLECTION.

LIB

SPECIFY LIBRARIES TO BE SEARCHED.

SEG

DIRECT THE SEGMENTATION OF A PROGRAM.

DSEG

SPECIFY A DYNAMIC SEGMENT.

RSEG

SPECIFY A RELOCATABLE SEGMENT.

DEF

SPECIFY EXTERNAL DEFINITIONS TO BE RETAINED IN THE
ABSOLuTE OR RELOCATABLE ELEMENT.

REF

SPECIFY THE EXTERNAL REFERENCES TO BE RETAINED IN THE
ABSOLUTE OR RELOCATABLE ELEMENT.

ENT

SPECIFY THE STARTING ADDRESS OF A PROGRAM.

EQU

GIVE VALUES TO UNDEFINED SYMBOLS AT THE TIME OF THE
COLLECTION.

CLASS

SPECIFY A MASK TO USE iN SELECTING ELEMENTS FOR
COLLECTION.

COR

SPECIFY THAT CORRECTIONS ARE TO BE MADE TO AN ELEMENT.

SNAP

DIRECT POSITIONING OF SNAPSHOT DUMPS.

END

END OF SOURCE LANGUAGE STATEMENTS TO BE PROCESSED.

THEIN CONTROL STATEMENT ALLOWS THE USER TO INCLUDE ANy OR ALL ELEMENTS FR'OM ANY
NUMBER OF FILES IN HIS COLLECTION AND SPECIFICALLY IN THE SEGMENT NAMED BY THE
PRECEDING SEG STATEMENT. THE FORMAT OF THIS STATEMENT IS THE FOLLOWING:
IN

FILEl.ELT1/VER1,FILE2.ELT2, •••

THE FIELDS 'FILE1.ELTl/VERl,' ETC., IDENTIFY SPECIFIC ELEMENTS TO BE INCLUDED IN
THE COLLECTION. BY SPECIFYING ONLY 'FILEl.', THE USER CAN SPECIFY THE INCLUSION OF
ALL ELEMENTS IN A PROGRAM FILE.
NORMALLY ALL THE RELOCATABLE ELEMENTS IN TrlE RUN'S TEMPORARY PROGRAM FILE, TPF$,
AKE INCLUDED IN EVERY COLLECTION. IF THE EXTERNAL DEFINITIONS OF THE TEMPORARY FILE
HAVE BEEN COLLECTED WITH A gPREP CONTROL STATEMENT, THE ELEMENTS ARE INCLUDED
SELECTIVELY. IN THIS CASE TPFS. IS THE FIRST PROGRAM FILE EXAMINED FOR ELEMENT
INCLUSION. ELEMENTS THAT ARE NOT ASSOCIATED WITH FILES MAY BE INCLUDED FROM TPF$. OR
ANY PROGRAM FILE NAMED IN LIB STATEMENTS.
AN ELEMENT NAME MAY APPEAR ON ONLY ONE IN STATEMENT AND ONLY ONCE IN A COLLECTION.
IT IS Ir,1PORTANT, FOR FORTRAN PROGRAMMEHS ESPECIALLY, TO NOTE THAT NO COMMON BLOCK
NAME (LABELLED, OK NAMED COMMON)' IN THE COLLECTION MAY BE IDENTICAL TO ANY ELEMENT
NAI;/\E. THROUGHOUT MOST OF THE COLLECTION COMMON BLOCKS AND ELEMENTS ARE HANDLED IN A VERY
SIMILAR MANNER, AND THEIR NAMES MUST DISTINGUISH THEM FROM ONE ANOTHER.
THE FOLLOWI~G ARE EXAMPLES ON THE USE OF THE IN STATEMENT:
IN

FILEA.,FILEB.
(ALL RELOCATABLE ELEMENTS IN FILEA AND FILEB
ARE INCLUDED.)

IN

~ILEB.bB,.CC,DD

(ELEMENTS BB AND CC FROM FILES, AND ELEMENT DO,

c

,

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

(
WHOSE FILE ISN.T INDICATED, ARE INCLUDED IN
THE COLLECTION,)
15.1.3.3.

THE NOT STATEMENT

THE NOT CONTROL STATEMENT IS ESSENTIALLY THE INVERSE OF THE IN STATEMENT. IT
ALLOwS THE USER TO STATE EXPLICITLY WHICH ELEMENTS WITHIN FILES ARE NOT TO 8E
INCLUDED IN A COLLECTION. THE FORMAT OF THIS STATEMENT IS AS FOLLOWS:
NOT

FILE1.ELTI/VER1,FILE2.ELT2/VER2, •••

WhERE THE SUCCESSIVE FIELDS INDICATE ELEMENTS NOT TO 8E INCLUDED. IF THE VERSION
NAME OR FILE NAME IS OMITTED, ALL ELEMENTS WITH THE SPECIFIED NAME ARE BYPASSED.
THE FOLLOWING ARE EXAMPLES ON THE USE OF THE NOT STATEMENT:
1.

fDIMAP, I A, A
NOT AA,BB
(ALL RELOCATABLE ELEMENTS IN THE TEMPORARY FILE
EXCEPT AA AND BB ARE INCLUDED IN THE
COLLECTION. )

2.

~MAP'I

IN
NOT

(

A,A
FILEA.
FILEA,AA,.SB
(ALL RELOCATABLE ELEMENTS IN FILEA EXCEPT
AA AND B8 ARE INCLUDED.)

r.JMAP,I A,A
IN
FILEA.,FILEB.
NOT
FILEA.AA,.B8,FILEB.CC,.DD
(ALL RELOCATABLE ELEMENTS FROM FILEA EXCEPT
AA AND 88, AND ALL RELOCATABLE ELEMENTS FROM
FILES EXCEPT CC AND DD ARE INCLUDED,)
15,1.:3.4.

THE LIB STATEMENT

THE LIB CONTROL STATEMENT ALLOWS THE USER TO SPECIFY LIBRARIES TO BE SEARCHED BY
TilE COLLECTOR FOR THE PURPOSE OF SATISFYING EXTERNAL REFERENCES AND/OR OF FINDING
ELEMENTS SPECIFIED WITHOUT FILE NAMES. THE FORMAT OF THE LIB STATEMENT IS:
LIS

FILE1,FILE2, •••

THE NAMES OF FILES TO BE TREATED AS LIBRARIES ARE SPECIFIED IN SUCCESIVE FIELDS.
THESE LIBRARIES ARE SEARCHED IN THE ORDER IN WHICH THEY ARE GIVEN AND BEFORE THE
SYSTEM LIBRARY. FILES MAY BE SPECIFIED TO BE SEARCHED MORE THAN ONCE BY NAMING IT
MuRE THAN ONCE IN A LIB STATEMENT. SEVERAL LIB STATEMENTS MAY BE SPECIFIED AND THEIR
EFFECT IS CUMULATIVE. FILES ARE NOT SEARCHED FOR EXTERNAL DEFINITIONS IF THE FILE
HAS NOT BEEN PREPARED BY THE PREP OPERATION.
TYPICAL LIB CONTROL STATEMENTS ARE AS FOLLOWS:
LIl3 USEfU

LIB

15.1.3.5.

(FILE USERI IS SEARCHED BEFORE THE SYSTEM
LIBRARY.)

USER1,USER2
(FILE USERI AND THEN FILE USER2 ARE SEARCHED
BEFORE THE SYSTEM LIBRARY.)
THE SEG STATEMENT

THE SEG CONTROL STATEMENT IS USED TO INFORM THE COLLECTOR OF THE BEGINNING OF A
NEW SEGMENT IN THOSE PROGRAMS REQUIRING SEGMENTATION, THE FORMAT IS;
SEG

NAME1, NAME2

7
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

OR

SEG

~AME1,

SYSTEM

15
•

SECTION:

8
PAGE:

(NAME2,NAME3 •••• )

THE FIELD 'NAME1' IS THE NAME OF THE SEGMENT AND MUST BE SPECIFIED. THE FIELD
GIVES THE NAMES OF OTHER SEGMENTS TO WHICH THE SEGMENT 'NAME1'IS BEING
RELATED. A SEGMENT CAN BE SPECIFIED FOR AUTOMATIC (INDIRECT) LOADING WHEN REFERENCED
BY SUFFIXING .AN ASTERISK TO JNAME1': 'NAME1*'.
'~AME2',ETC.

IF THE FIELD 'NAME2' IS VOID, THE SEGMENT BEING SPECIFIED IS ORIGINATED
IMMEDIATELY FOLLOWING THE SEGMENT DEFINED BY THE PRECEDING SEG STATEMENT. THE FIELD
'NAME2' (NOT INCLUDED IN PAREiHHESES) SPECIFIES THAT THE SEGMENT BEING DEFINED IS TO
ORIGINATE AT THE SAME LOCATION AS DOES SEGMENT 'NAME2'. IF THE RIGHT HAND FIELD
CONTAINS ONE OR MORE SEGMENT NAMES ENCLOSED IN PARENTHESES, THE SEGMENT 'NAME1' IS
STARTED FOLLOWING THE HIGHEST ADDRESS OCCUPIED BY ANY OF THESE SEGMENTS.
EACH SEGMENT MAY HAVE TWO PROGRAM AREAS (BANKS) NAMELY, THE INSTRUCTION AREA AND
THE DATA AREA (ALSO REFERHED TO AS IBANK AND OBANK). THEREFORE, SEGMENTS SPECIFIED
TO FOLLOW THE HIGHEST ADDRESS OF SEVERAL SEGMENTS MAY HAVE ITS INSTRUCTION AREA
FOLLOW THE INSTRUCTION AREA OF ONE SEGMENT AND ITS DATA AREA FOLLOW THE DATA AREA OF
A DIFFERENT SEGMENT.
THE FIRST SEGMENT NAMED IN THE SOURCE INPUT IS CALLED THE MAIN SEGMENT AND IS NOT
OVERLAYED bY OTHER SEGMENTS.
SEGMENTS MAY BE LOADED AND EXECUTED INDEPENDENTLY OF ONE ANOTHER. HOWEVER, THE
PLACEMENT OF ELEMENTS COMMON TO SEVERAL SEGMENTS MAY DICTATE THAT SOME SEGMENTS MUST
BE IN MEMORY WHEN OTHERS ARE BEING EXECUTED. ELEMENTS ARE NOT NECESSARILY ATTACHED
TO THE MAIN SEGMENT WHEN THEY ARE REFERENCED IN MORE THAN ONE SEGMENT BUT NOT
EXPLICITLY INCLUDED IN ANY SEGMENT. EACH SEGMENT HAS A PATH LEADING TO THE MAIN
SEGMENT. ELEMENTS REFERENCED BY TWO (OR MORE) SEGMENTS ARE ATTACHED TO THE SEGMENT
THAT IS IN THE PATH OF ALL THE REFERENCING SEGMENTS. NAMED COMMON BLOCKS ARE
LIKEWISE IN THE PATH OF ALL SEGMENTS REFERENCING THE BLOCK.

/'~
~ ,

~

THE PAT~ TO THE MAIN SEGMENT FOLLOWS THE PATH OF THE FIRST SEGMENT IN ITS PATH.
THE FIRST SEGMENT IN ITS PATH IS DETERMINED BY ITS RELATION SPECIFICATIONS.
OR:

SEG

A, (9)

SEG
SEG

B
A

SEG

A,B

SEGMENT A'S PATH IS IDENTICAL TO SEGMENT B'S.

SEG

A, (6,C.O)

THE FIRST SEGMENT IN A'S PATH IS THE SEGMENT
COMMON TO THE PATHS OF SEGMENTS B,C AND D.

SEGMENT A'S PATH STARTS WITH SEGMENT BAND
FOLLOWS B'S PATH TO THE MAIN SEGMENT.

AT LEAST ONE IN STATEMtNT MUST FOLLOW THE SEG STATEMENT.
ALL THE ELEMENTS SPECIFIED ON IN STATEMENTS AFTER THIS SEG STATEMENT AND BEFORE
THE FOLLOWING SEG STATEMENT ARE A PART OF THIS SEGMENT. OTHER ELEMENTS REFERENCED
ARE INCLUDED IN THIS SEGMENT OR IN A SEGMENT IN ITS PATH TO THE MAIN SEGMENT.
15.1.3.6.

THE OSEG STATEMENT

THE USEG CONTROL STATEMENT IS USED TO INFO~M THE COLLECTOR OF THE BEGINNING OF A
SEGMENT WITH SPEC~AL CHARACTERISTICS. THIS TYPE OF SEGMENT IS CALLED A DYNAMIC
SEGMENT. THE CORE AREA OF THE SEGMENT IN EXC~SS OF NORMAL SEGMENTS MAY BE
TEMPORARILY RELEASED TO THE EXECUTIVE ~YSTEM #ITH A REFERENCE TO DREL$. THE AREA MAY
BE RELEASED AU10MATICALLY WHEN A DYNAMIC SEGMENT IS OVERLAYED. THE AREA IS RELEASED
ONLY ~HEN IT IS AT THE END OF THE PROGRAM'S AREA. SINCE THE EXECUTIVE SYSTEM MAY
NEED TO MOVE OTHER PROGRAMS TO LOAD A DYNAMIC SEGMENT, DISCRETION SHOULD BE USED IN
DESIGNATING WHAT SEGMENTS ARE DYNAMIC SEGMENTS.
THE DSEG STATEMENT HAS THE SAME FORMAT AS THE SEG STATEMENT.

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

15.1.3.7.

SYSTEM

15
SECTION:

THE RSEG STATEMENT

THE KSEG STATEMENT IS USED TO INFORM THE COLLECTOR OF THE BEGINNING OF A SEGMENT
TriAT IS RELOCATABLE. THE SEGMENT CONTAINS OI'lLY AN INSTRUCTION AREA. RELOCATION OF
AuDKESS FIELOS IS ACCOMPLISHED BY ADDING THE BEGINNING ADDRESS OF THE SEGMENT TO THE
RIGHT OR LEFT hALF OF THE WORDS TO BE RELOCATED. RELoCATABLE SEGMENTS MAY NOT BE
DESIGNATED FOR INDIRECT LOADING. THE ELEMENTS TO MAKE UP A RSEG SEGMENT MUST BE
EXPLICITLY NAMED ON IN STATEMENTS FOLLOWING THE RSEG STATEMENT.
15.1.3.8.

THE DEF STATEMENT

THE UEF CONTROL STATEMENT IS USED TO LIST THOSE EXTERNAL DEFINITIONS TO BE
RETAINED bY THE RESULTlNG ABSOLUTE OR RELOCATASLE ELEMENT. FOR ABSOLUTE ELEMENTS,
THE PROGRAM MAY BE ENTERED BY INTERPRETIVE CODE (OUTPUT OF THE CONVERSATIONAL
PROCESSORS) AT ANY OF THE EXTERNAL DEFINITIONS LISTED, THE ADDRESS OF THIS TABLE IS
D~FINED BY THE COLLECTOR TO BE ENTRY$,
IT IS ADDRESSABLE BY THE PROGRAM USING THE
TAG ENTRY$. ALSO, DEF AND/OR REF STATEMENTS CAUSE THE COLLECTOR TO BUILD A TABLE
DEFINING THE LABELLED COMMON BLOCKS IN THE PROGRAM, THIS TABLE IS ADDRESSABLE BY THE
COLLECTOR OEFINED TAG COMMN$. THE FORMAT OF THE STATEMENT IS:
DEF

DEF1,DEF2,DEF3",.

WHERE THE SUCCESSIVE 'DEF1. FIELDS ARE THE NAMES OF EXTERNAL DEFINITIONS TO BE
RETAINED. AN EXAMPLE OF THIS STATEMENT IS AS FOLLOWS:
DEF SIN,COS,SORT
(THE LISTED EXTERNAL DEFINITIONS ARE RETAINED
BY THE RESULTING ELEMENT,)
(

15.1.3.9.

THE REF STATEMENT

THE REF CONTROL STATEMENT IS USED TO LIST THOSE EXTERNAL REFERENCES TO BE RETAINED
BY THE RESULTING ABSOLUTE OR RELOCATABLE ELEMENT, FOR ABSOLUTE ELEMENTS, THE
EXTERNAL REFERENCES LISTED MAY BE LINKED TO INTERPRETIVE CODE BY THE INTERPRETER,
ThE TABLE IS ADDRESSABLE BY THE COLLECTOR DEFINED TAG XREF$. THE FORMAT OF THIS
STATEMENT IS AS FOLLOWS:
REF

REF1,REF2,REF3, •••

WHERE THE SUCCESSIVE 'REFI. FIELDS ARE THE NAMES OF THE EXTERNAL REFERENCES TO BE
RETAINEO. NO ATTEMPT IS MADE TO SATISFY THESE REFERENCES FROM EITHER USER LIBRARIES
OK THE SYSTEM LIBRARY. AN EXAMPLE OF THE REF STATEME~T IS:
REF SIN,COS,SQRT
(THE LISTED EXTERNAL REFERENCES ARE RETAINED BY
THE NEW ELErv1[NT)
15.1.3.10.

THE ENT STATEMENT

THE ENT CONTROL STATEMENT PROVIDES THE USER THE CAPABILITY OF OVERRIDING THE
SlARTING ADDRESS SPECIFIEO VIA THE END ASSEMBLER DIRECTIVE OR THE ENTRANCE TO A MAIN
PkOGRAM GENERATED By FORTRAN OR COBOL. THE FORMAT OF THIS STATEMENT IS :
ENf

NAME

WhERE NAME IS AN EXTERNALLY DEFINED SYMBOL. CONTRoL IS TRANSFERRED TO THE ABSOLUTE
LUCATION GENERATED FOR THIS SYMBOL WHENEVER THE PROGRAM IS SUBSEQUENTLY EXECUTED, IN
THE A~SENC[ OF AN ENT STATEMENT, THE STARTING ADDRESS WILL BE TAKEN TO BE A TRANSFER
AUURESS ENCOUN1EREO IN THE PROCESSING OF RELOCATABLE ELEMENTS. THE STARTING ADDRESS
~UST bE IN THE MAIN SEGMENT,
15.1.3.11.

THE EQU STATEMENT

THE EQU CONTROL STATEMENT MAY BE USED TO GIVE A VALUE TO AN UNDEFINED SYMBOL AT

9
PAGE:

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

THE TIME OF COLLECTION.
EQU

SYSTEM

15
SECTION:

10
PAGE:

THE FORMAT OF THIS STATEMENT IS:

NAMEI/VALUE1,NAME2/VALUE2, •••

WHERE ,NAME1' IS A SYMBOL TO BE DEFINED AND 'VALUE' IS THE VALUE TO BE GIVEN TO THE
SYMBOL. THE SAI14E IS TRUE FOR ,NAME2/VALUE2', ETC. THE SU8-FIELD ,VALUE' MAY BE AN
OCTAL OR DECIMAL INTEGER, A SYMBOL, OR A SYMBOL WiTH AN OFFSET. IF A SYMBOL IS USED,
IT MUST BE EXTERNALLY DEFINED BY ONE OF Tt1E ELEMENTS TO BE INCLUDED. EXAMPLES OF THE
USE OF THE EGU STATEMENT ARE AS FOLLOwS:
1.
2.
3.

EQU JOE/0200
(EXTERNAL REFERENCE JOE IS DEFINED TO BE 0200.)
EQU AL/SAM+ln
(EXTERNAL REFERENCE AL IS DEFINED TO BE SAM+I0;
SAM MUST BE EXTERNALLY DEFINED).
EQU JOE/0200, AL/SAM+I0
(SAME AS 1 AND 2)

15.1.3.12.

THE CLASS STATEMENT

THE CLASS STATEM.ENT MAY BE USED TO SPECIFY THE RELOCATABLE ELEMENT TO BE INCLUDED
IN THE COLLECTION WHEN OTHERWISE MORE THAN ONE ELEMENT COULD QUALIFY. THERE ARE TWO
CONDITIONS WHERE MORE THAN ONE ELEMENT MAY QUALIFY:
1.
2.

THE VERSION IS NOT SPECIFIED ON AN IN STATEMENT AND MORE
THAN ONE RELOCATABLE ELEMENT HAS THAT SAME NAME.
MORE THAN ONE RELOCATABLE ELEMENT DEFINES AN EXTERNAL
REFERENCE AND NONE OF THE ELEMENTS HAS BEEN EXPLICITLY
INCLUDED IN THE COLLECTION, OR ALL BUT ONE EXPLICITLY
EXCLUDED FROM THE COLLECTION.
THE FORMAT OF THE CLASS STATEMENT IS
CLASS

STRING

WHERE THE FIELD 'STRING' IS TWELVE CHARACTlRS INCLUDI~G THE SPECIAL CHARACTER
ASTERISK (*). THE ASTERISK DESIGNATES A CliARACTER POSITION THAT IS TO BE IGNORED
WHEN MAKING COMPAHISONS. ~HEN SEVERAL ELEMENTS· QUALIFY TO BE INCLUDED IN THE
COLLECTION, THE COLLECTOR COMPARES THIS STkING OF CHARACTERS WITH THE VERSIONS OF THE
QUALIFYING ELEMENTS. IF THE ELEMENT DOES NOT HAVE THE SAME CHARACTERS IN THE VERSION
AS THE CHARACTERS OF THE 'STRING' (FOR EACH CHARACTER POSITION), IT NO LONGER
QUA(IFIES FOR INCLUSION.
WHEN ONLY ONE ELEMENT REMAINS QUALIFIED AFTER THE COMPARISONS, THAT ELEMENT IS
WCLUDEU Ir~ THE COLLECTION. wHEN MORE THAI"! Of'JE ELEMENT STILL QUALIFIES, THE VERSIONS
OF THESE ELEMENTS ARE COMPARED TO THE CHAkACT~R STRING OF THE NEXT CLASS STATEMENT.
IF MORE THAN OI~E ELEMENT QUALIFIES AFTER THE CLASS STATEMENT PARAMETERS HAVE BEEN
EXHAUSTED A DIAGNOSTIC MESSAGE IS GIVEN. ~ONE OF THE IQUALIFING, ELEMENTS IS
INCLUDED IN THE PROGRAM SINCE A UNIQUE ELEMENT MAY BE FOUND IN THE NEXT LIBRARY
EXAMINED. IT SHOULD bE NOTED THAT DIFFEHENT ORDERS OF CLASS STATEMENTS MAY GIVE
DIFFERENT RE~ULTS.
ASSUME THAT THE ELEMENT NAMED SIZE IS NAMEO ON AN IN STATEMENT AND THE FOLLOWING
ELEMENTS ARE IN THE TEMPORARY LI~RARY:

H~LOCATABLE

SIZE/A2SrviALL
~rZE/l:)3LARGE

SIZE/D3SMALL
SIZE/D2LARGE
THE SOURCE LANGUAGE TO THE COLLECTOR IS:
loifviAP, I S , A
~EG
AA

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

15
SECTION:

(IN

CLASS
CLASS

SIZE
**LA******.*
D******.**.*

THE ELEMENT SIZE/D2LARGE IS INCLUDED IN THE COLLECTION.

THE ONE CLASS STATEMENT:

CLASS
WILL GIVE THE SAME RESULTS.
15.1.3.13.

THE COR STATEMENT

THE COR STATEMENT IS USED TO SPECIFY THAT RELOCATABLE CORRECTIONS ARE TO BE MADE
TO AN ELEMENT-INCLUDED IN THE COLLECTION. THE FORMAT OF THE COR STATEMENT IS:
COR

ELT

THE RELOCATABLE CORRECTIONS FOR THE ELEMENT 'ELT' FOLLOW THE COR STATEMENT.
RELOCATABLE CORRECTIONS MAY BE ONE OF THREE FORMATS:
ADDRESS,LCl F JAB H I U,LC2,ELT1
ADURESS,LCl DATAWORD
ADDRESS,LC1 OATA,LC2 DATA,LC2
THE FIELD 'ADDRESS, SPECIFIES THE RELATIVE ADDRESS UNDER LOCATION COUNTER 'LCI' TO
MAKE THE CORRECTION. .THE F,J,A,B,H AND I FIELDS CORRESPOND TO PORTIONS OF THE UNIVAC
1108 INSTRUCTION ~ORD. THE FIELDS 'U' AND 'DATA' MAY BE A SYMBOL, SYMBOL AND OFFSET
OR AN OCTAL O~ DECIMAL NUMBER. OCTAL NUMBERS REQUIRE A LEADING ZERO. THE FIELD
'DATAWORD' MUST BE NUMERIC. THE OPTIONAL FIELD 'LC2' INDICATES THAT THE ru' OR
'DATA' FIELDS ARE RELATIVE TO THE VALUE OF THE LOCATIoN COUNTER 'LC2'. THE OPTIONAL
FIELD 'ELT1' SPECIFIES THE ELEMENT IN WHICH 'LC2' BELONGS, IF IT IS OTHER THAN THE
ELEMENT BEING CORHECTEO. THE DATA FIELDS REPRESENT THE UPPER AND LOWER HALVES OF THE
WORD.
COR

STATEMEI~TS

15.1.3.14.

ARE BYPASSED IN AN R-OPTION COLLECTION.

THE SNAP STATEMENT

THE SNAP CONTROL STATEMENT SPECIFIES ELEMENTS IN WHICH SNAPSHOT DUMPS ARE TO BE
TAKEN. THE FORMAT OF THE STATEMENT IS:
Sf~AP

THE

S,~AP

ELT

FI~LD

'ELT' IS AN ELEMENT INCLUDED IN THE COLLECTION.
STATE.i"ENT GIVE THE PARAMETERS FOR THE SNAPSHOT DUMP.

ADURESS,LCI

ADDRESS

LENGTH,R

STATEMENTS FOLLOWING THE
THE FORMAT IS:

TIMES, FREQUENCY

THE FIELD 'ADDRESS,LC1' SPECIFIES THE ADDRESS OF THE INSTRUCTION TO BE REPLACED WITH
A DUMP REQUEST. THE FIELD 'ADDRESS' GIVES THE ADDRESS TO START THE DUMP. THE FIELD
MAY BE 'U,LC2,ELT1' OR SYI"80L AND OFFSET AS IN THE COR STATEMENT PARAMETERS. THE
FIELD tLENGTH' SPECIFIES THE LENGTH OF THE MEMORY AREA TO DUMP. THE FIELD 'R' IS
USED TO INDICATE WHICH OF THE REGISTERS IS TO BE PRIN'TED ACCORDING TO THE VALUES:
R=

O-NO REGISTERS
l-R REGISTERS
2-A REGISTERS
3-A AND R REGISTERS
I+-X REGISTERS
5~X AND R REGISTERS
6-X AND A REGISTERS
7-X, A AND R REGISTERS

11
PAGE:

.-~-~---

-.----------~

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC' B

SYSTEM

PROGRAMMERS REFERENCE

l~

12

Sirci'iON: ,'.'

PAGE:

rf"\
\,
'
~.

THE 'TIMES' FIELD SPECIFIES THE NUMBER OF TIMES THE SNAPSHOT IS TO BE TAKEN, IF
OrvtITTED, THE VALUE IS 100. THE FIELD 'FREQUENCY' SPECIFIES AT WHAT INTERVALS THE
DUMP IS TO BE TAKEN. THE VALUE THREE SPECIFIES THE DUMP TO BE TAKEN EVERY THIRD
REFERENCEIFIVE EVERY FIFTH REFERENCE,ETC. THE VALUE OF ONE IS ASSUMED IF THE FIELD IS
OMITTED,
AT MOST SIXTEEN SNAPSHOT PARAMETER STATEMENTS MAY BE INCLUDED IN ONE COLLECTION.
WHAT ACTUALLY HAPPENS WITH A SNAP SHOT DUMp REQUEST IS TI-1AT AN ,SLJ SNAP$$'
INSTRUCTION IS INSERTED AT THE LOCATION AT WHICH THE SNAP IS CALLED. SNAP$$ IS AN
ENTRY POINT IN ELEMENT SNAP$. THE REPLACED INSTRUCTION WORD IS SAVED IN A TABLE IN
ELEMENT SNAP$. AFTER THE DUMP IS TAKEN, THE SAVED INSTRUCTION IS EXECUTED FROM
WITHIN SNAP$ AS IF IT HADNOT BEEN MOVED. IF THE SAVED INSTRUCTION IS A JUMP.
CONTROL GOES IMMEDIATELY TO THE JUMP DESIGNATION. OTHERWISE~ CONTROL IS TRANSFERED
TO THE LOCATION FOLLOWING THE LOCATION AT WHICH THE SNAP IS CALLED.
BECAUSE OF THIS EXECUTION OF THE REPLACED INSTRUCTION FROM WITHIN SNAP$, THE
REPLACED INSTRUCTION MUST NOT 8E -

ALTERED DURING THE COURSE OF PROGRAM EXECUTION.
REFERENCED AS DATA.
REFERENCED BY INDIRECT ADDRESSING.
AN SLJ WHICH SPECIFIES INDIRECT ADDRESSING OR INDEXING.
AN LMJ WHICH SPECIFIES INDEXING.
'
AN EX WHICH INDIRECTLY REFERENCES AN LMJ OR SLJ;
A TEST SKIP INSTRUCTION.

15.1.3.15.

THE END STATEMENT

IF A DATA STATEMENT (AS OPPOSED TO A CONTROL STATEMENT -- Q IN COLUMN 1) WHICH IS
UNRELATED TO THE COLLECTION FOLLOWS A QMAP STATEMENT, AN END STATEMENT PLACED AFTER
THE LAST COLLECTOR SOURCE STATEMENT MAY BE NECESSARY TO TELL THE COLLECTOR TO
DISREGARD T.HE DATA STATEMENTS FOLLOWING. THE FORMAT OF THE STATEMENT IS:

f~

\

~

"

END
15.1,4.

FUNCTIONAL ASPECTS

FUNCTIONALLY, THE COLLECTOR MUST INTERPRET THE SOURCE INPUT LANGAUGE, FIND THE
ELEMENTS TO INCLUDE, AND GENERATE THE OUTPUT LISTING. THE FOLLOWING DESCRIPTION
PERTAINS TO THE PROCEDURE FOR THE MORE GENERAL CASE OF A SEGMENTED PROGRAM; HOWEVER,
A NON SEGMENTED PROGRAM CAN BE CONSIDERED AS BEING A SEGMENTED PROGRAM WITH ONLY A
MAIN SEGMENT.
INITIALLY, PARAMETERS FROM THE QMAP (OR QXQT) CONTROL STATEMENT ARE OBTAINED AND
INTERPRETED. ALL OF THE COLLECTOR CONTROL STATEMENTS ARE INTERPRETED AND SAVED IN
TABLES INTERNAL TO THE COLLECTOR. DIAGNOSTIC MESSAGES ARE GIVEN WHERE APPROPRIATE.
ELEMENTS NAMED ON IN STATEMENTS BUT NOT PRECEDED BY A FILE NAME ARE MAINTAINED IN A
LIST APART FROM ELEMENTS NAMED WITH A DESIGNATED FILE NAME.
ELEMENTS ARE ADDED TO THE COLLECTION IN TWO STEPS. THE FIRST STEP INVOLVES
FINDING THE ELEMENTS EXPLICITELY NAMED ON lN STATEMENTS, AND PROCESSING THE
INFORM~TION CONTAINED IN THE PREAMBLE SECTION OF EACH ELEMENT.
IN ADDITION TO THE
THE EXPLICITELY NAMED ELEMENTS, ALL THE ELEMEr4TS IN THE RUN'S TEMPORARY PROGRAM FILE
(TPF$) MAY BE AUTOMATICALLY PROCESSED IN STEP ONE. WHEN TPF$ HAS BEEN PREPARED BY
THE QPREP STATEMENT (A BLANK NAME FIELD ON A ~PREP STATEMENT ALWAYS IMPLIES TPF$),
THE AUTOMATIC PROCESSING OF ITS ELEMENTS IS INHIBITED. TPF$ ELEMENTS AUTOMATICALLY
PROCESSED ARE ADDED TO THE PROGRAM ONLY IF REFERENCES ARE MADE TO THEM, OR IF THERE
AkE NO IN STATEMENTS AT ALL (WHICH THE COLLECTOR TREATS AS AN IMPLIED: IN TPF$).
TPF$ IS ALWAyS THE FIRST LIBRARY SEARCHED FOR ELEMENTS EXPLICITELY NAMED BUT
WITHOUT FILE DESIGNATION. (THE COLLECTOR INCLUDES TPF$ AS THE FIRST ENTRY IN ITS
INTERNAL LIB TABLE, AS IF THERE HAD BEEN A LI&TPF$ STATEMENT.) FILES ACTUALLY NAMED
Ol~ LIB STATEMENTS MAKE UP THE SECOND LEVEL OF SEARCHING.
THE LAST LEVEL OF SEARCHING

C~
!

.:

UP-4144

Rev. 1

UNIVAC 110B

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

I

15
SECTION:

COVERS SYS$*RLIH$ (SEE EXECUTIVE CONTROL LANGUAGE CHAPTER: SYSTEM LIBRARIES).
(SYS$*RLIe~ IS gP~EP'ED AT SYSTEM BOOT TIME, AND THE cOLLECTOR INCLUDES IT
AUTO~ATICALLY AS THE LAST ENTRY OF THE INTERNAL LIB TABLE, EXCEPT IN AN R-OPTION
iiill\\/\P) •
THE PR[~MULE OF AN ELEMENT INCLUDES THE DEFINITION OF EACH ENTRY POINT IN THE
ELEMENT, THE LENGTH OF EACH LOCATION COUNTER USED, EVERY SYMBOL YET UNDEFINED IN THE
ELEMENT, AND CU~M0N BLOCKS DEFINED BY THE ELEMENT. IN PROCESSING THE PREAMBLES, THE
ENTRY POINTS OF THE ELEMENT ARE PUT INTO TilE INTERNAL COLLECTOR EP TA8LE. THE
UNDEFINED SYMBOLS ARE LINKED TO AN ENTRY POINT BY THE SAME NAME IN THE EP TABLE, OR
ADOED TO TltE LIST OF SYMBOLS YET UNDEFINED (THE UNDE LIST) FROM ELEMENTS PREVIOUSLY
PROCESSED. SYMdOLS ARE REMOVED FROM THE UNDE LIST AS ENTRY POINTS OF THE SAME NAMES
ARE [NCOUNTERED IN PROCESSING PREAMBLES.
THE SECOND STEP IN ADUING ELEMENTS TO THE COLLECTION INVOLVES SEARCHING LIBRARIES
FUR ELEMENTS WITH ENTRY POINTS OF THE SAME NAMES AS THOSE IN THE UNDE LIST,
ACCUMULATED Ii~PHOCESSING PREAMBLES OF INCLUDED ELEMENTS. ONLY LIBRARIES THAT HAVE
BEEN QPHEP'ED (ENTRy POINT TABLE PREPARED) WILL BE SEARCHED IN THE SECOND STEP.
EVERY UNDEFI~EG SYMBOL CURRENTLY IN THE UNOE LIST IS LOOKED FOR IN EACH LIBRARY.
WHEN AN ELEMENT IS FOUND WITH AN ENTRY POINT dY THE SAME NAME, THE PREAMBLE OF THAT
ELEMENT IS THE~ ALSO PROCESSED AS DESCRIBED A80VE. THE UNDE LIST IS PROCESSED FROM
TOP TO BOTTOM ~ITH NEW SYM~OLS ADDED TO THE BOTTOM, TPF$ IS SEARCHED FIRST, THEN
FILES NAMED ON LIb STATEMENTS, AND THEN SYS$*HLIB$.

(-

THE ORDER OF THE APPEARANCE OF USER-SPECIFIED ELEMENTS IN ANY SEGMENT OF A PROGRAM
WILL BE THE SA~E AS THAT IN WHICH THEY WERE SPECIFIED SO LONG AS EACH WAS
SPECIFICALLY NAMED ON AN IN STATEMENT. WHEN ALL ELEMENTS WITHIN A FILE ARE INCLUDED
IN A SEGMENT, THE ORDERING OF THE ELEMENTS WITHIN A GROUP SO SPECIFIED WILL BE
RANDOM. AN EL[MEIJT INCLUDED ~y A LIBRARY SEARCH APPEARS IMMEDIATELY PRECEDING THE
USER SPECIFIED ELEMENTS OF THE SEGMENT IN THE PATH OF ALL SEGMENTS REFERENCING THE
ELEMENT.
T~E MOSr EFFICIENT COLLECTION RESuLTS WHEN EVERY ELEMENT DESIRED IN THE COLLECTION
IS EXPLICITELY NAMED, INCLUDING FILE NAME. THE REASON FOR THIS IS THE QPREP
R~QUIREMENTS AND LIBRARY SEARCHES ARE ELIMINATED.

THE FIRST ADoRESS OF THE INSTRUCTION AkEA IS ASSIGNED 01000 (OCTAL). THE ADDRESS
OF THE DATA AREA IS ALWAYS GREATER THAN THE HIGHEST ADDRESS OF ANY REENTRANT
PkOCESSOR IN THE SYSTEM. ODD LOCATION COUNTERS OF AN ELEMENT (l,3,5.ETC.) ARE
ASSIGNED TO THE INSTRUCTION AREA. EVEN NUMRERED COUNTERS (0,2,4 ETC.1 ARE ASSIGNED
TO THE DATA AREA. BLANK COMMON IS ASSIGNlD TO THE DATA AREA OF THE MAIN SEGMENT. A
NAMED COMMON BLOCK IS ATTACHED TO THE SEGMENT (IF NOT NAMED ON AN IN STATEMENT) IN
THE PATH TO THE MAIN SEGMENT OF ALL SEGMENTS REFERENCING IT.
SYMBOLIC NAMES OF EXTERNAL DEFINITIONS AND EXTERNAL REFERENCES (SEE cOMMENTS ON
rHE COLLECTOR DEF AND REF STATEMENTS), SEGMENT NAMES, QUALIFIER NAMES, FILE NAMES.
ELEMENT NAMES, VERSION NAMES, AND COMMON bLOCK NAMES, INSOFAR AS COLLECTOR
RESTRICTIONS A,H;: CONCEHNED, M.AY BE UP TO TWELVE CHARACTERS IN LENGTH AND MAY CONTAIN
AI'lY CmmINI\TION OF ALPHABETIC, NUio1ERIC, '1> OR HYPHEN CHARACTERS.
15.1.5.

COLLECTOR DEFINED

SYM~OLS

IN ADDITION TO THE COLLECTOR DEFINED SyMBOLS ENTRY$, COMMN$ AND XREF$, THREE MORE
SYMBOLS ARE AVAILAbLE TO THE USER. THE TAG LASTO$ IS GIVEN THE VALUE OF THE LAST
A~0RESS OF THE DATA AREA AT COLLECTIUN TI~E.
LIKEWISE, LASTI$ IS THE LAST ADDRESS OF
THE INSTRUCTION AREA. THE ADDRESS OF THE SEGMENT LOAU TABLE IS MADE AVAILABLE TO THE
DIAGNOSTIC SYSTEM BY DEFINING THE TAG SLTS. TfllS TAG SHOULD BE OF LITTLE INTEREST TO
THE uS[K.
15.1.6.

PROGRAM SEGMENTATION

A~D

LOADING

THE CAPABILITIES OFFERED BY THE COLLEC10R FOR SEGMENTING A PROGRAM PROVIDE THE
WITH A STRAIGflTFORWAkO MEANS OF-CONSIHUCTING OVERLAY SEGMENTS EXACTLY AS HE

US~R

13
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

is
SECTION:

WISHES~
FOR EACH SEGMENT THE USER PREPARES IN AND.NOT CONTROL STATEMENTS TO SPECIFY
TtE RELOCATABLE ELEMENTS TO BE INCLUDED WITHIN THAT PARTICULAR SEGMENT. THESE
STATEMENTS ARE PRECEDED BY A SEG OR DSEG STATEMENT SPECIFYING THE NAME OF THE SEGMENT
AND ITS LOGICAL ORIGIN. WHEN A SEGMENTED PROGRAM IS CALLED FOR BY THE QXQT EXECUTIVE
cuNTROL STATEMENT, ONLY THE MAIN SEGMENT IS It~ITIALLY LOADED. THERE ARE TWO WAYS BY
WHICH OTHER SE,Gr>1ENTS MAY BE LOADED. THE DIRECT METHOD IS WHENEVER THE USER MAKES A
DIRECT CALL TO THE SEGMENT LOADER SPECIFYING THE SEGMENT TO BE LOADED AND THE
LOCATION TO WHICH CONTROL IS TO BE TRANSFERRED AFTER IT IS LOADED.
THE DIRECT METtiOD OF LOADING IS ACCOMPLISHED WITH THE PROCEDURE CALL:

L$OAD

NAME,JUMP,CLEAR,ADDRESS

WHERE tNAr-IE' IS THE NAME OF THE SEGMENT TO LOAD. THE PARAMETER .JUMP' INDICATES THE
LOCATION TO WHIcH CONTROL wILL BE TRANSFERRED WHEN THE LOAD IS COMPLETE. THE USE OF
AN EXIT FO~ THE LOADER OF THIS FORM IS REQUIRED SINCE THE SEGMENT IN WHICH THE
CALLING SE0UENCERESIDES MAY BE OVERLAYED BY THE SEGMENT BEING LOADED. IF THIS FIELD
IS OMITTED, CONTROL IS RETURNED FOLLOWING THE CALL. WHEN THE FIELD 'CLEAR. IS
NONZERO THE AREA OCCUPIED BY THE SEGMENT BEING LOADED IS NOT CLEARED TO ZERO. THE
OPTIOi~AL FIELD 'AODRESS' IS THE ADDRESS TO LOAD A RELOCATABLE SEGMENT.
IF THIS FIELD
IS OMITTED WHEr~ LOADING A RELOCATABLE SEGMENT, THE ADDRESS MUST BE IN A2 BEFORE THE
CALL IS MADE.
THE CALL
L$OAD
NAME, JUMP
WILL GENERATE:
L,U
L,U
ER

AI,JUMP
AO,NAME
LOAD$

THE INDIRECT METHOD PROVIDES FOR AUTOMATIC LOADING OF A SEGMENT REFERENCED BY ANY
JUMP TYPE COMMAND TO AN INSTRUCTION (IBANK) AREA, WHENEVER THE SEGMENT IS NOT IN
CORE. SEGMENTS TO BE LOADED BY TtE INDIRECT METHOD MUST BE SO MARKED ON THE SEG OR
OSEG STATEMENT. THE MECHANICS FOR SUCH LOADIrJG ARE SET UP BY THE COLLECTOR AND
CARRIED OUT BY THE SEGMENT LOADER. THE COLLECTOR REPLACES THE ADDRESS PORTION OF THE
JUMP COMMAND WITH THE ADDRESS OF A INDIRECT LOAD TABLE ENTRY. THE INDIRECT LOAD
TABLE PERFORMS AN SLJ TO THE INDIRECT LOAD ROUTINE WHICH IN TURN PERFORMS AN ER TO
THE SEGMENT LOADER (IF THE SEGMENT IS NOT ALREADY LOADED) AND JUMPS TO THE LOCATION
OF TtiE EXTERNALLY DEFINED SyMBOL. ALL REGISTERS ARE pRESERVED BY THE PROCESS. THE
INUIRECT LOAD TABLE AND THE SEGMENT LOAD TABLE ARE ASSIGNED TO THE DATA AREA OF THE
MAIN SEGMENT.
IF INDIRECT LOADING IS
WITH AtJ OFFSET.

I)S~D,

THE REFERENCE MAY NOT BE MADE TO THE EXTERNAL SYMBOL

THE AREA ASSIGNED A DYNAMIC SEGMENT MAY BE RELEASED WITH THE PROCEDURE CALL:
NAfvlE,JUMP
dHERE 'NAME' SPECIFIES THE DYNAMIC SEGMENT TO RELEASE AND 'JUMP' SPECIFIES THE
L0CATION TO TRANSFER CONTROL WHEN ~HE SEGMENT IS RELEASED. ANY REFERENCE TO THE
(n :'lAMIC SEGMENT WITHOUT AGAIN CAUSING IT TO BE LOADED MAY RESULT IN A MEMORY
P~OTECTION VIOLATION.

THE ABOVE
L,U
L,U
EI{

pr~OCEDURE

CALL GENERATES THE. FOLLOWING INSTRUCTIONS:

AI,JUMP
AO,NAME
DREL$

THE FOLLOWING EXAMPLE IS GIVtN TO ILLUSTRATE THE USE OF THE SEGMENTATION
FACILITIES OF THE COLLECTOR.
ASSUME FILEA HAS THE FOLLOdING
001S1UE OF THE FILE:

RELOCATA~LE

ELEMENTS WITH THE INDICATED REFERENCES

/

14
PAGE:

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

15

PROGRAMMERS REFERENCE

SECTION:

(
F I LEA ELE.ivlENTS
i-JAME/VERSION

REFERENCES OUTSIDE OF FILEA REQUIRED
FILE. NAME/VERSION

r-lAIN
Al/A
A2/A

FILEA.A1,81.Fl
LIB1.SIN/X
LIB2.COS/X
LIBl.SQRT/X

A3/A

61/8

BUB
133/8

Cl/C

LIB1.SQRT/X

CUC

Ll1/D

LIB2.CAT/Y

l.I2/D

E1/E
E2fE
F1
F2
G1/G
&2/G
G3/G

LIB2.CAT/Y

LIB1.SIN/X
LIB2.COS/X

A PARTICULAR COLLECTION SETUP FOR SEGMENTING A PROGRAM FROM THIS FILE MIGHT BE AS
FOLLOWS:

iolPHEP
LIB1.
fOlPREP
LIEi2.
fOlMAP,LI
t-IAPSYM, t'~APABS
SE.G
MAIN
IN
FILEA.MAIN
SEG
A*, (MAIN)
IN
FILEA.A1/A,.A2/A".A3/A
SEG
8*, (A)
IN
FILEA.81/B,.B2/B,.B3/B
SEG
C*, 8
IN
FILEA.Cl/C,.C2/C
0*, (B,C)
SEG
IN
FILEA.Ol/D,.D2/D
SEG
E*, 0
IN
FILEA.El/E,.E2/E
F*, (D,G)
DSEG
IN
FILEA.Fl,.F2
SEG
G*, (MAUl)
IN
FILEA.Gl/G,.G2/G
LIB
LIBl,LIB2
folXGr

TillS PARTICULAR SET OF CONTROL STATEMENTS WOULD RESULT IN THE MEMORY STRUCTURE
ILLUSTRATED BELOW. THE HORIZONTAL COORDINATE IS USED TO DENOTE INCREASING MEMORY
ADDRESSES FROM LEFT TO RIGHT. SEGMENTS WITH COMMON HORIZONTAL COORDINATES MAY NOT BE
! hi ME1'10'RY S I MUL TANEOUSL Y•
INSTRUCTION AREA MEMORY MAP
01000

M

K

CAT
--bl-B2-B3---SQRT
-01-02-COS
-AI-A2-A3-SIN
-EI-E2-----MAIN----CI-C2---FI--F2-----

---GI---G2------------------------DATA AREA
CAT

MEMO~Y

MAP
--BI-82-83---

o

P

15
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

15
SECTION:

ILD$
SQKT
-DI-D2-COS
-A1-A2-A3--EI-E2--~-SIN
---C1-C2-------LT-6C--MAIN---F1-F2----------G1--G2-----ILD$ IS THE NAME OF THE INDIRECT LOAD ROUTINE AND IS ALWAYS IN THE MAIN SEGMENT.
LT REPRESENTS THE SEGMENT LOAD TABLE AND INDIRECT LOAD TABLE GENERATED BY THE
COLLECTOR.
tlC STANDS FOR BLANK COMMON.
NOTE THAT THE ELEMENT CAT IS ATTACHED TO SEGMENT A AND NOT SEGMENT B OR SEGMENT C,
THE CORE AREA FROM K TO M AND FROM 0 TO P IS RELEASED TO THE EXECUTIVE SYSTEM
WHENEVER THE SEGMENT F IS RELEASED BY THE PROGRAM.
THE FIRST ADDRESs OF THE DATA AREA ,N, IS GREATER THAN OR EQUAL TO THE MINIMUM
DATA AREA ADD~E5S SPECIFIED AT SYSTEM GENERATION TIME. THIS ENABLES THE DATA AREA TO
aE LINKED TO REENTRANT PROCESSORS. N IS ALWAYS A MULTIPLE OF 01000,

15.2.1.

GEfJERAL

THE PROCEDURE DEFINITION PROCESSOR (PDP) ACCEPTS SOURCE LANGUAGE DEFINING 1108
ASSEMBLER, FOHTRAN, OR COBOL PROCEDURES AND BUILDS AN ELEMENT IN THE USER DEFINED
PROGRAM-FILE. THESE PROCEDURES MAY SUBSEQUENTLY BE REFERENCED IN AN ASSEMBLY OR
COMPILATION WITHOUT DEFINITION.
ONE TABLE dILL BE GENERATED FOR EACH TYPE OF PROCEDURE (ASSEMBLER, FORTRAN, COBOL)
IIJ A PROGRAM-FILE. THIS TABLE WILL CONTAIN ANY LABELS THAT ARE DEFINED EXTERNALLY TO
THE PROCE00RE. IN THE CASE OF FORTRAN AND COBOL PRECEDURES, THESE WILL BE THE LABELS
ON THE PROC LINE. IN THE CASE OF ASSEMBLER PROCEDURES THESE WILL BE THOSE LABELS
DEFINED EXTERNALLY (TRAILJNG ASTERISK AFTER LABEL) ON THE PROC AND NAME LINES OF A
FIRST LEVEL PROCEDURE. FOR EVERY LABEL ENTERED IN A TABLE THE LOCATION OF THE
PROCEDURE OR NAME LINE IS NOTED, WHEN A CALL IS MADE FOR A PROCEDURE IN A SOURCE
PROGRAM THE SYSTEM AUTOMATICALLY RETRIEVES THE PROCEDURE. IF MORE THAN ONE PROCEDURE
OF THE SAM~ TyPE (ASSEMBLER, FORTRAN, COBOL) HAS THE SAME LABEL AN ENTRY WILL BE MADE
IN THE TAbLE FOR EACH PROCEDURE, BUT A CALL ON THAT PROCEDURE WILL PRODUCE THE LAST
ONE ENTERED.
THE PROCEDURE DEFINITION PROCESSOR IS CALLED WHENEVER A PDP EXECUTIVE CONTROL
STATEMENT IS ENCOUNTERED. THE FORMAT OF TillS STATEMENT IS AS FOLLOWS:
QPDP,OPTIONS ELEMENTl,ELEMENT2
THE FIELD 'OPTIONS' MAY CONTAIN ANy OF THE FOLLOWING LETTERS TO INDICATE
DIRECTIONS TO THE PROCEDURE DEFINITION PROCESSOR:
F
C

INDICATES A FORTRAN PROCEDURE ELEMENT.
IN0ICATES A COBOL PROCEDURE ELEMENT.
C PRODUCE A COMPLETE LISTING OF THE OUTPUT ELEMENT WITH
A ACCEPT THE RESULTS AS COR~ECT EVEN IF ERRORS ARE
DETECTEI).
X ABORT THE REMAINDER OF THE RUN IF ANY ERRORS ARE
DETECTED.
I INTRODUCE SOURCE LANGUAGE ELEMENT INTO PROGRAM FILE
FROM THE CONTROL STREAM.
U PRODUCE A NEW CYCLE OF THE SOURCE LANGUAGE ELEMENT.
WHEN THE 'F' OPTION IS PRESENT, PDP ASSUMES IT IS INSERTING OR UPDATING A FORTRAN
PKOCEOURE ELEI4ENT. WHEN THE 'C' OPTION IS PRESENT, THE PDP ASSUMES IT IS INSERTING
OK UPUATING A COBOL PROCEDURE ELEMENT. WHEN NEITHER OPTION IS PRESENT, THE PDP

16
PAGE:

UP-4144

Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

ASSUMES IT IS INSERTING OR UPDATING AN 1108 ASSEMBLER PROCEDURE ELEMENT.
THE FIELDS 'ELEMENT!' AND IELEMENT2' ARE OF THE STANDARD FORMAT FOR SYMBOLIC
ELEMENT DESCRIPTION. THE FIELD 'ELEMENT!' NORMALLy IDENTIFIES AN INPUT ELEMENT BY
FILE, ELEMENT NAME, VERSION, AND CYCLE. HOWEVER, W~EN THE I OPTION IS USED,
'ELEMENT!' IS THE IDENTIFICATION TO BE GIVEN TO THE NEW PROGRAM FILE ELEMENT.
THE FIELD 'ELEMENT2' IS USED AS THE IDENTIFICATION OF A NEW OUTPUT ELEMENT
WHENEVER IT APPEARS. STANDARD SYSTEM DROPOUT RULES APPLY TO BOTH ,ELEMENTl' AND
'ELEMENT2'.
THE I OPTION IS USED SOLELy TO INTRODUCE SOURCE CARD IMAGES INTO A PROGRAM FILE •
WHEN APPLYING CORRECTIONS TO AN ELEMENT, THE I OPTION IS NOT PERMITTED •
PDP WILL PEHMIT PROCESSING PROCEDURAL ELEMENTS FROM A TAPE FILE THAT IS IN ELEMENT
FILE FORMAT • FURTHERMORE, CORRECTIONS TO THIS ELEMENT ARE PERMITTED IF A SOURCE
ELEMENT IS PROUUCED IN A PROGRAM FILE. PDP WILL NOT ATTEMPT TO INTERPRET THE NAMES ON
A CONTROL CARD; I.E •• IT WILL MAKE NO EFFORT TO INSURE UNIQUENESS OR AVOID POSSIBLE
DUPLICATION OF NAMES IN SPEC! AND SPEC2 FIELDS.
CYCLING OF PROCEDURES IS PERMITTED. THE CYCLE NUMBER MAY BE INCREASED IF THE U
OPTION IS ON, BUT ONLy ONE CYCLE IS RETAINED, AND WHEN THE PROCEDURE IS CALLED FOR
INCLUSION , THE LATEST CYCLE IS GIVEN •
SOME EXAMPLES ON THE USE OF THE QPDP STATEMENT ARE AS FOLLOWS:
QPDP,L

A,B,C

PRODuCE A PROCEDURE ELEMENT
FROM FILE A ( IF IT IS A PF
OR TAPE FILE ) ELEMENT BAND
PUT THE NEW SOURCE CODE IN
THE TE~PORARY'PROGRAM FILE.
PRODUCE A COMPLETE LISTING.

fOlPDP,L

A.B,.C

PRODUCE A PROCEDURE ELEMENT
FROM PROGRAM FILE A ELEMENT
B , CALL IT ELEMENT C AND PUT
IT IN PROGRAM FILE A • PRODUCE A COMPLETE LISTING •
BOTH ELEMENTS BAND CARE
RETAINED • A TAPE FILE IS
NOT PERMITTED FOR SPEC2 •
PDP WILL ERROR OUT BUT WILL
NOT ABORT UNLESS THE 'x' OPTION
IS ON •

rOlPOP,L

A.B

PRODUCE A COMPLETE LISTING
OF ELEMENT B FROM FILE A •

QPl)P,U

A.B

iolPDP,I

AFILE.PHOCS/AB

rOlPl)p, u

BFILE.PAT/DE

IF FILE A IS A PROGRAM FILE
ELEMENT B HAS ITS CYCLE INCREASED BY 1 , AND THE
ELEMENT IS ENTERED INTO THE
PROGRAM FILE NAMED 'A' •
SPEC 2 MAY NOT DESIGNATE A
TAPE FILE •
~PROCEDURE DEFINITIONS
FOLLOWING THE ~PDP ARE
INTRODUCED INTO AFILE AS
ELEMENTPROCS, VERSION AB,
CYCLE 0.)
(CORRECTIONS ARE APPLIED TO
ELEMENT PAT, VERSION DE,
LATEST CYCLE, IN BFILE TO
PRODUCE AN UPDATED CYCLE OF
THE SAME ELEMENT IN THE SAME

(

17
PAGE: .

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

FILE. )
(ANY CORRECTIONS F-oLLOWING
THE ~PDP STATEMENT ARE MERGED
WITH THE MOST RECENT CyCLE OF
ELEMENT PRl FROM FILE AF TO
PRODUCE CYCLE O-OF ELEMENT
PR2 IN FILE BF.)
IF PDP IS PROCESSING ELEMENTS FROM A TAPE FILE, THE FILE MUST BE POSITIONED SO THE
LABEL BLOCK WILL BE READ IN • IF THE NAME IN THE LABEL BLOCK DOES NOT AGREE WITH THE
SPECl ELEMENT NAME, PDP TAKES THE ERROR EXIT .
QPDP

15.2.i.

AF ,PRl ,BF .PR2

ASSEMBLER PROCEDURES

THE PDP WILL ACCEPT SOURCE LANGUAGE DEFINING 1108 ASSEMBLER PROCEDURES THAT ARE TO
BE CALLED BY NAME THROUGH SOURCE INPUT TO THE 1108 ASSEMBLER. WHEN A GIVEN PROCEDURE
IS CALLED, THE ASSEMBLER WILL USE ANY DEFINITION OF THAT PROCEDURE INCLUDED IN ITS
INPUT SOURCE LANGUAGE. IF NONE IS PRESENT, THE PROGRAM FILE FROM WHICH THE SOURCE
INPUT WAS OBTAINED WILL BE INTERROGATED FOR A DEFINITION. IF NO DEFINITION IS FOUND
THERE, THE SYSTEMS LIBRARY IS INTERROGATED. IF NO DEFINITION IS FOUND, THE ASSEMBLER
GIVES AN ERROR INDICATOR.
THE 1108 ASSEMBLER PROCEDURE HAS THE FORM:
AA*

PROC

BB*

NAME
END

WHERE 'PROC' AND 'NAME' ARE THE STANDARD ASSEMBLER DIRECTIVES. AN ENTRY WILL BE
MADE IN THE PROGRAM-FILE ASSEMBLER PROCEDURE TABLE FOR LABELS 'AA' AND '8B'.
THE DEF DIRECTIVE.
THE FUNCTION OF THE DEF DIRECTIVE IS TO PRECEDE THE PROC DIRECTIVE WITH ANY NUMBER
OF EQU OR FORM DIRECTIVES FOR A PROCEDURE. THE ENTRY IN THE ASSEMBLER PROCEDURE
TABLE WILL THEN POINT TO THE DEF LINE RATHER THAN THE PROC LINE. THE PURPOSE OF THE
DEF DIRECTIVE IS TO SAVE PROCEDURE STORAGE SPACE IN CORE AT ASSEMBLY TIME. THUS:
DEF
AO
EQU
12
Al
EQU
13

A15
EQU
27
AREG* PROC
0,0
END
WILL ALLOW AO,A1, ••• ,A15 TO BE DEFINED IN A PROGRAM BY CALLING THE PROC AREG, YETONLY TWO ~ORDS OF PROCEDURE STORAGE IN CORE ARE USED.
15.2.3.

FORTRAN PROCEDURE

A FORTRAN PROCEOURE CONTAINS FORTRAN SOURCE LANGUAGE THAT IS TB BE INCLUDED IN A
COMPILATION BY USE OF THE FORTRAN INCLUDE STATEMENT. WHEN SUCH A CALL IS MADE THE
PkOGRAM-FILE FROM WHICH THE SOURCE INPUT .WAS OBTAINED IS INTERROGATED FOR THE
P~OCE0URE.
IF NONE, THE SYSTEM LIBRARY IS INTERROGATED. IF NO DEFIN1TION IS FOUND,
TrlE COMPILER GIVES AN ERROR INDICATION.
THE FORTRAN PROCEDURE HAS THE FORM:
AA

PI-WC

(FORTRAN STATEMENTS)
Elm

18
PAGE:

UP-4144
Re.v.1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

15
SECTION:

AN ENTRY WILL BE MADE IN THE PROGRAM-FILE FORTRAN PROCEDURE TABLE FOR THE LABEL
'AA'. THE END STATEMENT FOR FORTRAN PROCEDURES MUST BEGIN IN COLUMN TWO (2).
15.2.4.

COBOL PROCEDURE

A COBOL PROCEDURE CONTAINS COBOL SOURCE LA~GUAGE THAT IS TO BE INCLUDED IN A
BY USE OF THE COBOL INCLUDE AND COpy VERBS. WHEN SUCH A CALL IS MADE,
THE PROGRAM-FILE FROM WHICH THE SOURCE INPUT WAS OBTAINED IS INTERROGATED FOR THE
PkOCEDURE. IF NONE. THE SySTEMS LIBRARY IS INTERROGATED. IF NO DEFINITION IS FOUND,
THE COMPILER GIVES AN ERROR INDICATOR.
THE COBOL PkOCEDURE HAS THE FORM:
AA
PROC

COMPILATIO~

(COBOL STATEMENTS)
END
AN ENTRY WILL BE MADE IN THE PROGRAM-FILE COBOL PROCEDURE TABLE FOR THE LABEL
'AA'. 'END' MUST BEGIN IN COLUMN Z •
15.3.

THE QED STATEMENT

THE 'ED' STATEMENT MAY BE USED TO INSERT IMAGES INTO A PROGRAM FILE ELEMENT OR
DATA FILE. IT MAY ALSO BE uSED TO CHANGE THE IMAGE OR A PORTION OF THE IMAGE. OR IT
MAY BE USED TO 0ELETE THE ENTIRE IMAGE.

(

THE COOPERATION OF DR. J. SALTZER IN PROVIDING PROGRAM LISTINGS IS HEREWITH
EXPRESSLY APPRECIATED.
THE 'ED, PROCESSOR,BY NATURE OF ITS TECHNIQUE, WILL NOT ACCEPT CORRECTION LINES OF
THE FORM -N,M AS 00 OTHER sYSTEM PROCESSORS. THERE ARE TWO BASIC MODES IN WHICH THE
PROCESSOR OPERATES; (1) THE INPUT MODE, AND (2) THE EDIT MODE.
THE INPUT FILE NAMED AS SPECIFICATION FIELD ONE MUST HAVE BEEN PREVIOUSLY ASSIGNED
uR ~E CATALOGUED. SPECIFICATION FIELD TWO FILENAME NEED NOT BE ASSIGNED OR
CATALOGUED. 'ED' WILL ASSIGN THE FILE ON FASTRAND, BUT IT IS UP TO THE USER TO
PERFORM THE ACTUAL CATALOGING OF THE FILE IF DESIRED.
THE FORMAT OF THE PROCESSOR CALL IMAGE IS A FOLLOWS:
~ED.OPTroNS

NAMEl,NAMEZ.

NAME1(INPUT) AND NAMEZ(OUTPUT) ARE THE NAMES DEFINING THE PROGRAM FILE ELEMENT,
AND VERSION NAMES 8Y WHICH THE UNIT IS KNOWN. THE THREE OPTIONS WHICH ARE AVAILABLE
AHE:
1- ENTER 'ED' WITH THE INPUT MODE. NAMEZ IS IGNORED,
AND NAME1 IS THE NAME OF THE OUTPUT FILE CONTAINING
THE SOURCE IMAGES.
D- IF THE '0' OPTION IS PRESENT NAMEl AND/OR NAME2 ARE
THE NAMES OF A DATA FILE- AS OPPOSED TO A PROGRAM
FILE.
U- CREATE A NEW CYCLE OF THE DATA FILE OR PROGRAM FILE
ELEMENT.

('

NAME2 IS IGNORED.

E- ECHO (I.E., PRINT OUT) AL~ COMMANDS FROM THE INPUT
STREAM. THEY WILL BE INDENTED AND FLAGGED WITH
THREE ASTERISKS. THIS MAY BE PARTICULARLY USEFUL
FOR CARD INPUT (BATCH) RUNS.
- ABSENCE OF ALL OF THE OPTIONS I, 0, AND U REQUIRES
NAME! AS THE INPUT FILE NAME AND NAME2 AS THE
OUTPUT FILE NAME.
NOTE; THE FOLLOWING DEFINES THE ONLY DIFFERENCE IN THE UTILIZATION OF 'ED' FROM A

19
PAGE:

,
UP-4144

Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE.

15
SECTION:

20
PAGE:

c
TERMINAL (SUCH AS A TELETYPE) AND FROM A CARD READER. A.CARRIAGE RETURN ON A TTY
SIGNIFIES THE END OF THE IMA~E, WHILE ON A CARD READER THE IMAGE IS DETERMINED BY THE
IMAGE LENGTH PASSED ON BY READ$.
A SINGLE CR ON A TELETYPE OR A BLANK CARD CHANGES 'ED' FROM THE INPUT TO THE EDIT
MODE. OR VICE VERSA,
THE FOLLOWING COMMANDS ARE AVAILABLE TO 'EO' TO PERMIT THE MANIPULATION OF IMAGES
IN A FILE OR ELEMENT. NOTE THAT COMMANDS A THROUGH J MAY BE WRITTEN COMPLETELY OR
ABBREVIATED BY A SINGLE LETTER •

c

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROG.RAMMERS REFERENCE

cor.jMAlm
A.

TOP
T

B.

BOTTOM
B

C.

NEXT
NM

D.

SYSTEM

FUNCTIOiJ

-------------------------------------------POSITION A POINTER TO THE TOP OF A FILE. IF

THE CURRENT POSITION IS NOT AT THE TOP OR
BOTTOM OF A FILE REMAINING IMAGES FROM THE
INPUT ARE COPIED TO THE OUfPUT FILE, AND THE
POINTER IS POSITIONED AT T~E 'TOP' OF THE
OUTPUT FILE.
ANY IMAGES FROM THE O~D FILE (PLUS THOSE
3EING PROCESSEU) ARE COPIEJ TO THE NEW FILE.
'EU' THEN ENTEHS THE INPUT I-l0DE AND ANy
FOLLOWI~G IMAGES ARE WRITTEN TO THE NEW
FILE. THE INPUT MODE MAY BE TERMINATED BY
TYPING A CARRIAGE RETURN (CR).

M

THE 1>, 1f'.1AGES ARE COPIED FRO,,1 NAME1 TO NAME2.
THE MTH IMAGE IS NOT WRITTEN TO NAME2.

DELETE M THE CURRENT IMAGE IS SKIPPEO AS ARE THE NEXT
M-l IMAGES. THE POINTER INTo NAMEl IS ADVANCED M-l I~'AGES.

o M

E.

INSERr(CR) THE INPUT MODE IS ENTE~ED.
I(CR)
INSERT LINE THE LINE AS TYPED IS ACCEPTED FOLLOWING
I LINE
THE CURRENT IMAGE.

F.

RETYPE LliJE
R LINE

G.

PRINT
P N

H.

FIND LINEMASK. EACH I~AGE IS SCANNlD TO FIND A GROUP
F LINEMASK
OF CHARACTERS WHICh CORRESPONDS TO THE
LINEMASK EXCLUDING BLANKS. OBSERVE THAT
CAHO COLUMNS IN THIS COMMAND ARE IMPORTANT. SEE EXAMPLE bELON:

N

THE LINE AS TYPED IS ACCEPTED,
AND THE CURRENT IMAGE IS REPLACED.

THE CURRENT I~AGE IS PRINTEO. IF N>l SUCCEEDING IMAGES ARE PRINTED. THE PROCESS IS
SIMILAR TO 'NEXT N~l'.

1
F

5
9
B H M-

THIS SAYS TO FIND A MASK STARTING IN
COLUMN 3 WHICH CORRESPONDS TO B H M OR
BXHXM, ETC. THE POSITIONS OF THE COMMAND
WORD 'F ' OR 'FIND , MuST NOT BE COUNTED
AS PART OF THE IMAGE. ALANKS IN THE LINE
MASK CORRESPOND TO CHA~ACTERS WHItH MAY
liE IGNORED.
IF NO FIND APPLIES THE SCA,~ cONTINUES TO END
OF FILE. A MESSAGE THEN IS GIVEN STATING
THAT END OF FILE WAS EhCOU:HEHED.
I.

LOCATE STRII~G
L STkHH"
THIS

.
COfliji·~ANi)

SCANS IMAGES FOk A (>'lATCH ANY-

wiU::RE WITH 'STRING'. SndNG STARTS WITH THE

~EtOND CHARACTER FOLLOWINGrHE COMMAND.
lXAMPLE:
.
L LA A9
WILL LOCATE:
A9
OH,
LA
L
A A9, BUT NOT L

(

IF NO FIND APPLIES THE SCA;. CONTINUES TO
END OF FILE.

15
SECTION:

21
PAGE:

UP-4144

UNIVAC 1108 OPERATING

Rev.l

EXEC' B

SYSTEM

15

PROGRAMMERS REFERENCE

..J. CHAf~GE *STKII~GhSmING2*

SECTION:

22
PAGE:

NG

C *STRIIJG1*STRING2* N G

THIS COMMAND WILL EXAMINE 'N, IMAGES LOOKING
FOR A CHARACTER BY CHARACTER MATCH TO STRINGl
(INCLUDING ~LANKS). WHEN A FIND IS MADE
STRINGl IS REPLACED BY STRING2. IF G IS ABSENT
REPLACEMENT OtCURS ON ONE STRING ONLY. IF G IS
PRESENT EVERY APPEARANCE OF STRINGl IS REPLAC.
ED. ACCOUNT FOR DIFFERENT STRING LENGTHS IS
r,jADE. IF N IS ~USSING ONE I;VlAGE ONLY IS SCANNED. VIZ. C *A*B* G • THIS ~ILL CHANGE ALL A'S
TO B'S IN THE IMAGE. IF A SAVE COMMAND IS IN
EFFECT NO A'S WILL BE CHANGED AFTER THE SAVE
COLUMN. ANY CHARACTER MAY BE USED TO DELIMIT
STRINGl AND STRING2. G IN THE EXAMPLE IS THE
CHARACTER G.

EXM1f'LE l:
IiilRUN
fo1l:.0,1
IN!
AXi-($.

START*.
LA,U
EH
E,{

AO, [.lESS!
COI'lX
EXlh

ME-SSl +U
+13, $+&:

+u

'HI THERE,

• THE ELEMENT NAMED INl
• WILL BE INSERTEO IN THE
• TEMPORARY RUN FILE
• TOGETHER WITH THESE
• COMMENTS WHEN 'ED' IS
• TERMINATED

HJO STAfn

TOP

•

BLAf~K

CARD HERE (COMMENTS NOT PERMITTED)

N 4

CHMIGE.

*X*~h

( ANY CONTROL IMAGE l

~tOF

THE FOLLOWIrlG 'ED' COMMANDS HAVE NO AtI£iREVIATlONS.
K. SAVE M

THIS COMMANDS RESTRICTS THE CHANGE COMMAND
TO COLUMNS UP TO AND INCLUDING COLUMN M. IT
MIGHT BE DESIRABLE FOR EXAMPLE. TO PROHIBIT
CHANGING 10'5 COtHAHlED IN COLUMNS 73-80.
IF M IS NOT SPECIFIED ON THE COMMAND 72 IS
ASSUMED.

L. VERIFY

THIS COMMAND NULLIFIES THE'~RIEF' COMMAND.
ALL LINES Ifl THe.: NORK AREA 'EO' USES ARE
PRINTED.

M. ::\kIEF

IHIS COt'~r1ANO TUHNS OFF THE "ERIFY MODE. IF
SPECIfiED, THE VERIFY MOUE IS ALwAYS ON.

r~OT

N. SPLIT NM',E3 A PART IAL FILE (OR ELEMeNT) t.1AY BE FILED
UNDER NAME3 BY USING THIS COMMAND. ALL IMAGES
HJ THE HIPUT FILE PRECEt.l.lING THE ONE CURRENTLY
UEItJG PROCESSED ARE FILE.ll IlJ NAME3. SUCCEEDING IMAGES ARE NOT FILE~ IN NAME3.
O. ADD

NAMEL~

THIS COMMAND IS USED TO ENTER SUCCESSIVE
IMAGES FROfJl THE FILE NM1F.D IJAME4 (EITHER
A PREGRA~ FILE ELEMENT OR DATA FILE) TO THE
END Of THE FILE 'ED' IS PROctSSING.

c

UP-4144
Rev. 1

P.

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

Er~D

SYSTEM
REFERENCE

TERMINATE 'EO', 00 NOT FILE THE ELEMENT.

0. SlG,lD I SV lHIS COMMAND MAY BE USED IF IT IS DESIRED TO
PROVIDE SEQUENCE NUMAERS TO THE IMAGES. 10 IS
THE CONSTANT IDENTIFICATION TO BE SUPPLIED.
'I' IS THE INCREMENT TO UE USED IN COUNTING.
'5V' IS THE STARTING VALUE. IF THEY ARE NOT
SUPPLIED 'SV,= 100 AND '1'= 100.

THIS SETS ANY CHARACTER 'Q, AS THE TAB
CHARACTER TO BE USED IN THE IMAGE STRINGS OF
THE TYPE ANO INSERT COMMANDS OR IN INPUT
IMAGES.
S. SET Tl T2 -IN

lHIS COMMAND SETS TAB STOPS AT TN (1-80) ALONG
r HE I!V1AGE.

r.

(-

GO TO N
GO f\J

THE FIRST N-1 IMAGES ARE PUT INTO A WORK FILE.
THE POINTER IS POSITIONED AT IMAGE N.

15
SECTION:

23
PAGE:

c

·.~.
C.
".

\

UP-4144
Rev. 1

16.

16. 1 •

UNIVAC 1108

OPERATING

EXEC

PROGRAMMERS REFERENCE

a

SYSTEM

16
SECTION:

PROCESSOR INTERFACE ROUTINES

GENE.RAL

TO ENHAIJC~ THE MODULARITY OF THE UNIVAC 1108 EXECUTIVE SYSTEM, A SET OF ROUTINES
IS PkOVIDEU WHICH ALLOWS ALL PROCESSORS TO MAINTAIN A STANDARD INTERFACE WITH THE
ExECUTIVE SYSTEM. THIS MAKES lNCORPORATION OF ADDITIONAL PROCESSORS BY ANY
INSTALLATION A RELATIVELY MINOR TASK INSOFAR AS INTEGRATING THEM INTO THE SOFTWARE
SYSTEM IS CONCERNED. THESE ROUTINES ARE AVAILABLE FROM THE SYSTEMS LIBRARY AND, FOR
ANY PROCESSOR, ONLY THESE ROUTINES WHICH ARE ACTUALLY,REQUIRED WILL BE ALLOCATED WITH
THE PROCESSORS.
IN GENERAL, PROCESSORS ARE CONCERNED WITH A SOURCE INPUT, CORRECTION INPUT, SOURCE
OUTPUT, AND RELOCATABLE OUTPUT. WHEN USING THE PROCESSOR INTERFACE ROUTINES, THE
PROCESSOR NEED ONLY BE CONcERNED WITH REQUESTING THE NEXT SOURCE IMAGE, OR OUTPUTTING
A RELOCATABLE WORU. THE SOURCE INPUT ROUTINE (SIR) PROVIDES THE PROCESSOR WITH THE
N~XT SOURCE IMAGE WHILE AUTOMATICALLY MERGING CORRECTIONS, IF NECESSARY, AND
PROVIDING AN UPDATED SOURCE ELEMENT WilEN REQUESTED. THE RELOCATABLE OUTPUT ROUTINE
(HOH) FORMATS ANU OUTPUTS THE RELOCATABLE BINARY IN STANDARD BLOCK AND ITEM SIzES
ACCEPTABLE TO THE COLLECTOR.

(

PERTINENT INFQRMATIO~ FROM THE PROCESSOR CALL STATEMENT~ SUCH AS FILE NAMES,
ELEMENT NAMES, AND OPTIONS, IS PASSED ALONG To THE PROCESSOR WHEN IT IS INITIATED BY
THE SUPERVISOR. A PROCESSOR CALL STATEMENT HAS THE FOLLOWING FORMAT:
WPROCESSOR,OPTIONS
16.~.

ELEMENT1,ELEMENT2,ELEMENT3, •••

SOUH€E INPUT ROUTINE (SIR)

THE SOURCE INPUT ROUTI~E INPUTS TO THE PROCESSOR THE SYMBOLIC ELEMENT IDENTIFIED
BY THE 'ELEMENTl' FIELD OF THE CALL STATEMENT. THIS FIELD HAS THE FORM:
FILE.£LEMENT(CYCLE)
WHERE 'FILE' IS A EITHEH A PROGRAM-FILE OR A MAGNETIC TAPE FILE, AND 'ELEMENT'
IUENTIFIES THE SY;ViUOLIC ELEMENT WITHIN THAT FILE. IF THE FILE IS A TAPE FILE THE
ELEM~NT MUST BE IN THE STANDA~D TAPE ELEMENT FORMAT.
IF TilE ,I' OPTION IS USED IN THE CALL STATE~ENT, THE SOURCE INPUT WILL BE TAKEN
FROM THE CONTROL STREAM. IN THIS CASE, THE 'ELEMENTl' FIELD IDENTIFIES THE SOURCE
OUTPUT t.LE,·1ENT AND PROGRAM-F I LE:.
I~ THE SOURCE INPUT IS FROM A PROGRAM-FILE OR TAPE, CORRECTIONS MAY FOLLOW THE
CALL STATEHENT IN THE CONTROL STREANI. sm WILL MERGE THESE CORRECTIONS WITH THE
SYMBOLIC INPUT BY LINE NUMBER. (SEE CHAPlER 5.6.3)

IF 'HE 'I' OR 'U' OPTlON IS NOT USED IN THE CALL STATEMENT, THE CORRECTIONS
FOLLOWING THE CALL STATEMENT ARE APPLIED AGAli~ST THE SOURCE INPUT ELEMENT SPECIFIED
Iii THE 'ELE1",ENll, FIELD. A NEW SOURCE ELElv]ENT WHOSE NAME IS SPECIFIED IN THE
'~LEMEN13' FIELD IS GENERATED AND INSERTED IN THE PROGRAM-FILE SPECIFIED IN THE
'lLEMENT3' FIELD. IF THE 'ELEMENT3' ~lELO IS VOID, THE NEW SOURCE ELEMENT WILL NOT
BE KEPT.
IF THE ,U' OPTION IS USED IN THE CALL STATtMENT, THE CORRECTIONS FOLLOWING THE
CALL STAT[MENT ARE APPLIED AS A NEw CYCLE OF THE SOURCE INPUT ELEMENT SPECIFIED IN
ThE 'ELEM~NT1' FIELD. IF THE CYCLE LIMIT HAS ALREADY BEEN REACHED FOR THIS ELEMENT,
~lR WILL APPLY THE FIRST CYCLE OF CORRECTIONS TO THE SOURCE TO PRODUCE A NEW SOURCE

1
PAGE:

UP-4144

Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS .REFERENCE

16
SECTION,

2
PAGE:

o
WHILE ADDING THE LATEST CORRECTION CYCLE.
SIR IMPLEMENTS THE CYCLE FEATURE BY USING A RECURSIVE TECHNIGUE FOR THE
MULTI-LEVELS OF CORRECTIONS TO BE APPLIED TO THE SINGLE ELEMENT BEING UPDATED. THE
CONTROL INPUT PROVIDES THE CURRENT LEVEL OF CORRECTIONS. THE OLDEST COMPLETE SOURCE
AND THE CORRECTIONS OF THE CYCLES NOT YET IMBEDDED IN THE SOURCE ARE THE SOURCE INPUT
AND ARE MAINTAINEU IN THE PROGRAM LIBRARY.AS ONE ELEMENT. THE CORRECTION LINES UP
THROUGH THE CYCLE REQUESTED ARE APPLIED TO THE SOURCE INPUT AS IT IS PROVIDED TO THE
PROCESSOR,
SIR FOH:oIATS SY,"'BOLIC ELEMENTS IN STANDARD l)ATA FORMAT (SDF). EACH IMAGE HAS AN
THE UPPER THiRD CONTAINS THE IMAGE LENGTH, THE
MLUULE THU AS THE
FIRST IMAGE OF THE SYMBOLIC ELEMENT. THE IMAGE CONTROL WORD FOR A LABEL IMAGE HAS
BIT 35 SET TO ONE. SIR PASSES ALL IMAGES TO THE USER, BUT ONLY COUNifS THOSE IMAGES
WITH BIT 35 SET TO ZERO AS ,ITEMS WHEN APPLYING CORRECTIONS.
IMAeE CONTROL WORD PRECEDING IT.

NOTE.: THE ABOVE DISCUSSION ~1ENTIONS THIHO'SOF A WORD AS DOES THE EXAMPLE BEL.OW.
IN RtALITY THE IMAGE LENGTH, DELETE CYCLE, AND CYCLE NUMBER FIELDS UTILIZE ONLY A
SIXTH OF A WORD •
THE FOLLOWING EXAMPLE SHOWS HOw SIR FORMATS SYMBOLIC ELEMENTS.

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

16
SECTION:

THE FOLLOWING
ASSEMBLY:

THE FOLLOWING
UPDATE:

THE FOLLOWING
UPDATE:

fo)ASM,I PF.E
START NOP
ER EX!T$
END STAKT

roiASM,U
-1
NOP
Q •••

fa)ASM,U PF.E
-2,2"
TAG NOP
fa) •••

WOULD PRODUCE:

WOULD PRODUCE:

PF.E

Ill •••

WOULl) PRODUCE:
52

54

S6

----------.--o
:5001
0:
--.---.---.--: * 5 D F F *:
----------.--o
0:
2
--.---.------: S TAR T
--.---.------: N 0 P
------.---.-.u
2
0:
---~---------ERE X:

.-.---.------: I T $
----.-------.o 0:
2
--.---.---.--END
--.---.---.--:5 TAR T
:7777

.-.---.---.---

S2

S4

:5001

o

S6

S2

0:

: *

S DF F

: S

TAR

*:

--------.----2
o 0:
T

--------.-.--: N O'p
1

o

: N 0 P

----------.-.o 0:
2
--------.----ERE X:
----------.--: I T $
2

o

o :

-------------E N 0
-------------:S TAR T
:7777

S4

56

-.--.--------o 0:
:5001
-.-----------: * 5 D F F *:
-.--.---.----2
0
0:
-.--.--------:5 TAR T
-.--.--------: N 0 P
-.-----------2
1
1:
-.--.--------: N 0 P
-.--.--------o 2:
2
: TAG

N 0:

-------------: p
-------------. 2 o o •.
---------.. --ERE X:
--------------:1 T $

-------------o 0:
2
-------------END
:S TAR T

-------------:7717
--------------

IF THE tW' UPTION IS USED IN THE CALL STATEMENT, SIR WILL ALSO OUTPUT THE
CORRECTIONS TO THE PRINT OUTPUT FILE.
TO OPEN THE SOURCE INPUt AND OUTPUT FILES, THE PROCESSOR MUST MAKE THE FOLLOWING
CALL:
Li>1.J

11, OPNSRC
ERROR RETURr~
NORMAL.RETURN

THEREAFTERi THE PROCESSOR WILL EXECUTE
IMAGE AT THE ADUHESS SPECIFIED IN AO.

TH~

FOLLOWING CALL TO ACQUIRE A SOURCE

H1 bF AQ -~ LENGT~ OF USER IMAGE AREA
H2 OF AO -- LOCATION OF USER H'AG[ AHEA
LMJ
11,GETSRC

3
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS RE.FERENCE

SYSTEM

16
','

SECTiON:

4
PAGE:

o
ERROR RETURN
END-OF-FILE RETURN
NORMAL RETURN'
.
THE END-OF-FILE RETURN IS TAKEN WHEN AN SDF END_OF_FILE IMAGE IS ENCOUNTERED IN
THE SOURCE INPUT ELEMENT OR WHEN READ$ GIVES AN END-OF-FILE RETURN WITH THE -IOPTION ON.
WHEN THE NORMAL RETURN IS TAKEN, Al CONTAINS THE SDF IMAGE CONTROL WO~D FOR THE
I~AGE, AND H2 OF A2 CONTAINS THE 3 DIGIT FIELOATA CYCLE NUMBER FOR THE IMAGE.
IF THE
IMAGE CAME FROM THE RUN STREAM, S3 OF A2 CONTAINS A FIELDATA ASTERISK (050)1 IF NOT,
IT CONTAINS A FIELDATA SPACE (05). 51 AND S2 OF A2 ALWAYS CONTAIN FIELDATA SPACES.
AFTER THE LAST IMAGE HAS BEEN PROCESSED, THE FOLLOWING CALL IS MADE TO CLOSE THE
SOURCE INPUT AND OUTPUT FILES.
LM~

11,CLOSRC
ERROR RETURN
NORMAL RETURN

PREPROCESSOR ROUTINE (PREPRO)
A pREpROCESSOR ROUTINE MAYBE UTILIZED BY ~NY WOR~ERpROGRAM TO. ENABLE IT TO
OBTAIN FILE NAMES, OPTION~, FILE TYPES , ANd THt NEXT WRITE LOCATIONS TO HOLD THE
TEXT. THIS ROUTINE IS CALLEQ PREPRO, AND IT MUST BE ENTERED PRIOR TO.OPENING SIR.
THE PURPOSE OF PREPRO IS TQ DETERMINE IF THE fILE NAMES ON THE PROCESSOR CALL CARD
ARE PROGRAM OR TAPE FILES; I.E., IF THE PROGRAM. FILE DOES EXIST. IF IT DOES EXIST
WHERE CAN THE PROCESSOR WRITE THE TEXT AND PREAMBLE. pREPRO PRODUCES A TABLE WHICH
HAS THE FILE NAMES AND WRITE LOCATION FOR SIR AND THE PROCESSORS. THIS TABLE IS
DOCUMENTED MORE FULLY IN THE TECHNICAL DOCUMENT, THE FIRST CELL OF THE TABLE MUST BE
NAMED 'PARTBL' AND IS EXTERNALLY DEFINED.
TO CALL THE PREPROCESSOR:
LM~
Xll,PREPRO
- ERROR RETURN
- NORMAL RETURN

IF THE ERROR RETURN IS TAKEN A MESSAGE HAS BEEN DELIVERED TO PRINT$ AO HAS A CODE
VALUE
0 IF A HARUWARE ERROR CAUSED THE MALFUNCTION , NON ZERO VALUE IF THE ERROR IS
A RESULT OF A CONTROL CARD, UNDEFINED PROGRAM, OR AN IMPROPERLY POSITIONED TAPE,

=

16.4.

SOURCE OUTPUT ROUTINE (SOR)

CERTAIN PROCESSORS  GE:NERATE SOURCE LANGUAGE AS THEIR OUTPUT RATHER
THAN RELOCATAOLE TEXT. FOR THESE PROCESSORS, THE ~ELEMENT2- FIELD OF THE PROCESSOR
CALL CARD SPECIFIES THE OUTPUT SOURCE LANGUAGE WHIcH MUST NOT. BE CONFUSED WITH
'ELEMENT3', THE UPDATED SOURCE LANGUAGE. THE 'ELEMENl2' FIELD SHOULD CONFORM TO ALL
NORMAL SPECIFICATIONS FOR A SYMBOLIC ELEMENT IN A PROGRAM FILE, WITH THE EXCEPTION
THAT NO CYCLE NUMBER MAY BE GIVEN. THE CYCLE PRODUCED IS ALWAYS CYCLE O.
THE SYMBOLIC TEXT PRODUCED BY SUCH A PROCESSOR MAY BE WRITtEN OUT USING SORt SOR
PRODUCES AN ELEMENT IN THE SYSTEM DATA FORMAT (SDF), WHICH IS FULLY DESCRIBED IN THE
SECTION ON SIR (16.2).
SOR EXPECTS THAT PARTBL WILL HAVE BEEN INITIALltEDWITH THE INFORMATION FROM THE
PHOCESSOR CALL STATEMENT, GENERALLY BY.A CALLTP PREPRQ (SEE 16.~). MOREOVER, NO
OTHER ROUTINE SHOULD HAVE THE SAME PROGRAM FILE OPENED FOR OUTPUT, IN PARTICULAR,
THE fIRST PASS BY SIR SHOULD BE COMPL~TED BEFORE CALLING SORt
'.

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

16
SECTION:

TO OPEN THE SOURCE OUTPUT FILE, THE PROCESSOR MUST MAKE THE FOLLOWING CALL:
LM.J

11,550R
ERROl{ RETURN
NORMAL RETURN

THEREAFTER, THE PROCESSOR WILL MAKE THE FOLLOWING CALL TO OUTPUT A SOURCE IMAGE AT
THE ADDRESS SPECIFIED IN AO.
HI OF AO -- LENGTH OF USER IMAGE AREA «64)
H2 OF AD -- LOCATION OF USER IMAGE AREA
LM.J
11 ,SOR
ERROR RETURN
NORMAL RETURN
AFTER THE LAST IMAGE HAS BEEN OUTPUT, THE FOLLOWING CALL IS MADE TO CLOSE THE
SOURCE OUTPUT FILE.
LM.J

11,ESOR
ERROR RETURN
NORMAL RETURN

IF THE 'ELEMENT2' FI£LD HAS THE SAME FILE, ELEMENT, AND VERSION NAMES AS THAT FOR
THE UPDATED SOURCE LANGUAGE ('ELEMENT!, WITH 'I' OR 'U' OPTION, ELSE 'ELEMENT3'), THE
UPDATED SOURCE ELEi-1ENTwILL BE DELETED FROr.1 ITS PROGRAM FILE. IF THIS IS NOT TAKEN
INTO CONSIDERATION, UNEXPECTED RESULTS MAY OCCUR.
FINALLY, IT IS IMPORTANT THAT THE DIFFERENCE BETWEEN THE OUTPUT FUNCTION OF SOR
AND THE UPDATING FUNCTION OF SIR BE THOROUGHLy UNDERSTOOD. SIR APPLIES CORRECTIONS
TO AN EXISTING ELEMENT TO UPDATE ITI SOR AIDS IN THE CREATION OF AN ENTIRELY NEW
ELEMENT WHICH tJEED BEAR NO RESEMBLANCE WHATEVER TO THE INPUT ELEMENT.
16 .5.

RELQCATABLE OUTPUT ROUTINE (ROR)

THE 'ELEMENT2' FIELD OF THE PROCESSOR CALL STATEMENT SPECIFIES THE RELOCATABLE
ELEMENT NAME AND THE PROGRAM-FILE IN WHICH THE RELOCATABLE ELEMENT IS TO BE PLACED.
PRIOR TO OUTPUTTING ANY RELOCATABLE TEXT WORDS, THE PROCESSOR MUST INITIALIZE THE
RELOCATABLE OUTPUT ROUTINE WITH THE CALL.
AO -LM.J

K-BIT LIMIT
11, SROR.
ERROK RETURN
NORMAL RETURN

WHERE 'K-BIT LIMIT' IS THE NUMBER OF BITS REQUIRED TO CONTAIN THE LARGEST CONTROL
COUNTER USED OR THE NUMBER OF UNDEFINED SYMBOLS FOR THE RELOCATION, WHICHEVER IS
LARGER.
THEREAFTER, FOR EVERY WORD OF RELOCATABLE TEXT TO BE PLACED INTO THE RELOCATABLE
ELEMENT, THE PROCESsOR WILL EXECUTE THE FOLLOtiING CALL~
AU -LM.J

LOCATION OF ITEM
11 ,ROR
ERROK RETURN
NORMAL RETURN

WHEKE ,LOCATION' IS THE ADDRESS OF AN ITEM DESCRIBING THE TEXT WORD TO BE INSERTED IN
TrlE RELOCATABLE ELEMENT.
AFTER THE LAST TEXT WORD HAS BEEN PROCESSED THROUGH ROR, THE OPERATION MUST BE
T~RMINATED WITH THE CALL:

5
PAGE:

UP-4144

Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

16
SECTION:

AD -- TRANSFER ADDRESS,~OCATION COUNTER
~M.J
11,EROR
ERROH RETURN
NORMAL RETURN
THIS WILL OUTPUT THE LAST RELOCATABLE IMAGE, AND GENERATE A TRANSFER IMAGE IF AO
IS POSITIVE, THE UPPER HALF'OF AD CONTAINS THE TRANSFER ADDRESS, AND THE LOWER HALF
SPECIFIES THE LOCATION COUNTER OF THE TRANSFER ADDRESS. IF AO IS NEGATIVE WHEN EROR'
IS ENTERED NO TRANSFER IMAGE IS GENERATED.
THE PREAMBLE MUST BE CONSTRUCTED BY THE INDIVIDUAL PROCESSOR USING THE ROUTINES.
PREAMB~E

OUTPUT ROUTINE (TBLWR)

WHEN A PROCESSOR HAS CLOSED ROR • IT THEN MUST ENSURE THAT THE PREAMBLE WHICH IT
PKOUUCED GETS WRITTEN BECAUSE THESE DATA ARE REQUIRED FOR COLLECTION, THE FORMAT OF
THE PREAMBLE IS DEFINED IN THE INTERNAL SYSTEMS MANUAL (C.F, CHAPTER CONCERNING THE
COLLECTOR).
TO wRITE OUT THE PREAMBLE. LOAD CR AO WITH THE LOCATION OF THE TABLE, LOAD CR A1
WITH THE LENGTH OF THE TABLE AND:
LM.J
Xl1,TBLWR
- ERROR RETURN
- NORMAL RETURN
AN ERROR RETURN IS CAUSED BY A HARDWARE MALFUNCTION.
PHOPERLYWRITTEN.

THE TABLE HAS NOT BEEN

THE NORMAL RETURN IMPLIES ALL IS SATISFACTORY AND THE PROGRAM FILE IS READY TO
RECEIVE MORE DATA.

6
PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

1

17
SECTION:

PAGE:

(
17,

THE DIAGNOSTIC SYSTEM

17 ,1,

GENERAL.

THE 1108 EXECUTIVE SYSTEMS PROVIDES A COMPREHENSIVE DIAGNOSTIC SYSTEM TO AID IN
THE EFFICIENT CHECKOUT OF USER PROGRAMS. DUMPS ARE PROVIDED IN TWO FORMS: SNAPSHOT
(DYNAMIC) DUMPS, AND POSTMORTEM (STATIC) DUMPS • DYNAMIC DUMPS ARE ASSEMBLED WITH THE
USERS SOURCE CODE ( ASSEMBLER CODING ONLY ) AND THE RESULTANT CALLS ON THE DUMPS ARE
SATISF.IED AT COLLECTION TIME • POST MORTEM DUMPS ARE CALLED VIA THE QPMD CONTROL CARD
17.2.

17.2.1.

SNAPSHOT DUMPS VIA A PROCESSOR

BASIC OPERATION

THE 1108 EXECUTIVE SYSTEM INCLUDES THE CAPABILITY OF USING SNAPSHOT DUMPS
EMPL.OYING INFORMATION GENERATED BY THE PROCESSORS AND THE COLLECTOR. DUMPED
INFOHMATION IS WRITTEN TO A DIAGNOSTIC FILE, AND READ BACK LATER, FOR EDITING AFTER
THE PRCGRAM UNDER TEST HAS TERMINATED. ASSEMBLY PROCEDURES ARE USED IN GENERATING
CALLS TO LIBRARY SUBROUTINES WHICH ACTUALLY WRITE OUT THE DUMPS TO THE DIAGNOSTIC
FILE. THESE SUBROUTINES WILL SAVE AND RESTORE ALL THE PROGRAM,S ENVIRONMENT. THE
AMOUNT OF INFORMATION WRITTEN INTO THE DIAGNOSTIC FILE IS LIMITED BY A PARAMETER SET
AT SYSTEM GENERATION TIME.
THIS SECTION SPECIFICALLY DISCUSSES SNAPSHOT DUMPS FROM THE STANDPOINT OF A USER
OF THE 1108 ASSEMBLER. THERE IS NO INHERENT RESTRICTION ON THE EMPLOYMENT OF THE
SNAPSHOT FACILITY WITH ANY OTHER PROCESSOR, ALL THAT IS NEEDED IS THAT THE PROPER
INFORMATION BE WRITTEN TO THE DIAGNOSTIC FILE, LIBRARY ROUTINES ARE PROVIDED TO
ASSIST lN THIS PROCESS. THE USE OF THE SNAPSHOT FACILITY BY A HIGH-LEVEL LANGUAGE
PKOCESSOR FALLS OUTSIDE THE SCOPE OF THIS DOCUMENT.
17.2.2.

AVAILABLE SNAPSHOT DUMP TYPES

A GROUP OF 17 PROCEDURES IS AVAILABLE FOR THE PURPOSE o.F TAKING SPECIALIZED
SNAPSHOT DUMPS.
(1) CONDITIONAL (FOUR), X$IF, X$AND, X$OR, AND X$TALY"ARE USED
TO DETERMINE WHEN A GIVEN DUMP OR SERIES OF DUMPS SHOULD OCCUR.
(2) DUMP (SEVEN), X$MESG, X$CORE, X$DUMP, X$TAPE, X$DRUM,
X$FILE, AND X$CREG ARE USED TO RECORD DATA IN THE DIAGNOSTIC FILE.
(3) SPECIFICATION ·(SIX). X$FRMT, X$BUF, X$MARK, X$BACK, X$ON,
AND X$QFF ARE USED TO. SPECIFY ARBITRARY PRINT LINE FORMATS,
CORE SPACE FOR DRUM AND TAPE FILE DUMPs, DELETION OF
RECORDED DUMPS NOT OF INTEREST, AND A CONTROL FOR
NULL.IFYING AND ACTIVATING DIAGNOST1C PROCEDURES,
17.2.3.

(

THE CONDITIONAL PROCEDURES

A StRING OF CONDITIONAL PROCEDURES MAY EITHER PRECEDE, OR BE INTERSPERSED AMONG, A
SERIES OF DUMP PROCEDURES. THE PURPOSE OF Co.NDITIONAL PROCEDURES IS TQ DETERMINE
WHEN OR IF THE DUMP PROCEDURES WHICH IMMEDIATELY FOLLOW ARE EFFECTIVE. A STRING OF
CUNDITIONAL PROCEDURES MAY BE STARTED BY EITHER THE X$IF o.R X$TALY STATEMENT • THE
DIAGNOSTIC SYSTEM Co.NTAINS AN lNTERNAL CONDITION SWITCH WHICH MAY BE ALTERED BY THE
EXECUTION OF THESE CONDITIONAL PROCEDURES. DUMP PROCEDURE CALLS IMMEDIATELY
FOLLOWING A CONDITIONAL PROCEDURE CALL WILL BE EXECUTED o.NLY IF THE PRECEDING

UP-4144
Rev.1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

17

SYSTEM

2
PAGE:

SECTION:

o
CONDITIONAL PROCEDURE HAS LEFT THE CONDITION SWITCH SET ON •
17.2.3.1.

THE X$IF PROCEDURE

THE X$IF PROCEDURE BY DEFINITION BEGINS A STRING OF DIAGNOSTIC CALLS, THE
CONDITION SWITCH IS SET TO TRUE OR FALSE DEPENDING ON THE CURRENT VALUE OF THE FIRST
~OGICAL EXPRESSION (OPERAND 'REL' OPERAND) IN THE XSIF PROCEDURE CALL.
IT IS CALLED
BY:

IN WHICH M IS A ~OCATION IN CORE OR CONTROL MEMORY, X IS AN INDEX REGISTER
DESIGNATION, AND J IS A 'J FIELD' SPECIFYING ANY DESIRED PARTIAL WORD, OMITTED
FIELDS ARE TREATED AS ZERO. LITERALS MAY BE USED FOR M, IF DESIRED, AND INDIRECT
ADDRESSING IS ALLOWED; HOWEVER, THERE IS NO PROVISION FOR INDEX INCREMENTATION.
THE 'REL' FIELD SPECIFIES THE RELATION BETWEEN THE TWO OPERANDS TO BE TESTED.
CODES ARE:
CODE
MEANING
,GT'
GREATER THAN
.LT'
LESS THAN
.EQ'
EQUAL TO
'GE'
GREATER THAN OR EQUAL TO
.LE'
LESS THAN OR EQUAL TO
.NE'
NOT EQUAL

ALLOWAB~E

17.2.3.2.

THE

THE X$AND PROCEDURE

THE X$AND PROCEDURE HAS PRECISELY THE SAME FORMAT AND FUNCTION AS DOES THE XSIF
PROCEDURE, EXCEPT THAT THE CONDITION SWITCH IS SET 'ON' IF, AND ONLY IF, IT IS
ALREADY .ON' AND IF THE CURRENT CONDITION IS 'TRUE,.
17.2.3.3.

THE X$OR PROCEDURE

THE X$OR PROCEDURE HAS PRECISELY THE SAME FORMAT AS THE X$IF AND XSAND PROCEDURES,
EXCEPT THAT THE CONDITION SWITCH IS SET 'ON' IF IT IS ALREADY 'ON' AND/OR IF THE
CURRENT CONDITION IS 'TRUE'.
17.2.3.4.

THE X$TALY PROCEDURE

THE X$TALY PROCEDURE SERVES TO SET THE CONDITION SWITCH 'OFF' IF CERTAIN CRITERIA
ARE NOT SATISFIED. IT IS CALLED BY:
X$TALY

START~

UNTIL, EVERY

EVERY TIME A X$TALY PROCEDURE CALL IS EXECUTED WHILE THE CONDITION SWITCH IS .ON',
THE FOLLOWING TESTS ARE MADE TO A FIELD 'Z' WITHIN THE GENERATED CODE: IF
[START(Z(UNTILJ ANO [Z-START/EVERYJ PRODUCES A ZERO REMAINDER, THE CONDITION SWITCH
IS LEFT 'ON' AND THE FIELD 'Z' IS INCREMENTED BY ONE, IF BOTH OF THE ABOVE
CONDITIONS DO NOT HOLD, THE CONDITION SWITCH IS SET 'OFF.' DUMP PROCEDURES
IMMEDIATELY FOLLOWING THE X$TALY PROCEDURE WILL NOT BE EXECUTED IF THE CONDITION
SwITCH HAS BEEN SET 'OFF'.
17.2.3.5.

EXAr.iP~E.

AN EXAMPLE OF THE USE OF CONDITIONAL PROCEDURES WILL INDICATE HOW THE CONDITION
SwITCH IS SET. NOTE THAT IF DUMP PROCEDURES (DESCRIBED IN NEXT SECTION) ARE
INTERSPERSED WITH CONDITIONALS, ~HEY WILL BE EFFECTIVE IF AND ONLY IF THE CONDITION
SWITCH IS SET TO 'TRUE' AT THE TIME THEY. ARE ENTERED AND WILL HAVE NO EFFECT ON THE
SETTING OF THE CONDITION SWITCH.
ASSUME THAT A PROGRAM CONTAINS THE VARIABLe:sX, Y,AND Z, AND THE CONSTANTS A, B,
AND C. ALSO ASSUME THAT THE FOLLOWING PROCEDURES ARE EXECUTED SEQUENTIALLY (WITH OR
wITHOUT OTHER PROCEDURES OR INSTRUCTIONS INTERSPERSED) AND THAT THEY ARE PART OF A

C
.

~~~~-.-.-----------

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS

17

REFERENCE

SECTION:

f
LOOP WHICH WILL BE EXECUTED 4000 TIMES.
WITH o AND ENDING WITH 3999,
EXECUTION LOOP COUNT:

WE COUNT THE NUMBER OF EXECUTIONS STARTING

0

1

99

100

PROCEDURE: ( 1) X$IF

X 'EG' A

FALSE

FALSE

FALSE

FALSE

(2) X$OR

X 'LT' Z

TRUE

TRUE

TRUE

TRUE

(3) X$AND

Y 'GT' B

FALSE

FALSE

FALSE

FALSE

(1+)

X$OR

Y 'NE' Z

TRUE

TRUE

TRUE

TRUE

(5)

X$OR

A 'EQ' 90

TRUE

TRUE

TRUE

TRUE

(6)

X$OR

A 'EQ' 'A'

TRUE

TRUE

TRUE

TRUE

(7) X$TALY 0,4000,100

TRUE

FALSE

FALSE

TRUE

IF X. Y, AND Z HAVE VALUES OF 78, 80, AND 88 RESPECTIVELY, AND A, B, AND C HAVE
VALUES OF 'A' (FIELDATA CHARACTER), 180 AND OCTAL 040 RESPECTIVELY, THEN THE
CONDITION SWITCH WILL HAVE THE ABOVE VALUES (TRUE OR FALSE) AFTER EXECUTION OF THE
INDICATED PROCEDURE. NOTE: IF THE CONDITION SWITCH IS SET TO 'FALSE' WHEN THE
X$TALY PROCEDURE IS ENTERED, THE COUNTER IS NOT INCREMENTED AND RETURN IS MADE TO
USER.
THE DUMP PROCEDURES

17.2.4.

THE DUMP PROCEDURES GENERATE CALLING SEGUENCES WHICH OUTPUT THE INFORMATION
COMPRISING THE DESIRED DUMPS. THE ACTUAL OUTPUT WHILE THE OB~ECT PROGRAM IS RUNNING
IS TO A SPECIAL DIAGNOSTIC FILE. WHEN A PROGRAM TERMINATES, THIS DUMP INFORMATION IS
READ BA9K, EDITED, AND PRINTED. IF NO CONDITIONAL PROCEDURES ARE USED, THE DUMP
PROCEDuRES WILL ALWAYS PRODUCE OUTPUT AS THE DUMP PROCEDURES STANDING ALONE ALWAYS
PRODUCE OU·TPUT.
17.2.4.1.

THE X$MESG PROCEDURE

THE X$MESG WILL PRODUCE A LINE OF UP TO 120 CHARACTERS ON THE OUTPUT LISTINGIF THE
CONDITION SWITCH IS SET TO 'ON'. THE ALPHANUMERIC LINE IT PRODUCES IMMEDIATELY
FOLLOWS THE PROCEDURE REFERENCE. IT IS CALLED BY:
X$MESG
LENGTH
'DIAGNOSTIC MESSAGE'
THE FIELD 'LENGTH' SPECIFIES THE NUMBER OF WORDS IN THE MESSAGE THAT FOLLOWS' THE
FIELD .DIAGNOSTIC MESSAGE' CONSISTS OF ANY ALPHANUMERIC STRING ENCLOSED IN QUOTATION
MARKS, AND WILL BE PRINTED EXACTLY AS ASSEMBLED. THIS PROCEDURE PERMITS A PROGRAMMER
TO IDENTY THE CONDITIONS WHICH CAUSED A GIVEN DUMP BY HIS OWN SUITABLE MESSAGE.
17.2.4.2.

THE X$CORE PROCEDURE

THE X$CORE PROCEDURE PRODUCES A PRINTOUT OF CORE MEMORY, PROVIDED THAT THE
CONDI1ION SWITCH IS SET TO 'ON'. IT IS CALLED BY:
X$CORE

START, LENGTH, 'FORMAT', INDEX REGISTER

WHICH RESULTS IN 'LENGTH. NUMBER OF CORE LOCATIONS, BEGINNING AT CORE-LOCATION
'START+INOEX' BEING EDITED AND PRINTEO ACCORDING TO 'FORMAT'. THE FORMAT AND INDEX
FIELDS ARE OPTIONAL. THE FORMAT FIELD, IF PRESENT, CONTAINS A SINGLE LETTER ENCLOSED
IN GUOTATION MARKS, SUCH AS A,D,E,F,I,O, OR S FOR STANDARD FORMATS, OR MAY CONTAIN
SOME OTHER LETTER FOR A USER DEFINED FORMAT. IF A FORMAT IS NOT SPECIFIED '0' FORMAT
IS USED. SEE SECTION 17.2.5.1., FORMAT SPECIFICATION PROCEDURE. THE INDEX FIELD, IF
PRESENT GIVES THE NUMBER OF AN INDEX REGISTER TO BE USED TO MODIFY THE 'START'
ADDRESS TO OBTAIN THE EFFECTIVE DUMP ADDRESS. THE LEGAL VALUES FOR THE INDEX FIELD

3
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

SYSTEM

EXEC B

PROGRAMMERS REFERENCE

4

17.
SECTION:

PAGE:

c
AKE 1 THHV 15 (Xl THRU Xl5).

THE MAXIMUM ALLOwABLE 'LENGTH' VALUE IS 037777.

THE XSDUMP PROCEDURE

17.2.4.3,

TflE XSDUMP ~ROCEDURE PRINTS OUT THE PROGRAM'S ENVIRONMENTI THE X, A, AND/OR R
IF DESIRED; AND A PRINT-OUT OF CORE MEMORY, PROVIDED THAT THE CONDITION
SwITCH IS SET TO 'ON'. IT IS CALLtD BY:
.

R~GISTEHS.

START, LENGTH, 'FORMAT', 'REGISTERS', INDEX REG
WhICH RESULTS IN A PRINT-OUT OF THE CARRY AND OVERFLO~ CONDITIONS FOLLOWED BY
CUNTENTS OF THE SELECTEU HEGISTERS PRINTED IN OCTAL. THE 'REGISTERS' ARE SPECIFIED
UY THE ltTTEH5 'X', 'A' AND .R, IN ANY COM8INATION OR PERMUTATION. THE REGISTER
UUMP, IF REQUESTE0, IS FOLLOWED BY A CORE DUMP OF ,lENGTH' NUMBER OF CORE LOCATIONS,
~~GINNING AT CO~E-LOCATION 'START + INDEX' EDITED AND PRINTED ACCORDING TO THE
'~ORMAT'.
THE ',NOEX' FIELD, IF PRESENT, GIVES THE NUMBER OF AN INDEX REGISTER TO
USEU TO MOUIFY THE 'STAMT' ADDRESS TO OBTAIN THE EFFECTIVE DUMP ADDRESS. LEGAL INDEX
~lELU VALUES ARE 1 THRU 15.
ALL ~I~lUS AkE OPTIONALI IF 'START' IS A~SENT II START ADDRESS OF ZERO IS USED, IF
'LENGTH' IS ABSENT NO COHE DUMP WILL BE EXECUTED, AND IF 'FORMAT' IS ABSENT A
STANUARD OCTAL CORE DUMP dIll RESULT.
THE fl.lf\XIMl)i.i

llil

VIILUE OF 'lENGTH' IS

037777 •

THE X'C~ PROCEUUREPHUOUCES THE CALLING SEJUENCE FOR A 'CHANGED WORD' PRINTOUT OF
SPECIFIED AREA OF CORE MEMoRY , PROVIUING THAT THE CONDITION SWITCH IS 'ON, • THE

CALLI~G

SE~UENCE

15 :

TtilS CAUSES THE NUMBlH OF WORDS AS SPECIFIED BY THE LENGTH PARAMETER , BEGINNING
THE lOCI\TlOll SeECIFlEO R'f THE START PM~AMETEH TO BE SEARCHED FOR WORDS THAT HAVE
CliANGED SlI,ICE nit:. PREVIOUS CALL TO X$CI"J • THE CHANGED WORDS, IF ANY, ARE THEN
lUlTED liND PRli~TEu ACCORUING TO THE SPECIFIED FORMAT • ONLY STANDARD FORMATS MAY BE
S~ECIFIEU ( SECTION 17.2.~.1) • AND IT IS NOT POSSIBLE TO REOEFINE FOR CHANGED WORD
UYi~AMIC DUMPS ANY UF THE STANUARD FORMATS • IF A FORMAT IS SPECIFIED AS OTHER THAN A
STANDAHO ONE AN OCTAL DUMP RESULTS.
1\1

THE Flk~T REQUEST FOH A CHANGED ~ORD DYNAMIC DUMP OF A SPECIFIC AREA WILL-RESULT
THE t.LJlTING AND PRIIHH~G OF ALL WOHDS IN THAT AREA. ALTHOUGH THERE IS NO LIMIT TO
THE NU~U[k OF CALLS ON X$CW , THE NUMBER OF SEPAHATE AREAS WHICH MAY BE DUMPED IS
Ht.STHICTEL TO FIVe: • W TliE EVENT THE USEh SPeCIFIES f'o;ORE THAN FIVE AHEAS THOSE CALLS
At-TEH THE STli •.ILL BE IGi~ORED • THE 'START • ADLiHESS DETERMINES THE UI~IQUENESS OF ONE
I\t,CA FtWi·j HiE f!EXr •
!hj

17.2.4.~.

IHE X'j,Ti-If'>E PROCEDLJRE

TH~ X$TAPE PI{OCEDUHE PRODUCES A. PRINT-OUT OF THAT blOCK OF MAGNETIC TAPE JUST
Pi\lOR TO THE CUHHl:.ilT POSITION OF THE SPF.:CIFI[ft FILE-NAME, PROVIDED THAT THE CONDITION
S.1I rCtl IS SET ro 'ONI.
THE UIHSE;WO OUMPEu Is ALWAYS REPOSITIONED AFTER THE DUMP IS
M/\L)E; If- THE ut,.lSl:.HVO IS ':>051 TIONED ~T THe: H[GINNING OF A TAPE, NO DU,"1P WILL

U('CUf<.

IT IS CI\LLLD 1:lY :
kill MJE

MnJHESS OF EXEC I/O PACKET, • F0fd,1AT.

X'J, T/\I'E

AUDRESS UF FILE CONTROL TAillE, • FORMAT'

O~

THE 8l0CK OF GATA JUST P~IOR TO TilE CURRENT POSITION OF THE TAPE IS EDITED AND
PidNTE0 AC~OfmUJG TO 'FOHf<1AT'.

UP-4144

UNIVAC

Rev.)

110a

EXEC B

OPERATING

SYSTEM

PROGRAMMERS

17

REFERENCE

SECTION:

TIlt X$TAPE PROCEDURE REQUIRES THAT A MEMORY AREA OF SUFFICIENT SIZE BE AVAILABLE
IIITO WHICH THE BLOCK OF TAPE MAY BE READ. THIS BUFFER IS PROVIDED BY THE X$BUFR
PKOCEDUNE UESCRIBED IN SECTION 17.2.5.2. IF THE TAPE BLOCK IS LONGER THAN THE BUFFER
P~OVIUEU, ONLy THAT INFORMATION WHICH CAN BE fiELD IN THE BUFFER WILL BE PRINTED.
THEHE IVlLL NOT dE I\fH DIAGtJOSTIC r",ESSAGE FOR TRUNCATED BLOCKS.
1 7 • 2.4.6.

THE Xq;ORUM PROCEDURE

THE X$UHUM PROCEUURE PROVIDES A PRINT-OUT OF A PORTION OF MASS STORAGE MEMORY,
PKOVIDEO THAT THE CONDITION SWITCH IS SET TO 'ON'. IT IS CALLED BY:
X1>URUM

ADOR EXEC 1/0 PACKET,LOCN,LENGTH,'FORMAT,

>'>'tilCH HESULTS

THE 'LENGTH, - SPECIFIED NUMiH::R OF WORDS FROM THE
IN EXEC 110 PACKET, BEGli~NING WITH RELATIVE DRUM ADDRESS FOUND
Iij THE COR[ LOCATION 'LOCN' BEING EDITED AND PRINTED ACCORDING TO ,FORMAT'. THE
X,URUM PROCEDURE REQUIRES A CORE DUFFER INTO ~HICH INFORMATION FROM DRUM MAY BE READ,
WHILE A BLOCK OF UHUM STORAGE LARGER THAN THE SIZE OF THE BUFFER MAY BE DUMPED,
G~EATER EFFICIENCY WILL RESULT FROM PROVIDING A BUFFER SUFFICIENTLY LARGE TO HOLD ALL
Of THE DKUi\1 WFOR,YlATION REQUESTED AT ONE nr-1E.
li\l

'lNTEH~AL-FILE-NAME'

IF NO BUFFEH AHEA AT ALL IS PROVIDE:.D FOR THE X$TAPE AND X$DRlJM PROCEDURES, THESE
WILL NOT dE CARR lEU OUT; HOWEVER, THE SAME BUFFER AREA MAY BE USED FOR BOTH
Xi TAPE AND X$DRUM PROCEUURE CALLS.

OU~PS

WHEN IfJTERSPERSING CONDITIONAL PROCEDURES ~ITH DUMP PROCEDURES, THE SETTING OF THE
CONDlTION SWITCH REFLECTS ONLY THOSE CONDITIONALS WHICH HAVE BEEN PROCESSED AT THE
T11'-1E THE DUMP IS CALLED.

(

17.2.4.7.

fHE X$FILE PRUCEDURE

THE OIAGNOSTIC SYSTEM CAN INTERFACE WITH TilE ITEM 8UFFERING PACKAGE, IN ORDER TO
A SNAPSHOT WHENEVER A~ ITEM IS REAG FrIOM. OR WRITTEN TO, A PARTICULAR FILE.
TrlIS FACILITY IS NOT AVAILABLE WHEN USING INDEFINITELY LONG-SPANNED ITEMS. THE
Pf~OCE[)URE CALL:

P~OVIUE

X$FILE

FCB.

'Of~'.

'FOR;V)AT'

WILL CAUSE SUHSE~UENT ITE~S READ FROM, OR ~IIITTEN TO, THE FILE WHOSE FILE CONTROL
BLOCK IS AT 'FCH' TO HE WKITTt.. N I,'HO THE L,lAGJOSnC FILE AS A SNAPSHOT DUr-1P. THE
i-'t{OC!:.OUKE CALL:
X$FILE
~lLL

FCl'l, 'OFF'

Tt~MliJATE

SUCH SNAPSHOTS.

Feu IS THE

ADJR~SS

OF THE FILE CONTROL TABLE.

fHL X'hCREG PROCEDURE

1'1.2. 1+.7

Ht!:. X'hCr(lG PHOCt:!JUHE CALLS FUR A DlWP OF lJS[H5 CONTROL REGISTERS (PROVIDED THAT THE
C1ARK AND XSBACK PROCEOURES BEHAVE MUCH AS LEFT AND RIGHT PARENTHESES
SURROUNDING PORTIONS OF A PROGRAM WHICH ARE TO BE DUMPED ONLY IF TERMINATION OCCURS
BETWEEN THEM.
X$MARK AND XSBACK PAIRS MAY BE NESTED TO A DEPTH OF FIVE, THE TOTAL NUMBER OF
OCCURRENCES OF X$MARK AND XSBACK IS UNRESTRICTED. THE PROCEDURE CALLS ARE:
X$I'-lAt,K

X$BACK
THE xsON AND X$OFF PROCEDURES

17.2.~.4.

TWO PROCEDURES,. XSON AND X$OFF, ARE AVAILABLE FOR OVERALL CONTROL OF CALLS ON
L)EBUGGING PROCEQUHE5. wHENEVER A xsOFF IS IN CONTROL, ALL REFERENCES TO DEBUGGING
PkOC~OURES (EXCEPT XSON) ARE NULLIFIED.
REGARDLESS OF THE SETTING OF THE CONDITION
S.lTCH, NO OUTPUT WILL ~E MADE TO THE DIAGNOSTIC FILE, AFTER A X$ON IS ENCOUNTERED,
THE DEBUGGING PROCEDURES AGAIN BECOME ACTIVE. THE PROCEDURE CALLS ARE:
X~ON

X$OFF
THE CONOITION SWITCH IS INTERNAL TO THE DUMP
17.2,5.5.

~OUTINES

•

EXAf'JPLES.

PROCt'.OUHE:

$(2)
ALPHA
'i> (1)

RES

200

•

(1) X$rRMT 1,'0'
, (6014)'
(2)

XStiUFR

(3)

X$JI;jARK

(4)
(5)
(6)

HESULTS:

(1)

X$CORE
X$fJACK
X<£OFF
X$CORE
X$ON
X$CORE

ALPHA,200
ALPHA,200,'A'
ALPHA,200,'E'
ALPHA,200,.I'

THE STANDARD OCTAL FORMAT '0'
PRINT 6 OCTAL FIELDS PER LINE
APPROPIATEDATA IS WRITTEN ON
THE ABOVE ACTION IS EFFECTIVE
EDITOR PROCESSES THE RECORDED

HAS BEEN REDEFINED TO
INSTEAD OF 8. THE
THE DIAGNOSTIC FILE SO
WHEN THE DIAGNOSTIC
QYNAMIC DATA,

(2) PROVIdES THE DIAGNOSTIC SYSTEM WITH A 200 WORD
BUFFER FOR TAPE AND DRUM FILE DUMPS. FOR DRUM FILES
IT IS RECOMMENDED THAT THE BUFFER BE SOME MULTIPLE OF
28,THE LENGTH OF A FASTRAND SECTOR.

c

UP-4144
Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

PAGE:

(
(3) SAVES THE CURRENT LOCATION WHERE THE NEXT WRITE IS
TO BE MADE IN THE DIAGNOSTIC FILE.
R£SETS THE CURRENT LOCATION POINTER TO THE VALUE
SAVED BY THE MOST RECENT X$MARK ~~EFERENCf. RESULT IS
THAT ALL INTERVENING DUMp INFORMATION IS ERASED.
E.G. THE DATA RECORDED BY X$CORE ALPHA,200"A, HAS
BEEN DELETED.

(~)

(5) DISABLES ALL DIAGNOSTIC SYSTEM P~OCEDURES EXCEPT X$ON
SO THE X$CORE ALPHA,200,'E' CALL IS IGNORED.
(6) ENABLES DIAGNOSTIC PROCEDURES, XSCORE ALPHA,200,'I'
CALL IS IN EFFECT AND REQUESTED DUMP RECORDED.
17.2.6.

ASYNCRONOUS ACTIVITY DIAGNOSTIC CALLS

EACH DIAGNOSTIC ROUTINE THAT IS PART OF THE USER'S PROGRAM IS PROCESSED SERIALLY.
CARE SHOULO BE OBSERVED IN USING THE X$ON AND SUBPROGRAM ACTIVITY SHOULD SET THE
SWITCH OFF, IT WILL BE OFF FOR ALL ~UBPROGRAM ACTIVITIES.
A COMMON EXIT IN THE DYNAMIC DIAGNOSTIC LIBRARY ROUTINE WILL LOOK AHEAD TO SEE IF
THE NEXT lNSTRUCTION IS A CALL TO THE DIAGOSTIC SYSTEM, IF TRUE, A LOCK-OUT
CONDITION WILL REMAIN IN EFFECT UNTIL THE SERIES OF CALLS ON THE SYSTEM IS BROKEN.
THIS ASSURES THE USER THAT A SERIES OF CALLS WILL NOT BE INTERRUPTED INADVERTENTLY BY
ONE OF THE OTHER SUBPROGRAM ACTIVITIES.

(
17.3.1.

GEtJERAL

A POST-MORTEM DUMP EXECUTIVE CONTROL STATEMENT MAY BE USED TO DUMP CORE MEMORY
FOLLOWING THE EXECUTION OF A TASK. DUMPS MAY BE MADE OF OVERLAY SEGMENTS, ELEMENTS,
OR SPECIFIED PARTS OF ELEMENTS, AS LONG AS THEY WERE CURRENTLy IN CORE AT THE TIME
rHE ROUTINE TERMINATED. SEVERAL OPTIONS ARE AVAILABLE FOR OUTPUT FORMATTING AND FOR
SELECTING THE CORE AREAS TO BE DUMPED.
THE GENERAL FORM OF THE CONTROL STATEMENT IS:
folPMD, OPT IONS

SPECIFICATIONS

IF NO INFORMATION WAS SAVED BY THE SYSTEM WHEN THE PREVIOUS EXECUTION TERMINATED,
NO DUMPS ARE POSSIBLE.- THIS CONDITION MAY BE CAUSED BY A 'Z. OPTION GIVEN TO THE
COLLECTOR WHEN THE PROG~AM WAS CONSTRUCTED, By A MISPLACED PMD CARD, OR BY CERTAIN
RARE ERROR CONDITIONS. IN THE EVENT THAT NO DUMP IS AVAILABLE, A MESSAGE IS
Pi\OUUCED.
THE WPMJ STATEMENTS MUST FOLLOW THE QXQT STATEMENT OF THE PROGRAM THAT HAS
TlRMWATED IN ORDER TO \3E HONORED.
ONLY
PURE DATA AND THE CONDITIONAL STATEMENTS I Q5ETC, QJUMP, AND gTEST INTERVENE.
FOLLOWING IS AN EXAMPLE:
i~O

1
2

(

10
11

12

•

STATEMENT

------------------lolXQT
PKOGX
DATA

DATA
[",TEST
fol,JUMP

TE/6/53
;5

9

17
SECTION:

THE

UP-4144
Rev.1

UNIVAC

1108

EXEC B

13
14
15

fiilSETC
fiilpr,lD
fiilXQT

.

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

10

17
SECTION:

PAGE:

6/S4

ELEMENT-1,ELEMENT-2
PROGY

IF PROGX TERMINATES BEFORE PROCESSING ALL OF THE DATA STATEMENTS THAT FOLLOW THE
fiilXQT AND S3 OF THE cONDITION WORD HAS A VALUE OF 6, 54 OF tHE CONDITION WORD WILL BE
SET TO 6 AND STATEMENT NUMAERS 14,15 WILL BE HONORED FOR PROCESSING. WHEN STATEMENT
16 IS ENCOUNTERED, THE RUN WILL BE TERMINATED IF IT IS NOT DEMAND.

OPTIONS ARE SELECTED THROUGH USE OF OPTION LETTERS PUNCHED INTO THE fiilPMD CARD.
THE OPTIONS FALL INTO THE FOLLOWING CLASSES: (1) GENERAL, (2) SPECIAL, (3) OPTIONS
WITH SPECIALS, ANU (4) BLANK

TtlE GENERAL OPTIONS MAY BE USED WITH ANY OTHERS IN A fiilPMD STATEMENT.

THEY ARE:

(1) 'E' OPTION: IF THE LETTER E IS PLACED IN THE OPTIONS
FIELD, THE fiilPMD STATEMENT WILL BE PROCESSED ONLY WHEN
THE PREVIOUS ROUTINE TERMINATED IN ERROR.
(2) 'C' OPTION: THE 'C' OPTION WILL CAUSE A DUMP OF THE
WORDS THAT WERE CHANGED DURING THE EXECUTION OF THE
ALLOCATED PROGRAM FOR THE ARE~ OF CORE PRESCRIBED BY
THE SPECIFICATIONS PORTION OF THE PMD STATEMENT.
(3) 'B' OPTION: AFTER PROCESSING THE REST OF THE PMD
STATEMENT, THIS OPTION WILL CAUSE AN OCTAL DUMP OF ALL
OF BLANK COMMON STORAGE AREA. IF USED WITH THE 'C'
OPTION, THE ,C, OPTION WILL BE IGNORED FOR BLANK
cor-llrv10N STORAGE.
(4)

17.3.2.2.

'P' OPTION: THE LETTER 'P' USED IN CONJUNCTION WITH
ANY OF THE OTHER OPTIONS KNOWN TO PMD WILL CAUSE AN
OCTAL DUMp OF THE PCT BLOCK(S) USED BY THE RUN TO BE
PRINTED PRECEEDING THE DUMP OF THE PROGRAM • THE
BLOCKS ARE DUMPED IN OCTAL FORMAT • THE SEGMENT LOAD
TABLES (IF ANY EXIST) ARE ALSO DUMPED IN OCTAL FORMAT
IF THE ,p, OPTION IS SPECIFIED •
SPECIAL OPTIONS

ONLY ONE SPECIAL OPTIO~ SHOULD BE USED ON A SINGLE PMD STATEMENT. IF MORE THAN
THAN ONE SPECIAL OPTION IS USED, THE SPECIAL 'A' OpTION 'A' IS ASSUMED. ALL SPECIAL
OPTIONS REQUIRE THE SPECIFICATIONS FIELD DESCRIBED BELOW. IF NO SPECIAL OPTION IS
SUPPLIED, THE 'BLANK' OPTION RULES WILL BE APPLIED. THE SPECIFICATIONS FIELD FOR THE
SPECIAL OPTIONS TAKES THE FORM OF A LIST OF ELEMENT OR SEGMENT NAMES:

EACH NAMED ENTHY WILL BE DUMPED IN OCTAL FORMAT AND IN ORDER OF ALLOCATION.
THE SPECIFICATION FIELD IS BLANK, ALL ELEMENTS IN MEMORY AT TERMINATION OF THE
PREVIOUS ROUTINE WILL BE DUMPED. THESE SPECIAL OPTIONS ARE:
(1) 'A' OPTION: AN 'A' OPTION WILL PRODUCE A DUMP OF ALL
~EMORY SPECIFIED IN EACH ELEMENT OR SEGMENT NAMED IN
THE SPECIFICATION LIST.
(2) 'D' OPTION: A '0' OPTION WILL PRODUCE A DUMP OF THE
D-BAt4K PORTION OF EACH ELEMENT OR SEGMENT NAMED IN THE

IF

c

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SECTION:

SPECIFICATION LIST.
(3) 'I' OPTION: AN ,I' OPTION wILL PRODUCE A DUMP OF ALL
I-BANK PORTIONS OF EACH ELEMENT OR SEGMENT NAMED IN THE
SPECIFICATION LIST.
17.3.2.3.

OPTIONS USED WITH SPECIAL OPTIONS

(4) 'X' OPTION: WHEN USED IN CONJUNCTION WITH THE 'A',
'I', OR '0' OPTIONS, THE 'X' OPTION HAS AN EXCEPT
EFFECT. ALL ACTIVE ELEMENTS WIL~ BE DUMPED EXCEPT
THOSE NAMED IN THE SPECIFICATION LIST, AND THOSE
BELONGING TO THE SEGMENTS NAMED IN THE SPECIFICATION
LIST.
(5) 'L' OPTION:

WHEN USED WITH THE 'A', 'I', OR '0'
OPTIONS, THE L OPTION, PRESENT, CAUSES A DUMP TO BE
TAKEN OF ANy ACTIVE ELEMENTS FROM THE SYSTEM LIBRARY.
THE 'L' OPTION WHEN USED ALON! WILL CAUSE THE ACTIVE
LIBRARY ELEMENTS TO BE DUMPED.

17.3.2.4.

THE 'BLANK' OPTION

IF NO SPECIAL OPTIONS ARE NAMED ON THE PMD CARD, THE SPECIFICATION FIELD MUST
FOLLOW THE FORM:
NAME, START, LENGTH, FORMAT
THIS OPTION ALLOWS THE USER TO DUMP INFORMATION UNDER A SPECIFIC FORMAT WITHOUT
OUTPUTTING EXCESSIVE AMOUNTS OF UNNECESSARY MATERIAL.
THE 'NAME' FIELD IS THAT OF AN ELEMENT AND MUST BE PRESENT.
THE 'START' FIELD MUST BE OF THE FORM:
N/M .
WHERE ,M' REPRESENTS TH~ LOCATION COUNTER OF THE ELEMENT TO BE DUMPED, AND 'N'
REPRESENTS AN ADDRESS, RELATIVE TO THE BEGINNING OF 1M', AT WHICH DUMPING SHOULD
BEGIN. IF 'M' OR 'N' IS OMITTED, A ZERO IS ASSUMED TO BE ITS RESPECTIVE VALUE,
THE 'LENGTH' FIELD MUST BE THE NUMBER OF WORDS TO BE DUMPED. IF OMITTED, THE
6E ASSUMED TO BE ALL OF LOCATION COUNTER ,M' OF THE SPECIFIED ELEMENT.

~ENGTH WIL~

STANDARD 'D','S' AND US~R DEFINED FORMATS ARE NOT APPLICABLE FOR CHANGED WORD
DUMPS, FOR ALL OTHER CASES THE USER MAY SUPPLy HIS OWN FORTRAN TYPE FORMATS (ENCLOSED
IN PARENTHESES) OR USE THE SYSTEM DEFINED FORMATS PREVIOUSLY MENTIONED. THE
17.3.3

EXAMPLES
fj,jPMD

RESULTS IN AN OCTAL DUMP OF ALL ACTIVE (ALLOCATED IN CORE) SEGMENTS OF A USERS
PHOGRAM • NO BLANK COMMON WILL BE DUMPED •
gPMD,EAXL ELEMENT-NAME-1, ELEMENT-NAME-2
RESULTS IN AN OCTAL DUMP OF ALL ACTIVE ELEMENTS EXCEPT ELEMENTNAME-l, ELEMENT-NAME-2,
AND SYSTEM LIBRARY ELEMENTS ON AN ERROR TERMINATION.
gPMD,BOI

(

11

17

SYSTEM

PROGRAMMERS REFERENCE

SEGMENT-NAME

RESULTS IN AN OCTAL DUMP OF SEGMENT-NAME (IF ACTIVE) AND BLANK COMMON AREA OF CORE
STORAGE.

PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

12

17

SYSTEM

PROGRAMMERS REFERENCE

SECTION:

PAGE:

QPMD,EBCD ELEMENT-NAME
RESULTS IN AN OCTAL DUMP OF CHANGED ,WORDS IN DBANK OF ELEMENTNAME (IF ACTIVE) AND
BLANK COMMON.
~PMD

ALPHA,lOO/3,50,A

HESUL TS IN A 50 WORD ALPHANUMERIC FORr.,AT DUMP OF ELEMENT ALPHA (IF ACTIVE) UNDER
.CONTROL OF LOCATION COUNTER 3 BEGINNING WITH RELATIVE ADDRESS 100 OF LOCATION COUNTER
3.

r.i)PMD,B
17.4.

• DUMP ALL OF PROGRAM INCLUDING BLANK COMMON.

PMO AND DYNAMIC DUMP CORRELATION

~ECAUSE PMD AND THE DYNAMIC DUMPS WRITE INFORMATION INTO THE SAME FILE ( WHICH IS
KNOWN TO THE SYSTEM AND DYNAMICALLY ASSIGNED) ) IT IS NECESSARY THEY BE AWARE OF EACH
OTHERS EXISTENCE. ABSENCE OF A PARTICULAR FORMAT IMPLIES At-j OCTAL DUMP. DYNAMIC
DUMPS WILL PERFORM SEVERAL CHECKS TO ENSURE THEY NOT BEEN DESTROYED AND DO NOT
PRODUCE FALSE DATA •

IN ORDER TO ACCOMPLISH THIS IT MAY REQUIRE A CERTAIN AMOUNT OF COOPERATION FROM
THE USER • IT 1S SUGGESTED THAT THE USER SET UP AN ERROR INTERUPT ANALYSIS ROUTINE TO
O~TERMINE IF A R£~UEST FOR A DUMP RESULTED IN ACCESSING A CORE LOCATION OUTSIDE THE
USERS AREA • IN THE EVENT THIS ACCESS OCCURS A GUARD MODE INTERUPT RESULTS AND THE
/JUMP ROUTINE CAr~NOT DETEf~MINE THE USERS CORE LIMITS AT ALL TIMES • THIS IS NOT A
R£QUIREMENT FOR SUCCESSFUL UTILIZATION OF DYNAMIC DUMPS , BUT IS INTENDED TO ASSIST
IN SATISFACTORY PROGRAM TESTING •
THE

THE /JYNAMIC DUMPS MAKE SEVERAL CHECKS FOR 'REASONABLENESS',
~ORRECT FILE , AND NOT DUMPING PAST THE FILE LIMIT ) •

E.G. DUMPING INTO

THE FILE LIMIT IS AN INSTALLATION VARIABLE AND IS SPECIFIED AT SYSTEM GENERATION
TIME • THE PROGRAM TERMINATION ROUTINE WILL ( IF A QPMD IMAGE OCCURS ) DUMP THE
COMPLETED PROGRAM AT A GIVEN SECTOR ADDRESS WHICH IS THE ADDRESS SPECIFIED AT
GLNERATION TIME • THE CONSTANT THEN IS THE LENGTH OF THE DYNAMIC DUMP FILE • IN THE
EVENT TfiE DYNAMIC PORTION OF THE DIAGNOSTIC FILE IS FULL A MESSAGE FROM THE DUMP
ROUTINES IS PRODUCED AND PRINTED WHEN THE DUMPS ARE EDITED , NO MORE DUMPS WILL BE
THANSFERRED TO THE DIAGNOSTIC FILE, HOWEVER, THE CALLS WILL BE HONORED AS WILL A CALL
Oi~ pr"lD •

·"·'.·
C
~

UP-4144
Rev. 1

18.

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM"

18
SECTION:

SYSTEM SETUP

18.1.

18.1.1.

1108 EXECUTIVE SYSTEM GENERATION

GENERAL

THE SYSTEM GENERAJION PROGRAM PROVIDES EACH INSTALLATION WITH A MEANS OF
DESCHIBING THE MACHINE CONFIGURATION AND OPERATING SYSTEM FEATURES IT DESIRES IN SUCH
A MANNER THAT AN OPERATING SYSTEM IS PRODUCED TAILORED SPECIFICALLY TO THE
"
INSTALLATION'S PARTICULAR HARDWARE CONFIGURATION AND DATA PROCESSING NEEDS. THE
SYSTEM GENERATION ROUTINE ACCEPTS A CONTROL LANGUAGE WHICH DESCRIBES THE
CONFIGURATION OF THE SITE. IT ALSO ACCEPTS INSTALLATION MODIFICATIONS AND ADDITIONS,
UNIVAC SUPPLIED UPDATES TO THE .SYSTEM, AND PARAMETERS INDICATING THE DESIRED OUTPUTS
OF THE GENERATION RUN. THE ROUTINE THEN GENERATES A RUN WHICH PERFORMS THE REQUIRED
SYSTEM GENERATION AND UPDATING. iNPUT TO THE RUN ARE THE MASTER PROGRAM FILES OF THE
SYSTEM COMPONENTS. THE OUTPUTS ARE UPDATED MASTER PROGRAM FILES, AN OPERABLE SYSTEM
TAPE. AND A LISTING OF .THE UPDATING RUN.
MAINTENANCE OF THE 1108 SOFTWARE SYSTEflil IS EFFEcTED THROUGH THE USE OF THE SYSTEM
GENERATION PROGRAM. NORMALLY, ALL CHANGES ARE PREPARED BY UNIVAC AND FORWARDED TO
EACH INSTALLATION. THESE CHANGES WILL INCLUDE THE NECESSARY UPDATE STATEMENTS AND
SYMBOLIC CORRECTIONS. ALL PROGRAMS AFFECTED BY THE CHANGES ARE RE-ASSEMBLED AND
RE-ALLOCATED. OUTPUT OPTIONS ARE THE SAME AS FOR NORMAL SYSTEM GENERATION. ALL
HISTORICAL INFORMATION (FILE DIRECTORIES, ETC.) IS RETAINED WHENEVER AN UPDATE OF THE
SYSTEM IS PERFORMED; HENCE, AN UPDATE IS NOT A COMPLETE REGENERATION OF THE SYSTEM.
THE SYSTEM GENERATION PROGRAM WILL ALLOW FOR MAINTENANCE OF THE SYSTEM IN THE FACE OF
AUDITIONS MADE TO THE SYSTEM BY A PARTICULAR INSTALLATION. FOR ALL INSTALLATIONS THE
SAME DECK DISTRIBUTED BY UNIVAC WILL SUFFICE REGARDLESS OF CURRENT SYSTEM
CONFIGURATION.
18.1.2.

PROCEDURES

THE SYSTEM GENERATION ROUTINE (SGR) CONSTRUCTS AN ORDERED RUN FOR THE UPDATING OF
A SYSTEM.S SYMBOLIC ELEMENTS (SrSTEM LIBRARY) AND FOR THE CONSTRUCTION OF AN OPERABLE
SYSTEM TAPE, FROM A SET OF PARAMETER CARDS (SYSTEM GENERATION STATEMENTS - SGS'S), A
SKELETON CORRECTION DECK, UNIVAC CORRECTIONS, AND USER'S CORRECTIONS. UNIVAC
PROVIDES THE SGR WITH THE SKELETON CORRECTION DECK. THIS CORRECTION DECK CONTAINS
INFORMATION RELATING THE SGS'S TO THE CORRECTIONS NECESSARY TO AFFECT THOSE CHANGES
DESCRIBED ON THE SG5'5. UNIVAC CORRECTIONS WILL BE ENTERED IN THE SYSTEM LIBRARY, AS
OPPOSED TO USER CORRECTIONS WHICH ONLY AFFECT THE OPERABLE SYSTEM TAPE~
SYSTEM GENEHATION STATEMENTS (SGS'S) ARE COMPRISED OF ANY NUMSER;:OF FIELDS WHICH
MAY BE COMPRISED OF ANY NUMAER OF SUB-FIELDS. "A SUB-FIELD IS A STRING OF 18 OR FEWER
CHARACTERS NOT CONTAINING A SPACE. COMMA, RIGHT BRACKET, LEFT'BRA~KET, RIGHT
PARENTHESIS, LEFT PARENTHESIS, PLUS SIGN, MI~US SIGN, OR EQUAL. SIGN. NOTE, THE FIRST
FIELD NEED NOT START IN COLUMN 1.
""
A STATEMENT MAY BE COf~TINUED ON THE FOLLOWING CARD BY PLACING A SEMI-COLON
THE LAST SPECIFICATION FIELD.

~OLLOWING

THE SGS CARD fILE MAY BE FOLLOWED BY A FILE OF UNIVAC CORRECTIONS (PERMANENT
CURRECTIONS) AND A CARD FILE OF USER CORRECTIONS (TEMPORARY CORRECTIONS). THE
CORRECTIONS ARE OF THE FORM DESCRIBED IN SECTION 5.6.3. ALL CORRECTIONS TO AN
ELEMENT MUST BE GROUPED, ORDERED, AND PRECEDED BY A CARD WITH AN,ASTE~ISK IN COLUMN
ONE AND THE NAME ANO VERSION OF THE ELEMENT TO WHICH THE CORRECT[ONS ApPLY; IN THE
SteOND AND THIRD FIELDS. USER CORRECTIONS"WILL BE REPRODUCED. WITH UPDATED LINE
NUMBERS RESULTING FROM UNIVAC ADDITIONS OR DELETIONS.'
.

1
PAGE:

UNIVAC 1108 OPERATING

JP-4144
Rev. 1

EXEC B

18.1.3.

SYSTEM

18

PROGRAMMERS REFERENCE

SECTION:

SYSTEM GENERATION STATEMENTS

ACCOUNT PRIORITY AND DEADLINE
THE ACCOUNT STATEMENT IS USED TO SPECIFy THE LIMITATIONS
IMPOSED ON A GIVEN ACCOUNT NUMBER. THIS STATEMENT IS OF THE
FORM:
ACCOUNT N PRIORITY P,Q DEADLINE A REAL-TIME A
wHERE -N IS THE ACCOUNT NUMBER
-P IS THE HIGHEST PRIORITY A RUN WITH THE ACCOUNT
NUMBER N MAY TAKE.
'A'-'Z'
-Q IS THE PRIORITY USED WHEN NONE HAS BEEN
SPECIFIED. ON THE QRUN STATEMtNT.
'A'-'Z'
NOTE: THE 'PRIORITY, AND 'P,Q, FIELDS MAY BE OMITTED
WHEN THE STANDARD PRIORITY VALUES ARE TO BE
USED.
-A IS TO SPECIFY WHETHER DEADLINE OR REAL-TIME
PROGRAMS ARE TO BE ALLOWED FOR THE GIVEN
ACCOUNT NUMBER. A MAY BE EITHER
'A' (ALLOWED) OR
'N' (NOT ALLOWED)
NOTE: THE 'DEADLINE, AND 'A' FIELDS MAY BE
OMITTED WHEN THE SYSTEM STANDARD IS TO BE
USED.
NOTE: THE 'REAL-TIME' AND 'A' FIELDS MAY BE
OMITTED WHEN THE SYSTEM STANDARD IS TO BE
USED.
NOTE: SEE DELETE AC~OUNTS.
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE QRUN STATEMENT
PRIORITY SUB-FIELD
ADD PROCESSOR
THIS STATEMENT IS TO SPECIFY PROCESSORS TO BE ADDED TO THE
SYSTEM. ONE ADD STATEMENT IS NECESSARY FOR EACH PROCESSOR
TO BE ADDED. THE ADD STATEMENT IS OF THE FORM
ADD PROCESSOR

N F

PRODUCES

A

WHERE -N IS THE PROCESSOR NAME.
-F IS THE NAME OF THE FILE WHERE THE PROCESSOR IS
LOCATED.
-A IS ONE OF THE FOLLOWING.
'A SYMBOLlC ELEMENT'
'A RELOCATABLE ELEMENT'
'BOTH A SYMBOLIC AND A RELOCATABLE ELEMENT'
NOTE: SEE DELETE PROCESSORS.
SEE
-EXECUTIVE CONTROL LANGUAGE
PROCESSOR CALL STATEMENTS
THE ApDITION OF NEW PROCESSORS
ASSOCIATE SyMBIONTS
THIS STATEMENT SPECIFIES SYMBIONT ASSOCIATIONS.
MENT IS OF THE FORM~
ASSOCIATED SYMBIONTS I

PRINT 01, ••• ,ON

THE STATE-

PUNCH Pl, ••• ,PM

2
PAGE:

UP-4144

Rev.!

UNIVAC 1108 OPERATING

EXEC B

SYSTEM
SECTION:

(
WHERE -I IS THE INPUT SYMBIONT NAME.
-Ol, ••• ,ON ARE THE ASSOCIATED PRINT SyMBIONT
NAMES.
NOTE: THE 'PRINT' AND 'Ol, •••• ON' FIELDS MAY BE
OMITTED WHEN NO PRINT SYMBIONTS ARE
ASSOCIATED •
• Pl., •• ,PM ARE THE ASSOCIATED PUNCH SYMBIONT
NAMES.
NOTE: THE 'PUNCH' AND 'Pl ••••• PM' FIELDS MAY BE
OMITTED WHEN NO PUNCH SYMBIONTS ARE
ASSOCIATED.
NOTE: ONE STATEMENT IS NECESSARY FOR EACH DEVICE
ASSOCIATION DESIRED.
NOTE: SEE DELETE SYMBIONTS.
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE gSYM STATEMENT
USE OF ~SYM WITH PRINT$ AND PUNCH$
SEE
-SYMBIONTS
GENERAL DESCRIPTION
SYSTEM GENERATION PARAMETERS
DEVICE ASSOCIATION
AUTOMATIC SCHEDULING
THIS STATEMENT SPECIFIES ONE USER RUN TO BE AUTOMATICALLY SCHEDULED WHEN THE SYSTEM IS BOOTSTRAPPED.
STATEMENT HAS THE FORM:

(

AUTOMATICALLY SCHEDULE

THE

P

WHERE -P IS THE NAME OF THE FILE OR PROGRAM FILE
ELEMENT TO BE STARTED.
SEE

-EXECUTIVE CONTROL LANGUAGE
THE gSTART STATEMENT

AVERAGE PROGRAM SIZE
THIS STATEMENT IS USED TO SPECIFY THE AVERAGE SIZE OF
FORTRAN OR COBOL PROGRAMS. THE STATEMENT IS OF ~HE FORM:
AVERAGE

SIZE

OF. P

PROGRAMS

S

WHERE -P IS THE pROCESSOR NAME
'FORTRAN'
'COBOL'
-S IS THE NUMBER OF STATEMENTS
CATALOGUED FILES ESTIMATE
THIS VALUE ESTIMATES THE NUMBER OF FILES WHICH THE
SYSTEM WILL BE REQUESTED TO CATALOGUE. AN ACCURATE
ESTIMATE WILL AID IN THE EFFICIENT OPERATION OF THE
MASTER DIRECTORY SEARCH TECHNIQUE. THE FORM IS:
CATALOGUED FILES

N

WHERE -N IS THE NUMBER OF FILES EXPECTED.
COMMUNICATIONS OPTIONS
MAXIMUM COMMUNICATIONS: BUFFER LENGTH

3

18

PROGRAMMERS REFERENCE

PAGE:

IJP-4144
; Rev. 1
I

UNIVAC

110B OPERATING

EXEC B

SYSTEM

18

PROGRAMMERS REFERENCE

THIS STATEMENT IS USED TO ESTABLISH A MAXIMUM PERMISSABLE
BUFFER LENGTH TO BE ACCEPTED FOR BOTH INPUT AND OUTPUT
COMMUNICATIONS BUFFERS FOR ALL REAL-TIME PROGRAMS AND
SYSTEM SYMBIONTS FOR REMOTE TERMINALS~ THIS STATEMENT
IS OF THE FORM:
MAXIMUM COMMUNICATIONS BUFFER. LENGTH

N CHARACTERS

WHERE THE VALUE OF N IS EXPRESSED IN CHARACTERS.
MAXIMUM ESI COMPLETION ACTIVITY TIME
THIS STATEMENT IS USEU BY THE DISPATCHER AS THE LIMIT
FOR THE AMOUNT OF TIME AN ESI COMPLETION ACTIVITY MAY
HAVE CONTROL IN ORDER TO DETECT CLOSED LOOPS AND EXCESSIVE PROCESSING BY A REAL-TIME PROGRAt", WHICH MIGHT HAVE
AN ADVERSE EFFECT ON OTHER REAL-TIME PROGRAMS AND OTHER
~ARTS OF THE OPERATING SYSTEM.
THIS STATEMENT IS OF THE
FOHM:
MAXIMUM ESI COMPLETION ACTIVITY TIME

N MILLISECONDS

WHERE THE VALUE OF N IS EXPRESSED IN MILLISECONDS
REVERSE BUFFERING
THIS STATEMENT IS USED TO DEFINE WHETHER OR NOT THE CPU
HARDWARE FEATURE OF THE REVERSE BUFFERING CAPAAILITY IS
TO BE EMPLOYED UY THE SOFTWARE. THIS STATEMENT IS OF
THE FORM:
REVERSE BUFFERING FOR COMMUNICATIONS

A

WHERE -A IS EITHER
'ALLOWED' OR
'Nur ALLOWED'
COMMUNICATIONS BUFFER TIMING
THIS STATE~ENT DETERMINES WHETHER OR NOT THE TIMING OF
COMMUNICATIONS BUFFERS IS TO BE PROVIDED. THIS STATEMENT IS OF THE FORM:
COMMUNICATIONS BUFFER TIMING

A

WHERE -A IS EITHER
'PERFORMED' OR
'OMITTED'
AUTOMATIC DIALING OPERATIONS
THIS STATEMENT IS USED TO SPECIFY WHETHER OR NOT ANY
AUTOMATIC DIALING CAPABILITIES ARE PRESENT AT THE
CENTRAL SIlE. THIS STATEMENT IS OF THE FO~M:
DIALING OPERATIONS

A

WHERE -A IS EITHER
'ACCEPT' OR
,REJECT.
SYMBIONT SUPPORT
THIS STATEMENT UETERMINES WHETHER OR flOT SECOND LEVEL

SECTiON:

4
PAGE:

UP-4144
Rev. 1

UNIVAC

110B

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

SUPPORT IS TO BE PROVIDED. SECOND LEVEL SUPPORT IS USED
PRIMARILY BY THE SYMBIONTS. THIS STATEMENT IS OF THE
FOHM:
SECOND LEVEL COMMUNICATIONS SUPPORT

A

WHERE -A IS EITHER
'PROVIDED' OR
'OMITTED'
COMMUNICATIONS BUFFER POOLS
THIS STATEMENT UETERMINES WHETHER OR NOT THE USE OF
BUFFER POULS BY ANY REAL-TIME PROGRAM IS TO BE PERMITTED. THIS STATEMENT IS OF THE FORM:
COMMUNICATIONS BUFFER POOLS

A

WHERE -A IS EITHER
'ALLOWED' OR
'~JOT ALLOWED'
COMMUNICATIONS LOG ENTRIES
ThIS STATEMENT DETERMINES WHETHER DR NOT SYSTEM LOG
ENTRIES AKE TO HE MADE WITH INFORMATION-SUCH A~ TIME
OF INITIATION AND VOLUME OF USAGE. THIS STATEMENT IS
OF THE FOHM:
COMMUNICATIONS LOG ENTRIES

A

WHERE -A IS EITHER
'PHOVIDED' OR
'OMITTED'
REAL-TIME OPERATIONS VALIDATION
THIS STATEMENT IS USED TO DETERMINE WHETHER COMPLETE
VALIDATION IS TO BE PERFORMED FOR UNDEBUGGED HEAL-TIME
PROGRAMS OR IF ONLY PARTIAL VALIDATION .IS TO BE PERFOHMED ON STABLE AND THOROUGHLY DEbUGGED REAL-TIME
PROGRAMS. THIS STATEMENT IS EXPRESSED AS EITHER:
PERFORM COMPLETE REAL-TIME VALIDATION
OR
PERFORM PARTIAL. REAL-TIfJtE VALIDMIOH
CONNECT CHANNEL & DISCoNNECT CflANNEL
THESE STATEMENTS ARE TO SPECIFY CHAN~EL CONNECTIONS,
CtlANNEL TYpe:., EQUIPMENT TYPE, AND THE NUMBER OF UNITS
ATTACHED. THE CONNECT AND DISCONNECT STATEMENTS ARE 'NOT TO
BE USED FOR THE ALrERNATE CHANNEL OF A UUAL PAIR. THESE
STAT~MENTS ARE OF THE FORM:
CONNECT CHANNEL C TO 0, T U
DISCONNECT 0 FROM CHANNEL ~~T U

(-

wHERE -C IS TliE CHANNEL NUMBER
-u IS TIlE EQUIPMENT TYPE GIV~N BY ANY ONE OF THE
FOLLOWING.
CUNISERVO VI II C)
'VIlle'
(UNISERVO VI C)
'VIC'
(UNISERVO IV C)
'IVC'

SECTION:

18

PAGE:

5

- - - - - , - - - - - - ""---"""-----

UP-4144
I Rev. 1

--"---""---""

----------------------"-

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

-----"--""-"---- .

__.._-"_._.

SYSTEM

18
SECTION:

6
PAGE:

'IIIA.
'IIA'

(UNISERVO III A)
(UNISERVO II A)
'FH~32'
(FLYING HEAD ~32 MAGNETIC DRUM)
'FH880'
(FLYING HEAD 880 MAGNETIC DRUM)
'FASTRAND' (FASTRAND II)
'HSP755'
(HIGH SPEED PRI~TER)
'RP'
(CARD READER AND PUNCH)
'PT'
(PAPER TAPE)
'100411, (100~ II)
'1004111' (1004 III)
'CTS'
(COMMUNICATIONS)
'WTS'
(WORD TERMINAL)
'CTMC'
(COMMUNICATIONS TERMINAL CONTROL)
'NONSTD,
(NOi\lSTANDARD DEVICE TYPE)
-T IS THE CHANNEL TYPE GIVEN 8Y ONE OF THE
FOLLOWING.
,5' (SINGLE CHANNEL)
'PI (PARTIAL DUAL - R/W,R/R)
'0' (FULL DUAL - R/W,R/W)
NOTE: THE ALTERNATE CHANNEL IS ASSUMED TO BE C+1.
-U IS THE NUMBER OF UNITS.
SEE
-SUPERVISOR
SCHEOULING
FACILITIES INVENTORY
FOR NONSTANDARD DEVICES IT IS NECESSARY TO USE THE
NAME ASSOCIATION SYSTEM GENERATION PARAMETER TO
SPECIFY SyMUOLIC NAMES TO USE FOR ASSIGNING THESE
DEVICES. THE NUMBER OF UNITS FIELD IS DISREGARDED
FOR NONSTANDARD DEVICE CHANNELS. THESE CHANNELS ARE
ASSIGNED AS AN ENTITY.
OTHER, MORE SPECIFIC STATEMENTS MAY BE INCLUDED TO MORE
FUL~Y DESCRIBE THE CHANNEL'EQUIPMENT.
THESE ARE OF THE
FORM:
IVC 800 PPI C
THIS STATEMENT IS TO SPECIFy THAT A DENSITY OF 880 PPI
IS AVAILABLE ON THE IV C TAPE UNITS ON CHANNEL C.
IVC TRANSLATE C
VIC TRANSLATE C
VIlle TRANSLATE C
THIS STATEMENT SPECIFIES THE TRANSLATE FEATURE IS
AVAILABLE ON THE TAPE UNITS ON CHANNEL C.
FASTRAND FASTBAND C
THIS STATEMENT SPECIFIES FAsTBAND
FAsTRAND II ,UNITS. ON CHANNEL C.

~S

AVAILABLE ON THE

FASTRANO SECTOR BUFFER C
THIS STATEMENT SPECIFIES THAT A SECTOR BuFFER
IS PRESENT IN THE CONTROL UNIT OF THIS FASTRAND
CHANNEL, AND IN THE AJOINING CONTROL FOR DUALCHANNEL SUBSYSTEMS.
1004 CoDE IMAGE READER C
1004 PAPER TAPE READER C
1004 PAPER TAPE PUNCH C

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

1004 VIC N C .

THESE STATEMENTS SPECIFY ADDITIONAL 1004 II AND
1004 III FEATURES.
N GIVES THE NUMBER OF UNITS ON THE 1004 III.
SEE

CTS
CTS
CTS
WTS
WTS
WTS

-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE QCOL STATEMENT

AUTOMATIC DIALING
UNATTENDED
LEASED LINE
AUTOMATIC DIALING
UNATTENDED
LEASED LINE

C
C
C
C
C
C

THESE STATEMENTS ARE INCLUDED TO DESCRIBE MORE SPECIF,C
FEATURES OF THE CTS AND WTS. CARDS REFERRING TO A
LEASED LINE ARE USED FOR LINE SPEEDS OTHER THAN 2400
BPS.
CONTINUE OR TERMINAfE RUN
THESE STATEMENTS ARE TO SPECIFY RUN CONTINUATION OR
TERMINATION WHEN PRINT AND PUNCH FILES AREAS ARE EXCEEDED.
THE STATEMENTS ARE OF THE FORM:

(

CONTINUE
TERMINATE

RUN
RUN

WHEN
WHEN

P

FILE

P FILE

EXCEEDED
EXCEEDED

WHERE -P IS EITHER
,PRINT' OR
'PUNCH'
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANlZATIONAL STATEMENTS
THE "QRUN STATEMENT
PAGES SUB-FIELD
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE gRUN STATEMENT
CARDS SUO-FIELD
ANOTHER FORM OF THESE STATEMENTS ARE USED TO SPECIFy RUN
CONTINUATION OR TERMINATION WHEN THE RUN ESTIMATED TIME
HAS BEEN EXCEEDED.
COrnINUE
RUN WHEN TIME LIMIT EXCEEDED
TERMINATE RUN WHEN TIME LIMIT EXCEEDED
SEE

-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE QRUN STATEMENT
RUNNING TIME/DEADLINE FIELD

CORE SIZE
THIS STATEMENT IS TO SPECIFY THE SIZE OF CORE STORAGE
AVAILABLE. THE STATEMENT IS OF THE FORM:
CORE SIZE N K
wHERE -N IS THE NUMBER OF WORDS (IN THOUSANOS)IN CORE
STORAGE. THE OPTIONS ARE

SECTION:

18

PAGE:

7

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS

SEE

SYSTEM
REFERENCE

18
SECTION:

'65'
'131'
'196'
'262'

-SUPERVISOR
SCHEDULING
FACILITIES INVENTORY

DELETE LISTS
. THE FOLLOWING STATEMENTS ARE USED TO DELETE ENTIRE LISTS
PREVIOUSLY CONSTRUCTED BY THE SYSTEM GENERATION ROUTINE.
A LIST MAY BE DELETED AND RECONSTRUCTED WITH ONE SYSTEM
GENERATION. THE STATEMENTS ARE OF THE FORM:
DELETE
DELETE
DELETE
DELETE
DELETE
DELETE
REMOVE

ACCOUNTS
PKOCESSORS
SYMBIONTS
CHANNEL UNIT NAMES
RE-ENTRANT ROUTINES
REMOTE TERMINALS
PKOCESSORS

DErJlAND FACILITY
THIS STATEMENT INCLUDES OR DELETES THE DEMAND
FACILITY OF THE EXECUTIVE. THE FORM IS:
DEMAND FACILITY S
WHEKE -S IS EITHER:
'INCLUDED"
'DELETED'
DIVIDE
THE
AND
THE

OR

DRUM
DIVIDE STATEMENT IS TO DIVIDE FH432 AND FH880 DRUM iNTO CONTIGUOUS AREAS
SIMULATED FASTRAND. ALL REMAINING DRUM IS USED AS'SIMULATED FASTRAND.
STATEMENT IS OF THE FORM:

DIVIDE

C U N

WHERE -C IS THE CHANNEL NUMBER.
-U IS THE UNIT NUMBER.
-N IS THE NUMBER OF LOCATIONS TO BE ALLOCATED AS
CONTIGUOUS DRUM.
SEE
-SUPERVISOR
SCHEDULING
FACILITIES INVENTORY
SEE
-FILE CONTROL SYSTEM
FILE ORGANIZATION
MASS STORAGE ALLOCATION
GENERAL
LOG MEDIUM

THIS STATEMENT IS TO SPECIFY THE LOG MEDIUM, THE STATEMENT
IS OF THE FORM:
LOG MEDIUM

TYPE

wHERE -TYPE IS THE E:QUIPMENTTYPE.

8
PAGE:

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM

(MA~IMUM

DELAY TIME
THIS STATEM~NT SETS THE MAXIMUM TIME AN EXTERNAL FUNCTION
CAN 8E OUTSTANDING FOR THE ARBITRARY DEVICE HANDLER. THE
STATEMENT IS OF THE FORM:
MAXIMUM DELAY TIME T SECONDS
WHERE -T IS THE TIME IN SECONDS.

MAXIMUM FILE SIZE
THIS STATEMENT IS USED TO SET THE SYSTEM MAXIMUM FILE SIZE
TO BE USED WHEN A MAXIMUM FILE SIZE HAS NOT BEEN SPECIFIED
ON AN ASSIGN STATEMENT. THE STATEMENT IS OF THE FORM:
MAXIMUM FILE SIZE

N

WHERE -N IS THE NUMBER OF TRACKS
SEE
-EXECUTIVE CONTROL 'LANGUAGE
INPUT/OUTPUT SPECIFICATION STATEMENTS
THE QASG STAT-EMENT
THE FASTRAND QASG STATEMENT
MAXIMUM NUMBER OF LOG ENTRIES
THIS STATEMENT IS TO SPECIFY THE MAXIMUM NUMBER OF LOG
ENTRIES ANY ONE RUN MAY MAKE. THIS STATEMENT IS OF THE
FORM:
LOG MAXIMUM

N

WHERE -N IS THE MAXIMUM NUMBER.
SEE
-EXECUTIVE REQUEST FUNCTIONS
THE SYSTEM LOG
MINIMUM DBANK ADDRESS
THIS STATEMENT SETS THE MINIMUM DBANK ADDRESS FOR
EACH PROGRAM COLLECTED. ITS EFFECT IS TO RESERVE
I~ANK ADDRESS SPACE FOR LINKING RE-ENTRANT
PROCESSORS. THE FORM IS:
MINIMUM DBANK ADDRESS

A

wHERE A IS ~HE OCTAL OR DECIMAL ADDRESS.
MAXIMUM NUMBE~ OF OPENED RUNS
THIS STATEMENT IS USED TO SPECIFY THE MAXIMUM NUMBER OF
RUNS THAT MAY BE OPENED AT ANY ONE TIME. THE STATEMENT
IS OF THE FORM:
MAXIMUM OPENED RUNS

N

WHERE -N IS THE NUMBER OF RUNS.
SEE
-FILE CONTROL SYSTEM
FILE ORGANIZATION
MASS STOHAGE ALLOCAT10N
ROLLOUT OF FILES TO MAGNETIC TAPE

9

18
SECTION:

PAGE:

UP-4144

Rev. 1

UNIVAC

1108

EXEC B

OPERATING

SYSTEM

10

18

PROGRAMMERS REFERENCE

SECTION:

PAGE:

c
NAME AND C/U ASSOCIATION
THIS STATEMENT IS TO IDENTIFY CHANNELS AND SPECIFIC UNITS
WITH SYMBOLIC NAMES. THESE NAMES ARE TO BE USED IN THE
'TYPE' FIELD TO OBTAIN AN ASSIGNMENT. THIS SiATEMENT IS OF
THE FORM:
NAME N IS C U
WHERE -N IS A ONE TO SIX CHARACTER NAME.
-C IS THE CHANNEL NUMBER.
-U IS THE UNIT NUMBER.
liOTE: IF A NAME IS TO BE ASSOCIATED WITH A CHANNEL
THE U FIELD IS NOT NECESSARY.
NOTE: ONE STATEMENT IS NECESSARY FOR EACH ASSOCIATION
DESIRED.
NOTE: SEE DELETE CHANNEL UNIT NAMES.
SEE
-EXECUTIVE CONTROL LANGUAGE
INPUT/OUTPUT SPECIFICATION STATEMENTS
THE ~ASG STATEMENT
THE ARBITRARY DEVICE QASG STATEMENT
NOISE CONSTANT
THIS STATEMENT IS USED TO SET THE STANDARD TAPE NOISE
CONSTANT. THE STATEMENT IS OF THE FORM:
NOISE CONSTANT
WHERE

-I'-J

N

IS THE NOISE CONSTANT VALUE.

PROBE
THIS STATEMENT IS USED TO SPECIFY THE INPUT SYMBIONT, OR
SYMBIONT CLASS, WHICH IS rO BE PLACED IN THE PROBE MODE.
THE STATEMENT IS OF THE FORM:
PROBE

c

S

WHERE -S IS THE SYMBIONT NAME, OR SYMBIONT CLASS,
OF THE CORRESPONDING UNIT TO BE PROBED.
SEE
-SYMBIONTS
.
ON-SITE DEVICE HANDLERS
INPUT OPERATION
SEE
-SYMBIONTS
SYSTEM GENERATION PARAMETERS
PROBE

PROCESSOR DESCRIPTION
THIS STATEMENT DEFINES THE TYPE AND CHARACTERISTICS
OF THE CENTRAL PROCESSING UNIT. THE FORM IS:
PROCESSOR P CHANNELS C
WHERE -P IS '1108' OR '1108A'. AND
-C IS THE NUMBER OF CHANNELS

PRESENT~

RE_ENTRANT ROUTINES
THIS STATEMENT IS TO IDENTIFY RE-ENTRANT ROUTINES.
STATEMENT IS OF THE FORM:
REENTRANT

ROUTINE

R

THE

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

SYSTEM

18

PROGRAMMERS REFERENCE

WHERE -R IS ROUTINE NAME.
NOTE: SEE DELETE RE-ENTRANT ROUTINf;:S.,
SEE
-BASIC OPERATIONAL DESCRIPTIONS
DEMAND PROCESSING
CONVERSATIONAL COMPONENTS
RE-ENTRANT CONTROL
REAL TIME FACILITY
THIS STATEMENT INCLUDES OR DELETES THE REAL TIME
CAPABILITy OF THE EXECUTIVE. THE FORM IS:
REAL TIME S
WHERE -S IS 'INCLUDED' OR 'DELETED'.
REMOTE TERMINALS
THIS STATEMENT IS USED TO IDENTIFY THE EQUIPMENT AT THE
REMOTE TERMINALS. THE STATEMENT IS OF THE FORM:
REMOTE TERMINAL

(

I

C

R

P

T

Q

WHERE -I IS A SIX CHARACTER FIELD WHICH
IDENTIFIES THE REMOTE LOCATION.
-C IS THE REMOTE CONFIGURATION AND MAY BE ONE O~
THE FOLLOWING.
'100411' (100~ II)
'1004111' (1004 III)
'KSR35'*
(MODEL 35 TELETYPE*OR EQUIVALENT)
'ASR35'*
(AUTOMATIC SEND RECEIVE MODEL 35)*
-R IS THE NAME OF A SYMBIONT (FOR RUN INPUT) OR
THE NAME OF A FILE (TO AUTOMATICALLY START
A PREDEFINED RUN) FOR THE INPUT STANDBY IDLE
STATE CONDITION. IF R IS A NAME OF A FILE,
THIS FIELD HAS SUBFIELDS AS FOLLOWS:
Q,F,Kl,K2,E,V
WHERE

-Q .IS THE QUALIFIER (OPTIONAL) •
• F IS THE FILE NAME PORTION OF THE
EXTERNAL NAtvlE.
-Kl IS THE READ KEy tOPTI~NAL).
-K2 IS THE WRITE KEY (OPTIONAL).
-E IS THE NAME OF THE ELEMENT WITHIN
THE FILE IF MORE THAN ONE.
-v IS THE ELEMENT VERSION (APPLIES
ONLY IF E IS SPECIFIED),

-P IS A ONE TO SIX CHARACTER PRINT SITE-ID.
-T IS THE PROGRAM TYPE (IF NOT OTHERWISE
SPECIFIED) OF ALL RUNS ENTERED AT THIS
TERMINAL. T IS EITHER
'BATCH' OR
'DEMAND,.
-Q IS A ONE TO SIX CHARACTER PUNCH SITE-ID.
NOTE: THE Q FIELD MAY BE O~ITTED,
NOTE: ONE STATEMENT IS NECESSARY FOR EACH INPUT OUTPUT
ASSOCIATION DESIRED,
NOTE: SEE DELETE REMOTE TERMINALS.
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGA~IZATIONAL STATEMENTS
THE ~RUN STATEMENT
PRIORITY SUB-FIELD
·TRADEMARK OF TELETYPE CORPORTION

SECTION:

11
PAGE:

UP-4144

, Rev. 1

UNIVAC '1108 OPEFIATINGSYSTEM

EXEC B

PRO~AMMEFISREFERENCE

12

1,8
SECTION:

PAGE:

r

"-./1

SEE

SEE

-EXECUTIVE CONTROL LANGUAGE
INPUT/OUTPUT SPECIFICATION STATEMENTS
THE QASG STATEMENT
.
THE ARBITRARY DEVICE QASG STATEMENT
-SYMBIONTS
SYSTEM GENERATION PARA~IETERS
DEVICE ASSOCIATION

RESERVE MASS STORAGE
THE PURPOSE OF THIS STATEMENT IS TO RESERVE A MASS STORAGE
AREA AS A NAMED PERMANENT FILE. THE STATEMENT IS OF THE
FORM:
RESERVE F C U A 0 G
WHERE -F IS THE FILE NAME BY WHICH THE FILE IS CATALOGUED AND RETRIEVED. THE FILE NAME FIELD
HAS THE FORMAT:
Q,F,Kl,K2
WHERE -Q IS THE QUALIFIER (OPTIONAL).
-F IS THE FILE NAME PORTION OF THE
EXTERNAL NAME.
-Kl IS THE READ KEy (OPTIONAL).
-K2 IS THE WRITE KEY (OPTIONAL).
NOTE: THE F-CYCLE SUBFIELD OF THE FILE
NAME AS DISCUSSED ELSEwHERE IN THIS
DOCUMENT IS ALWAYs TAKEN AS ZERO
FOR THE RESERVE STATEMENT.
-C
-U
-A
-D

SEE

IS THE CHANNEL NUMBER.
IS THE UNIT NUMBER.
IS THE STARTING ADDRESS
IS TO INDICATE WHETHER POSITIONS OR TRACKS
ARE TO BE ASSIGNED. THE D FIELD MAY CONTAIN
'POSITIONS' OR
'TRACKS,.
-G IS THE NUMBER OF GRANULES TO ASSIGN. THE
STARTING ADDRESS IS THE LOGICAL SECTOR ADDRESS
o TO N FOR EACH UNIT AND MUST BE THE START OF
A TRACK IF 0 CONTAINS ~TRACKS' OR POSITION IF
D CONTAINS ,POSITIONS'.
-EXECUTIVE CONTROL LANGUAGE
INPUT/OUTPUT SPECIFICATION STATEMENTS
THE QASG STATEMENT
THE FASTRAND QASG STATEMENT

RETAIN CYCLES AND F-CYCLES·
THIS STATEMENT IS TO SPECIFY THE NUMBER OF CYCLES TO RETAIN
WHEN A NUMBER HAS NOT BEEN SPECIFIED. THE STATEMENT IS OF
THE FORt",:
RETAIN

N C

WHERE -N IS THE NUMBER OF CYCLES.
-C IS EITHER
,CYCLES' OR
'FCYCLES'
HOLLOUT CONTROL POINTS
THIS STATEMlNT IS USED TO SPECIFY THE FASTRAND AVAILABILITY
POINTS AT wHICH ROLL OUT OF FILES IS AUTOMATICALLY STARTED
AND STOPPED:

c

UP-4144
Rev. 1

UNIVAC 1108 OPERATING

EXEC B

ROLLOUT POINTS

SYSTEM

PROGRAMMERS REFERENCE

N M

WHERE -N IS THE NUMBER OF TRACKS AVAILABLE WHEN ROLLOUT
STARTS.
-M IS THE NUMBER OF TRACKS AVAILABLE WHEN ROLLOUT
IS STOPPED.
SEE
-FILE CONTROL SYSTEM
FILE ORGANIZATION
MASS STORAGE ALLOCATION
ROLLOUT OF FILES TO MAGNETIC TAPE
SEE
-EXECUTIVE SYSTEM DESIGN CRITERIA
PROGRAM FILES
'CYCLE' PARAMETER
SEE
-EXECUTIVE CONTROL LANGUAGE
INPUT/OUTPUT SPECIFICATION STATEMENTS
THE QASG STATEMENT
NOTATION FOR FILE NAMES
SEE
-EXECUTIVE CONTROL LANGUAGE
PROCESSOR CALL STATEMENTS
STATEMENT FORMAT
CTMC
THIS STATEMENT IS TO DEFINE THE UNITS ON THE CTMC. THE
STATEMENT IS OF THE FORM:

(

CTMC

G C T S

B N L

M 1,0

D

WHERE -G IS THE LT GROUP IDENTITY.
-C IS THE CHANNEL NUMBER.
-T IS TrlE UNIT TYPE AND MAY CONTAIN:
'STANDARD'
'NASA'
'GSA3EI.
-S IS THE UNIT SPEED AND MAY CONTAIN:
'LOW'
'MEDIUM,
'SYNC'
'PARALLEL'
-8 IS THE LINE SPEED IN BITS PER SECOND.
-N IS THE NUMBER OF BITS PER CHARACTER.
-L IS THe LINE TYPE AND MAY CONTAIN:
'COM~ONCARKIER'

SEE

c·

'LEASED.
'TELEGRAPH'
-M IS THE IDLE STATE FOR AN INPUT UNIT.
'OFF' SPECIFIES NO IDLE STATE MONITOR.
'STANDBY' CALL FOR AUTOMATIC STARTING
OF A RUN DEFINED IN THE REMOTE STATEMENT.
-1 IS THE INPUT UNIT INDICATOR NUMBER.
-0 IS THE OUTPUT UNIT INDICATOR NUMBER.
-u IS THE DJAL UNIT INDICATOR NUMBER
WHEN PHESENT.
-INPUT/OUTPUT DEVICE HANDLERS
COMMUNICATIONS MULTIPLEXOR HANDLER
ASSIGNING LT DEVICES

SHARING PERCENTAGES
THESE STATEMENTS ARE USED TO SPECIFY HOw CPU TIME IS TO BE
SHARED AMONG THE FOUR TYPES of PROGRAMS. THE STATEMENTS
ARE OF TtiE FORM:

18
SECTION:

13
PAGE:

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC

PROGRAMMERS REFERENCE

a

DEMAND MINIMUM PERCENTAGE
DEMAND MAXIMUM PERCENTAGE

SYSTEM

1~
SECTION:

14
PAGE:

N
N

WHERE -N IS THE PERCENTAGE.
SEE
-SUPERVISOR
SCHEDULING
THE DYNAMIC ALLOCATOR
SHARING BETWEEN PROGRAM TYPES
STANDARD DEADLINE SPECIFICATION
THIS STATEMENT IS TO SPECIFY THE ASSUMED DEADLINE SPECIFI~
CATION (THE DEADLINE SPECIFICATION USED IN THE ABSENCE OF
A DEADLINE SPECIFICATION ON AN ACCOUNT STATEMENT), THIS
STATEMENT IS of THE FORM:
STANDARD DEADLINES

A

WHERE -A IS EITHER
'ALLOWED' OR
'NOT ALLOWED'
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE QRUN STATEMENT
PRIORITY SUB-FIELD
STANDARD DENSITY
THIS STATEMENT IS USED TO RESET THE STANOARD TAPE DENSITY.
THIS IS THE DENSITY TO BE USED IF NOT SPECIFIED ON THE QASG
STATEMENT OR SET MODE I/O FUNCTION, THIs STATEMENT IS OF
THE FORM:
STANDAKD DENSITY N
WHERE -N IS THE NUMBER OF FRAMES PER INCH.
STANDARD PAGE AND CARD LIMIT
THESE STATEMENTS SET THE ASSUMED PAGE AND CARD LIMITS (THE
LIMITS USED WHEN NONE HAVE BEEN SPECIFIED ON THE RUN CARD),
THESE STATEMENTS ARE OF THE FORM:
STANDARD PAGE LIMIT
STANDARD CARD LIMIT

N
M

WHERE -N IS THE MAXIMUM NUMBER OF PAGES,
-M IS THE MAXIMUM NUMBER OF CARDS.
SEE
-EXECUTIVE CONTROL LANGUAGE
ORGANIZATIONAL STATEMENTS
THE QRUN STATEMENT
PAGES SUB-FIELD
SEE
-SYMBIONTS
SYSTEM GENERATION PARAMETERS
MASS STORAGE REQUIREMENTS
STANDARO RUN TIME
THE RUN TIME STATEMENT IS USED TO SET THE ASSUMED RUN
ESTIMATED TIME (THE ESTIMATED TIME USED WHEN NONE HAS BEEN
SPECIFIED ON THE folRUN CARD), THIS STATEMENT IS OF THE
FORM:
STANDARD RUN TIME

T MINUTES

(~

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

PROGRAMMERS REFERENCE

WHERE -T IS THE TIME IN MINUTES.
SEE
-EXECUTIVE CONTRO~ LANGUAGE
ORGANIZATIONA~ STATEMENTS
THE QRUN STATEMENT
THE RUN-OPTIONS SU8-FIE~D
STARTING UNIT NUMBER
THIS STATEMENT IS TO SPECIFY THE STARTING UNIT NUMBER ON
A GIVEN CHANNEL WHEN THE STARTING UNIT NUMBER IS OTHER
THAN ZERO. THE STATEMENT HAS THE FORM:
STARTING UNIT NUMBER ON

CHANNE~

C U

WHERE -C IS THE CHANNE~ NUMBER.
-U IS THE STARTING UNIT NUMBER.
SYSTEM RESIDENCE
THIS STATEMENT SPECIFIES THE CHOICE OF RESIDENCE FOR THE
1108 EXECUTIVE SYSTEM. THE STATEMENT IS OF THE FORM:
SYSTEM

RESIDENCE

C

WHERE -C IS THE CHANNEL NUMBER.
SEE
-SUPERVISOR
SCHEDU~ING

(

SEE

FACILITIES INVENTORY
-FILE CONTROL SYSTEM
FI~E ORGANIZATION
MASS STORAGE ALLOCATION
GENERAL.

TIME AL.LOCATION
THESE STATEMENTS DESCRIBE THE TIME VALUES USED IN THE
CAL.CULATION OF THE QUANTUMS OF TIME GIVEN TO BATCH
AND DEMAND PROGRAMS.
BATCH ALL.OCATION A
DEMAND AL.L.OCATION B
BATCH PRIORITY FACTOR C
DEMAND PRIORITY FACTOR D
TIMES A AND B ARE GIVEN IN MI~LISECONDS. IT IS
THE AMOUNT OF TIME GIVEN TO A PROGRAM AT THE
HIGHEST PRIORITY L.EVEL.
C AND DARE MULTIPL.IERS OF THE RUN PRIORITY WHICH
CONTRoL THE EFFECT OF PRIORITY UPON TIME AL.L.OCATION.
THE PRIORITY L.ETTERS YIEL.D THE VA~UES: 26-A,25-B, •••
1-Z, THE EXPRESSION USED TO FIND THE QUANTUM (Q) IS:
Q
A * (1 + PtF) * T
WHERE ,p, IS PRIORITY, 'F' THE PRIORITY FACTOR, AND
'T' THE LEVEL. FACTOR.

=

18.1. 4 •

INITIAL SYSTEM

THE FOL.LOWING STATEMENTS ARE USED TO GENERATE THE INITIAL. SYSTEM.
AVERAGE SIZE OF COBOL.
PROGRAMS 500
AVERAGE SIZE OF FORTRAN PROGRAMS 500
CONTINUE
RUN WHEN PRINT FILE EXCEEDED
RUN WHEN PUNCH FILE EXCEEDED
CONTINUE

18
SECTION:

15
PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

18
SECTION:

16
PAGE:

CONTINUE
RUN WHEN TIME LIMIT EXCEEDED
CORE SIZE 65 K
DEMAND MAXIMUM PERCENTAGE 70
DEMAND MINIMUM PERCENTAGE 20
LOG MAXIMUM 10
MAXIMUM DELAY TIME 300 SECONDS
MAXIMUM FILE SIZE 1000
MAXIMUM OPENED RUNS 5
NOISE CONSTANT 18
RETAIN 5 CYCLES
RETAIN 5 FCYCLES
STANDARD CARD LIMIT 500
STANDARD DEADLINES ALLOWED
STANDARD DENSITY 800
STANDARD PAGE LIMIT 100
STANDARD RUN TIME 6 MINUTES

18.2.

SYSTEM'LOADING

AS A PART OF THE ORDERED RUN CONSTRUCTED BY THE SYSTEMS ~ENERATION ROUTINE, AN
OUTPUT TAPE IS PRODUCED WHICH CONTAINS THE 1108 EXECUTIVE SYSTEM AND THE SYSTEMS
LIBRARY, THIS TAPE IS INITIALLY LOADED BY THE MANUAL HARDWARE BOOTSTRAP METHOD. THE
BOOTSTRAP CAN BE PERfORMED ON THE VIIIC, VIC OR IVC TAPE CHANNELS. FOUR 'INITIAL
LOAD' TOGGLE SWITCHES ON THE CPU MAINTENANCE PANEL MUST BESET TO DETERMINE THE INPUT
CHANNEL.
THE BOOTSTRAP BLOCK IS LOADED AT THE FIRST LOCATION IN THE MEMORY MODULE SELECTED
BY THE MEMORY SELECT REGISTER,
IMMEDIATELY AFTER THE BOOTSTRAP ROUTINE RECEIVES CONTROL THE AREAS AT 2000 OCTAL
AND ABOVE WHERE THE EXEC IS TO BE STORED IN CORE IS COPIED TO MASS STORAGE, IF A
PREVIOUS EXEC WAS STILL IN CORE, EXCEPT FOR THE FIRST 2000 OCTAL WORDS, ITS CONTENTS
ARE SAVED FOR INFORMATION PURPOSES,
IF JUMP KEy TWO (2) IS SET, A SERIES OF SELECTED CORE AREAS MAY BE SAVED ON MASS
STORAGE, THE PARAMETERS ARE ENTERED THROUGH THE PROGRAM ADDRESS COUNTER (P).
AFTER THE REQUESTED AREAS ARE SAVED, THE ROUTINE IN CORE READS THE TAPE TO BRING
IN EACH BLOCK OF THE SYSTEM AND COpy EACH TO THE PROPER DRUM LOCATIONS. THIS COpy OF
THE EXECUTIVE SYSTEM IS LOCATED AS SPECIFIED AT SYSTEM GENERATION TIME. A FIXED AREA
ON THIS DRUM BEGINNING AT ADDHESS ZERO IS RESERVED FOR EXECUTIVE SYSTEM USAGE ONLY.
THIS FIXED AREA IS DETERMINED AT SYSTEM GENERATION TIME, DEPENDING ON THE
CONFIGURATION, I.E. NUMBER OF EQUIPMENT HANDLERS REQUIRED AND NUMBER OF PROCESSORS
TO BE LOCATED ON DRUM.
THE USER HAS THE OPTION OF ~LACING ANY OF THE PROCESSORS ON A SLOWER MASS STORAGE
DEVICE IF IT EXISTS, AN INITIALIZATION ROUTINE FINALLY PLACES A COpy OF THE RESIDENT
"ORTION OF THE EXECUTIVE SYSTEM IN CORE, INITIALIZES AND/OR RE~INSTATES FILE
DIRECTORIES AND GIVES THE SYSTEM CONTROL,
18.2.1.

INITIAL LOAD CONSOLE COMMUNICATIONS

DURING INITIAL LOAD THERE EXISTS A MEANS OF TEMPORARILy MODIFyING THE SITE TABLE
ASSIGNMENTS. IF INITIAL LOAD IS MADE VIA A TAPE CHANNEL AND JUMP KEY 5 IS SET, THE
FOLLOWING TyPE-OUT WILL APPEAR :

THE CONSOLE WILL BE PLACED IN THE INPUT MODE TO ACCEPT DRUM AND/OR PRINTER CHANNEL

c

UNIVAC 1108 OPERATING

UP-4144

EXEC B

Rev.l

SYSTEM

PROGRAMMERS REFERENCE

MODIFICATIONS. THE DRUM CHANNEL IS THE CHANNEL USED TO OPERATE AND STORE THE EXEC.
THE PRINTER CHANNEL IS USED BY THE PANIC DUMP ROUTINES TO PRINT DATA. IF A PRINTER
CHANNEL IS NOT SPECIFIED THE DUMP WILL BE STORED IN A STORAGE AREA. THESE CHANNELS
MAY BE TEMPORARILY MODIFIED VIA THE FOLLOWING TYPE-INS:
DCC
PCC
DCC pCC

OR

PCC DCC

CC - DESIGNATES THE CHANNEL NUMBER (IN DECIMAL)
CR - DESIGNATES THE END OF MESSAGE.
IF AT ANY TIME A TYPE-IN ERROR OCCURS PRIOR TO TYPING T~E 'CR, THE ENTIRE MESSAGE
MAY BE IGNORED BY TyPING THE LOZENGE.
IF INITIAL LOAD IS MADE VIA A DRUM CHANNEL AND JUMP KEY 5 IS SET, THE FOLLOWING
TYPE-OUT WILL OCCUR:

(-

THE CONSOLE WILL BE PLACED IN THE INPUT MODE TO ACCEPT TEMPORARY MODIFICATIONS TO THE
PRINTER AND/OR TAPE BOOTSTRAP CHANNEL, THE ROUTINE ACCEPTS DATA UNTIL A PERIOD IS
ENCOUNTERED, THE ITEMS MUST BE SEPARATED BY A SPACE BUT THEY MAY APPEAR IN ANY ORDER
AND ANY COMBINATION OF ONE OR ALL. THE TyPE-IN HAS THE FOLLOWING FORMAT:
TCC
PCC
TCC PCC
CC - DESIGNATES THE CHANNEL NUMBER (IN DECIMAL),
AS IN THE TAPE BOOTSTRAP CASE, IF A TYPE-IN ERROR OCCURS BEFORE THE CR IS TYPED
THE MESSAGE MAY BE CANCELLED BY TYPING IN A LOZENGE.
ALSO ASSOCIATED WITH BOTH THE TAPE ANO DRUM INITIAL LOAD ROUTINES ARE CERTAIN
ERROR MESSAGES THAT MAY BE TYPED OUT DURING INITIAL LOAD. THESE ERROR MESSAGES MAY
BE DIVIDED INTO TWO SEPARATE GROUPS. THE FIRST IS THE I/O GROUP. THIS GROUP
CONSISTS OF ERROR MESSAGES THAT MAY BE TYPED OUT UPON THE' OCCURRENCE OF AN ERROR
CONDITION THAT ARISES IN CONJUNCTION WITH AN I/O OPERATION. IF THIS ERROR WAS IN THE
FORM OF AN EXTERNAL INTERRUPT THE APPROPRIATE STATUS CODE WILL BE INSERTED INTO THE
MESSAGE. THUS THERE EXISTS TWO FORMS OF AN I/O ERROR MESSAGE. THE FORMAT AND
EXPLANATION OF THESE TWO TYPES IS AS FOLLOWS:

AND

ERR : CH CC SSSSSS DDDDDD AAAAAA

ERR : CH CC DDDDDD AAAAAA
CC - CHANNEL NUMBER(OCTAL) FROM WHICH THE ERROR AROSE
S - STATUS CODE
U - DIAGNOSTIC MESSAGE EXPLAINING TYPE OF INTERRUPT.
THIS MAY BE ANY OF THE FOLLOWING:
ISIIN - lSI INPUT MONITOR
ISIOUT - lSI OUTPUT MONITOR
ISIFNC - lSI FUNCTION MONITOR
ESI IN - ESI UlPUT MONITOR
ESIOUT - ESI OUTPUT MONITOR
ESICWP - ESI CONTROL WORD PARITY
ISICWP - lSI CONTROL WORD PARITY

17

18
SECTION:

PAGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

. EXEC

a

SYSTEM,

PROGRAMMERS

REFERENCE'

18
sEtfrON:'

18
PAGE:

''
C
"

J

DATAP
ESIEI
ISlE I
A - ADDRESS OF

- ESI OR 151 DATA PARITy
_ ESIEXTERNAL INTERRUPT
- lSI EXTERNAL, INTERRUPT
THE MAIN CODE THAT WAS INTERRUPTED.

THE OTHER GROUP OF ERROR MESSAGES MAY BE CALLED COMPUTER MALFUNCTION AND
MISC£LLANEOUS ERRORS. THIS GROUP TAKES INTO ACCOUNT ALL THE INTERRUPTS THAT ARE NOT
ASSOCIATED WITH 1/0. THE FORM AND EXPLANATION OF THIS TYPE OF MESSAGE IS AS FOLLOWS:
ERR : DDDDDD AAAMA
o - DIAGNOSTIC MESSAGE EXPLAINING TYPE OF INTERRUPT.
THIS MAY BE ANY OF THE FOLLOWING:
POWLOS - POWER LOSS
MEM1P
- MEMORY 1 INSTRUCTION PARITY
MEM2P
- MEMORY 2 INSTRUCTION PARITY
MEM3P
- MEMORY 3 INSTRUCTION PARITY
MEM4P
- MEMORY 4 INSTRUCTION PARITY
ICRP
- ICR PARITY
ILINS
- ILLEGAL INSTRUCTION
EXRET
- EXECUTIVE RETURN
GRDMOD - GUARD MODE
TSTSET - TEST AND SET
FPUNDF - FLOATING POINT UNDERFLOW
FPOVF
- FLOATING POINT OVERFLOW
DIVFLT - DIVIDE FAULT.
A - ADDRESS OF THE MAIN CODE THAT WAS INTERRUPTED
18,3.

SYSTEM GENERATION

THE SYSTEM GENERATION ROUTINE MAY BE USED TO AID IN THE GENERATION AND
RE-GENERATION OF ANy SYSTEM (OR RUN DECK). THIS SECTION GIVES A DETAILED DESCRIPTION
OF HOW THE SYSTEM GENERATION ROUTINE CAN BE APPLIED TO ANY SYSTEM OR RUN.
18.3.1.

INTRODUCTION

THE OB..JECT OF THE SYSTEM GENERATION ROUTINE IS TO SUPPLY THE SYSTEMS PROGRAMMER
WITH A MEANS TO CONTROL THE CONTENTS OF ALL SYMBOLIC ELEMENTS OF A SYSTEM. THE
PURPOSE BEHIND THIS IS TO ALLOW THE SYSTEMS PROGRAMMER TO UPDATE ALL SYMBOLIC
ELEMENTS IN THE FIELD WITH THE SAME CORRECTION DECK. AT THE SAME TIME, THE SYSTEM
U~ER IS GIVEN A CONVENIENT AND SIMPLE MEANS TO ALTER THE RELOCATABLE ELEMENTS OF THE
SYSTEM AND GENERATE AN OPERABLE SYSTEM TO MEET THE REQUIREMENTS OF HIS CHANGING NEEDS
AND HARDWARE CONFIGURATION.
THE SYSTEMS PROGRAMMER MUST PROVIDE THE SGR WITH A SKELETON RUN DECK WHICH
CONTAINS A DESCRIPTION OF THE SYSTEM, ALL ALLOWABLE SYSTEM MODIFICATIONS, AND THE
CORRECTIONS NECESSARY TO ACCOMPLISH THESE MODIFICATIONS. THE USER THEN, NEED ONLY
SPECIFY, WITH SIMPLE STATEMENTS (SYSTEM GENERATION STATEMENTS, SGS;S) , THOSE
MODIFICATIONS HE DESIRES AND THE SGR WILL CONSTRUCT AND EXECUTE A RUN TO INCLUDE THE
DESIRED MODIFICATIONS AND GENERATE AN OPERABLE SYSTEM.
THE SYSTEMS PROGRAMMER AND THE USER MAY ALSO ENTER CORRECTIONS TO THE SYSTEM.S
ELEMENTS THROUGH THE SGR At~D THESE CORRECTIONS WILL BE INCLUDED IN THE RUN.
CORRECTIONS TO AN ELEMENT ARE OF TWO KINDS ... SYSTEMS PROGRAMMER CORRECTIONS WHICH ARE
ENTERED IN THE SYMBOLIC ELEMENTS AND USER CORRECTIONS WHICH ONLY ENTER SYMBOLIC
ELEMENTS WHEN AUTHORIZED BY THE SYSTEMS PROGRAMMER. THUS, THE SYSTEMS PROGRAMMER CAN
PKEVENT THE USER FI{OM ALTERING THE SYSTEM'S SYMBOLIC ELEMENTS AND YET ALLOW HIM TO
ALTER THE SYSTEM'S RELOCATABLE ELEMENTS. THE SGRWILL ALSO REPRODUCE THE USER.S
CORRECTION DECK WITH CORRECTED LINE NUMBERS WHICH HAVE RESULTED FROM SYSTEMS
PROGRAMMER CORHECTlONS AND THE CORRECTIONS GENERATED FROM SGS'S.

C·.
.

.

UNIVAC

UP-4144

Rev. 1

1108

EXEC B

18,3.2.

OPERATING

SYSTEM

CA~~ING SEQUE~CE

SECTION:

FOR THE SGR

A DESCRIPTION OF EACH OF THE DATA

FI~ES

AND OPTIONS WILL

FOL~OW.

QXGT,OPTIONS SGR
SKELETON E~EMENT NAME
QEOF
SYSTEM GENERATION STATEMENTS
QEOF
USER'S CORRECTIONS
QEOF
SYSTEMS PROGRAMMER CORRECTIONS
QEOF
SKE~ETON

CORRECTIONS

QEND
THE SKE~ETON 'FILENAME' (12 CHARACTERS MAXIMUM) MUST HAVE BEEN PREVIOUSLY
ASSIGNED. THE FILE INDICATED AS SKELETON CORRECTIONS WILL APPLY TO THIS ELEMENT.
THE QEOF AND QEND CARDS MUST BE PRESENT AS SHOWN, EVEN IF THE SECTION DOES NOT
CONTAIN DATA,
18,3.3.

SYSTEM GENERATION STATEMENTS

SYSTEM GENERATION STATEMENTS (SGS'S) ARE COMPRISED OF ANY NUMBER OF FIELDS WHICH
MAY BE COMPRISED OF ANY NUMBER OF SUB-FIELDS, A SUB-FIELD IS A STRING OF 18 OR FEWER
CHARACTERS NOT CONTAINING A SPACE, COMMA, RIGHT BRACKET, LEFT BRACKET, RIGHT
PARENTHESIS, LEFT PARENTHESIS, PLUS SIGN, MINUS SIGN, OR EQUAL SIGN. SUB-FIELDS ARE
SEPARATED BY A COMMA OR A COMMA FOLLOWED BY ONE OR MORE BLANKS, FIELDS ARE SEPARATED
BY ONE OR MORE BLANKS. THE FIRST FIELD MUST HAVE ONLY ONE SUB-FIELD, THIS FIELD IS
CA~LED THE SGS LABEL.
SGS.S HAVE THE FOLLOWING FORM.
LABEL

Sll,S12, •••• SlK

S21,S22, ••• ,S2L

•••

SN1,SN2, ••• ,SNM

A STATEMENT MAY BE CONTINUED ON THE FOL~OWING CARD BY PLACING A SEMI-CO~ON
THE LAST FIELD CODED ON THE LINE. NOTE THAT THE LABEL NEED NOT START IN
COLUMN 1.
FOL~OWING

18.3.4.

19

18

PROGRAMMERS REFERENCE

CORRECTIONS

THE SGS FILE MAY BE FOLLOWED BY A FILE OF USER CORRECTIONS (TEMPORARY
CORRECTIONS) AND A FILE OF SYSTEMS PROGRAMMER CORRECTIONS (PERMANENT CORRECT IONS).
THE CORRECTIONS ARE OF THE FORM DESCRIBED IN THE SECTION 'FORMAT OF CORRECTION LINES.
(5.6.3). SPECIAL CARE MUST BE TAKEN WHEN CHANGING CORRECT ION IDENTIFICATION
CHARACTERS. SINCE SKELETON, PERMANENT, AND USER CORRECTION WILL BE MERGED, THEY MUST
HAVE THE SAME IDENTIFICATION CHARACTERS ACTIVE AT ANY GIVEN POINT. IN THE SKELETON
FI~E, THE FIRST CHARACTER OF A CORRECTION IDENTIFICATION MAY NOT BE A POUND SIGN (")
OH A PLUS SIGN (+); AND IN THE PERMANENT, OR TEMPORARY FILE IT MAY NOT BE AN
ASTERISK(*), OR A LEFT BRACKET ([).
ALL CORRECTIONS TO AN ELEMENT MUST BE GROUPED, ORDERED, AND PRECEDED BY CARD
WITH AN ASTERISK IN COLUMN ONE, FOLLOWED BY THE NAME OF THE ELEMENT AND VERSION TO
WHICH THE CORRECTIONS APP~y. THE ELEMENT NAME AND VERSION MUST BE SEPARATED BY A
SLASH(/). PERMANENT AND TEMPORARY CORRECTIONS WILL BE INTERNALLY STORED AND MAY BE
~EFERENCED BY A 'CORRECT. DIRECTIVE.

PAGE:

--i

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

18.3.5.

SYSTEM

~------.

18
SECTION:

20
PAGE:

SKELETON

THE SGR WILL PRODUCE THE RUN DECK FROM A SKELETON (FURNISHED BY THE SYSTEMS
PROGRAMMER WITH THE SYSTEM.S SYMBOLIC ELEMENTS) BY REFERENCING THE SGS.S FOR
INFORMATION. THE SKELETON IS AN ELEMENT OF CARDS TO BE EDITED AND INSERTED IN THE
RUN DECK, AND CARDS TO DIRECT THE SGR. THE SKELETON IS PROCESSED SEQUENTIALLY AND
THE CARDS 'ARE INTERPRETED, EDITED AND ADDED TO THE RUN DECK AS THEY ARE ENCOUNTERED.
PERMANENT AND TEMPORARY CORRECTIONS ARE MERGED WITH THE RUN DECK AS THE SKELETON IS
PROCESSED. CONFLICTS IN LINE NUMBERS AND CORRECTIONS ARE DETECTED AND NOTED,
THE SKELETON IS COMPRISED OF THREE TYPES OF CARDS.
1. CARDS TO DIRECT THE SGR.
2. CARDS TO BE EDITED AND ADDED TO THE RUN DECK.
3. CARDS TO ENTER THE RUN DECK DIRECTLY.
DIRECTIVE CARDS IN THE SKELETON ARE RECOGNIZED BY AN ASTERISK IN COLUMN 1 AND A
SECOND FIELD CONTAINING ONE OF THE FOLLOWING:
CORRECT
END
IF
ELSE
INCREMENT
LOOP
DEFlNE
PROCESS
18.3.5.1.

SYSTEM GENERATION STATEMENT REFERENCES

DIRECTIVE CARDS AND CARDS TO BE EDITED REFERENCE INFORMATION ON SGS'S IN ANY OF
THE FOUR WAYS GIVEN BELOW. L INDICATES A SGS LABEL. AND N, F, AND S REPRESENT
INTEGERS.
1. [L]
2, [L,N]
3. [L,N,F]

.Lt.

REPRESENTS THE NUMBER OF SGS'S WITH THE
LABEL
REPRESENTS THE NUMBER OF FIELDS ON THE N'TH
SGS WITH THE LABEL 'L'
REPRESENTS THE NUMBER OF SUB-FIELDS IN THE
F.TH FIELD ON THE N.TH 5GS WITH THE LABEL

'L' •

4. [L,(J,F,S] REPRESENTS THE CONTENTS OF THE S.TH SUB ...

FIELD IN THE F'TH FIELD ON THE NtTH SGS
WITH THE LABEL 'L ••

ANY CARD NOT REcOGNIZED BY THE SGR IS SEARCHED FOR ANY OF THE ABOVE REFERENCES.
IF NONE IS FOUND THE CARD IS ADDED TO THE RUN DECK. IF A REFERENCE IS FOUND, THE
INFORMATION IS RETRIEVEO FROM THE SGS AND SUBSTITUTED FOR THE REFERENCE. WHEN ALL
REFERENCES ON THE SKELETON CARD HAVE BEEN RETRIEVED AND SUBSTITUTED, THE CARD IS
ADDED TO THE RUN DECK, IF THE INFORMATION CANNOT BE FOUND ON ANY OF THE SGS'S, THE
CARD IS NOT ADDED TO THE RUN UECK AND PROCESSING IS CONTINUED WITH THE NEXT SKELETON
CARD.
18.3.5.2.

CORRECT DIRECTIVE CARD

THE CORRECT DIRECTIVE CARD IS NECESSARY FOR THE INSERTION OF SYSTEM PROGRAMMER
AND USER CORRECTIONS INTO THE RUN DECK, THE END DIRECTIVE CARD IS USED IN
CONJUNCTION WITH THE CORRECT CARD AS SHOWN BELOW.

*

CORRECT -NAME VERSION

*

END

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM
SECTION:

18

ALL CORRECTIONS TO THE ELEMENT NAME/VERSION WILL BE INSERTED AT THE PROPER POINT
IN THE RUN DECK BETWEEN THE DIRECTIVE CARDS. USER. SySTEM PROGRAMMER. AND SKELETON
CORRECTION CARDS WILL BE MERGED AND CHECKED FOR CONFLICTING CORRECTIONS. OTHER FORMS
OF THE CORRECT DIRECTIVE CARD ARE:
* CORRECT
* CORRECT

NAME VERSION PERMANENTLY
NAME
PERMANENTLY

THESE CARDS ARE USED IN CONJUNCTION WITH THE END DIRECTIVE AS ABOVE. BUT ONLY
SYSTEMS PROGRAMMER CORRECTIONS ARE ADDED TO THE RUN DECK,
THE NAME AND VERSION ON A CORRECT DIRECTIVE MUST BE SEPARATED BY AT LEAST ONE
SPACE. WHEN A CORRECT OIRECTIVE IS ENCOUNTERED. SGR IS CONDITIONED TO MERGE THE
CORRESPONDING TEMPORARY AND/OR PERMANENT CORRECTIONS INTO THE RUN STREAM. A
THREE-WAY MERGE WILL TAKE PLACE WHEN A CORRECTION APPEARS IN THE SKELETON FILE. THE
*END DIRECTIVE ASSOCIATED WITH THE *CORRECT DIRECTIVE WILL CAUSE ALL TEMPORARY AND/OR
PERMANENT CORRECTIONS WHICH ARE NOT ALREADY ACCESSED TO BE MERGED AND INSERTED IN THE
RUN STREAM. CONFLICTS IN LINE NUMBERS WILL BE NOTED AND INSERTED OR BYPASSED
ACCORDING TO THE FOLLOWING RULE: TEMPORARY CORRECTIONS WILL BE GIVEN THE HIGHEST
O~DER OF PRIORITY. THEN PERMANENT CORRECTIONS. AND FINALLY SKELETON CORRECTIONS.
ANY TEMPORARY CORRECTIONS APPLIED TO A SOURCE ELEMENT BY THE SKELETON MUST OCCUR
PRIOR TO ANY 'PERMANENT ONLY' CORRECTIONS. PERMANENT FILES ARE DELETED FROM STORAGE
AFTER BEING ACCESSED AS 'PERMANENT ONLY'.
18.3.5.3.

(

IF DIRECTIVE CARD

THE IF DIRECTIVE CARD IS USED TO CONDITIONALLY SKIP.A SEQUENCE OF SKELETON CARDS.
THE END DIRECTIVE CARD IS ALSO USED IN CONJUNCTION WITH THE IF CARD AS SHOWN BELOW.
THE IF DIRECTIVE CARD CAN BE USED IN ONE OF TWO WAYS. THE FIRST IS:
* IF


3. 

= ::



:=

(BOOLEAN OPERAND>

::



:=

==
I
 OR
I
NOT 
(NUMBER)/(ALPHA8ETIC>1
(SGS INTEGER REFERENCE>

THE PROPER FORMS ARE THUS,
* IF (BOOLEAN EXPRESSION> THEN
AND
* INCREMENT  TO (FINAL VALUE>
18.3.5.8
NESTING
NESTING OF DIRECTIVES IN SGR IS LIMITED ONLY BY SIZE OF CORE, AND SGR WILL
REQUEST CORE DYNAMICALLY AFTER THE INITIAL AREA IS USED. BECAUSE OF THE NATURE OF
THE NEST CAPABILITY, RULES FOR *END DIRECTIVES MUST BE ADHERED TO STRICTLY. THE
RESULTS WHEN THESE RULES ARE BROKEN ARE INDETERMINATE.
18.3.6.

SKELETON 'ORRECTIONS

THE SKELEToN IS AN ELEMENT COMPRISED OF DATA ITEMS, CORRECTION ITEMS, AN CONTROL
ITEMS, CONTRO~ ITEMS WILL BEGIN WITH A POUND SIGN (~) INSTEAD OF THE CONVENTIONAL
MASTER SPACE (Q). CORRECTION ITEMS FOR UPDATING THE SKELETON MUST CONTAIN A PLUS (+)
SIGN IN COLUMN ONE,
IT SHOULD BE NOTED THAT CORRECTIONS AND ADDITIONS IN THE SKELETON SHOULD CANCEL
EACH OTHER OUT. THIS IS NECESSARY SINCE THE SKELETON ELEMENT IS USED FOR EACH
GENERATION, AND ADDITIONS OR DELETIONS WOULD THEREFORE BE CUMULATIVE
18.3.7.

(-

THE
ABC ~
DE F GH-

OPTIONS
FOLLOWING OPTIONS WILL BE RECOGNIZED BY SGRf
FORM OUTPUT ELEMENT RUN STREAM EVEN IN THE CASE OF ERRORS.
INHIBIT EXECUTION OF THE RUN ~TREAM.
SINGLE SPACE ALL PRINTING.
INHIBIT PUNCHING OF REVISED TEMPORARy (USER) CORRECTIONS,
PRINT INPUT SKELETON,
PRINT CORRECTION TO THE SKELETON.
PRINT REVISED SKELETON.
PRINT PERMANENT (SYSTEM PROGRAMMER) CORRECTIONS,

23
PAGE:

UNIVAC 1108 OPERATING

JP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

SECTION: 18

PAGE:

24

c
I - PRINT TEMPORARY (USER) CORRECTIONS.
J - PRINT REVISED TEMPORARY (USER) CORRECTIONS.
K - PRINT SGS'S.
L - PUNCH THE RUN STREAM.
M - PRINT THE RUN STREAM. 18,3.8 EXAMPLE
A, SKELETON ELEMENT 'SKELNAME'
URUN
*DEFINE ASM
*CORRECT
[t#1 1
I'fASM [t#1J,[U2l
-55,56

*INCREMENT A TO 2
*IF [DEMAND,A,l,ll:MAXIMUM
L
AO,[OEMAND,A,3,1J"U
*END
*IF
[DEMAND,A,l,ll:MINIMUM
L Al,[DEMAND,A,3,1J"U
*END
*LOOP
*END
*END
UASG,X
SYSTEM
ASM
*PROCESS
SOURCE
OBJECT
UEND
B. CAL.LING SEQUENCE
rolXQT, A,L
SGR
SKELETON
SKELNAME
fOlEOF
DEMAND MAXIMUM PERCENTAGE 70
OEMANL) MINIMUM PERCENTAGE 20
(,lEOF
*SOURCE
-8,9

J

r.lEOF

START

-5,6

(,lEOF
fOlEND

C. OUTPUT RUN STREAM
folRUN
folASG,X
SySTEM
(,lASM
SOURCE,OBJECT
-5,6
-8,9
-55,56

J

START

L

AO,70"U
A1r2Q."U

L
100END

D.

UPDATED USER CORRECTIONS

-6,7
J

START

c

UNIVAC 1108 OPERATING

UP-4144

EXEC B

Rev. 1

19.

SYSTEM

PROGRAMMERS REFERENCE

UTILITY ROUTINES

19. 1 •

CONVERSION AIDS

TO AID INSTALLATIONS IN THE TRANSITION FROM OTHER COMPUTERS TO THE UNIVAC 110S, A
SET OF CONVERSION AID ROUTINES ARE INCORPORATED INTO THE 1108 EXECUTIVE SYSTEM.
THOSE CONVERSION ROUTINES DESIRED BY AN INSTALLATION WILL BE INCLUDED IN THE SySTEMS
LIBRARY, AND DEFINED AS SYSTEMS PROCESSORS AT SYSTEM SET UP TIME. THE ROUTINES MAY
BE CALLED AS DESIRED BY USE OF THE EXECUTIVE PROCESSOR CALL STATEMENT (CHAPTER 5.6)
FOR THE INITIAL 1108 SOFTWARE SYSTEM, THE FOLLOWING CONVERSION AID ROUTINES WILL
BE PROVIDED:
19.1.1.

UNIVAC 1107 TO UNIVAC 1108

THIS PROCESSOR WILL CONVERT MAGNETIC TAPES CREATED BY THE 1107 COMPLEX UTILITY
ROUTINE (CUR) TO MAGNETIC TAPES ACCEPTABLE AS INPUT TO AN 1108 PROGRAM-FILE. THE
PROCESSOR WI~L ACCEPT 1107 SYMBOLIC ELEMENTS, COBOL LIBRARY ELEMENTS, AND PROCEDURE
ELEMENTS AND CONVERT THEM TO 1108 SYMBOLIC ELEMENTS, COBOL PROCEDURE ELEMENTS, AND
ASSEMBLER PROCEDURE ELEMENTS RESPECTIVELY. ALL OTHER 1107 ELEMENT TYPES WILL BE
IGNORED.
THE PROCESSOR RESIDES IN THE SYSTEMS LIBRARY AND IS INITIATED BY THE FOLLOWING
PROCESSOR CALL COMMAND:

(-

QCON78,OPTIONS

FILE1.,FILE2.

THE AVAILABLE OPTIONS WHICH INDICATE ELEMENT TYPE ARE AS FOLLOWS:
S
SYMBOLIC ELEMENTS
C
COBOL LIBRARY ELEMENTS
P
PROCEDURE ELEMENTS
IF NONE OF THE OPTIONS ARE SPECIFIED, ALL ELEMENTS OF TYPE '5., 'C', AND .p, ARE
CONVERTED.
'FILE1.' IS THE INPUT TAPE FILE OF 1107 ELEMENTS AND 'FILE2,' IS THE oUTPUT TAPE
FILE OF 1108 ELEMENTS. BOTH 'FILE1.' AND 'FILE2' MUST HAVE BEEN PREVIOUSLY ASSIGNED
TO THE RUN WITH THE 'ASG' CONTROL COMMAND, ONt CALL TO QCON78 CONVERTS ONE FILE, TWO
CALLS CONVERTS TWO FILES, ETC. IT SHOULD BE NOTED THAT A PERIOD IS REQUIRED TO DEFINE
THE FILE NAME, THE FILES ARE NEVER REWOUND AND END OF FILE MARKS ARE WRITTEN AFTER
EACH FILE CONVERTED.
COBOL PROCEDURES ARE HANDLED SOMEWHAT DISTINCTLY. EAC~ PROCEDURE IS SURROUNDED BY
A PROC LINE AND AN END LINE.THE LABEL ON THE PROC LINE IS THAT OF THE ELEMENT NAME
AND IT IS NOT EXTERNALLY DEFINED. THEREFORE , IN ORDER TO USE THE PROCEDURE IN A
COMPILATION IT WILL BE NECESSARY TO PDP IT.
19.2.

OUTPUT EDITING ROUTINE

19.2.1.

ORGANIZATION

THE OUTPUT EDITING ROUTINE IS AN INTERPRETIVE ROUTINE WHICH WILL PERFORM EDITING
FUNCTIONS FOR OUTPUT PRODUCED ON THE LINE PRINTER, THE CARD PUNCH, AND THE CONSOLE.
THE INTERPRETIVE II~STRUCTIONS PERFORMED BY THE ROUTINE ARE CONSTRUCTED ALONG MUCH THE
SAME LINES AS ARE MACHINE LANGUAGE INSTRUCTIONS:

------------------------------------------F
M
D
T
: X :
------------------------------------------2
5
7
16

1

19
SECTION:

PAGE:

~~~~~.~-

~_._.-

-~

~~

~~

--~------------~

[JP-4144
Rev. 1

UNIVAC

108 OPERATING

EXEC B

..

~-~~~~~------

,-----~---

~~

SYSTEM

PROGRAMMERS REFERENCE

SEctiON:

19

2
PAGE:

c
(F)
(T)
(D)
(X)

-- FUNCTION CODE
-- TYPE WHEEL, ETC,
-- DECIMAL POINT LOCATION, ETC.
-- SPECIFIES INDIRECT ADDRESS AND USE OF THE SIMULATED
INDEX REGISTER
(M) -- ADDRESS (MEMORy LOCATION OF DATA, ETC.)

THE AVAILABLE FUNCTIONS ARE LISTED BELOW WITH THEIR FUNCTION CODES IN OCTAL AND
THE NAME OF THE CORRESPONDING PROCEDURE CELL.
EDITING FUNCTIONS
E$O
01--DECIMAL
E$O
02--0CTAL
E$e
03--BINARY
E$e
04--ALPHANUMERIC CHARACTERS
E$A
05--ALPHANUMERIC WORDS
E$E
06--FLOATING-POINT (FORTRAN E)
E$F
07--FLOATING TO FIXED (FORTRAN F)
E$DE
26--DOUBLE PRECISION FLOATING POINT
E$DF
27--DOUBLE PRECISION FLOATING TO FIXED
OUTPUT FUNCTIONS
E$WT10--WRITE AND TERMINATE
E$W
l1--WRITE
E$WS
12--WRITE AND SAVE
MODAL FUNCTIONS
E$SCL
13--SET SCALE
E$PNT
14--SET POINT
E$FLD
15--SET FIELD
E$INDX
16--SET INDEX
E$OVRP
17--0VERPUNCH
CONTROL FUNCTIONS
E$TERM
20--TERMINATE
E$LINK
21--LINK
E$JUMP
22--JUMP
E$RPT
23--REPEAT
ESCLR
24--CLEAR
THE ROUTINE IS CALLED BY THE FOLLOWING INSTRUCTION:
LMJ
11, EOUT$
THERE ARE TWO ENTRY POINTS TO THIS SUBROUTINE. THE NORMAL ENTRY POINT IS EOUTS.
THE OTHER, EOUTR$, IS THE POINT FOR RE-ENTRY AFTER E$TERM (TERMINATE) FUNCTION AND IS
DISCUSSED UNDER TERMINATE.
THE ADDRESSED WORD IN THE M DESIGNATOR MAY BE EITHER IN CONTROL OR CORE MEMORY.
ANY WORD, EVEN A VOLATILE REGISTER, IS PERMISSIBLE I BUT IF REGISTER 11 IS ADDRESSED,
THE LOCATION OF THE INTERPRETIVE WORD WHICH REFERENCES 11 WILL BE PUT OUT. ALL
REGISTERS, INCLUDING VOLATILE ONES, ARE SAVED AND RESTORED. THE X DESIGNATOR IS USED
TO SPECIFY INDIRECT ADDRESSING AND THE USE OF THE SINGLE SIMULATED INDEX REGISTER.
ITS PERMISSIBLE VALUES ARE

o
1
2
3

NO ACTION
USE ADDRESS INDIRECTLY
APPLY SIMULATED INDEX REGISTER
APPLY SIMULATED INDEX REGISTER THEN USE ADDRESS
INDIRECTLY

INDIRECT ADDRESSING IS pERMITTED TO ONE LEVEL ONLY AND THE B, H, AND I DESIGNATORS
OF THE INDIRECTLY ADDRESSED WORD ARE IGNORED. HOWEVER, IT IS POSSIBLE TO INDIRECTLY
ADDRESS CONTROL MEMORY. ALL MODES MAY BE USED WITH INDIRECT ADDRESSING.

c

UP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC

PROGRAMMERS REFERENCE

a

SYSTEM

THE VARIOUS FUNCTIONS ARE DESCRIBED IN DETAIL. BEL.OW, THEY ARE AL.L. CAL.L.ABL.E AS
PROCEDUKES. EACH OF THE PROCEDURE CALL.S WIL.L GENERATE ONE WORD IN THE PROPER FORMAT,
THE PARAMETERS OF THESE PROCEDURES ARE INTERPRETED DIFFERENTL.Y DEPENDING ON THE
NUMBER WRITTEN. A SINGL.E PARAMETER IS TAKEN AS MI TWO PARAMETERS AS M AND x; THREE
PARAMETERS AS T, 0, AND MI AND FOUR AS T, 0, M, AND X. ANY MISSING PARAMETERS WIL.L
BE ASSUMED TO BE ZERO.
ENTRY TO THE GENERAL.IZED EDITOR MAy BE OBTAINED BY THE PROCEDURES ESOUT OR ESOUTR,
DEPENDING ON THE ENTRY POINT DESIRED. NO PARAMETERS ARE REQUIRED.
19.2.2,

THE EDITING FUNCTIONS

THESE FUNCTIONS ACTUALL.Y CONVERT THE INFORMATION TO BE PUT OUT, IN AL.L CASES
EXCEPT ESA, ALPHANUMERIC WORDS (SEE E$A BEL.OW), THE T FIEL.D SPECIFIES THE TYPE WHEEL.
AT WHICH THE RIGHT~MOST DIGIT, BIT, OR CHARACTER IS TO BE PRINTED.
ESD-... DECIMAL: THE ADDRESSED WORD IS TREATED AS IF IT WERE A SIGNED DECIMAL
INTEGER, AND IS EDITED WITHOUT A DECIMAL POINT UNLESS A SET POINT (1~) IS IN EFFECT.
LEADING ZEROS TO THE L.EFT ARE SUPPRESSED AND A MINUS SIGN, IF ANY, IS PRINTED
IMMEDIATELY TO THE LEFT OF THE NUMBER (ALSO SEE OVERPUNCH (17», IF THE VALUE IS
ZERO, A SINGLE ZERO WILL BE PRINTED, IF A SET POINT IS IN EFFECT, THE DECIMAL NUMBER
IS ASSUMED TO HAVE THE STATED POINT SPECIFIED BY THE SET POINT AND THE 0 FIELD
SPECIFIES THE NUMBER OF DECIMAL DIGITS TO BE PRINTED TO THE RIGHT OF THE DECIMAL
POINT, IF A SET FIELD (15) WITH 0=0 IS IN EFFECT, THE SPECIFIED FIELD IS TREATED AS
AN UNSIGNED DECIMAL INTEGER,
E$O--OCTAL.: THE D LOW-ORDER BITS OF THE ADDRESSED WORD ARE EDITED AND PRINTED AS
(0+2)/3 OCTAL. DIGITS, UNSIGNED, FOR A FUL.L. OCTAL, BINARY, OR ALPHANUMERIC CHARACTER
WORD, 0 MUST ALWAYS BE GIVEN AS 36,
E$B--BINARY: THE 0 L.OW-ORDER BITS OF THE ADDRESSED WORD ARE EDITED AS 0 BINARY
DIGITS UNSIGNED,
E$C--AL.PHANUMERIC CHARACTERS: THE D L.OW-ORDER BITS OF THE ADDRESSED WORD ARE
EDITED AND PRINTED AS (0+5)/6 ALPHANUMERIC CHARACTERS IN FIELD DATA CODE,
ESA--ALPHANUMERIC WORDS: THE 0 WQRDS BEGINNING WITH THE ADDRESSED WORD ARE EDITED
AS 6*0 CHARACTERS IN FIELD DATA CODE, FOR THIS EDITING FUNCTION ONLY, THE T FIELD
SPECIFIES THE PRINT POSITION AT WHICH THE LEFT-MOST CHARACTER IS PRINTED,
ESE--FLOATING-POINT (FORTRAN E): THE ADDRESSED WORD IS EDITED AS A FLOATING-POINT
NUMBER WITH D SIGNIFICANT DIGITS, NORMALL.Y THESE WIL.L. AL.L PRINT TO THE RIGHT of THE
DECIMAL POINT (ALSO SEE SET· ~CAL.E). A DECIMAL EXPONENT CONSISTING OF A SIGN AND TWO
DIGITS WIL.L BE INSERTED IMMEDIATELY TO THE RIGHT OF THE SIGNIFICANT PORTION. IF THE
FLOATING-POINT NUMBER IS NEGATIVE, A MINUS SIGN WILL BE INSERTED IMMEDIATELY TO THE
LEFT OF THE NUMBER (ALSO SEE OVERPUNCH). IF THE ADDRESSED WORD IS MINUS ZERO, NO
EFFECT WILL OCCUR, AND THE FIEL.D WILL BE LEFT BLANK.
E$F--FL.OATING TO FIXED (FORTRAN F): THE ADDRESsED WORD IS ASSUMED TO BE A
FLOATING-POINT NUMBER AND IS EDITED TO FIXED-POINT WITH D PLACES FOLLOWING THE
DECIMAL POINT. NEGATIVE NUMBERS, INCLUDING MINUS ZERO, ARE TREATED AS ABOVE,
ESDE--DOUBL.E PRECISION FLOATING POINT: THIS EDITING FUNCTION IS THE SAME AS THE
POINT (06) FUNCTION WITH THE ADDRESSED WORD AND THE ADDRESSED WORD PLUS ONE
EDITED AS A DOUBL.E PRECISION FLOATING POINT NUMBER. A DECIMAL. EXPONENT CONSISTING OF
A SIGN AND THREE DIGITS WILL BE INSERTED IMMEDIATELY TO THE RIGHT of THE SIGNIFICANT
PORTION.
FLOATI~G

ESDF--DOUBLE PRECISION FLOATING TO FIXED: THIS EDITING FUNCTION IS THE SAME AS THE
FLOATING TO FIXED (07) FUNCTION WITH THE ADDRESSED WORD AND ADDRESSED WORD PLUS ONE
EDITED AS A DOUBLE PRECISION FLOATING POINT NUMBER.
EXAMPLE OF EDITING FUNCTIONS

3

19
SECTION:

PAGE:

UNIVAC 1108 OPERATING

UP-4144
Rev.l

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

19

4
PAGE:

SECTION:

THE EDITING FUNCTIONS PERFORM THE GENERATION OF A FORM WORD WHICH WAS DISCUSSED
EARLIER, IT IS NECESSARY TO CALL EOUT$ PRIOR TO THE FUNCTIONS THEMSELVES. AFTER
CALLING EOUT$ THE EDITORS ARE INVOKED TO INDICATE THE. TYPE OF TRANSLATION,·
SUPPOSE IT IS DESIRED TO EDIT TWO WORDS INTO DIFFERENT FORMATS AND STORE THEM AS
PART OF A LINE TO BE OUTPUT, ONE METHOD IS SHOWN BELOW:
E$OUT
E$A
E$O

1,1,M. EDIT ALPHA WORD AT M TO POSITION 1
18,1,M1. EDIT DECIMAL VALUE AT M1 TO POSITION 18
• (M,=060710111213 & (M1)=0606061626364

UPON RETURN TO THE NEXT INSTRUCTION THE FIRST THREE WORDS OF THE PRINT BUFFER ARE:
AbCDEF
19.2.3,

1234
THE OUTPUT FUNCTIONS

THE OUTPUT FUNCTIONS SERVE TO TRANSMIT THE EDITED LINE TO AN OUTPUT DEVICE' THE
PRINTER, THE CARD PUNCH, OR THE CONSOLE, THE DEVICE TO BE USED IS DETERMINED BY THE
o Flt:.LD:
PRINTER
D=O
CAKD PUNCH 0=1
CONSOLE
0=2

f'"

THE WORD OR CHARACTER COUNT IS GIVEN IN THE T FIELD. THIS COUNT MUST BE GIVEN (IT
IS NOT ASSUMED MAXIMUM IF IT IS GIVEN AS ZERO>, FOR pRINTER, THE WORD COUNT IS
NOR~ALLY 22; FOR CARD PUNCH, NORMALLY 14.
FOK THE CONSOLE T IS A CHARACTER COUNT,
FUR THE PKINTER, THE M DESIGNATOR SERVES TO SPECIFY THE NUMBER OF LINES TO BE SPACED,
A VALUE GREATER THAN THE LENGTH OF A LOGICAL PAGE WILL RESULT IN PRINTING ON THE
FIRST LINE OF THE NEXT PAGE. FOR THE PUNCH AND CONSOLE THE M DESIGNATOR IS IGNORED,
E$WT--WRITE ANJ TERMINATE: THE EDITED IMAGE IS TRANSMITTED TO THE SPECIFIED
OEVICE AND THE ROUTINE KETURNS TO THE NEXT INSTRUCTION IN MACHINE LANGUAGE MODE.
IMAGE IS RESET TO BLANKS.

~/

THE

ESWS--WRITE AND SAVE: THE EDITED IMAGE IS TRANSMITTED TO THE SPECIFIED DEVICE AND
THE ROUTINE CONTINUES TO THE NEXT INSTRUCTION IN THE INTERPRETIVE MODE. THE IMAGE IS
LEFT AVAILABLE FOR USE ~Y FURTHER OUTPUT FUNCTIONS OR FURTHER EDITING,
19.2,4.

THE MODAL FUNCTIONS

THE MODAL FUNCTIONS SERVE TO ENTER INFORMATION WHIcH AFFECTS THE INTERPRETATION OF
ONE OR MORE OF THE INSTRUCTIONS WHICH FOLLOW. FIVE MODAL INSTRUCTIONS ARE AVAILABLE:
ESSCL--SET SCALE: THE CONTENTS OF THE ADDRESS FIELD ARE TREATED AS A SIGNED POWER
OF 10 TO ~~ APPLIEO TO ANY FLOATING-POINT OR FLOATING TO FIXED FUNCTION WHICH FOLLOWS
THE SET SCALE. FOR FLOATING-POINT, THE SCALE IS THE NUMBER OF DIGITS TO BE PRINTED
TO THE LEFT OF THE DECIMAL POINT. THE EXPONENT FIELD IS REDUCED ACCORDINGLY, SO THAT
THE RESULTING VALUE IS THE SAME AS IF NO SET SCALE MODAL WERE IN EFFECT, NEGATIVE
VALUES OF THE ADDRESS (THE 16-8IT ONES, COMPLEMENT) WILL INTRODUCE LEADING ZEROS
AFTER THE DECIMAL POINT AND INCREASE THE EXPONENT FIELD ACCORDINGLY,
FOR FLOATING TO FIXED CONVERSION, THE ACTUAL VALUE OF THE RESULTING NUMBER IS
ALTERED BY ~ULTIPLYING IT BY THE POWER OF 10 INOICATED BY THE ADDRESS. THE SET SCALE
MUUAL REMAINS IN EFFECT UNTIL IT IS COUNTERMANDED BY A NEW SET SCALE. UPON INITIAL
ENTRY TO EOUTS, TAE SCALE IS AS~UMED TO BE O.
ESPNT--SET POINT: THE SET POINT MODAL SPECIFIES THE POSITION OF THE BINARY POINT
FOR THE NEXT EOITING FUNCTION TO BE ENCOUNTERED (PRESUMABLY A DECIMAL EDITING
FUNCTION). IT ~EMAINS IN EFFECT ONLY FOR THE SINGLE EDIT. THE ADDRESS OF THE SET

c

UP-4144

UNIVAC

Rev. 1

1108

EXEC B

OPERATING

SYSTEM

19

PROGRAMMERS REFERENCE

POINT GIVES THE NUMBER OF BITS FOLLOWING THE BINARY POINT.
PERMITTED (SEE SET FIELD).

SECTION:

NEGATIVE VALUES ARE

E$FLD--SET FIELD: THE SET FIELD MODAL IS USED TO SPECIFY A SUBFIELD OF THE NEXT
WORD TO OCCUR (PRESUMABLY A DECIMAL, OCTAL, BINARY, OR ALPHANUMERIC CHARACTERS
FUNCTION). THE T FIELD SPECIFIES THE LEFT-HAI~D MARGIN AND THE M FIELD THE RIGHT-HAND
MARGIN. THE BITS OF THE 1108 WORD ARE NUMBERED, FOR THE PURPOSES OF THIS FUNCTION,
FROM LEFT (00) TO RIGHT (35). THE D FIELD SPECIFIES EXTENSION OF SIGN; IF IT IS
NON-ZERO, THE FIELD IS TREATED AS SIGNED. A SET FIELD WITH 0
0 AND T
0 MAY BE
USED TO TREAT FIELDS. INCLUDING THE SIGN BIT, AS UNSIGNED. UNLESS M 35 (I.E., A
WHOLE WORD MUST ALWAYS BE SIGNED IN THE EVENT A SIGN IS APPLIED).

=

= =

THE SET FIELD MODAL REMAINS IN EFFECT ONLY FOR THE NEXT FUNCTION ENCOUNTERED. IF
BOTH A SET FIELO MODAL AND A SET POINT MODAL ARE IN EFFECT WHEN EDITING OCCURS, THE
SET FIELD MODAL WILL BE APPLIED FIRST. IN THIS CASE, THE SET POINT SPECIFIES THE
BINARY POINT COUNTING FROM THE RIGHT-HAND END OF THE SPECIFIED FIELD.
E$INUX--SET INDEX: THE SET INDEX IS USED TO ADDRESS A QUANTITY IN MEMORY WHICH IS
TO BE LOADED INTO THE SINGLE SIMULATED INDEX REGISTER. FOR ANY FUNCTION WHICH
ADDRESSES MEMORY (INCLUDING THIS ONE), THE PRESENCE OF A 1 BIT IN THE INCREMENT (H)
PORTION OF THE ADDRESS WILL CAUSE THE SIMULATED INDEX TO BE ADDED TO THE SPECIFIED
ADDRESS BEFORE ACCESS IS MADE. THE LEFT HALF OF THE INDEX-REGISTER WORD IS IGNORED.
IF THE D FIELD IS NONZERO, THE CONTENTS OF THE M FIELD (WITH SIGN EXTENSION) ARE
LOADED INTO THE SIMULATED INDEX REGISTER. THE SET INDEX MODAL REMAINS IN EFFECT
UNTIL IT IS COUNTERMANDED BY ANOTHER SET INDEX.
E$OVHP--OVERPUNCH: THE OVERPUNCH MODAL SPECIFIES THAT ANY MINUS SIGNS PRODUCED BY
THE EDITING FUNCTIONS AHE TO BE REMOVED FROM THEIR POSITIONS IN FRONT OF THE EDITED
NUMBERS AND PLACED AS l1-PUNCHES OVER THE LOW-ORDER DIGITS. IN THE CASE OF FLOATING
POINT EDITING, THE SIGN OF THE MANTISSA IS PLACED OVER THE LOW-ORDER DIGIT OF THE
MANTISSA AND THE SIGN OF THE EXPONENT OVER ITS LOW-ORDER DIGIT. THE SPACE THAT WOULD
NORMALLY CONTAIN THE SIGN OF THE EXPONENT IS OMITTED. THE OVERPUNCH MODE IS
INITIATED BY ITS OCCURRENCE WITH ADDRESS 1. IT IS COUNTERMANDED BY ITS OCCURRENCE
WITH ADDRESS O. UPON INITIAL ENTRY TO EOUT$, THE OVERPUNCH MODE IS ASSUMED TO BE
OFF.
19.2.5.

THE CONTROL FUNCTIONS

THE CONTROL FUNCTIONS SERVE TO INTRODUCE INTO THE INTERPRETIVE LANGUAGE SOME OF
THE CONTROL OPERATIONS AVAILABLE IN MACHINE LANGUAGE.
E$TERM--TERMINATE: THE TERMINATE CONTROL CAUSES THE ROUTINE TO RETURN TO THE NEXT
INSTRUCTION IN MACHINE LANGUAGE. UPON RE-ENTRY TO THE ROUTINE AT THE POINT EOTR$,
ALL COUNTERS, MODES IN EFFECT, INTEHPRETIVE SUBROUTINES, AND ANY PARTIAL IMAGE ARE
LEFT UNDISTUR~ED. IF RE-ENTRY IS MADE AT EOUT$, THESE ARE ALL CLEARED. ENTRY AT
EOUTR$ IS MADE BY THE INSTRUCTION
LMJ

11. EOUTR$

E$LINK--LINK: THE LINK CONTROL IS USED TO FORM SUBROUTINES IN THE EDITING
LANGUAGE. ITS EFFECTIVE ADDRESS SPECIFIES THE LOCATION OF THE ENTRY TO A SUBROUTINE.
SUBROUTINES MAY BE NESTED TO A DEPTH OF 10.
E$JUMP--JUMP: THE JUMP CONTROL wITH
INTERPRETIVE TRANSFER OF CONTROL TO THE
THE JUMP CONTROL SERVES AS A SUBROUTINE
INSTRUCTION FOLLOWING THAT LINK CONTROL
B£EN PEHFORMED.

A NON ZERO EFFECTIVE ADDRESS CAUSES AN
DESIGNATED LOCATION. IF THE ADDRESS IS ZERO,
EXIT. TRANSFER IS TO THE INTERPRETIVE
MOST RECENTLY EXECUTED FOR WHICH NO EXIT HAS

E$RPT--REPEAr: THE REPEAT CONTROL CAUSES THE NEXT SINGLE INTERPRETIVE INSTRUCTION
TO BE REPEATED A NUMBER OF TIMES SPECIFIED IN THE D FIELD OF THE REPEAT WORD. A
R~PEAT CONTROL PRECEDING A LINK WILL BE MLANINGLESS; FOR MULTIPLE EXECUTION OF A
LINK, THE ROUTINE EOUT$ ITSELF SHOULD BE CALLED WITHIN A MACHINE LANGUAGE LOOP. THE
T ANt) M FIELDS COrHAIN INCREMENTs'rO THE T ANUM FIELDS OF THE INSTRUCTION TO BE

5
PAGE:

-.-...

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

-.----~------

--

SYSTEM

PROGRAMMERS REFERENCE

SECTIO~: 19

PAGE:

6

c
REPEATED FOR EACH EXECUTION. ANY MODES SET BY THE MODAL INSTRUCTIONS WHICH WOULD BE
If~ EFFECT FOR THE FIRST EXECUTION OF A REPEATED INSTRUCTION REMAIN IN EFFECT FOR ALL
EXEC UTI ONS.
E$CLR--CLEAR!
19.2.6.

THE CLEAR CONTROL SETS THE IMAGE TO BLANKS.

EXAMPLES

SEVERAL EXAMPLES OF TYPICAL CALLING SEQUENCES TO EOUTS FOLLOW:
1.

THE FORTRAN INSTRUCTION
100

PRINT Ino, A, I, N, B, C
FORMAT (6X, E20~7, 120, 020, IP.2F20.6)

IS EQUIVALENT TO THE INTERPRETIVE SEQUENCE
ESOUT
ESE
26,7,A
E$O
46,0,1
E$O
66,0, N
E$SCL
1
E$F
86, 6; B
E$F
106, 6, C
E$WT
22, 0, 1
NEXT MACHINE LANGUAGE INSTRUCTION
2.

IF THIS LINE WERE TO BE PUT OUT ALSO 'ON THE CARD PUNCH,
WHOSE OUTPUT CODE IS 1, THEN THE LAST INTERPRETIVE
INSTRUCTION WOULD BE REPLACED By
E$WS
E$WT

14, 1, 0
22, 0, 1

ONLY THE FIRST 80 COLUMNS OF THE IMAGE WOULD BE PUNCHED.
3.

THE FORTRAN INSTRUCTION
PRINT 100,
100 FORMAT

(..I

(1),

(2016)

K 0)' L(I),M(l), 1=1, 4)

IS EQUIVALENT TO THE FOLLOWING INTERPRETIVE SEQUENCES:
E$f{PT
E$D
E$RPT
E$i)

E$RPT
E$D
E$RPT
E$D
E$WT

30, 4, 1
6, 0, ...1, 2
30, 4, 1
12, 0, K, 2
30, 4. 1
18. 0, L, 2
30. 4, 1
24, O. M, 2
22, 0, 1

c

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

APPENDIX A--DIAGNOSTIC MESSAGES

BAD RUN STATEMENT
THE RUN STATEMENT IS IMPROPERLY FORMATTED. TWO COMMON ~RRORS ARE TO HAVE A
MISSING RUN-ID OR ACCOUNTING FIELD. THIS MESSAGE WILL ONLY BE PRINTED FOR
DEMAND RUNS' FOR BATCH RUNS THE DEVICE IS PLACED IN THE RUN SEARCH MODE. IF
THE STATEMENT WAS SUBMITTED FROM A DEMAND TERMINAL, IT MAY BE IMMEDIATELY
RETYPED IN THE PROPER FORMAT.
COARSE SCHEDULER COULD NOT FIND PROGRAM
THE REQUESTED PROGRAM OR PROCESSOR IS NOT IN THE GIVEN FILE, LIB$, OR TPF$
(DEPENDING ON THE STATEMENT). IF THE RUN IS NOT DEMAND, IT IS TERMINATED.
COARSE SCHEDULER ENcOUNTERED FILE ERROR
THE FILE REQUESTED ON A QXQT OR PROCESSOR STATEMENT COULD NOT BE ASSIGNED.
IF THE RUN IS NOT DEMAND, IT IS TERMINATED.
DATA STATEMENTS ENCOUNTEREO--IGNORED
DATA STATEMENTS WERE ENCOUNTERED WHEN THE COARSE SCHEDULER WAS ATTEMPTING TO
READ CONTRoL STATEMENTS; I.E., A PROGRAM OR PROCESSOR WAS NOT IN CONTROL OF
THE RUN AT THE TIME THESE STATEMENTS WERE ENCOUNTERED.
~END

STATEMENT ENCOUNTERED BY SYSTEM--IGNORED
AN gEND STATEMENT WAS ENCOUNTERED WHEN THE COARSE SCHEDULER WAS ATTEMPTING
TO READ CONTROL STATEMENTS I I.E., THE QDATA pROCESSOR WAS NOT IN CONTROL OF
THE RUN AT THE TIME THIS STATEMENT WAS ENCOUNTERED.

QEOF STATEMENT ENCOUNTERED BY SYSTEM--IGNORED
AN QEOF STATEMENT WAS ENCOUNTERED WHEN THE COARSE SCHEDULER WAS ATTEMPTING
ToO READ CONTROL STATEMENTS I I.E., A PROGRAM OR PROCESSOR WAS NOT IN CONTROL
OF THE RUN AT THE TIME THIS STATEMENT WAS ENCOUNTERED.
ILLEGAL ACCOUNT NUMBER
THE ACCOUNT NUMBER ON THE RUN STATEMENT IS NOT IN THE INSTALLATION'S SUMMARY
ACCOUNT FILE AND THE OPERATOR HAS CHoSEN TO RE~ECT IT. THIS MESSAGE WILL
ONLY BE PRINTED FOR DEMAND RUNS. THE RUN STATEMENT MAY BE IMMEDIATELY
RETYPED WITH AN ACCEPTABLE ACCOUNT NUMBER.
INTERVENING STATEMENTS SKIPPED
A CONDITIONAL STATEMENT HAS BEEN ENCOUNTERED AND HAS CAUSED ONE OR MORE
CONTROL STATEMENTS TO BE BYPASSED.
OPERATOR TERMINATED RUN
1. THE OPERATOR REPLIED WITH AN X TO ~MSG STATEMENT WITH A W OPTIONI BOTH
BATCH AND DEMAND RUNS ARE TERMINATED IN THIS CASE.
2. THE OPERATOR TYPED AN UNSOLICITED X KEYIN FOR THIS RUN. THE MESSAGE IS
PRINTED ONLY FOR SATCH RUNS. AN UNSOLICITED X KEYIN FOR A DEMAND RUN SIMPLY
TERMINATES THE CURRENTLY EXECUTING PROGRAM.
REMAINING CONTROL STATEMENTS IGNORED
THE RUN HAS BEEN TERMINATED BECAUSE OF AN ERROR CONDITION AND THE REMAINING
CONTROL STATEMENT ARE NOT PROCESSED.
UNRECOVERABLE I/O ERROR WHEN READING FILE FFFFFFFFFFFF
THE COARSE SCHEDULER ENCOUNTERED AN UNRECOVERABLE 1/0 ERROR WHEN SEARcHING
FILE FFFFFFFFFFFF FOR A PROGRAM OR PROCESSOR. IF THE RUN IS NOT DEMAND, IT
IS TERMINATED.

c

1

Appendix A
SECTION:

PAGE:

c

UNIVAC 110a OPERATING

UP·4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

(
APPENDIX B--ERROR CODES

LIST OF ERROR CODES
TYPE
2
2
2

CODE
01
02
03

2

04

2

040

2

041

.3
.3

01

3
.3

.3
3
.3
3
.3
.3
.3
.3
.3
.3
.3
.3
.3
.3
3
3

02
03
04
05
06
020
021
022
023
024
025

034
035
036
037
040
041
042
077

01
4
4

02
03

4
4

04
05
06

4
4
4

010
011

4

012

4

013

4

014

1+

015

4

016

07

DESCRIPTION
ATTEMPT TO READ PAST END OF RUN FILE
TWO ERROR RETURNS IN A ROW TO A USER
UNRECOVERABLE I/O (TAPE OR DRUM) ERROR
IMAGE LENGTH IN A READ FILE IS GREATER THAN 15
PACKET ERROR (NOT INSIDE STORAGE LIMITS OR
ACROSS I AND 0 BANK)
MAXIMUM PAGES WITH OPTION TO KILL AT MAX.
PAGES
PAST END OF FILE
SECOND ABNORMAL RETURN FROM READ$
I/O (READ$)
IMLENGTH (READ$)
ADO FILE NOT ASG'D
READ ACCESS WORD FAILURE
ALT. FILE NOT ASSIGNED ON DEMAND OR RT RUN
CANNOT ASSIGN ALT. FILE
TyPE OF CALL DOES NOT MATCH TYPE of FILE
PACKET OUT OF LIMITS
READ$ FILE NOT ASSIGNED
FIRST ERROR ON RE'AD IN READ$ FILE
EXCEEDED PRA FILE
EXCEEDED PRA FILE
EXCEED PU$ FILE
EXCEED PR$ FILE
BUFFER OUT OF LIMITS
MAX PAGES
MAX CARDS
NO ADD NESTING
ER INDEX VALUE GREATER THAN DEFINED. THE
ACTIVITY IS TERMINATED
PACKET NOT WITHIN PROGRAM LIMITS
ILLEGAL ER INDEX VALUE WITHIN THOSE DEFINED.
THE ACTI~ITY IS TERMINATED
NO IDENTITY UPON AWAIT$ REQUEST
DUPLICATE OR INVALID ACTIVITY 10 REQUESTED
WHEN REFERENCING FORKING
REAL TIME PRIORITY IS NOT PERMITTED UNDER THE
ACCOUNT NUMBER USED
EXCEEDED RUN TIME
PACKET NOT IN USERS AREA (ER FACIL$)
DRUM READ ERROR WHILE PROCESSING ER FACIL$
PACKET SUPPLIED IN ER TO BPOOL$ IS NOT
COMPLETELY IN USER AREA
BUFFER AREA SUPPLIED IN ER TO BPOOL$ IS NOT
COMPLETELY IN USER AREA
BUFFER AREA SUPPLIED IN ER TO SPOOLS IS NOT
LA.RGE ENOUGH FOR 1 BUFFER OF LENGTH SPECIFIED
BUFFER SIZE SUPPLIED IN EH TO BPOOLS IS LESS
THAN 2 WORDS
PACKET SUPPLIED IN ER TO BJOIN$ IS NOT

1

Appendix B
SECTION:

PAGE:

--

UP-4144

Rev. 1

I

UNIVAC 110B

OPERATING

EXEC B

PROGRAMMERS REFERENcE

4

017

4

4

020
021

4

022

4

023

4

024

4

030

4

031

4
4

032
033

4

0.34

4

035

4

036

4

037

4

040

4
4

041
042

4

043

4

050
051
052

4

4

4

053
054
055

4

060

4

077

6

01

6

02

6

03

6

34

6
6

06

6

07

6

10

4
4

05

SYSTEM

f,'

COMPLETELY IN USER AREA
BUFFER AREA SUPPLIED IN ER TO BJOIN$ IS NOT
COMPLETELY IN USER AREA
FILE CONTROL TABLE NOT IN USERS AREA
NO ABNORMAL-, FILE ERROR-, OR DEVICE-EXIT
SPECIFIED IN CONTROL TABLE
BUFFER SIZE SUPPLIED BY ER TO BJOIN$ IS LESS
THAN 2 WORDS
CONTROL PACKET REFERENCED IN BJOIN$ CALLING
PACKET IS NOT COMPLETELY IN USER AREA
BUFFER AREA SUPPLIED IN ER TO BJOIN$ IS NOT
LARGE ENOUGH FOR. 1 BUFFER AS SPECIFIED IN
CONTROL PACKET
REQUESTED NRT$ FROM AN ACTIVITY WHICH IS NON
REAL TIME
INTTERRUPT ACTIVITY LEVEL REQUESTED WHICH IS
NOT PERMITTED.
NO NAME COULD BE FOUND OR HAS "BEEN DEFINED.
ALL ACTIVITIES OF THE PROGRAM HAVE REQUESTED
DEACTIVATION.
REQUESTED QUARTER-WORD MODE. HOWEVER, NO
QUARTER WORD HARDWARE AVAILABLE.
REQUESTED PROC. STATE REG. BE CHANGED. HOWEVER,
1/0 WAS OUTSTANDING FOR THE ACTIVITY.
ILLEGAL STORAGE LIMITS REQUESTED. (PSRSI$,
PSRSD$).
ALL REMAINING ACTIVITIES W/IDENTITIES WENT TO
AWAIT$.
SYNTAX ERROR DISCOVERED IN CONTROL
STATEMENT IMAGE
IMAGE LENGTH OVER 40 WORDS LONG
CONTROL STATEMENT IMAGE CONTAINS A COMMAND
WHICH CANNOT BE SERVICED BY -CSFBUFFER ADDRESS OF CONTROL STATEMENT IMAGE
LIES OUTSIDE OF USERS CORE LIMITS
ATTEMPT MADE TO LOAD OUTSIDE PROGRAM AREA.
ATTEMPT MADE TO LOAD AN UNDEFINED SEGMENT.
PROGRAMS
SEGMENT LOAD TABLE CONTAINS ILLEGAL
SEGMENT.
ILLEGAL MCORE$ REQUEST.
ILLEGAL LCORE$ REQUEST.
BAD 1/0 STATUS.
UNACCEPTABLE RECOGNITION CODE FOR PRIVILEGED
EXECUTIVE REQUEST (ER DLOC$, DIW$).
ENTRANCE TO -FCUI- WITH AN ILLEGAL ER INDEX
WAS DETECTED. CURRENTLY LEGAL ER INDICES ARE
FACIL$, BPOOL$, AND BJOIN$
A CMO$ REQUEST WITH POOL MODE SPECIFIED AND
LT'S START OF OUTPUT BUFFER LOCATION IS ZERO.
A CMO$ REQUEST WITH POOL MODE SPECIFIED AND
LT,S·BUFFER POOL CONTROL WORD IS INVALtD.
A CMO$ REQUEST WITH POOL MODE sPECIFIED AND
BUFFER LOCATION SPECIFIED IS INVALID.
A CMO$ REQUEST WITH POOL MODE SPECIFIED AND
THE BUFFER CHARACTER COUNT EXCEEDS THE
SYSTEM'S MAXIMUM CHARACTER COUNT.
A CADD$ REQUEST WITH INVALID BUFFER LOCATIONS.
A CADD$ REQUEST AND FIRST BUFFER LOCATION IS
ZERO.
A ROUTE$ REQUEST WITH NO FACILITIES ASSIGNED
FOR THE SPECIFIED LT.
A ROUTE$ REQUEST WITH INVALID POINTER WHEN
REQUESTING AN ALTERNATE PATH. THE POINTER IS
GREATER HTAN THE NUMBER OF ALTERNATES

.Apre~di;K .B
SECTION; .

2
P·AGE:

UNIVAC 1108 OPERATING

UP-4144

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

3

A,ppendix B
SECTION:

SPECIFIED AT SYSTEMS GENERATION TUME.
A ROUTE$ REQUEST AND USERS SPECIFIED MODE CODE
ALTERNATE IS GREATER THAN 3 INDICATING A
POSSIBLE ERROR.
A ROUTE$ REQUEST WITH INVALID PROGRAM TYPE.
A ROUTE$ REQUEST WITH INVALID LT LOCATION.
A ROUTE$ REQUEST REQUESTING OUTPUT BUT OUTPUT
NOT ALLOWED FOR THE ALTERNATE ROUTE.
A CGET$ OR CADD$ REQUESTING A ZERO BUFFER
COUNT.
A ROUTE$ REQUEST AND ~SERS LT HAS NOT BEEN
INITIALIZED.
A CGET$ OR CADD$ REQUEST WITH INVALID EXECUTIVE
LINK PARAMETER.
A CGET$ OR CADD$ REQUEST WITH INVALID POOL
TYPE. MUST BE OPEN CHAINS TYPE.
A CGET$ REQUEST REQUESTING BUFFERS AND NO
BUFFERS ARE AVAILABLE.
BLE.
A ROUTE$ REQUEST REQUESTING AN ALTERNATE PATH
WHICH HAS ALREADY BEEN ASSIGNED.
AN ER CMS$ REFERENCE HAS BEEN MADE FROM THE WRONG TYPE OF
CODING. USE OF THIS ER IS NOT PERMITTED FOR DEMAND, DEAD_
LINE BATCH, OR BATCH ACTIVITIES.

6

11

6
6
6

12
13
14

6

16

6

20

6

21

6

22

6

23

6

24

7

1

7

2

AN ER CMS$ REFERENCE HAS SPECIFIED AN ADDRESS IN H2 OF AO
WHICH IS ~EYOND THE LIMITS OF THE PROGRAM.

7

03

7

04

7

05

7

06

7

07

7

010

7

011

7

012

7

013

THE INITIALIZATION REQUEST SPECIFIES
A LT TABLE WHICH IS CURRENTLY IN USE
OR HAS BEEN INITIALIZED BUT HAS
NEVER BEEN TERMINATED.
THE INITIALIZATION REQUEST SPECIFIED
AN INVALID FILE NAME, AN INCORRECT
FILE NAME OR THE FILE NAME CONTAINED
AN ERROR.
AN INVALID VALUE WAS SPECIFIED FOR
THE INPUT COMPLETION ACTIVITY USAGE
CODE WITHIN THE REQUESTING PACKET
FOR AN ER CMS$.
THE FILE NAME FOR AN INITIALIZATION
REQUEST DOES NOT APPEAR IN THE
FACILITY ASSIGNMENT SECTION OF THE
USER,S PROGRAM CONTROL TAdLE (PCT).
THE END OF INPUT ACTIVITY CODE IN
THE PACKET FOR AN INITIALIZATION
REQUEST IS NOT VALID.
THE SINGLE BUFFER MODE INPUT CHARACTER COUNT WITHIN THE PACKET FOR AN
INITIALIZATION REQUEST EXCEEDS THE
MAXIMUM PERMISSABLE VALUE ESTABLISHED
AT SYSTEMS GENERATION TIME.
THE CONTROL GROUP ADDRESS SPECIFIED
IN A PACKET TO BE USED FOR POOL MODE
OF OPERATION IS INVALID.
POOL MODE OF OPERATION HAS BEEN
SPECIFIED, BUT NO BUFFERS- PRESENTLY
EXIST IN THE POOL SPECIFIED AS THE
ONE TO BE USED,
THE ADDRESS WITHIN THE PACKET sPECIFIED AS THE INPUT COMPLETION ACTIVITY WAS NOT VALID.

PAGE:

I

I

OP-4144
Rev. 1

UNIVAC 1108

OPERATING

EXEC

PROGRAMMERS . REFERENCE

a

SYSTEM

4

Appendix B
SECTION:

PAGE:

((""

,="

7

014

7

015

7

016

7

017

7

020

7

021

7

022

7

023

7

024

7

025

7

026

7

027

7

030

7

031

7

032

THE OUTPUT USAGE CODE SPECIFIED
WITliIN THE PACKET FOR AN INITIALIZATION REQUEST IS NOT VALID.
THE SINGLE BUFFER MODE OUTPUT CHARACTER COUNT WITHIN THE PACKET FOR AN
INITIALIZATION REQUEST EXCEEDS THE
MAXIMUM PERMISSABLE VALUE ESTABLISHED
AT SYSTEMS GENERATION TIME.
AN ER CMTS REFERENCE HAS SPECIFIED A LT
GROUP WHICH HAS BEEN TERMINATED PREVIOUSLY OR HAS NEVER BEEN INITIALIZED.
AN ER CMTS REFERENCE HAS BEEN MADE FROM
THE WRONG TYPE OF CODING. USE OF THIS
ER IS NOT PERMITTED FOR DEMAND, DEADLINE BATCH, OR BATCH ACTIVITIES.
AN ER CMTS REFERENCE HAS SPECIFIED AN
ADDRESS IN H2 OF AO BEYOND THE BOUNDS
OF THE PROGRAM.
A REQUEST FOR AN INPUT OPERATION HAS
SPECIFIED A FILE NAME FOR WHICH INPUT IS NOT PERMISSABLE (NO INPUT
FACILITY FOR THE LT GROUP WAS DEFINED AT SYSTEMS GENERATION TIME).
AN INVALID VALUE WAS SPECIFIED FOR
THE INPUT COMPLETION USAGE CODE
WITHIN THE REQUESTING PACKET FOR
AN ER CMU.
THE NUMBER OF CHARACTERS SPECIFIED
FOR A SINGLE BUFFER MODE INPUT OPERATION EXCEEDS THE MAXIMU1-l PERMISSABLE VALUE ESTABLISHED AT SYSTEMS
GENERATION TIME.
AN ADDRESS BEYOND THE BOUNDS OF THE
PROGRAM WAS SPECIFIED IN H2 OF AO
FOR AN ER DIRECTED TO THE COMMUNICATIONS HANDLER,
A NON-MULTIPLE OF 6 WAS SPECIFIED
AS THE CHARACTER COUNT FOR AN INPUT
OPERATION ON THE WTS SUBSYSTEM.
AN INPUT OPERATION HAS SPECIFIED A
CHARACTER COUNT AND BUFFER STARTING
ADDHESS SUCH THAT A PORTION OF THE
INPUT BUFFER EXISTS BEYOND THE
LIMITS OF THE PROGRAM.
AN INPUT OPERATION HAS SPECIFIED
POOL MODE OF OPERATION FOR A FILE
NAME ASSOCIATED WITH EQUIPMENT WHlCH
USES THE lSI METHOD OF BUFFERING.
BUFFER SWAPPING FOR lSI DEVICES IS
NOT PERMITTED DUE TO THE OESIGN OF
THE HARDWARE WHICH OPERATES ON DATA
BY BLOCKS RATHER THAN AS A CONTINUOUS INPUT STREAM.
A REQUEST TO THE COMMUNICATIONS HANDLER HAS SPECIFIED AN INVALID FILE
NAME.
A REQUEST FOR AN OUTPUT OPERATION
HAS SPECIFIED A FILE NAME FOR WHICH
OUTPUT IS NOT PERMISSABLE (NO OUTPUT
FACILITY FOR THE LT GROUP WAS DEFINED AT SYSTEMS GENERATION TIME).
AN INVALID VALUE WAS SPECIFIED FOR
THE OUTPUT COMPLETION USAGE CODE
WITHIN THE REQUESTING PACKET FOR

r

\

\'J

C

UNIVAC 1108 OPERATING

UP-4144
Rev. 1

EXEC B

7

033

7

034

7

036

7

037

7

01+0

7

041

7

042

7

0'+3

7

044

SYSTEM

PROGRAMMERS REFERENCE

Appendix B
SECTION:

AN ER CMOS.
THE NUMBER OF CHARACTERS SPECIFIED
FOR A SINGLE BUFFER MODE OUTPUT
OPERATION EXCEEDS THE MAXIMUM PER~
MISSABLE VALUE ESTABLISHED AT
SYSTEMS GENERATION TIME.
AN OUTPUT OPERATION HAS SPEC IF lEO
A CHARACTER COUNT AND A BUFFER
STARTING ADDRESS SUCH THAT A PORTION OF THE OUTPUT BUFFER EXISTS
BEYOND THE LIMITS OF 1HE PROGRAM.
A CORE AREA SPECIFIED BY AN ER CPOOL$
IS NOT VALID AS IT IS EITHER BEYOND
THE BOUNDS OF THE PROGRAM OR SPLIT
BETWEEN THE I-BANK AND D-8ANK.
THE CORE AREA SPECIFIED By AN
ER CPOOL$ IS LOCATED IN THE I-BANK.
POOL BUFFERING USING THE I-BANK IS
NOT PERMITTED SINCE A PROGRAM IS
SUPPOSED TO BE SO POSITIONED IN CORE
SUCH THAT THE HARDWARE MEMORY OVERLAP FEATURE FOR ESI DATA TRANSFERS
WILL BE UTILIZED IN ORDER TO REDUCE
THE NUMBER OF CORE MEMORY ACCESSES
FROM 3 TO 2 FOR EACH DATA TRANSFER.
A CHARACTER COUNT EXCEEDING THE
MAXIMUM PERMISSABLE VALUE HAS BEEN
SPECIFIED BY AN ER CPOOL$.
AN INSUFFICIENT CORE AREA HAS BEEN
SPECIFIED BY AN ER CPOOL$ SUCH THAT
IT IS NOT POSSIBLE TO FORM A CLOSED
CHAIN WITH THE NUMBER OF SEGMENTS
SPECIFIED TO BE USED.
AN ER TO THE COMMUNICATIONS HANDLER
HAS BEEN EXECUTED FROM THE WRONG
TYPE OF CODING. USE OF THE COMMUNICATIONS HANDLER IS NOT PERMITTED
FOR DEMAND, DEADLINE bATCH, OR BATCH
ACTIVITIES.
THE SINGLE MODE OF BUFFERING HAS
SPECIFIED A COMMUNICATIONS BUFFER
WHICH IS IN THE I-BANK. COMMUNICATIONS BUFFERS ARE NOT PERMITTED IN
THE I-BANK BECAUSE REAL-TIME PROGRAMS ARE PROPERLy POSITIONED IN
CORE SO THAT THE D-BANK CAN UTILIZE
THE MEMORY OVERLAP FEATURE FOR EACH
CHARACTER TRANSFER.
AN ER HAS BEEN MADE TO THE cOMMUNICATIONS HANDLER PRIOR 10 THE ESTABLISHMENT OF AN 'ERR MODE' ROUTINE.
THE ADDRESS WITHIN THE PACKET SPECIFIED AS THE OUTPUT
PLETION ACTIVITY WAS NOT VALID FOR AN ER CMS$.

7

COM.

7

46

AN ER HAS BEEN MADE REQUESTING USE OF A LT GROUP BY THE COMMUNICATIONS HANDLER bEFORE THAT LT GROUP HAS BEEN INITIALIZEU. A LT GROUP MUST BE INITIALIZED VIA AN ER CMS$ BEFORE
ANY INPUT OR OUTPUT CAN BE PERFORMED.

7

47

AN ER CMO$ HAS DESIGNATED THAT POOL MODE SHOULD BE USED FOR
OUTPUT, BUT THE BUFFER POOL CONTROL WORD SPECIFIED IN THE
LT TA~LE IS INVALID.

5
PAGE:

---~

.-._--- - - - - - - - - - - - - - - -

UP-4144

UNIVAC 1108 OPERATING

Rev. 1

EXEC B

SYSTEM

PROGRAMMERS REFERENCE

Appendix B
SECTION:

7

50

AN ER CMI$ FOR SINGLE BUFFER MODE HAS SPECIFIED AN INPUT
BUFFER AREA WHICH CONFLICTS WITH THE MAIN STORAGE MODULE
LOCATIONS OF THE E5I ACCESS CONTROL .ORDS. COMMUNICATIONS
BUFFERS ARE NOT PERMITrED IN THE SAME MAIN STORAGE MODULE
AS THe: ESl ACW'S BECAUSE OF THE EXTENDED TIME REQUIRED FOR
EACH CHARACTER TRANSFER WHEN THE MEMORY OVERLAP CAPABILITY
IS NOT UTILIZEO~ THE REAL-TIME PROGRAM MUST BE PROPERLY
POSITIONED IN MAIN STORAGE SO AS TO TAKE ADVANTAGE OF THE
MEMORY OVERLAP FEATURE FOR E5I DATA TRANSFERS~

7

51

AN ER CMO$ FOR SINGLE BUFFER MODE HAS SPECIFIED AN OUTPUT
BUFFER AREA WHICH CONFLICTS WITH THE MAIN STORAGE MODULE
LOCATIONS OF THE ESI ACCESS CONTROL WORDS. COMMUNICATIONS
BUFFERS ARE NOT PERMITTED IN THE SAME MAIN STORAGE MODULE
AS THE ESI ACW'S BECAUSE OF THE EXTENDED TIME REQUIRED FOR
EACH CHARACTER TRANSFER WHEN THE MEMORY OVERLAP CAPABILITY
IS NOT UTILIZED. THE REAL~TIME PROGRAM MUST BE PROPERLY
POSITIONED IN MAIN STORAGE SO AS TO TAKE ADVANTAGE OF THE
MEMORY OVERLAP FEATURE FOR ESI DATA TRANSFERS.

7

52

THE CORE AREA SPECIFIED By AN"ER cPOOL$ IS LOCATED IN THE
SAME MAIN STORAGE MODULE AS THE ESI ACCESS CONTROL WORDS.
COMMUNICATIONS BUFFERS ARE NOT PERMITTED IK THE SAME MAIN
STORAGE MODULE AS THE ESI ACW'SBECAUSE OF THE EXTENDED
TIME REQUIRED FOR EACH CHARACTER TRANSFER WHEK THE MEMORY
OVERLAP CAPABILITY IS NOT UTILIZED. THE ~EFERENCE TO CPOO_
L$ MUST BE MADE BY A PROPERLY POSITIONED IN MAIN STORAGE SO
AS TO TAKE ADVANTAGE OF THE MEMORY OVERLAP FEATURE FOR ESI
DATA TRANSFERS.

7

53

AN ER CMS$ HAS SPECIFIED A LT TABLE WHICH EXISTS IN THE
EO TO BE SOHPISTICATEO ENOUGH TO UTILIZE THE HARDWARE FEAT_
URE OF MAIN STORAGE OVERLAP BY BEING DIVIDED INTO APPROPRI_
ATE I-SANK AND D-BANK PORTIONS. THE LT TABLE MUST BE PLACED
BY THE REAL-TIME PROGRAM IN ITS D-BANK.

7

54

AN ER CMD$ REFERENCE HAS BEEN MADE FROM THE WRONG TYPE OF
CODING. USE OF THIS ER IS NOTPERMITTEO FOR DEMAND, DEADLINE BATCH, OR BATCH ACTIVITIES.

7

55

AN ER CMD$ REFERENCE HAS sptCIFIED AN ADDRESS IN H2 OF AO
WHICrl IS BEYOND THE LIMITS OF THE PROGRAM~

7

56

AN ER CMD$ REFERENCE HAS SPECIFIED A LT GROUP WHICH HAS
BEEN TERMINATED PREVIOUSLY OR HAS NEVER BEEN INITIALIZED.

7

57

THE ADDRESS WITHIN THE PACKET SPECIFIED AS THE DIAL COMPLE_
TION ACTIVITY ADDRESS WAS NOT VALID FOR AN ER CMD$.

7

64

AN ER CMD$ REFERENCE HAS SPECIFIED A DIAL ACCESS CONTROL
WORD WHOSE CHARACTER COUNT AND BUFFER STARTING ADDRESS ARE
SUCH THAT A PORTION OF THE BUFFER AREA EXISTS BEYOND THE
LIMITS OF THE PROGRAM.

7

65

AN ER CMT$ REFERENCE HAS SPECIFIED A FILE NAME WHICH DOES
NOT APPEAR IN THE FACILITY ASSIGNMENT SECTION OF THE USER'S
PROGRAM CONTROL TABLE. THIS IND1CATES THAT THE ER WAS NOT
EXECUTED IN A PROPER SE~UENCE OF THE FILE HAS ALREADY BEEN
RELEASED.

7

66

AN ER CMD$ REFERENCE HAS SPECIFIED A FILE NAME WHICH DOES
NOT APPEAR IN THE FACILITy ASSIGNMENT SECTION OF THE USER'S
PROGRAM CONTROL TABLE. THIS lNDtCATES THAT THE ER WAS NOT
EXECUTED iN A PROPER SEQUENCE OR THE FILE HAS ALREADY BEEN

6
PAGE:

c

UP-4144

Rev. 1

UNIVAC 1108

OPERATING

EXEC B

PROGRAMMERS REFERENCE

SYSTEM
Appendix B
SECTION:

RELEASED.
7

(

(

".
I

67

AN ER CMH$ REFERENCE hAS SPECIFIED A FILE NAME WHICH DOES
NOT APPEAR IN THE FACILITy ASSIGN~ENT SECTION OF THE USER'S
PROGRAM CONTROL TABLE. THIS INDICATES THAT THE ER WAS NOT
EXECUTED IN A PROPER SE~UENCE OR THE FILE HAS ALREADY BEEN
RELEASED.

7
PAGE:

UP.4144 Rev. 1

A



---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19
Create Date                     : 2018:04:20 07:41:59-08:00
Modify Date                     : 2018:04:20 08:08:35-07:00
Metadata Date                   : 2018:04:20 08:08:35-07:00
Producer                        : Adobe Acrobat 9.0 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:17cc3ade-0a8c-1140-98bd-120fdfc3b8db
Instance ID                     : uuid:74c7e05e-7126-9e47-a130-0bc73455e78a
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 464

EXIF Metadata provided by EXIF.tools