CA Datacom/DB CA RS 1308 Service List

Transcription

1 CA Datacom/DB CA RS 1308 Service List Description Hiper 14.0 RO57425 S0C4 AT DBINRPR+23AC USING EXTENDED PROGRAMMING OPTION RO60177 EOJ_OK SUPPORT IN EXTENDED OPTION DOES NOT TAKE EFFECT The CA RS 1308 service count for this release is 2

2 CA Datacom/DB CA RS 1308 Service List Description Hiper 12.0 RO58453 MUF ABENDING WITH S / RC 65(44) DURING A DATASET OPEN RO60941 RETURN CODE 13(05), 65(42) OR 76(83) ON EXTEND RO60981 FOREIGN KEY CASCADE NOT WORKING WHEN TASK ALREADY HAS ROW **HIPER** RO61484 MISSING OR INCORRECT ROWS RETURNED ON SELNR The CA RS 1308 service count for this release is 4

3 CA Datacom/DB 3 CA RS 1308 Service List for CABDE00 FMID Service Description Hiper CABDE00 RO57425 S0C4 AT DBINRPR+23AC USING EXTENDED PROGRAMMING OPTION RO60177 EOJ_OK SUPPORT IN EXTENDED OPTION DOES NOT TAKE EFFECT The CA RS 1308 service count for this FMID is 2

4 CA Datacom/DB 4 CA RS 1308 Service List for CBDC000 FMID Service Description Hiper CBDC000 RO58453 MUF ABENDING WITH S / RC 65(44) DURING A DATASET OPEN RO60941 RETURN CODE 13(05), 65(42) OR 76(83) ON EXTEND RO61484 MISSING OR INCORRECT ROWS RETURNED ON SELNR The CA RS 1308 service count for this FMID is 3

5 CA Datacom/DB 5 CA RS 1308 Service List for CVEC000 FMID Service Description Hiper CVEC000 RO60981 FOREIGN KEY CASCADE NOT WORKING WHEN TASK ALREADY HAS ROW **HIPER** The CA RS 1308 service count for this FMID is 1

6 CA Datacom/DB CA RS PTF RO RO57425 RO57425 M.C.S. ENTRIES = ++PTF (RO57425) S0C4 AT DBINRPR+23AC USING EXTENDED PROGRAMMING OPTION If a user-written program using the Extended Programming Option (normally a program that manages multiple tasks) supplies its own ECB list, it abends in module DBINRPR near offset x'23ac' on the first OPEN request. An ECB list is supplied when using OPTION 2 or OPTION 3 of the Extended Programming Option. An application using the Extended Programming Option abends in module DBINRPR on the first OPEN. The application cannot run in CA Datacom/DB Version None. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4784 Copyright (C) 2013 CA. All rights reserved. R00418-DCM140-SP1 DESC(S0C4 AT DBINRPR+23AC USING EXTENDED PROGRAMMING OPTION). FMID (CABDE00) PRE ( RO46575 ) SUP ( RO34786 RO42639 RO49305 RO54278 TR34786 TR42639 TR49305 TR54278 TR57425 )

7 CA Datacom/DB CA RS PTF RO RO60177 RO60177 M.C.S. ENTRIES = ++PTF (RO60177) EOJ_OK SUPPORT IN EXTENDED OPTION DOES NOT TAKE EFFECT If a user-written application using the Extended Programming Option has specified the EOJ_OK option, it does not take effect when the EOJ command has been issued to the CA Datacom/DB Multi-User Facility. MUF remains up after an EOJ when it should have terminated. MUF remains up until the application has disconnected from the MUF by issuing the last CLOSE. Close all open URTs in the user application prior to issuing the EOJ command. PRODUCT(S) AFFECTED: CA Datacom/DB Release 14.0 DB 4804 Copyright (C) 2013 CA. All rights reserved. R00448-DCM140-SP1 DESC(EOJ_OK SUPPORT IN EXTENDED OPTION DOES NOT TAKE EFFECT). FMID (CABDE00) PRE ( RO46575 ) SUP ( AR47507 AR59165 RO34786 RO42639 RO49305 RO54278 RO57425 RO59165 TR34786 TR42639 TR49305 TR54278 TR57425 TR59165 TR60177 ) ++HOLD (RO60177) SYSTEM FMID(CABDE00) REASON (ACTION ) DATE (13186) COMMENT ( Product: CA Datacom/DB Release: 14.0 Sequence: Purpose: Relevance: Knowledge required: Access required: Steps to Perform: ). ++HOLD (RO60177) SYSTEM FMID(CABDE00) REASON (DOC ) DATE (13186) COMMENT ( Product: CA Datacom/DB Release: 14.0 Please see the associated Product Documentation Change (PDC) published as RI Publication: ).

