CA DB2 Tools CA RS 1308 Service List

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "CA DB2 Tools CA RS 1308 Service List"

Transcription

1 CA DB2 Tools CA RS 1308 Service List Description Hiper 16.0 RO57140 U333 U334 U335 ON UTS OBJECT IN DB2 10 RO57141 U333 U334 U335 ON UTS OBJECT IN DB2 10 RO57147 OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E RO57148 OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E RO57619 MODIFY LIST KEEP STOPS PROCESSING AFTER INITIAL OBJECT RO57696 S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. RO58179 S0C4 IN AFTER JOB CANCEL RO58490 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO58491 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO58492 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO58493 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO58494 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO58987 INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED RO59011 ACCUMULATE CLONED TABLESPACE NOT QUIESCED RO59012 ACCUMULATE CLONED TABLESPACE NOT QUIESCED RO59013 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS RO59014 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS RO59015 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS RO59489 PFL LOOPS WHEN MULTIPLE TABLES IN A TABLESPACE ARE VERSIONED RO59721 ADD ABILITY TO PASS IN PRI & SEC SPACE FOR DSNUTILB CALL RO60738 MEDIA MANAGER ERROR PFL0024E ON LOAD RESUME INTO PART RO60983 DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE **HIPER** RO61126 S0C7 IN FOR ONLINE REORG INDEX RO61127 S0C7 IN FOR ONLINE REORG INDEX RO61139 INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH RO61281 DB2 APPLICATIONS RETURN A 00C9007F ERROR AFTER LOAD REPLACE The CA RS 1308 service count for this release is 26

2 CA DB2 Tools CA RS 1308 Service List Description Hiper 15.0 RO58009 S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. RO59026 INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED RO60883 DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE **HIPER** RO61135 INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH RO61492 CA UTILITY PROBLEMS FOR CA RESTART TABLES AND TABLESPACES The CA RS 1308 service count for this release is 5

3 CA DB2 Tools CA RS 1308 Service List Description Hiper 14.5 NO-SRV2 CA RS 1308 Contains No Service For This Release of This Product. The CA RS 1308 service count for this release is 0

4 CA DB2 Tools CA RS 1308 Service List Description Hiper 14.0 NO-SRVC CA RS 1308 Contains No Service For This Release of This Product. The CA RS 1308 service count for this release is 0

5 CA DB2 Tools 5 CA RS 1308 Service List for CGENG00 FMID Service Description Hiper CGENG00 RO58491 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 The CA RS 1308 service count for this FMID is 1

6 CA DB2 Tools 6 CA RS 1308 Service List for CPDTF00 FMID Service Description Hiper CPDTF00 RO58009 S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. RO59026 INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED RO61135 INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH The CA RS 1308 service count for this FMID is 3

7 CA DB2 Tools 7 CA RS 1308 Service List for CPDTG00 FMID Service Description Hiper CPDTG00 RO57696 S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. RO58987 INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED RO61139 INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH The CA RS 1308 service count for this FMID is 3

8 CA DB2 Tools 8 CA RS 1308 Service List for CPFLF00 FMID Service Description Hiper CPFLF00 RO60883 DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE **HIPER** The CA RS 1308 service count for this FMID is 1

9 CA DB2 Tools 9 CA RS 1308 Service List for CPFLG00 FMID Service Description Hiper CPFLG00 RO59489 PFL LOOPS WHEN MULTIPLE TABLES IN A TABLESPACE ARE VERSIONED RO60738 MEDIA MANAGER ERROR PFL0024E ON LOAD RESUME INTO PART RO60983 DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE **HIPER** RO61281 DB2 APPLICATIONS RETURN A 00C9007F ERROR AFTER LOAD REPLACE The CA RS 1308 service count for this FMID is 4

10 CA DB2 Tools 10 CA RS 1308 Service List for CPFRG00 FMID Service Description Hiper CPFRG00 RO57140 U333 U334 U335 ON UTS OBJECT IN DB2 10 RO57147 OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E RO58490 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO59013 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS RO59721 ADD ABILITY TO PASS IN PRI & SEC SPACE FOR DSNUTILB CALL RO61126 S0C7 IN FOR ONLINE REORG INDEX The CA RS 1308 service count for this FMID is 6

11 CA DB2 Tools 11 CA RS 1308 Service List for CPMMG00 FMID Service Description Hiper CPMMG00 RO57619 MODIFY LIST KEEP STOPS PROCESSING AFTER INITIAL OBJECT RO58493 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO59011 ACCUMULATE CLONED TABLESPACE NOT QUIESCED RO59015 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS The CA RS 1308 service count for this FMID is 4

12 CA DB2 Tools 12 CA RS 1308 Service List for CPUTG00 FMID Service Description Hiper CPUTG00 RO58494 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO59012 ACCUMULATE CLONED TABLESPACE NOT QUIESCED The CA RS 1308 service count for this FMID is 2

13 CA DB2 Tools 13 CA RS 1308 Service List for CRCMF00 FMID Service Description Hiper CRCMF00 RO61492 CA UTILITY PROBLEMS FOR CA RESTART TABLES AND TABLESPACES The CA RS 1308 service count for this FMID is 1

14 CA DB2 Tools 14 CA RS 1308 Service List for CUGRG00 FMID Service Description Hiper CUGRG00 RO57141 U333 U334 U335 ON UTS OBJECT IN DB2 10 RO57148 OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E RO58179 S0C4 IN AFTER JOB CANCEL RO58492 DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 RO59014 RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS RO61127 S0C7 IN FOR ONLINE REORG INDEX The CA RS 1308 service count for this FMID is 6

15 CA DB2 Tools CA RS PTF RO RO57140 RO57140 M.C.S. ENTRIES = ++PTF (RO57140) U333 U334 U335 ON UTS OBJECT IN DB2 10 CA Fast Recover for DB2 for z/os(pfr) and the Accumulate function of Merge/Modify for DB2 for z/os(pmm) have a problem processing LOG records on a DB2 Version 10 NFM system and the log record is for a table which is defined with VAR.. colums. This happens when the object is a Universal Tablespace,UTS, the current processed log record is an insert and the contigouos space value found in PGFREEP does not allow the insert because not enough space is available. The page level space consolidation routines did not account for the pseudo-deleted rows in a UTS object and differences in the MAPID values in DB2 V10 NFM. PFR/PMM might end with RC=0. but leave the object, a DB2 dataset or image copy in an inconsistent state. PFR/PMM might end with U333, u334 or u335 and message PFR9998E - ABEND ON LOG RECORD WITH dbid: xxx psid: yyyy PAGE: zzzz For PFR - The object is not recovered correctly and is not usable. For PMM - The created Image copy is not usable in recover process. N/A PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Merge/Modify release 15.0 Fast Recover Release 16.0 Merge/Modify release 16.0 Fast Recover Release 17.0 Merge/Modify release 17.0 PFR 803 (C)2013 CA. All Rights Reserved.R01589-D16-SP1 DESC(U333 U334 U335 ON UTS OBJECT IN DB2 10). FMID (CPFRG00) PRE ( RO42042 RO42095 RO42165 RO42846 RO43402 RO43433 RO44032 RO44113 RO44425 RO44923 RO45797 RO45829 RO46713 RO46983 RO48050 RO49937 RO51274 RO54608 RO54668 ) SUP ( RO43498 RO46414 RO48974 RO52156 ZFRL062 ) ++IF FMID(CUGRG00) REQ(RO57141).

