Home > Archive > Cobol > May 2006 > Re: runtime message
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: runtime message
|
|
| Bob Iles 2006-05-23, 7:55 am |
| if this is RMcobol then the 39,xx indicates that
your definition of the file in the select statement
does not match the file you are opening.
I have normally found this to be a mismatch (programming
error) or a corrupted file. I have also generated this
error by having a file opened in one mode (as an indexed
file) and then opening the file again as a
binary-sequential.
hope this helps.
Bob.
Jerome wrote:
> Hello,
>
> Please, what is a "cobol I/O error 39,52 on ..." error ?
>
> I've not the description of this message in my "User's guide".
>
> thank you.
>
> Best regards,
>
> Jerome
| |
| Jerome 2006-05-23, 6:55 pm |
| Bob Iles a écrit :
> if this is RMcobol then the 39,xx indicates that
> your definition of the file in the select statement
> does not match the file you are opening.
>
Yes it is.
> I have normally found this to be a mismatch (programming
> error) or a corrupted file. I have also generated this
> error by having a file opened in one mode (as an indexed
> file) and then opening the file again as a
> binary-sequential.
>
It seems to be an error on duplicate key. Thank you for your help
[color=darkred]
| |
| Bob Iles 2006-05-23, 6:55 pm |
| Jerome wrote:[color=darkred]
> Bob Iles a écrit :
>
> Yes it is.
>
> It seems to be an error on duplicate key. Thank you for your help
>
Are you saying that the definition allows a duplicate key
but the created file does not? or the opposite?
I'm just curious, thanks.
bob.
| |
| Donald Tees 2006-05-23, 6:55 pm |
| Jerome wrote:[color=darkred]
> Bob Iles a écrit :
>
> Yes it is.
>
> It seems to be an error on duplicate key. Thank you for your help
>
If that is indeed what it is, then it should be regarded as a program
bug. In other words, you could only get it if someone coded a read
statement on an Isam file with no "invalid key" statement. A definite no-no.
Donald
| |
| Bob Iles 2006-05-23, 6:55 pm |
| Donald Tees wrote:
> Jerome wrote:
>
>
>
> If that is indeed what it is, then it should be regarded as a program
> bug. In other words, you could only get it if someone coded a read
> statement on an Isam file with no "invalid key" statement. A definite no-no.
>
> Donald
Normally the RMCOBOL, if that is what we are talking about, a
return code of 22,00 occurs with a duplicate key event, whereas
a 39,xx error in RMCOBOL) will only occurs from a mismatch of of file
types or a terribly corrupted index file.
bob.
|
|
|
|
|