Allow RRSF to distinguish between ALU commands and only propagate RESUMES/PWs commands.

This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan. If this requirement is high value, please re-open it, or open a new requirement.

Hi,

This is in response to an email I received stating additional information is needed. I see a comment about using ONLYAT keyword. While that would be for a specific admin issuing a command. But we have products that have system special or group special with CLAUTH that will be issuing the commands. We could possibly educate admins with the access as they come and go but we don't have any control over the products that have to issue the commands. We thought controlling who can resume users, reset password or set passwords across the enterprise via RRSF made much more sense. The solution using ONLYAT infers that there is no requirements for command direction in RRSF since you could always use ONLYAT. But we know that is not practical and RRSF is there and it does a great job with all the commands....just not the ALTUSER since some of the operands may or may not make sense to propagate and there is know way to distinguish that. We truly believe offering RRSF command in the form of or something similar to AUTODIRECT.node.USER.ALTPWD or AUTODIRECT.node.USER.ALTRES would allow us to direct commands for passwords and resumes at our discretion while protecting the other types of data that can be changed via an ALTUSER command that is unique between environments.

Thanks for your consideration.

Charlie

Thanks for submitting this requirement.
Have you considered specifying ONLYAT on your ALTUSER commands? You could write a REXX script and use IRRXUTIL to get the list of nodes, and issue the ALTUSER... ONLYAT for each.