Problem installing OVMS 8.3A Update 11

[Hoff]

Steve, that same-but-different V11 confusion was what I was referring to back with that Dec 8, 2009 16:18:58 reply.

And yes, VMS83A_UPDATE V11 has been pulled down (again), based on a check made at 17-Dec-2009 16:30 UTC. Here's what's currently posted:

[Hoff]

$ @tt:/out=x.x
direct/ftp/anon ftp.itrc.hp.com::"/openvms_patches/alpha/V8.3"
^Z
$ search x.x update /out=y.y
$ sort y.y tt:
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0500.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0500.txt
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0600.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0600.txt
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0700.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0700.txt
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0800.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0800.txt
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0900.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V0900.txt
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V1000.ZIPEXE
/openvms_patches/alpha/V8.3/VMS83A_UPDATE-V1000.txt
$

[Volker Halle]

Edgar,

VMS83A_UPDATE-V1200 has now been released. It contains a warning regarding the PTHREAD$RTL SYMVECMIS problem and suggests to continue the installation despite this error.

Volker.

[Neil Rieck]

I had a similar problem in not being able to go from VMS-8.3 (Alpha) update-9 to update-13. As others had already suggested, I first needed to install DEC-AXPVMS-VMS83A_SYS-V1300 but update-9 wouldn't allow it (not visible from the PROD INSTAL command). So I installed update-10 then was allowed to install DEC-AXPVMS-VMS83A_SYS-V1300 which then enabled an error-free install of update-13. Yippee!

[Shriniketan Bhagwat]

Hi,

This is because; VMS83A_SYS-V1300 kit is dependent on VMS83A_UPDATE-V1000 kit. Please refer the section 4.1 from ECO Cover Letter for SYS-V1300 kit.

http://www13.itrc.hp.com/service/patch/patchDetail.do?patchid=VMS83A_SYS-V1300&sel={openvms:alpha:8.3,}&BC=main|search|

Regards,
Ketan

[Volker Halle]

Niel,

here you've seen the consequences of HP OpenVMS Engineering breaking the rule: all OpenVMS updates are ALWAYS CUMULATIVE !

Volker.

[Bhadresh]

Hi,

Before installing any kit always look at the dependencies list first. VMS83A_PCSI-V0200 and MS83A_UPDATE-V1000 needs to be installed before VMS83A_SYS-V1300 kit.

Have a look at the dependencies section:

http://www11.itrc.hp.com/service/patch/patchDetail.do?&patchid=VMS83A_SYS-V1300&sel={openvms%3Aalpha%3A8.3%2C}&BC=main|search|#KIT%20DEPENDENCIES

Regards,
Bhadresh

[Sandeep Ramavana]

Hi Neil,

You should be able to install UPDATE 13 over UPDATE 9. Did you face any specific issues? If you get a prompt asking "Do you want to terminate?" you should answer NO to the question. This ensures that the installation is successful. More details are in the release notes of the UPDATE kit.

>> here you've seen the consequences of HP OpenVMS Engineering breaking
>> the rule: all OpenVMS updates are ALWAYS CUMULATIVE !
Hi Volker, updates are still cumulative.

Best Regards,
Sandeep

[H.Becker]

I'm sure, it was already said: there was a change in the base image. I don't remember all the details but - as we all know by now - it was for pthreads. So, at least the new PTHREAD$RTL depends on SYS$BASE_IMAGE. A cumulative update now happens to have both the changed base image and the changed PTHREAD$RTL. Obviously the base image is only in effect after a reboot. But as shown, the new pthread rtl is used in a subsequent image activation: %IMGACT-F-SYMVECMIS. This is very likely a check whether the required base image is present or there was an $install/replace. Either one breaks the cumulative update. In a situation like this, the check for the correct base image needs to be done with something else and the new rtl should not replace the installed one in memory.