We are doing this by passing into the service program the name of the
program calling it. That way the service program uses the other programs
message queue and not it's own. Just setup another procedure and pass in
the program name into the spgmq field of the service program.

I am not sure why changing the length makes a difference.

Jack Long
CBK Ltd.

"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote on 08/08/2008
04:30:03 PM:

"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
08/08/2008 04:30 PM

Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>



message subfile not working in service program

I'm attempting to use message subfile on a service program for the first
time and am having problem with it.

On the DSPF file, I have the SFLPGMQ(10) keyword on both the message
subfile and control record formats. In a regular RPG ILE program, I
usually set the value of SFLPGMQ(10) as the program name and use send
program message api to send messages that I want to display to the
Program Message Queue. This method works fine in regular ILE RPG

I attempted the same think on a service program and I'm getting a
CPF2479 error. This problem goes a way if I change the SFLPGMQ(10) to
SFLPGMQ(276) and place the value of the procedure name as the value of
SFLPGMQ(276). Just curious as why using the service program name as
value SFLPGMQ(10) won't work on service program.


This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].