Digital PDFs

DEC-11-OXERA-B-D

May 1975

163 pages

Original

5.5MB

Document:	RSX-11D Executive Reference Manual Version 6
Order Number:	DEC-11-OXERA-B-D
Revision:	0
Pages:	163
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11d/RSX11D_V6.2_Feb77/DEC-11-OXERA-B-D_RSX-11D_Version_6_Executive_Reference_Manual_197505.pdf

OCR Text

RSX-110
Executive Reference Manual
Order No. DEC-11-0XE RA-B-D

mnmnomo

RSX-110
Executive Reference Manual
Order No. DEC-11-0XE RA-8-D

RSX-llD Version 6

digital equipment corporation · maynard. massachusetts

First Printing, May 1975

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this manual.
The software described in this document is furnished to the purchaser
under a license for use on a single computer system and can be copied
(with inclusion of DIGITAL's copyright notice) only for use in such
system, except as may otherwise be provided in writing by DIGITAL.
Digital Equipment Corporation assumes no responsibility for the use
or reliability of its software on equipment that is not supplied by
DIGITAL.

@ 1975 by Digital Equipment Corporation
Associated Documents

Refer to RSX-llD Documentation Directory, DEC-11-0XUGA-B-D.

The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in
preparing future documentation.

The following are trademarks of Digital Equipment Corporation:
CDP
COMPUTER LAB
COMSYST
COMTEX
DDT
DEC
DEC COMM
DECTAPE
DIBOL

DIGITAL
DNC
EDGRIN
EDU SYSTEM
FLIP CHIP
FOCAL
GLC-8
IDAC
IDACS

INDAC
KAlO
LAB-8
LAB-8/e
LAB-K
OMNIBUS
OS/8
PDP
PHA

PS/8
QUICKPOINT
RAD-8
RSTS
RSX
RTM
RT-11
SABR
TYPESET 8
UNIBUS

CONTENTS
Page
x

PU PACE

CHAPTE:R 1

INTRODUCTION

1.1
1.1.1
1.1.2
1.1.3
1.1.4

SYSTEM EXECUTIVE SOFTWARE
Tasks
Memory Management
Significant Events and System Traps
System Directives

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

1.2

DEVICE HANDLERS

1-4

CHAPTER 2

RSX-llD EXECUTIVE

2.1
2.1.1
2.1.2
2.1. 3

MEMORY MANAGEMENT
Partitions
Shared Global Areas
System Communication Area (SCOM)

2-1
2-2
2-2
2-2

2.2
2.2.1
2.2.2
2.2.3

CONTROL OF TASK EXECUTION
Multiprogramming
Significant Events
System Traps

2-3
2-3
2-4
2-5

2.3
2.3.l
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.3.10
2.3.11
2.3.12
2.3.13
2.3.14
2.3.15

SYSTEM TABLES AND SYSTEM LISTS
Clock Queue
I/O Request Queue
Global Common Directory
Physical Unit Directory
System Task Directory
Send/Receive Queues
Task Partition Directory
Node Pool
Interrupt Connect Node
Memory Required List (MRL)
Checkpointable Task List (CTL)
Fixed Task List (FTL)
MCR Command Buffer
Batch Command Buff er
Asynchronous System Trap Queue

2-5
2-5
2-6
2-6
2-6
2-6
2-7
2-7
2-7
2-7
2-7
2-7
2-8
2-8
2-8
2-8

2.4

I/O OPERATIONS

2-9

CHAPTER 3

SYSTEM DIRECTIVES

3.1

INTRODUCTION

3-1

3.2

DIRECTIVE IMPLEMENTATION

3-1

3.3

CONVENTIONS

3-3

iii

Page
3.4

ERROR RETURNS

3-3

3.5
3.5.1
3.5.2

USING THE DIRECTIVE MACROS
Symbolic Off sets
Examples of Macro Calls

3-4
3-6
3-7

3.6
3.6.1

DIRECTIVE SUMMARIES
SEND and RECEIVE Directives

3-8
3-13

3.7

ABRT$ {ABORT TASK}

3-14

3.8

ALTP$ {ALTER PRIORITY)

3-15

3.9

ALUN$ {ASSIGN LUN)

3-16

3.10

ASTX$ {AST SERVICE EXIT)

3-17

3 .11

CLEF$ (CLEAR EVENT FLAG)

3-19

3.12

CMKT$ (CANCEL MARK TIME REQUESTS)

3-20

3.13

CSRQ$ (CANCEL SCHEDULED REQUESTS)

3-21

3.14

DIR$ (DIRECTIVE)

3-22

3.15

DECL$ (DECLARE SIGNIFICANT EVENT)

3-23

3.16

DSBL$ (DISABLE}

3-24

3 .17·

DSCP$ (DISABLE CHECKPOINTING}

3-25

3.18

ENAR$ (ENABLE AST RECOGNITION)

3-26

3.19

ENBL $ (ENABLE)

3-27

3.20

ENCP$ (ENABLE CHECKPOINTING)

3-28

3.21

EXEC$ (EXECUTE)

3-29

3.22

EXIF$

3-30

3.23

EXIT$ (TASK EXIT)

3-31

3.24

FIX$ (FIX IN MEMORY)

3-32

3.25

GCOM$ (GET COMMON BLOCK PARAMETERS)

3-33

3.26

GLUN$ (GET LUN INFORMATION)

3-35

3.27

GMCR$ (GET MCR COMMAND LINE)

3-36

3.28

GPRT$ (GET PARTITION PARAMETERS}

3-37

3.29

GSSW$ (GET SENSE SWITCHES)

3-38

3.30

GTIM$ (GET TIME PARAMETER&)

3-39

3.31

GTSK$ (GET TASK PARAMETERS)

3-40

(EXITIF)

Page

3.32

!HAR$ (INHIBIT AST RECOGNITION)

3-42

3.33

MRKT$ (MARK TIME)

3-43

3.34

QIO$ {QUEUE I/O)

3-44

3.35

QIOW$ {QUEUE I/O AND WAIT)

3-47

3.36

ROAF$ (READ ALL FLAGS)

3-48

3.37

RDEF$ (READ EVENT FLAG)

3-49

3.38

RQST$ (REQUEST)

3-50

3.39

RSUM$ \RESUME)

3-51

3.40

RUN$ (RUN)

3-52

3.41

SCHD$ (SCHEDULE)

3-54

3.42

SETF$ (SET EVENT FLAG)

3-56

3.43

SFPA$ (SPECIFY FLOATING POINT EXCEPTION AST)

3-57

3.44

SPND$ (SUSPEND)

3-58

3.45

SPRA$ (SPECIFY POWER RECOVERY AST)

3-59

3.46

SRDA$ (SPECIFY RECEIVE AST)

3-60

3.47

SVOB$ (SPECIFY SST VECTOR TABLE FOR DEBUGGING
AID)
3-61

3.48

SVTK$ (SPECIFY SST VECTOR TABLE FOR TASK)

3-62

3.49

SYNC$ (SYNCHRONIZE)

3-63

3.50

UFIX$ (UNFIX)

3-65

3.51

VRCD$ (RECEIVE DATA)

3-66

3.52

VRCS$ (RECEIVE DATA OR SUSPEND)

3-68

3.53

VRCX$ (RECEIVE DATA OR EXIT)

3-70

3.54

VSDA$ {SEND DATA)

3-72

3.55

VSDR$ (SEND DATA AND RESUME OR REQUEST
RECEIVER)

3-74

).56

WSIG$ (WAIT FOR SIGNIFICANT EVENT)

3-77

3.57

ETLO$ (WAIT FOR LOGICAL OR OF FLAGS)

3-78

3.58

WTSE$ {WAIT FOR SINGLE EVENT FLAG)

3-79

CHAPTER 4
4.1

SIGNIFICANT EVENTS AND SYSTEM TRAPS
SIGNIFICANT EVENTS

4-1

Page
4.2
4.2.1
4.2.2
4.2.3

SYSTEM TRAPS

Synchronous System Traps
Asynchronous System Traps
Processor Priorities

4-3
4-4
4-7
4-9

APPENDIX A

SYSTEM LISTS AND TABLES

A-1

APPENDIX B

GLOSSARY

:B-1

APPENDIX C

QIOMAC.MAC

c-1

APPENDIX D

DIRECTIVE PARAMETER BLOCKS

D-1

D.l

QUEUE I/O

D-1

D.2

QUEUE I/O AND WAIT

D-1

D.3

GET LUN INFORMATION

D-1

D.4

ASSIGN LUN

D-1

o.s

ALTER PRIORITY

D-2

D.6

REQUEST

D-2

D.7

EXECUTE

D-2

D.8

SCHEDULE

D-2

0.9

RUN

D-3

D.10

SYNC

D-3

D.11

MARK TIME

D-4

D.12

CANCEL SCHEDULED REQUESTS

D-3

D.13

CANCEL MARK TIME REQUESTS

D-4

D.14

CLEAR EVENT FLAG

D-4

D.15

SET EVENT FLAG

D-4

D.16

DECLARE SIGNIFICANT EVENT

D-4

D.17

READ EVENT FLAG

D-5

D.18

READ ALL FLAGS

D-5

D.19

WAIT FOR SINGLE EVENT FLAG

D-5

D.20

WAIT FOR LOGICAL OR OF FLAGS

D-5

D.21

WAIT FOR NEXT SIGNIFICANT EVENT

D-5

0.22

SUSPEND

D-6

D.23

RESUME

D-6

Page
D.24

EXIT

D-6

D.25

EXIT IF

D-6

D.26

GET TIME PARAMETERS

D-6

D.27

GET TASK PARAMETERS

D-6

D.28

GET PARTITION PARAMETERS

D-6

D.29

GET COMMON BLOCK PARAMETERS

D-7

D.30

SEND DATA

D-7

o. 31

SEND AND REQUEST OR RESUME

D-7

D.32

RECEIVE DATA

D-7

D.33

RECEIVE DATA OR EXIT

D-7

D.34

RECEIVE DATA OR SUSPEND

D-8

D.35

ABORT

D-8

D.36

FIX-IN-MEMORY

D-8

D.37

UNFIX

D-8

D.38

DISABLE

D-8

D.39

ENABLE

D-8

D.40

DISABLE CHECKPOINT ING

D-9

D.41

ENABLE CHECKPOINTING

D-9

D.42

INHIBIT AST RECOGNITION

D-9

D.43

ENABLE AST RECOGNITION

D-9

D.44

SPECIFY SST VECTOR TABLE FOR DEBUGGING AID

D-9

D.45

SPECIFY SST VECTOR TABLE FOR TASK

D-9

D.46

SPECIFY RECEIVE AST

D-9

D.47

SPECIFY POWER FAIL AST

D-10

D.48

SPECIFY FLOATING POINT EXCEPTION AST

D-10

D. 4 9

AST SERVICE EXIT

D-10

D.50

GET SENSE SWITCHES

D-10

D.51

GET MCR COMMAND LINE

D-10

vii

FIGURES
Number

3-1

Page
I/O Status Block

3-45

TABLES
Number
3-1
4-1

Page
RSX-110 Directives
Executive Trap Service Routines

viii

3-8
4-6

PREFACE
The RSX-110 Executive Reference Manual provides information required
to prepare user programs written in MACR0-11 Assembler Language for
execution under the RSX-110 Operating System. It touches only briefly
on preparing FORTRAN programs, because the FORTRAN Special Subroutines
Reference Manual covers this material.
The manual is organized as follows.
Chapters 1 and 2 present overview information, first on the whole
RSX-110 system, then on the RSX-llD Executive, respectively. Details
on the philosophy of RSX-llD can be obtained l.Jy reading
the
introductory chapters of the RSX-llD User's Guide.
Chapters 3 and 4 deal with specific Executive functions and how to use
them.
Appendixes A, B and C cover system list formats, a glossary, and a
sununary of the file QIOMAC.MAC.
QIOMAC.MAC provides all symbolic
values for QUEUE I/O function codes as well as symbolic definitions
of status return codes. Appendix D contains directive parameter block
formats for the directives.

CHAPTER 1
INTRODUCTION

RSX-llD is an event-driven multiprogramming operating system with
features that make it appropriate for a wide range of applications
involving real-time operations.
RSX-llD provides the basis for
process control systems, online business systems, and communications
systems.
The modular construction of RSX-110 allows the user to configure
available
hardware and software resources to fit a particular
processing requirement. The use of memory partitions and priority
scheduling facilitates user control over the execution of many
parallel real-time functions.
RSX-110 features include:
Fast interrupt response and servicing,
Simultaneous monitoring of multiple activities,

250 priority levels for task execution,
Priority servicing of I/O requests,
Convenient storage and recall of disk-resident programs,
Efficient, convenient task scheduling facilities,
Dynamic memory partitions to contain tasks of varying sizes,
Event flags for task synchronization and notification,
Checkpointing (roll-in/roll-out), a form of memory sharing,
Online program development, concurrent with task execution,
FORTRAU, COBOL*,
utilities,

and

MACR0-11

programming

languages

Asynchronous execution of I/O-dependent code,
Support of m.ultiuser programs and re-entrant code,
Dynamic shared global areas.
*Separate license

1-1

and

1.1

SYSTEM EXECUTIVE SOFTWARE

The following
software.

1.1.l

paragraphs

provide

brief

description

RSX-110

Tasks

The basic program unit under RSX-llD is called a task.
A task
consists of one or more programs that have been written in FORTRAN or
MACR0-11 Asseml>ly Language. Relocatable object modules are generated
and installed into the system online, making them available in
memory-image format on the disk. A task can initiate another task's
execution in various ways. The following are examples:
1.

Request inunediate exepution,

Request execution contingent upon available memory,

Schedule at a future
periodic intervals.

rescheduling

All these task ini'tiation functions can be accomplished from
operator's console as well as from a currently executing task.

1.1.2

time,

with

optional

Memory Management

There are three basic functional uses for which memory is allocated.
The amount of memory allocated to each function is specified by the
user at SYSGEN time.
The three functional memory areas follow.
1.

RSX-110 Executive code.

Partitions space for tasks and shared global areas.

User-controlled partitions in which only one task
shared global area can occupy the partition at a time

System-controlled partitions in which the
Executive
controls allocation of memory in the parti·bion and allows
multiple tasks or shared global areas
within
the
partition at one time

System lists and system tables.

1-2

1.1.3

Significant Events and System Traps

RSX-110 is an event-driven system in which task execution is governed
by the occurrence of significant events. A significant event is any
change in system status that affects the execution of a task.
For
example, completion of an I/O operation is a significant event.
One of the ways that significant events are signalled is through event
flags. There are 64 event flags. Flags 1 through 32 are local to the
task, while event flags 33 through 64 are conunon to all tasks. A task
can set, clear, test, and wait for any event flag or combination of
event flags, to achieve efficient synchronization between itself and
other tasks in the system.
When a significant event occurs, the Executive scans an active task
list, described in Chapter 2, seeking the highest priority task that
can be executed. When an eligible task is found, it is run until it
exits, suspends execution, waits for a significant event, or a
significant event occurs.
System traps are another means of governing task execution.
While
significant events have a system-wide scope, traps are local to a
task. Traps interrupt the sequence of instruction execution in the
task and cause control to be transferred to a prespecif ied point in
the program. Traps can be either synchronous or asynchronous.
Synchronous system traps (SSTs) allow servicing of fault conditions,
such as memory protection violation, that can occur internally in a
task.
Asynchronous system traps (ASTs) are executed as the result of
significant events.
Because the task has no control over when the
significant event is to occur, ASTs execute asynchronously with
respect to the task.
Trap service routines may or may not be provided by the user to handle
the synchronous and asynchronous traps.
If no synchronous trap
service routine is provided, the faulting task is aborted.
If no
asynchronous trap service routine is provided, the task continues to
execute without interruption.

1-3

1.1.4

System Directives

System directives are instructions to RSX-llD to perform functions for
an executing task.
System directives allow tasks to perform the
following:
Schedule other tasks,
Communicate with other tasks,
Measure time intervals,
Perform I/O functions,
Suspend execution,
Exit.
Directives are generated by MACR0-11 programs via macro calls and are
supported for FORTRAN by library routines supplied by DIGITAL. Refer
to Chapter 3 of this manual for details of directive usage in MACR0-11
programs.

1.2

DEVICE HANDLERS

Device Handlers are tasks that support I/O devices. These tasks are
similar
to normal tasks within the system with the following
additional features:
They usually contain an interrupt service
to respond to hardware interrupts,

routine

They are allowed to gain access
areas including privileged ones.

memory

any

By convention, device handler task names consist of two alphabetic
characters followed by four dots.
For example, the line printer
handler is named as follows.
LP ••••
Device handler tasks are loaded into memory on command from the
operator as needed.
Requ,~sts
from user tasks are queued by the
Executive to the device handler according to the priority of the I/O
request.
If no priority is specified, that of the requesting task is
used by default. When necessary, however, the requesting task can
reserve a device for its exclusive use for a period of time by
attaching it using the ATTACH function.

1-4

CHAPTER 2
RSX-110 EXECUTIVE

This chapter acquaints the user with the basic design elements of the
RSX-110 Executive. It is not intended to provide the detail required
by a systems programmer for modification of RSX-110.
The primary functions of the Executive include memory and disk
management, supervision of task execution and scheduling, intertask
communication, I/O
queuing,
console
command
monitoring,
and
maintenance of system integrity.
The basic program unit under RSX-110 is called a task and consists of
a program or set of programs that have been written in FORTRAN and/or
MACR0-11 assembly language.
Relocatable task modules are created
either online or offline and are installed into an RSX-110 system.
This process results in the recording of the task on the system disk
in memory image form~ i.e., the task is in executable form.

2 .1

MEMORY MAI.JAGEMENT

There are three different functional memory spaces. The size of
is specified during system generation. These areas are:
1.

The Executive,

Partitions,

System-controlled partitions

User-controlled partitions

System communication area (SCOM).

2-1

each

2.1.1

Partitions

Partitions are areas of contiguous real memory that are used for task
execution.
There are two modes of partition usage: user-controlled
where only one task at a time can occupy the partition
and
system-controlled where the system controls allocation of memory
within the partition for execution of one or more tasks.
The name,
base address, size, and mode of each partition are specified during
system generation and cannot be changed online. Tasks are installed
to run in a particular partition but, upon specific request, can run
in any partition that is large enough.
Normally, an active task remains resident in its memory space until
its execution is completed. A checkpointable task, however, can be
forced to relinquish its memory for execution of a higher priority
task.

2.1.2

Shared Global Areas

Shared global areas (libraries, global common blocks, and pure areas
of multiuser tasks) require space in partitions. They can be fixed in
memory or can be assigned memory by the Executive when tasks that use
them are activated.
Libraries normally are read-only and are used for code.
Global common blocks can be addressed on a per-task basis as
read/write or read-only. This is a characteristic of the task rather
than the global area and is specified during task building.
The
global area includes FORTRAN COMMON space and, normally, is used for
intertask exchange of large amounts of data.
SEND and SEND AND
REQUEST also can be used to exchange small amounts of data among
tasks. They should not be used for large amounts of data.
Multiuser tasks consist of a pure area and an impure area.
The pure
area of multiuser task is the area that is not modified during task
execution and can be shared among multiple versions of the task.
The
impure area changes during execution; one copy of the impure area
exists for each simultaneous user of the task.

2.1.3

System Communication Area (SCOM)

This memory space contains the tables, lists, system subroutines, and
other information required by the Executive to perform its functions
and maintain control of the system. It consists of a number of fixed
tables or lists and code, with the remaining space being available in
variable-length nodes. These nodes are used by the Executive and for
intertask communication.

2-2

2.2

CONTROL OF TASK EXECUTION

RSX-110 is event-driven, in contrast to systems which use a time slice
mechanism for determining a task's eligibility to execute. Under
RSX-llD, the highest priority task can run continuously until some
event or condition in the system causes it to be suspended. Another
event or change in system status can reactivate the task.
Tasks can be activated either by the operator or by another task.
Activation can be conditional, based on currently available partition
space (EXECUTE), or it can occur as soon as possible (REQUEST}.
Also
it can occur as soon as possible after some future time (SYNC,
SCHEDULE, and RUN).

2.2.1

Multiprogramming

Effective multiprogramming is achieved when many tasks reside in
memory simultaneously, spending some of their residency waiting for
I/O completion, waiting for synchronization with other tasks, or in
some way being unable to continue execution. While one or more tasks
are waiting, another task can utilize the central
processor's
resources.
Under RSX-llD, tasks are run at a software priority level ranging from
a low of 1 through a high of 250. The Executive grants central
processor resources to the highest priority task capable of execution.
When a task becomes ready to execute and it has a higher priority than
the currently executing task, the Executive interrupts the lower
priority task and allows the higher priority task to run. Execution
of the interrupted task continues when it once again becomes the
highest priority task capable of execution. The environment of an
interrupted task is preserved; except for elapsed time, interruption
is transparent to an interrupted task.
This multiprogramming scheme normally applies only to memory-resident
tasks.
Once a task is in memory, the Executive allows it to run to
completion in a multiprogramming fashion even if its memory becomes
required for the execution of a higher priority, non-resident task.
However, if it is desirable to free memory for execution of a higher
priority task, a task can be declared checkpointable when it is task
built. A checkpointable task is swapped out when its memory is
required for a higher priority task and swapped in when it once again
becomes the highest priority task requiring its memory.
Normally, a task is brought into memory when requested, executes, and
is removed from memory upon completion. This process frees memory for
another task to execute. However, a task can be fixed in memory to
permit faster response to requests for its execution. It remains in
the partition until it is explicitly removed by an UNFIX directive.
Tasks fixed in a system-controlled partition have no effect on the
rest of the partition which remains available for execution of other
tasks.

2-3

2.2.2

Significant Events

A task is considered active from the time its execution starts until
the time it has exited. While the task is active, it is included in a
priority-ordered list of active tasks called the active task list
(ATL). The system uses the ATL in the following way.
When a significant event is declared, the Executive interrupts the
executing task and scans the active task list examining the status of
tasks until a task capable of execution is found. Execution of that
task is then initiated, or continued, until one of the following
occurs.
l.

The task exits.

The task must wait for another event (e.g., I/O completion).

A significant event occurs and
capable of execution.

higher

priority

task

Task switching occurs as a result of a significant event, and
significant events occur only when declared explicitly or implicitly
by tasks.
NOTE
Task
switching
occurs
implicitly
when
a
lower
priority task is eligible for
execution and the currently
executing task performs one of
the following actions:
Suspends itself,
Waits for an event
(e.g., I/0 completion),
Exits.
Event flags are associated with significant events. Declaration of a
significant event indicates that something has happened in the system,
and the possible setting of a particular event flag indicates what has
happened.
For example, upon completion of I/O requests, a device
handler task normally sets a requester-indicated event flag and
declares a significant event.
If a requesting task instructs the
system that it cannot run until an event flag is set (signalling task
I/O completion), other eligible tasks of lower priority may run. In
the scan of the active task list, a task that is awaiting I/O
completion is by passed until a significant event is declared through
the setting of a event flag upon task I/O completion.
Each task has access to 64 event flags of which 1 through 32
unique to each task and 33 through 64 are common to all tasks.
use of event flags is detailed in Chapter 4.

2-4

are
The

2.2.3

System Traps

The ability to service certain conditions without continuously testing
for their existence is provided via system traps. As discussed in
Chapter l, two types o·f traps are defined:
synchronous
and
asynchronous (also see Chapter 4). A trap is a linkage method for
optional in-task service routines. Service routines must be included
as a part of the task, limited by the same restrictions as the task,
and run at the task's priority as a result of a system trap condition,
(e.g., fault, I/O completion). This facility also provides a means of
responding to the execution of privileged instructions and non-RSX-110
EMT's.
If the system is not explicitly notified of the existence of a
trap service routine, the system trap does not occur.

2.3·

system

SYSTEM TABLES AND SYSTEM LISTS

RSX-110 uses linked lists and fixed-length tables to maintain system
information.
Fixed-length tables are lists with elements that reside
in consecutive memory locations. This format is used when lists are
static, when list scan time is critical, or both.
Most linked lists are linked as double-ended queues and are called
deques (pronounced "decks•). Oeques allow list elements to be added
or deleted from either end, since they include backward and forward
pointers.
An RSX-llD deque consists of a listhead and list elements
(nodes), circularly linked by both ba<:'!kward and forward pointers. The
first word of a node (or listhead) is a forward pointer, i.e., the
address of the ·next node (or listhead) looking forward.
The second
word of a node (or listhead) is a backward pointer, i.e., the address
of the next node (or listhead) looking backward.
A listhead is a node that consists of only a forward and a backward
pointer, and is used as a reference point.
Hence, a listhead
identifies a deque, and indicates both the beginning and end of the
circularly linked list.
All nodes are a multiple of eight words in
length. Usually the first two words contain pointers and the third
defines the node's owner. The following paragraphs describe the major
lists used in RSX-110. Their formats and contents are described in
Appendix A.

2.3.1

Clock Queue

The clock queue is a linked list with its listhead in SCOM.
It
consists of one node for each operation to be performed at some time
in the future. A ticks-till-due count in the first node of the clock
queue is decremented at each clock tick until the node becomes due
(i.e., until the count is zero).
Then the indicated operation is
performed.
The nodes are linked in the order in which they come dua.
Each node is 16 words.

2-5

I/O Request Queue

2.3.2

The I/O request queue is a linked list with a listhead in the physical
unit directory entry for the unit to which the request has been
queued. Each entry is 16 words.
Global Common Directory

2.3.3

The global common directory (GCD) is a linked list of entries for each
global common block and library installed in the system. The GCD
listhead is in SCOM. Each entry is 16 words.
The GCD entries are created by INSTALL for the pure area of multiuser
tasks and for global common areas (libraries and global conunon). GCD
entries are linked into the GCD at run time and are pointed to by the
task's STD.

Physical Unit Directory

2.3.4

The physical unit directory (PUD) is a table of entries for each
physical unit specified during system generation. When a logical unit
number is assigned to a physical unit, the physical unit
is
represented by the address of the corresponding PUD entry. Each entry
is 25 words.

System Task Directory

2.3.5

The system task directory (STD) is a table that provides information
about each task installed in the system. The information recorded in
a task's STD entry includes the following:
1.

Information required when the
receive linked list listhead) ,

task

not

Information required to load a task into memory
name, disk address of image).

active
(viz.,

(viz.,
task

Under RSX-llD, tasks are referred to by name, and the STD is searched
for an indicated task name at each reference. The STD is structured
to enable this search to be performed rapidly, without imposing naming
conventions, order of installation, or the dedication of a large
memory area.
The STD consists of a table of entry pointers (alpha table)
for the
maximum number of installed tasks and a 16-word entry for each task
that is installed. The table is maintained by the programs that
install and remove tasks such that the number of entries is known and
consecutive table words point
to
task
STD
entries
ordered
alphabetically by task name. Thus, a task name can be found rapidly
using a binary search and memory is not dedicated for STD entries
until it is needed. The maximum size of the STD is specified during
system generation.
The 16-word block of memory for an STD entry is taken from the
when a task is installed and returned when a task is removed.

2-6

pool

2.3.6

Send/Receive Queues

The send/receive queues are linked lists with listheads in the STD
entries for each task.
Entries are created and queued in priority
order by the SEND directives and removed by the RECEIVE directives.
Entries are variable in length up to 255 words.

2.3.7

Task Partition Directory

The task partition directory (TPD) is a table of entries for each task
partition defined during system generation. Each entry is 10 words.

2.3.8

Node Pool

A node is a block of memory that is a multiple of eight words in
length.
Empty nodes for use in any deque are initially provided by
the system generation routine in the form of a long block called the
pool.
When a node is needed to expand a list, it is taken from the
pool. When a node is no longer needed, it is returned to the pool.

2.3.9

Interrupt Connect Node

Interrupt connect nodes connect the trap vector to the interrupt
service routine of a device handler task. Each node is 16 words.

2.3.10

Memory Required List (MRL)

The memory required list is a priority-ordered linked list of active
task list nodes for active tasks that require memory in a partition.
Its listhead is in the task partition directory (TPD).
There is an
MRL for each partition.
Whenever a nonfixed task exits, the MRL
associated with that partition is scanned, and an attempt is made to
assign memory to the highest-priority task in the list. If the
attempt is successful, the task's node is moved from the MRL to the
active task list. Each node is 24 words.

2.3.11

Checkpointable Task List (CTL)

For each partition, there is a priority-ordered list of checkpointable
tasks that are active in that partition. Actually, this list is a set
of links threaded through the ATL and not a distinct physical set of
nodes. The CTL listhead is in the TPD. Each entry is 24 words.

2-7

2.3.12

Fixed Task List (FTL)

The fixed task list (FTL) is a deque of active task list nodes for
tasks that have · been fixed in memory but are not active. The FTL
listnead is in SCOM. When a fixed task is made active, its node is
relinked from the FTL to the ATL. When the task exits it is relinked
into the FTL, Each node is 24 words.

2.3.13

MCR Conunand

Buffer

The MCR command buffer is 96-byte buffer that holds the data for a
reque•ted MCR function task. The buffer is set up by the MCR dispatch
task. The nod•• req~ired for the buffer are returned to the pool
after the GET MCR COMMAI~D LINE directive passes the command line to
the MCR function task.

2.3.14

Batch Conunand Buffer

The batch command buffer is a 96-byte buffer that holds data for the
batch processor.
It functions in the same manner as the MCR command
buffer.

2.3.15

Asynchronous System Trap Queue

The asynchronous system trap queue (ASQ) is a linked list that
operates on a first-in/first-out basis.
Its listhead is in ATL
entries. It con$ists of one node for each AST (asynchronous system
trap) to be executed for the task as defined by the STD entry. Each
node is eight words.

2-8

2.4

I/O OPERATIONS

The Executive's main function in I/O operations is to handle I/O
requests from tasks and pass the requests to the appropriate device
handler task. The general method follows.
1.

A QIO directive (see Chapter 3) is issued by a task.
The task specifies a number of parameters that are
required in processing the I/O request.
One of
these parameters is the logical unit number (LUN)
assigned to a device by the task.
The directive is issued
software emulated trap.
PDP-11 trap sequence.

by
It

means of a
follows the

normal
normal

The Executive examines the LUN parameter of the QIO
directive to determine which device handler is to
process the request. The particular device handler
is chosen by mapping the LUN of a particular task
into an entry in the physical unit directory using
the logical unit table.

The I/O request is put in the request queue of
device handler (one of a set of special tasks).

The requesting task can either suspend operation until the I/O request
is
completed
or continue to operate until interrupted by an
asynchronous system trap (see Chapter 4).
RSX-110 permits parallel
I/O requests to be issued by the same task. That is, the task
continues executing after issuing a QIO; subsequently the task can
issue further QIO requests without waiting for the previous request to
be completed.
Some device handlers operate in conjunction with the file control
primitives (FCP) to manipulate files.
When an FCP routine is
required, the device handler issues a SEND/REQUEST which injtiates
operation of the specified FCP routine.
I/O requests are queued for each unit by priority at requester task
priority unless otherwise specified. The handler tasks pick requests
from the top of request queues. Thus, preferential service is given
to high priority requests. However, when appropriate, devices can be
attached to a task,·in which case only requests from the attached task
or
express
request
are
dequeued.
This
continues until a
detach-unit-from-task request is dequeued, causing requests to be
dequeued by priority from the top of the I/O request queue once again.
The right to attach and detach devices is controlled by access
privileges defined for each device. Requests to attach a device are
rejected if the requester does not have the proper access rights.
Because device handler tasks can service many units, they are not
themselves attached.
The interface between a device handler task and the RSX-llD system is
accomplished by directives and system subroutines which attach and
detach devices and dequeue I/O requests.

2-9

CHAPTER 3
SYSTEM DIRECTIVES

3.1

INTRODUCTION

System directives are instructions to the Executive to perform an
indicated operation. The applications programmer uses them to control
the execution and interaction of tasks.
The system macro library
contains macro calls, which the programmer can use to execute
directives. The FORTRAN programmer invokes system directives through
a subroutine call, as described in the FORTRAN Special Subroutines
Reference Manual.
Directives are implemented solely through the EMT 377 instruction. By
using only EMT 377, programs using EMT 0 through EMT 376 can be run
via a non-RSX system trap. Any EMT other than EMT 377 traps to a
task-contained service routine that can be written to simulate another
environment to whatever degree is desired.
By using macro calls, instead of executing the directive, the
programmer need only reassemble his program if changes are made in the
directive specifications, rather ·::·, ,,-i. being required to edit the
source code.

3.2

DIRECTIVE IMPLEMENTATION

A Lrief discussion of how directives are implemented will help the
programiner understand and use the macro calls associated with the
directives.
Directive processing consists of five parts.
1.

The user issues a directive.
the
directive
parameters
parameter block {DPB).

Th~

are

directive identifier and
placed in the directive

The DPB can either be on the stack or be
space.
2.

An EMT 377 is issued.

3-1

the

user

task

The Executive traps the instruction and performs three steps:
1.

Determines whether the instruction is an EMT 377.

If it is a 377, transfers it to the directive processor.

If it is not a 377, determines whether user is capable of
handling the directive. If yes, user is given control.
If not, an error is returned.

The Executive processes the directive.

The Executive returns to the issusing task through "common
exit," if necessary, and processes any system events.

The EMT 377 is issued with the address of a directive parameter block
(DPB), or a DPB itself, on the top of the issuing task's stack. When
the stack contains a DPB pointer (address), the pointer is removed
(popped) after the directive is processed. When the stack contains a
DPB, the entire DPD is removed as the directive is processed.
In
either case, the DPB is not altered when the directive is processed.
With the exception of EXIT directives, control is returned to the
instruction following the EMT, with the C condition code set or
cleared and the directive status word (DSW)
set
to
indicate
performance or rejection. The DSW is at virtual location zero of each
task.
In the case of EXIT directives, control is not
condition code and DSW are set.

returned,

but

the

When a directive is performed properly, the C condition code in the PS
(CC-C) is cleared and the directive status word (DSW) contains a
positive number" unless otherwise noted in the directive description.
When a directive is rejected, the c condition code is set and the DSW
contains a negative nwnber. The number's value indicates the reason
for rejection.
The first word of all DPB's contains a directive identification code
(DIC) byte and a DPB size byte. The DIC indicates which directive is
to be performed. The size byte indicates the DPB length in words.
The DIC is in the low-order byte of the word and the size is in the
high-order byte.

3-2

3.3

CONVENTIONS

The following
directives.

3.4

conventions

and

assumptions

are

standard

Task and partition names can be up to six characters
long and are always represented as two words in
radix-SO form.

Device names are two characters long
represented by one word in ASCII form.

Time unit indicators, used for initial and repeated
requests, are 1 for clock ticks, 2 for seconds, 3
for minutes, and 4 for hours.

The term "background task• indicates a task that
initiated from batch.

and

for

all

are

ERROR RETURNS

Directive rejections are divided into two classes:
those where a
progranuned recovery would be common and those where it would be
unlikely. The error code, always negative, is returned in the DSW at
virtual location o.
Rejections with expected programmed recoveries
(i.e., where a branch is taken to an error routine) have values
between
-1 and -19.
Error codes indicating errors for which
programmed recoveries are not feasible are in the range from -20
through -99.
The error codes that can be received for a particular
listed with the individual directive descriptions.

3-3

directive

are

3.5

USING 'L'HE DIRECTIVE MACROS

This discussion applies to MACR0-11 programs.
FORTRAN programmers
should refer to the FORTRAN Special Subroutines Reference Manual for a
description of the library subroutines which support the directives
for that language.
Directives are issued by including appropriate macro calls in the
program.
Macro names consist of up to four letters followed by a
dollar sign and, optionally, one letter.
The optional
letter
specifies which of three possible expansions of the ~aero is desired.
If the optional letter is S, the macro produces code
onto the stack, followed by an E~rr 377.

push

DPB

If the optional letter is omitted, the macro produces only the
directive's DPB.
The macro expansion is inserted at the point of
macro invocation, but it does not contain executable code.
When the user uses the $ or $C form of the macro call, specifying the
generation of a DPB at assemble time, it is assumed that the
parameters required for DPB construction are valid expressions to be
used in MACR0-11 data storage instructions (e.g., .BYTE, .WORD,
• RADS O).
If, however, the $S form is used, specifying the generation of code to
store the DPB in the stack, the parameters must be valid source
operands to be placed directly in rmv instruction.
Only the $S form produces the DPB dynamically.
produce the DPB at assembly time.

The

other

two

forms

If the user has a predefined DPB, i.e., has used the$ or $C form of
the macro, and wishes to avoid the creation of another one, the DIR$
macro should be used instead of one that identifies the function.
This macro pushes the DPB address onto the stack using MOV SSS,-(SP),
where the macro parameter (shown here as SSS), is any
valid
representation of the DPD address. The instruction is followed by EMT

377.
In addition to the macro routines that correspond to tl1e directives,
the DIR$ macro is useful to the programmer, particularly in cases
where the DPB has been defined independently of the execution of the
directive.
DIR$ generates an RSX-llD Executive trap with a predefined DPB.
Hacro Call:

DIR$

adr,err

Three forms are possible, with the following interpretation:
DIR$

Assumes that the address of the DPB or the
DPB itself has already been pushed onto the
stack.

DIR$ adr

Generates the code to push the parameter adr
onto the stack.

DIR$ adr,err

Generates the code to push the parameter adr
onto
the
stack, executes an EMT 377,
generates a branch on carry clear to the
address
of
the
branch +4 (or +6 if
necessary) and generates a JSR PC to the err
address.

3-4

The argument adr is optional but, if present, must be a valid
assembler source qperand used to push the DPB address onto the stack.
The argument err is optional.
If defined, it must be a valid
assembler destination overand to permit a Jump to Subroutine (JSR)
instruction to an error handler if the directive is rejected.
If the optional letter is c, the macro generates a OPB in a separa.te
program section, called $DPB$$. The DPB is followed by a return to
the original program section, an instruction to push the DPB address
onto the stack, and an EMT 377. To ensure that the correct program
section is re-entered, the user must specify its name in the argument
list immediately following the required DPB parameters.
If the
argument is not specified, the blank
(unnamed) program section is
assumed.
The $C form of the macro call accepts an optional argument, PSECT.
This argument allows return to the PSECT specified rather than to the
default PSECT.
The SC and $S forms of macro calls and DIR$ accept an optional final
argument.
If included, the argument must be a valid assembler
destination operand to call a user error routine.
The argument
generates the following code.
OPEN$W

#FDBADR,,,,, ,OPEERR

BCC

.+6

;BRANCH ON DIRECTIVE ACCEPTANCE

JSR

PC,OPEERR

;ELSE, CALL ERROR SERVICE ROUTINE

This option is ignored when the user specifies the generation
DPB only.

3-5

the

3.5.l

Symbolic Offsets

Most system directive macro calls generate local symbolic offsets.
The symbols are unique to each directive and are assigned the values
of the byte offset from the start of the directive's DPB to the DPB
elements.
Because the offsets are defined symbolically, the programmer who must
refer to or modify DPB elements can do so without calculating the
offsets. Symbolic offsets also preclude the necessity of rewriting
programs to acconunodate changes in DPB specifications.
All $ and $C forms of macros that generate DPB's longer than one word
generate local offsets. All informational directives, including the
$S, form generate local symbolic offsets for the parameter block in
question.
If any of the $ or $C forms of the macros is invoked and the user
defined
symbol
$$$GLB is included, the DPB is not expanded.
are
Furthermore, if the macro produces symbolic offsets, they
generated as global symbols, unless previously defined. The symbol
$$$GLB has no effect on the expansion of $S macros.

3-6

3.5.2

Examples of Macro Calls

MRKT$
• BYTE
.WORD
.WORD
.WORD
.WORD

1,5,2,MTRAP [generate DPB only in current PSECT]
23.,S •
; "MARK-TIME" DIC AND DPB SIZE
;EVENT FLAG NUMBER
1
5
;TIME INTERVAL MAGNITUDE
2
;TIME INTERVAL UNIT
MTRAP
;AST ENTRY POINT

MRKT$C

l,S,2,MTRAP,PROGl,ERR [generates DPB in separate PSECT]

.PSECT

$DPB$$
;DEFIUE TEMPORARY SYMBOL

$$$•.

• BYTE
.WORD
.WORD
.WORD
.WORD

MT RAP

;"MARK TIME" DIC AND DPB SIZE
;EVENT FLAG rmMBER
;TIME INTERVAL MAGNITUDE
;TIME INTERVAL UNIT
;AST ENTRY POINT

.PSECT

PROGl

[return to the original PSECT]

MOV
EMT
BCC
JSR

#$$$,-:(SP)
377
.+6

PC,ERR

;PUSH DPB ADDRESS ON STACK
;TRAP TO THE MONITOR
;BRANCH ON DIRECTIVE ACCEPTANCE
;ELSE, CALL ERROR SERVICE ROUTINE

MRKT$S

#l,#5,f2,R2,ERR [push DPB onto stack]

MOV
MOV

R2 ,- (SP)
#2,-(SP)
#5 ,- (SP)
11,- (SP)
(PC)+,-(SP)

l'10V

MOV
MOV
.BYTE
EMT

nee

23.,5 •
1
5
2

23.,S.
377
.+6

JSR

PC,ERR

DIR$
MOV
EMT
BCC
JSR

@Rl I (R3)
@Rl ,- (SP)

377

.+4
PC~ (R3)

;PUSH AST ENTRY POINT
;TIME INTERVAL UNIT
;TIME INTERVAL MAGNITUDE
;EVENT FLAG NUMBER
;AND MARK TIME" DIC & DPB SIZE
;ON THE STACK
;TRAP TO THE MONITOR
;BRANCH ON DIRECTIVE ACCEPTANCE
;ELSE,CALI~ ERROR SERVICE ROUTINE
[DPB already defined. DPB address in Rl.]
;PUSH DPB ADDRESS ONTO STACK
;TRAP TO THE MONITOR
;BRANCH ON DIRECTIVE ACCEPTANCE
;ELSE, CALL ERROR SERVICE ROUTINE

3-7

3.6

DIRECTIVE SUMMARIES

Each directive description consists of a narrative explanation of its
function and use, the name of the macro associated with it and its
parameters, and the possible: :'.'.'•~ · lrn values of the directive status
word (DSW) , which is virtual memory location zero.
Only the $ form of the macro name is given, although all three options
are available unless otherwise specified.
The directive descriptions are presented in alphabetic order by macro
call
for
ease of reference.
However, the directives can be
categorized according to their function.
Table 3-1 lists
the
directives by function and describes them briefly.
Table 3-1
RSX-llD Directives

DIRECTIVE

ASSOCIATED
MACRO CALL

DIRECTIVE

DIR$

Generates
an
predefined DPB.

EXECUTE

EXEC$

Executes a task only if sufficient
memory is available at the present
time. If memory is not available, the
request is not queued.

REQUEST

RQST$

Runs a task contingent upon priority
and memory availability. If the task
cannot be run inunediately, the request
is queued.

SCHEDULE

SCHD$

Requests a task using
the
RQST$
directive at a specific future time
and, optionally, repeats the request
periodically;
e.g., the request can
be scheduled for 11:35 a.m.

RUN

RUN$

Requests a task using
the
RQST$
directive at a specified interval from
the current time and,
optionally,
repeats the request periodically.

SYNCHRONIZE

SYNC$

Requests a task using RQST$ at a
specific interval from a specified
future time and, optionally, repeats
the request periodically.

CANCEL SCHEDULED
REQUESTS

CSRQ$

Cancels
scheduled requests for
executions.

SUSPEND

SPND$

Suspends execution of the task issuing
the directive.

FUNCTION
RSX-llD

trap with a

Task Execution
Control

3-8

task

Table 3-1 (Cont.)
RSX-llD Directives
ASSOCIATED
MACRO CALL

DIRECTIVE

FUNCTION

RESUME

RSUM$

Reswnes the execution of a
has suspended itself.

task

that

TASK EXIT

EXIT$

the
task
Terminates execution of
issuing the directive and causes a
significant event.

ABORT TASK

ADRT$

Ten11inates execution of another task.

FIX IN MEMORY

FIX$

Fixes in memory (makes permanently
resident) an inactive, installed task.

UNFIX

UFIX$

Negates a FIX$ directive and frees the
memory allocated to the task.

DISABLE

DSBL$

Rejects future attempts to execute or
fix an indicated task using any of the
following directives:
RQST$, EXEC$,
SCUD$, RUN$, SYNC$, or FIX$.

EiJADLE

ENBL$

M.akes a
specified
capable of being run.

DIS ADLE
CIIECKPOIHTING

DSCP$

Disables the checkpointability of the
issuing task.

ENABLE
CHECKPOIHTING

ENCP$

Hakes the issuing task checkpointable
was
previously
checkpointing
if
disabled.

ALTP$

Alters the priority of the specified
to the new priority
task
active
indicated in the directive.

GET TIME PARAHETERSI

GTIH$

Fills an indicated a-word buffer with
current time and date information.

GET COMMON BLOCK
PARAMETERS

GCOM$

Fills an indicated a-word buffer with
conunon
information for a specific
block.

GET PARTITION
PARAllETE RS

GPRT$

Fills an indicated 3-word buffer ~ith
information for a specific partition.

GET TASK PARAHETERS

GTSK$

Fills an indicated 16-word buffer with
information about the task issuing the
directive.

Task Status Control

ALTER PRIORI':i.1Y

I
I
I

Inf orP1.ational
Directives

disabled

task

3-9

Table 3-1 (Cont.)
RSX-llD Directives

DIRECTIVE

ASSOCIATED
MACRO CALL

GET SENSE SWITCHES

GSSW$

Obtains the status of
the console
sense switches and stores it in the
issuing task's directive status word.

GET LUN

GLUN$

Fills a 6-word buff er with information
about a physical unit to which
the
task is assigned

FUNCTION

Event-Associated
Directives
DECLARE SIGNIFICANT
EVENT

DECL$

Declares a significant
event and,
optionally, sets an event flag and
reports the status of the flag before
it was set. DECL$ causes an ATL scan.

SET EVENT FLAG

SETF$

Sets an indicated event flag
and
reports the status of the flag before
it was set. SETF$ does not cause a
significant event.

CLEAR EVENT FLAG

CLEF$

Clears an indicated event flag and
reports
the
flag's status before
clearing.
CLEF$ does not cause a
significant event.

READ EVENT FLAG

ROEF$

Reads a specified event flag
and
indicates by the return code in the
directive status word whether the flag
is set or cleared.

READ ALL FLAGS

ROAF$

Reads all 64 event flags and records
their status by setting or clearing
corresponding
bits
in
a
64-bit
(4-word) buffer.

WAIT FOR SINGLE
EVENT FLAG

WTSE$

Suspends execution of the issuing task
until the indicated event flag is set.

WAIT FOR LOGICAL OR
OF FLAGS

WTLO$

Suspends execution of the issuing task
until any indicated event flag in one
of five groups is set.

WAIT FOR
SIGNIFICANT EVENT

WSIG$

Suspends execution of the issuing task
until the next
significant
event
occurs.

EXIT IP

EXIF$

Terminates the
execution
of
the
issuing task if an indicated event
flag is not set.

3-10

Table 3-1 (Cont.)
RSX-llD Directives

DIRECTIVE

ASSOCIATED
MACRO CALL

FUNCTION

Trap-Associated
Directives
MARK TIME

MRKT$

Declares a significant event after an
indicated time interval starting at
issuance of the directive.
An event
be set when the
also
can
flag
significant event is declared.

CANCEL MARK TIME
REQUESTS

CMKT$

Cancels any mark time requests made by
the issuing task.

INHIBIT AST
RECOGNITION

IHAR$

asynchronous
Inhibits recognition of
system traps for the issuing task.

ENABLE AST
RECOGNITION

ENAR$

Recognizes asynchronous system
for the issuing task.

SPECIFY POWER
RECOVERY AST

SPRA$

Tells the system whether or not power
recovery AST's are desired for the
desired, this
task.
If
issuing
directive indicates where control is
to be transferred when the AST occurs.

SPECIFY FLOATING
POINT EXCEPTION AS~

SFPA$

or not
the system whether
Tells
exception
PDP-11/45 floating point
AST' a are desired for the task. If
desired, the directive indicates where
control is to be transferred when the
AST occurs.

SPECIFY RECEIVE AS~

SlU>A$

Allows a task to determine whether
another task has sent data to it
without waiting for an event flag or
continually checking the buffer. When
data is detected, an AST is executed.

SPECIFY SST VECTOR
TABLE FOR DEBUGGING
AID

SVOB$

Specifies the virtual address of a
system trap
of synchronous
table
service routine entry points for use
by OD'l' or other debugging aids. SVOB$
takes precedence over SVTK$.

SPECIFY SST VECTOR
TABLE FOR TASK

SVTK$

Specifies the virtual address of a
system
trap
table of synchronous
service routine entry points for use
by the issuing task.

TERMINATE AST
EXECU'l'ION

ASTX$

Terminates
asynchronous
routine.

3-11

execution
trap
system

traps

of
an
service

Table 3-1 (Cont.)
RSX-llD Directives
ASSOCIATED
MACRO CALL

DIRECTIVE

FUNCTION

I/O Related
Directives
QUEUE I/O

QIO$

Places an I/O request for an indicated
device in a priority-ordered queue of
requests for that unit.

QUEUE I/O AND WAIT

QIOW$

Performs the functions of
(see above) and QIO$.

ASSIGN LUN

ALUN$

Assigns a logical unit number (LUN) to
a physical device unit.

SEND DATA

VSDA$

Queues a variable-length data block b:y
priority for a task to receive.

SEND DATA AND
RESUME OR
REQUEST RECEIVER

VSDR$

Queues a variable-length data block
by priority for a task to receive and
resumes or requests execution of the
receiving task.

RECEIVE DATA

VRCD$

Receives a variable-length data block
tbat was queued by another task.

RECEIVE DATA OR
EXIT

VRCX$

Receives a variable-lenqth data block
that has been queued by another task
or exits if none is queued.

RECEIVE DATA OR
SUSPEND

VRCS$

Receives a variable-length data block
if one is queued for the task or
suspends the task.

GET MCR COMMAND
LINE

GMCR$

Transfers an 80-byte conunand
the issuing task.
NOTE

For Information About:

Refer To:

SDAT$

VSDA$

SDRQ$

VSDR$

RCVD$

VRCD$

RCVX$

VRCX$

3-12

both

WTSE$

line to

3.6.l

SEND and RECEIVE Directives

The following additional information about SEND and RECEIVE directives
should be noted.
1.

Variable-length
received.

data

255

words

can

sent

and

If the receiver's buffer is too small to hold all the data
sent, the excess is lost and the receiver is notified by an
error cod~ in the directive status word (DSW).

The TI of a task is the same as the TI of the terminal from
which the task was initiated. If the task was initiated by
another task, the TI of the requesting task becomes the TI of
the requested task also.
Certain directives can be issued only to affect tasks with
the same TI: RESUME, ABORT TASK, ALTER PRIORITY I and CANCEL
SCHEDULED REQUEST.

Multiuser tasks issuing receive directives are passed only
that data sent with the same TI as the multiuse~ task. This
approach ensures the proper flow of data among several
multiuser tasks and a single-user task when the single-user
task is receiving from and sending to the multiuser tasks.

Up to three data words can be transmitted in a single 8-word
node1
the other five words are used for SEND/RECEIVE
overhead.

The default buffer length (13 words)
rather than 16 words.

3-13

requi~es

a 24-word node,

ABRT$
3 . 7 ABRT$ (ABORT TASK)
The ABORT TASK directive terminates the execution of the indicated
task.
This directive is intended for use as an emergency exit or
fault exit. It causes a printout at the console each time it is
invoked.
A task can abort any other task. If the task being aborted
is a multiuser task, it is aborted only if its TI matches that of the
task issuing the ABORT directive. ABORT TASK cannot be issued by a
background task.
Macro Call:

ABRT$ task

task • Task name.
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
A.BTTN = (Length is 4 bytes) Task name
DSW return codes:
+l
-02
-07
-08
-10
-80
-98
-99

Successful completion
Task not installed
Task not active
Task loading or exiting
Task is not abortable
Directive issued by background task
Part of OPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
ARH~

V("IJP'l

.~;VT!;'.

53., ~

.~A050

/V:"IJ~S/

3-14

ALTP$
3.8

ALTP$ (ALTER PRIORITY)

The ALTER PRIORITY directive alters the priority of the specified
active task to the new priority indicated in the directive. If the
task is multiuser, its priority is altered only if its TI matches that
of the calling task.
Macro Call:

ALTP$

task,pri

task ~ the name of the task whose priority is to be changed.
If task is not specified, the calling task's priority
is changed to its default priority.
pri = the new priority (1-250) for the task. If pri is not
specified, the new priority is the priority specified
at task build or installation. If a priority was not
specified during task build or installation, a system
default of 50 (decimal) is used.
The following symbols are defined locally with their
assigned values equal to the byte offset of the DPB.
A.LTTN = task name (4 bytes)
A.LTPR

= priority (2 bytes)

DSW return codes:
+l
-02
-07

-oa
-80
-95
-98

Successful completion
Task not installed
Task not active
Task in process of being loaded or exiting
Directive issued by background task
Invalid priority
Part of DPB is out of issuing task's address space

Macro Expansion:
ALT~~

T'S~tS,1~~

.rvr'?.:

i::.,.:i

.~A!".!t°'''

/TAt:V.l.~/

• t•· thFl

1 r: 7i

3-15

ALU NS
3.9

ALUN$ (ASSIGN LUN)

The ASSIGN LUN directive assigns a logical
physical device unit.
Macro Call:

ALUN$

unit

number

(LUN)

lun,devnam,devnum

lun
= Logical unit number
devnam = Physical device name (two characters)
devnum = Physical device unit nwnber
If devnam and devnum are omitted, the LUN is assigned as null. If it
has previously been assigned, omitting devnam and devnum deassigns the
LUN.
~he

following symbols are locally defined with their assigned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
A.LULU = (Length 2 bytes) logical unit number
A.LUNA = (2) Physical device name
A.LUNU = (2) Physical device unit number
DSW return codes:
+01
-90
-92

Successful completion
LUN usage interlocked (via file open)
Invalid device and/or unit
Invalid logical unit number
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

-96
-98

-99
Macro Expansion:
·\ L .l'J q;
.9YTf:
,j J~I}

') d.:.>. :'I

., '

.~-:;en

• UC It

/~!

•

• ·" 1 ~ f)

11.1

3-16

ASTX$
3.10

ASTX$ (AST SERVICE EXIT)

The AST SERVICE EXIT directive terminates execution of an asynchronous
system trap service routine. ASTs are described in Section 4.2.
If another AST is queued, and ASTs are not inhibited, the next AST
executed. Otherwise, the task's pre-AST state is restored.

When an AST service routine is entered, the stack contains certain
information.
This information is required because the AST routine
runs with the sar.te ATL node, task header, and DSW as the main part of
the task. Those ·portions of control areas that can be used to efeect
requests from AST service routines are ·saved on the stack.
The
following information is on the stack.
Event flag mask word for flags 1-16
Event flag mask word for flags 17-32
Event flag mask word for flags 33-48
Event flag mask word for flags 49-64
The pre-AST task's program status (PS)
The pre-AST task's program counter (PC)
The pre-AST directive status (virtual zero)
Additional parameters, if any
SP+l4
SP+l2
SP+lO
SP+06
SP+04
SP+02
SP+OO

The stack can contain additional information as well.
For power
recovery AST's, no information is added, but for I/O done the stack
contains the address of the I/O status block;
for MJ\RK TIME, the
stack contains the event flag number; and for an 11/45 floating point
exception, the stack contains the exception code, and the exception
address.
AST service routines must save and restore all .registers used.
The AST service routine must remove any information on the stack that
is additional to the seven words shown above before issuing an AST
SERVICE EXIT directive. The following example shows how this is done
when an AST routine is used on I/O completion:
;MAIN BODY OF PROGRAM
STAR'r:

•
QIO$S

#IO.WVB,#2,,,iIOSTBK,iASTSER,<#BUFFER,#60.,140)
;PROCESS & WAIT

EXIT$$
IOSTBK: .BLKW
BUFFER: .BLKW

;PROCESS

;EXIT TO MONITOR
2
60.

;AST SERVICE
ASTSER: •

TST(SP)+
ASTX$S

;REMOVE ADDR OF I/O STATUS BLOCK
;AST EXIT MACRO

3-17

Macro Call:

ASTX$

OSW return codes:
+01

-so

-98
-99

Successful completion
Directive not issued from an AST service routine
Part of DPB or table is out of task's address
space
DIC or DPB size is invalid

Macro Expansion:

115 •• 1

3-18

CLEFS
3.11

CLEF$ (CLEAR EVENT FLAG)

The CLEAR EVENT FLAG directive clears an indicated event flag and
reports the flag's polarity before clearing in the nsw. Clearing an
event flag does not ca~se a significant event.
Macro Call:

CLEF$

efn

efn • Event flag number
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
C.LEEF • (Length 2 bytes) event flag number
DSW return codes:
+00
+02

-97
-98
-99

Flag was already clear
Flag was set
Event flag number <l or >64
Part of DPB is out of issuing task's address
space
DIC or DPB size is invalid

Macro Expansion:
rLEF$
.~YT~

~1 •• ~

.~1~n

3-19

CMKT$
3.12

CMKT$ (CANCEL MARK TIME REQUESTS)

The CANCEL MARK TIME REQUEST directive cancels MARK TIME requests that
have been made by the issuing task. If no parameters are supplied
with the macro call, all MARK TIME requests that have been made by the
issuing task are cancelled.· Parameters are specified to cancel only
mark time requests that set an indicated event flag or cause an AST at
an indicated location.
Macro Call:

CMKT$

efn,ast

efn = event flag number (O implies no event flag)
ast = AST service routine entry address
The following symbols ar~ locally defined with their assigned values
equal to the byte offset from the start of the DPB to respective DPB
elements.
C.MKEF = (length 2 bytes) Event flag nwnber
C.MKAE = AST service routine entry address
DSW return codes:
+l
-90
-97

Successful completion
No EFN or AST entry specified
Invalid event flag number (event flag number <l or

-98
-99

Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

)64)

Macro Expansion:
C:HT i
• ~ VTF.:
• w :HH)
.wJ~I)

'5,C~fA~;T

21., ~

c;
:.vTAST

3-20

CSRQ$
3.13

CSRQ$

(CA~CEL

SCHEDULED REQUESTS)

The CANCEL SCHEDULED REQUESTS directive cancels scheduled requests for
task executions.
All requests to run a specified task can be
cancelled, or only those issued for a specified task by another
specified task.
If the task to be cancelled is a multiuser task, it
is cancelled only if its TI matches that of the scheduler.
This
directive cannot be issued by a background task.
Macro Call:

CSRQ$

ttask,rtask

ttask = Scheduled (requested) task name,
rtask = Scheduler (requester) task name.
The following symbols are locally defined with their assigned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
C.SRTN ~ (length 4 bytes) target task name
C.SRRN = (4) Requester task name
The issuing task is taken as the scheduler task when not specified.
DSW return codes:
+l
-02
-80
-98
-99

Successful completion
Task not installed
Directive issued by background task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
C~~1~

T~S~t,TA~~~

• ~· v T ~
• "' ti ~) ~ L1

~~• , "
I 'i' A ~'I. 1 I

.~:.t_~·.;.>

/TA~.1(2/

3...,.21

DIR$
3.14

DIR$ (DIRECTIVE)

DIR$ generates an RSX-110 Executive trap with a predefined DPB.
Macro Call:

DIR$

adr,err

Three forms are possible, with the following interpretation:
DIR$

assumes the address of the DPB or
itself has already been pushed
stack.

the DPB
onto the

DIR$ adr

generates the code to push the parameter adr
onto the stack.

DIR$ adr,err

generates the code to push the parameter adr
onto
the
stack, executes an EMT 377,
generates a branch on carry clear to the
address
of
the
branch +4 (or +6 if
necessary) and generates a JSR PC to the err
address.

The argument adr is optional but, if present, must be a valid
assembler source operand used to push the DPB address on the stack.
The argument err is optional.
If defined, it must be a valid
assembler destination operand to permit a jwnp to subroutine (JSR)
instruction to an error handler if the directive is rejected.

Macro Expansion:
1i J ~ $

ii A

~.., (. \/

H , • CS? )

f:r.11 r

3-22

DECL$
3.15

DECL$ (DECLARE SIGNIFICANT EVENT)

The DECIARE SIGNIFICANT EVENT directive declares a siqnificant event
and, optionally, sets an event flaq and reports its state before it
was set. Declaring a significant event causes a scan of the active
task list (ATL). The directive performs four functions:
l.
2.
3.
4.

Tests an event flag,
Sets the event flag,
Declares a significant event,
Reports the flag's polarity prior to being set in the

osw.

Macro Call:

DECL$

efn

efn = event flag number (an event flag number of 0 implies
no event flag nwnber)
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
D.CLEF = (Length 2 bytes) event flag number
DSW return codesi
+l
+O
+2
-97
-98
-99

No event flag specified
Specified flag was cleared
Specified flag was set
Event flag number <l or >64
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
0~CL,

.evTF.
.kJRn

3-23

DSBLS
3.16

DSBL$ (DISABLE)

The DISABLE directive instructs the system to reject future attempts
to run or fix an indicated task (REQUEST, EXECUTE, SCHEDULE, RUN,
SYNCHRONIZE, and FIX-IN-MEMORY directives). It is used effectively to
remove a task from a system without actually deleting its STD entry.
DISABLE cannot be issued by a background task.
If the task to be
disabled is active, it is not disabled until it becomes inactive.
When a task is installed into a system, it is not disabled,
is runnable.
Macro Call:

DSBL$

i.e.,

task

task = Task name,
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
o.SBTN

= (Length 4 bytes) task name

DSW return codes:

+l
-02
-08

... -

-10

-ao
-98
-99

successful completion
Task not installed
Task is already disabled
Task is not to be disabled
Directive issued by a backqround task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
M""'L.$

')C~l:T

.t<vTi;:

01.,5

.c;Al''iC"

/i)Jtr/

3-24

DSCP$
3.17

DSCP$ (DISABLE CHECKPOINTING)

The DISABLE CHECKPOINTING directive disables the checkpointability of
an issuing task that has been task built as being checkpointable.
This directive cannot be issued by a background task.
When a checkpointable task's execution is started,
not disabled, i.e., the task can be checkpointed.
Macro Call:

checkpointing

DSCP$

DSW return codes:
+l
-08
-10

-so

-98
-99

Successful completion
Task checkpointing already disabled
Issuing task not installed as checkpointable
Directive issued by a background task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
,., ~-CP ¢,
•

'.._<

"l ::

qr,;;. , 1

3-25

ENAR$
3.18

ENAR$ (ENABLE AST RECOGNITION)

The ENABLE AST
RECOGNITION
directive
allows
recognition
of
asynchronous system traps for the issuing task, i.e., nullifies an
INHIBIT AST RECOGNITION directive. AST's that have occurred while
recognition was inhibited are effected at issuance. When a task's
execution is started, AST recognition is not disabled.
ASTs are
described in Section 4.2.
AST service routines must save and restore all registers used.
Macro Call:

ENAR$

DSW return codes:
+l
-08
-98
-99

Successful completion
AST recognition not inhibited
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
\"1 •• 1

3-26

ENBL$
3.19

ENBL$ (ENABLE)

This directive instructs the system to make an indicated disabled task
runnable, i.e., to nullify a DISABLE directive. ENABLE cannot be
issued by a background task.
When a task is installed into a system, it is not disabled,
is runnable.
Macro Call:

ENBL$

i.e.,

task

task = Task name,
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
E.NBTN = (Length 4 bytes) Task name
DSW return codes:
+l
-02

-os
-so

-98
-99

Successful completion
Task not installed (No STD entry found)
Task is not disabled
Directive issued by a background task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
r \. ' L 5
.r.vrF:

l /. !' j( "\ )'

.~'.I.1''l~·

/Tt.Sl(5~/

tl.~.,~

3-27

ENCP$
3. 20

ENCP$

(Et~ABLE

CHECKPOINTING)

The ENABLE
CHECKPOINTING
directive
makes
the
issuing
task
checkpointable after its checkpointability has been disabled, i.e., to
nullify a DISABLE CHECKPOINTING directive.
Checkpoint cannot be
enabled for a task that was not built as being checkpointable.
Macro Call: ENCP$

osw return codes:
+l
-08

-so

-98
-99

Successful completion
Checkpointing not disabled
Pirective issued by background task
Part of DPB is out of issuing task's address space
DIC o~ OPB size is invalid

Macro Expansion:
r;~·c:FJ~

.~VTE

'>7.,t

3-28

EXEC$
3.21

EXEC$ (EXECUTE)

The EXECUTE directive activates a task only if the memory required for
its execution is presently available.
It cannot be issued by a
background task.
Macro Call:
task
part
pri
ugc
upc

EXEC$ task,part,pri,ugc,upc

= Task name,

= Partition name,
= ~riority,

= UIC group code,
= UIC programmer code.

A partition cannot be specified for a multiuser task1 i.e., the
must be requested to execute in its default partition.

task

The following symbols are locally defined with their assigned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
E.XCTN = (length 4 bytes) task name
E.XCPN = (4) Partition name
E.XCPR = (2) Priority
E.XCGC = (1) UIC group code
E.XCPC = (1) UIC programmer code
DSW return codes:
+l
-01
-02

-03
-06
-07
-08

-so

-91

-94
-95
-98
-99

Successful completion
Insufficient pool nodes available to requester
Task not installed
No memory for execution
Handler task not resident to load task
Task is active
Task is disabled
Directive issued by background task
invalid UIC
Partition not in system
Invalid Priority specified (<O or )250)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
EXFC~

