Progress -inp startup parameter

K

Krispy

New Member
Hi guys,

I've been writing some code this afternoon and have come across the following error for the first time.

Code: 
Preprocessor expansion buffer overflow. (2939)                           
 
Too many characters appear between curly braces ({}), or the result of a 
{&name} or {1}-type expansion is too large (note that a {&name} reference
can appear within another preprocessor name reference or definition).    
[B]The number of characters that are allowed in an expansion is governed by [/B]
[B]the -inp startup parameter.[/B]

I've checked the start up command and the -inp parameter does not appear to be referenced. Does anyone know how I can find out what the default -inp parameter value is on our system?

When we know the value that is being used, we can think about how we are going to increase it.

Thanks in advance.
Kevin
 
Thanks for the swift response.

I tried the following tip supplied by Joey,
Code: 
MESSAGE SESSION:STARTUP-PARAMETERS VIEW-AS ALERT-BOX
, but there was still no entry for the -inp parameter.

Do you know if this can be increased beyond 4096?, or is that the maximum?
 
me ?


if you're trying to compile-on-the-fly with compile-time &arguments

then there is an approx 3k limit


but tell us more on what it is you're writing ?
 
but there was still no entry for the -inp parameter.
Click to expand...

because you didn't specify it in the command line but neveretheless your session still uses its default value which is 4096.

Do you know if this can be increased beyond 4096?, or is that the maximum?
Click to expand...

Yes, it can be increased, of course, but i don't know its maximum value I have its value 12288.
 
joey.jeremiah said:
me?
Click to expand...

Yes, I managed to dig up an old thread where you helped someone with the -inp parameter. :biggrin:

I was using a generic include file which accepts chunks of code as parameters for different input/update/delete methods. My {&input-code} parameter had obviously exceded the maximum -inp value. I managed to get round the problem my moving my {&input-code} into its own include file. I probably should have tried this first, but I didnt think it would make anuy difference......but I was obviously wrong!! :blush1:

Thanks for the info though - it's good to know I can increase the default value above 4096 if I ever run into a similar problem.
 
Most times when you get the preprocessor expansion buffer overflow error it means you forgot a quote somewhere within a preprocessor statement. So check that first.

The -inp parameter is a client parameter:

You can include a client session startup parameter of -inp.
The default for this parameter is 4096; you can increase this
figure up to 32000. (prior to 8.2A this was 8000).
 
You must log in or register to reply here.
Back
Top