Well not too long ago Bryan Feddish was struggling with this error in OpenInsight and now we are experiencing the same problem in an AREV app.

The strange thing is that it seems somewhat random. We have 7 subroutines with a shared labeled common variable list - no symbolics at all. These procedures have run fine for a long time and then one day various machines would get this message. Sometimes you can reset a machine and it goes away, other times it will persist no matter what is done.

This is so sporatic but it seems to be getting nastier. What else could be causing this problem with multiple machines?

Thanks,

dbakke@srpcs.com

SRP Computer Solutions

The only time I have ever seen this error come up is when there are multiple programs using the same labelled common area, but they don't all have the same number of variables. The labelled common is initialized per session by the FIRST program that uses it. My guess is that in the cases where you are getting the error, a program compiled with a smaller declaration is being compiled first.

What you need to do is to check all programs that use that labelled common. If the declaration is in an include file, and the declaration was changed at some point, the programs will be corrected if you recompile them.

Yep,

Don is right. One of your programs has defined the labelled common

with less variables than the others. If it gets run first, you will

get the problem. If one of the other programs is run first, you won't. (That's why it seems random).

Warren Kinny

EXODUS Systems

Victor,

This is my point, there are only seven programs with this labeled common and it is not in an include file. I have copied every source code into a common text file and lined their labeled common statements on top of each other and there is not a single character difference among them.

Furthermore, this had been working fine for some time (at least a year) and then problems just began to surface. Could RAM or NIC problems cause this?

One last comment, this error message would also come up when the very first subroutine with this common label was invoked. So it was impossible for this to be a situation where one subroutine was called first and then a subsequent one with less variables was called.

I admit it, very strange…thanks for your ideas.

dbakke@srpcs.com

SRP Computer Solutions

Perhaps someone has written a subroutine using (inadvertantly) the same label for nother labelled common???

J

Two things to consider - 1) This is one of those accounts where we (specifically "I") am the only one who does any development. Everyone else is just so unaware of what's going on. 2) I've written a program that searches all available source code for whatever word/phrase I've requested. I looked for the name of the labeled common, QUEUE, and all I found were the seven programs that I knew already should have it.

dbakke@srpcs.com

SRP Computer Solutions

Way back in the dim resources of my memory I seem to recall there being an issue with labelled commons in an MFS during the Open or Init call.

akaplan@sprezzatura.com

Sprezzatura, Inc.

View this thread on the forum...