~VFA5~,Pl~T,~~,2~~,2~~

.6YTE

\3.,f

.~t1~0

/~VTASK/

.~AO~~

.~~~~

.~YTE

/PA~T/

?~~.~~~

3-29

EXIF$
3.22

EXIF$ (EXITIF)

The EXITIF directive terminates the execution of the issuing task if
an indicated event flag is NOT set.
Control is returned if the
specified event flag is set.
Macro Call:

EXIF$

efn

efn a event flag nwnber
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
E.XFEF = (length 2 bytes) event flag number
DSW return codess
+l
+2

-97
-98
-99

Indicated event fla,g cleared, task exited
Indicated event flag set, task not exited
No event flag specified in mask word(s),
or invalid event flag number (event flag number <l
or >64)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
F.'<CJF$

.RYTF:
.~1Rii

3-30

EXIT$
3.23

EXIT$ (TASK EXIT)

The TASK EXIT directive terminates the execution of the issuing task.
Macro Call:

EXIT$

osw return codes:
The OSW return codes can be tested only if the EXIT$ directive fails.
+l
-98
-99

Successful completion
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:

n:rn
• ~VH'.

c;1.,1

3-31

FIX$
3.24

FIX$ (FIX IN MEMORY)

The FIX IN ~MORY directive fixes an inactive, installed task in
memory. Once fixed in memory, the task cannot be checkpointed, and it
does not relinquish its memory space until removed by the UNFIX
directive.
The use of ~his directive is desirable when the timing of a task's
execution is critical, or when it is requested very frequently. when
fixed, a fresh copy of the task is not loaded for each request.
FIX~IN-MEMORY may not be issued by a background task.
Macro Call:

FIX$

task

task = Task name,
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
F.IXTN = (length 4 bytes) task name
DSW return codes:
+l

Successful completion

-01 -· Insufficient pool nodes available to requester

Task not installed
Partition too small for task
Handler task not resident to load task
Task is active
-os
Task is disabled
-09
Task is already fixed
-10
Task not fixable
-11
Task is checkpointable
-so
Directive issued by background task
-98
Part of DPB is out of issuing task's address space
-99 -· DIC or DPB size is invalid.

-02
-03
· -06
-07

Macro Expansion:
FtO

TASI<~

• f.i v T€

"5 •• 3

.i.;·A0'5;"

/TA5r<U

3-32

GCOM$
3.25

GCOM$ (GET COMMON BLOCK PARAMETERS)

The GET COMMON DLOCK PARAMETERS directive fills
buffer with common block parameters.

indicated

8-word

The 8-'WOrd buffer is filled as follows:
Wd.
Wd.
Wd.
Wd.
Wd.
Wd.
Wd.
Wd.

l/64th base address of common block
l/64th size of common block
Creation year
Creation month
Creation day
Owner identification code (UIC)
Starting ASR (APR)
Conunon block flags byte (low order)
and status byte (high order)

01
02
03
04
05
06
07

Macro Call:

GCOM$

blknam,bufadr

blknam = name of the cormnon block
bufadr ~ Adress of 8-word buffer
The following symbols are locally defined with their assigned
equal to the byte offset from the start of the DPB element.

value

G.COBN - (4) Common block name
G.COBA - (2) Buffer address
The following offsets are assigned relative to the start of the common
block parameters buffer.
G.COBB G.COBS G.COYR G.COMO G.COSA G.COUI G.COTP G.COFW -

(2)
(2)
(2)
(2)
(2)
(2)
(2)
(2)

1/64 common block base address
1/64 common block size
Creation year
Creation month and day
Status and starting APR
Owner identification (UIC)
TPD
Common block flags byte address

The flags byte and the status byte are in the same word (G.COFW). The
flags byte is in the low-order position and the status byte is in the
high-order position.
The following bits are defined for the fla9s byte.
Bit

O
1
2
3
4

Meaning When Set
Library or common area loaded
1 =library, 0 = common area
GCA is position independent
Nonowner has write access
Nonowner has read access

3-33

The following values are defined for the status byte.
Meaning
0

2
4
6

52
54
56

Global area not in use
Load request queued
Load request succeeded
Load request failed
Record request queued
Record request succeeded
Record request failed

DSW Status:
+l
-02
-98
-99

Successful completion
Indicated conunon block not in system
Part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid

Macro Expansion:
GCOMi

SYSR~S,C0~8UF

.PYTF:

~7 •,a

.P40'5!6
• 11.

oQ o

/SYS~ES/

c: c; M~ , 1F

3-34

GLUNS
3.26

GLUN$ (GET LUN INFORMATION)

The GET LUN INFORMATION directive fills a 6-word buffer
with
information about a physical unit to which the specified logical unit
is assigned for the requesting task. If requests to the physical unit
have been redirected to another unit, the information returned
describes the effective assignment.
The 6-word buffer of LUN inforrnation comprises the first six words
the Pun. See Appendix A.
Macro Call:

GLUN$

lun,bufadr

Logical unit number
lun
buf adr = ~ddress of 6-word buffer which holds LUN
information
The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the nPB to the respective
DPB elements.
G.LULU G.LUBA -

{length 2 bytes) Logical unit number
(2) Buffer address

DSW return codes:
+l

Successful completion
Unassigned LIB~
Invalid logical unit number
Part of DPB or buffer is out of task's address
space
DIC or nPB size is invalid

-OS
-96
-98
-99
Macro Expansion:
_;L .hi'S
• ;l 'f

Tl:'.

.... ")~11
• "")~!')

-;; , L.U B•JF
'), J
5
i..U 'Jd'Jf-"

3-35

GMCR$
3.27

GMCR$ (GET MCR COMMAND LINE)

The GET MCR COMMAND LINE directive instructs the system to transfer a
command line to the issuing task. The issuing task is an MCR function
task requested by the MCR dispatcher task. The command line can be 1
through 80 bytes in length. It was placed in a list in SCOM by the
MCR dispatcher. The GMCR$ macro call should be issued as soon as
possible by MCR function tasks ( ••• xxx) in order to free pool space.
If the command line is terminated by a carriage return, a flag is set
in the task's header to cause the MCR dispatcher task to be requested
upon exit.
The command line is read into a buffer that is picked from the pool by
the MCR dispatcher task. It is linked into the MCR queue or the batch
queue by the batch processor.
The format of the buffer is a standard MCR buffer.
The DSW contains the character count for the conunand line excluding
the
carriage
control
characters
if
the
directive executes
successfully.
Macro Call:

GMCR$

The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the respective DPB
element.
G.MCRB = (Length 80 bytes) MCR line buffer
DSW return codes.
+nn

Character count
No buffer exists or illegal task name
Part of DPB or buffer is out of issuing
address space
DIC or DPB size is invalid

-so
-98

-99

NOTE
No "$S" macro
directive.

form

Macro Expansion:
H
• -3VTF.

.;~1;:

1~7 •• 4t •

3-36

exists

for

this

task's

GPRT$
3.28

GPRT$ (GET PARTITION PARAMETERS)

The GET PARTITION PARAMETERS directive fills an indicated 3-word
buffer with partition parameters. If a partition is not specified,
the partition of the issuing task is assumed.
The 3-word buffer is filled as follows:
Wd.
Wd.
Wd.

l/64th base address of partition
l/64th size of partition
partition flags byte

Macro call:

GPRT$

prtnam,bufadr

prtnam = Partition name
bufadr = Address of buffer
The following symbols are locally defined with their assigned value
equal to the byte off set from the start of the DPB to the DPB element.
G.PRPN G.PRBA -

(4) Partition name
(2) Buffer address

The following offsets are assigned
partition parameters buffer:
G.PRPB G.PRPS G.PRFW -

relative

the

start

(2) 1/64 partition base address
(2) 1/64 partition size
(2) Partition flags byte

The following bits are defined for the flags byte.
Bit
0
1
2

Meaning When Set
User-controlled partition
Occupied user-controlled partition
System-controlled partition
Active system-controlled partition

DSW:
+O
-02
-98
-99

Successful completion
Indicated partition not in system
Part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid

Macro Expansion:
G F-' ~ f '.

Gt. '.: ~ L , ~ ~ IH~ U F

.BVTF.

b'5.,4

.~AD50

/GE\llo(L/

• J.. 1 R ;)

PA~ ~1 1 .J F

3-37

the

GSSW$
3.29

GSSW$ (GET SENSE SWITCHES)

This directive instructs the system to get the status of the console
sense switches and store it in the issuing task's directive status
word.
Macro call:

GSSW$

DSW Codes:
Successful completion is indicated if cc-c is clear. Switch
values will be found in the osw. Unsuccessful completion is
indicated by cc-c set and one of the following codes in the

osw.

-98
-99

Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
GS~AS

.~VTE

\25.,1

3-38

GTIM$
3.30

GTIM$ (GET TIME PARAMETERS)

The GET TIME PARAMETERS directive fills an indicated 8-word buff er
with current time and date parameters. All values are in binary. The
8-word buffer is filled as follows.
WO.

wo.
wo.
wo.
wo.
wo.
wo.
wo.

Year (since 1900),
Month of year,
Day of month,
Hol.lr of day,
Minute of hour,
Second of minute,
Tick of second,
Ticks per second (depends on frequency of
clock).

0
1
2
3

5
6
7

Macro Call:

GTII-1$

bufadr

buf adr = Address of 8-word buff er
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
G.TIBA ='(length 2 bytes) Buffer address
The following offsets are assigned relative to the start of
parameters buffer.
G.TIYR
G.TIMO
G.TIOA
G.TIHR
G.TIMI
G.TISC
G.TICT
G.TICP

=
=

=
=
=
=
:;:

(2)
(2)

the

Year
Month
Day
Hour
Minute
Second
Clock tick
Clock ticks per second

OSW return code$:
+l
-98

·-

-99

Successful completion
Part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid

Macro Expansion:
GlIM~

T P1'3UF

JYTf.

;.~ '· • ' ?

• ~· \1Rl1

T!M~UF

3-39

time

GTSK$
3. 31

GTSK$ (GET TASK PARAMETERS)

The GET TASK PARAMETERS directive fills an indicated
with parameters relating to the issuing task.

16-word

buffer

The 16-word buffer is filled as follows:

wn. 00

WD. 15
WD. 16
wo. 17

Issuing task's name (first half),
Issuing task's name (second half),
Partition name (first half),
Partition name (second half),
Name of the task to which the ATL
node is accounted; usually task name of
requester of issuing task (first half),
Name of the task to which the ATL node is
accounted; usually task name of requester
of issuing task (second half),
Run priority
User identification code (UIC for file
control services)
Number of logical I/O units (LUN's)
Machine type indicator e.g., 45, for PDP-11/45
STD flags words,
[~dress of task SST vector tables),
[Size of task SST vector table (in words)],
Zero (reserved)
Zero (reserved)
Zero (reserved)

Macro Call:

GTSK$

WD. 01

wo. 02
WD. 03
WD. 04
wo. 05
wo. 06
WD. 07
wo. 10
wo. 12
wo. 13

WD. 11
WD. 14

buf adr

bufadr = Address of a 16-word buffer.
The following symbol is locally defined with its assigned value equal
.to the byte offset from the start of the DPB to the DPB element.
G.TSBA = (length 2 bytes) Buffer Address,
The following offsets are assigned relative to the start of
parameters buffer:
G.TSTN = (4) Task name,
G.TSPN = (4) Partition name,
G.TSRN = (4) Name of task's requester,
G.TSPR = '(2) Priority,
G.TSGC = (1) UIC Group code
G.TSPC = (1) UIC Programmer code
G.TSNL = (2) Number of logical units,
G.TSMT = (2) Machine type,
G.TSFW = (2) STD flags word
G.TSVA = (2) Task's SST vector address
G.TSVL = (2) Task's SST vector (word) length

3-40

the

task

The following bits are defined for the flags word.
Bit

4
6

7
8

9
10
11
12
13

Meaning When Set
STD is 24 words long rather than 16 words long
Task is fixed in memory
Task is disabled
Task is being fixed in memory
Task is multiuser
Task is privileqed
Network attribute bit
Restricted usage level one (background batch jobs)
Restricted usage level two
Task cannot be aborted
Task cannot be disabled
Task cannot be fixed in memory
Task cannot be checkpointed

DSW:

+01
-98

-99

Successful completion
Part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid

Macro Expansion:
~, 5!<'

f Sl(Pi!F

.~vfE

'-3.,~

• '":'IQ!'\

TSi<?l'F

3-41

IHARS
3.32

IHAR$ (INHIBIT AST RECOGNITION)

INHIBIT AST RECOGNITION directive inhibits
recognition
of
asynchronous system traps for the issuing task. The AST's are queued
as they occur and are effected when AST recognition is enabled. There
is an implied AST inhibit whenever an AST service routine is
executing. When a task's execution is started, AST recognition is not
disabled. ASTs are described in Section 4.2.
The

It is the recognition only which is inhibited.
The ASTs are still
queued by the system. They are queued FIFO and occur in that order.
AST service routines must save and restore any registers used.
Macro Call:

IHAR$

DSW return codes:
+l
-08
-98
-99

Successful completion
AST recognition already inhibited
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
Q'!l., t

3-42

MRKT$
3.33

MRKT$ (MARK TIME)

The MARK TIME directive declares a 1ignificant event after an
indicated time interval.
The interval beqins at issuance of the
directive. If an event flag ia specified, it is cleared at issuance
and set at the time of the siqnificant event. If an AST entry point
is specified, an asynchronous system trap occurs at the time of the
aiqnificant event,
At the 1$T, the task's PS, PC, virtual zero
(directive status), and the event flag mask are pushed onto the task's
(user) stack.
If neither an event flag number nor an AST service
entry point is specified, the siqnificant event still occurs after the
indicated time interval. ASTs are described in Section 4.2.
Macro Calls

MRKT$

efn,timmag,timunit,ast

efn

•

timmag

•

timunit

•

ast

•

flag number (O implies no event
flag)
Time interval magnitude, i.e., how many time
int(;!rval units
Time interval unit
l • clock ticks
2 • seconds
3 • minutes
4 ~ hours
AST entry address
E~nt

The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
M.KTEF
M.KTMG
M.K'l'UN
M.KTAE

(Length 2 bytes) event flag
(2) time maqnitude
(2) Time unit
(2) AST entry address

•
•
•
•

DSW return codes1
+l
-01
-93
-97

Successful completion
Unavailable pool node
Invalid time specified
Invalid event flag number (event flag number <l or

·-

)64)

-98
-99

Part of OPB is out of issuing task's address space
DIC or DPB size ia invalid

-100'

Macro Expansions
.~q!(f'

4,~·a,2,MTAST

,t'HF.

'.!.,';

•'NOR!')

,WOR"

,wi~o

.~;O~f)

~UST

3-43

010$
3.34

QIO$ (QUEUE I/O)

The QUEUE I/O directive places an I/O request for an indicated device
in a queue of priority-ordered requests for that device unit. The
device unit is specified as a loqical unit number (LUN).
Normally, a significant event is declared by handler tasks (via system
subroutines) upon I/O completion. If an event flag is specified, it
is cleared when the request is queued, and set at the significant
event.
The I/O Status block is also cleared when the request is
queued.
If an AST service entry point is specified, the AST occurs upon I/O
completion with the task's PS, PC, virtual zero (directive status),
and the address of the I/O status block is pushed onto the task's
(user) stack. Refer to Section 4.2.
Macro Call:
f nc
lun
efn

QIO$.fnc,lun,efn,pri,iost,ast,prmlst

= I/O function code (see Appendix C for symbols)
= Logical unit number
= Event flag number (O implies no event flag)

It can be either global or local.
pri
= Priority
iost
= Address of I/O status block
ast
= Address of I/O done AST entry point
prmlst =Parameter list of the form <P1, •••• ,P6> •
Three error indicators are used in conjunction with QIO$:
1.

The C bit,

The directive status word,

The I/O status block.

The C bit is set to indicate that the format of the macro call was
incorrect1
i.e., it indicates that the Executive rejected the macro
call because it resulted in an incorrect DPB. If the C bit is clear,
format of the macro call is correct, but the I/O has not necessarily
been successful.
The directive status word can be tested to determine whether the
Executive successfully queued the I/O request. It is tested followinq
the WTSE$ macro call associated with the QIO$. If the request was not
queued, the directive status word contains one of the error codes
listed below.
The I/O status block can be tested upon I/O completion to determine
the success or failure of the actual transfer. The format of the I/O
status block is illustrated below.
I/O status error codes are
provided in Appendix c.

3-44

The first call of this macro defines the following symbols and
assigns, as values, their byte offset from the beginning of the DPB.
Q.IOFN
Q. IOLU
Q. IOEF
Q.IOPR
Q.IOSB
Q.IOAE
Q.IOPL

(length 2 bytes) I/O function
(2) Logical unit number
(1) Event flag number
( 1) Priority
(2) Address of I/O status block
(2) Address of I/O done AST entry point
(12) Parameter list (up to 6 words).

=
=
=
=

=
=
=

DSW return codes:
+l
-01
-OS
-06
-95
-96

-97
-98
-99

Successful completion
Unavailable pool node for request queue
Unassigned LUN
Handler task not resident
Invalid Priority ()250)
Invalid LUN
Invalid event flag nwnber (<l or >64)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Figure 3-1 illustrates the content of the I/O status block.
Byte o

Byte 1
TTY Termination
Character

Word 0

Success Indicator
OR

CTRL Z (EOF) Indicator
Number of Characters Transmitted

Word 1

Figure 3-1
I/O Status Block
Word 0 can contain two 1-byte entries (TTY termination character and
success indicator) or it can contain a -10 to indicate CTRL Z (EOF).
If two entries are placed in word o, the success indicator contains a
l to indicate that the operation was successful or an error code, as
described in Appendix c.
The TTY termination character.is used by teletype handler tasks and
similar handler tasks (e.g., DECWriter) and can be one of the
following:
15(8) =CR,
33(8) =ALT,
0

= maximum number of characters received.

Word 1 contains the number of characters transmitted to
I/O device.

3-45

from

the

Macro Expansions
1~rns

.HTE
.w~Rn

tJ.w~~.1,9,3e,to!a,Q10AST,c1u,,stz,4~>

l1UHH!i

rn.wve

• ~rn~r>

,BVT!

:;,50

,NO~t)

• w:)jlf,,
.~O~D

• w~~·l
• Wl'.JIM

IOSS
~IJAST

Su'
S?Z
.i~

3-46

QIOWS
3.35

QIOW$ (QUEUE I/O AND WAIT)

The QUEUE I/O AHO WAIT directive performs the functions of both QUEUE
I/O and WAIT FOR SINGLE EVENT FLAG (WTSE$). The format of the call
and other related information is identical with that of QIO$, with the
following exception:
if event flag 0 is specified, the queue I/O is
performed, but the wait is not performed.
The user should check the C bit and the I/O status
after the macro call.
Macro Call:

block

QIOW$

DSW return codes1
All those returned for QIO
-97
Event flaq >64
Macro Expansion:
:H'h''

t~.~L~.S,1,2~~,I~S~t,HUAST,~X~MU~,SIZ~>

• :~ryiql)

],·tUAlifG
tLl.Rt..rit

.Wl)~t)

.i;Hf
.to4vr~

.:..i1Rll
• w;Jilfn

·-~ ,~,,

·"i~ri

·', a0~

t~S'H

Q'')ASr
t l\JiiUI'

't lS::

3-47

inunediately

ROAF$
3.36

ROAF$ (READ ALL FLAGS)

The READ ALL FLAGS directive reads all 64 event flags for the issuing
task and records their polarities in a 64-bit (4-word) buffer.
Macro Call:

ROAF$

bufadr

bufadr = Address of 4-word buffer.
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
R.DABA = (Length 2 bytes) buffer address
DSW return codes:
+l
-98
-99

Successful completion
Part of DPB or buffer is out of issuing task's
address space
DIC or DPB size is invalid

Macro Expansion:
~r1 AF~

FL.AGS

.Ev Te:

39.,e
FLAGS

...

o~"

3-48

RDEFS
3.37

RDEF$ (READ EVENT FLAG)

The READ EVENT FLAG directive tests
reports its polarity in the osw.
Macro Call:

indicated

event

flag

and

RDEF$ efn

efn = Event flag number
The following symbol is locally defined with its assigned value equal
to the byte off set from the start of the DPB to the DPB element.
R.DEEF = (Length 2 bytes) event flag number
DSW return codes:
+O
+2
-97
-98
-99

Flag was cleared
Flag was set
Event flag nwnber <l or )64
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
~0EF~

.~vri:.:
.w:i~n

3-49

RQST$
3.38

RQST$ (REQUEST)

The REQUEST directive activate• a taak, i.e., enable• and runs the
task continqent upon priority and memory availability. If the task
cannot be run immediately, the request is retained so that the task
executes when condition• change, i.e., when more memory is available.
It cannot be issued by a backqround task.
Macro calla
task
part
pri
ugc
upc

RQST$

task,part,pri,uqc,upc

• Task name,
• Partition name,
• Priority
• UIC qroup code,
• UIC programmer code.

A partition cannot be specified for a multiuser taskr i.e., the
must be requested to execute in its default partition.

task

The followinq symbols are locally defined with their assigned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
(lenqth 4 bytes) task name in radix SO
(4) Partition name
(2) Priority
(1) UIC qroup code
(1) UIC proqrammer code

R.QSTN •
R.QSPN •
R.QSPR R.QSGC •
R.QSPC •

DSW return codes1
+l
-01
-02
-03
-06
-01
-08

-so

-91
-94
-95
-98
-99

Successful completion
Insufficient pool nodes available to requester
Task not installed
Partition too small for task
Handler task not resident to load task
Task is active
Task is disabled
Directive issued by backqround task
Invalid UIC
Partition not in system (no TPD entry found)
Invalid priority specified (<O or >250)
Part of DPB is out of issuinq task's address space
DIC or DPB size is invalid

Macro Expansion:
1-rn~T-S

~YTAi~,GENQL,~,l~A,5~

.F.YTE
.i:-AnSvJ

t 1.• , .,
/'HT 431(/

.~4Di::;QI

/~E~~L/

•.,; ::n~ ,,

.EYT~

5~,1)1/l

3-50

RSUM$
3. 39

RSUM$

(RESUME)

The RESUME directive instructs the system to resume the execution of a
task that has issued a auspend directive. If the task being resumed
is a multiuser task, it is resumed only if its TI matches that of the
task issuing the RESUME directive. The RESUME directive cannot be
issued by a background task.
NOTE
It is possible for a task to
RESUME
itself
using
the
asynchronous trap feature.
Macro Call:

RSUM$

task

task • Task name.
The following symbol is defined locally with its assiqned value equal
to the byte offset from the start of the DPB to the DPB element.
R.SUTN • (length 4 bytes) taak name
DSW return codeas
+l
-02
-07

-os
-so

-98
-99

Successful completion
Task not installed
Task not active
Task not suspended
Directive issued by background task
Part of OPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansiona
~H lJ '1 ;;

U S I( i;

.~YT~

~·1.,-s

.~Ar),~

/TAt;I(~/

3-51

RUN$
3 . 40

RUN$ ( RUN)

The RUN directive causes a task to be requested at a specified future
time, and optionally repeated periodically.
The schedule time is
specified in terms of delta time from issuance.
The RUN directive
cannot be issued by a background task.
Macro Call:
tsk =
prt =
pri =
ugc =
upc =
smg =
snt =

rmg =
rnt =

RUN$ tsk,prt,pri,ugc,upc,smg,snt,rmg,rnt

Task name,
Partition name,
Priority
UIC group code
UIC programmer code,
Schedule delta magnitude i.e., how many schedule
units,
Schedule delta unit,
l= clock ·ticks
2= seconds
3= minutes
4= hours
Reschedule interval magnitude,
Reschedule interval unit

A partition cannot be specified for a multiuser task1 i.e., the
must be requested to execute in its default partition.

task

The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
R.UNTN =
R.UNPN =
R.UNPR =
R.UNGC =
R.UNPC =
R.UNSM =
R.UNSU =
R.UNRM =
R.UNRU =

(length 4 bytes) task name
(4) Partition name
(2) Priority
(1) UIC group
(1) UIC programmer
(2) Schedule magnitude
(2) Schedule unit
(2) Reschedule magnitude
(2) Reschedule unit

DSW return codes:
+l
-01

-02
-03

-80
-91
-93
-94

-95
-98
-99

Successful completion
Insufficient pool nodes available to requester
Task not installed
Partition too small for task
Directive issued by background task
Invalid UIC
Invalid time parameter specified
Partition not in system
Invalid priority specified (<O or >250)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

3-52

Macro Expansion:
~l'~~

~CIT,MOSPA~,25,31,4~,1013115,3

• RYT€

11.,u •

.~Al)50

/DOI 1'I

• IH n.50
• w:Fm
.f;VTF.

;:t C\
.:11, St

/'1i)S~Hi/

.~:iq·i

1:'~

• W:')QI)

• ;.j :i"" i)
• "':'.'t~i')

1.5
~

3-53

SCHD$
3.41

SCHD$ (SCHEDULE)

The SCHEDULE directive cau•e• a ta•k to be reque•ted at a specified
future time, and optionally, repeated periodically. The schedule time
is specified in terms of absolute time-of-day. The SCHEDULE, RUN, and
SYNC directives are the same, differinq only in the form in which the
schedule data is presented. SCHEDULE cannot be issued by a background
task.
Macro Call:
tsk •
prt •
pri •
ugc •
upc •
hrs •
min sec •
tck a
rmag •
rnt •

SCHD$ tsk,prt,pri,ugc,upc,hrs,min,sec,tck,rmaq,rnt
Task name,
Partition name,
Priority,
UIC group code,
UIC proqrammer code,
Schedule hours,
Schedule minutes,
Schedule seconds,
Schedule clock ticks,
Reschedule interval magnitude (how many of the
defined by rnt),
Reschedule interval unit.
1 • clock ticks
2 • seconds
3 • minutes
4 • hours

A partition cannot be specified for a multiuser task1 i.e., the
must be requested to execute in its default partition.

units

task

The following symbols are locally defined with their assigned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
S.CHTN •
S.CHPN •
S.CHPR •
S.CHGC •
S.CHPC •
S.CHHR •
S.CHMI =
S.CHSC •
S.CHCT •
S.CHRM •
S.CHRU •

(length 4 bytes) Task name
(4) Partition name
(2) Priority
(1) UIC group
(1) UIC proqrammer
(2) Hours
(2) Minutes
(2) Seconds
(2) Clock ticks
(2) Reschedule magnitude
(2) Reschedule unit

DSW return codes:
+l -- Successful completion

-01 -- Insufficient pool nodes available to requester

-02
-03

-so

-91

-93
-94
-95
-98
-99

Task not installed
Partition too small for task
Directive issued by background task
Invalid UIC
Invalid time parameter specified
Partition not in system
Invalid priority specified C<O or >250)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

3-54

Macro Expansions
SC"4(U

~01L,rJ~E,~~~,40,40,1~,3~,00,0~,~,~

• evr~

ts., 1~ •

.P.:l!i50

/POOL./

• ~unslr!'

/COQ~/

• \I/ :I" 1

~~a

.t3VTE

4~:,'171

• 14 t'Hl,,

U'I

• ._'.0M11
._IAl\Htn

~~A

• ..inRr:>
• ~1a~n

.i.inQli

3-55

SETFS
3.42

SETF$ (SET EVENT FLAG)

The SET EVENT FLAG directive sets an indicated event flag and reports
the flaq's polarity before settinq in the osw. Settinq an event flaq
does not cause an ATL scan.
Macro Call:

SETF$ efn

efn • event flaq nwnber
The followinq symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
s.ETEF • (Length 2 bytes) event flaq number
DSW:
Flag was cleared
Flag was set
Event flag number <l or >64
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

+0
+2

-97
-98
-99

NOTE
It is recommended that the user avoid
specifyinq event flaq numbers from 59 to
64, which are reserved for RSX-llD.
Macro Expansion:
SETF$
.~YTE
.~ORD

3-56

SFPA$
3.43

SFPA$ (SPECIFY FLOATING POINT EXCEPTION AST)

The SPECIFY FLOATING POINT EXCEPTION AST directive
system to record one of the following two items:

instructs

That floating point exception ASTs for the issuing
task
are desired and where control is to be
transferred when a floating point exception AST
occurs,

The floating point exception ASTs
task are no longer desired.

for

the

issuing

When an AST service entry point is specified, future floating point
exception ASTs occur for the issuing task, and control is transferred
to the indicated location whenever a floating point exception AST
occurs.
When an AST service entry point is not specified (zero in the second
DPB word), future floating point exception ASTs do not occur until an
AST entry point is specified again. ASTs are described in Section
4.2.
If SFPA$ is not used, no AST is queued.
AST service routines must save and restore all registers used.
Macro Call:

SFPA$

ast

ast = AST service entry address.
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
S.FPAE = (Length 2 bytes) AST entry address
DSW return codes:
+l
-01
-08

Sucessful completion
No pool node available
AST entry already un-specified
Directive issued during AST service
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

-so
-98
-99

NOTE
This
directive
applies
only
for
PDP-11/45.
It
has
no
effect on
PDP-11/40. For the PDP-11/40, refer to
SVTK$.

Macro Expansion:
,SP4'
• AHE

• ·o~n

F?A)r

111 •• ~

FPAST

3-57

SPND$
3.44° SPND$ (SUSPEND)

The SUSPEND directive suspends the execution of the issuing task.
A
task can suspend only itself and not another task. The SUSPEND
directive cannot be issued by a background task.
Macro Call:

SPND$

DSW return codesa
+2

-so
-98
-99

Successful completion
Directive issued by background task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

i1acro Expansions
SP~n~

.BVT~

3-58

SPRA$
3. 4 5

SPRA$ (SPECIFY POWER RECOVERY AST)

The SPECIFY PCMER RECOVERY AST
record either of the following:

directive

instructs

the

system

That power recovery AST's for the issuing task are
desired, and where control is to be transferred when
a power recovery AST occurs, or

That p<Mer recovery AST's for the issuing
no longer desired.

task

are

When an AST service routine entry point is specified, future power
recovery ASTs occur for the issuing task, and control is transferred
to the indicated locat~on whenever a power recovery occurs.
When an
AST service entry point is not specified (zero in the second DPB
word), future power recovery.ASTs do not occur until an AST entry
point is specified again. ASTs are described in Section 4.2.
If SPRA$ is not used, no AST is queued.
AST service routines must save and restore all registers used.
Macro Call:

SPRA$ ast

ast = AST service routine entry address or zeros if none is
desired.
The following symbol is locally defined with its assigned value
to the offset from the start of the DPB to the DPD element.

equal

s.PRAE = (Length 2 bytes) AST entry address
DSW return codes:
+l
-01
-08
-80
-98
-99

Successful completion
No pool node available
AST entry already unspecified
Directive issued during AST service
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
.3YTE

PWRAST
t~~ •• 2

• r,.i,)Qi)

Pi•JiUST

SP~U

3-59

SRDA$
3.46

SRDA$ (SPECIFY RECEIVE AST)

The SPECIFY RECEIVE AST directive allows a task to determine whether
another task has sent data to it.
When the sending of data is
detected, the AST is executed. Use of this directive eliminates the
need for the receiving. task to check a buffer constantly for the
presence of data. ASTs are described in Section 4.2.
Macro Call:

SRDA$

ast

ast = AST service entry point. If ast is specified, receive
occurs for the issuing task and control is transferred
to the entry point. If ast is not specified, ASTs do
not occur.
The following symbol is defined locally with its assigned value
to the byte offset from the start of the DPB.

equal

s.RDAE = AST entry address (two bytes)

DSW return codes:
+l
-01
-08

-so
-98
-99

Successful completion
No pool node available
AST entry already unspecified
Directive issued during AST service
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

AST service routines must save and restore all registers used.

Macro Expansion:
SRi)U

~C\#AST

.BYTE

\~7.,2
~C\f AH

• W'.llH)

3-60

SVOB$
3.47

SVOB$ (SPECIFY SST VECTOR TABLE FOR DEBUGGING AID)

The SPECIFY SST VECTOR TABLE FOR DEBUGGING AID directive specifies the
virtual address of a table of synchronous system trap service routine
entry points for use by an intratask debugging aid (e.g., ODT).
SSTs
are described in Section 4.2.
When both the issuing task table and the CDT exist and both contain an
entry for a particular trap, the CDT table takes precedence.
The table can contain up to eight entry points.
Each entry point
corresponds to a type of error that could occur or an instruction.
The table is in the following format.
WD.

wo.

WD.
WD.

wo.
wo.

Odd address error or other trap through 4
Segment fault
T-bit trap or execution of a BPT instruction
Execution of an 'IOT' instruction
Execution of a reserved instruction
Execution of non-RSX EMT.
Execution of a trap instruction,
PDP-11/40 floating point exception

01
02
03

04
05

WD.

If the table does not exist and one of the errors or instructions
listed in the table above occurs, the task is aborted. Likewise, the
task is aborted if the table exists but does not contain an entry
point that corresponds to a particular error or instruction and that
error or instruction occurs.
The table does not exist if SVOB$ was not specified or
call contained incorrect parameters.

the

macro

SST service routines must save and restore all registers used.
Macro Call: SVOB$

adr,len

adr = Address of SST vector table
len = Number of entries in table
The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
S.VDTA = (Length 2 bytes) table address
s.VDTL = (2) Table length
DSW return codes:
+01
-98

Successful completion
Part of DPB or table is out of task's address
space, or table address not specified (zero
address)
DIC or DPB size is invalid

-99
Macro Expansion:
°"V >H

S'Hf;iL,"

.~'fT~

'H. 3

• ·Oiofl)

SS Tf ~L

• "tH'J

3-61

SVTK$
3.48

SVTK$ (SPECIFY SST VECTOR TABLE FOR TASK)

The SPECIFY SST VECTOR TABLE FOR TASK directive specifies the virtual
address of a table of synchronous system trap service routine entry
points for use by the issuing task. When both the issuing task table
and the ODT table exist and both contain an entry for a particular
trap, the ODT table takes precedence. SS~s are described in Section
4.2.
The table can contain up to eight entry points.
Each entry point
corresponds to a type of error that could occur or an instruction.
The table is in the ·following format.

wo.oo

Odd address error,
Segment fault
T-Bit trap or execution of a BPT instruction
Execution of an IOT instruction
Execution of a reserved instruction
Execution of non-RSX EMT,
Execution of a trap instruction
PDP-11/40 floating point exception.

WD.01
WD.02
WD.03
WD.04

wo.os

WD.06
WD.07

If the table does not exist and one of the errors or instructions
listed in the table above occurs, the task is aborted. Likewise, the
task is aborted if the table exists but does not contain an entry
point that corresponds to a particular error or instruction and that
error or instruction occurs.
The table does not exist if SVTK$ was not specified or
call contained incorrect parameters.

the

macro

SST service routines must save and restore all registers used.
Macro Call:

SVTK$

adr,len

adr a Address of SST vector table
len = Length of (number of entries in) table
The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
s.VTTA = (Length 2 bytes) table address
S.VTTL = (2) Table length
DSW return codes:
+l
-98

Successful completion
Part of DPB or table is out of task's address
space, or table address is not specified (zero
address)
DIC or DPB size is invalid

-99
Macro Expansion:
SVT!<'
.~~YTF.
• i'it)~;)
.l~11M

ssrP4L,2
1 ·-~ 'i. , 3
S:HT ~'-

3-62

SYNC$
3.49

SYNC$ (SYNCHRONIZE)

The SYNCHRONIZE directive requests a task at a specified future time,
and optionally, repeats it periodically.
The schedule time is
specified in terms of delta time from clock unit synchronization.
Clock
unit
synchronization
is
specified for a future time.
SYNCHRONIZE differs from RUN in that RUN requests task execution for
delta time from the present time, not delta time from a future time.
The SYNCHRONIZE directive cannot be issued by a background task.
Macro Call:

SYNC$

tsk,prt,pri,ugc,upc,smg,snt,sync,rmg,rnt

tsk
prt
pri
ugc
upc
smg
snt

• Task name,
= Partition name,
• Priority,
• UIC group code,
• UIC programmer code,
=Schedule delta magnitude1 i.e., how many delta units
• Schedule delta unit,
1 • clock ticks
2 = seconds
3 • minutes
4 = hours
sync = Synchronization unit,
rmg = Schedule interval magnitude,
rnt = Schedule interval unit.

A partition cannot be specified for a multiuser task1 i.e., the
must be requested to execute in its default partition.

task

The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
S.YNTN = (length 4 bytes) task name
S.YNPN = (4) Partition name
S.YNPR • (2) Priority
S.YNGC • (1) UIC group code
(1) UIC progranuner code
S.YNPC
S.YNSM = (2) Schedule magnitude
S.YNSU • (2) Schedule unit
S.YNSY • (2) Synchronization
S.YNRM • (2) Reschedule magnitude
S.YNRU = (·2) Reschedule unit

DSW return codes:
+l
-01
-02
-03
-80
-91
-93
-94
-95
-98
-99

3-63

Macro Expansion:
S'NCS

T~I~,r,E~QL,55,1~0,1~~.6,2,3,101~

• fiVTE

1Q., t? •

.~AO'i~

/T~lS/

.f(AO'i'-11
.. i-i0~i1
.Mr TE

1r.E'J~LI

.l·i~w:"\

tnJ,1'!0

.l•JwRi)

• lo'! :i ~ !)

.iH~~,,

:J
U'I

• It.' ~Iii I)

3-64

UFIX$
3.50

UFIX$ (UNFIX)

The UNFIX directive negates a FIX directive that has been issued to
make a task permanently memory-resident. The task specified in the
UNFIX directive must have the same TI as the issuing task.
The task
then can be removed from memory.
UNFIX cannot be issued by a
background task.
Macro Call:

UFIX$ task

task = Task name,
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
U.FXTN = (length 4 bytes) task name
DSW return codes:
+l
-02
-09

-so

-98
-99

Successful completion
Task not installed
Task is already unfixed
Directive issued by background task
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
Ufl(~

PN1l.

.P.YTE
·"A[J;e"

F7.,~

/POCL/

3-65

VRCD$
3.51

VRCD$ (RECEIVE DATA)

The RECEIVE DATA directive receives a variable-lenqth data block that
has been queued for it accordinq to priority. The SEND DATA or SEND
DATA AND RESUME OR REQUEST RECEIVER directives queue data for a
receiver.
When a sender task is specified, only data sent by the indicated
is received.

task

If the buffer size is not specified, a default size of 13 words is
used. A 2-word sendinq task name and the data block are placed in the
indicated buffer. The task name is in the first two words.
The
buffer lenqth should not include these two words.
If the location to store the TI is specified, the TI indicator
transferred from the SEND/RECEIVE node to this location.

If the receiver task is
assiqnment is received.

multiuser,

only

data

with

the

same

Data is transferred from the sending task to the receivinq task by
means of nodes picked from the pool. The number of nodes picked is
charqed to the sender. When the data is received, the nodes are
returned and subtracted from sender's usaqe count.
Macro call:

VRCD$

task,bufadr,buflen,ti

task
• sender task name
bufadr • buffer address
buf len = buffer lenqth
ti
• address to store TI
The following symbols are locally defined with their assiqned values
equal to the byte off set from the start of the DPB to the respective
DPB elements.
R.VDTN • (length 4 bytes) task name
R.VDBA • (2) buffer address
R.VDBL = (2) buffer length
R.VDTI • (2) address in which to store TI
Condition codes1

cc-c - cleared to indicate successful completion.
cc-c - set (with cc-v unaltered) if rejection occurs.
cc-v - set if sender task is privileqed

3-66

DSW return codes:
+01
-02
-08
-15
-89
-98

successful completion
sender task not installed
no data queued (sent)
receiver's buffer too small, data truncated
invalid buffer size (>255)
part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid.

-99

An alternate macro call is RCVD$ which receives a 13-word data block.
Macro call:

RCVD$

task,bufadr

Macro Expansion of VRCD$:
v~~~s
.H1T~

OT~~~.DATAIN,25.,TlAOOR
7~.,i$1Tq

.rt\0"i0

/!JTHF.R/
!)\T4!:'11

.'1-!!J~fl

.!IF

~~lTq.~,.WORO

25 •

• 1.'. ~F

~".l

t;·.ssT·~ ..

'flAODR

n, .wn1rn

3-67

VRCS$
3.52

VRCS$ (RECEIVE DATA OR SUSPEND)

The RECEIVE DATA OR SUSPEND directive receives a variable-length data
block that has been queued according to priority for it or suspends if
no data blocks can be received. The SEND DATA and SEND DATA AND
RESUME OR REQUEST RECEIVER are used to queue data for a receiver.
This directive cannot be issued by background task.
When a sender task is specified, only data sent by the indicated
is received.

task

If the buffer size is not specified, a default size of 13 words is
used.
A 2-word sending task name and the data block are returned in
the indicated buffer. The task name is in the first two words.
The
buffer length should not include these two words.
If the location at which to store TI is specified, the TI indicator is
transferred from the SEND/RECEIVE node to this specified location.
If the receiving task is
assignment is received.

multiuser,

only

data

with

the

same

Data is transferred from the sending task to the receiving task by
means of nodes picked from the pool. The number of nodes picked is
charged to the sender. When the data is received, the nodes are
returned and subtracted from sender's usage count.
Macro call:

VRCS$

task,bufadr,buflen,ti

task
= sender task name
buf adr
buffer address
buf len
buffer length
ti
= address in which to store TI

=
=

The following symbols are defined locally with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
R.VSTN • (length 4 bytes) task name
R.VSBA = (2) buffer address
R.VSBL = (2) buffer length
R.VSTI
(2) address in which to store TI

Condition codes:

cc-c
cc-c
cc-v

- cleared to indicate successful completion.
- set (with cc-v unaltered) if rejection occurs.
- set if sender task is privileged

DSW return codes:
+01
-02
-15

-so

-89
-98
-99

successful completion
sender task not installed
receiver's buffer too small, data truncated
directive issued by background task
invalid buffer size ()255).
part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid.

3-68

An alternate macro call is RCVS$ which receives a 13-word data block.
Macro call:

RCVS$

task,bufadr

Macro Expansion of VRCS$:
J Q c 5 .;

T t\ -; '( -? I l_I AT A I ~J ' 1 "' • , T I A f) [Hl

.~VT~

l~.,$~1Tq

4~.\1')5~

/TAS~?/

• :..i:) ~ ")

HT A r :,J

.t!F

~~~Tq.,,.WQP~

.!tF f1

;~~Tq-~,.~n~~

3-69

VRCXS
3. 53

VRCX$ (RECEIVE DATA OR EXIT)

The RECEIVE DATA OR EXIT directive receives a variable-length data
block that has been queued for it according to priority or exits if no
data block can be received. The SEND DATA and SEND DATA AND RESUME OR
REQUEST RECEIVER directives queue data for a receiver.
When a sender is specified, only data sent by the
received.

indicated

task

If the buffer size is not specified, a default size of 13 words is
used.
A 2-word sendinq task name and the data block are returned in
the indicated buffer. The task name is in the first two words.
The
buffer length should not include these two words.
If the location to store TI is specified, the TI indicator
transferred from the SEND/RECEIVE node to this specified location.

If the receiving task is
assignment is received.

multiuser,

only

data

with

the

same

VRCX$

task,bufadr,buflen,ti

task
= sender task name
bufadr • buffer address
buf len • buffer lenqth
ti
• address at which to store TI
The following symbols are locally defined with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
R.VXTN •
R.VXBA •
R.VXBL •
R.VXTI •

(lenqth 4 bytes) task name
(2) buffer address
(2) buffer length
(2) address in which to store TI

Condition codes:

cc-c
cc-v
cc-c

- cleared to indicate successful completion.
- set (with cc-v unaltered) if rejection occurs.
- set if sender task is privileged

DSW return codes:
+01
-02
-15

-89
-98
-99
An

successful completion
sender task not installed
receiver's buffer too small, data truncated
invalid buffer size ()255)
part of DPB or buffer is out of task's address
space
DIC or DPB size is invalid.

alternate macro call is RCVX$ which receives a 13-word data block.
Macro call:

RCVX$

task,bufadr

3-70

Macro Expansion of VRCX$:

Ii\,., T U•)i)R

'JRr;n

T~i;;(Q, 11UFIN,

.dYTF.
• :u L1Cj0

11.,~ .

.wCJ~I')

~ll.JF I r-J

.ttF GF.

$1~Tq·~ •• wnP~

urq

ITHl(q/

.tu: F,tl ~JiTq•e •• w~~u

flAOOR

3-71

VSDA$
3.54

VSDA$ {SEND DATA)

The SEND DATA directive queues a variable-length data block
to priority for a task to receive.

according

If the buffer size is not specified, a default of 13 words is used.
When an event flag is specified, a significant event is declared if
the directive is performed;
the indicated event flag is set.
Normally, the event flag is used to trigger the receiver into some
action.
The user must distinguish between the task's event flags (1
through 32) and the systems's event flags (33 through 64).
To be
effective, the task must set a system event flag.
If no priority is specified, the priority of the sending task is used.
If a TI is specified for the receiving task, the specified TI is
inserted in the SEND/RECEIVE node; an AST is declared if an active
task with the same TI is found. If no TI is specified, the sender's
TI is inserted in the SEND/RECEIVE node; an AST is declared if the
task is active regardless of its TI.
Data is transferred from the sending task to the receiving task by
means of nodes picked from the pool. The number of nodes picked is
charged to the sender. ·when the data is received, the nodes are
returned and subtracted from sender's usage count.
Macro Call:

VSDA$ task,bufadr,buflen,efn,sndpri,ti

task
= receiver task name
buf adr = address of data block
buflen = length of buffer (1 through 255 words)
efn
= event flag nwnber (O implies no event flag)
sndpri = priority of send (1 through 250)
ti
= TI indicator
The following symbols are defined locally with their assigned values
equal to the byte offset from the start of the DPB to the respective
DPB elements.
S.DATN = (length 4 bytes) task name
S.DABA = (2) buffer address
S.DAEF = (2) event flag number
S.DABL = (2) buffer length
s.DASP = (2) send priority
S.DATI = (2) TI indicator

3-72

DSW return codes:
+01
-02

successful completion
receiver task not installed
insufficient pool nodes for SEND
invalid TI
invalid buffer size (size > 255)
invalid event flag number (event f laq number < O or

-04

-as

-89
-97

64)

part of DPB or data block is
space
DIC or DPB size is invalid

-98
-99
An

out

task's

address

alternate macro call is SDAT$ which sends a 13-word data block.
Macro call:

SDAT$

task,bufadr,efn

Macro Expansion of VSDA$:
l~l~i

TAa<J,lATA,~4,1~,~~~.TIAPOR

• ;vrE

11., n-;rq

.~\1)C)~;,

/q:;"<~I

• "LH'.l

H TA

... ,·~1)

3..,

• r {r ·:; E ;; HT q • ., '

.lt~

Li~

~~'Hq-~,

• -~ ~HH> ;. "
•"'ORO r?~rn

.1r~

i~ir~-A.,

•

1t1 ~ 0

3-73

TI Al'l!H~

VSDR$
3. 55

VSDR$ (SEND DATA AND RESUME OR REQUEST RECEIVER)

The SEND DATA AND RESUME OR REQUEST RECEIVER queues a variable-length
data block according to priority for a task to receive and to rPqnf•f1 ~
or resume the execution of the receiver.
This directive canuol '"·~
issued by a background task.
This directive has the effect of issuing a SEND DATA directive
followed by a REQUEST directive with the following exceptions:
1.

No task switching occurs between the SEND and the RECEIVE
RESUME,

If the SEND is not performed,
REQUEST is attempted.

the

neither

the

RESUME

nor

If the buffer size is not specified, a default buffer size of 13 words
is used.
When an event flag is specified, a significant event is declared if
the directive is performed;
the indicated event flag is set. The
event flag is used commonly to trigger the receiver into some action.
The user must distinguish between task event flags (1 through 32) and
system event flags (33 through 64).
To be effective, the task must set a system event flag. If the send
priority is not specified, the priority of the sender is used to
insert the SEND/RECEIVE node into the receiver's queue.
If a TI is specified for the receiving task, the specified TI is
inserted in the SEND/RECEIVE node. An AST is declared if an active
task is found with the same TI and the task has specified RECEIVE AST.
If no TI is specified, the TI of the sending task is inserted in the
SEND/RECEIVE node;
an AST is declared if the task is active
regardless of its TI.
Data is transferred from the sending task to the receiving task by
means of nodes picked from the pool. The number of nodes picked is
charged to the sender. When the data is received, the nodes are
returned and subtracted from sender's usage count.
Macro calls

VSDR$

task,part,pri,ugc,upc,bufadr,buflen,efn,sndpri,ti

task
= receiver task name
part
• partition
priority
pri
uqc
UIC group code
upc
UIC programmer code
buf adr
address of data block
buf len • length of data block in words
efn
• event flag number (O implies no event flag)
sndpri • priority of send
ti
TI indicator

---

3-74

The following symbols are locally defined with their assigned values
equal to the byte offset for the start of the DPB to the respective
DPB elements.
s.DRTN •
s.DRPN •
s.DRPR •
S.DRGC a
S.DRPC •
S.DRBA •
s.DREF •
S.DRBL •
s.DRSP •
S.DRTI -

(length 4 bytes) task name)
(4) partition name
(2) request priority
(1) UIC group

(l) UIC programmer
buffer address
event flag
buffer length
send priority
TI indicator

(2)
(2)
(2)
(2)
(2)

DSW return codes:
In the following code descriptions, R indicates that the
REQUEST or RESUME was rejected, and B indicates that both the
SEND and REQUEST or RESUME were rejected.
+01 - data sent and task requested
+02 - data sent and task resumed
+03 - data sent to a non-suspended task
-01 - [R] insufficient pool nodes available for REQUEST
-02 - [B] receiver task not installed
-03 - [R] partition too small for receiver task

-04 - [BJ insufficient pool nodes for SEND
-06 - [R] handler task not resident to load task
-OS - [R) receiver task is disabled
-so - [B] directive issued by background task
-as - [B] invalid TI indicator
-89 - [B] invalid buffer size (>255)
-91 - [R) invalid uic
-94 - [R] partition not in system
-95 - [R] invalid priority specified C<O or )250)
-97 - [B] invalid event flag number (efn<O or >64)
-98 - [B] part of DPB or data block is out of the
address space
-99 - [B] DIC or DPB size is invalid.

task's

NOTE
The SEND portion of this directive can
complete and the REQUEST portion fail.
An alternate macro call is SDRQ$ which sends a 13-word data block.
Macro call:

SORO$

task,part,pri,ugc,upc,bufadr,efn

3-75

Macro Expansion of VSOR$:
JS H~

V1J,PA~T,a~,~~~,2~~,MYOATA,3~,&~,3~,TIAOD~

• ~'I Tr:

13.,~:;;rq

.~A!)'i'J

l'f.1U.1
' ' ' f 1 • ·~ ,
/Pt\l'lT I

.IIF t.T
• ~ Ut;'°'
• ;JQQr}

• ~.J 0 R :J

r;11

.~HE

?~':i, ~~-,

.~i1·1~,,

~11·U

·r A

• w1Rn
.l!F

l$~f1·1~ ••• ~nRn

• I! F

GS:

$~~Tq•l 1., .~.,U~J

.t~F

~~$Tq·1~.,.~0RO

flAOU~

3-76

WSIG$
3.56

WSIG$ (WAIT FOR SIGNIFICANT EVENT)

The WAIT FOR SIGNIFICANT EVENT directive suspends execution of the
issuing task until the next significant event occurs. It is an
especially effective way to suspend a task which cannot continue
because of a lack of pool nodes.
Macro Call:

WSIG$

DSW return codes:
+1

Successful completion

Macro Expansion:
WStG'

.evre:

3-77

WTLO$
3.57

WTLO$ (WAIT FOR LOGICAL OR OF FLAGS)

The WAIT FOR LOGICAL OR OF FLAGS directive suspends the execution of
the issuing task until any indicated event flag of one of the
following groups of event flags is set.
GR 0
GR 1
GR 2
GR 3
GR 4

FLAGS 1-16
FLAGS 17-32
FLAGS 33-48
FLAGS 49-64
FLAGS 1-64

If the indicated condition is
effectively not suspended.

met

issuance,

task

execution

Mask word bits from right-to-left represent increasing event flag
numbers.
A set mask word bit indicates that the task is to wait for
the corresponding event flag.
Macro Call:
set •

WTLO$

set,mask

Desired set of event flags

mask • If set is 0,1,2,J, mask is a 16
word1

bit

(16-flag)

mask

If set is 4, mask provides a list of four mask
in the form: < Ml, M2, MJ, M4>.

words

If zero is specified in the $S form of the macro,
not use a nwnber sign (I) preceding it.
Example:

The following macro is used to wait for flag 19, or flag 20,
or flag 21, or flag 32.
WTLO$

Example:

1,100034

This macro waits for 1, 19, 20, 21, 32 or 64.
WTLO$

4,<00000l,100034,0,100000>

DSW return codes:
+l
-97
-98
-99

Successful completion
No event flag specified in mask word(s)
or1 Flag set indicator other than 0,1,2,3, or 4
Part of DPB is o~t of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
wTLO'

l.l 1 <t,5r1'~,2,343>

.svn:

43.,'5

• lti Oi:tl'l
• w'.)~!')

l
5.:i1 ~
?.

.~,~,,

31n

.w~.~i)

3-78

WTSE$
3.58

WTSE$ (WAIT FOR SINGLE EVENT FLAG)

The WAIT FOR SINGLE EVENT FLAG directive suspends the execution of the
issuing task until an indicated event flag is set. If the flag is set
at issuance, task execution is effectively not suspended.
Macro Call:

WTSE$

efn

efn • event flag number
The following symbol is locally defined with its assigned value equal
to the byte offset from the start of the DPB to the DPB element.
W.TSEF • (Length 2 bytes) event flag number

osw return codes
+l
-97
-98
-99

Successful completion
Invalid event flag nwnher C<l or >64)
Part of DPB is out of issuing task's address space
DIC or DPB size is invalid

Macro Expansion:
~rse~

.~VT~
.11~~

3-79

CHAPTER 4
SIGNIFICANT EVENTS AND SYSTEM TRAPS

Understanding of trap logic and
PDP-11 Processor Handbook is
chapter.

EMT handling as described in the
a prerequisite to understanding this

Significant events and system traps are the
means
by
which
communication is effected among various parts of the system. Events
and traps appear to overlap in some areas, but three points may help
to clarify their function and use.

4.1

A significant event causes a change in
causes the Executive to re-evaluate
execution of all tasks.

System Traps are exclusive to a single taskJ
for intra-task communication and control•

The occurrence of an event can only change the eligibility of
a task to run_. A trap, however, is a real interrupt; the
sequence of instructions being executed by the task is
interrupted and control is transferred to another place in
the program. This process may be invisible to the user in
some cases.
However, it is a difference between events and
traps.

system status1
it
the eligibility for
they are useful

SIGNIFICANT EVENTS

Significant events provide a mechanism for achieving dynamic control
of
task
execution.
Tasks are able to declare and recognize
significant
events
through
event-associated
directives.
The
declaration and occurrence of significant events provide dynamic
control over the execution of tasks. Waiting for an event, such as
the waiting for an I/O request, can suspend a high priority program
witil that event occurs.
Meanwhile, lower priority programs ar~
allowed to run.
Event flags.are the means by which RSX-llD and tasks distinguish one
event from another.
Associated with each task are 64 event flags.
The first 32 flags (1-32) are unique to each task, and are set or
cleared only as a result of that task's operation. The integrity of
these flags is maintained by the task. They are stored in the task's
ATL and are not available to other tasks.

4-1

The second 32 flags (33-64) are common to all tasks, and can be set or
cleared as a result of any task's operation. Therefore, they require
system management to preserve their significance and are stored in
SCOM.
Event flags usually are set when significant events occur, and tasks
can read and/or clear them using system directives. Also, task
execution can be suspended until a particular event flag or a logical
combination of event flags is set.
Some system processes running for the user need event flags. The last
eight local (25-32) and global (57-64) event flags are reserved by
convention for use by RSX-110. Accounting uses flags 61 and 62.
In addition, device handler tasks use event
requests and event flag 2 for normal requests.

flag

for

express

All significant events occur as the result of a task's havinq issued a
system directive,
some directives have the event explicitly noted,
while in others it is implicit. Refer to Chapter 3 for a complete
discussion of the directives.
1.

The DECLARE SIGNIFICANT EVENT directive allows any task
stimulate the event-driven system whenever necessary;

The SEND, SEND AND RESUME OR REQUEST, or RESUME
also cause a significant event at issuance,

The directives that cause task execution (REQUEST, EXECUTE,
SCHEDULE, RUN, and SYNCHRONIZE) also cause a significant
event whenever task execution is initiated,

The MARK TIME directive causes a siqnificant
specified time interval after issuance,

Most I/O operations (initiated by the QUEUE I/O directive)
cause
a significant event upon completion.
Successful
completion of the QUEUE I/O directive itself causes a
significant event.

The following examples show the usaqe of the conunon
task synchronization.

event

directives

event

flags

for

Example l -- Global Flaqs
Task B specifies a global event flag (e.q., event flag number 35) in a
WAITFOR directive, and task A specifies the same event flaq in a SET
EVENT FLAG directive at the time it is appropriate for task B to
proceed.
Example 2 -- Global Flags
Task A specifies task B and a qlobal event flag in a SEND directive.
Task B has specified the same common event flaq in a WAITFOR directive
and issues a RECEIVE directive (to dequeue a block of data sent by
task A) when activated because the WAITFOR is satisfied.
Following are examples of event flag usage to detect I/O completion,
and to indicate that a specified period of time has elapsed.

4-2

Example 3 -- Local Flags
If an event flag is specified in QUEUE I/O and associated WAITFOR
directives, the flag is cleared when the request is queued. When the
task executes a WAITFOR predicated on the same event flag and the
requested action is not yet completed, execution of the task is
suspended.
The task performing the requested service sets the specified event
flag when the request is completed, and the task's execution is
resumed.
Example 4 -- Local Flags
If an event flag is specified in MARK TIME and WAITFOR directives, the
flag is cleared at MARK TIME issuance and set after the indicated time
has elapsed, and the task's execution is suspended for the indicated
interval of time.
In the above examples, computation and/or event flag testing are not
precluded prior to, or instead of, the WAITFOR directive, i.e.,
specifying an event flag does not imply that a WAITFOR directive must
be used.
Event flag testing can be performed at any time. The
purpose of a WAITFOR directive is to stop execution until an indicated
significant event occurs.
It is not necessary to issue a WAITFOR
directive immediately following the issuance of a QUEUE I/O or a MARK
TIME directive.

4.2

SYSTEM TRAPS

System traps are task interrupts initiated by the Executive to
servicing of certain conditions or situations that can occur.

allow

When a task plans to use the system trap facility, it must contain a
trap service routine. This routine is automatically entered when the
trap occurs with the task's normal priority and privilege. The action
taken by the Executive if a service routine is not supplied is
dependent upon the type of trap and is described below.
There are two types of system traps: synchronous system traps (SST's)
and asynchronous system traps (AST's).
SST's provide a means of servicing fault conditions within a task,
such as memory protection violation and PDP-11/40 floating point
exceptions. These conditions, which are internal to a task and are
not significant events, occur synchronously with respect to task
execution. In these cases, if an SST service routine is not included
in the task, the task's execution is aborted.

4-3

AST's conunonly occur as the result of a significant event and thus
occur asynchronously with respect to a task's execution, i.e., a task
does not have direct or complete control over when AST's occur.
A
characteristic of AST's is that they are for information purposes,
such as signifying an I/O completion that a task wants to know about
immediately and PDP-11/45 floating point exceptions.
If an AST
service routine is not provided, a trap does not occur and task
execution is not interrupted.
It should be emphasized that SST's only are initiated by the
Executive;
no further action. is taken. That is, they appear to the
Executive just like normal task execution.
The Executive having
initiated an SST, cannot determine that the task is in the SST service
routine. Thus, an SST service routine can be interrupted by another
SST or an AST. SST's can be nested.
SST's are caused by activities internal to the task, while AST's occur
as a result of an external event. The Executive keeps track of all
AST's, queues them (FIFO) and is aware of when a task is executing an
AST.

4.2.1

Synchronous System Traps

Before reading this section, it is advisable to review the
interrupt logic as described in the PDP-11 Processor Handbook.

vector

When an SST occurs, the task's PSW (program status word)
and PC
(program location counter) are pushed onto its stack, and return from
the SST routine is accomplished by issuing an RTI or RTT instruction.
Execution of an SST service routine is indistinguishable from task
execution, and an SST service routine can perform any operation that
the task can. However, if a service routine for a system trap is to
cause that same system trap to occur, it must be re-entrant.
SST service routine entry points are provided in a trap vector table
which is contained in the task. The trap vector table is described in
Section 3.41.
A zero address in the vector table is interpreted as if no entry point
were specified. If an SST occurs and no entry point is specified, the
task's execution is aborted. If an invalid address is specified as an
SST service address, an attempt is made to transfer control to the
address specified, which probably results in an odd-address or segment
fault.
The SST vector table is given to the monitor by the task by
use of the DECLARE SST VECTOR TABLE Directive.
On entry to an SST service routine, the stack contains
standard PDP-11 trap vector information:

SP+02

SP+OO

4-4

the

following

At the start of SST service, the stack can contain additional
information depending on the cause of the trap, as follows.
1. Segment Fault -

Segmentation Status Register 1
Segmentation Status Register 2
Segmentation Status Register 0
2. EMT Other Than 377 -

Instruction Operand (low-order byte) times two
Items 1 and 2, above, must be removed from the stack before the SST
exit is taken.
Exit from SST's is by means of an RTI or RTT
instruction.
The RTI or RTT instruction removes PC and PS from the stack.
The additional data is pushed on the stack by the RSX-llD interrupt
service routines. Seven trap service routines are provided as part of
the RSX-llD Executive. Table 3-2 lists the ISRs and describes their
functions.

4-5

Table 4-1

Executive Trap Service Routines
FUNCTION

ISR
Memory Parity Interrupt

Traps at location 114.
If a parity
error occurs at other than processor
priority zero (Executive code),
the
system is crashed.
If a parity error
occurs at processor priority zero, the
task's status is changed to task parity
error and the task is effectively locked
in memory and can execute no move.

Odd Address and
Miscellaneous Error

Traps at location 4. If the cause of
the trap is a red or yellow
trap
violation, the system crashes.If the
trap was in task code and the SST vector
table
is
defined, the SST service
routine executes.
If the SST vector
table
is not defined, the task is
aborted.
For other traps refer
to
Section 4. 2. 3.

Segment Faults

Traps at location 250. If the segment
fault occurs at other than task level,
the system is crashed. If the segment
fault was caused by task-level code, the
user task is notified by means of an SST
or aborted.

EMTs and Traps

Traps at locations 30 and 34.
If the
instruction is an EMT 377, control is
transferred to the RSX-110 EMT handler.
If the instruction was a .. trap and the
previous mode was kernel,· control is
transferred
to the directive status
return routine in the Executive.
For
other EMTs or traps, the user task is
notified by an SST or is aborted.

Bit and BPT

Traps at location 14.

IOT and Reserved
Instruction

Traps at locations 20 and 10.

Floating Point
Exception

Traps at location 244.
and AST for 11/45.

4-6

SST for 11/40

4.2.2

Asynchronous System Traps

When an AST occurs, the task's PSW and PC are pushed onto its stack.
There also can be other para..~eters pushed onto the stack depending
upon the cause of the AST.
After processing an AST, the trap dependent parameters must be removed
from the task's stack, and an EXIT AST SERVICE directive is issued
with the task's stack set as indicated in the description of the AST
SERVICE EXIT directive.
Upon AST service exit, control is returned to one of three placesz
1.

Another (queued) AST1

The task;

Another task
execution).

corresponding

task

was

not

Five variations on the stack format, depending upon
are as follows:

the

AST

origin,

(e.g.,

the

If a task is to be notified of power failure recoveries,
SPECIFY POWER RECOVERY AST directive is issued.
SP+04
SP+02
SP+OO

PS of task at AST (interrupt),
PC of task at AST (interrupt),
Task's directive status (virtual zero).

It is not necessary to pop any of this from the stack.
2.

When an I/O request is queued, an AST service entry point may
be specified in the macro. If specified, an AST occurs upon
c~mpletion of the request with the
task's stack containing
tni following information:
SP+l6
SP+l4
SP+l2
SP+50
SP+ 6
SP+04
SP+02
SP+OO

Event flag mask word for flags 1-16
Event flag mask word for flags 17-32
Event flag mask word for flags 33-48
Event flag mask word for flags 49-64
PS of task at AST (interrupt),
PC of task at AST (interrupt),
Task's directive status (virtual zero),
Address of I/O status block for request (or
zero if none specified). Must be popped off
stack before AST exit.

When a MARK TIME directive is issued, an AST service entry
point can be specified in the DPB. If specified, when the
indicated time interval has elapsed, an AST occurs with the
task's stack as followss
SP+l6
SP+l4
SP+l2
SP+lO
SP+06
SP+04
SP+02
SP+OO

Event flag mask word for flaqs 1-16
Event flag mask word for flags 17-32
Event flag mask word for flags 33-48
Event flag mask word for flags 49-64
PS of task at AST (interrupt) ,
PC of task at AST (interrupt),
Task's directive status (virtual zero),
Event Flag
number
(or
zero
if
none
specified).
Must be popped off stack before
AST exit.
4-7

If a task is to be notified of PDP-11/45 floating point
hardware exceptions, a SPECIFY FLOATING POINT EXCEPTION AST
directive is issued, and following floating point exceptions
will cause AST's to occur with the task's stack as follows:
SP+20
SP+l6
SP+l4
SP+l2
SP+lO
SP+06
SP+04
SP+02
SP+OO

Event flag mask word for flags 1-16
Event flag mask word for flags 17-32
Event flag mask word for flags 33-48
Event flag mask word for flags 49-64
PS of task at AST (interrupt) ,
PC of task at AST (interrupt),
Task's directive status (virtual zero),
Floating point exception code, must be popped
off stack before AST exit,
Floating point exception address, must be
popped off stack before AST exit.

For SPECIFY RECEIVE AST, nothing is placed on the stack. The
actual RECEIVE can be performed by the AST service routine.

The following are so~e general notes on the characteristics and use of
AST's.
1.

Two directives, INHIBIT AST RECOGNITION and ENABLE AST
RECOGNITION,
allow
AST's to be queued for subsequent
execution during critical periods. If AST's occur while AST
recognition is inhibited, they are queued (FIFO), and are
processed when AST recognition is enabled.

If an AST occurs while another AST is being processed, it is
queued (FIFO), and is processed when the preceding AST
service is completed unless AST recognition was disabled by
an AST service routine.

If an AST occurs while an SST is being processed, the SST
service routine execution is not distinguished from task
execution, and is interrupted for execution of the AST
service routine.

If an AST occurs while the related task is suspended, the
task remains suspended after execution of the AST service
routine unless explicitly resumed by the AST.

If an 1\ST occurs while the related task is waiting for an
event flag setting (WAITFOR directive), the task remains in a
wait state after execution of the AST service routine unless
an appropriate event flag is set by the AST or other routine.

If an AST occurs while the related task is in execution, the
task is interrupted for the execution of the AST service
routine. This interrupt is transparent to the task unless
the trap service routine changes the context of the task.

If an AST occurs while a task
remains checkpointed and the
after the task is reloaded.

4-8

is checkpointed, the task
AST is queued for execution

4.2.3

Processor Priorities

Seven processor priorities are used by the PDP-11, as described in the
PDP-11
Processor Handbook.
Peripheral device interrupt service
routines run at processor priority levels four through seven.
In
addition, software modules that cannot be interrupted run at priority
level seven for short periods of time.
Priority levels zero through three are used by the system as operation
indicators1
i.e., no software interrupts occur, and therefore, no
precedence is implied or invoked by levels zero through three.
Level zero is used exclusively for task execution. If a segment fault
occurs at level zero, a system trap is caused if the task has a
service routine to handle it. Otherwise, the task is aborted.
Level one is used for the servicing of trap type
EMT IOT, TRAP, and is used for the following:

instructions,

e.g.,

The processing of system directives (EMT 377s),

The causing of a synchronous system trap if a trap-type other
than BPT trap executes at priority one or the priority of the
interrupt service routine, whichever is higher.

Level two is used for the recognition of system events. These events
are indicated in the system event recognition flag called .SERFG and
are recognized only when returning to task execution, e.g., from an
interrupt or from a directive. System events are significant event
declarations, clock ticks, and power failure recoveries.
Level three is used for execution of routines that cannot be
interrupted
by
significant
event
recognition
or clock tick
recognition, but that can be interrupted by peripheral
device
interrupts, e.g., the system subroutine to dequeue a request for a
device handler task. In these cases, the level can be set to three by
any means, but it must be lowered to zero by transferring control to
subroutine •• ENBO to allow recognition of system events that might
have occurred while running at priority level three. The system trace
debugging routine also runs at level three.

4-9

APPENDIX A
SYSTEM LISTS AND TABLES

A-1

RS~llD •• ~~SI~E~T EXECUTIVE

EXEC MODUL~ O~E •• SY~80LIC
ttT8
"79

I
I

'680

't8l

>I
N

fe00Pl00

4h
4'81
488
489

1&1G'l000b

TPO •• TASK PARTITl~N OIR~CTOAV

000022

r WO. ~I CB 01)
r WD. Sl CB •2>
T.BA••04 , wo. 02 ce 04)
T.Pz••lb ' ~o. 01 (8 0~)
T.FW••10 I WO. 04 CB l~)
T.MP••1Z J wo. 05 (8 12)
T.RF••14 f ~O. 0& CB 12)
T,RB==lb f WO. 07 CB 14)
T.CF••20 J wo. 10 ce ze>
T.CB••22 I wo. 11 ca 2Z)

