[Info-vax] Moving UAF records from Cluster to Cluster

Paul Sture paul.nospam at sture.ch
Wed Jul 27 08:36:44 EDT 2011


In article 
<294b9314-72d8-4fad-83a6-8cab7aeadffa at c29g2000yqd.googlegroups.com>,
 FrankS <sapienza at noesys.com> wrote:

> On Jul 26, 11:44 am, Thomas Wirt <twn... at kittles.com> wrote:
> > I am migrating from a VMS Alpha cluster to a new VMS IA64 cluster. I
> > would like to be able to move individual accounts/records from one
> > cluster to the other.
> 
> You would be far, far, better served by creating a mixed architecture
> cluster and using a single, common SYSUAF, RIGHTSLIST, NET$PROXY,
> queue manager, password history, and so on.  Otherwise you're just
> asking for trouble somewhere down the line.

Using that route you need to look at the PQL parameters to adjust quotas 
and other process limits per architecture.

When we were running a mixed architecture VAX/Alpha cluster, we chose to 
have separate UAF files, because:

a) Using PQL_M* parameters affects all users on a system; we
   wanted per user tuning instead.
b) We were running a large production line so couldn't afford to
   get this wrong.
c) With the DCL procedures we had in place, we only had to execute
   the same command twice to create an account per architecture.
   Not a big deal.

-- 
Paul Sture



More information about the Info-vax mailing list