Well that's interesting.
I tried your command, just to be sure - when I try to schedule what you sent
below (changing the name to my library name), I still get  ANR2755E,
SPECIFIED COMMAND NOT AVAILABLE FOR SCHEDULING.",
which is why I wrote a script in the first place.

Perhaps it's releated to the type of library?
What server platform are you?

> -----Original Message-----
> From: Rik Foote [SMTP:Rik_Foote AT WESTPACTRUST.CO DOT NZ]
> Sent: Tuesday, March 21, 2000 2:27 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Fail to Schedule Daily Tape Checkin
>
> Not True!!!
>
> I schedule two CHECKIN commands every day for each of our two 10-slot SCSI
> libraries:
>
> CHECKIN LIBV STKR0 SEARCH=YES STATUS=SCRATCH
> and
> CHECKIN LIBV STKR0 SEARCH=YES STATUS=PRIVATE
>
> as administrative command schedules on the server.
>
> I am running ADSM 3.1.2.1, so I hope its not a 'feature' I can expect to
> encounter when upgrading?
>
> Rik Foote
> WestpacTrust, New Zealand
>
>
>
> "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU> on 22/03/2000 06:26:57
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Rik Foote/WestpacTrust/NZ)
> Subject:  Re: Fail to Schedule Daily Tape Checkin
>
>
>
>
> There are some commands that aren't eligible for admin scheduling;
> CHECKIN
> is one of them.
>
> However, you can define a server SCRIPT with the CHECKIN command in it;
> then
> you can define an admin schedule where the command is "run scriptname".
>
> ************************************************************************
> Wanda Prather
> The Johns Hopkins Applied Physics Lab
> 443-778-8769
> wanda_prather AT jhuapl DOT edu
>
> "Intelligence has much less practical application than you'd think" -
> Scott Adams/Dilbert
> ************************************************************************