Hi,
I've been looking for a documentation too, but until then I didn't managed to find one. My solution was to call ASTK to create a template .export file, and then rebuild this file with a script from template.
About lines format, I can guess :
* P stands for settings, followed by the variable and its value (space separated)
* F stands for File, and is aimed at connecting logical units (numbers) with input & output files.
* I don't know about A. Maybe A(rchive), e.g. folders for materials definition and so on...
Format: (I guess...)
> F mess ?ASTER_ROOT?/?ASTER_VERSION?/astest/forma01a.mess R 6
* F : File command
* mess : type = message (indicative, see below)
* ?ASTER_ROOT?/?ASTER_VERSION?/astest/forma01a.mess : the complete filename with path
* File type : R(esult) = Output // D(ata) = Input // C(ompress) = Compress data as gzip(?) files. Cumulative flags (e.g. input + output = 'RD', Output compressed file = 'DC', and so on...)
* 6 = Logical Unit #6 (= message output)
Since messages are always output by Aster on unit 6, I think the "mess" parameter isn't really usefull, but indicative... (as_run.py will execute a "mv fort.6 forma01a.mess" after computation if I remember right)
Some "standard" units are described in commands documentation (see "DEBUT()" for exemple). Otherwise ASTK has a built-in mapping table between unit number and file type. Too bad you can't use it to make a template .export file.
Regards,
Jérôme