⟦916aecb9b⟧

TextFileVerbose

>fo RCSL 52-AA 1026~MULTI RC8000 DQ SYSTEM~OP. GUIDE
>ul
INTRODUCTION

The main purpose of this operating guide is to be a description of
the DQ-system installed at Michigan Bell Telephone Company, spring 1981.

The operating guide describes a multi RC8000 configuration with 3
RC8000's sharing one RC3503 Front End Processor, which is able to
handle all inquiries from up to 4 bureaus each holding up to 72
DQ terminals. If one CPU system (e.g. RC8000) is to be disconnected
for servicing or data base updating, the other CPU systems will be
able to handle all the transactions.

>ne 35
>sp 33
>fg Central site configuration

As shown above the RC8000s may share an RC3600 I/O device controller, too.
To the RC3600 above is attached a console, a magnetic tape station,
and a line printer.

The FEP is duplicated, i.e. a hot standby machine can take over, using
an I/O switch.

If one bureau is local, i.e. placed at central site,
this bureau may use the two GCI-lines as the
connection to FEP.

If all bureaus are non-local,
they will have to be connected by one pair of BSC-lines each.

NOTE: The FEP-system is able to take care of at most
4 bureaus at the same time.

Connected to the FEP are
Battery Backup Memory, a local Ontel and a LAM multiplexer.
LAM holds 3 main consoles (one console per RC8000), a status printer
and 0 to 4 programming terminals.

Each bureau is configurated as scheduled on figure 2.

The Remote End machine, RC3503 CON (Concentrator) holds itself
up to 20 ONTELS. Furthermore it has got GCI-lines for two RC3503 TCCs
(Terminal Cluster Controllers) which holds up to 26 ONTEL DQ-terminals each.
The RC3503 CON is duplicated (a hot standby machine can take over).
>ne 26
>sp 24
>fg Bureau Configuration

Everywhere - both on central site and on the bureaus - RC3503's can be
replaced by RC3500 machines with 32 I/O-channels.
The software is working identically in the two machines.

RC3500 should not be used as FEP, though, for two reasons:

>in 3
>ti-3
1.@The FEP channel layout leaves no room for ASL-connection
(refer to Release Information, chapter 4).
>ti-3
2.@In a fully extended cluster, the CPU-load is too heavy for a RC3500.

>in-3
In the Michigan Bell system 23 bureaus are used. Thus 6 CPU complexes
(or "clusters") are needed. The exact configuration scheme of the
Michigan Bell DQ system for all 6 clusters is given in Appendix D,
which is taken from RADRU/C.
>a1 POWER-ON PROCEDURES
>a2 Central site
The central site part of the single cluster may be started up by
powering-on the separate parts in this order:

>in 4
>ti -4
STEP 1: TURN ON THE RC8000s

Operator control is exercised from a panel containing:

 - a POWER-key (the main circuit breaker)
 - three indicator lamps, marked POWER OK,
   RUN, and AUTOLOAD, and
 - an AUTOLOAD button.

To start the RC8000 you turn the main circuit breaker of each one to the
ON position. Wait until POWER OK lights (this may take up to 30 seconds).

>ti-4
STEP 2: TURN ON THE RC3600 (if any)

Normally the RC3600 (also known as the RC8301) will be fully powered from
the RC8000a. In case it has got its own power supply, F19 Power and
Autoload panel the power-up procedure will be as follows:

 1. Turn on the main power supply.
 2. Turn the power key to the extreme
    clock-wise position, pushing in, and
    then turning the key to its extreme
    counterclockwise position.
 3. The text POWER will appear in the RC3600
    console.

>ti-4
STEP 3: TURN ON THE RC3503 FEP

RC3503 is started by turning the POWER key to the ON
position.

The hot standby machine should be turned on, too.

>ne 4
>ti-4
STEP 4: TURN ON THE MAIN CONSOLES

The 3 main consoles on the RC3503 FEP are all turned on.

>ti-4
STEP 5: TURN ON THE DISCS

All the discs on all RC8000s are turned on.
>in-4

>a2 Bureaus
On the single bureau the power-on procedure
for the remote end system is this

STEP 1: TURN ON THE RC3500/RC3503 CON

STEP 2: TURN ON THE RC3500/RC3503 TCC's

The procedure of turning on these machines is the same as for the
RC3503 FEP above.

