VMS73_UPDATE-V0200 X-Files

[PatchAdmin]

Hi there

I dont know if any of you guys did notice this.

In the recent release of VMS73_UPDATE-V0200 it states that the patch kit supersedes VMS73_RMS-V0300 [Please refer to the KITS SUPERSEDED BY THIS KIT part] but in the earlier release of VMS73_UPDATE-V0200 it states that VMS73_RMS-V0400 [Please refer to the KITS SUPERSEDED BY THIS KIT part] is superceded by VMS73_UPDATE-V0200.

Q; Which VMS73_RMS_XXX patch kit is superceded by VMS73_UPDATE-V0200.

Also in the readme file of the recent release of VMS73_UPDATE-V0200 they do mention only the problems address in VMS73_RMS-V0300 and in the earlier release of VMS73_UPDATE-V0200 they mention both the address in VMS73_RMS-V0300 & VMS73_RMS-V0400.

Q: Which VMS73_UPDATE-V0200 patch kit contains the correct information?

Below is an extraction of the special installation instructions of both VMS73_UPDATE-V0200.The extraction from current the VMS73_UPDATE-V0200 and the previously released VMS73_UPDATE-V0200.

Newly release of VMS73_UPDATE-V0200

69.1 Special Installation Instructions:

69.1.1 SYSGEN Parameter Changes

As part of the post installation processing for the VMS73_RMS-V0200 kit,two SYSGEN parameters (PIOPAGES and IMGIOCNT)will be modified in order to accommodate changes being made within the RMS image.

Previous release of VMS73_UPDATE-V0200.

70.1 Special Installation Instructions:

70.1.1 SYSGEN Parameter Changes

As part of the post installation processing for the VMS73_RMS-V0400 kit, two SYSGEN parameters (PIOPAGES and IMGIOCNT) will be modified in order to accommodate changes being made within the RMS image.

Q: For which VMS73_RMS patch kit does this post installation processing apply for.

P.S.I we should start a forum just for patches.

Cheers
Patchadmin

[Martin P.J. Zinser]

Checking the RMS V400 Kit it lists UPD1 as a
requirement. That kind of hints in the direction that the kit was released before UPD2 came out. To be sure you could extract the relevant images from both patches and compare the build dates.

[John Gillings]

Unfortunately errors creep into patch descriptions from time to time. This is inevitable when the "words" involved differ by only one character! Very easy to mistype and very difficult to proof read. So, if you find an inconsistency there probably *is* something wrong! (and in this case there is).

Checking the actual images in VMS73_UPDATE-V0200, I see checksums and link dates that match the images in VMS73_RMS-V0300.

Use PRODUCT LIST to see the file names and PRODUCT EXTRACT FILE/SELECT=(name,...)/DEST= to pull out individual files.

If you don't want to go to the trouble of extracting and examining files, another option would be to go ahead and install any kits you're not sure about. PCSI won't allow regressions, so you can't damage anything by installing a redundant kit.

A request has been lodged that the ITRC patch listings include the image information. Compiling image information can be automated, so it's far less likely to pick up typos. No promises, but hopefully it will be implemented soon.

[George_171]

Errors creep in for other reasons also.
When the UPDATE-V0200 kit started production it did include the RMS-V0400 kit. Subsequently, due to field reports, it looked like there was a problem with the RMS kit so it was pulled from the UPDATE kit and replaced with the RMS-V0300 kit. Eventually the RMS-V0400 kit was cleared but it was too late to get it back in the UPDATE kit.

The problem is that all references to the RMS-V0400 kit were not removed from the UPDATE kit. Normally, benign, except for some customer confusion, but in this case one of the changes that got missed was that, although the RMS-V0300 CONVERT.EXE image was put in the kit, the generation number was not reverted back to the RMS-V0300 level. Consequently, if a user installed the RMS-V0400 kit and then the UPDATE kit it was possible to regress on a fix.

A new VMS73_UPDATE-V0300 kit will be released in the next week or two, depending on test results next week.