⟦41a813f7a⟧

TextFile

T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_

1. INTRODUCTION ........................................... 1

2. SOURCE TEXT ORGANISATION ............................... 2
2.1 The ROUTER Module ................................. 2
2.2 Mode Identification Process ....................... 2

3. CONFIGURATION AND COMPILATION OF RC-NET, ROUTERS ....... 4
3.1 Recognition of the ROUTER Types ................... 4
3.2 Creation of each ROUTER Type ...................... 5
3.3 Compilations and Linking .......................... 5
3.4 Maintenance ....................................... 6

4. PARAMETERS OF OPTIC, CODE OPTIONS ...................... 7
4.1 Version ........................................... 7
4.2 Region Routing Parameters ......................... 7
4.3 Node Routing Parameters ........................... 7
4.4 Host Routing Parameters ........................... 8
4.5 Network Time Parameters ........................... 8
4.6 Other Supervisor Parameters ....................... 8
4.7 HDLC Interface Parameters ......................... 8
4.8 Host Process Interface Parameters ................. 9
4.9 Packet Transporter Parameters ..................... 9
4.10 Various Parameters ................................ 9

5. PARAMETERS OF OPTIV, DIMENSIONING ...................... 10
5.1 Node Routing Parameters ........................... 10
5.2 Region Routing Parameters ......................... 10
5.3 Other Supervisor Module Parameters ................ 10
5.4 HDLC Interface Parameters ......................... 11
5.5 Driver Information ................................ 12
5.6 Host Process Interface Parameters ................. 13
5.7 Packet Transporter Inclusion ...................... 13
5.8 Various Parameters ................................ 14
5.9 Testmasks ......................................... 14
\f

T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _(_c_o_n_t_i_n_u_e_d_)_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_

A_P_P_E_N_D_I_X_:

A. REFERENCES ............................................. 15

B. EXEC JOB EXAMPLE ....................................... 16

F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_ 1.

This manual is a configuration guide, describing how RC-NET,
ROUTER modules may be configurated for installation in the RC3600
nodes of a network interconnecting RC8000 computers.

The main purpose of the manual is to describe the configuration
of a version of the RC-NET, ROUTER, which is as close as possible
to a standard version of the ROUTER, intended for installation in
the nodes of a network interconnecting RC8000 computers.

The manual is n_e_i_t_h_e_r_ a general RC-NET, ROUTER configuration
guide, n_o_r_ a description of the f_u_n_c_t_i_o_n_a_l_ _b_e_h_a_v_i_o_r_ of the "stan-
dard" ROUTER version defined in the manual.

Furthermore, the manual does not concern configuration and in-
stallation of line driver processes. The ROUTER process ident-
ifies the line driver processes according to the driver informa-
tion described in chapter 5. The ROUTER process operates on a
line driver interface as that of the HLC-driver, cf. ref. 3.

F_ 2_._ _ _ _ _ _ _ _ _S_O_U_R_C_E_ _T_E_X_T_ _O_R_G_A_N_I_S_A_T_I_O_N_ 2.

2_._1_ _ _ _ _ _ _ _T_h_e_ _R_O_U_T_E_R_ _M_o_d_u_l_e_

The RC-NET, ROUTER module consists of 9 source texts.

6 of these source texts are compiled into binary code files,
which are linked together to form the complete ROUTER module.

Two of the remaining three source texts contain configuration in-
formation used in the compilation, and the last source text holds
type definitions common to all ROUTER source texts. This source
text is also used in the compilation.

The 9 source texts are:

SFORM ROUTER type definitions,
SHPI
SPTRP
M_m_m_ SSUPV
Router source code,
P_p_p_ SHDLC
SPROC
SROUT
M_m_m_ OPTIC
ROUTER configuration texts.
P_p_p_ OPTIV

2_._2_ _ _ _ _ _ _ _N_o_d_e_ _I_d_e_n_t_i_f_i_c_a_t_i_o_n_ _P_r_o_c_e_s_s_ 2.2

A version of the process ONODE must be loaded into each network
node. The purpose of ONODE is to identify the node.

When loaded into an RC3600, the ROUTER searches, as its first ac-
tion, for the 'ONODE'-process, and when ONODE is found the node
number is read from the process description of ONODE (AC1 save).

The source of the ONODE process is

SNODE ONODE source test.
\f

Binary versions of SNODE are named:

ONOD1 ONODE of node 1
ONOD2 ONODE of node 2
M_ . (etc.)
.
P_ .

F_ 3_._ _ _ _ _ _ _ _ _C_O_N_F_I_G_U_R_A_T_I_O_N_ _A_N_D_ _C_O_M_P_I_L_A_T_I_O_N_ _O_F_ _R_C_-_N_E_T_,_ _R_O_U_T_E_R_S_ 3.

The generation of ROUTER processes for a specific network implies
the following:

1) Recognition of the required types of ROUTER processes.

2) Creation of the configuration texts for each ROUTER type.

3) Compilations and linking.

Adjusting parameters of existing ROUTER processes, implies

1) Adjusting the configuration texts.

2) Compilations and linking.

3_._1_ _ _ _ _ _ _ _R_e_c_o_g_n_i_t_i_o_n_ _o_f_ _t_h_e_ _R_O_U_T_E_R_ _T_y_p_e_s_ 3.1

It is recommended that each network is identified by a 2-charac-
ter mnemotechnic code. In this document EX will be used.

A network requires different ROUTER processes for d_i_f_f_e_r_e_n_t_ _t_y_p_e_s_
of nodes. A ROUTER process may be installed at all nodes, where
the number of lines and the line driver identification are alike,
unless traffic characteristics or other characteristics make it
questionable (cf. chapters 4 and 5). Each ROUTER type is ident-
ified by a single digit, e.g. the number of lines.

As an example, a network interconnecting 5 RC8000's through 5
nodes, may require two ROUTER types, one for two-line nodes and
one for three-line nodes. These two ROUTERs should be identified
ROEX2 and ROEX3.

Figure 1: ROUTER installations.
\f

3_._2_ _ _ _ _ _ _ _C_r_e_a_t_i_o_n_ _o_f_ _e_a_c_h_ _R_O_U_T_E_R_ _T_y_p_e_ 3.2

For each ROUTER type, a special version of the configuration
texts OPTIC and OPTIV must be edited, following the guidelines in
chapters 4 and 5.

This produces, for each ROUTER type, two texts that should be
named OC- and OV-, suffixed by the ROUTER type identification.

In the above example, the following configuration texts would be
produced:

OPTIC edited into OCEX2 and OCEX3
OPTIV edited into OVEX2 and OVEX3

3_._3_ _ _ _ _ _ _ _C_o_m_p_i_l_a_t_i_o_n_s_ _a_n_d_ _L_i_n_k_i_n_g_ 3.3

After the special versions of the configuration texts are edited,
a compile-and-link job must be created.

This job, which is executed by the EXEC process, should be named
according to the network identification suffix, e.g.

JBEX job file, network EX

The job should compile and link all ROUTER types for the network
EX.

The compile-and-link job must execute the following compilations
and linking for each ROUTER type:

DOMAC BIN.RHPI SFORM/S OPTIC/S SHPI
DOMAC BIN.RPTRP SFORM/S OPTIC/S SPTRP
DOMAC BIN.RSUPV SFORM/S OPTIC/S SSUPV
DOMAC BIN.RHDLC SFORM/S OPTIC/S SHDLC
DOMAC BIN.RPROC SFORM/S OPTIC/S SPROC
DOMAC BIN.RROUT SFORM/S OPTIC/S OPTIV SROUT
LINK CHECK.NO ENTRY.400 FORM.R!
! IN.RHPI RPTRP RSUPV RHDLC RPROC RROUT
\f

The job of the example above, for the network EX, is shown in ap-
pendix B.

The job will create the required binary ROUTER processes and save
the link-logs by the linkage editor.

3_._4_ _ _ _ _ _ _ _M_a_i_n_t_e_n_a_n_c_e_ 3.4

All files related to a specific network may be saved on a magnet-
ic tape, utilizing the FCOPY utility in this way:

FCOPY DUMP SSEXS

where the network identification is stated at 'EX'.

Adjusting parameters of ROUTERS of an existing network may be
done in a simple way, by re-editing the OC-resp. OV-files and re-
executing the job.

F_ 4_._ _ _ _ _ _ _ _ _P_A_R_A_M_E_T_E_R_S_ _O_F_ _O_P_T_I_C_,_ _C_O_D_E_ _O_P_T_I_O_N_S_ 4.

This chapter describes the initializations of the source text
OPTIC.

The main part of OPTIC concerns optional code parts, i.e. op-
tional facilities, of the RC-NET, ROUTER module.

4_._1_ _ _ _ _ _ _ _V_e_r_s_i_o_n_ 4.1

The configuration date and the name identifying the ROUTER must
be stated at page 2A of OPTIC.

The line following

.MACRO TXTPROG

must hold the date and the ROUTER identification in this format:

.TXT '821024 <32> ROEX2' ;

where ROEX2 is the name of the specific ROUTER module (cf. chap-
ter 3).

4_._2_ _ _ _ _ _ _ _R_e_g_i_o_n_ _R_o_u_t_i_n_g_ _P_a_r_a_m_e_t_e_r_s_ 4.2

IREGION = 0
SNGLREG = 0

4_._3_ _ _ _ _ _ _ _N_o_d_e_ _R_o_u_t_i_n_g_ _P_a_r_a_m_e_t_e_r_s_ 4.3

INODE = 1
IHDLC = 1
FNODE = 0
IPHLC = 1

4_._4_ _ _ _ _ _ _ _H_o_s_t_ _R_o_u_t_i_n_g_ _P_a_r_a_m_e_t_e_r_s_ 4.4

EXHOST = 1
MDHOST = 0

4_._5_ _ _ _ _ _ _ _N_e_t_w_o_r_k_ _T_i_m_e_ _P_a_r_a_m_e_t_e_r_s_ 4.5

NTIME = 1

4_._6_ _ _ _ _ _ _ _O_t_h_e_r_ _S_u_p_e_r_v_i_s_o_r_ _P_a_r_a_m_e_t_e_r_s_ 4.6

STSUP = 1
RROUT = 1
RHCFL = 1
RPNEI = 1
RTEST = 1

4_._7_ _ _ _ _ _ _ _H_D_L_C_ _I_n_t_e_r_f_a_c_e_ _P_a_r_a_m_e_t_e_r_s_ 4.7

CHDLC = 0
STHDLC = 1
RHDLC = 1
RDHDLC = 0
RCHLC = 1
DRHLC = 0
LRETC = 4
LRETT = 3

The value of LRETT defines the number of seconds between retrans-
missions on a line.

If all lines of a node operate at a speed of 9.6 Kbps (or more),
a value of 2 seconds may be chosen alternatively.

4_._8_ _ _ _ _ _ _ _H_o_s_t_ _P_r_o_c_e_s_s_ _I_n_t_e_r_f_a_c_e_ _P_a_r_a_m_e_t_e_r_s_ 4.8

ICOMMAND = 0
RHUP = 1
RPRID = 1
RHDISC = 1
STHPI = 1
IEXPROC = 1

4_._9_ _ _ _ _ _ _ _P_a_c_k_e_t_ _T_r_a_n_s_p_o_r_t_e_r_ _P_a_r_a_m_e_t_e_r_s_ 4.9

IPTRP = 1
STPTRP = 1
IIMDA = 0
IWSAVE = 1

4_._1_0_ _ _ _ _ _ _V_a_r_i_o_u_s_ _P_a_r_a_m_e_t_e_r_s_ 4.10

STEST = 0
DTEST = 1
IXREL = 1
XRBDATA = 1
XRCODE = 1

F_ 5_._ _ _ _ _ _ _ _ _P_A_R_A_M_E_T_E_R_S_ _O_F_ _O_P_T_I_V_,_ _D_I_M_E_N_S_I_O_N_I_N_G_ 5.

This chapter describes the initializations of the source text
OPTIV.

OPTIV concerns dimensionings of the network and of the individual
node.

I_m_p_o_r_t_a_n_t_!_ All ROUTER modules of a network must be compiled with
the same value of a parameter, if the NW indication is
stated.

5_._1_ _ _ _ _ _ _ _N_o_d_e_ _R_o_u_t_i_n_g_ _P_a_r_a_m_e_t_e_r_s_ 5.1

NNODE = see below (NW!)
NODE = 0

The value of NNODE states the m_a_x_i_m_u_m_ number of nodes constitut-
ing the network. Each RC3600 containing a ROUTER process is a
network node.

It is recommended that the value of NNODE is large enough to meet
small (future) network extension, i.e. in a network with 5-6
nodes, NNODE may e.g. be set to 8. (An increment of one (of
NNODE) costs less than 100 bytes of core in the node).

5_._2_ _ _ _ _ _ _ _R_e_g_i_o_n_ _R_o_u_t_i_n_g_ _P_a_r_a_m_e_t_e_r_s_ 5.2

NREGION = 0
CUREG = 0

5_._3_ _ _ _ _ _ _ _O_t_h_e_r_ _S_u_p_e_r_v_i_s_o_r_ _M_o_d_u_l_e_ _P_a_r_a_m_e_t_e_r_s_ 5.3

NEXHOST = see below (NW!)
NBRCP = 2
EXHTIM = 4000
NSTIME = 4000
\f

The value of NEXHOST should be the number of network nodes times
2 + 3, i.e.

NEXHOST = (NNODE * 2) + 3

5_._4_ _ _ _ _ _ _ _H_D_L_C_ _I_n_t_e_r_f_a_c_e_ _P_a_r_a_m_e_t_e_r_s_ 5.4

NHDLC = see below
NINPUT = see below
INMAX = 2
ASTART = 1

NHDLC states the number of network lines, i.e. lines to other
nodes, from the node.

I_m_p_o_r_t_a_n_t_!_ The value NHDLC = 1 must n_o_t_ be used. A network node
with one network line has to be configurated as if two
lines exist. In this case the second line may be a
dummy line or a back-up line using an alternative
channel, cf. 5.5.

The value of NINPUT defines the number of internal packet buffers
in the ROUTER module. These buffers are used for packet receipt
(from lines) and for transit packet transmission on lines.

A good choice of a value for NINPUT is

NINPUT = (NHDLC * 2) + 1

Each increment of NINPUT costs the core requirements of a packet
buffer, which is about 350 bytes.

A heavily loaded network node, carrying a lot of transit traffic
caused by the communication between other nodes, may operate
better with a larger value than stated above, especially if line
speeds are different.

Thus, the value of NINPUT may be subject to changes during a
trimming phase.

5_._5_ _ _ _ _ _ _ _D_r_i_v_e_r_ _I_n_f_o_r_m_a_t_i_o_n_ 5.5

By stating a proper text and channel identifications, the line
drivers are identified to the ROUTER. Follow the guidelines of
the source text OPTIV.

For a node with one network line the following possibilities are
relevant:

1) .TXT 'HLC <0> <0>' (name)
1 (no. of streams)
2 (stream)

.TXT 'DUMMY'
1
2

The line to be used is stream 2 of driver HLC, and the extra
line (cf. 5.4) is a dummy line.

2) .TXT 'HLC <0> <0>' (name)
2 (no. of streams)
2 (1st stream)
4 (2nd stream)

The line to be used is stream 2 or 4 of driver HLC, and the
other stream is a back-up line, ready for use.

If this driver information is used, the ROUTER may be instal-
led in nodes with two lines at operation too.

A node with 3 lines, channel 1, 2 and 3 of an HDLC-device, will
have this driver information:

.TXT 'HLC <0> <0>' (name)
3 (no. of streams)
2 (stream 2 (ch. 1))
4 (stream 4 (ch. 2))
6 (stream 6 (ch. 3))
\f

If more than one line driver process are present, all driver
names are stated, and for each driver, the streams in question.

5_._6_ _ _ _ _ _ _ _H_o_s_t_ _P_r_o_c_e_s_s_ _I_n_t_e_r_f_a_c_e_ _P_a_r_a_m_e_t_e_r_s_ 5.6

NHPROC = 7
NLHOST = 11
NPOUT = 14
NDHOST = 0
IEXPROC = 1
TMAX = 1500
ITMAX = 150
HPITIM = 40

5_._7_ _ _ _ _ _ _ _P_a_c_k_e_t_ _T_r_a_n_s_p_o_r_t_e_r_ _I_n_c_l_u_s_i_o_n_ 5.7

NPIPELIN = see below
NPPACK = see below
MXRCH = 4
TRNACOU = 1
TRHATIM = 100
TRHRNR = 4
STFREQ = 230
TRHLAST = 1100
RTINTV = 1000
MXTLAST = 1500
MXARNR = 8
MXRTC = 2
MINDISC = 200
PTTIMER = 20

The value of NPIPELIN states the number of 'logical connections'
from this node to other nodes in the network. A good choice is
the number of RC8000's interconnected via the network. The costs
of each 'connection' is less than 200 bytes so NPIPELIN should be\f

chosen large enough, e.g.:

NPIPELIN = (no. of RC8000's) + 2
and NPPACK = NPIPELIN

5_._8_ _ _ _ _ _ _ _V_a_r_i_o_u_s_ _P_a_r_a_m_e_t_e_r_s_ 5.8

MAXPSIZE = PHLEN * 2 + 274
IDUMP = 0
HLOC = 0
ISTART = 1

5_._9_ _ _ _ _ _ _ _T_e_s_t_m_a_s_k_s_ 5.9

TM001 = 0
TM002 = 8
TM003 = 8
TM004 = 0
TM040 = 8
TM041 = 8
TM042 = 8
TM010 = 0
TM011 = 0
TM012 = 0
TMLIN = 8

F_ A_._ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_ A.

1 RCSL No 43-GL6311:
Introduction to RC-NET, Level 1

2 RCSL No 43-GL7040:
Internal Structure of ROUTER

3 RCSL No 43-GL9533:
HDLC Driver, Description

F_ B_._ _ _ _ _ _ _ _ _E_X_E_C_ _J_O_B_ _E_X_A_M_P_L_E_ B.

JOB
LINE
M_ 1 DELET RHPI
2 DELET RPTRP
3 DELET RSUPV
4 DELET RHDLC
5 DELET RPROC
6 DELET RROUT
7 DELET ROE_X_2_
8 DELET LLE_X_2_
9 DOMAC BIN.RHPI SFORM/S OCE_X_2_/S SHPI
10 DOMAC BIN.RPTRP SFORM/S OCE_X_2_/S SPTRP
11 DOMAC BIN.RSUPV SFORM/S OCEE_X_2_/S SSUPV
12 DOMAC BIN.RHDLC SFORM/S OCE_C_2_/S SHDLC
13 DOMAC BIN.RPROC SFORM/S OCE_X_2_/S SPROC
14 DOMAC BIN.RROUT SFORM/S OCE_X_2_/S OVEX2 SROUT
15 LINK OUT.ROE_X_2_ CHECK.NO LOG.LLE_X_2_ TITLE.ROE_X_2_!
16 ! ENTRY.400 FORM.R IN.RHPI RRTRP RSUPV RHDLC RPROC RROUT

(REPEAT LINES 1 TO 16 WITH EX2 REPLACED BY EX3 IN LINE 17 TO 32)

P_ 33 FINISH

This job file will, when executed by EXEC, produce the binary
ROUTER modules

ROEX2 and ROEX3

and save the linkage editor log-files in

LLEX2 and LLEX3

(Old versions are deleted).

Underlined texts indicate the parts of the job text that are
replaced from project to project.

F_ i

P_R_E_F_A_C_E_

The intention of this manual is to help you in using the RC8000
testsystem parallel to customer software.

A more detailed description of how to run the individual testpro-
grams are to be found in the respective manuals.

The design of the system is based on the ideas of Flemming Kam
and the author.

Finn Grønning
A/S Regnecentralen af 1979, October 1980

F_ ii

iii

T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_

1. REVISION STATUS ....................................... 1

2. APPLICABLE DOCUMENTS .................................. 2

3. FAULT-FINDING ON RC8000 ............................... 3

4. REQUIREMENTS OF THE INSTALLATION ...................... 4

5. HOW TO LOAD THE TESTPROGRAMS .......................... 5
5.1 Loading from Magnetic Tape ....................... 5
5.1.1 Example ................................... 5
5.2 Loading from Flexible Disc ....................... 6
5.2.1 Example ................................... 6

6. HOW TO USE "TOP" ...................................... 7
6.1 Creating an "s"-Process .......................... 7
6.1.1 Example ................................... 7
6.2 Commands to "TOP" ................................ 8
6.3 The Schedule Facility ............................ 9
6.3.1 Example ................................... 10
6.4 Removal of "TOP" ................................. 10
6.4.1 Example ................................... 10

7. MORE JOBS ON THE SAME TERMINAL ........................ 12

8. OTHER PROGRAMS OF INTEREST ............................ 13

9. THE TESTPROGRAMS ...................................... 14
9.1 Memory Test, Example ............................. 14
9.2 CPU-Test ......................................... 15
9.2.1 Example ................................... 16
9.3 DISC Test ........................................ 17
9.3.1 Example ................................... 17
9.3.2 Example ................................... 18
9.3.3 C-test .................................... 19 \f

T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _(_c_o_n_t_i_n_u_e_d_)_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_

9.4 FPA Test ......................................... 22
9.4.1 Example ................................... 23

A_P_P_E_N_D_I_C_E_S_:

A. FORMAT OF "TOP>s" FIRST SEGMENT ....................... 25

B. IMPORTANT NOTES ....................................... 27
\f

F_ 1_._ _ _ _ _ _ _ _ _R_E_V_I_S_I_O_N_ _S_T_A_T_U_S_ 1.

0.00 First edition: RCSL No 30-M 262.
In this edition it is not possible to use a bs area on disc
as selected output medium. The wait command is not implemen-
ted.

F_2_._ _ _ _ _ _ _ _ _A_P_P_L_I_C_A_B_L_E_ _D_O_C_U_M_E_N_T_S_ 2.

RCSL No 30-M 57: RC8400 FPA Test
RCSL No 30-M 58: RC8005 CPU Test
RCSL No 30-M 179: PLU801, User>s Manual
RCSL No 30-M 198: RC8100 Memory Test
RCSL No 30-M 216: RC8000 Testprogram System, User>s Manual
RCSL No 30-M 241: RC8200 Disc Test
RCSL No 30-M 259: RC8000, Magnetic Tape Test
RCSL No 30-M 262: RC8000 Testprogram System, Binary, MT 1600 BPI
RCSL No 30-M 264: RC8000 Testprogram System, Binary, Flex. disc
RCSL No 30-M 266: RC8000 Testprogram System, Binary, MT 800 BPI
RCSL No 31-D 494: Print, System 3 Utility Programs
RCSL No 31-D 522: FPASTAT, DISCSTAT
RCSL No 31-D 595: Operating System "s"
RCSL No 31-D 598: Montest

F_ 3_._ _ _ _ _ _ _ _ _F_A_U_L_T_-_F_I_N_D_I_N_G_ _O_N_ _R_C_8_0_0_0_ 3.

In order to run the testprograms under the supervision of "TOP",
the machine must be rather clever. Most hardware errors prevent
even the monitor to get running. In this case "TOP" is of no use,
and other means must be applied.

Regarding testprograms the following tools are available:

1) RCSL No 30-M 179: PLU801 (P_rogram L_oad U_nit).
To be used, if not even the "stand alone"
testsystem can be loaded.

2) RCSL No 30-M 216: RC8000 "stand alone" testsystem.
To be used, if the monitor cannot be loaded.
Only on installations with RC3600 as front-
end.

F_ 4_._ _ _ _ _ _ _ _ _R_E_Q_U_I_R_E_M_E_N_T_S_ _O_F_ _T_H_E_ _I_N_S_T_A_L_L_A_T_I_O_N_ 4.

Although the testsystem is able to run parallel to customer soft-
ware, it may be of some inconvenience to the customer. The need
for resources must be shared.

First of all, the memory of the machine must be large enough to
create an "s"-process of a size not less than 60,000 halfwords.
The monitor revision must not be older than 6.0. It is, however,
possible to run a part of the testsystem (memory- and cpu test)
on older revisions.

F_ 5_._ _ _ _ _ _ _ _ _H_O_W_ _T_O_ _L_O_A_D_ _T_H_E_ _T_E_S_T_P_R_O_G_R_A_M_S_ 5.

The testprogram system is composed of a number of binary files.
You may check the existence of the testsystem by performing the
following commands.

ATT s
NEW FIG RUN
LOOKUP BTOP BMEM BCPU BDISC BFPA

5_._1_ _ _ _ _ _ _ _L_o_a_d_i_n_g_ _f_r_o_m_ _M_a_g_n_e_t_i_c_ _T_a_p_e_ 5.1

The tape consists of the following:

fileno: contents:
0-45 "stand alone" testsystem
46 PLU801 Mirror program for RC8000
47 RC8000 testsystem
48 RC8000 magnetic tape test.
49 MONTEST

The testsystem is placed on file 47 by help of the utility
program "save". It must be loaded by the utility program "load".
This may be done either as a BOSS job or in an "s"-process.

5_._1_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 5.1.1

ATT s
NEW FIG BASE -8388607 8388605 RUN
LOAD MT801001.47

In this example the testsystem will be loaded with system scope.

5_._2_ _ _ _ _ _ _ _L_o_a_d_i_n_g_ _f_r_o_m_ _F_l_e_x_i_b_l_e_ _D_i_s_c_ 5.2

The disc consists of the following:

file no: contents:
1 RC8000 testsystem (TOP version only)
2 RC8000 magnetic tape test
3 Montest

5_._2_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 5.2.1

ATT s
NEW FIG BASE -8388607 8388605 RUN
FDLOAD TOP.1 OWNER.TOP

ATT s
CALL 6 FD0TOP start

F_ 6_._ _ _ _ _ _ _ _ _H_O_W_ _T_O_ _U_S_E_ _"_T_O_P_"_ 6.

"TOP" is an operating system, which must run as an "s"-process.
It is able to handle only one testprogram.

It is, however, possible to create as many versions of "TOP"
(with different names) as the resources at the installation
allows.

6_._1_ _ _ _ _ _ _ _C_r_e_a_t_i_n_g_ _a_n_ _"_s_"_-_P_r_o_c_e_s_s_ 6.1

There is a number of resources which are absolutely necessary in
order to get started.

6_._1_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 6.1.1

ATT s
NEW TOP SIZE 60000 BUF 12 INTERNAL 1 PRIO 2 MODE 0 PROG BTOP RUN

Description of resources:
size: '_60000 ; a larger size may be necessary, e.g. if a larger
blocksize in the disc-test is wanted.
buf: '_ 12; a minimum of 12 must be available.
internal: 1; in order to be able to create the testprocess.
PRIO: 0-4095; the highest priority is 0.
; "TOP" itself will be given priority 0, but if it
; is desirable not to slow down the customer
; software too much a priority ' 1 may be selected.
; This will be the priority of the testprogram.
mode: 0; mode 0 is necessary.
PROG: BTOP; BTOP is the name of the file holding the binary
; version of "TOP".

6_._2_ _ _ _ _ _ _ _C_o_m_m_a_n_d_s_ _t_o_ _"_T_O_P_"_ 6.2

When "TOP" is created, it will execute a close command, in order
to define the output device.

C_l_o_s_e_:
The text "select output device =" is printed. The output from the
testprograms are of two types. Operator messages are always sent
to the console or terminal, where "TOP" is created; test
messages, however, are sent to the chosen device:

TTY ; operator console
LPT ; line printer
LPT1 ; second line printer
MT:<name' ; magnetic tape
DISC:<name' ; bs area on disc.

In general "TOP" is always ready to accept commands after having
written the text "select function:". After a start command has
been made it is, however, necessary to use an "attention".

a_t_t_ _<_n_a_m_e_'_:
The <name' is the process name of "TOP", which you are free to
choose, at that time "TOP" is created.

N_e_w_:
A new testprocess is created, but not started. The testprocess
will be given a name (e.g. DISCT0, DISCT1 ... DISCT9). You may
use the commands working on the parameters of the test.

L_i_s_t_:
The list command will cause the parameters to be listed, with
number, name, and the last value assigned.

P_a_r_a_m_:
The param command will force you to assign every parameter.
\f

P_O_<_x_y_'_:
If only a single or a few parameters are to be changed, the
PO<xy' command is used.

S_T_A_R_T_:
The start command will transfer the parameters to the
testprogram and start the test.

B_r_e_a_k_:
The break command will force the test process to stop and the
text "***test terminated" will be printed.

M_I_R_R_O_R_<_n_u_m_b_e_r_'_:
The mirror command is only used for the FPA test. This is the way
you select which FPA line to be tested. There may be several
mirror-programs on an installation. Every front-end,
concentrator, or another RC8000 may have a mirror-program.

Example:
MIRROR36001 ; default, normally first front-end.
MIRROR36002 ; concentrator or second front-end.
MIRROR35001 ; mirror program on RC3500.
MIRROR80001 ; mirror program on another RC8000.

The mirror command must be executed before the "new" command.
Actually, the mirror command prepare the new command to look up a
link with the given name.

Note: The names Mirror36001, Mirror36002 do not have relation to
the external processes MAIN36001, MAIN36002.

6_._3_ _ _ _ _ _ _ _T_h_e_ _S_c_h_e_d_u_l_e_ _F_a_c_i_l_i_t_y_ 6.3

In the schedule files you have the possibility of storing a
complete command string to "TOP". After having generated such a
string you may, by use of "TOP" command SDUL<no', cause an\f

execution of the commands in the schedule string. If you are not
going to write or make a clean track on a disc, the commands are
executed without further operator involvement.

The schedule file is easily generated by the Editor.

6_._3_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 6.3.1

ATT s
NEW FIG RUN
SDUL0=EDIT
I>
NEW/DISC P001/1 P002/5 P003/23 START FINIS
>
FINIS
SCOPE USER SDUL0

The finis command must always terminate a schedule string.

Legal names are SDUL0 ... SDUL9.

6_._4_ _ _ _ _ _ _ _R_e_m_o_v_a_l_ _o_f_ _"_T_O_P_"_ 6.4

***IMPORTANT***

If you are running a disc test, it m_u_s_t_ be terminated before the
remove of "TOP". The test may be terminated by itself, but if it
is running you m_u_s_t_ break it.

6_._4_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 6.4.1

ATT TOP
"SELECT FUNCTION:" BREAK
***TEST TERMINATED

This is because the disc test is borrowing the disc from the disc-\f

driver, and the system will look itself if the disc is not
released. In this case you have to autoload again!

It is always a good practice to terminate the testprogram before
removing "TOP".

The same danger of system lock will be present if "TOP" is
stopped. Do not ever stop or remove a "TOP" process while a
testprogram is running.

Both "TOP" and the testprocess are removed by performing the "s"
command:

ATT s
REMOVE

F_ 7_._ _ _ _ _ _ _ _ _M_O_R_E_ _J_O_B_S_ _O_N_ _T_H_E_ _S_A_M_E_ _T_E_R_M_I_N_A_L_ 7.

It is indeed possible to run more jobs from the same terminal;
but there are certain things to be aware of.

The "s" command REMOVE and RUN are working on a consolebuffer
describing the last job created. If you want to "REMOVE RUN" a
job, which is not the last one created, you have to do it in two
steps.

1) Proc <processname' REMOVE
2) New <processname' ..... RUN

If you have chosen the same terminal as output device for more
than one testprocess, you may be confused by the mixed output.
You can always stop and start a process by the "s" commands:

att s
proc <processname' stop
proc <processname' start

F_ 8_._ _ _ _ _ _ _ _ _O_T_H_E_R_ _P_R_O_G_R_A_M_S_ _O_F_ _I_N_T_E_R_E_S_T_ 8.

There is a number of programs which may be of great help:

1) RCSL No 31-D 494: Print
2) RCSL No 31-D 578: Montest
3) RCSL No 31-D 522: FPASTAT, DISCSTAT

Print is a program running under FP (File Processor). It is
used to print the contents of memory in several formats.

With Montest you have an easy way to check processdescriptions
and messagebuffers.

When you are using the statistical programs FPASTAT and DISCSTAT
remember that the FPA test will contribute to the fpastatistic,
as opposed to the disc test, which will n_o_t_ contribute to the
discstatistic.

F_ 9_._ _ _ _ _ _ _ _ _T_H_E_ _T_E_S_T_P_R_O_G_R_A_M_S_ 9.

9_._1_ _ _ _ _ _ _ _M_e_m_o_r_y_ _T_e_s_t_,_ _E_x_a_m_p_l_e_ 9.1
\f

F_ 9_._2_ _ _ _ _ _ _ _C_P_U_-_T_e_s_t_ 9.2

The CPU-test does provoke internal interrupts, which will cause
the internal process representing the CPU-test to be stopped
after error. If you use the "s" command "list", you will often
see this.

For all the other testprograms this will be a strong indication
of an error; but for the CPU-test it is normal.

F_ 9_._2_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 9.2.1
\f

F_ 9_._3_ _ _ _ _ _ _ _D_I_S_C_ _T_e_s_t_ 9.3

In order to run the disctest the external process for the
physical disc m_u_s_t_ have a name.

Note that this name will disappear if you change the disc-pack.

You have to know the l_o_g_i_c_a_l_ _d_e_v_i_c_e_ _n_o_. of the physical disc,
when you want to name a discprocess.

You may use MONTEST, to verify that a certain device number
represent a physical disc. Device kind is 62 and main process
description address is zero.

It is recommended always to use MONTEST before naming a device.

9_._3_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 9.3.1

att s
New FIG RUN
MONTEST external devno.28

If device number 28 is a physical disc you will have:
kind: 62
main: 0

att s
call 28 UNIT1

This "s" command will insert the name "UNIT1" in the external
processdescription for the logical device No 28.

F_ 9_._3_._2_ _ _ _ _ _E_x_a_m_p_l_e_ 9.3.2
\f

9_._3_._3_ _ _ _ _ _C_-_t_e_s_t_ _(_t_e_s_t_ _l_o_o_p_ _b_u_i_l_d_e_r_)_ 9.3.3

This is a new version of the C-test. The few changes are
described below. Detailed information to the test are found in
RCSL 30M241. The test enable the operator to define simple
channelprograms, which contains 3 channel commands. The
parameters p026 - p031 defines the two first commands, the third
will always be a stop command. There is no INIT command before
these 3 as in the old version.

The buffer area is change to:

The buffer area from 12296 - 12898 is a permanent area and is not
destroyed after each run. It is possible to use it to channel
program parameters. The area from 12900 - 23690 is cleared every
\f

time the test is started, and data specified in p033 - p035 are
inserted after this clearing. Notice that the addresses in the
buffer area are decimal relative to the testbase, and not the
real core addresses. The testbase is written every time the test
is executed.

9_._3_._4_ _ _ _ _ _A_d_j_u_s_t_m_e_n_t_ _o_f_ _h_e_a_d_s_ 9.3.4

It is possible to adjust the discdrives under "system running"
with the c-test. The procedure is described below. The disc must
be "free" to the technicians. The example is valid for 33/66 MB.
discdrives.

1. Power off the disc
2. Mount the master kit
3. The execiser board is inserted in slot 8, and the small cabel
in the read board. Connect the oscilloscope to the execiser.
The A/B cabel is not used.
4. Start the disc
5. CALL the disc e.g. CALL 26 DISC1.
6. Specify the parameters to the c-test after the procedure
below (1)
7. Start the test
8. CALL the disc e.g. CALL 26 DISC1 START
9. Specify the c-test with the parameters in (2)
10. Start the test. The heads are placed on cylinder 245 and head
no. 0 is thoosen.
11. Insert the aligment pin and adjust head no. 0
12. Select head with param 035 (3)
13. Start the test and adjust the new head
14. Repeat 12 - 13 untill all the heads are adjusted
15. Remove the aligment pin and unload the heads
\f