0eiee2"

T1 SZ••2U

kH'J~QlitG

001iHH0
~PI00U

000014
'6CJl!i>01 b
IO~IOV.20

T.P~a•00

•• PARTITION

~·~~

CFIR~T ~ALF,

•• PARTITION ~A~E (SECO~O MALf)

•• t/64TM BASE ~DDR~SS OF PARTITIQN (IN BYT~S>
•• 1/~UTM SIZE Of PARTITION (IN !VTESl
•• PARTITION FLAGS WOAD
•• tl~4T~ !ASE ADA ~F FIRST MOL!. OA 7ERO I~ ~o MnL'S~
•• MAL LtSTMEAO (FORWARD Lt~KAGE>
•• MRL LISTMfAO (BACKWARD LINKAGf)
•• CTL LtSTMEAD (FORWARD LI~KAGE)
•• CTL LISTMEAO (BACKWARD LtNKAC!)

•

qQ7

"98
'6~9

PAGE

.. 84
£t8S

49l
491
4CJ4
4q5
4'-1'0

l"•APA•T5 1215•

1 T~E "TPD" IS A FIXED LIST OF E~TRIES D£SCAI9INC ~A~M PARTJT!PN !N A
1 SYSTEM. TMIS DIRfCTOPV IS CRf ATfO BV TM! SYSTEM CON,IGURAT!DN
1 ROUTI~f CSYSCf~) CO~SISTING OF ENTRIES OF TM£ FOLL~WtNC ~~A~AT~

"81
tit&c

"'0
491

MACRO 00110

OEFINITIO~S

~00001

sei0

ioei0e02

~01

~0¥Je.01i

5fli

00~010

1SlZE CIN BYTES> OF TPD ENTRl!S

I
FLAGS WCAD BIT O!,INITIO~S1
1
TF.UCU0000Qlt
1(1~1 SET IF USER CONTROLLED PAAYITION.
TF. cu-=010012
t(0tl SET IF OCCU9!EC USER CCNTRCL~ED PARTtTT~~.
TF. TSH0H8f!4
1(021 SET IF l TI"£ S~lREO PAATITJ~N
TF • .tcn000011
tt011 1ET IF A Tl~! S~lAED PARTITJC~ !S ACTIVE

MSXt1D •• MESICENT EXECUTIVf
M•CRO 0~710
EXEC ~OOULt u~l •• SY~80~IC OEFINITIO~S
501.i

2"•APR•7~

508
509
S10

)11
51i
SU
SU
0e000U

G.BN:•04

~1q

~Y1'0~10
I000~12

G, 8AU10
G.CZ:=-12

520

0~001

~ll
~22

160~0i0

G,GSa•l',S

)::I
I

"'U!?l21

G,SA==21
G, Oln22

00002"

52&

~000i7

5C7

!000030

52&

G,P0=•24
G,FBs11ib
G,01•=27
G,ACs•30

~000l 1
I00~0l2

G,NAc•l2

0Ql00l4

G, 0An34

525

529
S30

00002&

531

t~O.

wo. 11 (8 22)
wo. 12 (8 24)
wo, u ce 2&>
wo,

G. 1Ccs31

000000
00~002

GS,LRQs:02

Sl~

0et000"

GS,LRS••01.1

GS,NUL••00

00000&

GS.LRF:=00&

538
539

0U052

GS. fH~Qn0s2

iJ00051.1

Sl.10

ia000So

GS, RRSn05"
GS,RRFne'So

k>00040

G,sz:1140
I
I

54&
547
Sl.19

tGLOBAL AREA NOT IN USE
1LOAO REQUEST QU~UED
tLOAO REQUEST SUCCEEDED
tLOAD REQUEST FAILED
tRECCRO REQUEST QUEUED
1RECCRO REQUEST SUCCEEDED
tRECORO REQUEST FAILED

544
545

St.i8

CREATION Tt~E (TWO WORes1 YEAR, MC~T~/DAY)
GLOBAL AREA STATUS
STARTING APR
OWNER IOE~TlFtCATION CUIC)
GLOBAL AREA TPD ADDRESS
FLAGS BYTE
•• CISI< I~DICATOR
ACTIVE REFEPENCE COU~T (BYYEl
INSTALLED REFERE~CE COU~T C8YTf)
•• I/O NODE ADDRESS
... GLOBAL ARf A OISI< ADDRESS

tTME FOLLOWING ARE GLO!•L AREA STATUSfS1

535

5£1i
Sl.ll

ce n>
ce 31'

14 CB 3lll)

wo. 1'5 (8 32)
wo. 1& (8 34)

s:u
s:u

s" 1

10 CB 20)
CB 21)

S3t?

~17

wo. 0& CB 11.1)

G.CTss1u

001ll0i2

~00,S

wo. 00 (8 00) •• FOR wAR 0 LI~ I<
wo. 01 CB P2) •• BACIOiARO LJNI<
wo. 02 (8 0l0
COM~ON BLOCK NA~E (6 C~AR t~ RAD!~-5~. 2-weAns'
WO, 04 CB UJ)
t/~4T~ BASE ADDRESS OF COM~ON ~LnCK
wo. 05 CB tz)
t/&4TM SIZE OF CO~MC~ BL9C~

515
Ste

GLOBAL CO~MCN AREAS ARE SMARABLE AREAS 0, ~E~ORY FOR USE AS
LIBRARIES, CR FOR co~~c~ DATA STORAGE.
f T~E "GCC" IS A LI~KEC LIST OF ENTRIES OESCRIBI~G EAC~ GLOBAL co~~ON
BLOCK I~ A SYSTEM. T~IS LIST IS CREATED BY INST~Ll
A~D CO~SISTS CF E~TRIES OF T~E FOLLOWING FOR~AT. NOTE T~AT Gen TYPE
ARE CREATED BY INSTALL fOR TM~ PURE AREAS CF ~ULTI•USER TA~K$, B~T
f T~ESE NCDf.S ARE NOT Ll~KED I~TO T~f Geo, BUT ARE POINTED TO ~y THE
t TASKS' STO ~ODES.

S07

S2l
524

PAGE

t GCO •• GLOB•L COMMON DIRECTORY

50~
~00

~17
~t~

1215&

lil00001
0000!02
000004

550

000010

551

0000i0

tSIZE CIN BVTES) OF GCO ENTRIES
FLAGS WCRO BIT

GF. E1u00eeei 1

GF. LIU000002
GF • RIn000H4
GF. Nwu000010

GF. NAU000020

t [001
1(011
1[021
1[031
1(041

DEFtNtTtO~S

EXISTE~CE JNCICATOR tSET W~E~.LI8 OA,CCMMON LOACED'
LIBRARY co~~o~ l~OIC~TOR •• t1~I8 eeco~
LIBRARY RELOCATABtLITV tNO?CATO~ ••SET FOR PI~ COO£
SET WMfN NON•OW~ER ~AS WRIT! ACCESS
SET WMEN ~ON•OW~EA ~AS READ ACC!SS

NSX11C •• RESICE~T EXECUTIVE
~•CAO 00710
EXEC ~OOUL~ ONE •• SY~BOLIC CEFI~ITIO~S
S53
55S
55b

~Set

!J:>I
I
~

THE "PUO" IS • ,IXEC LIST CF f~TRifS O~ScRrer~G fAC~ P~VSICAL OEVICE•
A SVSTE~. T~IS LIST IS CREATED 8~ T~! SV$TE~ CON'l~UR~TJON
CSVSGE~) A~D CO~SISTS OF E~TRIES OF TME ~CLLOW!NG '0A~AT1

000e0vi

U,Ct\:•00

000~02

u.u~•=02

u, Fene3
u.c1ueci

Sbl

~~0~03

Sb~

000004.l

563
Sci.I
Sb5
560
567

~000166

00001u

U1 AF:•14

!00012' 1 b

5&8

U1 RPcs16

~e~n0

Sb9

"01be22

~0001~
fcHH~012

~0"'02a

571

12100ne

S72

~0003"'

57l
574

00003U

ld00lH2

575
57o
"7 7
57S

U,C2••0b
U,Cl••10
U,CUs:•12

u.HA:•Z0

1J, xc••c2
U 1 RF1u24

U,AB:•26
U,TV•s:30
u.IPs:•32

u.ou:Ju
I
I

~01cHHt

Ll,Vl••3b

\?016~4.&0

U,Uic•40

t>i?.~12140

U,PCc:40

~82

0e"~"

U,GCn41

~00~~2

U, \1Pi::c:42

k10~21.i2

U,C,..••42

58~
~Bb

587

'°~~"~"

IO~!Ol?.4o

lJ,AR••4"

u.OACP==afl

see

~0!0050

u. ACP1n50

S69
590

~~0PS2

ld0~052

U,TFa:s52
u.PR:•52

00"105l
0011'0SU

U,F0•=53
u. LBt;i::aS"

sen

sqc
SH

wrn"esf>

U, LB~u:5~

5q"

5q5
59b

lllD, 00 (8 0111)
wo. 01 CB 02)

CB 03)

wo. ei2 ce u>

DEVICE ~A~E f2_ASCtI
U~IT

~V~BER

FLAGS CBVTE>

C~ARS)

CBVTEl

C~ARACTERIST!CS

WORO ONE (O!VICE

INDFP!~C!~T.I~D?C~T~AS>

wo. 01 CB 0~) •• CMARACTER!ST?CS WOAD T~O CD~VICf_OFPfNDE~T .lND!CATCR~).
wo. 04 (8 ll!l) •• c MAR ACT EA !ST res WORD T~RE!. c O!V l~f o,,~~O!NT - I ND TC~ TORS,
we, 05 ce tz>
CHARACTER!STJCS wopo FOU~ csu, 0, .BLOCIC, 8U~F~R. I IN!,
WO, 0b CB 14) •• ATTACH ,LAG CATL NOOE ADDR!SS O' ATTACMI~G TASK)
we. 07 CB 1~)
REDIRECT PCI~TER
wo. 10 CB 20) •• ~ANOLER TASK ATL ~ODE AODR!SS
wo. 11 CB 22)
COUNT O~ EXPRESS REQUESTS J~ QU!UE
wo. U <B 24)
UNIT REQU!ST DEQUE LiSTH!AQ f '~O P~TR)
, wo. u ce 26>
U~IT REQUEST OfQUf.LIST~EAC CBKO P~TR)
, wo. 11.& ce 10>
INTERRUPT TA~P VECTOR ADOR!SI _
i-o,

15 CB 32)

I~TfRRUPT

PRIORITY CtN BITS

wo. lb CB 34) •• CDEVtCE PAGE ADDRESS1

~·1)

RE~AI~OfR OF T~E PUD E~TRV IS A "VOLUME CCNTRCL BLOCK"~

~1q

561.t

' PHYSICAL UNITS ARE CO~SIOERED "VOLU~ES"
.
av THE f IL!S SVSTf~, AND T~E

!> 8 ki
581
~8l

1 UNIT I~
1 ROUTI~E

557

57111

P•GE

PUO •• P~YSICAL U~IT DIAECTOPV

554

55q
Sb"'

24•AP~•T5 12156

I0~0eto2

'
u.szu:b2

1i10.

1110. 20

ce 36>
ce 40>

re u>

wo,

._c.

CB 4'1)
21 CB U)

22
'1110. 21
we. 24
WO, 25

ce u>
ce l.IJ>
CB 44)

CB U)
CB 50)

<e 51>
wo. 25 CB 52)
(B 53)
wo. 26 CB 54)
1110. 27 (8 56)
wo. 30 (8 60)

ADDRESS OF VOLUME CO~TAOL BLOCk EXTENSfO~
USER IPE~T!FtCAT!ON COD! (U!C)
•• UIC PROGRAM~ER CODE
•• UIC GROUP COOE
VOLU~E PROTECTION WORD
•• C~ARACTfRteTtCS FLAGS
u
Rf SERVED BYTE
•• ACCESS R!G~TS FLAGS ~~AC
DEFAULT ACP NA~f, ~AC51 CFIRST_lllCRn)
STD ENTRY ADDR!SS 0' CURRE~T ACP
TERM?~AL FLAGS WORD _
TERMINAL PRIVILEGE BVTE
•• TERMINAL FOR~S BYTE
HIGH. ORDER •.TOTAL ~ OF ~LKS FPA DEVICE
•• LOW ORDER• TOTAL
OF BLOCKS ,OR DFVIC~
... RESERVED WOAC

1SIZE CIN BYTES) OF PUD ENTRIES

~q7

5qt;

FLAGS BVTE BIT

I
I

5q~

b00
b01

"~0~'40

b~2

0ee200
-'00100

b~l

0U~~40

UF.R0•=0"0
UF.Rfojc•200
UF • fLU100
uF. cn==0"0

I
I

1
I

001.t

oes

BIT

oh
"~~001

oeq

HSX110 ••
~x~c

::i::ii
I
U1

UC. CCLn000002
UC• T TYUQJ00U4

i1JQl00~"

"~&IDE~T

~OOULE

G~E

••

EXECUTIVE

SY~dOLIC

00001 QI

b11
b12
b13

I00~e'i~

b 1 ..

UC. REtn0u001

0~0002

~1(1~~"0
~00400

0r100e
002000

MACRO 00710

CE~I~ITIONS

UC• 0IR-=00BG'10
UC• SO In000020
UC.SlilD•=0e0eiae
uc.I~B==000400

uc. si.L==001 rme

0~~e00
01~~0~

UC. ISPn002001r.
UC. OSP==HIUH
UC. PSEH010el00

!021600~

UC• COf"n02eie100

01q

0~0000

02k)

1l"00~0

UC. Ft 1 UfiU&000QI
UC. M~Ta: 1 P0000

[71 SET W~EN MANCLER TASK rs D,C~ARED ~EStCE~T.
[61 SET WMEN ~ANCLER TASK RECOG~!ZES LCAC ANt AEeO~D
[5] SET WMEN DEV!C! rs CFFLINE
O~E

FCR CMARACTERISTtCS WOAD

1[001 SET !F RECORD OR!£NTED DEVICE cvtz,, TT, LP, CA)
1[011 SET tF CARRIAGE CO~TRO~ DEVICE <vtz •• TTL')
1(021 SET IF TTV DEVtCE tvtz •• kSA, LA10,

2"•APR•75 12156

010
017
018

t>1S

.
..
***********•TE~PCRARV•******************

DEFt~ITIO~S

007
o0S

CEF!NIT!O~S

PAGE

12•1

1[031 SET IF DEVICE JS A DIRECTORY D~VtCE
1(04'1 SET IF DEVICE rs A SINGLE OtRECTORY OEVICE
1[05] SET IF DEVICE rs A S~QUENTfAL DEvrtE.
1+003 [08] SET IF T~E DEVICE IS tNTER~fOtATE !UFFERE~
1£0q1 SET IF TME DevtcE is sc,+~~RE wRtTE Lcc~Eo
1C1e1 SET IF DEVICE rs INPUT SPOPLED
I [11] SET IF DEVICE rs OUTPUT SPOO~ED
1£121 SET IF OEVICE IS P~EUOO OEVI~E
1(13] SET IF OEV?CE rs COMMU~ICATICNS C~ANNEL
1(141 SET IF DEVICE IS F!LES•tl
1[151 SET IF DEVICE IS MOUNTABLE

b21
o2~

b21.1

000~04

BIT

DEFI~ITIO~S

uc.wcK=•000004

FCR CMARACTER!STtCS WORD TWO
-

1[021 SET IF A READ AFTER WRITE CMECK rs

REQUIRE~

02i;

BIT DEFINITIONS FOR VOLU~E CMARACTERISTICS BVT! U.C~

o2o
027
026

o2'i
Ol(r)
031

eu2e-0
~0kj 100

000~"0

Cl-4. OFF=-200

CM. FOR••U0
CM. U"L::ue

c1-1. ~nn20

032

000020
!000010

CM.NDCc:10

I00I00!01

C~.LABUl

o3"

1VOLU~E
1VOLU~E

IS OFF•LINE
rs FOREIGN

tDIS~OU~T PfhDING
1ATTACM/DETACH NOT PER~!TTEO.
1DEVICE CONTROL FU~CTICNS NOT PER~tTT!D
tVOLU~E tS LABELED TAPE

03!)

o3o

037

b36

03q

""0

000001

UT.PR•s1

l000Ui
000004

UT• SL.n,2
UT. L.G1u4

BIT DEFINITIONS ,OR TER~tNAL PRIVILEGE BVTE
tSET IF TTY IS PAtVLEGED
1SET IF TTV IS SLAVED
1SET tF TERMINAL IS LOGGED ON

RSX110 •• ~ESIOE~T EXECUTIVE
MACPO 00110
EXEC ~ODuLt O~E •• SV~80LIC OfFINITIO~S

2~•APR•75 121§~

PAGE

0£12
01.11

STD•• SYSTE~ TASK OIRECTORY

OCll.i

TME SYSTE~ TASK DIRECTORY IS A ME~ORY RESIDENT DIRECTORY or ALL TA~MS
WMIC~ MAVE BEEN ?~STALLED INTO A SYSTEM.
JMIS DIRECTORY CONSISTS ~~ TWO
PARTS1 (1) A FIXED SIZE AREA OF ONE WORD FOR EAC~ TASK TMAT ~AY
BE !~STALLED AT ANY TIME, AND (2) A~ STD E~TRV FeR EACM TASW TMAT TS

01.15

040
01.11
01.18
ol.19
b5IO

INSTALLED, TME FIXEO SiiED AREA IS CALLED TM~ "ALP~A TA8LE" ~NO
PROVIDES SPACE FOR AN ALPHABETICALLY ORDERED CONTIGUOUS LIST OF POTNT!RS
TO STD E~TRIES TO FACILITATE SEACM ~OR STD ENTRY BY TASM NA~,.
EACM STO ENTRY IS OF THE FOLLOWI~G FORMATi

051

oSi
o5J

000000

.TN••00 ' wO. 00 C

oss

~~'1001.i

o5o

0001110&

S.TD••01.i
S,Fws•0b

1110. 01 (
i-io. 02 c
~o. l'!l

057
058
059

000010
161'10011

S •OP•• 10
s.Dls•11

""o· 04 c

_,01d012

S,LZu12

~00011.i

S,TZ••14
S,AV••l&

051.i

);I
I

00001&

b&i

°'

eel

-'C?l0011

S.PV••11
S,PU••20

bb'f

0000i0
0000i2

00~021.l
00002~

S.DL=•2b

0HIZ'll

S, GCnlZ

us
807
068

S.RF . . 22

S.AB••21.i

b&9

00) •• TAS~ NA~E (~ CMAR IN RADYX·5~.
fl) •• CSECC~D MALF OF TASM ~AM!)

e4) •• DEFAULT TASk PARTITION

c 06) •• FLAGS ~CAD

wD• 0S

wo, 06

(
(
(
(
(

wo. 01
we. UC
we. 11 (
wo. 12 (
wo. 1l (

1110. 14 (

wo. 15 (

CTP~

z weAnS)

ADDRESS)

DEFAULT PRIORITY CB~TE)
•• ~YSTEM DISM ~NDieATOA CBYTE)
•• 1/64TM SIZE 0, LOAD IMAGE
•• il&4TM ~AX TASK SIZf
••~UMBER.~, ACTIVE VERSIONS. OF.T~Sk tBVT~)
•• TASk POOL LI~tT P!R VERJ!CN CBVTf)
•• TASM POOL UTtLIZAT!C~
•• RECEIV! DEQU! LtSTMEAD (FWO P~TR)
•• R!CE!Vf DEQU! LISTM!~D (BMG P~YRl
•• LOAD I~•GE FIRST BLOCK NU~BER t3~·~tTS)
CSECOND MA~F O~ OIIK •DDRE$S)
•• BEGINNI~G CF GCD POINTER AREA

10) ••

11)
12)
16)
16)
17)
20)
22)
24)
26)
31)
32)

070

1171
Uc

e7]

oh
017
078

TME SYSTE"1 CISK I~DICATCA SP£CIFl£S WMtC~ t/C A!QU!ST QU!U! TS
TO RECEIVE • "LOAC TAS~ l~AGE" RfQUESTt BY PROVJCtNG A "PUC fNTRV t~e!x•~
£.G,, A ZERO ~CULD t~DICATE TM£ ~EQUEST QUEUE 'OA T~! C!Vlt!•U~!T
REPRESE~TED BV TME ,I~ST (ENTRY ZERO) PUD ENTRY.
FLAGS WCRO BIT OEFl~ITIO~Si

I
0U0~Z

8,. 24 .. 00Uei 1
SF• FX . . 000H2

080

V'00001.l

081

S, • R"1H000004

000010

082

0000i0

Ul
OS'f

0000U

SF. TOH000010
S, • 8FU000020
SF .• XTH000QJIUI
SF'. MUU000100
SF .PTn0002u

000001

Wj00100

00U00

1(001
1[011
1(021
1[031
1[041
I [05]
1(061
1[07]

STD IS 24 WORDS LONG CD!,AULT IS t~)
SET WMEN TASK JS 'IX!D IN ~E~OAV
SET W~fN STD IS TO BE AEMOVEC
SET WMEN TASM IS O?SABLED
SET W~fN A TASK IS ~ftNG 'I~ED IN ~!~ORV
SET WHEN A TASK IS TO BE R!MeV!D o~ !X!T
SET W~fN TASM JS MULTI•USf~
SET W~EN TAS~ ts A PAIV!L!C!e TASK

080
087
088

I0~0UI00

~0100e

SF. ~T••0004e.0
SF.R1U00l000

b89

"'Qli"'00
004000

SF.Un00U00

Sf'. RZ .. 00i000

0~0

010000

091

!0216~00

oe>i

SF.XOU0100P0
SF. >nrn020u0

04000~

SF• )(Caa0U0H

o9J
o9"
095

00~U0

ocn

tSIZE OF STD lh BYTES

S,SU••32,

24•APR•75 1215•

™'

r wo. 00 CB 01) •• FORWARD LIM<AGE
r ~D. 01 (B 0l) •• BAC~WARO LINKAGE
r ~D. 02 CB 04)
~ODE ACCOU~Tt~G WORD CSTD E~TRV ADA 0, R!QUESTnR,

705
0000i"'

A,RQ••~ 1 Aw

709

~0"00~

7U
711
7li
7U
7U
715

A.TI••~.Tit~O.

0'110010

A,RP••l0 f

7Ut
717

0el00 l &

lt'0~~ l 1

00!01Z' 12

k)00013

A,IR••ll r
A,INs•U
A,CS••13

~O.

r WO,

r ~D.

000014

A,~T••14

000~15

A,CP••l5 '
A,MA••l• J WO,

VJ.a001&
000020
000021
ki0!0022

000024

A,NA••A,HA

0000Jl0

A,TS••~.se,wo,

A,ASuZl r
A,TD••22 S WO,
A,EF••24 J ~O,

722

72J
724'

PAGE

T~E "ATL" IS A PRIORITY ORDERED DEQUE OF "~TL". NCO!S FOR ACTfVE TAS~S
TMAT MAVE ME~CRV ALLOCATED FOR TMEIR EXECUTION. T~E TAS~S REPRE~ENT!D
BY E~TRtES r~ T~E ATL ARE EITMER ~!~CRV RESIDENT, OR A A~QUEST 'CR T~ftR
1 LOADI~G ~AS BEE~ QUEUED~
T~f LISTMEAD FDR TMt~ DEQU! !8 !~
~YST!M
I co~~U~ICATIO~S AREA CSCC~), ANO T~E ~ODES ARE OF TM! FOLLOW!~G ,OR~ATI

10&
70J

711
719
720
721

~ETWORK ATTRIBUTE BIT
RESTRICTED USAGE LEV!L ON~ ceACKGROUNO 8ATC~ JCB!)
RESTRICTED USAGE LEVEL TWO CUN!MPLE~ENTEC)
SET WM!N TAS~ IS N~VER TO BE A!O~TEO
S!T WMEN TASK tS NEVER T~ BE DtSABLfD
SET WMEN TAS~ tS NEVER TO BE FIXfO J~ ~f~CAY
SET WMEN TASM rs NEVER TO BE CMECMPOTNTEO
UNUSED en

ATL •• ACTIVE TASK LIST

.. q~
700
701

700
707
708

1(101
t[111
t[121
t[131
t[141
I (15]

bq8

......

t[0~l

ASXllO •• RESIDE~T EXECUTIVE
~ACRO 0~710
EXEC MOCUL~ O~t •• SY~BOLIC CEFI~ITIO~S

);"
I

' [08]

A,F~••ll

' 1'0,
WO.
J WO,

725

12•

' wo.

WO,

03 CB 0•>
TI !DE~TYFtCATtO~ • ~U~ ADOR!SS
04 CB ti) •• TASK•S AUN PAIPRITV tBYTf)
CB 1l) •• TASK 110 t~ ~RCC!SS COUNT (BVTE)
05 CB 12) •• TASK I/O PENDJNG_COUNT (BVTE,
CB 1]) •• SAVED STATUS OF CM!CKPCtNTfD TAS~
0• (8 14) •• TAS~ ~ARK TI~f P!NDING C~UNT (!V!!l .
CM,CKPOtNTED TASK t8VT~)
CB 15) •• ~AVED PRtORtTV
07 CB U•> •• tl64TM REAL ADA
LCAO !MAG!
•• I/O NOD! ADO~ESS WHEN TASK rs JN ~AL
10 (8 zeJ) ... TASI< STATUS. CBYT!>
(8 21) •• AST INDICATOR (P~f~IPU' STATUS> evt!
11 CB 22) •• SVST~M TASK DIAECTOAX (STOl ENTAV AODR~SS
12 CB 24) •• TASK'S !VENT FLAGS <t•~ll
u ce 2•> •• (SECOND ~AL, OF TASK'S rviNT 'lAGSl
14 (8 31> •• TASK'S fVfNT fLAGS MASKS ('4•8!TI)
15 (8 32) •• (SECOND WORD OF 'LAGS ~All<)
lb (8 !4) •• <T~tRD wbRo o,_,~•GS ~ASK>
11 (8 , . , •• CFOU~T~ WORD O' 'LAGS ~ASK)

727

~000U

728

000042
000044

729

730
731
73i
733
134'
735
73e

00004'~

~00052

00005U
0000Sb

737
738

A,PD••40 , ~o. 21 (8 41) •• TASK•s AU~ PARTITION CtPD. ~DDAESS)
A,AF••4Z r WD, 21 (B 42) •• AST DEQUE LIST~fAO ('WD PO,NTE~)
A,AB••44 r WD, 22 (8 44) •• AST D!QUE L!STMEAD CBKWD POJ~T~A)
A,IA••46 f ~D. 2J CB 46) •• TASK !~AC~ OJ~k ADDRESS
~o. 24
•• <SECOND WOAD D, IMAGE ADDR!SS)
INITIALLV • S.DL
CO~TAI~S CM£CKPOI~T AORS IF TASK is CMfCKPOi~T!D
l,TF••52 r ~D. 25 CB 52 •• TASK FL~GS
A,CF••54 r ~o. 2• (8 54) •• CHECKPOI~T T~SK LIST FCR~A~D_PO~~T!R
A,CB••56 r ~O. 27 CB 56) •• CHECKPOINT TASK LIST BACKWARD POtNT!R
TASk STATUS VALUES AA! DESCRIBED AT .ASXDT•

7H
740

BEFORE EXECUTJO~ , THE
FLAGS MAS~ WORDS ARE USED AS FOLLOwsi

741
74i
7" l
7h

A.F~+e
A.F~+4

745

74b
7" 1

AFTER

748
)=I
00

