Explore topic-wise InterviewSolutions in .

In NETWARE Btrieve v6.10, the Maximum Page Size parameter (/P:) is no longer required. NetWare Btrieve can now OPEN any Btrieve file with any page size. NetWare Btrieve v6.10 will not return status 24 from the Open operation and will ignore any value given for the /P: startup parameter.

Using NetWare Btrieve (NLM) v5.15 and Brequest v6.00b, the following SYNTAX generates a status 12 (File Not Found) on a Btrieve Open operation: servervoldirsubdirfile

To avoid this status code, either:

Use the PATCHED version of Brequest v5.16.
Add a colon (:) after the volume NAME when using Brequest v6.00b. For Brequest 6.00b the syntax would be: 
servervol:dirsub-dirfile

In NetWare Btrieve v6.10, the Maximum Page Size parameter (/P:) is no longer required. NetWare Btrieve can now open any Btrieve file with any page size. NetWare Btrieve v6.10 will not return status 24 from the Open operation and will ignore any value given for the /P: startup parameter.

Using NetWare Btrieve (NLM) v5.15 and Brequest v6.00b, the following syntax generates a status 12 (File Not Found) on a Btrieve Open operation: servervoldirsubdirfile

To avoid this status code, either:

Use the patched version of Brequest v5.16.
Add a colon (:) after the volume name when using Brequest v6.00b. For Brequest 6.00b the syntax would be: 
servervol:dirsub-dirfile

The information in the MANUAL is INCORRECT. you may only PLACE one BUTIL COMMAND in the command file.

The information in the manual is incorrect. you may only place one BUTIL command in the command file.

The NetWare SBACKUP utility uses both NetWare SQL v3.00 and NetWare Btrieve v6.00. BASICALLY, a status 88 will occur if there is anything WRONG with the Btrieve FILES. In this case, a file that was associated with the Named Database was not in the directory that the utility was TRYING to backup.

This status will also be returned if the files selected for backup were already in Continuous Operations. The SBACKUP utility will itself do a Continuous Operations on all the files associated with the Named Database. Thus, the utility will not be able to perform the backup.

The simple SOLUTION is to ensure that all files are in the proper location specified in the Named Database. The other solution is to ensure that the files are not in Continuous Operations when using the SBACKUP utility.

The NetWare SBACKUP utility uses both NetWare SQL v3.00 and NetWare Btrieve v6.00. Basically, a status 88 will occur if there is anything wrong with the Btrieve files. In this case, a file that was associated with the Named Database was not in the directory that the utility was trying to backup.

This status will also be returned if the files selected for backup were already in Continuous Operations. The SBACKUP utility will itself do a Continuous Operations on all the files associated with the Named Database. Thus, the utility will not be able to perform the backup.

The simple solution is to ensure that all files are in the proper location specified in the Named Database. The other solution is to ensure that the files are not in Continuous Operations when using the SBACKUP utility.

This error is similar to a Btrieve STATUS 2 (I/O Error). Btrieve v5.x returns status 2 when you attempt to use it to access Btrieve files stored in v6.x format. Microsoft Access returns "Disk or Network Error" under the same circumstances. When using Microsoft Access to IMPORT Btrieve files, either RUN BTRIEVE.NLM v6.x with Brequest v6.x and WBTRCALL.DLL, or make sure all files accessed with the client WBTRCALL.DLL are stored in v5.x format.

This error is similar to a Btrieve status 2 (I/O Error). Btrieve v5.x returns status 2 when you attempt to use it to access Btrieve files stored in v6.x format. Microsoft Access returns "Disk or Network Error" under the same circumstances. When using Microsoft Access to IMPORT Btrieve files, either run BTRIEVE.NLM v6.x with Brequest v6.x and WBTRCALL.DLL, or make sure all files accessed with the client WBTRCALL.DLL are stored in v5.x format.

Q+E SOFTWARE (formally PIONEER Software) has a PRODUCT called ODBC Pack 1.0. This product currently includes 11 drivers for VARIOUS database engines, including Btrieve. Q+E technical support SAID that the Btrieve file must be in NetWare SQL format. In other words, it requires .DDF files. The product also includes a utility to build the .DDF files if you do not have them.

