The sample IDCAMS statements for the define of the history dataset for CA XCOM Data Transport fro z/OS 12.0 contains an explicit EATTR(NO). XCOM announced support for EAVs in r11.6, so why is this specified?

Products

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

Issue/Introduction

The sample IDCAMS statements for the define of the history dataset contains an explicit EATTR(NO) - why since XCOM announced support for EAVs in r11.6? 

Environment

Release:
Component: XCMVS

Resolution

We added support for extended attributes for datasets that are TRANSFERRED in r11.6.

We did certify extended attributes for the XCOMHIST and XCOMRRDS datasets in 2016, however the samples had already been created.