As I recall the SQL end command nucleus extension stacks something.
On 16 January 2013 04:21, Glenn Knickerbocker <[email protected]> wrote: > I had forgotten this quirk that I wondered about before, and just > stumbled on it again. After I use PIPE SQL, when I get back to the > RDYMSG (which is rare, because I normally run a shell exec) I get two > messages: > >> Ready; T=0.06/0.08 21:38:22 >> Ready; T=0.01/0.01 21:38:22 > > While I'm still in the calling exec, QUEUED() and EXTERNALS() both > return zero, and running Rich McAllister's ENDCMD MODULE to trigger > ENDCMD processing doesn't have any effect. Any idea what's up here? > > ¬R
