Re: Tape hardware resources

[rick baird <rick.baird@xxxxxxxxx>]

thanks, I will!

On Thu, Mar 19, 2009 at 4:05 PM,  <rob@xxxxxxxxx> wrote:
> Probably not then.
> Make sure that TAPMLB02 is set to automatically vary on at IPL and TAP02
> isn't.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:
> rick baird <rick.baird@xxxxxxxxx>
> To:
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:
> 03/19/2009 03:37 PM
> Subject:
> Re: Tape hardware resources
> Sent by:
> midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> we're using BRMS, so I'm guessing 'random'.
>
> do I need TAP02?
>
> On Thu, Mar 19, 2009 at 2:46 PM,  <rob@xxxxxxxxx> wrote:
> > Leave tap02 with a resource name of TAP02.  Vary off TAPMLB02.  Try to
> > vary on TAP02 again.
> > You are using this in 'sequential' mode and not 'random' mode, right?
> > Otherwise you are going to play heck getting tap02 working.
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > From:
> > rick baird <rick.baird@xxxxxxxxx>
> > To:
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Date:
> > 03/19/2009 02:32 PM
> > Subject:
> > Re: Tape hardware resources
> > Sent by:
> > midrange-l-bounces@xxxxxxxxxxxx
> >
> >
> >
> > Rob,
> >
> > I'm sorry - here's a correction - I was playing around and things have
> > changed.
> >
> > > What troubles are you having varying on the devices?
> >
> > With these settings, my vary on error is:
> >
> > Device descriptions look like this (differences marked <-----)
> >
> > Device description . . . . . . . . :   TAPMLB02
> > Option . . . . . . . . . . . . . . :   *BASIC
> > Category of device . . . . . . . . :   *MLB
> >
> > Device class . . . . . . . . . . . :   *TAP
> > Resource name  . . . . . . . . . . :   TAPMLB02
> > Device type  . . . . . . . . . . . :   3582
> > Device model . . . . . . . . . . . :   001
> >
> >
> > Device description . . . . . . . . :   TAP02
> > Option . . . . . . . . . . . . . . :   *BASIC
> > Category of device . . . . . . . . :   *TAP
> >
> > Device type  . . . . . . . . . . . :   3580
> > Device model . . . . . . . . . . . :   002
> > Resource name  . . . . . . . . . . :   TAP02        <----------
> >
> > When varying TAP02 on with this, it fails with:
> >
> > Cause . . . . . :   The device resource is currently in use by object
> > TAPMLB02
> >  type *DEVD. If the object name and type are blanks, either the resource
> > is
> >  in use by the Dedicated Service Tools (DST), another client, or the
> data
> > is
> >  not available.
> >     If a media library drive is being allocated, the drive may already
> be
> >  allocated to another media library device that is varied on.
> >
> > If I change the TAP02 resource to TAPMLB02 (which I would assume is
> > correct), it changes the description to:
> >
> > Device description . . . . . . . . :   TAP02
> > Option . . . . . . . . . . . . . . :   *BASIC
> > Category of device . . . . . . . . :   *TAP
> >
> > Device type  . . . . . . . . . . . :   *RSRCNAME   <-------
> > Device model . . . . . . . . . . . :   *RSRCNAME   <-------
> > Resource name  . . . . . . . . . . :   TAPMLB02    <-------
> >
> > and that's when I get this message:
> >
> > --00002006: The device type specified in the device description TAP02
> does
> >  not match the type associated with resource TAPMLB02.
> >
> > Thanks again,
> >
> > Rick
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.