Tweet
A good deal of our users need the ability to view and/or print another user's spool files, by finding a specific job name for that user. Giving special authority of only *SPLCTL doesn't work - when trying to view the spool files for the desired job, the system responds with the error message "No authority to job". Giving *JOBCTL authority allows a user to see another user's jobs and spool files, but unfortunately also gives them the ability to change and cancel jobs, which has happened. Any ideas around this? We are on V3R2, security level 30. Thanks- Jim Michie
-
-
Special authorities
A good deal of our users need the ability to view and/or print another user's spool files, by finding a specific job name for that user. Giving special authority of only *SPLCTL doesn't work - when trying to view the spool files for the desired job, the system responds with the error message "No authority to job". Giving *JOBCTL authority allows a user to see another user's jobs and spool files, but unfortunately also gives them the ability to change and cancel jobs, which has happened. Any ideas around this? We are on V3R2, security level 30. Here's a couple of options, off the top of my head, you can try: 1. Put all common users under the same group profile - they should share access to the spool files then. 2. Print multiple copies of the spool file and send a copy to whoever may need it using SNDNETSPLF command. -
Special authorities
[*]SPLCTL special authority will be sufficient to access spool files, but not sufficient to access the spool files through a dspjob or wrkjob command. If the users were to view OUTQ's, then *SPLCTL would be sufficient authority to access the spool files.Comment
-
Special authorities
Jim, we are on v4r40 with security of 40. We are having the same problem since going to v4r4.... I found out this... edtobjaut on the outq in question. F11.. *public must have *change authority. This allows ANY user to do ANYTHING TO ALL spooled files in that output que. You could add that user with *change authority by pressing F6 from that command. You could change the user to have spcaut(*splctl) also. This would allow that user to be able to do anything to ANY spooled file anywhere. We are really stumped as to why this has changed.... We aren't sure what we really want to do yet...Comment
-
Special authorities
A subfile program which uses the API QUSLSPL (list spool files) could give your users the ability to view/print spool files created by specific users or jobs. The requestor would need *SPLCTL authority. The program could prompt the requestor to display spool files created by specific users, specific jobs, etc. I'm not sure if this would work, but the program might could grant the requestor *SPLCTL authority, allowing the requestor to view/ print the listed spool files, then revoke the authority when the user exists the program. Hope this helps.Comment
Comment