Hi Folks.

Got one for you gurus out there that I've not struck before.

Can anybody tell me what this error means:

[B211] in program ..... : TCL level-push limit exceeded.

I've never seen it before and consequently don't know how to combat it. Any
help would be appreciated.

Regards,

Alan

Hello Alan,

I'll give it a try and someone else will come along and make it right.

I don't know if D3 will still do this or not, but I know AP/Pro
would do this.

At tcl you can push a level by typing ">>" (two right arrows). This
would make a new prompt appear and you would operate just as
though you had just logged on. I forget how you got back up the
levels, maybe with "<<" or with exit or end ??? Cannot remember.

I believe with D3 what might be happening is that you have a program
that executes a program that executes a program that executes a ...
oh well - you get the idea. I think 15 of these executes deep is
all that D3 can handle, but I could be wrong.

Larry Hazel

"Alan Ramsay" <ajramsay (AT) iinet (DOT) net.au> wrote

Goo'day, Alan,

On Mon, 2 Oct 2006 10:00:39 +0800, "Alan Ramsay"
<ajramsay (AT) iinet (DOT) net.au> wrote:

IIRC, R83 (after the EXECUTE verb became avaiilable..) used to have a
maximum of eleven (???) levels that you could push using EXECUTEs....

Is this the same problem?

Regards,

Bruce Nichol
Talon Computer Services
ALBURY NSW Australia

http://www.taloncs.com.au

If it ain't broke, fix it until it is....

Yeah, fair chance I'd say.

There's a series of nested executes in this set of programs and think what
has happened is the user has run them in such a way that this has happened.
I haven't been able to recreate the error myself, but the user tells me he
has been dumped out by it 3 times in the past week.

A restructure of the code may be in order.

"Bruce Nichol" <reverse_ecurb (AT) taloncs (DOT) com.au> wrote

Hi Larry.

I think the execute that executes that executes... might be the issue here.
A restructure of the set of programs might fix it I'm guessing. It doesn't
appear to want to let me manually push using the >> command, so I guess
that's an AP thing.

Thanks for your help.

Alan.


"Homer L. Hazel" <hNoOmerlhANTI (AT) SPAMcox (DOT) net> wrote

Hi
There was/is also a parameter setting that limited the number of levels to a
sensibe number as defined by the system administrator. IFIRC Via went
overboard with 6 levels whereas I thought 2 was more than enough if you ever
wanted to find out what was going on. Bit like the good old days of
assembler set address zero the jump to zero fast but untrackable.
Peter McMurray

"Bruce Nichol" <reverse_ecurb (AT) taloncs (DOT) com.au> wrote

Yes, D3 currently has a maximum of 16 pushed levels. Info about this
is in the current D3 Ref manual in sections like "Levels" and "Level
Pushing", brk-level, esc-level, and others. To see how many levels
deep a process is, use "where L".

To see how many levels deep you are in BASIC and avoid the issue
described, have your code check the value of SYSTEM(16). If it is
already 15 then one more push causes an abort - so don't let that
happen.

If you're at a debug prompt like: ********
You can end the current level by typing END.
If you're at TCL: ::::::::
You can pop back to the next level by simply pressing Enter, or by
typing END.

HTH

"Alan Ramsay" wrote: