Example 4-24 shows RPIBLDDS being run. 

rpibldds Using default file RPIDIRCT SYSUT1 Processing batch file RPIDIRCT SYSUT1 using "RAC" command interface => RDEFINE VMCMD RACF UACC(READ) => RDEFINE VMCMD RAC UACC(READ) => ADDGROUP SYSTEM => ADDGROUP SYSTEM OVM(GID(0)) => ADDGROUP STAFF => ADDGROUP STAFF OVM(GID(1)) => ADDGROUP GBIN . . . => RDEFINE VMMDISK MAINT710.5A2 OWNER(MAINT) UACC(NONE) => PERMIT MAINT710.5A2 CLASS(VMMDISK) RESET ID(MAINT710) AC(ALTER) => RDEFINE VMMDISK MAINT710.5A4 OWNER(MAINT) UACC(NONE) => PERMIT MAINT710.5A4 CLASS(VMMDISK) RESET ID(MAINT710) AC(ALTER) => RDEFINE VMMDISK MAINT710.5A6 OWNER(MAINT) UACC(NONE) => PERMIT MAINT710.5A6 CLASS(VMMDISK) RESET ID(MAINT710) AC(ALTER) . . . => RDEFINE VMMDISK MAINT710.400 OWNER(LOHCOST) UACC(NONE) => PERMIT MAINT710.400 CLASS(VMMDISK) RESET ID(LOHCOST) AC(READ) . . . 

When the RPIBLDDS EXEC  completes, your RACF database is initialized with all the VMs and resources that were included with the z/VM system. Now, you create more RACF administrators. You must determine what VMs are trusted to manage your secure environment. 

The user IDs that are part of the system maintenance process (VMSES/E) must have authority to access minidisks across the system. For this reason, the RACF Program Directory recommends the following VMs be granted OPERATIONS authority: 

GLYPH<SM590000> MAINT710 

GLYPH<SM590000> BLDSEG 

GLYPH<SM590000> BLDRACF 

GLYPH<SM590000> BLDNUC 

GLYPH<SM590000> BLDCMS 

GLYPH<SM590000> MIGMAINT 

The RACF altuser  command is used to modify the RACF attributes for a VM (see Example 4-25). 

rac alu MAINT710 operations Ready; T=0.01/0.01 11:49:44 rac alu bldseg operations Ready; T=0.01/0.01 11:49:53 rac alu bldracf operations Ready; T=0.01/0.01 11:50:02 rac alu bldnuc operations Ready; T=0.01/0.01 11:50:04 

