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. Rod can delete the file if anna creates it, but anna can not delete the file if rod creates it. I do notice that Anna is *SYSOPR and Rod is *SECADM (noticing that, since i didn't create this account, I think I'm going to lower him down to *SYSOPR). I have searched high and low for security on this file and can't find any. Is it because rod is *SECADM and anna is only *SYSOPR? Regards, Jim Langston +--- | 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.