No Endevor Footprint after apply a PTF

Article Id: 132221
Status: Published
Updated On: 15-05-2019 05:56
Products:
CA Endevor Software Change Manager (SCM) , CA Endevor Software Change Manager - Natural Integration (SCM) , CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) , CA Endevor Software Change Manager - Enterprise Workbench (SCM)
Issue/Introduction:



After applying SO07919, CSIQOPTN member £REQPDS was delivered with no Endevor footprint (it's the same for the other delivered members in this PTF). Is this standard going forward?

Environment:

Release:
Component: ENDBAS

Resolution:

Yes, this is true for all members delivered with a PTF. This has always been true, it's because when we create a PTF everything for it is contained in a sequential file, so their is no directory information in it. When we create a PAX, we are copying everything directly from our Endevor libraries, so the directory information (footprints) are retained and wind up in the installed libraries. Installing a PTF overlays the directory information.