CA View - Reports not routing correctly since upgrade

Products

• OM Deliver
• OM View

Issue/Introduction

The client upgraded CA View to v14.0 and noticed that some reports were not being routed to the correct View database.

Sysout classes unaccounted for are X and W.

 

Environment

Release : 14.0

Component : CA View

Resolution

In this instance, sysout class X is a held class.

If a sysout goes to a held class, CA View will not collect it.

There was no mention, in any of the client SARINIT parameters, regarding sysout class W.

However, the client had a SARXTD task which was not running due to having a non-authorized library referenced in the //STEPLIB statement.
As a result, class W was not being processed.

The client changed the library in the statement, restarted the SARXTD task, and class W was processed as expected.