We are going to z/os 1.13 soon and want to set the DEVSUP parm non_vsam_xtiot=yes. Will there be any impact on your product?

Products

• Datacom
• DATACOM - AD
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services

Issue/Introduction

 

Will setting NON_VSAM_XTIOT=YES in DEVSUPxx cause any compatibility concerns with CA Common Services?

 

Resolution

 

If running ENF at release 12.0 or higher and utilizing the Datacom/AD database (i.e running ENFIMUF or ENFXMUF) then you should be aware of the following Datacom fixes. The symptoms would be a S0C4 abend in IBM module IGCT002D thus resulting in ENF terminating with a U0203 abend. The problems are not in ENF code itself, so the fixes are not ENF fixes.

Recommended Datacom/AD fixes:

RO41721 - Datacom r12.0 - FMID: CBDC000
RO41830 - Datacom r12.0 - FMID: CBDC000

Following are fixes for other CA Product fixes related to NON_VSAM_XTIOT=YES. These solutions have No tie-in to CA Common Services. Continue to check the z/OS Compatibilities for your specific CA Product for current information by visiting the Compatibilities link for Mainframe Environments on the CA Support Online site.

RO22249 - CA OSI Common Component r12.0 - FMID: CAG8C00
RO25822 - CA IDMS r17.0 - FMID: CGJH000
RO33996 - CA IDMS r17.0 - FMID: CGJH000
RO37156 - CA PDSMAN r7.6 - FMID: CPM7600
RO36320 - CA PDSMAN r7.7 - FMID: CPDS770