Added security options in WRKOBJBRM to prevent accidental restores to the original library

Request Description:

When using the WRKOBJBRM command in BRMS, selecting option 7 = Objects to restore, followed by option 1 = Select, results by default in a restoration into the original library, with the parameter:

• Restore library: *SAVLIB

This default behavior can cause an accidental restoration into the original library, and therefore the unintended overwriting of existing objects, simply due to a double key validation.
We want to avoid this operational risk and improve the safety of use for administrators and operators.

🎯 Enhancement Requests

1. Ability to disable option 1 = "Select" in WRKOBJBRM

Currently, this option is always visible and selectable.
It would be useful to allow:

• its deactivation,

• its removal,

• or an authorization control (USRCLS, special authority, etc.).

Objective: Prevent unintentional restorations caused by incorrect manipulation.

2. Ability to remove or modify the default value *SAVLIB

Today, the value *SAVLIB forces restoration into the original library.
We request the ability to define a different default behavior, such as:

• a different target library,

• a blank value,

• forcing the user to enter a target library,

• or a system/BRMS parameter allowing control of this default value.

Objective: Prevent any risk of overwriting an existing library.

3. Add a system/BRMS option “Forbid automatic overwrite”

Ideally, a global BRMS parameter could be added, for example:

• *RESTORE_ALLOW_REPLACE(NO)

• or an equivalent BRMS setting in WRKPCYBRM

This parameter would prevent any restoration into the original library unless explicitly confirmed.

📌 Expected Benefits

• Reduced risk of human error during restore operations

• Increased security in production environments

• Greater operational control for system administrators and operators

• Alignment with best practices for restore operations (separation of source/target libraries)

✅ Conclusion

We request the availability of these enhancements in BRMS, or any alternative allowing:

• Control over the presence of option 1

• Setting a default library other than *SAVLIB

• Preventing the unintentional overwriting of existing objects

These features would be highly beneficial for the IBM i community and would significantly improve the security of BRMS operations.