Why is a Job Not Defined in CA Deliver Showing RMOQPR01 Messages in its Output?
Article ID: 43729
Updated On:
Products
Issue/Introduction
Problem:
Client has some jobs, that are not defined in CA Deliver, that show RMOQPR01 messages in the output:
RMOQPR01 NO RESPONSE - VERIFY taskname IS ACTIVE (sid).
Environment: z/OS
Cause:
Some of client's jobs show message "RMOQPR01 NO RESPONSE - VERIFY RMOSTC IS ACTIVE (RMO$)" though those jobs are not defined in Deliver.
The client had last stopped the Deliver RMOSTC task with "/P rmostc", which (though stopping the task) did not remove Deliver's "hooks" from the system.
Resolution:
The RMOQPR01 messages were issued, in the client's application job run, because:
. The job processed in a way that matched Deliver pre-spool criteria (RMOPARMS JOBCLSL and SYSCLSL).
. The RMOSTC task was down during the time the job ran.
. Deliver's "hooks" were still in the system.
When stopping the Deliver RMOSTC task, "/F rmostc,OFF" should always be used, so that the hooks are removed, as well as the RMOSTC task being stopped.
If the task was last brought down with "/P rmostc", then the RMOSTC task should be started with "/S rmostc,PARM=OFF", so that the task can come up, remove the hooks, then shut down.
Environment
Component:
Feedback
