|
Hello David, You wrote: >To a certain degree you can use a fixed name. By default, I send all >user messages for interactive jobs to a single program queue. In a batch >job I send them to *PRV. I also do this with a standard set of >procedures I wrote a few years back. Those procedures hide many of the >ugly details of PEPs etc. They do allow you to override this behavior. I have a similar set of procedures to encapsulate the gory details of message handling -- I think they were among the first set of RPG procedures I wrote. Carsten reminded me of some additional options I had forgotten which nullify the effect of the generated RPG IV entry point name. How do you find the single program queue works in practice? How do you set that up? I mean does your application "know" the call stack and send all messages to the program queue of the main program? Do you walk the call stack looking for a specific program queue? Do you send all messages to the users message queue? I'm curious because I would think that sending to *PRV regardless of where the job is running would be a simpler approach. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.