Group Details Private

administrators

 
  • RE: OE 12 support

    pt3.141x (the pre-release branch of pt3.141) has the changes to support oe12.

    I also added back the "4" hotkey.

    Because it is an "x" release you need to explicitly ask for it when doing an update. i.e.

    bin/pt3upd.sh pt3.141x

    There also may be multiple releases in an "x" branch so the "as of" timestamp is worth noting.

    Lastly, I also (sneakily) patched the pt3.14 release a week or so ago. If your "as of" date on that is in May rather than March then you should also have the oe12 changes (but not the "4" hotkey).

    posted in Using ProTop
  • RE: Configure the User Information Viewer

    The "3" key got re-purposed as "server report". It now creates rpt/friendlyname.servers.rpt.

    "4" is currently unassigned.

    The documentation team seems to have neglected to mention this in the release notes - probably because the programming team was too busy goofing around to bother telling them 🙄

    I'm thinking that the statement cache should automatically appear or disappear based on whether or not it is enabled for a particular client.

    posted in Using ProTop
  • RE: OE 12 support

    @rob-fitzpatrick what version of PT was that from?

    posted in Using ProTop
  • RE: Happy pi day - pt3.14 has been released!

    Trust me, I had that idea long before Rob mentioned it 😉

    posted in Announcements
  • RE: Happy pi day - pt3.14 has been released!

    OMG Rob don't give him ideas. pt3.14159265359...

    posted in Announcements
  • RE: Happy pi day - pt3.14 has been released!

    @rob-fitzpatrick I am strongly considering it.

    I like that you said “if” 😁

    posted in Announcements
  • New killprosession.sh in pt3.14

    Hi all,

    The latest version of killprosession is available as part of the pt3.14 download from https://wss.com/progress-openedge-monitoring-with-protop/.

    New features:

    1. Added a force flag (runs kill -SIGFPE)
      If the user selects -f and the script determines that no DB files are open AND no DB shared memory segments are attached, it will proceed to send the SIGFPE signal.

    CAVEATS:
    a) On AIX, you need to specify DBFILESYSTEM=/<DB file system> in $PROTOP/bin/localenv. This is because lsof on AIX only returns the file system name and not the full file name. If you have multiple DBs on multiple FS then this won't work as expected.

    b) killprosession only checks shared memory segments of DBs in $PROTOP/etc/dblist.cfg.

    c) Only lightly tested on HPUX as that operating system is becoming mighty scarce

    1. Delivered in ECHO only mode
      The script is delivered with the line "ECHO=echo" uncommented. This means that lines like "$ECHO kill -s INT ${PID}" will only echo the kill command and not execute it. This mode is clearly indicated in the Usage and when running the script. You'll see:
    $ /usr/local/protop/bin/killprosession.sh 48365686
    
    pk4939 48365686 pts/27 _progres -pf /usr/local/etc/params.m.pf
    
    ECHO ONLY MODE is on. Comment ECHO=echo in script.
    
    USE AT YOUR OWN RISK. THERE IS NO 100% SAFE WAY TO KILL A SHARED MEMORY PROCESS
    
    Please confirm the kill of this session (y/n):
    

    and same in the usage:

     Usage: /usr/local/protop/bin/killprosession.sh [ -q ] [ -f ] [ -v ] pid1 [pid2 pid3 ...]
           -q  quiet. No prompts
           -f  force. Will execute a kill -SIGFPE if lsof and svmon/pmap seem clear. DANGEROUS !!
           -v  verbose. Generate verbose output
    
    ECHO ONLY MODE is on. Comment ECHO=echo in script.
    
    1. Added a verbose flag
      If you want to see every little thing that killprosesson does as it does it, add the -v flag. This is particularly useful in echo mode.
    posted in killprosession
  • Happy pi day - pt3.14 has been released!

    Go to your usual website and grab a download!

    Release highlights that I remembered to add to the notes:

    1. Added a column to the "s" (Remote Server IO) screen to show the -S port that the server is associated with.

    2. Also changed the "type" to reflect ABL, SQL or BOTH.

    3. Fixed some issues with the occasional unexpected display of negative numbers. These sometimes occur when certain integer fields overflow or when an instance of a metric "changes hands". That is annoying but not worth getting too excitied about -- the fix is just to actually show "-" rather than letting the error (74) occur.

    4. Made "zippy" less cowardly by adopting the standard mkFlag() routines.

    5. Added a DLC age field to report the number of days old your Progress release is.

    6. Added code from Mike at Consultingwerk to add a Windows registry entry recording the install directory. This simplifies integration of ProTop with 3rd party tools such as the Smart Component Library Desktop. (Only works with oe11+.)

    7. Further simplification to enabling session temp-table information aka lib/ttinfo.p, by removing the need to modify lib/ttdebug.i and by renaming the environment variable from "PTDEBUG" to "TTDEBUG". Now you only need to set the -tt* parameters in etc/protop.pf and TTDEBUG=yes in bin/localenv.

    8. Added LatchReq (latch requests) and Lat2LogRd (latches to logRd ratio) to the dashboard.

    9. Added con_BlockRec and con_BlkOther to distinguish between connections blocked on record locks vs connections blocked by internal resource contention. Record locking issues are generally coding problems while resource contention is more of a DB and OS tuning situation.

    10. Modified "programmer mode" (control-p) to toggle back and forth and to display "programmerMode" among the indicators found in the upper left part of the screen when it is enabled.

    11. Modified the -*rangesize checking routine to write suggested values to $TMPDIR/$FRNAME.range.pf to make it easier for people to copy them to their startup parameters.

    12. Added SKIPLGSCAN=yes to bin/localenv.x if you'd like to skip the scanning of the .lg file at startup. Post oe11.5 it should be redundant, prior to that the impact might be that some startup parameter values may not be available any other way.

    13. Replaced the conversion of an internalProDataSet to JSON/XML when passing data to the UI (lib/dynscreen.p) and the subsequent re-conversion back to a ProDataSet. This eliminates the need for the ptdefs/*.xsd files, improves UI performance somewhat and reduces memory usage.

    14. Enhanced the startup debugging messages for protop.p (the interactive client) to help to identify the source of startup issues (if there are any). You can change this at any time before or after starting a session (even while running). For instance:

      echo 3 > tmp/protop.s2k.dbg   
      

    will set the debugging level to 3 (which is more than enough for most purposes). You must delete the tmp/protop.*.dbg file to return to the normal default debug level.

    You probably should not set this unless you have a craving for annoying debug messages.

    1. ESC-D will allow the debug level to be changed from within a session. (I have no idea if that works with Windows -- DELETE-WORD is the keyfunction used.) This will NOT be persisted but it may be useful if change the startup debug level as described above and do not want to modify the .dbg file for some reason.

    2. Removed the "top blocker" sub-screen from blocked users because
      a) it was wrongly labelled -- it was actually the blocked session's stack and
      b) the blocker info was added to the notes some time ago so the need just isn't there and
      c) it takes up a lot of space for no good reason.

    3. Improved interoperability of bin/syncio.sh and bin/maintenance.*

    4. Released as pt3.14 in honor of pi day. Plus I was running out of letters to mark minor releases with 😉

    posted in Announcements
  • RE: Deprecated VSTs

    Something like that will probably occur. I need to start mucking about with oe12 now that it is actually available.

    posted in Roadmap
  • Introduction

    Are you using killprosession? Have questions? Suggestions? This is the place.

    You can get the latest version of killprosession by downloading ProTop at demo.wss.com. In Europe you can use protop-europe.com and in APAC dashboard.protop.com.au.

    Paul

    posted in killprosession

Looks like your connection to ProTop Community was lost, please wait while we try to reconnect.