SYSTEM OPERATING

(1)

, .

PROGRAMMER REFERENCE

n n

11

U

SERIES

OPERATING SYSTEM

UP-4144 Rev. 2

(2)

This document contains the latest information available at the time of publication. However, the Univac Division reserves the right to modify or revise its contents. To ensure that you have the most recent information, contact your local Univac Representative.

UNIVAC is a registered trademark of the Sperry Rand Corporation.

Other trademarks of the Sperry Rand Corporation in this publication are:

FASTRAND UNISCOPE UNISERVO

(3)

I

'---

4144 Rev. 2

UP.NUMBER

UNIVAC 1100 SERIES SYSTEMS

CONTENTS

1.

INTRODUCTION 1.1. SCOPE OF MANUAL 1.2. THE OPERATING SYSTEM 1.3. THE EXECUTIVE SYSTEM

1.3.1. MULTIPLE MODES OF OPERATION 1.3.1.1. BATCH PROCESSING

1.3.1.2. DEMAND PROCESSING (TIME-SHAR ING) 1.3.1.3. REAL TIME PROCESSING

1.3.1.4. MUL TIPROGRAMM ING AND MULTIPROCESSING 1.3.2. UTILIZATION OF MASS STORAGE

1.3.3. FUNCTIONAL AREAS OF THE EXECUTIVE SYSTEM 1.3.3.1. EXECUTIVE CONTROL LANGUAGE

1.3.3.2. THE SUPERVISOR

1.3.3.3. FACI LlTI ES ASSIGNMENT 1.3.3.4. FILE CONTROL

1.3.3.5. OPERATOR COMMUNICATIONS

1.3.3.6. INPUT/OUTPUT DEVICE HANDLERS AND SYMBIONTS 1.4. SYSTEM PROCESSORS

1.4.1. COLLECTOR

1.4.2. FILE UTILITY PROCESSOR (FURPUR) 1.4.3. POSTMORTEM DUMP PROCESSOR (PMD) 1.4.4. DATA AND ELT PROCESSORS

1.4.5. FILE ADMINISTRATION PROCESSOR (SECURE) 1.4.6. TEXT EDITOR (ED)

1.4.7. PROCEDURE DEFINITION PROCESSOR (PDP) 1.5. SYSTEM UTILITY PROCESSORS

1.5.1. CUR-TO-FUR CONVERSION (CON78) 1.5.2. FLUSH

1.5.3. SSG PROCESSOR 1.5.4. CULL PROCESSOR

1.5.5. DOCUMENT PROCESSOR (DOC) 1.5.6. LIST PROCESSOR

1.6. LANGUAGE PROCESSORS

1.7. RELOCATABLE SUBROUTINE LIBRARY 1.8_ APPLICATIONS PROGRAMS

PAG ERE VISION

Contents 1

PAGE

2.

GENERAL CONCEPTS AND DEFINITIONS 2.1. INTRODUCTION

2.2. DEFINITIONS AND ABBREVIATIONS 2.2.1. INTRODUCTORY DEFINITIONS 2.2.2. HARDWARE DEFINITIONS

2.2.3. PROGRAM ORGANIZATION DEFINITIONS 2.2.4. DEFINITIONS CONCERNING FILES 2.2.5. RUN PROCESSING DEFINITIONS 2.2.6. MULTIPROGRAMMING DEFINITIONS 2.2.7. MISCELLANEOUS DEFINITIONS

2.2.8. ABBREVIATIONS USED IN THIS MANUAL 2.3. CONVENTIONS

2.3.1. NOTATIONAL CONVENTIONS 2.3.2. CONTROL STATEMENT NOTATION 2.4. BASIC CONCEPTS OF RUN CONTROL 2.4.1. RUN INITIATION

2.4.2. R UN EXECUTION 2.4.3. SYMBIONT OUTPUT

2.4.3.1. SYMBIONT FILE CONCEPTS 2.4.4. RUN TERMINATION

2.5. BASIC CONCEPTS OF TASK CONTROL 2.5.1. REAL TIME

2.5.2. TASK INITIATION

2.5.3. TASK EXECUTION AND SWITCHING 2.5.4. EXECUTIVE REQUESTS

2.5.5. MULTIPROGRAMMING CONSIDERATIONS 2.5.6. TASK TERMINATION

2.5.7. PROGRAM PROTECTION

2.6. FILE NAMES AND ELEMENT NAMES 2.6.1. FILE NAMES

2.6.2. EXTERNAL AND INTERNAL FILE NAMES 2.6.3. FILE CYCLES (F-CYCLES)

2.6.4. ELEMENT NAMES

2.6.5. SYMBOLIC ELEMENT CYCLE

2.6.6. REFERENCING FILES AND ELEMENTS

2.6.7. EXAMPLES OF FILE AND ELEMENT REFERENCE

3.

EXECUTIVE CONTROL STATEMENTS 3.1. INTRODUCTION

3.2. CONTROL STATEMENT FORMAT 3.2.1. LABEL FI ELD

3.2.2. OPERATION FIELDS 3.2.3. OPERAND FIELDS

3.2.4. CONTROL STATEMENT ANNOTATION 3.2.5. CONTROL STATEMENT CONTINUATION 3.2.6. LEADING BLANKS IN FIELDS

3.2.7. GENERAL DROPOUT RULES

PAGE REVISION

2-1 2-1 2-1 2-1 2-1 2-3 2-4 2-4 2-5 2-6 2-8 2-12 2-12 2-13 2-13 2-13 2-13 2-14 2-14 2-15 2-15 2-15 2-15 2-15 2-16 2-16 2-17 2-17 2-18 2-18 2-18 2-19 2-20 2-21 2-21 2-22

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

Contents 2

PAGE

to 2-22

to 3-50

(5)

', ... "

