Tuning Performance › Control Message Flow in OCS

Control Message Flow in OCS

To ensure that OCS activity impedes the performance of your systems as little as possible, the following points should be considered:

• Restrict the types of messages that an operator receives using UAMS or an external security definition.
• Do not allow all operators to receive unsolicited messages by default.
• Use MSGPROCs. Held message limits can be reached while the panels are being displayed. If messages are not going to be examined, they should not be sent. These messages waste storage space and CPU time.
• Restrict the use of non-roll delete (NRD) messages. Extra system resources are needed to retain NRD messages.
• Encourage the use of selective commands. Monitor the use of $CMDENT. If excessive, perhaps the default wrap count should be lowered.
• Use the SYSPARMS HELDMSG=xxx,yyy command to limit the hold message queue. The queuing of messages causes excessive storage usage and fragmentation.