z/OS Cryptographic Services ICSF Application Programmer's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Usage Notes

z/OS Cryptographic Services ICSF Application Programmer's Guide
SA22-7522-16

Unless otherwise noted, all String parameters that are either written to, or read from, a TR-31 key block will be in EBCDIC format. Input parameters are converted to ASCII before being written to the TR-31 key block and output parameters are converted to EBCDIC before being returned (see Appendix G. EBCDIC and ASCII Default Conversion Tables). TR-31 key blocks themselves are always in printable ASCII format as required by the ANSI TR-31 specification.

Note that the Padding Block, ID “PB" is not allowed to be added by the user. A Padding Block of the appropriate size, if needed, will be added when building the TR-31 key block in TR-31 Export. If the TR-31 Export callable service encounters a padding block in the optional block data, an error will occur.

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

Table 120. TR-31 Optional Data Build required hardware
ServerRequired cryptographic hardwareRestrictions

IBM eServer zSeries 900

None
IBM eServer zSeries 990

IBM eServer zSeries 890

None
IBM System z9 EC

IBM System z9 BC

None
IBM System z10 EC

IBM System z10 BC

None
z196None

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014