tcc /c {cmd} - how to get the value of cmd in TCEXIT

[MikeBaas]

i would like to tweak my TCEXIT.BTM so that it checks the exist code (done) and if we had a problem, does a PAUSE (so that I have a chance to see what was going in a cmd session that whatever link may have fired).

Now, is it possible when a session was started with /c {myCmd} to execute a command find out what that command was?

 

[vefatica]

Maybe %CMDLINE or %@HISTORY[1] will help.

v:\> %comspec /c echo blah!
blah!

v:\> echo %cmdline
D:\tc31\TCC.EXE /c echo blah!

v:\> %comspec /c echo blah!
blah!

v:\> echo %@history[1]
D:\tc31\TCC.EXE /c echo blah!

 

[vefatica]

I probably misunderstood. You want the transient (/c) TCC's TCEXIT.BTM to know what the command was ... right? It's clumsy, but you could put the command into an environment variable that would be inherited by the transient TCC and thus known to its TCEXIT.BTM.

set transient_cmd=whatever
%comspec /c %transient_cmd

 

[MikeBaas]

yeah, you're right about the transient cmd. Will use that one, thanks!

 

[AnrDaemon]

does a PAUSE

Very, very, VERY bad idea. The moment your background script permanently blocks on some error message you get your system filled with dead sessions to complete denial of service.
Use logging instead. TCC has all the facility for that.