CA DB2 Tools 18.0 1 CA RS 1511 Service List · CA DB2 Tools 6 CA RS 1511 Service List for CPDTI00...

CA DB2 Tools 18.0 1

CA RS 1511 Service ListCA DB2 Tools 18.0 1

CA RS 1511 Service List

Release Service Description Type

18.0 RO84716 TBL ROW QUERY # OF ROWS TRUNCATED GE BILLION PTF

RO84770 S0C4 IN DETECTOR WHEN HIST-ACCT-DETAIL=PDTSQL SPECIFIED PTF

RO84905 MISSING AND OBSOLETE FIELDS IN THE DB2 ARCHIVE TABLES PTF

RO84960 DT511I WHEN VIEWING DS GROUP CURRENT PACKAGE/DBRM DATA PTF

RO84979 HIGH CPU UTILIZATION FOR EXCP0258 AND EXCP0376 PTF

RO84989 NO DATA OR BLANK OUTPUT ON SOME SCREENS PTF

RO84997 PREV/NEXT ON THREAD HISTORY SHOWS A BLANK SCREEN PTF

RO85014 S0C1 AFTER SQLCODE -911 PTF

RO85015 S0C1 AFTER SQLCODE -911 PTF

RO85016 WRONG TABLE ACCESS OCCURS IN THE SQL TABLE ACTIVITY DISPLAY PTF

RO85033 SY REPORTS SHOWING EX OPTION IN HELP PTF

RO85034 SY REPORTS SHOWING EX OPTION IN HELP PTF

RO85037 FAILURE MAKING INCREMENTAL COPY FOR 1G PARTITIONED UTS PTF

RO85044 EXTRA BLANK LINE IN TABLE OBJECT DEPENDENCY PTF

RO85046 SC-R REPORT DOES NOT SHOW VERSION OF ROUTINE PTF

RO85047 .CONNECT KEYWORD MISSING USING DDL/HDDL COMMAND & REMOTE LOC PTF

RO85050 RESERVE OBID ANALYSIS OPTION IS IGNORED. PTF

RO85071 RQE00837 MESSAGE MISSING IN BATCH MODE FOR SY-Z/SY-D REPORTS PTF

RO85092 PP023E: INTERNAL ERROR IN PZA#STK1 PTF

RO85107 ADDITIONAL ERROR LOGIC WHEN READING PRODUCT PARMLIB MEMBERS PTF

RO85115 BATCH CMD IN IDENTIFY PROBLEM SQL GETS PPPPBPM PANEL ERROR PTF

RO85120 S0C1 ABEND IN UTLGLIOE OFFSET +19C PTF

RO85171 S438 ABEND IN UTLGLRI2 PTF


RO85182 IDB2ACCT DB2-CPU VALUE INCORRECT PTF

RO85200 PTATOKE SQLDA C AND C++ SUPPORT PTF

RO85222 DA CRITICAL EXTENDED CREATES NON RECOVERABLE ICS FOR PFR PTF


RO85226 APPLY RO80595 FAILS WITHOUT DETECTOR ** PRP **

RO85228 INCORRECT ENQ RNAME OF D PTF

RO85247 INVALID DATABASE NAME ON SQL TRACE DISPLAY WITH DB2 11 PTF

RO85252 GRAPHIHC/VARGRAPHIC DATA TRUNCATION IN FORM MODE PTF

RO85259 DC-GROUP SYSPARM NOT OVERRIDDEN BY LAST OCCURRENCE IN FILE PTF

RO85263 VARIABLE FORMAT DUMMY ROWID COLUMN FAILS TO LOAD PTF

RO85287 COPY USER PROFILE DURING PRFCNVRT SQL -803 PTF

RO85294 ZLB0002E DICTIONARY SEQUENTIAL ORDER REBUILD INDEX(ALL) PTF

RO85331 XNET ABEND S0C3 PXNMGXNT IXNTACAG WITH OFA SCALABILITY ** PRP **

RO85332 SQLCODE -303 WHEN USING UTILITY OPTION STATS -> 'S' PTF

RO85342 RU678E ERROR ON BROWSE OF SYSTRIGGERS PTF

RO85385 BROKEN PAGE AFTER PFL ON PARTITION V11 BIGTAIL **HIPER**


RO85391 ONLINE HELP MISSING FOR INTERVAL OPTION PTF

RO85395 ABEND S0C4 NGRABPC0 AMXSSXC0 AFTER EDB CONTROL BLOCK CHANGE PTF

RO85397 RCM0179W WHEN LRSN/RBA UPDATE ALL PAGES IN SAME SUBSYSTEM PTF

RO85418 SYSTEM_TIME COLUMN ATTRIBUTES MISSING FROM ALTER TABLE DDL PTF

RO85435 DB2 00C20110 ERROR AFTER PBG TABLESPACE REORG PTF

RO85441 INV RETCDE FROM -DISP DB DURING STRATEGY ANALYSIS PTF

RO85468 PARTIAL ITE$STCK CAUSES DATA LOSS PTF

RO85474 TRUNCATED VPSIZE DATA IN BP-DS REPORT PTF

RO85481 LBIND/LREBIND COMMANDS NOT SUPPORTED IN DB2 V10 CM8 MODE PTF

RO85521 INACCURATE CPU TIMES/STALE ZIIP TIMES FOR DISTRIBUTED THREAD PTF


RO85527 SPECIAL CHARACTERS ARE NOT DISPLAYED IN EDIT OR BROWSE PTF

RO85529 MESSAGES SCREEN IS HORIZONTALLY TRUNCATED ** PRP **

RO85561 EXPLAIN FAILS WITH SQL299 PTF

RO85565 PRR2251E INDEX DELETE ERROR PTF

CA DB2 Tools 18.0 2

CA RS 1511 Service List

Release Service Description Type


RO85569 INVALID OPTIONS GENERATED FOR PLAN LBIND & LREBIND PTF

RO85581 S0C4 DURING ONLINE EXTENDED EXTRACT PTF

RO85582 ERROR ON USING OPTION I ON XO IN COMMAND CENTER PTF

RO85583 ERROR DURING SQL LOAD PTF

RO85584 U0047 FOLLOWED BY SC03 IN EXTENDED EXTRACT SQL DELETE PTF

RO85594 TEMPORAL TABLE DROPPED AND CREATED WHEN RENAMING A COLUMN PTF

RO85604 COLLECTION TERMINATES AFTER 0C4 IN DT$DII PTF

RO85607 RQ078E WITH FLDSTAT LINE COMMAND ON THE C-D REPORT PTF


RO85614 ABEND S138 FOLLOWING ERROR IN HISTORY FILE INITIALIZATION PTF

RO85626 S0C4 S0C6 NO ACTIVE MODULE AFTER SUCCESSFUL LOAD PTF


RO85634 SEMICOLON MISSING IN ALTER TABLESPACE DDL TO CHANGE LOCKPART PTF

RO85637 OBJECT IDENTIFICATION MESSAGE PFL0747I PTF

RO85640 INCORRECT DATA REPORTED FOR IFCIDS WITH REPEATING SECTIONS PTF

RO85654 FALSE ALTER TABLE ADD COLUMN ENTRY IN DDL REPORT OR SQL PTF

RO85665 RM005E HELP PANEL DOES NOT SAY REGION SIZE BEING SMALL. PTF

RO85679 RC=16 ON COPY WHEN SHRLVL NS/R AND SSID DIFFERENT DB2 VERSIO PTF

RO85686 PSABATCH UNLOAD CAUSES DATASTORE COMPATIBILITY ERROR PTF

RO85696 CMG999 - RM632E MESSAGE NOT FOUND IN 'ISPMLIB' LIBRARY PTF

RO85707 PBG GROWING ABEND S13E PUT9807E RC 8 RSN 02000000 PTF



RO85710 DROP & ADD VERSIONING GENERATED WHEN TEMPORAL TBLS COMPARED PTF

RO85734 PFR0688E WHEN ONE TABLE IN TABLE SPACE PTF

RO85758 IDB2UIFI DBG73106E FILE ALREADY LOADED WHEN FILE IS EMPTY ** PRP **

RO85759 NO DATA SCREEN AFTER PICK WITH INVALID SSID PTF

RO85821 DYN_TEXT_TOKEN IN PDT_STANTEXT TABLE CONTAINS SPACES PTF

RO85854 PFR0221E EXISTING OBID FOUND WITHOUT NEW OBID PTF

RO85856 COLUMN FILTERS CANNOT BE TURNED ON PTF

RO85859 VERSION MISMATCH BETWEEN BSDS AND DB2 RELEASE PTF

RO85894 ONE CHARACTER CREATOR OR OBJECT ISSUE/S0C1/SQL -311 PTF

RO85922 SQL ERROR WHEN UPDATING A TABLE WITH VARYING LENGTH IX NAMES PTF

RO85926 ENH: PAD SAAS UNLOAD PTF

RO85941 ABEND S0C4 IN UTL#SYM WHEN USING TEMPLATE TO ALLOCATE COPIES PTF

RO85943 EXECUTION ALTER TABLE FAILS WITH SQLCODE -20385 PTF

RO85958 LBIND/LREBIND ON PLAN OR PACKAGE FAILS WITH S0C4 PTF

RO85972 BROKEN PAGE AFTER PRR ON PARTITION V11 BIGTAIL PTF

The CA RS 1511 service count for this release is 95

CA DB2 Tools 3

CA RS 1511 Service List for CIDBI00CA DB2 Tools 3

CA RS 1511 Service List for CIDBI00

FMID Service Description Type

CIDBI00 RO84770 S0C4 IN DETECTOR WHEN HIST-ACCT-DETAIL=PDTSQL SPECIFIED PTF

RO84905 MISSING AND OBSOLETE FIELDS IN THE DB2 ARCHIVE TABLES PTF

RO84979 HIGH CPU UTILIZATION FOR EXCP0258 AND EXCP0376 PTF

RO84989 NO DATA OR BLANK OUTPUT ON SOME SCREENS PTF

RO84997 PREV/NEXT ON THREAD HISTORY SHOWS A BLANK SCREEN PTF

RO85182 IDB2ACCT DB2-CPU VALUE INCORRECT PTF

RO85259 DC-GROUP SYSPARM NOT OVERRIDDEN BY LAST OCCURRENCE IN FILE PTF

RO85395 ABEND S0C4 NGRABPC0 AMXSSXC0 AFTER EDB CONTROL BLOCK CHANGE PTF

RO85529 MESSAGES SCREEN IS HORIZONTALLY TRUNCATED ** PRP **

RO85614 ABEND S138 FOLLOWING ERROR IN HISTORY FILE INITIALIZATION PTF

RO85640 INCORRECT DATA REPORTED FOR IFCIDS WITH REPEATING SECTIONS PTF

RO85758 IDB2UIFI DBG73106E FILE ALREADY LOADED WHEN FILE IS EMPTY ** PRP **

RO85759 NO DATA SCREEN AFTER PICK WITH INVALID SSID PTF

RO85856 COLUMN FILTERS CANNOT BE TURNED ON PTF

The CA RS 1511 service count for this FMID is 14

CA DB2 Tools 4

CA RS 1511 Service List for CINSI00CA DB2 Tools 4

CA RS 1511 Service List for CINSI00


CINSI00 RO85033 SY REPORTS SHOWING EX OPTION IN HELP PTF

RO85047 .CONNECT KEYWORD MISSING USING DDL/HDDL COMMAND & REMOTE LOC PTF

RO85050 RESERVE OBID ANALYSIS OPTION IS IGNORED. PTF

RO85092 PP023E: INTERNAL ERROR IN PZA#STK1 PTF

RO85107 ADDITIONAL ERROR LOGIC WHEN READING PRODUCT PARMLIB MEMBERS PTF

RO85200 PTATOKE SQLDA C AND C++ SUPPORT PTF

RO85226 APPLY RO80595 FAILS WITHOUT DETECTOR ** PRP **

RO85228 INCORRECT ENQ RNAME OF D PTF

RO85332 SQLCODE -303 WHEN USING UTILITY OPTION STATS -> 'S' PTF

RO85397 RCM0179W WHEN LRSN/RBA UPDATE ALL PAGES IN SAME SUBSYSTEM PTF

RO85418 SYSTEM_TIME COLUMN ATTRIBUTES MISSING FROM ALTER TABLE DDL PTF

RO85481 LBIND/LREBIND COMMANDS NOT SUPPORTED IN DB2 V10 CM8 MODE PTF


RO85561 EXPLAIN FAILS WITH SQL299 PTF

RO85569 INVALID OPTIONS GENERATED FOR PLAN LBIND & LREBIND PTF

RO85594 TEMPORAL TABLE DROPPED AND CREATED WHEN RENAMING A COLUMN PTF


RO85634 SEMICOLON MISSING IN ALTER TABLESPACE DDL TO CHANGE LOCKPART PTF

RO85679 RC=16 ON COPY WHEN SHRLVL NS/R AND SSID DIFFERENT DB2 VERSIO PTF

RO85696 CMG999 - RM632E MESSAGE NOT FOUND IN 'ISPMLIB' LIBRARY PTF

RO85710 DROP & ADD VERSIONING GENERATED WHEN TEMPORAL TBLS COMPARED PTF

RO85894 ONE CHARACTER CREATOR OR OBJECT ISSUE/S0C1/SQL -311 PTF

RO85926 ENH: PAD SAAS UNLOAD PTF

RO85943 EXECUTION ALTER TABLE FAILS WITH SQLCODE -20385 PTF

RO85958 LBIND/LREBIND ON PLAN OR PACKAGE FAILS WITH S0C4 PTF


CA DB2 Tools 5

CA RS 1511 Service List for CPDAI00CA DB2 Tools 5

CA RS 1511 Service List for CPDAI00


CPDAI00 RO84716 TBL ROW QUERY # OF ROWS TRUNCATED GE BILLION PTF


CA DB2 Tools 6

CA RS 1511 Service List for CPDTI00CA DB2 Tools 6

CA RS 1511 Service List for CPDTI00


CPDTI00 RO84960 DT511I WHEN VIEWING DS GROUP CURRENT PACKAGE/DBRM DATA PTF

RO85016 WRONG TABLE ACCESS OCCURS IN THE SQL TABLE ACTIVITY DISPLAY PTF

RO85247 INVALID DATABASE NAME ON SQL TRACE DISPLAY WITH DB2 11 PTF

RO85468 PARTIAL ITE$STCK CAUSES DATA LOSS PTF


RO85604 COLLECTION TERMINATES AFTER 0C4 IN DT$DII PTF

RO85821 DYN_TEXT_TOKEN IN PDT_STANTEXT TABLE CONTAINS SPACES PTF


CA DB2 Tools 7

CA RS 1511 Service List for CPFLI00CA DB2 Tools 7

CA RS 1511 Service List for CPFLI00


CPFLI00 RO85014 S0C1 AFTER SQLCODE -911 PTF


RO85263 VARIABLE FORMAT DUMMY ROWID COLUMN FAILS TO LOAD PTF



RO85637 OBJECT IDENTIFICATION MESSAGE PFL0747I PTF


RO85922 SQL ERROR WHEN UPDATING A TABLE WITH VARYING LENGTH IX NAMES PTF


CA DB2 Tools 8

CA RS 1511 Service List for CPFUI00CA DB2 Tools 8

CA RS 1511 Service List for CPFUI00


CPFUI00 RO85708 PBG GROWING ABEND S13E PUT9807E RC 8 RSN 02000000 PTF


CA DB2 Tools 9

CA RS 1511 Service List for CPLAI00CA DB2 Tools 9

CA RS 1511 Service List for CPLAI00


CPLAI00 RO85654 FALSE ALTER TABLE ADD COLUMN ENTRY IN DDL REPORT OR SQL PTF


CA DB2 Tools 10

CA RS 1511 Service List for CPPAI00CA DB2 Tools 10

CA RS 1511 Service List for CPPAI00


CPPAI00 RO85115 BATCH CMD IN IDENTIFY PROBLEM SQL GETS PPPPBPM PANEL ERROR PTF


CA DB2 Tools 11

CA RS 1511 Service List for CPRAI00CA DB2 Tools 11

CA RS 1511 Service List for CPRAI00


CPRAI00 RO85441 INV RETCDE FROM -DISP DB DURING STRATEGY ANALYSIS PTF

RO85859 VERSION MISMATCH BETWEEN BSDS AND DB2 RELEASE PTF


CA DB2 Tools 12

CA RS 1511 Service List for CPRFI00CA DB2 Tools 12

CA RS 1511 Service List for CPRFI00


CPRFI00 RO85287 COPY USER PROFILE DURING PRFCNVRT SQL -803 PTF

RO85391 ONLINE HELP MISSING FOR INTERVAL OPTION PTF


CA DB2 Tools 13

CA RS 1511 Service List for CPRRI00CA DB2 Tools 13

CA RS 1511 Service List for CPRRI00


CPRRI00 RO85120 S0C1 ABEND IN UTLGLIOE OFFSET +19C PTF


RO85435 DB2 00C20110 ERROR AFTER PBG TABLESPACE REORG PTF


RO85972 BROKEN PAGE AFTER PRR ON PARTITION V11 BIGTAIL PTF


CA DB2 Tools 14

CA RS 1511 Service List for CPSAI00CA DB2 Tools 14

CA RS 1511 Service List for CPSAI00


CPSAI00 RO85686 PSABATCH UNLOAD CAUSES DATASTORE COMPATIBILITY ERROR PTF


CA DB2 Tools 15

CA RS 1511 Service List for CPUTI00CA DB2 Tools 15

CA RS 1511 Service List for CPUTI00


CPUTI00 RO85015 S0C1 AFTER SQLCODE -911 PTF







RO85941 ABEND S0C4 IN UTL#SYM WHEN USING TEMPLATE TO ALLOCATE COPIES PTF


CA DB2 Tools 16

CA RS 1511 Service List for CPXNI00CA DB2 Tools 16

CA RS 1511 Service List for CPXNI00


CPXNI00 RO85331 XNET ABEND S0C3 PXNMGXNT IXNTACAG WITH OFA SCALABILITY ** PRP **


CA DB2 Tools 17

CA RS 1511 Service List for CRCMI00CA DB2 Tools 17

CA RS 1511 Service List for CRCMI00


CRCMI00 RO85665 RM005E HELP PANEL DOES NOT SAY REGION SIZE BEING SMALL. PTF


CA DB2 Tools 18

CA RS 1511 Service List for CRCQI00CA DB2 Tools 18

CA RS 1511 Service List for CRCQI00


CRCQI00 RO85034 SY REPORTS SHOWING EX OPTION IN HELP PTF

RO85044 EXTRA BLANK LINE IN TABLE OBJECT DEPENDENCY PTF

RO85046 SC-R REPORT DOES NOT SHOW VERSION OF ROUTINE PTF

RO85071 RQE00837 MESSAGE MISSING IN BATCH MODE FOR SY-Z/SY-D REPORTS PTF

RO85474 TRUNCATED VPSIZE DATA IN BP-DS REPORT PTF



CA DB2 Tools 19

CA RS 1511 Service List for CRCUI00CA DB2 Tools 19

CA RS 1511 Service List for CRCUI00


CRCUI00 RO85252 GRAPHIHC/VARGRAPHIC DATA TRUNCATION IN FORM MODE PTF

RO85342 RU678E ERROR ON BROWSE OF SYSTRIGGERS PTF

RO85527 SPECIAL CHARACTERS ARE NOT DISPLAYED IN EDIT OR BROWSE PTF


CA DB2 Tools 20

CA RS 1511 Service List for CRCXI00CA DB2 Tools 20

CA RS 1511 Service List for CRCXI00


CRCXI00 RO85581 S0C4 DURING ONLINE EXTENDED EXTRACT PTF

RO85582 ERROR ON USING OPTION I ON XO IN COMMAND CENTER PTF

RO85583 ERROR DURING SQL LOAD PTF

RO85584 U0047 FOLLOWED BY SC03 IN EXTENDED EXTRACT SQL DELETE PTF


CA DB2 Tools 21

CA RS 1511 Service List for CUGRI00CA DB2 Tools 21

CA RS 1511 Service List for CUGRI00


CUGRI00 RO85037 FAILURE MAKING INCREMENTAL COPY FOR 1G PARTITIONED UTS PTF

RO85294 ZLB0002E DICTIONARY SEQUENTIAL ORDER REBUILD INDEX(ALL) PTF

RO85734 PFR0688E WHEN ONE TABLE IN TABLE SPACE PTF

RO85854 PFR0221E EXISTING OBID FOUND WITHOUT NEW OBID PTF


CA DB2 Tools 18.0 22

CA RS 1511 - PTF RO84716 DetailsCA DB2 Tools 18.0 22

CA RS 1511 - PTF RO84716 Details

Release Service Details18.0 RO84716 RO84716 M.C.S. ENTRIES = ++PTF (RO84716)

TBL ROW QUERY # OF ROWS TRUNCATED GE BILLION

PROBLEM DESCRIPTION:

CA Database Analyzer for DB2 for z/OS (PDA) online query report

TABLE ROW ANALYSIS will truncate the row count when the number of

rows reaches one billion.

SYMPTOMS:

Leftmost digit is missing from a row count of one billion or more.

IMPACT:

Row count is inaccurate for the TABLE ROW ANALYSIS report.

CIRCUMVENTION:

none

PRODUCT(S) AFFECTED:

CA Database Analyzer For DB2 for z/OS Version 18.0

CA Database Analyzer For DB2 for z/OS Version 19.0

Related Problem:

PDA 1291

Copyright (C) 2015 CA. All rights reserved. R01082-D180-SP1

DESC(TBL ROW QUERY # OF ROWS TRUNCATED GE BILLION).

++VER (Z038)

FMID (CPDAI00)

PRE ( RO75317 )

SUP ( TR84716 )





S0C4 IN DETECTOR WHEN HIST-ACCT-DETAIL=PDTSQL SPECIFIED


A CA Detector for DB2 for z/OS (PDT) collection can terminate abnormally

due to S0C4 abends when the HIST-ACCT-DETAIL=PDTSQL option is specified

in the parameters for a CA SYSVIEW Performance Management Option for DB2 for

z/OS (IDB2) data collector.

SYMPTOMS:

The following messages appear in the Xmanager log:

PDT0185 ABEND=S0C4 MODULE=*UNKNOWN* ADDRESS=...

PDT0102 DETECTOR TERM IN PROGRESS FOR DB2=ssid

PDT0730 DETECTOR TERM CLEANUP IN PROGRESS DB2=ssid

PDT0732 DETECTOR TERM CLEANUP COMPLETE DB2=ssid

PDT0103 DETECTOR TERM COMPLETE FOR DB2=ssid

IMPACT:

The PDT collection terminates and must be restarted manually.

CIRCUMVENTION:

Don't specify the HIST-ACCT-DETAIL=PDTSQL option in the parameters for the

IDB2 data collector.


CA SYSVIEW Performance Management Option for DB2 for z/OS Release 19.0


CA Detector for DB2 for z/OS Release 19.0


Related Problem:

IDB2 1883


DESC(S0C4 IN DETECTOR WHEN HIST-ACCT-DETAIL=PDTSQL SPECIFIED).

++VER (Z038)

FMID (CIDBI00)

PRE ( RO74129 RO74677 RO74879 RO75439 RO76367 RO76485

RO78961 )

SUP ( RO83216 TR82434 TR83216 TR84770 )

++HOLD (RO84770) SYSTEM FMID(CIDBI00)

REASON (ACTION ) DATE (15273)

COMMENT (

+----------------------------------------------------------------------+

| CA SYSVIEW Performance Management Option for DB2 for z/OS |

| Version 18.0 |

+----------+-----------------------------------------------------------+

|SEQUENCE | After Apply |

+----------+-----------------------------------------------------------+

|PURPOSE | To make the new version of IDBPDTCC available to Xmanager.|

+----------+-----------------------------------------------------------+

|USERS |Users of the PDTSQL option of the HIST-ACCT-DETAIL sysparm |

|AFFECTED | |

+----------+-----------------------------------------------------------+

|KNOWLEDGE |SMP/E, IEBCOPY. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS |Libary access to the product load libraries. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************

* STEPS TO PERFORM *

**************************

After application of this fix, the load module IDBPDTCC must be

copied to the Xmanager STEPLIB, and the Xmanager must be recycled,

in order for this fix to take effect if you use the PDTSQL option

of the HIST-ACCT-DETAIL sysparm.

).





MISSING AND OBSOLETE FIELDS IN THE DB2 ARCHIVE TABLES


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) NSIGMIGA

Archive Table Migration Utility does not include fields introduced in

release 18.0 and does not allow replacing obsolete DB2 fields by zero

fields.

SYMPTOMS:

Archive tables migrated to release 19.0 from release 16.0 or 17.0 with the

Archive Migration Utility will not contain fields introduced in 18.0.

The fields from non-supported DB2 releases are still referenced in the

archiving IQL requests when the archive tables are migrated to releases

18.0 or 19.0 using the Archive Table Migration Utility (NSIGMIGA).

IMPACT:

Missing and obsolete fields in the migrated archive tables.

CIRCUMVENTION:

Manually update archive tables DDL, load control statements and IQL requests

to include fields introduced in release 18.0 and replace obsolete fields in

IQL requests. Refer the documentation for the list of fields.


CA SYSVIEW Performance Management Option for DB2 for z/OS Version 18.0


Related Problem:

IDB2 1878


DESC(MISSING AND OBSOLETE FIELDS IN THE DB2 ARCHIVE TABLES).

++VER (Z038)

FMID (CIDBI00)

SUP ( RO73704 TR73704 TR84905 )





DT511I WHEN VIEWING DS GROUP CURRENT PACKAGE/DBRM DATA


CA Detector for DB2 for z/OS (PDT) may display a misleading

DT511I message and return no data when viewing the DS GROUP

CURRENT PACKAGE/DBRM DATA. The DT511I message appears when the

current interval is nowhere near being elapsed.

SYMPTOMS:

The following message appears

DT511I: Current collection interval has elapsed.

IMPACT:

No data is displayed and a misleading DT511I message is issued.

CIRCUMVENTION:

The expected information usually is displayed after a few subsequent

attempts.


Detector Release 17.0

Detector Version 18.0


Related Problem:

PDT 1329


DESC(DT511I WHEN VIEWING DS GROUP CURRENT PACKAGE/DBRM DATA).

++VER (Z038)

FMID (CPDTI00)

PRE ( RO77329 )

SUP ( TR84960 )

++HOLD (RO84960) SYSTEM FMID(CPDTI00)

REASON (RESTART) DATE (15271)

COMMENT (

+----------------------------------------------------------------------+

| CA Detector for DB2 for z/OS Version 18.0 |

+----------+-----------------------------------------------------------+

|SEQUENCE | Before Apply |

+----------+-----------------------------------------------------------+

|PURPOSE | Avoidance of module mismatch related errors in an Xmanager|

+----------+-----------------------------------------------------------+

|USERS | Collections of DB2 statistics via Detector or Subsystem |

|AFFECTED | Analyzer. |

| | DB2 subsystems that have active collections. |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | 1. SMP/E |

|REQUIRED | 2. z/OS System Programming |

| | 3. CA DB2 Tools Installation and Maintenance procedures. |

+----------+-----------------------------------------------------------+

|ACCESS | 1. Product runtime libraries. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************

To implement the PTF:

1. Stop product collections.

2. Stop the Xmanager task.

3. Update the runtime library.

4. Restart the Xmanager task.

Important!

Please do not apply maintenance to the Xmanager runtime libraries with

Xmanager active as it may result in a discrepancy between

dynamically loaded components and statically loaded components.

This may result in unpredictable behavior with CA-DB2 tools and/or may



Release Service Detailscompromise the operating system/DB2 including possible failures.

).





HIGH CPU UTILIZATION FOR EXCP0258 AND EXCP0376


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) IQL

exceptions EXCP0258 and EXCP0376 have a default "Number of seconds to

display after last occurrence" set to 1 week. This might lead to extensive

number of exception occurrences to be kept in memory, causing high CPU

overhead. The default display time for these exceptions has been reduced to

1 hour and related IQL requests were updated to be reset at midnight.

SYMPTOMS:

High CPU utilization when collection of IFCIDs 258 and 376 is active.

IMPACT:

High CPU utilization.

CIRCUMVENTION:

Update the definitions of EXCP0258 and EXCP0376 IQL exceptions to set the

"Number of seconds to display after last occurrence" field to a smaller

value.




Related Problem:

IDB2 1866


DESC(HIGH CPU UTILIZATION FOR EXCP0258 AND EXCP0376).

++VER (Z038)

FMID (CIDBI00)


RO81582 )

SUP ( TR84979 )



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+

|SEQUENCE | Before Exception System Restart. |

+----------+-----------------------------------------------------------+

|PURPOSE | Default definitions of the IQL exceptions EXCP0258 and |

| | EXCP0376 were udpated so that "Number of seconds to |

| | display after last occurrence" are set to 1 hour instead |

| | of 1 week. However this change is only automatically |

| | applied when an empty exception file is initially |

| | formatted after the product installation. So manual action|

| | is required to change the exception definitions provided |

| | the exceptions are active. |

+----------+-----------------------------------------------------------+

|USERS | All users. |

|AFFECTED | |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | Product administration. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS | Update access to the "Permanent Exception Definitions". |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************

1. Go to menu "0 Permanent Exception Definitions"

2. Choose "4 External/IQL Based Exceptions (Shadow Definitions)"



Release Service Details3a. Select "EXCP0258" with "U" action to update the exception.

3b. Select "Exception Display Control" with "S" action.

3c. Enter "3600" into the field "Number of seconds to display after

last occurrence", press Enter to save the changes and then

PF3 to go back to the exception list.

4a. Select "EXCP0376" with "U" action to update the exception.

4b. Select "Exception Display Control" with "S" action.

4c. Enter "3600" into the field "Number of seconds to display after

last occurrence", press Enter to save the changes and then

PF3 to go back to the exception list.

).





NO DATA OR BLANK OUTPUT ON SOME SCREENS


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) fails to

allocate a sufficient buffer for the output of some IQL requests.

This causes the user interface to display the 'no data' information panel

or a blank output screen. The probability of this defect is dependent on the

size of the request output. Requests requiring a large output buffer, such as

the System Parameters (SYSPARMS) and the Active Threads (THRDACTV) are most

likely to be affected.

SYMPTOMS:

The System Parameters screen (option 1.6.3) produces no output.

IMPACT:

Some online IQL request output cannot be displayed.

CIRCUMVENTION:

None.




CA Insight Database Performance Monitor for DB2 for z/OS Release 17.0


Related Problem:

IDB2 1886


DESC(NO DATA OR BLANK OUTPUT ON SOME SCREENS).

++VER (Z038)

FMID (CIDBI00)


RO81132 RO82325 RO83711 )

SUP ( TR84989 )





PREV/NEXT ON THREAD HISTORY SHOWS A BLANK SCREEN


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) fails to

correctly navigate between multiple threads in thread history.

When a thread detail is selected from option 6.2 (Thread History - List all

Threads), PF5 and PF6 should allow for inspecting the previous and the next

thread respectively. Occasionally this operation fails and blank output or

the contents of the current screen is displayed instead.

SYMPTOMS:

Blank screen is displayed when PF5 or PF6 is pressed on one of the history

thread detail screens.

IMPACT:

Browsing through multiple thread details in history is cumbersome.

CIRCUMVENTION:

None.





Related Problem:

IDB2 1890


DESC(PREV/NEXT ON THREAD HISTORY SHOWS A BLANK SCREEN).

++VER (Z038)

FMID (CIDBI00)


RO74826 RO74879 RO75439 RO77072 RO77678 RO78738

RO78961 RO80610 RO81947 RO82325 RO82720 RO83711 )

SUP ( RO81327 TR81327 TR84997 )





S0C1 AFTER SQLCODE -911


CA Fast Load for DB2 for z/OS (PFL) can abnormally terminate with a S0C1 when

experiencing a contention issue while updating the restart tables. Instead

of abending, PFL should attempt to retry what it was doing when the

contention occurred.

SYMPTOMS:

PFL will issue an error message and issue an SQL error from DB2. The DB2

error is as follows:

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN

ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON 00C9008E, TYPE

OF RESOURCE 00000210, AND RESOURCE NAME xxxxxxxx.yyyyyyyy.000-

00003

and the PFL-issued PUT error message is:

PUT4315W - Update failed with SQLCODE -911

** Attempting RETRY **

In certain situations, there will not be a PUT message.

IMPACT:

Error message PFL0713E will be issued and the product will stop processing or

abnormally terminate.

CIRCUMVENTION:

None.


CA Fast Load for DB2 for z/OS Version 18.0


Related Problem:

PFL 1157


DESC(S0C1 AFTER SQLCODE -911).

++VER (Z038)

FMID (CPFLI00)

PRE ( RO75158 RO79586 RO82275 RO83759 RO83928 )

SUP ( TR83595 TR85014 )

++IF FMID(CPUTI00) REQ(RO85015 ) .





S0C1 AFTER SQLCODE -911


CA Fast Load for DB2 for z/OS (PFL) can abnormally terminate with a S0C1 when

experiencing a contention issue while updating the restart tables. Instead

of abending, PFL should attempt to retry what it was doing when the

contention occurred.

SYMPTOMS:

PFL will issue an error message and issue an SQL error from DB2. The DB2

error is as follows:

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN

ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON 00C9008E, TYPE

OF RESOURCE 00000210, AND RESOURCE NAME xxxxxxxx.yyyyyyyy.000-

00003

and the PFL-issued PUT error message is:

PUT4315W - Update failed with SQLCODE -911

** Attempting RETRY **

In certain situations, there will not be a PUT message.

IMPACT:

Error message PFL0713E will be issued and the product will stop processing or

abnormally terminate.

CIRCUMVENTION:

None.




Related Problem:

PFL 1157


DESC(S0C1 AFTER SQLCODE -911).

++VER (Z038)

FMID (CPUTI00)

PRE ( RO75346 RO76023 RO76036 RO79589 RO82277 RO83760 )

SUP ( RO81867 TR81659 TR81867 TR85015 )

++IF FMID(CPFLI00) REQ(RO85014 ) .





WRONG TABLE ACCESS OCCURS IN THE SQL TABLE ACTIVITY DISPLAY


CA Detector for DB2 for z/OS (PDT) may sometimes show an unrelated table on

the Detector SQL Table Activity Display. Similarly, when viewing the DETECTOR

Table SQL Activity Display from CA Subsystem Analyzer for DB2 for z/OS (PSA),

an SQL program statement may be associated to the unrelated table.

This occurs when executing synchronized Detector and Subsystem Analyzer

collections.

SYMPTOMS:

The wrong table access is observed in the DETECTOR SQL Table Activity

Display. Likewise, the wrong SQL program statement is listed in the PSA

DETECTOR Table SQL Activity Display.

IMPACT:

Incorrect information about the system and SQL path is reported.

CIRCUMVENTION:

None.





Related Problem:

PDT 1318


DESC(WRONG TABLE ACCESS OCCURS IN THE SQL TABLE ACTIVITY DISPLAY).

++VER (Z038)

FMID (CPDTI00)


RO80897 RO83209 RO83388 RO83695 )

SUP ( TR85016 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************






Important!





Release Service Detailsdynamically loaded components and statically loaded components.


compromise the operating system/DB2 including possible failures.

).





SY REPORTS SHOWING EX OPTION IN HELP


In CA RC/Query for DB2 for z/OS (RCQ), the System(SY) reports show Execute

Clist/REXX (EX) as line command in help panel.

SYMPTOMS:

User defined line command EX is not valid on SY reports yet it is shown in

help panel.

IMPACT:

User may be misled with incorrect help panel.

CIRCUMVENTION:

None.


CA RC/Query for DB2 for z/OS Release 17.0

CA RC/Query for DB2 for z/OS Version 18.0


Related Problem:

RCQ 1493


DESC(SY REPORTS SHOWING EX OPTION IN HELP).

++VER (Z038)

FMID (CINSI00)

SUP ( TR85033 )

++IF FMID(CRCQI00) REQ(RO85034 ) .





SY REPORTS SHOWING EX OPTION IN HELP


In CA RC/Query for DB2 for z/OS (RCQ), the System(SY) reports show Execute

Clist/REXX (EX) as line command in help panel.

SYMPTOMS:

User defined line command EX is not valid on SY reports yet it is shown in

help panel.

IMPACT:

User may be misled with incorrect help panel.

CIRCUMVENTION:

None.


CA RC/Query for DB2 for z/OS Release 17.0



Related Problem:

RCQ 1493


DESC(SY REPORTS SHOWING EX OPTION IN HELP).

++VER (Z038)

FMID (CRCQI00)

PRE ( RO74958 RO75207 )

SUP ( TR85034 )

++IF FMID(CINSI00) REQ(RO85033 ) .





FAILURE MAKING INCREMENTAL COPY FOR 1G PARTITIONED UTS


CA Quick Copy for DB2 for z/OS (PQC) may fail to create an incremental copy

for DSSIZE 1G partitioned universal tablespaces.

Note: This is a fix for EXCP NO processing only. Fix for EXCP YES will be

provided separately.

SYMPTOMS:

PQC creates empty copy or copy containing just header page and segmented map

IMPACT:

The copy created is unusable.

CIRCUMVENTION:

Specify LRSNCOPY YES in the SYSIN.


Quick Copy Release 17.0



Related Problem:

PQC 792


DESC(FAILURE MAKING INCREMENTAL COPY FOR 1G PARTITIONED UTS).

++VER (Z038)

FMID (CUGRI00)

PRE ( RO74952 RO75457 RO76025 RO76037 )

SUP ( RO78779 TR78779 TR85037 )





EXTRA BLANK LINE IN TABLE OBJECT DEPENDENCY

PROBLEM DESCRIPTION:d

In CA RC/Query for DB2 for z/OS(RCQ), the Table object dependency report

display contain an extra blank line in the report.

SYMPTOMS:

Extra line inserted in the object dependancy for table object.

IMPACT:

The blank line is confusing and taking space.

CIRCUMVENTION:

None

Related Problem:

RCQ 1496


DESC(EXTRA BLANK LINE IN TABLE OBJECT DEPENDENCY).

++VER (Z038)

FMID (CRCQI00)

SUP ( TR85044 )





SC-R REPORT DOES NOT SHOW VERSION OF ROUTINE


In CA RC/Query for DB2 for z/OS (RCQ), the Schema-Routine(SC-R) report does

not show the version of a routine associated to a schema.

SYMPTOMS:

The Schema-routine(SC-R) report displays all routines but does not show

version of a routine.

IMPACT:

You will not be able to identify the uniqueness of a routine.

CIRCUMVENTION:

NONE.





Related Problem:

RCQ 1491


DESC(SC-R REPORT DOES NOT SHOW VERSION OF ROUTINE).

++VER (Z038)

FMID (CRCQI00)

PRE ( RO75328 )

SUP ( TR85046 )

++HOLD (RO85046) SYSTEM FMID(CRCQI00)

REASON (DB2BIND) DATE (15282)

COMMENT (

+----------------------------------------------------------------------+

| CA RC/Query for DB2 for z/OS Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|PURPOSE | Bind Plans and Packages |

+----------+-----------------------------------------------------------+

|USERS | |

|AFFECTED | All Users |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | |

|REQUIRED | CA DB2 Tools Post Install Customization. |

+----------+-----------------------------------------------------------+

|ACCESS | 1. CA DB2 Tools Post Install |

|REQUIRED | 2. BIND, SYSADM or SYSCNTL on DB2 subsystem. |

+----------+-----------------------------------------------------------+

**************************


**************************

DBRMs have changed as part of this maintenance. Refer to the

Implementation Guide for details on how to perform the following step.

1. Use Post-Install Tailoring option to Bind Product Packages and Plans.

).





.CONNECT KEYWORD MISSING USING DDL/HDDL COMMAND & REMOTE LOC


In CA RC/Query for DB2 for z/OS(RCQ), DDL or HDDL command does not generate a

.CONNECT batch processor statement when using remote location.

SYMPTOMS:

.CONNECT is missing when executing DDL/HDDL command with a remote location

which results in following error.

BPA0159E: UNABLE TO DETERMINE DB2 VERSION -OR- A .CONNECT

PROBLEM TO DB2 EXISTS; PROCESSING TERMINATED.

NEXT STATEMENT TO EXECUTE IS:

IMPACT:

Batch processor ends with return code = 16.

CIRCUMVENTION:

You need to manually insert .CONNECT SSID statement at the beginning.

Related Problem:

RCQ 1494


DESC(.CONNECT KEYWORD MISSING USING DDL/HDDL COMMAND & REMOTE LOC).

++VER (Z038)

FMID (CINSI00)

PRE ( RO82105 )

SUP ( TR85047 )





RESERVE OBID ANALYSIS OPTION IS IGNORED.


In CA RC/Migrator for DB2 for z/OS (RCM), while executing an RC/Merger (RMM)

analysis on a strategy with the Reserve OBID option selected, RMM fails to

reserve the OBID for the table resulting in OBID translation.

SYMPTOMS:

While executing analysis, following message is displayed:

RCM0136I - TABLE OBID 3 WAS UNAVAILABLE. RC/MERGER WILL

PERFORM OBID TRANSLATION FROM 3 TO 6

FOR TABLE CHOSA16.TB1SLAM6.

IMPACT:

Table at target side is created with different OBID and performance is

affected due to OBID translations.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED: RC/Migrator Release 18.0

RC/Migrator Release 19.0

Related Problem:

RMM 203


DESC(RESERVE OBID ANALYSIS OPTION IS IGNORED.).

++VER (Z038)

FMID (CINSI00)


SUP ( RO76219 RO84719 RO84941 TR76219 TR84678 TR84719

TR84941 TR85050 )

++HOLD (RO85050) SYSTEM FMID(CINSI00)

REASON (MSGSKEL) DATE (15274)

COMMENT (

+----------------------------------------------------------------------+

| CA Database Management Solution for DB2 for zOS Base Install |

| Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|PURPOSE | Relink XMESSAGES |

+----------+-----------------------------------------------------------+

|USERS | |

|AFFECTED | All CA DB2 Tools Users |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+


|REQUIRED | 2. BIND Authority on DB2 subsystems |

+----------+-----------------------------------------------------------+

**************************


**************************

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

1. Re-apply XMESSAGE customizations and relink XMESSAGE load modules.

Refer to the Post Installation and Customization Guide for details.

).





RQE00837 MESSAGE MISSING IN BATCH MODE FOR SY-Z/SY-D REPORTS


In CA RC/Query for DB2 for z/OS (RCQ), the SY-Z and SY-D reports do not

show XMSG RQE00387 in batch mode.

SYMPTOMS:

The SY-Z and SY-D report do not show the informational message RQE00837

in batch mode equivalent to online message RQ837I.

Example:

Online - RQ837I: THIS OPTION HAS BEEN MOVED TO THREAD TERMINATION/DYNAMIC.

Batch - RQE00999: RQE00837 ERROR HAS OCCURED BUT ERROR TEXT NOT AVAILABLE.

IMPACT:

You may get confused with error message in batch mode.

CIRCUMVENTION:

None.

Related Problem:

RCQ 1495


DESC(RQE00837 MESSAGE MISSING IN BATCH MODE FOR SY-Z/SY-D REPORTS).

++VER (Z038)

FMID (CRCQI00)

SUP ( TR85071 )

++HOLD (RO85071) SYSTEM FMID(CRCQI00)


COMMENT (

+----------------------------------------------------------------------+

| CA RC/Query for DB2 for z/OS Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************






).





PP023E: INTERNAL ERROR IN PZA#STK1


When using CA Plan Analyzer for DB2 for z/OS (PPA) to view the PPA SQL

Statement Report, the following message may be displayed:

PP023E: Internal error in PZA#STK1. RC=32, Reason= , Reason2=8

This message indicates a problem retrieving SQL statement text from the

DB2 catalog, which could prevent further PPA functionality for the user.

SYMPTOMS:

Message PP023E, accompanied by CSECT name and return codes.

IMPACT:

User is prevented from viewing the SQL statement text for the selected

criteria.

CIRCUMVENTION:

None.


CA Plan Analyzer for DB2 for z/OS Release 17.0

CA Plan Analyzer for DB2 for z/OS Version 18.0


PRODUCT OPENED PROBLEM

Related Problem:

PPADB2 930


DESC(PP023E: INTERNAL ERROR IN PZA#STK1).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75313 RO84185 )

SUP ( TR85092 )





ADDITIONAL ERROR LOGIC WHEN READING PRODUCT PARMLIB MEMBERS


Additional internal diagnostics are needed when reading the

CA Database Management Solutions for DB2 for z/OS product parmlib

members in order to diagnose a rare condition where a CHECK call

abends.

This PTF does not solve the underlying problem, but will provide

additional information in a generated SYSMDUMP that will assist

in diagnosing the problem.

SYMPTOMS:

S001 abends when reading product parmlib members. This can also

occur when an Xmanager performs a Health Check.

IMPACT:

The process reading the parmlib fails.

CIRCUMVENTION:

None.


CA Database Management Solution for DB2 for zOS Base Install Release 17.0

CA Database Management Solution for DB2 for zOS Base Install Version 18.0

CA Database Management Solution for DB2 for zOS Base Install Version 19.0

Related Problem:

GEN 1262


DESC(ADDITIONAL ERROR LOGIC WHEN READING PRODUCT PARMLIB MEMBERS).

++VER (Z038)

FMID (CINSI00)

SUP ( TR85107 )





BATCH CMD IN IDENTIFY PROBLEM SQL GETS PPPPBPM PANEL ERROR


In CA Plan Analyzer for DB2 for z/OS(PPA), the BATCH primary command

in Identify Problem SQL report encountered a panel error in PPPPRMB.

SYMPTOMS:

A user had generated the Identify Problem SQL report online, and

in between specifying the BATCH primary command had changed a couple

of the input header fields resulting in a field error. A combination

of the error message pointing the cursor to the field in error and

processing allowed to proceed forward to BATCH Reporting JOB Submission

panel (PPPPRMB) resulted in ISPF panel DIALOG error.

IMPACT:

Although an ISPF dialog panel error is issued, the impact is minor.

The user is able to correct the field error, before resubmitting the

BATCH command a second time.

CIRCUMVENTION:

None.


Plan Analyzer Release 17.0

Plan Analyzer Version 18.0

Plan Analyzer Version 19.0

Related Problem:

PPADB2 931


DESC(BATCH CMD IN IDENTIFY PROBLEM SQL GETS PPPPBPM PANEL ERROR).

++VER (Z038)

FMID (CPPAI00)

PRE ( RO73796 RO74983 RO75760 )

SUP ( TR85115 )





S0C1 ABEND IN UTLGLIOE OFFSET +19C


Executing CA Rapid Reorg for DB2 for z/OS to reorg an object.

When the number of SYSREC or SYSUT1 DDNAMES exceeds the defaulted

or specified UNLOAD-TASKS or MAXTASK values, Rapid Reorg may abend

in UTAGLIOE.

SYMPTOMS:

Reorg may encounter an abend in UTLGLIOE:

IEA995I SYMPTOM DUMP OUTPUT 213

SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001

TIME=10.01.51 SEQ=61232 CPU=0000 ASID=026C

PSW AT TIME OF ERROR 078C2000 B40B119C ILC 2 INTC 01

ACTIVE LOAD MODULE ADDRESS=340B1000 OFFSET=0000019C

NAME=UTLGLIOE

DATA AT PSW 340B1196 - 301807FE 00DEAD1E C995A581

PRR3001I - Tablespace DATABASE.TSNAME.0017 Opened for Unload - UL1

PRR0072E - CSECT: RRA$UL1 Abended, Code: X'840C1000' - ESTAE Intercepted

PRR0091E - Tablespace Database.TSSPACE.0021

Application Abended when UNLOADing the Tablespace

Task ECB: X'000C1000' Return Code: X'0000000C'

Detected in module RRA$ULD

PRR0028I - RAPID REORG Processing Ended - Return Code: 008

IMPACT:

Rapid Reorg abends. No recovery is needed.

CIRCUMVENTION:

Increase the value for UNLOAD-TASKS to be at least the number of

SYSRECs specified in JCL.


CA Rapid Reorg for DB2 for z/OS Version 18.0


Related Problem:

PRR 1265


DESC(S0C1 ABEND IN UTLGLIOE OFFSET +19C).

++VER (Z038)

FMID (CPRRI00)

PRE ( RO79588 )

SUP ( TR85120 )





S438 ABEND IN UTLGLRI2


Fast Load for DB2 for z/OS part level Load replace can receive an

S438 Abend when processing an index.

SYMPTOMS:

Fast Load can abend with the following:

PUT2101E - CSECT UTAGLIX2 Abended - X'84438000' ESTAE Intercepted

**SDWA**3A8E8070 3A8E84A4 84438000 FF040010 00000000 ................

.....

PUT2101E - CSECT UTAGLRI2 Abended - X'84438000' ESTAE Intercepted

PFL3003E - Index task processing abended

PFL3004E - Task ECB X'00438000' Return Code: X'00000010'

PFL0208E - Datasets did not load successfully -

RECOVERY required before RESTART

IMPACT:

The load fails.

CIRCUMVENTION:

Use a GLOBAL RESUME YES load instead of partition level load.




Related Problem:

PFL 1162


DESC(S438 ABEND IN UTLGLRI2).

++VER (Z038)

FMID (CPFLI00)


RO79586 RO82027 RO82275 RO83928 )

SUP ( RO75738 TR75738 TR85171 )


++HOLD (RO85171) SYSTEM FMID(CPFLI00)


COMMENT (

+----------------------------------------------------------------------+

| CA Fast Load for DB2 for z/OS Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************






).





S438 ABEND IN UTLGLRI2


Fast Load for DB2 for z/OS part level Load replace can receive an

S438 Abend when processing an index.

SYMPTOMS:

Fast Load can abend with the following:

PUT2101E - CSECT UTAGLIX2 Abended - X'84438000' ESTAE Intercepted

**SDWA**3A8E8070 3A8E84A4 84438000 FF040010 00000000 ................

.....

PUT2101E - CSECT UTAGLRI2 Abended - X'84438000' ESTAE Intercepted

PFL3003E - Index task processing abended

PFL3004E - Task ECB X'00438000' Return Code: X'00000010'

PFL0208E - Datasets did not load successfully -

RECOVERY required before RESTART

IMPACT:

The load fails.

CIRCUMVENTION:

Use a GLOBAL RESUME YES load instead of partition level load.




Related Problem:

PFL 1162


DESC(S438 ABEND IN UTLGLRI2).

++VER (Z038)

FMID (CPUTI00)

PRE ( RO75162 RO79897 RO82144 RO82277 RO83930 )

SUP ( TR85172 )


++HOLD (RO85172) SYSTEM FMID(CPUTI00)


COMMENT (

+----------------------------------------------------------------------+

| CA Utilities Common For DB2 Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************






).





IDB2ACCT DB2-CPU VALUE INCORRECT


The CA Insight Database Performance Monitor for DB2 for z/OS (IDB2) may

report an incorrect value for the IDB2ACCT DB2-CPU field. IDB2 uses the class

1 time stored procedure CPU time instead of class 2 in the field value

computation.

SYMPTOMS:

The DB2 CPU field on the Thread IDB2 Accounting Overview screen shows a

higher time value than the Total DB2 CPU field on the Active Threads Detail

screen.

IMPACT:

The DB2 CPU time is reported incorrectly on the IDB2 accounting screens.

CIRCUMVENTION:

None.






Related Problem:

IDB2 1896


DESC(IDB2ACCT DB2-CPU VALUE INCORRECT).

++VER (Z038)

FMID (CIDBI00)


RO78006 RO78828 RO78961 RO82325 RO83711 )

