CA DB2 Tools 17.0 1 CA RS 1409 Service List pfl0082e updating syscopy failed no restart for function...

CA DB2 Tools 17.0 1

CA RS 1409 Service ListCA DB2 Tools 17.0 1

CA RS 1409 Service List

Release Service Description Type

17.0 RO72039 REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS PTF

RO72355 ANALYSIS PROFILE NOT HONORED PTF

RO72381 %% SYMBOLIC MASK RESOLVES INCORRECTLY IN RCM/RCC MODELS PTF

RO72383 S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING PTF

RO72411 SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR PTF

RO72439 U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG' PTF

RO72441 XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH *HIP/PRP*

RO72450 UPDATE TO SUPPORT FUTURE RELEASE OF CA CHORUS DBA PTF

RO72465 DROP VIEW IS GENERATED FOR A NEWLY CREATED VIEW PTF

RO72473 DB2 10 OSE PHASE 1 SEGSIZE CMA AND LEGACY DDL PTF



RO72479 MISSING COMMIT CONFIRMATION HELP PANEL PTF

RO72480 MDXO DATASET DOES NOT GET LISTED PTF

RO72481 WORKFILE DB AGENT LIMIT EXCEEDED NOT SHOWN AFTER DB2 V9 PTF

RO72499 DISPLAY LONG SQL STATEMENTS PTF


RO72516 NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1 PTF

RO72541 INCORRECT IFCID 172 MAPPING PTF

RO72549 SQLCODE -110 PPA@EXE1:EXPLAIN SQL WITH HEX VAR VALUE PTF

RO72611 SQL016 PARSE ERROR ** PRP **

RO72648 TGRFXV007E ZERO CELL LENGTH FOUND PTF

RO72655 CONTROL WHETHER DC AND USER AUTHID IS USED FOR THREAD CANCEL PTF



RO72668 IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP PTF

RO72675 LOOP IN DETECTOR WHILE WORKING WITH INSIGHT PTF

RO72694 NEW MESSAGE FOR ELAPSED AND CPU TIME PTF

RO72703 S0C4-4 IN UTLFUM SQL-ACCESS EXTENSION OF LOB PTF

RO72707 INPUT-FORMAT IMAGECOPY W/ DDLDDN W/ FIELDPROC PTF

RO72726 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF









RO72745 ISQL EXPLAIN FORMATING PTF

RO72800 RMA907E NATIVE SP ANALYSIS FAILS WITH ASSERTION ** PRP **

RO72816 S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS PTF

RO72832 INVALID DROP VERSIONING ON HISTORY TABLE PTF


RO72845 TASK COUNT INCORRECT PTF

RO72883 CATALOG UPDATE INDEX CREATOR % PTF

RO72885 DISPLAY INTERNAL OBJECT STATUS FLAGS PTF

RO72887 PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION PTF

RO72888 INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET PTF

RO72908 VREX ABEND TS COLLECTION TASK DB2 11 ALTER DROP COLUMN PTF



RO72911 ROAAL1T INTERNAL ERROR 01 IF TIMESTAMP INCLUDED IN LIMIT KEY PTF

RO72912 EXPLAIN RUNS UNDER DATA COLLECTOR SECURITY INSTEAD OF USER PTF


RO72915 ALTER INDEX HELP PANEL DOES NOT LIST INCLUDE FOR ORDER FIELD PTF

CA DB2 Tools 17.0 2



RO72916 MISSING GETPAGES FOR PARALLEL TASKS EXECUTED UNDER DISTSERV PTF

RO72922 DSG DATASTORES NOT SORTED BY DATE AND TIME PTF

RO72923 SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM PTF

RO72926 SHRLEVEL CHANGE,BPLOOKUP, SYSADM X SET, AUTHORIZATION ERRORS PTF


RO72928 IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS PTF

RO72976 PUT0910E QUIESCE FAILED PTF


RO73014 S0C4 ABEND CANCELING THREAD VIA INSIGHT OR OPTION 6 IN PTT PTF

RO73018 SQL007 FOR PARSING SELECT FROM DELETE SYNTAX PTF

RO73026 S0C4 IN MODULE PTLGCHKP/PTLGCHKA/PTLGCHK9 PTF

RO73067 PTLOG DATE AND TIME VALUES INCORRECT FOR ASCII TABLES. PTF

RO73075 COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED PTF

RO73077 IMAGE COPY STATUS REPORT EXTENDED LOGGING SUPPORT PTF

RO73097 ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10 PTF


RO73135 S0C4 ABEND NSIGHTRW IF TRACE RECORD HAS ZERO DATA SECTIONS PTF

RO73176 RU597E ON VARGRAPHIC DATA DISPLAY PTF

RO73191 ENH:DATASTORE COMPATIBILITY ACROSS RELEASES PTF



RO73195 LOOP IN XMANAGER DURING DETECTOR COLLECTION STARTUP PTF

RO73196 PDTBATCH REPORT DISPLAYS 6-DIGIT USE COUNT PTF

RO73198 DYNAMIC SQL COLLECTION TERMINATES WITH AN S0C4 ABEND PTF

RO73232 MISSING IMAGE COPY STEP FOR PARTITIONED TABLESPACES PTF

RO73247 ABEND S0CX RIGHT AFTER INTERVAL END PTF

RO73252 RO73026 CAUSES A S0C4 ABEND INTO PTAGCHK{P|A|0} ON NON-DS PTF

The CA RS 1409 service count for this release is 83

CA DB2 Tools 16.0 3




16.0 RO72160 REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS PTF






RO72517 NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1 PTF

RO72616 0C4 DT$DII WITH EXCLUDED PLAN OR SQL ERROR ONLY COLLECTION PTF



RO72647 TGRFXV007E ZERO CELL LENGTH FOUND PTF

RO72665 IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP PTF

RO72693 FUNCTION RESTRICTED BY SECURITY IN CA SYSVIEW DB2 MENU PTF

RO72741 PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION PTF


RO72815 S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS PTF






RO73012 COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED PTF




CA DB2 Tools 15.0 4




15.0 RO72410 RMA531E WHEN BOTH I AND J DATASETS ARE PRESENT PTF



RO72581 ABEND S0C4 PSACDDCC COPY UTILITY IF INPUT DS HAS 1 INTERVAL PTF


CA DB2 Tools 5

CA RS 1409 Service List for CCIDG00CA DB2 Tools 5

CA RS 1409 Service List for CCIDG00

FMID Service Description Type

CCIDG00 RO72412 SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR PTF



RO72693 FUNCTION RESTRICTED BY SECURITY IN CA SYSVIEW DB2 MENU PTF

The CA RS 1409 service count for this FMID is 4

CA DB2 Tools 6

CA RS 1409 Service List for CCIDH00CA DB2 Tools 6

CA RS 1409 Service List for CCIDH00


CCIDH00 RO72383 S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING PTF


RO72481 WORKFILE DB AGENT LIMIT EXCEEDED NOT SHOWN AFTER DB2 V9 PTF


RO72541 INCORRECT IFCID 172 MAPPING PTF



RO73135 S0C4 ABEND NSIGHTRW IF TRACE RECORD HAS ZERO DATA SECTIONS PTF


CA DB2 Tools 7

CA RS 1409 Service List for CCOMG00CA DB2 Tools 7

CA RS 1409 Service List for CCOMG00


CCOMG00 RO72741 PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION PTF



CA DB2 Tools 8

CA RS 1409 Service List for CCOMH00CA DB2 Tools 8

CA RS 1409 Service List for CCOMH00


CCOMH00 RO72887 PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION PTF

RO72911 ROAAL1T INTERNAL ERROR 01 IF TIMESTAMP INCLUDED IN LIMIT KEY PTF




CA DB2 Tools 9

CA RS 1409 Service List for CDAGH00CA DB2 Tools 9

CA RS 1409 Service List for CDAGH00


CDAGH00 RO72656 CONTROL WHETHER DC AND USER AUTHID IS USED FOR THREAD CANCEL PTF


CA DB2 Tools 10

CA RS 1409 Service List for CDASG00CA DB2 Tools 10

CA RS 1409 Service List for CDASG00


CDASG00 RO72517 NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1 PTF


CA DB2 Tools 11

CA RS 1409 Service List for CDASH00CA DB2 Tools 11

CA RS 1409 Service List for CDASH00


CDASH00 RO72516 NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1 PTF




CA DB2 Tools 12

CA RS 1409 Service List for CEU9G00CA DB2 Tools 12

CA RS 1409 Service List for CEU9G00


CEU9G00 RO72160 REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS PTF


CA DB2 Tools 13

CA RS 1409 Service List for CEU9H00CA DB2 Tools 13

CA RS 1409 Service List for CEU9H00


CEU9H00 RO72039 REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS PTF


CA DB2 Tools 14

CA RS 1409 Service List for CGENH00CA DB2 Tools 14

CA RS 1409 Service List for CGENH00


CGENH00 RO72727 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF


RO73026 S0C4 IN MODULE PTLGCHKP/PTLGCHKA/PTLGCHK9 PTF

RO73252 RO73026 CAUSES A S0C4 ABEND INTO PTAGCHK{P|A|0} ON NON-DS PTF


CA DB2 Tools 15

CA RS 1409 Service List for CIDBG00CA DB2 Tools 15

CA RS 1409 Service List for CIDBG00


CIDBG00 RO72500 DISPLAY LONG SQL STATEMENTS PTF


CA DB2 Tools 16

CA RS 1409 Service List for CIDBH00CA DB2 Tools 16

CA RS 1409 Service List for CIDBH00


CIDBH00 RO72501 DISPLAY LONG SQL STATEMENTS PTF




CA DB2 Tools 17

CA RS 1409 Service List for COFSH00CA DB2 Tools 17

CA RS 1409 Service List for COFSH00


COFSH00 RO72800 RMA907E NATIVE SP ANALYSIS FAILS WITH ASSERTION ** PRP **


CA DB2 Tools 18

CA RS 1409 Service List for CPASG00CA DB2 Tools 18

CA RS 1409 Service List for CPASG00


CPASG00 RO72871 SQL007 FOR PARSING SELECT FROM DELETE SYNTAX PTF


CA DB2 Tools 19

CA RS 1409 Service List for CPASH00CA DB2 Tools 19

CA RS 1409 Service List for CPASH00


CPASH00 RO72611 SQL016 PARSE ERROR ** PRP **



CA DB2 Tools 20

CA RS 1409 Service List for CPDAH00CA DB2 Tools 20

CA RS 1409 Service List for CPDAH00


CPDAH00 RO72728 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF

RO72883 CATALOG UPDATE INDEX CREATOR % PTF



CA DB2 Tools 21

CA RS 1409 Service List for CPDTF00CA DB2 Tools 21

CA RS 1409 Service List for CPDTF00


CPDTF00 RO72446 XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH *HIP/PRP*


CA DB2 Tools 22

CA RS 1409 Service List for CPDTG00CA DB2 Tools 22

CA RS 1409 Service List for CPDTG00


CPDTG00 RO72459 XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH *HIP/PRP*

RO72616 0C4 DT$DII WITH EXCLUDED PLAN OR SQL ERROR ONLY COLLECTION PTF


CA DB2 Tools 23

CA RS 1409 Service List for CPDTH00CA DB2 Tools 23

CA RS 1409 Service List for CPDTH00


CPDTH00 RO72441 XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH *HIP/PRP*

RO72675 LOOP IN DETECTOR WHILE WORKING WITH INSIGHT PTF

RO72916 MISSING GETPAGES FOR PARALLEL TASKS EXECUTED UNDER DISTSERV PTF

RO72922 DSG DATASTORES NOT SORTED BY DATE AND TIME PTF


RO73195 LOOP IN XMANAGER DURING DETECTOR COLLECTION STARTUP PTF

RO73196 PDTBATCH REPORT DISPLAYS 6-DIGIT USE COUNT PTF

RO73198 DYNAMIC SQL COLLECTION TERMINATES WITH AN S0C4 ABEND PTF


CA DB2 Tools 24

CA RS 1409 Service List for CPFCH00CA DB2 Tools 24

CA RS 1409 Service List for CPFCH00


CPFCH00 RO72729 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF


CA DB2 Tools 25

CA RS 1409 Service List for CPFLG00CA DB2 Tools 25

CA RS 1409 Service List for CPFLG00


CPFLG00 RO72743 INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET PTF


CA DB2 Tools 26

CA RS 1409 Service List for CPFLH00CA DB2 Tools 26

CA RS 1409 Service List for CPFLH00


CPFLH00 RO72694 NEW MESSAGE FOR ELAPSED AND CPU TIME PTF

RO72885 DISPLAY INTERNAL OBJECT STATUS FLAGS PTF



CA DB2 Tools 27

CA RS 1409 Service List for CPFUG00CA DB2 Tools 27

CA RS 1409 Service List for CPFUG00


CPFUG00 RO72872 IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS PTF


CA DB2 Tools 28

CA RS 1409 Service List for CPFUH00CA DB2 Tools 28

CA RS 1409 Service List for CPFUH00


CPFUH00 RO72703 S0C4-4 IN UTLFUM SQL-ACCESS EXTENSION OF LOB PTF

RO72707 INPUT-FORMAT IMAGECOPY W/ DDLDDN W/ FIELDPROC PTF





CA DB2 Tools 29

CA RS 1409 Service List for CPLAG00CA DB2 Tools 29

CA RS 1409 Service List for CPLAG00


CPLAG00 RO73012 COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED PTF


CA DB2 Tools 30

CA RS 1409 Service List for CPLAH00CA DB2 Tools 30

CA RS 1409 Service List for CPLAH00


CPLAH00 RO73075 COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED PTF

RO73077 IMAGE COPY STATUS REPORT EXTENDED LOGGING SUPPORT PTF


CA DB2 Tools 31

CA RS 1409 Service List for CPLRF00CA DB2 Tools 31

CA RS 1409 Service List for CPLRF00


CPLRF00 RO72438 U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG' PTF


CA DB2 Tools 32

CA RS 1409 Service List for CPLRG00CA DB2 Tools 32

CA RS 1409 Service List for CPLRG00


CPLRG00 RO72440 U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG' PTF


CA DB2 Tools 33

CA RS 1409 Service List for CPLRH00CA DB2 Tools 33

CA RS 1409 Service List for CPLRH00


CPLRH00 RO72439 U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG' PTF



CA DB2 Tools 34

CA RS 1409 Service List for CPPAH00CA DB2 Tools 34

CA RS 1409 Service List for CPPAH00


CPPAH00 RO72549 SQLCODE -110 PPA@EXE1:EXPLAIN SQL WITH HEX VAR VALUE PTF

RO72745 ISQL EXPLAIN FORMATING PTF


CA DB2 Tools 35

CA RS 1409 Service List for CPQCH00CA DB2 Tools 35

CA RS 1409 Service List for CPQCH00


CPQCH00 RO72734 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF


CA DB2 Tools 36

CA RS 1409 Service List for CPRAH00CA DB2 Tools 36

CA RS 1409 Service List for CPRAH00


CPRAH00 RO73232 MISSING IMAGE COPY STEP FOR PARTITIONED TABLESPACES PTF


CA DB2 Tools 37

CA RS 1409 Service List for CPRRH00CA DB2 Tools 37

CA RS 1409 Service List for CPRRH00


CPRRH00 RO73098 ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10 PTF


CA DB2 Tools 38

CA RS 1409 Service List for CPSAF00CA DB2 Tools 38

CA RS 1409 Service List for CPSAF00


CPSAF00 RO72581 ABEND S0C4 PSACDDCC COPY UTILITY IF INPUT DS HAS 1 INTERVAL PTF


CA DB2 Tools 39

CA RS 1409 Service List for CPSAG00CA DB2 Tools 39

CA RS 1409 Service List for CPSAG00


CPSAG00 RO73138 ABEND S0CX RIGHT AFTER INTERVAL END PTF


CA DB2 Tools 40

CA RS 1409 Service List for CPSAH00CA DB2 Tools 40

CA RS 1409 Service List for CPSAH00


CPSAH00 RO73192 ENH:DATASTORE COMPATIBILITY ACROSS RELEASES PTF



CA DB2 Tools 41

CA RS 1409 Service List for CPTTG00CA DB2 Tools 41

CA RS 1409 Service List for CPTTG00


CPTTG00 RO72665 IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP PTF


CA DB2 Tools 42

CA RS 1409 Service List for CPTTH00CA DB2 Tools 42

CA RS 1409 Service List for CPTTH00


CPTTH00 RO72668 IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP PTF

RO73014 S0C4 ABEND CANCELING THREAD VIA INSIGHT OR OPTION 6 IN PTT PTF


CA DB2 Tools 43

CA RS 1409 Service List for CPUOH00CA DB2 Tools 43

CA RS 1409 Service List for CPUOH00


CPUOH00 RO72733 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF


CA DB2 Tools 44

CA RS 1409 Service List for CPUTG00CA DB2 Tools 44

CA RS 1409 Service List for CPUTG00


CPUTG00 RO72979 PUT0910E QUIESCE FAILED PTF


CA DB2 Tools 45

CA RS 1409 Service List for CPUTH00CA DB2 Tools 45

CA RS 1409 Service List for CPUTH00


CPUTH00 RO72731 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF



CA DB2 Tools 46

CA RS 1409 Service List for CPXMG00CA DB2 Tools 46

