Jerome, It's fun isn't it ? I had this happen a few times until I found out how they did it. If I remember correctly it was the CHGWTR commend that was getting invoked. Changed authority on the command to public *EXCLUDE (granting it to those I did want to have it) and the problem stopped. HTH -Steve Cotes -email@example.com > ---------- > From: Jromeh[SMTP:Jromeh@aol.com] > Sent: Thursday, October 30, 1997 11:40 PM > To: firstname.lastname@example.org > Subject: Restrict Printer Attachments? > > Hi, > > How can printer attachments be restricted? We need a way to allow > users > to create output into an outq, but restrict them from attaching a > printer > to that outq. > > When they're in the WRKSPLF screen (from a menu, no command line), > they > do 9=Work with printing status, then 2=Change status, then attach a > printer to the queue, thinking they're only routing their output to > that > printer. It's a monitored queue and should never be attached to a > printer, attaching it results in wasted paper and lost spool. > > TIA, > > > Jerome Hughes email@example.com > InterPro Consulting Services www.interproinc.com > Rosemont, IL USA these are my own opinions only > > OMNI User Communications Dir. www.omniuser.org > > "Remember, I started this company in my parent's garage." Steve Jobs > > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.