Re: QDLS limited readdir()

[craigs@xxxxxxxxx]

IBM pointed out my problem with using readdir() in directory QDLS as using
a "clear" opcode with QDLS.
The bad line of code is the "clear" opcode just before the readdir() call:

     C                   Clear                   dirent
     C                   Eval      p_dirent = readdir(dh)

The 'dirent' field is based off p_dirent. That storage is given back to
the application by the previous readdir(). It is NOT to be changed by
the application. That storage, in essence, is owned by readdir(), not
the application. The application can read it, of course, but should
never change it. The "Clear" statement above must be removed.

On one readdir() QDLS actually retrieves many directory entries and
squeezes them into that space. It also stores information necessary to
retrieve the next directory entry there. Other file systems, like the
root, don't do that and so clearing the space doesn't hurt. Again,
though, the application should never change the contents of what it
gets back from readdir().

** Craig wrote:
Scott mentioned using / instead of \.  That was just a typo in my e-mail.
I am already using / unsuccessfully.  I am also enrolled in the system
distribution directory (WRKDIRE).  I have all authority to QDLS and most
folders in QDLS.  Doing WRKLNK '/QDLS' shows PUBLIC *RWX for data and no
authority for object.  I can see most of the folders in QDLS using WRKLNK.

** Craig wrote:
I have been listing directories and files in the IFS for quite some time
now.  I recently discovered I was not listing anything in the \QDLS
directory.  I am using RPG IV with the opendir() and readdir() in a
recursive subprocedure.  This appears to get all directories and files
except those in the \QDLS directory.  On debug, I see that \QDLS is
successfully opened and only one directory (".") is read.  There are many
directories (folders) with files but they do not show up on any of the
readdir()s.  Any ideas?

Craig Strong