CA RS 1409 Service List for CPXMG00


CPXMG00 RO72815 S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS PTF


CA DB2 Tools 47

CA RS 1409 Service List for CPXMH00CA DB2 Tools 47

CA RS 1409 Service List for CPXMH00


CPXMH00 RO72816 S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS PTF



CA DB2 Tools 48

CA RS 1409 Service List for CRCMF00CA DB2 Tools 48

CA RS 1409 Service List for CRCMF00


CRCMF00 RO72410 RMA531E WHEN BOTH I AND J DATASETS ARE PRESENT PTF


CA DB2 Tools 49

CA RS 1409 Service List for CRCMG00CA DB2 Tools 49

CA RS 1409 Service List for CRCMG00


CRCMG00 RO72638 SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM PTF



CA DB2 Tools 50

CA RS 1409 Service List for CRCMH00CA DB2 Tools 50

CA RS 1409 Service List for CRCMH00


CRCMH00 RO72355 ANALYSIS PROFILE NOT HONORED PTF

RO72381 %% SYMBOLIC MASK RESOLVES INCORRECTLY IN RCM/RCC MODELS PTF


RO72465 DROP VIEW IS GENERATED FOR A NEWLY CREATED VIEW PTF





CA DB2 Tools 51

CA RS 1409 Service List for CRCOH00CA DB2 Tools 51

CA RS 1409 Service List for CRCOH00


CRCOH00 RO72474 DB2 10 OSE PHASE 1 SEGSIZE CMA AND LEGACY DDL PTF


RO72915 ALTER INDEX HELP PANEL DOES NOT LIST INCLUDE FOR ORDER FIELD PTF


CA DB2 Tools 52

CA RS 1409 Service List for CRCUH00CA DB2 Tools 52

CA RS 1409 Service List for CRCUH00


CRCUH00 RO72475 DB2 10 OSE PHASE 1 SEGSIZE CMA AND LEGACY DDL PTF

RO72479 MISSING COMMIT CONFIRMATION HELP PANEL PTF

RO73067 PTLOG DATE AND TIME VALUES INCORRECT FOR ASCII TABLES. PTF

RO73176 RU597E ON VARGRAPHIC DATA DISPLAY PTF


CA DB2 Tools 53

CA RS 1409 Service List for CRCXH00CA DB2 Tools 53

CA RS 1409 Service List for CRCXH00


CRCXH00 RO72480 MDXO DATASET DOES NOT GET LISTED PTF


CA DB2 Tools 54

CA RS 1409 Service List for CTGRG00CA DB2 Tools 54

CA RS 1409 Service List for CTGRG00


CTGRG00 RO72647 TGRFXV007E ZERO CELL LENGTH FOUND PTF



CA DB2 Tools 55

CA RS 1409 Service List for CTGRH00CA DB2 Tools 55

CA RS 1409 Service List for CTGRH00


CTGRH00 RO72648 TGRFXV007E ZERO CELL LENGTH FOUND PTF



CA DB2 Tools 56

CA RS 1409 Service List for CUGRH00CA DB2 Tools 56

CA RS 1409 Service List for CUGRH00


CUGRH00 RO72732 SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS PTF


CA DB2 Tools 17.0 57

CA RS 1409 - PTF RO72039 DetailsCA DB2 Tools 17.0 57

CA RS 1409 - PTF RO72039 Details

Release Service Details17.0 RO72039 RO72039 M.C.S. ENTRIES = ++PTF (RO72039)

REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS

ENHANCEMENT DESCRIPTION:

Object Framework Services Agent (OFA) has been updated to remove the

dependence on Execution Status Data Source in future releases of CA Chorus

for DB2 Database Management to work with CA Chorus DBA Services R17. As part

of this change, OFA is modified to utilize the internal BPLOG table to manage

Object Migration Analysis in a future release of CA Chorus instead of

Datacom.

SYMPTOMS:

This is an enhancement.

IMPACT:

None.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED:

CA Chorus DBA Services Release 16.0


Star Problem(s):

CHRDBM 231

Copyright (C) 2014 CA. All rights reserved. R00023-DF170-SP1

DESC(REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS).

++VER (Z038)

FMID (CEU9H00)

PRE ( RO63167 )

SUP ( RO57060 RO57488 RO58498 RO69341 TR57060 TR57488

TR58498 TR69341 TR71366 TR71501 TR72039 )

++IF FMID(CRCMH00) REQ( RO72450) .

++HOLD (RO72039) SYSTEM FMID(CEU9H00)

REASON (DB2BIND) DATE (14217)

COMMENT (

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

| CA Chorus DBA Services Release 17.0 |

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

|SEQUENCE | After Apply |

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

|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. |

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

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

* STEPS TO PERFORM *

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

DBRMs have changed as part of this maintenance

therefore you must use the Post-Install Tailoring option

to Bind Product Packages and Plans.

Refer to the Implementation Guide for details.

).





ANALYSIS PROFILE NOT HONORED

PROBLEM DESCRIPTION:

In CA RC/Merger for DB2 for z/OS (RMM), when analyzing a Move, Copy or Data

only copy strategy, the DATA ONLY COPY and SHARE LEVEL parameters are always

SET TO 'N' REGARDLESS OF THE VALUES IN THE ANALYSIS PROFILE.

SYMPTOMS:

THE DATA ONLY COPY AND SHARE LEVEL PARAMETERS ARE SET TO 'N' WHEN ANALYZING

no matter what they may be set to in the analysis profile.

IMPACT:

The customer is not able to change the DATA ONLY COPY and SHARE LEVEL

parameters for a MOVE analysis.

CIRCUMVENTION:

None.


RC/Migrator Release 17.0

Star Problem(s):

RCM 2592

(C)2014 CA. All Rights Reserved.R02001-D17-SP1

DESC(ANALYSIS PROFILE NOT HONORED) .

++VER (Z038)

FMID (CRCMH00)

PRE ( RO64737 RO65303 )

SUP ( ZRMM314 )





%% SYMBOLIC MASK RESOLVES INCORRECTLY IN RCM/RCC MODELS


IN CA RC/MIGRATOR FOR DB2 FOR Z/OS (RCM), THE '%%' MASK IN A

dataset name is resolved incorrecly in RCM/RCC models.

SYMPTOMS:

THE '%%' MASK IS RESOLVED INCORRECTLY. IT SHOULD RESOLVE IN

the following manner:

D%%DATE ==> D%DATE

IMPACT:

The generated dataset name is invalid.

CIRCUMVENTION:

None.



Star Problem(s):

RCM 2610


DESC(%% SYMBOLIC MASK RESOLVES INCORRECTLY IN RCM/RCC MODELS) .

++VER (Z038)

FMID (CRCMH00)

PRE ( RO58960 RO62309 RO63122 RO67122 RO67208 RO68369 )

SUP ( RO59340 ZRMM333 )





S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING


CA Insight Database Performance Monitor for DB2 for z/OS Data Collector

may abend with S0C4 when accounting record IFCID 3 originating from

a parallel DDF query is processed.

SYMPTOMS:

Abend S0C4 in LMOD NSIGHTPR CSECT NBRECRDR +000E28 occurs when DB2

subsystem finishes running a parallel DDF thread.

IMPACT:

Insight Data Collector abends with S0C4.

CIRCUMVENTION:

None.


Insight Performance Monitor Release 17.0

Star Problem(s):

IDB2 1674


DESC(S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING) .

++VER (Z038)

FMID (CCIDH00)

PRE ( RO55734 RO56118 RO57238 RO58372 RO58899 RO61468

RO62338 RO63688 RO64386 RO64774 RO65496 RO67673

RO68410 RO69402 RO70410 RO71416 RO71764 )

SUP ( ZDBK145 )





SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR



may ABEND when an IQL request with invalid syntax is started or

checked for syntax errors.

SYMPTOMS:

Unpredictable Data Collector ABENDs (S0C1, S0C4, S0C6) during IQL syntax

check or startup.

IMPACT:

Data Collector ABEND.

CIRCUMVENTION:

Use error-free IQL syntax.




Star Problem(s):

IDB2 1676


DESC(SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR) .

++VER (Z038)

FMID (CCIDH00)


RO67673 RO68410 RO70410 )

SUP ( ZDBK146 )





U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG'


Products calling the CA DB2 Log Reader common component may encounter

a U0776 abend, or with PTFs RO67305, RO67304, or RO67347 (for release

15.0, 16.0, or 17.0 respectively) generate a dump titled either

'SG_GO BEYOND LRNG' OR 'SG_LOOP3 BEYOND LRNG'.

SYMPTOMS:

Jobs will end with a non-zero return code and will show either the

abend or that a dump was produced.

IMPACT:

In all cases, the log read will end and the job will terminate.

Output results will not be produced.

CIRCUMVENTION:

None.


Log Analyzer Release 15.0



LogCompress Release 15.0



Fast Recover Release 15.0



Merge / Modify Release 15.0



Quick Copy Release 15.0



Recovery Analyzer Release 15.0



Rapid Reorg Release 15.0



Fast Unload Release 15.0



Star Problem(s):

PLR 128


DESC(U0776 ABEND OR DUMP TITLED 'SG_GO BEYOND LRNG') .

++VER (Z038)

FMID (CPLRH00)


RO66956 RO67347 RO68440 )

SUP ( RO59677 RO71787 ZLRL027 )





XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH


CA Detector for DB2 for z/OS (PDT) may cause the Xmanager to run low on

virtual storage. The Xmanager will issue warning/error messages, may abend

with various abend codes and possibly hang requiring it to be cancelled or

forced terminated. If the Xmanager is cancelled or force terminated DB2

subsystems with PDT or CA Subsystem Analyzer for DB2 for z/OS (PSA)

collections active may crash.

This problem can occur in r15 with APAR RO50593 installed, r16 with APAR

RO51131 installed and in the GA release of r17. The problem occurs when

Exceptions and SQL errors are being collected by PDT, the maximum exceptions

per interval has been reached, the SQL errors captured per interval has not

been reached and an excessive number of SQL statement executions receive a

negative SQLCODE.

Also, CA Detector for DB2 for z/OS (PDT) captures exceptions that do not meet

the Dynamic SQL Exception Thresholds or Static SQL Exception Thresholds.

This problem occurs when one of the following APARs is installed:

For r15 - APAR RO72151



SYMPTOMS:

The following symptoms occur for the low on virtual storage problem:

The following message will be issued by the Xmanager:

PXM0372 XMANAGER REGION INUSE HAS REACHED SHORTAGE THRESHOLD FOR EPVT

PXM0373 XMANAGER REGION EPVT STORAGE SHORTAGE RELIEVED

If a PDT collection is active the following messages may be issued:

PDT0171 DETECTOR COLLECTION INTERVAL END FORCED DUE TO XMANAGER STORAGE

SHORTAGE, DB2=<ssid>

If a PSA collection is active the following messages may be issued:

PSA0171 SSANALZE COLLECTION INTERVAL END FORCED DUE TO XMANAGER STORAGE


PSA0814 SSANALZE ABTERM/SDUMP IN PROGRESS DB2=<ssid>

Various storage related messages and abends will occur.

The following symptoms occur when exceptions are erroneously captured, i.e.

they do not meet the exception thresholds:

The value displayed on the DETECTOR Exception SQL Request Summary for the

SQL column is zero.

The value displayed on the DETECTOR Exception SQL User Summary

Display for the EXCEPTION column exceeds the exceptions per

interval limit specified in the exception profile.

IMPACT:

The Xmanager fails. DB2 subsystems may crash if the Xmanager hangs and has

to be cancelled or force terminated.

Exceptions are erroneously captured, i.e. they do not meet the exception

thresholds.

CIRCUMVENTION:

For the low on virtual storage problem:

Stop and restart PDT collections every four to eight hours to release the

storage that has been accumulated or do not collect SQL Errors.

To avoid invalid exceptions being captured:

Do not collect SQL errors.

To stop SQL Errors from being collected:

Depending on how collections are started SQL Error collection can be set so

NO SQL Errors will be collected as follows:

SETTING SQL ERRORS TO 'N' ON THE DETECTOR START COLLECTION DISPLAY OR BY

setting SQE(N) on the Xmanager modify command, i.e.,

F PTXMAN,START(DTR),DB2(ssid),SQE(N)... or in a member of CDBAPXMP PDS as

-START(DTR), DB2(ssid),SQE(N)...


Detector Release 15.0



Star Problem(s):



Release Service DetailsPDT 1208


DESC(XMANAGER OUT OF STORAGE CAUSING ABENDS AND DB2 CRASH) .

++VER (Z038)

FMID (CPDTH00)


RO66707 RO66750 RO67018 RO68135 RO69879 RO69977

RO70638 RO71275 RO71707 RO72018 RO72138 )

SUP ( HDTM008 ZDTM094 )

++HOLD (RO72441) SYSTEM FMID(CPDTH00)

REASON (ACTION ) DATE (14216)

COMMENT (

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

| Detector Release 17.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.

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.

).





UPDATE TO SUPPORT FUTURE RELEASE OF CA CHORUS DBA


CA RC/Migrator for DB2 for z/OS (RCM) has been updated to process new

parameters passed from CA Chorus DBA Services as part of the Object Migration

Analysis in a future release of CA Chorus for DB2 Database Management and

store them in the internal BPLOG table. This change is necessary to let you

manage Object Migration Analysis using a future release of CA Chorus without

Datacom.

SYMPTOMS:


IMPACT:

None.

CIRCUMVENTION:

None.


CA RC/Migrator for DB2 for z/OS Release 16.0


Star Problem(s):

RCM 2584


DESC(UPDATE TO SUPPORT FUTURE RELEASE OF CA CHORUS DBA) .

++VER (Z038)

FMID (CRCMH00)


RO68369 )

SUP ( ZRMM320 )

++IF FMID(CRBPH00) REQ(RO71117) .

++IF FMID(CINSH00) REQ(RO71118) .

++HOLD (RO72450) SYSTEM FMID(CRCMH00)


COMMENT (

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

|RC/Migrator Version 17.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).





DROP VIEW IS GENERATED FOR A NEWLY CREATED VIEW


CA RC/Migrator for DB2 for z/OS (RCM) generates drop view DDL for a

newly created view when the following conditions are true:

1) Parent table is altered to add a new column (DB2 Alter).

2) A new view is created using SELECT *.

SYMPTOMS:

Drop VIEW <VWCreator>.<VWName> is generated for the new view.

IMPACT:

The execution of the drop view DDL will fail.

CIRCUMVENTION:

Edit the generated script and delete the drop view DDL from the script

for the newly created view.



Star Problem(s):

RCM 2611


DESC(DROP VIEW IS GENERATED FOR A NEWLY CREATED VIEW) .

++VER (Z038)

FMID (CRCMH00)


SUP ( RO58864 RO59375 ZRMM334 )





DB2 10 OSE PHASE 1 SEGSIZE CMA AND LEGACY DDL


In CA RC/Migrator for DB2 for z/OS (RCM), there is no support

for the SEGSIZE OSE. Currently RCM drops and recreates

the Table Space when there is a SEGSIZE change. RCM

should determine if an ALTER TABLESPACE SEGSIZE could

work instead of DROP/CREATE. This will provide some support

for SEGSIZE OSE DB2v10.

SYMPTOMS:

Generated DDL is a DROP/CREATE on any alter of SEGSIZE.

IMPACT:

Any ALTER to SEGSIZE in a Strategy could be impacted.

CIRCUMVENTION:

None.



Star Problem(s):

RCM 2598


DESC(DB2 10 OSE PHASE 1 SEGSIZE CMA AND LEGACY DDL) .

++VER (Z038)

FMID (CRCMH00)


RO60338 RO60416 RO60968 RO61971 RO62309 RO62768

RO62806 RO62810 RO63122 RO63435 RO65303 RO65539

RO65664 RO65910 RO66627 RO67356 RO67443 RO68233

RO68267 RO68369 RO68776 RO68801 RO68912 RO69313

RO69789 RO70548 RO70853 RO71803 )

SUP ( RO55675 RO56657 RO57874 RO58836 RO59111 RO59326

RO59723 RO69496 ZRMM335 )

++IF FMID(CRCOH00) REQ(RO72474) .

++IF FMID(CRCUH00) REQ(RO72475) .













SYMPTOMS:


IMPACT:


CIRCUMVENTION:

None.



Star Problem(s):

RCM 2598



++VER (Z038)

FMID (CRCOH00)


SUP ( ZRMM335 )

++IF FMID(CRCMH00) REQ(RO72473) .

++IF FMID(CRCUH00) REQ(RO72475) .

++HOLD (RO72474) SYSTEM FMID(CRCOH00)


COMMENT (

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

|Catalog Facility Common Version 17.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).













SYMPTOMS:


IMPACT:


CIRCUMVENTION:

None.



Star Problem(s):

RCM 2598



++VER (Z038)

FMID (CRCUH00)

PRE ( RO67720 RO70549 RO70854 RO71561 )

SUP ( ZRMM335 )







MISSING COMMIT CONFIRMATION HELP PANEL


IN CA RC/UPDATE FOR DB2 FOR Z/OS (RCU), HELP PANEL FOR 'EDIT CONFIRMATION

PANEL' IS NOT AVAILABLE. WHEN ACCESSING THE HELP PANEL BY PRESSING PF1, THE

general PFU help panel is displayed.

SYMPTOMS:

On pressing PF1, the RCU General Help panel is displayed instead of commit

confirmation help panel.

IMPACT:

Help information is not available for the confirmation panel.

CIRCUMVENTION:

None.

PRODUCT AFFECTED:

RCU R17.0

Star Problem(s):

RCU 998


DESC(MISSING COMMIT CONFIRMATION HELP PANEL) .

++VER (Z038)

FMID (CRCUH00)

SUP ( ZRUM027 )





MDXO DATASET DOES NOT GET LISTED


In CA RC/Extract for DB2 for z/OS, when performing a batch mode extraction

on an extended extract, even though only EQF details or LIMIT details are

updated in the extraction JOB, the MDXO dataset is not Extended Extract

ManagementPanel.

SYMPTOMS:

Whenn EQF details or LIMIT details are edited, the extraction goes into

transport mode making the MDXO unavailable in the management panel.

IMPACT:

The MDXO dataset is unavailable for LOAD/EXPORT/VIEW and other features.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

RC/EXTRACT R17.0

Star Problem(s):

RCX 552


DESC(MDXO DATASET DOES NOT GET LISTED) .

++VER (Z038)

FMID (CRCXH00)

PRE ( RO56630 RO58412 RO68138 RO71967 )

SUP ( ZRXK074 )

++HOLD (RO72480) SYSTEM FMID(CRCXH00)


COMMENT (

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

|RC/Extract Version 17.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |

|REQUIRED | CA DB2 Tools Post Install Customization |

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



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

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


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

Bind Control Cards have changed as part of this

maintenance. After this maintenance is applied, Bind

Control Cards must be regenerated for all installed

products. Using the newly generated Bind Control Cards,

a Bind Replace must be performed on the plans and

packages for all installed products. Refer to the

Implementation guide for details.

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

|RC/Extract Version 17.0 |

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


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


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

|USERS | |




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

|KNOWLEDGE | |


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



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

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


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





).

++HOLD (RO72480) SYSTEM FMID(CRCXH00)

REASON (ENH ) DATE (14218)

COMMENT (

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

| RC/Extract Release 17.0 |

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


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

|PURPOSE | Bind Plans and Packages. |

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

|USERS | R17 ONWARDS |

|AFFECTED | |

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

|KNOWLEDGE | CA DB2 Tools Post Install Customization. |

|REQUIRED | |

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



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

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


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

1. ENSURE TO BIND MXA$POX, THIS WAS A NON DB2 MODULE EARLIER

).





WORKFILE DB AGENT LIMIT EXCEEDED NOT SHOWN AFTER DB2 V9


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

interface panels SYSWKDB and HSWKDB no longer show the number of

times the agent limit was exceeded if running DB2 V10 or higher.

SYMPTOMS:

The line:

Number of times agent limit exceeded ...

is missing from these two displays.

IMPACT:

The value of this field cannot be looked up.

CIRCUMVENTION:

The IQL requests may be manually corrected.




Star Problem(s):

IDB2 1679


DESC(WORKFILE DB AGENT LIMIT EXCEEDED NOT SHOWN AFTER DB2 V9) .

++VER (Z038)

FMID (CCIDH00)


RO65574 RO66053 RO71416 )

SUP ( RO61747 ZDBK147 )





DISPLAY LONG SQL STATEMENTS


Support display of long SQL statement text in the SQLTEXT and DYNSQLTX

IQL requests. Also add new IQL requests DSQDYNSL and DSQTHDSL for

Chorus support of long SQL statements.

SYMPTOMS:

SQLTEXT and DYNSQLTX displays show incomplete data when very long

SQL statements are encountered.

IMPACT:

All users referencing the SQLTEXT and DYNSQLTX displays.

CIRCUMVENTION:

None.




Star Problem(s):

IDB2 1677


DESC(DISPLAY LONG SQL STATEMENTS) .

++VER (Z038)

FMID (CCIDH00)


RO57842 RO58372 RO58899 RO59571 RO59641 RO61468

RO63575 RO63688 RO64386 RO64774 RO65574 RO66390

RO66640 RO67568 RO67673 RO67977 RO68410 RO68598

RO69049 RO69726 RO70410 RO70491 RO70965 RO71416

RO71764 )

SUP ( HCIK003 RO55923 RO56238 RO56385 RO56442 RO57766

RO62164 RO62203 RO62338 RO63261 RO63984 RO64025

RO64775 RO65052 RO65394 RO65496 RO65887 RO66048

RO66472 RO66520 RO67069 RO67677 RO67827 RO68766

RO68936 RO69052 RO69388 RO69402 RO70132 RO70718

RO71465 RO72162 RO72383 ZDBK149 )

++IF FMID(CIDBH00) REQ(RO72501) .










SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.




Star Problem(s):

IDB2 1677



++VER (Z038)

FMID (CIDBH00)


RO61312 RO61469 RO63689 RO64387 RO66641 RO67675

RO68412 RO70412 RO70492 RO71239 )

SUP ( RO56061 RO58663 RO62166 RO66132 RO66719 ZDBK149 )

++IF FMID(CCIDH00) REQ(RO72499) .





NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1


CA Database Analyzer for DB2 for z/OS (PDA) tablespace statistics

collection subtasks may abend before the collection is complete. See

SYMPTOMS section for specifics. The PDA extract execution environment

or conditions would need to minimally include the following:

- DB2 environment is non-datasharing

- Number of collection subtasks or Scans is > 1

- Includes at least one multiple versioned tablespace or was once

versioned and is not the first selected tablespace for stats

collection processing

SYMPTOMS:

The following message can be found in the PTIMSG output:

DB2 Version not supported RC=0211 RS=0000

Error opening DB2 loadlibs for <ssid> RC=0109 RS=0143

PTABDBS: PTLBDBC subtask has abended: S806 RC=0064 RS=2054

PTABDBS: PTLBDBC subtask has abended: S0C4 RC=0064 RS=0196


PTABDBS: PTLBDBC subtask has abended: S0F4 RC=0064 RS=0244

Also the following message can be found in the JOB log:

CSV005I BLDL FAILED FOR MODULE DSNACAB , DCB NOT OPEN

IMPACT:

One or more tablespace statistics collection subtasks will be

incomplete. The stats collection will continue, however, depending on

the severity of the symptom the entire extract may terminate before

all objects are processed.

CIRCUMVENTION:

Resubmit the extract with Scans=1. This will require the PDA batch

extract job to be regenerated with the Submit panel field "Nbr of

Scans" set to 1.


PDA Database Analyzer Release: 16.0


Star Problem(s):

PDA 1260


DESC(NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1) .

++VER (Z038)

FMID (CDASH00)

PRE ( RO57939 RO58594 RO58655 )

SUP ( RO67218 RO70205 ZDAM051 )





INCORRECT IFCID 172 MAPPING


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

uses incorrect mapping for IFCID 172 - DEADLOCK.

The LOCKCONT IQL request allows "T" line command for static statements

that are not available in the DB2 Catalog and incorrectly shows DYNSQLTX

request.

SYMPTOMS:

The use of line command "T" on LOCKCONT request causes incorrect statement

to be displayed.

IMPACT:

CA Insight DPM shows correct data on LOCKCONT screen, but displays incorrect

statement detail.

CIRCUMVENTION:

Modify the DEADLOCK part of the LOCKCONT IQL request. Change the key to use

HOLD-* fields for waiter statements and WAIT-* fields for holder statements.

Optionally, add a column to the request for fields WAIT-STMT-TYPE-FLG and

HOLD-STMT-TYPE-FLG to see what type of statement is involved in the

deadlock.



Star Problem(s):

IDB2 1672


DESC(INCORRECT IFCID 172 MAPPING) .

++VER (Z038)

FMID (CCIDH00)


RO62338 RO63688 RO64386 RO64774 RO65496 RO65574

RO66472 RO67673 RO68598 RO69402 RO71416 RO71764

RO72499 )

SUP ( RO55923 ZDBK148 )





SQLCODE -110 PPA@EXE1:EXPLAIN SQL WITH HEX VAR VALUE


An SQL error in PPA@EXE1 causes SQLCODE -110 to occur during EXPLAIN of

SQL statements using CA Plan Analyzer for DB2 for z/OS - Explain output when

HEX variable value present in SQL text. HEX variable value truncation by 1 b

causes a SQL error.

SYMPTOMS:

For example:

The original SQL statement:

SELECT * FROM CREATOR.TABLE_NAME WHERE COLUMN = X"C3C1E2C8"

modified by internal format service as

SELECT * FROM CREATOR.TABLE_NAME WHERE COLUMN = X'C3C1E2C'

The following -110 SQL error will appear in the explain output:

SQL ERROR IN PLAN PPAMR171 IN DBRM PPA@EXE1 STATEMENT 2,473

SSID: D10A DB2 VERSION: V10R1M0

DSNT408I SQLCODE = -110, ERROR: INVALID HEXADECIMAL CONSTANT BEGINNING

X'C3C1E2C'

DSNT418I SQLSTATE = 42606 SQLSTATE RETURN CODE

IMPACT:

The corrupted SQL statements cannot be explained and do not accurately

represent the original SQL text.

CIRCUMVENTION:

None.


Plan Analyzer Release 15.0



Star Problem(s):

PPADB2 844


DESC(SQLCODE -110 PPA@EXE1:EXPLAIN SQL WITH HEX VAR VALUE) .

++VER (Z038)

FMID (CPPAH00)

PRE ( RO56380 RO56462 RO57953 RO58125 RO69435 )

SUP ( ZPAM057 )





SQL016 PARSE ERROR


In CA Plan Analyzer Services for DB2 for z/OS (PAS), the SQL

Parsing Service has introduced a parse error when PTF RO72173 is

applied. The parse error SQL016 will occur for SQL similar to the

following example:

SELECT DISTINCT CORRNAME.COLUMN FROM CRT.TABLE CORRNAME

SYMPTOMS:

SQL016: Invalid TOKEN detected in SUBSELECT clause.

Expecting FROM

IMPACT: This error was introduced by PAS problem 207, PTF RO72173

which was created within the past two weeks.

CIRCUMVENTION:

None.


Plan Analyzer Common Release 17.0

Star Problem(s):

PAS 211


DESC(SQL016 PARSE ERROR) .

++VER (Z038)

FMID (CPASH00)

PRE ( RO64773 RO71836 )

SUP ( HPSL001 RO66874 RO72173 ZPSL022 )





TGRFXV007E ZERO CELL LENGTH FOUND


Tiger reads the VVRs for all data sets it is copying. If the length

of the VVR exceeded the size of the VVR buffer, the VVR was cut off

at the end of the buffer. The cell appeared to have a zero length

because it was not present in the buffer.

This fix provides larger VVR buffer and adds code to look for VVR

RECORD TRUNCATION. IF A VVR'S LENGTH EXCEEDS THE BUFFER SIZE, NEW

message TGRFXV009E is issued indicating the size of the VVR and the

size of the current buffer.

Also, an overlay of the working storage by a service routine has been

corrected. This overlay could manifest itself in unpredictable ways.

SYMPTOMS:

When performing FlashCopy operations, some data sets get message:

TGRFXV007E (2) Zero cell length found at offset 0x0847 searching for

type 0x27 cell in source VVR

The copy operation fails for that data set.

IMPACT:

Data sets with large VVRs (typically those with many extents) cannot

be processed.

CIRCUMVENTION:

None.


PQC DB2 Tools Quick Copy Release 18.0.0B

PQC DB2 Tools Quick Copy Release 17.0


DBCOPY IMS Tools Copy Release 18.0.0B

DBCOPY IMS Tools Copy Release 17.0


Star Problem(s):

TGR 247


DESC(TGRFXV007E ZERO CELL LENGTH FOUND) .

++VER (Z038)

FMID (CTGRH00)

PRE ( RO56138 RO67131 RO69090 RO70864 )

SUP ( RO70944 RO71479 ZTGK013 )

++HOLD (RO72648) SYSTEM FMID(CTGRH00)

REASON (MSGSKEL) DATE (14223)

COMMENT (

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

|Snapshot General Services Version 17.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,



Release Service Detailsno further action is required. If you do

customize XMESSAGES, after maintenance is APPLIED

re-apply any XMESSAGE customizations and relink

the XMESSAGE load modules. Refer to the Post

Installation and Customization Guide for details.

).





CONTROL WHETHER DC AND USER AUTHID IS USED FOR THREAD CANCEL


CA Insight Database Performance Monitor for DB2 for z/OS (IDB2) is enhanced

to cancel a thread from the Active Thread request either by using the

Data Collector or logged user authorization ID. A new system parameter

THREAD-CANCEL-AUTHID controls which authorization ID is used.

The default value is set to use the Data Collector authorization ID in order

to preserve existing functionality.

SYMPTOMS:

Threads can be only cancelled using the Data Collector AuthID.

IMPACT:

A user with no authority can cancel DB2 threads using the Data Collector ID.

CIRCUMVENTION:

Update the security settings to forbid unauthorized users from cancelling

threads.

PRODUCT(S) AFFECTED: Insight Performance Monitor Release 17.0

Star Problem(s):

IDB2 1682


DESC(CONTROL WHETHER DC AND USER AUTHID IS USED FOR THREAD CANCEL) .

++VER (Z038)

FMID (CCIDH00)


RO58899 RO59571 RO59641 RO61008 RO61468 RO62338

RO63575 RO63688 RO64386 RO64774 RO65496 RO66472

RO66640 RO67673 RO67977 RO68410 RO69049 RO69402

RO69726 RO70410 RO70491 RO70965 RO71238 RO71416

RO71764 RO72499 )

SUP ( HCIK001 HCIK003 HCIK004 RO56238 RO56360 RO56385

RO56437 RO56442 RO56823 RO57766 RO60770 RO61124

RO61160 RO62164 RO62203 RO63261 RO63336 RO63984

RO64025 RO64034 RO64576 RO64775 RO64933 RO65052

RO65103 RO65194 RO65281 RO65394 RO65516 RO65536

RO65887 RO65999 RO66048 RO66390 RO66520 RO66763

RO67069 RO67255 RO67568 RO67677 RO67827 RO68229

RO68766 RO68936 RO69052 RO69103 RO69109 RO69388

RO69938 RO70034 RO70132 RO70167 RO70718 RO70741

RO71309 RO71465 RO71485 RO72086 RO72162 RO72383

RO72411 ZDBK150 )

++IF FMID(CDAGH00) REQ(RO72656) .














SYMPTOMS:


IMPACT:


CIRCUMVENTION:


threads.


Star Problem(s):

IDB2 1682



++VER (Z038)

FMID (CDAGH00)

PRE ( RO56120 RO64388 RO67674 RO68411 RO70411 )

SUP ( ZDBK150 )















SYMPTOMS:


IMPACT:


CIRCUMVENTION:


threads.


Star Problem(s):

IDB2 1682



++VER (Z038)

FMID (CIDBH00)


RO59642 RO61312 RO61469 RO61846 RO63689 RO64387

RO66641 RO67675 RO67978 RO68412 RO69050 RO69573

RO70412 RO70492 RO70498 RO71239 RO72501 )


RO68548 RO69876 ZDBK150 )


++IF FMID(CDAGH00) REQ(RO72656) .





IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP


The CCSID DSNZPARM field help displays within CA Thread

Termination/Dynamic ZPARM for DB2 for z/OS (PTT) do not reflect the

following recommendation from the DB2 for z/OS Installation and

Migration Guide:

Recommendation: Never change CCSIDs on an existing DB2 system without

specific guidance from IBM Software Support.

SYMPTOMS:

The CCSID DSNZPARM field help displays within PTT do not reflect the


Migration Guide:



IMPACT:

UPDATING ONE OF THE CCSID'S MAY COMPROMISE DATA INTEGRITY.

CIRCUMVENTION:

BE MINDFUL OF IBM'S RECOMMENDATION:




Thread Terminator Release 15.0



Star Problem(s):

PTT 317


DESC(IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP) .

++VER (Z038)

FMID (CPTTH00)

SUP ( ZTTM021 )





LOOP IN DETECTOR WHILE WORKING WITH INSIGHT


CA Detector for DB2 for z/OS (PDT) may cause the an DB2 application

thread to loop.

SYMPTOMS:

An application thread may incur high CPU utilitization and

run times.

IMPACT:

Application threads may have to be terminated to resolve the

high CPU utilitization.

CIRCUMVENTION:

None.




Star Problem(s):

PDT 1209


DESC(LOOP IN DETECTOR WHILE WORKING WITH INSIGHT) .

++VER (Z038)

FMID (CPDTH00)


RO66064 RO66129 RO66619 RO68135 RO69879 RO69977 )

SUP ( ZDTM096 )



COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:







Release Service Detailsoperating system/DB2 including possible failure.

).





NEW MESSAGE FOR ELAPSED AND CPU TIME


This PTF adds diagnostics message PFL2207I for the CA Fast Load for DB2

for z/OS (PFL) product to display elapsed time and cpu consumption

per each data and sort task. This message is logged in the PTIIMSG

dataset if keyword ALLMSGS is in effect.

SYMPTOMS:

There is no related message currently logged in the output dataset

that displays cpu and elapsed time metrics per task.

IMPACT:

It may be cumbersome to evaluate performance without these metrics.

CIRCUMVENTION:

None

PRODUCT(S) AFFECTED: Fast Load Release 16.0

Fast Load Release 17.0

Star Problem(s):

PFL 1050