SUP ( RO75810 RO79219 RO81583 RO83466 TR75810 TR79219

TR81583 TR83466 TR85182 )





PTATOKE SQLDA C AND C++ SUPPORT


When using products that use the SQL Tokenizer a S0C4 could occur when

C HOSTLANG statements that had pointer host variables were being

proccessed.

SYMPTOMS:

S0C4

IMPACT:

Only affects the small subset of C HOSTLANG SQL statements that use

pointers in host variables.

CIRCUMVENTION:

N/A




Related Problem:

PPADB2 893


DESC(PTATOKE SQLDA C AND C++ SUPPORT).

++VER (Z038)

FMID (CINSI00)


SUP ( RO74576 RO77247 TR74576 TR76604 TR77247 TR85200 )





DA CRITICAL EXTENDED CREATES NON RECOVERABLE ICS FOR PFR


CA Online Rapid Reorg for DB2 for Z/OS (POR), using the

EXTENDED-TSREORG YES option produces inline image copies

that CA Fast Recover for DB2 for Z/OS (PFR) cannot process

during recovery.

The circumstances are as follows:

1) EXTENDED-TSREORG YES is specified or

EXTENDED-TSREORG NO is specified and the RIDDSP keyword is not used.

2) PQC BEFORE or AFTER is specified.

3) Tablespace is a 4-byte RID object.

SYMPTOMS:

PRR online completes normally. There is no indication of a problem.

PFR will restore less or in some cases no data. The tablespace

can be empty after recovery.

IMPACT:

A data recovery can result in DATA lost.

CIRCUMVENTION:

Specify EXTENDED-TSREORG NO using RID datasets. Do not specify

the RIDDSP option.

PRODUCT(S) AFFECTED: POR Release 18

Release 19

Related Problem:

POR 542


DESC(DA CRITICAL EXTENDED CREATES NON RECOVERABLE ICS FOR PFR).

++VER (Z038)

FMID (CPRRI00)


RO81515 RO82143 RO82276 RO83344 RO83976 )

SUP ( TR84897 TR84962 TR85222 )






DA CRITICAL EXTENDED CREATES NON RECOVERABLE ICS FOR PFR


CA Online Rapid Reorg for DB2 for Z/OS (POR), using the

EXTENDED-TSREORG YES option produces inline image copies

that CA Fast Recover for DB2 for Z/OS (PFR) cannot process

during recovery.


1) EXTENDED-TSREORG YES is specified or

EXTENDED-TSREORG NO is specified and the RIDDSP keyword is not used.

2) PQC BEFORE or AFTER is specified.

3) Tablespace is a 4-byte RID object.

SYMPTOMS:

PRR online completes normally. There is no indication of a problem.

PFR will restore less or in some cases no data. The tablespace

can be empty after recovery.

IMPACT:

A data recovery can result in DATA lost.

CIRCUMVENTION:

Specify EXTENDED-TSREORG NO using RID datasets. Do not specify

the RIDDSP option.

PRODUCT(S) AFFECTED: POR Release 18

Release 19

Related Problem:

POR 542


DESC(DA CRITICAL EXTENDED CREATES NON RECOVERABLE ICS FOR PFR).

++VER (Z038)

FMID (CPUTI00)

SUP ( TR85223 )

++IF FMID(CPRRI00) REQ(RO85222 ) .





APPLY RO80595 FAILS WITHOUT DETECTOR


Applying fix RO80595 to CA Database Management for DB2 for z/OS fails

if CA Detector for DB2 for z/OS (PDT) is not installed.

SYMPTOMS:

SMP apply fails with error message GIM67301W for the following modules.

DT$DXRCC

DT$EXVCC

DT$VALCC

DT$VUNCC

IMPACT:

Users are unable to apply maintenance to the INS component of CA

Database Management for DB2 for z/OS.

CIRCUMVENTION:

None

Related Problem:

INS 406


DESC(APPLY RO80595 FAILS WITHOUT DETECTOR).

++VER (Z038)

FMID (CINSI00)

PRE ( RO83358 )

SUP ( AR83358 TR85226 )

VERSION(CPDTI00).

VERSION(CPDTI00).

VERSION(CPDTI00).

VERSION(CPDTI00).





INCORRECT ENQ RNAME OF D


CA Utilities for DB2 for z/OS will use an incorrect RNAME value when

serializing DB2 Catalog Access. The RNAME value is --D-- when it

should be --DB2 CATALOG ACCESS SERIALIZING FOR ssid-- where ssid

is the Local DB2 subsystem name.

SYMPTOMS:

When conflicts are present the DISPLAY GRS,C command shows:

MIM1181I CONFLICTS DISPLAY

S=SYS CADB2 D

IMPACT:

The RNAME does not have include the proper DB2 system so

the JOB may be prevented from executing when no lock is necessary.

CIRCUMVENTION:

None.


Utilities Common Release 17.0

Utilities Common Version 18.0

Utilities Common Version 19.0

Related Problem:

PUT 749


DESC(INCORRECT ENQ RNAME OF D).

++VER (Z038)

FMID (CINSI00)

PRE ( RO81827 )

SUP ( TR85228 )





INVALID DATABASE NAME ON SQL TRACE DISPLAY WITH DB2 11


On the CA Detector for DB2 for z/OS (PDT) "DETECTOR SQL Trace Locks

Acquired Display," a DBASE value (a database name) may be blanks or

an invalid value. This problem can occur only with DB2 11.

SYMPTOMS:

On the DETECTOR SQL Trace Locks Acquired Display, a DBASE value (a

database name) is blanks or an invalid value.

IMPACT:

Determining the correct database name for a lock may be difficult

or impossible.

CIRCUMVENTION:

None.




Related Problem:

PDT 1338


DESC(INVALID DATABASE NAME ON SQL TRACE DISPLAY WITH DB2 11).

++VER (Z038)

FMID (CPDTI00)

SUP ( TR85245 TR85247 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************






Important!






).





GRAPHIHC/VARGRAPHIC DATA TRUNCATION IN FORM MODE


CA RC/Update for DB2 for z/OS, RC/Browse does not display GRAPHIC/VARGRAPHIC

data correctly in FORM mode.

SYMPTOMS:

Data in GRAPHICH/VARGRAPHIC columns might be truncated one character when

browsing or editing a table in FORM mode.

IMPACT:

Display of GRAPHIC/VARGRAPHIC column data is incorrect.

CIRCUMVENTION:

You have to switch to column mode view.

Related Problem:

RCU 1055


DESC(GRAPHIHC/VARGRAPHIC DATA TRUNCATION IN FORM MODE).

++VER (Z038)

FMID (CRCUI00)

PRE ( RO82562 RO84506 )

SUP ( TR85252 )





DC-GROUP SYSPARM NOT OVERRIDDEN BY LAST OCCURRENCE IN FILE


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2)

data collector initialization will use the value in the FIRST

occurrence of the DC-GROUP= system parameter. This is inconsistent

with Sysview/DB2 SYSPARM handling (last occurrence of a SYSPARM is always

used).

The last occurrence of DC-GROUP will now be used.

SYMPTOMS:

If DC-GROUP is coded more than once in the SYSPARMS deck, the last

occurrence is ignored.

IMPACT:

Processing is inconsistent with standard SYSPARM handling rules.

CIRCUMVENTION:

Only code the DC-GROUP= parameter once.




Related Problem:

IDB2 1894


DESC(DC-GROUP SYSPARM NOT OVERRIDDEN BY LAST OCCURRENCE IN FILE).

++VER (Z038)

FMID (CIDBI00)


RO78511 RO78828 RO78961 RO82325 )

SUP ( RO81339 TR81339 TR85076 TR85259 )



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+

|SEQUENCE | Before Restart |

+----------+-----------------------------------------------------------+

|PURPOSE |Ensure that you will be using the correct DC-GROUP Sysparm.|

+----------+-----------------------------------------------------------+

|USERS | |

|AFFECTED | |

| |Sysview/DB2 data collector address spaces. |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | |

|REQUIRED | |

| |Sysview/DB2 customization. |

+----------+-----------------------------------------------------------+

|ACCESS | |

|REQUIRED | |

| |Update access to the CA-Sysview/DB2 Sysparm file. |

+----------+-----------------------------------------------------------+

**************************


**************************

Review your Sysview/DB2 Sysparms. If DC-GROUP is coded more than

once, the LAST occurrence of it will be used. If this is NOT what

you want, remove the duplicate entries.

).





VARIABLE FORMAT DUMMY ROWID COLUMN FAILS TO LOAD


CA Fast Load for DB2 for z/OS (PFL) can issue an error message when

the following conditions are met:

- The table contains a ROWID column

- The ROWID column is loaded as a DUMMY column

- The positional parameter for the column is an *

If these conditions are met, PFL will issue an error message and stop

processing.

SYMPTOMS:

PFL will issue an error message and stop processing. The error message

is:

PFL0713E - Column DUMMY_ROWID_00001 is a dummy column that requires

definition.

IMPACT:

Error message PFL0713E will be issued and the product will stop

processing.

CIRCUMVENTION:

Alter the column definition on the LOAD control card to be a

VARCHAR type. The DUMMY processing will work correctly and PFL will

complete processing normally.




Related Problem:

PFL 1155


DESC(VARIABLE FORMAT DUMMY ROWID COLUMN FAILS TO LOAD).

++VER (Z038)

FMID (CPFLI00)

PRE ( RO75158 RO76002 RO82275 RO83928 )

SUP ( RO77543 TR77543 TR84255 TR85263 )





COPY USER PROFILE DURING PRFCNVRT SQL -803


CA Report Facility (BIPRF) Running the conversion utility to copy the user

profile with the DUPLICATE(SKIP) parameter set, an SQL -803 is issued. This

occurs when converting from PRF release 15.0 and earlier.

SYMPTOMS:

When converting user profile with assigned group profile the conversion may

end with SQL error -803.

IMPACT:

The PRF conversion is not complete and PRF might not be useable.

CIRCUMVENTION:

None.


Report Facility Release 17.0

Report Facility Version 18.0


Related Problem:

BIPRF 591


DESC(COPY USER PROFILE DURING PRFCNVRT SQL -803).

++VER (Z038)

FMID (CPRFI00)

PRE ( RO75311 )

SUP ( TR85287 )





ZLB0002E DICTIONARY SEQUENTIAL ORDER REBUILD INDEX(ALL)


CA Fast Recover for DB2 for z/OS (PFR) can end with RC=8 when

processing multiple indexes with a REBUILD INDEX or a RECOVER

TABLESPACE with concurrent REBUILD INDEX on a compressed tablespace

SYMPTOMS:

PFR step ends with RC=8.

PTIMSGS shows message:

ZLB0002E DICTIONARY PAGES MUST BE IN SEQUENTIAL ORDER

The following error may also occur and is accompanied by another internal

abend S13E:

PUT2101E - CSECT UTAGLIX2 Abended - X'0013E000' ESTAE Intercepted

IMPACT:

The object is not recovered/rebuilt correctly and is not usable.

CIRCUMVENTION:

Split the REBUILD of multiple indexes in different REBUILD Index steps.

Each step should process only one index.


Utility General Recovery and PFR PMM PQC PFC Version 18.0.0B

Utility General Recovery and PFR PMM PQC PFC Version 19.0.0B

Related Problem:

PFR 951


DESC(ZLB0002E DICTIONARY SEQUENTIAL ORDER REBUILD INDEX(ALL)).

++VER (Z038)

FMID (CUGRI00)


RO79590 RO82145 RO82278 )

SUP ( RO73769 TR73769 TR85294 )





XNET ABEND S0C3 PXNMGXNT IXNTACAG WITH OFA SCALABILITY


Xnet PTFs that introduced OFA scalability (r18 RO84333 and

r19 RO83861) are marked in error. When these PTFs are applied and

Xnet is used in a configuration without CA Unified Facility

Application Server or CA Chorus the IXNTACAG (create Agent) routine

incurs ABEND S0C3 attempting to access the Xnet Execution Space

component.

This fixing PTF also addresses an unreported ABEND S0C3 occurrence

when the XES command is issued to an Xnet STC that does not have

the XES component activated.

SYMPTOMS:

The Xnet STC incurs an ABEND S0C3 when an agent STC issues the

AGENT-UP request (for example, when an Insight Data Collector STC

signals AGENT_UP).

The Xnet STC incurs an ABEND S0C3 when the XES command is issued

and the XES component is not active (the XES startup parameter

was not specified in the PXNPARM parameter member used by Xnet).

IMPACT:

The AGENT_UP indication from the agent STC is not processed due to

the ABEND S0C3 and communication with the agent is not possible.

CIRCUMVENTION:

Adding the XES parameter to the PXNPARM parameter member used by

Xnet will activate the XES component and prevent most occurrences

of the ABEND S0C3. There is a "timing" condition that may result

in ABEND S0C3 during AGENT_UP processing even when the XES

component has been activated. In this case the Xnet STC and the

agent STC should be stopped. The Xnet STC should be restarted.

After the Xnet STC is completely initialized the agent STC

should be restarted.


CA XNET Communications Server For DB2 Version 18.0

CA XNET Communications Server For DB2 Version 19.0

Related Problem:

PXN 75


DESC(XNET ABEND S0C3 PXNMGXNT IXNTACAG WITH OFA SCALABILITY).

++VER (Z038)

FMID (CPXNI00)

PRE ( RO84333 )

SUP ( AR84333 TR85331 )

++HOLD (RO85331) SYSTEM FMID(CPXNI00)


COMMENT (

+----------------------------------------------------------------------+

| CA XNET Communications Server For DB2 Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|PURPOSE | This change resolves PE PTF RO84333. |

+----------+-----------------------------------------------------------+

|USERS | All Xnet users. |

|AFFECTED | |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | Xnet operations. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS | Authority to stop and start the Xnet STC. |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************



Release Service Details* STEPS TO PERFORM *

**************************

1. Apply this PTF to resolve problems with PE PTF RO84333 and its

companion PTF RO84332.

Follow all HOLDDATA instructions for PTFs RO84332 and RO84333.

).





SQLCODE -303 WHEN USING UTILITY OPTION STATS -> 'S'


When using CA RC/Migrator for DB2 for z/OS (RCM) to analyze a strategy

the analysis will end with SQLCODE -303 if the following conditions are true:

1) The strategy includes partitioned index.

2) The utility option STATS is set to 'S' during analysis.

3) The subsystem is V8 or V10(CM8) or V9(CM).

SYMPTOMS:

RMA199E PROGRAM RMA I2 RECEIVED THE FOLLOWING SQL ERROR:

DSNT408I SQLCODE = -303, ERROR: A VALUE CANNOT BE ASSIGNED TO OUTPUT

HOST VARIABLE NUMBER 13 BECAUSE THE DATA TYPES ARE NOT

COMPARABLE

IMPACT:

The analysis will end without generating any DDL.

CIRCUMVENTION:

None.


CA RC/Migrator for DB2 for z/OS Version 18.0


Related Problem:

RCM 2739


DESC(SQLCODE -303 WHEN USING UTILITY OPTION STATS -> 'S').

++VER (Z038)

FMID (CINSI00)

PRE ( RO74744 RO75329 RO83397 )

SUP ( TR85332 )



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************




).





RU678E ERROR ON BROWSE OF SYSTRIGGERS


In CA RC/Update for DB2 for z/OS (RCU), While browsing a table in SEARCHED

mode with LOB, XML or DECFLOAT columns , browsing of the data ends with a

RU678E error message.

SYMPTOMS:

While browsing a table with LOB, XML or DECFLOAT columns and when the table

has no primary key defined, a RU678E message will occur.

Example:

When browsing e.g.table SYSTRIGGERS or SYSVIEWS it fails with

following error

RU678E RC/Edit can't edit or browse the current table.

IMPACT:

You are not able to browse a table having LOB/XML/DECFLOAT columns.

CIRCUMVENTION:

Change the RC/EDIT Profile to have: Default method for applying updates ==> P

Related Problem:

RCU 1056


DESC(RU678E ERROR ON BROWSE OF SYSTRIGGERS).

++VER (Z038)

FMID (CRCUI00)

PRE ( RO75337 RO82562 RO83334 RO83638 )

SUP ( TR85342 )





BROKEN PAGE AFTER PFL ON PARTITION V11 BIGTAIL


When CA Fast Load for DB2 for z/OS (PFL) loads a partitioned object with

extended RBA values in DB2 11, it provides an incorrect value in the

FOSMNENT space map page field. FOSMNENT indicates the maximum number of

pages allowed per space map. If you subsequently try to copy the object with

an IBM COPY job, or with a CA Quick Copy for DB2 for z/OS (PQC) job that

specifies SHRLEVEL REFERENCE and AUDIT 1 or 2, the job will fail with a

broken page message.

SYMPTOMS:

IBM COPY jobs fail with the following message:

DSNU441I -DTTA 223 11:28:14.89 DSNUBASA - BROKEN PAGE FOUND

DBNAME = DBname

TSNAME = TSname

DSNUM = DSnum

PAGE = page number

ERRORCODE = X'0CA8'

PQC jobs that specify SHRLEVEL REFERENCE with AUDIT 1 or 2 fail with the

following messages:

PUT0150E - Error(s) found for Tablespace DBNAME.TSNAME Partition 1

PUT0151E - Error(s) found for page 00000001

PUT0170E - The number of SPACEMAP entries is invalid

PUT0152E - Invalid data: 00002A28

PQC0072E ERROR ENCOUNTERED FROM AUDIT INIT CALL, RC = 0000

