Shared objects generated with LOAD-MODE=ONCALL can only be exchanged if they were generated with versions.
If you exchange this type of shared object, only the version identifier to be loaded dynamically for the respective shared object is entered in the openUTM tables when the KDCPROG administration command is processed.
The new version is not loaded by each work process of the application until the next time this work process calls a program unit contained in this shared object. The program exchange can be implemented simultaneously by several work processes of an application. Until the requested program exchange has been implemented by all work processes of the openUTM application, different states of the application program are loaded in the individual work processes. However, it is ensured that each work process implements the requested exchange before another program unit is activated which is contained in the shared object to be exchanged.
The exchange of a shared object generated with ONCALL does not have a blocking effect on subsequent commands for program exchange. Immediately after processing the KDCPROG command, the administrator can therefore initiate another program exchange with another KDCPROG command.
If the version identifiers of the new and old shared object are the same, no program exchange is implemented.