CA Datacom/AD CA RS 1403 Service List

Transcription

1 CA Datacom/AD CA RS 1403 Service List Description Hiper 14.0 RO56304 CORRECT ELEMENT LENGTH CALCULATION WITH REDEFINES RO56349 EXPAND INTERNAL COMAND BUFFER RO59103 VLS CICS INQUIRE FILE INCORRECT RO60369 DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - MPX-0986 RO61746 USS: HEAP POOL DAMAGE IN CHORUS RO61843 REPACKAGE PTF RO60177 WITH CORRECTED HOLDDATA RO62358 COPY TO PROD LOOPS RO62605 CHANGE DATA CAPTURE PRODUCT ENHANCEMENT RO62980 MF: S0C4 SVDBS14 USING TCP/IP RO63016 VPE NOT CLEARING NEWLY-ALLOCATED GRT SEGMENTS RO63093 FIX DBSOCPR TRACE RO63245 CAAXSAMP AXRIM01 AND AXPOR02 JCL MEMBERS MINOR ERRORS RO63315 REDUCE OVERHEAD WHEN SHADOW MUF TAKES OVER FOR A FAILED MUF RO63454 RETURN CODE 13(017) DOING INDEX QUEUE PROCESSING RO63552 CA EXAMINE MODULE MISSING FROM CABDLPA RO63572 SQLCODE -39 IN PXX WITH POSITIVE/UNSIGNED PREDICATES RO63722 INTERNAL ERROR ATTEMPTING TO START STAR MUF RO63772 SPORADIC DBMUFPR ABEND DURING EOJ CLEANUP RO63961 MINOR PERFORMANCE ENHANCEMENT FOR INDEX QUEUE PROCESSING RO64065 DBUTLTY REORG WITH MULTUSE=NO S0C4 ABEND RO64298 MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND RO64299 MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND RO64338 IXX TYPE B REPORT GETS A RETURN CODE 03(027) RO64558 MUF S0C4 ABEND DBIDXPR+5D22 USING MUFPLEX RO64787 SHADOW MUF INCORRECTLY SHOWS ENABLED YEAR OF 2000 RO65436 SQL RETURN CODE -165 ON DDTRSLM IMPORT RO65555 CXX STATS ON DASD TO BE UPDATED EVERY 24 HOURS FROM MEMORY RO65595 TTM BLOCKS HUNG AND COUNTERS INCORRECT RO65632 VARIOUS SQL ERRORS ON DDTRSLM IMPORT RO65733 SPORADIC DELAY OF OPEN/CLOSE WITH STAR RO65864 DECIMAL FIELDS DISPLAY INCORRECTLY IN COBOL The CA RS 1403 service count for this release is 31

2 CA Datacom/AD 2 CA RS 1403 Service List for CAADE00 FMID Service Description Hiper CAADE00 RO56304 CORRECT ELEMENT LENGTH CALCULATION WITH REDEFINES RO62358 COPY TO PROD LOOPS RO65436 SQL RETURN CODE -165 ON DDTRSLM IMPORT RO65632 VARIOUS SQL ERRORS ON DDTRSLM IMPORT RO65864 DECIMAL FIELDS DISPLAY INCORRECTLY IN COBOL The CA RS 1403 service count for this FMID is 5

3 CA Datacom/AD 3 CA RS 1403 Service List for CAAXE00 FMID Service Description Hiper CAAXE00 RO63245 CAAXSAMP AXRIM01 AND AXPOR02 JCL MEMBERS MINOR ERRORS The CA RS 1403 service count for this FMID is 1

4 CA Datacom/AD 4 CA RS 1403 Service List for CABDE00 FMID Service Description Hiper CABDE00 RO60369 DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - MPX-0986 RO61843 REPACKAGE PTF RO60177 WITH CORRECTED HOLDDATA RO62605 CHANGE DATA CAPTURE PRODUCT ENHANCEMENT RO63315 REDUCE OVERHEAD WHEN SHADOW MUF TAKES OVER FOR A FAILED MUF RO63454 RETURN CODE 13(017) DOING INDEX QUEUE PROCESSING RO63552 CA EXAMINE MODULE MISSING FROM CABDLPA RO63722 INTERNAL ERROR ATTEMPTING TO START STAR MUF RO63772 SPORADIC DBMUFPR ABEND DURING EOJ CLEANUP RO63961 MINOR PERFORMANCE ENHANCEMENT FOR INDEX QUEUE PROCESSING RO64065 DBUTLTY REORG WITH MULTUSE=NO S0C4 ABEND RO64338 IXX TYPE B REPORT GETS A RETURN CODE 03(027) RO64558 MUF S0C4 ABEND DBIDXPR+5D22 USING MUFPLEX RO64787 SHADOW MUF INCORRECTLY SHOWS ENABLED YEAR OF 2000 RO65555 CXX STATS ON DASD TO BE UPDATED EVERY 24 HOURS FROM MEMORY RO65733 SPORADIC DELAY OF OPEN/CLOSE WITH STAR The CA RS 1403 service count for this FMID is 15

5 CA Datacom/AD 5 CA RS 1403 Service List for CAVEE00 FMID Service Description Hiper CAVEE00 RO63093 FIX DBSOCPR TRACE RO63572 SQLCODE -39 IN PXX WITH POSITIVE/UNSIGNED PREDICATES RO65595 TTM BLOCKS HUNG AND COUNTERS INCORRECT The CA RS 1403 service count for this FMID is 3

6 CA Datacom/AD 6 CA RS 1403 Service List for CAVQE00 FMID Service Description Hiper CAVQE00 RO56349 EXPAND INTERNAL COMAND BUFFER RO59103 VLS CICS INQUIRE FILE INCORRECT RO63016 VPE NOT CLEARING NEWLY-ALLOCATED GRT SEGMENTS The CA RS 1403 service count for this FMID is 3

7 CA Datacom/AD 7 CA RS 1403 Service List for CAYTE00 FMID Service Description Hiper CAYTE00 RO62980 MF: S0C4 SVDBS14 USING TCP/IP RO64298 MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND The CA RS 1403 service count for this FMID is 2

