CA Datacom/DB CA RS 1604 Service List

Transcription

1 CA Datacom/DB CA RS 1604 Service List Description Type 15.0 RO88293 DBUTLTY BACKUP FAILS WITH RC 21 WITH USER COMPRESSION *HIP/PRP* RO88365 ENHANCEMENT: DIAGNOSTIC FOR MEMORY USAGE PTF RO88391 S0C4 IN DBSRPPR WITH SMALL SQL_LRU_STATEMENT_CACHE PTF RO88393 S0C4 ABEND IN DBSRPPR QRYEXEC+00012E AFTER RO79732/RO83166 *HIP/PRP* RO88440 BLANK ERROR MESSAGE FOR SQLCODE -264 PTF RO88542 DDSDCLM GETS S0C4 WITH USER-DEFINED ENTITY PTF RO88616 S0C4 IN DBSRPPR SYSVIEW PTF RO88813 RARE DATA ROW CORRUPTION WHEN USING LOG_RECORD_FORMAT 1 *HIP/PRP* RO88868 FACILITATE TA24 COMPRESSION CHANGE WITH DDUPDATE PTF RO88875 DIAGNOSTIC FOR CDC PROBLEM ANALYSIS PTF RO88911 WORKAROUND FOR HUNG SQL PLAN LOCK INEFFECTIVE PTF RO88959 DATACOM/DB NOT PASSING ROW LENGTH TO READRXX ROUTINE PTF RO89021 DBUTLTY CXXCLONE/LOAD NOT HANDLING DBID RANGES CORRECTLY PTF RO89125 FATAL INTERNAL ERROR - XES-XXXX IN MUFPLEX PTF The CA RS 1604 service count for this release is 14

2 CA Datacom/DB 2 CA RS 1604 Service List for CAADF00 FMID Service Description Type CAADF00 RO88542 DDSDCLM GETS S0C4 WITH USER-DEFINED ENTITY PTF The CA RS 1604 service count for this FMID is 1

3 CA Datacom/DB 3 CA RS 1604 Service List for CABDF00 FMID Service Description Type CABDF00 RO88293 DBUTLTY BACKUP FAILS WITH RC 21 WITH USER COMPRESSION *HIP/PRP* RO88365 ENHANCEMENT: DIAGNOSTIC FOR MEMORY USAGE PTF RO88813 RARE DATA ROW CORRUPTION WHEN USING LOG_RECORD_FORMAT 1 *HIP/PRP* RO88868 FACILITATE TA24 COMPRESSION CHANGE WITH DDUPDATE PTF RO88875 DIAGNOSTIC FOR CDC PROBLEM ANALYSIS PTF RO88911 WORKAROUND FOR HUNG SQL PLAN LOCK INEFFECTIVE PTF RO88959 DATACOM/DB NOT PASSING ROW LENGTH TO READRXX ROUTINE PTF RO89021 DBUTLTY CXXCLONE/LOAD NOT HANDLING DBID RANGES CORRECTLY PTF RO89125 FATAL INTERNAL ERROR - XES-XXXX IN MUFPLEX PTF The CA RS 1604 service count for this FMID is 9

4 CA Datacom/DB 4 CA RS 1604 Service List for CAVEF00 FMID Service Description Type CAVEF00 RO88391 S0C4 IN DBSRPPR WITH SMALL SQL_LRU_STATEMENT_CACHE PTF RO88393 S0C4 ABEND IN DBSRPPR QRYEXEC+00012E AFTER RO79732/RO83166 *HIP/PRP* RO88440 BLANK ERROR MESSAGE FOR SQLCODE -264 PTF RO88616 S0C4 IN DBSRPPR SYSVIEW PTF The CA RS 1604 service count for this FMID is 4

