Error using TCC: "Label not found"

May 5, 2010
9
0
#1
We're starting using Mule ESB at work and when I try to start it within TCC, I get a "Label not found" error. It works well using the standard Windows command prompt. In fact the error I get is "Label non trouvé" because my system is in french, but I guess the error would be "Label not found" on an english system.

The error is very easy to reproduce:

1. Download MuleESB : http://dist.codehaus.org/mule/distributions/mule-standalone-3.1.1.zip

2. Unzip it to C:\mule-standalone-3.1.1

3. In TCC, go to C:\mule-standalone-3.1.1\bin and run "mule.bat"

4. Error:

Code:
TCC: C:\mule-standalone-3.1.1\bin\mule.bat [153]  Label non trouvé ":console"
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,570
46
Albuquerque, NM
prospero.unm.edu
#2
The issue isn't where the error message suggests. What I think is going on here is:

In line 73, variable COMMAND is set to value ":console".

Line 108 is call :%COMMAND%
which works out to call ::console

No label matches that string -- no label can match that string -- so you get an error message. How it fails to malfunction in CMD.EXE I don't know....

I suspect that removing the colon from line 73 would be a short-term solution. But it would probably be better to rewrite the whole mess as a .BTM.
 
Aug 9, 2009
133
0
#4
AND Why would anyone want to download a 65mb file just to find the bat
file is C.R.A.P
you could just post the offending batch file.. Like Charles said
re-write it in a real batch language


> -----Original Message-----
> From: electrotype [mailto:]
> Sent: Wednesday, 16 March 2011 3:23 a.m.
> Subject: [Support-t-2677] Error using TCC: "Label not found"
>
>
> We're starting using Mule ESB at work and when I try to start
> it within TCC, I get a "Label not found" error. It works well
> using the standard Windows command prompt. In fact the error
> I get is "Label non trouvé" error because my system is in
> french, but I guess the error would be "Label not found" on
> an english system.
>
> The error is very easy to reproduce:
>
> 1. Download MuleESB :
> http://dist.codehaus.org/mule/distributions/mule-standalone-3.1.1.zip
>
> 2. Unzip it to C:\mule-standalone-3.1.1
>
> 3. In TCC, go to C:\mule-standalone-3.1.1\bin and run "mule.bat"
>
> 4. Error:
>
>
> Code:
> ---------
> TCC: C:\mule-standalone-3.1.1\bin\mule.bat [153] Label non
> trouvé ":console"
> ---------
>
>
>
 
#6
---- Original Message ----
From: Kachupp
To: [email protected]
Sent: Tuesday, 2011. March 15. 12:05
Subject: RE: [Support-t-2677] Error using TCC: "Label not found"

| AND Why would anyone want to download a 65mb file just to find the bat
| file is C.R.A.P
| you could just post the offending batch file.. Like Charles said
| re-write it in a real batch language

65 millibit file? That's really tiny! While I agree that posting just the batch file would be sufficient for the experts among us in this forum, there are definite benefits to making the whole failing project available for examination. And as to the original .BAT file - not all customers of the vendor are sophisticated enough to have obtained the JP Software, Inc. product, so they must sell to the lowest common denominator - Microsoft Windows' command processor, which tolerates different syntax errors than TCC. If your development tool processes invalid code the way you want it done, you will not detect the errors it contains. For example, it tests for "windows nt" command processor, but if it finds something else, it uses WinNT syntax to quit (goto :EOF - where the :EOF label is implied only, a feature in CMD.EXE but not in COMMAND.COM). If you have only WinNT platforms on which to test, you'll never detect the wrong syntax.

Please be more respectful of other people's code, even if it were truly appallingly poor quality. If it works in the environment for which it is intended it is OK!
--
Steve
 
Aug 9, 2009
133
0
#7
> ---- Original Message ----
> From: Kachupp
> To: [email protected]
> Sent: Tuesday, 2011. March 15. 12:05
> Subject: RE: [Support-t-2677] Error using TCC: "Label not found"
>
> | AND Why would anyone want to download a 65mb file just to
> find the bat
> | file is C.R.A.P
> | you could just post the offending batch file.. Like Charles said
> | re-write it in a real batch language
>
> Please be more respectful of other people's code, even if it
> were truly appallingly poor quality. If it works in the
> environment for which it is intended it is OK!
> --
> Steve
I don't think its ok! Rexx gets, everyone [even seasoned 4nt/tcc/tc]
users "batch's" not working as intended why?
When I said dl 65MegaByte (to) I'm not interested. 65k I'd look at!
"send the offending batch"!~

Respects
Kach