All MYWINDOM windows users logged in on any workstation
user default cpu=@ + logon=MYWINDOM\\@
###########################################################
# APPLIES TO ALL "MYWINDOM" WINDOWS USERS LOGGED IN ON ANY
# WORKSTATION.
user default cpu=@ + logon=MYWINDOM\\@
begin
# OBJECT ATTRIBUTES ACCESS CAPABILITIES
# ---------- ------------ ----------------------
job cpu=@ access=@
schedule access=@
resource access=@
prompt access=@
file access=@
calendar access=@
cpu cpu=@ access=@
parameter name=@ access=@
userjob cpu=@ + logon =MYWINDOM\\r@ access=display
userobj cpu=@ + logon=@ access=@
eventrule name=@ access=add,delete,display,modify,list,unlock
action provider=@ access=display,submit,use,list
event provider=@ access=use
report name=@ access=display
runcygrp name=@ access=add,delete,display,modify,use,list,unlock
vartable name=g@,$default access=add,delete,display,modify,use,list,unlock
wkldappl name=@ access=add,delete,display,modify,list,unlock
lob name=@ access=use
end
############################################################Windows Users in MYWINDOM which name begins with 'r' can display only userjobs. All others MYWINDOM windows user that is logged in on any workstation are given unrestricted access to all objects. They are the only ones who can generate all kinds of plans and who can create, update, and delete event rule definitions. All users have access to all variable tables beginning with "g" and to the default table, irrespective of the default variable table name.
Note: Starting with version 9.2, due to support of the Windows users
in User Principal Name (UPN) format, you have to specify the windows
domain users in a different way in the Security file. In the same
example for the previous version you have the following syntax:
user default cpu=@ + logon=MYWINDOM\@
..........................................
userjob cpu=@ + logon =MYWINDOM\r@ access=display