Cobol run-tme send 0047 error code 2

[Dharispa]

Please, help anybody!
Client-Server (MRP-II System) Application while MRP-calculation throws away with error code 0047 that is explained as "Index table overflow" in the specific file FP2PLAN.dat with FP2PLAN.idx.

Does anybody know about an opportunity to resolve this problem without any cobol compiler. We have no such one and are ready working with these files only. I have only a REBUILD utility and try use it with /t:mf4 switch to increase duplicate key room, but with no success. Is there another way or recourses to help me?

Cobol run-time version 4.0.38.
Environment: Windows NT, PC

Thank you.

...to accelerate the process as work of the plant is paralyzed.

 

[gregsimpson]

I would suggest the following as a starting point.

Use the rebuild with /f as below.

rebuild FP2PLAN.dat /f:c63d5

Hopefully this will give you some further information.

Also try the following

rebuild FP2PLAN.dat /n to get some further information.

If you get desperate and your convinced that /t:mf4 is correct then try something along the following lines

rebuild FP2PLAN.dat,newfile.dat /s:mf4 /t:mf4


There are other options instead of mf4. These being btrv,c-isam,lii,mf. Are you sure your file is mf4(IDXFORMAT"4" format.

 

[sambadude]

hi there


if you still haveing the problem, try the following.

1. take a backup of your files

2. remove those files from system.

3. let the system create those files again.

4. get your file.dat from back and restore it (only this file)

try rebuild /i /v (Again)

hope it works for you.

Latif

 

[Dharispa]

Thanks everybody!

I try rebuild this file with some different switches, but with no success. Later, I made a new one (empty with no data) with the appropriate index file generated by system and got the same result (error code 0047 on FP2PLN.dat).

So, I wonder why PRODSTAR point on this file while the reason is somewhere else?

But this experience help us to find another way. And we simply replace this file and some others else, those are connected with it by Application links, from the Backup a day before incident.
From your, Latif, message I understand it's a usual practice. We (our team) come to it independently through 2 days of downtime of System.

Thanks to modesty of Cobol (I guess it's a one reason of it) PRODSTAR begin run correctly.

As for knowing of file format (is it mf:4), I really have no information how to check it. All my acts "were in the dark room in searching of black cat".

Thank you for your participation.
If you give another information about checking of file format and any information of files recovery, I will be appreciate to you. I mean site or manual for Cobol users like that have no ideas about this Language, but who come into collision with it from time to time.

Igor,
this is may name.

 

[sambadude]

do you need some cobol help files,

latif

 

[Dharispa]

Tehre is a necessity of short help information about Cobol usage itself.
I mean some utilities, definition of Cobol Run-time version. Maybe there is an opportunity of Cobol compiler or smth else.

I have a very limited knowledge about this Language.

Igor