We are not using the IMS CDC component but we noticed that when we upgraded from Attunity 5.3.3 to 5.3.4 on the IBM z/OS mainframe that the DFSFLGX0 module was placed in the Attunity LOAD library (it was not there under 5.3.3). Now we are getting S0C4's in this module. Why did this module get installed as we are not using the IMS CDC component (we are only capturing DB2 z/OS changes, not IMS changes) and why is it getting invoked?

Any help would be much appreciated.

We have test jobs that are abending and also when we bring up the test IMS control region we get the following messages:
01.24.11 STC08456 DFSFLGX0 01/25/16 21.45 Attunity CDC *Active*
01.24.11 STC08456 ATYC404W CDC$PARM Dataset not found - using defaults
01.24.11 STC08456 ATYC100I IMS Release 4.0 BUFNO=00030 BUFFSIZE=22550
01.24.11 STC08456 ATYC905E - Error attempting to connect to logstream
01.24.11 STC08456 IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM ATTUNITY.IMS.DCAPDATA
668 DID NOT SUCCEED FOR JOB IMSBRN. RETURN CODE: 00000008 REASON CODE:
668 0000080B DIAG1: 00000000 DIAG2: 00000000 DIAG3: 00000000 DIAG4:
668 00000000
01.24.11 STC08456 *ATYC999E - Logstream for Attunity CDC disabled
01.24.11 STC08456 IXG232I IXGCONN REQUEST=DISCONNECT FROM LOG STREAM **UNKNOWN** DID NOT
670 SUCCEED FOR JOB IMSBRN. RETURN CODE: 00000008 REASON CODE: 00000806
670 DIAG1: 00000000 DIAG2: 00000000 DIAG3: 03030000 DIAG4: 00000000