Q+E Software (formally Pioneer Software) has a product called ODBC Pack 1.0. This product currently includes 11 drivers for various database engines, including Btrieve. Q+E technical support said that the Btrieve file must be in NetWare SQL format. In other words, it requires .DDF files. The product also includes a utility to build the .DDF files if you do not have them.

If your files are STILL in NetWare BTRIEVE v5.x FORMAT, you can load Btrieve v6.x with the -d parameter, forcing new files to be generated in 5.x format. OTHERWISE, the only way to switch back to Btrieve v5.x is to save the contents of your v6.x format file, then generate a v5.x CLONE and load the data into the v5.x file.

If your files are still in NetWare Btrieve v5.x format, you can load Btrieve v6.x with the -d parameter, forcing new files to be generated in 5.x format. Otherwise, the only way to switch back to Btrieve v5.x is to save the contents of your v6.x format file, then generate a v5.x clone and load the data into the v5.x file.

This message results from improper installation of the Btrieve NLM. To install the NLM properly, obtain BTR61.EXE and perform the following ten steps:

• Create a temporary sub-directory (for EXAMPLE, TEMPDIR).
• COPY BTR61.EXE to TEMPDIR and type BTR61.EXE -d. (This step creates two subdirectories, SYSTEM and PUBLIC and copies appropriate files into each.)
• Back up all files on the server where Btrieve will be installed.
• Copy the files from TEMPDIRSYSTEM into SYSTEM on the server.
• Copy all the files from TEMPDIR PUBLIC to PUBLIC on the server.
• At the server console prompt, type "BSTOP" to unload the EXISTING VERSIONS of BTRIEVE.NLM and BSPXCOM.NLM.
• At the server console prompt, type "UNLOAD CLIB".
• At the server console prompt, type "LOAD CLIB" to load the latest version of CLIB.
• At the server console prompt, type "AFTER311".
• At theserver console prompt, type "BSTART" to load BTRIEVE and BSPXCOM with default values.

This message results from improper installation of the Btrieve NLM. To install the NLM properly, obtain BTR61.EXE and perform the following ten steps:

This STATUS code can be returned when RUNNING BREQUEST with v2.00 of the NetWare OS/2 REQUESTER. MAKE sure to UPDATE your requester to v2.01.

This status code can be returned when running BREQUEST with v2.00 of the NetWare OS/2 Requester. Make sure to update your requester to v2.01.

RAISE the IPX retry count in your NET.CFG. The RECOMMENDED value is 40 or more. The workstations are TIMING out and their SPX connections are being TERMINATED.

Raise the IPX retry count in your NET.CFG. The recommended value is 40 or more. The workstations are timing out and their SPX connections are being terminated.

The NETWARE Btrieve NLM v6.10x has BUILT in support for v5.x files. System administrators can choose whether or not to convert the Btrieve data files in order to upgrade the NLM to 6.10x. As always, READ the README that comes with Btrieve for up to date DIRECTIONS on moving from one version to the next.

The NetWare Btrieve NLM v6.10x has built in support for v5.x files. System administrators can choose whether or not to convert the Btrieve data files in order to upgrade the NLM to 6.10x. As always, read the README that comes with Btrieve for up to date directions on moving from one version to the next.

Btrieve has SENT a message to a workstation that has been timed out by the NetWare WATCHDOG.

To prevent the message, increase the SPX WATCHDOG ABORT TIMEOUT, SPX ACK WAIT TIMEOUT, and SPX WATCHDOG VERIFY TIMEOUT parameters on the server where BSPXCOM.NLM is loaded. Also increase the SPX ABORT TIMEOUT, SPX LISTEN TIMEOUT, and SPX VERIFY TIMEOUT parameters in the NET.CFG FILE on the workstation.

Btrieve has sent a message to a workstation that has been timed out by the NetWare watchdog.

