Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Synchronizing the RACF data base with the broadcast data set z/OS TSO/E Customization SA32-0976-00 |
|
To synchronize the RACF® data base with the broadcast data set use either the SYNC command or the SYNC subcommand of ACCOUNT. The SYNC command (or subcommand) must be invoked APF-authorized. Therefore, you must ensure that SYNC is an authorized command by either creating an entry in the authorized command table, or by updating the PARMLIB member IKJTSOxx. For information on updating PARMLIB, see Specifying authorized commands/programs, and commands not supported in the background. If you have converted all user information from the UADS to the RACF data base, specify the RACF operand when you issue the SYNC command. The RACF operand causes the broadcast data set to be synchronized with the RACF data base. That is, for every user ID defined to TSO/E in the TSO/E segment of the RACF data base, a corresponding entry is made in the broadcast data set. Figure 1 is a sample listing showing how to synchronize the broadcast data set with the RACF data base. For an explanation of this JCL, see Executing the terminal monitor program. Figure 1. Synchronizing
the broadcast data set and RACF data
base
Note: With dynamic broadcast support, the SYSLBC DDNAME is no longer
required. If the SYSLBC DDNAME is not specified, the currently active
broadcast data set will be used by the job. If the SYSLBC DDNAME
is specified, the referenced data set will be used by the job.
If you have not converted all user information to the RACF data base, specify the BOTH operand when you issue the SYNC command. The BOTH operand causes the broadcast data set to be synchronized with both the UADS and the RACF data base. That is, for every user ID defined in either the UADS or the TSO/E segment of the RACF data base, a corresponding entry is made in the broadcast data set. Figure 2 is a sample listing showing how to synchronize the broadcast data set with the UADS and the RACF data base. For an explanation of this JCL, see Executing the terminal monitor program. Figure 2. Synchronizing
the broadcast data set, UADS and RACF data
base
Note: With dynamic broadcast support, the SYSLBC DDNAME is no longer
required. If the SYSLBC DDNAME is not specified, the currently active
broadcast data set will be used by the job. If the SYSLBC DDNAME
is specified, the referenced data set will be used by the job.
|
Copyright IBM Corporation 1990, 2014
|