The context and credential handles used by these services are not the same as the context and credential handles used by the GSS-API C functions and cannot be used interchangeably. The input and output tokens used by these functions, however, are compatible with the input and output tokens used by the GSS-API C functions, which means that a token created by a R_GenSec service can be processed by a GSS-API C functions and vice versa.

All references to addresses in the description of this callable service are considered to be 4 bytes in length for AMODE 31 callers and 8 bytes for AMODE 64 callers.

Storage allocations performed by this service will be in the home address space and will be owned by the task issuing the call to R_GenSec. It is up to the caller to free any storage that is allocated and returned to the caller.

Any GSS-API error code which can be generated by the IBM® Kerberos runtime could be returned for the major and minor status code parameters. Refer to the messages and codes topic in the z/OS Integrated Security Services Network Authentication Service Administration for a description of the various error codes. Refer to the GSS-API function descriptions in the z/OS Integrated Security Services Network Authentication Service Programming for a description of the GSS-API functions, associated input and output parameters and status codes.

Status codes:

Bit 0							7 8	

15 16

31