Re: PTF Cross Reference

On 06-Oct-2016 12:08 -0500, Rob Berendt wrote:

Change/Usage information:
Change date/time . . . . . . . . . . : 10/06/16 07:24:32
Save/Restore information:
Save date/time . . . . . . . . . . . : 09/13/16 11:03:26
Restore date/time . . . . . . . . . : 06/20/16 14:18:53

Display Program Information

Program . . . . . . . : QTMSADDUSR Library . . . : QTCP
Module attributes:
Module . . . . . . . . . . . . . . . . . . . . : QTMSADDUSR
Library . . . . . . . . . . . . . . . . . . : QBUILDTC1
Module creation date/time . . . . . . . . . . : 12/27/15 23:31:37
Source file change date/time . . . . . . . . . :
User modified . . . . . . . . . . . . . . . . : *NO
Licensed program . . . . . . . . . . . . . . . : 5770TC1V7R3M0
PTF number . . . . . . . . . . . . . . . . . . :

That appears to be the build-date from either the first GA PTF SI58545, or for a pre-GA PTF, for which that PTF chain [with the same group of PTFed objects] remained intact. That object was *clearly not* included in the latest PTF, if the PTF processing on the applied-to system functioned properly.

Note: if not perm applied, the current PTF could be perm removed, and then the request to `MOVOBJ QTCP/QTMSADDUSR *PGM Your_Lib` could be issued, after which a new LODPTF [¿and APYPTF?] would have that object restored from the save file; that would confirm if the object was the same in the save file as was on the system, and if the same, then that shows that indeed the object was not properly included in the Create PTF processing -- be that a developer or a process error, who knows.