Re: [IBMiOSS] End-user & native ODBC in Python -- OPENSOURCE

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

Subject: Re: [IBMiOSS] End-user & native ODBC in Python
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Thu, 17 Oct 2019 17:29:54 +0000
List-archive: <https://archive.midrange.com/opensource/>
List-help: <mailto:opensource-request@lists.midrange.com?subject=help>
List-id: IBMi Open Source Roundtable <opensource.lists.midrange.com>
List-post: <mailto:opensource@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/opensource>, <mailto:opensource-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/opensource>, <mailto:opensource-request@lists.midrange.com?subject=unsubscribe>

Initially, the user was getting an AF on dir /QOpenSys/pkgs/share/ibm-iaccess/mri2924. The permissions were *PUBLIC & QSYS *R. I contacted IBM support and they had me change the permissions to QSYS *RWX & *PUBLIC *RX for the dir, and QSYS *RW & *PUBLIC *R for the files in that dir. After doing that, there haven't been any more AF entries. That's when it started giving the error in the OP.

Thanks

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.