>a1 AUTOLOADING PROCEDURES
>a2 RC8000
>a3 Autoloading from disc
>ul
Prerequisites

 - Power must be on the main console 
   and on the system discs.

>ul
Procedure

 - Press the AUTOLOAD button on the RC8000.
 - Initialize the date and time on the main console.

>a3 Autoloading from magnetic tape
(N.B.: The RC3600 will be autoloaded at the same time,
if switch on RC3600 is set to enable).

>ul
Prerequisites

 - The console on the RC3600 must be on-line.

>ul
Procedures

 - Set the switch on the FPA801 to AUTOLOAD ENABLED.
 - Set the switch on the FPA702 to AUTOLOAD ENABLED.
 - Mount the "mtload" magnetic tape on the tape station.
 - Set the switches 0, 11, 12 on the RC3600.
 - Remove plug 0 on the system disc.
 - Press the AUTOLOAD button on the RC8000.
 - Wait for the autoload function has been completed
   (the text ">S" will then appear on the main console).
 - If you are autoloading RC8000a you now type in
   INT LOADA. If you are autoloading RC8000b or
   RC8000c, type in INT LOADB or INT LOADC
   (see RCSL NO. 31-D463,
   RC8000 Operating Guide, section 3.2).
 - Replace plug 0 on the system disc.
 - Initialize the date and time on the main console.
 - Set the switch on the FPA702 to AUTOLOAD DISABLED.
 - Set the switch on the FPA801 to AUTOLOAD DISABLED.

>a2 RC3600
As mentioned in the previous section the RC3600 will be autoloaded
automatically by the procedure used to autoload the RC8000 from
magnetic tape. You have got two other possibilities
of autoloading the RC3600.

>a3 Autoload from RC8000 disc
>ul
Prerequisites:
A running RC8000.

>ul
Procedure

 - Set the following RC3600 switches:

   0, 10, 13, 14@@@@ (if RC8000a is used)
   0, 10, 11, 12, 13 (if RC8000b is used)
   0, 10, 11, 13@@@@ (if RC8000c is used)

 - Set up an "all" process and key in

   main36001 = autoload boot3600 (if RC8000a), or
   main36002 = autoload boot3600 (if RC8000b), or
   main36003 = autoload boot3600 (if RC8000c) 

   on the main console.

 - Set the switch on the FPA702 to AUTOLOAD DISABLED.

>a3 Autoload from magnetic tape
>ul
Prerequisites

You will need either another RC3600 NOVA
or a Technical Panel TCP701
or a F19 Feature.

>ul
Procedure

 - Mount the "mtload" magnetic tape on the
   tape station.
 - Set the switches 0, 11, 12 on the RC3600
   you want to autoload.
 - Press the AUTOLOAD button on the RC3600.
 - Wait for the reply ">S" on the RC3600
   console.
 - Type in INT SYS.

>a2 RC3500 and RC3503
>a3 Autoloading of FEP via FPA100
>ul
Prerequisites

A running RC8000. It is assumed that the FEP is receiving data via:

 - channel 3  (from RC8000a)
 - channel 5  (from RC8000b)
 - channel 7  (from RC8000c)

>ul
Procedure

 - Place the key on the RC3500/RC3503 in the
   ON position.
    
 - If RC3500: Push the STOP button downwards
   and the EX button upwards.
  
 - If RC3500: Set the switches so that

   bit   0-1   is 1
   bit   2-5   is 0
   bit   6-10  indicate interrupt no.
   bit  11-15  indicate device no.

>in 3
Interrupt no. and device no. both equal the number of the I/O-channel
used on the FEP for receiving data from the RC8000. For the Michigan Bell
system the I/O-channels are 3, 5 and 7 for RC8000a, RC8000b, and
RC8000c, respectively.
 
>ne 5
>ul
If@RC3503:
Set the switches so that
>sp 1
>in-1
 bit   0-1   is 1
 bit   2-8   is 0
 bit   9-15  indicate interrupt/device no
>in 1

This means, that the 4 rotary switches must be set to
C003 if RC8000a, C005 if RC8000b and C007 if RC8000c is used.
   
The debug mode switch can be set to 4,
indicating 300 bps, run test, no loop
(refer to RC3503 Reference Manual, section 10.1.1).
>in-3

 - Push the AUTO button.
   On the RC3503 FEP you have to turn the LOCK button
   to the right at the same time.

   If RC3500 for some reason is used as FEP,
   you should note that the
   interrupt level lamps must constantly
   indicate the interrupt number in question
   before proceeding.
 
 - Set up an "all" process using the RC3600
   console and type in

      main3500 = autoload boot3500

 - Turn the key on the RC3500/RC3503 FEP to the
   LOCK position.

