|
Or, opening up the door for a rogue programmer who thinks standards are for everyone else,, At 10:00 AM 7/26/2001, you wrote: >alan shore wrote: > ><Be careful which of the jobs adopt owner authority. It should only be the >job that needs it. Any job submitted from this job will also adopt that >owners authority.> > >VERY good point Alan, because that could open up the door for rogue stuff >if a programmer was unaware of that ! > >Chuck > > > > > >>> "Phil" <sublime78ska@yahoo.com> 07/25/01 06:13PM >>> > > If it is submitted to batch, use adopted authority *OWNER on the pgm > that is > > submitted. > > > > The batch job will then have the authority of the object owner. > > > > Phil > > > > > -----Original Message----- > > > From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On > > > Behalf Of Chuck Lewis > > > Sent: Wednesday, July 25, 2001 5:16 PM > > > To: RPG400-L > > > Subject: Programing Question/Authority... > > > > > > > > > Hi Folks, > > > > > > Don't do this enough and can't for the LIFE of me figure it out... > > > > > > We are using 3rd party software and we can define "Fast Paths" that let > > > user run programs we write outside of the 3rd party suite. > > > > > > I have written simple little RPG program that they call that prompts the > > > user for a date and then submits a CL to run the report. Initially I was > > > getting an error because the user is not authorized to the Submit > > > command. I fixed this with a Job Description. This second CL creates a > > > LF in QTEMP and then runs an RPG program to produce a listing. Well now > > > they can't create the LF because the submitted job is running under the > > > User Profile which does not have authority to do that. > > > > > > Is there an easy solution to this ? I've been buried in it now (along > > > with juggling a BUNCH of other stuff) and have some ideas but wanted to > > > avoid reinvent the wheel ! > > > > > > Thanks, > > > > > > Chuck > > > > > > +--- > > > | This is the RPG/400 Mailing List! > > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > > | To unsubscribe from this list send email to > RPG400-L-UNSUB@midrange.com. > > > | Questions should be directed to the list owner/operator: > > > david@midrange.com > > > +--- > > > > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > +--- > > | This is the RPG/400 Mailing List! > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > > > > +--- > > | This is the RPG/400 Mailing List! > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > >+--- >| This is the RPG/400 Mailing List! >| To submit a new message, send your mail to RPG400-L@midrange.com. >| To subscribe to this list send email to RPG400-L-SUB@midrange.com. >| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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-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.