SAF may be invoked to verify the caller is authorized to use this callable service, the key label, or internal secure key tokens that are stored in the CKDS or PKDS.

If the service is executed on the Cryptographic Coprocessor Feature, the generated internal DATA key token is marked according to the system default algorithm.

The hardware configuration sets the limit on the modulus size of keys for key management; thus, this service will fail if the RSA key modulus bit length exceeds this limit.

Specification of PKA92 with an input NOCV key-encrypting key token is not supported.

Use the PKA92 key-formatting method to generate a key-encrypting key. The service enciphers one key copy using the key encipherment technique employed in the IBM Transaction Security System (TSS) 4753, 4755, and AS/400 cryptographic product PKA92 implementations (see PKA92 Key Format and Encryption Process). The control vector for the RSA-enciphered copy of the key is taken from an internal (operational) DES key token that must be present on input in the RSA_enciphered_key variable. Only key-encrypting keys that conform to the rules for an OPEX case under the key generate service are permitted. The control vector for the local key is taken from a DES key token that must be present on input in the local_enciphered_key_token variable. The control vector for one key copy must be from the EXPORTER class while the control vector for the other key copy must be from the IMPORTER class.

The following table shows the access control points in the ICSF role that control the function of this service.

When the WRAP-ECB or WRAP-ENH keywords are specified and the default key-wrapping method setting does not match the keyword, the Symmetric Key Generate - Allow wrapping override keywords access control point must be enabled.

This table lists the required cryptographic hardware for each server type and describes restrictions for this callable service.

Table 103. Symmetric key generate required hardware

Server	Required cryptographic hardware	Restrictions
IBM zSeries 900	Cryptographic Coprocessor Feature	ICSF routes this service to a PCI Cryptographic Coprocessor if one is available on your server. This service will not be routed to a PCI Cryptographic Coprocessor if the modulus bit length of the RSA public key is less than 512 bits. RSA keys with moduli greater than 1024-bit length are not supported. Secure AES keys are not supported. DES, ENH-ONLY, USECONFG, WRAP-ENH, WRAP-ECB, and SHA-256 keywords not supported.
	PCI Cryptographic Coprocessor	Use of keyword PKA92 or PKCSOAEP requires the PCI Cryptographic Coprocessor. PKCSOAEP uses the SHA-1 hash method. RSA keys with moduli greater than 2048-bit length are not supported. Secure AES keys are not supported. DES, ENH-ONLY, USECONFG, WRAP-ENH, WRAP-ECB, SHA-1, and SHA-256 keywords not supported. PKCSOAEP with the SHA-256 hash method is not supported.
IBM zSeries 990 IBM zSeries 890	PCI X Cryptographic Coprocessor Crypto Express2 Coprocessor	The generated internal DATA key will not have any system encryption algorithm markings. RSA keys with moduli greater than 2048-bit length are not supported. Secure AES keys are not supported. ENH-ONLY, USECONFG, WRAP-ENH, WRAP-ECB, and SHA-256 keywords not supported. PKCSOAEP with the SHA-256 hash method is not supported.
IBM Systems z9 EC IBM System z9 BC	Crypto Express2 Coprocessor	The generated internal DATA key will not have any system encryption algorithm markings. RSA key support with moduli within the range 2048-bit to 4096-bit requires the Nov. 2007 or later licensed internal code (LIC). Secure AES key support requires the Nov. 2008 or later licensed internal code (LIC). ENH-ONLY, USECONFG, WRAP-ENH, WRAP-ECB, and SHA-256 not supported. PKCSOAEP with the SHA-256 hash method is not supported.