PFL4020E SORT ABEND


CA Fast Load for DB2 for z/OS (PFL) may abend with an S0C4 or log

message PFL2208I with invalid characters in the INDDN field when

ALLMSGS and RECLUSTER YES are in effect.

SYMPTOMS:

One or more of the following messages may be logged in the output:

PFL2208I - Data sort task ended. TCB:007D3100 Module:FLA$XSRT

INDDN:....o..J Elapsed Time 00:00:02 CPU 00:00:00

PFL4020E - SORT ABENDED - ABEND CODE: X'0C4'

SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011

ACTIVE LOAD MODULE ADDRESS=0003B000 OFFSET=0002FFB6

NAME=CSLVC31R

IMPACT:

The load completes successfully but the S0C4 or the invalid PFL2208I

message is shown in the output.

CIRCUMVENTION:

Remove the ALLMSGS keyword from the //SYSIN DD.



PFL 1062


DESC(NEW MESSAGE FOR ELAPSED AND CPU TIME) .

++VER (Z038)

FMID (CPFLH00)


RO64053 RO64313 RO64874 RO65973 RO69238 RO71065 )

SUP ( ZFLM023 ZFLM029 )

++HOLD (RO72694) SYSTEM FMID(CPFLH00)


COMMENT (

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

|Fast Load Version 17.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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




Release Service Details


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

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


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



no further action is required. If you do





).





S0C4-4 IN UTLFUM SQL-ACCESS EXTENSION OF LOB


CA Fast Unload for DB2 for z/OS (PFU) fails with S0C4-4 in module UTLFUM

offset=6378 when SQL-ACCESS EXTENSION, INPUT-FORMAT TABLE, and SHRLEVEL

REFERENCE options are used to unload a table with LOB columns. The main

reason for the failure is due to the LOB object created under a release prior

to DB2 9 and migrated to a DB2 9 and above release.

SYMPTOMS:

Job abends following information in job log;

SYSTEM COMPLETION CODE 0C4 REASON CODE 00000004

PSW AT TIME OF ERROR 078D0000 80122378 ILC 4 INTC 04

ACTIVE LOAD MODULE UTLFUM ADDRESS 0011C000 OFFSET 00006378

IMPACT:

PFU fails to UNLOAD.

CIRCUMVENTION:

Specify SQL-ACCESS ONLY in the PFU syntax to circumvent.

PRODUCT(S) AFFECTED: Fast Unload Release 17.0

Star Problem(s):

PFU 916


DESC(S0C4-4 IN UTLFUM SQL-ACCESS EXTENSION OF LOB) .

++VER (Z038)

FMID (CPFUH00)

PRE ( RO56658 RO57178 RO64636 RO72276 )

SUP ( ZFUM100 )





INPUT-FORMAT IMAGECOPY W/ DDLDDN W/ FIELDPROC


When executing CA Fast Unload for DB2 for Z/OS (PFU)

with the following parameters

INPUT-FORMAT IMAGECOPY

DDLDDN data-set

and the DDLDDN data set contains a column definition

using FIELDPROC

then PFU writes error message PFU0011E

PFU0011E - SYNTAX ERROR ON OR NEAR LOCATION 010

and ends with cond code 8

SYMPTOMS:

PFU writes error message PFU0011E

PFU0011E - SYNTAX ERROR ON OR NEAR LOCATION 010

and ends with cond code 8

IMPACT:

No rows are unloaded.

CIRCUMVENTION:

Remove PFU parameter

DDLDDN dataset



Star Problem(s):

PFU 917


DESC(INPUT-FORMAT IMAGECOPY W/ DDLDDN W/ FIELDPROC) .

++VER (Z038)

FMID (CPFUH00)


SUP ( ZFUM101 )





SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS


CA Database Analyzer Services for DB2 for z/OS (DAS) COLCARD

estimator service was updated to provide additional functionality

that will allow its callers to control when internal control blocks

are acquired in a synchronous environment.

These new changes used additional storage when there were DEFINE

NO objects included in the Extract. Additional storage was also

used based on first index key column found.

Main extracts that would be affected would have Column Stats = A

SYMPTOMS:

Various system related abends related to low storage (S40D, S878).

IMPACT:

Extract may not finish execution and if it does it may use more

storage than it did in the past.

CIRCUMVENTION:

Site should break the Extract(s) down to have more Extracts and less

objects in each one. For example, it is not recommended to bring the

entire subsystems set of objects into one Extract.

A better solution is for users to use Real Time Object Selection

(RTOS) Mode = Action based Extracts. These typically avoids DEFINE

NO objects because they are not defined in the IBM Real-Time

Statistics (RTS) tables that Extract Object Conditions are utilizing.


Database Analyzer Release 17.0

Star Problem(s):

PDA 1259


DESC(SOME STORAGE RELIEF OF SOME R17 GA INTERNAL CHGS) .

++VER (Z038)

FMID (CDASH00)


SUP ( RO67218 RO70205 RO72516 ZDAM052 )

++IF FMID(CGENH00) REQ(RO72727) .

++IF FMID(CPDAH00) REQ(RO72728) .

++IF FMID(CPFCH00) REQ(RO72729) .

++IF FMID(CPFUH00) REQ(RO72730) .

++IF FMID(CPUTH00) REQ(RO72731) .

++IF FMID(CUGRH00) REQ(RO72732) .

++IF FMID(CPUOH00) REQ(RO72733) .

++IF FMID(CPQCH00) REQ(RO72734) .















SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CGENH00)


SUP ( RO70026 ZDAM052 )

++IF FMID(CDASH00) REQ(RO72726) .






















SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPDAH00)


RO65301 RO67887 )

SUP ( RO64322 ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPFCH00)

PRE ( RO56706 RO58057 RO58595 RO61030 )

SUP ( ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPFUH00)


RO66659 )

SUP ( ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPUTH00)

PRE ( RO55773 RO56715 RO58067 RO58608 RO61039 )

SUP ( ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CUGRH00)


RO63732 RO64415 RO66432 RO70109 )

SUP ( RO59907 ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPUOH00)

PRE ( RO56195 )

SUP ( ZDAM052 )























SYMPTOMS:


IMPACT:



CIRCUMVENTION:










Star Problem(s):

PDA 1259



++VER (Z038)

FMID (CPQCH00)


RO66767 )

SUP ( RO62119 RO68804 ZDAM052 )













ISQL EXPLAIN FORMATING


IN CA INTERACTIVE SQL FACILITY'S (ISQL) INTERFACE TO THE CA PLAN ANALYZER

for DB2 for z/OS (PPA) Explain facility through the primary command EXPLAIN

formatting of the SQL statement(s) provided was unintentionally occurring.

SYMPTOMS:

Formatting of the SQL statement(s) in ISQL when using the primary command

EXPLAIN.

IMPACT:

SQL is unintentionally rearranged.

CIRCUMVENTION:

None.





Star Problem(s):

PAS 212


DESC(ISQL EXPLAIN FORMATING) .

++VER (Z038)

FMID (CPPAH00)


SUP ( ZPSL023 )





RMA907E NATIVE SP ANALYSIS FAILS WITH ASSERTION


In CA RC/Migrator for DB2 for z/OS (RCM), migration analysis of a native SQL

stored procedure fails with assertion.

SYMPTOMS:

The migrate process for a native SQL stored procedure fails with the

following errors and assertion.

RMA907E OFS ERROR IN THE MODULE RMA@UF2 AND RETURN CODES ARE:

R15=00000014 R0=0000000C R1=00000054

MIGRATOR ANALYSIS COMPLETED, RETURN CODE = 16

Assertion failed: iStartOffset < getData()->nDataLength file

//'SQAPROD.SLRI LJ EY.SYSIN(OFSTR)'

OFS0001E - ExtractPrimaryKeys IEPAddObject failed.

IMPACT:

The migration process cannot be completed for native SQL stored procedure.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED: Object Framework Services Release 17.0

RC Migrator Release 17.0

RC Query Release 17.0

Star Problem(s):

OFS 522


DESC(RMA907E NATIVE SP ANALYSIS FAILS WITH ASSERTION) .

++VER (Z038)

FMID (COFSH00)


RO58723 RO59115 RO67378 RO70403 RO70459 )

SUP ( HOFF003 RO71913 ZOFF113 )





S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS


CA Execution Manager for DB2 for z/OS (PXM) may abend with S0C4 in

module PXMZMVCC. This will prevent access to some CA Detector for DB2 for

z/OS (PDT), CA Subsystem Analyzer for DB2 for z/OS (PSA), and CA Thread

Termination/Dynamic ZPARM for DB2 for z/OS (PTT) displays when the DB2

subsystem is remote.

SYMPTOMS:

A symptom dump appears in the Xmanager log, reporting a S0C4 abend in

load module PXMZMVCC.

After the S0C4 abend occurs, an ISPF error message reading "Cross system

error Sysplex Support Inactive" may appear on the PDT, PSA, or PTT

main menu.

IMPACT:

The S0C4 abend will prevent access to some PDT, PSA, and PTT displays

when the DB2 subsystem is remote.

CIRCUMVENTION:

The Xmanager incurring the S0C4 abend must be restarted.





Execution Manager Release 15.0



Subsystem Analyzer Release 15.0






Star Problem(s):

PXM 165


DESC(S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS) .

++VER (Z038)

FMID (CPXMH00)

PRE ( RO70758 )

SUP ( ZXMM010 )

++HOLD (RO72816) SYSTEM FMID(CPXMH00)


COMMENT (

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

| Execution Manager Release 17.0 |

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


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


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




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




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


|REQUIRED | |

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

| | |




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


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






Note:






).





INVALID DROP VERSIONING ON HISTORY TABLE


In CA RC/Migrator for DB2 for z/OS (RCM), a Compare strategy generates

an ALTER of a history table with DROP VERSIONING.

SYMPTOMS:

The Compare generates the following ALTER of a history table:

ALTER TABLE <history table>

DROP VERSIONING;

Executing the DDL results in the following:

DSNT408I SQLCODE = -20525, ERROR: THE REQUESTED ACTION IS NOT VALID

FOR TABLE <history table> BECAUSE THE TABLE IS THE WRONG TYPE

OF TABLE. REASON CODE = 4

IMPACT:

The generated DDL is invalid.

CIRCUMVENTION:

The DDL can be edited to remove the ALTER.



Star Problem(s):

RCM 2616


DESC(INVALID DROP VERSIONING ON HISTORY TABLE) .

++VER (Z038)

FMID (CRCMH00)


SUP ( RO58730 RO59063 RO66729 RO66791 ZRMM337 )






INVALID DROP VERSIONING ON HISTORY TABLE


In CA RC/Migrator for DB2 for z/OS (RCM), a Compare strategy generates

an ALTER of a history table with DROP VERSIONING.

SYMPTOMS:

The Compare generates the following ALTER of a history table:

ALTER TABLE <history table>

DROP VERSIONING;

Executing the DDL results in the following:

DSNT408I SQLCODE = -20525, ERROR: THE REQUESTED ACTION IS NOT VALID

FOR TABLE <history table> BECAUSE THE TABLE IS THE WRONG TYPE

OF TABLE. REASON CODE = 4

IMPACT:

The generated DDL is invalid.

CIRCUMVENTION:

The DDL can be edited to remove the ALTER.



Star Problem(s):

RCM 2616


DESC(INVALID DROP VERSIONING ON HISTORY TABLE) .

++VER (Z038)

FMID (CRCOH00)

PRE ( RO58958 RO62307 RO63120 RO65663 RO70547 )

SUP ( ZRMM337 )






TASK COUNT INCORRECT


If the maximum number of tasks is limited and mutiple data movers

need to be used within a single copy operation, if DFSMSdss is one of

those data movers, it is possible that the number of tasks reserved

for DFSMSdss will be set to zero. This correction ensures there is

one task reserved for DFSMSdss.

SYMPTOMS:

The number of tasks displayed may not match the actual number of

tasks being used.

IMPACT:

The number of tasks in use may not be the quatity expected.

CIRCUMVENTION:

None








Star Problem(s):

TGR 248


DESC(TASK COUNT INCORRECT) .

++VER (Z038)

FMID (CTGRH00)

PRE ( RO56138 RO64049 )

SUP ( ZTGK014 )





CATALOG UPDATE INDEX CREATOR %

CA Database Analyzer for DB2 for z/OS (PDA) online Catalog Update

selection panel may require a DB2 wildcard (%) for some indexes.

This happens when the index was created prior to v8 NFM and during

DB2 migration, the SYSIBM.SYSINDEXES fields were padded with spaces

when the creator name was less than 8 bytes in length.

IMPACT:

The index is not found, so catalog update is not available.

SYMPTOMS:

SYSIBM.SYSINDEXES(CREATOR) has a length of 8 for creator names less

than 8 bytes with padded spaces. This occurs when migrating from

DB2 7 or less, to DB2 8 or greater where CREATOR data type changes

from CHAR 8 to VARCHAR 128.

CIRCUMVENTION:

Use wildcard at end of field (%)

PRODUCTS AFFECTED:

PDA 17.0.0+

Star Problem(s):

PDA 1262


DESC(CATALOG UPDATE INDEX CREATOR %) .

++VER (Z038)

FMID (CPDAH00)

PRE ( RO58593 RO70817 )

SUP ( ZDAM054 )





DISPLAY INTERNAL OBJECT STATUS FLAGS


This PTF provides a diagnostics summary report of the final object

status flags for the CA Fast Load for DB2 for z/OS (PFL) product when

keyword ALLMSGS is set. This report is generated to assist CA customer

support to analyze final object status settings for index and table spaces

at the end of the load. The output is routed to PTIIMSG dataset.

SYMPTOMS:

None

IMPACT:

Additional diagnostic info is written to PTIIMSG output.

None

CIRCUMVENTION:

None



Star Problem(s):

PFL 1084


DESC(DISPLAY INTERNAL OBJECT STATUS FLAGS) .

++VER (Z038)

FMID (CPFLH00)


RO66538 )

SUP ( RO56788 ZFLM047 )





PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION


CA Fast Load for DB2 for z/OS (PFL) can encounter a ZPARM

page protection error:

PUT4304E APPLICATION LACKS APF AUTHORITY and

PFL0082E - Updating SYSCOPY failed - NO RESTART for this function

when attempting to set a ZPARM to allow an update of SYSCOPY.

SYSTABLEPART, SYSINDEXPART or SYSTABLESPACE catalog updates, within the load

process can also be impacted.

SYMPTOMS:

The load completes. Return Code 20 is displayed if a SYSCOPY update

is attempted. If another catalog update is attempted, the return code

can be 4 or 0. In all cases a SNAP DUMP is returned.

The following messages are displayed:

From the PTIMSG output:

For SYSCOPY update:

PUT4304E APPLICATION LACKS APF AUTHORITY


is displayed.

The snap dump output contains the following:

ERLY Block - First pass

2B3ECF40 00A50

2B3ECF60 C4E2D540 C4E2D5D4 E2E3D940 00180200 2B3ECD58 207E4F40 00000

...

IMPACT:

The load completes but a system catalog update(s) are not completed.

CIRCUMVENTION:

NONE

PRODUCT(S) AFFECTED: PFL Release 16.0

Release 17.0

Star Problem(s):

PFL 1112


DESC(PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION) .

++VER (Z038)

FMID (CCOMH00)

SUP ( RO69047 ZFLM069 )





INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET


CA Fast Load for DB2 for z/OS (PFL) can overlay its input dataset when

INDDN SYSREC is specified during an OUTPUT-CONTROL ALL

execution and UNLDDN is not specified.

The default DDNAME for the unload dataset is SYSREC so when

INDDN SYSREC is specified and UNLDDN is not, the data is read from

the SYSREC dataset and the unload information is written back

to the SYSREC dataset.

SYMPTOMS:

The load completes. There is no indication that SYSREC information

has been overlaid until the SYREC dataset name is reloaded.

In that case PFL can fail with discard errors.

PFL0806I - Conversion rejects ..................n,nnn

IMPACT:

The load completes. The original input data is lost.

CIRCUMVENTION:

When INDDN SYSREC is specified make certain UNLDDN is also specified

with a different DDNAME.


Release 17.0

Star Problem(s):

PFL 1113


DESC(INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET) .

++VER (Z038)

FMID (CPFLH00)


RO61032 RO61764 RO64053 RO64313 RO64874 RO65973

RO69238 RO71065 RO72694 )

SUP ( ZFLM070 )


REASON (DOC ) DATE (14232)

COMMENT (

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

| Fast Load Release 17.0 |

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

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

* PUBLICATION *

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

Holddata

With the implementaion of this PTF, PFL will now terminate

if INDDN SYSREC for OUTPUT-CONTROL ALL is specified and

UNLDDN is not. This is implemented to prevent input data

from being overlayed.

xmessage PFL1112E will display for this circumstance.

PFL1113E - INDDN and UNLDDN specify the same data set name: SYSREC

Fast Load is terminating.

Change the INDDN or UNLDDN name and resubmit.

).



COMMENT (

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


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


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


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

|USERS | |





|KNOWLEDGE | |


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



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

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


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








).





VREX ABEND TS COLLECTION TASK DB2 11 ALTER DROP COLUMN



collection subtask may abend with a U811 before the collection

completes. This can occur when the table of the tablespace in the

abending collection subtask has had one or more ALTER TABLE DROP

