There really is no good way to do what you want. Regarding that post you've found, what that is doing is basically filtering what the user sees based on batch session name. You could theoretically create a role per user with a specific naming convention per user, but that would get messy very quickly if you have a lot of users. The users would also have to be responsible to name their batch sessions with the prefix in order for them to see their sessions.
Does the restriction need to be by user or can you restrict it by a group of users? If you can limit the number of roles you would have to create the aforementioned solution can be easier to manage.
As far as jobs, you can give the users access to SMX, which will only display their own jobs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.