SUPPRESS

The following solutions suppress system console messages that are not required by system operators. Suppressing such messages enables operators to receive only relevant messages that can then be investigated and handled.

The Control-O Message Statistics screen provides message statistics that are useful in determining which messages to suppress. Before deciding to suppress a message, read the detailed message description in the message guide of the relevant system component.

Individual messages are suppressed by individual rules. This means that each message is suppressed by the rule that contains its message ID.

The suppression rules for all messages in any of the following solutions are identical except for the message ID. Therefore, only the rule for the first listed message in each solution is detailed as a sample.

Solutions Provided

SolveWare subject SUPPRESS contains the following solutions:

MVS Message Suppression – Suppresses certain MVS messages that are not required by operators.
JES2 Message Suppression – Suppresses certain JES2 messages that are not required by operators.
JES3 Message Suppression – Suppresses certain JES3 messages that are not required by operators.
System Component Message Suppression – Suppresses various system component messages that are not required by operators.

MVS Message Suppression

This solution contains rules to suppress certain MVS messages from the system console. These messages are not suppressed from the system log.

Each message is suppressed by the rule that contains its message ID.

Rules

Table 33 lists the rules and the MVS messages that they suppress.

Table 33 MVS Message Suppression Rules

Rule	Message
IEA848I	IEA848I NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION REQUEST
IEA989I	IEA989I SLIP TRAP ID = xxxx MATCHED
IEA995I	IEA995I SYMPTOM DUMP OUTPUT ABEND CODE {SYSTEM \| USER} = code TIME=hh.mm.ss SEQ=number CPU=n ASID=asn PSW AT TIME OF ERROR pppppppp pppppppp ILC x INTC y ACTIVE LOAD MODULE = modname ADDRESS = aaaaaaaa OFFSET = ddddDATA AT PSW -xxxxxxxx - xxxxxxxx xxxxxxxx xxxxxxxx GPR 0-3 R00 R01 R02 R03 GPR 4-6 R04 R05 R06 R07 GPR 8-11 R08 R09 R10 R11 GPR 12-15 R12 R13 R14 R15 END OF SYMPTOM DUMP
IEC070I	IEC070I rc{(sfi)}-ccc,jjj,sss,ddn,ddd,ser,xxx,dsn,cat
IEC130I	IEC130I ddn - DD STATEMENT MISSING
IEC141I	IEC141I 013-rc,mod,jjj,sss,ddn{-#},ddd,ser,DSN
IEC161I	IEC161I rc{(sfi)}-ccc,jjj,sss,ddn,ddd,ser,xxx,dsn,cat
IEC331I	IEC331I rc-crs,jjj,sss,proc,mmm
IEC705I	IEC705I TAPE ON ddd,ser {IS}{,labtyp}{trtch},denBPI{,jjj,sss}{,dsn}
IEC999I	IEC999I mod,sub,debaddr = xxxxxx or IEC999I mod,sub,workarea = xxxxxx or IEC999I mod,jjj,sss{,ddd,ser,dsn}
IEE043I
IEE043I	IEE043I A SYSTEM LOG DATASET HAS BEEN QUEUED TO SYSOUT CLASS x
IEE400I	IEE400I THESE MESSAGES CANCELED - nn,nn,nn,...
IEF097I	IEF097I USER userid AND GROUP groupid ASSIGNED
IEF097I	IEF097I jobname USER userid ASSIGNED
IEF125I	IEF125I jjj- LOGGED ON {- TIME hh:mm:ss}
IEF126I	IEF126I jjj- LOGGED OFF {- TIME hh:mm:ss}
IEF170I	IEF170I n jjj (msg)
IEF188I	IEF188I PROBLEM PROGRAM ATTRIBUTES ASSIGNED
IEF196I	IEF196I jcl-text
IEF202I	IEF202I STEP sss WAS NOT RUN BECAUSE OF cde
IEF236I	IEF236I ALLOC. FOR jjj {ppp} sss
IEF237I	IEF237I ddd ALLOCATED TO ddn
IEF287I	IEF287I dsn dsp w VOL SER NOS = ser, ser, ser, ser, ser, ser
IEF288I	IEF288I dsn SYSOUT
IEF403I	IEF403I jjj STARTED{ - TIME=hh.mm.ss}
IEF404I	IEF404I jjj ENDED{ - TIME=hh.mm.ss}
IEF452I	IEF452I jjj - JOB NOT RUN - JCL ERROR
IEF452I	IEF452I ppp - JOB NOT RUN - JCL ERROR
IEF452I	IEF452I JOBFAIL - JOB NOT RUN - JCL ERROR
IEF453I	IEF453I jjj - JOB NOT RUN - JCL ERROR
IEF677I	IEF677I WARNING MESSAGES FOR JOB jjj ISSUED
IEF722I	IEF722I jjj - FAILED txt

Rules Structure

The following table details the structure of the MVS message suppression rules. All MVS messages included in this solution are identical, except for their message IDs.

Table 34 MVS Message Suppression Rule Structure

Item	Description
Title	MVS Message Suppression
Name	message-Id message-id can be any name (message ID), as listed in Table 33.
Table	SUPMVS
Message	message-id NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION REQUEST
Message Description	No dump was produced for a certain abend situation.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule suppresses the message from the operator console. The message still appears in the system log.
Rule Actions	Suppresses the message from the system console.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in PROD mode. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	If suppression of the particular message is not required, delete the rule from the table.

JES2 Message Suppression

This solution contains rules to suppress certain JES2 messages from the system console. These messages are not suppressed from the system log.

Each message is suppressed by the rule that contains its message ID.

Rules

Table 35 lists the rules and the JES2 messages that they suppress.

Table 35 JES2 Message Suppression Rules

Rule	Message
$HASP100	$HASP100 jobname ON device {progname} {FROM ijobid ijobname}
$HASP101	$HASP101 jobname HELD
$HASP110	$HASP110 jobname {ILLEGAL JOB CARD \| MULTIPLE JOB CARDS}
$HASP111	$HASP111 jobname – INVALID /*ROUTE CARD
$HASP112	$HASP112 jobname – INVALID /*JOBPARM CARD
$HASP113	$HASP113 jobname – INVALID /*OUTPUT CARD
$HASP114	$HASP114 jobname – INVALID EXECUTION NODE
$HASP115	$HASP115 jobname – INVALID /*NETACCT CARD
$HASP116	$HASP116 jobname – INVALID /*NOTIFY CARD
$HASP117	$HASP117 jobname – INVALID /*XMIT CARD
$HASP118	$HASP118 jobname – INVALID /* CONTROL STATEMENT
$HASP125	$HASP125 jobname SKIPPING FOR JOB CARD
$HASP150	$HASP150 jobname OUTGRP=groupid.jobid1.jobid2 ON device {nnnnnnnn (mmmmmmmm) LINES \| nnnnnnnn (mmmmmmmm) RECORDS \| nnnnnnnn (mmmmmmmm) PAGES}
$HASP160	$HASP160 device INACTIVE– CLASS = class1 class2 ...
$HASP250	$HASP250 jobname IS PURGED
$HASP301	$HASP301 jobname – DUPLICATE JOBNAME – JOB DELAYED
$HASP309	$HASP309 {XB \| bb} INIT nn INACTIVE {******** \|monitor} C = classes
$HASP373	$HASP373 jobname STARTED{– INIT nnn – CLASS x – SYS ssss}
$HASP395	$HASP395 jobname ENDED
$HASP523	$HASP523 jobname-device DELETED
$HASP524	$HASP524 devname INACTIVE
$HASP530	$HASP530 jobname ON device {nnnnn RECORDS}
$HASP532	$HASP532 jobname-device RESTARTED{, JOB HELD}
$HASP533	$HASP533 jobname-device DELETED
$HASP534	$HASP534 devname INACTIVE
$HASP540	$HASP540 jobname ON device {nnnnn RECORDS}

Rules Structure

The following table details the structure of the JES2 message suppression rules. All JES2 messages included in this solution are identical, except for their message IDs.

Table 36 JES Message Suppression Rule Structure

Item	Description
Title	JES2 Message Suppression
Name	message-id message-id can be any name (message ID), as listed in Table 35.
Table	SUPJES2
Message	message-id jobname ON device {progname} {FROM ijobid ijobname}
Message Description	JES2 received a JOB statement from device.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule suppresses the messages from the operator console. The message still appears in the system log.
Rule Actions	Suppresses the message from the system console.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in PROD mode. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	If suppression of the particular message is not required, delete the rule from the table.

JES3 Message Suppression

This solution contains rules to suppress certain JES3 messages from the system console. These messages are not suppressed from the system log.

Each message is suppressed by the rule that contains its message ID.

Rules

Table 37 lists the rules and the JES3 messages that they suppress.

Table 37 JES3 Message Suppression Rules

Rule	Message
IAT2000	IAT2000 JOB jobname(jobid) SELECTED main GRP=group {NET-ID=djnet}
IAT2006	IAT2006 PREMATURE JOB TERM – JOB jobname(jobid) {HELD \| RESTARTED \| PRINTED \| CANCELED}
IAT5200	IAT5200 JOB jobname (jobid) IN SETUP ON MAIN = main
IAT6101	IAT6101 {(jobid) \| (DEMSEL) \| JOB {jobno \| jobname}} jobid2 IS jobname PRTY=nnn [HOLD] [NETID=djnet]
IAT6108	IAT6108 JOB jobname (jobid) text [,NOTIFY NOT SENT, NO PATH]
IAT6118	IAT6118 nn CARDS FLUSHED [BEFORE JOB CARD FOUND]
IAT7001	IAT7001 JOB jobname (jobid) IS ON WRITER devname (ddd), RECORDS = {nnn \| NAVAIL} {PAGES = mmm}{(RESTARTED)}
IAT7007	IAT7007 JOB jobname (jobid) ON WRITER devname (ddd),DD=dsn, PURGED.
IAT7120	IAT7120 I/O ERROR ON con STATUS stat SENSE sens OP nn
IAT7450	IAT7450 JOB jobname (jobid) PURGED
IAT9123	IAT9123 DATA RECEPTION ACTIVE ON LINE lname
IAT9124	IAT9124 JOB RECEPTION ACTIVE ON LINE lname
IAT9127	IAT9127 JOB (jobid) IS jobname FROM nodename (userid)
IAT9190	IAT9190 JOB jobname (jobid) {JB \| OP} IS BEING SENT ON LINE lname
IAT9191	IAT9191 JOB jobname (jobid) {JB \| OP} SENT TO NODE nodename ON LINE lname

Rules Structure

The following table details the structure of the JES3 message suppression rules. All JES2 messages included in this solution are identical, except for their message IDs.

Table 38 JES3 Message Suppression Rule Structure

Item	Description
Title	JES3 Message Suppression
Name	message-id message-id can be any name (message ID), as listed in Table 37.
Table	SUPJES3
Message	message-id JOB jobname(jobid) SELECTED main GRP=group {NET-ID=djnet}
Message Description	Job jobname is scheduled to execute on a certain main system and group.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule suppresses the message from the operator console. The message still appears in the system log.
Rule Actions	Suppresses the message from the system console.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in PROD mode. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	If suppression of the particular message is not required, delete the rule from the table.

System Component Message Suppression

This solution contains rules to suppress certain TSO, VTAM, RACF, and DFHSM messages from the system console. These messages are not suppressed from the system log. Each message is suppressed by the rule that contains its message ID.

Rules

Table 39, Table 40, Table 41, and Table 42 list the rules and the TSO, VTAM, RACF, and DFHSM messages, respectively, that they suppress.

Table 39 TSO Message Suppression Rules

Rule	Message
IKJ144I	IKJ144I UNDEFINED USERID userid1 .. useridn
IKJ572I	IKJ572I USER userid NOT LOGGED ON, MESSAGE CANCELED
IKJ605I	IKJ605I TSOLOGON TERMINATED. TOO MANY ATTEMPTS. USER {userid \| UNKNOWN}
IKJ606I	IKJ606I TSOLOGON REJECTED. USERID, userid, IN USE
IKT100I	IKT100I USERID userid CANCELED DUE TO UNCONDITIONAL LOGOFF.
IKT108I	IKT108I userid {SEND\|RECEIVE} ERROR, RPLRTNCD=aa, RPLFDB2=bb, SENSE=code,WAITING FOR RECONNECTION termid.
IST532I	IST532I EVENT CODE = aaaaaaa EVENT ID = bbbbbbbb

Table 40 VTAM Message Suppression Rules

Rule	Message
IST234I	IST234I I/O ERROR termname, cmmod, ncpresp[, bstatus]
IST259I	IST259I INOP RECEIVED FOR nodename CODE = code [text]
IST530I	IST530I aaaaaaaa PENDING {FROM bbbbbbbb} {TO cccccccc } {FOR dddddddd}
IST532I	IST532I EVENT CODE = aaaaaaa EVENT ID = bbbbbbbb

Table 41 RACF Message Suppression Rules

Rule	Message
ICH408I	ICH408I USER(userid) GROUP(group) NAME(username) ICH408I {resource-name} {CL(class-name)} {VOL(vol)} ICH408I variable text ICH408I {FROM generic-profile-name (G)} ICH408I {ACCESS INTENT(intent) ACCESS ALLOWED(allowed)} or ICH408I JOB(jobname) STEP(stepname) SUBMITTER(userid) ICH408I {resource-name} {CL(class-name)} {VOL(vol)} ICH408I variable text ICH408I {FROM generic-profile-name (G)} ICH408I {ACCESS INTENT(intent) ACCESS ALLOWED(allowed)}
ICH70001I
ICH70001I userid LAST ACCESS AT hh:mm:ss ON www,month,day,yyyy

Rule

Message

ICH408I

ICH408I USER(userid) GROUP(group) NAME(username)

ICH408I {resource-name} {CL(class-name)} {VOL(vol)}

ICH408I variable text

ICH408I {FROM generic-profile-name (G)}

ICH408I {ACCESS INTENT(intent) ACCESS ALLOWED(allowed)}

ICH408I JOB(jobname) STEP(stepname) SUBMITTER(userid)

ICH408I {resource-name} {CL(class-name)} {VOL(vol)}

ICH408I variable text

ICH408I {FROM generic-profile-name (G)}

ICH408I {ACCESS INTENT(intent) ACCESS ALLOWED(allowed)}

ICH70001I

ICH70001I userid LAST ACCESS AT hh:mm:ss ON www,month,day,yyyy

Table 42 DFHSM Message Suppression Rules

Rule Name	Message Suppressed
ARC0100I	ARC0100I {RELEASE \| HOLD \| SETSYS} COMMAND COMPLETED
ARC0200I	ARC0200I TRAP IN MODULE pgm, CODE=cde, {LOG ALWAYS ADDED \| NODUMP ONCE ADDED \| FATAL ONCE ADDED \| DEBUG ALWAYS ADDED \| SNAP {ALWAYS \| ONCE \| NEVER} ADDED \| ABEND {ALWAYS \| ONCE \| NEVER} ADDED \| REMOVED}
ARC0208I	ARC0208I TRAP FOR ERROR CODE errcode, MODULE modname,{NODUMP ONCE \| FATAL ONCE \| DEBUG ALWAYS \| 200 MAXLIMIT \| SNAP {ALWAYS \| ONCE \| NEVER} \| ABEND{ALWAYS \| ONCE \| NEVER}
ARC0503I	ARC0503I ALLOCATION ERROR, {VOLUME=volser \| DATASET =dsname \| DD DUMMY}, RETURN CODE=rc, REASON CODE=reascode, INFO CODE=infocode
ARC0728I	ARC0728I VTOC FOR VOLUME volser1 COPIED TO DATASET dsname ON volser2
ARC0734I	ARC0734I ACTION=action FRVOL=volser1 TOVOL=volser2 {BLOCKS=blocks\|TRACKS=tracks} RC=retcde, REASON=rsncde, AGE=days, DSN=dsname

Rules Structure

The following table details the structure of the TAO, VTAM, RACF, and DFHSM message suppression rules. All JES2 messages included in this solution are identical, except for their message IDs.

Table 43 System Component Message Suppression Rule Structure

Item	Description
Title	System Component Message Suppression
Name	message-id message-id can be any name (message ID), as listed in Table 39 for TSO messages, Table 40 for VTAM messages, Table 41 for RACF messages, and Table 42 for DFHSM messages.
Table	SUPSYS
Message	message-id UNDEFINED USERID userid1 .. useridn
Message Description	An operator SEND command contains an undefined user. This user is ignored.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule suppresses the message from the operator console. The message still appears in the system log.
Rule Actions	Suppresses the message from the system console.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in PROD mode. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	If suppression of the particular message is not required, delete the rule from the table.