Full text of "cdc :: cyber :: cyber 70 :: kronos :: 60407000D KRONOS2.1v1 Jun75"

See other formats

60407000

CONTRPL DATA
CORPORATION

KRONOS® 2.1
REFERENCE MANUAL

Volume 1 of 2

CONTROL DATA®
CYBIEIR 70 SERIES

MODELS 72/73/74
6000 SERIES
COMPUTER SYSTEMS

REVISION RECORD

REVISION

DESCRIPTION

Manual released.

(7-1-73)

Revised to describe 580-12 line printer support, 667/669 tape unit support, TCS and QFM

(6-17-74)

macros, and auxiliary device requests, and to correct various technical and typographical

Revised to update the manual for KRONOS 2. 1. 1. A ll mo dification throu gh level 7 are in-

(12-6-74)

eluded in this revision. The RUN control card and references to FORTRAN 2. 3 are removed.

The ALGOL 4 control card is added. Miscellaneous corrections, smd clarifications are also

included.

Reprint with revision; obsoletes all previous editions. Manual revis ed t o describe the

(6-17-75)

KRONOS 2. 1. 2 operating system at correctiv e code l evel 404, and reorg anize the manual into
two volumes.

The following additions have been made due to KRONOS 2. 1. 2 modifications: enhanced user

controls as described under Validation and the LIMITS c ontro l card; accounting feature (use of

system resource unit and new d a^ rfile messages); 026/029 keypunch cony ersion mode;
RERUN/NORERUN control cards for I/O Queue protection feature; subsystem symbolic

name in control language; new control cards (ENQUIRE, LENGTH. STIM E, SUMMARY, CLEAR,

CONVERT, NEW, OLD, and USER).

This manual contains information which was formerly in the following sections of the manual at

revision C (sections and appendices in parentheses give the new locati on of the information): Sections

_ . ^, , 0-- - ;_; ._

1 through 3(remain the same), section 4 (sections 4 a nd 5 ), section 5 (sections 6, 7 , 8, 9,

10, and 14), section 6 (section 11). section 8 (section 15 ), sect ion 9 (section 10, appendix A,
and appendix F), section 10 (section 13). section 11 (section 10), appendix C (appe ndix C),

appendix H (appendix D), appendix I (appendix G), and appendix J (ap pe ndix E). A new appendix
(B) has been added which contains dayfile messages.

Publication No.
60407000

by Control Data Corporation

Printed in the United States of America

Address comments concerning this
tnanual to:

Control Data Corporation
Publications and Graphics Division
4201 North Lexington Ave.
Arden Hills, Minnesota 55112

or use Comment Sheet in the back of
this manual.

PREFACE

The KRONOS® Time-Sharing System was developed by Control Data Corporation to
provide remote interactive job processing for CONTROL DATA® CYBER 70 Series
Model 72, 73, and 74 Computer Systems and for CONTROL DATA® 6000 Series
Computer System.s. This interactive job processing capability is provided in addi-
tion to the local and remote batch processing capabilities available under KRONOS.

This manual describes the external features of KRONOS 2, 1. 2 for the batch user. In-
formation in this manual should be useful to those who use the programs and utilities
supplied with the system and those who wish to write their own. The manual is con-
tained in two volumes to separate information pertaining primarily to the applications
programmer from that of interest to the systems programmer.

Volume 1 (publication no, 60407000) contains information for the applications programmer.
This includes general information about files, job flow and execution, control card
processing, and an extensive discussion on control cards.

Volume 2 (publication no. 60448200) contains information for those who write system or
assembly language programs for use with KRONOS. It is primarily intended for the
COMPASS programmer; however, several portions contain information for users of
higher level languages. For reference, the table of contents of volunae 2 follows the
table of contents of this volunae.

Throughout this manual cross references to the KRONOS 2. 1 Reference Manual Volume
2 are of the form, "refer to section (or appendix) n, volume 2". If volume 2 is not
stipulated, the reference is to this manual.

This manual does not contain a description of KRONOS system operation, detailed des-
criptions of the software product set available under KRONOS, or descriptions of the
time -sharing commands.

The user is assumed to be familiar with CDC computer systems and with operating
systems in general. For further information concerning CDC CYBER 70 and 6000
Series Computer Systems, the KRONOS time-sharing system, and the products supported
by KRONOS, consult the following manu£j.s.

Control Data Publication

CDC CYBER 70 /Model 72 Computer System Reference Manual

CDC CYBER 70/Model 73 Computer System Reference Manual

CDC CYBER 70/Model 74 Computer System Reference Manual

CDC 6400/6500/6600 Computer Systems Reference Manual

KRONOS General Information Manual

KRONOS Instant Manual

KRONOS Installation Handbook

KRONOS Time-Sharing User's Reference Manual

KRONOS Operator's Guide

Publication No.

60347000
60347200
60347400
60100000
60407100
60407200
60407500
60407600
60407700

60407000 D

111

Control Data Publication

Publication No.

KRONOS Terminal User's Instant

TRANEX Reference Manual

TRANEX Operator's Guide Addendum

Export/Import Reference Manual

Text Editor Reference Manual

BASIC 2 Reference Manual

Time-Sharing FORTRAN Reference Manual

APL *CYBER Reference Manual

Modify Reference Manual

Modify Instant

Update Reference Manual

COMPASS 3 Reference Manual

FORTRAN Extended 4 Reference Manual

COBOL 4 Reference Manual

ALGOL 3 Reference Manual

ALGOL 4 Reference Manual

Sort/Merge 4 Reference Manual

Application Installation Handbook

PERT/ Time 1 Reference Manual

SIMULA 1 Reference Manual

SIMSCRIPT 3 Reference Manual

SYMPL 1 Reference Manual

APEX III Reference Manual

GPSS V/6000 1 General Information Manual

LCGT/IGS 1 Reference Manual

Math Science Library 1 Reference Manual

8-Bit Subroutines 1 Reference Manusil

Total Universal Reference Manual

Common Utilities Reference Manual

On-Line Maintenance Software Reference Manual

Record Manager Reference Manual

Loader Reference Manual

60407800
60407900
60408000
59150500
60408200
19980300
60408600
19980400
60281700
60283000
60342500
60360900
60305600
60384100
60329000
60384700
60343900
76071100
60133600
60234800
60358500
60328800
76070000
84003900
17322800
60327500
60359400
76070300
60493300
60436600
60307300
60344200

This product is intended for use only as described in this document. Control Data cannot be
responsible for the proper functioning of undescribed features or undefined parameters.

60407000 D

CONTENTS

VOLUME 1

SECTION 1

SECTION 2

SECTION 3

SECTION 4

SYSTEM DESCRIPTION
Central Processor Unit
Central Memory

Central Memory Resident

Extended Core Storage
Peripheral Processor Units
Peripheral Hardware
System Software;
User Programs

FILES

Logical /Physical File Structure

Mass Storage Device File Structure

Magnetic Tape File Structure

Punch File Structure
File Types

Queue Files

Special Files
Permanent Filess
Device Residence
Accessing Files

Reading Files

Writing Files
Libraries

JOB FLOW AND EXECUTION
Job Initiation
Job Origin Types
Job Names

System Origin Type (SYOT) Job Name Format

Batch Origin Type (BOOT) Job Name Format

Time-Sharing and Export/Import (TXOT and
EIOT) Job Name Format
Validation
Accounting
Job Scheduling
Job Control

Field Length Control

Input File Control

Time Limit Control

Rollout Control

Error Control
Job Completion

CONTROL LANGUAGE
Expressions

Constants

Arithmetic Operators

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

1-2-1

1-2-2

1-2-3

1-2-4

1-2-7

1-2-8

1-2-10

1-2-11

1-2-14

1-3-1
1-3-6
1-3-6
1-3-6
1-3-6
1-3-7

1-3-7

1-3-8

1-3-10

1-3-11

1-3-12

1-4-1
1-4-2
1-4-2
1-4-2

60407000 D

Relational Operators

Boolean Operators
Evaluation of Expressions
Symbolic Names
Control Language Statements

GOTO Statement

CALL Statement

DISPLAY Statement

SET Statement

IF Statement

FILE Statement

NUM Statement
Procedure Files
Time -Sharing Commands

ASCII Statement

CSET Statement

PARITY Statement

1-4-2

1-4-3

1-4-4

1-4-5

1-4-6

1-4-7

1-4-8

1-4-10

1-4-11

1-4-13

SECTION 5

SECTION 6

CONTROL CARD PROCESSING

Control Card Format

Job Card Format

Control Card Processing Flow

Exit Processing

JOB CONTROL CONTROL CARD

ACCOUNT Card
CHARGE Card
COMMENT Card
CTIME Card
DAYFILE Card
ENQUIRE Card
EXIT Card
LDI Card
LENGTH Card
LIMITS Card
MODE Card
NOEXIT Card
NORERUN Card
OFFSW Card
ONEXIT Card
ONSW Card
PASSWOR Card
RERUN Card
RESOURC Card
RFL Card
ROLLOUT Card
RTIME Card
SETCORE Card
SETPR Card
SETTL Card
STIME Card
SUBMIT Card
SUI Card
SUMMARY Card
SWITCH Card
USECPU Card
USER Card

1-5-1
1-5-1
1-5-4
1-5-6
1-5-8

1-6-1

1-6-2

1-6-3

1-6-4

1-6-5

1-6-6

1-6-8

1-6-9

1-6-10

1-6-11

1-6-14

1-6-15

1-6-16

1-6-20

1-6-21

1-6-22

60407000 D

SECTION 7 FILE MANAGEMENT CONTROL CARDS 1-7-1

ASSIGN Card 1-7-2

BKSPCard 1-7-3

CATALOG Card 1-7-4

CLEAR Card 1-7-8

COMMON Card 1-7-8

CONVERT Card 1-7-8

COPY Card 1-7-9

COPYBF Card 1-7-10

COPYBR Card 1-7-10

COPYCF Card 1-7-11

COPYCR Card 1-7-11

COPYEI Card 1-7-12

COPYSBF Card 1-7-12

COPYXCard 1-7-13

DISPOSE Card 1-7-14

DOCMENT Card 1-7-15

EVICT Card 1-7-16

GTR Card 1-7-17

LIBEDIT Card 1-7-18

LIBGEN Card 1-7-19

L1ST80 Card 1-7-20

LOCK Card 1-7-21

L072 Card 1-7-21

NEW Card 1-7-25

OUT Card 1-7-25

PACK Card 1-7-26

PRIMARY Card 1-7-27

RENAME Card 1-7-27

REQUEST Card 1-7-28

RESEQ Card 1-7-30

RETURN Card 1-7-31

REWIND Card 1-7-32

SETIDCard 1-7-32

SKIPEI Card 1-7-33

SKIPFCard 1-7-33

SKIPFB Card 1-7-33

SKIPR Card 1-7-34

SORT Card 1-7-34

STAGE Card 1-7-36

TDUMP Card 1-7-37

UNLOAD Card 1-7-38

UNLOCK Card 1-7-38

VERIFY Card 1-7-39

VFYLIB Card 1-7-40

WRITEF Card 1-7-40

WRITER Card 1-7-40

SECTION 8 PERMANENT FILE CONTROL CARDS 1-8-1

APPEND Card 1-8-5

ATTACH Card 1-8-6

CATLIST Card 1-8-7

CHANGE Card 1-8-9

DEFINE Card 1-8-10

GET Card 1-8-11

OLD Card 1-8-11

PACKNAM Card 1-8-12

PERMIT Card 1-8-13

PURGALL Card 1-8-13

PURGE Card 1-8-14

60407000 D vii

SECTION 9

SECTION 10

SECTION 11

SECTION 12

SECTION 13

SECTION 14

REPLACE Card
SAVE Card

LOAD/ DUMP CENTRAL MEMORY UTILITY CONTROL

CARDS
DMP Card
DMD Card
LBC Card
LOG Card
PBC Card
RBR Card
WBR Card

TAPE MANAGEMENT
ASSIGN Card
BLANK Card
LABEL Card
LISTLB Card
REQUEST Card
VSN Card
Magnetic Tape Formats

Data Formats

End-of-Tape/End-of-Reel Conditions

PRODUCT SET CONTROL CARDS
User Libraries
Control Card For:mats

FTN Card

COBOL Card

ALGOL 3 Card

ALGOL 4 Card

SORTMRG Card

PERT66 Card

SIMULA Card

SIMSCRIPT Card

BASIC Card

CHECKPOINT/ RESTART
CKP Card
RESTART Card

DEBUGGING AIDS
Central Memory Dumps
Generating Meaningful Dumps
Reading CM Dumps

PROGRAM LIBRARY AND SYSTEM UTILITY CONTROL

CARDS
Program Library Utility Control Cards

MODIFY Card

OPLEDIT Card

UPDATE Card

UPMOD Card
System Utility Control Cards

FAMILY Card

KRONREF Card

SYSEDIT Card

8-1

■8-15

■9-1

■9-2

■9-3

■9-4

■9-5

■10-

-10-

■10-

-10-

■10-

-10-

■10-

-10-

-11-

■3

-11-

•10

-11-

■12

-11-

■15

-11-

■16

-u-

•16

-11-

.18

-11-

■18

-12-

■1

-12-

-1

-12-

-2

-13-

-1

-13-

-1

-13-

-2

-13-

-3

_14.

-1

-14-

-1

-14

-1

-14

-3

-14

-7

-14

-10

-14

-10

-14

-11

-14

-12

-14

-13

Vlll

60407000 D

SECTION 15

LOADERS

Link Relocatable Loader

Memory Map

Link Card

1-15-1
1-15-2
1-15-2
1-15-2

APPENDIX A
APPENDIX B
APPENDIX C
APPENDIX D
APPENDIX E
APPENDIX F
APPENDIX G

CHARACTER SETS

DAYFILE MESSAGES

LIBEDIT

JOB OUTPUT INFORMATION

PERMANENT FILE DEVICE STATISTICS

CARD FORMAT AND CONVERSION PROBLEMS

TAPE LABELS

1-A-l
1-B-l
1-C-l
1-D-l
1-E-l
1-F-l
1-G-l

1-1-1

1-2-1

1-2-2

1-2-3

1-3-1

1-3-2

1-3-3

1-3-4

1-3-5

1-5-1

1-7-1

1-13-1

1-13-2

1-13-3

1-13-4

1-13-5

1-13-6

1-13-7

1-13-8

1-13-9

1-13-10

1-C-l

1-G-l

l-G-2

l-G-3

l-G-4

l-G-5

l-G-6

l-G-7

FIGURES

Central Memory Layout 1-1-2

Sanaple Card File Structure 1-2-2

Sample Random Access File Format 1-2-9

Modified Sample Random Access File 1-2-13

Basic Job Deck 1-3-1

COMPASS Assemble and Execute Deck 1-3-2

COMPASS Assemble, Execute, and Punch Binary Deck 1-3-3

FORTRAN Compile and Execute Deck 1-3-4

FORTRAN Load and Run Deck 1-3-5

Control Card Processing Flow 1-5-7

Sample Page of Catalog of SYSTEM 1-7-6

Exchange Package 1-13-1

Main Program of Main Overlay (0. 0) 1-13-5

Function Subroutine of Main Overlay (0. 0) 1-13-6

Subroutine of Main Overlay (0,0) 1-13-6

Main Program of Primary Overlay (1,0) 1-13-7

Loader Map of Main Overlay (0, 0) 1-13-8

Loader Map of Primary Overlay (1,0) 1-13-11

Program Output 1-13-11

Exchange Package Dumip 1-13-12

Central Memory Dump 1-13-12

Adding to the Old Program Library l-C-8

ANSI Labels: Single File, Single Volume l-G-13

Single File, Multivolume l-G-13

Multifile, Single Volume l-G-14

Multifile, Multivolume l-G-15

End-of-File, End-of- Volume Coincidence l-G-16

End-of-File, End-of- Volume Coincidence 1-G-l 7

End-of-File, End-of- Volume Coincidence l-G-18

ANSI Labels:
ANSI Labels:
ANSI Labels:
ANSI Labels:
ANSI Labels:
ANSI Labels:

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

TABLES

Response to Current Access Write/Read Access Desired 1-8-6

Response to Current Access Read/Read Access Desired 1-8-6

Response to Current Access Read/Write Access Desired 1-8-7

60407000 D

VOLUME 2

SECTION 1 INTRODUCTION 2-1-1

Function Processors 2-1-1

Macros and Common Decks 2-1-1

SECTION 2 PROGRAM/ SYSTEM COMMUNICATION 2-2-1

System Requests 2-2-1

System Request Processing 2-2-1

Issuing RA+1 Requests 2-2-3

Macro Usage 2-2-5

SYSCOM 2-2-5

Common Deck Usage 2-2-8

SECTION 3 FILE CREATION AND INPUT/OUTPUT 2-3-1

File Environment Table (FET) 2-3-1

Circular Buffers 2-3-2

FET Description 2-3-4

FET Creation Macros 2-3-14

FILEB 2-3-14

FILEC 2-3-14

RFILEB 2-3-14

RFILEC 2-3-14

CIO - Combined Input/Output 2-3-16

CIO Function Processing 2-3-20

Random Processing 2-3-20

CIO Open and Close Functions 2-3-22

OPEN 2-3-22

CLOSE 2-3-26

CLOSER 2-3-27

CIO Read Functions 2-3-29

RPHR (000) 2-3-29

READ (010) 2-3-29

READSKP (020) 2-3-30

READCW (200) 2-3-31

READLS (210) 2-3-33

RPHRLS (230) 2-3-34

READNS (250) 2-3-35

READN (260) 2-3-35

READEI (600) 2-3-36

CIO Write Functions 2-3-37

WPHR (004) 2-3-37

WRITE (014) 2-3-37

WRITER (024) 2-3-38

WRITEF (034) 2-3-38

WRITECW (204) 2-3-39

REWRITE (214) 2-3-39

REWRITER (224) 2-3-40

REWRITEF (234) 2-3-40

WRITEN (264) 2-3-41

60407000 D

File Positioning Functions

BKSP (040)

BKSPRU (044)

REWIND (050)

UNLOAD (060)

RETURN (070)

POSMF (110)

EVICT (114)

SKIPF (240)

SKIPFF (240)

SKIPEI (240)

SKIPB (640)

SKIPFB (640)
Data Transfer Macros

READC

WRITEC

READH

WRITER

READO

WRITEO

READS

WRITES

READW

WRITEW

2-3-42
2-3-42
2-3-43
2-3-44
2-3-46
2-3-48
2-3-49
2-3-52
2-3-52
2-3-53
2-3-54
2-3-54
2-3-55
2-3-55
2-3-59
2-3-60
2-3-60
2-3-60
2-3-61
2-3-61
2-3-62
2-3-62
2-3-63
2-3-63

SECTION 4

LOCAL FILE MANAGER

RENAME (000)

ASSIGN (001)

COMMON (002)

RELEASE (004, 005. 006, 007, 016, 030)

LOCK (010)

UNLOCK (Oil)

STATUS (012)

STATUS (013)

REQUEST (014)

REQUEST (015)

SETID (017)

ASSIGN (020)

ACCSF (021)

ENCSF (022)

PSCSF (023)

LABEL (024)

GETFNT (025)

PRIMARY (031)

2-4-1

2-4-2

2-4-3

2-4-4

2-4-5

2-4-6

2-4-7

2-4-8

2-4-10

2-4-11

2-4-12

2-4-13

2-4-14

2-4-15

2-4-20

2-4-22

SECTION 5

PERMANENT FILE MANAGER
Auxiliary Device Requests
SAVE (OOl.CCSV)
GET (002, CCGT)
PURGE (003, CCPG)
CATLIST (004.CCCT)
PERMIT (005, CCPM)
REPLACE (006, CCRP)
APPEND (007, CCAP)
DEFINE (010, CCDF)
ATTACH (Oll.CCAT)
CHANGE (012,CCCG)

2-5-1

2-5-4

2-5-5

2-5-6

2-5-7

2-5-8

2-5-12

2-5-13

2-5-15

2-5-18

2-5-20

60407000 D

SECTION 6

CONTROL POINT MANAGER

SETQP (000)

SETPR (001)

MODE (002)

SETTL (003)

EREXIT (004)

CONSOLE (005)

ROLLOUT (006)

ONSW (Oil)

OFFSW (012)

GETJN (013)

GETQP (014)

GETPR (015)

GETEM (016)

GETTL (017)

SETUI (021)

SETLC (022)

SETRFL (023)

GETJCR (024)

SETJCR (025)

SETSS (026)

GETJO (027)

GETJA (030)

USECPU (031)

USERNUM (032)

GETFLC (033)

PACKNAM (035)

PACKNAM (036)

GETSS (037)

VERSION (044)

GETLC (045)

GETGLS (046)

SETGLS (047)

2-6-1

2-6-2

2-6-3

2-6-5

2-6-7

2-6-8

2-6-9

2-6-10

2-6-11

2-6-12

2-6-13

2-6-14

2-6-15

2-6-16

2-6-17

2-6-18

2-6-19

SECTION 7

SECTION 8

QUEUE FILE MANAGER

RERUN (015)

NORERUN (016)

SUBMIT (017)

Assign File to Queue Device (020)

QUEUE DUMP/ LOAD PROCESSOR
Change File to Local (000)
Release File to Queue (001)

2-7-1
2-7-2
2-7-3
2-7-3
2-7-4

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

SECTION 9

SYSTEM FILE MANAGER
DAYFILE (001, 002, 003, 005)
ESYF (004)
RDVT (006)

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

2-9-4

SECTION 10

JOB CONTROL

Translate Control Statement

CONTROL (004)

EXCST (005)
Checkpoint / Re start

CHECKPT

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

Xll

60407000 D

SECTION 11

SECTION 12

APPENDIX A
APPENDIX B
APPENDIX C
APPENDIX D
APPENDIX E
APPENDIX F
APPENDIX G
APPENDIX H

SYSTEM/LOADER REQUESTS
System Requests

ABORT

CLOCK

DATE

EDATE

ENDRUN

ETIME

JDATE

MEMORY

MESSAGE

MOVE

PDATE

RECALL

RTIME

STIME

SUBR

SYSTEM

TIME
Loader Requests

EXU
LDR
Memory Allocation for Overlay Loaders

PROGRAM WRITING TECHNIQUES
Writing Programs under NOS
Writing Interactive Programs

Conversion Problems

Default File Assignments and Special
File Treatment

Special Handling

Other Special Handling
Program Control of Terminal Activity

Control Bytes

DISTC Macro

CSET Macro

Parity Macro

TLX Macro

TSTATUS Macro

CPU COMMON DECKS

EXAMPLES OF RANDOM I/O

CODING SPECIFICATIONS

PROGRAM EXAMPLE

JOB COMMUNICATION AREA

SPECIAL ENTRY POINTS

BINARY FORMATS

COMPASS CONTROL STATEMENT

2-11-1

2-11-2

2-11-3

2-11-4

2-11-5

2-11-7

2-11-8

2-11-9

2-11-10

2-11-11

2-11-12

2-11-13

2-11-14

2-11-17

2-12-1
2-12-1
2-12-1
2-12-1

2-12-2
2-12-2
2-12-2
2-12-3
2-12-4
2-12-5
2-12-8
2-12-8
2-12-9
2-12-9

2-A-l

2-B-l

2-C-l

2-D-l

2-E-l

2-F-l

2-G-l

2-H-l

60407000 D

FIGURES

2-3-1

2-3-2

2-3-3

2-3-4

2-3-5

2-3-6

2-11-1

2-B-l

2-B-2

2-B-3

2-B-4

2-B-5

2-C-l
2-C-2
2-E-l
2-G-l
2-G-2
2-G-3
2-G-4
2-G-5
2-G-6
2-G-7
2-G-8
2-G-9
2-G-lO

Circvilar Buffer

Write Operation

Read Operation

Standard FET for Mass Storage File

Standard FET for Magnetic Tape File

Data Transfer Buffer Arrangement

Absolute Loader Request Assignment

COMPASS Program to Create a Random File

Input File for Program Creating a Random File

Structure of the Random File Created

COMPASS Program Using READLS Macro to

Retrieve a List of Records from a Random File

COMPASS Program to Replace Certain Records

on a Random File

External Documentation of COPYB

Internal Documentation of COPYB

Job Communication Area

Modify Library File Format

Modification Table Format

Modify Text Format

Common Deck Modification Table Format

Library File Directory Table

Chippewa Record Format

User Library (ULIB) Format

ULIB Record Format

ULIB Deck Entry /Externals Format

Text Record Format

2-3-2

2-3-3

2-3-4

2-3-5

2-3-56

2-11-18

2-B-2

2-B-5

2-B-6

2-B-7

2-B-9

2-C-2

2-C-5

2-E-l

2-G-3

2-G-4

2-G-6

2-G-7

2-G-8

2-G-9

2-G-lO

XIV

60407000 D

SYSTEM DESCRIPTION

The CDC CYBER 70/Models 72, 73, and 74 Computer System and 6000 Series
Computer Systems consist of four logicsii hardware components. They are:

• Central processor unit

• Central memory

• Peripheral processor units

• Associated peripheral equipment

These hardware elements are controlled and coordinated by two basic levels of soft-
ware, the system software and user programs. This section describes briefly these
hardware and software elements and their relationship within the KRONOS Time-Sharing
system.

CENTRAL PROCESSOR UNIT

The central processor unit (CPU) performs computational tasks but has no I/O capa-
bility. It communicates with the external world through central memory. Under
KRONOS, the CPU is used to assemble, compile, and execute user programs and to
perform several system functions and utilities.

The CDC CYBER 70 Series and 6000 Series Computer Systems provide two types of
central processors. However, the programmer need be concerned only with the dis-
tinction between the two types when writing COMPASS progi-ams. Certain instructions,
if properly arranged, may be executed simultaneously by the CDC CYBER 70/Model 74
CPU and the 6600 CPU. For more information about CDC CYBER 70 and 6000 systems,
refer to the hardware reference manuals listed in the preface.

CDC CYBER 70 Series computers are equipped with a central exchange Jump/monitor
exchange jump (CEJ/MEJ) feature. This feature enables the system to switch control
between the system monitor and a user program. CEJ/MEJ Is an option on 6000
Series computers. It should be used when available to improve job performance,

CENTRAL MEMORY

Under KRONOS, central memory (CM) is used for three basic purposes.

• To hold instructions to be executed by the CPU

• To hold data to be manipulated by the CPU

• To buffer data to and from peripheral processors

Several programs can reside in CM simultaneously in hardware-protected areas called
control points. The fact that these control points are hardware-protected means that
a program cannot reference an address outside its field length. KRONOS supports a
maximum of 27o control points. The user need be concerned only with the memory

60407000 D 1-1-1

assigned to his own control point. The system assigns the CPU to the control points re-
quiring CPU activity. Normally, the assignment of the CPU is switched rapidly between
the control points to allow all programs in memory to execute. The exact amount of time
allowed for each control point depends on system activity anjl system parameters. Thus,
a job may take more real time to complete at one time than at another. The user has
no control over this switching process.

The user program communicates with the system by placing requests in address 1
(RA+1) of the control point. RA is the reference address that specifies the beginning of
the user's control point memory area.

When a user program completes, aborts, or is rolled out, the control point is released
and made available to another program,

CENTRAL MEMORY RESIDENT

A portion of CM is reserved for system use. This area is, in effect, a control point
with special privileges. This area is called central memory resident (CMR). It con-
tains system tables and directories as well as the CPU portion of the system monitor
(CPUMTR).

Figure 1-1-1 illustrates the layout of CM and shows the relationship between CMR and the
user control points.

Control
Point

Central

Memory

Resident

n-1

Address

CMR
RA,

RA,

length

FL.

CMRk„g,h * FL, * FL^

n-1

CMR, ,, + FL + FL_ + . . , + FL
length 12 n

Figure 1-1-1. Central Memory Layout

1-1-2

60407000 D

EXTENDED CORE STORAGE

Extended core storage (ECS), a second, slower form of memory, is also available.
KRONOS treats ECS as a mass storage device; it can be used:

• For storing frequently accessed data. Refer to the description of permanent
file and equipment/ file assignment requests for further information.

• As an alternate system device for storing copies of ABS, OVL, and PP type
routines. Refer to the SYSEDIT control card for further information.

The FORTRAN and COMPASS cards for ECS data storage/retrieval are not supported
by KRONOS.

PERIPHERAL PROCESSOR UNITS

The peripheral processor units (PPUs) are small processors that provide communication
paths between the central processor and individual peripheral equipment. KRONOS
supports the 10, 14, 17, and 20 PPU configurations of CDC CYBER 70/Model 72, 73,
and 74 computers. The 7, 8, 9, 10, and 20 PPU configurations are supported for
6000 Series computers. A peripheral processor can:

• Read and write CM

• Read and write ECS indirectly via CM or directly via the distributive data
path (DDP)

• Transmit data to and receive data from peripheral devices using the data
channels

The peripheral processors also perform those system control functions that are better
handled by a PPU than by the central processor.

For further information about PPUs, refer to the appropriate system hardware reference
manual listed in the preface.

PERIPHERAL HARDWARE

The system peripheral hardware varies from installation to installation but usually in-
cludes card readers and punches, line printers, mass storage devices, and magnetic
tape units. The following equipment is supported by KRONOS.

405 Card Reader

415 Card Punch

501. 505, 512, and 580 Line Printers

6603 Disk System

6638 Disk System

863 Drum Storage

854 Disk Storage Drive

814 Disk File

82V Data File

841 Multiple Disk Drive

60407000 D

1-1-3

844 Disk Storage Subsystem

Extended Core Storage

604, 607, 657, 659, 667, and 669 Magnetic Tape Units

6671 Multiplexers for communication with 200 User Terminals and 731-12/732-12
Remote Batch Terminals

6671 or 6676 Multiplexers for communication with Interactive terminals

The user need be concerned with these devices only to the degree that they affect the
format of data being transferred in the system.

SYSTEM SOFTWARE

The system consists of the group of CPU and PPU programs that control the flow of
user programs and satisfy any special requests that these programs may make. These
special requests include such functions as resource allocation requests and input/output
requests.

USER PROGRAMS

A user program is a group of CPU instructions defined by a user to perform a certain
task or calculate a specific result. A user program may be written in a language at
any of three levels.

• Compiler languages provide the user with a language suited to his particular
needs. The program cards are translated by the appropriate compiler
(FORTRAN, COBOL, ALGOL, etc.) that generates assembler language or
machine language instructions. Programs written in compiler languages are
usually machine -Independent.

• Assembler languages provide a one-to-one relationship between Instructions and
machine operation. Mnemonics are provided for each Instruction. These
languages are normally used by advanced programmers because they are
machine-dependent. Most of the KRONOS system Is written In COMPASS, the
assembler language of the CDC CYBER 70 and 6000 Series computers.

• Hardware instructions are interpreted directly by the computer, and therefore,
require no Interpretation by a compiler or assembler. Each hardware instruc-
tion is a binary number. The programmer is rarely concerned with instruc-
tions written at this level. The exception is when program debugging requires
that the user scan memory dumps.

1_1_4 60407000 D

FILES

A file is the largest collection of information addressable by name. It begins with a
beginning-of- information (BOD, an indicator which precedes all data in the file. A file
consists of one or more logical records of information. A logical record is a group of
related words or characters, of fixed or variable length, which is independent of its
physical environment.

The end of a logical record is the end-of-record (EOR). The end of a logical file is the
end-of-file (EOF) or the end- of- information (EOI), or both. If both, the EOF precedes the
EOI. An EOI is the last physical item of information on a file. Because of this EOF/EOI
concept, a file may actually be a multifile file. For example:

(BOI)data (EOR) data (EOR)(EOF) data (EOR)(EOF)(EOI)

A typical file is illustrated by the following example.

One line of an invoice may form an item, a complete invoice may form a
record, a set of such records may form a file, and the collection of invoice
files may form a multifile file.

LOGICAL/PHYSICAL FILE STRUCTURE

The actual structure of the BOI, EOR, EOF, and EOI indicators depends on the device
on which the information is stored.

The user defines the logical format of a mass storage or magnetic tape file when he
issues control cards or language specifications to create the file. Once a file is
created, it can be transferred from one storage medium to another without affecting its
logical format.

To take advantage of the physical characteristics of the medium on which a file is to be
stored, the system converts all user-defined logical file structures into a system -defined
physical file structure. In general, for higher leyel language users, this conversion
process and the resulting physical file format are transparent. AH file- related control
cards and language specifications transfer data or position a file according to its logical
definition. COMPASS users, on the other hand, have the option of reading, writing, or
positioning a file according to its logical or physical format.

The basis of all physical file structures is the physical record unit (PRU). The size of
a PRU depends on the storage medium used.

60407000 D 1-2-1

MASS STORAGE DEVICE FILE STRUCTURE

All data stored on mass storage devices! is written in 64 CM word PRUs. A logical
record consists of one or more of these PRUs. The last PRU of a mass storage logi-
cal record must be a short (less than 64 CM words) or zero-length PRU.

A BOI for a maas storage file is the disk address for the file listed in the file name
table (FNT). An EOR is a PRU containing less than 64 words and having a link to the
next PRU in the file. An EOF for a mass storage file is a zero-length PRU (that is,
a PRU containing no data) with a special link to the next F'RU in the file. An EOI is
a zero-length PRU with no forward link. The absence of a link signifies the EOI.

MAGNETIC TAPE FILE STRUCTURE

The operating system uses standard 7~ or 9-track, 1/2-inch magnetic tape. BOI on
magnetic tape is the load point. The definition of PRUs and of the EOR, EOF, and
EOI indicators varies according to the format in which the data was recorded. Any
of the following formats can be specified: external (X), blocked (B), line image (E),
Internal (I), SCOPE internal (SI), SCOPE stranger tape (S), SCOPE long block stranger
tape (L), and foreign (F). Refer to section 10 for a description of each of these for-
mats.

PUNCH FILE STRUCTURE

Because the physical characteristics of cards define the data, cards do not have a PRU
size as previously defined. Refer to appendix F for the conversion procedures used
for the various types of punch cards. The logical format of the file is indicated as
follows:

• The first card in the deck is the BOI

• A 7/8/9 punch in column 1 represents an EOR

• A 6/7/9 punch in column 1 represents an EOF

• A 6/7/8/9 punch in column 1 represents the EOI

Thus, a deck can consist of many files which can consist of many records, as illustrated
in Figure 1-2-1.

EOR

BOI

Figure 1-2-1. Sample Card File Structure

t ECS files are allocated in the sanae manner as all mass storage files.
1-2-2

60407000 D

FILE TYPES

Active files in the system are classified by their file type. Whenever a file is active,
one or more entries are made in the file name table (FNT). The FNT entry and the
file status table (FST) entry comprise a 2 -word description of the file. These two
entries contain the name of the file, the device on which the file resides, the file type,
the current position, and the current status. All system tasks involving a file use
this 2 -word entry for control.

In each of the following descriptions, the file type and its mnemonic (such as INFT)
which the system uses internally for file classification are listed.

QUEUE FILES

Five types of files are defined as queue files. They are categorized as such because
of the kinds of information they contain and the manner in which the system processes
them. Queue files always reside on mass storage. When a queue file is ready to be
processed, the system or the user places it in a queue where it waits until the re-
quired system resource or periphei'al equipment becomes available.

INPUT FILES (INFT)

Input files are the job files of the system. They contain all user-supplied control
cards and program data. There are two ways a file can be placed in the input queue:
directly by the sytem in initiating a local or remote batch job for processing and in-
directly by a user job in submitting another job via a SUBMIT control card or an LDI
control card.

When central memory space becomes available, either because a job has completed
or because a job in the input queue has a higher priority than that of a job being
processed, the input file is scheduled for processing (in other words, the job is
assigned to a control point in central memory). Refer to section 3 for a description
of the elements of jobs and the processes of job initiation and scheduling.

ROLLOUT FILES (ROFT)

At some stage in the processing of a job, the system or the user may determine that
the job must be temporarily removed from central memory. When this occurs, the
system writes all information concerning the job on a system- defined rollout file. The
rollout file includes the contents of the job's central memory field length and the job-
related system information from CMR. The file is read back into central memory
when the job is again scheduled at a control point (refer to Rollout Control in section 3).

TIMED/EVENT ROLLOUT FILES (TEFT)

A timed/event rollout file is similar to an ROFT file in that it contains all the infor-
mation concerning a job temporarily removed from central memory. A TEFT file,
however, is rolled back into central memory only when a specified event has occurred
(such as a file is no longer busy) or a specified tiime period has elapsed.

60407000 D 1-2-3

A job may be rolled out on a TEFT file as a result of system or user action. The
system uses a timed/ event file if a job issues certain requests for a file or device
that cannot be immediately honored. The COMPASS programmer can use the ROLLOUT
macro to roll out his job subject to specified time and/ or event dependencies.

PRINT FILES (PRFT)

A print file contains data the user wishes to have printed during his job or upon job
completion. The system -assigned name for print files is OUTPUT, t OUTPUT is
placed in the print queue either by the system when the job completes or by the user
via an OUT control card. The user can also include a DISPOSE control card to place
a file in the print queue.

Once a file enters the print queue, it is processed by the local or remote batch printer
processor. Then, when a printer becomes available, the PRFT file with the highest
priority is printed.

Most system utility reports are written on OUTPUT unless the user specifies an
alternate file. OUTPUT has no special internal format. Refer to appendix F for a
description of conversion methods and printer control characters and to appendix D for
a description of job output information.

PUNCH FILES (PHFT)

Punch files contain data that the user wishes to have punched on cards during his job
or upon job completion. The system- as signed names for punch files are:

PUNCH Contains Hollerith punch output

PUNCHB Contains binary punch output

P8 Contains 80-column absolute binary punch output

These files are released to the punch queue when the job completes. In addition, the
user can include an OUT or DISPOSE control card in the same manner as described
for PRFT files to place a file in the punch queue.

Refer to appendix F for a description of the format of the PUNCH, PUNCHB, and P8
files.

SPECIAL FILES

Of the five special files, the first two described (local and direct access permanent
files) are general purpose, and the remaining three (library, system, and primary
terminal) are special purpose.

LOCAL FILES (LOFT)

All scratch and working files are designated as local files,, The user can create a
local file in three ways; he can:

1. Implicitly create a local file by making the first reference to it in one of the
COPY control cards, any read or write language specification, or an OPEN

t For time-sharing jobs, the name OUTPUT h,as special meaning. Refer to section 12
volume 2, and to the Time- Sharing User's Reference Manual.

1-2-4 60407000 D

macro. Local files created In this manner always reside; on m^ass storage.

2. Create a local file by preceding any COPY cards, read or write specifications,
or OPEN macros with an explicit control card or macro file definition. The
ASSIGN control card or the REQUEST control card or macro assigns a local
file to mass storage or magnetic tape. The LABEL control card or macro
assigns a local file to magnetic tape.

3. Use a GET control card or macro to generate a local mass storage copy of an
existing indirect access permanent file. For a description of indirect access
permanent files, refer to Pei-manent Files in this section.

Unless the user includes a control card or macro to change a local file to another type
of file, it is released upon job completion.

DIRECT ACCESS PERMANENT FILES (PMFT)

A direct access permanent file is the type of permanent file that can be accessed
directly rather than through the use of a working copy. The user creates a direct
access file with the DEFINE control card or macro. Once the file is created, the
originator or anyone else to whom the originator has given permission can assign the
file to his job with an ATTACH control card or macro. The file remains in the system
until the originator removes the file with a PURGALL control card, or the originator
or any other user with the necessary permission removes the file with a PURGE control
card or macro.

For further information about direct access permanent files and their relationship to
indirect access permanent files, refer to Permanent Files in this section.

1-2-5
60407000 D

LIBRARY FILES (LIFT)

A library file is a read-only file that can be accessed by several users. A user must
be validated to access/create library files. Note that this type of file should not be
confused with system library programis or permanent file public (library) files.

A library file is created by performing the following steps.

1. Create a local file Ifn.

2. Enter the following directives as control cards or macros.

LOCK (Ifn)

COMMON(lfn)

If a user wishes to read this file and knows the file name, either the COMMON control
card or ASSIGN macro is entered. When either of these functions is performed,
an FNT entry representing this file as a library type file is created.

A library file cannot be removed from the system once it has been created except by
a deadstart. Library files are not retained on initial (level 0) deadstart. They are
retained on level 1 or 2 deadstart if a system checkpoint was done after their creation.

For a description of the relationship between LIFT files and other libraries and library
files, refer to Libraries in this section.

SYSTEM FILES (SYFT)

The system uses SYFT files for retaining special system information. SYFT files al-
ways reside on mass storage. Although the COMPASS programmer who is validated
to create system files can do so with an ESYF macro, only special system programs
can access them. Once a system file is created, no user including the originator can
remove it. System files are lost, however, at system deadstart unless the operator
recovers them.

PRIMARY TERMINAL FILES (PTFT)

The primary file is the main working file for the user. Of several files which may be
local to his job, the user may designate one file to be the primary file by using a
NEW or PRIMARY card. (A copy of an indirect access file may be retrieved and made
a primary file using the OLD card. ) This becomes the default file if a file name is
not specified. Only one primary file is available to the user at a time.

1-2-6 60407000 D

PERMANENT FILES

The user can create, retain, and access files which are available until he specifically
decides to remove them from the system. These files are called permanent files.
There are two types of permanent files.

• Direct access permanent files are accessed using normal I/O procedures,
including random read and write requests. Direct access permanent files
are allocated in large blocks;! thus, they are generally used as large data
base files. Direct access files have a write interlock. This means that if
one user has attached the file in write mode, it cannot be attached by an-
other user. Likewise, if a user wishes to attach the file in write mode, he
must wait until all current users have completed using the file. The user
should also note that because data is written directly on the file rather than
on a working file, care must be taken when modifying a direct access file.

The maximum size of a direct access file is determined either by the OS
validation parameter described in the LIMITS control card, section 6, or, if
no DS restriction is imposed, by the device limitations described in appendix
E.

• Indirect access permanent files are accessed by using a worKing copy of the
file as a local file attached to the user's job. This worRing copy is obtained
with the GET control card or macro. If the user wishes the working copy
to remain permanent after the file has been altered, the SAVE or REPLACE
functions must be issued. Indirect access files are allocated in blocks of

64 central memory words (640 characters). Because of this smaller block
size and the convenience of a worKing copy, the indirect access file is
generally the method used to create a small permanent file that does not
require a write interlocK.

The maximum size of an indirect access file is determined either by the FS
validation parameter described in LIMITS Control Card, section 6, or if no
FS restriction is imposed, by the device limitations described in appendix E.

To access permanent files, the batch user must specify a user number by entering the
USER control card. The user number is a 1- to 7 -character value which represents
a specific catalog in the permanent file system. Unless specified by an optional
(alternate) user number, all permanent file requests are made to this catalog.

User numbers that contain asterisKs represent users with automatic read-only permission
to files in catalogs of other users. The user number must match the alternate user
number in all characters not containing asterisKs. For example, the user with the user
number *AB*DE* can access the catalogs of the following users.

UABCDEF
UABDDEE
MABCDEl
MAB1DE3

■[■ Refer to Permanent File Device Statistics, appendix E,

60407000 D 1-2-7

DEVICE RESIDENCE

For most file operations, the user need not be concerned about the specific device on
which his file resides. However, under certain circumstances the user may wish to
override the system default device residence for local or permanent files.

With the ASSIGN control card, any user who has the necessary validation can assign a
local file to either a specific magnetic tape or mass storage device or to one of a type
of magnetic tape or mass storage devices.

Every permanent file the user creates resides either in his family of permanent file de-
vices or on an auxiliary device. Unless the user specifies otherwise, all permanent
files are saved in his family.

A family consists of 1' through 63 mass storage devices. Within a family each user has
a master device that contains his permanent file catalog, all indirect access files, and
some or all of his direct access files.

Normally a system has only one family of permanent file devices. However, because
families are interchangeable between KRONOS systems, several families may be active
on one system. For example, consider an installation with two systems. A and B.
System A provides bacKup service to system B. If system A failed, its family of per-
manent file devices could be introduced into system B without interrupting current op-
erations on system B.

The user identifies his family by supplying a 1- to 7-character family name. The
family name is Included on the USER card in batch jobs and is entered during login in
time -sharing jobs. If only one family is active or If another family has been introduced
into the user's normal system, he may but need not supply his family name. When the
family name is omitted, the system uses the system default family name. If the user's
family has been introduced Into another system, he must supply his family name.

If the user chooses to save his files on family devices, he has the option of either using the
system default device type or of specifying another type of permanent file device.

An auxiliary device is a supplement to the mass storage provided by family devices.
It is identified by a 1- to 7-character pack name. An auxiliary device is not necessarily
a disk pack that can be physically removed as the pack name implies. Rather, an
auxiliary device can be any mass storage device supported by the system and defined
as such by the installation. Each auxiliary device is a self-contained permanent file
device; all direct and indirect access files represented by the catalogs on the device
reside on the device. Auxiliary devices may be defined as public or private. Anyone
permitted to use auxiliary devices who supplies the appropriate pack name can create,
replace, and access files on a public device. Only one user, the owner, can create
and replace files on a private auxiliary device, but others may access those files as
permitted by the owner.

ACCESSING FILES

The two methods used to access files attached to a job are sequential and random access.
Any file can be accessed sequentially; however, only mass storage files can be accessed
randomly.

To read a file randomly, the system reads a portion of the file without reading all infor-
mation In the file, from the current position to the desired position. Any mass storage
file can be read randonaly if the user Knows which relative PRU (that is, which PRU in
relation to the BOI) he wishes to read. The desired PRU can be read by placing the PRU
number In the file's communication area (FET) and making the proper I/O requests
(refer to section 3, volume 2).

l_2-8 60407000 D

Several methods of random processing exist. The specific method depends on the lan-
guage being used; however, in all cases, the following points apply,

• Most random I/O operations require a directory or index that contains the
relative PRUs of records in the file.

• An EOR or EOF I/O operation transfers one PRU for the EOR or EOF.

• When randomly rewriting data within a file, the user must take care to ensure
that data following the area he wishes to write is not destroyed.

Figure 1-2-2 illustrates a typical example of the structure of a random access file.

BOI

System Information

Word count = 64

Word count = 30

Word count = 10

Word count =

Word count = 64

Word count = 10

Word count = 64

Word count = 10

Directory

EOR
EOR
EOF

EOR

EOF
EOI

Word count = 24

The directory can be built
in any format. This is a
typical example.

15
16

18
20

7000 0016 0-

Identifie
Table

•

„„„.„ n

Record 1 |

Record 2

Record 3

Record 4

138

record
length

random
address

Figure 1-2-2. Sample Random Access File Format

60407000 D

1-2-9

Each directory entry eontains the record name, the first PH.U of the record (random
address), and the record' length.

READING FILES

To read record 3 sequentially, the program rewinds the file to BOI and reads the file
and counts the number of EORs. System utilities and macros can be used to sKip the
records; however, the primary consideration is that the data must be read to determine
where record 3 begins. Once this is determined, record 3 can be read.

If a directory exists for this file, the only requirement is that the random address of
record 3 be obtained from the directory and placed in the FET. The proper random
read requests can then be issued. To perform this random read on record 3, the following
steps are required.

• Skip to the EOI. This is done by the system without reading the entire file.

• Backspace two logical records (one record for the EOF and one for the
directory). The system must read both records to perform this operation.

• Read the directory to obtain the random address to be placed in the FET.

NOTE

The EOF may or may not be used at the end of this
file. The language and methods used to build the di-
rectory determine whether an EOF is used.

In 3uinm.ary, to access record 3 sequentially, four PRUs must be read. To access the
record randomly, only three PRUs are read: two PRUs to position for the directory
and one PRU to read the directory.

For additional random accesses to any record in the file, it is not necessary to access
the directory again if it remains in central meniory.

The directory can be placed anywhere in the file. The only requirement is that those
users who wish to access the file randomly know where to position the file in order to
read the directory. However, the directory usually precedes the EOF /EOI.

1-2-10 60407000 D

WRITING FILES

After reading and modifying record 3 of the sample file, the user may wish to rewrite
the record in the file. If the modifications have not changed the number of PRUs re-
quired, a write operation can be used to replace the existing record with the modified
record. This write operation must be issued as a random I/O operation. (Refer to
section 3, volume 2 for a complete description of the method.) However, if the modifications
have changed the number of PRUs required, data following the record being written is lost.
For example, the size of record 3 in the sample file is 74 words or two PRUs. A
maximum of 53 words can be added to the record without requiring an additional PRU and
destroying data. If a random write request that adds 53 words to record 3 is issued,
the file has the following format.

record 3

Word count =

EOF

]30R

60407000 D

1-2-11

This operation is called a rewrite In place. If the write is issued as a nonrandom write
operation, the file has the following format.

record 3

Word count

= 64

Word count

= 63

EOR

EOI

All data following the inserted data is destroyed. If the word count for record 3 is
increased to 138, the file has the following format.

record 3

Word count =

= 64

Word count =

= 64

Word count =

= 10

EOR

PRU 7 is destroyed by the write operation. To properly rewrite record 3 without des-
troying the contents of PRU 7, the user should issue a write request at the end of the file
and alter the directory to reflect the change. Figure 1-2-3 illustrates the updated file
containing the new directory and the 138-word modified record 3 written at the end of
the file.

1-2-12

60407000 D

BOI

1
Word count = 64

2
Word count = 30

EOR

Word count = 10

EOR

4
Word count =

EOF

y////// //////// 5

// Word count = 64 ///
/////////////////

<ZWord count = 10 '^//

EOR

7
Word count = 64

8
Word count = 64

9
Word count = 10

EOR

V/yOld DirectoryOV/

Word count =

EOF

12
Word count = 64

13
Word count = 64

14
Word count = 10

EOR ~
EOR

15
Directory

EOF

EOI

7000 0016 -

Identifi
Table
• •

•
•

u
er

Record 1

Record 2

Record 3

138

Record 4

138

record

length

random
address

Note that the record 3
pointer in the directory
has been updated.

Word count = 24 >

Figure 1-2-3. Modified Sample Random Access File

Appendix B, volume 2 contains examples of COMPASS programs that create, read, and
write a random file.

60407000 D

1-2-13

LIBRARIES

The term library can be used in five ways in KRONOS,, The following paragraphs de-
fine the various types of libraries and the methods, if any, by which the user accesses
them.

• System library. The system library consists of the assembled routines that
comprise the operating system and its associated product set. System routines
may reside in central memory, mass storage, or ECS. The user accesses the
system library indirectly when a system routine is executed in response to a
control card or macro call. A complete copy of the system library is saved
on a read-only file named SYSTEM. Refer to the CATALOG control card in
section 7 for a partial list of the system library routines.

• Program library, A program library is a group of source deck images saved
on a program library file in compressed format. There are two system-de-
fined program libraries: OPL and OLDPL. OPL contains operating system
routines saved and maintained in Modify format via the MODIFY control card.
OLDPL contains product set routines saved and maintained in Update format
via the UPDATE control card. In addition, the programmer can use a
MODIFY or UPDATE control card to create and edit his own program library.

• User library. Before a user's compiled program can be executed, all external
references must be satisfied. The loader satisfies externals by searching
user libraries. A user library is a group of compiled or assembled object
time routines saved on a user library file. There are three types of user
library files: user-generated, product set, and system.

User-generated libraries are created with the LIBGEN control card and can be
specified on LIBRARY and/or LDSET control cards., Refer to the Loader
Reference Manual for further information. Product set libraries reside as
ULIB type records on the systena library. They are listed in section 11. If
some externals remain unsatisfied after searching these libraries, the loader
searches the system default user library SYSLIB, which also resides as a
ULIB record on the system library.

• Library files. Library files are read-only files. They are described in
Library Files (LIFT) in this section.

• User number LIBRARY. An installation can save under the user number
LIBRARY permanent mass storage files containing programs or text of general
interest (such as applications programs and games) to time- sharing users.
Refer to the Time-Sharing User's Reference Manual listed in the preface for
further information.

1-2-14 60407000 D

JOB FLOW AND EXECUTION

A job consists of a file of card images grouped into several records. The first logical
record contains the control cards that specify the job processing requirements. Each
job begins with a job card and ends with an EOI card. All other control cards directly
follow the job card. The end of the control cards is marked by an EOR, EOF, or an
EOI card. Figure 1-3-1 illustrates a basic job deck.

DATA

RECORD

PROGRAfl
RECORD

CONTROL

CARD
RECORD

Figure l-S-^l. Basic Job Deck

60407000 D

1-3-1

Figure 1-3-2 illustrates a COMPASS source deck that produces the object code and a
listing and executes the binary file using the input data supplied.

Figure 1-3-2, COMPASS Assemble and Execute Deck

1-3-2

60407000 D

Figure 1-3-3 illustrates a COMPASS deck that assembles the jprogram, produces binary-
punched files of each subprogram, and executes the object code of tlie first program
record.

DATA
RECORD

PROGRAM
RECORDS

CONTROL

CARD
RECORD

SUBPROGRAM

PROGRAM
RECORD

SUBPROGRAM

PROGRAM
RECORD

SUBPROGRAM

Figure 1-3-3. COMPASS Assemble, Execute, and Punch Binary Deck

60407000 D

1-3-3

Figures 1-3-4 and 1-3-5 illustrate examples of FORTRAN source decks used for
computation and user output.

DATA
RECORD

PROGRAH
RECORD

CONTROL
CARD

RECORD

DATA DECK

SOURCE DECK

Figure 1-3-4. FORTRAN Compile and Execute Deck

1-3-4

60407000 D

DATA
RECORD

KRWbrAn
RECORDS

CONTROL

CARD
RECORD

DATA DECK

BINARY DECK

SOURCE DECK

Figure 1-3-5, FORTRAN Load and Run De;ck

60407000 D

1-3-5

JOB INITIATION

When a job enters the system, the system determines the job origin type. The job
origin type identifies the means by which the job is entered into the system. It is
also used to identify the job while it remains in the system. The job origin type is
used by the system to control job activity and to aid in directing the job through the
system. It also deternaines the way the job exits from the system.

Jobs are initiated by:

• Reading a card deck in through a card reader, either from a local or a
remote batch reader.

• Using the available load utilities (refer to the LDI control card, section 6).

• Using the SUBMIT control card from a job already in the system.

The first two methods of initiation set the job origin type to indicate the method by
which the jobs are entered. When using the SUBMIT control card, a parameter is
entered with the command specifying the origin type. (Refer to the description of the
SUBMIT control card, section 6. )

JOB ORIGIN TYPES

If the job originates from the system console, the job is assigned system origin type
(SYOT). If the job is a time-sharing job and enters through the time-sharing executive,
it is given time-sharing origin type (TXOT). If the job enters the system through the
local card reader, it is a batch origin type (BCOT) job. A job coming into the sys-
tem from remote batch is entered into the system by the Export/Import package and is
assigned Export/import origin type (EIOT).

If a user is validated to do so, he can submit jobs to the system by using the SUBMIT
control card. He can also specify origin types which are different from his own.

JOB NAMES

After entering the system, the job is assigned a unique job name to prevent job name
duplication within the system. This job name is a combination of parameters that
describe the job; the first seven characters are the system- assigned job name; the
eighth character indicates the job origin type. This job name precedes all messages
issued to the system dayfile for that job. These messages include normal operating
messages, error messages, and accounting information isstied by the system.

SYSTEM ORIGIN TYPE (SYOT) JOB NAME FORMAT

The first four characters of a system job name are obtained from the job name entered
or are zero filled if fewer than four characters are entered. The nexit three characters
are a unique system sequence number in the range from AAA to 999. The eighth char-
acter is an S. For example, if the job entered is DIS, a possible job name is

DISOAABS-.

j_3_g 60407000 D

BATCH ORIGIN TYPE (BCOT) JOB NAME FORMAT

The first four characters of a batch origin job name are generated from the user index
associated with the user number supplied on the USER control card. These four char-
acters are unique to the user. The next three characters are the job sequence number.
The eighth character of a batch origin job name is B.

TIME. SHARING AND EXPORT/IMPORT (TXOT AND EIOT) JOB NAME FORMAT

The first four characters of these job names are generated from the user index associ-
ated with the user number supplied by the user when logging into the system. The next
three characters represent the number of the terminal on which the user is logged in
for TXOT or the system sequence number for EIOT. The eighth character Is T for
time-sharing origin jobs and E for remote batch jobs.

All jobs entered via the SUBMIT control card derive the first four characters of their
job names from the job's current user index in the same manner as EIOT and TXOT
jobs. The last three digits are the system sequence number with the eighth character
being either E or B, as described previously, depending on the parameter supplied with
the SUBMIT card.

VALIDATION

The USER card follows the job card and Is used to validate the user as a legal user
(refer to USER card, section 6). If the user is validated, a set of control values is
set in the control point area; these values are used by the system to control all system
requests. In most cases, if the user Is not permitted to perform specific functions
(such as access nonallocatable devices), his job is aborted and llie message

ILLEGAL USER ACCESS.

is issued when the Illegal function is attempted.

To determine the extent of his validation, the user can issue the LIMITS command and
receive a listing of his current validation control values. Refer to the LIMITS control
card In section 6 for an explanation of these values. For further information or to
change his validation, the user should contact Installation personnel,,

Each user number has a unique user Index associated with it. Once a user number is
validated, the user index is set In the control point area. The system uses this index
to determine on which permanent file device (and where) the user's permanent files re-
side. (Refer to part IV of the Installation Handbook for an explanation of tlie user In-
dex. )

ACCOUNTING

The unit of accounting for the system is the system resource unit (SRU). The SRU is
a conaposlte value of central processor time, l/O activity, and ixiemory usage. SRU
operations are initiated at the beginning of a job and reinitiated whenever another
CHARGE control card is encountered. SRU information includes:

• Central processor time

• Mass storage activity

• Magnetic tape activity

• Permanent file activity

60407000 D 1-3-7

• SRU value

• Application account charges t

This information is written to the user's dayfile at the end of the job or whenever a
CHARGE card is processed. The user may request SRU information to be written to
his output file at any time during his job by issuing the SUMMARY control card. The
format of SRU information written in the dayfile is given under Job Completion in this
section.

JOB SCHEDULING

When a job enters the system, it is placed in the input queue on mass storage, where
it waits for the required system resources to become available. The job is assigned
an input queue priority depending on its origin. The system priorities are system-de-
fined and can be altered only by the system operator. The job queue priority is
advanced as the job waits in the queue. The priority ages to a system-defined limit.
The job scheduler periodically scans the queues and active jobs to determine whether
action is necessary to ensure that the highest priority jobs are being serviced. This
action may include rolling out low priority jobs or rolling in higher priority jobs. The
job scheduler is also activated to analyze the system status whenever the status of the
system changes (for example, when the field length of a job is released, a job enters
a queue, or a job completes). Because of this automatic scheduling and analysis of
system status changes, a user can increase system performance by releasing memory
when all of the assigned memory is not required.

Once a job is brought to a control point, normal control card processing begins. The
general flow of the control card processing is illustrated in Figure 1-5-1.

JOB CONTROL

While a job is at the control point, the system exercises several controls over the job.

FIELD LENGTH CONTROL

When a job is active, the system controls the field length in either of two ways. The
action the system takes depends upon the requirements of ttie system routine called in
response to a control card request. Some system routines indicate their field length
requirements through RFL= or MFL= entry points. If the job issues a request to a
routine that does not have a predefined field length, the field length remains at or is
restored to the user-specified value. However, if the system does encounter an RFL=
or MFL= entry point, it sets the field length according to the rules governing RFL= or
MFL= processing (refer to appendix F, volume 2). The systera then restores the field
length to the user-specified value before processing the next control card, unless that
card calls a routine which also has an RFL= or MFL= entry point.

tNot currently supported by the system but reserved for future use.

1-3-8 60407000 D

The running field length for the job is set by the job card which must be validated as
previously described. The running field length can be set to any value less than the
maximum for which the user is validated by using one of the following methods.

• When the RFL control card is encountered, the running field length is adjusted
accordingly.

• If the executing program calls the control point manager (CPM) with the
MEMORY macro or a macro call to RFL, the running field length is altered.

• If the program issues the SETRFL macro, the running field length is set to
the field length specified.

Examples of field length control:

Control Card
JOB(CM50000, TIOOO)

USER(USERABC, 1234567, FAMl)

MODIFY(L=0, Z)/*EDIT. FORT

FTN(I)
LGO.

Field Length
50000
50000

36600

50000
15000

FTN(I= TAPED

REWIND(TAPE1, COMPILE)

SAVE(LGO=BIN)

RFL(30000)

50000

1100

1000

400

libe:dit(p=o, N. V)

30000

60407000 D

Comments
Sets running field length to 50000.

Running field length remains at
50000.

MODIFY increments in 2000 word
blocks to the table size required
to complete the MODIFY operation.

Running field length returns to
50000.

The loader automatlcaHy reduces
the job field length after perform-
ing a relocatable load. (RFL= Is
not present in LGO. ) The loader
requires a field length of 30200 to
load itself. It increments in 4000
word blocks until the required
table space is available.

The system restores the job to
the running field length because
no RFL== is specified in FTN.

The system sets the field length
because REWIND utility has
RFL= set. (FILES is the utility
package. )

The SAVE utility also has RFL=
set. (PFILES is the utility
package. )

The field length is set to 400 be-
cause the utility that sets running
field length (CONTROL) has
RFL==specified. This control card
changes the running field length
from 50000 to 30000.

Because LIBEDIT has no RFL=
specified, the system restores
the field length to the running
field before processing LIBEDIT.

1-3-9

INPUT FILE CONTROL

All user jobs, when initiated, have a file named INPUT. This file contains the control
cards and other input records required for job execution. INPUT is a locked file.
As a result, the user may read from it and reposition it, but the system does not
allow him to write on it. If for some special reason the user needs to write on
INPUT, he should first issue a RETURN(INPUT) control card (refer to section 7).
This card changes the name of the file from INPUT to INPUT* and leaves it attached
to the user's job. The change of name on RETURN applies only if the input file is
of type INFT.

TIME LIMIT CONTROL

The system sets a time limit for a job unless the job card specifies a time limit.
This time is the amount of central processor time that the job is allowed. The maxi-
mum time allowable on the job card is imOg seconds. Any job in the system with a
time limit of 77771g through 77777g seconds has an infinite amount of central processing
time at its disposal. If the user wants to increase a job's time limit, the SETTL con-
trol card or macro is used. The user cannot, however, increase the limit beyond that
for which he is validated.

While a job is using the central processor, the time of usage is accumulated and
checked against the time limit. If the job is not a time- sharing (TXOT) job, the job
in execution is aborted when the tlmie limit is reached. Time- sharing origin jobs are
rolled out, after which the user can reset the time limit and resume execution from
the point where the time limit was exceeded. Refer to the Time-Sharing User's
Reference Manual for a more detailed description.

ROLLOUT CONTROL

Each executing program is allowed to reside in CM for a certain amount of time before
relinquishing its space to another program. When this CM time slice is exceeded,
the progrson may be rolled out. This means that the contents of the job field length,
the job control area, and the control registers (exchange package) are written to mass
storage. The program remains on mass storage until it is rolled back into memory.
Execution resumes from the point where rollout occurred. The amount of time the job
is allowed to occupy CM is called the central memory time slice. The central memory
time slice is a system parameter that can be changed only by the system operator.
The time slices vary for each origin type. Whether a job is rolled out when its time
slice expires depends on several factors.

• Whether there are jobs waiting in the input and rollout queues

• Whether the jobs that are waiting have a lower priority

• Whether jobs that are waiting require more field length than would be available
if all jobs of lower priority were rolled out

When a job is rolled out, it is assigned a queue priority. The priority assigned is a
system paranaeter suid can be changed only by the system operator. The queue priori-
ties can vary for each origin type. The queue priority is aged (incremented) while the
job is in the rollout queue. Normally, all other factors being equal, the job with the
highest queue priority is selected to be rolled in.

1-3-10 60407000 D

ERROR CONTROL

The exit mode feature allows the programmer to select conditions that permit the sys-
tem to discontinue normal processing when errors occur. The error conditions and
assoicated condition codes that can occur are:

• Address is out of range (01) One of the following conditions has occurred.

The program^ attenapted to reference
CM memory or ECS outside the
established limits.

The program is attempting to branch
to an address outside the user's
field length.

• Operand is out of range (02) Floating-point arithmetic unit received an

infinite operand.

• Indefinite operand (04) Floating-point arithmetic unit attempted to

use an indefinite operand.

The user can select any combination of these conditions with the MODE control card
(refer to section 5). If one of these errors occurs and the proper mode for that
error is selected, the system notes the error by setting the appropriate error flag
and exiting from normal processing. The following dayfile error message occurs
defining the error exit conditions:

CPU ERROR EXIT xx AT yyyyyy.

This message identifies the error condition by the condition code xx (as listed above)
that was detected at location yyyyyy. Regardless of exit mode selection, the program
interrupt is unconditional If the error is an illegal instruction or address range error
on RNI or branch. If the exit mode is not selected, the central processor stops or
proceeds depending on the situation. For a detailed explanation, refer to the 6000
Series Computer Systems Reference Manual or the CDC CYBER 70/Model 72, 73, or
74 Computer System Reference Manuals.

When activity at a control point ceases, the system determines the reason. If an
error flag is set, the error is noted and execution is resumed at the error exit
address if one was specified.

Once control is transferred, the error flag is cleared. If the error occurs because
the central processor time limit is exceeded, the job is given another lOo seconds to
complete processing. If the error is caused by a central processor abort the address
at which the error occurred is specified and normal error processing continues.

When control is transferred from an executing program because of am error, the sys-
tem determines whether or not to continue with control card processing, perform error
processing, or terminate the job.

The system first searches for an EXIT control card. If an EXIT card is found, error
processing begins with the card following EXIT. K, prior to the detection of the error,
the system encountered a NOEXIT card, no search is made for an EXIT card and pro-
cessing continues with the next control card. If no EXIT or NOEXIT card was en-
countered, the system terminates the job,

60407000 D 1-3-11

JOB COMPLETION

When there is no more activity at a control point, no outstanding central processor re-
quests, and no control cards to process, the job is completed in the following manner.

1. All CM assigned to the job is returned to the system.

2. All equipment assigned to the job is returned to the system.

3. All library files attached to the job are returned; other jobs can then access
them.

4. All scratch (local) file space used by the job is released,,

5. All direct access permanent files attached to the job are returned; the status
Information for these files is updated.

6. The following information is issued to the user's dayfile and the account
dayfile (the associated account dayfile message formats follow each item).

Application charge activity in units

yy. mm. dd. hh. mm. ss. jobname. UEAD, xxxxxx. xxx UNTS.

Accumulated central processor time in seconds

yy. mm, dd, hh, mm. ss. jobname. UEC P, xxxxxx. xxx SECS.

Mass storage activity in kilo-units

yy. mm. dd. hh. mm. ss. jobname. UEMS, xxxxxx. xxx KUNS.

Magnetic tape activity in kilo-units

yy. mm. dd. hh. mm. ss. jobname. UEMT, xxxxxx. xxx KUNS.

Permanent file activity in kilo -units

yy. mm, dd. hh. mm. ss. jobname. UEPF, xxxxxx. xxx KUNS.

SRU value in units for total job usage including CPU time, I/O activity,
and memory usage

yy. mm. dd, hh, mm. ss, jobname. AESR, xxxxxx. xxx UNTS.

Cards read in kilo -cards

yy. mm. dd. hh. mm. ss. jobnanae. UCCR, es, xxxxxx. xxx KCDS.

Lines printed in kilo-lines

yy. mm. dd. hh, mm. ss. jobname. UCLP, es, xxxxxx. xxx KLNS.

Cards punched in kilo -cards

yy. mm. dd. hh. mm. ss. jobname. UCPC, es, xxxxxx. xxx KCDS.

7. Control point dayfile is copied to the end of the print file.

8. All output files are released to the output queue.

9. The control point area is cleared for the next job.

1-3-12

60407000 D

CONTROL LANGUAGE

The operating system control language allows the programmer to transfer control and
to perform arithmetic and test functions within the control card record. Control
language consists of statements very similar to FORTRAN statements. These state-
ments are normally composed of a command (as listed below), parameters, S3mibolic
names, and expressions. The following are legal commands.

GOTO

SET

CALL

DISPLAY

FILE

NUM

An important feature of control language is the capability to create procedure files. A
procedure file is a group of system control cards and /or control statements which can be
called much like a subroutine for insertion anywhere within the control card record. It
is activated either by the CALL statement or the name of the procedure file. Because
control cards or control language or both are allowed in a procedure file, the user is
given a much wider range of control for manipulating his files.

The following sections describe the various components and commands of the system control

language.

60407000 D 1-4-1

EXPRESSIONS

The expressions allowed are similar to FORTRAN expressions and may contain con-
stants, arithmetic operators, relational operators. Boolean operators, and functions.

CONSTANTS

Numeric constants are assumed to be decimal. If a constant has a post radix of D, it is
decimal. If it has a post radix of B, it is octal.

ARITHMETIC OPERATORS

Arithmetic operations are performed in one's complement with 48-bit evaluations. The
arithmetic operators processed are:

Addition

Subtraction

Multiplication

Division

**. ♦

Exponentiation

Leading -

Negation

Leading +

Ignored

RELATIONAL OPERATORS

Relational operations produce the value 1 if the relation is true and a value of if the
relation is false. The relational operators are (either form may be used):

. EQ. Equal to

^ . NE. Not equal to

< . LT. Less than

> . GT. Greater than

< . LE. Less than or equal to

> . GE. Greater than or equal to

1-4-2 60407000 D

BOOLEAN OPERATORS

The Boolean operators are (either form may be used):
— . EQV. Equivalence
V . OR. Inclusive OR
A .AND. AND
I . EOR. Exclusive OR
' . NOT. Complement

EVALUATION OF EXPRESSIONS

The order of evaluation of expressions is:

1. Exponentiation

2. Miltiplication. division

3. Addition, subtraction, negation

4. Relations

5. Complement

6. AND

7. Inclusive OR

8. Exclusive OR, equivalence

Nesting of expressions to any depth is allowed within a statement.

SYMBOLIC NAMES

The symbolic names used to reference values pertaining to the job process consist of those
with arithmetic values:

ARE Arithmetic error

BCO Local batch origin

CPE CPU abort

EF Previous error flag

EIO Remote batch (Export/Import) origin

EM Current exit mode

FL Job field length

FLE File limit error ■

MNE Monitor call error '

60407000 D 1_4.3

ODE Operator drop

OT Job origin type

PPE PPU abort

PSE Program stop error

Rl Contents of control register 1

R2 Contents of control register 2

R3 Contents of control register 3

I SS Job subsystem

SYO System origin

TKE Track limit error

TLE Time limit error

TXO Time -sharing origin

those with Boolean values:

SWn Setting (l=C)n, 0=Off) of sense switch n (1 < n < 6)

TRUE True value

T True value

FALSE False value

F False vadue

and those using the subsystem (ss) name. The associated name must be one of the
following:

NULL

BASIC

FTNTS

EXECUTE

BATCH

ACCESS!

TRANACTt

CONTROL LANGUAGE STATEMENTS

Statements are described in the following paragraphs. Separators and terminators must
be used as shown in the statement formats.

GOTO STATEMENT

The GOTO statement transfers control to another location within the control card file.

The statement format is:

GOTO. stmt.

stmt Name of any control card or a digit (0 through 9) followed by

a maximum of six alphanumeric characters, terminated by a
period.

tSpecial validation is necessary to access and use ACCESS and TRANACT. Refer to
the LIMITS card, section 6.

1-4-4 60407000 D

Example 1 Example 2

GOTO, 1WX2. REQUEST(TAPEl)

GOTO. REQUEST.
1WX:2, REQUEST (TAPE 1)

REQUEST(TAPE2)

When stmt appears more than once in the control statement file, the stmt to be executed is
the first occurrence of stmt from the beginning of the control statement file. Hence, in
both of the previous examples, the REQUEST (TAPED card is processed after the GOTO
statement.

CALL STATEMENT

The CALL statement allows the user to insert a file consisting of a group of control cards
(procedure file) at the specified position in the control card stream. This file is merged,
as specified on the CALL card, with the current control card record into a third record.
This third record becomes the current control card record. The remainder of the input
file is then copied to the new control card record. If the C option is exercised, the current
control card record is not used. Only the source file is used to generate a new control card
record. All options are order- independent.

The statement format is:

CALL(lfn,C,S=ccc,RENAME(oldnam- =newnam^ , oldnam„=newnam„, . . , ,
oldnam =newnam ) i i ^ <i

n n

CALLdfn, C, S=ccc(oldnam^ =newnam- , oldnam»=newnam„, .... oldnam =newnam )

Ifn Procedure file name (refer to the description of procedure files

in this section for further information). The system obtains Ifn
by:

1. Searching for a local file, Ifn

2. Searching the system librarjr for Ifn

3. Attempting to retrieve a working copy of an indirect
access file

C Clears current statement file before entering statements from

the called file. This replaces the entire control card record
with Ifn.

60407000 D 1-4-5

S=ccc Sets next control statement to be processed to statement ccc.

If S is not specified, the first statement in Ifn is processed.

RENAME Each occurrence of oldnam. iss replaced with newnam. before

the statement is entered inlfe the statement file. As ^hown by
the optional format, the word RENAME does not have to appear.

oldnam. Old name; name of a file or statement label used in the

^ specified procedure file

newnam. New name; name to replace oldnami.

1 1

DISPLAY STATEMENT

I The DISPLAY statement determines the current subsystem or evaluates an expression
and displays the result in the dayfile. Numeric results are displayed in both octal and
decimal formats. Expression evaluation is significant only to 23 bits. Therefore, the
octal representation of a negative number may be incorrect.

The statenaent format is:
DISPLAY(SS)

or
DISPLAY(expression)

expression Any legal expression

Example ;

DISPLAY(SS)

If the BASIC subsystem is currently in use, the preceding statement inserts the following
message into the dayfile.

BASIC
Example :

DISPLAY((R1+R3) * R2)

If Rl=5, R2=8, and R3=3, this statement inserts the following data in the dayfile.
64 lOOB

(Both decimal and octal values are dlspdayed, )

SET STATEMENT

The SET statement allows the user to specify a subsystem or to set software registers
to control the flow of a job. These registers are useful when designing a multipurpose
procedure file. They also can be used to select a particular option in the procedure
file. These software -defined registers are kept in the job control area and are pre-
served for the duration of the job. The control register specified in tlie control state-
ment is set to the value of the expression supplied. This register can be Rl, R2, R3,
or EF (refer to the description of symbolic names). The R registers are 18 -bit
quantities whereas the error flag (EF) is a 6 -bit quantity. Excess bits are Ignored.

1_4_6 60407000 A

The statement format is:
SET(Rl=expresslon)

or
SET(EF= expression)

or
SET(SS=ssname)
Ri
EF

expression
ssname

Software -defined register 1, 2,

An additional register

Any legal expression

Any legal subsystem name

or 3

Example:

This example illustrates the use of the SET statement to control execution of an object
program. Because register Rl Is set to 1 when file ABC is called, the object program
is not executed.

SET(R1 = 1)

CALL (ABC)

FTN.

IF(Rl=l)GOTO, 3.

REQUEST(TAPEI)

LGO.

3, REWIND(TAPEI)

IF STATEMENT

The IF statement is used to evaluate an expression. If the conditions given in the ex-
pression are true, the dependent statement is processed. The expression is considered
true if it Is evaluated to a nonzero numeric value.

The statement format is:
IF(expression)stmt.

or
IF(SS op ssname)stmt.

or
IF(SS op ssname expression) stmt.

expression Any legal expression

stmt Any legal control language statement

op One of the operators:

ssname

.EQ.

.NE.
Any legal subsystem name

60407000 D

1-4-7

Example :

IF(R2 = R1. AND. R3)GOTO, REQUEST.
SET(EF=1)

REQUEST{TAPE)

If the expression is true, the REQUEST control card is executed; otherwise, the SET
statement is executed.

Example ;

IF(SS. EQ. BASIC. AND. Rl = l)GOTO, 100.
SET(SS.EQ. BASIC)

100, OLD, BAS.

If the statement is true, the OLD control card is processed; otherwise, the SET state-
ment is processed.

FILE STATEMENT

The FILE statement is used to determine the status of any file assigned to the job and
is used in conjunction with the SET, IF, and DISPLAY statements.

The statement format is:

FILE (Ifn, expression)

Ifn File name

expression Any legal expression. FILE expressions, however, use

different symbolic names.

Symbolic names:

Names with values

EQ Equipment status table (EST) ordinal^

(0 through 77g)

ID File ID (0 through 67g)

Nam.es with true /false values

MS File is on m.ass storage

LK File is locked

OP File is opened

EX Execute- only file

AS File is assigned to user's control point

tContact installation personnel for a list of EST ordinals.

1-4-8

60407000 D

File Types

LO Local

PR Print

IN Input

PH Punch

LI Library

PM Direct access permanent file

PT Prinaary

Device Types

CP 415 Card Punch

CR 405 Card Reader

DA 6603 Disk System

DB 6638 Disk System

DC 863 Drum Storage

DD 853/854 Disk Storage Drive

DE Extended Gore Storage

DF 814 Disk File

DH 821 Data File

DI 844 Disk Storage Subsystem

DP Distributive Data Path to ECS

DS 6612 Console Display

LP 501, 505, 512, or 580-12 Line Printer

LQ 512 Line Printer

LR 580-12 Line Printer

MD 841 Multiple Disk Drive

MS Mass Storage

MT Magnetic Tape Drive (7- track)

NE Null equipment

NT Magnetic Tape Drive (9- track)

ST Remote Batch Multiplexer (6671)

TT Time-Sharing Multiplexer (6676 or 6671)

60407000 D 1-4-9

Examples:

SET(R1=FILE(TAPE, MT))

If TAPE is a magnetic tape file, Rl is set to 1; otherwise, it is given a value of zero.
I IF(FILE(TAPE, MT. OR. LI) )GOTO, lABC.

I If TAPE is a magnetic tape file or a library file, the statement at lABC is processed.

NUM STATEMENT

The NUM statement is used to determine if the specified parameter name has a num-
eric value. It is used in conjunction with the SET. IF, and DISPLAY statements.

The statement format is:

NUM(name)

name Pairameter name. If the name is numeric, the statement is true;

otherwise, it is false.

Example:

If the following CALL statement were used to call procedure file A:

CALL(A,RENAME(2XY=2,T=TAPE)
the IF statement in A :

IF(NUM(2XY))GOTO. IS.
would be evaluated as true, and control would transfer to IS.

However, the statement:

IF(NUM(T))GOTO, IS.
would be evaluated as false, and control would pass to the next statement in A,

^"■^'^^ 60407000 D

PROCEDURE FILES

Procedure files are source files consisting of control statements or system control
cards, or both. The first statement of a procedure file may be the file name. If the
first statement is the same as the file name used in the CALL statement, the first
statement is ignored. Procedure files are activated by the CALL statement or by using
the name of the procedure file, if the file is in the system.

Example 1;

This procedure file edits the decks MTR and LINK and builds a new deadstart tape
containing the edited routines. The procedure file determines whether the system OPL
is on mass storage and then modifies and assembles the specified decks.

Input Deck

JOB(T7777. PI 7, CM60000)

USER(USERNUM,PASSWRD.FAM1) I

REQUEST(TAPE) '

CALL(MOD(T=TAPE,OUT=OUTPUT,BIN=LGO,lNEXT=UNLOAD)

UNLOAD(TAPE)

COMMON(SYSTEM)

LIBEDIT(p=SYSTEM. N)

COMMON(NEW)

-EOR-

*EDIT, LINK, MTR

-EOI-

Pfocedure File on File MOD

MOD

IF(FILE{T, MT))GOTO, 2.

1, MODIFY, L=0.

COMPASSd, L=OUT, B=BIN)

GOTO, INEXT.

2,REWIND(T)

COPYBF(T,OPL)

GOTO, 1.

After the CALL control card is processed, the input file is:

JOB(T7777, PI 7. CM60000)

USER(USERNUM,PASSWRD,FAM1) I

REQUEST (TAPE) *

CALL(MOD(T=TAPE,OUT=OUTPUT,BIN=LGO, lNEXT=UNLOAD)

IF(FILE(TAPE. MT) KJOTO, 2.

1, MODIFY, L=0.

COMPASSd, L=OUTPUT, B=LGO)

GOTO, UNLOAD.

2.REWIND(TAPE)

COPYBF(TAPE,OPL)

GOTO, 1.

UNLOAD (TAPE)

COMMON(SYSTEM)

LIBEDIT(P=SYSTEM. N)

COMMON(NEW)

-EOR-

*EDIT, LINK. MTR
-EOI-

60407000 D 1-4-11

Example 2;

This is an example of nested calls. It illustrates the use of one procedure file to
skip a specified number of files on a tape (contents of Rl) and to copy ssource data to
the tape. The other procedure file retrieves source data from the OPL (old program
library) and calls the first procedure file to place that source data on the tape.

Input Deck

jobaaa
i user(us*ernum, passwrd, faml )

request(tape)
modify(s. z)/ *edit, link

SET(R1=0)

CALL(PROC,RENAME(A=TAPE, B=SOURCE. 2 = 2A, 3=3A)

SET(R1=R1+1)

CALL(PROB)

-EOR-

Procedure File PROB

PROB

MODIFY(S=NEW. Z)/ *EDIT, MTR
CALL(PROC,RENAME(A=TAPE, B=NEW)
RETURN. NEW.

Procedtire File PROC

PROC

REWIND(A. B)

SET(R2=0)

2.IF(R1=R2)G0T0.3.

SKIPF(A)

SET(R2=R2+1)

GOTO, 2.

3, COPYBF, B. A.

WARNING

On job initiation the user's input file is a locked file.
If the user wishes to call procedure files that write
data on the input file, he should enter the RETURN
(INPUT) control card before attempting to write on
INPUT. For further information, refer to the descrip-
tion of Input File Control in section 3.

1-4-12 60407000 D

TIME-SHARING COMMANDS

The following commands are Intended for use only by time -sharing origin jobs but in-
cluded here for their use in procedure files. For additional information about these
commands, refer to the Time-Sharing User's Reference Manual.

ASCII STATEMENT

The ASCII control statement specifies that all subsequent operations are to be done
using the ASCII character set.

The control statement format is:
ASCII.

If this control statement is processed while output is still available, the terminal
switches to ASCII mode for the remainder of the output.

CSET STATEMENT

The CSET control statement speciiles the current character set mode of the terminal.

The control statement format is:

CSET(m)

m Current terminal character set mode; m may be one of the following:

ASCII Set ASCII character set mode; escape code processing

is enabled

NORMAL Set NORMAL character set mode; escape code pro-
cessing is disabled

If this control statement is processed while output is still available, the terminal
switches to the new character set mode for the remainder of the output.

PARITY STATEMENT

The PARITY control statement sets the terminal to the indicated parity.

The control statement format is:
PARITY(p)

p Terminal parity; p may be one of the following:

ODD Set odd parity

EVEN Set even parity

If p is omitted, odd parity is assumed.

If this control statement is processed while output is still available, the terminal
parity switches to the new parity for the remainder of the output.

60407000 D 1-4-13

CONTROL CARD PROCESSING

Jobs entering the system consist of one or more logical records. The first logical record
contains system directives (control cards) which describe the processing that is to occur in
the job file (job deck). This section describes control card processing and how the control
cards affect other aspects of job processing.

The KRONOS Operating System recognizes three types of control cards,

• Local File Control Cards These cards call files that are assigned to the

job control point. LGO is the system default
local file used for retaining object code gener-
ated by one of the language processors des-
cribed in section H,

• System Control Cards These cards are divided into eight categories.

Job control control cards

File management control cards

Load and dump central memory utility control
cards

Loader control control cards t

Permanent file control cards

Tape management control cards

Program library utility control cards

System utility control cards

• Product Set Control Cards The product set control cards call the various

products available under KRONOS (refer to
section 11).

CONTROL CARD FORMAT

All control cards may consist of from one to four fields. The first field is the statement
label field. If present (the field is optional), it begins with a numeric character and termin-
ates with a separator character. The field is used only in conjunction with the system
control language described in section 4.

The second field, also optional, is a $ or / prefix character which precedes the program
name. If a $ is present, it indicates that the specified program to be executed must be
loaded from the system library, f Therefore, even if a lociil file of the same name is
present, it will not be executed, rrhe / option may be used on local file control card
calls. If a / is present, it indicates that the parameters following the program name
are to be processed in the operating system format. If a / is not present, the param- I
eters will be processed in product set format. The default is product set format be- |
cause it is assumed that most programs specified In local file calls have been generated
by one of the product set members,, The / option does not apply for control card calls
to programs residing on the systerei library. F'or those types of calls, parameters are _
processed in the operating system format unless the SC directive to SYSEDIT has been |
entered. Refer to the SYSEDIT control card for a description of the SC directive.

t Refer to section 15 and the Loader Reference Manual.

60407000 D 1-5-1

The third field contains the name of the program to be executed. The fourth field (optional)
contains parameters which further define the operation to be performed. The parameter
field is set off from the name field by a separator character. After the fourth field, or the
third field if no parameters are present, there miust be a valid terminator character.

The following is a comparison of the operating system and product set formats.

Operating System Format
1. Valid separators are

2. Valid terminators are

3. Letters, numbers, and the
* are the only characters
allowed in the parameter
field. The one exception to
this rule is the use of lit-
erals (that is, character
strings delimited by dollar
signs). Characters other
than letters, numbers, and
the * can be included in lit-
erals. No characters within
a literal have special mean-
ings; the system merely checks
the syntax of the literal.

The called program must do its
own processing of the literal.

Literals are allowed only on
equipment /file assignment
control cards and loader con-
trol control cards.

4. All embedded blanks within a
control statement except those
appearing in literals are
ignored.

5. Comments may appear on

the control card but they must
follow the terminator. Com-
ments may contain any char-
acter.

Product Set Format

1. Valid separators are

+ ■•"/=.(

and any other character with a display
code value greater than 44 „ except
* ) $ . and blank.

2. Valid terminators are

3. Any parameter field that includes
characters other than letters, num-
bers, and the * must be expressed
as a literal.

4. All embedded blanks within a control
statement except those appearing in
literals or after the program name ,
are ignored. A blank following the
program name is considered a valid
separator.

5. Same as for the operating system
format.

1-5-2

60407000 D

Operating System Format Product Set Format

6. Parameters, separators, 6. Parameters are stored in their display

and terminators are stored code equivalent beginning at RA+2.

in the user's field length Separators and terminators are stored

beginning at RA+2. The as follows:

characters , . and ) are stored
as zero. For all parameters
and all valid separators except
the comma, their display code
equivalent is stored.

Character

Code (0(

;tal)

(

Blank

•

) or .

Other valid

separators

7. File names are 1 to 7 alpha- 7. File names are 1 to 7 alphanumeric
numeric characters. characters. File names beginning

with a numeric character are illegal.

8. Not SCOPE compatible 8. SCOPE compatible

In general, no parameter can contain more than seven characters. If a parameter
contains more than seven characters, the entire control card is issued to the dayfile,
followed by the message:

FORMAT ERROR ON CONTROL CARD.

There are two exceptions to this rule. If a card calls a program from the system
library that has an ARG= entry point, parameters in the card can contain more than
seven characters. If a parameter contains more than seven characters, the ARG =
entry point is not present, and the SDM= entry point is present, the statement name
(such as DEFINE) is issued to the dayfile but all parameters are suppressed.

The parameters can appear in either order-dependent or order- independent format. Order-
dependent parameters are required when the parameters must be passed in a specific order.
An example of order-dependent parameters is

RESEQ(MYFILE, B. , 20)

In this example, the system expects the resequencing increment to be passed as the
fourth parameter; therefore, a separator must be present for the parameter not speci-
fied.

Order- independent parameters may be passed in any order. This is made possible by the
use of kesrwords. Keywords are identifiers which have meaning either by themselves or
when used in conjunction with other parameters. Usually, keywords are passed with a
parameter and a separator. The separator must not be a comma. When the list of param-
eters is passed to the called program, all separators except commas are also passed.

60407000 D 1-5-3

Some programs require specific separators (usually =), and others merely require that a
separator be present. Examples of keyword notation are:

1. COBOL(I=SFILE.B=BFILE)

2. COBOL(B-BFILE.I=SFILE)

3. COBOL{L=0.A,F)

4. JOBX.T10.CM45000.

In examples 1 and 2, both parameters and separators are passed to the COBOL com-
piler. Since these parameters are order-independent, both cards produce the same
result.

In example 3, two keywords are passed with no separator character or parameter.
example 4, the keyword is the first character of the parameter.

The control statements are processed in the following manner: parameters are extracted
from the control card and stored in the user's field length beginning at AIIGR (RA+2) through
RA+n (n cannot exceed 63g). t The total number of parameters stored in the user's field
length is placed in the lower 18 bits of RA+64jj. The name of the control statement is placed
in bits 18 through 59 of RA+64g.

'8*

The control card image, less any label or prefix field, is stored at RA+70„. If the program
being executed was loaded from the system library and has an ARG= entry point, then the
entire control card image will be present at RA+70g. Neither the information on arguments
nor the argument count, however, will be entered when ARG= is present. This entry point
allows for control cards with special parameter requirements (refer to appendix F, volume 2).

An example of how the control card

PERMIT(FILEABC/USERAAA=R,USERBBB=W)
appears in CM is illustrated.

Menaory

Display Code

Equivalent

ARGR

RA+E

RA + b

Obll IMDS OlOE D3DD
2S23 OSES DlDl

V I *" — ~\

DDSD FILEABC /
USERAAA

DIDD DDSM

EEOD DDDO ODOD OODO ODOD R

ESS3 DSEE OBOE DEOO ODSM USERBBB

DDDD DDDD U

E7D0 DQDD DDDO

ACTR
CCDR

RA+b^
RA+70

RA + 73

EDDS 2E1S 11B^ SbDb lllM PERMIT (FIL

OSDl aED3 SDE6 E3D5 EEOl EABC/USERA

DlDl 5MEE 5bES E30S EEDE AA=R-iUSERB

DEOH 5ME7 57SS DDDO DDDO BB=y)

The following control cards would provide exactly the same image in CM.

123, PERMIT (FILEABC/USERAAA=R, USERBBB^W)
123, $PERM1T (FILEABC /USERAAAA=R, USERBBB=W)

JOB CARD FORMAT

The first card of the control card record is always the job card,, The job card may be in
either order- dependent or order- independent format. When the job card is in order-inde-
pendent format, the keyword and parameter are passed with no separator character. The

format for the job card is:

t The first IOI3 words of the user's field length, from RA through RA+lOOo. comprise
the job communication area. Refer to appendix E, volume 2 for a description of this area.

1-5-4

60407000 D

jobname(Tt, CMfl. Pp) cm

jobname( p, t, fl) cm

jobname Alphanumeric job name (1 to 7 characters) which must begin

with a letter. This name Identifies indi\Fidual jobs being run
under the same user number.

t Central processor time limit in octal seconds, ranging from 1

to 7777O3. The time limit must be sufficient for completion of
the job. If t is absent, the system assumes t equals IOO3 (IOO3
seconds is approximately 1 minute).

fl CM field length (storage requirement) for the job. The system

rounds the value to the next highest multiple of lOOg. The field
length cannot exceed:

360,000- on a 131K machine

163, DOOg on a 65K machine

61. OOOg on a 32K machine

If fl is absent, the system assumes fl = 50,000„.

NOTE

The following messages are issued to the user's
dayfile if validation limits are exceeded.

CM NOT VALIDATED. The number of CM

words specified on
tiie job card exceeds
that for which the
user is validated.

TL NOT VALIDATED. The time limit

specified on the job
card exceeds that
for which the user
is validated.

The user may be further restricted by limits placed on him
by the validation file or by installatipn parameters. Also,
the user should consult installation personnel for additional
restrictions based on the machine configuration and sub-
systems used.

Priority level (octal) at which the job enters the system;

1 <p < 17g.

This para]:neter is currently ignored since the system will
automatically assign priorities specified by the installation
parameters.

60407000 D 1-5-5

cm Conversion mode contained in columns 79 and 80. A 26

indicates coded cards are to be converted in 026 mode; 29
indicates cards are converted in 029 mode. This is the
initial keypunch mode of the job but mode may be changed
by a conversion change card (refer to Coded Cards, appendix
F) when reading cards or a DISPOSE card when punching
cards. If this parameter is omitted,, the system default
keypunch mode is used.

In addition to the regular separator characters, the * may aLso be used to separate
parameters on the job statement.

CONTROL CARD PROCESSING FLOW

The system translates a control statement by:

1. Reading the statement from the control point control card buffer. If necessary,
the system reads control statements from file INPUT,.

2. Deleting all spaces between the beginning of the statement and the terminator
character (a period or a right parenthesis). I In general, the system allows only
standard FORTRAN characters to appear before the terminator character, although
other characters can appear within a literal or in the comment field.

3. Comparing special control card names with the name of the control card being
processed. If the card name is CTIME, RTIME, or SlIME, the system
processes the control statement.

4. Searching the file name table for a file assigned to the job with a name identical to
the nam.e of the control statement. However, if a $ precedes the program name,
this step is skipped. If an identical name is found, the program is loaded into
memory. The arguments are extracted from the control statement and stored in
RA+2 through RA+n+1 (n is the number of parameters). The CPU is requested to
begin execution unless special loader control cards follow.

5. Searching the central library directory for a program name that matches the control
card name. If the name is found, the system proceeds as in step 4; otherwise,

the system searches further.

6. Searching the peripheral processor library directory for a program name that
matches the control card name. If found, the name is placed, with a maximum of
two arguments, as a peripheral processor request, and the system exits to the
program.

7. If the control card name is not found during any of the above searches, the control
statement is declared Ulegal and the job is aborted.

tif product set format is used, a blank following the program name is considered
a valid separator.

1-5-6 60407000 D

Figure 1-5-1 illustrates the flow of control card processing.

READ A
CONTROL CARD

FOUND? ^

YES

CONTROL CARD
PROCESSOR
SEARCHES ITS LIST
OF CONTROL CARD
NAMES FOR SPECIAL
CONTROL CARD

SEARCH CPU
LIBRARY FOR
CONTROL CARD
NAME

FOUND ?
NO

YES

PROCESS
SPECIAL
REQUEST

PROCESS FIELD
LENGTH CONTROL
(SEE SECTION 3)

LOAD PROGRAM
TO CENTRAL
MEMORY

SEARCH PP
LIBRARY FOR
NAME, IF NAME
IS LEGAL PP
PROGRAM NAME

YES

•©

YES

USE KRCINOS FORMAT
FOR PROCESSING
PARAMETERS

SEARCH FNT
FOR FILE
ASSIGNED TO
THIS JOB

STORE CONTROL
STATEMENT AND
COWROL STATEMENT
ARGUMENTS IN
USER'S CONTROL
POINT AREA

/ EXECUTE
\^ PROGRAM

)

PLACE NAME
WITH UP TO T«»0
OCTAL ATCUMENTS
AS A PP REQUEST

EXIT TO PROGRAM '
(NO FL CHANGE) i

Figure 1-5-1. Control Card Processing Flow

60407000 D

1-5-7

EXIT PROCESSING

When an error condition occurs during job processing, the system searches the control card
record for an EXIT card. If the record does not contain an EXIT card, the system termi-
nates the job. If the system finds an EXIT card, it clears the error condition and processes
the control cards that follow the EXIT card. If the error was a time limit error, the limit
is reset to the time used plus lOg seconds. This gives the user time for post-error cleanup
operations.

If a NOEXIT card is encountered, normal error processing is not performed. That is, if
the no exit flag has been set (by the NOEXIT card) prior to the error, the error flag is
cleared, no search is made for an EXIT card, and processing continues with the next control
card. An ONEXIT card can be used to return to error processing mode; it clears the no
exit flag. For further discussion of possible error conditions, refer to section 3 of this
manual.

The following sequence of control cards illustrates this exit processing.

JOBABCD(T100, CM60000)
I USER(USERNUM, PASSWRD, FAMA)

GET (INPUT, I=INPUT)
MODIFY (N, 1=1, X)
LGO.
NOEXIT.

COMMON(SYSTEM)
LIBEDIT(P=SYSTEM, N, 1=1)
ONEXIT.
REQUEST(TAPE)
COPY(NEW, TAPE, V)
UNLOAD(TAPE)
EXIT.

DMP(2000, 12500)
-EOR-

During the processing of control cards 1 through 5 and control cards 10 through 12, normal
error processing is in effect. If an error condition occurs, the control cards are searched
for an EXIT card. This is found at the thirteenth card and processing continues with the
DMP card. If no errors occur before the NOEXIT card, normal error processing is turned
off until the ONEXIT card is processed.

1-5-8 60407000 A

JOB CONTROL CONTROL CARDS

The job control control cards enable the user to alter information that controls his
job while in the system and to retrieve information concerning the status of his job.
The control cards included in this category are:

ACCOUNT MODE ROLLOUT

CHARGE NOEXIT RTIME

COMMENT NORERUN SETPR |

CTIME OFFSW SETTL

DAYFILE ONEXIT STIME

ENQUIRE ONSW SUBMIT

EXIT PASSWOR SUI

LDI RERUN SUMMARY |

LENGTH RESOURC SWITCH |

LIMITS RFL USECPU

USER I

All of these cards, with the exception of PASSWOR and SUI, can be issued by
the user regardless of his validation. A listing of validation information can be obtained
using the LIMIT card. Although the user is allowed to change; several control values
for his job (such as RFL, SETPR,, and SETTL), he can never specify more than that
for which he is validated.

The system uses the USER card and CHARGE card for checking user validation and I

system accounting information. The RESOURC card is also used by the system to '

prevent deadlocks from occurring when several tapes or packs are used concurrently.

The user is enabled to submit files as batch origin type jobs through the LDI and
SUBMIT control cards. He can specify the mode of error exit processing desired
through use of the EXIT, ONEXIT, NOEXIT, and MODE cards. He can also set
conditions for his program with sense switches (such as ONSW, OFE'SW, and SWITCH).
In the event of a system malfunction causing jobs to be recovered, he may either allow
his job to be run again with the RERUN card or prevent it from being rerun with the |
NORERUN card. Additional information is returned to the user by the CTIME, RTIME,
and DAYFILE cards. The COMMENT card allows the user to provide his own docu-
mentation.

60407000 D 1-6-1

ACCOUNT CARD ^

The ACCOUNT control card is used to determine if the user is a legal user, which
resources he is validated to use, and the extent (limits) to which he may use those
resources.

The control card format is:

ACCOUNT(usernum, passwrd, familyname)

usernum User's user number

passwrd User's password

familyname Optional parameter identifying the family tt of permanent

file devices that have been or may be transferred from the
user's normal system to a backup system.

The ACCOUNT card performs the same function as the USER card and is used in
exactly the same way. All uses and restrictions apply to both. For further informa-
tion, refer to the USER card in this section.

CHARGE CARD

The CHARGE card causes the system to record on the account dayfile all information
regarding resources used under a specified charge number/project number combination.
Its purpose is to control the accounting activity of the system for a customer or the
installation.

The control card format is:

CHARGE(chargenum, projectnum)

chargenum A 1- to 10-alphanumeric character charge number assigned

to the user

projectnum A 1- to 20-alphanumerici character project number assigned

to the user

The CHARGE card is used in conjunction with user accounting control. An installation
which implements this feature can impose limits on the SRUs or connect time a user
may accumulate or restrict his access to the system to a certain time-of-day interval.

If access option 8 is not set (refer to LIMITS control card in this section), the user
must include a CHARGE card immediately following every USER card in his job. If
option 8 is set, the user may but is not required to include a CHARGE card. A user
assigned more than one charge and/or project number may include additional CHARGE
cards in his job to record resources used under each charge number/project number
combination. Whenever a new CHARGE card is issued, the SRU inforniation for the
previous charge number/ project number is written to the account dayfile and then cleared.
However, the other accumulators (central processor time, mass storage activity, and
so on) are not cleared but continue to increment. The following message is also issued
when a new CHARGE card is entered.

yy. mm. dd. hh. mm. ss. jobname. ACCN, chargenum, projectnum.

For a complete listing of messages issued to the user's dajrfile, refer to Job Completion
in section 3.

tThe ACCOUNT control card is included for compatibility with previous systems.
The USER control card is recommended,
tt Refer to section 2 for a description of permanent file devices.

1-6-2 60407000 D

COMMENT CARD

The COMMENT card is used to enter the specified comment in the system and user's
dayfile.

The control card format is:

COMMENT, comments or
^comments

comments Any combination of characters the user wishes to display

If the

^comment
format is used, the * must appear in column 1.

CTIME CARD

The CTIME control card requests that the accumulated CPU time for the job be issued
to the user's dayfile (in seconds).

The control card format is:
CTIME.

DAYFILE CARD

The DAYFILE control card causes the system to write the user's control point day-
file to the file specified.

The control card format is :

DAYFILE (If n)

Ifn File to which the dayfile is to be written; the default file

name is OUTPUT.

60407000 D 1-6-3

ENQUIRE CARD

The ENQUIRE control card gives information about the system to the user. Three
forms of the command are allowed.

The control card formats are:

ENQUIRE(OP=P]^P2. • . P^, JN=jobname, FN=lfnj, 0=lfn2)

or
ENQUIRE(pj^P2. . . p^)

or
ENQUIRE.

p. Any of the following options:

Option Description

A Causes all OP= options to be executed.

B Returns to the user informiation about his user identi-

fication and his priorities, such as USER NUMBER,
FAMILY NAME, CPU PRIORITIES. USER INDEX
HASH,, etc.

F Status of files at the user's control point.

Example:

FILENAME LENGTH/ PRUS TYPE STATUS

BFILE3

LO.

EOR

OUTPUT

PR.

IC RE/WR

OPL

19349

PM.

EOR

J Returns the contents of the user's control registers and

error flag field.

L Returns user's loader information.

R Returns to the user the amount of resources he has

used, such as CPU time, MS activity, MT activity, etc.
These statistics are the factors that make up the SRU.

S Gives the user his SRUs. The SRU represents the

total usage of the system by the user. This unit is
derived from central processor time, I/O activity, and
memory usage.

T Returns accumulated CPU time.

U Returns the amount of resources remaining available

to the user. Included in these resources are dispose
files, mass storage, dayfile messages, and control
cards.

jobname Last three characters of the name assigned by the system to a

remote batch job that has been initiated with the SUBMIT card.
When this parameter is specified, the status of the remote batch
job is returned. It is only possible to obtain the status of jobs
submitted under the current user number.

Ifn. Local file name. When this parameter is specified, the status of

the particular file is returned in the same manner as when the F
option is specified.

1-6-4 60407000 D

lft»2 Name of alternate file to receive output. If omitted, the system

assumes OUTPUT.

The third form of the card (ENQUIRE,.) defaults to the OP=A option. All OP= options
are executed and information is printed on OUTPUT.

EXIT CARD

The EXIT control card indicates the position in the control card record where process-
ing will resume if an error is encountered, or where to terminate normal control card
processing if an error is not encountered. For additional information, refer to the
description of the NOEXIT and ONEXIT control cards later in this section and to the
description of exit processing in section 5.

LDI CARD

The control card format is:
LDKlfn, id)

Ifn Name of file containing the batch job image to be submitted;

if Ifn is omitted, LOAD is assumed.

Identification code (0-6 7g); if this parameter is omitted,
is assumed.

The LDI routine copies fUe Ifn to mass storage and submits the file to the input queue
with identifier id. The file is submitted as a batch origin type job.

LENGTH CARD

The LENGTH control card gives the user the current status of one of his local files.

The control card format is:
LENGTH(lfn)

Ifn Name of local file

The information given for the local file includes its length, type, and current status.

60407000 D j_g_5

LIMITS CARD

The LIMITS control card directs the S3''stem to list validation information on file OUT-
PUT for the user named on the latest USER card.

The control card format is:
LIMITS.

Generally, validation limits are the internal system controls associated with each user
number which govern his use of certain system resources. The listing provided des-
cribes both the resources available to the user and the extent to which they may be
used. All numeric values listed are decimal unless the post radix B appears, signi-
fying an octal value. The following information is listed.

Field Description

ABt Answerback identifier (1 to 10 alphanumeric characters) used for

terminal identification

MT Maximum number of magnetic tape units the user is allowed to have

assigned to his job concurrently

RP Maximum number of removable auxiliary devices the user is

allowed to have assigned to his job concurrently

TL Maximum amount of central processor time (cumulative CPU time

slices) in seconds allowed for the user's job. TL represents the
actual time limit divided by lOg.

CM Maximum number of central memory words that the user is allowed

to request. The value stored for CM represents the actual word
limit divided by lOOg.

NF Maximum number of files that the user is allowed to have attached

to a job concurrently

DB Maximum number of deferred batch jobs that the user can have in

the system concurrently

If the user is validated for system privileges and DEBUG mode is
set on the system display console or if the user is submitting jobs
from system origin, this parameter is ignored. The user is
allowed to submit as many jobs as desired.

FC Maximum number of permanent files the user can have in each

catalog. This limit applies to each catalog being accessed (main,
public auxiliary, or private auxiliary).

CS Maximum number of PRUs available to the user for Indirect access

files

FS Maximum number of PRUs available to the user for any one In-

direct access file

PAt Terminal parity (EVEN or ODD)

ROt Specifies the number of rubout characters required for carriage

return delay

tFor further information about this field, refer to the Time-Sharing User's Reference
Manual.

1-6-6 60407000 D

Field Description

PXt FULL or HALF duplex transmission mode

TTt Terminal type

TC Character set to be used by time-sharing terminal

IS Initial subsystem for time-sharing terminal

MS Maximum nuimber of mass storage PRUs the user is allowed to

additionally allocate via his job

DF Maximum number of MESSAGE requests the user can issue to the

system and/ or job dayfiles

CC Maximum number of batch control statements processed for a user.

(Time-sharing processed control statements are excluded. )

OF Maximum number of print and punch files the user can dispose to

output queues

CP Maximum number of cards that can be punched from a user's

disposed punch file

LP Maximum number of lines that can be printed from a user's dis-

posed print file

ECtt Maximum number of ECS memory words that the user is allowed

to request

SLtt Maximum number of SRUs the user is allowed

CN Charge number to which the user is assigned

PN Project number to which the user is assigned

DS Maximum number of PRUs available to the user for any one

direct access permanent file

AW Access word; controls the user's access within the system ac-

cording to the following options (assumed values are options 1,
3, and 4)

Option Signifies

1 User can change his password.

2 User can use the privileged time-sharing commands.! 1 1

3 User is allowed to create direct access files.

4 User is allowed to create indirect access files.

tFor further information about this field, refer to the Time-Sharing User's Reference
Manual.
t tNot currently used by the system but provided for future expansion of validation control.
1 1 tFor further information about privileged time-sharing commands, refer to the operator's
guide.

60407000 D 1-6-7

Option Signifies

5 User can have system origin (SYOT) capability from any
job origin if the system console is in DEBUG mode.

The user is allowed to assign a device by its EST
ordinal although the system need not be in DEBUG
mode to do so.

The user is allowed to call the customer engineering
FPU based diagnostics if ENGINEERING mode (ENGR)
is set at the system console,,

6 User can access/create library files.

7 User can assign nonallocatable devices. A nonallocatable
device is a magnetic tape unit, card reader, card
punch, or line printer. Refer to File Management Con-
trol Statements in section 7 for further information.

8 User is allowed to access the system without supplying
his assigned charge and project numbers.

9 User can define, save, and replace files on auxiliary
devices.

10 User can access special transaction functions.

11 Allow no terminal timeout.

The octal value listed for AW corresponds to the preceding options
where bit is option 1, bit 1 is option 2. and so on. For example,
if the access word listed were:

AW=00000000000000000215
the user would be validated for options 1, 3, 4, and 8.

The LIMITS card is equivalent to the 0:P=I option of MODVAL. If any parameters are
included on the LIMITS card, the system issues the following message to the user's
dayfile.

ERROR IN LIMITS ARGUMENTS.

MODE CARD

The control card format is:
MODE(m)

m Exit mode (0 <. m < 7)

The following values can be supplied for m.

m Error Exit Mode

Disable exit mode; no selection made

1 Address out of range because:

• Attempt was made to reference CM or ECS outside
established limits, or

• Attempt was made to reference last 60 -bit word (word 7)
in relative address FL of ECS.

1-6-8 60407000 D

m Error Exit Mode

2 Operand out of range; floating-point arithmetic unit received an
infinite operand

3 Address or operand out of range (mode 1 or 2)

4 Indefinite operand; floating-point arithmetic unit received an in-
definite operand

5 Indefinite operand or address out of range (mode 1 or 4)

6 Indefinite operand or operand out of range (mode 2 or 4)

7 Indefinite operand, operand out of range, or address out of range
(mode 1, 2, or 4). If no mode is selected, the system assumes
m=7.

The MODE card is used to define the error conditions that cause the system to exit
from normal processing. When the specified error occurs, the system sets the appro-
priate error flag and exits from normal processing to perform any error processing
required. If an error occurs for which the exit mode is not selected, the system notes
the error, skips the operation that is causing the error, and continues normal proces-
sing. Note that if exit mode 3, 5, 6, or 7 is specified, a combination of exit modes
1, 2, and 4 is actually selected. For example, if exit mode 5 is specified, an error
exit will occur for either a mode 1 or mode 4 error condition. Refer to Error Con-
trol, section 3, and to the CDC CYBER 70 and the 6000 Series Computer Systems
Reference Manuals for further information about the processing of mode errors.

NOEXIT CARD

The NOEXIT control card suppresses the transfer of control to the statement following
the next EXIT statement if an error occurs.

The control card format is:
NOEXIT.

If a NOEXIT card has appeared in the control card record and an error occurs, pro-
cessing continues with the next control card, if possible (that is, if error does not
cause job to abort). Refer to the description of exit processing in section 4 for
further information.

NORERUN CARD

The NORERUN control card allows a user to clear job rerun status.

The control card format is:
NORERUN.

If the NORERUN card has been issued, the job may not be rerun. This may be de-
sirable to prevent updating of an important data base when the job would otherwise be
rerun.

This card is ignored from a time-sharing origin job.

60407000 D 1-6-9

OFFSW CARD

The OFFSW control card clears the pseudo- sense switches for reference by the user's
program.

The control card format is:
OFFSW(Sj,S2, .. .,s„)

s. Sense switch to be cleared; l<Si<6. If Si=0 is specified,

all sense switches are cleared".

The system stores the sense switch settings in the user's control point area and copies
them to RA for use by the central program. The system operator can change these
settings by console command.

ONEXIT CARD

The ONEXIT control card causes the transfer of control to the statement following the
next EXIT statement if an error occurs.

The control card format is:
ONEXIT.

The ONEXIT card reverses the effect of a NOEXIT card. If an error occurs in pro-
cessing a card following ONEXIT, control transfers to the card following the next
EXIT card. Refer to the description of exit processing in section 4 for further infor-
mation.

ONSW CARD

The ONSW control card sets the pseudo-sense switches for reference by the user's
program.

The control card format is:
ONSW(sj, Sg... -.Sjj)

Sense switch to be set; l<_Si<_6. If Si=0 is specified, all
sense switches are set.

The system stores the sense switch settings in the control point area and copies them
to RA for use by the central program. The system operator can change these settings
by console command.

1-6-10 60407000 D

PASSWOR CARD

The PASSWOR control card is used to change the user's password.

The control card format is :

PASSWOR (oldpswd. newpswd)

oldpswd Old password

newpswd New password

The user's password is changed from oldpswd to newpswd. The user can change his
password only if access option 1 is set (refer to the LIMITS control card in this
section). If option 1 is not set and the user submits a PASSWOR card, the system
issues the following message to his dayfile.

ILLEGAL CONTROL CARD,

If the control card parameters are in error, the system issues the following message.

ERROR IN PASSWOR ARGUMENTS.

RERUN CARD

The RERUN control card allows a user to set job rerun status.

The control card format is:
RERUN.

If the RERUN card has been issued, the job may be rerun. This card is ignored from
a time-sharing origin job.

RESOURC CARD

The RESOURC control card is necessary in any job that uses more than one tape or
pack concurrently in order to prevent deadlocks with other jobs which may need the
sanae resources.

The control card format is :

RESOURC(rti=ui, rt2=U2, . . . , rtn=Un)
rt^ Resource type:

MT Magnetic Tape Unit (7-track)

NT Magnetic Tape Unit (9-track)

DDi 854 Disk Storage Drive (l<i<8)

Dli 844 Disk Storage Subsystem (l<i<8)

MDi 841 Multiple Disk Drive (l<i<8)

u. Maximum number of unita of resource type rtj^ this job

will use concurrently; any rt^- Uj[ entry can be changed on
subsequent RESOURC control cards.

60407000 D 1-6-11

The system manages the use of tape units and disk packs in such a way as to prevent
deadlocks from occurring. A deadlock would occur if the system, by assigning a tape
unit or pack to one job, prevented another job with currently assigned resources from
completing, For example, an installation with two tape units is processing jobs A
and B. Each job needs both units during some phase of processing. Job A is assigned
unit 1. If job B were assigned unit 2, neither A nor B could complete until the other
job relinquished its assigned unit.

The system prevents such situations by requiring that a RESOURC control card be
included in any job that uses more than one tape or pack concurrently. When a job
that includes a RESOURC card is submitted, the system first checks if the specified
number of units exceeds the number of units for which the user is validated t or the
number of units available at the installation. If either of these situations occurs, the
system issues an error message to the user's dayfile and aborts the job.

When the job requests a tape or pack It, the system compares the number of units that
jobs being processed have scheduled via RESOURC cards with the number of units act-
ually assigned. If it determines that the assignment would cause a deadlock, it rolls
out the job until a deadlock would not occur. If the assignment would not cause a
deadlock, the system searches for the requested tape or pack. If found, it is assigned
to the requesting job. If the pack is not found and the NA keyword was included in
the request or if the tape is not found, the requesting job is rolled out until the
operator makes the pack or tape available.

Thus, in the previous example, a RESOURC card would be required in both jobs. The
information supplied by the cards would enable the system to anticipate the deadlock
situation and roll out job B until job A no longer needed both units.

Under certain conditions the system overcommits resources, provided all jobs with
currently assigned resources can complete. For example, an installation with three
tape units is processing jobs A and B. Included in each job is a RESOURC card
scheduling two units. Job A requests its first tape. It is assigned the tape (unit 1)
because there are enough units available for job A to complete. Job B requests its
first tape. It is assigned the tape (unit 2) because either A or B can complete if
assigned the last unit, and when the job that is assigned the last unit completes, the
other can then use that unit and also complete. Job B then requests and is assigned
its second tape (unit 3). It completes its operations (that is, terminates or returns
the files on the tape) and makes the unit available for job A to complete.

The system manages resources by keeping totals of the number of scheduled units and
assigned units. Each total can vary during job processing. A user can increase the
number of scheduled units by RETURNing all files attached to his job residing on re-
source units not currently needed and then scheduling the required number of units
with another RESOURC card. He can decrease the number of scheduled units by in-
cluding RETURN cards or additional RESOURC cards.

' For jobs that use only one tape or pack at a time and do not contain a RESOURC
card the system checks validation limits when the request is made.

1t Refer to Permanent File Control Cards for a description of disk pack requests and
to Tape Management Control Cards for a description of tape requests.

1-6-12

60407000 D

In the following job, for example, the second RESOURC card increases the number of
scheduled disk drives and decreases the number of scheduled tape units.

SAMSJOB(CM50000, T40)
USER(SJGREEN, WGT, AI.TFAM)
RESOURC(NT=2)

RESOURC (DD 1 = 2, NT = 1)

-EOI-

At some time during this phase of processing,
the job will require two 9-track tape units.

During this phase, the job will require two 854
Disk Storage Drives and one 9-track tape unit.
The N = l entry decreases the number of scheduled
tape units from two to one.

If the user decreases the total to less than the num.ber of currently assigned units or
increases the total to a point where a deadlock would occur, the system issues an
error message to the user's dayfile and aborts his job.

The method of assigning units depends on the resource type. For example, all tapes
and all private disk packs not accessible by alternate users can only be assigned to
one job at a time. All public packs and those private packs accessible by alternate
users are sharable, and therefore, can be assigned to several jobs at the same time.

On indirect access file requests the pack is charged to the job in fulfilling its resource
demand only if the request causes the pack to be mounted. For direct access file re-
quests, the pack is charged to the job when the first ATTACH of a direct access file
is made.

A unit is assigned to a job until the job terminates or all direct access files residing
on the unit that are assigned to the job are RETURNed. At this point a tape or a non-
sharable pack can be dismounted. A sharable pack, however, can be dismounted only
when there are no files residing on the unit that are assigned to any of the jobs sharing
the pack.

NOTE

In GET requests for indirect access files, a pack is
assigned to a job only as long as the pack is actually
being used (that is, until the system retrieves the local
copy of the file). Therefore, during a series of GET
requests, the operator may determine that the pack is
not being used £ind dismount it. If the user has a direct
access file on the pack, he can avoid this situation by
attaching the direct access file before issuing the GET
requests.

60407000 D

1-6-13

RFL CARD

The RFL control card allows the user to change the job field length from that speci-
fied on the job card. It also sets the restoration field length for all jobs.

The control card format is:
RFL{nnnnnn)

nnnnnn Field length (octal)

The restrictions on nnnnnn are the same as those described for the job card in
section 4. If the requested field length exceeds that for which the user is validated,
the following error message is issued to the user's dayfile.

FL BEYOND USER LIMIT.

ROLLOUT CARD

The ROLLOUT control card requests that the user's job be rolled out and all memory
assigned to the job released.

The control card format is:
ROLLOUT.

The user's job is entered into the rollout queue and is rescheduled by the system.

RTIME CARD

The RTIME control card requests that the current time be read from the realtime
clock and issued to the dayfile (in seconds).

The control card format is:
RTIME.

SETCORE CARD

The SETCORE control card presets each word within the field length.

The control card format is:
SETCORE(p)

or
SETCORE(-p)

p Any of the following: (If a minus sign precedes the parameter p,

the complement of p is set in core. )

p Fill Characters

ZERO Zeros (0)

INDEF Indefinite (1777 0000 0000 0000 0000)

INF Infinite (3777 0000 0000 0000 0000)

Each word within the field length is set to p. If p is omitted, the system assumes p=0.
1-6-14 60407000 D

ROUTE CARD

"Hie ROUTS control card allows a batehvuser (caris or TELEl) to route a
job to a specific CXTTPUT and locaHon,

The control format is:

ROUTE(lfn,EJ,C=cc,L«loc,EQ=eq,AT=at,WASTB] or SA1?E)

Ifn Logical file name. No default.

EJ If present, ROUTE occurs at end-of-job. Default-
immediate .

L=loc Location to which file is to be direeted. Default*
location at which Job was submitted,

EQ=»eq Output device to i*iich file is to be directed. 3

AT»at Attribute. Default- none.

G=cc Copy count. Default=l.

WASTE or Will ensure that each oage of printout begins
SAVE on a new page. Particularly helpful for a printout
to be in continuous use.

D-cJ Cou»^ie\r Oro^ C'r-Ac .

U Hold in 6o-^fl:A <j'jf'je'^(-Sf.ra ^r^'ni ^/,or,'f-v, ) "^uWer (72.

PS" P^ro^V,A,m( r /Uv«<^'.^ ^ IVP'Jl use

P \aJ pa 3 s J-'o iro( J

1-6-11,3

SETPR CARD

The SETPR control card allows the user to specify a new CPU priority for his job.

The control card format is:
SETPR(p)

p Priority, l<p<70g; if p exceeds that for which the user

is validatedT" If is reduced to that value.

The CPU priority controls the assignment of the CPU to active jobs. If the CPU
priority is lower than that of other jobs, the job is assigned to the CPU only when
jobs of a higher priority do not need it. The user is validated for a maximum CPU
priority. He cannot request a level that exceeds this value or 7O3 (the maximum
CPU priority).

SETTL CARD

The SETTL control card allows the user to specify a new CPU time limit for his job.
The control card format is:

SETTL(t)

t Central processor time limit in octal seconds (maximum

is 77777g); t is accurate to the nearest second.

The CPU time limit is the amount of time (in seconds) that a job is allowed to use
the CPU before the error message:

TIME LIMIT EXCEEDED.

is issued by the system.

The user is validated for a maximum time limit. If this is exceeded or 0<t<_777773
is not satisfied, the following message is issued.

ILLEGAL USER ACCESS.

If t is between 777708 ^^'^ 777778. **^® time limit is infinite. The user cannot set a
time limit greater than that for which he is validated.

STIME CARD

The STIME control card requests that the accumulated SRU value for the job be issued
to the user's dayfile.

The control card format is:
STIME.

60407000 D 1-6-15

SUBMIT CARD

The control card format is:

SUBMITafn.q,NR)c
Ifn

Name of the file to be submitted to the system for pro-
cessing as a batch job

Specifies disposition of job output as follows:

B Job output is disposed to local batch queue to be

printed and/or punched at the central site (default
value for nontime- sharing origin jobs)

N Job output is disposed to local batch queue, but is

dropped at job termination (default value for time-
sharing origin jobs)

E Job output is disposed to Export/import queue for

printing at a remote batch terminal.

No rewind option; inhibits rewind of file specified by re-
formatting directive cREAD. If omitted, file specified by
cREAD directive is automiatically rewound.

Escape character used to identify reformatting directives
in the file to be submitted (Ifn). If omitted, the system
assumes c==/.

The submit file Ifn contains a batch job submitted to the system for processing. The
reformatting directives described in this section are provided to aid the user in pre-
paring the submit file. When the SUBMIT card is processed, the submit file can be
reformatted according to the directives that appear in the file.

Each line in the submit file preceded by an escape character is recognized by KRONOS
as a reformatting directive. The escape character to be used must be specified on the
SUBMIT card (/ by default). Throughout this description, the letter c, preceding a
directive, denotes the escape character. Reformatting directives may be interspersed
throughout the submit file as long as transparent mode is not in effect. Transparent
mode is selected by the cTRANS directive and requires that the user observe special
rules when inserting subsequent directives into the file (refer to description of cTRANS
and cNOTRANS directives).

The systena does not process reformatting directives unless the first line of the
submit file contains the cJOB directive. In addition, the first two card images following
the cJOB directive (second and third cards of the submit file) must be a job and USER
card, respectively. All following information is determined by the user. Thus, the first
three lines of a submit file that is to be refornmatted before processing should be:

Inl cJOB

ln2 jobname, . . .
In3 USER,...

where Inl, ln2, and ln3 are optional line numbers.

1-6-16

60407000 D

The SEQ and NOSEO directives are used to determine, during reformatting, if the submit
file will contain leading line numbers. Therefore, it is a simple matter to include line
numbers on the entire submit file and specify which line numbers are to be removed
during reformatting. This is especially useful if the submit file contains a BASIC program
where line numbers are a requirement of the language.

The reformatting directives available are described as follows:

cJOB

cEOR

cEOF

cSEQ

cNOSEQ

cPACK

cNOPACK
cTRANS

Indicates that the submit file is to be reformatted and
selects the following default reformatting directives. The
default directives remain in effect until specified otherwise.

cNOTRANS (disabled by cTRANS)

cSEQ (disabled by cNOSEQ)

cPACK (disabled by cNOPACK)

The cJOB directive must be the first line of the submit file.
If omitted, the file is not reformatted.

Indicates that an end-of-record mark is to be placed at
this point in the submit file during reformatting.

Indicates that an end-of-file mark is to be placed at this
point in the submit file during reformatting.

Indicates that the following lines are preceded by line
numbers and requests that they be removed (default value).

Reverses the effect of the cSE]Q directive. No attempt is
made to remove leading line numbers from subsequent lines.

Requests that all succeeding end-of-record and end-of-file
marks be removed (default value). This directive applies
only to internal EOR and EOF marks that currently exist.
The cEOR and cEOF reformatting directives are not affected.

Reverses the effect of the cPACK directive. Requests the
system not to discard succeeding internal end-of-record and
end-of-file marks that currently exist.

Indicates transparent mode. When the system encounters this
directive, it checks the next line of the submit file for an
additional directive. If one exists, it is ,processed and the
next line is checked. This continues until a line that is not
a reformatting directive is encountered. Transparent mode
is then selected and all directives that exist on subsequent
lines are ignored until an internal EOR or EOF is encountered
(this pertains only to EOR and EOF marks that currently
exist, not cEOR and cEOF directives). The cPACK and
cNOPACK directives determine if the internal EOR or EOF
mark will be retained. The line following the internal EOR
or EOF mark is then checked for a reformatting directive.
If one exists, it is processed and the following line is checked.
All directives are processed until a line that does not con-
tain a reformatting directive is encountered. This causes
transparent mode to be reset unless a cNOTRANS directive
was encountered. This process continues until either the end
of the submit file is reached or until a cNOTRANS directive
following an Internal EOR or EOF is encountered.

60407000 D

1-6-17

cNOTRANS

cREAD.lfn

The cTRANS directive is typically used in conjunction with
the cREAD directive. It allows the user to copy the contents
of an existing file into the submit file at the location of the
cREAD directive. Because the file is read in transparent
mode, no check for reformatting directives is attempted until
an internal EOR or EOF is encountered. Note that the cREAD
directive must follow the cTRANS directive and must be located
before the first succeeding line that is not a reformatting di-
rective. If not, transparent mode is selected before the cREAI
directive is encountered and the cREAD will be ignored.

The cSEQ or cNOSEQ directive in effect before transparent
mode was selected has no effect upon the submit file or the
file being read (cREAD) while transparent mode is in effect.
Note, however, that the cPACK or cNOPACK directive in
effect before transparent mode was selected remains in effect
after it is selected.

Reverses the effect of the cTRANS directive and informs the
system that the submit file is to be examined on a line-by-line
basis. All directives encountered in the submit file while the
cNOTRANS directive is in effect will be processed. This
directive is initially selected by default and remains in effect
until a cTRANS directive is encountered in the submit file.

The user should be careful in placing this directive in the
submit file. If transparent mode is selected, this directive
can possibly be ignored unless it immediately follows either
a cREAD directive in the submit file or an internal EOR or
EOF mark.

Requests that the system read the entire contents of the
specified file, Ifn, and insert that file in place of the cREAD
directive in the submit file, during reformatting. If the file
to be read is not currently local to the job, the system
automatically attempts a GET and then an ATTACH on the
file. If Ifn is not specified in the directive, TAPEl is
assumed. If the file specified cannot be found, the message

NO READ FILE - Ifn.

is issued to the user's dayfile, and the job is terminated.
If the read file is found to be busy (direct access files only),
the message

READ FILE BUSY - Ifn.

is issued to the user's dayfile, and the job is terminated.
The file specified by Ifn in the cREAD directive is automati-
cally rewound before the read operation unless the NR para-
meter is specified on the SUBMIT control card. In this case,
the rewind directive must precede the cREAD directive in
the submit file if it is desired to rewind file Ifn before the
read operation begins. KRONOS returns all files specified
in cREAD directives before completion of the job.

If the cPACK directive is in effect at the time of the read,
all internal EOR and EOF marks will be removed. If the
cNOPACK directive is in effect, all internal EOR and EOF
marks are read into the submiit file in the proper position
during reformatting.

1-6-18

60407000 D

Unless transparent mode Is in effect when file Ifn is read,
each line of that file will also be checked for a reformatting
directive. Any directives contained in the file, except an-
other cREAD, will be processed. The cREAD directive cannot
be nested. In addition, any directives in effect before the
cREAD directive is processed will remain in effect for the
file being read, unless transparent mode is selected. Then,
only the cPACK or cNOPACK directive remains in effect for
the file being read. Moreover, only those directives that
immediately follow an internal EOR or EOF in the file being
read will be processed.

If the file to be read is a binary file, it is recommended
that the cTRANS directive be used. This is to ensure that
binary data will not be mistaken for a refor:matting directive.
The cTRANS directive should immediately precede the cREAD
directive In the submit file, if used.

cREWIND.lfn Requests that the system rewind file Ifn to the beginning-of-

informatlon (BOD. If Ifn is not supplied, TAPEl Is assumed.
This directive is required only if the NR parameter Is in-
cluded in the SUBMIT command. Otherwise, file Ifn is auto-
matically rewound.

This directive is used in conjunction with the cREAD directive.
Thus, if it is desired to rewind a file before the read operation
begins, this directive must precede the cREAD directive in
the submit file.

CjEC=C2 Indicates that the escape code character is to be changed

from Cj (current escape code) to C2 (new escape code). The
new escape code will be used to recognize all subsequent
reformatting directives until further change.

There is no restriction on the maximum number of characters per line for transparent
mode. For all other modes, no line can exceed 150 characters.

If the user determines that an error occurred during processing of his job, he may
reference a listing of the user's dayfile as an aid in identifying the cause of the error.
The user's dayfile contains a record of the job processing activity and is disposed to
the local batch queue or the Export /Import queue for printing when the job is terminated.
However, all output is normally dropped at job termination when a batch job image is
submitted from a time-sharing terminal. This includes the dayfile output as well as the
job output. In this event, the user can make provisions within his job to save the con-
tents of the dayfile if an error In processing occurs. This is done by including the
following control cards at the end of the control card record.

Inx

EXIT.

Iny

DAYFILE(lfn)

Inz

SAVE (Ifn)

For further information about using SUBMIT from a time-sharing terminal, refer to the
Time-Sharing User's Reference Manual.

60407000 D 1-6-19

SUI CARD

The SUI control card allows a user to access a permanent file catalog without using
the USER statement.

The control card format is:
SUI(n)

n User index desired; 0<n<3777778.

The SUI card is useful if validation is not active. Only system origin jobs may issue
this control card. If the job is not of systena origin, the following message is issued.

CPM ILLEGAL REQUEST.

SUMMARY CARD

The SUMMARY control card gives information about the system to the user. Three
forms of the command are allowed.

The control card formats are:

SUMMARY(OP=PiP2. . . Pq. JN=jobname, FN=lfni, 0=lfn2)

SUMMARY(pjP2. . . p^)

SUMMARY.

p. Any of the following options:

Option Description

A Causes all OP= options to be executed.

B Returns to the user information about his user identifi-

cation and his priorities, such as USER NUMBER,
FAMILY NAME, CPU PRIORITIES, USER INDEX HASH,
etc.

F Status of files at the user's control point.

Example :

FILENAME LENGTH/ PRUS TYPE STATUS

BFILE3 81 LO. EOR

OUTPUT 7 PR. IC RE/WR

OPL 19349 PM„ EOR

J Returns the contents of the user's control registers and

error flag field.

L Returns user's loader information.

R Returns to the user the amount of resources he has used,

such as CPU time, MS activity, MT activity, etc. These
statistics are the factors that make up the SRU.

S Gives the user his SRUs. The SRU represents the total

usage of the system by the user. This unit is derived
from central processor time, I/O activity, and memory
usage.

1-6-20 60407000 D

Option Description

T Returns accumulated CPU lime.

U Returns the amount of resources remtiaining available to

the user. Included in these resources are dispose files,
mass storage, dayflle messages, and control cards.

jobname Last three characters of the name assigned by the system to a

Ifh. Local file name. When this parameter Is specified, the status of

the particular file Is returned In the same manner as when the F
option is specified.

lfn„ Name of alternate file to receive output. If omitted, the system

assumes OUTPUT.

The third form of the card (SUMMARY. ) defaults to the OP=R option. The resource
usage of the job is listed on OUTPUT.

SWITCH CARD

The SWITCH control card sets the pseudo-sense switches for reference by the user's
program.

The control format is:

SWITCH(si, Sg, . . . Sjj)

Sj Sense switch to be set; l<Si^6. If Si=0 is specified, all

sense switches are set.

The system stores the sense switch settings in the control point area and copies them
to RA for use by the central program. The systiem operator can change these settings
by console command.

This control card performs the same function as the ONSW control card.

USECPU CARD

The USECPU control card specifies which central processor is to be used when more
than one is available for processing.

The control card format is:

USECPU(n)

n = Either central processor can be used.

n = 1 CPU is to be used (CDC CYBER 74- 2X or the 6600

CPU on the 6700).

n = 2 CPU 1 is to be used (CDC CYBEFl 74- 2X or the 6400

CPU on the 6700).

The USECPU card is to be used only when the system is running on a CDC CYBER
74-2X or 6700 system.

60407000 D 1-6-21

USER CARD

The system utilizes the USER control card to determine if the programmer is a legal
user, which resources he is validated to use, and the extent (limits) to which he may
use those resources. The USER card must follow the job card if user validation is
active.

The control card format is:

USER(usernum, passwrd, familyname)

usernum User's user number

passwrd User's password

familyname Optional parameter identifying the family f of permanent file

devices that have been or may be transferred from the user's
normal system to a backup system

This card defines controls and validation limits for the job and defines the user's per-
manent file base. The user can specify a different permanent file catalog during job
processing by issuing another USER card. However, the access limits (refer to LIMITS
control card in this section) for the user named on the first USER card remain in
effect for all subsequent USER cards.

Normally, the familyname parameter need not be included on the USEB; card. However,
if the user maikes a practice of specifying his family name each time he submits a job,
he can be sure that his job will be processed even if his normal system is not available
and his permanent file family had to be moved to a backup system. If, after the first
USER card, the user doesn't specify a familyname on the USER card, Ms permanent file
family remains the same. If the user specifies the (zero) familyname, his permanent
file family becomies the system default family.

Example:

An installation has two systems, A and B. System B provides backup service for sys-
tem A. The system default family name for system A is AFAM,and the system default
family name for system B is BFAM.

During normal operations, system A user CWJONES with password JPWD could enter
either of the following USER cards.

USER(CWJONES, JPWD)

USER(CWJONES, JPWD, AFAM)

System B user JDSMITH with password SPWD could enter either of the following cards.
USER(JDSMITH, SPWD)
USER, JDSMITH, SPWD, BFAM)

If system A failed, user CWJONES would be required to enter:

USER(CW JONES, JPWD. AFAM)

to identify his family of permanent file devices. User JDSMITH could enter either of
the USER cards as before because the defavilt family name would still be valid.

t Refer to section 2 for a description of permanent file devices.

1-6-22 60407000 D

If the user attempts to access permanent files on a device not present In the alternate
system, one of the following messages is issued to the user's dayfile.

DEVICE UNAVAILABLE, AT nnn. This message is issued if the user's

master device! was not transferred to
the backup system.

DIRECT ACCESS DEVICE ERROR. This message Is issued if the user attempted

AT nnn. to reference direct access files on a de-

vice (other than his master device) not
present in the backup system, t

t Refer to section 2 for a description of permanent file devices.

60407000 D 1-6-23

F^LE MANGEMENT CONTROL CARDS

The file management control cards enable the user to manipulate files attached to his
job. Many of these control cards are processed by the systenri processor, FILES.
The control cards included in this category are:

ASSIGN

COPYEI

NEW

SKIPF

BKSP

COPYSBF

OUT

SKIPFB

CATALOG

COPYX

PACK

SKI PR

CLEAR

DISPOSE

PRIMARY

SORT

COMMON

DOCMENT

RENAME

STAGE

CONVERT

EVICT

REQUEST

TDUMP

COPY

GTR

RESEQ

UNLOAD

COPYBF

LIBEDIT

RETURN

UNLOCK

COPYBR

LIST80

REWIND

VERIFY

COPYCF

LOCK

SETID

VFYLIB

COPYCR

L072

SKIPEI

WRITEF
WRITER

The cards in this section allow the user to position his files,, copy data from one file
to another, specify method and format of input/output, sort his files, and add correc-
tions. He can assign his files to a specific device type; change the file type, identi-
fication code, and write interlock status; and release them from job attachment. The
user can also receive information about records in a file or documentation in a file
containing COMPASS source code.

If an error is encountered in an operation on one file of a multiple file request, the
operation is not performed on the following files. For example, if an error occurs in
processing file B on the following control card:

COMMON(A, B, C. D)

files C and D are not processed.

If a file is not specifically assigned through the use of an ASSIGN, LABEL, or REQUEST
control card, the system assigns the file to available mass storage. Refer to the
ASSIGN and REQUEST cards in this section and Tape Management Control Cards in
section 10 for a more detailed description.

60407000 D

1-7-1

ASSIGN CARD

The ASSIGN control card directs the system to assign a file to the specified device or
device type.

The control card format is:

ASSIGN(nn, Ifn. (^g) )

nn Device or device type to which the specified file is to be

assigned; nn may be either the EST ordinalt of a peripheral
device or the device type as defined as follows:

Type Equipment

CP 415 Card Punch

CR 405 Card Reader

DA 6603 Disk System

DB 6638 Disk System

DC 863 Drum Storage

DD 854 Disk Storage Drive

DE Extended Core Storage

DF 814 Disk File

DH 821 Data File

DI 844 Disk Storage Subsystem

DP Distributive Data Path to ECS

LP 501, 505, 512, or 580-12 Line Printer

LQ 512 Line Printer

LR 580-12 Line Printer

MD 841 Multiple Disk Drive

MS Mass Storage Device

NE Null Equipment

TT Time-Sharing Multiplexer! t

Ifn Name of the file to be assigned to the specified equipment

CK Specifies that Ifn is to be used as a checkpoint file. Each time

a checkpoint dump is taken, the new information is written at the
previous EOI of Ifn.

CB Specifies that Ifn is to be used as a checkpoint file. Each time a

checkpoint dump is taken the new information is written at the
BOX of Ifn.

Before performing the assignment, the system issues a RETURN on Ifn. Any job can
assign a file to MS and any time-sharing origin job can assign a file to TT. However,
to assign any other devices, the job raust be of system origin or the user must be
validated for system origin privileges, t t T

If the user attempts to perform an assignment for which he is not validated, the job is
aborted and the following message is issued to the user's dayfile.

ILLEGAL USER ACCESS.

t Contact installation personnel for a list of EST ordinals,
t t This device type applies only to tune-sharing origin jobs,
tit Refer to LIMITS control card, section 6.

1-7-2 60407000 D

In addition, to assign a file to any nonmass storage device except device type TT, the
user must be validated to use nonallocatable devices. If the user does not have this
validation or the device is not available, the system aborts the job.

The user should not normally assign any nonallocatable devices to his job. While it is
possible to assign a central site card reader, line printer, or card punch directly on-
line to the user's job, only a subset of the capabilities of local batch input/output are
available through this method of access. Also, there is no need to assign nonallocatable
devices to local files named OUTPUT, PUNCH, P8, or PUNCHB and any other local
file disposed to an output queue because these files are always processed upon job
completion.

Example 1:

ASSIGN(MS, OUTPUT)

This card assigns file OUTPUT to mass storage. With this assignment, a time-sharing
user causes output normally printed at his terminal to be written on a mass storage
file instead. Here, output means information generated by a program durijpg execution.
Informative and error messages are still printed at the terminal. Once this assign-
ment is made, output is written on the mass storage file OUTPUT until the file is
returned or reassigned.

Example 2:

ASSIGN(TT.XYZ)

This card assigns file XYZ to the user's time- sharing terminal. The assignment
causes output that would nornaally be written on XYZ to he printed at the terminal in-
stead.

Example 3:

ASSIGN(MD, ABC)

This card assigns file ABC to an 841 Multiple Disk Drive if one is available.

The ASSIGN card can also be used to create or access existing 7- or 9-track unlabeled
tapes. For a description of the card as it applies to magnetic tape assignment, refer
to Tape Management, section 10.

BKSP CARD

The BKSP control card directs the system to bjrpass a specified number of logical records
in the reverse direction.

The control card format is:

BKSPdfn. n. m)

Ifn Name of the file to be backspaced

n Number of logical records (decimal) to backspace; if this para-

meter is omitted, the system assumes n=l.

m File mode; C for coded, B for binary. If omitted, the system

assumes the file is in binary mode.

60407000 D

1-7-3

The BKSP request can be issued at any point in a logical record. If, for example,
FILEl were positioned within the third record, a

BSKP( FILED

request would reposition FILEl to the beginning of the third record. The system does
not backspace past the beginning of information (BOX). However, EOF indicators are
considered separate records and are included in the record count. An unrecognizable
record count causes the following message:

ERROR IN FILE ARGUMENTS.

to be issued to the user's dayfile.

The BKSP card has no effect on a primary file since that file is rewound after every
operation.

CATALOG CARD

The CATALOG control card requests a listing of information about each record in a
specified file.

The control card format is:

CATALOGdfn, Pj, Pg. • . . . P^^)

Ifn Name of the file to be cataloged

p. May be one of the following:

N=0 Catalog until an empty file is encountered

N=x Catalog x files; default is N=l

N Catalog to end of information

L=frame Specifies the name of the file to receive output;

if this parameter is omitted, the system assumes
L = OUTPUT

U Select user library list (not given unless selected)

D Suppress all comment fields; suppress all page

headings after the initial page heading for each
individual file.

R Rewind Ifn before and after cataloging

CS Suppress character set list for OFL (old program

library) and OPLC (old program library common
deck) type records.

The listing for each file of a multifile set begins on a new page with a page heading
for that file. If the D option has been specified, the page heading appears only once,
at the beginning of the file. The information listed included:

• Number of the record cataloged

• Record name from the first word of the record or the second word of the prefix
(77) table, if present.

• Record tjrpe (list of valid record types follow this list)

l-'^-4 60407000 D

• Length (less 77 table length) in words printed as an octal number

• A checksum (not Including the 77 table)

• Dates and comments in 77 table, if present

• Character set mode for OPL/OPLC type records (unless suppressed by CS
option)

Type may be one of the following.

• ABS

• COS

• OPL

• OPLC

• OPLD

• OVL

• PP

• PPU

• REL

• TEXT

• ULIB

Multiple entry point overlay

Chippewa format central processor program

Modify old program library deck

Modify old program library common deck

Modify old program library directory

Central processor overlay

6000 series peripheral processor program

7600 peripheral processor program

Relocatable central processor program

Unrecognizable as a program

User library program

Entry points are listed for REL and ABS format records. The entire record is listed
for TEXT format records if the name of the record begins with CMRDECK, CMRDC,
IPRDECK. IPRDC. LIBDECK, or LIBDC. The first line is listed for TEXT format
records if the name of the record begins with OVERLAY. Correction identifiers and
their YANK status (refer to the Modify Reference Manual) are listed for OPL and
OPLC records.

A ULIB format record suppresses listing of records in the library unless the U option is
specified on the control card. Zero-length records cause the length since the last zero-
length record to be listed. EOFs cause the length since the last EOF to be listed.

60407000 D

1-7-5

CATALOG OF SYSTEM

FILE

REC

NAME

TYPE

LENGTH

301

PROFILE
PROFILE
ARG«
RFL»
SSJ«

ABS

5112

302

SFS

OVL

01,00

1716

303

OAV

(0000)

155

304

2TJ

(2000)

140

305

(00)

SUM »

25023

306

IBA

(1100)

401

307

3BA

(2000)

308

3BB

(2000)

374

309

3BC

(2000)

136

310

3B0

(2365)

311

3BE

(236i)

312

ICO

(1100)

1051

313

110

(HOC)

165

314

3IA

(2213)

237

315

318

(4113)

316

3IC

(2213)

163

317

5IA

(4325)

318

SIC

(4325)

319

5IE

(4325)

117

320

5IG

(4325)

117

321

2LP

(2000)

253

322

2PC

(2000)

270

323

2RC

(2000)

302

324

(00)

SUM »

4723

CKSUM DATE COMMENTS
7106 75/04/22. 73/05/24.

0262
7256
0744

6467
5751
0425
2771
5527
6720
2713
7162
6117
2354
5366
6335
7601
0462
7764
7000
6063
0151

75/04/19. 73/05/24.
75/04/19. 73/05/05.
75/04/19. 70/12/13.

75/04
75/04
75/04
75/04
75/04
75/04
75/04
75/05
75/05
75/05
75/05
75/05
75/05
75/05
75/05
75/04
75/04
75/04

/19.
/19.
/19.
/19.
/19.
/19.
/19.
/08.
/08.
/08.'
/08.
/08.

/oe.

/08.
/08.
/19.
/19.
/19.

74/04
74/04
74/04
74/04
74/04
74/11
75/03
74/04
74/04
7 4/04
74/04
74/04
74/04
74/04
74/04
70/12
70/12
70/12

/22.
/22.
/22.
/22.
/22.
/25.
/20.
/22.

tzz.

/22.
/22.
/22.
/22.
/22.
/22.
/13.
/13.
/13.

Figure 1-7-1. Sample Page of Catalog of System

1-7-6

60407000 D

325

E200CP

ovt

00^00

326

XSP

(1100)

327

lED

(1100)

328

ILS

(1100)

329

9IA

(2000)

330

9IB

(6000)

331

9IC

(6000)

332

910

(2000)

333

9IE

(2000)

334
335
336
337

9 IF

9IG
9IH
(00)

PP (2401)

PP (1100)

PP (7000)

SUM »

672

255

1075

123

555

122

121

131

4005

5255 75/04/19. 75/03/23.

3067
1267
3727
1661
2452
6122
6133
7515

75/04/19.
75/04/19.
75/04/19.
75/04/19.
75/04/19.
75/04/19.
75/04/19.
75/04/19.

74/05/19.
74/05/19.
74/05/19.
74/05/19.
74/05/19.
74/05/19.
74/05/19.
74/05/19.

671.2 75/04/19. 74/05/19.
2476 75/04/19. 74/05/19.
0056 75/04/19. 74/05/19.

338

CSl

[1123)

533

339

ITP

11100)

140

340

DATADEF

OVL

00>00

14222

341

OATAMAP

OVL

00»00

11330

342

DBFORM

OVL

00>00

14626

343

KTSDMP
KTSDMP
RFL"

ABS

6643

344

LIBTASK
LIBTASK
RFL»

ABS

7653

345

PRESIM

OVL

00*00

15446

346

TRANEX

OVL

00,00

7037

347

TRANEXA

OVL

01,00

260

348

TRANtXB

OVL

01,00

170

349

TRANEXC

OVL

01,00

235

350

TRANEXD

OVL

01,00

253

351

TRANEXE

OVL

01,00

252

352

TRANEXF

OVL

01,00

174

353

TRANDBM

OVL

01,00

6140

354

TRANEXl

OVL

00,00

6332

355

TRANEX2

OVL

01,00

1007

356

TRANSIM
TRANSIM
RFL =
SSJ»

ABS

1455

357

TRANLIB

ULIB

11?

375

BDMLIB

ULIB

140

395

(00)

SUM »

143246

396

DEMUX
DEMUX
RFL =

ABS

3303

5264 75/04/20. 71/11/16.

2011
7267
3602
6462
6370

5646
6643
3744
2473
4042
7276
2614
2655
3221
7120

5272
2502

75/04/20.
75/04/20.
75/04/20.
75/05/08.

75/04/20.

72/09/01.
71/10/13.
71/10/04.
05/08/72.
72/09/23.

4432 75/04/20. 71/09/01.

3173 75/04/20. 73/05/06.

75/05/20.
75/05/20.

75/05/20.
75/05/20.
75/05/20.
75/05/20.
75/05/20.
75/05/20.
75/05/20.
75/05/20.

75/0<r/20.
75/04/20.
75/04/20.
75/04/20.
75/04/20.
75/04/20.
75/04/20.
75/04/20.
72/04/29.
75/04/20.

0562 75/04/20. 71/12/09.

75/04/20.
75/05/20.

2744 75/04/20. 74/05/07.

Figure 1-7-1. Sample Page of Catalog of SYSTEM (Cont'd)

60407000 D

1-7-7

CLEAR CARD

The CLEAR control card releases all the user's current working files.

The control card format is:
CLEAR.

If a primary file exists, only the file name is retained; information within the file is
purged. The empty file remains available as the primary file.

COMMON CARD

The COMMON control card is used to either create or access a librari^ type file.

The control card format is:

COMMONdfnj, Un^. .... Ifn^)

Ifn Logical file name

The user must be validated to access/create library files. The specified file must be
a local mass storage file. If Ifn is not local, a search is made for a library file by
that name and an error message issued if the file is not found. If the operation com-
pletes successfully, the file is attached to the user's job as a library type file.

Before a local file can be made a library file, it must be locked. Refer to the LOCK
control card.

CONVERT CARD

The CONVERT control card converts records from one character set to another.

The control card format is:
CONVERT(Pj, Pg, . . . , P^)

p. May be one of the following:

P=lfnj Input on file Ifnj ; if omitted, file OLD is assumed

N=lfn2 Output on file lfn2: if omitted, file NEW is as-
sumed

RS=n-| Maxim.umi record size in characters (decimal);

l<n< 500. If omitted, 300 is the assumed maxi-
mum record size. (Each character is 6 bits. )

64 Convert from 63-to 64~character set; if omitted,

no conversion takes place. The TS option must
be specified if 64 is not.

TS=tj Convert from old to new time -sharing character

set; U may be one of the following terminal types:

t^ Te rminal Type

TTY ASCII code terminal with standard

print
COR Correspondence code terminal

with standard print

1-7-8 60407000 D

_*!_ TerminsJ. Type

CORAPL Correspondence code terminal
with APL print

MEMAPL Memorex 1240 (ASCII code)
terminal with APL print

BLKEDT ASCII code terminal with stan-

dard print, block edit mode

If ti is omitted, it is assumed to be TTY.
If TS Is omitted, no time-sharing conversion
takes place. The 64 option must be specified
if TS Is not.

R Rewind Input and output files prior to processing.

If omitted, no rewind takes place.

RC=n2 Convert n2 decimal records. If n2 Is omitted,
convert until an E^OF Is encountered. If RC Is
omitted, one record Is assumed.

The following table lists legal conversion using the appropriate CONVERT parameter.

Type of Record Lega l Conversion Parameters

6 3- character set, nontime -sharing 64

record

Old time-sharing record TS or

64 and TS

New NORMAL time-sharing record 64

(equivalent to BATCH character set)

New ASCII time -sharing record None

COPY CARD

The COPY control card causes the first file specified to be copied to the second file.

The control card format is:

COPYdfnj.lfng.x, c)

Ifn^ Name of the file to copy from; if this parameter is omitted, file

INPUT is assumed.

lfn„ Name of the file to copy to; if this parameter is omitted, file

OUTPUT is assumed.

X If a third parameter (1 to 7 alphanumeric characters) is present.

both files are rewound before the copy begins and rewound, veri-
fied, and rewound again after the copy is complete.

60407000 D 1-7-9

c If a fourth parameter (1 to 7 alphanumeric characters) is present,

the copy to or from an SI. S, or L format tape is performed in
coded rather than binary mode.

The copy begins at the current position of both files, unless the x parameter is speci-
fied, and continues until an empty file (a double EOF) or EOI is encountered in Ifnj.
If the copy is terminated by a double EOF, the second EOF is detected but is not trans-
ferred to Ifuo. That is, if the files are not rewound after the copjr (x parameter not
specified), file Ifn^ is positioned after the second EOF and Ifng after the first EOF.

COPYBF CARD

The COPYBF control card causes a specified number of binary files to be copied from
one file to another.

The control card format is:
COPYBF(lfnj, Ifng, n. c)

Ifnj Name of the file to copy from; if this parameter is omitted, file

INPUT is assumed,

IfUg Name of the file to copy to; if this parameter is omitted, file

OUTPUT is assumed.

n Number of files (decimal) on Ifn- to copy; if this parameter is

omitted, n=l is assumed.

c If a fourth parameter (1 to 7 alphanumeric characters) is present,

the copy to or from an SI, S, or L format tape is performed in
coded rather than binary mode.

The copy begins at the current position of Ifn^ . If Ifn^lfn^,, n files are skipped but no
data transfer occurs. If the EOI is encountered before the file count is satisfied, an
EOF is written on lfn2, and the operation terminates.

COPYBR CARD

The COPYBR control card causes a specified number of binary records to be copied
from one file to another.

The control card form^at is:

COPYBRdfni, Ifng, n, c)

Ifnj Name of the file to copy from; if this parameter is omitted, file

INPUT Is assumed.

IfUg Name of the file to copy to; if this parameter Is omitted, file

OUTPUT is assumed.

n Number of records (decimal) to copy; if this parameter is omitted,

n=l is assumed.

c If a fourth parameter (1 to 7 alphanumeric characters) is present,

the copy to or from an SI, S, or L format tape is performed in
coded rather than binary mode.

1-7-10 60407000 D

The copy begins at the current position of Ifn,. EOF indicators are considered separate
records and are included in the record count. If Ifn^slfng. n records are skipped but
no data transfer occurs. If the EOI is encountered before the record count is satisfied,
an EOF is written on lfn2> and the operation terminated.

COPYCF CARD

The COPYCF control card directs the system to copy a specified number of files from
one file to another.

The control card format is:

COPYCF(lfni, lfn2, n.fchar, Ichar)

Ifni Name of the file to copy from; if this parameter is omitted,

file INPUT is assumed.

Ifn2 Name of the file to copy to; if this parameter is omitted,

file OUTPUT is assumed.

n Number of files (decimal) to copy; if this parameter is

omitted, n=l is assumed.

fchar First character position of each line to copy; if this parj*-

meter is omitted, fchar=l is assumed.

Ichar Last character position of each line to copy; if this para-

meter is omitted, lchar=136 is assumed.

The copy begins at the current position of Ifn-^. If Ifn2==lfn2, n files are skipped but no
data transfer occurs. If the EOI is encountered before the file count is satisfied, an
EOF is written on Ifrio. and the operation terminates. COPYCF reformats the file into
line images if it is blocked in greater than Ichar blocks.

If Ichar is less than fchar, Ichar is greater than 150, or either fchar or Ichar is un-
recognizable, the following error message is issued to the user's dayfile.

ILLEGAL CHARACTER. NUMBER.

If COPYCF is attempted on a line longer than 150 characters which does not contain a
line terminator, the following message is issued.

NO LINE TERMINATOR.

If n is illegal or zero, the following message is issued.

ILLEGAL COUNT.

COPYCR CARD

The COPYCR control card directs the system to copy a specified number of records
from one file to another.

The control card format is:

COPYCRdfni, lfn2. n, fchar, Ichar)

Ifnj Name of the file to copy from; if this parameter is omitted,

file INPUT is assumed.

Ifn2 Name of the file to copy to; if this parameter is omitted,

file OUTPUT is assumed.

60407000 D 1-7-11

n Number of records (decimal) to copy; if this param.eter is

omitted, n=l is assumed,,

fchar First character position of line to copy; if this parameter

is omitted, fchar = l is assumed.

Ichar Last character position of line to copy; if this parameter

is omitted, lchar = 136 is assumed.

The copy begins at the current position of Ifn^. If lfnj=lfn2. n records are skipped but
no data transfer occurs. EOF indicators are considered separate records and are in-
cluded in the record count. If the EOI is encountered before the record count is satis-
fied, an EOF is written on lfn2, and the operation terminates. COPYCR is processed
in exactly the same manner as the COPYCF control card except that n specifies the
number of records rather than the number of files.

If COPYCR is attempted on a line longer than 150 characters which does not contain a
line terminator, the following message is issued.

NO LINE TERMINATOR.

COPYEi CARD

The COPYEI control card directs the system to copy one file to another.
The control card format is:

COPYEI(lfnj,lfn2,x.c)

Ifn^ Name of the file to copy from; if this parameter is omitted,

file INPUT is assumed.

Ifn^ Name of the file to copy to; if this parameter is omitted, file

OUTPUT is assumed.

X If a third parameter (1 to 7 alphanumeric characters) is

present, both files are rewound before the copy, and rewound,
verified, and rewound again after the copy is complete.

c If a fourth parameter (1 to 7 alphanumeric characters) is

present, the copy to or from an SI, S, or L format tape is
performed in coded rather than binary mode.

The copy begins at the current position of Ifn^ and continues until the EOI is encountered.
The EOI is not defined for certain tape formats (refer to Data Formats, section 10).

COPYSBF CARD

The COPYSBF control card enables the user to copy a file where the first character of
each line is not a printer control character and is to be printed.

The control card format is:

COPYSBPdfnj, Ifng, n)

Ifn, Name of the file to copy from; if this parameter is omitted, file

INPUT is assumed.

Ifn, Name of the file to copy to; if this parameter is omitted, file

OUTPUT is assumed.

n Number of files (decimal) to copy; if this parameter is omitted,

n=l is assumed.

1_7«12 60407000 D

The COPYSBF routine copies n files beginning at the current position of Ifn^ to file Ifng.
shifting each line image one character to the right and adding a leading space. A page
eject character is inserted at the beginning of each logical record (refer to appendix A for
a list of carriage control characters). If lfni=lfn2. n files are skipped but no data
transfer occurs. If the EOI is encountered before the file count is satisfied, an EOF
is written to lfn2, and the operation terminates.

If COPYSBF is attempted on a line longer than 150 characters which does not contain
a line terminator, the following message is issued.

NO LINE TERMINATOR.

COPYSBF results in single-line spacing and a page eject at the beginning of each
record when the file is printed.

COPYX CARD

The COPYX control card enables the user to specify certain conditions when copying
logical records.

The control card format is:

COPYXdfni, Ifng, X, b, c)

Ifni Name of the file to copy from; if this parameter is omitted,

file INPUT is assumed.

Ifn2 Name of the file to copy to; if this parameter is omitted,

file OUTPUT is assumed.

X Copy specifications; if omitted, one record is copied. The

value for x may be one of the following:

X Meaning

n Number of records (decimal) to copy

00 Copy all records up to and including first

zero-length record

name Copy all records up to and including record

of specified name (record name is first
seven characters of record)

type/name Copy all records up to and including record
of specified type and name (refer to CATA-
LOG control card for list of valid record
types )

b Backspace control; if omitted, is assumed.

b Meanin g

No backspace

1 Backspace file Ifnj^ one record after copy
completes

2 Backspace file lfn2 one record after copy .
completes

3 Backspace files Ifn^ and lfn2 one record
after copy completes

c If a fifth parameter (1 to 7 alphanumeric characters) is

present, the copy to or from an SI, S, or L format tape
is performed in coded rather than binary mode.

60407000 D 1-7-13

The COPYX routine copies logical records from file Ifni to file Hn2 at the current position
of Ifni until the condition specified by x is met. It then backspaces the files according to
the value specified by the b parameter. If lfni=lfn2, the file is repositioned according to
the X parameter; no data is transferred.

DISPOSE CARD

The DISPOSE control card is used to release specified files to the proper output queues.
The control card format is:

DISPOSEafni=qi,lfn2=q2. . . . ,lfnn=qn/ot=usernum)

Ifn^ Name of the file to be disposed

qi Queue type:

PR Print

PH Punch coded 026

P9 Punch coded 029

PB ]l\inch binary

P8 Punch 80 -column binary

ot Origin type to which files are to be disposed:

BC Local batch

EI Remote batch (Export /Import)

usernum Number of the remote batch (that is, ot is EI) user to which

the files are to be disposed (ignored if ot is BC). This
parameter is valid only if the user is allowed deferred
batch jobs. Also, usernum must match the number of the
user performing the DISPOSE on all character positions
except those containing an *.

The file type for file Ifn^ is changed to q^ in the FNT/FST entry for Ifn.. The system
then processes the file according to queue type. Theuser can dispose ^coded punch
files to either 026 or 029 regardless of the job's initial keypunch mode. If the sys-
tem cannot recognize qj^, the following message is issued.

ILLEGAL DISPOSE CODE.

If the ot and usernum parameters are not specified, a remote batch job disposes the
files to the 200 user terminal from which it was submitted, and all other origin types
dispose the files to the central site output device. If ot is BC, the usernum parameter
is ignored and the files are disposed to the central site device.

1-7-14 60407000 D

DOCMENT CARD

The DOCMENT control card enables the user to extract either the external or internal
documentation from a file containing COMPASS source code.

The control card format is:

DOCMENT(pp P2. . . . . p^)

Pi The parameters can be in any order and must be in one

of the following forms.

Omitted The first default value is assumed.

a The alternate default value is assumed.

a=x X is substituted for the assumed value.

Any numeric parameter can be specified with a post radix character of either B or D.
The values that p^ can assume are:

I=lfrn Name of the file that contains the page footing information;

this must be a single card in the following format.

Column(s)

Contents

Blank

•45

Document title

46-

■55

Publication numiber

56-

■60

Revision level

61-

■70

Revision date

S=lfn2 Name of the file containing the source card images from

which to extract the documentation

L=lfn3 Name of the file on which the file is to be written

N=nn Number of copies to be produced

T=type Documentation type:

INT Internal documentation (detailed description

of the internal features of the software)

EXT External documentation (detailed description

of the external features of the software)

C=cc Key character for documentation

P=pp Number of print lines per page

NT Negate table generator

TC List table of contents

60407000 D 1-7-15

The following are the default values lor tne parametera ueaui lucu.

First

Alternate

Parameter

Default

INPUT

COMPILE

SOURCE

OUTPUT

EXT

INT

OFF

Co mment

Page footing information; if I
is 0, no footing information
is printed.

Source card images

List file

Number of copies (decimal)

Documentation type

Check character (two octal
digits)

Number of print lines per page

Table generator status
Table of contents status

Refer to appendix C, volume 2 for a detailed explanation of the documentation standards
followed. It also contains examples of external and internal documentation for program
COPYB.

EVICT CARD

The EVICT control card releases file space for a specified file(s) but does not release
file attachment to the job.

The control format is:

EVICT(lfni.lfno....,lfn )
12 n

Ifn.

Name(s) of the file(s) to be evicted

The operation that EVICT performs depends on the file type. For permianent files, all
file space except the first track is released, job attachixient remains, and an EOI is
written on the first sector of the first track. For all other file types, file space is
released and job attachment remains. Also, all files for which write lockout is set
are returned to the system. An EVICT of a tape file performs the same function as
a RETURN except that EVICT cannot be used to decrease the number of tape units
scheduled via the RESOURC card.

1-7-16

60407000 D

GTR CARD

The GTR control card provides directives for specifying certain records to be copied
from one file to another.

The control card format is:

GTRdfn^ , Ifn , D, NR, S)selection directives

The parameters must be entered in the order shown; they are defined as follows:

Ifn^ File which is searched for the selected records; if this par-

ameter is omitted, file OLD is assumed.

lfn„ File on which the selected records are written; if this par-

ameter is omitted, file LGO is assumed.

D If specified, a directory record (OPLD type) is written at the

end of lfn2. In this case, lfn2 must be a mass storage file.

This parameter has special meaning for ULIB type records,
as follows:

If D is omitted, the first record of the user library,
that Is, the directory record (UPLD), is not copied to
lfn2; the last record (OPLD type) is copied but is not
altered.

If D is specified, the first record of the user library
(UPLD) Is copied to lfn2, but Is not altered, and an addi-
tional record, a new directory for the file (OPLD type),
is added to lfn2.

NR If specified, files Ifni and Ifno are not rewound before or after

the operation. If not specified, Ifn^ and Ifng are rewound both
before and after the operation.

S Ifn-i is processed as a sequential file; no attempt is made to read

a directory.

selection The user can specify the record types and names that he wants

directives retrieved; these can be:

type/nanrie Retrieves record of specified type and name

(refer to CATALOG control card for a list of
valid record types). The record name is the
first seven characters of the record.

name Retrieves the record specified; the type is

either TEXT or the type specified previously.
If name='S=, all records of the specified type
are retrieved.

Inserts a zero-length record on file Ifng.

type/name-- Retrieves records name- through name„ of
name„ type specified,

jTR searches file Ifn^^ for the records specified by the selection directives. The
selected records are then copied to file lfn2 starting at the current EOI. Note that
slanks are not legal between the terminator and the selection directives.

60407000 D 1-7-17

Examples of the use of this control card are:

• GTR(SYSTEM,BIN.D)PP/*

All records of type PP are retrieved from file SYSTEM and copied to file BIN.
A directory is built and placed as the last record on file BIN.

• GTR(OPL. NEW, , NR)OPLC/COMCARG, 0, COMCCIO

Record COMCARG (type OPLC) is retrieved from file OPL and written on
file NEW beginning at the current EOI. Then a zero-length record is written
on file NEW. Finally, record COMCCIO (also type OPLC) is retrieved from
file OPL and written on file NEW at its current position. File OPL is not
rewound either before or after the operation.

• GTR(SYSTEM, SYSLIB, D)ULIB/SYSLIB

The record named SYSLIB (type ULIB) is retrieved from file SYSTEM and
copied to file SYSLIB. The D parameter must be specified to copy the ULIB
directory (UPLD) of a ULIB record set. If the D parameter were omitted,
the UPLD record would be skipped.

LIBEDIT CARD

The LIBEDIT control card specifies directives for editing and replacing binary records
on a file with records from one or more correction files.

The control card format is:
LIBEDIT(pi,p2, .
Pi

Pn>
Any of the following parameters in any order:

I=lfni Directives comprise the next record on file Ifni.

1=0 No directive input.

I omitted Directives are on file INPUT.

P=lfn2 File lfn2 contains the old program library.

P=0 No old program library file.

P omitted Old program library is on file OLD.

N=lfn3 New program library will be written on file lfn3.

N=0 Illegal; no error message is issued, if used.

N omitted New program library will be written on file NEW.

L=l Short correction listing (includes only directives,

modifications, and errors) on the file specified
by the LO parameter.

L=0 No output is listed.

L omitted Full correction listing is written on the file
specified by the LO parameter.

LO=lfn4 List output on file lfn4

LO omitted List output on file OUTPUT.

B-lfns

B=0

B omitted

C omitted

1-7-18

Use file Ifns for the replacement file.
Do not use a default replacement file.
Use file LGO as the default replacement file.

Copy the new library file over the old library file
after processing.

Do not copy the new library file over the old
library file after processing.

60407000 D

R Do not rewind library files after processing.

R omitted Rewind old and new library files after LIBEDIT
and VFYLIB processing.

V Call VFYLIB after LIBEDIT processing.

V omitted Do not call VFYLIB to verify libraries after

LIBEDIT processing.

D Ignore errors and continue.

D omitted Do not ignore errors; abort job.

For a description of the LIBEDIT directives, refer to appendix C.

LIBGEN CARD

The LIBGEN control card allows the user to generate a user library file.

The control card format is:

LIBGEN(pi, pg, . . . . Pn)

p. Any of the following in any order:

F=lfnj^ Name of source file containing records to be

placed on user library file lfn2.

F System assumes source file LGO.

F omitted System assumes source file LGO.

P=lfn2 Name of the file on which the library is to

be written.

P System assumes library to be written on

ULIB.

P omitted Systena assumes library to be written on

ULIB.

N=lfn3 Name of the user library being generated;

this name becomes the name of the ULIB
and OPLD records.

N System assumes lfng=lfn2.

N omitted System assumes Ifn3=lfn2.

NX=n If n Is nonzero, no cross references are

given. That Is, decks are not cross -linked
In the ULIB directory. This can be used to
avoid duplicate entry points on loads.

NX omitted The system assumes n=0.

LIBGEN processes the source file specified and generates a library file on the file
specified with the P parameter. The library is given the name specified with the N
parameter. If the F and P options specify the same file, the message:

FILE NAME CONFLICT.

Is Issued.

60407000 D

1-7-19

LIBGEN rewinds and scans the source file and builds a directory of all entry points,
program names, and external references for records in the file. When an EOF mark
appears, LIBGEN terminates the directory and rewinds Ifnj. LIBGEN then copies Ifn-^
to Ifng, adding the library and directory records. The directory is written as the
first record of the new file. It is indicated as a user library type record by a 76
identification table. The identification table also contains the name of the library.

The directory contains all external references within the library and the linkage to
routines that reside In the library. This Indicates which routines must be loaded when
routines from this library are loaded. This means that all externals for routines in a
library are automatic eilly satisfied from that library first.

The entire file follows the directory record on the new file. The file index is the last
record on the file. This record contains random addresses for each record in the file.
The index record has a table Identifier of TOOOs. LIBGEN processes only REL and
COS type records, bypassing all other record types.

For example, file RELB contains routines that are used at execution tume for several
application programs. It Is desirable to load these routines as needed when executing
the application programs. To generate the library, the following control statement:

LIBGEN(F=RELB, P=MYLIB, N=APPLIB)

is entered. This creates user library APPLIB on file MYLIB. If FORTRAN applica-
tion programs are compiled using the control card:

FTN.

the user library can be used by loading the program In the following manner.

I LDSET(LIB=MYLIB/RUNLIB)

LOAD(LGO).
EXECUTE.

This causes the program to be loaded and executed with externals satisfied first from
user library MYLIB, then from user library RUNLIB, and finally from the system de-
fault library SYSLIB.

LIST80 CARD

The LIST80 routine reads a file containing COMPASS source code and compresses it to
80 columns, which fits on 8-1/2 by 11-lnch printer paper.

The control card format is:

LIST80(lfnj,lfn2.NR)

Ifnj File to copy from; if this parameter is omitted, file LIST

is assumed.

IfHg File to copy to; If this parameter is omitted, file OUTPUT

is assumed.

If this parameter Is specified, Ifn^ is not rewound.

1-7-20 60407000 D

LOCK CARD

The LOCK control card enables the user to prevent writing on a file.
The control card format is:
LOCK(lf ni , If ng . . . . , Ifn^)

Ifn.

Logical file name of a local file

With the LOCK card, the user can set the write interlock bit in the FNT/FST entry for
a local file. Subsequently, the system allows only read operations on the file. The
file specified must be a local file; if it is not. the following message is issued.

ILLEGAL FILE TYPE.

The LOCK card may also be used In conjunction with the COMMON card to lock local
files before making them library files for multiple user access. Refer to Library Files
in section 2 and the COMMON control card.

L072 CARD

The L072 control card allows the user to specify the reformatting of his files.
The control card format is:

L072(pj,p2. . . . ,Pn)
Pi

Any of the following parameters in any order:

I Reformat parameters are on file INPUT.

I=lfni
1=0

S
S=lfn^

L
L=lfn,

T=x

Reformat parameters are on file Ifn,.

There is no input file of reformat parameters.

If the I parameter is omitted, 1 = is assumed.

Data to be reformatted is on file SCR.

Data to be reformatted is on file Ifng. If the

S parameter is omitted, SCR is assumed.

Reformatted data is listed on file OUTPUT.
Reformatted data is listed on file lfn3. If the
L parameter is omitted, OUTPUT is assumed.

File to be reformatted is of type B.

File to be reformatted is of type x, where x is:

M Modify source data

C COMPASS source data

B Other source data

If the T parameter is omitted, B is assumed.

60407000 D

1-7-21

H Number of characters per output line Is 72.

H=xxx Number of characters per output line is xxx

(maximum allowed is 150 characters). If the
H parameter is omitted, 72 is assumed.

NOTE

H miust be greater than or equal to the
numiber of characters being moved (Nx)
plus the starting column number of the
destination field (Ox).

LP Output is formatted for the line printer.

NR Output file is not rewound.

Nx=y Specifies the number of characters to be moved

(up to 6 fields):

x(l to 6) Number of the field being moved

y Number of characters being moved

Note: N1+N2+N3+N4+N5+N6 must be less than or
equal to the numiber of columns specified
in the H parameter.

Ix=y Specifies the field the data originates from:

x(l to 6) Number of the field being moved
y Starting column of originating field

Ox=y Specifies the destination field the data is going to:

x(l to 6) Number of the field to receive data
y Starting column of destination field

1-7-22 60407000 D

The following table shows the default values assumed for the N, O, and I parameters
for the various source types.

Type
B
C

112

The remaining parameters of these types are defaulted to 0.

L072 reformats files (output files in general). The user can rearrange each line (all
lines must be formatted the same) in the format he chooses. All default values com-
press output to 72 columns, which is appropriate for terminal output or 8-1/2 by 11-inch
printer paper. If a 1 is encountered in column 1 (the page eject printer control char-
acter), the next two lines of source data are processed as a two-line header. This
header is compressed to 72 columns for all source types. If no page eject control
characters are encountered, no headers are processed.

The following values apply to the first line of header and cannot be changed.

Nl=42, 11 = 8, 01 = (if LP not specified; otherwise, 01 = 1)
N2=20, 12 = 90, 02=42
N3 = 5, 13 = 115, 03=62
N4 = 5, 14 = 121, 04=67

The subheader lines for COMPASS and Modify listings are processed uniquely.

For B listings, the following values apply to the reformatting.

Nl=43, 11=8, 01 = (if LP not specified: otherwise, 1 = 1)
N2=29. 12 = 70, 02=43

All parameters are passed to L072 by the control card. If an input file is specified.
L072 reads it for additional input parameters. If the job originates from a time-sharing
terminal, the user is asked if he wishes to change any of the input parameters. If he
enters YES, the system prints the current parameter values and allows him to change
them individually. Pressing the carriage return key for any parameter leaves the para-
meter at its former value. In the following examples, the same input parameters are
entered in three possible ways.

Control Card

LO72(I=0, S=SOURCE, T=C. L=OUT, N4 = 1,I4=2. 04 = 75, H = 90)

Time-Sharing Terminal : (underlined data is entered by user)

60407000 D

1-7-23

/L072

DO YOU WANT TO CHANGE A

,NY CONTROL

ARGUMENT VALU

ENTER: YES OR NO

? YES

ARGUMENT

VALUE

INPUT FILE NAME:

? *CR*

SOURCE FILE NAME:

SCR

? SOURCE

OUTPUT FILE NAME:

? OUT

SOURCE FILE TYPE:

? £_

OUTPUT LINE LENGTH:

72 CHARS.

? IQ

NO. OF I.iOVED FROM

MOVED TO

CHARS. COLUMN

COLUMN

(X) (NX)

(IX)

(OX)

1. 7

2. 50

3. 15

112

ENTER CHANGES IN THE FOLLOWING FORMAT:

NX=AA*CR*

IX=BB*CR*

OX=CC*CR*

ETC.

TO CONTINUE. ENTER

*CR*

ONLY.

? N4 = l *CR*

14=2 ^

!=CR*

04 = 75

*CR*

? *CR*
Input File

S=SOURCE, L=OUT, T=C.
N4 = l. 14=2, 04=75
H = 90.
-EOR-

Each line in the input file must end with a terminator.

1-7-24

60407000 D

NEW CARD

The NEW control card creates a primary file.

The control card format is:

NEW(lfn/ND)

Ifn Name of file to be made primary file

ND If this parameter is specified, current working files are

not released

The NEW card creates an empty file and makes it the user's new primary file. Any
currently existing primary file is released.

Note that all current working files are released unless the ND parameter is specified.

OUT CARD

The OUT control card is used to release output files from the control point to the
output queue.

The control card format is:

OUT.

The only files released are those having the names:

OUTPUT
PUNCH
PUNCHB
P8

This control card is used if the user wishes to initiate printing or punching of the
files before job termination. The PUNCH file is punched in either 026 or 029 mode
depending on the origin of the job. If the job is a local batch job, the coded deck
is punched in the initial keypunch mode of the job's control card record. For all
other job origin types, the coded file is punched in the system default keypunch mode.

60407000 D 1-7-25

PACK CARD

The PACK control card allows the user to pack a specified file and copy it to another.
The control card format is:
PACK(lfni,lfn2,x)

Ifn^ Name of file to be packed

Ifng Name of file to receive packed data

X If a third parameter (1 to 7 alphanumeric characters) is

specified, Ifni is not rewound before the pack occurs.

The input file, Ifnj, may consist of any number of records and/or files. If no third
parameter is supplied, Ifn^ is read from the BOX to the EOI, and all EOR and EOF
marks are removed. It is written to file lfn2 at the current position as one record.
File Ifng is rewound after the pack; Ifn^ is not. If lfn2 is not specified, file Ifn^ is
packed to itself.

The programmer should note that problems may arise when using PACK with direct
access files. For example, if file A resides on a legal direct access file device and
the following cards are submitted:

PACK(A)
DEFINE(A)

PACK may copy file A to a device which does not support direct access files. In this
event the DEFINE card would then cause the job to abort and the following message to
be issued to the user's dayfile:

DIRECT ACCESS DEVICE ERROR, AT nnn.
when nnn is the file environment table (FET) address.!

The user can avoid this situation by defining file A as an empty direct access file,
creating the file, and then packing it.

DEFINE(A)
create file A
PACK(A)

The following error messages may be issued to the user's dayfile in response to a PACK
card.

Message Description

PACK PARAMETER ERROR. The PACK control card contains an error.

ILLEGAL INPUT FILE. An attempt was made to pack a file that is

assigned to a time-sharing terminal (for
example, file INPUT for time-sharing origin
jobs represents data typed at the terminal
keyboard, and therefore cannot be packed).

ILLEGAL CIO REQUEST. An attempt was made to pack a nonmass

storage file.

WRITE ON READ-ONLY FILE fff. The direct access file was not attached in

AT nnn. write mode (refer to the ATTACH control

card).

■f Refer to Permanent File Manager, section 5, volume 2.

1_7_26 60407000 D

PRIMARY CARD

The PRIMARY control card makes a local file the primary file.

The control card format is:
PRIMARY (ifn)

Ifn Name of local file

The file to be made prim.ary miust be a local mass storage file. Any currently existing
primary file (other than the Ifn specified) is released. If the specified file is already
primary, the operation is ignored.

The primary file is rewound after every operation performed on that file. Therefore,
the file manipulation cards BKSP, SKIPEI. SKIPF, SKIPFB. and SKIPR cannot be used
to position within the file. The user should also remember that the primary file is
rewound after the completion of any of the COPY cards. An attempt to add to the file
using one of the COPY cards may result in writing over existing data at the BOI.

RENAME CARD

The RENAME control card allows the user to change the name of a local file.
The control card format is:

RENAME(nlfnj=olfnj. nlfn2=olfn2. .... nlfn^=olfn^)

nlfnj New name of the local file

olfn. Existing name of the local file

The RENAME control card is used to change the name of the file olfn^ to nlfn. in the
FNT/FST. This does not change the names of files in the permanent file system.

If a file by the name nlfn; already exists, it is returned to the system. Under certain
conditions the system also changes the file type of olfn^^ to that of the file which was returned.

• If olfn. is a local mass storage file and the returned file was a print, punch,
or primary type file, olfni is renamed and its fil.e type is changed to that

of the returned file.

• If olfn. is a local mass storage file and the returned file was not a print,
punch, or primary type file, olfnj is renamed but its file type is not changed.

• If olfn. is not a local file or does not reside on mass storage, an

ILLEGAL FILE TYPE,
error message is issued.

For example, the user has only two files assigned to his job. File A is a local mass
storage file and file B is a print type file. If the user issues the following request

RENAME (X=A)

file A is renamed file X and its file type (local) is not changed. However, if the user issues the
request:

RENAME(B=A)

file B is returned to the system; file A is renamed file B and changed to a print type file.

1 -7-97

60407000 D 1 ( ^<

REQUEST CARD

The REQUEST control card enables the user to assign a file to a device by including
in the comment field a description of an acceptable device.

The control card format is:

REQUESTdfn, ^^ )

Ifn Name of the file to be assigned to the specified equipment.

CK Specifies that Ifn is to be used as a checkpoint file. Each time

a checkpoint dump is taken, the new information is written at the
previous EOI of Ifn.

CB Specifies that Ifn is to be used as a checkpoint file. Each time

a checkpoint dump is taken, the new information is written at the
BOI of Ifn.

The descriptive comment is displayed at the system console, directing the operator to
make the requested assignment.

If Ifn already exists when the REQUEST is made, no new assignment is made and job
processing continues with the next control card. However, the user can reassign Ifn
by issuing a RETURN on the file before making the REQUEST.

Any user, regardless of his validation, may use the REQUEST card to assign a file
to a mass storage device. However, to assign a file to a nonmass storage device,
the user must be validated to use nonallocatable devices. T if the user does not have
this validation and attempts to request a nonmass storage device, the system aborts
his job.

If Ifn is to be used for checkpoint dumps, either the CK or CB keyword is specified.
These keywords are used in conjunction with the CKP and RESTART control cards; they
allow the user to:

• Save all checkpoint dumps by appending each dump to the checkpoint file:

REQUESTdfn, CK)

• Save the last checkpoint dump by writing each dump at the beginning of the
checkpoint file:

REQUESTdfn, CB)

• Save two consecutive checkpoint dumps by alternately writing on two check-
point files:

REQUESTdfni.CB)

REQUESTdfng.CB)

t Refer to LIMITS control card, section 6.

1-7-28 60407000 D

If the CK parameter is specified for alternate files or if more than two checkpoint files
are specified, the job is aborted and the following message is issued to the user's day-
file.

CHECKPOINT FILE ERROR.

The CK and CB parameters specify a checkpoint file that is local to the job. The user
can make the checkpoint file permanent by placing a DEFINE cardt before the REQUEST.

DEFINEdfn)

REQUESTdfn. CK)

CKP.

The user is not required to supply a REQUEST card to define a checkpoint file. He
can use an ASSIGN or LABEL card, or he can use default values.

If no REQUEST card specifying a checkpoint file has been detected when the first CKP
card is encountered, the system^ requests a device for the user, specifies a file name
of CCCCCC, and selects the CK option. For a subsequent restart job, however, the
system assumes the user has made the checkpoint file available.

The REQUEST card can also be used to create or access existing 7- or 9-track unlabeled
tapes. For a description of the card as it applies to magnetic tape assignment, refer
to Tape Management, section 10.

f Any mass storage file used as a checkpoint file must have write permission.

60407000 D 1-7-29

RESEQ CARD

The RESEQ control card is used to resequence source files which have leading sequence
numbers.

The control card format is:

RESEQdfn, t. xxx, yy)

Ifn Name of the file to be resequenced

t Type of file:

B BASIC source code

T Text source information; a five -digit sequence

number plus a blank is added at the beginning
of each line; the file text, however, is not in-
spected

other Any number at the beginning of a line is Con-

or sidered a sequence number and is resequenced

omitted according to the xxx and yy parameters; numbers

are added to lines where no leading sequence
numbers are present. This option can be used
with time-sharing FORTRAN statements.

xxx New line number of the first statement; if this parameter is

omitted, the system assumes xxx=100

yy Increment to be added to xxx for each succeeding line number;

if this parameter is omitted, the system assumes yy=IO.

Files which have leading sequence numbers include Time-Sharing B'ORTRAN and BASIC
source files. If the file has no leading sequence numbers, five-digit numbers are
attached to the beginning of each line. If the line number encountered or required ex-
ceeds 99999, the following message is issued.

LINE NUMBER LIMIT EXCEEDED.

Some BASIC statements reference the sequence numbers which must also be changed;
therefore, it is imperative that the user specify the proper file type (t). When errors
occur while resequencing a BASIC program, the following message is issued for all
lines containing errors.

ERROR AT LINE xxx.

1-7-30 60407000 D

RETURN CARD

The RETURN control card releases the specified file from job attachment and/or
releases its file space.

The control card format is:

RETURNdfn. , lfn„ ..... Ifn )
L I n

Ifn.

Name(s) of the file(s) to be returned

The operation performed depends on the file type.

Type
Input

Punch

Local

System

Library

Primary

Permanent

Opera tion

The file name is changed to INPUT*. File space is not
released; INPUT* remains attached to the job as a local
file (refer to Input File Control in section 3 for further
information).

Job attachment and file space are released.

Job attachment is released but file space remains.

Job attachment and file space are released.

Write Interlock Is cleared. Job attachment Is released
but the file space remains.

In addition, the RETURN card can be used to decrease the number of tapes or packs
scheduled for the job via the RESOURC control card.

60407000 D

1-7-31

REWIND CARD

The REWIND control card causes files to be rewound and positioned -to the BOI
(or beginning- of- reel for magnetic tape files).

The control card format is:

REWINDdfn, . lfn„ ..... If n )
1 4 n

Ifn. Name(s) of file(s) to be rewound

If the previous operation on the magnetic tape file was a write, a REWIND card causes
the following operations to be performed.

1. If the tape is ANSI labeled, the system writes a tape mark, an EOFl label,
and three tape marks and then rewinds the tape.

2. If the tape is unlabeled and the data format specified on the ASSIGN, LABEL,
or REQUEST card is X. S. L. E. B, or F, the system writes four tape
marks and then rewinds the tape.

3. If the tape is unlabeled and the data format is I or SI. the system writes
a tape mark, an EOFl label, and three tape marks and then rewinds the
tape.

Refer to Tape Management Control Cards in section 10 for further information about
tape files and to appendix G for a description of EOFl and EOVl labels.

SETID CARD

The SETID control card assigns a new identification code for the specified file.

The control card format is:

SETID(lfnj=Xj. lfn2=X2. .... lfn^=x^)

Ifn. Logical file name

X. New identification code for the file (0 through 67g). This code

^ must match the device identification code specified in the EST.

The identification code allows the user to route his file to an output device or device
group with the same identification code. This is useful when a print file requires
special forms.

The fUe Ifnj^ must be an input (INFT), local (LOFT), print (PRFT), or punch (PHFT)
type file or the following message is issued.

ILLEGAL FILE TYPE.

1-7-32 60407000 D

SKIPEI CARD

The SKIPEI control card directs the system to position the specified file at the EOI.
The control card format is:
SKIPEI(lfn)

Ifn Name of the file to be positioned

On magnetic tapes where no EOI is defined, the operation stops at an EOF.

The SKIPEI card has no effect on a primary file since the file is rewound after every
operation.

SKIPF CARD

The SKIPF control card directs the system to bypass, in a forward direction, the
specified number of files from the current position of the named file.

The control card form^at is:

SKIPF(lfn, n, m)

Ifn Name of the file to be positioned

n Number (decimal) of files to be skipped; if the parameter is

omitted, the system assumes n=l.

m File mode; C for coded, B for binary. If omitted, the system

assumes the file is in coded mode.

If an EOI is encountered before n files are bypassed, file Ifn remains positioned at
the EOI.

The SKIPF card has no effect on a primary file since the file is rewound after every
operation.

SKIPFB CARD

The SKIPFB control card directs the system to bypass, in the reverse direction, the
specified number of files from the current position of the named file.

The control card format is:

SKIPFBdfn, n. m)

Ifn Name of the file to be positioned

n Number (decimal) of files to be skipped; if the parameter is

omitted, the system assumes n=l.

m File mode; C for coded, B for binary. If omitted, the system

assumes the file is in coded mode.

The system does not backspace past the beginning -of- information (BOI), in the event
that BOI is encountered before n files are bypassed.

The SKIPFB card has no effect on a primary file since the file is rewound after every
operation.

60407000 D 1-7-33

SKIPR CARD

The SKIPR control card directs the system to bypass, in a forward direction, the
specified number of logical records from the current position of the napied file.

The control card format is:

SKIPR(lfn,n,f , m)

Ifn Name of the file to be positioned

n Number (decimal) of records to be skipped; if this parameter is

omitted, the system assumes n=l.

jt EOR level; 0<f < 17. If 0<j(! < 16, the system assumes £ =0. If

t =17, n indicates the number of files to skip i-ather than records.

m File mode; C for coded, B for binary. If omitted, the system

assumes the file is in binary mode.

EOR marks are considered separate records and included in the record count. If the
EOI is encountered before n records are bypassed, file Ifn remains positioned at the
EOI.

The SKIPR card has no effect on a primary file since the file is rewound after every
operation.

SORT CARD

The SORT control card enables the user to sort a file of line or card images in
numerical order based on leading line numbers consisting of a specified number of
digits.

The control card format is:

SORT(lfn.NC=n)

Ifn Logical file name of the file to be sorted; Ifn may be a local

file or a direct access perm.anent file.

n Number of leading line number digits the file is to be sorted

on; n < 10. If the NC parameter is omitted, the system
assumes n=5.

In the case of duplicate line numbers, all lines other than the first are considered
correction lines. All lines with the same number are deleted from the file except the
last line encountered.

1-7-34 60407000 D

For input from a time-sharing terminal, SORT deletes a line or card image if a line
number is followed by an empty line or a line number is followed by a blank and a
carriage return.

For batch input, SORT deletes a card or line image if a card containing only the line
number is submitted.

If a line number contains more than n digits, the user can delete the line either by
entering the first n digits of the line number and pressing the carriage return (terminal
input) or by submitting a card containing only the first n digits of the line number (batch
input).

After the sort, Ifn is packed and set at EOI.

The following SORT error messages may be issued to the user's dayfile.

Description

Message
NO LINE NUMBER ON SORT FILE

ILLEGAL SORT PARAMETER.

EMPTY SORT INPUT FILE.

WRITE ON READ-ONLY FILE fff
AT nnn.

A line on the input file is missing a line
number or a line exceeded the 150-char-
acter limit.

The SORT control card is in error.

File Ifn contains no data.

The direct access input file was not
attached in write mode (refer to the
ATTACH control card).

60407000 D

1-7-35

STAGE CARD

The STAGE control card causes files to be copied from the specified device to a file
residing on mass storage.

The control card format is:

STAGEdfn. Pj. Pg. ••••?„)

Ifn Name associated with file to be staged from magnetic tape to

mass storage

p- Any of the following in any order:

NR Do not rewind Ifn before beginning operation;

default is rewind.

NU Do not unload Ifn after staging operation; de-

fault is automatic unload.

DR Drop job after staging operation.

N=n Copy n files to Ifn.

T=xx Stage file Ifn from device with EST ordinal

XX. t This parameter is specified only when
tape containing files to be staged is unlabeled
(X format and system default density).

VSN=vsn Specifies the 1-to 6-character volu:me serial
number of the labeled tape containing the file
to be staged

D=den Tape density:

200 200 bpi (implies 7-track)

556 556 bpi (implies 7-track)

800 800 bpi/cpi (7- or 9-track)

1600 1600 cpi (implies 9-track)

F=format Data format (refer to section 9):
I Internal

X External

SI SCOPE Internal

MT 7-track tape (default)

NT 9-track tape

If T is not included but VSN is included, n files are copied from the specified tape.
If neither T nor VSN is included, a request for ifn is issued to the operator. If DR
is not included, STAGE requests the next set of parameters for the next staging opera-
tion to be entered by the K display on the system console. When Ifn is staged to mass
storage, it is designated as a library file. If a library file already exists with the
same name as the file being staged, the system issues the following message.

DUPLICATE COMMON FILE NAME.

tContact installation personnel for a list of EST ordinals.

j.^.gg 60407000 D

TDUMP CARD

The TDUMP control card lists a file in octal and/or alphanumeric form.

The control card format is:

TDUMP(ppP2.....p^)

Any of the following in any order:

I=lfn

L=lfn2
O

R=r count

F=f count

N=lines

Input file name (default is TAPED

Output file name (default is OUTPUT)

Octal dump only (default is octal and
alphanumeric dump)

Alphanumeric dump only (default is octal
and alphanumeric dump)

Number of records in decimal to dump
(default is dump to EOI)

Number of files in decimal to dump (de-
fault is dump to EOI)

Maximunn number of lines in decimal that
can be dumped (if N is omitted, there is
no restriction on the number of lines).

Do not rewind file Ifnj before dump (de-
fault is to rewind Uni).

The user has the option of dumping the entire file or of specifying the number of
records, files, or lines to dump.

60407000 D

1-7-37

UNLOAD CARD

The UNLOAD control card releases job attachment and/or the file space of the specified
file.

The control card format is:

UNLOADdfnj, Un^. .... Ifn^^)

Ifn. Name(s) of the file(s) to be unloaded

The UNLOAD card perfci'ms the same function as the RETURN control card; for
additional information, refer to the description of the RETURN card earlier in this
section). Unlike the RETURN card, an UNLOAD of a magnetic tape file cannot be used
to decrease the number of tape units scheduled for the job via the RESOURC control
card. For raagnetic tape files, if the previous operation was a write, the UNLOAD
card causes the following operations to be performed.

1. If the tape is ANSI labeled, the system writes a tape mark, an EOFl label,
and three tape marks and then unloads the tape.

2. If the tape is unlabeled and the data format specified on the ASSIGN, LABEL,
or REQUEST card is X, S, L, E, B, or F, the system writes four tape marks
and then unloads the tape.

3. If the tape is unlabeled and the data format is I or SI, the system writes a
tape mark, an EOFl label, and three tape marks and then unloads the tape.

Refer to Tape Management Control Cards, section 10. for further information about tape
files and to appendix G for a description of an EOFl label.

UNLOCK CARD

The UNLOCK control card rescinds the LOCK command and clears the write interlock
bit for the specified file.

The control card format is:

UNLOCK(lf Uj , If ng , . . . , Ifn^)

Ifn. Name(s) of local file(s)

The file must be a local file; if it is not, the following message is issued.
ILLEGAL FILE TYPE.

1-7-38

60407000 D

VERIFY CARD

The VERIFY routine performs a binary comparison of all data from the current position
of the files specified.

The control card format is:

VERIFYdfni. Ifn2, Pi. P2. • • • . Pn^

Ifn, Name of the first file; if this parameter is omitted, the

system assumes TAPEl.

Ifn^ Name of the second file; if this parameter is omitted, the

system assumes TAPE2.

p. Any of the following in any order:

N=0 Verify terminates on the first empty file en-

countered on either file.

N=x Verify x files; default is N=l.

N Verify terminates when end of information is

encountered on either file.

E=y List the first y errors encountered on the

comparison. If E is omitted, the system
assumes E = 100.

L=lfno List errors on file Ifn,. If L is omitted, the
system assumes L=OUTPUT.

A Abort if errors occur.

R Rewind both files before and after the verify.

Whenever words on the two files do not match, VERIFY lists the:

• Record number

• Word number within the record

• Words from both files that do not match

If errors are encountered, the following message is issued to the user's dayfile.

VERIFY ERRORS.
If any pair of Ifn^, lfn2. and Ifng are identical, the following message is issued.

FILE NAME CONFLICT.

1 -7-.^9
60407000 D

VFYLiB CARD

The VFYLIB program perforins a compare on binary records from the current position
of the specified files.

The control card format is:

VFYLIBdfnj, Ifn^. Ifn^, NR)

Ifn^ Name of the first file; if this parameter is omitted, the system

assumes OLD.

lfn„ Name of the second file; if this parameter is omitted, the system

assumes NEW.

lfn„ Name of the file to receive output; if this parameter is omitted,

^ the system assumes OUTPUT.

NR If specified, Ifn^ and lfn„ are not rewound.

The VFYLIB program lists:

• Replacements

• Deletions

• Insertions

on the output file Ifn,. A program is defined as being replaced when the actual binary
code is changed. Information in the prefix (77) table such as last modification date and
last assembly date are skipped in VFYLIB's comparison.

WRITEF CARD

The WRITEF control card directs the system to write a specified number of file marks
on the named file.

WRITEFdfn, x)

Ifn Name of the file to be written on

X Number of file marks to be written; if this parameter is

om^itted, the system assumes x=l.

WRITER CARD

The WRITER control card directs the system to write a specified number of empty
records on the named file.

The control card format is:

WRITERdfn, x)

Ifn Name of the file to be written on

X Number of empty records to be written; if this parameter is

omitted, the system assumes x=l.

1-7-40 60407000 D

PERMANENT FILE CONTROL CARDS

The permanent file control cards allow the user to utilize the permanent file system. '
The control cards included in this category are:

SAVE

APPEND

DEFINE

PERMIT

ATTACH

GET

PURGALL

CATLIST

OLD

PURGE

CHANGE

PACKNAM

REPLACE

The cards described in the following section allow the user to create permanent files
(DEFINE) and make local files permanent (SAVE, REPLACE). These fUes can be
accessed (ATTACH, GET), added to (APPEND), and destroyed (PURGE, PURGALL).
Requests are directed to a specified auxiliary device by the PACKNAM card. Certain
parameters can be changed with the CHANGE card without attaching and redefining
the file or retrieving and saving it.

Information on permanent files is obtained through the CATLIST card. Part of that
information is the permission status of the user as granted by another user by means
of the PERMIT card.

The following pages list options available on the control cards. Unless otherwise
stated, the options described apply to all of the permanent file control cards. For
a detailed description of permanent file structure, refer to section 2. Errors en-
countered during permanent file control card processing cause error messages to be
issued to the user's dayfile. For a description of these messages, refer to appendix
B.

t The batch user is unable to access permanent files unless he has included a
USER card in the job deck.

60407000 D

Keyword

UN =

Option

usernum

PW =

CT =

passwrd

Description

Alternate user number. This parameter is
necessary only if the permanent file involved
resides in another user's catalog. To be able
to access other catalogs, the. user must be
granted explicit permission (refer to the PERMIT
control card), the file must be a semiprivate
or public file, or the user must have automatic
permission. A user has automatic permission
to files in catalogs of other users if his user
number contains asterisks, and all nonasterisk
characters match the other user's user number.

The user has the option of specifying a l-to-7-
character password for a file. This password
miust be specified whenever alternate users access
the file.

Permanent files fall into three categories which
specify the method of access. This option must
be selected when the file is saved or defined.
The categories are:

p Private files are available for

or access only by the originator or

PRIVATE those to whom the originator has

explicitly granted permission (refer
to the PERMIT control card).

S Semiprivate files are available for

or access by all users who know the

SPRIV file name, user number, and pass-
word. The system records in the
originator's catalog the user num-
ber of each user who accessed the
file, the number of accesses, and
the date and time of the last access

PU Public files t are available for

or access by all users who know the

PUBLIC file name, user number, and pass-
word. The system records the
number of times the file was
accessed but does not record user
numbers or the last access date
and timie.

tCT=LI can also be used to specify public files.

1-8-2

60407000 D

Keyword
M =

Option

Description
File or user permission mode:

W Allows the user to write, read.

WRITE

M
or
MODIFY

A
or

APPEND

READ

READMD

READAP

EXECUTE

N
or

NULL

append, execute, modify, and/or
purge the file. This mode can be
specified for direct or indirect
access files.

Allows the user to modify, append,
read, and /or execute a direct
access file. Adding new informa-
tion within the existing boundaries
of the file is legal but the file
size must be maintained.

Allows the user to append infor-
mation to the end (EOT) of the file.
This mode can be specified for
direct or indirect access files.

Allows the user to read and/or
execute the file. This mode can
be specified for direct or indirect
access files.

Allows the user to read and/or
execute a direct access file with
the implication that another user
may currently be accessing the same
file in MODIFY mode. This
mode can be specified only for
direct access files.

Allows the user to read and/or
execute a direct access file with
the implication that another user
may currently be accessing the
same file in APPEND mode. This
mode can be specified only for
direct access files.

Allows the user to execute the file.
If the file is attached to the user's
job in E]XECUTE mode, the file
must be in absolute format. This
mode can be specified for direct
or indirect access files.

Relocatable files with EXECUTE
permission may be loaded and
executed only via a stand-alone
file name call (such as LGO),
which is not preceded by a
loader control.

Removes permission previously
grantsd via PERMIT control cards.
This mode can be specified for
direct or indirect access files.

60407000 D

1-8-3

Keyword

Option
r

Descrip tion

Specifies the type of device on which the permanent
file resides or is to reside; r can be any of the
following.

r Device

DE Extended Core Storage

Dli 844 Disk Storage Subsystem (l<_i<_8)

DP Distributive Data Path to ECS

MDi 841 M/ultiple Disk Drive (l<i<_8)

PN =

space

packname

The R keyword can be used in two ways.

1. It can be used on the DEFINE control card

to specify the family device on which the direct
access permanent file is to reside.

2. It can be used in conjunction with the PN
and NA keywords on any per:manent file con-
trol card (including DEFINE) to identify the
auxiliary device on which the permanent file
resides or is to reside. R is required only
if the desired device has a device type
different from that of the available device
and the installation has defined the desired
device as rem.ova.ble. If PN and NA are
specified but R is not specified, the system
default device type is used. If the specified
device type cannot be recognized or does
not exist in the system, the following
miessage is issued to the user's dayfile.

ILLEGAL DEVICE REQUEST, AT nnn.

Specifies the amount of space in decimal PRUs
desired for the direct access file. Refer to the
DEFINE control card.

A l-to-7 character pack name used in conjunction
with the R keyword to identify the auxiliary device
to be accessed in the permanent file request. This
parameter is specified only when the file to be accessed
resides on an auxiliary device. If the device is
currently not available and the NA keyword was not
specified, the following message is issued to the
user's dayfile.

DEVICE UNAVAILABLE, AT nnn.

An auxiliary device is a mass storage device that
supplements the normal family of permanent file de-
vices. A RESOURC control card must be included in
any job that uses two or more disk packs con-
currently.

1-8-4

60407000 D

Keywford

Option

Des cript ion
The NA keyword can be used in two ways.

1. Normally, if the user attempts to access
a file that is interlocked or if an error
occurs in an attempt to process the file,
the system aborts the job. With the

NA option the user can bypass a job abort
and continue processing. If Ifn is busy and
the NA option is specified on an ATTACH
control card, the system automatically
suspend the job until the file becomes avail-
able. If NA is specified and an error other
than pfn IBUBY occurs in processing file
Ifnj^, the system issues the appropriate
error message to the user's dayfile and then
continue with file Ifn., •.. If the error
occurred on the last file specified on the
cardj the system continues with the
next card*

2. If the user requests an auxiliary device
that is currently not available, the system
will abort his job. The NA keyword enables
him to bypass this abort and direct the
system to make the desired device available.

The ND keyword prevents releasing of the
user's working files upon processing of an
OLD control card.

Several files can be accessed with one control card. A slash (/) is used to separate
the files being accessed and the options described previously. The special options
are order-independent and are indicated by the keywords described. If special options
are specified on the control card, they apply to all files that appear on the card.

APPEND CARD

The APPEND control card allows the user to add supplenrientary information to an
existing indirect access file.

The control card format is:

APPEND(pfn, Ifnj, lfn2, .... lfnn/PW=passwrd, UN=usernum, PN=packname, R=r, NA)
pfn Name of the indirect access permanent file to which the

Ifm

locEil files are to be appended

Name(s) of local file(s) to be appended to pfn

The logical structure of the two files is retained; that is, EORs and EOFs are appended
as well as data. If the file is appended to a file in an alternate user's catalog, a
password naust be supplied if one is required.

60407000 D

1-8-5

ATTACH CARD

The ATTACH control card allows a user to access a direct access file.
The control card format is:

ATTACH(lfnj=pfn^,lfn2=pfn2.
PN=packname, R=r, NA f

,lfnj^=pfn^/UN=usernum, PW=passwrd,M = m,

Ifn,

pfnj

Local file name given to the direct access file while it is attached
to the user's job. A working copy is not generated
since user access is made directly to the permanent file.
Thus, Ifnj is used only when it is desirable to reference the
attached file by a name other than its permanent file name,
pfni.

Name of direct access file to be attached. If pfnj^ is omitted,
the system assumes pfnj^=lfnj^.

File or user permission mode, where m can be W, M, A, E,
R, RM, or RA. If m is omitted, the system assumes m is
R. This option must be specified by all users, including the
originator, if the file is to be modified or new information is
to be added to the file. If pfn^ is attached in W mode, the
date is recorded as last modification date even if the file
was not altered.

A read/write interlock is provided to ensure that only one user at a time can access
the file in write mode. Several users may access the file in read mode simultaneously.
The user should return the file as soon as possible to enable other users to access the
file. If Ifn^ is present before this command is issued, it is returned to the system
even if an error is encountered when processing the command.

The following tables show the resulting current access modes when the user attempts
to attach an active file. (FB means the file is busy and cannot be attached at that
time. Refer to the NA option. )

TABLE 1-8-1. RESPONSE TO CURRENT ACCESS WRITE /READ ACCESS DESIRED

Current Access

Access Desired

M/R

A/R

TABLE 1-8-2. RESPONSE TO CURRENT ACCESS READ/READ ACCESS DESIRED

Current Access

Access Desired

Free

1-8-6

60407000 D

TABLK 1-8-3, RESPONSE TO CURRENT ACCESS READ/WRITE ACCESS DESIRED

Current Access

Access Desired

Free

M/R

A/R

The resulting current access listed in these tables should not be confused with the mode
the user will have when requesting file access. For example, in Table 1-8-1, the user
desires RM (read/allow modification) access and the current access is M (modify). The
resulting current access (M/R) indicates that one user is modifying the file and at least
one user is reading the file. The user requesting RM access is permitted read-only
access.

Note that if an auxiliary device has been previously specified by a PACKNAM card, the
system attempts to attach pfn^ from the auxiliary device rather than the normal system
devices.

CATLIST CARD

The CATLIST control card lists information about the user's permanent files or those
permanent files he can access in the catalogs of alternate users.

The control card format is:

CATLIST(LO=p, FN=pfn, UN=usernum, PN=packname, R=r, L=lfn, NA, DN=dn)

p One of the following list options:

F Selects a listing of pertinent information about

each file in the user's catalog. If an alternate
user number is specified (UN option), the user
obtains a listing of all files that he can access
in the alternate user's catalog. Note that the
password for files in an alternate user's catalog
is not included in the listing. The password to
files in an alternate user's catalog must be ob-
tained directly from that user.

FP Selects a listing of permission information

recorded for each alternate user of a specified
file in the user's catalog. This option requires
that a file name be specified (FN option). If
an alternate user number is specified (UN option),
only the permission information for that user of
the specified file is listed.

The user numbers listed include those that have
been granted explicit permission to the file
(private file only) and those that have accessed
the file because of implicit permission (semiprivate
files only).t

tUser numbers are not recorded for accesses to public files.

60407000 D

1-8-7

pfn

usernum

packname

Ifn

Selects a short list that includes only the names

(zero) of the files in the user's catalog. If an alternate
user number is specified (UN option), the user
obtains only the names of the files that he can
access in the alternate user's catalog. If no
LO keyword is specified, the system assumes
this value.

P Selects a short list that indicates only the user

numbers of alternate users who have accessed
the specified private or seniiprivate file. This
option requires that a file namie be specified
(FN option).

Permanent file name. This option specifies that catalog
information is desired only for this permanent file. This
parameter is required when listing permit information
(LO=FP, LO = P). If the short list options are selected
(LO=0, LO = P), the message

pfn FOUND. AT nnn.

is issued if the file (or user number) is located. The
message

pfn NOT FOUND, AT nnn.

is issued if the specified file (or user number) is not located.

User number. This parameter has two purposes.

1. For LO=F and LO=0. Indicates the alternate catalog
for which the user desires catalog information.

2. For LO=FP and LO=P. Indicates the permission
information recorded for the specified alternate user.

This parameter specifies an auxiliary device that contains
catalog information for all users with files on that device.
The PN keyword must be specified if the user wishes to
obtain the following information from his catalog on the
specified auxiliary device.

• Pertinent information about each file (LO=F)

• Only the name of each file (LO = 0)

• Permission information for each alternate user that
has accessed a specific file (LO==FP)

• Only the user number of each alternate user that
has accessed a specific file (LO = P)

The PN parameter can also be specified to allow alternate
users to obtain a list of files they can access on the auxiliary
device, as well as pertinent information about each file.

Output file name. This is the name of a local file to which
the CATLIST information is written. If this parameter is
omitted, the system assumes L=OUTPUT. If Ifn exists and
is positioned at BOI, the contents of that file is purged be-
fore the CATLIST information is written. However, if Ifn
exists and is positioned at EOI, the CATLIST information is
appended to the file as a new logical record.

1-8-8

60407000 D

NA No abort option. CATLIST continues processing if errors

are encountered during processing.

dn Device number (0 through llg). List file residing on

specified device number dn.

If no entries are present in the specified catalog, the message

EMPTY CATALOG.

is issued to the user's dayfile.

CHANGE CARD

The CHANGE control card allows the originator of a direct or indirect access file to
alter any of several parameters without having to attach and redefine the file or re-
trieve and save it.

The control card format is:

CHANGE(nfn=ofn/CT=ct. M=m, PW=passwrd, PN=packname, R=r, NA)

nfn New permanent file name

ofn Old permanent file name. If no name change is desired,

only ofn is specified.

The CT, M, and PW keywords should be specified only if a change in the value asso-
ciated with that keyword is desired. To clear the password for an existing file, the
user must set PW=0. The PN and R keywords cannot be used to specify a new auxiliary
device. They are used only to specify the device on which ofn resides. CHANGE also
updates the last modification date and last access date for the specified file.

The following messages may be issued to the user's dayfile in response to a CHANGE
request.

Message Description

ofn NOT FOUND, AT nnn. The specified permanent file, ofn, was not

found in the user's cEitalog.

nfn ALREADY PERMANENT, The new permanent file, nfn, already exists

AT nnn. in the user's permanent file catalog.

60407000 D 1-8-9

DEFINE CARD

The DEFINE control card allows the user to define direct access permanent files.

The control card format is:

DEFINE (Ifni=pfni,lfn2=pfn2, . . . , lfn„=pfnn/PW=passwrd, CT=ct.M=m, R=r,
S=space, PN=packname, NA)

Ifn,

pfn.

If DEFINE is to be used to create an empty direct access
permanent file, Ifnj is specified only if the user desires to
reference the file by a nanrie other than its permanent file name.
If DEFINE is to be used to define an existing local file as a
direct access file, Ifn- is the name of the local file. Also,
if Ifnj exists, its position is not altered.

Permanent file name. If pfnj^ is omitted, the system assumes
lfnj=pfnj.

Type of device on which the permanent file is to reside. The
device must be a permanent file mass storage device on which
direct access files are allowed.

The user can either create an empty permanent file or define an existing local file as
a direct access file. If the user releases the file and wishes to access it at some
time in the future, the ATTACH control card must be included.

If Ifni does not exist, the device on which pfn^ resides depends on the r and space
parameters.

Specified
Specified

Not specified

space
Not specified

Specified
Specified
Not specified

Residency

The file resides on the device of type r with
the most space available.,

The file resides on the device of type r with
the most space available, provided that de-
vice has as many PRUs available as specified
by the space parameter.

The file resides on the device with the most
space available, provided that device has as
many PRUs available as specified by the
space parameiter.

The file resides on the device with the most
space available.

If an auxiliary device has been previously specified by a PACKNAM card, pfn. resides
on that auxiliary device rather than a system device.

If the optional parameters are omitted, the system assumes the following values.
Keyword Default

PW None

CT PRIVATE

M WRITE

PN None

1-8-10

60407000 D

If the S option is selected and no device has the specified amount of space available, the
request is aborted and the following message is issued to the user's dayfile.

PRUS REQUESTED NOT AVAILABLE, AT nnn.

Unused space is not guaranteed to be available if the user attempts to expand the file
at a later time.

If Ifn. already exists on a device other than that specified by r, or an illegal device
is specified, the system issues the following message to the user's dayfile.

DIRECT ACCESS DEVICE ERROR, AT nnn,

GET CARD

The GET control card enables the user to retrieve a copy of file pfni for use as a
local file.

The control card format is:

GET(lfn2=pfni, Ifn2=pfn2, . . . , lfnn=pfnji/UN=usernum, PW=password, PN=packname,
R=r, NA)

Ifm Local file name given the file while in use

pfn;^ Permanent file name. If pfnj^ is omitted, lfn^=pfnj

If the request is made with no parameters specified, the user's primary file is as-
sumed.

Each pfn specified must be an indirect access file. File Ifnj^ is returned to the
system if it is present before this command is issued even if an error is encountered
in processing the command. The new file is rewound. No interlock is provided to
prevent other users from obtaining working copies of the same file simultaneously.
If the name of the user's current primary file is specified as an Ifn, the corresponding
pfn is made the new primary file and any subsystem associated with it becomes the
user's new current time -sharing subsystem.

If the request is for a file in another user's catalog (UN option specified), the per-
mission mode is that which the user has beep permitted for private files or that speci-
fied in the catalog for semiprlvate and public files.

If an auxiliary device has been previously specified by a PACKNAM card, the system
attempts to retrieve the copy of pfn^ from the auxiliary device rather than the normal
system devices.

OLD CARD

The OLD control card retrlves a copy of a permanent file and makes it the primary file.

The control card format Is:

OLD(lfn=pfn/UN=usernum, PW=passwrd, PN=packname, R=r, NA, ND)
Ifn Local file name given the file while in use

pfn Permanent file name. If pfn is omitted, lfn=pfn.

60407000 D 1-8-11

The OLD card performs the same operation aa the GET card, and additionally makes
Ifn the primary file. Any currently existing primary file is released. All working
files are also released unless the ND parameter is specified.

If an auxiliary device has been specified previously by a PACKNAM card, the system
attempts to retrieve the copy of pfn from the auxiliary device rather than the normal
system devices.

PACKNAM CARD

The PACKNAM card directs subsequent permanent file requests to the specified auxiliary
device.

The control card format is:

PACKNAM(PN= packname )
or

PACK (packname)

packname A 1- to 7-character name used to identify the auxiliary device

to be accessed in subsequent permanent file requests

PACKNAM allows the user to omit the PN keyword from requests for files that reside
on the specified device. However, if permanent files on another auxiliary device are
to be accessed, the PN keyword can be specified in the request or another PACKNAM
request can be issued. Refer to Permanent File Devices, section 2 for information
concerning auxiliary permanent file devices.

The user cannot access permanent files residing on the normal system devices while
the PACKNAM request is in effect. To access these files, he must include a PACK-
NAM card in either of the following formats,

PACKNAM

or
PACKNAM(PX=0)

1_8-12 60407000 D

PERMIT CARD

The PERMIT control card allows a user to explicitly permit another user to access a
private file in his permanent file catalog.

The control card format is:

PERMIT(pfn, usernumi=m2, usernum2 = ni2, .... usernumj^fmn, PN=packname, R=r, NA)

pfn Permanent file name

usernum- User number to be permitted access to pfn

m. Permitted mode of access. If m^ is omitted, the system

assumes mode R.

If pfn is a public file, the following message is issued.

PFM ILLEGAL REQUEST, AT nnn.

PURGALL CARD

The PURGALL control card purges all permanent files in the user's catalog that
satisfy the criteria specified by the parameters.

The control card format is :

PURGALL(CT=ct, AD=ad, MD=md, CD=cd, DN=dn, TY=ty, TM=tm, FN=packname, R=r, NA)

ct File category

ad Last access date; format of date is yymmdd

md Last modification date; format is yymmdd

cd Creation date; format is yymmdd

dn Device number (0 through Tig). The device number is

assigned during system configuration time when the device
is defined. It uniquely identifies a device within a family.'

ty File type:

or Purge all indirect access files

INDIR

or Purge all direct access files

DIRECT

or Purge all files

ALL

If this parameter is omitted but other parameters are
specified, the system assumes ty is ALL. If no other
parameters are specified and the user wishes to purge
all files, he must specify TY=A.

tm Time of day on the date specified by ad, md, or cd

parameter. The time of day is expressed in the format
hhmmss.

' Refer to section 2 for further information about families of permanent file devices.

60407000 D 1-8-13

packname Name of auxiliary device on which the files to be purged

reside. The PN option cannot be selected if a device
number was specified.

r Type of auxiliary device on which the files to be purged

reside. The R option cannot be selected if a device
number was specified

The AD, MD, and CD keywords are used to purge any files whose Jast access, last
modification, or creation occurred before the specified date. To purge all files in
his catalog, the user must enter:

PURGALL(TY=A)

CT, CN, TY, TM, and either AD, MD, or CD may be entered simultaneously.

PURGE CARD

The PURGE control card allows a user to remove a file from the permanent file device.

The control card format is :

PURGE(pfni, pfn2, — , pfn^/UN=usernum, PW=passwrd, PN-packname, R=r, NA)
pfn. Permanent file name

I If the request is made with no parameters specified, the user's primary file is assumed.

When a PURGE command is issued for a direct access file which is not being used,
the file is purged and the permanent file catalog altered accordingly. If the direct
access file is in use, the catalog is altered to reflect purging of the permanent file
but the actual file is not purged untU the last user returns it.

To purge a file in an alternate user's catalog, the user must have write permission
or the file must be semiprivate or public with write mode. If pfn-]^ does not exist,
the following message is issued.

pfn NOT FOUND, AT nnn.

REPLACE CARD

The REPLACE control card enables the user to place a copy of a local file in the
permanent file system as an indirect access file.

The control card format is :

REPLACE(lfni=pfni, lfno=pfn2. . . . , lfnn=pfnjj/UN=usernum, PW = passwrd,
PN=packname, R=r,'TJA)

Ifn. Local file name

pfnj Permanent file name. H pfnj^ is omitted, lfnj^=pfni.

I If the request is made with no parameters specified, the user's primary file is assumed.

If pfn- already exists, it is purged and replaced by the new file. The new file is in
the same category as the file it replaced. If pfn, does not exist, the new file is saved
as a private file. Permission information and alternate user access data for the fQe
are not lost when a file is replaced.

A user who has been granted write permission to another user's file can replace that

file only if he is validated to create indirect access permanent files (refer to LIMITS

control card, section 6. )

60407000 D
1-8-14

SAVE CARD

The SAVE control card allows the user to retain a copy of a local file as an indirect
access file.

The control card format is :

SAVE(lfni=pfni, Ifn2=pfn2. .... lfnn=pfnn/PW=passwrd, CT=ct, M=m, PN=packname,
R=r, NA)

Ifn^ Local file name

pfnj^ Permanent file name. If pfn^^ is omitted, the system

assumes lfnj=pfnj^.

If the request is made with no parameters specified, the user's primary file is assumed.]
If the name of the user's current primary file is specified as an Ifn, the user's current
subsystem is stored in the file's catalog entry.

The local files are rewound when the save operation is completed. If the optional
parameters are omitted, the system assumes the following values.

Keyword

Default

None

PRIVATE

WRITE

If an auxiliary device has been previously specified by a PACKNAM card, the system
saves pfn^ on the auxiliary device rather than a normal system device.

If pfnj^ already exists in the user's catalog, the following message is issued.

pfn ALREADY PERMANENT. AT nnn.

60407000 D 1-8-15

LOAD/DUMP CENTRAL MEMORY UTILITY CONTROL CARDS

The load/dump central memory utility control cards allow the user to transfer infor-
mation that resides in his job field length to a peripheral device or to transfer infor-
mation from that device into central memory. The following cards are included in this
category.

DMP

LOC

RBR

DMD

PBC

WBR

LBC

The DMP and DMD control cards dump central memory in octal representation and/or
display code equivalences. These cards are particularly helpful in creating dumps for
debugging purposes. (Refer to Debugging Aids, section 13.) Other transfers of data
from central memory use the PBC card which dumps a binary record to PUNCHB and
the WBR card which writes a binary record on a specified file.

Data is loaded to central memory by the LBC, LOC, and RBR cards. The LBC con-
trol card is useful in loading binary data in an unknown format. All numeric parameters
may be expressed in octal (post radix is B) or decimal (post radix is D) notation. If
no radix is specified, octal is assuicned. If the parameter is expected to be numeric
and only B or D is specified, the value is assumed to be zero.

DMP CARD

The DMP control card requests a dump on file OUTPUT of central memory in four words
per line.

The control card fornaat is:

DMP(fwa, Iwa) or

DMP(lwa) or

DMP.

fwa First word address of memory to be dumped; fwa is relative

to RA. If fwa is absent, dump mode depends on presence or
absence of Iwa.

Iwa Last word address plus 1 of memory to be dumped; Iwa is

relative to RA. If Iwa alone is present, DMP assumes
fwa=0. If neither fwa nor Iwa is present, DMP dumps the
exchange package and 4O3 locations before and after the
program address register in the exchange package.

The DMP routine dumps on file OUTPUT central memory according to the DMP call
parameters in four words per line. If lines are duplicated, they are suppressed with
the following notation.

DUPLICATE LINES.

The DMP card must immediately follow the program to be dumped. No control card
other than EXIT card may intervene.

60407000 D 1-9-1

Dumping will always stop at FL if Iwa > FL. If a DMP control card image is entered
under the batch subsystem from a time-sharing terminal, the dump will be formatted for
72-column output. If either fwa or Iwa is nonnumeric, the request is interpreted as

DMP.

If fwa > FL, fwa is set to FL-lOg. If both fwa and Iwa > FL, fwa is set- to FL-lOg
and Iwa is set to FL. If fwa=lwa, the system adds lOs to Iwa and proceeds with the
operation. If fwa > 4000008, the first dump address is fwa-4000008, memory from
the first dump address through Iwa is dumped, and the job is aborted. If fwa > Iwa,
the system issues the following miessage to the user's dayfile.

DUMP FWA.GE. LWA+1.

DMD CARD

The DMD control card requests a dump similar to that of the DMP card but additionally
contains the display code equivalences to the right of the octal representations.

The control card format is:

DMD(fwa,lwa) or

DMD (Iwa) or

DMD.

fwa First word address of memory to be dumped; fwa is relative

to RA. If fwa is absent, dump mode depends on presence
or absence of Iwa.

Iwa Last word address plus 1 of naemory to be dumped; Iwa is

relative to RA. If Iwa alone is present, DMD assumes
fwa=0. If neither fwa nor Iwa is present, DMD dumps the
exchange package and 40g locations before and after the
program address in the exchange package.

The user should not enter the DMD card image from a time-sharing terminal; the data
transmitted for the display code equivalences may cause the terminal to be disconnected.

LBC CARD

The LBC control card is intended for loading binary data of unknown format.

The control card format is:

LBC(addr)

addr Address relative to RA at which binary load begins; if

addr is omitted, (RA) is assumed.

LBC reads only one record from file INPUT. The user must make an LBC call for each
record of data to be loaded. If addr is specified in the program call, binary data is loaded
beginning at that address; otherwise, loading begins at the reference address (RA).

1-9-2 60407000 D

The following messages may be Issued to the user's dayfile in response to an LBC
card.

LBC ARGUMENT ERROR. The load address, addr, is not numeric.

LBC FWA .GE.FL. The load address is greater than or equal

to the user's field length.

RECORD TOO LONG. The record is too long fof available memory.

Available memory is filled and the excess
data is skipped.

LOC CARD

The LOC control card calls the LOC program and specifies address parameters used by
LOC to read octal card images from file INPUT and enter them in CM.

The control card format is:

LOC(fwa,lwa)

LOC(lwa)

LOC.

fwa

First word address of an area to clear (zero) before loading
correction cards. If fwa is absent, LOC assumes 0.

Iwa Last word address plus 1 of the area to be cleared. If

Iwa is absent, LOC assumes 0.

The correction card images consist of octal address and data fields. The address field
specifies the location to be corrected, and the data field contains the data to be placed in
that location. Both fields may start at any column as long as the address precedes the
data. The address field consists of a one- to six-digit address. If it is five characters or
less, it is separated from the data field by a nonoctal character (for exsunple. a blank).
If it is six characters, no separator is required.

The data field consists of 1 to 20 octal chracters. If it is less than 20 characters, it

is terminated by a nonblank, nonoctal character and is stored right -justified. If it is

20 characters, no terminator is required. Embedded blanks in the data field are ignored

The following messages miay be issued to the user's dayfile.

LOC ARGUMENT ERROR. The fwa or Iwa parameter is not numeric.

LOC RANGE ERROR. Either fwa > Iwa or Iwa > FL.

ADDRESS OUT OF RANGE, The address aaaaaa on a correction card is

aaaaaa. greater than or equal to the user's field length.

The correction card is ignored and LOC continues.

If both addresses are specified and both are nonzero, storage is cleared from fwa to
Iwa and the octal line images are loaded at the specified addresses. LOC can be called
to clear storage by providing an empty (zero-filled) record on file INPUT.

60407000 D 1-9-3

PBC CARD

The PBC routine writes one record from the specified area of CM to file PUNCHB.
The control card format is:

PBC(fwa,lwa)

PBCdwa)

PBC.

fwa

Iwa

or
or

Address relative to RA at which the binary deck begins; if this
parameter is omitted, the PBC operation depends upon the
presence or absence of Iwa.

Last word address plus 1 of the binary deck. If Iwa alone
is present, PBC assumes that fwa=RA. If lwa=fwa, and a
nonzero value is specified. PBC adds 10-, to Iwa. If fwa
and lwa = or are omitted, RA contains Iwa in the lower 18
bits. If the upper 12 bits of RA are 7700j,, Iwa is the lower
18 bits of the location following the prefix (77) table plus the
length of the prefix table.

CM is not altered by PBC.

The following messages may be issued to the user's dayfile.

PBC ARGUMENT ERROR. Either fwa or Iwa is nonnumeric.

The fwa parameter is greater than Iwa.

PBC FWA .GT.LWA.
PBC RANGE ERROR.

The }wa parameter is greater than or equal
to the user's field length.

RBR CARD

The RBR routine loads one binary record from a specified file.

The control card format is:

RBR(n,name)
n

name

n is used in constructing the name of the file containing
the binary record to be read. If n is less than four char-
acters and is numeric, TAPEn is the file name. If n
contains a nonnumeric character or is four or more char-
acters long, then n itself is used as the file name. If n
is absent, TAPE is the file name.

A 1- to 7-character name used in a record prefix.

1-9-4

60407000 D

The RBR routine loads one binary record from the specified file,
is included, a record prefix is placed in memory starting at RA.
follows. The following is the format of the record prefix.

RA
RA+1
RA+2
RA+3

If the name parameter
The record itself

47 35

0016

length

name

date (yy/mm/dd. )

5200

length 1

RA+1 7
RA+20g

length Record length including the prefix

lengthi Record length minus words RA through RA+178

If the record is too long for available memory, memory is filled, excess data is skipped,
and the following message is issued to the user's dayfile.

RECORD TOO LONG.

WBR CARD

The WBR routine writes a binary record from CM to a file at its current position.
The control card format is:

WBR(n.rl)

n is used in constructing the name of the file on which the
binary record is to be written. If n is less than four
characters and is numeric, TAPEn is the file name. If
n contains a nonnumeric character or is four or more
characters long, then n itself is used as the file name.
If n is absent. TAPE is the file name.

Record length in words. If rl is or absent, the length
is taken from the lower 18 bits of RA.

WBR begins writing from I^A.

The following messages may be issued to the user's dayfile.

WBR ARGUMENT ERROR. The rl parameter is nonnumeric.

RECORD TOO LONG. The rl parameter is greater than or equal to

the user's field length.

60407000 D

1-9-5

TAPE MANAGEMENT

This section is devoted primarily to the control cards necessary to create and manage
files on magnetic tape. Following the control cards are descriptions of the various
types of tape formats available to the user.

The control cards described in this section are:

ASSIGN
BLANK
LABEL

LISTLB
REQUEST

VSN

The ASSIGN, LABEL, and REQUEST control cards cause files to be assigned to tape
units or devices. The REQUEST card requires operator action unless the VSN is
specified. In this case, if the tape has already been mounted, assignment is automatic
LABEL and ASSIGN also cause automatic assignment.

ANSI tape labels can be read using the LISTLB card and blank labeled for installation
control using the BLANK card.

The control cards available to the user for assigning a file to magnetic tape are also
used to create new and access existing 7- and 9-track labeled and unlabeled tapes.
The following terms are used in describing these cards.

Volume

Volume serial number

Block

Reel of magnetic tape

Number that uniquely identifies a reel of tape

One physical record unit (PRU); that is. a group of
contiguous characters recorded on and read from
magnetic tape as a unit.

Noise
Label

Tape mark
Owner

KRONOS 2. 1
written tape

Any block less than the minimum acceptable block size
is considered noise and discarded by the system.

Field of characters that identifies and/or delimits a
volume or file. Labels may be written in ANSI standard
or nonstandard format. ANSI labels are 80-character
blocks recorded at the beginning of a volume (VOLl),
the beginning of a file (HDRl), the end of a file (EOFl),
and the end of a volume (EOVl). Labels which do not
conform to ANSI standards in format and /or content
are defined as nonstandard.

Special configuration recorded on magnetic tape indicating
the boundary between files and /or labels

Owner of a KRONOS 2. 1 written tape identified in the
VOLl label by the combination of his family name and
user number

Tape with ANSI labels written by KRONOS 2. 1 and
identified as such in the system code field of each
HDRl, EOFl, and EOVl label

60407000 D

1-10-1

The format and contents of ANSI labels are described in appendix G. A RESOURC
control card must be included in any job that uses two or more tape units concurrently.

The following is a list of the parameters that may appear on one or more of the
tape mianagement control cards.

Keyword

Parameter Default

Valid on

Installation
parameter

ASSIGN
REQUEST

Installation
parameter

ASSIGN
REQUEST

Installation
parameter

ASSIGN
REQUEST

Installation
parameter

ASSIGN
REQUEST

Installation
parameter

ASSIGN
REQUEST

den Installation
parameter

ASSIGN
BLANK
LABEL
LISTLB

REQUEST

Description

200 -bpi tape density (implies
7-track tape)

556-bpi tape density (implies
7-track tape)

800-bpi tape density (implies
7-track tape)

800- cpi tape density (implies
9-track tape)

1600-cpi tape density (implies
9-track tape)

Specifies tape density:

LO
HI
HY
HD
PE
200
556
800
1600

200 bpi (7-track)

556 bpi (7-track)

800 bpi (7-track)

800 cpi (9-track)
1600 cpi (9-track)

200 bpi (7-track)

556 bpi (7-track)

800 bpi (7- or 9-track)
1600 cpi (9-track)

1-10-2

60407000 D

Keyword
FC =

Parameter
fcount

Default
None

Valid On Description

ASSIGN Frame count. Specifies the

LABEL maximum size block (in frames)

REQUEST that may be read or written.

This parameter applies only

to E, B, and F data formats

(refer to the F keyword ).

ccount

None

ASSIGN
REQUEST

CV =
or

N =

conv

PO^

P1P2- • • P

Installation
parameter

• • ' fn

Installation
parameter

Installation

parameter

A (nonsystem

origin jobs)

AU (system origin

jobs)

ASSIGN
LABEL

REQUEST

ASSIGN
BLANK
LABEL
LISTLB
REQUEST

ASSIGN
BLANK
LABEL
LISTLB

REQUEST

ASSIGN

LABEL

requp:st

Character count. Specifies
the maximum size block (in
6 -bit characters) that may
be read or written. This
parameter applies only to E,
B, and F data formats (refer
to the F keyword).

Specifies the conversiont mode
for 9-track tapes:

AS ASCII/display code

conversion
US Same as for AS
EB EBCDIC /display code

conversion

Specified file resides on or
is to reside on 7-track tape

Specified file resides on or
is to reside on 9-track tape

A string of characters
specifying processing options:

A Job will be automatically
aborted on an irrecover-
able read or write parity
error.

N Job will not be aborted
if an irrecoverable read
or write parity error
occurs; on a read opera-
tion, data will be passed
to the program.

R Enforce ring out. If the
tape is mounted with the
write ring in, job pro-
cessing will be suspended
until the operator re-
mounts the tape correct-
ly.

t Refer to appendix A for the character sets showing translation between display code
and ASCII (USA SI) and display code and EBCDIC.

60407000 D

1-10-3

Keyword

Parameter

Default

Valid On Description

W Enforce ring in. If the

tape is mounted without
the write ring in, job
processing will be sus-
pended until the operator
remounts the tape cor-
rectly.

U Inhibit unload. Do not

unload at the end of usage.
For system origin jobs,
the inhibit unload option
is selected by default;
for all other origin type
jobs, omission of the U
option causes the tape to
be unloaded at end of
usage.

F Force unload. Unload

at the end of usage.
This option is useful
for system origin jobs
where otherwise U (in-
hibit unload) would be
the default.

E Error inhibit. All hard-

ware read/write errors
are ignored and proces-
sing continues. The sys-
tem does not attempt
error recovery, issue
error messages, nor re-
turn error status. This
option is not intended for
the normal user. How-
ever, it can be used to
recover portions of data
from a bad tape, for
hardware checkout pur-
poses, and to write on
tape without skipping bad
spots; in the latter case,
the user is responsible
for verifying that the data
was written correctly.

B Directs the system to

write system noise
blocks when perform-
ing write error re-
covery. This option is
ignored for 1600-bpi
tapes. In addition, this
option should not be used
for tapes which are to
be interchanged with
other systems.

1-10-4

60407000 D

Keyword

Parameter

Default

Valid On

Description

format

NS=

I format for LABEL
card.

I format for AS-
SIGN card if VSN
keyword is included;
otherwise, default
is X format.
I format for RE-
QUEST card if VSN
keyword is included
or VSN control
card has been pro-
cessed; otherwise,
default is X format.

For all data for-
mats except I, SI,
and X, the default
for ns is 18 frames.
The NS keyword
should not be speci-
fied for I, SI, and
X format tapes be-
cause the definition
of noise block size
is implied by the for-
mat. (Refer to the
K keyword. )

ASSIGN
LABEL

REQUEST

ASSIGN
LABEL
REQUEST

I Directs the system to ig-
nore the block being read
when the EOT is encoun-
tered, t

P Directs the system to
accept the block being
read when the EOT is
encountered. '

S Specifies where the

system is to stop on an
exit condition. For
unlabeled tape, it directs
the system to stop at the
first tape mark after the
EOT is sensed. For
labeled tape, it directs
the system to stop at the
tape mark plus EOFl or
the tape mark plus EOVl
when the EOT is encoun-
tered.

Specifies the data format

Internal

External

Blocked

E
S
L

Line image

SCOPE stranger tape

SCOPE long block

stranger tape
SCOPE internal

Foreign

Noise size. Any block con-
taining fewer than ns frames
is considered noise and dis-
carded by the systemi; the
maximum value of ns is 31 ^q
frame. If a noise size of
zero is specified, the default
noise size is used.

t For further information, refer to End-Of-Tape/End-Of-Reel Processing in section 10.

60407000 D

1-10-5

Keyword

Parameter

Default

Valid On

Des(2ription

LB=

VSN=

vsn

KL for LABEL
card.

KL for ASSIGN card
if VSN keinvord is
included; otherwise,
default Is KU.
KL for REQUEST
card if VSN keyword
is included or VSN
control card has
been processed;
otherwise, default
is KU.

Refer to
appendix G.

ASSIGN Specifies whether the tape is

LABEL to be treated as labeled or un-

REQUEST labeled.

KU KRONOS unlabeled.

KL KRONOS labeled. The
tape is treated as hav-
ing ANSI labels. If the
tape is a KRONOS 2. 1
tape, volume and head-
er accessibility re-
strictions will be en-
forced.

NS Nonstandard labels.
The system skips over
labels based on tape
marks but does not
process the labels.
This option can also be
used in processing a
non KRONOS tape which
although designated as
unlabeled contains a
tape mark prior to the
beginning of data.

ASSIGN A 1- to 6 -character volume

BLANK serial number that uniquely

LABEL identifies a reel of tape (refer

REQUEST to the VSN control card).

FI=
or
L =

fileid

Refer to
REQUEST card.

Refer to
appendix G.

ASSIGN
LABEL
REQUEST

LABEL

Specifies that Ifn is to be used
as a checkpoint f Ue. Each time
a checkpoint dump is taken,
the new information is written
at the previous EOI of Ifn.

Specifies that Ifn is to be used
as a checkpoint file. Each
time a checkpoint dump is
taken, the new information is
written at the BOI of Ifn.

A 1- to 17-character file
identifier recorded in HDRl.

1-10-6

60407000 D

Keyword Parameter Default

Valid On

Description

FA =

Unlimited access

OFS=

Unlimited access

BLANK File accessibility. One char-

LABEL acter that indicates who has

access to the labeled file (refer
to appendix G, HDRl label).

A Only the owner of the

KRONOS 2, 1 written
tape can access the
file.

omitted FA omitted indicates
unlimited access.

other All future accesses

to this tape must
specify this character
as the fa parameter.

File accessibility is not
checked for system origin
jobs.

BLANK One character that indicates

the current file accessibility
of a labeled tape which is to
be blank labeled. (Refer to
FA description for explana-
tion of fa characters. )

SI=
or

M =

setid

Refer to
appendix G.

LABEL
LISTLB

SN =
or
V =

secno

Refer to
appendix G.

LABEL

QN =
or
P =

seqno

Refer to
appendix G.

LABEL
LISTLB

genno

Refer to
appendix G.

LABEL

E =

gvn

Refer to
appendix G.

LABEL

CR =

cdate

Current date

LABEL

or
C =

RT =

rdate

Current date

LABEL

1- to 6-character set identi-
fier for a multifile set (refer
to appendix G, HDRl label).

1- to 4-digit file section num-
ber (refer to appendix G, HDRl
label).

1- to 4-digit file sequence
number (refer to appendix G,
HDRl label).

1- to 4-digit generation
number (refer to appendix G,
HDRl label).

1- to 2 -digit generation version
number (refer to appendix G,
HDRl label).

Creation date in the form
yyddd where 1 < ddd <:366.
Creation date is meaningful
only on read operations;
on write operations, the
current date is always used.
(Refer to appendix G, HDRl
label).

Retention date in the form
yyddd (used to derive expira-
tion date described in appendix
G, HDRl label).

60407000 D

1-10-7

Keyword
T =

Parameter
ret cycle

Default

Refer to
appendix G.

Valid On
LABEL

LABEL

VA =

Unlimited access

BLANK

Description

1- to 3 -digit retention cycle
specifying the number of days
from the current date that the
file is to be retained (used to
derive the expiration date if
the RT keyword is not speci-
fied. Refer to appendix G,
HDRl label).

Directs the system to read the
existing ANSI label. The para-
meters on the LABEL card are
compared with the values re-
corded on the file labels. If
the comparison fails, the job
is aborted.

Directs the system to write
standard ANSI labels using the
parameters specified on the
LABEL card or their default
values. It is not necessary to
specify the PO=W option to
enforce ring in. If the tape is
mounted without the write ring,
job processing is suspended
until the operator remounts
the tape correctly. However,
if the PO=R option is specified,
the job is aborted.

Volume accessibility. One
character that indicates re-
strictions on who may have
access to information on the
reel (refer to appendix G,
VOLl label).

omitted VA omitted indi-
cates unlimited
access.

other Whenever this

reel is processed
under KRONOS as
a KRONOS 2. 1
labeled tape
(LB=KL), volume
accessibility re-
strictions are im-
posed. Thus, the
user cannot change
or destroy the
VOLl label on the
tape. This feature
enables an install-
ation to BLANK
label new tapes
and be assured
that the volume
serial number
field of VOLl
cannot be changed
by a user. If VA
is nonblank, only
a system origin
job can change
VOLl.

1-10-8

60407000 D

Keyword
OWNER =

LSL =

Parameter

usernum/
familyname

Isl

Default

Refer to
appendix G.

The labels and data
format of the speci-
fied volume require
the agreement of the
interchange parties.

Valid On
BLANK

BLANK

LO =

Itype

LISTLB

L =
U =

out

OUTPUT

LISTLB
BLANK

Description

Identifies the owner of the
KRONOS 2. 1 labeled tape (refer
to appendix G, VOLl label).

Label standard level (refer to
appendix G, VOLl label).

1 The labels and data

format of this volume
conform to the re-
quirements of the
ANSI standard.

blank LSL omitted indicates
that the labels and
data format of the
specified volume re-
quire the agreement
of the interchange
parties.

Specifies the type of labels to
be listed (refer to appendix G).

A List all required and

optional ANSI labels.

R List all required labels
(VOLl, HDRl. EOFl,
and if present, EOVl)

O List all optional

labels (VOL2-9,
HDR2-9, EOF2-9,
EOV2-9, UVLl-9.
UHLa, and UTLa)

List all VOLl-9
labels.

List all HRDl-9
labels.

List all EOF 1-9
labels.

List all EOVl-9
labels.

List all UVLl-9,
UHLa, and UTLa
labels.

Specifies the file on which the
labels are to be listed.

Unload tape after blank label-
ing it; tape is always returned
after blank labeling.

60407000 D

1-10-9

The system allows continuation cards for ASSIGN,. BLANK. LABEL, REQUEST, and VSN
cards that require more than 80 characters. If, in processing one of these cards, the
system does not encounter a termination character prior to the end of the line, it
assumes the next line is a continuation line. All continuation lines must contain a
blank in column 1.

NOTE

The system accepts continuation lines from
a time-sharing terminal only if they are con-
tained in procedure files.

The programimer can use a literal for any parameter on a tape management control
card that contains nonalphanumeric characters. Characters other than letters, numbers,
and asterisks are defined as nonalphanumeric. A literal is a character string delimited
by dollar signs. Blanks within literals are retained. If the literal is to contain a
dollar sign, two consecutive dollar signs must be included. Thus, the literal

$A B$$41$

is interpreted as:

A B$41

If continuation cards are used, a literal cannot extend from one card to another.

Generally, if more than one parameter of a given type is specified, the last one en-
countered in a left-to-right scan is used. The two exceptions to this rule are in the
processing option parameters. If both ring enforcement options (PO=R and PO=W) or
more than one EOT option (PO=I, PO=P, PO=S) is specified, the ARGUMENT ERROR
message is issued to the user's dayfile.

1-10-10 60407000 D

ASSIGN CARD

The ASSIGN control card can be used to create new and access existing 7- or 9-track
unlabeled tapes.

The control card format is:

ASSIGN(nn, lfn.D= den. {FC=f count j (^y^^onv, I^tI po==p,p„. . . p„.

\. C=ccount) [ NT j i ^ n

F=forniat, NS=ns, LB=1, VSN=vsn, j^^j

nn Device or device type to which the specified file is to be assigned;

nn may be either the EST ordinal t of a magnetic tape unit or one
of the device types MT or NT. MT is defined as a 7-track mag-
netic tape drive; NT is a 9-track magnetic tape drive.

Ifn Name of the file to be assigned to the specified equipment.

Although the user can also Include this card to assign a labeled tape to his job, he
cannot use it to create or verify tape labels. It is suggested that the user include
LABEL cards for all tapes whenever possible.

The job must be of system origin or the user must be validated for system origin

privileges. The user must also be validated for use of magnetic tapes, ft If 'the user

attempts to perform an assignment for which he is not validated, the job is aborted
and the following message is issued to the user's dayfile.

ILLEGAL USER ACCESS.

Before performing the assignment, the system issues a RETURN on Ifn.
Example:

ASSIGN(51, TAPED

This card assigns the file TAPEl to the magnetic tape unit identified by EST ordinal
51.

t Contact installation personnel for a list of EST ordinals,
tt Refer to LIMITS control statement, section 6.

60407000 D l-lO-ll

BLANK CARD

The control card format is:
I BLANK(D=den. | J^J" } , VSN=vsn, FA=fa, OFA=ofa„ VA=va, OWNER=usernum/famllyname,

LSL=lsl,U)

With the BLANK control card, an installation can establish control over the use of
labeled tapes. The values supplied on the card are used to blank label a tape with
standard ANSI volume header (VOLl), first file header (HDRl), and first end-of-file
(EOFl) labels. The labels are written as follows:

VOLl

HDRl

EOFl

In writing these labels, the system uses default values for all fields except those fields
for which there are corresponding parameters on the BLANK card. The VA and FA
keywords can be used to restrict access to information on the reel and the specified
files, respectively. If the tape to be blank labeled is a labeled tape which has a file
accessibility other than A, this old file accessibility must be specified by the OFA
parameter. When the tape is blank labeled, the file accessibility is that specified
by the FA parameter. The default track type may be set by the installation to either
MT or NT. t If a track type other than the default is desired, it must be specified.

Once a tape has been blank labeled, the user can modify the labels as follows:

1. If the volume accessibility field of VOLl indicates unlimited access (that is,
VA is blank), the user can:

• Include another BLANK card to change VOLl, HDRl, or EOFl values.

• Request the tape as unlabeled (that is, LB=KU) and write it in whatever
format he specifies.

• Include a LABEL card to change HDRl by specifying one or more of the
parameters associated with that label and selecting the write label (W)
option.

2. If the volume accessibility field is nonblank, the user can:

• Include a LABEL card to change HDRl. However, in requesting a tape
in which VA is nonblank, the user must specify an NOS labeled tape
(that is, LB=KL), and therefore, cannot change or destroy the VOLl
label.

• Submit a system origin job to change VOLl.

t Contact installation personnel for the default track type.

1-10-12

60407000 D

LABEL CARD

LABELdfn, D=den, FC=fcount,CV=conv,|jJ,j^|,PO=piP2. . .p^. F=format.NS=ns.

LB=f . VSN=vsn. { ^^|. { ^,^=^"^!^1 . FA=fa. { ?f ^^"^1 . 1 SN=secno» .
* ICBI I L=fileidf • • l]Vl=setidJ I v=secnor

I '*^S=^®^"°l.G=genno. E=gvn, | CR=cdate \ , (RT=rdate \ , / Wl x
\ P=seqnof « • K .| c=cdate I V T=retcycle T 1 R P

Ifn Name of the file that resides on or is to reside on magnetic

tape

The LABEL control card directs the system to assign file Ifn to a tape unit. This
assignment occurs using VSN only; the file identifier is not considered in assigning.
If a file by the name Ifn silready exists, the following action is taken.

1. If Ifn is assigned to a device other than a tape unit, job processing continues
with the next control card.

2. If Ifn is an existing tape file and the read label (R) parameter is specified,
the system compares the parameters on the LABEL card with the values re-
corded on the file labels. If the comparison fails, the job is aborted.

3. If Ifn is an existing tape file and the write label (W) parameter is specified, the
system compares the vsn specified on the LABEL or VSN card with the vsn in
the VOLl label. If the vsns match, the system writes file labels (refer to
appendix G) using the parameters specified on the LABEL card. If the vsns

do not match, the job is aborted.

To assign to tape an ifn that was previously assigned in the same job to another device,
the user must make sure that Ifn Is RETURNed before the LABEL card is processed.
Note that the default track type may be set by the installation to either MT or NT. f I

If a track type other than the default is desired, it must be specified. |

If Ifn is to be used for checkpoint dumps and the dumps are to be written on labeled tape,
the CK or CB parameter must be included on the LABEL card. For further information
about checkpoint dumps, refer to the REQUEST control card.

Example 1 :

LABEL (NEWFILE,VSN=TP01,FI=FILEA,W)

This card creates an ANSI-labeled tape which the job can access by the filename NEWFILE.
Default values are used for all fields of HDRl except the file identification, FILEA,
Any data written is recorded in 512 CM word blocks.

Example 2:

LABEL(OLDFILE,VSN=TP01,FI=FILEA)

This card assigns the tape file created in a previous job (refer to example 1) to the file
OLDFILE. The system compares the vsn in VOLl and the file identification in HDRl
with the values on the card.

Example 3:

LABEL(CFILE, VSN=TP02, FI=THIRDFILE, SI=ABCD, QN = 0003)

This card assigns the tape with vsn TP02 to the file CFILE. The system positions the tape to
the beginning of data of THIRDFILE. the third file in the multifile set ABCD.

tContact installation personnel for the default track type.
60407000 D 1-10-13

LISTLB CARD

The control card format is:

LISTLB (lf„. |g:n!i^)'(''?:IX I • LO=I.yp.,L=ou..

The LISTLB control card directs the system to read the ANSI labels on the tape file speci-
fied by Ifn and write them on the user specified file out. The setid and seqno parameters
enable the user to list only those HDRl-9 and EOFl-9 labels which have the specified
multifile set identifier a'..d/or file sequence number. The Itype parameter allows the
user to specify the type of labels to be listed. Refer to appendix G for a description
of each type of label.

REQUEST CARD

The REQUEST control card enables the user to assign a file to a device by including
in the comment field a description of an acceptable device.

The control card format is:

REQUESTafn,D=den.|FC:=fcount I cv=convJMTl PO=p,,p„. . .p .

\ C=ccountJ I NT J i^ ^ i^

F=format, NS=ns, LB=ie , VSN=vsn, j^^j )

This comment is displayed at the system console, directing the operator to make the
requested assignment. If the user has previously specified a vsn via a VSN control
card or if he has Included the VSN keyword on the REX5UEST card, the system initiates
automatic tape file assignment.

The REQUEST card can be used to create new and access existing 7- or 9-track un-
labeled tapes. Although the user can also include this card to assign a labeled tape
to his job, he cannot use it to create or verify tape labels. It is suggested that
LABEL cards be used for all tapes whenever possible., The default track type may be
set by installation of either MT or NT. t If a track type other than the default is
desired, it must be specified.

If Ifn is to be used for checkpoint dumps, either the CK or CB keyword is specified.
These keywords are used in conjunction with the CKP and RESTART control cards;
they allow the user to:

• Save all checkpoint dumips by appending each dump to the checkpoint file
REQUEST(lfn,CK)

tContact installation personnel for the default track type.

1-10-14 60407000 D

• Save the last checkpoint dump by writing each dump at the beginning of the
checkpoint file

REQUESTdfn.CB)

• Save two consecutive checkpoint dumps by alternately writing on two check-
point files:

REQUESTdfhi, CB)

REQUEST (Ifng, CB)

If the CK parameter is specified for alternate files or if more than two checkpoint files
are specified, the job is aborted and the following message is issued to the user's day-
file,

CHECKPOINT FILE ERROR.

The user is not required to supply a REQUEST card to define a checkpoint file,
can use an ASSIGN or LABEL card or he can use default values.

If no REQUEST card specifying a checkpoint file has been detected when the first CKP
card is encountered, the system requests a device for the user, specifies a file name
of CCCCCCC, and selects the CK option. For a subsequent restart job, however, the
system assumes the user has made the checkpoint file available.

VSN CARD

The control card format is:

VSN(lfn2=vsnj.lfn2=vsn2,

, lfnn=vsn^)

Ifn,

vsn;

Name of the file with which the specified vsn is to be
associated

1- to 6-character volume serial number to be associated
with Ifnj. If the vsn^ is zero, absent, or SCRATCH, any
available scratch tape will be automatically assigned to Ifn^.
If characters other than letters and numbers are used,
vsn^ must be specified as a literal.

60435400 A

1-10-15

The system allows tape assignment to be performed either by the system or by the
operator. By supplying a vsn uniquely identifying every tape (labeled, unlabeled, and
nonstandard labeled), the user enables the system to assign tapes without operator intervention.

A vsn is provided via the VSN keyword on a LABEL or REQUEST card or via a VSN
card. With a VSN card the user can:

• Omit the VSN keyword from his LABEL or REQUEST cards and specify
Ifn/vsn associations on the VSN card Instead. This allows the user to
specify new vsns without changing LABEL or REQUP;:ST cards.

• Override the vsn specified on subsequent ASSIGN, LABEL, REQUEST, or
VSN cards. For example, the sequence:

VSN(FILEA = 123)

VSN(FILEA = 124)

LABEL(FILEA)

directs the system to assign FILEA to the tape with vsn 123. However,
the user can redeclare an Ifn/vsn association by returning the file. Thus,
the following sequence

VSN(FILEA = 123)

RETURN(FILEA)

VSN(F1LEA = 124)

LABEL(FILEA)

directs the system to assign to FILEA the tape with vsn 124.

• Associate the vsns of two or more duplicate reels with one flle.t If any
of several duplicate reels can be used (that Is, they differ only In vsns),
the vsns should be separated by equal signs. Thus, the card

VSN(FILE1=VOL100=VOL101)

Indicates that either the tape with the vsn of VOL 100 or the tape with the
vsn of VOLlOl can be assigned to FILEl.

• Specify the vsns of a multireel flle.t If the file extends to more than one
reel, the vsns for all reels required must be separated by slashes.

The system assigns the reels In the order Indicated on the card. For ex-
ample, the card

VSN(FILE2=VSN23/VSN24/VSN25)

Indicates that FILE2 may extend to the three reels identified by the vsns of
VSN23, VSN24, and VSN25.

The system processes tape requests as follows:

1. Whenever a tape is mounted, the system checks for labels. If the tape was
labeled, the system keeps a record of the vsn read from VOLl and the equip-
ment on which the tape Is mounted.

t Up to 55 vsns can be specified for a single file in any combination of duplicate reel
and/or multireel configurations.

1-10-16 60407000 D

2. If, when a request is made for tape assignment, an Ifn/vsn association is en-
countered, the system compares the vsn associated with the file (or one of its
equivalences) with the vsns read from mounted tapes. If a match is found, the
system automatically assigns the tape to the requesting job, provided a deadlock
would not occur. If the tape is not mounted, the system rolls out the job until

a tape with the required vsn is mounted. For a mounted, unlabeled tape, the
operator enters a VSN command specifying the required vsn. The system is
then able to automatically assign the tape.

3. If no Ifn/vsn association is encountered when the request is made, the system
directs the operator to assign an available unit.

4. For an ASSIGN card, the method of assignment depends on the nn parameter.
If nn is a device type (MT or NT), the operator must assign an available
unit. If nn is the EST ordinal of a tape unit, the system automatically
assigns the specified unit.

The following is a summary of the system and/or operator action taken in response to
an ASSIGN, LABEL, or REQUEST card. The VSN column indicates whether or not the
user has specified an Ifn/vsn association via the VSN keyword or a VSN card. The
mode column shows the mode as determined by the system in checking for labels.

Card
ASSIGN

VSN
Yes

Mode
Labeled

REQUEST

LABEL

Yes

Unlabeled

Labeled

Unlabeled

Yes

Labeled

Yes

Unlabeled

Labeled

Unlabeled

Yes

Labeled

Yes

Unlabeled

Labeled

Unlabeled

Action

If the nn parameter is MT or NT, the operator
must assign an available unit. If the nn para-
meter is the EST ordinal of a tape unit, assign-
ment is automatic.

Same as when the vsn is specified and the tape
is labeled.

The system matches the vsn read from VOLl
with the vsn on the REQUEST or VSN card.
Assignment is automatic.

The operator enters a VSN command specifying
the vsn included on the REQUEST or VSN card.t
Assignment is automatic.

The operator assigns an available unit to Ifn.

The system matches the vsn read from VOLl
with the vsn on the LABEL or VSN card.
Assignment is automatic.

The operator enters a VSN command specifying
the vsn included on the LABEL or VSN card, f
Assignment is automatic.

The operator assigns an available unit to Ifn.

The LB keyword is not used in assigning a tape. Rather, it is used in processing the data
on the tape once the assignment has been made.

tA VSN which contains special characters should not be specified in a request for an
unlabeled tape. It is not possible to enter special characters via the VSN, xx, aaaaaa.
operator conamand.

60407000 D

1-10-17

MAGNETIC TAPE FORMATS

The standard magnetic tapes used are 7 -track, 1/2-inch tape and 9 -track, 1/2 -inch
tape. Each type of tape can be written in binary or coded mode. Unless specified
otherwise, tapes are assumed to be in binary mode. The user can select 200, 556,
or 800 bits per inch (bpi) density for 7-track tapes or 800 or 1600 characters per
inch (cpi) density for 9-track tapes, provided these densities are available with the
hardware. Tape density can be specified by a LABEL, ASSIGN, or REXJUEST control
card, the LABEL macro (refer to section 4, volume 2), or an IPRDECK installation
option (refer to the Installation Handbook). The system normally performs automatic
processing of tape parity errors and end-of-tape conditions. However, the user can
control the processing of these functions via the PO keyword on LABEL, ASSIGN, and
REQUEST control cards or the po field of the FET (FET+8,, bits 36 thirough 47).

DATA FORMATS

Data can be recorded on magnetic tape in any of eight formats.

Format

Description

Internal

SCOPE internal

External

SCOPE stranger

SCOPE long block stranger

Line image

Blocked

Foreign

1-10-18 60407000 D

The control card user specifies the data format via the F keyword of a LABEL, ASSIGN,
or REQUEST control card. The LABEL macro user specifies the data format via
FET + 10, bits 30 through 35. The following is a description of the physical and logical
characteristics of each format. Note that the user can define maximum block size,
end-of-reel conditions, and noise for any format via control card or FET parameters;
the following description of these characteristics defines the suggested (and default)
values.

I (INTERNAL) FORMAT

Characteristics

Mode

Block size (PRU size)

Logical end-of-record

Logical end-of-file

Logical end -of- information

t Refer to appendix G.

60407000 D

Description

Binary

Actual data block size can range from to 512
(lOOOo) CM words in exact multiples of CM words.
All blocks except those containing labels include
a 48-bit block terminator formatted as follows:

byte count

block number

i„

byte count

block number
In

Total number of bytes in the
block including the block
terminator

Number of blocks since the
last HDRl label t

Level number

End-of-record
End-of-file

User-specified frame or character counts have no
m^eaning.

Any block with fewer than 512 (lOOOg) CM words
of data is considered a logical end-of-record.
During a write operation, the level number field of
the block terminator contains the level number
obtained from FET+0, bits 14 through 17, or the
WRITECW macro control word. During read op-
erations, the systena will return end-of-record
status and the contents of the block terminator level
number field. If the level number is 17g, the
system will also return end-of-file status. Some
blocks may consist only of a block terminator.

Any block consisting of only a block terminator with
a level number of 17g is considered a logical end-
of-file. The system ensures that an end-of-record
will always precede an end-of-flle by writing. If
necessary, a block terminator with a level number
of zero prior to the end of file.

If the tape Is unlabeled, there Is no logical end-of-
Informatlon. For labeled tapes, a tape mark followed
by an EOFl label Is considered the end-of-lnformation.
The system issues a label content error if it
encounters a tape mark without a valid label following
It.

1-10-19

Characteristics
End-of-reel

Noise

Special considerations

Desc ription

Refer to option 3 under End-Of-Tape/End-Of-Reel
Conditions .

Any block containing fewer than eight frames for
7-track tapes or six frames for 9-track tapes is
considered noise, and therefore,, ignored.

All 9-track tapes are written in an even multiple of
bytes.

On all read operations, the system checks for fill
status and compares the number of bytes read and
the block number expected with the byte count and
block number values in the block terminator. If
the specified condition does not occur, the system
handles it as if it were a parity error. This method
is designed to prevent dropped or fragmented blocks;
in general, it provides a much higher degree of
reliability than any other format.

S (SCOPE INTERNAL) FORMAT

Characteristics

Mode

Block size (PRU size)

Desc ription

Binary or coded as indicated by FFJT+0, bit 1.

For binary mode, the block size can range from
to 512 (IOOO3) CM words in exact multiples of CM
words. Any block smaller than the maximum size
except those containing labels will contain a 48-bit
block terminator. This terminator has the same
format as that for I format. For coded mode, the
block size can range from to 128 (200g) CM words
in exact multiples of CM words. Any block smaller
than the maximum size except those containing labels
will contain a 48-bit block terminator formatted as
follow s :

blanks

In Blank if level is

1 through 17g for all other levels

User-specified frame or character counts have no
meaning.

1-10-20

60407000 D

Characteristics
Logical end-of-record

Logical end-of-file
Logical end-of -information
End-of-reel

Noise

Special considerations

X (EXTERNAL) FORMAT

Characteristics

Mode

Block size (PRU size)

Logical end-of-record

Desc ription

For binary mode, any block containing fewer than
512 (lOOOo) CM words represents a logical end-of-
record. For coded mode, any block containing fewer
than 128 CM words represents a logical end-of-record.
If a logical record consists of an exact multiple of
512 (binary) or 128 (coded) CM words, the block
that denotes the logical end-of-record consists solely
of a block terminator. During write operations, the
level number field of the block terminator contains
the level number from FET+0, bits 14 through 17,
or the WRITECW macro control word. During read
operations, the system will return end-of-record
status and the contents of the block terminator level
number field. If the level number is IVg, the system
will return end-of-file status.

Same as for I fornriat.

Same as for I format.

Refer to option 3 under End-Of-Tape/End-Of-Reel

Conditions.

Same as for I fornaat.

• The system writes all 9 -track tapes with 3n+2 mode.

• The system does not perform block checking via block
terminators as is done for I format.

• For read and write operations on a coded 7-track tape,
KRONOS is incompatible with SCOPE. The system con-
verts data from display code to external BCD on write
operations and from external BCD to display code on
read operations. SCOPE converts data from external
BCD to internal BCD on both read and write operations.

• For 7-track tapes, standard code conversion is per-
formed. For 9-track tapes, no code conversion will
be perform^ed.

• For read operations, if a coded 7-track tape contains
external BCD 1632 in byte 4 of a CM word, the
system converts it to an end-of-line (0000 in display
code). The converse is true for write operations.

• The FET device type is returned in SCOPE format
(refer to the description of the CIO OPEN naacro in
section 3, volume 2).

Description

Binary

Actual data block size can range from to 512 (lOOOo)
CM words in exact multiples of CM words.

Any block containing fewer than 512 CM words repre-
sents a logical end-of-record. If a logical record
consists of an exact multiple of 512 words, the block
that denotes the logical end-of-record consists solely
of a block terminator in the same format as that for
I format.

Logical end-of-file
60407000 D

Tape mark

1-10-21

Characteristics

Logical end-of-information

End-of-reel

Noise

Special considerations

Description

None

Refer to option 1 under End-Of-Tape/End-Of-Reel
Conditions.

Same as for I format.

X-formatted tapes cannot be kibeled.

All 9-track tapes are written in an even multiple of
bytes.

S (SCOPE STRANGER) FORMAT

Characteristics

Mode

Block size (PRU size)

Logical end-of-record

Logical end-of-file
Logical end-of-information

End'-of - reel

Noise

Special considerations

Descriy ition

Binary or coded as indicated by FET+0, bit 1.

No explicit multiple of frames is required. The
maximum block size miay be specified in the mlrs
field of the FET (FET+7, bits through 17). If
no block size is specified in the mlrs field, it is
assumed to be lOOOg.

On a CIO READ (010) or READSKP(020) request,
each PRU is considered an end of record.

None

If the tape is unlabeled, there is no logical end-of-
information. If the tape is labeled, the logical end-
of-information is a tape mark followed by an EOFl
label.

Refer to option 2 under End-Of-Tape/End-Of-Reel
Conditions .

Any block containing fewer than 18 frames is con-
sidered noise, and therefore, ignored.

• Level numbers 1 through 163 are interpreted as level
number 0,

• Standard code conversion is performed for 7- or 9-
track tapes in coded mode.

• For CIO READ (010), WRITE (014), WRITER (024).
and WRITEF (034) functions, a one-block (PRU)
operation is performed with the unused bit count
(FET+7, bits 24 through 29) taken from and returned
to the FET.

• The FET device type is returned in SCOPE format
(refer to the description of the CIO OPEN macro
in section 3, volume 2).

L (SCOPE LONG BLOCK STRANGER) FORMAT

The characteristics and descriptions are the same as for S format tapes except that if
no block size is specified in the mlrs field (FET+7, bits through 17). it is assumed
to be L IMIT- FIRST- 1.

1-10-22

60407000 D

E (LINE IMAGE) FORMAT

Characteristics

Mode

Block size (PRU size)

Logical end-of-record

Logical end-of-file
Logical end-of-information

End-of-reel

Noise

Special considerations

Descrip t ion

Coded

The block size cannot exceed 5120 frames. If the
tape unit will not allow an odd number of frames to
be written, the system will append a space. Unless
the user specifies otherwise when he requests the
tape, the system assumes the maximum block size
is 136 frames.

For a write operation, there is no logical end-of-
record. For a read operation, end-of-record status
is returned when a tape mark is encountered. An
additional read operation returns end-of-file status.

Tape mark

If the tape is unlabeled, there is no logical end-of-
information. If the tape is labeled, the end-of-
information is a tape mark followed by an EOFl
label.

Refer to option 2 under End~Of-Tape/End-Of-Reel
Conditions.

Same as for S-formatted tapes.

E-formatted tapes cannot be labeled.

For a write operation, a block of data will stop either
at a zero byte (end-of~line) in byte 4 of a CM word or
at the multiple of CM words (rounded up) based on the
frame or character count. The system will then space-
fill the buffer to the number of frames specified. Thus,
the amount of data written will exactly equal the amount
specified.

For a read operation, if there is an odd number of
characters, the system will space-fill the last six bits
of the last byte and delete all trailing spaces. This
ensures that data will be stored in the buffer with at
least one 12 -bit byte of zeros.

For a control word write operation, no end-of-line
processing is done. Data is blocked on tape using
the specified frame count. Likewise for a control
word read operation, no end-of-line processing is
done; data is transferred to the user as It is read.

B (BLOCKED) FORMAT

Characteristics

Mode

Block size (PRU size)

Description

Coded

The block size cannot exceed 5120 frames. If the
tape unit will not allow an odd number of frames
to be written, the system will append a space. Un-
less the user specifies otherwise when he requests
a tape, the system will assume the maximum block
size is 150 frames.

60407000 D

1-10-23

Characteristics

Description

Logical end-of-record

Logical end-of-file
Logical end-of-lnformation

End-of-reel

Noise

Special considerations

F (FOREIGN) FORMAT

Characteristics
Mode

Block size (PRU size)

Logical end-of-record
Logical end-of-file
Logical end -of- information
End of reel

Noise

Tape mark

If the tape is unlabeled, there is no logical end-of-
information. If the tape is labeled, the end-of-
information is a tape mark followed by an EOFl
label.

Refer to option 2 under End-Of-Tape/End-Of-Reel
Conditions .

Same as for S-formatted tapes.

• B-formatted tapes cannot be labeled.

• A write operation will stop either at the first zero byte
encountered in any byte position of a CM word or at a
multiple of CM words (rounded up) based on the frame
or character count.

• For a read operation, the system ensures that data will
be stored in the buffer with at least one 12 -bit byte of
zeros.

• For a control word write operation, no end-of-line
processing is done. Data is blocked on tape using
the specified frame count. Likewise for a control
word read operation, no end-of-line processing is
done; data is transferred to the user as it is read.

Description

Binary or coded, as needed, for 7-track tapes and
binary for 9-track tapes

The block size cannot exceed the CM buffer size.
No explicit multiple of frames is required. The
maximum block size must be specified at tape
request time. The block size is used to determine
whether to continue read or write operations based
on the amount of data versus the space in the buffer.
For example, if the maximum block size is lOOOs
CM words, the read operation will stop any time
less than lOOlg words remain. It is recommended
that the user specify a buffer size equal to the
largest block.

None

Tape mark

None

Refer to option 1 under End-Of-Tape/End-Of-Reel
Conditions.

Any block containing fewer than 18 frames is con-
sidered noise, and therefore, ignored.

1-10-24

60407000 D

Characteristics Des cri ption

Special considerations • F-formatted tapes cannot be labeled.

• For 7-track tapes, if a parity error is detected be-
cause the tape is being read in the opposite mode, the
mode will be switched.

• F-format operations are only done using control
word reads and writes. On read operations, the
control words are transferred to the user regard-
less of the operation being used.

END-OF-TAPE/END-OF-REEL CONDITIONS

The following is a description of the processing options for end-of-tape conditions. The
user can select one of these options by default by specifying the data format or he can
specify an option via the PO kejrword on a LABEL, ASSIGN, or REQUEST control card
or the processing option field of the FET (FET+8, bits 36 through 47). In addition, the
user processing option (FET+1, bit 45) gives the macro user control over end-of-reel
conditions. For further information, refer to the CLOSER, REWIND, and UNLOAD
macros described in section 3, volume 2.

Option PO= Option Description

1 I If, during a write operation, the system senses the

end-of-tape, it rewrites the block on which the EOT
occurred as the first block on the following reel. No
trailer Information Is written on the current reel.
During a read operation, the block on which the EOT
occurred is ignored and reading continues on the next
reel. If a tape mark and the EOT are sensed at the
same time, the EOT is Ignored,

2 P If, during a write operation, the system senses the

end-of-tape, the system writes a trailer sequence,
consisting of a tape mark, following the block on which
the EOT was sensed. Any data that occurs following
the block on which EOT was sensed, yet before the
tape mark, is ignored. During a read operation, the
system transfers to the user the block on which the
EOT was sensed. The read operation resunaes on the
next reel. If a tape mark and the EOT are sensed at
the same time, the EOT Is Ignored.

3 S If. during a write operation, the systera senses the

end-of-tape, the system writes a trailer sequence
following the block on which the EOT was sensed.
This trailer sequence consists of a tape mark followed
by an EOVl label for labeled tapes, and tape marks
for unlabeled tapes. The next block is written on the
next reel. During a read operation, the EOT is noted
and the system transfers to the user the block on which
the EOT was sensed plus all following blocks until a
trailer sequence (as described above) Is recognized.
Reading resumes on the next reel.

For options 1 and 2, the system is concerned only with the block on which the EOT
Is sensed. If tapes written using these options are transferred to another system,
any data that occurs on the reel after this block should be Ignored.

60407000 D 1-10-25

PRODUCT SET CONTROL CARDS 11

KRONOS supports the following products, t

FORTRAN Extended 4 Sort/Merge 4

COBOL 4 PERT /TIME 1

ALGOL 3 SIMULA 1

ALGOL 4 SIMSCRIPT 3

Although they are generally used in time-sharing jobs, the KRONOS interactive com-
piler (BASIC) and the KRONOS interactive interpreter (APL) can also be used in batch
jobs. The BASIC control card call is described in this section. The APL control
card is described in the APL Reference Manual.

FORTRAN Extended, COBOL 4, and Sort /Merge 4 use the Record Manager for accessing
files. In addition, KRONOS supports the indexed sequential (IS), direct access (DA), and I
actual key (AK) file management capabilities of the Record Manager. The user interfaces!
with the Record Manager via the FILE control card. This card is used to update the
file information table (FIT) which is required for files which the Record Manager
accesses. For further information, refer to the Record Manager Reference Manual.

This section describes the user library feature available to the KRONOS user and the
control card calls for the product supported by KRONOS.

USER LIBRARIES

KRONOS offers the user the option of specifying a library other than the product set
default libra,ry. The user can then write library routines to perform special functions
to meet his own requirements, t t Routines can also be given names identical to
routines from another library without causing a system conflict. This enables a user to
compare the performance of library routines without modifying his software.

The libraries from which externals are to be satisfied can be specified as parameters
on the LDSET card as follows:

LDSET(LIB=llbi/llb2/. . . /Hb^)
LOAD(lfn)

llbj^ Library from which externals are to be satisfied. The system checks

through the specified libraries sequentially.

Ifn Name of the file to be loaded

Libraries can also be specified by using the LIBRARY card to define the global library
set. (Refer to Loader Reference Manual. ) The default system library, SYSLIB, is
used to satisfy the externals if no library is specified or if unsatisfied externals exist
after using the libraries specified or defaulted.

t Refer to the preface for a list of product set reference manuals,
tt Refer to the Loader Reference Manual for Information about the generation of a user
library.

60407000 D 1-11-1

CONTROL CARD FORMATS

The following is a description of the program call cards for the product set members
supported by KRONOS. The reference manuals listed in the preface provide further
information concerning these products.

NOTE

The following product set control cards are pro-
cessed In product set format.

FTN SORTMRG FILE

COBOL SIMULA

ALGOL SIMI5

Product set format does not allow file nanries be-
ginning with a numeric character (refer to Control
Card Format, section 5).

1-11-2 60407000 D

FTN CARD

The FORTRAN Extended control card calls the compiler to a control point. The
minimum memory requirement for FORTRAN Extended is 46, 000 octal locations. FTN
externals are satisfied from the user library FORTRAN.

The control card format is:

FTN. p^,P2. .. •»?„•

p. Description

A Branch to EXIT control card if fatal compilation error occurs. If there

is no EXIT card, the job terminates.

A=0 Control transfers to the next control card, regardless of the instal-

lation default, if fatal compilation errors occur.

B Object code is written on file LGO. If the B parameter is omitted,

this option is assumed.

B=lfn^ Object code is written on file Ifn^.

B=0 Suppresses obj,ect code output.

BL Generates output listing that is easily separable into components by

issuing page ejects between source code, error summary (if present),
cross reference map, and object code (if requested); and ensures
that each program unit listing contains an even number of pages
(page parity) by issuing a blank page at the end if necessary. If
omitted, BL=0 is assumed.

BL,=0 Listings are produced in compact formiat.

C Use COMPASS assembler for compiler- generated code.

C=0 Selects the FTN assembler regardless of the installation default.

D Debug mode of compilation; a minimum of 61,000o locations is re-

quired if this option is selected. Debug input is obtained from INPUT
source.

D=lfn„ Debug input is to be obtained from Ifng.

D=0 Debug statements are ignored.

E Compiler- generated object code on file COMPS is output as COM-

PASS line images for input to Update.

E=lfn„ Compiler- generated object code on Ifn^ is output as COMPASS card

images for input to Update.

E=0 Normal binary object file is generated. If the E parameter is

omitted, this option is assumed.

EL=« Lists diagnostics according to list specification i :

60407000 D 1-11-3

Pj Description

i^ Description

A List diagnostics indicating all non-ANSI usagtjs, as well as

fatal diagnostics. Also, list informative diagnostics if com-
piling under OPT=0, 1, or 2; list note and warning diagnostics
if compiling in TS mode.

I List informative and fatal diagnostics if compiling under OPT=

0, 1, or 2; list note, warning, and fatal diagnostics if compiling
in TS mode.

N List note, warning, and fatal diagnostics if compiling in TS

mode; list fatal diagnostics if compiling under OPT = 0, 1, or
2.

W List warning and fatal diagnostics if compiling in TS mode;

list fatal diagnostics if compiling under OPT =0, 1, or 2,

F List fatal diagnostics.

If this parameter is omitted, EL=I is assumed.

G Loads the first system text overlay from the sequential binary file

SYSTEXT. A maximum of seven system texts can be specified by
any combination of the G, S, and C parameters.

G=lfn, Loads the first system text overlay from the sequential binary file

Ifn^.

G=lfn-/ovl Searches the sequential binary file, Ifn., for a system text overlay

with the name ovl and loads the first such overlay encountered.

G=0 No system text is loaded. If the G parameter is oitnitted, G=0 is

assumed.

GO Binary object file is loaded and executed at end of compilation.

GO=0 Binary object file is not loaded and executed. If the GO parameter

is omitted, GO=0 is assumed.

1 Source input is on file COMPILE. If I is omitted, input is on

file INPUT.

I=lfn_ Source input is on file lfn_.

L Listable output (specified by list control options BL„ EL, OL, R,

and SL) is to be written onto file OUTPUT. If list control options
are not specified, the listing consists of the source program, infor-
mative and fatal diagnostics, and a short reference map. If the L
parameter is not specified, this option is assumed.

L=lfn„ Listable output is to be written onto file Ifng.

L=0 Fatal diagnostics and the statements that caused them are listed on

the file OUTPUT. All other compile-time output, including inter-
mixed COMPASS, is suppressed. List control options are ignored.

1-11-4

60407000 D

Pi_

LCM=D
LCM=I

ML=nnn

OL=0

OPT=n

P=0

PL=n

PL=nB
Q

Q=0

R=n

Description

Selects 17-bit address mode for level 3 data. This method pro-
duces more efficient code for accessing data assigned to level 3.
User ECS field length must not exceed 131,071 words. If the LCM
parameter is omitted, this option is assumed.

Selects 21 -bit address mode for level 3 data. This mode depends
heavily upon indirect addressing. LCM=1 must be specified if the
execution ECS field length exceeds 131,071 words. In TS mode, all
LCM addressing is done in 21 -bit mode, regardless of the LCM
parameter.

Current date in the form yyddd is used for the MODLEVEL micro.
If the ML parameter is omitted, this option is assumed.

Specifies nnn as the value of the MODLEVEL micro used by COM-
PASS, nnn consists of 1 to 7 alphanumeric characters.

Generated object code is listed on the file specified by the L
param.eter.

Object code is not listed. If the OL parameter is omitted, OL=0
is assumed.

Level of optimization:

n=0 Fast compilation (automatically activates T option)

n=l Standard compilation and execution. (Default value).

n=2 Fast execution. OPT=2 is equivalent to OPT.

Page numbering is continuous from subprogram to subprogram, in-
cluding intermixed COMPASS. If P is omitted, page numbers begin
at 1 for each subprogram.

Page numbers begin at 1 for each subprogram.

n is the maximum number of records produced by the user program
at execution time which can be written on the file OUTF'UT. n does
not include the number of records in the source program listing,
and compilation and execution time listings; n < 999 999 999.

An octal number must be suffixed with a B; n j< 77 777 777.

Compiler performs full sjrntactic scan of the program, but no object
code is produced. No code addresses are provided if a reference
map is requested. This mode is substantially faster than a normal
compilation; but it should not be selected if the program is to be
executed.

Normal compilation. If the Q parameter is omitted, this option is
assumed.

Selects the kind of reference map required:

60407000 D

1-11-5

-Pi-

Description

ROlIND=s

ilOUND=0

ROUND
S=ovl

S=lib/ovl

S=0

SEQ

SEQ=0

SL=0
SYSEDIT

SYSEDIT=0

n=0
n=l

n=2
n=3

No map

Short map (symbols, addresses, properties, and a
DO- loop map)

Long map (short map plus references by line number)

Long map with printout of common block members
and equivalence groups

T=0

In TS mode, R=3 is identical to R=2; comn:ion and equivalence groups
are not listed.

Directs the compiler to produce code that rounds arithmetic opera-
tions involving the following operators: (s==!'/-i- or -).

Computation for the indicated operators is not rounded. If the
ROUND parameter is omitted, this option is assumied.

Implies ROUND=+-*/

The system text overlay, ovl, is loaded from the Job's current
library set.

The system t^xt overlay, ovl, is loaded from lib. lib can be a
user library file or a system library.

When COMPASS is called to assemble any intermixed COMPASS
programs, it will not read in a system text file. If the S param-
eter is omitted, the default is S=SYSTEXT.

Source input file is in sequenced line format (as used in TSRUN
FORTRAN). Specifying this option automatically activates the
TS option.

Source input file is in istandard FORTRAN format. If the SEQ
parameter is omitted, this option is assumed.

Source program is listed on the file specified by the L parameter.
If the SL parameter is omitted, this option is assumed.

Source program is not listed.

All input/output references are accomplished indirectly through a
table search at object timie. File names are not entry points in
main program, and subprograms do not produce external references
to the same file.

Input/output references accomplished directly; file names are used
as entry points in the main program, and subprograms produce
external references to the file name. If the SYSEDIT parameter is
omitted, this option is assumed.

If this parameter is specified, full error traceback occurs. This is
primarily used for programs in debug stages. Selecting the D
parameter or OPT=0 automatically activates the T option.

No traceback occurs when an error is detected.

1-11-6

60407000 D

Pj Description

If the T parameter is omitted, this option is assumed.

TS Timesharing mode. Compilation speed and field length are optim-

ized at the expense of execution speed and field length. TS mode
is preferable to the optimizing compilation modes (OPT=l, 2, or 3)
for the debugging stages of a program. Specifying the TS option
together with the C, D, E, or Q option constitutes a fatal control
card error.

X File OPL is the source of external text (XTEXT) when location field

of XTEXT pseudo instruction is blank. Only one X parameter may
be specified. If omitted, external text is on OLDPL file.

X=lfn„ External text on file lfn„.

Z When Z is specified, all subroutine calls having no parameters are

forced to pass a parameter list consisting of a zero word. This
feature is useful to COMPASS- coded subroutines expecting a variable
number of paramieters. Z should not be specified unless necessary,
since programs require less memory if Z is omitted.

Z=0 A zero word parameter list is not passed. If tlie Z parameter ie

omitted, this option is assumed,

COBOL CARD

The COBOL control card calls the COBOL compiler to the control point. The minimum
memory requirement for COBOL is 52.000 octal locations. External references are
satisfied from COBOL.

The control card format is:

COBOL. Pj, Pg. .... p . comments

If the control statement does not fit on one card, it can be continued on the next card.
However, the last character on the first card must be separator, such as (, +- or /.

The following parameters c£in be supplied.

p. Description

A Leading blanks are treated as zeros in arithmetic statements and

comparisons.

B Relocatable binary object code is written to file LGO. If the B

parameter is omitted, this option is assumed.

B=lfn^ Binary object code is written to file Ifn^ . The file name should

specify a mass storage file.

B=0 Suppresses binary output of object code.

BUF In COBOL 4 buffer sizes are based on the record description; a

minimun size of 514 words has been established. The BUF
parameter selects the Version 3 method which does not use record
description or ALTERNATE AREAS to determine the minimum
block size.

60407000 D

1-11-7

p- Description

C Specifies that a copy is to be made from source rather thsin from

the library, which is the default condition.

D Inhibits COBOL program execution when an E diagnostic is en-

countered.

DB Checks for subscript range errors. If an error is encountered, the

run is terminated. If DB is not specified, no check is made for
subscript range errors.

DBl Allows generation of object code which calls paragraph trace feature

to trace the flow of the COBOL program.

E Allows output of a COBOL compilation to be added to the system

library with EDITLIB. This parameter has no application for
KRONOS.

E=program- The main overlay of the program is named by progr ami- name, which
name must not exceed five characters.

F All data name entries described as COMPUTATIONAL are inter-

preted as COMPUTATIONAL- 1 when this parameter is included.

H Increases sort efficiency if no OPEN statement is executed during

SORT input or output procedure. If this parameter is not used,
unnecessary space is reserved for all program files. If a file
is opened during input/output and H is specified, the run is ter-
minated.

I Specifies that compiler input is to be obtained from file INPUT.

If this parameter is omitted, file INPUT is also assumed.

I=lfn2 Compiler input is obtained from file Ifng. Tape files must be BCD.

L Specifies that the listing is to be written on file OUTPUT. If the L

parameter is omitted, this option is assumed.

L=lfng Output is to be written on file Ifn,.

L=0 Suppresses output except for errors.

1-11-8 60407000 D

A-

N
OB

OB=lfn4

P
S

S=file-name
SUB

SUBM
T

Description

The L parameter may appear with one of the following suffixes
to produce special listings.

Suffix Meaning

C Listing of items copied from user libraries

M Data map

O Object code in octal

R Data-name and procedure-name cross-reference

list with pointers to source lines

X Extended diagnostics

Directs COBOL compiler to issue an E type diagnostic if a non-
ANSI feature is detected.

Separates binary overlay segments from main program and writes
them on LGO. If this parameter is omitted, this option is assumed.

Specifies that binary output from overlay segments is to be written
on lfn4.

Allows the user to execute a strictly ANSI program.

Specifies that external references are to be satisfied from the
source library file COLIB. If this parameter is omitted, this option
is assumed.

Specifies that external references are to be satisfied from the file
identified, which contains the COBOL source library.

Suppresses data division binary output that duplicates output from a
separately corapiled main program, except for working storage and
constant sections, so that the subprogram and main program can be
loaded together.

Identifies the COBOL program as a subprogram so that it can be called
from a main program written in another language.

Requests a tap)e sort rather than a disk sort,
files which may be assigned to the disk.

This requires four

Allows use of a collating sequence other than the standard CDC
sequence.

If the loaded program is to be saved using NOGO with the file name
specified, the V parameter must be specified for all COBOL/SORT
programs. Specifying this parameter causes the SORT code to be
included in the program rather than being loaded dynamically.

An independent segmerit (priority number 50 through 99) may overlay
or be overlayed by an overlayable fixed segment or another inde-
pendent segment. In COBOL version 4 and for ANSI programs, an
independent segment is made available in its initial state. To over-
ride this usage and provide independent segments in their last used
state so that COBOL 3 programs can be run without change, the W
parameter must be included.

Ensures compatibility with COBOL version 3 and turns on the C and
W parameters.

60407000 D

1-11-9

ALGOL 3 CARD

The ALGOL control card is used to call th0 ALGOL compiler to the control points
ALGOL requires a minimum of 27,000 octal locations. External references are satis-
fied from SYSMISC

The control card format is:
ALGOL. Pj. Pg. • • . . P„'

The following parameters may be supplied. Except for the I parameter, the absence
of any parameter suppresses the corrcisponding option.

j)._ Description

A Specifies that the assembly language encoded form of the object

code is to be written on file OUTPUT.

A=lfh| Specifies that the assembly language encoded form of the object

code is to be written on file Ifn..

B Specifies that the assembly language encoded form of the object

code is to be written on file PUNCH.

B=lfn2 Specifies that the assem.bly language encoded form of the object

code is to be written on file lfn«.

C Performs checks on actual parameters in object program to

ensure correspondence with number and kind of formals. Also
perform real to integer transformations on call-by-name parana-
eters. These checks are performed in the absence of C option
except when Q is selected.

D Debugging mode. Examine source program for debugging direc-

tives and install debugging code where required. If D is omitted,
debugging directives in source program are ignored.

F Compile with full checking of array bounds, formal parameter

specifications, and real to integer transformations, if necessary,
on call-by-name parameters. Absence of F implies F. This
parameter is not necessary; it is supplied only for compatibility
with ALGOL 2.0.

Gt Specifies that file LGQ contains user subprogram input exclusively.

This option can be specified only when the S option is specified
and the U option is not specified. This option suppresses the
explicit or implicit I option.

G=lfng Specifies that file IfUg contains user subprogram input exclusively.

I Input is to be obtained from file INPUT. If this parameter is

omitted, file INPUT is assumed.

I=lfn^ Input is to be obtained from file Ifn^.

L Specifies that a listing of the source input is to be written on file

OUTPUT.

tKRONOS does not support segmentation.

1_11-10 60407000 D

_p. Description

L=lfng Specifies that the source input is to be written on file Ifng.

M Produce a map, at compile time, of source input block structure

and relative stack locations of identifiers and descriptors. The
map is produced, following the source listing, on the file de-
clared by the L option or on the OUTPUT file if L is absent.

N Suppresses array bound checking in the object program.

O Optimization of generated code. The code which would be gener-

ated in absence of this option is optimized by eliminating dupli-
cate fetches and stores and by scheduling instructions. Provides
maximum utilization of X registers (all 6000 series CPU) and
functional units (6600 CPU only).

P Specifies that the binary form of the object code is to be written

on file PUNCHB. If P is omitted, no file is generated.

p=lfne Specifies that the binary form of the object code is to be written

** on file Ifng in PUNCHB format.

Q Perform optimization of code produced for loops and array

addressing. Do not check array bounds in the object program.
Do not check correspondence of actual parameters with formal
specifications in the object program.

R^ Specifies that the program on file SEGMENT is to be executed

in segmented form. If the S option is not specified, the system
assumes that the segmented object code already exists. The use
of this option suppresses the I, U, and G options. The file
must be a disk file.

R=lfnt Specifies that the object program on file Itn^ is to be executed

in segmented form.

S^ Specifies that the object program is to be written in segmented

form on file SEGMENT. This option suppresses the X option
but not the P parameter. The file must be a disk file.

S=lfn^ Specifies that the object program is to be written in segmented

'' form on file IfOg.

U Specifies that file LGO contains user input, supplementary to the

file specified with the I option. This is valid only when the S
option is specified.

U=lfnt Specifies that fUe Ifng contains user input, supplementary to the

^ input file.

Z Syntax errors only. Compile according to other options selected

unless the program has syntax errors (detected by PASS 1). If
syntax errors are detected, compilation terminates when the end
of program is read and syntax diagnostics are listed. This pro-
vides a preprocessing mode of compilation for debugging pur-
poses which may overcome error recovery problems.

tKRONOS does not support segmentation.

60407000 D 1-11-11

ALGOL 4 CARD

The ALGOL control card is used to call the ALGOL 4 compiler to the control point.
ALGOL 4 requires a minimum of 46, 000 octal locations to compile. External references
are satisfied from ALGOLIB.

The control card format is:
ALGOL, Pj, Pg, .... Pj^.

The following parameters may be supplied. The absence of any parameter suppresses
the corresponding option.

p . Description

A Specifies that the assembly language form of the object code is to

be written on the file specified by the L option.

A=0 No assembly language listing.

B The output object program is to be written on file LGO.

B=lfn, The output object program^ is to be written on file Ifn..

B=0 No binary object program,

C=n Comments interpretation for special delimiters. This option requires

the compiler to search comnaents for special delimiters interpretation.

n_ Description

No comments interpretation.

1 Debugging directives which are present in comments
are detected by the compiler and cause debugging
code to be inserted into the object program,

2 Overlay directives which are present in comments
are detected by the compiler and cause overlay
directives in loader input format to be inserted into
the object program.

3 Array bound checking directives which are present in
comments are detected by the compiler.

Multiple selection for the C option can be performed by separating
each value by a slash. For example: C=3/2/l is acceptable.

D The symbol file is created on file DUMPFIL .

D=lfn2 The symbol file is created on file Ifn-.

D=0 The symbol file is suppressed.

E The job is aborted to an EXIT control card if a fatal error occurs

during compilation.

E=0 Suppress abort in the event of a fatal error.

1-11-12 60407000 D

p. Description

F If a fatal error is found in the first pass, compilation is terminated

at the end of this pass.

F=0 Continue until the normal end of compilation.

G f Compilation will consider stack swapping to ECS and when the

program is executed, the swapping procedures will be activated
automatically.

G=0 No swapping will be considered.

This option must not be selected when using a machine without
ECS; otherwise, unpredictable results leading to a fatal error will
be obtained.

I Source input is on file INPUT,

I=lfn3 Source input is on file lfn3.

1=0 No source input.

K=n Input record size.

n The number of significant characters to be inter-

preted by the compiler on the source card image.

The default value of K is 72.

L The source program is listed with fatal diagnostics on file OUTPUT.

L=lfn^ The source program is listed with fatal diagnostics on file Ifn^.

L=0 Fatal diagnostics only are listed on file OUTPUT.

N A listing of advisory diagnostics is generated on the file specified

by the L option.

N=0 Advisory diagnostics are suppressed; only diagnostics fatal to code

generation are listed.

0=n Specifies the level of compiled optimization.

n Description

The program is compiled in fast compile mode.

1 Linguistic optimization is performed by optimizing
procedure calling.

2 Optimizations ofO-1 and also subscript and for
statement optimizations.

60407000 D 1-11-13

p. Description

P Specifies that the assembly language form of the object code is to

be punched in standard assembly language card format on file

PUNCH.

P=lfng Assembly language is to be punched on file Ifn^.

P=0 Assembly language punching is suppressed.

Q Create interactive file on file QFILE for ALGOL Interactive De-

bugging Aids (AIDA).

Q=lfng Create interactive file on file Ifng.

Q=0 Suppress interactive compilation and file.

Q may not be specified if the S option is selected.

R A cross-reference map is produced and listed at compile time for

identifiers in the source program on the file specified by the L
option.

R=0 No cross-reference map is produced.

S=n Array storage location.

n Description

All arrays are allocated to CM.

1 Virtual arrays are allocated to ECS.

S may not be specified if the Q parameter is specified.

U Specifies that the file COMPILE contains user implicit outer block

head input, supplementary to the file specified with the I option.

U=lfnY The source program is preceded by the implicit outer block head

list on file Lfny.

U=0 There is no file for implicit outer blocks.

X Allow real-integer (or integer-real) correspondence between formal

and actual parameters, and in the case real to integer perform
the conversion.

X=0 Forbid any real- integer (or integer- real) correspondence between

formal and actual parameters.

Selection of this option will significantly degrade the performance
of the program.

1-11-14 60407000 D

SORTMRG CARD

The SORTMRG control card calls Sort/Merge to process a logical record of directives.
The minimum memory requirements for Sort/Merge is 25, 000 octal locations.

The control card fornnat is:

SORTMRG(pi, P2. . . . . Pq)

pj Description

I=lfni/rj

0=lfn2 /r2

OWN

OWN=lfn3/r3

Sort/Merge directives are on file COMPILE, ff I is omitted
directives are on file INPUT.

Sort/ Merge directives are on file Ifn^ with the following rewind
options :

R
NR

Description

File is rewound before opening. If system INPUT
file is selected, R should not be specified.

File is not rewound before opening. This option is
assumed if rj is not specified.

Listings will be written to the file OUTPUT. If the O parameter
is omitted, this option is assumed.

Listings are written to file lfn2. with the following rewind options:

r2 Description

R File is rewound before opening. If the system

OUTPUT file is indicated, R should not be specified.

File is not rewound before opening,
assumed if r2 is not specified.

This option is

Owncode binaries are on file LGO. If the OWN parameter is
omitted, owncode binaries are on file INPUT.

Owncode binaries are located on file lfn3, with the following rewind
options :

R
NR

Description

File is rewound before opening. If the system
INPUT file is indicated, R should not be specified.

File is not rewound before opening,
assumed if r, is not specified.

This option is

60407000 D

l-ll-'lS

p. Description

MO=n Intermediate merge order; 2<_n< 64. In general, higher merge

orders produce faster sorts at The expense of greater field length
requirements. If insufficient core is available to merge at the re-
quested order, a fatal error occurs; and a diagnostic indicates how
much additional core is required.

MO=*n Intermediate merge order; 2<n<64. If insufficient core is available

to merge at the requested orBer, merge will take place at a smaller
order and an informative diagnostic will be issued.

MO omitted The installation default merge order is used (release system default

is 5).

PERT66 CARD

The PERT66 card calls PERT/Time to process the user-supplied directives. The
minimum memory requirement is 72,000 octal locations.

The control card format is:

PERT66.

PERT/Time 1. 2 is not provided with the KRONOS 2. 1 base system release package; refer
to the Installation Handbook for a description of the special procedures for using PERT/
Time.

SIMULA CARD

The SIMULA control card calls the compiler to the control point. The minimum memory
requirement for SIMULA is 30,000 octal locations. Externals are satisfied from user
library SYSMISC.

The control card format is:

SIMULA, p J, pg, . . . , p^.

The following parameters may be supplied. Except for the I parameter the absence of any
parameter suppresses the corresponding option.

_p._ Description

A Specifies that the assembly language encoded form of the object

code is to be written on file OUTPUT.

A=lfnj Specifies that the assembly language encoded form of the object

code is to be written on file Ifn^ .

B Specifies that the assembly language encoded form of the object

code is to be written on file PUNCH.

B=lfn2 Specifies that the assembly language encoded form of the object

code is to be written on file lfn„.

1-11-16 60407000 D

p. Description

D Specifies that debugging code is to be generated.

Gt Specifies that file LGO contains user subprogram input exclusively.

This option can be specified only when the S option is specified
and the U option is not specified. This option suppresses the
explicit or implicit I option.

G=lfnt Specifies that file Ifng contains user subprogram input exclusively.

I Input is to be obtained from file INPUT. If this parameter is

omitted, file INPUT is assumed.

I=lfn. Input is to be obtained from file Ifn^.

L, Specifies that a listing of the source input is to be written on file

OUTPUT.

L=lfnc Specifies that the source input is to be written on file lfn5.

N Suppresses array bound checking in the object program.

P Specifies that the binary form of the object code is to be written on

file PUNCHB. If P is omitted, no file is generated.

p=lfnft Specifies that the binary form of the object code is to be written on

file Ifnc in PUNCHB format.

R^ Specifies that the program on file SEGMENT is to be executed in

segmented form. If the S option is not specified, the system
assumes that the segmented object code already exists. The use
of this option suppresses the I, U, and G options. The file must
be a disk file.

R=lfnl Specifies that the object program on file Ifn,^ is to be executed in

segmented form.

S' Specifies that the object program is to be written in segmented

form on file SEGMENT. This option suppresses the X option but
not the P parameter. The file must be a disk file.

S=lfn^ Specifies that the object program Is to be written in segmented

form on file Ifno.

U Specifies that file LGO contains user input, supplementary to the

file specified with the I option. This is valid only when the S
option is specified.

U=lfnt Specifies that file Ifng contains user input, supplementary to the

input file'.

X Specifies that the object code is to be written on file LGO.

X=lfn.Q Specifies that the object code is to be written on file Ifn^Q.

t KRONOS does not support segmentation.

60407000 D l-ll-l?

SiMSCRiPT CARD

The SIMSCRIPT control card calls the compiler to process the user's program. The
minimum memory requirement for SIMSCRIPT is 55, 000 octal locations. External
references for SIMSCRIPT programs are satisfied from SIMLIB.

The control card format is:

SIMI5(I=lfni. L=lfn2, A =lfn3, B=lfn4. G=g. D=d)

I=lfnj^ Specifies that Ifn^^ is the input file. If the file nam^e or the

entire parameter is omitted, the input is obtained from file
INPUT.

L=lfn„ Specifies that output is to be written on Ifn,. If the file name or

the entire parameter is omitted, output is written on file OUT-
PUT. Output is suppressed when the user specifies L=0.

A=lfn„ lfn„ is the file on which the intermediate assembler code is

written. If A=0, no listing is generated (default is A=0).

B=lfn^ lfn4 is the file on which the binary object code is written. If

B=0, no binary file is produced (default is B=0).

G=g Compile error override flag

Abort il compile error (default)

1 Load and execute regardless of compile errors

D=d Debug mode flag

1 Normal (debug) mode (default)
Production naode

BASIC CARD

The BASIC control card is used to call the BASIC compiler to the control point. The mini-
mum field length required is 30,000 octal locations. Normally, BASIC coanpiles directly
to central memory. All object-time routines are contained within the coraipiler; therefore,
no external references are generated. However, the user can include the B parameter to
generate relocatable code. When this code is loaded, externals are satisfied from SYSMISC.

The control card format is:

BASIC, Pj, Pg. . . . , Pjj.

The following paramieters may be supplied.

_p. Description

L Source listing, diagnostics, and execution output on file OUTPUT

L=lfnj Source listing, diagnbstics, and execution output on Ifn^

L omitted Diagnostics and execution output on file OUTPUT

K Diagnostics and execution output on file OUTPUT

K=lfn2 Diagnostics and execution output on Ifn,

60407000 D 1-11-18

K omitted
I

I=lfn3
I omitted
B

B omitted
A

A=lfn5
A omitted
N

Description
Diagnostics and execution output on file OUTPUT
Source input from file INPUT
Source input from Ifn,
Source input from file INPUT
Relocatable code on file LGO
Relocatable code on Ifn^
No relocatable code generated
Assembly listing on file OUTPUT
Assembly listing on Ifn-
No assemblLy listing
Inhibits program execution

N=lfng Inhibits prognam execution. Absolute code is written on file Ifn-

N omitted Program is executed in place (no loading occurs)

If both the K and L options are specified on the control card, K is ignored.

TSRUN CARD

The TSRUN control card calls the time-sharing FORTRAN compiler to the control point.
The TSRUN compiler can also be used as a batch compiler. The minimum memory
requirement for TSRUN is 46,000 octal locations. Because TSRUN is written in
Chippewa format (refer to appendix D), all object-time routines are satisfied from the
COS library at compilation time. No user library is specified when loading COS pro-
grams.

Chippewa format presents several problems the user should be aware of when modifying
TSRUN routines. Object-time routines in Chippewa format are relocatable. Bits 15,
16, and 17 (the upper three bits of the address field) of 30-bit instructions are used
for loader control. If constants extend into these bits, they are treated as addresses
and relocated when loaded. Constants that extend into this field should be defined out-
side the block that is identified as that to be relocated. The relocatable block is
identified in the first two words of tlie routine as shown in the following example.

+ VFD 42/OLentry, 18/end

+ VFD 18/erc, 18/end, 24/n

BSSZ n

60407000 D

1-11-19

entry Entry point and beginning of relocatable code

ere End of relocatable code

end End of code

n Number of parameters passed to subroutine

Addresses between entry and ere are modified according to bits 15, 16, and 17 of
30-blt instructions; constants that interfere with these bits should be defined between
ere and end. The addresses pointing to these constants are modified, but the constants
are not.

The control card format is:

TSRUN, cm, if, rf, bl, fl, cl.

The following are the order-dependent parameters.

cm Compile mode option; if this parameter is omitted, the system assumes

cm=G; if this parameter is unrecognizable, the system assumes cm=S.

cm Mode

D Compiles with binary output; the program is not listed

or executed.

G Compiles and executes the program. No listing is

generated unless LIST cards appear in the deck.

L Compiles with source and object list; the program is not

executed.

O Compiles and executes the program; no listing is gener-

ated.

P Compiles with source list and punches deck on file

PUNCHB; the program is not executed.

S Compiles with source list; the program is not executed,

if Name of file containing compiler input; if this parameter is omitted, the

system assumes if=INPUT.

rf Name of file to receive binary information; if this parameter is omitted,

the system assumes rf=LGO.

bl Object program I/O buffer length (octal); if this parameter is omitted,

the system sets bl = 1001 „.

fl Object program field length (octal); if this parameter is omitted, the

system sets fl=field lengtii at compile time.

cl Object program common length.

1-11-20 60407000 D

CHECKPOINT/RESTART 12

A job may be terminated at any time as the result of system, operator, or programmer
error. For some jobs it becomes more advantageous to accept the overhead of check-
point procedures than to run the risk of losing the entire job output. The checkpoint/
restart feature is implemented through the CKP control card and the RESTART control
card.

CKP CARD

The CKP control card causes a checkpoint dunap to be taken.
The control card format is:
CKPdfni, Ifng, .... Ifnn)

Ifn. Specifies a file to be included in the checkpoint dump. If no files

^ are specified, all files local to the job at the time the CKP card

is processed will be checkpointed.

Each time a CKP card is processed, the system takes a checkpoint dump. The dump
is written on the tape or mass storaige checkpoint file specified on a REQUEST, AS-
SIGN, or LABEL control card. The dump consists of a copy of the user's central
memory, the system information used for job control, and the names and contents of
all assigned files explicitly or implicitly identified by the CKP card. These files
are:

• INPUT, OUTPUT, PUNCH, PUNCHB, P8, CCCCCCO, and LGO. These files |
are always included in the checkpoint dump.

• Library type files, working copies of indirect access files, and some direct
access files. If one of these types of files is specified on the CKP card, it
is included in the checkpoint dump, and all other files of that type are ex-
cluded. If no files are specified, all files of these types assigned to the job
are included in the dump.

Each checkpointed file is copied according to the last operation performed on it. If
the last operation was a write, the file is copied from the BOI to its position at
checkpoint time; only that portion will be available at restart time. The file is posi-
tioned at the latter point.

If the last operation was a read and the EOI was not detected, the file is copied from
its position at checkpoint time to the EOI; only that portion will be available at restart
time. The file is positioned at the former point. If the last operation was a read
and the EOI was detected, no copy is performed.

60407000 D 1-12-1

The exception to this rule is the type of operation performed on execute-only direct
access files. If a dump is specified for this type of file, its name and associated
system information are copied but the contents of the file itself is not copied. Thus,
if the user attempts to resume from such a dump, RESTART will be unable to retrieve
that file and will abort. The user can avoid this by selecting the NA and FC options
of the RESTART card and retrieving the file himself.

If the checkpoint file is to reside on mass storage, the user must include a SAVE or
DEFINE control card in the checkpoint job and a GET or ATTACH control card in the
restart job.

If the checkpoint file is to reside on magnetic tape, care should be taken to use a
labeled or nonblank tape. An unlabeled blank tape (one which has never been used)
cannot be specified as the checkpoint file since the checkpoint program attempts to
read the tape to determine the number of the last checkpoint. The tape subsystem then
aborts the job with a blank tape read message.

The system numbers checkpoints starting at one and incrementing by one to a limit of
4095. At this point, a second cycle of numbering begins, again starting at one. An
example showing how to restart from a specific checkpoint is given in the RESTART
control card section.

RESTART CARD

The RESTART control card directs the system to restart a previously terminated job
from a specified checkpoint.

The control card format is:

RESTARTdfn, nnnn, x^)

Ifn Identifies the checkpoint file; the user must have write permission

to Ifn.

nnnn Number of the checkpoint from which to restart; if nnnn Is *, the

last available checkpoint on Ifn is used; if nnnn is omitted, the first
checkpoint Is used. The nnnn parameter can be obtained from the
CHECKPOINT nnnn COMPLETE messages issued to the user's day-
file in response to CKP control cards.

X. Any of the following In any order:

RI If this parameter is included, the control card file on Ifn

Is not restored. The control card file of this restart
job at its current position Is used instead. If this
parameter Is not Included, the entire control card file of
the checkpolnted job Is restored and set to its position
at checkpoint time; any control cards following RESTART
are not processed.

NA If this parameter is included, RESTART is not aborted

if a required file is not available. Also, If NA is in-
cluded and a read parity error occurs In an attempt to
obtain a file from checkpoint nnnn, RESTART selects
checkpoint nnnn-1 If It is available.

FC Normally RESTART restores all files included in the

specified checkpoint. However, if this option is selected,
RESTART first checks if a file is already local to the
restart job. If it Is, RESTART does not replace it with
the file on the checkpoint dump.

1-12-2 60407000 D

The user must assign Ifn to his job before the RESTART card is processed. He must
include a REQUEST, ASSIGN, or LABEL control card if Ifn resides on magnetic tape or
a GET or ATTACH control card if Ifn resides on mass storage.

Checkpoint dumps are numbered in ascending order from 1 to 4095. When nnnn=4095,
the numbering sequence begins again at nnnn=l. The value of nnnn depends on the
structure of the checkpoint file, as defined by the CK and CB parameters of the RE-
QUEST, ASSIGN, or LABEL control cards.

If CK was specified when the checkpoints occurred, each dump is appended to the
checkpoint file, and therefore, all dumps up to the time the job aborted are available
for restart. The user may specify a particular checkpoint dump in the following man-
ner.

Assume a CK file of the name CHF:FILE is being used and checkpoint number 4095 has
been passed. The job is terminated at checkpoint number 10 In the second cycle of
numbering. To restart the job from checkpoint 4 of the second numbering cycle,
the following control cards can be used.

SKIPR(CHKFILE, 8196) There are two records for every checkpoint and

4098 checkpoints must be skipped to reach check-
point 4 of the second numbering cycle.

COPYBR(CHKFILE,AA, 2) The fourth checkpoint Is copied to file AA. At this

point, file CHKFILE Is not positioned correctly for
subsequent checkpoints. If the user intends to con-
tinue checkpointing on this file, a:

BKSP, CHKFILE.

card should be Included.

RESTART(AA. . . ) The job Is restarted from file AA using the fourth

checkpoint.

If CB was specified when the checkpoints occurred, each dump Is written over the pre-
ceding dump, and therefore, only the last dump Is available. If two REQUEST, ASSIGN,
or LABEL cards are submitted, successive CB-type dumps are alternated between two
files; therefore, the last two dumps are available.!

All files copied by RESTART are made local to the restart job. Therefore, the user
must make sure that any direct access files are not lost. For example, assume that
direct access files X, Y, and Z are attached to a job. The job is then checkpointed
and X, Y, and Z are copied to the checkpoint file Ifn. To retain these files as direct
access files during restart, the user should include the following sequence of control
cards.

PURGE(X.Y.Z)

DEFINE(X,Y,Z)

RESTART(lfn,nn,x.)

If the information table associated with a file was included on the checkpoint file, but
the file itself was not copied, RESTART issues the appropriate commands to retrieve
the file.

tif alternate checkpoint files are used and a read parity error occurs in an attempt to
read the last checkpoint, RESTART will abort even if the NA option was selected.

60407000 D 1-12-3

DEBUGGING AIDS

This section contains a description of central memory dumps and their use as a debug-
ging aid. This information should be of considerable assistance to" the user in finding
errors in his program.

CENTRAL MEMORY DUMPS

The first line of a dump gives the boundaries of the memory that is dumped, relative
to the user's field length. Four ceiitral memory words are printed per line, with the
address of the leftmost word printed on the left-hand side of the page. When the phrase
DUPLICATED LINES appears within the dump, all groups of four words not printed are
exactly like the last group of four words. Each word is divided into four groups of
15, „ bits, with the octal representation printed. Figure 1-13-10 is an example of a cen-
tral memory dump. Section 9 describes the options of the DMP control card that can
be used to obtain various dumps.

The user may also dump his exchange package,
the actUEil exchange package.

Figure 1-13-1 illustrates the format of

n+1
n+2
n+3

n+1 5

B<>

'/M

R^cm;

flcm:

y/A//A

'/////////y

RAecs

FLecS

y//////////////////////,

X7.

Figure 1-13-1, Exchange Package

60407000 D

1-13-1

P Program address currently being executed

RA Reference address, beginning address of the associated field length

[central memory (CM), extended core storage (ECS)]

FL Field length

EM-M Program error exit mode (refer to section 6)

MA Monitor address

An Address registers

Bn Increment registers

Xn Operand registers

When the user requests this form of a dump, he also gets the following information.

•

The contents of memory at the address contained by the A registers,
identified as (An)

The contents of RA (reference address) and RA+1, identified as (RA) and
(RA+1), respectively

• 40j> locations before and after the address contained in P (lOOg locations total)
Figure 1-13-9 illustrates an example of this exchange package dump.

GENERATING MEANINGFUL DUMPS

The following methods are used to generate meaningful central memory dumps.

• Error Exit Control

By using the EREXIT macro within his COMPASS program, the user can direct
execution when certain errors occur, rather than having his program completely
halt execution. This enables him to use it as a checkpoint method (that is, to
save generated data to this point). It could also enable him to do further cal-
culations or to write pertinent data to an output file. Refer to section 6,
volume 2 for a description of this macro.

• EXIT/NOEXIT/ONEXIT Control

Once program execution ceases, due to an error condition, and control card
processing is resumed, the user can direct which cards are to be processed
through the use of the EXIT, NOEXIT. and ONEXIT cards. Upon an error con-
dition, the user can issue the DMP control cards to obtain appropriate dumps.
For a detailed description of these control cards^ refer to section 6.

• Dumps may also be generated under control of the user's program through the
use of the SYSTEM macro. The FORTRAN user can generate dumps by calling
the DUMP subroutine.

1-13-2

60407000 D

READING CM DUMPS

Figures 1-13-2 through 1-13-10 are output from a FORTRAN program source deck
processed by the following sequence of control cards.

TESTA(CM50000, TIO)

USER(ABCD, PASS, FAMA)

SETCORE(O)

MAP(FULL)

FTN.

LGO.

OVLA.

DMP.

DMP, 10000.

The source deck in the example consists of four parts.

• Main program (main overlay)

• Function subprogram

• Subroutine subprogram

• Primary overlay

Each part is listed separately followed by the corresponding address assignments,
such as: statement assignments, variable assignments, program length, unused
compiler space, etc. (refer to Figure 1-13-2).

Figures 1-13-6 and 1-13-7 illustrate the load map generated by the MAP control card.
The load map gives the address and length of all block assignments and the address
and references of all entry points. Maps are listed separately for each overlay.
Finally, the load map contains the field length required to load and run the program.

Output generated by the program follows the load map (refer to Figure 1-13-8).

Figure 1-13-9 and 1-13-10 illustrate the central memory dumps generated by the
DMP. and DMP, 5000. control cards, respectively.

The following three examples illustrate the use of these dumps to obtain specific infor-
mation.

60407000 D 1-13-3

Example 1: (Finding Data Locations in a Core Dump)

Referring to Figure 1-13-2, the variable I is used as the control variable in the DO loop
defined by statements 10 through 20. To find the value of I at job termination, the
following steps must be performed.

1. Find I in the variable assignments (lower half of Figure 1-13-2), noting I is at
relative address 4167o.

2. Find the first word address (FWA) of the main overlay TESTA. (Refer to the
load map. Figure 1-13-6.) The FWA of TESTA is 1433.

3. Add (143g + 4167g = 4332o) to obtain the absolute address of I.

4. In Figure 1-13-10. address 4332 contains 00138 (Hio)' This should be the
last value of I.

Example 2: (Finding Data Locations in a Core Dump)

To find the variable B(3), the following points m^ust be considered.

• Find B in the variable assignments (lower half of Figure 1-13-2). The value is
12, which means that B begins at relative location 123 of common block AAA.
By referring to the map (Figure 1-13-6), note that AAA begins at absolute
address lOlg. Therefore, IOI3 + 12g (relative location of B) equals 1138..

the beginning address of array B. B(l) is 113g, and the address of B(3)
is 115g.

• The location in core of the B array is illustrated in Figure 1-13-10.

Example 3: (Finding an Address Within the Program)

By referring to Figure 1-13-9, note that the program stopped at address 10114 (the
value of P). To find where this is in the program, the following points must be
considered.

• Figure 1-13-6 or 1-13-7 contains the routine addresses.

• Figure 1-13-6 illustrates that routine SYS. RM is at 10114 which means the
program ended in routine SYS.RM.

1-13-4 60407000 D

I. • O >». V

. «r> fO K1 M
) O •> • •

I <r • N w

- ..N •. M.

» • O CM CM
» Ci CM • •

* cy ro

J Nk N^ X, X.

e: IM 4-k .

^ ** v40 U7

•.a h- M M -«

fw c n> ^ ••

■ — r* N.
•'I— o »i* «*
«i l/> o <i V

_J li! ■*-< V O

> f- « «i: o

O UJ <! -J

»- a: x ** OD

>- <4 X V X.

3S§§S

o; O X z z

lu a- r i: X
» o. o o o
o u u u

O T^ W

tr II II

o — ^ '

v-t «r 03

CO — «»

kK> 1^ t^ M -»

«>•.•. .,4 es

■H CJ « • »
^* ** *^ C3 *-»
O U U Xl »
. > •s^ <
.«> — —.•>_■

3 CM (\l <M C3 5» -»
^ •> «t « U\ O CC
► •rtCVJ « --I li
)— — —-<■»• O -
I O O t3 II ■- O t-l .

4 •.•.fc->>-_IO*-l

,.^^» ••<tCQ'<<'

H •• • "-i C»f »- •^«» '

'<-4i\jmwuJZ mm:
3 — — — sriOCn — i
'Ooo-'oa<t

^ -1 ^UJ

«<!«►-

UJtU u z

h-1

Oi Ck^ (K l-l

1— t

■§

o
-J

(4-1

aj II) uj -5

CVJ tO o c

*-i \D ^

"ctf

^ -1

J^ J-

X >•

i: I- I-

M « «r
u O cr

«t«i«t<<_l_l«-«"~«»"-'-J-'

|-l-l-l-l-_i_l MMH S<_I_J"

*4
~ -« » J

1-4 *-l CM ^ ^K

WW w O tf

«« « I sc

« » 4- -^ O

z
o

AAA

1- -f

U> 4^

-J

C3l CO

CD CD

«. *« — w O

-1

•i fo

CM -»

MM -^ >- -I

«K

4-t

ir- c=

-t t

S < "^S -J —

w w ^ ort-

>. M 11 II Ui z ->
KOf-i > 2^ 11

II
Of

<x <9: <

ma: oi

« <* <

ct.

crt

O IT

1- 4-1

4-1

O
PJ

J-

«-<

11 11 Ifl-S

.~ «. m •' -1 -J

MM 3f -1 _l W O

O X

w w O -1 <t ■«

o- a

«c CD o ai o u o

liJ

z ♦-

UJ UJ

I
1-

-1

O"-

aJ O

j-i-i

U* UJ

-I

t^.

-1 z

>-«<!«(

1- t-

J-

«r

7 -J

li.

1- UI Ui Ul z z

M. M

an; or MM

at'

•■>

X z

T O

1/1

»- I O X

>-
<

-i

<f
-J

O ♦- LJ T

tfl

■z u>

-1

o
to

bJ
<r

-J »o

Sj,

«r

o
o

(/*

IM 7 O O
-J U;UJ
_l .J V

T
>■

z en

M UJ

UJ 4 en o

M Z

t/\ Q.
UIZ
IM

Ui f-

in » otr
_I o •-

1- CJ

r ro

UJ
Ul C3

-J
to

X Ul z

«r o* CO <*

O: Ui « ^

-I

[.0 (J5 O-

_J a>

>•

II>

o <= -*

K<r

en tr\ ^

O
I

o
u

►H

»-

o u.

a- 3 X r:

«4

l-«
or

4-1 4-1

«1

Q- 4-«
O 4-1

i/i

a ceo o

J-

J-a-

I-*

1—

C J

Figure 1-13-2. Main Program of Main Overlay (0,0)

60407000 D

1-13-5

FUNCTION TRY(A,8»
1(1 TRY = SQRT(A)*SORT(a»

RETURN

ENTRY TRI

IF (A.LE.3) 10,20
20 TRY = SQRT(A)-S'3?T(B)

RETURN

ENO

SYMBOLIC REFEREN(

;e map (r=i)

ENTRY POINTS

1". TRI

"♦ TRY

VARIABLES SN TYPE
A REAL
31* T?Y REAL

RELOCATION
F.P.

EXTERNALS TYPE
SQRT REAL

ARCS

1 LIBRARY

STATEMENT LABELS

r 10

STATISTICS

PROGRAM LENGTH

35»J 2

REAL

F.P.

INACTIVE

Figure 1-13-3. Function Subroutine of Main Overlay (0,0)

SUBROUTINE PRMTtAJ

COMMON/ /O (1001

COMMON/ AAA/P(2qi

COMMON/ A/ S0e(5)

8=0

00 50 1=1,29
50 B=8tP<I)

PRINT 5 6,8, (SUa(I),I=l,5)
55 FORHAT (IX, 6F17.7)

RETURN

ENO

SYMBOLIC REFERENCE HAP (R=l)

ENTRY POINTS
3 PRNT

VARIABLES SN
A

TYPE
REAL
REAL
REAL

RELOCATION
•UNUSED F.P.
ARRAY / /
ARRAY AAA

FILE NAMES

OUTPUT

MODE
FMT

STATEMENT LABELS
SO

55 FM

LOOPS LA9EL
11 50

INDEX

FRON-TO LENGTH
6 7 33

PROPERTIES
INSTACK

COMMON BLOCKS
/ /
AAA
A

LENGTH

100

B
I

sue

REAL

INTEGER

REAL

ARRAY

STATISTICS

PROGRAM LENGTH 308 2'*

CM LA8ELE0 COMMON LENGTH »»2B S"*

CM 3LAMK COMMON LENGTH l<t<tB 100

Figure 1-13-4. Subroutine of Main Overlay (0,0)

l-13-(

60407000 D

1 OVERLAY (OVLA, 1,0)

PROGRAM OVLIO
COMMON/ AAA/' Wti>9)
PRINT 105, (Wd), 1=1, 7)

5 PRINT 105,(W(I»,I=8,1'»)

PRINT 105, (W(T), 1=15, 21)
PRINT 105, (W(T), 1*22, 28)
PRINT 106,(H(29))
105 F0RMAT<1X,7F17.7)
10 106 FORMAT (4X,Fl/,7)

END

SYMBOLIC REFERENCE MAP (R=l )

ENTRY POINTS

3 OVLIO

VARIABLES

SN TYPE

1*7 I

INTEGER

FILE NAMES

MODE

OUTPUT

FMT

RELOCATION

M REAL ARRAY AAA

STATEMENT LABELS

«»3 105 FMT «t5 106 FMT

COMMON BLOCKS LENGTH
AAA 23

STATISTICS

PROGRAM LENGTH V7B 39

BUFFER LENGTH 18 1

CM LABELED COMMON LENGTH 35B 29

Figure 1-13-5. Main Program of Primary Overlay (1, 0)

60407000 D 1-13-7

LOAD MAP - TEST*
OVERLAYIOVLA,a,a)

CYBER LOADER LO-UitOl

7S/06/0J, 13.21., 01,

PAGE

- OVERUAY<OVLA,0,a)

FMA OF THE LOAD
LHA-H OF THE LOAD

IDl

17 32

TRANSFER ADDRESS — TESTA

•»252

PROGRAM AND BLOCK ASSIGNHENTS.
BLOCK ADDRESS LE^

/AAA/

/BLOCKA/

TESTA

TRY

/A/

PRNT

/OA.IO./

/lOCON./

no«in=:

FLTOUT=
CHTAP-
FORSYS=
GETFIT=
KODE'^s
OUTC =
O'JTCOMi
OI/ERLAY
SQ=?T
SYSAIO=
SYS=IST
SYS.'^M
UCL040
/JIPS.RM/
LBUF.SQ
/CON.RM/
CIO.RM
/AOB.RM/
E!?R.^M
•lOtfE.RM
CHHR.SQ
ICT.^H
/MEMC.RM/
/OPES.FO/
/OPEN.FO/
OPFN.RM
0SU8.RH
OPEN, SO
OPEX.SQ
/PUT.RT/
RLEQ.RK
/TERM.RM/
/PUT.FO/
PUT.SQ
HAR.SQ
/CLSF.FO/
CLSF.RM
GLSF.SQ
/CLSV.FO/
0LSV,S(5
/GET.FO/
/GET.BT/
/GET.RT/
GET.SQ
2,S0
FSU.SQ
9TRT.SQ
LXER.SO
KEOX.SQ
/SKFL.FO/
3KFL.S0
//

Ifli

136

<.H22

i»*57

<«<«6if

1.5 1<»

<.650

<.712

1.775

5306

5667

65 /li

6575

7?5i.

71.1.6

7621

7761.

l')02''

100 30

10112

10162

101.1.0

lObSl

106 01.

10612

1061.6

10656

1126?

1131.5

11355

11610

11613

11611.

11623

12057

12152

121.32

121.1.6

121.57

12521

12522

12531

11.0 30

11-310

11.317

11.31.2

11.1.73

11.502

11.625

11.6 31.

11.61.1

11.652

1?7D1

16002

16110

16221.

lextbi.

16610

16617

16666

cldress of common block /AAA/ containing
variable arrays A, B, and C

DATE

PROCSSR VcR LEtfEL HARDWARE

'5
1.257

35
5

30
131.

1.2

53
311
351
651.

<.2
1.57
172
153
11.3

1.3
1

SO
255

11
1T3

31.

1.01.

233

2 31.

260

11.

<*?

12^7

260

131

--T'WA of main overlay

7S/0i/02 FTN
75/06/02 FTN

■..1. U1.01
1..1. U1.01

5
11

1027
101
106
111.
220
11.:.
7
i.7
1^1.

LGO

SL-FO?Ti»AN

SL--ORTr<AM

SL-FORT?AiJ

SL-FORTRA-<

SL-FO^T^A>l

SL-FORT?A>l

3L-F0RT<AN

SL-FORTi?A>l

SL-FORTRAN

SL-FORT'^A'^

3L-F0?T^AN

SL-FO^TRAM

SL-5YSI0

SL-3YSia

SL-3YSI0

SL-5YSI0
SL-SYSIO
SL-3YSI0
SL-3Y3IO

SL-SYSIO
3L-iYSI0
SL-3YSI0
SL-SYSIO

SL-3YSI0

SL-3YSI3
SL-SYSIO

SL-SYSIO
SL-3YSI0

75/0D/02 FTl*

123 SL-SYSI3

SL-SYSIO
SL-SYSIO
SL-3YSI0
SL-SYSIO
SL-SYSIO
SL-3YSID

SL-3YSI0

75/03/27
75/01/27
75/03/27
75/03/27
7"!/f)3/27
75/03/27
76/03/27
75/03/27
75/03/27
75/03/27
75/03/27
75/03/27
75/03/27
75/03/27

COMPASS
COiPASS
DD1PASS
C31PASS
'?3'1PASS
C31PASS
OD-tPASS
CD'IPASS
COiPASS
COiPASS
COiPASS
531PASS
COMPASS
C31PASS

75/03/27 COMPASS

75/03/27 COiPASS

75/03/27 COiPASS
75/03/27 COiPASS
75/03/27 COiPASS
76/03/27 COiPASS

75/03/2^ CDIPASS
75/03/27 COiPASS
75/03/27 COiPASS
75/03/27 CSiPASS

3. 75096

3. 75086

3. 75006

3. 7508b

3. 75086

3. 75096

3, 75086

3. 75096

3. 75086

75/03/27 CDiPASS 3. 75096

75/03/27 CSiPASS
75/03/27 COiPASS

76/03/27 C3iPASS
75/03/27 COiPASS

75/03/27 COiPASS

75/03/27
75/03/27
75/03/27
75/03/27
75/03/27
75/03/27

COiPASS
COiPASS
COiPASS
COiPASS
COiPASS
COiPASS

666y
666X

3. 75086
3. 75086

3. 75036
3, 75186

75086

3. 75086

3. 75096

3. 75086

6fc6X I

COMMENTS

0PT = 1
OPTsl

0PT=1

COiMON COaEO I/O ROJTINES ANU CONSTANTS.
COiMON FLOATING OUTPJT CODE
CRACK APLliT AN3 Fa^iAT FOR KOOER/KRAKER.
FO:?TRAN OBJECT LIBi'.A^Y UTILITIES,
LOCATE AN FIT GI\(EN H FILE NAME.
OUTPUT FORMAT INTE'^P^ETER.
FORiATT£0 W^ITE FJ*TRAN RECORO

COMMON OUTPUT cooe

OV-RLAY LOADING ROUTINE.

COiPUTE THE SaUARE OOT OF X. OPT = ALL.

LINK BtTWttN SYS = Alr) ANO INITIALIZATION COJE.

MATH LIBRARY LINK TO ERROR MESSAGE P-JOCtiSOR.

PROCFSS SYSTEM RECWEST.

L7;5086 LOAUE=! USER 'lALL INTERFACE riOJTINt.

75/03/27 COiPASS

75086

Figure 1-13-6. Loader Map of Main Overlay (0. 0)

1-13-8

60407000 D

ENTRY POINTS.

ENTRY

AnORESS

PROGRAM

REFERENCES

TNPUTr

11.3

TESTA

OUTPUT=

Z20i»

PRNT

TESTA

itzsz

TRY

hkZ^

TRY

TESTA

TRI

'.If 76

TESTA

PRNT

".(.e/

PRNT

TESTA

OSNTRY.

1.K1.1

FORSYS=

TESTA

FECCHR.

1*717

COM 10 =

<OOFR=

FeOP?T.

U7 3T

FHTA3=

c^OFOL.

i.7 75

FLTO'JT =

KnDER=

^EOEOV,

5017

l<OOFP-

FEOEXP.

5021

KOnER:

FEOPNO.

5n5n

KODEi'.s

FE0S04.

5113

<ODER=

FE07',0.

5177

<onFR=

-ECN4P.

5316

FMTAP =

<0DFO=

ff-:ap.

ESZ^t

OUTC =

FEHFMT.

634?

K00f'=

FECFMU.

53^6

KIOER'

FECJP=

51.51

OUTC =

FECL".

?i*S2

KOOFR=

FECP?.

51*75

<<OCFR=

FECE-.

5512

KOOE^=

FECV.

556(1

KOOF=>=

FECB'JG.

5567

KOnF'P=

RANDOM.

5667

FORSYS=

LITE.

5651

FLSCM.

5662

FLLCM.

55r.3

END.

5715

I'^STA

= XTT

67ul

STOP.

571.3

A9N0R1.

57e7

SYSAPG =

5773

lOE'?'..

6012

OUTC

SYSEND.

<?n36

SYP=S

6037

CLSLNK.

6053

SYSERR.

611i«

r;oMio=

itsnj

itzei*

1.270

1.256

1.306

1.252

6653

671.0

5575

7035

7051.

7075

7051.

7036

7023

7051

7072

7013

701.6

7066

7021.

70S2

7073

6660

6735

671.1

67b 1

6775

7360

6655

7231

7203

721 3

721.3

6611.

6720

7353

661.7

6650

7001

6621.

6575

6576

7736

1.311

r;oMio=

1.756

FMTAP=

5611.

GETFTT=

6562

OUTC:

71.1.0

OVrpL^Y

7730

1.771

SYSTIA.

6155

SY°=1

6161

SYP = 2

6167

SYP=3

62 36

SYPil.

62-1.

SYS = 6

!)271.

SYS2 =

6317

:oi.

6356

cso.

6365

coo.

6372

BFM.

6i.ni

FECQPt.

61.06

OUTC =

7 335

LINLIM.

61.51

OUTC =

71.17

liGAT.

6'*65

3=<3FTT.

61.76

Oi/EPHY

7652

GETFTT.

65 36

G-rFiT=

0(1 TC =

7277

NAME.

6573

KOJPT.

65'6

03E=; =

0!)Tr=-

7267

<OaM'.T =

7237

OUTC =

731.7

KO'EP.

721.1.

O'.IJC-

7270

OJTCI.

7271

OJTC=

PRNT

4501

3UTC'..

7367

FEDL.

71.1.6

ojTcaM=

<ODEi!'=

6613

6656

FFOT.

71.51

KOCER'

6610

6611

FEOVFL.

7516

FLTOUT-

5020
7077

5210
711.6

FEO»FM.

757..

FLTOUT=

501.1.

501.7

5051

5055

= 205

FEOBLS.

7531

FLTOUT:
K001R=

5000
5203
7030

6001
7155

5002

6004

5174

FEOnNV.

76*..

FLTOUT=

5016

FEORIF.

7575

FLTO'JIT =

5172

FEORto.

7601

FEONTL.

7506

OVERLAY

7673

ni/-RLAY

TESTA

1.251.

4301.

S1',T

77h5

S1?T

SQRT.

inoni.

TRY

1.1.31

4433

41. 47

445 1

SYSAIn^

100 27

SY5Aia=

OR. TO,
SYS=1^T

1.51.0

1001.7

3YS1ST.

10033

SY3=1ST

SQPT

10017

WORGLIE.

100,15

!)175

5201

Figure 1-13-6. Loader Map of Main Overlay (0. 0) (Cont'd)

60407000 D

1-13-9

SYS=

MUB-
MSG=

C10=

LOADER^

LOUDER

L9l)F.SQ

RM.CIO

s<rs.RH

RM.RGLi

R'l.ROLP

RM.SYS=

iR^l.Rf

HOtfE.R"

OHMR.SO

ICT.'^M

OPfN.RM
0S'J9.RM
OPEN.SQ
OPXX.SG
OPEX.SO
^LErJ.OM

?UT.3Q

fLSH.SO
H«R.30

^EPO.SO
CLSF.PM

SLSF.SC
'.SPT.SQ

10127
101S3

1011. :i

1015?

loi«>z

10162
10l»51
10613

10623

10630

1063'
lO/Su

1071.0
11116
11262

llSiio

11362

11623
12057
12152
12267
121.32
12<.57

125^2

13«5i.3
li>030

lfc2?7
l^Sl?

11.3U2
li.i."lO

UDLOAO

L3UF.Sa
CID.RH

tR?.^M

lOKE.Rw
CHMR.S1
MOT .?!1
O'EN.RM

o'tN.sa
o'h:x.33

^LEI.R-1
PJT.SQ

C.3F.R1

C.5F.S')

FORSYS=
ERR.RM

QS.IO.
FaRSYS=

ERO.R1

puT.sa

LXEP.3Q

OtfERHY

LXER.5Q

ERR.R1

OPEN. SI

nPEX.Sf)

PUT.S5

HAP. SI
CLSF.Sa
CLSV.30
GET, S3
MEOX.Sd
ERR.R1
PUT.S5
WAR. S3
CLSF.Sil
GET. SI
3TOT.ST
PUT. S3
GET. S3

JMPS.'M
MEMC.'.M
OPES.FO
OPEN.FO
OPEN.^I

OSUB.^M

OPtN.SO

OPEX.SO
RLEQ.RM
PUT.F3
''UT.S3

OLSF.FO
CLSF.'^M
CLSF.33
CLSV.FO
GET. FT
GET. 33

LXER.S3
MEOX.30
SKFL.=0
SKFL.Sn

PUT. S3
FSU.33
OPEN. 30
=UT.S3
OPEN.^M

r;LSF.^?i

FORSYS=
OPEN.^M
FORSYS=
0PEX.3Q
OPEN. 33
PUT. S3
HAR.S3
F3''SYS =
3UTC=

PUT. S3
ME0X.33

FORSYS=^
OUIC=

ODEN.SO
OPEX.Sn
CLSV.sa

GET. S3

<.536

461.6

5701

5733

5 77 2

11067

11106

11237

1.51. «.

5726

6731

5761

576 3

5770

6267

6306

6311.

11024

11041.

11115

13262

13316

16355

7701.

1631.1.

11103

12275

1?1.10

121.37

12600

1322 3

13310

1333

13541

13551

13634

11.020

11.132

11.306

11. 1.01.

11.1.71

11.535

11.545

11.561

11.571

14603

15101.

15271

15361.

15321

15533

16532

16552

11073

13522

13657

14007

11.232

11.372

11.752

15026

16210

13236

13256

1621.5

101.1.1

10442

101.43

101.44

10445

101.1.6

10450

11610

11611

11512

11613

11611.

11615

11616

11517

11623

11521

11522

11625

11716

11765

12031

1201.0

1201.2

12046

12050

12051

1211.0

1211.1

1211.2

1211.3

1211.1.

12145

121i.b

1211.7

12150

12226

12230

12233

122? 4

12334

12336

12373

121.23

1Z1.21.

121.33

121.62
12522

12523

12521.

1252 5

125Z6

12527

12530

12531

12535

12572

12513

12515

12623

12572

12731.

12770

13017

1322 5

13254

13255

13275

11.015

11.023

11.310

11.311

11.312

11.313

1431*

11.315

14315

14321

11.332

11.31.0

11.350

ll.i.27

141.72

11.1.73

11.1.71.

11.1.75

141.7 6

11.477

11.500

11.501

11.625

11.526

11.627

1453

11.631

11.532

14533

11.652

14656

11.573

147

11.705

161.05

15527

15562

15605

16371

151.51.

161.61.

161.57

165

16610

16611

16512

15513

16614

16615

15516

16621

16621*

16527

13111

16061

12162

13026

1161.6

11650

11752

117!;i*

12022

12026

11.321.

61.1.7

11766

641.7

121.1.5

12266

1261.1.

12726

11.031

5 331

71.23

1765'2

161.77

6101

6140

7327

1231.5

12431.

14521

11.615

15 027

15 = 13

Figure 1-13-6. Loader Map of Main Overlay (0, 0) (Cont'd)

1-13-10

60407000 D

OVERLAy(OVLA,l,0)

FHA OF THE LOAD 17033

LHA*1 OF THE LOAD 17103

TRANSFER ADDRESS ~ OVLIO

i7o;<";

PROGRAM AND BLOCK ASSIGNMENTS.
BLOCK ADDRESS LENGTH FILE

OVLIO 17033 SO L60

ENTRY POINTS.

DATE PROCSSR tfER LEVEL HARDWARE COMMENTS

75/06/02 FTN 't.'f UffOl 566X 1 0PT«1

ENTRY

ADDRESS

PROGRAM

REFERENCES

OUTPUT=

zzn>*

TESTA

OVLIO

aSNTRY.

<»5<.l

FORSYS=

OVLIO

END.

5715

OVLIO

OUTCI.

7271

OUTC=

OVLIO

DVLIO

17036

OVLIO

17052 17056 17062 17056 17072

17036

17051

irO'»0 170i»2 1701.4 1701.6 17050

Figure 1-13-7. Loader Map of Primary Overlay (1, 0)

i.doooooo
s.ooooooo

500.0000000

2.1000000

3.3000000

6177.2000000

2.0000000

16.0000000

6. 32<i$553

2.1000000

3.3000000

795. 7*9»875

2.0000000

9.0000000

600.0000000

3.1000000

0.0000000
If. 0000000
18.0000000
6.92820 32
3.1000000

0.00 000 00

3.0000000

lO.oooooon

700.0000000
202.0000000

o.ooooonn
6. ooooooo

20. DQOQOOO

7.<»03Jl«t3

202.0000000

0.0000000

<».nQoaaoo
lOO.oooonoo
Boo.noooooo

2.2000000

0.3000000
6.3000000
2.S2ai»271

8.3000000
2.20000DD

0.0000000

s.onoriQoo

200.0000000

900.0000000

3.2000000

0.0000000

lo.ooooiono
H.ooQoioao

8.<»8S2814

3.20001000

0.0000000

Figure 1-13-8. Program Output

6.0000000

300.0000000

1000.0000000

303.0000000

0.0000000

12.0000000

<«.0S89795

8.9'»42719

303.0000000

0.0000000

7.0000000
1(00.0000000
101.0000000

2.3000000

ii».oaoooua

5.65685if2

101.0000000

2.3000000

60407000 D

1-13-11

EXCHANGE PACKAGE.

1 1011*1 AO

220* an

12*100 «1

1 81

17200 AJ

: 6530 fl2

7 7775 5

7 A3

6531 33

2*5

RAX

5670 B*

FLX

«5

; 567* 35

10***

2200 Ae

1 86

6102

2236 87

0000

0000 0000 0000

0000

0000 0000 0000

1717

0631

»631 *b*0 361S

2000

0000

0000 0000 0012

X"»

2000

0000

0000 0000 0000

0000

0000 0000 0003

0516

0*20

onoo 0000 0000

20O0

0000

0000 0000 0001

(RIM

0000

0000 0000 0000

tR»n»

osie

0*20

0000 0000 0000

DUNP FROM 1005* TC

1 1016*

10 05<»

52577

77676

66622

53*55

lOOSO

10633

553*1

2270*

5 5*31

10 06*

01000

00000

61000

*6aao

10070

21322

530*0

0*000

10030

1007*

00000

10100

55012

20725

15051

6 2*55

1010*

00000

00 00

10110

00000

OOOOD

00000

0000

1011*

0*000

0573*

00000

00 00

10120

51100

10112

0*000

10122

101?*

51100

00001

01000

10112

10130

51100

00001

03110

10127

1013*

71602

2031*

2065 2

J 6662

101*0

0*000

10132

61000

*6aoa

101**

2 6??

12161

20651

20123

10150

■♦3652

71100

00002

12661

1019*

7S220

01000

1011*

*6a03

(A0>

1725

2'.20

252*

0000

(Al)

0516

0*20

0090

0000

ooon

(A2)

1717

0631

*6J1

*6*0

3615

(A3>

2000

0000

0012

(A*)

5555

5733

36*0

(A5»

2000

0000

0003

1571

(A6I

0516

0*20

000

0000

(A7)

0000

066 00

10056

5*11)5

55*31

76165

51600

10103

55761

513 00

10076

61100

00001

00000

OOOOO

00000

11160

*0506

11161

12*05

OOQOO

00000

oonoo

OOOOO

00000

OOOOO

51100

00001

03110

10115

71100

00130

20 160

V6000

20&62

01000

1011*

v6nofl

71502

2031*

0*000

10125

53160

2017 3

03310

10133

71603

2*616

12661

20651

03760

101*1

71600

0301

53120

11161

71600

31117

0*00*

10155

blOOP

*6noO

03*10

10057

56330

5 6*31

10633

7*260

2270*

55671

*3002

f5231

26060

63735

OOOOO

0*000

10125

OOOOO

5*610

0*000

10113

*6aD0

13661

13161

13661

*6aoo

51100

roooi

03110

10126

20150

36661

01000

1011*

03010

10133

51100

OOOOl

OlOOO

1011*

61000

*6000

206i.5

13115

0*000

101*1

032-'0

10153

1*777

27606

53120

20173

03310

10160

03610

10060

56330

57*31

21111

55761

55071

*6oao

21322

95121

63635

55*11

OOOOO

11160

61116

112*0

50000

OOOOO

1007*

01300

OOOOO

51100

0066

03310

10121

51600

10113

10611

*6000

0*00*

10127

61000

*6ooa

0*00*

10133

61000

*6aD0

03110

10135

71100

00001

0*000

05732

OOOOO

01000

10133

61000

*6000

12 717

20652

53720

12662

03110

101*7

52120

00001

Figure 1-13-9. Exchange Package Dump

DUMP FROM TO

1 IDOOO

OOOOO

05160

*2aoo

OOOOO

30000

OOOOO
OUPLICATiC

OOOOO

1 LINES

OOOOO

oonoo

OOOOO

56110

03110

0005*

5*710

51100

00001

03110

3 0055

15091

52000

OOOOO

0061

OOOOO

17200

90000

OOOOl

17261

*oiao

OOOOO

*0000

OOOOO

17103

17261

*0157

5500

OOOOO

a oooo

OOOOO

0000

100

OOOOO

00001

71030

*252 MAA(A)1721*

OOOOO

10*

1723*

OOOOO

17235

OOOOO

110

172**

OOOOO

172**

*0000

OOOOO

11*

1722*

OOOOO

1722*

71*21

60500

4**11

120

17226

73J17

27205

*11*5

17227

36735

20*26

40772

12*

1723*

36156

7*671

3 76*5 (C) 17226

OOOOO

130

17275

2*000

OOOOO

1721*

31*63

1*631

+ 6315

13*

1721*

*631*

631*6

31*63

17215

*o31*

631*6

?li.63

1*0

172**

*0000

OOOOO

172*6

OOOOO

30000

1**

90000

OOOOO

0163

OOQOa

000*2

60000

Q 0000

150

oonoo

00002

OOOOO

00203

OOOOO

01*00

OOOOO

15*

OOOOO

OUPLICATSn LINES

; ,

220*

17252

*20 25

2*00

OOOOO

1*700

*0630

D7727

2210

OOOOO

06103

OOOOO

00003

OOOOO

22**

221*

OOOOO

0000

OOOOO

2 220

OOOOO

10000

OOOOO

03 00

OOOOO

22**

2 22*

OOOOO

00002

2**00

OOOOO

oonoo

2230

0*021

*6aoo

000*0

22**

OOOOO

OOOPO

OOOOO

3 2?**

223*

OOOOO

02237

OOOOO

22*0

OOOOO

22**

55555

56555

55555

5 553*

57333

33333

56655

2250

35555

53657

33333

3 3333

333 35

66565

55555

55S55

?25*

33333

33555

5 5555

55555

556*1

57 333

33333

2260

OOOOO

oonoo

OOOOO

55555

5 6i*3

226*

33333

333 33

55555

55553

*3357

33 333

33333

2270

55565

56556

35333

3 5733

33333

33556

55555

227*

33335

73333

33333

3 3333

OOOOO

2300

55555

555*1

33335

7 3333

33333

55555

?30*

33573

33333

3 3355

55555

55655

'.*333

35-'33

2310

33333

35566

6565 6

5 553*

333*5

73333

33333

3 3 333

231*

573*3

33333

35555

5555J

55665

55 365

7 3*33

2 320

33335

55555

5 5555

35573

53333

33333

333';5

2 32*

55553

63336

57333

33333

35 665

55555

ss-^ss

2330

55555

55556

55555

5 65 55

55553

65736

33 333

33733

233*

37363

33333

33 333

3 5555

55555

55655

55335

7 3333

?3*0

53335

55555

65556

5 5555

33573

33333

33 333

3 3355

2 3**

55555

55533

57333

3 3333

33333

30000

OOOOO

2350

55555

55565

55375

73333

333 33

33333

65555

36555

7 35*

*357J

33333

3333 3

3 3355

56555

55665

553*3

35733

11162 0262* OOOOO 001*3

oonoo OOOOO ooooo ooooo

17252 *202S 2*000 0220*
OOOOO OOOOO OOOOD OOOOO

6*650

02650

OOOOO

*6000

OOOOO

ooooo

*02*2

noonn

ninon

1703?

OOOOO

ooooo

1722*

OOOOO

ooooo

17236

ooooo

172*5

noooo

OOOOO

ooooo

17725

52023

531*7

7*736

1723*

ooooo

OOOOO

1721*

1*631

*631*

631*6

17215

31*6'!

1*631

*6316

17226

nnnofi

OOOOO

172*7

*oooo

OOOOO

oooon

20010

oonoo

noooo

ooooo

OOOOO

ooooo

00*2

60010

ooooo

22600

03*00

0*521

ooooo

00002

ooooo

noooo

ooooo

oooon

ooooo

OOOOD

ooooo

022**

ooooo

OOOOO

ooooo

noooo

ooooo

55555

',5555

55355

73333

37673

3 3333

33333

33355

33333

35555

55555

95555

57333

3 3 333

33333

35555

33335

65555

55555

53*33

55553

63333

57333

33333

55665

5555'=:

5555*

33 33

55*23

33357

33333

33555

55555

OOOOO

oonoo

ooooo

OOOOO

33333

55555

56655

55555

E5555

55553

65735

55365

7J63J

33333

33000

oonoo

ooooo

oooon

33333

55555

6555«

55553

35733

55555

!;S555

55555

55536

55555

6*157

33333

33331

33333

3J555

55555

(B)

OOOOO

ooooo

OOOOO

*aooo

OOOOO

*00Q0

oooon

ooooo

OOOOO

ooooo

OOOOO

ooooo

17226

OOOOO

ooooo

17237

ooooo

17215

52023

63147

7*736

17226

2*613

01655

51333

1723*

17*15

66315

755*7

17216

1*631

*631*

631*5

1730*

37000

OOOOO

17236

OOOOO

11162

252*

00000

OOOOO

ooooo

OOOOO

ooooo

OOOOO

ooooo

OOOOO

ooooo

OOOOO

ooooo

OOOOO

20010

ooooo

00002

OOOOD

ooooo

022**

17252

*2025

2*000

00131

37520

ooooo

01000

0*2*5

OOOOO

ooooo

OOOOl

OOOOO

ooooo

OOOOO

33333

6S565

55555

5555*

05733

55*25

73333

33333

3 3333

55555

55**5

73333

33573

33333

33355

33333

35565

55555

55537

67333

33333

35555

33335

56555

55555

5*333

553*3

33333

67333

33333

55555

55535

65353

33557

33333

335S5

55SS5

OOOOO

55555

55*13

**2*2

55555

53357

33333

13333

33555

55555

57333

333 33

33333

35565

33335

56555

55555

33*36

57333

33333

1-13-12

Figure 1-13-10. Central Memory Dump

60407000 D

2340

33333

36556

55555

S5553

34375

73333

33333

ooooo

oonoo

OOOOO

55655

55555

55655

63441

•"sei*

57333

33333

3 5555

55555

34435

73333

33333

55565

55555

55553

53357

33333

?3ro

33335

55555

S55S5

35574

33543

37354

?345S

55555

55565

55553

75733

33333

33656

55555

?37<»

55555

55537

571.31.

4 434+

1*2444

05555

55555

3 5555

55405

74140

41434

03735

OOOOO

2i>ao

55555

5 5541

57363

53740

40 40 3

55555

55553

55415

74436

43353

33535

55555

55565

JI.BI.

55555

51.257

37433

6363.*

37435

55655

55555

5 5555

43573

33333

33355

65655

55555

55554

35737

2<»ia

t3i.03

SttSSi.

37555

5 5555

55555

55543

57443

73735

42344

1.5555

55555

55534

33345

73333

33333

3333 3

^itiii

nOODO

OOOOO

55555

55556

55635

57343

33333

35555

55555

55656

65365

73433

2W0

33333

55555

5 5555

55353

33557

33333

33335

65565

55555

35673

53333

33333

33365

PI.?*

55555

55i665

65553

65735

33333

33555

55555

55553

63335

57333

33333

36556

55555

65555

ZU30

55355

73633

33333

3 3333

OOOOO

55555

65665

65655

55555

55553

55736

33333

?i.3l»

33000

OOOOO

55555

55554

24440

57423

741*43

431.24

05555

55655

55556

55335

73333

pititO

33333

333 3 3

55556

5 5555

55553

53357

33333

3 3 333

33335

55555

55655

33573

333 33

33333

33355

21. mt

55555

55553

3 57 33

33333

33655

5 5555

55555

55533

57333

33333

30000

OOOOO

2I«30

00000

OOOOO

90000

ooooo

ooono

OOOOO

noooo

OOOOO

ooooo

OUPLIC«T=:

■) LINES.

-Z»i.

ooooo

nciDoo

OOOOO

oaooo

ooooo-

22600

OOOOO

31.521

OOOOO

22600

OOODQ

04521

77777

66167

If 250

21.05?

3?U01

5565

4252

OOOOO

oonno

10000

siino

4 245

01000

04541

51100

04312

46000

45000

1*25 <»

oinoo

07'623

00160

4250

51100

01*316

46000

01000

04457

00170

04250

71700

00001

61700

04332

4 260

51500

01,332

62450

00100

72750

ooion

40644

<6000

51700

04320

51700

04321

54640

51100

04320

46000

i-2&if

010 00

01*1.26

00220

4250

51500

04332

72750

00100

52650

00100

51700

01*320

51700

04321

51100

04320

"•270

01000

01.1.36

00230

4250

51500

04332

72750

00001

72077

77754

52660

00112

54750

03300

04250

46000

■.271,

71700

00001

51700

01.333

51500

04333

61600

30006

35055

63750

62500

00100

51570

00100

56450

30045

1-30

61550

00002

24700

460 00

51770

00135

61770

00001

06670

04277

76770

46000

51700

04333

51100

04323

t301»

01000

07623

00260

01*250

51100

04316

46000

1*5000

01000

04467

00270

04250

51500

04333

51100

04260

''310

77005

21.700

51700

00123

04000

05715

45000

46000

OOOOO

04416

OOOOO

04327

-311.

OOOOO

43 30

OOOOO

UOOOQ

OOOOO

0000

onooo

OOOOO

onooo

04331

nooon

OOOOO

'.3?0

ooooo

OOOOO

00112

ooooo

OOOOO

00112

ooooo

ooono

ooooo

OOOOO

onnnn

00900

ooooo

04420

t321t

OOOOO

ooooo

OOOOO

4327

ooooo

OOOOO

4330

OOOOO

noooo

OOOOO

noooo

OOOOO

00001

•.330

ooooo

OOOOO

ooooo

onooo

OOOOO

loonoo

ooooo

OOOOO

00013 1 I

ooooo

OOOOO

ooooo

OOOOd

<-33i.

ooooo

00173

ooooo

ooono

ooooo

00173

ooooo

noooo

ooooo

00173

oonoo

OOOOO

noooo

00173

DUPLICAT?

D LINFS.

1,411,

ooooo

0173

oonoo

ooooo

0173

17251

1.0155

55565

55555

ooooo

OOOOO

ooooo

00300

"1.20

17261

1.0155

55655

5 6555

ooooo

OOOOO

24223

1555=

55550

04426

noooo

ooooo

17200

"Wfc

511.00

01*1.56

10644

46000

61300

04423

52030

oonoo

04000

04271

OOOOO

74600

51*010

51600

01*423

' <»30

^6000

1*6000

46000

64500

53150

ainno

1 0004

50500

03001

53150

46000

51500

04464

01000

10004

'•'.3".

51500

011.1.51.

30056

24700

51700

04456

04000

14424

04000

04271

OOOOO

51200

a444i

10622

46000

I'lftO

51600

01.1*3

04000

4427

04000

04442

51000

1.6000

51100

04456

51200

04436

lObll

22702

51600

04430

titHi.

51700

041.26

61000

46000

54500

50400

00001

53150

53340

31031

24700

46000

03270

04431

01000

10004

"♦kSO

50500

00001

53150

46000

51500

04451*

01000

1 0004

51600

041*54

31066

24700

51700

3 4455

04000

041*24

ltl»5!t

17221.

36156

74671

37645

-.60 00

45000

46000

17234

36156

74671

37646

OOOOO

ooooo

OOOOO

-I.&0

OOOOO

oonoo

OOOOO

ooooo

OOOOO

oooon

OOOOO

ooooo

OOOOO

i-<.5l.

20221

62455

5555

4467

OOOOO

ooooo

17200

51300

0446F

52030

OOOOO

04000

04307

ooooo

■-.1.70

71.600

54010

61600

4455

43700

71600

nnnoi

*6noo

51700

04512

51600

04613

61500

04513

51500

00035

i-i»rit

63750

46000

51500

04512

51470

00100

517'0

00001

30045

2 470

61*750

06670

01*475

75770

1.500

51700

04513

51100

04503

010 no

07271

00100

04454

04oan

04466

46000

00000

30000

ooooo

220 4

i-Efli.

OOOOO

01*510

000 30

OOOOO

01000

04^12

00030

OOOOO

06000

041*57

OOOOO

000 00

ooooo

oooon

i.510

551,01.

05555

55000

OOOOO

51343

04105

34426

74262

17'16

15677

75120

0744

onooo

30000

ooooo

000 35

1-511.

OOOOO

01.21*3

ooooo

OOOOO

30000

03172

D3122

11071

02455

OOOOO

ooooo

:.520

OOOOO

ooooo

OOOOO

oonoo

55553

55555

55554

'4440

57423

74443

43424

05665

55555

55335

73333

■'$21*

33333

55555

55353

53357

33533

33333

33335

55555

33573

33333

siiss

33355

1-530

55555

5555 =

6555 3

35733

33333

33555

55':55

55555

55533

57333

33333

1153".

55353

736 33

33333

3 33 33

20552

12661

1*3101

J0151

12561

01000

10114

46000

51200

04531

10722

46000

1.51.0

OOOOO

4504

OOOOO

74410

01*315

OOOOO

02204

OOOOO

ooooo

04504

1.5141,

OOOOO

onooa

OOOOO

ooooo

OOOOO

oooon

OOOOO

00005

77777

77776

1.550

OOOOO

oonoo

n oono

OOOOO

onooo

30000

00007

OOOOO

noooo

OOOOO

00001

1.551,

ooooo

00000

OOOOO

00 04

ooooo

10000

OOOOO

ooooo

00226

20060

ooooo

00021

•■B60

11701

54335

06020

4576

31200

04625

11403

37673

ooooo

00002

oonoo

ooooo

OOOOO

1.551.

20120

00001

01000

4S12

ooooo

oonoo

1)0030

30000

ooooo

04521

01*000

07244

51000

45000

1.570

ooooo

0057

51300

04627

55710

54300

01000

04640

61000

46000

51500

04527

61500

00001

I-S7I.

20120

ooooo

4511

1*3052

04000

1462 3

45000

57225

03310

04523

53210

Q3120

04bOO

53710

46000

1.600

10265

57510

00006

46000

71500

001

43773

20535

15667

11775

36667

2 0637

54650

52510

00005

45000

1.601.

71600

00006

1.3771

2 0545

15567

11773

55557

20626

54650

52510

00002

46000

71600

00002

43772

20532

-610

1E667

11775

36557

2 0542

51*650

52S10

00002

45000

71600

00002

43772

20536

15667

11776

36657

20536

1.611.

51,650

52S10

00006

4 3752

15457

52610

00005

* 371*1*

2151*4

15657

61500

00001

03140

04621

71600

00226

-.620

711.00

04521

61000

4 50 00

205i*t

1276 4

51*710

loeii

22502

54640

54115

54446

03210

4560

07020

04560

1-62 It

03350

04^32

14155

4 60 00

04000

04532

IblOOO

46000

20140

OOOOO

00002

OOOOO

;-630

22227

36727

20503

1521i

20701

12661

35771

53525

20506

15160

63410

22244

73113

11505

03320

04530

-631.

56357

041*00

04637

66322

03150

04640

04430

04637

67545

05520

464

55300

43400

04300

04640

10677

l.6«0

OOOOO

noooo

61000

«50oa

71400

07774

43056

76600

65211

13777

51307

7774H-

204Z3

56500

713

00007

■~e>*it

01.000

04632

61000

46000

OOOOO

1.63

55555

5 5555

77777

7777'

77777

'7700

77777

'7777

77777

70000

■•65',

77777

7777

0000

7777'

77777

77000

OOOOO

77777

OOOOO

OOOOfl

77777

77700

OOOOO

-660

'7777

70000

OOOOO

ooooo

77770

OOOOO

77000

onooo

oonoo

OOOOG

OOOOO

ooooo

1*661.

17201.

001100

OOOOO

ooon

172 35

OOOOO

noooo

OOOOO

17266

20000

ooono

OOOOO

17317

61*000

OOOOO

ooooo

1.670

17351.

7O40O

OOOOO

ooooo

17405

05600

noooo

0000

17437

50220

000 no

OOOOO

17474

51132

OOOOO

ooooo

1.674

17525

75360

1.0000

ooooo

17557

31*654

eiOOOO

ooooo

17614

52013

71000

OOOOO

17645

54416

67200

ooooo

1.70

17677

21522

1*5040

ooooo

17731*

430123

'>7124

ooooo

17765

53630

40751

OOOOO

2002/

165 76

61143

20000

^701.

2 0061.

3415 7

11676

2000

20115

1.3712

74135

42400

20145

74n5>

63161*

73100

20201*

251*34

43011

01*750

Figure 1-13-10. Central Memory Dump (Cont'd)

60407000 D

1-13-13

PROGRAM LIBRARY AND SYSTEM 14

UTILITY CONTROL CARDS

PROGRAM LIBRARY UTILITY CONTROL CARDS

The following control cards are provided by KRONOS to enable the user to maintain a
program library,

MODIFY Edits a Modify -formatted program library file

OPLEDIT Removes modification decks and identifiers froim a Modify-formatted
program library file

UPDATE Edits an Update-formatted program, library file

UPMOD Converts an Update-formatted programi library file to a Modify-

formatted program library file

MODIFY CARD

The MODIFY control card edits a Modify-foraxiatted program library file.

The control card format is:

MODIFY(pi.p2,....Pn)

Pjj Any of the following in any order:

I Use directive input from file INPUT. If the

I option is omitted, file INPUT is assumed.

I=lfn. Use directive Input from file Ifn^.

1=0 Use no directive input.

P Use file GPL for the old program library.

If the P option is omitted, file GPL Is
assumed.

P=lfn2 Use file Ifng for the old program library.

P=0 Use no old program library

C Write compile output to file COMPILE. If

the C option Is omitted, file COMPILE is
assumed.

C=lfn3 Write compile output to file Ifng.

C=0 Write no compile output.

N Write new program library on file NPL.

N=lfn^ Write new program on file Ifn^.

N=0 Write no new program library. If this option

is omitted, N=0 is assumed.

S Write source output on file SOURCE.

S=lfn5 Write source output on file Ifn^.

S=Ci Write no source output. If this option Is

omitted, S=0 Is assumed.

60407000 D

1-14-1

L List output on file OUTPUT. If the L option

is omitted, file OUTPUT is assumed.

L=lfng List output on file Ifng.

L=0 List no output.

LO Select list options: ECTMWDS

LO=chars Selects up to seven list options which can
be any of the following:

E Errors

C Directives other than INSERT,
DELETE, RESTORE

T Input text

M Modifications made

W Compile file directives

D Deck status

S Statistics

I Inactive cards

A Active cards

A Write compressed compile file.

D Ignore errors.

F Modify all decks.

U Modify only decks mentioned on DECK

directives; F overrides the U option.

NR Do not rewind the compile file.

X Rewind input and output files, set A option,

and call the COMPASS assembler when
modification is complete.

X=prog Rewind input and output files, set A option,

and call the processing program prog when
modification is complete.

X=0 Do not call another processing program. If

this option is omitted, X=0 is assumed.

Q Rewind the output file, set A option, and call

the COMPASS assembler when modification
is complete.

Q=prog Rewind the output file, set A option, and

call the prog assembler when modification
is complete.

Q=0 Do not call another processing program. If

this option is omitted, Q=0 is assumed.

Z If this parameter is present, the MODIFY

control card contains the input directives
following the terminator. When this para-
meter is specified, the I parameter is ignored.

NOTE
Do not place another terminator
after the directives.

1-14-2 60407000 D

CV=f)3 Convert 64 character set OPL to 63 character

set OPL.

CV=64 Convert 63 character set OPL to 64 character

set OPL.
The following parameters can be entered only if the X or
Q options are selected.

CB Set assembler argument B=LGO. If the CB

option is omitted, B=LGO is assumed.

CB=lfnr, Set assembler argument B=lfn^. ,

CB=0 Set assembler argument B=0.

CL Set assembler argument L=OUTPUT.

CL=lfn8 Set assembler argument L=lfn8.

CL=0 Set assembler argument L=0. If this option

is omitted, L=0 is assumed.

CS Set assembler argument S=SYSTEXT. If the

CS option is omitted, S=SYSTEXT is assumed.

CS=llfng Set assembler argument S=lfng. t

CS=0 Set assembler argurtient S=0.

CG Set assembler argument G=SYSTEXT.

CG=lfnj^Q Set assembler argument G=lfnjQ. t t

CG=C( Set assembler argument G=0. If this option

is omitted, CG is defined by the CS option.

For a more detailed description of Modify, refer to the Modify Reference Manual.

OPLEDIT CARD

The OPLEDIT control card removes modification decks and identifiers from a Modify-
formatted program library file.

The control card format is:

OPLEDIT(Pj. Pg, . . . , pj

Pjj Any of the following in any order:

I Use directive input from file INPUT. If the

I option is omitted, file INPUT is assumed.

Use directive input from file Ifn^.

Use no directive input.

Use file OPL for the old program library.
If the P option is omitted, file OPL is
assumed.

Use file lfn2 for the old program library.

Use no old program library.

N Write new program library on file NPL.

Ifn.^

=lfn2

t The desired file is retrieved from the system.
tt The desired file is a local file.

60407000 D 1-14-3

N=lfn3 Write new program library on file lfn3.

N=0 Write no new program library. If this option

is omitted, N=0 is assumed.

L List output on file OUTPUT. If the L option

is omitted, file OUTPUT is assumed.

L=lfn4 List output on file Ifn^.

L=0 List no output.

M=lfn5 Write output from *PULLMOD directives on

file lfn5. If this option is omitted, M=MODSETS
is assumed.

LO'^x Set list options x; each bit in x, if set,

turns on the corresponding option.

001

Errors

002

Directives

004

All other input cards

010

Modifications made

020

Directives processed from the

program library

040

Deck status

100

Directory lists

200

Inactive cards

400

Active cards

If this option is omitted, x=177 is assumed
(that is, the first seven options listed).

F Modify all decks.

D Debug; ignore errors.

U Generate *EDIT directives for all decks.

U=0 Generate no *EDIT directives.

If the U option is omitted, generate *EDIT
directives for common decks.

The OPLEDIT routine is used to completely remove specified modification decks and
modification identifiers from an OPL. It can also be used to determine the contents
of a specified modification set on an OPL file. The OPLEDIT parameters are similar
to the MODIFY parameters. However, the only input directives are as follows:

*PURGE name

*PURGE name, *

name Modification identifier to be purged

* Indicates that name and all identifiers thereafter are to be

purged

*EDIT dckl

*EDIT dckl.dckn

dckl Deck to be edited

dckl.dckn Edit all decks from dckl to dckn

1-14-4 60407000 D

The EDIT directive requests OPLEDIT to edit a program deck and transfer it to the
new program library. The deck names specified normally are the decks that contain

the modification identifiers.

The PULLMOD directive is available to reconstruct a modset to a deck and write it on
a specified file.

*PULLMOD d moda, modb, .... modn

d Valid OPLEDIT delimiter

moda, modb, Modnames to be pulled and generated onto the file specified

.... modn by the M option (MODSETS is assumed by default)

The PULLALL directives also make it possible to generate a modset that contains the net
effect of all current modsets or all modsets added after and including a specific mod-
set.

* PULLALL
*PULLALL, modn

modn First modset to be included; all modsets following modn are also

included.

Example 1

The user requires a composite modset of all mods that have been added to a deck.
The following cards performi this function.

job card
USER(. . . )

OPLEDIT(M=MOD, . . . )

-EOR-

*PULLALL

*EDIT ITD

-EOI-

Plle MOD would contain:

*IDENT*'''*^=***
*DECK ITD

-EOI-

File MOD plus the ITD OPL, which contains no mods, builds the latest ITD OPL.

Example 2

The user requires 3 modsets to be combined into one composite modset. The following
cards perform this function.

job card

USER(. . . )

OPLEDIT(M=MOD, . . . )

-EOR-

*PULLALL. 1TD27

*EDIT, ITD

-EOI-

60407000 D 1-14-5

File MOD would contain:

*IDENT*******
*DECK ITD

-EOI-

File OPL contains ITD.lTDl, 1TD2, . . . , 1TD27, 1TD28. The resulting MOD file contains
1TD27 and 1TD28.

Example 3

The user requires a noncomposite mod for file MOD. The following cards per-
form this function.

job card
USER(. . . )

OPLEDIT(M=MOD, ...)

-EOR-

*PULLMOD, 1TD27, 1TD28

*EDIT, ITD

-EOI-

File MOD would contain:

1TD27

*IDENT 1TD27
*DECK ITD

1TD28

*IDENT 1TD28
*DECK ITD

-EOI-

It is not possible to pull modsets implicitly; that is, *PULLMOD A. B is illegal. Also,
-PULLMOD A, * does not pull modset A sind all modsets that follow (as on the *PURGE
directive). Rather, it pulls modset A and modset *.

Modnames requested are pulled only from edited decks. The *PULLMOD and >:= PURGE
directives may be used in any order and combination.

The modsets generated are in a form suitable for use by MODIFY as follows:

*READ, file, *

or
*READ, file, ident

That is, each modset is a separate record, with ident being the first card. The *PULLALL
modset, if any, is the first record on the file. The file specified by the M option is returned
before, and rewound after use.

1-14-6 60407000 D

UPDATE CARD

The UPDATE control card edits an Update-formatted program library file.
The control card format is :

UPDATE(pi,P2,
Pi

.Pn>

Any of the following in any order:

A Sequential- to- random program library copy

B Random-to-sequentlal program library copy

C Write compile file output on COMPILE. If

the C option is omitted, file COMPILE is
assumed.

C=lfn. Write compile file output on Ifn^.

C = Write no compile output.

D Compile output has 80 columns for data; if D

is omitted, compile output has 72 columns
for data.

E Update rearranges the directory to reflect the

actual order of decks on the program library.
If E is omitted, the old program library
directory is not edited.

F Full update; all decks are compiled. If F is

omitted, corrected decks and those named on
COMPILE directives are processed.

G=lfn2 Output from PULLMOD directives is written

on lfn2. Any rewind option applying to the
source file also applies to this file. OUTPUT
is not a valid file for this option. If G is
omitted, pulled modifications are appended to
the source file.

I Input is on file INPUT. If the I option is

omitted, file INPUT is assumed.

I=lfno Input comprises next record on lfn3.

K Compile output decks to be written on file

COMPILE in COMPILE directive sequence.

K=lfn4 Compile output decks to be written on Ifn^ in

COMPILE directive sequence. If this option
is omitted, output is determined by the C
option.

L=char char is a string that specifies any of the A,

F, and through 9 list options. If this option
is omitted, options A, 1, 2, 3, and 4 are
selected. Any use of suppresses listing.

M Merge input is on file MERGE.

M=lfn5 Merge input is on file Ifn^. If M option is

omitted, there is no merge file.

N New program library to be written on file

NEWPL.

60407000 D

1-14-7

N=lfng New program library to be written on file

Ifng. If N option is omitted, no new pro-
gram library is written.

O List output to be written on OUTPUT. If

the O option is omitted, OUTPUT is assumed.

0=lfn7 List output to be written on Ifny. If O

option is omitted, OUTPUT is assumed.

P Use file OLDPL for the old program library.

If the P oiition is omitted, OLDPL is assumed.

P=lfng Use file Ifng for the old program library.

If this option is omitted, OLDPL is
assumed.

Q Only decks on COMPILE directives are

processed. If Q is omitted, corrected
decks and those named on COMPILE
directives are processed.

R No rewinds are issued for the program

libraries, compile file, or source file.

R=char Each character in the string char indicates

a file to be rewound before and after the
Update run.

C Compile

N New program library

P Old program library and merge

library

S Source and PULLMOD

Files not specified in char are not re-
wound. If R is omiitted, files are
rewound before and after the Update run.

S Source output written on file SOURCE.

S=lfn9 Source output written on file Ifng. If S

is omitted. Update does not generate a
source output file unless the source output
is specified by T.

T Source output excluding common decks on

file SOURCE.

T=lfnio Source output excluding common decks on

file Ifnio. If T is omitted, no source
output unless source output is specified
by S.

U Update execution is not terminated by

normally fatal errors. H U is omitted.
Update execution terminates upon en-
countering a fatal error.

W TTie new program library (refer to N

option) will be a sequential file. If W
is omitted, the new program library will
be a random file (unless it is a magnetic
tape file).

1-14-8 60407000 D

X Compile file is in compressed format. If X

is omitted, the compile file is not in com-
pressed format.

7. The input file (refer to I option) is assumed

to be in PCS compressed format. This para-
meter applies to the directives input file only;
it does not apply to files specified by READ
directives. If Z is omitted, the input file is
a normal, coded file.

8 Compile file output is composed of 80- column

line Images. If this option is omitted, com-
pile file output is composed of 90-column line
images.

*=char The master control character (first character
of each directive) for this Update run is char
which can be any character having a display
code octal value in the range 01 through 54
except for 51 and 52 (the open and close
parentheses). If this option is omitted, the
master control character is *.

/=char The comment control character for this Update
run is char which can be A through Z,
through 9, or +-*/$=. Note, however, that
the character should not be changed to one of
the abbreviated forms of directives unless
NOABBREV is in effect. If this option is
omitted, the comment control character is
a slant bar.

Note that the UPDATE control card is processed in product set format. For a more
detailed description of Update, refer to the Update Reference Manual.

60407000 D 1-14-9

UPMOO CARD

The UPMOD control card converts an Update-formatted program library file to a
Modify-formatted program library file.

The control card format is:

UPMOD(pj, pg. . . . , Pn)

p. Any of the following in any order:

P Update program library from file OLDPL.

If the P option is omitted, file OLDPL is
assumed.

P=lfn, Update program library from file Ifnj^.

N Modify program library on file OPL.

N=lfn2 Modify program library on file lfn2.

M Modify progranti library name is OPL. If

the M option is omitted, file OPL is as-
sumed.

M=lfn3 Modify program library name is lfn3.

F Convert to file mark

NR Do not rewind file Ifn^^.

The Update file must be in sequential format. A random Update file must first be
changed to sequential format via Update before being submitted to UPMOD for conversion.
Unless otherwise specified, only one record from the Update file is converted. After
the Modify OPL has been created, no references should be made to modset identifiers
present on the Update library. The new OPL should be treated as any other program
library created by a Modify creation run.

SYSTEM UTILITY CONTROL CARDS

The following utility control cards aid the system programmer in manipulating the
system.

FAMILY Specifies the name of the systera's normal family of

permanent file devices. FAMILY can be used by any
' system origin job.

KRONREF Generates a cross-reference listing of system symbols.

SYSEDIT Modifies the system library. SYSEDIT can be used by

system origin jobs or users with system origin privileges
(if the system is in DEBUG mode).

1-14-10 60407000 D

FAMILY CARD

The FAMILY control card allows the user to change the family name associated with
his job.

The control card format is:

FAMILY(familyname)

familyname 1- to 7-character name of a family of permanent file

devices

If an alternate family of permanent file devices is introduced into the system without
a VALIDUS file, the job to create VALIDUS could include a FAMILY card identifying |

that family. If the familyname parameter is omitted, the default family name is. used.
If the normal system has a default family name but the alternate system does not,
the user can specify the edternate system by submitting the following card.

FAMILY. 0.

The FAMILY card can be used by any system origin job. If the card is included in

any nonsystem origin job, the job is aborted and the system issues the following message

to the user's dayfile.

ILLEGAL CONTROL CARD.

If the default family is required but not known to the user, a

FAMILY,
card will set the default fam^ily name.

Refer to Device Residence, section 2, for further information about families.

60407000 D 1-14-11

KRONREF CARD

The KRONREF control card generates a cross-reference listing of system symbols
used by decks on a MODIFY OPL.

The control card format is:

KRONREF (P=lfni, L=lfn2 . S=lfn3 . G=lfn4 )

P=lfn2 OPL input from file Ifnj. If the P option is omitted or

P alone is specified, file OPL is assumed.

L=lfn2 List output on file lfn2. If the L option is omitted or L

alone is specified, file OUTPUT is assumed.

S=lfn3 System text from overlay Ifns- If the S option is omitted

or S alone is specified, file SYSTEXT is assumed.

G=lfn4 System text from local file lfn4. If G is omitted, system

text is acquired as specified or defaulted by the S option.
If G alone is specified, local file TEXT is used. Use of
the G option overrides any S specification.

The names of programs on the OPL are listed for those decks that reference the
following.

• PP direct cell locations defined in lfn3 or lfn4

• PP resident entry points defined in lfn3

• Monitor functions

• Central memory pointers (in low core) defined in Ifng of Ifn^

• Central memory locations (in low core) defined in lfn3 or lfn4

• Control point area words defined in lfn3 or lfn4

• Dayfile message options

• File types and mass storage constants

• Job origin types, queue types, and priorities

• Error flags referenced

• Common deck calls

• PP packages called

1-14_12 60407000 D

SYSEDIT CARD

The SYSEDIT control card enables modifications to be made to the system library.

The control card format is:

SYSEDIT(pi, P2, • . . . Pn)

p. Any of the following in any order:

I Directive input is on file INPUT. If the

I option is omitted, file INPUT is assumed.

I=lfn| Directive input is on file Ifn^.

1=0 No directive input.

B Binary change cards are on file LGO. If

the B option is omitted, file LGO is as-
sumed.

B=lfn2 Binary change cards are on file Ifng.

B=0 No binary change cards.

L List output on file OUTPUT.

L=lfn3 List output on file Ifng.

L=0 No list output. If the L option is omitted,

the system assumes L=0.

R Restore to initial deadstart system.

R=n Restore to copy n of the system. The

system copy number is printed on the out-
put listing.

R=0 No system file restoration. If the R option

Is omitted, the system assumes R=0.

C Checkpoint the system following SYSEDIT.

If the C option Is omitted, no checkpoint
Is performed unless the system was gener-
ated employing the alternate system library
residency feature. System using the alter-
nate library feature are check-pointed
automatically following SYSEDIT.

If the job Is not of system origin, DEBUG must be set from the system console to
allow changes to the operating system. The user must also be validated for system
origin privileges.

60407000 D 1-14-13

The following are the valid input directives to SYSEDIT. f

*An, nn, tvj 'rec|,ty2/rec2, . . . t
tyn'reCjj

*CM, tyi/reci,ty2/rec2, . ...
tyn/recjj

*MS, tyl/reci, ty2/rec2, ....
tyn/rec^

^DELETE, tyi/reci,ty2/rec2, . • • ,
tyjvec^

*D, tyi/reci, ty2/rec2, ....
tyn/rec^

Specifies the alternate device to be used
instead of the system device(s) for storing
ABS, OVL, and PP tj^pe routines; nn is
either the EST ordinal or the device type.

Define record recj of type tyj^ as being
central memory resident.

Define record rec^ of type ty^^ as being
mass storage resident.

Delete record rec^ of type ty^ from the
system library. Type tyj^-ULlB is
ignored; user libraries cannot be de-
leted.

*FILE,lfn
or
*FILE,lfn. NR

*IGNORE. tyi/reci, ty2/rec2, ....

tyn/j'ec^

*PROC. reci, rec2, .... rec^

» . . . »

*RENAME,oej-nej, oe2-ne2
oen-nen

*PPSYN, nam/namj, nam2, . . . ,

nam.

*SC, tyi/reci,ty2/rec2, . ...
tyn/recn

Define file Ifn as a file containing system
changes. If NR is not present, Ifn
is rewound before processing.

Do not process record rec^ of type ty^
when it appears on the system change
file.

Define record recj of type TEXT as
procedure file.

Rename CPU entry names oej to ne..

Add entries to system library to provide
synonym nam^ for the FPU program nam.

Define record reci of type ty; as product
set format control cards. The control card
parameters will be processed in product
set formiat (refer to Control Card Format,
section 5).

t Refer to the CATALOG control card for record types.

1-14-14

60407000 D

LOADERS 15

System loading is done by the following loaders.

• LINK relocatable loader

• CDC CYBER reloc table loader

• Absolute overlay loader (LDR)

• Chippewa-formatted overlay loader (EXU)

A relocatable loader provides high-speed transfer of relocatable binary programs from
storage devices to central memory. It is called when a job requires loading of a file
or program in relocatable format. The LINK loader is provided for compatibility
with previous operating systems. It provides many of the features available with the
CDC CYBER relocatable loader but differs in the following respects.

• The LINK loader does not allow multiple sequential loads such as those
available with the CDC CYBER loader through the LOAD card.

• It allows only the Cnnnnnn origin optional OVERLAY directive parameter to
specify the origin of the overlay (refer to the Loader Reference Manual).

• It does not recognize the global library set specified by the LIBRARY control
card.

• It uses the first library of the global library set as an alternate default
library. This library Is; searched after the libraries specified on the LINK
card and the libraries specified (if any) in LDSET tables, but before the de-
fault library SYSLIB.

Additional information and a description of the LINK control card is discussed later
In this section. For a complete description of the CDC CYBER loader, its control
cards and processing, refer to Oie Loader Reference Manuiid.

The overlay loaders provide direct transfer of absolute overlays or binary data from
storage devices to central memoi^y. An absolute record consists of code or data that
is not relocatable and must be loaded at specific core locations. Because the overlay
loaders perform no address manipulation, absolute code can be loaded more rapidly
than relocatable code. For fvirther information on the ovez-lay loaders and the LDR
and EXU requests, refer to section 11 in volume 2 of the reference manual.

60407000 D 1-15-1

LINK RELOCATABLE LOADER

The LINK relocatable loader is called by the absolute overlay loader as the result of
a LINK call card request to load a file that is in relocatable binary format. Input to
the LINK relocatable loader is object code generated by compilers and assemblers
according to specifications for loader tables. Subprograms assembled or compiled
independently, in relocatable or binary format, can be loaded and linked to each other
or to library subroutines by the loader. The loader issues diagnostic messages to
the dayfile and generates memory maps when requested.

The loader can generate overlays that are written on a specified file in absolute format.
These overlays can be loaded later by the absolute overlay loader.

MEMORY MAP

Following completion of loading, an optional map of the user's field length is produced
on file OUTPUT. A full map includes:

• Names, length, and positions of entry points with a sublist of all programs
referencing the entry points

• Names and locations of common blocks

• Total length of all loaded programs and common blocks

• Length of the loader and its tables

• Unsatisfied external references

Map options can be selected using the MAP control card. (Refer to Loader Reference
Manual. )

LINK CARD

The LINK control card specifies directives for the LINK loader. The LINK routine
processes the loading of relocatable programs and generating of absolute binary files
for present or future executuion. LINK does not load execute-only mode files.

The control card format is:
LINK(pj,P2, ...,Pj^)

■^1

p. Any of the following in any order:

F=lfn-, Loads from file Ifn^.

F omitted The system assumes lfn]=LGO.

P Satisfy external references from program

library SYSLIB.

P=lfn2 Satisfy external references from program

library lfn2.

P omitted Satisfy external references from program

library SYSLIB.

1-15_2 60407000 D

B=lfrL3

B=0

B omitted

L=lfrL4

L=0

L omitted

E=name

LO F=c. . . c

Write loaded program on file LGOB.

Write loaded program on file lfn3.

No loaded program to write.

The system assumes B=0.

Write load map on file Ifn^.

No map

The default file name is OUTPUT but no
map is produced unless either errors
occur or some map options (LO parameter)
are explicitly selected.

Load program with the specified entry
point name from file Ifnj. If this option
is selected, Ifn^ must be a user library
file.

Set map options S and B.

Set map option S for statistics and errors
and any of the following characters.

B Block assignments

E Entry points

X External references and entry

points.

Execute loaded program.

Since the loader resides in the program area, the user must have enough memory
available to load the largest overlay in the file.

Many of the options on the control card are self-explanatory; however, the following
examples illustrate some of the features of the LINK program.

If the user has generated a library file (refer to the description of the LIBGEN
control card), he can load any program on that file.

For example, assume the user has file LIBl attached to a control point. LIBl
contains routines TESTl, TEST2, and TESTS. TESTS has the entry point TESTSE.
The control card :

LINK(F=LIB1, E=TEST3E, X)

loads the routine TESTS and begins execution at entry point TESTSE.

60407000 D

1-15-S

A more common example illustrates a relocatable load that generates an overlay
using several different user libraries. The control cards:

MAP(FULL)

LIBRARY{M YLIBI )

LINK(F=BINREL, P=MYLIBO, L=MYMAP, B=BINABS)

generate an absolute overlay format [level (0,0) unless BINREL contains overlay
control cards specifying other levels] of file BINREL and write it on file BINABS.
A full load map is written on file MYMAP. The externals are satisfied from libraries
in the following order.

MYLIBO

LDSET tables (if any)

M YLIBI

SYSLIB

NOTE

The CDC CYBER loader does not satisfy exter-
nals from libraries in this order. (Refer to
Loader Reference Manual. )

The following example illustrates the previous example using the CDC CYBER reloca-
table loader. The control cards:

LIBRARY(MYLIBl)

MAP(FULL)

LDSET(LIB=MYLIBO, MAP=/MYMAP)

LOAD(BINREL)

NOGO(BINABS)

generate an absolute overlay format of the file BINREL and write it on file BINABS,
with map written on MYMAP. The externals are satisfied from libraries in the follow-
ing order.

MYLIBl

MYLIBO

LDSET tables (if any)

SYSLIB

1-15-4

60407000 D

CHARACTER SETS

KRONOS 64-CHARACTER SET FOR TIME -SHARING TERMINALS

ASCII CODE TERMINALt |

CORRESPONDENCE CODE

TERMINALttI

INTERNAL
DISPLAY CODE
(6/12-BlT OCTAL)

STANDARD PRINtJ

APL PRINT 1

STANDARD PRINT ]

APL PRINT 1

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(7-BIT OCTAL)

CHAR.

CODE
(7-BIT OCTAL)

;

072

27 6

•

1 53

121

10 I

341

171

102

342

166

303

14 -.5

172

104

344

052

305

145

1 12

112

306

146

163

107

347

043

1 10

350

046

31 1

151

031

1 1

312

152

103

1 2

1 13

353

032

314

154

106

115

355

141

116

3561

122

317

157

105

120

360

013

321

161

133

322

162

051

123

363

045

324

164

002

125

365

062

126

366

061

327

167

165

330

170

142

131

371

147

132

372,

124

060

144

261

040

262

020

063

160

264

004

065

010

066

130

267

150

270

070

071

064

053

055

023

067

055

275

067

252

120

070

013

257

007

(

050

(

053

(

064

(

153

)

251

)

252

)

144

)

1 II

044

176

004

171

275

245

023

010

t THE

. OCTAL C0D1

ES LIS

TED FOR ASC

II COD

E TERMINAL

S ARE

SHOWN WIT

H EVEN '*^'"

PARITY (NORMAL)

tt THE OCTAL CODES LISTED FOR CORRESPONDENCE CODE TERMINALS ARE SHOWN
WITH ODD PARITY (NORMAL)
60407000 D

1-A-l

ASCII CODE TERMINAL

CORRESPONDENCE

CODE TERMINAL

INTERNAL
DISPLAY CODE
(6/12-BIT OCTAL)

STANDARD PRINT

APL PRINT

STANDARD PRINT

APL PRINT

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
{7-BIT OCTAL)

CHAR.

CODE
(7-BIT OCTAL)

(SPACE)

240

(SPACE)

240

(SPACE)

100

(SPACE)

100

254

073

056

121

243

••

041

160

••

040

333

273

1/4

001

153

6 1

335

072

'/2

001

III

245

173

010

023

042

050

••

1 1 1

070

—

137*

306

067

163

041

251

♦

130

064

246

137

150

144

047

113

1 II

032

077

321

007

1 33

074
276
300

243
047
044

NULL
NULL

<
>

160
150
004

72
73
74

>
<

020

134

077

NULL

007

176
273

042
074

NULL

020
073

76
77

153

140
341

NULL
a

NULL

NULL
a

7600
7601

101

171

342

102

166

7602

143

303

172

7603

344

104

052

7604

145

305

112

7605

146

134

163

023

7606

347

107

043

7607

350

110

046

76 10

151

311

031

76 1 1

152

312

103

7612

353
154

336
314

032
106

NULL

7613
76 14

106

355

115

141

7615

356

116

122

76 16

157

317

105

76 17

360

100

013

00!

7620

16 1

134

133

101

7621

162

322

051

762'>

363

123

045

7623

164

324

002

76 24

365

125

062

76 25

366

126

061

76 26

167

327

165

76 27

170

330

142

76 30

371

131

147

7631

3AE3A

♦on TTY MODELS HAVING NO UNDERLINE, THE BACKARROW (H TAKES ITS PLACE

l-A-2

60407000 D

ASCII CODE TERMINAL

CORRESPONDENCE CODE

TERMINAL |

INTERNAL
DISPLAY CODE
(6/12-BIT OCTAL)

STANDARD PRINT

APL PRINT 1

STANDARD PRINT

APL PRINT 1

CHAR.

CODE

(8-BIT OCTAL

CHAR.

CODE
{8-BIT OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

372

132

124

7632

173

■

140

NULL

7633

174

246

040

130

7634

175

}

374

NULL

7635

176

175

NULL

7636

DEL

377

DEL

377

NULL

7637

NUL

000

NUL

000

NUL

075

NUL

075

7640

SOH

201

SOH

201

SOA

166

SOA

166

7641

STX
ETX

202
003

STX
ETX

202
003

EOA
NULL

064

EOA
NULL

064

7642
7643

EOT

204

005

EOT

ENQ

ACK

BELL

204
005

006

207

EOT
NULL

ACK
NULL

174

EOT
NULL
NULL
NULL

174

7644
7645
7646
7647

ENQ

067

ACK

006
207

BELL

210

135

7650

01 1

057

7651

012
213
014

LF
VT
FF

012
213
014

LF
NULL

NULL

156

LF
NULL
NULL

156

7652
7653
7654

V T

F F

215

155

7655

216

UCS

034

UCS

034

7656

SI
DLE
DCI

017
220
021

SI
DLE
DCI

017
220
021

LCS
NULL
NULL

037

LCS
NULL
NULL

037

7657
7660

7661

DC2

022

DC2

022

NULL

7662

DC 3

023

DC3

023

NULL

7663

DC4

024

DC 4

024

STO

054

STO

064

7664

NAK

225

NAK

225

NAK

001

NAK

001

7665

SYN

226

SYN

226

075

7666

ETB

027

ETB

027

EOB

136

EOB

136

7667

CAN

SUB

030

231
232

CAN

EM
SUB

030
231
232

DEL
NULL
NULL

177

DEL
NULL
NULL

137

7670
7671
7672

ESC
FS
GS

033

234
035

ESC
FS

033
234
035

NULL

076

PF
NULL
NULL

076

7673
7674
7675

NULL

036
237

NULL

036
237

NULL

NULL
NULL
NULL

7676
7677
7400
7401

300

044

020

004

176

—

042

NULL

.—

020

7402

NULL
NULL

CNL

NULL

001

CNL
NULL

001

7403
7404

NULL
NULL

7405
7406

NULL

7407

60407000 D

l-A-3

KRONOS 63 -CHARACTER SET FOR TIME-SHARING TERMINALS

ASCII CODE TERMINALt |

CORRESPONDENCE

CODE

TERMlNALttI

INTERNAL
DISPLAY CODE
(6/12-BIT OCTAL)

STANDARD PRINT~1

APL PRINT 1

STANDARD PRINT 1

APL PRINT !

CHAR.

CODE

(8-BST OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(7-BlT OCTAL)

CHAR.

CODE 1
(7- BIT OCTAL)]

NULL
A

00
1

101

341

171

102

342

166

303

143

172

104

344

052

305

145

112

306

146

163

107

347

043

1 10

350

046

311

151

031

1 1

312

152

103

1 2

1 13

353

032

314

154

106

115

355

141

116

356

122

317

157

105

120

360

013

01 3

321

161

133

322

162

051

123

363

045

324

164

002

125

365

062

126

366

061

327

167

165

330

170

142

131

371

147

132

372

124

060

144

261

040

262

020

063

160

264

004

065

010

066

130

267

150

270

070

071

064

053

055

023

067

055

275

067

252

120

070

013

257

007

(

050

(

053

(

064

(

153

)

251

)

252

)

144

)

1 II

176

004

171

275

245

023

010

l-A-4

t THE OCTAL CODES LISTED FOR ASCII CODE TERMINALS
PARITY (NORMAL)

tt THE OCTAL CODES LISTED FOR CORRESPONDENCE CODE
WITH ODD PARITY (NORMAL)

ARE SHOWN WITH EVEN
TERMINALS ARE SHOWN

60407000 D

ASCII CODE TERMINAL

CORRESPONDENCE CODE

TERMINAL

INTERNAL
DISPLAY CODE
(6/12-BIT OCTAL)

STANDARD PRINT

APL PRiNT

STANDARD PRINT

APL PRINT

CHAR.

CODE
(8-BlT OCTAL)

CHAR.

CODE
(8-BIT OCTAL)

CHAR.

CODE
(7-BIT OCTAL)

CHAR.

CODE
(7-BIT OCTAL)

(SPACE)

240

(SPACE

240

(SPACE)

100

(SPACE)

100

254

073

056

•

121

042

•■

041

•■

1 II

••

040

333

273

1/4

001

153

6 1

335

072

001

III

072

;

276

;

153

;

121

047

1 13

1 1 1

032

246

134

150

023

I.F

215

012

2)5

012

NULL

NULL
LF

66
67

156

t
#

336

243

042
336

NULL
#

020
070

70
71

160

074
276

243
047

NULL
NULL
NULL

NULL

160

1 50

72
73
74

(ESC 1)

NULL

077

321

007

133

(ESC 2)

NULL

;

273

;

074

153

073

NULL

NULL
a

7600
7601

341

10 1

171

342

102

166

7602

143

303

172

7603

344

104

052

7604

145

305

112

€

112

7605

146

137

163

7606

347

107

043

7607

350

110

046

76 10

151

31 1

03 1

031

76 1 1

152

312

103

7612

353

—

100

032

004

7613

154

314

106

76 14

355

—

134

141

76 15

356

116

122

76 16

157

317

105

76 17

360

044

013

130

7620

161

246

133

7621

162

322

051

7622

363

123

045

7623

164

050

002

7624

365

125

062

76 25

366

126

061

76 26

167

(1)

327

165

76 27

170

330

142

76 30

371

131

147

76 31

60407000 D

l-A-5

ASCII CODE TERMINAL

STANDARD PRINT

CHAR.

(8.

CODE
Bit OCTAL)

APL PRINT

CHAR.

(8-1

CODE
BIT OCTAL)

CORRESPONDENCE CODE TERMINAL

STANDARD PRINT

CHAR.

CODE
(8-BIT OCTAL)

APL PRINT

CHAR.

CODE
(8-BlT OCTAL)

INTERNAL
DISPLAY CODE
(6/12-BIT OCTAL)

z
DLE
BELL
DC2
ETX
DC4
NAK
SYN
ETB
CAN

SON

HT
EOT

6S
NUL

SO
STX

SUB
ACK

a
\

RS
DEL

NL
ESC
NULL

X-ON

X-OFF

ENQ

372

220

207

022

003

024

225

226

027

030

231

213

201

041

017

210

Oil

204

035

000

014

216

202

173

175

232

006

246

134

174

176

243

234

036

377

237

033

300

245

140

137 t

021

223

005

c
DLE
BELL
DC2
ETX
DC4
NAK
SYN
ETB
CAN

VT
SOH

HT
EOT

6S
NUL

SO
STX

}

SUB
ACK
NULL

NULL
FS
RS
DEL
US
NL
ESC
NULL

X-ON

X-OFF

ENQ

132
220
207
022
003
024
225
226
027
030
231
213
201
251
017
210
01 1
204
035
000
014
216
202
140
374
232
006

077
I 15
324

234
036
377
237

033

175
173
335
306
021
223
005

z
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL

HT
NULL
NULL

NUL

NULL
NULL
NULL
NULL

NULL

NULL
NULL
NULL
NULL
NULL

NL
MULL
NULL

NULL

NULL
NULL
NULL

124

135
057

075
073
I 2 I

130
040

155

020
010

067

c
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL

HT
NULL
NULL

NUL
NULL
NULL
NULL

NULL
NULL
NULL

NULL
NULL
NULL
NULL
NULL

NL
NULL
NULL

V
NULL
NULL
NULL
NULL

124

135
057

075

00 1
101

007
141
002

155

144
023
064

7632

7633

7634

7635

7636

7637

7640

7641

7642

7643

7644

7645

7646

7647

7650

7651

7652

7653

7654

7655

7656

7657

7660

7661

7662

7663

7664

7665

7666

7667

76 70

7671

7672

7673

7674

7675

7676

7677

7400

7401

7402

7403

7404

7405

7406

7407

3AE6A

t ON TTY MODELS HAVING NO UNDERLINE, THE BACKARROW ( — ) TAKES ITS PLACE.

l-A-6

60407000 D

KRONOS STANDARD CHARACTER SET

CDC
GRAPHIC

ASCII

GRAPHIC

SUBSET

DISPLAY
CODE

HOLLERITH
PUNCH
(026)

EXTERNAL

BCD

CODE

ASCII

PUNCH
(029)

ASCII
CODE

•

001

8-2

12-1

6 1

12-1

12-2

12-3

12-4

12-5

12-6

12-7

12-8

1 1

12-9

ll-l

11-2

11-3

11-4

11-5

11-6

M-7

11-8

11-9

0-2

0-3

0-4

0-5

2 7

0-6

0-7

0-8

0-9

t TWELVE OR MORE ZERO BITS AT THE END OF A 60- BIT WORD ARE
INTERPRETED AS END-OF-LINE MARK RATHER THAN TWO COLONS.
END-OF-LINE MARK IS CONVERTED TO EXTERNAL BCD 1632.

60407000 D

3AEI3A

l-A-7

ASCII

HOLLERITH

EXTERNAL

ASCII

CDC

GRAPHIC

DISPLAY

PUNCH

BCD

PUNCH

ASCII

GRAPHIC

SUBSET

CODE

(026)

CODE

(029)

CODE

1 1

12-8-6

1 1

1 1-8-4

11-8-4

0-1

(

{

0-8-4

12-8-5

)

12-8-4

11-8-5

11-8-3

1 1-8-3

8-3

8-6

BLANK

5 5

NO PUNCH

.(COMMA)

0-8-3

.(PERIOD)

12-8-3

0-8-6

8-3

8-7

12-8-2

]

6 2

0-8-2

11-8-2

%tt

8-6

0-8-4

" (QUOTE)

8-4

8-7

—

_ (UNDERLINE)

0-8-5

ll-O

12-8-7

6 7

0-8-7

'(APOSTROPHE)

1 1-8-5

8-5

11-8-6

0-8-7

12-0

12-8-4

11-8-7

0-8-6

7 4

8-6

8-4

12-8-5

0-8-2

-»

^(CIRCUMFLEX)

12-8-6

11-8-7

|: (SEMICOLON)

; (SEMICOLON)

12-8-7

11-8-6

3AE6A

it IN INSTALLATIONS USING THE CDC 63 -GRAPHIC SET, DISPLAY CODE 00 HAS NO ASSOCIATED
GRAPHIC OR HOLLERITH CODE; DISPLAY CODE 63 IS THE COLON (8-2 PUNCH). THE
SELECTION OF THE 63- OR 64-CHARACTER SET FOR TAPES IS AN INSTALLATION OPTION.

l-A-8

60407000 D

ASCII/DISPLAY CODE AND EBCDIC /DISPLAY CODE CONVERSION

DISPLAY
CODE

ASCII

EBCDIC I

UPPERCASE

LOWERCASE

UPPERCASE

LOWERCASE I

OCTAL

CHAR

HEX

CHAR

HEX

CHAR

HEX

CHAR

HEX

•_

SUB

[

SUB

1 1

5 A

DLE

DCI

1 1

DC2

DC3

DC 4

0C4

3AETA

60407000 D

l-A-9

OISP
CO

LAY
DE

ASCII

EBCDIC 1

UPPERCASE

LOWERCASE

uppIrcase I

LOWERCASE |

OCTAL

CHAR

HEX

CHAR

HEX

CHAR

HEX

CHAR

HEX

NAK

SYN

ETB

CAN

¥ti

{

(

)

EOT

IGS

NUL

ETX

4 A

IPS

]

SOH

ENQ

STX

DEL

ACK

BEL

I US

{

IRS

—I

.F>rf

•
I

ESC

3AE8A

1-A-lO

60407000 D

CARRIAGE CONTROL CHARACTERS

CHARACTER

COMMAND

SPACE

SINGLE SPACE

EJECT PAGE BEFORE PRINT

SKIP ONE LINE BEFORE PRINT (DOUBLE SPACE)

SKIP TWO LINES BEFORE PRINT (TRIPLE SPACE)

SUPPRESS SPACE BEFORE PRINT

SUPPRESS SPACE AFTER PRINT

SKIP TO LAST LINE OF FORM BEFORE PRINT

SKIP TO FORMAT CHANNEL 1 BEFORE PRINT t

SKIP TO FORMAT CHANNEL 2 BEFORE PRINT t

SKIP TO FORMAT CHANNFI 3 BEFORE PRINT t

SKIP TO FORMAT CHANNEL 4 BEFORE PRINT t

SKIP TO FORMAT CHANNEL 5 BEFORE PRINT t

SKIP TO FORMAT CHANNEL 6 BEFORE PRINT t

SKIP TO FORMAT CHANNEL I AFTER PRINT

SKIP TO FORMAT CHANNEL 2 AFTtR PRINT

SKIP TO FORMAT CHANNEL 3 AFTtR PRINT

SKIP TO FORMAT CHANNEL 4 Ah ThR PRINT

SKIP TO FORMAT CHANNEL 5 AFTER PRINT

SKIP TO FORMAT CHANNEL 6 AFTER PRINT

CLEAR AUTO EJECT; REMAINDER OF LINE IS

NOT PRINTED

SET AUTO EJECT; REMAINDER OF LINE IS
NOT PRINTED

SELECT 6 LINES/INCH; tt REMAINDER OF
LINE IS NOT PRINTED

SELECT 8 LINES/INCH; 1 1 REMAINDER OF
LINE IS NOT PRINTED

3AE9A

fNo space after print. For all other control characters, a line
feed is issued after print.

■ft Used only on the 512 and 580 line printers. The deselection of
auto eject mode on a 512 or 580 line printer results in the
deselection of 8 lines per inch, if previously selected.

60407000 D

1-A-ll

DAYFILE MESSAGES B

This appendix contains an alphabetical listing of the messages which may appear in a
user's dayfile. Lowercase characters are used to identify variable names or fields.
If the first word or characters are variable, the message is listed according to the
second word. For example, the message:

pfn ALREADY PERMANENT, AT nnn.

is listed alphabetically with the messages beginning with the letter A. This is done
because the variable pfn (permanent file nanae) may change each time the message is
issued. All messages beginning with numbers follow the alphabetical listing.

The CIO and PFM file processors utilize the file environment table (FET) as a communi-
cation area to contain Information about the requests of a user's job. Higher level
languages (COBOL, FORTRAN, etc. ) automatically establish and use these areas but the
COMPASS programnier must define the FET. (Refer to volume 2 for detailed infor-
mation on the FET. ) CIO and PFM error messages contain the address, nnn, of the
FET associated with the request and the logical file name, fff, from word zero of the
table (FET+0).

When the error processing (ep) bit is set in word 1 of the FET, status information is
returned by the function processor when an abnormal situation or error occurs. The
abnormal termination codes are returned to bits 10 through 13 of word zero of the FET
(bits 10 through 17 of PFM). Following the alphabetical listing of messages Is a list
of LFM and PFM error codes and explanations. Also Included at the end of this sec-
tion is a table summary of the action taken by PFM when an error is detected while
reading mass storage.

60407000 D 1-B-l

a c

"it

^§

■kJ CO

a> «>
So w

09 CO 2

o
v

Q* til w .

-H am
^ o o

I <u

•a <*

C CQ

—I m

f 3

a, «

U
O

o o

«5
•-<

>■«:

O 3

•-< 3

o S

0) u

-< 4)
^^

I
H a

B
3
O

"Ha

IMC
C O

^«

•ga

01
(B.2

V '3

i-iS

00.2

bo
B

s .y

§ .

°c3 .2 ™

B
O
o

a
■§

■fl

-a

■s

'-' ^ H-l

VI v|-'

■o

•«
e

a HH "

03 CO f^

KBSi

EH-I I—'
feO

sS§

vivl

HH^

m CO f-<

KK p

EEo

5,'

Cci

K
Q

m
O

l-t

c
c

•

«
n

a
o

D
<

K
O
K
K

>
i

»
K

•J

rr!

ft.

►4

•

w
p

g
^

i;^

P
P3

l-B-2

60407000 D

I «

■S o

rt ™

5 c

u o

S I"

h ■»
Mm

<L>

11) g

a g

^o
-. "" .

C , 0)

s
J
o

o
a
o.

■n

6(1

•3

a) 01

•o ■'■' "J

iri I" a "

S3 " -3 "

o 'S b "i

S £ " *-

&^:t: Si

*" c :S

HO, is H

a. S3 o

>
•-ci
o
aj

Li
-3

B
o

go
m M
— I -t->

o 6
<.£

^^
ct)

<»
u

"t.
(i>
m

£ C

a n

•^ o

QJ
I"

0] <U
03 Ci
m S

01 -M
OO

4-*

<u o

(^ (<

..-I •*-*

■a c

a o

.2 o

•3

S
u

^ a

3 .

a
(«

fcl
.s

o -o
a

a "!
d

■a S3
o

0) a

a (U

■"' o
■o S

(U -^

"§

QJ S ^ 0>

QJ R g 41

"3. . o- "3.

S § "■ fi

Co >

C ^ ^ C

W
<;
H"
en
M a

£ QJ

§«

■a (U 1=

J3 o a

C o g-
C ^

u .a

I -t-> -O

uf^ a

QJ o

S QJ

6 "S

j3 "■

- ti

■I
u
ni
IE

^ OJ

5» 05

J3 .

"■s

■a.°

•gJ

£ -M

3
QJ OJ

rB Q>

-ts "

"•a
OJ a

H oo
ad:::!

to QJ

<" 'S

-t^ Co

a a

T3 -JJ

a 7}

0) u

a 01
m g

01 ol

(^ T3

-tJ ■*-»

a o

o -w

(X 0)

QJ H

Sen
W

^ cc •

OJ QJ

S !H::d
>>a

* is -^

a 2' o
o g a

2«|

■" a ""

^J 0) iS

'*"^ a o
m 0) 0)

^ ^ ra

ca "> 0,

6f35

•r" -M Tj

fa a 01
5 o OJ

<
H

■3

■V

f..

a i5

SI a
3 3

cr- o

.2 ™

-a
01

&
0)

S.H

■a

^Ti

TO Q)

a o

O
a.

O nl

■o

I"
§•2

J3
H S

ii „ -O

•Sea

3 £

•a
a
o
J

-H "^

a ='
S.2

^-(

ti
3

o> .::

a
o
o

fa y Ik,

ll<

PC
<
H

W
CC

^ s

K
<
H

E-<

t.l

a
a
a

H
<

05
O
05
K

Q
K

H
Z
O
U

w
m

(jj

fll

t§

i«

>-!

0;
0<

2
t2

Q
fa

►J

E
fa

fa
J
J

H
2

-Fi

Q
fa

fa
J
fa

o
u

H
2

O
fa

05
05
fa

H
2

w
ffi
u

t-J

■3

,>r;

u
fa

Q
fa

03
05

2
fa

D
03

Q
K

-1

fa
p

<
>

<X,

-1

-J

tei

ffi

60407000 D

l-B-3

■s «-

T3 3

o is

c
o
u

H
K

a
o
v»
a.
o

&
o

■O
C

o
a

11) ^

■a
td

c
o

'OD
CO

« o

is fi

o ;

.2 a

I- C
0)

M (II

'= a

T3 .5

(d
t<
o
a
o

■a
<ii
<i>
u

O QJ
01

V 73

■"• r-

0) rt

X
0) jq

CO <k, 0) «

, G "'

■s

5"°

o o>

K S

0> Ih

0, 0)

o
p

u o

O ti

a a
o
s P

5 u

u 0)

d. o

o a

0) •-;

■£§

•a «
c <"

0) >>

01
«tH S CI

o ^ o
■3 H •■

<1| S 01

fl gxi
so

oSi.,
, ti o
S-i 01 t.

HU W

a x)

S-.'D •?'

"> "m
> to

m C <u
2 S '^

2 u O
m t< C

0) 0) 0)

o o

> > >

01 0> 0>

QDQ

p m

> *» O O T»*
0) i-( *H to

«^ fr,^ a,< S

5.S

O h

u o>

^.2

>50

K 3

^ S S w

fc fe li. Q

P< en m to

BO
01

iz;

en
K

-5

1-4

>-l

|x<

ffi

■

•

(Ih

K
O

K
O
K
K
W

W
en
<!
m

a
w

H
►J

1— 1

•1
X

:«!

l-B-4

60407000 D

03 Q>
-w ■**

C C

„ T3 T3
2 C C

^^ t-t t~*

cfl

•a

ZmCC

o o

Q n

01 01
O O ^ CO jH 2
i-< f-l CO .u! -S

WDhHotK

r/)

2 fe

•

OS
03

§
H
U

P
^

•

1-1

»<

■

Ix<

►J

»— 1

H ''^

■> •

!»

60407000 D

l-B-5

■a

ly 0)

IK T3

"-J

c »!

<" ?. £

43 m jQ

(0
III Li

•= s

•a. .2

-- - .3 r

o> c
3

CO m

to o

■O
T3
CD

5"
Q.

<u ^ .5 o -e
3 o -B m

3
Q 10

.^Ii o o u o
o 'm 'ui 'co CO

3 J3 ja j3 X!

0) lU

££

cd tj

£2
^^.
2 c
£ o

° a.

(1) o

2 >
'>^

■° o

§ i"

. w

ra-O 2

•*■* 0) to

at .Z o

ID
■^"^

<o n ^

CO S

lu cd

o -^

o
a

&-.
CO

.S "

0) =

ti ? H

>" 2

"2 <u

H
g

CJ lU

— ^ -o ,

o
c <v

•5 Si;
i-^-io

a> u.

-« -a-C

^ S X s< « >.
S g. X X >« 3
S o'PUHra

i|-i > ^

O "^
I1)T>

Q.. C

Ht3

Ji m 2 -S

lU lU

H-5

*« o-

o o

TJ *

-4 0)

ID **

<J T3

■a Q.
u

tD ID

cd u

ID 0)

10 M m

ID CC CU)

> a ^
S S 3

<! m o

o
u

B
ID
Si
%

ki
3
o
o
O

c J-

oj *i-i

o
o

c c

ID >>

OJ cd

Q h

ElH

•s a

<D cd

fc •§

<; -o

III

■a

Sc'

Ji^-

§3

p fa

§§

u
n

ID
f)

3
o

01 >f

a ^

•s a

•>

t a

(D Id

01 cd

Qfa

Dfa

Q IK

(1)

X
M

i-l

o
2

C
■a

K
X
X

c X
■3 X

H
i-l

1—4

Ix,
O
K
di

(bOo,

01
tU)

§
<

K
O
K
K
»

I-l

>
Q
en

O
O

H
U

„

ffi

III

IxJ

H
U

U
K

H-l

H
O

-§

D
W

J
K
W
Eh
g

X
b

2
Q

K
K
W

b
W
D

X
X
X
X
X
X
X

■a
2

X
X
X
X
X
X
X

l-B-6

60407000 D

Q) 0)

js xm

I-. eo

■^ c

d. '•'

D 01

^.4

5ii

X! O

a
1

J3
o

t<
o
u

O
0)

u
u
<u

•o

u
o

rS
"S

■V
(U

u
<u
■o

M
C
O
O

T! C

(1,
Q
Q

m
m

o
o

B
o

■o

«•-«

fci Tl

ITl

5l t-

T3 en
<U X

01 XI

(i>

(II

&,<QQD

r; ^

a
e

3 n

^3 _,

H
to

CO 05

(t-i

0) S

en x:

!>,

inS

WUW

(C c

S'e

« g>

01 H

s»>

>> o

«f^

&,(U

^!^

< 0)

V 01

o o ^1 o c a

rH t-l CC' 1-* >S 1-3

p.; a ^1 z CO 05

Oh < cr.i fe 05 g

c o

0} s

a OJ

CO .-<

m ■*-»
o

01 B

II o

J5
PL.

m
m

XI
0)

>•.
t-.
o

o
u

a s

O 0)

S? --S -i^

5 a
o

•S ft

(» 2

2 °

« CD

ir; s 01 ID

X xi
H at

01 ID
—I ■ "

< OJ

01
XI

^ CO

fi -H CO
3 ™ t^

C .. a>

o g 6
0) c a

(;4 ^ 4->

■3.2'o

■S u a-

BO).

OJ jQ ^

01 S o
o *-* ^

°a-a

^ " t<
.b <«

S 0)
u X <»

OJ
T3 0)

d B "

O t,xi

K £ a

6 c

B i o •

d ., * :3
Si .2*

^^ - °-S

tl a;
I 4-> a.o
1 o B
: 01X1 B

•o.2§

3 5 <u

ss-s «

01X3 , ."

.!i 3 0) a

-■ x> 3

01 o B X!

o 01

g m m £

ct n

t. B •- tlO

O C X rH
0) 01 .-

B "-o «
" 1^ S c

X> 0) o o
(D a) Jlj o

o ^^ « :>,

u
u

a 2

0) -B

O (4 tl

01 01
^ -,Q X>

S: 0) m ST
.Q 3 o

x> a g

S 3 "• Q.

.S ° Mq,
tl *. B t,

.2 o a o

rt 0) „ t-i X3

' 3 CO
c B a, m

CO s
CO

3 tl

Q ^ CO a

o S x>

«" . tl

B a ., t4 rt

I^ .Q 01

00 CO «i5 e t.

•B tl o B 5

■B 01 tl 3 .-i

H XI a fixj

«Jl

H
<!

W
2

W
H

<!
y

Oh
Q

K
H

pq
S
P

H
U
W

H
<!

3
0,

05
W
CO
P

H
<

60407000 D

l-B-7

•2

O -u

« a

X) W

s >

§ s

«M O

■o
a

m ^

2 ii

*• o

0) o

xj c

^ 2

c o

§ o

o ^

§ .s

0) o

a.
n

d »-,

? i!

s. s

5 B 3

XI
CO

o 01

c
o

X)
01

01 s

m
ej m

^ m

.' 3

•Ox)

s§

>
O

X3
0>

ra 2
CD 5

§ i

[O <^ (U

■S ti iS
ag-

Ti 5 S

Ox)
0) o
<J TO

c
cm

"I
■9-2

XJ t,

2.2

u 8

— S 0)
0) O 3

■333

5 -?"

d r_ ro

. XI

X £ o

o S

&^
3 d

.. n
C d
o

t! -O

0) .

£ *

Ui d
O 0)

Q -}

H 3
S " c

3« d

X! O

<« ^

^ 3

2' ">

d .M

■" d

S »!

*^ 0)

.a™

a *"

O 73

■B .
B Id

» I
" m

■s°

^ to

." 0>

'^ a
o>

d bo

t.XJ
0)

o .

Oi 01 S

5.„-

<u a
<« 2

So;

s i - "S -

X)
d

a- C
' 0) c
' ,c d

(u ^ a

U M

.u — o>.
d J3 "^ •• o -H

5^.232g.S

fe iJ IM I

H S: 0) 2 rt 3 3
m

^ Ma, 0) (U

cS§<u S

. m "* a
o «> c

03, m II mm a;. c"Sg

9 «

.T^ "

^ t(

. «> tl

o t> m
0) , o t.
fci S fc. 01

,3 t, " a
m ■?, d
"X! .2 ^

0) (J rj d

oja ^

3 a - t<

^ c ° '•'
3 Oj<l o

a dirt's

•-;OXl c

•" 2 O-S
■= c

t, m

2«aiS^<mSc5

o ce;

I o

01 CO

Si c
H 5

.S 3
-< g

a a
o o
u u
m m

a
a
a a
a a
a XI a
a ja a
a X3 Q.
c XI a

3
O
PS

<!
u

H
K
O

o
6

i-J

•

111

I— I

«
O
CO

:s u w

<
V

X
H
CU

Q
Z
P
O
b

H
O

H
Z
b

1-4

i-i

K
H
H

«
O

M
PQ

z
u

PS
M
H
Z

o
u
z

m SI
JLO-

8^
".xJ .

"•S ?•

«l-l .

" eg

"Co

i? .0

3 *"* *

I £■ 01

01 |i| U
I i •
000
u o o

l-B-8

60407000 D

4^
o

o
o
o

Message

EQ, Ccc-uu, vsn, rw, est, Ss, GSgggg.

EQ. Ccc. Dddd. . . d

EQ, Ccc, Fff, lii, Bnnnnnn, Lbbbb, Ppppppppp.

EQ, Ccc, Eec, Hhhhhhhhh, type.

Routine

Description

IMT

The third line of the message contains the following information:

CO Channel number: the channel number is repeated to allow the

analyst to associate this message with the first and second mes-
sages if errors are occurring on more than one tape channel at
the same time.
Octal error code value.

Controller options selected at the time of the error; each two
digits is a function code.
Additional description of the error (one of the following):

ec
0000000000

type

BAD ERASE.

BLOCK TOO
LARGE
BUSY.
CHANNEL ILL.

CON. REJ.
CON. REJ. OFF.

iJ£.lNOIl 1

CHANGE.
FNnn, Pyyyy.

Lbbbb, Bnnnnnn.

NO EOP.

NOISE.

NOT READY.

ON THE FLY.

POSITION

LOST.

RECOVERED.

STATUS.

WRONG
PARITY.

Error detected after an erase was attempted to

recover a write error.

Data block was larger than expected.

Unit was still busy after 1 second.
Channel is not accepting function or status
requests properly.

Connect reject; unable to connect to the unit.
Connect reject; unable to connect to unit. Unit
turned OFF.

Either user error where auto select does not
match user selection (0-track only), or hardware
error where status does not match user selection.
Function nn was rejected by the controller; yyyy
is the address in IMT where the function was
initiated.

The length (bbbb) and block number (nnnnnn) read
from trailer bytes in block did not match the
actual length or the block number read; given in
previous message line.

No end-of-operation detected from unit within 1
second.

A noise block was skipped on the tape.
Tape unit dropped ready status.
Error was corrected as the data was read.
The last good block written cannot be found during
write recovery.

Previously reported error has been successfully
recovered.

Error type cannot be deternained so actual con-
troller status is returned.

Tape was written in parity opposite that being
read.

Four-line message describing a magnetic tape hardware malfunction occurring on
a 667 or 669 tape unit.

EQ MT for 667; NT for 669

The first line provides the following information:

cc-uu Channel and physical unit number of tape unit on which error

was encountered,
vsn Volume aerial number associated with the tape on the specified

unit.

Message

Routine

o
o
o

Description

est

s
gggg

Read (RD) or write (WR) operation; any operation not Involving an

actual read or write is listed as a read.

EST ordinal of the unit on which the tape was written. This is

provided only for labeled tapes generated under NOS 1.0; otherwise,

the field is blank.

Channel status

General status of magnetic tape unit.

The second line of the message contains:

cc Channel number; the channel number is repeated to allow the

analyst to associate this message with the first message if errors
are occurring on more than one tape channel at the same time.

ddd. . . d Detailed status of magnetic tape unit.

The third line of the message contains:

oc Channel number; repeated to associate this message with the

previous messages,
ff Software function on which the error occurred,

ii Error iteration; number of times error has been encountered on

this unit without successful recovery,
nnnnnn Block number on which error occurred,

bbbb Length of block on which error occurred. In octal bytes,

pppppppp IMT internal error parameters.

The fourth line of the message contains:

cc Channel number; repeated to associate this message with the

previous messages.
Octal error code value.

Unit format parameters. Refer to Magnetic Tape Subsystem
Reference Manual for descriptions of unit format parameter fields.
Additional description of the error (one of the following):

ec
hhhhhhhh

type

FNnn, Pyyyy.

Lbbbb. Bnnnnnn.

BAD ERASE. Error detected after an erase was attempted to
recover a write error.

B.C. RESTART. Magnetic tape controller firmware restarted.

BLOCK TOO Data block was larger than expected.

LARGE.

BUSY. Unit was still busy after 1 second.

CHANNEL ILL. Channel is not accepting function or status re-
quests properly.

CON. REJ. Connect reject; unable to connect to the unit.

CON. REJ, OFF. Connect re'-ect" unable to connect to unit. Unit
turned OFF.

DENSITY Either user error where auto select does not

CHANGE. match user selection (9-track only), or a hardware

error where status does not match user selection.

Function nn was rejected by the controller; yyyy

is the address in IMT where the function was

initiated.

The length (bbbb) and block number (nnnnnn) read

from trailer bytes in block did not match the

actual length or the block number read; given in

previous message line.

o
o

Message

Routine

Description

EQxx,CHyy Adddd INCOMPLETE TRANSFER.

NO EOF. No end-of-operation detected from unit within 1

second.

NOISE. A noise block was skipped on the tape.

NOT READY. Tape unit dropped ready status.

ON THE FLY. Error was corrected as the data was read.

POSITION The last good block written cannot be found

LOST. during write recovery.

RECOVERED. Previously reported error has been successfully
recovered.

STATUS. Error type cannot be determined so actual con-

troller status is returned.

WRONG Tape was written in parity opposite that being

PARITY. read.

An incomplete data transfer was detected by a local batch equipment driver.

EQxx,CHyy CONTROLLER HUNG BUSY.

EQxx,CHyy Fzzzz FUNCTION TIMEOUT.

txi

dddd

One of the following equipment types:

CP 415 card punch

r^v? 405 card reader

LP 501, 505, 512. or 580 line printer

TjQ 512 line orinter

LR 580 line printer

EST ordinal of local batch equipment

Channel number

Octal byte count not transferred

The specified local batch controller did not drop BUSY status.

EQ One of the following equipment types:

CP 415 card punch

CR 405 card reader

LP 501, 505. 512, or 580 line printer

LQ 512 line printer

LR 580 line printer

XX EST ordinal of local batch equipment,

yy Channel number

No response (inactive) was received after Issuing a function code to the specified
local batch equipment. (Converter and equipment status unavaUable. )

EQ One of the following equipment types:

415 card punch

405 card reader

501, 505, 512, or 580 line printer

512 line printer

580 line printer

EST ordinal of local batch equipment

Channel

number

zzzz

Function

code

o
-J
o
o
o

Message

Routine

Description

EQxx.CHyy Fzzzz REJ Paaaa.Cbbbb, Ecccc.

Detected function reject or transmission parity error on the specified local batch
equipment.

EQ One of the following equipment types:

CP 415 card punch

CR 405 card reader

LP 501. 505, 512, or 580 line printer

LQ 512 line printer

LR . 580 line printer

XX EST ordinal of local batch equipment

yy Channel number

zzzz Function code

aaaa Driver (ICD) address

bbbb Converter status

ccoc Equipment status

EQxx.CHyy RESERVED.

The specified local batch equipment is reserved and cannot be connected on
channel yy.

EQ One of the following equipment types:

CP 415 card punch

CR 405 card reader

LP 501, 505, 512, or 580 line printer

LQ 512 line printer

LR 580 line printer

XX EST ordinal of local batch equipment
- yy Channel number

EQxx.CHyy TURNED OFF.

The specified local batch equipment was logically turned off (OFF status set in
EST). Note: this message is preceded in the error log by a message for the
same equipment which specifies the failing condition.

EQ One of the following equipment types:

CP 415 card punch

CR 405 card reader

LP 501, 505, 512, or 580 line printer

LQ 512 line printer

LR 580 line printer

XX EST ordinal of local batch equipment
yy Channel number

EQxx, DNdn. DIRECT ACCESS FILE ERROR, AT nnn.

PFM

The system sector data for the file does not match the catalog data.

XX EST ordinal of device
dn Device number

EQxx, DNdn, FILE LENGTH ERROR, AT nnn.

PFM

The length of a file does not equal the catalog length.

XX EST ordinal of device
dn Device number

-a
o
o
o

Message

Routine

Description

The action taken depends on the type of command issued.

Command Action

GET A local file is created with length being the actual length

retrieved.
SAVE If file length is loriger than TRT specification, file is

truncated.
REPLACE Same as for SAVE.

EQxx, DNdn. MASS STORAGE ERROR AT nnn.

PFM

An error was encountered in reading a portion of the permanent file catalog or
permit Information.

XX EST ordinal of device
dn Device number

EQxx. DNdn, RANDOM INDEX ERROR, AT nnn.

PFM

The random disk address of the permit sector is in error.

XX EST ordinal of device
dn Device number

EQxx, DNdn, REPLACE ERROR, AT nnn.

PFM

The same file was found twice during a catalog search. This error can occur for
APPEND or REPLACE commands after a file is found and purged and the catalog
search is continued.

XX EST ordinal of device
dn Device number

EQxx. DNdn, TRACK LIMIT, AT nnn.

PFM

No allocatable tracks remain on equipment xx.

XX EST ordinal of device
dn Device number

EQxx FILE ACTIVE - fUename.

IMS/MSI

An attempt to initialize a dayfile on device xx was not completed because it was
still in use as an active dayfile.

XX EST ordinal of device
filename Name of dayfile

EQxx. FILE BUSY - filename.

IMS/MSI

The inactive dayfile has track interlock set indicating It Is attached to another
control point and thus may not be initialized.

XX EST ordinal of device
filename Name of dayfile

EQxx NO SYSTEM DAYFILES FOUND.

IMS /MSI

An attempt was made to initialize an inactive dayfile on device xx but no dayfile
was found.

XX EST ordinal of device

EQxx PROTECTED QUEUES IGNORED.

IMS /MSI

Device XX was Initialized for permanent files and protected queue files were found.
XX EST ordinal of device

at
o
>«k
o
~i
o
o
o

Message

Routine

Description

EQxx, RM=mnimmmmm, PF=ppppppp, UI=ililli.

PFM

Additional line written only in error log after one of the following messages.

EQxx. DNdn. DIRECT ACCESS FILE ERROR. AT nnn.
EQxx, DNdn, FILE LENGTH ERROR, AT nnn.
EQxx, DNdn, MASS STORAGE ERROR. AT nnn.
EQxx, DNdn, RANDOM INDEX ERROR, AT nnn.
EQxx, DNdn, REPLACE ERROR. AT nnn.
EQxx, DNdn. TRACK LIMIT, AT nnn.

XX EST ordinal of device
mmmmmmm Family name
ppppppp Permanent file name
iiiiii User index

filename EQxx TRACKtttt LENGTH ERROR.

QREC

EOI of disk and EOI of TRT are not Identical.

filename Name of file in error
XX EST ordinsil of device
tttt First track of file in error

EQUIPMENT NOT AVAILABLE

LFM/RESEX

Requested equipment Is either in use or does not exist.

ERASE LIMIT, fff AT nnn.

CIO

The system made 20 erasures (10 feet of tape) without being able to successfully
write the tape.

ERROR AT LINE xxx

Issued when errors occur while resequencing a BASIC program. The line con-
taining the error is specified by xxx.

ERROR IN ARGUMENTS

One or more of the following conditions was detected.

• More than one date was entered.

• No options were selected.

e The param.eter was illegal or could not be recognized.

• The TM option was selected but no data was specified.

• Both the device number parameter and the paokname or auxiliary device
parameter were selected; auxiliary devices do not have device numbers.

ERROR IN CHARGE NUMBER.

PROFILE

The charge number is in error. The charge number entry is disregarded and
PROFILE skips to the next charge number entry in the input directives.

ERROR IN COMMAND PARAMETERS.

Either no parameters are allowed or an Illegal parameter has been encountered.

ERROR IN DATE.

PURGALL

The format of the date (ad, md, or cd) parameter in a PURGALL request was
incorrect.

ERROR IN DEVICE NUMBER.

PURGALL

The file residency as specified by the device number parameter was illegal.

ERROR IN DIRECTORY.

Program library does not have a directory record, or has an Incorrectly for-
matted directory record.

ERROR IN FILE ARGUMENTS

FILES

The parameter could not be recognized.

-J
o

o
o

ixl

Message

Routine

Description

ERROR IN FILE CATEGORY.

PURGALL/
PFILES

The user specified an illegal file category.

ERROR IN FILE TYPE.

PURGALL

The user specified an illegal file type.

ERROR IN IDENTIFIER.

PROFILE/
MODVAL

PROFILE cannot recognize a directive identifier. The action taken depends upon
the position of the erroneous identifier within the entry.

• If the error occurs within a project number entry, the entire project
number entry is disregarded.

• If the error occurs in a directive that appears after a charge number but
before the first project number, only the erroneous directive is disre-
garded. However, if the error occurs on the first PN directive, the
entire project number entry is disregarded.

• If the error occurs in any PN directive except the first one. It is treated
as an error within the preceding project number entry. Both the project
number entry for the erroneous project number and the preceding project
number entry are disregarded.

ERROR IN LIMITS ARGUMENT.

TCS

Parameters were included on the LIMITS statement.

ERROR IN LINK ARGUMENTS.

LINK

An invalid parameter was used on the LINK control card.

ERROR IN NUMERIC DATA.

PROFILE/
MODVAL

PROFILE detected nonnumeric data or numeric data exceeding the maximum limit
for specified control value. The entire project number entry containing the
erroneous directive is disregarded.

ERROR IN PASSWOR ARGUMENTS.

TCS

Parameters specified on a PASSWOR control statement were in error.

ERROR IN PROFILE ARGUMENTS

PROFILE

Error on PROFILE control statement.

ERROR IN PROJECT NUMBER.

PROFILE

The data field on the PN directive does not contain 1 to 20 alphanumeric characters.
The entire project number entry associated with the erroneous PN entry is dis-
regarded.

ERROR IN TIME.

PURGALL

The format of the time parameter in a PURGALL request was incorrect.

ERROR IN USER NUMBER.

PROFILE

The data field of the UN directive does not contain 1 to 7 alphanumeric characters
(or asterisks). The entire project number entry containing the erroneous UN
directive is disregarded.

ERROR - FILE(S) NOT PROCESSED.

CHKPT

One or more files were not checkpointed because CHKPT detected address errors.

FET ADDRESS OUT OF RANGE AT nnn.

CIO

FET extends past job's field length.

FILE ALREADY INTERLOCKED.

QFM

The track interlock for the specified file in the DULL word in the MST is already
set.

nnnn FILE DEQUEUED Dndn FMxxxxxxx.

QREC

Indicates the number of files that have been dequeued on the specified device.

nnnn Number of files
dn Device number
xxxxxxx Family name

FILE EMPTY.

LFM/SFM/QFM

The file specified was empty.

>f>>
o
-J
o
o
o

Message

Routine

Description

FILE ERROR Iftl.

CHKPT/
RESTART

An illegal address was detected on file Ifn,

FILE NAME CONFLICT.

QREC

Processing was attempted on two files having the same name.

FILE NAME ERROR, AT nnn.

PFM

File name contains illegal characters.

FILE NOT FOUND

LFM/SFM/QFM/QDL

Requested file was not found.

FILE NOT ON MASS STORAGE.

SAD

The specified file does not reside on mass storage.

FILE NOT OVERLAY FORMAT.

LDR

The first record of the file was not an overlay.

FILE TOO LONG, AT nnn.

PFM

The local file specified for a SAVE, REPLACE, or APPEND command exceeds
the length allowed, or the direct access file specified for an ATTACH in write,
modify, or append mode exceeds the direct access file length limit for which the
usel- Is validated.

nnnn FILES ACTIVATED DNdn FMxxxxxxx.

QREC

Indicates the number of files that have been activated on the specified device.

nnnn Number of files
dn Device number
xxxxxxx Family name

nnnn FILES IGNORED DNdn FMxxxxxxx.

QREC

Indicates the number of queued files remaining inactive on the specified device.

nnnn Number of files
dn Device number
xxxxxxx Family name

nnnn FILES PURGED DNdn FMxxxxxxx.

QREC

Indicates the number of queued flies which have been purged on the specified de-
vice.

nnnn Number of files
dn Device number
xxxxxxx Family name

FL BEYOND USER LIMIT.

IMA

The requested field length exceeds that for which the user is validated.

FL TOO SHORT FOR LIBRARY GENERATION.

LIBGEN

Additional memory Is required for LIBGEN.

FL TOO SHORT FOR LOAD.

LINK

The program requires additional field length.

FL TOO SHORT FOR LOADER, NEED xxx.

LINK

The loader requires xxx additions^ words of memory.

FL TOO SHORT FOR MAP.

LINK

Additional memory Is required for the MAP operation.

FL TOO SHORT FOR OVERLAY GENERATION.

LINK

Additional memory Is required for overlay generation.

FL TOO SHORT FOR PROGRAM.

3AE

The user's field let^th Is too short for the program.

pfn FOUND. AT nnn.

PFM

The specified permanent file was found.

FORMAT ERROR ON CONTROL CARD.

TCS

An error was detected In the format of the control statement.

05
O

o
-J
o

o
o

I ,

Message

FORMAT ERROR ON OVERLAY DIRECTIVE
ILLEGAL ACCESS TO EXECUTE ONLY FILE.
ILLEGAL CHARACTER NUMBER.

ILLEGAL CHARGE.

ILLEGAL CIO REQUEST.
ILLEGAL CONTROL CARD.

ILLEGAL COUNT.

ILLEGAL DEVICE REQUEST, At nnn.

ILLEGAL DISPOSE CODE.
ILLEGAL EQUIPMENT.

ILLEGAL EXTENSION ON Iff AT nnn.
ILLEGAL FILE NAME fff AT nnn.

Routine

LDR
SAD
FILES

CHARGE

PACK
TCS

COPYBF/COFYBR/
COPYX

PFM

CIO
110

CIO
CIO

Description

Illegal overlay directive parautneter or no arguments found.
The specified file is an execute -only file.

In a copy request, one of the following was detected.

• Last character position was less than first character position.

• Last character position was greater than 150.

• Either first character position or last character position was unrecogniz-
able.

The specified charge or project number does not exist or the project number was
not assigned to this user.

An attempt was made to pack a nonmass storage file.

One of the follcv/inE :

• The control statement could not be identified.

• An Invalid parameter was specified or no terminator was detected.

• The user attempted to pass too many parameters on the program call
statement (such as LGO).

• The user submitted a control statement considered Illegal because of his
validation. For example, if access option 1 (refer to LIMITS control
statement) was not set and the user submitted a PASSWOR control state-
ment.

• The user submitted a control statement considered Illegal for a particular
job type or fUe type. For example, the use of a FAMILY statement In a
nonsystem origin job.

Number of files in copy request was either Illegal or zero.

The device type (r parameter) specified on a request for an auxiliary device cannot
be recognized or does not exist in the system.

If the auxiliary device specified by the pn parameter Is not the same type as the
system default, the r parameter must be included; If not, the message is issued.

The queue type (q^) specified on a DISPOSE control statement was unrecognizable.

File is assigned to illegal equipment for the specific request. For example, the
file specified in a COMMON request is not on mass storage.

The user attempted to lengthen a file that could not be extended.

The file name does not conform to established rules.

o
-J

o
o
o

Message

Routine

Description

ILLEGAL FILE TYPE.

LFM/QDL/QFM

The specified file Is of a type not allowed in the requested operation. For example,
this message would be Issued if the file name in a RELEASE request was not a
queue type file (input, print, or punch) or if the user attempted to make a non-
local file a library fUe.

pfn ILLEGAL FILE TYPE, AT nnn.

PFM

The user attempted to define a file that was not a local file.

ILLEGAL INPUT FILE.

CIO

An attempt was made to pack a file that is assigned to a time -sharing terminal.
For example, file INPUT for time -sharing origin jobs represents data typed at
the terminal keyboard, and therefore cannot be packed.

ILLEGAL I/O REQUEST ON FILE fff AT nnn.

CIO

CIO could not recognize the specified function code, or the code was not valid for
the type of device to which the tile was assigned. The system provides a dump on
the FET on fUe OUTPUT.

ILLEGAL LEVEL NUMBER.

LDR

One of the following:

• Assembly error

• Level number greater than 773

• First overlay not zero level (0.0) overlay

ILLEGAL LOAD ADDRESS.

3AE

The load address is less than 2.

ILLEGAL MAP OPTION, MUST BE -PFSBEXR-

LINK

The MAP control card contained an invalid parameter.

ILLEGAL MODIFICATION OF fff AT nnn.

CIO

Either the user has attempted to shorten a modify-only file or the file cannot be
modified at all.

ILLEGAL ORIGIN.

SFM/QFM/QDL

The origin type specified when releasing a local file to a queue was illegal.

ILLEGAL ORIGIN SPECIFIED.

Origin word count error.

ILLEGAL OVERLAY LOADED.

LINK

Overlay processing was already in progress.

ILLEGAL PROFILE INQUIRE.

PROFILE

The user is not allowed to access the control information for the charge number
supplied.

ILLEGAL QUEUE TYPE.

QDL

The queue type specified in the request was illegal.

ILLEGAL RECORD TERMINATION.

COPYX

Illegal format on record terminator.

ILLEGAL SORT PARAMETER.

The SORT control statement is in error.

ILLEGAL TERMINAL REQUEST.

A command intended for time-sharing origin jobs only (refer to Time-Sharing
Commands, section 4) has been used in a non-time -sharing origin job.

ILLEGAL USER ACCESS.

LFM/QFM/QFSP

User tried to perform an operation for which he was not validated.

ILLEGAL USER ACCESS, AT nnn.

PFM

The user is not validated to create direct access or indirect access files or to
access auxiliary devices.

o
-J

o
o

Message

IMPROPER ACCESSIBILITY.
IMPROPER VALIDATION.

INDEX ADDRESS OUT OF RANGE FOR fff AT nnn.

INPUT FILE IN NORERUN STATUS.
INPUT FILE IN RERUN STATUS.
INQUIRY COMPLETE.

deckname -INVALID CS, 63 ASSUMED.

I/O EXECUTE-ONLY FILE fff AT nnn.

I/O SEQUENCE ERROR.

I/O SEQUENCE ERROR, AT nnn.

I/O SEQUENCE ERROR ON FILE fff AT nnn.

IQFT FILE INTERLOCKED.

JOB ABORTED, fff AT nnn.

JOB CARD ERROR. (20 characters)

JOB EXECUTING.

JOB IN INPUT QUEUE.

JOB IN NORERUN STATE ON RECOVERY.

JOB IN OUTPUT QUEUE.
JOB IN PUNCH QUEUE.
JOB NOT FOUND.

JOB REPRIEVED.

Routine

RESEX
TCS

CIO

QFM

PROFILE/
MODVAL

TCS

CIO

QFM/QDL
PFM

CIO

IMS /MSI

CIO

3AA

lAJ

Description

SFP

The user did not specify the correct file accessibility on the LABEL statement.

A validation program (one containing a VAL= entry point, such as that used for
CHARGE and USER is required before continuing.

The random sector address for a random input/output request was equal to or
greater than field length.

Informative message.

The inquiry was successfully completed.

Character set identification for deck deckname was not recognizable. OPLEDIT
assumes 63 character set and uses it for the new program library if one is being
created.

The user attempted to read, write, or position an execute-only file. RETURN is
the only operation allowed for an execule-oiily file.

Action was requested by a busy file.

A request was attempted on a local file that is currently active. This error can
occur, for example, if the user creates two FETs for the same file and Issues a
second request before the first is completed.

The user attempted to perform more than one concurrent function on a single file.

The IQFT file Is Interlocked by another job and cannot be Initialized.

The job was aborted while a tape operation was pending.

The job statement on the file being submitted is In error. The first twenty
characters of the statement In error follow the message.

The job Is either executing or has been rolled out for a higher priority job.
Informative message.

Identifies a job recovered on level deadstart that was aborted because It was In
a no-rerun mode 'due to NORERUN control statement or macro).

Informative message.

This message normally indicates that the job has been processed and no longer
exists In the system. However, It may also be Issued If the jobname was entered
Incorrectly (misspelled).

The job has been successfully reprieved.

a>
o
><^
o
-a
o
o
o

Message

Routine

Description

LABEL CONTENT ERROR, fff AT nnn.

CIO

A block read was the correct size for a label but one or more required fields
(such as the label name) were incorrect. The programmer should use the
LlSTLB control statement to determine the cause of the problem.

LABEL MISSING, fff AT nnn.

CIO

During a read operation, a required label was missing. The programmer should
use the LISTLB control statement to determine the cause of the problem.

LABEL PARAMETER CONFLICT ON OPEN, fff AT nnn.

CIO

Label fields did not match on open request. An additional message:

FIELD BEGINNING AT nnn NO COMPARE.

specifying the decimal character position in HDRl of the first field that did not
compare correctly is also issued.

LBC ARGUMENT ERROR.

CPMEM

The load address, addr, specified on the LBC control statement was not numeric.

LBC FWA .GE. FL.

CPMEM

The load address specified on the LBC control statement was greater than or
equal to the user's field length.

LDR ERROR.

LDR

Issued after one of the following errors.

OVERLAY NOT FOUND IN LIBRARY.

ARG ERROR.

FILE NOT OVERLAY FORMAT.

LEVEL NUMBER MISSING

LDR

First or second level number was blank or unspecified.

LEVEL-3 DATA BASE ERROR.

PROFILE

PROFILE detected a format error in the user number/control value entries of the
project profile file.

LFM ILLEGAL REQUEST.

LFM

One of the following:

• LFM function detected was not recognized as a legal function.
» An LFM function was issued without the auto recall bit set.

LIBGEN ARGUMENT ERROR.

LIBGEN

An invalid parameter was vised on the LIBGEN control statement.

LIBRARY GENERATION COMPLETE.

LIBGEN

Informative message.

LIBRARY GENERATION FILE EMPTY.

LIBGEN

The file to be processed is empty.

LINE NUMBER LIMIT EXCEEDED,

RESEQ

The line number encountered or required during a resequencing (RESEQ) operation
exceeded 99999.

LIST COMPLETE.

PROFILE

The list operation has been successfully completed.

** LOAD ERRORS.

LINK

During the load operation, xx errors were encountered.

LOAD FILE EMPTY.

LINK

No data on the file to be loaded.

o
lli.
o
-I

o
o
o

Message

Routine

Description

LOADER MISSING.

TCS

Either CALL or LDR= were not found in the library.

LOC ARGUMENT ERROR.

CPMEM

The first word address or last word address parameter specified on the LOC
control statement was not numeric.

LOG RANGE ERROR.

. CPMEM

Either the first word address was greater than the last word address or the last
word address was greater than the user's field length.

-LO-ERROR. MUST BE IN -BEXCR-.

LINK

The LO parameter specifying the map list option for the LINK control card Is
incorrect.

LPxx, ... .

Refer to the EQxx, ... series of corresponding messages for full descriptions
of messages beginning with LPxx, ... .

LQxx.... .

Refer to the EQxx.... series of corresponding messages for lull descriptions
of messages beginning with LQxx, ....

LRxx, ....

Refer to the EQxx,... series of corresponding messages for full descriptions
of irieSsages beginning with LBxx, ... .

MASS STORAGE DIRECTORY NOT WRITTEN.

On a GTR control card, user requested that a mass storage directory record
be written on a non-mass storage file.

MDxx, Cyy. ec. ann, Stttt, FNqqqq-r.
or

6MD

An error has been detected on mass storage device xx. The nature of the error
Is determined by examining each parameter In the message.

MDxx, Cyy, ec, ann, Stttt, Ux Cxxxx Stttt.

XX EST ordinal of 841 disk

yy Channel number

ec Error code; one of the following:

PE Parity error/checkword error

AD Address error

ST Device status error

FN Function reject for any device connected to data

channel converter (6681), or function timed out with

no response
RS Device reserved
NR Device not ready

a Type of operation; one of the following:

R Read
W Write

nn Retry count; error Is considered irrecoverable after following
number of retries.

PE 10

AD 10

ST 64

FN 10

RS Indefinite

NR Indefinite

txi

Message

Routine

o
-I
o
o
o

MEMORY OVERLOW.

MISSING OVERLAY FILE SPECIFICATION.

MIXED CHARACTER SET OPL,

M. T. NOT AVAILABLE ON FILE fff AT nnn.
MT/NT CONFLICT

NO CONNECT TIME AVAILABLE,

NO CPU TIME AVAILABLE.

NO DIRECTIVES.

NO EOR FOUND ON ZZZZZDF.

NO FILE SPECIFIED FOR LOAD.

NO INPUT FILE

NO INPUTFILE FOUND.

NO IQFT FILE FOUND.

LINK

CIO

RESEX

CHARGE
CHARGE

LINK

PROFILE
QFM

IMS/ MSI

Description

tttt Device status, implies there was an incomplete transfer if status

does not indicate an error

qqqq Function rejected

r Data channel converter (6681) status, if present

Ux Physical unit

Cxxxx Upper address Physical address

Sxxxx Lower address

Insufficient storage was allowed for an OPLEDIT run.
No overlay file name specified.

Records of more than one character set were encountered on the old program
library.

The magnetic tape executive is not executing.

Conflict exists between 7-track and 9-track tape descriptors. For example, a
request for a 9-track tape specifies 200-bpl density.

This message can also be issued if the device type specified in FET+1 conflicts
with the track type specified In FET+8, bit 56. If dt=MT and bit 56 Is set, or if
dt=NT and bit 56 Is not set, the message Is issued.

The user has accumulated the maximum connect time allowed for the specified
project number.

The user has accumulated the maximum CPU time allowed for the specified project
number.

Directive file was empty.

Illegal file format for ZZZZZDF. The FILE control statement (described in the
Record Manager Reference Manual) is used to update the file information table
(FIT) which is required for files the Record Manager accesses. The system uses
information the programmer supplies on the FILE statement to prestore FIT in-
formation in file ZZZZZDF.

The file to be loaded was not specified on the control card.

No input directives were present.

No valid input file exists; functions cannot be performed.

An attempt to initialize inactive queues on the device was not completed since an
IQFT file could not be found.

o
>(^
o
-J
o
o
o

Ca3

Message

Routine

Description

NO LINE NUMBER ON SORT FILE.

SORT

A line on the input file to a SORT request is missing a line number or a line
exceeded the 150-character limit.

NO LINE TERMINATOR.

A copy operation was attempted on a line longer than 150 characters which did
not contain a line terminator.

NON-MATCHING CONVERSION

The conversion mode required for the tape is not the same as that specified on the
control statement. This Is only a warning message.

NO READ FILE - Ifn.

SUBMIT

The specified file cannot be found.

filename NOT DECLARED RANDOM.

An EOF was encountered on the nonrandom file, filename.

NOT ENOUGH DATA IN BUFFER.

QDL

The CIO buffer does not contain enough words to be written into the system sector.

NOT ENOUGH ROOM IN BUFFER.

QDL

There are not enout^h words 9.vstil5ible in the buffer to contain the system sector.

Ifn NOT FOUND.

RESTART

RESTART was unable to retrieve a file named, but not Included, on Ifn.

NORERUN/RERUN IGNORED FROM TTY JOBS.

QPM/CONTROL

User entered NORERUN/RERUN from a terminal. The command is ignored.

XXX NOT IN PP LIB.

SFP

PP package xxx was not found in PP libraries.

XXX NOT IN PP LIB. - CALLED BY yyy.

SFP

PP package xxx was not found in the PP libraries and was called by package yyy.

pfn NOT FOUND, AT nnn.

PFM

One of the following:

• The specified permanent file could not be found.

• The specified user number could not be found.

• The user is not allowed to access the specified file.

• The user Issued an Indirect access file conamand on a direct access file.

• The user issued a direct access file command on an Indirect access file.

If this message occurs in response to the SAVE request, the specified local file
is not attached to the control point. Is a direct access file, or is an execute-only
file.

Ifn NOT ON MASS STORAGE, AT nnn.

PFM

The file to be saved is not on mass storage; the first track of the file Is not
recognizable.

Refer to the EQ. . . . series of corresponding messages for full description of
messages beginning with NT.

o
-J
o

o
o

Message

Routine

Description

NO WRITE ENABLE, ON fff AT nnn.

CIO

Either the user attempted to write on a tape mounted with no -write ring, or no
write was allowed because of additional constraints described Ln an additional
message line:

LABEL NOT The user attempted to write over a label that had
EXPIRED. not yet expired.

WRITE OVER The user is not allowed to destroy the VOL! label.
LABEL ILLEGAL.

200 BPI WRITE The tape unit (667 or 669) does not support 200-bpl
ILLEGAL. densitj.

OLDPL ERROR.

Update program library format was bad.

OPERATOR DROP.

SAB

The job was dropped by the operator.

OPLEDIT COMPLETE.

OPLEDIT

Informative message indicating OPLEDIT completion.

OPLEDIT ERROP>S,

OPLEDIT

Errors were encountered while modifying a particular deck.

OUTPUT FILE LIMIT

LFM

The total number of files disposed to the output queue by the job has exceeded the
limit for which the user is validated.

OUTPUT FILE LIMIT, FILE fff AT nnn.

CIO

During an attempt to close this flle, the number of files disposed to output queues
by the job has exceeded the limit for which the user is validated.

OVERLAPPING INSERT OR DELETE.

Insertions and deletions affect the same deck.

OVERLAY FILE EMPTY.

SAD

No data appears in the requested file.

OVERLAY FILE NOT FOUND.

SAD

The specified file was not available.

OVERLAY LEVEL NOT (0,0).

LINK

The overlay was not a zero level (0,0) overlay.

OVERLAY NOT FOUND.

OVERLAY NOT FOUND IN LIBRARY.

3AD/3AE
LDR

The specified overlay was not found.

The specified overlay was not found in the system library.

PACK PARAMETER ERROR.

PARITY ERROR - RESTARTED FROM kk.

PACK
RESTART

The PACK control statement contains an err-or.

Because RESTART detected a parity error In attempting to restart from the
specified checkpoint nn, the alternate checkpoint kk was used instead.

PBC ARGUMENT ERROR.

CPMEM

Either the first word address or the last word address specified on a PBC control
statement was nonnumeric.

o
»{».
o
-J
o
o
o

Message

Routine

Description

PBC FWA .GT. LWA.

CPMEM

The first word address was greater than the last word address.

PBC RANGE ERROR.

CPMEM

The last word address parameter specified on a PBC statement was greater than
or equal to the user's field length.

PFM ABORTED, AT nnn.

PFM

Error flag detected at PFM control point.

PFM ILLEGAL REQUEST, AT nnn.

PFM

One of the following:

• Illegal command code passed to PFM

• Illegal permit mode o r catalog type specified

• CATLIST request has permit specified without a file name

• PERMIT command attempted on a public file

PF UTILITY ACTIVE, AT nnn.

PFM

Because a permanent file utility is currently active, the operation was not
attempted; the user sho'old retry the operation.

PL ERROR IN DECK dname.

Error encountered in processing deck dname.

POSITION ERROR ON— xxxxxxx.

File xxxxxxx was not repositioned after being checkpointed because CHKPT
tected an address error.

de-

POSITION LOST, fff AT nnn.

CIO

During write error recovery, the system could not find the last good block
making It impossible to successfully perform error recovery.

of data.

PP CALL ERROR.

3AB

The monitor detected an error in a CPU request for PP action.

PROPILA UPDATED.

PROFILE

The project profile file was successfully updated.

PROFILE ABORTED.

PROFILE

Central site operator aborted PROFILE.

PROGRAM FILE EMPTY.

TCS

A load of an empty data file was attempted.

PROGRAM LIBRARY EMPTY.

The old program library contained no data.

PROGRAM NOT FOUND.

EXU

The program to be loaded was not found on the specified library file.

PROGRAM NOT ON MASS STORAGE.

EXU

The program does not reside on a mass storage device.

PROGRAM STOP AT xxxxxx.

SAB

The monitor detected a program stop instruction at address xxxxxx.

PROGRAM TOO LONG

EXU

The program does not fit in the available storage.

o
-J

o
o
o

Message

Routine

Description

PROTECTED FILE

The user has attempted to release a locked file.

PRU LIMIT. AT nnn.

PFM

The job's mass storage PRU limit has been exceeded during preparation of a local
copy of an indirect access file.

PRU LIMIT. FILE fff AT nnn.
PRUS REQUESTED UNAVAILABLE.

CIO

3PF

The job's mass storage PRU limit was exceeded during an attempt to write or

extend this file.

The number of PRUs requested is not available.

PRUS REQUESTED NOT AVAILABLE, AT nnn.

PFM

The number of PRUs specified via the s parameter on the DEFINE request is not
available.

QDL ARC ERROR.

QDL

Parameter addresses passed to QDL were not within the user's field length.

QDL ILLEGAL REQUEST.

QDL

One of the following:

• The job was not of system origin and the user did not have system
origin privileges.

• Job did not have SSJ= entry point.

• Auto recall bit was not set.

• The RA+1 call to QDL contained an illegal function code.

QFM ARGUMENT ERROR.

QFM

One of the following:

• Address is outside field length

• Address Is equal to one

• Origin code is out of range

• ID code is out of range

QFM EOI BAD ON ATTACHED FILE.

QFM

The EOI sector cannot be found on the specified file.

QFM FILE ALREADY ATTACHED.

QFM

The specified file is already attached to the control point.

QFM FILE EMPTY.

QFM

The submitted file has not been used.

QFM - FILE IGNORED filename.

QFM

The file was ignored because it had an illegal origin or type code. It could
indicate a bad IQFT file.

QFM FILE NAME ERROR.

QFM

The Ifn specified does not check as a valid file name.

QFM FILE NOT FOUND.

QFM

The submitted file could not be found.

QFM FILE NOT ON MASS STORAGE.

QFM

The submitted file does not reside on mass storage.

QFM ILLEGAL EQUIPMENT.

QFM

The equipment specified in FET+7 either is not mass storage or is not in the
range of the EST.

QFM ILLEGAL FILE TYPE.

QFM

The submitted file is not a local file.

QFM ILLEGAL ID CODE.

QFM

The ID code is out of range.

QFM ILLEGAL ORIGIN TYPE.

QFM

The origin type for the submitted file is not batch or Export/Import.

o
M^
o
-J
o
o
o

Message

M
-J

QFM ILLEGAL REQUEST.

QFM INTERLOCK ERROR.
QFM TRACK MISMATCH.

QFM UNABLE TO INTERLOCK MST.

QREC/QLIST ABORTED. \

QUEUE STATUS INDEFINITE.)
QUEUE FILE UTILITY COMPLETE.

QUEUED FILES LOST.

QUEUES UNRECOVERABLE THIS DEVICE.

RANDOM ADDRESS NOT ON FILE fff AT nnn.

READ AFTER WRITE, fff AT nnn.
READ FILE BUSY - Ifn
nnnnn RECORDS CONVERTED.

n RECORD(S) NOT REPLACED.
RECORD SIZE EXCEEDS 500.

RECORD TOO LONG.

REPRIEVE IMPOSSIBLE - BAD CHECKSUM
REQUEST UNDEFINED ON DEVICE fff AT nnn.

RERUN NOT POSSIBLE.
RESEX DETECTED ERROR.

Routine

QFM

QFM
QFM

QFM
QREC
QFSP
QREC

QREC

CIO

SUBMIT

CPMEM

SFP
CIO

IDS

LFM

Description

One of the following:

• Specified function illegal or undefined

• Job did not have SSJ= entry point

• Auto recall bit was not set

Track interlock could not be set due to a conflict.

The file about to be purged is not the same file that was previously attached.
The first track in the EST does not equal the one from the DULL word.

Informative message.

This pair of messages occurs if QREC aborts for any reason.

Informative message.

Files which process error conditions were not requeued. This error should never
occur but may if QREC was aborted and could not modify its files correctly. A
level deadstart will recover the queues.

This message is issued in conjunction with the mass storage error message

DNdn FMxxxxxxx MS ERROR.
Refer to that message for the appropriate device information.

The random address specified was not within the bounds of the file. The system
provides a dump of the FET on file OUTPUT.

The user attempted to read a tape on which the last operation was a write.

The read file is found to be busy (direct access file only).

Informative message indicating number of records <nnnnn) converted from one
character set to another.

Informative message; the job Is aborted unless the D option was specified.

ine mtiximuiii iine iengcii lur
exceeded.

reuui'u lu ue cuiivcx^lcu \uuu uiiew"«ti: lci's » weiEs

The record is too long for available memory. Available memory is filled and the
excess data Is skipped. In response to a WBR requests the record length
parameter was greater than or equal to the user's field length.

Post-recovery checksum does not match pre-recovery checksum.

The specified function cannot be performed on the device on which the file resides.
The system provides a dump on the FET on file OUTPUT.

Operator attempted to rerun a job that is In no-rerun mode.

The resource executive (RESEX) detected an error.

da
t

C»

o
o

-4
O
O

Message

Routine

Description

RESEX FAILURE, AT nnn.

PFM

The resource executive has detected a fatal error.

RESOURCE DEMAND ERROR.

RESEX

The user attempted to decrease the number of scheduled units to less than the
number of currently assigned units, or Increase the number of scheduled units
to a point where a deadlock would occur.

RESOURCE TYPE ERROR.

RESEX

The user specified an illegal resource type.

jobname RESTARTED FROM yy/mm/dd. hh.mm.ss.

RESTART

The checkpolnted job identified by jobname was restarted from the checkpoint
taken on the specified data and time. This message is issued whenever a check-
point job is restarted.

ROLLIN FILE BAD.

IRI

An illegal format was detected In the rollin file.

SFM ARGUMENT ERROR.

SFM

The argument passed to SFM was out of bounds or the FET specified did not
specify a buffer of at least lOOg words.

SFM DAYFILE BUSY.

SFM

Action was requested on a busy dayfile.

SFM ILLEGAL DAYFILE CODE.

SFM

The dayfile code passed in the FET was not within range.

SFM ILLEGAL REQUEST.

SFM

The requested function or origin type specified in the function call was not
recognizable, or SFM request was made and the auto recall bit was not set.

SFM TRACK INTERLOCK ERROR.

SFM

Track was either interlocked when it should not have been or not interlocked when
it should have been.

SMF UNABLE TO INTERLOCK DEVICE.

SFM

SFM request was not performed because the selected device could not be inter-
locked.

SEP CALL ERROR.

SEP

SFP was not loaded by default.

SFP.xxx ILLEGAL ORIGIN CODE.

SFP

Function illegal for user's job origin.

SFP/xxx PARAMETER ERROR.

SEP

Parameter address outside FL.

SPCW CALL ERROR.

lAJ

A DMP= type call was made and the program called is either not in the CLG
or does not have a DMP= entry point defined.

SPECIAL REQUEST PROCESSING ERROR.

SFP

The SPCW word was busy.

STATUS ERROR. f« AT nnn.

CIO

An irrecoverable error was encountered. A second message line describes the
error in more detail.

CRC ERROR. An error was detected In cyclic redundancy character.

DATA TIMING Hardware malfunctions. Another unit should be tried.

PROBLEMS.

FILL STATUS The system has detected an odd number of frame, a

ILLEGAL. condition which is illegal for the data format of the

tape being read.
FLAG BIT ERROR. The tape being read with ASCII conversion contains

characters not included in the 128-character set.
MEMORY PARITY A parity error was detected in the conversion memory
ERROR. of the tape controller.

o
-J

Message

Routine

Description

MULTI-TRACK Multiple tracks were found to be in error at 1600 cpi,
PHASE ERROR. making recovery impossible.
PARITY ERROR. The tape could not be read/written correctly.
UNIT HAS MOTION The tape unit cannot properly write the tape. The
PROBLEMS. user should resubmit his job, using a different tape
unit.

SYSTEM ABORT.

IMA

PP program detected an irrecoverable system error.

SYSTEM SECTOR ERROR.

QFM/QDL

An error occurred while reading the system sector.

TABLE OVERFLOW.
JOB ABORTED.

Resubmit job with increased field length.

TAPE BLOCK DEFINITION ERROR.

RESEX

The user attempted to define data block size via the EC or C keyword or noise
block size via the NS keyword in such a manner that the system is unable to
correctly define the size of the data block. The omission of the FC or C param-
eter on a control statement where it is required also causes this message to be
issued.

TAPE FORMAT PROBABLY WRONG.

CIO

This message is issued In addition to one of the following messages:

BLOCK SEQUENCE ERROR, fff AT nnn.
BLOCK TOO LARGE, fff AT nnn.
WRONG PARITY, fff AT nnn.

if one of these error conditions occurs on the first block.

TIME LIMIT.

SAB

The monitor detected that the time limit for the job has expired.

TIME LIMIT EXCEEDED.

CPM

Job used more CPU time (In seconds) than allowed.

TL NOT VALIDATED.

ACCFAM

The time limits specified on the job statement exceed that for which the user is
validated.

TOO MANY ARGUMENTS,
or

TCS

The number of arguments on the control statement exceeds that allowed by the
program.

TOO MANY ARGUMENTS.

COPYB

More arguments were specified on a copy request than are allowed on that
control card.

TOO MANY DEFERRED BATCH JOBS.

QFM

The user is not validated for this function or he has more jobs in the system
than he is allowed. (All jobs in batch queues and E/I queues are counted.)
The count is ignored if the job is of system origin or the user is validated for
system privileges and DEBUG mode is set by the operator.

TRACK ALREADY ASSIGNED

QFM

The track byte for the IQFT file in the DULL word in the MST is already assigned.

TRACK LIMIT. FILE fff AT nnn.

CIO

The device on which the file resides is full.

UNIDENTIFIED LOADER INPUT.

LINK

The file to be loaded is not in correct format.

UNABLE TO READ IQFT FILE.

IMS /MSI

An attempt to initialize inactive queues failed because the IQFT file could not be
read.

Message

Routine

Description

o i
-a !

o
o
o

UNIDENTIFIED PROGRAM FORMAT.
UNRECOVERABLE MS ERROR.
UPMOD COMPLETE.
USER NOT VALID TO UPDATE.

VERIFY ERRORS.

WBR ARGUMENT ERROR.

WRITE ON READ-ONLY FILE fff AT nnn.

WRITE OVER LABEL ILLEGAL ON fff AT nnn.
WRONG PARITY, fff AT nnn.
25555 FIELD LENGTH INCREASE.

3AE
QFM

PROFILE

VERIFY
CPMEM
CIO

CIO
CIO

The file the user requested to be loaded was not in a recognizable format.

An irrecoverable mass storage error was detected during an I/O operation.

Informative message indicating UPMOD completion.

A user who attempted an update was not the master user for the specified charge
number entry. That entry is ignored and PROFILE skips to the next charge
number entry in Ifn,.

Errors were encountered during VERIFY routine.

The record length parameter specified on a WBR statement was nonnumerlc.

Either the user attempted to write on a file with write interlock or the direct
access file was not attached in write mode.

The user is not allowed to destroy the VOLl label.

A 7-track tape is being read In opposite parity from which it was written.

The job field length was too small for LIBEDIT. Field length was increased
to 26K.

LFM ERROR CODES

The following error codes are returned to the error code field of the FET word 0, bits
10 through 13 in response to LFM requests.

Error Codes Description

1 File not found

2 File name error

3 Illegal file type

4 File empty

5 Waiting for common file

6 Duplicate common file name

7 Illegal equipment

10 Equif)ment not available

11 Duplicate file name

12 Illegal user access

13 Illegal user number

14 Illegal ID code

15 Resource executive (RESEX) detected an error

16 I/O sequence error

17 Output file limit
20 Local file limit

PFM ERROR CODES

The following error codes are returned to the error code field of the FET word 0, bits
10 through 17 in response to PFM requests.

Error Codes Description

1 The specified direct access file is attached In the opposite
mode.

2 One of the following:

• The specified permanent file could not be found.

• The specified account number could not be found.

• The user is not allowed to access the specified file.

• The user issued an indirect access file command on
a direct access file.

• The user issued a direct access file command on an
indirect access file.

If this message occurs in response to the SAVE macro, the
specified local file is not attached to the control point, is a
direct access file, or is an execute-only file.

3 The file specified on a SAVE macro contains no data.

4 The file to be saved is not on mass storage; the first track
of the file is not recognizable.

60407000 D l-B-31

Error Codes Description

5 The user has already saved or defined a file with the name
specified.

6 The user attempted to define a file that was not a local file.

7 File name contains illegal characters.

10 The user is not validated to create direct access or indirect

access files or to access auxiliary devices.

11 The device type (r parameter) specified on a request for an

auxiliary device cannot be recognized or does not exist in
the system.

If the auxiliary device specified by the pn parameter is not
the same type as the system default, the r parameter must
be included; if not, this message is issued.

12 The local file specified for a SAVE, REPLACE, or APPEND

command exceeds the length allowed, or the direct access
file specified for an ATTACH in write, modify, or append
mode exceeds the direct access file length limit for which
the user is validated.

13 One of the following:

• Illegal command code passed to PFM

• Illegal permit mode or catalog type specified

• CATLIST request has permit specified without a file

name

• PERMIT command attempted on a library file

14 Access to the permanent file device requested is not possible.

15 The device on which the file resides may not contain direct

access files because:

1. The device is not specified as a direct access de-
vice in the catalog descriptor table.

2. llie device is not specified as ON and initialized
in the catalog descriptor table.

3. The device is a dedicated indirect access perma-
nent file device.

16 Because a permanent file utility is currently active, the

operation was not attempted; the user should retry the oper-
ation.

17 An error occurred in a read operation during a file trans-
fer.

20 The nunrber of files in the user's catalog exceeds the limit

(refer to LIMITS control card, section 6 ).

21 The cumulative size of the indirect access files in the user's

catalog exceeds the limit (refer to LIMITS control card,
section 6).

l-B-32 60407000 D

Error Codes Description

22 The number of PRUs specified via the s parameter on the

DEFINE macro is not available.

23 A request was attempted on a local file that is currently

active. This error can occur, for example, if the user
creates two FETs for the same file and issues a second
request before the first is completed.

24 The job's local file limit has been exceeded by an attempt

to GET or ATTACH the file.

25 The job's mass storage PRU limit has been exceeded during

preparation of a local copy of an indirect access file.

30 The resource executive has detected a fatal error.

31 No allocatable tracks remain on equipment xx, where xx is

the EST ordinal.

32 The length of a file does not equal the catalog length; the

action taken depends on the type of command issued.

C ommand Action

GET A local file is created with length

being the actual length retrieved.

aWE If file length is longer than TRT

specification, file is truncated.

REPLACE Same as for SAVE.

33 Permit random address error.

34 The system sector data for the file does not match the

catalog data.

35 The same file was found twice during a catalog search.

This error can occur for APPEND or REPLACE commands
after a file is found and purged and tltie catalog search is
continued.

36 Error flag detected at PFM control point.

37 An error was encountered in reading a portion of the

permanent file catalog or permit Information.

Table 1-B-l specifies the action PFM takes if it detects an error while reading mass
storage. The symbols used in the table designate the type of response PFM makes
and are defined as follows:

Symbol Description Code

DTE DATA TRANSFER ERROR. 17

EOI Processing continues as If an EOI was encountered.

MSE MASS STORAGE ERROR. 37

FNF pfn NOT FOUND. 2

DAF DIRECT ACCESS FILE ERROR. 34

FLE FILE LENGTH ERROR. 32

60407000 D l-B-33

?, "O

S <"

3 a
m tn

.2.2

2 "«.

1—4

2? So

•1^

t— 1

-1—

■1—

1—4

ffi rr

«K

Kfl

H W

•-]

JCO

"co
fa^

E-i

aj ^

t— 4

« cd

o
U

eing read
catalog.

iz;

■^'fa

1— 1

m 0,

1— 1

trl

s-s

o "
03 O
03 "^

•

«« Si

1-^ n

1—1

H—
1— <

0) -2

^ I

1^ S;

U (3

fH O

1— 1

O X)

u s

,-^

•—1

4->

.-H

^ tl

o o

«3

P MO

g2
«.go

". tlfl(U

-M

■^ S-<

Ih O

iH O

1 t>

•a o

1 c

-devi

if ori,

sect

-devi
if ori
lid s

-4-a
CO

a<2

ai §

<u o

O 73

1 ^ tJ

1 h -

<3J0

CL.2

M m

" to o

sll

Device
transfe
file (no

.S !^

Readin
inform
update

•X3

Devi
tran
sect

^ 2 «i

Q *3 w

Devi
tran
file

III "*^

CtJ o
« 0)

H— +-

l-B-34

60407000 D

LIBEDIT

LIBEDIT is a binary record managertient program that is used to:

• Create and maintain a library file

• Copy records to a library file

• Delete records from a library file

• Replace records on a library file

Binary logical records are the basic unit manipulated. LIBEDIT manipulates the records
of the old library file and optional replacement files. Records for replacement can be
on one or more secondary files. Replacement is the implicit mode of a LIBEDIT run.
Additions and no-replacements must be explicitly requested.

LIBEDIT manipulates the following record types.

Relocatable central processor program (RED

Central processor overlay (OVL)

Multiple entry point overlay (ABS)

6000 peripheral processor program (PP)

7600 peripheral processor program (PPU)

Modify old program library deck (OPL)

Modify old program library common deck (OPLC)

Modify old program library directory (OPLD)

User library programs (ULIB)

Chippewa format central processor program (COS)

Unrecognizable as a program (TEXT)

Formats are further described in appendix G, volume 2.

LIBEDIT is called from the operating system library using a control card. The record
managing process is controlled by LIBEDIT directives.

LIBEDIT executes in two phases. During the first phase, it reads directives and re-
placement records. It groups directives by type and file and groups corrections when
several insertions take place relative to the same record.

During the second phase, LIBEDIT performs modifications and generates the new library.
If LIBEDIT cannot process the specified combination of directives and the D option
(refer to the following control card description) was not specified, LIBEDIT lists the
conflicting directives (or a simulated form of the directives), issues an error message,
and aborts the job. If the D option was specified, LIBEDIT continues processing the
directives.

60407000 D 1-C-l

CONTROL CARD FORMAT

The following control cards call the LIBEDIT program to be loaded and executed. Param-
eters specify, mode and files.

LIBEDIT(pj, pg. . . . , Pn)

The optional parameters, pi, can be in any order within the parentheses. Generally, a
parameter can be omitted or can be in one of the following forms.

a (C, R, and V only)

a=lfn

a=0

a is one of the following options: I, P, N, L, LO, B, C; R, and V. Ifn is the 1- to
7-alphanumeric character file name. LIBEDIT accepts only one instance of any param-
eter.

Option

I=lfn

1=0

I omitted

Description

Directives comprise the next record on file Ifn
No directive input
Directives are on file INPUT

P=lfn

P=0

P omitted

N=lfn

N=0

N omitted

L=l

L=0

L omitted

LO=lfn

LO omitted

B=lfn

B=0

B omitted

C omitted

R om^itted

V omitted

D omitted

File Ifn contains the old program library

No old program library file

Old program library is on file OLD

New program library will be written on file Ifn
Illegal; no error message is issued, if used
New program library will be written on file NEW

Short correction listing (includes only directives, modifications,

and errors) on the file specified by the LO parameter

No output is listed

Full correction listing is written on the file specified by the LO

parameter

List output on file Ifn

List output on file OUTPUT

Use file Ifn for the replacement file

Do not use a default replacement file

Use file LGO as the default replacement file

Copy the new library file over the old librai*y file after processing
Do not copy the new library file over the old library file after
processing

Do not rewind library files after processing

Rewind old a:id new library files after LIBEDIT and VFYLIB

processing

Call VFYLIB after LIBEDIT processing

Do not call VFYLIB to verify libraries after LIBEDIT processing

Ignore errors and continue

Do not ignore errors; abort Job

l-C-2

60407000 D

LIBEDIT DIRECTIVES

Directives comprise a program record on file INPUT or on the file specified through the
I mode parameter on the LIBEDIT control card. Directives control the record manage-
ment process. A directive begins with an asterisk in column 1 followed immediately by
the card identifier. The card identifier is delimited by a comma and/or one or more
spaces. Parameters are delimited by -, a blank, an end-of-line, or a comma.

Card parameters have no embedded blanks. If a directive does not begin with an
asterisk and a card identifier, LIBEDIT assumes the operation is a continuation of the
last directive operation. If the card was not preceded by a directive, the operation is
assumed to be:

*BEFORE *. gidj.gidg,. . ..gid^.
Note, however, that gid entries cannot be split between cards. For example, the cards

*B. OVL/Pl, OVL/P2, . . . , OVL/P

N
do not constitute a valid directive. The last entry would not be processed as OVL/PN.
Qn the other hand, the cards

*B, OVL/Pl, OVL/P2

OVL/P3

OVL/PN

TEXT/Tl

do constitute a valid directive and would be processed in the same manner as

*B, OVL/Pl, OVL/P2,OVL/P3, OVL/PN, 0. TEXT/Tl

Directives are not required. If they are not provided, LIBEDIT replaces the records
of the old program library file that have the same name and type as the records on the
correction file, and LIBEDIT writes the new library.

Parameters common to many of the correction directives are the reference record
identifier (rid) and the group record identifier (gid).

rid The rid parameter specifies a reference point for a correction. It can

be in one of the following forms.

type/rname Reference record is of the specified type

rname Reference record is the implied type (refer to type)

* Reference point is an end-of-file mark (^BEFORE

card only)

gid One or more gid parameters on a directive indicate records or groups

of records to be inserted, deleted, or replaced. A gid can be in one
of the following forms.

type/rname Single record of the specified type

type 2 / rname j^- Group of records beginning with rname of typej and
type2/rname2 ending with rname2 of type2. Types sire specified
or implied.

rname Record identifier can be one of the following.

rname Name of record

60407000 D

l-C-3

type

LIBEDIT recognizes the following directives.
Directive

* If used for rname. on an

INSERT. AFTER, BEFORE,
or IGNORE, an * indicates
that all records on the library
of the specified or implied
type are to be inserted or
ignored.

If used for rnameo on INSERT,
AFTER, BEFORE, or IGNORE,
an =!= indicates that all records
of typei, starting with rnamej^,
are to be inserted or ignored.

Indicates that a zero -length

record is to be inserted.

Identifies the type of the named record. When
type is absent from a rid or gid parameter,
LIBEDIT uses the type most recently speci-
fied on a directive. For valid types, refer
to the description of the TYPE directive.

Definition

*ADD

BEFORE or i=B

*BUILD

♦COMMENT

*COPY

*DATE

♦ DELETE or *D

♦FILE

♦IGNORE

♦INSERT or *I
♦AFTER or ♦A

♦NOREP

♦RENAME

♦REPLACE

♦REWIND
♦TYPE or NAME

Adds records at end of library.

Inserts records before the named record.

Builds an index at end of new file.

Adds comment to prefix table.

Copies new file to old at end of editing.

Adds date and comment to prefix table.

Deletes specified records.

Declares additional correction file.

Ignores records when reading correction file.

Inserts records from correction file after named record.

Does not auto raatic ally replace records frora named file.

Renames record.

Replaces records on old file with records from correction file.
Optionally declares current correction file as no-replace.

Designates file to be rewound before and after editing.

Sets type of library to be used for default.

l-C-4

60407000 D

FILE

The directive format is:

*FILE Ifn

Ifn Name of the additional replacement file; subject to operating system

restrictions on file names. If Ifn is an *, LIBEDIT uses the re-
placement file specified by the LIBEDIT control card or the default
file (LGO), if none is specified.

The FILE directive declares a secondary file as an additional file that contains replace-
ment records. LIBEDIT directives following a FILE card specify records on the declared
replacement file.

REWIND

The directive format is:

^REWIND Ifn

Ifn Name of file to be rewound

LIBEDIT rewinds the specified file before and after editing.

TYPE OR NAME

The formats for the directives are:

*TYPE type
*NAME type

type Specifies default type of internal record format:

REL Relocatable CPU program

OVL CPU overlay program

ABS Multiple entry point overlay

PP 6000 series format peripheral processor unit program

PPU 7600 format peripheral processor unit program

OPL Modify old program library deck

OPLC Modify old program library common deck

OPLD Modify old program library directories

ULIB User library; begins with a ULIB type record and terminates

with OPLD type record

COS Chippewa format CPU program

TEXT Unrecognizable as a program

Any explicit use of a type or a rid or gid parameter resets the default value to the new
type.

With the TYPE (or NAME) directive, the user specifies the type of record to which sub-
sequent LIBEDIT directives refer. A type specification is in effect until the next TYPE
(or NAME) directive is supplied or until a type is explicitly declared on another directive.
If no TYPE or NAME directive is sup»plied or no explicit type is used, the type is TEXT.

60407000 D l-C-5

For example.

♦BEFORE *, JANE-*

* DELETE HENRY -IDA

♦INSERT GEORGE, MARY

/*TYPE COS
is equivalent to

♦BEFORE *. COS /JANE-*

*DELETE COS/HENRY-COS/IDA

INSERT COS /GEORGE, COS /MARY

INSERT OR AFTER

The formats for the directives are:

♦INSERT rid, gid^, gidg. .... gid^ or *I rid, gid^, gid^, .... gid^

♦AFTER rid, gid^^, gidg, .... gid^ or *A rid, gid^, gidg, .... gid^

rid Identifies the record on the old library file after which the

specified records or groups of records are to be inserted

gidj Identifies the records or groups of records from the replacement

file to be inserted after rid

An INSERT or AFTER directive directs LIBEDIT to insert records or groups of records
from the current replacement file after the specified old library record for transcription
to the new library file. The current replacement file is the most recent file specified
by a FILE directive or by the LIBEDIT control card,. Insertion of records causes auto-
matic deletion of the old records having the same names and types from the old library
file.

An example of the use of this directive is:
♦INSERT GPL/LEA, TEXT/OSCAR-*

These cards direct LIBEDIT to insert, after the OPL deck LEA on the old library file,
all TEXT records from OSCAR until an end-of-file mark is encountered. If any of these
TEXT records have the same name as a TEXT record that is already on the old library
file, the old TEXT record is not transcribed to the new library file.

j_(-._g 60407000 D

BEFORE

The directive formats are:

^BEFORE rid, gidj,gid2, . .. .gidn or *B rid,gid]^,gid2. . . • .gid^

rid Identifies the record on the old library file before which the

specified records are to be inserted. On the form omitting the
directive name, rid is assumed to be * (that is, insert before
end-of-file).

gidj Identifies records or groups of records from the replacement

file to be inserted before rid.

A BEFORE directive causes LIBEDIT to insert records or groups of records from the
current replacement file before the specified old library record for transcription to the
new library file. The current replacement file is the most recent replacement file
specified by a FILE directive or by the LIBEDIT control card. Insertion of records
causes automatic deletion of the old records having the same names and types from
the old library file.

DELETE

The directive formats are:

*DELETE gidj.gidg... ..gidn or *D gid^, gidg. . • • . gid^

gid. Identifies records or groups of records to be deleted from the

^ old library file. An asterisk cannot be used.

The DELETE directive causes LIBEDIT to suppress copying of the specified records
from the old library file to the new library file.

An example of the use of this directive is:
*DELETE PPU/LAD-REL/RUN

This card directs LIBEDIT to delete records starting with 7600 PPU program LAD
through relocatable CPU program RUN.

IGNORE

The directive format is:

^IGNORE gidj, gid2. .... gid^

gidj Identifies records or groups of records from the replacement file

to be ignored.

The IGNORE directive causes LIBEDIT to Ignore a record or group of records on the
current replacement file during record processing.

An example of the use of this directive is:

^IGNORE FRAN-*
*FILE WOMAN

LIBEDIT ignores program FRAN of the current type and all following programs of the
current type until an end-of-file mark on the replacement file WOMAN is encountered.

60407000 D l-C-7

ADD

The directive format is:

*ADD lib. gidj, gid2. .... gidj,

lib Specifies that the library is to be added to the old program library

file before the zero -length record for the old library file indicated.
A library cannot be added if there is no zero-length record.

LIB! to Libraries 1 through 63 on the old program library file.
LIB63
gid. Identifies records or groups of records to be added to the speci-

^ fied library.

The ADD directive causes LIBEDIT to append records to the specified library for tran-
scription to the new library. Two libraries are separated by a zero-length record on the
new library file.

NOTE

Directories are determined from file OLD; adding
a zero-length record does not change the directory
of the library being added.

Figure 1-C-l illustrates where records are inserted with the ADD directive.

CATALOG

CI- NEW

FILE

REC

NAME

TYPE

LENGTH

CKSun

DATE

conoRDU

TEXT

2DbS

7231

concuTu

TEXT

ISDb

3sm

I.lHl

nopup

TEXT

113bS

2bb2

LLT

TEXT

20t7

10Mb

RTtI

TEXT

bit

Mb31

LIST

TEXT

bD23

7735

A flrli>in' i .' V-»^»r*-«»n-i

{003-

sun

= 2bllQ

zero-lengtli record

KROQS

TEXT

3S1

im3

CHP7

TEXT

132

27b0

LI 132

cnP6

TEXT

17 S

132M

CflPI

TEXT

3Sb

5203

•CQO>

sun

lasb

KROQMb

TEXT

11S3

S05S

I.IB3

KR00M7

TEXT

41S

5313

KRODMl

TEXT

IDDDS

S3bS

■CDQ}

sun

- 11S7S

RUNOMfi

TEXT

b7M5

Ifi

RUN0M1

TEXT

37MM

1,1154

RUNDSQ

TEXT

bM37

RUNQSl

TEXT

bb71

RUNDD3

TEXT

231

0253

■CDO>

sun

4MS

KRONDl

TEXT

07Q3

SMP

TEXT

1373

323b

MH") ,

PdON

TEXT

13D1

bH7D

zscpom

TEXT

25Sb

3132

■CDQ}

sun

5523

I.IBfi <

2fi

MODIFY

OPL

1251DS

2MSS

7D/lD/m.

{D0>

sun

= lasios

Last Uhi-a»-y cannot

- .^^n

noDS

OPLD

7172

71/01/12.

be ipf('r«jnc(Ml by

^JU

ADI) hut can he

T-el(M'('nt!ed by a

* EOF *

sun

= 17MS37

HKKOKK end-of-nie

Figure 1-C-l. Adding to the Old Program Library

l-C-8

60407000 D

BUILD

The directive format is:

*BUILD dname

dname Name of directory record.

The BUILD card requests LIBEDIT to construct and append a directory record in Modify
format to the new library file. If the old library file has such a directory, LIBEDIT
automatically generates a new directory deck without an explicit BUILD request.!

COMMENT

The directive format is:

*COMMENT rid comment

rid Name of the record on the replacement or old library file.

comment A string of up to 40 jq characters that is suitable as a comment.

Additional characters are truncated.

The COMMENT card adds a comment to the prefix (77) table for a program

on a replacement file or the old library file. If the program previously did not have a

prefix table, LIBEDIT generates one that includes the date and the comment.

DATE

The directive format is:
*DATE rid comment

rid Name of the record on the replacement or old library file.

comment A string of up to 40io characters that is suitable as a comment.

Additional characters are truncated.

The DATE card adds the current date and the specified comment to the prefix (77) table
for a program on a replacement file or the old library file.

NOREP

The directive format is:

*NOREP lfni.lfn2....,lfn,j^

The NOREP card declares the specified replacement files to be no-replace files. LIBEDIT
does not replace all records of the old library file with records on the no-replace file
having identical names, but selectively replaces records from a no-replace file according
to REPLACE. INSERT, and BEFORE directives.

t BUILD can also be used to change the directory name.

60407000 D l-C-9

RENAME

The directive format is:

♦RENAME rid, name

rid Name of the record on the replacement or old library file to be

renamed.

name New name of the record (1 to 7 characters),,

The RENAME card assigns a new name to a record on the old library or the current
replacement file for transcription to the new library file. If the renamed record is
referenced by another correction card in the same run, the old name should still be
used.

REPLACE

The directive format is:

♦REPLACE gid^.gidg, ...,gidj^

gidj Name of the record or record group from the replacement file

to replace on the old library file.

The REPLACE card directs LIBEDIT to selectively replace records on the old library
file with records of the same name from a current replacement file that has been de-
clared a no-replace file (refer to the NOREP card description). Thus, the user can
selectively replace records by using the NOREP and REPLACE directives, or he can
selectively not replace records by using the IGNORE directive according to the circum-
stances.

An example of the use of this directive follows: A user has a replacement file named
FRUIT containing records APPLE, CEDERRY, GRAPE, and ORANGE. Records having the
same names are on the old library file. The user wishes to retain records APPLE and
CHERRY but replace records GRAPE and ORANGE.

The following two sequences of directives produce the same results.

^♦REPLACE GRAPE -ORANGE /*IGNORE APPLE -CHERRY

/*NOREP FRUIT /*FILE~FRUIT

j^*FILE FRUIT

COPY

The directive format is:

♦COPY

The COPY card directs LIBEDIT to copy the new library file to the old library file after
it has processed all correction cards.

1-C-lO 60407000 D

LIBEDIT EXAMPLES

The following two examples illustrate the use of LIBEDIT.

Job 1:

The following steps describe the operations performed by job 1.

1. The job requests an old deadstart tape, OLDSYS.

2. The job modifies decks CPM and SYS EDIT (fromOPL) with the changes from the
input file, assembles the two decks, and writes the new binary code on file LGO.
The MODIFY control card assumes that file OPL is a read-only common file.

If, however, OPL is a direct access permanent file, the user must include an
ATTACH control card before issuing the MODIFY request.

3. LIBEDIT reads the new binary code from LGO, the old binary code from
OLDSYS, and writes a copy of OLDSYS to file NEW with the two decks (CPM
and SYSEDIT) replaced with the new code.

4. The job requests a new deadstart tape.

5. File NEW is then copied to the new deadstart tape, NEWSYS, and the copy is
verified.

JOBKCMeoOOO, TlOO)
USER(U5ERNUM. PASSWRD, FAMl)

REQUEST(OLDSYS)

MODIFY (Q)

LIBEDIT(P=OLDSYS,I=0)

UNLOAD(OLDSYS)

RETURN(OLDSYS)

REQUEST (NEWSYS)

REWIND(NE W, NEWSYS)

COPY (NEW, NEWSYS, V)

UNLOAD(NEWSYS)

RETURN(NEWSYS)

-EOR-

♦IDENT CPM****

*/ ****PREVENT TIME LIMIT ON TELEX JOBS

*/ WHEN SETTING TIME LIMIT

*DECK CPM

*I, 265

UJN STL5

*I, 266

STL5 BSS

*IDENT SYSED**

*/ .,^^^jPjX ERROR THAT CAUSES CERTAIN

*/ LIBDECK CARDS TO BE IGNORED.

*DECK SYSEDIT

*I, 1360
SL52.1

BSS

*D, 1379

SA2

SB3

B2, B3. 5LS1

IF NOT END OF BUFFER

*EDIT CPM, SYSEDIT
'■EOI'*

60407000 D 1-C-ll

Job 2:

The following steps describe the operations performed by job 2.

1. The job copies the source decks for VERIFY and VFYLIB from file INPUT to

file VERS. (Note: The 6/7/9 card following VFYLIB makes the COPYBF possible.)

2. It creates the decks VERIFY and VFYLIB and writes them in program library
format to file NFL. It then assembles the decks and writes the binary code to
file LGO.

3. LIBEDIT reads the program library code from file NPL and writes a copy of the
old program library OPL to file N. At the same time, it inserts the code for
VERIFY and VFYLIB immediately following the program UPMOD (this assumes
that VERIFY and VFYLIB are not already on file OPL).

4. It requests a new program library tape.

5. File N is copied to tape file NEWPL and verified.

6. It requests an old deadstart tape OLDSYS.

7. LIBEDIT reads the binary code for VERIFY and VFYLIB from file LGO and writes a
copy of the old system object programs from file OLDSYS to file NEW. Meanwhile, the
code for VERIFY and VFYLIB is inserted immediately before the fourth zero-length
record on file OLDSYS (this assumes that VERIFY and VFYLIB are not already on file
OLDSYS).

8. It requests a new deadstart tape file NEWSYS.

9. File NEW is then copied to tape file NEWSYS and verified.

l-C-12 60407000 D

JOB2(CM60/)00, T7777,)

USER(ajSERNUM, PASSWRD, FAMl)

COPYBFdNPUT, VERS)

COMMON(OPL)

MODIFY(Q,N,CL)

LIBEDIT(P=OPL, B=NPL. N=N)

REQUEST(NEWPL)

REWIND(N. NEWPL)

COPY(N„NEWPL,V)

UNLOAD(NEWPL)

RETURN(NEWPL)

REQUEST(OLDSYS)

LIBEDIT(P=OLDSYS)

UNLOAD(OLDSYS)

RETURN (OLDSYS)

REQUEST(NEWSYS)

REWIND(NEW, NEWSYS)

COPY(NEW,NEWSYS,V)

UNLOAD(NEWSYS)

RETURN(NEWSYS)

-EOR-

VERIFY

Insert VERIFY program source deck here.

-EOR-

VFYLIB

Insert VFYLIB program source deck here.

-EOF-

*REWIND VERS

♦CREATE VERS

*EDIT

VERIFY, VFYLIB

-EOR-

*TYPE

OPL

*INSERT

UPMOD, VERIFY, VFYLIB

-EOR-

*ADD

LIB4. ABS/*, OVL/*

-EOI-

I
I

LIBEDIT issues dayfile messages to report program completion or errors encountered
during processing. A fatal error results in job termination. In recreating the card
for the error listing, the parameters are changed to reflect the rid (record reference
identifier) or gid (group reference identifier) being processed when the error was
encountered. These messages are included in Appendix B.

60407000 D

l-C-13

JOB OUTPUT INFORMATION

Appendix D lists the output information printed for the sample job below. The notes in
the right margin identify the various format conventions of KRONOS output.

The following control cards are submitted.

TESTA(CM50000, TIO)
USER(JEANCOM, PASSWOR. SYSl 72)
FTN.
-EOR-

PROGRAM CONVERdNPUT, OUTPUT)
C THIS PROGRAM CONVERTS OCTAL TO DECIMAL

C THE SECOND VALUE PRINTED IS 10 OCTAL TIMES THE FIRST

C TERMINATE BY TYPING ZERO

2 CONTINUE
READ 1, J

1 FORMAT(08)

K=J*10B

PRINT 6, J.K
6 FORMAT(5X, 110, 5X, 110)

IF{J. EQ. 0)3, 2

3 CONTINUE
STOP
END

-EOI-

60407000 D 1-D-l

KROHOS Z,i-hw. r3/0*»/19.

OPERATING SYSTEM
JOB ORIGIN ' BATCH.

USER NUMBER = JEANCOM
JOBCARD NAME ' TESTAOO

The first three lines of the banner page indicate that this local batch job
was run under the control of version 2, 1. 2 of the KRONOS Operating System.
The system creation date was April 19, 1975.

The user number is that which was supplied on the USER card. The jobcard
name is the name of the particular job which was supplied on &e job card.

AAAAAAAAAA

fFPFFFFFFPFP

tITXIIIIIIII

AAAAAAAAAA

AAAAAAAAAAAA

F.FFFFFFFFFFF

IIIIIIIIIIII

AAAAAAAAAAAA

AA AA

rFFFFFF?

AA AA

AAAAAAAAAAAA

FFFFFFFF

AAAAAAAAAAAA

AA AA

A A A A

AA AA

riiiiiiiiiii

AA AA

IIIIIIIIIIII

AA AA

ICCCCCCC3C

cccccccccacc

cc cc

cc
cc
cc

C3 cc

cccccccccccc
cccccccccc

FFFFFFFFFFFF

FFFFFFFF

FF
FF
FF
FF
FF
FF

7S/06/02. 13.26.27.

This line specifies the current date
(June 2, 1975) and the time (hh.mm, as.)
when ttie job printing was initiated.

The first four characters of
the banner job name are gen-
erated from the user index
associated with the user num-
ber. These four characters
are unique to each user and
remain the same for subse-
quent jobs run under the same
user number. The last three
characters are the job se-
quence number assigned by the
system at the time of pro-
cessing.

en
o
)t^
o
-J
o
o
o

o
if^
o
-J

o
o
o

D
I

PROGRAM CONVER

7Z/7S 0PT=1

FTN i».i»+Uitni

75/06/02. 13.26.2it.

PAGE

PROGRAM CONWERtlNPUT, OUTPUT}
C THIS PROGRAM COMWERTS OCTAL

C THE SECOND VALUE PRINTED IS

C TERMINATE BY TYPING ZERO

2 CONTINUE
READ 1,J

1 FORMAT (OS)

6 FORMAT(5X,I10,5X, IIOJ

K=J»10B

PRINT 6,JsK

IF(J.EQ.0)3,2

3 CONTINUE
STOP

END

TO DECIMAL

10 OCTAL TIMES THE FIRST

The job calls the FORTRAN Extended compUer
which compiles the program. CONVER, contained
in the program record. The symbolic reference
map for program CONVER is printed below.

SYMBOLIC REFERENCE MAP tR=l >

ENTRY POINTS
V107 CONVER

VARIABLES
«fl37 J

SN TYPE
INTEGER

RELOCATION

FILE NAMES
INPUT

MODE
FMT

2nitl OllTP'JT

STATEMENT LABELS
'»12'f 1 FMT
'♦126 6 FMT

l»l

<»l<fO

INTEGER

INACTIVE

STATISTICS

PROGRAM LENGTH
BUFFER LENGTH

3 6B
fftOSB

30
2115

>4^

AAFIACF. 75/06/02.(10) CVBER73 KRONOS This line specifies the job name, the current date, and the computer system being used.

13 26 23 TESTA CMSOOOO TlO The dayflle includes a listing of the Control cards, system supplied status messages, and

ir^fcpaii^CB 'icSNrnM 'sYsi?? program output, if any. Spaces precede status messages and program output. Each line

U.ieie'.'pTN? Includes the time the message was issued to the dayfUe.

13.26.25. .08<* C? SECONDS COHPILATION TIME ., xi. x » j ^ ^

1^ 26 2? iiFM=; ' n i;73KUNS The last four lines specify the type and amount of system resources the job used. This job

1326.25.UECP oIo93SEGS. used 0.573 kilo-units 6f mass storage activity. 0.093 seconds of CPU time, and 1.000 SRU.

13'26!25'aesr' lioOOUNTS. The job produced 0.iS2 kilo-lines of printable output. Depending on the resources used,

Is'zesz'uCLp' 23 ' 0.192KLNS. additional information may be included in the dayflle. The formats of these messages are

■ * * ' ' ' given under Job Completion in section 3.

o
><^
o

o
o

PERMANENT FILE DEVICE STATISTICS

The system allocates space for permanerAt mass storage files in units called reservation
blocks. The size of a reservation block depends upon the type of file and/or the type
of device on which the file is to reside. For indirect access files, the reservation
block size is always one PRU (64 CM words), regardless of the device residence.
For direct access files, the reservation block size is a multiple of PRUs and varies
according to the device type, as shown in the following table.

Device

Type Device

DA 6603 Disk System

DB 6638 Disk System

DC 863 Drum Storage

DD 853/854 Disk Storage

Drive (lln<_8)

DE Extended Core Storage

DF 814 Disk File

DH 821 Data File

DI 844 Disk Storage Sub-

system (l<^n<_8)

DP Distributive Data

Path to ECS

MD 841-n Multiple Disk

Drive (1< n<.8)

PRUs/
Block

CM
Words

Characters

Maximum
No. of Blocks

50.
64

3200,
4096

32,000,
40, 960

2048

3136

31,360

2048

1600

16,000

256

n>!26 *

n*1664

n*16, 640

n*400 (854)
n*200 (853)

1024

10,240

121 for 125K
243 for 250K

5440

54, 400

2048

320

20,480

204, 800

2048

n*107

n*6, 848

n*68,480

n*1616

1024

10, 240

121 for 125K
243 for 250K

n*32

n*2048

n*20, 480

n*1600

In this table, n indicates the unit count for multiunit devices.

In general, the largest permanent file the user can create is a direct access file that
resides on a nonmaster device within his family of permanent file devices. Such files
are restricted in size by the limitations of the device itself and the DS validation
parameter which limits the size of direct access files. If no DS restriction is im-
posed, the maximum file size equals the maximum number of reservation blocks that
can be allocated for the device.

All other permanent files reside either on the user's master device or on an auxiliary
device. Their maximum size is restricted to the device limit minus any space allo-
cated for catalog information and other files. In addition, an installation can use the
FS validation parameter to limit the size of indirect access files.

60407000 D

1-E-l

CARD FORMAT AND CONVERSION PROBLEMS

Data within the system is stored in binary or coded records. Binary records are vari-
able in length and consist of cen1;ral memory images. Coded records consist of lines
of display-coded characters. Binary and coded data can enter the system in several
different formats as some enter the system directly; others must be converted to a
recognizable form by the peripheral driver that enters the data. The converted data
can reside in the system in several formats. The processing program must recognize
the specific format and process the data accordingly.

Described are the formats for punched cards and the format for printed data. In
addition, this appendix describes the conversion performed by the system on data trans-
ferred between the system and peripheral devices and the method by which time- sharing
terminal data is converted in the system.

When using the 64 character set, the user should avoid using consecutive colons
(00 characters). It is possible for these colons to be Interpreted as an end-of-llne.
An end-of-line is defined as 12 to 66 bits of zero right-justified in one or two central
memory words. If consecutive colons appear in the lower 12 bits of a central memory
word, they are interpreted as an end-of-line rather than as colons.

Example :

The following characters are punched on a coded card beginning in column 1:
:::::::::A::::::::AA

This would appear in memory as follows:
59 47 35 23

00 00

00 01

: :

• •
■ •

: :

: A

00 00

01 01

: :

A A

00 00

end-of-line

60407000 D

1-F-l

However, if the characters were copied with the COPYSBF utility, the following would
appear:

55 00

00 00

end -of -line

01 00

00 00

00 01

A :

: :

: A

01 00

00 00

end -of -line

NOTE

If a colon is the last character of a line, the
system appends a blank character to preserve
the colon and then appends an end -of -line.
(Two blanks may be added to ensure an even
number of characters. )

FORMATS FOR CARDS READ

The system reads cards in coded and binary formats,
in both formats.

The following conditions apply

1. A card with a 7/8/9 punched in cplumn 1 is, an EOR mark.

2. A card with a 6/7/9 punched in column 1 is an EOF mark.

3. A card with a 6/7/8/9 punched in column 1 is an EOI mark.

The reaminder of each card is ignored except for columns 79 and BO of the EOR and
EOF cards. These columns can contain the keypunch conversion mode for the input
records that follow. Conversion modes are discussed in the following section.

CODED CARDS

Cards are read in Hollerith punch code. The 3447 card reader controller converts the
Hollerith code to internal BCD code and passes the data to the card reader driver. The
driver converts the data from internal BCD code to display code. Up to 80 characters
can be transferred per card. Trailing spaces are deleted.

Two conversion modes, 026 and 029, t exist for the Hollerith punch code. All data
is converted in the system default keypunch mode unless a conversion mode change is
specified. This change can be specified on any of the following cards.

The job card, 7/8/9 card (EOR mark), and 6/7/9 (EOF mark) can contain the keypunch
conversion mode in columns 79 and 80. A 26 punched in columns 79 and 80 indicates
all subsequent coded cards are converted in 026 mode. A 29 indicates subsequent cards
are converted in 029 mode. Each conversion change remains in effect until another
change card is encountered or the job ends. The user can switch between 026 and
029 mode as often as desired. If 26 or 29 does not appear in columns 79 and 80 of the

t These codes are ignored by a 200 User Terminal since conversion mode is selected
by a hardware switch. (Refer to the Export/import Reference Manual. )

l-F-2

60407000 D

job card, the Initial keypunch mode of that job is the system deftiult mode. If 26 or
29 does not appear on a 7/8/9 or 6/7/9 card, no conversion change is made and the
most recent keypunch mode remains in effect.

Keypunch mode can also be changed by a card containing a 5/7/9 punch in column 1.
A blank (no punch) in column 2 indicates 026 conversion mode; a 9 punched in column
2 indicates 029 mode. The conversion change remains in effect until another change
card is encountered or the job ends.

The 5/7/9 card also allows literal input when 4/5/6/7/8/9 is punched in column 2.
Literal input allows 80 column binary data to be read while transmitting input in coded
mode. Cards are read (16 central menaory words per card) until a card identical
to the previous 5/7/9 card (4/5/6/7/8/9 in column 2) is read. The next card can
then specify the new conversion mode.

BINARY CARDS

Binary cards are denoted by a 7/9 punch in column 1 and can contain up to 15 central
memory words. The 3447 card reader controller reads the binary data and passes it
to the card reader driver in 12 -bit codes. Each card column row corresponds to a bit
position. The driver checks the checksum figure if this option is specified. The driver
then passes the data to the central memory buffer.

The fields within a binary card are:

Column(s) Descrip t ion

1 7/9 punch indicates a binary card

4 punch ignores checksum punch in column 2

Rows 0, 1, 2, and 3 contain the binary equivalent of the
word count of the card

2 Binary data checksum (modulo 4095)

15 central memory words of binary data
Blank
24-bit binary card sequence number

3 through 77

79 and 80

SUMMARY

The following punches appearing in column 1 of a card have the corresponding meaning
to the card reader driver.

Punch

7/8/9

6/7/9

6/7/8/9

5/7/9

7/9

Not 7 and

Represents
End-of-record (optional conversion mode change)
End-of-file (optional conversion mode change)
End-of -information

Conversion mode change /Read 80 column binary
Binary card
Coded card

B0407000 D

l-F-3

FORIVLAT FOR CARDS PUNCHED

Punched cards can be in three formats.

• Coded (punch Hollerith)

• Binary

• Absolute binary

The following conditions apply to all three formats.

• When an EOR is encountered, a card is punched with a 7/8/9 in columns 1 and
80. This card is offset.

• When an EOF is encountered for a file, a card is punched with a 6/7/9 in
columns 1 and 80; the remainder of the card is blank. This card is offset.

• When an EOI is encountered on a file, a card is punched with a 6/7/8/9 in
columns 1 and 80; the remainder of the card is blank. This card is offset.

•

If a compare error is encountered, the erroneous card and the following card
are offset. These two cards are repunched until no error is detected. An
EOI card with 6/7/8/9 punches in columns 1 and 80 contains a binary count in
column 40 of the number of compare errors.

• During the punching of each file, the system maintains a count of the number
of cards punched for the file. If the number exceeds the limit for which the
user is validated, punching of the file is terminated. A special banner card
with the word LIMIT is punched and offset as the last card of the deck.

The following methods are used by the system to punch each of the three forms of
cards.

CODED CARDS (PUNCH)

With the exception of decks punched via the DISPOSE request, the keypunch mode (026
or 029) of coded cards depends on the job origin type. If the job is of local batch
origin, decks are punched in the initial keypunch mode; that is, the mode specified on
the job card or set by system default. For all other job origin types, decks are punched
in the system default keypunch mode. However, the DISPOSE request allows the user
to specify that decks be punched in either 026 or 029 mode regardless of the job's
keypunch mode.

^-F-'i 60407000 D

BINARY CARDS (PUNCHB)

The card punch driver retrieves 15 words of binary data from central memory. The
driver then generates a checksum for the data and issues a card number. The card
punch controller receives the binary data and punches it on the card unchanged, that is,
in 12 -bit codes. Each row in a card column corresponds to a bit position. The driver
formats the binary card in the following manner.

Column(s) Contents

1 7/9 punch denotes binary card

Rows 0,' 1, 2, and 3 contain the binary equivalent of the
word count of the card

2 Binary data checksunti (modulo 4095)

3 through 77 15 central memory words of binary data

78 Blank

79 and 80 24-bit binary card sequence number

ABSOLUTE BINARY CARDS (P8)

Absolute binary cards are central memory images in 12~bit codes. Each row in a card
column corresponds to a bit position. Sixteen central memory words are punched per
card with no special punches or fields added.

PRINTED DATA

All printed data is in coded format. The line printer driver extracts data until an end-
of-line mark occurs or until 14 central memory words are retrieved. The end-of-line
is denoted by a zero byte, as the last byte of a central memory word. The print line
consists of a maximum of 136 characters. If an end-of-line mark does not appear after
136 characters, the last four characters of that group are lost. The driver converts the
extracted data from display code to internal BCD code (refer to appendix A for the char-
acter set equivalences) and forwards the data to the line printer controller.

The driver interprets the first chsiracter in a line as the carriage control character
(refer to appendix A) and that character is not printed. In most cases, the proper
carriage control is issued while thie remainder of the line is printed. However, when
Q, R, S, or T is specified, no printing takes place for that line. The Q, R, S, and T
format controls remain in effect until changed, and all other carriage control options
must be supplied for each line they control. Line spacing is normally done in the auto
eject mode; that is, creases in the paper are skipped by the line printer controller's
automatic line spacing mechanism if the paper is loaded properly.

During the printing of each file, the system maintains a count of the number of lines printed/
skipped for the file. If the number exceeds the limit for which the user is validated, printing
of the file is terminated. The informative diagnostic LINE LIMIT EXCEEDED is printed.
If a job's dayfile is part of the terminated print file, the dayfile Is subsequently printed.

The Installation can impose an implied page control by setting a certain number of default
lines for each page. If less than the default number of lines is printed/ skipped on a page,
the line limit is still decremented by the default number of lines.

60407000 D l-F-5

TERMINAL CHARACTER CONVERSION

Normal input mode from a terminal consists of a 64-character set where all lowercase
alphabetlcs are converted to uppercase characters. Under ASCII mode, the characters
74 and 76 represent the beginning of a 74xx or 76xx escape sequence. Under NORMAL
mode, the characters 74 and 76 are treated as data rather than escape codes. ASCII
and NORMAL modes apply to both input and output.

DATA INPUT

The terminals KRONOS supports can be grouped into ASCII terminals and correspondence
code terminals. The manner in which the characters entered from a terminal are in-
terpreted by the system depends on whether the user specifies that the characters belong
to the full character set. For example, if the user enters the following characters to
be mapped into the full ASCII set:

aAbBcCdDeEfF

the central memory equivalent ls:t

7.& 0.1

01 76

02 02

76 03

03 76

04 04

76 05

05 76

06 06

00 00

I However, if a NORMAL command is issued, the characters are mapped into the sub*
set of the ASCII character set; then the central memory equivalent is:

01 01

02 02

03 03

04 04

05 05

06 06

00 00

In ASCII mode, 1 1 ^U 128 characters from an ASCII or correspondence code terminal
are recognized. These characters, in addition to the first 64, are processed as 12-bit
characters with an escape code conversion as shown previously. Appendix A lists
the character set equivalences. The programs that process data must recognize that
data is in ASCII mode rather than normal display code and process it accordingly.

DATA OUTPUT

Data output is in either a 64/63 or 128 character set, depending on whether the termi-
nal is in NORMAL or ASCII mode. When the terminal is in NORMAL mode, the codes
74 and 76 represent data rather than escape codes. In ASCII mode, 74 and 76 are
treated as the beginning of an escape sequence. All inforraation is transmitted in even
parity unless the user specifies odd parity.

For a more detailed description of terminal operation, refer to the Time-Sharing User's
Reference Manual.

Data can also be transmitted to or from a terminal through a paper tape reader.
paper tape character mode is always ASCII.

The

t Partial words are zero-filled; partial bytes are blank-filled.
tt Refer to the Time-Sharing User's Reference Manual for descriptions 'of the ASCII
and NORMAL commands.

l-F-6

60407000 D

TAPE LABELS

The operating system accepts ANSI standard and nonstandard labeled tapes. Labels
which do not conform to ANSI standsirds In format and/or content are defined as non-
standard,

ANSI labels perform two functions. They provide information that uniquely identifies
a file and the reel on which it resides, and they mark the beginning and end of a file
and the beginning and end of a reel.

ANSI labels are designed to conform to the American National Standard Magnetic Tape
Labels for Information Interchange X3. 27- 1969. All labels are 80 characters in length
and are recorded at the same density as the data on the tape. The first three char-
acters of an ANSI label identify the label type. The fourth character indicates a number
within a label type.

The following is a summary of each label type, name, function, and whether or not it
is required.

lype

No.

Name

VOL

Volume header label

UVL

1-9

User volume Isibel

HDR

File header label

HDR

2-9

File header label

UHL

Useir header label

EOF

End- of- file label

EOF

2-9

End- of- file label

UTL

■■

User trailer label

EOV

End- of- volume label

EOV

2-9

End- of- volume label

Used At

Beginning-of- volume
Beginning-of-volume
Beginning-of- file
Beginning-of-file
Beginning-of- file
End-of-file
End-of-file
End-of-fUe
End-of- volume

End-of-volume

Required /Optional

Required

Optional

Required

Optional

Required

Optional

Required when

appropriate

Optional

REQUIRED LABELS

The VOLl, HDRl, and EOFl labels are required on all ANSI-labeled tapes. In addition,
an EOVl label is required if the physical end-of-tape reflector is encountered before an
EOFl label is written or if a multifile set is continued on another volume. In the
descriptions of the contents of these labels, n is any numeric digit and a is any letter,
digit, or any of the following special characters.

tAny member of the CDC 6-bit subset of the ASCII character set.

60407000 D

1-G-l

(

[

]

Some fields are optional. An optional field which does not contain the designated infor-
mation must contain blanks. Fields which are not described as optional are required
and will be written as specified. Note that n-type fields are right- justified and zero-
filled, and a -type fields are left- justified and blank- filled.

VOLl - VOLUME HEADER LABEL

The volume header label must be the first label on a labeled tape. All reels begin with
a VOLl label. If two or more reels belong to a volume set, the file section field in
the following HDRl label gives the actual reel number.

VOL

volume serial number

reserved

owner
identification

owner identification (oid)

oid

reserved

Isl

l-G-2

60407000 D

c
o

O .

.2
•a o3

Cm W 0) a, f^

5^50)

w <u m 5 S

:5^^ S i 3

i'^ «M to > C

o "2

" O

«2 V -H

(U K o

o2|

Zffl 8

to <S 1^

^S-^Q

O rn

5 ci:

^..2°

Q) to T5

Vl nj r-l

a> 3 0)

05 oc;

c
o

►J

0.1
XI

C 0)

o ja

•O M
at C
m -rt
u

C O ■-'
O -w at

CO m 03

.a S >>
Soft

T3
3 .fh r< eS

o a) « ««
> nj S o

^T3

ffl3

S w
•- c

X! O

U CO

(U 0)

-" t<

CO 0)

u x:
CO ■"

•fl to

y <u

c
a; O

2 CO

jS.o
S'S
0-"

X! 0)
^£

o ->-•

. CO
to, to
C <U

CO y

:„ o

CO
CO

« CO
XI T3

jS 3

§s

•2t3 S ?i

a; "O <U X) *"
4.» C ;^ O O
O CO bn (-1 -w

<U C X! P^
Q, CO -"

to ,. S CO i

o fi <" <i> .S '
>, cs tS ^ r •

<; S.Sx! af

CO
f— *

X5
•♦J
CO

CO
^^'^^

:;:3 eu XI

s ss

in""

S O

c o

to ?
x: o .-4

" /., cS

csxi"

s -^ CO

<! .w o.

CO
CO

a >

CO .rt

-I X!

2 to

CO cd

u
p

O C

«^ *

rtXl CO

s . s

3 U to

<D ^-> "^

.4- (O (U

•" M X3

■« 2 to

(U
J3

rt -'-'

6 c

rt 0) .

X5 c to

o S <"

t» <U -rt

to Sh ^

UU rt

CO Q,

CO 2 y

g|s

O O X! C o r C

,H C! iS t! C <A ti .rt

>-. CO
h 0) 0)

.^.^

•4->

f-i

H-(

•>^

*'-'

P— 1

<1>

(U h

rrt^

1—4

■^1

■rt

> c

m^^

,j2

(.<

(U B

y -H

t .-a

frt

h en

CO o

1-1

y ^
<5^

U CO

u ti

OT)

o-o

«-< C

«rt c

"5!^

7>«

^ to

gjto

Sh 0)

(h 0) d

V h

(U t. o

CO 3
<1> rt

035

•rt
CO

Res
futu
zati

rt '^

C -rt

(U o

- e
u g

■X3
U

u a

O X)

•4->

.rt

«1H

ISI

t-l

00
CO

•a

(U —t

60407000 D

l-G-3

HDRl - FIRST FILE HEADER LABEL

The first file header label must appear before each file. When a file is continued on
more than one volume, the file header label is repeated after the volume header label
on each new volume for that file. If two or more files are grouped in a multifile set,
each HDRl label indicates the relative position of its associated file within the set.

HDR

1 1 file identifier (fi)

file identifier (fi)

set identification nu*^ee^r®es*^9??io )

secno

fUe
sequence number

generation number

gvn

creation date ^^S'iV^J^^^"

expiration

date

block count

system code

system code I reserved

l-G-4

60407000 D

-a "o

oj aJ

5 V

<Si

^, ft

f, ft

■^ S3

o o
2 «
^- ft

c
cd

1 — 1

ffl

ctf

1—4

o
o
o

o
o

•?w

ilPQ

c «,

o S?

•" J3

-l-a -l-»

0)
XI

•4->

identif
imeter
rol car

Oj TO -y

rH h C

f^ ft u

" m ««

(U a; y

W oj o

rn ^ ^

x;x:<^

T!XI S

•'■> x:

Kl^ O

B
x: -u

3 "M

1°

to
(U <u

.-I [TJ.

to "J

i«

o --<
CO

«o.S

n. m <"
i XI XI

^ «£

O
m

. ?! 3

o o £

o -"

° " oT
.2 Is

^> "U 3

:3 >< o

O J3

en 3 a
., ^ O *:!

§ 9 ft «
5 > CO ^

o m M ™
3 O Sh •

-H JJ; 4) CO
d 50 3 O O

.SS^£3

CO (N

— o

>> .. 3 °

£ -o £ 5 ^

c ^-S

c
o

o -"c

CO <d g

c o r:H

i ™-*" »-^ ,^* X

2 3£

oW"

(U ^ o
to t-l o

tc 0) to 4)

X ,

ct)

^, "i^ CD

o c r3 X

tt-4 ^■M C4H +J

■*

^S1

r-4

(u *;

•1-4

XI ?,

«4^

hJS

c
.2

c
a>

•s

•4->

f— 1

•r^

o
c
v

iiS

<1>

■«->

•F-l

.tJ

T-i

'i'

1
CM
CM

03
CM

60407000 D

l-G-5

^ a)
U w

01
0)

O .3 h
TO rj fr*

9- c to

O tt) 3

.2.2i

■tJ 4-3 Tj

■a

U &

o
o
o

o
o

X! is 01 0)

a >,£^

3 XI ^ rt

s-a o >

C! Q) ti m

* CO cd rt

O etf P. O

O O
C! O
O 0)

•^ to

pi (U

'-' X!

0) ^
W)0

'W o c

•woo

£ <u to

.2 2

to .s g

3 w rt
3+*

^■^
Jd.2 g
U 3 o

0)
J3

•l-<

-*-»

••-*

tJB>

.2c£
;7i to .

y td ft CI

g .59

ca o *s i-I

0) u

■*^

u
o

lisS

cd «

CO CO

cd cd

1-1 T3

° _ o

O TJ «H
^ tt) „

Sh ^ 2

■2.2-2 «

(-1 -rt Cm -*

U Q <U

„ td ii J3

+» <u tj *-" •

5i c «> -S ?,

<S -H <u S w

" .15 ^^ Id O

d fe o 2 ^

^ cj id -S

<" >, ^, ft S

^ ** -I

.- n^ 5 * '-'

cd C
-,, "O td
^ x:

a; >i M

•2 xi ■"
to o iS
fl -"

o n 5i
cJ oj o

to •$ o

3^ 3

.2 fe

CO •-• .g

-.2 S

c ■•-; <u
•^ -o ^
c c a,

> o is

bc to ,

*J ^-» .^

Cd _, <M

^ £.2
•"•^ tJ

X! t> ™

+3 l> to

> «w

•" XI

11.

P s

> c

Xi £
4-» -t-i

o ^

to Vt 3
3 O i.

1 ^'S

— 1 " X3

2 P CO
S Tj to

•H a)

"^ aj ■"

0) 2
> fl) 3

-«-* -4-3 M

cd-g

-a d.a

to a3

0..2

cdri

ftW)^ !>

>< d . ^

^^ 2 to

aj a) H "^

d o 3 a>

o ^H o Cd

" ft > TJ

to
u
<u

■>*

--^

■A ,-^

Gene rat
number
(optiona

!L|

<u d

P> rS

i to

CO
CO

d
.2

d u

0) 3

> d

•o

d
o

•H
ft

■>*

l-G-6

60407000 D

c
o

x:
U

CO •«-*

<u 03 "^

O n>

■g «!-< •

C! O TJ

w « o

« «^

O ci! ■»

O ti C

« s °

a .

..- CO

^§

a .^
.^ ■•-»

^ ••-4
•4->

u m

at (p
o n

cii -M

" CI

• tn

S a>
™ o

.fj Co

§.2

3 .
to

m t— I

.rf i-

tf ^ (U
C3 ^ *■

B: • oj
w S

.a 3 o w o

I Co ti

M O

«> o

S "« ^ *-<
cii S n n>

f' o

- a

=1 >»

'to ti

tn o

r_ B O «> -

O ^ H i O W 5-

O ' ^ • -a

ft '43 3 5^ £

to
o

«>
Si

Mc<?IS^

•r* rt
rt) M

O C!

TO ^^

Oi °

CO ^

'^^^

CO .J -^

x^ CI i-
-^ oi>

M KM

o (u c

o
a

S •

Co *■»

o aj

4) O

$-1 ■!-> X) N -•->

01
(U
O

£1

j:
^

■a
I— I

(D
01
(U

o cd

o
o

r-H
ffl

>>
m

h CD
O TJ

CM fl

^ «

Sh (U c

a> h Q
CO 3 -rj

u
oi
u
a

o CO

<o t-

I I

in 1-t

in CO

60407000 D

l-G-7

EOFl - FIRST END-OF-FILE LABEL

The end-of-file label is the last block of every file. It is the KRONOS end-of- informa-
tion for the file, A single tape mark precedes EOFl, A double tape mark written
after the EOFl label marks the end of a multifile set.

EOF

file identifier (fi)

set identification 1 mirnlipr Tspono)

secno

sequence^number I generation number

gvn

creation date | ^^'8^^i|*'°^

expiration
(iate

1 fa 1 block count

system code

reserved

l-G-8

60407000 D

■a "5

fl> ?,

o X

CO H!

-l->

c
o
u

•l-a

-M

•f-4

1-4

t— 1

•IH

.S w a* 3 ^

>L ^ XI O 3

acters speci
r of data bio
is label and
HDR label g
does not inc

•f-4

a.
en

a>
o.
cd

U V'S &D'-<

■*-»

cd ^ r! Cd

CO C

cd--

|2
cntS

Six n ch
the num
between
precedii
This tot

o
en

■— 1

^_^

flj

*•>

•^

o
in

r— I

•r-l

rj d
hJ3

■—I

ffl) CQ

o -^

3
O

o
o

• H

«w

f— 1

ffi

•f-4

(U d

H .5J4

60407000 D

l-G-9

EOVl - FIRST END- OF- VOLUME LABEL

The end-of-volume label is required only if the physical end-of-tape reflector is en-
countered before an EOFl label is written or if a multifile set is continued on another
volume. EOVl is preceded by a single tape mark and followed by a double tape mark.

EOV

file identifier (fi)

file section
number (secno)

generation number 1 gvn

secno

set identification

file — ;: —

sequence number

expiration
diitg.

gvn

creation date

expiration

■Wa'a'

block count

system code

system code j

reserved

1-G-lO

60407000 D

c
o

'o'H

D ?,

S 0)

Q
OS

Q
oi

c
o

<-i

+»

■^

.»i4

■i-i

• 1-4

.S w

tttS
axH

OS XI

•^ S
og

c c

P4 (1>

X! O S

■a ^ly .
d—i £ to

rt OS to "^

o o.

•i-i rC 'D ci5
C rt fn

a
o
o.

CO
0)

u
u

"(«

X! T-i
CO C

cd -

<"^
S3
CS.2

^.^

«i

•4-*

flj

x:
o

•1-4

o
in

5P^

u
.2

<-\

(U
XI

Same as
correspo
fields in
(optional

o
o

ffl

c »?
0) to o

eii

0.2

CO O tS<>

9) C

•t^ O

U 'S

js.-a

cd o

■*

in
I

(»

60407000 D

1-G-ll

These labels define four possible file configurations,

• A single file on a single volume

• A single file on two or more volumes

• Two or more files on a single volume

• Two or more files on two or more volumes

Figures 1-G-l through l-G-7 illustrate the use of ANSI labels in these configurations.

l-G-12 60407000 D

* = TAPE MARK
-= USER DATA

Figure 1-G-l. ANSI Labels: Single File, Single Volume

Figure l-G-2. ANSI Labels: Single File, Multivolume

60407000 D

l-G-13

HDRI

-^ ^^--FILE A--

FILE B * EOFI

¥e - tape: mark

- = USER DATA

Figure l-G-3 ANSI Labels: Multifile, Single Volume

l-G-14

60407000 D

HDRI

X : TAPE MARK
- = USER DATA

Figure l-G-4. ANSI Labels: Multifile. Multivolume

60407000 D

l-G-15

NOTE:

THE LETTERS (A) AND (B) IN
PARENTHESES INDICATE TO WHICH
FILES THE LABELS ABOVE THEM BELONG.

^= TAPE MARK
- = USER DATA

Figure l-G-5. ANSI Labels: End-of-File. End-of- Volume Coincidence

l-G-16

60407000 D

EOFI

HDRI

EOVI

NOTE:

THE LETTERS (A) AND (B) IN PARENTHESES
INDICATE TO WHICH FILES THE LABELS ABOVE
THEM BELONG.

H - TAPE MARK
- = USER DATA

Figure l-G-6. ANSI Labels: End-of-File, End- of- Volume Coincidence

60407000 D

l-G-17

HDRI

EOFIPE *

■)«• = TAPE MARK
- = USER DATA

Figure l-G-7. ANSI Labels: End-of-File, End- of- Volume Coincidence

l-G-18

60407000 D

OPTIONAL LABELS

Six types of optional labels are allowed. They are additional header (HDR2-9), end-of-
file (EOF2-9), end-of-volume (EOV2-9), user volume (UVLa), header (UHLa), and trailer
(UTLa) labels.

(HDR2-9) - ADDITIONAL FILE HEADER LABELS

HDR2-9 labels may immediately follow HDRl. Their format is:

Default
Written

Character
Position

Field Name

Length
(in characters)

Contents

1-3

Label
identifier

HDR

Label number

2-9

5-80

HDR

2-9

Only the label identifier and the label number are checked on read.

(EOF2-9) - ADDITIONAL END-OF-FILE LABELS

EOF2-9 labels may immediately foUov/^ EOFl. Their format is:

Character
Pos ition

Field Name

Ltmgth
(in characters)

Contents

1-3

Label
identifier

EOF

Label number

2-9

5-80

Default
Written

EOF

2-9

Only the label identifier and the label number are checked on read,

(EOV2-9) - ADDITIONAL END-OF-VOLUME LABELS

EOV2-9 labels may immediately follow EOVl. Their format is:

Character
Position

Field Name

Length
(in chai?acters)

Contents

1-3

Label
identifier

EOV

Label nunaber

2-9

5-80

Default
Written

EOV
2-9

Only the label identifier and the label number are checked on read.

60407000 D

l-G-19

Refer to section 3, volume 2 for a description of the use of EOV2 labels in conjunction
with CLOSER. REWIND, and UNLOAD macros.

USER LABELS

USER labels may immediately follow their associated system labels. Thus, user volume
labels (UVLa) may follow VOLl, user header labels (UHLa) may follow the last HDRn
label, and user trailer labels (UTLa) may follow the last EOVn or EOFn label. Their
format is:

Character
Position

1-3

5-80

Field Name

Label
identifier

Label number

User option

Length
(in characters)

Contents

Default
Written

UVL, UHL. or UTL UVL, UHL,

or UTL

Must be 1, 2, 3, 4,
etc. , consecutively
for UVL labels. For
other labels, any a
character.

Any a characters.

Only the label identifier and the label number are checked on read. The system checks
the number of user labels of a label type; a maximum of 64 is allowed.

l-G-20

60407000 D

INDEX

AB 1-6-6

*A directive l-C-4

A mode 1-8-3

Abnormal termination codes 1-B-l; 2-3-6

Abort CPU 2-6-3

Abort job 1-5-6; 1-10-3; 2-3-11; 2-4-16;
2-11-1

ABORT macro 2-11-1

Abort PPU 2-6-3

ABS record type 1-7-5

Absolute binary cards l-F-3, 4, 5

ACCESS 1-4-4

Access date 1-8-13

Access limits 1-6-2

Access word 1-6-7

Accessibility, tape l-G-3, 7

Accessing files 1-2-8

Accessing direct access files 1-8-6

Access mode 1-8-3, 6, 7; 2-5-2, 16, 19

Accessing permanent file catalog 1-6-20

Accessing tape files 1-10-13

Accessing unlabeled tapes 1-10-11

ACCOUNT card 1-6-2

Account dayfile 1-6-2,3; 2-9-3

Account dayfile message formats 1-3-12;
1-6-2

Accounting information 1-3-7,12; 2-6-13

ACCSF macro 2-4-13; 2-A-l

ACTR symbol 2-2-6; 2-E-l

*AD directive 1-14-14

*ADD directive l-C-4, 8

Address errors 2-3-19

Address out of range 1-3-11; 1-6-8

Address registers 1-13-2

*AFTER directive l-C-4, 6

Aging jobs 1-3-8,10

ALGOL 3 card 1-11-10

ALGOL 4 card 1-11-12

ALTER, OPEN function 2-3-22

Alternate checkpoint dumps 1-10-15

Alternate system 1-1-3; 1-2-8; 1-6-22

Alternate user information 1-8-7

Alternate user number 1-2-7; 1-8-2

ALTERNR, OPEN function 2-3-22

ANSI labels 1-10-1, 14; 1-G~1; 2-3-49;
2-4-16,18

ANSI labels

End-of-file, end-of- volume coinci-
dence l-G-16, 17, 18
Multifile, multi volume l-G-15
Multifile, single volume l-G-14
Single file, multi volume l-G-13
Single file, single volume l-Gr-13

Answerback identifier 1-6-6

APL card 1-11-1

APPEND card 1-8-5

APPEND macro 2-5-13

APPEND mode 1-8-3

Appending information to a file 1-8-5;

2-5-13
Applications programs, converting 2-12-1
ARE 1-4-3
ARET error 2-6-3
ARG= entry point 1-5-3; 2-F-l
ARGR symbol 2-2-6; 2-E-l
Arithmetic error 1-4-3; 2-6-3
Arithmetic operators 1-4-2
ASCII/ display code conversion 1-10-3;

l-A-9, 10; 2-3-11; 2-4-16
ASCII mode 1-4-13; 2-12-5
ASCII statement 1-4-13
ASCII terminals l-F-6
Assembler languages 1-1-4
Assign file to queue device 2-7-4
ASSIGN card 1-7-2; 1-10-11
ASSIGN macro 2-4-3, 13
Assigning a file 1-10-11, 13, 14; 2-4-11, 15
Assigning a pack 1-6-11
Assigning a tape unit 1-6-11; 1-10-11, 13,

14
Assigning equipment 1-7-2; 2-4-10
Assigning nonallocatable devices 1-6-8
Assigning resources 1-6-11
Assignment, file 2-12-2
ATTACH macro 2-5-18
Auto eject mode l-F-5
Auto input byte 2-12-4
Auto recall 2-2-1, 3

CIO 2-3-16

LFM 2-4-1

PFM 2-5-1

SFM 2-9-1

*option 2-3-39,41
Automatic permission 1-8-2
Automatic tape assignments 2-4-18
Auxiliary device requests 1-8-12; 2-5-4
Auxiliary devices 1-2-8; 1-6-6; 1-8-4;

2-3-10
Auxiliary devices, creating files on 1-6-8;

1-8-12
AW 1-6-7

60407000 D

Index- 1

B format 1-10-23: 2-3-12; 2-4-17

*B directive l-C-3,4

Backspacing a file 1-7-3; 2-3-42, 54

Backup system 1-2-8; 1-6-2, 22

BASIC card 1-11-18

BASIC subsystem 1-4-4

Batch job image 1-6-5

Batch jobs, subinitting 1-6-5, 16

Batch origin type 1-3-6, 7

BATCH subsystem 1-4-4

BCD code l-F-2

BCO 1-4-3

BCOT 1-3-6,7

*BEFORE directive l-C-3,4, 7

Beginning of information 1-2-1,2

Binary cards l-F-3, 4, 5

Binary data 1-9-2,4,5

Binary files 2-3-6

Binary formats 2-G-l

Binary input mode 2-12-5

Binary output mode 2-12-5

Binary punch output 1-2-4

Binary random file 2-3-14

Binary record management 1-C-l

Binary records 1-9-4,5; 1-F-l

Binary sequential file 2-3-14

BKSP card 1-7-3

BKSP macro 2-3-42

BKSPRU macro 2-3-43

BLANK card 1-10-12

Blank labeling a tape 1-10-8, 12

Block count l-G-7, 9, 11

Block, defined 1-10-1

Block size 2-3-8, 12; 2-4-18

Blocked data format 1-2-2; 1-10-23; 2-4-17

BOI 1-2-1,2

Boolean operators 1-4-3

Buffer, circular 2-3-16

Buffer empty, defined 2-3-3

Buffer full, defined 2-3-3

Buffer parameters 2-3-2

Buffer size 2-3-3, 15

Buffers, working 2-3-55

*BUILD directive l-C-4, 9

*CALL directive 2-2-9; 2-C-15

CALL statement 1-4-5

Card deck 1-2-2

Card file structure 1-2-2

Card format 1-2-2; l-F-2

Cards, binary l-F-3, 4, 5

Cards, coded l-F-2

Cards, punched l-F-4, 5

Cards, read l-F-2

Carriage control characters 1-A-ll; l-F-5

Carriage return delay 1-6-6

Catalog 1-6-22

CATALOG card 1-7-4

Catalog information 2-5-9

Catalog, user 1-8-2,7

Category, file 1-8-2, 13; 2-3-10; 2-5-3

CATLIST card 1-8-7

CATLIST macro 2-5-9; 2-A-l

CB parameter 1-7-2; 1-10-6; 1-12-3

CC 1-6-7

CCAP 2-5-13

CCAT 2-5-18

CCCCCCC 1-10-15

CCCCCCO 1-12-1

CCCG 2-5-20

CCCT 2-5-9

CCDF 2-5-15

CCDR symbol 2-2-6; 2-E-l

CCGT 2-5-6

CCPG 2-5-7

CCPM 2-5-12

CCRP 2-5-12

CCSV 2-5-5

CEJ/MEJ option 1-1-1; 2-E-2

Central e;xchange jump 2-2-3

Central exchange jump/ monitor exchange

jump 1-1-1; 2-E-2
Central library directory 1-5-6
Central memory, defined 1-1-1
Central memory dumps 1-9-1,2; 1-12-1;

1-13-1; 2-11-12
Central memory field length 1-5-5
Central memory resident, defined 1-1-2
Central memory resident records 1-14-14
Central memory time slice 1-3-10
Central processor abort 1-3-11
Central processor, select 1-6-21
Central processor time 1-3-10; 1-5-5;

1-6-15
Central processor time, maximum 1-6-6,

15
Central processor unit, defined 1-1-1
CHANGE card 1-8-9
CHANGE macro 2-5-20
Character conversion l-F-2, 4
Character count 1-10-3
Character set conversion 1-10-3
Character sets 1-A-l; l-F-6; 2-12-9
CHARGE card 1-3-7; 1-6-2
Charge number 1-6-2, 7
Checkpoint dumps 1-7-2; 1-10-13,14;

1-12-1; 2-3-15; 2-4-10
Checkpoint files 1-10-6; 1-12-1
Checkpoint messages 1-B-l
Checkpoint option 1-14-14
Checkpoint/ restart 1-12-1; 2-10-3
CHECKPT macro 2-10-3; 2-A-l
Checksum l-F-3, 5
Chippewa CPU programi 2-G-7

Index-2

60407000 D

CIO 2-3-16

CIO circular buffer 2-3-16

CIO CLOSE macro 2-3-9

CIO, common decks 2-3-20

CIO detail error return codes 2-3-19

CIO error messages 1-B-l

CIO FET format 2-3-17

CIO function processing 2-3-15

CIO OPEN and CLOSE functions 2-3-9, 22

CIO read functions 2-3-29

CIO write functions 2-3-37

Circular buffers 2-3-2, 16

Circular read operation 2-3-4

Circular write operation 2-3-3

CK parameter 1-7-2; 1-10-6; 1-12-3

CKP card 1-12-1

CKP messages 1-B-l

CLEAR card 1-7-8

CLOCK macro 2-11-1

CLOSE macro 2-3-26

CLOSER macro 2-3-27

Closing a file 2-3-26, 27

CM, defined 1-1-1

*CM directive 1-14-14

CM dumps 1-13-1

CM, maximum 1-6-6

CM parity error 2-6-4

CM time slice 1-3-10

CMR, defined 1-1-2

CMU option 2-E-2

CMUR symbol 2-2-6; 2-E-2

CN 1-6-7

COBOL card 1-11-7

Code, Hollerith l-F-2

Display l-F-2

Internal BCD l-F-2
Coded cards l-F-2, 4
Coded files 2-3-6
Coded format l-F-4
Coded random file 2-3-14
Coded records l-F-1,2
Coded sequential file 2-3-14
Coding specifications 2-C-l
Combined Input/output 2-3-16
COMCARG 2-A-3
COMCCDD 2-A-3
COMCCFD 2-A-3
COMCCIO 2-A-3
COMCCOD 2-A-3
COMCCPM 2-A-3
COMCDXB 2 -A -3
COMCEDT 2-A-3
COMCFCE 2-A-3
COMCLFM 2 -A -3
COMCMAC 2-A-l
COMCMTM 2-A-3
COMCMTP 2-A-3
COMCMVE 2-A-3
COMCOVL 2-A-3

COMCPPM 2-A-3

COMCRDC 2-A-3

COMCRDH 2-A-3

COMCRDO 2-A-3

COMCRDS 2-A-3

COMCRDW 2-A-3

COMCSFM 2-A-3

COMCSFN 2-A-3

COMCSRT 2-A-3

COMCSSN 2-A-3

COMCSST 2~A-4

COMCSTF 2-A-4

COMCSYS 2 -A -4

COMCUPC 2-A-4

COMCWOD 2-A-4

COMCWTC 2-A-4

COMCWTH 2 -A -4

COMCWTO 2-A-4

COMCWTS 2-A-4

COMCWTW 2-x\-4

COMMENT card 1-6-3; 2-C-l

*comment card 1-6-3

^COMMENT directive l-C-4, 9

Comment field 2-C-ll

Comments on control cards 1-5-2; 1-6-3

COMMON card 1-7-8

Common decks 2-1-1; 2-2-8; 2-A-l; 2-C-15

CIO 2-3-20

CPM 2-6-1

Data transfer macros 2-3-59

LFM 2-4-2

PFM 2-5-2

QFM 2-7-1

SFM 2-9-1

System requests 2-11-1

TCS 2-10-1
COMMON macro 2-4-4
Com.munlcatlon area 1-B-l
Compare error l-F-4
Compare/move unit 2-E-2
COMPASS source deck 1-3-2
COMPASS statement 2-H-l
COMHLE file 1-14-1,7
Compiler languages 1-1-4
Completion of a job 1-3-12
Condition codes 1-3-11
Configurations, PPU 1-1-3
Configurations, tape file l-G-12
Conflict on tags 2-2-11
Connect time limits 1-6-2
Console, display a message 2-6-5; 2-11-7
CONSOLE macro 2-6-5; 2-A-l
Constants 1-4-2
Continuation cards 1-10-10
Control bytes 2-12-4
Control card buffer 2-10-2
Control card format 1-5-1
Control card input buffer 1-5-6; 2-10-2
Control card processing 1-3-8; 1-5-1; 1-6-5

60407000 D

Index-3

Control card processing flow 1-5-6, 7;

2-10-1
Control cards 1-5-1

Checkpoint/ restart 1-12-1

File management 1-7-1

Job control 1-6-1

Load/dump central memory utility
1-9-1

Loader control 1-5-1; 1-15-1

Permanet file 1-8-1

Product set 1-11-1

Program library utility 1-14-1

System utility 1-14-10

Tape management 1-10-1
Control language 1-4-1
CONTROL macro 2-10-1
Control point area 1-3-7; 2-6-1
Control point dayfile 1-3-12; 1-6-3; 2-9-3
Control point manager 1-3-9; 2-6-1
Control points, defined 1-1-1
Control statement, execute 2-10-2
Control statement file 2-4-13, 14
Control statement image 2-E-2
Control statement parameters 2-10-1;

2-E-2
Control words 2-3-13, 31, 39
Conversion, character set 1-10-3
Conversion mode 1-5-5,6; 1-10-3; l-F-2,

3: 2-3-11; 2-4-16
Conversion processes l-F-2
CONVERT card 1-7-8
Converting applications programs 2-12-1
COPY card 1-7-9
*COPy directive l-C-4, 10
COPYB listing 2-D-l
COPYBF card 1-7-10
COPYBR card 1-7-10
COPYCF card 1-7-11
COPYCR card 1-7-11
COPYEI card 1-7-12
COPYSBF card 1-7-12
COPYX card 1-7-13
Correction line images 1-9-3
Correspondence code terminals l-F-6
COS format 2-G-7
COS record type 1-7-5
CP 1-6-7
CPE 1-4-3
CPET error 2-6-3
CPM 1-3-9; 2-6-1
CPM, common decks 2-6-1
CPU 2-6-14
CPU abort 2-6-3
CPU common decks 2-2-8; 2-A-l
CPU, defined 1-1-1
CPU error exit 1-3-11; 2-6-2, 3
CPU parity error 2-6-4
CPU priority 1-6-15; 2-6-2,8
CPU program error exit mode 1-6-8

CPU programs 1-1-4

CPU, select 1-6-21

CPU time, 1-6-6, 15; 2-11-13

CPU time limit 1-6-6, 15; 2-6-2

CPUMTR 1-1-2; 2-2-4

Creating

Direct access file 1-6-7; 1-8-10;
2-5-15

File on an auxiliary device 1-6-8

Indirect access file 1-6-7; 1-8-14, 15;
2-5-5

Labeled tape 1-10-13

Library file 1-2-6; 1-C-l; 2-3-1, 22

Random file 2-B-l

Tape files 1-10-1,13

Unlabeled tape 1-10-11
Creation date 1-8-13; 1-10-7; l-G-6;

2-3-14; 2-4-18
Cross reference, system symbols 1-14-12
CS 1-6-6

CSET macro 2-12-9; 2-A-l
CSET statement 1-4-13
CSMR 2-2-6; 2-E-l
CT option 1-8-2
C TIME card 1-5-6; 1-6-3
Current date 2-11-2,9
Current random index 2-3-9
Current tirae 1-6-14
CYBER loader 1-15-1

*D directive 1-14-14; l-C-4

Data channels 1-1-3

Data conversion mode l-F-2

Data format 1-10-5, 18; 2-3-12; 2-4-17

Data Input l-F-6

Data output l-F-6

Data tag conventions 2-C-14

Data transfer macros 2-3-55

*DATE directive l-C-4, 9

DATE macro 2-11-2

Date, packed 2-11-2

DAYFILE card 1-6-3

Dayfile, displaying information 2-11-7

DAYFILE macro 2-9-3; 2-A-l

Dayfile messages 1-B-l; 2-11-7

DB 1-6-6

DDP 1-1-3

Deadlock 1-6-11

DEBUG mode 1-6-8; 1-14-14

Debugging aids 1-13-1

Deck structure 1-3-1

Default family name 1-2-8; 1-14-11

Default system library 1-11-1

Deferred batch jobs 1-6-6; 2-7-3

DEFINE card 1-8-10

DEFINE macro 2-5-15

*DELETE directive 1-14-14; l-C-4, 7

Index-4

60407000 D

Density, tape 1-10-2; 2-3-10; 2-4-lB
Detail error return code 2-3-15, 19
Device, auxiliary 1-2-8
Device not ready error 2-3-19
Device number 1-8-9,13
Device, permanent file 1-2-7
Device reserved error 2-3-19
Device residence 1-2-8
Device statistics 1-E-l
Device status errors 2-3-19
Device type 1-4-9; 1-7-2; 1-8-4,10;

2-3-7,15; 2-4-8; 2-9-4
DF 1-6-7

Diagnostic messages 1-B-l
Direct access file management capability

1-11-1
Direct access files 1-2-5
Accessing 1-8-6
Attaching 2-5-18
Block sizes 1-2-7; 1-E-l
Changing parameters 1-8-9
Creating 1-6-7
Defining 1-8-10; 2-5-15
Interlock 1-8-6
Maximum size in PRUs 1-E-l
PRUs desired 2-3-12
Purging 1-8-13,14
Space 1-8-4; 2-3-12
Directives

Escape character 1-6-16
Modify 1-14-1
OPLEDIT 1-14-4
SYSEDIT 1-14-14
Update 1-14-7
Disable program exit mode 1-6-8
Disconnect terminal 2-12-4
Dismounting packs 1-6-13
Dismounting tapes 1-6-13
Display code l-F-2

Display code conversion 2-3-11; 2-4-16
Display code dumps 1-9-2; 2-11-3
DISPLAY statement 1-4-6
DISPOSE card 1-7-14
Disposition of job output 1-6-16
DISTC macro 2-12-6; 2-A-l
Distributive data path 1-1-3
Division, integer 2-2-7
DMD card 1-9-2
DMD request 2-11-13
DMP card 1-9-1; 1-13-1
DMP= entry point 2-F-l
DMP request 2-11-13
DOCMENT card 1-7-15; 2 -C-1
Documentation cards 2-C-l, 11
DS 1-6-7

DTY parameter 2-3-15

Dumping central naemory 1-9-1,2; 1-13-1
Dumps 1-13-1
Duplicate common file names 2-4-4'

Duplicate lines in dump 1-9-1; 1-13-1

*E card 2-C-lO

E format 1-10-23; 2-3-12; 2-4-17

E mode 1-8-3

EBCDIC /display code conversion 1-10-3;

l-A-9, 10
EC 1-6-7

EC directive 1-6-19
ECS 1-1-3

ECS data storage/ retrieval 1-1-3
ECS files 1-2-2
EDATE macro 2-11-2; 2-A-l
*EDIT directive 1-14-4
Editing an OPL-formatted file 1-14-3
Editing an OPLDPL -formatted file 1-14-7
EESET macro 2-6-6
EF 1-4-3
EIO 1-4-3
EIOT 1-3-6,7
E mode 1-8-3
EM 1-4-3

EM-M 1-6-8; 1-13-2
Empty buffer, defined 2-3-3
ENCSF macro 2-4-14; 2-A-l
End of block byte 2-12-4
End-of-device status 2-3-7,17,18
End of file 1-2-1

B format 1-10-24

E format 1-10-23

F format 1-10-24

I format 1-10-19

S format 1-10-22

SI format 1-10-21

X format 1-10-21
Eind of file label 1-G-l, 8, 19
End of information 1-2-1; 2-3-6

B format 1-10-24

E format 1-10-23

F format 1-10-24

I format 1-10-19

S format 1-10-22

SI format 1-10-21

X format 1-10-22
End of line byte 1-F-l; 2-12-4
End of record 1-2-1

B format 1-10-24

E format 1-10-23

F format 1-10-24

I format 1-10-19

S format 1-10-22

SI format 1-10-21

X format 1-10-21
End of reel, defined 1-10-25; 2-3-11, 27;
2-4-17

B format 1-10-24

E format 1-10-23

60407000 D

Index-5

F format 1-10-24

I format 1-10-20

S format 1-10-22

SI format 1-10-21

X format 1-10-22
End-of-tape, defined 2-3-11; 2-4-17
End of tape processing 1-10-25; 2-4-17
End-of-tape reflector 1-G-l
End of transaction block 2-12-5
End of volume label 1-G-l, 10. 19
ENDRUN macro 2-11-3
Enforce ring 1-10-3,4
ENQUIRE card 1-6-4
EOF 1-2-1,2

EOF card 1-2-2; 1-3-1; l-F-2
EOF directive 1-6-17
EOF 1 label 1-G-l, 8
EOF2-9 labels 1-10-14; 1-G-l, 19
EOI 1-2-1,2

EOI card 1-2-2; 1-3-1; l-F-2
EOR 1-2-1,2

EOR card 1-2-2; 1-3-1; l-F-2
EOR directive 1-6-17
EOVllabel 1-G-l, 10
EOV2 label 1-G-l; 2-3-27
EOV2-9 labels 1-G-l, 19
EPR parameter 2-3-15
Equipment/ file assignment 1-7-2
EREXIT macro 2-6-3
ERRLOG 2-9-3
Error codes 1-B-l
Error codes, LFM 2-4-1
Error conditions 1-3-11; 1-6-8
Error control 1-3-11; 1-6-8; 1-13-2
Error exit address 1-3-11; 2-6-3
Error exit mode 1-6-8; 2-6-2
Error flag 1-3-11; 1-5-8; 1-6-8; 2-11-1
Error inhibit 1-10-4
Error log. dayflle 2-9-3
Error messages 1-B-l
Error processing 1-5-8; 1-6-8; 2-4-16;

2-5-19
Error processing bit 1-B-l; 2-3-7. 15, 18
Excape character 1-6-15,19
ESYF macro 2-9-4; 2-A-l
ETIME macro 2-11-4; 2-A-l
Evaulatlon of control language statements

1-4-3
Event descriptor 2-6-6
EVICT card 1-7-16
EVICT macro 2-3-52
Evicting a file 2-3-52
Exchange jump 2-2-3
Exchange package 1-9-1, 2; 1-13-1
EXCST macro 2-10-2; 2-A-l
EXECUTE mode 1-8-3
EXECUTE subsystem 1-4-4
EXIT card 1-3-11; 1-5-8; 1-6-5; 1-13-2

Exit mode 1-3-11; 2-6-2, 9
Exit processing 1-5-8; 1-6-8
Expiration date l-G-6; 2-3-14; 2-4-18
Export/Import origin type 1-3-6, 7
Expressions 1-4-2
Extended core storage 1-1-3
Extended label processing 2-3-7, 15, 18, 24
External data format 1-2-2; 1-10-21;

2-4-7
External documentation 2-C-l
External reference

ALGOL 3 1-11-10

ALGOL 4 1-11-12

BASIC 1-11-18

COBOL 1-11-7

FORTRAN 1-11-3

SIMSCRIPT 1-11-18

SIMULA 1-11-16
EXU 2-11-13

F format 1-10-24; 2-3-12; 2-4-17

Family 1-2-8; 1-6-2,22; 1-14-11

FAMILY card 1-14-11

Family device 1-8-4

Family name 1-2-7; 1-6-2,22; 1-14-11

FAST attach file 2-5-19

FC 1-6-6

FCLI category 2-5-2

FCPB category 2-5-2

FCPR category 2-5-2

FCSP category 2-5-2

FET 1-B-l; 2-3-1

FET creation macros 2-3-14

FET description 1-2-8; 2-3-4

FET formats 2-3-4

CIO requests 2-3-17

LFM requests 2-4-2

PFM requests 2-5-1

SFM requests 2-9-1
FET, LABEL macro 2-4-15
FET length 2-3-7, 15
FET parameter 2-3-15
FET, position in field length 2-12-1
Field length 1-3-8,9; 1-5-5; 1-6-14;

1-13-2; 2-6-11; 2-11-5
Field length control word 2-6-15
Field length, reducing 2-6-11; 2-11-5
Field length, user defined 1-3-9; 1-6-14
File accessibility 1-2-8; 1-10-7; 2-3-12;

2-4-18
File, assigning 2-4-10
File assignments, terminals 2-12-2
File, block sizes 1-E-l
File category 1-8-2; 2-3-10; 2-5-3, 16
File, checkpoint 1-12-1,2
File, communication area 1-2-8

Index -6

60407000 D

File creation. COMPASS 2-3-1
File, direct access 1-2-5; 1-8-6,, 10;

2-5-15,17
*FILE; directive 1-14-15; l-C-4, 5
File environment table 1-B-l; 2-3-1
File header label 1-G-l, 4, 19
File identifier 1-10-6; l-G-5; 2-3-13;

2-4-18
File information table 1-11-1
File limit error 2-6-4
File, magnetic tape 2-4-18
File management control statements 1-7-1
File mode 2-3-6,10
File name 2-3-15
File name in FET 2-3-6
File name, new 1-8-9; 2-5-2
File name table 1-2-2,3
File password 1-8-2; 2-3-13; 2-5-2
File permission mode 1-8-2, 13; 2-5-2, 12,

16
File positioning 2-3-42; 2-4-8
File, private 1-8-2; 2-5-3
File processors 2-3-1
File, public 1-8-2; 2-5-3
File, purging 1-8-13, 14; 2-5-7
File, replacing 1-8-14; 2-5-12
File, residency 1-8-10; 2-5-4, 15
File returning 2-3-48
File, rewinding 2-3-44
File, saving 1-8-15; 2-5-5
File section number 1-10-7; l-G-2, 5;

2-3-12; 2-4-18
File, semiprivate 2-5-3
File sequence number 1-10-7; l-G-5;

2-3-12; 2-4-18
File, skipping 2-3-52,53
File space, releasing 2-3-48, 52
FILE statement 1-4-8
File status 1-4-8
File status table 1-2-3
File, structure 1-2-1
File types 1-2-3; 1-8-13
FILEB macro 2-3-14
FILEC macro 2-3-14
Files 1-2-1

Files, backspacing 2-3-42,54
Files, binary 2-3-14
Files, coded 2-3-14
Files, FET formats 2-3-4
Files, local 1-2-4; 2-4-1
Files, magnetic tape 1-10-1
Files, maximum number attached 1-5-6
Files on auxiliary devices 2-5-4, 15
Files, random 2-3-14
Files, sequential 2-3-14
FIRST 2-3-3, 5, 7
First file header label l-G-4
First end-of-file label l-G-8
First end -of -volume label 1-G-lO

First word address of memory 1-9-1

FIT 1-11-1

FL 1-4-3

FLE 1-4-3

FLET error 2-6-4

FNT entry 1-2-2, 3; 2-3-15; 2-4-9, 20

FNT pointer 2-3-8

Force unload 1-10-4

Foreign data format 1-2-2; 1-10-24;

2-4-17
Formats for cards read l-F-2
Formats for cards punched l-F-4
Formats for printed data l-F-5
FORTRAN source deck 1-3-4
FORTRAN switches 2-E-2
Frame count 1-10-3
FS 1-6-6
FSET error 2-6-4
FST entry 1-2-3; 2-4-9,20
FTNcard 1-11-3
FTNTS subsystem 1-4-4
Full buffer, defined 2-3-3
FULL duplex transmission mode 1-6-7
Function processors 2-1-1
fwa 1-9-1
FWPR symbol 2-2-6; 2-E-l

Generation number 1-10-7; l-G-6; 2-3-14;

2-4-18
Generation version number l-G-6; 2-3-14;

2-4-18
GET card 1-8-11
GET macro 2-5-6
GETEM macro 2-6-9
GETFLC macro 2-6-15; 2-A-l
GETFNT macro 2-4-20; 2-A-l
GETGLS macro 2-6-18; 2-A-l
GETJA macro 2-6-12; 2-A-l
GETJCR macro 2-6-11; 2-A-l
GETJN macro 2-6-7; 2-A-2
GETJO macro 2-6-13; 2-A-2
GETLC macro 2-6-17; 2-A-2
GETPR macro 2-6-8; 2-A-2
GETQP macro 2-6-8; 2-A-2
GETSS macro 2-6-16; 2-A-2
GETTL macro 2-6-9; 2-A-2
gld l-C-3

Global library set Indicators 2-6-18, 19
GOTO statement 1-4-4
Group record identifier l-C-3
GTR card 1-7-17

HALF duplex transmission mode 1-6-7
Hardware components 1-1-1
Hardware instructions 1-1-4

60407000 D

Index -7

HDRl label l-G-1,4; 2-3-49; 2-4-18
HDR2-9 labels 1-10-14; l-G-19
Header documentation 2-C-ll
Header label, defined l-G-1,4
Hollerith punch code l-F-2, 3
Hollerith punch output 1-2-4

I format 1-2-1; 1-10-19; 2-3-12; 2-4-17

*I directive l-C-4

ID code 2-4-12

Identification code 1-6-8; 2-4-12

IF statement 1-4-7

*IGNORE directive 1-14-14; l-C-4, 7

Illegal instruction 1-3-11

IN 2-3-3,5,8

Increasing the number of scheduled units

1-6-11
Increment registers 1-13-2
IND parameter 2-3-15
Indefinite operand 1-3-11; 1-6-9
Index length 2-3-9, 15
Index random 2-3-9
Index, writing 2-3-26
Indexed sequential files 1-11-1
Indirect access files 1-2-7; 1-8-14, 15;
2-5-5,6

Accessing 1-8-6; 1-12-1

Appending information 1-8-5

Block size 1-2-7; 1-E-l

Changing parameters 1-8-9; 2-5-20

Creating 1-8-14,15; 1-6-6; 2-5-5,12

Maximum number 1-6-6

Maximum size in PR Us 1-6-6; )-E-l

Purging 1-8-13; 2-5-7

Replacing 1-8-14; 2-5-12

Saving 1-8-15; 2-5-5

Working copy 1-8-12; 2-5-6
Infinite operand 1-3-11; 1-6-9
INFT type files 1-2-3
Inhibit error processing 2-4-16
Inhibit unload 1-10-4
Initiate ASCII output 2-12-5
Initiating a job 1-3-6
Input, binary 2-12-5
Input, data l-F-6
INPUT file 1-3-10
INPUT* file 2-3-48
Input file control 1-3-10
INPUT file, terminal 2-12-2
Input file type, releasing 2-3-48
Input file type, returning 2-3-48
Input files 1-2-3
Input/output buffers 2-3-56
Input/output, COMPASS 2-3-1
Input /output queue protection 2-7-1
Input queue 1-3-8, 10
Input queue priority 1-3-8

INPUT, writing on 1-3-10
*INSERT directive l-C-4, 6
Interactive compiler 1-11-1
Interactive interpreter 1-11-1
Interchangeable families 1-2-8
Interlock 1-8-6
Internal BCD code l-F-2
Internal data format 1-2-2; 1-10-19
I/O sequence error 2-4-1
Irrecoverable parity error 2-4-16
IS 1-6-7

JDATE macro 2-11-4
Job abort 1-5-6; 1-10-3
Job accounting information 2-6-13
Job action requests 2-3-1
Job attachment 2-3-48, 52
Job communication area 2-E-l
Job completion 1-3-12
Job control 1-3-8; 1-6-1; 2-10-1
Job control control cards 1-6-1
Job control registers 2-6-11, 12
Job control statements 1-3-1.; 1-5-4
Job deck 1-3-1
JOB directive 1-6-17
Job field length 1-6-14
Job files 1-2-3
Job flow 1-3-1
Job initiation 1-3-6
Job name 1-3-6; 1-5-5; 2-6-7
Job name format 1-3-6, 7
Job origin 2-6-13
Job origin type 1-3-6; 2-8-2
Job output information 1-D-l
Job priority 1-2-3; 1-3-8
Job scheduling 1-2-3; 1-3-8; 1-6-2
Job subsystem 1-4-4
Job termination 1-3-12
Jobs, submitting 1-6-5,16
'JOPR symbol 2-2-6; 2-E-l
Ji^llan date 2-11-4

K display 2-6-5

Keyboard buffer address 2-6-5

Keywords 1-5-3

KRONOS 2. 1 written tape 1-10-1; l-G-7

KRONREF card 1-14-12

L display 2-6-5

L format tapes 1-10-22; 2-3-9, 12; 2-4-7

L format tapes, reading 2-3-35

L format tapes, writing 2-3-37,38,41

Label bit 2-3-10; 2-4-16

Index -8

60407000 D

Label buffer 2-3-12

LABEL card 1-10-13

Label, defined 1-10-1

Label identifier l-G-3, 5. 9, 11, 20

LABEL macro 2-4-15

Label number l-G-3, 5, 9, 11, 20

Label processing 2-3-18,24; 2-4-15

Extended 2-3-7

Standard level 1-10-9; l-G-3; 2-3-7
Label types 1-G-l
Label verification 2-3-25
Labeled tape 1-10-6,12; 2-4-15
Labels 1-G-l
Labels, optional l-G-19
Labels, required 1-G-l
Last transfer address 1-15-8
Last word address of memory 1-9-1
LBC card 1-9-2
LDI card 1-6-5
LDR processor 2-11-14
LDRR symbol 2-2-6; 2-E-l
LDV processor 2-11-14
Legal user 1-6-2.22
LENGTH card 1-6-5
Length of PET 2-3-2, 7
Length of index 2-3-9
Level number 2-3-6, 17
LFM 2-4-1
LFM call format 2-4-1
LFM, common decks 2-4-2
LFM error codes 1-B-l; 2-4-1
LFM FET format 2-4-1
LGO 1-5-1; 1-12-1
LIBEDIT 1-C-l
LIBEDIT directive 1-C-l, 3
LIBEDIT examples 1-C-ll
LIBEDIT messages 1-B-l
LIBEDIT card 1-7-18; 1-C-l
LIBGEN card 1-7-19
^LIBRARY directive 1-14-15
Library files 1-2-6,14; 1-C-l; 2-3-48;

2-4-3,4,13
Library pointer 1-11-1
Library, program 1-14-1
Library routines 1-11-1
Library, system default 1-11-1
Library type file, returning 2-3-48
Library type files 1-2-6, 14; 2-4-13;

2-5-3
Library user 1-11-1
Libraries 1-2-14

System 1-2-14

Program 1-2-14

User 1-2-14

User number LIBRARY 1-2-14
LIFT type files 1-2-6
LIMITS card 1-3-7; 1-6-6; 1-14-3;

2-3-3,5,8
Linefeed, suppress 2-11-4

Line Image data format 1-2-2; 1-10-23;

2-4-17
Line numbers 1-6-16
Line spacing l-F-5
LINK card 1-15-2
LINK loader 1-15-1,2
LINP symbol 2-2-6
List address 2-3-8
LISTLB card 1-10-14
LIST80 card 1-7-20
Literal input l-F-3
Literals 1-5-2
Load map 1-13-3
Load/dump central memory utility control

statements 1-9-1
Loader control word 2-6-10,17
Loader requests 2-11-14
Loaders 1-5-1
Loading binary data 1-9-2,4
Loading octal card images 1-9-3
Loading overlays 2-11-14
Local file control statements 1-5-1
Local file manager 2-4-1
Local file, retrieve permanent file 1-8-12
Local file, saving 1-8-15
Local files 1-2-4

Local files, releasing 2-3-48; 2-4-5
Local type file, returning 2-3-48
Location of data in core dump 1-13-4
LOG card 1-9-3
LOCK card 1-7-21
LOCK macro 2-4-6
Locked common files 2-4-6
LOFT type files 1-2-4
Logical end of file 1-2-1
Logical end of information 1-2-1
Logical end of record 1-2-1
Logical file name 2-3-6
Logical/ physical file structure 1-2-1
Logical record 1-2-1; 1-3-1; 2-3-9, 18
Log-off user 2-12-4
L072 card 1-7-21
LP 1-6-7
Iwa 1-9-1
LWPR symbol 2-2-6; 2-E-l

M. mode 1-8-
Macro usage
Magnetic tape
Magnetic tape
Magnetic tape
Magnetic tape
Magnetic tape
Magnetic tape
Magnetic tape
Magnetic tape
Blocked

■3
2-1-1; 2-2-5

1-10-1; 2-4-10
file, checkpoint 1-12-1,2
file, structure 1-2-2
files, buffer size 2-3-15
files, creating 1-10-1
files, rewinding 2-3-44
files, unloading 2-3-46
formats 1-2-2
1-2-2; 1-10-23

60407000 D

Index-9

External 1-2-2; 1-10-21

Foreign 1-2-2; 1-10-24

Internal 1-2-2; 1-10-19

Line image 1-2-2; 1-10-23

SCOPE internal 1-2-2; 1-10-20

SCOPE long block stranger tape
1-2-2; 1-10-22

SCOPE stranger tape 1-2-2
Magnetic tape labels 1-G-l
Magnetic tape, standard FET 2-3-4
Magnetic tape units, maximum 1-6-6
Magnetic tapes, access restrictions 1-6-12
Magnetic tapes, assigning 1-6-11
Magnetic tapes, scheduling 1-6-11
Magnetic tapes, system management 1-6-11
Main overlay 1-13-5
Managing tapes and packs 1-6-11
Map flags 2-6-10; 2-E-2
Mass storage, assigning a file 2-4-10
Mass storage device file structure 1-2-2
Mass storage device statistics 1-E-l
Mass storage files, buffer size 2-3-15
Mass storage files, size 1-8-4
Mass storage files, rewinding 2-3-44
Mass storage files, unloading 2-3-46
Mass storage, maxim^um 1-6-6
Mass storage resident records 1-14-23
Mass storage, standard FET 2-3-4
Master device 1-2-8; 1-6-3
Maximum logical record size 2-3-9, 18
Maximum number of control points 1-1-1
Maximum time 1-3-10
Memiory boundaries 1-13-1
MEMORY macro 1-3-9; 2-11-5
Memiory map 1-15-2

Memory, releasing 1-3-8; 1-6-13; 2-11-5
Memory requirenaents

ALGOL 3 1-11-10

ALGOL 4 1-11-12

BASIC 1-11-18

COBOL 1-11-7

COMPASS 1-11-2

FORTRAN 1-11-3

PERT66 1-11-16

SIMSCRIPT 1-11-18

SIMULA 1-11-16

SORTMRG 1-11-15

TRSUN 1-11-19
MERGE file 1-14-7
Message, LFM 2-4-1
MESSAGE macro 2-11-7
Messages 1-B-l
MFL= entry point 1-3-8; 2-E-l
Minimum buffer size 2-3-15
MNE 1-4-3

MODE card 1-3-8; 1-6-8
Mode me 2-3-10
MODE macro 2-6-2
Modif Ic a tlon dat e 1-8-13

Modification decks 1-14-3
Modification identifiers 1-14-4
MODIFY card 1-14-1
Modify directive 1-14-1
Modify library file format 2-G-2
MODIFY mode 1-8-3
MODIFY OPL 1-14-12
Modify-formatted programi library file

1-14-1,3
Modifying the system library 1-14-13
MODVAL card 1-6-8
MOVE macro 2-11-9
MS 1-6-7

*MS directive 1-14-14
MT 1-6-6

MTR functions 2-11-12
Multifile reels l-G-12
Multifile sets 1-G-l; 2-3-49
Multifile tape, positioning 2-3-49
Multireel files l-G-12
Multiunit device 2-3-13; 2-5-4

N mode 1-8-3

NA option 1-8-4

Name change 2-4-2

Name conventions 2-C-13

*NAME directive l-C-4, 5

Name, file 2-3-10

ND option 1-8-5

Nested calls to procedure files 1-4-11

NEW card 1-7-25

New file name 1-8-9; 2-3-14; 2-5-2

New password 1-6-11

New permanent file name 1-8-9

NEWPL file 1-14-7

NF 1-6-6

No abort option 1-8-5

No drop option 1-8-5

NOEXIT card 1-3-11; 1-5-8; 1-6-9; 1-13-2

Noise size 1-10-1, 6; 2-3-12; 2-4-18

Nonallocatable device 1-6-8

Nonallocatable devices, assigning 1-6-8

Nonstandard label bit 2-3-10; 2-4-16

Nonstandard labels 1-G-l; 2-4-16

Nonstop read 2-3-35

Nonstop write 2-3-41

NOPACK directive 1-6-17

*NOREP directive l~C-4, 9

NORERUN card 1-6-9

NORERUN macro 2-7-3; 2-A-2

NORMAL mode 1-4-12

NOSEQ directive 1-6-17

NOTRANS directive 1-6-18

NPL file 1-14-3

NR functions 2-3-22, 26, 27

NULL 1-4-4

NULL mode 1-8-3

NUM statement 1-4-10

Index- 10

60407000 D

Octal card image format 1-9-3

Octal card Images, loading 1-9-3

ODET error 2-6-4

OF 1-6-7

OFA 1-10-7

OFFSW macro 2-6-7

OLD card 1-8-11

Old file accessibility . 1-10-7, 12

Old password 1-6-11

Old permanent file name 1-8-9

OLDPL file 1-14-7,9

ONEXIT card 1-5-8; 1-6-10; 1-13-2

ONSWcard 1-6-10

ONSW macro 2-6-7

Open for read 2-3-24

Open for write 2-3-24

OPEN macro 2-3-22

Opening a file 2-3-22

Operand out of range 1-3-11; 1-6-9

Operand registers 1-13-2

Operating registers, restoring 2-12-8

Operating system format 1-5-1,2,3

Operator assignment of equipment 2--4-10

Operator assignment of tapes 2-4-18

Operator drop 2-6-4

Operator/user communication 2-6-5

Operators 1-4-2,3

OPL common decks 2-2-9

OPL fae 1-14-1,3.9,11

OPL format 2-G-2

OPL record type 1-7-5

OPLC format 2-G-5

OPLC record type 1-7-5

OPL D format 2-G-6

OPLD record type 1-7-5

OPLEDIT card 1-14-3

Optional tape labels 1-6-19

Optional user number 2-3-12; 2-5-2

Order -dependent format 1-5-3

Order-independent format 1-5-3

Origin type 1-3-6; 2-8-2

Origin type, batch 1-3-6,7

Origin type, remote batch 1-3-6,7

Origin type, system 1-3-6

Origin type, time-sharing 1-3-6,7

OT 1-4-4

OUT card 1-7-25; 2-3-3, 5, 8

Output, automatic 2-12-2

Output, binary 2-12-5

Output, data l-F-6

Output file 1-2-4

OUTPUT file 1-2-4; 1-12-1

Output file terminal 2-12-2

Output information 1-D-l

Output problems, terminals 2-12-2

Overcommitnaent of resources 1-6-11

OVERLAY macro 2-11-16

Overlays, loading 2-11-14

OVL record type 1-7-5

OWN parameter 2-3-15
OWNCODE address 2-3-15
Owner identification l-G-3
Owner of a KRONOS 2. 1 written tape

1-10-1,9
Owner of auxiliary device 1-2-8
026 mode 1-5-6; l-F-3; 2-3-26; 2-4-6
029 mode 1-5-6; l-G-3; 2-3-26; 2-4-6

PA 1-6-6

PACK card 1-7-26

PACK directive 1-6-17

Pack name 1-2-8; 1-8-4.12; 2-3-13;

2-5-2,4; 2-6-15
Packed date 2-11-2,9
Packed time 2-11-4.9
PACKNAM card 1-8-12
PACKNAM macro 2-6-15. 16
Packs, access restrictions 1-6-12
Packs, assigning 1-6-11
Packs, private 1-6-12
Packs, public 1-6-12
Packs, scheduling 1-6-11
Packs, sharable 1-6-12
Packs, system management 1-6-11
Paper tape reader l-F-6
Parameter field 1-5-2
Parameters, control statement 1-5-3;

2-E-2
Parameters, number of characters 1-5-3
Parity errors 2-3-19; 2-6-4
PARITY macro 2-12-9; 2-A-2
PARITY statement 1-4-12
Parity, terminal 2-12-9
PASSWOR card 1-6-11
Password 1-6-2,22
Password, changing 1-6-7, 11
Password, file 2-3-13; 2-5-2, 4
PBC card 1-9-4
PCET error 2-6-3
PDATE macro 2-11-9
Peripheral hardware 1-1-3
Peripheral processor library director

1-5-6
Peripheral processor units 1-1-3
Permanent file catalog 1-6-19
Permanent file catalog area 1-6-2
Permanent file control statements 1-8-1
Permanent file devices 1-2-8; 1-6-2; 1-8-4;

1-14-11; 1-E-l; 2-5-4
Permanent file information 1-8-7
Permanent file manager 2-5-1
Permanent file name 1-8-6; 2-3-10; 2-5-2
Permanent file name, changing 1-8-9;

2-5-20
Permanent file, returning 2-3-48

60407000 D

Index- 11

Permanent files 1-2-5, 7
Private 1-8-2
Public 1-8-2
Semiprivate 1-8-2
Permanent file size 1-E-l
Permanent file system 1-8-1; 2-5-1
Permanent file request to auxiliary device

1-8-12
Permanent file, used as local file 1-8-12
Permanent files, direct access 1-2-8;

1-8-6; 2-5-15
Permanent files, indirect access 1-2-8
Permanent files, purging 1-8-10,13,14;

2-5-7
Permanent type files, releasing 2-4-5
Permission, file 1-8-2, 13; 2-5-12
Permission information 1-8-7; 2-5-10
PERMIT card 1-8-16
PERMIT macro 2-5-12
PERT66 card 1-11-16
PFM 2-5-1
PFM call format 2-5-1
PFM, common decks 2-5-2
PFM communication words 2-3-16
PFM error codes 1-B-l
PFM error messages 1-B-l
PFM FET format 2-5-1
PFM, registers used 2-5-2
PGNR symbol 2-2-6; 2-E-l
PHFT type files 1-2-4
Physical file structure 1-2-1
Physical record unit, magnetic tape

1-2-2; 1-10-1
Physical record unit, mass storage 1-2-2.
Physical record units, defined 1-2-1; 2-3-8
PMFT type files 1-2-5
PN 1-6-7

Positioning a file 2-3-42
Positioning a labeled tape 2-3-49
Positioning the control statement file

2-4-14
POSMF macro 2-3-49
PP call error 2-6-3
PP format 2-G-2
PP record type 1-7-5
PPE 1-4-4
PPET error 2-6-3
*PPSYN directive 1-14-14
PPU 1-1-3
PPU abort 2-6-3
PPU absolute records 2-G-2
PPU record type 1-7-5
Prefix character 1-5-1
PR FT type files 1-2-4
PRIMARY card 1-7-27
PRIMARY macro 2-4-21; 2-A-2
Primary terminal files 1-2-6
Primary terminal type file, releasing
2-4-6

Primary terminal type file, returning

2-3-48
Print file priority 1-2-4
Print files 1-2-4
Print type files, releasing 2-4-6
Print type files, returning 2-3-48
Printed data l-F-5
Printer queue 1-2-4
Priority, CPU 1-6-5, 13; 2-6-2, 8
Priority, job 1-2-3
Priority level 1-5-5
Priority, maximum 1-6-5
Priority, queue 1-3-8; 2-6-1, 8
Private file 1-8-2, 13; 2-5-3
Private packs 1-2-8; 1-6-12
Privileged commands 1-6-6
^'PROC directive 1-14-14
Procedure files l-4-l> 10
Processing options 1-10-3; 2-3-11; 2-4-16
Processing tape requests 2-3-22; 2-4-10,15
Product set control statements 1-5-1;

1-11-1
Product set format 1-5-1, 2, 3
Program address 1-13-2
Program address register 1-9-1
Program call statements 1-11-2
Program control of terminal activity

2-12-4
Program error exit mode 1-6-8; 1-13-2
Program example 2-D-l
Program library 1-2-14
Program library utility control statements

1-14-1
Program name field 1-5-2
Program stop 2-6-4

Program /system communication 2-2-1
Program termination 2-11-3
Program text documentation 2-C-ll
Project number 1-6-2, 7
Project number entry 1-14-10
PRU 1-2-1

Magnetic tape 1--2-2; 1-10-1
Mass storage 1-2-2
Punched statements 1-2-2
PRU, reading 2-3-29

PRU size 1-2-1; 1-E-l; 2-3-8, 12, 18; 2-4-18
PSCSF macro 2-4-14; 2-A-2
PSE 1-4-4
PSET error 2-6-4
Pseudo- sense switches 1-6-10,21
P TAP mode 2-5-2
PTEXmode 2-5-2
PTFT type files 1-2-6
PTMD mode 2-5-2
PTNU mode 2-5-2
PTRA mode 2-5-2
PTRD mode 2-5-2
PTRMmode 2-5-2
PTWR mode 2-5-2

Index-12

60407000 D

Public file 1-8-2; 2-5-3

Public packs 1-2-8; 1-6-12

♦PULALL directive 1-14-5

*PULLMOD directive 1-14-5; 1-6-12

PUNCH 1-2-4

Punch code l-F-4

Punch file structure 1-2-2

Punch file types, releasing 2-4-6

Punch files 1-2-4

Punch type file, returning 2-3-48

PUNCHB 1-2-4; 1-9-4; 1-12-1; 1-F-!)

PUNCH9 2-4-6

Punched card format l-F-4, 5

PURGALL card 1-8-13

PURGE card 1-8-14

PURGE macro 2-5-7

*PURGE directive 1-14-4

Purging files 1-8-13, 14; 2-5-7

Px 1-6-6

PW option 1-8-2

P8 1-2-4; 1-12-1; l-F-5

QDL 2-3-1; 2-8-1

QFM 2-3-1; 2-7-1

QUAL pseudo instruction 2-2-13

QUAL$ tag 2-2-13

Qualifying common decks 2-2-13

Queue device assignment 2-7-4

Queue dump/load processor 2-3-1; 2-8-1

Queue file manager 2-7-1

Queue files 1-2-3; 1-7-13; 2-4-12

Queue, input 1-3-10

Queue priority 1-3-8,10:2-6-1,8

Queue protection 2-7-1

Queue, rollout 1-3-10; 2-6-5

Queue, type files 2-8-2

Queues, releasing files 1-7-13; 2-8-3

R option 1-8-4
RA 1-1-2; 2-E-l
RA mode 1-8-3
RA+1 requests 2-2-1,3
Random access 1-2-8; 2-3-20
Random access bit 2-3-7
Random address 2-3-20
Random file, sample 2-B-l,6
Random index 2-3-9, 15
Random I/O, examples 2-B-l
Random processing 2-3-18,20
Random request 2-3-9, 15
Random rewrite request 2-3-9
RBR card 1-9-4
RDVT macro 2-9-4; 2-A-2
*REAd directive 1-14-5

READ directive 1-16-18

READ ftinction 2-3-22

Read functions 2-3-29

READ macro 2-3-29

READ mode 1-8-3

Read nonstop 2-3-31

READ, OPEN function 2-3-22

Read/write 2-3-10; 2-4-16

Read/write interlock 2-5-18

READAPmode 1-8-3

READC macro 2-3-59

RE ADC W macro 2-3-31

READEI macro 2-3-36

READH macro 2-3-60

Reading ANSI labels 2-4-15

Reading binary records 1-9-4

Reading CM dumps 1-13-3

Reading files 1-2-10

Reading labels 2-4-16

Reading statements l-F-2

READLS macro 2-3-33

READ mode 1-8-3

READMD mode 1-8-3

READN macro 2-3-35

READNR, OPEN function 2-3-22

READNS macro 2-3-35

READO macro 2-3-61

READS macro 2-3-62

READSKP macro 2-3-30

READW macro 2-3-63

Real-time clock 1-6-14; 2-11-10

Recall 2-2-1,3

RECALL macro 2-11-10

Record 1-2-1

Record logical 1-3-1

Record management 1-C-l

Record manager 1-11-1

Record prefix 1-9-4

Record type 1-7-5

Records, skipping 2-3-52, 53

REEL function 2-3-22

REELNR function 2-3-22

Reference address 1-1-2; 1-13-2

Reference record identifier l-C-3

Reflector, end-of-tape 1-G-l

Reformatting directive 1-6-16

Registers, job control 2-6-11, 12

Registers, restoring 2-12-8

REL type record 1-7-5

Relational operators 1-4-2

RELEASE macro 2-4-5

Releasing a local fUe 2-4-6; 2-7-1

Releasing file space 2-4-6

Releasing files to output queues 2-4-7

Releasing job attachment 2-3-48,49

Releasing memory 1-3-8; 1-6-14

Releasing output files 1-3-12

Remote batch origin type 1-3-6, 7

60407000 D

Index-13

Removable auxiliary devices, maximuxn,

file residency 1-6-6; 1-8-4
Remove file 1-8-13, 14
RENAME card 1-7-27
RENAME macro 2-4-2
^RENAME directive 1-14-15; l-C-4, 10
Renaming a file 2-4-2
REPLACE card 1-8-14
^REPLACE directive l-C-4, 10
REPLACE macro 2-5-12
Replacing files 1-8-14; 2-5-12
REQUEST card 1-7-28; 1-10-14
REQUEST macros 2-4-10, 11
Request processor 2-3-1
Request/ return codes 2-3-6
Requests, system 2-2-1; 2-11-12
Required tape labels 1-G-l
RERUN card 1-6-11
RERUN macro 2-7-2; 2-A-2
Rerun status 1-6-9, 11; 2-7-2
Rescheduling a job 1-6-12
RESEQ card 1-7-30
Reservation blocks 1-E-l
Reserved name conventions 2-C-13
Residency, file 1-2-8; 1-8-10; 2-5-15
RESOURC statement 1-6-11; 2-5-16
Resource types 1-6-11
Resource utilization 1-6-2,11
RESTART card 1-12-2
Restarting a job 1-12-1, 2; 2-10-3
Restoration field length 1-6-14
Retention cycle 1-10-8
Retention date 1-10-7
RETURN card 1-6-12; 1-7-31
Return codes 2-3-6
RETURN function 2-3-26
RETURN macro 2-3-48
RETURN vs E\aCT macros 2-3-52
RETURN vs UNLOAD macros 2-3-46
Returning a pack 1-6-12; 2-3-48
Returning a tape file 1-6-12; 2-3-48
REWIND card 1-7-32
REWIND directive 1-6-19
*REWIND directive 1 -C -4, 5
REWIND function 2-3-26
REWIND macro 2-3-44
REWIND vs UNLOAD macros 2-3-46
Rewinding a file 2-3-27,44
Rewrite In place 1-2-12
REWRITE macro 2-3-39
REWRITEF macro 2-3-39
REWRITE R macro 2-3-39
RFILEB macro 2-3-14
RFILEC macro 2-3-14
RFL card 1-3-9; 1-6-14
RFL= entry point 1-3-8; 2-F-l
rid l-C-3
R mode 1-8-3
RM mode 1-8-3

RO 1-6-6

ROFT files 1-2-3

Rolling out a job 1-3-10; 1-6-14

ROLLOUT card 1-6-14

Rollout control 1-3-10

Rollout files 1-2-3; 1-3-10

ROLLOUT macro 2-6-5; 2-A-2

Rollout queue 1-3-10; 1-6-14; 2-6-5

Rollout time period 1-3-10; 2-6-6

Routine name conventions 2-C-13

RP 1-6-6

RPHR macro 2-3-29

RPHRLS macro 2-3-34

RTIME macro 2-11-10

RTIME statement 1-5-6; 1-6-14

Rubout characters 1-6-6

Running field length 1-3-9

S format 1-10-22; 2-3-9. 12; 2-4-17

S format tapes, reading 2-3-36

S format tapes, writing 2-3-38,41,46

S option 1-8-4

Sample job 1-D-l

SAVE card 1-8-15

SAVE macro 2-5-5

Saving a file 1-8-15; 2-5-5

*SC directive 1-5-1; 1-14-15

Scheduling jobs 1-2-3; 1-3-8

Scheduling packs 1-6-11

Scheduling resources 1-6-11

Scheduling tape imits 1-6-11

Scheduling units 1-6-11

SCOPE internal data format 1-2-2

1-10-20; 2-4-17
SCOPE long block stranger format 1-2-2;

1-10-22
SCOPE stranger tape data format 1-2-2;

1-10-22: 2-4-17
Scratch files 1-2-4
Scratch tape files 1-10-15
SDM= entry point l--;j-3; 2-F-l
Section number l-G-5
Semlprivate files 1-8-2; 2-5-3
Sense switch 1-6-10,21; 2-6-7; 2-E-2
Separators 1-5-2
SEQ directive 1-6-17
Sequence error 2-4-1
Sequence number l-G-5
Sequential access 1-2-8
Set binary input mode 2-12-5
Set identification l-G-5
Set identifier 1-10-7; 2-3-14; 2-4-18
SET statement 1-4-6
Set transparent mode byte 2-12-5
SETCORE card 1-6-14
SETGLS macro 2-6-19
SETID card 1-7-32

Index- 14

60407000 D

SETID macro 2-4-12

SETJCR macro 2-6-12; 2-A-2

SETLC macro 2-6-10; 2-A-2

SETLC macro 2-6-10; 2-Ar.2

SETPR card 1-6-15

SETPR macro 2-6-2; 2-A-2

SETQP macro 2-6-1; 2-A-2

SETRFL macro 1-3-9; 2-6-11

SETSS macro 2-6-12; 2-A-2

SETTL card 1-3-10; 1-6-15

SETTL macro 1-3-10; 2-6-2

SETUI macro 2-6-9; 2-A-2

SFM 2-9-1

SFM call format 2-9-1

SFM common decks 2-9-1

SFM FET format 2-9-1

Sharable packs 1-6-12

SI format 1-10-20; 2-3-12; 2-4-17

SIMSCRIPT card 1-11-18

SIMULA card 1-11-16

SKIPB macro 2-3-54

SKIPEI card 1-7-33

SKIPEI macro 2-3-54

SKIPF card 1-7-33

SKIFF macro 2-3-52

SKIPFB card 1-7-33

SKIPFB macro 2-3-52

SKIPFF macro 2-3-53

SKIPR card 1-7-34

SL 1-6-7

SORT card 1-7-34

SORTMRG card 1-11-15

SOURCE file 1-14-1,8

Space for direct access file 1-8-4; 2-3-12

Special control cards 1-5-6

Special files 1-2-4

SRU 1-3-7; 2-11-11

SS 1-4-4

SSJ= entry point 2-F-l

STAGE card 1-7-36

Standard label processing 2-3-7, 18, 24

Standai-d labels 1-G-l

Statement label field 1-5-1

Status information 1-B-l; 2-3-6

Status information, CIO 2-3-17

STATUS macro 2-4-8

Status of terminal 2-12-10

STIME card 1-5-6; 1-6-15

STIME macro 2-11-11

Structure of files 1-2-1

SUBMIT card 1-3-6, 7; 1-6-17

SUBMIT macro 2-7-3; 2-A-2

Submitting jobs 1-3-6; 1-6-5, 16; 2-7-3

SUBR macro 2-11-12; 2-A-2

Subroutine tag conventions 2-C-13

Subsystem 1-4-4

Subsystem control 2-6-12,16

Subsystem type 2-12-11

SUI card 1-6-20

SUMMARY card 1-6-20

SWITCH card 1-6-21

SYET error 2-6-4

SYFT type files 1-2-6

Symbolic names 1-4-3

Symbols, system communications 2-2-5

SYO 1-4-4

SYOT 1-3-6

SYSCOM macro 2-2-5

SYSEDIT card 1-14-13

SYSLIB 2-2-8

System abort 2-6-4

System code l-G-7

System communication symbols 2-2-6

System control cards 1-5-1

System dayfile 1-6-3; 2-9-3

System default library 1-11-1

System description 1-1-1

System file manager 2-9-1

System files 1-2-6; 2-9-4

System interface rules 2-C-15

System job name 1-3-6

System library 1-2-14; 1-14-13

SYSTEM macro 1-13-2; 2-11-2

System macros 2-3-7; 2-C-16

System monitor 1-1-2

System origin type 1-3-6

System origin privileges 1-6-8

System priorities 1-3-8

System request processing 2-2-1

System requests 2-11-1

System resource units 1-3-7; 2-11-1

System sequence number 1-3-6,7

System software 1-1-4

System symbols 1-14-12

System type file, returning 2-3-48

System/user interface 2-E-2

System utility control statements 1-14-10

SYSTEXT file 1-14-12; 2-2-5

*T card 2-C-lO
Tags, conflict of 2-2-11
Tape, CIO buffer size 2-3-15
Tape density 2-3-10; 2-4-16
Tape file 2-3-22; 2-4-10, 15
Tape file assignment 2-4-15, 18
Tape file configurations 1-G~12
Tape file structure 1-2-2
Tape files

Evicting 2-3-52

Returning 2-3-48

Rewinding 2-3-44

Unloading 2-3-46
Tape files, accessing 2-4-10,15
Tape files, block size 2-4-17
Tape files, creating 2-4-10, 15
Tape formats 1-2-2; 1-10-18

60407000 D

Index- 15

Tape label processing 2-3-24
Tape labels 1-G-l
Tape management 1-10-1
Tape mark 1-10-1; l-G-8, 10
Tape requests 2-3-22; 2-4-10,15
Tape units

Assigning 1-6-11

Dismounting 1-6-13

Scheduling 1-6-11

System management 1-6-11
TAPEn 1-9-4,5

Tapes, access restrictions 1-6-12; 2-4-15
TC 1-6-7
TCS 2-3-1; 2-10-1
TDUMPS card 1-7-37
TEFT fUe 1-2-3
Terminal buffer sizes 2-3-15
Terminal character conversion l-F-6
Terminal control 2-12-4
Terminal data input l-F-6
Terminal output problems 2-12-2
Terminal parity 1-6-6; 2-12-9
Terminal, print position 2-12-4
Terminal status 2-12-10
Terminal suspended 2-12-6
Terminal type 1-6-7; 2-12-11
Termination 1-3-12; 2-11-3
Terminators 1-5-2
Text format 2-G-4
TEXT record type 1-7-5
Time, accumulated CPU 2-11-13
Time limit 1-3-10; 1-6-6, 15; 2-6-2, 9
Time limit error 1-5-8; 2-6-3
TIME macro 2-11-13
Time of day 1-6-14; 1-8-13; 2-11-1,4
Time -sharing commands 1-4-13
Time -sharing origin type 1-3-6, 7
Time -sharing terminal, buffer sizes

2-3-15
Timed/ event rollout file 1-2-3
TKE 1-4-4
TKET 2-6-4
TLE 1-4-4
TLET error 2-6-3
TLX macro 2-12-2; 2-A-2
Track limit error 2-3-19; 2-6-4
Track mode 2-4-16
Tracks bit 2-3-10; 2-4-16
Trailer label sequence 2-3-27
TRANACT 1-4-4
TRANS directive 1-6-17
Transaction functions 1-6-8
Translate control statements 1-5-6; 2-10-1
Translation of control cards 2-9-1
Transmission mode 1-6-7
Transparent mode 1-6-16; 2-12-5
TSRUN card 1-11-19
TSTATUS macro 2-12-10; 2-A-2
TT 1-6-7

TTY character conversion l-F-6

TXO 1-4-4

TXOT 1-3-6,7

*TYPE directive l-C-4,5

UHLa labels 1-G-l, 20

ULIB record type 1-7-5; 2-G-8

UN option 1-8-2

Unit count 2-3-12; 2-5-15

Unlabeled tape 1-10-6, 11; 2-4-10, 15, 16

Unload, force 1-10-4

Unload, Inhibit 1-10-4

UNLOAD card 1-7-38

UNLOAD macro 2-3-46

UNLOCK card 1-7-38

UNLOCK macro 2-4-7

Unused bit count 2-3-9, 18

Up bit 2-3-7,15,18

UPDATE card 1-14-7

Update -formaitted program library file

1-14-7
Update to modify conversion 1-14-10
UPMOD card 1-14-10
UPR parameter 2-3-15
USASII conversion 2--3-11; 2-4-16
USECPU card 1-6 '-21
USECPU macro 2-6-14
User catalog 1-8-2,7
User control word 2-3-13
User dayfile 2-9-3
User header Label 1-G-l, 20
User index 1-3-7; 1-6-20; 2-6-9
User label buffer 2-3-24
User labels l-G-20
User libraries 1-2-14; 2-G-9
User number 1-2-7; 1-3-7; 1-6-2,22;

2-6-14
User number, alternate 1-8-2
User number library 1-2-14
User number, optional 2-3-12; 2-5-2, 4
User /operator com.munlcation 2-6-5
User permission 1-8-3, 6, 13; 2-5-2
User processing 2-3-18
User processing bit 2-3-7, 15, 18
User programs 1-1-4
User/ system interface 2-E-2
User trailer label 1-G-l, 20
User validation 1-6-2,22
User volume label 1-G-l, 20
USERNUM macro 2-6-14
User's control point dayfile 1-6-3
UTLa labels 1-G-l, 20
UVLa labels 1-G-l, 20

Index-16

60407000 D

VAL= entry point 2-F-2

Validation 1-3-7

Validation information 1-6-6,7,8

VALIDUS 1-14-11

VERIFY card 1-7-39

VERSION macro 2-6-17

VFYLIB 1-7-40

Volume accessibility 1-10-8

Volume, defined 1-10-1

Volume header label l-G-1,2

Volume aerial number 1-10-1, 6, 13;

2-3-12; 2-4-18
VOLl l-G-1,2, 3; 2-4-18
VSN 1-10-1,6,13; l-G-3; 2-3-12; 2-4-18
VSN card 1-10-15

WRITEF card 1-7-40

WRITEF macro 2-3-38

WRITER macro 2-3-60

WRITEN macro 2-3-41

WRITENR, OPEN function 2-3-22

WRITEO macro 2-3-61

WRITER card 1-7-40

WRITER macro 2-3-38

WRITES macro 2-3-62

WRITEW macro 2-3-63

Writing ANSI labels 2-4-15

Writing files 1-2-11

Writing interactive programs 2-12-1

Writing labels 2-4-16

WSA parameter 2-3-15

Wmode 1-8-3

WBR card 1-9-5

Working buffers 2-3-56

Working copy of a file 1-8-11, 13; 2-5-6

Working files 1-2-4.6

Working storage 2-3-8, 15

WPHR macro 2-3-37

WRIF$ symbol 2-3-39

Write functions, CIO 2-3-37

Write lockout bit 2-4-6

WRITE macro 2-3-37

WRITE mode 1-8-3

Write, nonstop 2-3-39,41

WRITE, OPEN functions 2-3-22

WRITEC macro 2-3-60

WRITECW macro 2-3-39

X format 1-10-21; 2-3-12; 2-4-17

XJ instruction 2-2-3

XJPR symbol 2-2-4, 6; 2-E-l

XJR system request 2-12-8

xl bit 2-3-7,18,49

XTEXT common deck call 2-2-11

Zero byte l-F-5

6681 function reject error 2-3-19
6/7/8/9 statement 1-2-2; l-F-2
6/7/9 statement 1-2-2; l-F-2
7/8/9 statement 1-2-2; l-F-2
80-column binary punch output 1-2-4

60407000 D

Index- 17

COMMENT SHEET

MANUAL TiTiF CDC KRONOS 2.1 Reference Manual, Volume 1

60407000 D
PUBUCATION Na REVISION

FROM: name:.

business
address:

COMMENTS:

This form is not intended to be used as an order blank. Your evaluation of this manual will be welcomed
by Control Data Corporation. Any errors, suggested additions or deletions, or general comments may
bemade below. Please include page number references and fill in publication revision level as shown by
the last entry on the Record of Revision page at the front of the manual. Customer engineers are urged
to use the TAR.

U|l

zl
3\

(91
Z

3
<\

NO POSTAGE STAMP NECESSARY IF MAILED IN U. S. A.

FOLD ON DOTTED UINES AND STAPLE

STAPLE

FOlO

FOLD

FIRST CLASS
PERMIT NO. 8241

MINNEAPOLIS. MINN.

BUSINESS REPLY MAIL

NO POSTAGE STAMP NECESSARY IF MAILED IN U.S.A.

POSTAGE WILL BE PAID BY

CONTROL DATA CORPORATION

Publications and Graphics Division

ARH219

4201 North Lexington Avanuo

Saint Paul, Minnesota 55112

z
o

FOlO

FOLD

CORPORATE HEADQUARTERS, P.O. BOX 0, MiNNEAPOLIS, MINNESOTA 55440 , ,Tho in U S a

SALES OFFICES AND SERVICE CENTERS IN MAJOR CITIES THROUGHOUT THE WORLD

CONTRpL DATA CORPORATION