DB2 Recovery Expert for z/OS Version 3.2
|
|||||
APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
---|---|---|---|---|---|
2024 |
TABLE SPACES AND INDEXES ARE RECOVERED IN DIFFERENT JOBS WHEN PARALLELISM IS ENABLED. | ||||
2024 |
'ARYS004I - NO RELATIONSHIP EXISTS...' IF COPY POOL VERSIONS=0 | ||||
2024 |
ADD V13R1M506 AS A POSSIBLE VALUE FOR TCZ VARIABLE "DB2 APPLCOMPAT BIND OPTION" | ||||
2024 |
SQLERROR = -304 IN THE ARYLBB4U MODULE | ||||
2024 |
IMPROVEMENTS TO RECOVERY TIME OBJECTIVES AND PREDICTIONS. | ||||
2024 |
IMPROVEMENTS TO RECOVERY TIME OBJECTIVES AND PREDICTIONS. | ||||
2024 |
ABEND0C9 IN ARYLJGCX | ||||
2024 |
IMPROVE ERROR HANDLING NEAR THE MEMORY BOUNDARIES. | ||||
2024 |
ADD CAPABILITY TO MANAGE PARAMETER SMSDSEXIST IN ICKDSF FOR OPTION: REINIT SPACE EFFICIENT VOLUMES. | ||||
2024 |
GROUP NAME IS USED INSTEAD OF THE MEMBER NAME WHERE IT IS POSSIBLELE. | ||||
2024 |
GENERATE CRESTART=CANCEL STEP FOR NON-RESTARTED MEMBERS. | ||||
2024 |
ADD VALIDATE TRANSLATION TO GUI. | ||||
2024 |
IMPROVE DSNINFO ALLOCATION. | ||||
2024 |
SETUP NOT REPORTING ON VOLUME PAIRS PROBLEM | ||||
2024 |
UI97971 |
POSSIBLE ABEND0C4 OR MISSING INDEX PARTITIONS IN THE "RESOLVE RECOVER/REBUILD PENDING OBJECTS" JOB. | |||
2024 |
FIX COMPATIBILITY ISSUES WITH IMS RE -( ABENDS0C4, S0C4 ) | ||||
2024 |
DFMSMSDSS BACKUP ERROR MSGADR171T 1021+ VOLUME | ||||
2024 |
SHORTAGE OF SERVER MEMORY DURING VULNERABILITY SCANNING. | ||||
2024 |
SYSAFF PARAMETER IS UNCONDITIONALLY ADDED TO THE TRANSACTION RECOVERY JOB (GUI) | ||||
2024 |
ERROR DURING REDIRECTED RECOVERY BUILD JCL. | ||||
2024 |
MISCELLANEOUS FIXES | ||||
2024 |
UI97200 |
V13R1M505 TOLERATION | |||
2024 |
MISCELLANEOUS FIXES | ||||
2024 |
INTERNAL FIXES FOR SYSTEM-LEVEL OPERATIONS. | ||||
2024 |
STATUSES OF OBJECTS ARE NOT RESET AFTER RECPEND STEP. | ||||
2024 |
REDESIGN MASS APPLICATION RECOVERY. | ||||
2024 |
OFFLOAD ENDS WITH RETURN CODE 00 EVEN IF HSM ENDS WITH RC 002E | ||||
2024 |
DUPLICATE REBUILD INDEX STEPS ARE GENERATED AFTER RESTORE SYSTEM. | ||||
2024 |
SECONDARY ARCHIVE LOGS ARE NOT TAKEN INTO ACCOUNT FOR RECOVERY. | ||||
2024 |
PAGENUM PARAMETER IS NOT GENERATED | ||||
2024 |
ABEND S0C4 IN MODULE = ARYLJGTA, OFFSET = 000004E4 | ||||
2024 |
MISCELLANEOUS FIXES. 24/02/15 PTF PECHANGE |
||||
2024 |
MISCELLANEOUS FIXES. | ||||
2024 |
MISCELLANEOUS FIXES. | ||||
2024 |
ADD SUPPORT FOR UTILITY HISTORY TABLES. | ||||
2024 |
ADD SUPPORT FOR UTILITY HISTORY TABLES. | ||||
2024 |
ADD SUPPORT FOR TLS 1.3 | ||||
2023 |
ONLY THE UNDO SQL PLAN IS GENERATED | ||||
2023 |
SLR UPDATE DOESN'T PROCESS COPYTOCOPY RECORDS CORRECTLY. | ||||
2023 |
POSSIBLE ARYA440E DURING THE DB2 CATALOG SCAN | ||||
2023 |
POTENTIAL ERROR WHEN ACCESSING WEB SPECIFICATION. | ||||
2023 |
INTERNAL FIXES FOR SYSTEM-LEVEL OPERATIONS | ||||
2023 |
V13R1M504 TOLERATION | ||||
2023 |
ADD SUPPORT FOR ARCHIVE TABLE SELECTION. | ||||
2023 |
CONSISTENT JCL MEMBER NAMES VIA ONLINE AND BATCH FACILITY. | ||||
2023 |
USE RECOVER EVENTS AS A BASE FOR RECOVERY | ||||
2023 |
ALLOW USE OF THE REUSE KEYWORD ON BASIC/NON-ADVANCED RECOVERY PLANS. | ||||
2023 |
ARY#YARC - WAITING 15 SECONDS MESSAGE REPETITION | ||||
2023 |
RECOVER A SINGLE TABLE AND RESOLVE CHECK PENDING FOR RELATED TABLES. | ||||
2023 |
Description not available. Security/Integrity exposure | ||||
2023 |
REMOVE ACEE CONTROL BLOCK ALTERATION. | ||||
2023 |
MISCELLANEOUS FIXES | ||||
2023 |
MISCELLANEOUS FIXES | ||||
2023 |
USE RECOVER FOR COPY YES INDEXES IN REDIRECTED RECOVERY. | ||||
2023 |
IMPROVE MIGRATION PROCEDURE. | ||||
2023 |
ELIMINATE DISPLAY LIMIT WHEN EXPLODING APPLICATION PROFILES | ||||
2023 |
REPORT NUMBER OF TRACKS TO BE COPIED DURING THE BACKUP. | ||||
2023 |
WEB UI IS NOT AVAILABLE IF IPV4 ADDRESS IS SPECIFIED. | ||||
2023 |
DESCRIPTION FOR ARY DSN PREFIX VARIABLE IS INCORRECT. | ||||
2023 |
MISSING PACKAGES IN ARYBIND1 FOR DB2 V13 FL100 | ||||
2023 |
REDUCE MEMORY USAGE | ||||
2023 |
ADD SUPPORT FOR VARIANT CHARACTERS IN THE SPACE NAMES. | ||||
2023 |
ADD SUPPORT FOR VARIANT CHARACTERS IN THE SPACE NAMES. | ||||
2023 |
Description not available. Security/Integrity exposure | ||||
2023 |
INTERNAL IMPROVEMENTS | ||||
2023 |
POSSIBLE S0C4 ABEND DURING JCL GENERATION | ||||
2023 |
DATABASE AND TABLESPACE IS NOT TRANSLATED FOR MQT | ||||
2023 |
ISSUE DURING PROCESSING OF SEGMENTED TABLE SPACE WITH MULTIPLE TABLES WHERE SOME OF THE TABLES WERE PREVIOUSLY DELETED. | ||||
2023 |
ARC0059I, ARC1006I AND IKJ56238I ERRORS DURING LOG DATA SETS RECALL. | ||||
2023 |
POSSIBLE ABEND WHEN OPENING APPLICATION PROFILE PANEL 23/04/21 PTF PECHANGE |
||||
2023 |
SUPPORT FOR PRDID CHANGE. | ||||
2023 |
ABEND U0501 ON PLAN VALIDATION | ||||
2023 |
SQLCODE = -805 IN PLAN ARYP3202 FOLLOWING DB2 13 MIGRATION | ||||
2023 |
RESOLVE REC/REB PENDING OBJECTS TO Y IN THE RESTORE OPTIONS, THE LOG RESTORE MEMBER WILL HAVE DUPLICATE ARYPOBJS DD | ||||
2023 |
ISSUES WHEN RESOLVE RECOVER/REBUILD PENDING OBJECTS IS ENABLED | ||||
2023 |
VARIOUS INTERNAL FIXES 23/04/21 PTF PECHANGE |
||||
2023 |
VARIOUS INTERNAL FIXES | ||||
2023 |
LOW PERFORMANCE OF RESOURCE SELECTION | ||||
2023 |
ARYS917E IS SHOWN INCORRECTLY. | ||||
2023 |
MESSAGE ARYR749W IS ISSUED INCORRECTLY | ||||
2022 |
SUPPORT DB2 LOAD LIBRARIES PLACED ON NON-SHARED DASD | ||||
2022 |
POSSIBLE 0C4 IN ARYDTL4 | ||||
2022 |
TYPE COLUMN IS MISSING IN ARYMIG1 TEMPLATE. | ||||
2022 |
ARYX094S WHEN AN OBJECT HAS MORE THAN 16 INCREMENTAL IMAGE COPIES | ||||
2022 |
&UID VARIABLE IS NOT PROCESSED IN THE IC MASK. | ||||
2022 |
CHECK DATA IN THE WRONG JOB IF PARALLELIZATION IS ENABLED | ||||
2022 |
DISCOVER EXEC ABENDS WITH S0C4 | ||||
2022 |
"ARYX093S--AN UNEXPECTED ERROR OCCURRED (./PITHELPER.CPP,260)." MAY OCCUR WHILE GENERATING THE RECOVERY PLAN. | ||||
2022 |
MESSAGE ARYS200E - LOADLIB DATASET: ... SHOULD BE INFORMATIONAL | ||||
2022 |
SUPPORT FOR DB2 V13 FL502 | ||||
2022 |
ABSTRACT: POTENTIAL ERROR DURING JCL GENERATION | ||||
2022 |
UI83405 |
TASK HANG WHEN SSID IS INACTIVE | |||
2022 |
UI83405 |
A CONDITIONAL RESTART RECORD IS NOT INSERTED IF A RECOVERY LRSN IS FFFFFFFFFFFFFFFFFFFF | |||
2022 |
S0C1 DURING PLAN GENERATION | ||||
2022 |
ISSUES IN LOG BASED RECOVERY | ||||
2022 |
LOW PERFORMANCE OF A QUERY TO SYSTABLEPART DURING PLAN GENERATION | ||||
2022 |
INCORRECT BUFFER POOL VALUE IN ARYCHIX TEMPLATE | ||||
2022 |
SERVER POTENTIALLY HANGS AFTER THE SCAN UTILITY | ||||
2022 |
S0C9 DURING PLAN GENERATION | ||||
2022 |
SHORT APPLCOMPAT PROCESSED INCORRECTLY. | ||||
2022 |
Q3 ROLLUP APAR | ||||
2022 |
UI82672 |
WEB UI SECURITY IMPROVEMENTS | |||
2022 |
Q3 ROLLUP APAR | ||||
2022 |
SA78 WHEN GENERATING A SYSTEM RESTORE JOB FROM WEB INTERFACE | ||||
2022 |
UPDATE SLB-RELATED MESSAGES | ||||
2022 |
POSSIBLE 0C4 ABEND IN ARYSUBGC | ||||
2022 |
SYCOPY RECORDS ARE DISCARDED ON DATA SHARING SUBSYSTEMS IN SOME CASES | ||||
2022 |
FOREIGN KEY IS NOT RECREATED IN LOG-BASED RECOVERY | ||||
2022 |
ARY1479E ERROR DUE TO INCORRECT INCREMENTAL IMAGE COPY PROCESSING | ||||
2022 |
POSSIBLE S0C4 DURING JCL GENERATION | ||||
2022 |
ARYU089E ERROR IN TRANSACTION RECOVERY TAB | ||||
2022 |
INCORRECT DATABASE NAME FOR ARYES7 TABLESPACE IN ARY15021 TCZ TEMPLATE. | ||||
2022 |
WEB UI WELCOME MESSAGES HAVE INCORRECT FORMATTING | ||||
2022 |
ABEND=40D DURING LOAD SLR | ||||
2022 |
REPLACE 3DES WITH AES | ||||
2022 |
THE "WAITING 15 SECONDS" MESSAGE REPETITION. | ||||
2022 |
EXTERNALIZE START/END BACKUP MESSAGES | ||||
2022 |
INVALID CONVERSION OF COPYPAGESF VALUE | ||||
2022 |
POSSIBLE SERVER HANGUP AFTER SECURITY SCAN | ||||
2022 |
VARIOUS IMPROVEMENTS FOR RECOVERY EXPERT V3.2.0 | ||||
2022 |
SUPPORT FOR DB2 VERSION V13 | ||||
2022 |
SUPPORT FOR DB2 VERSION V13 | ||||
2022 |
SUPPORT FOR DB2 VERSION V13 | ||||
2022 |
UI83846 |
HANDLE EMPTY SLB ENTRY | |||
2022 |
UI81023 |
LOW PERFORMANCE FOR SYSCOPY SELECTS. | |||
2022 |
MESSAGE CONVERSION FAILED IN THE AGENT LOG | ||||
2022 |
MESSAGE CONVERSION FAILED IN THE AGENT LOG | ||||
2022 |
UI80083 |
POSSIBLE S0C4 ABEND AFTER DB2SORT INITIALIZATION CALL | |||
2022 |
AN SQL ERROR OCCURS WHILE RESTORING A TABLE WITH GRAPHIC DATA | ||||
2022 |
UPDATE BINDING FILES | ||||
2022 |
BACKUP GENERATIONS VALUE IS ALWAYS 0 FOR SYSTEM BACKUP PROFILES WITH DB2 BACKUP METHOD | ||||
2022 |
THE "WAITING 15 SECONDS" MESSAGE REPETITION | ||||
2022 |
IMAGE COPY FOR MULTIVOLUME OBJECTS IS POTENTIALLY INCORRECT | ||||
2022 |
UI79234 |
CORRECT THE DATASHARING STATUS ON ISPF SSID SELECTION PANEL | |||
2022 |
S0C1 ON ARYGMSQT PANEL | ||||
2022 |
UI79234 |
INCORRECT TRANSLATION OF OBJECTS WITH DSNDBNN MASK | |||
2022 |
UI79234 |
VERSIONED TABLESPACE IS NOT REPAIRED AFTER RDR | |||
2022 |
S0C1 ON ARYGMSQT PANEL | ||||
2022 |
UI79234 |
REDESIGN THE WEB UI LOGIN PROCESS | |||
2022 |
UI79234 |
RECOVERY HISTORY EVENTS ARE UNLIMITED | |||
2022 |
UI79234 |
POSSIBLE TSO SESSION HANGING WHEN DDL GENERATION IS SELECTED. | |||
2022 |
UI79234 |
MISSED CREATEDBY COLUMN IN MIGRATION SCRIPT | |||
2021 |
UI78281 |
POSSIBLE ABEND SOC4 DURING REDIRECTED RECOVERY | |||
2021 |
UI78281 |
CNK046E SORT CAPACITY EXCEEDED ERROR DURING REDIRECTED_RECOVERY USING DB2 SORT | |||
2021 |
RECOVERY EXPERT 3.2 - Q3 2021 PTF BUG FIX | ||||
2021 |
RECOVERY EXPERT 3.2 - Q3 2021 PTF BUG FIX | ||||
2021 |
RECOVERY EXPERT 3.2 - Q2 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - Q2 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - Q2 2021 PTF | ||||
2021 |
UI79233 |
IEW2230S SMPE ACCEPT ERROR ON ARYGDEVT MODULE. 21/10/28 PTF PECHANGE |
|||
2021 |
DUBIOUS RELATIONSHIP DURING CREATE/VIEW OF A SLB PROFILE | ||||
2021 |
RECOVERY EXPERT 3.2 - AUGUST 2021 PTF | ||||
2021 |
RE IS NOT HANDLING SYSPRINT WHEN DB2 BACKUP UTILITY ABENDS | ||||
2021 |
THE RBA CLEANUP PROCEDURE PRODUCES AN ERROR MESSAGE | ||||
2021 |
CANNOT OBTAIN ZPARM INFORMATION | ||||
2021 |
UI77062 |
REMOVING ACEE MODIFICATION FROM ALA COMPONENT | |||
2021 |
RECOVERY EXPERT 3.2 - JULY 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - JULY 2021 PTF | ||||
2021 |
SDC2 ABEND DURING REDIRECTED RECOVERY STEP USING DB2 SORT | ||||
2021 |
ARCHIVE TABLES ARE NOT FETCHED | ||||
2021 |
ARYE004E PRODUCES BY AGENT FOR 3 CHAR SSID NAME | ||||
2021 |
TRANSLATION IS CHECKED FOR DISABLED OBJECTS | ||||
2021 |
SERVER LOOPING OR S0C4 ABEND IS POSSIBLE IF THE CONNECTION IS CLOSED WHILE SENDING A LARGE AMOUNT OF DATA | ||||
2021 |
DR JOB WITH MODE(QUIESCE) OPTION FAILS FOR DATA SHARING SUBSYSTEM | ||||
2021 |
RECOVERY EXPERT 3.2 - MAY 2021 PTF | ||||
2021 |
UI75473 UI75474 |
DDL GENERATION ISSUES | |||
2021 |
UI75473 UI75474 |
PARTITIONS REMAIN IN RESTRICTED STATE AFTER RDR | |||
2021 |
UI75473 UI75474 |
IDT STEP IS GENERATED IF LOG APPLY IS DISABLED | |||
2021 |
RECOVERY EXPERT 3.2 - APRIL 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - APRIL 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - APRIL 2021 PTF | ||||
2021 |
UI74767 |
DB2_SORT JOBCARD IS NOT GENERATED IN GGC STEP REGARDLESS OF USE DB2 SORT CF OPTION | |||
2021 |
RECOVERY EXPERT 3.2 - Q1 2021 PTF | ||||
2021 |
UI74767 |
UTILITY THAT ALLOWS US TO CONVERT FROM TIMESTAMP TO LRSN | |||
2021 |
UI74767 |
ARYAGENTSESSIONINFO DOESN'T CLEAN RESOURCES | |||
2021 |
UI74767 |
ARYSPLNB USES HARDCODED LOW LEVEL QUALIFIERS | |||
2021 |
RECOVERY EXPERT 3.2 - Q1 2021 PTF | ||||
2021 |
UI74767 |
CURSOR ERROR FOR CDG AUX TABLES | |||
2021 |
INVALID MANAGEMENT CLASS FOR DISASTER RECOVERY ARCHIVE LOGS | ||||
2021 |
RECOVERY EXPERT 3.2 - FEBRUARY 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - JANUARY 2021 PTF | ||||
2021 |
RECOVERY EXPERT 3.2 - JANUARY 2021 PTF | ||||
2021 |
ABEND 0C4 IN THE AGENT | ||||
2021 |
ERROR MESSAGE "ARYZ075E... ALREADY EXISTS" FOR ISPF UI AD-HOC OPERATIONS | ||||
2021 |
UI73405 UI73406 UI73407 |
"ON DISK" FIELD IS INCORRECTLY RESET TO NO AFTER OFFLOADS WITH WAIT_FOR_BACKGROUND_COPY=S | |||
2021 |
UI73405 UI73406 UI73407 |
RECOVERY PLAN GENERATION FAILS WITH ABEND S906 | |||
2021 |
UI73405 UI73406 UI73407 |
REDIRECTED RECOVERY PLAN IS GENERATED INCORRECTLY IN BATCH BECAUSE OF THE "PLAN-DDLONLY" STATEMENT | |||
2021 |
RECOVERY EXPERT 3.2 - Q4 2020 PTF | ||||
2021 |
BATCH JCL GENERATION UTILITY INCORRECTLY RESOLVES DATA SET INCLUDING &USERID | ||||
2021 |
UI73405 UI73406 UI73407 |
REPAIR CATALOG IS NOT GENERATED FOR TABLESPACE RECOVERED BY PARTITIONS | |||
2021 |
UI73405 UI73406 UI73407 |
TARGET TABLE IS EMPTY AFTER REDIRECTED RECOVERY | |||
2021 |
UI73405 UI73406 UI73407 |
"USE DB2 SYSTEM CATALOG ONLY" IS NOT HONORED FOR IMAGE COPIES | |||
2020 |
BATCH UTILITY INCORRECTLY SHOWS SOME OBJECTS IN THE LIST OF UNRECOVERABLE | ||||
2020 |
RECOVERY EXPERT 3.2 - OCTOBER 2020 PTF | ||||
2020 |
ABEND 0C4 IN ARY#LRD6 DURING REDIRECTED RECOVERY | ||||
2020 |
UNNECESSARY OBJECTS ARE PROCESSED DURING THE REDIRECTED RECOVERY | ||||
2020 |
INVALID DATA AFTER REDIRECTED RECOVERY | ||||
2020 |
DB2 SUBSYSTEMS WITH ALIASES SPECIFIED AS LOAD LIBRARIES ARE NOT DISCOVERED RESULTING IN ERROR ARYT062I | ||||
2020 |
WORK VOLUME IS SELECTED INCORRECTLY DURING THE CREATION OF IC FROM SLB | ||||
2020 |
RECOVERY EXPERT 3.2 - OCTOBER 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - Q3 2020 PTF | ||||
2020 |
SET CURRENT SQLID STATEMENT IS MISSED FROM THE MIGRATION JCL | ||||
2020 |
ERROR MESSAGE FOR LINE COMMANDS NOT ALLOWED FOR WILDCARDS IS UNCLEAR | ||||
2020 |
"ALTER TABLE ADD SYSTEM VERSIONING" STATEMENT IS GENERATED INCORRECTLY FOR "INCLUDE RI RELATED OBJECTS" = N | ||||
2020 |
BIND SQL WARNING FOR DB2 V11 IS NOT MENTIONED IN DOCUMENTATION | ||||
2020 |
RECOVERY EXPERT 3.2 - AUGUST 2020 PTF | ||||
2020 |
ABEND U0012 DURING THE COPY ACCUMULATION PROCESS | ||||
2020 |
"CREATE AUXILIARY TABLE" STATEMENT IS GENERATED INCORRECTLY FOR "INCLUDE RI RELATED OBJECTS" = N | ||||
2020 |
ABEND IN ISPF UI FOR NOT IMPORTED CATALOGS | ||||
2020 |
ABEND S906-08 REQUESTS FOR MODULE ARYLINKL EXCEED MAXIMUM USE COUNT | ||||
2020 |
IC FROM SLB CREATION FAILS DURING THE RESTART AFTER AN ABEND | ||||
2020 |
RECOVERY EXPERT 3.2 - JULY 2020 PTF | ||||
2020 |
BATCH UTILITY FAILS WITH "LOCATION ... IS NOT KNOWN TO THE DATA SHARING GROUP NAME IS USED | ||||
2020 |
UI70359 |
LIMIT NUMBER OF OBJECTS RECOVERED OR REBUILT SIMULTANEOUSLY | |||
2020 |
RECOVERY EXPERT 3.2 - Q2 2020 PTF | ||||
2020 |
UI70359 |
MAKE OPTIONS "IGNORE ALTERS" AND "USE DB2 CATALOG ONLY" AVAILABLE SEPARATELY | |||
2020 |
RECOVERY EXPERT 3.2 - Q2 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - MAY 2020 PTF | ||||
2020 |
MISCELLANEOUS PROBLEMS WITH DB2 MIGRATION SCRIPT | ||||
2020 |
ERROR MESSAGES "ARYS880E - THE COLUMN WAS NOT FOUND" ARE INCORRECTLY GENERATED DURING THE IVP FOR V12R1M100 | ||||
2020 |
LBDR LOG SCAN FAILS WITH SQLCODE -407 AFTER THE MIGRATION TO DB2V12 | ||||
2020 |
DATA IS NOT RECOVERED IN OBIDXLAT_CATALOG MODE | ||||
2020 |
RECOVERY OF PARTITIONED TABLESPACE FAILS WITH DSNUCASA - DATA SET LEVEL RECOVERY IS REQUIRED | ||||
2020 |
RECOVERY JCL GENERATION FAILS WITH ARYW007E FOR "USING LOAD..." PLANS | ||||
2020 |
RECOVERY EXPERT 3.2 - APRIL 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - Q1 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - Q1 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - FEBRUARY 2020 PTF | ||||
2020 |
UI68211 |
SYSTEM LEVEL RESTORE FROM OFFLOADED BACKUP FAILS FOR SPACE VOLUMES WITH REINIT_SPACE_EFFICIENT = Y | |||
2020 |
UI68211 |
AGENT HOLDS EXCLUSIVE ACCESS TO JCL LIBRARIES | |||
2020 |
UI68211 |
PRIMARY KEY IS NOT GENERATED FOR MIGRATED TABLE | |||
2020 |
UI68211 |
SYSTEM LEVEL BACKUP FAILS WITH ERROR MESSAGE ARYS118E FOR COPY PENDING LOB TABLESPACE | |||
2020 |
RECOVERY EXPERT 3.2 - FEBRUARY 2020 PTF | ||||
2020 |
UI73405 |
HOLD ACTION FOR APAR PH14999 IS INCOMPLETE | |||
2020 |
UI67844 UI67845 |
AGENT TASK FAILS WITH ABEND S913-38 IF CLIENT DOES NOT HAVE ACCESS TO DB2 LIBRARIES | |||
2020 |
UI67844 UI67845 |
ERROR MESSAGE ARYP029S IS SHOWN WHEN SECTION IS NOT DEFINED IN THE CONFIGURATION FILE | |||
2020 |
RECOVERY EXPERT 3.2 - JANUARY 2020 PTF | ||||
2020 |
UI67844 UI67845 |
DROP STATEMENT MAY BE INCORRECTLY GENERATED FOR ALTERED PARTITIONED TABLESPACES | |||
2020 |
UI67844 UI67845 |
RECOVERY OPTIONS ARE IGNORED BY THE EXPLODE COMMAND | |||
2020 |
UI67844 UI67845 |
ESTIMATED COST OF ADVANCED RECOVER OR REDIRECTED RECOVERY MAY BETOO LOW | |||
2020 |
RECOVERY EXPERT 3.2 - JANUARY 2020 PTF | ||||
2020 |
RECOVERY EXPERT 3.2 - JANUARY 2020 PTF | ||||
2020 |
MISCELLANEOUS INTERNAL IMPROVEMENTS | ||||
2020 |
MISCELLANEOUS INTERNAL IMPROVEMENTS | ||||
2020 |
UI67380 UI67381 |
ENHANCEMENT TO MATERIALIZE DEFINE NO TABLESPACES | |||
2020 |
MISCELLANEOUS INTERNAL IMPROVEMENTS | ||||
2019 |
EARLY FILTRATION OF NETWORK REQUESTS | ||||
2019 |
RECOVERY EXPERT 3.2 - NOVEMBER 2019 PTF | ||||
2019 |
INFINITE LOOP IN RECOVERY PLAN GENERATION FOR REDIRECTED RECOVERY | ||||
2019 |
ERROR MESSAGE ARYU115E IS ISSUED BY THE WEB UI IF PLANS ARE NOT GENERATED BECAUSE OF UNRECOVERABLE OBJECTS | ||||
2019 |
RECOVERY PLAN GENERATION FOR OBJECTS WITH REFERENTIAL INTEGRITY FAILS WITH ABEND S0C4 IN MODULE ARYLJGCR | ||||
2019 |
RECOVERY EXPERT 3.2 - OCTOBER 2019 PTF | ||||
2019 |
UI66201 |
IVP PROCEDURE DOES NOT CHECK ALL PRODUCT COMPONENTS | |||
2019 |
UI66201 |
PERFORMANCE PROBLEMS OF TRANSACTION SCANS IF MANY URIDS ARE FOUND IN THE SCANNED RAGE | |||
2019 |
UI66201 |
REDIRECTED RECOVERY JOB GENERATED WITH "NUMBER OF PARALLEL JOBS"GREATER THAN 1 MAY FAIL WITH ERROR MESSAGE: ARY2699E | |||
2019 |
UI66201 |
SLR UPDATE JOB FAILS WITH ARYE600E SQLCODE -206 ON DB2 V12R1M500 | |||
2019 |
UI66201 |
ABEND U0012, CODE=DC2 DURING THE REDIRECTED RECOVERY | |||
2019 |
RECOVERY EXPERT 3.2 - OCTOBER 2019 PTF | ||||
2019 |
RECOVERY EXPERT 3.2 - Q3 2019 HIP PTF | ||||
2019 |
UI65470 |
SUPPORT OF DDL STATEMENT KEYLABEL FOR DROPPED/ALTERED OBJECTS | |||
2019 |
UI65470 |
ARYR884E INCORRECTLY SHOWN. THIS CAN OCCUR IF SERVER INFO IS MANUALLY ENTERED OR CLIST ARYV320 HAS THE SERVERNM IN UPPERCASE |
|||
2019 |
RECOVERY EXPERT 3.2 - Q3 2019 HIP PTF | ||||
2019 |
SLB OF A DATA SHARING GROUP ENDS WITH ABEND S0C4 FOR COPYPOOL FRS=DUMPONLY | ||||
2019 |
ERROR MESSAGE ARYS293E FOR LBDR RECOVERY WITH AUTOMATIC IMAGE COPIES ENABLED | ||||
2019 |
RECOVERY EXPERT 3.2 - AUGUST 2019 PTF | ||||
2019 |
COMMENTS ABOUT WARNINGS FOR MODULES ARY#OBRP AND ARY#XMLI ARE MISSING FROM DB2 V12 BIND JOB | ||||
2019 |
MISCELLANEOUS PROBLEMS WITH SELECTION OF OLD, MIGRATED OBJECTS. | ||||
2019 |
MESSAGE 'ARYR706I: THE CONTROL FILE RECORD ... HAS BEEN SUCCESSFULLY UPDATED' IS SHOWN BUT RECORD IS NOT UPDATED. | ||||
2019 |
UI64540 UI64541 |
INCORRECT PLANS ARE GENERATED FOR COPIES WITH NON-EMPTY DSVOLSERIF DB2 APAR PH03679 IS APPLIED. | |||
2019 |
UI64540 UI64541 |
ERROR ARYT053E FOR ISPF USERS WITHOUT ACCESS TO PTKTDATA. | |||
2019 |
RECOVERY EXPERT 3.2 - JULY 2019 PTF | ||||
2019 |
RECOVERY EXPERT 3.2 - JULY 2019 PTF | ||||
2019 |
RECOVERY EXPERT 3.2 - JULY 2019 PTF | ||||
2019 |
ERROR MESSAGE GGC4611E THE DATASET ... HAS REACHED THE MAXIMUM SIZE... DURING RECOVERY | ||||
2019 |
INVALID RECOVER PLAN IS GENERATED WHEN REQUIRED COPIES AND LOGS ARE NOT AVAILABLE. | ||||
2019 |
RECOVERY FAILS IN LOG APPLY STEP WITH SQL CODE -530 | ||||
2019 |
RECOVERY LRSN IS INCORRECT FOR DATASHARING SUBSYSTEMS | ||||
2019 |
ARY#YCTL - LOCATE ON IMAGE COPY DSNDB0#.SYS#### FAILED. | ||||
2019 |
IVP CAN ISSUE INVALID MESSAGE ARYS340E IF OPTIONAL SYSTEM RBA CAPTURE FILE IS NOT USED. | ||||
2019 |
ABEND 0C4 IN ISPF UI ON PANEL ARYGJSLP | ||||
2019 |
PLANS INCLUDING "REDO SQL" MAY RECEIVE ERROR ARYA029E FOR EMPTY TABLESPACES | ||||
2019 |
RECOVERY EXPERT 3.2 - JUNE 2019 PTF | ||||
2019 |
REORGANIZATION OF LBDR AND TRANSACTION RECOVERY PANELS IN ISPF CLIENT | ||||
2019 |
REORGANIZATION OF LBDR AND TRANSACTION RECOVERY PANELS IN ISPF CLIENT | ||||
2019 |
RECOVERY EXPERT 3.2 - Q2 2019 HIP PTF | ||||
2019 |
ADDITIONAL MONITORING OF SYSTEM LEVEL BACKUP AND OFFLOAD. | ||||
2019 |
CUSTOMIZABLE SYSCOPY SELECTION FOR REDIRECTED RECOVERY. | ||||
2019 |
COMMAND "F CATALOG" MAY BE REPEATEDLY ISSUED MULTIPLE TIMES | ||||
2019 |
LBDR MISSES DEPENDENT OBJECTS ALTERED JUST BEFORE THE DROP | ||||
2019 |
REPORT UTILITY LOOKS FOR DSNDB06.SYSCOPY ON DB2 V12R1M100 AND FAILS WITH RC=8 | ||||
2019 |
"BACKUP ON DISK = YES" IS SHOWN WHEN THERE IS NO BACKUP ON DISK | ||||
2019 |
RECOVERY EXPERT 3.2 - MAY 2019 PTF | ||||
2019 |
MISCELLANEOUS PROBLEMS WITH INCREMENTAL SLBS | ||||
2019 |
SLB PROFILE WITH TYPE "DB2" DOESN'T WORK PROPERLY WITH WAIT_FOR_BACKGROUND_COPY=S | ||||
2019 |
DATA SHARING GROUP NAME IS GENERATED INSTEAD OF SSID IN TCZ SETUP JOB ARYCF1UP | ||||
2019 |
&USERID IS NOT RESOLVED FOR 'DATA SET NAME PREFIX' FOR TEMPORARYWORK FILES | ||||
2019 |
DROPPED OBJECT RECOVERY REDO/UNDO STEP GETS UNAVAILABLE RESOURCEBECAUSE CHILD TABLE SPACE IN UT STATUS | ||||
2019 |
MISCELLANEOUS PROBLEMS WITH TCZ MIGRATION SCRIPTS | ||||
2019 |
RECOVERY EXPERT 3.2 - APRIL 2019 PTF | ||||
2019 |
ALLOW REDIRECTED RECOVERY OF DROPPED OBJECTS | ||||
2019 |
ABEND U0012 IN REDIRECTED RECOVERY | ||||
2019 |
LBDR LOG SCAN FAILS WITH SQLCODE -407 ON DB2 V12. | ||||
2019 |
UI62597 UI62598 |
LBDR SCAN FAILING WITH ABEND=S000 U0035 OR ABEND=S000 U0022 IN MODULE ARYDTL4 WHEN PROCESSING LOBS | |||
2019 |
UI62597 UI62598 |
REQUIRED INDEXES ARE NOT RECREATED CAUSING SQL ERROR -540 | |||
2019 |
DISASTER RECOVERY ENHANCEMENT TO ADD AN ABILITY TO SPECIFY A DEVICE TYPE AND SMS CLASSES FOR ARCHIVE LOGS AT THE DR SITE | ||||
2019 |
UI62597 UI62598 |
ENHANCEMENT TO DISPLAY A DATASHARING GROUP NAME ON THE RESTORE SYSTEM ISPF PANEL | |||
2019 |
UI62597 UI62598 |
ERROR "ARYX092E - AN ERROR OCCURRED WHILE PERFORMING AUTHENTICATION" FOR MULTI FACTOR AUTHENTICATION USERS | |||
2019 |
UI62597 UI62598 |
GENERATED DDL FOR ALTER COLUMN FAILS WITH SQL CODE -20180 | |||
2019 |
UI62597 UI62598 |
LBDR SCAN FAILING WITH ABEND=U0066 IN MODULE ARYDTL4 | |||
2019 |
UI62597 UI62598 |
RACF ICH408I MESSAGES FOR DEFINE - INSUFFICIENT AUTHORITY DURINGJCL GENERATION FOR LBDR SCAN | |||
2019 |
RECOVER RUNTIME STATISTICS DURING THE LBDR RECOVERY | ||||
2019 |
RECOVERY EXPERT 3.2 - MARCH 2019 PTF | ||||
2019 |
UI62597 UI62598 |
CREATE DEPRECATED OBJECTS IN DB2 V12 FL504 | |||
2019 |
DB2 RECOVERY EXPERT NOT AWARE OF HSM FAILURE | ||||
2019 |
UNABLE TO OFFLOAD SLB WHEN DISPLAY COPYPOOL SHOWS FRS=DUMPONLY | ||||
2019 |
MONITOR WORK DATASETS AND ARCHIVE DATASETS SEPARATELY | ||||
2019 |
RECOVER PLAN IS GENERATED WHEN REQUIRED LOGS ARE NOT AVAILABLE | ||||
2019 |
MASTER OFFLOAD JOB MAY HANG WHEN CONTACT IS LOST WITH SPAWNED, MULTI-JOB MULTI-LPAR JOBS | ||||
2019 |
ARY 3.2 - FEBRUARY 2019 PTF | ||||
2019 |
INCORRECT OPTIONS IN SYSTEM LEVEL BACKUP PROFILES CREATED BEFOREUI58559 / UI57940 | ||||
2019 |
ADD SUPPORT TO ADVANCED RECOVER AND REDIRECTED RECOVERY TO ALLOWUNCATALOGED ICS TO BE USED. | ||||
2019 |
ARY2017E VSAM WRITE ERROR DURING RECOVERY REDIRECTED RECOVERY | ||||
2019 |
RECOVERY EXPERT 3.2 - JANUARY 2019 PTF | ||||
2019 |
SQLCODE -407 FOR REDIRECTED RECOVERY ON DATASHARING GROUP | ||||
2019 |
SLR DATA NOT RETAINED DURING DB2 VERSION MIGRATIONS | ||||
2019 |
AN SQL ERROR OCCURRED WITH SQL CODE = -553 FOR USERS WITHOUT SYSADM | ||||
2018 |
SYSTEM LEVEL BACKUP FAILS WITH ARYS118E - ARY#CVAF: PIN UCB FAILED | ||||
2018 |
SETCXF ERRORS ARE NOT REPORTED | ||||
2018 |
MISCELLANOUS ISSUES WITH COPY YES INDEXES AND FLASHCOPY ICS ( IMAGE COPY ) | ||||
2018 |
DETECT ACTIVE DB2 SUBSYSTEMS AUTOMATICALLY | ||||
2018 |
SHOW SYSTEM LEVEL BACKUPS IN THE LIST OF RECOVERY HISTORY EVENTS | ||||
2018 |
DDL GENERATION OPTIONS DO NOT WORK | ||||
2018 |
UNNECESSARY REPAIR VERSIONS STATEMENTS GENERATED | ||||
2018 |
NEW OPTION TO RECREATE UNRECOVERABLE OBJECTS OR MAKE IT EMPTY | ||||
2018 |
ESTIMATE LOG RECORDS TO AVOID SORT PROBLEMS DURING ADVANCED RECOVER OR REDIRECTED RECOVERY | ||||
2018 |
RECOVERY EXPERT 3.2 RELEASE | ||||
2018 |
PARAMETER RESTORE-TO-VOLSER IS NOT BEING PASSED TO THE SPAWNED JOBS | ||||
2018 |
REPORT FOR ARY IVP JOB IS TRUNCATED FOR DB2 V12R1M100 OR DB2 V11CM | ||||
2018 |
SLB PROFILE USING DB2 BACKUP METHOD SHOWS INCORRECT MAPPING WITHSHARED TARGET STORAGE GROUPS | ||||
2018 |
DDL IS NOT GENERATED FOR MQT IN REDIRECTED RECOVERY JCL | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
MAKE CONTROL FILE OPTION "RBR DSMEMBER" CONFIGURABLE VIA TCZ | ||||
2018 |
MESSAGE ARYS334I - VOLUME IS OFFLINE IS INCORRECTLY ISSUED FOR ONLINE VOLUMES. | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES, #2 | ||||
2018 |
INVALID CHECK DATA SYNTAX IS GENERATED FOR PARTITIONED TABLESPACES | ||||
2018 |
RELOAD IDAA TABLES AFTER RECOVERY | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
SARYDENU(ARYSRVCF) CONTAINS INVALID COMMENT | ||||
2018 |
MESSAGE ARY2067E FOR ADVANCED RECOVERY OF DROPPED OBJECT AFTER REORG. | ||||
2018 |
RECOVERY POINT TYPE "CURRENT" SHOULD BE "LAST IC" FOR REDIRECTEDRECOVERY | ||||
2018 |
DURING RECOVERY PLAN GENERATION, DB2 RE SHOULD HAVE AN OPTION TO VALIDATE THE EXISTENCE OF REQUIRED DB2 LOGS AND COPIES | ||||
2018 |
REMOVE THE REQUIREMENT OF BPX.FILEATTR.APF FOR THE REDIRECTED RECOVERY OR ADVANCED RECOVER USAGE | ||||
2018 |
S0C1 IN ARYLOX00 IF USER EDITS ARYCF1UP JOB INCORRECTLY | ||||
2018 |
DB2 RECOVERY EXPERT ABENDS WITH ABEND=E37 REASON CODE=00000004 WHEN PERFORMING LOG SCAN FOR DROPPED LOB | ||||
2018 |
MONITORING OF RECOVERY JOBS AND RECOVERED OBJECTS IN THE ISPF CLIENT | ||||
2018 |
USABILITY ISSUES ON THE "BUILD JOB" ISPF PANEL | ||||
2018 |
OPTION TO MOVE WAITING FOR SLB BACKGROUND COPY TO A SEPARATE STEP | ||||
2018 |
REPORT AVAILABLE SLB BACKUPS AT THE DISASTER RECOVERY SITE | ||||
2018 |
ARYA107E AND ARYA061W DURING LOG SCAN FOR LOG BASED RECOVERY | ||||
2018 |
MISSING SOURCE VOLUME INFORMATION IN THE ARYS048E ERROR MESSAGE | ||||
2018 |
ARYBIND1 MAY RECEIVE ERRORS FOR DBRM=ARY@SCPY, STATEMENT=1024, SQLCODE=-551 | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
PROVIDE WARNING IF SLB REPORTS RESTRICTED OBJECTS | ||||
2018 |
RESET_COPY_PENDING FAILS IN SYSTEM LEVEL BACKUP BECAUSE OF INCORRECT TRAILING SPACES IN REPAIR STATEMENTS | ||||
2018 |
EXPIRATION DATE AND RETENTION PERIOD NOT BEING PLACED INTO GENERATED JCL FOR TAPE IMAGE COPIES | ||||
2018 |
CODE CHANGE TO PREVENT ALLOCATING AN EXISTING ARCHIVE LOG COPY DATASET | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
RECOVERY EXPERT V3.2 REDIRECTED RECOVERY ABEND U0012 AND ARY2088E | ||||
2018 |
DB2 METHOD SLB PROFILE INCORRECT MAPPING WITH SHARED TARGET STORAGE GROUPS | ||||
2018 |
SUPPORT SLIDING SCALE ALLOCATION ALGORITHM FOR REDIRECTED RECOVERY AND ADVANCED RECOVER | ||||
2018 |
RECOVERY EXPERT TO SUPPORT LOGS > 4 GIG FOR V12 | ||||
2018 |
NEW RECOVERY PLAN 'ADVANCED RECOVER'. | ||||
2018 |
SQLCODE -553 FOR ANY CURRENT SQLID VALUE | ||||
2018 |
USE THE SAME PAGESIZE AND BUFFERPOOL FOR LBDR TABLES AND SYSTEM CATALOG TABLES | ||||
2018 |
FC INCREMENTAL BROKEN BUT NOT REPORTED | ||||
2018 |
CHECK FOR XML TEMPLATE AND XML JOBS DATA SETS EXISTENCE DURING THE REDIRECTED RECOVERY PLAN GENERATION | ||||
2018 |
NEW OPTION TO ALLOW JOB NAMES TO BE USED AS MEMBER NAMES | ||||
2018 |
'ARYPCF00 - ERROR FETCHING LRSN DELTA' INCORRECTLY ISSUED FOR INACTIVE DB2 SUBSYSTEMS | ||||
2018 |
'ARYX093S - AN UNEXPECTED ERROR OCCURRED (./ARYAGENTREQUESTGENRECPLANS.CPP,294)' RECOVERING EMPTY APPLICATION GROUPS | ||||
2018 |
ARYGRANT DOES NOT HAVE THE REQUIRED GRANT STATEMENTS | ||||
2018 |
ENHANCEMENT TO CREATE TRIGGERS IN REDIRECTED RECOVERY (RFE 116837) | ||||
2018 |
CONTROL FILE REPORT MAY INCORRECTLY SHOW LOAD LIBRARIES AS NOT APF AUTHORIZED | ||||
2018 |
ENHANCEMENT TO ISSUE WARNING MESSAGES FOR ANY RECOVERED TABLES WITH DATA CAPTURE CHANGES ENABLED | ||||
2018 |
ENHANCEMENT TO DISPLAY ALL DROPPED OBJECTS FOR LBDR RECOVERY ( RFE 114402 ) | ||||
2018 |
MULTI-LPAR RESTORE AND OFFLOAD FAILS WITH ENQ_SYSTEMS ERR FOR CA-MIM ENVIRONMENT | ||||
2018 |
RE-READ DB2 SUBSYSTEMS' PROPERTIES ON REFRESH | ||||
2018 |
ENHANCEMENT TO ALLOW PARAMETERS OVERRIDE ON THE PROFILE LEVEL | ||||
2018 |
ADMIN_USERID IS NOT HONORED FOR SYSTEM LEVEL BACKUP PROFILES. ARYR313E MAYBE SEEN. | ||||
2018 |
ARYS9918E AT LEAST ONE USERCAT STATEMENT IS REQUIRED | ||||
2018 |
DB2 RECOVERY EXPERT SHOULD ALWAYS USE THE DATA COMPLETE LRSN AS THE BACKUP LRSN. | ||||
2018 |
WEB INTERFACE USES INCORRECT LRSN AS RECOVERY POINT | ||||
2018 |
DASH CHARACTER SHOULD BE ALLOWED IN THE SERVER NAME FIELD | ||||
2018 |
APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
ENHANCEMENT TO ENABLE/DISABLE JOBPARM SYSAFF IN THE GENERATED RECOVERY JCLS (RFE116838) | ||||
2018 |
BATCH UTILITY ENHANCEMENTS FOR THE RECOVERY PLAN/JCL GENERATION (RFE 114662) | ||||
2018 |
LOG RANGE SCAN ASSIGNS DIFFERENT TIMESTAMPS TO STATEMENTS WITH THE SAME UOW IN A DATA SHARING ENVIRONMENT | ||||
2018 |
ENHANCEMENT TO ENABLE ALL NPI INDEX REBUILDS IN PARALLEL JOBS TOSHORTEN THE RUN-TIME OF THE OVERALL RECOVERY (RFE 111491) | ||||
2018 |
DUPLICATE INDEXES FOR CONSTRAINTS ADDED BY ALTER | ||||
2018 |
CREATE UNRECOVERABLE OBJECTS AT DR SITE | ||||
2018 |
JCL COMMENTS TO DESCRIBE THE FUNCTION OF EACH STEP (RFE 114972) | ||||
2018 |
DR PREP - DELETE DSNAME FAILS WITH DSNJ218I | ||||
2018 |
ADD OF MESSAGES ARYT019I AND ARYY022I FROM SYSPRINT TO SYSLOG ( RFE 111895 ). | ||||
2018 |
SUBSYSTEM ANALYSIS REPORT TRUNCATES ALIAS NAME | ||||
2018 |
&RBRLVL..&LLIB IS USED INSTEAD OF &RBRLOAD1 IN CLIST AND SKELETONS | ||||
2018 |
WRONG LRSN VALUE USING LRSN CONVERSION UTILITY | ||||
2018 |
IGNORE UNRECOVERABLE OBJECTS DURING RECOVERY PLAN GENERATION | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
ENHANCEMENT TO OPTIONALLY ALLOW IMAGE COPIES CREATED IN PREVIOUSVERSIONS TO BE USED FOR RECOVERY. | ||||
2018 |
ENHANCEMENT TO UPDATE DSC/SLR/LBDR REPOSITORIES WITH ANALOGUE INFORMATION FROM SYSIBM.SYSTABCONST AND SYSIBM.SYSKEYCOLUSE | ||||
2018 |
EMPTY USER CATALOG NOT UNALLOCATED DURING SYSTEM RESTORE FROM SLB | ||||
2018 |
DB2 SLB ABEND S0C1 WITH PARM RESET_COPY_PENDING_TS = Y | ||||
2018 |
REBUILD INDEX MAY BE INCORRECTLY SPLITTED | ||||
2018 |
ALLOW DB2 RECOVERY EXPERT FOR Z/OS TO SUPPORT MULTIPLE DB2 TYPE BACKUP PROFILES | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
SUPPORT 'USE DB2 SYSTEM CATALOG ONLY' DEFAULT VALUE FOR MULTIPLE REDIRECTED RECOVERY PROFILES. | ||||
2018 |
LOG RANGE SCAN FOR A LOG BASED APPLICATION PROFILE CAN ASSIGN DIFFERENT TIMESTAMPS TO STATEMENTS WITH THE SAME UOW | ||||
2018 |
MISSING PAGES WITH IC FROM SLB WITH EXTENDED PAGE TABLESPACES/INDEXSPACES | ||||
2018 |
RESTART IS NOT PASSED TO THE SPAWNED JOBS DURING THE MULTI-JOB RESTORE OR OFFLOAD | ||||
2018 |
ARY BIND MAY RECEIVE SQLCODE -203 FOR ARY@BAKO ON DB2 V12 | ||||
2018 |
SERVER HANGS WITH 'ARYX062E--A SOCKET ERROR OCCURRED ON "SEND" WITH RC = 0000008C: EDC5140I BROKEN PIPE.' | ||||
2018 |
ENHANCEMENT TO SUPPORT UTS IN RECOVERY EXPERT REPOSITORY MIGRATION PROCESS. (RFE 91707) | ||||
2018 |
JOB RECEIVES RESOURCE UNAVAILABLE. DSNT500I 00C90094 | ||||
2018 |
INTERNAL APAR RESOLVING MULTIPLE ISSUES | ||||
2018 |
DO NOT GENERATE RECOVERY PLANS FOR PBG PARTITION PRUNING. | ||||
2018 |
SQLCODE -501 ON DBRM/PACKAGE: ARYLB9UT DURING RECOVERY | ||||
2018 |
DDL MAY BE NOT GENERATED FOR REDIRECTED RECOVERY IF SOME 'DDL GENERATION OPTIONS' ARE SET TO N | ||||
2018 |
MESSAGE ARYZ048E THE SPECIFIED LRSN IS NOT WITHIN THE SCOPE OF THE LOG | ||||
2018 |
DB2 RECOVERY EXPERT MAY NOT RETRIEVE ALL OBJECTS AND REBUILD ALLINDEXES | ||||
2018 |
INFRASTRUCTURE CHANGES RELATED TO THE PLANNED TRANSITION TO CONTINUOUS DELIVERY | ||||
2017 |
DROPPED OBJECT RECOVERY ENDS WITH SQLCODE = -904 | ||||
2017 |
DATA MISSING AFTER DROPPED OBJECT RECOVERY DUE TO DEFAULT PIT BEING SELECTED. | ||||
2017 |
DROPPED OBJECT RECOVERY REDO/UNDO STEP GETS UNAVAILABLE RESOURCEBECAUSE PARENT TABLE SPACE IN UT STATUS | ||||
2017 |
DR PREP FOR V11 CM AND QUIESCED SUBSYSTEM ISSUES | ||||
2017 |
UI65081 |
DB2 RECOVERY EXPERT INCORRECTLY SELECTING THE OLDER CHECKPOINT IF THE RBA/LRSN IS EXPANDED | |||
2017 |
USE ALA WORKFILES FOR BYPASSING THE 500 LOG RECORDS RESTRICTION OF ALA 64BIT MODE. | ||||
2017 |
DB2 RECOVERY EXPERT NOT RETRIEVING ALL OBJECTS AND NOT REBUILDING ALL INDEXES | ||||
2017 |
DR PREP DOES NOT PROCESS ALL THE ACTIVE LOGS IN MEMBERS SSIDDELCAND SSIDALLC | ||||
2017 |
ISPF UI CHANGES TO MAKE IT MORE CONSISTENT | ||||
2017 |
ABENDU0077 IN ARYDTL4 WITH REDO SQL RECOVERY PLAN | ||||
2017 |
REDIRECTED RECOVERY MAY FAIL OR PRODUCE INCORRECT DATA IF SYSTEMHAS MAX ACTIVE LOGS | ||||
2017 |
CNK998E UNSUCCESSFUL SORT S0C1 RUNNING DB2 RECOVERY EXPERT V3.2 V32 | ||||
2017 |
UNABLE TO GENERATE REDIRECTED RECOVERY PLANS DUE TO OBJECT BEINGFLAGGED AS DROPPED. | ||||
2017 |
ARY#YARC - ERROR ALLOCATING LOCAL LOG BECAUSE OF HSM BACKUP CONTENTION | ||||
2017 |
DR JOB SSID#JC1 RECEIVES DSNJ415E RBA NOT ON 4K BOUNDARY WITH COORDINATED RECOVERY | ||||
2017 |
ROLL UP APAR RESOLVING MUTIPLE ISSUES. | ||||
2017 |
UNCOMMITTED DROPS CAUSE ARY REPOSITORY TO NOT BE UPDATED | ||||
2017 |
PADDED STORAGE GROUP NAMES ARE NOT TRIMMED IN GENERATED DDL | ||||
2017 |
DEPENDENT PARTITIONS MAYBE NOT FOUND IN SLR FOR ALTERED TABLESPACES | ||||
2017 |
UI75974 |
POTENTIAL LINKEDIT ISSUES WHEN APPLYING PTF'S IN MASS. | |||
2017 |
ADD CANDIDATE VOLSERS TO REDIRECTED RECOVERY OUTPUT DATASETS PRIOR TO USE. | ||||
2017 |
REDIRECTED RECOVERY JOB FAILS WITH ARY2071E WHEN TRYING TO RECOVER OBJECTS WITH XML TO SAME SSID. | ||||
2017 |
REDIRECTED RECOVERY ACROSS LPARS | ||||
2017 |
DR RESTORE FROM-OFFLOAD RECOVERYSITE USING MULTIJOB FAILS WITH ARYS118E | ||||
2017 |
MULTIPLE GUI UPDATES | ||||
2017 |
THE RECOVERY JOB FAILED AT LGNL00XX STEP WITH SQLCODE = -311 | ||||
2017 |
REDIRECTED RECOVERY XML ISSUE WITH DOCID | ||||
2017 |
CORRECT ISSUES RELATED TO DDL GENERATION AND REDIRECTED RECOVERY | ||||
2017 |
CLONE - 3.2 CONNECTION REFUSED - GETPEERNAME | ||||
2017 |
RECOVERY PLANS NOT GENERATED IF AUTOMATION TOOL OBJECT PROFILE USE " ADVANCED SQL " | ||||
2017 |
WILDCARDS IN AUTOMATION TOOL OBJECT PROFILES ARE NOT HONOURED INRECOVERY EXPERT OBJECT PROFILES | ||||
2017 |
3.2 OFFLOAD STEP FAILED ON REFORMATING ON ONLINE VOLUME | ||||
2017 |
V32 CREATING IMAGE COPIES FROM SLB IN JES3 ENVIRONMENT - EOJ NOTRECOGNIZED FROM SPAWNED OFFLOADS | ||||
2017 |
DR - COPIED NUMBER OF ARCHIVE LOGS TO DASD NOT WORKING AS EXPECTED AND EXCLUDE NON-RECOVERABLE USER TABLESPACES FROM IC | ||||
2017 |
UI65081 |
WHEN PERFORMING WITHDRAW WITH TSE DEVICES, RECOVERY EXPERT MUST PERFORM SPACE RELEASE YES TO PREVENT POSSIBLE HOST ADAPTER FAIL |
|||
2017 |
GENERATED RECOVERY JOB FAILS WITH -102 | ||||
2017 |
REDIRECTED RECOVERY UPDATES | ||||
2017 |
RESTRICTED OBJECTS REPORT DUPLICATED FOR D-SHARING ENVIRONMENTS | ||||
2017 |
REMOVE VOLUMES FROM SHARED TARGET POOL WHEN IN A RELATIONSHIP | ||||
2017 |
RECOVERY NTFY#### STEP ISSUES ARYX013E AND ICH408I DURING RECOVERY | ||||
2017 |
UI65081 |
DB2 RE DOES NOT WORK WITH EXTENT SPACE EFFICIENT VOLUMES | |||
2017 |
UI62596 |
USING RESTORE FROM SYSTEM LVL BACKUP, RECOVER LOGONLY MAY FAIL W/VSAM CATALOG RETURN CODE IS 132 - REASON CODE IS IGG0CLFJ-72 |
|||
2017 |
INVALID VALUE, NUMERIC EXPECTED. | ||||
2017 |
OBJECT RESTORE FROM OFFLOADED SLB NOT WORKING, ERROR ARYS429E | ||||
2017 |
ARCHIVE LOGS NEEDED AT DR (OPTION IN DRE PANEL) | ||||
2017 |
3.2 DEADLOCK WHEN RUNNING SLR UPDATE | ||||
2017 |
ARYZ018E FOR RECOVERY POINT BETWEEN THE TIMESTAMP AND START_RBA OF FULL IC ( IMAGE COPY ). | ||||
2017 |
COORDINATED DR SSIDTIME MEMBER HAS INVALID RBA | ||||
2017 |
ALA UPDATES FOR ARY | ||||
2017 |
TEMPLATE DSN FOR AUTOMATIC IC IS TRUNCATED AT 44TH CHARACTER | ||||
2017 |
3.2 PARTITION-LEVEL RECOVERY PLAN REBUILDS ENTIRE INDEX | ||||
2017 |
POSSIBLE DUPLICATES IN SYSBACK.OBJS FILE WHEN RUNNING MULTIPLE CONCURRENT SYSTEM-LEVEL BACKUPS | ||||
2017 |
SUPPORT FOR PARALLEL_CLONE FOR EMC-DEVICES | ||||
2017 |
3.2 RACF ERROR ON DD: ARYUILOG | ||||
2017 |
ARYX093S--AN UNEXPECTED ERROR OCCURRED ( ARYAGENTREQUESTGENUNDOSQL.CPP,208 ). | ||||
2017 |
ALLOW TO CUSTOMIZE WILDCARD CHARACTERS FOR REDIRECTED RECOVERY MASKING | ||||
2017 |
RECOVER STATEMENT FAILS RUNNING #JC3 GENERATED FROM DR METHOD OFIMAGE COPY | ||||
2017 |
V3.2 SSIDCATL GENERATING INVALID CONTROL CARD | ||||
2017 |
RECOVER JCL MEMBER SSIDDELA IS MISSING NOSCRATCH OPTION FOR IDCAMS DELETE | ||||
2017 |
3.2 UNNECESSARY 'SET CURRENT SCHEMA' STATEMENT IS GENERATED IN DDL STEP | ||||
2017 |
UI62894 |
3.2 ARY IEF465I DURING RECOVERY | |||
2017 |
DEFINE A SET OF UPPERCASE-XXXX PARAMETERS TO MANAGE PASSWORD ANDUSER ID SEPARATELY | ||||
2017 |
UI65081 |
3.2 SLB OFFLOAD WITH SPACE EFFICIENT TARGETS LEAVES VOLUMES IN INDETERMINATE STATE | |||
2017 |
ERROR WHEN USING A DR METHOD OF IMAGE COPY. | ||||
2017 |
MISSING RECOVERY STATEMENT FOR SYSTSSFB TABLESPACE | ||||
2017 |
RESOLVING TCZ ISSUES FOR V32 RECOVERY EXPERT | ||||
2017 |
ADD OPTION ON SERVER TO DISABLE SENDING MULTICAST PACKETS | ||||
2017 |
UI65081 |
VOLUME PAIRINGS CAUSING ABENDS FOR RECOVERY EXPERT BACKUPS | |||
2017 |
3.2 ARYE600E ARYLBBUK STMT 00412 SQLCODE -811 | ||||
2017 |
RECOVERY EXPERT 3.2 - USE CONFIGURATION TO DETERMINE HOW MANY LOGS NEEDED FOR DR | ||||
2017 |
AE PI70960 FIX COMPLETION / BATCH REDIRECTED OBJECT RECOVERY FAILING WITH WITH ARYX104E ( SQLCODE -104 ). | ||||
2017 |
REDIRECTED RECOVERY FAILING WITH IDC3202I / IDC0002I, MAXIMUM CONDITION CODE WAS 12 | ||||
2017 |
REDIRECTED RECOVERY MAY FAIL DEFINING THE TARGET VSAM CLUSTER BECAUSE REQUESTED SIZE IS TOO LARGE. | ||||
2017 |
REDIRECTED RECOVERY FAILING WITH ABEND=S000 U0012 REASON=00001007 IN NAME=ARY#MAIN | ||||
2016 |
OBJECT RECOVERY IN BATCH IS FAILING WITH SQLCODE -304 | ||||
2016 |
VARIOUS WEB GUI FIXES | ||||
2016 |
UI65081 |
ERROR ARYS173E - ALLOCATE FAILED FOR JCLOUT WHEN RUNNING OFFLOAD | |||
2016 |
HSM OFFLOAD FAILS WITH ARYS285E - HSM COMMAND FAILED. RC = 00000005. RS = 00000004. | ||||
2016 |
UI65081 |
ARYS118E WHEN CREATING IMAGE COPY FROM SLB | |||
2016 |
ALLOW TRANSACTION RECOVERY TO BACKOUT LOAD LOG YES | ||||
2016 |
SUPPORT FOR FUTURE DB2 ENHANCEMENTS | ||||
2016 |
ABEND U0012 IN MODULE ARY#MAIN | ||||
2016 |
REDIRECTED RECOVERY JOB MAY FAIL WITH ABENDU0012 AND MESSAGE IDC3211I KEYWORD 'PURG' IS IMPROPER | ||||
2016 |
ARY#RIO: ERROR WRITING TO BACKUP KSDS RETCDE= 00000008 FDBAREA=00000008 | ||||
2016 |
RC=8 WITH BYPASS_DB2_VALIDATION IN SLB CREATE PROCESS | ||||
2016 |
UI65081 |
ERROR ARYS173E - ALLOCATE FAILED FOR JCLOUT. WHEN RUNNING A MULT-JOB OFFLOAD. | |||
2016 |
EMPTY -NONE- VOLUME DATASET REPORT AND MOD 54 TRACK COUNT INCORRECT | ||||
2016 |
VARIOUS BUG FIXES | ||||
2016 |
SYSTEM LEVEL BACKUP MAY BE INCORRECTLY MARKED UNAVAILBLE, MESSAGE ARYS265E GENERATED | ||||
2016 |
ABEND S0C4 RC=4 ON NAME=UNKNOWN MAY OCCUR PERFORMING A REDIRECTED RECOVERY | ||||
2016 |
INCORRECT DSN HLQ DURING REDIRECTED RESTORE | ||||
2016 |
GENERATE NEW KEY DATABASE JOB ARYSSLCR FAILING WITH ARYX141E | ||||
2016 |
ARYX141E--A SSL ERROR OCCURRED ON "GSK_SECURE_SOCKET_INIT" WITH RC = 000001A4: SOCKET CLOSED BY REMOTE PARTNER | ||||
2016 |
ALLOW USE OF RACF FOR ENCRYPTION KEY STORAGE INSTEAD OF USS PATH | ||||
2016 |
SERVER MAY HANG WHEN PROCESSING MULTIPLE REQUESTS OR REQUESTS FROM MULTIPLE USERS | ||||
2016 |
ENABLE SERVER TO WORK IN A VIPA ENVIRONMENT | ||||
2016 |
UI65081 |
BREAK SPACE EFFICIENT RELATIONSHIP AFTER PERFORMING THE UNLOAD | |||
2016 |
ALLOW THE FCFASTREVERSERESTORE KEYWORD TO BE SPECIFIED ON FLASH COPY | ||||
2016 |
VARY ONLINE NOT ISSUED FOR ALL VOLUMES PREVIOUSLY SET TO OFFLINEIN RESTORE JOB USING BYPASS_VARY=N | ||||
2016 |
DSN1984I MAY OCCUR WHEN TRYING TO RECOVER A SINGLE DROPPED TABLEFROM A MULTI-TABLE TABLESPACE | ||||
2016 |
ARYJ101E SPACE NOT ACCESSIBLE IN STEP CRST#### | ||||
2016 |
ICH408I ARYUILOG WITH 0C4 PROCESSING COMMAND ' ARY$MAIN ' | ||||
2016 |
ARYT006S - THE PRODUCT IS NOT PROPERLY CONFIGURED TO AUTHENTICATE USERS | ||||
2016 |
POOR PERFORMANCE INSERTING MANY TRANSACTIONS INTO TRANSACTION TABLE | ||||
2016 |
ADD SUPPORT FOR BATCH OPERATIONS IN RECOVERY EXPERT | ||||
2016 |
REDIRECTED RECOVERY FAILS BECAUSE DDL IS GENERATED WHEN DDL GEN OPTIONS ARE SET TO "N" N | ||||
2016 |
S0C4 IN ARYUTIM WHEN PERFORMING REDIRECTED RECOVERIES | ||||
2016 |
SQLCODE -20356 DURING RECOVER PLAN "USING LOAD" | ||||
2016 |
IMAGE COPY UTILITY CAN GENERATE INVALID NAMES FOR IC | ||||
2016 |
GENERATED RESTORE JOBS MAY FAIL WHEN USING MULTI-JOBS | ||||
2016 |
IC FROM SLB MAY FAIL WITH S0C4 | ||||
2016 |
SA03 ABEND MAY OCCUR WHEN CREATE A LBDR PROFILE | ||||
2016 |
PERFORMING FLASH BACKUP USING GROUP NAMES RESULTS IN INVALID LRSN | ||||
2016 |
S0C4 MAY OCCUR AFTER MESSAGE ARYS078E | ||||
2016 |
PARMLIB OPTION ARCHIVE_WARNINGS IS IGNORED WHEN GENERATING A SLBJOB | ||||
2016 |
ABENDSB78 RC18 DURING SLRUPDT | ||||
2016 |
DURING RESTORE, CONDITIONAL RESTART RECORD NOT SET FOR THIRD MEMBER OF 3-WAY DATASHARING GROUP | ||||
2016 |
PROVIDE TOLERATION SUPPORT FOR FUTURE DB2 ENHANCEMENTS | ||||
2016 |
RECOVERY EXPERT REDIRECTED RESTORE MAY ABEND WITH U0008 OR U1008 | ||||
2016 |
TAPE OPTIMIZATION INDEX BUILD OPTIMIZATION DURING OBJECT RECOVERY | ||||
2016 |
TRANSACTION RECOVERY OFILTER GETS ARYR917I IF DB OR TS NAME IS LESS THAN 8 CHARACTERS LONG | ||||
2016 |
ADD THE ABILITY TO SPECIFY TCP/IP STACK IN THE ISPF UI | ||||
2016 |
SYSTEM LEVEL BACKUP MAY NOT MAP THE SOURCE AND TARGET VOLUMES CORRECTLY | ||||
2016 |
DIRECTORY DATASETS MAY SHOW AS 'NON-DB2' DATASETS DURING SUBSYSTEM ANALYSIS AND CONFIGURATION | ||||
2016 |
IEC141I 013-E1 DURING REDIRECTED RECOVERY | ||||
2016 |
UI65081 |
AFTER ICKDSF APAR PI25913 IS APPLIED, RESTORE FROM SLB MAY FAIL WITH MSG ICK10710I | |||
2016 |
SCHEMA LEVEL REPOSITORY CLEANUP PROCEDURE | ||||
2016 |
DIRECTORY DATASETS MAY INCORRECTLY SHOW UP AS 'NON-DB2' DURING " SUBSYSTEM ANALYSIS AND CONFIGURATION " | ||||
2016 |
DIRECTORY DATASETS MAY BE IN MORE THEN ONE VOLUME IN DB2 SUBSYSTEM ANALYSIS AND CONFIGURATION REPORT. | ||||
2016 |
DURING BACKUP OF DATA SHARING GROUP, A MEMBER MAY NOT GET SUSPENDED | ||||
2016 |
ROLLUP APAR FOR VARIOUS GUI FIXES | ||||
2016 |
ABENDU0022 OR ABENDU0047 REASON=00000000 IN LMOD ARYDTL4 DURING LOG BASED RECOVERY | ||||
2016 |
ROLLUP APAR FOR LOG ANALYSIS SERVICES | ||||
2016 |
VARIOUS BUG FIXES | ||||
2016 |
Description not available. Security/Integrity exposure | ||||
2016 |
GUI SCREEN NAVIGATION AFTER RUNNING QUIT TIME REPORT INCOMPLETE | ||||
2016 |
OBJECT DEFINITION LEVELS AND QUIET TIMES FOUND ARE NOT FORMATTEDCLEANLY IN GUI | ||||
2016 |
DO NOT ALLOW A SPECIFICATION AT THE MEMBER LEVEL TO BE COPIED INTHE WEB BROWSER INTERFACE WHEN DSMEMBER = N | ||||
2016 |
TIMESTAMP DEFAULT SORTED ORDER WILL BE ALTERED FOR USABILITY. | ||||
2015 |
UI65081 |
ARY#RIO: VSAM BUFFER SYNCHRONIZATION ERROR WRITING TO A KSDS SHARED ACROSS MULTIPLE LPAR'S | |||
2015 |
UI65081 |
CNTRL CARD RESTORE-LOGS MISSING IN JCL AT DISASTER RECOVERY TIME | |||
2015 |
UI65081 |
ARYS340E - ARY$BUTD - NO OFFLOADED COPY OF SYSTEM BACKUP FOUND FOR SSID | |||
2015 |
AE PI49726 FIX COMPLETION | ||||
2015 |
UNABLE TO RECOVER OBJECT(S) WITHOUT RI ENFORCED TO INCLUDE RELATED OBJECTS. | ||||
2015 |
ROLLUP APAR FOR VARIOUS FIXES | ||||
2015 |
NOT ALL VOLUMES BEING RESTORED WHEN USING AN OFFLOADED SLB | ||||
2015 |
DURING DB2 SUBSYSTEM CUSTOMIZATION ALLOW SEPARATE DSNLOAD AND DSNEXIT LIBRARY SPECIFICATIONS. | ||||
2015 |
VARIOUS FIXES FOR V3.2 |