RE: IBM i Access for Web - Not yet a replacement for Navigator -- MIDRANGE-L

MPG is a great product, I love it and use it, however, it can only use data
collected based on the tooling that IBM has provided into the LIC/Storage
Management/IBM i etc., so its comparison would be performance data
investigator, not management central monitors. The question here is the
management central monitoring functions that are real time and have the
ability to cause an event to occur. That functionality is widely used and
many folks rely on it. Are hooks there to roll your own monitors, sure, but
the management central monitors have been around for some time and do a
yeoman's job of monitoring the system. The CAAC and LUG should be looking
at getting IBM to replace Management Central with something that is
delivered in IBM i Navigator. When, that's a different question.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Wednesday, August 19, 2015 2:57 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: IBM i Access for Web - Not yet a replacement for Navigator

V6R1 MTU

System i Navigator removal of support for memory-resident database monitors
next release
V6R1 will be the last release for System i Navigator and Systems Director to
provide support for memory-resident database monitors. Memory-resident
database monitors are identified as type Summary in the SQL Performance
Monitors folder.
Note: The memory-resident database monitor APIs will still be available.
In prior releases, the main advantage of the memory-resident database
monitor over the Detailed monitor
(STRDBMON) was its smaller impact on system resources. This was due to the
fact that it maintains the collected information in memory and writes to
files only if and when the user requests that it do so. The result was the
ability to gather database performance statistics with a minimal impact to
the performance of the system as whole, or to the performance of individual
SQL statements. However, significant enhancements introduced in V5R4 and
V6R1 allow additional filtering on detailed SQL performance monitors, which
greatly reduces the system impact of this type of monitor. SQL Plan Cache
viewing and snapshot capabilities have also been added to provide access to
the "always on" statement information cache. These new and redesigned tools
provide great detail while maintaining low system impact. These improvements
have eliminated the advantage the memory-resident database monitor once
provided.
If you plan to continue working with the memory-resident database monitors,
you can directly call the memory-resident database monitor API interfaces.

V7R1 MTU

System i Navigator removal of support for memory-resident database monitors
Starting in i 7.1, System i Navigator and IBM Navigator for i no longer
provide support for memory-resident database monitors. Memory-resident
database monitors are identified as type Summary in the SQL Performance
Monitors folder.
Note: The memory-resident database monitor APIs are still available.
In prior releases, the main advantage of the memory-resident database
monitor over the Detailed monitor
(STRDBMON) was its smaller impact on system resources. This was because it
maintains the collected information in memory and writes to files only if
and when the user requests that it do so. The result was the ability to
gather database performance statistics with a minimal impact to the
performance of the system as whole, or to the performance of individual SQL
statements. However, significant enhancements introduced in V5R4 and 6.1
allow additional filtering on detailed SQL performance monitors, which
greatly reduces the system impact of this type of monitor. SQL Plan Cache
viewing and snapshot capabilities have also been added to provide access to
the "always on" statement information cache. These new and redesigned tools
provide great detail while maintaining low system impact. These improvements
have eliminated the advantage the memory-resident database monitor once
provided.
If you plan to continue working with the memory-resident database monitors,
you can directly call the memory-resident database monitor API interfaces.

On a V7R1 system, IBM Navigator for i
System Monitors
"The monitor function needs to run on V7R2M0 or later, The target system is
V7R1M0."

These are reasons I'm still using MPG for perf monitoring.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue
Baker
Sent: Wednesday, August 19, 2015 11:52 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: IBM i Access for Web - Not yet a replacement for Navigator

"Jim Oberholtzer"
<midrangel@xxxxxxxxxxxxxxxxx>
wrote on Wed, 19 Aug 2015 14:48:39 GMT:

It sound to me that replacement of Management Central has to become a
significant topic at the CAAC

Jim, thank you for posting and suggesting bringing the issue to development
through one of many channels. While I know there are other IBMers
monitoring the conversations here, and I forward items to development when I
spot things, the best way to get their attention is via CAAC, CEAC (COMMON
Europe), ISV council, and the LUG in addition to design change requests.

Of course, opening PMRs for function which should work and doesn't is also
important.

--
Sue
IBM North America Advanced Technical Sales Support (ATS) Power Systems
Rochester, MN

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.