That's what we will be doing, but since we are not converting this to STK
for a while we were just trying to get all the esoterics in place. And we
don't want to force JCL changes to the users. This brings me to my next
question isn't there a way to only have tape units defined to the default
Currently most of our HSM work is going to an IBM virtual tape system.
We
are in the process of migrating off of IBM and going to STK. To get a
jump on this we decided we would add the STK Virtual Tape drives to the
Esoteric that's currently used by for the IBM VTS. When we did this HSM
Lo
Check out the text in APAR's OA11362, OA13098, and OA11603.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of John Benik
Sent: Monday, November 13, 2006 3:24 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: ARC0103I when adding STK VSM to virtual
These are virtual tapes we are talking about.
You can't mix device types in the same esoteric defined to HSM. I've
run into issues at DR with 9840A / 9840B mixture. Do you know what
CDR (configuration data) returns? I think ShowMVS and MXI can tell you.
I don't know what your IBM VTS emulat
The higher density cartridges are physically compatable with the two
machines,
But the data are recorded in an incompatable format. i.e. IBM cannot
read STK and
Vice-versa. I believe you will need more than on esoteric for this
process.
Try SETSYS USERUNITTABLE
Currently most of our HSM work is
Currently most of our HSM work is going to an IBM virtual tape system. We
are in the process of migrating off of IBM and going to STK. To get a
jump on this we decided we would add the STK Virtual Tape drives to the
Esoteric that's currently used by for the IBM VTS. When we did this HSM
had
6 matches
Mail list logo
