How do I get around this error? Are what are the max variables? It seems to be happening when a user executes a posting process on more than 40 records, but not less. Do I need to do some reprogramming and reuse variable names? We make extensive use of equates.

'CATALYST' Line 1. B114 Maximum number of variables exceeded

Thanks in advance

Lisa B Porch

UtiliCorp

First, equates are not variables. Perhaps you are running into an infinite loop or something. Can you describe in more detail how your process works?

Try making some functions and subroutines expendable and removing any {field} references or "FIELD" in XLATE. All these can add to varibles in use. Also, you might want to reuse some variables more often, if possible. If you are dynamically creating a dimensioned array, each element is a variable.

Equates are not variables so they should not cause this problem

[email protected]

Sprezzatura Group

Are you using any DIM statements? This is the curse of the cat people in terms of variable usage. A DIM VARNAME(250,4) reserves 1000 variable entries. You get +- 1700 variables in AREV. Any curly-brace dictionary evaluate {DICT_ENTRY} in your program will also suck up a variable plus the variables used in the call, if it is a symbolic. If you pass a dimensioned array into CATALYST, it will blow up (I think). It wants to use dynamic arrays.

Don Miller

C3 Inc.

Thanks gentleman. I am working on a new-to-me system with a lot of MFSs and subroutine calls. I was taught to use expendable. This system only had about 4 expendable subroutines.

Haven't had a reoccurance since I changed more than 100 subroutines.

Lisa

Hi Lisa,

To isolate the cause, try making the programs involved "expendable" subroutines. You may be running out of space in the program stack.

View this thread on the forum...