Demetrius,
you are fine... the RL_COMPRESSION should be set to YES, while the 3590s
are doing their own compression.
The RL_COMPRESSION is more likely a SAP "software" compression, therefore
is improving yr overall compression packaging.
You will be surprise of the reduction rate after you set the RL_COMPRESSION
to yes, of-course also depends of the database that you use for SAP
(Oracle, Informix, etc...), and how empty (null and zeros) are your tables
and dbspaces.

Cheers.

Othonas


"Malbrough, Demetrius" <d_malbrough AT TI DOT COM>@VM.MARIST.EDU> on 02/13/2001
12:54:05 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  TDP for SAP R/3 compression vs. TAPE DRIVE compression



Good Afternoon, *SMers & SAPsters!

I wanted to see if I could pick your brains for a second!

What happens if you are performing null block compression before sending
the
data over the network to the TSM server (RL_COMPRESSION YES in the SAP R/3
profile) and also using Tape Drive compression (3494 ATL w/ 3590 drives on
Solaris FORMAT=3590C via device=/dev/rmt/#stc)?  Will the data grow due to
being compressed twice or compression on the SAP R/3 side is so simple it
does not affect Tape Drive compression?

Thanks,

Demetrius A. Malbrough
ADSM/TSM Consultant
Texas Instruments
6550 Chase Oaks Blvd.
Plano, TX 75023

(972) 927-9869 Office
(214) 314-3350 Pager
d_malbrough AT ti DOT com