Defining CONSOLE SETs

Option

Description

CONSOLE

Must be specified as shown.

SET

Begins the definition of a named console message set.

Name

Specifies the name of the console message set. This operand is required. Code a name of from one to sixteen characters. The name of the set must be unique: if you code a name that is the same as a previously-defined message set it is rejected with an error. The name of the first selected set that a console message qualified for is returned in the CONSOLE field CR_SetName.

DESC | MACRO | MCSflag | ROUTcde

Optionally specify required or prohibited characteristics of messages in order to qualify for the message set. The optional operand NOT indicates characteristics, any of which disqualify the message; if NOT is omitted the parameter indicates characteristics at least one of which is required in order to qualify the message for the set. If you specify a given parameter (DESC, MACRO) more than once each with or without the NOT operand then the specifications are cumulative. DESC, MCSflag and ROUTcde refer to operands of the WTO or WTOR macro. Desc desc ... are one or more integers in the range 1 to 13 inclusive. Routcde routcde ... are one or more integers in the range 1 to 128 inclusive. See the WTO description in the IBM documentation.

JOBName('jobname') | USERID('userid')

Optionally specifies a required job name or user ID of one to eight alphanumeric characters, or one to seven alphanumeric characters and an asterisk (*). An asterisk matches zero or more characters. Only one asterisk can be coded, and it must be the last character of the specification. The specification is not case-sensitive; it is converted to upper case. Some issuers of console messages do not have an associated job name or user ID; you might specify console messages with no job name or user ID by coding '-NONE' (not case sensitive, and note the leading hyphen). (The effective user ID of the MSTR address space – ASID 1 – is +MASTER+.) If JOBName or USERID is omitted then the SET matches a console message with any job name or user ID.

The following table shows examples of jobname or userid specifications and matching job names or user IDs.

Specification	Matching job names or user IDs	Notes
'SYS01234'	SYS01234	The only matching job name or user ID.
'sys'	SYS	The only matching job name or user ID.
'Sys*'	SYS SYSA SYS01 SYS01234 etc.
'usrabcd*'	USRABCD USRABCD1 etc.
'-NONE'		Matches console messages issued by address spaces with no associated job name or user ID.
'SYS'	--	Invalid; only one asterisk might be coded.
'USER*A'	--	Invalid; any asterisk must be in the last position.
' '	--	Invalid; specification must be one to eight characters.
'USRABCDE*'	--	Invalid; specification must be one to eight characters.
' * '	All	Valid, but superfluous. Equivalent to omitting JOBName or USERID.

PREFIX('prefix')

Optionally specifies a required message prefix of one to sixteen characters. (The message prefix is the first up to sixteen characters of the message, often used as a message identifier or number.) The specification is case-sensitive: PREFIX(‘ief’) is not the same as PREFIX(‘IEF’). The message as examined by PREFIX does not include the MCS screen status character such as -, *, @ or +. A message displayed on an MCS console or formatted for the SIEM as +ABC1234E might be specified with PREFIX(‘ABC’).

Any specified DESC, JOBName, LINE, MACRO, MCSflag, PREFIX, ROUTcde or USERID characteristics are joined by an implied logical AND: if you specify DESC(2 3) DESC(NOT 5) MCS(NOT BRDCST) PREFIX(‘IEF’) then in order for a message to qualify for the set it must have a WTO descriptor that includes 2 or 3 and does not include 5, must not be a broadcast message, and must begin with IEF. A console message set defined with only a name, and optionally a SEVerity (no DESC, MACRO) matches every console message (that was not matched by a previously-selected message set).

SEVerity(severity)

Specifies the syslog severity for syslog messages derived from this console message set. Specify one of the severity values from syslog facilities and severities. If you omit SEVerity or code SEVerity(DEFault) then the severity assigned to the syslog message is based on the WTO descriptor code as shown in the following table. If the WTO specified more than one descriptor code the greater severity (lower numeric severity) is assigned.

Descriptor code	Descriptor code meaning	Severity assigned if SEVerity is not specified
1	System Failure	0 – Emergency
2	Immediate Action Required	1 – Alert
3	Eventual Action Required	4 – Warning
4	System Status	5 – Notice
11	Critical Eventual Action Required	2 – Critical
12	Important Information	5 – Notice
None, 5 – 10, 13	Other	6 – Informational

If the first message SET for which a message qualifies specifies SEVerity(SUPpress), then the message is not queued for BMC AMI Defender processing; the message is not processed further by BMC AMI Defender.

Modifying the CONSOLE message sets

You can modify the $$$CONSL member in the amihlq.CZAGENT.PARM file.

The following code shows the $$$CONSL member:

;**********************************************************************;
;**********************************************************************;
; $$$CONSL: User agent parameter member for BMC AMI Defender ;
; This is a copy of CZACONSL and made available for ;
; user modification. It will be included in CZAPARMS ;
; SIEMTYPE-independent ;
; Copyright 2014-2018, 2019-2020 BMC Software, Inc. ;
;**********************************************************************;
;**********************************************************************;

SAY "v6.0.02 Updated 21 March 2020"

; ---------------------------------------------------------------------
; Pre-defined CONSOLE message sets
; You may add your own here as you wish
; CONSOLE definitions have no effect until you SELECT them
;
; By default, all CONSOLE messages are defined to LOCAL4 Facility
; You can override this by adding a "FACILITY(xxx)" parameter to
; the CONSOLE SET command. You can also specify SEVERITY:
;
; For example:
;
; CONSOLE SET(RACF_ICH_Msgs PREFIX('ICH') +
; FACILITY(SECURITY4) SEVERITY(ALERT))
;
; Consult the BMC AMI Defender for z/OS Technical Documentation
; manual for the valid SYSLOG facility and severity codes.
; ---------------------------------------------------------------------

; Health Checker messages
CONSOLE SET(Health_Chk_Msgs PREFIX('HZS'))

; Critical and System Failure z/OS messages
CONSOLE SET(Critical_Msgs DESC(1 2) SEV(ALERT))

; RACF messages
CONSOLE SET(RACF_ICH_Msgs PREFIX('ICH'))
CONSOLE SET(RACF_IRR_Msgs PREFIX('IRR'))

; DB2 messages
CONSOLE SET(DB2_Msgs PREFIX('DSN'))

; CICS messages
CONSOLE SET(CICS_Msgs PREFIX('DFH'))

; WTORs
CONSOLE SET(WTOR_Msgs MACRO(WTOR) SEV(NOTICE))

; System Security (ROUTCDE 9) messages
CONSOLE SET(Security_Msgs ROUT(9))

; JES2 messages
CONSOLE SET(JES2_Msgs PREFIX('$HASP'))

; JES3 messages
CONSOLE SET(JES3_Msgs PREFIX('IAT'))

; BMC Defender messages
CONSOLE SET(Defender_Msgs PREFIX('CZA'))

; BMC messages
CONSOLE SET(BMC_Msgs PREFIX('BMC'))

; Test of Suppressed
CONSOLE SET(Suppressed_Msgs PREFIX('I/O RATE IS ') SEV(SUPPRESS))

; All other messages
CONSOLE SET(Default_Msgs)

Defining CONSOLE SETs

Modifying the CONSOLE message sets

On this page