Hi!
I did test both these parameters scratch=yes/no
I have also tested 1-10 mount points..
One of the run i also specified 3 volumes (scratchtapes) but i got the same
error...
Here is my jcl:
//TSM JOB MSGLEVEL=(1,1),REGION=128M,TIME=1440,CLASS=A,MSGCLASS=H
//SERVER EXEC PGM=ANRSERV,DYNAMNBR=300,TIME=NOLIMIT,
// PARM='/UNLOADDB DEVCLASS=KASS SCRATCH=YES'
//OPT DD DSN=TSM.ANRSERV.OPTIONS,DISP=MOD
//STEPLIB DD DSN=TSM.V41.LINKLIB,DISP=SHR
//DSMAMENG DD DSN=TSM.V41.SANRMSG(ANRMENU),DISP=SHR
//HLPAMENG DD DSN=TSM.V41.SANRHLP(ANRHENU),DISP=SHR
//IMAGES DD DSN=TSM.V41.SANRIMG(WEBSERV2),DISP=SHR
//IDL DD DSN=TSM.V41.SANRIMG(ANRIDL),DISP=SHR
//DSK DD DSN=TSM.DISKLOG,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
/*
-----Ursprungligt meddelande-----
Från: Chibois, Herve [mailto:[EMAIL PROTECTED]]
Skickat: den 10 april 2001 14:16
Till: [EMAIL PROTECTED]
Ämne: Re: DSMSERV UNLOADDB on S/390 running TSM 4.1.3
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:[EMAIL PROTECTED]]
> Envoyé : mardi 10 avril 2001 11:22
> À : [EMAIL PROTECTED]
> 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
>
