Questions with RSVLOGIC parameter for CA Workload Automation ESP Edition

Products

• ESP Workload Automation

Issue/Introduction

Question:

I have 4 master/proxy groups here. Two production master/proxy group in the production plex and 2 in the test plex. All master/proxies in all groups have the following RSVLOGIC statememt:

RSVLOGIC ENQ QNAME(CYBERRSV) RNAME(CYBERRSV)

Recently we have started having issues with ESP locking up (100% enqueue on CYBERRSV). I just want to confirm that what I am thinking is correct:

1 - Need to use a unique qname for each of my master/proxy groups - as a note: each of my groups does have it's own queue dataset.

2 - Need to add to MIM inclusion table. And we should specify SCOPE=SYSTEMS in MIM.

 

Environment

CA WA ESP Edition 11.4 Z/OS

 

Answer: 

 

The behavior change is related to PTF RO72017, which will make ESP master have about %80 of the share of cycle, so that Master can process more requests. But you have 4 masters, so this can cause resource constraint at times. Without this fix, the MINHOLD/MINDORM/MAXDORM in ESPPARM will be used to calculate the share, and by default, Master uses about %50 of the share.

 

1. Yes.

2. Yes, no need to specify SCOPE=SYSTEMS in MIM.

 

Additional Information: 

N/A

Environment

Release: ENCWLA00200-11.4-Workload Automation-Restart Option-EE
Component: