Updating SMF parameters
Updating SMF parameters is necessary to activate the exits used by the agent for z/OS for event tracking.
- IEFACTRT
- Job-end and step-end exit.
- IEFUJI
- Job initiation exit.
- IEFU83
- Record write exit.
- 26
- For all job tracking
- 30
- For all job tracking
- 14
- only for EDWA with SRREAD=YES
- 15
- only for EDWA SRREAD=YES or SRREAD=NO
- 64
- only for EDWA with VSAM data sets
- Read processing
- Output processing
- Either read or output processing
- Type 14 records are required for non-VSAM data sets opened for INPUT or RDRBACK processing.
- Type 15 records are required for non-VSAM data sets opened for output.
- Type 64 records are required for VSAM data sets.
- Type 90 records support daylight savings time automatically (optional).
To avoid data set triggering, and thus to improve performance, specify SRREAD=NO in the IEFU83 SMF exit on invocation of the EELEXIT macro. The SRREAD=NO parameter prevents data set triggering for only SMF record type 14.
/*SYS and SUBSYS keywords*/
SYS(TYPE(4,5,6,14,15,28,30,37,38,39,64,70,71,72,73,74,75,76,77,78))
SYS(EXITS(IEFACTRT,IEFUJI,IEFU83,IEFU84,IEFU85,IEFUTL,IEFU29,IEFUJV))
SUBSYS(STC,EXITS(IEFACTRT,IEFUJI,IEFU29,IEFU83,IEFU84,IEFU85))
SUBSYS(JESn,EXITS(IEFUJI,IEFACTRT,IEFU83))
- JESn is either JES2 or JES3. This parameter does not refer to JES itself, but to batch jobs handled by JES. So do not suppress exit invocation. Ensure that you do not specify TYPE6=NO and TYPE26=NO on the JOBCLASS and STCCLASS statements of the JES2 initialization parameters.
- You might find it useful during installation to code two SMFPRMnn members, one with the exits active and the other with the exits inactive. You can then use the SET SMF=nn z/OS® command to switch your current SMF parameters to the new member. By switching back, using the SET SMF=nn command, you avoid the need to re-IPL, if you encounter a problem.
- Exits for SUBSYS STC are required only if you run
also HCL Workload Automation for Z in the same system. If
you run only the agent for z/OS, the
following line is of no use:
SUBSYS(STC,EXITS(IEFUJI,IEFACTRT,IEFU83))
Use the PROGnn parmlib member to specify installation exits and control their use. Using PROGnn, you can associate multiple exit routines with installation exits at IPL, or while the system is running. Consider using PROGnn in addition to SMFPRMnn to specify exits, whether or not you want to take advantage of these functions.
SYS(...EXITS(IEFACTRT,IEFUJI,IEFU83))
you
would add this to get the equivalent processing in PROGnn: EXIT ADD EXITNAME(SYS.IEFACTRT) MODNAME(IEFACTRT)
EXIT ADD EXITNAME(SYS.IEFUJI) MODNAME(IEFUJI)
EXIT ADD EXITNAME(SYS.IEFU83) MODNAME(IEFU83)
- For exits listed on the EXITS keyword of the SYS statement in SMFPRMnn, each exit will have the name SYS.xxxx (where xxxx is one of the exits listed).
- For exits listed on the EXITS keyword of the SUBSYS statement of SMFPRMnn, each exit will have the name SYSzzzzz.xxxx (where zzzz is the name of the subsystem and xxxx is one of the exits listed).