_______ _ _ _ | _____| | | /\ | \ / | | | | | / \ | \ / | | | | | / /\ \ | \ / | | |____ | | / / \ \ | |\ \ / /| | | ____| | | / / \ \ | | \ \/ / | | | | | | / /______\ \ | | \ / | | | | | | / /________\ \ | | \/ | | | | | |_____ / / \ \ | | | | |_| |_______| /_/ \_\ |_| |_| INSTALLATION OF FLAM V5 ON AIX ------------------------------ Frankenstein Limes(r) Infrastructure Version 5 Copyright (C) limes datentechnik(R) gmbh All rights reserved ---- limes datentechnik gmbh Louisenstrasse 101 61348 Bad Homburg / Germany Tel.++49 (0)6172-59190 Fax ++49 (0)6172-591939 eMail support@flam.de https://flam.de https://limesdatentechnik.de ---- PREREQUISITES ------------- None. For commercial usage and compatibility with previous FLAM V4, a separate package containing a license is required. Without this, all conversions are limited to files smaller than 1 MiB. DESCRIPTION: ------------ The following package formats are supported: * TAR INSTALLATION ------------ If you don't want to or cannot use one of the packages, you can use the tarball version. Just extract it with a command like this: ---- cd / gunzip /flam-X.X.X-X-$arch.tar.gz tar -xvf /flam-X.X.X-X-$arch.tar ---- where "X.X.X-X" must be replaced with the version number and "$arch" with the name of the used platform, either ppc or ppc64. After extracting the tarball with root permissions in the root directory '/' you will find everything in the directory '/opt/limes/flam' This is the same directory layout as if installed from one of the packages. Just make sure '/opt/limes/flam/bin' is in your 'PATH' variable and '/opt/limes/flam/lib' is in your 'LD_LIBRARY_PATH' in order to start using FLAM. To be able to use the provided man pages with the man utility, set the variable MANPATH to contain the path '/opt/limes/flam/doc/man' ---- export MANPATH=/opt/limes/flam/doc/man: ---- The position of the colon determines if this directory is searched before or after the standard manpath. See manpath(5) In case you want to put the FLAM directory somewhere else, extract the tarball to where you want it to be. To install the license package: ---- cd / gunzip /flamlic-X.X-$arch.tar.gz tar -xvf /flamlic-X.X-$arch.tar ---- where "X.X" must be replaced with the version number and "$arch" with the name of the used platform. Known install issues: --------------------- none First steps after installation: ------------------------------- The config file of FLCL is managed with its builtin functions. It is read from FLCL at the beginning and if it was changed during its execution it is overwritten. Without changes, nothing is written. Therefore a config file will only exist if an FLCL command was executed which changed a default setting. The first line of output of FLCL shows the used config file. If the environment variable 'FLCL_CONFIG_FILE' is not set, FLCL looks for a file with the name '.flcl.config' in the current directory. If it is not found there, it looks in the user home directory. If the environment variable 'FLCL_CONFIG_FILE' is set, it uses its value as the filename. It is advisable to at least set the environment variable 'LANG' appropriately to get the correct character conversions. For example: ---- flcl setenv LANG=de_DE.CP1252 ---- To get information about the active license execute ---- flcl license ---- FLCL has a lot of documentation builtin. First of all, when called without any arguments a list of all commands and buitin functions is given. To view a list of all possible LEXEM and GRAMMAR on can execute ---- flcl lexem flcl grammar ---- To get help for an individual command e.g. CONV ---- flcl help conv ---- To get help for the READ overlay of the CONV command ---- flcl help conv.read ---- To get a part of the manual, e.g. for the input object of the XCNV command ---- flcl help xcnv.input man ---- or for the syntax, here with all levels ---- flcl syntax conv.read all ---- The dot notation allows to get specific help for each object, overlay and single parameter of FLCL. All condition and reason codes are shown with ---- flcl errors ---- Further buitin functions allow e.g. to activate TRACE messages, manage properties and environment variables, generate the complete documentation, ... With "flcl manpage" it is possible to view the manpage of each command or builtin function. ---- flcl manpage setprop ---- All config settings are done for a specific owner (default owner is "LIMES"). This might be used for separation of clients. The GUI FLCC allows to create and edit property files and FLCL command lines and provides access to all documentation. Examples: --------- To decompress a FLAMFILE: ---- flcl conv "read.flam(file='flamfile.adc') write.binary/text/record(file='output.dat')" ---- To compress a file with ADC: ---- flcl conv "read.record/text/binary(file='input.dat') write.flam(file='flamfile.adc')" ---- Compatibility with Version 4.3: ------------------------------- To be compatible with the older flam4 utility the default record format can be adjusted by setting the properties: ---- flam4 CHGPROP flam outrecformat=stream inrecformat=stream ----