Changes to MODULE entity occurrences in the dictionary after the in-core LMT is built do not affect the in-core LMT. CREATE MODULE, DELETE MODULE, and IDENTIFY MODULE commands consequently do NOT modify the in-core LMT.
The REFRESH command updates the in-core LMT and synchronizes it with the dictionary entity occurrence as follows:
If an in-core LMT entry exists, it is updated; otherwise, an entry is added. In a CICS environment, if PPT entries do not exist, they are added and a CICS DISABLE, NEWCOPY, and ENABLE for each module associated with the program or panel, is performed.
If an in-core LMT entry exists, it is deleted; otherwise, an error message is issued.
A SELECT SYSTEM command executed before the REFRESH command identifies the CA Ideal system that contains the program or panel. The syntax of the REFRESH command is described in the Command Reference Guide.
Execute the REFRESH command for each program or panel that was replaced. You should also execute it in each environment using the replaced program or panel.
Carry out this process with standard CICS commands. However, using the CA Ideal REFRESH command with the program name means that all three modules are refreshed for application programs; you do not need to remember the proper module suffixes, and you do not need to remember the seven‑character module name.
If a CICS NEWCOPY service fails because the module is still in use, CA Ideal waits five seconds and tries again. If it still fails, CA Ideal continues waiting and tries again in one minute. If, after a minute, the NEWCOPY still fails, the load modules are left disabled and a message indicating the problem is sent to the user. This usually implies that the CA Ideal DISABLE or ENABLE command was not correctly issued or that the ENABLE command was issued before the REFRESH command. For more information about the REFRESH command, see the "Application Migration Considerations" chapter.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|