CA XCOM errors XCOMU0438E or XCOMN0438E Record length greater than maxreclen
search cancel

CA XCOM errors XCOMU0438E or XCOMN0438E Record length greater than maxreclen

book

Article ID: 25662

calendar_today

Updated On:

Products

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

Issue/Introduction



How does the MAXRECLEN (maximum record length) parameter function when sending different types of files and when sending to the mainframe? This parameter is displayed as Max. Record length in GUI. In the .cnf file it is the MAXRECLEN= parameter.

Environment

Release: CA XCOM Data Transport for Windows, UNIX and Linux.
Component: XCUHP9

Resolution

When CA XCOM sends a text file, the MAXRECLEN parameter specifies the maximum number of bytes allowed in a record. If CA XCOM encounters a record longer than this during the transfer, it terminates the transfer with the error message:

XCOMU0438E or XCOMN0438E Record length greater than maxreclen, but truncation not allowed

However, if the parameter TRUNCATE=YES has also been specified, CA XCOM does not terminate the transfer, but discards the extra bytes and continues the transfer.


When CA XCOM sends a binary file, this value indicates the length of the records that are transferred. Therefore, for binary transfers sent to the mainframe, the MAXRECLEN parameter should match the LRECL size on the mainframe side. When receiving a binary file, MAXRECLEN is automatically set to whatever the LRECL value is on the partner side.


For RECEIVE transfers between Windows and UNIX or Linux systems, the Max. Record Length value specified by the initiating system is sent to the remote system, which uses this value to set its Max. Record Length value.