Abbydale Systems LLC. - Because IT matters

	System Exits	We would be very neglectful if on this page we didn't issue a warning about SMF, or indeed any, system exits. Exits have the potential to make your operating system useless so extreme caution should be exercised before implementing any new exits or recoding any old exits. If possible always use a sandbox system for the testing of your exits. This page provides information and some sample code for SMF (System Management Facilities) exits. Most sites have some SMF exits installed, usually for accounting purposes. IEFACTRT is an exit that most sites use to produce resource usage statistic for a job, but there are several other useful SMF exits. It is up to the individual site to determine which, if any, SMF exits to install and implement. We only offer these exits here as examples, however, these exits are implemented and working on our system.
	Installation	Installation will depend upon how your site implements SMF exits. For a full explanation of how to activate and deactivate exits please refer to the IBM publication "z/OS Initialization and Tuning Reference". In any case SMF exits should be re-enterant and authorised. They should be assembled and linked into a library that is in the system concatentation (usually LPA lib). The target load library must also be authorised. If an exit fails to load it will be disabled.

Exit

Description

IEFU29

Source Code

Program Information

XMI File

SMF Dataset Switch Exit.

This exit is invoked when the system switches to a different SMF dataset.

The exit checks to see if the last available dataset is being processed the exit will issue a start command for SMFDUMP.

Obviously, if your site doesn't use a procedure named SMFDUMP to offload the data from the SMF datasets, then you need to change the start command in the code.

If your automation package is being used to process the SMF datasets when the IEE985A message is issued, then you should carefully consider the implications of using this exit.

The advantage of letting IEFU29 handle the condition rather than an automation package is that using IEFU29 doesn't rely on any 3rd party software and will trigger even if the automation package isn't running...but the choice is your sites to make, not ours.