Transfer being compressed without COMPRESS being specified with XCOM for z/OS

Products

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

Issue/Introduction

How does XCOM Data Transport for z/OS use the compression parameter for a TYPE=SCHEDULE transfer to a z/OS box from a z/OS box? 

Environment

XCOM™ Data Transport® for z/OS

Resolution

There are several areas where COMPRESSION can be set in XCOM Data Transport for z/OS:

• The default for the SYSIN01 COMPRESS= parameter is NO.
• The default for a DEST member's COMPRESS= parameter is YES. 

Additional Information

If the transfers are using DEST members like XCOM1 and XCOM2 as such, it correctly use COMPRESS=YES in the absence of a different COMPRESS setting in either the DEST member or the SYSIN01.

Even a TYPE=SCHEDULE transfer to a specific LU will use a DEST member, IF the LU name is defined in a DEST member that is ENABLED in the XCOM server at the time the transfer runs.

If the transfer was submitted to an LU for which there was an enabled DEST member (XCOM1 and XCOM2). This would have caused COMPRESS=YES to be used - UNLESS COMPRESS=NO was specified in that particular DEST member being used.

In NO case will COMPRESS_ALLOWED be overridden by a COMPRESS parameter or default.

So, if you wish to completely disable or limit compression use, COMPRESS_ALLOWED will overrule any COMPRESS parameter setting that is used. The default setting for COMPRESS_ALLOWED is ALL. If you want to completely prevent compression from being used, you can also do so via the COMPRESS_ALLOWED parameter in the CONFIG member.