License Terms

The license terms for all software components owned by limes datentechnik gmbh ® can be found in the LICENSE.txt file provided at download or located in the doc/txt folder of the installation directory or in the HLQ.FLAM.DOCTXT partitioned dataset. Additional license information for external libraries used by this software can be found in the corresponding LICAPX.txt, ABOUT.txt, or manual files. The replacement of external libraries (LGPL) is described in the LICAPX.txt file or in the corresponding manual chapter. All license terms for external libraries are included as LICxxxxx.txt files in the doc/txt folder or in the HLQ.FLAM.DOCTXT partitioned dataset.

All old FLAM components up to version 4 are fully owned by limes datentechnik gmbh ®. On Linux systems, the unmodified glibc is used as a prerequisite (part of the operating system, not part of the distribution) based on the LGPL license. The old FLAM4 components do not provide additional license, about and version commands or functions.

The service provider interfaces (exits, extensions) of FLAM are fully owned by limes datentechnik gmbh ® and provided to our users for individual extension of this software. The driver complies with these license terms, but limes datentechnik gmbh ® is not responsible for any individual implementations that are not part of our distribution. Our own implementations of these SPIs (e.g. FAVECAV, PKCS#11, IBM-CCA/ICSF) comply with the stated license terms.

A lot of this information is generated during the package build process and can be obtained via the corresponding built-in commands of our utilities or the corresponding functions of the APIs. To obtain the current valid state, please use the commands or functions listed below (there are more APIs with similar functions available):

 COMMAND            API 1      API 2      ...   API n
 > flam4 license   fcblic()   FCRLIC()   ...   fliconv_license()
 > flam4 about     fcbabo()   FCRABO()   ...   fliconv_about()
 > flam4 version   fcbvsn()   FCRVSN()   ...   fliconv_version()

The about and version information are also included as appendices in the manuals provided by limes datentechnik gmbh ®.

The version information contains the version, release, and revision number of each component, followed by the current build number. The versioning of the different components is independent of each other. The build number must be the same for all components and must correspond to the build number of the installation package. If the build number is not identical for all compiled and linked components, then the installation is incorrect.