Using the JDBC driver, in the Sub channel I have been using
destCommandProcessor no problems. I send an XML Nodeset from a
variable, with an XML document to process, I get a response back
immediatly, I get my value out of it. All is good.

Now on the Publisher channel, I have an event coming from the DB, that
when it happens, I know my Subscriber event actually worked, so I want
to write some SQL back to the DB.

No problem, build the XML Doc, XML PArse() it, send it to
command:execute($srcCommandProccesor,$MyXMLDocVari able) and it gets
sent. I get this in immediate response:

13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT: Action:
do-set-local-variable("JDBC-RESULT",scope="policy",arg-node-set(token-xpath("command:execute($srcCommandProcessor,$JDBC-CALL)"))).
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT:
arg-node-set(token-xpath("command:execute($srcCommandProcessor,$JDBC-CALL)"))
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT:
token-xpath("command:execute($srcCommandProcessor,$JDBC-CALL)")
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT: Direct command from policy
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT:
<nds>
<input xmlns:jdbc="urn:dirxml:jdbc">
<jdbc:statement>
<jdbc:call-procedure jdbc:name="IDM_SMSYSGETNEXT_WO_DET_SEQ">
<jdbcaram>
<jdbc:value>0</jdbc:value>
</jdbcaram>
</jdbc:call-procedure>
</jdbc:statement>
</input>
</nds>
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT: Direct command from policy result
13:17:57 92197BA0 Drvrs: MAGIC-JDBC PT:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.0.20070315 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<status level="success">Document scheduled for execution on Subscriber
channel.</status>
</output>
</nds>

Bugger, I would prefer nothing till it was done, instead of that
Document scheduled message!!! If I got nothing, I am pretty sure I
would wait until success happened... But since I got a response, I move
on, and of course, I was expecting a <value> tag to grab a sequence
number out of (From my Stored procedure I called in the XML doc).

Eventually I get the response back, but man it is a long time (in trace
events) later (dozens and dozens of pages).

When I do this in the Sub channel, on the destCommandProccesor it takes
nearly no time at all it seems.

Any hints to resolve this timing issue? Is there a variable to
srcCommandProccessor to tell it to not say anything till it is done?
I.e. Suppress that Document is scheduled response?