error message text not found

 4 Replies
 0 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
BrianM
Advanced Member Send Private Message
Posts: 41
Advanced Member
I have a user who sent me an error message I've never seen before.  They ran a PO220 and got the following examine log message.  Does anyone know what this means?  Thanks in advance for your help! Program Messages:         ** Creating .prt and .dtl files         Processing PO220 - PO Status Report         Execution error : file '/lawson/law/prod/obj/PO220.gnt'         error code: 114, pc=0, call=1, seg=0         114         error message text not found (Signal 11)         Elapsed Time . . . . . : 00:10:28 ERROR:   Stopped on Exit 255.  
BTM
Woozy
Veteran Member Send Private Message
Posts: 709
Veteran Member
This looks like the message that appears when the code is trying to call an error code that doesn't exist in msgmnt. Perhaps the program needs to be recompiled, or maybe a patch or code change was incompletely promoted (maybe the code was promoted, but not the metadata)? Try recompiling first. If a regular recompile doesn't work, you could try compiling the PO220 with the "-T" parameter, which will then cause the log to show every section the code hits - so one of the last sections displayed would be the "problem" area. However, this will create a very large log, so you will want to limit the data selection as much as you can. We don't use PO220, so I'm not sure how reasonable that is. Good Luck! Kelly
Kelly Meade
J. R. Simplot Company
Boise, ID
BrianM
Advanced Member Send Private Message
Posts: 41
Advanced Member
Thanks Woozy, we will give that a try.
BTM
John Henley
Send Private Message
Posts: 3351
Brian, that error typically indicates a memory overrun. I've seen it in two cases, first when a program internally overruns an array size indicating a logic error in the code. In that case you should submit a case to Lawson/Infor and work with them to duplicate it. Second is when a program generates a work file that is just huge and the compiler/COBOL runtime can't handle it. I'm guessing that your user ran PO220 for ALL PO's in the entire company, used an attribute list that was really large or something like that. Have them send you a screen shot of the parameters they used on PO220.
Thanks for using the LawsonGuru.com forums!
John
BrianM
Advanced Member Send Private Message
Posts: 41
Advanced Member
Thank you John
BTM