...

Overview

...

Certain MVS installation exits are utilized by the following Universal Agent components to provide their

...

services:

• Universal Command Server uses one SMF exit to provide support for starting Started Tasks (STC) using Universal Command Manager. If Universal Command STC support is not required, the SMF exit does not need to be installed.
• Universal Automation Center Agent uses
a number of SMF
• several exits to provide a range of services available in Universal Controller.

The following sections describe how to install the

...

exits for each component. The

...

exits are only required if the component or component services are required.

SMF Exit Introduction

...

Note
title Note
For detailed information on SMF, MVS installation exits and their configuration, refer to the IBM manuals MVS System Management Facilities (SMF), MVS Installation Exits, and MVS Initialization and Tuning Reference.

SMF configuration is performed with SYS1.PARMLIB (PARMLIB) member SMFPRMxx. SMF configuration relevant for product installation is the SMF record types being recorded and the SMF exits defined. The SMFPRMxx parameters SYS and SUBSYS define these SMF recording options. The SYS parameter specifies system wide recording options for all subsystems (JES2, TSO, STC, etc.). The SUBSYS parameter specifies subsystem specific recording options. The SUBSYS parameter options override the equivalent options specified on the SYS parameter. Any SUBSYS parameter option not specified will default to the SYS parameter option.

The following example illustrates how SMF SYS and SUBSYS parameters work together.

Panel
SYS( EXITS(IEFU83,IEFU84) ) SUBSYS( STC, EXITS(IEFU83) )

The SYS parameter EXITS option defines the two SMF exits IEFU83 and IEFU84. The SUBSYS parameter for the STC subsystem also specifies the EXITS option, overriding the SYS EXITS option. The SUBSYS parameter EXIT option defines one SMF exit IEFU83 for the STC subsystem. Consequentially, only the IEFU83 exit is called for the STC subsystem workload. The IEFU84 exit is not called for STC subsystem workload. For all workload other

...

than the STC subsystem, the SMF exits IEFU83 and IEFU84 are called.

Once SMFPRMxx has defined the appropriate SMF record types to collect and the SMF exits to activate, the product SMF exit routines are

...

defined to SMF.

IBM provides the dynamic exit facility to

...

manage exit routines dynamically and at IPL. IBM has defined all the SMF exits to the dynamic exit facility. The exit routines are added or removed from SMF

...

exit points using the PROGxx PARMLIB members or the MVS SETPROG EXIT command. The PROGxx EXIT statements used to add product exit routines are

...

detailed in the appropriate sections below.

Note
The SETPROG command is documented in the IBM manual: MVS system commands reference.

The exit names used in the dynamic exit facility are formatted as SYSssn.exitname, where ssn is the subsystem name, or blank if it is a system wide exit, and exitname is the name of the exit, such as IEFU83. The following table provides some example dynamic exit facility exit names.

Name	Description
SYS.IEFU83	The default SMF exit IEFU83 for all system workload types.
SYSSTC.IEFU83	The SMF exit IEFU83 for STC subsystem workload.
SYSJES2.IEFU83	The SMF exit IEFU83 for JES2 subsystem workload.

...

...

When using SMF Exit items, please check against conflicting existing SMF definitions, such as SYSJES2.IEFXXX.

Universal Command Server

The Universal Broker STC establishes the environment to support STC execution by Universal Command Server. Part of the environment consists of adding SMF exit routine UNVACTRT to SMF exit point SYSSTC.IEFACTRT.
 

...

The Universal Automation Center Agent (UAG) establishes the environment to support Universal Controller services on z/OS. Part of the environment consists of establishing the following exit routines:

Configuring SMF

Configuring SMF consists of specifying required SMF record types to collect and the required exit points to define.

The SMF configuration must meet the following requirements:

• SMF record types 14, 15, 16, 17, 18, 30, and 70 must be collected.
• System exit points IEFUSI, IEFU83, and IEFU84 must be defined.
• Assuming the Universal Command SMF exit is installed or there is already a SUBSYS EXITS option for STC, the subsystem STC exit point IEFU83 must be defined.

The record types and exit points are defined in the SMFPRMxx PARMLIB member. The following SMFPRMxx statements illustrate how to define the record types to collect and exit points.

The SYS statement uses the NOTYPE parameter to exclude specific record types. This is one of many ways the SYS statement can be specified to meet the SMF record type requirements.

...

Configuring SMF

Configuring SMF consists of specifying required SMF record types to collect and the required exit points to define.

The record types and exit points are defined in the SMFPRMxx PARMLIB member.

Installation job UNVIN14 can be used to verify that the correct record types are being collected and the correct exits are defined on the SYS and SUBSYS keywords. This job will read in the SMF configuration member for the system, check the appropriate record and exit definitions are present and produce the PARMLIB PROGxx member ADD EXIT statements required for UAG to function.

When job UNVIN14 is executed, it checks that SMF configuration meets the following requirements:

• If SUBSYS(SYSJES2, …) or SUBSYS(SYSJES3, …) is defined, SMF record types 15, 17, 18, 30 (subtypes 4 and 5) and 70 must be collected for it. In this case, only SMF record types 15, 17, 18 and 70 must be collected for SYS(…).
• If neither SUBSYS(SYSJES2, …) nor SUBSYS(SYSJES3, …) is defined, SMF record types 15, 17, 18, 30 (subtypes 4 and 5) and 70 must be collected for SYS(…).
• SMF record types 15, 17, 18 and 70 must be collected for every other SUBSYS(…).
• If SUBSYS(SYSJES2, …) or SUBSYS(SYSJES3, …) is defined, SMF exits IEFUSI, IEFU83, and IEFU84 must be defined for it. In this case, only exit IEFU83 must be defined for SYS(…).
• If neither SUBSYS(SYSJES2, …) nor SUBSYS(SYSJES3, …) is defined SMF exits IEFUSI, IEFU83, and IEFU84 must defined for SYS(…).
• SMF exit IEFU83 must be defined collected for every other SUBSYS(…)
• Other record types can be collected as required and will be ignored by the UAG exits.
• Other exits can be defined without impacting UAG behavior.

Job UNVIN14 will produce the required ADD exit statements. It might also point out issues with the configuration that might cause problems with proper UAG processing. It will also produce an ADD EXIT statement for CNZ_WTOMDBEXIT module UAGWMDBX. This is not an SMF exit by is still required for UAG to operate.

If the SMFPRMxx PARMLIB member has been modified, the SMFPRMxx member can be activated dynamically by restarting SMF with the following command:

The following console command displays the active SMF options:

Installing SMF Exit Routines

The

...

exit routines are installed using the appropriate PROGxx PARMLIB member. The ADD EXIT statements for the PROGxx PARMLIB member

...

CNZ_WTOMDBEXIT is not an SMF exit, so it can be configured simply by coding an EXIT statement in a PROGxx PARMLIB member.

For example:

...

can be created with installation job UNVIN14.

The exit routines are added when the system is IPL'ed and the PROGxx member is processed. The SMF exit routines can be added dynamically without an IPL by activating PROGxx member with the SET console command. The following SET command activates

...

PROG member xx.

The PROGxx PARMLIB member is documented in the IBM MVS Initialization and Tuning Reference manual. The SET console command is documented in the IBM MVS System Commands manual.