Unable to access Endevor MCF libraries via IBM ADDI - Error IAYMF1029E and LDM0521E

Products

• Endevor

Issue/Introduction

When attempting to retrieve elements from Endevor via IBM Application Discovery and Delivery Intelligence (ADDI), the process fails. The ADDI console reports an IAYMF1029E error, and the L-Serv MSGLOG indicates a file server request failure (LDM0521E).

• MF Agent Error ( IAYMF1029E ): Agent/module IAYCONN : ERROR returned from ENDEVOR RC=0012, REASON=0003
• LDM0521E File server request failed - function=0 ddname=FILE001 return code=64 reason code=640

Logs may indicate an HLQ inconsistency where the defined DDName does not match the actual catalogue being used: 

Error log from IBM- ADDI-

17:21:54:00 7:21:54  C1X0006E  C1DEFLTS ELM CTLG NAME DIFFERENT THAN LAST ELM CTLGUSED: EN02.#.####### 
17:21:54:00 ENAPIMGR CALL4000 ROUTINE RC=00012 RE=00003                                                
17:21:54:00 ENAPIMGR PROC4000 COMPLETE MESSAGE SENT - ADDRESS=000DAD3C LENGTH=08D0      

 

 

Environment

• Product: Endevor
• Integration: IBM ADDI (Application Discovery and Delivery Intelligence)
• Components: L-Serv, Endevor MCF (Master Control File)

Cause

This issue frequently occurs in environments that have been cloned or copied (e.g., an existing system like 'EN02' was copied to a new system 'ENT1') without fully updating all associated library definitions or the C1DEFLTS table to reflect the new system identity.

The high-level qualifier (HLQ) definition used by the Endevor environment does not match the datasets allocated or expected by the L-Serv file manager. So, an HLQ mismatch prevents the ADDI connector from successfully accessing the MCF libraries.

Resolution

To resolve this inconsistency, Follow these steps:

1. Analyze Logs: Review the L-Serv and ADDI job logs for element catalogue (CTLGUSED) mismatches. Confirm if the catalogue referenced in the error logs differs from the expected DDName definition. For example, verify if the log references an old catalogue name (e.g., EN02.#.#######) while the DDName is defined for the new environment (e.g., ENT1.#.#######). HLQ mismatch here EN02 vs ENT1. 
2. Inspect C1DEFLTS: Review the contents of the C1DEFLTS table to identify configuration errors or outdated HLQ references (e.g., lingering references to a source system after a clone).
3. Validate Configuration: Use the Endevor BC1PXCNMVALIDATE utility to check the current validity of your element catalogue definitions.
4. Update Definition: Use the BC1PXCNMUPDATE utility to correct the element catalogue HLQ definition in the C1DEFLTS table so that it matches the environment's actual configuration.
5. Refresh Connections: After the definitions are synchronized, restart the ADDI tasks to ensure the new configuration is applied.

Note: If the issue persists after updating the catalogue definition, verify that the service account used by the ADDI connector has the appropriate permissions for the MCF datasets in your security manager (e.g., RACF, ACF2, Top Secret).