Message-Related Parameters

Contents
coema123
Contents
The parameters described in the following sections affect the
CA OPS/MVS® Event Management and Automation
 (
CA OPS/MVS
) message processing.
MESSAGEHIGH Parameter
Displays the high watermark that the message rate control mechanism has reached during the current life of the product or since this parameter value was last reset. This is the highest value that the MESSAGECURRENT parameter has ever reached since that time. Compare the MESSAGEHIGH value to the value specified on the MESSAGEMAX parameter to determine how close
CA OPS/MVS
has come to the point at which it would shut itself down due to exceeding the MESSAGEMAX limit.
 Resetting this parameter affects the data recorded in the product SMF records and the reports produced by the AME.
  • Default value
    No default value
  • Other possible values
    The only possible value you can set this parameter to is zero.
  • Set or modify this parameter…
    Anytime
Example: MESSAGEHIGH
This function resets the MESSAGEHIGH value to zero.
OPSPRM('SET','MESSAGEHIGH',0)
MESSAGEMAX Parameter
This parameter limits the number of write-to-operator messages that
CA OPS/MVS
can generate in a given second.
 By default, TRACE statements from rules or from REXX programs running in a server are written to OPSLOG only; they are not WTOed.
The MESSAGEMAX parameter dictates the maximum value of the message counter kept by the MESSAGECURRENT parameter. When the value of MESSAGECURRENT reaches the value of MESSAGEMAX,
CA OPS/MVS
terminates and issues message OPS3146S. Setting the MESSAGEMAX parameter to its maximum possible value prevents
CA OPS/MVS
from ever shutting down due to an excessive message rate.
  • Default value
    3000
  • Other possible values
    Any number of messages between 100 and 100000
  • Set or modify this parameter…
    Anytime
Example: MESSAGEMAX
This function limits
CA OPS/MVS
to generating 250 WTO messages.
OPSPRM('SET','MESSAGEMAX','250')
MESSAGERATE Parameter
This parameter sets the rate by which
CA OPS/MVS
decrements the value of the MESSAGECURRENT counter every second.
  • Default value
    100
  • Other possible values
    Any number between 1 and 1000
  • Set or modify this parameter…
    Anytime
Example: MESSAGERATE
This function decrements the MESSAGECURRENT counter by 5 each second.
OPSPRM('SET','MESSAGERATE','5')
MLWTOMAXLINES Parameter
The MLWTOMAXLINES parameter determines the maximum lines that can be used for input. This parameter can be changed in the OPSSPAxx member.
  • Default value 
    1024
  • Other possible values 
    0-10000
  • Set or modify this parameter... 
    At initialization
Example: MLWTOMAXLINES
This function changes the default to 100 lines.
OPSPRM('SET','MLWTOMAXLINES','100')
MSGCOLOR Parameter
This parameter sets the default display color for messages in OPSLOG browse for which the MSG.COLOR attribute variable was not set.
 You set the MSG.COLOR variable in AOF message rules.
  • Default value
    NONE
    When the MSGCOLOR parameter has a value of NONE, the message descriptor code (if any) determines the message display color. Otherwise, the color specified on MSGCOLOR overrides the color set by the message descriptor code.
  • Other possible values
    BLUE, GREEN, PINK, RED, TURQ (turquoise), WHITE, or YELLOW
  • Set or modify this parameter…
    Anytime
Example: MSGCOLOR
This function sets the default message display color to green.
OPSPRM('SET','MSGCOLOR','GREEN')
MSGDRAINRATE Parameter
This parameter with the MSGTHRESHOLD parameter, detects address spaces that issue excessive numbers of messages. To understand what these parameters do, consider this analogy: each address space is like a bathtub with a depth set by MSGTHRESHOLD. Each time the address space issues a message, it flows into this bathtub, which has a drain through which the MSGDRAINRATE number of messages flows each second. When the message bathtub overflows,
CA OPS/MVS
issues message OPS4402O.
To prevent messages from overflowing an address space and causing system problems due to looping, you can create a message rule. This rule might cancel the looping address space or place it in a penalty performance group.
  • Default value
    10 (messages)
  • Other possible values
    Any number of messages between 1 and 32767
  • Set or modify this parameter…
    Anytime
Example: MSGDRAINRATE
This function sets the message drain rate to 5000.
OPSPRM('SET','MSGDRAINRATE','5000')
MSGTHRESHOLD Parameter
This parameter, with the MSGDRAINRATE parameter, detects address spaces that generate excessive numbers of messages.
  • Default value
    3000
  • Other possible values
    Any number between 10 and 32767
  • Set or modify this parameter…
    Anytime
Example: MSGTHRESHOLD
This function sets the threshold for messages in an address space to 10000.
OPSPRM('SET','MSGTHRESHOLD','10000')
PROPAGATEATTR Parameter
This determines whether
CA OPS/MVS
propagates back to the console display color changes for messages that the z/OS subsystem interface intercepts, when a
CA OPS/MVS
rule modified the color attribute.
  • Default value
    NO
  • Other possible values
    YES
  • Set or modify this parameter…
    Anytime
Example: PROPAGATEATTR
This function tells
CA OPS/MVS
to propagate message color changes.
OPSPRM('SET','PROPAGATEATTR','YES')
SSIMSG Parameter
This parameter determines whether
CA OPS/MVS
processes messages before or after JES2 processes them.
  • Default value
    NO
    This value causes
    CA OPS/MVS
    to process messages after JES2 has seen them. Changes made to the messages are not reflected in the job log messages of an individual, but the changes will appear in the system SYSLOG.
  • Other possible values
    YES
    This value causes
    CA OPS/MVS
    to process messages before JES2 does so, preventing the
    CA OPS/MVS
    MSG.JOBNM environmental variable from being populated.
  • Set or modify this parameter…
    At initialization
Example: SSIMSG
This function tells
CA OPS/MVS
to process messages before JES2 sees them.
OPSPRM('SET','SSIMSG','YES')
SSIWTL Parameter
This parameter determines whether
CA OPS/MVS
processes Write-to-Log (WTL) messages.
  • Default value
    NO
    This value prevents
    CA OPS/MVS
    from processing WTL messages.
  • Other possible values
    YES
    This value causes
    CA OPS/MVS
    to treat WTL messages like other messages, except that it deliberately skips the WTL done by JES2 or CONSOLE to put the message on the SYSLOG.
  • Set or modify this parameter...
    At initialization
Example: SSIWTL
This function prevents
CA OPS/MVS
from processing WTL messages.
OPSPRM('SET','SSIWTL','NO')
WTODEFAULTROUTE Parameter
This parameter specifies the single z/OS route code to add to any WTO issued by OPSWTO or ADDRESS WTO when no route codes are specified, no console is specified, and the MCSFLAG is not set to HRDCPY only. This parameter supersedes any z/OS default route code and reduces the number of undeliverable messages.
  • Default value
    0
    No default route code is defined.
  • Other possible values
    A single integer route code between 0 and 128
  • Set or modify this parameter...
    Anytime
Example: WTODEFAULTROUTE
This function sets the default route code to 24.
OPSPRM('SET','WTODEFAULTROUTE','24')