EasyManua.ls Logo

Xerox 900 series - MONARCH UPDATE ROUTINE ($UPDATE)

Xerox 900 series
105 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
I
;1
•
-\*
I
SCIENTIPIC
DATA
SYSTEMS
IDENTIFICATION:
PURPOSE:
ACTION:
ICALLING
'SEQUENCE:
PROGRAMMING
CONVENTIONS:
84
SOS
PROGRAM
LIBRARY
PROGRAM
DESCRIPTION
042010 (900 Series)
Catalog
Nos.
642026 (9300)
MONARCH
UPDATE ROUTINE ($UPDATE)
To
create
new
MONARCH
system
tapes
and
to
update
existing
system
tapes.
See
Section
4
of
the
MONARCH
Reference
Manual
for a
de-
tailed
description
of
the
functional
capabilities
of
this
routine.
Performs
insertion,
deletion
and
replacement
functions
related
to
creat-
ing
and
maintaining
a
MONARCH
system
tape.
See
Section
4
of
the
MONARCH
Reference
Manual
for a
description
of
the
operations
per-
formed
by
this
routine.
BRM
MONUPD
with
the
following
MONARCH
Unit
Assignment
Table
entries
set
as
indicated:
(QSYS)
=
unit
and
channel
addresses
of
magnetic
tape
unit
con-
taining
the
old
system
tape
in
bits
0-8.
Address
of
a
magnetic-tape
input/output
subroutine
in
bits
9-23.
(QSYST)
=
unit
and
channel
addresses
of
magnetic
tape
unit
on
wh
ich
the
new
system
tape
is to
be
written
in
bits
0-8.
Address
of
a
magnetic-tape
input/output
subroutine
in
bits
9-23.
(QSYSU)
=
unit
and
channel
address
of
a
card
reader
or
paper-tape
reader
in
bits
0-8.
Address
of
a
card
or
paper-tape
in-
put
subroutine
in
bits
9-23.
(QMSG)
=
unit
and
channel
addresses
of
control-message
input
de-
vice
in
bits
0-8.
Address
of
an
input
subroutine
for
the
control-message
device
in
bits
9-23.
(QSMO)
=
unit
and
channel
address
of
typewriter
or
line
printer
in
bits
0-8.
Address
of
a
typewriter
or
line
printer
output
subroutine
in
bits
9-23.
Relocatable
subroutine
assembled
with
META-SYMBOL
assembly
pro-
gram.
No
PROGRAMMED OPERATORS
are
used.
With
the
exception
of
typewriter
messages,
communication
with
input/output
subroutines
is
via
the
MONARCH
Unit
Assignment
Table.
The
routine
is
written
in
such a
way
that
it
relies
on
subroutines
in
the
MONARCH
Monitor
end
hence
it
is
loaded
into
memory
above
the
MONARCH
Monitor
subroutines
to
which
it
refers.

Table of Contents

Related product manuals