Transfer failures to XCOM on i5/OS (AS/400) version r11 (IPv6) GENLVL 1707 SP02 with message id LBE7204
The job log shows:
===
Message . . . . : Application error. MCH0601 unmonitored by CAXC2SSL at statement 0000000035, instruction X'0000'. Cause . . . . . : The application ended abnormally because an exception occurred and was not handled. The name of the program to which the unhandled exception is sent is CAXC2SSL CAXC2SSL as400_pase_DoEnded. The program was stopped at the high-level language statement number(s) 0000000035 at the time the message was sent. If more than one statement number is shown, the program is an optimized ILE program. Optimization does not allow a single statement number to be determined. If *N is shown as a value, it means the real value was not available. Recovery . . . : See the low level messages previously listed to locate the cause of the exception. Correct any errors, and then try the request again. CPF9999 Escape 40 20/09/19 02:15:58.220985 QMHUNMSG *N XCOMR XCOM3 2718 Message . . . . : Function check. CEE9901 unmonitored by XCOMR at statement *N, instruction X'2718'.
Cause . . . . . : An escape exception message was sent to a program which did not monitor for that message. The full name of the program to which the unmonitored message was sent is XCOMR . At the time the message was sent the program was stopped at higher level language statement number(s) *N. If more than one statement number is shown, the program was a bound program. Optimization does not allow a single statement number to be determined. If *N is shown as a value, it means the actual value was not available. Recovery . . . : See the low level messages previously listed to locate the cause of the function check. Correct any errors, and then try the request again. LBE7433 Information 00 20/09/19 02:15:58.224946 QLREXHAN QSYS 064F QLREXHAN QSYS 064F Message . . . . : Error handler 'XCOMCEH' in library 'XCOM3' called for COBOL/400* message 'LBE7204'.
===
XCOM™ Data Transport® for AS/400 i5/OS 11.0 SP02
This problem occurs when the user who starts XCOM TCP or SSL does not have access to the user space created by QSECOFR. Always make sure the user who starts STRXCTCP (user space TCP4M08044) and STRXCTCPS (user space SSL4M08045) has access to those user spaces.
As user who has access to user spaces TCP4M08044 and SSL4M08045: