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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

REPROthe name the key is known by on the system where the REPRO DECIPHER isto be per<strong>for</strong>med. This keyname must be the same one specified inINTERNALKEYNAME if REPRO DECIPHER is to be run on the same system.If REPRO DECIPHER is run on a different system, the specified keyname canbe different from the one specified in INTERNALKEYNAME orEXTERNALKEYNAME.This parameter is valid only when INTERNALKEYNAME orEXTERNALKEYNAME is specified. If the keyname is stored in the data setheader, it does not have to be supplied by the user when the data isdeciphered.Restriction: Keyname values identified by the SHIPKEYNAMES parametercannot be stored in the header. There<strong>for</strong>e, you might want to avoid usingSTOREKEYNAME and SHIPKEYNAMES together because this could result instoring header in<strong>for</strong>mation unusable at some locations.Abbreviation: STRKNUSERDATA(value)specifies 1-to-32 characters of user data to be placed in the target data setheader. For example, this in<strong>for</strong>mation can be used to identify the securityclassification of the data.Value can contain 1-to-32 EBCDIC characters. If value contains a specialcharacter, enclose the value in single quotation marks (<strong>for</strong> example,USERDATA('*CONFIDENTIAL*')). If the value contains a single quotationmark, code the embedded quotation mark as two single quotation marks (<strong>for</strong>example, USERDATA('COMPANY''S')).You can code value in hexadecimal <strong>for</strong>m, where two hexadecimal charactersrepresent one EBCDIC character. For example,USERDATA(X'C3D6D4D7C1D5E8') is the same as USERDATA(COMPANY).The string can contain up to 64 hexadecimal characters when expressed in this<strong>for</strong>m, resulting in up to 32 bytes of in<strong>for</strong>mation.Abbreviation: UDATADECIPHERspecifies that the source data set is to be deciphered as it is copied to the targetdata set. The in<strong>for</strong>mation from the source data set header is used to verify theplaintext deciphered data encrypting key supplied, or deciphered from thein<strong>for</strong>mation supplied, as the correct plaintext data encrypting key <strong>for</strong> thedecipher operation.Abbreviation: DECPHRDATAKEYFILE(ddname) | DATAKEYVALUE(value) | SYSTEMKEYspecifies whether you, PCF, or ICSF manages keys privately.DATAKEYFILE(ddname)specifies that the key is to be managed by you, and identifies a data setthat contains the private data encrypting key that was used to encipher thedata. For ddname, substitute the name of the JCL statement that identifiesthe data set containing the private data encrypting key.Abbreviation: DKFILEDATAKEYVALUE(value)specifies that the key is to be managed by you, and supplies the 1- to8-byte value that was used as the plaintext private data encrypting key toencipher the data.Chapter 30. REPRO 317

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

Saved successfully!

Ooh no, something went wrong!