I'm not sure if this applies in os/390 as it does in AIX, but did you:
- specify enable3590 yes in dsmserv.opt
- create new 3590 device class
- checkin new libvols with status=scratch and devt=3590





Jim Kirkman <jmk AT EMAIL.UNC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/18/03 03:09 PM
Please respond to jim_kirkman


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Native 3590 drives


So, in our 3494 tape robot, which is connected to an OS\390 system
running 2.10 and TSM 4.1.4.2 we installed 3 (the 4th is on the way)
native magstar drives this past weekend.

The plan has been to leave our TSM configuration as is and, by changing
our dfsms routines to point to the new media type, start by sending our
archives to the 3590K tapes. Well, it didn't work. We get ANR5336E
'volume SCRTCH must be read-only on 3590 device. This leads me to
believe that TSM somehow knows that these drives need to be assigned to
the 3590 device class as opposed to any of the existing cartridge d.c.
Oh well, I guess it should have been obvious given the fact that there
are two distinct tape device classes. I would assume it is because of
how the data is written to the tape?

So, are we forced to set up a whole new structure, complete with a new
prefix, or are there any alternative approaches?


--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884