We are working with a client which has PEM.  We have everything working fine. We have the dual source working for CICSPEM and BATCHPEM. We are having an issue when a single Hogan PEM source file is built, the CICSPEM or BATCHPEM or both, is being added to be relinked.  Also, the dependency logicalFile for any of the Hogan PEM source file including CICSPEM and BATCHPEM show any dependencies except for Macros.

We have done several --fullBuild, with scanLoadModule on all the Hogan source files and the full build works and tests fine.  It is just the single source file is changed, CICSPEM and BATCHPEM don't get relinked.  

I am looking for a way to either force all the Hogan PEM source files to added to the buildList or force CICSPEM or BATCHPEM to be relinked when a single file is built.

Any advice or suggestions are welcome.

Hi Jerry,

(I recommend to move this discussion to the dbb-zappbuild repository.)

I need to make a few assumptions based on your query, I assume,

• the Hogan sources are just compiled, not not finally linked in the same step.
• link cards are managed in your repository that contain information to the binder/linker, that are processed separately.

To allow DBB to locate the corresponding link card for a source member, it queries both collections that are maintained by zAppBuild (<application>-<branch> + <application>-<branch>-outputs) to find impacted files.

For a Hogan source entry you will likely only find source-level dependencies in the first collection (catgegy MACRO/COPY). Since there are no outputs produces for this source file, you need to check the collection for the link cards. The link cards should have a list of dependencies (stored in the output collection) that are of category type LINK, if your metadatastore is intializied correctly. The dependency set of type LINK contains the references to the hogan modules (CSECTs that got included during the link process).