8 CA Datacom/AD 8 CA RS 1403 Service List for CAYTE02 FMID Service Description Hiper CAYTE02 RO61746 USS: HEAP POOL DAMAGE IN CHORUS RO64299 MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND The CA RS 1403 service count for this FMID is 2

9 CA Datacom/AD CA RS PTF RO RO56304 RO56304 M.C.S. ENTRIES = ++PTF (RO56304) CORRECT ELEMENT LENGTH CALCULATION WITH REDEFINES A user defines an element to a table that has REDEFINES fields within the body of the defined element. The add/update will be successful, but the calculated length for the element will be incorrect if one or more of the fields included in the definition are children of a REDEFINES fields. Defining an element to a table results in an incorrectly calculated length for the element. The impact is high since the user has no way of knowing the length is not correct and will return incorrect data when used. PRODUCT(S) AFFECTED: CA Datacom Datadictionary Release 12.0 CA Datacom Datadictionary Release 14.0 DD 2055 Copyright (C) 2013 CA. All rights reserved. R00405-DCM140-SP1 DESC(CORRECT ELEMENT LENGTH CALCULATION WITH REDEFINES). FMID (CAADE00) PRE ( RO44743 ) SUP ( TR56304 )

10 CA Datacom/AD CA RS PTF RO RO56349 RO56349 M.C.S. ENTRIES = ++PTF (RO56349) EXPAND INTERNAL COMAND BUFFER Internally built commands, especially in DDOL, using maximum length operand names, may exceed the current buffer length, which matches the size of the 3270 command line (76 bytes). Truncation of the command can cause the product to report a syntax error. Syntax errors are produced even though each component of the command is valid. Limit lengths of operands used in combination. The limitation is on the total length of the command only. PRODUCT(S) AFFECTED: CA IPC Release 14.0 CA Ideal Release 14.0 CA Datacom Datadictionary Release 14.0 IPC 56 Copyright (C) 2013 CA. All rights reserved. R00035-IPC140-SP1 DESC(EXPAND INTERNAL COMAND BUFFER). FMID (CAVQE00) PRE ( RO36799 ) SUP ( RO53071 TR53071 TR56349 )

11 CA Datacom/AD CA RS PTF RO RO59103 RO59103 M.C.S. ENTRIES = ++PTF (RO59103) VLS CICS INQUIRE FILE INCORRECT VLS code executing in CICS is not properly handling the INQUIRE FILE function causing abends or other unpredictable results processing the first access of a VLS (BDAM) file when CICS has been recycled. If the NETT task has been invoked via the PLT, it may abend with the following error message in the CICS joblog: ICPSINIT99E - ERROR DETECTED AT PSS INITIALIZATION PSS1 RF=4 R0=2 The problem is most likely to affect the first CA Ideal tasks of the CICS cycle. Subsequent tasks are successful. PRODUCT(S) AFFECTED: CA IPC Release 14.0 CA Ideal Release 14.0 CA Ideal Release 11.0 CA Datacom Datadictionary Release 14.0 CA Datacom Datadictionary Release 12.0 IPC 57 Copyright (C) 2013 CA. All rights reserved. R00036-IPC140-SP1 DESC(VLS CICS INQUIRE FILE INCORRECT). FMID (CAVQE00) PRE ( RO27894 RO33979 ) SUP ( RO35442 TR35442 TR59103 )

12 CA Datacom/AD CA RS PTF RO RO60369 RO60369 M.C.S. ENTRIES = ++PTF (RO60369) DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - MPX-0986 In full MUFplex mode, including during MIGRATE_TO_SHADOW, the CA Datacom Multiuser Facility (MUF) very sporadically abends with message: DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - MPX The error occurs when MUF attempts to push a row lock to the Coupling Facility that it already owns, i.e. a duplicate row lock. MUF abends with the above message. In MUFplex mode B, including during MIGRATE_TO_SHADOW, other MUFs in the MUFplex abend with message: DB02341I - MUFPLEX MODE 'S/B' REMOTE MUF FAILURE CLEANUP NOT POSSIBLE, TERMINATING WITH ABEND 4. The impact is an outage of one MUF in a MUFplex running in mode A or an outage of the entire MUFplex if running in MUFplex mode B, including the Shadow during MIGRATE_TO_SHADOW. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4811 Copyright (C) 2013 CA. All rights reserved. R00453-DCM140-SP1 DESC(DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - MPX-0986). FMID (CABDE00) PRE ( RO38425 RO41191 ) SUP ( RO54282 TR54282 TR60369 )

13 CA Datacom/AD CA RS PTF RO RO61746 RO61746 M.C.S. ENTRIES = ++PTF (RO61746) USS: HEAP POOL DAMAGE IN CHORUS CA LDAP Server crashes when accessing a LOB column stored in CA Datacom/DB. The symptom of the defect is typically a S0C4, but since the defect results in a storage overlay, other symptoms are possible. CA Chorus will abend. Neither the CA Datacom Server Mainframe Region nor the CA Datacom Multi-User Facility region are affected. PRODUCT(S) AFFECTED: CA Datacom Server Release 14.0 COMPONENTS AFFECTED: cadcmf32 cadcmf64 cadcdb32 cadcdb64 libcacdb32.so libcacdb64.so DBSRV 558 Copyright (C) 2013 CA. All rights reserved. R00103-DSR140-SP1 DESC(USS: HEAP POOL DAMAGE IN CHORUS). FMID (CAYTE02) PRE ( RO40499 RO41066 RO42673 RO42697 RO43168 RO44504 RO44527 RO45190 RO45595 RO45733 RO47379 RO51470 RO52943 ) SUP ( TR61746 ) BINARY LINK('libcadcdb32.so') PARM(PATHMODE(0,7,7,5),APF,PROGCTL). BINARY LINK('libcadcdb64.so') PARM(PATHMODE(0,7,7,5),APF,PROGCTL). BINARY LINK('cadcmf32') PARM(PATHMODE(0,7,7,5),APF,PROGCTL). BINARY LINK('cadcmf64') PARM(PATHMODE(0,7,7,5),APF,PROGCTL). BINARY LINK('cadcpp32') PARM(PATHMODE(0,7,7,5),APF,PROGCTL).

