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?
Article ID: 12362
XCOM Data TransportXCOM Data Transport - WindowsXCOM Data Transport - Linux PCXCOM Data Transport - z/OS
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?
Release: Component: XCMVS
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.