🚀 go-pugleaf

>We observe that when jobs are being submitted to VMBATCH very rapidly,
>completion of worker initialization is suppressed.  In an example case I
>followed today, a user ran an exec that submitted 76 jobs within 15
>minutes.  Jobs that were begun on workers during that time, and even for
>a while after, got as far as having the worker autologged and the
>SERVICE macro entered, but the SERVICE macro did not complete for a very
>long time -- as much as 30 minutes.  During this time the jobs were
>simply shown as being in initialization status.  It eventually got to
>the point where there were no workers actually running jobs.
>
>We see this as a serious problem.  Systems Center's response is that
>it's just the way it's designed, and they aren't particularly inclined
>to change the design.  Does anyone else see it as a problem?
>
>------------------------------------------------------------------------
>Kent Fiala <snoklf@vm.sas.com>
>SAS Institute Inc., Cary NC 27513 USA                 919-677-8000 x6646

Oh good grief, yes this is a problem!   The system should either run
the jobs or refuse to accept further requests.  (And one can envision
all sorts of user-friendly options, such as prompting the user if the
submission is interactive, or at least adding Wait/Nowait a la VMTAPE.)

I'd ask to speak to the superior of the support rep you're dealing with.

/Rich Wiggins, Michigan State U