XCF Abend 00C Reason code 02070001 in LOGREC
Article ID: 247281
Updated On:
Products
Issue/Introduction
We have an increase in LOGREC Records related to Datacom/AD Version 15.1, but I see no functional issues in the Datacom/AD STC or the CA Scheduler STC that uses Datacom/AD.
Can you tell me what is happening, or what is causing this error?
Below is a snippet from the LOGREC:
JOBNAME: CADATACM SYSTEM NAME: BSYS
ERRORID: SEQ=00097 CPU=4001 ASID=003D TIME=03:54:03.4
SEARCH ARGUMENT ABSTRACT
PIDS/5752SCXCF RIDS/IEANUC01#L RIDS/IXCS1STB AB/S000C PRCS/02070001 REGS/8287C
RIDS/IXCM2REC#R
SYMPTOM DESCRIPTION
------- -----------
PIDS/5752SCXCF PROGRAM ID: 5752SCXCF
RIDS/IEANUC01#L LOAD MODULE NAME: IEANUC01
RIDS/IXCS1STB CSECT NAME: IXCS1STB
AB/S000C SYSTEM ABEND CODE: 000C
PRCS/02070001 ABEND REASON CODE: 02070001
REGS/8287C REGISTER/PSW DIFFERENCE FOR R08:-287C
RIDS/IXCM2REC#R RECOVERY ROUTINE CSECT NAME: IXCM2REC
OTHER SERVICEABILITY INFORMATION
RECOVERY ROUTINE LABEL: IXCMIFRR
DATE ASSEMBLED: 03/06/17
MODULE LEVEL: HBB77B0
SUBFUNCTION: USER ERROR MESSAGE EXIT
Environment
Release : 15.1
Component : Datacom/AD
Component : Datacom/DB
Cause
Some application other than the MUF or Scheduler is using the same XCF group name that the MUF is using.
Resolution
A review of the dump associated with the LogRec errors led to issuing XCF console commands:
- /D XCF,GROUP
- /D XCF,GROUP,SCHD,ALL
This output showed:
D XCF,GROUP,SCHD,ALL
IXC333I 13.12.08 DISPLAY XCF 253
INFORMATION FOR GROUP SCHD
MEMBER NAME: SYSTEM: JOB ID: STATUS:
CDCCCIB@SCHD BSYS ENF ACTIVE
CH01OMSASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM01ASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM02ASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM03ASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM04ASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM05ASYS$$$$ ASYS CH01OMS ACTIVE
CH01OM06ASYS$$$$ ASYS CH01OMS ACTIVE
PRODCXX BSYS CADATACM ACTIVE
In looking at the dump, the XCF message exit showed data that did not appear to be Datacom-related. This appears to be the result of the CDCCCIB member sending ENF data through XCF using the same group name. The dump also showed a S0C4 abend, and it was consistent that the S0C4 and the S00C were related to our trying to process ENF data as if it were Datacom data.
Changing the XCF group name for CCI or for Datacom will resolve the conflict, and should clear this up and allow each application to use its own XCF path.
Additional Information
As always, please contact Broadcom support for Datacom if you have further questions.
Feedback
