For more information on the convert_id_np (BPX1CID) callableOS/390service, s OpenEdition Programming: Assembler Callable Services Reference. The C
language support for the __convert_id_np() OS/390is discussedR2 C/C++ in
New Application Authorization | Service |
|
|
|
|
|
|
|
|
|
|
|
A DCE application server on OS/390 can | use | DCE | security | services | for | a | ||||||
control to resources that | are owned | by | the | application | server. As | a | ||||||
the application developer can use | RACF | for | access | control | for | the | se | |||||
that are managed by the application server. |
|
|
|
|
|
| ||||||
Consider | that application | servers | that | use |
| DCE | services | exclusively | on | |||
the most portable to platforms that support | DCE. If | portability | is | no | ||||||||
concern and the application developer wishes to centralize access co | ||||||||||||
information in RACF, the application | developer | can consider | using | the |
| |||||||
auth_check_resource_np service. |
|
|
|
|
|
|
|
|
|
| ||
Through OS/390 OpenEdition MVS, a new a callable service
auth_check_resource_np (BPX1ACK) enables application servers to invoke R authorization services. This callable service is also supported by th library through the __check_resource_auth_np() function call. This ser application servers to perform authorization requests for resources t to RACF general resource classes.
For more information on the auth_check_resource_np callableOS/390service, s OpenEdition Programming: Assembler Callable Services Reference.
Changes to the Class Descriptor Table
The maximum length of profile names has changed for the following clas
ŸINFOMAN
ŸGINFOMAN
ŸJCICSJCT
ŸKCICSJCT
This change might require changes to customer code which uses these
ŸRACROUTE REQUEST=FASTAUTH
Ÿ RACROUTE | REQUEST=AUTH, | DEFINE, or EXTRACT, if the ENTITY keyword |
is used | instead of | ENTITYX |
IBM products should not need changes, because their usage of these compatible with this change.
Programming Interfaces
For a summary of changes to the programming interfaces for RACF for Release 2, see:
Ÿ “Class Descriptor Table (CDT)” on page 13
Ÿ “Data Areas” on page 16
Ÿ “Exits” on page 16
Chapter 10. Application Development Considerations53
