The handling of concurrent user access is described here.
Another major feature of the management functions API is the handling of concurrent accesses of multiple users to the same management objects. For this purpose there is another database table as shown in the example in the table below.
Table 1. RTP_ADM_SESSIONS
|User||Hostname||Login Time||Server Address||Active Objects|
The table above shows an example with a snapshot of all currently existing user sessions. The above-mentioned MgmtSession class controls its contents. The user management function can be used to retrieve the table's contents for information purposes.
The listed ActiveObjects correspond to instances of the management classes in the management function API. If one user updates data belonging to a particular management object (an EventMgmt object), any other user sessions currently using an object of the same class are informed about the update.
Using the above example: If sysop2 updates event parameters (being handled by his instance of the EventMgmt class), sysad receives a note about this update as he also has an instance of the EventMgmt class. It is up to the respective user interface how this information is handled; it might request the modified data or instead provide a pop-up dialog window informing the user that the data being displayed probably is out of date.
Among others, the update information mechanism is part of the BaseMgmt class in the management function API (InformUpdate member function). Any other management classes (classes being part of the RTP as well as application-level management classes provided by Fujitsu Computers) inherit their basic functionality from the BaseMgmt class.
Parent topic: CLI User Management