RE: IFS and OPENDIR

As others have said check the errno value. I just checked and I have
directories opening with paths of at least 100. The usual culprit in
these cases is spaces. Either spaces at the end of you path that you
didn't know existed, or using a variable with spaces at the end of it
when calling opendir.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Doug Englander
Sent: Monday, April 9, 2018 1:21 PM
To: midrange-l@xxxxxxxxxxxx
Subject: IFS and OPENDIR


I have a situation where the OPENDIR command is returning a NULL for a
directory that does exist on the IFS. I have tried having a slash at

the end of

the path, and not having the slash. Both ways return NULL. I verified

the

authority on all levels of the folder, and it is fine *PUBLIC

basically has *ALL to

the folder and the folders within it.

My only success seems to be with the length of the directory path

being

passed to it. Is there a maximum length of this path? This seems to

work

sometimes, but not consistently. When it does work, I believe it is

because

the parameter being passed is small i.e. 80 characters or less. Is

there a limit

as to the length of the parameter passed to OPENDIR?

Thank you,

Doug

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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: http://amzn.to/2dEadiD