Michael,

The requirements for the system where this is being run are that this
routine be written in COBOL. (Hence, I haven't posted the sample code as
most on this list wouldn't follow it.)

As you posted to midrange rather than rpg I don't believe posting COBOL
code would have been much of a problem. You might be surprised by how many
IBM i COBOL developers are around (and on this list). Seeing the actual
call might have accelerated resolution of the problem.

On Mon, Dec 30, 2019 at 8:31 PM Michael Quigley <MichaelQuigley@xxxxxxxxxx>
wrote:

Kevin/Scott and others,

Kevin--Yes that's what we're talking about.

Thanks to all who responded.

The issue came down to the requirement for the Mode to be passed by value.
The requirements for the system where this is being run are that this
routine be written in COBOL. (Hence, I haven't posted the sample code as
most on this list wouldn't follow it.)

I added the "BY VALUE" phrase for Mode and now I'm getting the expected
results. I found this before IBM got back to me on the Case (formerly known
as PMR) by searching through previous code working in the IFS.

Thanks for the responses to Kevin and all who responded.

Michael Quigley
Computer Services
The Way international
www.TheWay.org


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Kevin Bucknum
Sent: Monday, December 30, 2019 3:54 PM
To: Midrange Systems Technical Discussion <midrange-
l@xxxxxxxxxxxxxxxxxx>
Subject: RE: mkdir() API and IFS authorities

Actually your copybook does use the options(*string), but I just stripped
that
code out off a fix format program and it compiled and worked, so didn't
bother fixing it up. I'm not having the issue. My example is how it is
working
for me, which is the way I expect it to, and the way it is documented to
work.
It's not working for Michael, and I think he is going to open up a PMR.
My
example was just to make sure Michael and I were talking apples to
apples.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Scott Klement
Sent: Monday, December 30, 2019 2:42 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: mkdir() API and IFS authorities

Kevin,

Thanks for the example. From what you've posted there, you are doing
this:

Mode = S_Ixusr // My user profile - *X only
+ S_Iroth + S_Iwoth; // Other (*PUBLIC) *RW Path =
'/kevin/mkdirtest/newfolder' + x'00'; Mkdir(%Addr(Path):Mode);

This code looks like it was written for V3R2 with the manual x'00' and
%addr(). It'd be nice to modernize that a bit to use options(*string),
but the
old way still works.

As the comments say, you're asking for your user profile to have *X and
the
public to have *RW. in your screenshot that follows the code you show
this:

*PUBLIC *RW
KEVIN *X

As far as I can tell, this is exactly what was expected. Can you
explain what the trouble is?

-SK

On 12/30/2019 1:14 PM, Kevin Bucknum wrote:
I'm in the root file system. I threw together an example of what I'm
seeing
just to make sure we are talking about the same things. And I'm on V7R3
btw.

https://code.midrange.com/076773896a.html



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.