How Can I convert Compress hardware RESERVE requests using my multi-system serialization product?

Products

• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu

Issue/Introduction

Compress Data Compression uses hardware RESERVEs to serialize updates to its Analysis and Control files. Hardware RESERVE contention problems are possible, especially in the BrightStor CA-Compress started task as it processes concurrent I/Os to the Control File. If the hardware RESERVE on the Control File is not converted to a global SCOPE=SYSTEMS ENQ request and SYNCHRES(YES) is specified in SYS1.PARMLIB(GRSCNFxx), Compress Control File I/O is likely to hang, stopping the started task and any user job waiting for the Control File I/O to complete. Performance penalties caused by needless waiting are less serious, but worth avoiding.

Environment

Release: SMCOMV00200-5.5-Compress-Data Compression
Component:

Resolution

We therefore advise you to use your multi-system serialization product to convert Compress hardware RESERVE requests.

 

IBM Global Resource Serialization (GRS) users should add the following two statements to the RNL RESERVE section in SYS1.PARMLIB member GRSRNLxx:

 

RNLDEF RNL(CON)  TYPE(GENERIC)  NAME(SYSxxxx)
RNLDEF RNL(CON)  TYPE(GENERIC)  NAME(SHRINKFE)

 

Unicenter CA-Mult-image Manager (CA-MIM) users should place the following two statements in member MIMQNAME in the CA-MIM parmlib:

 

SYSxxxx  GDIF=YES,     
         SCOPE=RESERVES, 
         EXEMPT=NO,     
         ECMF=YES,      
         RPTAFTER=30,   
         RPTCYCLE=60 

SHRINKFE GDIF=YES,   
         SCOPE=RESERVES, 
         EXEMPT=NO,     
         ECMF=YES,      
         RPTAFTER=30,   
         RPTCYCLE=60

 

Note: In SYSxxxx, xxxx is the Compress subsystem name as you have installed it, equal to the first four characters of the Compress started task name.