ITransactionPhase0NotifyAsync::Phase0Request
Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
The DTC Proxy calls this method to notify a Phase0 participant that phase 0 processing has commenced. The Phase0 participant must perform any operations necessary to ensure the transaction is in a state where it can begin two-phase commit and then signal completion using the ITransactionPhase0Enlistment::Phase0Done method.
A phase0 participant that receives a phase0 notification after calling Unenlist may choose to call Phase0Done but is not required to do so.
Syntax
HRESULT Phase0Request( BOOLfAbortHint);
Parameters
fAbortHint
[in] A value of TRUE provides the phase0 participant with an indication that further work on this transaction is not worth pursuing, since another participant has already aborted the transaction.
Note
Certain Phase0 participants such as caches may choose to simply invalidate portions of the cache rather than flushing them to stable storage or other Resource Managers. The fact that the fAbortHint argument is FALSE does not in any way imply that the transaction will eventually commit (since other phase0 participants or Resource Managers may subsequently abort it)—it merely implies that at Phase0Request time, the eventual outcome is still uncertain.
Return Values
S_OK
Success—The Phase0 participant has been notified that the transaction is ready to enter phase one of 2PC.
Requirements
For an explanation of the requirement values, see Requirements (Component Services).
Platforms: Windows Server 2016, Windows 10, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista
Header: Declared in txdtc.h