16 CA DB2 Tools CA RS PTF RO RO57141 RO57141 M.C.S. ENTRIES = ++PTF (RO57141) U333 U334 U335 ON UTS OBJECT IN DB2 10 CA Fast Recover for DB2 for z/os(pfr) and the Accumulate function of Merge/Modify for DB2 for z/os(pmm) have a problem processing LOG records on a DB2 Version 10 NFM system and the log record is for a table which is defined with VAR.. colums. This happens when the object is a Universal Tablespace,UTS, the current processed log record is an insert and the contigouos space value found in PGFREEP does not allow the insert because not enough space is available. The page level space consolidation routines did not account for the pseudo-deleted rows in a UTS object and differences in the MAPID values in DB2 V10 NFM. PFR/PMM might end with RC=0. but leave the object, a DB2 dataset or image copy in an inconsistent state. PFR/PMM might end with U333, u334 or u335 and message PFR9998E - ABEND ON LOG RECORD WITH dbid: xxx psid: yyyy PAGE: zzzz For PFR - The object is not recovered correctly and is not usable. For PMM - The created Image copy is not usable in recover process. N/A PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Merge/Modify release 15.0 Fast Recover Release 16.0 Merge/Modify release 16.0 Fast Recover Release 17.0 Merge/Modify release 17.0 PFR 803 (C)2013 CA. All Rights Reserved.R01589-D16-SP1 DESC(U333 U334 U335 ON UTS OBJECT IN DB2 10). FMID (CUGRG00) PRE ( RO42043 RO43318 RO43405 RO44114 RO44427 RO44924 RO45472 RO45798 RO45830 RO51275 RO54610 ) SUP ( ZFRL062 ) ++IF FMID(CPFRG00) REQ(RO57140).

17 CA DB2 Tools CA RS PTF RO RO57147 RO57147 M.C.S. ENTRIES = ++PTF (RO57147) OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E CA Fast Recover for DB2 for z/os (PFR) fails for an OBIDXLAT FULLDD option with error message PFR0239E when the DSGROUP search process returns not found information. An informational message is missing in this case which results in the printing of PFR0239E error message and stopping the recover process with return code 8. PFR job fails with following information in PFR0239E message: PFR0239E - DIFFERENT SUBSYSTEM NAMES FOUND IN HEADER PAGE FOR DIFFERNT FULLDD DURING OBIDXLAT 'DD1' SSID DF1G 'DD1' SSID... This Error has Occurred in CSECT - Recover job fails. N/A PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Fast Recover Release 17.0 PFR 849 (C)2013 CA. All Rights Reserved.R01716-D16-SP1 DESC(OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E). FMID (CPFRG00) PRE ( RO42839 RO42842 RO42846 RO43504 RO44170 RO44416 RO44425 RO44923 RO45829 RO46725 RO50765 RO52621 RO54608 RO55307 ) SUP ( ZFRL063 ) ++IF FMID(CUGRG00) REQ(RO57148). ++HOLD (RO57147) SYSTEM FMID(CPFRG00) REASON (ACTION ) DATE (13094) COMMENT ( XMESSAGE components have changes as part of this maintenance. If you do not customize XMESSAGES, no further action is required. If you do customize XMESSAGES, after maintenance is APPLIED re-apply any XMESSAGE customizations and relink the XMESSAGE load modules. Refer to the Post Installation and Customization Guide for details. ).

18 CA DB2 Tools CA RS PTF RO RO57148 RO57148 M.C.S. ENTRIES = ++PTF (RO57148) OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E CA Fast Recover for DB2 for z/os (PFR) fails for an OBIDXLAT FULLDD option with error message PFR0239E when the DSGROUP search process returns not found information. An informational message is missing in this case which results in the printing of PFR0239E error message and stopping the recover process with return code 8. PFR job fails with following information in PFR0239E message: PFR0239E - DIFFERENT SUBSYSTEM NAMES FOUND IN HEADER PAGE FOR DIFFERNT FULLDD DURING OBIDXLAT 'DD1' SSID DF1G 'DD1' SSID... This Error has Occurred in CSECT - Recover job fails. N/A PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Fast Recover Release 17.0 PFR 849 (C)2013 CA. All Rights Reserved.R01716-D16-SP1 DESC(OBIDXLAT RECOVER FULLDD FAILS WITH PFR0239E). FMID (CUGRG00) PRE ( RO42043 RO43405 RO43436 RO44035 RO44114 RO44171 RO44418 RO44427 RO44924 RO45798 RO46726 RO52622 RO54610 RO55308 ) SUP ( ZFRL063 ) ++IF FMID(CPFRG00) REQ(RO57147).

19 CA DB2 Tools CA RS PTF RO RO57619 RO57619 M.C.S. ENTRIES = ++PTF (RO57619) MODIFY LIST KEEP STOPS PROCESSING AFTER INITIAL OBJECT When running the CA Merge/Modify for DB2 for z/os (PMM) MODIFY RECOVERY KEEP function with LIST option, PMM will not process the second and subsequent objects expanded in the list and no rows are deleted from SYSIBM.SYSCOPY for those objects. In PTIMSG you can find a SQL statement which will be issued: PMM0224I - THE FOLLOWING SQL WILL BE ISSUED: DELETE FROM SYSIBM.SYSCOPY WHERE (DBNAME = 'dbname' AND TSNAME = 'tsname' AND INSTANCE = n) AND ( ICDATE < 'date1' OR ICDATE > 'date2') In the SQL statement the 'date1' value in the ICDATE clause equals to hexadecimal zeros. The requested PMM function will be executed only for the first expanded object in the list. Other objects will not be processed and no rows will be deleted from SYSIBM.SYSCOPY. None. PRODUCTS AFFECTED: PMM 16.0 PMM 17.0 PMM 316 (C)2013 CA. All Rights Reserved.R01763-D16-SP1 DESC(MODIFY LIST KEEP STOPS PROCESSING AFTER INITIAL OBJECT). FMID (CPMMG00) PRE ( RO42251 RO42849 RO43407 RO43439 RO44115 RO49609 RO51365 RO56395 RO57555 ) SUP ( RO56017 ZMMJ053 )

