Re: VMS83A_UPDATE V11

In article <4b21116a$1@xxxxxxxxxxxxxxxxxxx>, peter@xxxxxxxxxxxxxx (Peter 'EPLAN' LANGSTOeGER) writes:
In article <d5db01aa-e7f6-4561-8525-f15616723c2d@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, Volker Halle <volker_halle@xxxxxxxxxxx> writes:
VMS83A_UPDATE-V1100 has been put 'on hold'.

For those of you who hadn't noticed yet:

VMS83A_UPDATE-V1100 reappeared on 6-DEC-2009 (File date is 4-DEC-2009
instead of 26-NOV-2009 as before), repackaged to include the following note:

During the installation of this UPDATE kit, you may see the
following error during the installation of PTHREAD kit.

%PCSI-I-PRCOUTPUT, output from subprocess follows ...
%IMGACT-F-SYMVECMIS, shareable image symbol vector table mismatch
-IMGACT-F-FIXUPERR, error when PTHREAD$RTL referenced
SYS$BASE_IMAGE

%PCSI-E-INSTALLERR, error executing DCL INSTALL command
-IMGACT-F-SYMVECMIS, shareable image symbol vector table mismatch
%PCSI-E-OPFAILED, operation failed Terminating is strongly
recommended. Do you want to terminate? [YES]

You should answer "NO" to this question and allow the installation
to continue. PTHREAD kit has a dependency on the SYS kit. PTHREAD
kit expects that the system be rebooted after installing SYS kit.
The error is thrown as both the dependent kits are part of the same
UPDATE kit, and there is no interim reboot of the system.

It is important to note that once the UPDATE kit is installed and
the system is rebooted, this error will not impact the system and
the correct images will be in use.


So, the kit is the same, and if you had VMS83A_PTHREAD and VMS83A_SYS
installed before the installation attempt of VMS83A_UPDATE V11 (like me)
you hadn't seen the SYMVECMIS error (only if you didn't reboot between
SYS and PTHREAD ;-). Otherwise, simply answer "no" to the abort question.

Sorry for follow-up my own posting, but I have a new situation:

Installing UPDATE V11 (filedate 4-DEC-2009) on one of my Alphas gave me:

%PCSI-W-NOTFNDKIT, imglib module PTHREAD$DBGSHR from product DEC AXPVMS VMS83A_U
PDATE V11.0 was in previous kit but is not in current kit
%PCSI-W-NOTFNDKIT, imglib module PTHREAD$RTL from product DEC AXPVMS VMS83A_UPDA
TE V11.0 was in previous kit but is not in current kit
%PCSI-W-NOTFNDKIT, imglib module SDA$SHARE from product DEC AXPVMS VMS83A_UPDATE
V11.0 was in previous kit but is not in current kit
%PCSI-W-NOTFNDKIT, imglib module SYS$PEDRIVER from product DEC AXPVMS VMS83A_UPD
ATE V11.0 was in previous kit but is not in current kit
%PCSI-W-NOTFNDKIT, imglib module SYS$PEDRIVER_MON from product DEC AXPVMS VMS83A
_UPDATE V11.0 was in previous kit but is not in current kit

%PCSI-W-KITNOTSAME, kit for product DEC AXPVMS VMS83A_UPDATE V11.0 differs from
same version of product previously installed
-PCSI-W-OPERMAYDEL, objects (identified above) previously installed may be delet
ed and not replaced
Do you want to continue? [YES]

This message was new for me (and is not the one mentioned in the release notes)

Problem was identified as installing UPDATE V11 (DEC4) over UPDATE V11 (NOV26)

So, this begs the questions:
Are both UPDATE V11 kits identical (besides the release notes)?
Does installing a kit over itself always produce such KITNOTSAME messages?

Does anyone already have the answers?

TIA

-EPLAN

PS: In case, you haven't noticed:

$ help/mess kitnotsame
%MSGHLP-F-NOTFOUND, message not found in Help Message database
$ help/mess opermaydel
%MSGHLP-F-NOTFOUND, message not found in Help Message database
$ help/mess notfndkit
%MSGHLP-F-NOTFOUND, message not found in Help Message database
--
Peter "EPLAN" LANGSTÖGER
Network and OpenVMS system specialist
E-mail Peter@xxxxxxxxxxxxxx
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
.

Relevant Pages

  • screend.conf - help an idiot
    ... > You might want to try the appropriate patch listed ... > Modification Type: NEW KIT ... > The Patch Kit Installation Instructions and the ... > 2 Special Instructions ...
    (Tru64-UNIX-Managers)
  • Re: 625 - 405 standards converter from the 60s
    ... SiS which included the installation and audio testing of the coders ... chassis extender was causing the pots to shift sufficiently for the ... I can remember a slightly fraught meeting, chaired by the SiS project ... Department, who built the kit, and who took the line that it was ...
    (uk.tech.broadcast)
  • Re: 625 - 405 standards converter from the 60s
    ... SiS which included the installation and audio testing of the coders ... I can remember a slightly fraught meeting, chaired by the SiS project ... Department, who built the kit, and who took the line that it was ... engineering design of the BBC kit was carried out by Designs ...
    (uk.tech.broadcast)
  • Re: Undocumented (?) PCSI error messages
    ... > The OpenVMS engineers responsible for the POLYCENTER Software Installation ... if this operation specifies a full product kit along with the ... any products that may be installed to satisfy software dependency ... * This product does not have any configuration options. ...
    (comp.os.vms)
  • [VulnWatch] Tru64 Unix (various versions) stdio vulnerability
    ... Attached is the announcment for Tru64 Unix version 4.0G... ... Modification Type: NEW KIT ... The Patch Kit Installation Instructions and the Patch Summary and Release ...
    (VulnWatch)