Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
acocobol error 39
- Thread starter mdcsys
- Start date
I think we'll need more detailed information about this.
For example, what do you exactly mean by this: "There is
nothing wrong with the files since I can get back into
the program immediately".
What statement produces this error?
Do you mean that the "error" is really the FILE STATUS CODE?
Do you have more than one program accessing the files in error?
Is there a reproduceable pattern to obtaining the error?
__________________________________________
Try forum1391 for lively discussions
For example, what do you exactly mean by this: "There is
nothing wrong with the files since I can get back into
the program immediately".
What statement produces this error?
Do you mean that the "error" is really the FILE STATUS CODE?
Do you have more than one program accessing the files in error?
Is there a reproduceable pattern to obtaining the error?
__________________________________________
Try forum1391 for lively discussions
- Thread starter
- #3
Yes I mean file status 39. I know that file status "39" occurs when the the program FD does not match the file
record structure. This is not the case in this situation.
You can run the program, get this status, and a minute later do the same thing and all is fine. This occurs at random locations in the program. I should also mention that
this is a multiuser system and others users may be accessing the files. I'm thinking that this may be a system
bug in file locking etc. Perhaps related to XP SPII?
mdcsys
record structure. This is not the case in this situation.
You can run the program, get this status, and a minute later do the same thing and all is fine. This occurs at random locations in the program. I should also mention that
this is a multiuser system and others users may be accessing the files. I'm thinking that this may be a system
bug in file locking etc. Perhaps related to XP SPII?
mdcsys
I am willing to "bet" that the File Status = 39 *DOES* mean
"the program FD (and other "fixed file attributes") does not match the file record structure."
My "best guess" is that given the
"multiuser system"
nature of the sytem, that while one user is "updating" (possibly even reading) the file that the run-time is doing someting to one (or more) fixed file attributes of the physical file - which causes the FS=39.
If you are currently "under support" for this COBOL system, then I certainly think this is something that you should be dealing with the vendor about.
If you are NOT currently "under support" - then this is the type of problem that causes most customers to think that paying for support is "worth it".
Bill Klein
"the program FD (and other "fixed file attributes") does not match the file record structure."
My "best guess" is that given the
"multiuser system"
nature of the sytem, that while one user is "updating" (possibly even reading) the file that the run-time is doing someting to one (or more) fixed file attributes of the physical file - which causes the FS=39.
If you are currently "under support" for this COBOL system, then I certainly think this is something that you should be dealing with the vendor about.
If you are NOT currently "under support" - then this is the type of problem that causes most customers to think that paying for support is "worth it".
Bill Klein
- Status
Similar threads
- Locked
- Question
- Locked
- Question