Getting Analyze/error info for HSD10 Connected Disks

[Jim Maxwell]

Hi,

As noted in the topic title I am looking for info. on how to get specific disk error information using the analyze/error utility for HSD10 connected shadowset disks such as a shadowset like this :-

$ sh dev dsa22

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA22: Mounted 0 TORNESS_DATA 971523 3 2
$3$DIA310: (HSD3) ShadowSetMember 2 (member of DSA22:)
$3$DIA1310: (HSD7) ShadowSetMember 0 (member of DSA22:)
$

Where you do not seem to be able to use either :-

/include=dsa22: or/include=$3$dia1310: etc.

Any help greatly appreciated as I am trying to generate some historic error log analysis by disk ID over a long period of time.

[Arch_Muthiah]

Jim,

These are the commands to look into shadow set disks structure, but not analyze/error...

Try this...
$ ANALYZE/DISK_STRUCTURE/SHADOW/BRIEF DSA716:

The other related commands are
SET SHADOW and SHOW SHADOW

Archunan

[Volker Halle · Accepted solution]

Jim,

if you're using HSD10s, you are probably running a VAX and the ANAL/SHAD command is not available. This command would also just compare the contents of the shadowset members and NOT report any information from ERRLOG.SYS

For including disk errors, you just need to use the device name (without the allocation class), i.e. /INCLUDE=DIA310: instead of /INCLUDE=$3$DIA1310:

Including DSA devices does not seem to be supported:

VAXVMS $ anal/err/inc=dsa11
Error Log Report Generator Version V6.1
%ERF-F-INVQUAVAL, value 'DSA11' invalid for /INCLUDE qualifier

Please provide the exact version of OpenVMS you're running ? Which architecture ?

You may want to consider using DECevent ($ DIAGNOSE) as that tool does not seem to reject DSA device names.

Volker.

[Arch_Muthiah]

Jim/Volker,

OpenVMS VAX Version 5.5-2 and OpenVMS Alpha systems 6.1 and later will support HSD10 controllers.

Hp clearly mentioned that shadow member can not be analyzed using $ana/erro/include=disk error.log

For this purpose only HP added this feature in VMS 7.3-2 onwords to analyze shadow set member using this...
$SET Shadow, $show shadow, and $ANALYZE/DISK/SHADOW disk:


Archunan

[Jim Maxwell]

Hi - thanks for all the rapid responses :)

The system is running OpenVMS 6.2 ON VAX

I have tried using the dia1310: syntax but this also seems to get get rejected with the same error message as the dsa22: syntax

It is actually the dia1310: level disk history I am after anyway so not having the ability to analyze/error on dsa volumes is not a problem right now......

Any more suggestions ?

[Volker Halle]

Archunan,

ANAL/DISK/SHADOW is something completely different. It compares the data on the shadowset members for discrepancies. It does NOT analyse the errorlog entries for DSAn: devices.

DECevent V3.3 accepts /INCL=DSA11 as an include qualifier.


Jim,

I'm also running OpenVMS VAX V6.2 and I do not get a %ERF-F-INVQUAVAL error when specifying /INCL=DIA1310 - although I don't have such a device and can't tell, whether ANAL/ERR would find errors from that device unit. Can you supply the command line and the error message ?

Volker.

[Jim Maxwell]

Hi Volker,

Thanks for the reply - is the DEcEvent product included in VMS 6.2 as standard ?

Unfortunately I cant post any more info. from sute till next turs. as I'm off on a course next week :( but I will post back later next week

[Uwe Zessin]

No, DECEVENT is the start of VMS not being able to analzye its own errorlogs :-(

It need to be installed separately
http://h18023.www1.hp.com/support/svctools/decevent/

I really hope for you that the quality has much improved since I had installed it the first time - please make a full, verified backup of your system disk.

[Arch_Muthiah]

I accept Volker's info. Yes, if Jim has DECEVENT installed, he can go ahead using /INCL qualifier.

Yes Volker, HSD members can not be used in $ana/erro log command, I mentioned this, I just gave alternate option to analyze these HSD member.

Thanks
Archunan

[Arch_Muthiah]

I accept Volker's info. Yes, if Jim has DECEVENT installed, he can go ahead using /INCL qualifier.

If you don't have devevent, this can be installed from the link Mr.Uwe mentioned.

Yes Volker, HSD members can not be used in $ana/erro log command, I mentioned this, I just gave alternate option to analyze these HSD member.

Thanks
Archunan

[Jim Maxwell]

Thanks once enore for the further input - but I'm getting a little woried about the Decevent tool :( can someone please explain the possible issues/problems ? and why I would need to back up and verify my disks before using an errorlog analysis tool (presuming that is what it is) ?

Also can anyone out there confirm why/whether I can or cant slect the diaxxxx: dievices in the standard analyze/error command using /include ? is this a known problem or restriction with HSD10 connected /mscp served devices ?

Thanks.
Jim

[Volker Halle]

Jim,

DECevent V3.4 (VAX) explicitly supports bit-to-text errlog translation for HSD10 controllers.

The DECevent tool has first been developped on UNIX, so it is not fully OpenVMS aware (e.g. it installs into the specific root of each system, which is an annoyance on shared system disks), but with the latest version V3.4, it's useable. As with all product installations using @VMSINSTAL, it's your decision how you answer the question:

* Are you satisfied with the backup of your system disk [YES]?

DECevent (by default) only installs on your system disk, so there is no need to worry about any of your other disks. And I wouldn't even worry about the system disk.

Note that ANAL/ERR on OpenVMS VAX continues to work even up to V7.3, it only stopped working as of OpenVMS Alpha V7.1-2 with the introduction of a new errlog header format.

The DECevent /FSTERR qualifier produces a one-line report per disk or tape error and may also work for DIA devices.

Again, using /INCL=DIA1310 does not fail with a syntax error on OpenVMS VAX V6.2, so please provide the error message you're seeing when trying to analyse your HSD disks.

Volker.

[Jim Maxwell]

Thanks Volker - that helps a lot :)

Does the latest version you mention work o.k. on VMS 6.2 ?

I will post back the error mesages when I can get access tothe systems next week - may be Thursday though......

I did think tha it should be possible to use the standard analyze/error util though and this would obviously be preferable as I wouldn't need to go through our change management process ;)

Is there any licensing/support restrictions on the Decevent tool ?

Thanks again.

Jim

[Volker Halle]

Jim,

DECevent V3.4 is supported on OpenVMS VAX V6.2 and all previous versions (says the release notes). I'm running V3.3 on OpenVMS VAX V6.2.

If you can or would want to mail me your ERRLOG.SYS, I could at least try to run it through DECevent and see if it works and can translate the DIA1310 disk errors...

Volker.

[Jim Maxwell]

Hi Volker - thanks for confirming the Decevent status on V6.2 and also thanks for the kind offer to try out Decevent on your system.

I may take you up on thatlater so thanks again.

Jim