20 CA DB2 Tools CA RS PTF RO RO57696 RO57696 M.C.S. ENTRIES = ++PTF (RO57696) S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. CA Detector for DB2 for z/os (PDT) collection may abnormally terminate with an S0C4 in module DT$DII when executing parallel tasks. The following messages are issued in the XMANAGER's Joblog: ABEND=S0C4 MODULE=DT$DII OFFSET=XXXXXXXX DB2=xxx PDT0102 DETECTOR TERM IN PROGRESS FOR DB2=XXXX The following symptom is seen in the dump: AB/S00C4 PRCS/ REGS/A0168 Symptom Description AB/S00C4 System abend code: 00C4 PRCS/ Abend reason code: REGS/A0168 Register/PSW difference for R0A:-0168 The Detector collection terminates and will need to be restarted. None. PRODUCT(S) AFFECTED: Detector Release 15.0 Detector Release 16.0 Detector Release 17.0 PDT 1102 (C)2013 CA. All Rights Reserved.R01768-D16-SP1 DESC(S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS.). FMID (CPDTG00) PRE ( RO42750 RO44286 RO45410 RO46085 RO47745 RO47746 RO48124 RO49569 RO50557 RO53542 RO54115 RO54876 RO54974 RO55607 RO55636 RO56241 RO57651 ) SUP ( RO44445 RO45747 RO52624 ZDTL083 ) ++HOLD (RO57696) SYSTEM FMID(CPDTG00) REASON (ACTION ) DATE (13107) COMMENT ( Product: Detector Release: 16.0 Sequence: Before updating production load libraries. Purpose: Avoidance of module mismatch related errors. Relevance: Required procedure for all users of CA Detector. Knowledge required: 1. SMP/E 2. z/os System Programming 3. CA DB2 Tools Installation and Maintenance procedures. Access required: 1. Product Libraries. Steps to Perform: The Xmanager address space must be recycled before these changes will take effect. Do not apply this maintenance to the Xmanager STEPLIB or PTILIB load libraries while the address space is active. If you are executing the Xmanager address space directly from your SMP/E target load libraries then only apply maintenance while the Xmanager address space is inactive. Applying this maintenance to an executing Xmanager address space may result in a discrepancy between those components that are dynamically loaded and those components that are loaded for the life of the Xmanager

21 CA DB2 Tools CA RS PTF RO57696 address space. This may result in unpredictable behavior of the CA-DB2 tools, cause a CA-DB2 tools failure, or compromise system and/or DB2 subsystem integrity. ).

22 CA DB2 Tools CA RS PTF RO RO58179 RO58179 M.C.S. ENTRIES = ++PTF (RO58179) S0C4 IN AFTER JOB CANCEL CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) may abend with a s0c4 when cancelled after processing has started. The problem is due to code not using the LIST and EXECUTE forms of macros inside a reentrant csect. An occassional s0c4 may occur after cancelling the started job. The s0c4 prevents all queued xmessages from being printed out. These xmessages may help clarify where the job was processing when cancelled. None. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Release 16.0 Release 17.0 Merge/Modify Release 15.0 Release 16.0 Release 17.0 PFR 846 (C)2013 CA. All Rights Reserved.R01785-D16-SP1 DESC(S0C4 IN AFTER JOB CANCEL). FMID (CUGRG00) PRE ( RO43405 RO44427 RO44924 RO45798 RO54610 ) SUP ( ZFRL067 )

23 CA DB2 Tools CA RS PTF RO RO58490 RO58490 M.C.S. ENTRIES = ++PTF (RO58490) DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) have a problem with a storage leak in the DB2 DBM1 address space on DB2 10. Environments with a heavy workload to SYSLGRNX are more at risk than shops with lighter work loads. In some environments a storage leak is possible causing DB2 to run out of storage needed to function in the DB2 DBM1 address space when running in a DB2 10 environment. Samples of possible symptoms: - DB2 applications may end with SYSTEM COMPLETION CODE=04E REASON=00E Accumulate may end with SYSTEM COMPLETION CODE=04E REASON=00E20004 and message: PFR0370E - BUILDING OF LOG RANGE NODES FAILED This Error has Occurred in CSECT - DB2 must be recycled to resolve the storage leak. None. The fix must be applied. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Accumulate Release 15.0 Accumulate Release 16.0 Accumulate Changes Release 15.0 Accumulate Changes Release 16.0 PFR 825 (C)2013 CA. All Rights Reserved.R01794-D16-SP1 DESC(DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10). FMID (CPFRG00) PRE ( RO42042 RO42095 RO42157 RO42165 RO42839 RO42842 RO42846 RO43402 RO43433 RO43451 RO43504 RO44032 RO44113 RO44170 RO44416 RO44425 RO44923 RO45011 RO45797 RO45803 RO45829 RO46713 RO46725 RO48050 RO48883 RO50765 RO51274 RO52621 RO54608 RO54668 RO55307 RO55331 RO57140 RO57147 RO57482 ) SUP ( RO42856 RO43449 RO43498 RO46414 RO46727 RO46983 RO48974 RO49937 RO50770 RO51221 RO52156 RO52947 ZFRL052 ) ++IF FMID(CGENG00) REQ(RO58491). ++IF FMID(CUGRG00) REQ(RO58492). ++IF FMID(CPMMG00) REQ(RO58493). ++IF FMID(CPUTG00) REQ(RO58494). ++HOLD (RO58490) SYSTEM FMID(CPFRG00) REASON (ACTION ) DATE (13127) COMMENT ( XMESSAGE components have changes as part of this maintenance. If you do not customize XMESSAGES, no further action is required. If you do customize XMESSAGES, after maintenance is APPLIED re-apply any XMESSAGE customizations and relink the XMESSAGE load modules. Refer to the Post Installation and Customization Guide for details. ).

24 CA DB2 Tools CA RS PTF RO RO58491 RO58491 M.C.S. ENTRIES = ++PTF (RO58491) DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) have a problem with a storage leak in the DB2 DBM1 address space on DB2 10. Environments with a heavy workload to SYSLGRNX are more at risk than shops with lighter work loads. In some environments a storage leak is possible causing DB2 to run out of storage needed to function in the DB2 DBM1 address space when running in a DB2 10 environment. Samples of possible symptoms: - DB2 applications may end with SYSTEM COMPLETION CODE=04E REASON=00E Accumulate may end with SYSTEM COMPLETION CODE=04E REASON=00E20004 and message: PFR0370E - BUILDING OF LOG RANGE NODES FAILED This Error has Occurred in CSECT - DB2 must be recycled to resolve the storage leak. None. The fix must be applied. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Accumulate Release 15.0 Accumulate Release 16.0 Accumulate Changes Release 15.0 Accumulate Changes Release 16.0 PFR 825 (C)2013 CA. All Rights Reserved.R01794-D16-SP1 DESC(DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10). FMID (CGENG00) SUP ( ZFRL052 ) ++IF FMID(CPFRG00) REQ(RO58490). ++IF FMID(CUGRG00) REQ(RO58492). ++IF FMID(CPMMG00) REQ(RO58493). ++IF FMID(CPUTG00) REQ(RO58494).