PQC0192E INTERNAL RC 16 AT LOCATION 0160

IMPACT:

You cannot copy the object with IBM COPY or with a PQC job that specifies

SHRLEVEL REFERENCE with AUDIT 1 or 2.

CIRCUMVENTION:

Run Reorg and then rerun IBM image copy.





Related Problem:

PFL 1153


DESC(BROKEN PAGE AFTER PFL ON PARTITION V11 BIGTAIL).

++VER (Z038)

FMID (CPFLI00)

PRE ( RO75158 RO77232 RO82275 RO83928 )

SUP ( RO77538 RO79476 TR77538 TR79476 TR84218 TR85385 )






BROKEN PAGE AFTER PFL ON PARTITION V11 BIGTAIL


When CA Fast Load for DB2 for z/OS (PFL) loads a partitioned object with

extended RBA values in DB2 11, it provides an incorrect value in the


pages allowed per space map. If you subsequently try to copy the object with

an IBM COPY job, or with a CA Quick Copy for DB2 for z/OS (PQC) job that

specifies SHRLEVEL REFERENCE and AUDIT 1 or 2, the job will fail with a

broken page message.

SYMPTOMS:



DBNAME = DBname

TSNAME = TSname

DSNUM = DSnum

PAGE = page number

ERRORCODE = X'0CA8'


following messages:







IMPACT:

You cannot copy the object with IBM COPY or with a PQC job that specifies

SHRLEVEL REFERENCE with AUDIT 1 or 2.

CIRCUMVENTION:

Run Reorg and then rerun IBM image copy.





Related Problem:

PFL 1153


DESC(BROKEN PAGE AFTER PFL ON PARTITION V11 BIGTAIL).

++VER (Z038)

FMID (CPUTI00)

SUP ( AC85453 TR85386 )






ONLINE HELP MISSING FOR INTERVAL OPTION


CA Report Facility (BIPRF) online HELP is missing description of the Commit

Interval (INTERVAL) parameter on the Post Install screens for the PRF Table

Conversion Utility (PRFCNVRT) task.

SYMPTOMS:

There is no online help for the Commit Interval parameter in Post Install

screens.

IMPACT:

User cannot easily find the description of the Commit Interval parameter.

CIRCUMVENTION:

None


Report Facility Release 17.0



Related Problem:

BIPRF 612


DESC(ONLINE HELP MISSING FOR INTERVAL OPTION).

++VER (Z038)

FMID (CPRFI00)

PRE ( RO75249 )

SUP ( TR85350 TR85391 )





ABEND S0C4 NGRABPC0 AMXSSXC0 AFTER EDB CONTROL BLOCK CHANGE


CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) may

encounter an S0C4 ABEND in the data collector if the Data Base

exceptions for high space used or high number extents is active. An

ABEND S0C4 may also occur when viewing the Open Data Sets request

(Option 1.6.2).

SYMPTOMS:

ABEND S0C4 in data collector module NGRABPC9/0/1 or AMXSSXC9/0/1.

Alternate symptoms may be missing or erroneous exceptions raised

for the Data Base exceptions (High Space Used or High number of Extents), or

invalid data displayed when viewing the DATASETS or EXTENTS requests.

IMPACT:

The status of DB2 data sets is not accurately reported. Exceptions may be

not raised, or erroneously raised.

CIRCUMVENTION:

None.





Related Problem:

IDB2 1876


DESC(ABEND S0C4 NGRABPC0 AMXSSXC0 AFTER EDB CONTROL BLOCK CHANGE).

++VER (Z038)

FMID (CIDBI00)


RO74677 RO74826 RO74879 RO75439 RO76303 RO76570

RO77226 RO77678 RO78738 RO78961 RO81335 RO81582

RO81947 RO82229 RO82325 RO83061 RO83711 RO84357

RO84503 )


TR85395 )





RCM0179W WHEN LRSN/RBA UPDATE ALL PAGES IN SAME SUBSYSTEM


In CA RC/Migrator for DB2 for z/OS (RCM), while executing an RC/Merger (RMM)

analysis on a strategy with the MOVE option selected within the same

subsystem, RMM resets the RBA/LRSN values on all the headers and data pages.

SYMPTOMS:

While executing the analysis, the following message is displayed:

RCM0179W - THE SOURCE SUBSYSTEM RBA/LRSN IS GREATER THAN THAT OF THE

TARGET SUBSYSTEM. RC/MERGER WILL NEED TO RESET

THE LAST UPDATED RBA/LRSN ON EVERY PAGE.

IMPACT:

As the pages of the target are updated, the performance of RC/Merger is

impacted.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED: RC/Migrator Release 18.0


Related Problem:

RMM 204


DESC(RCM0179W WHEN LRSN/RBA UPDATE ALL PAGES IN SAME SUBSYSTEM).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75319 RO83587 RO84941 RO85050 )

SUP ( RO84719 TR84678 TR84719 TR85397 )





SYSTEM_TIME COLUMN ATTRIBUTES MISSING FROM ALTER TABLE DDL


CA RC/Migrator for DB2 for z/OS (RCM) generates alter table DDL without

key attributes 'GENERATED ALWAYS', 'ROW BEGIN', 'ROW END' if the newly added

column is a SYSTEM_TIME column and the target subsystem supports DB2 V11.

SYMPTOMS:

'NOT NULL GENERATED ALWAYS AS ROW BEGIN' is missing from the follwoing

alter table DDL:

ALTER TABLE BDBS.LANT2XX

ADD SYS_START TIMESTAMP ( 12 )

;

IMPACT:

Customer will not be able to add a SYSTEM_TIME column.

CIRCUMVENTION:




Related Problem:

RCM 2741


DESC(SYSTEM_TIME COLUMN ATTRIBUTES MISSING FROM ALTER TABLE DDL).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75754 )

SUP ( RO80620 TR80620 TR85418 )





DB2 00C20110 ERROR AFTER PBG TABLESPACE REORG


CA Rapid Reorg for DB2 for z/OS (PRR) after reorganizing a partition by

growth tablespace, can cause subsequent

DB2 00C20110 errors when processing DB2 utilities.


1) DATA-AVAILABLE NORMAL has been specified.

2) The tablespace being reorged is partitioned by growth.

3) The tablespace is defined with a DSSIZE specification.

4) PIECESIZE has a value of zero in the DB2 catalog for a non

partitioned index defined to the tablespace.

5) The index grows beyond the first dataset.

SYMPTOMS:

The reorg completes normally however,

A subsequent DB utility or DML returns the following ERROR code

DSNU590I !DB2G 251 12:17:32.54 DSNUKDRN - RESOURCE NOT AVAILABLE,

REASON=X'00C20110', ON DBname.IXname PROHIBITS PROCESSING

IMPACT:

The reorg builds the index incorrectly.

CIRCUMVENTION:

NONE.

PRODUCT(S) AFFECTED: PRR 16.0

PRR 17.0

PRR 18.0

PRR 19.0

Related Problem:

PRR 1262


DESC(DB2 00C20110 ERROR AFTER PBG TABLESPACE REORG).

++VER (Z038)

FMID (CPRRI00)


RO82276 RO83929 )

SUP ( RO75741 RO83539 TR74106 TR75741 TR76800 TR83539

TR85435 )





INV RETCDE FROM -DISP DB DURING STRATEGY ANALYSIS


CA Recovery Analyzer for DB2 for z/OS (PRA) displays error message

"Inv Retcde from -DISP DB" in "Check TS/IX status" phase during strategy

analysis for index-space. This occurs if a database has been dropped but

an object that was within that database still has an entry in the strategy.

Analysis process stops.

SYMPTOMS:

PRA error report (PRAERRPT) displays:

Phase: Validate Spaces Exists

Warning IX is-name db-name Space not found in Catlg

Phase: Check TS/IX status

Sev Err IX is-name 0000 db-name Inv Retcde from -DISP DB

for missing object, followed by error message:

RAE00418: OVERRIDE_ERRORS parmlib setting of Y will be ignored:

The JCL generated may be unexecutable and therefore

will not be created

Analysis process stops.

IMPACT:

Recovery analysis process stops.

CIRCUMVENTION:

Remove dropped objects from strategy.


Recovery Analyzer Release 17.0

Recovery Analyzer Version 18.0

Recovery Analyzer Version 19.0

Related Problem:

PRA 852


DESC(INV RETCDE FROM -DISP DB DURING STRATEGY ANALYSIS).

++VER (Z038)

FMID (CPRAI00)

SUP ( RO83784 RO84676 TR83784 TR84676 TR85441 )





PARTIAL ITE$STCK CAUSES DATA LOSS


Partial STCK value collected by CA Detector for DB2 for z/OS (PDT)

may cause missing or incorrect SQL statement statistics in the CA SYSVIEW

Performance Management Option for DB2 for z/OS (IDB2) accounting record.

These statistics are collected when the PDTSQL is specified in the

HIST-ACCT-DETAIL SYSPARM parameter.

SYMPTOMS:

Missing or incorrect SQL statement executions on the THRDIDSQ

(thread detail "SYSVDB2 Acct Rec SQL Summary"), HTUIDSQL (thread history

summary "SYSVDB2 Acct Rec SQL History Summary"), or HTIDBSQL (thread

history detail "SYSVDB2 Acct Rec SQL History") IQL displays.

IMPACT:

All CA SYSVIEW Performance Management Option for DB2 for z/OS users who

have the PDTSQL option included in the HIST-ACCT-DETAIL SYSPARM parameter.

CIRCUMVENTION:

None.


CA Detector for DB2 for z/OS Version 18.0


Related Problem:

PDT 1339


DESC(PARTIAL ITE$STCK CAUSES DATA LOSS).

++VER (Z038)

FMID (CPDTI00)


RO77520 RO78101 RO78198 RO78446 RO78514 RO78682

RO79431 RO79574 RO79877 RO79934 RO79949 RO80038

RO80194 RO80397 RO80869 RO80899 RO81146 RO81196

RO81417 RO82518 RO82587 RO82974 RO83695 RO84200 )

SUP ( RO73491 RO73552 RO74003 RO74580 RO83776 RO84898

TR73491 TR73552 TR74003 TR74580 TR74996 TR75133

TR75226 TR75241 TR75379 TR75436 TR75468 TR75494

TR75533 TR78973 TR79455 TR80527 TR80717 TR83776

TR84898 TR85468 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************




Release Service Details1. Stop product collections.




Important!






).





TRUNCATED VPSIZE DATA IN BP-DS REPORT


In CA RC/Query for DB2 for z/OS (RCQ), BP-DS report shows a truncated value

for the VPSIZE column.

SYMPTOMS:

The BP-DS report displays only 6 character data under VPSIZE report column.

even when buffer pool size is greater than 6 characters.

Example:

CMD NAME ID USE VPSIZE HPSIZE VPSEQT VPPSEQT

________ BP3 38 0 000000 N/A 80 50

________ BP4 39 0 30 N/A 80 50

IMPACT:

You cannot not be able to determine the VPSIZE value from the BP-DS report.

CIRCUMVENTION:

None.

Related Problem:

RCQ 1497


DESC(TRUNCATED VPSIZE DATA IN BP-DS REPORT).

++VER (Z038)

FMID (CRCQI00)

PRE ( RO75330 )

SUP ( TR85474 )





LBIND/LREBIND COMMANDS NOT SUPPORTED IN DB2 V10 CM8 MODE


In CA RC/Query for DB2 for z/OS (RCQ), LBIND/LREBIND commands are not

supported in DB2 v10 CM8 mode.

SYMPTOMS:

In DB2 v10 CM8 mode, issuing LBIND/LREBIND commands on packages returns an

error:-

DSNT408I SQLCODE = -206, ERROR: BUSTIMESENSITIVE IS NOT VALID IN THE

CONTEXT WHERE IT IS USED

IMPACT:

You cannot use LBIND/LREBIND commands in DB2 v10 CM8 mode.

CIRCUMVENTION:

NONE.

Related Problem:

RCQ 1498


DESC(LBIND/LREBIND COMMANDS NOT SUPPORTED IN DB2 V10 CM8 MODE).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75312 )

SUP ( RO77458 TR77458 TR85038 TR85473 TR85481 )





INACCURATE CPU TIMES/STALE ZIIP TIMES FOR DISTRIBUTED THREAD


CA Thread Termination/Dynamic ZPARM for DB2 for z/OS (PTT) reports

inaccurate INDB2 CPU times for distributed threads. In addition, the

"Thread ZIIP CPU" time value on the Thread Terminator Thread Time

Display may not be updated readily for a distributed thread in

comparison to the corresponding time values on the CA Sysview

Performance Management Option for DB2 for z/OS (IDB2) "Active Thread

Detail" and "Thread Response Time" displays. This problem occurs with

DB2 10 and above. This solution resolves the problem for DB2 11 and

above, including DB2 11 CM.

SYMPTOMS:

The INDB2_CPU time value for a distributed thread on the Thread

Terminator Active Threads Display is inaccurate.

The "INDB2 CPU" time value on the Thread Terminator Thread Time Display

for a distributed thread is inaccurate.

The thread monitor does not select the appropriate distributed threads

when a nonzero "INDB2 CPU Time" thread monitor threshold value is in use

for distributed threads.

The "Thread ZIIP CPU" time value on the Thread Terminator Thread Time

Display for a distributed thread is not updated readily in comparison to

the "DB2 zIIP Time" and "Local DB2 zIIP" time values on the IDB2 "Active

Thread Detail" and "Thread Response Time" displays respectively.

IMPACT:

The thread monitor may terminate the wrong distributed threads or fail

to terminate the right distributed threads.

Viewing the PTT displays for distributed threads may lead to incorrect

conclusions based on the reported INDB2 CPU time consumption and zIIP

CPU time consumption of the distributed threads.

CIRCUMVENTION:

To ensure that the thread monitor will select the appropriate

distributed threads, do not use a nonzero "INDB2 CPU Time" thread monitor

threshold value for distributed threads.


Thread Terminator Release 16.0



Thread Terminator Version 19.0

Related Problem:

PTT 330


DESC(INACCURATE CPU TIMES/STALE ZIIP TIMES FOR DISTRIBUTED THREAD).

++VER (Z038)

FMID (CINSI00)

PRE ( RO83304 RO83329 )

SUP ( RO74668 TR74668 TR85521 )

++IF FMID(CPDTI00) REQ(RO85522 ) .



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+






Release Service Details+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************






Important!






).





INACCURATE CPU TIMES/STALE ZIIP TIMES FOR DISTRIBUTED THREAD


CA Thread Termination/Dynamic ZPARM for DB2 for z/OS (PTT) reports

inaccurate INDB2 CPU times for distributed threads. In addition, the

"Thread ZIIP CPU" time value on the Thread Terminator Thread Time

Display may not be updated readily for a distributed thread in

comparison to the corresponding time values on the CA Sysview

Performance Management Option for DB2 for z/OS (IDB2) "Active Thread

Detail" and "Thread Response Time" displays. This problem occurs with

DB2 10 and above. This solution resolves the problem for DB2 11 and

above, including DB2 11 CM.

SYMPTOMS:

The INDB2_CPU time value for a distributed thread on the Thread

Terminator Active Threads Display is inaccurate.

The "INDB2 CPU" time value on the Thread Terminator Thread Time Display

for a distributed thread is inaccurate.

The thread monitor does not select the appropriate distributed threads

when a nonzero "INDB2 CPU Time" thread monitor threshold value is in use

for distributed threads.

The "Thread ZIIP CPU" time value on the Thread Terminator Thread Time

Display for a distributed thread is not updated readily in comparison to

the "DB2 zIIP Time" and "Local DB2 zIIP" time values on the IDB2 "Active

Thread Detail" and "Thread Response Time" displays respectively.

IMPACT:

The thread monitor may terminate the wrong distributed threads or fail

to terminate the right distributed threads.

Viewing the PTT displays for distributed threads may lead to incorrect

conclusions based on the reported INDB2 CPU time consumption and zIIP

CPU time consumption of the distributed threads.

CIRCUMVENTION:

To ensure that the thread monitor will select the appropriate

distributed threads, do not use a nonzero "INDB2 CPU Time" thread monitor

threshold value for distributed threads.





Thread Terminator Version 19.0

Related Problem:

PTT 330


DESC(INACCURATE CPU TIMES/STALE ZIIP TIMES FOR DISTRIBUTED THREAD).

++VER (Z038)

FMID (CPDTI00)

PRE ( RO77329 )

SUP ( RO73722 TR73722 TR85522 )






SPECIAL CHARACTERS ARE NOT DISPLAYED IN EDIT OR BROWSE


In CA RC/Update for DB2 for z/OS (RCU), when you browse or edit table data

that contains special characters (for example, accented vowels or currency

symbols), the special characters are not displayed properly on the screen.

SYMPTOMS:

Special characters are displayed as periods in regular display mode, or

as blanks in hex display mode.

IMPACT:

Determining the true contents of table data is difficult as it is unclear.

CIRCUMVENTION:

None.

Related Problem:

RCU 927


DESC(SPECIAL CHARACTERS ARE NOT DISPLAYED IN EDIT OR BROWSE).

++VER (Z038)

FMID (CRCUI00)

SUP ( TR85527 )





MESSAGES SCREEN IS HORIZONTALLY TRUNCATED


The CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2) User

Interface may display horizontally truncated output on certain screens. The

problem occurs when PTF RO80935, RO82325 or RO83196 has been applied.

The list of affected screens includes Messages and the DCCPU command output.

SYMPTOMS:

After having visited the Active Threads screen, navigating to the Messages

screen produces a horizontally truncated output, with only the first ~50

characters of each line visible.

IMPACT:

Poor usability of the affected screens.

CIRCUMVENTION:

Restart the UI session before accessing one of the affected screens.






Related Problem:

IDB2 1901


DESC(MESSAGES SCREEN IS HORIZONTALLY TRUNCATED).

++VER (Z038)

FMID (CIDBI00)


RO78961 RO82325 )

SUP ( AR82325 TR85526 TR85529 )





EXPLAIN FAILS WITH SQL299


IN CA Plan Analyzer Services for DB2 for z/OS (PAS)Explain fails with SQL299

when derived column names exceeds 30 characters.

SYMPTOMS:

A generated SQL statement with derived column names with more than 30

characters triggered the SQL299 internal error message:

SQL299: You have specified an ordinary long column name

with a length exceeding 30 characters.

Total length must not exceed 30 characters.

IMPACT:

Any SQL using derived column names with more than 30 characters.

CIRCUMVENTION:

Change the SQL column name to be 30 characters or less.


Plan Analyzer Services Release 18.0

Plan Analyzer Services Release 19.0

Related Problem:

PPADB2 932


DESC(EXPLAIN FAILS WITH SQL299).

++VER (Z038)

FMID (CINSI00)

PRE ( RO76119 RO76640 RO84444 )


TR79359 TR84889 TR85561 )





PRR2251E INDEX DELETE ERROR


CA Rapid Reorg for DB2 for z/OS (PRR) receives an error when performing a

standard mode, partition level reorg with DATA-AVAILABLE NORMAL on a DB2 11

subsystem.

SYMPTOMS:

Reorg fails with the following messages:

UTAIXUIN IX: L#@IP01X Updates Expected: 000000444 Keys Processed: 000000000

PRR3002I - Tablespace L#@DP01.L#@SP01.0002 Unload...........898 Rows

PRR2251E - Index PDUTL01.L#@IP01X Delete Error

PRR0174E - Strip Index Processor Abended

IMPACT:

Reorg fails to reorg the object.

CIRCUMVENTION:

Reorg the entire object not just the specific partitions.




Related Problem:

PRR 1266


DESC(PRR2251E INDEX DELETE ERROR).

++VER (Z038)

FMID (CPRRI00)


RO75161 RO76022 RO76403 RO77233 RO77346 RO78826

RO79588 RO82143 RO82276 RO83344 RO83929 )

SUP ( RO75741 RO76551 RO83539 RO85120 RO85435 TR74106

TR75741 TR76551 TR76800 TR83539 TR85120 TR85435

TR85565 )






PRR2251E INDEX DELETE ERROR


CA Rapid Reorg for DB2 for z/OS (PRR) receives an error when performing a

standard mode, partition level reorg with DATA-AVAILABLE NORMAL on a DB2 11

subsystem.

SYMPTOMS:

Reorg fails with the following messages:

UTAIXUIN IX: L#@IP01X Updates Expected: 000000444 Keys Processed: 000000000

PRR3002I - Tablespace L#@DP01.L#@SP01.0002 Unload...........898 Rows

PRR2251E - Index PDUTL01.L#@IP01X Delete Error

PRR0174E - Strip Index Processor Abended

IMPACT:

Reorg fails to reorg the object.

CIRCUMVENTION:

Reorg the entire object not just the specific partitions.




Related Problem:

PRR 1266


DESC(PRR2251E INDEX DELETE ERROR).

++VER (Z038)

FMID (CPUTI00)

PRE ( RO74446 RO82277 )

SUP ( TR85566 )

++IF FMID(CPRRI00) REQ(RO85565 ) .





INVALID OPTIONS GENERATED FOR PLAN LBIND & LREBIND

ENHANCEMENT DESCRIPTION:

In CA RC/Query for DB2 for z/OS(RCQ), LBIND and LREBIND line commands on a

plan generates invalid keywords SYSTIMESENSITIVE, BUSTIMESENSITIVE, DESCSTAT

and ARCHIVESENSITIVE.

SYMPTOMS:

SYSTIMESENSITIVE, BUSTIMESENSITIVE, DESCSTAT and ARCHIVESENSITIVE are invalid

for a PLAN LBIND and LREBIND, the following error is displayed:

BPA0016E: DB2 UTILITY APPLICATION - INCOMPLETE. RETCODE = 8

IKJ56712I INVALID KEYWORD, SYSTIMESENSITIVE(NO)

IMPACT:

You cannot LBIND or REBIND the PLAN.

CIRCUMVENTION:

Manually remove these keywords from the generated batch cards.




Related Problem:

RCQ 1489


DESC(INVALID OPTIONS GENERATED FOR PLAN LBIND & LREBIND).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75312 )


TR85569 )





S0C4 DURING ONLINE EXTENDED EXTRACT


In CA RC Extract for DB2 for z/OS(RCX), the ONLINE extract on EXTENDED

EXTRACT DEFINITION containing multiple SRCDEFS abends with a S0C4.

SYMPTOMS:

The following abend occurs when an ONLINE extraction is attempted:


IMPACT:

You cannot perform the online extraction on an EXTENDED EXTRACT DEFINITION.

CIRCUMVENTION:

BATCH extraction on the EXTENDED EXTRACT DEFINITION runs successfully.

PRODUCTS AFFECTED:

RC/X 17.0

Related Problem:

RCX 567


DESC(S0C4 DURING ONLINE EXTENDED EXTRACT).

++VER (Z038)

FMID (CRCXI00)

PRE ( RO75425 RO81440 RO82482 )

SUP ( TR85581 )





ERROR ON USING OPTION I ON XO IN COMMAND CENTER


In CA RC Extract for DB2 for z/OS(RCX), when using the 'I' option (INSERT

INTO DEFAULT TARGETS USING SQL) on an extract object through the command

center it fails with return code 99.This happens when the table being loaded

has one or more index other than the primary index defined on it.

SYMPTOMS:

The Below error message is given during the online execution:

RCX1001E: RC/EXTRACT SQL LOAD INCOMPLETE.

RETCODE = 99

IMPACT:

You cannot use the 'I' option.

CIRCUMVENTION:

None.


RC/Extract Release 17.0

RC/Extract Version 18.0


Related Problem:

RCX 569


DESC(ERROR ON USING OPTION I ON XO IN COMMAND CENTER).

++VER (Z038)

FMID (CRCXI00)

PRE ( RO82482 )

SUP ( TR85582 )





ERROR DURING SQL LOAD


In CA RC Extract for DB2 for z/OS(RCX), the SQL LOAD fails with error code

99.This happens when the table being loaded has a primary index and one or

more other index defined on it.

SYMPTOMS:

The Below error message is given during the online execution:

RCX1001E: RC/EXTRACT SQL LOAD INCOMPLETE.

RETCODE = 99

IMPACT:

You cannot perform the SQL LOAD.

CIRCUMVENTION:

Utility Load can be used.





Related Problem:

RCX 570


DESC(ERROR DURING SQL LOAD).

++VER (Z038)

FMID (CRCXI00)

SUP ( TR85583 )





U0047 FOLLOWED BY SC03 IN EXTENDED EXTRACT SQL DELETE


In CA RC/Extract for DB2 for z/OS(RCX), the SQL Delete for an EXTENDED

EXTRACT fails with U0047 error followed by SC03 abend.

SYMPTOMS:

The below abend occurs when an SQL Delete is attempted on an EXTENDED EXTRACT

IEF450I P$DBCA01 STEP1 - ABEND=SC03 U0000 REASON=00000000 401

ICE047A 1 RECORD COUNT OFF, SPECIFIED 1472 , RECEIVED 78065.

BPA0071E: CALLED PROGRAM RXL$SLEI ABENDED. ABEND CODE U0047 REASON CODE

00000000 - PROCESSING TERMINATES.

RETCODE = 20

IMPACT:

You cannot perform the SQL Delete operation for an EXTENDED EXTRACT.

CIRCUMVENTION:

None.





Related Problem:

RCX 571


DESC(U0047 FOLLOWED BY SC03 IN EXTENDED EXTRACT SQL DELETE).

++VER (Z038)

FMID (CRCXI00)

PRE ( RO75425 )

SUP ( TR85584 )





TEMPORAL TABLE DROPPED AND CREATED WHEN RENAMING A COLUMN


Customer may experience two different problems when using RC/Migrator

for DB2 for z/OS (RCM) to rename a column of a temporal table.

Problem 1: The analysis will generate DDL to drop and create the

base table if the column is defined as 'TRANSACTION START ID'

or 'ROW BEGIN' or 'ROW END'.

Problem 2: The analysis generates DDL to rename the column of the

history table without generating DDL to drop the view

if the view references the history table.

SYMPTOMS:

The generated script will have drop and create DDL for the base table.

DDL to drop the view which references the history table will be missing.

IMPACT:

The execution of the generated script will unnecessarily unload and load

base table.

The execution of the alter table DDL to rename the column of the

history table will fail.

CIRCUMVENTION:

None.



RC/Migrator Version 18.0


Related Problem:

RCM 2738


DESC(TEMPORAL TABLE DROPPED AND CREATED WHEN RENAMING A COLUMN).

++VER (Z038)

FMID (CINSI00)

PRE ( RO74132 RO75326 RO76410 RO78051 )

SUP ( RO82505 TR82505 TR85594 )





COLLECTION TERMINATES AFTER 0C4 IN DT$DII


CA Detector for DB2 for z/OS (PDT) may stop collections after receiving

0C4 abends.

SYMPTOMS:

Messages similar to the following appear in the Xmanager joblog:

PDT0185 ABEND=S0C4 MODULE=DT$DII OFFSET=0000386C DB2=111

PDT0102 DETECTOR TERM IN PROGRESS FOR DB2=DBH2 USER=CONSOLE

PDT generates a SVC dump having a title similar to the following:

CA-DETECTOR 18.0 DIAG/DUMP ABEND=S0C4 MODULE=DT$DII

OFFSET=0000386C DB2=XXXX

IMPACT:

PDT collection terminates.

CIRCUMVENTION:

None.




Related Problem:

PDT 1341


DESC(COLLECTION TERMINATES AFTER 0C4 IN DT$DII).

++VER (Z038)

FMID (CPDTI00)


RO77520 RO78101 RO78446 RO78514 RO78682 RO79431

RO79574 RO79877 RO79934 RO80038 RO80194 RO80397

RO80869 RO80899 RO81196 RO82518 RO82587 RO82974

RO83776 RO84200 RO85468 )


TR74580 TR74996 TR75133 TR75226 TR75241 TR75379

TR75436 TR75468 TR75494 TR75533 TR80527 TR80717

TR84898 TR85604 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************







Release Service Details4. Restart the Xmanager task.

Important!






).





RQ078E WITH FLDSTAT LINE COMMAND ON THE C-D REPORT


In CA RC/Query for DB2 for z/OS (RCQ), FLDSTAT line command does not work

from column detail(C-D) report.

SYMPTOMS:

Execution of the FLDSTAT line command from the C-D report ends with the

following error even though SYSCOLDIST holds the entry for the same columns.

RQ078E - COMMAND REQUESTED IS NOT VALID FOR SELECTED OBJECT

IMPACT:

You cannot use FLDSTAT command from C-D report.

CIRCUMVENTION:

None.

Related Problem:

RCQ 1490


DESC(RQ078E WITH FLDSTAT LINE COMMAND ON THE C-D REPORT).

++VER (Z038)

FMID (CINSI00)

PRE ( RO74957 RO75206 RO75312 RO82105 RO83825 )

SUP ( TR85042 TR85607 )

++IF FMID(CRCQI00) REQ(RO85608 ) .





RQ078E WITH FLDSTAT LINE COMMAND ON THE C-D REPORT


In CA RC/Query for DB2 for z/OS (RCQ), FLDSTAT line command does not work

from column detail(C-D) report.

SYMPTOMS:

Execution of the FLDSTAT line command from the C-D report ends with the

following error even though SYSCOLDIST holds the entry for the same columns.

RQ078E - COMMAND REQUESTED IS NOT VALID FOR SELECTED OBJECT

IMPACT:

You cannot use FLDSTAT command from C-D report.

CIRCUMVENTION:

None.

Related Problem:

RCQ 1490


DESC(RQ078E WITH FLDSTAT LINE COMMAND ON THE C-D REPORT).

++VER (Z038)

FMID (CRCQI00)

PRE ( RO74958 RO75207 RO85034 )

SUP ( TR85043 TR85608 )






ABEND S138 FOLLOWING ERROR IN HISTORY FILE INITIALIZATION


The CA SYSVIEW Performance Management Option for DB2 for z/OS (IDB2)

may fail during startup with an ABEND S138 if initialization of the

history task fails for any reason.

Additionally, the format of error message DBG21023E has been changed to

include a reason code:

DBG21023E ssid hh:mm:ss HISTORY: FILE histfile INVALID HISTORY FILE: reasoncd

SYMPTOMS:

CCSR010E NMSPRMVC S138 at 3CD92C9A LMOD NAINSLOG CSECT NUHSTLOM+4C9A

IEA794I SVC DUMP HAS CAPTURED: 924

DUMPID=166 REQUESTED BY JOB (IDCD11AS)

CCSR021I OWNER = CA SYSVIEW for DB2 R19.0

CCSR022I MODULE = NUHSTLOM FMID = CIDBJ00 RMID = RO85183

CCSR060I BREAKING EVENT ADDRESS: 00000000 0190097A

CCSR061I PSW: 07042001 80000000 00000000 3A84F2C6

CCSR062I ILC: 02 INTERRUPT CODE: 0D

CCSR067I COMPLETION CODE S138 REASON CODE 02470003

IMPACT:

The data collector is terminated and must be restarted.

CIRCUMVENTION:

Correct the underlying problem causing history initialization to

fail.





Related Problem:

IDB2 1905


DESC(ABEND S138 FOLLOWING ERROR IN HISTORY FILE INITIALIZATION).

++VER (Z038)

FMID (CIDBI00)


RO75472 RO77226 RO78006 RO78828 RO78961 RO82325

RO83061 RO83708 RO83711 )


TR79219 TR81583 TR83466 TR85182 TR85614 )





S0C4 S0C6 NO ACTIVE MODULE AFTER SUCCESSFUL LOAD


CA Fast Load for DB2 for z/OS (PFL) may experience an abend when it

is attempting to remove an ESTAE because of a corrupt control

block. With this solution Fast Load will detect the situation,

issue message PFL0746W and continue processing.

SYMPTOMS:

Various S0C4 and S0C6 abends may occur:

JOB05494 IEA995I SYMPTOM DUMP OUTPUT 551


TIME=17.44.44 SEQ=00310 CPU=0000 ASID=0198

PSW AT TIME OF ERROR 070C0000 F86FC5F8 ILC 2 INTC 10

NO ACTIVE MODULE FOUND

NAME=UNKNOWN

DATA AT PSW IS UNAVAILABLE AT THIS TIME



TIME=16.17.34 SEQ=00177 CPU=0000 ASID=016F



NAME=UNKNOWN


IMPACT:

Fast Load successfully completes but the job abends during cleanup.

The dynamic deallocation of datasets is not performed.

CIRCUMVENTION:

None.




Related Problem:

PFL 1163


DESC(S0C4 S0C6 NO ACTIVE MODULE AFTER SUCCESSFUL LOAD).

++VER (Z038)

FMID (CPFLI00)


RO82275 RO83928 RO85171 )

SUP ( TR85626 )




COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************



Release Service DetailsXMESSAGE components have changes as part of this maintenance.





).





S0C4 S0C6 NO ACTIVE MODULE AFTER SUCCESSFUL LOAD


CA Fast Load for DB2 for z/OS (PFL) may experience an abend when it

is attempting to remove an ESTAE because of a corrupt control

block. With this solution Fast Load will detect the situation,

issue message PFL0746W and continue processing.

SYMPTOMS:

Various S0C4 and S0C6 abends may occur:



TIME=17.44.44 SEQ=00310 CPU=0000 ASID=0198



NAME=UNKNOWN




TIME=16.17.34 SEQ=00177 CPU=0000 ASID=016F



NAME=UNKNOWN


IMPACT:

Fast Load successfully completes but the job abends during cleanup.

The dynamic deallocation of datasets is not performed.

CIRCUMVENTION:

None.




Related Problem:

PFL 1163


DESC(S0C4 S0C6 NO ACTIVE MODULE AFTER SUCCESSFUL LOAD).

++VER (Z038)

FMID (CPUTI00)

PRE ( RO82277 )

SUP ( TR85627 )






SEMICOLON MISSING IN ALTER TABLESPACE DDL TO CHANGE LOCKPART


When CA RC/Migrator for DB2 for z/OS (RCM) generates DDL to alter the

LOCKPART of a tablespace, the ending semicolon(;) is missing from the

alter DDL.

SYMPTOMS:

The alter tablespace DDL will be without the ending semicolon(;).

The execution will end with sqlcode -104.

IMPACT:

Customer will not be able to alter the LOCKPART of the tablespace.

CIRCUMVENTION:

Edit the script and add a semicolon(;) at the end of the alter tablespace

DDL before executing the script.





Related Problem:

RCM 2737


DESC(SEMICOLON MISSING IN ALTER TABLESPACE DDL TO CHANGE LOCKPART).

