Digital PDFs

DEC-XV-IRSMA-A

September 1976

148 pages

Original

4.8MB

Document:	Master Index
Order Number:	DEC-XV-IRSMA-A
Revision:
Pages:	148
Original Filename:	http://bitsavers.org/pdf/dec/pdp15/XVM/DEC-XV-IRSMA-A_XVM-RSXsysMan/DEC-XV-IRSMA-A_pt07_On-line_Task_Development.pdf

OCR Text

PART VII
XVM/RSX ON-LINE TASK DEVELOPMENT

CHAPTER 1
INTRODUCTION TO MULTIACCESS

1.1

FUNCTION OF TASK DEVELOPMENT

RSX has the capability of multiuser on-line task development with
concurrent batch processing.
Multiuser task development (TDV) is
known as the MULTIACCESS facility.
RSX offers a full range of TDV
functions under control of the MULTIACCESS Monitor.
By calling
different TDV system modules (function tasks) supplied with RSX,
the
user can enter or change source code, compile a FORTRAN IV program or
assemble a MACRO program, and bu~ld this program as a task that will
execute under RSX control.
(In addition, the user can invoke utility
routines to perform a variety of file listing and maintenance
functions.)
The TDV function tasks supplied as part of RSX are listed
in Table 1-1.
Besides the TDV function tasks, the MULTIACCESS Monitor supports a set
of commands that control the user TDV environment. The MULTIACCESS
Monitor commands are listed in Table 1-2.
Furthermore,
three
control-character facilities have been provided to help the user
control
his
particular
task
development.
The
MULTIACCESS
control-character facilities are listed in Table 1-3.
JOB, BAT and END (not listed in Table 1-1)
are classified as TDV
functions,
but because they have meaning only when batch processing,
they are separtely described in Part VIII of this manual.
Another TDV function task (not listed in Table 1-1), PUP (Peripheral
Utility Program), resembles PIP (Peripheral Interchange program),
which is used on other systems.
PUP enables the user to transfer
files from one device to another. Although it is not supplied with
RSX, the user can obtain it from the DEC User Society (DECUS).
The MULTIACCESS facility can be used from any number of terminals up
to
the
maximum
number
supported
by
the particular system
configuration.
However, for most installations,
the number
of
terminals used simultaneously for task development should be limited
to six. This is suggested because of the large size of several
critical TDV function tasks.

XVM/RSX VIB

VlI-l-l

September 1976

Table 1-1
TDV Function Tasks
TDV Function Task

•
•

Function Performed

FOR [TRAN]

Compile a FORTRAN IV program

MAC [RO]

Assemble a MACRO program

EDI [TOR]

Text-edit source code

SLI [P]

Edit batch files

TKB [UILDER]

Build a task for execution

BTK

Basic Task Builder

FIN [PUT]

Transfer a sequential file to disk

DEC [K]

Batch transfer to disk

FOU [TPUT]

Transfer a sequential file from disk

LIS[T]

Transfer a sequential file
to printing device

from

disk

TYP [E]

Transfer a sequential file
to printing device

from

disk

DEL [ETE]

Delete file from disk

REN[AME]

Rename file stored on disk

DIR[ECTORY LIST]

List files in file directory on disk

DTD [IRECTORY]

List DEC tape file directory

NEW [DIRECTORY]

Write out a new DECtape file directory

INS [TALL] *

Install a task in the system

REQ[UEST]*

Request task execution

REM [OVE]*

Remove a task from the system

MNT*

Logically mount a disk

DSM*

Logically dismount a disk

CON [STRUCT]

Store a task on a user disk

STA[TUS]

Print MULTIACCESS Monitor statictics

QUE[UE]

Queue a batch job

ODT

Octal Debugging Technique

ACI

Initialize batch account file

ACD

Display batch account file

I *Not recommended for use under MULTIACCESS
XVM/RSX VlB

VII-1-2

September 1976

Table 1-2
MULTIACCESS Monitor Commands
Command

Function Performed

OFF

Log the user off
system

DEV [ICES]

Print
the
relationship

PAR[TITION]

Specify the user's memory requirements

KPAR[TITION]

Specify the userls memory requirements

ASG (ASSIGN)

Assign the user's LUNs
devices

XQT

Execute a user task

the

user's

MULTIACCESS
LUN-to-device

peripheral

Table 1-3
MULTIACCESS Control-Character Facilities
Control Character

Function Performed

CTRL/T

Begin the login process, if
is not logged in.

the

user

Inform the user of his current
status, if the user is logged in.

job

CTRL/Y

Abort the user's current task
(TDV
function or user-written task), if one
is active.

CTRL/P

Resume a user task if it has been
suspended by a FORTRAN PAUSE statement
or MACRO SUSPEND directive.

XVM/RSX V1B

VII-1-2.1

September 1976

All TDV function tasks are invoked through the MULTIACCESS Monitor, an
exec-mode task that is built for any user-specified partition within
the first 32K of core. TDV function tasks, such as the FORTRAN IV
Compiler, reside on the disk until requested by the Resident TDV
Dispatcher. These tasks typically share a core partition, although
they can be built to run in any partition.
To facilitate concurrent operations, it is necessary to assign virtual
user LUNs in such a way that devices need not be reassigned when the
user switches from one TDV function to another.
Table 1-4 contains
recommended virtual LUN assignments for TDV use.
Device names
correspond to devices listed in Table 1-5. Function names are given
in Table 1-1.
NOTE
Thoughout this part of the manual and
wherever user LUNs are referred to, it
must be understood that
these
are
virtual
LUNS.
virtual
LUNS
are
automatically "mapped" to system LUNs by
the MULTIACCESS Monitor.
The MULTIACCESS Monitor accepts requests for specific functions as
input from a dynamically allocated system LUN. The resident task then
requests that a specific TDV function task be brought into its core
partition from disk.
This function task assumes control and can
perform the jobs described in subsequent chapters.
TDV function tasks accept command input from LUN-12, in much the same
way as the Resident MCR accepts requests for MCR functions from LUN-2.
TDV error messages are sent to LUN-13 just as MCR error messages are
sent to LUN-3. The MULTIACCESS user should leave virtual LUNs 12 and
13 assigned to TT (the default assignment) •
Actual time of execution of TDV function tasks, like user tasks,
depends on partition availability and task priority. More detailed
descriptions of this process appear below and in Part XI of this
manual.

XVM/RSX VIB

VII-1-3

September 1976

Table 1-4
TOV Virtual LUN Assignments
1

LUN
Recornr.lended
Device
Assignr.tents

I-'

DIR
dsk
drvr

RF,

RP or

RF,
RP or

TKB
user
libr

RF,

RP or

TKB
sys
lihr

RF,

LUN
Use

<:
H

19
DT

TDV
cmd
in

TDV
err
log

FOR
cmd
in

FOR
err
msgs

FOR
SRC
in

FOR
list

FOR
BIN
out

MAC
cmd
in

MAC
err
msgs

MAC
SRC
in

MAC
list

MAC
BIN
out

MAC
sec
in

MAC
aux
in

EDI
cmd
in

EDI
err
msgs

EDI
aux
out

EDI
SRC
I/O

EDI
temp
file

EDI
aux
in

TKB
cmd
in

TKB
term
out

TKB
BIN
in

TKB
TSK
out

FIN
cmd
in

FIN
err
msgs

FIN
file
out

FIN
file
in

FOU
cmd
in

FOU
err
msgs

FOU
file
in

FOU
file
out

LIS
cmd
in

LIS
err
msgs

DEL
cmd
in

DEL
err
msgs

DEL
file
I/O

REN
cmd
in

REN
err
msgs

REN

OIR
cmd
in

OIR
err
msgs

LIS
list

EDI
term
I/O

LIS
file
in

file
I/O
OIR
list

(Continued)

Table 1-4 (Cont.)
TDV Virtual LUN Assignments
LUN

DTD
cmd
in

err,

NEW
cmd
in
INS
TSK
in

INS
cmd
in
REO
cmd
in
REM
cmd
in

c:::

MNT
cmd
in

H
I
I-'
I
111

DSM
cmd
in
XQT
cmd
in
CON
TSK
in

CON
cmd
in
DF.C
cmd
in

DTD

DTD
tape
in

list

NEW

NEW
tape
out

err

msgs

INS

err
msgs

REO

err

msgs

REM

err
msgs

MNT

err
msgs

DSM

err

msgs

XOT

err

msgs

CON

err

msgs

DEC

DrC

nEe

msgs

I out

err

file

Table 1-5
I/O Devices
Device Name

Device

TTn

Terminal

DTn

DEC tape

MTn

Magtape

Fixed-Head Disk

RPn

Disk Pack

RKn

Disk Cartridge

Paper Tape Reader

Paper Tape Punch

Card Reader

Card Punch

Line Printer

Analog-to-Digital Converter

Automatic Flying Capacitor Scanner

Universal Digital Controller

System COMMON Communicator

VTn

Display

VWn

writing Tablet

XY Plotter

Card Reader (CRll)

XVM/RSX VIB

VII-1-6

September 1976

1.2

REQUESTING THE RESIDENT TDV DISPATCHER

Task development can be requested from any idle terminal by typing
CTRL/T.
This usually causes the LOGIN Processor to be invoked.
CTRL/T is ignored, however, if the terminal
is ATTACHed or
if
the
Resident TDV Dispatcher cannot execute for any reason (e.g., if it has
not been INSTALLed, if it is DISABLEd or if its partition is in use) .
If the user is already logged into MULTIACCESS, CTRL/T causes the
stgtus of the current function to be printed. The format of this
status message is:
TASKNME PARTITION ATL STATUS ABBREVIATION
where TASKNAME is the name of the user program or system function,
PARTITION is the name of the partition in which the task is running
and ATL STATUS ABBREVIATION is one of the following:
ATL Status Abbreviation
CREATING TASK

Meaning
Task is not yet active

WAITING FOR PARTITION
ON DISK

ATL status 1 or 2

WAITING AT (address)

ATL status 3 (restart address is printed
after the abbreviation)

EXECUTING

ATL status 4,5,7 or 10

SUSPENDED

ATL status 6
FORTRAN)