8 CA Datacom/DB CA RS PTF RO RO58453 RO58453 M.C.S. ENTRIES = ++PTF (RO58453) MUF ABENDING WITH S / RC 65(44) DURING A DATASET OPEN CA Datacom/DB Multi-User Facility (MUF) aborts with RC 65(44) followed by IEA705I ERROR DURING GETMAIN SYS CODE = due to a shortage of 24-bit memory when there is a very large number of datasets open. MUF may abend when attempting to open an Area (dataset). The following DB return code and IBM message may be seen: Datacom/DB RC 65(44) IEA705I ERROR DURING GETMAIN SYS CODE = MUF must be restarted. To circumvent the problem, do the following 1. Increase the storage below the line in 24-bit memory, or 2. Decrease the number of datasets open at one time. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 CA Datacom/DB Release 14.0 DB 4790 Copyright (C) 2013 CA. All rights reserved. R00831-DCM120-SP1 DESC(MUF ABENDING WITH S / RC 65(44) DURING A DATASET OPEN). FMID (CBDC000) PRE ( RO22965 RO32510 RO35507 RO41721 RO53056 ) SUP ( AR35507 RO15988 RO26399 RO37574 RO41830 RO47826 RO53658 TR15988 TR26399 TR30822 TR36672 TR37574 TR41830 TR47826 TR53658 TR58453 )

9 CA Datacom/DB CA RS PTF RO RO60941 RO60941 M.C.S. ENTRIES = ++PTF (RO60941) RETURN CODE 13(05), 65(42) OR 76(83) ON EXTEND PTF RO53658 (CA Datacom/DB Version 12.0) or RO56152 (Version 14.0) was written to resolve a problem where a DBUTLTY EXTEND of a Multi-Dataset Index (MDI) on non-sms managed volumes failed with RC 13(05). The PTF did not address all cases. In fact, it caused new symptoms for Data Areas and Index Areas (whether MDI or not). The problem happens when DBUTLTY EXTEND expands the file to a new volume in conjunction With an UNCATALOG and re-catalog with a larger number of volumes. Without this new solution, EXTENDs will continue to fail until the area is reinitialized. This fix reverses PTF RO53658/RO56152 and resolves the problem in a different way for all known cases. DBUTLTY EXTENDs fail with RC 13(05), 65(42), 65(44) or 76(83). The user sees the following message. DB01405I - DATA SET VOLUME IGNORED, NOT CHAINED A Data Area or Index Area that is not SMS-managed cannot be extended beyond its last volume (as defined in the catalog prior to the re-catalog on additional volumes). In a production environment, this could cause a significant operational impact. Until the solution is applied, the only way to avoid the problem when additional space is needed is to do an INIT of the area with larger extents or more volumes instead of doing an EXTEND. If an Index Area is nearly full, follow these steps: 1. With the database offline, run DBUTLTY INIT to initialize the IXX Area(s) with larger Extents or more volumes. 2. Do a DBUTLTY RETIX at the DBID level to rebuild the index for all tables in the database. If a Data Area is nearly full, follow these steps: 1. With the database offline, run DBUTLTY BACKUP for the Data Area. 2. Run DBUTLTY INIT to initialize the Data Area with larger extents or more volumes. 3. Do a DBUTLTY LOAD from the BACKUP taken in step 1. DB 4799 Copyright (C) 2013 CA. All rights reserved. R00857-DCM120-SP1 DESC(RETURN CODE 13(05), 65(42) OR 76(83) ON EXTEND). FMID (CBDC000) PRE ( RO19101 RO22965 RO24059 RO26756 RO28894 RO32510 RO35507 RO41721 RO46435 RO47047 RO53056 RO55995 ) SUP ( AR35507 AR53658 RO09466 RO15988 RO20811 RO21962 RO22468 RO23174 RO25336 RO26399 RO37574 RO40564 RO41830 RO47826 RO52950 RO53658 RO58453 TR09466 TR15988 TR20811 TR21962 TR22468 TR23174 TR25336 TR26399 TR30822 TR36672 TR37574 TR40564 TR41830 TR47826 TR52950 TR53658 TR58453 TR59503 TR60941 )

