09.07.2015 Views

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

REPRODATAKEYFILE(ddname)identifies a data set that contains the plaintext data encrypting key. Forddname, substitute the name of the JCL statement that identifies the dataencrypting key data set.Abbreviation: DKFILEDATAKEYVALUE(value)specifies the 8-byte value to be used as the plaintext data encrypting key toencipher the data.Value can contain 1-to-8 EBCDIC characters or 1-to-16 hexadecimalcharacters coded X'n'. Value must be enclosed in single quotation marks ifit contains commas, semicolons, blanks, parentheses, or slashes. A singlequotation mark must be coded as two single quotation marks. With eitherEBCDIC or hexadecimal representation, value is padded on the right withblanks (X'40') if it is fewer than 8 characters.Abbreviation: DKVSHIPKEYNAMES(keyname[ keyname...])supplies the 1-to-8 character key name of one or more external file keys to beused to encipher the data encrypting key. Each key name and itscorresponding enciphered data encrypting key is listed in SYSPRINT, but is notstored in the target data set header. The primary use <strong>for</strong> this parameter is toestablish multiple enciphered data encrypting keys to be transmitted to otherlocations <strong>for</strong> use in deciphering the target enciphered data set. This parameteris valid only when INTERNALKEYNAME or EXTERNALKEYNAME isspecified.Abbreviation: SHIPKNSTOREDATAKEY|N<strong>OS</strong>TOREDATAKEYspecifies whether the enciphered data encrypting key is to be stored in thetarget data set header. The key used to encipher the data encrypting key isidentified by INTERNALKEYNAME or EXTERNALKEYNAME. Thisparameter is valid only when INTERNALKEYNAME orEXTERNALKEYNAME is specified. If the enciphered data encrypting key isstored in the data set header, it does not have to be supplied by the user whenthe data is deciphered.Restriction: A data encrypting key enciphered under the keys identified bySHIPKEYNAMES cannot be stored in the header. There<strong>for</strong>e, you might want toavoid using STOREDATAKEY and SHIPKEYNAMES together because thiscould result in storing header in<strong>for</strong>mation unusable at some locations.STOREDATAKEYspecifies that the enciphered data encrypting key is to be stored in thetarget data set header.Abbreviation: STRDKN<strong>OS</strong>TOREDATAKEYspecifies that the enciphered data encrypting key is not to be stored in thetarget data set header. The keyname and its corresponding enciphered dataencrypting key is listed in SYSPRINT.Abbreviation: NSTRDKSTOREKEYNAME(keyname)specifies whether to store a keyname <strong>for</strong> the key used to encipher the dataencrypting key in the target data set header. The specified keyname must be316 z/<strong>OS</strong> <strong>V1R6.0</strong> <strong>DFSMS</strong> <strong>Access</strong> <strong>Method</strong> <strong>Services</strong> <strong>for</strong> <strong>Catalogs</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!