XCOMN3652E loading .cnf file into XCOM GUI - TAPEDISP parameter

Products

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

Issue/Introduction

After an upgrade from XCOM for Windows r11 to 12.0 the error "XCOMN3652E Error in reading the configuration file" occurred when trying to load an existing r11 transfer configuration file (.cnf) into the XCOM GUI (StandaloneUI.bat). The target of the transfer is z/OS.
The error was resolved by commenting out the parameter "TAPEDISP=2".
What is the significance of this parameter as it does not seem to be documented anywhere under XCOM for Windows or z/OS?

Resolution

The TAPEDISP parameter is not documented under XCOM for Windows, z/OS, UNIX/Linux or AS/400 documentation, but is still referenced in the legacy documentation Non Stop 11.0 Product Guide. i.e. TAPEDISP "Specifies the disposition value for MVS tape data sets. (1 = New, 2 = Old, 3 = Mod)".

XCOM Engineering has confirmed that TAPEDISP is not actually used on any platform.
Therefore removing or commenting out the TAPEDISP parameter from the .cnf file before loading into the XCOM GUI is the correct approach.

Additional Information

As the only documentation that refers to TAPEDISP is legacy,  it will not be updated to remove that parameter.