|
Maybe IBM should have created a "schema" object that is associated with a user profile through a user profile attribute. Kind of like the 'home directory' is. Anyway, the major problem we encountered with this is that the VB client process just stopped working. When we examined the joblog we discovered that the system process was trying to CHGOBJOWN on a newly created object and the 'current' user didn't have enough authority to change the objects owner to the user profile that just happened to be the same name as the library. IBM's suggestion .... Use the *SYS naming convention when working with the iSeries database. Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400e Professional System Administrator NW Natural (Gas Services) keg@nwnatural.com Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** -----Original Message----- From: R. Bruce Hoffman, Jr. [mailto:rbruceh@attglobal.net] Sent: Thursday, September 05, 2002 9:05 AM To: midrange-l@midrange.com Subject: Re: SQL enhancements ----- Original Message ----- From: "Graap, Ken" <keg@nwnatural.com> To: <midrange-l@midrange.com> Sent: Thursday, September 05, 2002 11:48 AM Subject: RE: SQL enhancements > It is apparently considered a "feature" of SQL, that if you have a library > with the same name as a user profile, anything you add to the library via > the SQL interfaces (CREATE TABLE for example) will be owned by the user > profile that just happens to have the same name as the library! > > Would any of you SQL gurus care to take a stab at explaining why any objects > added to a collection would be owned by a user account with the same name as > the collection? I still shake my head as I write this. This seems totally > disconnected from any security scheme I can think of... Libraries are unique to the 400. In the DB2 world, there are instances of databases and you connect to them. Some architectures allow more than one instance. The 400 is a single instance image. Schemas were a way of segregating tables by "owner". The 400 people mapped that schema name to libraries. On other instances of DB2 it is not uncommon to produce user profiles that are "owner" profiles only. Then you log on with that user and create the tables. They all appear in one instance, but with different owners. Sometimes the owner is named ACCOUNTSPAYABLE or AP or whatnot. It's just the way SQL works everywhere else. The 400 is unique. =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified Specialist - iSeries Administrator -- IBM Certified Specialist - RPG IV Developer "There is a crack in everything, that's how the light gets in. - Leonard Cohen _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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-2025 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.