SSL listener fails to start on XCOM for AS/400

Products

• XCOM Data Transport

Issue/Introduction

We are trying to start the XCOM SSL listener and it is failing and we don't know the reason for the failure.

Environment

• XCOM™ Data Transport® for AS/400 i5/OS
• IBM i 
   

Cause

The joblog for the XCOM SSL listener showed the following error messages:

MCH6902 Escape 40 04/30/18 10:36:21.491955 
Módulo destino . . . . . . : QC2ALLOC 
Procedimiento destino . . . : do_free_default__FPv 
Sentencia . . . . . . . . . : 2 

and 

C2M1212 Diagnóstico 30 04/30/18 10:36:21.492251 QC2UTIL1 QSYS 
Módulo origen . . . . . . . : QC2ALLOC 
Procedimiento origen . . . : send_message__FiPvUi 
Sentencia . . . . . . . . . : 55 
Módulo destino . . . . . . : TXPISTR 
Procedimiento destino . . . : StrFree 
Sentencia . . . . . . . . . : 15 

and finally

XCM0899 Informativo 00 04/30/18 10:36:21.494089 XCOMMSG3 
Mensaje . . . . : Fatal TCP/IP communications error occurred in program XCOMSRVR during state INIT SERVER. Check second level text for more 
information. 
The error occurred while attempting to perform function INIT SERVER

Return code information is: Primary return code 1 Parameter invalid. 
Secondary return code 0. TCP/IP primary return code 212. 
TCP/IP secondary return code 3420. TCP/IP message Txpi 212: Socket bind error return value = 3420.

If this is a socket error the error description is: Address is already in use. 
 

Resolution

Based on all of those messages here is what you need to check: 

1. 1.  Make sure that you have fixes RO62015 and RO58264. As a matter of fact, if you have XCOM r11.0 SP01 installed on AS/400, the requirement to support that is: 
      
      XCOM Data Transport for AS/400 r11.0 (SP1 with RO83699) 
      XCOM Data Transport for AS/400 r11.0 SP2 
      
      See Informational Solution RI59050 AS400 RISC SUPPORT FOR XCOM DATA TRANSPORT FOR AS/400.  for fixes at each level of the operating system
      
      The above fixes, RO62015 and RO58264, address a problem with those same messages. XCOM r11.0 SP02 has all of the fixes mentioned above.
       
   2. If you have the above fixes or requirements, then the next step is to do the following: 
      1. Make sure that the XCOM2SBS subsystem is down.
      2. Issue command: WRKOBJ xcomlib/*ALL *USRSPC ---> where "xcomlib" is your XCOM library 
      3. Delete all of the user space, such as SSL4M08045 and/or TCP4M08044 
      4. Start the XCOM2SBS and STRXCTCP or STRXCTCPS. The user space should be recreated again.