|
IMS RE 210
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2015 |
ENHANCE DLI BATCH PROCESSING DURING DR PREPARATION PROCESSING | ||||
2015 |
MULTIJOB RESTORE FAILURE PROCESSING SAME VOLUME MULTIPLE TIMES WHEN USING STACKED TAPES | ||||
2015 |
TIMING ISSUE WHERE SSO/SAR PULLS THE OUTPUT FROM JES BEFORE THE MASTER JOB HAS A CHANCE TO CHECK IT RESULTING IN HANG CONDITION |
||||
2015 |
SUPPORT FOR MIGRATED DATA SETS DURING IMAGE COPY DR PREPARATION | ||||
2015 |
SUPPORT FOR FAST PATH SECONDARY INDEXES WHICH ARE VALID IN IMS VERSION 12 AND LATER | ||||
2014 |
ABEND0C4 IN BSY$GDBD WHEN RUNNING JOB FOR QUIET TIME ANALYSIS | ||||
2014 |
WITH PTF UI16617, THE NEW SAMPLE JCL MEMBERS ENDS UP IN SBSYBASEINSTEAD OF SBSYSAMP. 14/06/20 PTF PECHANGE |
||||
2014 |
FIXES FOR THE USER UTILITY SUPPORT AND OTHER RELATED ITEMS. | ||||
2014 |
PERFORM COORDINATED IMS AND DB2 DATABASE RECOVERY USING IMS AND DB2 RECOVERY EXPERT WITHOUT NEEDING SLB AS INPUT | ||||
2014 |
GETTING ERROR TRYING TO FIND VOLUME MIGRAT1 OR MIGRAT2 WHEN SOMEUNDETECTED USER DATA SETS ARE MIGRATED BEFORE RECOVERY. | ||||
2013 |
ADD ABILITY FOR BOTH IMS AND DB2 RECOVERY EXPERT TO PROVIDE A COORDINATED RECOVERY CAPABILITY FOR LOCAL USES. | ||||
2013 |
MULTIPLE QUIET TIME ISSUES AND MISCELLANEOUS ISSUES | ||||
2013 |
SOURCE VOLSER FOR MANUALLY INCLUDED DATA SETS THAT MATCH HLQ FORIMS DATA SETS NOT DETECTED | ||||
2013 |
GETTING DUPLICATE VOLSER CONDITIONS WHEN ZOS IS IPL'D. | ||||
2013 |
ENHANCE OFFLOAD AND RESTORE PROCESSING | ||||
2013 |
S0C4 OCCURS IN BSY#ORGN OFFSET +002E16 DURING SUBSYSTEM ANALYSISWHEN GLOBAL ONLINE CHANGE IS ACTIVE IN THE IMS ENVIRONMENT. | ||||
2013 |
IMS V12 CATALOG SUPPORT | ||||
2013 |
IMS V13 RUN-UNDER SUPPORT FOR IMS RECOVERY EXPERT | ||||
2013 |
WHEN APPLYING PTF UK82173 WE GET A SERIES OF IEW MESSAGES FOLLOWED BY CC=8 | ||||
2013 |
CAR - DATABASES NOT RESTARTED AFTER A PIT RECOVERY / POST UK83449 FIXES | ||||
2013 |
BSYI002I ABEND CODE:0E0 REASON CODE: 00000030 | ||||
2013 |
FAILS TO EXCLUDE NON IMS DATA SETS IF THE DATA SETS ARE EMBEDDEDIN VOLUMES THAT ARE PART OF THE SYSTEM LEVEL BACKUP. | ||||
2012 |
IDENTIFY COORDINATED, CONSISTENT, QUIET TIME FOR A GROUP OF DB2 AND IMS OBJECTS AND THEN RUN PITR FOR SAME OBJECTS | ||||
2012 |
ADD AN OPTION TO HAVE NOTIFY.IC ISSUED FOR DATA SETS INCLUDED INA SYSTEM BACKUP. | ||||
2012 |
BACKUP JOB HANGS WHEN COLLECTING INFORMATION FROM AN SLB FOR OBJECT LEVEL RECOVERY. | ||||
2012 |
AE APAR FOR PM56003 | ||||
2012 |
IMS SUBSYSTEM REGISTRATION IS FAILING BECAUSE IMS CONTROL REGIONSTEPLIB DATA SETS CAN NOT BE DYNAMICALLY ALLOCATED. | ||||
2012 |
ADD OPTION TO ALLOW COORDINATED DR RECOVERY TIMESTAMP TO SEE HOWFAR BACK THE RECOVERY POINT WOULD BE. | ||||
2011 |
ADD FUNCTION TO COORDINATED DB2 AND IMS DISASTER RECOVERY USING VOLUME LEVEL RECOVERY AND RECOVERY TO END OF LAST GOOD LOG. | ||||
2011 |
IMS SYSTEM ANALYSIS TAKES CLOSE TO AN HOUR TO RETURN THE LIST OFVOLUMES AND DATA SETS DISCOVERED IN THE IMS ENVIRONMENT. | ||||
2011 |
PANEL 'BSY$PLX1' ERROR. PANEL FIELD NAME (OR AREA NAME) EXCEEDS MAXIMUM LENGTH OF 8. 11/07/15 PTF PECHANGE |
||||
2011 |
ALLOW FOR STORAGE BASED FLASH COPY CONSISTENCY TO BE USED FOR FLASH COPY AND DFDSS BACKUP PROFILES. | ||||
2011 |
EXTENDING TOLERATION SUPPORT FOR IMS | ||||
2011 |
WHEN REGISTERING IMS SYSTEMS VIA ISPF GET MULTIPLE MESSAGES BSYI410E, BSYI107E AND RC 4 RSN CODE: 17080002 | ||||
2011 |
PROVIDE A SOLUTION FOR SEVERAL MINOR ISSUSES LISTED IN PROBLEM DESCRIPTION | ||||
2011 |
ABEND0C4 IS IN BSY BRGN+29C6 | ||||
2011 |
MSGISPV006 "DATA TRUNCATION OCCURRED DATA FOR CHAR FORMAT VARI- ABLE "RSSBUF" WAS TOO LONG. " IF USING 27*132 SCREEN SIZE. | ||||
2011 |
PROVIDE SUPPORT FOR PITR RECOVERY IN DRF AND FIX VARIOUS PROBLEMS | ||||
2010 |
INDIVIDUAL MULITPLE AREA DATA SETS NOT ALLOWED TO BE EXCLUDED INAPPLICATION PROFILE. | ||||
2010 |
RECOVER A HSAM OR SHSAM DATABASE, THE DRF STEP IS ABENDING WITH MESSAGE FRD6024A | ||||
2010 |
JCL ERROR IN DBRDB STEP DURING APPLICATION RECOVERY. | ||||