<<>       ...   this fails to place an ENV file in the spoolfle.
>However, it works OK on 5.0.
>
Yeah.. it comes and goes with each new release!>>

Reminds me of a problem LINKEDIT had back around the A.04.12 through .15
time frame: there were two problems, one where LINKEDIT would blow up on
a LISTXL if it encountered an entry point with a name longer than 80
characters, the other something to do with invalid file generation. For a
series of about 5 consecutive releases, these two problems were in
"non-zero-XOR" mode; every release had one of them, no release had both,
and no release fixed both problems at the same time. We suspected some
type of loss of source control problem, where one party fixing one
problem kept reinstalling the other, but there was never an admission
from HP.

As an aside, what kind of person uses a function name like
 tl_process_set_breakpoint_request$209$tl_attempt_to_mark_breakpoint_in_li
st_file

or
 tl_execute_trandebug_command_shell$155$check_to_see_if_we_have_hit_a_data
_breakpoint

? I type pretty fast, and I'd *never* consider using identifiers like
that!

Steve