What do messages XCOMN0288E/XCOMU0288E tell - was the transfer succesful?

book

Article ID: 16845

calendar_today

Updated On:

Products

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

Issue/Introduction



My transfer to Windows or Unix ends with message

XCOMN0288E System function failed, RC=nn

or

XCOMU0288E System function failed, RC=nn

Was the transfer successful or not?

Environment

Release: XCOM..01300-11.6-XCOM Data Transport-for AIX
Component:

Resolution

A XCOM-Transfer can fail due to many different reasons, from invalid Userid and Password, Network Problems, Allocation problems, Unicode Conversion trouble and so on.

There are a lot of different Error Messages for these events:

 XCOMN0416E Error writing output file: No such file or directory
 XCOMM0900E UNICODE CONVERSION ERROR - RC=nn REASON=rr
 XCOMN0929E Unicode conversion detected malformed characters.
 XCOMN0298E Unable to allocate remote transaction program: Txpi 211: Socket connect error return value = nnnnn
 XCOMN0302E Unable to open local input file: No such file or directory
 XCOMN0410E Error sending feature negotiation record: Txpi 227 

Messages XCOMN0288E/XCOMU0288E are a bit different:

 XCOMN0288E System function failed, RC=nn

 XCOMU0288E System function failed, RC=nn

These messages appear in two cases:

1. If you transfer a file to Windows or Unix and one of the optional commands (Preprocessing - XCOMPRE, Post Processing - XENDCMD, Print Jobs - XLPCMD, User Notification - XNOTIFYCMD, Successful Completion - XPPCMD) does not end successful.

2. If you transfer a Batch file to Windows or Unix and that Batchfile does not successful execute.

In both cases the system() function is used to initiate these Batch Jobs. It returns an error which is docuemnted in the RC at the end of the message.

So the transfer itself went well but the execution caused a problem. In such cases you need to debug the Batch file as the error is outside of XCOM.