DX Application Performance Management

Hi,

our customer is monitoring 200 CTG servers (zOS 2.2/ CTGServer 9.00 Java 1.7.0 32bit) with JAVA Agent for standalone jvm (10.3.0.15) and PP for CTG, without problems.

Today customer tested a new configuration (zOS 2.2 /CTG Server 9.2 Java 1.7.0 64bit) with the same JAVA agent, but in the folder CTG_to_CICS_ECI_IPIC all the CICS folder are now inactive, without data. The generic execute folder is present and works correctly. Application traffic is present. 

Has anyone encountered this kind of problem?

Thank You

Could be a few things. 

1. Double check your APM Status Console for any issues.  Agent side clamping may contribute to this.

2. Check your agent log and even enable debug and see if there are any errors.  Possibly a few threads may have died in the application but the process is still able to run.

3. Check your Collector log to ensure that there is nothing else going on.

4. Click on one of those grayed out metrics and check back on what date/time it stopped sending data and see what happened in the Collector and Agent log at that point in time.

5. Exercise that area of your application.  It is possible for metrics belonging to one part of an application to go gray if there is no execution for more than 60 minutes.

Thank You.

We'll apply your suggestions as soon as possible and we'll let you know the results.

M

Hi Matthew,

we checked Agent and EM logs, but we didn't find anything (in Debug too).

The agents have few metrics (<100) , so we can't suppose agent-side clamping.

The target EM doesn't appear in the APM System Information list.

Customer says that there are active connections with CICS.

First scenario: 

zOS 2.2/ CTGServer 9.00 Java 1.7.0 32bit with JAVA Agent for standalone jvm (10.3.0.15) and PP for CTG

we have specific CICS metrics:

Second Scenario:

zOS 2.2 /CTG Server 9.2 Java 1.7.0 64bit/1.8.0 64bit

JAVA Agent for standalone jvm (10.3.0.15) and PP for CTG

No specific CICS metrics available:

Thank You

Marco

Hi all,

we worked on this issue with support (00933520).

The issue has been solved using DefaultAgent for os400 in Legacy mode vers.10.5.1.8 inserting in the directive string PPCTGServer-full.pbd instead of PPCTGServer-Typical.pbd.

We tested with success the following configurations too:

DefaultAgent for os400 in NOLegacy mode vers.10.5.1.8 with PPCTGServer-full.pbd

DefaultAgent for os400 in NOLegacy mode vers.10.5.2.52 with PPCTGServer-full.pbd

DefaultAgent for os400 in NOLegacy mode vers.10.5.1.8 with PPCTGServerHC-full.pbd and the related CTGPP-HC jar files.

I recap the CTG Server Environment:

zOS 2.2 /CTG Server 9.2 /Java 1.7.0 64bit/Java 1.8 64bit

Thank You

Marco