|
|
Message Processing Facility exits can be useful, especially if a site has no console automation product, to automate responses to important console messages. If console messages are left totally unsuppressed then the console could become flooded with irrelevant or unimportant messages and the important messages may be missed in the chaos. IBM do supply a list of messages that are candidates for message suppression but it is up to a site to decide whether to be aggressive with message suppression, or to be conservative.
The usual disclaimers apply to all our code samples (including the MACROs).
This page contains MPF exit code to perform particular tasks that are useful at our site, you need to consider if they are relevant to your site and please, check with your site System Programmers before attempting to install any of these exits. You will need to change the in-use PARMLIB member in order to implement any of these exits so you are not likely to have access to this unless you are a System Programmer anyway!
These MPF exits should be assembled and linked into a library that is defined in the LNKLST concatenation.
Once they are in a LNKLST defined load library, you will need to change the MPFLST member of PARMLIB that is in use at your site. The following in the foramt of the MPFLST definitons:
msgid,SUP(NO),USEREXIT(Exit Name)
Obviously you will need to replace the values in the pertinent places with the definition.
It is always a good idea to not change the currently active MPF list member, but to create a new version. It is also recommended that messages be kept in alphabetic order
to assist in reading the member. It is not required, but we do recommend it.
All of these exit are available in one transmitted partitioned dataset from here.
If you prefer it in IEBUPDTE format then it too is available. The link for this is here.
Name
|
Description |
| | |
Abbydale Systems LLC. - Because IT matters
Page #1 2 Next Last
| ASLLLA1R | This MPF exit will issue a refresh for LLA when the message ASLLLA1R is issued.
Now given that ASLLLA1R isn't a standard IBM message and indeed stands no chance of being issued in the normal scheme of things, however, if you need something to issue the message then BSLBR14 is worth a look at.
Details of BSLBR14(ASLBR14) are available from this site.
If you wish to use a different message identifier you need only change the MPF list member. It is recommended that you use this exit with some caution, but we use it to refresh LLA when we assemble a new program/exit that resides in the LINKLIST chain.
|
|
| ASLLLA2R | This MPF exit is similar to ASLLLA1R except this exit contains a table of authorised jobnames.
If the jobname issuing the ASLLLA1R message isn't contained within the table, then the refresh won't be issued. |
|
| BPXI078D | This MPF exit will reply "Y" to the message to shutdown the z/OS zFS service.
This is usually only done at shutdown or to restart a zFS service, the premise is that if you are shutting it down you want that to happen as quickly as possible. There may be times when you didn't intend to issue the shutdown in the first place but in our case we only ever want it to close down.
The program assembly and link information can be accessed by clicking here. |
|
| DFHS517X | This exit will cause the MPF exit to cut an SMF record when the CICS system is started (Control is being given to CICS) or stopped (CICS is being terminated).
You probably already use things like SMF type 30 records to report CICS start and end times but for more accurate service level times this exit will report the times that a CICS system is actually up. A CICS regions is not truly available to users until the "Control is being given to CICS" message is issued.
In a similar, but often a less obvious way, a CICS system is unusable after the "Termination in Progress" message is issued.
Of course, the sample code provided will work for cutting a SMF record for any message you wish to cut an SMF record for.
The exit also shows how to build and issue a Write To Operator (WTO) in a MPF exit. |
|
| HASP190X | This MPF exit will issue a start command ($SPRTx) for a printer when $HASP190 is issued for it.
Back in the day operators had to physically load the FCB (Forms Control Buffer) using a paper tape loop and ready the printer with the correct paper, print chain etc. nowadays all that stuff is usually done by the printer and so operator interaction is less likely to be required. However, sometimes it is so further checking in the MPF exits may be required but it should be pretty intuitive as to how this can be done. If you need any further assistance though, please feel free to contact us. |
|
| IEA793AX | This MPF exit will reply "D" to the message that indicates that a dump cannot be taken.
This is usually because the disk containing the dump datasets is full.
The message itself is:
nn IEA793A NO DUMP DATA SETS AVAILABLE FOR DUMPID...
We only use this exit on our test and development systems as we really don't care about the dumps on these systems. Please follow our own sites standards when considering using this MPF exit. |
|
| IEBUPDTE.MPF.SOURCE | This offload file contains the source code for all of our released message processing exits (MPF)
For information about what each exit does and how to implement them. please see the link below.
There is also a XMI version of this file available from the list of XMI files.
Link to information page click here. |
|
| IEF176IX | This MPF exit will shutdown an external writer when it issues the IEF176I WAITING FOR WORK message.
The code uses SVC 34 to issue a stop (P) command for the writer. The code, as written, will check that the output class being spooled off is either class R or class L (usually the SYSLOG output class).
The code is fully functional and working but caution should be used before implementing this exit to ensure that output isn't discarded or overwritten.
Note that the sample JCL uses a separator routine (IEFSD094) which may or may not be installed at your site. Replace the output class being spooled but remember that the exit code will also need changing to reflect the change in output class. |
|
| IKT002IX | This simple MPF exit will change the text of the IKT002I message when the reason code is '04' to a more reasonable explanation. i.e. TSO is already running.
It will change the message:
IKT002I TCAS IS TERMINATING, REASON CODE= 04
which is basically saying that TSO is already active and change the message to:
IKT002I TSO ALREADY ACTIVE. REQUEST IGNORED
While this may seem like a fairly trivial exit it does demonstrate how to change the text of a message using a message processing exit. |
|
| MPF.SOURCE | This TSO transmitted file contains the source code for all our released Message Processing Exits.
Link to information page click here. |
| Page # 1 2 Next Last | |
