Customer has a release defined with 2 areas . Promotion is only defined for the system area. When they submit a promotion from the system area, the job completes, but uses the subsystem area libraries to copy from.
• Create release and attach package to the release • Checkout a SRO(which creates and OBJ) and stage component using the CMNCOB2OB ------------------------- STAGE: GAT1000098 COMPONENTS ------- Row 1 to 2 of 2
Recreation scenario: (1) Create an ERO release with one package attached to it. (2) Recompile from baseline a source module, activate it, check it into the sub-area and into the final/system area (OUTAR013 in the example below). (3) Issue a “PA” promote command and go through the series of panels required to submit the promote function.
============= Recreation scenario: (1) Create an ERO release with one package attached to it. (2) Recompile from baseline a source module, activate it, check it into the sub-area and into the final/system area (OUTAR013 in the example below). (3) Issue a “PA” promote command and go through the series of panels required to submit the promote function.
CMR9500I - SNAA Promotion UNIT/UNIT20 for START is undefined. If the promotion level is also defined to the first area then the request will run copying components from that area to the promotion dataset rather than from the requested area library .
For common components located in different ERO releases / area libraries the “overlaid” flag is only set for the last promo site selected. As the result, overlaid modules are getting deleting in Promotion libraries after installing the original package in ERO.