++VER (Z038)

FMID (CINSI00)


TR76621 TR78409 TR85634 )





OBJECT IDENTIFICATION MESSAGE PFL0747I


Identification of general tablespace and index characteristics has

increased in complexity with each release of DB2. CA Fast Load for

DB2 for z/OS will now issue message PFL0747I to display some of

these characteristics.

The following tablespace information will be displayed:

Tablespace type: Classic Segmented, Classic Partitioned, Partitioned by

Growth, or Partitioned by Range

SEGSIZE if greater than 0

Number of partitions if object is partitioned

Maximum number of partitions if applicable

Number of tables if greater than 1

The following index information will be displayed for each index:

CLUSTERED

PARTITIONED

The UNIQUERULE value of the index:

Unique, Enforce Constraint

Duplicates are allowed

Unique

Unique, primary index

Unique where not null

Unique, non-primary parent

Unique, ROWID gen-by-dflt

Unique, XML Values

Non-default values for the following attributes: COPY, PADDED, SPARSE,

COMPRESS and EXT-TYPE




Related Problem:

PFL 1164


DESC(OBJECT IDENTIFICATION MESSAGE PFL0747I).

++VER (Z038)

FMID (CPFLI00)


RO77345 RO79586 RO82027 RO82142 RO82275 RO83928

RO85023 RO85171 RO85626 )

SUP ( RO73432 TR73432 TR76799 TR85637 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************




Release Service Details**************************






).





INCORRECT DATA REPORTED FOR IFCIDS WITH REPEATING SECTIONS



may report incorrect data based on IQL declared fields when processing

an IFCID with a repeating section that has more than 256 occurrences.

SYMPTOMS:

Data reported are incorrect or incomplete.

IMPACT:

Invalid data reported.

CIRCUMVENTION:

None.






Related Problem:

IDB2 1902


DESC(INCORRECT DATA REPORTED FOR IFCIDS WITH REPEATING SECTIONS).

++VER (Z038)

FMID (CIDBI00)

PRE ( RO74677 RO74879 RO75439 RO78961 )

SUP ( RO74496 TR74496 TR85358 TR85640 )





FALSE ALTER TABLE ADD COLUMN ENTRY IN DDL REPORT OR SQL


CA Log Analyzer for DB2 for z/OS (PLA) may report false ALTER TABLE ADD

COLUMN statements even if no such activity occurred. The problem is caused by

a coincidence of several factors, so it occurs in seemingly random cases, but

always when SYSIBM.SYSCOLUMNS table gets updated. For example when a RUNSTATS

utility was run, or a COMMENT ON COLUMN sql statement was issued.

SYMPTOMS:

DDL object report contain false entries related to ALTER TABLE ADD COLUMN

statement.

IMPACT:

Generated DDL object report is inaccurate.

CIRCUMVENTION:

None.


CA Log Analyzer for DB2 for z/OS Release 19.0



Related Problem:

PLA 1203


DESC(FALSE ALTER TABLE ADD COLUMN ENTRY IN DDL REPORT OR SQL).

++VER (Z038)

FMID (CPLAI00)

PRE ( RO73663 RO74232 )

SUP ( TR85654 )





RM005E HELP PANEL DOES NOT SAY REGION SIZE BEING SMALL.


CA RC/Compare for DB2 for z/OS (RCC) may issue RM005E message when

the requested region size is too small. When the customer increases the

region size, the RM005E message may disappear. But the help panel RM005E

does not say anything about the region size.

SYMPTOMS:

RM005E help panel message does not say anything about the region size

being one of the reasons for RM005E message.

IMPACT:

Customer does not know that the region size needs to be increased.

CIRCUMVENTION:

Increase the region size.





Related Problem:

RCC 664


DESC(RM005E HELP PANEL DOES NOT SAY REGION SIZE BEING SMALL.).

++VER (Z038)

FMID (CRCMI00)

SUP ( TR85665 )





RC=16 ON COPY WHEN SHRLVL NS/R AND SSID DIFFERENT DB2 VERSIO


CA RC/Migrator for DB2 for z/OS (RCM) , when executing an RC/Merger (RMM)

copy or data only copy analysis on a partitioned object where the source

and target reside on different DB2 versions and sharelevel is set to NS/R,

the job fails with RC=16.

SYMPTOMS:

The job fails with RC=16 without displaying any error message.

IMPACT:

You cannot analyse a copy or data only copy analysis successfully.

CIRCUMVENTION:

None.





Related Problem:

RMM 202


DESC(RC=16 ON COPY WHEN SHRLVL NS/R AND SSID DIFFERENT DB2 VERSIO).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75319 RO83587 RO84941 RO85050 RO85397 )

SUP ( RO84719 TR84678 TR84719 TR85679 )





PSABATCH UNLOAD CAUSES DATASTORE COMPATIBILITY ERROR


When using the CA Subsystem Analyzer for DB2 for z/OS Batch Report and/or

Unload the job fails due with Datastore compatibility error messages.

SYMPTOMS:

Occurrence of PXM2002 followed by PSA0312, PSA0356, and PXM2001.

IMPACT:

The PSABATCH job fails with a non-zero return code and has to be restarted

CIRCUMVENTION:

None.


Subsystem Analyzer Release 16.0

Subsystem Analyzer Release 17.0

Subsystem Analyzer Version 18.0

Subsystem Analyzer Version 19.0

Related Problem:

PSA 454


DESC(PSABATCH UNLOAD CAUSES DATASTORE COMPATIBILITY ERROR).

++VER (Z038)

FMID (CPSAI00)

PRE ( RO73433 RO73932 )

SUP ( TR85686 )

++HOLD (RO85686) SYSTEM FMID(CPSAI00)


COMMENT (

+----------------------------------------------------------------------+

| CA Subsystem Analyzer for DB2 for z/OS Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+




+----------+-----------------------------------------------------------+


|REQUIRED | |

+----------+-----------------------------------------------------------+

| | |

+----------+-----------------------------------------------------------+

**************************


**************************






Note:

DO NOT apply maintenance to the Xmanager runtime libraries with

Xmanager active as it may result in a discrepancy between dynamically

loaded components and statically loaded components. This may result in

unpredictable behavior with CA-DB2 tools and/or compromise the

operating system/DB2 including possible failure.

).





CMG999 - RM632E MESSAGE NOT FOUND IN 'ISPMLIB' LIBRARY


When creating a migration strategy using CA RC/Migrator for DB2

for Z/OS (RCM), you may experience an ISPF dialog error if the following

conditions are true:

1) The primary object should include at least two different dependent

object types in the hierarchy.

2) An invalid implode/explode option is used for the first dependent

object in the hierarchy.

3) Implode/Explode option 'S' is used to select the second dependent

object.

4) After selecting the second dependent object, hit PF3.

SYMPTOMS:

CMG999

Message RM632E

RM632E message not found in 'ISPMLIB' library.

IMPACT:

Customer will not be able to save the strategy.

CIRCUMVENTION:

Create a new strategy and use valid Implode/Explode options.





Related Problem:

RCM 2742


DESC(CMG999 - RM632E MESSAGE NOT FOUND IN 'ISPMLIB' LIBRARY).

++VER (Z038)

FMID (CINSI00)

SUP ( TR85696 )





PBG GROWING ABEND S13E PUT9807E RC 8 RSN 02000000


When CA Fast Load for DB2 for z/OS (PFL) attempts to grow a Partition

By Growth (PBG) tablespace, a partition instantiation

can fail with a return code 8 and reason code 02000000.

SYMPTOMS:

When PFL attempts to grow a PBG tablespace, a partition instantiation

can fail with a return code 08 and reason code 02000000. The data sets

do not load.

Below is an example of the output received:

PUT9807E - Partition instantiation for a Partition By Growth Tablespace

failed.

Part number: 0002, Return Code: 08, Reason Code: 02000000

PFL1201W - Number of pages exceeds maximum allowed for partition 00001

Load will Continue or End depending on DISCARDS value

PFL3019E - ESTAE intercepted in CSECT FLAUTS1 - ABEND code X'840C4000'

PFL0206E - FASTLOAD application did not complete successfully

PFL0207E - T_Space Task ECB: X'000C4000' Return Code: X'00000004'

PFL2104E - CSECT: FLAUIX4 Abended, Code: X'0013E000' - ESTAE

Intercepted

PFL0212E - Data sets did not load successfully

IMPACT:

The job will abend with S13E. The data sets will not load successfully.

CIRCUMVENTION:

None.




Related Problem:

PFL 1156


DESC(PBG GROWING ABEND S13E PUT9807E RC 8 RSN 02000000).

++VER (Z038)

FMID (CPFLI00)


RO82142 RO82275 RO83928 )

SUP ( TR75998 TR77032 TR77037 TR85707 )

++IF FMID(CPFUI00) REQ(RO85708 ) .











SYMPTOMS:



do not load.



failed.








Intercepted


IMPACT:


CIRCUMVENTION:

None.




Related Problem:

PFL 1156



++VER (Z038)

FMID (CPFUI00)


RO75160 RO77504 RO78859 RO79248 RO80890 RO82436

RO82899 RO84292 )


TR75999 TR76592 TR76686 TR77033 TR77038 TR85708 )












SYMPTOMS:



do not load.



failed.








Intercepted


IMPACT:


CIRCUMVENTION:

None.




Related Problem:

PFL 1156



++VER (Z038)

FMID (CPUTI00)


RO80960 RO82008 RO82144 RO82277 RO82878 RO83394

RO83930 )

SUP ( RO83945 TR83945 TR85709 )

++IF FMID(CPFUI00) REQ(RO85708 ) .






DROP & ADD VERSIONING GENERATED WHEN TEMPORAL TBLS COMPARED


CA RC/Migrator for DB2 for z/OS (RCC) generates DDL to drop and add

versioning when two identical SYSTEM PERIOD temporal tables with different

creators are compared.

SYMPTOMS:

DDL to drop and add versioning are generated when there are no changes

between the source and target base tables.

IMPACT:

The execution will unnecessarily drop and add versioning.

CIRCUMVENTION:

Do not execute the script.





Related Problem:

RCC 663


DESC(DROP & ADD VERSIONING GENERATED WHEN TEMPORAL TBLS COMPARED).

++VER (Z038)

FMID (CINSI00)

PRE ( RO73682 )

SUP ( TR85710 )





PFR0688E WHEN ONE TABLE IN TABLE SPACE


CA Fast Recover for DB2 for z/OS (PFR) may fail when OBIDXLAT is performed

on a tablespace that contains or did contain more than one table.

SYMPTOMS:

The following message is issued:

PFR0688E DUE TO HPGTBLC > 1, OBIDXLAT SYNTAX USING OLD-OBID,NEW-OBID

MUST BE ENTERED FOR OBJECT '&DB..&TS.'

IMPACT:

The OBIDXLAT processing with automatic OBID translation (source and target

OBID not specified in the SYSIN) cannot be used for a tablespace that

currently contains only one table, but contained more tables in the past.

CIRCUMVENTION:

Specify source and target OBID in the SYSIN.


Fast Recover Release 15.0



Related Problem:

PFR 918


DESC(PFR0688E WHEN ONE TABLE IN TABLE SPACE).

++VER (Z038)

FMID (CUGRI00)

PRE ( RO73869 RO74954 RO78711 )


TR85734 )





IDB2UIFI DBG73106E FILE ALREADY LOADED WHEN FILE IS EMPTY



history file LOAD/UNLOAD utility IDB2UIFI will get error message

DBG73106E FILE ALREADY LOADED even though the output file is empty.

The utility may also get error DBG21022E FILE INIT FAILED - FILE TOO

SMALL if the input parms to the utility specify that a LOAD is to be

done, but UNLOAD parms such as UNLD and UNLDTYP are also coded.

SYMPTOMS:

DBG73106E 04:40:37 HISTSTAT FILE ALREADY LOADED

DBG21022E 04:40:37 HISTORY:

FILE HISTACCT INITIALIZATION FAILED. FILE IS TOO SMALL

IMPACT:

The LOAD utility cannot load the LDS history file.

CIRCUMVENTION:

None.





Related Problem:

IDB2 1907


DESC(IDB2UIFI DBG73106E FILE ALREADY LOADED WHEN FILE IS EMPTY).

++VER (Z038)

FMID (CIDBI00)


SUP ( AR83711 TR85758 )





NO DATA SCREEN AFTER PICK WITH INVALID SSID



interface displays No data screen when the PICK command is called with

an invalid subsystem name from the THRDACTV screen (Active threads).

SYMPTOMS:

No data screen is displayed instead of the list of active threads.

IMPACT:

The user interface claims there are no threads running.

CIRCUMVENTION:

Reload the screen by pressing ENTER.






Related Problem:

IDB2 1908


DESC(NO DATA SCREEN AFTER PICK WITH INVALID SSID).

++VER (Z038)

FMID (CIDBI00)


RO75381 RO75439 RO75508 RO78961 RO80610 RO81060

RO82325 RO84357 )

SUP ( RO74286 RO75071 RO75137 RO80242 RO81720 RO84818

TR74286 TR75071 TR75137 TR80242 TR81720 TR84818

TR85759 )





DYN_TEXT_TOKEN IN PDT_STANTEXT TABLE CONTAINS SPACES


When loading data from the sysrec file into CA Detector for DB2 for z/OS

(PDT) history tables, the load control cards for the PDT_STANTEXT table

specify the wrong position for the DYN_TEXT_TOKEN column. This field can be

used to join the dynamic SQL text information with the standard activity data

in the PDT_STANDARD table.

SYMPTOMS:

When viewing records in the PDT_STANTEXT table with a RECTYPE of "DTXT", the

DYN_TEXT_TOKEN column contains EBCIDIC spaces.

IMPACT:

Does not allow the PDT_STANTEXT table to be joined with other PDT history

tables using that column.

CIRCUMVENTION:

None.




Related Problem:

PDT 1345


DESC(DYN_TEXT_TOKEN IN PDT_STANTEXT TABLE CONTAINS SPACES).

++VER (Z038)

FMID (CPDTI00)

SUP ( TR85821 )





PFR0221E EXISTING OBID FOUND WITHOUT NEW OBID


CA Fast Recover for DB2 for z/OS (PFR) ends with RC=8 executing

RECOVER TABLESPACE OBIDXLAT and only 1 table exists in the tablespace.

The HPGTBLC field of FULLDD header page is > 1 and there is no

OLD-OBID,NEW-OBID specified in PFR SYSIN OBIDXLAT.

Message PFR0221E - EXISTING OBID(S) X'zzzz' FOUND WITHOUT NEW OBID

is written out.

SYMPTOMS:

PFR step ends with RC=8.

PTIMSG shows message

PFR0221E - EXISTING OBID(S) X'zzzz'

FOUND WITHOUT SPECIFIED NEW OBID(S)

IN TABLESPACE 'DB1.TS1'

IMPACT:

The object is not recovered/rebuilt correctly and is not usable.

CIRCUMVENTION:

Specify the OLD-OBID and NEW-OBID values in the PFR OBIDXLAT step.


Utility General Recovery and PFR PMM PQC PFC Release 17.0

Utility General Recovery and PFR PMM PQC PFC Version 18.0

Utility General Recovery and PFR PMM PQC PFC Version 19.0

Related Problem:

PFR 954


DESC(PFR0221E EXISTING OBID FOUND WITHOUT NEW OBID).

++VER (Z038)

FMID (CUGRI00)

PRE ( RO74491 RO74954 RO78617 RO82278 RO85294 )

SUP ( TR85854 )





COLUMN FILTERS CANNOT BE TURNED ON



Interface may not display the column filters on some tabular reports. The

problem occurs when the IQL request layout has changed since the user last

used the SORT command.

SYMPTOMS:

The column headers on the affected screen contain dashes (-) instead of the

filter input fields. Using the "FILTER" or "FILTER ON" commands has no

effect.

IMPACT:

Column filtering feature is not available on some screens.

CIRCUMVENTION:

Navigate to the affected screen and issue command "SORT OFF". Press ENTER to

refresh the screen.




Related Problem:

IDB2 1898


DESC(COLUMN FILTERS CANNOT BE TURNED ON).

++VER (Z038)

FMID (CIDBI00)


RO75381 RO75439 RO75508 RO78961 RO80610 RO81060

RO82325 RO84357 RO85759 )


TR75071 TR75137 TR80242 TR84818 TR85856 )





VERSION MISMATCH BETWEEN BSDS AND DB2 RELEASE


CA Recovery Analyzer for DB2 for z/OS (PRA) fails to run ssid@CDC recovery

job on a migrated V11 NFM DB2 subsystem with BSDS converted to extended RBA

by the DSNJCNVT utility.

SYMPTOMS:

The ssid@CDC job abends in the ARCHLOG step. The following messages appear

in the joblog:

RAE00123: Program PRA#ARCL abnormally terminating.

GEN0301E Version mismatch between the BSDS and the DB2 release.

DB2 version:

BSDS version: 11

DSN: bsds.dsname

Cannot process BSDS, program aborting.

IMPACT:

Archive logs are not created and restore jobs are not generated for the

disaster recovery strategy.

CIRCUMVENTION:

None.


CA Recovery Analyzer for DB2 for z/OS Version 18.0

CA Recovery Analyzer for DB2 for z/OS Version 19.0

Related Problem:

PRA 853


DESC(VERSION MISMATCH BETWEEN BSDS AND DB2 RELEASE).

++VER (Z038)

FMID (CPRAI00)