(equivalent

PAUSE

ABORTING
SYSTEM ERRORTASK NOT IN ATL
If no user-specified task is running
(i.e.,
if the Resident TDV
Dispatcher is waiting for the user to enter a command), the following
message is printed:
TDV AWAITING COMMAND
TDV>
If the user is not logged into MULTIACCESS,
the LOGIN Processor
determines whether there are sufficient resources available to log the
user into the system.
If resources are not available,
the LOGIN
Processdr prints the message:
MULTIACCESS - TOO MANY JOBS
on the terminal and ignores any user-typed commands until CTRL/T is
typed again.
If resources are available, the LOGIN Processor logs in
the user and prints the message:
XVM/RSX VIBOOO MULTIACCESS
MONTH/DAY/YEAR

XVM/RSX V1B

HOUR: MINUTE

VII-1-7

September 1976

NN USERS LOGGED IN
SPECIFY DISK TYPE (RK, RP OR RF), UNlT AND UFO>
The user must then
following format:

respond

typing

the

requested

data

the

disk,

the

(e.g., RK5 <XYZ»
The default disk type is the same as that of the system
default unit number is 0 and the default UFO is <SCR>.

If the user does not complete the response with a line terminator
within 60 seconds,
the LOGIN Processor returns the terminal to the
idle state.
If the UFO specified does not exist for
the disk
specified, the LOGIN Processor creates it.
In this event, the LOGIN
Processor informs the user by printing the message:
UFO CREATED:

<UFO>

During the login process, user errors cause the following messages
be printed:

Cause

Error Message
NONEXISTANT UNIT NUMBER
RETYPE>

The
unit
exist.

number

specified

does not

SYNTAX ERROR
RETYPE>

The command
error.

line

contains

a syntax

UFO CREATION ERROR

A new UFO was specified and disk errors
prevented its creation. This is a fatal
error.

SYSTEM ERRORMISSING PDVL NODE

This is a fatal error.

Fatal errors cause an automatic logoff to occur.
Once the user has successfully logged
responds by printing the prompter:

into

MULTIACCESS,

the

system

TDV>
In response to this
command.

1.3

prompter,

the

user

can

enter

any

legal

TDV

invoking

the

TDV/SYSTEM COMMUNICATION

Consider the following command line as
FORTRAN IV compiler:

example

TDV>FOR BPROGI
In RSX, both the command to run the Compiler and the
Compiler itself are typed on the same line.

XVM/RSX VIB

VII-1-8

command

the

September 1976

When the Compiler is loaded into core and begins to run, it issues a
system directive called XFRCMD, which causes the line read by the
Resident TDV Dispatcher to be transferred to the Compiler. This is a
command used by all TDV function tasks regardless of whether or not
they request any command input. until XFRCMD is issued, the Resident
TDV Dispatcher command line buffer is occupied.
Once the command line is transferred and the requested task has
completed
its
operation, the Resident TDV Dispatcher task is
automatically requested by the TDV function task (the FORTRAN Compiler
in this example). Alternatively, the user can abort the current user
task and invoke the Resident TDV Dispatcher by typing CTRL/Y.

1.4

TDV COMMAND CONVENTIONS

Requests for individual TDV function tasks are
the following conventions:

entered

according

Command strings are terminated by either a carriage return or
an altmode.
These terminators are treated identically by
MULTIACCESS.

Each element of the command string must be separated
either a comma, a space or a back arrow, as appropriate.

Any number of characters (except a comma or space)
can be
inserted between a TDV function task name and its arguments
or command-string terminator (carriage return or altmode).
This facility is useful for
improving the readability of
teleprinter copy. For example, the following two commands
illustrate the abbreviated and the more readable way of
calling the Editor:

TDV>EDI
or
TDV>EDITOR
4.

1.5

If the user discovers an error in the command string before
the terminator has been typed, the line can be deleted as far
back as the prompting character
(»
by typing a single
CTRL/U.
An "at~ symbol
(@) is echoed, informing the user
that he can now retype the command string. Rubout, echoed as
a backslash (\), can be used to delete characters one by one,
starting with the last character typed.

TDV FUNCTION TASKS

Each of the following chapters describes one TDV function task.
In
all models and examples included in these chapters, the following
conventions apply:

XVM/RSX VIB

VII-1-9

September 1976

A space in the text indicates an actual space in the
line.

+indicates an actual backward arrow in the command line.

V indicates a terminator.

This

can

either

command

carriage

return or an altmode.

Square brackets ([, .•• ]) indicate optional characters.

Optional items that can be repeated are indicated by dots
following the item in square brackets. If a comma precedes
tbese dots ([ •.• ]), only the last parameter can be repeated.
Repetitions must be separated by commas. Therefore, in:
FIN[9]

[option]name [ext]

[, •.. ]

at least one name with an optional extension must be
specified.
Additional file names, each with an optional
extension, can be included, as in:
TDV>FIN Fl,F2,F3
TDV>FIN Fl SRC,F2 BIN
TDV>FIN FI,F2 SRC
6.

In ~form" models, upper-case characters (except LUN) indicate
those required by the system. Lower-case characters indicate
entries that are to be specified by the user and are
dependent on his particular task.

All LUNs requested are virtual LUNs.

Braces ({l) enclosing a stack of items indicate that one item
in the stack must be selected.

Five TDV functions described in the following
recommended for use under MULTACCESS. They are:

chapters

are

not

INSTALL
REQUEST
REMOVE
MOUNT
DISMOUNT
They can be included
procedures), but only
ba tch streams.

XVM/RSX VIB

in
to

the system (via atypical system-build
maintain compatibility with existing user

VII-I-IO

September 1976

CHAPTER 2
FORTRAN:

COMPILING A FORTRAN PROGRAM

The FORTRAN TDV Function Task invokes the FORTRAN IV Compiler.
This
Compiler is a two-pass system program that produces relocatable object
code. The Task Builder (TKB) then links this code with required
Object-Time
System
(OTS)
library routines and optionally with
additional
user-specified
FORTRAN-compiled
or
MACRO-assembled
routines.
Systems with a Floating-Point Processor (FPP) have a special version
of
the
FORTRAN
IV Compiler and OTS which utilizes hardware
instructions rather than software calls.
For example, RELEAE, the
REAL arithmetic p~ckage, is not included in FPP systems since REAL
arithmetic expreSS10ns are evaluated with the aid of
hardware
instructions. The FPP FORTRAN System consists of the standard FORTRAN
IV Compiler and Object-Time System interfaced (via
conditional
assembly and additional routines) to the hardware FPP (Floating-Point
Processor). The interface applies to single and double precision
floating-point arithmetic and extended integer arithmetic (double
integers). Single integer arithmetic is still handled, in part, by
software.
Installations with a Floating-Point Compiler should delete
FOR ••• and rename F4F ••• as FOR ••••
The FORTRAN Compiler can also be invoked in batch mode.

2.1

INVOKING THE FORTRAN IV COMPILER

The user can invoke the FORTRAN IV
according to the following formata

Compiler

VII-2-1

typing

command

Form:

FOR[TRAN) [ option[,) ••• )+name[,name ••• ]V

Where:

option is a one-character symbol specifying a
compilation option (see Table 2-1), option
characters may be either concatenated or
separated by commas
name of program to be compiled is a string of
one to six .SIXBT characters, at least one
name is required, but several programs may
be compiled in sequence to produce separate
binary files

Example:

Compile program named PROG, creating a binary
file (B) and a listing (L) :
TDV>FOR BL+PROG

Table 2-1 illustrates all compiler options available under RSX.
number of these may be concatenated in a TDV command string.

Any

Table 2-1
FORTRAN IV Compiler Options
Option

Action

Default

Binary output

No binary file

Use subroutine .S5
to generate addresses
of two- and threedimensional array
elements

Use in-line code to
generate array element
addresses (except for
I/O parameter list
elements)

Source listing

No listing

Object listing

No listing

Symbol map

No symbol map

Print Compiler version number and END
PASS1 on output
terminal

No printout

VII-2-2

2.2

INPUT/OUTPUT

The following LUN assignments should be made
Compiler is invoked under MULTIACCESS:
LUN

before

the

FORTRAN

Assignment

Error messages (terminal recommended)

Source file input

Listing output

Binary file output

If an I/O error occurs during compilation, the message:
FOR-I/O ERROR LUN xx yyyyyy
is produced on LUN-13. In this message, xx represents the logical
unit number
(decimal) and yyyyyy represents the event variable value
(octal), indicating the cause of the error.

2.3

COMPARISON WITH OTHER VERSIONS OF FORTRAN

The FORTRAN IV language employed under XVM/RSX is basically the same
as that used under the XVM/DOS system.
It differs, however, from the
versions of the Compiler used in support of previous versions of RSX.
All user FORTRAN programs developed under previous versions of RSX
must be recompiled and rebuilt by the Task Builder to enable them to
run under XVM/RSX.
The basic l~nguage and operating conventions of XVM/RSX FORTRAN are
described 1n the FORTRAN IV XVM Language Manual and FORTRAN IV XVM
Operating Environment Manual. Nevertheless, RSX user interaction with
FORTRAN IV differs in some ways from the descriptions in those
manuals. The main differences occur in support of the auxiliary disk,
input/output, the STOP and PAUSE statements, the floating-point
processor, OTS output and table initialization. These differences are
described in more detail below. Differences in methods for opening,
closing, deleting and renaming files are described in Part VI of this
manual.

2.3.1

Auxiliary Disk

FORTRAN IV under RSX supports all standard FORTRAN features, except
and auxiliary disk I/O functions (e.g., REWIND,
BACKSPACt, etc.).
certain~magtape

XVM/RSX VIB

VII-2-3

September 1976

2.3.2

Input/Output

The Input Command Decoder of the Compiler has been modified to use
standard task development function input and to compile multiple files
with the same switches. For example:
FOR BLFILEI,FILE2
causes the FORTRAN IV Compiler to compile programs FILEI and FILE2
sequence and to produce separate binary files and listings.

More specifically, RSX random-access I/O to the disk differs slightly
from the description in the manuals listed above. The description of
disk I/O in Part VI of this manual gives details on random-access I/O.

2.3.3

STOP and PAUSE Statements

FORTRAN IV STOP and PAUSE statements call library routines that have
been slightly modified for RSX use. A STOP message prints on the
terminal only if nonzero arguments are present; otherwise, the task
simply exits.
PAUSE produces a new message that includes the task
name. To continue after a PAUSE, the user can type a CTRL/P or the
operator can use the RESUME MCR Function Task.

2.3.4

Floating-Point Processor

Under RSX, the JEA register for the floating-point processor (FPP)
is
initialized by the SETJEA system directive.
If the system has not
been configured for FPP hardware, an unrecoverable .OTS 52 error is
output.

2.3.5

OTS Output

Output from the FORTRAN object-time system, such as .OTS errors and
STOP and PAUSE messages, goes to LUN-4, typically assigned to the user
TDV terminal, except when the system is batch processing.
When
FORTRAN jobs are run under MCR, LUN-4 is typically assigned to the MCR
terminal.

2.3.6

Table Initialization

Under RSX, the I/O Table Initialization Routine (.FP) has been removed
from FlOPS and now exists as a separate routine. This implementation
prevents unnecessary loading of FlOPS when no I/O capability is
required.

XVM/RSX VIB

VII-2-4

September 1976

2.4

ERROR MESSAGES

Tables 2-2, 2-3, and 2-4 list possible error messages and their
implications.
All messages in Table 2-2 are printed in the following
form:
Form:

>mA<

Where:

m is the error number
A is the alphabetic mnemonic characterizing the
error class
Table 2-2
FORTRAN Error Messages

Number

Letter

Meaning
Common, equivalence, data errors:

No open parenthesis after variable
in DIMENSION statement

No slash after COMMON block name

COMMON Block name previously defined

Variable appears twice in COMMON

EQUIVALENCE list
open parenthesis

Only one variable in EQUIVALENCE class

EQUIVALENCE distorts COMMON

EQUIVALENCE extends COMMON down

Inconsistent equivalencing

EQUIVALENCE extends COMMON down

Illegal delimiter in EQUIVALENCE list

Non-COMMON variables in BLOCK DATA

Illegal repeat factor in DATA statement

DATA statement stores in COMMON
non-BLOCK
DATA
statement
or
non-COMMON in BLOCK DATA statement

does

not

begin

name

with

in
in

(Continued on next page)

VII-2-5

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning
00 errors:

Statement with
unparenthesized = sign
and conuna not a DO statement

variable not followed by = sign

variable not integer

Initial value of
followed by conuna

Improper delimiter in DO statement

Illegal
loop

terminating

variable

statement

for

not

External symbol and entry-point
errors:

Variable in EXTERNAL
statement
not
simple non-COMMON variable or simple
dununy variable

ENTRY name non-unique

ENTRY statement in main program

No = sign following argument
arithmetic statement function

No argument list in FUNCTION subprogram

Subroutine list
in
CALL
already defined as variable

Function
or
array
name
used
expression without open parenthesis

list

statement

Format errors:

Bad delimiter after FORMAT numqer in I/O
statement

Missing field width, illegal
or unwanted repeat factor

character

(Continued on next page)

VII-2-6

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning

Field width is 0

Period expected, not found

Period found, not expected

Decimal

length

missing

(no

Rd"

Integer

"Fw.d")

Missing left parenthesis

Minus without number

No P after negative number

No number before P

No number or 0 before H

No number or 0 before X

Too many left parentheses
Hollerith errors:

More than two characters in
Logical Hollerith constant

Number preceding H not between 1 and 5

Carriage return inside Hollerith field

Number preceding H not an integer

More than five characters inside quotes

Carriage return inside quotes
Various illegal errors:

Unidentifiable statement

Misspelled statement

Statement out of order

Executable
subroutine

statement

BLOCK

DATA

(Continued on next page)

VII-2-7

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Illegal character in
following unit number

Illegal delimiter in ASSIGN statement

Illegal type in IMPLICIT statement

Logical IF as target of logical IF

RETURN statement in main program

Semicolon in COMMON statement outside of
BLOCK DATA

Illegal delimiter in IMPLICIT statement

Misspelled REAL or READ statement

Misspelled END or ENDFlLE statement

Misspelled ENDFlLE statement

Statement function
undimensioned array

Typed FUNCTION statement out of order

Illegal character in context

Illegal logical or relational operator

Illegal letter in IMPLICIT statement

Illegal
letter
statement

Illegal delimiter in letter
IMPLICIT statement

Illegal character in context

Illegal comma in GOTO statement

Illegal variable used in multiple RETURN
statement

Meaning

out

I/O

statement,

range

order

IMPLICIT

section

(Continued on next page)

VII-2-8

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning
Pushdown list errors:

DO nesting too deep

Illegal DO nesting

Subscript/function nesting too deep
Incomplete DO loop-caused by backwards
DO loop, error in DO loop foot statement, or error in I/O statement with
implied DO loop
Overflow errors:

EQUIVALENCE class list full

Program size exceeds 8K

Local array length larger than 8K

Element position in local array larger
than 8K or in common array larger than
32K (EQUIVALENCE, DATA)

Integer negative or larger than 131071

Exponent of floating point number larger
than 76

Overflow
accumulating
many digits

constant - too

Overflow
accumulating
many digits

constant - too

Overflow
accumulating
many digits

constant - too

Statement number errors:
01

Multiply defined
compiler error

Statement erroneously labeled

Undefined statement number

statement

number

(Continued on next page)

VII-2-9

Table 2-2 (Cont.)
FORTRAN Error Messages
Nwnber

Letter

Meaning
statement

without

FORMAT
number

statement

statement number expected, not found

Statement number more than five digits

Illegal statement number

Invalid statement label or continuation
Partword errors:

Expected colon, found none

Expected close bracket, found none

Last bit number larger than 35

First bit number larger
number

First and last bit
integer constants

than

numbers

last

bit

not

simple

Subscripting errors:
01

Illegal
subscript
delimiter
specification statements

More than three subscripts specified

Illegal delimiter in subroutine argument
list

Non-integer subscript

Non-scalar subscript

Integer scalar expected, not found

Two operators in a row

Close parenthesis following an operator

Adjustable dimension not in dummy array
(Continued on next page)

VII-2-10

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning

Adjustable dimension not a dummy integer

Two arguments in a row

Digit or
letter
argument conversion

Number of subscripts stated not equal to
number declared

encountered

after

Table overflow errors:

Arithmetic statement,
computed
GOTO
list, or DATA statement list too large

Too many dummy variables
statement function

Symbol and constant tables overlap

arithmetic

Variable errors:

Two modes specified
name

Variable expected, not found

Constant expected, not found

Array defined twice

Error: variable is EXTERNAL or argument
(EQUIVALENCE, DATA)

More than one dimension
scalar variable

indicated

for

First character after READ or WRITE
open parenthesis in I/O statement

not

Illegal constant in DATA statement

Variables outnumber
statement

constants

DATA

Constants outnumber
statement

variables

DATA

for

same

variable

(Continued on next page)

VII-2-11

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning

Illegal dummy variable (previously
as non-dummy variable)

Logical
operator
has
non-logical arguments

Illegal mixed mode expression

Logical
operator
has
non-logical arguments

Signed variable left of = sign

Illegal combination for exponentiation

.NOT.
operator
has
non-logical argument

Function in specification statement

Two exponents in one constant

Illegal redefinition of a
function

No number after E or D in a constant

Non-integer
record
random-access I/O

Illegal delimiter in I/O statement

Illegal syntax in READ,
or DECODE statement

END or ERR
statement

Constant and variable modes don't
in DATA statement

match

ENCODE or DECODE not
parenthesis

followed

open

Illegal
delimiter
statement

used

non-integer,

scalar

number

WRITE,

ENCODE,

exists out of order

I/O

ENCODE/DECODE

(Continued on next page)

VII-2-12

Table 2-2 (Cont.)
FORTRAN Error Messages
Number

Letter

Meaning

Array expected as first
ENCODE/DECODE statement

argument

Illegal
delimiter
statement

ENCODE/DECODE

Expression errors:

Carriage return expected, not found

Binary WRITE statement with no I/O list

Illegal element in I/O list

Illegal
statement
number
computed or assigned GOTO

Illegal delimiter in computed GOTO

Illegal computed GOTO statement

Illegal delimiter in DATA statement

No close parenthesis in IF statement

Illegal delimiter
statement

arithmetic

Illegal delimiter
statement

arithmetic

Expression on left
arithmetic statement

sign

Unequal number of right and left parentheses

Illegal
open
parenthesis
specification statements)

Illegal open parenthesis

Unequal number of right and left parentheses

Illegal alphabetic in numeric constant

Symbol contains more than six characters

list

(in

(Continued on next page)

VII-2-l3

Table 2-2 (Cont.)
FORTRAN Error Messages
Number
22

Letter

Meaning
.TRUE., .FALSE., or .NOT.

preceded

an argument
23

Unparenthesized
expression

Unary minus in I/O list

Illegal delimiter in I/O list

Unterminated implied-DO loop in I/O list

Illegal = sign in I/O list

Illegal partword operator

Illegal arithmetic expression

Illegal operator sequence

Illegal use of = sign

Missing parenthesis in I/O statement
with implied DO loop will also cause
>041<

Extraneous characters at the end of
assignment statement

VII-2-l4

comma

arithmetic

In Table 2-3, (R) indicates a recoverable error and
terminal error.

(T)

indicates

Table 2-3
OTS Error Messages
Number

possible Source

Meaning

05 (R)

SQRT

Negative REAL square-root argument

06 (R)

DSQRT

Negative DOUBLE PRECISION
argument

07 (R)

.GO

Illegal index in computed GOTO

10 (T)

.FR, .FW, .FS, .FX,
DEFINE, RANCOM

Illegal I/O device number

.FR, .FA, .FE, .FF,
.FS, RANCOM,
RBINIO, RBCDIO

Bad input data - lOPS mode incorrect

12 (T)

.FA, .FE, .FF

Bad FORMAT

13 (T)

.BC, .BE, ALOG

Negative or zero REAL logarithmic
argument (terminal)

(R)

.BD, .BF, .BG, .BB,
OLOG, DLOGIO

Negative or zero DOUBLE PRECISION
logarithmic argument

15 (R)

• BB , • BC , • BD , • BE ,
• BF, • BG , • BH

Zero raised to a zero or negative
power (zero result is passed)

16 (R)

ATAN2

ATAN2
(0.0,0.0)
returned

17 (R)

DATAN2

OATAN2 (0.000, 0.000)
returned

20 (T)

FlOPS, AUXIO, RANCOM

Fatal I/O error (RSX only) •
The message format is
"OTS-20-XXX-NNNNNN-TSKNM", where XXX
is the LUN, NNNNNN is the event
variable (two's complement) and
TSKNM is the task name.

(T)

square-root

attempted

Pl/2

attempted

Pl/2

21 to 26 are direct-access errors:
21 (T)

RANCOM

Undefined file

22 (T)

DEFINE

Illegal record size

23 (T)

RANCOM

Size discrepancy

DEFINE, RANCOM

Too many records per file
record number

RANCOM

Mode discrepancy

(T)

25 (T)

illegal

(Continued)

XVM/RSX VIB

VII-2-l5

September 1976

Table 2-3 (Cont.)
OTS Error Messages
possible Source

Number
26 (T)

DEFINE

Too many open files

(R)

RELEAE, . FPP

Single integer overflow (detected only
when fixing a floating-point number)

(R)

DBLINT, JFIX,
JDFIX, ISNGL

Extended (double) integer overflow;
also prints PC with FPP system (with
non-floating-point processor system,
detected
only
when
fixing
a
floating-point number)

RELEAE

Single floating-point overflow;
prints PC with FPP system

32 (R)
33

(R)

also

Double floating-point overflow;
also
prints PC with FPP system (detected
only by FPP system, not by software
system)
RELEAE

Single floating-point underflow;
prints PC with FPP system

also

Double floating-point underflow; also
prints PC with FPP system (detected
only by FPP system, not by software
system)

35 (R)

Meaning

36 (R)

RELEAE

Floating-point divide check;
prints PC with FPP system

also

(R)

INTEAE

Integer divide
integer divide
FPP system

(T)

ENCODE

Illegal number of characters specified
(legal:
O<c<625)

(R)

ENCODE

Array exceeded

(T)

DDIO

Bad input data

(T)

Attempt to pass
expected

(T)

check;
if extended
check, prints PC with

arguments

than

FPP memory-protect/nonexistent memory;
also prints PC with FPP system
BCDIO, BINIO

XVM/RSX VlB

READ to WRITE illegal I/O direction
change to disk without intervening
CLOSE or REWIND

VII-2-16

September 1976

In software systems, arithmetic errors resulting in the OTS error
messages summarized above are detected in the arithmetic package
(RELEAE and INTEAE). In the hardware FPP systems, these errors are
detected by the hardware (with the exception of single integer divide
check) and serviced by a trap routine in the FPP routine .FPP.
Where applicable, on such error conditions, the result is patched for
both software and hardware systems as summarized in the following
table.
Table 2-4
OTS Error Messages in FPP Systems
Patched Value
Error
FPP Hardware System

Software System

Single Floating
Overflow (.OTS 32)

± largest single floating
value

same

Double Floating
Overflow (.OTS 33)

± largest double floating
value

not detected

Single Floating
Underflow (.OTS 34)

zero

same

Double Floating
Underflow (.OTS 35)

zero

not detected

Floating Divide
Check ( • OTS 36)

± largest single floating
value

same

Integer OVerflow
(.OTS 30)

limited detection

same

Double Integer
detection
Overflow (.OTS 31)

none

limited

Integer Divide
Check (.OTS 37)

none

same

"Limited detection" means that while a floating-point number is being
fixed, integer overflow and extended integer overflow are detected.
In these instances, plus or minus the largest integer for the data
mode is patched as result.
For Double Integer OVerflow, "none" means that with the FPP system all
extended integer overflow conditions are detected, but the results are
meaningless. Elsewhere, "none" means the result is meaningless.
Further, when converting an extended integer, the magnitude of which
is >2(17) -1, to a single integer, no error is indicated and the high
order digits are lost.
VII-2-17

CHAPTER 3
MACRO:

ASSEMBLING A MACRO PROGRAM

The MACRO Assembler produces relocatable binary object code that can
be loaded for debugging or execution. The Assembler prepares the
object program for relocation, and the Task Builder sets up linkages
to external subroutines.
The MACRO Assembler processes source programs in either a two-pass or
three-pass operation.
In the two-pass assembly operation the source
program is read twice and the object program (and printed listing when
requested) are produced during the second pass. During the first pass
(PASSl) the locations to be assigned the program symbols are resolved
and a symbol table is constructed by the Assembler. The second pass
(PASS2) uses the information computed during PASSl to produce the
final object program.
In an optional three-pass assembly operation, PASS2 calls in a third
pass (PASS3) portion of the Assembler program. PASS3, when called,
performs a cross-referencing operation during which a listing is
produced which contains all user symbols, where each symbol is
defined, and the number of each program lin~ in which a symbol is
referenced. On completion of its operation, PASS3 calls the PASSl and
PASS2 portions of the Assembler program back into core for further
assembly operations.
The MACRO Assembler can also be invoked in batch mode.

VII-3-1

3.1

INVOKING THE MACRO ASSEMBLER

The user can invoke the MACRO Assembler by typing a command
to the following format:

according

[option [,1 ••• 1+name [ext] [, ••• ] 'iJ

Form:

MAC [ROl

Where:

option is a one-character symbol specifying
an assembler option (see Table 3-1), option
characters may be either concatenated or
separated by commas
name of program to be assembled is a string
of one to six .SIXBT characters, one or
more names may be required, depending on
whether or not certain assembly options
(e.g., FZ) have been requested,
several
programs may be specified so that they are
assembled in sequence to produce separate
binary files
ext is a string of one to three .SIXBT
characters representing the extension. SRC
is the default

Example:

Assemble program named TMAC, creating
binary file (B) and a listing (L):
TDV>MAC BL+TMAC

Assemble programs PI and P2 to produce a
separate binary file
(B) for each, both
require the use of a parameter file (P):
TDV>MAC PB+PARAM,Pl,PARAM,P2
Table 3-1 illustrates all Assembler options.
Any number of these
options, in any order and optionally separated by commas, may be
included in a TDV command string.
Table 3-1
Assembler Options
Option

Action

Default

Generate a binary file

No binary file

Generate a listing file on
the requested output device

No listing file (see options

Number each source line (decimal), it is not necessary to
type the L option

Do not number source lines

Do not print program areas
that fall between unsatisfied
conditionals; it is not
necessary to type the L option

Print all source lines

N, C, G)

(Continued on next page)
VII-3-2

Table 3-1 (Cont.)
Assembler Options
Action

Default

Print only the source line of
a MACRO expansion; it is not
necessary to type the L option

Generate printouts for MACRO
expansions and expandable
pseudo-ops (e.g., .REPT)

Before assembly begins, read
program parameters from LUN20; (the code read from LUN20 is read only once; for
this reason only direct assignments should be used)

No parameters; begin assembly
immediately after command
string termination

Print symbols at end of PASS2
in alphanumeric sequence

Do not print symbols in
alphanumeric sequence (see
options V, S, and H)

Print symbols at end of PASS2
in value sequence

Do not print symbols in value
sequence (see options A, S,
and H)

Same as selecting both A and
above

DO not print symbols unless
option A, option V, or both
are requested (see option H)

If A, V, or S option is used,
print symbols one to a line

If A, V, or S option is used,
print symbols horizontally,
four to a line

At completion of PASS2, load
PASS3 to perform the crossreferencing operation; at
completion of PASS3, the
Assembler calls in PASSI and
PASS2 to continue assembling
programs; if the command
string is terminated by an
ALTMODE, control returns to
RSX at the end of assembly

Do not provide a crossreference and do not call in
PASS 3

Do not output the source
extension and the linking
loader code 33 as a special
code in the binary file; this
option must be used when assembling programs in RSX to
run in Background/Foreground

Assemble as usual (use of
unique extensions permits
easy identification of different versions of a program)

Option

(Continued on next page)

VII-3-3

Table 3-1 (Cont.)
Assembler Options
Default

Option

Action

Print any errors occurring
during assembly on the
console printer (LUN-l3) in
addition to the device
assigned to LUN-16; the L or
N option should be used with
the I option; this option is
particularly useful to users
who assign nonprinting
devices to LUN-16

Output errors only to the
listing device (LUN-16)

Generate a Table of Contents
during PASSI; the table will
contain the page number and
text of all assembled .TITLE
statements in the program

No table of contents

Identify assembler version
number; print END PASSI, END
PASS2, and error count on
output terminal

Do not print version number,
END PASS1, END PASS2,
or error count

Ignore .EJECTs; treat the
.EJECT pseudo-op as a comment

Skip to head of form when
.EJECT is encountered

Assembly includes an
additional file: a macro
definition file, a second
parameter file, or a second
part of the program file;
this additional file is
specified in the command
string and it is read via
LUN-IS; (see option Z)

No additional

Assemble the file associated
with the F option not only
during PASSI but also PASS2;
this allows assembly of a
two-part source file on two
different devices or on the
same device; this option
takes effect only if the F
option is also specified

F-option file is referenced
only during PASSl and
therefore may contain
only direct assignment
statements and comments

VII-3-4

file

If the L and X options are entered in the same command string, MACRO
assumes that the N option is also entered. Without the N option, the
user would obtain a cross-reference that would be virtually useless,
because the source lines of the listing would not be numbered.

3.2

INPUT/OUTPUT

The following LUN assignments should
Assembler is invoked under MULTIACCESS:
LUN

made

before

the

MACRO

Assignment

Error messages (terminal recommended)

Source file input

Listing output

Binary file output

Secondary source file input

Auxiliary input (terminal recommended)

A secondary input device is needed to assemble a program from two
different sources.
An auxiliary input device is needed to supply
parameters for a file that is to be assembled.
If an I/O error occurs during assembly, the message:
MAC-I/O ERROR LUN xx yyyyyy
is produced on LUN-13.
In the message, xx represents the logical unit
number
(decimal)
and yyyyyy represents the event variable value
(octal), indicating the cause of the error.

•

XVM/RSX VIB

VII-3-5

September 1976

3.3

COMPARISON WITH OTHER VERSIONS OF MACRO

The MACRO Assembler is essentially the same under RSX as it is under
the other XVM monitor systems. The basic instructions and operation
conventions are described in MACRO XVM ASSEMBLER LANGUAGE MANUAL.
Nevertheless, RSX user interaction with the MACRO Assembler differs in
some ways from the descriptions in the manual. The main differences
occur in support of dump mode, input/output, parameter input, the
definitions of certain standard functions and certain pseudo-ops.
These differences are discussed in more detail below.

3.3.1

Dump Mode

MACRO under RSX supports all standard MACRO features except the
pseudo-ops • IODEV,
.ABS,
.ABSP . • FULL, and .FULLP. This is because
RSX \f70 Device Handler Tasks do not support dump mode (mode 4).

3.3.2

Input/Output

The Assembler's Input Command Decoder has been modified to use
standard Task Development function input and to assemble multiple
files with the same switches. For example:
MAC BNX+FILEl,FlLE2
causes the MACRO Assembler to assemble programs FlLEl and
sequence and to produce separate binary files and listings.

3.3.3

FILE2

from

the

Parameter Input

If the P assembly option is used and input is to come
terminal, the MACRO Assembler types the following message:
MAC-INPUT PARAMETER DEFINITIONS

on the output terminal (LUN-20). The user responds by entering input
parameters.
To terminate input, he types a CTRL/D (to) followed by a
carriage return.

3.3.4

MACRO Definitions File

The RSX Assembler does not contain within itself the definition of
standard, frequently-used System Directive and I/O calls. These exist
in a MACRO Definitions File (ru1C.nn SRC where nn is the current edit
number) which is provided as part of the RSX system. During assembly,
this definition file can be accessed via the secondary-input LON
(LUN-lS)
if assembly option F is specified.
(Z is also needed when
two passes are required.)
This file cannot be read via the auxiliary
input LON (LUN-20) using the P option because many MACROs make forward
symbolic references, necessitating a second pass on the file.

VII-3-6

3.4

ERROR MESSAGES

The Assembler examines each source statement for possible errors.
A
statement containing an error is flagged by one or several letters in
the left-hand margin of the line, or, if the lines are numbered,
between the line number and the location. The following table lists
error flags and their meanings.
Table 3-2
MACRO Assembler Error Flags
Flag

Meaning

Error in direct symbol table
ignored

bank

assignment - assignment

Memory
large)

error

(program

Page error - the location of an instruction
and
the
address it references are on
different memory pages (error in page mode
only)

A .ENDC or
conditional.
line.

Statement contains a reference to a
symbol - the first value is used

.CBE is
The error

gi ven \iith no
appears on the

too

opening
offending

multiply-defined

Symbol not found
during PASS2

user's

symbol

table

Operator combined with its
produce erroneous results

operand

may

resolved

Forward reference - symbol value is not
PASS 2

Line ignored:

segment

Redundant pseudo-op

A second .LOCAL pseudo-op appears
matching .NDLOC pseudo-op

before

.NDLOC appears
.LOCAL pseudo-op

associated

Too many .LTORG pseudo-ops (more than eight)

without

Literal error:
1.

Phase error - literal encountered in PASS 2
does not equal any literal found in PASSI

Nested literal (a literal within a literal)
(Continued on next page)
VII-3-7

Table 3-2 (Cont.)
MACRO Assembler Error Flags
Flag

Meaning

Multiple symbol definition - first value
used

defined

Error in number usage (digit 8 or 9 used
influence)

under

• OCT

Phase error:

PASSl symbol value not equal to PASS2 symbol
value (PASS2 value ignored)

A tag defined in a local area (.LOCAL
pseudo-op) is also defined in a non-local
area

Questionable line:
1.

Line contains two
or
more
operators (e.g., LAC A+*B)

Bad line delimiter - address
fteld
not
terminated
with
a
semicolon, carriage
return, or comment

Bad argument in .REPT pseudo-op

sequential

Possible relocation error

Symbol error - illegal character used in tab field

Undefined symbol

Line overflow during macro expansion

Illegal use of macro name or index reqister

A .CBS was given with no closing .CBE, a .DEFIN has
no corresponding .EliDM and/or a .IF conditional has
no closing .ENDC. This error is output on the .END
statement at the end of PASS 1.

VII-3-a

In addition, certain conditions cause assembly to be terminated
prematurely.
The following table lists possible error messages and
their meanings.
Table 3-3
MACRO Assembler Error Messages
Message

Meaning

SYNTAX ERR

Bad command string;
returns to TDV

NAME ERROR

File named in command string
not found; control returns to TDV

TABLE OVERFLOW

Too many symbols and/or MACROs;
control returns to TDV

CALL OVERFLOW

Too many embedded MACRO calls:
control reutrns to TDV

CORE EXHAUSTED
AT LINE nnn

PASS3 error; too many Symbol
references; control
returns to TDV

VII-3-9

control

CHAPTER 4
EDITOR:

TEXT-EDITING SOURCE CODE

The Text Editor is an effective text editing program that allows the
modification and creation of symbolic source programs and other ASCII
text material. The Editor reads and writes standard lOPS ASCII lines.
By means of keyboard commands, the Editor is directed to bring a line
or group of lines from an input file to an internal buffer. By means
of additional commands, the user can then examine, delete and change
the contents of the buffer, and insert new text at any point in the
buffer.
When the line or block of lines has been edited, it is
written into a new file on the output device.
The Editor is most frequently used to modify MACRO and FORTRAN IV
source programs, but it can also be used to edit any symbolic text.
The Editor operates in either an "edit" or "inputh mode.
In the
"editll (or command) mode, the program accepts and acts on control-word
and data strings to open and close files; to bring lines of text from
an open file into the work area; to change, delete or replace the
line currently in the work area; and to insert single or multiple
lines after the line in the work area. In the "input" (or text) mode,
lines from the 'keyboard are interpreted as text to be added to the
open file. Commands are available for conveniently changing from one
operating mode to the other.
Data from the input file are made available for editing in two ways:
in line-by-line mode or in block mode. In the line-by-line mode, a
single line is the unit of the input file available to the user for
modification at any point.
In the block mode, a user-specified
portion of the input file is held in a core buffer for editing until
the user requests that the contents of the buffer be added to the
output file. Line-by-line mode is the default data mode.

4.1

INVOKING THE TEXT EDITOR

The user can invoke the Text Editor by typing a command in the format:
Form:

TDV>EDIV

To return to the MULTIACCESS Monitor after editing and closing a file,
the user must type:

XVM/RSX VIB

VII-4-1

September 1976

E [XIT]
An example of interaction
prompter) :
TDV>EDI
EDITOR XVM/RSX VlBOOO
>OPEN FILNAM EXT

EDIT

>N
>P
.TITLE FILNAM

>C /TOR/TION/

4.2

the

Text

Editor

follows

User invokes Text Editor
Editor gives version number
Open the file FILNAM, with extension
EXT, for editing
Editor indicates EDIT mode
Go to top of file
Print current line: nothing is printed,
because pointer is above first line
of file
Go to next line
Print current line
/EDIT COMMAND DEMONSTRATOR
Change DEMONSTRATOR to DEMONSTRATION

.TITLE FILNAM
>CLOSE
>EXIT
TDV>

with

/EDIT COMMAND DEMONSTRATION
Close file
Exit from Text Editor

INPUT/OUTPUT

Make the following LUN assignments before the Text Editor
under TDV:
LUN

invoked

Assignment

Auxiliary output (listing)

Source file input/output (disk)

Source file scratch input/output
(temporary file) (disk)

Auxiliary output file (disk)

Auxiliary input

• If an I/O error occurs during editing, the message:
EDI -

I/O ERROR LUN xx yyyyyy

is sent to LUN-13. In the message, xx represents the logical unit
number
(decimal)
and yyyyyy represents the octal event variable,
indicating the cause of the error.

XVM/RSX VIB

VII-4-2

September 1976

4.3

COMPARISON WITH OTHER VERSIONS OF THE TEXT EDITOR

The Text Editor runs the same way under RSX as it does under the other
XVM operating systems. Program commands and conventions are described
in the EDIT/EDITVP/EDITVT XVM utility Manual.
RSX user interaction with the Text Editor differs in some ways from
the descriptions in the manual.
The main differences occur in
disk-to-disk editing, buffer size and partition size. The differences
are described in detail in the following sections.

4.3.1

Disk-to-Disk Editing

RSX supports all standard EDIT features, but is restricted to
Therefore, LUN-17 and LUN-18 must be assigned
disk-to-disk editing.
the to disk.

4.3.2

Buffer and Partition Size

On program initialization, the maximum buffer size parameter for
the
SIZE command is computed. The parameter retains the computed value or
is set to 56, whichever is smaller.
The SIZE command is then
restricted to a value less than or equal to the maximum buffer size.
If the partition size is too small to permit buffers, the message:
EDI-PARTITION TOO SMALL
is set to LUN-13 and the Text Editor exits.

•
4.4

ERROR MESSAGES

When a colon follows an error message, the incorrect command
printed below the error message.

XVM/RSX VIB

VII-4-3

line

September 1976

Table 4-1
Editor Error Messages
Message

Meaning

BUFFER NON-EMPTY

BLOCK
OFF
command
issued
before Block Buffer emptied by
WRITE command

NOT A REQUEST:

Command string error

Command string
BRIEF mode ON

END OF BUFFER REACHED BY:

Command has
moved
below last line

pointer

END OF FILE REACHED BY:

Command has
moved
below last line

pointer

READ ERROR:

Incorrect parity or checksum

TRUNCATED:

Line too long

BUFFER CAPACITY EXCEEDED BY:

Buffer
Mode

NO FILE NAME GIVEN.

File name missing

NO INPUT FILE PRESENT.

Input file missing

FILE name IS PRESENT ON OUTPUT
DEVICE. PLEASE RENAME IT OR IT
WILL BE DELETED.

More than one file called name

NOTHING IN FILE

No output to file

SIZE TOO SMALL

When Block Mode is ON, number
of lines specified in MOVE >
size of current block buffer

NOT ENOUGH LINES
END OF FILE REACHED BY:

When Block Mode is OFF, number
of lines MOVE specifies to be
moved > number in current file

NOT ENOUGH BUFFER SPACE

Not enough buffer space
store lines being moved

LINES MOVED TO END

Line containing text string
specified in MOVE not found

NO STRING

Convert missing first argument

NOT FOUND

First argument
never found
VII-4-4

error

overflowed

while

Block

CONVERT

CHAPTER 5
SLIP:

EDITING BATCH FILES

The SLIP command invokes a batch-oriented file editor, which not only
can edit ASCII source programs and data sets, but can also produce
line-numbered listings and perform operations
similar to those of
PIP.
SLIP complements EDIT, the TDV interactive Text Editor.
SLIP is
designed particularly for batch operation or for file manipulation,
while EDIT is designed for the on-line user who manipulates text
within a single file. SLIP works at the record level, while EDIT has
extensive intrarecord facilities.
SLIP processes as many as four streams of information
shown in the following diagram:

run,

Correction Input
(commands and insertion)

input
(original file)

output

~(edited file)

external
file
inputs

This editor SLIPs information from one file to another.
It always
generates a new file so that the original file can be preserved.
Batch operation requires this; otherwise a minor change, incorrectly
specified, could destroy an important file. The user can maintain
many backup levels.

VII-5-1

5.1

INVOKING SLIP

The user can invoke SLIP in one of two ways.
has the following format:

From

TDV,

Form:

SLIP option [, ••• ]V

Where:

option is an option from Table 5-1

Example:

TDV>SLIP N

the

command

The user can also invoke SLIP in BATCH mode as part of a job with
following control record:
$SLIP options
as explained in 5.1.1.
A SLIP run must contain the following four sections:

5.1.1

TDV>SLIP options or $SLIP options

*FILE specifications

SLIP control records and insertion records

End-of-file (-$ in DV or $EOF in BATCH or TDV)

$SLIP Options

The $SLIP record has the following format:

... )

Form:

$SLIP option [,

Where:

option is an option from Table 5-1

Example:

List output file and suppress trailing spaces
of input file:
$SLIP L,S

VII-5-2

the

Table 5-1
SLIP Options
Meaning

option
N[LIST)

No printout except *FILE cards and errors

C[HANGES]

List control records, deleted lines, *FILE
and errors (default)

L[IST)

List entire output file, with line
numbers,
inserted lines, deleted lines, *FILE cards, and
errors

K[EEP)

Retain trailing spaces on input records

cards,

S[UPPRESS) Suppress trailing spaces (in multiples of 5)
input record (default)

5.1.2

from

*FILE Specifications

SLIP uses *FILE, an indirect file selection system.
The
specify exactly one input and one output file as follows:

user

Form:

*FILE I[NPUT):LUN=' [infile [ext)]'O[UTPUT]:
LUN=' [outfile [ext])'$

Where:

LUN is a one- or two-digit Logical unit
Number
infile is a string of one to six .SIXBT
characters representing the input file and
is optional only if the input LUN is
non-file-oriented
ext is a string of one to three .SIXBT
characters representing the file extension
outfile is a string of one to six .SIXBT
characters representing the output file and
is optional only if the output LUN is
non-file-oriented

Example:

Input FILEI RC from LUN-17 to be edited and
output on LUN-18:
*FILE I:17='FILEl SRC' :18='FILEI SRC'$

must

The infile ext and outfile ext can be identical, but it is better to
keep a backup file.
If a backup file is desired, the user should
enter a sequence such as the following:

VII-5-3

$DELETE

file bak

$RENAME

file src, file bak

$SLIP

options

*FILE

I:LUN='file bake O:LUN='file src'

$EOF
If the user then makes a bad edit run, she can remove the $DELETE and
$RENAME records and rerun the update, because the original file is
still intact as "file bak."
Note that certain SLIP commands
*FILE records.

5.1.3

described

below

require

additional

SLIP Control Records and Insertion Records

SLIP logically numbers all lines within each file it processes so that
the first line in each file is number 1. If a SLIP run includes a LIST
option, but no control or insertion records, it produces a line
printer listing of the file with line numbers as in the example below.
Whether or not the run includes control and insertion records, the
listing always shows the final, resultant line numbers, those to be
used for the next SLIP performed on that file.
Because
the
renumbering occurs after editing and before output of the listing, the
user refers while editing to the original line numbers.
Renumbering does occur, however, when any of the four search commands
is used.
The line selected by the search becomes line 1. Line
references in all subsequent commands are then relative to that line.
For instance, after a command causes a search for 'C' in the sample
input file below, the command
-3,3
will delete the line containing 'E', which was originally line 5.
Each search sets the selected line to 1. It is impossible to reference
the original line numbers after any search has been conducted.
The file in the example
subsequent SLIP examples:
Example: 1.
2.
3.
4.
5.
6.
7.

below

will

B
C
0

E
F
G

VII-5-4

the

input

file

for

all

Subsequent sections give details on the nine
which are:

SLIP

control

commands,

• INSERT
• INSERT FILE
• REPLACE
• REPLACE WITH FILE
• SEARCH AND INSERT
• SEARCH AND INSERT FILE
• SEARCH AND

REPI~CE

• SEARCH AND REPLACE WITH FILE
• END-OF-FILE
All control commands must follow the *FILE specification and must
begin with a minus sign (-) in column one, followed by one or more
parameters. Embedded blanks are allowed within the parameters and are
ignored except when between single quotes ('). The commands that
permit insertion of an entire file are especially useful for inserting
subroutines.

5.1.4

End-of-File

A set of correction cards must be terminated by an end-of-file
specification.
This is $EOF in BATCH mode or the command -$ in BATCH
or TDV.

5.2

CONTROL RECORDS

The following sections summarize
examples of usage.

SLIP

VII-S-S

control

records

and

provide

5.2.1

INSERT

The user can specify an INSERT operation by a control
following format:

record

Form:

-n

Where:

n is the number of the line after which the
insertion will be made

the

All records that follow the INSERT control record and precede another
control record or an $EOF are inserted into the output file following
line n of the input file. For example if the following records
-1
X
Y
Z

are specified to edit the input file in 5.1.3,
file is:
1.

5.
6.
7.
8.
9.
10.

C
D
E
F
G

VII-5-6

the

resulting

output

5.2.2

INSERT FILE

An INSERT FILE operation requires two control records.
in the forma t:

The

first

Form:

-n

Where:

n is the number of the line after which
insertion is to be made

the

The second record is a *FILE record in the format:
Form:

*FILE I [NPUT] :LUN='secfile ext'

Where:

LUN is the logical unit number, which must
be different from those used for the input
and output files of the edit
secfile is a string of one to six
.SIXBT
characters representing the file
to be
inserted
ext is a str ing of one to three
.SIXBT
characters representing the file extension

The entire second file is inserted into the input file after relative
line number n.
Another control record usually follows the *FILE
record.
If noncontrol records follow it, they are inserted after
the
last line of the inserted file and before the next line of the input
file.

For example, if the second file, ZZZ RC, consists of:

and is inserted into the input file in 5.1.3 by the commands:
-1
*FILE I:15=IZZZ SRC'$

the resulting output file is:
1.
2.
3.

A
XX
YY

6.
7.
8.
9.
10.
11.

B
C

XVM/RSX VIB

E
F

VII-5-7

September 1976

5.2.3

REPLACE

The user can specify
following format:

replacement

control

record

Form:

-n,m

Where:

n is the number of the first line to be deleted
and replaced
m is the number of the last line to be deleted
and replaced

the

All input file records numbered n through m, inclusive, are deleted
and all insertion records following the REPLACE control record are
inserted in the output file following the (n-l)th record of the input
file.
Note that if no records are inserted, lines n through m
The command

are

deleted.

-204,99999
deletes all lines after 203. The command
-204,204
deletes only line 204.
The following example illustrates
inserted. If the records

the

case

which

records

are

-2,4
X
Y
Z

-$
are specified to edit the input file in 5.1.3,
file is:
1.
2.
3.
4.
5.

6.
7.

A
X
y

E
F
G

VII-S-8

the

resulting

output

5.2.4

REPLACE WITH FILE

A REPLACE WITH FILE operation requires two control records.
is in the following format:

The first

Form:

-n,m*

Where:

n is the number of the first line to be deletedJ
second file will follow line n-l
m is the number of the last line to be deleted;
second file will precede line m+l

The second record is a *FILE record in the following format:
Form:

*FILE I[NPUT):LON='secfile ext'

Where:

LON is the Logical Unit Number
secfile is a string of one to six .SIXBT
characters representing the file to replace
the deleted lines
ext is a string of one to three .SIXBT
characters representing the file extension

Lines n through m are deleted and replaced with the entire second file
specified.
Another control record usually follows the *FILE record.
If other insertion records follow it, they are inserted after the last
line of the second file.
For example, if the following control records:
-3,4*
*FILE I:l5='ZZZ SRC'$
-$

are specified to delete lines 3 and 4 of the input file in 5.1.3 and
to replace them with the second file, ZZZ SRC in 5.2.2,the resulting
output file is:
1.
2.

A
B

4.
5.
6.

7.
8.
9.

ZZ
KK
E

F
G

VII-5-9

5.2.5

SEARCH AND INSERT

The user can specify a SEARCH AND INSERT operation by a control record
of the following format:
Form:

-'xxxxx'

Where:

xxxxx is a string of one to five characters;
the insertion will be made after the line
beginning with the string

The search facility is designed to detect FORTRAN line numbers.
SLIP
examines each line of the input file until it finds one beginning with
the string xxxxx. All lines that follow the SEARCH AND INSERT control
record and precede another control record or $EOF are inserted into
the output file following the line containing xxxxx in the input file.
For example, if the following records

-'A'
X

Y
Z

are specified to edit the input file in 5.1.3,
file is:
1.
2.
3.
4.
5.
6.

7.
8.
9.
10.

the

resulting

output

A
X

y
Z
B

C
D
E

F
G

Renumbering occurs when the search is successful.
by the search becomes line 1.

VII-5-10

The

line

selected

5.2.6

SEARCH AND INSERT FILE

SEARCH AND INSERT FILE operation requires two control records.
first is in the following format:

Form:

-'xxxxx'*

Where:

xxxxx is a string of one to five characters:
the file will be inserted after the line in
which the string appears

The

The second record is a *FILE record in the following format:
Form:

*FILE I[NPUT):LUN='secfile ext'$

Where:

LUN is the Logical unit Number
secfile is a string of one to six .SIXBT
characters representing the file to be
inserted
ext is a string of one to three .SIXBT
characters representing the file extension

SLIP examines each line of the input file until it finds one beginning
with the string xxxxx. The entire second file is inserted into the
output file after the line containing xxxxx. Another control record
usually follows the *FILE record. If other insertion records follow
it, they are inserted after the last line of the inserted file.
For example, if the following records

-'A'

*FILE I:15='ZZZ SRC'$

are specified to insert the second file, ZZZ SRC in 5.2.2, after
i of the input file in 5.1.3, the resulting output file is:
1.

line

3.
4.

YY
ZZ

KK
B

9.
10.
11.

E
F
G

Renumbering occurs when the search is successful.
by the search becomes line 1.

VII-S-ll

The

line

selected

5.2. 7

SEARCH AND REPLACE

The user can specify a SEARCH AND
record of the following for.mat:

REPLACE

operation

control

For.m:

-'xxxxx' ,m

Where:

xxxxx is a string of one to five characters;
the line containing the string is the first
to be deleted and replaced
m is the number of the last line to be
deleted and replaced

SLIP examples each line of the input file until it finds one beginning
with the string xxxxx.
All input file records from the line
containing the string through line m, inclusive, are deleted.
All insertion records following the SEARCH AND REPLACE control record
are inserted in the output file following the record just before the
record containing xxxxx.
Note that if no records are inserted, the specified lines are deleted.
The command
-' ABC' ,99999

deletes all lines after the one containing 'ABC'. The command
-' ABC' ,1

deletes only that line.
The following example illustrates
inserted. If the records

the

case

which

records

are

-'B',3
X

are specified to edit the input file in 5.1.3, the
file is:
1.
2.
3.

resulting

output

X
Y

5.
6.
7.

E
F
G

Renumbering occurs when the search is successful.
by the search becomes line 1.
VII-5-12

The

line

selected

5.2.8

SEARCH AND REPLACE WITH FILE

A SEARCH AND REPLACE WITH FILE operation requires two control records.
The first is in the following format:
Form:

-'xxxxx', m*

Where:

xxxxx is a string of one to five characters:
the line containing the string is the first
to be deleted: second file will follow the
preceding line
m is the number of the last line to be
deleted: second file will precede line m+l

The second record is a *FILE record in the following format:
Form:

*FILE I [NPUT] :LUN='secfile ext'S

Where:

LUN is the Logical Unit Number
secfile is a string of one to six .SIXBT
characters representing the file to replace
the deleted lines
ext is a string of one to three .SIXBT
characters representing the file extension

SLIP examines each line of the input file until it finds one beginning
with the string xxxxx.
All input file records from the line
containing the string through line m, inclusive, are deleted and
replaced with the file specified.
Another control record usually
follows the *FlLE record.
If other insertion records follow it, they
are inserted after the last line of the second file.
For example, if the following records:
_IC' ,2*

*FlLE I:15='ZZZ SRC'$
-$

are specified to delete lines 3 and 4 of the input file in 5.1.3 and
to replace them with the second file, ZZZ SRC in 5.2.2, the resulting
output file is:
1.

B
XX

4.
5.

YY
ZZ

7.
8.
9.

E
F
G

Renumbering occurs when the search is successful.
by the search becomes line 1.
VII-5-13

The

line

selected

5.2.9

END-OF-FILE

The user can specify END-OF-FILE by a control record of the
format:

following

5.3

INPUT/OUTPUT

The SLIP TDV Function Task is assigned Task name
SLI...
at
Task-Building time. SLIP uses LUN-12 for command input and LUN-16 for
listing output. The user may use Logical units for files as he
wishes.
Normal editing operations use LUN-17 for input, LUN-IS for
output, and LUN-15 for secondary input.

5.4

ERROR MESSAGES

SLIP detects four types of errors:

· *FILE specification errors
· $SLIP control record errors
· SLIP command syntax errors
· SLIP sequencing errors
5.4.1

*FILE Errors

A message of the following form indicates a *FILE error:
*FILE ACCESS ERROR xx -- PROGRAM TERMINATED
where xx is a code in Table 5-2.

VII-5~14

Table 5-2
Error Codes for *FILE Routine
Code

5.4.2

Meaning

*FlLE does not appear in columns 1-5 of card read

File type inputs or outputs not found

Colon missing after file type

Missing Logical unit Number (i.e., INPUT:='file ' )

Logical unit Number does not consist of digits 0-9

Logical Unit Number is too long (more than 2 digits)

Missing equal sign (=) after Logical unit Number

Missing quote (I) after equal sign

Invalid delimiter within file name or missing quote (I)
after file name

Illegal file type, not INPUT:

File not found on input device

File already open for output

Not enough space in partition for buffer

Logical Unit is not assigned to a device

Empty system pool

File I/O error other than codes 11-15

File already open but cannot be closed

File name is greater than 8 characters (only first 6
are used): probably missing space between file name and
extension or missing quote (I)

Incorrect number of files specified:
meet program requirement

or OUTPUT:

input

does

not

$SLIP Control Record Errors

Selecting a nonexistent processing option causes
control record error of the following form:
SLIP DOES NOT HAVE A x OPTION
where x is the nonexistent option.

VII-5-15

nonfatal

$SLIP

5.4.3

SLIP Command Syntax Errors

SLIP command syntax errors are more serious, for they might cause
considerable damage to a file. Therefore, most errors of this type
cause SLIP to perform a reasonable action. It usually runs through to
the end-of-file, copying the rest of the input file into the output
file.
Illegal characters in the command line are
cause the following message to appear:

detected,

however.

They

CORRECTION CARD ERROR -- ILLEGAL CHARACTER x
where x is the illegal character.
as if it were

Because the faulty line is

treated

-99999

SLIP processes through to the end-of-file, making
corrections. The remaining command records are ignored.

5.4.4

further

SLIP Sequencing Errors

A SLIP sequencing error is caused by a reference to a line number that
has already been passed. This indicates that the correction deck is
out of order. SLIP exits immediately after producing a message of the
following form:
CORRECTION CARD ERROR
CURRENT LINE = xx
AFFECTED LINE - xx -- xx
If an existing file bears the same name as the output file specified,
the existing file is retained. If not, a new but incomplete file is
generated.

5.5

DEMONSTRATION OF SLIP EDITING

$LIST SLTJOB JOB
page eject
$JOB 50(002) DEMONSTRATION OF SLIP EDITING
$LIST SLTJOB JOB
$OECK TESTIN SRC
~

BBBBBBBB
CCCCCCCC
DODDDODD
EEEEEEEE
FFFFFFFF
GGGGGGGG
HHHHHHHH
VII-5-16

11111111
JJJJJJJJ

KKKKKKKK

LLLLLLLL
MMMMMMMM

$EOF
$LIST TESTIN SRC
$SLIP L,S
*FlLE IN:17='TESTIN SRC' OUT:18='TESTOU SRC'

$SLIP L,S
*FILE IN:17='TESTIN SRC' OUT:18='TESTOU SRC'
-3
XXXXXXXX
YYYYYYYY

zzzzzzzz

$LIST TESTOU SRC
$SLIP L,S
*FlLE IN:17='TESTIN SRC' OUT:18='TESTOU SRC' $

-2,5

XXXXXXXX
YYYYYYYY

zzzzzzzz

$LIST TESTOU SRC
$SLIP L,S
*FlLE IN:17='TESTIN SRC' OUT:18='TESTOU SRC'

-'GGG'
-2,2

XXXXXXXX
-$

$LIST TESTOU SRC
$DECK EXTIN SRC
ITHIS IS A USEFUL WAY
IOF INSERTING OPERATING
/INSTRUCTIONS INTO A LISTING WITHOUT
lRAVING TO TYPE THEM TWO OR MORE TIMES.
$EOF
$LIST EXTIN SRC
$SLIP L,S
*FILE IN:17='TESTIN SRC' OUT:18='TESTOU SRC' $
-3*

*FlLE IN:15='EXTIN SRC' $
-6*
*FlLE IN:15='EXTIN SRC' $
-$

$LIST TESTOU SRC
$SLIP L,S
*FlLE IN:17='TESTIN SRC'
-'HHH' ,2*
*FlLE IN: 15= ' EXTIN SRC'
-$
$LIST TESTOU SRC
$END
$DECK TESTIN SRC
$LIST TESTIN SRC

OUT:18='TESTOU SRC'
$

VII-S-17

page eject
AAAAAAAA

BBBBBBBB
CCCCCCCC
DDDDDDDD
EEEEEEEE
FFFFFFFF
GGGGGGGG
HHHHHHHH
IIIIIIII
JJJJJJJJ
KKKKKKKK

LLLLLLLL
MMMMMMMM

page eject
$SLIP L,S
*FlLE IN:1717='TESTIN SRC' OUT:lS'TESTOU SRC'

* *CHANGE* *

-$
1 AAAAAAAA

2 BBBBBBBB
3 CCCCCCCC
4 DDDDDDDD
5 EEEEEEEE
6 FFFFFFFF
7 GGGGGGGG
S HHHHHHHH
9 IIIIIIII
10 JJJJJJJJ
11 KKKKKKKK
12 LLLLLLLL

13 MMMMMMMM

********** S LIP

COM P LET E **********

page eject
$SLIP L,S
*FlLE IN:17='TESTIN SRC' OUT:lS='TESTOU SRC'

* *CHANGE* *

-3
1 AAAAAAAA

2 BBBBBBBB
3 CCCCCCCC
4 XXXXXXXX

VII-5-18

5 yyyyyyyy
6

* *CHANGE * *

zzzzzzzz

-$
7 00000000

8 EEEEEEEE
9 FFFFFFFF
10 GGGGGGGG

11 HHHHHHHH
12 IIIIIIII
13 JJJJJJJJ
14 KKKKKKKK
15 LLLLLLLL
16 MMMMMMMM

********** S LIP

COM P LET E **********

$LIST TESTOU SRC
page eject
AAAAAAAA

BBBBBBBB
CCCCCCCC
XXXXXXXX
yyyyyyyy

ZZZZZZZZ
00000000

EEEEEEEE
FFFFFFFF
GGGGGGGG
HHHHHHHH
IIIIIIII
JJJJJJJJ
KKKKKKKK
LLLLLLLL
MMMMMMMM

page eject
$SLIP L,S
*FlLE IN:17='TESTIN SRC I UT:18='TESTOU RC I $

* *CHANGE * *

-2,5
1 AAAAAAAA

* *DELETE * *

BBBBBBBB
2 XXXXXXXX
3 YYYYYYYY

4 ZZZZZZZZ
* *CHANGE * *

VII-5-19

**DELETE**
**DELETE**
**DELETE**

CCCCCCCC
DDDDDDDD
EEEEEEEE
5 FFFFFFFF
6 GGGGGGGG

7 HHHHHHHH
8 IIIIIIII
9

JJJJJJJJ

10 KKKKKKKK

11 LLLLLLLL
12 MMMMMMMM

********** S LIP

COM P LET E **********

$LIST TESTOU SRC
page eject
AAAAAAAA
XXXXXXXX

yyyyyyyy

ZZZZZZZZ
FFFFFFFF
GGGGGGGG

HHHHHHHH
IIIIIIII
JJJJJJJJ
KKKKKKKK

LLLLLLLL
MMMMMMMM

page eject
$SLIP L,S
*FlLE IN:17='TESTIN RC' OUT:18='TESTOU SRC'

* *CHANGE * *

-'GGG'

1 AAAAAAAA
2 BBBBBBBB
3 CCCCCCCC
4 DODOOODD
5 EEEEEEEE
6 FFFFFFFF
7 GGGGGGGG

* *CHANGE ** -2,2
* *DELETE * * HHHHHHHH
8 xxxxxxxx
* *CHANGE * * -$
9 IIIIIIII

VII-5-20

10 JJJJJJJJ
11 KKKKKKKK
12 LLLLLLLL
13 MMMMMMMM

********** S LIP

COM P LET E **********

$LIST TESTOU SRC
page eject
AAAAAAAA

BBBBBBBB
CCCCCCCC
DODODOOD
EEEEEEEE
FFFFFFFF
GGGGGGGG
XXXXXXXX
11111111

JJJJJJJJ
KKKKKKKK
LLLLLLLL
MMMMMMMM

$OECK EXTIN SRC
$LIST EXT IN SRC
page eject
/THIS IS A USEFUL WAY
/OF INSERTING OPERATING
/INSTRUCTIONS INTO A LISTING WITHOUT
/HAVING TO TYPE THEM TWO OR MORE TIMES.
page eject
$SLIP L,S
*FILE IN:17='TESTIN SRC' OUT:18='TESTOU SRC' $

* *CHANGE * * -3*
*FILE IN:15='EXTIN SRC' $
1 AAAAAAAA

2 BBBBBBBB
3 CCCCCCCC
4 /THIS IS A USEFUL WAY
5 /OF INSERTING OPERATING
6 /INSTRUCTIONS INTO A LISTING WITHOUT
7 /HAVING TO TYPE THEM TWO OR MORE TIMES.
* *CHANGE * * -6*

VII-5-21

*FlLE IN:15='EXTIN SRC' $
8 DDDDDDDD
9 EEEEEEEE
10 FFFFFFFF
II/THIS IS A USEFUL WAY
12 /OF INSERTING OPERATING
13 /INSTRUCTIONS INTO A LISTING WITHOUT
14 /HAVING TO TYPE THEM TWO OR MORE TIMES.
* * CHANGE * * -$
15 GGGGGGGG
16 HHHHHHHH
17 11111111
18 JJJJJJJJ
19 KKKKKKKK

20 LLLLLLLL
21 MMMMMMMM

********** S LIP

COM P LET E **********

$LIST TESTOU SRC
page eject
AAAAAAAA

BBBBBBBB
CCCCCCCC
/THIS IS A USEFUL WAY
/OF INSERTING OPERATING
/INSTRUCTIONS INTO A LISTING WITHOUT
/HAVING TO TYPE THEM TWO OR MORE TIMES.
DDDDDDDD
EEEEEEEE
FFFFFFFF
/THIS IS A USEFUL WAY
/OF INSERTING OPERATING
/INSTRUCTIONS INTO A LISTING WITHOUT
/HAVING TO TYPE THEM TWO OR MORE TIMES.
GGGGGGGG
HHHHHHHH
11111111

JJJJJJJJ
KKKKKKKK

LLLLLLLL
MMMMMMMM

page eject
$SLIP L,S
*FlLE IN:17='TESTIN SRC'

OUT:18='TESTOU SRC'

VII-S-22

* *CHANGE* * -'HHH',2*
*FlLE IN:15='EXTIN SRC' $
1 AAAAAAAA

2 BBBBBBBB
3 CCCCCCCC
4 DDDDDDDD
5 EEEEEEEE
6 FFFFFFFF
7 GGGGGGGG
**DELETE** HHHHHHHH
8 /THIS IS A USEFUL WAY
9 /OF INSERTING OPERATING
10 /INSTRUCTIONS INTO A LISTING WITHOUT
11 /HAVING TO TYPE THEM TWO OR MORE TIMES.
* *DELETE ** IIIIIIII
* *CHAN GE** -$
**DELETE** JJJJJJJJ
12 KKKKKKKK
13 LLLLLLLL
14 MMMMMMMM

********** S LIP

COM P LET E **********

$LIST TESTOU SRC
page eject
AAAAAAAA

BBBBBBBB
CCCCCCCC
DDDDDDDD
EEEEEEEE
FFFFFFFF
GGGGGGGG
/THIS IS A USEFUL WAY
/OF INSERTING OPERATING
/INSTRUCTIONS INTO A LISTING WITHOUT
/HAVING TO TYPE THEM TWO OR MORE TIMES.
KKKKKKKK
LLLLLLLL
MMMMMMMM

VII-S-23

CHAPTER 6
TASK BUILDER AND BASIC TASK BUILDER:

BUILDING A TASK FOR EXECUTION

The Task Builder is an interactive program used to build user and
system tasks from relocatable binary files. This program links the
user's binary files to library functions to create an executable task.
By responding to questions asked by the Task Builder, the user
supplies information on run priority, core partition, COMMON block
requirements, and other task operating characteristics.
The Task Builder is flexible, allowing the user to build a simple
one-program task with no overlays or very complex tasks made up of
multiple programs (some written in FORTRAN and some written in MACRO),
a resident portion, and multiple overlays and suboverlays. Tasks may
be built for a variety of execution modes with the following
characteristics:
1.

Uses floating-point hardware or not

Runs in BANK addressing mode or in PAGE mode

Runs in USER mode (protected) or EXEC mode (privileged)

If in USER mode, runs in XVM mode (wide addressing) or not

The user generates a system of overlays - a resident main program
which may include resident subprograms, a resident blank COMMON
storage area, and a set of subroutines which overlay each other at the
user's request.
Subroutines are organized into units called LINKs
which may overlay each other. Several LINKs may overlay a larger LINK
without overlaying each other.
A LINK is loaded into core when a
subroutine within the LINK is called and it remains resident until
overlayed.
A LINK's core image is not recorded or ·swapped out· when
it is overlayed. The same image is brought into core each time a LINK
is loaded.
For the user who wants to build a simple Task, the flexibility of the
Task Builder can be a nuisance.
For that reason, a second version of
the Task Builder whose task name is BTK... (Basic Task Builder) is
provided.
BTK... assumes answers to all the questions that the
standard Task Builder, TKB ••• , asks directly.
Section 6.5 describes
BTK in more detail.
All disk-resident RSX tasks are built and incorporated in the system
in the . same way.
Throughout the process, the task name is usually
used as file name, but the extension changes. Tasks are assembled or
compiled from source code to produce relocatable binary (extension
BIN) files. The binary files (combined perhaps with other
binary
files, typically library subprograms) are fed through the Task B·uilder
to produce a binary task file (extension TSK) , . . which is cme _ ste~
closer to the executable form than BIN files. Finally, TSK files are

VII-6-1

read by the FININS task or the INSTALL function task, which converts
the task file into absolute core-image form, stores it on the disk for
rapid loading and records its existence in the System Task List.

6.1

INVOKING THE TASK BUILDER

The Task Builder is invoked under TDV in the following way:
Form:

TDV>TKBV

Control is passed to the Task Builder, which establishes dialogue with
the user by typing a question and a prompting character (», and
expecting a response. An example of user interaction with TKB appears
in Figure 6-1.
In all cases, user responses are identified by their
placement after the prompting character.
Each TKB question is
described in detail later in this chapter.

XVM!RSX VIB

VII-6-2

September 1976

TDV>TI,B

TASK BUILDER XVM V1A003
LIST OPTIONS
>BI·U;:, NRM, NFF'

NAME TASK
>STI~+ +.

SPECIFY DEFAULT PRIORITY
DESCRIBE PARTITION
DEFINE RESIDENT CODE
)STATUS,CORE,USERS,TASKS
DESCRIBE LINKS & STRUCTURE
ALLOC. STRATEGV:BOTTOM UP
ACTUAL PARTITION 8IZE:032000
EFFECTIVE PARTITION SIZE:032000
VIRTUAL PARTITION 51ZE:032000
ST(~Tl.JS

000020··-00 ()"72-4

CORE
USERS
TASKS
DATF.5
SPYF.1

OOO"?;~~:=;-··()():l 00:·5

001004-00:l421
00 1422·-()():L 677
SF~C 00:L700-()()1737
SF~C 001740·-00:1.763
.DA
015 001·764--00:?O63
BCDIO 056 002064····00612l
STOP
008 006 122-00613~)
FlOPS 047 ()06136-()()70~.:;6
BBlINT 007 007057-007455
INTEAE 009 007456-007606
RELEAE 011 007607-01070~5
OTSER 016 010706-()11225
SPMSG 01.4 011226·-()1135~5
.CB
004 011356-()11377
.FP
000 011400-011401
MINIMUM EFFECTIVE PARTITION 51ZE:012000
CORE REQ'D
000000-011401.

Tnv>
Figure 6-1
Task Builder Session
An altmode is a null entry. To terminate command input prematurely,
the user should type CTRL/Q followed by a carriage return in response
to any command output message. This causes the Task Builder to exit.

XVM/RSX VIB

VII-6-3

Septe.mber 1976

6. 2

INPUT/OUTPUT

The following LON assignments should be made before the
is invoked under TDV:
LON

Task

Builder

Assignment

System Library input

User Library input

Terminal input

Terminal output

Binary file input

Task file output

If an I/O error occurs during Task Building, the following message:
TKB - I/O ERROR LUN xx yyyyyy
is produced on LUN-l3; xx represents the Logical Unit Number (decimal)
. and yyyyyy the octal Event Variable indicating the cause of the error.

6.3

COMPARISON WITH CHAIN AND EXECUTE DIALOGUE

The operations of the Task Builder under RSX are very similar to those
of the CHAIN and EXECUTE programs which run under control of DOS.
Interaction with these prograITlS is described in detail in the CHAIN
XVM/EXECUTE xvr1 UTILITY MANUAL. i~ote that all command lines logically
terminate with an ALTTvlODE character. Lines terminated by a carriage
return are continued on the next physical line; therefore, a logical
command line may ~onsist of several physical lines.
User interaction with the Task Builder differs in some ways from the
descriptions in the manual. The following sections summarize those
components of the dialogue which remain the same as well as those
which differ significantly under RSX.

6.3.1

List Options

Any of the list, execution mode, and library options, shown in Table
6-1 may be specified. If more than one option is included, entries
must be separated by commas.

VII-6-4

Table 6-1
Task Builder List, Execution Mode, and Library Options
Option

Action

BKR

BANK-mode relocation
(13-bit addressing)

PGR

BUFFS:n

Reserve n decimal I/O
buffers of 422 octal words
each when calculating
effective partition size

n = 0

EXM

EXEcutive mode (neither
protection nor relocation)

NRM

Hardware Floating-Point
Library (floating-point
hardware available)

See MFP option

Output global symbol and
file name in load maps

Output program names
in load maps

Allows task to issue lOT
instructions. (Permitted
only for USER-mode
tasks)

Don't allow task to
issue lOT instruction
unless task is any
EXEC-mode task

NFP

Non-hardware FloatingPoint Library (no floating point hardware
available)

In default, the FP/NFP
option is dynamically
determined by the
availability of floatingpoint hardware

No load map

Output load map

USER-mode (protection
and relotation)

NRM

PAL

Pause after outputting
each link

No pause after outputting each link

PAR

Pause after outputting
resident code

No pause after outputting resident code

PGR

Page-mode relocation
(l2-bit addressing)

PGR

//Ni~M

hardware
be used.

1 XWI

Default

must

exist on the installation if this option

VII-6-S

Table 6-1 (Cont.)
Task Builder List, Execution Mode, and Library Options
Option

Action

Default

RES/name, ••• ,name/ Force the COMMONs named
to be part of the resident
code and load them from
the top of the virtual
partition space down

Make only those COMMONs
declared in the resident
code resident

SAC

Single allocation of
COMMON blocks.
Elements of labelled
COMMONs may be referenced by any coresident link

Elements of labelled
CO~1MONs may not be
referenced by any coresident link

Some COMMON blocks
should be allocated memory
within Shared Addressing
Space. Request specification of these COMMONs
later in dialogue, (permitted only for USERmode tasks)

There will be no
COMMONs allocated
in Shared Addressing
Space

SL:
name

System Library name
(alternate user-specified
System Library name)

.LIBRX (non-floatingpoint hardware) or
.LIBFX (floatingpoint) ,depending on
choice of NFP or FP,
respectively

Output size in load maps

No size in load maps

UL:
name

User Library name
(alternate User Library
name)

.LIBRS

XVM mode or l7-bit
indirect addressing
mode, (permitted only
for USER-mode tasks)

IS-bit addressing

1 XVI-.!

hardware must exist on the installation if this option

be used.

VII-6-6

is to

6.3.1.1 PAGE Mode - Bits 6-17 of a memory-reference instruction are
taken as an operand address, and bit 5 is used to select address
modification via the Index Register (XR). Thus 4K of core is directly
addressable.

6.3.1.2 BANK Mode - Bits 5-17 of a memory reference instruction are
taken as an operand address. Thus aK of core is directl~ addressable,
but the Index Register cannot be used for address modification.
6.3.1.3 EXEC Mode - Tasks running in EXEC mode are not restricted in
the core they may reference or alter, or in the instructions which
they may· execute. I/O Handler and MCR Function tasks must run in EXEC
mode.
Hardware relocation is not used in this mode. Thus the IS-bit
addressing range limits EXEC-mode tasks to partitions below 32K. If a
machine does not have hardware relocation, all tasks must be run in
EXEC mode.
EXEC-mode tasks are assumed to
be
debugged
and
well-behaved.
For this reason, the system performs practically no
checking on EXEC-mode tasks.
6.3.1.4 USER Mode - This is anonprivileged mode in which a task is
prohibited access or execution outside its partition. It may not
direct the system by means ~ I/O Directives or System Directives to
alter any core partition but its own.
The only exceptions are:
1.

USER-mode Tasks may transmit data to and receive data from
System COMMON Blocks by using the COMMON Communicator I/O
Handler task as an intermediary.

USER-mode Tasks may transmit data to and receive data from
System COMMON Blocks or partitions using XVM core sharing
hardware, the SHR option, and the SHARE directive.

USER-mode Tasks may access memory
directives.

via

the

Spy

and

SPYSET

A USER-mode Task is also prohibited by the hardware from
executing
such privileged instructions as HLT, rOT, OAS, or double XCT (unless
the rOT option was specified when the task was built).
Reasonable protection is provided, but this m~e should .not ~
considered II idiot proof, II because a USER-mode Task l.S not restrl.cted l.n
issuing Directives which affect areas other than core.
Such a Ta~k
may, for example, interfere with the scheduling of other TasksJ l.t
may tie up I/O devices by attaching them indefinitely:
and it may
enter tight loops, making continued system requests that could exhaust
the Pool of Empty Nodes.
USER-mode Tasks are relocated to zero, and use hardware relocation and
upper-bound checking to effect memory protection. Unless XVM mode is
specified, IS-bit addressing range limits the size of such a task's
useful partition space to 32K. However, hardware r~locati_on permits
positioning of partitions for USER-mode tasks anywhere in l28K.

VII-6-7

The protected/relocated mode is called "user" mode to emphasize the
fact that it is the normal mode;
the mode recommended for tasks,
unless they must run unprotected. A task that is to run "protected"
is not protected from other tasks;
rather, other tasks are protected
from it. Such protection is necessary when debugging a new task.

Most tasks under RSX can be aborted (i.e., forced to exit).
In this
event,
I/O rundown is performed for the task. For example, if a task
should exit, leaving some device attached and several files open on
the disk, I/O Rundown is invoked.
In effect, this detaches the device
and closes all of the files.
An advantage to building user-mode tasks is that their partitions can
be redefined without requiring that the tasks be rebuilt. All user
tasks that run under MULTIACCESS must be built in user mode to
preserve system integrity.
If XVM mode as well as user mode is specified for a task,
that task
can indirectly access memory via l7-bit addressing. Such a task could
access up to l28R if such a partition were allowed in the system.
In
practice, however, the maximum partition size is l14K*. Despite this
wide addressing capability, the executable code and initialized COMMON
blocks** of such a task cannot exceed 32K. Nevertheless, XVM mode is
highly useful if a task contains extensive code as well as large
uninitialized COMMON blocks. The ability to access such COMMON blocks
is the primary use of XVM mode.
The XVM option depends on the
existence of XVM hardware.
Users without an XVM or PDP-IS with an
XM-lS option should not attempt to build a task in XVM mode.

6.3.2

Name Tasks

The user specifies a one- to six-character task name
task to be built.

6.3.3

identifying

the

Specify Default priority

The user specifies the default priority at which a task will run.
This is an optional parameter. It can be entered or changed when the
task is installed.
If specified,
the priority must be between 1
(highest
priority)
and decimal 512
(lowest priority).
If not
specified, TKB assumes a default priority of 400.

*Since l28K is the maximum supported core size and must include space
for the Executive,
I/O handlers and MCR partition, the maximum
partition size is l14K.
**COMMON blocks are initialized by block data subprograms
and by the .CBS/.CBC/.CBE pseudo-ops in MACRO.

XVM/RSX VlB

VII-6-8

FORTRAN

September 1976

6.3.4

Describe Partition

The user identifies the core partition in which
using the form:
Form:

the

task

will

run,

name [ (size) ]
a user-mode task
Cname[(base,size)]
J for
for an exec-mode task

Where:

name identifies a partition that has already
been defined
base is the octal starting address of the
partition
size is the octal size of the partition

Example:

DESCRIBE PARTITION
)P40.0

Typing an altmode causes the task being built to be relocated for the
partition currently in use by the user's copy of TKB. This feature is
available for convenience.
Normally,
the
MULTIACCESS
Monitor
dynamically selects the partition assignment of all user-mode tasks
executed under MULTIACCESS.
If the partition base and size are unspecified, the named partition is
presumed to exist in the current configuration. The Partition Block
Description List (PBDL) is scanned by the Task Builder for the named
partition and the existing values of base and size are used.
Alternately, if the partition does not exist in
the
current
configuration and the task is being built to run in user mode
(relocated), only the partition size need be specified; the base can
be
omitted.
Exec-mode
tasks
require
both
base
and size
specifications.
The execution mode is not a characteristic of a given partition.
Consequently, the user can build tasks with different execution modes
to run within the same partition. Partitions must be a multiple of
400 (octal) words in size.
Partitions can be defined starting
immediately above the top of the Executive.
The size of the partition specified to TKB or the existing value of
the partition size is called the actual partition S1ze. This value is
reduced by the buffer space, specified by the BUFFS option, to obtain
what is called the effective partition size. This is the space that
could be used by the task, assuming that it were able to address it.
For user-mode tasks, buffer space is always rounded to the next
highest increment of 400 (octal) words to permit effective use of the
memory-protection/relocation hardware. The virtual partition size is
that part of the effective paitition size that the task can address.
Usually the effective partition size is equal to the virtual partition

XVM/RSX VlB

VII-6-9

September 1976

only reason the effective partition size might exceed the virtual
partition size is if the effective partition size were greater than
the maximum virtual partition size for a task built with a particular
set of options. The maximum virtual partition size for a task can be
determined from the following chart.
Options Specified

Maximum Virtual Partition Size

EXM

32K

NR14 (not XVM and not SHR)

32K

NRM, XVM (not SHR)

l28K

NRI-1, SHR (not XVM)

24K

URM, XVM, SHR

l20K

The Task Builder allocates code and COInI.'lon bloe1::s within the virtual
partition space with one exception. Shared common blocks are always
allocated memory within the shared address space (SAS) which is
immediately above the virtual partition space ,-rhenever the SHR option
is specified.
6.3.5

Describe System or Shared COMMON Blocks

If the task is being built in EXEC'mode, the user will be asked to
specify System COMMON blocks. If the task is being built in USER-mode
and the SHR option was declared, the user will be asked to specify
Shared COMMON Blocks.
The way in which such COMMON blocks are
indicated is quite similar but tilere are some differences between the
formats used to specify System or Shared cor·u,'tONs.

6.3.5.1

Describe System COMMON Blocks

Here the user identifies co~rnON blocks which are referenced by the
task but may be common to all tasks in RSX. These System COMMON
Blocks are used for communication between tasks; however, a task may
also have its own internal COl-1MON blocks.
such
EXEC-mode tasks can indirectly access System COMMONs provided
COMMONs lay within the first 32K of core. This is because EXEC-mode
tasks reside within the lower 32K of memory and run unprotected~
EXEC-mode tasks cannot indirectly access system COMMONs which reside
above 32K.
Each such COMMON block is specified according to the following format:

VII-6-10

Form:

name (base,size) [, ••• l

Where:

name identifies a COMMON block which has been
defined in RSX at System Startup time
base is the octal starting address of the
COMMON block
size is the octal maximum size of the COMMON
block

Example:

DESCRIBE SYSTEM COMMON BLOCKS
>FLAG(36400,400)

The user can enter as many as four COMMON block
descriptions by
inserting commas between entries.
Those COMMON blocks in the user
program which are not declared to the Task Builder to be System COMMON
Blocks are allocated within the task's virtual partition space and are
referenced only by that task. Blank COMMON has the name .XX.
6.3.5.2

Describe Shared COMMON Blocks

The user must identify those COBMON Blocks referenced by the task
which should be allocated memory within the task's Shared Address
Space. These COl4MONs must be named and uninitialized.
The physical
memory actually accessed when the task references a word in such a
Crn/illON will depend upon the state of the MM register at the time of
the access.
The I~ register will be set when the task issues the
SHARE directive. Once the SHARE directive has been issued with the
correct parameters, ~~ hardware will map the task's accesses to
Shared Addressing Space (SAS) into other locations within physical
memory.
Since a task's SAS is not part of the task's virtual
partition space, accesses to shared cm~ONs prior to issuing the SHARE
directive will cause a.memory protection violation, forcing the task
to be aborted.
SAS is divided into Internal Shared Address Space (ISAS) and External
Shared Address Space (ESAS). ISAS is always 400 octal words long and
its base is identical to the base of SASe ESAS begins at the base of
SAS plus 400 octal words (i.e., at the end of ISAS). The length of
ESAS depends upon parameters given in the SHARE directive. For tasks
not built in XVM-mode, SAS starts at word 60000 octal relative to the
partition's base. SAS starts at word 360000 octal relative
to the
partition's base for tasks built in XVM-mode.
When the task has issued the SHARE directive, accesses to ISAS will be
mapped into the first 400 octal words of the task's partition.
References to ESAS will be mapped into
specified in the SHARE directive.

area

physical

memory

The use of the SHR option depends upon the existence of XVM hardware
and the SHARE directive. If the user does not have such hardware or
the NOXM assembly parameter was defined when the RSX executive was
assembled, no tasks -should be built in SHR mode.

VII-6-11

Each Shared COMMON
following formats:

Block

specified

Form 1:

name (offset, size)

Form 2:

name (size)

Form 3:

name [, ••• ]

according

one

the

[, ••• ]

In these formats, name identifies a COMMON Block declared by the task.
In Form 1, offset is added to the base of ESAS to obtain the base
address of the COMMON named. The offset from ESAS can be negative but
cannot cause a shared COMMON to start outside of the task's SASe
For
example, it is possible to set the offset equal to -400 octal.
This
would cause the base of the named COMMON to coincide with the base of
SASe Offset and size should be specified as octal numbers.
Size
specifies the length in words, of the shared CO~~ON Block. Note that
size also specifies the base address of the next
shared
COMMON
relati ve to the base of the current shared COr~ON. The only exception
to this rule is that a specification made using Form 1 will
override
all previous specifications. The value of size must be a
positive
octal number and cannot direct TKB to allocate space
for a
shared
COMMON outside SASe Form 3 is simply a short form for Form 2 with
a
size of zero, (e.g., "COl-1," means "COM(O) ,"). The use of
each
of
these forms is apparent from the following example.
Shared COMMON Definition

COr-1MON Base

COMl(-400, 1000) ,

SAS = ESAS -

CO~12 (100) ,

SAS + 1000 = ESAS + 400

COM3,

SAS + 1100 = ESAS + 500

COM4,

SAS + 1100 = ESAS + 500

COl-iS (0 , 20 0) ,

SAS + 400 = ESAS

COM6(100) ,

SAS + 600 = ESAS + 200

COM7(2000, 0)

SAS + 2400 = ESAS + 2000

400

If forms 2 or 3 are used prior to form 1, the base of the first shared
named is made to coincide with the base of ESAS.

COI~ON

The user can enter as many shared COMr·10N Blocks as are declared in the
task by inserting commas between entries. All shared crn1MONs must lay
within SASe Those COMHON Blocks in the user's program which are not
declared to be shared are allocated within the task's virtual
partition wall and are referenced only by that task.
Blank COMMON
cannot be shared.

VII-6-12

Since the Task Builder does not allocate space for shared CO~1MONs
within the task's virtual partition space, the actual size of any
shared CONl.'l.iON is irrelevant. Hence, when calculating ':.he size of a
shared COHl:10N to be printed in load maps, TKB assumes that its top
address coincides \vi th the top of ESAS.

6.3.6

Define Resident Code

Here the user lists the names of files containing reiocatable binary
units of routines to be resident throughout a run and the names of
library routines (flagged by library indicators (I»
to be resident
throughout a run. These names are listed in the following format:
Form:

name [, ••• ]

Where:

name is the name of a file or of a library
routine (see above) to be resident throughout
a run

Example:

DEFINE RESIDENT CODE
>ZZZ.12,ILIBl

RSX transfers initial control to the entry point of the first resident
routine relocated, i.e., the first routine of the first file listed,
unless resident code consists exclusively of library' rou~ines.
The
response~o DEFINE RESIDENT CODE must be at least one ~ame.
6.3.7

Describe Links and Structures

Here the user describes the overlay structure in terms of LINK names.
When a LINK is to qonsist of only Qne external component, the name of
the file containing the external component may be used as the LINK
name.
However, when a LINK is to consist of more than one external
component, the LINK must be named and defined.
In the DOS system, the supervision of core overlays.is handled by a
system program called EXECUTE, which exists as a separate file from
the user's XCT file built by CHAIN. In XVM/RSX, the equivalent
of
EXECUTE is a subroutine called EXU.13 (the number may vary). lihenever
the Task Builder constructs a file with qverlays, it expects to find
EXU.lJ in the system library, .LIBRX or .•'LIBFX. If the appropriate
library file is not present on LUN-lO when an overlay task is being
built, an error message will be printed during the expansion of the
resident code:
'
TKB-I/O ERROR LUN 10 13
Code 13 means that the file was not found.

VII-6-13

6.3.7.1 LINK Definitions - Each LINK definition requires one line
command input in the following format:

Form:

name =

rxtfile [, ••• 1 !II [intfilel [, ••• 1 }
[extfile 1 [, ••• ] [/1 intfile [, ••• 1

Where:

name is the name of the LINK
extfile is the name of an external LINK
component
intfile is the name of an internal LINK
component

Example:

Define the LINK named ABC to consist of
external components SUBI and SUB2 and
internal components SUB3 and SUB4:
DESCRIBE LINKS & STRUCTURES
>ABC=SUBl,SUB2/SUB3,SUB4

A LINK definition is a list of the names of files which contain the
relocatable binary units that comprise the LINK components. The
individual file names listed are separated by commas (,)~ the two
types of LINK components which may be used (external and internal) are
separated within the definition by a slash (I). All external LINK
component names must be listed before (to the left of) the slash
separator~
all internal LINK components must be listed after (to the
right of) the slash. External LINK components are accepted only from
files with names which match the external component name (i.e., GLOBAL
symbol definition).
Rules for defining a LINK:
1.

A LINK may not be a component of another LINK.

The names of the components of a LINK may not be used as LINK
names.
When a LINK consists of only one component, the
component's file name may be used as the LINK name in the
overlay structure description, but not in a LINK definition~
i.e., it is not necessary to define a single component LINK
but, if defined, the LINK name cannot be the component name.

A file name used in the resident code description
used in a LINK definition.

A file name preceding a slash may be used only once.

A file name following a slash may
definitions (following a slash).

VII-6-14

used

cannot

other

LINK

6.3.7.2 over~ay structure Description - An overlay structure
is
described uS1ng the names of defined LINKS, or the names of files
containing LINK. components and the operators colon (:) and comma (,).
This description has the following basic format:
Form:

overlaid: [ ••• ]overlaying[, ••• ]

Where:

overlaid is the name of the part of the
structure to be overlaid (a defined LINK
or a file containing a LINK component)
overlaying is the name of the part of the
structure to overlay overlaid (a defined
LINK or a file containing a LINK component)

Example:

SUB2 overlays SUBl:
DESCRIBE LINKS & STRUCTURES
SUB1:SUB2

The following rules apply:
1.

A line is an independent statement
right.

processed

from

left

A colon signifies "is overlayed by."
loading order, is implied.

Core

mapping,

but

A comma signifies "and." The following:
SUB1:SUB2
SUB2:SUBl,SUB4
indicates that SUBl is overlayed by (uses the same core as)
SUB2, SUB2 is overlayed by SUB3 and SUB4, but SUBl and SUB4
do not overlay each other.

A colon operator may not be used in a line after a comma has
been
used.
This
restriction
prevents the following
ambiguity:
SUB2:SUBl,SUB4:SUBS
The above line is rejected because it is not clear whether
SUBS overlays SUB3 or SUB4 or both.
All four of the
following examples are acceptable:
SUB2:SUBl,SUB4
SUB4:SUB5

SUBS uses the same core as
SUB4 but not the same core
as SUBl.

SUB2:SUBl,SUB4
SUB3:SUB5

SUBS uses the same core as
SUB3 but not the same core
as SUB4.

VII-6-l5

SUB2:SUBS:SUB3,SUB4

SUBS uses the same core as
SUB3 and SUB4. SUB3 and
SUB4 are loaded individually (if nonresident) as
called.

LINK=SUB3,SUB4
SUB2:LINK:SUBS

SUBS uses the same core as
SUB3 and SUB4. Both SUB3
and SUB4 are loaded (if
nonresident)
whenever
either is called.

A LINK name may appear only once preceding a colon
once following another colon.

If a LINK name is used twice, it must be used
colon before being used before another colon.

Several LINKs overlaying each other may
statement, as in the following:
SUBl:SUB2:SUB3,SUB4

and

only

following

defined

a
one

Core
mapping,
but
no
loading order, is implied.
This is a short method of
defining the same overlay
structure as in the first
example, under rule 3.

Although rules 5 and 6 may appear restrictive, they do not limit the
user's description of an overlay structure, but do prevent mUltiple
description of the position of a LINK in an overlay structure. A LINK
may be both overlayed and overlaying, and it may not be possible or
convenient to describe both conditions by using the LINK name only
once, as follows:
SUBl:SUB2:SUB3

SUB2 is overlaying SUBl and is
by SUB3.

overlayed

Therefore, when a LINK is both overlaying and overlayed, its LINK name
may be used twice, but the LINK(s) overlayed by it must be described
before the LINK(s) by which it is overlayed, as follows:
SUB2:SUB3,SUB4
SUB3:SUBS

SUB3 overlays SUB2.
SUB3 is overlayed by SUBS.
NOTE

The description of an overlay structure
only defines a desired core mapping,
i.e., stating that SUBl is overlayed by
SUB2 means that both are to be relocated
to the same core and cannot coreside,
but does not ~ply that SUBl must be
called before SUB2. There is no imposed
order in which routines must be called,
nor is there restriction of the routines
callable by any routine.

VII-6-16

6.3.8

Completion of Dialogue

After all of the previously described characteristics have been
supplied by the user and accepted by TKB, the program computes the
amount of core required by the task and prints it in the format:

•

XVM/RSXV1B

VII-6-17

September 1976

Form:

start-end size

Where:

start is the octal starting address of the task
in the core partition identified above
end is the last filled octal location in this
partition
size is the octal size of the task

Example:

CORE REQ'D
40000-46266 06267

TK8 terminates interaction with the user by returning control to the
MULTIACCESS Monitor.
When in control, the Monitor requests another
function by typing:
TDV>

6.4

CONVERSION TO XVM/RSX

Builder
differs
from
XVM/RSX user interaction with the Task
interaction with previous versions of the Task Builder. All user
FORTRAN programs developed under previous versions of RSX must be
recompiled and rebuilt by the Task Builder to enable them to run under
XVM/RSX. Similarly; assembly language programs should be reassembled
and rebuilt for XVM/RSX operation.

6.5

BTK:

BASIC TASK BUILDER

BTK, the Basic Task Builder, closely resembles TKB, but requires
different
input.
BTK
is
useful for building simple tasks,
particularly for batch-processing.
BTK is invoked in the following
way:
Form:

BTK name[,name ... ]V

Where:

name is the name of the task to be built

Example:

TDV>BTK SCAN,SCSUB

BTK assumes the following options and conditions (refer to Table 6-1):
NRM
FP or NFP
PGR
priority of 400
TDV partition
The resident code that has been entered
BTK generates a load map.
removes trailing spaces
Monitor.

XVM/RSX VIB

As an aid to the system, the batch handler
from card images passed to the MULTIACCESS

VII-6-I8

September 1976

6.6

ERROR MESSAGES

Tables 6-2 and 6-3 list possible
error
messages
and
their
implications.
Messages regarding command string errors immediately
follow the erroneous logical line. The command is ignored and must be
retyped.
The > prompt follows the message if the error is recoverable.
When
possible, the faulty character or name is output after the error
message. If the error is not recoverable, TKB exits to TDV after
typing the message.
Below is a sample sequence of miscellaneous recoverable errors:
TDi..»TI<B

TASK BUILDER XVM V1AOOO
:> r:: (.~l F;.: ~ ~:) z:
r',

Uf'.JF::FCOGN I ZED B'y'··'i.f:()i... .......

}::':\I;:~

SPECIFY DEFAULT PRIORITY

- IMPROPER PRIORITY
~3P[CIF'{

DEF/'IU!...T PF:IDPIT"'(

>- ~:S ()()
DESCRIBE PARTITION
>BLK1- PAR1ITION NOT IN SYSTEM
DEFINE REBIDENT CODE

:> L.. :< :!. :::: :.:;; Un:i. ;' F.::.::

IMPROPER BREAK CHA~

:> 1...!-':; j. :; L.l< :::::
~

NAME USED LEFT OF COLON TWICE -- LKl

VII-6-19

Table 6-2
Messages Produced by Recoverable TKB Errors
Error Message

Meaning

t UNRECOGNIZABLE SYMBOL

Unrecognizable
command string

tRES ROUTINE REQ'D

No resident routine
declared

tLINK NAME USED PRV

Name used previously

tNAMELENGTH ERR

Legal name has 1-6 characters

t IMPROPER BREAK CHAR

Break character used incorrectly

tINTERNAL NAME REPEATED IN LINE

Internal LINK component name
used more than once within
LINK

tEXTERNAL NAME USED PRV

External LINK component name
used previously within overlay
system

tCOMPONENT NAME USED AS LINK NAME

Name of LINK component used as
name of a LINK

tLINK DEF WITHIN OVERLAY
DESCRIPTION

LINK definition within overlay
description

tCOLON MUST FOLLOW FIRST
LINK NAME

Colon missing after first LINK
name

tMORE THAN ONE LINK OVERLAYED

DIRECTORY

Form:

NEW [ DIRECTORY] 'iJ

Example:

TDV>NEW
NEW DIRECTORY ON DECTAPE UNIT 4
TDV>

typing

command

INPUT/OUTPUT AND TASK-BUILDING

The NEW DIRECTORY TDV Function Task is assigned Task name NEW... at
Task-Building time.
This Task can be built to run in either USER
(protected and relocated) or EXEC
mode.
It
expects
LUN-13
(recommended dedicated terminal) to receive error and confirmation
messages and LUN-19 for DECtape output.

12.3

ERROR MESSAGES

Table 12-1 lists possible error messages and their implications.
messages are printed in the following format:
TDV>NEW
NEW-message
TDV>

VII-12-1

All

Table 12-1
NEW DIRECTORY Error Messages
Error Message

Meaning

System Action

NEW-ATTACH ERR

ATTACH Directive to the
output device rejected;
possible that DECtape
I/O Handler not assigned
to the output LUN

Command ignored

NEW-NOT DECTAPE

output LON not assigned
to the DECtape I/O
Handler

Command ignored

NEW-DECTAPE ERR

Attempt to write out one
of the DEC tape directory
blocks failed

No further action

NEW-DETACH ERR

DETACH Directive to the
listing device rejected;
error does not occur unless operator reassigns
listing LON in midstream

Command ignored

VII-12-2

CHAPTER 13
INSTALL:

INSTALLING A TASK IN THE SYSTEM

The INSTALL TDV Function task (also an MCR function task) adds a task
to RSX previously built using the Task Builder. The Task Builder
creates a binary file as output. When the INSTALL TDV Function task
is invoked, the binary file is read from LUN-5 and recorded as an
absolute image on the disk. The existence of the task is recorded in
the System Task List.
This function task has been implemented for batch processing, not for
use under the MULTIACCESS Monitor. Its inclusion in the system (via
atypical system build procedures)
is permitted only to maintain
compatibility with existing user batch streams.

13.1

INVOKING INSTALL

The user can invoke INSTALL by
format:

typing

command

according

the

Form:

INS [TALL] name [p]V

Where:

name of task to be INSTALLed is a string of one
to six .SIXST characters
p is an integer in the decimal range 1 to 512,
specifying the task priority

Examples:

priority has been set dur ing task building:
TDV>INSTALL SCAN
TDV>
Priority was not set at task building time or
priority redefined here as 10:
TDV>INS SCAN 10
TDV>

The user can override a priority specified during task building by
indicating a priority in the INSTALL command line.. If a priority has
not previously been specified during task-building, an
INSTALL
priority is a required parameter.

XVM/RSX VIS

VII-13-l

September 1976

13.2

INPUT/OUTPUT AND TASK-BUILDING

The r:tmTAJJL Function Task is assign~r. task
name
rTf; • • •
at
Task-Building time.
This task must he built to run EXEC mode.
It
expects LUN-13
(recor~ended
dedicated terminal)
to receive error
messages and LU~-5 for binary filp, input.

13.3

ERROR MESSAGES

Table 13-1 lists possible error messages and their implications.
messages are printed in the following format:
TDV>INS
INS-message
TDV>

VII-13-2

All

Table 13-1
INSTALL Error Messages
Error Message

Meaning

System Action

INS-SYNTAX ERROR

Task name omitted or
priority invalid

Command ignored

INS-TASK ALREADY IN
SYSTEM

Task to be INSTALLed has
node in STL

Command ignored

INS-PARTITION NOT IN
SYSTEM

Partition name specified
at Task-Building time not
available

Command ignored

INS-TASK WOULD OVERFLOW PARTITION

Task to be INSTALLed too
large for available partition

Command ignored

INS-OUT OF POOL

No nodes left in pool to
create new STL entry

Command ignored

INS-OUT OF DISK

No room left on the disk

Command Ignored

INS-INPUT CHECKSUM ERR

Error while performing
checksum processing

Command ignored

INS-INPUT PAR ERR

Error while performing
parity checking

Command ignored

INS-SYS COM BLK ERR

INSTALL needs system common
block not currently in
system

Command ignored

INS-READ ERR ON LUN-S

Error in reading binary
file from LUN-S

Command ignored

INS-DISK ERR

Error while performing
disk get or allocate operation

Command ignored

INS-NO DEFAULT PRIORITY

Priority not specified in
INSTALL command, and no
priority included at TaskBuilding time

Command ignored

INS-FILE NOT FOUND ON
LUN-S

Binary file not available
for input from LUN-S

Command ignored

INS-RELOCATION HARDWARE NOT AVA

No relocation hardware
available on machine

Command ignored

INS-FLOATING POINT
HARDWARE NOT AVA

No floating-point hardware
available on machine

Command ignored

VII-13-3

CHAPTER 14
REQUEST:

REQUESTING TASK EXECUTION

The REQUEST TDV Function task (also an MCR function task) REQUESTs the
execution of a task at a specified software priority.
Actual time of
execution depends on task priority and partition availability.
This function task has been implemented for batch processing, not for
use under
the MULTIACCESS Monitor.
Its inclusion in the system (via
atypical system build procedures)
is permitted only to maintain
compatibility with existing user batch streams.
Tasks requested by this TDV function will not execute under control of
the MULTIACCESS Monitor.
14.1

INVOKING REQUEST

The user can invoke REQUEST by
format:

typing

command

according

Form:

REQ [UEST] name [p]V

Where:

name of task REQUESTed is a string of one to
six .SIXBT characters
p is an integer in the decimal range 1 to 51,
specifying the task priority

Examples:

Priority has been set during task building or
installation:
TDV>REQUEST SCAN
TDV>

the

Priority is redefined here at 50:
TDV>REQ SCAN 50
TDV>
The priority that has been specified during task building
or
installation can be overridden when the task is REQUESTed.
If a new
priority is not included in the command line, the task runs at the
previously specified default priority.
14.2

INPUT/OUTPUT AND TASK BUILDING

The REQUEST TDV Function task is assigned task name REQ...
at
task-building time. This task can be built to run in either user mode
(protected and relocated)
or exec
mode.
It
expects
LUN-13
(recommended dedicated terminal) to receive error messages.
XVM/RSX VIB

VII-14-1

September 1976

14.3

ERROR MESSAGES

Table 14-1 lists possible error messages and their implications.
messages are printed in the following format:

All

TDV>REQ
REQ-message
TDV>
Table 14-1
REQUEST Error Messages
Meaning

System Action

REQ-SYNTAX ERR

Task name omitted or
priority invalid

Command ignored

REQ-TASK NOT IN SYSTEM

STL node for REQUESTed
Task cannot be found

Command ignored

REQ-TASK ALREADY
ACTIVE

REQUESTed Task is
currently active

Command ignored

REQ-TASK DISABLED

Task has been disabled
and is unavailable

Command ignored

REQ-POOL EMPTY

No nodes left in pool to
create new CKQ entry

Command ignored

REQ-PART LOST

Partition in which Task is
to run has been lost
because of reconfiguration

Command ignored

Error Message

VII-14-2

CHAPTER 15
REMOVE:

REMOVING A TASK FROM THE SYSTEM

The REMOVE TDV Function task (also an MCR function
inactive task from the system.
If the user
reinstall a task, he must REMOVE it first.

task)
deletes an
plans to alter and

This function task has been implemented for batch processing, not for
use under the MULTIACCESS Monitor. Monitor. Its inclusion in the
system (via atypical system build procedures)
is permitted only to
maintain compatibility with existing user batch streams.

15.1

INVOKING REMOVE

The user can invoke REMOVE
format:

15.2

typing

command

according

Form:

REM [OVE] name"

Where:

name of task to be REMOVEd is a string of one
to six .SIXBT characters

Example:

TDV> REMOVE SCAN
TDV>

the

INPUT/OUTPUT AND TASK BUILDING

The REMOVE TDV Function task is assigned task name REM...
at
task-building time. This task must be built to run in exec mode. It
expects LUN-13
(recommended dedicated terminal)
to receive error
messages.

15.3

ERROR MESSAGES

Table 15-1 lists possible error messages and their implications.
messages are printed in the format:

All

TDV> REM
REM-message
TDV>

XVM/RSX VIB

VII-1S-l

September 1976

Table 15-1
REMOVE Error Messages
Error Message

Meaning

System Action

REM-TASK ACTIVE

Task to be REMOVEd
currently active

REM-SYNTAX ERR

Task name omitted

Command ignored

REM-TASK NOT IN SYSTEM

STL node Eor task to be
REMOVEd cannot be found

Command ignored

REM-DISK ERR

Error while performing
disk GET operation

Command

REM-ALLOCATE ERROR

Error while performing
disk ALLOCATE operation

Command ignored

REM-TASK HAS
MULTIPLE STL
ENTRIES

Disk space allocated to
this task
cannot be
deallocated at this time

Command ignored

XVM/RSX VlB

VII-lS-2

Command ignored

i~nored

September 1976

CHAPTER 16
MOUNT:

LOGICALLY MOUNTING A DISK

The MNT TDV Functions task (also an MCR function task) specifies UFOS
for all LUNs assigned to the named disk where no UFO specification has
previously been made.
For additional information, refer to the
documentation on the MNT MCR Function task in Part IV of this manual.
This function task is not recommended for use under the MULTIACCESS
Monitor.
Its inclusion in the system (via atypical system build
procedures) is permitted only to maintain compatability with existing
user batch streams.

16.1

INVOKING MOUNT

The user can invoke MOUNT by typing a command according to the format:

16.2

Form:

MNT Rnm UFDV

Where:

Rn is disk type: RF, RP or RK
m is a valid disk unit number
UFO is a valid three-character user file
directory

Example:

TDV>MNT RP3 ABN
TDV>

INPUT/OUTPUT AND TASK BUILDING

The MOUNT TDV Function task is assigned task name MNT...
at
task-building time. This task must be built to run in exec mode. It
expects LUN-13 (recommended dedicated terminal)
to receive error
messages.

16.3

ERROR MESSAGES

Table 16-1 lists possible error messages and their implications.
messages are printed in the format:

All

TDV>MNT
MNT-message
TDV>
XVM/RSX VIB

VII-16-1

September 1976

Table 16-1
MOUNT Error Messages
Error Message

Meaning

System Action

MNT-ALLOCATION ERROR

Error while performing
disk ALLOCATE operation

Command ignored

MNT-DISK PUT ERROR

Error while performing
disk PUT operation

Command ignored

MNT-FORMAT ERROR

Invalid device name, unit,
or UIC

Command ignored

MNT-DISK HAS NO PDVL
NODE

PDVL node for specified
disk cannot be found

Command ignored

MNT-DEVICE IS NOT A
DISK

Device name does not correspond to a disk in the
RSX system

Command ignored

MNT-ILLEGAL TO MOUNT
THE SYSTEM DISK

Device name corresponds to
the system disk

Command ignored

MNT-DISK NOT DISMOUNTED

Specified disk has not
been dismounted since last
mount

Command ignored

MNT-DISK GET ERROR

Error while performing
disk GET operation

Command ignored

VII-16-2

CHAPTER 17
DISMOUNT:

LOGICALLY DISMOUNTING A DISK

The DSM TDV Function task (also an MCR function task) dismounts a user
disk and, therefore, disables all file-oriented I/O addressed to the
disk. For additional information, refer to the documentation on the
DSM MCR Function task in Part IV of this manual.
This function task is not recommended for use under the MULTIACCESS
Monitor.
Its inclusion in the system (via atypical system build
procedures) is permitted only to maintain compatability with existing
user batch streams.

17.1

INVOKING DISMOUNT

The user can invoke DISMOUNT by typing
forma t:

17.2

command

Form:

DSM RnmV

Where:

Rn is disk type: RF, RP or RK
m is a valid disk unit number

Example:

TDV>DSM RK6
DISK IS READY FOR DISMOUNTING
TDV>

according

the

INPUT/OUTPUT AND TASK BUILDING

The DISMOUNT TDV Function task is assigned task name DSM...
at
task-building time.
This task can be built to run in exec mode. It
expects LUN-13 (recommended dedicated terminal)
to receive error
messages.

17.3

ERROR MESSAGES

Table 17-1 lists possible error messages and their implications.
messages are printed in the format:

All

TDV>DSM
DSM-message
TDV>

XVM/RSX VIB

VII-17-1

September 1976

Table 17-1
DISMOUNT Error Messages
Meaning

System Action

DSM-FORMAT ERROR

Invalid device name or
unit

Command ignored

DSM-DISK HAS NO PDVL
NODE

PDVL node for specified
disk cannot be found

Command ignored

DSM-DEVICE IS NOT A
DISK

Device name does not correspond to a disk in the
RSX system

Command ignored

DSM-ILLEGAL TO DISMOUNT THE SYSTEM
DEVICE

Device name corresponds to
the system disk

Command ignored

DSM-DEVICE NOT MOUNTED

Disk to be dismounted is
not currently mounted

Command ignored

DSM-DEVICE IS IN USE

Specified disk is currently being used for I/O

Command ignored

DSH-HA.RK TIHE ERROR

Error encountered while
marking time until all
open files are closed

Command ignored

Error Message

.VII-17-2

This page intentionally left blank.

XVM/RSX VIB

VII-lS-l

September 1976

This page intentionally left blank.

XVM/RSX VIB

VlI-lS-2

September 1976

CHAPTER 19
CONSTRUCT:

STORING A TASK ON A USER DISK

The CONSTRUCT TDV Function task (also an MCR function task)
adds a
task to RSX previously built by the Task Builder. When CONSTRUCT is
invoked, the binary file is read from LUN-5.
Unlike the INSTALL
function, however, the task core image is stored in a created file on
a disk, not simply in allocated space on the system disk.
Because
space on the user disk is allocated by the disk file handler, a LUN
that specifies the disk on which the created file is to reside must
usually be included in the CONSTRUCT command.
Unlike INSTALL,
CONSTRUCT does not affect the System Task List in any way.

•
19.1

INVOKING CONSTRUCT

The user can invoke CONSTRUCT by typing a
format:

according

CON [STRUCT] name [LUN]V

Where:

name of task to be CONSTRUCTed is a
string of one to six .SIXBT characters
LUN is an integer representing a logical
unit number currently associated with
a disk (the default value is decimal
14)
TDV>CON SCAN 16
TDV>

the

Form:

Example:

19.2

command

INPUT/OUTPUT AND TASK BUILDING

The CONSTRUCT TDV Function task is assigned task name CON...
at
task-building time. This task can be built to run in either user mode
(protected and relocated) or exec
mode.
It
expects
LUN-13
(recommended dedicated terminal) to receive error messages and LUN-5
to be assigned for binary file input.

XVM/RSX VIB

VII-I9-1

September 1976

19.3

ERROR MESSAGES

Table 19-1 lists possible error messages and their implications.
messages are printed in the format:

All

TDV>CON
CON-message
TDV>
Table 19-1
CONSTRUCT Error Messages
Error Message

•
•

Meaning

System Action

CON-SYNTAX ERROR

Task name or LUN omitted
or invalid or out-of-range
LUN

Command ignored

CON-CREATE ERR

Error while performing
create operation

Command ignored

CON-READ ERR

Error while performing
READ operation

Command ignored

CON-DISK ERR

Error while performing
disk GET or ALLOCATE
operation

Command ignored

CON-FILE NOT FOUND

Binary file not available
on LUN-5

Command ignored

•

XVM/RSX VIE

VII-19-2

September 1976

This page intentionally left blank.

XVM/RSX VIB

VII-20-1

September 1976

This page intentionally left blank.

XVM/RSX V1B

VII-20-2

September 1976

This page intentionally left blank.

XVM/RSX VIB

VII-20-3

September 1976

This page intentionally left blank.

XVM/RSX VlB

VII-20-4

September 1976

CHAPTER 21
QUEUE:

QUEUING A BATCH JOB

The QUEUE TDV Function task (also an MCR function task)
informs the
batch processor that a job is ready to be run, whether or not the
batch handler is in core. The user can specify the name of the job to
be queued, the LUN from which it comes and a series of job
characteristics, including:

21.1

•

Maximum time that the job can run (in minutes)

•

Class at which the job can run

•

Memory use

•

Use of sequencing (run in order of submission)

•

Whether the job requires operator availability

•

Whether QUEUE expects to find the job on the specified device
a t this time

•

Whether the job file should be deleted after the job runs

•

Use of hold mode

•

Whether the job is to be forced

•

INVOKING QUEUE

Job characteristics can be delimited in the command string by one or
more spaces, commas or both.
The following examples show various
forms of delimited parameters. The user can invoke QUEUE by typing a
command according to the format:

XVM/RSX VIB

VII-2l-1

September 1976

•I

Form:

QUE[OE]
[name]
[LUN]
[T=time]
[C=class]
[M=memory]
[SEQ]
[OPR]
[NCK]
[DEL]
[HLD]
[STK]
[FRC]V

Where:

name of task to be queued is a string of one
to six characters (first character
must be
i1
alphabetic). E..x.-r ~U"i"'" 13£ ":::ro6
LUN is an integer representing a logical unit
number currently in the system
time is an integer in the decimal range 1 to
1023, representing the maximum number of
minutes that the job can run
class is an integer in the decimal range 0 to
7

memory is an integer in the decimal range 1
to 128, representing memory use (in K)

I
Examples:

TDV>QUE COMPIL
TDV>QUE NAMX 15 SEQ C=2
TDV>QUE SCAN 5 T=C C=3 M=28 SEQ SPN
'rOV>QUE 14 NCK

All parameters of
however, a name
reasons:

the QUEUE command are optional.
In practice,
or LUN is often specified for one of the following

The default LUN is LUN-17;
usually assigned to the disk.
Specification of an explicit LUN is necessary to override
this default.

The name can be omitted if the LUN from which it comes is not
associated with a file-oriented device.
In the example:
TDV>QUE 14
14 is associated with the card reader
requires no explicit name definition.

and

the

command

If the first character of a QUEUE command line is numeric, it
is assumed that the name has been omitted and the number
represents the LUN of a non-file-oriented device.
The user
should ensure that names included in the command line begin
with an alphabetic character.

The HLD option causes QUEUE to queue the job, but to leave it in the
hold mode until the operator releases it. The STK option causes QUEUE
to stack the job by copying it into a
temporary file on disk and
queuing it. STK implies deletion after execution.

•

If the file is on DEC tape or disk and if NCK and STK have not been
specified, QUEUE opens the file,
reads the JOB record and outputs
errors, if necessary.
If a memory size is specified and not enough
core is available to run, the job waits until the TDV partition is
large enough.

XVM-RSX VIB

VII-2l-2

September 1976

Job information defaults are:
Parameter

21.2

Default

Time specified in the job file

Zero

Core available at the time the job is run (0)

SEQ

No use of sequencing

OPR

Job does not require operator availability

NCK

Job is on the specified device at this time

DEL

Preserve the job file after the run

HLD

Run the job as soon as priority permits

STK

Do not copy the job file to the disk

Do not force

•
•

INPUT/OUTPUT AND TASK BUILDING

The QUEUE Function task is assigned task name QUE ••• at task building
time.· This task can be built to run in either user mode (protected
and relocated)
or exec mode.
It uses LUN-13 to receive error
messages.

21.3

ERROR MESSAGES

Table 21-1 lists possible error messages and their implications.
messages are printed in the format:

All

TDV>QUE
message
TDV>

XVM/RSX VIB

VII-21-3

September 1976

Table 21-1
QUEUE Error Messages
Error Message

Meaning

System Action

FORMAT ERROR IN COMMAND

One or more
nonexistent options
in conunand line

Command ignored

ILLEGAL VALUE FOR ARGUMENT

Illegal T,C,M, or U
argument

Command ignored

CANNOT INPUT FROM
DEVICE SPECIFIED

Nothing to input
from that LUN

Command ignored

NEED FILE NAME FOR
THIS DEVICE

File-oriented LUN

Command ignored

FILE NOT FOUND

File cannot be found

Command ignored

Error during READ
operation

Command ignored

JOB RECORD MUST BE
FIRST LINE

First line not JOB
record

Command ignored

INCORRECT JOB LINE
FOLLOWS

Incorrect time limit
not
three digits or not
in correct sequence

COIn.'"nand ignored

IMPOSSIBLE TO
QUEUE JOB

Exec or empty
nodes unavailable

Command ignored

TDV COMMAND
TRANSFER ERROR

Error in TDV
Command transfer

Command ignored

READ

ERROR

specification~

VII-21-4

CHAPTER 22
aDT:

aCTAL DEBUGGING TECHNIQUE

The aDT TDV Function task allows users to debug tasks with an "octal
debugging technique
under XVM/RSX.
It permits users to start and
stop tasks, examine and modify task registers and locations within the
task partition, set and remove breakpoints within the task, and
proceed with task execution after a breakpoint has been reached.
aDT
allows the user to define symbols for program addresses so that
command parameter inputs can be given as either octal numbers or
previously defined symbols. Furthermore, aDT monitors task progress
to ensure that the task does not permanently prevent other system
activities if it enters an infinite loop.
II

Because of the way that breakpoints are handled,
restrictions apply to tasks debugged using aDT:
1.

the

Tasks can have no overlays. If the user debugs a task with
overlays using ODT, he should use extreme caution so that no
breakpoints are set within a link.
address

following

Tasks must be built in user mode. If the user attempts to
debug an exec-mode task with aDT, the error message "EXEC
MODE" is printed and ODT is reinitialized.

virtual

I
I

(autoincrement

Tasks cannot modify
register X17).

Tasks cannot modify virtual addresses 0 to 3.

Tasks cannot modify the instruction at a breakpoint.

The last four restrictions are not checked by ODT. If the user task
violates these restrictions, system integrity is not compromised, but
the user task will probably fail to run correctly.

•

XVM/RSX VIB

VII-22-1

September 1976

•

22.1

INVOKING ODT

The user can invoke aDT by typing a command according to the format:

22.2

Form:

ODT name [ LUN]\?

Where:

name of a CONSTRUCTed task
image is a string of
one to six .SIXBT characters
LUN is an integer representing the
logical unit number on which
the file resides (the default
value is decimal 14)

Example:

TDV>ODT SCAN 16
TDV>

DEBUGGING WITH ODT

When ODT begins execution, it prints a header message and attempts
to
fix
the specified task
in core.
If
the
task can be fixed, ODT
requests additional commands by typing the prompter:
ODT>

If the task cannot be fixed in its partition
prints the message "FIX ERR" and exits.

In response to the ODT prompter, the user can enter
following commands:

for

any

reason,

anyone

ODT
the

Command

Function

OPEN
START
EXIT
DEFINE
SET
REMOVE
CONTINUE

Opens a register or memory location
Starts the task
Exits and aborts the task
Defines a symbol
Sets a breakpoint
Removes a breakpoint
Continues task execution after
reaching a breakpoint
Restarts the task at some location
Reloads the task with symbols and
breakpoints
Dumps the task partition into a
created file on disk
Decodes the opened memory locations
or stops decoding the opened memory
locations
Prints all registers when the task
has reached a breakpoint

RESTAR'r
RELOAD
DUMP*
DECODE*
REGISTERS*
Each of these
paragraphs.

commands

described

detail

the

following

* Legal only if ONEPLS was defined

XVM/RSX VIB

VII-22-2

September 1976

22.2.1

OPEN

The OPEN command examines and optionally modifies the contents of task
registers or locations within the task partition. The format of this
command is:
ODT>OPE[N] nnnnnn
where nnnnnn is an address relative to the base of the task partition.
The nnnnnn specification can be a symbol or one of the following
registers: $AC, $MQ, $XR, $LR, $LINK or $XIO TO $XI6.

•

OOT prints the contents of the location or register and waits for a
response.
If a value (octal only) is then given as a response, that
value replaces the former contents.
If only a
terminator is typed,
aOT does not modify the current contents of the register or location.
If the response is terminated with an altmode, a new command is
requested.
If the response is terminated with a carriage return, the
next location is opened (unless a register was specified).
If a
register was specified, a new command is always requested.

If a new value for the link is to be entered, only bit 17 of the octal
word typed is relevant.

This command is legal any time, but registers can be
the task is at a breakpoint.

22.2.2

opened

only

•

START

The START command begins execution of the task
format of this command is:

being

debugged.

The

already

been

ODT>STA[RT]
This command can be used
started.

22.2.3

only

the

task

has

not

EXIT

The EXIT command terminates the debugging
task. The format of this command is:

session

for

particular

ODT>EXI[T]
The EXIT command causes the task to abort.
time.

XVM/RSX VIB

VII-22-3

any

•

September 1976

This command is legal

22.2.4

DEFINE

The DEFINE command defines a symbol. Once a symbol has been defined,
it can replace program addresses indicated in octal notation in other
cOffimand string inputs. The format of this command is:
ODT)DEF [INE]

xxx=nnnnnn

where xxx is a one- to three-character symbol and nnnnnn is any octal
number.
After the first three characters of a symbol are input,
subsequent characters are ignored. Unlike other commands, nnnnnn for
this command cannot be a symbol.
This command is legal any time.

22.2.5

SET

The SET command enters a breakpoint into the task at some location
specified. When the executing task reaches a breakpoint, its progress
is stopped prior to the execution of the instruction at which the
breakpoint is SET. The format of this command is:
ODT)SET nnnnnn
•

where nnnnnn is an address relative to the base of the task partition,
and can be a symbol.
This command is legal any time.

22.2.6

REMOVE

The REMOVE command removes a breakpoint from the task.
the SET command. The format of this command is:

It complements

ODT)REM[OVE] nnnnnn
•

where nnnnnn is an address relative to the base of the task partition,
and can be a symbol.
This command is legal any time.

XVM/RSX VIB

VII-22-4

September 1976

22.2.7

RESTART

'rhe RESTART command causes the task to be started at the loca tion
specified once that task has reached a breakpoint. The format of this
command is:

•

ODT)RES[TART] nnnnnn
where nnnnnn is an address relative to the base of the task partition,
and can be a symbol.

•

This command is legal only if the task is at a breakpoint.

22.2.8

RELOAD

The RELOAD command instructs ODT to reload the task image
(i.e.,
refresh the task partition with a new copy of the task). Breakpoints
and symbols defined when this command is issued are retained, but the
contents of user-modified locations are lost. The format of this
command is:

ODT)REL[OAD]
This command is legal any time.

22.2.9

CONTINUE

The CONTINUE command is used to resume task execution
breakpoint has been reached. The format of this command is:

once

ODT)CON [TINUE]
This command is legal only if the task is at a breakpoint.

22.2.10

REGISTERS

The REGISTERS command is legal only if the assembly
was defined. The format of this command is:

parameter

ONEPLS

ODT) REG [ISTERS]
This command prints the contents of the AC, MQ, XR, LR and link.
This command is legal only if the task is at a breakpoint.

22.2.11

DECODE

The DECODE command sets a flag to tell the OPEN command whether it
should print the opcodes of opened locations as well as their
contents. The format of this command is:
ODT)DEC[ODE] string

XVM/RSX VlB

VII-22-5

September 1976 I

Where string is either "ON"

or "OFF"

If string is "ON", tne opcodes are decoded.
If string is
"OFF;',
the
opcodes are not decoded.
(No opcode decoding is the default mode of
operation for the OPEN command.) The DECODE command is valid only if
ONEPLS was defined when ODT was assembled.
This command is legal any time.

22.2.12

DUMP

The DUMP command is used to write an image of t;le task partition into
an RSX-created file on disk.
The file is named TSKNAM DMP, where
TSKNAM is the task name. The image of
the
task does not contain
breakpoints, but all breakpoints are restored whe~ the dumping process
is complete. This command is valid only if ONEPLS was defined when
lOOT was assembled. The format of this command is:
aOT>DUM[P]
This command is legal any time.

22.3

MONITORING TASK PROGRESS

Whenever a task has been started,
restarted or continued after a
breakpoint, ODT monitors its progress.
If the task does not exit or
reach a breakpoint within several seconds, ODT prints the task ATL
status and asks the user whether the task should be aborted.
If the
user types "NO'I, aDT resumes monitoring task progress.
If the user
types "YES", aDT reloads the task, aborting it in the process.
If the
task exits while aDT is monitoring its progress, the message "TASK HAS
EXITED" is printed. The task is then reloaded.

22.4

AN EXAMPLE aF ODT USE

The following listing gives an example of a task to be debugged with
ODT.
This program contains two errors
that will be found and
subsequently corrected using ODT. The program consists of a main
section and a single subroutine. The function of the main section is
to simulate input data and call the subroutine. The subroutine, which
is presumably used in another program, is intended to count the bits
that are set in the accumulator on entry to the subroutine.
It is
this subroutine that contains errors and can be debugged using ODT.
When the example program is
task built,
it is relocated so that
location 0 1n the listing corresponds to the base address of the
partition for this task plus 20 (octal).
The example program is listed on the following page:

XVM/RSX V1B

VII-22-6

September 1976

I
I
I
I
I
I
I

2
3

4
5

7
8
9

440000 A
000010 A

12
13
14
15
16
17
18
19

20
21

<
H
H

00000 R 200053 R
00001 R 060054 R
00002 R 200055 R
00003 R 100013 R
00004 r, 200056 R
00005 R 100013 R
00006 R 777777 A
00007 R 100013 R
00010 r, 750000 A
00011 r, 100013 R
00012 R 000054 R

LAC
JMS
LAC
JMS
LAW
JMS
CLA
JMS
CAL

23
24

26
27

~
~
~

28
29

30
31
32
33

34
35
36
37
38
39

40
41
42
43
44
45

AS GIVEN HERE~ THIS SUBROUTINE HAS TWO ERRORS.

IDX=ISZ
Xl0=10
I
START
LAC
DAC*

10
11

THIS PROGRAM IS INTENDED TO TEST THE SUBROUTINE 'ONECNT'
WHICH COUNTS THE 1 BITS IN THE AC ON ENTRY TO THE
SUBROUTINE.

I
I
I
I

00013 R 000000 A
00014 R 652000 A
00015 R 777756 A
00016 R 040051 R
00017 R 744000 A
00020 R 641002 A
00021 R 740010 A
00022 R 740400 A
00023 R 440052 R
00024 R 440051 R
00025 R 600021 R
00026 R 200052 r,
00027 R 060010 A
00030 r, 620013 R

IUSED IF INTENT IS TO INCREMENT ONLY
IAUTOINCREMENT REGISTER 10
(BUFF-l
(Xl0
(654321
ONECNT
(123456
ONECNT
-1

ONECNT
ONECNT
(10

IINITIALIZE Xl0
IUSE Xl0 AS A BUFFER POINTER FOR
ISTORING RESULTS.
IGET 1ST DATA WORD
IGO COUNT THE ONE'S
IGET 2ND DATA WORD
IGO COUNT THE ONE'S
IGET 3RD DATA WORD
100 COUNT THE ONE'S
IGET 4TH DATA WORD
IGO COUNT THE ONE'S
IEXIT

SUBROUTINE ONECNT -- COUNT THE ONE BITS IN THE AC ON ENTRY?
STORE RESULTS VIA Xl0

ONECNT

lOOP

0
LMQ
LAW
DAC
elL
lACQ
RAl
SNL
IDX
ISZ
JMP
lAC
DAC*
JMP*

-22

BITCNT
ICLEAR THE lINK
IRETRIEVE DATA WORD
ISHIFT BITS AND TABULATE ONE'S
ONES
BITCNT
LOOP
ONES
Xl0
ONECNT

00031 R
A
BUFF
.BlOCK
BITCNT 0
00051 R 000000 A
00052 R 000000 A
ONES
0
000000 A
.END
00053 R 000030 R *L
00054 R 000010 A *L
00055 R 654321 A *L
00056 r, 123456 A *L
SIZE=00057
NO ERROR LINES

ISAVE THE DATA WORD IN MQ
ISET UP A BIT COUNTER

IDONE WITH WORD?
INO -- CONTINUE
IYES -- STORE RESULT
IRETURN
IRESULTS BUFFER
IBIT COUNTER
lONE'S COUNTER

The following terminal output shows how ODT can be used to
subroutine in the example program:

onT V1BOOO
ODT>DEF BUF::::31
ODT>DEF BIT=::~51
ODT>DEF ONE=::52
(}DT>SET 24
ODT>SET 26
ODT>SET 30
ODT>SET 32
BRKPT AT 000024
ODT>OF'EN BlJF
000051 : 00001:L
000052 :101550
00005~5 : 60041:1.
ODT>OPEN ONE
000072 :000011
ODT>OF'EN BIT
000071 :000000
ODT>CONT
BRKPT AT ()OOO~~6

}

Set
breakpoints
at
all
subroutine return addresse:--; .

}

later

use

Open those locations that show
the results of the subrouti~e.
The first result is correct.

Open
subroutine
temporary
variables to check them. They
are OK so far.
-Continue task execution.
-A breakpoint has been reached at
location 6 (L2).
Check the results buffer and
subroutine temporary storage
locations. An error has been
found.
The temporary storage
}
location ONES must be zeroed
before counting.
-Reload the task
into
memory
keeping symbols
and breakpoints.
-Change loc~tion 17 from a CLL to
a DZM ONES.
-Start task execution.
-The first breakpoint has been
reached.

}

ODT>OF'EN BUF
000051 :000011
000052 :000022
000053 : 60041:1.
ODT>OPEN ONE
000072 :000022
ODT>RELOAD
ODT>OPEN :~7
000037 :744000 :140072
ODT>START
BRKPT AT 000024

XVM/RSX V1B

}

Define symbols for
in command inputs.

-St·lrt execution of the task.
+-A breakpoint has been reached
loca tion 4 (Ll).

ODT>STAI~T

ODT>OPEN BUF
000051 :000011
000052 :000011.
000053 :600411
ODT>OF'EN ONE
000072 :00001.1
ODT>CONT
BRKF'T AT 000030

the

+-Name program to be debugged.

TDV>ODT TEST

OIlT>OF'EN BUF
000051 :000011
000052 :101.550
000053 :6()0411
ODT>OF'EN ONE
000072 :000011
OIIT>CONT
BRKF'T AT 000026

debug

}

Check results.

They look OK.

-Continue task execution.
-The next breakpoint has
reached.
}

Check results again.

-Contlnue.
breakpoint
-Another
reached.

VII-22-8

has

been

OK.

been

September 1976

OIlT>OPEN BUF
000051 :000011
000052 :000011
000053 :000000
OIlT)RELOAII
OIlT>OPEN 42
000042 :740400 :741400
OIlT>OPEN 37
000037 :744000 :140072
OIlT>START
BRKPT AT 000024
OIlT)OPEN BUF
OOOO~l
:000011
000052 :101550 :
000053 :600411 :
OIlT)CONT
BRKPT AT 000026
OIlT>OPEN BUF
000051 :000011
000052 :000011
000053 :600411
OIlT)CONT
BRKPT AT 000030
OIlT)OPEN BUF
000051 :000011
000052 :00001:1.
000053 :000022
000054 :101635
000055 : 2042:1.7
ODT>CONT
BRKPT AT 000032
ODT>OPEN BUF
000051 :000011
000052 :000011
000053 :000022
0000~j4 : 000000
000055 :204217
ODT>OPEN $X10
777770 :000054
OnT>EXIT
Tnv>

22.5

Check results again.
Another
error has been found.
The
subroutine is counting cleared
bits instead of set bits.
+-Reload the task once again.
Change location 22 from an SNL
}
to an SZL instruction.
+-Enter previous correction.
+-Start task execution and check
the results at each breakpoint as
they are reached.
Use the same
procedures as above.