To prevent the message, increase the SPX WATCHDOG ABORT TIMEOUT, SPX ACK WAIT TIMEOUT, and SPX WATCHDOG VERIFY TIMEOUT parameters on the server where BSPXCOM.NLM is loaded. Also increase the SPX ABORT TIMEOUT, SPX LISTEN TIMEOUT, and SPX VERIFY TIMEOUT parameters in the NET.CFG file on the workstation.

If your system requires that the files be available for both NLM and client use, there are several steps to take to insure the proper use of the file:

Do not convert the 5.x files to the 6.x FORMAT. The versions of Btrieve for DOS, MS Windows, and OS/2 do not support the v6.x file format.

Read the SECTION of the Btrieve v6.10 README file that gives instructions on preimage files. Btrieve v5.x and v6.x pre-image files are incompatible and you need to take steps to prevent the different versions of the engines from using different version of the pre-image file.

When using BSETUP, be sure to select the option that creates files in the 5.x format. If this option is not used all files that are created will be in the new 6.x format and the clients will return status 2S when trying to access them.

If BTRIEVE.NLM v6.1x is configured with the -d option to force Btrieve to create files in v5.x format, what would happen if v6.1x file flags like: Index Balanced File Duplicate Pointers Key Number Specified VATs used in File are set at creation time?

These bits are IGNORED if you load NETWARE Btrieve v6.1x with -d. No errors will be returned. For more information about these new file creation options, see the Btrieve Programmer's Manual included with the Btrieve Developer's Kit Supplement.

If your system requires that the files be available for both NLM and client use, there are several steps to take to insure the proper use of the file:

Do not convert the 5.x files to the 6.x format. The versions of Btrieve for DOS, MS Windows, and OS/2 do not support the v6.x file format.

Read the section of the Btrieve v6.10 README file that gives instructions on preimage files. Btrieve v5.x and v6.x pre-image files are incompatible and you need to take steps to prevent the different versions of the engines from using different version of the pre-image file.

When using BSETUP, be sure to select the option that creates files in the 5.x format. If this option is not used all files that are created will be in the new 6.x format and the clients will return status 2s when trying to access them.

If BTRIEVE.NLM v6.1x is configured with the -d option to force Btrieve to create files in v5.x format, what would happen if v6.1x file flags like: Index Balanced File Duplicate Pointers Key Number Specified VATs used in File are set at creation time?

These bits are ignored if you load NetWare Btrieve v6.1x with -d. No errors will be returned. For more information about these new file creation options, see the Btrieve Programmer's Manual included with the Btrieve Developer's Kit Supplement.

WBTRCALL.DLL is a DOS Protected MODE Interface (DPMI) and allocates real mode memory according to the FOLLOWING formula:

DOSPARMBLK + maxDataLen + POSBLK_SIZE + KEYBUF_SIZE + 2 bytes

where: DOSPARMBLK is 28 bytes maxDataLen is defined by /d switch specified on the BREQUEST.EXE COMMAND LINE POSBLK_SIZE is 128 bytes KEYBUF_SIZE is 255

WBTRCALL.DLL is a DOS Protected Mode Interface (DPMI) and allocates real mode memory according to the following formula:

DOSPARMBLK + maxDataLen + POSBLK_SIZE + KEYBUF_SIZE + 2 bytes

where: DOSPARMBLK is 28 bytes maxDataLen is defined by /d switch specified on the BREQUEST.EXE command line POSBLK_SIZE is 128 bytes KEYBUF_SIZE is 255

NETX is causing the wrong path to be passed to BREQUEST. USE VLMs instead of NETX under the NetWare v4.x operating SYSTEM.

NETX is causing the wrong path to be passed to BREQUEST. Use VLMs instead of NETX under the NetWare v4.x operating system.

When ACCESSING Btrieve on a Netware Runtime Server, the USER must have a USERNAME other than SUPERVISOR. The SUPERVISOR username and password cannot be used on this server to access NetWare Btrieve.

LOAD BREQUEST with /C:1,USERNAME,PASSWORD

