Manage Work Requests in Status 60 or 65

This document explains what to do if work requests are stuck in status 60 or 65-'Release in progress' after release. Some steps are usually done by a system administrator or super user.

The work request status is set to '60' when released. Status '65' is set briefly while the work request is being processed by the system. Sometimes the work request gets stuck in one of these statuses for different reasons.

Outcome

The work request is released, or the status is reset to '20'.

Workflows

Use these workflows to release a work request or to reset the status to '20'.

If the work request is in status 60:

  1. Verify that auto start job MMS940 is running on the auto start job server.

    If it is not running, you must check the dump logs.

  2. Check 'Subsystem Job. Open' (MNS051) to ensure that the status of the auto start job is '20'.
  3. Restart the auto start job.

If the work request is in status '65':

  1. Verify that auto start job MOS005 is running on the auto start job server.

    If it is not running, you must check the dump logs.

  2. Check (MNS051) to ensure that the status of the auto start job is '20'.
  3. Restart the auto start job.

If the auto start job is running but the work request is still stuck in status '65':

Use related option 37='Unlock' in 'Work Request. Open' (MOS170).

If records remain in the work table MMO001 used by the auto start job, a warning message is displayed stating 'WARNING - Release in progress. Verify that MOS005 is running. Select the option again to force reset of status to 20.' Select related option 37 again. The status in (MOS170) is reset to '20' and the records in work table MMO001 are deleted. Now the work request can be deleted or released again.

Related topics