topic Re: OVMS SCSI inquiry error using MSA$Util, show or set commands in Operating System - OpenVMS

OVMS SCSI inquiry error using MSA$Util, show or set commands

David Huizar — Tue, 08 Jan 2008 21:32:47 GMT

I have a site manager connecting to an OVMS 7.3-2 system at a remote site. We need to verify his external hot spare disks are set properly in the MSA1000 external storage. The system boots from the MSA1000 and he can get to all his data, so we know the system and data disks are accessable. What we are geting is a SCSI Inquiry Error when running MSA$Util on the OVMS system when it scans for the MSA controllers. Any information on the error would be helpful:

$ run sys$etc:msa_util.exe
MSA> show controllers

A default controller is not set. All matching controllers displayed

Error doing SCSI Inquiry to controller _$1$GGA1:. VMS Status = 24

Error doing SCSI Inquiry to controller _$1$GGA2:. VMS Status = 24

No controllers found matching request.

MSA> set controller $1$gga1:

Error doing SCSI Inquiry to controller _$1$GGA1:.Could not find a matching controller.

Any help would greatly be appreciated.

Thanks

David

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

Steven Schweda — Tue, 08 Jan 2008 22:25:35 GMT

I know nothing, but if that "VMS Status = 24"
is decimal, then:

ALP $ exit 24
%SYSTEM-W-EXQUOTA, process quota exceeded

As usual, figuring out which process quota
was exceeded is more of an ordeal than one
might wish.

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

David Huizar — Tue, 08 Jan 2008 22:31:28 GMT

Stee,

I'm thinking the manager may not have all priveleges set for his account if it's a process quota exceeded.

I'll have him $set proc/priv=all or try running MSA$Util with the SYSTEM account.

I'll get back to you.

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

Steven Schweda — Tue, 08 Jan 2008 22:36:46 GMT

Quotas and privileges are pretty independent
of each other.

A diligent search for EXQUOTA should turn up
one or more techniques for finding the
culprit (if that really is the problem).

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

Jim_McKinney — Tue, 08 Jan 2008 22:45:29 GMT

Do either $1$GGA1: or $1$GGA2: exist from VMS' perspective? If not, then you'll need to configure a numeric IDENTIFIER value on your MSA1000 (VMS requires this value to be numeric rather than Alpha) in order to get VMS to present them. Have your site manager issue a SHOW THIS command on the MSA1000 to see what you've got. I think that the command to set the ID value is something like "SET THIS/ID=nn".

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

David Huizar — Wed, 09 Jan 2008 00:26:59 GMT

Jim,

When the MSA1000 was installed the ID's were set:

CLI> SET THIS_CONTROLLER_ID 1
CLI> SET OTHER_CONTROLLER_ID 2

I get back in touch with the site manager tomorrow to see if he ses the devices $1$gga1 and $1$gga2 in OVMS.

Thanks

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

Hoff — Wed, 09 Jan 2008 02:47:20 GMT

$ x=f$mess(24)
$ show symbol x
X = "%SYSTEM-W-EXQUOTA, process quota exceeded"
$ x=f$mess(%x24)
$ show symbol x
X = "%SYSTEM-F-NOPRIV, insufficient privilege or object protection violation"
$

I'd bet on the latter.

That it's a hexadecimal status code.

I'd bet you're missing a privilege. Quite possibly one or more of DIAGNOSE, SHARE, PHY_IO or LOG_IO, but I haven't checked the MSA_UTIL documentation. (And I don't immediately find the MSA_UTIL documentation.)

Either turn'm all on and run sans "blade guards", or use security auditing to figure out which privilege(s) MSA_UTIL wants.

Stephen Hoffman
HoffmanLabs LLC

Re: OVMS SCSI inquiry error using MSA$Util, show or set commands

Hoff — Wed, 09 Jan 2008 02:49:28 GMT

Ok. It looks like it's definitely hexadecimal:

$ search sys$share:*.req ss$_exquota

******************************
SYS$COMMON:[SYSLIB]STARLET.REQ;1

literal SS$_EXQUOTA = 28;
literal SS$_EXQUOTASTRT = 10752;
literal SS$_EXQUOTAEND = 11007;
$ x=f$message(28)
$ show symbol x
X = "%SYSTEM-F-EXQUOTA, process quota exceeded"

$

Note the difference in the severity for the status.