I think my mention for concerns for *JOB scoped override must have
been off the mark. I just did a quick test, and from the results
seen, I infer I had incorrectly recalled the reverse effect. Seems
that a *JOB scoped override is _later_ in the search order than a
call-level scoped override.?