If you were creating a note pad, the note pad might or might not have been created. If you were deleting a note pad, the note pad might or might not have been deleted. Your program might need to take a recovery action to determine how to proceed. For example, you might issue a query note pad request to see if the note pad exists and then proceed appropriately. If you simply reissue the request, your program might need to deal with additional failure conditions. For example, a second create note pad request might be rejected because the note pad already exists; a second delete note pad request might be rejected because the note pad no longer exists.

If you reissue a delete note pad request, consider specifying ETODCREATED to ensure that the correct instance of the note pad is deleted. If the original request actually deleted the note pad, some other thread might create a new instance of the note pad before the delete request can be reissued. Without the ETODCREATED specification, the reissued delete note pad request would unintentionally delete this new instance of the note pad.

A query note pad request can always be reissued.