Comment 2 for bug 415049

I researched this a little further, and it appears that there's already a setting that allows you to turn error trapping on in XUP:

GTM>D ^XUP

Setting up programmer environment
 Terminal Type set to: C-VT102

Select MENU OPTION: EVE// XPAR EDIT PARAMETER Edit Parameter Values
Edit Parameter Values
                         --- Edit Parameter Values ---

Select PARAMETER DEFINITION NAME: XUS-XUP SET ERROR TRAP Set error trap in X
UP

XUS-XUP SET ERROR TRAP may be set for the following:

     1 User USR [choose from NEW PERSON]
     2 System SYS [VISTA.GOLD.MEDSPHERE.COM]

Enter selection: 2 System VISTA.GOLD.MEDSPHERE.COM

---- Setting XUS-XUP SET ERROR TRAP for System: VISTA.GOLD.MEDSPHERE.COM ----
Value: YES

XUS-XUP SET ERROR TRAP may be set for the following:

     1 User USR [choose from NEW PERSON]
     2 System SYS [VISTA.GOLD.MEDSPHERE.COM]

Enter selection:
-------------------------------------------------------------------------------

Select PARAMETER DEFINITION NAME:

TRAIN>W $ET
D ERR^XUP
TRAIN>W $ZT

TRAIN>D ^TEST1

$ECODE=,M9,Z150373210, $STACK=2

Want to record the error: No// Y
TRAIN>D ^XTER

In response to the DATE prompt you can enter:
     'S' to specify text to be matched in error or routine name

1 error logged on 12/22/2009
  1) <(DIVZERO)>TEST1^TEST1 13:28:00 [TRAIN] MANAGER:

Which error? >