| Task | Required Privilege Class |
|---|---|
| Display information about a server background process | Any administrator |
| Cancel a server process | System |
When a user or administrator issues an ADSM command or uses a graphical user interface to perform an operation, the server starts a process. Some examples of an operation are registering a client node, deleting a management class, or canceling a client session.
Many processes occur quickly and are run in the foreground, while others take longer to complete. To allow you to perform other tasks during long-running operations, ADSM runs the following operations as background processes:
The server assigns each background process an ID number and displays the process ID when the operation starts. For example, if you issue an EXPORT NODE command, ADSM displays a message similar to the following:
+--------------------------------------------------------------------------------+ |EXPORT NODE started as Process 10 | +--------------------------------------------------------------------------------+
Some of these processes can also be run in the foreground by using the WAIT=YES parameter when you issue the command from an administrative client. See ADSM Administrator's Reference for details.
You can request information about server background processes. If you know the process ID number, you can use the number to limit the search. However, if you do not know the process ID, you can display information about all background processes by entering:
query process
The following figure shows a server background process report after a DELETE FILESPACE command was issued. The report displays a process ID number, a description and a completion status for each background process.
Figure 43. Information about Background Processes
+--------------------------------------------------------------------------------+ | Process Process Description Status | | Number | |-------- ------------------------ --------------------------------------------- | | 2 DELETE FILESPACE Deleting filespace DRIVE_D for node CLIENT1: | | 172 files deleted. | | | +--------------------------------------------------------------------------------+
You can cancel a server background process by specifying its ID number in the following command:
cancel process 2
You can issue the QUERY PROCESS command to find the process number. See "Requesting Information about Server Processes" for details.
If the process you want to cancel is currently waiting for a tape volume to be mounted (for example, a process initiated by EXPORT, IMPORT, or MOVE DATA commands), the mount request is automatically canceled. If a volume associated with the process is currently being mounted by an automated library, the cancel may not take effect until the mount is complete.
ADSM can preempt server or client operations for a higher priority operation when a mount point is in use and no others are available, or access to a specific volume is required.
The following are high priority operations that can preempt operations for a mount point:
The following lists operations that can be preempted and are listed in order of priority. ADSM selects the lowest priority operation to preempt, for example reclamation.
You can disable preemption by specifying NOPREEMPT in the server options file. When this option is specified, the BACKUP DB command is the only operation that can preempt other operations.
A high priority operation that requires access to a specific volume currently in use by a low priority operation can automatically preempt the operation. For example, if a restore request requires access to a volume in use by a reclamation process and a drive is available, the reclamation process is canceled and message ANR0494I or ANR1441I is issued.
The following are high priority operations that can preempt operations for access to a specific volume:
The following lists operations that can be preempted, and are listed in order of priority. ADSM preempts the lowest priority operation, for example reclamation.
You can disable preemption by specifying NOPREEMPT in the server options file. When this option is specified, no operation can preempt another operation for access to a volume.