[Info-vax] F$GETQUI: the mystery deepens

[Phillip Helbig undress to reply]

In article <pujv45$lm1$1 at dont-email.me>, Stephen Hoffman
<seaohveh at hoffmanlabs.invalid> writes: 

> >> The GQC that is saved for wildcarded F$GETQUI calls is destroyed if you 
> >> run any DCL queue-related command, such as SHOW QUEUE or SHOW ENTRY. To 
> >> avoid this problem, use the SPAWN command to create a new process in 
> >> which to run the DCL commands."
> > 
> > It's not completely destroyed...
> 
> Just as soon as this is considered undefined, any potential behavior 
> becomes entirely possible.  Entirely random, 
> seemingly-predictable-but-not, phase of the moon dependent, we hate 
> Monday, or otherwise.  Anything goes, here.

In the Fortran community, the standard quip is that non-standard code 
can do anything, such as start WW III.

SHOW QUEUE was the obvious quick command to alert me to the problematic
queue.  While the code I posted appears to work (tested on several
combinations of hardware and operating systems), I'm not relying on it,
but have modified it to remove the SHOW QUEUE.  I have the queue name
anyway, so $ WRITE SYS$OUTPUT 'QUEUE_NAME' is enough.