Trusted transfer sudden errors "XCOMN0287E Error setting remote user id"
Article ID: 429631
Updated On:
Products
Issue/Introduction
On a previously working XCOM for Windows 12.0 production server the error "XCOMN0287E Error setting remote user id" suddenly started to occur one evening for z/OS initiated trusted transfers at 21:00:
*****
2026/02/09 21:00:26 TID=REMOTE PRG=xcomtcp PID=9292 IP=##.###.##.##.###:49328
XCOMN0793I Remote TCP/IP Connection Established.
2026/02/09 21:00:26 TID=073275 PRG=xcomtcp PID=9292 IP=REMOTE
XCOMN0943I REMOTE compression types have been deprecated. Using YES.
2026/02/09 21:00:27 TID=000287 PRG=xcomtcp PID=9292 IP=##.###.##.##.###:49328
XCOMN0805I TCP/IP Connection Ended.
2026/02/09 21:00:27 TID=000287
XCOMN0287E Error setting remote user id
2026/02/09 21:01:19 TID=000287
XCOMN0017I Transfer expired and was removed from queue.
*****
The same error continued until a restart of the xcomd Windows server after midnight at 2026/02/10 02:44:32.
That resolved the issue and subsequent transfers were successful.
The problem also did not return at a later date.
- All users for incoming transfers are authorised by the local XCOM DB2 trusted database.
- The DB2 installation and all related files are on drives that are local to the XCOM server.
- 'Event Viewer > Windows Logs > Application' did not show any DB2 related issues.
What could have been the root cause of the problem?
Environment
XCOM™ Data Transport® for Windows 12.0
XCOM™ Data Transport® for z/OS
Cause
Support reviewed the uploaded db2dialog.log ("C:\ProgramData\IBM\DB2\DB2COPY1\DB2\DIAG0000") and it is showing DB2 was taken down on Feb 9 at 08.50.33 (references to DB2StopMain) and not started again until Feb 10 02.47.30, just after the xcomd was also restarted at 02:44:32. Then incoming transfers were successful from 02:51:17.
The xcom.log shows that there were no incoming transfers between 08.50 and 21:00 on Feb 9 so the error would only have been reported when those incoming transfers started @ 21:00:27.
The xcom.log also showed xcomd was stopped on Feb 9 (08:49:24) just before DB2 (08.50.33) was stopped and then it was restarted around 84 minutes later.
2026/02/09 08:49:24 PRG=xcomd PID=4340
XCOMN0089I The XCOMD XCOM Data Transport Scheduler Service ended.
2026/02/09 10:13:19 PRG=xcomd PID=12116
XCOMN0088I The XCOMD XCOM Data Transport Scheduler Service started, Version r12.0 24110 SP00 64bit for Windows Family (CPIC & TCP/IP).
So either DB2 was not restarted on Feb 9 at the same time as the xcomd or DB2 failed to start for some reason.
Resolution
In summary DB2 was not available on Feb 9 after 8:50 am until it was restarted on Feb 10 at 2:47 am which was the root cause of the XCOMN0287E user id errors.
Feedback
