× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Assuming that he has decided to use IFS to check for the file (and I'm not sure I'd do that) then why on EARTH would he want to do a kludge like call CHKIN from an RPG program?!

If you must use CHKIN, do it from a CL program. Still a kludge, IMHO, but at least you don't have to worry about character escaping, et al.

But, I recommend using the access() API, since that's what it's designed for. From RPG, I'd call access() directly. From CL, I'd use one of the wrappers, like CHKIFSOBJ.



On 8/9/2010 10:13 PM, Dave wrote:
Just use CHKIN and monitor for CPFA0BE. It has worked without issues for a
long time in a couple of our apps.

We wrote a small subprocedure in our "general" service program called
CheckFileExist().

We use this all the time, so we created a small subprocedure to verify files
exist on the QNTC share...

DCheckFileExist pi n
D sFileIn 50a const

// Work Variables
D sFile s 52a inz
D sApost s 1 inz('''')

/free

// Setup path name with document name.
sFile = sApost + %trim(sFileIn) + sApost;

// Use CHKIN to determine if any documents exist.
system('CHKIN OBJ(' + %trim(sFile) + ')');

// If documents exist, 'CPFA0BE' will be returned from the CHKIN
// command since CHKIN is not allowed for a document in the QNTC
// file system. If no documents exist, 'CPFA093' is returned.
return (cpfmsg = 'CPFA0BE');


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.