topic Re: mc sysman io auto issue in Operating System - OpenVMS

mc sysman io auto issue

Tru64Unix — Mon, 24 Sep 2007 01:40:58 GMT

Hi,

When I run "mc sysman io auto/full" on my system with OpenVMS8.3 for IA64.I got some errors as below.Anybody can help me ? Thanks a lot.

CSD001$
CSD001$ mc sysman io auto/full

%SYSMAN-I-OUTPUT, command execution on node CSD001
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM_401F
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM_40
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM
%IOGEN-E-ACTERR, error activating ICBM
-SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%IOGEN-W-NOICBM, failed to find ICBM with prefix SYS$
%IOGEN-I-PREFIX, searching for ICBM with prefix DECW$
%IOGEN-I-ACTIVATE, activating ICBM DECW$ICBM_401F
%IOGEN-I-ACTIVATE, activating ICBM DECW$ICBM_40
%IOGEN-I-ACTIVATE, activating ICBM DECW$ICBM
%IOGEN-E-ACTERR, error activating ICBM
-RMS-E-FNF, file not found
%IOGEN-W-NOICBM, failed to find ICBM with prefix DECW$
CSD001$

Re: mc sysman io auto issue

Jur van der Burg — Mon, 24 Sep 2007 10:02:37 GMT

You probably have a logical name "ICBM" defined somewhere.

Jur.

Re: mc sysman io auto issue

Daniel Fernandez Illan — Mon, 24 Sep 2007 11:25:51 GMT

Hi

Help message reponse:

The image SYS$SHARE:SYS$ICBM.EXE is not present on your system disk or is not installed.

Command:

$dir sys$share:SYS$ICBM.EXE

Reponse:

Directory SYS$COMMON:[SYSLIB]

SYS$ICBM.EXE;1

Check to see whether the image file exists and verify that it is installed as a known image.

Command:

$install list SYS$ICBM.EXE

Reponse:

DISK$ALPHASYS:.EXE
SYS$ICBM;1

Saludos.
Daniel.

Re: mc sysman io auto issue

Tru64Unix — Tue, 25 Sep 2007 01:15:44 GMT

Hi,Daniel

Thanks.when I run "install list sys$icbm.exe",it says "file not found" on all nodes.
==========================================
CSD002$

CSD002$ dir sys$share:sys$icbm.exe

Directory SYS$COMMON:[SYSLIB]

SYS$ICBM.EXE;1

Total of 1 file.

CSD002$

CSD002$ dir sys$common:[syslib]sys$icbm.exe

Directory SYS$COMMON:[SYSLIB]

SYS$ICBM.EXE;1

Total of 1 file.

CSD002$

CSD002$

CSD002$ install list sys$icbm.exe
%INSTALL-E-OPENIN, error opening DISK$I64SYS:SYS$ICBM.EXE; as input
-RMS-E-FNF, file not found
CSD002$

Re: mc sysman io auto issue

Edwin Gersbach_2 — Tue, 25 Sep 2007 01:55:47 GMT

Try INSTALL LIST SYS$SHARE:ICBM.EXE

The default is SYS$SYSTEM which is wrong for ICBM

Edwin

Re: mc sysman io auto issue

Edwin Gersbach_2 — Tue, 25 Sep 2007 02:00:02 GMT

should be
INSTALL LIST SYS$SHARE:SYS$ICBM.EXE
of course

Sorry for the typo
Edwin

Re: mc sysman io auto issue

Richard Brodie_1 — Tue, 25 Sep 2007 03:22:02 GMT

They look harmless to me. Have you got a real problem?

Re: mc sysman io auto issue

Daniel Fernandez Illan — Tue, 25 Sep 2007 04:57:23 GMT

Edwin, you are in the certain thing
The exactly command is:

$install list sys$share:SYS$ICBM.EXE

Sorry for my mistake.

If the image is not well installed, then (help says):

For instructions on installing a known image, refer to the Install utility chapter in the HP OpenVMS System Management Utilities Reference Manual. If you still have problems, reinstall OpenVMS onto your system disk or contact an HP support representative for assistance.

After install image, you might use SYSMAN IO SHO PREFIX and SYSMAN IO SET PREFIX to check IO AUTOCONFIGURE options

See:
http://h71000.www7.hp.com/doc/83final/6048/6048pro_079.html#index_x_2117
link.

Saludos.
Daniel.

Re: mc sysman io auto issue

Volker Halle — Tue, 25 Sep 2007 08:27:10 GMT

You should find an entry for SYS$SHARE:SYS$ICBM.EXE in SYS$MANAGER:VMSIMAGES.DAT - this should cause the image to be automatically installed during boot.

Volker.

Re: mc sysman io auto issue

Tru64Unix — Tue, 25 Sep 2007 22:01:01 GMT

Hi,

The problem is when I add a new hard disk into system and run "MC SYSMAN IO AUTO /LOG".System can not find the newly added hard disk.

Re: mc sysman io auto issue

Karl Rohwedder — Tue, 25 Sep 2007 23:58:53 GMT

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

regards Kalle

Re: mc sysman io auto issue

Tru64Unix — Wed, 26 Sep 2007 00:20:40 GMT

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

Re: mc sysman io auto issue

Volker Halle — Wed, 26 Sep 2007 01:16:45 GMT

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.

Re: mc sysman io auto issue

Karl Rohwedder — Wed, 26 Sep 2007 03:18:28 GMT

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

Re: mc sysman io auto issue

Tru64Unix — Wed, 26 Sep 2007 22:01:24 GMT

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$

Re: mc sysman io auto issue

Thu, 27 Sep 2007 04:05:14 GMT

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

Re: mc sysman io auto issue

Volker Halle — Sun, 30 Sep 2007 02:24:05 GMT

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

$ DEFINE/EXEC IAC$DEBUG FF

and re-try your SYSMAN command.

Volker.

Re: mc sysman io auto issue

Volker Halle — Sun, 30 Sep 2007 02:26:34 GMT

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.

Re: mc sysman io auto issue

Tru64Unix — Tue, 09 Oct 2007 04:51:37 GMT

hi volker,

could you pls find some infomation?

Re: mc sysman io auto issue

John Gillings — Tue, 09 Oct 2007 20:31:57 GMT

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.