In SYSSEC, you can define a different FUSER for a particular library definition. This allows you to be able to store programs in a single FUSER from multiple environments (FSECs) in various LPARs in an enterprise. This is allowable (and useful) on the mainframe. NaturalONE currently does not honor that and it ought to mimic the mainframe capability.
Hope this will resolve hem without any delay.
This is a MAJOR problem. NaturalONE is supposed to be a complete replacement for Natural3270. We have systems designed around different FUSER settings to properly manage and run our applications. We've spent hundreds of hours working on the implementation of NaturalONE and then we run into this. Please fix ASAP.