3.8 Uninstalling the Driver

3.8.1 Uninstalling the Security System Exits

The procedure you use for uninstalling the security exits depends on how you set them up.

If you linked the LDXNPXIT exit with exits of your own:

Reinstall your original exits, then IPL with CLPA to load the relinked exits in the active LPA.
If you change the exit names as you relinked them, be sure to also update the GSO EXITS record with the changed exit names.
Delete the exit modules from the LPA library containing them. Then IPL with CLPA at a convenient time.

If you are using LDXNPXIT, LDXNPHXT or LDXPOST alone:

Update the GSO EXITS record to remove the exit names.

Enter the following TSO commands:

 READY
acf
  ACF
set control(gso) sysid(system)
  CONTROL
insert sysid(system) exits lidpost() newpxit() npwpexit()

Install the new values. From an z/OS console, enter:
```
 MODIFY ACF2,REFRESH
```

Delete the exit modules from the LPA library containing them. Then IPL with CLPA at a convenient time.

Remove the change log started task (LDXLOGR) and driver shim (ACF2DRV) started task from your system startup and shutdown procedures.
Stop both started tasks (LDXLOGR and ACF2DRV).

For details, see Starting and Stopping the Change Log Started Task and Starting and Stopping the Driver Shim Started Task.
Remove members LDXLOGR and ACF2DRV from your started task procedure library.
Remove the driver load library from your APF list by modifying PARMLIB IEAAPFxx or PROGxx member as appropriate.

NOTE:If you use the dynamic APF facility, you can use the SET PROG command to activate your changes. Otherwise, you must IPL for the change to take affect.
Remove the LDXSERV and ACFQUERY TSO commands from IKJTSOxx.
Remove the driver files from the HFS:
```
  oshell rm -rf /opt/novell
```
Delete the SAMPLIB, LOAD and EXEC driver data sets.
Delete the change log data set that you created in Allocating and Initializing the Change Log Data Set.