When accessing Btrieve on a Netware Runtime Server, the user must have a username other than SUPERVISOR. The SUPERVISOR username and password cannot be used on this server to access NetWare Btrieve.

Load BREQUEST with /C:1,USERNAME,PASSWORD

You should use BREBUILD in cases where you are converting data files from v5.x format to a v6.x format. Once the files are in v6.x format, they are considered to be "rebuilt." If the file shows SIGNS of data CORRUPTION, reload the data into a new file. STEPS for reloading data are described in the NETWARE Btrieve 6.10c README file.

You should use BREBUILD in cases where you are converting data files from v5.x format to a v6.x format. Once the files are in v6.x format, they are considered to be "rebuilt." If the file shows signs of data corruption, reload the data into a new file. Steps for reloading data are described in the NetWare Btrieve 6.10c README file.

To direct OUTPUT to a text FILE from an NLM, enter the command:

LOAD BUTIL -STAT BTRFILE (CLIB_OPT)/>SYS:output.txt

This command is case-sensitive with no spaces.

To direct output to a text file from an NLM, enter the command:

LOAD BUTIL -STAT BTRFILE (CLIB_OPT)/>sys:output.txt

This command is case-sensitive with no spaces.

• PRIOR to starting the application, if the environment variable SET BTRPARMSCHK=Y is specified, the status 1015 is returned.
• Isolation of errors that are caused by passing invalid pointers to Btrieve is done by using this environment variable.
• Once this variable is set, Btrieve performs the VALIDATION on pointer parameters that are passed in to READ/WRITE access on certain ranges.
• Btrieve validates position block pointer on the range of 128 BYTES, length pointer validates on TWO bytes and data BUFFER is validated on 255 bytes for key buffer

• The 62 Status is an error in the descriptor / EXTRACTOR.
• The first two bytes of the data buffer NEED to contain the exact length of the data buffer that are sent to Get Next EXTEND operation
• The Data Buffer length need not be the4 exact length
• If any other variable is defined, the data buffer would be OVERWRITTEN

The reasons for this are:

• An ALTERNATE collating sequence might be used.
• This REQUIRE to allocate an additional 265 bytes in the data buffer.
• NINE bytes are ALLOCATED for the name of the collating sequence and 256 bytes are allocated for actual sequence.

The reasons for this are:

• Yes. the right creation is necessary.
• BTRIEVE may create a file CALLED pre-image file, in ACCELERATED mode.
• During an insert(2), an index does not allow the DUPLICATES and the insertion of records causes a duplicate ERROR that is to be returned. 
• Any pages that have been updated already for the insertion, would need to roll back.

• No. Because Btrieve ALWAYS bypasses the bit 7 of the KEY flags at the time of creation.
• The bit 7 is DESIGNATED as an INDEX SUPPLEMENTAL
• The indexes are created as permanent.

The following are the factors :

• The page sizes of Btrieve are SET to 1024 and 512 bytes
• All the WORKSTATIONS are configured with IPX v2.15
• The disk block SIZE was set to a size apart from default 4k block size
• These factors cause a minor Btrieve performance degradation. 

The following are the combination of factors to improve performance.

• REBUILD the file size of Btrieve with a page size of 4096 bytes
• Upgrade IPX to v3.10
• Recreate all the volumes block size with 4k

The following are the factors :

The following are the combination of factors to improve performance.

To ensure the data retrieval correctly by BTRIEVE:

• Use the latest VERSION of NETWARE Shell - IPX v3.10, NETX v3.22 or NETX v3.26
• Make sure that latest BREQUEST.EXE is running
• Verify the Btrieve data file's page size
• If the pages are not evenly divisible into 4k, NetWare mishandles the pages
• Use only the pages of sizes 512k, 1024K, 2048k, or 4096k. 
• The situation would be resolved by USING NetWare Patch ASNCROFX.NLM

To ensure the data retrieval correctly by Btrieve:

When Netware time restrictions are in force and any user's connection to NetWare is terminated, the Btrieve files are remain open to that connection.

