Velocity Software, Inc.
Performance Data Interfaces

As the leader in z/VM and Linux on z/VM performance data gathering, your enterprise monitor mayl require an interface to incorporate the VM and Linux data collected by ESALPS.

The Performance Data Base (PDB) provided by Velocity Software is referred to as "history" data in the documentation. This is a collection of 5 files,

The format of the history data is in segments. Each segment has a 6 byte name followed by a 2 byte length code. If processing these files, it is mandatory that this format is used - as when segments are increased with new fields, your programs will still work if incrementing pointers based on the length code, and not a hard coded length that may change from release to release.

Velocity Software provides several interfaces to this data. ESAMAP: ESAMAP processes the history, producing reports

  • ESAEXTR: Part of the ESAMAP product, installations can define their own reports, selecting only data pertinent to the requirement
  • SAS code: Very much out of date, using Merrill Consultants' MXG is a much better option
  • PLI declares: If Velocity Software does not provide a function that meets the requirements, this is an option. Note that we (Velocity Software) would like to meet your needs and perform the needed programming, please contact us with your needs.

    • Computer Associates: MICS Support / NeuMICS Support

    MICS is directly supported by ESAWRITE, allowing the records required by MICS to be generated directly without the need to collect raw monitor data.
    From Computer Associates ENews:
    Velocity Software's ESAMON and NeuMICS

    Did you know the Unicenter NeuMICS Resource Management Analyzer Option for VM and CMS can process monitor history records from Velocity Software's ESAMON?

    The VM monitor records extracted by Velocity Software's ESAMON product have the same format and content as the standard monitor records collected by IBM's VM supplied MONWRITE utility. Additionally, ESAMON can extract monitor data at longer intervals than the set Monitor interval, substantially reducing DASD space requirements. This allows the Monitor interval to be set to a small value for effective real-time monitoring, without using large amounts of DASD space for data logging. To learn more about Velocity Software visit the Velocity Software webpage.

    Instructions on moving this data to z/OS for MICS processing can be found at ESAMICS EXEC

    Merrill Consultants: MXG

    MXG supports using ESALPS history data as input. Data of any granularity is supported, either the one minute produced by ESAWRITE or the long term data with 15 minute granularity produced by ESAMAP. Look for the "XAMSYS", "XAMCPU", "XAMUSR", "XAMDEV" and "XAMTCP" declarations.

    Note, that in single CPU environment, ESAMAP should use the parameter "CPU_HISTORY='1110'B".

    Tivoli Performance Reporter

    For those using the Tivoli Performance Reporter, the following was provided by an IBM location for release 2.4. Please send any updates to Velocity Software for inclusion and assistance to others if you develop further enhancements.

    Tivoly / PRF Conversion Support
    ESASYS History Support
    ESACPU History Support
    ESAUSR History Support
    ESADEV History Support

    Service Level Reporter

    For those running SLR, since replaced by Tivoli Performance Reporter, the files are archived and available at:

    SLR Support

    VM PAF Support

    For those using the old VM PAF from IBM, the following is the interface to that product.

    ESAPAFVL EXEC
    ESAPAFKW EXEC
    ESAPAFHF EXEC
    ESAPAFEF EXEC
    ESAPAFCV EXEC
    ESAPAF KWIC
    VMPAF ESAEXTR

    PL1 Declares

    For those needing the PL1 declares for the history data, The following is upto date as of ESALPS 3.5:

    ESASYS History Link
    ESACPU History Link
    ESADEV History Link
    ESAUSR History Link
    ESATCP History Link