|
|
Monitoring for EntireX is currently only supported if TCP/IP stubs in the
entire call, also internally on the Mainframe.
our impression that SVC on z/OS is by far the most common setup for internal
communication. And also the fastest communication.
consequence is that we and most customers on z/OS will have to change the stub-setup
in all environments in order to use Application Monitoring.
in itself a heavy task especially in outsourced environment.
On topof this, we and many customer use “trusted-userid=yes” for easier authentication.
Because this is only possible using SVC, these customers will also have to
change their security setup, which may involve a considerable effort – as well technically – but certainly also from an organizational perspective.
This change will impact all our integration and this will require a test which will cost way to much.
And until changed, we are not able to do application monitoring.
| Created on Brainstorm | 10/13/2017 5:01 |
| Brainstorm ID | 5342 |
EntireX RnD and PM analyzed this request.
It would mean a re-design of Application Monitoring as a basic feature is missing from SVC/NET: Receive-All.
This in turn would mean XL efforts.
Compared with our existing backlogs, we cannot see this to get implemented.