We deployed locked snapshot ( configuration and component versions ) to production environment. The component was created with template ( Use Latets template option). We found that even though Snapshot is locked, any changes in the template process were getting reflected in the snapshot deployment. ideally the latest version of the template process should be locked in the snapshot. Did anyone observe this behavior ? Is there a way to specifically lock the process ( template process ) when snapshot is locked ?
This is different behavior when component is self contained and in that case process gets locked. Any response will be appreciated.
I am able to reproduce the behavior which you are experiencing. Let me look more into how to lock the process using snapshot
Answer by ScottNeibarger (95) | May 26, 2016 at 08:54 AM
This is documented in APAR PI47557 and was resolved in 6.2.1.