ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
DBSQLPR gets RC 2020 after upgrading Datacom to 15.0
Article ID: 129947
DatacomDATACOM - ADCISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesCA ECOMETER SERVER COMPONENT FOCEASYTRIEVE REPORT GENERATOR FOR COMMON SERVICESINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertware
An SQL query is executed via DBSQLPR and the selected rows are saved on an z/OS dataset with LRECL 80 (allocated to STDOUT dataset). The job ran fine when running Datacom 14.0 but after the upgrade to 15.0, it gets RC 2020.
Datacom 15.0 corrected some DBSQLPR errors to file management, so some functions have changed.
CA Datacom 15.0 and above
The problem occurs when the STDOUT dataset has a LRECL=121 or less. If so, a PRTWIDTH option must be specified for DBSQLPR. The value of this option must match the LRECL of the STDOUT dataset. SQL 15.0 APAR ST07726 (or SQL 15.1 ST07727) must be applied too.
A quick workaround: If adding any of the following options: NOECHO NOPAGEHDR NOPAGES it works fine on 15.0 too.