[Info-vax] OpenVMS Patch FTP server URI

[Volker Halle]

On 5 Jul., 16:09, RobertsonEricW <robertsoner... at netzero.net> wrote:
> On Jul 4, 2:35 am, Jan-Erik Soderholm <jan-erik.soderh... at telia.com>
> wrote:
>
>
>
>
>
> > RobertsonEricW wrote 2011-07-04 03:43:
>
> > > On Jul 2, 5:41 am, Matt<scope-nospam.matt... at btinternet.com>  wrote:
> > >> On 30/06/2011 19:36, RobertsonEricW wrote:
>
> > >>> Does anybody know the OpenVMS Patch FTP server URI? Also, has this URI
> > >>> changed with the new web-based HP Support Center Patch Management
> > >>> Service?
>
> > >>> Thanks in advance for any information.
>
> > >>> Eric
>
> > >> I think patches are now only available via the website and only to
> > >> customers who have a current software support contract with HP.
>
> > >> Matt
>
> > > Yes. The Company I work for has a software support contract. The
> > > reason I asked the question was because there is a bug in the online
> > > patch management logic that prevents you from downloading a patch that
> > > depends on another patch that was rescinded and replaced with a newer
> > > updated patch. I thought that only the anonymous FTP download was
> > > removed but, that user based ftp might still be available so that I
> > > could download the "unobtainable" patch directly via FTP. This is
> > > actually frustrating because I had a similar problem a couple of years
> > > ago which I reported to OpenVMS engineering. I was expecting this
> > > would no longer be a problem. Apparently my expectations are too hight.
>
> > > Eric
>
> > An example ? With patch-names.
>
> > I also see that when I select patches (yesterday, actualy) I do get
> > a few extra patches automaticly selected that the system thinks
> > are needed. Such as en old UPDATE or SYS patch already replaced
> > wit a later one. I simply de-select them from the list before
> > going tothe next page. And then I click "Download" on the individual
> > patches anyway.
>
> > Note that I also always select architecture, verision and "browse
> > patch list".
>
> > I do not understand what your problem is.
>
> > Jan-Erik.
>
> The problem I am having is when using the patch management interface
> to download the VMS84I_MUP-V0200 Patch for OpenVMS Integrity V8.4,
> There is a registered dependency on the VMS84I_UPDATE-0400 kit.
> However, since that exact kit is not present it will not permit
> download of the patch even though the VMS84I_UPDATE-V0500 is present
> and selected in the download list. The VMS84I_UPDATE-V0500 should
> serve as an acceptable substitute for the VMS84I_UPDATE-0400. But,
> apparently, the "patch management" is not programmed to "know" this
> and stubbornly refuses to permit the download of the VMS84I_MUP-V0200
> kit.
>
> Eric- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

Eric,

note that the SYSTEM_PRIMITIVES*.* images present in VMS84I_MUP-V0200
are included in VMS84I_UPDATE-V0500, although the text in
VMS84I_UPDATE-V0500 seems to imply, that only VMS84I_MUP-V0100 is
included.

Volker.