Ocean-XL docs and controlling parallel jobs

In the past when faced with needing to run a large number of simulations on a block (different analysis types, different corners, different sets of controls or bias conditions, etc. I have used some external scripts to launch N ocean jobs in parallel to make the full set run faster.  When the individual sims are smaller it is quite effective to run many in parallel.  However, my external scripts were a hack for sure and then afterwards, I had to assemble logged data points into waveforms using other tools.

Ocean has had a non blocking mode for a long time but I've never quite understood how to use it, especially if I need to build up a waveform with data points from multiple runs.

I've not found a good Ocean-XL reference. Is Ocean-XL really the place to look for more efficiently running jobs in parallel?  Saving a script from an active ADE-XL state is somewhat of a start but I don't really understand how the parallelization jobs works there.

I have an example of a call to ocnxlOutputOceanScript() but for that I have been unable to figure out what information may be passed into that ocean script.  For example,

ocnxlOutputOceanScript( "/tmp/my_ocean_script.ocn" ?name "Test_Ocean" ?plot t)

inside of /tmp/my_ocean_script.ocn, how do I access the simulation data?  Are results already opened so I can just do selectResults()?  The difference between not specifying ?evalType and using ?evalType 'corners is not really clear to me.

ADE-XL feels close but a bit clunky in some cases.  Here are some examples:

1)  simulation where I need to run a baseline sim first for calibration followed by a number of simulations on the calibrated circuit

2)  simulation where there is more complicated post processing involving results from multiple simulations.  For example, produce a waveform made of 1 x-y point from each of N simulations and plot the derivative of this waveform.

3) simulations with specifications that only apply for some conditions.  For example a VCO with a required tuning range.  The spec is Fvco > F_upper @ tuning voltage = max tuning voltage and Fvco < F_lower @ tuning voltage = min tuning voltage.  Currently the only ways I see to set this is either create a copy of the test (not fun because now if I decide I need to change a PSS parameter or something I have to propagate this to multiple copies of the same basic sim) or put in hacks in my expressions based on VAR().

Straight up ocean with for and foreach loops can do all this fairly easily but is decidedly single threaded which is quite inefficient if a large server is available.

Any comments?  Is there a good Ocean-XL manual I should be looking in? 

-Dan