Calculating the number of blocks required for the profiles

Use the formula that is shown in Figure 1 to calculate the number of blocks that are required for the profiles (the value of A is described in Formula for the RACF database size).

Figure 1. The number of blocks that are required for the profiles

 A  = the number of blocks required for the profiles:

 A = F + G + H + I + J + K + L + M + N + O + P + Q + R + S + T + U + V + W + X + Y + Z
    --- --- --  --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
     16  16  16  16  16  16  16  16   3  16  16  16   2  16  16   8  16  16  16  16  16 

     + AA + BB + CC + DD + EE + FF + GG + HH + II + JJ + KK + LL + MM + NN + OO + PP + QQ + RR + SS
      ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---  ---
       16    8   16   16   16   16   16    3   16   16    3   16   16    2   16   16   16   16   16
     + TT + UU + VV 
      ---  ---  ---  
       16   16   16

In the formula,

F: = the number of users that are defined to RACF®
G: = the number of groups that are defined to RACF
H: = the number of data sets that are defined to RACF
I: = the number of general resources that are defined to RACF
J: = the number of user CICS® segments
K: = the number of user CSDATA segments
L: = the number of user DCE segments
M: = the number of user DFP segments
N: = the number of user EIM segments
O: = the number of user KERB segments
P: = the number of user LANGUAGE segments
Q: = the number of user LNOTES segments
R: = the number of user PROXY segments
S: = the number of user NDS segments
T: = the number of user NETVIEW segments
U: = the number of user OMVS segments
V: = the number of user OPERPARM segments
W: = the number of user OVM segments
X: = the number of user TSO segments
Y: = the number of user WORKATTR segments
Z: = the number of group CSDATA segments
AA: = the number of group DFP segments
BB: = the number of group OMVS segments
CC: = the number of group OVM segments
DD: = the number of group TME segments
EE: = the number of data set DFP segments
FF: = the number of data set TME segments
GG: = the number of general resource ALIAS segments
HH: = the number of general resource CERTDATA segments
II: = the number of general resource CFDEF segments
JJ: = the number of general resource DLFDATA segments
KK: = the number of general resource EIM segments
LL: = the number of general resource ICTX segments
MM: = the number of general resource KERB segments
NN: = the number of general resource PROXY segments
OO: = the number of general resource SESSION segments
PP: = the number of general resource STDATA segments
QQ: = the number of general resource SSIGNON segments
RR: = the number of general resource SVFMR segments
SS: = the number of general resource TME segments
TT: = the number of general resource CDTINFO segments
UU: = the number of general resource SIGVER segments
VV: = the number of general resource ICSF segments

Note:

The divisor of 16 is used in most cases because, in most cases, approximately 16 profiles (or segments) fit in one 4096-byte block. However, the profile (or segment) size is variable depending upon factors such as installation data, the number of users in a group, and the number of entries on a data set or resource access list. You might want to replace the divisor 16 in one or more factors with 15 or less if the profiles (or segments) are longer than 256 bytes on the average. Because digital certificates are often 1K to 2K bytes in size, a divisor of 3 is used for the CERTDATA segments. Because OMVS segments are large, a divisor of 8 is used for the user and group OMVS segments. A divisor of 2 is used for PROXY segments, and 3 for EIM segments, because these segments are also large.
Set the values for Q, S, U, and BB to zero if your database is using stage 3 of application identity mapping. At this stage, RACF no longer maintains mapping profiles that correspond to alias index entries in the LNOTES, NDS, or OMVS segments.