Product Documentation
Abstract
This document contains a complete list of releases, refreshes and fix packs sorted by version for IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI).
Content
Tab navigation
Table of Contents:
6.1.4.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 5 December 2025 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.4 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.4-ifix2 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.4 base level. |
| APARs fixed | Description |
|---|---|
| PH61877 | BUILD CLIENT STOPS UNEXPECTEDLY DURING PROJECT CREATION IF REPOSITORY DB IS REMOTE DB2 LUW AND INCORRECT CLIENT DRIVER INSTALLED |
| PH63824 | CALL CHAIN REPORT IS NOT SHOWING ALL THE CALL CHAINS |
| PH63822 | DASHBOARD SESSION IS NOT SHOWN IN WEB INTERFACE FOR REMOTE CONNECTION USERS TO ANALYZE CLIENT HELP |
| PH64079 | SYNCHRONIZATION FAILED WHEN USING PARALLEL (BATCH) SYNC. |
| PH64126 | AN ERROR MESSAGE WAS ISSUED RELATED TO DOUBLE CLOSING PARANTHESIS AT A CERTAIN IMS CALL |
| PH64228 | ADDI NOT RESOLVING SYMBOLICS IN IDCAMS CARDS |
| PH64257 | AD PROJECT SHOWS FAIL STATUS IN MONITOR DASHBOARD AFTER SUCCESSFUL BUILD |
| PH64638 | JCL CALL OF A CONTROL CARD IS NOT DONE PROPERLY |
| PH65000 | GETTING SYNTAX ERROR: 'PARSE ERROR, EXPECTING .... ' BUILDING NATURAL PROGRAM. |
| PH65408 | APPLICATION DISCOVERY AND DELIVERY INTELLIGENCE SYNTAX ERROR SYM_END_LOOPS LOOPS |
| PH65534 | AD CONNECT DOWNLOADED LINE BYTE LENGH |
| PH66117 | COBOL PROGRAM BUILD PRODUCING CONFUSING SYNTAX ERROR |
| PH66335 | MISSING RESULTS FOR TO-SIDE VARIABLES IN COBOL VARIABLE USAGE AND FIELD USAGE REPORT |
| PH66336 | ADDI DATASET FLOW NOT GENERATED AS EXPECTED IN A SPECIFIC SCENARIO. MISSING SOME DATA SETS |
| PH66455 | ISSUE WITH PROGRAM RESOLUTION IN JCL ANALYSIS (JOB CALLGRAPH AND PROGRAM USAGE REPORTS) |
| PH66560 | ADDI WHEN PERFORMING SEARCH IN FILES ON A BIG NUMBER OF PROJECTS, THE ANALYSIS FAILS |
| PH66575 | ADDI 613 REPORTING OF DSNS |
| PH66722 | WRONG DISPLAY NAMES FOR DYNAMIC CALLS |
| PH66725 | MISSING INFORMATION IN PGM USAGE IN JOBS |
| PH66954 | "ERROR [104] : ERROR WHILE COLLECTING PROGRAM SEMANTICS" OCCURS WHEN BUILDING A COBOL PROGRAM. |
| PH67309 | SYNTAX ERROR: 'PARSE ERROR, EXPECTING .... ' BUILDING NATURAL PROGRAM. |
| PH67724 | BUILD CONFIGURATION CLI SESSION HANGS WHEN BUILD CONFIGURATION UI SESSION IS OPEN |
| PH67957 | BUILD CONFIGURATION CRASH WHEN RETRIEVE CONTROLM DATA |
| PH67962 | WHEN USING JAPANESE CHARACTERS IN VARIABLE NAMES, SOME CHARACTERS ARE GARBLED AND THE VARIABLES CANNOT BE RECOGNIZED CORRECTLY. |
| PH68259 | SECURITY VULNERABILITY CVE-2022-2068 |
| PH68386 | KOREAN TEXT SHOWS CORRUPTED CHARACTERS IN BUILD CLIENT WHEN OPENING THE SOURCE CODE AND IN THE BUILD OUTPUT TEXT. |
| PH68448 | ADDI'S PGMMODULEMAP.TXT FILE PLACEMENT AND USAGE IS NOT FULLY DOCUMENTED. |
| PH68672 | SECURITY VULNERABILITY CVE-2024-5535 |
| PH68706 | ERROR [1043] : SYNTAX ERROR: 'M' |
| PH68621 | IN PROGRAM CALL GRAPH, SOME COBOL PROGRAM DOESN'T SHOW IMS LINK |
| PH67113 | ADDI AYMF0023E ERROR CODE RETURNED FROM TCP. FUNC: SOCKET |
| PH68039 | IN ADDI DASHBOARD > MONITOR PAGE, "EXPORT ALL LOGS" OR "DOWNLOAD" INDIVIDUAL LOGS DOES NOT WORK |
| PH67562 | BUILD CLIENT FAILS TO BUILD CSD FILE |
| PH67250 | IN ABSA PROJECT A CALL IN ONE ASSEMBLER ISN'T RESOLVED PROPERLY BUT WE SEE EITHER DLM010_R15_62 OR ABSATDLI_R15_62 |
| PH66249 | ON A JAPANESE WINDOWS OS, THE BUILD CLIENT GUI CRASHES WHEN CREATING A NEW PROJECT WITH IBM DB2 LUW AS THE PROJECT DB TYPE. |
| PH67191 | SECOND ADMINISTRATOR CANNOT OPEN PROJECTS UNDER BUILD CONFIGURATION |
| PH67997 | AD BUILD OF PL1 PROGRAMS GIVING ERROR MESSAGE "UNABLE TO COMPILE THE FILE..." |
| PH66207 | THE IMPACT ANALYSIS FOR PL/1 REPORT EXPORTED AS A PDF DOES NOT DISPLAY JAPANESE CHARACTERS ON A JAPANESE WINDOWS OS |
| PH67653 | PROJECTS LIST FAIL TO LOAD FOR AC USERS. |
| PH66183 | IMPACT ANALYSIS NOT WORKING FOR THE 2 AND 3 DEPTH BUT NOT FOR 1 |
| PH66636 | NATURAL SYNTAX ERROR: 'PARSE ERROR WHEN ENCOUNTERING TOKEN' |
| PH66675 | NATURAL SYNTAX ERROR: 'PARSE ERROR, EXPECTING `TOP' OR `BOTTOM' OR `MODULE' OR `ROUTINE' WHEN ENCOUNTERING TOKEN |
| PH64134 | AD CONNECT FAILING WITH AT_TLS USER/PASSWORD: USER PASSWORD HASSPECIAL CHARS NOT CONVERTING ASCII => EBCDIC PROPERLY |
| PH64133 | COBOL SYNTAX ERRORS DURING THE BUILD AT AD613 |
| PH67500 | NATURAL PROGRAM BUILD FAILED WITH SYNTAX ERROR |
| PH64718 | NATURAL ERROR: "ERROR [999] : SYNTAX ERROR: 'PARSE ERROR, EXPECTING `SYM_INT' WHEN ENCOUNTERING TOKEN: I OR: I'" |
| PH63279 | AD BUILD CLIENT ISSUES WITH NATURAL CODE |
| PH65190 | IN ADDI 6.1.2 IFIX4, TWO CICS TRANSACTIONS INCORRECTLY IDENTIFIED INSTEAD OF ONE. HOWEVER, IN AD ANALYZE CLIENT, IT'S CORRECT. |
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 11 April 2025 | Superseded |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.4 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.4-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.4 base level. |
| APARs fixed | Description |
|---|---|
| PH65931 | ADDI API CALL EXTENSIBILITY DOESN'T CORRECTLY RESOLVE A CALLED PROGRAM IF SPECIFIED AS A STRING IN A CALL STATEMENT |
| PH65525 | NOT ENOUGH MEMORY RESOURCES ARE AVAILABLE TO COMPLETE THIS OPERATION' WHILE RETRIEVING CICS DATA USING BUILD CONFIGURATION |
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 26 March 2025 | Superseded |
| Impact assessment |
|---|
| The IBM ADDI V6.1.4.0 base-level package is complete and contains all components at their latest levels; therefore, it can be installed independently. |
| APARs fixed | Description |
|---|---|
| PH63661 | SYNC FAILED FOR SOME PROJECTS WHEN USING PARALLEL (BATCH) SYNC |
| PH64480 | AFTER LOGIN SESSION EXPIRES IN DASHBOARD THE USER IS REQUIRED TO ENTER THE CREDENTIALS TWICE |
| PH64621 | ADDI PREPROCESSING EXTENSIBILITY FEATURE DOES NOT SUPPORT PL1 |
| PH64718 | NATURAL ERROR: "ERROR [999] : SYNTAX ERROR: 'PARSE ERROR, EXPECTING `SYM_INT' WHEN ENCOUNTERING TOKEN: I OR: I'" |
| PH64771 | NATURAL ERROR: VARIOUS SYNTAX ERRORS COMING FROM PROGRAMS |
| PH64971 | ASSEMBLER MACRO BUILD WARNINGS IN BUILDING AN ASSEMBLER PROGRAM IN AD BUILD CLIENT WHEN MACRO EXPANSION FEATURE IS OPTED |
| PH64993 | CLIENT SAW THAT AFTER UPGRADING FROM AD V612IFIX3 TO V613IFIX1 BATCH BACKGROUND PROJECT REPORT CHECK ISN'T WORKING ANYMORE |
| PH65046 | ISSUE WITH ADDI BUILD CONFIGURATION AND EXEC DLI PCB RANKING IN COBOL |
| PH65186 | WHEN RETRIEVING SOURCES FROM CHANGEMAN, AD ATTEMPTED TO ACCESS USS/OMVS FILE SYSTEMS AND RETURNED AN ERROR |
| PH65525 | 'NOT ENOUGH MEMORY RESOURCES ARE AVAILABLE TO COMPLETE THIS OPERATION' WHILE RETRIEVING CICS DATA USING BUILD CONFIGURATION |
| PH65530 | UNABLE TO RECOGNIZE DATASET CALL FROM JOB |
| PH65536 | UPGRADE TO SPRINGBOOT 3 IS REQUIRED, PLEASE PROVIDE THE FIX |
6.1.3.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 5 December 2025 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.3 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.3-ifix3 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.3 base level. |
| APARs fixed | Description |
|---|---|
| PH63824 | CALL CHAIN REPORT IS NOT SHOWING ALL THE CALL CHAINS |
| PH66560 | ADDI WHEN PERFORMING SEARCH IN FILES ON A BIG NUMBER OF PROJECTS, THE ANALYSIS FAILS. |
| PH67562 | BUILD CLIENT FAILS TO BUILD CSD FILE |
| PH66207 | THE IMPACT ANALYSIS FOR PL/1 REPORT EXPORTED AS A PDF DOES NOT DISPLAY JAPANESE CHARACTERS ON A JAPANESE WINDOWS OS |
| PH66183 | IMPACT ANALYSIS NOT WORKING FOR THE 2 AND 3 DEPTH BUT NOT FOR 1 |
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 11 April 2025 | Superseded |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.3 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.3-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.3 base level. |
| APARs fixed | Description |
|---|---|
| PH63661 | SYNC FAILED FOR SOME PROJECTS WHEN USING PARALLEL (BATCH) SYNC |
| PH64480 | AFTER LOGIN SESSION EXPIRES IN DASHBOARD THE USER IS REQUIRED TO ENTER THE CREDENTIALS TWICE |
| PH64621 | ADDI PREPROCESSING EXTENSIBILITY FEATURE DOES NOT SUPPORT PL1 |
| PH64718 | NATURAL ERROR: "ERROR [999] : SYNTAX ERROR: 'PARSE ERROR, EXPECTING `SYM_INT' WHEN ENCOUNTERING TOKEN: I OR: I'" |
| PH64771 | NATURAL ERROR: VARIOUS SYNTAX ERRORS COMING FROM PROGRAMS |
| PH64971 | ASSEMBLER MACRO BUILD WARNINGS IN BUILDING AN ASSEMBLER PROGRAM IN AD BUILD CLIENT WHEN MACRO EXPANSION FEATURE IS OPTED |
| PH64993 | CLIENT SAW THAT AFTER UPGRADING FROM AD V612IFIX3 TO V613IFIX1 BATCH BACKGROUND PROJECT REPORT CHECK ISN'T WORKING ANYMORE |
| PH65046 | ISSUE WITH ADDI BUILD CONFIGURATION AND EXEC DLI PCB RANKING IN COBOL |
| PH65186 | WHEN RETRIEVING SOURCES FROM CHANGEMAN, AD ATTEMPTED TO ACCESS USS/OMVS FILE SYSTEMS AND RETURNED AN ERROR |
| PH65525 | 'NOT ENOUGH MEMORY RESOURCES ARE AVAILABLE TO COMPLETE THIS OPERATION' WHILE RETRIEVING CICS DATA USING BUILD CONFIGURATION |
| PH65530 | UNABLE TO RECOGNIZE DATASET CALL FROM JOB |
| PH65931 | ADDI API CALL EXTENSIBILITY DOESN'T CORRECTLY RESOLVE A CALLED PROGRAM IF SPECIFIED AS A STRING IN A CALL STATEMENT |
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 5 December 2024 | Superseded |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.3 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.3-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.3 base level. |
| APARs fixed | Description |
|---|---|
| PH42088 | DATA FLOW REPORT NOT WORKING PROPERLY WHEN THRESHOLD LEVEL IS 2 OR HIGHER IN IBM APPLICATION DISCOVERY (AD) V5.1.0.8 |
| PH55726 | HANDLE UPPER CASE CONVERSION OF XML TAGS FROM CHANGEMAN ON RECORDS LONGER THAN 80 BYTES |
| PH59443 | GETTING SYNTAX ERROR: 'LTH ATTRIBUTE IS MISSING' BUILDING MFS |
| PH61695 | WHILE COMPILING PL/I FILES, THE COMPILER SEEMS TO BOUNCE BACK AND FORTH BETWEEN A FEW SPECIFIC PL/I FILES |
| PH61722 | PL1 PROGRAM BUILD RESULT IN ?SYNTAX ERROR: 'SCOPE PROBLEM ENCOUNTERED.'? |
| PH62548 | SQL TABLE INFORMATION MISSING AFTER ADDI 6.1.1 IFIX6 INSTALLATION ON NEW ENVIRONMENTSQL TABLE INFORMATION MISSING AFTER ADDI 6.1 |
| PH62646 | AD DOES NOT UNDERSTAND CERTAIN CICS SYNTAX |
| PH62647 | AD IMPACT ANALYSIS IS STUCK AT 51% ON ECLIPSE/IDZ |
| PH62732 | JCL BUILD ISSUE - ERROR[1043] : SYNTAX ERROR : 'SYMLIST' |
| PH62734 | JCL BUILD ISSUE - ERROR[1043] : SYNTAX ERROR: 'HOLD' |
| PH62749 | ERROR TO GENERATE THE PROGRAM CALLGRAPH WHEN SELECTING THE COBOLPROGRAM WHERE A CHARACTER ' APPEARS |
| PH62922 | NATIONAL CHARACTER REPLACED DURING LOCAL_REMOTE SYNC |
| PH63263 | MSMAPCOMPILER CRASHED DURING COMPILATION ON VERSION 6.1.2_IFIX4 |
| PH63279 | AD BUILD CLIENT ISSUES WITH NATURAL CODE |
| PH63309 | CAN'T BUILD COBOL SOURCE WITH EXEC SQL IN DATA DIVISION |
| PH63337 | WHEN BUILDING A PROGRAM WITH PROGRAM ID LONGER THAN 93 CHARACTERS WE GET AN ERROR "COMPILER FAILURE WHEN COMPILING PROGRAM" |
| PH63581 | EXTENSIBILITY PREPROCESSING FEATURE LOOKS BROKEN |
| PH63684 | ADDI INCORRECTLY SHOWING LINKAGES BETWEEN PROGRAMS DUE TO EIBTRNID USAGE |
| PH63891 | THE BUILD CLIENT CHECK REPORT INDICATES MISSING MAP FILES, HOWEVER, THEY CAN BE FOUND IN THE VIRTUAL FOLDER BMS |
For the prerequisites and installation instructions, see Overall Instructions.
| Link | Date Released | Status |
|---|---|---|
| 19 July 2024 | Current |
| Impact assessment |
|---|
The IBM ADDI/AD V6.1.3.0 base-level package is complete and contains all components at their latest levels; therefore, it can be installed independently. Starting with IBM ADDI V6.1.3.0, IBM AD Build Client and Analyze Client provide TLS 1.3 support and other enhancements and there is no compatibility with earlier versions of the product. It is necessary to install or update to the latest version of IBM AD Build Client and Analyze Client that are delivered through the IBM ADDI V6.1.3.0 base-level package. |
| APARs fixed | Description |
|---|---|
| PH60541 | MF PROJECTS FAILED TO CONNECT TO SQL SERVER IF SQL FORCE ENCRYPTION IS ENABLED. |
| PH61691 | WHENEVER DEAD SOURCE CALL STATEMENT IS BEING CALLED/REFERENCED IN THE CALLER MODULE THEN AD DOESN'T RECOGNIZE IT AS DEAD SOURCE |
| PH61779 | Source cannot build with SELECT;WHEN;ELSE statements and function call "to_char" |
| PH61881 | SYNTAX ERROR: 'ERROR IN COLLECTING SEMANTICS WHILE BUILDING A CERTAIN JCL FILE |
| PH61940 | ERROR [1075] : FAILED TO INSERT INTO REPOSITORY DATA FOR THE CURRENT PROGRAM ERROR |
6.1.2.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 5 December 2024 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.1.2 ifix4, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM AD V6.1.2-ifix5 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM AD V6.1.2 base level. The IBM ADDI V6.1.2-ifix5 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH61722 | PL1 PROGRAM BUILD RESULT IN ?SYNTAX ERROR: 'SCOPE PROBLEM ENCOUNTERED.'? |
| PH62732 | JCL BUILD ISSUE - ERROR[1043] : SYNTAX ERROR : 'SYMLIST' |
| PH62734 | JCL BUILD ISSUE - ERROR[1043] : SYNTAX ERROR: 'HOLD' |
| PH62922 | NATIONAL CHARACTER REPLACED DURING LOCAL_REMOTE SYNC |
| PH63263 | MSMAPCOMPILER CRASHED DURING COMPILATION ON VERSION 6.1.2_IFIX4 |
| PH63279 | AD BUILD CLIENT ISSUES WITH NATURAL CODE |
| PH63337 | WHEN BUILDING A PROGRAM WITH PROGRAM ID LONGER THAN 93 CHARACTERS WE GET AN ERROR "COMPILER FAILURE WHEN COMPILING PROGRAM" |
| PH63581 | EXTENSIBILITY PREPROCESSING FEATURE LOOKS BROKEN |
| PH63891 | THE BUILD CLIENT CHECK REPORT INDICATES MISSING MAP FILES, HOWEVER, THEY CAN BE FOUND IN THE VIRTUAL FOLDER BMS |
| Link | Date Released | Status |
|---|---|---|
| 28 June 2024 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.1.2 ifix3, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM AD V6.1.2-ifix4 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM AD V6.1.2 base level. The IBM ADDI V6.1.2-ifix4 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH59818 | PROGRAM CALL GRAPH NOT SHOWING SQL REFERENCE FOR SPECIAL DB2 KEYWORD TIMESTAMP |
| PH59970 | CHECK PROJECT TERMINATED AT USER REQUEST |
| PH60520 | UPDATE MEMBERS IN BUILD CLIENT NOT WORKING |
| PH60643 | I-O-CONTROL. RERUN. CLAUSE CAUSES "ERROR [999] : SYNTAX ERROR: '.' " ON COMPLIE. |
| PH60706 | REPLACING COMMAND CAUSING ERRORS IN BUILD |
| PH60851 | FILTER EXPRESSION IN SYNCHRONIZATION FILE DOES NOT WORK PROPERLY |
| PH61151 | ERRONEOUS CONDITIONAL GOTO THRU EXIT FALL THROUGH REPORTED ON PROGRAM FLOW |
| PH61336 | "AN UNEXPECTED ERROR HAS BEEN ENCOUNTERED. PLEASE CLOSE THE APPLICATION AND START IT AGAIN" WHEN BUILD/MAKE |
| PH61599 | SYMBOLIC INCLUDE NAME IN JCL_PROCLIB CAN'T BE BUILT |
| PH61773 | ADDI IS NOT HANDLING CLIENT CUSTOM DATACOM CALL LOGIC. |
| Link | Date Released | Status |
|---|---|---|
| 28 March 2024 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.1.2 ifix2, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM AD V6.1.2-ifix3 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM AD V6.1.2 base level. The IBM ADDI V6.1.2-ifix3 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH55343 | COBOL BUILD GENERATE WARNING [999] : SYNTAX ERROR: 'SYSTEM_TIME' |
| PH57491 | SQL REFERENCE FOR SPECIAL KEYWORD FINAL NOT ADDED |
| PH58398 | OK/CANCEL BUTTON CANNOT BE CLICKED IN AD V612 JAPANESE BUILD CLIENT SETTINGS WINDOW |
| PH59075 | PL1PREPROCESSOR.LOG SHOWED "SYNTAX ERROR AT TOKEN: ||=" WHILE BUILDING A PL1 PROGRAM. |
| PH59103 | DEAD CODE NOT IDENTIFIED PROPERLY |
| PH59518 | PROGRAM COMPILE TIMEOUT DURING BUILD ON RANDOM COBOL PROGRAMS |
| Link | Date Released | Status |
|---|---|---|
| 15 December 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.1.2 ifix1, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM AD V6.1.2-ifix2 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM AD V6.1.2 base level. The IBM ADDI V6.1.2-ifix2 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH56376 | BUILD CLIENT BUILD PROCESS HANGS ON CERTAIN COBOL PROGRAMS |
| PH56495 | CHECK PROJECT IN BUILD CLIENT FAILED DUE TO A PROGRAM CONTAININGXMLQUERY FOR SQL |
| PH56641 | ERROR [999] : SYNTAX ERROR: 'FETCH' ERROR [999] : SYNTAX ERROR: '1' RECEIVED DURING COBOL PROGRAM BUILD |
| PH57005 | "PROGRAM ID ALREADY DEFINED" MESSAGE |
| PH57054 | APPLICATION DISCOVERY ANALYZE CLIENT SEARCH IN FILES CANNOT FINDSINGLE QUOTE |
| PH57093 | DEAD CODE NOT IDENTIFIED PROPERLY |
| PH57132 | PROGRAMS NOT SAVED IN THE REPOSITORY |
| PH57239 | ERROR [120] : THE LEXER DETECTED UNKNOWN COMBINATION: SOURCE FILE MIGHT BE CORRUPTED. ABORTING SOURCE FILE COMPILATION. |
| PH57309 | 'SEARCH IN FILES' DOESN'T EXCLUDE SOME FOLDERS SPECIFIED IN AD BATCH SERVER'S PROJECT.PROPERTIES FILE AND GIVES UNWANTED RESULTS |
| PH57453 | CHECK STOPS RUNNING WHEN IT ENCOUNTERS AN ASSEMLER INCLUDE IN THE ZOS COBOL FOLDER |
| PH57488 | COMPILATION ERROR SQLCA RECEIVED DURING PROJECT BUILD |
| PH57507 | DEAD CODE NOT IDENTIFIED PROPERLY IN CERTAIN SITUATIONS |
| PH57701 | ERROR [120] : THE LEXER DETECTED UNKNOWN COMBINATION: 'INVALID STATE AT LINE X. SOURCE FILE MIGHT BE CORRUPTED. |
| PH57771 | PLI INCLUDE HAS ITS SOURCE DISPLAYED IN ANALYZE CLIENT INSTEAD OF THE PLI PROGRAM |
| Link | Date Released | Status |
|---|---|---|
| 17 September 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.2 base release, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.2-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.2 base level. |
| APARs fixed | Description |
|---|---|
| PH55454 | SEARCH IN FILES FOR IMS MAP NOT RETURNING RESULTS |
| PH55536 | COBOL BUILD GENERATE SYNTAX ERROR IF A INTEGER ENDED WITH . (DOT) -IN SQL SELECT LIST AND WHERE CLAUSES |
| PH55659 | JCL BUILD FA100525 GENERATE ERROR [1043] : SYNTAX ERROR: 'SOURCE2' |
| PH55684 | DB2 SELECT INTO WITH NULL INDICATOR ON 2 LINES NOT BEING HANDLEDCORRECTLY |
| PH55911 | JCL call to a PL1 program via utility does not show in Job call graph |
| PH56068 | INCORRECT DEAD CODE REPORT |
| PH56081 | EXPANDED SOURCE PROCESSING FOR PL/I INCLUDES NEEDS TO BE ALTEREDSO THAT IT WORKS IN SYNTAX VARIATIONS OF INCLUDE. |
| PH56376 | BUILD CLIENT BUILD PROCESS HANGS ON CERTAIN COBOL PROGRAMS |
| Link | Date Released | Status |
|---|---|---|
| 14 July 2023 | Current |
| Impact assessment |
|---|
The IBM ADDI/AD V6.1.2.0 base-level package is complete and contains all components at their latest levels; therefore, it can be installed independently. Starting with IBM ADDI/AD V6.1.2.0, IBM AD Build Client and Analyze Client provide Cross Java To Mainframe Call Graph support and there is no compatibility with earlier versions of the product. It is necessary to install or update to the latest version of IBM AD Build Client and Analyze Client that are delivered through the IBM ADDI/AD V6.1.2.0 base-level package. |
| APARs fixed | Description |
|---|---|
| PH44452 | AUDIT SERVICE IS IN UNAVAILABLE STATUS ON THE DASHBOARD |
| PH44716 | WAZI WEB UI FOR AD, ASSEMBLER PROGRAMS ARE DISPLAYED AS COBOL PROGRAMS IF THEY ARE CALLED FROM COBOL PROGRAM |
| PH49131 | ADDI DOCUMENTATION DOESN'T YET MENTION WHETHER A SINGLE DATABASEINSTANCE CAN BE SHARED BETWEEN MULTIPLE ADDI SERVERS. |
| PH49406 | SOURCE RETRIEVAL(PDSE) FROM MAINFRAME RESULTED IN 0C4 ABEND |
| PH49953 | AD CONNECT IAYLSTNR GETS DYNALLOC ERROR |
| PH50107 | NO PROJECT NAME IN AUDIT IN SOME OPERATIONS LIKE CROSS APP |
| PH50259 | IBM APPLICATION DISCOVERY 6.0.1 AUDIT EVENTS DIDN'T GET ARCHIVED AFTER THE RETENTION PERIOD IS EXPIRED |
| PH50750 | ADDI CROSS APPLICATION CALLGRAPH, WHEN EXPANDED, SHOWS DIFFERENTRESOURCES THAN THOSE LISTED IN GRAPH INVENTORY. |
| PH51145 | ABEND S0C4 IN AD CONNECT ENDEVOR BATCH POST STEP AFTER INSTALLING AD 6.1.1 |
| PH51435 | CSD FILE COMPILE CRASHES ON AD 602 |
| PH51508 | AD SYNTAX ERROR: 'FOR' AND "(" IN COBOL SQL STATEMENT |
| PH51550 | SECURING PROCESS DOESN'T WORK AND FAILS WITH SEVERAL ERROR MESSAGES |
| PH51662 | COVERAGE OF POS=N FOR DFHMDF |
| PH52170 | AD MAINFRAME CONNECT D3.2 PSW ADDRESS CHANGE VIA DCB BUFFER OVERFLOW |
| PH52857 | MISSING DATA IN COLUMN NULLS FOR MFDB2COLUMN TABLE |
| PH52960 | ADDI 6.1.1 ANALYZE CLIENT LOGS MSG " ERROR OCCURRED WHILE REQUEST CROSS DATA (HTTP RESPONSE CODE:400)"ONCE PER SECOND. |
| PH53310 | ANALYZE CLIENT - WHEN EXPANDING A SOURCE FILE, SOME CHARACTERS ARE NOT SHOWN CORRECTLY. |
| PH54110 | SEARCH IN RESULTS DOESN'T SEARCH IN ALL PROJECTS RESULTS BUT ONLY IN FIRST OR SELECTED PROJECT |
| PH54505 | DOCUMENTATION REGARDING MQ OPERATIONAL INFORMATION AND HOW IT CAN BE USED IN APPLICATION DISCOVERY IS INCOMPLETE. |
| PH54697 | ERROR PROCESSING BUFFER IN PROCESSING TASK: OPERATOR_CMD_CPU |
| PH55193 | IMS MAP BUILD GENERATE ERROR [1043] : SYNTAX ERROR: 'LTH ATTRIBUTE IS MISSING' |
| PH55243 | JCL BUILD GENERATE SYNTAX ERROR: 'ERROR IN COLLECTING SEMANTICS' |
| PH55454 | SEARCH IN FILES FOR IMS MAP NOT RETURNING RESULTS |
6.1.1.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 15 December 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.1 ifix5, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.1-ifix6 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.1.1 base level. The IBM ADDI V6.1.1-ifix6 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH56376 | BUILD CLIENT BUILD PROCESS HANGS ON CERTAIN COBOL PROGRAMS |
| PH56495 | CHECK PROJECT IN BUILD CLIENT FAILED DUE TO A PROGRAM CONTAININGXMLQUERY FOR SQL |
| PH56641 | ERROR [999] : SYNTAX ERROR: 'FETCH' ERROR [999] : SYNTAX ERROR: '1' RECEIVED DURING COBOL PROGRAM BUILD |
| PH56784 | MFS ERRORS IN ADDI BUILD |
| PH57005 | "PROGRAM ID ALREADY DEFINED" MESSAGE |
| PH57054 | APPLICATION DISCOVERY ANALYZE CLIENT SEARCH IN FILES CANNOT FINDSINGLE QUOTE |
| PH57132 | PROGRAMS NOT SAVED IN THE REPOSITORY |
| PH57161 | PROJECT CHECK FAILS FOR THE PROJECT WITH ERROR: "AN ERROR OCCURRED DURING THE VERIFICATION PROCESS." |
| PH57239 | ERROR [120] : THE LEXER DETECTED UNKNOWN COMBINATION: SOURCE FILE MIGHT BE CORRUPTED. ABORTING SOURCE FILE COMPILATION. |
| PH57309 | 'SEARCH IN FILES' DOESN'T EXCLUDE SOME FOLDERS SPECIFIED IN AD BATCH SERVER'S PROJECT.PROPERTIES FILE AND GIVES UNWANTED RESULTS |
| PH57771 | PLI INCLUDE HAS ITS SOURCE DISPLAYED IN ANALYZE CLIENT INSTEAD OF THE PLI PROGRAM |
| PH58395 | GRAPH, REPORT OR USAGE DOES NOT SHOW SQL TABLES ASSOCIATED WITH INSERT STATEMENTS IN THE COBOL PROGRAM |
| Link | Date Released | Status |
|---|---|---|
| 17 September 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.1 ifix4, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.1-ifix5 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.1.1 base level. The IBM ADDI V6.1.1-ifix5 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH55454 | SEARCH IN FILES FOR IMS MAP NOT RETURNING RESULTS |
| PH55536 | COBOL BUILD GENERATE SYNTAX ERROR IF A INTEGER ENDED WITH . (DOT) -IN SQL SELECT LIST AND WHERE CLAUSES |
| PH55659 | JCL BUILD FA100525 GENERATE ERROR [1043] : SYNTAX ERROR: 'SOURCE2' |
| PH55684 | DB2 SELECT INTO WITH NULL INDICATOR ON 2 LINES NOT BEING HANDLEDCORRECTLY |
| PH55911 | JCL call to a PL1 program via utility does not show in Job call graph |
| PH56068 | INCORRECT DEAD CODE REPORT |
| PH56081 | EXPANDED SOURCE PROCESSING FOR PL/I INCLUDES NEEDS TO BE ALTEREDSO THAT IT WORKS IN SYNTAX VARIATIONS OF INCLUDE. |
| PH56376 | BUILD CLIENT BUILD PROCESS HANGS ON CERTAIN COBOL PROGRAMS |
| PH56784 | MFS ERRORS IN ADDI BUILD |
| Link | Date Released | Status |
|---|---|---|
| 25 May 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.1 ifix3, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.1-ifix4 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.1.1 base level. The IBM ADDI V6.1.1-ifix4 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH53160 | COBOL SYNTAX ERRORS ON AD |
| PH53538 | AD ANALYZE CLIENT V6.1.1 WHEN EXPORTING JAPANESE REPORTS IN PDF OR XLSX FORMAT FAILS WITH AN ERROR |
| PH54012 | WARNING [999] : SYNTAX ERROR DURING BUILD |
| PH54110 | SEARCH IN RESULTS DOESN'T SEARCH IN ALL PROJECTS RESULTS BUT ONLY IN FIRST OR SELECTED PROJECT |
| PH54283 | ERROR[1044]:MISSING PROCS EVEN THOUGH PROC EXISTS IN CORRESPONDING PROJECT FOLDER |
| PH54392 | AD BUILD CLIENT 6.1.1 NEEDS THE MSOLEDBSQL DRIVER FROM VERSION 18 UP TO 18.6.5; |
| PH54425 | SYNTAX ERRORS DURING BUILDING A COBOL PROGRAM WHICH HAS AN INCLUDE STATEMENT WITHIN THE EXEC SQL BLOCK |
| PH54675 | AD SYNTAX ERROR: UOW PARAMETER ON THE EXEC CICS INQUIRE |
| Link | Date Released | Status |
|---|---|---|
| 12 April 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.1 ifix2, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.1-ifix3 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.1.1 base level. The IBM ADDI V6.1.1-ifix3 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH52781 | COBOL COMPILER THROWS SYNTAX ERROR WHEN CERTAIN BUILT-IN SQL/XMLFUNCTIONS / SQL UPDATE STATEMENT USE " WHEN SPECIFYING TABLE |
| PH52910 | AD Batch Import fails when JCL program contains a statement "RUNPROGRAM" program between apostrophes/single quotes. |
| PH53308 | IAYAA0052I COMPILATION OF THE 'XXXXX.CBL' FILE FAILED. THE PROCESS WAS TERMINATED DUE TO LONG TIME PROCESSING |
| Link | Date Released | Status |
|---|---|---|
| 10 Febuary 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.1 ifix1, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.1-ifix2 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.1 base level. The IBM ADDI V6.1.1-ifix2 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH51122 | THE AD JCL COMPILER COULD NOT FIND SPECIFIC JCL STEPS DEFINED INNESTED "IF THAN" JCL STATEMENTS WHEN AN OVERRIDE WAS PERFORMED.1 |
| PH52073 | BUILD CLIENT CRASHES |
| PH52031 | AD 6.0.2 - MISSING DATA IN MFDB2DATABASES TABLE AFTER RETRIEVEDOPERATIONAL INFORMATION FROM DB2 |
| Link | Date Released | Status |
|---|---|---|
| 1 December 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.1, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.1.1-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI/AD V6.1.1 base level. |
| APARs fixed | Description |
|---|---|
| PH42121 | DELETED USERS REAPER AFTER AUDIT SERVICE RESTART |
| PH49406 | SOURCE RETRIEVAL(PDSE) FROM MAINFRAME RESULTED IN 0C4 ABEND |
| PH49422 | THE CRITERIA PROJECT NAME IN AUDIT DOES NOT FILTER THE EVENTS INAD V6.0.1 |
| PH49676 | WARNING [999] : SYNTAX ERROR: 'DISABLED' IN COMPILATION LOG FOR ENABLESTATUS(DISABLED). |
| PH49855 | ERROR [120] : THE LEXER DETECTED UNKNOWN COMBINATION: 'COPY' |
| PH49859 | SYNCHRONIZATION IS NOT DELETING THE MEMBERS IN PROJECT IF A LIBRARY WAS EMPTIED OF ITS MEMBERS ON MAINFRAME. |
| PH50102 | ADDI JCL BUILD ERROR [1047] and Override is performed was not found in JCL |
| PH50174 | SYNC PROCESS STOPS AND CRASHES AT 99% |
| PH50259 | IBM APPLICATION DISCOVERY 6.0.1 AUDIT EVENTS DIDN'T GET ARCHIVED AFTER THE RETENTION PERIOD IS EXPIRED |
| PH50265 | ERROR WHILE TRYING TO ADD WORKSPACE VIA AD ADMIN DASHBOARD |
| PH50936 | AD BUILD GENERATE: "ERROR [120] : THE LEXER DETECTED UNKNOWN COMBINATION: '.'" |
| PH50962 | AD BUILD - FAILED TO CREATE A PROJECT IF SQL USER PASSWORD CONTAIN SPECIAL CHARACTERS LIKE § CHAR. |
| PH51117 | COM ERROR "IDISPATCH ERROR #3119 WHEN APPLYING ASSEMBLER MANUAL RESOLUTIONS |
| PH51120 | IBM AD BUILD CLIENT SOMETIMES THROWS "ERROR WHILE SAVING PROJECT : INTEGRITY VIOLATION" WHEN SAVING A BIG PROJECT |
| PH51122 | THE AD JCL COMPILER COULD NOT FIND SPECIFIC JCL STEPS DEFINED INNESTED "IF THAN" JCL STATEMENTS WHEN AN OVERRIDE WAS PERFORMED. |
| Link | Date Released | Status |
|---|---|---|
| 7 October 2022 | Current |
| Impact assessment |
|---|
The IBM ADDI/AD V6.1.1.0 base-level package is complete and contains all components at their latest levels; therefore, it can be installed independently. Starting with IBM ADDI/AD V6.1.1.0, IBM AD Connect for Mainframe and Build Client provide pass phrase support and there is no compatibility with earlier versions of the product. It is necessary to install or update to the latest version of IBM AD Connect for Mainframe and Build Client that are delivered through the IBM ADDI/AD V6.1.1.0 base-level package. |
| APARs fixed | Description |
|---|---|
| PH31594 | ZOS COBOL ERROR [999] : SYNTAX ERROR:'1'. |
| PH46038 | MODULE IAYCONN, CSECT IAYPSCAN, OFFSET X'9E': ABEND S0C1. |
| PH47212 | FETCH IN DELETE STATEMENT CAUSED WARNING [999] : SYNTAX ERROR: 'FETCH' DURING COBOL BUILD. |
| PH47235 | SELECT SYNTAX ERROR SUPPORT. |
| PH48243 | PROGRAMS DUPLICATING AFTER PARTIAL BUILD. |
| PH49198 | JCL COMPILER DOES NOT SAVE THE TEMPORARY DATASET NAME CORRECTLY. |
| PH49406 | SOURCE RETRIEVAL(PDSE) FROM MAINFRAME RESULTED IN 0C4 ABEND. |
| PH49590 | JMCOBOL GOES IN AN INFINITE LOOP. |
| PH49589 | JMCOBOL LEVEL 88 ITEM IS IGNORED. |
6.1.0.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 12 April 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.1.0-ifix4, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.0-ifix5 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.1.0 base level. The IBM ADDI V6.1.0-ifix5 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 10 Febuary 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.0 ifix3, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.1.0-ifix4 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.1.0 base level. The IBM ADDI V6.1.0-ifix4 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH52073 | BUILD CLIENT CRASHES |
| Link | Date Released | Status |
|---|---|---|
| 1 December 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.0-ifix2, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.1.0-ifix3 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.1.0 base level. The IBM ADDI/AD V6.1.0-ifix3 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH42121 | DELETED USERS REAPER AFTER AUDIT SERVICE RESTART |
| PH49422 | THE CRITERIA PROJECT NAME IN AUDIT DOES NOT FILTER THE EVENTS INAD V6.0.1 |
| PH50259 | IBM APPLICATION DISCOVERY 6.0.1 AUDIT EVENTS DIDN'T GET ARCHIVED AFTER THE RETENTION PERIOD IS EXPIRED |
| Link | Date Released | Status |
|---|---|---|
| 20 September 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.0-ifix1, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.1.0-ifix2 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.1.0 base level. The IBM ADDI/AD V6.1.0-ifix2 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 19 August 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.1.0, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.1.0-ifix1 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.1.0 base level. The IBM ADDI/AD V6.1.0-ifix1 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH47527 | AFTER DELETING THE -DJAVAX.NET.SSL.* ENTRIES FROM THE ECLIPSE.INI, THE ADDI SERVICES WERE CAUGHT. |
| Link | Date Released | Status |
|---|---|---|
| 31 May 2022 | Current |
| Impact assessment |
|---|
The IBM ADDI/AD V6.1.0.0 base-level package is complete, and it contains all components at their latest levels. Therefore, it can be installed independently. Starting with IBM ADDI/AD V6.1.0.0 there is no compatibility with previous versions of IBM AD Analyze Client. It is necessary to install or update to the latest version of IBM AD Analyze Client. The latest version of IBM AD Analyze Client is delivered through the IBM ADDI/AD V6.1.0.0 base-level package. The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new version (V6.1.0.0) of IBM ADDI Extensions. |
| APARs fixed | Description |
|---|---|
| PH23458 | CORRECT PROBLEM PARSING CHANGEMAN XML OUTPUT CONTAINING NON-ASCII CHARACTERS. |
| PH38717 | Error indicating Analyze Client can't create parts displayed in Analysis Browser perspective in IDz, and slf4j errors in .log |
| PH39755 | 'NO VALID PSB FILE INFORMATION FOUND FOR THIS PROGRAM' WARNING NOT SHOWN WHEN BUILDING COBOL EVEN IF PSB FILES ARE MISSING |
| PH40481 | IBM ADDI UNINSTALL FAILURE THRU THE COMMAND LINE |
| PH41619 | FAILED TO CREATE ANNOTATION TO A PROJECT USING ANNOTATION API WHEN THE ACL IS SETUP FOR THE WORKSPACE |
| PH42928 | CONTROL-M ACCESS ERROR RETRIEVING INFORMATION |
| PH43387 | CHANGE MECHANISM TO PERSIST DATA INTO THE DATABASE USING QU |
| PH43424 | PROBLEM OF SEEING VIEWS/POP-UPS PROPERLY SIZED IN ANALYZE CLIEN |
| PH44458 | THE ARGUMENT FOR THE CONNECTION FUNCTION.FROM THE CONFIG FILE AS |
| PH44702 | BATCH SERVICE - THE FOLLOWING ERROR IS RECEIVED AS A RESULT OF "JAVA.NIO.BUFFEROVERFLOWEXCEPTION" |
| PH45296 | MISSING COMPONENTS REPORT IS FAILING. BUILD CLIENT STUCK AND DOES NOT PROGRESS WHEN WE RUN MISSING COMPONENT REPORT. |
| PH45299 | WHEN BUILDING THE WHOLE ASSEMBLER PROJECT THE RESULTS IN AN ABEND IN ADASM.EXE STILL WITH ENABLE MACRO ENABLED. |
| PH45735 | IBM AD 6.0.1 'SEARCH IN FILES' DOES NOT WORK FOR STRINGS CONTAINING SWEDISH NATIONAL CHARACTERS |
| PH47527 | PH47527: AFTER DELETING THE -DJAVAX.NET.SSL.* ENTRIES FROM THE ECLIPSE.INI, THE ADDI SERVICES WERE CAUGHT. |
Table of Contents:
6.0.2.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 25 May 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2-ifix10, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.2-ifix11 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.2 base level. The IBM ADDI V6.0.2-ifix11 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 12 April 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2-ifix9, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.2-ifix10 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.2 base level. The IBM ADDI V6.0.2-ifix10 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH52781 | COBOL COMPILER THROWS SYNTAX ERROR WHEN CERTAIN BUILT-IN SQL/XMLFUNCTIONS / SQL UPDATE STATEMENT USE " WHEN SPECIFYING TABLE |
| Link | Date Released | Status |
|---|---|---|
| 10 Febuary 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.0.2 ifix8, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.2-ifix9 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.0.2 base level. The IBM ADDI V6.0.2-ifix9 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH52073 | BUILD CLIENT CRASHES |
| Link | Date Released | Status |
|---|---|---|
| 1 December 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.0.2-ifix7, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.0.2-ifix8 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.0.2 base level. The IBM ADDI/AD V6.0.2-ifix8 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH42121 | DELETED USERS REAPER AFTER AUDIT SERVICE RESTART |
| PH49422 | THE CRITERIA PROJECT NAME IN AUDIT DOES NOT FILTER THE EVENTS INAD V6.0.1 |
| PH50259 | IBM APPLICATION DISCOVERY 6.0.1 AUDIT EVENTS DIDN'T GET ARCHIVED AFTER THE RETENTION PERIOD IS EXPIRED |
| Link | Date Released | Status |
|---|---|---|
| 20 September 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.0.2-ifix6, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.0.2-ifix7 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.0.2 base level. The IBM ADDI/AD V6.0.2-ifix7 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 20 August 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.0.2-ifix5, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.0.2-ifix6 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.0.2 base level. The IBM ADDI/AD V6.0.2-ifix6 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH45299 | WHEN BUILDING THE WHOLE ASSEMBLER PROJECT THE RESULTS IN AN ABEND IN ADASM.EXE STILL WITH ENABLE MACRO ENABLED. |
| PH47527 | AFTER DELETING THE -DJAVAX.NET.SSL.* ENTRIES FROM THE ECLIPSE.INI, THE ADDI SERVICES WERE CAUGHT. |
| Link | Date Released | Status |
|---|---|---|
| 31 May 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2.0-ifix4, the following components are modified by fixing vulnerability issues:
The IBM ADDI V6.0.2-ifix5 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.2 base level. The IBM ADDI V6.0.2-ifix5 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 19 April 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.0.2.0-ifix3, the IBM Application Discovery Batch Server is modified by fixing a potential security issue. The new version of IBM Application Discovery Batch Server that is delivered through the IBM AD V6.0.2-ifix4 package is v4.0.3. The IBM AD V6.0.2-ifix4 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM AD V6.0.1 base level. The IBM AD V6.0.2-ifix4 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 15 March 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2-ifix2, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH42120 | PROJECT IS SHOWN AS 'FAIL' UNDER DASHBOARD, BUT IT WAS BUILD OK |
| PH43102 | AD BUILD CLIENT AND AD CONNECT DOES NOT SUPPORT THE USE OF TLS CERTIFICATES WITH COMMON NAME TO A HOST NAME. |
| PH43446 | The annotations created for a project are getting deleted after a project rebuild. |
| PH43829 | UPGRADE FROM 602 TO 602IFIX1 ERASED CONTENTS OF SEARCH SERVICE LIB FOLDER RENDERING IT INOPERABLE STATE AFTER UPGRADE |
| PH44462 | WHEN COMPILING AN ASSEMBLER PROGRAM CONTAINING AN EXEC SQL |
| Link | Date Released | Status |
|---|---|---|
| 4 January 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2-ifix1, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH42710 | APPLICATION DISCOVERY API CALL EXTENSIBILITY DOES NOT SHOW VALUES CORRECTLY |
| PH42928 | CONTROL-M ACCESS ERROR RETRIEVING INFORMATION |
| Link | Date Released | Status |
|---|---|---|
| 15 December 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.2, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH41697 | SEARCH IN FILES' ERROR |
| PH42120 | PROJECT IS SHOWN AS 'FAIL' UNDER DASHBOARD, BUT IT WAS BUILD OK |
| PH42599 | DATASET USAGE IN JOBS SHOWS DD NAMES OF PREVIOUS DSN IN THE JOB |
| Link | Date Released | Status |
|---|---|---|
| 22 October 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1.0, the following components are modified:
The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new version (V6.0.2.0) of IBM ADDI Extensions. |
| APARs fixed | Description |
|---|---|
| PH38698 | TLS CERTIFICATES CAN'T BE ADDED IN SECURITY SECTION OF DASHBOARDDUE TO FAILURE AFTER SAVING |
| PH40083 | RTC2AD SCRIPT IS GIVING AN ERROR ON "SUBCOMMAND" DOES NOT SUPPORT -ALLOW |
| PH40057 | IBM ADDI ANALYZE CLIENT 6.0.0.0 GENERATES UNHANDLED EVENT LOOP EXCEPTION DURING EXPLORE OF PROJECT |
| PH41271 | BUILDCLIENT SEEMED TO BE STUCK WHILE DOING SYNC |
| PH40190 | CCS MONITOR PROJECTS OPTION SHOWS ONLY 20 PROJECTS IN THE WEBPAGE |
| PH40634 | ADV600 COBOL PARSING ERROR - ERROR [1075] : FAILED TO INSERT INTO REPOSITORY DATA FOR THE CURRENT PROGRAM |
| PH31164 | STATEMENT 'COPY ... REPLACING ... BY ...' GENERATES WARNING SYNTAX ERROR |
| PH41229 | BATCHMAKESTATUSFILE LOG SHOWS > 100% OF PROJECT VERIFICATION |
| PH40486 | ASSEMBLER PARSE ERROR - ERROR [999] SYNTAX ERROR 'FATAL ERROR WHILE PARSING THE FILE' |
| PH39795 | TEMPORARY PDS DATASET MEMBER IN JCL NOT RECOGNIZED IN AD BUILD PROCESS |
| PH39006 | TABLES ARE NOT REPRESENTED WHEN REQUESTING A CALL GRAPH FOR A COBOL PROGRAM |
| PH38729 | APPLICATION DISCOVERY - PL/1 COMPILER ERROR ERROR [1073] WRONG PREPROCESSING MAPPING |
| PH18465 | UNUSED ROUTINES WITHIN PROGRAM REPORT IS INCORRECT IN AD 5.1.0.3 |
| PH37224 | AUDIT SERVICE USING SUSE LINUX 12 ON IBM Z HOST NOT WORKING FOR REMOTE ADMIN |
| PH40401 | 'COPY' STATEMENT CAUSES "THE FILE DOES NOT CONTAIN AN ASSEMBLER PROGRAM" ERROR DURING PROJECT BUILD |
| PH33582 | ADDI DYNAMIC CALL PROBLEM |
| PH40814 | THE OCCURRENCES BOX DOES NOT APPEAR IN ANALYZE CLIENT SEARCH IN FILES RESULTS IN A PARTICULAR PROJECT |
| PH45299 | WHEN BUILDING THE WHOLE ASSEMBLER PROJECT THE RESULTS IN AN ABEND IN ADASM.EXE STILL WITH ENABLE MACRO ENABLED. |
| PH47527 | AFTER DELETING THE -DJAVAX.NET.SSL.* ENTRIES FROM THE ECLIPSE.INI, THE ADDI SERVICES WERE CAUGHT. |
6.0.1.x Overall instructions
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html. |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 25 May 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1-ifix10, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.1-ifix11 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.1 base level. The IBM ADDI V6.0.1-ifix11 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 12 April 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1-ifix9, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.1-ifix10 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.1 base level. The IBM ADDI V6.0.1-ifix10 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH29778 | PLI INCLUDES NOT FOUND EVEN IF AVAILABLE IN THE INCLUDES FOLDER PATHS |
| Link | Date Released | Status |
|---|---|---|
| 10 Febuary 2023 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI/AD V6.0.1 ifix8, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI V6.0.1-ifix9 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing the IBM ADDI V6.0.1 base level. The IBM ADDI V6.0.1-ifix9 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH52073 | BUILD CLIENT CRASHES |
| Link | Date Released | Status |
|---|---|---|
| 1 December 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1-ifix7, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.0.1-ifix8 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.0.1 base level. The IBM ADDI/AD V6.0.1-ifix8 package contains all fixes provided in the previous iFixes. |
| APARs fixed | Description |
|---|---|
| PH42121 | DELETED USERS REAPER AFTER AUDIT SERVICE RESTART |
| PH49422 | THE CRITERIA PROJECT NAME IN AUDIT DOES NOT FILTER THE EVENTS INAD V6.0.1 |
| PH50259 | IBM APPLICATION DISCOVERY 6.0.1 AUDIT EVENTS DIDN'T GET ARCHIVED AFTER THE RETENTION PERIOD IS EXPIRED |
| Link | Date Released | Status |
|---|---|---|
| 20 September 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1-ifix6, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
The IBM ADDI/AD V6.0.2-ifix7 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI/AD V6.0.2 base level. The IBM ADDI/AD V6.0.2-ifix7 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 20 August 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1-ifix5, the following components marked with "YES" are modified by fixing vulnerability issues; the components marked with "NO" remain unchanged.
|
| Link | Date Released | Status |
|---|---|---|
| 1 June 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1.0-ifix4, the following components are modified by fixing vulnerability issues:
The IBM ADDI V6.0.1-ifix5 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM ADDI V6.0.1 base level. The IBM ADDI V6.0.1-ifix5 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 18 April 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V6.0.1.0-ifix3, the IBM Application Discovery Batch Server is modified by fixing a potential security issue. The new version of IBM Application Discovery Batch Server that is delivered through the IBM AD V6.0.1-ifix4 package is v3.7.5. The IBM AD V6.0.1-ifix4 package is complete, it represents a cumulative refresh of the entire product, it contains all components at their latest levels, and therefore it can be installed independently without installing an earlier iFix level or the IBM AD V6.0.1 base level. The IBM AD V6.0.1-ifix4 package contains all fixes provided in the previous iFixes. |
| Link | Date Released | Status |
|---|---|---|
| 15 March 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1.0-ifix2, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH42120 | PROJECT IS SHOWN AS 'FAIL' UNDER DASHBOARD, BUT IT WAS BUILD OK |
| PH43165 | SYNTAX ERROR IN BUILD PHASE FOR SPECIAL-NAMES IN CONFIGURATION SECTION. |
| PH44851 | BATCH SERVICE - THE FOLLOWING ERROR IS RECEIVED AS A RESULT OF AN IMPORT: "JAVA.NIO.BUFFEROVERFLOWEXCEPTION" |
| Link | Date Released | Status |
|---|---|---|
| 4 January 2022 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1.0-ifix1, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH42710 | APPLICATION DISCOVERY API CALL EXTENSIBILITY DOES NOT SHOW VALUES CORRECTLY |
| Link | Date Released | Status |
|---|---|---|
| 15 December 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.1, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH40190 | CCS MONITOR PROJECTS OPTION SHOWS ONLY 20 PROJECTS IN THE WEBPAGE |
| PH41271 | BUILDCLIENT SEEMED TO BE STUCK WHILE DOING SYNC. |
| PH41697 | SEARCH IN FILES' ERROR |
| PH42120 | PROJECT IS SHOWN AS 'FAIL' UNDER DASHBOARD, BUT IT WAS BUILD OK |
| PH42121 | DELETED USERS REAPER AFTER AUDIT SERVICE RESTART |
| PH42599 | DATASET USAGE IN JOBS SHOWS DD NAMES OF PREVIOUS DSN IN THE JOB |
| Link | Date Released | Status |
|---|---|---|
| 9 July 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM ADDI V6.0.0.0, the following components are modified:
The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new version (V6.0.1.0) of IBM ADDI Extensions. |
| APARs fixed | Description |
|---|---|
| PH07300 | SUPPORT THE PROGRAMS RUN IN A //SYSTIN DD WHEN THE STEP IS EXECUTED USING IKJEFT01, IKJEFT1A, OR IKJEFT1B |
| PH30986 | JCL COMPILER |
| PH31563 | AD 5105 - BUILD HANGS AFTER GETTING A POPUP |
| PH31706 | COBOL COMPILER |
| PH31715 | COBOL COMPILER |
| PH31741 | COBOL COMPILER |
| PH31742 | COBOL COMPILER |
| PH31743 | COBOL COMPILER |
| PH31744 | COBOL COMPILER |
| PH31745 | COBOL COMPILER |
| PH33109 | WSMETRICS TASK CONSTANTLY FAILED WHILE GDBIMPORT, ADIDX, INDEX TASKS ARE WORKING PROPERLY |
| PH33150 | LOGGED MSG JAVA.LANG.STACKOVERFLOWERROR AFTER RUNNING AMS-COMPILER |
| PH34377 | UNINSTALL AND RE-INSTALL OF ADDI 5.1.0.9 CAUSES UPGRADE WIZARD TO APPEAR BY DEFAULT. |
| PH35312 | A CERTAIN CALL STATEMENT GIVES COBOL BUILD ERROR [1075]: FAILED TO INSERT INTO REPOSITORY DATA FOR THE CURRENT PROGRAM |
| PH35503 | ADDI AND DANISH LETTERS IN MEMBER NAMES |
| PH35774 | ADDI: CRYPTIC REPRESENTATION OF UMLAUTS |
| PH36246 | CA7 INGESTION TAKES A LONG TIME |
| PH36259 | CANNOT VIEW AAUTO NETWORK SOURCE CODE IN AD ANALYZE CLIENT |
| PH36681 | APPLICATION DISCOVERY BACKWARD CALL CHAIN REPORT NOT WORKING BEYOND DEPTH OF 3 |
| PH37327 | COBOL COPYBOOKS IN QUOTES ARE NOT RECOGNIZED IN ADDI COBOLPP |
| PH37473 | "SYNTAX ERROR: 'ELSE SCOPE IS UNKNOWN.'", WHILE COMPILING PL/I FILE. |
| PH37513 | ERROR OCCURRED DURING VERSIONING IN THE LAST STEP OF BUILD-COM ERROR: 'NOT ENOUGH STORAGE IS AVAILABLE TO COMPLETE.." |
| PH37681 | COMPILER FAILURE WHEN COMPILING JCL PROGRAM ON AD |
| PH37682 | APPLICATION DISCOVERY BACKWARD CALL CHAIN REPORT WITH DUPLICATE CHAINS |
| PH37684 | APPLICATION DISCOVERY ERROR 1073 ON BUILD |
| PH38020 | BUILD CLIENT |
| PH38073 | ANALYZE CLIENT DOCUMENTATION SHOULD CONTAIN A DESCRIPTION OF EACH OF THE ANALYZE CLIENT FEATURES |
| PH38076 | NUMBER OF DEPENDENT JOBS SHOWN IN CA 7 JOB TRIGGERING FLOW GRAPH MAY BE INCORRECT IN SOME CASES. |
| PH38121 | CA-7 JOB TRIGGERING FLOW GRAPHS ARE LOADING SLOWLY |
| PH38177 | ANALYZE CLIENT |
| PH38309 | ORIENTDB CONFIGURATION FOR SSL MISSING STEPS IN IBM AD BATCH SERVER SECTION |
| PH38327 | INCORRECT FMID LEVEL/SMPE DATASET REFERENCED IN AD6 USERS GUIDE |
| PH38359 | BUILD CLIENT |
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html. |
|---|---|
| Installation instructions |
|
| Link | Date Released | Status |
|---|---|---|
| 19 March 2021 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.9, the following components are modified:
The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new version (V6.0.0.0) of IBM ADDI Extensions. |
| APARs fixed | Description |
|---|---|
| PH19600 | PARTIAL PROCEDURES RESULTS RUNNING JOB USAGE INVENTORY IN ANALYZE CLIENT. |
| PH22467 | IBM AD DOCUMENTATION INCORRECTLY LISTS TARGET FOLDER FOR VALIDATION SERVER TEMPLATE CONFIGURATION FILES |
| PH24105 | UPGRADE STEPS FROM OLDER AD LEVELS TO SOME NEWER LEVELS DON'T MENTION UPDATING ANNOTATIONS DB NAME IN CCS. |
| PH24960 | AD NEEDS TO GIVE A MEANINGFUL ERROR MESSAGES AND A CLICK-THROUGH SOLUTION |
| PH25144 | CHANGING VALUE OF PATH FOR THE RETRIEVED MEMBERS FIELD IN CCS RESULTS IN DELETION OF PROJECT FILES DURING SYNCHRONIZATION |
| PH25757 | AD 5.1.0.6 HTTPS CONNECTION FOR AUDIT IS NOT IMPLEMENTED IN CCS. |
| PH30667 | SEARCH IN FILES FAILED TO RETURN RESULTS USING TERM PATTERN CONTAINING DOT CHARACTER (EG 4.0). |
| PH30752 | THE AD CONNECT FOR MAINFRAME LISTENER STARTED TASK ABENDED WHEN RETRIEVING A CICS CSD FILE. |
| PH31295 | DYNAMIC VARIABLE RESOLUTION MECHANISM IS NOT SUPPORTING SOME SCENARIOS. |
| PH31501 | OVERRIDE RESOLUTIONS USING MANAGE RESOLUTIONS AND PROGRAM CALL GRAPH IS NOT WORKING IN ANALYZE CLIENT-AD 5.1.0.7. |
| PH31506 | AD 5.1.0.8 ERROR READING PROJECT DETAILS FIELD FROM CCS IS DISPLAYED REPEATEDLY IN MAINFRAME SERVICE LOG |
| PH31988 | SHOW JOB'S INFORMATION NOT DISPLAYED FOR JOBS THAT ARE NOT TIME TRIGGERED JOBS |
| PH32057 | JMJCL STOPS OR FAILS COMPILING SOME JCLS WITH SYNTAX ERROR: 'ERROR WHILE PARSING <PATH>\<JCL FILE NAME' |
| PH33108 | DATASET NAMES NOT BEING FULLY RESOLVED WITHIN JCL PROCS |
| PH33644 | CONFIGURE DASHBOARD HANGS WITH SPINNING CIRCLE AFTER ACTIVATING ENVIRONMENT DURING MANUAL UPGRADE TO 5.1.0.9 |
| PH33774 | IBM APPLICATION DISCOVERY V5.1.0.9 PROGRAM FLOW GRAPH DEFECT |
| PH33793 | WEB SERVICES AREN'T STARTING AFTER INSTALLING AD5109 USING NON-DEFAULT INSTALLATION PATH. |
| PH33824 | JMCOBOL MODULE STOPPED WORKING DURING MAKE IN PAT ENVIRONMENT |
| PH33990 | During manual upgrade from pre-5.1.0.7 code level to 5.1.0.9, documentation and GUI messaging are unclear. |
| PH34013 | PROBLEM OF ABNORMAL NAME OF SEGMENTS IN THE USAGE ANALYSIS OF IMS DB |
| PH34105 | PL1 PREPROCESSOR ERRORS DURING BUILD |
| PH34187 | AD DASHBOARD 'MANUAL RESOLUTIONS SERVICE' HAS THE INCORRECT TITLE FOR JOURNAL FILES. |
| PH34233 | INCORRECT SETTING OF DB2 VERSION LEVEL IN BUILD CONFIGURATION MAY CAUSE ERRORS COMMUNICATING TO DB2 |
| PH34356 | AD 5107 BUILD CLIENT GIVING SOME JCL SYNTAX ERROR AND MISSING MESSAGES |
| PH34377 | UNINSTALL AND RE-INSTALL OF ADDI 5.1.0.9 CAUSES UPGRADE WIZARD TO APPEAR BY DEFAULT. |
| PH34380 | JMCOBOL MODULE STOPPED WORKING DURING MAKE IN PAT ENVIRONMENT FOR NON COBOL PROGRAMS |
| PH34461 | PL1 CALL VARIABLE RESOLUTION IN ANALYZE CLIENT |
| PH34532 | SYNTAX ERROR RELATED TO COMMENTS IN THE IDENTIFICATION DIVISION THAT HAVE NO * (asterisk) IN COLUMN 7. |
| PH34648 | HOSTNAME OF CONFIGURATION SERVER >20 CHARS ENTERED DURING BUILD CLIENT INSTALLATION CAUSES JAVA-BASED COMPILER FAILURE. |
| PH34654 | JCL SYNTAX ERRORS WITH CONTINUATION CHARACTER IN COLUMN 72 |
| PH34688 | A COPY STATEMENT EMBEDDED WITHIN ANOTHER STATEMENT IS NOT CORRECTLY EXPANDED AND PARSED BY THE AD COBOL PARSER. |
| PH34809 | MSG " ERROR [82] : VALIDATING CONTROL-M XML FAILED " WHEN BUILDING SOME CONTROL-M FILES IN IBM AD 5.1.0.9 |
| PH35100 | UPDATING A RULE BASED ATTACHMENT IN DASHBOARD DOES NOT REPLACE THE INITIALLY ADDED ATTACHMENT DATA. |
| PH35157 | AD JCL OVERRIDE PROBLEM |
| PH35161 | GRAPH IMPORT IS SUCCESSFUL BUT TAKING A LONG TIME |
Table of Contents:
5.1.0.x Overall instructions
Note: The 5.1.0.x overall instructions apply for 5.1.0.9, 5.1.0.8, 5.1.0.7, 5.1.0.6, 5.1.0.5, 5.1.0.4 and 5.1.0.3 fix packs.
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions | You can use this package to fully install IBM AD without installing the base version (V5.1.0.0) first. For installation instructions, see the Installing section in IBM AD User Guide. If an earlier version of IBM AD is installed, make sure that all the modified components are upgraded to the fix pack version that you want. For upgrade instructions, see the Upgrading section in IBM AD User Guide. After the upgrade, take the following steps:
|
| Link | Date Released | Status |
|---|---|---|
| 17 December 2020 | Current |
| Impact assessment |
|---|
Refer to the specific Readme file that you obtain along with an AD or ADDI ifix package and check the modified components. The following APAR list covers all the APARs that are delivered through AD and ADDI 5.1.0.9 ifix packages cumulatively. |
| APARs fixed | Description |
|---|---|
| PH23837 | AD AGENT MAINFRAME SLOW FIRST TIME RETRIEVAL SOURCES |
| PH26909 | INSTALLATION_STATUS.TXT FILE SAYS THAT SERVICES INSTALLED SUCESSFULLY EVENTHOUGH FOLDER CREATION FAILED FOR THEM |
| PH28106 | BUILD DECISIONS IN ALL VERSIONS USING DB2 AS REPOSITORY AREN'T SAVED. |
| PH28612 | AD CONNECT FOR MAINFRAME - WRONG STATISTICS (SIZE) FOR NON EMPTYMEMBERS |
| PH29778 | PLI INCLUDES NOT FOUND EVEN IF AVAILABLE IN THE INCLUDES FOLDER PATHS |
| PH30007 | ADDI DASHBOARD DOES NOT SHOW CORRECT LICENSE IN USE |
| PH30487 | MISSING INSTRUCTION TYPE REPLACING BY IMS_CALL IN THE IMS DB ANALYSIS |
| PH30592 | ENABLING ADI INDEXING FROM AD DASHBOARD ENTERS INCORRECT VALUE |
| PH31386 | AD 5.1.0.8 INFINITE RUNNING BUILD FOR ASSEMBLER PROGRAM |
| PH31511 | SYNTAX ERROR: 'ERROR IN SAVING DATA TO REPOSITORY IN ... JCL' OCCURS WHEN BUILDING A JCL FILE |
| PH31576 | DURING BUILD GETTING "UNABLE TO COMPILE THE FILE..." FOR COBOL SOURCE |
| PH31585 | COBOL COMPILER ERROR RELATED TO MAX FUNCTION |
| PH38020 | BUILD CLIENT |
| Link | Date Released | Status |
|---|---|---|
| 15 September 2020 | Current |
| Impact assessment |
|---|
Refer to the specific Readme file that you obtain along with an AD or ADDI ifix package and check the modified components. The following APAR list covers all the APARs that are delivered through AD and ADDI 5.1.0.8 ifix packages cumulatively. |
| APARs fixed | Description |
|---|---|
| PH25192 | IBM ADDI REPORTING ASSEMBLER SYNTAX ERRORS IN CODE |
| PH25599 | COBOL ERROR [104] : ERROR WHILE COLLECTING PROGRAM SEMANTICS |
| PH25781 | COBOL COPY STATEMENT SUPRESS OPTION IS IGNORED BY APPLICATION DISCOVERY BUILD CLIENT COBOL COMPILER. |
| PH25974 | GUI MSG ERROR OPENING FILE, AND LOGGED MESSAGE INDICATING BAD PATH AND UNKNOWN PREFIX, WHEN DIFFERENT PATH NOMENCLATURE USED |
| PH26294 | APPLICATION DISCOVERY CONNECT FOR MAINFRAME HIGH CPU USAGE |
| PH26712 | SYMLINK IS CONVERTED INTO REAL REPOSITORY DATA DURING THE UPGRADE PROCESS. |
| PH27140 | AD5105: ERROR WHILE IMPORTING THE DATA FROM ZOS MAINFRAME - WRONG DATA BUFFERS FORMAT |
| PH27577 | A NEW PROJECT CANNOT BE CREATED IN BUILD CLIENT |
| PH27670 | AD AUDIT CONFIGURATION FOR BLOCKING THE ACCESS TO AD AUDIT UI FROM ANY USER |
| PH28716 | AD 5.1.0.7 BATCH IMPORT PROBLEM |
| PH45296 | MISSING COMPONENTS REPORT IS FAILING. BUILD CLIENT STUCK AND DOES NOT PROGRESS WHEN WE RUN MISSING COMPONENT REPORT. |
| Link | Date Released | Status |
|---|---|---|
| 26 June 2020 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.6, the following components are modified:
|
| APARs fixed | Description |
|---|---|
| PH16217 | JMCOBOL MODULE HAS STOPPED WORKING |
| PH22281 | APPLICATION DISCOVERY BUILD CLIENT MIS-INDENTIFYING COMPONENT TYPE |
| PH22714 | BOLDING OF SEARCH IN FILES RESULTS IN OCCURRENCES IS SHIFTED TO THE RIGHT AFTER A JAPANESE CHARACTER APPEARS IN CODE |
| PH22715 | SWEDISH CHARACTERS ARE NOT SHOWN CORRECTLY IN ANALYZE CLIENT V5.1.0.5 VIEW SOURCE WINDOW. |
| PH23335 | IBM AD DOCUMENTATION IS UNCLEAR REGARDING HOW CREDENTIALS OF AD SERVICES ARE USED AND WHAT ACCESS AND PERMISSIONS THEY NEED. |
| PH23504 | APPLICATION DISCOVERY BUILD CLIENT V5.1.0.5 GET STUCK WHEN BUILDING COBOL PROGRAMS AND SEVERAL COBOL WARNING MESSAGES. |
| PH23621 | ADDI 5.1 PROJECT BUILD HANG, JMCOBOL.EXE IS LOOPING. |
| PH23658 | GRAPH VIEW RESIZING RESULTS IN NON-RESPONDING WORKBENCH WITH DURATION OF MINUTES |
| PH23668 | AD V5.1.0.5 COBOL BUILD ERROR [1075] : FAILED TO INSERT INTO REPOSITORY DATA FOR THE CURRENT PROGRAM |
| PH23673 | SWEDISH NATIONAL CHARACTERS ARE NOT SHOWN IN AD ANALYZE MENUS AND GRAPHS IN COBOL PROGRAMS |
| PH23990 | AN ELLIPTIC CATCH ERROR INSTEAD OF THE ACTUAL MESSAGE THAT COMES FROM THE MF: "MF AGENT (ZLG1014U ): AGENT/MODULE IAYCONN |
| PH24222 | WHEN RUNNING IN PARALLEL 10 DIFFERENT SYNC PROCESSES, SOME OF THEM WERE FAILING WITH RC14 ERROR |
| PH24909 | NATURAL - PROBLEM WITH UPDATE MAINFRAME MEMBERS WHEN DATE/TIME STAMP IS SPACES |
| PH25974 | GUI MSG ERROR OPENING FILE, AND LOGGED MESSAGE INDICATING BAD PATH AND UNKNOWN PREFIX, WHEN DIFFERENT PATH NOMENCLATURE USED |
| PH26646 | DEFAULT EDITOR IS NOT OPENING TO SELECTED SECTION (LINE FROM USAGES OR OTHER REPORTS) |
| Link | Date Released | Status |
|---|---|---|
| 13 March 2020 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.5, the following components are modified:
The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new component that is called IBM ADDI Extension. For more information, see IBM ADDI Extension User Guide. |
| APARs fixed | Description |
|---|---|
| PH08624 | BUILD GETTING SQL 'WITH' SYNTAX ERROR |
| PH12824 | GETTING SEVERAL TYPES OF WARNING [999]: SYNTAX ERROR IN AD BUILD CLIENT V5.1.0.2 |
| PH16813 | PROBLEMS WHEN RETRIEVING MEMBERS VIA AD THAT CONTAINS SWEDISH CHARACTERS ON THE NAME |
| PH17335 | ADI INSTALL PATH WHEN USING ADDI INSTALLER ALWAYS DEFAULTS TO C:\ADI, PREVENTING AUTOMATED MIGRATION OF EXISTING DATA. |
| PH18362 | JAVA CROSS APPLICATION CALL GRAPH IS NOT GENERATED AFTER UPGRADE TO 5.1.0.4 |
| PH18636 | FLOWCHART PROBLEM WITH THE SET STATEMENT MADE IN 2 LINES |
| PH19310 | SYNTAX ERROR '(' DURING BUILD COBOL PROGRAM IN 5.1.0.3 |
| PH19415 | AD 5.1.0.3 BUILD CLIENT REPORTS SYNTAX ERROR: '(' WARNING when building Cobol program |
| PH19491 | SEARCH IN FILES RESULTS ARE GARBLED IN V5104 |
| PH20054 | WRONG DISPLAY OF BMS MAP UNDER EXPLORE PROJECT VIEW IN AD ANALYZE CLIENT. |
| PH20504 | BUILD CLIENT IS GETTING HANGED (JMCOBOL HANGS IN DBFILTERS) |
| PH21492 | ERROR [1047]: MISSING DSNAME PARAMETER DURING JCL BUILD PROCESS |
| PH22174 | MSG "ERROR WHILE IMPORTING THE DATA - WRONG DATA BUFFERS FORMAT" APPEARS IN MF_ERRORS LOG AFTER LIBRARIAN SCAN. |
| PH22319 | BUILD ERROR: ERROR 104. ERROR WHILE COLLECTING PROGRAM SEMANTICS IN AD 5.1.0.2 |
| PH22719 | AD AUDIT IS SHOWING LOADING SCREENS, DATA IS LOADED PARTIALLY AND HANGING AND EXPORT IS NOT WORKING. |
| PH22862 | MAINFRAME CONNECTOR DB2 INTEGRATION CONVERT THE BIND INTO BIND PACKAGE AND BIND PLAN |
| PH22952 | MEMBERS INVENTORY REPORT DISPLAYS ELEMENT WITH NUMBER OF LINES = 0 FOR ENDEVOR MEMBERS |
| PH24105 | UPGRADE STEPS FROM OLDER AD LEVELS TO SOME NEWER LEVELS DON'T MENTION UPDATING ANNOTATIONS DB NAME IN CCS. |
| Link | Date Released | Status |
|---|---|---|
| IBM Application Discovery for IBM Z V5.1.0.5 | 13 December 2019 | Current |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.4, the following components are modified:
The IBM ADDI installer also contains a new version (V5.1.0.5) of IBM Application Delivery Intelligence for IBM Z (IBM ADI). |
| APARs fixed | Description |
|---|---|
| PH07559 | ADNATURAL MODULE NOT WORKING |
| PH14043 | IMS PSB RESOURCES ARE ONLY PROCESSED FOR FULL BUILD OR BUILD SELECTION BUT NOT FOR MAKE. |
| PH14044 | A-AUTO RESOURCES ARE ALWAYS PROCESSED (BUILT) FOR MAKE REGARDLESS IF NOT CHANGED. |
| PH14045 | IMS DBD RESOURCES ARE ONLY PROCESSED FOR FULL BUILD OR BUILD SELECTION BUT NOT FOR MAKE. |
| PH15016 | PROBLEM PARSING IDMS COBOL PROGRAM WITH THE ":" |
| PH16710 | I-O CONTROL SYNTAX ERROR IS NOT PARSED |
| PH17941 | PL1 COMMENT CONTAINING SLASH AS THE FIRST CHARACTER CAUSES SYNTAX ERROR |
| PH18366 | WARNING [999] : SYNTAX ERROR: '>' DURING BUILD |
| PH18415 | WARNING [999] : SYNTAX ERROR: 'CONCAT' |
| PH18821 | WHEN USING AD ANALYZE CLIENT IN IDZ, MEMBERS ARE OPENED IN 'EDIT MODE' NOT FOLLOWING THE IDZ DEFINED PREFERENCES |
| PH19104 | ERROR 1075 DURING BUILD COBOL PROGRAM |
| PH19624 | NATURAL MEMBERS CANNOT BE VIEWED WHEN ANALYSIS CLIENT IN IDZ |
| PH20375 | AD 5104 - IDZ CANNOT SEE THE PROGRAM RESOURCE IN THE PROJECT |
| PH20377 | SQL KEYWORD RID NOT SUPPORTED IN AD-BUILD GIVING WARNING |
| PH20413 | AD 5.1.0.4 AUTHENTICATION SERVER (DEX) BINARY ERROR ON LINUX X64 |
| PH20416 | AD 5.1.0.4 FILE SERVICE BINARY ERROR ON LINUX X64 |
| PH20436 | SYNTAX ERROR "POSITION ATTRIBUTE IS MISSING" DURING PROJECT BUILDS. |
| PH20439 | BUILD PROGRESS HANG AND IMPOSSIBLE TO STOP |
| Link | Date Released | Status |
|---|---|---|
| IBM AD V5.1.0.4 | 13 September 2019 | Current |
| What's new |
|---|
| For a list of new features of IBM Application Discovery for IBM Z version 5.1.0.4, see the IBM Application Discovery and Delivery Intelligence for IBM Z Library page. |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.3, the following components are modified:
The following components are new:
The IBM ADDI installer also contains a new version (V5.1.0.4) of IBM Application Delivery Intelligence for IBM Z (IBM ADI). |
| APARs fixed | Description |
|---|---|
| PH11889 | IBM AD CONNECT AGENT - INCORRECT CLASSIFICATION OF SOME PLI SOURCE FILES AS REXX |
| PH12803 | A COBOL "SET TO TRUE" STATEMENT WITH MULTIPLE LEVEL-88 REFERENCES ARE NOT CORRECTLY RESOLVED IN BUILD CLIENT. |
| PH13866 | FIELD EXPANSION REPORT DOES NOT REPORT THE SAME NUMBER OF VARIABLES EACH TIME IT'S RUN. |
| PH13964 | MISSING A PERIOD AFTER THE VARIABLE DEFINITION IN COBOL PROGRAMS CAUSES THE BUILD PROCESS TO HANG IN BUILD CLIENT. |
| PH14275 | PARENT PROGRAM IS NOT OUTPUT WHEN A BACKWARD CALL CHAIN IS RUN FROM A COBOL PROGRAM. |
| PH14455 | SQL TABLE USAGE PROBLEM WITH DOUBLE QUOTATION MARKS IN THE DB2 TABLE NAME. |
| PH14526 | WHEN FLOWCHART RUN FROM ASM SOURCE THE MESSAGE "RESOURCE NAME .XML FLOWCHART FILE IS INVALID" IS OUTPUT. |
| PH14709 | BATCH SERVER) WEB SERVICE CANNOT USE A KEYSTORE FILE OTHER SELF-SIGNED KEYSTORE GENERATED IN AD. |
| PH16710 | I-O CONTROL SYNTAX ERROR IS NOT PARSED. |
| PI96547 | APPLICATION DISCOVERY BUILD CLIENT CAN'T PARSE DB2 SQL STATEMENT. |
| Link | Date Released | Status |
|---|---|---|
| IBM AD V5.1.0.3 | 14 June 2019 | Current |
| What's new |
|---|
| For a list of new features of IBM Application Discovery for IBM Z version 5.1.0.3, see the IBM Application Discovery and Delivery Intelligence for IBM Z Library page. |
| Impact assessment |
|---|
Comparing with IBM AD V5.1.0.2, the following components are modified:
The following components are new:
The IBM Application Discovery and Delivery Intelligence for IBM Z (IBM ADDI) installer also contains a new version (V5.1.0.3) of IBM Application Delivery Intelligence for IBM Z (IBM ADI). |
| APARs fixed | Description |
|---|---|
| PH02454 | SPECIFIC ANALYZE CLIENT FEATURES RESULT IN A CONNECTION ERROR. |
| PH02679 | SYNTAX ERRORS DURING BUILD ON JCL/PROCS PARSING IF STATEMENT IF IT HAS OR IN IT. |
| PH03806 | AD ZOS STARTED TASK HAS TIMESTAMPS IN EUROPEAN TIMEZONE |
| PH03995 | IBM Application Discovery Connector for Mainframe v5.0.5 |
| PH04048 | CALL GRAPH NOT REFERENCING CORRECT PROGRAMS. |
| PH05944 | ADDING DFHLIBS TO STEPLIB. |
| PH06477 | REPLACING ISSUE WITH PREFIX IN PROGRAM ANALYSIS |
| PH08160 | UMM UPDATES UNCHANGED MAINFRAME MEMBERS. |
| PH09582 | MISSING SOME INSTALL INSTRUCTIONS RE: ANNOTATIONS DB. |
| PH10318 | AD BUILD 5.0.5.2 THROWS ERROR WHEN PROCEDURE DIVISION IS IN A COPYBOOK. |
| PH11144 | INVENTORY REPORT CONTAINS SOME STRANGE NUMBERS INSTEAD OF TYPES OF SOURCE. |
| PI82388 | SYSTEM ABEND 0C7 RUNNING MAINFRAME LISTENER (WITH BUILD SERVER NOT YET SUCCESSFULLY CONNECTED TO IT). |
| Link | Date Released | Status |
|---|---|---|
| IBM AD V5.1.0.2 | 27 March 2019 | Current |
| What's new |
|---|
| For a list of new features of IBM Application Discovery for IBM Z version 5.1.0.2, see the IBM Application Discovery and Delivery Intelligence for IBM Z Library page. |
| Impact assessment |
|---|
The following AD components are modified in this fix pack compared with the previous version 5.1.0.0:
|
| APARs fixed | Description |
|---|---|
| PH06534 | PROJECTS NOT RELEASE AFTER AUTO BUILD PROCESS. |
| PH04676 | EMCS HEALTHCHECK CONFIGURATION FOR AD Z/OS AGENT. |
| PH05286 | COBOL PROGRAMS ARE INCORRECTLY INDICATED AS ASSEMBLER WHEN ADDING FILES FROM MAINFRAME. |
| PH05954 | CICS HANDLE CONDITION STATEMENT IS BEING REPORTED AS DEAD/UNREFERENCED CODE. |
| PH00509 | COBOL ERROR [104] : ERROR WHILE COLLECTING PROGRAM SEMANTICS. |
| PH07353 | RETRIEVING DDM MEMBER WITH NAME LONGER THAN 8 BYTES RESULTS IN ERROR. |
| PH08187 | ECLIPSE/IDZ IDE DOES NOT REMEMBER "LAST WORKSPACE" WITH AD ANALYZE CLIENT PLUGIN. |
| PH07683 | COBOL "READ XXX INTO YYY" STATEMENT NOT SAVED INTO REPOSITORY FOR ANALYSIS. |
| PH08111 | RULE BASED ANALYZE DOES NOT DISPLAY THE FAILING LINE ACROSS PAGES. |
| PH07664 | BUILD CLIENT NOT LOGGING OR DISPLAYING ERROR WHEN IT CAN'T RESOLVE LOCALHOST ADDRESS - EDITING NEEDED BEFORE OPEN. |
| PH04071 | DURING ENDEVOR EXTRACTION STC CRASHES IN U3009 AND CONTINUES UNTIL HANGS IN 2 MINUTES. STOPPING AND RELAUNCH REFURBISHES ST. |
| PH07737 | HIGH CPU USAGE IN IBM APPLICATION DISCOVERY CONNECT FOR MAINFRAME STARTED TASK. |
| PI82388 | S0C7 ABEND WHEN USING TELNET TO ACCESS APPLICATION DISCOVERY CONNECT FOR MAINFRAME'S LISTENER PORT. |
| PH08500 | IDISPATCH ERROR #3092 RECEIVED DURING PROJECT REPOSITORY UPGRADE IN AD 5.1 BUILD CLIENT. |
| PH05617 | SQL UPDATE NOT SHOWING ON BACKWARDS IMPACT ANALYSIS REPORT. |
| PH07684 | JAPANESE CHARACTERS TREATED BY COBOL REPLACE STATEMENTS ARE SHOWN GARBLES IN AD ANALYZE CLIENT AND EXPANDED SOURCE CODE. |
| PH08260 | THE MEMBER INVENTORY REPORT SHOWS THE TOTAL MEMBER COUNT INCLUDING THE DELETED RESOURCES. |
| PH07659 | NATURAL - DA FILE IS NOT GENERATED FOR A SPECIFIC DATA AREA FILE. |
| PH06731 | DEFECT IMS SETUP FOR OPERATIONAL INFORMATION RETRIEVAL IN AD CONNECT. |
| PH03970 | S0C7 ABEND IN IAYLSTNR MAINFRAME LISTENER - ENDEVOR SHOP. |
| PH03973 | ERROR WHILE INSERTING INTO THE DATABASE. REASON: DUPLICATE SECTION NAME : 'X910-GET-PERS-BUS-IND-EXIT'. |
| PH09157 | CANNOT START AD ANALYZE CLIENT IN ECLIPSE IF COMPUWARE TOPAZ PLUGIN IS INSTALLED. |
| PH05944 | ADDING DFHLIBS TO STEPLIB. |
| PH09829 | SSL CONFIGURATION FOR ORIENTDB AND BATCH SERVER USING CA-SIGNED CERTIFICATE. |
| PH08160 | MEMBERS WHICH HAVE NOT BEEN CHANGED IN THE MAINFRAME ARE UNEXPECTEDLY UPDATED IN THE SERVER SIDE BY UMM. |
| PH09828 | INCONSISTENT OCCURRENCE OF "ERROR [104] : ERROR WHILE COLLECTING PROGRAM SEMANTICS" FOR SOME COBOL FILES. |
| PH09738 | UNABLE TO COMPILE A MFS FILE IN A IMS PROJECT. |
| PH09842 | WHILE BUILDING/MAKING A PROJECT, GOT JMCOBOL POP-UP ISSUE. |
| PH08108 | CHILDREN COBOL PGMS ARE NOT TAKEN INTO ACCOUNT BY THE CURRENT DYNAMIC RESOLUTION MECHANISM FROM THE COBOL COMPILER. |
| PH05764 | COBOL PROGRAM FAILS TO COMPILE DURING THE BUILD. |
| PH10043 | DYNAMIC VALUES NOT FULLY RESOLVED IN AD EXTENSIBILITY FEATURE FOR FILE ACCESS VIA EXEC CICS CALLS. |
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
|---|---|
| Installation instructions | Being a complete AD package, it can be used to fully install or upgrade an IBM AD instance to the latest version 5.1.0.2 without installing the base version 5.1.0.0 first. Follow the instructions from IBM AD User Guide on how to install or upgrade an existing IBM AD instance. For a fresh installation of AD Connect for Mainframe or for an upgrade from a version older than 5.1.0.0, first install the base version 5.1.0.0 from the IBM AD Connect for Mainframe\5.1.0.0 folder by following the instructions in IBM AD User Guide. Then, apply the 5.1.0.2 fix pack located in the IBM AD Connect for Mainframe\5.1.0.2\SMPE Files folder by following the instructions available in the IBM AD Connect for Mainframe\5.1.0.2\Install instructions folder. If you already have AD Connect for Mainframe 5.1.0.0, just apply the 5.1.0.2 fix pack located in the IBM AD Connect for Mainframe\5.1.0.2\SMPE Files folder by following the instructions available in the IBM AD Connect for Mainframe\5.1.0.2\Install instructions folder. Make sure to upgrade all the modified components to the new version to have a consistent and functional installation. After upgrading the IBM AD code to the latest level, take the following steps: - Upgrade the repository database to the latest level - Perform a full Build of each IBM AD project to correctly populate the repository database and allow the corresponding changes to be propagated to the graph database. Instructions for upgrading the repository can be found at https://www.ibm.com/support/knowledgecenter/SSRR9Q_5.1.0/ibm_ad_user_manual/upgrade_a_repository.html . Instructions for performing a full Build of the project can be found at https://www.ibm.com/support/knowledgecenter/SSRR9Q_5.1.0/ibm_ad_user_manual/Building_Projects.html . |
| Link | Date Released | Status |
|---|---|---|
| IBM AD V5.1.0 | 13 December 2018 | Current |
| What's new |
|---|
| For a list of new features of IBM Application Discovery for IBM Z version 5.1.0, see the IBM Application Discovery and Delivery Intelligence for IBM Z Library page. |
| APARs fixed | Description |
|---|---|
| PH00429 | AD 5.0.4.2 ACCEPTS WRONG CSD INPUT FROM EXTRACT. |
| PH00760 | APPLICATION DISCOVERY FAILED TO INSERT REPOSITORY DATA FOR THE CURRENT PROGRAM. |
| PH00944 | ISSUE WITH PROGRAM CALL RESOLUTION OF NESTED ASSEMBLER PROGRAMS. |
| PH01758 | LISTENER TASK RECORDING 0C7 ABEND IN LOGREC. |
| PH01774 | "ERROR [999]: SYNTAX ERROR: 'PROGRAM-ID'" CAUSED BY OPTIONAL TERMINATING PERIOD IN SOME COBOL BEING HANDLED INCORRECTLY. |
| PH01815 | S0C4 AND S0C7 IN IBM APPLICATION DISCOVERY CONNECT FOR MAINFRAME DURING PDS RETRIEVAL. |
| PH02010 | OK/CANCEL BUTTON CANNOT BE CLICKED IN 5051 JAPANESE BUILD CLIENT SETTINGS WINDOW. |
| PH02029 | APPLICATION DISCOVERY: ENDEVOR IS LISTING MEMBERS THAT ARE NOT SPECIFIED IN SYNCHRONIZATION FILE. |
| PH02056 | MSGS IAYCONN: AGENTS LOST APF AUTHORIZATION. AND C1G0700I PROGRAM ABCRC1 WAS FOUND NOT TO BE AUTHORIZED. ISSUED WHENSYNCHR. |
| PH02250 | APPLICATION DISCOVERY DOES NOT PARSE ++INCLUDE MEMBERS CORRECTLY. |
| PH02274 | COBOL COMPILER HANGS WHEN A VARIABLE REDEFINES ONE OF ITS CHILDREN. |
| PH02372 | BATCH SERVER PROCESSING NEVER STARTS FOR PROJECT AFTER A BUILD OR AFTER RESTARTING BATCH/GRAPHDB SERVICES OR VM REBOOTING. |
| PH02374 | IN AD 505, ANALYZE CLIENT USER COULDN'T VIEW PROJECTS WHEN USER ID IS ENTERED IN UPPERCASE AND ACL ACCESS TO WORKSPACE IS USED. |
| PH02420 | SYNTAX ERROR: 'ERROR IN SAVING DATA TO REPOSITORY IN AD V5.0.4 FOR CERTAIN JCL SYNTAX. |
| PH02449 | "CHECK PROJECT" IN AD BUILD CLIENT DOESN'T REPORT MISSING ++INCLUDE MEMBERS FOR ASSEMBLER PROGRAMS. |
| PH02454 | DELETING A JOB ON MAINFRAME CAN RESULT IN EXCPTION IN GUI. |
| PH02622 | APPLICATION DISCOVERY: IGNORE COMMENTS IN SEARCH IN FILES IS NOT WORKING. |
| PH02625 | APPLICATION DISCOVERY: BACKWARDS IMPACT ANALYSIS REPORTING ISSUE RELATED TO MOVE FUNCTION. |
| PH02723 | AD BUILD SHOWS SYNTAX ERRORS WHEN USING "COLUMN NAMES". |
| PH02929 | JAPANESE TEXT IS DISPLAYING WHEN ANALYSE CLIENT IS CONFIGURED TO DISPLAY FRENCH. |
| PH03214 | USE OF UNDEFINED PARAGRAPH/SECTION ERROR APPEARS IN COBOL COMPILER. |
| PH03471 | APPLICATION DISCOVERY: ABEND 522 TIMEOUT DOCUMENTATION UPDATE. |
| PH03946 | COBOL FIGURATIVE CONSTANTS HIGH-VALUES FLAGGED AS MISSING COMPONENT. |
| PH04419 | MAINFRAME PDS MEMBERS DOWNLOADED AS 0 BYTE FILES INSTEAD OF FILES THAT CONTAIN THE CORRECT CONTENTS. |
| PH04508 | BUILDING A COBOL PROGRAM STOPS WITH THE JMCOBOL.EXE POP-UPS ERROR AND THE BUILD PROCESS HANGS. |
| PH04620 | APPLICATION DISCOVERY: TWS REPRESENTATION: WORKSTATION ENDPOINT MISREPRESENTATION. |
| PH04681 | PROC NOT BEING FOUND MESSAGE IN BUILD CLIENT IF PROC IS CALLED USING SYMBOL. |
| PH04845 | PARALLEL VALIDATION STOPS HALFWAY, RESUMED PROCESSING AFTER STOPPING ADAGREGGATES.EXE. |
| PH04986 | AD 5.0.5 BUILD CLIENT - JMJCL.EXE HANGS WHEN BUILDING JCL PROGRAM. |
| PH05128 | STANDARD SQL DATATYPE STATEMENTS - BIGINT AND NOT - ARE NOT SUPPORTED BY BUILD CLIENT. |
| PH05176 | CSD JAVA PARSER FOR STAND-ALONE CSD FILES MIGHT NEED SOME MODIFICATION TO HANDLE LONG DESCRIPTION FIELDS. |
| PH05179 | THE SQL DATABASE NAME FROM EZ#ANNOTATION IS CAUSING THE CUSTOMER DATABASE BACKUP TO FAIL DUE TO THE '#' SPECIAL SYMBOL. |
| PH05203 | UNHANDLED EXCEPTION CAUSING JMCOBOL TO CRASH. |
| PH05213 | BUILD CLIENT AD 5052 HANGS AND DOES NOTHING RANDOMLY (NO COMMAND FORM MENU OR RIGHT CLICK WORKS). |
| PH05286 | COBOL PROGRAMS ARE INCORRECTLY INDICATED AS ASSEMBLER WHEN ADDING FILES FROM MAINFRAME. |
| PI96739 | BUILD CLIENT NOT OVERRIDDING JCL WITH PROC CORRECTLY. |
| PI99466 | COMPONENT TYPE NOT SPECIFIED IN THE FOLDERMAPPINGS.TXT FILE CAN PREVENT THE VALIDATION PROCESSING TO PROCEED. |
| PI99768 | MEMORY LEAK ISSUE IN AD AGENT CAUSES ENDEVOR API BATCH CALL TO ABEND. |
| Prerequisites | Generate the detailed system requirements report at https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html. |
|---|---|
| Installation instructions | Follow the installation instructions provided in IBM AD User Guide, which can also be found in the IBM Application Discovery and Delivery Intelligence for IBM Z Library page. |
IBM Application Discovery and Delivery Intelligence for IBM Z Support
- To review FAQs, lists of known problems, fixes, and a wealth of important support information, visit the IBM Support Portal.
- To request and track product feature enhancements, visit the IBM RFE Community.
- Interact with IBM Application Discovery and Delivery Intelligence developers and users on the mainframe forum and blog.
Helpful Hints For Obtaining Technical Assistance:
Before you contact IBM Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
Related Information
Was this topic helpful?
Document Information
Modified date:
09 December 2025
UID
swg27049339