|
It would be up to the break handling program to decide what to do based on the inbound message. It could do a DSPMSG and emulate the default DLVRY(*BREAK) action, or it could do anything else. If this is a oft-forgotten task it could call the program to perform the task. I have a break handling program that sends my "job completed" messages to me as status messages so they don't get in my way, but my "job failed" messages still pop up. Nice when you're compiling 100s of things and only one fails -- just one popup. -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Friday, August 27, 2004 9:28 AM To: Midrange Systems Technical Discussion Subject: Re: Break handling program Would this break message then go to a program and not break into the users interactive job? I've always HATED break messages. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx 08/27/2004 02:26 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: Break handling program Hi, > How might I have a new job run a command without changing the initial > program? How about setting up a routing entry to make the first program called be a CL that changes the message queues? Something like: ADDRTGE SBSD(QINTER) SEQNBR(5) CMPVAL(QCMDI) PGM(MYLIB/MYPGM) Then have MYLIB/MYPGM look something like this: PGM CHGMSGQ MSGQ(*USRPRF) DLVRY(*BREAK) PGM(MYBRKPGM) TFRCTL PGM(QCMD) ENDPGM -- 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.