- Generated on for FSEG-SPI by
1.18.0
Below you can find some general information about these interface.
Below, you can find all trademarks or registered trademarks of limes datentechnik (R) gmbh. These trademarked terms are marked with the appropriate symbol ((R) or (TM)), indicating registered or common law trademarks owned by limes datentechnik (R) gmbh at the time this information was published. The following terms are trademarks of limes datentechnik (R) gmbh in Germany, other countries, or both: LIMES(R) - Short company name of the owner of this document limes datentechnik(R) - Company name of the owner of this document FLCL(R) - Frankenstein Limes Command Line FLCC(R) - Frankenstein Limes Control Center FLAM(R) - Frankenstein Limes Access Method FLUC(R) - Frankenstein Limes Universal Converter FLIES(R) - Frankenstein Limes Integrated Extended Security FKMS(R) - Frankenstein Key Management System FKME(R) - Frankenstein Key Management Extension/Exit FLAMFILE(R) - A file based on FLAM syntax CLE/P(R) - Command line Executer/Parser
The license terms for all software components owned by limes
datentechnik gmbh (R) 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 (R). 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 (R) and provided to our users for
individual extension of this software. The driver complies with these
license terms, but limes datentechnik gmbh (R) 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
> &{pgm} license fcblic() FCRLIC() ... fliconv_license()
> &{pgm} about fcbabo() FCRABO() ... fliconv_about()
> &{pgm} version fcbvsn() FCRVSN() ... fliconv_version()
------------------------------------------------------------------------
The about and version information are also included as appendices in the
manuals provided by limes datentechnik gmbh (R).
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.
Every external library FL5 uses under the LGPL is delivered as a shared library (.so, .dll) in the program directory, never linked statically into the FL5 binaries, so that it can be replaced. Libraries under other licenses may be linked statically and are not covered here. To replace one, either delete it in the program directory when the replacement is already on the library path, or overwrite it in the program directory. The replacement has to fulfil the same interface, which in practice means the same major version of the same library. NOTE: In all cases we recommend using the tested and supported libraries from this package. If a supplied library is replaced, the license terms and warranty of the new library become valid, replacing the license and warranty of the replaced library. In particular, FL5 itself is then no longer covered by our warranty, because we can no longer say which code it runs against. THE THREE ZLIB IMPLEMENTATIONS: The zlib compression interface is provided by more than one implementation, and which one is active depends on the platform. This matters for reading the SBOM and the CVE reports, so it is stated here rather than left to be inferred. zlib-ng is used wherever it can be built, because it is markedly faster and is a drop-in replacement: it provides the zlib interface, and the zlib version it reports is the interface level it implements, not a zlib release. Where zlib-ng cannot be built, the original zlib is used instead, with no difference in behaviour. On z/OS and USS the extended zlib of IBM is used, which supports the zEDC hardware compression of the platform. It is part of the operating system and is maintained by IBM, so it is a prerequisite rather than something we deliver. Where zEDC is unavailable and no Language Environment is at hand, FL5 falls back to its own build of the original zlib. For the SBOM and for vulnerability tracking, zlib and zlib-ng are therefore carried as two separate components with their own versions, their own licenses and their own advisories -- they are separate projects, and a vulnerability in one is not a vulnerability in the other. IBM's zlib is not tracked by us at all: as part of the operating system it is covered by IBM's own maintenance, in the same way as the C runtime library.
1.18.0