Anyone ever gotten:

:error code: 114, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 10)


i'm trying to read about 12,000 records from a flat file and load them into an oracle table.

i found a kb article and tried everything it said (modify the startjobqueue file, set-up a cobconfig file etc). but to no avail.

Sounds like a problem with transfer of control. Did you try a debug session to see where it bombs ?

seems to be a limitation on space or memory someplace.
i can run it up to about 9000 records added, anything above that and I get the error message.

Any chance there's a hard limit set in an array definition somewhere? I remember hitting that kind of thing in years past -

Other option is to split you file and do 2 loads

Yes I have seen this for sure.
I can't quite remember when or why. But I believe it had to do with trying to read the Next record in an index when the first hadn't been found yet. It was a silly error. If I remember I'll post it.

seems like u r using occurs class , there is a restriction on occurs class , we can not define the restriction by number of occurs but its dependent on memory

I am not sure if my assumption is correct, but I'm thinking your transaction maybe overflowing. Try to find your 910-AUDIT-BEGIN and 920-AUDIT-END, it is maybe outside the 820-STORE-<database> loop.

what if......

you made a "SYSTEM" call to importdb??? :rau:

Any resolution on this?

We're finishing our setup on LSF 9 / Apps 9 and will go live soon ... but we keep getting "Error 114 ... Signal 11" errors on some AP screens. The solution in the KnowledgeBase, at least for the old 8 environment, was to do a number of changes to config files. This I've done -- on the Production server, but not the Test server. Yet the error persists in both our environments.

AAAaaaargh! :banghead:

Well, I finally got going (after a few choice words from the boss about procrastination :beat: ) and contacted Lawson. They pointed out that the COBOL compiler was a little, er, out of date. Ooops. :bye: I was told that we needed to apply a Micro Focus Server Express FixPack. So the first server is now busy recompiling every single program in every product line in the whole blinking box which will take "only" 10 hours or so. :disco: Oh well.

If the update doesn't fix it, I'll keep people posted on the continuing saga. <_<

Applying Server Express FixPack 63 (UNIX) fixed the error in one program.

Occasional errors in other programs were eliminated by adjusting rpt.cfg and commenting out these lines that were installed by the Lawson installers:
# RUNTIME_XML_ENABLE ON
# RUNTIME_XML ON
# RUNTIME_CSV ON
# RUNTIME_LOC_PROP OFF

Those settings are only supposed to be needed for Lawson's own debugging purposes. If they need to be turned back on, they can be turned on on a system code level, or even program by program.

In my experience with LSF, it is best to adjust the parameters you mentioned on an app by app basis and not at the system code or pl level. Setting them at the productline or system code can cause the Error Code 114 to re-appear in various apps.

I'm not sure who said that these settings are only used for debugging by Lawson, but that's not entirely true. They are required settings for many apps to broadcast correctly to LBI.

Again, in my experience, it's best to comment out these variables from your rpt.cfg, leave them alone in any Lawson delivered app-specific.cfg files, and then set them at the application level on an as-needed basis.

..and that's my $0.02.