You hit the point %Boolean s an excellent example  it can be TRUE, FALSe or NULL
in Caché terms: 1, 0, ""

Your example ^CODE("TNO","BIO",291,"AKI"))  is partially misleading in that sense that a global subscript can NEVER be ""
while the content of $LB() can be $LB(1,2,"",4)  or $lb(1,2,,4)  here you find your  "undefined" again,
similar to NULL in SQL (which is a different story)

there is a major difference between 1) and 2)

1) is also true if you have SET ^CODE("TNO","BIO",291,"AKI"))=""

this information is stored in ^|"%SYS"|SYS("Security","ApplicationsD")

you could extract it by MERGE ^mySAVE=^|"%SYS"|SYS("Security","ApplicationsD")
and then do any export of the global

Thanks!
One headache less in the discussion about the "right" way to write code.
+a tiny piece for "creative freedom".   

Procedureblock =1 

means ALL local variables except call parameters and %variables move to stack
and return when you return from your method (=procedure)

see Summary on Local Variable Scoping  for more 

this memory operation is not free but nothing to get a headache upon

Of course, if your utility classes are all ABSTRACT it is pure code.  As any .MAC, just easier to read.
OREF is just a special data type (object pointer) and not better or worse than any other variable.

I 'd guess variable scoping and procedure block has much more (microscopic) influence on performance.

My personal preference is to have only code tightly related to stored date in "object"-classes.
Anything else outside that is not only related to this class.

Use PuTTY instead

setting your terminal width to 132 will show the rest

I use * X for linuX aiX uniX solaris and similar real OS.

on Win* you just have to click on start caché in the cube

BTW you can see the Content of Journal also from System Mgmt Portal 

Sorry Kevin,
I concentrated on CPIPE.

my code was Written for a FOR p=1:1:254 loop to find unused IP addresses in a specific subnet.

in your case, ping might be something like  set ping= "ipconfig"

$system.SQL.DAYOFWEEK(dateexp) is probably easier to use
dateexp 
An expression that is a logical %Library.Date value, %Library.TimeStamp, %Library.PosixTime, or an $Horolog value.

The returned values represent these days: 1 - Sunday, 2 - Monday, 3 - Tuesday, 4 - Wednesday, 5 - Thursday, 6 - Friday, 7 - Saturday
The Caché default is that Sunday is the first day of the week.

Journal is definitely a valuable source.
BUT: It documents Global changes. It doesn't know about objects nor rows in tables.