Operator not able to process messages
Article ID: 122760
Updated On:
Products
VM:Operator
Issue/Introduction
We are seeing some issues where CP is sending Messages to Operator, like DASD DETACH messages, and Operator is not able to process them fast enough to prevent OPERATOR from breaking out of its full screen environment.
Currently OPERATOR is defined with CP TERM MORE 00 and HOLD OFF, as well as defined with 128M of virtual storage.
The Process that Caused the issue was Processing Detaches for all DASD in a specific range which could be up to 4096 devices with in a 9 Second window.
This is on an Active Production system so these were not the only messages coming to Operator .
Are there any settings we can modify to allow Operator to be able to process all these?
Currently OPERATOR is defined with CP TERM MORE 00 and HOLD OFF, as well as defined with 128M of virtual storage.
The Process that Caused the issue was Processing Detaches for all DASD in a specific range which could be up to 4096 devices with in a 9 Second window.
This is on an Active Production system so these were not the only messages coming to Operator .
Are there any settings we can modify to allow Operator to be able to process all these?
Environment
Release:
Component: VMY
Component: VMY
Resolution
The IUCV *MSG buffers are likely overflowing.
Increase VM:Operator's MSGLIMIT to 3000 as shown here:
IUCV ANY MSGLIMIT 3000
IUCV *MSG MSGLIMIT 3000 .
Increase VM:Operator's MSGLIMIT to 3000 as shown here:
IUCV ANY MSGLIMIT 3000
IUCV *MSG MSGLIMIT 3000 .
Additional Information
If needed, it can be increased even more to
MSGLIMIT 65000.
MSGLIMIT 65000.
Feedback
Yes
No
Powered by
