On a system with a large number of user IDs it can occur that individual user IDs are no longer used and are forgotten. Access to these user IDs should be locked automatically after a specified time, the “inactivity limit”. The lock takes effect when the number of days following the last access which is defined by the inactivity limit has elapsed.
The user administrator can release a user ID which has been locked on account of inactivity using the /MODIFY-LOGON-PROTECTION command either by disabling the inactivity limit or resetting the expiration date.
For a newly created user ID, the creation date applies in place of the date of the last access.
Until the first logon after the inactivity limit has been agreed on, the date of this agreement applies in place of the date of the last access.
In the event of a version upgrade, the upgrade date applies in place of the date of the last access for all user IDs.
When a backup of the user catalog is restored, the remaining runtime at the time the backup took place is restored for the user IDs whose inactivity limit had not yet been reached when the backup was made.
Inactivity limits can be exceeded on standby pubsets because of the long storage time. It is then not possible to log on when they are imported as a home pubset. The system administrator must therefore maintain the user catalogs of the home and the standby pubset at the same status.