This document explains what XCOMM0104E INVALID DATA RECEIVED - EXPECTING MEMBER NAME, means and how to resolve it.
With REPCR=YES in the XCOMDFLT table or config member, this message may occur. With REPCR=NO, this message goes away.
The addition of the REPCR parameter was a r11 SP01 enhancement allowing you to specify whether CA XCOM Data Transport should attempt to CREATE the dataset instead of failing the transfer when the dataset did not exist and REPLACE or ADD was specified for the transfer.
Previously, when sending a file to CA XCOM for z/OS and specifying FILEOPT=REPLACE or FILEOPT=ADD and the dataset did not exist, the transfer failed with XCOMM0669E DATASET NOT FOUND IN CATALOG. The new parameter REPCR specifies whether CA XCOM Data Transport should attempt to CREATE the dataset instead of failing the transfer. When set to NO, CA XCOM will work as before. When set to YES, CA XCOM will attempt to create the dataset. The REPCR default parameter can be specified in the XCOMDFLT table or config member or specified as an XCOMJOB or XCOMXFER EXEC parameter.
If you want to use REPCR=YES, you will need to specify the parameters needed to create the file on z/OS IN CASE the file does not exist. This is needed only if you are doing a RECEIVE from a non-z/OS partner like Windows or Unix, because they do not have DCB information on their system. If you are receiving from another z/OS partner, CA XCOM will use the DCB info of the originating file if it isn't specified in the SYSIN01 parameters.
In other words, to use the REPCR=YES with REPLACE, you will need to specify the required SPACE and DCB info as if you are doing a CREATE. This is due to the fact that the REPLACE will get changed to a CREATE if the target file does not exist.
Specify DCB and SPACE parameters for REPLACE transfers if REPCR=YES is set in the XCOMDFLT table in case the target file does not exist and it gets changed to a CREATE. This is required only if the file is being RECEIVED from a non-MVS partner.