Migration R19 to R20 : RECORD SIZE different in UNLOAD DEDB
Article ID: 131387
CA Database Analyzer (IMS Tools)CA Mainframe Configuration Manager for IMS for z/OSIMS TOOLS - MISCCA Compress Data Compression (IMS Tools)CA Database Analyzer for IMS for z/OSCA Database Copier for IMS for z/OSCA Database Organizer for IMS for z/OSCA Mainframe Extended Terminal Manager (IMS Tools)CA High Performance Recovery for IMS for z/OSCA Database Organizer (IMS Tools)CA Mainframe Program Restart Manager for IMS for z/OSCA Secondary Index Builder for IMS for z/OSCA Secondary Index for IMS for z/OS
We updated CA TOOLS IMS (DBA - DBO - SIB) from R19 to R20. But for 2 jobs, in which there are UNLOAD for 2 bases DEDB, the DFSURG0 files have DIFFERENT RECORD SIZE between R19 and R20. Could it be possible to modify this parameter in the jobs, with DBO Control Statements?
Release: Component: DBO
Some years ago, we fixed a bug where “CA Database Organizer for IMS for z/OS (DBO) may interpret LRECL value incorrectly when a value was specified in the JCL to override the LRECL value for the DBOUNLD1/DFSURGU1 unload data set.”
Basically, the LRECL is now respected, as in the past, it was incorrectly interpreted as “LRECL + 4 bytes”.
So there are two options:
Changing the JCLs to specify the LRECL exactly as they want it to be. It may be many JCLs and I don’t expect they’ll be willing to do it.
Reinstate the old behavior (LRECL + 4) by usage of Environment Specific Product Customization - ITKOPTN, option LRECLEXT=Y. LRECLEXT=Y: Overridden LRECL value for the DBOUNLD1 unload data set will be increased by 4 bytes.