25 CA DB2 Tools CA RS PTF RO RO58492 RO58492 M.C.S. ENTRIES = ++PTF (RO58492) DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) have a problem with a storage leak in the DB2 DBM1 address space on DB2 10. Environments with a heavy workload to SYSLGRNX are more at risk than shops with lighter work loads. In some environments a storage leak is possible causing DB2 to run out of storage needed to function in the DB2 DBM1 address space when running in a DB2 10 environment. Samples of possible symptoms: - DB2 applications may end with SYSTEM COMPLETION CODE=04E REASON=00E Accumulate may end with SYSTEM COMPLETION CODE=04E REASON=00E20004 and message: PFR0370E - BUILDING OF LOG RANGE NODES FAILED This Error has Occurred in CSECT - DB2 must be recycled to resolve the storage leak. None. The fix must be applied. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Accumulate Release 15.0 Accumulate Release 16.0 Accumulate Changes Release 15.0 Accumulate Changes Release 16.0 PFR 825 (C)2013 CA. All Rights Reserved.R01794-D16-SP1 DESC(DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10). FMID (CUGRG00) PRE ( RO42043 RO42097 RO42168 RO42840 RO42848 RO43318 RO43405 RO43436 RO43454 RO43505 RO43887 RO44012 RO44035 RO44114 RO44171 RO44418 RO44427 RO44493 RO44924 RO45472 RO45798 RO45804 RO45830 RO46726 RO48051 RO48352 RO51275 RO52622 RO54610 RO55308 RO55333 RO57141 RO57148 RO57484 RO57556 ) SUP ( RO42063 RO43981 RO44754 RO45103 RO46474 RO50769 RO58179 ZFRL052 ) ++IF FMID(CPFRG00) REQ(RO58490). ++IF FMID(CGENG00) REQ(RO58491). ++IF FMID(CPMMG00) REQ(RO58493). ++IF FMID(CPUTG00) REQ(RO58494).

26 CA DB2 Tools CA RS PTF RO RO58493 RO58493 M.C.S. ENTRIES = ++PTF (RO58493) DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) have a problem with a storage leak in the DB2 DBM1 address space on DB2 10. Environments with a heavy workload to SYSLGRNX are more at risk than shops with lighter work loads. In some environments a storage leak is possible causing DB2 to run out of storage needed to function in the DB2 DBM1 address space when running in a DB2 10 environment. Samples of possible symptoms: - DB2 applications may end with SYSTEM COMPLETION CODE=04E REASON=00E Accumulate may end with SYSTEM COMPLETION CODE=04E REASON=00E20004 and message: PFR0370E - BUILDING OF LOG RANGE NODES FAILED This Error has Occurred in CSECT - DB2 must be recycled to resolve the storage leak. None. The fix must be applied. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Accumulate Release 15.0 Accumulate Release 16.0 Accumulate Changes Release 15.0 Accumulate Changes Release 16.0 PFR 825 (C)2013 CA. All Rights Reserved.R01794-D16-SP1 DESC(DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10). FMID (CPMMG00) PRE ( RO42044 RO42098 RO42251 RO42849 RO43407 RO43439 RO43455 RO44013 RO44038 RO44115 RO44116 RO44428 RO44925 RO45012 RO45799 RO45831 RO46108 RO46714 RO48110 RO48353 RO49609 RO51276 RO51365 RO54609 RO55332 RO56395 RO57555 ) SUP ( RO43460 RO44118 RO56017 RO56301 RO57619 ZFRL052 ) ++IF FMID(CPFRG00) REQ(RO58490). ++IF FMID(CGENG00) REQ(RO58491). ++IF FMID(CUGRG00) REQ(RO58492). ++IF FMID(CPUTG00) REQ(RO58494).

27 CA DB2 Tools CA RS PTF RO RO58494 RO58494 M.C.S. ENTRIES = ++PTF (RO58494) DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10 CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) have a problem with a storage leak in the DB2 DBM1 address space on DB2 10. Environments with a heavy workload to SYSLGRNX are more at risk than shops with lighter work loads. In some environments a storage leak is possible causing DB2 to run out of storage needed to function in the DB2 DBM1 address space when running in a DB2 10 environment. Samples of possible symptoms: - DB2 applications may end with SYSTEM COMPLETION CODE=04E REASON=00E Accumulate may end with SYSTEM COMPLETION CODE=04E REASON=00E20004 and message: PFR0370E - BUILDING OF LOG RANGE NODES FAILED This Error has Occurred in CSECT - DB2 must be recycled to resolve the storage leak. None. The fix must be applied. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Accumulate Release 15.0 Accumulate Release 16.0 Accumulate Changes Release 15.0 Accumulate Changes Release 16.0 PFR 825 (C)2013 CA. All Rights Reserved.R01794-D16-SP1 DESC(DB2 STORAGE LEAK WITH ACCUMULATE/RECOVER IN DB2 10). FMID (CPUTG00) PRE ( RO43412 RO43445 ) SUP ( ZFRL052 ) ++IF FMID(CPFRG00) REQ(RO58490). ++IF FMID(CGENG00) REQ(RO58491). ++IF FMID(CUGRG00) REQ(RO58492). ++IF FMID(CPMMG00) REQ(RO58493).

28 CA DB2 Tools CA RS PTF RO RO58987 RO58987 M.C.S. ENTRIES = ++PTF (RO58987) INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED CA Detector for DB2 for z/os (PDT) may incorrectly report a INDB2_CPU time that is less than the corresponding ZIIP_CPU time reported. This should never occur because PDT's INDB2_CPU metric includes the ZIIP_CPU time. The INDB2_CPU time reported is less than the ZIIP_CPU time reported, as in this example from an online display: SQL_CALL INDB2_CPU ZIIP_CPU PREPARE 00: : OPEN 00: : FETCH 00: : DESCRIBE 00: : The INDB2_CPU time reported is incorrectly too low and the correct INDB2_CPU time cannot be determined. None. PRODUCT(S) AFFECTED: Detector Release 14.0 Detector Release 14.5 Detector Release 15.0 Detector Release 16.0 Detector Release 17.0 PDT 1110 (C)2013 CA. All Rights Reserved.R01855-D16-SP1 DESC(INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED). FMID (CPDTG00) PRE ( RO42750 RO44286 RO45410 RO46085 RO47745 RO47746 RO48124 RO49569 RO50557 RO53542 RO54115 RO54876 RO54974 RO55607 RO55636 RO56241 RO57651 RO57696 ) SUP ( RO44445 RO45747 RO52624 ZDTL088 ) ++HOLD (RO58987) SYSTEM FMID(CPDTG00) REASON (ACTION ) DATE (13137) COMMENT ( Product: Detector Release: 16.0 Sequence: Before updating production load libraries. Purpose: Avoidance of module mismatch related errors. Relevance: Required procedure for all users of CA Detector. Knowledge required: 1. SMP/E 2. z/os System Programming 3. CA DB2 Tools Installation and Maintenance procedures. Access required: 1. Product Libraries. Steps to Perform: The Xmanager address space must be recycled before these changes will take effect. Do not apply this maintenance to the Xmanager STEPLIB or PTILIB load libraries while the address space is active. If you are executing the Xmanager address space directly from your SMP/E target load libraries then only apply maintenance while the Xmanager address space is inactive. Applying this maintenance to an executing Xmanager address space may result in a discrepancy between

29 CA DB2 Tools CA RS PTF RO58987 those components that are dynamically loaded and those components that are loaded for the life of the Xmanager address space. This may result in unpredictable behavior of the CA-DB2 tools, cause a CA-DB2 tools failure, or compromise system and/or DB2 subsystem integrity. ).

30 CA DB2 Tools CA RS PTF RO RO59011 RO59011 M.C.S. ENTRIES = ++PTF (RO59011) ACCUMULATE CLONED TABLESPACE NOT QUIESCED When the log accumulation component of CA Merge/Modify for DB2 for z/os (PMM) creates SHRLEVEL REFERENCE full image copy of a cloned table space, base table space is quiesced instead of the cloned table space with the following consequences: 1. SHRLEVEL CHANGE full image copy is created instead of SHRLEVEL REFERENCE copy. 2. The SHRLEVEL CHANGE copy is registered as SHRLEVEL REFERENCE copy in the SYSIBM.SYSCOPY table. The CLONE keyword is not displayed in the DSNU050I message. PMM creates SHRLEVEL CHANGE full image copy instead of SHRLEVEL REFERENCE copy and registers it as SHRLEVEL REFERENCE copy in the SYSIBM.SYSCOPY table. None. PRODUCTS AFFECTED: PMM 16.0 PMM 17.0 PMM 320 (C)2013 CA. All Rights Reserved.R01815-D16-SP1 DESC(ACCUMULATE CLONED TABLESPACE NOT QUIESCED). FMID (CPMMG00) PRE ( RO42044 RO42098 RO43407 RO44038 RO44115 RO44428 RO44925 RO45799 RO54609 RO58493 ) SUP ( ZMMJ055 ) ++IF FMID(CPUTG00) REQ(RO59012).

31 CA DB2 Tools CA RS PTF RO RO59012 RO59012 M.C.S. ENTRIES = ++PTF (RO59012) ACCUMULATE CLONED TABLESPACE NOT QUIESCED When the log accumulation component of CA Merge/Modify for DB2 for z/os (PMM) creates SHRLEVEL REFERENCE full image copy of a cloned table space, base table space is quiesced instead of the cloned table space with the following consequences: 1. SHRLEVEL CHANGE full image copy is created instead of SHRLEVEL REFERENCE copy. 2. The SHRLEVEL CHANGE copy is registered as SHRLEVEL REFERENCE copy in the SYSIBM.SYSCOPY table. The CLONE keyword is not displayed in the DSNU050I message. PMM creates SHRLEVEL CHANGE full image copy instead of SHRLEVEL REFERENCE copy and registers it as SHRLEVEL REFERENCE copy in the SYSIBM.SYSCOPY table. None. PRODUCTS AFFECTED: PMM 16.0 PMM 17.0 PMM 320 (C)2013 CA. All Rights Reserved.R01815-D16-SP1 DESC(ACCUMULATE CLONED TABLESPACE NOT QUIESCED). FMID (CPUTG00) PRE ( RO43412 RO43445 ) SUP ( ZMMJ055 ) ++IF FMID(CPMMG00) REQ(RO59011).

32 CA DB2 Tools CA RS PTF RO RO59013 RO59013 M.C.S. ENTRIES = ++PTF (RO59013) RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS PROBLEM DESCRIPTION CA Fast Recover (PFR) for DB2 for z/os doesn't recover objects correctly when running RECOVER of multiple objects and one of the objects is being recovered to the last image copy, specified with 'TOCOPY LAST-COPY'. PFR job ends with RC=0, but no or only few logs are applied to the objects that are being recovered to the current time: PFR0082I - LOG APPLY PROCESSING COMPLETED SUCCESSFULLY LOG RECORDS APPLIED = 0; PAGES EXTENDED = 0 Not all needed logs are applied to the objects that are being recovered to the current time and are in inconsistent state after recovery. Run RECOVER of objects with 'TOCOPY LAST-COPY' specification in separate step without any other objects specified. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Fast Recover Release 17.0 PFR 840 (C)2013 CA. All Rights Reserved.R01832-D16-SP1 DESC(RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS). FMID (CPFRG00) PRE ( RO42042 RO42095 RO42157 RO42165 RO42846 RO43402 RO43433 RO43504 RO44032 RO44113 RO44170 RO44416 RO44425 RO44923 RO45011 RO45797 RO45803 RO45829 RO46713 RO48050 RO50765 RO51274 RO52621 RO54608 RO54668 RO55331 RO57140 RO57482 RO58490 ) SUP ( RO42856 RO43449 RO43498 RO46414 RO46727 RO46983 RO49937 RO50770 RO51221 RO52156 RO52947 ZFRL065 ) ++IF FMID(CUGRG00) REQ(RO59014). ++IF FMID(CPMMG00) REQ(RO59015).

33 CA DB2 Tools CA RS PTF RO RO59014 RO59014 M.C.S. ENTRIES = ++PTF (RO59014) RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS PROBLEM DESCRIPTION CA Fast Recover (PFR) for DB2 for z/os doesn't recover objects correctly when running RECOVER of multiple objects and one of the objects is being recovered to the last image copy, specified with 'TOCOPY LAST-COPY'. PFR job ends with RC=0, but no or only few logs are applied to the objects that are being recovered to the current time: PFR0082I - LOG APPLY PROCESSING COMPLETED SUCCESSFULLY LOG RECORDS APPLIED = 0; PAGES EXTENDED = 0 Not all needed logs are applied to the objects that are being recovered to the current time and are in inconsistent state after recovery. Run RECOVER of objects with 'TOCOPY LAST-COPY' specification in separate step without any other objects specified. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Fast Recover Release 17.0 PFR 840 (C)2013 CA. All Rights Reserved.R01832-D16-SP1 DESC(RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS). FMID (CUGRG00) PRE ( RO42043 RO42097 RO42168 RO42840 RO42848 RO43318 RO43405 RO43436 RO43454 RO43505 RO43887 RO44012 RO44035 RO44114 RO44171 RO44418 RO44427 RO44493 RO44924 RO45472 RO45798 RO45804 RO45830 RO46726 RO48051 RO48352 RO51275 RO52622 RO54610 RO55308 RO55333 RO57141 RO57148 RO57484 RO58492 ) SUP ( RO42063 RO43981 RO44754 RO45103 RO46474 RO50769 RO58179 ZFRL065 ) ++IF FMID(CPFRG00) REQ(RO59013). ++IF FMID(CPMMG00) REQ(RO59015).

34 CA DB2 Tools CA RS PTF RO RO59015 RO59015 M.C.S. ENTRIES = ++PTF (RO59015) RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS PROBLEM DESCRIPTION CA Fast Recover (PFR) for DB2 for z/os doesn't recover objects correctly when running RECOVER of multiple objects and one of the objects is being recovered to the last image copy, specified with 'TOCOPY LAST-COPY'. PFR job ends with RC=0, but no or only few logs are applied to the objects that are being recovered to the current time: PFR0082I - LOG APPLY PROCESSING COMPLETED SUCCESSFULLY LOG RECORDS APPLIED = 0; PAGES EXTENDED = 0 Not all needed logs are applied to the objects that are being recovered to the current time and are in inconsistent state after recovery. Run RECOVER of objects with 'TOCOPY LAST-COPY' specification in separate step without any other objects specified. PRODUCT(S) AFFECTED: Fast Recover Release 15.0 Fast Recover Release 16.0 Fast Recover Release 17.0 PFR 840 (C)2013 CA. All Rights Reserved.R01832-D16-SP1 DESC(RECOVER TOCOPY LAST-COPY AFFECTS ALL OBJECTS). FMID (CPMMG00) PRE ( RO42044 RO42098 RO43407 RO43455 RO44013 RO44038 RO44115 RO44116 RO44428 RO44925 RO45012 RO45799 RO45831 RO46108 RO46714 RO48110 RO48353 RO51276 RO54609 RO55332 RO58493 RO59011 ) SUP ( RO43460 RO44118 RO56301 ZFRL065 ) ++IF FMID(CPFRG00) REQ(RO59013). ++IF FMID(CUGRG00) REQ(RO59014).

35 CA DB2 Tools CA RS PTF RO RO59489 RO59489 M.C.S. ENTRIES = ++PTF (RO59489) PFL LOOPS WHEN MULTIPLE TABLES IN A TABLESPACE ARE VERSIONED CA Fast Load for DB2 for z/os (PFL) can Loop under the following conditions: 1) RESUME NO REPLACE or RESUME YES are specified. 2) PFL is loading a non versioned table 3) The tablespace is segmented and defined with multiple tables 4) There are versioned tables in the tablespace The Load begins to run but eventually abends because of storage utilization and or a VSAM dataset runs out of extensions. The loop uses up available storage and causes datasets to go into multiple extends. The following messages have been observed: IEC070I ,$L540017,PLAT1,SYS00006,BD48,DB2P43, 794 IEC070I SPDB2.DSNDBC.LCCUSTBK.COMNPARM.I0001.A001, IEC070I SPDB2.DSNDBD.LCCUSTBK.COMNPARM.I0001.A001,CATALOG.UCATDPL1 The load fails NONE PRODUCT(S) AFFECTED: PFL Release 16.0 PFL Release 17.0 PFL 1046 (C)2013 CA. All Rights Reserved.R01894-D16-SP1 DESC(PFL LOOPS WHEN MULTIPLE TABLES IN A TABLESPACE ARE VERSIONED). FMID (CPFLG00) PRE ( RO42164 RO43401 RO43431 RO44031 RO45451 RO53281 ) SUP ( RO51297 ZFLL070 )

36 CA DB2 Tools CA RS PTF RO RO59721 RO59721 M.C.S. ENTRIES = ++PTF (RO59721) ADD ABILITY TO PASS IN PRI & SEC SPACE FOR DSNUTILB CALL ENHANCEMENT DESCRIPTION: CA Fast Recover for DB2 for z/os (PFR) and CA Merge/Modify for DB2 for z/os (PMM) are being enhanced to 1) epand the fields supporting the ESTIMATED-RECS and ESTIMATED-KEYS keywords to hold a value greater than billion. PFR and PMM are also being enhanced to 2) pass in a parameter list for primary and secondary quantities to be used when a process calls a utility that may require excessive amounts of storage to be written to its SYSOUT ddname such as the output of a REPORT RECOVERY for thousands of objects. For 1) the amount of sort work space requested may not be sufficient to process the job if the quantity needed exceeds billion. For 2) the utility may fail to capture all the output if the data returned exceeds the current space allocations of (1,5) in tracks. For 1) the sort may fail due to insufficient sort work space requested. 2) the utility may fail to process the returned output from a function such as a REPORT RECOVERY. None. PRODUCT(S) AFFECTED: Fast Recover Release 16.0 Release 17.0 Release 18.0 Merge/Modify Release 16.0 Release 17.0 Release 18.0 PFR 832 (C)2013 CA. All Rights Reserved.R01858-D16-SP1 DESC(ADD ABILITY TO PASS IN PRI & SEC SPACE FOR DSNUTILB CALL). FMID (CPFRG00) PRE ( RO42095 RO42165 RO43402 RO44032 RO44113 RO44425 RO44923 RO45797 RO45829 RO46983 RO51274 RO54608 RO58490 RO59013 ) SUP ( RO50770 ZFRL069 )

37 CA DB2 Tools CA RS PTF RO RO60738 RO60738 M.C.S. ENTRIES = ++PTF (RO60738) MEDIA MANAGER ERROR PFL0024E ON LOAD RESUME INTO PART CA Fast Load for DB2 for z/os (PFL) issues message PFL0024E (GETDIR) and ends with return code 16 when running load RESUME YES into partition x - in some circumstances. The message will show the Return Code and Reason Code as 0. The error is dependent on the location of the second system page and load resume point. (System pages are created when the table is altered.) Fast Load ends with a condition code 16. Message PFL0024E is issued from UTAFLRM2.GETDIR with a zero return code. PFL0024E - MMGR GETDIR routine failed in module UTAFLRM2 TCB: <address> Buffer Address: <address> Return Code: Reason Code: DSN: <table space dataset name> The PFL0024E message is followed by snap dumps of the relevant control blocks. The tablespace partition is corrupt and will have to be recovered. None. PRODUCT(S) AFFECTED: Fast Load Release: r15 Fast Load Release: r16 Fast Load Release: r17 PFL 1047 (C)2013 CA. All Rights Reserved.R01983-D16-SP1 DESC(MEDIA MANAGER ERROR PFL0024E ON LOAD RESUME INTO PART). FMID (CPFLG00) PRE ( RO42164 RO43401 RO43431 RO44031 RO45451 RO53281 ) SUP ( RO51297 RO59489 ZFLL073 )

38 CA DB2 Tools CA RS PTF RO RO60983 RO60983 M.C.S. ENTRIES = ++PTF (RO60983) DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE CA Fast Load for DB2 for z/os (PFL) overwrites the end of an initial timestamp value with the time zone. If no time zone is specified in the TIMESTAMP THEN A DEFAULT OF '+00:00' IS USED. THE TABLE IS LOADED successfully and no error messages are logged. This problem occurs only under DB2 V10. No error messages are logged. Other applications accessing the table after the load may uncover the error. The table is loaded with an incorrect initial timestamp values. A default of '+00:00' WILL BE USED IF NO TIME ZONE IS SPECIFIED IN THE TIMESTAMP. None. PRODUCT(S) AFFECTED: Fast Load Release 15.0 Fast Load Release 16.0 Fast Load Release 17.0 PFL 1038 (C)2013 CA. All Rights Reserved.R01991-D16-SP1 DESC(DB2 V10: LAST 4 DIGITS OF TIMESTAMP OVERWRITTEN BY TIMEZONE). FMID (CPFLG00) PRE ( RO42164 RO43401 RO43431 RO44031 RO45451 ) SUP ( RO41713 RO43684 RO50165 RO57470 ZFLL072 )

