Infostorage Rule Directories (INFODIR)

The INFODIR record indicates which infostorage rule directories are built and made globally resident at CA ACF2 initialization time.
acf2src16
The INFODIR record indicates which infostorage rule directories are built and made globally resident at
CA ACF2
initialization time. The INFODIR record also indicates if the rule sets associated with those directories are made resident and if the residency is global (in common storage) or local (in an address space). The INFODIR record is similar in function to the RESDIR record. While the RESDIR record enables you to specify a code and a type, the INFODIR record lets you specify a code, class, and type. This capability lets you use different class codes for your applications. Migrate RESDIR records to INFODIR records.
Resident directories can also be created by a RACROUTE REQUEST=LIST and GLOBAL=YES or SUBPOOL=(241). When this is done, CA ACF2 reads the appropriate rules into storage. This directory cannot be deleted and remains until the next IPL.
The following lists the record format and field descriptions for INFODIR:
INFODIR TYPESX(
code
-
classtype257,...,code
-
classtype512
)
  • TYPES(
    code
    -
    classtype1,...,code
    -
    classtype256
    )
    Code
    Indicates whether the rule set associated with the directory is made resident, and whether that residency is global or local. The three possible codes are:
    • T
      Rule sets are transient and never are made resident.
    • D
      Rule sets are made resident locally in the user's address space when access to a resource is attempted rather than being made resident in global storage at CA ACF2 initialization time. Locally resident rules are not affected by the F ACF2,REBUILD command. To clear locally resident rules, use the ACF2 SETNORUL command or the address space must come down and back up (or the user must sign off and sign on again.) The rules are reloaded when access to the resource is attempted.
    • R
      Rule sets are made resident in global storage at CA ACF2 initialization time.
      We recommend specifying R for the code; specifying T or D could affect performance since additional I/O to the infostorage database is required for transient or on-demand processing.
CLASS Types
In addition to the TYPES field codes, the following list shows the field classes and the associated record, type, and resource class TYPE code.
  • CLASS(D)
    • Record Type:
      DB2 Resource
    • Type:
      DB2 resource classes BPL, CON, DBS, FNC, JAR, PLN, PRC, ROL, SCH, SEQ, STG, SYS, TBL, TSP, TYP, VAR
  • CLASS(E)
    • Record Type:
      ENTRY SOURCE
    • Type:
      SRC
  • CLASS(F)
    • Record Type:
      EXPRESSION
    • Type:
      EXP
  • CLASS(F)
    • Record Type:
      RECORD
    • Type:
      REC
  • CLASS(P)
    • Record Type:
      PROFILE
    • Type:
      USR GRP ALU CSF XCS ERA KEY PTK SDB SEC DSN
  • CLASS(R)
    • Record Type:
      RESOURCE  
    • Type:
      GSO CLASMAP internal and site defined TYPES xxx
  • CLASS(S)
    • Record Type:
      SCOPE
    • Type:
      SCP
  • Type
    Specifies the pertinent rule set for which a directory is built and made globally resident at
    CA ACF2
    initialization. The
    type
    is the same three-character type code used in the $TYPE control statement of the rule set.
    For example, to create an INFODIR record for DB2 resources, use the following:
    TYPES(R-DSYS,D-DDBS,T-DBPL)
  • R-DSYS
    Specifies that a rule directory is built and loaded into common storage for
    CA ACF2
    for DB2 rules of $TYPE(SYS), and the rules themselves are made globally resident.
  • D
    -
    DDBS
    Specifies that a rule directory is built and loaded into common storage for
    CA ACF2
    for DB2 rules of $TYPE(DBS) and the rules themselves are made resident in an address space upon request.
  • T
    -
    DBPL
    Specifies that a
    rule directory is built and loaded into common storage for
    CA ACF2
    for DB2 rules of $TYPE(BPL), but the rules themselves are never made resident in common storage nor in an address space, but are loaded and unloaded into an address space on a transient basis.
    Regardless of whether a given type of rule set is resident or transient, a directory is built for each type of rule set specified in the INFODIR record. The directory itself is always made globally resident.
    Resident directories are rebuilt at each IPL, at each restart of
    CA ACF2
    , or when the console operator enters the following command:
    F ACF2,REBUILD(type),CLASS(class)
    To use a mask (asterisks) in the $KEY or $SYSID control statement of a resource rule, you must make the directory resident for the given type of rule set.
    Storage utilization is improved when common rules are made globally resident. For example, when 100 users access the same resource, 100 copies of that rule are in LSQA unless the rule is made resident.
  • TYPESX(
    code
    -
    classtype257,...,code
    -
    classtype512
    )
    The TYPESX field is identical to the TYPES field. Both fields allow up to 256 entries and are processed separately. By enabling the TYPES and TYPESX fields, the maximum number of entries that can be specified increases from 256 to 512.
    To activate, issue the following REBUILD command.
    F ACF2,REBUILD(
    xxx
    ),CLASS(
    y
    )
Display the INFORDIR Record
The SHOW RESIDENT and SHOW ACF2 subcommands of the ACF command display the types of resources as specified in the INFODIR record.