Determining the Number of Affected Jobs

Use the DCL command

        SHOW SYSTEM
        

to observe whether most processes are getting work done.

If one process is [almost] constantly in the COM state, reduce its priority with the following DCL command.

        SET PROC/PRIO=0/ID=pid
        

If only one user is identified as having a problem, and a second process doing a similar function would not cause damage to the data of the application, check to see if another user doing a similar task also hangs.

If there is only one process affected, issue the following DCL command to prevent that process from consuming CPU cycles, and indirectly interfering with other processes:

        SET PROC/PRIO=0/ID=pid
        

If only one process is affected, and other important work is at hand, you may defer the rest of the steps until an appropriate time.

If more than one application is affected, the problem is unlikely to be directly caused by GT.M. Test to ensure that the disk drives are not full, and that they are both read and write accessible. Perform steps recommended by HP for determining the state of OpenVMS.