14 CA Datacom/AD CA RS PTF RO RO61843 RO61843 M.C.S. ENTRIES = ++PTF (RO61843) REPACKAGE PTF RO60177 WITH CORRECTED HOLDDATA PTF RO60177 has HOLDDATA of type ACTION that was unintended. Only the HOLD of type DOC is correct. The customer can simply BYPASS the unintended HOLD, but there has been confusion among customers. This solution redelivers the code from RO60177 with the extraneous ACTION HOLD removed. This PTF supersedes RO60177, so if the earlier solution has not already been applied, the problem can be avoided. An SMP/E APPLY of RO60177 will request that the customer respond to the type ACTION HOLD which only has skeleton text that is not meaningful (and was not intended). The customer will not know how to respond. Customers are confused by the presence of this incomplete and unintended ACTION HOLD. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4827 Copyright (C) 2013 CA. All rights reserved. R00469-DCM140-SP1 DESC(REPACKAGE PTF RO60177 WITH CORRECTED HOLDDATA). FMID (CABDE00) PRE ( RO46575 ) SUP ( AR47507 AR59165 RO34786 RO42639 RO49305 RO54278 RO57425 RO59165 RO60177 TR34786 TR42639 TR49305 TR54278 TR57425 TR59165 TR60177 TR61843 ) ++HOLD (RO61843) SYSTEM FMID(CABDE00) REASON (DOC ) DATE (13316) COMMENT ( PRODUCT: CA DATACOM/DB RELEASE 14.0 PUBLICATION: CA DATACOM/DB DATABASE AND SYSTEM ADMINISTRATION GUIDE Version 14.0 Please see the associated Product Documentation Change (PDC) published as RI ).

15 CA Datacom/AD CA RS PTF RO RO62358 RO62358 M.C.S. ENTRIES = ++PTF (RO62358) COPY TO PROD LOOPS Attempts to copy a database, area, or table occurrence to PRODuction status using either the CA Datacom Datadictionary DDUPDATE utility or DDOL can induce a loop. The loop will not always occur, depending on factors such as the number of elements in the dataview, the target PROD version number, the number of relationships pointing at history elements, and the number of relationships pointing at elements that have rolled off the dictionary due to the ENTY-HIST-VERS attribute for the element table. Trying to copy a database or one of its sub-structures to PROD status using either DDUPDATE or DDOL can result in a looping condition. Not all database definitions will exhibit the loop. Those that do cannot be successfully copied to PROD. PRODUCT(S) AFFECTED: CA Datacom Datadictionary Release 12.0 DD 2062 Copyright (C) 2013 CA. All rights reserved. R00476-DCM140-SP1 DESC(COPY TO PROD LOOPS). FMID (CAADE00) PRE ( RO54667 ) SUP ( TR62358 )

16 CA Datacom/AD CA RS PTF RO RO62605 RO62605 M.C.S. ENTRIES = ++PTF (RO62605) CHANGE DATA CAPTURE PRODUCT ENHANCEMENT This solution delivers code changes related to a future enhancement of the Change Data Capture (CDC) feature of CA Datacom/DB. This is an enhancement. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4794 Copyright (C) 2013 CA. All rights reserved. R00478-DCM140-SP1 DESC(CHANGE DATA CAPTURE PRODUCT ENHANCEMENT). FMID (CABDE00) PRE ( RO31497 RO31887 RO33475 RO33807 RO33933 RO35280 RO35426 RO36029 RO36034 RO36631 RO36773 RO37575 RO38446 RO41209 RO43272 RO44202 RO47505 RO48009 RO48058 RO48653 RO49483 RO49554 RO50927 RO51924 RO53059 RO53265 RO54630 RO59348 RO59522 RO61435 ) SUP ( AC57573 RO31570 RO34236 RO34482 RO34971 RO35392 RO35611 RO36137 RO36213 RO36931 RO38729 RO43731 RO46955 RO48173 RO48349 RO50288 RO50687 RO51282 RO55958 RO57549 RO59664 RO60448 TR31570 TR34236 TR34482 TR34971 TR35360 TR35392 TR35611 TR36137 TR36213 TR36931 TR38729 TR43731 TR46955 TR48173 TR48349 TR50288 TR50687 TR51282 TR55958 TR57549 TR59664 TR60448 TR62605 )

17 CA Datacom/AD CA RS PTF RO RO62980 RO62980 M.C.S. ENTRIES = ++PTF (RO62980) MF: S0C4 SVDBS14 USING TCP/IP A client connection which goes through timeout processing on mainframe server causes S0C4. The condition occurs using type2 TCP and type4 connections. Mainframe Server abends with a S0C4. The Mainframe Server region must be restarted. PRODUCT(S) AFFECTED: CA Datacom Server Release 14.0 DBSRV 570 Copyright (C) 2013 CA. All rights reserved. R00104-DSR140-SP1 DESC(MF: S0C4 SVDBS14 USING TCP/IP). FMID (CAYTE00) PRE ( RO52942 RO53293 RO54082 RO54856 RO55939 ) SUP ( RO56798 TR56798 TR62980 )

18 CA Datacom/AD CA RS PTF RO RO63016 RO63016 M.C.S. ENTRIES = ++PTF (RO63016) VPE NOT CLEARING NEWLY-ALLOCATED GRT SEGMENTS VPE is not clearing new segments added to its Global Resource Table (GRT), which can cause problems when the new segment is accessed. Various symptoms are possible. Internal calls within VPE will fail unpredictably. Complex Ideal batch applications can fail when GRT segments reuse previously freed storage. PRODUCT(S) AFFECTED: CA IPC Release 14.0 CA IDEAL Release 14.0 IPC 60 Copyright (C) 2013 CA. All rights reserved. R00038-IPC140-SP1 DESC(VPE NOT CLEARING NEWLY-ALLOCATED GRT SEGMENTS). FMID (CAVQE00) PRE ( RO33979 RO55842 ) SUP ( RO37638 RO40889 RO46573 TR36553 TR37638 TR40889 TR46573 TR63016 )

