Redimension Error

[Rick Weiser]

Hi all,

I am porting the newest version of DB to QM and I am getting the following when I try to run any program:

:DBI.RUN.LAST

0000024B: Redimensioning common to larger size in DBI.RUN.LAST

My $basic.options is:

MODE UV.LOCATE

MODE OPTIONAL.FINAL.END

MODE FOR.STORE.BEFORE.TEST

DEBUGGING

CATALOG LOCAL

MODE OPTIONAL.FINAL.END

MODE PICK.ENTER

MODE PICK.ERRMSG

MODE PICK.JUMP.RANGE

MODE PICK.READ

MODE UNASSIGNED.COMMON

MODE PICK.SUBSTR

MODE NOCASE.STRINGS

MODE PICK.SELECT

MODE PRCLOSE.DEFAULT.0

MODE COMPATIBLE.APPEND

MODE STDFIL

MODE KEEP.OLD.OBJECT

MODE PICK.MATRIX

MODE IMPLIED.STOP 

Any ideas?

Thanks,

Rick

[Rick Weiser]

Never mind.  I restarted the QM service and all is fine now.

[Rick Weiser]

Sorry, spoke too fast.  I am getting this again.  This time the a restart of QMSYS does not solve the problem.

What does this mean??

Rick

[Brian Speirs]

Here is a bit of a guess:

The program has a named common. This common is used by other programs. You have recently changed the definition of the common (added new variables to it) but have not recompiled all the programs that use this named common. DBI.RUN.LAST has a larger version of the common than the program calling DBI.RUN.LAST hence the run-time error.

So, try SELECTing all the programs that use that named (or unnamed) common and recompiling them.

HTH,

Brian

[Martin Phillips]

Hi Rick,

Brian’s interpretation of the cause sounds correct to me. Please confirm that you have found the problem and fixed it.

 

 

Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton NN4 6DB, England
+44 (0)1604-709200

--
You received this message because you are subscribed to the Google Groups "OpenQM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openqm+un...@googlegroups.com.
To post to this group, send an email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openqm?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rick Weiser]

Yes, recompiling fixed the issue.  This was the scenario.  I compiled and cataloged the programs on v3.0.7/Windows.  Then moved the account to another server which is 2.12.7/Windows and globally cataloged the programs (did not recompile).

So, my next question.  Is the object code backward compatible?

Rick

[Martin Phillips]

Hi Rick,

 

Object code should be backward compatible so long as you do not use features that are not in the older release. I do not know of anything that should result in the error that you saw unless there was a module somewhere that you did not recompile/catalogue.

 

If the problem occurs again, it would be good to investigate a bit more carefully.

 

 

Martin

[Rick Weiser]

Martin,

I will be doing this procedure again next week.  I will let you know.

Rick

[Martin Phillips]

Hi again Rick,

 

A suggestion that might explain things…..

 

Is it possible that you have a LOGIN paragraph that is executing something from the old release of DB, creating a named common. You then go on to install the new version with a larger common and, on starting this new version, you get the size mismatch error?

 

If this sounds like it might be this case, you should be able simply to do

   DELETE.COMMON ALL

from the QM command prompt to get rid of the old common.

[Rick Weiser]

Martin,

No.  We do have named commons but they are initialized in the main programs, not a login PA.

Rick