× 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.




All -

We have a multi-LPAR environment, with some on V5R2 and others on V5R4.
We will soon have all LPAR's on V5R4.

We recently received a 1099 update from Oracle for our JDE software, and experienced the following problems. We received both source and compiled objects from Oracle. These programs were compiled on their V5R4 system, specifying V5R2 as the target release.

However, the development system where we are modifying this program is on V5R2.

When attempting to compile one of the SQLRPGLE programs that we received, it fails in the SQL pre-processor with the following errors:
SQL0408 30 2629 Position 17 Value for column or variable WFAN8 not compatible.
SQL0408 30 2629 Position 17 Value for column or variable WFYR not compatible.
SQL0408 30 2636 Position 17 Value for column or variable WFAN8 not compatible.
SQL0408 30 2636 Position 17 Value for column or variable WFYR not compatible.
SQL0408 30 2643 Position 17 Value for column or variable WFAN8 not compatible.SQL0408 30 2643 Position 17 Value for column or variable WFYR not compatible.
These errors are occurring on INSERT statements, and It turns out that the fields WFAN8 and WFYR are numeric fields in the database, but the host variables used in the insert statement are alphameric fields, not numeric.

I recently made the determination (purely by accident) that DB2/400 on V5R4 will automatically attempt to re-cast fields to the proper type. It appears that on the V5R4 system it compiles fine (even when specifiying target release V5R2), since it apparently recasts the alphameric field as numeric on the INSERT.

However, I'm relatively confident that even though this program compiled properly on the V5R4 machine, it would bomb when we tried to run it on the V5R2 box, since DB2/400 can't do the proper recasting on V5R2.

The simple fix is to change the host variables to be numeric, which we did, and it now compiles on the V5R2 box.

However, my thoughts are that IBM should enforce this casting restriction when compiling on the V5R4 box to target release V5R2. Comments?

Regards,
Steve





_________________________________________________________________
Put your friends on the big screen with Windows Vista® + Windows Live™.
http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_012008

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.