39 CA DB2 Tools CA RS PTF RO RO61126 RO61126 M.C.S. ENTRIES = ++PTF (RO61126) S0C7 IN FOR ONLINE REORG INDEX CA Fast Recover for DB2 for z/os (PFR) has introduced a S0C7 when called by CA Rapid Reorg for DB2 for z/os (PRR) online reorg when PTF RO58492 is applied. This problem only impacts Index processing with DATA-AVAILABLE CRITICAL specified in the PRR syntax. S0C7 in PFR load module when called by PRR using DATA-AVAILABLE CRITICAL. The REORG of the requested object fails with the following message: POR0171I - REORG INDEX Processing Complete. Highest Return Code = 8 Avoid option DATA-AVAILABLE CRITICAL within PRR syntax. PRODUCT(S) AFFECTED: Fast Recover Release 16.0 PFR 867 S0C7 IN FOR ONLINE REORG INDEX CA Fast Recover for DB2 for z/os (PFR) has introduced a S0C7 when called by CA Rapid Reorg for DB2 for z/os (PRR) online reorg when PTF RO59721 is applied. This problem only impacts Index processing with DATA-AVAILABLE CRITICAL specified in the PRR syntax. S0C7 in PFR load module when called by PRR using DATA-AVAILABLE CRITICAL. The REORG of the requested object fails with the following message: POR0171I - REORG INDEX Processing Complete. Highest Return Code = 8 Avoid option DATA-AVAILABLE CRITICAL within PRR syntax. PRODUCT(S) AFFECTED: Fast Recover Release 16.0 PFR 864 (C)2013 CA. All Rights Reserved.R01986-D16-SP1 DESC(S0C7 IN FOR ONLINE REORG INDEX). FMID (CPFRG00) PRE ( RO42095 RO43402 RO44032 RO44113 RO44425 RO44923 RO45797 RO46983 RO51274 RO54608 RO58490 RO59013 RO59721 ) SUP ( HFRL002 ZFRL074 ZFRL075 ) ++IF FMID(CUGRG00) REQ(RO61127).

40 CA DB2 Tools CA RS PTF RO RO61127 RO61127 M.C.S. ENTRIES = ++PTF (RO61127) S0C7 IN FOR ONLINE REORG INDEX CA Fast Recover for DB2 for z/os (PFR) has introduced a S0C7 when called by CA Rapid Reorg for DB2 for z/os (PRR) online reorg when PTF RO58492 is applied. This problem only impacts Index processing with DATA-AVAILABLE CRITICAL specified in the PRR syntax. S0C7 in PFR load module when called by PRR using DATA-AVAILABLE CRITICAL. The REORG of the requested object fails with the following message: POR0171I - REORG INDEX Processing Complete. Highest Return Code = 8 Avoid option DATA-AVAILABLE CRITICAL within PRR syntax. PRODUCT(S) AFFECTED: Fast Recover Release 16.0 PFR 867 S0C7 IN FOR ONLINE REORG INDEX CA Fast Recover for DB2 for z/os (PFR) has introduced a S0C7 when called by CA Rapid Reorg for DB2 for z/os (PRR) online reorg when PTF RO59721 is applied. This problem only impacts Index processing with DATA-AVAILABLE CRITICAL specified in the PRR syntax. S0C7 in PFR load module when called by PRR using DATA-AVAILABLE CRITICAL. The REORG of the requested object fails with the following message: POR0171I - REORG INDEX Processing Complete. Highest Return Code = 8 Avoid option DATA-AVAILABLE CRITICAL within PRR syntax. PRODUCT(S) AFFECTED: Fast Recover Release 16.0 PFR 864 (C)2013 CA. All Rights Reserved.R01986-D16-SP1 DESC(S0C7 IN FOR ONLINE REORG INDEX). FMID (CUGRG00) PRE ( RO43405 RO43454 RO44114 RO44427 RO57556 RO58492 ) SUP ( HGRJ002 ZFRL074 ZFRL075 ) ++IF FMID(CPFRG00) REQ(RO61126).

41 CA DB2 Tools CA RS PTF RO RO61139 RO61139 M.C.S. ENTRIES = ++PTF (RO61139) INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH CA Detector for DB2 for z/os (PDT) may report INDB2_CPU times that are incorrectly too high. This can occur with r17 or following the APPLY of r15 PTF RO59026 or r16 PTF RO INDB2_CPU times that are clearly too high are reported. When a INDB2_CPU time is incorrectly too high, the correct INDB2_CPU time cannot be determined. None. PRODUCT(S) AFFECTED: Detector Release 15.0 Detector Release 16.0 Detector Release 17.0 PDT 1120 (C)2013 CA. All Rights Reserved.R02019-D16-SP1 DESC(INDB2_CPU TIMES REPORTED ARE INCORRECTLY TOO HIGH). FMID (CPDTG00) PRE ( RO42750 RO44286 RO45410 RO46085 RO47745 RO47746 RO48124 RO49569 RO50557 RO53542 RO54115 RO54876 RO54974 RO55607 RO55636 RO56241 RO57651 RO57696 RO58987 ) SUP ( HDTL003 RO44445 RO45747 RO52624 ZDTL095 ) ++HOLD (RO61139) SYSTEM FMID(CPDTG00) REASON (ACTION ) DATE (13199) COMMENT ( Product: Detector Release: 16.0 Sequence: Before updating production load libraries. Purpose: Avoidance of module mismatch related errors. Relevance: Required procedure for all users of CA Detector. Knowledge required: 1. SMP/E 2. z/os System Programming 3. CA DB2 Tools Installation and Maintenance procedures. Access required: 1. Product Libraries. Steps to Perform: The Xmanager address space must be recycled before these changes will take effect. Do not apply this maintenance to the Xmanager STEPLIB or PTILIB load libraries while the address space is active. If you are executing the Xmanager address space directly from your SMP/E target load libraries then only apply maintenance while the Xmanager address space is inactive. Applying this maintenance to an executing Xmanager address space may result in a discrepancy between those components that are dynamically loaded and those components that are loaded for the life of the Xmanager address space. This may result in unpredictable behavior of the CA-DB2 tools, cause a CA-DB2 tools failure, or compromise system and/or DB2 subsystem integrity. ).

