_______ _ _ _ | _____| | | /\ | \ / | | | | | / \ | \ / | | | | | / /\ \ | \ / / | | |____ | | / / \ \ | |\ \ / /| | | ____| | | / / \ \ | | \ \/ / | | | | | | / /______\ \ | | \ / | | | | | | / /________\ \ | | \/ | | | | | |_____ / / \ \ | | | | |_| |_______| /_/ \_\ |_| |_| INSTALLATION OF FLAM V5 ON WINDOWS ---------------------------------- 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 ------------- Windows 7 or newer 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: ------------ On Windows, FLAM V5 is installed using an MSI package. Just double click on the MSI file to execute it and follow the instructions. On the command line, the installation can be done with the command: ---- msiexec /i flam-X.X-.msi /lv install.log ---- This will write verbose log messages of the installation into the file install.log. To remove FLAM, you can use the uninstall function from the Windows Control Panel or execute the command. ---- msiexec /x flam-X.X-.msi /lv uninstall.log ---- to install the license package: ---- msiexec /i flamlic-X.X-.msi ---- In the commands above "X.X" must be replaced with the version number and "" with the name of the used platform (i386 or x86_64). In order to use the Micro Focus support, it is needed to run the script ---- installMF.bat link ---- once before it can be used. It provides hard links of the DLL matching the name of each entry which might occur at first in a program. If the hard link causes trouble, execute the script without the link argument. This way copies are made instead. Note: "" is the folder path containing the FLAM libraries. ENVIRONMENT Variables: ---------------------- Make sure the bin folder from the installation directory is in your %path% variable in order to start using flam. For Micro Focus Enterprise Server support you might want to set ---- FLAM4MF=yes ---- within the ES instance. See FL4REC documentation. If automatic character conversion is needed the encoding should be set, e.g. ---- FLAM4MF=IBM-1047 ---- to use the US EBCDIC encoding. If the encoding string begins with 'IBM', big endian is assumed and binary values will be byte swapped. In case of an error a trace file can be activated with ---- FLAM4MF_TRACEFILE=flam4mf_trace.txt ---- To support static and dynamic system variables, the two filenames below are read to the environment. The second file name can be used in conjunction with the JCL User Exit to provide the dynamic system variables. ---- FLAM4MF_STATIC_SYSVAR=~/.sysvar.txt FLAM4MF_DYNAMIC_SYSVAR=.sysvar.txt ---- An additional alternative to define system variables in the MF EDZ environment is the DD name SYSVAR. For example, this job card can be used to define the JOBNAME as inline encoding. Known Micro Focus issue: ~~~~~~~~~~~~~~~~~~~~~~~~ Functions passing pointer adresses, for example flmloc(), only work if the Cobol compiler directive AMODE is NOT used. With AMODE, mainframe pointers are used in the Cobol program which cannot be converted. FLAM V4 ------- If FLAM V4 is needed, it must be installed separately from the flam4 MSI file. The installation procedure is the same. Note: A commercial license is required to use it. Known install issues: --------------------- If the error message ---- "Installation directory must be on a local drive" ---- is shown, the installation can be done with the command ---- msiexec /i flam-X.X-.msi WIXUI_DONTVALIDATEPATH="1" ---- This will skip the faulty path validation on some older systems. If the error message ---- "Warning 1909. Could not create Shortcut FLCC Frankenstein Limes Control Center.lnk. Verify that the destination folder exists and that you can access it." ---- is shown, you are most probably on Windows XP and need to create the Shortcut manually. And you should do what the message says: Verify that you can find and use FLAM. If the destination folder was not modified during installation it is in 'C:\program files\limes\flam' Operating systems older than Windows 7 might need an update of the system install service program in order to use our schema 200 MSI package. If this cannot be done, a schema 100 package can be provided on request. Or the 32bit MSI package can be used, as this is a schema 100 package. 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 ----