Pervasive Encryption for V2R2 Compatibility Matrix

Use this grid to identify which Broadcom product release support Pervasive Encryption with IBM releases. If maintenance is required:

• A PTFs section link is provided.
• Use FIXCAT HOLDDATA to identify maintenance that is required to support a hardware device, software, or function.
• If found, select the additional information link that appears under the compatibility status.

Launch Mainframe Compatibility Main Page

The following grid contains a list of all Broadcom mainframe products and releases. The column values include:

Product List

Additional Information

• No information found.

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Allocate supports PE as is out of the box with no required product    
   changes. However to provide customers additional flexibility within      
   CA Allocate, PTF SO04404 adds three new CA Allocate system variables     
   to provide additional flexibility z14 does not provide.                  
      

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Allocate supports PE as is out of the box with no required product    
   changes. However to provide customers additional flexibility within      
   CA Allocate, PTF SO04404 adds three new CA Allocate system variables     
   to provide additional flexibility z14 does not provide.                  
      

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Allocate supports PE as is out of the box with no required product    
   changes. However to provide customers additional flexibility within      
   CA Allocate, PTF SO04404 adds three new CA Allocate system variables     
   to provide additional flexibility z14 does not provide.                  
      

• CA 1 Flexible Storage 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• CA 1 Flexible Storage 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• CA 1 Flexible Storage 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   See documentation for datasets that can be considered.                   
      

• CA 1 Tape Management 12.6

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                   
      

• CA 1 Tape Management 12.6

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• CA 1 Tape Management 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• CA 1 Tape Management 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• CA 1 Tape Management 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   See documentation for datasets that can be considered.                   
      

• CA 11 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• CA 11 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• CA 7 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• CA 7 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• CA 7 12.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• CA 7 12.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• COBOL/XE 3.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   VSAM files must be defined as Extended-Format data sets and not as       
   Extended Addressability data sets.                                       
      

• COBOL/XE 3.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   VSAM files must be defined as Extended-Format data sets and not as       
   Extended Addressability data sets.                                       
      

• Database Management Solutions for IMS for z/OS 20.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Please see more information at https://docops.ca.com/ca-database-managem 
   ent-solutions-for-ims-for-z-os/20-0/en/getting-started/pervasive-encrypt 
   ion                                                                      
      

• DATACOM CICS SERVICES 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
                                                                           00000800 
      

• DATACOM CICS SERVICES 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
  
      

• DATACOM CICS SERVICES 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• Datacom DB Core 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   (to be provided shortly)                                                00000100 
      

• Datacom DB Core 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (V14.0, V15.0, V15.1) supports PE as is out of the box for    
   external created user data files such as DBUTLTY BACKUPs and EXTRACTS.   
   For user data stored within the databases we recommend using the         
   built-in Datacom encryption capabilities which exploit the available     
   Crypto co-processors. For complete implementation recommendations        
   see CA Datacom documentation or contact the CA Datacom support team.     
      

• Datacom DB Core 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM DL1 TRANSPARENCY 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM DL1 TRANSPARENCY 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM SERVER 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• DATACOM SERVER 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM SERVER 15.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM SERVER 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the      00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see Datacom documentation or contact the Datacom support       00000600 
   team.                                                                   00000700 
                                                                           00000800 
      

• DATACOM SERVER 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the      00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see Datacom documentation or contact the Datacom support       00000600 
   team.                                                                   00000700 
                                                                           00000800 
      

• DATACOM SERVER 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the      00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see Datacom documentation or contact the Datacom support       00000600 
   team.                                                                   00000700 
      

• DATACOM STAR 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• DATACOM STAR 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM STAR 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM VSAM TRANSPARENCY 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• DATACOM VSAM TRANSPARENCY 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• DATACOM VSAM TRANSPARENCY 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• Datacom/AD 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• Datacom/AD 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• Datacom/AD 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• Disk Backup and Restore 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   Day one support using the USEDSSIO data mover.                           
      

• Disk Backup and Restore 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Day one support using the USEDSSIO data mover.                           
      

