These application programming interfaces, or APIs, are superseded by the APIs defined in API reference.

• gsk_free_memory() (see gsk_free_memory())
• gsk_get_cipher_info() (see gsk_get_cipher_info())
• gsk_get_dn_by_label() (see gsk_get_dn_by_label() )
• gsk_initialize() (see gsk_initialize())
• gsk_secure_soc_close() (see gsk_secure_soc_close())
• gsk_secure_soc_init() (see gsk_secure_soc_init())
• gsk_secure_soc_read() (see gsk_secure_soc_read())
• gsk_secure_soc_reset() (see gsk_secure_soc_reset())
• gsk_secure_soc_write() (see gsk_secure_soc_write())
• gsk_srb_initialize() (see gsk_srb_initialize())
• GSKSRBRD() (see GSKSRBRD)
• GSKSRBWT() (see GSKSRBWT)
• gsk_uninitialize() (see gsk_uninitialize())
• gsk_user_set() (see gsk_user_set())

Although use of the deprecated set of APIs in this topic is still supported in z/OS® Version 2 Release 1, make sure that new applications be developed using the set of APIs defined in API reference.

The deprecated APIs are not being explicitly updated to allow utilization of new functionality to be added to System SSL. If an application wants to use new functionality to be added, for example TLS V1.2 protocol, the application must be coded to the SSL APIs in API reference.

In addition, make sure that existing applications are modified to use the set of APIs defined in API reference. Those modified applications should only use the new APIs, and not a mix of the new APIs and these deprecated APIs. Information about migrating your existing application programs to use the new API set can be found in Migrating from deprecated SSL interfaces.