×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Receiving the following message when embedded SQL statement runs in RPG
(using execute immediate):
MCH0601 - Space offset X'00101400' or X'0000000000000000' is outside
current limit for object FUNDDNRP DMIGPLS C00J75D.
After sending the email , I actually found something on Google that gave me
an idea. As opposed to doing my INSERT INTO, I did a CREATE TABLE AS (sql
statement) WITH DATA. The resulting table had one field that was different
from my destination file. There was one destination field defined as
decimal(11,2) while the source field was defined decimal(9,2). When I
modified the query to manually convert the source field to decimal(11,2),
the query started working.
This has me confused. I could see this being a problem if the source field
was larger than the destination, but it seems that SQL should handle moving
a smaller field into a larger one. I have never seen this problem before
and this program has been running in its current form since (at least)
March 2007. I am confused as to why the issue suddenly popped up this
morning.
Anyone aware of a recent PTF that would likely trigger this problem? Maybe
this should have come up a long time ago and I've just been lucky for
nearly 3 years. Seems hard to imagine..
As an Amazon Associate we earn from qualifying purchases.