• Disk Backup and Restore 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Day one support using the USEDSSIO data mover.                           
      

• ESP Workload Automation 11.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Most of operational ESP data sets could be encrypted without changing    
   ESP configuration. The only exception is the following ESP operational   
   data sets and related utilities:                                         
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   ESP uses EXCP access method for them, and EXCP cannot be used for        
   encrypted data sets. Therefore those data sets should not be             
   encrypted.                                                               
      

• ESP Workload Automation 11.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Most of operational ESP data sets could be encrypted without changing    
   ESP configuration. The only exception is the following ESP operational   
   data sets and related utilities:                                         
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   ESP uses EXCP access method for them, and EXCP cannot be used for        
   encrypted data sets. Therefore those data sets should not be             
   encrypted.                                                               
      

• ESP Workload Automation 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Most of operational ESP data sets could be encrypted without changing    
   ESP configuration. The only exception is the following ESP operational   
   data sets and related utilities:                                         
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   ESP uses EXCP access method for them, and EXCP cannot be used for        
   encrypted data sets. Therefore those data sets should not be             
   encrypted.                                                               
      

• ESP Workload Automation 12.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Most of operational ESP data sets could be encrypted without changing    
   ESP configuration. The only exception is the following ESP operational   
   data sets and related utilities:                                         
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   ESP uses EXCP access method for them, and EXCP cannot be used for        
   encrypted data sets. Therefore those data sets should not be             
   encrypted.                                                               
      

• Gen 8.6

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R5

   The majority of Gen data sets are PDSEs, PDS, or temporary data sets.    
   Only PDSEs are supported for Pervasive Encryption along with data sets   
   created for Db2 Databases.                                               
  
   Gen has been certified with Pervasive Encryption for PDSEs and Db2       
   v12 datasets with no required product changes.                           
      

• Gen 8.6

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   The majority of Gen data sets are PDSEs, PDS, or temporary data sets.    
   Only PDSEs are supported for Pervasive Encryption along with data sets   
   created for Db2 Databases.                                               
  
   Gen has been certified with Pervasive Encryption for PDSEs and Db2       
   v12 datasets with no required product changes.                           
      

• IDEAL 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• IDEAL 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• IDEAL 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• IDMS/DB 18.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IDMS/DB 18.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IDMS/DB 18.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IDMS/DB 19.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IDMS/DB 19.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IDMS/DB 19.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA IDMS supports PE out of the box, for database and disk journal        
   files, when VSAM is used as an access method.  PE is supported for       
   non-Database sequential work files, backups, and data extracts, when     
   defined to PE requirements.  See IBM documentation for PE requirements.  
   For implementation recommendations, see CA IDMS documentation            
   or contact the CA IDMS support team.                                     
      

• IPC 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• IPC 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• IPC 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the   00000100 
   box for externally created user data files such as DBUTLTY BACKUPs and  00000200 
   EXTRACTs.  For user data stored within the databases, we recommend      00000300 
   using the built-in Datacom encryption capabilities which exploit the    00000400 
   available crypto co-processors.  For complete implementation recommen-  00000500 
   dations, see CA Datacom documentation or contact the CA Datacom support 00000600 
   team.                                                                   00000700 
      

• IPC 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• IPC 15.1

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA Datacom (Versions 14.0, 15.0, 15.1) supports PE, as is, out of the    
   box for externally created user data files such as DBUTLTY BACKUPs and   
   EXTRACTs.  For user data stored within the databases, we recommend       
   using the built-in Datacom encryption capabilities which exploit the     
   available crypto co-processors.  For complete implementation recommen-   
   dations, see CA Datacom documentation or contact the CA Datacom support  
   team.                                                                    
      

• JOBTRAC 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• JOBTRAC 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• SCHEDULER MVS 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• SCHEDULER MVS 11.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• Spool 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   The CA Spool ESFSPTP backup/restore utility supports PE with no          
   required product changes.                                                
  
   CA Spool supports ICSF-based encryption of spool data-at-rest            
   using IBM ICSF services for encryption/decryption.                       
  
   No CA Spool changes are necessary for JES2 sysout encryption support.    
   All changes required are done in ICSF and the external security package. 
      

