TRACELOG for PowerBuilder application

What is a tracelog?

The tracelog (n_trace) is a Powerbuilder object that allows:

• Catch all sql errors (with object name and line information)
• Catch print messages from server
• Organize debug logging for your applications (online, text file, html)

Restrictions

Today only Sybase ASE and Microsoft SQL servers are supported.

Download

n_trace object prototype

• of_setTitle (string s)
  Sets the title of the Tracelog window, and the tooltip for the icon in the tray.
  returns none.
• of_log ( string as_object, string as_info, long al_mask)
  Adds the message into a log.
  as_object the object name that sends a message.
  as_info the message test to add into the log.
  al_mask the message type defined through msg_xxx members of n_trace.
  
• of_log (powerobject apo_object, string as_info, long al_mask)
  The version of the function with first parameter defined not as object name but as object itself.
  
• of_dbHandlerSet (transaction atr)
  Installs the message/error handler for Sybase ASE (SYC) or Microsoft SQL (MSS) servers.
  If you want to install message handler, you should do it after "connect" command. If the message came from the server it will be automatically added into the tracelog with "sql error" or "sql print" mask (type).
  
• of_dbHandlerDel (transaction atr)
  Removes previously installed message/error handler.
  Must be called before "disconnect" command.
  
• of_debug (powerobject obj, string s)
  identical to call: n_trace.of_log( obj, s, n_trace.msg_debug )
• of_info (powerobject obj, string s)
  identical to call: n_trace.of_log( obj, s, n_trace.msg_info )
• INSTANCE VARIABLES:
  privatewrite long msg_syserr     = 1      //sys error   
  privatewrite long msg_sqlerr     = 2      //sql error   
  privatewrite long msg_sqlprint   = 4      //sql print   
  privatewrite long msg_sqlpreview = 8      //sql preview
  privatewrite long msg_procreturn = 16     //proc return
  privatewrite long msg_debug      = 32     //debug       
  privatewrite long msg_info       = 64     //info        
  privatewrite long msg_create     = 128    //create      
  privatewrite long msg_destroy    = 256    //destroy     
  privatewrite long msg_open       = 512    //open        
  privatewrite long msg_close      = 1024   //close       
  privatewrite long msg_click      = 2048   //click       
  privatewrite long msg_dblclick   = 4096   //dblclick    
  privatewrite long msg_keydown    = 8192   //keydown     
  privatewrite long msg_keyup      = 16384  //keyup       
  privatewrite long msg_message    = 32768  //message     
  privatewrite long msg_datawindow = 65536  //datawindow  
  

Screenshots

To access the log you need just click on the icon in the tray:

You will see the log:

At any time during your application execution the developer able to change the mask (types) of messages that he want to see in the log:

All messages from the start of application will be redisplayed according to the selected mask.

To see the full message text, doubleclick on it or press "Enter":

The log window is enabled; even you have a PowerBuilder system error or application crash. Of cause, If PB application was terminated, then tracelog will be terminated also, because it is the same process.

Trace Log Configuration

All configurations are stored in tracelog.ini file: