Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm assuming you want to write custom data, not just the lines executed (which is sadly all you get from PBDEBUG; I've always wanted a custom data write to a PBDEBUG trace, but I've never been able to convince anyone at Sybase to add this to the product). </p> <p><strong>PFC</strong></p> <p>PFC offers a Debug service that does this, but if you haven't built your app with PFC already, it may require a moderate effort to adapt it to your infrastructure. If you've got a PFC-based app, all you have to do is </p> <pre><code>of_SetDebug (TRUE) </code></pre> <p>in the pfc_Open event of the Application Manager (or some other appropriate place), then start peppering your code with </p> <pre><code>IF IsValid (gnv_App.inv_Debug) THEN gnv_App.inv_Debug.of_Message (...) </code></pre> <p>This way, you can just remove the of_SetDebug() to turn off the messaging, without having to remove all the messages' code. (OK, in theory this will slow down your app a little, checking to see if IsValid () all the time.) I even put in code so that I can turn on the Debug Service with a command line option (that I don't tell the users about). That way, I can do this style of troubleshooting at the end-users' workstations (assuming I've anticipated the data I need to write).</p> <p><strong>Other</strong></p> <p>If I'm stuck with a non-PFC app, I'm afraid I'm usually too rushed (read: too lazy) to adapt the PFC debug service, so I just create a global function that does a FileOpen, FileWrite and FileClose on a hard-coded file name, writing the message passed in as a parameter. Then I load my code with calls to this function. In theory you could make this an empty function when it's time to deploy, but I have usually removed all the calls instead.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload