Re: Restrict Printer Attachments?

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     Re: Restrict Printer Attachments?

>>
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 
>>
pr

>What I did at one place was to build a CL program, with display screen, to
>be copied over for each printer.  WRKSPLF was not a user choice from a
>menu, nor was there a command line.   On the screen were the choices that
>we were allowing for that printer, including view, print, start printer,
>and a few other commands.  Would the same approach be useful for your
>OUTQs?
>Booth Martin     
---------------------------------------------------

This is one of the functions of my company's package ETIKIT. 
It has a WRKSPLF & WRKOUTQ & WRKWTR & WRKUSRJOB lookalike with 
which you can;
1. Secure who has the function.
2 You can secure individual action options to certain people(or groups)
        like 2=change, 4=End job(wrkusrjob) or who can start which wtr's
3 You can't get to WRKWTR's (F22 from wrkoutq)
4. etc.

John Carr
EdgeTech

(I appologize if this is out of line. but it was in reference to a 
specific need.) 
+---
| 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: david@midrange.com
+---