trx proc echo statements

If on your release you can pass arguments at that UPoC position, why not pass a switch then interrogate that switch and echo only if it is on?

Leave the switch on in Test, turn it off for Prod.

If arguments cannot be passed then you can use a Lookup table for the switch using a unique table name base on the IB thread name with something like ‘trxid’ appended. Your proc will need to look for that Table using the thread name and get the switch from the table.

If the TrxID UPoC Configuration allows for expressing arguments (I do not know that it does), then you can either use a positional argument or a keyed list (I prefer keyed lists).

So if GUI indicates args:

• Positional just place a y or n (or 0 1 your preference)
• Keyed List – {DEBUG y}.

I like to code that the value can be any case and I check to make sure a proper value is presented.

Then when your proc is invoked the uargs has whatever you presented.

If you would like an example (not Trxid but another UPoC) of how I do this email me.

Why create a table?  It is superfluous.

If the proc has no startup, simply do this.

In the body of the proc add the following:
if {![info exist DEBUG]} {set DEBUG 0}

The above says you do not want echo statements.  If you do change above to
set DEBUG 1

Then for debug statements:
if {$DEBUG} {echo something}

There are methods I have used for turning debug on or off while the engine is running, but I won’t get into that here.