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



The answer, I think: programmer error. A service program mysteriously
wasn’t there (after six years), the stored procedure (a surprise; I’d been
told it was a Java call) specified a qualified service program name, and
the error, SQL0204, was the most accurate error message. It appears a
compile failed because of a missed binding directory entry and the
programmer thought seeing the *MODULE object meant everything was good…even
though I’d already sent an email reminding them to look for the *SRVPGM
object. Sigh…the RPC failed because the object wasn’t there (and I
considered stored procedure overloading as a possible problem as well).

The director of software engineering was on the call; he’d written the
Linux code and we confirmed the connection string was good.

There’s no good in roasting the likely guilty party for botching a compile
and missing it, so I just talked the group through recreating the service
program in the standard object library and rebuilding the stored procedure.

If you know about the Five Why’s, you want to drill down. The root cause
was dummy data sent by an EDI customer (who likely sent a pickup request
before the order was picked, meaning the actual weight and pieces were
unknown and they sent one piece and one pound to meet reasonableness
requirements) that got into the order database and that dummy data
triggered an unwanted action in the service program. Further down the
stack: I should have added a bit of additional logic in the service program
to prevent inadvertent execution of the unneeded code. The programmer
wanted to comment out those few lines of code to solve the problem caused
by the customer process error. This is the world we live in!

On Sat, Jul 31, 2021 at 11:49 Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Tell us more about the program. What language? Special environment (e.g.,
COMXML)?
Complete error messages? Anything ...

On Sat, Jul 31, 2021 at 12:27 PM Reeve <rfritchman@xxxxxxxxx> wrote:

Greetings all--I'm trying to help a customer who recompiled a service
program targeted by an RPC called from a Linux interface.


--
Jack Woehr, IBM Champion 2021
<
https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/public_url

Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


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.