The FLAM client offers the element interface, the record interface, and the byte interface (access method) on the local system. It is used by the FLAM subprogram and utility to transfer files, streams, database tables, or other data sets to FLAM. This is done by compressing, encrypting, and signing the data in parts (segments) via the FLAM kernel on the local machine. After that, data can be written either locally by the client or remotely (IP, MQ, ...) via the FLIES server into a FLAMARCHIVE (file, database, cluster (VSAM/ISAM)). From there they can be read again, modified, deleted, or inserted while care is taken that only Segments actually needed are being exchanged. Network-capability was first introduced with FLAM version 5.
Among others, the FLAM client can be used for moving compression workload from the central systems to remote ones.
The FLAM client (just as the FLIES server) supports various communications protocols. Currently available is the so-called IP-native implementation. It requires any network link capable of IPv4 or IPv6.
- IP-Secure (SSL/TLS-connection)
- MQ-Series (IBM®-Middleware)
- SSH (RFC425x)
The latter 3 features are still under development as part of the new FL5 infrastructure. If you would like more information - please do not hesitate to call us.