Defining SAPI File Disposition

You can use the NODE SAPI_DISP parameter of the platform server to specify the disposition of a data set when a SPOOL request is completed.

You can set the following three dispositions:

  • KEEP: keeps the spool file.
  • HOLD: puts the spool file on hold, and tries the request again later.
  • DELETE: deletes the spool file.

The spool dispositions are used when a spool file request is completed and is removed from the platform server request queue. A request is removed from the request queue in the following three situations:

  • Successful request: the request is successfully completed.
  • Permanent network error: the request is ended with a network error and exceeds the try count defined.
  • Permanent Error: the request terminates with an error other than a network error.
Note: When a request receives a network error and the request is eligible for a retry, the disposition is hard coded as KEEP. In that way, the platform server tries the request again when the errors are reset.