@tom said in OE 12 support: 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). That explains it, I got the error from the original March version.

@tom said in Configure the User Information Viewer: I'm thinking that the statement cache should automatically appear or disappear based on whether or not it is enabled for a particular client. That's reasonable. Though I'd still like to be able to turn the individual browses on or off. It would also be nice to have the act of turning off User Information Viewer revert to a view that is more useful, as opposed to just removing the header section. E.g. if the act of going into it cached the current list of displays (e.g. d, t, i, u), so they could be restored when u is pressed again. Food for thought.

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

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

Just came across a case with a new CentOS VM where "time" wasn't installed. syncio.sh didn't do much of anything, just exiting pretty much immediately. which time didn't find a time command. Upshot: I installed time and then syncio.sh worked as expected. The code that sets TIMECMD may need to be a little more robust.

@kynan great!

Zing!

@rob-fitzpatrick Yes, that is correct.

I would like to see historical Checkpoint information on the portal. It would help to verify changes to biclustersize

Rob is correct, and ProTop already has the equivalent alarm: it's called the heartbeat. If monitoring is NOT running OK for any given monitored resource, the web portal generates an alert saying "HEY! I haven't heard anything from the ProTop agent for siteName.ResourceName for the past x minutes!!". This is much more interesting than getting an hourly or daily "Everything is OK!" email as you may not notice if you miss one or two or five. The default heartbeat check interval is 1200 seconds. After that, a heartbeat alert is generated. Note however that you must configure in ProTop where your heartbeat alerts are sent. They can stay in the web portal, they can be sent to an email list, or they can be sent to an emergency "pager" list (typically to your mobile phone). The various web portals around the world also ping each other via email to make sure that outbound alerting is always working. if one of the portals fails to send emails for more than a few minutes, one of the other portals alerts our devOps team so that we can investigate.

@jdpjamesp (Somewhat off-topic): That KB list is pretty close to a list of my own that I've been updating off and on over the years. I stopped updating mine when, thankfully, I got rid of my last WG license. However to me this looks questionable, re licensing requirements for TDE: OpenEdge Enterprise RDBMS and OpenEdge TDE or alternatively Advanced Enterprise Edition RDBMS available since OpenEdge 11.5 (for Production) OpenEdge Development Server (for Application deployment) I don't see what OE Dev Server has to do with TDE. It is the development version of App Server, is it not? Same goes for the footnotes for MT and TP. Also, aren't -napinc and -napstep decommissioned?

Understood. Enhancement added to our TODO list.

YES. Or maybe right-click - copy the whole thing to clipboard.

It is ugly and annoying but it should be harmless. The issue has been fixed in the next release.