PARAMETERS TO THE C-TEST

(1) (2) (3)
000 C C C
001 1 1 1
002 5 (unit 1) 5 5
003 23 (33MB) 23 23
049 10 10 10
026 IN SK SK
027 12296 irrelevant 12296 12296
028 0 - 0 irrelevant 0 irrelevant
029 ST ST ST
030 12940 12940 12940
031 0 0 0
032 1 1 1
033 12296 12298 12296
034 1 1 1
035 00172400 00000000 see note
036 500 500 500

Note:

HEAD 0 33/66 035 00172400
HEAD 1 33/66 035 00172401
HEAD 2 33/66 035 00172402
HEAD 3 33/66 035 00172403
HEAD 4 33/66 035 00172404
\f

9_._4_ _ _ _ _ _ _ _F_P_A_ _T_e_s_t_ 9.4

The FPA test is sharing buffers in the front-end with other
devices. This means that an FPA output ERROR may occur.

If the parameter 018 is greater than max. blocksize you may be
sharing buffers with the magnetic tape driver. If somebody else
is using magnetic tape at the same time, you may see the error:

+ + FPA801 OUTPUT ERROR
characters expected: <number'
characters transferred: 0

Your can only avoid the error by changing the max. blocksize
parameter to a smaller size. (e.g. P018/256).
\f

F_ 9_._4_._1_ _ _ _ _ _E_x_a_m_p_l_e_ 9.4.1
\f

F_\f

F_ A_._ _ _ _ _ _ _ _ _F_O_R_M_A_T_ _O_F_ _"_T_O_P_>_s_"_ _F_I_R_S_T_ _S_E_G_M_E_N_T_ A.

In the first segment of "TOP" a number of informations is stored.
You may find this segment in the following way:

att s
list

This will give you the memory address where TOP is placed.

Then you may create an FP-process and use the program "Montest".

att s
New FIG RUN
Montest veri <memaddress'.34
\f

F_ <mem start address'
+0 ; address of first location of area
+2 ; wo dump in case of
+4 ; w1 internal interrupt
+6 ; w2
+8 ; w3
+10 ; status
+12 ; IC
+14 ; cause
+16 ; SB
+18 ; no. of segments shift 16
+20 ; checksum
+22 ; escape buffer address
+24 ; process descr addr for primout
(console)
+26 ; stack start address
+28
+30
+32 O, R55 ; Dump of TOP>s process description in
case of internal interrupt

Format of escape buffer:
+0 ; last buffer address
+2 ; current pointer
+4 ; from address
+6 ; to address
+8 ; from address
+10 ; to address

F_ B_._ _ _ _ _ _ _ _ _I_M_P_O_R_T_A_N_T_ _N_O_T_E_S_ B.

1) Do not Remove a disctest without Breaking it.

2) Avoid "REMOVE RUN" if more than one job on the same terminal.

2.2 Dead Start for RC 6000

From the F19 Power and Autoload Panel

F19 Power and Autoload Panel

1) The ON/OFF switches on the individual terminal device(s) and
peripheral devices (see sections 8 and 9) should be turned on
once and for all so that power is always applied to the com-
plete system through the POWER key.

2) Turn on the mains power supply.

3) Insert POWER Key.

4) Apply power to the system by turning the POWER key to its ex-
treme clockwise position, pushing in, and then turning the
POWER key to its extreme counter-clockwise position. Release
the POWER key.

5) When the POWER OK indicator lights proceed to Section 3 Auto-
loading. Power is hereby automatically applied to all units of
the system. (Exceptions are the RC 3645 Charaband Printer and
the RC 8221/2/3/4/5/6 Disc Storage Modules, which have separate
power supplies.)

6) If the POWER OK lamp does not light then repeat the above pro-
cedure. If this is not successful then call a service engineer.

RCSL No. 42-i0938\f

F_ 2.3 Daily Restart

For the RC 6000 System

Daily Restart procedure is the same as the Dead Start procedure.

See, therefore, Section 2.2

RCSL No. 42-i0399\f

F_ 2.4 Power Failure Restart for RC 6000

If power failure occurs while an application program is in use
then loss of information can occur. See therefore the instruc-
tions given in the description of the application program in
question.

Recovery after a power failure can otherwise always be made by
autoloading again.

RCSL No. 42-i0939\f

F_ 3.1.2 RC 6000 System Information

The RC 6000 Basic Software, user software and user"s registers
are located on a number of disc packs. This is to say that the RC
6000 Basic Software disc pack mentioned in Section 3.2.1 - step
2) is to be understood as the complete set of Disc Packs for this
specific system (the number may vary from 1 to 4 disc packs). The
disc packs should, furthermore, be mounted in the associated disc
drives.

Below you will find the names of the disc packs associated with
your system, and the disc drives in which they are to be mounted.

Disc Pack Label Disc Drive
No.

RCSL No. 42-i0940\f

F_ 3.2 Autoloading From Disc Cartridge

3.2.1 I_n_s_e_r_t_i_n_g_ _t_h_e_ _B_a_s_i_c_ _S_o_f_t_w_a_r_e_ _D_i_s_c_ _P_a_c_k_ _i_n_ _t_h_e_ _D_i_s_c_ _C_a_r_t_r_i_d_g_e_ _D_r_i_v_e_

RC 3652 Disc Cartridge Drive

1) Check that the LOAD/RUN switch (1) is in the LOAD position
and that the LOAD light (2) is on.

2) Insert the Basic Software Disc Pack in the disc cartridge
drive.

Inserting a disc pack in the disc cartridge drive.

RCSL No. 42-i 0941\f

F_ 3) Close the lid and set LOAD/RUN switch (1) to RUN.

4) Check that console device and printer (if present) are
switched on.

5) When the yellow READY lamps on all disc cartridge drives (3)
light proceed to Section 3.3

RCSL No. 42-i 0941\f

F_ 4.2 Initializing Procedure for the RC 6000 System

4.2.1 I_n_i_t_i_a_l_i_z_i_n_g_ _t_h_e_ _B_a_s_i_c_ _S_o_f_t_w_a_r_e_
The following procedure must be carried out at the main terminal
(console):

Check that power is applied to the terminals and printer.

1) Several items of information will now appear on the main ter-
minal. An example is given here:

FROM S

OLD CATALOG LOGUD RESULT 3
DISC1 STATUS ...1...............
DISC2 STATUS ...1...............

MONITOR VERSION: 22.10.78 12.00.00
DATE OF OPTIONS: 18.11.78 00.00.00

2) The following will also be output to the main terminal:

initialize date:

3) The date must then be typed in using the following format:

day'month'year'hour'minute'second' RETURN

For example:

22 01 78 16 26 15 RETURN

could be typed.

N_o_t_e_: A complete line can be written on the terminal display
without the system acting on the contents of the line. The system
will first act on the line when the RETURN key is depressed. It
is therefore possible to correct typing errors before the RETURN
key is depressed. Pressing the RUBOUT key will delete the last
typed character; pressing it repeatedly will delete further cha-
racters to the left. Pressing the Line Feed key will delete the
entire line.

RCSL No. 42-i 0404\f

F_ A common error message is:

syntax

This indicates than an error has been made in the typing in
of a command or its parameters. It could, for example, be a
spelling error. When a syntax error appears the command has
not been accepted, therefore retype the command correctly.

4) After the RETURN key is pressed the text "ready" will ap-
pear on the terminal display.

RCSL No. 42-i 0404\f

F_ 5.2 Process Creating Procedure for the RC 6000 System

5.2.1 The following procedure can be carried out from any terminal in
the system if the terminal is switched on.

1) Type: ESC
The text "att #" will appear on the terminal.

2) Type: S RETURN

3) Type:

all processname' base 0 9 0 100 run RETURN

where "all" is the command telling the monitor that this user
wants the entire system and resources (other commands can be
used). processname' is the text (name) used by this specific
company for the program to be executed, and "base 0 9 0 100"
is the key under which the program has been stored, telling
the system that this user is allowed to use this specific
program.

4) After a few seconds the following will appear on the termi-
nal:

READY
TO processname'

Below you will see an example of the complete contents of the
terminal. The typed text is shown underscored.

ESC att # S_ RETURN
# A_L_L_ _R_C__S_ _B_A_S_E_ _0_ _9_ _0_ _1_0_0_ _r_u_n_
READY

TO RCS
#

A program from the program library situated on the disc can now
be loaded.

RCSL No. 42-i 0405\f

F_ 5.3 Process Removal for RC 6000 System

Before a process is removed programs loaded into it must be ter-
minated. The program removal procedure is dependent on the pro-
gram running in the process. See, therefore, the appropriate pro-
gram description for instructions on program termination.

As a general rule processes should be removed at the respective
terminals before the system is shutdown.

The system can only be shut-down from the console therefore
process removal in connection with system shutdown is described
in Section 7 System Shutdown.

1) Type:
ESC S RETURN
The text "att" appears on the terminal display.

2) Type:
remove RETURN
When this command has been executed the following will appear
on the terminal display:
to process name'

3) Type:
RETURN
The following will now appear on the terminal display:
from S
ready

The process removal procedure is now complete. If another process
is required then go to Section 5.2. Process Creation.

If the process has been removed in order to shut down then go to
Section 7 System Shutdown, Process Removal and System Shutdown.

RCSL No. 42-i0942\f

F_ (6)1 Description of Flexible Disc Programs

(6)1.1 Introduction

Flexible discs are the data medium whereby invoicing, book-keep-
ing postings and stock movement information are transferred to
the central RC 4000 computer system. In addition to this periodic
transfer of information via flexible discs to the central compu-
ter the individual RC 6000 user should also use the flexible
discs to take safety copies of all files from the cartridge disc
(DRUM).

The programs required for administration and copying of flexible
discs are:
1) flxdope
2) flxsave
3) flxload
4) flxlookup
where flx is simply an abbreviation for flexible disc. The use of
the specific programs is described in the following sections. But
a brief description will be given here.

(6)1.1.1 f_l_x_d_o_p_e_
Before a flexible disc can be used it must be given some form of
identification. This identification is written on the flexible
disc using the flxdope program.

The operator should immediately transfer this information to the
cover of the flexible disc.

N_o_t_e_:_ Remember that the WRITE PROTECT should be de-activated
before any information can be written on the flexible disc, i.e.
WRITE PROTECT push-button (2) should not be lit.

The recommended practice is to name a certain number of flexible
discs with the flxdope program, at the beginning of the day or
week, so that named flexible discs are always available when
required.

I_M_P_O_R_T_A_N_T_: It is, in fact, essential that flexible discs in
quantities sufficient to contain the day's invoices or book-keep-
ing are named before the invoicing or postings programs are
called; once the invoicing or postings programs run, it is im-
possible to call the flxdope program to name a flexible disc

RCSL No. 42-i 0416\f

should the current flexible disc be full.

(6)1.1.2 f_l_x_s_a_v_e_
When all files (e.g., article file, customer file, etc.) have
been created using the maintain program, they will initially only
exist on the cartridge disc (DRUM). The proper functioning of the
system is, therefore, entirely dependent on the integrity of
DRUM; if DRUM is damaged, and the files thereby spoiled, much
time must be invested to create and check the files again.

This problem can be avoided by taking regular safety copies of
all files on flexible discs using the flxsave program. If DRUM is
damaged, the latest copies of DRUM files on flexible discs can
then be transferred to a new copy of DRUM.

(6)1.1.3 f_l_x_l_o_a_d_
This program is used to transfer information (files or programs)
from flexible disc to DRUM. The flxload program is used, for
example, to load safety copies of files onto DRUM if the existing
files are damaged. flxload functions, in fact, in the opposite
direction to flxsave (see flxsave).

The flxload program can also be used, for example, to load a new
program version to DRUM, if required.

(6)1.1.4 f_l_x_l_o_o_k_u_p_
The flxlookup program is used to obtain information on the con-
tents of a flexible disc, i.e. the flexible disc index is "looked
up". The amount of detail obtained from the index can be con-
trolled by the operator.

(6)1.2 Program Name: flxdope

(6)1.2.1 I_n_t_r_o_d_u_c_t_i_o_n_
The following describes the procedure for naming flexible discs
with the flxdope program. All flexible discs must be named before
they can be used.