+-The final breakpoint has been
reached
and
the
subroutine
output looks fine.

+-Examine autoincrement register
10 to be sure that it points to
the correct location within the
data buffer. It does, so leave
ODT.

ERROR MESSAGES

Table 22-1 lists possible error messages and their implications.

XVM/RSX VlB

VII-22-9

September 1976

Table 22-1
aDT Error Messages

I
Message

Meaning

Routines Generating
Error Message

HINF ERR

HINF error on LUN-14

PUT ERR

ODT is unable to write
the task image to disk

DUMP

CREATE ERR

oo'r is unable to

DUMP

CREATE a file on
LUN-14
ILLEGAL

Registers cannot be
opened unless the task
is at a breakpoint

OPEN

BRDPT AT XCT

Illegal to have a
breakpoint at XCT
instruction

SET, OPEN

EXEC MODE*

Task is in exec mode

ODT

READ ERR*

Terminal read error

ODT INITIALIZATION,
COMMAND DISPATCH,
OPEN, MONITOR
ROUTINE

Violation of command
syntax

ODT INITIALIZATION,
COMMAND DISPATCH,
RESTART, SET,
REMOVE, OPEN,
DECODE

INITIALr~~rION

FIX ERR*

ODT is unable to FIX
the task

ODT INITIALIZATION,

