In our example, we show the  PERMIT  for each user, although defining the permission by group  (for example, ITSOGRP) is a preferred practice. Run  RPIBLDDS EXEC  again to run these  definitions, as shown in Example 5-17. Example 5-17 Output of RPIBLDDS rpibldds rpidirct sysut1 Processing batch file RPIDIRCT SYSUT1 using "RAC" command interface  => RDEFINE SURROGAT LOGONBY.MAINT UACC(NONE) AUDIT(ALL)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(ALTER) ID(MAINT) RESET(ALL)   => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(PWNOVAK)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(PACOSTA)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(BADER)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(EDI)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(VIC)   => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(KLAUSM)  => PERMIT LOGONBY.MAINT CL(SURROGAT) ACC(READ) ID(WILLIANR)   => RL SURROGAT LOGONBY.MAINT AUTH CLASS NAME ----- ---- SURROGAT LOGONBY.MAINT LEVEL OWNER UNIVERSAL ACCESS YOUR ACCESS WARNING ----- -------- ---------------- ----------- ------- 00 IBMUSER NONE READ NO  INSTALLATION DATA ----------------- NONE APPLICATION DATA USER ACCESS ACCESS COUNT  ---- ------ ------ ----- IBMUSER ALTER 000000 PWNOVAK READ 000000 PACOSTA READ 000000 BADER READ 000000 EDI READ 000000 VIC READ 000000 KLAUSM READ 000000 WILLIANR READ 000000 Chapter 5. Security policy management on IBM z/VM  125