Defining user ID associations

You can define these types of user ID associations:
  • For your own user ID, with password synchronization
  • For your own user ID, without password synchronization
  • For other users, with password synchronization
  • For other users, without password synchronization
  • Managed user ID associations
Important: In the following defining user ID sub-topics, if the password or phrase contains special characters that cause problems with TSO/E, the entire string ([node].userid2[/password-or-phrase]) must be enclosed in single quotation marks. Additionally, if the phrase contains blanks, or special characters such as the comma, parenthesis, or comment delimiter (/*), the string must be enclosed in quotes. Likewise, when a password or phrase starts with an asterisk, the string must be enclosed in quotes. For example: 
RACLINK ID(COREY) DEFINE('MVS03.TREVOR/We got your back') PEER(PWSYNC)
Note: Although, it is possible to define associations to users with 8 character IDs on systems that do not support TSO 8 character user IDs, care must be taken when doing so. Errors may appear on the operator console due to a failed SEND command when the association is defined.

Certain commands directed to 8 character users on systems where 8 character user IDs are not supported or enabled by TSO might fail. Examples include dataset commands (addsd, altdsd, listdsd, deldsd) when the dataset name is not specified in quotes. Also, certain rdefine and ralter commands might fail if the addmem() or delmem() operands contain dataset names that are not specified in quotes.