Command processing changes

Before RACF® 2.2, when a RACF TSO command was issued, control was passed directly to the appropriate command processor.

To make this happen, RACF included an entry similar to the following for ADDGROUP in the linkage editor statements for each RACF command.

   INCLUDE AOSBN(ICHCAG00)
   INCLUDE AOSBN(other modules)
     :
   ALIAS AG,ADDGROUP
   ENTRY ICHCAG00
   SETCODE AC(1)
   NAME ICHCAG00(R)

Note: AG or ADDGROUP is the alias name by which the command is issued by a user and ICHCAG00 is the full name of the command by which it is invoked internally.

In RACF 2.2 and OS/390® Security Server (RACF), the entry in the linkage editor statements for most RACF commands look like this:

   INCLUDE AOSBN(ICHCAG00)
   INCLUDE AOSBN(other modules)
     :
   ENTRY ICHCAG00
   NAME ICHCAG00(R)

Note: The aliases are not present.

The aliases are removed from each individual command and placed in a new entry for IRRENV00.

   INCLUDE AOSBN(IRRENV00)
   INCLUDE AOSBN(other modules)
   ENTRY IRRENV00
   ALIAS AD,ADDSD
   ALIAS AG,ADDGROUP
   ALIAS other commands
     :
   SETCODE AC(1)
   NAME IRRENV00(R)
   etc.

IRRENV00 receives control before each command processor. If the AT or ONLYAT keywords were not specified, IRRENV00 invokes the appropriate command processor using its full name. When the command processor returns control, IRRENV00 determines if automatic direction is required for the command. If so, a work item is sent to the RACF subsystem address space. If the AT or ONLYAT keywords were specified, IRRENV00 sends the command to the RACF subsystem address space for processing.