David M Kerr

dbgobj is one of the best bshell debugging options you have available to track down a problem.

It will give you the actual path to an object: this is essential if you have multiple VRCs to find out the VRC that the bshell is using (not always what you expect, and not always the same as explode6.x)

To execute this trace you add -dbgobj to your bshell. it's best to add two other debugging commands to your bshell so you can specify your logfile:
-keeplog and -logfile

In Unix that would look like

ba6.1 -- -dbgobj -keeplog -logfile /tmp/bshell.log

In Windows you add it to the command line

Command: -- -dbgobj -keeplog -logfile c:\bshell.log

The output file will look like this:

---------------------------OBJECT HEADER--------------------------------
B:0000005:::(00001):Object      = otiitm0101
B:0000006:::(00001):Pathname    = /apps/baan/bse/application/tiB40U_c4_stnd/otiitm/oitm0101
B:0000007:::(00001):Magic               = [_bic_dll_]
B:0000008:::(00001):relno               = 61
B:0000009:::(00001):obj_revision        = 1
B:0000010:::(00001):object_flags        = 10

The key to look at is the path to the object. you can see here that I've got object otiitm0101 Installed in tiB40U_c4_stnd which is my standard update VRC for PMC. So we know that I haven't customized my item master (thank goodness)