Now let’s get into something slightly more complicated. DBSLOG to help find out what’s going on when a session “hangs” I’ve placed a lock on a record in the item master. The bottom of the dbs.log looks like this: —— QPS Input Row ——- Bind :1 : string : [0x8185d20] ‘` ‘ —– DBMS Where [...]

Now you’ve generated your DBSLOG=1570 output let’s look at what you’ve got: DBSLOG is nice enough to tell you in your logfile exactly what flags were used to generate it. <6692> 2009-11-09[20:17:44]: Logging started mode 01570 —- LOG ROW INFO [0000010] —- —- LOG TABLE INFO [0000020] —- —- LOG DB INFO [0000040] —- —- [...]

DBSLOG is my favorite toy. It looks all communications between the driver and the database. I’m mostly familiar with the Oracle driver, so that’s what i’ll show here. Other drivers look different in DBSLOG. Here are the options that can be sent to DBSLOG: 00000 – Turn DBSLOG tracing off 00001 – Display data dictionary [...]

Now that you know where your object is located. You probably need some more information about it. Before we saw that the object for my item master oitm0101 was located here: /apps/baan/bse/application/tiB40U_c4_stnd/otiitm/oitm0101 Now if we want some info we can use one of three commands what /apps/baan/bse/application/tiB40U_c4_stnd/otiitm/oitm0101 – or (if you’re fancy) – what `explode6.1 [...]

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 [...]