|
Hi, Rod That sounds cool. I believe that, to use it with library objects, you actually DO tell it the object type. It's in the extension. E.g., a userspace named MYUSRSPC, in library VERN, would be /QSYS.LIB/VERN.LIB/MYUSRSPC.USRSPC (uppercase not required - just for emphasis). That makes this essentially like CHKOBJ, where you have to specify that object type. When something like readdir() or Qp0lProcessSubtree() gives you the path name, the object type, then is included for objects under the QSYS.LIB file system. The others have types like *STMF, *DIR, *DDIR, *SYMLNK, and a host of others. The object type is useful, for me, to keep me from looking at symbolic links, e.g. We have a product that walks the IFS tree, using Qp0lProcessSubtree() and Qp0lGetAttributes(). It''s kind of slow for full-tree walks. (I'm looking at different ways to accomplish our purpose quickly.) Another wrinkle is that some of the Qp0l* APIs were introduce only in V4R3 and later - check the QP0LSTDI member in QSYSINC/H to check this. My, there's a lot to talk about with this stuff, isn't there? Cheers Vern At 04:33 PM 8/28/02 +1000, you wrote: >This message is in MIME format. Since your mail reader does not understand >this format, some or all of this message may not be legible. >-- >[ Picked text/plain from multipart/alternative ] > >Vernon, > >for completeness, we could also add Qp01GetAttr() which has a more complex >structure returned than stat(), lstat(). >David Leland wrote a little freeware cmd called ChkIfsObj which uses just CL >and calls stat(). Whilst intended for stream files this could be used to >check *any* object too. The only downside to this cmd is that you don't tell >it what objecttype to check and it doesn't tell you what objecttype it found >(if it did). e.g. if you used it to check a user-parameter for a stream file >and it found a directory it would report ok. > >Rod Orr
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.