Vsam AIX Backup error: ADSVS067 2545 GET: WORK AREA NOT LARGE ENOUGH FOR DATA RECORD

Document ID : KB000095677
Last Modified Date : 15/05/2018
Show Technical Document Details
Introduction:
It can happen that, during CA Disk BACKUP procedure of a Vsam AIX file, an error looking like the following is got in the //MSGPRINT DD : 

...
ADSTH004 * 0381 DUPLICATE COPY TAPE NOT PRODUCED, ARCHIVEC DD STMT IS DUMMIED OUT
ADSVS067 2524 THE FOLLOWING ERROR OCCURED WHILE ISSUING A GET REQUEST FOR CLUSTER QFLSI1.SI0NSVS.FLBT.ANAGTSIN.AIX1
ADSVS067 2524 RPL FEEDBACK CODE = 44 REGISTER 15 CONTENTS = 8
ADSVS067 2545 GET: LOGICAL ERROR DURING PROCESSING RPL FDBK = 44
ADSVS067 2545 GET: WORK AREA NOT LARGE ENOUGH FOR DATA RECORD
ADSVS060 0394 QFLSI1.SI0NSVS.FLBT.ANAGTSIN.AIX1 WAS NOT ARCHIVED TWO TO PREVIOUS ERROR
...

How to bypass it and have the Backup end correctly? 
Environment:
CA DISK all releases 
Instructions:
Usually the error: 

ADSVS067 2545 GET: WORK AREA NOT LARGE ENOUGH FOR DATA RECORD 

indicates that the CA Disk  IOMAXREC Sysparm value is too low and should be increased :

IOMAXRECnnnnnn - This sysparm specifies the maximum logical record size for data sets processed by CA Disk. The default value is 65,000 bytes. 
The maximum value for this sysparm is 999,999 bytes. To save real storage, this sysparm should be set to the lowest value possible that still allows normal CA Disk processing. 

So, in order to bypass this error, it is possible to rerun the Backup procedure increasing this Sysparm value and taking care of the notice provided about how to save real storage. 

If, after this change,  the problem persists, You need to rerun the same job with the following diagnostic statements added and open a CA Disk case, attaching the complete joblog : 

//MTFLIBDG DD SYSOUT=* 
//SYSPARMS DD * 
SYSPARMSS 
DIAGALOCY 
IOMAXRECnnnnnn