As of z/OS® Version
1 Release 12 Message Flood Automation is part of the z/OS operating system; therefore, you no longer
require the IEAVMXIT ++USERMOD for Message Flood Automation and need
to remove it. If you have already used the PTF for OA25602 on z/OS Version 1 Release 11 to implement
the ++USERMOD for Message Flood Automation, do not reapply the ++USERMOD
through the SMP/E RESTORE command on Version 1 Release 12. Review
all Message Flood Automation user exits to verify the appropriate
actions to take in order to ensure successful migration to the new
version of Message Flood Automation for Release 12.
If you have been using Message Flood Automation and
want to install a new level, take the following actions:
- Remove Message Flood Automation processing from the MPF installation
exit IEAVMXIT. If Message Flood Automation is the only user of IEAVMXIT,
do the following:
- Replace the UEXIT(Y) parameter with UEXIT(N) on the INIT statement
with the CONSOLxx PARMLIB member.
- Remove IEAVMXIT from the LINKLIST concatenation.
If Message Flood Automation is not the only user of IEAVMXIT,
do one of the following: - Fall back to the earlier version of the exit without Message Flood
Automation invocations.
- Remove the invocations of Message Flood Automation from the exit.
Reassemble and rebind the exit to verify that the new exit has replaced
the old exit in the LINKLIST concatentation.
- Remove the invocation of Message Flood Automation from the CNZZVXT2
sample program. Reassemble and rebind the exit to verify that the
new exit replaced the old exit in the LINKLIST concatenation.
- Remove IEAVMXIT from the LINKLIST concatenation.
- If Message Flood Automation is the only user of the command processing
exit specified for USEREXIT on the MPFLSTxx .CMD statement, before
you load the initial program of z/OS Version
1 Release 12, remove the .CMD statement from all MPFLSTxx members
in which the exit has been specified. If Message Flood Automation
is not the only user of the exit, remove the CNZZCMXT entry from
all .CMD statements.
- Remove all invocations of the SETMF FREE command from the system,
including COMMNDxx and automation.
- You are not required to make changes to the MSGFLDxx PARMLIB member.
Because Message Flood Automation commands are now subject to authorization
checking, you can define the Message Flood Automation commands to
your security product. For profiles defined to security products,
you can see the table MVS™ Commands, RACF® Access Authorities, and Resource
Names in z/OS MVS System Commands.