Re: DSMSERV UNLOADDB on S/390 running TSM 4.1.3
2001-04-10 08:14:07
Subject: |
Re: DSMSERV UNLOADDB on S/390 running TSM 4.1.3 |
From: |
"Chibois, Herve" <Chibois_H AT ADMIRAL DOT FR> |
Date: |
Tue, 10 Apr 2001 14:15:45 +0200 |
Hi Niklas,
give me the command you typed for unloading your DB.
Normally, if you specify scratch=yes, either with a tape devc
or a file one, TSM will allocate one volume, then another...
$ dsmserv unloaddb devc=DLTCLASS scratch=YES
check how many mount points are available at the same time in your devc
sned me your log offline if you want
rv
> -----Message d'origine-----
> De : Nilsson Niklas [mailto:ninil AT WMDATA DOT COM]
> Envoyé : mardi 10 avril 2001 11:22
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : DSMSERV UNLOADDB on S/390 running TSM 4.1.3
>
>
> Hi!
>
> Has anybody had problem doing a unloaddb on an S/390 system
> running 4.1.3???
> We are trying to do a unload to tape but when the tape get
> full, the TSM
> don't mount next tape.
> Tried to do this to 3390-disc but got the same problem , when
> the disc get
> full , "he" unmounts
> the disc but never mounts the next one.
> There is no problem if you do an export to a deviceclass=file
> or tape when
> server is up and running.
>
> Regards
> Niklas
>
|
|
|