In its general form the program is called and operated as fol-
lows:
2
owner.owner ident' 2
flxdope name.flxname' 0
color.flx.color'0

RCSL No. 42-i 0416\f

The parameter name.flxname' is compulsory, it gives the flexible
disc a name. The bracketed parameters indicate that a mini-
mum of 0 of the parameters enclosed are compulsory and a maximum
of 2 is allowed. (This may be easier to understand if one imagi-
nes that the numbers attached to the brackets were as follows:
. This indicates that a minimum of 1 parameter compulsory
and a maximum of 3 is allowed. The compulsory parameter can be
any of the parameters enclosed in the brackets, in other words,
as long as one of the parameters in brackets is used the condi-
tions are satisfied.)

The owner.owner ident' parameter causes an identification of the
owner of the flexible disc to be written on the flexible disc.
This identification could, for example, be your company name.

The color.flxcolor' parameter is a means of categorizing the dif-
ferent flexible discs after information content, where a colored
label on the outside of the disc cover immediately informs the
operator on the flexible disc"s type of information content. This
parameter causes the label color to be written on the disc.

The parameters may also be written in any order:

flxdope name.flxname' owner.owner ident' color.flxcolor'
flxdope owner.owner ident' name.flxname' color.flexcolor'
flxdope name.flxname' color.flxcolor' owner.owner ident'

are all valid.

If RETURN must be used in the middle of a parameter list, then
a comma (,) must be typed before RETURN.

P_a_r_a_m_e_t_e_r_s_
flxname' must be an unbroken string of up to 6 characters or di-
gits.
owner ident' must be an unbroken string of up to 11 characters
or digits.
flxcolor' must be one of the following:
red
green
blue
grey
yellow
violet

RCSL No. 42-i 0416\f

These colors can be matched with the colored labels supplied with
the flexible discs and be used to indicate the type of information
on a particular flexible disc. For example, green for invoicing,
blue for postings, grey for safety copies of files.

(6)1.2.2 P_r_o_c_e_d_u_r_e_
1) Insert unnamed flexible disc in flexible disc drive and close
door.
2) Press WRITE PROTECT push-button so that WRITE PROTECT light
goes out.
3) Type:
flxdope name.flxname' color.flxcolor' owner.owner ident'
RETURN
(This line is completed when Section 5.2 is carried out. See
section 5.2 Program Loading.)
4) When the text
endnumber'
#
appears on the terminal display either remove the flexible
disc and name another flexible disc in the same way, or load
another program and use the flexible disc just named.

(6)1.2.3 U_s_e_ _o_f_ _t_h_e_ _f_l_x_d_o_p_e_ _c_o_m_m_a_n_d_ _i_n_ _N_i_l_f_i_s_k_ _6_0_0_0_ _I_n_v_o_i_c_i_n_g_ _S_y_s_t_e_m_

R_e_c_o_m_m_e_n_d_e_d_ _u_s_e_ _o_f_ _p_a_r_a_m_e_t_e_r_s_:_
1) flxname' must be 6 characters.
Use the first 2 characters for country code and the remaining
4 for flexible disc accession number,
i.e. flxname' = 0 0 0 0 0 0
country accession
number number

Example:
country code = 04 (i.e., text country, Utopia)
accession number = 0013 (i.e., the 13th flexible disc
used in the system)
flxname' = 040013

2) owner ident' a maximum of 11 characters.
Use the first character for company name immediately followed
by country code.

Example:
owner ident' = nilfisk04 (04 = Utopia)

RCSL No. 42-i 0416\f

3) flxcolor' must be one of the following:
red
green
blue
grey
yellow
violet

Use as follows:
red - programs ( a new program version)
green - invoicing
blue - postings and stock movements
grey - safety copies of files
yellow - not yet used
violet - not yet used

If, for example, the flexible disc to be named is intended for
invoicing, then
flxcolor' = green
and the complete program load operation as given in 1.2.2
Procedure step (3) would be as follows:

Type:
flxdope name.040013 color.green owner.nilfisk04 RETURN

(6)1.3 Program Name: flxsave

(6)1.3.1 I_n_t_r_o_d_u_c_t_i_o_n_
The following describes the procedure for copying disc cartridge
files onto flexible discs using the flxsave program.

In its general form the program is called and operated as
follows:

1owner.owner ident' 3
flxfile' = flxsave file.disc file' name.flxname' color.flxcolor'
0 fileage.no. of days' 0

The parameter file.disc file' is the name of a file on the car-
tridge disc and is a compulsory parameter. The parameter
name.flxname' is the name of the flexible disc and is also a com-
pulsory parameter. The bracketed parameters 0 indicates that a
minimum of 0 of the parameters enclosed are compulsory and a maxi-
mum of 3 is allowed. (This may be easier to understand if one

RCSL No. 42-i 0416\f

imagines that the numbers attached to the brackets were as fol-
lows:
This indicates that a minimum of 1 parameter is compulsory and a
maximum of 3 is allowed. The compulsory parameter can be any of
the parameters enclosed in the brackets, in other words, as long
as one of the parameters in brackets is used the conditions are
satisfied.)

The owner.owner ident' parameter is checked against that written
on the flexible disc.

The fileage.no. of days' parameter gives the number of days from
the system"s current date the file must be preserved, i.e., the
file must not be destroyed before no. of days' days have elapsed.

The parameter flxfile' which precedes the actual program name is
optional and need only be used when the contents of a disc car-
tridge file, named disc file' are to be transferred to a flex-
ible disc file of a different name, flxfile'. For example, the
customer file on the cartridge disc may be called "customerreg".
If "customerreg" is frequently updated then it may be appropriate
to give the flexible disc containing the safety copy of "customer-
reg" a date. "customreg10" would then indicate that the flexible
disc file contains a copy of "customerreg" (on the cartridge disc)
from October (10th month).

In this case the program call would be written as follows:
customreg10 = flxsave file.customerreg name.flxname' etc.

The parameters may also be written in any order:

flxsave name.flxname'owner.owner ident'fileage.no of days'
color.flxcolor'name.flxname'
flxsave file.discfile'name.flxname'color.flxcolor'
owner.owner ident'fileageno. of days'

are both valid.

Remember that if RETURN must be used in the middle of a parameter
list, then a comma (,) must be typed before RETURN.

P_a_r_a_m_e_t_e_r_s_
flxname' is the name of the flexible disc (given with flxdope)
onto which the cartridge file is to be copied.

RCSL No. 42-i 0416\f

owner ident' is the same as the owner ident' given to the flex-
ible disc with the flxdope program.

flxcolor' must be grey if copies of files are to be taken.

no. of days' is a number giving the number of days from the sys-
tem date the file must be preserved.

disc file' is the name of the cartridge file - a maximum of 11
characters.

flxfile' - the name of the flexible disc file - a maximum of 11
characters.

(6)1.3.2 P_r_o_c_e_d_u_r_e_
1) Insert named flexible disc in flexible disc drive and close
door.
2) Press WRITE PROTECT push-button so that WRITE PROTECT light
goes out.
3) Type:
1
flxfile' = flxsave file.disc file'name.flxname'
0
owner.owner ident'color.flxcolor'fileage.no of days' RETURN

(This line is, in fact, completed when Section 5.2 is carried
out. See Section 5.2 Program Loading.)

4) When the text
end number'
#
appears on the terminal display then the flxsave procedure is
complete.

(6)1.3.3 U_s_e_ _o_f_ _t_h_e_ _f_l_x_s_a_v_e_ _c_o_m_m_a_n_d_ _i_n_ _N_i_l_f_i_s_k_ _R_C_ _6_0_0_0_ _I_n_v_o_i_c_i_n_g_ _S_y_s_t_e_m_

P_a_r_a_m_e_t_e_r_s_:_
1) flxname' = 040014 (same as flxname' given under flxdope
program).
2) owner ident' = nilfisk04 (same as owner ident' given under
flxdope program).
3) flxcolor' = grey (for safety copy of a disc cartridge file).
4) If the article file on the cartridge disc is called article-
reg, and the copy is made after an update in the month of June,
then the disc file could be called artreg06. The file age no.
of days' parameter could be set to 31 days when a newupdate

RCSL No. 42-i 0416\f

and copy of the file would be made.
5) The parameters are then as follows:
flxfile = artreg06
disc file = articlereg
flxname = 040014
owner ident = nilfisk04
flxcolor = grey
no. of days = 31
6) The complete program load operation as given in 1.3.2
Procedure step (3) would be as follows:

Type:

artreg06 = flxsave file.article reg name.040014 owner.nilfisk04.
color.grey fileage.31 RETURN

(6)1.4 Program Name: flxload

(6)1.4.1 I_n_t_r_o_d_u_c_t_i_o_n_
The following describes the procedure for copying flexible disc
files and programs onto cartridge discs using the flxload
program.

In its general form the program is called and operated as
follows:

1 owner.owner ident 2
disc file' = 0 flxload file.flxfile' name.flxname' color.flxcolor'0

The parameter file.flxfile' is the name of the file on the flex-
ible disc and is a compulsory parameter. The parameter name.flx-
name' is the name of the flexible disc and is also a compulsory
parameter. The bracketed parameters indicate that a minimum
of 0 of the parameters enclosed are compulsory and a maximum of 2
is allowed. (This may be easier to understand if one imagines
that the numbers attached to the brackets were as follows: .
This indicates that a minimum of 1 parameter is compulsory and a
maximum of 3 is allowed. The compulsory parameter can be any of
the parameters enclosed in the brackets, in other words, as long
as one of the parameters in brackets is used the conditions are
satisfied.)

The owner.owner ident' parameter is checked against that written
on the flexible disc.

RCSL No. 42-i0416\f

The color.flxcolor' parameter is also checked against that writ-
ten on the flexible disc.

The parameter disc file' which precedes the actual program name
is optional and need only be used when the contents of a flexible
disc file, named flxfile' are to be transferred to a disc car-
tridge file of a different name, disc file'.

For example, it may be necessary to transfer the latest flexible
disc safety copy of the customer file to a cartridge disc. The
file on the cartridge disc may be called "customerreg", and the
latest copy may be called customreg10 (indicating that this copy
was made in October, the 10th month). In this case the program
call would be written as follows:

customerreg = flxload file.customerreg10 name.flxname' etc.

The parameters may also be written in any order as follows:

flxload file.flxfile'color.flxcolor'owner.owner
ident'name.flxname'
flxload owner.owner ident'file.flxfile'color.flxcolor'
name.flxname'

are both valid.

Remember that if RETURN must be used in the middle of a parameter
list then a comma (,) must be typed before RETURN.

P_a_r_a_m_e_t_e_r_s_
flxname' is the name of the flexible disc (given with flxdope)
from which the file is to be copied.

owner ident' is the same as the owner ident' given to the flex-
ible disc with the flxdope program.

flxcolor' must be grey if copies of files are being transferred
or red if new program versions are being transferred.

disc file' is the name of the disc cartridge file - a maximum of
11 characters.

flxfile' is the name of the flexible disc file - a maximum of 11
characters.

RCSL No. 42-i0416\f

(6)1.4.2 P_r_o_c_e_d_u_r_e_
1) Insert named flexible disc in flexible disc drive and close
door.

2) Type:
1
disc file' flxload file.flxfile' name.flxname'
0 owner.owner ident' color.flxcolor' RETURN

3) When the text
end number'
#
appears on the terminal display then the flxload is complete.

(6)1.4.3 U_s_e_ _o_f_ _t_h_e_ _f_l_x_l_o_a_d_ _c_o_m_m_a_n_d_ _i_n_ _N_i_l_f_i_s_k_ _R_C_ _6_0_0_0_ _I_n_v_o_i_c_i_n_g_ _S_y_s_t_e_m_

P_a_r_a_m_e_t_e_r_s_

1) flxname' = 040015 (same as flxname' given under flxdope
program).

2) owner ident' = nilfisk04 (same as owner ident' given under
flxdope program).

3) flxcolor' = grey (for safety copies of disc cartridge files).