>a3 Autoload of FEP from RC8000 Disc
The FEP will be autoloaded with the RC8000,
if FEP is made ready for autoload
in the manner specified in the previous section.

>ul
Prerequisites

 - The 3500 console must be online.
>a3 Autoloading from paper tape
RC3500/RC3503 can be autoloaded from paper tape using a RC500
paper Tape Reader.

>ul
Procedure

 - Power up the paper tape reader.
 - Set the reader in the LOAD position.
 - Push RESET on the reader.
 - Place key in the ON position.
 - If RC3500: push STOP button downwards
   and EX button upwards.
 - Using I/O-channel 8 on the RC3500/RC3503
   set the switches to:

>ne 7
                    int. no  device no

       0 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0   (RC3500)

                        int./device no.

       0 1 1 0 0 0 0 0 0 0 0 0 1 0 0 0   (RC3503)

 (pos. 0 1 2 . . . . . . . . . . . . 15)

   which means rotary switches are set to .
   6 0 0 8  on RC3503.

 - Activate the AUTO button (see section 2.3.1)
 - Push RESET on the reader.
 - Place the program tape in the reader
   (upside down).
 - Set the reader in the RUN position.
 - Push READ on the reader.
 - The paper tape will be loaded, and the
   system starts automatically.
 - If the paper tape after loading remains
   in the reader, the RESET button on the
   reader must be pushed repeatedly until
   the paper tape is released from the
   reader.
 - Place the key on the RC3500/RC3503 in
   the LOCK-position, and the key may be
   removed.

>a3 Autoloading RC3500 from ASL prom
>ul
Prerequisites

The 
>ul
internal
switches of the RC3500 must be set to

                  int. no  device no

     0 1 1 0 0 0 1 1 1 1 0 1 1 1 1 0

(pos 0 1 2 . . . . . . . . . . . . 15)

on both the FEP's and
on all remote RC3500's by the customer's engineer.

>ul
Procedure

 - Turn the key on the RC3500 to the OFF-position.
 - Turn the key on the RC3500 to the LOCK-position.

>a3 Autoloading RC3503 from TES201/202
TES201/202 is also known as the Image Load module.

Set the switches to 5, 1, 0,  0, if module no is 11
(hexadecimal) and program index is 0.

>ul
Procedure:
 - Turn the key on the RC3503 to the OFF position.
 - Turn the key on the RC3503 to the LOCK position.

Refer to General Information for RC3503
Standard Autoload, chapter 6.
>a1 STANDARD LINKS
>np
Links may be created from the FEP programming terminals by the
following method:

 - Depress CTRL and G together.
 - Enter the local command, e.g. "select RC8000a".

If succeeding in doing so, the message LINK CREATED will appear
on the terminal. If not, one of the two messages HOST UNKNOWN or COMMAND
UNKNOWN will appear, as appropriate.

>a1 STANDARD MESSAGES AND ERROR PROCEDURES
>a2 Messages on the RC3600 console
>a3 Messages concerning FPA-lines
When a communication line between RC3600 and a RC8000 is connected
or disconnected a HOST message will appear at the main console.

Refer to RC NET General Information for the concepts host, jobhost,
device host, and link.

>ul
Connection@message@is:

 HOST <hostid> READY

>ul
Disconnection@message
is

 HOST <hostid> DISCONNECTED <errorcode>

Both messages may be preceeded by the text:

 >NCPWR

<hostid> is the host identification of the RC8000 in RC NET. The
value is an option in the RC8000 Monitor.

<errorcode> is an octal number giving the reason for the disconnection:

>ne 16
Error code@@Reason for disconnection
  
 001        Status byte from RC8000 state a
            parity error or wrong block number.
 002        Parity error in received block from RC8000.
 003        Status timeout, disconnect or receiver
            not ready on the transmitter.
            Or statusbyte from RC8000 state an error
            in blocklength.
 004        Status illegal or reset from receiver
            or power lost during receiving a datablock.
 005        Power failure (RC3600).
 006        Master clear header received from RC8000.
 011        Dump request refused.
 013        Status illegal or error in blocklength
            or parity error or timeout.

