Okay, After a few more days of playing and reading, we came upon the answer.
For DFHSM you need to do the same thing to ML2 tape as TAPECOPY tape. Since we had only be changing the output device on one - it was not working. Once we changed the device definition on both ML2 and TAPECOPY to 3592-2 it worked. The 3592-1 So, we are now having DFHSM ML2 and TAPECOPY tapes encrypted successfully by using the correct device type and the coding in the ACS for this process to use the appropriate dataclas for these dataset names. Lizette ---------------------------------------------------------------------- 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
