Okay, after spending more than a few seconds on this, I think my answer is that
we use the SETSYS USERUNITTABLE parm. This specifies ATL.
Then we have a couple of other SETSYS parms
SETSYS
USERUNITTABLE(ATL)
SETSYS
TAPEUTILIZATION(
UNITTYPE(ATL) PERCENTFUL(97))
SETSYS
UNITNAME(ATL)
SETSYS
TAPEMIGRATION(ML2TAPE(TAPE(ATL)))
I think this is where I have to change the process.
>From what I was told we need to add a new IODF for the 3592 drives for E05.
>Then add that Esoteric to DFHSM.
I am still researching.
Lizette
>
>> Why do you think HSM is not letting your tapes use the hardware
>> encryption?
>> dd keller
>>
>>
>>
>>
>>
>>
>>
>>
>> Sorry, I should have included
>>
>> z/OS V1.9 RSU0902
>> Using TS3500 with 1120 E05 tape drives.
>>
>> We would like to be able to encrypt the DFHSM Mig tapes. We prefer
>using
>> our DATACLAS but I am not sure DFHSM is letting it happen.
>>
>> We are using this ACS code for all of our customer backup tape data so
>it
>> can be sent offsite incase of a DR. However, we want to include the
>DFHSM
>> tapes as well in the encryption process.
>>
>> Lizette
>>
>>
>> >
>> >Depends on who(m) you want to do the encryption. DFHSM or the Tape
>> Drives.
>> >
>> >See the ENCRYPT keyword on the DUMPCLASS definitions.
>> >
>> >BTW, AFAIK, this is not available for DFHSM BACKUP or MIGRATION.
>> >IIRC, this came in about the z/OS 1.7 time frame via an APAR ( I
>wasn't
>> able to locate it w/a quick search).
>> >
>> >HTH,
>> >
>> ><snip>
>> >I am struggeling through the 2000 page hsm,dss, and ... manual.
>> >
>> >Is there a parm in DFHSM to tell him we will be using encryption on
>his
>> tapes?
>> >
>> >I have an acs routine currently that says if the DSN = HSM.HMIG.*
>then
>> Dataclas=ENCRYPT
>> ></snip>
>> >
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