• Spool 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   The CA Spool ESFSPTP backup/restore utility supports PE with no          
   required product changes.                                                
  
   CA Spool uses EXCP to access checkpoint and spool datasets, which is     
   not supported by Pervasive Encryption.                                   
  
   CA Spool support for ICSF-based encryption of spool data-at-rest         
   using IBM ICSF services for encryption/decryption has been               
   available since release 11.6.                                            
      

• Spool 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   The CA Spool ESFSPTP backup/restore utility supports PE with no          
   required product changes.                                                
  
   CA Spool uses EXCP to access checkpoint and spool datasets, which is     
   not supported by Pervasive Encryption.                                   
  
   CA Spool support for ICSF-based encryption of spool data-at-rest         
   using IBM ICSF services for encryption/decryption has been               
   available since release 11.6.                                            
  
      

• TLMS Tape Management 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

   See documentation for datasets that can be considered.                  00000100 
      

• TLMS Tape Management 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   See documentation for datasets that can be considered.                   
      

• TPX for z/OS 5.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   CA TPX 5.4 does work with Pervasive Encryption in TPX single instance    
   environment and TPX Generic Resource environment, successfully.          
   Limited testing has been done with CA L-SERV as Single System            
   successfully.                                                            
   TPX Affinity has not been tested.                                        
  
   We are in the process of creating a PTF to have new JCL samples related  
   to definig and initializing CA TPX Pervasice Encrypted VSAM Files; and   
   migration existing CA TPX VSAM FILES to new Pervasice Encrypted VSAM     
   Files. This PTF is expected in mid 2020.                                 
      

• TPX for z/OS 5.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   CA TPX 5.4 does work with Pervasive Encryption in TPX single instance    
   environment and TPX Generic Resource environment, successfully.          
   Limited testing has been done with CA L-SERV as Single System            
   successfully.                                                            
   TPX Affinity has not been tested.                                        
  
   We are in the process of creating a PTF to have new JCL samples related  
   to definig and initializing CA TPX Pervasice Encrypted VSAM Files; and   
   migration existing CA TPX VSAM FILES to new Pervasice Encrypted VSAM     
   Files.                                                                   
      

• UFO 3.2

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   VSAM files must be defined as Extended-Format data sets and not as       
   Extended Addressability data sets.                                       
      

• UFO 3.2

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   VSAM files must be defined as Extended-Format data sets and not as       
   Extended Addressability data sets.                                       
      

• Verify for CICS and Verify for VTAM 9.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Tests can be run on encrypted files, but the test stream file itself can 
   not be encrypted.                                                        
      

• Verify for CICS and Verify for VTAM 9.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Tests can be run on encrypted files, but the test stream file itself can 
   not be encrypted.                                                        
      

• VISION:RESULTS INTERFACE TO IDMS DB FULL-FUNCTION 4.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   IDMS VSAM data bases must be defined as Extended-Format data sets and    
   not as Extended Addressability data sets.                                
      

• VISION:RESULTS INTERFACE TO IDMS DB FULL-FUNCTION 4.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   IDMS VSAM data bases must be defined as Extended-Format data sets and    
   not as Extended Addressability data sets.                                
      

• VISION:RESULTS INTERFACE TO IDMS DB READ-ONLY 4.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   IDMS VSAM data bases must be defined as Extended-Format data sets and    
   not as Extended Addressability data sets.                                
      

• VISION:RESULTS INTERFACE TO IDMS DB READ-ONLY 4.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   IDMS VSAM data bases must be defined as Extended-Format data sets and    
   not as Extended Addressability data sets.                                
      

• Workload Automation Agent for z/OS 11.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

   Most of operational data sets used by CA Workload Automation Agent for   
   z/OS could be encrypted without changing Agent configuration. The only   
   exception is the following operational data sets and related utilities:  
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   CA Workload Automation Agent for z/OS uses EXCP access method for them,  
   and EXCP cannot be used for encrypted data sets. Therefore those data    
   sets should not be encrypted.                                            
      

