× 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.



Charles

As to #2 - you don't really NEED QSYSINC. If you are using APIs in RPG, you can construct your own data structures - these CAN change from release to release, but, as Jim Wiant said, are clearly documented. Much less surprising than PRTF output changes. Also, you usually need to recompile only when there is something new you want to use. Yes, there are exceptions! But not many.

As to #3 - if you use the offsets and all in API structures, you are pretty well protected from the changes. It's when you start using constants and hard-coding things like positions into a structure that you get bit badly.

Prototypes - well, none of the QSYSINC stuff has RPGLE prototypes - only data structures for the most part. Maybe some constant for the API program name - I'd have to look, but it's not very useful to me.

There are several online sources for prototypes - the more common APIs, anyhow. A google search with the API name and the word prototype and RPG will usually net you some nice hits.

HTH
Vern

On 8/2/2012 5:38 PM, Charles Sallee wrote:
Guys,


I appreciate everyone's comments on this and, 'best practices' aside; I
went with the spool file option for several reasons:


1. I have lots of experience using this method (we always done it
that way! :-) :-)).

2. I can not get the operations staff to load the QSYSINC copy
library.

3. I don't have much experience with APIs and they can also change
with a release.


I know #3 is not likely but a possibility.


Jeff, thanks for your note. I had looked at the DSPJOB printout and
overlooked the job date. So, you helped me finish the task the way I
had started.


All of this brings me back to the reason for writing this code. Has
anyone else experienced a problem with Client Access when the user turns
off their PC before shutting down Client Access? About once a week
someone will do so (or the PC crashes) and I get a runaway job that is
eating up a lot of the CPU.


The job log has the following messages in it:

Session stopped by a request from device SG8BWCP1A1.

Input or Output request failed. See message CPF5140.


For my procedure, after checking the WRTACTJOB printout, I wanted a way
to check the job date before any further logic.


Thanks again for all of your comments and help.


Chuck S. (not to be confused with guru Chuck P.)




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.