If the last message is HOST <hostid> READY,
you can continue,
otherwise call a service technician.
>a3 Messages concerning link to RC8000
When a link is created or removed a message will appear at the main
console.

Creation message:

 CONNECTED TO <hostname>

where <hostname> is a name associated with <hostid> or a '*' if no name
is associated.

Removing message:

 DISCONNECTED CAUSED BY <cause>

where <cause> may be one of these:

 JOB HOST DOWN
 JOB HOST RELEASE
 JOB HOST LOCAL DEVICE
 JOB HOST NO RESOURCES
 JOB HOST TIMEOUT
 REMOVE COMMAND

If the last message is a creation message you can continue.

>a3 Editing commands on the RC822
RC822 is the name of the programming terminals,
connected to the FEP.

A complete line can be written on the terminal display without any action
before the RETURN-key is depressed. It is therefore possible to correct
typing errors before the RETURN-key is depressed. Pressing the &-key
twice, will delete the two last characters etc. Pressing the %-key
will delete the complete line.

E.g.:
        the line:
          abcd&efgh&&
        will be perceived as:
          abcef

>ne 5
E.g.:
        the line:
          abcdefghijk%
        will be perceived as a blank line

There is
>ul
one
exception to the above mentioned - namely if a typing error occurs
in the command INT LOAD. In this case you can delete the last
character by depressing the RUBOUT-key.
>a2 Messages on the RC3500 Console
The line status between the RC3502 Front End and the RC8000 Host
is given on the 3500-console
in a status_word in binary form:

    15                             0
     1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

means FPA100 receiver disconnected.

    15               7 6           0
     1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0

means MASTER CLEAR received.

>ne 9
Other statuswords than these two should be under_stood this way:

    15           9 8 7 6           0



       RC8000    Software  Hardware
       answer    status    status
       byte

>ne 9
>ul
Hardware errors

>nf
1<0  Parity error
1<1  Reset received
1<2  Disconnected
1<3  Autoload received
1<4  Receive block end missing
1<5  Character time out
1<6  Transmit block end missing
>fi

>ne 4
>ul
Software errors

>nf
1<7  Software time out
1<8  Block no. error
>fi

>ne 7
>ul
Answer byte from RC8000

>nf
1<9  Parity error
1<10 Block length error
1<11 Wait
2<11 Skip
3<11 Reject
>fi

>a2 Messages on statusprinter
Just after reset of the FEP the message

    *** system started ***

is displayed on the statusprinter.

During the working phase,
status messages of different kinds are displayed on the
statusprinter.
If Battery Backup Memory (BBM) is included,
these messages are all equipped with the current time.

The COM35 module in the Front End Machine can print out
the following messages on the statusprinter:

>ne 8
   HOST <host-no> DISCONNECTED
   HOST <host-no> TIMED OUT
   HOST <host-no> RECOVERING
   HOST <host-no> OPEN
   NO HOST OPEN
   HOST <host-no> CLOSED
   SERIALNO. SET
   BBM STATUS <bbm100-status>

<host-no> is either A, B or C in a cluster with 3 RC8000's.

<bbm100-status> indicates the status of the BBM:

>ne 5
 status  bit mask    indicates

   00    all 0's     BBM ok
   01    1 shift 0   power error or disconnected
   04    1 shift 2   battery alarm

If the BBM is excluded in the FEP (i48=0),
the status will be 00, too.

The HICC-modules in the FEP and CON machines
supervises the communication lines (BSC or GCI)
to the next level.
Just after reset of the machine (the host),
and in case of changes in the line status,
messages with the following format are displayed
on the statusprinter:

   NODE <node-no> LINE<line-no> STATUS <line status>

<node-no> indicates the host.
The following values may occur:

   A                indicating the FEP
   B, D, F, H and J indicating the 5 possible CON-machines

<line-no> indicates a communication line to the next level,
and may thus have values 0 through 9 for node A,
and values 0 and 1 for the CON nodes.

For the meaning of the node and line numbers,
refer to the node description in Appendix E.

<line status> is an octal number indicating the status
of the communication line in ISO 7-bit representation:

>ne 9
 status   bit mask   indicates

   00     all 0's    line ok
   01     1 shift 0  vertical parity error
   02     1 shift 1  longitudinal parity error
   04     1 shift 2  power error or software time out
   10     1 shift 3  input from line with syntax error
   20     1 shift 4  overrun - some data is lost
   40     1 shift 5  too many errors - latest data nak'ed

