[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssag::ask_ssag

Title:	Ask the Storage Architecture Group
Notice:	Check out our web page at http://www-starch.shr.dec.com
Moderator:	SSAG::TERZAN

Created:	Wed Oct 15 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6756
Total number of notes:	25276

6554.0. "%pcsi-e-openout" by MDR01::NIEVES (MCS Madrid) Mon Apr 07 1997 02:51

    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
     Hi,
    
        a customer has an ALPHA 8200 with VMS 6.2-1H3. There is a HW raid 1.
        The system has the following disks:
    
        ALPHA3$DKD0 (system disk)
        ALPHA3$dra0 (shadowing for 4 disks)
        ALPHA3$dra1 (shadowing for 4 disks)
        ALPHA3$dra2 (shadowing for 12 disks)
        ALPHA3$dva0 (diskette)
        ALPHA3$dkb400 (cd)
    
        She is trying to install the "Storageworks raid array 200 on line
    mgmt utility" following the manual.
    
        She tried installing it using the system disk or data disk (drax),
    but an error appears during the installation in both cases. We really 
    don't know if we are missing something, or why is the reason for the error.
    
        This is part of the installation:
    
        $ @DVA0:[SWXCR$KIT]INVOKE_PCSI.COM
        Enter target device name: DRA0
        ...
        Requires 922 disk blocks
        ...
        Do you want all the default values for this product (yes)
        Do you want to view the values (yes)
        DEC AXPVMS SWXCR V3.0 SXWCR SOFTWARE FOR OPENVMS AXP (available)
        DEC AXPVMS VMS V6.2-1H1 (available)
        are you satisfied with the values (yes)
           %PCIUI-I-DONEASK, execution phase starting
        the following product will be installed
        ...
        %PCSI-I-VOLINFO, estimated space information for volume DISK$ALPHA3
        -PCSU-I-VOLSPC, 0 requeired; 2134608  available; 2134603 net.
        %PCSI-I-VOLINFO, estimated space information for volume DISK$ARENAL
        -PCSU-I-VOLSPC, 0 requeired; 16501632 available; 1650632 net.
        portion done:0%
    
        %PCSI-E-OPENOUT, error opening
        DISK$ARENAL:[VMS$COMMON.][DECW$DEFAULTS.USER]SWXCRMGR.DAT;*
        as output
        -RMS-E-DNF, directory not found
        -SYSTEM-W-NOSUCHFILE, no such file
        %PCIS-E-OPFAILED, operation failed
        Terminating is strongly recommnenede. Do you want to terminate (yes)
        %PCSI-E-CANCEL-WIP ...
    
        ***************************************************
    
        Now, disk$arenal is a logical pointing to ALPHA$DRA0:
        and disk$alpha3 pointing to ALPHA3$DKAD0: (SYSTEM DISK).
    
        If we look for vms$common.dir in disk$arenal, this doesn't appear.
    
        What are we doing wrong, or missing something,
    
        HELP needed,
    
        Regards,
    
        Nieves

T.R	Title	User	Personal Name	Date	Lines
6554.1	Corrupt System Disk File Structure...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Apr 07 1997 13:11`	25
	This is not a storage question, this appears to be an OpenVMS question... : If we look for vms$common.dir in disk$arenal, this doesn't appear. This SYS$SYSDEVICE:[000000]VMS$COMMON.DIR file is the system root entry for the OpenVMS operating system system disk file structure -- the SYSCOMMON.DIR directory entries in each SYS$SYSDEVICE:[SYS] directory are all aliases for this VMS$COMMON directory file... In other words, if you do not have SYS$SYSDEVICE:[VMS$COMMON], then you have a corrupt system disk file structure. You may be able to resolve problem this via SET FILE/ENTER commands and via ANALYZE/DISK, depending on any other structure corruptions that might be lurking. -- We might be able to provide a suggested sequence for how to repair this situation... Post a DIRECTORY/FILE SYS$SYSDEVICE:[SYS]SYSCOMMON.DIR for a start, and post a DIRECTORY/FILE SYS$SYSDEVICE:[000000]SYS.DIR,VMS.DIR.
6554.2	Sounds like a careless .COM file	SUBSYS::BROWN	SCSI and DSSI advice given cheerfully	`Tue Apr 08 1997 09:09`	19
	Either there's a bug in INVOKE_PCSI.COM, or it needs a release note which says to run it only from the system disk. Since the target device changes from DISK$ALPHA3 to DISK$ARENAL in the middle of the procedure, I suspect the procedure is assuming it's being run from the system disk. For a workaround, try setting default to somewhere on DRA0 before running the .COM file. > $ @DVA0:[SWXCR$KIT]INVOKE_PCSI.COM > Enter target device name: DRA0 > ... > %PCSI-I-VOLINFO, estimated space information for volume DISK$ALPHA3 > -PCSU-I-VOLSPC, 0 requeired; 2134608 available; 2134603 net. > %PCSI-I-VOLINFO, estimated space information for volume DISK$ARENAL > -PCSU-I-VOLSPC, 0 requeired; 16501632 available; 1650632 net. > portion done:0%
6554.3	more info	MDR01::NIEVES	MCS Madrid	`Wed Apr 09 1997 09:08`	41
	Hi, well, first of all: $DIR/FILE SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR directory SYS$SYSDEVICE:[SYS0] SYS$COMMON.DIR (15,1,0) $DIR/FILE SYS$SYSDEVICE:[000000]SYS.DIR directory SYS$SYSDEVICE:[000000] SYS0.DIR (11,1,0) $DIR/FILE SYS$SYSDEVICE:[000000]VMS.DIR directory SYS$SYSDEVICE:[000000] VMS$COMMON.DIR Total 1 file. This seems to be correct. ************************************ The other test, she $set def DRA0:[000000] executed the procedure $@DVA0_[SWXCR$KIT]INVOKE_PCSI.COM obtains the same result as I mentioned in .0 I don't know what is wrong, any clue would help. Regards, Nieves
6554.4	invoke_pcsi??	MDR01::NIEVES	MCS Madrid	`Wed Apr 09 1997 09:50`	17
	Hi, the strange thing, is that when the procedure is executed, if you say the target disk is the system disk, it also looks for SWXCRMGR.DAT in systemdisk:[vms$common.][decw$defaults.user]swxcrmgr.dat and this file isn't suppose to be in the disk, or does the invoke_pcsi.com procedure copy this and other files to disk? What does the invoke_pcsi.com do? Has anyone configured this in VMS? Some collegues have done it in a UNIX enviroment, but not VMS. Thanks Nieves