TASK NOT IN STL*

Task specified is not
in the system**

ODT INITIALIZATION

WHAT?

unrecognized command

COMMAND

ALREADY STARTED

Task was previously
started

START

REQUEST ERR*

ODT is unable to
REQUEST the task

START

DIS~~TCH

(Continued)

I *Causes ODT to exit.
**This error should never appear unless the system list structure
been corrupted.

XVM/RSX V1B

VII-22-10

has

September 1976

Table 22-1 (Cant.)
ODT Error Messages

Message

Meaning

I
Routines Generating
Error Message

TABLE FULL

Breakpoint or symbol
table full

DEFINE, SET

ALREADY OEF I ~~e: I)

~reakpoint has already
been defined or set

SET

NOT AT A BRKPT

Task is not at a
breakpoint

RESTART, CONTINUE,
REGISTERS

NOT IN TABLE

Breakpoint is not in
the table

CONTINUE, REMOVE

ATTACH ERR*

ODT is unable to
ATTACH the terminal

ODT INITIALIZATION,
COMMAND DISPATCH,
MONITOR

TASK NOT IN ATL*

Task is deleted from
ATL

ODT INITIALIZATION,
CONTINUE

OU'f OF BOUNDS

Address is not within
the task partition
space

RESTART, SET,
REMOVE, OPEN

