[Intel Navigation Header]

    LANDesk(R) Manager 1.51: Inventory Manager Usage Tips

    Contents:

    • BTRIEVE* ENVIRONMENT
    • BTRIEVE* AND BREQUEST V6.10 SUPPLIED WITH NETWARE* V3.12 / V4.X
    • BTRIEVE* V5.15 AND BREQUEST V5.16 SUPPLIED WITH NETWARE* V3.11
    • MISCELLANEOUS BTRIEVE* NOTES
    • BTRIEVE* DEFAULTS AND MINIMUM REQUIREMENTS
    • "BTRIEVE ERROR 2001 OR BTRIEVE ERROR 1002"
    • LOADER CANNOT FIND PUBLIC SYMBOL"
    • AUTOMATIC INVENTORY CLEANING AND CPU UTILIZATION
    • ERROR: "UNABLE TO OPEN TRANSACTION FILE" / REBUILD THE INVENTORY DATABASE
    • USING BTRIEVE* AS CLIENT/SERVER VERSUS LOCAL CLIENT
    • "LDINV FOUND A LOCAL COPY OF WBTRCALL.DLL IN C:\NMS\BIN IN WBTRCNMS.DLL..."
    
    

    BTRIEVE* ENVIRONMENT

    
       Inventory Manager v1.5x supports Btrieve* versions shipped with NetWare*
    
        v3.11, NetWare v3.12, and NetWare v4.01. NetWare v3.12 and v4.x ship
    
       with Btrieve v6.1, which is backwards compatible with NetWare v3.11. DO
    
       NOT load LANDesk(R) Manager v1.51 or earlier Inventory Manager NLMs on a
    
       NetWare v4.1 file server; Inventory Manager will support NetWare v4.1 as
    
       soon as possible.
    
    
    
       LANDesk Manager  v1.0x only supported the Btrieve version supplied with
    
       NetWare v3.11. Due to the common practice of running updated NLMs on
    
       NetWare v3.11 file servers, we highly recommend every LANDesk Manager
    
       server (especially NetFrame file servers) that run LDINV.NLM use one of
    
       the following sets of Btrieve v6.1 files:
    
    
    
       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. Novell's self-extracting BTR61.EXE is available
    
       on the Desktop Remote diskette, the LANDesk Manager Current Area on the
    
       Intel's online services, or from Novell NetWire on CompuServe.
    
    
    
    

    BTRIEVE* AND BREQUEST V6.10 SUPPLIED WITH NETWARE* V3.12 / V4.X

    
                                 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     5-13-93
    
       SYS:PUBLIC\WBTRVRES.DLL   1-30-93     1-30-93
    
       SYS:LANDESK\WBTRCALL.DLL  5-13-93     5-13-93
    
       SYS:LANDESK\WBTRVRES.DLL  1-30-93     1-30-93
    
    
    
       Note:     In rare instances, conflicting versions of WBTR*.DLL or
    
       BREQUEST.EXE in the Windows* environment should be renamed or removed. 
    
       See the section "Using Btrieve* as Client/Server Versus Local Client".
    
    
    
    

    BTRIEVE* V5.15 AND BREQUEST V5.16 SUPPLIED WITH NETWARE* V3.11

    
       These January/February 1991 files work fine in a pristine NetWare* v3.11
    
       environment, but with so many patches available from Novell that
    
       destabilize the Btrieve* environment, we highly recommend that NetWare
    
       v3.11 servers runnings post-1991 NLMs upgrade their Btrieve to v6.1.
    
       This is available on the Desktop Remote CD in LDM v1.51, in the LDM
    
       current area on the Intel's online services, or from Novell's NetWire on
    
       CompuServe.
    
    
    
       If you are not running post-1991 NLMs on your NetWare v3.11 file server,
    
       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)
    
    
    
    

    MISCELLANEOUS BTRIEVE* NOTES

    
       If you use BSTART.NCF, make sure the Btrieve* parameters meet or exceed
    
       the settings in the section Btrieve Defaults and Minimum Requirements.
    
       If no other application uses Btrieve, load LDINV.NLM and allow it to
    
       load the  Btrieve NLMs automatically with the defaults listed in this
    
       document, the same as loading BTRIEVE.NLM and BSPXCOM.NLM without any
    
       special parameters. If Cheyenne ArcServe is first in loading Btrieve in
    
       its ASTART.NCF file, after using the section Btrieve Defaults and
    
       Minimum Requirements to run BSETUP.NLM and double Btrieve's environment
    
       space (which records large enough parameter settings in a new BSTART.NCF
    
       file), modify ASTART.NCF to load Btrieve with the same parameters or run
    
       BSTART before ASTART in the AUTOEXEC.NCF file.
    
    
    
       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. Ad
    
    
    
       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 LANDesk(R)
    
       Manager is installed on multiple file servers, LDINV.NLM on one file
    
       server can support additional file servers. Run LDISCAN.EXE /s=FSNAME
    
       from the system login script of each file server. Some Flash memory
    
       versions may require the case-sensitive parameter /NF with LDISCAN.EXE.
    
       NetWare* login script functionality (IF DAY OF WEEK/MONTH...) can
    
       control when LDISCAN.EXE runs. The error: "SERVERNAME Not a Valid File
    
       Provider" indicates that SAP 0x0102 is not passing between a workstation
    
       running LDISCAN.EXE or a file server running LDISCAN.NLM and the file
    
       server running LDINV.NLM.
    
    
    
       Solution:
    
       Configure the routers between the devices in question to pass SAP 0x0102
    
    
    
       If your LANDesk Manager workstation's Windows* is low on conventional or
    
       upper memory, a MACHINES.DAT error or Btrieve errors 1002/2001 may
    
       occur. Unload other Windows applications or TSRs to increase the largest
    
       executable program size (500 KB should be enough). Also, place a working
    
       directory in the Inventory icon. When printing to a file, select
    
       Window's Generic/Text Only printer.
    
    
    
    

    BTRIEVE* DEFAULTS AND MINIMUM REQUIREMENTS

    
       The default Btrieve* values are used when BTRIEVE.NLM and BSPXCOM.NLM
    
       are loaded individually or when LDINV.NLM loads them automatically. If
    
       any other NLM 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 with the proper parameters that you should use to load
    
       Btrieve.
    
    
    
       NetWare Btrieve Defaults                     LANDesk(R) Manager Uses
    
       -----------------------------------------------------------------
    
       Number of Open Files=20                      3
    
       Number of Handles=60                         9
    
    
    
         (Number of Handles requires at least 3
    
          times the Number of Remote Sessions)
    
       Number of Locks=20                           1
    
       Number of Transactions=0                     0
    
       Largest Compressed Record Size=0             0
    
       Largest Record Size=8192 (600 is minimum)    88
    
       Largest Page Size=4096                       4096
    
       Number of Remote Sessions=15 (user defined)  3 (minimum)
    
       Cache Allocation=512                         na
    
       Perform Index Balancing=No                   na
    
       Create Files as Transactional=No             no
    
       Logging of Selected Files=No                 no
    
       Create Btrieve files in pre v6.x format=No   na
    
       Configure BSTART.NCF to Load BRouter=No      na
    
    
    
    

    "BTRIEVE ERROR 2001 OR BTRIEVE ERROR 1002"

    
       Product:  LANDesk(R) Manager, Component:  Inventory Manager
    
    
    
       Description:
    
       Your Windows* environment does not have sufficient conventional or total
    
       memory available for LDINV.EXE to execute.
    
    
    
       Solution:
    
       Do one or more of the following items:
    
    
    
         *  If you use BSTART.NCF, make sure the Btrieve* parameters meet or
    
            exceed the settings in the section Btrieve Defaults and Minimum
    
            Requirements. If no other application uses Btrieve, load LDINV.NLM
    
            and allow it to load the  Btrieve NLMs automatically with the
    
            defaults listed in this document, the same as loading BTRIEVE.NLM
    
            and BSPXCOM.NLM without any special parameters. If Cheyenne
    
            ArcServe is first in loading Btrieve in its ASTART.NCF file,  run
    
            BSETUP.NLM and double Btrieve's environment space (which records
    
            large enough parameter settings in a new BSTART.NCF file), modify
    
            ASTART.NCF to load Btrieve with the same parameters or run BSTART
    
            before ASTART in the AUTOEXEC.NCF file.
    
    
    
         *  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
    
            LANDesk(R) Manager is installed on multiple file servers, LDINV.NLM
    
            on one file server can support additional file servers. Run
    
            LDISCAN.EXE /s=FSNAME from the system login script of each file
    
            server. Some Flash memory versions may require the case-sensitive
    
            parameter /NF with LDISCAN.EXE. NetWare* login script functionality
    
            (IF DAY OF WEEK/MONTH...) can control when LDISCAN.EXE runs.
    
    
    
         *  Unload some of the other Windows applications currently loaded. If
    
            the  error still appears with only Program Manager running, follow
    
            the instructions  in the next item.
    
    
    
         *  Increase the largest executable program size to at least 500 KB
    
            before  entering Windows. (MEM or MEM /C shows you what is in
    
            memory and what the  largest executable program size is.)
    
    
    
       The first two items cover up to 99 percent of the issues, but here's
    
    
    
       more:
    
    
    
         *  Download and use the new WUSER.EXE in DTAC.EXE (self-extracting zip
    
            in the  LANDesk Manager Current area on the Intel's online
    
            services)--it handles Windows memory even  better than previous
    
            versions.
    
    
    
         *  Try reducing the value specified by the /D configuration option
    
            when  loading BREQUEST.EXE in DOS. We only use the default but
    
            probably don't need it.
    
    
    
               BREQUEST /D:2048
    
    
    
               BREQUEST v5.15 supports the following parameters:
    
    
    
                  [/R:number of mapped drives] default is 32 - range= 1-32
    
                  [/D:data message length] default is 4096 - range= 532-57,748 
    
                  [/S:number of file servers] default is 8 - range= 1-8
    
                  [/?] help screen
    
    
    
               BREQUEST v6.1 supports the following parameters:
    
    
    
                  Usage: BREQUEST [/d:data_buffer_length]
    
                  /d: The size of the largest data buffer which BREQUEST can
    
                  send or  receive. Default is 4096 - range= 532-57,748
    
                  /s and /r are obsolete parameters which are accepted but
    
                  ignored.
    
                  /c:0 or /c:1[,loginName[,password]] run-time server support 
    
                  disabled/enabled
    
                  /o on-the-fly compression
    
    
    
         *  Change Window's WIN.INI file. The [brequestDPMI] section should
    
            read:
    
    
    
               datalength=nnn ;same as the /D: option on Brequest
    
              c;validate pointer parameters
    
              l;access local files through Btrieve DLL
    
              t;maximum numver of active tasks to use the DLL 
    
    
    
    

    LOADER CANNOT FIND PUBLIC SYMBOL"

    
       Symptom:
    
       When you try to load LDINV.NLM and you get the error  "Loader cannot
    
       find public symbol".
    
    
    
       Solution:
    
       Get latest Btrieve* files and it will work.  Btrieve version 6.1x is on
    
       the Intel online services (BTR61.EXE in the current area).
    
    
    
    

    AUTOMATIC INVENTORY CLEANING AND CPU UTILIZATION

    
       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. During the
    
       Btrieve* record management process, you may see high CPU utilization on
    
       the file 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 may take 10 minutes for a 100 record database, but
    
       you will not notice it unless you're watching MONITOR.NLM at the right
    
       time or Server Monitor notifies you when utilization exceeds a certain
    
       level. In an effort to lower utilization concerns, we changed cleaning
    
       to every 24 hours and worked with Btrieve Technologies to slow the
    
       process. Download IMGR.EXE.
    
    
    
    

    ERROR: "UNABLE TO OPEN TRANSACTION FILE" / REBUILD THE INVENTORY DATABASE

    
       This error may appear at the file server console when loading
    
       BTRIEVE.NLM. 
    
    
    
       Solution:
    
       We recommend that you use BTRIEVE* v6.1 (download BTR61.EXE from the
    
       Interim area of the LANDesk(R) Manager section on the Intel's online
    
       services if necessary).
    
    
    
       Make sure that the CLIB.NLM is dated 12-16-92 or later and currently
    
       resides in the file server's memory. This may involve unloading the
    
       currently running CLIB.NLM (a sometimes laborious process because of
    
       common NLMs resourcing it that must be unloaded first).
    
    
    
       Follow the steps to rebuild the Inventory database to make sure .DAT
    
       files from different versions of Btrieve are gone.  Before loading
    
       Btrieve, delete or rename BTRIEVE.TRN in the SYS:SYSTEM directory.
    
    
    
       Rebuild the Inventory Database
    
    
    
       If you are experiencing problems with the Btrieve database files, we
    
       recommend that you use the steps below 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.
    
    
    
       You may be able to salvage the inventory already gathered by using
    
       Novell's BCLEAN.EXE, BUTIL.EXE, or BUTIL.NLM to fix the .DAT files. 
    
       Contact Novell for details on fixing a corrupt Btrieve database.
    
    
    
         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 if no other
    
            application is currently using it.
    
    
    
         4. At a workstation, delete or rename the following files in the
    
            administrator's network files directory (default SYS:LANDESK):
    
    
    
            MACHINES, TYPES, & VALUES .DAT files
    
            MACHINES, TYPES, & VALUES .PRE files 
    
            LDINV.ERR
    
            BTRIEVE.TRN in SYS:SYSTEM
    
    
    
         5. Type PURGE to totally eradicate the deleted .DAT and .PRE files.
    
    
    
         6. At the server console, type
    
    
    
            BSTART (only necessary if other NLMs use Btrieve)
    
            LOAD LDINV FILE=SYS:\LANDESK (substitute as necessary)
    
            LOAD LDISCAN INV_SERV=servername FILE=SYS:\LANDESK
    
    
    
         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(R) 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*.
    
    
    
    

    USING BTRIEVE* AS CLIENT/SERVER VERSUS LOCAL CLIENT

    
       If other software on your administrator's workstation (for example, NMS)
    
       requires a local version of WBTRCALL.DLL, perform the following steps to
    
       convert that WBTRCALL.DLL to WBTRLOCL.DLL:
    
    
    
         1. Get WNDBCNVT.EXE from BTR61.EXE on the Desktop Remote diskette or
    
            in the LANDesk(R) Manager Current area of the Intel's online
    
            services.
    
    
    
         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 be:
    
    
    
            local=Yes       ; allow access to Client-Only Btrieve DLL
    
    
    
       Run DIR WBTR*.DLL /S from the root of your hard drive and file server
    
       volumes to find extraneous files (older or newer versions) that can
    
       possibly interfere with Inventory Manager, which relies only on matching
    
       WBTR*.DLL files in your SYS:PUBLIC and SYS:LANDESK. The most common
    
       manifestation of mismatched versions is that the main Inventory Manager
    
       screen will have a number in the lower right corner indicating records
    
       are in the database, yet the display is empty.
    
    
    
    

    "LDINV FOUND A LOCAL COPY OF WBTRCALL.DLL IN C:\NMS\BIN IN WBTRCNMS.DLL..."

    
       Symptom:
    
       There is a new Btrieve* .DLL file for NMS 2.0B called WBTRCNMS.DLL that
    
       does what WBTRCALL.DLL did in earlier versions.  LDINV.EXE complains as
    
       before, but the old workaround (delete WBTRCNMS.DLL) leaves NMS
    
       inoperable.
    
    
    
       Description:
    
       A mistake was made in renaming the file WBTRCALL.DLL to WBTRCNMS.DLL. 
    
       Novell renamed it ok but forgot to change the name INSIDE the file.  A
    
    
    
       fix is now on CompuServe.
    
    
    
       Solution:
    
       Download the new NMS upgrade from Novell. The upgrade has made some
    
       changes to the WBTRCNMS.DLL and it will work with the WBTRCALL.DLL 
    
       properly (NMS190.EXE).
    
    
    
       Note:     These changes were made to the file NMS190.EXE on 5-13-94.
    
    
    
       Note:     Previously, NMS (v2.0) left a WBTRCALL.DLL in C:\NMS\BIN. 
    
       LDINV.EXE used to complain about it, saying that the NMS copy of
    
       WBTRCALL.DLL was a local one.  We used to simply get rid of NMS's
    
       WBTRCALL.DLL or run WNDBCNVT.EXE and all appeared to be well.
    
    

    Trademark information