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



This is in fact what the APAR tells you to do.
Initially, IBM provided this support for older versions of BPCS at v5r1
OS/400 and said that this would not be provided at V5R2, however I can tell
you that it is provided, and that V5R2 is fine with these versions of BPCS.
As Genyphyr points out, newer BPCS releases do not need it.

Clare

----- Original Message -----
From: "Francesc Junyent" <francescjm@xxxxxxxx>
To: <bpcs-l@xxxxxxxxxxxx>
Sent: Wednesday, April 09, 2003 11:45 AM
Subject: RE: BPCS 5.1 Issues upgrading to OS/400 V5R1


>
> My wife works in BPCS V5.01. When they upgraded to OS/400 V5R1, of course,
they had the well-known problems whith SQLRPG programs.
>
> The problems, you can remember, were originated because before V5R1, after
the get SQL operation FETCH the return code was 100 if the reading does not
succeed or 0 if it succeed. However in V5R1 a new return code has been
added. It is 30 when the reading has been done but with a litle trouble as,
for instance, different lengh fields. The most of programs are build as (in
pseudo code) :
>
>
>     IF Return code is not equal 0 then finish the loop.
>
> Therefore if the return code is 30 (reading has been done), the loop
finishes.
>
>
> My wife solved this trouble doing these two steps:
>
>
>     She copied the QAQQINI file from QSYS library to QSYSUSR.
>
>
>     She inserted a new record to the copied file using INSET SQL sentence
with these field values.
>
>
>             QQPARM => SQL_SUPPRESS_WARNINGS
>
>             QQVAL  => *YES
>
>
> That new record ovoids the new return code 30
>
>
> This is only a temporary solution, because I think in 2 or three years,
the QAQQINI new record will not work
>
>
> Francesc Junyent.
>
>
> Barcelona
>
>
> --------------------------------------------------------------
>
> Original message:
>
> ---------------------------------------------------------------
>
> APAR II12963 tells us that the SQL problems were confined to BPCS V6
>
> and
>
> above.
>
>
>
> Does the group agree?
>
>
>
> Are there any other caveats we should be aware of?
>
>
>
> Thanks,
>
>
>
> John G. Dyer, CDP
>
> Vice President
>
> Information Management Consultants, Inc.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------
> Yahoo! Messenger
> Nueva versi&oacute;n: Super Webcam, voz, caritas animadas, y m&aacute;s
#161;Gratis!
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.