[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Software Product Integration Architecture |
|
Moderator: | STAR::HAMMOND |
|
Created: | Fri Apr 28 1989 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 370 |
Total number of notes: | 1977 |
370.0. "Problem with Motif 1.2-4 on OpenVMS VAX V7.1" by PGREEN::GRAVESG (Geoff Graves, Global Knowledge Network (UK)) Tue Apr 29 1997 05:55
I attach a string I posted in BULOVA::DECWINDOWS about a PCSI problem
encountered whilst attempting to upgrade from DECwindows Motif V1.2-3
to V1.2-4 on a VAX 3100/GPX running OpenVMS VAX V7.1.
(The last suggestion in 5829.3 resulted in the same error)
Any help gratefully received!
Thanks,
Geoff
<<< BULOVA::DISK$PUBLIC:[NOTES$LIBRARY]DECWINDOWS.NOTE;2 >>>
-< DECWINDOWS >-
================================================================================
Note 5829.0 1.2-4 install fails: VAXStation & V7.1 3 replies
PGREEN::GRAVESG "Geoff Graves, Global Knowledge Net" 34 lines 22-APR-1997 04: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
================================================================================
Note 5829.1 1.2-4 install fails: VAXStation & V7.1 1 of 3
GRIM::MESSENGER "Bob Messenger" 16 lines 22-APR-1997 16:05
--------------------------------------------------------------------------------
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
================================================================================
Note 5829.2 1.2-4 install fails: VAXStation & V7.1 2 of 3
PGREEN::GRAVESG "Geoff Graves, Global Knowledge Net" 20 lines 23-APR-1997 05:15
-< Same error again! >-
--------------------------------------------------------------------------------
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
================================================================================
Note 5829.3* 1.2-4 install fails: VAXStation & V7.1 3 of 3
GRIM::MESSENGER "Bob Messenger" 11 lines 23-APR-1997 12:04
--------------------------------------------------------------------------------
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
T.R | Title | User | Personal Name | Date | Lines |
---|
370.1 | Need more info... | STAR::HAMMOND | Charlie Hammond -- ZKO3-04/S23 -- dtn 381-2684 | Tue Apr 29 1997 12:38 | 10 |
| I have DECwindows Motif V1.2-4 running on a 3100. No problems.
Please do the following and post the output.
(These commands will product 132 coll output.)
$ product show product * /full
$ product show history /full
$ product show object [decw$defaults] /full
|
370.2 | Info requested in .-1 | PGREEN::GRAVESG | Geoff Graves, Global Knowledge Network (UK) | Wed Apr 30 1997 05:56 | 83 |
| Re .1
Thanks for the reply, Charlie.
The displays you asked for follow; unfortunately the VT emulator I'm
using (don't ask!) doesn't play at 132 mode. The displays are still
usable though.
Hope this helps,
Geoff
$
$ PROD SHOW PROD * /FULL
----------------------------------- ----------- ------------ -------------------
---------------- -----------------------------------
PRODUCT KIT TYPE STATE MAINTENANCE
REFERENCED BY
----------------------------------- ----------- ------------ -------------------
---------------- -----------------------------------
DEC VAXVMS DECNET_PHASE_IV V7.1 Full LP Available
DEC VAXVMS DWMOTIF V1.2-3 Full LP Available
DEC VAXVMS VMS V7.1 Transition Available
DEC VAXVMS DECNET_PHASE_IV V7.1
----------------------------------- ----------- ------------ -------------------
---------------- -----------------------------------
3 items found
VMSINSTAL history file contains additional information
$
$
$ PROD SHOW HISTORY * /FULL
----------------------------------- ----------- ----------- --------------------
--- ------------ ----------------------------------
PRODUCT KIT TYPE OPERATION DATE AND TIME
ERR USER NAME REMARK
----------------------------------- ----------- ----------- --------------------
--- ------------ ----------------------------------
DEC VAXVMS DECNET_PHASE_IV V7.1 Full LP Install 18-MAR-1997 10:37:27
0 SYSTEM
DEC VAXVMS VMS V7.1 Transition Reg Product 11-MAR-1997 13:01:47
0 SYSTEM
DEC VAXVMS VMS V7.0 Transition Reg Product 04-JAN-1995 12:16:33
0 SYSTEM
DEC VAXVMS DWMOTIF V1.2-3 Full LP Install 05-JUL-1995 13:41:59
0 GRAVES
DEC VAXVMS VMS V6.2 Transition Reg Product 23-JUN-1995 23:04:19
0 SYSTEM
DEC VAXVMS VMS V6.1 Transition Reg Product 22-JUN-1994 12:43:57
0 SYSTEM
----------------------------------- ----------- ----------- --------------------
--- ------------ ----------------------------------
6 items found
VMSINSTAL history file contains additional information
$
$
$
$ PROD SHO OBJ [DECW$DEFAULTS] /FULL
----------------------------------------------- ----------------- -------- -----
--------------------------- ------------------------
OBJECT NAME OBJECT TYPE STATUS DESTI
NATION ROOT DIRECTORY PROVIDED BY
----------------------------------------------- ----------------- -------- -----
--------------------------- ------------------------
[DECW$DEFAULTS] directory OK DISK$
VAXSYS_7.1:[VMS$COMMON.] DWMOTIF V1.2-3
[DECW$DEFAULTS] directory OK DISK$
VAXSYS_7.1:[VMS$COMMON.] VMS V7.1
----------------------------------------------- ----------------- -------- -----
--------------------------- ------------------------
2 items found
$
$
|
370.3 | | STAR::HAMMOND | Charlie Hammond -- ZKO3-04/S23 -- dtn 381-2684 | Wed Apr 30 1997 09:46 | 43 |
| RE: Note 370.2 by PGREEN::GRAVESG
Hmm..
I'll look at this some more, but one thing I see right off is that apparently
you've changed the system disk volume label when you uprgraded to V7.1.
This USED to "confuse" PCSI if you didn't do a PRODUCT REGISTER VOLUME,
but I don't think this is the problem.
The PRODUCT SHOW OBJECT output seems to indicate that you're new system disk
volume label is "VAXSYS_7.1". I think that the period (".") may be causing
problems.
>$ PROD SHO OBJ [DECW$DEFAULTS] /FULL
>----------------------------------------------- ----------------- --------
>OBJECT NAME OBJECT TYPE STATUS
> -------------------------------- ------------------------
> DESTINATION ROOT DIRECTORY PROVIDED BY
>----------------------------------------------- ----------------- --------
> -------------------------------- ------------------------
>[DECW$DEFAULTS] directory OK
> DISK$VAXSYS_7.1:[VMS$COMMON.] DWMOTIF V1.2-3
^^^^^^^^^^
While INIT and SET VOL/LABEL allow any ascii characters, OpenVMS doesn't always
work fully correctly if you use any characters other than A-Z, 0-9, dollar
("$"), underscore ("_") and hyphen ("-"). I suspect that PCSI is tripping
over this in some way.
I suggest that you SET VOL/LABEL to change the system disk volume label.
Then REBOOT (this is a MUST!) and do a PRODUCT REGISTER VOLUME. And
finally try the installation again.
Let us know if this works.
...and, yes, your right -- sometimes it is a long way around! <smile>
..........................................................................
BTW -- here is an exercise for the brave and/or foolish. Set the label on
one of your disks to a string that include an exclamation point ("!").
**** DON'T DO THIS ON A PRODUCTION SYSTEM OR AT A CUSTOMER SITE!!!!!!
(Hint: "!" is the DCL comment introducer.)
|
370.4 | Problem solved!! | PGREEN::GRAVESG | Geoff Graves, Global Knowledge Network (UK) | Thu May 01 1997 08:08 | 35 |
| Re .-1
Thanks very much, Charlie - that did the trick!!
The "." in the system disk label was the problem - that will teach me to read
the HELP documentation, won't it!
SET
VOLUME
/LABEL
/LABEL=volume-label
Specifies a 1- to 12-character ANSI name to be encoded on the
volume. The specified label remains in effect until it is changed
explicitly; dismounting the volume does not affect the label.
>> Digital strongly recommends that a volume label should consist
>> only of alphanumeric characters, dollar signs ($), underscores
>> (_), and hyphens (-).
If you change the volume label on an OpenVMS system disk, you
should also update the POLYCENTER Software Installation utility
database. To accomplish this, use the PRODUCT REGISTER VOLUME
command to replace the old volume label with the new volume ...
Thanks again!
Geoff
PS: The "!" in a volume label is a good test for trainee system
managers and students on courses!
|