
LANDesk Manager v1.50: Inventory Manager Usage Tips [06\25\94]
---------------------------------------------------------------
This file contains extensive information on the Btrieve environment used by
LANDesk Inventory Manager along with general tips on memory, Windows, etc.

This document is available as FaxBack Document 5534. It is also available with
the latest Inventory Manager software improvements discussed at the end of
this document in the self-extracting zip file IMGR.EXE on the Intel BBS in the
LANDesk Manager Current area. IMGR.TXT contains the text in this document.


Btrieve Environment
-------------------
Inventory Manager v1.50 supports Btrieve versions shipped with NetWare v3.11,
NetWare v3.12, and NetWare v4.01. The newer Btrieve versions are backwards
compatible with previous versions of NetWare. LANDesk Manager v1.0x only
supported the Btrieve version supplied with NetWare v3.11.

	Btrieve v5.15 and BREQUEST v5.16 supplied with NetWare v3.11
	------------------------------------------------------------
	If your files vary from the following list, you may obtain these files
	from your NetWare v3.11 Btrieve diskette.

		SYS:SYSTEM\BTRIEVE.NLM          2-19-91
		SYS:SYSTEM\BSPXCOM.NLM          1-24-91
		SYS:SYSTEM\CLIB.NLM             2-14-91 (or later)
		SYS:PUBLIC\BREQUEST.EXE         2-12-91
		SYS:PUBLIC\WBTRCALL.DLL         2-12-91 (or 6-28-91)

	Btrieve and BREQUEST v6.10 supplied with NetWare v3.12/v4.x
	----------------------------------------------------------------------
	If your files vary from the following lists, use your NetWare diskettes
	or download BTR61.EXE. NOTE: WBTR*.DLL must be copied to the
	administrator's network files directory (default SYS:LANDESK), and
	completely match either one OR the other Btrieve version.

						v6.10a          v6.10c/e
						------          ------
		SYS:SYSTEM\BTRIEVE.NLM          5-24-93         11-19-93
		SYS:SYSTEM\BSPXCOM.NLM          5-5-93          11-24-93
		SYS:SYSTEM\CLIB.NLM             12-16-92 (or later for both)
		SYS:PUBLIC\BREQUEST.EXE         5-13-93         12-09-93
		SYS:PUBLIC\WBTRCALL.DLL         5-13-93         same
		SYS:PUBLIC\WBTRVRES.DLL         1-30-93         same
		SYS:LANDESK\WBTRCALL.DLL        5-13-93         same
		SYS:LANDESK\WBTRVRES.DLL        1-30-93         same

NOTE: In rare instances, conflicting versions of WBTR*.DLL or BREQUEST.EXE in
the Windows environment should be renamed or removed. See the next section.



Copyright 1994 Intel Corporation
Miscellaneous Notes
-------------------
If you use BSTART.NCF, please make sure the parameters are not below the
settings listed in the section "Btrieve Defaults and Minimum Requirements." If
no other application uses Btrieve, just load LDINV.NLM and allow it to load the
Btrieve NLMs automatically (this loads the defaults listed in this document,
same as loading BTRIEVE.NLM and BSPXCOM.NLM without any special parameters).

If LDISCAN.EXE runs from a DOS prompt but seems to run out of memory during the
login process, increase conventional memory or consider running LDISCAN.EXE
outside the login script. LDISCAN.EXE/NLM need to see SAP 0x0102 (OT_INTEL) in
order to accurately detect that LDINV.NLM is running at the file server.

If your LANDesk Manager workstation's Windows is low on memory (conventional or
upper), a MACHINES.DAT error may occur. Unload other Windows applications or
TSRs to increase the largest executable program size (500 KB should be enough).
ALSO, adding a working directory to the Inventory Manager icon may help. When
printing to a file, select Window's Generic/Text Only printer.

If other software on your LDM administrator's workstation (for example, NMS)
requires a local version of WBTRCALL.DLL, you need to perform the following
steps to convert that WBTRCALL.DLL to WBTRLOCL.DLL:
	1.  Get WNDBCNVT.EXE from BTR61.EXE in the LANDesk Manager Interim area
	of the Intel BBS.
	2.  Run WNDBCNVT.EXE on the local version of WBTRCALL.DLL (not the one
	in the LANDESK directory). It will convert the local version of
	WBTRCALL.DLL to WBTRLOCL.DLL.
	3.  Place the WBTRCALL.DLL (requester) and WBTRLOCL.DLL (local) in the
	same directory or directories.
	4.  Edit the LOCAL line in NOVDB.INI's [brequestDPMI] section to read:
		local=Yes       ; allow access to Client-Only Btrieve DLL


Rebuilding the Inventory Database
---------------------------------
If you are experiencing problems with the Btrieve database files, you may want
to try salvaging the inventory already gathered by using Novell's BCLEAN.EXE,
BUTIL.EXE, or BUTIL.NLM to fix the .DAT files (contact Novell for details).
Or use the following steps to rebuild the MACHINES, TYPES, and VALUES .DAT
files. These steps may be required if a power outage or other unexpected
termination of the file server has corrupted the Btrieve files.
	1.  At the server console, type UNLOAD LDINV and UNLOAD LDISCAN.
	2.  Type LOAD LDINV REMOVE.
	3.  Type BSTOP. This unloads BSPXCOM.NLM and BTRIEVE.NLM.
	4.  At a workstation, delete MACHINES, TYPES, & VALUES .DAT files in
	the administrator's network files directory (default SYS:LANDESK). Also
	delete or rename LDINV.ERR and any MACHINES, TYPES, and VALUES .PRE
	files; in SYS:SYSTEM, delete or rename BTRIEVE.TRN (if they exist).
	5.  Type PURGE to totally eradicate the deleted .DAT and .PRE files.
	6.  At the server console, type LOAD LDINV FILE=SYS:\LANDESK then LOAD
	LDISCAN INV_SERV=servername FILE=SYS:\LANDESK (substitute as necessary).
	7.  At a workstation, run LDISCAN /V /S=servername (or just log in to
	the network if LDISCAN.EXE runs in the system login script).
	8.  Reboot the LANDesk Manager administrator's workstation and run
	BREQUEST /R:26 (the /R:26 option only benefits BREQUEST v5.16).
	9.  Load Inventory Manager from the LANDesk Control Panel in Windows.