4) If the article file on the cartridge disc is called articlereg
and the latest flexible disc copy is from September, for
example, then the flexible disc file could be called artreg09,
if this was the name given under flxsave.

5) The parameters are then as follows:
disc file = articlereg
flx file = artreg09
flxname = 040015
owner ident = nilfisk04
flxcolor = grey

6) The complete program load operation as given in 1.4.2 Proce-
dure step (2) would be as follows:

Type:
artreg = flxload file.artreg09 name.040015 owner.nilfisk04
color.grey RETURN

RCSL No. 42-i0416\f

N_o_t_e_: Safety copies of flexible discs can also be taken by using
the flxload program to load the flexible disc onto DRUM (take
care to use a new file name - otherwise the flexible disc file
may be loaded on top of an existing DRUM file). The flexible disc
should then be removed, a new one inserted, and the flxsave pro-
gram used to transfer the file on DRUM to the flexible disc.

(6)1.5 Program Name: flxlookup

(6)1.5.1 I_n_t_r_o_d_u_c_t_i_o_n_
The following describes the procedure for "looking up" in the
index of flexible discs with the flxlookup program.

In its general form the program is called and operated as fol-
lows:

file.flxfile' 3
flxlookup name.flxname'
quantity.amount' 0

The bracketed parameters indicate that a minimum of the0 of
parameters enclosed are compulsory and that a maximum of 3 is
allowed. (This may be easier understood if one imagines that the
numbers attached to the brackets were as follows: .This in-
dicates that a minimum of 1 parameter is compulsory and a maximum
of 3 is allowed. The compulsory parameter can be any of the pa-
rameters enclosed in brackets, in other words, as long as one of
the parameters in brackets is used the conditions are satisfied.)

The name.flxname' parameter is the name of the flexible disc.

The file.flxfile' parameter is the name of the file on the flex-
ible disc about which information is required.

The quantity.amount' gives the amount of information required.

The parameters can also be written in any order.

P_a_r_a_m_e_t_e_r_s_

flxname' must be an unbroken string of up to 6 characters or
digits.

RCSL No. 42-i0416\f

flxfile' is the name of the flexible disc file - a maximum of 11
characters.

amount' can take the values:
nil
min
max

If n_i_l_ is used:
flxname'
owner ident'
flxcolor'
space left' (how much room there is left on the
flexible disc)
is written out on the terminal display.

If m_i_n_ is used:
flxname'
owner ident'
flxcolor'
flxfile'
valid to' (date when file may be destroyed)
file space left' (space left in this file)
is written out on the terminal display.

If m_a_x_ is used:
flxname'
owner ident'
flxcolor'
creation date' (date of file creation)
last updated' (date when file was last updated)
valid to' (date when file may be destroyed)
file location'
file location' (location of file on disc)
file location'
file space left' (space left in this file)
is written out on the terminal display.

(6)1.5.2 P_r_o_c_e_d_u_r_e_
1) Insert flexible disc in flexible disc drive and close door.

2) Type:
flxlookup file.flxfile'name.flxname'quantity.amount' RETURN

RCSL No. 42-i0416\f

3) When the text
end number'
#
appears on the terminal display then the lookup program may be
used again, or any other program may be loaded.

(6)1.6 Error Messages

The following error messages can occur during use of the flexible
disc programs.

c_o_m_m_a_n_d_ _s_y_n_t_a_x_ Program called incorrectly. This
error will occur if flxsave, flx-
load, flxdope are typed without
parameter, i.e. flxsave RETURN
etc.

f_i_l_e_n_a_m_e_ _f_o_r_m_a_t_ _i_l_l_e_g_a_l_ The discfile' or flxfile' para-
meters are incorrectly used; the
first character must be a letter.

f_i_l_e_a_g_e_ _s_y_n_t_a_x_ no. of days' must be an integer
value.

c_o_l_o_r_ _s_y_n_t_a_x_ flxcolor' does not exist in the
list of allowed colors.

p_a_r_a_m_ _l_i_s_t_ _s_y_n_t_a_x_ Parameter incorrectly placed or
incorrectly spelled.

p_e_r_i_p_h_e_r_a_l_ _p_r_o_c_e_s_s_ _n_o_t_
c_r_e_a_t_e_d_ __c_o_d_e_'_

p_r_o_c_e_s_s_ _n_o_t_ _r_e_m_o_v_e_d_ __c_o_d_e_'_

The following error messages can occur during operation of the
flxdope program.

n_a_m_e_ _m_i_s_s_i_n_g_ flxname' has been omitted

t_h_e_ _m_o_u_n_t_e_d_ _d_i_s_k_e_t_t_e_ _i_s_ The flexible disc is damaged on the
d_e_f_e_c_t_ file catalog track.

RCSL No. 42-i0416\f

The following errors can occur during operation of the flxsave
program.

d_i_s_k_e_t_t_e_ __f_l_x_n_a_m_e_'_The flexible disc mounted does not
n_o_t_ _m_o_u_n_t_e_d_ have the name flxname'.

o_w_n_e_r_ _d_o_e_s_ _n_o_t_ _f_i_t_ The entered owner ident' does not
agree with the information on the
flexible disc.

c_o_l_o_r_ _d_o_e_s_ _n_o_t_ _f_i_t_ The entered flxcolor' does not
agree with the information on the
disc.

r_e_d_ _d_i_s_k_e_t_t_e_s_ _a_r_e_ _r_e_s_e_r_v_e_d_ Red flexible discs are reserved for
system programs and are "write pro-
tected".

n_o_ _r_o_o_m_ flxfile' does not already exist
but there is no room on this flex-
ible disc to create one of the re-
quired size.

_f_l_x_f_i_l_e_'_ _t_o_o_ _s_m_a_l_l_ flxfile' exists already but is not
large enough to contain disc file'.

_f_l_x_f_i_l_e_'_ _r_e_s_e_r_v_e_d_ flxfile' exists already but "valid
to" date is not exceeded.

_d_i_s_c_ _f_i_l_e_'_ _d_o_e_s_ _n_o_t_ _e_x_i_s_t_ This file does not exist on the
cartridge disc.

_d_i_s_c_ _f_i_l_e_'_ _t_o_o_ _b_i_g_ The file on the cartridge disc con-
sists of more than 300 segments,
which is the flexible disc's maxi-
mum size.

The following error messages can occur during operation of the
flxload program.

d_i_s_k_e_t_t_e_ __f_l_x_n_a_m_e_'_ _n_o_t_ flxname' does not agree with the
m_o_u_n_t_e_d_ name on the flexible disc mounted.

RCSL No. 42-i0416\f

o_w_n_e_r_ _d_o_e_s_ _n_o_t_ _f_i_t_ The entered owner ident' does not
correspond with the owner ident'
on the flexible disc.

c_o_l_o_r_ _d_o_e_s_ _n_o_t_ _f_i_t_ The entered flxcolor' does not
correspond with the information on
the flexible disc.

_f_l_x_f_i_l_e_'_ _d_o_e_s_ _n_o_t_ _e_x_i_s_t_ flxfile' does not exist on this
flexible disc.

t_h_e_ _f_i_l_e_ _c_a_n_n_o_t_ _b_e_ _c_r_e_a_t_e_d_ disc file' cannot be created due
o_n_ _t_h_e_ _d_i_s_c_ _b_e_c_a_u_s_e_to one of the five possible rea-
- of catalog I/O errorsons.
- of name conflict
- of no resources
- of catalog base conflict
- the name format is illegal

RCSL No. 42-i0416\f

F_ (6) Program Name: lookup

I_n_t_r_o_d_u_c_t_i_o_n_
The lookup program is used to obtain information about the loca-
tion and size of storage area requirements of files.

P_r_o_c_e_d_u_r_e_
Type:

lookupfilename' RETURN

If this file name does not exist then the following will be out-
put:

***lookupfilename' unknown

If the filename does exist then the following will be output:

filename' = set no. of segments'disc name'
n'n'n'n'n';project
;n'n'n'n'n'

The following parameters are important:-
filename' = set no. of segments'disc name' n' n'
n'n'n';project
;n'n'n'n'n'

n' = number' how many times the file
has been updated.
n' = either 0 or 1 - update mark.
If 0 then file is correct.
If 1 then system failure has oc-
curred during opdating of this file
(see maintain program).
no. of segments' how many segments of the
disc this file occupies.

RCSL No. 42-i0432\f

F_ (6) Program Name: claim

I_n_t_r_o_d_u_c_t_i_o_n_
This program lists the resources which are still available to the
user.

P_r_o_c_e_d_u_r_e_
Type:

claim RETURN

The following will now appear on the terminal display:

arean' bufn' sizen' first coren'

drum: 1 seg/slice
temp n' segm n' entr
user n' segm n' entr
project n' segm n' entr

n' = number

tempn' segm n' entr
gives the number of segments left on the disc (n' segm) and the
maximum no. of files which can be created (n' entr).

RCSL No. 42-i0417\f

F_ (6) Program Name: O

I_n_t_r_o_d_u_c_t_i_o_n_
This program is used to change the current output device.

P_r_o_c_e_d_u_r_e_
Type:
O lp RETURN

lp (line printer) is now the current output device.

If the output is to be returned to the terminal display -

Type:
O c RETURN

E_x_a_m_p_l_e_:_
Type:
( O lp RETURN
lookup articlereg RETURN
O c ) RETURN

The first line informs the system that the output is required on
the line printer.

The second line shows that a "lookup" of the article file is re-
quired.

The third line indicates that when this is complete then the out-
put should be returned to the terminal display.

The brackets () indicate that what follows after the left-hand
bracket should not be performed before the right-hand bracket is
typed.

RCSL No. 42-i0418\f

F_ (6) Program Name: clear

I_n_t_r_o_d_u_c_t_i_o_n_
This program removes a file and its catalog entry from DRUM.

P_r_o_c_e_d_u_r_e_
Tyep:
clear scope' filename' RETURN

scope' can be either project, user or temp.

A file on project base means that all users of the system have
access to the file.

A file on user base means that only the individual user with
user base' has access to the file.

A file on temp base is stored only temporarily on DRUM - it dis-
appears at the next autoloading.

RCSL No. 42-i0419\f

F_ (6) Program Name: copy

I_n_t_r_o_d_u_c_t_i_o_n_
The program copy is intended for obtaining output of the day"s
input, a copy of which is stored on the disc until the next time
the particular program is used.

The files containing the day"s input are postings log, invoicing
log and maintain log.

P_r_o_c_e_d_u_r_e_
Type:
lp = copy log name' RETURN

lp means that the output will appear on the line printer (lp).

log name' can be postlog, invlog or maintainlog.

RCSL No. 42-i0420\f

F_ (6) Program Name: set

I_n_t_r_o_d_u_c_t_i_o_n_
The program set is intended to create an empty area with a cer-
tain name on a specified disc unit. After the program call the
file will have scope temp.

P_r_o_c_e_d_u_r_e_
new area' = set number'disc unit' RETURN
where:
new area' is a name with at most 11 letters
number' means number of segments
disc unit' can be drum or disc.

E_x_a_m_p_l_e_
If you wish to create a new empty area called hidetextreg on disc
you can type:
hidetextreg = set 10 disc

RCSL No. 42-i0943\f

F_ (6) Program Name: scope

I_n_t_r_o_d_u_c_t_i_o_n_
The program scope is intended to change scope level of files.

scope level:
temp means temporary
user means user permanent
project means project permanent

All files with scope temp will disappear when you autoload.

P_r_o_c_e_d_u_r_e_
scope level'filename'
where level can be temp, user or project. Filename means the name
of the area.

E_x_a_m_p_l_e_
scope user hidetextreg
the file hidetextreg will be permanent on user level after the
program call.

RCSL No. 42-i 0944\f

F_ (6) Program Name: move

I_n_t_r_o_d_u_c_t_i_o_n_
The program move is intended to move the content of one file to
another area. Suppose you have a file called textreg and an area
called hidetextreg, then you can move textreg to hidetextreg. If
textreg is bigger than hidetextreg then hidetextreg will be
increased automatically to the same size during the operation.

P_r_o_c_e_d_u_r_e_
new file' = move old file' RETURN

E_x_a_m_p_l_e_
hidetextreg = move textreg

RCSL No. 42-i 0945\f

F_ 7.2 System Shutdown for the RC 6000 System

This procedure can only be carried out at the main console. The
system shutdown procedure consists of removing all processes (if
they have not already been removed under the process removal
procedure described in Section 5.3).

Process Removal at the main console.

1) Type:
ESC S RETURN
The text "att" will appear on the console display.

2) Type:
LIST RETURN
If the text "READY" appears then go to Section 7.2.1.

