Figure 11. | Changed Exits for RACF |
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
Exit | Description |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Support |
|
| |||
|
|
|
|
|
|
|
|
|
| ||||||||||||
ICHRCX01 | For | unauthenticated | client | ACEEs, | the | RACROUTEOS/390 |
|
| |||||||||||||
ICHRCX02 | REQUEST=AUTH | preprocessing |
| and |
|
|
|
| OpenEdition |
| |||||||||||
| postprocessing | exits |
| are | invoked |
| for | bothDCE | the | client |
| ||||||||||
| ACEE | and | the | server | ACEE. For | more | information, |
|
| ||||||||||||
| see | “Effects | of | OS/390 | OpenEdition | DCE | Support |
|
| ||||||||||||
| on ICHRCX01, ICHRCX02, and IRRSXT00” on |
|
|
|
| ||||||||||||||||
| page | 35. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||
ICHRDX01 | Processing | of | a |
| RETPD | value | specified |
| viaAPAR the |
|
| ||||||||||
| RACROUTE | REQUEST=DEFINE |
| preprocessing |
|
|
| OW13967 |
|
| |||||||||||
| exit has changed. For more information, see |
|
| ||||||||||||||||||
| “RACROUTE | REQUEST=DEFINE |
| Preprocessing |
|
|
|
|
|
|
| ||||||||||
| Exit | (ICHRDX01)” |
| on |
| page 36. |
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
| |||||||||||||
IRRSXT00 | For | the | R_dceinfo | and | R_dceruid | callableOS/390services: |
| ||||||||||||||
| Ÿ | IRRSXT00 | must | be | capable | of |
|
|
|
| OpenEdition |
| |||||||||
| executing | in |
|
| |||||||||||||||||
|
| either | problem | or | supervisor | state. | DCE |
|
|
| |||||||||||
|
|
|
|
|
| ||||||||||||||||
| Ÿ | IRRSXT00 | must | not | expect | to | receive control | in |
| ||||||||||||
|
| a | system | storage | protection | key |
|
|
| ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Macros
Figure 12 lists changes | to | RACF macros | for | OS/390 Release 2. These ch | |||||||
are |
|
|
| ||||||||
|
|
|
|
|
|
|
|
| |||
Figure 12. | Changed Macros for RACF |
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
| |
Macro | Description |
|
|
|
|
|
| Support |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
ICHEINTY | The | ICHEINTY | macro | can | be | used | to | renameRACF | 1.10 |
| |
| profiles in the FILE and DIRECTRY | classesfor. TheVM |
| ||||||||
| existing keywords RENAME, NEWNAME, and |
|
|
|
| ||||||
| NEWNAMX | can now be | used | to | rename | profiles |
|
| |||
| when | specifying | CLASS=FILE | or |
|
|
|
|
| ||
| CLASS=DIRECTRY. |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| ||||
RACROUTE | The | RACROUTE | REQUEST=DEFINE | macro can | RACF | 1.10 |
| ||||
| be used to rename resources in the newforFILEVM and |
| |||||||||
| DIRECTRY classes. The existing keywords |
|
| ||||||||
| NEWNAME and NEWNAMX can now | be | used | to |
|
|
| ||||
| rename resources when specifying CLASS=FILE or |
|
| ||||||||
| CLASS=DIRECTRY. |
|
|
|
|
|
|
|
|
| |
| For more information, OS/390see Security Server |
|
| ||||||||
| External Security Interface (RACROUTE) Macro |
|
| ||||||||
| Reference. |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
Messages
The | messages that have been added or changed in | RACF | for | OS/390 Re |
are | listed below. Compare the message identifiers | and | the | correspond |
text with any automated operations procedures your installation uses whether updates are required.
Chapter 3. Summary of Changes to RACF Components for OS/390 17Release 2
