On Sat, 7 Jan 2017, Sven Schreiber wrote:
 So this is an "embarassingly trivial" type of parallelism,
where 
 each worker gets its own gretlcli instance/process. 
As I've indicated, IMO either MPI or simple shell parallelism is the 
way to go, but I've experimented with coercing "launch" into doing 
what you wanted (on Linux, I'm not in a position to test in Windows 
right now) and it can be done, though redirection of the child's 
output doesn't seem to work so you have to use "outfile".
<parent>
print "parent started"
launch gretlcli -b taketime.inp
print "parent done"
</parent>
<child>
outfile child.out --write
print "child started"
loop 1000 -q
   matrix X = mnormal(500,500)
endloop
print "child done"
outfile --close
</hansl>
If you run parent in gretl you get the "parent done" message right 
away, and taketime.inp works on in the background to produce 
child.out.
This forking stuff is fiendishly complicated and also differs 
radically by platform, which is one reason for recommending software 
that really knows what it's doing in this department, such as MPI or 
the respective shells.
Allin