You can configure the Z Common Data Provider System Data Engine to collect System
Management Facilities (SMF) data by using SMF user exit code that is provided with Z Common Data Provider. By using the SMF user exit, you can
collect and stream SMF data independently of whether SMF is running in log stream recording mode or
data set recording mode.
Before you begin
The SMF user exit will not affect any existing exits. Also, make sure that you set SET
IBM_RESOURCE = 'EXIT' in the SDE started task.Important: The SMF types that you define
on the SYS parameter in z/OS®
SYS1.PARMLIB member SMFPRMxx (or its
equivalent) do not take effect if you also have SUBSYS parameter definitions.
Therefore, if you define any subsystems, you must define the associated SMF types, and the MVS installation exits IEFU86, for each subsystem that is
specified by a SUBSYS parameter.
About this task
If you want to use the user exit to collect SMF data, install HBOSMF86 to the IEFU86 MVS installation exit.
For more information about MVS installation exits, see the z/OS MVS installation exits documentation.
An MVS installation exit does not receive control for records when the writing of the record is suppressed either because of a system failure or because of options that were selected at IPL time or by using the SET SMF command.
The SMF user exit code provided by the Z Common Data Provider is in the SHBOLPA library.
All modules in the SHBOLPA library must be added to the system link pack area (LPA). For more
information about the LPA, see the z/OS
MVS initialization and tuning documentation.
Procedure
To install the SMF user exit, complete the following steps:
-
Verify that the SMF IEFU8x exits are configured in the existing
SMFPRMxx member.
| Action |
Instruction |
|---|
Verify that the IEFU8x exits are enabled in the
SMPRMxx member |
- In the SYS parameter of your existing
SMFPRMxx member, you must ensure that IEFU86 exit is included in
the EXITS parameter. If the EXITS parameter is not coded
for the SYS parameter, you must code the EXITS parameter
for the SYS parameter to include all the required SMF user exits including
IEFU86.
- If there are SUBSYS parameters in your existing
SMFPRMxx member, and the EXITS parameter is
coded for the SUBSYS parameter, you must ensure that IEFU86 exit is included in
the EXITS parameter.
|
-
To add the load modules to an LPA, complete one of the following actions:
| Action |
Instruction |
|---|
| Add the SHBOLPA library to the pageable link pack area (PLPA) at system IPL |
Add the following statement to an LPALSTxx member, but
replace hlq with the target library high-level qualifier that is used to install
Z Common Data Provider, and replace
volume with the volume identifier of the data set:
hlq.SHBOLPA(volume)
|
| Add the individual modules in the SHBOLPA library to the dynamic LPA after the system
IPL |
Run the following MVS system
command:SETPROG LPA,ADD,MODNAME=HBOSMF86,DSNAME=hlq.SHBOLPA
|
-
To install the exit, complete one of the following actions:
| Action |
Instruction |
|---|
| Install the user exit on an MVS installation exit at
system IPL |
Add the following statements to a PROGxx member of
library
SYS1.PARMLIB:EXIT ADD EXITNAME(SYS.IEFU86) MODNAME(HBOSMF86)
If
you specified any subsystems in an SMFPRMxx member, you must add
the exit to those subsystems. For example, for the subsystem JES2, you must add the following
statements: EXIT ADD EXITNAME(SYSJES2.IEFU86) MODNAME(HBOSMF86)
|
| Dynamically install the user exit after the system IPL |
Run the following MVS
commands:SETPROG EXIT,ADD,EXITNAME=SYS.IEFU86,MODNAME=HBOSMF86
If you
specified any subsystems in an SMFPRMxx member, you must define
the exit to those subsystems. For example, for the subsystem JES2, you must run the following
commands: SETPROG EXIT,ADD,EXITNAME=SYSJES2.IEFU86,MODNAME=HBOSMF86
|