• If a new USES logs in and uses the same connection ID, the Monitor utilities will show all the files opened by new user.
• All these files have opened by Btrieve
• Back up can be taken when they are not in Continuous Operations Mode.
• As the necessary Btrieve Position blocks are not available, the user can not ACCESS these files.
• The application should perform an explicit Btrieve Reset Operation in ORDER to AVOID leaving files open or the work station should reboot before NetWare time restrictions take EFFECT.

When Netware time restrictions are in force and any user's connection to NetWare is terminated, the Btrieve files are remain open to that connection.

NETWARE Btrieve v6.x can access both v5.x and v6.x FORMAT files simultaneously and the performance is PROPER.

NetWare Btrieve v6.x can access both v5.x and v6.x format files simultaneously and the performance is proper.

• The 62 STATUS is an error in the descriptor / extractor.
• The first two BYTES of the data buffer need to contain the exact length of the data buffer that are SENT to Get Next Extend operation
• The Data Buffer length need not be the4 exact length
• If any other variable is DEFINED, the data buffer WOULD be overwritten

C long integer can be defined as a KEY in Btrieve by specifying the key as an integer. But the length need to be specified as FOUR bytes.

C long integer can be defined as a key in Btrieve by specifying the key as an integer. But the length need to be specified as four bytes.

• "TOTAL" column gives the NUMBER of UNIQUE values for EVERY KEY
• The column is different from "Total Records" column

• Once a file is opened by Btrieve, no other user / application can OPEN it until Btrieve closes that file.
• The operating system's 'COPY' command will not work
• One can BACK up the Btrieve file using BUTIL operations.
• BUTIL operations uses CLONE for CREATION of a backup file.
• Followed by CLONE, COPY command is used to backup the RECORDS from one file to backup file.

• Data available in a file can be SHARED by USING Single Engine File Sharing and Multiple Engine File Sharing modes.
• SEFS is ALLOWED only to the clients to ACCESS the engine for altering databases.
• MEFS allows multiple clients running under multiple engines for accessing the database.

• Rebuilding Btrieve FILES is possible using BREBUILD, if they have not extended across a volume.
• CONVERT4 should be USED after the files have been extended, for the purpose of translating Btrieve v3.x files to v4.x FORMAT
• Later we can run BREBUILD.
• Btireve v4.x and v5.x files can also be rebuild using BREBUILD.

• YES. First the DOS requester is loaded
• Later WINDOWS is loaded
• While the windows application is RUNNING,
• The first window calls BTRIEVE to load and Btrieve Request Interface for windows.

The following engines are REQUIRED to run BTRIEVE on SFT III server.

• Btrieve.nlm on MSEngine
• BSPXCOM.NLM on MSEngine
• AFTER311.NLM on IOEngine
• Btrieve is unaware of RUNNING SFT III Server
• The I/O and mirroring will be TAKEN care by OS

The following engines are required to run Btrieve on SFT III server.

• SYSTEM transactions are non-transactional OPERATIONS
• System transactions are used for DATA recovery using MKDE.
• User transactions are concurrent transactions.
• User transaction might have LOST when a recent transaction was rolled back
• When a user transaction is rolled back, an option might be set which causes the MKDE to force the system transactions.

• BREQUEST will not PROPERLY FUNCTION in multiple PRIVATE DOS boxes. The system will halt.
• Trap D occurs when Btrieve calls are made.

The following ENGINES are required to RUN Btrieve on SFT III server:

• Btrieve.nlm on MSEngine
• BSPXCOM.NLM on MSEngine
• AFTER311.NLM on IOEngine
• Btrieve is UNAWARE of running SFT III Server
• The I/O and MIRRORING will be taken care by OS

The following engines are required to run Btrieve on SFT III server:

• Btrieve Commander is a file viewer.
• The primary view is named as Main View that lists the records one per line. A cursor VERTICAL bar indicates the current record.
• Record View : It shows the records in the Main view and is limited
• Calculate Totals : This VIEWS allows to compute numeric fields of current record
• Import and Export of Records : The records in Btrieve can be imported from or exported to a Comma SEPARATED Value files or the raw format that is utilized by the BUTIL’s save FUNCTION.

