AXP_DNVOSIECO02-V732 checksum?

[William J. Clogher, Jr.]

Patch lists:

Checksum of Compressed Kit: 863420154

I've tried two separate downloads and both times the compressed kit checksummed to: 863411962 . Decompression was successful. Is the listed checksum just incorrect?

[Dave Gudewicz]

There was another recent patch with checksum differences; VMS732_F11X_V0400. What was published was not the correct checksum.

Was fixed by: George Pagliarulo who is responsible for the OpenVMS ECO release process.

email: first.last@hp.com

Dave...

[John Gillings]

William,

Unfortunately some methods of calculating checksums include information from the header of the file, which can be changed by the process of transferring the file (for example, losing file attributes). It could also be a stuffup at the HP end.

If the file is supposed to be a PCSI$COMPRESSED kit, make sure it's:

SET FILE/ATTR=(RFM:FIX,MRS:512,LRL:512,RAT:NONE)

This *may* correct the checksum.

There are two purposes for the checksum. First to verify the integrity of the file (did it get corrupted in transit?). The second to protect against malicious modification (has someone planted a trojan in it?).

If you're not concerned with the latter, then the command:

$ PRODUCT LIST prodname /SOURCE=kit-directory

is a quick and simple way to check that the kit is intact, without having to unpack or install it.

If you are concerned about potential security breaches, check with George.

Note that ITRC downloads now include a "patch manifest". This will eventually be used by PCSI to validate the integrity of the patch kit in a future version of OpenVMS.

[William J. Clogher, Jr.]

The set attributes did not fix this particular checksum issue, but thanks for the suggestion. It has has fixed other erroneous checksums I've encountered.

[John F. Muench]

I'm planning OpenVMS Alpha V7.2-1 to V7.3-2 upgrade (for our VMSclusters) and happen to need this patch kit as well as others. I downloaded and expanded [12] kits but get errors (starting with "Error in processing product description file" per attached text file) when trying to extract release notes or list kit contents (via PRODUCT EXTRACT RELEASE_NOTES or PRODUCT LIST commands) so I'm concerned I won't be able to install the kits. The checksum on at least some problem files (shown in attached) matches related kit ECO Summary so I'm perplexed. Any help you or HP can provide will be appreciated.
Thanks, John

[Ian Miller.]

Are you up to date with PCSI patches?

[John F. Muench]

Ian, There's a PCSI kit I plan to install right after VMS V7.2-1 to V7.3-2 upgrade. I started separate forum request on this and got replies indicating that some of these kits likely contain [UNDO] feature that was implemented in VMS V7.3-1 so my hope is that once I do upgrade and install the related DEC-AXPVMS-VMS732_PCSI-V0300--4.PCSI;1 kit, then I'll be abled to install the other kits (we'll see). Thanks for the reply!