For a RUN TASK using CMD, the file to be executed under the cover is CMD.EXE. Now, if you have a Program Directory restriction configured for your local user or your remote proxy, then this restricts execution to files in the configured directory only. It may not find a CMD.EXE there and hence fail.
Original Message:
Sent: 07/08/26 08:41 AM
From: MIGUEL ANGEL PUENTE
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Volker could help me ?
2. Executive Summary
The same PROCESS and the same CONVPAPYRUS script. CMDs work correctly in Connect:Direct 6.1.0.2_iFix050, but systematically fail in 6.4.0.0 and 6.4.0.3_iFix019 only when executed using RUN TASK (PGM='NT') using SYSOPTS="CMD(...)".
3. Results matrix
| Environment | Version | Result |
|---|
| PRE | 6.1.0.2_iFix050 | ✔ Correct |
| PRE | 6.4.0.3_iFix019 | ✖ Error LSMR014I |
| PRO | 6.1.0.2_iFix050 | ✔ Correct |
| PRO | 6.4.0.0 | ✖ Error LSMR014I |
4. Evidence
- The initial COPY ends successfully.
- The RUN TASK returns LSMR014I File exe not found during RUN JOB/RUN TASK - rc 2.
- Then LSMG415I Runtask wait failed.
- TXT and AFP files do not exist because the process never generates them.
- The manual execution of the CMD completes successfully.
5. Hypotheses evaluated
| Hypothesis | Status | Justification |
|---|
| Error in CONVPAPYRUS. Commander | Discarded | The script works outside of Connect:Direct. |
| Error in data or parameters | Discarded | The same data works in 6.1. |
| Windows Permissions | Unlikely | It does not explain the change between versions. |
| Change in RUN TASK/SYSOPTS CMD() | Very likely | Matches IBM documentation and incidents. |
6. Technical analysis
RUN TASK (PGM='NT')SYSOPTS=&CMDXPCMD(D:\APLIC\CONNECT\PAPYRUS\APP\CONVPAPYRUS.CMD ...)
The difference in behavior occurs exclusively after the upgrade to the 6.4 branch, maintaining the same PROCESS, script, parameters, and data.
7. IBM References
8. Recommendations
- Upgrade to at least 6.4.0.4_iFix033 or later.
- As a test, temporarily replace CMD(...) with PGM(...) if the PROCESS allows it.* (Its impossible it's Production )
Conclusion: The available evidence suggests that the problem is associated with the treatment of SYSOPTS="CMD(...)" in Connect:Direct 6.4 and not to the CONVPAPYRUS script. CMD. The correlation with IBM-documented issues and the difference between versions make it advisable to validate the behavior after applying the most recent maintenance.
9. Compatibility of recommended versions and levels
| Operating System | Branch | Recommended level |
|---|
| Windows Server 2016 | 6.3.x | 6.3.0.6_iFix060 |
| Windows Server 2019 | 6.3.x | 6.3.0.6_iFix060 |
| Windows Server 2022 | 6.4.x | 6.4.0.5 |
| Windows Server 2025 | 6.4.x | Latest Fix Pack available |
10. Branch Reference 6.1
| Branch | Validated level |
|---|
| 6.1.x | 6.1.0.2_iFix050 |
11. Migration recommendations
- Windows Server 2016/2019: Use 6.3.0.6_iFix060.
- Windows Server 2022: Upgrade directly to 6.4.0.5.
- Do not recommend 6.4.0.0 or 6.4.0.3_iFix019 for this scenario.
- If the problem persists, open IBM case by attaching PROCESS, statistics and logs.
After update from 6.4.0.0 to 6.4.0.5 fp 5 a new execution obtain the same error
could be a syntax change in 6.4.X.X from 6.1.0.2 in host invocation command?
------------------------------
Miguel A. Puente
------------------------------
Original Message:
Sent: 05/27/26 06:36 AM
From: Fumani Hlungwani
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Volker
I have installed the fix 6.3.0.6_iFix060, tested and all good both pgm() and cmd() are working perfectly.
Thank you for the assistance.
Regards
Fumani
------------------------------
Fumani Hlungwani
------------------------------
Original Message:
Sent: Tue May 26, 2026 11:30 AM
From: Volker Friedrich
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
The issue has been fixed in CD Windows 6.3.0.6_iFix060 and 6.4.0.4_iFix033, available on IBM Fix Central.
------------------------------
Volker Friedrich
------------------------------
Original Message:
Sent: Thu May 07, 2026 01:38 AM
From: Fumani Hlungwani
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Volker
I have updated few processes to test with replacing cmd() with pgm(). All the processes I have tested with are now logged in the log file (C:\Connect\FileAgent\Logs) and cleared in the Process Monitor.
Thank you, hopefully when IBM finds the solutions won't require us to change again.
Regards
Fumani
------------------------------
Fumani Hlungwani
Original Message:
Sent: Wed May 06, 2026 07:16 AM
From: Volker Friedrich
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Fumani,
There appears to be an issue with "cmd() args()". IBM Support is currently investigating.
Since you are calling a batch file, you can simply overcome this by replacing cmd() with pgm() in your RUN TASK.
LOGOK RUN TASK PNODE (PGM=WINDOWS)
SYSOPTS="pgm(C:\Connect\Process\logstamp.bat) args(~"&F~" &D &T OK)"
LOGNOTOK RUN TASK PNODE (PGM=WINDOWS)
SYSOPTS="pgm(C:\Connect\Process\logstamp.bat) args(~"&F~" &D &T NOTOK)
------------------------------
Volker Friedrich
Original Message:
Sent: Tue May 05, 2026 08:51 AM
From: Fumani Hlungwani
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Volker
Thank you for feedback, so I went back to check exactly what happened since it was working fine in CD 6.1.0 and 6.3.0. I'm running CD in Windows.
I have picked up these:
1. All our outbound processes have a step to log an entry in the specific folder, which was used in CD 4.6, 4.7, 6.1 and it was working in CD 6.3.0, code below
IF (STEP1 EQ 0) THEN
LOGOK RUN TASK PNODE (PGM=WINDOWS)
SYSOPTS="cmd(C:\Connect\Process\logstamp.bat) args(~"&F~" &D &T OK)"
ELSE
LOGNOTOK RUN TASK PNODE (PGM=WINDOWS)
SYSOPTS="cmd(C:\Connect\Process\logstamp.bat) args(~"&F~" &D &T NOTOK)"
EIF
PEND
2. The script is saved is in this C:\Connect\Process\logstamp.bat) and the logs are saved here C:\Connect\FileAgent\Logs
Script:
@echo off
rem Script to generate a logentry
rem ------------------------------
set LOGDIR=C:\Connect\FileAgent\Logs
set LOGFILE=ConnectDirect.log
set FILENAM=%1
set FDATE=%2
set FTIME=%3
set FSTATUS=%4
echo Filename=%FILENAME%
Fdate=&FDATE%
echo %FDATE%%FTIME% FILE processed: %FILENAM%, Status: %FSTATUS% >> %LOGDIR%\%FDATE%_%LOGFILE%
3. It looks like after installing 6.3.0.6_iFix044, CD can't log the entries in that folder hence we have processes not completing and gets stuck in the process monitor.
4. In the Process Monitor the step name highlighted point to the LOGOK which is the last step after transferring the file to the client.
5. The service account has permission to the folders, I'm not sure if these log entries are being logged somewhere.
------------------------------
Fumani Hlungwani
Original Message:
Sent: Tue May 05, 2026 07:21 AM
From: Volker Friedrich
Subject: IBM Connect Direct v6.3.0.6_ifix044 Process Monitor
Hi Fumani,
which platform are you running Connect Direct on? Is it Windows?
Once a process completes - successfully or with failures - it will be automatically removed from the TCQ.
Processes you see in the TCQ are not completed yet. Typically, they are scheduled, waiting for a connection, executing, retrying or hold in error. For further details, see TCQ Logical Queues - IBM Documentation.
To get more insight of your processes, I suggest to check their TCQ status and statistics.
------------------------------
Volker Friedrich