×
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.
On 31-Oct-2014 14:03 -0500, Charles Wilt wrote:
On Fri, Oct 31, 2014 at 2:48 PM, Kelly Beard wrote:
Thanks. Yes, eventually I did a DSPMSG QSYSOPR and found that a
command in the CL program the Java program was trying to run
couldn't be found. I fully qualified the CL command name in the CL
program, recompiled, and the Java program was happy. I wish these
things would just fail instead of hanging.
Was the job in a MSGW then?
You might see about issuing a CHGJOB INQMSGRPY(*DFT)
Also, consider looking at the error handling in the CL.
The default Work Management for the jobs that processes the command
requests for the connection [or the connection generally] might be
changed instead, using the Change Job Description (CHGJOBD) for the same
Inquiry Message Reply Handling (INQMSGRPY) parameter. The replies can
be processed first by the System Reply List Entries by specifying the
special value *SYSRPYL; any replies for which an entry does not exist
[or an exit program does not respond] will be required (*RQD).
A program can be written and registered for the exit point that
controls Inquiry message processing. See the OP and replies for the
past thread from the archives with Subject: Can I send a reply message?:
<
http://archive.midrange.com/java400-l/200808/threads.html#00047>
The following web search yields other discussions in that archive
which might have more information worth review:
<
https://www.google.com/search?q="message+wait"+OR+"msgw"+site%3Ahttp%3A%2F%2Farchive.midrange.com%2Fjava400-l>
As an Amazon Associate we earn from qualifying purchases.
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.