ABEND S0C4 REASON CODE 11 DURING SHUTDOWN

Products

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

Issue/Introduction

Customer reported the following problem:

-

 

We have had an issue in a Production environment. The XCOM server had a "hung" transaction, so client asked to bounce the XCOM

server  to release it. After the second STOP command was issued and the immediate shutdown started, the server generated a  S0C4

abend with reason code 11:

 

SYSTEM COMPLETION CODE=0C4  REASON CODE=00000011     

 

This of course was flagged as an abnormal termination, which triggered the automatic restart of the server.

 

We have 2 questions:

 

a) Is there any particular PTF that would handle the 0C4   during shutdown?

 

b) Would defining the XCOM listen port as SHARED avoid XCOM not being able to open it?

Environment

OS : z/OS

Release : 12.0

Component : CA XCOM Data Transport for z/OS

Cause

-

Resolution

We provided this response to customer--with help from XCOM L2 Support:

-

1. When you do a STOP of the task it will stop the task in an orderly manner. In other words, it will let whatever 

active work going on at the time to finish. That is why the STOP will not immediately stop the task.

 

2. When you do the STOP,IMMED it tells XCOM to stop the task regardless of what is happening.

 

3. We have several fixes related to the STOP--make sure you have them all    applied.

 

4. Please also review XCOM for z/OS 12.0 doc remarks for  STOP command   (under ● IMMED):

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/traditional-management/ca-xcom-data-transport-for-z-os/12-0/using/operation-and-control/using-the-modify-commands.html#concept.dita_a9f4d3da8d890b76b84918708d81fe27805152b6_STOPCommand  

 

5. Regarding your other question: It is NOT recommended to share the listener port.   

 

-