×
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.
I solved my own problem. I was trying to make it more complicated than it
needed to be. I tried using the program name and the procedure name on the
message APIs without much success. When I simply used '*' on the APIs in
place of the program/procedure name, that solved it.
-----Original Message-----
From: Robert J. Mullis
Sent: Thursday, October 27, 2011 12:18 PM
To: RPG programming on the IBM i / System i
Subject: MAIN Keyword and Error Message Subfiles
I have been using procedures and error message subfiles for quite awhile
now and haven’t had any issues with getting my messages to display. I
recently tried using the MAIN keyword on the H-spec and defining my mainline
as a procedure. That is working fine, but I can’t get my error message
subfile to display my messages. I have put the program in debug to make
sure that my error is getting triggered correctly. The error message is
coming from a procedure 3 levels into the call stack of the program.
Previously, I simply sent the message to the message queue of the program,
but that doesn’t work with the MAIN keyword. I get an error telling me that
the name is not found in the call stack. I have changed the SFLPGMQ length
in my DSPF to 276 and tried loading the MAIN procedure name into it, as well
as the name of the procedure sending the message. Neither have worked. The
message gets sent, but it will not display on the screen.
Has anyone else encountered this issue? And if so, how didn’t you
correct it?
As an Amazon Associate we earn from qualifying purchases.
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.