COLUMN EXECUTED *AND* THEN THE TABLESPACE REORG'D.

ALTER drop column was introduced in DB2 11 for z/OS in NFM.

SYMPTOMS:

Stats collection subtask abends with a U811. Example message in PTIMSG:

Collection of TS - <dbname>.<tsname> - RC0811

When run in batch messages are written to the job log that contain

object identification information. Here is an example format of those

messages:

CA VREX: Error occurred while processing DBID=xxxxx PSID=xxxxx TBID=xxxx

CA VREX: DBNAME=<dbname> TSNAME=<tsname>

CA VREX.BLD: Unknown from/to column data type pair !!!

A S0C4 in RALMCTL at offset x73A0 may also occur, but note this is a

byproduct of the U811.

IMPACT:

Statistics collection for the specified tablespace(s) is incomplete.

The stats collection for the remaining objects will continue.

CIRCUMVENTION:

None.


PDA Database Analyzer Release 17.0

Star Problem(s):

PDA 1261


DESC(VREX ABEND TS COLLECTION TASK DB2 11 ALTER DROP COLUMN) .

++VER (Z038)

FMID (CDASH00)


SUP ( RO63504 RO64311 ZDAM053 )















SYMPTOMS:





messages:






IMPACT:



CIRCUMVENTION:

None.



Star Problem(s):

PDA 1261



++VER (Z038)

FMID (CGENH00)

PRE ( RO61277 )

SUP ( RO68952 ZDAM053 )















SYMPTOMS:





messages:






IMPACT:



CIRCUMVENTION:

None.



Star Problem(s):

PDA 1261



++VER (Z038)

FMID (CPDAH00)

PRE ( RO55765 RO58593 )

SUP ( ZDAM053 )







ROAAL1T INTERNAL ERROR 01 IF TIMESTAMP INCLUDED IN LIMIT KEY


CA RC/Compare for DB2 for z/OS (RCC) will not generate DDL to add a

new partition or alter an existing partition if the following conditions

are true:

1) The compare strategy is an AUTOMAP or DDL-SSID.

2) The source limit key values for timestamp columns are specified

without the fraction of seconds.

SYMPTOMS:

-- ROAAL1T internal error 01

-- INVALID LENGTH FOUND FOR TIMESTAMP TYPE.

IMPACT:

DDL will not be generated to add a new partition or

to alter an existing partition.

CIRCUMVENTION:

None.


RC/Compare Release 17.0

Star Problem(s):

RCC 636


DESC(ROAAL1T INTERNAL ERROR 01 IF TIMESTAMP INCLUDED IN LIMIT KEY) .

++VER (Z038)

FMID (CCOMH00)

SUP ( ZRMM338 )





EXPLAIN RUNS UNDER DATA COLLECTOR SECURITY INSTEAD OF USER


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

that perform the EXPLAIN function, whose security profile specifies

the security parm EXPLAIN=DC, may have the EXPLAIN run under

the authority of the data collector rather than the individual.

The problem also applies to the EXPLAIN=ALL security profile setting, when

RAF or the VTAM UI is being used.

SYMPTOMS:

EXPLAIN may fail if the data collector user ID is not authorized to

do an EXPLAIN.

EXPLAIN may succeed for users who are not permitted to perform the

function, if the data collector user ID is authorized to do an

EXPLAIN.

IMPACT:

Incorrect authorization check for EXPLAIN.

CIRCUMVENTION:

Use EXPLAIN=TSO which requires a TSO non-RAF connection, or use the

EXPLAIN-AUTHID= sysparm to assign a specific user to all non-TSO EXPLAINs.





Star Problem(s):

IDB2 1691


DESC(EXPLAIN RUNS UNDER DATA COLLECTOR SECURITY INSTEAD OF USER) .

++VER (Z038)

FMID (CCIDH00)


SUP ( ZDBK151 )






EXPLAIN RUNS UNDER DATA COLLECTOR SECURITY INSTEAD OF USER


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

that perform the EXPLAIN function, whose security profile specifies

the security parm EXPLAIN=DC, may have the EXPLAIN run under

the authority of the data collector rather than the individual.

The problem also applies to the EXPLAIN=ALL security profile setting, when

RAF or the VTAM UI is being used.

SYMPTOMS:

EXPLAIN may fail if the data collector user ID is not authorized to

do an EXPLAIN.

EXPLAIN may succeed for users who are not permitted to perform the

function, if the data collector user ID is authorized to do an

EXPLAIN.

IMPACT:

Incorrect authorization check for EXPLAIN.

CIRCUMVENTION:

Use EXPLAIN=TSO which requires a TSO non-RAF connection, or use the

EXPLAIN-AUTHID= sysparm to assign a specific user to all non-TSO EXPLAINs.





Star Problem(s):

IDB2 1691


DESC(EXPLAIN RUNS UNDER DATA COLLECTOR SECURITY INSTEAD OF USER) .

++VER (Z038)

FMID (CIDBH00)


RO72657 )

SUP ( RO61588 ZDBK151 )






ALTER INDEX HELP PANEL DOES NOT LIST INCLUDE FOR ORDER FIELD


When altering an index in CA RC/Migrator for DB2 for z/OS (RCM), the

help information for the ORDER field does not list

the INCLUDE option.

SYMPTOMS:

When displaying the Index Alter/Create help information for

the ORDER field, the INCLUDE option is not listed in the description.

This is panel ROHIXCLD.

IMPACT:

The ORDER field description is not complete.

CIRCUMVENTION:

None.



Star Problem(s):

RCM 2617


DESC(ALTER INDEX HELP PANEL DOES NOT LIST INCLUDE FOR ORDER FIELD) .

++VER (Z038)

FMID (CRCOH00)

SUP ( ZRMM339 )





MISSING GETPAGES FOR PARALLEL TASKS EXECUTED UNDER DISTSERV


CA Detector for DB2 for z/OS (PDT) may not collect all the getpages for the

requests run with CPU parallelism. Also with the Synchronized PDT/PSA

collection, on the DETECTOR Table SQL Activity Display, the SQL CALL type of

UNKNOWN may be displayed in the Active interval for the parallel tasks

executed under Distserv Plan.

SYMPTOMS:

For the Parallel tasks executed under Distserv Plan, the following symtoms

may occur.

1) On the DETECTOR Table SQL Activity Display SQLCALL type of UNKNOWN may be

displayed instead of OPEN.

2) The Getpage count reported on the DETECTOR Plan Program Display may be

higher than the getpage count on the Plan SQL Display.

IMPACT:

1) Missing or incorrect getpage count under Detector activity display.

2) Incorrect SQL call Type for synchronized PDT/PSA collection.

CIRCUMVENTION:

None.


Star Problem(s):

PDT 1207


DESC(MISSING GETPAGES FOR PARALLEL TASKS EXECUTED UNDER DISTSERV) .

++VER (Z038)

FMID (CPDTH00)


RO61138 RO62524 RO65437 RO65579 RO65920 RO66064

RO66129 RO66619 RO68135 RO68244 RO68455 RO69879

RO69977 RO70539 RO70631 RO71707 RO71883 RO71894

RO72235 )

SUP ( RO69266 RO70948 ZDTM098 )


REASON (RESTART) DATE (14233)

COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Release Service Details3. Update the runtime library.


Note:






).





DSG DATASTORES NOT SORTED BY DATE AND TIME


CA Detector for DB2 for z/OS (PDT) does not properly sort datastores by

LAST DATE / LAST TIME when viewing historical data sharing datastore

displays. This problem occurs when the date format is not specified as

YYYY-MM-DD or YYYY/MM/DD in the SETUP member of the parmlib dataset.

SYMPTOMS:

Under PDT option 10 - DS Group historical interval data, datastores are not

listed by the date/time they were last used and the date format in use is

not YYYY/MM/DD or YYYY-MM-DD.

IMPACT:

The most recently used datastore is not always listed first.

CIRCUMVENTION:

Change the SETUP member of the parmlib dataset to use a date format of

YYYY/MM/DD or YYYY-MM-DD.


CA Detector Release 17.0

Star Problem(s):

PDT 1217


DESC(DSG DATASTORES NOT SORTED BY DATE AND TIME) .

++VER (Z038)

FMID (CPDTH00)

PRE ( RO58819 RO72113 )

SUP ( ZDTM099 )





SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM


An analysis in CA RC/Migrator for DB2 for z/OS (RCM) ends with

SQLCODE -518 when ACM is used and procedures are in the strategy.

SYMPTOMS:

The analysis ends with SQLCODE -518 in RMA@UF2.

IMPACT:

The analysis does not complete.

CIRCUMVENTION:

Run analysis without using ACM.



Star Problem(s):

RCM 2613


DESC(SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM) .

++VER (Z038)

FMID (CRCMH00)


SUP ( ZRMM336 )

++HOLD (RO72923) SYSTEM FMID(CRCMH00)


COMMENT (

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


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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).





SHRLEVEL CHANGE,BPLOOKUP, SYSADM X SET, AUTHORIZATION ERRORS


CA Fast Unload job failed because of insufficient authority to use

DB2 checkpoint and log resources for buffer pool lookup processing

when a valid SYSADM value was coded in the PFU syntax and that DB2

userid had been granted the proper authority.

SYMPTOMS:

The following messages were received as a result of processing:

GENCK05E - PTLGCHKP Log Reader OPEN failed.

IFI READS H call failed, IFCARC2 = 00E60824

ID USED FOR DB2 ACCESS = 'XXXXXXX ' FETCH FOR HIGH LRSN FAILED

IMPACT:

The PFU execution failed, ending in Return code 8. Processing of

all SELECT statements were impacted by this failure.

CIRCUMVENTION:

None.





Star Problem(s):

PFU 915


DESC(SHRLEVEL CHANGE,BPLOOKUP, SYSADM X SET, AUTHORIZATION ERRORS) .

++VER (Z038)

FMID (CPFUH00)


RO58342 RO58599 RO58870 RO58918 RO58954 RO59286

RO59839 RO59908 RO61015 RO61034 RO61046 RO61583

RO61629 RO62178 RO62300 RO62357 RO63116 RO64168

RO65974 RO67487 RO72730 )

SUP ( HFUM001 HFUM002 HFUM003 RO56575 RO56658 RO56666

RO56687 RO56928 RO57162 RO57175 RO57178 RO57198

RO57544 RO58034 RO58139 RO58203 RO58868 RO59764

RO59911 RO60420 RO60855 RO60929 RO61054 RO61060

RO61573 RO61628 RO61761 RO62484 RO62974 RO63363

RO63889 RO64175 RO64295 RO64636 RO64813 RO65122

RO65351 RO65637 RO66487 RO66511 RO66659 RO67488

RO68061 RO68077 RO68186 RO68298 RO69088 RO69291

RO69294 RO69400 RO69424 RO69922 RO70164 RO70350

RO72276 RO72703 RO72707 ZFUM099 )

++IF FMID(CPLRH00) REQ(RO72927) .





SHRLEVEL CHANGE,BPLOOKUP, SYSADM X SET, AUTHORIZATION ERRORS


CA Fast Unload job failed because of insufficient authority to use

DB2 checkpoint and log resources for buffer pool lookup processing

when a valid SYSADM value was coded in the PFU syntax and that DB2

userid had been granted the proper authority.

SYMPTOMS:

The following messages were received as a result of processing:

GENCK05E - PTLGCHKP Log Reader OPEN failed.

IFI READS H call failed, IFCARC2 = 00E60824

ID USED FOR DB2 ACCESS = 'XXXXXXX ' FETCH FOR HIGH LRSN FAILED

IMPACT:

The PFU execution failed, ending in Return code 8. Processing of

all SELECT statements were impacted by this failure.

CIRCUMVENTION:

None.





Star Problem(s):

PFU 915


DESC(SHRLEVEL CHANGE,BPLOOKUP, SYSADM X SET, AUTHORIZATION ERRORS) .

++VER (Z038)

FMID (CPLRH00)

SUP ( ZFUM099 )


++HOLD (RO72927) SYSTEM FMID(CPLRH00)


COMMENT (

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

| Log Reader Release 17.0 |

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

|SEQUENCE | Before using PFU |

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

|PURPOSE | To implement PLR portion of this fix. |

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

|USERS | |

|AFFECTED | All users. |

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

|KNOWLEDGE | |

|REQUIRED | Ability to restart the relevant XMAN subsystem |

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

|ACCESS | |

|REQUIRED | Ability to restart the relevant XMAN subsystem |

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

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


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

Restart XMAN related to DB2 subsystem being used by the PFU in question.

CA does not recommend or support applying this

maintenance to any load library on the STEPLIB or

PTILIB concatenation for an Xmanager address space

while the address space is active. If you are

executing the Xmanager address space directly from

your SMP target load libraries then only apply

maintenance while the Xmanager address space is

inactive.

Applying this maintenance to an executing Xmanager



Release Service Detailsaddress space may result in a discrepancy between

components that are loaded for the life of the

Xmanager address space and dynamically loaded

components that may result in unpredictable behavior

or compromise DB2 subsystem integrity.

).





IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS


CA Fast Unload for DB2 for Z/OS (PFU) may experience a lack of

region type of failure when using a SYSIN with the number of SELECT

statements including a WHERE clause exceeds 147 and there is at least

two or more columns referenced inside the WHERE clause of each

SELECT statement. The number of SELECT statements containing WHERE

clauses PFU is able to handle could be smaller than 147 based on the

content in the WHERE clause(s). The greater the number of columns and

conditions in the WHERE clause, the smaller number of SELECT statements

PFU can safely process.

SYMPTOMS:

PFU may abend with a S106, S806, S878 or other type of lack of

available region failure.

IMPACT:

The job fails without unloading the requested data.

CIRCUMVENTION:

Reduce the number of SELECT atatements containing WHERE clauses

referencing 2 or more columns each to a number less than 147.


Release 17.0

Release 18.0

Star Problem(s):

PFU 918


DESC(IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS) .

++VER (Z038)

FMID (CPFUH00)


RO59839 RO64636 RO65974 RO68061 RO72926 )

SUP ( ZFUM102 )





PUT0910E QUIESCE FAILED


CA Fast Load for DB2 for z/OS (PFL), CA Fast Unload for DB2 for

z/OS (PFU), CA Rapid Reorg for DB2 for z/OS (PRR), CA Quick Copy for DB2

for z/OS (PQC), CA Fast Check for DB2 for z/OS (PFC), CA Fast Recover

for DB2 for z/OS (PFR) and all CA utilities common for DB2 for z/OS

(PUT) that are calling the DSNUTILB might end with an OPEN TASKLIB ERROR

when there are about 1700 JCL DD statements specified on the step level

(LENGTH OF TIOT > X'7FFF')

SYMPTOMS:

The called IBM utility is NOT executed

JESMSGLG shows entries as below

IEC130I "* q DD STATEMENT MISSING

and Abends with S378-14 (for PFR)

PTIMSG shows messages as below

PUT0910E - RUNSTAT failed on OPEN to TASKLIB (PRR update-catalog RSDT)

PUT0910E - QUIESCE failed on OPEN to TASKLIB (PQC or QUIESCE)

nothing for PFR

IMPACT:

The called IBM utility was NOT executed

CIRCUMVENTION:

Reduce the number of DD statements in the step


Utilities Common Release 16.0



Star Problem(s):

PUT 730


DESC(PUT0910E QUIESCE FAILED) .

++VER (Z038)

FMID (CCOMH00)

SUP ( ZUTM053 )















SYMPTOMS:








nothing for PFR

IMPACT:


CIRCUMVENTION:






Star Problem(s):

PUT 730



++VER (Z038)

FMID (CPUTH00)


SUP ( ZUTM053 )

++IF FMID(CCOMH00) REQ(RO72976) .





S0C4 ABEND CANCELING THREAD VIA INSIGHT OR OPTION 6 IN PTT


A S0C4 abend may occur within CA Thread Termination/Dynamic ZPARM for

DB2 for z/OS (PTT) when an attempt to cancel a DB2 thread is made via

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

or the "6 Terminate pageset users" option on the PTT main menu.

SYMPTOMS:

Messages similar to the following may appear:

PXM0811 PSW: 078C2000 B75AED96 LMOD: *UNKNOWN OFFSET: N/A ABEND: S0C4

PTT1104E ABEND OCCURRED PROCESSING REQUEST. RC=000C4000-00000010.

IMPACT:

The DB2 thread is not canceled.

CIRCUMVENTION:

None.



Star Problem(s):

PTT 318


DESC(S0C4 ABEND CANCELING THREAD VIA INSIGHT OR OPTION 6 IN PTT) .

++VER (Z038)

FMID (CPTTH00)


SUP ( ZTTM023 )

++HOLD (RO73014) SYSTEM FMID(CPTTH00)


COMMENT (

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

| Thread Terminator Release 17.0 |

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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:







Release Service Detailsoperating system/DB2 including possible failure.

).





SQL007 FOR PARSING SELECT FROM DELETE SYNTAX


The CA Database Management Solutions for DB2 for z/OS (PAS) SQL Parser

would incorrectly generate parse errors for valid SQL with SELECT from DELETE

syntax when WHERE clause apply to SELECT clause:

The following SQL contains an example of this syntax:

SELECT * FROM OLD TABLE ( DELETE FROM SYSIBM.SYSTABLES_HIST )

WHERE CREATOR = 'XXXXXXXX'

SYMPTOMS:

Parse error is generated for valid SQL containing SELECT from DELETE syntax:

