XCOM fails to terminate after "p xcom" command is entered

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC
• XCOM Data Transport - z/OS

Issue/Introduction

When attempting to bring down XCOM after running some transfers, XCOM accepts the termination command and issues the following error messages:
IEC999I IFG0TC0A,IFG0TC0B,XCOMD ,XCOMD ,DEB ADDR=9CA5D8
IEC999I IFG0TC0A,IFG0TC0B,XCOMD ,XCOMD ,DEB ADDR=9CA908
IEC999I IFG0TC0A,IFG0TC0B,XCOMD ,XCOMD ,DEB ADDR=9D48B0

The termination never completes and the CPU usage by XCOM goes up to 60+%, so the XCOM task must be cancelled by the asid to force it down. User written EXIT01 is turned on.

This issue occurs after upgrading XCOM to r12.0 (GEN LEVEL 1407 SP00). 

Environment

Release:
Component: XCMVS
CA XCOM for z/OS 

Cause

The problem was traced to user written EXIT01.  Not reassembling the EXIT01 when upgrading to a new release and the lack of serialization in the exit are causing this problem.

Resolution

• SO05741 SC03 ABEND DURING SERVER TERMINATION FOR AIX DATA SETS
• Always reassemble the exits, if any, when upgrading to a new release.
• Specify a separate DD (or dynamically allocated dataset) for each EXIT01 task processing in parallel - OR -serialize its use so that only one task is processing that DD at a time. Dynamically allocated DDs would be better, since that method will not create a processing bottleneck while serializing around a single DD. 

 

Additional Information

XCOM for z/OS r12 no longer directly attaches the EXIT01 modules as before. It now dispatches them as a post-processing phase of the transfer itself. It runs using the XCOM internal subtask that was used to perform the transfer. Any failure of this processing can leave the XCOM subtask in an unusable state. This may also lead to problems terminating the XCOM region.

Before XCOM for z/OS  r11.6, XCOM just ATTACHED the EXIT01 code and it ran as its own subtask
At r11.6, it was changed to run as a Transaction Program as part of the transfer - that caused it to be subject to the MAXxxxx and TCPSESS limitations.