5 CA Datacom/DB CA RS PTF RO RO88293 RO88293 M.C.S. ENTRIES = ++PTF (RO88293) The following items are included in this solution: 1. DBUTLTY BACKUP FAILS WITH RC 21 WITH USER COMPRESSION 2. RETIX S0C4 IN DBCL1PR DUE TO STORAGE OVERLAY 3. DBUTLTY EXTRACT SEQ=PHYSICAL ABORTS WITH RC 51(1) ========================================================================== DBUTLTY BACKUP FAILS WITH RC 21 WITH USER COMPRESSION CA Datacom DBUTLTY functions running in the CA Datacom/DB Multi-User Facility (MUF) and also application programs can fail with return code 21 (compression error) when accessing tables with User Compression. This can occur when some or all of the solutions related to TA24 (Table Alter 24X7) are applied. The problem does not affect PRESSPAK, DB compression or tables with compression exit DBVVRPR (VSAM variable records). Users experience RC 21(73) or 21(74) during DBUTLTY BACKUP or DB applications running inside MUF. Some DBUTLTY functions and applications do not execute successfully for tables with User Compression. For DBUTLTY BACKUP: specify CMPRS=NO, i.e. run BACKUP uncompressed. DB 5113 ========================================================================== RETIX S0C4 IN DBCL1PR DUE TO STORAGE OVERLAY CA Datacom/DB DBUTLTY RETIX may abort with a S0C4 in module DBCL1PR. This can occur if the associated Multi-User Facility (MUF) has been activated with the SIMPLIFY feature. DBUTLTY RETIX aborts with a SC04 abend in module DBCL1PR. DBUTLTY RETIX against certain areas or bases may fail when running the MUF in SIMPLIFY mode. None. DB 5125 ========================================================================== DBUTLTY EXTRACT SEQ=PHYSICAL ABORTS WITH RC 51(1) CA Datacom/DB DBUTLTY EXTRACT with SEQ=PHYSICAL aborts with RC 51(01) if the Multi-User Facility (MUF) has been activated with the SIMPLIFY feature. DBUTLTY EXTRACT SEQ=PHYSICAL aborts with the following message: DB13001E - UNEXPECTED RETURN CODE 51 (1) INVALID MIX OF DATACOM/DB UTILITIES In SIMPLIFY mode, DBUTLTY EXTRACT cannot be used to retrieve data in PHYSICAL sequence. DBUTLTY EXTRACT with SEQ=NATIVE provides a possible circumvention. DB 5137 Copyright (C) 2016 CA. All rights reserved. R00268-DCM150-SP2

6 CA Datacom/DB CA RS PTF RO88293 DESC(DBUTLTY BACKUP FAILS WITH RC 21 WITH USER COMPRESSION). FMID (CABDF00) PRE ( RO68861 RO72197 RO72240 RO72244 RO77059 RO81127 RO81931 RO82864 RO83027 RO85366 RO85408 ) SUP ( DC80958 JC80958 RO74016 RO74448 RO76058 RO81525 RO83425 RO84293 TR74016 TR74448 TR76058 TR81525 TR83425 TR84293 TR88293 )

7 CA Datacom/DB CA RS PTF RO RO88365 RO88365 M.C.S. ENTRIES = ++PTF (RO88365) ENHANCEMENT: DIAGNOSTIC FOR MEMORY USAGE ENHANCEMENT DESCRIPTION: This solution provides internal diagnostic information about memory usage by CA Datacom/DB. DB 5120 Copyright (C) 2016 CA. All rights reserved. R00270-DCM150-SP2 DESC(ENHANCEMENT: DIAGNOSTIC FOR MEMORY USAGE). FMID (CABDF00) PRE ( RO67423 RO72197 RO72240 RO72571 RO73777 RO77059 RO77246 RO83027 RO85408 RO87023 RO87938 ) SUP ( RO74018 RO81240 RO81820 TR74018 TR81240 TR81783 TR81820 TR88271 TR88365 )