Btrieve Defaults and Minimum Requirements
---------------------------------------------------------------
The default Btrieve values are used when BTRIEVE.NLM and BSPXCOM.NLM are
loaded individually or automatically when LDINV.NLM loads. If any other NLM(s)
uses Btrieve, run BSETUP.NLM to increase (perhaps double) the Btrieve
parameters so that LDINV.NLM and any other NLM(s) that access Btrieve will
have enough environment space. BSETUP.NLM builds a new BSTART.NCF (increasing
the parameters) that you should use to load Btrieve.

	NetWare Btrieve Defaults                LANDesk Manager Uses
	------------------------------------------------------------
	NUMBER OF OPEN FILES=20                         3
	NUMBER OF HANDLES=60                            9
	  (NUMBER OF HANDLES requires at least 3 times the NUMBER OF SESSIONS)
	NUMBER OF LOCKS=20                              1
	NUMBER OF TRANSACTIONS=0                        0
	NUMBER OF FILES PER TRANSACTION=12              0
	LARGEST COMPRESSED RECORD SIZE=0                0
	LARGEST RECORD SIZE=8192 (600 is minimum)       88
	LARGEST PAGE SIZE=4096                          4096
	NUMBER OF SESSIONS=15 (user defined)            3 (minimum)
	CONSOLE REFRESH COUNT=3
	CREATE FILES AS TRANSACTIONAL=NO                no
	LOGGING OF SELECTED FILES=NO                    no


Automatic Inventory Cleaning
----------------------------
Every 3 hours, LDINV.NLM initiates a cleaning process on the database files
(MACHINES.DAT, TYPES.DAT, and VALUES.DAT). This process purges any machine
information you may have deleted using LDINV.EXE. While the Btrieve record
management process runs, you may see high CPU utilization on the file server.
Server response time is not degraded because the low priority Btrieve operation
can be interrupted several times each second with higher priority requests.

The cleaning process takes less than a minute for a 30 record database, which
is the same amount of time it would take to load LDINV with the PACK option. A
100 record database may maintain high CPU utilization for 10 minutes, but you
will not notice it unless you're watching MONITOR.NLM at the right time or
using Server Monitor to notify you when utilization exceeds a certain level.


LANDesk Manager Inventory DataBase Definition Files
----------------------------------------------------
	INDEX.DDF     2,560  04-29-93  10:41p
	FIELD.DDF     7,168  04-29-93  10:41p
	FILE.DDF      3,072  04-29-93  10:41p
	FORMATS.DOC  21,746  05-18-94  11:26p

Since LANDesk Manager uses Btrieve to store inventory information, other
database programs that can read Btrieve files (for example, Microsoft Access)
can access LANDesk Manager's inventory information in its native format. This
allows greater flexibility presenting LANDesk Manager's inventory information.

Novell supplies three dynamic data dictionary files (.DDF) that contain the
necessary information to export Btrieve files into third-party programs. See
the enclosed Microsoft Word document called FORMATS.DOC for details.
Enhanced Software Scanning
--------------------------
	LDAPPL.INI  212484  4-21-94  8:30p

Use this updated LDAPPL.INI to enhance the number of software packages
recognized by LDISCAN.EXE. Approximately 500 companies and 4000 entries are
represented in this database. Copy this file to the same directory where
LDISCAN.EXE runs (default SYS:\LOGIN\LANDESK).

This new LDAPPL.INI may require multiple passes to accurately scan all of your
software, especially when a workstation is low on conventional memory. The
login process significantly reduces the largest executable program size, so
executing LDISCAN.EXE with the new LDAPPL.INI outside of the login process may
deliver better performance.

When you choose Edit/Software List in Inventory Manager's Windows' interface
(LDINV.EXE), Inventory Manager loads the editor LDISWED.EXE to modify the
contents of LDAPPL.INI. Unfortunately, the new LDAPPL.INI is too large for
LDISWED.EXE, and it reports a fault--closing it does not affect Windows.
Another text editor like DOS EDIT.COM can load and modify LDAPPL.INI just fine.

If your original LDAPPL.INI contains modifications you do not want to lose,
rather than run LDISCAN.EXE again with /q or cutting and pasting the unique
information into the new LDAPPL.INI, rename one of the LDAPPL.INI files and run
LDISCAN.EXE a second time with /I=NEWNAME.INI (the new file name) and /f to
force software scanning (the default setting is to scan software once daily).


Enhanced Error-Reporting
------------------------
	LDINV.NLM  58,530  04-21-94  11:53a

Customers with a rare combination of Btrieve errors would find LDINV.NLM
recording each and every instance of the errors until the error file grew very
large. We have modified LDINV.NLM to react differently in such a sitation; now
the file LDINV.ERR will grow at a normal pace with less repetition. If Btrieve
experiences many errors, each time LDINV.ERR reaches a size of 2 MB, we will
cut the first half of the file (the oldest messages), thus reducing the size
back to 1 MB.

Place this new LDINV.NLM in your SYS:SYSTEM directory, unload the LDINV.NLM
currently running, and load this one. Thanks for using LANDesk Manager!
