Gadi wrote: >Users can still see a job in the job lists that they do not have authority to >view.
Ok. We all at first assumed you want to prevent them to see the CONTENTs of the jobs and to reroute/purge the jobs. Thanks for finally saying it is about the tables you want to be limited. Gadi: We here [ and possibly many IBM-MAINers ] simply don't care if the users can see other's jobs names/nr/etc and even the printer destinations and other details. We limit access to jobcontents, priority, classes, destinations, SDSF screens/commands etc. via SDSF, JESSPOOL and OPERCMDS commands. Much easier for us instead having to maintain an exit. Itschak Mugzach wrote: >What you need is Table Build Exit (see SDSF installation & customization guide >for details). in short, it get control on every row in a table display and can >remove row from the table. from my experience it have a low overhead as it got >control after all filters are executed. Hope this is what you are looking for. Agreed! It will have a low overhead. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