*Causes ODT to exit.

XVM/RSX VIB

VII-22-11

September 1976

CHAPTER 23
STATUS:

MULTIACCESS STATUS REPORT

The STATUS TDV Function task prints a status report of internal
MULTIACC~SS
information. This status information is intended for use
by the system manager and, in general, is not of interest to the TDV
user.

23.1

INVOKING STATUS

The user can invoke STATUS
format:

23.2

Form:

STA[TUS]V

Example:

TDV>STA
TDV>

typing

command

according

the

INPUT/OUTPUT AND TASK BUILDING

The STATUS TDV Function task is assigned task name STA...
at
task-building time.
This task is written in FORTRAN and should be
built to run in user mode (protected and relocated).
Output status
information is sent to LUN-16.
A sample STATUS report is listed below:

XVM/RSX VlB

VII-23-1

September 1976

TIIV>STr::}
MULTIACCESS STATUS REPORT 13-JUL-76
:1. ACTIVE USEi=H S)
TOTAL NUMBER OF USER(S) =
1
TOTAL NUMBER OF JOBCS) =
15
MEAN WAIT TIME IS O~OO SECONDS/JOB
ACTIVE TERMINAL NUMBERS ARE: 0
THERE ARE 198 (10) WORDS OF DYNAMIC STORAGE
OOOO()()"~OO:L ?7"7

