ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

z/OS SMF records & UC4

book

Article ID: 88883

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

z/OS SMF records & UC4

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

General


The Automic z/OS Agent – or the Event Monitor – can use SMF records for the following functionality:
· Automatic File-System Events
o Support of Generation Data Groups
· Recognizing and assessing job ends
To use this feature it is important that the SMF subsystems logs all SMF records of type 14, 15, 30 and 64. Make sure that the exits IEFU83 and IEFU84 are active.

Solution

 

Check current SMF configuration
All details about the SMF configuration can be found in the SMFPRMxx member, which is located in the PARMLIB, 'xx' stands for the current SMF suffix number. E.g.:
SYS1.PARMLILB(SMFPRM00)
SYS1.ASAMPLIB(SMFPRM00)
ADCD.ZOSV1R3.PARMLIB(SMFPRM01)
 
With the following MVS command it is possible to find out which members currently active is (D stands for display):
D SMF,O
D PROG,EXIT
 

 

With the following MVS command it is possible to find out which exit module (e.g. AutomicEXIT) has connected to the default exits; connected modules are active (D stands for display):

 

D PROG,EXIT,EN=SYS.IEFU83,DIAG
D PROG,EXIT,EN=SYS.IEFU84,DIAG
 
In case of another member is active, it is possible so switch so another member using the MVS SET command. The change takes place immediately:
SET SMF=xx
'xx' stands for the suffix number of a SMFPRMxx member. – This command may change the current system configuration!
 
Note: SMF settings are always related to the LPAR. That means in an SYSPLEX environment it is important to have the same configuration on each LAPR.
?