Microframe Corporation 3007 Series Guide de l'utilisateur télécharger pdf (Page 94)

1-86

Status Codes

 Tried to update or delete a record locked by another

application.

The application can use either of the following recovery

methods:

 Retry the operation until it is successful. This can be the

simplest and quickest solution for a network with light to

moderate use.

Note Applications should limit the number of retry attempts

when status 84 is received inside a concurrent transaction.

Otherwise, the application might enter a deadlock situation with

another transaction. If status 84 is still received after a few retries,

abort the transaction and then attempt the transaction again.

 Use the wait option (+100/+300) instead of the no-wait

option (in versions that support the wait option).

85: The file is locked

The MicroKernel returns this status code in one of the following

situations:

 While one user has a file locked in an exclusive transaction,

another user attempts to lock all or part of that file.

 The workstation MicroKernel has a file open, and a client

machine that has the Requester loaded tries to open the same file

via the server MicroKernel. The server MicroKernel cannot

open the file because it cannot obtain exclusive access. The client

machine that has the Requester loaded receives this status code.

 When opened by a MicroKernel, two data files have the same

filename but different extensions (for example, INVOICE.HDR

and INVOICE.DET). One file is open and in Continuous

Operation mode, causing the MicroKernel to generate a delta

file (for example, INVOICE.^^^). The MicroKernel returns this

status code when you attempt to open the second file. For this

reason, we recommend naming your files with completely

different names, not just reusing the same name with different

extensions.

1 2 ... 89 90 91 92 93 94 95 96 97 98 99 ... 251 252

Pas de commentaire

Microframe Corporation 3007 Series Guide de l'utilisateur Page 94