IDADERRP13E - INTERR: LIB WRITE error, LIB=IDDAT VLS ADD RC=004-24

Products

• Ideal

Issue/Introduction

Attempts to edit the resources of any Ideal program fail with. 

1-IDADERRP13E - INTERR: LIB WRITE error, LIB=IDDAT 

SRVC=VLS FUNC=CREATE RC=004-24 PGM=ADSVCS 11.0 -3968 
CALPGM= CURACT=AR ACTTYP=D USER=OWI ERRID= 
SYS=£ID ENTTYP=PGM ENTNAM=P9525 ENTVER=002 ENTSTAT=PROD 
LIB=IDDAT MEM=£IDP9525 002E 

Similarly a DISPLAY INDEX PGM fails with... 

1-IDADERRP13E - INTERR: LIB WRITE error, LIB=IDDAT 

SRVC=VLS FUNC=ADD RC=004-24 PGM=ADSVCS 11.0 -3C54 
CALPGM= CURACT= ACTTYP= USER=OWI ERRID= 
SYS=£ID ENTTYP=PGM ENTNAM= ENTVER=000 ENTSTAT= 
LIB=IDDAT MEM=OWIINT1DV02 Z X 

The CICS region has been up for many weeks. Recycled CICS (in case of control block corruption) but it made no difference. 

Batch VLSUTIL LIBRARY functions are successful. Online Ideal @I$UTIL OUT INDEX IDDAT is successful. 

No changes to the CICS/Ideal/IPC configuration have been made recently. I see no evidence of hardware errors on the DASD. 

Environment

z/VSE 
CICS Transaction Server 1.1.1  
CA IDEAL 11.0

Cause

IDDAT library corruption.

Resolution

Run  VLSUTIL BACKUP/FORMAT/RESTORE on IDDAT. 

Additional Information

Most often this problem is due to a mismatch in BLKSIZE used to INIT the VLS file and the block size specified in the CICS FCT.
This was not the cause here. 
Block size in the CICS FCT is 1960 which matches the block size found in VLSUTIL LIBRARY report. 
No signs of storage violations in this CICS. CICS was up for 33 days..