RE: Odd behavior with QDLS folder

  I tried creating an IFS folder but could not get the file created.

  It is a physical file with one field.  All of the records are copied to
  the text file using COPYTOPCD.

    ----------------------------------------------------------------------

    From:  "Bob O." <otis_the_cat@xxxxxxxxxxx>
    Reply-To:  Midrange Systems Technical Discussion
    <midrange-l@xxxxxxxxxxxx>
    To:  midrange-l@xxxxxxxxxxxx
    Subject:  Odd behavior with QDLS folder
    Date:  Fri, 21 Oct 2005 14:09:26 -0500
    >   This is confusing the **** out of me...
    >
    >   I created a folder in QDLS to hold a single text file.  Other
    >users need
    >   to access this *.txt file for uploading a the text file into a
    >database.   When they go to access the folder/file, they are
    >prompted for a user
    >   profile and password.  The only user/password that works is mine,
    >it will
    >   not accept theirs.
    >
    >   I checked the permissions through the iSeries Navigator.  I was
    >listed as
    >   the owner on both the folder and the file.  I deleted the folder,
    >created
    >   a new user specifically for the folder and file and then
    >recreated the
    >   folder using this user.  This user profile is now the owner for
    >both the
    >   folder and the file.  I also added all of the users to the
    >permission list
    >   with "All" access.  Still, the only user profile and password
    >that works
    >   to access the folder and file is mine.
    >   The PC is a Windows XP machine.
    >   Am I missing some step somewhere that will allow these users to
    >access the
    >   folder/file?
    >--
    >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: http://lists.midrange.com/mailman/listinfo/midrange-l
    >or email: MIDRANGE-L-request@xxxxxxxxxxxx
    >Before posting, please take a moment to review the archives
    >at http://archive.midrange.com/midrange-l.
    >