MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2014

Re: When was a PTF applied?



fixed

On 04-Apr-2014 06:09 -0700, rob@xxxxxxxxx wrote:
Well, this did help
DSPLOG PERIOD((0000 032714)) OUTPUT(*PRINT) MSGID(CPF3621 CPF3629
CPF3620 CPC1216 CPC1215 CPI3602 CPF35CA CPI35E8 CPI35E9)

GO LICPGM Option-50 "Display Install History" is supposed to perform something similar to the above, to include /install-related/ messages; including PTF activity. The included messages may however, only include overall completion\failure per product versus a record of each PTF processed.

Note: Transitions both to and from status /temporarily applied/ are indicative of a different code-level becoming active. And there are some transitions meeting that criteria which additionally require [de]activation. The noted Message Identifier selection may be too narrow to include the actual changes to the installed\active code [fix] level.

FWiW: including CPF3600, for example, would cause all messages in the _range_ of CPF36## [where # represents a hexadecimal digit 0-F] to be included, without having to name separately, each specific message of the same extended prefix [the three-byte message identifier prefix with the first two hex digits].






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact