| Task | Required Privilege Class |
|---|---|
| Display information about client sessions | Any administrator |
| Cancel a client session | System or operator |
| Freeing links for client connections | Administrator with root authority |
| Query client restartable restore sessions | Any administrator |
| Cancel client restartable restore sessions | System or operator |
| Interrupt client restartable restore sessions | System or operator |
A client session can be either an administrative or a client node session.
If you want to prevent clients from accessing the server for an extended period of time, use the LOCK and UNLOCK commands for client node and administrator sessions, or disable the server.
For information on locking or unlocking administrators from the server, see "Locking and Unlocking Administrators from the Server". For information on locking or unlocking client nodes from the server, see "Locking and Unlocking Client Nodes".
When administrators or users access ADSM, an administrative or client node session is established with the server. Each client session is assigned a unique session number.
To request information about client sessions, enter:
query session
Figure 34 shows a sample client session report.
Figure 34. Information about Client Sessions
+--------------------------------------------------------------------------------+ | Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name | |Number Method State Time Sent Recvd Type | |------ ------ ------ ------ ------- ------- ----- -------- -------------------- | | 3 Tcp/Ip IdleW 9 S 7.8 K 706 Admin OS/2 TOMC | | 5 Tcp/Ip IdleW 0 S 1.2 K 222 Admin OS/2 GUEST | | 6 Tcp/Ip Run 0 S 117 130 Admin OS/2 MARIE | | | +--------------------------------------------------------------------------------+
Check the session state and wait time to determine the session state of the server and how long (in seconds, minutes, or hours) the session has been in the current state. The server session state can be one of the following:
Aggregation can cause multiple media waits within a transaction and is indicated by one client message. For more information, see "Reclaiming Space in Sequential Access Storage Pools".
| Note: | If QUERY SESSION FORMAT=DETAILED is specified, the Media Access Status field displays the type of media wait state. |
If a client does not initiate communication within the specified time limit set by the IDLETIMEOUT option in the server options file, then ADSM cancels the client session.
For example, if the IDLETIMEOUT option is set to 30 minutes, and a user does not initiate any operations within those 30 minutes, then ADSM cancels the client session. The client session is automatically reconnected to the server when it starts to send data again.
You may cancel a client session when:
To cancel a client session, you must identify it by session number. You can display a session number by issuing a query for session information. For example, if the session number is 6, you cancel that session by entering:
cancel session 6
If you want to cancel all backup and archive sessions, enter:
cancel session all
If an operation, such as a backup or an archive process, is interrupted when you cancel the session, ADSM rolls back the results of the current transaction. That is, any changes made by the operation that are not yet committed to the database are undone. If necessary, the cancellation process may be delayed.
When user and administrator sessions are canceled, those persons must access the server again. If they were in the process of performing a function when the session was canceled, they must reissue their last command.
If the session you cancel is currently waiting for a media mount, the mount request is automatically canceled. If a volume associated with the client session is currently being mounted by an automated library, the cancel may not take effect until the mount is complete.
If the session is in the Run state when it is canceled, the cancellation process does not take place until the session enters the SendW, RecvW, or IdleW state.
When a client node initially logs on to an ADSM server by using SNA LU6.2, a SNASVCMG session link is established between the client and the server. This link remains in session even after the user logs off from ADSM. If enough sessions are left connected, new clients can be prevented from connecting to the server.
Because only SNA LU6.2 links must be recycled only after the first time a client logs on and off the system, administrators must deactivate the SNASVCMG link once for each new user. Initially, you may want to recycle links daily until most users have registered with ADSM. After most users have been registered with ADSM, you may want to recycle SNA LU6.2 links less frequently; monthly, for example.
To free unused SNA LU6.2 links, an administrator with root authority must recycle the links as described below.
The server cannot stop the SNASVCMG mode sessions because it does not create them. It is the task of the administrator with root authority to manually deactivate SNASVCMG mode sessions between the server and clients. Because only one SNASVCMG mode session is created for each client, you only need to deactivate the client once. You should deactivate the SNASVCMG sessions on a regular basis to reduce the number of active sessions to zero so that link stations can be recycled.
The administrator with root authority can remove the SNASVCMG sessions by doing the following:
Repeat the last 2 steps as necessary to deactivate the SNASVCMG mode sessions with other clients.
Some large restore operations may invoke a special type of restore operation that allows a user to restart the restore session from where it left off if the session was interrupted. Message ANS1247I is displayed on the client node to identify when a client restartable restore session is started. These restore sessions can be restarted as long as the restore interval has not expired. When a restartable restore session is saved in the ADSM database, the session can be restarted from the point of interruption but any files associated with the file space cannot be moved from sequential volumes. The RESTOREINTERVAL server option allows you to specify how long a restartable restore session is saved in the server database. For more information, refer to the RESTOREINTERVAL server option in ADSM Administrator's Reference.
An administrator can display information about restartable restore sessions to determine which client nodes have eligible restartable restore sessions by issuing the following command:
query restore
Restartable restore sessions have a negative session number.
When a client restore session is in a restartable state, the file space is locked and no files can be moved from sequential volumes. This prevents the data from being migrated, moved, reclaimed, or backed up by another operation. These sessions will automatically expire when the specified restore interval has passed.
An administrator can cancel a restartable restore session that is in an active or restartable state. If the restore session is active, any outstanding mount requests related to the active session are automatically canceled. When a restartable restore session is canceled with the CANCEL RESTORE command, it cannot be restarted from the point of interruption. A restartable restore session always has a negative session number. To cancel a restartable restore session, you must specify the session number. For example:
cancel restore -1
An administrator can interrupt an active restartable restore session and have the option to later restart the session from its point of interruption by canceling the session.
cancel session 2