CA Datacom/DB 14.0 1 CA RS 1602 Service List Description Type 14.0 RO86865 S0C4 IN DBSRPPR SYSVIEW+001750 PTF RO87076 DBSQLPR S0C4 WITH LARGE OUTPUT REQUESTED PTF RO87316 DB CONSOLE COMMAND "QUIESCE RST" HANGS MUF PTF RO87334 MESSAGE DB00506C AND APPLICATION HANG *HIP/PRP* RO87343 DDSDCLM GIVES INVALID IIN RC ON VERIFY FUNCTION PTF RO87443 DBUTLTY REPORT TYPE=H DOESN'T SHOW RETIX WITH SORT=0 PTF RO87668 DDRTVCAT GETS INVALID DATABASE NAME ERROR PTF The CA RS 1602 service count for this release is 7
CA Datacom/DB 2 CA RS 1602 Service List for CAADE00 FMID Service Description Type CAADE00 RO87343 DDSDCLM GIVES INVALID IIN RC ON VERIFY FUNCTION PTF RO87668 DDRTVCAT GETS INVALID DATABASE NAME ERROR PTF The CA RS 1602 service count for this FMID is 2
CA Datacom/DB 3 CA RS 1602 Service List for CABDE00 FMID Service Description Type CABDE00 RO87316 DB CONSOLE COMMAND "QUIESCE RST" HANGS MUF PTF RO87334 MESSAGE DB00506C AND APPLICATION HANG *HIP/PRP* RO87443 DBUTLTY REPORT TYPE=H DOESN'T SHOW RETIX WITH SORT=0 PTF The CA RS 1602 service count for this FMID is 3
CA Datacom/DB 4 CA RS 1602 Service List for CAVEE00 FMID Service Description Type CAVEE00 RO86865 S0C4 IN DBSRPPR SYSVIEW+001750 PTF RO87076 DBSQLPR S0C4 WITH LARGE OUTPUT REQUESTED PTF The CA RS 1602 service count for this FMID is 2
CA Datacom/DB 14.0 5 CA RS 1602 - PTF RO86865 14.0 RO86865 RO86865 M.C.S. ENTRIES = ++PTF (RO86865) S0C4 IN DBSRPPR SYSVIEW+001750 In certain cases, a SELECT * FROM SYSADM.SQL_STATUS_CURRENT Dynamic System Table (DST) can cause the MultiUser Facility (MUF) to abnormally terminate. A S0C4 abend occurs in DBSRPPR member SYSVIEW at offset x'001750'. MUF must be restarted. Do not query the SYSADM.SQL_STATUS_CURRENT DST. CA Datacom SQL Version 14.0 CA Datacom SQL Version 15.0 SQL 2035 Copyright (C) 2016 CA. All rights reserved. R00864-DCM140-SP1 DESC(S0C4 IN DBSRPPR SYSVIEW+001750). FMID (CAVEE00) SUP ( AR58696 RO57691 RO58696 RO71847 TR57691 TR58696 TR71847 TR86865 )
CA Datacom/DB 14.0 6 CA RS 1602 - PTF RO87076 14.0 RO87076 RO87076 M.C.S. ENTRIES = ++PTF (RO87076) DBSQLPR S0C4 WITH LARGE OUTPUT REQUESTED When DBSQLPR runs and the output is greater than 1500 characters, it can overrun the output buffer, causing a S0C4 abend. The program, DBSQLPR, abends with a S0C4. The program ends with an abend, so no data is returned. None. CA Datacom SQL Version 14.0 CA Datacom SQL Version 15.0 SQL 2031 Copyright (C) 2016 CA. All rights reserved. R00867-DCM140-SP1 DESC(DBSQLPR S0C4 WITH LARGE OUTPUT REQUESTED). FMID (CAVEE00) PRE ( RO40578 RO40623 RO45087 RO47621 RO51838 RO71273 ) SUP ( RO36556 RO36943 RO41794 RO42461 RO43495 RO44080 RO46449 RO49565 RO85188 TR36556 TR36943 TR41794 TR42461 TR43495 TR44080 TR46449 TR49565 TR51194 TR83734 TR85069 TR85188 TR87076 ) ++HOLD (RO87076) SYSTEM FMID(CAVEE00) REASON (DOC ) DATE (16020) COMMENT ( +----------------------------------------------------------------------+ CA Datacom SQL Release 14.0 +----------------------------------------------------------------------+ *************************** * PUBLICATION * *************************** For documentation on the changes to DBSQLPR options PRTWDITH and DATASEPARATOR delivered by this PTF, please see Product Documentation Change (PDC) Informational Solution RI87626. ).
CA Datacom/DB 14.0 7 CA RS 1602 - PTF RO87316 14.0 RO87316 RO87316 M.C.S. ENTRIES = ++PTF (RO87316) DB CONSOLE COMMAND "QUIESCE RST" HANGS MUF In rare circumstances, the seldom-used COMM QUIESCE RST command can cause the Multi-User Facility (MUF) to hang. The special processing command COMM QUIESCE RST is used when a MUF has been executing for a very long time and the sequential number used to track current log blocks nears 4 billion. This occurrence is very rare and is typically only seen in very active MUFs. The COMM QUIESCE RST command causes a slight pause in the MUF processing, so the log sequence number can be reset. When a QUIESCE RST console command is received, the MUF will respond with message: DB02901I MUF QUIESCE RST STARTING The process should end within a few seconds and should then be followed by message: DB02904I MUF QUIESCE RST ENDED Instead, this message is never issued and the MUF hangs indefinitely. There is an outage of the MUF, since it becomes unusable and must be recycled. None. CA Datacom/DB Version 14.0 CA Datacom/DB Version 15.0 DB 5128 Copyright (C) 2016 CA. All rights reserved. R00870-DCM140-SP1 DESC(DB CONSOLE COMMAND "QUIESCE RST" HANGS MUF). FMID (CABDE00) PRE ( RO35280 RO48653 RO51924 RO61435 RO62605 RO71451 RO74874 RO77961 RO78319 RO79202 RO80968 ) SUP ( RC57573 RO34971 RO35392 RO35611 RO76683 TR34971 TR35360 TR35392 TR35611 TR76683 TR87316 )
CA Datacom/DB 14.0 8 CA RS 1602 - PTF RO87334 14.0 RO87334 RO87334 M.C.S. ENTRIES = ++PTF (RO87334) MESSAGE DB00506C AND APPLICATION HANG After applying PTF RO80232 in Version 14.0 or RO85869 in Version 15.0 and reloading the corresponding module DBPCCPR via a CAIRIM execution, applications can receive message: DB00506C - REQUEST RETURN HANDLER FAILURE, ECB This message implies that the application cannot be posted to run, and therefore it hangs indefinitely. In certain cases, the message is issued in error and the application hangs even if it could have been posted to run. The error is sporadic and frequently does not recur when the application is submitted a second time. The corresponding solution only prevents the message and hang when it was issued in error. It will still be issued and posting will be bypassed when the application truly cannot be posted, for instance, when it was cancelled while processing in the CA Datacom/DB Multi-User Facility. Applications sporadically receive message: DB00506C - REQUEST RETURN HANDLER FAILURE, ECB After this message has been issued, the application hangs indefinitely. Applications sporadically get hung up and do not finish processing. There is no systematic circumvention, but re-submitting the failing application is usually successful. Reducing the load on the system or an IPL can also be mitigating factors. CA Datacom/DB Version 14.0 CA Datacom/DB Version 15.0 DB 5135 Copyright (C) 2016 CA. All rights reserved. R00871-DCM140-SP1 DESC(MESSAGE DB00506C AND APPLICATION HANG). FMID (CABDE00) PRE ( RO33475 RO34871 RO47507 RO63772 ) SUP ( AR80232 RO80232 TR80232 TR87334 ) ++HOLD (RO87334) SYSTEM FMID(CABDE00) REASON (ACTION ) DATE (16007) COMMENT ( +----------------------------------------------------------------------+ CA Datacom/DB Release 14.0 +----------+-----------------------------------------------------------+ SEQUENCE After Apply +----------+-----------------------------------------------------------+ PURPOSE Module DBPCCPR must be re-installed via CAIRIM for the solution to take effect. +----------+-----------------------------------------------------------+ USERS AFFECTED All users. +----------+-----------------------------------------------------------+ KNOWLEDGE REQUIRED 1. Product administration 2. SMP/E +----------+-----------------------------------------------------------+ ACCESS REQUIRED
CA Datacom/DB 14.0 9 CA RS 1602 - PTF RO87334 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 RI47534. ).
CA Datacom/DB 14.0 10 CA RS 1602 - PTF RO87343 14.0 RO87343 RO87343 M.C.S. ENTRIES = ++PTF (RO87343) The following items are included in this solution: 1. DDSDCLM GIVES INVALID IIN RC ON VERIFY FUNCTION 2. ALLOW ERON OPTION IN DSF ========================================================================== DDSDCLM GIVES INVALID IIN RC ON VERIFY FUNCTION When executing the VERIFY function of the DDSDCLM batch utility an invalid error message may be returned. For example: **** ERROR **** RETURN CODE = DDPIIN0001 INVALID INDEX NAME The Detail Report following the message shows the attribute reported as erroneous is indeed valid. An error message is generated when executing the DDSDCLM VERIFY function, but the Detail Report following the message shows the attribute value to be correct. The DDSDCLM VERIFY function does not complete with a condition code of zero, possibly delaying the upgrade to a new release. None. CA Datacom Datadictionary Release 14.0 CA Datacom Datadictionary Version 15.0 DD 2135 ========================================================================== ALLOW ERON OPTION IN DSF In some cases use of the ATON and SFON trace options do not provide enough information to resolve the problem. When the ATON and SFON trace options are used to diagnose a problem they may not provide sufficient information in some cases. The primary impact is time required to resolve the problem. There is no circumvention. CA Datacom Datadictionary Release 14.0 CA Datacom Datadictionary Version 15.0 DD 2134 Copyright (C) 2016 CA. All rights reserved. R00872-DCM140-SP1 DESC(DDSDCLM GIVES INVALID IIN RC ON VERIFY FUNCTION). FMID (CAADE00) PRE ( RO38253 RO44743 RO67544 RO84636 ) SUP ( AC68557 AR67544 RO68211 RO68826 RO70208 RO83447 TR68211 TR68826 TR70208 TR83447 TR87343 )
CA Datacom/DB 14.0 11 CA RS 1602 - PTF RO87443 14.0 RO87443 RO87443 M.C.S. ENTRIES = ++PTF (RO87443) DBUTLTY REPORT TYPE=H DOESN'T SHOW RETIX WITH SORT=0 A CA Datacom/DB DBUTLTY TYPE=H function History Report does not reflect that a RETIX job ran without using SORT. In the Report under the header column "OTHER", "SORT=0" should be displayed when a RETIX or LOAD was executed without the SORT parameter or if SORT=0 was specified. The report correctly displays "SORT=0" for a non-sorted LOAD. REPORT TYPE=H for a DBID is not displaying "SORT=0" under the header column "OTHER" for a RETIX without the SORT parm or with SORT=0 specified on the control card. The report fails to indicate if the RETIX was sorted or non-sorted. None. CA Datacom/DB Version 14.0 CA Datacom/DB Version 15.0 DB 5136 Copyright (C) 2016 CA. All rights reserved. R00876-DCM140-SP1 DESC(DBUTLTY REPORT TYPE=H DOESN'T SHOW RETIX WITH SORT=0). FMID (CABDE00) PRE ( RO33475 RO33933 RO35803 RO36029 RO36984 RO37148 RO37575 RO51924 RO53265 RO68868 RO77511 RO78418 RO81739 RO83522 ) SUP ( RO35276 RO38329 RO83103 TR35276 TR38329 TR83103 TR87443 )
CA Datacom/DB 14.0 12 CA RS 1602 - PTF RO87668 14.0 RO87668 RO87668 M.C.S. ENTRIES = ++PTF (RO87668) DDRTVCAT GETS INVALID DATABASE NAME ERROR When using the Alternate Basis feature of DDRTVCAT the following message is returned if the Database Name in the Alternate Basis does not match either the Primary or Alternate Basis Name but the Primary Basis Name is correct. DDRTVT0003 DATABASE NAME INVALID The error message "DDRTVT0003 DATABASE NAME INVALID" is incorrectly produced when correctly using the Alternate Basis executing DDRTVCAT. The DDRTVCAT execution fails and the database cannot be cataloged. There is no circumvention. CA Datacom Datadictionary Release 14.0 CA Datacom Datadictionary Version 15.0 CA Datacom Datadictionary Release 15.1 DD 2138 Copyright (C) 2016 CA. All rights reserved. R00879-DCM140-SP1 DESC(DDRTVCAT GETS INVALID DATABASE NAME ERROR). FMID (CAADE00) PRE ( RO41344 ) SUP ( RO65981 TR65981 TR87668 )