8 CA Datacom/DB CA RS PTF RO RO88391 RO88391 M.C.S. ENTRIES = ++PTF (RO88391) S0C4 IN DBSRPPR WITH SMALL SQL_LRU_STATEMENT_CACHE The Multi-User Facility (MUF) ABENDs with a S0C4 in DBSRPPR in various modules with a small SQL_LRU_STATEMENT_CACHE set. The problem occurs when one task tries to copy a statement that another task is deleting from the cache. The MUF ABENDs with a S0C4 in DBSRPPR. Observed modules include STMTRELO and GETSTMT, but other modules may be possible. MUF must be restarted. Increase the size of the SQL_LRU_STATEMENT_CACHE. CA Datacom SQL Version 14.0 CA Datacom SQL Version 15.0 SQL 1990 Copyright (C) 2016 CA. All rights reserved. R00271-DCM150-SP2 DESC(S0C4 IN DBSRPPR WITH SMALL SQL_LRU_STATEMENT_CACHE). FMID (CAVEF00) PRE ( RO72175 ) SUP ( TR88391 )

9 CA Datacom/DB CA RS PTF RO RO88393 RO88393 M.C.S. ENTRIES = ++PTF (RO88393) S0C4 ABEND IN DBSRPPR QRYEXEC+00012E AFTER RO79732/RO83166 Beginning with RO79732 in 14.0 and RO83166 in 15.0, the MultiUser Facility (MUF) may abend if the cursor is in an invalid state and either detail-level execution-time messages are turned on, or DIAGOPTION A is turned on and an inefficient query triggers the SQL Optimization Execution-Time report. MUF abends with a S0C4 in DBSRPPR module QRYEXEC at offset x'00012e'. A MUF outage occurs. Turn off detailed execution-time messages and/or DIAGOPTION A. CA Datacom SQL Version 14.0 CA Datacom SQL Version 15.0 SQL 2036 Copyright (C) 2016 CA. All rights reserved. R00272-DCM150-SP2 DESC(S0C4 ABEND IN DBSRPPR QRYEXEC+00012E AFTER RO79732/RO83166). FMID (CAVEF00) PRE ( RO67512 RO83166 RO85846 ) SUP ( AR83166 RO78697 TR78697 TR88393 )

10 CA Datacom/DB CA RS PTF RO RO88440 RO88440 M.C.S. ENTRIES = ++PTF (RO88440) BLANK ERROR MESSAGE FOR SQLCODE -264 When a query returns a -264 SQLCODE error for an index that already exists, the error message information is missing. The user will see: MESSAGE = instead of MESSAGE = INDEX ALREADY EXISTS: authid.indexname The message for the SQLCODE -264 error is blank. It may take more time to figure out what the problem is or which index already exists. None. CA Datacom SQL Version 15.0 CA Datacom SQL Version 15.1 SQL 2043 Copyright (C) 2016 CA. All rights reserved. R00273-DCM150-SP2 DESC(BLANK ERROR MESSAGE FOR SQLCODE -264). FMID (CAVEF00) SUP ( TR88440 )

11 CA Datacom/DB CA RS PTF RO RO88542 RO88542 M.C.S. ENTRIES = ++PTF (RO88542) DDSDCLM GETS S0C4 WITH USER-DEFINED ENTITY Executing DDSDCLM with the -SDC nnn function against a DATA-DICT database with a user-defined entity in an area different from DATA-DICT-AREA-1 will get a S0C4 abend in DDSDCLM. A S0C4 abend occurs in DDSDCLM when executing a -SDC nnn function against a DATA-DICT database that includes a user-defined entity in an area other than the installed DD1 area (DATA-DICT-AREA-1). If the occurrence name of the AREA occurrence is later alphabetically than DATA-DICT-AREA-1, then the standard part of the database will have been correctly verified and any messages generated prior to the abend. If the AREA occurrence name is earlier alphabetically than DATA-DICT-AREA-1, then only the user-defined data is processed prior to the abend. The only circumvention is to move the used-defined entity under the standard area (DATA-DICT-AREA-1). CA Datacom Datadictionary Release 14.0 CA Datacom Datadictionary Version 15.0 CA Datacom Datadictionary Release 15.1 DD 2142 Copyright (C) 2016 CA. All rights reserved. R00274-DCM150-SP2 DESC(DDSDCLM GETS S0C4 WITH USER-DEFINED ENTITY). FMID (CAADF00) PRE ( RO87452 ) SUP ( RO83547 TR83547 TR88542 )

