RE: CHKOBJ in RPG IV programme

["Orr, Rod" <ROrr@xxxxxxxxxxxxxx>]

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 ]

-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@attbi.com]
.....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.....


Vern, Quite right, the objtype for a QSys object is implicit in the Path
name.
I wasn't suggesting people use ChkIfsObj (meaning stat()) instead of ChkObj
for QSys objects. ChkObj is clearly the obvious choice, merely that
ChkIfsObj wasn't necessarily doing what people thought it did (i.e. checking
for a stream file existence). If you were using ChkIfsObj in a CLP to check
a user-entered path parameter (e.g. StmF) you could get (theoretically) a
"found" condition on an object that wasn't, say, a streamfile
I have modified ChkIfsObj to include an ObjType parm (only supported  *STMF,
*DSTMF, *DIR, *DDIR, *SYMLNK, *FLR, *DOC)

In a previous pend you said "The gotcha with stat() is that it follows
symbolic links - like a shortcut in Windows. " In what way do you see
symbolic links as a gotcha? Could you elaborate?

Rod Orr

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



**********************************************************************
This email may be confidential and/or privileged. Only the intended
recipient may access or use it. Any dissemination, distribution or
copying of this email is strictly prohibited. If you are not the
intended recipient please notify us immediately by return email and
then erase the email.

We use virus scanning software but exclude all liability for viruses
or similar in any attachment or message...,..,..,.


**********************************************************************