19 CA Datacom/AD CA RS PTF RO RO63093 RO63093 M.C.S. ENTRIES = ++PTF (RO63093) FIX DBSOCPR TRACE The trace facility for DBSOCPR does not print the correct output. The trace output is not usable to diagnose problems. This problem makes it difficult to diagnose problems. PRODUCT(S) AFFECTED: CA Datacom SQL Release 14.0 SQL 1910 Copyright (C) 2013 CA. All rights reserved. R00481-DCM140-SP1 DESC(FIX DBSOCPR TRACE). FMID (CAVEE00) SUP ( TR63093 )

20 CA Datacom/AD CA RS PTF RO RO63245 RO63245 M.C.S. ENTRIES = ++PTF (RO63245) CAAXSAMP AXRIM01 AND AXPOR02 JCL MEMBERS MINOR ERRORS CA Datacom/AD CAAXSAMP members AXRIM01 and AXPOR02 have minor problems. AXRIM01 has an edit symbolic that should not be present. AXPOR02 is using a DBUTLTY function that was not available in The AXRIM01 member fails with a JCL error when submitted. The AXPOR02 member fails with a S000 U0004 and produces the following error message if the source MUF is version 'DB10010E - INCORRECT VALUE FOR KEYWORD' The AXRIM01 and AXPOR02 members do not run successfully without making changes that should not have to be done. In the AXRIM01 member, remove the BDTLL='CAI.THLQ.CAAXLOAD' entry from the PCLOAD PROC. Below is how the PROC should look after the change. //PCLOAD PROC BDCSS='CAI.CACSS.CAW0LOAD', // SYSOUT='*' ** INSTALLATION STANDARD SYSOUT CLASS Change the AXPOR02 DBUTLTY 'ACCESS STATUS=UTLTY,DBID=nnn,USERS=WAIT' input statement to 'ACCESS STATUS=OFF,DBID=nnn,USERS=WAIT' where the 'nnn' is the database ID of the database being migrated. PRODUCT(S) AFFECTED: CA Datacom/AD Release 14.0 AD 21 Copyright (C) 2013 CA. All rights reserved. R00010-AAX140-SP1 DESC(CAAXSAMP AXRIM01 AND AXPOR02 JCL MEMBERS MINOR ERRORS). FMID (CAAXE00) PRE ( RO61813 ) SUP ( RO47028 TR46152 TR47028 TR63245 )

21 CA Datacom/AD CA RS PTF RO RO63315 RO63315 M.C.S. ENTRIES = ++PTF (RO63315) REDUCE OVERHEAD WHEN SHADOW MUF TAKES OVER FOR A FAILED MUF Running with a Shadow Multi-User Facility (MUF) has potential for unneeded overhead during a condition where it takes over for a failed MUF. This overhead involves the possible closing of datasets which delays completion of restart processing and so increases the time before the Shadow MUF is enabled for full processing. Overhead will also occur after MUF enable in opening any closed datasets that need not have been closed. Note that this overhead of closing datasets does not occur when using the MIGRATE_TO_SHADOW ability that enables the Shadow MUF without a restart process. Note also that this overhead occurs only for areas not subject to 'REDO' reprocessing of the log records done to rebuild the pipeline of maintenance in the failed MUF. If all or most areas have reprocessing, then the overhead is none or little. The Shadow MUF takeover restart processing requires more processing and elapsed time than is needed or intended. The Shadow MUF takeover restart processing requires more processing and elapsed time than is needed. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4817 ABEND IN MODULE DBMFRPR WITH CA DATACOM STAR IN USE An abend in module DBMFRPR may occur while trying to restart a Multi-User Facility (MUF) that includes the startup parameter DATACOM STAR. The problem occurs while trying to resolve inflight two-phase commit transactions. When attempting to start MUF, the RESTART phase may fail with an S806 return code or S0C1 at location x' '. The CA Datacom STAR MUF restart will fail. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4622 Copyright (C) 2013 CA. All rights reserved. R00483-DCM140-SP1 DESC(REDUCE OVERHEAD WHEN SHADOW MUF TAKES OVER FOR A FAILED MUF). FMID (CABDE00) PRE ( RO33960 RO61435 ) SUP ( RO35033 TR35033 TR63315 )

22 CA Datacom/AD CA RS PTF RO RO63454 RO63454 M.C.S. ENTRIES = ++PTF (RO63454) RETURN CODE 13(017) DOING INDEX QUEUE PROCESSING This solution resolves a problem with a 13(017) return code doing index queue processing in the CA Datacom Multi-User Facility (MUF). A RC 13(017) can occur when MUF is doing index queue processing. DB02405I - PXX START ***QUEUE 0 13(017) QUEUE-nn- D-nn If queue processing is not able to complete due to the 13(17) error, performance could eventually degrade. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4834 IMPROVE LONG RUNNING MUF INDEX QUEUE PROCESSES The Mutli-User Facility (MUF) index queue process can run a very long time if one area in a database is being null loaded while many rows are being added to a different area in the same database. COMM STATUS displays show an index queue process that has been running for many minutes or sometimes several hours. The long running queue process consumes resources from MUF that could be used for other tasks. Do not run the high volume add processes at the same time as a NULL load. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 DB 4480 Copyright (C) 2013 CA. All rights reserved. R00484-DCM140-SP1 DESC(RETURN CODE 13(017) DOING INDEX QUEUE PROCESSING). FMID (CABDE00) PRE ( RO37617 RO44821 RO47505 RO49554 RO49884 RO52117 RO56209 RO59522 ) SUP ( RO32494 RO34555 RO35564 RO36140 RO41379 RO43822 RO49898 RO60761 RO61183 RO62077 TR32494 TR34084 TR34555 TR35564 TR36140 TR41379 TR43822 TR49898 TR60761 TR61183 TR62077 TR63454 )