006()OO'~'0077"77

O:L 4000·..·0 1 ~:)777
()22000 .... ()2~3·77·?
0;·5()OOO·..·031 '?T?
0:36000'-037"7T7

044000 .... 0457T7
0~:i2000·..·0~53777

060000-061777
066000,-0677"77
07 4000-07~57T7
Tnl»

T(")SI< SIZE HI~:)TOGi=;;i;~I~'j
o 002000-003777
o 010000-011777
():I. 60()0 .... O 1'7::?/'7
o 024000 .... 02!:5777
()
0320()O .... 03377"?
o 04()OOO .... 041 TT7
o 046000 ..··04 '7:.7'77
()
O~.:j40()() .... ()~j~57'77
o 062000 .... 06~~77"?
()
070000 .... 07:1. ,/'77
o 076000··.. 077·?77

,.:

()

o:i. :?OOO .... OJ. :::<,]'77

:1.

()

() ::.~ () (;c I) () .... () :::.~ 1 '~.") ';7 ',?

() ::.~ \~) () () () .... () ::.~ ~l )' ',? ::.:.t

()

034000 .... 03!::.i??·/
04;;.~()OO-04::~ 1'77
O~)OOOO""O!:i:l. '777
o~5 bO 0 0 .~. 0 !~; '7 "/ '7 7
() {:) -'1 () () () .....~) f.) !:5 :7 ';:., ~")

