ADR952E error on ADRDSSU DUMP of VSAM RLS managed ACDB and UAMS

book

Article ID: 242770

calendar_today

Updated On:

Products

SOLVE: Access Session Management

Issue/Introduction

Changed the UAMS and ACDB files to be VSAM RLS managed. After this change, an ADRDSSU DUMP of these files gets the following errors:

ADR952E (001)-DTDSC(01), THE IDAQDMP MACRO FAILED DURING QUIESCE PROCESSING FOR CLUSTER QNM.SOLVE.ACCESS.ACDB WITH RETURN CODE  
                         00000008 AND REASON CODE 61FF0004                                                                      
ADR952E (001)-DTDSC(01), THE IDAQDMP MACRO FAILED DURING QUIESCE PROCESSING FOR CLUSTER QNM.SOLVE.ACCESS.UAMS WITH RETURN CODE  
                         00000008 AND REASON CODE 61FF0004                                                                      

although TOLERATE(ENQFAILURE) parameter is specified, when the ADRDSSU job is executed while the Solve:Access region is active.

Cause

The ADR952E Reason Code explanation is the following:

-----------------------------------------------------------          
8      X'61FF0004'     A batch application has the sphere open        
                       for output and this is an attempt to take      
                       a non BWO copy.                                
-----------------------------------------------------------  

So, the ADRDSSU DUMP job tries to take a non BWO copy. 
BWO means Backup-While-Open and it requires that the application (Solve:Access in this case) must support the QUIESCE of VSAM RLS files issued from DFSMSdss.

CICS and IMS support this; Solve Access doesn't as the QUIESCE function makes the dataset unavailable to the region. So that would prevent logons and session list access. For a CICS disabling one application makes sense, but for SOLVE:Access it would disable its primary functions, so it may as well be down. 

Environment

Release : 5.0

Component : SOLVE:Access Session Management

Resolution

The Solve regions must be down in order to take a ADRSSU DUMP of these files, even though they are managed by RLS.

Workaround: use IDCAMS REPRO to do the backup and specify RLSSOURCE=YES. This would provide read integrity and allow the regions to remain active.