23 CA Datacom/AD CA RS PTF RO RO63552 RO63552 M.C.S. ENTRIES = ++PTF (RO63552) CA EXAMINE MODULE MISSING FROM CABDLPA The CA Auditor module is missing from the CABDLPA data set. The CA Datacom/DB release cannot be verified by CA Auditor. The impact is very low, since CA Datacom product functionality is not affected. CA Auditor will not be able to detect the presence of CA Datacom in the environment. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4741 Copyright (C) 2013 CA. All rights reserved. R00485-DCM140-SP1 DESC(CA EXAMINE MODULE MISSING FROM CABDLPA). FMID (CABDE00) SUP ( TR53323 TR63552 )

24 CA Datacom/AD CA RS PTF RO RO63572 RO63572 M.C.S. ENTRIES = ++PTF (RO63572) SQLCODE -39 IN PXX WITH POSITIVE/UNSIGNED PREDICATES The SQL PXX file contains SQLCODE -39 errors when predicates use a negative value to compare against unsigned or positive only columns. This error is ignored and the query succeeds. This solution only eliminates the SQL error output in the PXX. Also, a join of a negative value to a positive only column previously gave SQLCODE -39 NEGATIVE RESULT FOR UNSIGNED DECIMAL TARGET; but it will now receive no error, and just not find a matching row. 1. Unneeded SQL error summaries for SQLCODE -39 appear in the SQL PXX file. 2. Join query with negative source value will complete without error. Impact is low since the error is ignored. Redefine the POSITIVE ONLY column as DATATYPE SENSITIVE in the index definition. PRODUCT(S) AFFECTED: CA Datacom SQL Release 14.0 SQL 1914 Copyright (C) 2013 CA. All rights reserved. R00486-DCM140-SP1 DESC(SQLCODE -39 IN PXX WITH POSITIVE/UNSIGNED PREDICATES). FMID (CAVEE00) PRE ( RO42592 RO50843 RO51307 RO53622 RO55447 ) SUP ( RO34399 RO34896 RO60528 TR34399 TR34896 TR60528 TR63572 )

25 CA Datacom/AD CA RS PTF RO RO63722 RO63722 M.C.S. ENTRIES = ++PTF (RO63722) INTERNAL ERROR ATTEMPTING TO START STAR MUF Task areas associated with CA Datacom STAR (STAR) can be detached while still needed by incoming remote transactions when attempting to start a Multi-User Facility (MUF) that specifies a SYSIN parameter of DATACOM STAR and that uses XCF communication. An internal error will occur in DMDPRPR or DMBLDPR. An example is: DM01500C - INTERNAL ERROR IN DMDPRPR AT OFFSET xxxx The xxxx will vary, depending on many circumstances. A STAR MUF restart can fail, or MUF can fail to connect to other STAR MUFs. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4623 LAST FEW CHARACTERS IN MESSAGE DB00501E SOMETIMES TRUNCATED The last few characters in the CA Datacom/DB DB00501E message may be truncated if the Multi-User Facility (MUF) startup option 'MUFMSG' is set to YES,YES,YES. The truncation only occurs on 43(nnn) and 72(002) return code errors. When a return code 43(nnn) or 72(002) error is received, the last few characters in the DB00501E are missing. The number of characters depends on the length of the MUFNAME that is in the message header when YES,YES,YES is specified for the MUFMSG startup option. Identifying the cause of the error condition is more time consuming due to the information at the end of the DB00501E message not being complete. One or more of the MUFMSG startup options could be set to NO in order to shorten the message header such that the message no longer gets truncated. Caution needs to be taken if this is done as shifting the message content to the left could impact automated operation functionality. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4842 Copyright (C) 2013 CA. All rights reserved. R00488-DCM140-SP1 DESC(INTERNAL ERROR ATTEMPTING TO START STAR MUF). FMID (CABDE00) PRE ( RO34871 RO35657 RO36631 RO40587 RO47507 RO47843 RO53059 RO56818 RO59348 RO60055 RO60293 ) SUP ( RO33689 RO33789 RO35457 RO36866 RO45503 RO46364 RO48459 RO52366 RO53406 RO53483 RO53774 RO53902 RO58531 TR33689 TR33789 TR35457 TR36866 TR45503 TR46364 TR48434 TR48459 TR51219 TR52366 TR52441 TR52482 TR53404 TR53406 TR53483 TR53774 TR53902 TR58040 TR58531 TR63722 )

26 CA Datacom/AD CA RS PTF RO RO63772 RO63772 M.C.S. ENTRIES = ++PTF (RO63772) SPORADIC DBMUFPR ABEND DURING EOJ CLEANUP The CA Datacom/DB Multi-User Facility (MUF) can sporadically abend during EOJ cleanup processing. MUF validates the ASID of any user tasks needing to be posted. If this validation fails, module DBPCCPR takes a bad branch resulting in unpredictable abends. When DBPCCPR branches to an arbitrary address, MUF abends with unpredictable abend codes. There is an outage of MUF. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4847 Copyright (C) 2013 CA. All rights reserved. R00489-DCM140-SP1 DESC(SPORADIC DBMUFPR ABEND DURING EOJ CLEANUP). FMID (CABDE00) PRE ( RO33475 RO34871 RO47507 ) SUP ( TR63772 ) ++HOLD (RO63772) SYSTEM FMID(CABDE00) REASON (ACTION ) DATE (13291) COMMENT ( Product: CA Datacom/DB Release 14.0 Sequence: After applying this solution, you must re-execute CAIRIM. Purpose: Module DBPCCPR must be re-installed via CAIRIM for the solution to take effect. Relevance: The solution will not take effect until module DBPCCPR has been re-installed. Knowledge required: 1. Product administration 2. SMP/E Access required: Product libraries. Steps to Perform: Execute CAIRIM (see sample INSTJCL member BDRIM01) to re-install module DBPCCPR. Please also see the Product Documentation Change (PDC) published as RI ).

27 CA Datacom/AD CA RS PTF RO RO63961 RO63961 M.C.S. ENTRIES = ++PTF (RO63961) MINOR PERFORMANCE ENHANCEMENT FOR INDEX QUEUE PROCESSING This solution delivers a minor enhancement that will improve performance of Index Queue processing. This is an enhancement. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4843 Copyright (C) 2013 CA. All rights reserved. R00491-DCM140-SP1 DESC(MINOR PERFORMANCE ENHANCEMENT FOR INDEX QUEUE PROCESSING). FMID (CABDE00) PRE ( RO37617 RO44821 RO47505 RO49554 RO49884 RO56209 RO59522 RO61183 RO63454 ) SUP ( RO32494 RO35564 RO43822 RO49898 TR32494 TR35564 TR43822 TR49898 TR63961 )

28 CA Datacom/AD CA RS PTF RO RO64065 RO64065 M.C.S. ENTRIES = ++PTF (RO64065) DBUTLTY REORG WITH MULTUSE=NO S0C4 ABEND Running DBUTLTY REORG and specifying MULTUSE=NO will cause DBUTLTY to get a S0C4 abend in module DBIDXPR near offset x'5f42' or DBROIPR near offset x'139e'. DBUTLTY will get a S0C4 abend in DBIDXPR at or near offset x'5f42' or in module DBROIPR near offset x'139e'. The user will be unable to run DBUTLTY REORG with MULTUSE=NO specified. This abend can be circumvented by running DBUTLTY REORG with MULTUSE=YES. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4849 Copyright (C) 2013 CA. All rights reserved. R00492-DCM140-SP1 DESC(DBUTLTY REORG WITH MULTUSE=NO S0C4 ABEND). FMID (CABDE00) PRE ( RO38425 RO47844 ) SUP ( TR64065 )

29 CA Datacom/AD CA RS PTF RO RO64298 RO64298 M.C.S. ENTRIES = ++PTF (RO64298) MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND - A JDBC application using TCP/IP protocol with a connection string such that a type 4 connection is invoked (JDBC:Datacom://xxxxxxxx:nnnn/ServerName=xx) can hang if a request is made where the total size of the transmitted data to the Mainframe type 4 connection exceeds A JDBC application using a Type 2 connection crashes if an internal buffer exceeds the maximum size of This can happen when an SQL query uses more than 300 parameter markers (?) in a parameterized query or if there are more than 300 columns in a result set. - An ODBC app issuing a SQLSetStmtAttr(handle,SQL_ATTR_ROWS_FETCHED_PTR) always gets a returned value of zero which can result in the application not fetching any rows when there are rows returned. This is an application dependent function not related to the rows actually being present. - An ODBC application crashes when an internal buffer exceeds the maximum size of This can happen when an SQL query uses more than 300 parameter markers (?) in a parameterized query or when there are more than 300 columns in a result set. - A JDBC application that uses a Type 4 driver connection will stop responding and appear to hang and the connection in the Server Mainframe region will be terminated. - An application that uses a Type 2 driver connection or an ODBC application will crash with EXCEPTION_ACCESS_VIOLATION. A Java HotSpot error log indicates the Problematic frame is cadcdb32.dll or cadcdb64.dll. - For the SQL_ATTR_ROWS_FETCHED_PTR value being set to zero the application can potentially return no rows during processing. Depending on the circumstances outlined above, the Server Proxy region may crash or loop; the Server Mainframe region may loop; or the JDBC or ODBC application may crash or loop. The Datacom MUF region is not affected. In JDBC applications, use a CCI connection rather than TCP/IP. For ODBC applications there is no circumvention. PRODUCT(S) AFFECTED: CA Datacom Server Version 14.0 COMPONENTS AFFECTED: cadcjdbc.jar Driver Version: cadcdb32 cadcdb64 libcadcdb64.so libcadcdb32.so DBSRV 568 Copyright (C) 2013 CA. All rights reserved. R00105-DSR140-SP1 DESC(MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND). FMID (CAYTE00) PRE ( RO52942 RO53293 RO54082 RO54856 RO55939 ) SUP ( RO56798 RO62980 TR54612 TR54657 TR54710 TR56798 TR62980 TR64298 ) ++IF FMID(CAYTE02) REQ( RO64299).

30 CA Datacom/AD CA RS PTF RO RO64299 RO64299 M.C.S. ENTRIES = ++PTF (RO64299) MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND - A JDBC application using TCP/IP protocol with a connection string such that a type 4 connection is invoked (JDBC:Datacom://xxxxxxxx:nnnn/ServerName=xx) can hang if a request is made where the total size of the transmitted data to the Mainframe type 4 connection exceeds A JDBC application using a Type 2 connection crashes if an internal buffer exceeds the maximum size of This can happen when an SQL query uses more than 300 parameter markers (?) in a parameterized query or if there are more than 300 columns in a result set. - An ODBC app issuing a SQLSetStmtAttr(handle,SQL_ATTR_ROWS_FETCHED_PTR) always gets a returned value of zero which can result in the application not fetching any rows when there are rows returned. This is an application dependent function not related to the rows actually being present. - An ODBC application crashes when an internal buffer exceeds the maximum size of This can happen when an SQL query uses more than 300 parameter markers (?) in a parameterized query or when there are more than 300 columns in a result set. - A JDBC application that uses a Type 4 driver connection will stop responding and appear to hang and the connection in the Server Mainframe region will be terminated. - An application that uses a Type 2 driver connection or an ODBC application will crash with EXCEPTION_ACCESS_VIOLATION. A Java HotSpot error log indicates the Problematic frame is cadcdb32.dll or cadcdb64.dll. - For the SQL_ATTR_ROWS_FETCHED_PTR value being set to zero the application can potentially return no rows during processing. Depending on the circumstances outlined above, the Server Proxy region may crash or loop; the Server Mainframe region may loop; or the JDBC or ODBC application may crash or loop. The Datacom MUF region is not affected. In JDBC applications, use a CCI connection rather than TCP/IP. For ODBC applications there is no circumvention. PRODUCT(S) AFFECTED: CA Datacom Server Version 14.0 COMPONENTS AFFECTED: cadcjdbc.jar Driver Version: cadcdb32 cadcdb64 libcadcdb64.so libcadcdb32.so DBSRV 568 Copyright (C) 2013 CA. All rights reserved. R00105-DSR140-SP1 DESC(MF/USS: JDBC TYPE 4/PROXY HANGS/CRASHES; NO ROWS FOUND). FMID (CAYTE02) PRE ( RO40499 RO41066 RO42673 RO42697 RO43168 RO45190 RO45595 RO45733 RO47379 RO51470 RO52943 RO60149 RO61746 ) SUP ( RO28666 RO37945 RO37947 RO40718 RO44442 RO44975 RO46759 RO57771 RO58535 TR28666 TR35652 TR35761 TR37911 TR37934 TR37935 TR37945 TR37947 TR38072 TR40718 TR43223 TR44442 TR44618 TR44975 TR46759 TR57771 TR58535 TR64299 ) ++IF FMID(CAYTE00) REQ( RO64298). BINARY LINK('libcadcdb32.so') PARM(PATHMODE(0,7,7,5),APF,PROGCTL). BINARY LINK('libcadcdb64.so') PARM(PATHMODE(0,7,7,5),APF,PROGCTL).

31 CA Datacom/AD CA RS PTF RO64299 LINK('cadcjdbc.jar') PARM(PATHMODE(0,7,7,7)). LINK('cadcjdoc.jar') PARM(PATHMODE(0,7,7,7)).

32 CA Datacom/AD CA RS PTF RO RO64338 RO64338 M.C.S. ENTRIES = ++PTF (RO64338) IXX TYPE B REPORT GETS A RETURN CODE 03(027) This solution corrects a problem that causes return code 03(027) to be returned when running DBUTLTY to do an IXX TYPE B report. This will only occur when the length of the key definition information in the CXX exceeds a certain size. The DBUTLTY job will get the following error: DB13001E - UNEXPECTED RETURN CODE 03 (27) KEY NAME NOT IN CXX The user will be unable to run an IXX TYPE B report. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4647 Copyright (C) 2013 CA. All rights reserved. R00495-DCM140-SP1 DESC(IXX TYPE B REPORT GETS A RETURN CODE 03(027)). FMID (CABDE00) PRE ( RO36034 RO38446 RO47505 RO48058 RO50927 RO54630 RO62605 ) SUP ( RO50288 TR45607 TR50288 TR64338 )

33 CA Datacom/AD CA RS PTF RO RO64558 RO64558 M.C.S. ENTRIES = ++PTF (RO64558) MUF S0C4 ABEND DBIDXPR+5D22 USING MUFPLEX This solution corrects a problem that causes the Multi-User Facility (MUF) to get a S0C4 abend in module DBIDXPR near offset x'5d22' when using MUFplex. The problem occurs under very narrow circumstances, so we believe it would occur very rarely. The MUF will get a S0C4 abend in module DBIDXPR near offset x'5d22'. A MUF outage will occur. Avoid the use of MUFplex if possible until applying this solution. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4846 Copyright (C) 2013 CA. All rights reserved. R00498-DCM140-SP1 DESC(MUF S0C4 ABEND DBIDXPR+5D22 USING MUFPLEX). FMID (CABDE00) PRE ( RO37617 RO44821 RO47505 RO49554 RO49884 RO56209 RO59522 RO61183 RO63454 ) SUP ( RO32494 RO35564 RO43822 RO49898 RO63961 TR32494 TR35564 TR43822 TR49898 TR63961 TR64558 )

34 CA Datacom/AD CA RS PTF RO RO64787 RO64787 M.C.S. ENTRIES = ++PTF (RO64787) SHADOW MUF INCORRECTLY SHOWS ENABLED YEAR OF 2000 When a Shadow MUF takes over from a primary Multi-User Facility (MUF) after a 'MIGRATE_TO_SHADOW' command is issued on the primary MUF, its 'START' date always shows an invalid year of 2000 via CA Sysview or CA Dynamic System Tables. 1) If a user runs a query against the MUF_TABLE_STATS system, column BEGIN_TIME will show <2000-mm-dd-hh.mm.ss.ms>. Note that YY is the only portion which is invalid. 2) Sysview screen DCTABREQ also shows an invalid date as above. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4854 Copyright (C) 2013 CA. All rights reserved. R00500-DCM140-SP1 DESC(SHADOW MUF INCORRECTLY SHOWS ENABLED YEAR OF 2000). FMID (CABDE00) PRE ( RO34871 RO63823 ) SUP ( RO53666 TR53666 TR64787 )

