Idea Details


Last activity 03-25-2019 08:20 AM
Earle Shulman's profile image
10-10-2017 04:08 PM

We receive many DATA EXCEPTION messages when running SQL queries against IDMS network database records.

IDMS provides no information as to where the data exception occurred.

It is a very labor and time consuming process to figure out where the problem is, especially in a query with multiple records and when the records are very large.


It would be very helpful if there was some way for the system to display the record and field which provoked the data exception.


03-25-2019 08:20 AM

Hi Earle - thank you for your idea.


This has been reviewed and researched by the product team and has moved to the "currently planned" stage.  Please note that ideas can be moved from any stage to the "not planned" stage at Broadcom's discretion based on product direction, feasibility analysis or other factors. 


Thank you for your idea - we appreciate your input and helping us shape the future of CA IDMS! 

11-26-2018 09:35 AM

I'm not sure how much that helps. When you get a data exception in OCF, you just get the message with no indication of how far the query got:


*+ Status = -4 SQLSTATE = 22005 Messages follow:
*+ DB001025 T57 C-4M322: Data exception


It would only help if you were running this through Server with the "Invalid Decimal Option" set to display a certain value, in which case the other columns in that row would tell you as much as the ROWID would have anyway.

11-26-2018 09:21 AM

You can add the ROWID pseudo column to the result set for any query to get the DBKEY (which includes PAGE-INFO for IDMS 19.0).  Note that ROWID is automatically added to SELECT * when the Virtual Key feature is enabled.

11-05-2018 03:16 PM

Thank you for submitting this idea. The product team has taken this idea in for review and further research.  Community members, if you agree that this is a good idea please feel free to vote. Also please provide additional input using the comments section.  Thank you!

10-20-2017 05:56 AM

Nice idea!

At our site we also want to make use of SQL queries against our IDMS Network databases .

When using OLQ you get an asterisk ('*') for instance when a numeric element contains a non-numeric value.  Your SQL query will throw a data exception but it would be very helpful if you could also see the dbkey/rowid.
Kind regards, Johan.