Control the invocation of data reduction exit routines

Description: As of z/OS V2R1, if you are running unauthorized applications that invoke the RMF Monitor II Sysplex Data Gathering service (ERB2XDGS) or the RMF Monitor III Sysplex Data Retrieval service (ERB3XDRS), you must take certain actions to allow the applications to make use of data reduction exit routines

Element or feature:

RMF.

When change was introduced:

z/OS V2R1. This function is rolled back to z/OS V1R13, z/OS V1R12, and z/OS V1R11 with APAR OA38022 for RMF Monitor II service and APAR OA37965 for RMF Monitor III.

Applies to migration from:

z/OS V1R13 and z/OS V1R12, both without the PTFs for APARs OA38022 and OA37965 applied.

Timing:

Before the first IPL of z/OS V2R1.

Is the migration action required?

Yes, if you have unauthorized applications that invoke ERB2XDGS (RMF Monitor II Sysplex Data Gathering service) or ERB3XDRS (RMF Monitor III Sysplex Data Retrieval service).

Target system hardware requirements:

None.

Target system software requirements:

None.

Other system (coexistence or fallback) requirements:

None.

Restrictions:

None.

System impacts:

None.

Steps to take: To allow your applications to make use of data reduction exit routines specified with the ERB2XDGS or ERB3XDRS services, take the following actions:

If the application has been designed to run authorized, you must adapt the application or program so that it runs in supervisor state, system state, or be APF authorized.
You can approve the exit by adding RACF resource ERBSDS.MON2EXIT.<exit_name> or ERBSDS.MON3EXIT.<exit_name> to the RACLISTed class FACILITY and by granting read access to the profile for the user ID that invokesg the Sysplex Data Server API.
If you are running an unauthorized application that invokes RMF Monitor II Sysplex Data Gathering service ERB2XDGS/ERB2XD64 or Monitor III Sysplex Data Retrieval service ERB3XDRS/ERB3XD64, you must take one of the following actions to allow the application to make use of data reduction exits.
1. If the application is properly designed and secure to run authorized, you must adapt the application or program so that it runs in supervisor state, system state, or APF authorized.
2. You can approve the exit by adding RACF resource ERBSDS.MON2EXIT <exit_name> or ERBSDS.MON3EXIT<exit_name>.RACLISTed class FACILITY and by granting read access to the profile for the user id invoking the Sysplex Data Server API.

Reference information: For details about the RMF sysplex data services see z/OS RMF Programmer's Guide