If the text
process name'number'number'number'
process name'number'number'number'
.
.
.
etc.,
appears,

3) Type:
ESC S RETURN
The text "att" will appear on the console display.

4) Type:
proc process name' remove RETURN
The following text till now appear on the console display:
ready
to process name'

5) Repeat until processes have been removed. Then go to Section
7.2.1.

RCSL No. 42-i 0946\f

I_N_D_H_O_L_D_S_F_O_R_T_E_G_N_E_L_S_E_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _S_I_D_E_ _

1. INTRODUKTION .......................................... 1

2. BETJENING ............................................. 2
2.1 Terminal ......................................... 2
2.1.1 Betjeningspanel ........................... 2
2.1.2 Skrivehovedet ............................. 7
2.1.3 Papirtransport ............................ 8
2.1.4 Farvebånd ................................. 9
2.2 Tastatur ......................................... 9
2.2.1 Tegntaster ................................ 10
2.2.2 Programtaster ............................. 10
2.2.3 Terminaltaster ............................ 11

3. BETJENINGSVEJLEDNING .................................. 13
3.1 Isætning af papir ................................ 13
3.2 Margenindstilling ................................ 15
3.3 Advarselssignaler ................................ 15

4. SUPPLERENDE INFORMATION ............................... 16
4.1 Installation ..................................... 16
4.2 Papirformat ...................................... 17
4.3 Skift af farvebånd ............................... 17
4.4 Fejlfinding ...................................... 18
4.5 Vedligeholdelse .................................. 21

ii
\f

F_ 1_._ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_K_T_I_O_N_ 1.

Figur 1: Skriveterminal med tastatur.

Skriveterminalens overdel kan åbnes ved at trykke på udløserne.
Overdelen er hængslet bagtil og kan vippes bagover. Når overdelen
er åbnet, kan man se skrivehovedet (jf. 2.1.2) og papirtranspor-
ten (jf. 2.1.3); yderligere ses farvebåndskassetten (jf. 2.1.4)
til højre for skrivehovedet.

Skriveterminalen (som for nemheds skyld er kaldt >terminalen> i
det følgende) installeres på et bord og en papirføring sættes
bagpå terminalen (jf. 4.1).
\f

F_ 2_._ _ _ _ _ _ _ _ _B_E_T_J_E_N_I_N_G_ 2.

I det følgende beskrives de forskellige funktioner som operatøren
skal betjene. Se også vejledningen i betjening, som er beskrevet
senere.

2_._1_ _ _ _ _ _ _ _T_e_r_m_i_n_a_l_2.1

2_._1_._1_ _ _ _ _ _B_e_t_j_e_n_i_n_g_s_p_a_n_e_l_ 2.1.1

POWER ON/OFF - en hovedafbryder findes på
(ikke vist) terminalens bagside. Hvis
terminalen anvendes som kon-
sol, kan den forblive tændt
efter første betjening. Kon-
sollen vil så blive tændt/
slukket, når systemet tændes/
slukkes.

POWER ON indikeres med en af
indikatorerne: LOCAL, DATA
eller TERM READY.

Figur 2: Betjeningspanel.

LOCAL - når indikatoren er tændt, er
tastekontakt/indikator terminalen i lokal mode; ter-
minalen kan betjenes, men kan
ikke modtage eller sende tegn.
\f

Lokal mode kobles ind,
a: når LOCAL tasten trykkes ned,
b: når PRINTER TEST aktiveres,
c: når terminalens overdel åbnes,
d: når der er modtaget 8 linie-
skiftsignaler i data mode
efter et advarselssignal om
papir slut.

Lokal mode kobles ud,
a: når advarselsårsagen elimineres,
b: efter indkobling af data mode.

DATA - når indikatoren er tændt, er
indikator terminalen i data mode; terminalen
er on-line og i stand til at
modtage og sende tegn. Terminalen
kobles automatisk i data mode,
styret fra systemet.

Data mode kobles ud,
a: når der er modtaget 8 linie-
skiftsignaler efter et advar-
selssignal om papir slut,
b: når datasignaler fra systemet
går tabt,
c: når PRINTER TEST aktiveres,
d: når LOCAL tasten aktiveres.

Indikatoren kan eventuelt blinke,
hvilket antyder kortvarige for-
styrrelser i datatransmissionen.

DATA tasten bør ikke aktiveres.

TERM READY - denne indikator tændes eventuelt
(system bestemt) dermed vises, at
terminalen er klar til drift.
\f

Under betjening skal enten lokal
eller data modeindikatoren være
tændt i stedet.

TERM READY tasten bør ikke aktive-
res.

INTRPT (I_n_t_err_up_t_) - når indikatoren er tændt, er
transmissionen fra systemet blevet
afbrudt. Denne funktion er helt
systemafhængig.

INTRPT tasten bør aldrig aktiveres
af operatøren.

ALARM - når indikatoren er tændt, fore-
indikator kommer en af følgende situationer,
a: advarsel om papir slut (dette
er et forhåndssignal, der bety-
der, at 8 linieskiftsignaler fra
nu brydes data mode - og 13
linier fra nu vil der ikke
længere være papir ved skrive-
hovedet),
b: advarsel om åben overdel,
c: advarsel om indkobling af
PRINTER TEST.

Advarselssignalet elimineres,
a: når der sættes mere papir i
terminalen,
b: når overdelen lukkes,
c: når PRINTER TEST kobles ud.
\f

Bell-signal - bell-signalet (klokke) lyder, når
et tegn tastes ind syv positioner
før højre margen, og igen når et
tegn tastes ind i samme position
som højre margen.

PRINTER TEST - når tasten trykkes ned, startes
tastekontakt en selvtest af terminalens funk-
tioner.

Testen består i: vedvarende ud-
skrivning af tegnsæt (94 tegn),
aktivering af bell signal, samt
automatisk vogn-retur og linie-
skift. Alt inden for de indstil-
lede margenpositioner.

Testen udføres kun lokalt og uaf-
hængigt af systemet; terminalen går
i lokal mode og ALARM indikatoren
tændes.

Testen stoppes ved at trykke tasten
ned n gang mere (udløser den selv-
låsende taste).

PARITY - den korrekte stilling afhænger af
tastekontakt systemet.

Når tasten står i øverste position
(PARITY ON - UP), vil tegn med
forkert (ulige) paritet blive ud-
skrevet som tegnet > >.
\f

Når tasten står i nederste position
(PARITY OFF - DN), vil tegn med
forkert (ulige) paritet blive
udskrevet, respektive funktionen
blive udført, forudsat det er mu-
ligt.

Ved aktivering af tasten låser
denne skiftevis i nederste stil-
ling.

DUPLEX - den korrekte stilling afhænger af
tastekontakt systemet.

Når tasten står i øverste stilling
(DUPLEX HALF - UP), vil alle data,
der sendes og modtages, blive ud-
skrevet. Tastaturet vil være inak-
tivt, medens der modtages data.

Når tasten står i nederste stil-
ling (DUPLEX FULL - DN), kan der
sendes data fra terminalen samtidig
med modtagelse af data fra syste-
met.

Ved aktivering af tasten låser den-
ne skiftevis i nederste stilling.

CPS - denne taste sættes i den stilling,
tastekontakt der svarer til transmissionshastig-
heden bestemt af systemet.

Når tasten står i øverste stilling
(CPS 30 - UP), sættes hastigheden
til 30 cps.
\f

Når tasten står i nederste stilling
(CPS 10 - DN), sættes hastigheden
til 10 cps.

Ved aktivering af tasten låses den-
ne skiftevis i nederste stilling.

2_._1_._2_ _ _ _ _ _S_k_r_i_v_e_h_o_v_e_d_e_t_ 2.1.2

Figur 3: Skrivehovedet.

Ved skift af farvebånd skal skrivehovedet frigøres med låsehånd-
taget (håndtaget bevæges væk fra skrivevalsen).

Margenpositionerne, inden for hvilke skrivehovedet arbejder, ind-
stilles i henhold til beskrivelsen under betjeningsvejledningen
(med henvisning til pkt. 2.2.2).

Næste skriveposition (og den position, hvor en margen bliver sat)
vises med en forsinkelse på 1 sekund. Positionsmarkøren er vist i
figur 4.

Selve skrivehovedet skal ikke justeres af operatøren.
\f

Figur 4: Positionsskala, positionsmarkør.

2_._1_._3_ _ _ _ _ _P_a_p_i_r_t_r_a_n_s_p_o_r_t_ 2.1.3

Figur 5: Papirtransport.

Papiret fremføres ved hjælp af kanthuller. Papirfremføringen sker
med linieskift-ordren eller manuelt ved hjælp af skrivevalsens
håndhjul (der findes et håndhjul på hver side af terminalen).

Papirfølerarmen (øvre venstre hjørne) kan betjenes uden at åbne
overdelen. Den vippes op, når der isættes nyt papir, tilsvarende
gælder papiradskiller og papirbom.

2_._1_._4_ _ _ _ _ _F_a_r_v_e_b_å_n_d_ 2.1.4

Figur 6: Farvebånd.

Farvebåndet er af kassettetypen. Kassetten sidder på et beslag i
højre side; den holdes på plads af magnetlåse. En vejledning i
skift af farvebånd findes på indersiden af overdelen, jf. også
4.3.

2_._2_ _ _ _ _ _ _ _T_a_s_t_a_t_u_r_ 2.2

Der findes 3 tastetyper:

- tegntaster (2.2.1)
- programtaster (2.2.2)
- terminaltaster (2.2.3)

Bemærk: Beskrivelsen i det følgende omhandler kun de faciliteter,
der er fælles for alle tastaturer uanset alfabet og øvrigt
ekstraudstyr.

2_._2_._1_ _ _ _ _ _T_e_g_n_t_a_s_t_e_r_ 2.2.1

Når en af disse taster aktiveres, transmitteres det pågældende
tegn til systemet, hvis terminalen er i data mode - ellers til
lokal udskrivning. Tegnet der sendes, svarer til indgraveringen
på tasten - jævnfør en traditionel skrivemaskine.

Tegntasterne virker på samme måde, hvadenten terminalen er i
lokal eller data mode. De mnemotekniske indgraveringer på de al-
fabetiske taster er til brug i sammenhæng med CTRL tasten (jf.
2.2.2).

2_._2_._2_ _ _ _ _ _P_r_o_g_r_a_m_t_a_s_t_e_r_ 2.2.2

Det er vigtigt at mærke sig, at funktionen af disse taster kan
være forskellig fra system til system. Konkret information om
virkemåde og brug af disse taster kan findes i de publikationer,
der vedrører programmelsystemer og deres anvendelse.

ESC (E_s_c_ape)
LINE FEED
RETURN - funktion programmelbestemt.
BACK SPACE
DELETE

CTRL - bruges til at sende styrekoder, der
ikke er defineret med egen taste.

CTRL holdes nedtrykket og samtidig
trykkes en alfanumerisk taste ned -
en styrekode svarende til den på-
gældende alfanumeriske taste trans-
miteres så. Hvilket alfanumerisk
tegn, der i en given situation skal
bruges og hvilken funktion der ud-
løses, er programmelbestemt. De
mnemotekniske indgraveringer omtalt
under 2.1.2, giver en antydning
vedrørende funktion.
\f

De anvendelser, der er beskrevet i det følgende, kan benyttes med
samme virkning uagtet programmelsystem (virker både i lokal og
data mode):

ESC l - sæt venstre margen (trykkes ESC ned
efterfulgt af et tegn fra "nedre
tegnsæt" - her et lille L - udføres
den funktion, der beskrives - her
sættes venstre margen).
ESC r - sæt højre margen.
ESC x - slet højre og venstre margen.
ESC m - frigør højre og venstre margen.
ESC = - slet begge loop-back modes.
ESC w - vognretur og linieskift.