SQL007: A left parenthesis has been found without a

matching right parenthesis.

IMPACT:

Any CA DB2 tool which attempts to parse SQL containing the above syntax

may be affected by this problem.

CIRCUMVENTION:

None.






Star Problem(s):

PAS 206

SQL294 ERROR ON VALID SQL


In CA Plan Analyzer Services for DB2 for z/OS (PAS), the SQL

Parsing Service has the potential to generate a parse error

SQL294 for valid SQL similar to the following example:

WITH TABLE (NAME ) AS (SELECT * FROM TABLE )

SELECT * FROM SYSIBM.SYSTABLES (NAME, CREATOR)

WHERE CREATOR = 'SYSIBM'

SYMPTOMS:

Parse error SQL294.

IMPACT:

Low.

CIRCUMVENTION:

None.





PAS 210


DESC(SQL007 FOR PARSING SELECT FROM DELETE SYNTAX) .

++VER (Z038)

FMID (CPASH00)

PRE ( RO64773 RO71836 )

SUP ( HPSL001 RO66874 RO72173 RO72611 ZPSL019 ZPSL021 )





S0C4 IN MODULE PTLGCHKP/PTLGCHKA/PTLGCHK9


The CA DB Tools for DB2 for z/OS General Checkpoint log record service

may encounter a S0C4 abend in one of the following modules: PTLGCHKP,

PTLGCHKA, PTLGCHK9. Alternately, the service may fail to report on

members of the group past a certain memid.

This occurs in one of the following conditions:

1) One or more members of the group have been permanently

quiesced and their Boot Strap Data Sets have been deleted.

2) One or more members of the group have been permanently

quiesced and their Active Log data sets have been deleted.

3) One or more members of the group have been deleted using

the DELMBR option of DSNJU003.

SYMPTOMS:

The job may encounter a S0C4 in one of the above mentioned modules.

Otherwise, the service will not return checkpoint information for

members with memids larger than the count of remaining members

not in one of the above three states.

For example, on a 12-way data sharing system with members one, two

and five permanently quiesced, checkpoint information will not be

returned for members ten, eleven, or twelve.

IMPACT:

If using CA Fast Unload for DB2 for z/OS with BP-LOOKUP, the resultant

output may not contain transactions that were inflight on the lost

members.

If using CA Quick Copy for DB2 for z/OS with SHRLEVEL CHANGE, the

START_RBA generated for the image copy may not reflect transactions

that were inflight on the lost members.

CIRCUMVENTION:

None.


General Services Release 15.0









Star Problem(s):

GEN 1216


DESC(S0C4 IN MODULE PTLGCHKP/PTLGCHKA/PTLGCHK9) .

++VER (Z038)

FMID (CGENH00)

PRE ( RO57940 RO58869 )

SUP ( ZGEM062 )





PTLOG DATE AND TIME VALUES INCORRECT FOR ASCII TABLES.


CA RC/Update for DB2 for z/OS (RCU) updates the CA PTLOG tables for each

action when RC/Edit or RC/Browse logging has been enabled. When editing or

browsing an ASCII table the data inserted into column LOG_TIMESTAMP of the

PTLOG table is invalid.

SYMPTOMS:

The PTI.PTLOG_MAIN_1500 table contains invalid data in the LOG_TIMESTAMP

column which is displayed as dots.

LOG_USER LOG_TIMESTAMP LOG_ID LOG_TYPE LOG_FUNCTION

USER_ID ........10320334 RCUPDATE TABLE EDIT


USER_ID ........00541187 RCUPDATE TABLE BROWSE


USER_ID ........01010668 RCUPDATE TABLE BROWSE


IMPACT:

The data cannot be used for auditing purpose.

CIRCUMVENTION:

None.

Star Problem(s):

RCU 1024


DESC(PTLOG DATE AND TIME VALUES INCORRECT FOR ASCII TABLES.) .

++VER (Z038)

FMID (CRCUH00)

PRE ( RO67720 )

SUP ( ZRUM050 )





COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED


CA Log Analyzer for DB2 for z/OS (PLA) DML Summary reports may report

Commit Status of unit of recovery (UR) as Committed even if it was rolled

back. This happens only on data sharing systems.

SYMPTOMS:

ABORTED UR'S ARE REPORTED AS COMMITTED.

IMPACT:

Reported Commit Status on data sharing systems may be incorrect.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED: PLA Release 17.0

PLA Release 16.0

Star Problem(s):

PLA 1157


DESC(COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED) .

++VER (Z038)

FMID (CPLAH00)


RO58983 RO59781 RO60892 RO62195 RO62208 RO63083

RO63318 RO64158 RO64765 RO67452 RO67908 RO67942

RO69217 RO69219 RO69840 RO69872 RO70256 RO71489

RO71502 RO72215 )

SUP ( RO57187 RO63163 RO63605 RO69051 RO70122 ZLAM060

ZLAM105 )





IMAGE COPY STATUS REPORT EXTENDED LOGGING SUPPORT


CA Log Analyzer for DB2 for z/OS (PLA) Image Copy Status Report displays

incorrect values on DB2 11 subsystems that have been converted to use

extended RBA/LRSN.

SYMPTOMS:

Image Copy Status Report job ends with RC=0 but the reported log points

(RBA or LRSN) are truncated.

IMPACT:

Incorrect data in the report.

CIRCUMVENTION:

None.



Star Problem(s):

PLA 1158


DESC(IMAGE COPY STATUS REPORT EXTENDED LOGGING SUPPORT) .

++VER (Z038)

FMID (CPLAH00)


RO58360 RO58362 RO58983 RO59781 RO59863 RO60892

RO62195 RO62208 RO63083 RO63370 RO64158 RO64183

RO67344 RO67452 RO67908 RO67942 RO69219 RO69840

RO70256 RO70973 )

SUP ( ZLAM106 )

++HOLD (RO73077) SYSTEM FMID(CPLAH00)


COMMENT (

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

|Log Analyzer Version 17.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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








).





ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10


CA Rapid Reorg for DB2 for z/OS (PRR) does not HONOR KEEPDICTIONARY

even though the ZPARM HONOR KEEPDICTIONARY is SET to YES

and the following conditions are in effect.

1) The tablespace is compressed and KEEPDICTIONARY is specified.

2) DATA-AVAILABLE CRITICAL or HIGH is specified

3) the tablespace is created under DB2 VERSION 10 or higher

SYMPTOMS:

The ROWFORMAT option is specified and the ZPARM HONOR KEEPDICTIONARY

is YES and KEEPDITIONARY is in effect.

the following messages are displayed:

PRR0600I - ROWFORMAT RRF/BRF Request - will ignore KEEPDICTIONARY for

- Partition = 0001

PRR0811I - Tablespace DSN8D91Z.A0AORDTE.0001 - Dictionary Statistics

PRR0940I - Dictionary: Built, Entries ..............4,096

PRR0941I - Pages ...................16

IMPACT:

The REORG ignores KEEPDICTIONARY even though it

is specified.

CIRCUMVENTION:

NONE

PRODUCT(S) AFFECTED: PRR Release 16.0

Release 17.0

Star Problem(s):

PRR 1170


DESC(ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10) .

++VER (Z038)

FMID (CCOMH00)

PRE ( RO61762 )

SUP ( ZRRM047 )

++IF FMID(CPRRH00) REQ(RO73098) .





ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10


CA Rapid Reorg for DB2 for z/OS (PRR) does not HONOR KEEPDICTIONARY

even though the ZPARM HONOR KEEPDICTIONARY is SET to YES

and the following conditions are in effect.

1) The tablespace is compressed and KEEPDICTIONARY is specified.

2) DATA-AVAILABLE CRITICAL or HIGH is specified

3) the tablespace is created under DB2 VERSION 10 or higher

SYMPTOMS:

The ROWFORMAT option is specified and the ZPARM HONOR KEEPDICTIONARY

is YES and KEEPDITIONARY is in effect.

the following messages are displayed:

PRR0600I - ROWFORMAT RRF/BRF Request - will ignore KEEPDICTIONARY for

- Partition = 0001

PRR0811I - Tablespace DSN8D91Z.A0AORDTE.0001 - Dictionary Statistics

PRR0940I - Dictionary: Built, Entries ..............4,096

PRR0941I - Pages ...................16

IMPACT:

The REORG ignores KEEPDICTIONARY even though it

is specified.

CIRCUMVENTION:

NONE

PRODUCT(S) AFFECTED: PRR Release 16.0

Release 17.0

Star Problem(s):

PRR 1170


DESC(ROWFORMAT WITH KEEPDICTIONARY FAILS TO KEEPDICTIONARY DB V10) .

++VER (Z038)

FMID (CPRRH00)


RO61026 RO61038 RO61048 RO61768 RO62800 RO63131

RO64785 RO65325 RO69244 RO69855 RO70704 RO71407 )

SUP ( RO58073 RO59629 ZRRM047 )

++IF FMID(CCOMH00) REQ(RO73097) .





S0C4 ABEND NSIGHTRW IF TRACE RECORD HAS ZERO DATA SECTIONS


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

report writer NSIGHTRW may receive an ABEND S0C4 in module NDREFORC

if the IFI trace record contains no data sections.

SYMPTOMS:

The following messages will appear in the DBGPRINT log:

DBG11017I 08:02:53 ESTAE EXIT IN NBRWDRV INVOKED BY ABEND

ABEND CODE IS 840C4000 - EC PSW AT ABEND IS 078D2000 999827A6 - P

ILC, INTERRUPT CODE 00020010 - TRANSLATE EXCEP 1A3FF400 - PROGRAM

EYECATCHER POINTED BY R12 - NBRWDRVM 03/13/14 18.32. + 0

OFFSET TO ABEND ADDRESS FROM R12 IS 0017E196

R0 1A3FF107 R1 000360C8 R2 00000018 R3 1A3FF107

R4 19D9981E R5 19E9F01C R6 199A6E80 R7 19D996BE

R8 19CECEF8 R9 19E9F000 R10 0003A000 R11 0003C000

R12 19804610 R13 00036000 R14 19D99838 R15 00000018

AR0 007F8030 AR1 00000000 AR2 00000000 AR3 00000000

AR4 00000000 AR5 00000000 AR6 00000000 AR7 00000000

AR8 00000000 AR9 00000000 AR10 00000000 AR11 00000000

AR12 00000000 AR13 00000000 AR14 00000000 AR15 01000002

EYECATCHER POINTED BY R12 - ENDDATA

IMPACT:

The batch report job fails.

CIRCUMVENTION:

None.





Star Problem(s):

IDB2 1697


DESC(S0C4 ABEND NSIGHTRW IF TRACE RECORD HAS ZERO DATA SECTIONS) .

++VER (Z038)

FMID (CCIDH00)


RO62338 RO63261 RO63688 RO64386 RO64774 RO65496

RO67673 RO68410 RO69402 RO70132 RO70410 RO71416

RO71764 RO72162 RO72499 RO72655 )

SUP ( RO62203 RO65887 ZDBK152 )





RU597E ON VARGRAPHIC DATA DISPLAY


CA RC/Update for DB2 for z/OS (RCU) does not display VARGRAPHIC data

correctly. The data present in the DB2 tables is correct but when using

RC/Browse, error RU597E is displayed and, the PF3 action is also affected.

SYMPTOMS:

On accessing a DB2 table with VARGRAPHIC column data, the following message

is displayed,

"RU597E: Data exceeds maximum column length"

IMPACT:

The data cannot be browsed.

CIRCUMVENTION:

None.

Star Problem(s):

RCU 1025


DESC(RU597E ON VARGRAPHIC DATA DISPLAY) .

++VER (Z038)

FMID (CRCUH00)

PRE ( RO58830 RO67720 RO68526 )

SUP ( RO69532 RO69845 ZRUM051 )





ENH:DATASTORE COMPATIBILITY ACROSS RELEASES


Xmanager component needed for the Datastore Compatibility feature.


Star Problem(s):

PXM 164



As a user we would like to see Detector datastore and profile dataset

compatibility across multiple releases of the product. This

compatibility should extend both upward and downward.

Some customers have several DB2 data sharing environments across

multiple LPARs. They upgrade products on an LPAR basis, so in many

cases they do not have DSGs, whose member being on different LPARS, are

using different releases of CA products.

This requires having to re-initialize these datasets which:

1) Extends and complicates the maintenance upgrade process, since

extra time is required for the initialization procedures.

2) Prevents developers from seeing Detector data for a member, when

that member is running a different CA Tools release than the

member from which the developer is executing the Detector product.

SYMPTOMS:

N/A

IMPACT:

How this would resolve their problem:

1) Shortens release/maintenance upgrade time.

2) Ensures that all Detector data for a Data Sharing Group is

accessible, regardless of the product code used to access that data

How important is this enhancement for most customers:

One customer indicated that this is extremely important due to they

have about 150 DB2 subsystems and with the workload they need to be

able to apply product upgrades in as short a time as possible with a

minimum of release incompatibility issues as possible.

CIRCUMVENTION:

N/A


PRODUCT(S) AFFECTED: XXX Release VV.R

PDT 1161



As a user we would like to see Subsystem Analyzer datastore and profile

datastore compatibility across multiple releases of the product. This












SYMPTOMS:

N/A

IMPACT:










Release Service Detailsable to apply product upgrades in as short a time as possible with a



This enhancement allows customers to collect and view Historical Data

across multiple releases of the products without the need for extended

and complicated setup in order to collect new data on a newer release

while still maintaining older release data in case of a fallback need.


PSA 406


DESC(ENH:DATASTORE COMPATIBILITY ACROSS RELEASES) .

++VER (Z038)

FMID (CPDTH00)


RO62137 RO63052 RO63053 RO65579 RO65748 RO65920

RO66064 RO66656 RO66707 RO66750 RO67018 RO67964

RO68135 RO68516 RO68555 RO69134 RO69172 RO69236

RO69879 RO69977 RO70501 RO70638 RO71275 RO71707

RO71883 RO72018 RO72138 RO72441 )

SUP ( RO67241 RO67505 RO70049 ZDTM095 ZSAM041 ZXMM011 )

++IF FMID(CPSAH00) REQ(RO73192) .

++IF FMID(CPXMH00) REQ(RO73193) .



COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






).









Star Problem(s):

PXM 164
















SYMPTOMS:

N/A

IMPACT:










CIRCUMVENTION:

N/A



PDT 1161
















SYMPTOMS:

N/A

IMPACT:


















PSA 406



++VER (Z038)

FMID (CPSAH00)


RO67967 RO68517 RO68534 RO70481 RO72163 )

SUP ( RO58950 RO69200 ZDTM095 ZSAM041 ZXMM011 )

++IF FMID(CPDTH00) REQ(RO73191) .

++IF FMID(CPXMH00) REQ(RO73193) .

++HOLD (RO73192) SYSTEM FMID(CPSAH00)


COMMENT (

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

| Subsystem Analyzer Release 17.0 |

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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






).









Star Problem(s):

PXM 164
















SYMPTOMS:

N/A

IMPACT:










CIRCUMVENTION:

N/A



PDT 1161
















SYMPTOMS:

N/A

IMPACT:


















PSA 406



++VER (Z038)

FMID (CPXMH00)

SUP ( ZDTM095 ZSAM041 ZXMM011 )

++IF FMID(CPDTH00) REQ(RO73191) .

++IF FMID(CPSAH00) REQ(RO73192) .

++HOLD (RO73193) SYSTEM FMID(CPXMH00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






).





LOOP IN XMANAGER DURING DETECTOR COLLECTION STARTUP


CA Detector for DB2 for z/OS (PDT) can enter a loop during collection

startup. This problem can occur if the prior execution of the Xmanager

address space abnormally terminated, or was CANCELed or FORCEd.

SYMPTOMS:

High CPU usage by the Xmanager address space following the start of

a Detector collection.

IMPACT:

The Detector collection cannot be started. The Xmanager must be

canceled. If the subsequent restart also enters a loop, the DB2 subsystem

will need to be recycled before the Xmanager can be restarted again.

CIRCUMVENTION:

None.





Star Problem(s):

PDT 1220


DESC(LOOP IN XMANAGER DURING DETECTOR COLLECTION STARTUP) .

++VER (Z038)

FMID (CPDTH00)


SUP ( HDTM003 RO61110 RO68009 ZDTM100 )



COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






Release Service Detailsunpredictable behavior with CA-DB2 tools and/or compromise the


).





PDTBATCH REPORT DISPLAYS 6-DIGIT USE COUNT


THE 'USE COUNT' FIELD ON THE CA DETECTOR FOR DB2 FOR Z/OS (PDT) BATCH

Reporting Facility (PDTBATCH) only holds 6 digits worth of data. As a

result, higher order digits are truncated.

SYMPTOMS:

The following examples show this behavior:

Online Detector History DETECTOR Plan Dynamic SQL Display:

USE COUNT 2134076

PDTBATCH batch report:

Use Count - 134076

IMPACT:

THE VALUE IN THE 'USE COUNT' FIELD IN THE PDTBATCH OUTPUT IS INCORRECT IF

the value is greater than 999999.

CIRCUMVENTION:

VERIFY THE 'USE COUNT' IN THE ONLINE DISPLAY.





Star Problem(s):

PDT 1204

PDTBATCH UNLOAD JOB FAILS WITH ABEND S878-14


CA Detector for DB2 for z/OS (PDT) Batch Reporting Facility (PDTBATCH)

