About Recompiling Components

Recompile executes an entire stage procedure, but the like-source input is obtained from a promotion or baseline library instead of from your package staging library. You use recompile when you want to include new versions of like-copy components in a build process where the like-source component is not changing.

An important secondary benefit of recompile is that component history and prior baseline versions reflect actual changes, not just multiple copies of the same component. Both component history and prior versions in baseline libraries are limited, and if you checkout, stage, and install the same source with no changes, real changes are eventually lost.

You can initiate recompile from your change package to add like-load components to your package. Recompile can be automatically invoked by the auto resolve feature of package audit to fix SYNCH errors. For example, if audit detects a like-source component in baseline that uses a copybook in your package, auto resolve initiates a recompile for the source to create a new load to add to your package.