|
On 21-Oct-2014 12:59 -0500, Michael Ryan wrote:
Ok...I seem to be getting this more frequently. I'm issuing a remote
connect, and occasionally receive a 0842 error code. I can't seem to
get a lot of info by googling, but it appears that the connection
already exists. I am making a lot of calls. Should I use SET
CONNECTION when this happens? Anyone encounter this? Thanks.
The results of a request to Display Message Description (DSPMSGD) of the
corresponding SQLCODE is often helpful to review; though IIRC the identical
information should be in the InfoCenter\KnowledgeCenter under SQL codes and
messages:
DSPMSGD SQL0842 QSQLMSG
As I recall for my few programs using DRDA coded to utilize or allow for
more than one hard-coded connection, I would just issue a SET CONNECTION
for the specified RDB when that was the condition for a CONNECT statement.
--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.