ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

View - Consolidation of View Databases with Existing EAS Tasks Inquiry

book

Article ID: 223635

calendar_today

Updated On:

Products

View

Issue/Introduction

We are consolidating 10 View JCL Collector databases into one.  Currently, these databases utilize two primary EAS tasks and one secondary EAS task that are also shared among other View Report databases. 

Will there be performance issue if the new database uses only a primary EAS task? 

Environment

Release : 14.0

Component : CA View

Resolution

As the client will be reducing the overall number of their View databases by 9, the implementation of their new JCL collector database, being tied to a primary EAS task, will work with no performance issues.

The client's set up of having 3 EAS tasks per LPAR (1 Primary, 2 Secondary) will work to their satisfaction, as the work is spread out proportionately.