Module Format for Programs and Panels › Module Runtime Considerations › Tailoring the LMT

Tailoring the LMT

The introduction of site-defined AMTs and @ILMLIST let you designate the exact contents of the in-core LMT. This can be useful in a variety of situations:

• Multiple CICS regions sharing a single dictionary and each of those CICS regions run different programs
• Creating separate AMTs for batch only applications
• Simplification of processing

AMT processing removes the PPT and LMT entries for load modules that are not run in a specified CICS region.

AMT processing can also simplify the processing that must otherwise execute at the receiving site of migrated applications. You can do this by simply supplying the load modules and AMTs to the receiving site. In some cases, you can also supply @ILMLIST. In other cases, the receiving site executes the steps necessary to update, reassemble, and link @ILMLIST.

Sites using AMT processing should be aware of the following restrictions. For more information see the “Application Migration Considerations” chapter.

• REFRESH command deletes the LMT entry if no dictionary module entry is present. Execute the CICS NEWCOPY command to refresh an existing program.
• Modifications to @ILMLIST and AMTs require recycling. CICS NEWCOPY commands do not affect the contents of the LMT once CICS is active.
• New subprograms require you add additional entries to the corresponding AMT. You must either recycle CICS or issue the IDENTIFY MODULE command before a REFRESH command so that the LMT can be updated. CICS NEWCOPY commands do not make the module known to the CA Ideal LMT.