OPSMVS alerting on IOEZ00581E when previously it did not

Document ID : KB000117094
Last Modified Date : 08/10/2018
Show Technical Document Details
Our OS team recently applied some IBM critical maint over this past weekend.
They are now getting multiple auto-generated tickets for the message id IOEZ00581E and IOEZ00830E.
Previous to this weekend these messages did not result in auto-generated tickets. We are trying to help our OS team out with their IBM case to determine if some new route/desc codes were changed or action bits changed that would cause the new alerting so that IBM can correct it if possible.
The AFLAGS have changed from old v. new. Not sure if this is indicative of the issue or not. The ROUTE/ROUTEX appear to be the same in the OPLSOG column from old v. new. 
The updated version of the IOEZ00581E and 830E messages no longer have the cmdresponse bit set on. The immediate action bit is still the same and the urgent message bit is unchanged - not set.
The AOF rules guide for MSG rules lists the bit to check in the OPSLOG display columns for the AFLAGS and OPSFLAGS fields. This bit breakdown is easier to see in the Display all columns panel in OPSLOG (place cursor on event text and hit enter), then place the cursor on the AF field and hit enter - the bits are explained at the very bottom of the panel.
The 2 messages are alerts that indicate a zfs file is quiesced. Now it's not certain if the message comes out right after the file has been quiesced or after some time as if just giving a status.
IBM did correct an old issue they had for incorrect bit setting, APAR OA54303. So now the system is alerting on a message that never alerted on before and aren't too concerned on.