|
G, this code works fine for *EXCP messages when you use MSGQ(*PGMQ) MSGTYPE(*EXCP) (and *COMP messages too). But those pesky *DIAG's are just out of my reach. -G On 5/5/06, Grizzly Malchow <grizzlym@xxxxxxxxxxxxxxxxxxxxx> wrote:
I haven't tested the code, but it might be a start. DCL VAR(&KEYVAR) TYPE(*CHAR) LEN(4) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) DCL VAR(&SEV) TYPE(*DEC) LEN(2 0) DCL VAR(&RTNTYP) TYPE(*CHAR) LEN(2) MSG: RCVMSG MSGQ(SOMEMSGQ) MSGTYPE(*DIAG) RMV(*NO) + KEYVAR(&KEYVAR) MSGID(&MSGID) SEV(&SEV) + RTNTYPE(&RTNTYP) IF COND(&MSGID *EQ 'CPD32E7') THEN(DO SOMETHING) -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Guthrie G Sent: Friday, May 05, 2006 9:05 AM To: midrange-l@xxxxxxxxxxxx Subject: Receiving *DIAG messages I'm trying to receive a diagnostic message (CPD32E7, "The trigger operation failed") in a CLLE program with RCVMSG but I haven't been able to find a published example. I'd be grateful for a snippnet of code or a link. Thanks, GP -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.