Show TOC

Subsequent update requests

Description

Until now it has been difficult to post-update the Update1 part of an update request. The problem was that the update locks were reset when an update was terminated. In some applications, this loss of locks could result in inconsistent data when post-updating. This is hy the update manager always issues a post-update warning and it is always necessary to check with other users of the application.

In Release 3.0 and later, those modules that run in Update1 and which cannot be post-updated are flagged. When one of these function modules is maintained, Immediate start no post-update has to be selected. No update request containing one or more function module that has been maintained in this way can be updated subsequently by the update manager.