Resolution
What paths are correct in RRM secured entries?
goal
Can I use OS/400 generics in RRM secured entries?
fact
NetIQ Security Solutions for iSeries 8.0
fact
VigilEnt Security Agent for iSeries 7.5
fact
Remote Request Management (RRM) 7.5
fact
PSSecure 8.0 Remote Request Management
fix
RRM Secured entries use full IFS paths to establish whether the secured entries cover certain files. This is not only for IFS files but for any files/members in any library. This includes the use of IFS generics.
For example, if you want to secure member test1 in file TEST in library QGPL, use the following path:
QSYS.LIB/QGPL.LIB/TEST.FILE/TEST1.MBR
If you want to secure multiple files in a library, wildcards can be used. To secure all files in library QGPL, use the following path:
QSYSLIB.LIB/QGPL.LIB/*.FILE
To secure all objects that start with DE in library QGPL, use the following path:
QSYS.LIB/QGPL.LIB/DE*.*
OS/400 generics like *LIBL, *USRLIBL and *ALL do not work. For example, QSYS.LIB/QGPL.LIB/SALES1.FILE/*ALL.MBR and QSYS.LIB/BRICHLIB.LIB/*ALL.*ALL will not work and should be QSYS.LIB/QGPL.LIB/SALES1.FILE/*.MBR and
QSYS.LIB/BRICHLIB.LIB/*.*