Actually, "maxdrv_dsmserv" should only be used to define those drives
you can not currently define.  Halt the server once the drives are
defined and then   re-invoke your original "dsmserv" and continue your
operation.   The validation was only done during DEFINE and UPDATE
drive time.



---aloes <aloes AT ACORUS DOT FR> wrote:
>
>
> Hi Stanley,
> My apologise, levels are :
> Command line interface : V3.1.0.3
> Server                          : V3.1.1.1
> and the duck is still alive !
> R. Spieth
> aloes AT acorus DOT fr
>
>
********************************************************************************
> This is a bug in 3.1.0.2 level.  Please update to 3.1.1.1 level.   The
> fixes can be obtained by ftp to index.storsys.ibm.com
>
> regards,
> Stanley
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
*************************************************************************************
> Pb description :
> ADSM with STK9710 - 6 drives.
> No problem to define drives 1 to 4, we can use them with ADSM.
> The define drive for the fifth and sixth drive failed with msg :
> ANR8366E invalid parm
> ANR8101   RC=3
>
> for ACSLS these two drives are up and running (no pb with a TAR and
other application)
>
> Did some body experience such pb ? if yes, is there a way to valid
this define ?
> Thanks for your help.
>
> R. Spieth
> aloes AT acorus DOT fr
>

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com