Multiple Types of XCOM Failures

Products

• XCOM Data Transport
• XCOM Data Transport - z/OS
• XCOM - SUPPORT

Issue/Introduction

I was recently reached out to by an app group that has a mainframe batch job that has failed multiple times over the last couple months during the XCOM step portion.

In looking through the errors, I have noticed 3 different ones that have come up:

-----

XCOMM0780E Txpi  228: Select exception condition for socket 0

XCOMM0853E ALLOCATION FAILED, MAXMOUNTWAIT EXCEEDED

XCOMM0153E INVALID DATA RECEIVED - EXPECTING FMH7 AFTER RC 0846

-----

Most, if not all of the time, when the job fails, the app team reruns the job without issue.

I have looked at logs for the jobs, the systems, and XCOM, but nothing is standing out.

Is there anything that can be looked at or gathered to help diagnose what could be going on with these errors?

 

Environment

Release : 12.0

Component : CA XCOM Data Transport for z/OS

Resolution

1. Message XCOMM0780E Txpi  228: Select exception condition for socket 0
   Reason 228 is the TCPIP function that failed. 0 is the return value from TCP/IP causing the transfer request to terminate. This message usually indicates a failing socket function and the error return value
   Action:Many errors are the result of the specification of the wrong IPNAME or IPPORT, configuration problems, name resolution on the partner. 
   
2. Message XCOMM0853E ALLOCATION FAILED, MAXMOUNTWAIT EXCEEDED indicates that the wait time for a tape mount was exceeded. For this message you will have to evaluate the value of parameter MAXMOUNTWAIT in your CONFIG member. You would have to determine what should be a valid value based on the workload of the system.
3. Message XCOMM0153E INVALID DATA RECEIVED - EXPECTING FMH7 AFTER RC 0846
   Reason:XCOM has received sense code 0846 from its conversation partner. Check the partner side for the message detailing the actual failure.