Previous Topic: Changing the Key of a Compressed VSAM Data Set

Next Topic: Subsystem Activation and Operation

Concepts and Facilities › Special Considerations › Changing the Record Length of Compressed Data Sets

Changing the Record Length of Compressed Data Sets

If you are using a noncustom algorithm, or if your FDT uses RDL that specifies VER (Variable to End of Record), there is no need to reimplement the data set. However, if the RDL specifies a total noncompressible area greater than the length of the shortest record, compression fails with message SHR015I, unless you use the Transparency User Exit to handle this condition.

If your FDT's RDL expects a minimum record length and you have shorter records in the data set, whether it is VSAM or PS, you need to reimplement the data set as explained in the previous topic. Considerations specific to VSAM do not apply to PS. In particular, Safeguards is not supported for PS data sets, and they do not have data components, paths, or keys.