ZOS Metrics are not generating consistent JMX MBean metric values

When using JMX instrumentation wildcards in AppDynamics, the extended PCF character sets returned from a ZOS queue manager are creating a bad JMX MBean that does not contain the full set of expected metrics for a given type. This causes AppD to assume the expected metric is NULL. After two attempts getting a NULL response to the metric value, AppD disables the metric and it becomes unusable.

This is only an issue when using a * wildcard to collect the MBean metrics.