IUVM04 with VSAM CC=08 FDBK=1C during update of MODSDIS file

Products

• NetMaster Network Management for TCP/IP
• NetMaster File Transfer Management
• NetMaster Network Automation
• NetMaster Network Management for SNA

Issue/Introduction

Just enabled parameter group VSAMUPDATE to automatically copy the the updated elements to the MODSDIS and PANLDIS VSAM files of the region.

Some maintenance has been correctly applied but suddenly the automatic process starts failing with the following messages:

IAVP0201I Installing VSAM data member MOD@$OC for LU11517                                   
TI0125 TIMER PROCESSING STARTED 0 TIMERS RESTORED, 0 DELETED DUE TO EXPIRY                  
IAVP0102I IUV001 Start of request validation phase                                          
IAVP0102I  COPY MODS INDD=SYS00025 OUTDD=MODSDIS OPT=INSTALL                                
IAVP0102I IUVC01 Request valid, request number    1 assigned                                
IAVP0102I IUV002 End of request validation phase                                            
IAVP0102I IUV003 Processing request number    1                                             
IAVP0102I  COPY MODS INDD=SYS00025 OUTDD=MODSDIS OPT=INSTALL                                
IAVP0102I IUVR10  Input DD Name=SYS00025 DSN=hlq.NETMAST.R122.NMC2.CC2DVSMI                
IAVP0102I IUVR10 Output DD Name=MODSDIS  DSN=hlq.NMC2.MODSDIS                         
IAVP0102I IUVM04 System error: INDD=SYS00025 OUTDD=MODSDIS  Function=WRITE OUTPUT     RC=08 VSAM CC=08 VSAM FDBK=1C
IAVP0102I IUVM03 Key=UK$HM030$OC$SHOW       F$REPLY      0001                               
IAVP0102I IUV006 VIP terminated due to previous errors                                      
IAVP0103E VSAM update failed RC=12 for hlq.NETMAST.R122.NMC2.CC2DVSMI(MOD@$OC) 

The same error occurs for the rest of the MODSDIS elements that need to be updated.

Environment

NetMaster 12.2 on z/OS

Cause

Error on VSAM file

Resolution

Per IBM documentation, VSAM Feedback Code 28(X'1C') means:

Data set cannot be extended because VSAM cannot allocate additional direct access storage space. Either there is not enough space left to make the secondary allocation request, or you attempted to increase the size of a data set while processing with SHAREOPTIONS=4 and DISP=SHR.

Check which of the above conditions is true and then take the appropriate actions. Usually the cause is the first one (volume full).