On Mon, Jul 28, 2008 at 10:10 PM, RPN01 <[EMAIL PROTECTED]> wrote:
> We started this way, but I felt that this made it harder to isolate, list,
> or find the LPAR specific minidisks. With them in the same userid, you have
> the entire list at hand.
The other motivation for your approach is that y
We started this way, but I felt that this made it harder to isolate, list,
or find the LPAR specific minidisks. With them in the same userid, you have
the entire list at hand.
On 7/28/08 2:04 PM, "Kris Buelens" <[EMAIL PROTECTED]> wrote:
> Now that you wrote this, I remember my setup which is ea
Now that you wrote this, I remember my setup which is easier in m eyes
(we only had 2 systems sharing the directory). For example
USER VMUTIL
MDISK 1191 RR
MDISK 2191 RR
SYSAFFIN system1
LINK * 1191 191 M
SYSAFFIN system2
LINK * 2191 191 M
Nowadays, one would probably use the RRD o
In principle, what you've done is correct... But very wrong. :-)
We NEVER put an mdisk statement under a SYSAFFIN statement. All the
minidisks that need to be "owned" by a specific LPAR are defined in the
userid DISKOWNR, and the only thing under the SYSAFFIN statements are LINK
statements back to
When I run DIRM DIRMAP in my CSE cluster, I get a map back that includes an
extra column indicating the SYSAFFIN'ed node that this minidisk is effective
on. This causes wierdness when you use the +VMRES symbolic for the VM
respack and have several VM releases in the cluster, but for everything else
On: Mon, Jul 28, 2008 at 08:08:00AM -0500,Florian Bilek Wrote:
} I am working now, thanks to Kris, with SysAffin in the Directory. In
} principle this works fine but I have now an issue with the DISKMAP utility.
} The report run on one system shows space of the disk as free where a
} SysAffin is c
Troubling indeed. Have you tried DIRMAP?
DIRM USER BACKUP
VMLINK DIRMAINT 1DB
DIRMAP USER BACKUP
(as creator of the DRM tool, I enter "DRMAC" instead to XEDIT USER
BACKUP and press F4 to run DIRMAP and XEDIT USER MDISKMAP)
2008/7/28 Florian Bilek <[EMAIL PROTECTED]>:
> Dear all,
>
> I am wo
Dear all,
I am working now, thanks to Kris, with SysAffin in the Directory. In
principle this works fine but I have now an issue with the DISKMAP utilit
y.
The report run on one system shows space of the disk as free where a
SysAffin is coded for another system.
IMHO this will lead to confusion