Introduction › Starting and Stopping CA VM:Secure and CA VM:Director › Stopping CA VM:Secure and CA VM:Director › Checking CA VM:Secure and CA VM:Director Activity Before Stopping

Checking CA VM:Secure and CA VM:Director Activity Before Stopping

Before you stop CA VM:Secure or CA VM:Director, check who is using the system by entering the QPCB command. For example, for CA VM:Secure enter the following:

vmsecure qpcb

This command lists the currently active processes and the commands they are executing.

Occasionally a user ID has an active process that prevents either a graceful shutdown of CA VM:Secure or CA VM:Director, or a shutdown within a reasonable amount of time. When CA VM:Secure or CA VM:Director takes longer to stop than you think is reasonable after you enter the END command, check which user ID has a lock on an object. Object locks indicate that something is still processing.

You can check for activity by entering the QLOCK command. For example, for CA VM:Secure, enter the following:

vmsecure qlock

This command lists all commands that are holding locks, the kinds of locks they are holding, and the objects on which they are holding locks. To correlate these commands with the user IDs that are running them, enter the QPCB command (see above) and match the commands with the currently active processes they are executing.