Also dropping the /N will return just the bare function names in the specified library, without including the library name prefix, if that's what you are looking for. library utils.library$*

Try this: library /n utils.library$*

When you start a command line with quotes, both CMD and TCC interpret that string as a filename to be executed. To see what is happening try executing this from the command line in CMD and TCC. "c:\FileWhichDoesNotExist.bat TestParm" When you run cmd.exe /c "..." then the quotes are...

I definitely did not get a dialog from Windows. What exactly does "continuing with the next command" mean in this context. 1. A .btm script was started from Windows Task Scheduler with a command line equivalent to this: "C:\Program Files\JPSoft\TCMD36\tcc.exe" /k C:\Batfile\BackupDaily.btm /B...

Also, I figured out that two MAPEXE commands were probably executing because I had inadvertently put two SETLOCAL commands in my script. What seems odd to me is that this would happen, because even though my script appears to have aborted running before reaching the end, it appears that TCC...

I still had the problem TCC session up from this morning. When I ran the tasklist command there were no .DLLs from anywhere other than C:\Windows and the TCC installation directory. So I started up a fresh session and ran the same tasklist command and compared the results to the problem...

More info on my issue where my BTM script fails to complete, and mid-script the same BTM script is re-executed from the top, but without the expected command line parameters. I see that this file "C:\ProgramData\JP Software\Take Command 36\TCC.exception.log" contains the following entries...

Thanks for the explanation. That make sense. It wasn't a big issue for me...it just caught me by surprise when I was trying to trace through what was being executed by following the commandlog and some commands I expected to see weren't there.

Thanks for the explanation Rex. I know MAPEXE is not the cause of my issue, and I have no concern with MAPEXE in the logs. In fact, it might prove to be useful in figuring out the cause of my intermittent script failures.

Executing this BTM @echo off setlocal log /E /w "E:\Floppy\TCErrorLog.txt" log /A /w "E:\Floppy\TCLogAll(Output).txt" log /w "E:\Floppy\TCCommandLog(AftVarExp).txt" Echo Good Morning Echox Good Afternoon echos Good night echo ! :END endlocal log OFF log /A OFF log /E OFF results in a...

Thank you Charles! I actually just discovered that literally 30 seconds ago, testing a different issue with Logs. I'll post that separately. So looking at my original issue at the top of this thread, the two executions of MAPEXE might indicate that I was encountering two different ENDLOCAL...

Well that's interesting. I'm definitely not trying to execute a PATH command. I'm going to assume two things (1) There are no other situations where MAPEXE would be run with (with those arguments) and (2) MAPEXE wouldn't be run twice in a row as shown in the log unless I somehow triggered a...

I'm in the middle of trying to figure out a thorny, sporadic issue (more on that later) so I turned on Command Logging. There's a point in the process where a running BTM script is re-executed from the start (could be self-inflicted). I noticed in command log that when this happens, there are...

Do you have ANSI enabled in TCC Options

No more artifacts on the text in TCMD/TCC version 36.52.81. Thank you Rex!