|
CHGJOB INQMSGRPY(*DFT) should take care of that. Help on INQMSGRPY parameter: *DFT The default message reply is used to answer any inquiry messages issued during the running of this job. Thanx, PLA -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Denis Robitaille Sent: Friday, August 24, 2001 2:51 PM To: midrange-l@midrange.com Subject: RE: reply list (WRKRPYLE) This would change the default answer, but what I want is to have an automatic response (so the user do not have to press enter). Thanks anyway. Denis Robitaille Directeur services techniques Cascades Inc 819 363 5187 fax 819 363 5177 >>> Patrick.Archibald@HomeTelco.com 08/24/01 01:21pm >>> Denis I think you could create a message file, duplicate the message descriptions you want to change the default on, change the message description: CHGMSGD MSGID(CPFXXXX) MSGF(QGPL/NEWMSGF) DFT(I) do an OVRMSGF MSGF(QCPFMSG) TOMSGF(QGPL/NEWMSGF) in your CL. Thanx, PLA -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Denis Robitaille Sent: Friday, August 24, 2001 1:12 PM To: MIDRANGE-L@midrange.com Subject: reply list (WRKRPYLE) Hello all, I have a need to add an automatic reply to a message, but only for certain jobs. As far as I know, I cant specify an automatic reply restricted to a specific job. We have a solution, but it bring one question mark. Here it is: We can (in a CL) add a reply to the specific message before the instruction that needs it and then remove the automatiuc reply right after it. But to do so, we will use about 20 entries in the reply list. Some of my collegue think that in the future, IBM (or a third party product) may add entry in the reply list and that they may collide with the ones that I would add/remove repetidely. Does anybody knows if there is a range that is safe to use? Any other tought? Thanks Denis Robitaille Directeur services techniques Cascades Inc 819 363 5187 fax 819 363 5177 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com
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.