|
DB2 Automation Tool Version 2.1
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2006 |
EXECUTING THE "E"XPORT COMMAND FROM AN EMPTY PROFILE LIST RESULTS IN USER ABENDU0050 ( U0050 ) | ||||
2006 |
ADDING MULTIPLE OBJECT PROFILES INCONSISTENT WITH BEHAVIOR OF ADDING MULTIPLE UTILITY PROFILES | ||||
2006 |
ROLL UP APAR | ||||
2006 |
ROLL UP APAR | ||||
2006 |
ENHANCE THE UTILITY DEADLINE PROCESSING TO ALLOW CURRENT DATE AND SPECIFIC TIME OFFSETS TO BE COMBINED | ||||
2006 |
DATASET MANAGER CREATES INCORRECT SYNTAX WHEN VOLUME NAMES WITH LESS THAN FIVE CHARACTERS ARE USED | ||||
2005 |
ALLOW EXEC PARAMETER TO OVERRIDE RETURN CODE VALUE FOR MIGRATED FILES | ||||
2005 |
IMPROVE PERFORMANCE OF ISPF INTERFACE | ||||
2005 |
GROUP ATTACH NAME FOR A DATA SHARING MEMBER SUBYSTEM MAY NOT BE CORRECTLY RESOLVED | ||||
2005 |
HAA072E MESSAGE INCORRECTLY ISSUED WHEN DESELECTING PERCOFFPOS EXCEPTION CONDITION. | ||||
2005 |
UPDATES TO DISASTER RECOVERY PROFILE DESCRIPTION FIELD AND UPDATE OPTION FIELD MAY NOT BE SAVED | ||||
2005 |
SSIDCATL MAY CONTAIN IMAGE COPY INFORMATION OLDER THAN THE SELECTED NUMBER OF DAYS | ||||
2005 |
DISASTER RECOVERY PDS MEMBER SSIDALLC MAY NOT CONTAIN ALL FILE ALLOCATIONS | ||||
2005 |
MISSING FILESEQUENCENUMBER PARAMETER COULD RESULT DURING DISASTER RECOVERY PROCESS. | ||||
2005 |
DISASTER RECOVERY JOB DOES NOT DEFINE ALL REQUIRED IMAGE COPIES | ||||
2005 |
ABEND U0050 IN DISASTER RECOVERY BUILD JOB HAA$YPRU DOES NOT " COPY LOCALSITE LOGS " FOR A VALID VALUE | ||||
2005 |
DON'T DISPLAY NON-EXISTING COLUMNS IN HAA STATISTICS REPORTS | ||||
2005 |
SOME ARCHIVED LOGS MAY NOT BE COPIED DURING THE DISASTER RECOVERY BUILD PROCESS | ||||
2005 |
ARCHIVE LOG COPIES FOR DISASTER RECOVERY ARE COPIED BASED ON THEDATE THE ACTIVE LOG WAS STARTED, NOT ARCHIVED | ||||
2005 |
ABEND S0C1 CAN OCCUR WHEN BUILDING DISASTER RECOVERY JCL | ||||
2005 |
PROVIDE NEW JCLIN WITH UPDATED SYSLIB DD STATEMENTS TO INCLUDE COMMON CODE TO CORRECT POTENTIAL CALLLIBS ISSUES. | ||||
2005 |
ISPF DIALOG ERROR ISPP241 IN DATASET MANAGER WHEN UPDATING VOLUMES IN A STOGROUP | ||||
2005 |
INTERMITTENT ABENDS0C4 IN ISPMAIN WHEN SELECTING A PROFILE AFTERAN ADD UTILITY OR EXECPTION PROFILE ACTION. | ||||
2005 |
SAMPLE HAAADBI CONTAINS INVALID REFERENCES TO HAA V1.3 | ||||
2005 |
REMOVE CREATE STATEMENTS FROM SAMPLIB DDL FOR DLC.SYSCOLDIST AND DLC.SYSCOLDISTSTATS, THESE ARE NO LONGER USED | ||||
2005 |
ERROR MESSAGE DLC133E ERRONEOUSLY ISSUED WHEN ATTEMPTING TO EXPORT A PROFILE TO A 44 CHARACTER PDS | ||||
2005 |
EXPIRATION DATE ON IMAGE COPY PANEL HAA$UCPO RETURNS INCONSISTENT RESULTS | ||||
2005 |
ABEND S0C4 RC11 AT X'1570' IN FEC$BOOT. OTHER S0CX ABENDS, S01F, ETC. CAN ALSO OCCUR | ||||
2004 |
Abend S913 when attempting to update the control file if using non RACF security software and no update permission exists | ||||
2004 |
EXIT FROM EXECUTION REPORTS (OPTION 'R') TO HAA$MAIN RESULTS IN OPTION 'R' ERRONEOUSLY REMAINING DISPLAYED ON THE OPTION LINE | ||||
2004 |
FIELDS 'FROM' AND 'SP' ARE TOO SHORT ON DATASET MANAGER PANEL HAA$DXEQ | ||||
2004 |
DISPLAY ERROR MESSAGES THAT IDENTIFY RACF ERRORS RATHER THAN AN ERRONEOUS "INVALID SUBSYSTEM ID" MESSAGE (HAA400E) | ||||
2004 |
THE IMAGE COPY OPTIONS PANEL ERRONEOUSLY ALLOWS THE USER TO GENERATE INVALID IMAGE COPY UTILITY OPTIONS. | ||||
2004 |
IMPORT/EXPORT CODE REWRITE | ||||
2004 |
SAMPLE CLISTS HAAV21 AND HAAV21C CONTAINS SEQUENCE NUMBERS IN COLUMNS 73 - 80, WHICH CAN CAUSE CLIST FAILURE. | ||||
2004 |
REGISTRATION STEP MISSING WHEN JCL GENERATED IN BATCH, OK FOR ONLINE GENERATION | ||||
2004 |
MAXPRIME KEYWORD NOT GENERATED IN TEMPLATE WHEN BUILDING JOB IN BATCH MODE | ||||
2004 |
MAXPRIME RULES NOT APPLIED FOR ALTER UTILITY WHEN BUILDING JOBS IN BATCH MODE | ||||
2004 |
WHEN EXITING PANEL HAA$YPRU, THE MESSAGE 'HAA0901I PROFILE SAVED' IS ISSUED WHEN NO UPDATES HAVE OCCURRED | ||||
2004 |
The last field of 'Volume list' on panels HAA$USHA and HAA$UEMC for backup options erroneously allows only 5 characters. | ||||
2004 |
ABEND COULD OCCUR WHEN ACCESSING CONTROL FILE TO WHICH NO PERMISSION EXISTS | ||||
2004 |
DISASTER RECOVERY JOB STEP SSIDCATL CONTAINS INVALID APOSTROPHESIN THE FILESEQUENCENUMBERS PARAMETER | ||||
2004 |
S0C4 CAN OCCUR WHEN BUILDING A DISASTER RECOVERY JOB | ||||