()

o
o
o
o
o
()

07 2000·..·0'?:3 7 '.1'-;:-'

-<+

o
()
I.)

()
()

:I. O()O 00 .... '.1'777 '77

The status report presents important
current
information
and
historical information compiled since TDV stqrted running. Current
information includes:
•

Number of active users

•

Active terminal numbers

•

Words of dynamic storage (this system management
fully documented in the TDV code listing)

concept

Historical information includes:
•

Total number of different users

•

Total number of jobs handled

•

Mean wait time per job

•

Number of tasks that have been run in each of 33 size ranges,
each progressively increasing by 2000 (octal) words

XVM/RSX V1B

VII-23-2

September 1976

~
~

CHAPTER 24
BATCH ACCOUNT FILE INITIALIZATION AND DISPLAY

Two TDV function tasks, ACI and ACD, control batch job accounting and
account summaries. The use of ACI and ACD is described in Part VIII
of this manual, Batch Processing.

24.1

ACI:

INITIALIZE BATCH ACCOUNT FILE

ACI allows the system manager to initialize (clear to zero) the Batch
processor account file or create an account file if one does not exist.

24.2

ACD:

DISPLAY BATCH ACCOUNT FILE

ACD allows the system manager to list the Batch Processor account file.

XVM/RSX VlB