• Workload Automation Agent for z/OS 11.4

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

   Most of operational data sets used by CA Workload Automation Agent for   
   z/OS could be encrypted without changing Agent configuration. The only   
   exception is the following operational data sets and related utilities:  
     APPLFILE                                                               
     CKPT                                                                   
     EXH                                                                    
     NETQUEUE                                                               
     QUEUE                                                                  
     TRAKFILE                                                               
  
   CA Workload Automation Agent for z/OS uses EXCP access method for them,  
   and EXCP cannot be used for encrypted data sets. Therefore those data    
   sets should not be encrypted.                                            
      

Required PTF(s)

• ACF2 for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  ACF2 for z/OS (CAX1G00)

  • SO14631

• ACF2 for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  ACF2 for z/OS (CAX1G00)

  • RO96906 SO06603 SO06605 SO06670 SO07057

• ACF2 for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

  ACF2 for z/OS (CAX1G00)

  • RO96906 SO06603 SO06605 SO06670 SO07057

• SMF Director 12.7

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  SMF Director (CASFC70)

  • SO04739

• SMF Director 12.7

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  SMF Director (CASFC70)

  • SO04739

• SMF Director 12.7

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

  SMF Director (CASFC70)

  • SO04739

• OPS/MVS 14.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  OPS/MVS (CCLXE00)

  • SO15502

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  Allocate DASD Space and Placement (CCTVC50)

  • SO04404

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  Allocate DASD Space and Placement (CCTVC50)

  • SO04404

• Allocate DASD Space and Placement 12.5

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

  Allocate DASD Space and Placement (CCTVC50)

  • SO04404

• Database Management Solutions for Db2 for z/OS 20.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  Endevor Interface for Db2 for z/OS (CAHOK00)

  • SO07804

  Chorus DBA Services (CEU9K00)

  • SO04453 SO07805

  SYSVIEW Performance Management Option for Db2 for z/OS (CIDBK00)

  • SO04454 SO05010 SO07806

  Db2 Common Components (CINSK00)

  • SO04455 SO05011 SO07807 SO08313 SO08406 SO10389

  Object Framework Services for Db2 (COFSK00)

  • SO04456 SO07808

  Database Analyzer for Db2 for z/OS (CPDAK00)

  • SO04457 SO07809

  Detector for Db2 for z/OS (CPDTK00)

  • SO04458 SO07810

  Fast Load for Db2 for z/OS (CPFLK00)

  • SO04459 SO05012 SO07811 SO08407

  Fast Unload for Db2 for z/OS (CPFUK00)

  • SO04460 SO05013 SO07812

  Log Analyzer for Db2 for z/OS (CPLAK00)

  • SO04461 SO05014 SO07813

  Plan Analyzer for Db2 for z/OS (CPPAK00)

  • SO04462 SO07814

  Recovery Analyzer for Db2 for z/OS (CPRAK00)

  • SO04463

  Compile/PRF (CPRFK00)

  • SO04464 SO07815

  Report Facility for Db2 for z/OS (CPRFK01)

  • SO04465 SO07816

  Report Facility for Db2 for z/OS (CPRFK02)

  • SO04466 SO07817

  Rapid Reorg for Db2 for z/OS (CPRRK00)

  • SO04467 SO05015 SO07818

  Subsystem Analyzer for Db2 for z/OS (CPSAK00)

  • SO04468 SO07819

  Utilities Common (CPUTK00)

  • SO04469 SO05016 SO07820

  RC/Migrator for Db2 for z/OS (CRCMK00)

  • SO04470 SO07821

  RC/Query for Db2 for z/OS (CRCQK00)

  • SO04471 SO07822

  RC/Secure for Db2 for z/OS (CRCSK00)

  • SO07823

  RC/Update for Db2 for z/OS (CRCUK00)

  • SO04472 SO07824

  RC/Extract for Db2 for z/OS (CRCXK00)

  • SO04473

  Snapshot General Services (CTGRK00)

  • SO04474 SO05017 SO07825

  Utility General Recovery (CUGRK00)

  • SO04475 SO05018 SO07826

