CA PMO issues a message "PMO163I PMO/MOPS Stopped". What does this mean and what do I do in response? We have CA OPS/MVS on this system.

Document ID:  TEC569212
Last Modified Date:  06/29/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA PMO Runtime Performance Optimizer

Releases

  • CA PMO Runtime Performance Optimizer:Release:4.4

Components

  • CA-PMO for OS/390:PMO
Question:

CA PMO issues a message "PMO163I PMO/MOPS Stopped". What does this mean and what do I do in response? We have CA OPS/MVS on this system.

Answer:

PMO/MOPS was stopped. The CA PMO subtask MOPS, which interfaces to the CA OPS/MVS system, has terminated. This is a normal event when the CA PMO system ends. When CA PMO starts, it starts the MOPS subtask to attempt communication with the CA OPS/MVS system.

If CA OPS/MVS is not active, MOPS will retry the connection periodically.

Eventually if CA OPS/MVS (for 8 hours) is still not active, MOPS will terminate and this message is issued.

Action:
No action is required; this is an informational message.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >