You can skip this step if you are not using SMF logstream recording, but if you are planning to use it in the future, it is a good idea to perform this step now. It will have no impact on your operation but when you do convert to SMF logstream recording, the logstream dump process exits will already be registered.
If you are using SMF logstream recording and have a level of z/OS that supports the SMFDLEXIT parameter in the SMFPRMxx member of PARMLIB, you must complete this step. (SMFDLEXIT was added to z/OS 1.9 through 1.11 with a PTF and is built into z/OS 1.12 and above.)
CA SMF Director uses the IBM utility IFASMFDL to dump data from SMF logstreams. To do this, these three user exits control how IFASMFDL obtains the data for CA SMF Director:
|
Exit Point |
CA SMF Director Exit Name |
|---|---|
|
USER1 |
SMFDLX1 |
|
USER2 |
SMFDLX2 |
|
USER3 |
SMFDLX3 |
In order for these exits to be called, they must be registered with SMF in the SMFDLEXIT statement in the SMFPRMxx member that is active. To do this, code this statement:
SMFDLEXIT (USER1(SMFDLX1),USER2(SMFDLX2),USER3(SMFDLX3))
If additional user exits for IFASMFDL are needed, they can be added to the USER1, USER2, and USER3 operands as needed. For example, if your site has another IFASMFDL user exit 2 named UX2TEST, it can be coded like this:
SMFDLEXIT (USER1(SMFDLX1),USER2(SMFDLX2,UX2TEST),USER3(SMFDLX3))
For more information on the SMFDLEXIT parameter, see the IBM MVS Initialization and Tuning Reference guide.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |