Thanks Daniel. I think I may have to go with a 3rd party compression solution but this is still some really valuable information.

Hi, The Define Deployment Archive form is using a internal function to create a UAR file. This functionality is unfortunately not available on the command line. You could define the ASN setting $RESOURCES_OUTPUT so that it points to the UAR file you want to create and compile the messages from the command line (using the command line switch /mes). The catch here is that you cannot specify the language when compiling from the command line. However, you could create a component that uses $ude("compile"). Here you can specify the library and language of the messages that should be compiled. When you create a small start-up shell that runs this component then you could of course pass the required info about which messages (from which library/language) should be compiled from the command line. So you basically could create your own command line compiler tool with this. Please note that the Define Deployment Archive form will create a text file inside the UAR file (in the sub-directory .\\UAR). This file is called <ArchiveName>.ver (e.g. when the archive is called ARCHIVE1 then the mentioned file would be called ARCHIVE1.ver). This file contains an associative list with the following items:

• Archive=<Name of Archive> ; e.g. ARCHIVE1
• Version=<Uniface version used to created the Archive>; this can be checked using: $concat($item("track", $about), " (", $item("config", $about), ")")
• DateTime=<TimeStamp when the Archive was created>; e.g. the value of "%%$datim"
• Desc=<Additional description for Archive>

The info of the <ArchiveName>.ver will be displayed when running the /who command line switch. Using this info it is of course possible to create the content of the mentioned file and create it by using filedump (placing it into the sub-directory \\UAR in the UAR file). Hope this helps. Daniel