|
DB2 Cloning Tool Version 3.2.0
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2024 |
SUBSYSTEM CLONING DOES NOT UPDATE VCATS IN A COMPRESSED DIRECTORY WHEN CLONING DATA SHARING GROUPS | ||||
2024 |
APPLICATION CLONING DOES NOT TRANSLATE/RESET THE CONTENTS OF COMPRESSION DICTIONARIES | ||||
2024 |
RERUNNING RESTORE-FROM-DUMPTAPES RESULTS IN CKZ07024W MESSAGE WITH MISSING VOLUME SERIAL | ||||
2024 |
SUPPORT ADDED FOR UNLOAD/LOAD WITH SPANNED RECORD FORMAT IN APPLICATION CLONING. | ||||
2024 |
SUPPORT DB2 VERSION 13 WITH ACTIVATED FUNCTION LEVEL 504 | ||||
2024 |
SUPPORT CLONING ARCHIVE TABLES, DB2 13 UTILITY HISTORY AND OPTIMIZING TARGET LOG APPLY MEMORY USAGE ADDED TO APP CLONING. |
||||
2024 |
THE SIMPLIFIED ISPF INTERFACE MIGHT GENERATE AN INCORRECT VALUE FOR DDL-REPORT KEYWORD. | ||||
2024 |
THE APPLICATION CLONING TARGET JOB FAILS WITH RC=8 AND DSNU056I DURING LOAD | ||||
2024 |
APPLICATION CLONING SOURCE SERVER JOB STOPS RESPONDING DURING XML PROCESSING | ||||
2024 |
APPLICATION CLONING SOURCE JOB ENDS WITH CKZ61338E ERROR AFTER RE-CREATING TABLE IN AN IMPLICIT DATABASE | ||||
2024 |
SUBSYSTEM CLONING DB2ALTERBSDS COMMAND CANNOT FIND THE SLB LRSN IN THE ACTIVE LOG | ||||
2024 |
SUBSYSTEM CLONING DB2SCHEMA-UPDATE COMMAND DOES NOT DETECT SOME EXISTING TARGET SCHEMAS | ||||
2024 |
APPLICATION CLONING SOURCE JOB ENDS WITH CKZ00051E WHEN A DATA SET KEY LABEL IS PROTECTED WITH CRITERIA(SMS(DSENCRYPTION)) | ||||
2023 |
THE MESSAGE CKZ28127W DOES NOT PROVIDE SUFFICIENT DIAGNOSTIC INFORMATION | ||||
2023 |
SOURCE JOB FAIL WITH CODE=0C4 REASON CODE=00000004 ACTIVE MODULE NAME=CKZ00544 | ||||
2023 |
APPLICATION CLONING SOURCE JOB ENDS WITH SQLCODE = -304 WHEN READING RTS | ||||
2023 |
SEVERAL INTERNAL BUGS ARE FIXED. | ||||
2023 |
DDL GENERATED BY APPLICATION CLONING ENDS WITH SQLERROR = -20525 WITH REASON CODE 7 | ||||
2023 |
UTILITIES SHOULD BE ALLOWED TO RUN AFTER RTS LOAD FAILURES IN APPLICATION CLONING TARGET JOB | ||||
2023 |
SUBSYSTEM CLONING DB2SCHEMA-UPDATE AND DB2SQL COMMANDS RE-CREATEONLY THE LAST VERSION OF VERSIONED SQL PROCEDURES AND TRIGGERS. |
||||
2023 |
CLONING TOOL 3.2 Q2 2023 HIP PTF | ||||
2023 |
INTERNAL FIXES FOR 2023 JULY RELEASE | ||||
2023 |
APPLICATION CLONING TARGET OBJECT IS INACCESSIBLE BECAUSE OF INCORRECTLY APPLIED INSERT LOG RECORD | ||||
2023 |
TARGET PARTITIONS WITHOUT SYSTEM PAGES ARE INACCESSIBLE AFTER APPLICATION CLONING | ||||
2023 |
APPLICATION CLONING IGNORES IX_UNIQUERULE MISMATCH IF DDL GENERATION IS ENABLED | ||||
2023 |
INVALID DDL IS GENERATED FOR EXTERNAL USER-DEFINED FUNCTIONS | ||||
2023 |
INTERNAL FIXES FOR 2023 JUNE RELEASE | ||||
2023 |
CLONING TOOL 3.2 Q1 2023 HIP PTF | ||||
2023 |
SUBSYSTEM CLONING IS NOT PROCESSED DEPENDENCIES ON INDEXES DURING DB2SCHEMA-UPDATE | ||||
2023 |
DB2 V13 FL503 SUPPORT | ||||
2023 |
MARCH INTERNAL FIXES | ||||
2023 |
FEBRUARY 2023 INTERNAL BUG FIXES | ||||
2023 |
APPLICATION CLONING GENERATES DDL FOR EXISTING TARGET STORAGE GROUPS AND DATABASES. | ||||
2023 |
DB2 CLONING TOOL 2022 Q4 PTF | ||||
2022 |
APPLICATION CLONING GENERATES DDL FOR AN EXISTING TARGET PRIMARYKEY | ||||
2022 |
SEVERAL INTERNAL BUGS ARE FIXED | ||||
2022 |
CLONING TOOL - DB2 V13 FL502 SUPPORT | ||||
2022 |
DROP/CREATE STATEMENTS FOR DEPENDENT FUNCTIONS ARE GENERATED IN THE WRONG ORDER | ||||
2022 |
SEVERAL INTERNAL ERRORS ARE FIXED | ||||
2022 |
APPLICATION CLONING FAILS WITH A DYNAMIC ALLOCATION ERROR WHEN GENERATING ALTER COLUMN RESTART WITH STATEMENTS | ||||
2022 |
DB2ALTERBSDS DOES NOT RECOGNIZE AN SLB WHEN A CHECKPOINT HAS A HIGHER RBA/LRSN THAN THE SLB | ||||
2022 |
INTERNAL FIXES APAR HOLDER FOR 2022OCT PTF | ||||
2022 |
APPLICATION CLONING REPORTS IX_UNIQUERULE MISMATCH AFTER CREATING A PRIMARY KEY ON A TABLE | ||||
2022 |
DB2SCHEMA-UPDATE COMMAND FAILS WITH MESSAGE CKZ28128E | ||||
2022 |
CLONING TOOL 3.2 INTERNAL FIXES FOR SEPTEMBER 2022 PTF | ||||
2022 |
CLONING TOOL 3.2 Q2 2022 HIP PTF | ||||
2022 |
RENAME FAILS WITH CKZ14310E WHEN OPENING BCS ON TARGET VOLUME | ||||
2022 |
APPLICATION CLONING TARGET JOB ENDS WITH RC=0 WHEN RTS PROCESSING ENDED WITH AN ERROR | ||||
2022 |
APPLICATION CLONING SOURCE JOB ENDS WITH CKZ00051E / CKZ0708A MESSAGE | ||||
2022 |
CLONING TOOL -SRCIMCPY DOES NOT CORRECTLY PROCESS EXISTING DATA SET EXTENTS | ||||
2022 |
SIMPLIFIED ISPF UI ISSUES ERROR CKZ515E WHEN BUILDING JCL FOR READ ONLY PROFILES | ||||
2022 |
UI82681 |
SIMPLIFIED ISPF UI INCORRECTLY SAVES TCP/IP SERVER PORT NUMBERS GREATER THAN 32768 | |||
2022 |
DB2 CLONING TOOL SUPPORT FOR DB2 V13 | ||||
2022 |
THE APPLICATION CLONING DDL DOES NOT GENERATE DDL FOR VIEWS IF THEIR BASE OBJECTS ALREADY EXIST ON THE TARGET | ||||
2022 |
CKZPG005W WARNINGS ON TABLE SPACES WITH CLONES | ||||
2022 |
CLONING TOOL APRIL APAR VARIOUS INTERNAL BUG FIXES | ||||
2022 |
THE APPLICATION CLONING DDL GENERATOR DOES NOT GENERATE PRIMARY KEYS FOR EXISTING TARGET TABLES | ||||
2022 |
TARGET COMPRESS YES XML TABLE SPACES ARE INACCESSIBLE AFTER CLONING | ||||
2022 |
INVALID IDCAMS COMMANDS ARE GENERATED WHEN MINILOG-HLQ-TARGET ISNOT SPECIFIED | ||||
2022 |
DDL EXECUTION FAILS ON POSITIVE SQL CODES | ||||
2022 |
ROLL UP APAR | ||||
2022 |
CLONING TOOL GDG ERROR MESSAGE CKZ14153E | ||||
2022 |
APPLICATION CLONING COULD FAIL DUE TO IX_DSSIZE AND IP_DSSIZE MISMATCH ON A PARTITIONED INDEX WHEN PAGENUM = 'A' ( 22028 ) | ||||
2022 |
CLONING TOOL 3.2 JANUARY PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 NOVEMBER PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 Q3 PTF | ||||
2021 |
DB2 CLONING TOOL 3.2 OCTOBER PTF | ||||
2021 |
SOURCE JOB WITH SRCIMCPY AND REUSE(Y) FAILS WITH CKZ1559E | ||||
2021 |
Description not available. Security/Integrity exposure | ||||
2021 |
DB2 CLONING TOOL - SEPTEMBER 2021 PTF | ||||
2021 |
CKZG4611E DURING SRCIMCPY WITH REUSE(Y) | ||||
2021 |
DB2 CLONING TOOL - 3.2 AUGUST PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 Q2 PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 JULY PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 JUNE PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 MAY PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 Q1 PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 APRIL PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 MARCH PTF | ||||
2021 |
DB2 CLONING TOOL - 3.2 FEBRUARY PTF | ||||
2021 |
UI74351 |
DB2 CLONING TOOL - 3.2 JANUARY PTF | |||
2021 |
UI74351 |
XML OBJECTS ARE UNAVAILABLE AFTER APPLICATION CLONING | |||
2021 |
CKZ01CIO/REV=49 WTRNSR INSERTED RECORDS INVISIBLE | ||||
2020 |
DB2 CLONING TOOL - 3.2 DECEMBER HIP PTF | ||||
2020 |
UI73295 |
DB2 CLONING TOOL - 3.2 DECEMBER PTF | |||
2020 |
DB2 CLONING TOOL - 3.2 NOVEMBER PTF | ||||
2020 |
DB2 CLONING TOOL - 3.2 2020Q3 PTF | ||||
2020 |
ERROR WITH SQLCODE=-802 CAN OCCUR IN THE TARGET JOB DURING UPDATE STATISTICS | ||||
2020 |
DB2 CLONING TOOL - 3.2 OCTOBER PTF | ||||
2020 |
DB2 APPLICATION CLONING SOURCE JOB CAN END WITH RC=8 AND MESSAGEAUTO-INDEXSPACE-TRANSLATE(N) ARE SPECIFIED ANDWITH DIFFERENT | ||||
2020 |
UI72348 |
DB2 CLONING TOOL - 3.2 SEPTEMBER PTF | |||
2020 |
DO NOT GENERATE PARTITION BY RANGE CLAUSE FOR AN INDEX THAT IS SPECIFIED WITH BUSINESS_TIME WITHOUT OVERLAPS CLAUSE | ||||
2020 |
DB2 CLONING TOOL - 3.2 AUGUST PTF | ||||
2020 |
INFINITY LOOP OCCURS IF TABLE SPACE HAS MORE THAN ONE MQT | ||||
2020 |
DB2 CLONING TOOL - 3.2 JUNE HIP PTF | ||||
2020 |
UI70843 |
ABEND S0C4 CAN OCCUR DURING PROCESSING JOB TEMPLATE WITH REPAIR STATEMENTS IN THE TARGET JOB | |||
2020 |
UI70843 |
DB2 CLONING TOOL - 3.2 JULY PTF | |||
2020 |
IMPLICIT LOB TS/IX MATCHING ERRORS IF BASE TS IS PBG AND SOURCE MORE PARTITIONS THAN TARGET TS | ||||
2020 |
DB2 CLONING TOOL - 3.2 JUNE PTF | ||||
2020 |
DB2 CLONING TOOL - 3.2 MAY PTF | ||||
2020 |
RACF-VIOLATION CAN OCCUR WHEN DB2 SUBSYSTEM CLONING FROM SLB | ||||
2020 |
DB2 CLONING TOOL - 3.2 APRIL PTF | ||||
2020 |
DB2 CLONING TOOL - 3.2 MARCH HIP PTF | ||||
2020 |
UI68721 |
DB2 CLONING TOOL - 3.2 MARCH PTF 20/03/17 PTF PECHANGE |
|||
2020 |
DB2 CLONING TOOL - 3.2 MARCH PTF | ||||
2020 |
DB2 CLONING TOOL - 3.2 FEBRUARY PTF | ||||
2020 |
SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001 NAME=CKZ00047 | ||||
2020 |
DB2 CLONING TOOL - 3.2 JANUARY PTF | ||||
2020 |
DB2 CLONING TOOL - 3.2 DECEMBER 2019 HIP PTF | ||||
2019 |
1. USE APPLCOMPAT IN TOOLS CUSTOMIZER AND SAMPLIB BIND SCRIPTS 2. MISCELLANEOUS FIXES IN ISPF INTERFACE | ||||
2019 |
DB2 CLONING TOOL - 3.2 NOVEMBER 2019 PTF | ||||
2019 |
UI66514 |
FIX GENERATION OF SUPPRESS-GRANTS KEYWORD IN THE SOURCE JCL JOB FROM ISPF INTERFACE | |||
2019 |
DB2 CLONING TOOL - 3.2 OCTOBER 2019 HIP PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 OCTOBER 2019 HIP PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 OCTOBER 2019 PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 SEPTEMBER 2019 PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 JULY 2019 HIP PTF | ||||
2019 |
ADD SUPPORT FOR DB2 SORT IN LOG APPLY | ||||
2019 |
LOGS ARE APPLIED TO INDEXES, SO THEY DO NOT NEED TO BE REBUILT. | ||||
2019 |
DB2 CLONING TOOL - 3.2 JULY 2019 PTF | ||||
2019 |
PE FIXER FOR UI62811 - EXPANDED DOCUMENTATION FOR APAR PH09578 19/07/05 PTF PECHANGE |
||||
2019 |
DB2 CLONING TOOL - 3.2 JUNE 2019 PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 MAY 2019 PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 APRIL 2019 HIP PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 APRIL 2019 PTF | ||||
2019 |
DB2 CLONING TOOL - 3.2 MARCH 2019 PTF | ||||
2019 |
REMOVE THE REQUIREMENT FOR BPX.FILEATTR.APF FOR LOG APPLY FUNCTIONALITY | ||||
2019 |
DB2 CLONING TOOL - 3.2 FEBRUARY 2019 PTF | ||||
2019 |
DOC PE FOR UI58442 | ||||
2019 |
DDL GENERATION WITH EXPLODE-OBJECTS(Y) COMPLETES WITH ERROR FOR TRIGGERS AND ROUTINES CREATED IN DB2 VERSIONS PRIOR TO V9 | ||||
2019 |
DB2 CLONING TOOL - PHXXXXX | ||||
2019 |
S0C4/S0C7 ABENDS IN DB2 CLONING TOOL SUBSYSTEM CLONING COPY COMMAND WHEN TARGET-UCATS-ON-TARGET-VOLUMES(Y) IS SPECIFIED. | ||||
2018 |
ABEND S0C1/S0C4 MAY OCCUR ON RI NESTING MORE THAN 40 LEVELS | ||||
2018 |
ADD DYNAMIC-ALIAS KEYWORD TO DB2UPDATE COMMAND | ||||
2018 |
DB2 CLONING TOOL | ||||
2018 |
ERROR IN PROCESSING INDEXES CLONED WITHOUT THEIR TABLE SPACES VIA TCP/IP. | ||||
2018 |
CATALOG FETCH FOR INDEXES THAT ARE CLONED WITHOUT THEIR TABLE SPACES FAILS WHEN EXCLUDE-MISMATCH-PROCESSING IS SET TO Y | ||||
2018 |
ADD SUPPORT FOR PERVASIVE DATA ENCRYPTION IN DFSMS AND DB2 VERSION 12 WITH FUNCTION LEVEL 502 | ||||
2018 |
INCORRECT PROCESSING OF PGSIZE FROM SYSIBM.SYSINDEXES FOR INDEXES THAT WERE CREATED PRIOR TO VERSION 9 | ||||
2018 |
DB2 CLONING TOOL - PHXXXXX | ||||
2018 |
IGNORE WARNING WITH SQLCODE +203 IN DB2SCHEMA-UPDATE COMMAND | ||||
2018 |
CLONING FROM AN IMAGE COPY THAT HAS MORE DATA SET EXTENSIONS THAN THE SOURCE OBJECT RESULTS IN ERRORS | ||||
2018 |
DEFINE ADDITIONAL INDEXES ON THE CATALOG FOR IMPROVING PERFORMANCE OF DB2SCHEMA-UPDATE | ||||
2018 |
CHECK-DATASET-COMPATIBILITY FAILS DURING IDCAMS LISTCAT PROCESSING WHEN SOURCE HAS MORE PARTITIONS THAN TARGET | ||||
2018 |
SRCE JOB S378 ABEND DURING TRGT CTLG PREFETCH PROCESSING IF CAF OR DDF CONNECTION AND TRGT PREFETCH DBASE LIST NOT SPECIFIED | ||||
2018 |
REDUCE MEMORY USAGE WHEN COPYING STATISTICS DURING TABLE SPACE CLONING | ||||
2018 |
ALWAYS GENERATE ALTER SEQUENCE RESTART WITH SQL FOR USER-DEFINEDSEQUENCES | ||||
2018 |
DDL CAN BE GENERATED WITH THE WRONG VALUES FOR DECIMAL DATA TYPEON A DB2 SUBSYSTEM WITH BIF_COMPATIBILITY=V9_DECIMAL_VARCHAR | ||||
2018 |
PARTITIONED TABLE SPACES ARE NOT STARTED IN THE TARGET JOB IF SUBTASK-DATASET-EXTENSION(Y) IS SPECIFIED WITH | ||||
2018 |
DB2 CLONING TOOL INSTALLATION VERIFICATION PROCESS | ||||
2018 |
THE BIND SCRIPTS FOR DB2 VERSION 12 MUST INCLUDE THE DBRM MODULES FOR BOTH DB2 VERSION 12 AND VERSION 11 | ||||
2018 |
DB2 CLONING TOOL | ||||
2018 |
ADD EXECUTE-CREATE-DDL(Y/N) PARAMETER TO DB2SCHEMA-UPDATE COMMAND | ||||
2018 |
OBJECTS WITH SAME SOURCE AND TARGET DATA SET NAME SHOULD NOT BE EXCLUDED FROM CLONING WHEN DATA-MOVER PGM(NONE) IS USED | ||||
2018 |
IF SOURCE JOB ENDS WITH RC=4 AND MESSAGE CKZ70804W IS ISSUED, THE TARGET JOB MIGHT END WITH RC=8 AND MESSAGE CKZ70808E | ||||
2018 |
REPAIR STATEMENTS SHOULD BE GENERATED WITH CLONE ATTRIBUTE FOR CLONE INSTANCES | ||||
2018 |
SOURCE JOB HANGS IF INDEX SPACE DATA SET IS NOT CATALOGED | ||||
2018 |
CHANGE CKZ23526W TO CKZ23526E TO MATCH THE SEVERITY OF THE CONDITION BEING REPORTED | ||||
2018 |
ADD DATA SET CLEANUP JOB EXAMPLE FOR USING WITH COPY-BY-DS | ||||
2018 |
SOURCE JOB STAYS UNAWARE OF DDL EXECUTION FAILURE IF TCP/IP OR DDF CONNECTION IS USED | ||||
2018 |
ENHANCE SUBSYSTEM CLONING TO ALLOW TARGET ICF CATALOGS TO BE ON THE TARGET VOLUMES | ||||
2018 |
PROVIDE MORE CUSTOMER-FRIENDLY JOB TEMPLATES FOR FUZZY-COPY(Y) TABLE SPACE CLONING SCENARIOS | ||||
2018 |
PRINT REQUIRED SYNCDB2 PARAMETERS FOR CLONE INSTANCES FOR REPAIRUTILITY | ||||
2018 |
IEC070I 209-220 ERROR DURING LOG APPLY PROCESSING WHEN DATA-MOVER IS SET TO PGM(ADRDSSU) OR PGM(EMCAPI) | ||||
2018 |
RENAME THREE OF THE VOLOPTIONS KEYWORDS | ||||
2018 |
DATABASE DDL IS NOT GENERATED IF RELATED OBJECTS EXIST ON THE TARGET | ||||
2018 |
KEEP TARGET VOLUMES IN SAME STORAGE GROUP WHEN SOURCE VOLUMES ARE IN SAME SOURCE STORAGE GROUP DURING SUBSYSTEM CLONING | ||||
2018 |
PROVIDE SAMPLE WORKFLOW FOR TABLE SPACE CLONING VIA Z/OSMF | ||||
2018 |
DB2 CLONING TOOL MAY NOT GENERATE REBUILD STATEMENTS WHEN NEEDEDIF INDEX SPACES ARE CLONED WITHOUT THEIR TABLE SPACES. | ||||
2018 |
ABENDS AND ERRORS DURING RENAME PROCESSING ON SYSTEMS WITH MORE THAN 100 STATIC SYSTEM SYMBOLS DEFINED. | ||||
2018 |
SUPPORT MULTI-FACTOR AUTHENTICATION | ||||
2018 |
DO NOT ADD QUALIFIER TO THE CONSTANT STRING VALUES | ||||
2018 |
END THE SOURCE JOB WITH RETURN CODE 8 WHEN WARNINGS OCCUR IN THESOURCE JOB AND MAX-RC(0) IS USED | ||||
2018 |
CHECK-DATASET-COMPATIBILITY FAILS DURING IDCAMS LISTCAT PROCESSING WHEN SOURCE OBJ HAS MORE EXTENSIONS THAN TARGET OBJ |
||||
2018 |
LISTDEF PROCESSING ISSUES | ||||
2018 |
SKIP CLONING INDEXES THAT NEED TO BE REBUILT | ||||
2018 |
ONLY ONE STORED PROCEDURE/FUNCTION FOR A TABLE IS INCLUDED IN GENERATED DDL ON DB2 V11 CM | ||||
2018 |
INVALID DDL GENERATED FOR STORED PROCEDURE | ||||
2018 |
WHEN AN INVALID MASK IS SPECIFIED IN OBJECT-TRANSLATE RULE, MESSAGE CKZ00012E IS ISSUED | ||||
2018 |
WHEN PROCESS-TYPE(A), DDL GENERATION DOES NOT CORRECTLY GENERATEDDL (TABLE SPACE CLONING, DDL) | ||||
2018 |
ABEND S0C4 MIGHT OCCUR IF A TABLE SPACE THAT CONTAINS NO TABLES IS CLONED USING AUTO-TABLESPACE-TRANSLATE(Y) | ||||
2018 |
CLONING FROM DB2 V12 WITH DDL GENERATION ENABLED ENDS WITH RC=8 AND MESSAGE CKZB209E IS ISSUED FOR SQLCODE=-305 IN CKZCIX2C.C | ||||
2018 |
CHANGE DDL GENERATOR EXPLODE LOGIC | ||||
2018 |
DB2UPDATE IS USED TO RENAME STORAGE GRPS WITH TRAILING SPACES IN ITS NAME, COMMAND ENDS WITH RC=8 AND CKZ22460E MSG IS ISSUED |
||||
2018 |
MISCELLANEOUS FIXES IN DDL GENERATION FOR DB2 V11 CM | ||||
2018 |
TARGET JOB ENDS WITH RC=0 WHEN REBUILD INDEX ENDS WITH RC=4 | ||||
2018 |
MISCELLANEOUS FIXES FOR LOG APPLY | ||||
2018 |
DDL GENERATION ENDS WITH OC1 ABEND WHEN OBJECT TRANSLATION IS USED FOR LONG OBJECT CREATOR OR NAME | ||||
2018 |
REPAIR UTILITY ISSUES MSG "DSNU667I - SOME PARTITIONS IN THE PAGE SET WERE COPIED WITH DSN1COPY, AND SOME WERE NOT" | ||||
2018 |
ALLOW DNS NAMES TO BE USED FOR TCP/IP CONFIGURATIONS | ||||
2018 |
END THE SOURCE JOB WITH AN ERROR MESSAGE WHEN ERRORS OCCUR DURING CLONING AND MAX-COPY-RC(0) IS USED | ||||
2018 |
ADD REUSE(Y/N) KEYWORD AND SMS CLASSES FOR ALLOCATION PARAMETERSOF TARGET DATA SETS | ||||
2018 |
IMPROVE REBUILD-INDEXES-EXECUTE AND INTELLIGENT-REBUILD LOGIC | ||||
2018 |
INCORRECT RC WHEN SDSNLOAD IS NOT SPECIFIED IN THE SOURCE JOB | ||||
2018 |
TREAT SQLCODE = 162 AS A WARNING AND NOT AS AN ERROR | ||||
2018 |
ALTER COLUMN RUN ON AN IDENTITY COLUMN IN A TABLE WITH VERSIONING CAUSES AN ERROR | ||||
2018 |
EXTRA SPACES IN COMMENT CHARACTER STRINGS GENERATED IN DDL FOR CREATE PROCEDURE | ||||
2018 |
SQLCODE=-206 IN DB2 V11 CM/V11 NFM TABLESPACE CLONING BINDS FOR CKZCTS2C, CKZCTB2C, CKZCIX2C | ||||
2018 |
INVALID DDL IS GENERATED FOR PUBLIC ALIAS | ||||
2018 |
DB2XCFCLEAN JOB IS NOT BEING GENERATED FOR DATASHR-ATTR = FEWER | ||||
2018 |
SCHEMA NAME WAS NOT TRANSLATED | ||||
2018 |
THE SOURCE TCP/IP SERVER JOB MAY END WITH ABEND S0C4 IF TARGET LOG APPLY IS USED | ||||
2018 |
UNSUCCESSFUL BIND USING BIND-ON-TARGET=Y | ||||
2018 |
USE IBM LISTDEF IN CLONING TOOL | ||||
2018 |
USE SYSIBM.SYSDEPENDENCIES TABLE TO BUILD THE MAP BETWEEN OBJECTS | ||||
2018 |
THE SOURCE JOB FINISHES WITH ERROR IF MAX-RC=0 AND ONLY CKZ535103W WARNING MESSAGE OCCURS | ||||
2018 |
CREATE COMPLETE DDL FOR TARGET SYSTEM WHEN CLONING RFE 74602 | ||||
2018 |
MISCELLANEOUS FIXES | ||||
2018 |
ENHANCE VERSIONING SUPPORT FOR DB2 EPIC 37738 | ||||
2018 |
RTS IS NOT GATHERED WHEN DATA-MOVER PGM(NONE) IS USED | ||||
2018 |
CKZ00547 MAY GO INTO A LOOP IF UNLOAD/LOAD DATA SET PROCESSING ENCOUNTERS ONE OF UNLOAD'S RESTRICTIONS | ||||
2018 |
MISCELLANEOUS FIXES | ||||
2018 |
CANDIDATE VOLUMES NOT ADDED IF DATACLASS IS NULL | ||||
2018 |
INCORRECT VOLUME SIZE BEING USED FOR EAV VOLUMES BY RESTORE-FROM-DUMPTAPES AND DB2GETBACKINFO | ||||
2018 |
WRONG DDL GENERATION FOR HISTORY TABLES WHEN ENABLE-PREFETCH(Y) IS SPECIFIED | ||||
2018 |
TARGET TCP/IP SERVER JOB ABENDS IF TARGET CATALOG PREFETCH IS ENABLED FOR DB2 V11 IN CM MODE | ||||
2018 |
CHECK-DATASET-COMPATIBILITY DOES NOT WORK WITHOUT SHARED DASD | ||||
2018 |
CLONING TOOL SHOULD HANDLE DATASET PLACEMENT FOR NEWLY ALLOCATED DATASETS CORRECTLY. RFE 29884 | ||||
2018 |
PROVIDE AN OPTION IN DB2START TO STOP WAITING IF DB2 TERMINATES DURING STARTUP IN ISPF UI AND EXPORT/IMPORT BATCH UTILITY | ||||
2018 |
USE EMPTY DEFAULT VALUES FOR MINILOG-HLQ AND RTSFILE-DATA-SET-HLQ IN ISPF UI AND EXPORT/IMPORT BATCH UTILITY |
||||
2018 |
USER ABEND 0012 IN MODULE CKZ#LGAP | ||||
2017 |
MEMORY LEAKS IN TCP/IP SERVER CODE | ||||
2017 |
MISCELLANEOUS FIXES | ||||
2017 |
IMPROVE THE PROCESSING OF CMDDDNAME IN ISPF UI | ||||
2017 |
CKZ61325W SQL ERROR IN MODULE CKZ07182 WITH SQL ERROR SQLCODE -991 | ||||
2017 |
ADD REQUIRED OBJECT-MISMATCH-RETURN-CODE TO ALL COMPONENTS | ||||
2017 |
ALWAYS USE VOLCOUNT(ANY) AND TGTALLOC(SRC) FOR THE CALL TO ADRDSSU COPY UTILITY | ||||
2017 |
WRONG LIMITKEY GENERATED FOR INDEX- AND TABLE-CONTROLLED PARTITIONED OBJS WHEN DATE/TIMESTAMP COL NOT INCLUDED | ||||
2017 |
INCORRECT KEYWORD BEING GENERATED FOR DDF ALIAS NAME PARAMETER | ||||
2017 |
CHECKING THE EXISTENCE OF SYSTEM PAGE OF SPECIFIED VERSION | ||||
2017 |
THE STORED PROCEDURE SHOULD OPEN THE CKZINI WITH ONLY READ INTENT | ||||
2017 |
CKZ54736I MESSAGE RFE 36343 | ||||
2017 |
MISCELLANEOUS FIXES | ||||
2017 |
RESTORE-FROM-DUMPTAPES RERUN IS NOT PUTTING ALL VOLUMES INTO VOLPAIRS | ||||
2017 |
GRAPHIC DEFAULT VALUES ARE GENERATED INCORRECTLY FOR TABLES | ||||
2017 |
ENHANCED HANDLING FOR DOCID WHILE CLONING XML TABLES - GENERATE A NEW, UNUSED DOCID FOR THE TARGET ENVIRONMENT | ||||
2017 |
CREATE JOB TEMPLATE TO COPY CONSISTENT FLASHCOPY DATA SETS TO DB2 DATA SETS USING STERLING CONNECT:DIRECT | ||||
2017 |
CHANGE THE PROCESSING OF ALTER TABLE FOR IDENTITY COLUMNS WITH SIM(A) | ||||
2017 |
BCSCLEAN CLEANUP-CATALOG-ORPHANS SHOULD CHECK FOR USER CATALOG DUPLICATES | ||||
2017 |
USE DOCUMENTED MESSAGES INSTEAD OF TRACE IN THE OUTPUT FOR CLEANUP-CATALOG-ORPHANS | ||||
2017 |
VSAM TO VSAM COPY - LOG APPLY DB2 OBJECT COPY WITH OR WITHOUT APPLYING LOGS | ||||
2017 |
CKZ1S061E TASK EXECUTION ENDED WITH ERROR: .... MN_STATUS UNEXPECTED CONDITION | ||||
2017 |
POSSIBLE CKZ25536E WHEN USING DATASHR-ATTR =NONDS IN STORED PROCEDURE | ||||
2017 |
SUPPORT REBUILD INDEX (ALL) | ||||
2017 |
CLONE USING TABLE NAME ON SOURCE AND TARGET INSTEAD OF TABLESPACE AND INDEXSPACE NAMES | ||||
2017 |
UNEXPECTED CKZ421E MESSAGE IN THE CKZ1STSS PANEL | ||||
2017 |
CKZ#BIND DOES NOT SUPPORT GANAME | ||||
2017 |
UPDATE CKZ01CIO MODULE | ||||
2017 |
CKZ99041E SUBTASK 01, TABLE NOT FOUND BY OBID = 1163 | ||||
2017 |
NEW USE-LAST-CONSISTENT-FLASHCOPY(Y/N) KEYWORD IN COPY COMMAND | ||||
2017 |
MESSAGES IN CKZ2SUTL UTILITY SHOULD PROVIDE MORE INFORMATION FORUSERS | ||||
2017 |
INFINITE LOOP IN UNMATCHED INDEXES PROCESSING CODE | ||||
2017 |
ERROR IN THE GENERATION OF DDL FOR PARTITIONED BY RANGE TABLESPACES | ||||
2017 |
POSSIBLE CKZ02347E EMCSAI ERROR: DEVICSSTATUS RETURN CODE=12 REASON CODE=61 LOC=DEV61 | ||||
2017 |
REBUILD INDEX ENHANCEMENTS / RFE74185 | ||||
2017 |
CLONING TOOL AND REALTIME STATS - OPTION TO COPY DB2 RTS STATS WITHIN THE JOBS FOR TABLESPACE CLONING | ||||
2017 |
DETECT AND REBUILD TARGET-ONLY ("UNMATCHED") INDEXES | ||||
2017 |
SPLIT THE UNLOAD/LOAD PROCESS BETWEEN SOURCE AND TARGET JOBS | ||||
2017 |
LOG CONVERSION ERROR: TYPE 02000009 (DBD VIRTUAL MEMORY COPY) CAN CAUSE A SOC4 ABEND IN CKZ#LRDR OFFSET=0000A452 | ||||
2017 |
CKZ56401E - RC=X'000003EA ERROR CAN OCCUR WHEN APPLYING RECORDS TO A LOB TABLESPACE | ||||
2017 |
POSSIBLE CKZ07062E SHOWING AN INVALID STORAGE GROUP NAME | ||||
2017 |
WRONG PROCESSING OF PGSIZE FROM SYSIBM.SYSINDEXES FOR INDEXES THAT WERE CREATED PRIOR TO VERSION 9 | ||||
2017 |
OBJECT-TRANSLATE FOR DATABASE AND TABLESPACE DOES NOT WORK PROPERLY IF NAME IS LESS THAN 8 CHARACTERS | ||||
2017 |
OPTION TO GENERATE UNLOAD/LOAD TEMPLATES WHEN MISMATCHES ARE DETECTED | ||||
2017 |
CLONING OF IMPLICIT LOB AND XML TABLESPACES. | ||||
2017 |
ALLOCATION ERROR WHEN USING CONSISTENT FLASH COPY IMAGE COPIES. | ||||
2017 |
BATCH UTILITY TO EXPORT/IMPORT DB2 CLONING TOOL PROFILES | ||||
2017 |
ENHANCEMENT TO AUTOMATICALLY SET A COMMON TO_LOGPOINT FOR MULTIPLE OBJECTS. | ||||
2017 |
NEW PARAMETER CALLED GMT_OFFSET TO ENABLE PROCESSING IMAGE COPIES AROUND DAYLIGHT SAVINGS SWITCH. | ||||
2017 |
ADD OPTION TO CKZDUTST TO ALLOW OBJECTS IN UTXX STATUS TO NOT BESTARTED IN RW STATUS | ||||
2016 |
ALLOW SPECIFICATION OF DATA SHARING GROUP | ||||
2016 |
REQUIRED REBUILD OF INDEX MAY NOT BE GENERATED IF SOURCE AND TARGET INDEX HAVE MISMATCHED PADDED / NOT PADDED SETTINGS | ||||
2016 |
CLONE FROM IMAGE COPY W/IMAGE COPIES ON TAPE ENDS WITH CKZ56401ESUBTASK 01, COMPLETED W/ERRORS, RC=X'000003F0, RS=X'00NNNNNN' | ||||
2016 |
PROVIDE EXPLOITATION SUPPORT FOR FUTURE DB2 ENHANCEMENTS | ||||
2016 |
BROKEN PAGE WHEN PROCESSING UNCOMMITTED RECORDS ON A TABLESPACE WITH DATA CAPTURE TURNED ON DURING LOG APPLY. | ||||
2016 |
THE DB2UTILXCLEAN COMMAND DOES NOT WORK WITH THE COPY-BY-DS COMMAND | ||||
2016 |
S04E REASON X'00C90101' IN REBUILD INDEX UTILITY AFTER CLONING ANON PARTITIONED MULTIDATASET TABLESPACE FROM IMAGE COPY. | ||||
2016 |
UTS TABLESPACE INSERT ON A PRE-EXISTING PSEUDO-DELETED RID REQUIRING HOLES TO BE CONDENSE FIRST | ||||
2016 |
RESOLVE ISSUE WHERE NOOP LOG RECORDS WERE INADVENTENLY BEING PROCESSED. | ||||
2016 |
POSSIBLE CKZ07073E WHEN THE VOLUMES HAVE MULTIPLE SIZES | ||||
2016 |
ISPF UI NOT CREATING CONDITIONAL RESTART RECORD FOR SLB CLONING | ||||
2016 |
POSSIBLE CKZ27140E ERROR FROM THE DB2ALTERBSDS SLB-START COMMAND | ||||
2016 |
SOURCE JOB WITH LOG APPLY ENABLED FAILED WITH CKZ00004E ERROR ONOPERAND TRUNCATED FOR: LOG-APPLY | ||||
2016 |
DDL FOR XML TABLES NOT CREATED CORRECTLY IF COLUMNS ARE SUBSEQUENTLY ADDED WITH ALTER | ||||
2016 |
BSDS DATASETS NOT CORRECT IF CLONING FROM SECONDARY MEMBERS | ||||
2016 |
POSSIBLE CKZ04635A SPANNED RECORD ERROR | ||||
2016 |
AUTOMATED DETECTION OF A VERSIONS MISMATCH AND GENERATION OF REPAIR VERSIONS | ||||
2016 |
SUPPORT DB2 RULES FOR PRIMARY AND SECONDARY SPACE ALLOCATION | ||||
2016 |
CKZ00066E SUBTASK 01, REBUILD, ALLOC DDNAME(SYSIN) | ||||
2016 |
ENHANCEMENT TO SPECIFY COMMON TO_LOGPOINT AND OTHER LOG-APPLY PARAMETERS FOR MULTIPLE PROFILES / JOBS. | ||||
2016 |
USABILITY COMMANDS ADDED TO LOG APPLY | ||||
2016 |
CREATE A LOG APPLY REPORT | ||||
2016 |
LIMIT IS TOO SMALL FOR THE NUMBER OF ENTRIES IN EXCLUDE-FROM-VOLSER AND EXCLUDE-TO-VOLSER | ||||
2016 |
RESTORE-FROM-DUMPTAPES CAN FAIL WHEN ALL DUMPS ARE ON A SINGLE TAPE | ||||
2016 |
COPY COMMAND RUNNING EXCESSIVELY LONG WITH EMC SNAP AND MANY VOLUMES | ||||
2016 |
PROVIDE TOLERATION SUPPORT FOR FUTURE DB2 ENHANCEMENTS | ||||
2016 |
POSSIBLE S0C4 IN CKZ00215 WITH DB2GETBACKINFO USE-DUMPTAPES WHENA DUMP SPANS MORE THAN 6 TAPES | ||||
2016 |
ADD SUPPORT FOR USER CREATED SYSTEM-LEVEL BACKUPS TO SUBSYSTEM CLONING STORED PROCEDURE | ||||
2016 |
VOLUME CLIP MAY FAIL WHEN ICKDSF APAR PI25913 HAS BEEN APPLIED | ||||
2016 |
POSSIBLE CKZ02081E WITH IOSCDR RC=4 RSN=C | ||||
2015 |
ROLL UP APAR FOR TABLE SPACE CLONING POST GA | ||||
2015 |
TARGET JOB S0C4 IN MODULE CKZ00760 | ||||
2015 |
ROLL UP APAR FOR SUBSYSTEM CLONING POST GA | ||||
2015 |
SQLCODE104 IN SOURCE JOB DDL GENERATION CKZ76713E | ||||
2015 |
ABENDS0C3 IN RENAME COMMAND WHEN RUNNING SUBSYSTEM CLONING ON Z/OS 2.2 V22 | ||||