ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
XCOMM0294E XCOMHIST OPEN ERROR 00 64
Article ID: 104090
XCOM Data TransportXCOM Data Transport - WindowsXCOM Data Transport - Linux PCXCOM Data Transport - z/OS
Getting these messages on several LPAR's: XCOMM0294E XCOMHIST OPEN ERROR 00 64 - NOT LOGGING HISTORY XCOMM0455E J1XCOM HAS ENCOUNTERED A CRITICAL ERROR ON DATASET XCOMHIST IEC161I 038-061,TAXCOM,TAXCOM,XCOMSYST,,, 346 IEC161I SYS4.XCOM.PROD.JPNA.XCOMSYST.AIX, IEC161I SYS4.XCOM.PROD.JPNA.XCOMSYST.AIX.DATA,SYSCAT.JPNA.NET XCOMM0409E XCOMSYST OPEN ERROR 00 C4 - INQUIRY LIMITED
So I deleted and redefined all the VSAM files and restarted the XCOM STC, Still getting messages. I have attached: DEFHIST - job that deleted and redefined the History file and the AIX's DEFRRDS - job that deleted and redefined the RRDS VSAM file PREXCOM - the STC log before VSAM files were recreated POSTXCOM - STC log after VSAM files recreated Please advise how to correct these error messages.
XCOM r12 for z/OS
While reviewing output provided, the following messages were found:
BIX IDS(XCOM.PROD.XCOMHIST) - ODS(XCOM.PROD.XCOMSYST.AIX) 0IDC1644I ALTERNATE INDEX KEY NOT IN BASE RECORD 00000000000000000000 0IDC1653I XCOM.PROD.XCOMSYST.AIX BUILT WITH ERRORS 1IDCAMS SYSTEM SERVICES TIME: 00:28:57 07/04/18 PAGE 4 0IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 4
That will explain part of the problem.
The other thing we noticed in your output is the following:
The first thing that captured our attention is the KEYS(12 48) for your XCOMREQ. That is incorrect. Actually, that was the KEYS value used in the JCL to define the XCOMHIST in XCOM r11.5. The correct KEYS for XCOM r12.0 is KEYS(18 2024).
Please review and make sure that you are using the appropriate JCL for XCOMUTIL and/or DEFHIST for XCOM r12.0. You will find sample JCL for both in the CBXGJCL library.