CTRL/SUB - udskriver .
CTRL/BEL - udløser bell signal (klokke).
CTRL/BS - udfør backspace.
CTRL/RETURN - som ESC w, men der sendes intet
signal on-line i data mode.

2_._2_._3_ _ _ _ _ _T_e_r_m_i_n_a_l_t_a_s_t_e_r_ 2.2.3

Disse taster bruges til almindelige skrivemaskinefunktioner; de
enkelte taster og deres funktioner er:

SHIFT - bruges sammen med alfabetiske og
numeriske taster; foranlediger
skift til store bogstaver, respek-
tive tegn indeholdt i det "øvre
tegnsæt". SHIFT tasten udløser ikke
en eventuel CAPS LOCK.

CAPS LOCK - tilsvarende SHIFT, men kun på
alfabetiske taster. Selvlåsende,
udløses ved at trykke n gang
mere.
\f

REPT (R_e_peat_) - nedtrykkes denne taste, vil et
tegn, der aktiveres dernæst, blive
gentaget sålænge REPT holdes nede.

Terminaltasterne virker på samme måde, hvadenten terminalen er i
lokal eller data mode.

F_ 3_._ _ _ _ _ _ _ _ _B_E_T_J_E_N_I_N_G_S_V_E_J_L_E_D_N_I_N_G_ 3.

Når der tændes for terminalen, vil skrivehovedet bevæge sig ud i
yderste venstre position og tidligere satte margenpositioner
bliver slettet, hvorefter margenpositionerne vil være 1 og 131.

Umiddelbart når terminalen tændes, lyser TERM READY indikatoren
(afhængigt af system); når betjeningen påbegyndes (kommunika-
tionslinie etableret og system driftsklart), skal DATA indika-
toren lyse. Terminalen kan også arbejde i lokal mode - i så fald
aktiveres LOCAL tastekontakten, men kontrollr først, at der ikke
samtidig modtages meddelelser på terminalen.

3_._1_ _ _ _ _ _ _ _I_s_æ_t_n_i_n_g_ _a_f_ _p_a_p_i_r_ 3.1

Papiret sættes i på sammen måde som på en almindelig skrivema-
skine - dog er papiret til brug på terminalen forsynet med kant-
huller.

Papiret kan isættes uden at åbne overdelen og uden at strømmen
afbrydes. For at undgå tab af data, bør man imidlertid kun skifte
papir, når terminalen er i lokal mode. Skrivehovedet centreres og
en eventuel papirrest fjernes, hvorefter papir isættes på følg-
ende måde (se også illustrationen næste side):

1) Vip papirfølerarmen op. Løft bagkanten af papiradskilleren og
vip den forover.

2) Fold første papirformat bagover (om ønsket) og før derefter
papiret indover papirføringen og nedenunder papiradskilleren.
Kanthullerne i begge sider rettes op, så de griber fat i frem-
føringstænderne på skrivevalsen. Papiret føres nedenunder
skrivevalsen. Papiradskilleren vippes tilbage.
\f

3) Papiret føres frem til papirbommen ved hjælp af skrivevalsens
håndhjul.

4) Løft papirbommen (derved vippes papirfølerarmen automatisk
tilbage). Før papiret under plaststangen og luk stangen ned-
over papiret.

Papiret kan nu føres frem til den ønskede position ved hjælp
af CTRL/RETURN tasterne. Når strømmen er afbrudt, er
CTRL/RETURN inaktiv og skrivevalsen drejes med håndhjulet.

Papiret kan fødes direkte fra den æske, hvori det leveres. Når
der anvendes en papirholder bagpå, kan en begrænset mængde papir-
formater placeres i holderen. Papiret skal altid ledes via papir-
føringen (trådgitteret), for at sikre en effektiv luftkøling af
terminalen (udsparring under trådgitter).

3_._2_ _ _ _ _ _ _ _M_a_r_g_e_n_i_n_d_s_t_i_l_l_i_n_g_ 3.2

Margenpositionerne kan indstilles både i lokal og data mode, idet
escape-procedurene i pkt. 2.2.2 benyttes. Margenen sættes i den
position, der angives af positionsmarkøren (vent ca. 1 sekund
efter sidste indtastning for at få den rigtige positionsangivel-
se).

For at kunne ændre en af margenpositionerne udefter, skal begge
marginer slettes og derefter sættes påny.

3_._3_ _ _ _ _ _ _ _A_d_v_a_r_s_e_l_s_s_i_g_n_a_l_e_r_ 3.3

De situationer, hvor der udløses advarselssignaler, er beskrevet
under pkt 2.1.1.

F_ 4_._ _ _ _ _ _ _ _ _S_U_P_P_L_E_R_E_N_D_E_ _I_N_F_O_R_M_A_T_I_O_N_ 4.

4_._1_ _ _ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ 4.1

Når terminalen installeres, benyt da følgende kontrolpunkter:

Figur 7: Terminalens bagside.

. terminalbord, korrekt arbejdshøjde.

. tilslutning af datakabel (2 skruer).

. tilslutning af strømkabel.

. montering af papirføring (trådgitter skal altid være på plads
for at sikre en effektiv kølingsmulighed).

. en papirholder kan desuden monteres, enten fastgjort på
papirføringens trådgitter eller i udsparringerne i kabinettet
(afhænger af papirholdertype).

4_._2_ _ _ _ _ _ _ _P_a_p_i_r_f_o_r_m_a_t_ 4.2

Papiret til terminalprinteren skal være 12-tommer bredt og for-
synet med kanthuller. Flerlagspapir må højst bestå af orginal
plus 2 kopigennemslag. Mest almideligt benyttes foldet enkelt-
lagspapir af størrelsen 11-tommer x 8 1/2-tommer (efter afrivning
af kanter med fremføringshuller). Dette 15 lb. basispapir kan
leveres fra RC.

4_._3_ _ _ _ _ _ _ _S_k_i_f_t_ _a_f_ _f_a_r_v_e_b_å_n_d_ 4.3

Kun originale farvebåndskassetter beregnet for terminalprinteren
bør anvendes. Farvebåndskassetter kan leveres fra RC.

Farvebåndet skal altid skiftes, når det bliver frynset i kanter-
ne, eller når det iøvrigt er slidt (sværtning ikke kraftig nok).
Pånær de første par farvebånd, bør hvert farvebånd normalt kunne
bruges til mindst 3 mill. tegn.

Før farvebåndet skiftes, centreres skrivehovedet, terminalen kob-
les i lokal mode (det er ikke nødvendigt at afbryde for strømmen)
og overdelen åbnes.

Gå frem på denne måde:

1. Fjern det gamle farvebånd fra terminalen. Kassetten løftes
fri af beslaget og båndet fjernes fra rullerne.

2. Frigør skrivehovedet ved at trække låsearmen helt frem foran
(væk fra skrivevalsen).

3. Det nye farvebånd føres omkring rullerne i venstre side.

4. Kassetten trækkes mod højre side og farvebåndet føres mellem
skrivehovedet og farvebåndsføringerne.

5. Sæt kassetten fast i beslaget i højre side (den holdes fast
med magnetlåse).

6. Skub skrivehovedet ind mod farvebåndet (og skrivevalsen) og
lås skrivehovedet med låsearmen.

Kontrollr om farvebåndet er ført korrekt omkring alle fire rul-
ler, før overdelen lukkes.

4_._4_ _ _ _ _ _ _ _F_e_j_l_f_i_n_d_i_n_g_

Ved hjælp af følgende spørgsmål vil det ofte være muligt at af-
hjælpe elementære fejl, eventuelt klarlægge fejlårsagen mere kon-
kret forud for et servicekald. Under alle omstændigheder skal man
dog følge de forskrifter, der lokalt er gældende.
\f

Start med sprøgsmål 1) og fortsæt i henhold til JA/NEJ svarene:

1) Er en af indikatorene
LOCAL, DATA eller
TERM READY tændt?

- JA: gå til 2)
- NEJ: a) Kontrollr om termi-
nalen er tændt.

b) Kontrollr om strøm-
kabel er tilsluttet.

c) Kontrollr strømfor-
syning (stikkontakt,
øvrig udstyr i orden
osv.).

d) Lokal fejl i udstyr;
tilkald en service-
tekniker.

2) Udskrives tegn-
sættet korrekt,
når PRINTER TEST
tasten aktiveres?

- JA: gå til 4)
- NEJ: gå til 3)

3) Er den røde indikator
på strømforsyningsmo-
dulet tændt (ses gen-
nem udsparring, 6.
åbning fra venstre)?

- JA: Lokal fejl i terminal-
printer; tilkald en
servicetekniker. \f

- NEJ: Lokal fejl i strømfor-
syningsmodul; tilkald
en servicetekniker.

4) Reagerer skrivemo-
dulet rigtigt på
tasteoperationer
(lokal mode)?

- JA: gå til 5)
- NEJ: Lokal fejl i tastatur;
tilkald en service-
tekniker.

5) Er terminalen
koblet direkte
til systemet
(anvendt som
konsol)?

- JA: gå til 7)
- NEJ: gå til 6)

6) Lyser DATA
indikatoren?

- JA: gå til 7)
- NEJ: a) Kontrollr tilslut-
ning af datakabel.

b) Kontrollr om system
er driftsklart og
on-line.

c) gå til 7).

7) Sendes og modtages
meddelelser korrekt
i data mode?
\f

- JA: gå til 8)
- NEJ: a) Kontrollr om DUPLEX
og PARITY tasterne
er indstillet for-
skriftsmæssigt.

b) Kontrollr om INTRPT
tasten er udkoblet
(øverste stilling).

c) Fejl i on-line for-
bindelse; tilkald en
servicetekniker.

8) Har det ikke været
muligt at lokaliseres
fejlen med spørgsmålene
så vidt - og gør fejlen
sig stadig gældende?

- JA: Fejlårsagen lader sig
ikke lokalisere umid-
delbart; tilkald en
servicetekniker.
- NEJ: Fortsæt arbejdet; ind-
bert som midlertidig
fejl ved næste service-
kald.

4_._5_ _ _ _ _ _ _ _V_e_d_l_i_g_e_h_o_l_d_e_l_s_e_ 4.5

1_ _g_a_n_g_ _h_v_e_r_ _m_å_n_e_d_ _(_f_o_r_ _h_v_e_r_ _2_4_0_ _d_r_i_f_t_s_t_i_m_e_r_)_

Rengør området omkring skrivehovedet og farvebåndsføringen; brug
en blød pensel samt støvsuger. \f

F_i_g_u_r_t_e_k_s_t_ _t_i_l_ _4_2_-_i_1_4_6_5_:

Figur 1: Overdel Papirføring

Tastatur

Udløser

Betjeningspanel

Papiradskiller

Papirtransport

Skrivehoved

Farvebånd

Illustration
side 17 : Afrivningskant

Papiradskiller

Papirbom
(plaststang)

Håndhjul til
skrivevalse

Skrivevalse

Illustration
side 20 : Farvebånd

Udløser
\f

Illustration
side 21 : Farvebåndsrute

Illustration
side 22 : udsparring

Tekst side 5: Bemærk: Hvis margenpositionerne er
indstillet til færre end 96 tegn,
overspringes et tegn (skrives ikke)
hver gang en ny linie starter und-
tagen på den linie, hvor en ny ud-
skrivningscyklus begynder.

side 5: Bemærk: Terminalen er indstillet
til at generere og kontrollere lige
paritet.

side 6: Bemærk: En lokalt aktiveret vogn-
retur/linieskift vil ikke blive
udført lokalt, når terminalen er i
full-duplex mode.

side 12: Bemærk: De mnemotekniske indgrave-
ringer er ikke øvre tegnsæt.

side 12: Bemærk: Gentagelseshastigheden
følger indstillingen 10 eller 30
cps on-line og er cirka 50 cps
lokalt.
\f

«eof»

DataMuseum.dk

CP/M

⟦41a813f7a⟧ TextFile

Derivation

TextFile