|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 76160 (0x12980)
Types: TextFile
Names: »D90«
└─⟦5dbd6b396⟧ Bits:30005867/disk12.imd Dokumenter (RCSL m.m.)
└─⟦this⟧ »D90«
F_ i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. CALL ................................................... 2
3. FUNCTION ............................................... 3
4. EXAMPLES ............................................... 4
5. ERROR MESSAGES ......................................... 5
\f
F_ ii
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
The program is a diagnostic tool for printing statistical infor-
mation maintained by a physical disc driver, serving a disc
storage module (RC82xx) connected to an RC8000 computer.
The program may as well print directly from the core as from a
file containing a core picture.
\f
F_ 2_._ _ _ _ _ _ _ _ _C_A_L_L_ 2.
M_m_m_ 1
discstat disc.<drivername>(<device>)
P_p_p_ 0
or
discstat dump.<dumparea>.<proc descr addr>
<device>::= <devicenumber>
<dumparea>::= name
<devicenumber>::=
<proc descr addr>::= integer
\f
F_ 3_._ _ _ _ _ _ _ _ _F_U_N_C_T_I_O_N_ 3.
The program sends a message to the specified driver to collect
the statistics. The driver may be either a logical or a physical
disc driver - in either case the statistics concern the informa-
tion created by a physical driver.
Please note that the driver will reset its statistics when the
information has been collected. Please also note that a logical
disc holding a logical backing storage during normal use will be
reserved by the anonymous process executing process functions -
therefore use the discstat program on the physical disc driver or
on another logical disc (e.g. the autoload disc) on the same
physical disc.
If <device> is specified the program creates a peripheral process
named <drivername> to the device.
If the first parameter is 'dump', it is supposed that the backing
storage area <dumparea> contains a core picture with core address
0 equivalent to area address 0.
The driver addressed may be either a logical or a physical disc
driver - in either case the statistics concern the information
created by a physical driver.
\f
F_ 4_._ _ _ _ _ _ _ _ _E_X_A_M_P_L_E_S_ 4.
The following command extracts statistics about the disc to which
the disc driver process named 'disc2' is connected:
discstat disc.disc2
The following command creates the peripheral process 'disc2auto'
on device 12:
discstat disc.disc2auto.12
The following command extracts statistics about the disc with the
process description address 24678 from the coredump in the file
named core8000:
discstat dump.core8000.24678
\f
F_ 5_._ _ _ _ _ _ _ _ _E_R_R_O_R_ _M_E_S_S_A_G_E_S_ 5.
***discstat, syntax
syntax error in call
***discstat, buffer claim exceeded
no message buffer available
***discstat, monitor result<result>
a normal answer was not received from the disc driver.
<result> is the result deliverd in the answer to the message
***discstat, create <result>
not possible to create a peripheral process for a reason given
by <result>
***discstat, status error <status>
<status> is the (decimal) statusword received from the disc
driver
\f
F_
\f
\f
i
F_O_R_E_W_O_R_D_
First edition: RCSL No 43-GL11342.
Second edition: RCSL No 43-GL11696.
The text has been changed on the following points because the
reference manual is now available:
- chapter 4: Pseudonet, is deleted.
- the resource demands are defined.
Some minor changes in the program are the reason for changes
concerning:
- warning about suspending of testoutput after an error
- new program parameter 'first'.
Finally the possibility of stopping the execution of SMM by
removing the NPM process is no longer recommended.
The corrections are marked with lines in the left margin.
Lis Clement
A/S REGNECENTRALEN af 1979, November 1981
\f
ii
\f
iii
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
1.1 Notation for Character Values ..................... 1
2. COMMUNICATION FROM RC8000 CONSOLE ...................... 2
2.1 Program Start Up .................................. 2
2.2 Warnings .......................................... 3
2.3 Alarms ............................................ 3
2.4 Program Close Down ................................ 6
3. COMMUNICATION WITH NETWORK TERMINAL .................... 7
3.1 Session Establishment ............................. 7
3.2 Inputs ............................................ 7
3.2.1 Interrupts ................................. 7
3.2.2 Text Block Primitives ...................... 8
3.2.3 Control Block Primitives ................... 9
3.2.4 Parameter Block Primitives ................. 9
3.2.5 Negotiation Phase Commands ................. 9
3.2.6 Input Conversion ........................... 9
3.3 Outputs ........................................... 10
3.3.1 Interrupts ................................. 10
3.3.2 Text Block Primitives ...................... 10
3.3.3 Control Block Primitives ................... 11
3.3.4 Parameter Block Primitives ................. 11
3.3.5 Negotiation Phase Commands ................. 11
3.3.6 Output Conversion .......................... 11
3.4 Normal Printouts .................................. 11
3.5 Errors ............................................ 12
3.6 Session Termination ............................... 13
3.6.1 Abort and Disconnect Causes ................ 14
A_P_P_E_N_D_I_C_E_S_:
A. REFERENCES ............................................. 15
B. SURVEY OF SMM PARAMETERS ............................... 17
\f
iv
\f
F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This paper describes - briefly - how to use the RC8000 Scroll
Mode Mapping module (SMM) when it is applied to the CENTERNET
Scroll Mode Terminal module (SMT).
The paper contains two main chapters. Chapter 2 is the operating
guide for the SMM on the RC8000, i.e. the procedures for start up
and close down are described together with the possible alarms
and printouts which may occur on the RC8000 console. Chapter 3 is
the user's guide for the network terminal using the Virtual Ter-
minal Protocol on the X.28 interface in order to access the
RC8000 as a host computer.
Appendix A lists the references to other manuals and appendix B
gives a survey of the possible parameters for the SMM program.
1_._1_ _ _ _ _ _ _ _N_o_t_a_t_i_o_n_ _f_o_r_ _C_h_a_r_a_c_t_e_r_ _V_a_l_u_e_s_ 1.1
Character values are given in the same way as in ref. 2. A
character value is defined by <column>/<row> referring to the
IA5 Basic Code Table.
I.e. 2/0 corresponds to the character value 2*16 + 0 = 32 (= SP)
and 6/13 = 6*16 + 13 = 109 (= m).
\f
F_ 2_._ _ _ _ _ _ _ _ _C_O_M_M_U_N_I_C_A_T_I_O_N_ _F_R_O_M_ _R_C_8_0_0_0_ _C_O_N_S_O_L_E_ 2.
The SMM module is started from an RC8000 console as a program in
an internal process (by means of the File Processor (FP)).
2_._1_ _ _ _ _ _ _ _P_r_o_g_r_a_m_ _S_t_a_r_t_ _U_p_ 2.1
Via the operating system 's' an internal process is created. The
processname is the identification of the application used during
session establishment, see section 3.1.
The size and the other resources reserved by the process must be
sufficient to run the SMM module (= program). The bases must be
-8388607, 8388605. The resources depend mostly on the program
parameters 'terms' and 'letters':
size: 60566 + terms * (2622 + letters * 370) HW
buf: 5 + terms * (6 + letters)
area: 3 + terms
the numbers refer to release 1.20. Further details concerning
evaluation of the resource demands can be found in ref. 7.
The parameters to the program can be stated, when the program is
activated by FP, e.g. number of terminals and NPM processname. A
survey of the possible parameters is given in appendix B.
When the program is started, it prints the release identification
and a verification of the program parameters. See example 1.
\f
M_ att s
new smm base -8388607 8388605 size 87000 buf 70 area 11 run
ready
to smm
smmp terms.8 ctest.255 testname.smmtestmax netname.npm3
smm release: 1.20
date: 81 10 24
terms: 8
first. default
letters: default
recmask1: default
recmask2: default
delay: default
waitatt: default
netname: npm3
pseudonet: default
log: default
ctest: 255
testname: smmtestmax
cyclic: default
P_ trace: default
Example 1: Activation of the SMM program from RC8000 main con-
sole.
2_._2_ _ _ _ _ _ _ _W_a_r_n_i_n_g_s_ 2.2
Warnings are printouts on current output indicating an error, but
the execution of the program keeps going.
The only warning from the program occurs if the production of
testoutput is stopped because of an illegal status:
testoutput stopped, status =..., halfwords=..., segment count=...
2_._3_ _ _ _ _ _ _ _A_l_a_r_m_s_ 2.3
Alarms are printouts on current output when the execution of SMM
is stopped. They are all serious errors which cannot be repaired
by SMM, e.g. program errors (index, field and the like) and the
network program is not accessible.
\f
The alarms provided by the ALGOL8 running system are not listed,
but can be found in ref. 3, 4 and 5.
The alarms are given in alphabetical order.
appl mess <res> One of the application message corou-
tines cannot be started. <res> is the
result received from the ALGOL8 proce-
dure new _activity, cf. ref. 4.
break 6 Too many buffers used, cf. ref. 3.
fatal <no> A fatal error has been discovered and
<no> =
1 an output message to the network is
greater than the network buffer size
2 the application process, which has
sent a message to SMM, is not
available when SMM wants to access
its process description in order to
get its name
3 illegal action
4 illegal state
5 operation received from the delay
semaphore
7 pseudonet only: the message area
cannot be accessed
8 pseudonet only: the answer area can-
not be accessed
9 pseudonet only: the buffer area of a
message or an answer cannot be ac-
cessed.
netinput <res> As 'appl mess' but concerning the net-
work input coroutine.
npm ans <res> As 'appl mess' but concerning the
pseudonet coroutine: npm answer.
\f
npm mess <res> As 'appl mess' but concerning the
pseudonet coroutine: npm message.
npm res <res> Dummy answer received from the npm pro-
cess. <res> is the result from the moni-
tor function wait _answer (18), cf. ref.
6.
ps create <res>*1000 + <index>
If <res> is greater than zero then the
creation of the pseudo process corres-
ponding to <index> was unsuccessful.
<res> is the result received from the
monitor function create _pseudo _process
(80), cf. ref. 6.
If <res> is zero the creating of the
pseudo process corresponding to <index>
was reported correctly but the investi-
gation of the process description by
means of the monitor function
process _description (4) failed.
<index> less than or equal to the number
of terminals indicates pseudo processes
named 'smm<first>', 'smm<first+1>' and
so on, while <index> equal to 1 + number
of terminals indicates the pseudonet.
start <res> As 'appl mess' but concerning the start
network input coroutine.
terminal <res> As 'appl mess' but concerning one of the
terminals.
\f
2_._4_ _ _ _ _ _ _ _P_r_o_g_r_a_m_ _C_l_o_s_e_ _D_o_w_n_ 2.4
The program may be closed down by breaking the SMM process.
Before the program stops, it tries to close all the ports and to
remove the pseudo processes created for the terminals and the
pseudonet. These actions are provided by the trap routine. In
order to inform the operator about the state of the clearing, the
trap routine produces a printout
- at entry
- when a close port attempt has been performed
- when a remove pseudo process has been executed
- at exit.
Finally the ALGOL8 printout 'end <blocksread>' will appear.
M_ att s
prog smm break
ready
from smm
break 8 monitor
called from ...
called from ...
.
.
.
coroutine 0 result -4
trap entry
ports closing
port 3 closed
smm1 removed
trap exit
end 518
from s
P_ pause smm break
Example 2: Normal Close down of SMM program by means of s-command
BREAK.
\f
F_ 3_._ _ _ _ _ _ _ _ _C_O_M_M_U_N_I_C_A_T_I_O_N_ _W_I_T_H_ _N_E_T_W_O_R_K_ _T_E_R_M_I_N_A_L_ 3.
The communication between SMM and the network terminal is based
on the X.28 interface and the Virtual Terminal Protocol (VTP),
see ref. 2 and 1 respectively.
3_._1_ _ _ _ _ _ _ _S_e_s_s_i_o_n_ _E_s_t_a_b_l_i_s_h_m_e_n_t_ 3.1
Sessions can only be established on initiative of the terminal
operator, i.e. use the selection command.
Example: keying
.recau,.smm CR
will connect the terminal to the RC8000 located at RECAU provided
that the SMM module is in service under the pseudonym 'smm', i.e.
the process name.
3_._2_ _ _ _ _ _ _ _I_n_p_u_t_s_ 3.2
3_._2_._1_ _ _ _ _ _I_n_t_e_r_r_u_p_t_s_ 3.2.1
INT interrupts the current operation, if any. If an
input operation is interrupted, the application is
answered status = timer and no characters are for-
warded, and a clear mechanism is started. Other-
wise the text 'att' is sent to the terminal en-
abling the operator to write the processname. The
processname may be empty which means same name as
current process.
Note that the first interrupt on the terminal must
be an INT in order to define the processname.
INTD interrupts the current operation, if any. If an
input operation is interrupted, a clear mechanism
is started. The processname cannot be changed,
i.e. logically an INTD has the same function as if
the text 'att' after an INT has been answered with
EOM without any text characters was entered.
\f
XPARAM is ignored.
RESET interrupts the current operation, if any and a
clear mechanism similar to the one in SMT, see
ref. 1, is activated.
PLEASE acts as INT when the terminal is either idle or
receiving output from the application. In any
other state, the PLEASE primitive is ignored.
(PLEASE is not defined as an interrupt, but in
this case it is treated as a kind of an inter-
rupt).
EOM(2) in addition to terminate the input line as any
other EOM indicator, EOM(2) acts as an INT, but
the clear mechanism is not activated.
(EOM(2) is not defined as an interrupt, but in
this case it is treated more like an interrupt
than a text block primitive).
3_._2_._2_ _ _ _ _ _T_e_x_t_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.2.2
TEXT-SEG is accepted when the terminal has the turn, i.e.
when either a process name may be stated or when
the application wants input.
The characters from one or more TEXT-SEG are
stored in a buffer either until the buffer is full
or until an EOM is received.
EOM(2) see subsection 3.2.1: Interrupts.
All other text block primitives are illegal and will start a
clear mechanism.
\f
3_._2_._3_ _ _ _ _ _C_o_n_t_r_o_l_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.2.3
PLEASE see subsection 3.2.1: Interrupts.
CLEAR-MARK the primitive is used in the clear mechanism.
ASSIGN illegal, i.e. a clear mechanism is started.
3_._2_._4_ _ _ _ _ _P_a_r_a_m_e_t_e_r_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.2.4
All parameter block primitives are illegal and will cause the
start of a clear mechanism.
3_._2_._5_ _ _ _ _ _N_e_g_o_t_i_a_t_i_o_n_ _P_h_a_s_e_ _C_o_m_m_a_n_d_s_ 3.2.5
CONN a connect block is accepted if the parameter TER-
MINAL-MODE is selected as scroll mode. If more
parameters are given, they must allow the default
values, cf. ref. 1.
No other negotiation phase commands are valid, i.e. they will
abort the session.
3_._2_._6_ _ _ _ _ _I_n_p_u_t_ _C_o_n_v_e_r_s_i_o_n_ 3.2.6
Capital letters are converted to small letters in order to serve
terminals where small letters cannot be input.
The conversion condition is set to true when
- the terminal is connected
- the text 'att' has been written on the terminal
- an INTD is accepted.
The conversion condition is set to false when
- a small letter is received.
\f
When the conversion condition is true, the capital letters A
through Z and the 3 national letters (e.g. Æ, Ø, Å) (i.e. 4/1
through 5/13) are converted to the small letters (i.e. 6/1
through 7/13).
The characters (5/14) and (7/14) are converted to NUL (0/0)
no matter what the conversion condition is.
When data are forwarded to the application, they are finished by
an NL character (0/10).
3_._3_ _ _ _ _ _ _ _O_u_t_p_u_t_s_ 3.3
3_._3_._1_ _ _ _ _ _I_n_t_e_r_r_u_p_t_s_ 3.3.1
The only interrupt sent by SMM to the terminal is RESET.
RESET is sent whenever the program discovers an illegal
situation during normal VTP communication, as long
as this situation can be repaired, otherwise the
session is aborted.
3_._3_._2_ _ _ _ _ _T_e_x_t_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.3.2
TEXT-SEG is sent during output from an application or when
SMM wants to inform the operator about a change in
current state, e.g. shift in communicating process
(to <proc>, from <proc>), before receiving a new
process name (att) and in an error situation.
NL is sent after an EOM is received from the terminal
in order to simulate an ordinary RC8000 communica-
tion and to indicate that the input has been re-
ceived.
\f
3_._3_._3_ _ _ _ _ _C_o_n_t_r_o_l_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.3.3
The only control block primitive used is CLEAR-MARK. The primi-
tive is sent in a clear situation only.
3_._3_._4_ _ _ _ _ _P_a_r_a_m_e_t_e_r_ _B_l_o_c_k_ _P_r_i_m_i_t_i_v_e_s_ 3.3.4
No parameter blocks are sent from SMM.
3_._3_._5_ _ _ _ _ _N_e_g_o_t_i_a_t_i_o_n_ _P_h_a_s_e_ _C_o_m_m_a_n_d_s_ 3.3.5
The only negotiation command used by SMM is CACC. The parameters
received in the CONN command are answered in the CACC by means of
the default values given in ref. 1 except the TERMINAL-MODE as
this one must be scroll mode.
3_._3_._6_ _ _ _ _ _O_u_t_p_u_t_ _C_o_n_v_e_r_s_i_o_n_ 3.3.6
The data from the application are sent to the terminal in text
blocks without EOM (i.e. EOM(0)).
The NL character (0/10) is sent as an NL primitive whereas the
characters SP through å, except (i.e. 2/0 through 7/13 except
5/14) are sent - without conversion - as TEXT-SEG primitives. All
other characters are ignored. One TEXT-SEG primitive holds at
most 60 characters.
3_._4_ _ _ _ _ _ _ _N_o_r_m_a_l_ _P_r_i_n_t_o_u_t_s_ 3.4
During normal communication a number of printouts are produced by
SMM, i.e.
NLatt indicates that a (new) process name may be
written on the terminal.
\f
NL receipt on an input operation implying that
the characters have been forwarded to the
application or a process name has been
received.
NLto <process>NL indicates that <process> is able to receive
data. The text is sent only if the former
process was different to <process>.
NLfrom <process>NL is written if the succeeding data is sent by
an other process than latest active
application.
EOM(2) indicates that the application is able to
receive input; the turn is changed in order to
enable the operator to enter data and the bell
is activated.
3_._5_ _ _ _ _ _ _ _E_r_r_o_r_s_ 3.5
Errors are printouts indicating an illegal situation, which is
not serious, e.g. misspelling a process name.
The errors are listed in alphabetical order.
disconnectedNL Dummy answer (4) on an attention
message to the application.
does not existNL Dummy answer (5) on an attention
message to the application.
illegalNL The process name is not the name of an
internal process.
NLlast inputline skippedNL The last input line has not been for-
warded to the application because it
was longer than wanted by the
application or similar errors.
\f
no answerNL The application did not answer the at-
tention message within a certain (op-
tional) time limit. The attention mes-
sage has been regretted by SMM.
rejectedNL Dummy answer (2) on an attention
message to the application.
unintelligibleNL Dummy answer (3) on an attention
message to the application.
unknownNL The process does not exist. The name
is either the one just typed or
current process name if the name was
omitted.
unnormalNL Dummy answer (1); usually that answer
means normal answer but if this error
occurs it denotes an unnormal
situation in SMM.
3_._6_ _ _ _ _ _ _ _S_e_s_s_i_o_n_ _T_e_r_m_i_n_a_t_i_o_n_ 3.6
When the operator wants to terminate a session, the CLR command
is entered, and a receipt is forwarded to the terminal either
informing about the accept from SMM or the reason for an abnormal
termination.
A session may be terminated by the SMM; when it happens, the
cause is described by a number in the receipt.
\f
3_._6_._1_ _ _ _ _ _A_b_o_r_t_ _a_n_d_ _D_i_s_c_o_n_n_e_c_t_ _C_a_u_s_e_s_ 3.6.1
The cases used when sending abort or disconnect messages are:
cause explanation
0 disc confirmation
164 clear procedure error
166 connect procedure error
170 unexpected VTP CONN
176 SC protocol error
244 parameters not acceptable.
\f
F_ A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_ A.
1 RCSL No 43-GL11428:
C_E_N_T_E_R_N_E_T_,_ _V_i_r_t_u_a_l_ _T_e_r_m_i_n_a_l_ _P_r_o_t_o_c_o_l_ _(_V_T_P_)_,_ _R_e_p_o_r_t_
Per Høgh, Inger Marie Toft Hansen
A_b_s_t_r_a_c_t_: This document contains the specifications of the
Virtual Terminal Protocol for CENTERNET. The protocol covers
the three terminal classes, data entry, scroll and native.
The protocol definition is mainly based on the Data Entry
Protocol for EURONET (VTP-D/Issue 4). Scroll and native mode
terminals and parameters selection during a session have
been added. (Not printed yet).
2 RCSL No 43-GL11412:
C_E_N_T_E_R_N_E_T_,_ _X_._2_8_-_S_c_r_o_l_l_ _M_o_d_e_ _T_e_r_m_i_n_a_l_ _S_u_p_p_o_r_t_,_ _R_e_p_o_r_t_
Inger Marie Toft Hansen
(Not printed yet).
3 RCSL No 42-i0781:
A_L_G_O_L_7_,_ _U_s_e_r_'_s_ _M_a_n_u_a_l_,_ _P_a_r_t_ _1_
Bodil Larsen, August 1979
A_b_s_t_r_a_c_t_: Description of the ALGOL7 programming language.
(148 printed pages).
4 RCSL No 31-D581:
A_L_G_O_L_8_
Jørgen Zachariassen, November 1979
A_b_s_t_r_a_c_t_: Description of the ALGOL8 programming language, as
extensions to ALGOL7. ALGOL8 includes the activity concept,
allowing procedures to act as coroutines with current I/O
transfers, format 8000 procedures for IBM3270 compatible
transaction processing, new layout possibilities, character
constants and a few minor changes to ALGOL7.
\f
5 RCSL Nr. 31-D639:
A_L_G_O_L_,_ _C_o_r_o_u_t_i_n_e_ _S_y_s_t_e_m_,_ _B_r_u_g_e_r_v_e_j_l_e_d_n_i_n_g_
Jesper Tågholt, Oktober 1981
R_e_s_u_m__: Denne manual beskriver et coroutine system til brug
under ALGOL8.
6 RCSL No 31-D477:
R_C_8_0_0_0_ _M_o_n_i_t_o_r_,_ _P_a_r_t_ _2_,_ _R_e_f_e_r_e_n_c_e_ _M_a_n_u_a_l_
Tove Ann Aris, Bo Tveden-Jørgensen, January 1978
A_b_s_t_r_a_c_t_: This manual describes monitor conventions, monitor
procedures and format of monitor tables.
(129 printed pages).
7 RCSL No 43-GL11697:
C_E_N_T_E_R_N_E_T_,_ _R_C_8_0_0_0_ _S_c_r_o_l_l_ _M_o_d_e_ _M_a_p_p_i_n_g_ _M_o_d_u_l_e_ _(_S_M_M_)_
R_e_f_e_r_e_n_c_e_ _M_a_n_u_a_l_
Lis Clement, November 1981
A_b_s_t_r_a_c_t_: This document describes the functions and the
internal structure of the Scroll Mode Mapping module of
CENTERNET. The SMM module maps the SC and VTP formats/
protocols into the conventions of the standard terminal
interface, known as the way the RC822 terminal is accessed
from an internal process in RC8000.
(106 printed pages).
\f
F_ B_._ _ _ _ _ _ _ _ _S_U_R_V_E_Y_ _O_F_ _S_M_M_ _P_A_R_A_M_E_T_E_R_S_ B.
\f
F_
\f
i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. INSTALLATION ........................................... 2
2.1 The PICCOLO Microcomputer ......................... 2
2.2 The Electric Supply Mains ......................... 3
2.3 Coaxial Cables .................................... 3
2.4 Fuses ............................................. 4
3. FLEXIBLE DISC DRIVES (MINI AND MAXI) ................... 5
3.1 How to Insert the Flexible Disc ................... 5
3.2 The Flexible Disc ................................. 6
3.2.1 Care of the Discs .......................... 6
3.2.2 Write Protection ........................... 7
3.2.3 Type of Flexible Discs ..................... 8
4. DISPLAY UNIT ........................................... 10
4.1 Control Buttons and Plugs ......................... 10
4.1.1 Front ...................................... 10
4.1.2 Back ....................................... 10
4.2 How to Use the Display Unit ....................... 11
4.3 Cleaning .......................................... 11
5. KEYBOARD ............................................... 12
6. TECHNICAL DATA ......................................... 13
6.1 Signal Cables, Connections ........................ 13
6.2 Dimensioning, Weight, Consumption ................. 14
6.3 Microcomputer Specifications ...................... 14
7. FLOW CHART ............................................. 16
8. PARALLEL IN/OUT PLUGS .................................. 18
\f
ii
\f
F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
This user's guide describes how to use your new PICCOLO micro-
computer system
Chapter 2 describes how the system is installed and assembled,
whereas the flexible disc drive, the display unit and the key-
board are described in the chapters 3 to 5. There is a separate
description of the matrix printer.
Chapters 6 to 8 describe the cables and technical data.
The actual programming is dealt with in special manuals.
RC hope that your new microcomputer system will be very useful to
you, and should any problems arise, you are welcome to write to
your distributor.
\f
F_ 2_._ _ _ _ _ _ _ _ _I_N_S_T_A_L_L_A_T_I_O_N_ 2.
2_._1_ _ _ _ _ _ _ _T_h_e_ _P_I_C_C_O_L_O_ _M_i_c_r_o_c_o_m_p_u_t_e_r_ 2.1
The rooms in which the PICCOLO microcomputer systems are instal-
led, should - with a view to the legibility of the displays - be
located in such a way that large amounts of sunshine through the
windows are avoided. The electric light should be adjusted so as
to make the monitor display stand out clearly and without any
troublesome reflections. The flooring must be made of a material
that will give no problems with static electricity. For the same
reason, the relative humidity of the atmosphere must not be below
40%.
Below is shown which units of the PICCOLO microcomputer system
that are to be supplied with 220 V 50 Hz from the mains, and
which units that are to be supplied via the central processing
unit. The power socket should be three pin with an earth connec-
tion and socket sharing with other machines such as copying
machines or refrigerators should be avoided, as these may give
some troublesome noise pulses in the mains. We recommend the use
of an approved power distribution panel, e.g. the RC "power
panel" type MF002, which will handle up to 5 power connection
plugs.
M_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Unit Supplied Length of Power
from supply
P_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _m_a_i_n_s_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RC702 Microcomputer Socket Outlet 2.5 m 100 W
_ _ _ _ _ _ _i_n_c_l_._ _k_e_y_b_o_a_r_d_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_R_C_7_5_2_ _D_i_s_p_l_a_y_ _U_n_i_t_ _ _ _ _ _ _ _ _ _ _ _ _ _ _M_i_c_r_o_c_o_m_p_u_t_e_r_ _ _1_._6_ _m_ _ _ _ _ _ _ _ _ _ _3_0_ _W_ _
_R_C_7_6_1_ _F_l_e_x_i_b_l_e_ _D_i_s_c_ _D_r_i_v_e_ _M_i_n_i_ _ _M_i_c_r_o_c_o_m_p_u_t_e_r_ _ _1_._6_ _m_ _ _ _ _ _ _ _ _ _ _3_0_ _W_ _
_R_C_7_6_2_ _F_l_e_x_i_b_l_e_ _D_i_s_c_ _D_r_i_v_e_ _M_a_x_i_ _ _S_o_c_k_e_t_ _O_u_t_l_e_t_ _ _2_._0_ _m_ _ _ _ _ _ _ _ _ _ _8_0_ _W_ _
_R_C_7_9_1_ _L_i_n_e_ _S_e_l_e_c_t_o_r_ _ _ _ _ _ _ _ _ _ _ _ _ _S_o_c_k_e_t_ _O_u_t_l_e_t_ _ _2_._5_ _m_ _ _ _ _ _ _ _ _ _ _3_0_ _W_ _
_R_C_8_6_1_ _P_r_i_n_t_e_r_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _S_o_c_k_e_t_ _O_u_t_l_e_t_ _ _2_._0_ _m_ _ _ _ _ _ _5_0_-_3_5_0_ _W_ _
\f
The signal cable connection between the PICCOLO microcomputer and
peripheral units such as line selector, modem or other computers,
is established via standard cables supplied by RC in lengths of
5, 12 and 25 m. RC762 flexible disc drives are connected via 1 m
special cable delivered together with the disc drive. This also
applies to the printers.
Should you want any further information, you are welcome to con-
tact RC or your PICCOLO distributor.
2_._2_ _ _ _ _ _ _ _T_h_e_ _E_l_e_c_t_r_i_c_ _S_u_p_p_l_y_ _M_a_i_n_s_ 2.2
The microcomputer is connected to a socket outlet with earth
(3-pole). Apart from increasing the security, the earth connec-
tion serves to protect the electronic equipment against electric
noise.
2_._3_ _ _ _ _ _ _ _C_o_a_x_i_a_l_ _C_a_b_l_e_s_ 2.3
The coaxial cable is connected to the socket "VIDEO MONITOR" and
the antenna socket. The keyboard is connected to the socket
"KEYBOARD". Insert the plug into the socket and tighten the two
screws, but not too tight. The highest voltage in these cables
and the other plugs and sockets is 15 Volts.
\f
2_._4_ _ _ _ _ _ _ _F_u_s_e_s_ 2.4
The fuse (+ one spare one) is placed behind the power connection
socket in a small drawer. A blown fuse should only be replaced
once. If the second fuse blows too, there is something wrong, and
the computer should be repaired by your distributor.
\f
F_ 3_._ _ _ _ _ _ _ _ _F_L_E_X_I_B_L_E_ _D_I_S_C_ _D_R_I_V_E_S_ _(_M_I_N_I_ _A_N_D_ _M_A_X_I_)_ 3.
Flexible disc drive or Floppy Disc. The latter name is the one
generally used, although it is actually a slang phrase for the
flexible disc.
There are two types: MINI, which is built into the cabinet of the
microcomputer, and MAXI, which is detached. The maximum number
that can be installed is two, marked 1 and 2.
N.B.: It is not possible to have both MINI and MAXI drives on the
same central processing unit at the same time.
3_._1_ _ _ _ _ _ _ _H_o_w_ _t_o_ _I_n_s_e_r_t_ _t_h_e_ _F_l_e_x_i_b_l_e_ _D_i_s_c_ 3.1
MAXI: When the oblong button is
pressed, the door flies open. If
there is already a flexible disc in
the drive, it will be pushed out a
few centimetres, ready to be re-
moved.
\f
MINI: The door is tipped upwards.
Place a new flexible disc in the
opening with the label upwards as
shown on the picture and press it
into the opening until it is
locked. All this can be done no
matter whether the motor is running
or not. The red lamp will be alight
when data is transferred to or from
the flexible disc.
3_._2_ _ _ _ _ _ _ _T_h_e_ _F_l_e_x_i_b_l_e_ _D_i_s_c_ 3.2
The flexible disc is a thin, plasticcoated disc and the surface
can be magnetised. This disc is contained in a closed cardboard
envelope. Reading and writing is done in the oblong slit while
the disc rotates. Do not touch or damage the coating visible in
the slit.
3_._2_._1_ _ _ _ _ _C_a_r_e_ _o_f_ _t_h_e_ _D_i_s_c_s_ 3.2.1
Flexible discs should always be kept in protective covers. Do not
write with a ballpoint pen on the cover when the disc is inside.
\f
3_._2_._2_ _ _ _ _ _W_r_i_t_e_ _P_r_o_t_e_c_t_i_o_n_ 3.2.2
MAXI: Write Protect. If you wish to
protect what has already been writ-
ten on the flexible disc from being
overwritten (this automatically de-
letes the "old" data), you can make
a notch in the envelope, as shown
below. A hole puncher and a pair of
scissors can be used for this
(measurements in millimetres).
If, later on, you want to write on
the flexible disc, the notch can be
covered by a piece of opaque tape.
MINI: Write Protect. Is protected
by covering the notch on the edge\f
with tape (please notice that the opposite is the case with
MAXI).
3_._2_._3_ _ _ _ _ _T_y_p_e_ _o_f_ _F_l_e_x_i_b_l_e_ _D_i_s_c_s_ 3.2.3
The existing RC700 software packages support MINI as well as MAXI
flexible discs. Different types of flexible discs are used in the
individual packages.
The instruction manual for the different software packages con-
tains a detailed description of format, capacity, etc.
Generally the following three types of flexible discs are used,
and can be ordered through RC:
- Type 0, Unformatted
double sided flexible disc with double density coating.
- Type 1, Pre-formatted
single sided flexible disc with single density coating and a
sector size of 128 bytes.
- Type 2, Pre-formatted
double sided flexible disc with double density coating and a
sector size of 512 bytes.
All MINI flexible discs are supplied as type 0 flexible discs.
MAXI flexible discs are supplied as type 1 or type 2 flexible
discs. As for delivery, please see the RC700 Pricelist, under
accessories.
MINI 5 1/4" type 0.
- MEMOREX 3201-3421 or similar disc is used.
RC order number 47009.
MAXI 8" type 1.
- IBM1, 2305830 or similar flexible disc is used.
RC order number 47011. \f
Furthermore a double sided flexible disc can be used (with two
symmetrically placed index holes) corresponding to 3M 740/2-0.
RC order number 47012.
MAXI 8" type 2.
- 3M 743-0-512 or a similar flexible disc is used.
RC order number 47008.
As can be seen from the introduction material for the individual
software packages, the MINI flexible disc can be formatted cor-
responding to type 1 or type 2. In some systems it is, further-
more, also possible to reformat MAXI flexible discs.
\f
F_ 4_._ _ _ _ _ _ _ _ _D_I_S_P_L_A_Y_ _U_N_I_T_ 4.
4_._1_ _ _ _ _ _ _ _C_o_n_t_r_o_l_ _B_u_t_t_o_n_s_ _a_n_d_ _P_l_u_g_s_ 4.1
4_._1_._1_ _ _ _ _ _F_r_o_n_t_ 4.1.1
OFF/ON:
(a red lamp will be alight)
BRIGHT. = picture brightness
CONT. = contrast
4_._1_._2_ _ _ _ _ _B_a_c_k_ 4.1.2
V. HOLD = Vertical Hold
H. HOLD = Horizontal Hold
Power connection plug:
insert the plug in the socket MO-
NITOR POWER on the back of the mi-
crocomputer (15 V direct current).
VIDEO IN:
is by means of the coaxial cable
connected to MONITOR VIDEO on the
back of the microcomputer. The
changeover switch is set at 75 Ohm.
VIDEO OUT:
Is used if you wish to connect an extra display unit (e.g. in
connection with a demonstration to a group of people). The cable
must be a coaxial cable with an impedance of 75 Ohm, and the
VIDEO IN on the extra machine must also be marked 75 Ohm. The
changeover switch at VIDEO OUT should now be switched to HIGH.
\f
4_._2_ _ _ _ _ _ _ _H_o_w_ _t_o_ _U_s_e_ _t_h_e_ _D_i_s_p_l_a_y_ _U_n_i_t_ 4.2
Turn on the unit and adjust the picture brightness and the con-
trast. A dimly luminous background gives the most pleasant dis-
play. Turn down the picture brightness or turn off the unit if it
is not to be used for a long period of time. As the text is al-
ways written in the same place, the internal coating of the pic-
ture tube may in the corse of time be impaired in these places.
4_._3_ _ _ _ _ _ _ _C_l_e_a_n_i_n_g_ 4.3
Wipe the picture tube with a soft cloth moistened with a solution
of a window cleaning preparation. Do not scratch the antireflec-
tion coating with a sharp instrument.
\f
F_ 5_._ _ _ _ _ _ _ _ _K_E_Y_B_O_A_R_D_ 5.
Besides the functions shown on the drawing, the following addi-
tional functions are available:
CTRL + E: (ESCAPE) = ESC
+ L: (CLEAR SCREEN) = CLEAR
+ M: (CARRIAGE RETURN) =
+ J: (NEW LINE/CURSOR DOWN) =
+ H: (CURSOR LEFT) =
+ X: (CURSOR RIGHT) =
+ Z: (CURSOR UP) =
CTRL-key is pressed while the other key (the key following +) is
activated.
CTRL + other characters and may have different meanings de-
pending on the software. You are asked to verify in the appropri-
ate user manuals.
If a key is pressed for more than 0.7 sec., the character is re-
peated with 0.1 sec. intervals until the key is released.
\f
F_ 6_._ _ _ _ _ _ _ _ _T_E_C_H_N_I_C_A_L_ _D_A_T_A_ 6.
6_._1_ _ _ _ _ _ _ _S_i_g_n_a_l_ _C_a_b_l_e_s_,_ _C_o_n_n_e_c_t_i_o_n_s_ 6.1
\f
6_._2_ _ _ _ _ _ _ _D_i_m_e_n_s_i_o_n_i_n_g_,_ _W_e_i_g_h_t_,_ _C_o_n_s_u_m_p_t_i_o_n_ 6.2
D_i_m_e_n_s_i_o_n_s_:
w h d weight
Microcomputer RC702: 460 140 290 (mm), 10.5 kg
Display Unit RC752: 360 300 330 (mm), 6.5 kg
Keyboard RC721: 380 50 235 (mm), 3.0 kg
Flexible Disc Drive RC762: 290 140 460 (mm), 13.5 kg
V_o_l_t_a_g_e_ _a_n_d_ _C_o_n_s_u_m_p_t_i_o_n_:
Microcomputer 100 W, 220 V + Earth, 50 Hz
Display Unit 21 W, 15 V DC
Flexible Disc Drive 80 W, 220 V + Earth, 50 Hz
E_n_v_i_r_o_n_m_e_n_t_a_l_:
All units Ambient temperature 10-30C
6_._3_ _ _ _ _ _ _ _M_i_c_r_o_c_o_m_p_u_t_e_r_ _S_p_e_c_i_f_i_c_a_t_i_o_n_s_ 6.3
Processor Z80A microprocessor, 8 bits, 4 MHz
Memory ROM: 2 KB
RAM: 48 KB (max. 64 KB)
Access time: 480 nanoseconds
Plugs Printer V.24 25 pin D-plug (1200 bps)
Terminal V.24 25 pin D-plug
Keyboard 25 pin D-plug
Parallel in/out 25 pin D-plug (8 bits paral-
lel in/out)
Display unit 75 Ohm BNC
\f
Flexible Disc Drive,
built-in (max. 2) 5 1/4" single density, dual sided, 128
bytes/sector, 0.12 MB, or
5 1/4" dual density, dual sided, 512
bytes/sector, 0.3 MB
Flexible Disc Drive,
detached (max. 2) 8" single density, single sided, 128
bytes/sector, 0.25 MB, or
8" dual density, dual sided, 512
bytes/sector, 0.9 MB
\f
F_ 7_._ _ _ _ _ _ _ _ _F_L_O_W_ _C_H_A_R_T_ 7.
L_i_s_t_ _o_f_ _A_b_b_r_e_v_i_a_t_i_o_n_s_:
CPU Central Processing Unit
REG Register
ROM Read Only Memory
Contr. Controller
I/O Input/Output
RAM Random Access Memory
K Kilo = 1024
B Byte
Char. Gen. Character Generator
DMA Direct Memory Access
Par. to Ser. Parallel to Serial
Conv. Converter
A(0:15) Address, bit 0 to 15
D(0:7) Data, bit 0 to 7
\f
V.24 Internationally adopted rules for signal transmission
over the telephone network. Also used for connection to
printers and the like.
S_i_g_n_a_l_s_ _V_._2_4_:
Pin 2 Transmitted Data
Pin 3 Received Data
Pin 4 Request To Send
Pin 5 Clear To Send
Pin 7 Signal Ground
Pin 8 Data Carrier Detected
Pin 20 Data Terminal Ready
\f
F_ 8_._ _ _ _ _ _ _ _ _P_A_R_A_L_L_E_L_ _I_N_/_O_U_T_ _P_L_U_G_S_ 8.
This is a parallel in/out plug that can transfer data to or from
a peripheral unit, under program control.
The following pin connections have been used:
J3 pin 22 IN/OUT 0
J3 - 23 IN/OUT 1
J3 - 24 IN/OUT 2
J3 - 21 IN/OUT 3
J3 - 17 IN/OUT 4
J3 - 18 IN/OUT 5
J3 - 19 IN/OUT 6
J3 - 20 IN/OUT 7
J3 - 12 REGISTER READY
J3 - 2 STROBE
J3 - 3 0 V
J3 - 13 0 V
J3 - 14 0 V
IN/OUT 0 is the least significant data bit, and IN/OUT 7 is the
most significant data bit. REGISTER READY is a signal from RC702
and STROBE is the peripheral unit's reply to REGISTER READY.
Electrical specifications of the output signals:
Logical 0: 0.0 V to 0.4 V. Load current max. 2.0 mA
Logical 1: 2.4 V to 5.0 V. Load current max. 250 A
The output signals can be used to supply current to transistors
in a Darlington coupler, and can supply a base current of at
least 1.5 mA with an output voltage of 1.5 V.
\f
F_ i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. CALL ................................................... 2
3. FUNCTION ............................................... 3
4. EXAMPLES ............................................... 4
5. ERROR MESSAGES ......................................... 5
\f
F_ ii
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
The program a diagnostic tool for printing statistical informa-
tion and testoutput from an FPA-process (RC8000) or an SCC-pro-
cess (RC4000).
The program may as well print directly from the core as from a
file containing a core picture. When printing directly from core
the generation of testoutput is disabled for a moment.
\f
F_ 2_._ _ _ _ _ _ _ _ _C_A_L_L_ 2.
fpastat <proc spec><function>
<proc spec>::= core8000.<name(fpa-mainproc)>
core4000.<name(scc-mainproc)>
dump8000.<dump file>.<proc desc addr(fpa-mainproc)>
dump4000.<dump file>.<proc desc addr(scc-mainproc)>
<function>::= <empty>
test.yes
test.no
The <proc spec> field is used to define the type of the computer
(RC8000/RC4000) and where the statistical information shall be
printed from (core or a core dump).
The <function> field is used to specify whether the test records
shall be printed, - the default value is 'test.no'.
\f
F_ 3_._ _ _ _ _ _ _ _ _F_U_N_C_T_I_O_N_ 3.
The program finds the receiver and transmitter processes associ-
ated with the main process specified.
The program extracts and prints on current output the statistics,
first from the receiver process, then from the transmitter pro-
cess description.
If a dump file is specified, it is supposed to contain a core
picture with core address 0 equivalent to area address 0.
If the function field specifies output of the testrecords, the
generation of testoutput to the testbuffer is disabled while the
test mask and the testbuffer are inspected and enabled again with
the same testmask (in case of testrecords from the core), even in
case of abnormal program termination.
The testrecords of the buffer are printed in FIFO order as indi-
cated by the buffer pointers.
The program moves <no of segm> segments from the disc or until
end of document, starting with segment number <first segm>.
Default values are
<first segm> : 840
<no of segm> : 168
corresponding to the normal locations of the system dump area on
the autoload disc.
\f
F_ 4_._ _ _ _ _ _ _ _ _E_X_A_M_P_L_E_S_ 4.
The following command extracts the statistics from the FPA main
process named 'main 36001':
fpastat core8000.main36001
The following command extracts the statistics and the testbuffer
from the FPA main process with the address 20786 in the coredump
contained in the file 'coredump':
fpastat dump8000.coredump. 20786 test.yes
\f
F_ 5_._ _ _ _ _ _ _ _ _E_R_R_O_R_ _M_E_S_S_A_G_E_S_ 5.
***fpastat, error in call
the call is not syntactically correct
***fpastat, no testbuffer
the main process specified has no testbuffer
***fpastat, mainprocess unknown
the FPA or SCC main process specified does not exist
***fpastat, main process not found
- the kind of the main process specified and found is not
correct (80).
- the coredump area could not be found or the address points
outside the coredump area.
- the address of the mainproc specified was not found in the
name table in the coredump.
\f
F_
\f
F_ i
T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_
1. INTRODUCTION ........................................... 1
2. CALL ................................................... 2
3. FUNCTION ............................................... 3
4. EXAMPLES ............................................... 4
5. ERROR MESSAGES ......................................... 5
\f
F_ ii
\f
1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.
The program moves the coredump caused by autoload action from the
system dump area on the autoload disc to a backing storage file.
\f
F_ 2_._ _ _ _ _ _ _ _ _C_A_L_L_ 2.
<outfile> = movedump,
M_m_m_ 1 1
(device.<device spec>) (first.<first segm>)
P_p_p_ 0 0
M_m_m_ 1
(segm.<no of segm>)
P_p_p_ 0
<device spec>::= <device name><device no>
<device name>::= name
<device no> ::=
<first segm> ::=
<no of segm> ::= number
\f
F_ 3_._ _ _ _ _ _ _ _ _F_U_N_C_T_I_O_N_ 3.
The program moves the coredump caused by autoload action from the
system dump area on the autoload disc to the backing storage file
<outfile>.
If <outfile> does not exist, movedump will create a temporary
entry with that name.
If a device is specified, and if the device number exists or a
peripheral process with the given name exists, it is supposed to
be the autoload disc.
If a device is not specified, the program tries to find the auto-
load disc itself.
The autload disc is, as far as the program is concerned, defined
to be a logical disc whose first segment on the physical disc has
number zero and whose physical disc has device number 4.
If the autload disc is placed on an RC8233 Fixed Media Disc, this
definition does not fit, and the program will fail to find it.
If the program cannot find the autoload disc itself, it gives up
with a message that the device should be specified.
If device is not specified by name, the process executing the
program must be allowed to perform the monitor procedure 'create
peripheral process' (function mask bit No 4).
The program moves <no of segm> segments from the disc or until
end of document, starting with segment number <first segm>.
Default values are
<first segm> : 840
<no of segm> : 168
corresponding to the normal location of the system dump area on
the autoload disc.
\f
F_ 4_._ _ _ _ _ _ _ _ _E_X_A_M_P_L_E_S_ 4.
The call
coredump = movedump
will move 168 segments starting in segment number 840 on the
autoload disc, i.e. the system dump area of the autload disc, to
the file 'coredump'.
The call
dumpfile = movedump device.autodisc1
will move 168 segments starting in segment number 840 on the disc
named 'autodisc1' to the file 'dumpfile'. If the disc named
'autodisc1' is the logical disc on an RC8233 Fixed Media Disc
containing the RC8000 Monitor and Front End systems, the segments
moved will be the system dump area.
\f
F_ 5_._ _ _ _ _ _ _ _ _E_R_R_O_R_ _M_E_S_S_A_G_E_S_ 5.
***movedump call
no left hand side in the call
***movedump syntax, param no <no>
parameter no <no> violates the syntax of the call
***movedump unknown, param no <no>
parameter no <no> is unknown
***movedump create entry outfile, result <n>
the outfile entry did not exist and could not be created
***movedump create peripheral process, result <k>
a peripheral process associated with the given device number
or with the autoload disc found could not be created
***movedump peripheral process does not exist
a peripheral process by the specified name could not be found
***movedump please specify autoload device
autoload disc was not specified and the program was not able
to find it.
\f
F_
\f
«eof»