flam4_manual-glossary

Glossary

ADC: Abbreviation for Advanced Data Compression, which is the default compression algorithm of FLAM4.
AES: The Advanced Encryption Standard (AES) is a symmetric crypto system, the successor of DES and 3DES. It uses the Rijndael algorithm with a fixed block size of 128 bits and a variable key length of 128, 192 or 256 bits, providing a high grade of security.
ASCII: The American Standard Code for Information Interchange (ASCII) is a 7-Bit encoding, which is the source for later character sets based on more bits.
AVS: Anti virus scanning
BAS: Abbreviation for base encoding.
BCS: Banking Communication Standard.
Specification for remote data transmission between customers and credit institutions. The BCS is used, for example, in cash management systems to enable multi-bank capability, i.e. the processing of data from different credit institutions with software.
BIG ENDIAN: Endianness refers to the term byte order. A big-endian machine stores the most significant byte first, i.e. at the lowest byte address. This behavior is most important when two computers with different byte orders communicate with each other. The big-endian format is used by Motorola 6800 and 68k, Xilinx Microblaze, IBM POWER, System/360, System/370, ESA/390, z/Architecture and PDP-10.
BIN: Abbreviation for binary.
BOM: The Byte Order Mark (BOM) characterizes in which order the bytes are interpreted. This is important when exchanging data between different systems. For UTF-16 and UTF-32 a BOM sign at the beginning of the data stream is necessary, as more than one byte is used for the encoding of one character. UTF-8 uses the BOM sign "EF BB BF", which is used to mark a text file as UTF-8, even though byte order is not issue here.
BOMUTF: With this option of the FLCL, you can determine the correct UTF CCSID from the byte order mark (BOM).
BOMUCS: With this option of the FLCL, you can determine the correct UCS CCSID from the byte order mark (BOM).
BYTE ORDER: The byte order is the order in which bytes are interpreted for entities that consist of multiple bytes, e.g. Unicode characters. This is important when exchanging data between different systems. A big-endian machine stores the most significant byte first, i.e. at the lowest byte address. A little-endian machine, however, stores the least significant byte first.
BZ2: Abbreviation for BZIP2.
CANONICAL EQUIVALENCE: Canonical equivalence is a fundamental equivalence between individual Unicode characters and sequences of Unicode characters.
CASEMETHOD: FLCL offers a method for converting unicode characters to uppercase, lowercase or some special representation (CASE=UPPER/LOWER).
CCSID: This is an abbreviation used by IBM for "Coded Character Set Identifier". The encoding of a specific code page is referred to by a 16-bit number. see also: CCSID
CHAR: Abbreviation for the conversion of character streams.
CHR: Abbreviation for character
CLAMD: Clam Anti Virus Daemon
CNV: Abbreviation for conversion. Collects all conversion components which transform data stream in data stream (e.g. character conversion, compression, de/encryption, de/encoding, ...).
CODEPAGE: IBM introduced a numbering scheme to character encodings (16 bits). This scheme was taken over by other vendors like Microsoft, SAP or Oracle Corporation. The term Codepage is used synonymously for character encoding or character set.
CODE POINT: A code point or code position is a single character in a list of characters represented as numerical values that create the code space. The Unicode code space has a total size of 17 * 65536 code points. The same code space may have several codepages.
COMPATIBILITY EQUIVALENCE: One speaks of compatibility equivalence of two sets of characters if their full compatibility decompositions are identical.
CONV: The sub-program FLUC offers all possible conversion and formatting methods via the CONV command. These are various read and write procedures, many useful conversion tools and some special data formatting features.
CNV: Conversion component
CRY: Abbreviation for crypto(graphy).
CX7: Compression encoding as printable characters in FLAM4
CX8: Compression encoding as binary data in FLAM4
DAT: Abbreviation for data.
DIACRITIC: A diacritic is also called diacritical mark, diacritical point or diacritical sign. Typical diacritical marks are the acute (´) and grave (`), which are often called accents. Diacritical marks may be a dash, dot or tick above or below a letter, or in some other position such as within the letter or between two letters.
DIR: Abbreviation for directory (walk).
EBCDIC: The Extended Binary Coded Decimals Interchange Code (EBCDIC) was developed by IBM as 8-Bit-encoding, which, however, does not use all code words. EBCDIC originates from the older 4-Bit-Code BCD (Binary Coded Decimals) and is applied solely on Mainframes. The EBCDIC codepages are available in German, US, Swedish, Arabian, Latin-1 and other languages. Moreover, there exists a Unicode set of characters based on EBCDIC and it is called UTF-EBCDIC.
BLK: Abbreviation for block.
ENV: Abbreviation for environment.
FINGERPRINT: In public-key cryptography, a public key fingerprint is a short sequence of bytes used to identify a longer public key. Fingerprints are created by applying a cryptographic hash function to a public key. Since fingerprints are shorter than the keys they refer to, they can be used to simplify certain key management tasks.
see also: Public key fingerprint
FIO: Abbreviation for File I/O. All components to read or write files. The C programming language has a general mechanism for reading and writing files abstracting all Input/Output to streams of bytes. The operating system offers redirection which can be very useful. Examples are the standard input stream, standard output stream and standard error stream.
FKME: FLAM Key Management Exit/Extension Service provider interface to connect FLAM till version 4 with different kinds of cryptographic infrastructure, hardware security modules and/or key management systems.
FL4: Abbreviation for FLAM in Version 4 or lower.
FL5: Abbreviation for FLAM in Version 5.
FLAM: Frankenstein Limes Access Method. FLAM is our access method for encrypted and compressed data. In particular, FLAM is a utility for converting, compressing, encrypting (with AES (Advanced Encryption Standard)), signing and formatting of mass data with simple interfaces for integration in all kinds of solutions. All this is done with a minimum of CPU utilization, utilization of co-processors and the use of professional key management solutions. Ordinarily, FLAM provides - when used as sub-program - the commands COMP and DECO and makes use of an element interface for the subsystems/plugins/drivers and also the sub-program.
FLAM4: This component writes a Flamfile record-oriented. You can state the name of a Flamfile or that of a member.
FLAMFILE: The FLAMFILE is composed like a package file, as multiple files can be compressed. It is structured clearly and divided hierarchically in records, segments and members. In this connection a segment is referred to the single matrix of a compressed file and a member to the entity of segments that are part of the compressed file. In order to ensure the universal exchangeability, the FLAMFILE has to be available in a format that is representable on all operating systems (so-called heterogeneous compatibility). Each compressed data segment is unique referring to data content, environment and time. This allows - despite compression/encryption - an access down to the record-level, without decompressing/decrypting.
FLCC: Frankenstein Limes Control Center (GUI).In contrast to FLCL this is the graphical user interface for running FLAM, FLUC and FLIES, quasi a dialogue utility
FLCL: Frankenstein Limes Command Line. FLCL offers a command line for the three sub-programs FLAM, FLUC and FLIES. It is a quasi-batch utility for the sub-programs. Moreover, FLCL is a universal data format and character set converter, which can be included easily in professional internationalization projects. It supports different input and output formats (GZIP, PDF, B64...) and can be integrated into scripts or as sub-program. More than 150 codepages are supported. FLCL can be applied to various commonly used platforms if working with processable data streams or file I/O.
FLIES: Frankenstein Limes Integrated Extended Security. The sub-program FLIES governs the compressed and encrypted segments using commands like FIND and CHNGE. In particular, it is useful for processing Flamfiles, which however cannot be decrypted or decompressed. For instance the data in the file header is managed by FLIES to re-encrypt the file, change the data access, use as backup, archive or as mediator/headend.
FLUC: Frankenstein Limes Universal Converter. FLUC is a universal text converter with special focus on the high requirements in professional internationalization projects, where Mainframes and external applications are used as central backend.
FLUCUP: FLUC Subprogram as C interface (DLL) for Data source to target conversion.
FMT: Abbreviation for formatting. All components to parse a data stream in FLAM5 element list or build a data stream from FLAM5 elements list.
FROM-CODE: The FROM-Code specifies the character encoding of the input data that used as source encoding for character conversion.
GZIP: GZIP is a compression program for nearly every operation system and uses the DEFLATE algorithm from the ZLIB library. GZIP is the short form for GNU zip. The used algorithm is a combination of LZ77 and Huffmann encoding. The source code is licensed under the GPL. The program has 9 compression steps providing either optimal CPU time or compression ratios. The compressed file has the ending ".gz". As GZIP compresses only single files. Several files must first be combined with (for example) "tar" to a tarball which can then be compressed to a ".tar.gz" file. GZIP files have a 10-byte header, containing a magic number, a version number and a timestamp. With FLCL you are able to read and write GZIP files, to mark content as text data in the header, set operating/file system or modified time (seconds since 1970).
GZP: Abbreviation for GZIP.
HOST: see MAINFRAME
HSH: Abbreviation for hash (checksum)
ICNV: Abbreviation for iconv conversion with simplified commands on the command line.
ICONV: With the standard program iconv, characters can be translated between different encodings on UNIX-like systems. As iconv is now part of the GNU C Library, actual Linux systems are equipped with iconv. Under Windows®, iconv is provided only as DLL or static library, which is under the license of the GPL and can be used via Cygwin or GnuWin32. Iconv is also supported as Dynamic Link Library for PHP.
ID: Abbreviation for identifier.
ISO-8859: The ISO-8859 norm family contains some useful 8-bit character sets (e.g. Latin-1 to Latin-15). The frequently used Latin-1 character set is identical with the first 256 characters of the Unicode character set. These codepages are also called extended Ascii.
LITTLE ENDIAN: A little-endian machine stores the least significant byte first. The endianness of a 16, 32 or 64 bits word or even bits can occur in some Unicode representations. Also mixed forms of endianness are possible, for example when the byte order within a 16 bits word differs from that of a 16 bits word within a 32 bits word. The little-endian format is used by x86 (including x86-64), 6502 (including 65802, 65C816), Z80 (including Z180, eZ80 etc.), MCS-48, 8051, DEC Alpha, Altera Nios II, Atmel AVR, SuperH, VAX, and PDP-11.
LOGGING: In FLCL various messages (warnings, errors, debug information, important information, input data) can be logged. The messages can be redirected from stderr to stdout or a file.
LXZ: Abbreviation for LZMA XZ.
MAINFRAME: A mainframe is a very complex and powerful computer system. Its capacity is far beyond that of a common Personal Computer and that of most servers. They are applied for the highly reliable processing of mass data, mass transactions and company critical data and gain importance again in connection with server consolidation and cloud computing.
MODE: With the keyword MODE in FLCL you can select the mode of operation.
NDC: Abbreviation for No Data Compression, which can be considered as copying data in FLAM4.
NFC: This is Normalization Form C (Canonical Decomposition, followed by Canonical Composition).
NFD: This is Normalization Form D (Canonical Decomposition).
NFKC: This is Normalization Form KC (Compatibility Decomposition, followed by Canonical Composition).
NFKD: This is Normalization Form KD (Compatibility Decomposition).
Normalization: The transformation of a character sequence in one of the four normal forms is called normalization. Normalization is necessary, because there is more than one differing possibility for many characters to be represented as a sequence of Unicode characters. The four normal forms consist of one form for the canonical equivalence, one for the compatible equivalence, and both can be in a "composed" or "decomposed" form.
OS: Abbreviation for operation/file system in the header
PADDING: Padding are bytes inserted to align the data to certain lengths or storage positions. Padding bytes are most commonly appended after the the last data byte. When reading padded data, the padding bytes are discarded.
PDS: Partitioned data set. A PDSE consists of a directory and zero or more members,
PDSE: Partitioned data set extended. Exactly same as PDS in many respects. PDSE data sets can be stored only on DASD, not on tape. Interesting thing is the directory can expand automatically as needed. Additionally it has an index which helps to locate the members inside the PDSE faster. SPACE from deleted members are automatically reused in PDSE .
PGP: Abbreviation for pretty good privacy (OpenPGP).
PLATFORM NEUTRAL: The components of FLAM are platform neutral. This means that they work independently from the used operating system. Operating systems can be for example LINUX, UNIX-like systems, WINDOWS® or z/OS®.
PO: Data set organisation partitioned organized.
PS: Data set physical sequential file.
REC: Abbreviation for record.
SEPA: The Single Euro Payments Area (SEPA) is a project to harmonize the way retail payments are made and processed in Euro. The motivation behind it is to make payments in Euro and across the EU as fast, safe and efficient as national payments are now. SEPA shall enable customers to make cashless Euro payments to anyone in the EU, for instance by credit transfer, direct debit or debit card.
see also: SEPA
SIG: Abbreviation for signature
SSH: Secure shell
see also: SSH
SUB CHARSET: A Sub Charset is a partial quantity of a character set. For instance the new identity card issued in Germany (nPa) requires that each printed character - even the diacritical characters - is "composed". It means that they remain in their original form and are not "decomposed" into several bytes. For that reason, the Sub Charset "Latin in Unicodes" with some more than 500 letters is used.
SUBCHR: FLCL can substitute characters that are unsupported in their target encoding by system specific characters (e.g. 0x1A for ASCII or 0x3F for EBCDIC pages) or by arbitrary characters. In the first case, you must use SUBCHR=SYSTEM, in the other you can define your own substitution characters. On z/OS®, the utility iconv is available on the system and replaces all invalid characters by system specific characters, including the BOM sign. Note that it does not stop in contrast to LINUX or WINDOWS® but completes conversion.
SUBSTITUTE: If a character exists in the source code but not in the target code, it will be converted to a converter-defined substitute character.
SURROGATE: The Unicode code space is divided into 17 planes of 65536 code points each. Some code points have no character value, some are reserved for private use, and some are permanently reserved as non-characters. UTF-16 with code points beyond these planes is encoded in 16 bit surrogate pairs (High surrogate and low surrogate), which are in fact replacement characters. UTF-16 surrogate values are illegal in UTF-32. Note that the conversion of UTF-16 strings into UTF-8 byte sequences requires that the High and Low surrogate have to be combined correctly before they are transfered into UTF-8.
SYSTEM TABLE: FLCL makes use of a pre-loaded system substitution table for the transliteration of characters. This is comparable to "translit.h" of iconv under LINUX.
TAB: Abbreviation for table.
TAR: Tape Archiver; Short for Tape Archive, and sometimes referred to as tarball, a file that has the TAR file extension is a file in the Consolidated Unix Archive format. A program or command that can open archives is needed to open a TAR file. Because the TAR file format is used to store multiple files in one single file, it's a popular method for both archiving purposes and for sending multiple files over the internet, like for software downloads. The TAR file format is common in Linux and Unix systems, but only for storing data, not compressing it. TAR files are often compressed after being created, but those become TGZ files, using the TGZ, TAR.GZ, or GZ extension.
TARGET: Trans-European Automated Real-time Gross Settlement Express Transfer System.
see also: TARGET
TXT: Abbreviation for text.
TO-CODE: With few utilities you can convert text from one encoding to another. The TO-Code specifies the output encoding that characters are converted to.
TRANSCRIPTION: To transcribe the expression of a language means by dictionary, to represent it in another writing system rather in that, in which the language is usually written respectively in which it is available in written form. For the term of transcription it does not matter, in which medium the expression is available. Note that the transliteration of an expression is a particular type of transcription.
TRANSLATION: This is the transfer of a (mostly written) and fixed text from the original language into any target language; the process will be also denoted as "Translating".
TRANSLITERATION: To transliterate an expression represented in writing S1 into a writing system S2 means, that the characters contained in the expression are exchanged from S1 to S2 according to a fixed rule. In the simplest case, this can be a table which assigns each character of S1 a character of S2. Frequently, there are complications for the simple case, if for example a single character is assigned to a digraph or vice versa or if a character is mapped in context A onto a specific character, in context B however onto another character. For example: in a payment order from Germany, the name of the receiver must be written explicitly in Latin letters so that a transliteration of the original text with help of a table is required.
UNICODE: The so-called Unicode is an attempt, started in the 90s, to standardize a single character set that eliminates the need for different and incompatible encodings in different countries and cultures. The text should be always readable with a Unicode-supporting appropriate editor. This allows an error free data exchange (for the purpose of readability) also on a global and international level. For this character set, 8 bits (1 byte) are no longer sufficient to for a representation of every possible character. The length of characters encoded in Unicode can be between 1 and 4 bytes. ISO 10646 is a practically equal notation of the Unicode character set called Universal Character Set (UCS).
URL: Uniform Resource Locator
see also: URL
USER TABLE: For character set conversion in FLCL you can define your own user substitution table to transliterate those characters that are not handled respectively replaced by the system table.
UTF-8: The 8-Bit Unicode Transformation Format is the most commonly used encoding for Unicode characters. The term Unicode is used equivalent to UCS. UTF-8 has a central meaning in the global character conversion for internet protocols.
UTF-16: In UTF-16 an encoded byte sequence with a length of 2 bytes is assigned to each Unicode character. UTF-16 is used in Java for internal character sequence representation. UTF-16 is the eldest format of the Unicodes.
UTF-32: UTF-32 (UCS-4) is encoded with 4 bytes and therefore the most simple Unicode representation, as other formats need variable byte lengths for their representation. One disadvantage of UTF-32 is the greater space requirement compared to UTF-8 and ISO-8859 character sets and the missing backward compatibility to ASCII.#
VSAM: Virtual Storage Access Method
see also: VSAM
VR8: Enhanced compression encoding as binary data in FLAM4
ZIP: ZIP is an archive file format that supports lossless data compression.