THANK YOU..... Downloading now.
Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We're here to make lives better." I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. From: Alan Altmark <[EMAIL PROTECTED]> To: IBMVM@LISTSERV.UARK.EDU Date: 12/12/2007 01:33 PM Subject: Re: Dirmaint and RACF - a disconnect On Wednesday, 12/12/2007 at 03:48 EST, "Lionel B. Dyck" <[EMAIL PROTECTED]> wrote: > disclaimer - I do have this reported to IBM > > I have a challenge with Dirmaint and RACF > > Doing a "DIRM ADD userid" results in the account being created but an MDISK or > AMDISK statements in the "userid direct" are not fully processed. By that I > mean that the directory knows about the disks but when I log on to the new > account none of the disks are their in either a Q DISK or Q DASD. The consensus > here is that DIRM is not issuing the appropriate RACF Permit to allow the > account access to its own mini-disks. > > Has anyone else seen this and/or have any insight? Look at APAR VM64275. It fixes the PERMIT issued by DIRMAINT. Alan Altmark z/VM Development IBM Endicott
<<image/gif>>
