Fellow list members,

My latest tasks have brought forth a few questions that I'd like to bounce
against the collective knowledge base:

1.  Does anyone know of a way of 'directing' programs executing in the
posix domain (I'm referring specifically to 'touch.hpbin.sys') NOT to
enable the default 'interrupts'.   I have a home grown utility that
'spawns' a CI process and 'feeds' it with requests to invoke
'touch.hpbin.sys' and the whole process 'hangs' while 'touch' is trying to
enable some 'interrupt traps' (see stack trace).  Additional 'user' inputs
seem to somehow 'allow' 'touch' to proceed a few steps and then again hang
until some further user input, etc.....

******(And tracing pin 230 in glance):
 Wait :       TERMINAL WRITE      | Compatibility Mode %   ............<0%

 Procedure Trace for Pin  230 is:
   PC=a.0016a70c enable_int+$2c
 NM* 0) SP=418383b0 RP=a.014782ac
 notify_dispatcher.block_current_process+$324
 NM  1) SP=418383b0 RP=a.0147a734 notify_dispatcher+$264
 NM  2) SP=41838330 RP=a.0019ac20 wait_for_active_port+$ec
 NM  3) SP=41838230 RP=a.0019b8a0 receive_from_port+$534
 NM  4) SP=418381b0 RP=a.0033eefc extend_receive+$494
 NM  5) SP=41837fb0 RP=a.0032d91c rendezvousio.get_specific+$158
 NM  6) SP=41837e30 RP=a.0032dc80 rendezvousio+$1d8
 NM  7) SP=41837d70 RP=a.00332e4c enable_term_signal_char+$1ec
 NM  8) SP=418379f0 RP=a.00b2fbac enable_device_interrupt+$c4
 NM  9) SP=41837870 RP=a.00b2fde4 enable_interrupt+$1d0
 NM  a) SP=418377f0 RP=a.00b33f0c config_ssbrk_interrupts+$170
 NM  b) SP=41837730 RP=a.00e41a04 XCONTRAP+$4e8
 NM  c) SP=418376b0 RP=a.00e414e8 ?XCONTRAP+$8
          export stub: 924.0000f50c
 NM  d) SP=41837430 RP=924.000125d8
 NM  e) SP=41837330 RP=924.0000dbbc
 NM  f) SP=418361b0 RP=924.00000000
          (end of NM stack)

2.  While working on the same issue I found out that another conflict was
being caused by the 'touch' inheriting the '$STDERR' file of its parent CI
process, which in this case was defaulting to, I assume $stdlist.  Further
investigation showed that a 'new' item exists for the 'createprocess'
intrinsic (item #14) that can be used to 'set' the $STDERR file.   Does
anyone of the sites that have migrated to 6.X know if the 'run' or 'implied
run' commands have been enhanced to allow the 'stderr' re-direction?

3.  On occasion I perform some remote support on an HP967SX located in
another state.  The users have been complaining, especially around
'financial month end' about the poor response (in terms of length of time
for jobs to be processed), and their management are willing to examine the
available options.

Keeping in mind that they'd like to stay within the same tier, in order to
avoid the big upgrade cost of a certain vendor, can anyone offers some
suggestions.

Regards
Paul Christidis