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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

btrieve error 1

Status
Not open for further replies.

smeyer

IS-IT--Management
Nov 15, 2002
52
US
ile error 025 on file DATAFILS/PSDATA/PSMRQF.DAT

Operating system error.

Termination occurred in EDCRPC

Prev COBOL I/O operation: READ (random) WITH NO LOCK
Prev rec buffer contents: 000E4 YC 1
Prev Btrieve ops/stats: 5/3016 205/84 205/84 205/84 205/84

How do I read this and what does it mean?
Thanks
 
I'm making the assumption that the 025 error is a Btrieve return code, if so:

25: The application cannot create the specified file.

The MicroKernel can return this status code if an application attempts to create a data file, but the disk directory or the disk itself is full. If the application is creating a file over an existing file, the MicroKernel returns this status code when the existing file is open or when the operating system prevents the operation for some other reason (for example, because the file is flagged transactional in NetWare).
Sometimes pre-v6.0 MicroKernels can return this status code if the HOLD parameter in NET.CFG or SHELL.CFG is set to ON and the application attempts to create a data file on a network drive. (The HOLD parameter is set to OFF by default.) Creating the file on a local drive is successful regardless of the value of the HOLD parameter.
 
Could this be an issue with the record lock wait time. We had the wait time set at 15 seconds, I changed it to 30 seconds last night. I think the open file you mentioned may be a problem since my other errors tend to be could not open file - already opened or could not close file - already closed. We must be having some access issues that I am just starting to track down.
Thanks
 
If I am reading the message correctly, this is probably the key line for information:

5/3016 205/84 205/84 205/84 205/84

This indicates that there were 4 status 84s (record locked) on 205 calls (op code 5 - Get Equal - with a Lock Bias of 200 - Single No Wait [Attempts to lock a single record and returns control if the record is already locked]) and one status 3016 (The MicroKernel router encountered an internal error) on a normal Op 5 (Get Equal).

The 3016 should be logged. Check the Pervasive Event Log (PVSW.LOG) for more information

 
I saw the 3016 in the log but didn't know how to interpret the 205 calls, is there somewhere that explains this?

Could you explain the single no wait and could this be caused by a short wait lock timeout?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top