ASP question

We don't have user ASPs set up so, apologies, but I'm not able to answer this question for myself by testing things out and I'm having difficulty finding the answer online.

One of our tools, which is used 99% of the time to access stream files in the IFS, also supports the use of the /QSYS.LIB naming format to allow processing of members in physical files. This works fine most of the time.

However, a customer of ours has a case where this is returning a "not found" condition (errno 3025 message id CPE3025) on a particular member, which definitely exists. This is coming back from a call to the lstat API.

Doing a WRKLNK '/QSYS.LIB/LIBRARY.LIB/FILENAME.FILE/MEMBER.MBR' also fails to find the member.

The only thing I can see that is any way "special" here is that the library in question is in a user ASP. I believe that to access an IFS directory in a user ASP you need to mount a UDFS over the directory, and refer to directory using the /dev/QASPxx etc. naming convention, so I'm wondering whether the /QSYS.LIB naming convention won't work on libraries in user ASPs? Can anyone confirm or deny that theory? It seems unlikely to me but I'm beginning to clutch at straws here.

If it it the case that you can't using /QSYS.LIB naming in this instance, since it does not appear to be possible to mount a UDFS over a multi-member file (i.e. treat it as a directory), is there any way to use IFS-style naming to refer to a member in a file in a library in a user ASP? Is there some naming trick I'm missing, maybe including the ASP name in the path somehow?