[Info-vax] Problem with patch access with support contract.

[Jan-Erik Soderholm]

Rich Jordan wrote 2013-10-09 18:54:
> Our AllianceONE account (paid) is also apparently no longer sufficient
> to access the patches (which is what I was asking about a few weeks ago
> here:  https://groups.google.com/forum/#!topic/comp.os.vms/ujZW4LR9XIw
> ).  So software download is blocked, and now patch access is apparently
> disallowed for 'mere developers', even those who are paid company
> members.
>
> I couldn't get a firm answer on if this was going to happen (and to be
> fair I got so busy I was very slow following up).  But I guess HP really
> doesn't give a crap about further third party development on OpenVMS.
> But I note our useless paid account still provides access to "patches
> for other platforms" like windows and linux.  Gee thanks.
>
> The details page says we have HP-UX 11iV3 HP9000 as the ONLY linked
> products on our AllianceONE SAID.  We have never sold, used, or licensed
> HPUX, and certainly not on the HP9000 platform, and it was never part of
> our developer profile with HP.  It doesn't provide patch access for HPUX
> either.
>
> Interestingly I finally found the SAR that another section of the site
> has been demanding and AllianceONE was unable to provide to us; it was
> at the link to see what patch access was available.  I entered it along
> with the AllianceONE provided SAID and found out we now have access to
> absolutely NOTHING on the software updates and licensing page.
>
> So no software access, no compiler access, no VMS downloads, and now no
> patches, with a PAID company account.  Our cup runneth over.  Our
> account renews in a few weeks, but why should we even bother any more?
> Which of course might be HP's whole point.  Go away, you bother us...
>

Arg... I talked to Ken Surplice (HP Product Manager Business
Critical Systems EMEA) on Monday, he was at the Oracle/VMS
forum in Sweden. I should have known this on Monday so
that I could have mentioned it directly to him...

Anyway, according to Ian MIllers post earlier today, it seems
to be a "known problem", så maybe it will be fixed soon...

Jan-Erik.