Unfortunately TDUDATA cannot be specified as a destination/config member parameter, but there are other destination/config member parameters that can be used to set the CA XCOM for Windows parameter REMOVE_TRAIL_BLANKS from the XCOMPRE.bat user exit.
One way would be to have two destination/config PSO members that point to the same target destination, you can direct which SPOOL file goes to which XCOM destination.
For example: Make a copy of your current CA XCOM for z/OS PSO destination/config member. Edit the member and add the CA XCOM for z/OS destination/config parameter PSOPREF=XCRTBYES. This will override the PSOPREF value specified in the CA XCOM for z/OS DEFAULT table:
Specifies the high-level qualifier that is used by the PSO interface when allocating temporary data sets. This value is also used by PDSE program library transfers when creating temporary data sets.
* PSO DEST FOR Windows XCRTBYES
By the user directing the SPOOL files that require special processing to this CA XCOM for z/OS PSO destination XCRTBYES it allows for the ability to define a unique/specific prefixed remote filename:
remote_file: " XCRTBYES.xxxxxxxx.xxxxxxxx.xxxxxxxx"
which can be used by the CA XCOM for Windows XCOMPRE exit to set the REMOVE_TRAIL_BLANKS=YES for this particular transfer:
if /%use_echo%/ == /YES/ echo XCOMPRE_REMOTE
rem The following two if statements are case-sensitive. To make them not case-sensitive
rem a "/I" must follow the word "if" as if /I /%file%/ == ......
if NOT /%xcrmtfname%/ == /"XCRTBYES"/ GOTO XCOMPRE_END
%xcomqm% -p%local_reqno% REMOVE_TRAILING_BLANKS =YES
Please be aware that the above XCOMPRE code is a sample. The user will be responsible for making the necessary changes or updating the script for their site specifications and/or maintenance.