12 CA Datacom/DB CA RS PTF RO RO88616 RO88616 M.C.S. ENTRIES = ++PTF (RO88616) S0C4 IN DBSRPPR SYSVIEW 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. R00276-DCM150-SP2 DESC(S0C4 IN DBSRPPR SYSVIEW ). FMID (CAVEF00) SUP ( RO71850 TR71850 TR88616 )

13 CA Datacom/DB CA RS PTF RO RO88813 RO88813 M.C.S. ENTRIES = ++PTF (RO88813) RARE DATA ROW CORRUPTION WHEN USING LOG_RECORD_FORMAT 1 When using MUF option LOG_RECORD_FORMAT 1 it is possible to have a row set to incorrect data under extremely rare circumstances. These circumstances are complex and cannot be exactly described in detail, but they first involve an abend of the Datacom/DB Multi-User Facility (MUF) while maintenance transactions (ADDIT, UPDAT, DELET) are in flight and a particular pattern of data area blocks in memory versus data blocks written to DASD is present. When the MUF is brought back up, a ROLBK of a transaction that was subject to RESTART processing can result in the incorrect row data. A return code 13(69) is also possible. The problem is very unlikely to occur. A ROLBK after a MUF RESTART could leave invalid data in a row after an abnormal termination of the MUF. Data corruption is possible. None. DB 5127 Copyright (C) 2016 CA. All rights reserved. R00277-DCM150-SP2 DESC(RARE DATA ROW CORRUPTION WHEN USING LOG_RECORD_FORMAT 1). FMID (CABDF00) PRE ( RO77059 RO83027 RO86101 ) SUP ( KC80958 TR88813 )

14 CA Datacom/DB CA RS PTF RO RO88868 RO88868 M.C.S. ENTRIES = ++PTF (RO88868) FACILITATE TA24 COMPRESSION CHANGE WITH DDUPDATE ENHANCEMENT DESCRIPTION: Feature "Table Alter 24x7" (TA24, furnished by PTFs RO81761 and RO83027 for 14.0 and 15.0 respectively) provides the ability to change compression on a table while the table is actively being used. This is accomplished by CA Datadictionary program DDUPDATE using statements -UPD TABLE... and 1000 ALTER. Prior to this solution an edit prevented the ALTER from continuing if the Occurrence Name, Status or Version did not match the equivalent in the CXX. Cataloging the correct values to make them match requires closing the corresponding base and thus would cause an interruption contrary to the purpose of the TA24 feature. While the above edit, in addition to many others, all intend to provide maximum safety, it is not a true requirement in this case. The solution removes this particular edit so as to better facilitate change of table compression in 24x7 mode. DB 5133 Copyright (C) 2016 CA. All rights reserved. R00278-DCM150-SP2 DESC(FACILITATE TA24 COMPRESSION CHANGE WITH DDUPDATE). FMID (CABDF00) PRE ( RO72081 RO72240 RO72571 RO73777 RO77658 RO81931 ) SUP ( RO74060 RO82156 RO83799 TR72466 TR74060 TR82156 TR83799 TR88868 )

15 CA Datacom/DB CA RS PTF RO RO88875 RO88875 M.C.S. ENTRIES = ++PTF (RO88875) DIAGNOSTIC FOR CDC PROBLEM ANALYSIS This PTF will facilitate the analysis of problems pertaining to the Change Data Capture (CDC) feature of CA Datacom/DB. Not applicable. None. Not applicable. DB 5134 Copyright (C) 2016 CA. All rights reserved. R00279-DCM150-SP2 DESC(DIAGNOSTIC FOR CDC PROBLEM ANALYSIS). FMID (CABDF00) PRE ( RO72244 RO77059 ) SUP ( TR88875 )