PRE ( RO82069 )

SUP ( TR85859 )





ONE CHARACTER CREATOR OR OBJECT ISSUE/S0C1/SQL -311


In CA RI Manager for DB2 for z/OS (PRI)

1.

When trying to add a child to a table with one character creator name or one

character table name, the column list for selection is not displayed.

2.

When trying to create a user defined RI, SQL ERROR -311 occurs after

selecting the foreign keys.

3.

When trying to create a user defined RI, S0C1 is encountered after

selecting the foreign keys.

4.

When trying to create a system RI, if the table is with one character creator

name or one character table name, the DDL generated for execution does not

have the creator name.

SYMPTOMS:

Below messages are displayed :

1.

None.

2.

DSNT408I SQLCODE = -311, ERROR: THE LENGTH OF INPUT HOST VARIABLE

NUMBER 001 IS NEGATIVE OR GREATER THAN THE MAXIMUM

3.

IEA995I SYMPTOM DUMP OUTPUT


4.

None.

CIRCUMVENTION:

None.


PRI Release 18.0

PRI Version 19.0

Related Problem:

PRI 82


DESC(ONE CHARACTER CREATOR OR OBJECT ISSUE/S0C1/SQL -311).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75302 RO75316 RO82105 )

SUP ( TR85894 )





SQL ERROR WHEN UPDATING A TABLE WITH VARYING LENGTH IX NAMES


CA Fast Load for DB2 for z/OS (PFL) can run into an SQL Error when a table

in a DEFINE NO tablespace has multiple indexes that have names with

different lengths.

SYMPTOMS:

PFL will issue an SQL error message followed by the SQL that was attempted to

be executed. This may look like the following:

PUT0701E - An SQL error has occurred:

DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL "BWGCAWD1". SOME

SYMBOLS THAT MIGHT BE LEGAL ARE: AT MICROSECONDS MICROSECOND

SECONDS SECOND MINUTES MINUTE HOU

DSNT418I SQLSTATE = 42601 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNHPARS SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = 3 0 0 -1 205 502 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'00000003' X'00000000' X'00000000'

X'FFFFFFFF' X'000000CD' X'000001F6' SQL DIAGNOSTIC

INFORMATION

UPDATE SYSIBM.SYSINDEXPART SET SPACE = 0 WHERE IXNAME = 'xxxxxxx''

AND IXCREATOR = 'yyyyyyyy'

AND PARTITION = 00000

IMPACT:

Error message PUT0701E/SQLCODE -104 will be issued, and the program will

terminate processing with an RC=16.

CIRCUMVENTION:

None.



0

Related Problem:

PFL 1160


DESC(SQL ERROR WHEN UPDATING A TABLE WITH VARYING LENGTH IX NAMES).

++VER (Z038)

FMID (CPFLI00)


SUP ( TR85922 )





ENH: PAD SAAS UNLOAD


Allow CA Performance Analytics for DB2 (PAD) to unload CA Detector for

DB2 for z/OS datastore data for upload to SaaS version of PAD.





Related Problem:

PDT 1328


DESC(ENH: PAD SAAS UNLOAD).

++VER (Z038)

FMID (CINSI00)

PRE ( RO83358 RO84444 )

SUP ( TR85895 TR85926 )





ABEND S0C4 IN UTL#SYM WHEN USING TEMPLATE TO ALLOCATE COPIES


When CA Quick Copy for DB2 for z/OS (PQC) uses TEMPLATE to dynamically

allocate image copies, an S0C4 ABEND may occur in module UTL#SYM.

SYMPTOMS:

ABEND S0C4 occurs in module UTL#SYM.

IMPACT:

Creation of dynamically allocated image copy fails.

CIRCUMVENTION:

None.


CA Quick Copy Version 17.0



Related Problem:

PQC 801


DESC(ABEND S0C4 IN UTL#SYM WHEN USING TEMPLATE TO ALLOCATE COPIES).

++VER (Z038)

FMID (CPUTI00)

PRE ( RO74951 RO75456 )

SUP ( TR74732 TR85941 )





EXECUTION ALTER TABLE FAILS WITH SQLCODE -20385


In CA RC/Migrator for DB2 for z/OS (RCM), an SQLCODE -20385 will result

when executing the analysis of an alter table DDL if the analysis generates

DDL as follows:

1) Alter tablespace to alter SEGSIZE.

The execution of this alter tablespace will place the tablespace

in advisory reorg pending status.

2) Alter table which follows the Alter tablespace. The table is created

in the altered tablespace.

SYMPTOMS:

The execution of the Alter tablespace DDL will issue SQLCODE 610 as follows:

DSNT404I SQLCODE = 610, WARNING: A CREATE/ALTER ON OBJECT

<Database>.<Tsname> HAS PLACED OBJECT IN ADVISORY REORG PENDING

DSNT408I SQLCODE = -20385, ERROR: THE STATEMENT CANNOT BE PROCESSED

BECAUSE THERE ARE PENDING DEFINITION CHANGES FOR OBJECT

<Database>.<Tsname> OF TYPE TABLESPACE (REASON 2)

IMPACT:

Customer will not be able to make changes to the table when an alter on

tablespace causes an advisory reorg pending status.

CIRCUMVENTION:

Re-analyze the strategy setting the analysis option 'Drop & Re-create'

to 'Y'.





Related Problem:

RCM 2740


DESC(EXECUTION ALTER TABLE FAILS WITH SQLCODE -20385).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75383 RO75714 )

SUP ( TR85416 TR85906 TR85943 )



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+

|SEQUENCE | Before using CA RC/Migrator for DB2 for z/OS (RCM) |

+----------+-----------------------------------------------------------+

|PURPOSE | To activate this PTF, the customer must perform a |

| | post-install process to load the new MODEL. Additionally, |

| | a change to the BATPROC CDBAPARM library member is |

| | suggested. |

+----------+-----------------------------------------------------------+

|USERS | This process is recommended for ALL USERS; however, it is |

|AFFECTED | specific to customers using CA RC/Migrator to alter |

| | TABLESPACE parameters - MAXROWS, SEGSIZE, DSSIZE, |

| | BUFFERPOOL and/or MEMBER CLUSTER - which result in the |

| | TABLESPACE being placed in Advisory REORG Pending status. |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | RCM Product Administration |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS | Access to the RCM product tables. |

|REQUIRED | Access to update the CDBAPARM library (BATPROC member). |



Release Service Details+----------+-----------------------------------------------------------+

| | |

+----------+-----------------------------------------------------------+

**************************


**************************

NOTE: This action is not required if CA RC/Migrator is NOT being used

to act on table spaces by modifying the following parameters - MAXROWS,

SEGSIZE, DSSIZE, BUFFERPOOL and/or MEMBER CLUSTER. However, if CA

RC/Migrator is being used to act on table spaces in such a manner, take

the action described below.

First, the customer must use the post-install process to load the new

model definition which has been delivered. Alternatively, below is a

copy of the MODEL definition which may be used to CUT and PASTE the

utility into your custom MODEL.

1. Start up the Install process.

2. Enter 3 Tasks.

3. Select your desired subsystem to customize.

4. Select the RCM post-install task of LOAD AND CUSTOMIZE THE MODEL

SERVICES TABLE

5. After entering necessary information, run the generated job to

install the delivered MODEL.

6. Exit the install process.

7. Once the job completes successfully, access the Main Menu for the

CA Database Management Solutions for DB2 for z/OS.

8. Select RC/Migrator (2).

9. Select Profile (0).

10. Select Utility Model Services (6).

11. Use the U line command to update the Model installed in 5 above.

12. Use the X line command next to the OREORGTS utility to activate it.

13. Use PF-3 or END command to save the changes.

Next, it is recommended that the BATPROC CDBAPARM library member be

updated as follows.

1. From the CA DB2 Tools product main menu, select EP to edit a

parmlib member.

2. Select the BATPROC member.

3. Use the I line command to insert a line for a new message number.

4. Enter DSNU1166 in the MESSAGE ID field and O in the FLAG field.

5. Use PF-3 or END to save the changes.

Note the following additional information:

With this PTF, we have delivered a "new" custom utility. This utility

is designed to allow Pending DDL changes made to a TABLESPACE to be

applied via an IBM REORG. This REORG must use SHRLEVEL CHANGE or the

REORG will not apply the pending change. Please go through the

post-install steps to load the new model with the new symbols (see

below). To take advantage of this updated process, this utility or one

like it must be used to allow timely application of TABLESPACE changes

which may restrict the ability to make subsequent TABLE and/or INDEX

changes.

To enable processing:

1. This utility must be in an ACTIVE state.

2. The %OREORG symbol, must be set to a value of 1 so that the

analysis processing can determine whether the IBM REORG was

generated. It may have an X in the ERR column if this symbol is not

in use by the utility text.

When running the generated REORG (under Batch Processor), it is

expected that the utility will issue message DSNU1166I, an

informational message, which results in a RC=4. To override this RC=4

when this message is issued, add message DSNU1166 to the BATPROC

CDBAPARM library as follows:

(DSNU1166,O)

Without the addition of this message to BATPROC, the REORG (if message

DSNU1166I is issued) will stop the script prior to the .SYNC that

follows it.



Release Service DetailsOne final note, this utility relies on a new auto-symbol, %PENDDDL,

which was added specifically for this process. It MUST NOT appear in

the utilities symbol list, or that symbol's value will override the

set auto-symbol. If the utility should have generated, but didn't,

verify that this new auto-symbol is not in the utilities user-symbol

list. To verify, use the BROWSE line command on the model, then the

SYMBOLS line command on the utility, If the symbol is listed, then it

is included in the utility's user symbol list and must be removed.

Here is the new custom utility, OREORGTS:

UTILITY OBJ DESCRIPTION SIZE

OREORGTS TS PENDING DDL ONLINE REORG

CMD SYMBOL ERR REPLACEMENT VALUE

_ COPYDSN %ODSN.&PA..COPY______________________________________

_ DATACLAS _____________________________________________________

_ DISCDSN %ODSN..DISC__________________________________________

_ DSN %USERID..%DSNQUAL2..%DSNQUAL3________________________

_ MGMTCLAS _____________________________________________________

_ ODSN %DSN..TS_____________________________________________

_ OREORG 1____________________________________________________

_ PRIQTY -1___________________________________________________

_ SECQTY -1___________________________________________________

_ STORCLAS _____________________________________________________

_ UNLDDSN %ODSN..UNLD__________________________________________

#CM *******************************************************************

#CM * *

#CM * THIS MODEL IS USED TO GENERATE AN ON-LINE IBM REORG TO APPLY *

#CM * PENDING DDL CHANGES MADE AT THE TABLESPACE-LEVEL. IT IS MEANT *

#CM * TO BE EXECUTED AT THE SQLPOSO POSITION IMMEDIATELY AFTER ALL *

#CM * TABLESPACE DDL HAS BEEN PRODUCED. WITHOUT THIS REORG, POTENTIAL *

#CM * TABLE OR INDEX DDL MAY FAIL DURING EXECUTION. *

#CM * *

#CM * NEW SYMBOL ADDED: *

#CM * %PENDDDL 0 | 1 - THIS IS AN AUTO SYMBOL ONLY SET AT THE SQLPOSO *

#CM * POSITION WHEN DETECTED TS CHANGES HAVE BEEN *

#CM * MADE CAUSING PENDING DDL. *

#CM * %OREORG 1 - IF THIS USER SYMBOL IS PRESENT, IT INDICATES *

#CM * THAT THIS IS AN ON-LINE REORG UTILITY USED TO *

#CM * APPLY PENDING DDL. IF THIS VALUE IS MISSING OR *

#CM * SET TO A VALUE OTHER THAN 1, SUPPRESSION TO *

#CM * CURRENTLY QUEUED REORGS WILL NOT BE DONE. *

#CM * *

#CM *******************************************************************

#IF(%SQLPOSO)

#IF(%OBJDISP,EQ,ALTER)

#IF(%PENDDDL)

.CALL UTIL REORG PARM(%TOSSID)

.DATA

TEMPLATE PTIUNLD DSN '%UNLDDSN'

DATACLAS(%DATACLAS)

MGMTCLAS(%MGMTCLAS)

STORCLAS(%STORCLAS)

SPACE CYL

TEMPLATE PTICOPY DSN '%COPYDSN'

DATACLAS(%DATACLAS)

MGMTCLAS(%MGMTCLAS)

STORCLAS(%STORCLAS)

SPACE CYL

TEMPLATE PTIDISC DSN '%DISCDSN'

DATACLAS(%DATACLAS)

MGMTCLAS(%MGMTCLAS)

STORCLAS(%STORCLAS)

SPACE CYL

EXEC SQL

CREATE TABLESPACE %STRATEGY

IN %DBNAME



Release Service DetailsUSING STOGROUP SYSDEFLT

PRIQTY %PRIQTY

SECQTY %SECQTY

ERASE NO

SEGSIZE 4

BUFFERPOOL BP0

LOCKSIZE ANY

LOCKMAX SYSTEM

LOCKPART NO

CLOSE NO

CCSID EBCDIC;

ENDEXEC

EXEC SQL

CREATE TABLE MT%DBNAME%OBJECT._TB

(TYPE CHAR( 01 ) NOT NULL,

SOURCE_RID CHAR( 05 ) NOT NULL,

TARGET_XRID CHAR( 09 ) NOT NULL,

LRSN CHAR( 06 ) NOT NULL)

IN %DBNAME..%STRATEGY

CCSID EBCDIC

ENDEXEC

EXEC SQL

CREATE UNIQUE INDEX MI%DBNAME%OBJECT_IDX

ON MT%DBNAME%OBJECT._TB

(SOURCE_RID ASC,

TYPE,

TARGET_XRID,

LRSN)

USING STOGROUP PTSG

PRIQTY %PRIQTY

SECQTY %SECQTY

ERASE NO

BUFFERPOOL BP0

CLOSE NO

ENDEXEC

REORG %OBJTYPE %CREATOR..%OBJECT

LOG NO

COPYDDN PTICOPY

UNLDDN PTIUNLD

DISCARDDN PTIDISC

SHRLEVEL CHANGE

DRAIN_WAIT 20

RETRY 10

RETRY_DELAY 60

MAPPINGTABLE MT%DBNAME%OBJECT._TB

MAXRO 18

DRAIN WRITERS

LONGLOG CONTINUE

DELAY 1200

FASTSWITCH YES

UNLOAD CONTINUE

KEEPDICTIONARY

STATISTICS

TABLE(ALL)

INDEX(ALL)

REPORT NO

UPDATE ALL

HISTORY NONE

FORCEROLLUP NO

EXEC SQL

DROP TABLESPACE %DBNAME..%STRATEGY

ENDEXEC

.ENDDATA

#ENDIF

#ENDIF

#ENDIF

).





LBIND/LREBIND ON PLAN OR PACKAGE FAILS WITH S0C4


In CA RC/Query for DB2 for z/OS (RCQ), LBIND/LREBIND commands on a plan or

package may fail with abend S0C4.

SYMPTOMS:

Issuing LBIND/LREBIND commands on a plan or package fails with S0C4 abend in

module PTALBND.

Example:

IRX0250E System abend code 0C4, reason code 00000017

IRX0255E Abend in host command ISPEXEC or address environment routine TSO.

IMPACT:

You cannot use LBIND/LREBIND commands on plan/packages.

CIRCUMVENTION:

NONE.

Related Problem:

RCQ 1499


DESC(LBIND/LREBIND ON PLAN OR PACKAGE FAILS WITH S0C4).

++VER (Z038)

FMID (CINSI00)

PRE ( RO75312 )


TR85481 TR85569 TR85958 )



COMMENT (

+----------------------------------------------------------------------+


| Version 18.0 |

+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|USERS | |


+----------+-----------------------------------------------------------+

|KNOWLEDGE | |


+----------+-----------------------------------------------------------+



+----------+-----------------------------------------------------------+

**************************


**************************




).





BROKEN PAGE AFTER PRR ON PARTITION V11 BIGTAIL


When CA Rapid Reorg for DB2 for z/OS (PRR) reorgs a partitioned object

with extended RBA values in DB2 11, it updates an incorrect value in the


pages allowed per space map. If you subsequently try to copy the object

with an IBM COPY job, or with a CA Quick Copy for DB2 for z/OS (PQC) job

that specified SHRLEVEL REFERENCE and AUDIT 1 or 2, the job will fail with

a broken page found message.

SYMPTOMS:



DBNAME = DBname

TSNAME = TSname

DSNUM = DSnum

PAGE = page number

ERRORCODE = X'0CA8'


following messages:







IMPACT:

Users cannot copy the object with IBM COPY or with a PQC job that

specifies SHRLEVEL REFERENCE with AUDIT 1 or 2.

CIRCUMVENTION:

None


CA Rapid Reorg for DB2 for Z/OS Version 17.0



Related Problem:

PRR 1267


DESC(BROKEN PAGE AFTER PRR ON PARTITION V11 BIGTAIL).

++VER (Z038)

FMID (CPRRI00)

PRE ( RO73458 RO78826 RO80267 RO82276 )

SUP ( TR85972 )

CA DB2 Tools 18.0 1 CA RS 1511 Service List · CA DB2 Tools 6 CA RS 1511 Service List for CPDTI00...

Documents

Transcript of CA DB2 Tools 18.0 1 CA RS 1511 Service List · CA DB2 Tools 6 CA RS 1511 Service List for CPDTI00...