Restricting Command Use
You can easily restrict command use to a specific group of users. You can specify first entries for those users who should be allowed to use the command, then specify an entry to trap the use of that command by any other user. Finally have an entry for any users who should have general command usage except for the restriction. The following example demonstrates command restriction.
*------------------------ --- --- -- -------- -------- -------- --------
*T S E T U N A P
*E C C Y S O C A
*X O O P E D T R
*T L L E R E N M
*------------------------ --- --- -- -------- -------- -------- --------
/CMD /SHUTDOWN / 1 12 LGLOPR HOSTNODE DMSPOR TOVM
/CMD /SHUTDOWN / ACTIONX
/CMD /NETWORK /SHUTDOWN / 1 25 NETOP1 HOSTNODE DMSPOR TOVM
/CMD /NETWORK /SHUTDOWN / ACTIONX
/CMD /NETWORK / 1 20 NETOP1 HOSTNODE DMSPOR TOVM
/CMD /NETWORK / 1 20 NETOP RMTNODE DMSPOR TOVM
/CMD /NETWORK / ACTIONX
/CMD / 1 4 LGLOPR HOSTNODE DMSPOR TOVM
/CMD / 1 4 MAINT HOSTNODE DMSPOR TOVM
/CMD / 1 4 MAINT PROPNODE DMSPOR TOVM
*------------------------ --- --- -- -------- -------- -------- --------An RTABLE containing these entries allows LGLOPR at HOSTNODE to use the SHUTDOWN command, but anyone else trying to use it invokes ACTIONX. ACTIONX could be DMSPOS sending the offending command to the logical operator or it could be a user-written action routine taking some other action against the issuer, depending of the severity of the offense. The same description applies to the NETWORK SHUTDOWN and NETWORK commands. So, routing table coding provides considerable flexibility in granting or restricting command authority.