• Database Management Solutions for Db2 for z/OS 20.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

  Endevor Interface for Db2 for z/OS (CAHOK00)

  • SO07804

  Chorus DBA Services (CEU9K00)

  • SO04453 SO07805

  SYSVIEW Performance Management Option for Db2 for z/OS (CIDBK00)

  • SO04454 SO05010 SO07806

  Db2 Common Components (CINSK00)

  • SO04455 SO05011 SO07807 SO08313 SO08406 SO10389

  Object Framework Services for Db2 (COFSK00)

  • SO04456 SO07808

  Database Analyzer for Db2 for z/OS (CPDAK00)

  • SO04457 SO07809

  Detector for Db2 for z/OS (CPDTK00)

  • SO04458 SO07810

  Fast Load for Db2 for z/OS (CPFLK00)

  • SO04459 SO05012 SO07811 SO08407

  Fast Unload for Db2 for z/OS (CPFUK00)

  • SO04460 SO05013 SO07812

  Log Analyzer for Db2 for z/OS (CPLAK00)

  • SO04461 SO05014 SO07813

  Plan Analyzer for Db2 for z/OS (CPPAK00)

  • SO04462 SO07814

  Recovery Analyzer for Db2 for z/OS (CPRAK00)

  • SO04463

  Compile/PRF (CPRFK00)

  • SO04464 SO07815

  Report Facility for Db2 for z/OS (CPRFK01)

  • SO04465 SO07816

  Report Facility for Db2 for z/OS (CPRFK02)

  • SO04466 SO07817

  Rapid Reorg for Db2 for z/OS (CPRRK00)

  • SO04467 SO05015 SO07818

  Subsystem Analyzer for Db2 for z/OS (CPSAK00)

  • SO04468 SO07819

  Utilities Common (CPUTK00)

  • SO04469 SO05016 SO07820

  RC/Migrator for Db2 for z/OS (CRCMK00)

  • SO04470 SO07821

  RC/Query for Db2 for z/OS (CRCQK00)

  • SO04471 SO07822

  RC/Secure for Db2 for z/OS (CRCSK00)

  • SO07823

  RC/Update for Db2 for z/OS (CRCUK00)

  • SO04472 SO07824

  RC/Extract for Db2 for z/OS (CRCXK00)

  • SO04473

  Snapshot General Services (CTGRK00)

  • SO04474 SO05017 SO07825

  Utility General Recovery (CUGRK00)

  • SO04475 SO05018 SO07826

• Database Management Solutions for IMS for z/OS 20.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  Change Accumulation for IMS (CCHAK00)

  • SO03976

  Database Analyzer for IMS (CIDAK00)

  • SO03977

  Database Organizer for IMS (CIDOK00)

  • SO03978

• Database Management Solutions for IMS for z/OS 20.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  Common Component for IMS (CITKK00)

  • SO03979

• SYSVIEW Performance Management 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  SYSVIEW Performance Management (CNM4G00)

  • SO13927

• NetMaster Network Management Suite 12.2

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  NetMaster Network Management (CC2D810)

  • SO15966

  NetMaster Management Services (CC2D811)

  • SO15967

  SOLVE:FTS (CDEMC20)

  • SO15968

• SOLVE:Operations Automation 11.9

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  Unicenter NetMaster Management Services (CC2D710)

  • SO15946

• Top Secret for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R4

  Top Secret for z/OS (CAKOG00)

  • LU01372 RO97892 SO07542 SO13895 SO14000 SO15905

• Top Secret for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R3

  Top Secret for z/OS (CAKOG00)

  • RO97892 SO07542

• Top Secret for z/OS 16.0

  Fix Category: CA.Function.Pervasive.Encryption.z/OS.V2R2

  Top Secret for z/OS (CAKOG00)

  • RO97892