Best posts made by tom

After a long gestation ProTop 3.3s has arrived!

Highlights include (but are by no means limited to):

• Tips and Tricks on the splash screen
• A startup warning if you do not have -tablerangesize and -indexrangesize set adequately
• A new screen to show the *rangesize calculations (press "1")
• Alternate Buffer Pool indicator columns on table and index activity
• A new "2" data collector to show buffer statistics (some of which are only available in OE 11.7+)
• New "user experience" metrics - this metric reads a fixed number of records and times it
• Modified the startup handling of .pf files to increase flexibility
• Modified UIO to show the current number of locks held per session rather than lock requests/sec (11.7+)
• Generally took advantage of OE 11.7 improvements where available
• Added the option to toggle the client statement cache on/off for a session when selecting a session via # or P
• Added an experimental "task scheduler"

... and lots of other stuff!

Done.

I dunno, you're a pretty shady character...

... and I have now added that capability! Coming soon

I had a bad result with this - it seems to interfere with the icons somehow.

(Yes, that might mean that I am testing on Windows. For the record I regret it already.)

As Paul says every block with data in it must be read - even for an incremental backup. Which is why an incremental backup takes about as long to run as a full backup.

-Bp 10 helps to prevent the entire -B buffer pool getting flushed as a result of a backup running and the follow-on impact that that will have to the hit ratio. During the backup itself though you will still almost certainly see a poor hit ratio.

I'm circling back around to this today and as I poke around in the code I find that I actually started on this and had many of your examples covered back on June 7th -- three weeks before you asked

I have added an "on stop, undo leave" around most of protop.p which I think will take care of this problem.

A new release is imminent - there is really just one more thing I'd like to squeeze in.

The parenthesis are a bad idea. You really want to do it like this:

if "%DLC%"=="" set DLC=D:\Progress\OpenEdge11.7

Portal v4 has a lot of enhancements to stuff like this. Real Soon Now.

Yes, it's true.

I blame Paul. He keeps taking time off instead of "working"...

etc/appsrv.cfg is your friend

The extensive and highly detailed documentation in the header servers as your "user guide":

# appsrv.cfg
#
# type name "query command"
#
#   - names (column 2) are case sensitive!
#   - the "name" field will be substituted for "&1" when the command is run
#
# i.e.
#   ws ws1 "wtbman -i &1 -query 2>&&1"
#
# admin proadsv    "proadsv      -q 2>&&1"      # admin server does not actually use the name field -- but we need a name entry
# ns    NS1        "nsman  -i &1 -q 2>&&1"
# apsv  asbroker1  "asbman -i &1 -q 2>&&1"
# ws    wsbroker1  "wtbman -i &1 -q 2>&&1"

You can then add a resource in the usual manner. Just use -1 for the dbname

Unless you only have one db or you have one that it makes sense to tie the app servers to, you will probably want an etc/pt3agent.resource.cfg file dedicated to your app servers.

Regardless the ptInitDC needs to have AppSrvStatus added to it. If it is a stand-alone app server agent (no db) then you will probably not want any other data collectors running. Something like this (etc/pt3agent.appsrv.cfg):

# pt3agent.cfg
#
# you must restart after changes -- this cfg file is not monitored
#
# pt3agent.friendlyName.cfg will override this config for a friendlyName instance of pt3agent
#
ptInitDC "AppSrvStatus"

As always, you can (and should) test your configuration with the ChUI ProTop before getting too crazy. If you called your resource "appsrv":

protop appsrv

Will fire up the ChUI client. The dashboard and other db centric screens will be null but you can dismiss them if you'd like. The "@" command brings up app server data.

@kynan great!