CA SYSVIEW Performance Management

Expand all | Collapse all

Sysview History files and the Logger

  • 1.  Sysview History files and the Logger

    Posted 07-10-2019 03:22 AM
    All history files of the product are defined as logstreams. It means that the Logger automatically deletes old files after retention period. The problem though is that Sysview issues ENQ on a logstream when a user is browsing a history file. So if the Logger is trying to delete such file the deleting fails, and the deleting of subsequent logstreams on this LPAR can't be done. The dedicated storage group will eventually overflow.

    This is especially severe problem with CICS history files. The Support told me that this ENQ is the feature of the product which was introduced for the better performance. They proposed a REXX program which cancels user session after some time. But it can't be a solution: there will always be cases when a logstream is locked and Logger tries to delete it.

    I suppose that development will issue APAR which removes this ENQ. This not editing but browsing of the file. If a user browses a file which is going to be deleted he may get a message on the screen, but the Logger's work should not be interrupted.

    Alex Libkind
    Products and Networking Team
    zOSCP Unit
    Central Infrastructure Department
    Bank Poalim

  • 2.  RE: Sysview History files and the Logger

    Posted 07-10-2019 09:51 AM
    Hi Alex,

    Thank you for posting.

    To be clear, SYSVIEW does not hold the ENQ on the logstream. Rather, when a user is browsing the contents of the logstream from within SYSVIEW, a connection with the logstream is opened with IXGLOGR and IXGLOGR holds an ENQ on the data set where IXGLOGR is reading from.

    Your post will be reviewed by SYSVIEW Product Management.

    Sean McShane