How can I learn patch details

[mustafa_12]

When examining the individual patch enhancments, some have a ptr, cfs, req id or bug node id as you can see below link. Is it possible to find the related complete problem for which the patch is required by using these information. What are ptr, cfs, req id, bud no?

http://www4.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=DEC-AXPVMS-TCPIP_ECO-V0504-155-4&context=openvms:alpha:7.3-2

....
....
ECO A Alpha and VAX

Problem:

TCPIP$INTERNET_SERVICES INVEXCEPTN crash during shutdown caused
by $ TCPIP DISCONNECT DEVICE command.

Deliverables:

TCPIP$INTERNET_SERVICES.EXE V5.4-15A

Reference:

PTR 70-5-2380 / CFS.102586 / Req Id: GB_G08063
TCPIP_BUGS Note 2986
....
....

[Volker Halle]

Mustafa,

the additional reference information numbers in patch descriptions are pointers to HP (previously Digital) internal problem escalation and management tools. TCPIP_BUGS is a notes conference internal to TCPIP engineering.

This additional information from those systems is only available inside HP.

Volker.

[comarow]

In the patch tree, read the .txt file.

For example.

At
ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/

You'll see a both the patch and a txt file.
The .txt file has the description of the ECO

VMS732_FIBRE_SCSI-V0700.PCSI-DCX_AXPEXE
is the patch, while
VMS732_FIBRE_SCSI-V0700.txt

is a description of the ECO.

Good luck.

[George_145]

The problem descriptions and problem analysys sections in the patch documents take the contents of the case reports (PTR, CFS, etc) and syntehsize them down to what the customers need to know about the problems fixed. Because these case reports are customer specific, there is often a good deal of proprietary or customer specific information that we need to remove.
If you need more information you can try asking your field representative if there is more information available. They have access to the case reports.

George Pagliarulo
OpenVMS ECO Release Process