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


  • Subject: Re: API for subfile messages.
  • From: Buck Calabro/commsoft<mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 23 Mar 1999 10:05:40 -0500

On 03/23/99 04:26:00 AM Rowthu Ravichandra  wrote:

>I have used API's for subfile messages. Interestingly, On one run I find 
the
>messages displayed in the 24th line and on the other run, there are no
>messages. I am attaching the source code for the RPGLE program I have 
used.
>Can anyone explain why this happens?? I am now forced to write a CLP for 
the
>same task.

Ravi,
  I like the API approach, but haven't used it myself yet.  In my old code, 
when I want to clear messages, I do an EXFMT MSGCTL with the SFLCLR 
indicator set on.  If you use *ALL, with QMHRMVPM, aren't you removing all 
the messages in the job message queue?  I'm wondering if there's some 
discrepancy between the job message queue and the subfile.  Do you ERASE 
the error subfile at any point? 

Buck Calabro
Billing Concepts Inc (formerly CommSoft), Albany, NY
mailto:mcalabro@commsoft.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.