'''--..../

4144 Rev. 2

UP-NUMBER

UNIVAC 1100 SERIES SYSTEMS Contents 3

PAGE REVISION PAGE

3.3. SUMMARY OF CONTROL STATEMENTS 3-3

3.4. SCHEDULING CONTROL STATEMENTS 3-5

3.4.1. RUN INITIATION (@RUN) 3-5

3.4.2. RUN TERMINATION (@FIN CONTROL STATEMENT) 3-9

3.4.3. DYNAMIC INITIATION OF AN INDEPENDENT RUN (@START) 3-9

3.5. MESSAGE CONTROL STATEMENTS 3-11

3.5.1. DISPLAYING A MESSAGE (@MSG) 3-11

3.5.2. INSERTING INFORMATION IN THE MASTER LOG (@LOG) 3-12

3.6. SYMBIONT DIRECTIVE STATEMENT 3-13

3.6.1. PRINT OUTPUT HEADING CONTROL (@HDG) 3-13

3.6.2. SYMBIONT FILE BREAKPOINTING (@BRKPT) 3-14

3.6.2.1. PRIMARY OUTPUT FILE BREAKPOINT 3-14

3.6.2.2. ALTERNATE SYMBIONT FILE BREAKPOINT 3-15

3.6.3. SYMBIONT OUTPUT FILE QUEUING (@SYM) 3-16

3.6.4. @BRKPT/@SYM CONTROL STATEMENT USAGE 3-17

3.6.5. CARD READER MODE CONTROL (@COL) 3-18

3.7. FACILITY CONTROL STATEMENTS 3-19

3.7.1. ASSIGNING FILES AND PERIPHERAL DEVICES (@ASG) 3-19

3.7.1.1. FASTRAND-FORMATTED FI LE ASSIGNMENT 3-21

3.7.1.2. MAGNETIC TAPE ASSIGNMENT 3-26

3.7.1.3. WORD ADDRESSABLE DRUM ASSIGNMENT 3-31

3.7.1.3.1. NORMAL ASSIGNMENT 3-31

3.7.1.3.2. WHOLE UNIT ASSIGNMENT 3-32

3.7.1.4. ARBITRARY DEVICE ASSIGNMENT 3-33

3.7.2. TAPE UNIT MODE CONTROL (@MODE) 3-34

3.7.3. INDEPENDENT CATALOGUING OF FILES (@CAT) 3-35

3.7.4. RELEASING FILES AND PERIPHERAL DEVICES (@FREE) 3-37

3.7.5. ATTACHING INTERNAL FILENAMES (@USE) 3-40

3.7.6. SPECIFYING FILENAME QUALIFIER (@QUAL) 3-41

3.8. DATA PREPARATION CONTROL STATEMENTS 3-42

3.8.1. DIRECT CREATION OF CARD IMAGE FILES (@FILE) 3-42

3.8.2. TERMINATING THE FILE MODE (@ENDF) 3-43

3.9. DYNAMIC RUN STREAM MODIFICATION 3-44

3.9.1. DYNAMIC RUN STREAM EXPANSION (@ADD) 3-44

3.9.2. CONDITIONAL STATEMENTS 3-45

3.9.3. STATEMENT LABELING 3-45

3.9.4. CONDITION WORD 3-46

3.9.4.1. CONDITION WORD CONTROL (@SETC CONTROL STATEMENT) 3-47

3.9.4.2. CONDITION WORD TESTING (@TEST) 3-48

3.9.4.3. BRANCHING FROM WITHIN RUN STREAM (@JUMP) 3-49

3.9.4.4. CONDITIONAL RUN STREAM EXAMPLE 3-50

4.

EXECUTIVE SERVICE REQUESTS 4-1 to 4-30

4.1. INTRODUCTION 4-1

4.1.1. CODING RESTRICTIONS 4-1

4.1.2. CALLING SEQUENCE CONVENTIONS 4-1

4.1.3. E R SYNCH RONY 4-2

4.1.4. ERROR HANDLING 4-2

4.2. SUMMARY OF EXECUTIVE REQUESTS 4-2

(6)

4144 Rev. 2

UP-NUMBER

4.3. ACTIVITY AND PROGRAM CONTROL 4.3.1. ACTIVITY REGISTRATION

4.3.1.1. CREATE A NEW ACTIVITY (FORK$)

4.3.1.2. CREATE A NEW ACTIVITY WITH TIMED WAIT (TFORK$) 4.3.2. ACTIVITY TERMINATION

4.3.2.1. ACTIVITY NORMAL TERMINATION (EXIT$) 4.3.2.2. ACTIVITY ERROR TERMINATION (ERR$) 4.3.2.3. ABORT RUN (ABORT$)

4.3.2.4. PROGRAM ERROR TERMINATION (EABT$) 4.3.3. ACTIVITY SYNCHRONIZATION

4.3.3.1. JOINING OF ACTIVITIES (AWAIT$) 4.3.3.2. ACTIVITY NAMING (NAME$) 4.3.3.3. ACTIVITY DEACTIVATION (DACT$) 4.3.3.4. ACTIVITY ACTIVATION (ER ACT$)

4.3.4. REAL TIME PROGRAM/ACTIVITY CONTROL

4.3.4.1. CHANGING PROGRAM/ACTIVITY TO REAL TIME STATUS (RT$) 4.3.4.2. REMOVAL OF PROGRAM/ACTIVITY REAL TIME STATUS (NRT$) 4.3.5. TIMED ACTIVITY WAIT (TWAIT$)

4.4. CONDITION WORD CONTROL

4.4.1. SETTING THE CONDITION WORD (SETC$) 4.4.2. CONDITION WORD RETRIEVAL (COND$) 4.5. RETRIEVAL OF THE TIME AND DATE 4.5.1. TIME AND DATE IN FIELDATA (DATE$) 4.5.2. TIME AND DATE IN BINARY (TDATE$) 4.5.3. TIME IN MILLISECONDS (TIME$) 4.6. CONSOLE COMMUNICATIONS

4.6.1. CONSOLE OUTPUT AND SOLICITED INPUT (COM$) 4.6.2. UNSOLICITED CONSOLE INPUT (11$)

4.7. PROGRAM STORAGE EXPANSION AND CONTRACTION 4.7.1. MAIN STORAGE EXPANSION (MCORE$)

4.7.2. MAIN STORAGE CONTRACTION (LCORE$) 4.8. MISCELLANEOUS EXECUTIVE REQUESTS

4.8.1. DYNAMIC REOUEST OF CONTROL STATEMENTS (CSF$) 4.8.2. RETRIEVING @XOT CONTROL STATEMENT OPTIONS (OPT$) 4.8.3. PROGRAM CONTROL TABLE RETRIEVAL (PCT$)

4.8.4. ALTERING PROCESSOR STATE REGISTER (PSR$) 4.8.5. SNAPSHOT DUMP (SNAP$)

4.8.6. MASTER CONFIGURATION TABLE RETRIEVAL (MCT$) 4.9. CONTINGENCI ES

4.9.1. INTRODUCTION

4.9.2. CONTINGENCY TYPES AND STANDARD ACTION 4.9.2.1. ERROR TERMINATION CONSIDERATIONS 4.9.3. CONTI NG ENCY REG ISTRATION (lALL$) 4.9.4. CONTINGENCY PROCESSING (NON-ESI) 4.9.4.1. THE CONTINGENCY ROUTINE

4.9.4.2. CONTINGENCY MODE TERMINATION (CEND$) 4.9.4.3. ADDITIONAL CONTINGENCY CONSIDERATIONS 4.9.5. ESI CONTINGENCIES

PAGE REVISION

Contents 4

PAGE

4-6 4-6 4-6 4-6 4-7 4-7 4-7 4-7 4-8 4-8 4-8 4-9 4-9 4-10 4-10 4-10 4-11 4-11 4-11 4-11 4-12 4-12 4-12 4-13 4-13 4-13 4-13 4-15 4-15 4-15 4-16 4-17 4-17 4-18 4-19 4-20 4-21 4-22 4-23 4-23 4-23 4-25 4-25 4-27 4-27 4-28 4-28 4-29

(7)

"-_{'--_.-.'}

,.~"'"

(

~-.

4144 Rev. 2

UP.NUMBER

PAGE REVISION PAGE

5.

SYMBIONT INTERFACE REQUESTS 5·1 to 5·17

5.1.1. SYMBIONTS 5-1

5.1.2. SYMBIONT/USER INTERFACE ROUTINES 5-2

5.2. OBTAINING INPUT IMAGES 5-3

~.2.1. READING FIELDATA IMAGES (READ$) 5-3

5.2.2. READING ASCII IMAGES (AREAD$) 5-4

5.2.3. FIELDATA IMAGES - ALTERNATE FILE (READA$) 5-4

5.2.4. ASCII IMAGE - FROM AN ALTERNATE FILE (AREADA$) 5-5

5.2.5. FIELDATA IMAGES - CONVERSATIONAL MODE (TREAD$) 5-6

5.3. TRANSFERRING OUTPUT IMAGES 5-7

5.3.1. PRINTING FIELDATA IMAGES (PRINT$) 5-7

5.3.2. PRINTING ASCII IMAGES (APRINT$) 5-7

5.3.3. FIELDATA IMAGES - ALTERNATE PRINT FILE (PRNTA$) 5-8

5.3.4. ASCII IMAGES - ALTERNATE PRINT FILE (APRNTA$) 5-9

5.3.5. PUNCHING FIELDATA IMAGES (PUNCH$) 5-9

5.3.6. PUNCHING ASCII IMAGES (APUNCH$) 5-10

5.3.7. FIELDATA IMAGES - ALTERNATE PUNCH FILE (PNCHA$) 5-10

5.3.8. ASCII IMAGES - ALTERNATE PUNCH FILE (APNCHA$) 5-11

5.4. OUTPUT CONTROL FUNCTIONS 5-11

5.4.1. FIELDATA CONTROL FUNCTIONS - PRINT FILE (PRTCN$) 5-11

5.4.2. ASCII CONTROL FUNCTIONS - PRINT FILE (APRTCN$) 5-12

5.4.3. FIELDATA CONTROL FUNCTION - ALTERNATE PRINT FILE (PRTCA$) 5-13

5.4.4. ASCII CONTROL FUNCTIONS - ALTERNATE PRINT FILE (APRTCA$) 5-13

5.4.5. FIELDATA CONTROL FUNCTIONS - PUNCH FILE (PCHCN$) 5-14

5.4.6. ASCII CONTROL FUNCTION - PUNCH FILE (APCHCN$) 5-14

5.4.7. FIELDATA CONTROL FUNCTIONS - ALTERNATE PUNCH FILE (PCHCA$) 5-15

5.4.8. ASCII CONTROL FUNCTION - ALTERNATE PUNCH FILE (APCHCA$) 5-15

5.5. LISTING USER·DEFINED CONTROL STATEMENTS (CLlST$) 5-16

5.6. FIELDATA AND ASCII TRANSLATION 5-17

6.

INPUT/OUTPUT DEVICE HANDLERS 6-1 to 6-34

6.1.1. BASIC I/O EXECUTIVE REQUEST 6-1

6.1.2. INTERRUPT ACTIVITY 6-4

6.1.3. QUEUEING AND UNIT CONTROL 6-4

6.2. I/O PACKET GENERATION 6-4

6.2.1. MAGNETIC TAPE I/O PACKET GENERATION (I$OT) 6-4

6.2.2. MASS STORAGE I/O PACKET GENERATION (1$00) 6-6

6.3. PROGRAM - I/O SYNCHRONIZATION 6-7

6.3.1. WAIT FOR COMPLETION OF SPECIFIC I/O (WAIT$) 6-7

6.3.2. WAIT FOB_GOMPLETION OF ANY I/O (WANY$) 6-8

6.3.3. INITIATE I/O AND RETURN CONTROL IMMEDIATELY (10$) 6-8

6.3.4. INITIATE I/O AND RETURN CONTROL IMMEDIATELY, WITH INTERRUPT (101$) 6-8

6.3.5. INITIATE I/O AND WAIT FOR COMPLETION (lOW$) 6-9

6.3.6. INITIATE I/O AND WAIT FOR COMPLETION, WITH INTERRUPT (lOWI$) 6-9

6.3.7. INITIATE I/O AND EXIT, WITH INTERRUPT (lOXI$) 6-9

6.3.8. REDUCING INTERRUPT ACTIVITY PRIORITY (UNLCK$) 6-10

(8)

4144 Rev. 2

UP-NUMBER

6.4. MAGNETIC TAPE HANDLER 6.4.1. TAPE HANDLER FUNCTIONS 6.4.1.1. SET MODE FUNCTION 6.4.2. GENERAL CONSIDERATIONS 6.4.2.1. READ BACKWARD LIMITATIONS 6.4.2.2. WRITE CONSIDERATIONS 6.4.2.3. MOVE CONSIDERATIONS

6.4.2.4. ABNORMAL FRAME COUNT CONSIDERATIONS 6.4.3. MULTIPLE-CHANNEL OPERATION

6.5. MAGNETIC DRUM AND UNITIZED CHANNEL STORAGE HANDLER 6.5.1. HANDLER FUNCTIONS

6.5.2. GENERAL CONSIDERATIONS 6.5.3. MULTIPLE·CHANNEL OPERATION 6.6. FASTRAND MASS STORAGE HANDLER 6.6.1. FASTRAND HANDLER FUNCTIONS 6.7. DISC HANDLER

6.7.1. DISC HANDLER FUNCTIONS 6.7.2. PREPPING THE DISC

6.8. ABSOLUTE READ/WRITE CAPABI LlTY 6.9. ARBITRARY DEVICE HANDLER 6.9.1. ADH I/O PACKET

6.9.2. INITIATE ADH AND RETURN CONTROL IMMEDIATELY (I0ARB$) 6.9.3. INITIATE ADH, EXIT AT INTERRUPT (lOAXI$)

6.9.4. FREE FORMAT DISC HANDLER 6.10. STATUS CODES

7. FILE CONTROL 7.1. INTRODUCTION 7.2. FILE ORGANIZATION 7.2.1. MASTER FILE DIRECTORY 7.2.2. MASS STORAGE ALLOCATION 7.2.3. FILE ADDRESSING

7.2.4. EXCLUSIVE USE OF FI LES

7.2.5. ROLLOUT AND ROLLBACK OF FI LES

7.2.6. RETRIEVING FACILITY ASSIGNMENT (FITEM$) 7.2.6.1. UNIT RECORD AND NONSTANDARD PERIPHERAL 7.2.6.2. FASTRAND MASS STORAGE PERIPHERALS 7.2.6.3. MAGNETIC TAPE PERIPHERALS

7.2.6.4. MAGNETIC DRUM PERIPHERALS 7.2.6.5. COMMUNICATIONS PERIPHERALS 7.2.6.6. DISC PERIPHERALS

7.2.7. ALTERNATE METHODS OF RETRIEVING FACILITY ASSIGNMENT SYNOPSIS (FACIL$ AND FACIT$)

7.2.8. TAPE FILE INITIALIZATION (TINTL$) 7.2.9. TAPE SWAPPING (TSWAP$)

PAGE REVISION

Contents 6

PAGE

6-10 6-10 6-12 6-14 6-14 6-14 6-18 6-18 6-18 6·21 6·21 6·23 6-23 6·23 6-23 6·25 6-25 6-26 6-27 6-27 6-27 6·30 6·31 6·31 6·32

7-1 to 7-19 7·1

7-1 7-1 7-2 7-2 7-3 7·3 7-3 7-5 7·6 7-7 7-10 7-11 7-13 7-14 7·14 7-15

(9)

/

'---..

...

4144 Rev. 2

UP.NUMBER

PA GE REVISION PAGE

7.3. TAPE LABELING 7·15

7.3.1. READING AND WRITING TAPE LABEL BLOCKS (LABEL$) 7-18

7.4. DISC LABELING 7·19

8.

FILE UTILITY ROUTINES (FURPUR) 8·1 to 8-26

8.1. INTRODUCTION 8·1

8.1.1. COMMON INFORMATION 8-2

8.1.2. SIMULTANEOUS USE OF FILES 8-3

8.1.3. MULTI REEL FI LES 8-3

8.1.4. BASIC FILE FORMATS 8-3

8.2. FURPUR CONTROL STATEMENTS 8-5

8.2.1. FILE COPYING (@COPY) 8-5

8.2.2. COPYING FROM TAPE TO PROGRAM FILES (@COPIN) 8-9

8.2.3. COPYING PROGRAM FILES TO TAPE (@COPOUT) 8-11

8.2.4. POSITIONING TAPE FILES (@MOVE) 8-13

8.2.5. LISTING FILES AND MASTER FILE DIRECTORY (@PRT) 8-14

8.2.6. EMPTYING A PROGRAM FILE (@ERS) 8-17

8.2.7. DELETING FILES AND ELEMENTS (@DELETE) 8-17

8.2.8. REWINDING TAPE FILES (@REWIND) 8-18

8.2.9. MARKING AN EOF ON TAPE (@MARK) 8-19

8.2.10. CLOSING TAPE FILES (@CLOSE) 8-19

8.2.11. ENTRY POINT TABLE CREATION (@PREP) 8-19

8.2.12. PUNCHING PROGRAM FILE ELEMENTS (@PCH) 8-20

8.2.13. POSITIONING WITHIN ELEMENT FILES (@FIND) 8-21

8.2.14. REMOVAL OF DELETED ELEMENTS (@PACK) 8-22

8.2.15. CHANGING FILE ELEMENT, AND VERSION NAMES, AND FILE KEYS AND 8-22 MODES (@CHG)

8.2.15.1. CHANGING CATALOGUED FILE NAMES, KEYS, AND MODES 8-22 8.2.15.2. CHANGING PROGRAM FILE ELEMENT AND VERSION NAMES 8-23

8.2.15.3. EXAMPLES 8-24

8.2.16. ALTERING CYCLE RETENTION LIMIT (@CYCLE) 8-24

8.2.17. ENABLING FILES DISABLED DUE TO MALFUNCTIONS (@ENABLE) 8-26

9.

LANGUAGE PROCESSORS AND LIBRARIES 9-1 to 9-13

9.2. OPERATING SYSTEM LIBRARY FILES (LlB$, RLlB$) 9-1

9.3. TEMPORARY PROGRAM FI LE (TPF$) 9-1

9.4. PROCESSOR CONTROL STATEMENTS 9-1

9.4.1. LANGUAGE PROCESSOR CONTROL STATEMENTS 9-2

9.4.2. SOURCE INPUT ROUTINE CONTROL OPTIONS 9-6

9.4.3. COMPRESSED SYMBOLIC ELEMENTS 9-6

9.5. MODIFYING SYMBOLIC ELEMENTS 9-7

9.5.1. LINE CORRECTION STATEMENT 9-7

9.5.1.1. REDEFINITION OF THE CORRECTION INDICATOR 9-8

9.5.2. PARTIAL LINE CORRECTIONS 9·8

9.5.2.1. RANGE CORRECTION STATEMENT 9·8

9.5.2.2. CHANGE CORRECTION STATEMENTS 9-9

9.5.2.3. PARTIAL LINE CORRECTION DIAGNOSTICS 9-10

(10)

4144 Rev. 2

UP-NUMBER

UNIVAC 1100 SE RI ES SYST EMS Contents 8

9.6. PROCESSOR INTERFACE ROUTINES

9.7. PROCEDURE DEFINITION PROCESSOR (PDP)

10. PROGRAM CONSTRUCTION AND EXECUTION 10.1. INTRODUCTION

10.2. THE COLLECTOR

10.2.1. COLLECTOR INITIATION (@MAP) 10.2.2. COLLECTOR DIRECTIVES 10.2.2.1. ELEMENT INCLUSION (IN) 10.2.2.2. ELEMENT EXCLUSION (NOT) 10.2.2.3. FILE SEARCH SEQUENCING (LIB)

10.2.2.4. EXTERNAL DEFINITION RETENTION (DEF) 10.2.2.5. EXTERNAL REFERENCE RETENTION (REF) 10.2.2.6. STARTING ADDRESS REDEFINITION (ENT) 10.2.2.7. EXTERNAL REFERENCE DEFINITION (EQU) 10.2.2.8. ELEMENT SELECTION DETERMINATION (CLASS) 10.2.2.9. CORRECTIONS FOR A RELOCATABLE ELEMENT (COR) 10.2.2.10. ADDING SNAPSHOT DUMPS (SNAP)

10.2.2.11. END OF INPUT (END)

10.2.2.12. ABSOLUTE ELEMENT OPTIMIZATION (MINGAP, MINSIZ) 10.2.2.13. PROGRAM SEGMENTATION (SEG)

10.2.2.14. RELOCATABLE SEGMENTS (RSEG) 10.2.2.15. DYNAMIC SEGMENT DEFINITION (DSEG) 10.2.3. FUNCTIONAL ASPECTS OF THE COLLECTOR

10.2.3.1. COLLECTOR-PRODUCED RELOCATABLE ELEMENTS 10.2.3.2. ELEMENT INCLUSION

10.2.3.3. SEGMENTED VERSUS NONSEGMENTED PROGRAMS 10.2.3.4. COLLECTING REENTRANT PROCESSORS

10.2.3.5. PROCESSING ELEMENT PREAMBLES 10.2.4. PROGRAM SEGMENTATION

10.2.4.1. SEGMENTATION DIRECTIVES 10.2.4.2. INSTRUCTION AND DATA AREAS 10.2.4.3. SEG 01 RECTIVE CONSIDERATIONS 10.2.4.4. RSEG DIRECTIVE CONSIDERATIONS 10.2.4.5. LOADING PROGRAM SEGMENTS

10.2.4.5.1. DIRECT METHOD (L$OAD AND LOAD$) 10.2.4.5.2. INDI RECT METHOD

10.2.4.5.3. RELOADING THE MAIN SEGMENT 10.2.4.6. USE OF COMMON BLOCKS

10.2.4.7. SEGMENTATION EXAMPLE

10.2.4.8. COLLECTOR GENERATED TABLES 10.3. PROGRAM EXECUTION

10.3.1. INITIATING EXECUTION (@XQT) 10.3.1.1. INITIAL EXECUTION STATUS 10.3.2. PROGRAM DATA SEPARATION (@EOF)

PA GE REVISION PA GE

9-10 9-12

10-1 to 10-43 10-1

10-1 10-2 10-4 10-5 10-6 10-7 10-7 10-8 10-9 10-9 10-10 10-12 10-13 10-15 10-16 10-16 10-17 10-17 10-18 10-18 10-18 10-19 10-20 10-20 10-20 10-21 10-21 10-21 10-23 10-24 10-24 10-26 10-26 10-27 10-27 10-30 10-31 10-31 10-32 10-32

(11)

.-"

\

... -..

....

-

^...^~

(

"-/'

4144 Rev. 2

UP.NUMBER

10.4. REENTRANT PROCESSOR EXECUTION 10.4.1. GENERAL

10.4.2. SEARCHING THE REENTRANT PROCESSOR LISTS

10.4.3. ENTERING A LIST OF USER-CREATED REENTRANT PROCESSORS (RLlST$) 10.4.4. REFERENCING A REENTRANT PROCESSOR (LlNK$ AND RLlNK$)

10.4.4.1. LlNK$ EXECUTIVE REQUEST 10.4.4.2. RLlNK$ EXECUTIVE REQUEST

10.4.5. REENTRANT PROCESSOR TERMINATION (EXLNK, UNLNK$, AND EXIT$) 10.4.5.1. EXLNK$ EXECUTIVE REQUEST

10.4.5.2. UNLNK$ EXECUTIVE REQUEST 1004.5.3. EXIT$ EXECUTIVE REQUEST 10.4.6. REENTRANT PROCESSOR FORKING

10.4.7. REENTRANT PROCESSOR CONTROL AND RESTRICTIONS 10.5. REENTRANT PROCESSOR PREPARATION

10.5.1. USAGE OF A REENTRANT PROCESSOR 10.5.1.1. COMMON I BANKS

10.5.1.2. ADDITIONAL INSTRUCTION SPACE

10.5.2. STORAGE ALLOCATION AND REENTRANCY 10.5.3. WRITE PROTECT MODE

10.5.4. D BANK ADDRESSING 10.5.4.1. COLLECTION 10.5.4.2. REGISTER BASING

10.504.3. COLLECTOR PRODUCED TABLES 10.5.5. REP SIZE

10.5.6. EXECUTIVE REQUESTS WITHIN REENTRANT PROCESSORS 10.5.6.1. MCORE$ AND LCORE$ USAGE

10.5.6.2. IALL$ USAGE

10.5.6.3. CMS$ AND CPOOL$ USAGE 10.5.6.4. LOAD$ USAGE

10.5.6.5. RLlNK$ USAGE

10.5.7. DUMPING REENTRANT PROCESSORS

11.

POSTMORTEM AND DYNAMIC DUMPING 11.1. INTRODUCTION

11.2. POSTMORTEM DUMP PROCESSOR (PMD) 11.2.1. @PMD CONTROL STATEMENT

11.3. DYNAMIC DUMPS

11.3.1. CUMP CALLING PROCEDURES 11.3.1.1. MAIN STORAGE DUMP (X$CORE)

11.3.1.2. CONTROL REGISTER AND MAIN STORAGE DUMP (X$DUMP) 11.3.1.3. CHANGED WORD DUMP (X$CW)

11.3.1.4. TAPE BLOCK DUMP (X$TAPE) 11.3.1.5. MASS STORAGE DUMP (X$DRUM) 11.3.1.6. FILE DUMP (X$FILE)

11.3.1.7. CONTROL REGISTER (USER SET) DUMP (X$CREG) 11.3.1.8. EDITING FORMATS FOR DYNAMIC DUMPS

11.3.1.8.1. STANDARD EDITING FORMATS FOR DUMPS 11.3.1.8.2. USER-DEFINED EDITING FORMATS (X$FRMT) 11.3.2. CONDITIONAL CONTROL PROCEDURES

11.3.2.1. INITIATING A STRING OF CALLS (X$IF)

PAGE REVISION

10-33 10·33 10-33 10-34 10·35 10-35 10-35 10-37 10-37 10-37 10-37 10-37 10-38 10-39 10-39 10-39 10-39 10-39 10-40 10-40 10-40 10-41 10-41 10-41 10-41 10-41 10-41 10-41 10-41 10-42 10-42

11-1 11-1 11-1 11-l 11-4 11-5 11-5 11-6 11-8 11-9 11-10 11-11 11-12 11-13 11-13 11-14 11-15 11-16

Contents 9

PAGE

to 11-29

(12)

4144 Rev. 2

UP-NUMBER

11.3.2.2. LOGICAL OR CONTROL OF DUMPS (X$OR) 11.3.2.3. LOGICAL AND CONTROL OF DUMPS (X$AND)

11.3.2.4. CONTROLLING THE CONDITIONAL DUMP SWITCH (X$TAL Y) 11.3.3. SPECI FICATION PROCEDURES

11.3.3.1. INITIALIZING A BUFFER (X$BUFR)

11.3.3.2. ALLOWING AND IGNORING DUMP PROCEDURE CALLS (X$ON and X$OFF) 11.3.3.3. SAVING AND DELETING DYNAMIC DUMPS (X$MARK AND X$BACK) 11.3.3.4. PLACING A MESSAGE IN THE DUMP (X$MESG)

11.3.4. EXAMPLES OF DYNAM IC DUMPI NG 11.4. PROGRAM TRACE ROUTINE (SNOOPY)

12.

DEMAND PROCESSING 12.1. INTRODUCTION

12.1.1. GENERAL DEMAND TERMINAL OPERATIONAL PROCEDURES 12.1.1.1. INITIALIZATION

12.1.1.2. DEMAND RUN STREAM SUBMISSION 12.1.1.3. TERMINATION

12.1.1.4. DEMAND TERMINAL/SYSTEM INTERFACE MESSAGES 12.1.2. DEMAND SYMBIONT/USER INTERFACE

12.1.3. EXECUTIVE LANGUAGE INTERFACE

12.2. GENERAL OPERATION OF THE DEMAND SYMBIONTS 12.2.1. TELETYPEWRITER DEMAND SYMBIONT

12.2.1.1. OPERATIONAL CONSIDERATIONS 12.2.1.2. PAPER TAPE INPUT

12.2.1.2.1. FORM I PAPER TAPE INPUT 12.2.1.2.2. FORM" PAPER TAPE INPUT 12.2.1.3. SPECIAL CONTROL SEQUENCES 12.2.1.4. BREAK KEY

12.2.1.5. TAB CONTROL STATEMENT (@TABSET)

12.2.1.6. CENTRAL SITE TO REMOTE SITE OPERATOR COMMUNICATION 12.2.1.7. FRIDEN 7100

12.2.1.8. OCT 500 IN TELETYPEWRITER MODE

12.2.2. OCT 500 DEMAND SYMBIONT (SEMI-AUTOMATIC) 12.2.2.1. OPERATIONAL CONSIDERATIONS

12.2.2.2. SPECIAL CONTROL SEQUENCES 12.2.2.3. USER/PROGRAM INTERFACE

12.2.3. UNISCOPE 100/DCT 1000 DEMAND SYMBIONT

12.2.3.1. OPERATIONAL CONSIDERATIONS FOR THE UNISCOPE 100 12.2.3.2. OPERATIONAL CONSIDERATIONS FOR THE OCT 1000 12.2.3.3. SPECIAL CONTROL SEQUENCES

12.2.3.4. USER PROGRAM INTERFACE 12.2.4. UNISCOPE 300 DEMAND SYMBIONT 12.2.4.1. OPERATIONAL CONSIDERATIONS 12.2.4.2. SPECIAL CONTROL SEQUENCES 12.2.4.3. USER PROGRAM INTERFACE 12.3. TERMINAL USER TECHNIQUES 12.4. EXAMPLE OF A DEMAND RUN

PAGE REVISION

11-17 11-17 11-18 11-19 11-19 11-20 11-21 11-22 11-22 11-24

12-1 12-1 12-1 12-2 12-2 12-3 12-3 12-4 12-4 12-5 12-5 12-5 12-5 12-6 12-7 12-7 12-8 12-9 12-9 12-10 12-10 12-11 12-11 12-13 12-14 12-14 12-14 12-16 12-16 12-19 12-20 12-20 12-21 12-22 12-22 12-22

Contents 10

PAGE

to 12-24

(13)

4144 Rev. 2

UP.NUMBER

UNIVAC 1100 SERIES SYSTEMS Contents 11

PAGE REVISION PAGE

(14)

4144 Rev. 2

UP.NUMBER

PAGE REVISION PAGE

13.5.3.2. EXAMPLE OF A COMPLETED FORMAT DEFINITION 13-38

13.5.3.3. RULES FOR CODING FORMAT SUBROUTINES 13-38

13.5.3.3.1. LABEL RECORD SUBROUTINES 13-41

13.5.3.3.2. BLOCK RECORD SUBROUTINES 13-41

13.5.3.3.3. ITEM RECORD SUBROUTINES 13-41

13.5.3.3.4. END-OF-REEL SUBROUTINES 13-42

13.5.3.3.5. END-OF-FILE SUBROUTINES 13-42

13.6. HANDLING OF LABELS AND SENTINELS 13·42

13.6.1. LABEL AND SENTINEL HANDLING FOR OUTPUT FILES 13-42

13.6.2. LABEL AND SENTINEL HANDLING FOR INPUT FILES 13-43

13.7. DATA FILE ORGANIZATION 13-43

13.8. ERROR PROCESSING 13-46

13.8.1. DEVICE ERROR HANDLING 13-46

13.8.2. FILE ERROR HANDLING 13-46

13.8.3. ABNORMAL ERROR HANDLING 13-49

14.

OUTPUT EDITING PACKAGES 14-1 to 14-14

14.2. EDIT$ (IMAGE COMPOSITION EDITING PACKAGE) 14-1

14.2.1. GENERATING THE EDIT$ PACKET (E$PKT AND E$PKTF) 14-3

14.2.2. INITIALIZATION AND TERMINATION OF EDITING MODE 14-4

14.2.3. GENERAL PURPOSE EDITING ROUTINES 14-4

14.2.4. FLOATING-POINT EDITING ROUTINES 14-9

14.3. EOUT$ (GENERALIZED OUTPUT EDITING ROUTINES) 14-10

14.3.1. EDITING FUNCTIONS 14-11

14.3.2. OUTPUT FUNCTIONS 14-12

14.3.3. MODAL FUNCTIONS 14-12

14.3.4. CONTROL FUNCTIONS 14-13

14.3.5. EXAMPLES 14-13

15.

COMMUNICATIONS HANDLER ^15-1 to 15-24

15.1.1. EQUIPMENT 15-1

15.1.1.1. THE CTS AND WTS 15-1

15.1.1.2. THE CTMC 15-1

15.1.2. MODES OF OPERATION 15-2

15.2. ASSIGNING LINE TERMINAL (L T) DEVICES 15-2

15.3. THE LINE TERMINAL TABLE 15-2

(15)

4144 Rev. 2 UNIVAC 1100 SERIES SYSTEMS Contents 13

U P.NUMBER PAGE REVISION PAGE

15.4. COMMUNICATIONS HANDLER OPERATIONS 15-8

(

15.4.1. SUPPORT OPERATIONS 15-8

....

15.4.1.1. INITIALIZATION (CMS$) 15-9

15.4.1.2. DIALING (CMD$) 15-9

15.4.1.3. INPUT (CMI$) 15-10

15.4.1.4. OUTPUT (CMO$) 15-10

15.4.1.5. SEND AND ACKNOWLEDGE (CMSA$) 15-11

15.4.1.6. SINGLE BUFFER MODE FOR INPUT/OUTPUT OPERATIONS 15-11

15.4.1.7. POOL MODE FOR I/O OPERATIONS 15-12

15.4.1.8. DUAL POOL MODE FOR INPUT OPERATIONS 15-13

15.4.1.9. HANGUP (CMH$) 15-13

15.4.1.10. TERM INATION (CMT$) 15-13

15.4.2. COMMUNICATION POOLS 15-14

15.4.2.1. ESTABLISHING A COMMUNICATIONS POOL (CPOOL$) 15-15

15.4.2.2. REMOVING BUFFERS FROM A POOL (CGET$) 15-17

15.4.2.3. RETURNING BUFFERS TO A POOL (CADD$) 15-17

15.4.2.4. EXPANDING A POOL (CJOIN$) 15-18

15.4.2.5_ RELEASING COMMUNICATIONS POOL (CREL$) 15-18

15.4.3. ALTERING COMMUNICATIONS PATHS (ROUTE$) 15-19

15.4.3.1. ROUTING PROCEDURES 15-20

15.5. COMPLETION ACTIVITIES 15-20

15.5.1. EXITING FROM AN ESI ACTIVITY (ADACT$) 15-20

15.6. IDLE LINE MONITOR 15-21

15.7. TIMING CONSIDERATIONS 15-21

i ^\ 15.7.1. INTERRUPT RESPONSE 15-22

15.7.2. BUFFER PROCESSING 15-22

15.8. INFORMATION ANALYSIS 15-24

15.9. ERROR CODES FOR L T CONTINGENCIES 15-24

16.

REAL TIME PROCESSING ^16-1 to 16-9

16.2. PROGRAM LOCATION 16-1

16.3. BUFFER OPERATIONS 16-1

16.3.1. TRANSM ISSION TYPES 16-2

16.3.2. MAIN STORAGE AVAILABILITY 16-2

16.3.3. POOL SIZE 16-2

16.3.4. BUFFER SIZE 16-2

16.3.5. DUAL POOL METHOD 16-3

16.4. PROGRAM EXECUTION CONSIDERATIONS 16-3

16.4.1. PRIORITY CATEGORIES 16-3

16.4.1.1. I/O PRIORITY 16-4

16.4.1.2. DISPATCHING PRIORITY 16-4

/ ...

(

'"--,,

(16)

4144 Rev. 2

UP-NUMBER

UN IV AC 1100 SE RI ES SYS T EMS Contents 14

PAGE REVISION PAGE

16.4.2. PRIORITY CONTROL 16-5

16.4.2.1. CHANGING ACTIVITY PRIORITIES (RT$ AND NRT$) 16-5

16.4.2.2. APPLICATION OF MULTIPROGRAMMING TO REAL TIME 16-6 16.4.2.3. INTERRUPT ACTIVITY PRIORITY REDUCTION (UNLCK$) 16-6

16.4.2.4. ACTIVITY TERMINATION (EXIT$) 16-6

16.4.2.5. TIMED WAIT CONSIDERATIONS 16-7

16.4.2.6. CONSOLE INTERRUPT HANDLING 16-7

16.4.3. EXCEEDING MAXIMUM TIME LIMITATION 16-7

16.4.4. TEST AND SET USAGE 16-7

16.5. PROGRAMMER'S GENERAL RESPONSIBILITIES 16-8

16.6. ESI CONSIDERATIONS 16-8

16.6.1. ESI ACTIVITY CONCEPT 16-8

16.6.2. ESI TIMING 16-9

16.6.2.1. ESI INTERRUPTS 16-9

16.6.2.2. REAL TIME ACTIVITIES 16-9

17.

CHECKPOINT/RESTART 17-1 to 17-10

17.2. COMPLETE CHECKPOINT/RESTART 17-1

17.2.1. COMPLETE CHECKPOINT - RUN SAVE 17-1

17.2.1.1. CONTROL STATEMENT (@CKPT) 17-2

17.2.1.2. EXECUTIVE REQUEST 17-2

17.2.1.3. UNSOLICITED CONSOLE REQUEST 17-2

17.2.1.4. EXAMPLES OF CH ECKPOINT 17-3

17.2.2. CHECKPOINT FILE FORMAT 17-3

17.2.3. CHECKPOINT FILE IDENTIFICATION MESSAGE 17-5

17.2.4. COMPLETE RESTART - RUN RESTORE 17-5

17.2.4.1. CONTROL STATEMENT (@RSTRT) 17-6

17.2.4.2. EXECUTIVE REQUEST 17-6

17.2.4.3. UNSOLICITED CONSOLE REQUEST 17-6

17.2.4.4. EXAMPLES OF RESTART 17-7

17.2.5. RESTART CONTINGENCY ROUTINE 17-7

17.3. PARTIAL CHECKPOINT/RESTART 17-8

17.3.1. PARTIAL CHECKPOINT - PROGRAM SAVE (@CKPAR) 17-8

17.3.2. PARTIAL RESTART - PROGRAM RESTORE (@RSPAR) 17-9

17.4. CHECKPOINT/RESTART ERROR CODES 17-10

18.

SYSTEM SYMBOLIC PROCESSORS 18-1 to 18-20

18.2. E L T PROCESSOR 18-1

18.2.1. INPUT TERMINATION SENTINEL (@END) 18-4

18.3. DATA PROCESSOR 18-4

(17)

... -. ~

.. -- I

~~~ .... "

4144 Rev. 2

UP-NUMBER

PAGE REVISION PA GE

18.4. ED PROCESSOR 18-6

18.4.1. EDIT MODE COMMANDS 18-7

18.4.2. USAGE CONSIDERATIONS 18-15

18.5. CULL PROCESSOR 18-15

18.6. LIST PROCESSOR 18-18

18.7. CON78 PROCESSOR 18-19

19.

FILE ADMINISTRATION PROCESSOR (SECURE) 19-1 to 19-13

19.2. MAJOR FUNCTION DEFINITIONS 19-2

19.3. @SECURE CONTROL STATEMENT 19-2

19.4. INPUT AND OUTPUT BACKUP TAPE ASSIGNMENTS 19-3

19.5. CATALOGUED FILE ASSIGNMENTS 19-4

19.6. USE OF SYS$*DLOC$ 19-4

la~ SECURE SOURCE LANGUAGE 19-5

19.7.1. STANDARD COMMANDS 19-5

19.7.2 . NAMELISTS AND LIMITERS 19-6

19.7.3. EXCLUSIONS 19-7

19.7.4. DIRECTION 19-7

19.7.5. EXAMPLES OF SOURCE LANGUAGE 19-7

19.8. SELECTION OF FILES FOR UNLOAD 19-7

19.9. OWN-PROJECT APPLICATIONS 19-8

19.10. CATALOGUED FILE RECOVERY APPLICATIONS 19-8

19.11. SUMMARY OF SECURE PROCESSOR COMMANDS 19-9

19.12. EXAMPLES OF THE USE OF THE SECURE PROCESSOR 19-10

20.

SYMBOLIC STREAM GENERATOR (SSG) 20-1 to 20-28

20.2. INPUT STREAMS 20-1

20.3. OUTPUT STR EAMS 20-2

20.4. @SSG CONTROL STATEMENT 20-3

20.5. FILE IDENTIFICATION STATEMENTS 20-4

(18)

4144 Rev. 2

UP-NUMBER

UN IVAC 11 00 SE RI ES SYST EMS Contents 16

PA GE RE VISION PA GE

20.6. SUPPLEMENTARY INFORMATION 20-4

20.7. FUNDAMENTALS OF SYMSTREAM 20-5

20.7.1. ELEMENTS OF SYMSTREAM 20-5

20.7.1.1. VAR IABLES 20-5

20.7.1.2. PROCESS PARAMETERS 20-5

20.7.1.3. INTEGER EXPRESSIONS 20-5

20.7.1.4. STREAM GENERATION STATEMENTS 20-5

20.7.1.5. NUMERIC EXPRESSIONS 20-6

20.7.1.6. SUPPLEMENTARY BASICS 20-6

20.7.2. SYNTAX OF SYMSTREAM 20-6

20.7.2.1. GENERATING OUTPUT STREAMS (*BRKPT) 20-7

20.7.2.2. ZEROING EXISTING AND CREATED VARIABLES (*CLEAR) 20-7 20.7.2.3. MERGING INPUT AND SKELETON STREAMS (*CORRECT AND *END) 20-8 20.7.2.4. DYNAMIC EXPANSION OF SSG's OR PERM AND TEMP CHAINS (*CREATE) 20-9 20.7.2.5. DEFINING SKELETON IMAGE SEQUENCES (*DEFINE AND *END) 20-9

20.7.2.6. VARIABLE DIVISION (*DIVIDE) 20-10

20.7.2.7. OUTPUTIING NONDIRECTIVE SKELETON IMAGES AS ONE IMAGE (*EDIT) 20-10 20.7.2.8. SKIPPING SKELETON IMAGES (*IF, *ELSE, AND *END) 20-11 20.7.2.9. SKELETON IMAGE LOOPS (*INCREMENT AND *LOOP) 20-13

20.7.2.10. VARIABLE MULTIPLICATION (*MULTIPLY) 20-14

20.7.2.11. CALLING A PREDEFINED SEQUENCE OF SKELETON IMAGES (*PROCESS) 20-14 20.7.2.12. DELETING SGS's, AND PERM AND TEMP ELEMENT/VERSION NAMES (*REMOVE) 20-15 20.7.2.13. CHANGING EXISTING OR CREATED VARIABLES (*SET) 20-16

20.8. EXAMPLES OF SSG STREAM GENERATION 20-17

20.9. MERGE OF INPUT STREAMS 20-22

20.10. BACKUS NORMAL FORM OF SYMSTREAM ELEMENTS 20-25

20.11. DIRECTIVES STRUCTURE 20-26

21. DOCUMENTATION PROCESSORS 21.1. INTRODUCTION

21.2. FLOWCHART GENERATOR (FLUSH) 21.2.1. GENERAL OUTPUT

21.2.2. OPERATION MODES

21.2.3. FLUSH DIRECTIVE OPTIONS 21.2.3.1. TYPE I OPTIONS (I, J, P, T, W) 21.2.3.2. TYPE II OPTION (A)

21.2.3.3. TYPE III OPTIONS (E, H)

21.2.3.4. TYPE IV OPTIONS (B, C, D, N, R) 21.2.3.5. TYPE V OPTIONS (L, S)

21.2.4. CONTINUATION REQUIREMENTS 21.2.5. SUMMARY OF BOX TYPES 21.3. DOCUMENT PROCESSOR (DOC) 21.3.1. OUTPUT LISTINGS

21.3.2. INTERNAL CONTROL DIRECTIVES 21.3.2.1. TITLE CONTROL

21.3.2.2. LISTING CONTROL 21.3.2.3. TEXT CONTROL 21.3.2.4. EDITING CONTROL

21-1 21-1 21-2 21-2 21-3 21-4 21-5 21-6 21-9 21-11 21-12 21-12 21-13 21-13 21-14 21-14 21-15 21-15 21-16 21-17

to 21-19

(19)

\~

'-.. -_/

... _ ...

4144 Rev. 2

UP.NUMBER

PAGE REVISION PAGE

22.

MASTER FILE DIRECTORY 22·1 to 22·36

22.2. MASTER FILE DIRECTORY STRUCTURE 22·1

22.3. MASTER FILE DIRECTORY MANIPULATION (MSCON$) 22·2

22.3.1. ITEM RETRIEVAL FOR ALL FILES (DGET$) 22·4

22.3.2. ITEM RETRIEVAL FOR DISC PACKS (DGETP$) 22·8

22.3.3. ITEM RETRIEVAL FOR AN INDIVIDUAL FILE (DREAD$) 22·9

22.3.4. ALTERING MAIN ITEM (DBIT$) 22·10

22.3.5. ALTERING BACKUP FILE ENTRIES (DBACK$) 22·10

22.3.6. ALTERING LAPSE ENTRIES (DLAPS$) 22·11

22.3.7. CHANGING UNLOAD TIME (DUNLD$) 22·13

22.3.8. CHANGING MAXIMUM CYCLE RANGE (DCYC$) 22·13

22.3.9. CHANGING READ/WRITE KEYS (DKEY$) 22·14

22.3.10. CHANGING BLOCK BUFFERING EOF SECTOR ADDRESS (DBB$) 22·14

22.3.11. MODIFYING FILE IDENTITY (DREG$) 22·15

22.3.12. LINK INSERTION FOR REMOVABLE DISC PACKS (DLlNK$) 22·16

22.3.13. ADDING GRANULE ITEMS (DADD$) 22·16

22.3.14. MONITORING MASS STORAGE AVAILABILITY (MSALL$) 22·17

22.4. MSCON$ STATUS CONDITIONS 22·21

22.5. DIRECTORY ITEM FORMATS 22·22

23.

LOGGING AND ACCOUNTING 23·1 to 23·27

23.2. LOG ENTRY INITIATION AND CONTROL 23·1

23.3. PRINT FILE OUTPUT 23·2

23.4. SUMMARY ACCOUNT FILE CREATION AND UPDATING 23·3

23.5. MASTER LOG FILE CREATION AND CONTROL 23·3

23.6. FILE FORMATS 23·3

23.6.1. BASIC NOTATION 23·3

23.6.2. SUMMARY ACCOUNT FILE STRUCTURE 23-4

23.6.3. SUMMARY ACCOUNTING FILE ENTRY FORMAT 23·5

23.6.4. MASTER LOG ENTRY FORMATS 23·7

23.6.4.1. CONTROL STATEMENT LOG ENTRIES 23·8

23.6.4.2. FACILITY USAGE LOG ENTRIES 23·9

23.6.4.3. CATALOGUED MASS STORAGE FILE USAGE ENTRY 23·10

23.6.4.4. PROGRAM TERMINATION LOG ENTRY 23·12

23.6.4.5. RUN TERMINATION LOG ENTRY 23·13

23.6.4.6. I/O ERROR LOG ENTRY 23·14

23.6.4.7. CONSOLE LOG ENTRIES 23·16

23.6.4.8. CHECKPOINT LOG ENTRY 23·17

23.6.4.9. RUN INITIATION LOG ENTRY 23·18

23.6.4.10. CONSOLE REPLIES LOG ENTRY 23·19

23.6.4.11. LOG KEYIN ENTRY 23·19

23.6.4.12. UNSOLICITED KEYIN LOG ENTRY 23·20

23.6.4.13. TAPE LABELING LOG ENTRY 23·30

(20)

4144 Rev. 2

UP.NUM BER

PAGE REVISION PAGE

23.7. BILLING ROUTINE (BILLER) 23-21

23.7.1. GENERAL DESCRIPTION 23-21

23.7.2. CONSTRAINTS FOR USER-IMPLEMENTED BILLING ROUTINES 23-21

23.7.3. INITIALIZING AND CHAINING OF ACCOUNT ENTRIES 23·22

23.7.3.1. INSERT COMMAND 23·22

23.7.3.2. REMOVE, PURGE, AND READ COMMANDS 23·23

23.7.3.3. NO INPUT SPECIFIED TO BILLER 23·24

23.7.4. PRINTER OUTPUT 23·24

23.8. LOG FI LE EDITOR (LOGFED) 23-25

24.

FILE STRUCTURE AND MAINTENANCE 24-1 to 24-14

24.2. FILE FORMATS 24-1

24.2.1. PROGRAM FILE FORMAT 24-1

24.2.2. ELEMENT FILE FORMAT 24-3

24.2.3. SYSTEM DATA FILE (SDF) FORMAT 24-4

24.3. FILE MAINTENANCE 24-7

24.3.1. PROGRAM FILE MAINTENANCE EXECUTIVE REQUESTS 24-7

24.3.1.1. UPDATING THE ELEMENT TABLE (PFI$) 24-7

24.3.1.2. TABLE OF CONTENTS SEARCH (PFS$) 24-10

24.3.1.3. MAR K ELEM ENT FOR DELETION (PFD$) 24-11

24.3.1.4. UPDATING NEXT WRITE LOCATION )PRUWL$) 24-12

24.3.1.5. RETRIEVING NEXT WRITE LOCATION ADDRESS (PFWL$) 24-12

24.3.1.6. PROGRAM FILE PACKAGE STATUS CONDITIONS 24-13

24.3.2. PROGRAM FILE BASIC SERVICE PACKAGE 24-13

25.

INTERNAL EXECUTIVE DESIGN 25·1 to 25-17

25.2. BASIC DESIGN PHILOSOPHY 25-1

25.3. EXECUTIVE MAIN STORAGE USAGE 25-2

25.3.1. GENERAL LAYOUT AND DISCUSSION 25·2

25.3.2. PCT USAGE 25-3

25.3.3. DEFINITION AND RESIDENCY OF COMPONENTS 25-3

25.4. MULTIPROCESSING 25-5

25.5. SCHEDULING 25-5

25.5.1. GENERAL 25-5

25.5.2. FACILITIES INVENTORY AND SELECTION 25-5

25.5.3. CONTROL STATEMENT INTERPRETER (CSI) 25-7

25.5.4. COARSE SCHEDULER 25-7

25.5.5. DYNAMIC ALLOCATOR 25-9

25.5.5.1. GENERAL OVERVIEW 25-9

25.5.5.2. DYNAMIC MAIN STORAGE ALLOCATION 25-9

25.5.5.3. DEMAND/BATCH SHAR ING 25-11

25.5.5.4. TIMESHARING 25-11

25.5.6. DISPATCHER 25·12

25.5.6.1. INTERLOCK PROCESSING 25-12

25.5.6.2. SWITCHING 25-13

(21)

4144 Rev. 2

UP-NUMBER

PAGE REVISION PAGE

25.6. CLOCKI NG

25.6.1. REAL TIME CLOCK 25.6.2. DAY CLOCK

25.7. INTERRUPT HANDLING

25.7.1. INPUT/OUTPUT INTERRUPTS AND QUEUEING 25.7.2. INTERPROCESSOR INTERRUPTS

25.7.3. HARDWARE FAULT INTERRUPTS

25.7.3.1. STORAGE AND ICR PARITY ERROR INTERRUPTS 25.7.3.2. POWER LOSS INTERRUPTS

25.7.4. PROGRAM-GENERATED INTERRUPTS 25.8. CATALOGUED FILE RECOVERY

26. RUN SETUP EXAMPLES

APPENDIXES

A. SUMMARY OF CONTROL STATEMENTS

B. SUMMARY OF EXECUTIVE REQUESTS

C. SYSTEM DIAGNOSTIC MESSAGES AND STATUS CODES C.1. RUN STREAM DIAGNOSTIC MESSAGES

C.2. FACILITY REQUEST STATUS CODES

C.3. ERR MODE (EMODE) AND I/O STATUS CODES C.4. CSF$ EXECUTIVE REQUEST STATUS CODES

C.4.1. FACILITY REQUEST STATUS CODES (@CAT, @ASG, @FREE, @LOG, @MODE, @USE) C.4.2. @SYM AND @BRKPT STATUS CODES

C.4.3. @ADD STATUS CODES

C.4.4. @START DIAGNOSTICS AND STATUS CODES

C.4.5. CHECKPOINT/RESTART STATUS CODES (@CKPT, @CKPAR, @RSTRT, @RSPAR) C.5. MSCON$ AND PFP STATUS CODES

C.5.1. MSCON$ REQUEST STATUS CODES

C.5.2. PROGRAM FILE PACKAGE STATUS CODES C.6. CHECKPOINT/RESTART ERROR CODES

C.7. BLOCK BUFFERING AND ITEM HANDLER ERROR CODES C.7.1. DEVICE AND FILE EXIT CODES

C.7.2. ABNORMAL EXIT CODES

25-14 25-14 25-14 25-14 25-15 25-15 25-16 25-16 25-16 25-17 25-17

26-1 to 26-12

A-1 to A-6

B-1 to B-6

C-1 to C-29 C-1

C-10 C-12 C-22 C-22 C-22 C-22 C-23 C-23 C-23 C-23 C-25 C-25 C-27 C-27 C-29

(22)

4144 Rev. 2

UP.NUMBER

D. CONVERSION TABLES 0.1. INTRODUCTION

0.2. ASCII AND FIELDATA CONVERSION TABLES 0.2.1. THE SPECIAL CHARACTERS IN ASCII 0.3. UNISCOPE 100 DISPLAY TERMINAL

0.4. CHARACTER CODES, XS·3, BCD CONVERSION TABLE 0.5. BINARY/HEXADECIMAL CONVERSION TABLE 0.6. OCTAL/DECIMAL CONVERSION TABLE

E. EQUIPMENT CODES

FIGURES

6-1. I/O Packet, Mass Storage and Magnetic Tape Peripherals 6-2. Arbitrary Device Handler Packet

8-1. FURPUR Control Statements Used tq Alter File Formats

10-1. Instruction Area (I Bank) Main Storage Map for the Segmented FILEA 10-2. Data Area (0 Bank) Main Storage Map for the Segmented FILEA 11-1. Standard Editing Format for Integer and Octal Dumps, Sample Printout 13-1. Data Block Layout

13-2. Single Item Layout 13-3. Blocked Item Layout 13-4. File Control Table Format

13-5. Example of Complete Format Definition

13-6. Item Level Tape File Organization, Single·File Reels 13-7. Item Level Tape File Organization, Muotifile Reels

13-8. Item Level Tape File Organization, Multifile Reels with Void File 13-9. Item Level Tape File Organization, Multireel Files

13-10. Item Level FASTRAND·Formatted Mass Storage File Organization 22-1. Example of an MFD Entry

22-2. Search Item

22-3. Lead Item - Sector 0 22-4. Lead Item - Sector 1

22-5. Mass Storage File Main Item - Sector 0 22-6. Mass Storage File Main Item - Sector 1 22-7. Main Item - Sectors 2'n

22-8. Tape File Main Item - Sector 0 22-9. Mass Storage File Granule Item 22-10. Tape File Granul~ Item

PAGE REVISION PAGE

0·1 0·1 0·1 0·4 0·6 0·9 0·11 0·11

E·1

6·2 6·28 8·4

to 0·15

to E·3

10·29 10·30 11·13 13·10 13·23 13·23 13·27 13·38 13·44 13·44 13·45 13·45 13·46 22·2 22·23 22·24 22·25 22·26 22·29 22·31 22·32 22·35 22·36

(23)

\ '-

. ,.,'.' ,

(

\ ... ^_..• ,~'

4144 Rev. 2

UP-NUMBER

UN IV AC 1100 S E R I ES SY STEMS Contents 21

. PAGE REVISION PAGE

23-1. Logging and Accounting Process, Block Diagram 23-2

23-2. Summary Account File Format 23-4

24-1. Program File Format 24-2

24-2. Element File Format 24-4

24-3. Element in Element File Format 24-5

TABLES

3-1. Summary of Executive Control Statements 3-4

3-2. @RUN Control Statement, Options 3-6

3-3. @MSG Control Statement, Options 3-12

3-4. FASTRAND @ASG Control Statement, Options 3-22

3-5. Magnetic Tape -ASG Control Statement, Options 3-26

3-6. @CAT Control Statement, Options 3-36

3-7. @FREE Control Statement, Options 3-38

4-1. Available ERs 4-3

4-2. Contingency Types 4-24

4-3. Error Types 4-25

5-1. Bit Settings in Control Register AO for A R EAD$ Request 5-4

5-2. Print Control Functions 5-12

6-1. Octal and Mnemonic I/O Codes Defined in SYS$*RLlB$ 6-3

6-2. Magnetic Tape I/O Functions and Codes 6-10

6-3. Type 5017 Fieldata/BCD Translations 6-15

6-4. MSA Data Word Formats 6-17

6-5. Magnetic Tape Function vs. Unit Type 6-19

6-6. Standard Tape/Processor Code Translation (Octal) 6-20

6-7. Magnetic Drum and Unitized Channel Storage I/O Functions and Codes 6-21

6-8. FAST RAND Mass Storage I/O Functions and Codes 6-24

7-1. Volume Header Label Field Description for Table Labeling 7-16

7-2. First File Header Label Field Description for Table Labeling 7-17

8-1. Summary of FURPUR Control Statements 8-1

8-2. @COPY Control Statement, Options Applicable When Filenames are Specified 8-5 8-3. @COPY Control Statement, Options Applicable When Element Names are Specified 8-7 8-4. @COPIN Control Statements, Options Applicable When Filenames are Specified 8-9 8-5. @COPIN Control Statement, Options Applicable When Element Names are Specified 8-10 8-6. @COPOUT Control Statements, Options Applicable When Filenames are Specified 8-11 . 8-7. @COPOUT Control Statement, Options Applicable When Element Names are Specified 8-12

8-8. @PRT Control Statement, Options Applicable When Filenames, Account Numbers, 8-14 or Project-id are Specified

8-9. @PRT Control Statement, Options Applicable When Elements are Specified 8-15

9-1. Processors Which Use the SI, SO, and RO Parameters 9-4

9-2. Processors Which Require the SI and SO Parameters 9-5

9-3. Source Input Routine Options 9-6

9-4 . Partial Coding Line Correction Diagnostics 9-10

9-5. @PDP Control Statement, Options 9-12

(24)

4144 Rev. 2

UP.NUMBER

UNIVAC 1100 SERIES SYSTEMS Contents 22

PAGE REVISION PAGE

10-1. @MAP Control Statement, Options 10-3

11-1. @PMP Control Statement, General Options 11-2

11-2. @PMD Control Statement, Special Options 11-3

11-3. Standard Editing Formats for Dump Printouts 11-14

11-4. Demand Mode Commands 11-27

12-1. Demand Terminal Interface Messages 12-3

12-2. Teletypewriter Control Characters 12-8

12-3. DCT 500 Control Characters 12-13

12-4. UNISCOPE 100 and DCT 1000 Control Messages and Sequences 12-17

12-5. UNISCOPE 300 Symbiont, Control Sequences 12-21

13-1. Device Error Status Codes 13-47

14-1. Editing Routines for Initiation and Termination of Editing Mode 14-4

14-2. General Purpose Editing Routines 14-5

14-3. Floating-Point Editing Routines 14-9

15-1. L TT Input-Status Codes 15-6

18-1. @ELT Control Statement, Options 18-2

18-2. @DATA Control Statement, Options 18-5

18-3. @ED Control Statement, Options 18-7

18-4. ED Processor Commands 18-8

18-5. @CULL Control Statement, Options 18-16

19-1. @SECU REControl Statement, Options 19-3

19-2. Summary of SECU R E Processor Commands 19-9

20-1. @SSG Control Statement, Options 20-4

21-1. Summary of FLUSH Directive Options 21-4

21-2. @DOC Control Statement, Options 21-14

21-3. DOC Processor, Title Control Directives 21-15

21-4. DOC Processor, Listing Control Directives 21-16

25-1. Executive Components That Reside Permanently in Main Storage 25-3

25-2. Nonresident (Transient) Components of the Executive System 25-4

C-1. Facility Status Bits C-10

C-2. ERR Mode (EMODE) and I/O Status Codes C-12

C-3. @SYM and @BRKPT Status Codes C-22

C-4. Status Codes for Successful Completion (S=O) C-24

C-5. Status Codes for Error Termination (S=1) C-24

C-6. Checkpoint Error Codes C-26

C-7. Restart Error Codes C-26

C-8. Device and File Exit Codes C-27

(25)

\

4144 Rev. 2

UP-NUMBER

UNIVAC 1100 SERIES SYSTEMS

D-1. Fieldata=to-ASCII Conversion D-2. ASCII-to-Fieldata Conversion

D-3. UN ISCOPE 100 Display Term inal Control Functions D-4. Illegal Text Characters

D-5. Cursor/SOE Coordinates

D-6. XS-3 Fieldata-EBCD IC-BCD Conversion Table D-7. Binary/Hexadecimal Conversion

D-8. Octal/Decimal Conversion

PA GE RE VISION

D-2 D-3 D-6 D-7 D-8 D-9 D-11 D-12

Contents 23

PAGE

(26)

(27)

4144 Rev. 2

UP.NUMBER

1.1.

SCOPE OF MANUAL

UNIVAC 1100 SERIES SYSTEMS 1-1

PAGE REVISION pAGE

I. INTRODUCTION

The UN IVAC 1100 Series Operating System comprises the Univac-supplied software for the UN IVAC 1100 Series Computer Systems. This manual discusses the base portion of the operating system, that is, the executive system (EX EC 8) and the associated software needed to construct, execute, and maintain user programs. Information on language processors such as COBOL, FORTRAN, and the assembler, and on applications software such as SORT/MERGE, APT, and PERT can be found in their respective manuals.

Information that is primarily of interest only to an operator, installation manager, or systems analyst is covered only briefly if at all (for example, operating procedures, system generation procedures, internal system logic, and so forth). Such material is covered in other Univac publications.

The purpose of this manual is to provide information for the user programmer so that he can make full use of the wide range of capabilities provided by the UN IVAC 1100 Series Hardware/Software Systems. Any differences between the operating system described in this manual and the latest released software are described in the Univac 1100 Series System Memorandum.

A knowledge of the 1100 series hardware architecture and machine (assembler) language programming is assumed. This knowledge is helpful, but not mandatory for the user of a higher level language or ~pplications package.

1.2.

THE OPERATING SYSTEM

The UNIVAC 1100 Series Operating System was designed to meet the total computing requirements of today's users, and to allow for the change and growth required for the future. The operating system is the outgrowth of Univac's many years of experience in multiprogramming, multiprocessing, time sharing, communications, and real time oriented systems, and provides a system that contains the facilities required in complex environments, yet it is easy to operate and use.

A complete set of software, ranging from high level language compilers to basic service functions, is included in the operating system. The six major categories are:

II Executive System II System Processors 11 Utility System Processors II Language Processors a Subroutine Library

Applications Programs

(28)

4144 Rev. 2

UP-NUMBER

PAGE REVISION PAGE

The first three categories are discussed in detail in this manual. The execution environment is specified for the software falling into the last three categories. In addition to the standard operating system, this manual describes certain utility routines provided only for the convenience of the user and they are not supported as operational software. These unsupported utility routines are:

Document Processor (DOC) - see Section 21 Flow Charting Processor (FLUSH) - see Section 21 Log File Editor (LOGFED) - see Section 23 Billing Routine (BILLER) - see Section 23 Element Listing Routine (LIST) - see Section 18 Cross-reference Processor (CULL) - see Section 18 CUR-to-FUR Conversion (CON78) - see Section 18 Program Trace Routine - see Section 11

1.3.

THE EXECUTIVE SYSTEM

To take full advantage of the speed and hardware capabilities of the 1100 series and to make effective use of a given hardware configuration, a comprehensive internal operating environment has been created.

This environment permits 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 accords with the stringent demands of real time applications; it can store, file, retrieve, and protect large blocks of data; and it makes the best use of all available hardware facilities, while minimizing job turnaround time.

Only through central control of all activities of the system can this environment of the combined hardware and software systems be fully established and maintained to satisfy the requirements of all applications. The responsibility for efficient, flexible, centralized control is borne by the executive system, which controls and coordinates the functions of the complex internal environment. By presenting a relatively simple interface to the programmer it allows him to use the system easily, while relieving him of concern for the internal interaction between his program and other coexistent programs.

1.3.1. MULTIPLE MODES OF OPERATION

The technical capabilities of the executive system cover a great variety of data processing activities. Its design is such that no penalties are imposed upon anyone of these activities by the support provided for the others, and an installation not interested in making use of the full range of capabilities may specify component features to be eliminated at system generation time.

1.3.1.1. BATCH PROCESSING

Foremost among the capabilities of the executive system is the support provided for batch processing. The system is designed to ease run preparation and submission, to shorten job turn-around time, and to reduce the need for operator intervention and decisions. Batch jobs may be processed from a variety of remote terminals, as well as from central site equipment.

1.3.1.2. DEMAND PROCESSING (TIME-SHARING)

Complementing the batch processing capabilities of the executive system are its time-sharing capabilities, the simultaneous accommodation by the executive system of requests and demands from users at numerous remote inquiry terminals,

(29)

4144 Rev. 2

UP-NUMBER

UNIVAC 1100 SERIES SYSTEMS 1-3

PAGE REVISION PAGE

operating in a demand (or conversational) mode. All facilities available to the batch processing user are also available in the demand mode, the primary difference being that the executive system permits the user additional flexibility in the statement and control of individual runs; when an error is made, the user simply corrects it online and proceeds rather than suffering the turn-around cycle inherent in batch processing. The demand user may communicate directly with either the executive or a user program or he may communicate with a conversational processor, such as Conversational FORTRAN.

1.3.1.3. REAL TIME PROCESSING

The executive system is also designed to be applicable to programs which have real time requirements. The UNIVAC Communications Subsystem, together with efficient scheduling and interrupt processing features of the executive system, provide an environment satisfactory for any real time program.

1.3.1.4. MULTIPROGRAMMING AND MULTIPROCESSING

Runs may come from many sources, remote and central. These various runs, through the executive system's use and control of efficient multiprogramming and multiprocessing techniques may, at any given moment, be in different stages of activity;

input, processing, and output may all be occurring simultaneously, thus ensuring efficient operation.

1.3.2. UTILIZATION OF MASS STORAGE

The executive system is designed to ensure effective and efficient utilization of the mass storage devices. The consequence is an unprecedented ability to relieve operators and programmers of the responsibility of maintaining and handling cards and magnetic tapes, thus eliminating many of the errors which heretofore have accompanied the use of large scale software systems. At the same time, the overall operating efficiency is considerably improved.

Permanent data files and program files are maintained on the mass storage devices, with full facilities for modification and manipulation of these files. Security measures are established by the executive system to ensure that files are not subject to unauthorized use. Provisions are also made within the executive system for automatic relocation of infrequently used files to magnetic tape, as unused mass storage space approaches exhaustion. When the use of files relocated in such a manner is requested, they are retrieved and restored under control of the executive system with no inconvenience to the user.

1.3.3. FUNCTIONAL AREAS OF THE EXECUTIVE SYSTEM

The executive system is composed of many different routines which perform many different functions. These functions and routines are summarized in the following paragraphs.

1.3.3.1. EXECUTIVE CONTROL LANGUAGE

In the executive system, the user has a simple means of directing the execution of the individual tasks of a run and of relaying operational information concerning the run to the executive. This is accomplished through a set of control statements capable of performing all of the functions desirable or necessary in a modern executive system. The control language is open ended and easily expanded, so that features and functions may be added as the need arises.

The basic format of a control statement is quite simple, and is adaptable to a large number of input devices. Statements are not restricted to punched cards and may be of variable lengths. Each control statement consists of a heading character (@), for recognition purposes, followed by a command and a variable number of parameters. The end of a control statement is indicated by the end of a card, a carriage return, or an equivalent signal, depending on the type of input device.

1.3.3.2. THE S,UPERVISOR

The supervisor is the executive system component that controls the sequencing, setup, and execution of all runs. It is designed to control the execution of a large number of independent and interdependent programs.

(30)

4144 Rev. 2

UP.NUMBER

PAGE REVISION PAGE

The supervisor contains three levels of scheduling: coarse scheduling, dynamic allocation of storage space, and central processor unit (CPU) dispatching. Runs entering the system are sorted into information files and these files are used by the supervisor for run scheduling and processing. Control statements for each run are retrieved and scanned by a control statement interpreter in the supervisor to facilitate the selection of runs for setup by the coarse scheduler. The coarse scheduling of each run primarily depends on two factors: the priority of the run, and its facility requirements.

The dynamic allocator takes runs set up by the coarse scheduler and allots storage space according to the needs of the individual tasks (programs) of a run. Normally, tasks from many different runs are located in storage at the same time. Each run may be thought of as being made up of tasks, where a task is a single operation of a system processor or the execution of a user program. All tasks for a given run are processed serially but not necessarily consecutively; if there are several runs, the tasks of separate runs are interleaved.

When time-sharing of storage is appropriate, the dynamic allocator initiates storage swaps. This involves writing one program on mass storage and replacing it temporarily in main storage with another program. Such action is taken only to provide reasonable response time to remote demand-processing terminals, or to satisfy batch priority requirements.

The CPU dispatching routine is a third level of scheduling; it selects among the various tasks currently occupying main storage whenever it is appropriate to switch the commitment of the CPU from one task to another. Under normal circumstances, a batch program is allowed to use a CPU either until it becomes interlocked against some event or until some higher priority program is freed of all of its interlocks. On multiprocessor systems, two or more tasks will be in actual execution at the same time.

1.3.3.3. FACILITIES ASSIGNMENT

Available facilities and their disposition are indicated to the system at system generation time; thereafter, the executive system assigns these facilities, as needed and as available, to fulfill the facilities requirements of all runs entering the system.

The executive system maintains current inventory tables that indicate what facilities are available for assignment, and which runs are using the currently unavailable facilities.

1.3.3.4. FI LE CONTROL

The executive file control routines afford the highest degree of operational flexibility in storing and retrieving data, without concern for the physical characteristics of the recording devices. Thus, most files are made insensitive to input/output (I/O) media characteristics, as the system adjusts the interface between the file and the device. Security measures ensure that files are not subject to unauthorized use or destruction. File control routines are provided to roll out files from mass storage devices to magnetic tape, as well as reconstruct such files on the mass storage devices when the'user calls for them.

Comprehensive utility routines are available for manipulation of files and for informing the user of current status and structure of his files. Provisions are made for random storage and retrieval of data, under the direction of the user. User program files and data files are maintained and processed in the same environment.

1.3.3.5. OPERATOR COMMUNICATIONS

Operator functions are required for a large variety of activities. The executive system groups them into four classes, thus equally dividing operator duties in a multioperator installation. These functions may be associated with as many as three system consoles or as few as one, depending on the complexity and layout of the installation.

The executive system displays information such as current system load and operator requests associated with I/O setup and I/O interlocks. The operator can request other information, such as backlog status. If the display area becomes filled up, the executive defers lower priority displays.

Since this manual is for the user programmer as opposed to the computer operator, it does not contain detailed information concerning the operator communication functions.

(31)

.\.. ..

4144 Rev. 2

UP-NUMBER

PAGE REVISION PA GE

1.3.3.6. INPUT/OUTPUT DEVICE HANDLERS AND SYMBIONTS

The input/output device handlers and symbionts control the activities of all I/O channels and peripheral equipment attached to the system.

The following is a list of the onsite and remote peripheral hardware that is supported by the executive:

IJ Mass Storage Devices

FH-432, FH-880, and FH-1782 Magnetic Drum Subsystems Unitized Channel Storage

8414 0 isc Subsystem

FASTRAND II and" I Magnetic Drum Subsystems 13 Magnetic Tape Devices

UN ISE RVO 12 and 16 Magnetic Tape Subsystems

UNISERVO IV-C, VI-C, and VIII-C Magnetic Tape Subsystems UNISERVO II-A and III-A Magnetic Tape Subsystems

lEI Printer Subsystems

Type 0751,0755,0758, and 0768 High Speed Printers UNIVAC 1004 Printer

a

Card Subsystems

Type 0706 and 0711 Card Readers Type 0600 and 0603 Card Punches UNIVAC 1004 Card Reader/Punch C Remote Devices

Onsite Interface Hardware

(1) Communications Terminal Module Controller Subsystem (CTMC) (2) Communications Terminal Synchronous Subsystem (CTS) (3) Word Terminal Synchronous Subsystem (WTS)

Remote Terminal Hardware (1 )

(2) (3) (4) (5)

(6)

(7) (8)

I

UNISCOPE 100 Display Terminal

UNISCOPE 300 Visual Communications Terminal

OCT 2000, 1000, and 500 Data Communications Terminals UN IV AC 9300/9300-11 Remote System

UNIVAC 9200/9200-11 Remote System Teletypewriter Models 33 and 35 UN IVAC 1004 Card Processor Friden 7100 Typewriter

(32)

4144 Rev. 2

UP.NUMBER

PAGE REVISION PAGE

1.4. SYSTEM PROCESSORS

The system processors of the operating system are programs which provide for the utilitarian functions required to construct and modify programs, maintain and modify files, and provide diagnostic information upon program termination.

1.4.1. COLLECTOR

The collector is designed to provide the user with the means of collecting and linking relocatable subprograms to produce an absolute program in the form ready for execution under control of the executive system.

1.4.2. FILE UTILITY PROCESSOR (FURPUR)

FURPUR consists of a set of file maintenan"ce routines which provide the flexibility in management and manipulation of catalogued or temporary files containing data or programs.

1.4.3. POSTMORTEM DUMP PROCESSOR (PMD)

The postmortem dump processor (PMD) produces edited dumps of the contents of main storage at program termination;

dumps produced dynamically during execution are automatically printed. Individual program parts are identified with the assistance of diagnostic tables produced with the absolute program by the collector.

1.4.4. DATA AND EL T PROCESSORS

The DATA and E L T processors are used to create and manipulate data streams and program elements.

1.4.5. FILE ADMINISTRATION PROCESSOR (SECURE)

The SECU R E processor uses a source language structure which allows the user to define specific tasks with simple COBOL·like statements. The processor's primary functions are to produce backup tapes for catalogued files, and to provide a

recovery mechanism for these files in case of system failure. /

1.4.6. TEXT EDITOR (ED)

The ED processor is a text editor which enables a user to modify or move character strings in either program files or data files.

1.4.7. PROCEDURE DEFINITION PROCESSOR (PDP)

The procedure definition processor (PDP) accepts source language statements defining assembler, COBOL, or FORTRAN procedures and builds an element in the user·defined program file. These procedures may subsequently be referenced in an assembly or compilation without definition.

1.5. SYSTEM UTILITY PROCESSORS

The system utility processors provide features which are commonly required and used. Unlike the system processors, the features provided are not necessary for the effective utilization of the operating system.

1.5.1. CUR-TO-FUR CONVERSION (CON78)

This processor converts magnetic tapes created by the UNIVAC EXEC II complex utility routine (CUR) to magnetic tapes acceptable as input to UNIVAC 1100 series program files. The processor will accept UN IVAC EXEC II symbolic elements, COBOL library elements, and procedure elements, and converts them to the proper formats.