TAS~ EXECUTJO~,

750
751
75ii

flAGS WOAD BIT DEFINITIONS

ASX11D •• kESICE~T EXECUTIVE
MACRO 00710
EXEC ~ODULt O~E •• SY~BOLIC CEF!~ITIO~S
754

Z4•APR•75 12156

PAGE

14•1

755

1:100e01

7So

AF.CPnHl

0et0~~2

757
758
759

AF .Ron00z

00~0"'"

AF.•0••004

ICVJtiJ~10

lfJ0iar.i~

000e!l.l0

"00101?1
000200
~00'£00

AF,CCH010
AF,MC1:•0Z0
AF.GC••040
''· IOn100

AF, JTs•i00
A.F,GR••400

7b'4

00100~

!002000

7&D
1e7

01~000

AF,8F••1000
AF,F>Cs•2000
AF, A$H4000
AF,AAU10000

0et0~b~

A,SIZ••48,

lii~l.t~00

768
1b~

IS SET lS FOLLOWSi

8lT•q IS SET WMEN 110 RUNDOWN ~!SSAG£ IS RfQUiR!O.

75]

7o"'

.,,,~+0•

BIT•! IS SET WHE~ THE LOW PAD!~ ~VTE (81!9.l~J) CO~Tii~ •.
TER~I~ATION NCTI,tCATION CCO! CCOD!S D!SCRtB!D AT •st.CAt•'

71.1~

7U
7oc
7U

•• ADDRESS o~ TASK LOAD JIO R!QUEST D!QUE LISTH!AD,
•• TASk urc.

SET W~E~ TASK IS C~fCKPOiNTED
SET WME~ TASK•s 110 r~ B~I~~ AUN DOW~
SET WME~ TASK A~T RECOGNITION tS INHt8ITED
SET WMEN CMECKPO!NTING IS DISABLED
SET W~EN TASK IS ~ARKED FOR C~!CKPOINT?NG
SET WME~ TASK IS MOLDING A, co~~A~P BUFFE~
SET WME~ TASK MAS AN 110 CC~PL,TIO~ EV!NT IN ITS, AST QU!UE
SET W~EN TASK HAS AN INTER~EDIATE TR~NSFEA t~ PR~G~ESS
SET WME~ TASK'S SMAR~O GLOBAL AREAS MAVE BEE~ RELEASro
SET W~EN A TASK IS TQ BE FIXED
SET WM£~ A TASM IS FIXED
SET W~E~ A~ AST MAS BEEN OfCLAAEC
SET W~f~ TMERE IS A POTENTIAL REtEIV~ AST
tSIZE

OF ATL IN BVTES

RSX110 •• "ESIOE~T EXECUTIVE
MACRO 00710
EXEC ~COuLE O~E •• SY~80LIC CEFI~ITIO~S
771
77C
77l

714
775

~RL

24•APR•75 1215b

••

~E~ORY

PAGE

REQUIRED LIST

TME "~RL" IS A PRIORITY ORDERED PE~UE OF "ATL"_NCDES ~OR_ACT,VF TAS~S
TMAT REQUIRE ~E~DRY I~ A PARTITID~. EAC~ PART,T!ON ~AS JTS OWN ~RL.
~~E~EVER A ~O~•FIXED TASK RUNNING ~N A PARTITION E~ITS, AN, . _
I ATTf ~PT IS ~ADE TO ASSIGN ~E~ORY TO TME FIRST (H!GMEST PRtnRTTV)
1 TASK IN T~E LIST.
IF ~E~ORY IS FCU~D, TME TASK;S NODE_IS
~OVEC FRO~ TME "MRL" TC THE "ATL" OEQUE.
l~E ~RL Lt!TMEAD IS TN
T~E TPD E~TRY FOR T~E CCRRESPONDtNG PARTITION.

7h
777
71~

77q
780
781

RSX11D •• ~ESIO~~T EXECUTIVE
~ACRO 00710
EXEC MODULE O~E •• SY~BOLIC CEFI~ITIO~S

2"•APR•75 t215b

PAGE

783
786'
):>!
I
\0

785

CTL •• CMECKPCI~TABLE TASK LIST

787
788

T~E

78&

"CTL" IS A PRIORITY ORDERED CE~UE OF ENTRIES FO~ C~fCK~OTNY,AUL~
T~AT ARE ACTIVE I~ A PARTITIO~.
EACM PARTJTTC~ MAS ,TS ow~
CTL. T~E CTL LIST~EAO IS IN T~E TPC ENTRY FOR T~E CDRAESPDNOI~G
PART IT IO~,
T~E CTL IS REALLY JUST A RELI~KI~G CF T~E ATL, ~CWfVER, AND ~AS
~o U~IQUE ~CDES OR FCR~AT CF ITS o~~.
. ~
.
T~E CTL FOR~ARC A~D BACKWARD POI~TERS ARE TME LAST TWO.WORDS t~
T~f ATL ~COE, A~O , CC~SEQUENTLY, ~EGATIVE OFFSETS ~UST ei_DFf1NPO
SO T~AT PARA~ETERS ~AV BE REFERE~CEC WIT~ A!SPECT TC T~E CTL fORWA~C
TAS~S

78q
7q0
7q1
1fii.
JqJ
7(J6'

7q5
7q"

POI~TER.

7fi7

7q5
7qq

800

177710
1 '177b4

,RQ:•A.RQ•A.CF
1<.PO:•A,PO•A.CF
1<.RP:•A.RP•A.CF
1<.IR••A.IR•A.CF

801

177'1lU
1777l5
177731)

8Pl

K.IN••Ael~•A.CF

1777"0

K.MT:•A.MT•A.CF
K.CP••A,CP•A.CF
K.NA:•A.NA•A.CF
K,HA••A,MA•A.CF
K.TS:•A.TS•A.CF
K.AS••A,AS•A.CF
1<.TD••A,TD•A.CF

e0c

8~"

117741

805

1777ij2

60f)

1777U2
177hU

807

sea

177h'5

e0q

17771HJ

810
811
812

813
81't

ens
81~

817
818

E~EC

1<,FM••A1F~•A.CF

K,TI••AeTZ.A,CF
1< 1 AF1uA.AF•A.CF
1<,AB••A,AB•A.CF
K, IA••A, IA•A,CF
K,TF••A,T,.•A,CF
t<,CS••A,CS•A,CF

177737

RESIDE~T
~OOUL~ O~~ ••

RSX110 ••

K,Ef'••A,EF•A.CF

177750
177754
177 73?.
1777&&
17717P
177772
17777&

EXECUTIVE

SYMBOLIC

tt21
822

MACRO 00110

CEFINITIO~S

823
824

82S

))I
I

.......

Ue
827
U8

92q

830

000004'
000006

~00010

839
840
841
84i
8Ul

000012

i100011

00001 l
00~01"

000016
000020

000022
~0~022

000023
000024

852
853

IRQ •• IIC REQUEST QUEUE
TME "IRQ" IS A PRIORITY ORCERED DfQUE 0, 110 REQUEST NODES WTTM TTS
LISTMEAO IN T~E PUO E~TRY OF TME PMYSJCAL UNIT FpR W~l~M TME llD
REQUEST WAS QUEUED. EACM PMYSICAL UNJT MAS ITS CWN ?IC REQU~ST QUFUE.
l/C RlQUEST NODES ARE CREATED AND QUEUED PAJMARILV BY TM~ "QUEU! l/O•
DIRECTIVE. MCWEVER, TME EXEC ALSO CREATES l/C R~QU~ST~ roi
Ct> LOAD A TASK I~AGE, (2) RECORD A TASK IMAGE [CM!CKPOtNTt~GJ, AN~
(3) TO RUNOCW~ I/O CN A~ EXtT•EO TASK. !/C REQUEST NODES ARF- OF
f

~O.

..,0, U

00 CB HJ)

FOAWARO LtNIOG!

' ~o. 01 ce n> •• BACKWARD LINKAGE

837
fU8

8 ""
845
8'&b
847
648
849
850
851

PAGE

TME FOLLC~I~G FOR~AT,

830
831
83i
83l
834
83~

24•APR•T5 12156

"'01t'04~

R 1 T0••~1AW

( B 0'0 ••

~OD!

ACCOUNTtNG WORO (STD ENTRV AOR OF R~QU!StnR'

03 CB 06)
ATL NODE OF ~EQU,STCR ***
04 (8 tt) •• PR!OAUV cenn
(8 11) •• DPB SIZE (BVTE) ***
~5 CB lZ) •• LOGICAL UNIT NU~BER (8VTE)
ce 13) •• EVENT 'LAG NUM~fR CBVTE)
06 CB 14) •• I/O FU~CTION COD~
07 (B 16) •• VIRTUAL ADDRESS P' STATUS BLOCW
R,AE••20 ' ~D. 10 (8 20) •• VIRTUAL ADDRfSS OF AST SfAVtCE !NTAV
R,Uin22 ' WO, 11 CB 22) •• USER IDENTl,ICATtON CODE
R1 PC••22 J
(8 22)
PROGAA,..,..EA CODE
R.GC••23 I
CB Zl)
GROUP CODE
R,PB••24 ' wo. 12 ce 24) •• PARAMETER #t
1110. u (8 26) •• PARAMETER #Z
wo, u ce 11>
PARAMETER #l
wo. 15 (8 32) •• PARAM!TER #4
wo. 16 CB 34)
PARAM!TER #5
.,_D, 17 CB lft)
PARAMETER h
R.P0••40
~o. 20 ce 40> •• PUO POl~TER FOR TM!S REQUEST
R,AT••0b I WO,
R.PR••10 I WO,
R,OP••11 I
R,LU••12 ' WO,
R,FN••t3 '
R,FC••14 ' ~D.
R1 S8c•t6 J wO.

854

~~~042

85~

~~~~4ij

850

R,EL=•~2 '
k.~Aas44 '

857
858
859
8bVJ

0~e0su

Sb1

~0005b

8b~

~o.

~HhHZ01

8b7
8b8
8b9
87d

00~~02

•• ERROR LOG BUFFER

POI~TER/FLAG

•• FLAG BVTE FOR EXEC

•• WORK AREA FOR DEVICE HANDLERS
•• wORK AREA FOR DEVICE rANOLERS

•• wORK AREA FOR DEVICE HANDLERS

25 (8 52) •• wORK AREA FOR DEVICE HA.NnL!RS

021~0~1.i

AS fCLLC~S:

RF• )(RU0000P.2

I ( 0]
I ( 1)

RF. lRs&000004

I [2)

87Z
871
87't
875
87b

......
......

T~E LOw O?OfR THREE•BITS OF THE I/O FUNCTION COOf ARF us~o

RF. ITn0000M

871

878

ev THF SVSTF~

RESERVED FOR FUTURE USE
"EXPRESS REQUEST"
RESERVED FOR FUTURE USE

*** ~HE~EVER AN I/O REQUEST IS QU!~EO BV THE "QU!UE t/0" O!R~CT!VE, TH'

OPB SIZE ANO THE REQUESTOR'S ATL ~ODE ADDRESS AR~ REeORD,O I~ THF ~IC
REQUEST NOOE. WHENEVER AN I/O REQUEST IS QUEUfO AS A RESULT OF ~NOTHER
DIRECTIVE (VIZ., "REQUEST" CAUSING A TASK I~AG! TO BE LO~OFD}, TME p~B
SIZE ANO THE REQUESTOR'S ATL NODE ADDRESS ARE SET TO ZERO. TMUS, ~OTM
BOTH TME OPB SIZE ANO THE ATL NODE ADDRESS ARE ALSO "fXEC REQU~ST"
INDICATORS.

HSXttO •• RfSIOENT EXECUTIVE
~ACRO 00710
EXEC ~oo~~E O~E •• SY~BOLIC DEFINITIONS

Z4•APR•75 1Zl5b

PAGE

CKQ •• CLOCK QUEUE

87~

880

TME CLOCK QUEUE 15 A DEQUE CONSISTING OF ONE N~Of 'O~ !ACM OPERAIIO~
SCMECULED TC BE PER,ORMEO AT SOME FUTURE TjMf. A "SCMEOULE nELT~·
TI~E" I~ TME FIRST ~COE CIF ANV) 0' THE CLOCK QUEUE IS D!CREME~T'D
AT EACM CLOCK TICK U~TIL T~E NOOE "COMES DUE", AY WM!CM TI~! TME
INCICATEC OPERATION IS PfRFOR~EO. CLOCK QUEUE NCC!$ AR.E LtNKfO
IN TrE CROER IN WMICM TMEV WILL CO~E DUf, ANO TMf sc~EOULE C'LTA•TTMF
IN EACH NOOE (EXCEPT TME FIRST) IS RELATIVE TO TME SCMfOUL~ TIME
OF TrE PREVIOUS CLOCK QUEUE NODE. CLOCK QUEUE NCOES ARE 0' TME

881
88i
Hl

eeu

885
880

887
888

FOLLC~I~G

ee~

n0
nt

8ql

000UU

0000~b

eq~

Ce 42)
CB UU)
(8 45)
(8 4~)
CB 50)

R,IBs•54 ' ~o. 2b (B 54) -- INTER~EOIATE BUFFER ADtRESS
R.UB••5~ r wO. 27 CB 5~) •• USER BUFFER AODRESS(INTER~EO!AT~ TRANS,ER)
I

tibo

21
22
wD. 22
~o. 23
wo. 24

86}

8b'6
8bS

)I
I

~O.
~O.

000010

FOR~AT,

J WO, 00 •• FORWARD LINKAGE
' ~D, 01 •• BACKWARD LINKAGE
' ~O. 02 •• NOOE ACCOUNTt~G WORD CSTO ENTRY ADR OF REQU~STOR)

C,TD••~.AW

C,AT••0b ' WO, 0l •• ATL ~ODE ADDRESS OF REQUESTQR
C,S0••10. r WD, 04 •• SCMEDULE DELTA I~ TICKS (b4•8ITS)

890
n1
898
809

00~01"

000014t
000020

C,RT••14
I
C.F~••1b

901

00~022

C,,As•20
C,FNs:22

902

tiH11 0024

C • AE=•24

9NJ

903
904
905
900
907
908
909
910

911
91i

wD, 0~ •• (LOWER ORQER MALF OF SCMEDULE DEL!A)
wo. 06 •• REQUEST TYPE INDICATOR & UNUSED evTr
IND. e7 ••

000016

C.Riu1b

000022
000024i

C,R2••22

000026
000ei:JQI
00VIP 12

C,Aln24

C.R4••2b
c.uinl0

c.u .. u

[~T1

FLAG MAS~ f BIS SRC)

we. 10 •• [MT1 FLAGS WORD ADR (!JS OST ADR)
WO, 11 •• CMT1 !VENT FLAG ~UMBER
WO, 12 •• [MT1 VIRTUAL ADDRESS OF AST SERVICE ENTRY
U~USED

WORDS>

wo. 07 •• [TS] RESCMEDULE INTERVAL IN TICKS (64•8!TS)

i-io. u

[TS1 f LOW ORDER MALF 0, R!SCHEDULf J~YEBVA~)
WD. 11 •• [TS] STO ENTRY ADA OF R{QUESJtD T~SK.JR~ ~QR ',REOS;>
lliO, 12 •• [TS1 TPO ENTRY AOR,, OR !!RO. fU ,CR ..'.R!QfJ')
WO• l J •• (TS1 RU~ PRIORITY, OR Z~RO fR4 ·fOA '.R!OI')
wo. 1"
(TS1 Ult INDICATOR FOR ',REqS'
.

"40, 15 •• fTS1

TI IOENTtfICATION FOR •.REOS•
C2 U~USED WCPDS)

913

(MT) •• ~ARK TI~E NOOE ENTRIES
CTS] •• TASk SCMEOULING NOD£ ENTRIES

914
'H~

910
917
918
919
920
921
92;!

0001J00

REQUEST TYPE INDICATORS1

t
0 •• ~ARK TIME
TM.SL=•U00
tSUB CODE FCR AN INTERNAL TI~E SttCE
1 •• TASK SCHEDULING (SINGLE SHOT)
2 •• TASK SCHEDULING WITH PfRtoorc ~fSCMEDULtNG

923

924
~25

NOTE •• THE CLOCK QUEUE SCAN, RO~Tt~f IN "C•NCfl SCHEOV~fp ~EQU!STS"
ASSUMES TASK SCHEDULING IF NO~•ZERO REQUEST TYPE INDtCATOA.

RSX110 •• kESIOE~T EXECUTIVE
MACRO OP710
EXEC ~OOULE v~E -· sv~BOLIC OEFI~ITIO~S

ASQ ••

927
928
q2q
930

q11

t
1

Hi
q31

cn4

935

'Ho
q37

24•APR•75 12156

~0000&

cne

000010

939

000012

SYSTEM TRAP QUEUE

TME "ASQn IS A OEQUE CFIFO), WITM LISTMEAO IN ATL ENTRIES, CONSISTJ~G
CF C~E ~ODE FOR EACM AST (ASYNCHRONOUS SY~TEM TRAP' TO BE ~XPCUT~D FCR
TME TASK OEFI~ED BY TME STD ENTRY. ASQ NODES ARE 0, TM~ FnLLOW!NG
FOR~AT.

00 •• FORWARD LINKAGE
01 •• BACKWARD LINKAGE
02 •• ACCOUNTING WORO CSTO ENTRY ADDRESS OF CMAAGFD TASK)
03 •• AST TYPE & NU~BER OF PARAMETERS **
04 •• AST ENTRY POINT
05 •• AST PARAMETER 1
wO. 05 •• AST PARAMETER 2
we. 06 ·- AST PARAMETER 3
•••• ETC,

qui
CIUi

'iUl
1

qus

wO.
WO,
WD.
Y.TTs•06 ' WO.
Y,AE••10 ' ~O.
Y1 P1••12 r WO.

9U0

94'~

AY~C~RO~OUS

PAGE

** T~E AST TYPE & NUMBER OF PARAMETER DEFINITIONS ARE AS '~LLOWSt

);ii

94b

000 'H)~

Y,.~T==0+CU00•t>

t~AR~•TIME

947

946

000u01
H1002

YF.IC••l+CU00•t>
YF.FE•=2+C400•2>
YF.PR••3+C400•0>
YF.RE••4+C400•0>
YF.PC••7+cue0•3>

1110 COMPLETION fPARAMETER1,STATUS_!~Oek. ADDAESSl
1F.P. ~XCEPTIC~ tP~RAMETERS1 EXC~'TIDN COOP & AOnR~S~)
1POWER RECOVERY (NO PARAMETERS,
1RECEIVE QUEUElo (NO PARAMETERS)
tCOMMUNtCATtONS AST

.....

949
950
951
95i

~00003

000001.4
001407

(PARA~ETER1

EVE~T

F~AG

NUM~fR'

RSX1l0 •• RESIOE~T fX£CUTIVE
~ACRO D0110
EX£C ~ODULE -O~E •• SY~80LIC 0£FI~tTIO~S

24•APR·T~

9'54

9~5

t S~Q

954
9.57

'59
HI

T~£

fOllC~ING 10R~AT.

967
9U

:t-

....i
~

•• Sf~O/RECEIVE QU£U!

9b1
CJ&i

PAGf

THE "SRQ" IS A OEQUE (FifO), WIT~ tIST~EAD IN STD !~TRJfS,_CCNSISTt~G
ON-E ~COE FOR EAC1'4 8l0CI< 0, DAU "SENT" CYU •sn1J)• OA "Sf'ND ' REQU~ST·
DIRECTIVES) TO THE TASK OEFI~!O av THE STD fNTRY. RQS ~oo~s AR! 0,

9U
CUtS

t21~b

0'100041

n.SI••~.•w

0001lH
000010

o.TI••~.TI

-IO~hhH1

D.8S••11
0.01••12

1u0012

O.PR••10

RSX11D •• RESIOE~T EXECUTIVE
"ACRO 00718
EXEC ~OOuLE O~E •• SYM80lIC DEFINITIONS

J
f
f

wo. 10 ••
WO. 01 ••

FORWA~D lINkAGE
8ACK~AAD ll~kAG£

wo. 02 ce 04) •• S£NO£R IO tNAW)
' wa. 03 (8 16) •• Tl INDICATOR
r wo. 04 (B 11) •• PRIORITY Of SfNO
CB tt) •• IUfffR SlZ£ (WORDS>
' wo. es (8 12) •• f tAST ~o~o 0' ~•TA BLOCK

24•APR•75

121~6

PAGE

MCR •• ~c~ co~~•ND BU,FfR

970

911
Ul
97l

t THE ~CR COMMA~O BUFFER IS A •6 BYTE BUFF!A THAT ~OLDS TM~ DATA
' FOA A REQUESTED MCR FUNCTION.TH! !U,FEA rs S!T UP av THE MCA
t OISPATC~ FU~CTION A~O IS R!TUAN!D TO THf POOL RV THE 'G!T ~CR
t COMM•~D LINE
DtAECTIVEA,TER TH! IN,ORMATION HAS 8!!N PASSFD
t TO T~E MCR FU~CTION.THE BU,FERS A~£ LtNK!D TO THf MCR BUFFrR
t LIST BY THE ~CA DISPATCH ,UNCTtO~.

974

ens

977
978
09

980

981
~0000e
~00010

M.TN••~

98i
983
9U

0eiee 12

~.TI••10
~.BC••lZ

985

00~014

~.BF••14

t
t

'
t

WO.
WO.
WO.
WO.
WO.

I• •• FORWARD Ll~KAG!
11 •• 8AC~WARD LINKAGE
IZ •• ~ODE ACCOUNTING ~CAD
IJ •• SECOND HALF OF ~CR TAS~ NAM!
I~ •• Tl ADDRESS C' MCR 'UNCTION
we. 15 •• ~o. OF BYTES IN COM~ANC LINE
WO. lb •• START CF DATA AREA IN !UFF!A

APPENDIX B
GLOSSARY
ATL (Active Task List)

A priority-ordered list of Active
Tasks used to drive the system.
The ATL is a deque consisting
of
one node for each Active Task in
the system.

CLOCK QUEUE

The
Clock Queue
is
a
deque
consisting of one node for each
item to be done at some time in the
future, such as scheduling of Tasks
(Via the SCHEDULE and MARK TIME
Directives) , and rescheduling of
Tasks
(Clock
interrupt service
routine) .
The nodes are linked in
the order in which they come due.

COMMON BLOCK, INTERNAL

An area of contiguous memory within
a partition, available only to the
Task in the partition
during its
residency.

COMMON BLOCK, SYSTEM

An
area of
contiguous memory,
defined at System Generation time,
where data can be
stored
and
referenced by all Tasks. A SYSTEM
COMMON BLOCK is referenced by using
a COMMON name matching a SYSTEM
COMMON BLOCK ~ame and declaring
that COMMON as SYSTEM COMMON to the
Task Builder.

DEFAULT PRIORITY

A priority given to a Task during
Task Building or Task Installation
that is used when a priority is not
specified and the Task's execution
is requested or scheduled.

DE QUE

A double-ended queue consisting of
a
listhead
and
list elements
(nodes), circularly linked by both
forward
and
backward pointers.
Deques or linked lists are used to
store system information.

DEVICE HANDLER

A Task in the RSX-llD system which
drives or services an I/O device.
Handler tasks are activated using
the Queue I/O directive.

DIRECTIVE

See SYSTEM DIRECTIVE

DISK-RESIDENT TASK

A Task which normally resides on
the disk and is brought into a
memory partition to execute.

B-1

DPB (DIRECTIVE PARAMETER BLOCK)

A block of up to 12 {decimal)
contiguous
words
containing
information needed in processing a
System Directive.

EVENT FLAG

One of 64 bits associated with a
Task, which is set or cleared to
indicate
that
a
particular
Significant Event has occurred.

EXECUTIVE

The Executive coordinates all activities in the system including
Task scheduling, I/O supervision,
resource allocation, and interactive
operator communication.

I/O RUNDOWN

A process which delays the availability of a partition until all
transfers to and from that partition
have been stopped or have been allowed to complete. I/O RUNDOWN is
invoked when a Task is terminated
by the Executive or by the ABORT
MCR Function Task and has outstanding transfers pending to/from its
partition.

LISTHEAD

A 2-word memory block with forward
and backward pointers pointing to
the next and previous list node or
to itself if empty. The listhead
is a reference point in a circularlylinked list.

LINKED LIST

A deque consisting of nodes and
a list~ead used to store system
information. An
empty list consists of only a listhead.

LUN (LOGICAL UNIT NUMBER)

Logical Unit Numbers are used to
represent logical I/O device units
rather than physical units. Each
Logical Unit Number is represented
by an entry in the Logical Unit
Table.

LUT (LOGICAL UNIT TABLE)

A block of contiguous memory with a
1-word entry, or slot, for each
Logical Unit Number. When a LUN is
assigned to a physical device unit,
the corresponding LUT slot contains
the address of the appropriate
Physical Unit Directory node.

MCR (MONITOR CONSOLE ROUTINE)

The MCR allows the user to ccimmunica te on-line with the system
from the console Teletype. The MCR
consists of the Resident MCR Task,
whicn accepts user's commands, and
the MCR Functions, which actually
carry out the indicated requests.

B-2

MEMORY-RESIDENT TASK

A Task which has been fixed-in-memory
or which is assembled as part of the
Executive.

MONITOR CONSOLE

The control Teletype of the RSX-llD
system where MCR Function requests
may be issued by the operator.

NODES

The list elements of a deque.
All
nodes
(of dynamic lists) consist of
the listhead, followed by
data
(list elements) •

PARTITION

An area of contiguous memory within
which Tasks are executed; defined
at System Generation time.

PUD (PHYSICAL UNIT DIRECTORY)

A table constructed during System
Generation to describe the I/O
devices and units in the system.
When
a
logical I/O number is
assigned to a physical unit, the
device and unit are set in a LUT
entry corresponding to the LUN.

POOL (POOL OF EMPTY NODES)

Empty 17-word nodes for use in any
deque. The pool is generated by
System Generation from a core area
not specified for other use.

SIGNIFICANT EVENT

An
event which results in the
scanning of the active task list.
The following events are considered
significant events: 1) I/O queuing,
2) normal I/O request completion,
3) a task request, 4) a scheduled
RUN, SCHEDULE, or SYNC coming due,
5) a Mark Time expiration, 6) a task
resumption (Resume directive) , and
7) a task exit(Exit directive).

STD (SYSTEM TASK DIRECTORY)

A directory of all tasks installed
in the system.

SYSTEM GENERATION

The process through which the user
tailors the RSX-llD system to best
fit his requirements.

SYSTEM DIRECTIVES

Instructions to the
RSX-110
Executive
tn
perform
special
functions, such as I/O, etc.

TASK

A program written by the user or
supplied by Digital which is built
via the Task Builder, installed in
the system via the Monitor Console
Routine, and scheduled and. executed
on a priority basis.

TKB (TASK BUILDER)

The Task Builder program is used to
build Task files from relocatable
binary files.

B-3

APPENDIX C
QIOMAC.MAC

C-1

GIOMAC •

QTOSY~

MACRO OEFINITIO MAC~O 0071~

'
J

I
I

1
8
q

10
11
1'
tJ

14
15
1 fl\

17
18
10
2?.

25•MAA•75 l4t2l

PAGE

,TtTL£ QlOMAC • QIOSYM MACRO DEFINITION
ALTtRtO SUNDAY 24•NOV•74 13100
ALTERtD TUESOAY 28•Jl~·15 tJ1581I~
ALTERtO THU~SOAY 06•FE8•75 15150
•LTERlO MONO•Y 24•F£8•75 15140108 8¥ ED MARISON
AlTEREO TU£ 25•MAR•75 15131 EDIT • •S~t

***** ALWAYS UPDATE THE FOLLO~ING T~O lINES T-OGETMEM
,!DENT /03.,4/
.QI, vER•0l04

P.\ll0JPl4

THIS snfT~ARE IS FURNISHED TO PURCHAS£~ UNOtR l LICENSE FOR USE
ON A SINGLf. COMPUTER SYSTtM A~O CAN 8£ COPIED (WITH INClUSION
Of O£C1S COPYHIG~T NOTICE) ONLY FOR USE IN SUCH SYSTEM, EXCtPT
1 AS MAY OT~ERWlSf Bf PROVID£0 IN ~RITING SY Oft,

TMf lNFOqMATI-ON I~ THIS OOCUHlNT IS SUBJECT TO CHANuE WlT~OUT
NOTICt ANO SHOULO NOT 8t CONSTRUED AS l COMMITMtN1 oV DIGITAL

fQUJ~MENT

2'
23
24
25

OtC ASSUMtS NO ~ESPONSISILITV FOR THE USE OR HELIA81L1TY
OF ITS SOFTWAwE o~ tQOIPMENT WHICH IS NOT SUP~LIED liY OEC.

CORPO~AllON,

2~
()

21
2R

Jiii
3t

J ANO IOSd

MACRO TO DEFINE SllNOARO QUEUE. l/O OIRECTIVI:. FUNCTION' VALUES
~fTURN VALUfS,
TO INVOKt AT lSSEMdLY TIME (wlfH LOCAL
DtFINITlON) USf 1

J:'
Jd

a1nsvs

TO OijTAIN GLOBAL

JDEFINE SYMBOLS
DE~INJTJON

OF THESt SYMBOLS USEI

Jf\

QIOSVS OHSG

JR
JO
421
4t

4,
4J
44

45
4"
47
48

49
~p

bl
5,
bl
54
55
56

I
J

••

ISYMBOLS OEfJNEO GLOBALLY

THE MACRO CAN SE CALLED ONCt ONLY ANO THEN
REOtFlNES fTSELf AS NULL,

.MACRO
,IIF
.IF

QIOSVS SSSGBl,SSSMSG
ION,<SSSGBL>,<DEFSG>,
JON 1 <$SSMSG>,<DtFSS>

,GLOBL

QI,VER

SS~MAX•"

U'°'SG• t

,IFF
5SMSG•0
,t.NUC
,MCALL lOEkRI
JOEwRS

ISSGBL

.MCALL
OkfkRS
,IF
,MCALL
FILI OS

DMEwPS

SSSGRL

11/U ERROR CODES FAOM ~ANOLERS 1 fCP, fCS

JOIRECTIVt STATUS WOHO tARO~ CODES

OlF 1 <$S5MSG>,cOfflS>
FILIOi
S$SG8L
IOEFJNE

G~NfRAL

QI/O ~UNCTION coo~s

QIOMAC - UTOSYM

n~71A

25-MlA•75 1•123

.MCALL

SPCIOS

SPClOS

6'1'

,MACRO
.E.tl!OM
,tNOC
,f.NOM

SSSGBt.
GIOSY$
QIOSVS

62
63

0£FINITIO MACRO

58
61

