CA Vantage CSA/ECSA and SQA/ESQA Usage

Products

• Allocate DASD Space and Placement
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• 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