Filter
Top Products
RACF Storage Considerations
This section discusses storage considerations for RACF.
Virtual Storage
Figure 21 estimates RACF virtual storage usage, for planning purposes.
Figure 21 (Page 1 of 2). RACF Estimated Storage Usage
Storage Subpool Usage How to Estimate Size
FLPA RACF service routines, if IMS or CICS is using
RACF for authorization checking
47 000
RACROUTE REQUEST=FASTAUTH and
ICHRTX00 exits
Measure using AMBLIST
PLPA RACF installation exits that are AMODE(24) or
AMODE(ANY)
Measure using AMBLIST
RACF RMODE(24) code 750
RACF service routines, if IMS or CICS is not using
RACF for authorization checking, unless explicitly
removed from SYS1.LPALIB and placed
elsewhere for use in FLPA
47 000
RACROUTE REQUEST=FASTAUTH and
ICHRTX00 exits
Measure using AMBLIST
RACF range table 4 + (number_of_ranges × 45)
EPLPA RACF installation exits that are AMODE(31) Measure using AMBLIST
RACF above-the-line resident modules 875 000
SQA RACF communications vector table and extension 2800
Class descriptor table (CNST) and RACF router
table
7500 + 58 ×
number_of_customer_defined_classes
ESQA RACF data sharing control area 300 (when enabled for sysplex communication)
Class descriptor table (CNSX) (number_of_IBM-defined_classes × 28) +
(number_of_IBM-defined_entries_in_router_table ×
30) + (number_of_customer_defined_classes ×
58) + 26
For Security Server (RACF) Release 2, there are
43 IBM-defined classes and 165 IBM-defined
entries in the router table, so the size of the CNSX
is 6180 + (number_of_customer_defined_classes
× 58). If you install a PTF that adds entries, you
will need to recalculate this number.
LSQA ACEE and related storage
Notes:
1. Applications can place this storage in a
different subpool.
2. Applications can create multiple ACEEs in this
and other storage subpools.
400 + installation_data_length +
terminal_installation_data_length +
application_installation_data + (52 for every 78
temporary datasets, rounded up to the next
multiple of 52)
If the address space has been dubbed an
OpenEdition process, then add: 52 +
(number_of_connected_groups_with_GIDs × 4)
Add 112 bytes if the user has CLAUTH for a class
with a POSIT value over 127.
Formula for average_profile_size:
average_profile_size = 51 + average_installation_data + (average_number_of_access_entries × 9) +
(average_number_of_categories × 2) + (average_number_of_conditional_access_entries × 17)
32 OS/390 V1R2.0 Security Server (RACF) Planning: Installation and Migration