|
I saw that manual section, sorry I should have mentioned it in the original post. They're programmers, of course they need access to CRTLF <G>. Here's the bigger issue, the physicals we're concerned with are in a test environment. The programmers need access to the environment to review test data when there is a problem. However, they have a (nasty) habit of building logicals in their private library over the physical in the test library, so when we go to clear that lib to refresh from production we have to find all the cross-library logicals and delete them first. We were hoping for a simple authority-fix to prevent them from creating the logical. One solution we've come up with is to add a VCP to the CRTLF command that checks that the based on library isn't the test library, or even better, checks to see if the programmer has Management rights, so we can allow it where they do and prevent it where they don't. Of course the enterprising programmer will simply start SQL and do a create view statement. I can revoke rights to create index, but not create view. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: Vern Hamberg [mailto:vhamberg@centerfieldtechnology.com] Sent: Thursday, December 12, 2002 5:34 PM To: midrange-l@midrange.com Subject: Re: Prevent creation of a logical over a physical Walden This is the straight stuff from the manual >To create a keyed logical file over one or more physical files, the user >must have object operational and object management authorities or object >alter authority for each of the files specified on the PFILE or JFILE >keywords in DDS. To create a non-keyed logical file, only object >operational authority is required. So removing Management or Alter rights should stop keyed logicals, but not, it appears, unkeyed logicals. Can you restrict the CRTLF command? Or do they need it for other things? Hmm Vern At 04:52 PM 12/12/2002 -0500, you wrote: >We'd like to prevent the programmers from creating logicals over a physical >in our test environment. We thought removing 'Management' authority would be >sufficient, but it's not. Any ideas? The programmers still need to be able >to read the data so we can't remove Operational rights. > >-Walden _______________________________________________ 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-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.