Consider the following DCL script, saved as SAMPLE.COM:
\n$ foo = "Sausages"\n$ bar = 20\n$ baz = 5\n$ quux = bar + baz\n$ say "I like ''foo'"\n$ say "bar + baz = ''quux'"\n
(You output the value of a symbol by surrounding it with '' and ')
It produces the following output (stuff I type is blue):
\n$ @sample\nI like Sausages\nbar + baz = 25\n
Now consider the following session transcript:
\n$ set verify\n$ @sample\n$ foo = "Sausages"\n$ bar = 20\n$ baz = 5\n$ quux = bar + baz\n$ say "I like Sausages"\nI like Sausages\n$ say "bar + baz = 25"\nbar + baz = 25\n
See how the values of foo and quux are right there in the output? That's what I'm talking about.
Another example:
\n$ TEMP$FILE = "SYS$SCRATCH:''f$getjpi("","PID")'.TMP"\n$ say ''temp$file'\n
Regular output:
\nSYS$SCRATCH:0000D01A.TMP\n
SET VERIFY output:
\n$ TEMP$FILE = "SYS$SCRATCH:0000D01A.TMP"\n$ say temp$file\nSYS$SCRATCH:0000D01A.TMP\n
See how the call to F$GETJPI() has been expanded to its results inline? (This is why the F$ family of DCL functions are referred to as Lexical Functions, BTW).
This is fabulously useful. I want it. But I'm not sure I can have it.