The creator of the note pad specifies the MULTIWRITE keyword to indicate whether the number of connections having update access to the note pad is to be restricted. If MULTIWRITE=NO is specified, only one connection in the entire sysplex is allowed to have update access to the note pad. If such a connection exists, a request to create a second connection with update access is rejected. If the existing connection with update access is deleted, whether explicitly by the application or implicitly by XCF when the connector terminates, a new connection with update access can be created. If MULTIWRITE=YES is specified, more than one connection can be created with update access to the note pad.

For example, an application might use MULTIWRITE=NO to simplify the serialization of changes to notes in the notepad. If there is but one connection capable of creating, replacing, and deleting notes, the application might not need code to account for the conflicts that could arise when multiple competing connections manipulate the same note. However, note that MULTIWRITE=NO does not prevent multiple work units from using the same connection token simultaneously. If single threading is needed for serialization, you might need to devise a mechanism to ensure that the application has but one work unit issuing note requests.