(')

~•CRn

QIOSVI

PAGE

l•l

JDEVICE DEPENDENT I/O FUNCTION CODES
AHG 1 AHG1 1 1AG2

JRECLAIM MACRO STORAGE

QlOMAC • QIOSVM MACRO OEFINITlO MACRO 00710
65
66
67

68
69
70
71
1'2

2e•MAR•75 14123

,MACRO IOERRS SSSGBL
,MCALL ,JOER,,OEFINS
,IF
ION,<iSIGBL>,<OEFSG>
,.,G8L•l
.IFF
,,,GAL•0

75
76
71
78

.ENOC

,IIF

8P!
8~

SYSTE~

,lOER,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,
.IOER,
,IOER,
,IOER,

, I OE. R •

,lOER,
,lnEP,
,IOER,
.lOE.R,
.IOER,
,IOt.R,
.IOER,
,IOER,

84
85
86
87

88
89
9PI

.a:.

9!"

915

91
~A

9Q
10P

t 01
102

, I (')t:: R,

,IOER,
,IOER,
,IOER,
,IOER,
,Int::R,
.IOER,
,IOER,
.IOEi:;.
.IOER,

103

104
U5
106
107
10~

10~
11~

111

NOF,SSMSG,SSMSG•0

STANDARD coots, USED BY ALL FUNCTIONS

()

DEFINE TME ERROR CODES RETURNED BY DEVICE HANDLER ANO FlLE PRIMITIVES
IN THt FIRST WORD OF THE I/O STATUS BLOCK
TMESE CODES ARE ALSO RETURNED BY FILE CONTROL SERVICES CFCS) IN THE
BYTE F.ERR IN T~E FILE DESCRIPTOR BLOCK (FD~>
THE BYTE F,ERR+l IS 0 IF F,ERR CONTAINS A HANDLER OR FCP ERROR CODE,

PAGE

IE,BAo,-01,,cSAO PARAMETERS>
fUNCTION CODE>
If.ONR,•03,,<0EVICE NOT READY>
IE,VEM,•04,,<PAHITV EHROR ON DEVICE>
IE,ON~,-0~ 1 ,cHARO~AHE OPTION NOT PRtSENT>
IE.SPC,•06,,<lLLEGAL USER 8UffER>
tE,ONA,•07.,<DEVICE NOT ATTACHED>
IE,OAA,•08,,<0EVICE ALREADY ATTACHED>
If ,OUN,•09,,<0EVICE NOT ATTACHABLE>
IE,EOF,-10,,cENO OF FILE DETECTED>
IE,EOV,•11,,<fNO OF VOLUME OETECTtD>
lE,wLK,•12,,<wRITt ATTEMPTED TO LOCKED UNIT>
If,OA0,•13,,<0ATA OVERRUN>
IE,SRt,•14,,<SENO/RECEIVE FAILURE>
If,A80,•1~,,<REQUEST TEMMJNATEO>
IE.PRl,•16,,<PRJVILEGE VIOLATION>
IE,HSU,•t1,,<SHARA8LE RtSOUHCE IN USE>
It,OVR,•t~.,<lLLEGAL OVERLAY REQUEST>
IE,8VT,•19,,<00D 8VTE COUNT (OR VIRTUAL ADDRESS)>
IE,&LK,·2~ 1 ,<LOGICAL BLOCK NUMBER TOO LARGE>
IE,M00,•21,,<INVALIO UDC MOOULf M>
IE,CON,-22.,cuoc CONNECT ERROR>
IE,BBt 1 •56,,<8AD BLOCK ON OEVICt>
IE,STK,-sa.,cNOT ENOUGH STACK SPACE CFCS OR FCP)>
IE,FHE.,•59,,<FATAL HAROWAME EHROR ON DEVICE>
IE,EOT,•62,,<END OF TAPE DETECTED>
IE,OFL,·6~.,coEvICE OFF LINE>
IE,BCC,•66,,<dLOC~ CHECK OR CRC ERROR>
IE,IFc,-02.,clNVALI~

tit>
113

114
1 15

FILE

~RJMITIVE

CODES

116
111
1l 8
119

12"'
121

.IOER,
.IDER,
,IOERa
,!OER,

It,N00,•2J, 1 <CALLER 1 S NODES EX~AUSTtD>
IE,DFu,•24,,<0EVICE FULL>
IE,IFu,-20,,<INDEX FILE FvLL>
IE,NSF,-2b,,<NO sue~ FILE>

QIOMAt •

QJOSY~ ~ACRO

DEFINITIO MACRO D0110

25•MAR•75 14123
,IOER,
,IOER,
,IOER,
,InER,
,IOER,
,IOER,
,IOt:.R,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,
.IOER,
,lOER,
,IOER,

122
123

124
12,
12~

127
128

129
1 JP!

t 31
132
133

134
1J5
136

137
138
13<>

PAGE

2•1

IE,LCK,•21,,<LOCKED FROM WRITE ACCESS>
tE,HFU,•28,,<FtLE HEADER FULL>
IE,~AC,•29,,<ACCESSED FOR WRITE>
IE,CKS,•J~,,<FILE HEADER CHECKSUM FAILURE>
IE,~AT,•31,,<ATTRIBUTE CONTROL LIST FORMAT ERHOR>
IE,RER,•32,,<FILE PROCESSOR DEVICE READ ERROR>
IE,WER,•JJ,,<FILE PROCESSOR DEVICE WRITE ERROR>
IE,ALN,•34,,<fILE ALREADY ACCtSSEO ON LUN>
IE,SNC,•35,,<FILE IO, FILE NUMBER CHECK>
It,SQC,•36,,<FILE ID, SEQUENCE NUMBER CHECK>
IE,NLN,•37,,cNO FILE ACCESSED ON LUN>
IE,CL0,•38,,<FILE WAS NOT PROPERLY CLOSED>
tE,OUP,•57,,ct:.NTE~ • OUPLICATt:. ENTRY lN DIRECTORY>
IE,bVR,•63 1 ,<SAO VERSION NUMBER>
IE,BH0,•64,,<~AO FILE HEAOEH>
IE,EXP,•15,,<FILE EXPIRATION DATE NUT RtACHED>
IE,BTF,•76,,<~AO TAPE FORMAT>

140

14 t
14?
143
144

t45

146
(')

147

1 ~u~

149
1 5'11

151
15?.
15J
154

15!;
156
157

l5R
1~9

16QI

FILt:.

CONT~OL

,IOER,
,IOE:.R,
,IOER,
,lOER,
1 IOER 1
,IOt:.R,
,IOER,

,IOER,
1 lOER,
,IOER,
,lOE.R,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,
,IOER,

161

.Ioe.~.

162

,IOER,

163
1b4

,IOt:.R,

16~

166
167

16A
16Q
17~

171

173

174
175

SEHVIC~S

CODt:.S

IE,NBF,•39,,<0PE.N • NO BUFFER SPACE AVAILABLE FOR FILE>
JE,RBG,•4~,,<IL~EGAL RECORD SlZt>
IE,NBK,•41,,<fILE EXCEEDS SPACE ALLUCATEO, NO BLOCKS>
IE,ILL,•42,,<ILLEGAL OP~RATlON ON FILE DESCRIPTOR BLOCK>
ll:.,BT~,•43 1 ,<BAD RECORD TYPE>
.
lf:.,WAC,•44,,cILLEGAL wECOHO ACCESS ~ITS St:.T>
IE,HAT,•4o,,cILLEGAL RECORD ATTRI~UTES bITS StT>
IE,RCN,•4o,,cILLEGAL RECORD NUMBER • TOO LAHGE>
lE,M~K,•41,,<MULTIPLE BLOCK Rt:.AO/wRITI:. • NOT IMPLEMtNTED YET>
IE,2DV,•4b,,<RENAME • 2 DIFFERENT DEVICES>
IE,fEX,•49,,cRENAME • NEW FlLt:. NAME ALRtADV IN USt:.>
lE,BOH,•50,,<8AO DI~ECTORY FILE>
lf,RNM,·•51,,<CAN'T HENAME 01.D FILt:. SYSTl:.M>
It.~OI,•52 1 ,<BAO DIRECTORY SYNTAX>
IE~FOP,•5J,,<FILE ALREADY OPEN>
It:.,BNM,•54 1 ,<SAD FILE NAME:.>
IE,BOV,•5o,,cBAO OEVltE NAME>
IE.,NFI,-60,,cfILE ro ·~AS NOT SPECIFIED>
IE.,ISQ,•61 1 ,clLLEGAL SEQUENTIAL OPERATION>
JE,NNC,•77,,<NOT ANSI IOI FORMAT SYTE COUNT>

NETWOkK ACP CODf:.S
,IOER,
,lOt::R,
,IOER,
,lOER,
,lOE.R,
,IOER,
,IOER,
,IOER,
,IOER,

IE,AST,•67,,<NO AST SPECIFIED IN CONNECT>
sue~ NOOE>
IE,NFw,•69,,<PATH LOST TO PARTNER> 1+~01 THIS CODI:. MUST Bt:. ODD
IE,BLB,•7~,,cbAD LOGICAL BUfFtR> 1+~01
IE,TMM,•11,,<TOO MANY OUTSTANDING MESSAGES>
IE,NOR,•72,,<NO DYNAMIC SPACE AVAILAB~E>
IE,CNR,•73 1 ,<CONNECTION RtJECTEO>
It,TM0,•74,,<TIMEOUT ON REQUEST>
lE,NNL,•78 1 ,cNOT A NETWORK LUN> 1+0~1

If ,NNN,•68,,<NO

1 7 fi
177
178

SUCCESSFUL

~ETURN

CODES•••

QlO~AC

• QIOSYM MACRO DfFl~ITJO MatNO

0871~

25•M4R•75 14123

PAG£

2•2

179
ta~

tel

0-EF INS

182

DE.FINS

183

rs.suc,.01.

Off'INS

tS.tlV,•05,

184

I s • PNU' • ee •

185
186
187

JOPERATION PENOlNG
'OPERATION COMPL~TE, SUCCfS8
JON A/O AEAO, AT LfAST O~E tiAO VALUt
l•AS AfAD CREMAlNO£R MO BE .GOOO>e
18AD CHANN£L IS INDICATED 8Y A
JN£GAflV£ VAlU£ IN TWt S1JffEA.

188

lH
19!'1

TTY SVCCfSS COOESI

191

192
t93
19•

DEFl~S

nEFINI

IS.CR,<15•401•1> JCAAHJAGE RETURN WAS Tt.A-MINATOH
J£SCAPE (lLlMOOtl WAS TfAMINATON

rs.t.sC.<33•480•1~

195
196
1~7

•
en

196
199
20cii
201
2it'?
2~J

2"'
2~5

'"&
2~?

••••••
THE ~tXT AVllLA8LE tR~O~ NUMB~A ISi •79,
ALL lO~ER NUMBERS ARE IN USEJ&

•••••

.lF

EQ,SSMSG

.MACRO
.t:.NOM

IOEWAS

IOENRS

.£NOC

.t.NDM

lOE~AS

QlOMAt • QtOSYM ~ACRO OEFINITIO MACRO 00710
t>09
2UI

211
212

'13
214
21~
21~

DEFINE THE DIRECTIVE ERROR CODES RETURNED IN THE OlHECTIVE STATUS WORD
FILE CONTROL SERVICES CFCS) RETURNS THESE CODES IN THE SYTE F.ERA
OF TME FILE DESCRIPTOR SLOCK (FOB), TO DISTINGUISH TMEM fAOM THE
OVERLAPPING CODES FROM ~ANOLER ANO FILE PRIMITIVES, THE BYTE
F,EHA•t I~ TME FOB WILL 8£ NEGATIVE FOR A DlRlCTIV£ ERROR CODE.

'19

,IF
ION,~SSSGHL>,cOEF$G>
.,,GftL•1

223
224
22!'i

22-6
227

nf'
22Q

2J0
2J,
I

.~ACRO

'2~

()

PAGE

21'
21A
220!
221

-.)

25•MAR•75 1•123

2J'
'3J

23.t

.~CALL

DR£RRS SSSGBL
,QtOf,,OEFINS

.IFf

,,,G9L•0
,tNOC
,IJF

NOF,SSMSG,SSMSG•I

STjNOARO ERHON CODES HETURNED 9Y OlRECTIVES IN THt OlWECTIVt STATUS
,<HClf,

, QT OE•
, tH OE,
,QJOE,
,QTOE.
, \ii TOE,

,QJOE,

23~
23~

It.uPN,-01.,clNSUfFitIENT OYNAMlC SlOJU,E>
lE.lNS,-02,,csPECIFlEU TASK NUT lNSTA~L~O>
It,ULN,·0~ 1 ,c~N·ASSlGNED LUN>
It.H•k,•06, 1 <HANOLER TAS• ~OT R~SIO~NT>
IE.ACT,•01.,cTASK NOT AClIVt>
JE,JTS,•08,,cotRfCTlVE INCO~SISTENT WIT~ TASK STATE>
IE,CKP,·t~,,cISSUING TASK NOT CHECK~Ol~TA~LE>

237

2JQ
24111

.QYOE.

,QJOE,
I

GI I OE.

241
24i?

• <.l I OE•

243

,<.IIOf,

244

,QIOE,
.~lOE.

24~

,1.IJOE,

246

.QTOE,

~47

:>4R

249

tE,AST,·8~,,<0IMECTIVt ISSUtO/NOT
It.LNl,·9~,,<LUN LOCKtO IN USE>

IE,1ou,-q~.,c1Nv•LIO DEVICE OR UNlT>
IE,lTl,•9J,,cINVALIO TIME PARAMtTtRS>
If,IP~,-95.,cINVALJO PRIORITY C ,GT. 25~.)>
It.lLU,•96.,<INVALIO LUN>
lE,IEf,•91,,<INVALIO tVENT ( ,GT, 64,)>
IE.,AD~,-98,,<PART OF DPb OUT OF USE~IS SPACE>
IE,SD~,-99,,<DIC OR DPB SIZt INVALI~>

SUCCESS CODES F"OM UIRECTIVES - PLACED IN THE OIRtCTIVE STATUS

251'l!
251

OE FINS

IS,CLR,0

~52

DE Fl Ni

IS,SET,2

:?53
254

DE.FI Ni

IS,SPL),2

• IF
.MACRO
,ENOM

fQ, UMSG

JEVENT ~LAG wAS CLEAR
JFROM CLEAR EVENT FLAG DIRECTlVt
JEVENT ~LAG WAS SET
JFROM SET EVENT FLAG DIRECTIVE
JTASK wAS SUSPENDED

255
2!>6

:n>,

25A
25Q

ISSUED fROM AST>

260

.~NOC

2b\

,E.NOM

O~ERFU
O~EIH~S

DRERRfl

~a~o

~ORO

QIOMAC • QJOSYM MACRO DEFINITIO MACRO 00710
263
264
265
266
267
26A
269
27A

PAGE

THE GENERAL QI/O FUNCTION CODES • OEVICE lNDEPENO!NT

DE~INt

,MACRO FILIOS SllGBL
,MCALL ,wORO,,OEFINS
,IF
ION,<SSSG8L>,<DEFIG>
,,,GBL•l
, I-FF
,,,G8L•0
,t:NOC

271
2n
273
274

GENERAL QI/O QUALIFIER BYTE D~FINITIONS

27~
27~

, i'IORD 1

IQ,x,0211 ,eee

277

WORD,

IQ 1 Q,1002,ro00

278
27Q
281A

"'
'

281

,wORO,

E~PRESS

IQ,,0!04,000

,WORD,

IO,KIL,0121000

• 1110~0'

28~

,wORD,

IO,HOlll,02210HI
tO,UN\..10421000

wOHO 1
, wORO,

IO,LTK,05'°1000
IO,•H",0601000

n
()0

290!

291
2~n

JNO EHROR RlCOVERY
~EQUfST IN EXPRESS QUEUE

JQUEUE

IRESEHVEO

DUEUE COMMANDS

282
2H3
284
286
287
268
289

2S•MAR•75 lA123

IKILL CURRENT RlQUEST
'l/O RUNDOWN
IUNLOAO I/O HANOLtR TASK
JLOAO A TASK IMAGE ~ILE
IRECOHO A TASK IMAGE FILE

GENERAL OtVICE HANDLE~ CODES
, ._,OHO,
, wOHO,

to.wLB,"Qlfd,001
tO.RLB,000,002
!O,LOV,0tri>,002

2Ul

, ii.OMO 1

294
29!5

, lllOHO,

IO,ATT,0001003

,wORO,

IO,DET,000,004

JwRITE LOGICAL 8LOCK
JHEAO LOGICAL BLOCK
ILOAO OVERLAY COISK DHIVER)
IATTACH A O~VICE TO A TASK
IOETACH A DEVlCt FROM A TASK

29~

297
29A
290

30QI
3k!t
l0:>
31i:'J

DIRECTORY PHIMITtVE CODES
.w~HcD.
,wt'H~O,

,wo;rn,

IO,FNA,CiHlld,011
IO,RNA,0001013
IO,E.NA,~H'l01014

Jli/l!li

31~

3P
314
31~

, WOHO,
, WORD,

,wOHD,
, l'llOHO,
, WORD,

, lllORD 1
, "''ORD,

,WOHO,
,wORO,

IO,CRE,~00,024

IO,OEL10001E25
IO,RAT,00"'1026
IO,..,AT,0001027

, WORI),

,wOHO,

317

319

IO,CLN,001t11007
ICJ,ACR,0001015
IO,ACW,00"',016
tO,ACE,000,017
to, DAC, 1iH''"' ia20
IO,Rva,0ei0,021
tG,.-.vs,'°0ia,022
IO.EXT,0Ql0,02J

,WORD,

31~

31R

JREMOVE FILE NAME FkOM DIRECTORY
IENTER FILE NA~E IN DlRECTOHY

FILt PRIMlTIVt CODES

304
306
307
J0A
309
JUI
311

JFIND FILE NAME IN OIHECTORY

1110RO 1
, l'IOfo/D,

T0 1 APVd'll~1030

ro,APC,000,ld30

ICLOSE OUT LUN
JACCESS FOR RE.AD
JACCESS FOR WRITE
JACCESS FOR EXTEND
JDE•ACCESS FILE
JREAO VIRITUAL BLOCK
JwRlTE VIRITUAL B~OCK
IEXTEND FILE
ICRUTE FILE
10ELETE FILE:.
JREAO FILE ATTRIBUTES
l~RlTE

FI~E

JPRlVlLEG~D

JACP

CO~T~OI.

ATT~IBuTE~

ACP

CO~T~~L

QlOMAC • QJOSYM MACRO DEFINITIO MACRO 00710

2~•MAR•75

14123

PAGE

320

(')

I
\0

321

,MACRO

FILI OS

322
323

,ENOM
,ENOM

FILI OS

••1

QlOMAC • QIOSYM MACRO 0£FINIT10 MACRO oe11e

25·MAA•75 1•123

PAGE

32!15

326
327
328

32C)
3J9
331
332
333
334

335
338

337
3J8

33q
340
341

342
343
344

345
346
347
348
349
35'11
()

I
I-'
0

351
352
353
35.t

355
3b,.

357
3!>8

359
36A
3bt

362
363
364
365
366
367
368

369
370
371
372

373
374
37~

376
317

378
379
38Pl
381

DEFINE THE QI/0 FUNCTION CODES TMAT ARE SPECIFIC TO INDIVIDUAL OEVlCES
.MACRO SPCIOI SISGBL
.MCALL 1 wOR0 1 ,0EfINS
.IF
ION,cSISG8L>,cOEFSG>
11 ,GBL•l
1If'F
,.,GBL•0
,ENOC
0110 FUNCTION CODES FOA SPECIFIC DEVICE DEPENDENT FUNCTIONS

.woRo.
• lliORO.
.wORO.
.1110"0.
.~ORD.

.1110RO I
1 wORD 1
.wOHO.
1 WOR0 1

.wOMO.
.WC'RD.

• \lllORO,
•"'ORD•
• wOkO,
,WORD.

wOHD.
.wOHD.
1 WORO.
• wORD 1
1

.worto.

, 1110RO,
,wORO,
.wOHD 1

.woRo.

,wORO,
, l!IORO,
.1110F~D I

,WORD,
.~ORD,

rn.wLv, 110,001
IO.wLs,010,001
IO.wNS,0201001
I 0, RLV, 11110 dJ02
IO,RNC,04",002
IO,RAL,ld10i002
IO,RNt,0201002
ro.ADa.2rae,0e2
IO,RH0,0101002

IO,RNS,020,002
IO.CRC,040,002
IO,RlC,111001005
IO,INL,000100~

IO, TRt4,010,00b

I0 1 t(8C,000,006
IO.MOD,1400,01116
IO,HO>C,~10,006

IO.Fox,020,006
ro.SVN,0416,006

IO,RTC,000,007
10,wwo1000,005
IO,SPB,0201005
IO,SPf ,11J401005
IO.EClF,0001006
IO,STC., 1001005
10.sEc,12fd,00f>
to.Rwu,1•0,005
IO.SMQ, 1601005
IO,SAO,IOH,010
ro,sso,000,011
IO,MS0,000,012
IO,SL0,0001013
IO,ML0,000,014
IO,LED,000102•

, ... OHO,
, wORD,
,WORD,
,WORD,
,WORD,
,WORD,
,WORD,
.WORD,
,WORD,
,WORD,
, w·oRD,
.wORO.

10.scs,eru,026
IO,REL,000,021
IO.MCS,000,021
I0 1 AOS10001030
to,cc1,110,ral0

,WORD,
,WORD,

10,oc1,000,el1
IO,XMT,(r>101031

• '-!ORD,

10,soo,000,025
IO.so1,000,026

tO,MDl,H0,li!l31

J~RITE LOGICAL REVERSE (DECTAPE)
J(COMMUNICATIONS) wRlTE PRECEOED SY SYNC TRAIN
J(COMMUNICATIONS) WRITE, NO SYNC TRAIN
JREAD REVERSE COECTAPE)
JREAD • NO LOwEH CASE CONVERT (TTY)
JREAO PASSING ALL C"ARACTtRS CTTY)
JREAD WITHOUT ECHO (TTY)
JREAO BINARY HOOE CCARO RlADEW)
JCCOMMUNICATIONS) RtAO, STRIP SYNC
J(COHMUNICATIONS) READ, DONIT STRIP SYNC
J(COMMUNICATIONS) RtAO, OONIT CLEAR CMC
JREAO SIN~Lt CHANNEL (AFC, &001 1 UOC)
JCCOMHUNICATIONS) INITIALIZATION ~UNCTION
J(COMMUNlCATIONS) TERMINATION FUNCTION
JREAD MULTICHANNELS C~UFFER DEFINES CHANNELS)
J(CUMMUNICATIONS) StTMOOE FUNCTION fAHILY
J(COMMUNICATIONS) StT UNIT HALF DUPLEX
JCCOMMUNICATIONS) SET UNIT FULL DUPLEX
JCCOMHUNICATIONS> SPECIFY SYNC CHARACTER
JREAO CHANNEL • TIME BASED
1REWIND CMAGTAPE, DtCTAPE)
JMAGTAPE, SPACE "N" BLOCKS
JMAGTAPE 1 SPACE "N" EOF MARKS
JMA~TAPE 1 WRITE EOF
JMAGTAPE 1 SET CHARACTERISTIC
JMA,TAPE, SENSE CHARACTERISTIC
JREWIND AND UNLOAD (MAGTAPE, OECTAPt)
JMAGTAPE, MOU~T & S~T CHARACTERISTICS
IUDC SINGLE CHANNEL ANALOG OUTPUT
IUDC SI~GLE SHOT, SINGLE POINT
JUDC SINGLE SHOT, MULTI•POINT
IUDC LATCHING, SINGLE POINT
IUDC LATCHING, MULTI•POlNT
1LPS11 WRITE LED DISPLAY LIG~TS
JLPSll WRITt DIGITAL OUTPUT REGISTER
ILPStl READ DIGITAL INPUT REGISTER
JUDC CONTACT SENSE, SINGLE POINT
JLPS11 WRITE RELAY
IUDC CONTACT SENSt, MULTI•POINT
JLP511 SYNCHRONOUS AIU SAMPLING
JUDC CONTACT INT • CONNECT
JLPSll SYNCHRONOUS DIGITAL INPUT
1UDC CONTACT INT • DISCONNECT
J(COMMUNICATIONS) TRANSMIT SPECIFIED 8LOCK ~ITH ACK

QlOMAC • QIOSYM MACRO DE,INITIO MACAO D87ll
382

383
38'
385
386

387
388
389

.......

.woRo.
.wOROe
.wORD,
.wORO,
1 WORDe
.woAD.
,WORD.
.WORD,

39f!I
391
392
393

.woRo.

39•
395
396
397
398
399
•0ei

,WOAD.
.woRo.
.WORD.
,WORD,
.WOHO,
,WOAD,
• WORD•
,wOffD,
, \liOAO,

•0t
0
I
.......

25•MAA•75 14123

•02

•0:.
•04
•05
•06
•1111
•011

.WORD,

.woRD.

.wnRo.

.woAo.

,WORD,
,wOkO,
.wOAO,
.woAn.
.woND,

•M9

,wOMO.

•1~

.wORD.

•11

•"'ORO.

•12

1 1-0RD.

•13

.WOHO.
.wOHO,
.woRo.
.woRo.

•1•
•15

416
•11
118

•19

.tiiiORD.

.llllORO,
,lifOROe

PAGE

IO.XNA,011,031
to.Hts1IH1u2
10.RCI1H01032
to,Rcv1ae.,1032
IO.MD0 11H01033
IO,CTI1000103J
IO.CON,f1Hll010J3
IO.CPR,0101033
IO.CAS11U010Jl
IO,CRJ10•0,033
10.ceo, 11010Jl
IO.CTA,210,033
IO,GNl,010,035
IO.GLI,02111,035
tO.GLC,0J0,0J~

IO,GRI,11"01035
IO,GAC.0501035
IO.GAN,0601035
IO.CSM,070,0J5
I0 1 CIN11001035
IO.CBN, 1101035
10.ceo, 120.035
I 0, OTI 1001111 03•
10,01s1000,0J•
IO,MOA 1000103•
YO.RTI,0HJ1035
I0 1 CTL,11JHJ10J5
IO.STP.08'111035
rn.n110H10J6
10.wPe,0•0,001
IO.RP8104I01002
IO.SHT,lllll01005
IO,SST,11130,005
IO.SEM,0•01005
tO.SNM 1050,005
10,CCT ,060,fH5
10,0CT ,87'1 IH5
I0 1 ESA1lH1011Jb

•2A

•21
•22
•23

•2•

.MACAO

,ENOM
,ENDM

5•1

SPCIO-S
SPCIOI
SPCIOI

JCCOMMUNICATIONS) TRANSMIT WITHOUT ACK
JLPSll SYNCHRONOUS HISTOGRAM SAMPLING
JUDC CONTACT INT • AfAO
J(COMMUNICATIONS) RECfIVE DATA IN BUFFER SPECIFIED
JLPStl SYNCHRONOUS DIGITAL OUTPUT
IUDC TIMER • CONNECT
JCCOMMUNICATIONS) COMMUNlCATIONS CONNECT FUNCTION
JCCOMMUNICATIONS) COMMUNICATIONS CONNECT NO TIMEOUTS
JCCOMMUNICATIONS) COMMUNICATIONS CONNECT WITH AST
J(COMMUNICAT!ONS) COMMUNICATIONS CONNECT REJECT
J•001 (COMMUNICATIONS) COMMUNICATIONS BOOT CONNECT
J•00l <COMMUNICATIONS) COMMUNICATIONS TRANSPA~ENT CONNECT
J(COMMUNICATIONS) COMMUNICATION~ GET NODE INFO
JCCOMMUNICATIONS) COMMUNICATIONS GET LINK INFO
JCCOMHUNICATIONS) GET LINK INFO CLEAR COUNTlAS
JCCOMMUNICATIONS) G~T REMOTE NODE INFO
J•0~1 (COMMUNICATIONS) GET REMOTE NOD~ ERMOM COUNTS
J•llJ01 CCOMMuN.) GET REMOTE NODE NAMl
J•l~l CCOMMUNICATIONS) CHANGE SOLO MOOE
1•0~1 (COMMUN.) CHANGt CONNECTION IN~lBIT
J•001 (COMMUNICATIONS) CIRCULAR BUFFER NCS
1•01111 (COMMUNICATIONS) CIRCULAR BUFFER DDCMP
JUDC TIMER • DISCONNECT
J(COMMUNICATIONS) COMMUNICATIONS DISCONNECT FUNCTION
JLPS11 SYNCHRONOUS O/A OUTPUT
JUOC TIMER • READ
JCCOMMUNICATIONS) NETwORK CONTROL FUNCTION
JLPStt STOP IN PAOG~ESS FUNCTION
JUDC TIMER • INITIALIZE
1 AX01 • FLOPPY OISK WRITE PHYSICAL BLOCK
I AX0l • FLOPPY DISK ffEAD PHYSICAL SLOCK
JSET "OAIZONTAL TAB POSITIONS
JSfT SPECIAL TERMINATOR CHARACTtRS
JSET TERMINAL MOOE (CHARACTERISTICS)
JSENSE TERMINAL MOOt
JCONNECT TO REMOTE TERMINAL (AUTO OlALOUT)
JDISCONNECT FROM REMOTE TERMINAL (HANGUP)
JtNABLE STATUS AST

QIOMlC • QIOSYM MACRO ~EFINITIO MACRO 00711
•26
•27
08
•29
430
01
•32
•33
•JS

eIOMG 1

,IOER, SVM,LO,MSG
SYM,LO
GT,SSMSG
.IOMG,
SYflll1LO,cHSG>

,ENOC
.ENOM

.IOt.A,

~110 EAAOR CODES ARE DEFlNEO THOUGH THIS MACRO WHICH THEN INVOKES
E~ROR MESSAGE GENERATING MACRO, ERROR CODES •129 THROUGH •256

.~ACRO

,QtOE,

Off INS

A46

.IF
,MCAL-1..

SYM,LO
GT.SSMSG

U1
448
4140

el0f1G.
_.fNOC
.ENOM

SYM,<LO•t~8 1 >,cMSG•

•••
445
•5~

•51
452
453

•5•
455

THE

AR£ USED IN THE QIOSYM.MSG FILE

441

442
Ul

eMACAO
DEF INS
.IF
a MCALL

•37
4138
09
00

.....I

PAGE

HANDLER ERROR CODES AETUAN£D lN 1/0 STATUS BLOCK ARE DEFINED THMOUGH THIS
MACAO WHttH THEN CONDITIONALLY INVOKES THE MESSAGE GENERATING MACRO
¥0A T~E QIOSYM.MSG FILE

•3•

25•MAA•75 1~12J

SYM,LO,~SG

al0MG 1

,QIO£,

,' CONDITIONALLY GENERATE uATALO,MSG

FO~ WHITI~G

a MACRO

,WORD

.uc !Z

4f)6

.EVt::H

457
•58
4159
•60
46t
462
463
46•

, IIF
aENDM

A MESSAGE FILE FOR MO

,IOMG, 8YM 1
•AO<LO>
AMSGA

LT 1 AOcSSSMAX•<LU>>,SISMAX••A0CL0>
1

l0Mti,

DEFINE THE SYMBOL SYM WHERE LO IS IS THE LOW ORDER 8VTE 1 HI IS THE HIGH BYTE
WORO,

SYM,LO,HI

.MAC~O

OE FINI

9YM,cAOcH1•410•L0>~

.ENOM

,WOH0 1

....

...

..., .
..-.. ..."
.
'5

lal

IO
....
I

ac
c
z:

.,,
I

>
oz
a

-"".
lf)O

•
•

....
0

u
c
z:

.......
0

....

•
••a

D
CIC

u
c
z:
z:

.,.,
>

...
0

•

ISi

m
IS)
s
15

-a.

C-13

QIOMAC • QIOSYM MACAO OEFINITIO MACAO 01711
SYMBOL TABLE
IE,ABO•
IE.ACT•
If,ADP•
JE,ALN•
JE,AST•
If,8AD•
JE,88E•
IE,8CC•
IE,801•
IE,8DR•

()

I
.....,
~

t77781 G
177771 G
177636 G
177736 G
177660 G
111111 G
177710 G
117676 G
t777t• G
177716 G
I~.BDV• 177711 G
tf,8MO• t77700 G
IE,BLB• 177672 G
It,BLK• t77754 G
IE.BNM• t777t2 b
tE.BTf • t77664 G
IE.8TP• t77725 '
tf.BVR• 1777~1 G
lf.SVT• t711~~ G
Jt.CKP• t77766 G
It,CKS• t17742 G
JE,CLO• 177732 G
JE,CNw• 177667 G
IE,CO~• 1777~2 G
tf,DAA• 17777~ G
IE,OAO• 177763 G
JE,OFU• 17775~ G
JE,UNA• !77771 G
Il,ONR• !77175 G
IE,OU~• 177767 G
IE,OUP• t711~7 G
IE,E~F• 1777~6 G
IE,fOT• 1777~2 G
IE,EOV• 17776~ G
tt,EXP• ,11665 G
IE,FE~• t77717 G
IE,FHE• f 777~5 G
IE.FOP• 117713 G
IE,HFU• 177144 G
IE.HWN• 177172 G
IE,lDU• 177644 G
IE.lEF• 177637 G
IE,lFC• 111116 G

• ASS,

IE.IFU•
IE.ILL•
1£,ILU•
IE.INS•
IE.IPA•
IE.ISQ•
IE.IT!•
IE, ITS•
IE.LCK•
IE,LNL•
fl.MAK•
IE.MOO•
IE.NBF•

1111•1 G
177126 G
177641 G
177776 G
177641 G
1777~3 G
t7764l G
177770 G
177745 G
177646 G
177721 G
177753 &
177731 G
It.NB~• 177727 G
YE.NOR• 177670 G
IE,NFI• 177704 G
tE,NFW• 177673 G
TE.NLN• 177733 G
Il.NNC• 177o6J G
JE.NNL• 177662 G
It.NNN• 171b74 &
tE,NOO• 177751 G
IE.NSF• 177746 b
IE.OFL• 111b11 G
JE.ONP• 177773 G
IE,OVR• 177756 G
IE,PRl• 177760 G
JE,HAC• 177724 G
IE.RAT• 117723 G
tE,AffG• 177730 G
!E.,RCN• 117722 G
JE,RER• 177740 G
tE,RNM• 177715 G
IE,~SU• 177757 G
JE,SOP• 177635 G
IE.SNC• 17773~ G
IE,SPC• 177772 G
JE,SOC• 177734 G
If.SAE• 177762 G
IE.STk• 177796 G
IE,TMM• 177671 G
YE, TMO• 117666 G
JE,ULN• 177173 G

QhH!000

fH0

CIJ0fl0H

