DB Return code 22 and DQ025 error during DRAW


Article ID: 7488


Updated On:


CA Datacom CA DATACOM - AD 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


Getting DB Return Code: 22 

Ran a data query and got DQ025E during DRAW command.

Base that was used before it was obsoleted and a new on in place is still the same, but the contents are different still the same base 592.

CXX dictionary is showing record length - old table was much shorter.


This is normally a problem because a URT does not have SYNONYM specified. 

A DBOC INQ=???.xxx.??? confirmed this. 



z/os, CA Datacom/DB 15.1


From similar symptom:

" did a DBOC INQ=???.nnn.??? and discovered 2 urts with this table but SYNONYM NOT included, DQ was getting the wrong URT, she will code in SYNONYM in URT "


Customer bypass:

"Did a DBOC INQ to confirm the table does exist in other table. When we closed the other table DQRY ran fine."


Additional Information



The element was not found for one of the following reasons:

â–  The element name specified in the Element List was not defined through DB-ELM-NAME in the CA Datacom Datadictionary element entity-occurrence.

â–  The end of the Element List was not indicated with the required five blanks.

â–  The Element List contained more names than the maximum specified in the MUF startup option. (Examine this possibility first if using the Accounting Facility which generates an element for each field specified.)


Determine the cause of the problem and implement the corresponding recovery procedure as follows:

â–  If the element was not defined, add the element entity-occurrence to CA Datacom Datadictionary and post it to the Directory.

â–  If the Element List format did not include five blanks as the end-of-list indicator, correct the format.

â–  If the Element List was too long, either reduce the size of the list or increase the maximum number of elements that can be accessed per request. To accommodate the requirements of this request, revise the MUF startup option MAXELRQ.