16 CA Datacom/DB CA RS PTF RO RO88911 RO88911 M.C.S. ENTRIES = ++PTF (RO88911) WORKAROUND FOR HUNG SQL PLAN LOCK INEFFECTIVE For an unknown reason an SQL plan value lock may remain outstanding after a rebind of the plan completes. CA Datacom SQL support has provided a means of manually freeing this lock by inserting a row into the SYSADM.SQL_STATUS_PLAN Dynamic System Table. This insert has no effect and the plan lock remains hung. The workaround used to release a hung SQL plan value lock by inserting a row into the SYSADM.SQL_STATUS_PLAN Dynamic System Table is not successful. The CA Datacom/DB Multi-User Facility (MUF) must be cycled before the plan is executable. None. CA Datacom/DB Version 15.1 DB 5150 Copyright (C) 2016 CA. All rights reserved. R00280-DCM150-SP2 DESC(WORKAROUND FOR HUNG SQL PLAN LOCK INEFFECTIVE). FMID (CABDF00) PRE ( RO81529 RO83027 ) SUP ( TR88911 )

17 CA Datacom/DB CA RS PTF RO RO88959 RO88959 M.C.S. ENTRIES = ++PTF (RO88959) DATACOM/DB NOT PASSING ROW LENGTH TO READRXX ROUTINE CA Datacom/DB is not passing row lengths to the READRXX subroutine. Row lengths are not passed to applications using the READRXX subroutine. Applications reading the RXX file with subroutine READRXX do not receive row lengths. None. CA Datacom/DB Version 15.1 DB 5152 Copyright (C) 2016 CA. All rights reserved. R00281-DCM150-SP2 DESC(DATACOM/DB NOT PASSING ROW LENGTH TO READRXX ROUTINE). FMID (CABDF00) SUP ( TR88959 )

18 CA Datacom/DB CA RS PTF RO RO89021 RO89021 M.C.S. ENTRIES = ++PTF (RO89021) DBUTLTY CXXCLONE/LOAD NOT HANDLING DBID RANGES CORRECTLY CA Datacom DBUTLTY CXXCLONE may not LOAD one or more DBIDS to the new CXX if multiple DBID ranges are coded in the control statement. The problem also occurs with DBUTLTY LOAD=CXX when using DBID ranges. DBUTLTY functions CXXCLONE and LOAD=CXX may skip one ore more DBIDs. The output will not contain the usual message: BASE PROCESSED - nnnn (where nnnn is the DBID) for these DBIDs. DBUTLTY functions CXXCLONE and LOAD=CXX cannot be used with DBID ranges. Listing all DBIDs individually (i.e. without specifying ranges of DBIDs) on the DBUTLTY control statements may provide a circumvention. CA Datacom/DB Version 15.1 DB 5149 Copyright (C) 2016 CA. All rights reserved. R00282-DCM150-SP2 DESC(DBUTLTY CXXCLONE/LOAD NOT HANDLING DBID RANGES CORRECTLY). FMID (CABDF00) SUP ( TR89021 )

19 CA Datacom/DB CA RS PTF RO RO89125 RO89125 M.C.S. ENTRIES = ++PTF (RO89125) FATAL INTERNAL ERROR - XES-XXXX IN MUFPLEX Exclusive control of rows from bases that are shared between members of a MUFplex is established by obtaining a lock in the Coupling Facility (CF) in addition to locking the row in the local exclusive control table. If a task has a local lock on a row and another task is waiting for it, the local lock is passed to the waiting task. In MUFplex mode, the waiting task then releases the corresponding coupler lock under certain contention circumstances to give other members of the MUFplex a chance to get exclusive control of the row. If the task passing the local lock failed to obtain the corresponding lock in the coupler, the task the local lock was passed to causes the MUFplex member to abend when trying to release the coupler lock that is not owned. The error is extremely rare. If the CF returns an error feedback to a member of a MUFplex indicating that the RELEASE of a coupler lock failed because the caller did not own it, the MUFplex member abends with message: DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - XES-xxxx where xxxx denotes an offset in module DBXESPR. The impact is an outage of one member of the MUFplex. None. CA Datacom/DB Version 15.1 DB 5151 Copyright (C) 2016 CA. All rights reserved. R00283-DCM150-SP2 DESC(FATAL INTERNAL ERROR - XES-XXXX IN MUFPLEX). FMID (CABDF00) PRE ( RO72240 ) SUP ( RO81155 RO87765 RO88154 TR81155 TR87765 TR88154 TR89125 )