|
<<SNIP>>
What I'm thinking is to write a marker in ProgA before calling
ProgB as Scott suggested.
Change ProgC to pass 'ProgA' to ProgD to write the message.
(Currently it is passing 'ProgC') <<SNI>>
On Tue, Apr 20, 2010 at 2:10 PM, Scott Klement wrote:
<<SNIP>>
On 4/20/2010 9:57 AM, Robert Rogerson wrote:
I'm having trouble receiving a message which I can see in the
job log.
Here is the scenario...
ProgA calls ProgB
ProgB calls ProgC
An error occurs in ProgC
ProgC calls ProgD to send the message
ProgD sends the message
(SNDPGMMSG MSGID(WDC0145) MSGF(TFMMSG) MSGDTA('')
TOPGMQ(*SAME ('WIM331')) KEYVAR(&W@MSGNO)
ProgD ends
ProgC ends
ProgB ends returning an error
If an error occurred
// Receive program message
QMHRCVPM( msgBack
: %Size(msgBack)
: 'RCVM0100'
: '*'
: 0
: '*PRV'
: Pm_MKey
: 0
: '*SAME'
: Qusec )
I want to receive the message issued by ProgD (this may be
different errors depending on the error generated in ProgC)
so I may display it in ProgA
to give a better indication of what error occurred. One
condition I should add is that ProgC and ProgD are vendor
supplied programs I am trying to avoid changing.
Can anyone shed some light on what I am doing wrong?
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.