10 CA Datacom/DB CA RS PTF RO RO60981 RO60981 M.C.S. ENTRIES = ++PTF (RO60981) FOREIGN KEY CASCADE NOT WORKING WHEN TASK ALREADY HAS ROW When the current transaction already has primary exclusive control on a row that the Foreign Key CASCADE option indicates should be deleted or updated, the CASCADE process stops. Exclusive control being in effect should not prevent the CASCADE operation. This condition can occur when either: 1. a Record-At-a-Time DELET or UPDAT is issued on a table referenced by a Foreign Key, or 2. a DELETE "where current of cursorname" is processed on the parent table. Inserting child table rows with SQL and then deleting the parent table row is not affected because, although secondary exclusive control is still held (because there is no commit work issued), primary exclusive control is dropped after an INSERT with SQL. The rows the CASCADE Foreign Key option specifies should be deleted or updated are not all changed. Child rows are left "orphaned" because there is no longer a matching parent row. See the DBUTLTY CONFIRM function to validate constraints and find any orphaned rows. None. PRODUCT(S) AFFECTED: CA Datacom SQL Release 12.0 CA Datacom SQL Release 14.0 Release 12.0 SQL 1886 Copyright (C) 2013 CA. All rights reserved. R00859-DCM120-SP1 DESC(FOREIGN KEY CASCADE NOT WORKING WHEN TASK ALREADY HAS ROW). FMID (CVEC000) PRE ( RO09311 ) SUP ( RO17898 TR17898 TR60981 )

11 CA Datacom/DB CA RS PTF RO RO61484 RO61484 M.C.S. ENTRIES = ++PTF (RO61484) MISSING OR INCORRECT ROWS RETURNED ON SELNR This solution fixes a problem saving the set definition from the SELFR command when the CBS buffer is full. Subsequent SELNR commands using the corrupted set definition can return wrong, or invalid, rows. Missing or incorrect rows are returned with the SELNR command when the CBS Buffer becomes full. This can cause data integrity issues if the rows returned by SELNR are used to update the database. Increase the size of the CBS buffer so that it does not become full. If the buffer is at maximum size and still fills, change applications to release sets. PRODUCT(S) AFFECTED: CA Datacom/DB Release 12.0 DB 4824 Copyright (C) 2013 CA. All rights reserved. R00868-DCM120-SP1 DESC(MISSING OR INCORRECT ROWS RETURNED ON SELNR). FMID (CBDC000) PRE ( RO10336 RO37405 RO52174 ) SUP ( CC56161 RO07454 RO12811 RO16421 RO18769 RO20003 RO20029 RO21420 RO30687 RO31099 RO37892 RO41099 RO43239 RO44825 RO56525 TR07454 TR12811 TR16421 TR18769 TR19397 TR20003 TR20029 TR21420 TR30687 TR31099 TR37892 TR41099 TR43239 TR44825 TR56525 TR61442 TR61484 )