|
Hi, Joel. (Assuming security level 40 on the AS/400) You will have to grant Use rights to the dummy profile to any user that needs to submit jobs for the dummy user. In effect, any rights that the dummy profile has are now available to the submitter (they can submit anything they want under that user's profile.) I assume that you don't want to grant rights to the directory to end users. You will indirectly give them access to that directory by granting Use rights to the dummy profile. Instead, perhaps just have the CL (or whatever) that drives the import/export process adopt the dummy profile's authority? That way, users will not need direct rights to use the dummy profile. By the way, how do you plan to kick off the NT update process? Gary R. Patterson NexSource, Inc. 980 N Michigan Ave, Suite 1400 Chicago, IL 60611 (312) 214-3526 640 W. Main St. Louisville, KY 40202 (502) 581-0106 Information technology services for business http://www.nexsource.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Joel Fritz Sent: Friday, September 22, 2000 1:50 PM To: MIDRANGE-L@midrange. com (E-mail) Subject: running batch job under another profile What are the pros and cons of running a batch job under a user profile different from that of the person who submits the job using the USER parm of SBMJOB? I'm interested in doing a cpytoimpf to a directory on an NT server visible in QNTC but only accessible by a dummy userid that exists both on the 400 and the NT box. I know it works, but I'm curious about the security ramifications as well as the things I haven't thought about at all. The benefit to me would be total control of a data export process including kicking off the process that updates the NT application. TIA +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.