DBSQLPR gets RC 2020 after upgrading Datacom to 15.0

book

Article ID: 129947

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

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.

Cause

Datacom 15.0 corrected some DBSQLPR errors to file management, so some functions have changed.

Environment

CA Datacom 15.0 and above

Resolution

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.
 

Additional Information

A quick workaround:
If adding any of the following options: 
NOECHO 
NOPAGEHDR 
NOPAGES 
it works fine on 15.0 too.