× 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: Message Subfiles and ILE
  • From: David & Eileen Keck <bstars@xxxxxxxxxxxxx>
  • Date: Sun, 27 May 2001 22:50:22 -0700

Consider a working RPG/400 program and associated DDS whose sole purpose is
to display a message in a message subfile on a standard *DS3 non-window
display file.  If you create an ILE version of the program using CVTRPGSRC
(to activation group QILE), would you expect the converted program to behave
the same as original version ?  I did, but no entry ever appears in the
message subfile of the ILE version of the program.

The Send Program Message API QMHSNDPM does cause the message to be reflected
in the job log, and the message details (F9) indicate a correct call stack
entry.  In my test code I specify the Call Stack Entry / Program Queue to be
'*' for both the QMHSNDPM API and the SFLPGMQ DDS keyword.  I have tried
both SFLPGMQ(10) and SFLPGMQ(276).   I can post the code but thought someone
might know what's wrong from this description alone.  Thanks - Dave K.

+---
| 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-Ups:

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.