Data Set Violation Exit (DSSVIOEX) remove.

Products

• ACF2 - z/OS

Issue/Introduction

We have a DSN violation exit, DSSVIOEX, registered in our GSO records. We believe its function is obsolete. We would like to test that hypothesis. What would happen if we renamed the DSSVIOEX module and then IPLed. Would ACF2 just complain that it cannot find the module, or would it stop ACF2 from starting?

Environment

Product: ACF2

Resolution

DSSVIOEX (the ACF2 Data Set Violation Exit) still exists, but it is rarely used today because newer SAF/ACF2 facilities provide better and more flexible control. Many sites no longer customize it unless they have very old legacy logic.

Recommend testing this on a Test Lpar if you want to remove DSN violation exit, DSSVIOEX.

You can remove the USERMOD from SMP/E (optional) or simply delete/rename the module from the loadlib  (recommended only if you know nothing else references it)

Also, see Exit Specifications (EXITS) section Process the GSO EXITS Record.