We are getting the below messages in our XCOM started in Production.
XCOMM0425E XCOM HISTORY FILE HAS RUN OUT OF SPACE
XCOMM0455E V@XCOM HAS ENCOUNTERED A CRITICAL ERROR ON DATASET XCOMHIST
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=
SVM4000I XCOM, XCOM, XCOMHIST, ATTEMPTING SPACSECR FOR SYSC.XCOM121.XCOMSYST.AIX.DATA, GSS012, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
SVM4000I XCOM, XCOM, XCOMHIST, ATTEMPTING SPACVOLA FOR SYSC.XCOM121.XCOMSYST.AIX.DATA, GSS012, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
S0049170 IEC070I 209-220,XCOM,XCOM,XCOMHIST,1394,GSS012, 292
IEC070I SYSC.XCOM121.XCOMHIST,SYSC.XCOM121.XCOMSYST.AIX.DATA,
IEC070I SUCAT.SYSCV
XCOMM0425E XCOM HISTORY FILE HAS RUN OUT OF SPACE
XCOMM0455E V@XCOM HAS ENCOUNTERED A CRITICAL ERROR ON DATASET XCOMHIST
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=
SYSC.XCOM121.XCOMHIST *VSAM*
SYSC.XCOM121.XCOMHIST.DATA GSS031
SYSC.XCOM121.XCOMHIST.INDEX GSS031
SYSC.XCOM121.XCOMSYST.AIX.DATA GSS012
Is the XCOMHIST dataset is full? How can this be addressed?
Release : 12.0
Component : CA XCOM Data Transport for z/OS
Message XCOMM0425E basically tells you that the XCOM history (XCOMHIST) file is indeed full.
You have 2 options here:
1. Stop the XCOM task and redefine the XCOMHIST using the DEFHIST member in our CBXGJCL library.
or
2. Stop the XCOM task and run the XCOMUTIL job which performs other tasks with the the XCOMHIST should you need to keep records. This is also in the CBXGJCL library.
Please refer to the manual for info:
Also based on the following messages:
SVM4000I XCOM, XCOM, XCOMHIST, ATTEMPTING SPACSECR FOR SYSC.XCOM121.XCOMSYST.AIX.DATA, GSS012, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
The Alternate Index file for XCOMSYST is full. Please make sure to allocate enough space for all the Alternate Index files for the XCOMHIST.