Have NetMaster running on 3 systems sharing a UAMS dataset. After adding a user (using /UAMS from within NM), it does not show up on other systems.
You are sharing a UAMS file across multiple regions defined with share options 3 3.
VSAM share options 3 3 utilizes buffered IO to and from the physical VSAM file that may not occur until either the VSAM buffer becomes full or the file is closed when a region is shut down or restarted. This in turn may cause updates to the UAMS file from the updating region to not be immediately visible to other regions sharing the file until either of those conditions are met.
Unfortunately, there is not a way to force physical IO to or from the VSAM file when share options 3 3 are used, so in order to see an immediate update it may be necessary to recycle the regions involved for the physical IO to occur.
Data integrity is another concern when using share options 3 3. If simultaneous updates are performed from multiple regions, then the potential for data corruption exists. Because of this, we recommend using VSAM RLS (Record Level Sharing) when sharing the UAMS file. This method guarantees data integrity and also makes updates to the UAMS file immediately visible to all sharing regions. To enable RLS support for your UAMS file follow these steps:
Release: SLOPFC00200-12.1-NetMaster-File Transfer Management