Completed XCOM job shows as still executing under CONTROL-M

Products

XCOM Data Transport - z/OS

Issue/Introduction

After applying XCOM 12.0 maintenance CARS2501 an XCOM job completes but CONTROL-M still shows it in executing status.

SYSLOG before maintenance was applied (Friday May 23, 2025)

194A 25143 21:14:04.12 JOB24177 00000285 >$HASP100 FS1MI6XT ON INTRDR XCOM TRANS FROM STC07529
CTMTROLM
194A 25143 21:14:04.12 JOB24177 00000090 $HASP1100 FS1MI6XT Job correlator J0024177JES2RYDEE3699B93.......:CTM_FS
MI6BAL_CRJLT
194A 25143 21:14:04.13 JOB24177 00000285 >$HASP520 FS1MI6XT ON L19.JT1
194A 25143 21:14:04.43 00000281 $HASP524 L19.JT1 INACTIVE
194A 25143 21:14:04.44 JOB24177 00000281 $HASP250 FS1MI6XT PURGED -- (JOB KEY WAS E3699B93)
194A 25143 21:14:07.49 JOB24177 00000281 $HASP540 FS1MI6XT ON L19.SR1 FROM FS# AT JES2RYD8 165 RECORDS
194A 25143 21:14:07.94 JOB24181 00000281 $HASP540 FS1MI6XT ON L19.SR1 FROM FS# AT JES2RYD8 165 RECORDS
194A 25143 21:14:19.09 JOB24186 00000281 $HASP540 FS1MI6XT ON L19.SR1 FROM FS# AT JES2RYD8 653 RECORDS
194A 25143 21:14:27.98 STC07529 00000281 CTMD50S READING JOB DATA BY IEFSSREQ FAILED 0021 TIMES. LAST RC
000-FS1MI6XT/ 24177

SYSLOG after maintenance was applied (Monday May 26, 2025)

194A 25146 21:18:01.83 JOB49506 00000285 >$HASP100 FS1MI6XT ON INTRDR XCOM TRANS FROM STC29525
CTMTROLM

194A 25146 21:18:01.84 JOB49506 00000090 $HASP1100 FS1MI6XT Job correlator J0049506JES2RYDEE36BF4D7.......:CTM_FS
MI6BAL_CRQ42

194A 25146 21:18:01.84 JOB49506 00000285 >$HASP520 FS1MI6XT ON L37.JT1
194A 25146 21:18:01.85 00000281 $HASP524 L37.JT1 INACTIVE
194A 25146 21:18:01.86 JOB49506 00000281 $HASP250 FS1MI6XT PURGED -- (JOB KEY WAS E36BF4D7)

194A 25146 21:18:04.10 JOB49506 00000281 $HASP540 FS1MI6XT ON L38.SR1 FROM FS# AT JES2RYD8 165 RECORDS
194A 25146 21:18:07.11 JOB49507 00000281 $HASP540 FS1MI6XT ON L38.SR1 FROM FS# AT JES2RYD8 165 RECORDS
194A 25146 21:18:09.65 JOB49508 00000281 $HASP540 FS1MI6XT ON L39.SR1 FROM FS# AT JES2RYD8 654 RECORDS
194A 25146 22:00:05.82 JOB24186 00000281 $HASP250 FS1MI6XT PURGED -- (JOB KEY WAS E3699B9F)

The CTMD50S message is ‘normal’ for this job and was appearing every day prior to the weekend maintenance.
Since Monday when the job began to NOT TRACK this message is absent .. but re-appeared again last night upon a successfully tracked run.

Environment

XCOM™ Data Transport® for z/OS

Resolution

The job log output received was for a job that included 2 XCOMJOB steps.
One step schedules the transfer to the XCOM task (TYPE=SCHEDULE)
The other step is a TYPE=INQUIRE, which will inquire on the status of the transfer of the scheduled transfer(s).

Support see that the TYPE=SCHEDULE transfer was successful:
XCOMM0300I REQUEST # 015194 PROCESSED SUCCESSFULLY

The TYPE=INQUIRE was also successful:
XCOMM0655I REQUEST 015194 COMPLETED: SUCCESSFUL TRANSFER

This job also contains multiple steps that are not XCOM related.

The BMC "Control-M for z/OS" Knowledge Article 000272235: CTMD50S while NJE job is still executing says the message CTMD50S can be IGNORED and that it will retry until it can properly detect the status of the job at the remote NJE node.

BMC Support advised Control-M took the wrong JES2 line because of SYSDATA mismatch, often caused by output class changes, message ordering or partial job output capture. This lead to XCOM jobs staying in "Executing" status since the expected completion message or RC was not detected. SYSDATA was transmitted to two different JES lines.
XCOM Engineering advised that there have been no changes to how XCOM writes its SYSOUT.
The fact that things have normalized recently with no fixes or changes to XCOM suggests that the problem was due to a condition in the system, or a problem with how Control-M is processing the SYSOUT. Therefore this problem could not have been caused by XCOM.

BMC Support later advised to change current parameter value ENHNJE=N to ENHNJE=Y.