CA Vantage CSA/ECSA and SQA/ESQA Usage

book

Article ID: 50995

calendar_today

Updated On:

Products

CA Allocate DASD Space and Placement CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Disk Backup and Restore - MVS CA DISK BACKUP AND RESTORE- ADD-ON OPTIO CA DISK BACKUP AND RESTORE

Issue/Introduction

Description:

The actual CA Vantage CSA/ECSA and SQA/ESQA usage is displayed via SYSVIEW command VSMTRACK or via the corresponding CA Vantage view 'VSMTRACK ? VSM ? Tracking' from the SYSVIEW interface.

Solution:

SYSVIEW sample display for the Vantage task:

 Cmd Jobname  Jobid    ASID EndDate  EndTime    CSA E-CSA   SQA E-SQA Total   
     VANTAGE  STC00063 0062                    5968  368K  1752  3176  379K

The amount of data placed in CSA/ECSA may change slightly from time to time.

For example module sizes change as maintenance and enhancements are done.

Actual usage will also vary based upon what options the customer has purchased, activated, and used. The only way to see/know exact values is to use another product or tool (such as SYSVIEW) that displays the precise information at the moment the inquiry is made.

As a sample, the CSA/ECSA usage of a Vantage development system showed:

The largest area was a 129K buffer used by RAID support in connection with system event notifications. The next was a 27K area for use by the Vantage automation servers, followed by a 24K buffer used for cross-memory communications.

There were two 8K buffers, one used by SMF support, the other by the hardware error monitor. Then there were a few very small ones (8-350 bytes) used by messages, health checks, security and TCP services.

If the customer identifies the memory usage in these areas to be vastly different, or substantially growing over time, that would indicate a problem which would need to be further analyzed.

Regarding SQA/ESQA, we don't getmain storage directly in SQA/ESQA.

It is IBM services that places data here, so they control that usage.

Environment

Release:
Component: VANT