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



We use RXS and had similar issues way back.
Check authorities for both QTMHHTTP and QTMHHTP1.

We use a group authority for all our users, I ended up adding both QTMHHTTP and QTMHHTP1 to the group.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, November 09, 2017 12:37 PM
To: Midrange Systems Technical Discussion
Subject: Weird SSL problems with RXS calls for a specific user

One of our customers uses Krengeltech RXS to communicate with web services from a program tied to an exit hook in one of our products.

For most users, this works reasonably well. But for a single specific user, it fails with a message to the effect of
RXS0000010 . . . RXS_getUri . . . SSL connect error

in the joblog.

On the advice of Krengeltech technical support, which sent me this link,
<https://isupport.krengeltech.com/rxs/configuring_ssl_permissions/>
I checked the permissions of /QIBM/UserData/ICSS/Cert/Server. The files
in the directory are already both *PUBLIC *R, and all the directories in
the path are already *PUBLIC *RX all the way down to /QIBM.

Anybody got any ideas what could be going on? I've already sent
Krengeltech my findings.

--
JHHL

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.