What are the Ffenics Network Timeouts for?

This forum is Read Only . If you feel a thread should be added to the FAQ please contact a moderator

What are the Ffenics Network Timeouts for?

Postby Pete Tabord » Wed Sep 12, 2007 10:41 am

Ffenics has different locking and file handling on a network than the DataEase technology that it is based on.

When multiple users are accessing the same files, obviously sometimes a resource is in use by another user or even by the operating system, quite apart from when another Ffenics user explicitly locks the data. Ffenics implements a system of multiple retries and time-outs to deal with this, along with a number of other precautions.

The defaults for the time-outs are usually satisfactory, but networks vary widely in performance, especially wide area networks.

The two I/O time-outs therefore, are settable in PRISM.INI or via the Database Engine preferences screen. The appropriate time-out should be increased depending on the type of error reported - file open, file read etc. They are:

Open/Close on the dialog, Major Timeout in the ini file - default 2 seconds

This is the retry delay applied when an error occurs while opening a file (or very rarely, when closing one).

Read/Lock on the dialog, Minor Timeout in the ini file - default 1 tenth of a second

This is the retry delay applied when an error occurs:
Reading a file
Writing a file
Placing a control file lock
Getting conflicting user name
Locking one of a sequence (or set) of locks.

The retry time-outs when an actual lock placed by another user of Ffenics is encountered are also configurable:

Initial Delay on the dialog, ITimeout in the file - default 5 seconds.

Subsequent in the dialog, STimeout in the file - default 0 seconds.

'Initial Delay' is used when the design of the app is such that delays waiting for other users are common and you don't wish Ffenics to go into its 'waiting for resource' message routine.

'Subsequent' is increased to reduce network traffic while waiting for a resource to become free. (there is an inbuilt slight delay which is not configurable to avoid flooding the network totally).

All these are deliberately settable by workstation so that the configuration can be tuned to cater for, say a single machine being used from a remote site with a slower connection.

Peter J. Tabord
Head of Development
Database Software Ltd.
Pete Tabord
Posts: 1881
Joined: Fri Sep 07, 2007 12:48 pm
Location: Caernarfon, Gwynedd, UK
Has thanked: 0 time
Been thanked: 3 times

Return to Ffenics FAQ

Who is online

Users browsing this forum: No registered users and 1 guest