IBM GC28-1920-01 Application Development Considerations, Support, Servers, 01yydddF, Year, Racf

Chapter 10. Application Development Considerations

Application development is the process of planning, designing, and coding application programs that invoke RACF functions. This section highlights ne support that might affect application development procedures:

Ÿ	Year	2000	support
Ÿ	OS/390	OpenEdition		DCE	Application Servers
Ÿ	Changes	to	the	class	descriptor table

ŸProgramming interfaces

Year

2000 Support

RACF provides a date conversion routine, IRRDCR00. Programs can call

IRRDCR00

to

convert

a RACF 3-byte packed decimal dateyydddF inintothe form

a 4-byte packed

decimal

dateccyydddin theF, wherefoccm

is

00

for

dates in

the

range 1971-1999 and

01

for

dates in

the range

2000-2070.

The

routine

re

date in

the

form:

00 yydddF ifyy is

71

or

higher

01yydddF

ifyy is

less

than

71

For

more

information

on

IRRDCR00, OS/390see

Security

Server

(RACF)

Macros

and

Interfaces.

OS/390

OpenEdition DCE

Application

Servers

OS/390 OpenEdition has two fundamental types of application servers:

ŸMultithreaded applications

Ÿ Single threaded applications

A multithreadedapplication has multiple sequential flows of control. In a multithreaded application, more than one unit of work at a time is pr server application.

A single threadedapplication has one sequential flow of control. In a sin threaded application, one unit of work is processed at a time by server.

OS/390 OpenEdition provides an S/390 assembler callable service, the pthread_security_np service, and support through the C run time libra

support enablesunauthorized(the unauthorizedterm refers to applications that a not APF-authorized and do not run in supervisor state or in a system protection key) multithreaded applications to create and delete a RA fashion that is mediated and controlled by the MVS OpenEdition kernel

The pthread_security_np service enables multithreaded applications to the security environment of a thread, meaning that the thread can e different RACF identity than the server. If the server customizes t for the client with the client's RACF identity, any resource access RACF-protected resources are made using the client's RACF identity and authorizations.

 Copyright IBM Corp. 1994, 1996 51