🚀 go-pugleaf

It's correct: You can't set an "unblock".

INITIATE has to decide to allow or disallow the start of a job
*each time* it is asked for this job. That is
-each time VMBATCH tries to start this job because there are
 no holding conditions and the job is the next one to start
-and each time someone asks for the STATUS of this Job via STATUS
 or LIST (WAITSTAT and the job has no other holdings.

VMBATCH tries this for each job with no holdings that matches
a free worker until INITIATE allows a job.
When no job is allowed VMBATCH waits 90 seconds and tries again.
If something changes in the system VMBATCH tries again.

The way to set a global "unblock" is:
Remember *your reason* of "blocked/unblocked" in a file or GLOBALV
and let INITIATE read this for deciding *each time* it is asked.

We work with INITIATE for years and there were some other problems
around this, for example:

 Why is INITIATE asked (start or status)?
 Will the job really start when INITIATE allows it
  (VMBATCH checks for tape-availibility after INITIATE)?
 Would INITIATE allow another job than the one in question
  (don't run into an endless loop via STATUS)?

Please ask for ideas of solutions when these problems come up.