Also other octal numbers in the range 01 through 37 may occur,
indicating a line status where more than one error bit are set.

Other messages than the ones here specified
may occur on the statusprinter.
They will originate from the application.
>a2 RC3500 Error Procedures
In error situations proceed as follows:
 
>in 3
>ti-3
1) Reset RC3500. Like this:

>in 3
>ti-3
a. Place the key on RC3500 in the ON position.
>ne 8
>sp0
>ti-3
b.@Set the switches on RC3500 to the following positions:

      0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

(pos  0 1 2 . . . . . . . . . . . . 15)

and push the leftmost switch upwards.

>ti-3
c.@Place the key on the RC3500 in the LOCK position.
>in-3

>in-3
If the error situation still exists, continue as follows:
>in 6

>ti-6
2)
a.@Place the key in the RC3500 in the ON position.
>ti-3
b.@Push the STOP switch on the RC3500 (downwards).
>ti-3
c.@Set all the switches on the RC3500 to:

>in-11
>ne 5
                                        priority  w-reg addr

      0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0   0 0 0 0 0   0 0

>ti-1
 (pos  0 1 2 . . . . . . . . . . .  15   0 1 2 3 4   0 1)
>in 8


d. Push DEP W on RC3500 (downwards).
>sp0
e. Push RUN on RC3500 (upwards).
>sp0
f.@Place the key in the RC3500 in the LOCK @@@position.

>ti-3
If the error situation still exists, then:

>ti-3
3)@Autoload the RC3500 according to the method in section 2.3.

>ti-3
If the error situation still exists, then:

>ti-3
4) Consult the closest Technical Centre, RC.
>in-3

Error procedures concerning the I/O switch are described in the two
manuals: "Front-End Processor I/O Switch Operation" and
"Remote-End Processor I/O Switch Operation".

>a2 RC3503 Error Procedures
In error situations, proceed as follows:
>in 3

>ti-3
1) Reset RC3503

>in 3
>ti-3
a. Set the hexadecimal bus switches to

              0 0 0 0

>ne 5
>ti-3
b. Set the hexadecimal bus switches to

              E 0 0 0

If the error situation still exists,
continue as follows:

>in 6
>ne 5
>ti-6
2)@a.@Connect a debug console to the console jack
>ti-3
b.@Perform the debug commands:
 
 - S
 - L00 0004 xxxx xxxx xxxx
 - R
>in-6

If the error still exists,
then continue as part 4.2 step 3.
>a1 POWER-OFF PROCEDURE
>a2 Central site
In this procedure it is virtually to go through the Power-On procedure
in the opposite direction, except that the power must be removed from the
discs before it is removed from the RC8000s.

>in 8
>ti-8
STEP@1:@Remove the power from the main consoles on the RC3500/RC3503.

>ti-8
STEP@2:@Remove the power from the RC3500 by turning the key to the
OFF position.

>ti-8
STEP@3:@Remove the power from the RC3600 by turning the key to the 
OFF position.

>ti-8
STEP@4:@Remove the power from the discs on the RC8000s.

>ti-8
STEP@5:@Remove the power from the RC8000s by turning the power key
to the OFF position.
>in-8

>a2 Bureaus
Turn the key on every RC3500/RC3503 to the OFF position.

>a1 REFERENCES
RC8000 Operating Guide, RCSL 31-D 463.

RC3600 MUS Operating Guide, RCSL 43-GL 7397.

RC3500 Front-End Processor Switch Operation.

RC3500 Remote-End Processor Switch Operation.

RCNET Terminal Users Guide and RC3600 Device Controller,
Operator's Guide, RCSL 43-RI 1059.

RC3500 General Purpose Controller, General Infor_mation,
RCSL 52-AA 059.

RC NET General Information, RCSL 43-RI 0635.

RC3503 Reference Manual, RCSL 42-I 540.

RC3503 General Purpose Controller, General Infor_mation,
RCSL 52-AA 1013.

RADRU/C, A DAS/C Proposal for MBT, Lockheed.

General Information for RC3503 Standard Autoload,
RCSL 52-AA 1019.

LEC RC3500 SOFTWARE, Rev. 3, Release Information,
RCSL 52-AA 1027.

LEC RC3500 SOFTWARE, Rev. 3, Programming Guide,
RCSL@52-AA@1035.
«eof»
DataMuseum.dk

RC3500

⟦916aecb9b⟧ TextFileVerbose

Derivation

TextFileVerbose
