ZMDES Clean Up after zDFDL Schema zOLDR Fallback or zOLDR Delete

1. ZMDES Manage Deployment Descriptors Process requires multi-CPU/LPAR clean up after a zDFDL Schema zOLDR Fallback or Delete. The other LPARS in the z/TPF Loosely Coupled Complex (LCC) generally do not have their tables updated until an IPL. This prohibits the reload of the Descriptor without an IPL of each of the LPARS in the z/TPF LCC.
2. 2019-01-10 After fallback, clear and deletion of zREST and zEV Configuration, DFDL, and Swagger Files within a z/TPF Loosely Coupled Computing Cluster (LCCC), it requires an IPL to reload the updated file copy so that all of the LPARs show the updated status - (VPARS VP Clear clears problem in Lab but everything has to be reloaded) - ETR/PMR
a. Swaggers are deployed on a per LPAR basis
b. The problem occurs during reloads
c. Chet.wares@travelport.com and Billy.carter@travelport.com are recreating the problem to provide additional evidence
3. 2018-09-27 Information from Z/TPF Lab call
a. Last ECB is exited is when the deleted completes and the cleanup the begins
b. Z/TPF Lab has seen it take a several hours
c. Common deployment (PMR) BC & PD
d. File name and zEV Name have a paired set of GUID keys
e. Naming Standard and file
f. IPL after the removal
g. Same file name cannot have the same key
h. Internal name is a key
i. File name is external
j. Several Files cannot have the same key