CA Endevor Add action getting errors: VSI1102E , SMGR103S, and C1G0236S

Products

• Endevor

Issue/Introduction

 When doing an Add getting the following errors in the JES log:

 

SVM4000I #xxxxx, NDVRBAT, SYS#####, ATTEMPTING SPACVOLA FOR iprfx.iqual.xxxxx.STAGED.DATA, ENDVxx, 9
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA   
IEC070I 209-220,######,NDVRBAT,SYS#####,A###,ENDV##,   
IEC070I iprfx.ipqual.xxxxx.STAGED,iprfx.iqual.xxxxx.STAGED.DATA,  
IEC070I ICFCAT.SYSCxxxx 

 

Endevor messages:

 

VSI1102E  RETURN CODE 0008 FEEDBACK CODE 0028 RECEIVED FROM PUT MACRO FOR RPL CNTL BLOCK
SMGR103S  RC=0008/0028 CREATE ERROR ACCESSING DEV MASTER FILE                   
C1G0268E  ELEMENT RECORD WAS NOT FOUND FOR ELEMENT IN ENV: DEVVAL SYS: TEST SBS: COBOL6 STAGE D
C1G0277I  ADD PROCESSING TERMINATED BECAUSE OF THE PREVIOUS ERROR               
C1G0200I  ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGHEST ENDEVOR RC WAS 0016

 

Environment

Release : 18.0

Component : CA Endevor Software Change Manager

Cause

The data component for the involved MCF failed to allocate a new extent when Endevor tried to add a new record to the MCF.

StopX37 product from BMC is installed and tried to recover the situation by adding a new extent into volume ENDV11 as per message SVM4000I

However, StopX37 settings prevented the product to automatically allocate the new extent as per message SVM4001I

SVM4000I #7455H, NDVRBAT, SYS0000x, ATTEMPTING SPACVOLA FOR iprfx.iqual.xxxxx.STAGED.DATA, ENDVxx, 9 

SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA                     

Therefore, VSAM routines failed to extend the data component as per message IEC070I with RC 209

IEC070I 209-220,#xxxxx,NDVRBAT,SYS0000x,Axxx,ENDVxx,        

IEC070I iprfx.iqual.xxxxx.STAGED,iprfx.iqual.xxxxx.STAGED.DATA, 

IEC070I ICFCAT.SYSCAT04                                     

This caused Endevor to receive RC 08 with reason code 28 (hex 1C) from a VSAM PUT macro and fail the action

Resolution

This is a VSAM administration issue. If they expect StopX37 to automatically extend the file, just setup it to do that. 

Otherwise, they can follow standard VSAM actions to either:

- Make space on the volume

- Add a new volume to the data component so that VSAM can allocate new extents there

- Reorganize the MCF hoping that the redistribution of records will clear the problem.