|
But that will only discourage, and not prevent a user from changing the library for the output file. And it won't affect queries they have already written. Also, it doesn't address files of the same name as the production file being written to whatever library (shudder!!). I feel better knowing the library is locked down. Any user on our system with Query has their own library to play in, not in any job description or library list. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Tuesday, November 1, 2005 9:18 AM To: Midrange Systems Technical Discussion Subject: RE: Determine name of query that created data file To discourage users from creating files in QGPL change their user profiles. CHGUSRPRF CURLIB(...) Pick something besides *CRTDFT or QGPL as they are one and the same. Had the same problem here. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
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.