Michael Knutson asks:

> ** How can we change the dataset name prefix for devclass Cartridge and
> devtype CARTRIDGE ???? We want to change ADSM to ADSM.P so that tape DSNs
> follow our "standard."

You can not change the prefix for a devclass of type CARTRIDGE. The printed
Admin Reference incorrectly states that you can change this, but if you run
the HELP UPDATE DEVCLASS command from an ADSM command line admin, you'll see
that the PREFIX option has been removed from the syntax.

You can, however, specify a multi-node PREFIX with DEFINE DEVCLASS, i.e.:

   DEF DEV MYDEV DEVTYPE=CARTRIDGE PREFIX=ADSM.P

The ability to enter multi-node prefix names on MVS was introduced in a PTF
to the V2 server (around 2.1.0.7 or later). HOWEVER, the total PREFIX length
is still restricted to 8 characters, including the dots. Thus, the following
are legal prefixes:

      ADSM.P
      DSM.PROD
      DSM.PL.A

The following is NOT legal:

      ADSM.PROD     <== too many characters

Actually, even if you could update the prefix, I would normally advise against
it. ADSM does not record the data set names of each cartridge in it's
inventory; rather, this is the prefix that it will use for *all* cartridges
with that device class. Thus if you had already created several cartridges
with a prefix of ADSM (i.e. ADSM.BFS), then changed the prefix to ADSM.P,
ADSM would call for existing cartridges as ADSM.P.BFS. You would then get a
data set name conflict, and you would be unable to access the existing
cartridges (of course, new tapes would also be created with ADSM.P, and they
would be okay).

So even if you could update the prefix, you probably wouldn't want to. And if
you don't have any cartridges defined with that devclass, you can simply
delete the devclass (I think you'll have to delete any storage pools also
created with that devclass), and redefine it with the desired prefix.

If you already have cartridges with that data set name prefix in it, then you
can create a new devclass with the desired prefix, create a new storage pool
that uses that devclass, then use storage pool migration or MOVE DATA to move
data from the existing cartridges to the new pool (with the new devclass
prefix). Once the old storage pool is empty, you can delete it and it's
devclass.

Hope this helps,

Andy Raibeck
ADSM Level 2 Support