Version 7.7.3
 —  Adabas Manager Documentation  —

Working with a Protected Nucleus

The information is organized under the following headings:


Accessing a Protected Nucleus

The user has to supply user ID and password when attempting to access a protected nucleus. The ID and password supplied for System Management Hub (SMH) are not applied here.

If the nucleus is protected by Adabas SAF Security, Adabas Manager will verify the user ID and password defined in the mainframe security system.

You are prompted for login

Note:
Tree items you are not authorized to view for security reasons are not displayed; where menus are available for viewing but may not be modified, the respective buttons are grayed out in the detail-view panels.

Top of page

Terminating a Session with a Protected Nucleus

The session with a protected nucleus is terminated

Top of page

Passwords

Adabas Manager does its own user authentication check independent of the credentials supplied for System Management Hub (SMH) logon. The authentication is specific for each nucleus, but you can simultaneously logon to several with one password.

On expiry of a user password, the databases protected by Adabas SAF Security will request that you set a new password. User IDs and passwords in Adabas Manager are restricted to 8 characters. Other than that, Adabas Manager will check that a new password is being entered and that it is not the same as the previous one.

Top of page

Non-activity Timeout

The duration of an Adabas Manager session with a protected nucleus can be determined by setting the non_activity_time value in the registry; this will be the priority timeout value and apply to all databases.

If non_activity_time has not been set in the registry, the ADARUN parameter TNAE will set the timeout for the session with a database.

Top of page