Overriding delete requests
Your resource manager can override parameters specified on an IXGDELET
request by manipulating the RMEPLDELETEOVERRIDEBLOCKID field mapped
by the IXGRMEPL mapping macro. The resource manager manipulates the
field in the parameter list (RMEPL) passed to the resource manager
exit as follows:
- Proceed with the delete operation as requested on the IXGDELET request. This is specified by placing a return code of binary zeros in register 15.
- Do not proceed with the delete operation requested on the IXGDELET request. This results in no log blocks being marked for deletion in the log stream. This is specified by placing a return code of X'08' in register 15.
- Override the log block identifier specified on the IXGDELET request with one specified by the resource manager. The overriding log block identifier must be less than or equal to the log block identifier specified on the IXGDELET request. This is specified by placing a return code of X'04' in register 15.
If you specify FORCE=YES on a delete request, the resource manager exit is called, but cannot override the delete request.
If you specify AUTODELETE=YES for a log stream and you also manage that log stream with a resource manager and a resource manager exit, note that the automatic deletion processing takes precedence over the delete override processing performed by the resource manager exit. Log data that is deleted by automatic deletion does not trigger the resource manager exit, so the exit cannot override the delete request. IBM® recommends AUTODELETE=NO for a log stream managed by a resource manager that needs to override delete requests.