Ok, thank you Alfonso. The solution of running conn_batch() twice is quite suboptimal if the use-case is to drive conn_batch() by building the BATCH structure with functions that read parameters from a JSON specification file - in that case, the function to build BATCH.Setup would have to return the instruction to run conn_batch twice, and somehow handle the update of the Setup struct for each run, to pass the descrip fields as different subfields.
Is there any plan to fix the underlying problem by naming the fields differently?
Is there any plan to fix the underlying problem by naming the fields differently?