If your tape management system is DFSMSrmm, insertion of tapes happens
differently than CA-1 or CA-TLMS. If the tape isn't defined to the RMM
control dataset (CDS), then RMM adds it to his CDS using the default
insertion catagory (private/scratch) defined for that library. So, to
prevent RMM from adding these tapes, include a REJECT ANYUSE() directive in
the EDGRMMxx startup parmlib member. We have our Magstar tapes labeled with
'M' for mainframe and 'R' for our RS/6000 TSM server(s).
You should also make sure that your checkin command uses the volrange=
keyword. If you for some reason have mainframe tapes that have been inserted
into the library, but haven't been accepted by a 'host', they would be
checked in to TSM and used as scratch, possibly overlaying the existing (if
any) mainframe data. I have created a server script that does the checkin
command and I have this scheduled to run daily.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Allen Barth
Sent: Tuesday, January 30, 2001 11:37 AM
To: [EMAIL PROTECTED]
Subject: Re: shared 3590
Welcome to the world of dueling hosts.....
...been there done that....
this condition is fixed by patching the mainframe. Get a good
understanding of what happens during library insert mode with respect to
the hosts attached, then look for info on CBRUXENT. This module is part of
OAM and provides an exit point for processing before tape entry into the
volcat. We're using CA-1 on the mainframe and they (CA) supply their own
version of the module which looks in the CA-1 db for the tape being
inserted. If the tape had not been defined in CA-1 the the exit sets a
return code which effectively bypasses checkin processing, which is where
the 000F or other categories get assigned. Also be aware of the OS/390
LIBRARY RESET command as there are conditions where the CBRUXENT can get
disabled and then things seem to go whacky again.
You don't mention what platform your TSM server is on, and each one has a
library interface with varying capabilities.
You can not change category codes, eject tapes, etc from the library
manager console.
Hope this helps
Al Barth
Zurich Scudder Investments
Sergio Cherchyk
<scherchyk@BANCOR To: [EMAIL PROTECTED]
IO.COM.AR> cc:
Sent by: "ADSM: Subject: shared 3590
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
01/25/01 09:46 AM
Please respond to
"ADSM: Dist Stor
Manager"
Hi all.
We recently included four new Magstar drives to an existent 3590 library
that is being used in our mainframe environment, to allow us use it also
with our TSM.
We connected and configured it and it seems to be ready for use, but I
cannot manage to check in any tape.
When I try to label the volume ts0001 using
LABEL LIBVOLUME IBM-1 ts0000 CHECKIN=SCRATCH DEVTYPE=3590 OVERWRITE=NO
TSM prompts me to insert the volume into the library. When I do it, the
volume is assigned to the device category 000F (I configured the library
to have a device category of h012d for scratch volumes) and the label
command fails with this message:
01/25/01 11:31:43 ANR8846E Volume TS0001 is assigned to a category
that does
not belong to library IBM-1.
01/25/01 11:31:43 ANR8802E LABEL LIBVOLUME process 641 for library
TS0001
failed.
I tried to manually change the device category through the library
console but I didn't find how to do it (if it is possible at all).
Can anybody help me with this?
Thanks in advance
--
--------------------------------------------
Sergio R. Cherchyk
Arquitectura Tecnológica - Midrange
Banco Río de la Plata S.A. - Grupo BSCH
Mire 480, 2do piso - 1036 Cap. Fed.
Argentina
Tel. (054)-11-4341-1643
Fax. (054)-11-4341-1264
--------------------------------------------