may encounter S878-14 during the unload datastore process.

SYMPTOMS:

The job ends abnormally with the following message:

ERROR DURING GETMAIN SYS CODE = 878-14

SYSTEM COMPLETION CODE=878 REASON CODE=00000014

NO ACTIVE MODULE FOUND NAME=UNKNOWN

IMPACT:

Users of PDTBATCH are unable to unload the CA Detector statistics

and load into Detector DB2 tables to investigate DB2 performance

issues.

CIRCUMVENTION:

None.





PDT 1206


DESC(PDTBATCH REPORT DISPLAYS 6-DIGIT USE COUNT) .

++VER (Z038)

FMID (CPDTH00)

PRE ( RO56187 RO57946 RO69236 RO73191 )

SUP ( RO67241 RO67505 ZDTM090 ZDTM093 )





DYNAMIC SQL COLLECTION TERMINATES WITH AN S0C4 ABEND


CA Detector for DB2 for z/OS (PDT) may abend with a S0C4 in load module

PDTDYWCX WHERE THE 'X' REPRESENTS THE VERSION OF DB2. THIS PROBLEM OCCURS

when dynamic SQL text is being collected and the SQL text is one byte in

length, i.e. an invalid SQL statement.

SYMPTOMS:

Message PDT0216 is issued in the Xmanager job log followed by the S0C4 abend

messages, for example:

PDT0216 DYNAMIC COLLECTION S0C4 ABEND INCURRED/TERMINATION FORCED

IEA995I SYMPTOM DUMP OUTPUT 179


TIME=06.16.58 SEQ=17723 CPU=0000 ASID=00F9

PSW AT TIME OF ERROR 478C2000 A84F57F2 ILC 4 INTC 11

ACTIVE LOAD MODULE ADDRESS=284F5000 OFFSET=000007F2

NAME=PDTDYWC0

DATA AT PSW 284F57EC - E00141F0 F0019540 F00047D0

...

IMPACT:

Dynamic SQL collection terminates resulting in lost statistics and dynamic

SQL text.

CIRCUMVENTION:

Stop and restart the collection to resume Dynamic SQL collection.





Star Problem(s):

PDT 1211


DESC(DYNAMIC SQL COLLECTION TERMINATES WITH AN S0C4 ABEND) .

++VER (Z038)

FMID (CPDTH00)

PRE ( RO66656 RO73191 )

SUP ( ZDTM097 )



COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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



Release Service DetailsTo implement the PTF:





Note:






).





MISSING IMAGE COPY STEP FOR PARTITIONED TABLESPACES


CA Recovery Analyzer for DB2 for z/OS (PRA) does not generate image copy

statements for partitioned tablespaces when generating a backup job from

the strategy analysis job.

SYMPTOMS:

JCL generated from the strategy analysis job does not contain COPY

statements for partitioned tablespaces, although QUIESCE statements are

present.

IMPACT:

Partitioned tablespaces are not backed up.

CIRCUMVENTION:

Manually select partitioned tablespaces into the strategy creation when

prompted to Select Objects for Recovery.

PRODUCT(S) AFFECTED: PRA Release 17.0

Star Problem(s):

PRA 827


DESC(MISSING IMAGE COPY STEP FOR PARTITIONED TABLESPACES) .

++VER (Z038)

FMID (CPRAH00)


SUP ( ZRAM049 )





ABEND S0CX RIGHT AFTER INTERVAL END


The CA Subsystem Analyzer for DB2 for z/OS (PSA) may abend with an

0C4 right after interval swaps when collecting subsystem statistics.

SYMPTOMS:

The following messages appred on the Xmanlog:

PSA0122 ABEND=S0C4 MODULE=SA$CGE OFFSET=00001CFC DB2=101

PSA0122 ABEND=S0C6 MODULE=SA$CGE OFFSET=00001CB6 DB2=101

PSA0122 ABEND=S0C4 MODULE=SA$CUT OFFSET=000028EC DB2=101

PSA0814 SSANALZE ABTERM/SDUMP IN PROGRESS DB2=DB2A

PSA0815 SSANALZE SDUMP CAPTURE COMPLETE DB2=DB2A RETURN CODE=00

REASON=00



TIME=15.45.07 SEQ=64972 CPU=0000 ASID=0129

PSW AT TIME OF ERROR 078D2000 9C06DB38 ILC 4 INTC 11

ACTIVE LOAD MODULE ADDRESS=1C067000 OFFSET=00006B38

NAME=PSACIOCC

IMPACT:

The Subsystem Analyzer collection stops and must be restarted.

CIRCUMVENTION:

None.





Star Problem(s):

PSA 415


DESC(ABEND S0CX RIGHT AFTER INTERVAL END) .

++VER (Z038)

FMID (CPSAH00)

PRE ( RO64204 RO64838 RO65659 )

SUP ( ZSAM042 )

++HOLD (RO73247) SYSTEM FMID(CPSAH00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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




Release Service Details1. Stop product collections.




Note:






).





RO73026 CAUSES A S0C4 ABEND INTO PTAGCHK{P|A|0} ON NON-DS


PTF RO73026 for release 17.0 introduced an error with the CA DB2 Tools for

z/OS General Checkpoint log record service. When executing on a

non-datasharing subsystem, it will encounter a S0C4 abend in one of the

following modules: PTLGCHKP, PTLGCHKA, PTLGCHK9.

SYMPTOMS:

The job encounters a S0C4 in one of the above mentioned modules.

IMPACT:

Users of CA Fast Unload for DB2 for z/OS with BP-LOOKUP or

CA Quick Copy for DB2 for z/OS with SHRLEVEL CHANGE will abend with a S0C4.

CIRCUMVENTION:

None.





Star Problem(s):

GEN 1220


DESC(RO73026 CAUSES A S0C4 ABEND INTO PTAGCHK{P|A|0} ON NON-DS) .

++VER (Z038)

FMID (CGENH00)

PRE ( RO57940 RO58869 )

SUP ( HGEM002 RO73026 ZGEM064 )





REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS


Object Framework Services Agent (OFA) has been updated to remove the

dependence on Execution Status Data Source in future releases of CA Chorus

for DB2 Database Management to work with CA Chorus DBA Services R17. As part

of this change, OFA is modified to utilize the internal BPLOG table to manage

Object Migration Analysis in a future release of CA Chorus instead of

Datacom.

SYMPTOMS:


IMPACT:

None.

CIRCUMVENTION:

None.




Star Problem(s):

CHRDBM 231

Copyright (C) 2014 CA. All rights reserved. R00049-DF160-SP1

DESC(REMOVE EXECSTAT DEPENDENCY FOR FUTURE RELEASE OF CA CHORUS).

++VER (Z038)

FMID (CEU9G00)


RO52243 RO52691 RO53510 RO54200 RO57118 RO70460 )


TR45615 TR55243 TR55321 TR57059 TR57786 TR58537

TR72160 )

++HOLD (RO72160) SYSTEM FMID(CEU9G00)


COMMENT (

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

| CA Mainframe Chorus DBA Role Services Release 16.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).





SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR



may ABEND when an IQL request with invalid syntax is started or

checked for syntax errors.

SYMPTOMS:

Unpredictable Data Collector ABENDs (S0C1, S0C4, S0C6) during IQL syntax

check or startup.

IMPACT:

Data Collector ABEND.

CIRCUMVENTION:

Use error-free IQL syntax.




Star Problem(s):

IDB2 1676


DESC(SYNTAX ERROR IN IQL CAUSES ABEND IN DATA COLLECTOR) .

++VER (Z038)

FMID (CCIDG00)


RO48144 RO54436 RO54886 RO64382 RO66638 RO67256

RO68620 )

SUP ( RO43775 ZDBJ189 )











SYMPTOMS:



IMPACT:



CIRCUMVENTION:

None.


























Star Problem(s):

PLR 128



++VER (Z038)

FMID (CPLRG00)

PRE ( RO61386 RO66977 RO67304 RO68438 RO70683 )

SUP ( RO62839 ZLRK015 )


















negative SQLCODE.







SYMPTOMS:
















SQL column is zero.




IMPACT:




thresholds.

CIRCUMVENTION:

















Star Problem(s):






++VER (Z038)

FMID (CPDTG00)


RO65829 RO65951 RO66122 RO66747 RO67418 RO69949

RO69980 RO72139 )

SUP ( HDTL006 RO45159 RO55024 RO72013 ZDTL144 )

++HOLD (RO72459) SYSTEM FMID(CPDTG00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






).










SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.




Star Problem(s):

IDB2 1677



++VER (Z038)

FMID (CCIDG00)


RO43485 RO44213 RO44302 RO45380 RO46784 RO48733

RO51539 RO53991 RO54436 RO54886 RO55643 RO58694

RO59218 RO61473 RO61904 RO63686 RO64382 RO65573

RO66638 RO67572 RO68559 RO68620 RO70966 )

SUP ( HCIJ002 HCIJ003 HCIJ005 RO41921 RO41973 RO44212

RO44552 RO45721 RO46482 RO47499 RO48129 RO48325

RO48612 RO49699 RO49845 RO49974 RO50542 RO51956

RO52556 RO55553 RO56157 RO56446 RO56721 RO57181

RO57707 RO59577 RO60998 RO62159 RO62199 RO63257

RO64622 RO64738 RO65327 RO65504 RO65888 RO66047

RO66466 RO66475 RO67029 RO67684 RO67782 RO68932

RO71300 RO71423 RO71482 ZDBJ191 )

++IF FMID(CIDBG00) REQ(RO72500) .










SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.




Star Problem(s):

IDB2 1677



++VER (Z038)

FMID (CIDBG00)


RO52881 RO53992 RO54438 RO61311 RO61474 RO63687

RO64383 RO68623 RO70743 )

SUP ( RO55703 RO62118 ZDBJ191 )

++IF FMID(CCIDG00) REQ(RO72498) .





NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1



collection subtasks may abend before the collection is complete. See

SYMPTOMS section for specifics. The PDA extract execution environment

or conditions would need to minimally include the following:

- DB2 environment is non-datasharing

- Number of collection subtasks or Scans is > 1

- Includes at least one multiple versioned tablespace or was once

versioned and is not the first selected tablespace for stats

collection processing

SYMPTOMS:

The following message can be found in the PTIMSG output:

DB2 Version not supported RC=0211 RS=0000

Error opening DB2 loadlibs for <ssid> RC=0109 RS=0143


PTABDBS: PTLBDBC subtask has abended: S0C4 RC=0064 RS=0196


PTABDBS: PTLBDBC subtask has abended: S0F4 RC=0064 RS=0244

Also the following message can be found in the JOB log:

CSV005I BLDL FAILED FOR MODULE DSNACAB , DCB NOT OPEN

IMPACT:

One or more tablespace statistics collection subtasks will be

incomplete. The stats collection will continue, however, depending on

the severity of the symptom the entire extract may terminate before

all objects are processed.

CIRCUMVENTION:

Resubmit the extract with Scans=1. This will require the PDA batch

extract job to be regenerated with the Submit panel field "Nbr of

Scans" set to 1.




Star Problem(s):

PDA 1260


DESC(NON-DATASHARE TS STATS COLLECTION ERRORS WHEN SCANS > 1) .

++VER (Z038)

FMID (CDASG00)


RO44083 RO45467 RO57895 RO64066 )

SUP ( RO69412 ZDAK068 )





0C4 DT$DII WITH EXCLUDED PLAN OR SQL ERROR ONLY COLLECTION


CA Detector for DB2 for z/OS (PDT) collection terminates with

S0C4 in DT$DII after the application of R16 PTF RO68043 or

R17 PTF RO68244.

SYMPTOMS:

The following messages appear in the Xmanager joblog:

PDT0185 ABEND=S0C4 MODULE=DT$DII OFFSET=000016DE DB2=091

PDT0102 DETECTOR TERM IN PROGRESS FOR DB2=D91B USER=USER112

An SVC dump is taken. The title is

CA-DETECTOR 17.0 DIAG/DUMP ABEND=S0C4 MODULE=DT$DII OFFSET=00016DE

IMPACT:

The collection terminats and must be restarted.

CIRCUMVENTION:

None.




Star Problem(s):

PDT 1200


DESC(0C4 DT$DII WITH EXCLUDED PLAN OR SQL ERROR ONLY COLLECTION) .

++VER (Z038)

FMID (CPDTG00)


RO48124 RO49569 RO50557 RO53542 RO54115 RO54876

RO54974 RO55607 RO55636 RO56241 RO57651 RO57696

RO58987 RO61139 RO62359 RO65462 RO65503 RO65829

RO65951 RO68043 RO69949 RO69980 RO71353 RO71362 )

SUP ( RO44445 RO45747 RO52624 RO69259 RO71249 ZDTL138 )

++HOLD (RO72616) SYSTEM FMID(CPDTG00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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








Release Service DetailsNote:






).





S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING



may abend with S0C4 when accounting record IFCID 3 originating from

a parallel DDF query is processed.

SYMPTOMS:

Abend S0C4 in LMOD NSIGHTPR CSECT NBRECRDR +000E28 occurs when DB2

subsystem finishes running a parallel DDF thread.

IMPACT:

Insight Data Collector abends with S0C4.

CIRCUMVENTION:

None.



Star Problem(s):

IDB2 1674


DESC(S0C4 IN NSIGHTPR DURING PROCESSING PARALLEL DDF ACCOUNTING) .

++VER (Z038)

FMID (CCIDG00)


RO55643 RO58694 RO60998 RO61473 RO63686 RO64382

RO65504 RO68620 RO72498 )

SUP ( RO51956 ZDBJ192 )





SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM


An analysis in CA RC/Migrator for DB2 for z/OS (RCM) ends with

SQLCODE -518 when ACM is used and procedures are in the strategy.

SYMPTOMS:

The analysis ends with SQLCODE -518 in RMA@UF2.

IMPACT:

The analysis does not complete.

CIRCUMVENTION:

Run analysis without using ACM.



Star Problem(s):

RCM 2613


DESC(SQLCODE -518 ISSUED WHEN MIGRATING PROCEDURES USING ACM) .

++VER (Z038)

FMID (CRCMG00)


RO52247 RO56531 RO62194 RO69073 )

SUP ( ZRML342 )

++HOLD (RO72638) SYSTEM FMID(CRCMG00)


COMMENT (

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


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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).





TGRFXV007E ZERO CELL LENGTH FOUND


Tiger reads the VVRs for all data sets it is copying. If the length

of the VVR exceeded the size of the VVR buffer, the VVR was cut off

at the end of the buffer. The cell appeared to have a zero length

because it was not present in the buffer.

This fix provides larger VVR buffer and adds code to look for VVR

RECORD TRUNCATION. IF A VVR'S LENGTH EXCEEDS THE BUFFER SIZE, NEW

message TGRFXV009E is issued indicating the size of the VVR and the

size of the current buffer.

Also, an overlay of the working storage by a service routine has been

corrected. This overlay could manifest itself in unpredictable ways.

SYMPTOMS:

When performing FlashCopy operations, some data sets get message:

TGRFXV007E (2) Zero cell length found at offset 0x0847 searching for

type 0x27 cell in source VVR

The copy operation fails for that data set.

IMPACT:

Data sets with large VVRs (typically those with many extents) cannot

be processed.

CIRCUMVENTION:

None.








Star Problem(s):

TGR 247


DESC(TGRFXV007E ZERO CELL LENGTH FOUND) .

++VER (Z038)

FMID (CTGRG00)


RO70863 )

SUP ( RO56856 RO70956 RO71478 ZTGJ026 )

++HOLD (RO72647) SYSTEM FMID(CTGRG00)


COMMENT (

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

|Snapshot General Services Version 16.0 |

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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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




Release Service Detailsmaintenance. If you do not customize XMESSAGES,






).





IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP


The CCSID DSNZPARM field help displays within CA Thread

Termination/Dynamic ZPARM for DB2 for z/OS (PTT) do not reflect the


Migration Guide:



SYMPTOMS:

The CCSID DSNZPARM field help displays within PTT do not reflect the


Migration Guide:



IMPACT:

UPDATING ONE OF THE CCSID'S MAY COMPROMISE DATA INTEGRITY.

CIRCUMVENTION:

BE MINDFUL OF IBM'S RECOMMENDATION:







Star Problem(s):

PTT 317


DESC(IBM CCSID UPDATE RECOMMENDATION NOT REFLECTED IN FIELD HELP) .

++VER (Z038)

FMID (CPTTG00)

SUP ( ZTTL037 )





FUNCTION RESTRICTED BY SECURITY IN CA SYSVIEW DB2 MENU


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

data collector refuses the access from DB2 menu in CA Sysview when

security access is restricted to the specific security group ID

in CA Insight security file.

SYMPTOMS:

Error message in CA Sysview panel

DB20004E Agent CA31DA0G7709DC77 request IDB2:DSQSTBP failed -

rc 197 rsn 24 - DBG55096E Function restricted by security

DB20004E Agent CA31DA0G7709DC77 request IDB2:DSQSTBP failed -

Error message in CA Insight Data Collector JES2 Job Log

NUINSUB DISPLAY for DSQSTBP : call results 806

RC-0024 Ln-0000 Ct-0000 Data-00000100 807

Ti-0000 Co-0000 Kl-0000 808

Error messages in CA Insight Data Collector DBGPRINT file

