Common problems and considerations

If you define special classes in the class descriptor table, you might encounter some common problems.

Common problems that could occur as a result of defining special classes in the class descriptor table (CDT) follow:

• A class is not defined in the CDT.

  This results in a return code of 4 (profile not found) from the RACF access control module.

• If a class is defined in the static CDT, there are incorrect linkage editor procedures from the CDT.
• If a class is defined in the static CDT, it is link-edited properly but a re-IPL has not occurred to pick up the changes.
• If a class is defined in the dynamic CDT, the CDTINFO class was not RACLISTed or refreshed to pick up the changes.
• Single-subsystem scope class names are being used and a new subsystem is using the RACF access control module before classes for the subsystem have been defined.
• Messages IRR900A, IRR901A, IRR902A, and IRR903A are issued because the RACF access control module cannot initialize correctly.
  1. Check to see if Db2 classes are active.
  2. Determine if and why RACLISTing of classes is failing in the module by examining RACROUTE REQUEST=LIST return and reason codes.
  3. Check to see if any other required resources (such as GETMAIN, for example) are obtainable.