mc sysman io auto issue

[Karl Rohwedder]

What kind of disk (IDE/SCSI/FC...), has it worked before or in another system, correctly jumpered?

regards Kalle

[Tru64Unix]

My system is RX4640 and hard disk type is SCSI.This disk works correctly in another system.

[Volker Halle]

Something is wrong on your system. SYS$ICBM.EXE should be installed automatically during boot through the entry in VMSIMAGES.DAT - if that does not happen, you may want to find out, why not !

As a workaround, try to manually install the image:

$ INSTALL ADD SYS$SHARE:SYS$ICBM.EXE

Then re-try the SYSMAN IO AUTO/LOG command.

Volker.

[Karl Rohwedder]

I assume we are speaking of the internal drive bays, are both configured correctly? The quickspec mentions a so-called duplex configuration, where each bay has its own scsi channel.

regards Kalle

[Tru64Unix]

Hi,Volker

Pls see the log below.
Normally when running "MC SYSMAN IO AUTO/LOG",it should wait a few seconds and then give some info.But on this system it did not wait.




CSD001$
CSD001$ recal /all
CSD001$
CSD001$ install add sys$share:sys$icbm
%INSTALL-E-FAIL, failed to CREATE entry for DISK$I64SYS:SYS$ICBM.EXE
-INSTALL-E-EXISTS, Known File Entry for a version of this file already exists
CSD001$
CSD001$ mc sysman io auto/log

%SYSMAN-I-OUTPUT, command execution on node CSD001
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-W-NOICBM, failed to find ICBM with prefix SYS$
%IOGEN-I-PREFIX, searching for ICBM with prefix DECW$
%IOGEN-W-NOICBM, failed to find ICBM with prefix DECW$
CSD001$

[#6]

Just a guess!!!

Try removing the image and then again installing both the image sys as well as decw

install remove sys$icbm.exe
install remove decw$icbm.exe

install add sys$share:sys$icbm.exe
install add sys$share:decw$icbm.exe

Regards,
ajaydec

[Volker Halle]

Try setting IAC$DEBUG - the image activator debug flags:

$ DEFINE/EXEC IAC$DEBUG FF

and re-try your SYSMAN command.

Volker.

[Volker Halle]

To get even more information from the image activator, use

$ DEFINE/EXEC IAC$DEBUG FFFFFFFF

Compare the results from a working system with the output of your failing system...

Volker.

[Tru64Unix]

hi volker,

could you pls find some infomation?

[John Gillings]

I don't think this is a real problem. As long as I can remember SYSMAN IO AUTO/FULL usually generates some errors on most systems (note that /FULL is not mentioned in HELP). On a V8.3 Alpha I get a bunch of -I- messages, plus:

%IOGEN-E-ACTERR, error activating ICBM
-RMS-E-FNF, file not found
%IOGEN-W-NOICBM, failed to find ICBM with prefix DECW$GRAPHICS_
%IOGEN-E-ACTERR, error activating ICBM
-RMS-E-FNF, file not found
%IOGEN-W-NOICBM, failed to find ICBM with prefix X25$
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-E-LOADERR, error configuring device SRA0, driver SYS$SRDRIVER.EXE
-RMS-E-FNF, file not found

I assume it's just the way AUTOCONFIGURE searches for devices and reports results. The PRIVINSTALL message is curious, but I wouldn't lose any sleep over it.

I also doubt it has anything to do with your disk problem. Repeat the IO AUTO command without /FULL or /LOG. If there are no messages, then I'd suggest you concentrate on the hardware. If there are messages post them here.