42 CA DB2 Tools CA RS PTF RO RO61281 RO61281 M.C.S. ENTRIES = ++PTF (RO61281) DB2 APPLICATIONS RETURN A 00C9007F ERROR AFTER LOAD REPLACE CA Fast Load for DB2 for z/os (PFL) fails to correctly write the first spacemap and dictionary pages for a non-partitioned tablespace under the following conditions: 1) RESUME NO REPLACE is specified. 2) The tablespace is segmented and non-partitioned. 3) The page size is greater than 4K. The Load runs to completion. A subsequent DB2 application may return the following error: If the tablespace is compressed and a dictionary exists the following message may be displayed: DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C9007F, TYPE OF RESOURCE RESOURCE NAME dbname.tsname. If the tablespace is not compressed the following message may be displayed: DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90094, TYPE OF RESOURCE RESOURCE NAME dbname.tsname CA Quick Copy whether called by PFL or stand alone will return the the following error: PQC9010E - INTERNAL ERROR : INCORRECT PAGE NUMBER COMPUTED FOR RESTART - SPACEMAP PAGE : The tablespace has been corrupted and is not usable. NONE PRODUCT(S) AFFECTED: PFL Release 16.0 Release 17.0 PFL 1055 (C)2013 CA. All Rights Reserved.R02034-D16-SP1 DESC(DB2 APPLICATIONS RETURN A 00C9007F ERROR AFTER LOAD REPLACE). FMID (CPFLG00) PRE ( RO42164 RO43401 RO43431 RO44031 RO45451 RO53281 ) SUP ( HFLL001 RO51297 RO59489 RO60738 ZFLL075 )

43 CA DB2 Tools CA RS PTF RO RO58009 RO58009 M.C.S. ENTRIES = ++PTF (RO58009) S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS. CA Detector for DB2 for z/os (PDT) collection may abnormally terminate with an S0C4 in module DT$DII when executing parallel tasks. The following messages are issued in the XMANAGER's Joblog: ABEND=S0C4 MODULE=DT$DII OFFSET=XXXXXXXX DB2=xxx PDT0102 DETECTOR TERM IN PROGRESS FOR DB2=XXXX The following symptom is seen in the dump: AB/S00C4 PRCS/ REGS/A0168 Symptom Description AB/S00C4 System abend code: 00C4 PRCS/ Abend reason code: REGS/A0168 Register/PSW difference for R0A:-0168 The Detector collection terminates and will need to be restarted. None. PRODUCT(S) AFFECTED: Detector Release 15.0 Detector Release 16.0 Detector Release 17.0 PDT 1102 (C)2013 CA. All Rights Reserved.R03853-D15-SP1 DESC(S0C4 ABEND IN MODULE DT$DII WHEN EXECUTING PARALLEL TASKS.). FMID (CPDTF00) PRE ( RO28494 RO31140 RO31742 RO32719 RO33051 RO33712 RO34821 RO40847 RO41089 RO42711 RO43544 RO45546 RO46544 RO46591 RO47311 RO48122 RO49572 RO50511 RO52626 RO52878 RO53603 RO53974 RO54953 RO54983 RO55550 RO56049 RO57638 ) SUP ( HDTI001 RO28568 RO30364 RO31884 RO32058 RO32594 RO33009 RO33235 RO33336 RO34700 RO44341 RO45258 ZDTI212 ) ++HOLD (RO58009) SYSTEM FMID(CPDTF00) REASON (ACTION ) DATE (13114) COMMENT ( Product: Detector Release: 15.0 Sequence: Before updating production load libraries. Purpose: Avoidance of module mismatch related errors. Relevance: Required procedure for all users of CA Detector. Knowledge required: 1. SMP/E 2. z/os System Programming 3. CA DB2 Tools Installation and Maintenance procedures. Access required: 1. Product Libraries. Steps to Perform: The Xmanager address space must be recycled before these changes will take effect. Do not apply this maintenance to the Xmanager STEPLIB or PTILIB load libraries while the address space is active. If you are executing the Xmanager address space directly from your SMP/E target load libraries then only apply maintenance while the Xmanager address space is inactive. Applying this maintenance to an executing Xmanager address space may result in a discrepancy between

44 CA DB2 Tools CA RS PTF RO58009 those components that are dynamically loaded and those components that are loaded for the life of the Xmanager address space. This may result in unpredictable behavior of the CA-DB2 tools, cause a CA-DB2 tools failure, or compromise system and/or DB2 subsystem integrity. ).

45 CA DB2 Tools CA RS PTF RO RO59026 RO59026 M.C.S. ENTRIES = ++PTF (RO59026) INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED CA Detector for DB2 for z/os (PDT) may incorrectly report a INDB2_CPU time that is less than the corresponding ZIIP_CPU time reported. This should never occur because PDT's INDB2_CPU metric includes the ZIIP_CPU time. The INDB2_CPU time reported is less than the ZIIP_CPU time reported, as in this example from an online display: SQL_CALL INDB2_CPU ZIIP_CPU PREPARE 00: : OPEN 00: : FETCH 00: : DESCRIBE 00: : The INDB2_CPU time reported is incorrectly too low and the correct INDB2_CPU time cannot be determined. None. PRODUCT(S) AFFECTED: Detector Release 14.0 Detector Release 14.5 Detector Release 15.0 Detector Release 16.0 Detector Release 17.0 PDT 1110 (C)2013 CA. All Rights Reserved.R03887-D15-SP1 DESC(INDB2_CPU TIME REPORTED LESS THAN ZIIP_CPU TIME REPORTED). FMID (CPDTF00) PRE ( RO28494 RO31140 RO31742 RO32719 RO33051 RO33712 RO34821 RO40847 RO41089 RO42711 RO43544 RO45546 RO46544 RO46591 RO47311 RO48122 RO49572 RO50511 RO52626 RO52878 RO53603 RO53974 RO54953 RO54983 RO55550 RO56049 RO57638 RO58009 ) SUP ( HDTI001 RO28568 RO30364 RO31884 RO32058 RO32594 RO33009 RO33235 RO33336 RO34700 RO44341 RO45258 ZDTI217 ) ++HOLD (RO59026) SYSTEM FMID(CPDTF00) REASON (ACTION ) DATE (13140) COMMENT ( Product: Detector Release: 15.0 Sequence: Before updating production load libraries. Purpose: Avoidance of module mismatch related errors. Relevance: Required procedure for all users of CA Detector. Knowledge required: 1. SMP/E 2. z/os System Programming 3. CA DB2 Tools Installation and Maintenance procedures. Access required: 1. Product Libraries. Steps to Perform: The Xmanager address space must be recycled before these changes will take effect. Do not apply this maintenance to the Xmanager STEPLIB or PTILIB load libraries while the address space is active. If you are executing the Xmanager address space directly from your SMP/E target load libraries then only apply

46 CA DB2 Tools CA RS PTF RO59026 maintenance while the Xmanager address space is inactive. Applying this maintenance to an executing Xmanager address space may result in a discrepancy between those components that are dynamically loaded and those components that are loaded for the life of the Xmanager address space. This may result in unpredictable behavior of the CA-DB2 tools, cause a CA-DB2 tools failure, or compromise system and/or DB2 subsystem integrity. ).