CA XCOM Data Transport

Tech Tip: How does CA 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? 

08-28-2017 05:56 AM

Question:

How does CA 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? 

 

Answer:

There are several areas where COMPRESSION can be set in CA 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.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

08-28-2017 10:53 AM

Yohai, I am in process checking this and come back to you with my findings. Thank You for your patience, Gerlinde

08-28-2017 07:30 AM

Geraldine,

In the Admin_Guide of XCOM 12.0 for Z/OS, it says that COMPRESSION_ALLOWED in the CONFIG file only has meaning for TYPE=EXECUTE jobs.  

Indeed, we would be glad if we could specify it for XCOM servers (PGM=XCOMXFER), because compression does slow down the elapsed time for many of our transfers.

We could specify COMPRESS=NO in the individual DEST members, but I suppose that this would have effect only on transfers that are locally initiated.

Regards,

Yohai

Related Entries and Links

No Related Resource entered.