Re: DSFS Error

2025-01-16 Thread Paul Gilmartin
On Thu, 16 Jan 2025 18:01:50 +, Mark Jacobs wrote: >Yea. I found that idea and gave it a big upvote too. I also added one of my >own. TL;dr. Just pass any new allocation over to DFSMS to handle using its >already in place ACS logic. > >https://ideas.ibm.com/ideas/ZOS-I-4384 > Can't happen.

Re: DSFS Error

2025-01-16 Thread Mark Jacobs
Yea. I found that idea and gave it a big upvote too. I also added one of my own. TL;dr. Just pass any new allocation over to DFSMS to handle using its already in place ACS logic. https://ideas.ibm.com/ideas/ZOS-I-4384 Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public

Re: DSFS Error

2025-01-16 Thread Lionel B Dyck
See https://ideas.ibm.com/ideas/ZOS-I-3849 On Thu, Jan 16, 2025 at 11:01 AM Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > > On Wed, 15 Jan 2025 18:13:35 +, Mark Jacobs wrote: > > >Is there anyway to get around this restriction? > > > >IDFS03229E Could not set creatio

Re: DSFS Error

2025-01-16 Thread Paul Gilmartin
On Wed, 15 Jan 2025 18:13:35 +, Mark Jacobs wrote: >Is there anyway to get around this restriction? > >IDFS03229E Could not set creation parameters, return code 111 reason code >ED076242. >6242 The dsadm createparm command failed because the HLQ of the high-level >qualifier directory name do

DSFS Error

2025-01-15 Thread Mark Jacobs
Is there anyway to get around this restriction? IDFS00329E Could not set creation parameters, return code 111 reason code ED076242. 6242 The dsadm createparm command failed because the HLQ of the high-level qualifier directory name does not match the current user ID. Sent from [ProtonMail](http