SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Wednesday, December 21

21-Dec-2005

Hardware problems
HSZ50 has been initialized and port alloocation classes set - Diana can be started, but both Daphne and Dido wont' even startup in console mode - ends up in " e6...." and then give s list of addresses, anding with this text:

fe.fd.fc.fb.fa.f9.f8.breakpoint expected at PC110940, XDELTA not loaded
f7.f6.f5.
ef.de.ee.ed.ec.f4.eb.esa.e9.e8.e7.e6....

and nothing will happen.

Diana could boot, will see all disks as $1$ - it's own (standard) allocation class, MSCP parameters are:
SYSGEN> SHO MSCP
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
MSCP_LOAD 1 0 0 16384 Coded-valu
MSCP_SERVE_ALL 2 4 0 15 Bit-Encode
MSCP_BUFFER 1024 1024 256 -1 Coded-valu
MSCP_CREDITS 32 32 2 1024 Coded-valu
MSCP_CMD_TMO 0 0 0 2147483647 Seconds D

but SYS$DEVICES.DAT contains the right code:

[Port DIANA$PKB]
allocation class 116

and the devices can not be accessed:

$ init dkb100
_Label: alpha082
%INIT-F-MEDOFL, medium is offline
$


Have to dig through the manulas to find out why....(or someone to tell me)

The weird thing is: the Aplhastations could be started one moment, and booted, where the shared SCSI disks could not be initialized during startup. But after all has een switched off, things go wrong - severely.

Security
Not checked today...

0 Comments:

Post a Comment

<< Home