×
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 a COMPILE utility that stores the compile commands in the source, so there shouldn't be a problem with incorrect compile parameters.
Thanks
-----Original Message-----
From: MichaelQuigley@xxxxxxxxxx [mailto:MichaelQuigley@xxxxxxxxxx]
Sent: Tuesday, July 16, 2019 1:56 PM
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Subject: Re: [WDSCI-L] Authority for RDi
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 07/16/2019
01:41:20 PM:
----- Message from "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx> on
Tue, 16 Jul 2019 12:27:46 -0500 -----
To:
"'Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries'" <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Authority for RDi
. . .
. . .
. . .
My guess is the remote system is trying to connect to directories or
libraries that the user is not authorized to. I would look at the
connection and the filters on the connection.
I think I've seen it when trying to bind to a procedure or module that the compiler cannot find. Is the new developer properly specifying binding directories and/or service programs to bind to?
Michael Quigley
Computer Services
The Way International
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.