21-Oct-2009

Missing metadata in OpenVMS patches

Recently, I've been having to do a lot of edits to the text files that describe OpenVMS patch releases. I download all of these files for all versions and platforms OpenVMS runs on so I can generate the Patch Syndication feeds.

Noteably, the "Release date" field, which always was a part of the file, has been missing. In every single patch. I have no choice but to use the date that the file shows up on HP's FTP server as the release date of the patch.

Over two years ago, I put together a proposal urging OpenVMS Engineering to consider using XML to deploy patch information. I thought this might actually happen at the time, as I'd been encouraged by Hoff (then working in Engineering) to put this to HP's management. Hoff also wrote an article on the same subject.

What's happened since these articles where written? Nothing, as far as I can see. The metadata in the files seems to be getting worse, not better.

With standardized format, we can write automated tools to notify systems managers of patches that they should apply, automatically download them, generate installation scripts that the system manager can run once satisfied with the patch list, and do all types of other timesaving things.

What do people think about this? Would you use automated patch staging and notification?

Let me know what you think in the comments.

Posted at October 21, 2009 11:33 AM
Tag Set:
Comments

I agree. Although there are fewer patches on OpenVMS than on other platforms there are enough that automation of patch tracking would be of value.

Posted by: Ian Miller at October 21, 2009 10:30 PM

Wouldn't it a good idea if HP would offer webservices to
- get information on request about patches
- download the file

and create programs - openVMS native, of course, no JAVA please - to obtain the information and download if required ?

No auto-update, that is, but such a facility could easily be added.

Posted by: SYSMGR at October 22, 2009 10:05 PM

Comments are closed