35 CA Datacom/AD CA RS PTF RO RO65436 RO65436 M.C.S. ENTRIES = ++PTF (RO65436) SQL RETURN CODE -165 ON DDTRSLM IMPORT Executing the CA Datacom Datadictionary utility DDTRSLM to Import tables with referential (foreign key) constraints results in a -165 return code from SQL when SET IMPORT COLLISION REPLACE is specified to replace objects that already exist. DDTRSLM is executed to import a large number of tables that have foreign key constraints associated with them. This results in a -165 return code from SQL if the tables and associated referential constraints already exist in the target dictionary: DDTRS0016E DBQEXEI FAILED SQL COMMAND QEXEI, RC: SQL ERROR MESSAGE: DUPLICATE CONSTRAINT NAME: authid.constraint_name The import cannot be completed so the impact is significant. Execute the Import job a second time. The second execution will be successful. PRODUCT(S) AFFECTED: CA Datacom Datadictionary Release 14.0 DD 2067 Copyright (C) 2013 CA. All rights reserved. R00503-DCM140-SP1 DESC(SQL RETURN CODE -165 ON DDTRSLM IMPORT). FMID (CAADE00) PRE ( RO41344 RO42501 RO54667 ) SUP ( RO36555 RO41801 RO44161 RO48812 RO49924 RO54956 TR36555 TR41801 TR44161 TR48812 TR49924 TR54956 TR64758 TR65436 )

