Jim Langston wrote: > We have one S36 procedure that runs that gives one user problems. > > This procedure creates a temp file in qs36f and leaves it when it's > done. > The beginning of the procedure deletes the file if it exists before > creating it. > We have 2 users that use this procedure, anna and rod, rod's user group > is anna. > > When Rod runs the procedure, everything is fine and dandy. > When Anna runs the procedure after Rod does, an error occurs saying she > is not allowed to delete the file. Even though Rod is a member of Anna's group, Anna does not automatically get rights to stuff that Rod creates. I think that what you are trying to accomplish is to have the objects that Rod creates owned by Anna's group. Do this by specifying the OWNER(*GRPPRF) in Rod's profile. This will cause everything that Rod creates to be owned by user Anna. Or better still, create a group called SYSOP and have both Rod and Anna be a member of it (with OWNER(*GRPPRF) of course) . This way when Anna eventually leaves the company, you don't have to fix the ownership of all of those objects her group created. jte -- John Earl firstname.lastname@example.org The PowerTech Group 206-575-0711 PowerLock Network Security www.400security.com The 400 School www.400school.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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.