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

Conference bulova::decwindows

Title:DECWINDOWS
Notice:DECwindows Motif V1.2-4 SSB kits: note 5519
Moderator:GRIM::MESSENGER
Created:Wed Nov 28 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5861
Total number of notes:24081

5829.0. "1.2-4 install fails: VAXStation & V7.1" by PGREEN::GRAVESG (Geoff Graves, Global Knowledge Network (UK)) Tue Apr 22 1997 05:46

Can anyone shed some light on this please?

I'm running Motif 1.2-3 on a VAXstation 3100/GPX with OpenVMS VAX V7.1.

When upgrading to Motif 1.2-4 using a copy of the PCSI kit from BULOVA::,
I get the following error immediately after the   "Portion done: 0%" 
message:

%PCSI-E-OPENOUT, error opening [SYSHLP]DECW$MOTIFU3012.RELEASE_NOTES as output
-RMS-F-SYN, file specification syntax error
%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended.  Do you want to terminate?  [YES]


If I say "No" to this, I get the same error message for a number of files
[SYSMGR]DECW$CHECK_PARAMS.COM
[SYSMGR]DECW$AUTOGEN.COM
[000000]
and others.

All these files exist, so what's the problem???  It looks like a bug in 
PRODUCT INSTAL, but apart from the entries in Note 5530.*, which were not 
resolved, I can't find any other reference to this?

Surely, somebody must have installed 1.2-4 on VAXstations with OpenVMS
V7.1?

Help please?

Thanks,

Geoff
T.RTitleUserPersonal
Name		DateLines
5829.1GRIM::MESSENGERBob MessengerTue Apr 22 1997 17:0516
Did you invoke pcsi_installation.com to perform the installation?

It sounds like this problem might be caused by the definition of either
pcsi$destination or sys$sysdevice on your system.  pcsi$destination is a
logical name that specifies the device and directory where you want to
install the product, in this case DECwindows Motif.  If you don't define
pcsi$destination it defaults to sys$sysdevice:[vms$common].  You can also
specify the destination by using the /destination qualifier to the
"product install" command.

Apparently there is something about the destination that PCSI doesn't
like.  If sys$sysdevice is a search list maybe there is a problem with one
of the devices or directories in the list.  Try redefining the process
version of sys$sysdevice and see whether that fixes the problem.

				-- Bob
5829.2Same error again!PGREEN::GRAVESGGeoff Graves, Global Knowledge Network (UK)Wed Apr 23 1997 06:1520
    Re .1
    
    Thanks for your reply, Bob.
    
    I hadn't used PCSI_INSTALLATION.COM, but have just done so with exactly
    the same error message appearing.
    
    SYS$SYSDEVICE is fine, but I don't have PCSI$DESTINATION defined.
    
    As the error message (see .0) implies a *device* specification error
    (the directory and file names really do exist), I defined
    PCSI$DESTINATION as SYS$SYSDEVICE and retried - again the same
    error. (I tried it with and without /EXEC)
    
    
    Can you suggest anything else to try?  I'm flummoxed!
    
    Thanks,
    
    Geoff
5829.3GRIM::MESSENGERBob MessengerWed Apr 23 1997 13:0411
Re: .2

>    As the error message (see .0) implies a *device* specification error
>    (the directory and file names really do exist), I defined
>    PCSI$DESTINATION as SYS$SYSDEVICE and retried - again the same
>    error. (I tried it with and without /EXEC)
    
Try defining it as SYS$SYSDEVICE:[VMS$COMMON].  If that doesn't work either
post a note in EVMS::SPIA or enter a QAR.

				-- Bob
5829.4Problem solved!!PGREEN::GRAVESGGeoff Graves, Global Knowledge Network (UK)Thu May 01 1997 08:1210
    Re -.*
    
    Problem solved - I posted the query in EVMS::SPIA (370.0) and my
    problem was a "." in the system disk label:-  "VAXVMS_7.1" !
    See 370.* for the full story, but don't be tempted to put anything
    other than the standard characters in a volume label!!
    
    Thanks for the suggestions in -.*
    
    Geoff