36 CA Datacom/AD CA RS PTF RO RO65555 RO65555 M.C.S. ENTRIES = ++PTF (RO65555) CXX STATS ON DASD TO BE UPDATED EVERY 24 HOURS FROM MEMORY CXX statistical information (such as the number of records in a table) could be lost in the case of a failed Multi-User Facility (MUF) or a MUF failover if the SIMPLIFY option is not in use. This solution delivers a minor enhancement to update DASD CXX statistics daily if the History Database is in use. A CXX report may not reflect the correct statistical information, especially when databases stay open for long periods of time. Issue the following command as often as you would like to update CXX statistics from memory onto dasd: COMM STATS,DBID=ALL PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4857 Copyright (C) 2013 CA. All rights reserved. R00505-DCM140-SP1 DESC(CXX STATS ON DASD TO BE UPDATED EVERY 24 HOURS FROM MEMORY). FMID (CABDE00) SUP ( TR65555 )

37 CA Datacom/AD CA RS PTF RO RO65595 RO65595 M.C.S. ENTRIES = ++PTF (RO65595) TTM BLOCKS HUNG AND COUNTERS INCORRECT TTM Blocks can become 'hung' and may not be released for queries that contain subqueries. Also, some counters in the SQL_STATUS table show incorrect values including CURSORS_OPEN and TASKS_ACTIVE. The SQL_STATUS table shows a large number for TTM_BLKS_IN_USE, CURSORS_OPEN, or TASKS_ACTIVE. The TTM area could potentially fill up, and incorrect values are displayed for the SQL_STATUS table. PRODUCT(S) AFFECTED: CA Datacom SQL Release 12.0 CA Datacom SQL Release 14.0 SQL 1917 Copyright (C) 2013 CA. All rights reserved. R00507-DCM140-SP1 DESC(TTM BLOCKS HUNG AND COUNTERS INCORRECT). FMID (CAVEE00) PRE ( RO34410 RO34438 RO34590 RO40578 RO41475 RO42275 RO42439 RO51307 RO56904 RO57814 RO59167 RO60006 ) SUP ( AR41475 AR42275 AR46161 RO35606 RO40967 RO42352 RO46161 RO48579 RO58791 RO59917 TR35606 TR40967 TR42352 TR46161 TR48579 TR57640 TR58791 TR59917 TR65595 )

38 CA Datacom/AD CA RS PTF RO RO65632 RO65632 M.C.S. ENTRIES = ++PTF (RO65632) VARIOUS SQL ERRORS ON DDTRSLM IMPORT When executing the CA Datacom Datadictionary utility DDTRSLM to IMPORT an SQL object, various SQL return codes may be reported. The return code will vary, depending on the entity being transported. Executions of DDTRSLM to accomplish the IMPORT of an SQL object may generate the following error message: DDTRS0016E DBQxxxx FAILED SQL COMMAND yyyyy, RC: -rrr where xxxx is the failing routine within the utility, yyyyy is the SQL command being processed (such as QPRPS), and rrr is the return code returned to DDTRSLM by SQL. Each component of the message may vary based on the SQL object being transported. Return codes -276 and -20 have been seen, but others are possible. The IMPORT cannot be accomplished due to the SQL error. PRODUCT(S) AFFECTED: CA Datacom Datadictionary Release 12.0 DD 2059 Copyright (C) 2013 CA. All rights reserved. R00508-DCM140-SP1 DESC(VARIOUS SQL ERRORS ON DDTRSLM IMPORT). FMID (CAADE00) PRE ( RO41344 RO42501 RO54667 ) SUP ( RO36555 RO41801 RO44161 RO48812 RO49924 RO54956 RO65436 TR36555 TR41801 TR44161 TR48812 TR49924 TR54956 TR64758 TR65436 TR65632 )

39 CA Datacom/AD CA RS PTF RO RO65733 RO65733 M.C.S. ENTRIES = ++PTF (RO65733) SPORADIC DELAY OF OPEN/CLOSE WITH STAR CA Datacom/DB (DB) can sporadically experience a delay in OPEN/CLOSE processing when CA Datacom STAR (STAR) is active. The affected task shows a command of OPEN or CLOSE and a status of "WAIT STAR" in DB's COMM STATUS display. The wait or temporary hang clears up as soon as another OPEN or CLOSE is issued on some other task in DB. The delay has been observed ranging from a few seconds to a couple of minutes. Instances of such delays are more likely to occur in a system that issues many OPEN/CLOSE requests simultaneously. However, these delays are also generally shorter in a system that issues OPEN/CLOSE frequently. A DB task temporarily hangs in status "WAIT STAR". The hang ends when another task issues an OPEN or CLOSE. Sporadic delays in OPEN/CLOSE processing causing applications to wait and therefore occasionally perform slower than expected. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4860 Copyright (C) 2013 CA. All rights reserved. R00509-DCM140-SP1 DESC(SPORADIC DELAY OF OPEN/CLOSE WITH STAR). FMID (CABDE00) PRE ( RO47507 RO59348 RO63722 ) SUP ( RO48459 RO52366 TR48434 TR48459 TR52366 TR65733 )

40 CA Datacom/AD CA RS PTF RO RO65864 RO65864 M.C.S. ENTRIES = ++PTF (RO65864) DECIMAL FIELDS DISPLAY INCORRECTLY IN COBOL A packed decimal field defined with a length greater than nine will not display properly when executing the CA Datacom Datadictionary DDUTILTY to produce a COBOL copybook. Symptoms: A user defines a packed decimal field with a length greater than nine bytes. The precision is calculated correctly for the field, but a COBOL copybook will display the field as having a maximum length of eighteen when adding the number of decimal positions to the right and left of the decimal point. For example, a packed decimal field is defined as 11 bytes in length with decimals = 002 and is signed. The copybook picture clause generated by DDUTILTY is: PIC S9(16)V9(2). To match the precision and scale defined in dictionary, it would be: PIC S9(19)V9(2). If used in a COBOL program as produced by the Source Language Generator, the data returned will not be intepreted correctly by the executing program. The copybook can be manually updated prior to inclusion in a program. PRODUCT(S) AFFECTED: CA Datacom Datadictionary Release 12.0 CA Datacom Datadictionary Release 14.0 DD 2060 Copyright (C) 2013 CA. All rights reserved. R00510-DCM140-SP1 DESC(DECIMAL FIELDS DISPLAY INCORRECTLY IN COBOL). FMID (CAADE00) SUP ( RO36763 TR36763 TR65864 )