HP3000-L Archives

June 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Lancaster <[log in to unmask]>
Reply To:
Bill Lancaster <[log in to unmask]>
Date:
Tue, 16 Jun 1998 18:29:17 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
I'd also add that the next time (if there is one :-) I'd recommend naming
the set something like PROD and skip the "_SET".  It's repetitively
redundant over and over again.  :-)

Bill

At 05:21 PM 6/16/98 -0700, Stan Sieler wrote:
>Glen writes:
>
>> NEW SETUP.
>>
>> LDEV1      MEMBER1     MPEXL_SYSTEM_VOLUME_SET
>> LDEV2      MEMBER2     MPEXL_SYSTEM_VOLUME_SET
>> LDEV3      MEMBER3     MPEXL_SYSTEM_VOLUME_SET
>> LDEV5      MEMBER5     PROD_SET
>> LDEV11    MEMBER11   PROD_SET
>> LDEV12    MEMBER12   PROD_SET
>> LDEV13    MEMBER13   PROD_SET
>> LDEV14    MEMBER14   PROD_SET
>> LDEV15    MEMBER15   PROD_SET
>> LDEV16    MEMBER16   PROD_SET
>> LDEV17    MEMBER17   PROD_SET
>> LDEV18    MEMBER18   PROD_SET
>
>The only thing I'd recommend is that next time (if there is one :),
>I'd name the PROD_SET members something like PROD1, PROD2, ...
>there's little benefit (generally) in linking the volume name to
>an ldev, particularly since you could renumber the ldevs and the
>volume would still be found.
>
>
>--
>Stan Sieler                                          [log in to unmask]
>                                     http://www.allegro.com/sieler.html
>
>

ATOM RSS1 RSS2