Allocating the user attributes data set (SYS1.UADS)

When TSO/E is installed, member IBMUSER0 will be placed in the data set pointed to by the UADS DDDEF or DD statement in the SMP/E procedure. If you have previously installed TSO/E, you should allocate a dummy user attributes data set (UADS) for installation. This will prevent SMP/E from putting IBMUSER0 back in your UADS data set (if you have deleted it), or replacing it with the default IBMUSER entry (if you use the IBMUSER0 user ID and have changed its attributes).

The dummy UADS data set may have any high-level qualifier, and need not be cataloged in the master catalog. It should be available for SMP/E processing, in case the IBMUSER0 default entry is changed, or other entries are added, by service.

If you are installing TSO/E for the first time, allocate a SYS1.UADS data set and catalog it in the master catalog.

Note:

If you are installing TSO/E for the first time and reallocate the UADS data set, or if you have deleted IBMUSER0 and allow SMP/E to replace it in your production UADS data set during the installation of TSO/E you will need to use the SYNC command to re-synchronize the UADS and BRODCAST data sets.
SYS1.UADS must be allocated with LRECL=80 for installation. When the SMP/E installation is complete, it should be reallocated with LRECL=172. Any high level qualifier can be used for UADS when installing. However, when you IPL, a SYS1.UADS must exist, be cataloged, and contain at least one user.

Optimize the block size of SYS1.UADS to minimize waste of space. For more information about allocating the UADS, see Working with the UADS and broadcast data set.