${BSE}/lib directory

The ${BSE}/lib directory contains the subdirectories that contain the settings and files with the database driver information.

This diagram is an example of the structure in the ${BSE}/lib directory:

In the ${BSE}/lib directory, you can find these subdirectories:

  • barcode: Contains the scripts that are required to print barcodes (UNIX only)
  • defaults: Contains files to set resources.

    See LN environment variables and resources

  • install: Contains the files, and not merely log files, that are used to install LN. You cannot remove or clean up this directory.
  • labels: Contains the label resource files from which the label descriptions are read at runtime
  • locale: Contains the LN superset locales. A locale contains information about character-set definitions, native language support, and the minimum and maximum values of the forms and database fields.
  • models: Contains runtime files for Document Authorization, also known as Database Change Management (DBCM).
  • nlsinf: Contains the files for various terminal types, which enables the Virtual Machine (VM) to support several languages and their specific characters
  • RDBMS: Contains the programs for the database you use. For example, if you use an Oracle database, the notation of the RDBMS directory is ${BSE}lib/ora.
  • roles: Contains the authorizations and database permissions of the LN users
  • printinf: Contains the printer drivers with detailed printer definitions for various types of printers. You can use a driver each time an LN report is sent to a printer.
  • terminf: Contains the terminal definition files (drivers) for various types of terminals
  • textinf: Contains error messages for the display servers
  • user: Contains the u<User> files for every LN user. These files store the basic user data, such as the Startup menu, the package combination, and the default company. Some other files are optional, for example, the remote user file r<User> .
  • zoneinfo: Contains files to support dates/times in various time zones
  • zonerules: Contains files to support dates/times in various time zones

The ${BSE}/lib directory also contains these files:

  • auditdef6.2 / auditdef6.1: Contains the directory paths where the sequence files are stored on the system. The auditdef6.1 is used for Infor Baan IVc. The auditdef6.2 is used for Infor Baan 5.0 and Infor LN.
  • audit_spec: Specifies how the audit trail is organized and handles permission issues
  • audit_cols: Defines which tables and fields are audited, and when the tables are audited
  • audit_hosts: Defines on which system the audit servers run
  • compnr6.2 / compnr6.1: Contains information on the mapping of logical and physical companies/tables. The compnr6.1 is used for Infor Baan IVc. The compnr6.2 is used for Infor Baan 5.0 and Infor LN.
  • datecurr: Contains the date format and currency format
  • dtopt.<Language Code> : Contains information that the Virtual Machine uses to display the menus in the user interface
  • fd6.2.<Package Combination> : Contains the location of the software components for a particular package combination
  • ipc_info: Contains the technical information the display driver uses, and the database drivers
  • srdd_tab6.2 / srdd_tab6.1: Contains the names of the software components that are loaded into shared memory during the start-up process. The srdd_tab6.1 is used for Infor Baan IVc. The srdd_tab6.2 is used for Infor Baan 5.0 and Infor LN.
  • tabledef6.2 / tabledef6.1: Contains the database types that are used for the various tables. If one or more tables are located on a remote system, then the remote system name is in this file. The tabledef6.1 is used for Infor Baan IVc. The tabledef6.2 is used for Infor Baan 5.0 and Infor LN.
  • tss*: These files are related to the Triton Super Set (TSS). TSS is a collection of character sets that you can use in Infor LN or Baan applications. TSS accommodates all multibyte character sets in a single package. TSS includes both ASCII character sets and multibyte character sets, such as Japanese, Chinese, and Hebrew.
Note: Do not edit the files in the ${BSE}/lib directory manually.
  • Some files are delivered as standard files and must only be modified by Infor
  • Some files can be regenerated through a conversion to the runtime data dictionary. For example, to change the contents of a user file in ${BSE}/lib/user. Perform the desired changes in the User Data (ttaad2500m000) session. Subsequently convert the changes to runtime through the Convert Changes to Runtime DD (ttams2200m000) session.