Enabling SMF exits - ironstream_for_servicenow_discovery_1 - 7.5

Ironstream™ Software for ServiceNow® Discovery for IBM Z® Installation

Product type
Software
Portfolio
Integrate
Product family
Ironstream™ software
Product
Ironstream™ software > Ironstream™ software for ServiceNow® Discovery
Version
7.5
ft:locale
en-US
Product name
Ironstream™ Software for ServiceNow® Discovery for IBM Z®
ft:title
Ironstream™ Software for ServiceNow® Discovery for IBM Z® Installation
First publish date
2007
ft:lastEdition
2026-02-03
ft:lastPublication
2026-02-03T14:17:18.347000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Ironstream
L4_Investment_Segment
Log Data Integration
L5_Product_Group
LDI - Ironstream
L6_Product_Name
Ironstream for ServiceNow

If you intend to capture SMF records for the job or program probes, copy these three load modules:

EVIEFU83

EVIEFU84

EVIEFU85

from the Ironstream LOAD library to a LINKLST library on the system, such as SYS1.LINKLIB. Enter the console command:

F LLA,REFRESH

to refresh the linklist, incorporating these Ironstream exits.

Verify that the exits IEFU83, IEFU84, and IEFU85 are being driven for all your subsystems.

If you specify subsystems in your SMF parameters, such as JES2 or TSO, you must specify these three exits in every one to ensure z/OS activates them. If you only define the exits at the SYS level, or if you leave them all active by default, and there are no other EXIT options, all these exits will be active in all subsystems.

The z/OS SMF parameters are such that any EXIT definition within a subsystem is taken as the complete list of exits to be activated. There is no "flowing down" from the default or the SYS level.

By looking at the output of a 'D SMF,O' console command, you can check which exits are defined and from where. Each line of that output is tagged with DEFAULT if this is a default value, SYS if it is taken from the SYS definitions, and PARMLIB if it is explicitly defined in a PARMLIB member.

The following is an example of defining the required exits at the SYS level. However, if you define any EXIT parameters for other subsystems, these exit definitions need to be repeated in full in each one.

SYS(NOTYPE(16:19),EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT, IEFUSI,IEFUJI,IEFU29),NOINTERVAL,NODETAIL)