What version of Radia are you using?

You need to be a little bit careful how you update each PACKAGE as you need to ensure that existing deployments don't see the change it as an update.  You can use ZEDMAMS with a ZFILE to update the instances remembering to use the KEEPDATES=YES parameter on each update.

Hope that points you in the right direction!

Thanks for quick reply.

I'm promise that I will be careful ;)

Could you send me some example about that because I didn't see any examples in docs files about ZEDMAMS. I didn't see also ZFILE parametr for ZEDMAMS command.

We are using Radia 10 version.

The ZEDMAMS documentation can be found in the "Radia Client Automation Reference Guide" on pages 617-659.
The reference guide is named Reference_Guide.pdf and is included in the Core Setup Media under "\Documentation\RCA_Guides".

You should backup your database before using this utility and be very careful running it.  
Test your commands/updates in a non-production environment and be sure the result is what you want/expect before making any changes to the production environment.

I really need that one. I hope that will help

Thank you! :)

Pawel,

The question is why was that zstop put in in the first place (aside from the very obvious reason). Zstops are sometimes used as a negative replacement for proper positive assignment, i.e. where software has been blanket assigned to the wrong devices and the zstop is used as a filter. A better approach is to assign things more accurately (if possible). So when you now consider updating your zstop, are you going to add Win10 to the list and create another potential future problem or review the underlying assignment?