What's a quick way to inactivate an ACF2 exit?

Document ID : KB000025503
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

An ACF2 "local" exit (defined in the GSO EXITS record) is causing serious production problems. I need to inactivate it until I can find out what's wrong.  How can I do that?

Answer:

The objective is to remove the active exit that is causing the problem. There are a couple of ways to do this, depending on whether an administrator can access the GSO records. If the GSO records can be updated, issue the ACF commands:

SET C(GSO)

CHANGE EXITS   exitname()    where exitname is the specific exit to be deleted, e.g., VIOEXIT, RSCXIT2, DSNPOST, etc.
F ACF2,REFRESH(EXITS)             to bring in the modified EXITS record

If the administrator is unable to change the GSO EXITS record, then issue the operator command F ACF2,REFRESH(EXITS),SYSID(BOGUS) where BOGUS is a sysid that does not exist among your GSO records. This will bring in a default EXITS record with all the exits set to NONE.
CAUTION: If you have more then one exit active, this option will temporarily disable all of the exits till the EXITS record is restored.

When the problem exit has been removed, correct it, reassemble it and link it into CAILPA. Then refresh LLA with operator command, F LLA,REFRESH.

You can then reactivate the exit by issuing the F ACF2,REFRESH(EXITS) command to retrieve the original EXITS record. If a SYSID was specified when starting ACF2, that SYSID should be specified on the REFRESH command.

If the EXITS record was changed to delete the problem exit, the record should be changed to restore the module name for that exit before issuing the F ACF2,REFRESH(EXITS) command again.