RE: can we on IBMi restrict database updates to user@host like other db platforms

Sorry, I didn't mean everyone had two profiles. I meant there was one
generic readonly profile (or maybe one per department due to visibility
restrictions like who can see GL stuff, I don't remember) that everyone used
for ODBC and then they used their own profile for normal access.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Gerald
Magnuson
Sent: Monday, June 15, 2020 11:31 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: can we on IBMi restrict database updates to user@host like
other db platforms

here is what they do today on their MySQL databases....
all developers share 1 profile to connect "developer"....
it is read only from all sources EXCEPT the actual server ip, which has full
update rights.
developer@% = read only
developer@10.xxxxxxxxxx = full access

on DB2, each developer has their own userprofile, but I just took away their
update ability (made their profiles *USE)....

My manager doesn't want me to make a 2nd profile for each individual,
allowing them update, but would rather have them use the "developer" method
we use on MySQL...




On Mon, Jun 15, 2020 at 10:13 AM <smith5646midrange@xxxxxxxxx> wrote:

I don't know if this would be an option for what you are doing but we
have provided a "readonly" profile for user ODBC connections and then
blocked their normal profiles from connecting via ODBC. It was a lot
easier than what I think you are about to go through.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Kevin Bucknum
Sent: Monday, June 15, 2020 11:05 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: can we on IBMi restrict database updates to user@host
like other db platforms

QIBM_QDB_OPEN looks like it has the information to make that decision,
but I've never played with it.

https://www.ibm.com/developerworks/ibmi/library/i-open-db-file-exit-pr
ogram/
index.html
<https://www.ibm.com/developerworks/ibmi/library/i-open-db-file-exit-p
rogram/index.html>


On Mon, 2020-06-15 at 09:50 -0500, Gerald Magnuson wrote:

well, that looks good, but now I was just given another curve ball...

I misspoke when I said "connection" accept or reject...

if the user id connects from anywhere but the specific IP, they can
connect

as READONLY.



On Mon, Jun 15, 2020 at 9:04 AM Kevin Bucknum <

<mailto:Kevin@xxxxxxxxxxxxxxxxxxx>

Kevin@xxxxxxxxxxxxxxxxxxx

wrote:


Then you are looking for QIBM_QZDA_INIT.

<https://www.itjungle.com/2011/02/23/fhg022311-story01/>

https://www.itjungle.com/2011/02/23/fhg022311-story01/


On Mon, 2020-06-15 at 08:57 -0500, Gerald Magnuson wrote:


yes, only ODBC...





[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any
other party and is required to destroy the information after its
stated need has been fulfilled. If you are not the intended
recipient, or the employee of agent responsible to deliver it to the
intended recipient, you are hereby notified that any disclosure,
copying, distribution or action taken in reliance on the contents of
these documents is STRICTLY PROHIBITED. If you have received this
email in error, please notify the sender immediately to arrange for
return or destruction of these documents.
--
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

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

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