SMF Extensions › Features and Benefits › System Requirements

System Requirements

The following system related facts should be considered when running SMF/E:

• SMF/E utilizes CAIRIM, one of the CA Common Services for z/OS CAIRIM is a collection of dynamic initialization routines that eliminate the need for User SVCs, SMF exits, subsystems, and other installation requirements required in prior releases of this product.
• CAIRIM must be run with the specific CA JARS family PARM prior to the activation of SMF/E. Running CAIRIM does not activate SMF/E. See the Installation Guide for more information.
• SMF/E no longer uses SMF exits. All SMF information used by SMF/E is obtained by a dynamic intercept that gains control prior to any SMF exits. The intercept is done using dynamic front ends, where we branch to our code and then back to the real IBM routines. No changes to the operating system, no replacements of IBM modules, and no overlays of IBM code are used. The technology is as reliable as the SMF exit conventions themselves.
• SMF/E requires that the target library, CAI.CAJRLOAD, be in the Linklist and APF-authorized.
• A small amount of CSA, probably under 4K, is needed by SMF/E.
• SMF/E messages CAJR250I, CAJR251I, and CAJR252I are written to the JOB LOG for each job. These messages are written with a Write-To-Operator (WTO) specifying ROUTCDE=11. For those jobs (notably started tasks) that have no RPL for the Job Log data set, these SMF/E messages appear in the SYSLOG. Any consoles in the complex servicing ROUTCDE=11 receives these messages. If you do not want them to display on any particular console, then change the console ROUTCDE so that ROUTCDE=11 is not serviced. Alternatively, the messages can be suppressed entirely from all consoles in your complex by specifying message suppression in MPFLSTxx (Message Processing Facility List) for the three messages.
• Once SMF/E is customized to your installation requirements, a procedure should be installed in a proclib that can be used to activate and deactivate SMF/E. The activation procedure can also be started through your COMMNDxx SYS1.PARMLIB member. This ensures that SMF/E is started after every IPL.