Specificaties:
- CPU: KA640
- RAM: 20 MB
- Harddisk: 2 x RF31 (381 MB, 5 1/4" half-height, DSSI)
- Backup: TK70 DLT Drive
- Netwerk: Ingebouwd. (AUI en BNC aansluiting)
- OS: OpenVMS VAX V7.1
Foto's:
Bedieningspaneel
Aansluitingen
KA640-A V5.3, VMB 2.7
Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.
Available devices.
-DIA0 (RF31)
-DIA1 (RF31)
-MUA0 (TK70)
-ESA0 (08-00-2B-26-55-D1)
Device? [ESA0]:
>>>SHOW VERSION
KA640-A V5.3, VMB 2.7
>>>SHOW MEMORY
Memory 0: 00000000 to 003FFFFF, 4MB, 0 bad pages
Memory 1: 00400000 to 013FFFFF, 16MB, 0 bad pages
Total of 20MB, 0 bad pages, 106 reserved pages
>>>SHOW QBUS
Scan of Qbus I/O Space
-20000120 (760440) = 1F80 (300) DHQ11/DHV11/CXA16/CXB16/CXY08
-20000122 (760442) = F081
-20000124 (760444) = DD18
-20000126 (760446) = 0000
-20000128 (760450) = 0000
-2000012A (760452) = 0000
-2000012C (760454) = 8000
-2000012E (760456) = 0000
-200001A0 (760640) = 0002 (310) DSV11
-200001A2 (760642) = 0005
-200001A4 (760644) = AAAA
-200001A6 (760646) = 0000
-20000DE0 (766740) = 3800
-20000DE2 (766742) = 0008
-20000DE4 (766744) = 8008
-20000DE6 (766746) = 0008
-20000DE8 (766750) = 0008
-20000DEA (766752) = 0008
-20000DEC (766754) = 0008
-20000DEE (766756) = 1048
-20000DF0 (766760) = 8008
-20000DF2 (766762) = 0008
-20000DF4 (766764) = 0028
-20000DF6 (766766) = D028
-20000DF8 (766770) = 1000
-20000DFA (766772) = 8008
-20000DFC (766774) = 2821
-20000DFE (766776) = 0008
-20000E00 (767000) = 3800
-20000E02 (767002) = 00AA
-20000E04 (767004) = 009A
-20000E06 (767006) = ADEA
-20000E08 (767010) = 0018
-20000E0A (767012) = C2EA
-20000E0C (767014) = 0822
-20000E0E (767016) = A03A
-20000E10 (767020) = CBFA
-20000E12 (767022) = 0018
-20000E14 (767024) = 06A8
-20000E16 (767026) = BAEA
-20000E18 (767030) = 00CA
-20000E1A (767032) = 61B8
-20000E1C (767034) = 2821
-20000E1E (767036) = 0068
-20001940 (774500) = 0000 (260) TQK50/TQK70/TU81E/RV20/KFQSA-TAPE
-20001942 (774502) = 0BC0
-20001F40 (777500) = 0020 (004) IPCR
Scan of Qbus Memory Space
>>>SHOW DEVICE
DSSI Node 0 (DISK0)
-DIA0 (RF31)
DSSI Node 1 (DISK1)
-DIA1 (RF31)
DSSI Node 7 (*)
UQSSP Tape Controller 0 (774500)
-MUA0 (TK70)
Ethernet Adapter
-ESA0 (08-00-2B-26-55-D1)
>>>HELP
Following is a brief summary of all the commands supported by the console:
UPPERCASE denotes a keyword that you must type in
| denotes an OR condition
[] denotes optional parameters
<> denotes a field that must be filled in
with a syntactically correct value
Valid qualifiers:
/B /W /L /Q /INSTRUCTION
/G /I /V /P /M
/STEP: /N: /NOT
/WRONG /U
Valid commands:
DEPOSIT [<qualifiers>] <address> [<datum> [<datum>]]
EXAMINE [<qualifiers>] [<address>]
MOVE [<qualifiers>] <address> <address>
SEARCH [<qualifiers>] <address> <pattern> [<mask>]
SET BFLG <boot_flags>
SET BOOT <boot_device>[:]
SET HOST/DUP/DSSI <node_number> [<task>]
SET HOST/DUP/UQSSP </DISK | /TAPE> <controller_number> [<task>]
SET HOST/DUP/UQSSP <physical_CSR_address> [<task>]
SET HOST/MAINTENANCE/UQSSP/SERVICE <controller_number>
SET HOST/MAINTENANCE/UQSSP <physical_CSR_address>
SET LANGUAGE <language_number>
SHOW BFLG
SHOW BOOT
SHOW DEVICE
SHOW DSSI
SHOW ETHERNET
SHOW LANGUAGE
SHOW MEMORY [/FULL]
SHOW QBUS
SHOW RLV12
SHOW UQSSP
SHOW VERSION
HALT
INITIALIZE
UNJAM
CONTINUE
START <address>
REPEAT <command>
X <address> <count>
FIND [/MEMORY | /RPB]
TEST [<test_code> [<parameters>]]
BOOT [/R5:<boot_flags> | /<boot_flags>] [<boot_device>[:]]
NEXT [count]
CONFIGURE
HELP
>>>SET HOST/DUP/DSSI 0
Starting DUP server...
DSSI Node 0 (DISK0)
Copyright (C) 1990 Digital Equipment Corporation
PRFMON V1.0 D 3-OCT-1990 15:05:42
DRVEXR V2.0 D 3-OCT-1990 15:05:42
DRVTST V2.0 D 3-OCT-1990 15:05:42
HISTRY V1.1 D 3-OCT-1990 15:05:42
DIRECT V1.0 D 3-OCT-1990 15:05:42
ERASE V2.0 D 3-OCT-1990 15:05:42
VERIFY V1.0 D 3-OCT-1990 15:05:42
DKUTIL V1.0 D 3-OCT-1990 15:05:42
PARAMS V2.0 D 3-OCT-1990 15:05:42
Total of 9 programs.
Task Name? params
Copyright (C) 1990 Digital Equipment Corporation
PARAMS> HELP
ENABLE MSCP
EXIT
HELP
LOCATE
SET {parameter | .} value
SHOW {parameter | . | /class}
/ALL /CONST /DRIVE
/SERVO /DUP /PROFILE
/SCS /MSCP
STATUS [type]
CONFIG LOGS DUMP
THREADS MEMORY SEEKS
MSCP PATHS DATALINK
WRITE
ZERO counter
ALL MSCP SEEKS
PARAMS> STATUS
Configuration:
Node DISK0 is an RF31 controller
Software RFX V246 built on 3-OCT-1990 15:05:42
Electronics module name is EN04812433
Unit is inoperative, error code A508(X)
Last known unit failure code A508(X)
In 59322 power-on hours, power has cycled 91 times
System up time is 0 00:03:40.45
System time is 3-OCT-1990 15:09:22
Log History:
Pid TCB Addr Process Name WQ Addr State Pri CPU
0 FFFFA86C NULL 00000000 RDY 255 0 00:03:33.87
1 FF843B7A PERIODICS FFFF8DAA BLK 254 0 00:00:00.02
66 FF84462C PRFMON FF8445DC IDL 130 0 00:00:00.00
67 FF84467C DRVEXR FF84462C IDL 124 0 00:00:00.00
68 FF8446CC DRVTST FF84467C IDL 121 0 00:00:00.00
69 FF84471C HISTRY FF8446CC IDL 118 0 00:00:00.00
70 FF84476C DIRECT FF84494C IDL 115 0 00:00:00.00
71 FF8447BC ERASE FF84471C IDL 112 0 00:00:00.00
72 FF84480C VERIFY FF8447BC IDL 109 0 00:00:00.00
73 FF84485C DKUTIL FF84480C IDL 106 0 00:00:00.00
74 FF8448AC PARAMS FFFFA8C2 CUR 103 0 00:00:00.13
2 FF84499C MSCP$DUP FFFF934C TIM 28 0 00:00:00.08
3 FF845250 SCS$DIRECTORY FFFF947A BLK 25 0 00:00:00.00
4 FF845AE2 MSCP$COPY FFFF94A6 BLK 22 0 00:00:00.00
5 FF846332 MSCP$BBR FFFF93D6 BLK 19 0 00:00:00.00
6 FF846B82 PPT$DISK FFFF89BA BLK 16 0 00:00:06.58
7 FF8473D2 SCS$DSSI FFFF8E14 BLK 13 0 00:00:00.13
8 FF84C49E MSCP$DISK FFFF90D0 BLK 14 0 00:00:00.00
Pool statistics:
Fragments: 1
Total bytes free: 20656
Largest block free: 20656
Seek statistics:
Interval: 120 seconds
Total seeks: 0
On-track seeks: 0
On-cylinder switch: 0
Seek length histogram (cylinder ranges):
MSCP statistics:
Interval: 220 seconds
I/O Commands: 0
Primary revectors: 0
Tertiary revectors: 0
Max Queue Depth: 0
Queue Depth Histogram:
Commands Processed Histogram:
GetUnit: 2:**
SetCon: 1:*
Blocks Accessed Histogram (cylinder ranges):
Read Lengths Histogram (block count ranges):
Write Lengths Histogram (block count ranges):
Datalink Counters:
Interval: 221 seconds
Pkts Rcv'd: 239:***********************
Pkts Xmt'd: 237:***********************
Naks Rcv'd: 295:*****************************
Naks Xmt'd: 0:
Resets Rcv'd: 504:**************************************************
Resets Xmt'd: 0:
No response: 295:*****************************
Duplicates: 0:
Unrecogs: 0:
VC Close Log History:
1: VC closed from ID 0 to ID 7, at 3-OCT-1990 15:06:09.
Received a Start when VC was open.
2: VC closed from ID 0 to ID 7, at 3-OCT-1990 15:06:32.
Datalink layer exhausted retries.
ID Path Block Remote Node DGS_S DGS_R MSGS_S MSGS_R
-- ------------ --------------- ---------- ---------- ---------- ----------
0 PB FF84824E Internal Path 0 0 0 0
1 PB FF848382 DISK1 RFX V246 0 0 0 0
7 PB FF84871E 7 VMB BOOT 0 0 268 268
PARAMS>
>>>SHOW BOOT
MUA0
>>>SET BOOT DIA1
>>>SHOW BOOT
DIA1
>>>BOOT
(BOOT/R5:0 DIA1)
2..
-DISK1$DIA1
1..0..
VAX/VMS Version V5.2 Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 15-JUL-2008 12:40
$! Copyright (c) 1989 Digital Equipment Corporation. All rights reserved.
The connecting computer systems and services belong to
Jos van Dijken www.josvandijken.nl.
Unauthorised use and/or misuse of these systems and services may
constitute a breach of Dutch Criminal Law (paragraphs 225 and/or 350),
and could lead to legal disciplinairy action.
Username: SYSTEM
Password:
Last interactive login on Monday, 14-JUL-2008 14:44
Last non-interactive login on Tuesday, 15-JUL-2008 12:42
SNIM01 $ HELP
HELP
The HELP command invokes the VMS HELP Facility to display
information about a VMS command or topic. In response to the "Topic?"
prompt, you can:
o Type the name of the command or topic for which you need help.
o Type INSTRUCTIONS for more detailed instructions on how to use
HELP.
o Type HINTS if you are not sure of the name of the command or
topic for which you need help.
o Type a question mark (?) to redisplay the most recently requested
text.
o Press the RETURN key one or more times to exit from HELP.
Press RETURN to continue ...
You can abbreviate any topic name, although ambiguous abbreviations
result in all matches being displayed.
Additional information available:
:= = @ ACCOUNTING ALLOCATE ANALYZE APPEND
ASSIGN ATTACH AUTHORIZE AUTOGEN BACKUP CALL CANCEL
CLOSE CONNECT CONTINUE CONVERT COPY CREATE
DEALLOCATE DEASSIGN DEBUG DECK DEFINE DELETE DEPOSIT
DIFFERENCES DIRECTORY DISCONNECT DISKQUOTA DISMOUNT DUMP
EDIT ENCRYPT EOD EOJ Errors EXAMINE EXCHANGE
EXIT FDL GOSUB GOTO HELP Hints IF
INITIALIZE INQUIRE INSTALL Instructions JOB LATCP
Lexicals LIBRARY LICENSE Line_editing LINK LOGIN
LOGOUT MACRO MAIL MERGE MESSAGE MONITOR MOUNT
NCP NCS ON OPEN PASSWORD PATCH PHONE
PRINT PURGE Queues READ RECALL RECOVER RENAME
REPLY REQUEST RETURN RMS RTL_Routines RUN
RUNOFF SEARCH SET SHOW SORT SPAWN Specify
Press RETURN to continue ...
START STOP SUBMIT Symbol_Assign SYNCHRONIZE
SYSGEN SYSMAN System_Services TFF TYPE UNLOCK
V52_NewFeatures VIEW WAIT WRITE
Topic?
SNIM01 $ SHOW SYSTEM
VAX/VMS V5.2 on node SNIM01 16-JUL-2008 23:38:35.15 Uptime 0 00:52:41
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00000081 SWAPPER HIB 16 0 0 00:00:00.42 0 0
00000086 ERRFMT HIB 8 118 0 00:00:00.53 82 117
00000087 OPCOM HIB 8 100 0 00:00:00.65 284 143
00000088 AUDIT_SERVER HIB 10 48 0 00:00:00.80 1360 189
00000089 JOB_CONTROL HIB 9 660 0 00:00:02.80 261 263
0000008A CONFIGURE HIB 9 31 0 00:00:00.19 100 152
0000008B SYMBIONT_0001 HIB 6 71 0 00:00:00.47 217 128
0000008C NETACP HIB 9 69 0 00:00:02.38 385 561
0000008D EVL HIB 6 80 0 00:00:00.70 1094 48 N
0000008E REMACP HIB 8 25 0 00:00:00.10 64 33
00000090 SYSTEM CUR 7 2975 0 00:00:48.12 7908 249
SNIM01 $ SHOW NETWORK
VAX/VMS Network status for local node 1.1 JVDVAX on 16-JUL-2008 23:39:21.80
This is a nonrouting node, and does not have any network information.
The designated router for JVDVAX is node 0 JVDVAX.
SNIM01 $ SHOW STATUS
Status on 16-JUL-2008 23:39:40.36 Elapsed CPU : 0 00:00:48.26
Buff. I/O : 2547 Cur. ws. : 256 Open files : 0
Dir. I/O : 447 Phys. Mem. : 218 Page Faults : 7966
SNIM01 $ SHOW DEVICE
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DISK0$DIA0: Online 0
DISK1$DIA1: Mounted 0 VAXVMSRL052 324906 128 1
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
SNIM01$MUA0: Online 0
Device Device Error
Name Status Count
OPA0: Online 0
RTA0: Offline 0
RTB0: Offline 0
RTC0: Offline 0
TXA0: Online 0
TXA1: Online spooled 0
alloc
TXA2: Online 0
TXA3: Online 0
TXA4: Online 0
TXA5: Online 0
TXA6: Online 0
TXA7: Online 0
Device Device Error
Name Status Count
ESA0: Online 0
ESA1: Online 0
PIA0: Online 2
PTA0: Online 1
WSA0: Offline 0
SNIM01 $
Update 04-AUG-2008
Harddisk DIA0 heeft een flinke pedagogische tik gekregen, en heeft in de vrees voor nog een tik maar besloten om weer te gaan werken. Probleem was een vastzittende Head-Assembly in de HDA.
Bij het booten vanaf DIA0 bleek dat ook daar een VMS installatie op stond. Deze heb ik nu vervangen door een verse VMS 7.1 installatie:
226276> factory Factory will RESTART controller. Are you sure? (y/n) y
FLASH Boot Utility Version A1 FBOOT-I-LOAD, Load sequence commencing -
Type CTRL/C to abort
FBOOT-I-LOADING, Loading HSD10 rev C294 code to 0x80020000:0x8007f310
FBOOT-I-STARTING, Executing loaded code
Controller HSD10
Serial No.: 15204
Firmware Revision: C294
Date/Time: 01-JAN-1990 00:00:00
Uptime: 0 DAYS 00:00:00
Processor DRAM size: 1 MB
Processor Free Pool: 236 KB
Device Type = HS
Spinup Delay = 5 Seconds
Redundant Mode = OFF
SCS Parameters
Nodename: 226276
System ID: 226276
DISK_ALCS: 0
TAPE_ALCS: 0
MAX_HOSTS: 4
DATREQ_PR: LOW
Cache 32 MB read cache
Ports
Port 0: DSSI, Disabled
Port 1: SCSI, id= 7, power_on_reset=ON
226276>
01-JAN-1990 00:00:00 0000 INIT Event Logger Startup
01-JAN-1990 00:00:00 4710 INIT SCSI Port 1, Bus Power-On Reset
226276>
01-JAN-1990 00:00:05 2705 SCSIDR0 Port 1, SCSI Reset Detected
01-JAN-1990 00:00:05 2713 SCSIDR0 Port 1 Chip Reset
226276> Set Port 0 /Enable
226276> autoconfig
Creating Type Inquiry Data Device Attributes
--------------------------------------------------------------------------------
D160 CDROM TOSHIBA CD-ROM 1001 Sync Rmv
226276> map unit d160 dia6
226276> show dev
Name Pcnt Used by Type Inquiry Data Device Attributes
--------------------------------------------------------------------------------
D160 1 DIA6 CDROM TOSHIBA CD-ROM 1001 Sync Rmv
No Stripe sets Found.
No Mirror sets Found.
No Tapes Found.
Name Member Status Host Set-members/Modifiers
--------------------------------------------------------------------------------
DIA6 D160 (1) AVAIL online, cache, disconnect,
immediate, tagging, truncate,
spindown, sync_rate=10
FLASH Boot Utility Version A1 FBOOT-I-LOAD, Load sequence commencing -
Type CTRL/C to abort
FBOOT-I-LOADING, Loading HSD10 rev C294 code to 0x80020000:0x8007f310
FBOOT-I-STARTING, Executing loaded code
Controller HSD10
Serial No.: 15204
Firmware Revision: C294
Date/Time: 01-JAN-1990 00:00:00
Uptime: 0 DAYS 00:00:00
Processor DRAM size: 1 MB
Processor Free Pool: 236 KB
Device Type = HS
Spinup Delay = 5 Seconds
Redundant Mode = OFF SCS Parameters
Nodename: 226276 System ID: 226276
DISK_ALCS: 0 TAPE_ALCS: 0
MAX_HOSTS: 4 DATREQ_PR: LOW
Cache 32 MB read cache
Ports Port 0: DSSI, id= 6 Port 1: SCSI, id= 7, power_on_reset=ON
226276>
01-JAN-1990 00:00:00 0000 INIT Event Logger Startup
01-JAN-1990 00:00:00 4710 INIT SCSI Port 1, Bus Power-On Reset
226276>
01-JAN-1990 00:00:05 2705 SCSIDR0 Port 1, SCSI Reset Detected
01-JAN-1990 00:00:05 2713 SCSIDR0 Port 1 Chip Reset
226276> show dev
Name Pcnt Used by Type Inquiry Data Device Attributes
--------------------------------------------------------------------------------
D160 1 DIA6 DISK
No Stripe sets Found.
No Mirror sets Found.
No Tapes Found. Name Member Status Host Set-members/Modifiers
--------------------------------------------------------------------------------
DIA6 D160 (1) AVAIL online, cache, disconnect, immediate,
tagging, truncate, spindown, sync_rate=10
KA640-A V5.3, VMB 2.7 Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03.. Tests completed.
>>>show dev
DSSI Node 0 (DISK0)
-DIA0 (RF31)
DSSI Node 1 (DISK1)
-DIA1 (RF31)
DSSI Node 6 (226276)
-DIA6 (HSX0)
DSSI Node 7 (*)
UQSSP Tape Controller 0 (774500)
-MUA0 (TK 70)
Ethernet Adapter -ESA0 (08-00-2B-26-55-D1)
>>>boot dia6 (BOOT/R5:0 DIA6)
2.. -226276$DIA6
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version X6NO Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 4-AUG-2008 12:30
Configuring devices . . .
Now configuring HSC, RF, and MSCP-served devices . . .
Please check the names of the devices which have been configured,
to make sure that ALL remote devices which you intend to use have been configured.
If any device does not show up, please take action now to make it available.
Available device MUA0:
device type TK70 Available device 226276$DIA6:
device type HSX00 Available device DISK1$DIA1:
device type RF31 Available device DISK0$DIA0:
device type RF31 Enter "YES" when all needed devices are available: YES
%BACKUP-I-IDENT, Stand-alone BACKUP V7.1; the date is 4-AUG-2008 12:32:03.03
$ backup/image/verify 226276$DIA6:VMS071.B/save_set DISK0$DIA0:
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-I-PROCDONE, operation completed. Processing finished at 4-AUG-2008 12:38:23.25
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
?02 EXT HLT
PC = 80E65347
>>>boot dia0
(BOOT/R5:0 DIA0)
2.. -DISK0$DIA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version BI71-6NO Major version id = 1 Minor version id = 0
OpenVMS VAX V7.1 Installation Procedure
Model: MicroVAX 3400 Series
System device: RF31 - _DISK0$DIA0:
Free Blocks: 681198
CPU type: 10-01
* Please enter the date and time (DD-MMM-YYYY HH:MM) 4-aug-2008 12:40
*********************************************************
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT
%SYSTEM-I-SETTZ, to set your local timezone use:
$ @SYS$MANAGER:UTC$TIME_SETUP.COM
*********************************************************
On MIN or UPGRADE system startup - CLUE is not run.
% OPCOM 4-AUG-2008 12:40:12.77
% Operator _OPA0: has been enabled, username SYSTEM
% OPCOM 4-AUG-2008 12:40:12.88
% Operator status for operator _OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS,
NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7,
OPER8, OPER9, OPER10, OPER11, OPER12
% OPCOM 4-AUG-2008 12:40:13.75
% Logfile has been initialized by operator _OPA0: Logfile is
SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
% OPCOM 4-AUG-2008 12:40:13.79
% Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 CENTRAL, PRINTER,
TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3,
OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
% OPCOM 4-AUG-2008 12:40:15.93
% Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
% OPCOM 4-AUG-2008 12:40:15.95
% Message from user JOB_CONTROL -RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%SYSTEM-I-BOOTUPGRADE, security server not started
% OPCOM 4-AUG-2008 12:40:23.38
% Message from user SYSTEM
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager Startup processing continuing...
If this system disk is to be used in a cluster with multiple system
disks, then each system disk must have a unique volume label. Any
nodes having system disks with duplicate volume labels will fail to
boot into the cluster.
You can indicate a volume label of 1 to 12 characters in length. If you
want to use the default name of OpenVMS071, press RETURN in response
to the next question. * Enter the volume label for this system disk [OpenVMS071]:
* Enter name of drive holding the OpenVMS distribution media: dia6
* Is the OpenVMS media ready to be mounted? [N] y
If your kit is on an HSC device then you must use the HSC node name
in the device name, as in HSC001$DJA1:
If your kit is a DSSI device then you must use the DSSI node name
in the device name, as in RF001$DIA1:
* Enter name of drive holding the OpenVMS distribution media: 11 226276$dia1 6
* Is the OpenVMS media ready to be mounted? [N] y
%MOUNT-I-MOUNTED, VAXVMS071 mounted on _226276$DIA6:
Select optional software you want to install.
You can install one
or more of the following OpenVMS or DECwindows components:
o OpenVMS library - 52200 blocks
o OpenVMS optional - 19000 blocks
o OpenVMS Help Message - 10400 blocks
o OpenVMS Management Station - 20000 blocks
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts - 6200 blocks
o DECnet-Plus networking - 80000 blocks
Space remaining on system disk: 681018 blocks
* Do you want to install the OpenVMS library files? (Y/N) y
Space remaining on system disk: 628818 blocks
* Do you want to install the OpenVMS optional files? (Y/N) y
Space remaining on system disk: 609818 blocks
The Help Message utility (MSGHLP) provides online explanations
and user actions for OpenVMS messages in place of the hardcopy
OpenVMS System Messages and Recovery Procedures Reference Manual,
which is now separately orderable.
The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA,
consumes approximately 10400 blocks and will be
placed by default on your system disk in SYS$COMMON:[SYSHLP]
unless you specify an alternate device when prompted.
* Do you want to install the MSGHLP database? (Y/N) y
You can install this database on your system disk in SYS$COMMON:[SYSHLP]
or on an alternate device. If you specify an alternate device, but no
directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When
prompted, take the default of the system disk or specify an alternate
device using this format:
device:[directory]
* Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]]
Space remaining on system disk: 599418 blocks
The OpenVMS Management Station is a client-server application
that provides OpenVMS system management capabilities through a
client application on a personal computer (PC) running Microsoft
Windows. The server application runs on OpenVMS systems and is
automatically installed as part of the OpenVMS operating system.
This option provides the files used to create the installation media
for the PC client software. If you want to use the OpenVMS Management
Station, you must install these files on at least one OpenVMS system to
create the installation media, which can then be used to install the
PC client on one or more PCs.
Note: To use the OpenVMS Management Station on your PC, you must be
running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1)
software.
The OpenVMS Management Station optional files consume approximately 20000
blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].
* Do you want to install the optional OpenVMS Management Station files? (Y/N) y
Space remaining on system disk: 579418 blocks
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the installation.
Some media, TK50s in particular, can be very slow when tailoring on files.
You might want to select DECwindows now and tailor off unwanted files later.
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.1.
The DECwindows components provided in this kit requires approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* a VAXcluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
* Do you want the DECwindows base support? (Y/N) y
Space remaining: 575018 blocks
You must select the DECwindows workstation support option if
- you are installing this kit on
* a workstation or
* a VAXcluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows workstation support, then you will have
to use the DECW$TAILOR utility to provide font files.
* Do you want to install DECwindows workstation support? (Y/N) y
Space remaining: 551218 blocks
DECwindows workstation support includes the 75 dots per inch video fonts.
All DECwindows applications run with 75 dots per inch video fonts.
By default, most systems startup with 75 dots per inch video fonts.
Certain applications can take advantage of 100 dots per inch video fonts.
For the VAXstation 4000 series machines, 100 dots per inch video fonts
are used by default. If you decide not to install 100 dots per inch
video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
to force 75 dots per inch video fonts to be the default. Otherwise,
certain applications may not space text properly.
For instructions on how to configure your system with both 75 and 100
dots per inch video fonts, see the installation guide or look at the
template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.
* Do you want 100 dots per inch video fonts installed? (Y/N) y
Space remaining: 545018 blocks
Beginning with OpenVMS V7.1 DECnet-Plus is provided with the
OpenVMS operating system. Digital strongly recommends that DECnet
users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is available for separate installation. Please see the
"OpenVMS V7.1 Release Notes" for important information regarding
DECnet Phase IV support.
If you plan to install DECnet Phase IV do NOT select DECnet-Plus.
* Do you want to install DECnet-Plus? (Y/N) y
Space remaining on system disk: 465018 blocks
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Help Message
OpenVMS Management Station Software -- PC files
DECwindows base support
DECwindows workstation support with:
- 75 dots per inch video fonts
- 100 dots per inch video fonts
DECnet-Plus
Space remaining on system disk: 465018 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Help Message save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Management Station Software -- PC files
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows base support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows workstation support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 75 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 100 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
You can now remove the distribution kit from 226276$DIA6:.
Creating [VMS$COMMON] directory tree ...
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.
Cluster configuration cannot be done at this time because no network
is present. In order to configure a cluster you must FIRST do one
or both of the following:
o Install DECnet-Plus (or DECnet Phase IV), or
o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the
comment delimiter ("!") from the line
$! @SYS$STARTUP:LAN$STARTUP
in SYS$MANAGER:SYSTARTUP_VMS.COM.
Then configure the cluster by executing the following command:
@ @SYS$MANAGER:CLUSTER_CONFIG
See the OpenVMS System Manager's Manual: Essentials for more information.
* Do you want DECwindows Motif as the default windowing system? (Y/N) y
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
* Enter password for SYSTEM:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-PWDLESSMIN, new password is shorter than minimum password length
%UAF-I-MDFYMSG, user record(s) updated
* Enter password for FIELD:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, rights database created
%UAF-I-RDBADDMSGU, identifier DEFAULT value [000200,000200] added to rights database
%UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights database
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights database
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights database modified
Creating MODPARAMS.DAT database file, SYS$SYSTEM:MODPARAMS.DAT
* Please enter the SCSNODE name: VAX3400
VAX3400 is an invalid node name.
The name must be 6 or fewer alphanumeric characters
with at least one alphabetic character
* Please enter the SCSNODE name: JVDVAX
* Please enter the SCSSYSTEMID: JVDVAX
JVDVAX is not a legal SCSSYSTEMID
Legal range is 1025 - 65535
* Please enter the SCSSYSTEMID: 10000
After the installation finishes, you might want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system
libraries are shipped in a data-compressed format. If you have
enough disk space, you can decompress the libraries for faster access.
To data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you do not decompress these libraries, you will experience slower
response to the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in the upgrade and installation supplement"
supplied for your VAX computer.
o TAILOR THE SYSTEM DISK - You might want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
OpenVMS tailoring:
$ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring:
$ RUN SYS$UPDATE:DECW$TAILOR
NOTE: The tailor procedure cannot be used to TAILOR ON or TAILOR OFF
files located on an alternate disk.
=================================================================
Continuing with OpenVMS VAX V7.1 Installation Procedure.
Configuring all devices on the system ...
If you have Product Authorization Keys (PAKs) to register, you can
register them now.
* Do you want to register any Product Authorization Keys? (Y/N): n
********************************************************************************
After the system has rebooted you must register any Product
Authorization Keys (PAKs) that you have received with this kit.
You can register these PAKs by executing the following procedure:
$ @SYS$UPDATE:VMSLICENSE
See the OpenVMS License Management Utility Manual for any additional
information you need.
********************************************************************************
Now registering the OpenVMS operating system in the
POLYCENTER Software Installation product database
The following product will be registered:
DEC VAXVMS VMS V7.1
Transition (registration)
The following product has been registered:
DEC VAXVMS VMS V7.1
Transition (registration)
%UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE]
Configuring the Local Time Zone TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore 10) GB-Eire
20) MET 30) SystemV 0) None of the above
Select the number above that best describes your location: 0 ***
%UTC-W-GMT, A choice of 0 defaults your local time to GMT ***
Is this correct? (Yes/No) [NO]: TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore 10) GB-Eire
20) MET 30) SystemV 0) None of the above
Select the number above that best describes your location: 20
You selected MET as your time zone. Is this correct? (Yes/No) [YES]: yes
Default Time Differential Factor for standard time is 1:00.
Default Time Differential Factor for daylight saving time is 2:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most repects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
Is Daylight Savings time in effect? (Yes/No): yes
Enter the Time Differential Factor [2:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = 2:00.
Is this correct? [Y]: y
DECnet-Plus will now be installed.
Media containing the DECnet-Plus kit must be available.
If you are installing OpenVMS from an Infoserver (DAD1)
or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.
If you are installing from a cartridge tape (TK50) or
from an open reel tape, you should have a DECnet-Plus kit
on cartidge tape or open reel tape.
An appropriate DECnet-Plus kit may also be available on
the Consolidated Distribution CD-ROM, or you may have a
separate DECnet-Plus kit.
NOTE: You may choose any available media for the
DECnet-Plus kit. It is NOT NECESSARY to use the same
type of media that contained the OpenVMS kit.
If you do not have a DECnet-Plus kit available, or if you
have decided NOT to install/upgrade DECnet-Plus, you can
bypass the DECnet-Plus installation by entering "EXIT"
for the "name of drive holding the DECnet-Plus kit".
* Enter name of drive holding the DECnet-Plus kit: exit
"EXIT" indicates that you do NOT want to install
or upgrade DECnet-Plus.
* Is this correct? (Y/N) y
********************************************************************************
Running AUTOGEN to compute the new SYSTEM parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 created
%SYSGEN-I-CREATED, DISK0$DIA0:[SYS0.SYSEXE]ERRORLOG.DMP;1 created
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found
SHUTDOWN message from user SYSTEM at Batch 13:29:07
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
?06 HLT INST
PC = 81666595
>>>boot (BOOT/R5:0 DIA0)
2.. -DISK0$DIA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V7.1 Major version id = 1 Minor version id = 0
*****************************************************************
OpenVMS VAX V7.1
You have SUCCESSFULLY installed the OpenVMS VAX Operating System.
The system is now executing the STARTUP procedure. Please
wait for the completion of STARTUP before logging in to the
system.
*****************************************************************
%STDRV-I-STARTUP, OpenVMS startup begun at 4-AUG-2008 13:33:48.32
%DCL-S-SPAWNED, process SYSTEM_1 spawned
% OPCOM 4-AUG-2008 13:34:31.49
% Operator _JVDVAX$OPA0: has been enabled, username SYSTEM
% OPCOM 4-AUG-2008 13:34:31.57
% Operator status for operator _JVDVAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS,
DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4,
OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12
% OPCOM 4-AUG-2008 13:34:31.85
% Logfile has been initialized by operator _JVDVAX$OPA0:
Logfile is JVDVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
% OPCOM 4-AUG-2008 13:34:31.86
% Operator status for operator JVDVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9,
OPER10, OPER11, OPER12
%SET-I-NEWAUDSRV, identification of new audit server process is 0000010A
% OPCOM 4-AUG-2008 13:34:33.40
% Message from user AUDIT$SERVER on JVDVAX
%AUDSRV-I-NEWSERVERDB, new audit server database created
% OPCOM 4-AUG-2008 13:34:34.79
% Message from user JOB_CONTROL on JVDVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
% OPCOM 4-AUG-2008 13:34:34.88
% Message from user JOB_CONTROL on JVDVAX -RMS-E-FNF, file not found
% OPCOM 4-AUG-2008 13:34:35.23
% Message from user AUDIT$SERVER on JVDVAX
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
% OPCOM 4-AUG-2008 13:34:35.71
% Message from user AUDIT$SERVER on JVDVAX
%AUDSRV-I-NEWOBJECTDB, new object database created
%LICENSE-F-EMTLDB, license database contains no license records
% OPCOM 4-AUG-2008 13:34:40.20
% Message from user SYSTEM on JVDVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
% OPCOM 4-AUG-2008 13:34:40.32
% Message from user SYSTEM on JVDVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
% OPCOM 4-AUG-2008 13:34:40.32
% Message from user SYSTEM on JVDVAX
%SECSRV-I-SERVERSTARTINGU, security server starting up
% OPCOM 4-AUG-2008 13:34:41.06
% Message from user SYSTEM on JVDVAX
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
% OPCOM 4-AUG-2008 13:34:43.07
% Message from user SYSTEM on JVDVAX
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager Startup processing continuing...
% OPCOM 4-AUG-2008 13:34:45.31
% Message from user SYSTEM on JVDVAX Warning: DECdtm log file not found
(SYS$JOURNAL:SYSTEM$JVDVAX.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
% OPCOM 4-AUG-2008 13:34:47.35
% Message from user AUDIT$SERVER on JVDVAX Security alarm (SECURITY)
and security audit (SECURITY) on JVDVAX, system id: 10000 Auditable event:
Audit server starting up
Event time: 4-AUG-2008 13:34:46.83
PID: 00000103
Username: SYSTEM
% OPCOM 4-AUG-2008 13:34:49.89
% Message from user AUDIT$SERVER on JVDVAX Security alarm (SECURITY)
and security audit (SECURITY) on JVDVAX, system id: 10000 Auditable event:
Identifier added Event time: 4-AUG-2008 13:34:49.77
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: DISK0$DIA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_JVDVAX
Identifier value: %X80010000
Attributes: none
%UAF-I-RDBADDMSG, identifier SYS$NODE_JVDVAX value
%X80010000 added to rights database
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM
job terminated at 4-AUG-2008 13:34:53.34
Accounting information:
Buffered I/O count: 1290
Peak working set size: 953
Direct I/O count: 502
Peak page file size: 4502
Page faults: 4721
Mounted volumes: 0
Charged CPU time: 0 00:00:49.52
Elapsed time: 0 00:01:17.62
Welcome to OpenVMS (TM) VAX Operating System, Version V7.1
Username: system Password:
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.1
$ @sys$update:libdecomp.com
OpenVMS Library Decompression Utility
1 HELPLIB.HLB 15 SDA.HLB 28 PHONEHELP.HLB
2 STARLET.OLB 16 SHWCLHELP.HLB 29 LIB.MLB
3 ACLEDT.HLB 17 SYSGEN.HLB 30 STARLET.MLB
4 ANLRMSHLP.HLB 18 ANALAUDIT$HELP.HLB 31 STARLETSD.TLB
5 DBG$HELP.HLB 19 SYSMANHELP.HLB 32 SYS$STARLET_C.TLB
6 DBG$UIHELP.HLB 20 TFF$TFUHELP.HLB 33 ERFLIB.TLB
7 DISKQUOTA.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB
8 EDFHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB
9 INSTALHLP.HLB 23 EVE$HELP.HLB 36 VAXCRTLG.OLB
10 LATCP$HELP.HLB 24 EVE$KEYHELP.HLB 37 IMAGELIB.OLB
11 MAILHELP.HLB 25 UAFHELP.HLB 38 DECCCURSE.OLB
12 MNRHELP.HLB 26 TECO.HLB 39 DECCRTL.OLB
13 EDTHELP.HLB 27 PATCHHELP.HLB 40 DECCRTLG.OLB
A ALL libraries to be decompressed
E EXIT this procedure
* Enter letter or number(s) of libraries to be decompressed
(Separate multiple entries with a comma): a
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]HELPLIB.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]ACLEDT.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]ANLRMSHLP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]DBG$HELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]DBG$UIHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]DISKQUOTA.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]EDFHLP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]INSTALHLP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]LATCP$HELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]MAILHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]MNRHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]EDTHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]NCPHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]SDA.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]SHWCLHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]SYSGEN.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]ANALAUDIT$HELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]SYSMANHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]TFF$TFUHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]EXCHNGHLP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]TPUHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]EVE$HELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]EVE$KEYHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]UAFHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]TECO.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]PATCHHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSHLP]PHONEHELP.HLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]LIB.MLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]STARLET.MLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]STARLETSD.TLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]SYS$STARLET_C.TLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]ERFLIB.TLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]VAXCCURSE.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]VAXCRTL.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]VAXCRTLG.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]IMAGELIB.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]DECCCURSE.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]DECCRTL.OLB
%UPGRADE-I-EXPANDING, decompressing library SYS$COMMON:[SYSLIB]DECCRTLG.OLB
$ shutdown
SHUTDOWN -- Perform an Orderly System Shutdown
on node JVDVAX
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
% OPCOM 4-AUG-2008 14:31:30.92
% Operator status for operator _JVDVAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS,
DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4,
OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
% OPCOM 4-AUG-2008 14:31:32.74
% Message from user JOB_CONTROL on JVDVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
% OPCOM 4-AUG-2008 14:31:32.76
% Message from user JOB_CONTROL on JVDVAX -RMS-E-FNF, file not found
SHUTDOWN message on JVDVAX from user SYSTEM at _JVDVAX$OPA0: 14:31:33
JVDVAX will shut down in 0 minutes; back up LATER. Please log off node JVDVAX.
SHUTDOWN 1 terminal has been notified on JVDVAX.
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down
% OPCOM 4-AUG-2008 14:31:37.46
% Message from user AUDIT$SERVER on JVDVAX Security alarm (SECURITY) and
security audit (SECURITY) on JVDVAX, system id: 10000
Auditable event: Audit server shutting down
Event time: 4-AUG-2008 14:31:37.45
PID: 0000010E
Username: SYSTEM
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
% OPCOM 4-AUG-2008 14:31:44.87
% Message from user SYSTEM on JVDVAX _JVDVAX$OPA0:,
JVDVAX shutdown was requested by the operator.
% OPCOM 4-AUG-2008 14:31:45.03
% Logfile was closed by operator _JVDVAX$OPA0:
Logfile was JVDVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
% OPCOM 4-AUG-2008 14:31:45.21
% Operator _JVDVAX$OPA0: has been disabled, username SYSTEM
SYSTEM SHUTDOWN COMPLETE - use console to halt system
?02 EXT HLT
PC = 80F8FED3
>>>halt
>>>
Update 05-AUG-2008
vandaag de TOY accu maar eens vervangen. Deze was aardig verrot (Ni-Cd, > 10 jaar oud). Helaas was de stekker van de accu ook verrot, dus deze ook vervangen.
KA640-A V5.3, VMB 2.7
Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.
Available devices.
-DIA0 (RF31)
-DIA1 (RF31)
-MUA0 (TK70)
-ESA0 (08-00-2B-26-55-D1)
Device? [ESA0]:
(BOOT/R5:0 ESA0)
2..
-ESA0
KA640-A V5.3, VMB 2.7
Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03..
Tests completed.
>>>show boot
>>>set boot dia0
>>>show boot
DIA0
>>>
KA640-A V5.3, VMB 2.7
Performing normal system tests.
41..40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..
25..24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..
09..08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DIA0)
2..
-DISK0$DIA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V7.1 Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 5-AUG-2008 20:23
$! Copyright (c) 1996 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, OpenVMS startup begun at 5-AUG-2008 20:23:52.53
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:36.15 %%%%%%%%%%%
Operator _JVDVAX$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:36.24 %%%%%%%%%%%
Operator status for operator _JVDVAX$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:36.65 %%%%%%%%%%%
Logfile has been initialized by operator _JVDVAX$OPA0:
Logfile is JVDVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:36.65 %%%%%%%%%%%
Operator status for operator JVDVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SET-I-NEWAUDSRV, identification of new audit server process is 0000010A
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:39.42 %%%%%%%%%%%
Message from user JOB_CONTROL on JVDVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:39.44 %%%%%%%%%%%
Message from user JOB_CONTROL on JVDVAX
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:43.59 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:43.66 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:43.72 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:44.05 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:46.36 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:48.60 %%%%%%%%%%%
Message from user SYSTEM on JVDVAX
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$JVDVAX.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
%%%%%%%%%%% OPCOM 5-AUG-2008 20:24:50.86 %%%%%%%%%%%
Message from user AUDIT$SERVER on JVDVAX
Security alarm (SECURITY) and security audit (SECURITY) on JVDVAX, system id: 10000
Auditable event: Audit server starting up
Event time: 5-AUG-2008 20:24:50.18
PID: 00000103
Username: SYSTEM
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 5-AUG-2008 20:24:54.35
Accounting information:
Buffered I/O count: 1010 Peak working set size: 999
Direct I/O count: 441 Peak page file size: 4021
Page faults: 3405 Mounted volumes: 0
Charged CPU time: 0 00:00:41.60 Elapsed time: 0 00:01:03.71
Welcome to OpenVMS (TM) VAX Operating System, Version V7.1
Username: system
Password:
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.1
Last interactive login on Monday, 4-AUG-2008 13:35
$ show system
OpenVMS V7.1 on node JVDVAX 5-AUG-2008 20:28:55.56 Uptime 0 00:05:55
Pid Process Name State Pri I/O CPU Page flts Pages
00000101 SWAPPER HIB 16 0 0 00:00:00.34 0 0
00000105 CONFIGURE HIB 9 15 0 00:00:00.19 121 183
00000107 IPCACP HIB 10 6 0 00:00:00.13 95 164
00000108 ERRFMT HIB 9 21 0 00:00:00.30 125 213
00000109 OPCOM HIB 9 41 0 00:00:00.50 202 251
0000010A AUDIT_SERVER HIB 9 48 0 00:00:01.08 542 831
0000010B JOB_CONTROL HIB 9 29 0 00:00:00.28 159 281
0000010C SECURITY_SERVER HIB 10 25 0 00:00:01.15 950 1295
0000010D TP_SERVER HIB 10 25 0 00:00:00.63 203 306
00000110 SYSTEM CUR 6 80 0 00:00:01.84 647 693
$lo
SYSTEM logged out at 5-AUG-2008 20:29:44.14
Overview
This chapter provides a brief overview of the KA640 CPU module and MS650 memory modules.
1.1 Introduction
The KA640, shown in Figure 1-1, is a quad-height VAX processor module for the Q22-bus (extended LSI-ll bus) with built-in DSSI and Ethernet controllers. It is designed for use in high speed, real-time applications and for multiuser, multitasking environments. There are two variants, KA640-AA and the KA640-BA. The KA640-AA runs multi-user software; the KA640-BA runs single-user software.
The KA640 is used in two systems, the MicroVAX 3300 and the MicroVAX 3400. The MicroVAX 3300 is in a BA215 enclosure. The MicroVAX 3400 is in a BA213 enclosure. Refer to the BA21S Enclosure Maintenance and the BA2l3 Enclosure Maintenance for a detailed description of each enclosure.
The KA640 CPU module and MS650 memory modules combine to form a VAX CPU/memory subsystem that uses the Q22-bus, DSSI bus, and Ethernet to communicate with mass storage and 110 devices. The KA640 and MS650 modules mount in standard Q22-bus backplane slots that implement the Q22-bus in the AB rows and the CD interconnect in the CD rows. A single KA640 can support up to three MS650 modules, if enough Q22/CD slots are available.
The KAA640 communicates with the console device via the H3602-SA CPU cover panel, which also contains configuration switches, an LED display, and DESTA (Ethernet connector).
The major functional blocks of the KA640 CPU module are shown in Figure 1-2, and are described in the following paragraphs.
1.2 Central Processing Unit
The central processing unit (CPU) is implemented by the CVAX chip. The CVAX chip contains approximately 180,000 transistors in an 84-pin CERQUAD surface mount package. It achieves a 100 ns microcycle and a 200 ns bus cycle at an operating frequency of 20 MHz. The CVAX chip supports full VAX memory management and a 4 Gigabyte virtual address space.
The CVAX chip contains all VAX visible general purpose registers (GPRs), several system registers (MSER, CADR, SCBB, etc.), the cache memory (1 Kbyte) , and all memory management hardware including a 28-entry translation buffer.
The CVAX chip provides the following functions:
- Fetches all V AX instructions
- Executes 181 VAX instructions
- Assists in the execution of 21 additional instructions
- Passes 70 floating point instructions to the CFP A chip
The remaining 32 VAX instructions (including H-floating and octaword) must be emulated in macrocode.
The CVAX chip provides the following subset of the VAX data types:
- Byte
- Word
- Longword
- Quadword
- Character string
- Variable length bit field
Support for the remaining V AX data types can be provided via macrocode emulation.
1.3 Floating Point Accelerator
The floating point accelerator is implemented by the CFPA chip. The CFPA chip contains approximately 60,000 transistors in a 68-pin CERQUAD surface mount package. It executes 70 floating point instructions.
The CFPA chip receives opcode information from the CVAX chip, and receives operands directly from memory or from the CVAX chip. The floating point result is always returned to the CVAX chip.
1.4 Cache Memory
The KA640 module incorporates a cache memory within the CV AX chip to maximize CPU performance. The cache is a 1 Kbyte, two-way associative, write through cache memory, with a 100 ns cycle time.
1.5 Memory Controller>
The main memory controller is implemented by a VLSI chip called the CMCTL. The CMCTL contains approximately 25,000 transistors in a 132- pin CERQUAD surface mount package. It supports up to 64 Mbytes of ECC memory, of which only 52 MBytes can be used on a KA640, with a 400 ns cycle time for longword transfers and a 600 ns cycle time for quadword transfers. This memory resides on the KA640 CPU module, and depending on the system configuration, one to three MS650 memory modules.
1.6 MS650-AA Memory Modules
The MS650-AA memory modules are 8 Mbyte, 450 ns, 39-bit wide arrays (32-bit data and 7 -bit ECC) implemented with 256 Kb dynamic RAMs in zig-zag in-line packages (ZIPs). MS650-AA memory modules are single, quad-height, Q22-bus modules, as shown in Figure 1-3.
The MS650 modules communicate with the KA640 via the MS650 memory interconnect, which utilizes the CD rows of backplane slots 2 through 4, and a 50-pin ribbon cable. The KA640 memory subsystem supports a maximum of 3 memory modules.
1.7 DSSI Interface
An on-board digital small storage interconnect (DSSI) bus interface is implemented by the SII chip and four 32K by 8 static RAMs. The DSSI interface allows the KA640 to transmit packets of data to, and receive packets of data from up to seven other DSSI devices. The KA640 system configurations contain one or more RF30 fixed disk devices, connected through the DSSI bus.
1.8 Ethernet Interface
The KA640 CPU module features an on-board network interface that is implemented via the LANCE chip and two 32K by 8 static RAMs. When used in conjunction with the H3602-SA CPU cover panel, this interface allows the KA640 to be connected to either a Thin Wire or standard Ethernet network.
The Ethernet interface includes registers for control and status reporting as well as a DMA controller, a 24 word transmit silo and a 24 word receive silo.
1.9 Q22-bus Interface
The Q22-bus interface is implemented by the CQBIC chip. The CQBIC chip contains approximately 40,870 transistors in a 132-pin CERQUAD surface mount package. It supports up to 16-word, block mode transfers between a Q22-bus DMA device and main memory, and up to 2-word, block mode transfers between the CPU and Q22-bus devices. The Q22-bus interface contains the following:
- A 16-entry map cache for the 8,192-entry, main memory-resident "scatter-gather" map, used for translating 22-bit Q22-bus addresses into 26-bit main memory addresses
- Interrupt arbitration logic that recognizes Q22-bus interrupt requests BR7-BR4
- Q22-bus termination (240 Ω)
1.10 MicroVAX System Support Functions
System support functions are implemented by the system support chip (SSC). The SSC contains approximately 83,000 transistors in an 84-pin CERQUAD surface mount package. The SSC provides console and boot code support functions, operating system support functions, timers, and many ~xtra features, including the following:
- Word-wide ROM unpacking
- 1 Kbyte battery backed-up RAM
- Halt arbitration logic
- Console serial line
- Interval timer with 10 ms interrupts
- VAX standard time of year (TOY) clock with support for battery back-up
- IORESET register
- Programmable CDAL bus timeout
- Two programmable timers similar in function to the VAX standard interval timer
- A register for controlling the dignostic LEDs
1.11 Firmware
The firmware consists of 128 Kbytes of 16 bit-wide ROM, located on two 27512 EPROMs. The firmware gains control when the processor halts, and contains programs that provide the following services:
- Board initialization
- Power-up self-testing of the KA640 and MS650 modules
- Emulation of a subset of the VAX standard console (automatic/manual bootstrap, automatic/manual restart, and a simple command language for examining/altering the state of the processor)
- Booting from supported Q22-bus devices
- Multilingual capability
- MOP support
1.12 Clock Functions
All clock functions are implemented by the CVAX clock chip. The CVAX clock chip is a 44-pin CERQUAD surface mount chip that contains approximately 350 transistors, and provides the following functions:
- Generates two MOS clocks for the CPU, the floating point accelerator, and the main memory controller
- Generates three auxiliary clocks for other miscellaneous TTL logic
- Synchronizes reset signal for the CPU, the floating point accelerator, and the main memory controller
- Synchronizes data ready and data error signals for the CPU, floating point accelerator, and the main memory controller
Bron: KA640 CPU Module Technical Manual
Overzicht.
Blauwe connector: Front Panel
Grijze connector: DSSI en Memory-Bus
