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



Infor put an alert on their site at
https://community.infor.com/lx/f/lx-discussions/26991/after-bringing-ibm-i-os-7-4-ptfs-current-sfc500-shop-order-maintenance-and-pro150-list-price-book-maintenance-displayed-no-records/72169

I think I saw a thread on this list about this issue or a similar one.

Basically if you put on a certain DB2 fix pack on 7.4 or 7.3 certain errors may start occurring.

The Memo To Users at R730 and R740 were updated to include the new behavior. As shown below:
</snip>
Queries that compare a numeric value with blanks or an empty string will
fail with SQLSTATE/SQLCODE ‘22023’/-302 or '53045'/-678
Previous to PTF SI76030 on IBM i 7.4 and PTF SI76035 on IBM i 7.3, a query that included an invalid
comparison between a numeric value and blank(s) or a numeric value and an empty string would not
result in an SQL failure.
Blank characters and empty strings are both incompatible with numeric values. Any such queries will now
fail with SQLSTATE: '22023'/-302 or '53045'/-678.
</snip>

Infor published an environment variable which came out in a PTF which can be used to circumvent this.
PTF SI76529 (7.3) and SI76674 (7.4) need to be applied to use the circumvention.

They also said something to the effect that 7.4 will be the last release to have this circumvention and you really should get the BMR’s from Infor which will correct the code instead.

<snip>
Note - The job needs to be restarted after the environment variable is put in place.

Activating the circumvention system wide for all jobs:
ADDENVVAR ENVVAR(QIBM_QUERY_CONVERT_BLANK_TO_0) LEVEL(*SYS)

Activating the circumvention at the job level:
Run the following in the job you want to revert to the incorrect behavior.
Note: This must be added before the job does any SQL or query. Otherwise, it will not be picked up.

ADDENVVAR ENVVAR(QIBM_QUERY_CONVERT_BLANK_TO_0) LEVEL(*JOB)

The circumvention is only available at R730 and R740.

Removing the circumvention:
RMVENVVAR ENVVAR(QIBM_QUERY_CONVERT_BLANK_TO_0) LEVEL(*SYS)
RMVENVVAR ENVVAR(QIBM_QUERY_CONVERT_BLANK_TO_0) LEVEL(*JOB)
</snip>

I defy you to find this environment variable with any search engine.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.