ERRORS 0£lfCTEOI

FREE CC'IRf I

wo~os

5b69,

,~P1•lt56,1J3J0IOMAC,Tt1

2'5•MAA•7'; 14 I 23
IE.UPN•
IE.V£R•
IE,WAC•
lE,wAT•
IE.WEA•

PA&E

111117 G
l1777• G
t7774l G
177741 G
177737 G
IE.WL~• 177764 G
IE,2DV• 177720 G
IO,ACE• 00740~ G
IO,ACA• 006410 G
IO,ACW• 007000 G
IO.ADS• 014000 G
IO.APC• 014010 G
IO.APV• 014010 G
IO.ATT• aet•ero G
IO,CAS• 015•20 G
IO,CBD• 016520 G
10,CBN• 01651~ G
10,CBO• 015~10 G
IO.CCI• 014000 '
tO,CCT• 00246~ G
IO.CIN• 016500 G
IO,CLN• 003400 G
IO.CON• 015400 ~
IO.CPR• 015410 G
10.c~c· 0010•i0 G
IO,CAE• 012000 '
IO,CRJ• 015440 G
IO.CSM• 016470 G
IO,CTI• 015400 G
IO,CTl• 016410 G
10,CTR• 015610 G
10,0AC• 01000~ G
IO.OCI• 014400 G
tO,OCT• 10247~ G
10,0EL•. 012400 G
IO.DET• 002000 G
IO,ots• 116100 G
IO,OTl• 816001 G
JO.ENA• 186188 G
IO.EOF• ee3ee0 G
IO.ESA• 012510 G
IO.EXT• 111408 G
IO,FOX• 083120 G

7•1
10.FNA• 114•11 G
IO,GLC• 116431 G
IO,GLI• 11642~ G
10,GNI• 116411 G
10,GRC• 116•50 G
10,GAI• 1164•0 G
IO.GAN• 116460 G
IO,HOX• 00301'0 G

IO.HIS• 015000 G
IO,INL• 002411 G
ro.ITI• 011010 G
IO.KIL• 011112 G
IO.LED• 012HI G
10,LOV• 01151010 G
IO.L. TK• 001050 G
IO.MCS• 013400 G
IO,MDA• 0U50H 11
IO,MDl• 114410 G
IO,MOO• 015400 G
IO I MLO• 006000 G
IO,MOO• 003018 G
10,MSO• 005000 G
IO.RAL.• 00t0U G
10,RAT• 013000 G
10,HBC• 003H0 G
10,HCl• 11500~ ~
IO,RCV• 01501~ G
IO,RD~• 001210 G
IO,RO~• 001~22 G
10,REL• 013411 G
IO,~MO• 101010 G
10.RLd• 001000 G
tO,RLV• 011Ul0 c,
10,HNA• 00540~ G
IO,MNC• 001040 G
I~ 1 RNE• 101020 G
IO.RNS• 011020 G
IO,HP8• 0110•0 G
10,HTC• 003409 G
10,HTI• 116400 G
10,RTK• 111860 G
IO,RV8• 111411 G
10,AWD• 112410 G

IO,AWU• 1125•0 G
10,RtC• 112481 G
10,SAO• 014100 G
10,SCS• 113011 G
10,801• 113110 G
10,SOO• 012•11 G
IO,SEC• 102520 G
10,SEM• 1~2440 G
I0 1 SHT• 112•11 G
10,SLO• 115410 G
IO.SMO• 0I02b6ll G
10,SNM• H2•50 G
10,SPS• 182420 G
I0 1 SPF• 0i12•40 G
IO,SSO• 104•00 G
IO,SST• 002430 G
IO,STC• 002500 G
IO,STP• 116400 G
10,SY~• 003040 G
IO, TRI,.. IH24U G
IO,UNL.• 000042 G
IO,wAT• 113410 G
IO.wL8• 000400 ~
IO,wLS• 100410 G
IO.~LV• 0~0500 G
l0 1 WNS• 1004"20 Ci
IO, wPti• H0440 G
IO,wVB• 111000 G
IO,XMT• 01440~ G
10,XNA• 114410 G
IQ,Q • llJHH2 G
IQ.X • li08Hl G
IS,8V • 100015 G
IS,CLR• 100010 G
IS,CR • 006401 G
IS,ESC• 115411 G
IS,PNO• 111080 G
lS,SET• 101012 G
IS,SPO• 111112 '
IS,SUC• 801011 G
QI,VER• 18138• G
SIMSG • IHHI
,,,GBL• 1eaa01

APPENDIX D
DIRECTIVE PARAMETER BLOCKS
D.l

QUEUE I/O

A 6- to 12-word DPB of the following format is used for the Queue I/O.
•'t U.

lfv I.).

1'1 l).
,~ l).

'" L) •
NL)•

UlC ( u 1 • J

Ul
Ut
UJ

1/U f lJtK .l .1.Ut'4

u<t
u~

;., u. uo
1-wU.

lfv l).

'" L).

... u.
lfv I.) •

D.2

l l

l.)l:'d S.Llt:.

....

Cuvl':..,

lb• 1 d ,

LUI'~,

l i:; t• j~ J

(!JIHUKin:J,

l AUU~t:..S.S Ur i/L) S'l'A'l'US bLUC.:KJ,
l 1/U UU1'4C: AS'l' St:..KvlC.:t:: l:.1'4 lt< ~ PUlN 1' J ,
t-'AKAMt.H.H # 1 ,
PAKA1'1t.It.R 11' ,
t-'AkAMl:::ft.K #3,
l:'At<Af•1t:.. lt.K I"''

t>ARA:'1~ft..K

I! :, ,

t->AkAMt:. ft:.H

# b.

QUEUE I/O AND WAIT

A 6- to 12-word DPB of the following format is used.
... u. uu

"'LJ. Ul

.... u. u.:
ff J.
UJ

WU.

Ut>d

lo•lt),

LUN,
Lt.r 1~1 Ill lPIHUtUBJ,
lAJUkt.6.S Ut' l/U ~>l'Al'US bLl.JCK],
l !IU UUi'4C.. ASL' .St:..K~1CI:. l:.N'ft<l PUlN lJ,
PAkAMt::lt:;.K I l ,

w1).

uo
uI

PAkA:-1t:.l't:.~

IN I.)•

t:-' AKAl•1l:. lt:;r<

# J. I
# j,

ll
1.:
1J

PAt<AMt.l't.K

II 'i '

•'WU•

Sl~t:.

CUUl':..,

'" l ) .

'" L.J.

t:-'AKA1-Wit. J.'t..K I!:>'
t-'AHAMc.'It.K

lb.

GET LUN INFORMATION
lfv

u. uu

'"I.). u l
,.. U.

D.4

( u j. J

r Ut-vC l llJN

1"IU.

.,. i).

D.3

U.lC
1/U

Ui.

UlC

(U~.)

LJ~d

Sl~t:.

l3.),

LUN,
AUUkt::.S~

SlX·~UHU

bUff t:.H.

ASSIGN LUN
irvu. vu

... u.

·'IU •

Ui.

hU •

~ LJl:'d ~llt:. (4.),
LUGlCAL UN11 NuMblH,
PHYSICAL Ut:.VlCt:: NAM~,
PttiSlCAL UtVlCt UN!T ~U~blk.

UlC (UJ.J

D-1

0.5

ALTER PRIORITY

A 4-word DPB in the following format is used.
·".J L).

"''I).
'" l).

141.).

O. 6

uu
vl

IJ J.C

.s J.tt; l 4.) •

(vO:I.) 6r IJPtS

i'A~I\

1~AM~

U-lt<~'I'

0111!

TA~f\

1'4A1~I:;

l~t.:CUl'W

lASf. PKlllt<.i'H.

HA Lr'),
HA,L,f).

REQUEST

A 7-word DPB in the ·following format is used.

wu. vu

D. 7

lHC ll 1.) '6. LiPli SH,c; (7.),

WI).

fASK

NAM~

(tlHbT HALf),

... u.

tAb~

NAM~

lS~CU~U

~l).

(Jj

lPAHflIJ.U~

t4U.
WIJ.

(~Ak'llllUN

lt'Hll>Hll~J,

~I.)•

(UlCJ.

HALt·J,
hALY)J,
NAMt. lS~CU~U hALt)J,
~AM~

lflH~T

EXECUTE

A 7-word DPB in the following format is used.
~v lJ •

WiJ •
WI)•

~'ii,) •

O<t

WlJ.

~..,

0.8

Uv
01
u I.

"4 lJ.

L> lC (lJ. ). & Ut>b ~H.t; ( 7.) ,
1' A61\ NAM!:; (f!K.S"f HALt ) ,

f A:)I\ NAMt; (~l:.i.;Ul'W HAL.if),
( P At< 1' l l 1 l) I~ NAMt.. Ci'l~Sl HALf)J,
l~Atn i'l'.lU1~ ~AMc; l St;CUNO HAlJi') J ,
l ~to< iUkJ.'l xJ ,
l ~ lC J •

SCHEDULE

A 13-word DPB in the following format is used.
~L>.

LJiC l l ~.)

ri• IJ.

(J i.

lf lt<SI ttA!Jf ) ,

~J,Za:;

Ul'b

(13.),

ttU.

vi.

'!ASK NAMt;
'i AS1' NAMt.

14 L).

lPAH'!'.LTlUi~

NAMt:.

lflt<Sl' HALE )J,

ii i.J.

li-'Ak'i !l.lUN

NAM~

(:;r..cuND hALt·) l ,

v~u.

o~
VO

lc'tHUt<l'i'X J,
Lu lC J ,

~CHtUUi,,t;

wu.
wV I).
iN

u. lU

WU.

II LJ •

Wt)•

... (). l4

lSl:.CUNO HAt..f),

iilJUI-<~

(O•lJ),

SCHE:;t.iUJ.,t:; Mi1~u1·~~
~Ct1~1.HJ1'C: .l)l:.l:t)1Wi>

(0-~IJ),

(0·!:>~),

oCHllJULt.: ClC~S (0•3~J,
l Kl:.•~C Ht:OU,L,t. J.Nlt:t<VAJ,, MAGt4J.lUOt:.J,

l t<~·SC ttt.uULt; ltHt.t< VAL

0-2

U~l'!~

(1•4)J •

D.9

RUN

An 11-word DPB in the following format is used.

wu.

0 \)

~L).

wlJ •

VJ.

llfU •

WI)•

wl). Ub
""I).

WI)•

l l
li

wu. lu
WU.

D.10

l l 7. ) (i, 1.H'tj Slit; (11.),
TA.St.. NAMt:; (i' lt<::>'I HALi"),
1' J\S K ~AME (St.CU NO HALf),
LPAt:HU'lU1~ NAMt:: ( f!HSl' HAL1' l l ,
( PA H l' 1 'l' l U1'4 NAMt.: (::>t:;Cut-40 HALI' ) l ,
[f)t<lUHLO j ,
lulU,
SCttt.lJULC: L>l:.LlA MAliN.l llJLH:;,
SCttt:.L>Ut.d:. Ut:.L.fA UN! lS (1•4),
L.-<1:.-::;c tti:;L>uLt:: lNft:kvAL MAli~ l 'i'lJlJi:. J ,
l .k i:.;- .SC n t:: lJ Ui, E. !a-..11:.H VAi.t i.JNllS (l•4Jl.

lJ lC

SYNC

A 12-word DPB in the following format is used.
'" lJ.

~u.

WI)•

Ut.

"'lJ. iJ j

WU. 0"
IN I)•

(J5

rJU •

wu • U I
~LI•

"'O •

l l
li
d

to u.
t~ i) •

b. i.Wd ::; l Zt: (l~.),
l'ASl\ NAM!:; O.lHSl HAi,,11 ) ,
TASK NAi~t:; ( S t: C LI I14 () HALto ) ,
ll?Ak'i i'l'lUN NAM!:: ( f l HST hALF'l J ,
lt'AtU J. T iUt'f NAMt; ( ~t:.:\.:UNU ttAL~ ) J ,

UlC ( 1 ~. J

LPKlUtU'fX J,
l J lC J ,
.SCHt.UULi:. Ut:.LT A MAliN 11 U lH~.,
.SCHt.OUJ.,t:.: uc;1.d'A uN1 ·rs ( l •4) ,
S 't ilfC ti~UN .l 'lA l iUN

UN.1.TS

(1•4),

l Kt:.•.S(. rtt:..LhJLI:; un.:t<VAL MA(,,r-.1 'l UDI:.: J ,
U<r.:•.:>C nt:.0ULC: Hdt:.kVA1.1 UNll .S l1•4)J.

D.11 MARK TIME
A 5-word DPB in the following format is used.
1tU.

VU
Ul

DIC liJ.) ~ OPd Slli (5.),
Lt;Vt.Nl' 1'.LA~ 1W1-\bt:R (1:.i'N)J I

"4i.J.

TlMt.

lNl~HVAL

~U.

U.3

f1M~

lNtt.M~A~

14U.

wU. Ut.t

D.12

LS~Slt.M

fMAP

MAGN!tUU~,
U~llS,

~NikX

PUlN1J.

CANCEL SCHEDULED REQUESTS

A 3-word DPB in the following format is used to cancel all scheduled
requests for an indicated task.

wu. 00
WU•

wlJ.

urc

& UP~ SlZ~ (3.),
TAbK NAMI:.: lflHSl HALF),
SCH~UUL~U fAS~ NAM~ (S~CO~D HALF).
(2~.)

bCH~OUL~U

D-3

A 5-word OPB in the following format is used to cancel only those
requests issued for an indicated task by an indicated task.

D,13

~u.

U!C

~u.

sc~~UUL~U

TA~K

NAM~

~CH~UU~~u

IA~~

NAM~

(~~.)

u~~

~u.

lSCHtUUL~~

{A~~

~u.

l~CH~UUL~H

lAS~

SlZ~

NAM~
NAM~

(5.),
CflHST HALf),
(S~CUN~ HALf'),
(fl~Sl

HAL~)J,

(S~COND

HALf)J.

CANCEL MARK TIME REQUESTS

A 1-word DPB of the following format is used to cancel all Mark Time
requests made by the issuing task.
~u.

vu ~· ul' lil.J ~ u~~ s1i~ ll.l.

A 3-word directive in the following format is used to cancel only
Mark Time request made by the issuing task and that set an indicated
event flag or cause an AST at an indicated location.

0.14

~u.

ui~

~u.

l~V~~I

~u.

(A~l

c,1.l & o~~ s1i~ (J.l,
Y~A~

NUM~~~

&l~V!~~

ll~N)J,

kUUTlN~

~N1k¥J.

CLEAR EVENT FLAG

A 4-word DPB of the following format is used.
wU.
~u.

0.15

UU
Vl

vlC lJl.J
~VtNl

r~A~

u~b

l2.J,

l~~~).

SET EVENT FLAG

A 2-word DPB in the following

D.16

s1i~

~UM~~H

fo~mat

~u.

ULC lJJ.J & UPd

~u.

~v~NA

t~A~

~ll~

~UMd~H

is used.
l2.J,

(~~-~).

DECLARE SIGNIFICANT EVENT

A 2-word DPB of the following format is used to read an event flag,
set an event flag, declare a significant event, and to report the
pre-event flag polarity.
hU.
~u.

U0 -~ UlC (J~.J ~ U~~ ~li~ (~.),
Vl -- ~v~N! ~~A~ NUMU~~ l~~~J.

A 1-word DPB in the following format is used to declare a significant
event.

D-4

D.17

READ EVENT FLAG

A 2-word DPB of the following format is used.
ulC l31.J
~~l::,~J

D.18

UPb

~LA{.,

SlZ~

~UMb~K

l~.),

(t.~~).

READ ALL FLAGS

A 2-word DPB of the following format is used.
·~ lJ.
fl L.).

D.19

1Hl

l3'1.)

AU0K~,:)~

SJ.~t,

UPb

U.),

Uf b4•bll

l~lH[UAL)

bU~f~~.

WAIT FOR SINGLE EVENT FLAG

A 2-word DPB of the following format is used.

D.20

~u.

I'll).

OlC

(~l.J

UPM

Slt~

c:vun FLA~ !'4lJ1•lbt.K

(~.),

(t:.H-.).

WAIT FOR LOGICAL OR OF FLAGS

A 3-word DPB of the following format is used to wait for event flags
of sets 0, 1, 2, or 3.
w'iU.

.-iL).

uH:: l43,) (I& UP8 s1i~ (J.),
.:>t.J lfW.lCATlJ;.{ (u, 1, J., 3),

~u.

Ui.

,:;txl~~~

iLA~

MAS~

~URU.

A 5-word DPB of the following format is used tQ wait for event flags
of set 4.
ff l).

1'o U •

1•1 l) •

ui.

t1U.

D.21

lJ J.C (43.J ~ UPu
J. i.t. ( ~. J ,
l"'ASK wurW f U~ f LA(;S l•lo,
NA.SI\ wUt<l) f UH. f LAliS 17•32,
I~ A.SI\ 11\UtW l"uH. r·LA~S B-4~,
•'1 A.::) I\ WUKI) l'lJK r· LiA<..S 49•b4.

WAIT FOR NEXT SIGNIFICANT EVENT

A 1-word DPB of the following format is used.
l"U.

0.i.C

l4~.J

UPu

Sll~

D-5

Cl.).

D.22

$USPEND

A 1-word DPB of the following format is used.

wu.
D.23
A

UlC

l~~.J

OPli SlZt (1.).

RESUME

3-word DPB of the following format is used.
wl) •

UV
01

~-vu.

wl) •

0.24

l J. ) ,
~ IJPU s l l.t.
N"1'lt:; ll' ~K~f HA1.ir·),
l\IAMi:: ( St;CUt~O HALf).

OlC l 4 I. )

·-

'l'A~I\

TAS~

EXIT

A 1-word DPB of the followipg format is used.

wu. UU ~- UlC l~l.J ~ U~d Sl~~ Cl.).
0.25

EXITIF

A 2-word DPB of the following format is used.
~u. OU -- UlC (~j.J ~ u~~ s1i~ (2.),
wU. Vl
~V~NT ~~A~ NUM~~H.

D.26

GET TIME PARAMETERS

A 2-word DPB of the following format is used.

D.27

vvu. vu

OlC Col.J

wµ. Ol

Avo~~s~

~ OP~ Sli~ l2.),
Ul' t$- .... u1w dur·n:.k.

GET TASK PA~TERS

A 2-word DPB of the following format is used.
~l>.
~IJ.

D.28
A

U1' (oJ.J 6r U.,~ SlZ~ (2.),
AUUk~~~ Uf Sl'l~~h ~UHO bUff~H.

vO
Ul

GET PARTITION PARAMETERS

4-word DPB of the following format is used.
ti I).

ViJ

UlC

U..!

LPAk'l'llJ.UN NAMt; Ct"lt<Sl' HALF)J,
l iJAk l' l HI.JN NAMt:; CSJ::COND HAL~JJ,
AUuk~S~ Ut0 'l'HKt;t!: wUHIJ .bUH.l:.R •

""L). \) l
WU.

wo. OJ

....

lb~.)

1).,~

Sil~

D-6

( 4.) ,

D.29

GET COMMON BLOCK PARAMETERS

A 4-word DPB of the following format is used.

ulC lb7.)

~-~ l) •

~L).

tiLOCk NAMc; (flHST HAL~),
CUM~UN bLUCK NAM~ (S~CONU HAL~),
AUUH~SS U~ ~l~rlt WUKU bU~f~k.

..vO •

"I). Ul

D.30

s1i~

UPb

(4.J,

CUMMU~

SEND DATA

A 5- to 8-word DPB of the following format is used.
~u.

UlC (11.)

~u.

H~C~l~c;H

TAS~

~u.

Ui
UJ

H~C~1vc;H

~U.

~~U.

lt:;Vt.NT l"LAG NUMt3.Et0,

wu.

[bUFFEH

wu.

AUUH~S~

wu. vb
0.31

UP~

SlZ~

l5.·8.),

(flkSl hALf),

NAM~

!ASK NAM~ (~~CONO hALt),
Uf UATA bLUCK,
SlZ~

•

l·i~~.J,

Lt>klUHln ur- seNOJ,

f1l.

LH~C~IVEH

SEND AND REQUEST OR RESUME

A 9- to 12-word DPB of the following format is used.
ulC C7J.) ~ UP8 SlGi:. (9.·1~.),
wl) • OU
wu. Ul
RECElVt.k !ASK NAM~ (flkST HALf),

wu.

~i).

;NI.).

Wt)•

~u.

wO. U7

.--

l~Vt.Nl

~~A~

ltj l).

10
11

~l).

li-'HluR!l' t Ui"

~u.

lH~Cl:.1 Vt:~

tJ l).

D.32

lASK NAM~ (SECU~U MALt),
lPAHllT!UN NAM~ (~lkSl HALf)J,
l~ARlltlUN NAME (S~CUND HALf)J,
lt:>HIUR.U.'X J,
lUlCJ,
AUUH~SS Uf UAIA bLUCK,

M~CElVt.H

ltiUff~k

SlZ~

NUM~t.HJ,

1•25~.J,

~t.t'40J 1

'l'lJ.

RECEIVE DATA

A 4- to 6-word DPB of the following format is used.
v>tlJ.
WU.

U!C

lSENU~~

~u.

Oi
OJ
04
U::>

wu.
wu.
WU•

0.33

(7~.)

TASK

lS~NUtK

tAS~

AUDH~SS

lbU~ft.K

S1Z~

L~uc.

uPb

(4•b),
HALf)),
(S~CUNU hALf)J,

Sli~

~AMl
~AM~

(fl~SI

bUff~H.

•

S1Uk~

1~2~~.J,

TlJ.

RECEIVE DATA OR EXIT

A 4- to 6-word DPB of the following format is used.

wu.

OlC (77.J

~U.

Ul ••

TASK

wO. Ui

lS~~U~K
[SENU~H

AUUH~bS

NU. U4

l8Uf~~K

S1Z~

~U.

wu.

LLUC. tu

~UP~

fAS~

Sl~l

NAM~
~AM~

(4•b),

(f1HS1 HALt)J,
(S~CU~U HALF)),

dUff~R.

•

SIUK~

l•l5~.J,

ill.

D-7

0.34

RECEIVE DATA OR SUSPEND

A 4- to 6-word DPB of the following format is used.
~ u~u ~''~

u1c

1\U.

lAti~

1'd).

uI.
uJ

l~~~Utk
LS~~UtH
ALJUt<t;S~

Ut'
~ii~

~u.

D.35

l7~.J

~·· u.

1·H.1.

U 't

l~~t'~t~

1•; l ) .

lLU(. tu

fAtiK

~AM~
wAM~

C4•b),
(flHST HALf)J,
(~~CU~U

HALf)J,

tjUtff~~.

~1UH~

1•J3~.J,

flJ.

ABORT
---

A 3-word DPB of the following format is used.

D.36

~u.

uu -· u1c

~v.

fAS~

w"U•

1.J'J,

l'A.:i!J..

C~J.J
~AM~
~A1111t:.

u~~ s1i~

CJ.J,

lt1K~l HA~f),
(.;~t;UNIJ tfAl,,~).

FIX-IN-MEMORY

A 3-word DPB of the following format is used.
UlC

l8~.J

... u .. 0 l

lA~~

~AM~

l~ikSf

\)I.

fAS~

~AM~

(b~C~NU

1411).
..... L).

D.37

1)1,)

u~u

&!'~

CJ.),

HA~fJ,

riALr> •

A 3-word DPB of the following format is used.

D.38

UlC

(~1.)

~UP~

~u.

Ul ••

IA~~

NAMt

l~lHSf

Cl.),
HALYJ,

~u.

fAbK

NAM~

l~tCUNU

HAL~).

~u.

s1i~

DISABLE

A 3-word DPB of the following format is used.

D.39

01c c~1.J ~ u~~ size cJ.J,

~lJ.

~u.

lA~~

~AM~

(~lk~l

~u.

vi.

!AS~

~AM~

(S~~u~o

HALf),
HALf).

ENABLE

A 3-word DPa of the following format is used.
00
0 .1

ulC (~3.J
IASK ~AM~

,,, I).
~L).

04'

lA5~

(~~CU~D

~I).

NAM~

U~d

Sil~

(fl~ST

C3.J,

rlA~f),

HALf).

D.40

DISABLE CHECKPOINTING

A 1-word DPB of the following format is used.
i"<U e

D.41

ENABLE CHECKPOINTING

A 1-word DPB of the following format is used.
~o.

D. 42

INHIBIT AST. RECOGNITION

A 1-word DPB of the fol'lowing format is used.
1•n).

D.43

IJ U

ulC

(9~.J

& UPd

s1i~

(1.).

ENABLE AST RECOGNITION

A 1-word DPB of the following format is used.
~u.

D.44

OlC llUl.J

UP~

Slil (1.),

SPECIFY SST VECTOR TABLE FOR DEBUGGING AID

A 3-word DPB of the following format is used.

D.45

l'I L).

\,) u

hi).

UlC llOJ.J
AUUHtbS Uf

1•,u.

NUM~~~

uP~

~Sl

~l~~

~EClUH

lA~~~

(J,),
TA~~~.

~NTHl~S

ld),

SPECIFY SST VECTOR TABLE FOR TASK

A 3-word DPB of the following format is used.
¥'1

D.46

u. () u

01~

llu~.)

~'I;,) •

I,) 1

AUUMt~~

..., l ; .

u J.

~UM~~H

Uf
UY

& LJ~~ SlZ~ (J.),
s~r vlClUH lAbL~.
1AtiL~

~~~Hl~b

(ij),

SPECIFY RECEIVE AST

A 2-word DPB of the following format is used.
•'YU•

01c llU/.J & o~~

~LJ.

LA~1

b~HVlC~

5!~~

~N1Ht

(i.J,

~U1N1J.

D-9

D.47

SPECIFY POWER FAIL AST

A 2-word DPB of the following format is used.

D.48

nu.

Ul~

~LJ.

(ASl Sl:.t<'V lCt:;. i:;NlRi

llU~.J

& OPb

SlZ~

(~.),

PlJlt-.TJ,

SPECIFY FLOATING POINT EXCEPTION AST

A 2-word DPB of the following format is used.

wu. uu
-hu.

D.49

UlC (111.J ~ U~d SlZ~ li.),
lASt Sl:.~ViC~ l:.NTRX PU!NTJ.

AST SERVICE EXIT

A 1-word DPB of the following format is used.
"4LJ.

D.50

I)\)

UiC

(11~.)

& U~d

SlZ~

ll.),

GET SENSE SWITCHES

A 1-word DPB of the following format is used.
~u.

D.51

ulC CllS.J

uPd SllE Cl.).

GET MCR COMMAND LINE

A 41-word DPB of the following format is used.
~u.

14V.

UlC (lll.J & UP~ SIZ~ (41.),
flHSl ~UHO Uf 8U·b~T~ bUYt~~.

D-10

INDEX
GET COMMON BLOCK PARAMETERS
(GCOM$), 3-33
GET LUN INFORMATION (GLUN$) , 3-35
GET MCR COMMAND LINE {GMCR$) ,
3-36
GET PARTITION PARAMETERS (GPRT$) ,
3-37
GET SENSE SWITCHES (GSSW$) , 3-38
GET TIME PARAMETERS (GTIM$),
3-39
GET TASK PARAMETERS (GTSK$) , 3-40
Global conunon directory, 2-6
Global flags, 4-2

ABORT TASK {ABRT$) , 3-14
ALTER PRIORITY {ALTP$) , 3-15
ASSIGN LUN {ALUN$) , 3-16
AST SERVICE EXIT (ASTX$), 3-17
Asynchronous system trap {AST) ,
4-17
Asynchronous system trap queue,
2-8
Batch conunand buffer, 2-8
CANCEL MARK TIME REQUESTS {CMKT$) ,
3-20

CANCEL SCHEDULED REQUESTS (CSRQ$) ,
3-21
C condition code, 3-2
Checkpointable task list, 2-7
CLEAR EVENT FLAG {CLEF$) , 3-19
Clock queue, 2-5
Control of task execution, 2-3

INHIBIT AST RECOGNITION (IHAR$),
3-42

Interrupt connect node, 2-7
I/O operations, 2-9
I/O request queue, 2-6
Local flags, 4-3

DECLAR,E SIGNIFICANT EVENT (DECL$) ,
3-23
Device handlers, 1-4
DIR$, 3-4, 3-22
Directive conventions, 3-3
Directive forms, 3-4, 3-5
$,
$C,
$S,
Directive implementation, 3-1
Directive status word {OSW) , 3-2
Directive sununaries, 3-8
DISABLE {DSBL$) , 3-24
DISABLE CHECKPOINTING {DSCP$) ,
3-25
EMT 377, 3-1
ENABLE AST RECOGNITION (ENAR$) ,
3-26
ENABLE (ENBL$) , 3-27
ENABLE CHECKPOINTING {ENCP$) , 3-28
Error returns, 3-3
Examples of macro calls, 3-7
EXECUTE {EXEC$) , 3-29
EXITIF {EXIF$) , 3-30
EXIT {EXIT$) , 3-31
Executive trap service routines,
4-6
Fixed task list, 2-8
FIX IN MEMORY {FIX$) , 3-32

MARK TIME (MRKT$) , 3-43
MCR conunand buffer, 2-8
Memory management, 1-2, 2-1
Memory required list, 2-7
Multiprogramming, 2-3
Node pool, 2-7
Partitions, 2-2
Physical unit directory, 2-6
Processor priorities, 4-9
PSECT, 3-5
QUEUE I/O (QI0$) , 3-44
QUEUE I/O AND WAIT {QIOW$) I 3-47
QIO directives, 2-9
READ ALL FLAGS {ROAF$) , 3-48
READ EVENT FLAG (RDEF$) , 3-49
RECEIVE DATA {VRCD$) I 3-66
RECEIVE DATA OR EXIT {VRCX$),
3-70
RECEIVE DATA OR SUSPEND (VRCS$) ,
3-68
REQUEST (RQST$) , 3-50
RESUME (RSUM$) , 3.-51
RUN (RUN$), 3-52

Index-1

SCHEDULE (SCHD$), 3-54
SCOM, see system communications
area
SEND DATA (VSDA$) , 3-72
SEND DATA AND RESUME OR REQUEST
RECEIVER (VSDR$) , 3-74
SEND and RECEIVE directives, 3-13
Send/receive queues, 2-7
SET EVENT FLAG (SETF$) , 3-56
Shared global areas, 2-2
Significant events, 1-3, 2-4, 4-1 4-3
SPECIFY FLOATING POINT EXCEPTION
AST (SFPA$) I 3-57
SPECIFY POWER RECOVERY AST
(SPRA$) , 3-59
SPECIFY RECEIVE AST (SRDA$) , 3-66
SPECIFY SST VECTOR TABLE FOR
DEBUGGING AID (SVOB$), 3-61
SPECIFY SST VECTOR TABLE FOR TASK
(SVTK$) , 3-62
SUSPEND (SPND$) I 3-58
SYNCHRONIZE (SYNC$) , 3-63
Synchronous system trap (SST) , 4-4
Symbolic offsets, 3-6
System communication area (SCOM) ,
2-2

System directives, 1-4
System lists, 2-5, A-1
System tables, 2-5, A-1
System task directory, 2-6
System traps, 1-3, 2-5, 4-3
Task, definition of, 1-2
TASK EXIT (EXIT$), 3-31
Task partition directory, 2-7
UNFIX (UFIX$) I 3-65
Using directives, 3-4
WAIT FOR LOGICAL OR OF FLAGS
(WTLO$), 3-78
WAIT FOR SIGNIFICANT EVENT (WSIG$) ,
3-77
WAIT FOR SINGLE EVENT (WTSE$) ,
3-79

Index-2

RSX-llD Executive
Reference Manual
DEC-11-0XERA-B-D

READER'S COMMENTS
NOTE:

This form is for document comments only. Problems
with software should be reported on a Software
Problem Repcrt (SPR) form

Did you find errors in this manual?

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

Is there sufficient docume<ltation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.

Assembly language programmer
Higher-level language programmer
(] Occasional programmer (experienced)
User with little programming experience
(] Student progranuner
[] Non-progranuner interested in computer concepts and capabilities

Name

Date _________________________

Organization----------------------------------------~-------------------

Street------------------------------------------------------------------City __________________________ state~-----------Zip Code----~-------or
Country
If you require a written reply,

please check here.

O·

·------------------------------------------------------------Fold llere------------------------------------------------------------

------------------------------------------------ Do Not Tear - Fold llere and Staple -----------------------------------------------

FIRST CLASS
PERMIT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL
NO POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

Postage will be paid by:

~nmnnma
Software Communications
P. 0. Box F
Maynard, Massachusetts 01754

~omoomo
digital equipment corporation

Printed in U.S.A.