• Btrieve Commander is a file viewer.
• The primary view is named as Main View that lists the records ONE per line. A cursor vertical bar indicates the CURRENT record.
• Record View : It SHOWS the records in the Main view and is limited
• Calculate Totals : This VIEWS allows to compute numeric fields of current record
• Import and EXPORT of Records : The records in Btrieve can be imported from or exported to a Comma Separated Value files or the raw format that is utilized by the BUTIL’s save function.

The .DDF FILE can be OBTAINED in TWO ways;

• The vendor of the product should be able to provide .DDF along with the SOFTWARE.
• Or use Xtrieve PLUS,XQL or NetWare SQL for creating the .DDF file.

The .DDF file can be obtained in two ways;

• DDF editor allows to create the description of FILES
• DDF is NECESSARY to access BTRIEVE files through ODBC / OLE
• Allows to
• create / view / edit dictionary DDF
• import and export data from ODBC data SOURCE
• drag and drop / copy and paste the descriptions
• rebuild files
• search FILTRATION data

• System TRANSACTIONS are non-transactional operations
• System transactions are used for data recovery using MKDE.
• User transactions are CONCURRENT transactions.
• User transaction might have LOST when a recent transaction was ROLLED back
• When a user transaction is rolled back, an option might be set which causes the MKDE to FORCE the system transactions.

• EVERY Btrieve file and DDF has a owner of their creation.
• Owner NAME can be USED to read only access.
• SET OWNER = command is used before utilizing SELECT statement.
• .lck FILES are lock files and can not read them directly.
• .btr files are DDF files.
• The conversion can be made by using ODBC DSN that points to data and utilizes SSIS or DTS to export the data from.

When you attempt to open v56.x file with v5.x version, a status (I/O ERROR) will be RETURNED

When you attempt to open v56.x file with v5.x version, a status (I/O error) will be returned

• INVALID OPERATION – The PARAMETER of the operations of a call is invalid
• I/O ERROR – An error OCCURRED during a disk read / write operation.
• FILE NOT OPEN – Any operation on the DESIGNATED file can not be PERFORMED as the file is not open
• KEY VALUE NOT FOUND - The designated key value is not found in the index path
• INVALID POSITIONING - Each time the current position need to be established. This position is application for update / deletion of a record.

• DATA available in a file can be shared by using Single ENGINE File Sharing and Multiple Engine File Sharing modes.
• SEFS is ALLOWED only to the clients to access the engine for altering databases.
• MEFS allows multiple clients RUNNING under multiple engines for accessing the database.

• Prior to starting the APPLICATION, if the environment variable SET BTRPARMSCHK=Y is specified, the status 1015 is returned.
• Isolation of errors that are caused by passing invalid pointers to Btrieve is done by using this environment variable.
• Once this variable is set, Btrieve performs the validation on POINTER parameters that are passed in to READ/WRITE access on certain ranges.
• Btrieve VALIDATES POSITION block pointer on the range of 128 bytes, length pointer validates on two bytes and data buffer is validated on 255 bytes for key buffer

The PROCESS is as follows:

• Run the BUTIL NLM version 6.x from the file server, which displays the version of file format after executing a STAT call.
• No client BUTIL program is AVAILABLE to display this status
• Another way is to check the version format of a Btrieve file by using DOS DEBUG utility
• Type debug-d at DOS prompt.
• The initial TWO bytes of the FCR will be set to FC when the file is STORED in 6.x format.
• Otherwise the bytes will be set to 0x00.

The process is as follows:

C long integer can be DEFINED as a key in Btrieve by specifying the key as an integer. But the length need to be specified as FOUR bytes.

C long integer can be defined as a key in Btrieve by specifying the key as an integer. But the length need to be specified as four bytes.

• Btrieve is a NAVIGATIONAL database product
• Based on Indexed Sequential Access Method(ISAM)
• ISAM is a way of FAST DATA retrieval
• Btrieve retrieves one RECORD at a time.
• TRANSACTION Operation is faster as there is little overhead with Btrieve Engine