What are the pros and cons for using Strong Compression versus Custom Compression with CA Datacom Presspack?

Products

• Datacom
• DATACOM - AD
• Ideal
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description:

When using CA Datacom Presspack, here are a some pros and cons for using Strong Compression versus Custom Compression.

Solution:

Strong Compression versus Custom Compression:

• Strong compression is simple to use and does not require keeping the custom compression modules
  
  
  • Pro: Easier to manage, easier to recover.
  • Con: Someone else with the CXX definition and Presspack could decompress the data (if they had a mainframe with CA Datacom Presspack - not your typical hacker).
  
  
  
• Custom compression requires extra steps to create custom modules but provides better compression value.
  
  
  • Pro: Better value is achieved, better protection because only a person with the Custom DCT (module) and CXX etc. would be able to decompress.
  • Con: If you lose the DCT you cannot recover the data from the compressed file.

Environment

Release: DATABB00200-14-Datacom/AD
Component: