There was a small disconnect between the last and the previous poster, which is what I wanted to point out. No directory management, no SMAPI.
A doc check shows that DIRMAINT (specifically) was required at z/VM V5R2.
This prereq evolved to a generic directory manager at V5R3+ ... I hadn't
noticed that.
Thanks,
--Jim--
From: David Boyes <[EMAIL PROTECTED]>
To: [email protected]
Date: 10/22/2008 08:01 PM
Subject: Re: Lx86
It requires A directory manager, but it doesn't have to be Dirmaint.
Regardless of brand, you'll need some kind of disk/Dir management
package to do any useful automation so I'm not too worried about
making it a prereq.
On Oct 22, 2008, at 5:54 PM, "James Tison" <[EMAIL PROTECTED]> wrote:
>>> I, as a VM guy first, don't really see the big win over just using
>>> mdisks, but I suppose since we have no dirmaint / directory/
>>> vmsecure
>>> bits it would allow most of the VM's management to occur from the
>>> Linux side of things.
>>
>> Theoretically, that's what SMAPI is supposed to allow you to do.
>> The API
>> is kinda ugly, but you can do all the directory munging and disk
>> manipulation from a Linux app.
>>
>
> I'm pretty sure VSMSERVE (SMAPI) requires DIRMAINT.
>
> --Jim--
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO
> LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
