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

Try doing a dsppgm of the PGM A object. Press enter twice, This should
display a list of modules called from that program and the library they
are called from.
If PGM B is in the list that will explain your issue.

You will need to re-compile PGM A to get the new module definitions and
libraries included...

Phil Catlin

anupam sinha <anupam_sinha15@xxxxxxxxx>
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
04/02/2014 10:29 PM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>

"bpcs-l@xxxxxxxxxxxx" <bpcs-l@xxxxxxxxxxxx>

[BPCS-L] BPCS Programs referring old objects


I have this unique situation. Recently, we switched our LPARS and restored
all the BPCS libraries to new LPAR and activated it for users.

We have now started discovering that in some cases programs are not making
call to the objects that are on top of library list. Rather it is making
call to the object in other library, but in library list

PgmA in lib LIB1 calls PgmB in LIB2

this is how the lib is setup


If I re-compile PgmB and place object in QTEMP and then call Pgm A,
ideally PgmB from QTEMP should be picked up. But, it is not the case. PgmA
is referring to object PgmB in LIB2

I tried renaming the PgmB in LIB2 to xxPgmBx and call PgmA, but now PgmA
is referring to xxPgmBx in LIB2

I'm not sure if this is something related to any setting in BPCS or
i-Series setting

Any help on this would be greatly appreciated


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