z/OS Cryptographic Services System SSL Programming
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Building a z/OS System SSL application

z/OS Cryptographic Services System SSL Programming
SC14-7495-00

  1. Write the System SSL source program (see Writing a System SSL source program).
  2. Compile your System SSL source program using the DLL compiler option.
  3. Include the /usr/lib/GSKSSL.x or /usr/lib/GSKSSL64.x sidedeck in the prelink or bind step input.

    If using the Certificate Management APIs, include either the /usr/lib/GSKCMS31.x or /usr/lib/GSKCMS64.x sidedeck in the prelink or bind step input.

  4. Build a key database file or z/OS® PKCS #11 token using the gskkyman utility or create a SAF key ring or PKCS #11 token using the RACDCERT command. The name of the key database file, z/OS PKCS #11 token, or SAF key ring must match the name you specified as the GSK_KEYRING_FILE on the gsk_attribute_set_buffer() API. You need the name of the key database file, z/OS PKCS #11 token, or SAF key ring and, for key database files, either the password associated with the key file or the stash file name. The password must match the password specified on GSK_KEYRING_PW on the gsk_attribute_set_buffer() API or must be set to NULL if using a SAF key ring or z/OS PKCS #11 token. Note that the password is case-sensitive. See Certificate/Key management for information about how to create a key database file, SAF key ring, or z/OS PKCS #11 token.
Parent topic: Writing and building a z/OS System SSL application

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014