Lizette Koehler wrote:
>The 3295-1 will only create unencrypted tapes. And due to the way DFHSM
works, you cannot chang the TAPECOPY, for instance, to 3592-2 and leave
ML2 at 3592-1. So both parts, ML2 and TAPECOPY, need to be the same
device type which in our case is the 3592-2 device type.
Sure,
The 3295-1 will only create unencrypted tapes. And due to the way DFHSM works,
you cannot chang the TAPECOPY, for instance, to 3592-2 and leave ML2 at 3592-1.
So both parts, ML2 and TAPECOPY, need to be the same device type which in our
case is the 3592-2 device type.
Lizette
>
>Lize
Lizette Koehler wrote:
>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 [ ... snipped ... ]
Sorry Lizette, but could you be very kind to tell us what you wanted to write
in the sentence starting
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-
4 matches
Mail list logo