DBG44033I DA0G 09:30:02 USER JIRAN01 -........ SECURITY BLOCK COMMAND

CONNECT

DBG82001I DA0G 09:30:02 NUAGTDSP - RETURN CODE FROM NUINSUB = 36 FOR

REQUEST DSQSTBP ELAPSED 00:00:00.000000

Dots in the message DBG44033I represents binary zero value.

IMPACT:

CA Insight Data collector is not accessible from CA Sysview DB2 menu

when the applied security rule in Insight Security file is restricted

by security group ID.

IDB2 command is not affected by this bug.

CIRCUMVENTION:

Use the IDB2 command instead of the DB2 menu in CA Sysview, or remove

the rule with the group restriction in the CA Insight security file.





Star Problem(s):

IDB2 1628


DESC(FUNCTION RESTRICTED BY SECURITY IN CA SYSVIEW DB2 MENU) .

++VER (Z038)

FMID (CCIDG00)


RO46784 RO54436 RO64382 RO68620 )

SUP ( ZDBJ184 )





PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION


CA Fast Load for DB2 for z/OS (PFL) can encounter a ZPARM

page protection error:

PUT4304E APPLICATION LACKS APF AUTHORITY and


when attempting to set a ZPARM to allow an update of SYSCOPY.

SYSTABLEPART, SYSINDEXPART or SYSTABLESPACE catalog updates, within the load

process can also be impacted.

SYMPTOMS:

The load completes. Return Code 20 is displayed if a SYSCOPY update

is attempted. If another catalog update is attempted, the return code

can be 4 or 0. In all cases a SNAP DUMP is returned.

The following messages are displayed:

From the PTIMSG output:

For SYSCOPY update:

PUT4304E APPLICATION LACKS APF AUTHORITY


is displayed.

The snap dump output contains the following:

ERLY Block - First pass

2B3ECF40 00A50

2B3ECF60 C4E2D540 C4E2D5D4 E2E3D940 00180200 2B3ECD58 207E4F40 00000

...

IMPACT:

The load completes but a system catalog update(s) are not completed.

CIRCUMVENTION:

NONE


Release 17.0

Star Problem(s):

PFL 1112


DESC(PFL0082E UPDATING SYSCOPY FAILED NO RESTART FOR FUNCTION) .

++VER (Z038)

FMID (CCOMG00)

SUP ( RO60171 ZFLL100 )





INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET


CA Fast Load for DB2 for z/OS (PFL) can overlay its input dataset when

INDDN SYSREC is specified during an OUTPUT-CONTROL ALL

execution and UNLDDN is not specified.

The default DDNAME for the unload dataset is SYSREC so when

INDDN SYSREC is specified and UNLDDN is not, the data is read from

the SYSREC dataset and the unload information is written back

to the SYSREC dataset.

SYMPTOMS:

The load completes. There is no indication that SYSREC information

has been overlaid until the SYREC dataset name is reloaded.

In that case PFL can fail with discard errors.

PFL0806I - Conversion rejects ..................n,nnn

IMPACT:

The load completes. The original input data is lost.

CIRCUMVENTION:

When INDDN SYSREC is specified make certain UNLDDN is also specified

with a different DDNAME.


Release 17.0

Star Problem(s):

PFL 1113


DESC(INDDN SYSREC WITHOUT UNLDDN CAN OVERLAY INPUT DATASET) .

++VER (Z038)

FMID (CPFLG00)


RO44031 RO45451 RO45801 RO47008 RO48719 RO49446

RO54267 RO55937 RO59639 RO59714 RO60966 RO63708

RO64071 RO64100 RO64962 )

SUP ( RO45808 ZFLL101 )

++HOLD (RO72743) SYSTEM FMID(CPFLG00)

REASON (DOC ) DATE (14226)

COMMENT (

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


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


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

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

* PUBLICATION *

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

Holddata

With the implementaion of this PTF, PFL will now terminate

if INDDN SYSREC for OUTPUT-CONTROL ALL is specified and

UNLDDN is not. This is implemented to prevent input data

from being overlayed.

xmessage PFL1112E will display for this circumstance.

PFL1113E - INDDN and UNLDDN specify the same data set name: SYSREC

Fast Load is terminating.

Change the INDDN or UNLDDN name and resubmit.

).

++HOLD (RO72743) SYSTEM FMID(CPFLG00)


COMMENT (

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


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


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





|USERS | |


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

|KNOWLEDGE | |


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



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

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


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








).





S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS


CA Execution Manager for DB2 for z/OS (PXM) may abend with S0C4 in

module PXMZMVCC. This will prevent access to some CA Detector for DB2 for

z/OS (PDT), CA Subsystem Analyzer for DB2 for z/OS (PSA), and CA Thread

Termination/Dynamic ZPARM for DB2 for z/OS (PTT) displays when the DB2

subsystem is remote.

SYMPTOMS:

A symptom dump appears in the Xmanager log, reporting a S0C4 abend in

load module PXMZMVCC.

After the S0C4 abend occurs, an ISPF error message reading "Cross system

error Sysplex Support Inactive" may appear on the PDT, PSA, or PTT

main menu.

IMPACT:

The S0C4 abend will prevent access to some PDT, PSA, and PTT displays

when the DB2 subsystem is remote.

CIRCUMVENTION:

The Xmanager incurring the S0C4 abend must be restarted.














Star Problem(s):

PXM 165


DESC(S0C4 IN MODULE PXMZMVCC, THEN LIMITED REMOTE DB2 ACCESS) .

++VER (Z038)

FMID (CPXMG00)

PRE ( RO42807 RO44048 RO70624 )

SUP ( ZXML018 )

++HOLD (RO72815) SYSTEM FMID(CPXMG00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |




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


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






Note:






).





TASK COUNT INCORRECT


If the maximum number of tasks is limited and mutiple data movers

need to be used within a single copy operation, if DFSMSdss is one of

those data movers, it is possible that the number of tasks reserved

for DFSMSdss will be set to zero. This correction ensures there is

one task reserved for DFSMSdss.

SYMPTOMS:

The number of tasks displayed may not match the actual number of

tasks being used.

IMPACT:

The number of tasks in use may not be the quatity expected.

CIRCUMVENTION:

None








Star Problem(s):

TGR 248


DESC(TASK COUNT INCORRECT) .

++VER (Z038)

FMID (CTGRG00)

PRE ( RO42109 RO52372 RO55596 RO63645 )

SUP ( ZTGJ027 )





SQL007 FOR PARSING SELECT FROM DELETE SYNTAX


The CA Database Management Solutions for DB2 for z/OS (PAS) SQL Parser

would incorrectly generate parse errors for valid SQL with SELECT from DELETE

syntax when WHERE clause apply to SELECT clause:

The following SQL contains an example of this syntax:

SELECT * FROM OLD TABLE ( DELETE FROM SYSIBM.SYSTABLES_HIST )

WHERE CREATOR = 'XXXXXXXX'

SYMPTOMS:

Parse error is generated for valid SQL containing SELECT from DELETE syntax:

SQL007: A left parenthesis has been found without a

matching right parenthesis.

IMPACT:

Any CA DB2 tool which attempts to parse SQL containing the above syntax

may be affected by this problem.

CIRCUMVENTION:

None.






Star Problem(s):

PAS 206


DESC(SQL007 FOR PARSING SELECT FROM DELETE SYNTAX) .

++VER (Z038)

FMID (CPASG00)

PRE ( RO42385 RO44271 RO44617 RO71069 )

SUP ( RO43786 RO45170 RO45956 RO66736 RO72150 ZPSK031 )





IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS


CA Fast Unload for DB2 for Z/OS (PFU) may experience a lack of

region type of failure when using a SYSIN with the number of SELECT

statements including a WHERE clause exceeds 147 and there is at least

two or more columns referenced inside the WHERE clause of each

SELECT statement. The number of SELECT statements containing WHERE

clauses PFU is able to handle could be smaller than 147 based on the

content in the WHERE clause(s). The greater the number of columns and

conditions in the WHERE clause, the smaller number of SELECT statements

PFU can safely process.

SYMPTOMS:

PFU may abend with a S106, S806, S878 or other type of lack of

available region failure.

IMPACT:

The job fails without unloading the requested data.

CIRCUMVENTION:

Reduce the number of SELECT atatements containing WHERE clauses

referencing 2 or more columns each to a number less than 147.


Release 17.0

Release 18.0

Star Problem(s):

PFU 918


DESC(IEA705I GETMAIN S80A FAILURE MANY SELECT STATEMENTS) .

++VER (Z038)

FMID (CPFUG00)


RO57166 RO62380 RO67884 RO70417 )

SUP ( RO46121 RO59815 ZFUL103 )














SYMPTOMS:








nothing for PFR

IMPACT:


CIRCUMVENTION:






Star Problem(s):

PUT 730



++VER (Z038)

FMID (CCOMG00)

SUP ( ZUTK058 )

++IF FMID(CPUTG00) REQ(RO72979) .














SYMPTOMS:








nothing for PFR

IMPACT:


CIRCUMVENTION:






Star Problem(s):

PUT 730



++VER (Z038)

FMID (CPUTG00)

PRE ( RO43412 RO43445 RO59012 )

SUP ( ZUTK058 )

++IF FMID(CCOMG00) REQ(RO72978) .





COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED


CA Log Analyzer for DB2 for z/OS (PLA) DML Summary reports may report

Commit Status of unit of recovery (UR) as Committed even if it was rolled

back. This happens only on data sharing systems.

SYMPTOMS:

ABORTED UR'S ARE REPORTED AS COMMITTED.

IMPACT:

Reported Commit Status on data sharing systems may be incorrect.

CIRCUMVENTION:

None.


PLA Release 16.0

Star Problem(s):

PLA 1157


DESC(COMMIT STATUS READS COMMITTED WHEN UR WAS ABORTED) .

++VER (Z038)

FMID (CPLAG00)


RO46382 RO46426 RO46900 RO48857 RO49459 RO49722

RO51083 RO53288 RO54559 RO54613 RO55989 RO61636

RO67869 )

SUP ( RO46604 RO50569 RO52438 RO64964 ZLAK121 )





UPDATE TO SUPPORT FUTURE RELEASE OF CA CHORUS DBA


CA RC/Migrator for DB2 for z/OS (RCM) has been updated to process new

parameters passed from CA Chorus DBA Services as part of the Object Migration

Analysis in a future release of CA Chorus for DB2 Database Management and

store them in the internal BPLOG table. This change is necessary to let you

manage Object Migration Analysis using a future release of CA Chorus without

Datacom.

SYMPTOMS:


IMPACT:

None.

CIRCUMVENTION:

None.




Star Problem(s):

RCM 2584


DESC(UPDATE TO SUPPORT FUTURE RELEASE OF CA CHORUS DBA) .

++VER (Z038)

FMID (CRCMG00)


RO47022 RO47638 RO58856 RO59335 )

SUP ( RO51633 ZRML336 )

++IF FMID(CRBPG00) REQ(RO71823) .

++IF FMID(CINSG00) REQ(RO71824) .

++HOLD (RO73104) SYSTEM FMID(CRCMG00)


COMMENT (

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


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


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


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

|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).





ABEND S0CX RIGHT AFTER INTERVAL END


The CA Subsystem Analyzer for DB2 for z/OS (PSA) may abend with an

0C4 right after interval swaps when collecting subsystem statistics.

SYMPTOMS:

The following messages appred on the Xmanlog:

PSA0122 ABEND=S0C4 MODULE=SA$CGE OFFSET=00001CFC DB2=101

PSA0122 ABEND=S0C6 MODULE=SA$CGE OFFSET=00001CB6 DB2=101

PSA0122 ABEND=S0C4 MODULE=SA$CUT OFFSET=000028EC DB2=101

PSA0814 SSANALZE ABTERM/SDUMP IN PROGRESS DB2=DB2A

PSA0815 SSANALZE SDUMP CAPTURE COMPLETE DB2=DB2A RETURN CODE=00

REASON=00



TIME=15.45.07 SEQ=64972 CPU=0000 ASID=0129

PSW AT TIME OF ERROR 078D2000 9C06DB38 ILC 4 INTC 11

ACTIVE LOAD MODULE ADDRESS=1C067000 OFFSET=00006B38

NAME=PSACIOCC

IMPACT:

The Subsystem Analyzer collection stops and must be restarted.

CIRCUMVENTION:

None.





Star Problem(s):

PSA 415


DESC(ABEND S0CX RIGHT AFTER INTERVAL END) .

++VER (Z038)

FMID (CPSAG00)


SUP ( RO41931 ZSAL067 )

++HOLD (RO73138) SYSTEM FMID(CPSAG00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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




Release Service Details1. Stop product collections.




Note:






).





RMA531E WHEN BOTH I AND J DATASETS ARE PRESENT


In CA RC/Merger for DB2 for z/OS (RMM), when analyzing a Move, Copy or Data

only copy strategy, the analysis fails with RMA531E if both the I0001 and

J0001 datasets are present.

SYMPTOMS:

Analysis fails with :

RMA531E LOCATE SORT error in RMA@DDLM , duplicate Annn numbers in DSN =

DATASET NAME and object INDEX/TABLESPACE object name.

IMPACT:

The customer will not be able to analyze the strategy.

CIRCUMVENTION:

Identify the active dataset by querying the IPREFIX value from SYSIBM.

SYSTABLEPART or SYSIBM.SYSINDEXPART and manually rename the inactive

dataset.


RC/Merger Release 15.0

Star Problem(s):

RMM 167


DESC(RMA531E WHEN BOTH I AND J DATASETS ARE PRESENT) .

++VER (Z038)

FMID (CRCMF00)


RO42228 RO42424 RO43695 RO46369 RO61166 )

SUP ( RO53076 RO60868 ZRMI640 )

++HOLD (RO72410) SYSTEM FMID(CRCMF00)


COMMENT (

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


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


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


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

|USERS | |


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

|KNOWLEDGE | |

|REQUIRED | CA DB2 Tools Post Install Customization |

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



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

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


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

Bind Control Cards have changed as part of this

maintenance. After this maintenance is applied, Bind

Control Cards must be regenerated for all installed

products. Using the newly generated Bind Control Cards,

a Bind Replace must be performed on the plans and

packages for all installed products. Refer to the

Implementation guide for details.

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


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


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





|USERS | |


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

|KNOWLEDGE | |


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



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

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


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





).











SYMPTOMS:



IMPACT:



CIRCUMVENTION:

None.


























Star Problem(s):

PLR 128



++VER (Z038)

FMID (CPLRF00)


SUP ( RO62838 ZLRH031 )


















negative SQLCODE.







SYMPTOMS:
















SQL column is zero.




IMPACT:




thresholds.

CIRCUMVENTION:

















Star Problem(s):






++VER (Z038)

FMID (CPDTF00)


RO53603 RO59129 RO65576 RO66070 RO66693 RO66732

RO69821 RO72151 )

SUP ( HDTI004 HDTI017 RO34477 RO35106 RO35766 RO38969

RO45153 ZDTI262 )

++HOLD (RO72446) SYSTEM FMID(CPDTF00)


COMMENT (

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


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


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


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




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




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


|REQUIRED | |

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

| | |

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

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


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






Note:






).





ABEND S0C4 PSACDDCC COPY UTILITY IF INPUT DS HAS 1 INTERVAL


The CA Subsystem Analyzer for z/OS (PSA) data store copy utility may

receive an ABEND S0C4 if the input data store being copied only

contains one interval.

SYMPTOMS:



TIME=14.59.36 SEQ=63185 CPU=0000 ASID=035A

PSW AT TIME OF ERROR 078D2000 80017F58 ILC 4 INTC 04

ACTIVE LOAD MODULE ADDRESS=00011000 OFFSET=00006F58

NAME=PSACDDCC

DATA AT PSW 00017F52 - 60085060 20081233 4780A222

AR/GR 0: 00000000/00000000_0007D128 1: 00000000/00000000_00000000

2: FFFFFFFF/FFFFFFFF_00000000 3: FFFFFFFF/FFFFFFFF_00000000

4: FFFFFFFF/FFFFFFFF_CECBF290 5: FFFFFFFF/FFFFFFFF_33EE1B5C

6: FFFFFFFF/FFFFFFFF_33EDB014 7: FFFFFFFF/FFFFFFFF_33EDB000

8: FFFFFFFF/FFFFFFFF_33E7F000 9: FFFFFFFF/FFFFFFFF_33D1E000

A: FFFFFFFF/00000000_00017D40 B: FFFFFFFF/00000000_0007D000

C: FFFFFFFF/FFFFFFFF_00006000 D: FFFFFFFF/00000000_0007D098

E: 00000000/00000000_00000001 F: 00000000/00000000_000157A0

IMPACT:

The utility abnormally terminates and the data store is not copied.

CIRCUMVENTION:

Collect another interval to the data store so that at least 2 intervals

are being copied.





Star Problem(s):

PSA 411


DESC(ABEND S0C4 PSACDDCC COPY UTILITY IF INPUT DS HAS 1 INTERVAL) .

++VER (Z038)

FMID (CPSAF00)

PRE ( RO28975 )

SUP ( ZSAI090 )

CA DB2 Tools 17.0 1 CA RS 1409 Service List pfl0082e updating syscopy failed no restart for function...

Documents

Transcript of CA DB2 Tools 17.0 1 CA RS 1409 Service List pfl0082e updating syscopy failed no restart for function...