VII-24-l

September 1976

INDEX

Abbreviations for commands, 1-9
ACD, TDV Function task, 24-1
ACI, TDV Function task, 24-1
Altmode, 1-8, 6-3, 6-9
Assembler options, 3-2
Assembling a MACRO program, 3-1
"At" sign (@), 1-9
Auxiliary disk functions, 2-3

Date, 11-1
Debugging with ODT, 22-2
DECtape Directory List TDV,
Function task, 11-1
error messages, 11-2, 11-3
Default priority of task, 6-8
Delete character or line, 1-9
DELETE FILE error messages, 8-2
DELETE FILE, TDV Function
task, 8-1
Delimiters, 7-3
Devices, I/O, 1-6
Dialogue, TKB, 6-17
DIRECTORY LIST, TDV Function
task, 10-1
error messages, 10-2, 10-3
Disk directory, 10-1
Disk, task storage on, 19-1
Disk-to-disk editing, 4-3
DISMOUNT, TDV Function task, 17-1
error messages, 17-1
Dismounting a disk (logically),
17-1
Dismount tape, 7-4
-$ command, 5-5
DSM, TDV Function task, 17-1
Dump mode, 3-6

Backarrow (+), 1-9, 7-3
Backslash (\), 1-9
Bank-mode option, 6-7
Basic Task Builder, 6-1, 6-18
Batch account file,
display, 24-2
initialization, 24-2
Batch file editing, 5-1
Batch mode, 3-1
FORTRAN, 2-1
MACRO Assembler, 3-1
processing, 13-1, 14-1, 15-1
Block-mode editing, 4-1
Braces ({ p, 1-10
Breakpoints in a task, 22-1
Buffer and partition size, 4-3
Building a task for execution,
6-1

Carriage return, 1-8
CHAIN and EXECUTE programs, 6-4
Characters, upper/lower case,
1-10
Comma character, 7-2
Command abbreviations, 1-9
Command string terminators, 1-8
Command syntax errors, SLIP,
5-16
Commands, MULTIACCESS Monitor,
1-2.1
COMMON blocks, 6-8, 6-10, 6-11
Compiler options, FORTRAN IV,
2-2
Compiling a FORTRAN program, 2-1
CONSTRUCT TDV Function task, 19-1
error messages, 19-2
Control-character facilities, 1-2.1
Control records, SLIP, 5-4
Conventions for TDV command, 1-8
Conversion to XVM/RSX, 6-18
CTRL/D, 3-6
CTRL/Q, 6-3
CTRL/T, 1-7
CTRL/U, 1-9
XVM/RSX VIB

Editor, 4-1
error messages, 4-3, 4-4
Editing batch files, 5-1
Editing disk-to-disk, 4-3
END-OF-FILE, 5-14
End-of-file, SLIP, 5-5
Error codes for *FILE routine,
5-15
Error flags, MACRO Assembler, 3-7
Error messages,
CONSTRUCT, 19-2
DECTAPE DIRECTORY LIST, 11-3
DELETE FILE, 8-1
DIRECTORY LIST, 10-3
DISMOUNT, 17-2
EDITOR, 4-3, 4-4
FORTRAN, 2-5
INSTALL, 13-3
MACRO Assembler, 3-9
MOUNT, 16-2
NEW DIRECTORY, 12-2
ODT, 22-10
OTS, 2-15, 2-17
QUEUE, 21-4
REMOVE, 15-2
RENAME FILE, 9-2
REQUEST, 14-2

VII-Index-l

September 1976

INDEX ( CONT • )

Error messages (cont.)
SLIP, 5-14
TDV, 7-5
TKB, 6-19
Errors,
$SLIP control record, 5-15
SLIP sequencing, 5-16
TKB recoverable, 6-20
Executive-mode option, 6-7
External links, 6-14
EXU.13, 6-13

File creation date, 10-2
*FILE errors, 5-14
File name and extension, 10-2
File name list, 6-13
*FILE records, 5-4
File size, 10-2
*FILE specification, SLIP, 5-3
File transfer, 7-3, 7-4
FIN, TDV Function task, 7-2
Floating-Point Processor (FPP) ,
2-1, 2-4
F option, 7-3
Form feeds, 7-3
FORTRAN error messages, 2-5
FORTRAN IV Compiler options,
2-2
FORTRAN line numbers, 5-10
FORTRAN, other versions, 2-3
FORTRAN program compilation,
2-1
FOU, TDV Function task, 7-2
FPP system OTS error messages,
2-17
Free blocks, 11-1
Function tasks, TDV, 1-2

Historical system information,
23-2

Image mode, 7-3
Index register (XR), 6-7
Initialize FORTRAN I/O tables,
2-4
Input/output, 2-3
CONSTRUCT, 19-1
DEC TAPE DIRECTORY LIST, TDV
Function task, 11-2
DELETE FILE, 8-1
DIRECTORY LIST, TDV Function
task, 10-2
DSM, 17-1

XVM/RSX V1B

Input/output (cont.)
EDITOR, 4-2
FORTRAN IV, 2-4
INSTALL, TDV Function task, 13-2
MACRO Assembler, 3-5, 3-6
MOUNT, 16-1
QUEUE, 21-3
RE~10VE, 15-1
RENAME FILE, TDV Function task,
9-2
REQUEST, 14-1
SLIP, 5-14
STATUS, 23-1
Task Builder, 6-4
TDV function tasks, 7-3
INSERT, 5-6, 5-7
Insertion records, SLIP,
5-4
INSTALL, TDV Function task, 13-1
error messages, 13-1
Internal links, 6-14
Introduction, 1-1
lnvoking,
CONSTRUCT, 19-1
DECTAPE DIRECTORY LIST, 11-1
DIRECTORY LIST, 10-1
DISMOUNT, 17-1
FIN, DEC, FOU, LIS and
TYPE, 7-2
FORTRAN IV Compiler, 2-1
INSTALL, 13-1
MACRO Assembler, 3-2
MOUNT, 16-1
NEW DECTAPE DIRECTORY
LIST, 12-1
ODT, 22-2
QUEUE, 21-1
REMOVE, 15-1
REQUEST, 14-1
SLIP, 5-2
STATUS, 23-1
Task Builder, 6-2
Text Editor, 4-1
I/O devices, 1-6
lOPS ASCII mode, 7-3
lOPS binary data mode, 7-3

Library files, 6-13
Library routines, 6-13
Line-by-line mode editying, 4-1
Linkages, 3-1
LINK definitions, 6-14
Links and structures description,
6-13
LIS, TDV Function task, 7-2
List options, Task Builder, 6-4
Lower-case characters, 1-10

VII-Index-2

September 1976

INDEX (CONT.)

LUN assignments,
Editor, 4-2
FORTRAN IV, 2-3
MACRO Assembler, 3-5
TDV function tasks, 1-4

MACRO Assembler
error flags, 3-7
error messages, 3-9
other versions, 3-6
MACRO definitions file, 3-6
MACRO program assembly, 3-1
Magtape operation, 7-4
Memory protection, 6-7
MNT, TDV Function task, 16-1
error messages, 16-1
Monitoring task prograss, ODT,
22-6
Mounting a disk logically, 16~1
Mount tape, 7-4
MULTIACCESS, 1-1
control-character facilities,
1-2.1
Monitor commands, 1-2.1

Name task option, 6-8
NEW DECTAPE DIRECTORY, TDV
Function task, 12-1
error messages, 12-2
N option, 7-3
No parity check, 7-3

Object-Time System (OTS)
library routines, 2-1
ODT, 22-1
commands, 22-2
error messages, 22-10
example, 22-6
monitoring task progress, 22-6
restrictions, 22-1
Optional characters, 1-9
Optional itmes, 1-10
Options,
Assembler, 3-2
SLIP, 5-3
$SLIP, 5-2
OTS error messages, 2-15
OTS error messages in FPP
systems, 2-17
OTS output, 2-4
Overlay structure description,
6-15

XVM/RSX VIB

Page eject, 7-4
Page-mode option, 6-7
Parameter input,
MACRO assembler, 3-6
Partition Block Description
List. (PBDL), 6-9
Partition description, 6-9
Partition size, 4-3, 6-7, 6-8
6-9
Parity error message suppression,
7-3
PASS1, PASS2, PASS3, 3-1
PAUSE statements, 2-4
Pool of Empty Nodes, 6-7
Priority default, 6-8
PUP (Peripheral Utility Program) ,
1-1

QUEUE, TDV Function task, 21-1
error messages, 21-3

Random-access information, 10-2
Recoverable TKB errors, 6-20
REMOVE, TDV Function task, 15-1
error messages, 15-2
RENAME FILE, TDV Function
task, 9-1
error messages, 9-2
REPLACE, 5-8
REPLACE WITH FILE, 5-9
REQUEST, TDV Function task, 14-1
error messages, 14-2
Resident code definition, 6-13
Resident TDV Dispatcher, 1-7
Rubout, 1-9
SEARCH AND INSERT, 5-10, 5-11
SEARCH AND REPLACE, 5-12
SEARCH AND REPLACE WITH FILE, 5-13
Sequential files transfer, 7-1
Shared address space (SAS) , 6-10,
6-11
external (ESAS), 6-11
internal (ISAS), 6-11
Shared COMMON block description,
6-10, 6-11
SIZE command, 4-3
SLIP, 5-1
command syntax errors, 5-16
control records, 5-4
editing demonstration, 5-16
error messages, 5-14
options, 5-3
sequencing errors, 5-16

VII-Index-3

September 1976

INDEX ( CONT • )

$SLIP control record errors, 5-13
$SLIP options, 5-2
Source programs, 3-1
Space, 1-10
Space character, 7-2
Square brackets ([]), 1-10
Starting block number, 10-2
STATUS, TDV Function task, 23-1
STOP Statements, 2-4
Structures description, 6-13
Symbol table, 3-1
System blocks, 11-1
System COMMON blocks description,
6-10
System library, 6-13
System status, 23-1

Table Initiali~ation, 2-4
Task breakpoint, 22-1
TASK BUILDER, 6-1
input/output, 6-4
options, 6-5
Task building,
CONSTRUCT, 19-1
DELETE FILE, 8-1
DECTAPE DIRECTORY LIST, 11-2
DIRECTORY LIST, 10-2
DISMOUNT, 17-1
FILE INPUT, 7-3
INSTALL, 13-1
MOUNT, 16-1
NEW DECTAPE DIRECTORY, 12-1
QUEUE, 21-3
REMOVE, 15-1
RENAME FILE, 9-2
REQUEST, 14-1
STATUS, 23-1

XVM/RSX VIB

Task development (TDV), 1-1
Task name, 6-8
Task storage on disk, 19-1
TDV command conventions, 1-9
TDV error messaqes, 7-5
TDV function tasks, 1-2, 1-9
TDV/system communication, 1-8
(terminator), 1-10
Terminators, command string, 1-9
Text-editing source code, 4-1
Text Editor, other versions, 4-3
TKB errors, 6-19
recoverable, 6-20
unrecoverable, 6-21
Transferred files, 7-3
Truncation mark, 10-2
TYPE, TDV Function task, 7-1

UFD, 16-1
Unrecoverb1e TKB errors, 6-21
Upper-case characters, 1-10
User files, 11-1
Us~r-mode option, 6-7
,/

V~rtual

partition size, 6-10

XFRCMD system directive, 1-9

VlI-Index-4

September 1976